Hey, just to let people know, be wary of flashing the firmware from the M7 Sense 6 update from T-Mobile, I pulled it from the OTA and it flashed successfully in RUU mode, but now im stuck in the dreaded QHSUSB_DLOAD mode, trying to figure a way to get a replacement, but just letting people know to be careful...
Whoareyou said:
Hey, just to let people know, be wary of flashing the firmware from the M7 Sense 6 update from T-Mobile, I pulled it from the OTA and it flashed successfully in RUU mode, but now im stuck in the dreaded QHSUSB_DLOAD mode, trying to figure a way to get a replacement, but just letting people know to be careful...
Click to expand...
Click to collapse
Please provide more details;
Do you have a T-Mobile device? --Did you change your CID?
What ROM?
What recovery?
Bootloader unlocked? S-Off?
What hboot did you have before flashing (stock? custom?)
How exactly did you pull the firmware?
These details would be very helpful.
Sent from my HTC One_M8 using Tapatalk
krook6023 said:
Please provide more details;
Do you have a T-Mobile device? --Did you change your CID?
What ROM?
What recovery?
Bootloader unlocked? S-Off?
What hboot did you have before flashing (stock? custom?)
How exactly did you pull the firmware?
These details would be very helpful.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Yes I have a T-Mobile Device, yes its S-OFF, CID is SUPERCID (1111111), had Firewater HBOOT previously.
ViperONE 6.2.1
TWRP
i used WinRAR and pulled the firmware.zip from the OTA file, then booted into rebootRUU mode and "fastboot flash zip firmware.zip" the it told me to flush again as per usual, i did it again, then when i went to reboot, i was in QHSUSB_DLOAD
Whoareyou said:
Yes I have a T-Mobile Device, yes its S-OFF, CID is SUPERCID (1111111)...
Click to expand...
Click to collapse
Maybe an issue with SuperCID...
You should read this thread: http://forum.xda-developers.com/showthread.php?t=2753631
People had a similar problem and a few were able to get back into hboot by plugging the phone to computer and persistently pressing power and volume down and/or volume up in different combinations. If you can get back to the boot loader flash a know working firmware. It's worth a shot... Here are some relevant comments from that thread...
streather said:
Same problem here, bricked the phone.
I have managed to get it to turn back on and got to the silver HTC logo but I sent the wrong command over fastboot and it turned off again
Click to expand...
Click to collapse
BanBoo said:
How do you managed it?!
Click to expand...
Click to collapse
simaka said:
OK, I got back to the bootloader.
Guys, be persistent in pressing power+vol buttons while usb connected to PC, it took me about 10-15 minutes but now I am back to fastboot!
Any ideas what would be the best course of action now?
Click to expand...
Click to collapse
simaka said:
Not sure if it was power + vol down or + vol up... But I definitely waited each time about 20 secs before switching to the other possibility. And the phone was usb connected to my pc.
Click to expand...
Click to collapse
simaka said:
Yes, each time. I also tried pressing both + and - at the same time, but that was not the winning combination.
Click to expand...
Click to collapse
yoshi8 said:
how did you recognized that you are in fastboot again? did your screen turn on again?
Click to expand...
Click to collapse
simaka said:
Yes, it has booted and screen is lit and I am in fastboot. Now wondering what is the best next step... Which firmware should I upgrade with...
Click to expand...
Click to collapse
simaka said:
Here is what I did the last time:
1. winclock showing seconds in front of me.
2. hold power + vol down.
3. Count 3 seconds
4. release.
5. Go to 1 and add 1 second on step 3 . In about 20 minutes (when I surpassed 20 secs I started from 3 seconds on step 3 again) I woke it up.
good luck!
Click to expand...
Click to collapse
Sent from my HTC One_M8 using Tapatalk
All CID's must have eight characters. SuperCID would have to be 11111111 not 1111111
Sent from my HTC One using XDA Free mobile app
NxNW said:
All CID's must have eight characters. SuperCID would have to be 11111111 not 1111111
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
you know what i mean, it was all 1s also holding the buttons didnt work
Whoareyou said:
you know what i mean, it was all 1s also holding the buttons didnt work
Click to expand...
Click to collapse
Just checking- someone said it could be an issue with the CID, and that would definitely be "an issue" ; )
Whoareyou said:
Yes I have a T-Mobile Device, yes its S-OFF, CID is SUPERCID (1111111), had Firewater HBOOT previously.
ViperONE 6.2.1
TWRP
i used WinRAR and pulled the firmware.zip from the OTA file, then booted into rebootRUU mode and "fastboot flash zip firmware.zip" the it told me to flush again as per usual, i did it again, then when i went to reboot, i was in QHSUSB_DLOAD
Click to expand...
Click to collapse
That right there is what bricked your phone. I honestly don't know why people care so much about the red message on boot to flash a modded Hboot. Most devs on the One international forum are starting to pull of their modded Hboots as people usually don't know flashing a modded one can brick phones on future updates or so.
I haven't manually flashed just firmware. I am s-off with supercid. To get most current I loaded the last tmous ruu then let it go through all updates until it was at the latest sense 6, then reloaded twrp and my latest nandroid.
Sent from my HTC One using XDA Free mobile app
Jorakal said:
I haven't manually flashed just firmware. I am s-off with supercid. To get most current I loaded the last tmous ruu then let it go through all updates until it was at the latest sense 6, then reloaded twrp and my latest nandroid.
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
That is a good way however we should point if one has a moded hboot and applies the official RUU will brick the phone. Just pointing that out.
Sent from my HTC One using Tapatalk
Firmware Update
I have been looking to update to the latest firmware on my tmobile htc one, but i also have a custom hboot that i got from here " http://forum.xda-developers.com/showthread.php?t=2497712 " so im holding off on flashing the newest firmware, because it will probably brick my phone. But what i am wondering is does anyone know where i can just fine the 1.44 tmobile hboot that i was currently on?? so that i dont have to flash the stock RUU and start all back over from scratch ?? I could just flash back to the 1.44 stock hboot and then upgrade to the newest firmware without bricking my phone ??
Tewessarino said:
I have been looking to update to the latest firmware on my tmobile htc one, but i also have a custom hboot that i got from here " http://forum.xda-developers.com/showthread.php?t=2497712 " so im holding off on flashing the newest firmware, because it will probably brick my phone. But what i am wondering is does anyone know where i can just fine the 1.44 tmobile hboot that i was currently on?? so that i dont have to flash the stock RUU and start all back over from scratch ?? I could just flash back to the 1.44 stock hboot and then upgrade to the newest firmware without bricking my phone ??
Click to expand...
Click to collapse
Take a look @Behold_this thread TMOUS Firmware Packages - Release Builds for the correct firmware to return you to stock hboot.
factory reset
i tried almost everything i cant do ruu.exe cause i get and error 155 which is unknown error and yes i was relocked before running the ruu. i tried doing s-off with no luck im on t-mobile us network htc one m7
i have viper rom 6.2.0 running right now on it
bootloader menu i have
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-4A.21.3263.03
OpenDSP-v32.120.274.0909
OS-*** this is what im not sure why theres nothing when there used to be***
eMMC-boot 2048m
its tampered and unlocked at the moment plz help thanx i need to factory reset
matador1510 said:
i tried almost everything i cant do ruu.exe cause i get and error 155 which is unknown error and yes i was relocked before running the ruu. i tried doing s-off with no luck im on t-mobile us network htc one m7
i have viper rom 6.2.0 running right now on it
bootloader menu i have
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-4A.21.3263.03
OpenDSP-v32.120.274.0909
OS-*** this is what im not sure why theres nothing when there used to be***
eMMC-boot 2048m
its tampered and unlocked at the moment plz help thanx i need to factory reset
Click to expand...
Click to collapse
Which RUU.exe are you attempting to run? If it is this one: T-Mobile HTC One 4.3 3.24.531.3 RUU then your hboot is too high. I would suggest trying this one: T-Mobile USA | 4.4.2 | Sense 6 | 5.14.531.11. Also, since you are S-ON the bootloader needs to be locked/relocked for you to run a RUU. You can lock it in bootloader/FASTBOOT USB with this command: fastboot oem lock
If Viper is running on your One without an issue then you have an operating ROM and the missing OS is due to the custom recovery you used. If you are using TWRP, I would recommend TWRP 2.6.3.3 or TWRP 2.6.3.4 or TWRP 2.7.1.2! The last one has some changes built in that help eliminate the issue of a blank OS.
factory reset
majmoz said:
Which RUU.exe are you attempting to run? If it is this one: T-Mobile HTC One 4.3 3.24.531.3 RUU then your hboot is too high. I would suggest trying this one: T-Mobile USA | 4.4.2 | Sense 6 | 5.14.531.11. Also, since you are S-ON the bootloader needs to be locked/relocked for you to run a RUU. You can lock it in bootloader/FASTBOOT USB with this command: fastboot oem lock
If Viper is running on your One without an issue then you have an operating ROM and the missing OS is due to the custom recovery you used. If you are using TWRP, I would recommend TWRP 2.6.3.3 or TWRP 2.6.3.4 or TWRP 2.7.1.2! The last one has some changes built in that help eliminate the issue of a blank OS.
Click to expand...
Click to collapse
thanx i will try this will let you what happens
htc m7 pn07110 bricked
htc m7 pn07110 bricked
hi i have a problem when usin my phone it suddenly freezers and was not able to get acces to anything (Was rooted/Bootloader Unlocked/having Custom Rom/TRWP/S-ON).. tried to restore my rom by usin twrp 2.8. but there was no file and it cannot mount my storage...
Then, found on a thread to restore stock ROM via RUU, so i relocked my bootloader and then find myself stuck at everything
When I plug in AC adapter for charging, phone load in bootloader, and whenever i press "Fastboot/Factory Reset" my phone freezes
Even fastboot and ADB command freezes my phone,
I need help please.
Code:
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
M7_U PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.28.3218.04
OpenDSP-v32.120.274.0909
OS-6.09.401.111
eMMC-boot 2048MB
Nov 12 2014,21:44:28.0
lordtopher said:
htc m7 pn07110 bricked
hi i have a problem when usin my phone it suddenly freezers and was not able to get acces to anything (Was rooted/Bootloader Unlocked/having Custom Rom/TRWP/S-ON).. tried to restore my rom by usin twrp 2.8. but there was no file and it cannot mount my storage...
Then, found on a thread to restore stock ROM via RUU, so i relocked my bootloader and then find myself stuck at everything
When I plug in AC adapter for charging, phone load in bootloader, and whenever i press "Fastboot/Factory Reset" my phone freezes
Even fastboot and ADB command freezes my phone,
I need help please.
Code:
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
M7_U PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.28.3218.04
OpenDSP-v32.120.274.0909
OS-6.09.401.111
eMMC-boot 2048MB
Nov 12 2014,21:44:28.0
Click to expand...
Click to collapse
Check out this post for the TWRP nandroid, firmware and stock recovery for your phone. You will need to unlock your bootloader to flash the recovery or TWRP. If you decide to flash the firmware your bootloader should remain locked. In fact, I would flash the firmware first, then install TWRP to install the nandroid.
majmoz said:
Check out this post for the TWRP nandroid, firmware and stock recovery for your phone. You will need to unlock your bootloader to flash the recovery or TWRP. If you decide to flash the firmware your bootloader should remain locked. In fact, I would flash the firmware first, then install TWRP to install the nandroid.
Click to expand...
Click to collapse
the problem is the phone... when i got the fastboot menu...i can scroll down and up but when i press on power button to enter the bootloader the phone freezer and i must turn it off. have you heard this issue??? must i buy another phone??:crying:
lordtopher said:
the problem is the phone... when i got the fastboot menu...i can scroll down and up but when i press on power button to enter the bootloader the phone freezer and i must turn it off. have you heard this issue??? must i buy another phone??:crying:
Click to expand...
Click to collapse
Can you connect the phone to a computer and is it recognized?
If yes, then I would recommend flashing the firmware. It contains hboot and you may have an issue with hboot.
Here is the procedure for flashing the firmware. If your phone is already in bootloader/FASTBOOT USB you can skip the first line.
Code:
[B][I]adb reboot bootloader[/I][/B]
After that, type:
Code:
[B][I]fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]fastboot reboot[/I][/B]
Click to expand...
Click to collapse
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
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!
Someone responded to my post with this: "Try booting into the bootloader and use Fastboot to flash the recovery. From recovery flash a sense 3.6 ROM. Maybe that will work." But I don't know how to do this. Keep in my mind everything I do just takes me to the white HTC screen. Please help.
ADashOfCapers said:
Someone responded to my post with this: "Try booting into the bootloader and use Fastboot to flash the recovery. From recovery flash a sense 3.6 ROM. Maybe that will work." But I don't know how to do this. Keep in my mind everything I do just takes me to the white HTC screen. Please help.
Click to expand...
Click to collapse
You don't have a rooted phone and you don't have recovery.
If you flash Stock Rom, download stock rom from http://www.androidfiles.org/ruu/?developer=Shooter. With your phone started, start your *.exe rom and follow instructions.
I unroot my phone recently with
PG86IMG_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304-signed
and tried to root again last night and somehow sort of brick the thing. I can get into hboot and tried the same image again, and it will pick it up from bootloader. However, once the file finishes loading, it doesn't give me an option to upgrade (press volume up/down), and only goes back to the menu. I really have no idea what to do next. I can get into 4ext, and maybe I can flash a new ROM, but I'm not sure which one.
Currently my bootloader shows:
UNLOCKED
SHOOTER XC SHIP S-ON RL
HBOOT-1.58.0000
RADIO-1.09.00.0108
OpennADSP-v02.6.0.226.00.0217
eMMC-boot
HBOOT
I really appreciate the help. Thanks!
kzn said:
I unroot my phone recently with
PG86IMG_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304-signed
and tried to root again last night and somehow sort of brick the thing. I can get into hboot and tried the same image again, and it will pick it up from bootloader. However, once the file finishes loading, it doesn't give me an option to upgrade (press volume up/down), and only goes back to the menu. I really have no idea what to do next. I can get into 4ext, and maybe I can flash a new ROM, but I'm not sure which one.
Currently my bootloader shows:
UNLOCKED
SHOOTER XC SHIP S-ON RL
HBOOT-1.58.0000
RADIO-1.09.00.0108
OpennADSP-v02.6.0.226.00.0217
eMMC-boot
HBOOT
I really appreciate the help. Thanks!
Click to expand...
Click to collapse
Try to install any rom from http://forum.xda-developers.com/forumdisplay.php?f=1098 in 4EXT Recovery mode.
ADashOfCapers said:
Someone responded to my post with this: "Try booting into the bootloader and use Fastboot to flash the recovery. From recovery flash a sense 3.6 ROM. Maybe that will work." But I don't know how to do this. Keep in my mind everything I do just takes me to the white HTC screen. Please help.
Click to expand...
Click to collapse
http://androidforums.com/evo-v-4g-all-things-root/626186-easy-guide-get-out-bootloops.html
Try that.
Do I need to relock my Bootloader?
ADashOfCapers said:
Do I need to relock my Bootloader?
Click to expand...
Click to collapse
No.
I have the Rom installed and everything. I wiped everything and now it'll reboot to the Virgin Mobile screen and just stay there.
I have 2 phones
one of them stuck at HTC white screen suddenly when i was talk to some one it restart with that problem
ICS
S-on
1.93.002
unlocked
Able to flash recovery It success install but not working when try to enter recovery from bootloader nothing else :crying:
yesterday i install Hboot 1.93.222 successfully install but when i restart it come again 1.93.002
ANY HELP OR SUGGESTION
haninatoon said:
I have 2 phones
one of them stuck at HTC white screen suddenly when i was talk to some one it restart with that problem
ICS
S-on
1.93.002
unlocked
Able to flash recovery It success install but not working when try to enter recovery from bootloader nothing else :crying:
yesterday i install Hboot 1.93.222 successfully install but when i restart it come again 1.93.002
ANY HELP OR SUGGESTION
Click to expand...
Click to collapse
Hboot 193.222 can only be installed on s-off devices. It's the hacked engineering version.
Odysseus1962 said:
Hboot 193.222 can only be installed on s-off devices. It's the hacked engineering version.
Click to expand...
Click to collapse
now iam
hboot 1.93.002
i re-locked the phone
and it successfully install t-mobile ics ph85img.zip from sd card
noting : i can not install ph85img.zip when my phone is unlocked
but i still stuck in htc logo screen
any idea!!!!!!!!!!!!
haninatoon said:
now iam
hboot 1.93.002
i re-locked the phone
and it successfully install t-mobile ics ph85img.zip from sd card
noting : i can not install ph85img.zip when my phone is unlocked
but i still stuck in htc logo screen
any idea!!!!!!!!!!!!
Click to expand...
Click to collapse
Lock the phone and try the install. Following instructions where to place it.
haninatoon said:
now iam
hboot 1.93.002
i re-locked the phone
and it successfully install t-mobile ics ph85img.zip from sd card
noting : i can not install ph85img.zip when my phone is unlocked
but i still stuck in htc logo screen
any idea!!!!!!!!!!!!
Click to expand...
Click to collapse
You've been around for awhile, so you should know these things. Now you are what, s-off or s-on? It's normal to only be able to flash the image with your phone relocked. Was it a T-Mobile US or another version? Did it have JB or ICS? If it didn't already have ICS and it's an Asian or unbranded phone you need s-off and to get s-off you need to be on the stock RUU. If it's s-on and not a T-Mobile US phone and you installed the T-Mobile RUU, the radio and kernel probably didn't flash or you have a CID mismatch which is keeping it from booting.
Remember the steps to take for Asian or unbranded Amazes, is to first get s-of then SuperCID then flash the T-Mobile RUU. If it wasn't already on ICS you're going to have to go back to GB and start over, so you can get s-off.
Odysseus1962 said:
You've been around for awhile, so you should know these things. Now you are what, s-off or s-on? It's normal to only be able to flash the image with your phone relocked. Was it a T-Mobile US or another version? Did it have JB or ICS? If it didn't already have ICS and it's an Asian or unbranded phone you need s-off and to get s-off you need to be on the stock RUU. If it's s-on and not a T-Mobile US phone and you installed the T-Mobile RUU, the radio and kernel probably didn't flash or you have a CID mismatch which is keeping it from booting.
Remember the steps to take for Asian or unbranded Amazes, is to first get s-of then SuperCID then flash the T-Mobile RUU. If it wasn't already on ICS you're going to have to go back to GB and start over, so you can get s-off.
Click to expand...
Click to collapse
T-Mobile US ON SCREEN
iam s-on
ICS updated from internet on air from jb to ics even it is s-on location egypt with out any effort and it worked a bout 3 months
hboot now be 1.93.003 cause i install the (OTA_RUBY_ICS_35_S_TMOUS_2.14.531.3-1.43.531.3_release_259660) framework now
simply i do the update from software update in phone setting
haninatoon said:
T-Mobile US ON SCREEN
iam s-on
ICS updated from internet on air from jb to ics even it is s-on location egypt with out any effort and it worked a bout 3 months
hboot now be 1.93.003 cause i install the (OTA_RUBY_ICS_35_S_TMOUS_2.14.531.3-1.43.531.3_release_259660) framework now
simply do the update from software update in phone setting
Click to expand...
Click to collapse
So it is a T-Mobile US Amaze and you previously had received and installed the OTA which got you to hboot 1.93.003. It worked fine this way for three months until you had the problems. Am I correct?
yes
haninatoon said:
yes
Click to expand...
Click to collapse
That's not good. If it had been working well and then all of a sudden from out of nowhere it started behaving badly during a call, and you weren't in the process of doing anything else to it, then that leads me to believe that it's a hardware problem.
hardware problem. even
1- it install from boot-loader any thing
2-hboot now just now i make it 1.93.003
3-i flash ph85img from fastboot about 14 confirm ok
4-i can lock or re unlock
but at all stuck at logo & also try to downgrade to jb but i can not
That make me sad
But thanks at all man
I still have one work so I still amazed
haninatoon said:
hardware problem. even
1- it install from boot-loader any thing
2-hboot now just now i make it 1.93.003
3-i flash ph85img from fastboot about 14 confirm ok
4-i can lock or re unlock
but at all stuck at logo & also try to downgrade to jb but i can not
That make me sad
But thanks at all man
I still have one work so I still amazed
Click to expand...
Click to collapse
Unlock your bootloader if it's locked and put 4ext recovery image inside a zip renaming at as recovery and name the zip as PH85IMG.zip and flash it from bootloader and get into recovery and flash a stock amaze rom and do s-off.. I've seen this problem once the hboot 1.93.003 it's a issue .. S off and flash a RUU and it'll work perfectly again..
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
ravike14 said:
Unlock your bootloader if it's locked and put 4ext recovery image inside a zip renaming at as recovery and name the zip as PH85IMG.zip and flash it from bootloader and get into recovery and flash a stock amaze rom and do s-off.. I've seen this problem once the hboot 1.93.003 it's a issue .. S off and flash a RUU and it'll work perfectly again..
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I do that
Unlock your bootloader if it's locked and put 4ext recovery image inside a zip renaming at as recovery and name the zip as PH85IMG.zip and flash it from bootloader
but i can not do that
get into recovery cause stuck at HTC white screen
but i can not do that
haninatoon said:
I do that
Unlock your bootloader if it's locked and put 4ext recovery image inside a zip renaming at as recovery and name the zip as PH85IMG.zip and flash it from bootloader
but i can not do that
get into recovery cause stuck at HTC white screen
Click to expand...
Click to collapse
Bootloader comes before HTC white screen. Put PH85IMG.zip on root of sd card. Reboot to bootloader. If your bootloader screen says "Fastboot AC" put the selector on "Bootloader" and press the power button--it will search for, find, flash PH85IMG.zip.
It will tell you when done, at which point you can reboot into recovery and follow raivke14's instructions.
I have a HTC desire 601 bought this Summer from Virgin Mobile USA, a CDMA based carrier using Sprint network. My son played with it yesterday and now it is bricked. A "HTC" log is shown up and frozen in the display, not able to shutdown the phone by pressing anything.
I asked my son what he did, but he didnt say anything as he is afraid of punishment
what I can do is try to remove the battery, then hold the volume down key and power key, then it brings up this screen:
***Tampered***
***Unlocked***
ZARA_C PVT SHIP S-ON RL
HBOOT-2.20.0000
RADIO-1.14.50.1003
OpenDSP-v16.2.0268.noBeats.0902
OS-1.10.652.9
eMMC-boot 1024MB
Oct 7 2013 18:39.56.0
HBOOT
<vol_up>to previewitem
<vol_down> to next item
<power> to select item
Fastboot
Recovery
Factory reset
CLEAR storage
SIMLOCK
Image CRC
Show barcode
after I press "recovery", it enter this page::
Team Win Recovery project v2.7.1.1(kk)
Install Wipe
Backup Restore
Mount Settings
Advanced Reboot
what I want to to go back to the stock Virgin Mobile ROM. what should I do? thanks.
I'm assuming you don't have a backup... Try a factory reset from twrp, if that didn't help seek out a zara_cl backup
attrunner said:
I have a HTC desire 601 bought this Summer from Virgin Mobile USA, a CDMA based carrier using Sprint network. My son played with it yesterday and now it is bricked. A "HTC" log is shown up and frozen in the display, not able to shutdown the phone by pressing anything.
I asked my son what he did, but he didnt say anything as he is afraid of punishment
what I can do is try to remove the battery, then hold the volume down key and power key, then it brings up this screen:
***Tampered***
***Unlocked***
ZARA_C PVT SHIP S-ON RL
HBOOT-2.20.0000
RADIO-1.14.50.1003
OpenDSP-v16.2.0268.noBeats.0902
OS-1.10.652.9
eMMC-boot 1024MB
Oct 7 2013 18:39.56.0
HBOOT
<vol_up>to previewitem
<vol_down> to next item
<power> to select item
Fastboot
Recovery
Factory reset
CLEAR storage
SIMLOCK
Image CRC
Show barcode
after I press "recovery", it enter this page::
Team Win Recovery project v2.7.1.1(kk)
Install Wipe
Backup Restore
Mount Settings
Advanced Reboot
what I want to to go back to the stock Virgin Mobile ROM. what should I do? thanks.
Click to expand...
Click to collapse
You're still on the old firmware so you can simply use the RUU which can be downloaded from my Drive.
Re-reading your post I see a problem - You installed the KitKat recovery on your device but your device is still Jelly Bean. As stated in the thread, you want the official version from TWRP's site if you're still on Jelly Bean
-Duir- said:
You're still on the old firmware so you can simply use the RUU which can be downloaded from my Drive[/URL].
Re-reading your post I see a problem - You installed the KitKat recovery on your device but your device is still Jelly Bean. As stated in the thread, you want the official version from TWRP's site if you're still on Jelly Bean
Click to expand...
Click to collapse
sir, can you show me where did you see it's Kitkat recovery on my device, and where did you see it's still Jelly bean? I am still leaning.
attrunner said:
sir, can you show me where did you see it's Kitkat recovery on my device, and where did you see it's still Jelly bean? I am still leaning.
Click to expand...
Click to collapse
Team Win Recovery project v2.7.1.1(kk)
^^where it says "kk" at the end means that is a kitkat recovery.
Sent from my cdma Virgin Mobile HTC Desire 601 zara_cl
Hedied4me said:
Team Win Recovery project v2.7.1.1(kk)
^^where it says "kk" at the end means that is a kitkat recovery.
Sent from my cdma Virgin Mobile HTC Desire 601 zara_cl
Click to expand...
Click to collapse
where it shows it's jelly bean? thank you very much.
attrunner said:
where it shows it's jelly bean? thank you very much.
Click to expand...
Click to collapse
The OS version in your post is Jelly Bean.
-Duir- said:
You're still on the old firmware so you can simply use the RUU which can be downloaded from my Drive.
Re-reading your post I see a problem - You installed the KitKat recovery on your device but your device is still Jelly Bean. As stated in the thread, you want the official version from TWRP's site if you're still on Jelly Bean
Click to expand...
Click to collapse
sir, This is what I did:
1 I tried to use the RUU (file name RUU_ZARA_CL_JB422_SENSE50_Sprint_WWE_VM_1.10.652.9_Radio_1.14.50.1003_NV_SPCS_5.17_003_PRL55009_release_337148_signed_2.exe), but after the RUU erase data, and trying to send data, it has error message:
ERROR[155]: unknown error.
The ROM Update Utility can not update your Android phone.
Please get the correct ROM update utility and try again.
2 I tried different TWRP version as recovery, then use your RUU, all failed as step 1.
openrecovery-twrp-2.6.3.0-zaracl
openrecovery-twrp-2.7.0.0-zaracl
openrecovery-twrp-2.7.1.0-zaracl
3. I tried a stock ROM in Google dirve:
/folderview?id=0B-kSF8g8H7KuME12ai1OVHVqd3M&usp=sharing#list
I chose file JB_stock_system_dump.zip, tried to copy to external SD card and install from recovery, but failed.
So please help what should I try next. thank you very much
attrunner said:
sir, This is what I did:
1 I tried to use the RUU (file name RUU_ZARA_CL_JB422_SENSE50_Sprint_WWE_VM_1.10.652.9_Radio_1.14.50.1003_NV_SPCS_5.17_003_PRL55009_release_337148_signed_2.exe), but after the RUU erase data, and trying to send data, it has error message:
ERROR[155]: unknown error.
The ROM Update Utility can not update your Android phone.
Please get the correct ROM update utility and try again.
2 I tried different TWRP version as recovery, then use your RUU, all failed as step 1.
openrecovery-twrp-2.6.3.0-zaracl
openrecovery-twrp-2.7.0.0-zaracl
openrecovery-twrp-2.7.1.0-zaracl
3. I tried a stock ROM in Google dirve:
/folderview?id=0B-kSF8g8H7KuME12ai1OVHVqd3M&usp=sharing#list
I chose file JB_stock_system_dump.zip, tried to copy to external SD card and install from recovery, but failed.
So please help what should I try next. thank you very much
Click to expand...
Click to collapse
Lock the bootloader and then run it.
Also:
Custom recovery does not affect the RUU.
The system dump zip is literally that, a dump of the system partition. As such, it's not recovery flashable.
-Duir- said:
Lock the bootloader and then run it.
Also:
Custom recovery does not affect the RUU.
The system dump zip is literally that, a dump of the system partition. As such, it's not recovery flashable.
Click to expand...
Click to collapse
Don't lock the boot loader, that's not why the ruu is failing.
You need to change the mid first
mrplowdan said:
Don't lock the boot loader, that's not why the ruu is failing.
You need to change the mid first
Click to expand...
Click to collapse
That's exactly why it's failing. You need to be relocked to run the RUU.
-Duir- said:
That's exactly why it's failing. You need to be relocked to run the RUU.
Click to expand...
Click to collapse
Perhaps its different for the cl varient but for my ul, I'm 100% positive you don't need to be relocked. However, mid and cid must match the ruu.
*edit*
Also your hboot must be older or the same version as the ruu's hboot
mrplowdan said:
Perhaps its different for the cl varient but for my ul, I'm 100% positive you don't need to be relocked. However, mid and cid must match the ruu.
*edit*
Also your hboot must be older or the same version as the ruu's hboot
Click to expand...
Click to collapse
Well, they have the Virgin Mobile zara_cl variant which the RUU is made for, so the mid and cid shouldn't be an issue since they're S-ON and can't change it. Also, as stated their using 4.2.2. They still have the old firmware and partition layout which is why the version of twrp they installed won't work so hboot version is also not an issue. Also, it throws a different error if your device has a newer hboot than the RUU.
While it's not entirely outside the realm of possibility that something else could be causing the error, it's definitely not hboot version or mid/cid.
Were you S-OFF when you ran RUU on unlocked bootloader? I'm not sure of all the benefits of being S-OFF, but maybe one is being able to RUU with an unlocked bootloader. It makes perfect sense for an unlocked bootloader to throw an error since it can void your warranty and RUUs are generally ran by service techs.
But in all my experience the bootloader needs to be locked/relocked for the RUU to run.
-Duir- said:
... Were you S-OFF when you ran RUU on unlocked bootloader? I'm not sure of all the benefits of being S-OFF, but maybe one is being able to RUU with an unlocked bootloader. It makes perfect sense for an unlocked bootloader to throw an error since it can void your warranty and RUUs are generally ran by service techs.
But in all my experience the bootloader needs to be locked/relocked for the RUU to run.
Click to expand...
Click to collapse
I haven't tried running the ruu while s-on. I'm pretty sure the distinction is if your s-off you can flash ruu zips (which don't have the mid/cid requirements) after running fastboot oem rebootRUU as well as the standard exe RUUs, and if your s-on you can only run exe RUUs.
Hey, guys. I've finally made an account here after clumsily stepping into the world of custom ROMs. I recently got a Zara_CL on Virgin mobile and somehow wound up in the same position as the OP here. I never updated to KitKat due to the update failing with a custom recovery image. After unlocking the bootloader, I installed TWRP 2.7.1.1 and tried to flash InstertCoin yesterday without making a backup (couldn't mount certain partitions and now I know why ^_^). It took many hours to figure out what I did wrong and to make many plans of action to fix those mistakes.
I have re-locked my bootloader and the RUU has allowed me to get the stock Jellybean ROM back on my phone. I tried before while still unlocked and the RUU made no progress at all.
From what I've experienced, S-OFF and Unlocked are sort of interchangeable on a device in this stage of being cracked. One can flash recoveries with S-OFF and a locked loader, or with S-ON and an unlocked loader. I'm still learning after a few months and a successful root, s-off, and rom flash on an ancient EVO 3D. The high of that success drove me to buy this phone and try some magic on it, but my conjuration skills are quite unpolished.
To OP: Relock your bootloader with fastboot command "oem lock" and then run the RUU you found here. This should resurrect your handset flawlessly as it did in my situation. Don't punish your son, but teach him to be more careful. We both learned the hard way, but I guess I learned more quickly.
I had to always lock bootloader before running ruu. Would always get same error otherwise. This was for s-on. I can't remember my one experience running ruu while s-off.
Sent from my cdma Virgin Mobile HTC Desire 601 zara_cl
Hedied4me said:
I had to always lock bootloader before running ruu. Would always get same error otherwise. This was for s-on. I can't remember my one experience running ruu while s-off.
Sent from my cdma Virgin Mobile HTC Desire 601 zara_cl
Click to expand...
Click to collapse
How to lock bootloader? I only know how to unlock.
Get into boot loader and type "oem lock" into adb/command prompt.
attrunner said:
How to lock bootloader? I only know how to unlock.
Click to expand...
Click to collapse
You're phone needs to be in fastboot mode.
You need adb on your computer and to run a command prompt from your adb folder. Plug your phone into the computer and from the command prompt type "fastboot oem lock" and press enter. You're bootloader will now be locked. If you get a message about too many flags or something and a security warning afterwards, don't worry, it worked.