Root 2.1 to 1.5 reversion problem, please help?


Last Updated:

  1. boostlover

    boostlover Member This Topic's Starter

    Joined:
    May 6, 2010
    Messages:
    5
    Likes Received:
    0
    I need some help, please!

    I had rooted 2.1, dowloaded the unzipme.zip and installed 1.5 again, but I can't get fastboot to accept the recovery image or the hboot image. Whenever I try it, this is what I get:

    c:\androidsdk\tools>fastboot flash recovery recovery.img
    sending 'recovery' (2004 KB)... FAILED (remote: not allow)

    Can someone please help me with this issue?
     

    Advertisement
  2. T2noob

    T2noob Well-Known Member

    Joined:
    Jan 16, 2010
    Messages:
    471
    Likes Received:
    98
    its saying you don't have permission for that so are you sure you were rooted?
     
  3. erisuser1

    erisuser1 Well-Known Member

    Joined:
    Nov 11, 2009
    Messages:
    1,644
    Likes Received:
    759
    Either that or he succeeded. (Although I'm not sure what method uses an "unzipme.zip" file).

    OP: If your bootloader screen (hboot/fastboot) displays "S-ON" at the top of the screen, that means either you previously did not have root, or you succeeded in rolling back.

    Post the details of what you see at the top of the HBOOT/FASTBOOT screen on the phone (and the software version number "Settings...About phone... etc") and maybe someone can give you some more useful help.

    eu1
     
  4. boostlover

    boostlover Member This Topic's Starter

    Joined:
    May 6, 2010
    Messages:
    5
    Likes Received:
    0
    I'm positive my phone was rooted, I used NAND backup numerous times before flashing and running ROMs on my phone.

    I downloaded "unzipme.zip" as specified by Acidbath in the forum, it contained the following files:

    downgrade.zip
    hboot.nb0
    recovery.img

    I succeded in reinstalling 1.5 on my phone, but can't get away from Amon's recovery image, hence my problem. I put the recovery and hboot image in the tools directory of my sdk, but to no avail. I'm trying to get my phone back to 100% stock.

    This is what I see upon loading fastboot on the phone:
    DESIREC XC SHIP S-ON
    HBOOT-1.47.0000
    MICROP-0111
    TOUCH PANEL-SYN0104
    RADIO-2.32.40.BLAH BLAH
    Oct 23 2009, 17:02:23

    I did everything as Acidbath specified, and to reiterate, I'm back to Android Firmware version 1.5 (Software version 1.17.605.1), but still have Amon's recovery image and the wrong hboot.
     
  5. erisuser1

    erisuser1 Well-Known Member

    Joined:
    Nov 11, 2009
    Messages:
    1,644
    Likes Received:
    759
    OK, gotcha.

    The same bootloader was used for both the 1.16.605.1 and 1.17.605.1 RUUs. I don't have the version info in front of me, but it looks like (judging from the Oct 23, 09 date) that you think that you have the first-ship bootloader instead of the bootloader from the MR1 or MR2 (1.5) updates?

    You won't be able to use "fastboot" to write anything to any partitions with an S-ON bootloader. If you desperately need to get rid of the Amon_RA recovery, you will need to re-root the phone. The only bootloader which will allow you to have your way with the phone is the hboot_*.nb0 file in the "root" PB00IMG.ZIP.

    There was a battery-pull trick where you could replace only the bootloader - do a search on XDA. This might save you some work - leave 1.5 in place (/system), start the reflashing process with the root PB00IMG.ZIP, and pull the battery right at the moment when it reboots (the 2nd time, I think - you'll see it very briefly mention, like less than one second, that it is flashing HBOOT, and then the screen will blank. You have several seconds in which you can pull the battery) I've done it a couple of times, including following it up with manually reflashing recovery.img and then (last) hboot_[version].nb0 with fastboot.

    Also - something else just occured to me - if you really have the first-ship bootloader on your phone now, you should be able to use the MR1 or MR2 updates to get back to a complete stock phone - have you tried that?

    eu1
     
  6. erisuser1

    erisuser1 Well-Known Member

    Joined:
    Nov 11, 2009
    Messages:
    1,644
    Likes Received:
    759
    PS. I just found some photos I took after a MR1 update - the bootloader version numbers on my screen are identical to what you reported above. Why do you think the bootloader version is wrong?

    eu1
     
  7. n1ghtwish

    n1ghtwish Well-Known Member

    Joined:
    Feb 17, 2010
    Messages:
    113
    Likes Received:
    4
    does the downgrade use the recovery?? if not, wouldn't he be able to upgrade to 2.1 root again, delete the recovery through ADB, then follow the downgrade method again???

    just a thought.. never read anything about the downgrade so I have no idea how it works
     
  8. boostlover

    boostlover Member This Topic's Starter

    Joined:
    May 6, 2010
    Messages:
    5
    Likes Received:
    0
    Well, I just wasn't sure if the hboot version was correct or not, and figured it wasn't since there was a copy included with the downgrade zip. I've got the MR2 RUU and tried running it, but it won't run at all, just keeps waiting on bootloader and then saying that it can't flash the ROM.

    I'm not really desperate to get rid of the recovery image, I would just like everything to be kosher with the phone once the OTA 2.1 update comes around so it can be legitimate.
     
  9. erisuser1

    erisuser1 Well-Known Member

    Joined:
    Nov 11, 2009
    Messages:
    1,644
    Likes Received:
    759
    There's lots of ways to skin this cat, but all methods either need to use Amon_RA's recovery, OR have the S-OFF (aka "root") bootloader on the phone. So, yes - if he was worried about being "pristine 1.5 (1.17.605.1)", then he would need to re-root. If I was in his shoes and wanted to do that, I would:

    1) Use "Toastcfh"'s battery pull trick with the root-ROM to only install the S-OFF bootloader. This would leave his stock 1.5 intact, but have both the non-factory bootloader and recovery installed. Then,

    2) Manually use fastboot mode to flash the recovery partition back to the 1.17.605.1 "factory" state, and finally

    3) Manually use fastboot mode to flash the HBOOT image (or bootloader, or SPL, or whatever you want to call it) back to the "factory" 1.17.605.1 state. This should produce a "near factory" phone. (I have some suspicions that the NVRAM - not the flash - gets modified during the MRx/leak installs, and none of the recovery methods deal with this at all)

    If I were a betting man, I would bet that the OTA install process does not inspect the contents of the recovery partition - it simply over-writes it. That's my guess, but I don't know that for a fact.

    eu1

    PS. I would also bet that within a few days after the OTA, there will be a root ROM sort of like what jcase produced when leak-v3 came out: mostly identical to the factory code, but with root thrown in (and preserving the S-OFF bootloader, too). Your call - but if you've already been root, why give it up? You'll be very likely to get all of the new software that's in the OTA - but with root, too.

    Just saying - but it's your call.
     
  10. pkopalek

    pkopalek Well-Known Member

    Joined:
    Dec 19, 2009
    Messages:
    837
    Likes Received:
    117
    Ok what it looks like here is that you sightly DIDN'T follow the directions, exactly.

    Clearly, you flashed the hboot.nb0 already, BEFORE flashing the new recovery.img.

    The instructions state to flash the recovery.img first, and also to do them both in the same fasboot session.

    That's OK though! Nothing to worry about!

    By the time you mess around with all of those other things that 'should' work, here's what WILL work, and exactly what I would do:

    Re-root your phone, with the PB00IMG.zip and soon.
    Re-do the process as much as necessary (recovery may already be in there).

    If you use the Eris Master Application, it'll do everything for you. Neither here nor there.

    THEN, once you've got your root and recovery properly put back exactly how it was BEFORE you started to downgrade, start the downgrade process again.

    Wipe data and cache
    Flash downgrade.zip
    Reboot a couple of times
    Shut down the phone
    Turn it on with CALL + END

    do the fastboot commands, but do THE RECOVERY one FIRST!
    Don't battery pull until AFTER you flash the recovery.img and hboot.nb0 (in that order!), and then wait a minute (I've been waiting a full minute, just in case, before doing the battery pull, but that's your call).

    Good luck, hombre.
     
    bberryhill0 likes this.
  11. Mrkarias

    Mrkarias Member

    Joined:
    May 21, 2010
    Messages:
    20
    Likes Received:
    0
    Ok Android Forums, Ive used all my info for Root from this website and this website only. all the instructions have been extremely precise. :)

    So I rooted my phone, and now im trying to unroot to get the OTA 2.1.
    I followed the Unzipme instructions and I went through the downgrade and the downgrade went very smoothly. But as soon as I tried to Flash the Recovery Image and the Hboot, I keep getting "error: cannot load recovery.img"

    What am i not doing wrong? I have rooted the phone all over again and downgraded again and ONLY tried the FASTBOOT FLASH RECOVERY RECOVERY.img and it still kept getting me the ""error: cannot load recovery.img" after that i didnt try the Hboot

    I turned the phone back on and it tried to do the OTA update and it seemed to be working and it even downloaded successfully as soon as it tried to reboot and install it gives me this error
    E: No signature required (690 Files)
    E: Verification failed

    I am desperate for some help...

    Thank you all in advance
     

Share This Page

Loading...