Will Nandroid revert radio, hboot & OS version? - Droid Incredible General

Hey everyone- I used the hboot push method to update my OS to the 8/26 leak which updated the radio, hboot & obviously updated the phone to Froyo. I did a nandroid backup of how the phone was before all of this. I did not realize that doing a push through hboot would wipe the phone. I would like to revert back to how my phone was and didn't know if running a Nandroid restore is safe with the radio and whatnot... Suggestions?

it will not:
*revert radio
*revert hboot
it will:
*revert OS version
(if im not mistaken)

Related

Reverting from Cyanogen to Stock ION

Hey everyone! Glad to join the community!
Anyways, I have a T-Mobile 32B Magic, with Cyanogen's Recovery 1.4 and CyanogenMod 4.2.12.2
I am debating going back to stock HTC ION Rom (I don't need any of the T-Mobile crap, MyFaves etc.)
I have a backup .img of the recovery that came loaded on the phone if that is needed.
Am I correct to assume that simply booting into recovery and flashing the "signed-google-ion-img" will revert me back to 1.6 stock? I know I'll lose root and everything.
I'm loving Cyanogen, but I'm curious as if there is a way back.
Thanks to anyone who can help me.
Check the link on my sign
OK, sounds easy enough, but can I skip the SPL and fastbooting part and use the hacked recovery I already have on my MT3G? Like just copy the zip to sd, do a wipe and flash?

Rooted with hboot 1.49 S-ON?

I had Leak 2.1v3 on my phone, and following the XDA thread, I've successfully rooted my Eris using the stock 8gb card. Twice. I re did the root thinking I corrupted the RUU file, or something else during the initial root. I have Amon recovery installed and accessible at will.
I have full access to my phone with adb shell with SU access, but I'm unable to boot into any custom rom. So far I've tried Evil Eris 3.0 and Aloysius. They install without errors, but on reboot the phone to access the rom, the phone will freeze or loop. I've tried waiting over 20 minutes with the HTC boot screen flashing about every 15 seconds after installing Aloysius.
I'm still showing hboot 1.49.0000 S-ON. Is this what is stopping me from booting a custom rom? Or am I missing something that will change the security status to off?
Suggestions? What am I missing?
Thanks
Ok, looks like I got somewhere, I managed to install the grdlock beta rom. Not sure why the other roms wouldn't install tho. They all came from the same source. hboot is still 1.49.0000 S-ON tho.
NAA_Silent said:
Ok, looks like I got somewhere, I managed to install the grdlock beta rom. Not sure why the other roms wouldn't install tho. They all came from the same source. hboot is still 1.49.0000 S-ON tho.
Click to expand...
Click to collapse
The new rooting method ("Incredible/Slide") does not currently replace the S-ON bootloader, so phones rooted this way will not have 1.49.2000 S-OFF on them.
As for your troubles, you need to Wipe /data (FR) in Amon_RA recovery before you install a new ROM. Amon_RA does not enforce wiping of the /system and /data partitions before a new rom is loaded from the SD card, so you probably ended up with a mixture of old ROM and new ROM in a couple of places. (The dev can pre-clean those partitions in the update-script, but I'm not sure if that happens for the ROMs you mentioned.)
Always a good idea to wipe before a new ROM install (not necessary for a Nandroid restore, though, because it does a wipe itself).
bftb0
I thought I'd wiped those caches within Amon recovery. Good to know that I'm not going insane with the 1.49 S-ON tho! I couldn't find anything anywhere to let me know the S-ON was normal. After I get everything up and running with the grdlock rom, I'll back it up and try one of the other roms, being darn sure to wipe everything Amons will let me wipe first. Thanks for the info!
It appears that the rom files that I was using were corrupt. Without the md5 info for those files I had no way of checking. I went to a different site and downloaded Aloysius 12, and it's up and running just fine now
Thanks for the nudges in the right direction!

[Q] how can i backup the stock recovery???

I have just rootet my magic, but i cant backup my recovery with recovery flasher 1.1.3 .
I think the last 1.5 rom for magic 32a is patched against flash recovery.
And the rom manager doesnt support a backup of the current recovery.
How can backup my stock recovery??
Magic 32a s-on h
1.76.0009 spl
6.35 radio
no one an idea?
i'll be sure, before i flash a custom recovery, i am able to go back.
so i need a orginal recovery.img
the best would be the own, but i cant backup the recovery.
Its not that we don't know how it's just thar there is no reason to.. if you can get into the bootloader you can restore the stock rom via SAPPIMG.zip or SAPPIMG.nbh .. this includes the stock recovery.
Having a stock recovery on a custom rom is not very useful.
Just note while you have the 6.x radio you want a hero custom recovery
(Advance users unzip the sappimg and grab recovery.img ..)
thanks for the information about the SAPPIMG.zip or SAPPIMG.nbh, it was very usefull.
i'll try the clockwork recovery with the rommanager out of market.
i think this is possible, or isnt it?
with the 6.35 radio?
I've heard about lots of bricked phones thanks to clockwork/rom manager. Use AmonRA's recovery.
keinengel said:
I've heard about lots of bricked phones thanks to clockwork/rom manager. Use AmonRA's recovery.
Click to expand...
Click to collapse
In theory it will be fine if you use the hero recovery not the ion/magic one..
But given the confusion/problems/near bricks of others.. I agree getting the hero RA recovery and booting it manually with home+power is the safest way... that way if you goof you just boot android normally and try the flash again.
ok i will flash amonRA recovery.
like in this thread:
http://forum.xda-developers.com/showthread.php?t=756918
edt:
nice, it worked. thank guys for protect a maybe brick (with this sh.. rommanager clockwork)
edt2:
now i am using this rom:
http://forum.xda-developers.com/showthread.php?p=8142644#post8142644
best i have ever seen

[Q] How to update the radio while S-ON

so here I am now with my new Legend which unfortunately is already hboot 1.0
so I downgraded to version 1.31 and now can install e.g. CM7 via fake-flash CWM
but one problem remains
the 1.31 downgrade also downgraded the RADIO firmware image and now I need a way to update it again to get GPS working under CM7
flashing it via CWM fails (although CWM says everything has gone well)
and fastboot flash radio radio.img fails also since I am S-ON and have no means to downgrade hboot (the only way so far seems to be HTC-Clip S-OFF the rom and then downgrade hboot and then alpharoot, not confirmed as far as I know)
anyone got any Idea?
Are you wiping "cache"?
Recovery > Mounts and storage > Format cache
Radio flashes are done via CWM 2.X. Downlad a proper radio zip from the development forum, flash it like normal ROM. The process will continue after reboot.
Sent from my HTC Legend using XDA Premium App
I just tried it 4 times and the 4th time it worked -.-
damn Legen, you scare me
thx for all the replies

Stuck after migrating to Desire z HBOOT?

Hi Everyone,
Currently I am running GV 1.5 on my G2 and wanted to migrate to the Desire Z HBOOT using zedomax's video as Virtuous ROM's migration process basically was too complicated. Well I went through the exact steps as zedomax showed. After updating the HBOOT and removing the PC10IMG.zip file I rebooted and bootloader shows: Vision PVT ENG S-OFF, HBOOT- 0.84.2000, RADIO- 26.02.01.15_M2. Now I went into recovery and restored my recent backup. Then it just sits at the HTC screen and has sat there for over 15mins and just doesn't boot! I pulled the batt then I just did a full wipe and tried the restore several times and It still just sits at the HTC splash screen. I have adb drivers installed properly so if anyone has some things to try using adb to maybe deal with these issues hopefully I can get this resolved. Thanks!
Clockwork Mod update problem...
I realized that when I was using my latest restore save it wasn't passing the checking md5 sums. So before when I flashed CWmod it was 5.x after that I did a backup. When I updated to Desire Z HBOOT and got to recovery it said recover 3.4.x so I'm guessing thats why It wasn't restoring my backup becuase it was created with 5.x, so w/e doesn't matter now.

Categories

Resources