Menu

Main Menu
Talk Get Daily Search

Member's Online

    User Name
    Password

    Is it possible to access files on a not booting device? UPDATE: Device won't boot anymore!

    Reply
    Page 2 of 4 | Prev |   1   2   3     4   | Next
    efekt | # 11 | 2011-04-07, 11:50 | Report

    I'd REALLY like to try and flash my eMMC without doing it in the 5 dots screen (I mean those 5 horizontal dots which usually show when Maemo is booting up, right after the "Nokia" logo screen, yes?), but the problem is that its just impossible now.
    You see, this is what happens if I run the flasher while the device is connected:
    1. I execute:
    Code:
    flasher-3.5.exe -F RX-51_2009SE_10.2010.13-2.VANILLA_PR_EMMC_MR0_ARM.bin -f
    2. CMD shows:
    Code:
    flasher v2.5.2 (Sep 24 2009)
    
    Image 'mmc', size 255947 kB
            Version RX-51_2009SE_10.2010.13-2.VANILLA
    USB device found found at bus bus-0, device address \\.\libusb0-0001--0x0421-0x0105.
    Found device RX-51, hardware revision 2101
    NOLO version 1.4.14
    Version of 'sw-release': RX-51_2009SE_20.2010.36-2_PR_MR0
    Booting device into flash mode.
    The immediately the device loses the connection, and the CMD shows:

    Code:
    Suitable USB device not found, waiting.
    If I wait for a minute or so:
    1. The device suddenly starts up again - only showing the 5 running dots.
    2. The device reconnects to the PC.
    3. The running dots freezes.
    4. The flasher is now able to recognize the device, if flasher is started. flashing succeeded:

    Code:
    flasher-3.5.exe -F RX-51_2009SE_10.2010.13-2.
    VANILLA_PR_EMMC_MR0_ARM.bin -f
    flasher v2.5.2 (Sep 24 2009)
    
    Image 'mmc', size 255947 kB
            Version RX-51_2009SE_10.2010.13-2.VANILLA
    Suitable USB device not found, waiting.
    USB device found found at bus bus-0, device address \\.\libusb0-0001--0x0421-0x01c8.
    Raw data transfer EP found at EP2.
    Using flashing protocol Mk II.
    Image(s) flashed successfully in 26.668 s (9597 kB/s)!
    Now, flashing the firmware works and completes just fine and I don't have to do any tricks to make it work (holding 'u', connecting the device to the USB - I have to hold 'u' btw) but as I said - in the end the device would still not start.
    If it matters for any reason - I'm using Windows 7 64bit and flashing through the Windows XP mode. It used to work just fine (though now it isn't )

    Edit | Forward | Quote | Quick Reply | Thanks

    Last edited by efekt; 2011-04-07 at 11:52.

     
    m4r0v3r | # 12 | 2011-04-07, 12:17 | Report

    am blaming windows 7 for this. get a linux live cd and use that instead

    Edit | Forward | Quote | Quick Reply | Thanks

     
    efekt | # 13 | 2011-04-07, 15:36 | Report

    Originally Posted by m4r0v3r View Post
    am blaming windows 7 for this. get a linux live cd and use that instead
    Then don't
    I just tried reflashing via Kubuntu - still, got the exact same result.

    I even tried disabling watchdog, but it didn't help either (yea, I know, it was a long shot )...

    Edit | Forward | Quote | Quick Reply | Thanks

     
    pursueky | # 14 | 2011-04-07, 16:23 | Report

    Have you ever dropped it off or sth like that ?
    I broke my N900 too and it just appeared like what you described here. So if you want to have a try . That's here: Take your machine apart completely and put a piece of soft paper on the HDD. And also some helps in this url: talk.maemo.org/showthread.php?t=71089

    Edit | Forward | Quote | Quick Reply | Thanks

     
    efekt | # 15 | 2011-04-07, 16:46 | Report

    Didn't drop it, well not as far as I remember... This problem just appeared by itself... A day before, the device was rebooted successfully when I had to replace its battery...

    Originally Posted by pursueky View Post
    Take your machine apart completely and put a piece of soft paper on the HDD.
    What? why?

    Edit | Forward | Quote | Quick Reply | Thanks

     
    pursueky | # 16 | 2011-04-07, 17:15 | Report

    Originally Posted by efekt View Post
    Didn't drop it, well not as far as I remember... This problem just appeared by itself... A day before, the device was rebooted successfully when I had to replace its battery...


    What? why?
    in my issue, the HDD loose.....

    Edit | Forward | Quote | Quick Reply | Thanks

     
    efekt | # 17 | 2011-04-07, 18:57 | Report

    Nope, nothing was loose in my device. I opened it and everything was intact...

    Edit | Forward | Quote | Quick Reply | Thanks

     
    MohammadAG | # 18 | 2011-04-07, 21:09 | Report

    Flash the COMBINED image without -R, then flash the eMMC image.

    Edit | Forward | Quote | Quick Reply | Thanks

     
    mrsellout | # 19 | 2011-04-07, 21:20 | Report

    efekt I think you've missed a bit on the wiki about flashing the emmc. You need to remove the battery once the emmc has been flashed, presumably because the n900 is on at some level.

    Originally Posted by
    Flashing the eMMC in the N900
    Image:Ambox_notice.png
    When flashing the eMMC content, the safe way is flash the eMMC/VANILLA image first, then remove battery for a moment, and then flash the FIASCO/Rootfs image. Do not boot up the device between the two i.e do NOT use the -R parameter at the end! Rationale: on accidental booting in between the 2 flash processes, the sequence formerly suggested (rootfs first) will result in a broken system. The sequence "eMMC first, then rootfs" is checked back with Nokia affiliates and is proven to work. The former advice on tablets-dev.nokia.com was not based on any facts for the recent eMMC VANILLA image. It's fixed now and in line with this wiki

    Edit | Forward | Quote | Quick Reply | Thanks

     
    mrsellout | # 20 | 2011-04-07, 21:42 | Report

    Apologies, I've misread what you've said, you've already done this.

    Edit | Forward | Quote | Quick Reply | Thanks

     
    Page 2 of 4 | Prev |   1   2   3     4   | Next
vBulletin® Version 3.8.8
Normal Logout