Database Users

[Q] Bricked Wildfire after attempted Froyo Update, Please help!

First of all, sorry if this is posted in the wrong place. Im pretty new to all this and don't really know how things work here.
I think im pretty buggered, and im pretty far out of my depth now. Im just posting to see if anything can be done or if it's already too late. Sorry if im missing something obvious that can fix this, however after 3 days of messing with this stuff my brain is starting to blur lol. Ok so here it is:
Tried updating to froyo via the OTA update pushed out recently. That failed and ive tried various ways of getting froyo to install over the last few days using Clockworkmod recovery. I ended up pushing a load of system files onto my phone via adb just to let the updater-script get past assert's. The point is, this was obviously a bad idea as I now have some kind of messed up copy of froyo installed which will not boot up past the HTC splash screen. Problem: the half-cocked update replaced the Clockworkmod recovery with the stock recovery so I now cannot use nandroid to push a backup back onto the phone
To make things worse when I boot into the stock recovery I also can't get into adb/shell, it detects the device but just says offline. Tried a lot of things to get round this but nothing has worked. So as ive got stock recovery and can't seem to get into adb anymore it would appear ive pretty much run out of options unless something can be done with fastboot... I don't know what im doing with that though so any help would be appreciated.
HTC Wildfire T-Mobile UK
S-ON
HBoot - 1.01.0001
Radio - 3.35.20.10
Recovery - Stock
Im at the end of the road here. If anyone has any ideas to try I would be very very grateful, otherwise il have to go see how much T-Mobile wants to repair it
Thanks in advance !

Undeadllama said:
First of all, sorry if this is posted in the wrong place. Im pretty new to all this and don't really know how things work here.
I think im pretty buggered, and im pretty far out of my depth now. Im just posting to see if anything can be done or if it's already too late. Sorry if im missing something obvious that can fix this, however after 3 days of messing with this stuff my brain is starting to blur lol. Ok so here it is:
Tried updating to froyo via the OTA update pushed out recently. That failed and ive tried various ways of getting froyo to install over the last few days using Clockworkmod recovery. I ended up pushing a load of system files onto my phone via adb just to let the updater-script get past assert's. The point is, this was obviously a bad idea as I now have some kind of messed up copy of froyo installed which will not boot up past the HTC splash screen. Problem: the half-cocked update replaced the Clockworkmod recovery with the stock recovery so I now cannot use nandroid to push a backup back onto the phone
To make things worse when I boot into the stock recovery I also can't get into adb/shell, it detects the device but just says offline. Tried a lot of things to get round this but nothing has worked. So as ive got stock recovery and can't seem to get into adb anymore it would appear ive pretty much run out of options unless something can be done with fastboot... I don't know what im doing with that though so any help would be appreciated.
HTC Wildfire T-Mobile UK
S-ON
HBoot - 1.01.0001
Radio - 3.35.20.10
Recovery - Stock
Im at the end of the road here. If anyone has any ideas to try I would be very very grateful, otherwise il have to go see how much T-Mobile wants to repair it
Thanks in advance !
Click to expand...
Click to collapse
You'll need a goldcard and an RUU. Look up how to make a goldcard and let me know when you have one

Wow, thanks for the quick reply
I did try creating a goldcard yesterday (using android.modaco.com/content/software/308798/pc-application-goldcardtool/). So assume I DO have one for the time being...
however if it doesn't work and I need to create a new goldcard:
Since I can't get into adb or boot up android and therefore can't access my sd card through my phone I presume il have to go out and buy a cheap card reader tomorrow.
Also, I have to run this command again:
adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid
But if I can't get into adb how would I go about doing this, can I get the CID of the sd card from a card reader?
As for the RUU, there's many to choose from on shipped-roms.com, does this sound about right?
RUU_Buzz_TMO_UK_1.14.110.1_Radio_13.45.55.24_3.35.15.19_release_130442_signed.exe
Thank you so much for your help.

This this a decent guide from Paul over at MoDaCo.

Ok disregard my last post about a card reader... I managed to borrow a friends android phone since it appears goldcard's are specific to the sd card, not the phone. So after following the instructions I now definitely have a goldcard.
Also have the RUU mentioned in the previous post.
RUU_Buzz_TMO_UK_1.14.110.1_Radio_13.45.55.24_3.35. 15.19_release_130442_signed.exe
Is this right, and what do I do with these now to get them on my phone? Ive tried running the RUU whilst in Hboot and in recovery but it wont recognise my phone, presumably because adb isn't working.
Thanks again for the help.

There is another way to do it when it can only get into hboot. I'll look today for the method and let you know.
Sent from my HTC Wildfire using XDA App

Ah I did manage to get round it in the end. Using the PC49IMG.zip hboot method. Tried pulling the rom.zip from the temporary files that are made when running the 1.14.110.1 RUU. But obviously as I had a newer hboot or bootloader or whatever it was and it wouldn't let me downgrade back to this version. So I went for the newest one, 2.22.405.1 I think it was. With that in the root of the sdcard everything was up and running again after it had finished installing over the top of the messed up system.
Only worked because T-Mobile's OTA was a slightly older version 2.21.110.2, thank god there was a newer version available on the interwebs.
Probably not the best way of doing it but im just glad ive got a working phone again.
Thanks for replying though.
Just on a side note... its bloody ridiculous that its so hard to downgrade android!!! It causes people like me, who don't really know what they're doing, large quantities of banging-head-against-wall sessions

Undeadllama said:
Ah I did manage to get round it in the end. Using the PC49IMG.zip hboot method. Tried pulling the rom.zip from the temporary files that are made when running the 1.14.110.1 RUU. But obviously as I had a newer hboot or bootloader or whatever it was and it wouldn't let me downgrade back to this version. So I went for the newest one, 2.22.405.1 I think it was. With that in the root of the sdcard everything was up and running again after it had finished installing over the top of the messed up system.
Only worked because T-Mobile's OTA was a slightly older version 2.21.110.2, thank god there was a newer version available on the interwebs.
Probably not the best way of doing it but im just glad ive got a working phone again.
Thanks for replying though.
Just on a side note... its bloody ridiculous that its so hard to downgrade android!!! It causes people like me, who don't really know what they're doing, large quantities of banging-head-against-wall sessions
Click to expand...
Click to collapse
Yeah that's the method I was going to suggest, glad you sorted it out.
It's the fact that they lock out fastboot and stuff. If we had S-OFF from the factory, fixing these things would be so much easier

Hi,
how were you able to do this?
"Ah I did manage to get round it in the end. Using the PC49IMG.zip hboot method. Tried pulling the rom.zip from the temporary files that are made when running the 1.14.110.1 RUU. But obviously as I had a newer hboot or bootloader or whatever it was and it wouldn't let me downgrade back to this version. So I went for the newest one, 2.22.405.1 I think it was. With that in the root of the sdcard everything was up and running again after it had finished installing over the top of the messed up system. "
Thanks

[Q] Unroot for Warranty Repair

I need to send my Mytouch 4g in for repair due to an issue with "limited service" problems. Both T-Mobile and HTC said it is a rare problem and it needs to come in for repair.
My problem is that my phone is/has been rooted. I need to COMPLETELY UNROOT it before sending it in, or they will not repair/replace.
What can I do to completely unroot so they will not know that it was ever rooted?
I have run the unlockr method with the PD15IMG but Im not sure that is it. What else can do to see that it was rooted? Is there anything other than info in the bootloader? I turned the S-On again.
PS - the issue with my phone is when i put in my SIM card (under any rom, including stock) it comes back with a message saying "limited service" and i cannot do anything to fix it. If you have an answer for this too, that would be helpful.
Either way I dont want to lost this phone due to root/warranty problems.
Thanks ahead of time....

How did you root it? Did you use gfree and simunlock? Did you flash engineering hboot? Did you S-OFF? Did you flash custom images?
There are a lot of questions to answer in what to undo.
If you SIM/Super CID unlocked and radio S-OFF with gfree then you need to follow the instructions in the gfree thread on how to restore your part7 backup.
If you flashed the engineering hboot, again, follow info in the gfree thread on how to flash it back to stock.
Once you are back to normal hboot and S-ON, just loading the PD15IMG for the complete OTA (find the thread in the dev section) will factory wipe and clear the rest for you.

Thanks for the quick reply. I followed the unlockr method completely to gain root.
theunlockr.com/2010/12/10/how-to-gain-permanent-root-and-s-off-on-the-t-mobile-mytouch-4g-htc-glacier/
Then I installed Iced Glacier.
I also did their unroot method which includes flashing the PD15IMG and turning the S-On. Normally, should I receive an OTA after flashing this? Or is this THE updated image?
If is should expect an OTA, I will not get it. The reason i need to send the phone in is because i do not get service with the SIM card in. It reads "Limited service" "Emergency Calls Only". In this case, i would not recieve an OTA. Is there anything else I can do?
Thanks again.

http://forum.xda-developers.com/showthread.php?t=858996
Scroll down to "follow these steps to restore stock hboot (0.86.0000) and flash that back on if you have not already.
If you flashed the PD15IMG from this thread then it already has the OTA updated applied and you should be g2g.

Thank you very much. That is a huge help.
After updating the HBoot and flashing the PD15IMG we should be back to stock.
Is there any way after that HTC will see it as previously rooted?
I thought to myself that the hackers were smarter than the developers.... Im glad I was right.
Thanks again.
Sent from my HTC Glacier using XDA App

pnut22r said:
Is there any way after that HTC will see it as previously rooted?
Click to expand...
Click to collapse
With S-ON, a stock hboot, and a fresh flash of the OTA image -- no, not to my knowledge.

Ok so I am expecting to receive a replacement for the BAD SCREEN (inferior) issue. So preparing to get my phone to STOCK condition.
--------PRESENT STATE----------
Rooted - using http://forum.xda-developers.com/showthread.php?t=858021
S=OFF
Radio - 26.09.04.26
ROM - Nexus AOSP 1.2.7
Recovery - 3.0.2.4
----------STOCK STATE------------
Unroot - http://forum.xda-developers.com/showthread.php?t=924923
S=ON
Radio - 26.03.02.26 http://forum.xda-developers.com/showthread.php?t=1059347
Recovery - ????
Now I kind of know where I need to be at but I am not sure of the sequence of the steps. Also, how do I get back to stock recovery from Clockwork?
Is there a good check list of things to make sure before sending back the old phone?
thanks a lot.

for unroot
download stock rom from here http://forum.xda-developers.com/showthread.php?t=901477
rename it PD15IMG.zip and put it in the root of your sdcard not in a folder
go into hboot by powering off then hold VOL DOWN+POWER
then it will automatically check to find PD15IMG.zip when it ask for update click yes
wait for it to install done stock unroot

Thanks for your reponse. I was aware of that method and was planning on using it. Does that also take care of clockwork recovery and updated radio?

HTC Desire HD 2.3 update problem

Hi,
I'm in the UK and had the 2.3 update notification a couple hours ago. I have downloaded it and after clicking install I get an exclamation mark with a green Android robot on my screen and nothing happens.
Anyone else getting this?
Just some background info. I have stock Sense Android 2.2 which I have used Visionary to perm root with S-OFF. I have used Visionary to unroot and used the app called Root Checker to see if I am rooted and it says I am not rooted.
Do I need to get S-OFF back on aswell and if so how?
Sent from my Desire HD using XDA App

ToneyEricsson said:
Hi,
I'm in the UK and had the 2.3 update notification a couple hours ago. I have downloaded it and after clicking install I get an exclamation mark with a green Android robot on my screen and nothing happens.
Anyone else getting this?
Just some background info. I have stock Sense Android 2.2 which I have used Visionary to perm root with S-OFF. I have used Visionary to unroot and used the app called Root Checker to see if I am rooted and it says I am not rooted.
Do I need to get S-OFF back on aswell and if so how?
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Do you have a recovery?, i dont know if this would work but it did work for me before, have you tried flashing it within the recovery?

I haven't no I was recommended to follow these instructions to get rooted and S-OFF to get apps like Adfree etc working
http://forum.xda-developers.com/showthread.php?t=857537
I have undone Visionary so I am not rooted anymore but the 2.3 update wont install.
Would this be because of S-OFF still being off do you think and needs to go back on?

ToneyEricsson said:
I haven't no I was recommended to follow these instructions to get rooted and S-OFF to get apps like Adfree etc working
http://forum.xda-developers.com/showthread.php?t=857537
I have undone Visionary so I am not rooted anymore but the 2.3 update wont install.
Would this be because of S-OFF still being off do you think and needs to go back on?
Click to expand...
Click to collapse
Yeah you would need S-OFF to be not off to install updates the normal way

cashisback, you are wrong. S-OFF does not matter. Get the official 2.36.405.8 RUU from the dev subforum and install it.

It is because you remove some preinstalled apps such as Amazon MP3,News etc. I did it myself and i had to reinstall stock RUU.and then it worked. It worked even with S-OFF. I still have S-OFF after update. Good Luck.

I haven't uninstalled any preinstalled apps.
All I have done is simply following those instructions to get rooted with Visionary and S-OFF so apps like Adfree, Drocap2 etc to work.
So instead of getting the OTA over wifi I have to now flash to a stock RUU? I haven't even flashed an RUU before, any help with that would be good.

jkoljo said:
cashisback, you are wrong. S-OFF does not matter. Get the official 2.36.405.8 RUU from the dev subforum and install it.
Click to expand...
Click to collapse
@jkoljo I have a stock RUU on my phone, can I not just do the latter part of these instructions?
http://forum.xda-developers.com/showthread.php?t=857537
To go back to S-ON:
Temproot using Visionary
Use my tool, do Stock CID and S-ON (enter brand CID if you had a branded device, see second post)
Enjoy your factory-state phone
And then update to 2.3 via OTA?
Edit: I tried it, it doesnt seem to be possible to get S-OFF back on using the tool?

Thanks for making me aware of this thread, OP!
My phone is ENG/S OFF and I'm using the stock rom. I'm quite certain that I haven't uninstalled any stock apps so I don't think that's related.
Regarding S-OFF: If this was the cause (and I cannot really see how it could be - but I'm at most a layman at this), there would be many more users getting this error, right?
Just to add what I've written in the main 2.3 update thread:
When entering CWM I get this error message regarding the OTA update:
Code:
ClockworkMod Recovery v3.0.0.6
Finding update package...
E:unknown volume for path [SDCARD:download/OTA_Ace_....zip]
E:Can't mount SDCARD:download/OTA_Ace_....zip
Installation aborted.
I've abbreviated the name of the file. It might be/is a stupid idea but... might the file name be too long (90 characters) for some weird format of my/our SD card? Rights: drw, format should be FAT32 - any idea how to check this on the phone?
Sorry for probably not making much sense

ToneyEricsson said:
@jkoljo I have a stock RUU on my phone, can I not just do the latter part of these instructions?
Click to expand...
Click to collapse
Keep S-OFF, trust me, you will not regret it.
baum01 said:
ClockworkMod Recovery v3.0.0.6
Finding update package...
E:unknown volume for path [SDCARD:download/OTA_Ace_....zip]
)
Click to expand...
Click to collapse
You cannot flash OTA in clockworkmod, come on..
Make sure that you have Radio S-OFF and then use Gingerbread RUU.

@jkoljo I see your point obviously still will be able to get rooted apps working in 2.3.
But I'm complete new to all this flashing RUU stuff.
Which thread is this RUU that I need and how do you flash the DHD?
The HTC Desire HD I have is unlocked sim free and I am in the UK if that makes any difference. My current software version is the 1.32.405.6 one which I think is the world wide version.

jkoljo said:
You cannot flash OTA in clockworkmod, come on..
Make sure that you have Radio S-OFF and then use Gingerbread RUU.
Click to expand...
Click to collapse
Then you will imagine my surprise when after pressing the power button briefly (while the triangle was shown) CWM was shown. Is it possible that I have to 'deactivate' it for the OTA to install itself?
(I'm currently running 1.72.405.3)

I am currently in the same boat as you same error as well.

Thanks for pointing me this way same issue here. If I'd have known it was gonna cause FOTA issues I wouldn't have bothered with root as I only wanted it for root explorer to regain the standard lock screen and thought that I'd do the Radio S-OFF and and SUPERCID in case HTC didn't live up to their word.
Chuffin annoying to say the least.

i keep getting the signature verification failure

Anyone know how to get passed this verification error? Thats what I'm having too. Click install update and on reboot theres an exclamation mark which stays there.

I've updated CWM to the latest version and tried the OTA installation again. Same triangle error after reboot, no option to get to the CWM screen and only the removal of the battery helped to restart the phone. This probably doesn't help but I thought to let you know.
I'd have used the RUU already (or another ROM) but I'm a bit hesitant of having to reconfigure my device completely again. Besides, there should be an easy solution for this problem. There always is
Sent from my Desire HD using XDA App

thanks for pointing this whole thread
i'm in Australia, and have Desire HD by Vodafone, and all i have done is permroot with visionary in order to have superuser access to be able to run Samba server on my phone.
OTA update by Vodafone is still not avail, but I wonder now, if I will be facing any kind of problem while updating ?? (p.s. only super user access is taken and only visionary was used, phone still has stock rom and no modifications)

Just so everyone is aware if having this problem. I flashed my DHD with the stock 1.32 the same as what was originally on my DHD and then was able to get the 2.3 update without any problem which I currently am on.
Alternative if you still want root and S-OFF probably be worth flashing with the leaked Gingerbread ROM from 1.32 with root and S-OFF already done. I may try this, does anyone know if there is a .zip of it so can flash from SD card?
Sent from my Desire HD using XDA App

Same issue on Vodacom South Africa DHD.
Standard install of 2.3 update shows the exclamation mark / droid image.
Booting into ClockworkMod and manually applying the update.zip file yields
====================
E:Can't open /sdcard/update.zip
(No such file or directory)
Installation aborted
====================
DHD has been rooted a while back, installed CyanogenMod, reverted to backup ROM.
Running ClockworkMod Recovery 3.0.2.6

What does this mean exactly?

PermROOT said:
Hello Phateless do you remember me? lol I am always on diff name so ya.
But yes PD15IMG.zip is not the golden solution to everything. It all depends on how you originally rooted your MT4G as VISIONary+ (TempROOT) and root.sh (PermROOT). In that case your S=OFF security off flag is dependent on the eng hboot which was pushed to /dev/block/mmcblk0p18 during PermROOT.
Now since its not true security off once you have newer radio. You try to run PD15IMG.zip (Sense 2.2.1 Rom/Radio 26.03.02.26_M) after the first update which is stock hboot you would be locked due to it changing S=ON thus on next step it will fail due to the image being older than originally on which is currently flashed which would be the radio. In this case your in a point where you shouldn't be as you can be locked out and no way to reroot. which I am working on finding. This also goes for gfree radio s=off.
If you do want to go back download PD15IMG.zip (stock radio 26.03.02.26_M) and then flash it once that is done then you can revert back to stock rom/radio using standard PD15IMG.zip (Sense 2.2.1 Rom/Radio 26.03.02.26_M). Keep in mind unless the new PD15IMG.zip is out you can't revert it back if your locked out due to source being outdated than current image.
Click to expand...
Click to collapse
--------------------------
Found this post here in THE Bible. Trying to understand exactly what it means.
What is he saying here?
Can someone put this into noob terms please?
THANK!!!

I am not sure how to explain it furthermore as when I posted that it was clear to everyone, but ill try to simplify.
The original stock rom that came with our device was 2.2.1S and later we had GB2.3.X port and we mostly switched. Then came the radio rom which I hope I don't need to explain what the image does. So the standard stock radio that came with our device was 26.03.02.26_M. So later on as Panache came out we had leak to other radios which user could flash, thus changing it from stock radio to leaked radio. I hope it make sense up to there.
Now keep in mind we have 2 type of root meth as one is via TempROOT/PermROOT as I explained before via VISIONary+ which just push the eng_hboot and gives the illusion of S=OFF but the true security is not off as that is only done if you do the other rooting meth which is PermaROOT which disables the radio security completely.
Now the problem few users faced was when they flashed the leaked radio and they wanted to revert back to stock rom/radio via PD15IMG.zip for our MT4G (IDD15000). The installation would fail only for folks who had root via PermROOT as they never had true S=OFF thus once the eng_hboot is replaced with stock bootloader the security is disabled thus user can't complete the second part of the process which would be flashing the radio. So only solution was that they first revert back to stock radio or wait for newer radio because the source of the image inside PD15IMG.zip was older than the radio.img that was already flashed inside user's MT4G.
I hope it explains if not well IDK how to explain any better man :O

So if I'm understanding this all correctly, how I find out if this will affect me?
Where and what information should I provide you in order to find out if this will happen to me as well.
I'm getting ready to send my phone in for an exchange and was looking to flash PD15IMG.zip before doing this when I came across this post.
I rooted my phone with Visionary R14 and Terminal Emulator.
What other info do you need? Please let me know. Thank you.

At this point it wont affect you as thats obsolete due to TMoUS releasing newer stock rom/radio for our MT4G few months ago as Panache radio leak is older than the current stock rom/radio. As its GB2.3.4S which comes with the newest radio which is newer than any radio you flash. So the source of the PD15IMG.zip if you have the newest one then it will always be newer or equal to the radio.img already in device and it means in simple term it will flash the 2nd part. I hope it make sense as it should not affect anyone now. Even if it does all they have to do is run the current new PD15IMG.zip and it will fix the issue which user faced few months back.

nguyendqh said:
So if I'm understanding this all correctly, how I find out if this will affect me?
Where and what information should I provide you in order to find out if this will happen to me as well.
I'm getting ready to send my phone in for an exchange and was looking to flash PD15IMG.zip before doing this when I came across this post.
I rooted my phone with Visionary R14 and Terminal Emulator.
What other info do you need? Please let me know. Thank you.
Click to expand...
Click to collapse
If this is all about going back for an exchange, i recently did just this. Please see my post on the topic: http://forum.xda-developers.com/showthread.php?t=1241740
If all you did was the temproot/permaroot method via visionary+, and not the gfree method (gfree is actual s=off), then I believe some of the steps may be different. Specifically, you may be able to skip the whole bit about turning s=on again.
So which is it?

So rooted via Visionary R14 and being on Virtuous Unity (newest update)
I should be able to flash PD15IMG.zip from this link here: http://forum.xda-developers.com/showthread.php?t=863899
and have no problems yeah?
Sorry for all the questions. But yeah I'm only half to 75% following what you're saying.
I'm not advanced yet. =(
Thanks for the help again though.

Keep in mind PD15IMG.zip is the default system file for our device which is checked on the bootloader as our device ID is PD15000 thus getting the PD15IMG name. So PD15IMG.zip can be multi files as we have 2 of them 1 is 2.2.1 and newest one is 2.3.4 just look in the dev section you will find the newest PD15IMG.
http://forum.xda-developers.com/showthread.php?t=1059347
NEW-PD15IMG: PD15IMG_Glacier_Gingerbread_S_TMOUS_2.19.531.1_Radio_12.58.60.25_26.11.04.03_M_release_200756_signed

nicholasb said:
If this is all about going back for an exchange, i recently did just this. Please see my post on the topic: http://forum.xda-developers.com/showthread.php?t=1241740
If all you did was the temproot/permaroot method via visionary+, and not the gfree method (gfree is actual s=off), then I believe some of the steps may be different. Specifically, you may be able to skip the whole bit about turning s=on again.
So which is it?
Click to expand...
Click to collapse
I did not use the gfree method.

AggNA said:
Keep in mind PD15IMG.zip is the default system file for our device which is checked on the bootloader as our device ID is PD15000 thus getting the PD15IMG name. So PD15IMG.zip can be multi files as we have 2 of them 1 is 2.2.1 and newest one is 2.3.4 just look in the dev section you will find the newest PD15IMG.
http://forum.xda-developers.com/showthread.php?t=1059347
NEW-PD15IMG: PD15IMG_Glacier_Gingerbread_S_TMOUS_2.19.531.1_Radio_12.58.60.25_26.11.04.03_M_release_200756_signed
Click to expand...
Click to collapse
Thanks for all the help bro. I really really appreciate it.
Love all the help that the XDA community provides.

this guy definitely knows what he's talking about, provided help for me in the past

[Q] Need to unroot froyo 2.2

I have looked and looked but probably not in the right places... I have a rooted Evo 4G with froyo 2.2. I used unrevoked forever and know how to get the s-on back... I just would like to update the phone to the newest update and root it again. Is it still necessary to get s-on back then load the original ruu rom? I would think I just need to remove the unrevoked then update. The phone works I just want newer firmware on it... My apologies if I did not look for my response properly, but all I see is a reload the IMG file... I dont want to set back to factory... just wanted to post this question. Thank You

Mee2 said:
I have looked and looked but probably not in the right places... I have a rooted Evo 4G with froyo 2.2. I used unrevoked forever and know how to get the s-on back... I just would like to update the phone to the newest update and root it again. Is it still necessary to get s-on back then load the original ruu rom? I would think I just need to remove the unrevoked then update. The phone works I just want newer firmware on it... My apologies if I did not look for my response properly, but all I see is a reload the IMG file... I dont want to set back to factory... just wanted to post this question. Thank You
Click to expand...
Click to collapse
There is absolutely no reason to unroot. All you have to do is flash a custom stock ROM based on the newest firmware. A whole bunch are available for flashing in the Development forum.

It is much easier to leave the phone S-OFF and then either flash a rooted stock ROM or run a stock RUU. Then all you would need to do to obtain full root again (with stock ROM) would be to install a custom recovery and then flash a superuser.zip file, rather than turning the phone back S-ON and then going through a potentially complicated procedure just to reroot and possibly turn the phone back S-OFF.

Thank You guys sounds like a custom rom is the way to go... it would get rid of that IQAgent also... I'll look around for a nice looking rooted rom.