Downgrade Problem! - Droid Eris Android Development

I have searched and searched, tried every method, but I am offically stuck (I think) - I'm prepping a rooted Eris for return - i had previously been able to flash the 2.1 RUU to return to stock, but it now will not work - I guess somewhere along the lines of rooting/ROM flashing my bootloader has changed (it is now v1.49.000) - I can't get any RUU to work (get ERROR in RUU interface) - I have also tried flashing a P00IMG through HBOOT, but it also errors out (something is older than something else - forgot exactly) - I have tried flashing new HBOOT/Recovery Image through ADB per a JCASE post, but that will not work either - I've gotten older ROM's loaded that will allow for new OTA updates, but they ultimately will not work (signature issues i believe) -
So the question is, is there a method that will get me back to 2.1 "stock" & get rid of Amon Ra recovery?
Again, I have searched and tried every method I could find - I have updated my SDK - help anyone?

Ive seen people just send in rooted ones without any problem, so I dont know if they'll check. But if your worried, i would just flash a 2.1 rom that looks like the stock, cause i dont think they'll know the difference.

Do you have a Nandroid backup from when you first rooted?

crax0r said:
Do you have a Nandroid backup from when you first rooted?
Click to expand...
Click to collapse
Unfortunately I don't have it - you wanna loan me yours?
I'm only kind of kidding....

download unzipme.zip which jcase removed on xda from here http://androidmobileos.com/?p=14928 Inside theres dowgrade rom that you flash through custom recovery (which ever one you use). After that you just follow the instructions (adb parts). Works very well. If you will have any issues with adb part as far as flashing back to stock recovery and hboot than check your hboot version and make sure its s-off. If its not you can get it s-off with batery pull trick.

i had an issue like this where the ruu would say that my phone was disconnected and told me to connect it to the computer,i was on a froyo rom,i flashed a 2.1 rom and the ruu worked,just an fyi just incase this might help if you want to return to stock 2.1,once you run the ruu and sync with google you wiil receive the july update also.
sent from my Eris using Tapatalk pro

Related

Go back to Stock on Hero

I just purchased a HERO 6262 GSM on ebay and looks like it is already rooted and is running FirmwareVerison: Villain5.2, Baseband version:63.18.55.06EU_6.35.06.18, but I want to go back to stock HTC rom. I've installed HTC Sync and downloaded two different RUU's and try to install but it fails. I've tried RUU_Hero_HTC_WWE_1.76.405.6_WWE_release_signed_NoDriver and RUU_Hero_HTC_WWE_1.76.405.1_R3_WWE_release_signed_NoDriver.
It acts like it is going to install the rom, but it fails. In the RUU I get error 140: Bootloader version error. What am I doing wrong? Or which Stock rom should I install.....please help. I would also like the ability to root again and go to Villain down the road.
Much thanks and all help is appreciated!
Nevermind.....I just downloaded and installed RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver without any problems. So I guess I must use this one from now on to go back to stock version. How about how to reinstall Villain 5.2? Much thanks.
Well you haven't done yourself any favours, putting an official, non-rooted ROM on, then wanting to re-root it later.
Goldcard for you methinks.
Lol
You should have read more before you messed with the phone...
You should have done android backup first.
Now
I think you have to.. root.. then load the new ROM.
Sent from my HERO200 using Tapatalk
why would you buy a rooted phone, just to throw some stock firmware on there to want to root it again?
*Facepalm*
Because I wanted to make sure the phone was all good and not screwed up by the previous owner......looks like I gotta use the goldcard method to root it. However, which ROM do you guys recommend?
with the ruu 2.73.405.5 you can use flashrec-20090815.apk and flash recovery image without goldcard
knudsen81 said:
with the ruu 2.73.405.5 you can use flashrec-20090815.apk and flash recovery image without goldcard
Click to expand...
Click to collapse
Seconded. That's actually the RUU I used, to downgrade to, via a gold card. So at least the OP has saved themselves the hassle of that.

eris 2.1 to 1.5 downgrade

my girlfriend hates the OTA 2.1 cause there is so much not working now
so i was wondering if there is way/tutorial to downgrade from the crappy 2.1 OTA back to original 1.5 without rooting
if not what is there a tutorial for rooting then downgrading
Edit:
since i have a moto droid and my girlfriend didnt care much about rooting till now what type of things are diffrent when rooting the eris compared to droid (OCing, roms, themes, nandroid backups, ect.)??
Check out this link to root the eris: http://forum.xda-developers.com/showthread.php?t=647707
I'll post again once I find the 1.5 rom, although I think it may have been removed.
After searching it appears that jcase took the download down at the request of a few users.
So, what I would do is root then flash some of the new roms that have come out. Personally, I'd give either CyanogenEris or Senseless a try because they are AOSP based (like your droid is).
If you are into the Sense scene, I would check out the plethora of roms listed here: http://forum.xda-developers.com/showthread.php?t=649705
so your not able to just downgrade?? cause thats all my girlfriend really wants
and are the 2.1 roms(with sense ui cause for some reason my girlfriend likes it) based off the leaks or the official 2.1 and do they run better then the official 2.1
Edit: that tutorial is for stock 1.5 not 2.1
Downgrade instructions are here http://androidforums.com/all-things...ot-thread-apps-roms-updated-05-06-2010-a.html
Full Downgrade from 2.1root (any) to 1.5 stock - FULLY WORKING
THIS IS NOT FOR LEAK USERS SO DON'T ASK
If it bricks your phone, not my fault (it shouldn't and I hope it doesn't).
Please read and follow the directions included.
unzipme.zip md5sum: 0ed3c91d7574367d65428b3bc230f217
http://www.multiupload.com/6UE7AUN810
This is fully working, I just did a full reflash to 1.5, including the kernel, the system software, the radio firmware, recovery image and the bootloader.
This must be done from a PC with Fastboot, which comes with windows. Linux/Mac users will have to find it and compile it. You will need to have Amon's recovery image installed to use this downgrade, at the end we will overwrite his image with the stock one.
Inside unzipme.zip are three files
downgrade.zip md5sum: c440c87f1e67f4b62e05da0d255e80e9
-Do not unzip/open/alter this file
--Contains your kernel, radio firmware, and system.
recovery.img md5sum: 71a4b633bdb32de9dcdd8953fef43cdc
--stock recovery image
hboot.nb0 md5sum: 38899da4e5e002e3be22900f5f4eb6f7
--Original bootloader
Step one:
Put hboot.nb0 and recovery.img in the tools dir of your sdk.
Put downgrade.zip on the sdcard of your phone
Step two:
Turn your phone off, then turn it back on holding the power button (red) and send button (green). Once in the boot loader press volume down, then volume up to get to Amon's recovery image. Go to wipe, wipe dalvik cache, and do a factory reset (aka wipe data). Then choose flash zip from sdcard, and flash downgrade.zip. The phone will flash the kernel, and system softare, then ask you to reboot. Let it reboot so it can flash the radio, it will restart back in the recovery image. You can power down your phone now.
At this point if your just wanted 1.5 back, you are done.
If you want the original bootloader and recovery image, (ie 100% stock) continue on.
Step three:
Plug your phone into your PC. Power your phone on using the power button (red) and send button (green). Your phone should now be sitting back at the bootloader screen and say FASTBOOT USB. Now on your PC, go to the sdk tools dir in command line. Issue this commanhttp://www.multiupload.com/6UE7AUN810d
Code:
fastboot flash recovery recovery.img
Let it flash, when done wait a minute (just to make sure).
Then issue this command
Code:
fastboot flash hboot hboot.nb0
Once this is done, wait a minute then pull your battery and restart your phone.
You are now back at factory stock.
Click to expand...
Click to collapse
Personally I'd stop after step 2 in case you ever want to flash a rom in the future.
Woops, I missed that she's not rooted. You could root it and go back down to 1.5.
tiggerxplur said:
so your not able to just downgrade?? cause thats all my girlfriend really wants
Click to expand...
Click to collapse
In theory you could downgrade using the same methods as going from RUU 1.17-1.16 (since they have the same bootloader version and are both signed), but I don't know that anyone on 2.1 OTA has tried that.
Even if you got it to downgrade she'd be bugged constantly about the OTA (every 2 minutes I believe), which would suck for her. Also it takes up ~100MB of space on her phone too, so I would just go with rooting.
tiggerxplur said:
Edit: that tutorial is for stock 1.5 not 2.1
Click to expand...
Click to collapse
The root process is exactly the same for 2.1 OTA users, but will not work if it's a 2.1 leak.
At this point all the roms are based on 2.1 OTA or another person's 2.1 rom and most of them run better than the 2.1 OTA.
It's really just a trial-and-error process. Some users will swear by one rom and hate another, while others will swear by a different rom.
I'd have her look at all of the roms and pick one based on looks, because it sounds like she won't use most of the advanced features anyways.
nindoja said:
In theory you could downgrade using the same methods as going from RUU 1.17-1.16 (since they have the same bootloader version and are both signed), but I don't know that anyone on 2.1 OTA has tried that.
Even if you got it to downgrade she'd be bugged constantly about the OTA (every 2 minutes I believe), which would suck for her. Also it takes up ~100MB of space on her phone too, so I would just go with rooting.
The root process is exactly the same for 2.1 OTA users, but will not work if it's a 2.1 leak.
At this point all the roms are based on 2.1 OTA or another person's 2.1 rom and most of them run better than the 2.1 OTA.
It's really just a trial-and-error process. Some users will swear by one rom and hate another, while others will swear by a different rom.
I'd have her look at all of the roms and pick one based on looks, because it sounds like she won't use most of the advanced features anyways.
Click to expand...
Click to collapse
yea she doesnt care for the advanced things i have tried to get her to use another home replacement app like helix cause i know sense ui is a resource hog but she likes it too much and doesnt wanna try and get used to something new but i will talk her into rooting and choosing a rom she might like thanks for the help
i had a rom before 2.1 for the droid that didnt block the ota and it was very annoying it varied between 2 minutes to ten minutes
is there an app like rom manager to switch between roms like the droid
I went from 2.1 OTA back down to 1.5 using the RUU MR2 on the computer. Worked like a charm!
downgrade leak 2.1 to 1.5 stock
Is there anyway to downgrade this horrible 2.1 leak back to the stock 1.5 version.
damon428 said:
Is there anyway to downgrade this horrible 2.1 leak back to the stock 1.5 version.
Click to expand...
Click to collapse
No...... x10
Please Delete. Duplicate.
If its been said once, it's been said a thousand times here,
"can I root the 2.1 LEAK?"
As always the answer is HELL NO!!!!
"can I root 2.1 OTA?"
Yes.
"can I downgrade 2.1 OTA to 1.5"
Yes.

God, I just KNEW I shouldn't have even tried to root... Please help =(

I recently got back a warranty swap Nexus One with an old version of android (2.2) and thought to myself "Hell, I might as well try rooting for once since it the 1-click method doesn't unlock the bootloader and you can always go back right?" Wrong
Well, I updated the radio as part of the Cyanogen 6.1 installation to radio version 5.12.00.08 and now that I don't want to be rooted anymore I can't seem to get the radio version back to normal to what it should be on 2.2.1
The 2.2.1 radio should be: Baseband version 32.36.00.28U_4.06.00.12_7
But when I updated to 2.2.1 it stayed the same: Baseband version 32.50.00.32U_5.12.00.08
Have I screwed up my radio? I just want to get my phone back to normal please help
ap3604 said:
I recently got back a warranty swap Nexus One with an old version of android (2.2) and thought to myself "Hell, I might as well try rooting for once since it the 1-click method doesn't unlock the bootloader and you can always go back right?" Wrong
Well, I updated the radio as part of the Cyanogen 6.1 installation to radio version 5.12.00.08 and now that I don't want to be rooted anymore I can't seem to get the radio version back to normal to what it should be on 2.2.1
The 2.2.1 radio should be: Baseband version 32.36.00.28U_4.06.00.12_7
But when I updated to 2.2.1 it stayed the same: Baseband version 32.50.00.32U_5.12.00.08
Have I screwed up my radio? I just want to get my phone back to normal please help
Click to expand...
Click to collapse
Does the phone still function? Making calls, sending texts.. etc?
If so, then whats the problem? The radio update was probably included in the ROM you flashed, if you're experiencing problems, search the forum for the Radio you want and instructions on how to flash
Be careful though, you can brick your phone when flashing a radio.. so make sure you read the instructions..
Good Luck
S_Dot said:
Does the phone still function? Making calls, sending texts.. etc?
If so, then whats the problem?
Click to expand...
Click to collapse
2 things I am worried about:
1. Before I rooted and changed the radio, I could check for system updates and it would say I could to update to 2.2.1 ota... Now, after I unrooted and got it back to stock 2.2, I would check system updates and it no longer gave me the option to update to 2.2.1 (I had to manually do this)
This worries me since I don't want to miss out on all future ota updates if my radio has been screwed up when I flashed one earlier.
2. Radio has been slower since upgrading manually to 2.2.1 but still having the old radio in place.
Isn't the each radio optomized for the particular android build?
Also what about rooting causes the phone not to get the new ota update? Is it the changing of its radio?
What country is yor phone? And with what build did it came after warranty?
My guess the radio is just part of the update (if you flashed a stock rom)
I recently bought my nexus in holland it came with FRF91
And 5.08.00.04 radio so
Radio isn't per build.
There was a major change to adjust to Froyo in 4.06 radio, all the above are compatible with it, all the 4.04 and below are compatible with Eclair and not suitable for Froyo.
2.2.1 includes 5.08 anyway. Your not getting OTA doesn't have anything to do with radio.
You can flash any radio you want when you're rooted, using the guide found in Wiki.
Yeah I've benefited from newer radios. Dont sweat it your rooted, this is good.
Sent from my Nexus One using XDA App
ap3604 said:
Also what about rooting causes the phone not to get the new ota update? Is it the changing of its radio?
Click to expand...
Click to collapse
It's the rom and recovery.
I really would not get stressed out about this. Worst case scenario is that you have to come on xda every so often and flash the update manually.
LOL, if ur on CM6 u already have 2.2.1 and worrying about future otas, root user update to latest version normally before unrooted people and u should have to problem updating, if u want to revert back to the old boring stock version just flash one of the shipping roms in bootloader by renaming them to PASSIMG.zip
ap3604 said:
I recently got back a warranty swap Nexus One with an old version of android (2.2) and thought to myself "Hell, I might as well try rooting for once since it the 1-click method doesn't unlock the bootloader and you can always go back right?" Wrong
Well, I updated the radio as part of the Cyanogen 6.1 installation to radio version 5.12.00.08 and now that I don't want to be rooted anymore I can't seem to get the radio version back to normal to what it should be on 2.2.1
The 2.2.1 radio should be: Baseband version 32.36.00.28U_4.06.00.12_7
But when I updated to 2.2.1 it stayed the same: Baseband version 32.50.00.32U_5.12.00.08
Have I screwed up my radio? I just want to get my phone back to normal please help
Click to expand...
Click to collapse
1) From where did you upgrade to 2.2.1?
if you upgraded from rom manager or any ROM given by developer, they remove the radio and provide it as a separate update file.
http://www.tap3w0rm.com/hosted/android/radios/nexus-1/FRF50-radio-4_06_00_12_7.zip is the update for radio you want.
2) However, Radio update is not what you want. "Recovery" is what you want. Recovery is a piece of software that allows you to flash custom ROMS. did you install Amon's recovery or Clockwork (from ROM Manager) recovery?
You will not get OTA if you have one of these custom recoveries. you will need the stock recovery.
3) In short, you need to flash your phone with a completely stock google ROM.
follow these instructions
http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
hmmm interesting...what makes you wanna unroot besides OTA? From what I see that's virtually no advantage to go back to stock rom
If you really want official OTAs, just make sure you check xda often when those are pushing out. There will be stock OTA updates hanging around.
Try this:
http://djmcnz.batteryboss.org/Kang-o-rama/froyo/radio/froyo-radio-update-signed.zip
Flash it from custom recovery. It will reboot, unpack the radio, reboot again in a few minutes, and you should end up back on the 4.06 radio. For what it's worth.
If you want to go back to totally stock unrooted, the most complete way to do so is using a PASSIMG file.
arkavat said:
However, Radio update is not what you want. "Recovery" is what you want. Recovery is a piece of software that allows you to flash custom ROMS. did you install Amon's recovery or Clockwork (from ROM Manager) recovery?
You will not get OTA if you have one of these custom recoveries. you will need the stock recovery.
Click to expand...
Click to collapse
I installed Clockwork recovery when I first did the Cyanogen flash so how do I know if I still have it on my phone blocking OTA updates?
I had an old 2.2.1 update.zip on my SDcard from an old Nexus One that I sent in through a warranty swap.
Then I powered off and did the whole Volume Down + Power button.
I get the screen with the 3 androids on skateboards and clicked on Recovery
I press on recovery
When I see the triangle with exclamation mark I press power button + volume up and the only options I see are reboot system now, install update.zip from sd card, factory reset, wipe cache
I click on install update.zip (2.2.1) and reboot system now so the phone reboots but I still am stuck with the old radio. How do I know if I have stock recovery and will get OTA updates from now on?
arkavat said:
In short, you need to flash your phone with a completely stock google ROM.
follow these instructions
http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
Click to expand...
Click to collapse
I tried the steps exactly (PASSIMG.ZIP on sd card) but when I do the power + volume down step 7 doesnt happen. There isn't any screen looking for update files. I get the screen with the 3 skateboarding androids instead and no way to get the PASSIMG.ZIP file to work.
Can't you download a unrooted 2.2 rom from rom manager and then ota once its installed? Dont quote me though I've never actually tried to unroot
Sent from my Nexus One using XDA App
ap3604 said:
I tried the steps exactly (PASSIMG.ZIP on sd card) but when I do the power + volume down step 7 doesnt happen. There isn't any screen looking for update files. I get the screen with the 3 skateboarding androids instead and no way to get the PASSIMG.ZIP file to work.
Click to expand...
Click to collapse
On my phone this is what I get in bootloader mode...
I start up the phone holding down the trackball, and I get the Fastboot with the skateboards. The first menu option, BOOTLOADER, is highlighted. I press Power and I get to the HBOOT screen (also with skateboarding androids). I wait 5-10 seconds and it checks for a PASSIMG on SD. Since I don't have one, it finds nothing and returns me to HBOOT.
Or alternately I boot while holding volume down and I get HBOOT directly. In 5-10 seconds it checks for PASSIMG. The only time it won't do that is if my SD is not installed.
You're saying that on yours it doesn't check for PASSIMG at all?
I am in a somewhat similar boat (though not exactly), a colleague of mine purchased a used Nexus One off of fleebay and it came rooted running Cyanogen 6 with Clockwork Recovery (for the Recovery Image).
My colleague wants it to be completely stock (which I do not understand as I find Cyanogen 6 to be far better) and asked me the resident Android guy if I could help.
I figured PASSIMG.zip was the way to go and downloaded the stock rom from developer.htc.com and renamed it PASSIMG.zip. I put the PASSIMG.zip file on his SD card and booted into the bootloader. It checks the PASSIMG.zip image but does not offer me option to install it. It simply checks it and then offers me the normal 4 options.
Any thoughts?
Dan
Read the Wiki, it has specific reference to FRG83 stock ROM now, which refuses to work in PASSIMG mode.
dan1431 said:
I am in a somewhat similar boat (though not exactly), a colleague of mine purchased a used Nexus One off of fleebay and it came rooted running Cyanogen 6 with Clockwork Recovery (for the Recovery Image).
My colleague wants it to be completely stock (which I do not understand as I find Cyanogen 6 to be far better) and asked me the resident Android guy if I could help.
I figured PASSIMG.zip was the way to go and downloaded the stock rom from developer.htc.com and renamed it PASSIMG.zip. I put the PASSIMG.zip file on his SD card and booted into the bootloader. It checks the PASSIMG.zip image but does not offer me option to install it. It simply checks it and then offers me the normal 4 options.
Any thoughts?
Dan
Click to expand...
Click to collapse
Try as update.zip through custom recovery? Then clear the custom recovery by flashing stock one...then delete superuser.apk + unroot?
liam.lah said:
It's the rom and recovery.
[snip]
Click to expand...
Click to collapse
Actually, it's just the ROM. Even if you have a custom recovery: a rooted, stock ROM will still receive OTA updates...
Yes but on quite a few custom recoveries, it will fail to install due to the signature.
Rusty! said:
Yes but on quite a few custom recoveries, it will fail to install due to the signature.
Click to expand...
Click to collapse
True. If you are using anything earlier than Amon_RA 1.8 or the latest ClockworkMod, it won't install.

[GUIDE] Installing RUU's

mod: If this should be in DHD General, please move it
At the moment, sometimes current RUUs (ROM Update Utility) do not flash from the latest RUU exe - many times it will not recognise the Desire HD.
If you are having this problem, this is how to flash the latest stock RUU.
The latest RUU at the time of writing is 1.32.405.6.
You can download the RUUs from xmoo's thread or from mousey_'s site.
note: This is mainly for stock phones, for vendor-derived ones (e.g Vodafone DHDs in Australia) you will also need a goldcard.
Common Steps
Download the latest RUU (1.32.405.6).
Run it as administrator.
Tick the 'I understand the caution indicated above...' box, and click next.
At this point do not go any further.
Navigate to C:\Users\Ivo\AppData\Local\Temp (Replace my username with yours; AppData is a hidden folder)
You should see one or two folders like this:
{719CE201-7B12-4A13-9AF6-8F359FE69C7B}
Go into the one with dotnetinstaller.exe in it.
Open up the next folder.
Copy rom.zip into another folder (outside of temp).
At this point just Cancel and quit out of the ROM Update Utility.
A) Install through PC
Download and install HTC Sync 3.0 and restart.
Download the 1.15.405.1 Test RUU. It is the only one currently known to find the Android DHD.
Start it the same way as before, get to the
1. Connect the Smartphone to the USB Cable.
step. (but no further)
Again, go to the AppData local temp directory (same as above), and find the folder with dotnetinstaller.exe and inside that, rom.zip
You want to delete the rom.zip (which is the 1.15 version) and replace it with (copy back) the 1.32 rom.zip you copied out earler.
DO NOT UPDATE WITH 1.15 ROM, IT IS NOT DESIGNED FOR RETAIL DHDs.
Now click through the next buttons.
The 1.15 Utility should now be set to update with the 1.32 rom. You will see the version number of the rom at the final step.
Click update and watch the magic happen
B) or Install through Phone
With the rom.zip you copied out earlier, rename it PD98IMG.zip
Copy this onto the root of your microSD card through some means (disk drive, ftp, wireless).
Restart your phone and boot into the bootloader by holding power and volume down at the same time as it restarts.
It should go into the bootloader, take a fair while to check the zip on the sd card, and then ask you if you want to flash it.
Say yes!
Hope this can help some people for whom the 1.32 RUUs aren't working for them
Thanks for putting up this post! I was about to request one last night.
Now if only there could be a similar guide to flashing custom ROMs
To force unroot, I could reinstall RUU 1.32.405.6 from Win7 without problems, a bit longer than updating/reinstalling a WinMo 6.5.x rom (my former HD2), but it went through...
Thanks Ivolol this worked a treat
Appreciate your guide and efforts.
I am running Win 7 64. folowed 1.15 method now running latest 1.32.405.6
Howling Wolf said:
To force unroot, I could reinstall RUU 1.32.405.6 from Win7 without problems, a bit longer than updating/reinstalling a WinMo 6.5.x rom (my former HD2), but it went through...
Click to expand...
Click to collapse
Weird; I tested a couple of RUUs (not as many as xmoo did) and all of them couldn't connect to my phone (whereas 1.15 could).
It'd be interesting to find out what the factors are that cause this. ATM the guide above is what to do if someone finds themselves in the same situation (the current ROMs won't find the phone).
Howling Wolf said:
To force unroot, I could reinstall RUU 1.32.405.6 from Win7 without problems.
Click to expand...
Click to collapse
+1 here, went through the normal RUU process fine just for ****s and giggles. I've extracted the ROM.zip though in case it's needed for future use.
sorry for the noob question..just had my DHD for the last 5 days. I come from galaxy S, and in there whenever we flash a rom all the data gets wiped out.
is it true also when we flash a RUU??
also if I do that...would i still be able to get OTA updates??
nandihno said:
sorry for the noob question..just had my DHD for the last 5 days. I come from galaxy S, and in there whenever we flash a rom all the data gets wiped out.
is it true also when we flash a RUU??
also if I do that...would i still be able to get OTA updates??
Click to expand...
Click to collapse
I haven't got complete knowledge of the entire subject yet, but:
a RUU will completely wipe all user settings / apps. Won't do anything to the sd card though.
An update.zip is akin to an OTA update, it does not wipe user settings.
Flashing with a stock RUU will mean that you can still get OTA updates.
I've tried using the phone method and unable to flash successful. I believe you need a valid GoldCard to use this method.
Can you confirm if the GoldCard is required for doing it with the phone method?
In addition, once the unit (especially our Voda branded one) is flashed with the latest ROM, OTA may not run properly which will result in disabled functionality (as recorded in this thread: forums.whirlpool.net.au/forum-replies.cfm?t=1575514, wifi stopped working). Theory said you'll need a GoldCard to get OTA to work properly (from another thread in XDA).
Thanks.
Great Guide thank you very much. Now i know to flash back to stock now if something gose wrong as iam a noob to android it took some time to work it out even tho it is a simple guide now i wanna know after getting perm root how do i flash a custom rom ? do i need clockwork mod?
tleehm said:
I've tried using the phone method and unable to flash successful. I believe you need a valid GoldCard to use this method.
Can you confirm if the GoldCard is required for doing it with the phone method?
In addition, once the unit (especially our Voda branded one) is flashed with the latest ROM, OTA may not run properly which will result in disabled functionality (as recorded in this thread: forums.whirlpool.net.au/forum-replies.cfm?t=1575514, wifi stopped working). Theory said you'll need a GoldCard to get OTA to work properly (from another thread in XDA).
Thanks.
Click to expand...
Click to collapse
There is a big reason I decided to buy my DHD outright and not through Vodafone
I'm pretty sure that Vodafone's OTAs will be different from HTC's. In order to get OTAs from Vodafone you will need their image on it.
Also with vodafone's ROM installed, I wouldn't think it would accept HTC's vanilla ROM/RUU without going through the entire root process (it would only accept Vodafone signed ROMs). So in order to get onto HTC's ROMs I would think you need to follow http://forum.xda-developers.com/showthread.php?t=841076 before the phone will let you run a HTC RUU on it.
I haven't explored goldcards as I personally have no use for one, but you might also need one by the sounds of it for the Vodafone ROM to let you replace it. (edit: yes it looks like you need one to officially flash from a Vendor ROM to a generic one.)
So this guide is mainly for people with vanilla HTC phones. Although someone has posted a stock rooted Vodafone ROM on the phones so you might be able to use the same techniques outlined here with that.
ssimmmo said:
Great Guide thank you very much. Now i know to flash back to stock now if something gose wrong as iam a noob to android it took some time to work it out even tho it is a simple guide now i wanna know after getting perm root how do i flash a custom rom ? do i need clockwork mod?
Click to expand...
Click to collapse
clockwork mod is useful but not entirely necessary. You might be able to use this guide's method to flash a custom ROM onto it (haven't tried yet), but otherwise I think what you need is a recovery img that will let you upload custom/unsigned ROMs onto it. And also S-OFF I imagine.
ok so i have S-OFF and clockwork mod recovery...
if i have the rom.zip and rename it to PD98IMG.zip and run bootloader.
i shouldnt have any problems flashing this rom??
BTW am using Aus branded Vodafone HDH.
also..IF i flash this rom..would i loose S-Off and clockwork recovery mod??
would flashing this allow me to gain OTA???
nandihno said:
ok so i have S-OFF and clockwork mod recovery...
if i have the rom.zip and rename it to PD98IMG.zip and run bootloader.
i shouldnt have any problems flashing this rom??
BTW am using Aus branded Vodafone HDH.
also..IF i flash this rom..would i loose S-Off and clockwork recovery mod??
would flashing this allow me to gain OTA???
Click to expand...
Click to collapse
If you flash a stock RUU rom.zip then you will loose all custom apps, data, s-off, recovery, etc. It puts it to factory settings. If you are in the business of flashing ROMs then I wouldn't worry about OTA because the developers here will integrate HTC updates as they come out, if they come out
However yes I think if you flashed a stock RUU then you will be able to get OTA. You might still need a goldcard, I'm not exactly sure.
ivolol said:
mod: If this should be in DHD General, please move it
At the moment, sometimes current RUUs (ROM Update Utility) do not flash from the latest RUU exe - many times it will not recognise the Desire HD.
If you are having this problem, this is how to flash the latest stock RUU.
The latest RUU at the time of writing is 1.32.405.6.
You can download the RUUs from xmoo's thread or from mousey_'s site.
note: This is mainly for stock phones, for vendor-derived ones (e.g Vodafone DHDs in Australia) you will also need a goldcard.
Common Steps
Download the latest RUU (1.32.405.6).
Run it as administrator.
Tick the 'I understand the caution indicated above...' box, and click next.
At this point do not go any further.
Navigate to C:\Users\Ivo\AppData\Local\Temp (Replace my username with yours; AppData is a hidden folder)
You should see one or two folders like this:
{719CE201-7B12-4A13-9AF6-8F359FE69C7B}
Go into the one with dotnetinstaller.exe in it.
Open up the next folder.
Copy rom.zip into another folder (outside of temp).
At this point just Cancel and quit out of the ROM Update Utility.
A) Install through PC
Download and install HTC Sync 3.0 and restart.
Download the 1.15.405.1 Test RUU. It is the only one currently known to find the Android DHD.
Start it the same way as before, get to the
1. Connect the Smartphone to the USB Cable.
step. (but no further)
Again, go to the AppData local temp directory (same as above), and find the folder with dotnetinstaller.exe and inside that, rom.zip
You want to delete the rom.zip (which is the 1.15 version) and replace it with (copy back) the 1.32 rom.zip you copied out earler.
DO NOT UPDATE WITH 1.15 ROM, IT IS NOT DESIGNED FOR RETAIL DHDs.
Now click through the next buttons.
The 1.15 Utility should now be set to update with the 1.32 rom. You will see the version number of the rom at the final step.
Click update and watch the magic happen
B) or Install through Phone
With the rom.zip you copied out earlier, rename it PD98IMG.zip
Copy this onto the root of your microSD card through some means (disk drive, ftp, wireless).
Restart your phone and boot into the bootloader by holding power and volume down at the same time as it restarts.
It should go into the bootloader, take a fair while to check the zip on the sd card, and then ask you if you want to flash it.
Say yes!
Hope this can help some people for whom the 1.32 RUUs aren't working for them
Click to expand...
Click to collapse
As I am Newbie of Android and I have noob quesitons. Could you please explain what is RUU and use this for what purpose?
Yeah. I got a goldcard inside of my phone but the bootloader doesn't recognize the P98IMG on my sdcard even though its there for sure. No idea how to fix this
Dr. lele said:
Yeah. I got a goldcard inside of my phone but the bootloader doesn't recognize the P98IMG on my sdcard even though its there for sure. No idea how to fix this
Click to expand...
Click to collapse
How big is ur sd-card, and also what brand. Sometimes this is also a issue....
It's a kingston 8 gb class 4, but thanks for the tipp, I'll try another.
Yep, it was the sdcard xD. It's updating as I type
Carnt I just use the updater on the pc with the Rom? I have tried the method and I don't see a Rom file just a data1 file which is a ear file. I really would like stock ROM on my device
edit: i just used the exe and it installed perfect, so now it should be stock with no root,and sn
cxeka7 said:
As I am Newbie of Android and I have noob quesitons. Could you please explain what is RUU and use this for what purpose?
Click to expand...
Click to collapse
An RUU is an exe which contains the stock 'firmware' from HTC to flash to your device. Basically it will do a full factory reset of your device. It won't wipe your sdcard but it will overwrite everything else.
it didnt asked me for anything on option B) or Install through Phone. i didnt get the option to flash it.

[REQUEST] Can anyone write a guide for Unrooting

Its only going to be a matter of time before people will need to send phones back under warranty for whatever reasons so a guide for unrooting will be needed.
Any takers?
G2 already has one, but obviously we will need different rom/hboot etc to go back to our stock.
Not just unrooting, but going completely back to stock, i.e. S-ON and stock ROM.
As you say, we should be able to base it on this - http://forum.xda-developers.com/showthread.php?t=835971
Although we have several different stock ROMs, e.g. European, Asian, Vodafone UK, etc.
this is already covered in the FAQ (easy tutorial @ dev forum)
http://forum.xda-developers.com/showpost.php?p=9143411&postcount=2
gtrab said:
this is already covered in the FAQ (easy tutorial @ dev forum)
http://forum.xda-developers.com/showpost.php?p=9143411&postcount=2
Click to expand...
Click to collapse
That just says to use Visionary to turn off rooting. Or did I miss something ?
As I said, I think we need to cover how to return a phone completely to stock, and I don't think it includes all that you'd really need to do, or if you didn't use Visionary in the first place, e.g. the kind of stuff in the G2 post that I linked.
steviewevie said:
That just says to use Visionary to turn off rooting. Or did I miss something ?
As I said, I think we need to cover how to return a phone completely to stock, and I don't think it includes all that you'd really need to do, or if you didn't use Visionary in the first place, e.g. the kind of stuff in the G2 post that I linked.
Click to expand...
Click to collapse
It does say to flash an RUU to S-ON which in the past I would have said would work, but seeing how the G2 forums are not suggesting that its that simple my guess would be that its not that simple.
I had to flash the PC10img thing taken from the stock ROM to restore root and s-on. But no idea how to extract that PC10img thing, not that I have looked into it either.
That info was from one of the guides in the dev section I'm sure.
Sent from my HTC Vision using XDA App
What might work now will probably not work once an OTA update comes out for the DZ though, as per the problem on the G2 they've had which has led to quite a few semi-bricks (possibly full bricks in some cases ?).
Done some research, it would seem that flashing an RUU would work fine for those of us already rooted, if an OTA were to come out those who rooted after the OTA would have issues unless an RUU for the same OTA was released as well. (this is basically because the RUU's currently available will be older than the software the phone is on so the RUU would fail leaving you with a semi-bricked phone as described above, basically it would flash stock hboot and recovery then fail to flash the /system so you would be left with no root or recovery and no rom.
Flashing the ruu would give rise to accepting the OTA too, if you really wanted to do that, but it might block root.
you just need the RUU for your correct original phone version
OR use a gold card
eg. I have debranded mine from bell NAM 1.34.666.5 to euro generic 1.34.405.5
To go back to stock, I can:
1.- grab the bell 1.34.666.1 RUU (its slightly previous, but is the correct original version for my phone)
OR
2.- run the euro generic 1.34.405.5 with a golcard inserted
gtrab said:
you just need the RUU for your correct original phone version
Click to expand...
Click to collapse
Isn't that dangerous though once we get any OTAs, and could lead to this ?
http://forum.xda-developers.com/showthread.php?t=838484
Or am I missing something ?
steviewevie said:
Isn't that dangerous though once we get any OTAs, and could lead to this ?
http://forum.xda-developers.com/showthread.php?t=838484
Or am I missing something ?
Click to expand...
Click to collapse
Yes thats what I was getting at in my post above, any RUU you flash needs to be of the same or newer version of what your previously flashing. You cannot GoldCard to flash an RUU to S-ON or you get left with the semi-brick where you have stock recovery and hboot, but no rom installed.
So if an OTA comes out, you can't accept it, s-off then use an older RUU to s-on again. You would have to flash an RUU of that OTA version (if one is released).
Basically its best to not accept any OTA if you can avoid it and just wait for a custom rom of the same, that way we can always use the older RUU's to s-on if we need it.
I successfully downgraded my rooted/S-OFF'd phone to an earlier ROM last night. I simply followed this method - http://forum.xda-developers.com/showthread.php?t=832503
I'm of the firm belief that this is the onyl way to do it if you are at S-OFF. If you have S-OFF, then flashing an older RUU will probably brick your phone.
Well yesterday I perm root and s-off my european Desire Z with World/Euro generic 1.34.405.5. Somehow everything went bad after flashing recovery mode, so I decided to unroot it and bring it back to original settings.
I found there are 2 methods, one is to run the original ruu, and the other one was to copy the exact World/Euro generic 1.34.405.5 PC10img.zip to the root of my sd card.
Then entered to bootloader, and the phone recognize the archive, I simply apply it, and now I am back again to original stock.
However now I tried again and I am happily root, and S-Off following the amazing gtrab guide (http://forum.xda-developers.com/showthread.php?t=835777)
buzmay said:
I found there are 2 methods, one is to run the original ruu, and the other one was to copy the exact World/Euro generic 1.34.405.5 PC10img.zip to the root of my sd card.
Click to expand...
Click to collapse
That's the thing I keep saying though, flashing the original RUU worked for you because you weren't trying to downgrade the ROM, it was the same version that you already had on (just S-OFF etc). If you had a later version on your phone (e.g. via an OTA update) and were trying to flash to an earlier one, you would have bricked it trying the straight RUU method.
So what should be done is download and install an RUU - say 1.234.987, so you're on 1.234.987 - then root / S-OFF / custom ROM the phone. If anything goes wrong, reinstall the 1.234.987 RUU.
By the way - that's a fake RUU
DanWilson said:
So what should be done is download and install an RUU - say 1.234.987, so you're on 1.234.987 - then root / S-OFF / custom ROM the phone. If anything goes wrong, reinstall the 1.234.987 RUU.
Click to expand...
Click to collapse
During that process, if the stock HBOOT/recovery that is installed by that RUU decides that what you're trying to flash is "older" than your custom ROM, you're screwed though. That's why the "debranding" guide has extra steps in it, i.e. gold card and editing the misc partition.
steviewevie said:
During that process, if the stock HBOOT/recovery that is installed by that RUU decides that what you're trying to flash is "older" than your custom ROM, you're screwed though. That's why the "debranding" guide has extra steps in it, i.e. gold card and editing the misc partition.
Click to expand...
Click to collapse
I hate HTC.
Love the phones, love the Sense, hate the security.
Why not give us a command like the N1? WHY!?
So you should backup the system partition before S-OFF and so on? Like so a dd? (Following on from previous post)
DanWilson said:
So you should backup the system partition before S-OFF and so on? Like so a dd? (Following on from previous post)
Click to expand...
Click to collapse
The system partition isn't changed in S-OFF, that's the boot partition (just allows writing to the system partition).
The gold card and editing of the misc partition should work fine, as per this thread - http://forum.xda-developers.com/showthread.php?t=832503
It worked for me last night to flash to an older stock ROM (which also gave me S-ON again, removing my S-OFF).
steviewevie said:
The system partition isn't changed in S-OFF, that's the boot partition (just allows writing to the system partition).
The gold card and editing of the misc partition should work fine, as per this thread - http://forum.xda-developers.com/showthread.php?t=832503
It worked for me last night to flash to an older stock ROM (which also gave me S-ON again, removing my S-OFF).
Click to expand...
Click to collapse
Cool. Confused. I believe you though.
But you are saying just to make a gold card, and edit the misc partition?
Nice
DanWilson said:
Cool. Confused. I believe you though.
But you are saying just to make a gold card, and edit the misc partition?
Click to expand...
Click to collapse
Following that guide that I linked worked for me. Yes, I turned my SD card into a gold card and edited the misc partition. Then it is fooled into thinking you're restoring a ROM of the same version that it already is running, so it lets you do it.
Actually, I do wonder whether both steps are necessary (i.e. gold card *and* editing misc), because I thought the whole point of the gold card was that it avoided those checks, so perhaps you can do one or the other ? I am only thinking out loud here, and may well be missing something, so I don't suggest trying it other than as in that guide.

Categories

Resources