Related
Hi, I need to return my evo but I have s-off using unrevoked forever. I ran the latest s-0n tool through recovery (latest Clockwork) and it appears that everything went ok when looking at the log as the s-on ran. But now when I verify it still says S-off. Can anyone assist?
radio 2.15.00.11.19
clavin78 said:
Hi, I need to return my evo but I have s-off using unrevoked forever. I ran the latest s-0n tool through recovery (latest Clockwork) and it appears that everything went ok when looking at the log as the s-on ran. But now when I verify it still says S-off. Can anyone assist?
radio 2.15.00.11.19
Click to expand...
Click to collapse
Run the son tool from the unrevoked site
iitreatedii said:
Run the son tool from the unrevoked site
Click to expand...
Click to collapse
I did, I downloaded the latest s-on tool
See if THIS helps...
Thanks for the link. Ran the s-on about 20 times and still s-off. Guess I'm bringing it in s-0ff and chancing it. Hopfully they don't need to replace and can just fix my power button without ever needing to see the s-off
damn you even flashed the pc36img in bootloader and you still cant get s-on? huh... Hopefully it all works out for ya! Goodluck man
You need to run the ruu after flashing s on zip
Sent from my PC36100 using XDA App
Instructions said s-on first then the other zip so i didn't want to run the other one until it said s-on. Thanks guys
clavin78 said:
Instructions said s-on first then the other zip so i didn't want to run the other one until it said s-on. Thanks guys
Click to expand...
Click to collapse
Sorry I thought you I'd thought my fault for the assumption
Jo
clavin78 said:
Instructions said s-on first then the other zip so i didn't want to run the other one until it said s-on. Thanks guys
Click to expand...
Click to collapse
Yup, s on first. I'm not sure why its not taking. Maybe download it again, and possibly use a different recovery to try flashing it? Try using rom manager to flash Among RA, then try again.
Sent from my PC36100 using XDA App
I'm not sure, but I think after running s-ON and then the RUU, it'll show up as S-On.
I know it did when I ran RUU last week, after running the S-On tool, but tbh, I didn't check before running the RUU.
HipKat said:
I'm not sure, but I think after running s-ON and then the RUU, it'll show up as S-On.
I know it did when I ran RUU last week, after running the S-On tool, but tbh, I didn't check before running the RUU.
Click to expand...
Click to collapse
You do want to be sure that the s on tool works. The RUU wont turn s on if you've used unrevoked forever. You'll end up stock, s off, and no recovery to flash the s on tool.
Sent from my PC36100 using XDA App
k2buckley said:
You do want to be sure that the s on tool works. The RUU wont turn s on if you've used unrevoked forever. You'll end up stock, s off, and no recovery to flash the s on tool.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Exactly what I was thinking so I got a zip of my recovery from the unrevoked site to run from hboot since I still had s-off which would allow me to run the zip just incase. I would be able to get a recovery again if running the stock image didn't help.
Anyway, I ran the PC36IMG image with S-off and noticed that when going though the install the HBOOT section installed, installation stopped then just went back to HBOOT where it inspected the PC36IMG again. Noticed right when that happened that it was back to S-ON. Current HBOOT is 93, not sure if it was different before and needed to be on 93.
If your hboot is version .76 it is s-off by default. No need to use unrevoked for anything.
Sent from my PC36100 using XDA Premium App
I'm trying to root my brothers Evo again and running into some problems.
Back story: I had rooted his device with Revolutionary and he was running CM7 just fine. He started to have troubles with his screen so we unrooted it and got S-ON back. He took his phone to Sprint and instead of replacing the device, they decided to just replace the screen on it.
Current story: Downloaded Revolutionary and ran it and got this;
Code:
=============================================
| Revolutionary S-OFF & Recovery Tool 0.4pre4 |
=============================================
Brought to you by AlphaRev & unrEVOked.
Waiting for device...
Found your device: PC36100 (supersonic-6.17.0001, Android: 2.3.3, ROM version: 4.53.651.1)
Your device is already S-OFF, what exactly do you think you're doing? Not setting S-OFF.
Do you want to download (Internet connection required) and flash ClockworkMod Recovery? [Y/ny
Downloading recovery for your phone (supersonic)...Done.
Rebooting to fastboot...
Flashing recovery over fastboot...INFOsignature checking...
FAILED. Unable to flash recovery. Please download custom recovery yourself and flash it over fastboot.
So here I am with the HBOOT saying that S-ON and Revolutionary telling me it's off and won't turn it off.
Not sure where to go from here!?
Thanks!
When it tells you that your Device is already S-OFF, you should have an option to turn it off regardless.
If that doesn't work, I guess you could try and use another method to do it.
and if THOSE don't work, I guess you could just sbf flash it it
I don't have an option to turn it off regardless.. it finds the device and logs the fact it thinks S-OFF is present and asks to download the recovery.
I thought revolutionary was the only option for HBOOT 1.6 at this point. Is this incorrect?
Also what do you mean by sbf flash it?
DruKe said:
I don't have an option to turn it off regardless.. it finds the device and logs the fact it thinks S-OFF is present and asks to download the recovery.
I thought revolutionary was the only option for HBOOT 1.6 at this point. Is this incorrect?
Also what do you mean by sbf flash it?
Click to expand...
Click to collapse
You didn't do the last step after getting S-ON, which is flashing a stock ROM. Because of your HBOOT version, Revolutionary thinks you're already S-OFF. You need to flash a stock ROM to normalize your HBOOT version, and then Revolutionary will work.
He cannot flash a stock ROM if he is S-ON. Sbf basically resets everything on your phone back to its "out of the box" state
@Druke, can you get to recovery? If there is no recovery you may want to RUU back to 4.54 then try revolutionary again. Or just go through the un-rooting steps again.
imheroldman said:
@Druke, can you get to recovery? If there is no recovery you may want to RUU back to 4.54 then try revolutionary again. Or just go through the un-rooting steps again.
Click to expand...
Click to collapse
Just remember to not do any updates after RUU'ing back to 4.54! Then you'll have to use other methods to unlock and revert. Good luck.
Flowsick said:
He cannot flash a stock ROM if he is S-ON.
Click to expand...
Click to collapse
This is incorrect. You can flash a signed HTC stock ROM in PC36IMG format (or RUU on a PC for that matter) just fine. As I said, that's the last necessary step to returning the device to stock conditions. Trust me, I've done it probably almost 100 times.
P.S. Since I'm the one that came up with the unrooting method that was used, I would know .
I did try an RUU yes. I will need to try an RUU again. The one I used must have been unsigned or unofficial somehow. Anyone help me out? With the megaupload thing it seems all the links around here have dried up. Thanks!
Sent from my PC36100 using XDA App
DruKe said:
I did try an RUU yes. I will need to try an RUU again. The one I used must have been unsigned or unofficial somehow. Anyone help me out? With the megaupload thing it seems all the links around here have dried up. Thanks!
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
The unrooting Revolutionary root link in my sig has links to some PC36IMG zips that can be flashed in bootloader.
I recommend the 4.54 version. Sometimes it won't work if you're using a version that's too old, or if your SD card isn't a high capacity card or got corrupted somehow.
Captain_Throwback said:
The unrooting Revolutionary root link in my sig has links to some PC36IMG zips that can be flashed in bootloader.
I recommend the 4.54 version. Sometimes it won't work if you're using a version that's too old, or if your SD card isn't a high capacity card or got corrupted somehow.
Click to expand...
Click to collapse
4.54 RUU or PC36IMG is the most likely to work, however, 4.24 and 4.53 contain the same HBOOT needed for Revolutionary to work again as well.
Sent from my PC36100 using XDA Premium App
shortydoggg said:
4.54 RUU or PC36IMG is the most likely to work, however, 4.24 and 4.53 contain the same HBOOT needed for Revolutionary to work again as well.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Of course, but my recommendation was referring to the ones posted in the link .
I tried grabbing the 4.54 version from you post however the link to it is dead.
Got dropbox?
DruKe said:
I tried grabbing the 4.54 version from you post however the link to it is dead.
Got dropbox?
Click to expand...
Click to collapse
It shouldn't be - I refreshed those links earlier today and changed them to 4shared. When did you last try?
So weird.. works now! Thanks a ton! I'll give it a shot this weekend. Hopefully everything goes aces!
Thanks again.
Hi everyone, ive been tryin to find a way to unroot my evo so i can take it into sprint. Im currently running MIUI 2.7.6, hboot version 2.18, unlocked. Would really like to put everything back to normal or as close to it as possible. Any help would be great!
Sent from my HTC Evo 4G using xda app-developers app
younginferlife said:
Hi everyone, ive been tryin to find a way to unroot my evo so i can take it into sprint. Im currently running MIUI 2.7.6, hboot version 2.18, unlocked. Would really like to put everything back to normal or as close to it as possible. Any help would be great!
Sent from my HTC Evo 4G using xda app-developers app
Click to expand...
Click to collapse
http://androidforums.com/evo-4g-all...gerbread-2-3-5-dummies-guide.html#post3847623
See the "Unrooting" section.
I was just looking at that method but was unsure if it woild work. I forgot to mention in the beginning of this, that i have tried to use 3 different pc36img files and everytime it said error, main is newer or somethimg like that. But thanks, i will give that method a shot right now and let ya kno how it goes
Sent from my HTC Evo 4G using xda app-developers app
younginferlife said:
I was just looking at that method but was unsure if it woild work. I forgot to mention in the beginning of this, that i have tried to use 3 different pc36img files and everytime it said error, main is newer or somethimg like that. But thanks, i will give that method a shot right now and let ya kno how it goes
Sent from my HTC Evo 4G using xda app-developers app
Click to expand...
Click to collapse
Well the first thing you have to do in the unrooting procedure is downgrade the misc partition so you don't get that message . It's all outlined there nicely, and if you have any questions, it might be easier for you to post over there - they're all very helpful .
Captain_Throwback said:
Well the first thing you have to do in the unrooting procedure is downgrade the misc partition so you don't get that message . It's all outlined there nicely, and if you have any questions, it might be easier for you to post over there - they're all very helpful .
Click to expand...
Click to collapse
Thanks again for the help. Everything went good with achieving the "locked oow" but the only problem im presenting is being able to flash the pc36img file due to the fact that i have to press up in order to update. My volume up button is broken (second time with in a month) which is why im taking my phone into sprint. Im downloading and RUU from rootzwiki to see if im able to flash back to the stock unrooted rom from there or by recovery. Thanks again.
younginferlife said:
Thanks again for the help. Everything went good with achieving the "locked oow" but the only problem im presenting is being able to flash the pc36img file due to the fact that i have to press up in order to update. My volume up button is broken (second time with in a month) which is why im taking my phone into sprint. Im downloading and RUU from rootzwiki to see if im able to flash back to the stock unrooted rom from there or by recovery. Thanks again.
Click to expand...
Click to collapse
If you do an "adb reboot bootloader", and then run the RUU from your PC, you shouldn't have to press any buttons on the device.
Captain_Throwback said:
If you do an "adb reboot bootloader", and then run the RUU from your PC, you shouldn't have to press any buttons on the device.
Click to expand...
Click to collapse
call me a pain or even a noob (cause i am), but i have been trying to run the ruu from pc but seem to be having issues. would you mind posting the proper commands to run?:good::silly:
younginferlife said:
call me a pain or even a noob (cause i am), but i have been trying to run the ruu from pc but seem to be having issues. would you mind posting the proper commands to run?:good::silly:
Click to expand...
Click to collapse
There are no commands to run an RUU from the PC - you just double-click it.
Thats where my problem was, the "RUU" I downloaded from the first thread you mentioned was in .zip format not .exe but all is good now, fully unrooted and back to original crappy malfunctioning 2.3.5 :thumbdown: thanks again for your help and puttin up with my noobness :thumbup:
Sent from my PC36100 using xda app-developers app
hey guys i had to unroot my evo with the unrooting method mentioned above, but i messed up and flashed the s-on and flashed an RUU b4 downgrading the misc partition. The phone also installed the 5.07 OTA with the stock recovery. The phone says it has "s-on" but the hboot is 6.17 and i cannot get it to update back to 2.18, everytime i try to RUU again, i get a error 140 saying bootloader version error. I tried to root again using revolutionary and i get told that the s is already off and get asked to install a custom recovery and that fails every time. i tried to install amon ra via pc36img method in bootloader and it does nothing. i tried using unrevoked since my phone says its hboot 2.16 and unrevoked fails and says my firmware is too new. I tried using htc dev to achieve root again and the cmd gives me an error every time i try to get the code from my phone. i made a booboo and i cant root nor update and i gotta return my phone to sprint since i upgraded my phone to a diff phone. Any ideas guys?
Synergies14 said:
hey guys i had to unroot my evo with the unrooting method mentioned above, but i messed up and flashed the s-on and flashed an RUU b4 downgrading the misc partition. The phone also installed the 5.07 OTA with the stock recovery. The phone says it has "s-on" but the hboot is 6.17 and i cannot get it to update back to 2.18, everytime i try to RUU again, i get a error 140 saying bootloader version error. I tried to root again using revolutionary and i get told that the s is already off and get asked to install a custom recovery and that fails every time. i tried to install amon ra via pc36img method in bootloader and it does nothing. i tried using unrevoked since my phone says its hboot 2.16 and unrevoked fails and says my firmware is too new. I tried using htc dev to achieve root again and the cmd gives me an error every time i try to get the code from my phone. i made a booboo and i cant root nor update and i gotta return my phone to sprint since i upgraded my phone to a diff phone. Any ideas guys?
Click to expand...
Click to collapse
WHAT?? I'm lost. First you said your Hboot is 6.17, then you said your phone says it has Hboot 2.16.
Sounds like your misc partition is screwed up from the different Hboots that your phone had, especially from the 5.07 OTA. If that's the case, there is no current RUU that will work for that (the 5.07 misc). It's there to prevent you from downgrading. You will need the Tacoroot method in order to downgrade your misc partition so that you can run your RUU again. It will give you a temp root so that you can run adb commands to downgrade that misc partition. It's in the rooting method guide from Captain Throwback's link above.
shortydoggg said:
WHAT?? I'm lost. First you said your Hboot is 6.17, then you said your phone says it has Hboot 2.16.
Sounds like your misc partition is screwed up from the different Hboots that your phone had, especially from the 5.07 OTA. If that's the case, there is no current RUU that will work for that (the 5.07 misc). It's there to prevent you from downgrading. You will need the Tacoroot method in order to downgrade your misc partition so that you can run your RUU again. It will give you a temp root so that you can run adb commands to downgrade that misc partition. It's in the rooting method guide from Captain Throwback's link above.
Click to expand...
Click to collapse
My apologies, i was in a rush earlier. My hboot is 6.17, not 2.16. I tried unrooting and did for the most part except getting hboot back to 2.18. In this process, the phone forced itself to update to the new 5.07 OTA that there is no RUU for so im screwed to that end. I am currently trying Tacoroot method but am having issues being stuck at the sprint screen bootloop so i cant run the flash_image command from the sdcard (since the phone isnt starting fully for it to be in "charge only mode"). Seems alot of ppl have that same issue but havent found a solution yet. Not sure if i just start over if it bootloops or not. I've tried 3 complete times now and still get stuck on the bootloop.
Ouch, that sucks. If you cannot boot into the operating system, then there might not be anything that you can do.
shortydoggg said:
Ouch, that sucks. If you cannot boot into the operating system, then there might not be anything that you can do.
Click to expand...
Click to collapse
i can boot into the phone, its just when doing the tacoroot method, i cannot get past the step where the phone goes into the loop and you have to enter 3 commands.
Synergies14 said:
i can boot into the phone, its just when doing the tacoroot method, i cannot get past the step where the phone goes into the loop and you have to enter 3 commands.
Click to expand...
Click to collapse
The looping doesn't matter - you should still have adb access, unless you didn't follow the instructions exactly.
2 steps.. rooted/s-off to perfect stock sprint evo 4g unrooted/s-on
younginferlife said:
Hi everyone, ive been tryin to find a way to unroot my evo so i can take it into sprint. Im currently running MIUI 2.7.6, hboot version 2.18, unlocked. Would really like to put everything back to normal or as close to it as possible. Any help would be great!
Sent from my HTC Evo 4G using xda app-developers app
Click to expand...
Click to collapse
i just stumbled over this method.. unrevoked web site has a s-on tool, go to there site ://unrevoked.com/rootwiki/doku.php/public/forever you will see the blah blah blah tutorial.. scroll down until you get down to:
How can this be removed or undone if I need to take my phone in for service?
Download the latest ''S-ON'' tool to a temporary location and follow the installation instructions above to run it. Once your phone is S-ON, you may lose root permanently if you install an official update.. download it to your phone.. recovery mode.. flash from zip.. poof.. S-ON
now head over to htcevohacks, ://htcevohacks.com/htc-evo-hacks/how-to-unroot-your-htc-evo-4g/ get htc update rom utility for your phone.. that erases entire phone and and places sprints latest stock factory rom and everything back on your phone.. do all sprint updates.. and return to sprint and recieve your refurbished motorola photon.. sprint htc evo 4g has been dissed-continued.. oh yeah if you dont do it in that order.. you will loose your root with update utility.. which means you will have to use unrevoked3 to reroot and flash s-on tool .. done the right way its only two steps.. peace out
A while back, my brother's incredible randomly stopped working, he blamed me for rooting and s-offing it, and moved on to the iphone world.
Today, I decided to give fixing it a go, and I think I have made it worse...
Before, I couldn't boot into recovery or the system, but fastboot and hboot were working fine.
Then, I decided to try this (http://forum.xda-developers.com/showthread.php?t=1031752).
It finished successfully, and the incredible rebooted to the white incredible screen.
Then, it goes into the software update screen for a second or two and finally bootloops all over again.
csmcdem said:
A while back, my brother's incredible randomly stopped working, he blamed me for rooting and s-offing it, and moved on to the iphone world.
Today, I decided to give fixing it a go, and I think I have made it worse...
Before, I couldn't boot into recovery or the system, but fastboot and hboot were working fine.
Then, I decided to try this (http://forum.xda-developers.com/showthread.php?t=1031752).
It finished successfully, and the incredible rebooted to the white incredible screen.
Then, it goes into the software update screen for a second or two and finally bootloops all over again.
Click to expand...
Click to collapse
None of the links in that thread work so im not sure ecactly what you did. I assume it had you flash the eng hboot, fastboot flash some partition img's, and then reflash .92 hboot and do an ruu? If you cant boot, or enter hboot, the phone is bricked.
cmlusco said:
None of the links in that thread work so im not sure ecactly what you did. I assume it had you flash the eng hboot, fastboot flash some partition img's, and then reflash .92 hboot and do an ruu? If you cant boot, or enter hboot, the phone is bricked.
Click to expand...
Click to collapse
It's live on the last page (which you seemed to have downloaded too haha) http://forum.xda-developers.com/showpost.php?p=23011865&postcount=22
As far as I can tell that's what it did. Would a ruu really cause a brick?
Thanks
csmcdem said:
It's live on the last page (which you seemed to have downloaded too haha) http://forum.xda-developers.com/showpost.php?p=23011865&postcount=22
As far as I can tell that's what it did. Would a ruu really cause a brick?
Thanks
Click to expand...
Click to collapse
Yeah thats just the eng hboot i downloaded, no instructions though on what exactly they had you flash. Doing an ruu could possibly brick the phone. A phone usually gets bricked with a bad radio flash, ruus flash a radio, so sometimes things can go wrong. Or it also flashes an hboot so something may have gone wrong there and now there is no working hboot. It may have been some sort of incompatibility between the img's you flashed and the img's in an ruu. What img's did you flash (misc, boot, recovery?), also what ruu did you flash froyo or gb?
cmlusco said:
Yeah thats just the eng hboot i downloaded, no instructions though on what exactly they had you flash. Doing an ruu could possibly brick the phone. A phone usually gets bricked with a bad radio flash, ruus flash a radio, so sometimes things can go wrong. Or it also flashes an hboot so something may have gone wrong there and now there is no working hboot. It may have been some sort of incompatibility between the img's you flashed and the img's in an ruu. What img's did you flash (misc, boot, recovery?), also what ruu did you flash froyo or gb?
Click to expand...
Click to collapse
I flashed clockwork 5.0.2.0 and the misc you recommended here (http://forum.xda-developers.com/showpost.php?p=25522827&postcount=31)
I ran the RUU that was included in the zip. I'm not sure what version it was but i think it gave me the 0.92 hboot, if that means anything.
Does the RUU not flash everything?
Thanks, just trying to understand what went wrong, guessing the final verdict that it's bricked
csmcdem said:
I flashed clockwork 5.0.2.0 and the misc you recommended here (http://forum.xda-developers.com/showpost.php?p=25522827&postcount=31)
I ran the RUU that was included in the zip. I'm not sure what version it was but i think it gave me the 0.92 hboot, if that means anything.
Does the RUU not flash everything?
Thanks, just trying to understand what went wrong, guessing the final verdict that it's bricked
Click to expand...
Click to collapse
Yes the ruu should reflash all partitions. I thought mabey you used the wrong ruu to match the mtd0.img, but if you used the one from that thread it was the correct one.
Yeah if you cant run an ruu, get into hboot, recovery, or boot, then im sad to say the phone is a brick.
cmlusco said:
Yes the ruu should reflash all partitions. I thought mabey you used the wrong ruu to match the mtd0.img, but if you used the one from that thread it was the correct one.
Yeah if you cant run an ruu, get into hboot, recovery, or boot, then im sad to say the phone is a brick.
Click to expand...
Click to collapse
that's what i thought
any idea why the software update screen comes up?
csmcdem said:
that's what i thought
any idea why the software update screen comes up?
Click to expand...
Click to collapse
Mabey since the phone cant boot to the os or hboot, it auto boots to recovery and tries to load an image. Try renaming an ruu to update.zip instead of PB31IMG.zip, place it on the sd card in no folders and see if the phone will try to use it.
Are you able to get adb to work from the splash screen?
cmlusco said:
Mabey since the phone cant boot to the os or hboot, it auto boots to recovery and tries to load an image. Try renaming an ruu to update.zip instead of PB31IMG.zip, place it on the sd card in no folders and see if the phone will try to use it.
Are you able to get adb to work from the splash screen?
Click to expand...
Click to collapse
damn, i tried using the gb stock image found here: http://pvillecomp.com/?page_id=22 to no avail
it reboots too quickly for me to check if adb's working
qualcomm diagnostic mode works, but i doubt that means anything.
i guess this thing's dead
thanks again
Hey I'm just wondering if you checked the MD5 sum of you downloaded RUU?
That sucks the worse part is you lost your brother to iDrone.
Could be a hardware failure probably no way to ever know.
ToyTank said:
Hey I'm just wondering if you checked the MD5 sum of you downloaded RUU?
That sucks the worse part is you lost your brother to iDrone.
Could be a hardware failure probably no way to ever know.
Click to expand...
Click to collapse
yeah, I checked the MD5.
really wanted to play around with JB, while waiting for htc to release the kernel source for my rezound. Too bad :/
Hello,
I have a question that I have been searching for the last several hours for an answer. I currently have 5.10.605.9 stock with the HTC unlock method and rooted using the OneClickRoot_1.1 tool. I am not looking for S-OFF for the time being but if its necessary I'll do it. What I would like to do is remove the CWM 4.0.0.5 Recovery and replace it with the stock recovery that came with the phone. The 5.10.605.9 version has been the only version of Android installed on the phone and this is the version that it came with. Its been a while since I flashed the CWM so I don't remember exactly what guide I used, so I cannot reference that guide. There have been several guides I have come across but none that fit my exact situation or phone so I am kinda leery about following them.
I have spent several hours reading about RUU's and this seems like the easiest way but since I have the HTC unlock I cannot flash the same version I currently have, I have to have a newer version. That is my understanding at least. Is there a RUU available for the latest version, 6.01.605.05?
Since the CWM recovery was just flashed using the command line (if my memory serves me right) is it possible just to extract the recovery from a 5.10.605.9 stock build and flash that using the command line? I have a stock build and I notice a recovery_signed.img file, similar to the cwm-recovery-vivow.img file.
Well that was several questions but if anyone could be of any help it would be greatly appreciated. If its not possible its fine, I'm due for an upgrade soon anyway..... I'm just looking to be able to walk into Verizon and see about possibly getting a replacement, the speaker is starting to sound tinny and I am having and occasional 3G problem.
Thanks!!!
Misc Info
VIVO_W XB SHIP S-ON RL
HBOOT-0.98.0000
RADIO-1.09.01.1111
eMMC-BOOT
Jul 18 2011, 12:39:36
http://forum.xda-developers.com/showthread.php?t=1599767
That will put your phone to stock and.will be able to get replacement. Do not.flash. put on root of SD card and load through bootloader. Works 100% this will put factory recovery also. Very easy
sk842018 said:
http://forum.xda-developers.com/showthread.php?t=1599767
That will put your phone to stock and.will be able to get replacement. Do not.flash. put on root of SD card and load through bootloader. Works 100% this will put factory recovery also. Very easy
Click to expand...
Click to collapse
Thank you for your replay but unfortunately I have tried this post several times in the past, guess I should have mentioned that. However I did tried it again with the same results, "WRONG ZIPPED IMAGE". I have double checked hash as well and the name being PG32IMG.zip, not PG32IMG.zip.zip. I have used 2 different microSD cards, one being freshly formatted. Both of them are formatted as FAT32. My understanding is this error is because I currently have 5.10.605.9 and cant flash the same thing over because I have the HTC unlock.
Should be fastboot flash recovery.img
Sent from my Venomized ViperINC
tylerlawhon said:
Should be fastboot flash recovery.img
Sent from my Venomized ViperINC
Click to expand...
Click to collapse
Just extract the recovery image from the link sk842018 provided and flash that using fastboot flash recovery.img?
jlaj1989 said:
Just extract the recovery image from the link sk842018 provided and flash that using fastboot flash recovery.img?
Click to expand...
Click to collapse
Yes. That's how you install a kernel when you're unlocked through htc and I'm pretty sure it's the same process.
Sent from my Venomized ViperINC
tylerlawhon said:
Yes. That's how you install a kernel when you're unlocked through htc and I'm pretty sure it's the same process.
Sent from my Venomized ViperINC
Click to expand...
Click to collapse
That worked beautifully thank you. I didn't realize it was that simple. Since the warranty of the phone is up in 2 weeks I decided to take the plunge get S-OFF. Upon reading the steps for this process it says I have to re-lock the bootloader before I do anything else. Once I did this hboot read the RUU file just fine and asked if I wanted to proceed with the update. So I guess it is possible to flash RUU with the same version it just need to bootloader re-locked?? This makes no sense but I have S-OFF now and everything is good, thank you all.