maemo.org - Talk
Page 1 of 3 1 23
Show 40 post(s) from this thread on one page

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Alternatives (https://talk.maemo.org/forumdisplay.php?f=36)
-   -   N900 rescue OS - testing release (https://talk.maemo.org/showthread.php?t=75369)

NIN101 2011-07-31 15:08
N900 rescue OS - testing release
 
A rescue initrd for the N900. It can mount the maemo rootfs, can access the EMMC, has mass-storage support, USB networking cababilities and WiFi support. It can also charge the battery (which it currently doesn't automatically, please refer to the documentaiton for that).

Please keep in mind that this is a testing release which might mean that something won't work. It comes with absolutely no warranty! Usage at own risk
To use it, you need to be familiar with the linux console.

Version 1.3:
Download: here mirror

This project should not be confused with the meego rescue initrd.

Thanks to: The meego project(mainly for the kernel), #maemo on freenode and everyone who's work I have used here :-).

prankster 2011-07-31 15:15
Re: N900 rescue OS - testing release
 
oh man ,this is gonna get everyone crazy ,its awesome.. man !! great work .

abill_uk 2011-07-31 15:21
Re: N900 rescue OS - testing release
 
Yep sounds good to me keep up the great work, sounds like this is going to be something everyone needs at some point or other, great work !!!.

cutehunk04 2011-07-31 19:53
Re: N900 rescue OS - testing release
 
still i didnt get what actually it does ?

kingoddball 2011-08-02 03:12
Re: N900 rescue OS - testing release
 
Quote:
Originally Posted by cutehunk04 (Post 1061858)
still i didnt get what actually it does ?
I'm a little puzzled by this as well. BackupMenu also has these features (USB mount etc).

But! Any new OS is great! Time to download and prod and probe...

NIN101 2011-08-02 09:29
Re: N900 rescue OS - testing release
 
BackupMenu is good. In fact, in many cases, stuff invoked from /sbin/preinit(for example, a shell, or BackupMenu), is sufficient to fix messed up things. Under normal circumstances, you won't need a rescue os. But:

-BackupMenu has to be already installed before you break your things. It can not help you afterwards, if you didn't have backups(you should :-) ).

-It can not help you(say by providing a shell) in some worst case scenarios (say a borked busybox, broken libc, syntax errors in /sbin/preinit prior to backupmenu.sh execution), simply because it is not designed for that and couldn't do it by design. Flashing would be required anyway.

So, RescueOS and BackupMenu are two different things which can hardly be compared. RescueOS has been created for one simple reason: There wasn't imho a non-PITA solution known to me out there to mount your rootfs and access the EMMC partitions with a broken maemo system.

Once RescueOS can charge the battery, I think more people will find a usecase for it.

Nokia 5700 2011-08-03 00:48
Re: N900 rescue OS - testing release
 
Sweet! :)
I love recovery terminals like these.
It would be nice to have this as a simple recovery solution. Which text editors does it have?
I do hope it has nano? Because vi just wouldn't work without an Escape button.

But there is a small fact that not many know about. If you have NITDroid, you basically have a recovery solution. At least in UMay, you find a terminal app in the Dev Tools app. And root privilieges are simple to acquire. From there, you actually find all Maemo partitions mounted in /mnt/... And that's it.

GSMobserver 2011-08-03 04:35
Re: N900 rescue OS - testing release
 
"maemo code cracking" as per your list of features...


this is going to be good,,looking forward to the final version..

RobbieThe1st 2011-08-03 12:26
Re: N900 rescue OS - testing release
 
Quote:
Originally Posted by NIN101 (Post 1062690)
Once RescueOS can charge the battery, I think more people will find a usecase for it.
If you can find an i2cget/i2cset binary(or copy/compile Pali's one), charging the battery should be simple. Here's the script I've been using with Backupmenu:
Code:
#/bin/bash
# Reset

#echo -n Reset...
#i2cset -y -m 0x80 2 0x6b 0x04 80
#echo -n Done. Sleep 1...
#sleep 1
#echo -n Done.

#echo "Charger: " $(cat /sys/devices/platform/musb_hdrc/charger)

# Disable charger for configuration:
i2cset -y 2 0x6b 0x01 0xcc # No limit, 3.4V weak threshold, enable term, charger disable


# Register 0x04
# 8: reset
# 4: 27.2mV  # charge current
# 2: 13.6mV
# 1: 6.8mV
# 8: N/A
# 4: 13.6mV # termination current
# 2: 6.8mV
# 1: 3.4mV
# 7-1250 6-1150 5-1050 4-950 3-850 2-750 1-650 0-550
# 7-400 6-350 5-300 4-250 3-200 2-150 1-100 0-50
i2cset -y -m 0xFF 2 0x6b 0x04 0x50;

# Register 0x02
# 8: .640 V
# 4: .320 V
# 2: .160 V
# 1: .080
# 8: .040
# 4: .020 (+ 3.5)
# 2: otg pin active at high (default 1)
# 1: enable otg pin
i2cset -y -m 0xfc 2 0x6b 0x02 0x8c;
# 4.2 = 3.5 + .640 + .040 + .02 = 8c
# 4.16 = 3.5 + .640V + .020 = 84
# 4.1 = 3.5 + .320 + .160 + .08 + .04 = 78
# 4.0 = 3.5 + .320 + .160 + .02 = 64
# 3.9 = 3.5 + .320 + .080 = 50

# Register 0x1
# 8: 00 = 100, 01 = 500, 10 = 800mA
# 4: 11 = no limit
# 2: 200mV weak threshold default 1
# 1: 100mV weak treshold defsult 1 (3.4 - 3.7)
# 8: enable termination
# 4: charger disable
# 2: high imp mode
# 1: boost
i2cset -y 2 0x6b 0x01 0xc8;

# Register 0x00
# 8: Read:  OTG Pin Status
#    Write: Timer Reset
# 4: Enable Stat Pin
# 2: Stat : 00 Ready 01 In Progress
# 1:      : 10 Done  11 Fault
# 8: Boost Mode
# 4: Fault: 000 Normal 001 VBUS OVP 010 Sleep Mode
# 2:        011 Poor input or Vbus < UVLO
# 1:        100 Battery OVP 101 Thermal Shutdown
#          110 Timer Fault 111 NA
i2cset -y 2 0x6b 0x00 0x00;

#echo -n "Charge parameters programmed. Sleep 1..."
sleep 1
#echo "Status: " $(i2cget -y 2 0x6b 0x00)
i2cset -y 2 0x6b 0x00 0x80 # timer reset
cat /sys/devices/platform/musb_hdrc/charger >/dev/null

# Initialize variables
THROTTLE=0
FULL=0
MODE="STANDBY"
WALLCHARGER=0

# Assuming a nice round number 20mOhm for bq27200 sense resistor
RS=20

get_nac ()
{
    NAC=$(i2cget -y 2 0x55 0x0c w)
    NAC=$(($NAC * 3570 / $RS / 1000))
}
get_rsoc ()
{
    RSOC=$(i2cget -y 2 0x55 0x0b)
    RSOC=$((RSOC))
}
get_volt ()
{
  VOLT=$(i2cget -y 2 0x55 0x08 w)
  VOLT=$(($VOLT))
}

STATUS=$(i2cget -y 2 0x6b 0x00)
while true ; do
  sleep 15;
  STATUS=$(i2cget -y 2 0x6b 0x00)
  #echo $STATUS

  i2cset -y -m 0x80 2 0x6b 0x00 0x80; # timer reset
  get_nac
  get_rsoc
  get_volt

  if [ $MODE == "STANDBY" ] ; then
      if [ $STATUS == 0x10 ] || [ $STATUS == 0x90 ] ; then
        MODE="CHARGING"
        #echo $(date) "standby -> CHARGING. Current available capacity: " $NAC "mAh" >> /home/user/MyDocs/charger.log
        echo 60 > /sys/class/backlight/acx565akm/brightness
        WALLCHARGER=$(cat /sys/devices/platform/musb_hdrc/charger)
      fi
  fi
  if [ $MODE == "CHARGING" ] ; then
      if [ $STATUS == 0x00 ] ; then
        MODE="STANDBY"
        echo 15 > /sys/class/backlight/acx565akm/brightness
        #echo $(date) "charging -> STANDBY. Current available capacity: " $NAC "mAh" >> /home/user/MyDocs/charger.log
        WALLCHARGER=0
        # This will stop USB from eating power as long as you haven't plugged it into a PC
        echo 0 > /sys/devices/platform/musb_hdrc/connect
      fi
  fi

  if [ $STATUS == 0xa0 ] && [ $FULL == 0 ] ; then
      #echo "Charge done"
      #echo $(date) "FULL: " $NAC "mAh" >> /home/user/MyDocs/charger.log
      FULL=1
  fi
  if [ $STATUS == 0x00 ] && [ $FULL == 1 ] ; then
      FULL=0
  fi
  echo Status: $STATUS Mode: $MODE Full: $FULL WallCharger: $WALLCHARGER Battery Voltage: $VOLT NAC: $NAC Battery level: $RSOC %
done
One other thing: On your page you're talking about needing to copy over the wifi modules. Why not make it attempt to auto-copy those modules(and load them) on the first boot?
Seems like it'd make things simpler

isfr21 2011-08-12 12:35
Re: N900 rescue OS - testing release
 
Wow this looks perfect for exactly what I'm dealing with right now. I need to get my broken screen n900 into mass storage mode. However, your solution seems a complicated. Any chance someone can guide me through the steps needed to get my phone into mass storage mode using your rescue OS? :)

joerg_rw 2011-08-17 15:47
Re: N900 rescue OS - testing release
 
Quote:
Originally Posted by isfr21 (Post 1068437)
... I need to get my broken screen n900 into mass storage mode....
you tried hooking it up to a TV via AV?

/j

demolition 2011-08-17 16:32
Re: N900 rescue OS - testing release
 
Just checking - is this aiming at being analogous to "Safe Mode" so the system starts and runs but can't access/assert a lot of user-settings? If so a really good idea and would probably stop reboot loops!


Quote:
Originally Posted by isfr21 (Post 1068437)
Wow this looks perfect for exactly what I'm dealing with right now. I need to get my broken screen n900 into mass storage mode. However, your solution seems a complicated. Any chance someone can guide me through the steps needed to get my phone into mass storage mode using your rescue OS? :)
Have you looked at ways you can transfer data via wifi? As you say, a backup OS might overkill!

Mentalist Traceur 2011-08-17 16:42
Re: N900 rescue OS - testing release
 
Keep it up and my little boot-shell /sbin/preinit script won't be necessary for much :)

ALTHOUGH, the one advantage a properly syntaxed /sbin/preinit or bootmenu.sh script has is that you don't have to have a flashing-capable utility to get things running.

So, like you said, they do different things. :) Which is great, because your rescue-OS image provides a final non-reflash-requiring fallback position, for when RobbieThe1st's backupmenu and/or my /sbin/preinit boot-shell and/or pali's recovery console bootmenu item, etc, aren't enough.

Honestly, I wish we could someday reverse engineer the flashing process and the boot process completely (the latter, really, is mostly 'open', if not open source, aside from nolo), because then an entirely optionally enable-able, or at-boot-activateable, recovery shell, could be developed, made stable, and then added in as a feature of the CSSU, whereupon at least those devices would have the built-in fallback position on-device, and ideally most of those people wouldn't touch the actual code, thus avoiding wrongly-syntaxed-code problems.

Of course, either way, there will always come a situation where on-device data is f'cked and we need to break out the on-other-device flasher utilities, and then it's stuff like this to the rescue.

joerg_rw 2011-08-18 08:06
Re: N900 rescue OS - testing release
 
right on, right on!
This is really cool, not like the mostly useless meego rescue-initrd "solution" that left user even without [0-9] on kbd of the "shell" and allowed users to earn a CS degree en passant while mastering the task to mount maemo's NAND ubifs /.

Wrap this into a nice generic linux script to run on x86 which will take care of all the wget and dd and flasher-3.5 --foo and whatnot, and this will definitely earn a ranking among top three most useful maemo packages ever. 'Integration' (as in interoperability) of backupmenu (possibly incl the mtd_debug based raw image handling I suggested, buzzword >loopmount<) and maybe even fiascogen would be the icing on top.


I already offered to NIN101 (on IRC) to help with charging, though robbiethe1st's stuff is based on shadowjk's charging script and thus directly from the creators of (jrbme) charging and vboost and confirmed to be ok.

Also please ping me if you look for help and/or proofreading of the x86-side shellscript

/j

NIN101 2011-08-18 19:53
Re: N900 rescue OS - testing release
 
Hi,

Quote:
I do hope it has nano? Because vi just wouldn't work without an Escape button.
nano is the standard editor.

Quote:
Any chance someone can guide me through the steps needed to get my phone into mass storage mode using your rescue OS?
Well, I am sorry, but this is not a final release, more for curious tinkerers at this stage.
----
Because we are only using the keyboard inside rescueOS and nothing else, it is probably a good idea to have localized translation tables. On the other hand, after some time you get used to the default keyboard map. Either way, I have already started a map for the german keyboard layout, it is however not completed. So if anyone wants to finish this, go ahead.

misterc 2011-08-19 23:52
Re: N900 rescue OS - testing release
 
very nice, indeed :)
+ keyboard features of the Maemo kbd (Ctrl + I = Tab aso.) :)
+ Sym = Esc :D (yes, vi works ¦-)
+ boots, of course :p
+ even boots from ext2 :eek:

wish list:
  • mc / midnight commander?
    it comes with a built in text editor & with a little key settings (Ctrl + I mapped to Tab in the settings) auto completion
    THE ncurses file manager...
    source available from https://www.midnight-commander.org/downloads
    Storage Usage shows it @ 3.8 MB in Fremantle
    there is a MeeGo package according to Community Repo (listed under the last Code box)
  • partimage
    very handy backup software; been using it for years on all my PCs (included in SystemRescueCd or compiled on a Linux / GNU box)
  • GNU GRUB
    i know, we have already more then enough (too many?) boot menus for the N900, thus maybe a chance to port THE boot menu? :o

AndyYan 2012-05-09 10:26
Re: N900 rescue OS - testing release
 
Working nice, boots up...
Wait, this thing can't access /home (of maemo rootfs)?! Then what kind of recovery job am I gonna do with this? AND mass storage drive appeared as "RAW" unidentified format in Windows... Then what use is this for...?

reinob 2012-05-09 11:41
Re: N900 rescue OS - testing release
 
@AndyYan,

Did you read the documentation at all?
http://206.253.166.96/N900/rescueOS/documentation.txt

Quote:
Mounting maemo root
-------------------
/rescueOS/mount-maemo-root.sh
This scripts mounts the maemo root to /mnt/maemo.

/rescueOS/umount-maemo-root.sh

unknown.obvious 2012-05-09 13:34
Re: N900 rescue OS - testing release
 
Nice. I can imagine a OS installer on top of that.

immi.shk 2012-05-09 13:42
Re: N900 rescue OS - testing release
 
wow .. the thread got bumped almost after a year..

Estel 2012-05-09 14:00
Re: N900 rescue OS - testing release
 
BTW, is it still developed?

NIN101, why You've left Your post?
NIN101, do You copy?

SW pun intended

AndyYan 2012-05-09 14:17
Re: N900 rescue OS - testing release
 
Quote:
Originally Posted by reinob (Post 1203961)
@AndyYan,

Did you read the documentation at all?
http://206.253.166.96/N900/rescueOS/documentation.txt
I already read. I executed the script. I mounted. I went to /mnt/maemo/home. I typed "ls". It's simply empty. And WTF is that?!

NIN101 2012-05-09 16:16
Re: N900 rescue OS - testing release
 
Sigh. People...
maemo's home is on EMMC, rootfs on NAND. Now, think why you can't access /home/ if you just mount the rootfs... yep, you didn't mount mmcblk0p2 (which is mmcblk1p2 in rescueOS).


Quote:
BTW, is it still developed?
Not entirely dead, but also not really alive atm. I am focusing on other things, not N900 related.

Quote:
NIN101, why You've left Your post?
NIN101, do You copy?
Please rephrase.

Quote:
AND mass storage drive appeared as "RAW" unidentified format in Windows..
Not sure why. I don't have windows, so I can't really look into that.

Estel 2012-05-09 23:24
Re: N900 rescue OS - testing release
 
Don't worry about second part of my post, it was Star Wars/you nick pun, as seen in original (imperial Officer to Harrison Ford aka Han Solo disguised as Stormtrooper):

TK-412, why you've left Your post?
TK-412, do You copy?

...and was widely used as SW pun many times in many cases/movies/books/whatever.

So, particularly, it was meaningless for meritocratic discussion ;)

AndyYan 2012-05-10 07:09
Re: N900 rescue OS - testing release
 
Quote:
Originally Posted by NIN101 (Post 1204159)
Sigh. People...
maemo's home is on EMMC, rootfs on NAND. Now, think why you can't access /home/ if you just mount the rootfs... yep, you didn't mount mmcblk0p2 (which is mmcblk1p2 in rescueOS).



Not entirely dead, but also not really alive atm. I am focusing on other things, not N900 related.



Please rephrase.


Not sure why. I don't have windows, so I can't really look into that.
Aye, I AM Linux n00b for sure. But surely I tried mounting mmcblk1p2/3 and some error occurred... I'll be reporting error line later

bvaibhav 2012-08-10 09:16
Re: N900 rescue OS - testing release
 
Hi,

Can someone tell me how to use rescue os to enable mass storage mode, as the screen of my N900 is dead so I'll be doing it blindly.

reinob 2012-08-10 09:59
Re: N900 rescue OS - testing release
 
@bvaibhav,

Code:
USB Mass-Storage mode
--------------------
/rescueOS/mass-storage-enable.sh
Makes /dev/mmcblk1p1 and /dev/mmcblk1p2 available for the mass-storage
mode. These are the EMMC home partition and MyDocs in maemo. 

/rescueOS/mass-storage-disable.sh: Deactivates mass-storage mode.
Is it so hard to read a text file?!

bvaibhav 2012-08-10 11:46
Re: N900 rescue OS - testing release
 
Quote:
Originally Posted by reinob (Post 1250026)
@bvaibhav,

[
Is it so hard to read a text file?!

It is not hard to read a text file but as I told earlier the display of my phone is dead so I wont even come to know what happens when rescue OS boots....... or even confirm whether rescue os is loaded.....

bvaibhav 2012-08-10 13:10
Re: N900 rescue OS - testing release
 
I did the below mentioned but nothing happened, correct me if I was wrong.

1. Flashed the rescue os
Code:
sudo flasher-3.5 -k 2.6.37 -n rescueOS-initrd-0.5.3.img -l -b"rootdelay root=/dev/ram0"
[sudo] password for user:
flasher v2.5.2 (Oct 21 2009)

Suitable USB device not found, waiting.
USB device found found at bus 001, device address 013.
Found device RX-51, hardware revision 2204
NOLO version 1.4.14
Version of 'sw-release': RX-51_2009SE_20.2010.36-2.004_PR_004
Sending kernel image (1901 kB)...
100% (1901 of 1901 kB, avg. 23476 kB/s)
Sending initfs image (12548 kB)...
100% (12548 of 12548 kB, avg. 24038 kB/s)
Using kernel command line: "rootdelay root=/dev/ram0"
2. No LED was glowing on the device
3. Keyed in the command
Code:
/rescueOS/mass-storage-enable.sh
4. Nothing happened so also tried
Code:
sh /rescueOS/mass-storage-enable.sh
5. Pressed and held power key for 10 secs
6. Repeated above mentioned steps

Still nothing happened......

NIN101 2012-08-10 16:30
Re: N900 rescue OS - testing release
 
Your attempt didn't work because the keys are slightly differently mapped in rescueOS than in maemo...

Use this
Code:
flasher-3.5 -k 2.6.37 -n rescueOS-initrd-0.5.3.img  -l -b"rootdelay root=/dev/ram0 autostart=/rescueOS/mass-storage-enable.sh"
Works and the EMMC is accessible on Linux without any problems for me.
Good luck.
If you can make sure the battery is charged to a reasonable level.

Quote:
No LED was glowing on the device
Normal.

Quote:
Aye, I AM Linux n00b for sure. But surely I tried mounting mmcblk1p2/3 and some error occurred... I'll be reporting error line later
To mount, always use mount -t [filesystem type, e. g. vfat] [...] . I guess that's the reason.

bvaibhav 2012-08-11 05:00
Re: N900 rescue OS - testing release
 
Well I tried the command that you told, still no luck.

Output:
Code:
flasher-3.5 -k 2.6.37 -n rescueOS-initrd-0.5.3.img -l -b"rootdelay root=/dev/ram0 autostart=/rescueOS/mass-storage-enable.sh"
flasher v2.5.2 (Oct 21 2009)

Suitable USB device not found, waiting.
USB device found found at bus 001, device address 012.
Found device RX-51, hardware revision 2204
NOLO version 1.4.14
Version of 'sw-release': RX-51_2009SE_20.2010.36-2.004_PR_004
Sending kernel image (1901 kB)...
100% (1901 of 1901 kB, avg. 23476 kB/s)
Sending initfs image (12548 kB)...
100% (12548 of 12548 kB, avg. 24130 kB/s)
Using kernel command line: "rootdelay root=/dev/ram0 autostart=/rescueOS/mass-storage-enable.sh"
Just confirm one thing, after flashing, do I have to unplug the USB cable or press power key to start rescueOS.

Also I have microsd card in my N900, so can log be generated of the above command or whatever happens after rescueos boots, in the microsd card so that the issue can be traced...

One more thing, Please confirm that enable-mass-storage.sh script mounts the emmc and sdcard on the N900 itself or on my Linux desktop, coz if the partitions gets mounted on the device itself how do i copy the contents from phone to PC.

*PS I am using ubuntu 12.04 desktop version

NIN101 2012-08-11 09:25
Re: N900 rescue OS - testing release
 
Tried this?
---
Because you read the documentation, you actually should know that such a thing as "flashing rescueOS" simply does not exist. It only gets loaded by using the flasher, and therefore you don't need to press any power button.

Run the given command, and don't unplug the USB cable (because you want to have a working mass-storage mode...)

Quote:
One more thing, Please confirm that enable-mass-storage.sh script mounts the emmc and sdcard on the N900 itself or on my Linux desktop, coz if the partitions gets mounted on the device itself how do i copy the contents from phone to PC.
mass-storage mode does not mount anything. If it would mount the EMMC on the N900, then it simply wouldn't be a mass-storage mode. It also doesn't mount it on your Linux PC. The only it does is exposing the MyDocs and maemo home parittion so the PC the N900 is connected to can access it. It is up to you(or the desktop environment / filemanager you are using...) to actually mount the partitions. It kinda seems you don't really know what mass-storage mode does in the first place...

Quote:
Also I have microsd card in my N900, so can log be generated of the above command or whatever happens after rescueos boots, in the microsd card so that the issue can be traced...
Unfortunately, this would require a modification of rescueOS.

bvaibhav 2012-08-11 10:18
Re: N900 rescue OS - testing release
 
Yes I tried TV out connection, getting blank screen with blue horizontal strip on the top.

I really don't know about mass-storage mode, only thing I knew was that the MyDocs partition gets unmounted and it automatically gets mounted as removable media on desktop pc.

So if rescue os simply exposes the partition for the PC to access it, how do I manually access it from PC coz its not happening automatically.

bvaibhav 2012-08-11 10:36
Re: N900 rescue OS - testing release
 
'sudo fdisk -l' on my PC does not show any partition other than my internal hard disk's and only "sda and sdb" is shown in /dev no "sdc or mmcbklp**"

bvaibhav 2012-08-11 12:11
Re: N900 rescue OS - testing release
 
dmesg output

Code:
[  258.696491] usb 1-3: new high-speed USB device number 4 using ehci_hcd
[  258.828836] usb 1-3: unable to get BOS descriptor
[  259.130255] usb 1-3: USB disconnect, device number 4
[  259.908025] usb 1-3: new high-speed USB device number 5 using ehci_hcd
[  260.239436] phonet: disagrees about version of symbol module_layout
[  261.114500] usb 1-3: USB disconnect, device number 5
[  275.116082] usb 1-3: new high-speed USB device number 6 using ehci_hcd
[  290.228036] usb 1-3: device descriptor read/64, error -110
[  305.444035] usb 1-3: device descriptor read/64, error -110
[  305.660033] usb 1-3: new high-speed USB device number 7 using ehci_hcd
[  320.772031] usb 1-3: device descriptor read/64, error -110
[  335.988035] usb 1-3: device descriptor read/64, error -110
[  336.204048] usb 1-3: new high-speed USB device number 8 using ehci_hcd
[  346.612033] usb 1-3: device not accepting address 8, error -110
[  346.724033] usb 1-3: new high-speed USB device number 9 using ehci_hcd
[  357.132027] usb 1-3: device not accepting address 9, error -110
[  357.132052] hub 1-0:1.0: unable to enumerate USB device on port 3
[  357.400025] usb 3-1: new full-speed USB device number 2 using uhci_hcd
[  372.568026] usb 3-1: device descriptor read/64, error -110
[  387.840045] usb 3-1: device descriptor read/64, error -110
[  388.056027] usb 3-1: new full-speed USB device number 3 using uhci_hcd
[  403.168036] usb 3-1: device descriptor read/64, error -110
[  418.384027] usb 3-1: device descriptor read/64, error -110
[  418.600055] usb 3-1: new full-speed USB device number 4 using uhci_hcd
[  429.008027] usb 3-1: device not accepting address 4, error -110
[  429.120046] usb 3-1: new full-speed USB device number 5 using uhci_hcd
[  439.528038] usb 3-1: device not accepting address 5, error -110
[  439.528062] hub 3-0:1.0: unable to enumerate USB device on port 1

misterc 2012-08-11 15:59
Re: N900 rescue OS - testing release
 
Quote:
Originally Posted by bvaibhav (Post 1250302)
[...]

Also I have microsd card in my N900[...]
instead of all the mounting stuff you don't seem to understand well, why don't you simply copy the stuff onto the microSD card?
it's one of the basic feature of rescue OS

bvaibhav 2012-08-13 02:59
Re: N900 rescue OS - testing release
 
Quote:
Originally Posted by misterc (Post 1250519)
instead of all the mounting stuff you don't seem to understand well, why don't you simply copy the stuff onto the microSD card?
it's one of the basic feature of rescue OS
Even that would do but question is how do i copy it??

* My N900 has dead screen and no TV out

Update: Found that usb-networking-enable.sh script works as I was able to ping the device at 192.168.2.15 with the PC ip being 192.168.2.14.

NIN101 2012-08-13 19:36
Re: N900 rescue OS - testing release
 
Quote:
Update: Found that usb-networking-enable.sh script works as I was able to ping the device at 192.168.2.15 with the PC ip being 192.168.2.14.
flasher-3.5 -k zImage -n rescueOS-initrd-0.5.3.img -l -b"rootdelay root=/dev/ram0 autostart=/rescueOS/usbnetworking-enable.sh"

Wait a few seconds
Press enter
type: telnetd
Press enter

You should now be able to telnet into rescueOS. The IP should be 192.168.2.15.

User: root, password: rootme.

bvaibhav 2012-08-14 03:49
Re: N900 rescue OS - testing release
 
Quote:
Originally Posted by NIN101 (Post 1251456)
flasher-3.5 -k zImage -n rescueOS-initrd-0.5.3.img -l -b"rootdelay root=/dev/ram0 autostart=/rescueOS/usbnetworking-enable.sh"

Wait a few seconds
Press enter
type: telnetd
Press enter

You should now be able to telnet into rescueOS. The IP should be 192.168.2.15.

User: root, password: rootme.
Thank you very much !!! It worked...

After telnet into the device ran the mass-storage-enable script and was able to access the data on PC.

labaxp 2012-09-05 15:13
Re: N900 rescue OS - testing release
 
Hi,
First of all i have windows xp.
1.I want to copy some files from my nokia n900 (MyDocs) to my micro sd card.
2. If possible, i also want to keep my contacts.
I tried some thing but i am a complete noob.
Can someone pls tell me the steps.?
I read the documentation.
Regards.
Plz help. I am desperate.


All times are GMT. The time now is 03:17.
Page 1 of 3 1 23
Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8