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!
Related
Ok, i post it because i think i've read it all and still no fix.
I have 1.5 hboot S-ON HTCUnlocked, custom recovery.
putting the ruu in the SD does not work (unlocked or relocked)
when relocked there is a security warning and the phone doesn't boot, only bootloader.
Stock Rom and htc update just end in the red "!" symbol because i have custom recovery.
I flashed a "stock recovery" i downloaded using fastboot, same problem.
So, does anyone in the same circumstances have succided updating the firmware, antennas, etc?
fcomeba said:
Ok, i post it because i think i've read it all and still no fix.
I have 1.5 hboot S-ON HTCUnlocked, custom recovery.
putting the ruu in the SD does not work (unlocked or relocked)
when relocked there is a security warning and the phone doesn't boot, only bootloader.
Stock Rom and htc update just end in the red "!" symbol because i have custom recovery.
I flashed a "stock recovery" i downloaded using fastboot, same problem.
So, does anyone in the same circumstances have succided updating the firmware, antennas, etc?
Click to expand...
Click to collapse
extract all the .img files from the RUU zip and flash them one by one using fastboot. That should work.
Try to flash in this order (you must be unlocked again): boot, system & userdata. let it boot then access again fastboot and then flash recovery.
lets see what happens.
Thanks
Well I just solve the problem, i expect it help some people in the future.
I had tu relock it again using fastboot oem lock.
download the RUU exe format.
I couldn'y run the OS because relocked and I think the custom roms previously installed by myself messed something so I couldn't start "relocked"
So start the phone in Bootloader (holding down button).
Relock using fastboot oem lock
Once relocked run the RUU app on your computer (It wont read your actual firmware, antennas, etc... just tell you the ones it will update).
Follow the instructions and Voila, your are updated...
So the bottom lines are:
being locked (relocked) no matter what, and run the RUU app because it won't ask for the recovery image installed.
Thanks megabiteg I would like to try your method but my phone is already fixed.
What computer app you talkin about I need to update mine
Sent from my PG86100 using xda premium
search for this
It's like a RUU PC Version.
the one i used was named:
RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed
Google it, i hope you'll find it.
I think WWE_2.17.651.5 is the lastest update, you could also apply an older version, just search for it.
Also follow my instruction, i couldn't get my phone updated with other method
I have directions for both the .exe & zip versions in the guide/flashing notes in my signature. Post 1.5
Sent from my PG86100 using Tapatalk
fcomeba said:
Well I just solve the problem, i expect it help some people in the future.
I had tu relock it again using fastboot oem lock.
download the RUU exe format.
I couldn'y run the OS because relocked and I think the custom roms previously installed by myself messed something so I couldn't start "relocked"
So start the phone in Bootloader (holding down button).
Relock using fastboot oem lock
Once relocked run the RUU app on your computer (It wont read your actual firmware, antennas, etc... just tell you the ones it will update).
Follow the instructions and Voila, your are updated...
So the bottom lines are:
being locked (relocked) no matter what, and run the RUU app because it won't ask for the recovery image installed.
Thanks megabiteg I would like to try your method but my phone is already fixed.
Click to expand...
Click to collapse
I am about to try this because I have been having the exact same problem. I have been trying to update my phone for the past 4 days and I am just about through with trying.
It worked! If any one else needs the .exe here is the link.
goo-inside.me/devs/zanzibar/Shooter/RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed.exe
fcomeba said:
Well I just solve the problem, i expect it help some people in the future.
I had tu relock it again using fastboot oem lock.
download the RUU exe format.
I couldn'y run the OS because relocked and I think the custom roms previously installed by myself messed something so I couldn't start "relocked"
So start the phone in Bootloader (holding down button).
Relock using fastboot oem lock
Once relocked run the RUU app on your computer (It wont read your actual firmware, antennas, etc... just tell you the ones it will update).
Follow the instructions and Voila, your are updated...
So the bottom lines are:
being locked (relocked) no matter what, and run the RUU app because it won't ask for the recovery image installed.
Thanks megabiteg I would like to try your method but my phone is already fixed.
Click to expand...
Click to collapse
There's stickies on this you know.. could've saved yourself a lot of time.
G.Newton said:
There's stickies on this you know.. could've saved yourself a lot of time.
Click to expand...
Click to collapse
Yep, and the guide in my signature that I suggested has links to the stickied threads also.
Hi guys,
I have rooted, S-OFF, 4EXT recovery, SuperCID, running Stock T-Mobile ICS HTC Amaze. My current configuration is
SHIP S-OFF
HBOOT 1.93.2222
Radio_1.14.550L.17DC_30.78.550L.15
I have searched "Amaze how to revert to stock" from within the forum and google as well but the answers came up so confuse and not very clear. So I dare to oen a new thread here asking for help. Somebody else might looking for the same thing.
Basically I want to go back to T-Mobile Stock Gingerbread. I have:
Hasson AllinOne V3.1,
PH85IMG_Ruby_TMOUS_1.43.531.3_Radio_1.08.550L.19DC_30.66.550L.08D_release_228638_signed
How would I safely going back to stock?
I know I have to flash the PH85IMG_Ruby_TMOUS_1.43.531.3 via fastboot as the last step but what step should I take first? Flash the stock bootloader first or flash the stock recovery first?
Any advice would be appriciated
Im S-on so idk if its different.
download this: http://www.filefactory.com/file/c0d...19DC_30.66.550L.08D_release_228638_signed.zip
idk if its the same one you have but just download it just in case, and RENAME IT to PH85IMG.
AFter that put it in your sd and boot into bootloader and then fastboot so it reads that file. then just click yes to the update and you are set.
^^ will that "update" revert EVERYthing back to s-on, shipped bootloader and recovery?
Will it revert the radio as well?
You might need to run the Mainver Error Fix in the all-in-one toolkit. It "spoofs your software version so you can downgrade your ROM."
Hasoon can correct me on this if I'm wrong.
kered424 said:
You might need to run the Mainver Error Fix in the all-in-one toolkit. It "spoofs your software version so you can downgrade your ROM."
Hasoon can correct me on this if I'm wrong.
Click to expand...
Click to collapse
Thanks. I tried this, running the mainver error fix, but it fails, saying device not found. I ran this with the phone connected to the computer via usb, and the phone in fastboot.
aiwapro said:
Thanks. I tried this, running the mainver error fix, but it fails, saying device not found. I ran this with the phone connected to the computer via usb, and the phone in fastboot.
Click to expand...
Click to collapse
Someone PLEASE reply to this gentlemen. This is the exact same problem I'm having at the moment, and have been for a week. I've looked high and low, and was on the verge of creating a new thread.
Just flash the stock file you have via hboot by renaming it to PH85IMG and placing it on your sdcard.
Dark Nightmare said:
Just flash the stock file you have via hboot by renaming it to PH85IMG and placing it on your sdcard.
Click to expand...
Click to collapse
This is the same process I've been following. When I flash the stock file, I get the Mainver Error. When I try using Hasoon's Mainver Error Fix, command prompt tells me the device isnt found. I get no further than this.
Sylvaeria said:
This is the same process I've been following. When I flash the stock file, I get the Mainver Error. When I try using Hasoon's Mainver Error Fix, command prompt tells me the device isnt found. I get no further than this.
Click to expand...
Click to collapse
Is the device in fastboot mode?
Are you s-on or s-off?
Also are you on GB or ICS?
Dark Nightmare said:
Is the device in fastboot mode?
Are you s-on or s-off?
Also are you on GB or ICS?
Click to expand...
Click to collapse
Fastboot.
This was my first root, and I've done nothing to mess around with anything related to security, so I'm gonna say S-On.
And I'm currently on ICS.
Sylvaeria said:
Fastboot.
This was my first root, and I've done nothing to mess around with anything related to security, so I'm gonna say S-On.
And I'm currently on ICS.
Click to expand...
Click to collapse
If you're on ICS, you cannot revert to GB, so your best option would be to flash a custom recovery, 4EXT recommended and look in the dev section for Hasoon2000's thread of stock zip files, download the carrier file that's for your device and flash that via a custom recovery, since T-Mobile is the only carrier we have bootloader flashable ruu files.
Dark Nightmare said:
If you're on ICS, you cannot revert to GB, so your best option would be to flash a custom recovery, 4EXT recommended and look in the dev section for Hasoon2000's thread of stock zip files, download the carrier file that's for your device and flash that via a custom recovery, since T-Mobile is the only carrier we have bootloader flashable ruu files.
Click to expand...
Click to collapse
I actually meant I was flashing to stock ICS. I just posted here for sake of simplicity. I have all of this ready to go already. Recovery and stock .zip. The only problem left is that the Mainver Fix in Hasoon's AIOT doesn't detect my device. I heard the fix for this is enabling USB Debugging, but I cannot do that since I get a permanent whitescreen after I boot up my device, and I've unlocked/relocked my bootloader and it reset the USB Debugging option. I feel like I'm pretty screwed at this point. Definitely not giving up, though.
Sylvaeria said:
I actually meant I was flashing to stock ICS. I just posted here for sake of simplicity. I have all of this ready to go already. Recovery and stock .zip. The only problem left is that the Mainver Fix in Hasoon's AIOT doesn't detect my device. I heard the fix for this is enabling USB Debugging, but I cannot do that since I get a permanent whitescreen after I boot up my device, and I've unlocked/relocked my bootloader and it reset the USB Debugging option. I feel like I'm pretty screwed at this point. Definitely not giving up, though.
Click to expand...
Click to collapse
What is your device's bootloader version and what carrier are you on?
You're going around in circles and that's not exactly gonna solve the problem atm.
Dark Nightmare said:
What is your device's bootloader version and what carrier are you on?
You're going around in circles and that's not exactly gonna solve the problem atm.
Click to expand...
Click to collapse
No kidding. T-Mobile. Not sure how to check version, so this is what I see:
RUBY PVT SHIP S-ON (Welp, I guess I got it right) RL
HBOOT-1 1.93.0002 (Assuming this is it?)
Open ADSP-v02.6.0.2226.00.0202
eMMC-boot
Mar 15 2012, 21:46:51
Sylvaeria said:
No kidding. T-Mobile. Not sure how to check version, so this is what I see:
RUBY PVT SHIP S-ON (Welp, I guess I got it right) RL
HBOOT-1 1.93.0002 (Assuming this is it?)
Open ADSP-v02.6.0.2226.00.0202
eMMC-boot
Mar 15 2012, 21:46:51
Click to expand...
Click to collapse
Download this file: http://d-h.st/3VD
Relock your devices bootloader, put the device into fastboot, get hasoon's tool ver 3.2, or whatever the latest atm is, relock/lock the bootloader command.
rename that file PH85IMG exactly like that, put it on your sdcard, not your phone memory, do not extract it or place it into any folders, reboot into bootloader, volume up to update.
Let it boot completely at least once before attempting to root/flashing a custom rom.
Going for it. Thanks for the help so far. I'll report back soon.
Okie dokie artichokie.
Dark Nightmare said:
Download this file: http://d-h.st/3VD
Relock your devices bootloader, put the device into fastboot, get hasoon's tool ver 3.2, or whatever the latest atm is, relock/lock the bootloader command.
rename that file PH85IMG exactly like that, put it on your sdcard, not your phone memory, do not extract it or place it into any folders, reboot into bootloader, volume up to update.
Let it boot completely at least once before attempting to root/flashing a custom rom.
Click to expand...
Click to collapse
You, sir, are a god among men. Thank you SO much. Is there any way I can thank you twice?
Sylvaeria said:
You, sir, are a god among men. Thank you SO much. Is there any way I can thank you twice?
Click to expand...
Click to collapse
Lol, you're welcome, happy you got it resolved, have fun.
hey yall i used the htc dev method to unluck the sprint 3d however when i do the flash recovery img in fastboot i get a failed remote not allowed- i have done this on other phones with no issue but i have tried every recovery.img with no luck . i also tried the PG86IMG but it just says either main version older or PARSING . ant help is MUCH appreciated.
ganjamatik said:
hey yall i used the htc dev method to unluck the sprint 3d however when i do the flash recovery img in fastboot i get a failed remote not allowed- i have done this on other phones with no issue but i have tried every recovery.img with no luck . i also tried the PG86IMG but it just says either main version older or PARSING . ant help is MUCH appreciated.
Click to expand...
Click to collapse
What exactly does your bootloader say? It sounds like it is not unlocked.
If you relocked to run the RUU.exe or take the OTA update it may not be locked now.
ramjet73
ramjet73 said:
What exactly does your bootloader say? It sounds like it is not unlocked.
If you relocked to run the RUU.exe or take the OTA update it may not be locked now.
ramjet73
Click to expand...
Click to collapse
its shows UNLOCKED and hboot 1.58 s-on
ganjamatik said:
its shows UNLOCKED and hboot 1.58 s-on
Click to expand...
Click to collapse
Hmmm...
Well, you won't be able to flash PG86IMG.zip files from the bootloader with S-ON unless thay are signed by HTC so that's probably your problem there.
The "remote not allowed" is usually an indication the bootloader is locked. Make sure your phone is in "fastboot usb" mode in the bootloader, then issue the following commands:
fastboot devices
fastboot flash recovery recovery.img (where "recovery.img" is the file name of your custom recovery)
What responses do you get?
ramjet73
it shows my device listed and then says the same remote not allowed-
Did you check usb debugging in your phone's settings first? Also if you have htc sync on your pc you may want to unistall it also. Some programs do interfere with fastboot.
ganjamatik said:
it shows my device listed and then says the same remote not allowed-
Click to expand...
Click to collapse
Can you try those fastboot commands again and copy and paste the actual output from the commands into this thread? Sometimes there is something in that which might give us a clue as to what the problem is.
Edit: Never mind. I saw you posted again in the other thread so you can wait for a response over there. Make 100% sure your bootloader is unlocked because sometimes flashing the unlock bin file doesn't take and the phone doesn't show the unlock option if you upgraded to ICS via the OTA. If nothing else works I would suggest relocking the bootloader and starting over with the RUU.exe, per the instructions in my root and S-OFF guide.
ramjet73
From the other thread
mpgrimm2 said:
My guess is that you are not really unlocked (Screenshot?) or you are not using a compatible recovery file/filename.
Have a look at the HTC Unlock Guide in my signature to see if anything stands out that you are overlooking.
Even if you get a recovery going, I'm not sure what your ultimate goal is here. You should continue this in one thread, specifically your Remote Not Allowed thread.
Click to expand...
Click to collapse
Go with Ramjet's suggestion if you don't figure it out.
Semi-noob here, would appreciate any help!
S-Off using revone, flashed CWM, and then ROM'd. Found an issue with the phone (wireless charger not working), so need to return to stock before bringing to Verizon. Used adb to S-On, and now, I am STUCK in Fastboot (or is it called Hboot?)!
None of the "options in Fastboot do anything (Bootloader, Reboot, Reboot Bootloader, Factory Reset). I can't get anywhere past Fastboot!
I think my problem was that I did not flash the stock ROM first, before S-on again. The phone no longer goes into Bootloader, so I don't know how to flash a ROM at this point.
Any help would be majorly appreciated! Thank you, oh wise ones...
geeDoh said:
Semi-noob here, would appreciate any help!
S-Off using revone, flashed CWM, and then ROM'd. Found an issue with the phone (wireless charger not working), so need to return to stock before bringing to Verizon. Used adb to S-On, and now, I am STUCK in Fastboot (or is it called Hboot?)!
None of the "options in Fastboot do anything (Bootloader, Reboot, Reboot Bootloader, Factory Reset). I can't get anywhere past Fastboot!
I think my problem was that I did not flash the stock ROM first, before S-on again. The phone no longer goes into Bootloader, so I don't know how to flash a ROM at this point.
Any help would be majorly appreciated! Thank you, oh wise ones...
Click to expand...
Click to collapse
The good news is, if you really are stuck in fastboot, you can still use adb/fastboot commands to get your phone working again. There is an important distinction between fastboot and hboot, though: fastboot is basically the bootloader's "debug" mode, while hboot is the regular bootloader mode. You won't be able to do much if your bootloader says "hboot" above the available options, but if it says "fastboot" or "fastboot usb" you're fine.
You should try to get s-off again (assuming you haven't relocked your bootloader) either via revone or facepalm, then flash a stock rom and proceed from there.
Clarification: if you have relocked your bootloader, unlock, then get s-off.
Used adb to S-On? Meaning what exactly? Did you lock beforehand?
I currently have S-on. I used revone's method to S-off.
I think the problem is that I have relocked the bootloader (phone shows LOCKED) with a custom ROM installed. I think I should have flashed a stock ROM before relocking. Would this have caused the problem I'm having?
I am not sure how to get S-off again, because I am stuck on the FASTBOOT. Selecting Bootloader/Reboot/Reboot Bootloader just returns me to the same screen. When I try to enter any line items (in Terminal), adb says there are no devices connected (this is probably due to the fact that my phone no longer boots to the homescreen). Any suggestions of how to get S-off again??
Thanks...
What method did you use for S-ON? There are guides here that lay out every step needed to return to stock.
Also when in fastboot, you need to use fastboot, not adb. Type in fastboot devices. Does your device ID show?
I would suggest trying to run the RUU. Although it may not work depending on HBOOT version and the fact you are now S-ON.
Can you boot into Recovery? If so, is there a ROM still on the phone? If so, try flashing it...
geeDoh said:
I currently have S-on. I used revone's method to S-off.
I think the problem is that I have relocked the bootloader (phone shows LOCKED) with a custom ROM installed. I think I should have flashed a stock ROM before relocking. Would this have caused the problem I'm having?
I am not sure how to get S-off again, because I am stuck on the FASTBOOT. Selecting Bootloader/Reboot/Reboot Bootloader just returns me to the same screen. When I try to enter any line items (in Terminal), adb says there are no devices connected (this is probably due to the fact that my phone no longer boots to the homescreen). Any suggestions of how to get S-off again??
Thanks...
Click to expand...
Click to collapse
Does the unit show up in device manager? You may need to install a driver.
Phaded said:
What method did you use for S-ON? There are guides here that lay out every step needed to return to stock.
Also when in fastboot, you need to use fastboot, not adb. Type in fastboot devices. Does your device ID show?
I would suggest trying to run the RUU. Although it may not work depending on HBOOT version and the fact you are now S-ON.
Can you boot into Recovery? If so, is there a ROM still on the phone? If so, try flashing it...
Click to expand...
Click to collapse
Oh, using Fastboot gave me my device ID. What can I do now??
I can't get into Recovery from Fastboot USB. The option for Bootloader and Reboot Bootloader are there, but selecting them just returns me to Fastboot USB. I assume this is because I am already S-On again...?
geeDoh said:
Oh, using Fastboot gave me my device ID. What can I do now??
I can't get into Recovery from Fastboot USB. The option for Bootloader and Reboot Bootloader are there, but selecting them just returns me to Fastboot USB. I assume this is because I am already S-On again...?
Click to expand...
Click to collapse
Select bootloader, then recovery. The menus look the same, but they are different.
If you can boot into recovery, what is it? Stock or custom?
Phaded said:
Select bootloader, then recovery. The menus look the same, but they are different.
If you can boot into recovery, what is it? Stock or custom?
Click to expand...
Click to collapse
When I select Bootloader -> Recovery, the HTC screen flashes, then I'm returned to Fastboot USB.
geeDoh said:
When I select Bootloader -> Recovery, the HTC screen flashes, then I'm returned to Fastboot USB.
Click to expand...
Click to collapse
That's because you have unsigned boot.img and/or recovery and relocked the device.
You need to RUU or unlock again to boot to anything.
Any tips on how to unlock again? (and once I am unlocked, i assume I need to load Recovery, and from there, flash a stock ROM?)
geeDoh said:
Any tips on how to unlock again? (and once I am unlocked, i assume I need to load Recovery, and from there, flash a stock ROM?)
Click to expand...
Click to collapse
Run Moonshine.
If that fails, RUU to stock.
You didn't happen to make an unlock_code.bin with htc did you?
No, i didn't. Not even sure what that is...haha...
I'm going to run RUU, and hope that works! Thanks for everyones input...
still no luck! =T
So, I've tried running RUU (this is the RUU file I'm using: RUU_DLX_WL_JB_45_VERIZON_WWE_1.15.605.4_Radio_1.00.00.1023_3_NV_VZW_1.98_002_release_290923_signed), but after it runs for a while (it says it is erasing data, then sending to the phone),
RUU says I am currently on 2.06, so is this the correct RUU file?
Another option for me, other than putting the phone back to stock, is for me to completely brick it. I tried unplugging and powering off the phone while RUU was running, but it still comes back to Fastboot. Suggestions?
Thanks again....
geeDoh said:
So, I've tried running RUU (this is the RUU file I'm using: RUU_DLX_WL_JB_45_VERIZON_WWE_1.15.605.4_Radio_1.00.00.1023_3_NV_VZW_1.98_002_release_290923_signed), but after it runs for a while (it says it is erasing data, then sending to the phone),
RUU says I am currently on 2.06, so is this the correct RUU file?
Another option for me, other than putting the phone back to stock, is for me to completely brick it. I tried unplugging and powering off the phone while RUU was running, but it still comes back to Fastboot. Suggestions?
Thanks again....
Click to expand...
Click to collapse
Just run the RUU. There is only one RUU. You are on 2.06, that's why it tells you that. Let the whole thing run.
You cannot downgrade via RUU. You need to unlock the phone, s-off it (facepalm should suffice) then you can RUU back to 1.15 if you choose.
beaups said:
You cannot downgrade via RUU. You need to unlock the phone, s-off it (facepalm should suffice) then you can RUU back to 1.15 if you choose.
Click to expand...
Click to collapse
Ah forgot he went back to S-On.
Phaded said:
Ah forgot he went back to S-On.
Click to expand...
Click to collapse
I have the same problem. Since it was relocked, the htc dev site can't give the bin file to unlock it again. So I'm stuck in fastboot usb mode and I can't do anything about it. If only I can unlock it again, then I can move on from there.
okyere said:
I have the same problem. Since it was relocked, the htc dev site can't give the bin file to unlock it again. So I'm stuck in fastboot usb mode and I can't do anything about it. If only I can unlock it again, then I can move on from there.
Click to expand...
Click to collapse
Still have the token? Or the email that it got sent in?
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