My evo got pretty ****ed over the past day, originally I rooted it by installing the hboot drivers then using unrevoked,I assumed everything would be done from there, I never got to flash Amon ra or any custom roms so I wanted to try it out, every guide I found involved using adb shell and a Tom of other steps I never used while originally rooting.
I got so fed up with all the error messages that I decided to start from the absolute beginning and root again and then try unlocking nand, one method involved me putting all these files on the sdcard and using adb a lot, I followed all if these steps exactly and DEFINITELY DID A NAND BACKUP but then after rebooting in one step my phone went back to eclair 2.1 and all my info was deleted and now its as if I bought it today, its not even rooted anymore so all the apps I backed up with titanium I can't even access anymore since it requires root
One step told me to do the nand restore and when I went the folder was empty, I would kill to have my old evo back or at least all my apps, any and all help would be HIGHLY appreciated
Sent from my PC36100 using XDA App
If youre back on 2.1, just root it, put whatever recovery you used to make your nandroid on there and then restore your nandroid.
Sent from my PC36100 using XDA App
I assumed onceI was on 2.1 I would be rooted again, I tried unrevoked once it was on 2.1 but it just stayed saying "running root" and never changed, and my nandroid restore didn't show up before so why would it now
Sent from my PC36100 using XDA App
The root method you used was older, and was the way to go before Froyo was officially rooted. It involved downgrading (which you did) and then rooting 2.1 and then flashing a froyo ROM. It sounds like you made it to the downgrade part and then you stopped for whatever reason. You aren't in bad shape, you just need to get that 2.1 rooted and you're good to go.
As far as the nandroid is concerned, if you made it, then it should be there. You said you never got to flash a custom recovery but you must've if you were able to do a nandroid. Now if you made your nandroid with clockwork you won't be able to restore it with Amon and vice versa, which is where I think the confusion lies. Do you remember what recovery you made the nandroid with?
Your only real option at this point is to root your 2.1 and restore your nandroid with the correct recovery. Check your SD card, if there is a folder called Nandroid then it was made with Amon, and I'm pretty sure clockwork puts it's nandroid into a folder called Clockwork.
As far as why the root wasn't finishing, I'm not really sure because it's been a while since I used that method. It could be a driver issue. Have you installed the proper drivers?
_MetalHead_ said:
The root method you used was older, and was the way to go before Froyo was officially rooted. It involved downgrading (which you did) and then rooting 2.1 and then flashing a froyo ROM. It sounds like you made it to the downgrade part and then you stopped for whatever reason. You aren't in bad shape, you just need to get that 2.1 rooted and you're good to go.
As far as the nandroid is concerned, if you made it, then it should be there. You said you never got to flash a custom recovery but you must've if you were able to do a nandroid. Now if you made your nandroid with clockwork you won't be able to restore it with Amon and vice versa, which is where I think the confusion lies. Do you remember what recovery you made the nandroid with?
Your only real option at this point is to root your 2.1 and restore your nandroid with the correct recovery. Check your SD card, if there is a folder called Nandroid then it was made with Amon, and I'm pretty sure clockwork puts it's nandroid into a folder called Clockwork.
As far as why the root wasn't finishing, I'm not really sure because it's been a while since I used that method. It could be a driver issue. Have you installed the proper drivers?
Click to expand...
Click to collapse
yae the recovery is where the whole issue began, i assumed i was good so i tried flashing amon RA with the terminal emulator and whenever i typed 'su' it always said permission denied, i was rooted for sure so some people said i had to probably unlock NAND and more errors came from there so i tried that other rooting method so i definitely flashed with clockwork and i remember seeing the build name on the bottom as well which makes me pretty happy as well since i found it in the directory which you said under my sdcard with the date name and whatnot so major kudos for that
i installed the hboot drivers before so i assumed i didnt need to do it again but when unrevoked kept staying at "running root" i tried installing again, and on this video online from djr3z he said under 'My Devices' that Android 1.0 would show up where I could click to install it but it never showed up so I've been stuck since that point, are there any other alternative root methods you recommend/should i try updating the drivers? or perhaps i can delete the driver and reinstall?
Check your hboot, are you S-ON or S-OFF? Also, what hboot version are you?
im definitely S-OFF, saw it all the time in the bootloader screen, how do i check the hboot version exactly?
R1pTheJacka said:
im definitely S-OFF, saw it all the time in the bootloader screen, how do i check the hboot version exactly?
Click to expand...
Click to collapse
you load it up with volume down and power button, same way you go as if your going to boot into recovery
ok and my hboot version is .76.2000
can anyone confirm if .76.2000 is the latest hboot driver? everytime i connect my phone and check device manager it shows android bootloader interface which, from what i heard, is what im supposed to see
everytime i run unrevoked it stays at "running root..." and doesnt change from there
The latest hboot is 2.02 I believe but you don't want that one, I hear it's a pain to root. Yours is the engineering hboot which must have gotten put on there from whatever rooting method you were using. It's fine to leave that one on there, it will allow you to flash CM6 if you ever decide to. What happens when you select recovery from the hboot menu?
Have you tried downloading ROM manager from the market and using it to flash clockwork? I would give that a whirl.
when i select recovery from bootloader it gives me the black screen with the phone and red triangle, i started button mashing and it seemed like a recovery image but it said 'Android system recovery <2e>' with a few commands like wipe/reboot etc.
i was trying the clockwork before, i installed rom manager, then tried "Flash ClockworkMod Recovery" but it kept giving me error messages about attempting to run privilleged commands, assuming that means im not rooted again
i dont even think i have the clockwork recovery image on my sd card, it does however show my amon RA one, but there's no point in flashing that if the clockwork has my nandroid backup right? and couldn't i just put the clockwork recovery image on my sdcard from online somewhere?
Try this- Download THIS FILE, put it on the root of your SD card, and boot into hboot. It will automatically find it, load it and ask you if you want to run it. Choose yes and let it go. It *should* install clockwork recovery on your phone. If it doesn't work, no harm no foul and we can try something else. If it does work, you should be able to restore that nandroid that you made. It will only work if you are S-OFF, which you say you are so it's worth a shot.
okay and if it works, before i do the restore should i wipe everything?
It won't hurt but when doing a nandroid restore wiping is not necessary.
so close...your method worked, but i couldnt restore it gave me an error messgae..
ClockworkMod Recovery v2.5.0.1
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Error whille flashing boot image!
takes me back to the main menu of the recovery =\
do you think it has to do with me still being on 2.1 rather than 2.2?
So you now have clockwork on there? That's a step in the right direction! Try restoring your nandroid once more and if that doesn't work, you can flash a ROM and then restore your titanium backups.
It shouldn't matter what ROM you're on when restoring a nandroid. Do you remember what hboot version you were on when you made the nandroid? If I remember correctly that could cause an issue but I'm not entirely sure about that.
hmm i cant even get out of the bootloader screen now though..even when i reboot it takes me straight to bootloader
and also if i flash a rom will have to be designed for 2.1 since im still technically on that?
no idea about the hboot version =\ just assumed it was upgraded to the most advanced version when i updated the driver
but i cant even put any ROMs on my sdcard now because i cant even leave the bootloader screen?
No, flashing a 2.2 ROM will upgrade you from 2.1, it should work fine. You must have made your nandroid on a different hboot version then the one you have now.
What I would do in this situation is run the 3.29 RUU found HERE which will bring you back to full stock, and then you can run Unrevoked and reroot it. The whole process should only take you a half hour or so. I don't know if you will be able to restore your nandroid because of the hboot discrepancy, but at the very least you will be able to restore your titanium backups.
Sorry if this sounds stupid, but I'm a little confused. I'm aware of all the S-OFF, permarooting etc and the necessary ways to get them. Before I go through with these guides however, I'd like a backup of some sort.
I know ClockworkMod is a custom recovery and you can perform nandroid backups with it, but I also understand there is a default recovery mode you can access from the bootloader that can also do that. Obviously I'd like to make a full nandroid backup before I make any permanent changes.
However, when I select 'Recovery' from the bootloader, my phone goes to a black screen with a generic phone icon and a red ! in a triangle. Why could this be? It is a standard UK T-Mobile Desire Z with no modifications aside from a Gfree S-OFF that was reversed again by copying the backup partition back.
That is the splashscreen of the stock recovery. Press Vol-Up and Power to get past that screen - but you won't be able to do a nandroid unless you have a custom recovery installed - sorry!
Thanks very much for that info. So there's no way of making a nandroid backup before I do things like permarooting? Will the unroot option in Visionary reverse that?
Presumably there's a way of reverting from ClockworkMod to the stock recovery?
the only time you will be able to make a backup is when you install clockwork. No clockwork no backup.
Use titanium backup for the settings and apps and then install clockwork and then do nandroid. if that doesnt work you have your TB to restore.
You can also try to "adb pull /system" and pull everything to your desktop.,... but pushging it back will require skillz.
If you want to revert from clockwork to stock recovery you need to flash stock recovery but do not do it with an incompatible rom.
Thank you, oh wise one!
Don't worry about the fact you can't do a nandroid backup before you root the phone, because it's easy enough to un-root.
You can do the nandroid backup as soon as you've got root/S-OFF, installed ROM Manager and flashed Clockwork recovery. It's very important to do this before you flash any sort of custom ROM. I am amazed by the number of people who seem to flash a custom ROM straight away with no backup whatsoever !
1.) From what I've read, CWM 2.x doesnt handle GB's ext4 partition, and you need 3.x for that. What will I lose/gain if I update to 3.x?
2.) If I do decide to use CWM 3.x, will I still be able to go back to my Froyo's file system?
3.) How do I get back to the nandroid backup of my Froyo 2.2.1? Can I use CWM 3.x as well? Do I just restore the backup I've made? What about the filesystem?
4.) Assuming I can just go back from GB to my Froyo by restoring through the nandroid backup I made, will the custom kernel I've flashed with it also come back with the restore?
I have flashed back and forth between Froyo and GB ROMs using CWM 3.x. If it doesnt work, can't you always reflash CWM 2.x ?
Anyway, you ask too many questions .. Like the rest of us, you should throw caution to the wind and try it out yourself.
i guess im just one of those people.
anyway, thanks for the response. cleared a few things for me.
I don't even flash recovery. That way I can use whatever recovery I want and keep stock recovery so I don't get cwm popping up when I charge and the phone is off.
./fastboot boot recover.img
Someone swyped my idea.
Hey Guys, I have searched for this but I cant find an answer so I just wondered...
Say for instance I made a Nandroid backup in Clockwork Recovery 5.x and then my friend who has Clockwork Recovery 5.x and the exact same device HTC Wildfire (Buzz) used my Nandroid backup in the same directory but on his SD card then would Clockwork Recovery be able to recover his device from my Backup?
Thanks in advance.
Yes it will work. (Barring issues like MD5 mismatches etc. You should be preferably be having the same CWM version, and, if possible, he should use your SDCard to restore, since, there are cases when you transfer Nandroids from once place to another, they don't play nice)
Anyway, another alternative is to simply use fastboot. Assuming your friend has S-OFF'ed his device via Revolutionary, he will simply need all the IMG files from your backup, and, that should definitely work irrespective of CWM versions, and other limitations.
The other day I was restoring a backup in TWRP 2.6.0 on my Sprint Galaxy S3. The ROM I was on was AOSP based and the one I was restoring was AOSP based. During the restore, the phone rebooted during the data restore and then started a boot loop on the device, where it appeared I was starting TWRP again, only to have the device reboot at the TWRP splash screen.
I eventually finagled the device into getting TWRP to load by starting DL mode and then booting into recovery where I proceeded to do a full wipe and install a ROM from fresh. Anyone know why this would occur? It was very scary to think I was about to brick my device over something as simple as restoring what was a successful backup. I have not tried to restore any backups since out of fear of this issue occurring again. I also read on the TWRP page about a defect of reboot during restores if not enough data is available, but I have plenty of storage room available on my internal (26.26) and external (29.93) SD cards.
Not much help here, and at the risk of sounding like a Negative Nelly, I gave up on image-based backups several devices ago. The only device that I could get reliable nandroids was my HTC EVO 4G running AmonRA recovery. Since then, I've owned/rooted 4 or 5 other Android devices, and every single one of them have been completely unreliable with nandroid restores to the point that I just gave up, use Titanium Backup, and then just flash the ROM again. That's been with CWM and TWRP, all versions (and I've probably tried them all) on all of my devices.
I would love it if someone could enlighten the both of us on how to be successful with nandroid backups/restores. Again, sorry I'm not of much help, but consider me a confirmation of what you're encountering (a "yeah, what he said").
dante32278 said:
The other day I was restoring a backup in TWRP 2.6.0 on my Sprint Galaxy S3. The ROM I was on was AOSP based and the one I was restoring was AOSP based. During the restore, the phone rebooted during the data restore and then started a boot loop on the device, where it appeared I was starting TWRP again, only to have the device reboot at the TWRP splash screen.
I eventually finagled the device into getting TWRP to load by starting DL mode and then booting into recovery where I proceeded to do a full wipe and install a ROM from fresh. Anyone know why this would occur? It was very scary to think I was about to brick my device over something as simple as restoring what was a successful backup. I have not tried to restore any backups since out of fear of this issue occurring again. I also read on the TWRP page about a defect of reboot during restores if not enough data is available, but I have plenty of storage room available on my internal (26.26) and external (29.93) SD cards.
Click to expand...
Click to collapse
What I have found out the hard way is that every device is different. Some prefer CWM Recovery, some TWRP Recovery. If TWRP is not working for you, try CWM. A stable Custom Recovery is a must have.
TEAM MiK
MikROMs Since 3/13/11