Related
hi all,
so I saw that unrevoked3 is out and read that it makes installing other ROM's really easy.
so I installed the windows hboot driver and unrevoked3 automatically installed ClockworkMod 2.5.0.1
i didn't really know what todo next so I did a nandroid backup... that took a while, so I assumed it had backedup everything (old rom + apps + user settings etc)
anyways then I rebooted back into my stock ROM and copied opendesire 2.2 onto the SD.
then I rebooted into ClockworkMod and installed the opendesire2.2.zip
then I tried booting normally and it sort of sat on the initial screen for a long while, so I rebooted back into CWM and did a wipe/factory reset.
then rebooted again.
this time it loaded up opendesire fine.
after playing around for a bit I wanted to go back to my old rom.
so i rebooted into CWM and just did a nandroid restore...
now when I boot into my old ROM I am missing all my apps.
the home screens are blank
there is a new "super user privs" app
various other things are missing.
so what did I do wrong?
doesn't nandroid backup everything?
Cheers
D.
I forgot to say, I havn't rooted the phone - I dont know if that makes a difference... I actually thought the unrevoked thing was going todo more that just install a different debug boot loader...
Hi, got my first andriod, the desire, only 6 weeks ago so still a n00b myself! Hopefully someone can answer better and correct my mistakes but here goes:
With Linux you have to be a root (or superuser) to access, modify, execute, etc any and all files. Our Desires, with stock ROMS, do not allow us to do these things - hence we need to 'root' our phones.
I think the internal memory of the phones has two parts - one holds the ROM (the operating system) and the other is a 'cache' which holds user/system info relevant to the ROM. The cache is specific to the ROM which is why if you change from say the stock ROM to opendesire you need to wipe the cache. However, if you upgrade the ROM, eg opendesire 2.1 to opendesire 2.2 you do not need to wipe the cache.
To be able to access the part of the phone which holds both the ROM and the cache you need to be root/superuser. If unrevoked worked without errors and you have been able to change ROMS (i recommend ROM manager) then you have 'rooted' your phone.
When ROM manager asks if you wish to back up your ROM I think it only backs up the cache, not the ROM itself, as that would already be on your SD card as a .zip file.
If you wish to go back to stock I think you need to download stock ROM, use ROM manager to install it, then go back to ROM manager and use the backup/restore option and restore your initial backed up cache.
Hope this helps a little!
tephra said:
I forgot to say, I havn't rooted the phone - I dont know if that makes a difference... I actually thought the unrevoked thing was going todo more that just install a different debug boot loader...
Click to expand...
Click to collapse
You rooted the phone when you ran Unrevoked3, that's why you have superuser permissions.
It doesn't install a different boot loader, it installs a new recovery which allows you to easily flash custom roms without having to use fake-flash.
Something must have gone wrong during your nandroid backup.
ok i understand about the root bit and also the recovery bit now - thanks
my nandriod backup folder has:
boot.img
cache.img
data.img
nandroid.md5
recovery.img
system.img
one thing, is this desire is a telstra branded phone. Now i have read that i might require a goldcard.
could this be causing the problems I am seeing?
last night I loaded the original RUU on, now I will see if the nandroid restore fixes my apps and stuff...
edit - hrmm the original RUU has removed CWM recovery... i will load up unrevoked3 again...
tephra said:
ok i understand about the root bit and also the recovery bit now - thanks
my nandriod backup folder has:
boot.img
cache.img
data.img
nandroid.md5
recovery.img
system.img
one thing, is this desire is a telstra branded phone. Now i have read that i might require a goldcard.
could this be causing the problems I am seeing?
last night I loaded the original RUU on, now I will see if the nandroid restore fixes my apps and stuff...
edit - hrmm the original RUU has removed CWM recovery... i will load up unrevoked3 again...
Click to expand...
Click to collapse
You shouldn't need a goldcard with ClockworkMod, I didn't need one for my branded Desire.
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.
Hi guys!
I am sorry if this has already been answered somewhere, but I searched pretty thoroughly and I couldn't find a solution
I am trying to S-OFF an HTC Desire for a friend of mine and install CyanogenMod using this guide http://forum.xda-developers.com/showthread.php?t=1016084.
We rooted the phone without any issues, but before going through Alpharev I decided to make a nandroid backup through the phone's original recovery image (just as advised on Alpharev's site: "We try to leave the current ROM and datastructures completely intact. It is, however, advised to ALWAYS nandroid backup your phone before you run this procedure.
You will then always have a correct/current backup to fall back on in case something breaks."). So I just went into the Backup and Recovery menu and I chose backup.
Unfortunately after backing up, the phone went into a boot loop. We tried taking-out the battery and even doing a hard reset but nothing helped. Eventually we flashed the original RUU from O2 (it's an O2 Germany phone) and this fixed the issue.
I am a bit concerned since I wasn't able to find anyone who had the same problem and it is a bit weird that the phone should go into a boot loop without even installing another ROM or anything - just trying to do a backup of the stock ROM. I am thus a bit hesitant to go on with the S-OFF...
Any help would be deeply appreciated!
Well, first of all, you don't need to be S-Off to install CyanogenMod7. Only root. Usually, people do S-Off so they can change the Boot Splash image.
Make a Gold Card for your SD. Some Desire's need it, some don't. Better safe than sorry.
Secondly, after root, I would goto the market and install ROM Manager. Then flash to the latest Clockwork Recovery.
Then,I would make sure I have a recent Recovery image (NandBackup)
Download Gapps.zip to the root of the SD.
Download the CyanogenMod7 to the root of the SD, boot phone to recovery, Wipe cache memory, also goto Advanced and wipe the Delvik memory.
Then Install from SD, do the CM7, then after it finishes, Select Install from SD again, and install the Gapps.zip
Why your backup failed, who knows. I suppose you were using Unrevoked?
Thanks! Do you know why the boot loop could happen?
Moscow Desire said:
Well, first of all, you don't need to be S-Off to install CyanogenMod7. Only root. Usually, people do S-Off so they can change the Boot Splash image.
Make a Gold Card for your SD. Some Desire's need it, some don't. Better safe than sorry.
Secondly, after root, I would goto the market and install ROM Manager. Then flash to the latest Clockwork Recovery.
Then,I would make sure I have a recent Recovery image (NandBackup)
Download Gapps.zip to the root of the SD.
Download the CyanogenMod7 to the root of the SD, boot phone to recovery, Wipe cache memory, also goto Advanced and wipe the Delvik memory.
Then Install from SD, do the CM7, then after it finishes, Select Install from SD again, and install the Gapps.zip
Why your backup failed, who knows. I suppose you were using Unrevoked?
Click to expand...
Click to collapse
I suppose, there was some code that didn't get deleted due to the rooting process, if you used unrevoked. Although it rarely happens, sometimes it does.
Or maybe it didn't like some Application. Who knows. All it takes, is 1 peice of bad code.
With AlphaRev, although many use it, I believe it changes your bootloader code.
And, you can sometimes have problems as well.
But follow the steps I mentioned, and you should be ok.
Just make sure you create and use the Gold Card first.
The boot loop is a common issue with the first nandroid. All you had to do was restore the nandroid you just made.
Sent from my HTC Desire using XDA Premium App
TheGhost1233 said:
The boot loop is a common issue with the first nandroid. All you had to do was restore the nandroid you just made.
Sent from my HTC Desire using XDA Premium App
Click to expand...
Click to collapse
Right - I thought about that, but then I was hesitant, because I figured if it went into a boot loop then it probably did not create the backup image properly... So can I still restore the backup image now? It is saved on the sdcard so it should be intact after the RUU, right?
It "should be", but, one can only assume so.
Typically, I make a couple of backups each week. One never knows. Yeah, it will tell you successsful. but, better safe than sorry.
Hi Guys,
I Rooted my HTC Desire using Unrevoked Here
http://androidforums.com/desire-all...nrevoked-windows-updated-20th-may-2011-a.html
after that I saw AR-Recovery (via recovery-RA-desire-v2.0.1.img) and there I created a Nandroid Backup. After creating a backup I saw Nandroid folder made in my SD card with backup inside.
Last night I S-OFF my HTC desire using AphaRev 1.08 and when it asked to isntall CWM Recovery during process, I replied YES..
Now I have CWM Recovery, when I go to it to restore my ROM, it cant locate and use my Previouis backups created with AR-Recovery.
Any Way I can restore those backups since I had lots of applications and settings done with that and I cant go through the whole process from Zero again....
And If I restore the backups when I created before S-OFF, will that turn my Phone S-ON again?
Well, you can flash AmonRa via Fastboot Commander.
Or with unrevoked V3.21
Pipusz said:
Well, you can flash AmonRa via Fastboot Commander.
Click to expand...
Click to collapse
I dont know why ppl are mad about CWM Recovery?
I would love to flash AmonRA Recovery.. its just amazing... creates and restores backup so quick.. CWM takes so much time... But still I will install CWM recovery because it ahs become universal recovery
Is there any way I can one time Restore my backup restored with AmonRA recov ery without flashing it? Like some Fastboot stuff..?
jjdoctor said:
I dont know why ppl are mad about CWM Recovery?
I would love to flash AmonRA Recovery.. its just amazing... creates and restores backup so quick.. CWM takes so much time... But still I will install CWM recovery because it ahs become universal recovery
Is there any way I can one time Restore my backup restored with AmonRA recov ery without flashing it? Like some Fastboot stuff..?
Click to expand...
Click to collapse
This issue is intimately tied to the inner workings of the recoveries which are obviously different. I don't believe that it's a good idea to restore backups made with a different recovery.
If you restore an amonra backup with clockworkmod or reverse, you will get an usb brick.
Swyped from my HTC Desire using XDA App
ok I might just flash AmonRa recovery.. can anyone give me a link on how to do that?
EDIT: Found it on youtube.. Thanks all..
Here it is... very good and simple instructions using only Terminal Emulator..
http://www.youtube.com/watch?v=4dHVdAtG1Ew
jjdoctor said:
ok I might just flash AmonRa recovery.. can anyone give me a link on how to do that?
EDIT: Found it on youtube.. Thanks all..
Click to expand...
Click to collapse
You should have posted the youtube link for others.
Swyped from Oxygen
Here it is... very good and simple instructions using only Terminal Emulator..
http://www.youtube.com/watch?v=4dHVdAtG1Ew
I' m lost. Is it OK ?
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.