Related
Okay, so I'm in a bit of a bind. I'm S-OFF, and I tried updating to the global leak and it seems I've lost boot and recovery. Everytime I boot it goes through the splash screen and then a black screen with the phone and green update symbol, then it turns to a red triangle and exclamation mark. any help would be greatly appreciated. I'm fairly experienced and everything i've tried has failed. I tried going into hboot and flashing the PH98IMG again. It took, but still the same result. I tried flashing the recovery in fastboot but it continues to fail, and I also tried flashing my boot.img but it also failed. Any ideas?
tomtripp21 said:
Okay, so I'm in a bit of a bind. I'm S-OFF, and I tried updating to the global leak and it seems I've lost boot and recovery. Everytime I boot it goes through the splash screen and then a black screen with the phone and green update symbol, then it turns to a red triangle and exclamation mark. any help would be greatly appreciated. I'm fairly experienced and everything i've tried has failed. I tried going into hboot and flashing the PH98IMG again. It took, but still the same result. I tried flashing the recovery in fastboot but it continues to fail, and I also tried flashing my boot.img but it also failed. Any ideas?
Click to expand...
Click to collapse
unlock the bootloader and flash a recovery. you need to unlock since you dont have eng commands.
btw this belongs in q&a
antp121 said:
unlock the bootloader and flash a recovery. you need to unlock since you dont have eng commands.
btw this belongs in q&a
Click to expand...
Click to collapse
Thanks I'll give that a try. Will the firmware and ROM still be in place? Will I have do the update again? BTW Sorry for posting it in the wrong section..
tomtripp21 said:
Thanks I'll give that a try. Will the firmware and ROM still be in place? Will I have do the update again? BTW Sorry for posting it in the wrong section..
Click to expand...
Click to collapse
Its OK. And once you unlock, it'll reboot. Then you just go back into the boot loader and flash a recovery with fast boot.
Sent from my aokp_tenderloin using Tapatalk 2
So got the recovery flashed, but now it only boots into the recovery.
tomtripp21 said:
So got the recovery flashed, but now it only boots into the recovery.
Click to expand...
Click to collapse
Did you try flashig a rom?
Sent from my aokp_tenderloin using Tapatalk 2
i tried to restore my backup that didn't work, I haven't tried a new ROM yet. I'll try that and get back to you. Thanks again for all your help.
antp121 said:
Did you try flashig a rom?
Sent from my aokp_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
Tried flashing a ROM, the stock deodexed rooted 4.03.605.02. Still boots to recovery...
tomtripp21 said:
Tried flashing a ROM, the stock deodexed rooted 4.03.605.02. Still boots to recovery...
Click to expand...
Click to collapse
You need to use interface to fastboot boot.img then run firmware update for old firmware n old CWR. BASICALLY GO BACK TO STOCK REZOUND N START THE WHOLE PROCESS OVER LIKE DAY 1!
Good news is you don't need to do the wire trick again. Your phone crashed during the firmware upgrade now its stuck in limbo n doesn't know how to handle the 2 sets of hardware commands its receiving from the CMOS.
[Q] Can only get into recovery after attempting Juopunutbear S-OFF
I wanted to S-OFF after being stock locked, with the OTA ICS update. I performed HTC dev unlock successfully. After that, I may have gone wrong during one of several steps.
-Pushed AmonRa recovery 3.15 to my phone (seemed to be successful)
-Flashed ICE-EnableRoot.img (got an error message saying it was unsuccessful, but when I rebooted my phone, SuperUser was installed).
-Flashed vigorOTAStockRooted.zip (because I wanted to try the S-OFF method from stock GB rom)
-Ran HTC Rezound S-OFF Kit By Hasoon2000
-Made sure HTC Drivers were installed
-Enabled USB Debugging
-Put in blank SD Card
-Run Juopunutbear v.6 If You Are On Gingerbread
After running Juopunutbear v.6 for Gingerbread, my phone screen went blank and HTC's splash screen came up momentarily, and then my phone screen went dark. The cmd box that popped up then gave me an error message saying I had to install the HTC Drivers. I went to HTC's website to download the drivers. When I tried to install them, I was told they were already installed.
I can reboot my phone into Hboot and AmonRa recovery and I can do anything from there. But when I try to start my phone, I get the HTC splash screen and then black screen. The orange LED lights up when my phone is powered off and plugged in via USB. When I try to boot from Hboot, I either get a static HTC splash screen or splash screen going to a black screen.
This is what my Hboot screen reads:
*** TAMPERED ***
*** UNLOCKED ***
VIGOR PVT SHIP S-ON RL
HBOOT-2.25.0000
RADIO-1.22.10.0421r/1.22.10.0424r
Open DSP-v13.6.0.7611.00.0104
eMMC-boot
Apr 12 2012,16:47:46
Any advise would be greatly appreciated! Thank you!
jtayag said:
I wanted to S-OFF after being stock locked, with the OTA ICS update. I performed HTC dev unlock successfully. After that, I may have gone wrong during one of several steps.
-Pushed AmonRa recovery 3.15 to my phone (seemed to be successful)
-Flashed ICE-EnableRoot.img (got an error message saying it was unsuccessful, but when I rebooted my phone, SuperUser was installed).
-Flashed vigorOTAStockRooted.zip (because I wanted to try the S-OFF method from stock GB rom)
-Ran HTC Rezound S-OFF Kit By Hasoon2000
-Made sure HTC Drivers were installed
-Enabled USB Debugging
-Put in blank SD Card
-Run Juopunutbear v.6 If You Are On Gingerbread
After running Juopunutbear v.6 for Gingerbread, my phone screen went blank and HTC's splash screen came up momentarily, and then my phone screen went dark. The cmd box that popped up then gave me an error message saying I had to install the HTC Drivers. I went to HTC's website to download the drivers. When I tried to install them, I was told they were already installed.
I can reboot my phone into Hboot and AmonRa recovery and I can do anything from there. But when I try to start my phone, I get the HTC splash screen and then black screen. The orange LED lights up when my phone is powered off and plugged in via USB. When I try to boot from Hboot, I either get a static HTC splash screen or splash screen going to a black screen.
This is what my Hboot screen reads:
*** TAMPERED ***
*** UNLOCKED ***
VIGOR PVT SHIP S-ON RL
HBOOT-2.25.0000
RADIO-1.22.10.0421r/1.22.10.0424r
Open DSP-v13.6.0.7611.00.0104
eMMC-boot
Apr 12 2012,16:47:46
Any advise would be greatly appreciated! Thank you!
Click to expand...
Click to collapse
For starters, you are on ics firmware so you should run the ics version of juopunutbear. I suggest flashing a rooted Rom based on the ota and then try again.
Sent from my ADR6425LVW using Tapatalk 2
topgun1953 said:
For starters, you are on ics firmware so you should run the ics version of juopunutbear. I suggest flashing a rooted Rom based on the ota and then try again.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
I successfully flashed one of the stock ICS ROMs! What got me all confused to begin with was the prerequisite that I had to be on a stock Gingerbread ROM or the 3.14.605.5 ICS leak. That's why I tried flashing the original Vigor GB ROM on my phone. I still want to get S-OFF, but I need to read the instructions more carefully. Thanks for your help!
dragonstalker said:
You need to use interface to fastboot boot.img then run firmware update for old firmware n old CWR. BASICALLY GO BACK TO STOCK REZOUND N START THE WHOLE PROCESS OVER LIKE DAY 1!
Good news is you don't need to do the wire trick again. Your phone crashed during the firmware upgrade now its stuck in limbo n doesn't know how to handle the 2 sets of hardware commands its receiving from the CMOS.
Click to expand...
Click to collapse
So I just need to flash my backed up boot.img, and then flash the 3.14.605.12 RUU? Then re-root and retry the OTA Global Update?
tomtripp21 said:
So I just need to flash my backed up boot.img, and then flash the 3.14.605.12 RUU? Then re-root and retry the OTA Global Update?
Click to expand...
Click to collapse
pretty much. From looking at everything looks like you are on ICS, but its not letting you reprogram. usually happens when an update fails. When you run Juonobear and run the ics upgrade over again, it should reboot like 3 or 4 times. Sounds like you never let the process finish. Final note, i'm not sure where you got your firmware from, but your radios do not look familiar. Not saying they are wrong, just not radio's i've ever seen flashed. BUT, I don't usually change radio's unless there is a huge need for it. you should be on radio's 10r/08r that come with the original ICS firmware update. I'll watch the thread throughout the day to lend support where I can. Hope this helps.
dragonstalker said:
pretty much. From looking at everything looks like you are on ICS, but its not letting you reprogram. usually happens when an update fails. When you run Juonobear and run the ics upgrade over again, it should reboot like 3 or 4 times. Sounds like you never let the process finish. Final note, i'm not sure where you got your firmware from, but your radios do not look familiar. Not saying they are wrong, just not radio's i've ever seen flashed. BUT, I don't usually change radio's unless there is a huge need for it. you should be on radio's 10r/08r that come with the original ICS firmware update. I'll watch the thread throughout the day to lend support where I can. Hope this helps.
Click to expand...
Click to collapse
Now I'm a little confused, sorry. I need to run the juopunutbear program again? My radios are 2.22.10.0801r/2.22.10.0803r, Hboot 2.27. I'm downloading the .12 RUU from Android Police. I've tried re-flashing the boot.img from my nand backup, but it keeps saying:
C:\mini-adb_vigor>fastboot flash boot.img
unknown partition 'boot.img'
error: cannot determine image filename for 'boot.img'
edit: I fixed the flash, I forgot to add the partition in the command, duh... So I flashed my backed up boot.img, now I just need to flash the .12 RUU?
I have the backup img in the file where I have fastboot, adb, etc.. What am I doing wrong?
tomtripp21 said:
Now I'm a little confused, sorry. I need to run the juopunutbear program again? My radios are 2.22.10.0801r/2.22.10.0803r, Hboot 2.27. I'm downloading the .12 RUU from Android Police. I've tried re-flashing the boot.img from my nand backup, but it keeps saying:
C:\mini-adb_vigor>fastboot flash boot.img
unknown partition 'boot.img'
error: cannot determine image filename for 'boot.img'
edit: I fixed the flash, I forgot to add the partition in the command, duh... So I flashed my backed up boot.img, now I just need to flash the .12 RUU?
I have the backup img in the file where I have fastboot, adb, etc.. What am I doing wrong?
Click to expand...
Click to collapse
I have now tried to flash the .12 RUU in Hboot but it will not flash it, probably because my firmware is newer right? Back to the drawing board....
Still to no avail I am getting nowhere. I flashed the stock recovery and did a factory reset from Hboot. Nothing, I have tried flashing the newest RUU, nothing, I'm flashed back to ra-recovery. Can anybody give me a solution step by step to get a ROM loaded and booting?
Well I finally got it up and working. I loaded the old firmware and was able to restore by backup. Thanks to all who chimed in with helpful advice. I'm hesitant to retry the Global update, but I might go ahead and give it another shot.
Glad you figured to restore the firmware. It's not hard to flash the global. Run the firmware, then run the recovery then flash Rom. Do it right in that order n you don't have any issues. Use 2 sdcards if you need to because the firmware upgrade won't delete the ph98 off your card. You will need to do it manually.
Sent from ICS REZOUND S-OFF
Gave my Evo 3d to my borother a few months back, but hes come back to me today saying it was stuck in bootloop.
He booted into the bootloader and did a factory reset, but it was still stuck in bootloop.
I tried to get into recovery to flash a new rom, but when i select recovery from the bootloader, that also goes into a bootloop.
Used adb to push the recovery onto the phone again but still just keeps bootlooping.
Not sure if its important but the phone is s-off. Any ideas on whats going on or how to fix?
Apologies, supposed to put this in Q&A forum
While you're at bootloader, connect USB and then flash a stock RUU.
androidcdma said:
While you're at bootloader, connect USB and then flash a stock RUU.
Click to expand...
Click to collapse
Thanks for the reply. Will i lose s-off with this?
Tones1971 said:
Gave my Evo 3d to my borother a few months back, but hes come back to me today saying it was stuck in bootloop.
He booted into the bootloader and did a factory reset, but it was still stuck in bootloop.
I tried to get into recovery to flash a new rom, but when i select recovery from the bootloader, that also goes into a bootloop.
Used adb to push the recovery onto the phone again but still just keeps bootlooping.
Not sure if its important but the phone is s-off. Any ideas on whats going on or how to fix?
Apologies, supposed to put this in Q&A forum
Click to expand...
Click to collapse
You didn't say what version of the Evo 3D you have (CDMA or GSM) or what bootloader is installed, but if it's a Sprint CDMA model I would recommend flashing the Sprint ICS RUU.exe from Windows after putting the phone into fastboot mode in the bootloader. You may have to relock the bootloader with the "fastboot oem lock" command first if it shows "***UNLOCKED***" at the top of the screen.
That will fix a lot of problems, especially when the phone is in an indeterminate state. After flashing the RUU you can HTC unlock, flash a custom recovery and then root the stock ROM or flash a rooted ROM.
ramjet73
Sorry it is a UK GSM (Europe). I have revolutionary bootloader installed. Got an RUU to try now thanks.
androidcdma said:
While you're at bootloader, connect USB and then flash a stock RUU.
Click to expand...
Click to collapse
Tones1971 said:
Thanks for the reply. Will i lose s-off with this?
Click to expand...
Click to collapse
^^^^ He got it first with the short version.
No, you won't lose S-OFF and won't need to relock the bootloader first if that's your current status.
And if it's a GSM model everything still applies, you just need a different RUU, which you already have.
ramjet73
Thanks ramjet. Thought this was going to be straightforward but cant get ruu to install. Error 170. Ill keep plugging away / googling away, hopefully come up with something
Tones1971 said:
Thanks ramjet. Thought this was going to be straightforward but cant get ruu to install. Error 170. Ill keep plugging away / googling away, hopefully come up with something
Click to expand...
Click to collapse
Error 170 means that the RUU utility can't find the phone. There's a readme.doc for running the RUU here, and the error codes are towards the end of that.
Are you putting it into "fastboot" mode in the bootloader, which should change to "fastboot usb" when it is connected to a computer? You also need to have the HTC USB drivers active, which can be accomplished by installing HTC Sync.
ramjet73
Tones1971 said:
Used adb to push the recovery onto the phone again but still just keeps bootlooping.
Click to expand...
Click to collapse
adb push into a bootlooping phone?
do you have the drivers for the phone? (if not download and install HTC Sync as they come with it)
did you try flashing a custom recovery img through fastboot? (go to bootloader select fastboot, connect USB, type "fastboot flash recovery nameOfYourRecoveryImg.img")
Yeah have tried installing custom recovery through fast boot again, and im in fastboot ok when trying to run the RUU. Also have HTC Sync installed from when i had the phone.. Drivers seemed to be ok as i was able to install the custom recovery with adb, alhough i still got bootloop after that.
Ive a few other things to try when i get home from work. Im sure it shouldnt be too difficult to resolve. Hopefully anyway.
Well this isnt going smoothly at all. Used another PC and was able to get the RUU to run.
However it now comes up with Error 131 Customer ID problem. The RUU was for HTC Europe (non branded). The phone was sim free. When i posted months back my cid was HTC_001. I checked it here: http://forum.xda-developers.com/showpost.php?p=22394863&postcount=172
However now when i get my CID it is showing as CID0202. Any way i can get an RUU to install? Any idea how a CID could change?
EDIT: noticed i used a different command last time.
fastboot getvar cid shows CID0202
adb shell getprop ro.cid now shows device not found (previously showed CID_001)
Thats typing both commands in same window, one after the other. One gets CID0202, the other device not found???
There's a change cid command in fastboot, fastboot oem writecid or something along those lines... however i believe the cid check is in the updater scripts of the ruu in which case a fastboot flash of all the img files should avoid it entirely... i don't remember the procedure for extracting the img files from the ruu but i believe ur supposed to run it and then dig through your temp files...
dessolator666 said:
There's a change cid command in fastboot, fastboot oem writecid or something along those lines... however i believe the cid check is in the updater scripts of the ruu in which case a fastboot flash of all the img files should avoid it entirely... i don't remember the procedure for extracting the img files from the ruu but i believe ur supposed to run it and then dig through your temp files...
Click to expand...
Click to collapse
Thanks for this. Ill see if i can find anything else out about it. So saves running the RUU exe and no cid check done then?
Need to bump this as im not getting anywhere. No RUU's will install, error 31 customer error. Have flashed recovery via ADB and through PG86IMG.ZIP, but still cant get in to recovery as it just continually reboots.
S-OFF with revolutionary. Anybody any ideas please?
Got bigger problems than i thought. Finally got an RUU to install after 4 days of trying, by first using fastboot oem writecid 11111111. But when the phone rebooted it was back bootlooping again. Is there any hope for my phone?
Tones1971 said:
Got bigger problems than i thought. Finally got an RUU to install after 4 days of trying, by first using fastboot oem writecid 11111111. But when the phone rebooted it was back bootlooping again. Is there any hope for my phone?
Click to expand...
Click to collapse
You need to stop cross posting in the d3rp Q&A thread and your own thread if you want more help. Cross-posting is stongly discouraged on XDA and it's really confusing when you are asking for help in one thread while getting different advice in another.
It sounds to me like all the CID changes on your phone have left it in an indeterminate state and I'm not sure at this point what is the correct CID and RUU for your model. If you could detemine that, set the CID correctly and flash the right RUU the phone should work, but it might be too late if you have in fact been flashing firmware that doesn't match your phone because the right RUU may not back that out properly.
That's all I can offer at this point, but since I don't know the history of your phone and how it got the various CID's you have reported, you will probably be the one that needs to figure it out.
ramjet73
I was given a phone to try to resurrect from the dead. It powers on directly to the bootloader screen and does no more. I really know nothing about this phone model. Before I start, I want to know if it is even possible. The screen says the following:
*** LOCKED ***
SHOOTER XC SHIP S-ON RL
HBOOT-1.57.0000
eMMC-boot
Apr 20 2012, 17:39:22
And then there are the normal bootloader options. Can this thing be saved?
silenthatred said:
I was given a phone to try to resurrect from the dead. It powers on directly to the bootloader screen and does no more. I really know nothing about this phone model. Before I start, I want to know if it is even possible. The screen says the following:
*** LOCKED ***
SHOOTER XC SHIP S-ON RL
HBOOT-1.57.0000
eMMC-boot
Apr 20 2012, 17:39:22
And then there are the normal bootloader options. Can this thing be saved?
Click to expand...
Click to collapse
if you can get to the bootloader screen and access the fastboot selection,plug it into a computer and get it to read fastbootusb then its fixable,first find your token and unlock the bootloader, then from there install a custom recovery , next copy the stock ROM over to your sdcard and boot into recovery... select install zip from sdcard and guide yourself to where the file is located ,select it and let it install... from there it should be able to reboot and boot up into the ROM
wloftus said:
if you can get to the bootloader screen and access the fastboot selection,plug it into a computer and get it to read fastbootusb then its fixable,first find your token and unlock the bootloader, then from there install a custom recovery , next copy the stock ROM over to your sdcard and boot into recovery... select install zip from sdcard and guide yourself to where the file is located ,select it and let it install... from there it should be able to reboot and boot up into the ROM
Click to expand...
Click to collapse
Thanks, it does show fastboot usb...find your token? Not sure what that means. I'll search around a bit when I get home. My original Evo 4G I did root, but don't remember that part.
silenthatred said:
Thanks, it does show fastboot usb...find your token? Not sure what that means. I'll search around a bit when I get home. My original Evo 4G I did root, but don't remember that part.
Click to expand...
Click to collapse
You don't need to unlock the bootloader to fix it, and you shouldn't unlock it anyways, until you have it fully booted properly.
Run the RUU EXE from a PC for the 3.28 update (or whatever the later version is) while the phone is connected via fastboot USB mode, it will re-flash the ROM and should boot properly then.
Unknownforce said:
You don't need to unlock the bootloader to fix it, and you shouldn't unlock it anyways, until you have it fully booted properly.
Run the RUU EXE from a PC for the 3.28 update (or whatever the later version is) while the phone is connected via fastboot USB mode, it will re-flash the ROM and should boot properly then.
Click to expand...
Click to collapse
RUU.EXE finds it and then gets to the restarting into bootloader step and the phone restarts. Then it just saying waiting for bootloader until it times out, but the bootloader is up on the phone.
silenthatred said:
RUU.EXE finds it and then gets to the restarting into bootloader step and the phone restarts. Then it just saying waiting for bootloader until it times out, but the bootloader is up on the phone.
Click to expand...
Click to collapse
This happens sometimes if you have a custom bootloader installed when you flash the RUU. Just cancel the Windows task and restart it and you should be fine.
ramjet73
wloftus said:
if you can get to the bootloader screen and access the fastboot selection,plug it into a computer and get it to read fastbootusb then its fixable,first find your token and unlock the bootloader, then from there install a custom recovery , next copy the stock ROM over to your sdcard and boot into recovery... select install zip from sdcard and guide yourself to where the file is located ,select it and let it install... from there it should be able to reboot and boot up into the ROM
Click to expand...
Click to collapse
Unknownforce said:
You don't need to unlock the bootloader to fix it, and you shouldn't unlock it anyways, until you have it fully booted properly.
Run the RUU EXE from a PC for the 3.28 update (or whatever the later version is) while the phone is connected via fastboot USB mode, it will re-flash the ROM and should boot properly then.
Click to expand...
Click to collapse
Couple things since I have looked into this a little more. Despite it saying Sprint on the front, it is a Virgin Mobile phone. It has the OTA that came down on it, so I can't flash the older RUU. It says it is an older version. So it looks like unlocking the bootloader is my only option? Question is, how do I do that from the bootloader? I was able to get the token and have the unlock_code.bin file, but the instructions to flash it seem to rely on having a working ROM to complete it, which I don't have. The phone is stuck in a bootloader loop. S-OFF, I have the answer. But it is S-ON, so not sure what to do.
silenthatred said:
Couple things since I have looked into this a little more. Despite it saying Sprint on the front, it is a Virgin Mobile phone. It has the OTA that came down on it, so I can't flash the older RUU. It says it is an older version. So it looks like unlocking the bootloader is my only option? Question is, how do I do that from the bootloader? I was able to get the token and have the unlock_code.bin file, but the instructions to flash it seem to rely on having a working ROM to complete it, which I don't have. The phone is stuck in a bootloader loop. S-OFF, I have the answer. But it is S-ON, so not sure what to do.
Click to expand...
Click to collapse
You are right that the Virgin Mobile RUU can't be flashed when S-ON and the OTA has been installed unless you can flash a zip to downgrade your main version (mainver) and you have to be unlocked and rooted to do that.
The unlock_code.bin file is flashed via fastboot USB mode so it might work, but if you've tried that and it doesn't you may be able to use unknownforce's hboot downgrade method to get straight to S-OFF. I don't know of anyone that's done it on an Evo V 4G but it might work if you use the RUU zip file for that model.
ramjet73
ramjet73 said:
You are right that the Virgin Mobile RUU can't be flashed when S-ON and the OTA has been installed unless you can flash a zip to downgrade your main version (mainver) and you have to be unlocked and rooted to do that.
The unlock_code.bin file is flashed via fastboot USB mode so it might work, but if you've tried that and it doesn't you may be able to use unknownforce's hboot downgrade method to get straight to S-OFF. I don't know of anyone that's done it on an Evo V 4G but it might work if you use the RUU zip file for that model.
ramjet73
Click to expand...
Click to collapse
It flashes unlock_code.bin to the phone successfully, but the next steps say to click yes on the screen to unlock on the phone. Can't access that without a working ROM. I'll try unknownforce's method when I get home, thanks for the help!
ramjet73 said:
You are right that the Virgin Mobile RUU can't be flashed when S-ON and the OTA has been installed unless you can flash a zip to downgrade your main version (mainver) and you have to be unlocked and rooted to do that.
Click to expand...
Click to collapse
Why is this? Is there not a full RUU for the latest version?
ramjet73 said:
The unlock_code.bin file is flashed via fastboot USB mode so it might work, but if you've tried that and it doesn't you may be able to use unknownforce's hboot downgrade method to get straight to S-OFF. I don't know of anyone that's done it on an Evo V 4G but it might work if you use the RUU zip file for that model.
ramjet73
Click to expand...
Click to collapse
You still have to brick the device for this and I haven't been able to brick it without using a full RUU flash, which he apparently can't do?
silenthatred said:
It flashes unlock_code.bin to the phone successfully, but the next steps say to click yes on the screen to unlock on the phone. Can't access that without a working ROM. I'll try unknownforce's method when I get home, thanks for the help!
Click to expand...
Click to collapse
Does it still say ** LOCKED ** Or does it say ** UNLOCKED ** now?
Unknownforce said:
Why is this? Is there not a full RUU for the latest version?
Click to expand...
Click to collapse
No. Virgin Mobile released an OTA update in November but there's no RUU that corresponds to it available yet. Fortunately, the bootloader version didn't change so the original RUU can be flashed with S-ON if the mainver is set low, but you need to be unlocked and rooted already to flash the zip file that does that.
You still have to brick the device for this and I haven't been able to brick it without using a full RUU flash, which he apparently can't do?
Click to expand...
Click to collapse
That would be a problem for him then. I don't know of anyway to flash the RUU with S-ON after the OTA has been installed if the bootloader is actually locked and he can't unlock it.
ramjet73
Yeah, not looking good. Thanks for the help though!
So I have a problem with my phone randomly rebooting, so I am trying to run the stock RUU to make sure it is nothing I did. The problem is that when I do this I get to the step were the phone is supposed to go to the bootloader and it just shows a black screen with the HTC logo. Any idea what I should try next?
Have you re-locked your bootloader and installed a stock recovery?
How do I do that without the ruu
Sent from my EVO using xda app-developers app
You have to be re-locked for the RUU to work.
fastboot oem lock
Try this script thanks to viperboy
http://forum.xda-developers.com/showthread.php?t=2197909
Good luck!
Sent from my EVO using xda app-developers app
The script hangs at starting ruu mode
RUU not working on Evo Jewel
kevinb99 said:
The script hangs at starting ruu mode
Click to expand...
Click to collapse
Did you ever figure this out? I have the same problem, and I too have tried the Vipe utility. It does flash the recovery in the batch file, but RUU fails. I have tried all RUU's from androidfiles for the jewel and they fail to with an unknown error. I cannot get any custom roms to flash either, they fail altogether or they flash but never get past they HTC screen. I can still boot into recovery and I have also tried relocking the bootloader.
jseibert81 said:
Did you ever figure this out? I have the same problem, and I too have tried the Vipe utility. It does flash the recovery in the batch file, but RUU fails. I have tried all RUU's from androidfiles for the jewel and they fail to with an unknown error. I cannot get any custom roms to flash either, they fail altogether or they flash but never get past they HTC screen. I can still boot into recovery and I have also tried relocking the bootloader.
Click to expand...
Click to collapse
No, that sucks, I was able to get stock rooted on and have since gotten 5 replacement phones.
Got RUU working
kevinb99 said:
No, that sucks, I was able to get stock rooted on and have since gotten 5 replacement phones.
Click to expand...
Click to collapse
So your problem is with the phone rebooting still? I was having trouble installing the RUU and it seems so have a lot of people. The boot loader does need to be locked, that was one of my problems. I'm also pretty sure I wasn't using the correct RUU, as I tried so many. Vipe doesn't work but will at least push a recovery. I re-locked the bootloader, and tried one last RUU and it worked.
When I tried flashing the phone originally, something went wrong. TWRP wouldn't install any Roms at all even when some completed successfully. It would just hang at the HTC screen. I could probably go back and try it again but I'm done. I won't touch another HTC phone as far as flashing goes.
Hey I am probably going to call verizon tomorrow to get a replacement for my rez, but I am worried about unrooting mine. This one is a replacement and after i got it s off I tried to flash the newest RUU to get the radios, but it would constantly get stuck when updating the system and would then loop and try again and never finish. So I just flashed a recovery and then got the flashable version of the radios and it worked good enough. But now my problem is that before when I sent in my rez I just reflashed the RUU and it reset everything and my HBOOT showed that it was locked s on and not tampered. That would be ideal if I could get that again, how would I go about doing that? just flashing a stock rom, deleting superuser, and then flashing a HBOOT that shows s on and not tampered? any help would be greatly appreciated
No one answered so im trying to figure this out by myself, and i cant get my hboot to not say tampered but still be on the stock hboot so i can adb the s on command. I have pulled the hboot update out of the RUU and it flashed fine but it still says tampered
hboot says tampered if a custom recovery is installed. You have to be on stock recovery (not hboot) to keep it from saying tampered. Flashing a stock RUU is the easiest way.
shrike1978 said:
hboot says tampered if a custom recovery is installed. You have to be on stock recovery (not hboot) to keep it from saying tampered. Flashing a stock RUU is the easiest way.
Click to expand...
Click to collapse
thanks for answering, but that my problem. My phone doesnt like flashing a RUU, it will update until it gets to system, then it will just gt in a loop of flashing and unzipping the system. I had made a modified version that just flashed the hboot and recovery in hboot but it didnt change the tampered
xxtsxx said:
thanks for answering, but that my problem. My phone doesnt like flashing a RUU, it will update until it gets to system, then it will just gt in a loop of flashing and unzipping the system. I had made a modified version that just flashed the hboot and recovery in hboot but it didnt change the tampered
Click to expand...
Click to collapse
It usually takes at least twice for an RUU to fully flash. I've had it take 3 times. When it's done completely, it will reboot normally.
Edit: Also, system is huge and is actually made up of a bunch of files. It does each of those individually, so you see it flashing system several dozen times. That's completely normal.
shrike1978 said:
It usually takes at least twice for an RUU to fully flash. I've had it take 3 times. When it's done completely, it will reboot normally.
Edit: Also, system is huge and is actually made up of a bunch of files. It does each of those individually, so you see it flashing system several dozen times. That's completely normal.
Click to expand...
Click to collapse
wow oh crap i feel stupid. im gonna just let it do its thing for awhile then and see what happens
Edit: well that worked perfectly. i guess a little patience goes a long way. thanks for all the help