I am stuck in HBOOT after after fastboot oem lock from cmd
Now reads:
RELOCKED
Security Warning
HBOOT 2.10
Radio -0.95.00.1017_2r/0.95.00.1013r
OpenDSP-v10.6.0.7611.00.0919
Reboot sends me back..
Power Down ..reboots to HBOOT
Can I run RUU via pc? Is this>>> WWE_1.02.605.6_Radio_RS_0.95.00.1013r_3161E_9K_NV_8k_1.12_9k_1.83_V_APT_release_2215<<< the correct version?
If so..How do i enter RUU mode??
Please Help! Thanks
drknrgy said:
I am stuck in HBOOT after after fastboot oem lock from cmd
Now reads:
RELOCKED
Security Warning
HBOOT 2.10
Radio -0.95.00.1017_2r/0.95.00.1013r
OpenDSP-v10.6.0.7611.00.0919
Reboot sends me back..
Power Down ..reboots to HBOOT
Can I run RUU via pc? Is this>>> WWE_1.02.605.6_Radio_RS_0.95.00.1013r_3161E_9K_NV_8k_1.12_9k_1.83_V_APT_release_2215<<< the correct version?
If so..How do i enter RUU mode??
Please Help! Thanks
Click to expand...
Click to collapse
you can pull the rom.zip from the ruu, and run that in hboot.. or just unlock the bootloader again
drknrgy said:
I am stuck in HBOOT after after fastboot oem lock from cmd
Now reads:
RELOCKED
Security Warning
HBOOT 2.10
Radio -0.95.00.1017_2r/0.95.00.1013r
OpenDSP-v10.6.0.7611.00.0919
Reboot sends me back..
Power Down ..reboots to HBOOT
Can I run RUU via pc? Is this>>> WWE_1.02.605.6_Radio_RS_0.95.00.1013r_3161E_9K_NV_8k_1.12_9k_1.83_V_APT_release_2215<<< the correct version?
If so..How do i enter RUU mode??
Please Help! Thanks
Click to expand...
Click to collapse
Yes, you can run the RUU via pc in fastboot. That's how I ran it . Just as long as it says fastbootusb , it will work.
I was stuck in Hboot as well.. so not sure how you avoid it. Easy enough to run the RUU out of fastboot though.
andybones said:
you can pull the rom.zip from the ruu, and run that in hboot.. or just unlock the bootloader again
Click to expand...
Click to collapse
Can I run the RUU.exe directly on pc while in fastboot usb?
"you can pull the rom.zip from the ruu, and run that in hboot." not sure what that means if you run RUU.exe on pc How could I "pull the rom.zip from the ruu" if I cant run recovery??
Never ran RUU
Ok Just to make sure then.. Am I running the correct RUU? Will this further effect me if trying to run the wrong RUU file ? I guess my question is, to be more specific, does my listed RADIO in hboot need the correct RUU file ??
drknrgy said:
Ok Just to make sure then.. Am I running the correct RUU? Will this further effect me if trying to run the wrong RUU file ? I guess my question is, to be more specific, does my listed RADIO in hboot need the correct RUU file ??
Click to expand...
Click to collapse
It won't let you run the wrong RUU.. if you havent taken the OTA yet, the correct RUU is 1.06.xxxxx
Yes, you run the exe on the PC while in fastboot.
mjh68 said:
It won't let you run the wrong RUU.. if you havent taken the OTA yet, the correct RUU is 1.06.xxxxx
Yes, you run the exe on the PC while in fastboot.
Click to expand...
Click to collapse
Is there a way to determine the correct RUU? This one>>>>
WWE_1.02.605.6_Radio_RS_0.95.00.1013r_3161E_9K_NV_ 8k_1.12_9k_1.83_V_APT_release_2215<<<<
FAILED
"ERROR [140] BOOTLOADER VERSION ERROR"
Would the latest > new RUU for 2.01.605.11 < WorK?
drknrgy said:
Is there a way to determine the correct RUU? This one>>>>
WWE_1.02.605.6_Radio_RS_0.95.00.1013r_3161E_9K_NV_ 8k_1.12_9k_1.83_V_APT_release_2215<<<<
FAILED
"ERROR [140] BOOTLOADER VERSION ERROR"
Would the latest > new RUU for 2.01.605.11 < WorK?
Click to expand...
Click to collapse
Did you update with the OTA or have your main ver updated ? Sounds like you had a partial update with the bootloader being updated to 2.11 maybe.
Try the new RUU see if it will run it.
mjh68 said:
Did you update with the OTA or have your main ver updated ? Sounds like you had a partial update with the bootloader being updated to 2.11 maybe.
Try the new RUU see if it will run it.
Click to expand...
Click to collapse
I do not have the new OTA. I was root/unlocked. I tried doing wipe from ra and then run CleanRom GBE 1.6OTA zip from sd. Then I think I ran fastboot boot.img...
I have lost track of my steps at this point but the bootloader still states HBOOT-2.10.0000 on the white security warning screen w/3 droids at the bottom
BTW...Is there a direct link for new RUU available? DpBox??
drknrgy said:
I do not have the new OTA. I was root/unlocked. I tried doing wipe from ra and then run CleanRom GBE 1.6OTA zip from sd. Then I think I ran fastboot boot.img...
I have lost track of my steps at this point but the bootloader still states HBOOT-2.10.0000 on the white security warning screen w/3 droids at the bottom
BTW...Is there a direct link for new RUU available? DpBox??
Click to expand...
Click to collapse
It is in the developement forum.. Sticky thread for the Vigor rom collection. It was on the last page.. might have been bumped back a page or so.
Hmm , not sure why it is giving you that error if you still have hboot 2.10 , let me check and make sure that first RUU was the right one. Yes, you quoted the same RUU I used when I did the process.
mjh68 said:
It is in the developement forum.. Sticky thread for the Vigor rom collection. It was on the last page.. might have been bumped back a page or so.
Hmm , not sure why it is giving you that error if you still have hboot 2.10 , let me check and make sure that first RUU was the right one. Yes, you quoted the same RUU I used when I did the process.
Click to expand...
Click to collapse
Thanks for the D/L on the latest RUU.. almost finished. If I run this one via .exe and still get a failure re: bootloader what are my other options? I have other options don't I? Can I use a cmd to "push"? Any ideas? Thanks for all the help!
before running the RUU...
current image Version:
2.01.605.11
(same as latest RUU) crossing fingers now..
drknrgy said:
Thanks for the D/L on the latest RUU.. almost finished. If I run this one via .exe and still get a failure re: bootloader what are my other options? I have other options don't I? Can I use a cmd to "push"? Any ideas? Thanks for all the help!
before running the RUU...
current image Version:
2.01.605.11
(same as latest RUU) crossing fingers now..
Click to expand...
Click to collapse
Looks like somehow your mainver did get updated so the newest RUU should work. If this one fails I am out of ideas, I am fairly new to this myself so learning as I go. RUU's are similar to SBF's from motorla to return phone to stock out of the box condition. The way they work I don't think you can force push it to restore as far as I know.
This one worked perfectly and included the OTA . I am however complete stock now, lost root. My mind is a bit warped from all this confusion. How do I get root back again..? Flash amon ra ? go into Developer and install su. ?
drknrgy said:
This one worked perfectly and included the OTA . I am however complete stock now, lost root. My mind is a bit warped from all this confusion. How do I get root back again..? Flash amon ra ? go into Developer and install su. ?
Click to expand...
Click to collapse
Yes, just go into amon ra install su and superuser , then reboot. Might have to still download superuser from the market and install ,but then you should be good to go.
mjh68 said:
Yes, just go into amon ra install su and superuser , then reboot. Might have to still download superuser from the market and install ,but then you should be good to go.
Click to expand...
Click to collapse
Thanks for the great advice. I am back up and running w/OTA and root. Just need to nan-restore now. Bring on ICS!
i have read this post and my problem is somewhat similar. i can't seem to get my computer to read my phone. my sd port isn't coming up. i have my phone connected and using hasoon2000 all in one tool kit. my hboot version is 20225.0000 and radio is 1.22.10.0421r/1.22.10.042r. how can i get my phone off this white screen and also how can i get my phone and computer to read each other??? im also relocked i tried to unlock it using hasoon 2000 all in one tool kit but can't get it to kick in. and when i go into the cmd command prompt it tells me device error. the phone isn't reading.
Related
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.
I have been trying for months to try and get back to stock in order to get S-OFF and rooted. I have tried many tut's and when I get to the RUU part, it stops me and prompts the error 140. Then I have gone to other websites and threads to find a solution to the problem but I haven't found a successful one.
As of right now this is what I have when I go into bootloader:
*** RELOCKED ***
SHOOTER XC SHIP S-ON RL
HBOOT-1. 58.0000
eMMC-boot
May 17 2012,15:06:44
lxbeale said:
I have been trying for months to try and get back to stock in order to get S-OFF and rooted. I have tried many tut's and when I get to the RUU part, it stops me and prompts the error 140. Then I have gone to other websites and threads to find a solution to the problem but I haven't found a successful one.
As of right now this is what I have when I go into bootloader:
*** RELOCKED ***
SHOOTER XC SHIP S-ON RL
HBOOT-1. 58.0000
eMMC-boot
May 17 2012,15:06:44
Click to expand...
Click to collapse
What RUU are you trying to run? Since you are S-ON with hboot 1.58 the only version that should work is the Sprint ICS (2.89.651.2) version.
If you issue the following commands from fastboot you can verify that you have correct CID and man version (mainver) to flash that RUU:
fastboot getvar cid
fastboot getvar mainver
Click to expand...
Click to collapse
ramjet73
ramjet73 said:
What RUU are you trying to run? Since you are S-ON with hboot 1.58 the only version that should work is the Sprint ICS (2.89.651.2) version.
If you issue the following commands from fastboot you can verify that you have correct CID and man version (mainver) to flash that RUU:
ramjet73
Click to expand...
Click to collapse
Do you have a link to a RUU that would work? And I was trying RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed
lxbeale said:
Do you have a link to a RUU that would work? And I was trying RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed
Click to expand...
Click to collapse
Yea, that's the latest GB version but won't flash over the Sprint ICS build.
Here's the one you want.
ramjet73
ramjet73 said:
Yea, that's the latest GB version but won't flash over the Sprint ICS build.
Here's the one you want.
ramjet73
Click to expand...
Click to collapse
I downloaded it and ran it, It got about 3 minutes into it and then gave me ERROR[132]: Signature error
lxbeale said:
I downloaded it and ran it, It got about 3 minutes into it and then gave me ERROR[132]: Signature error
Click to expand...
Click to collapse
Did you ever run the fastboot commands posted above to display your CID and mainver? If so, what were the values they returned?
Also, did you check the MD5 for the RUU.exe file after you downloaded it? I know that RUU.exe is good because there have been almost 1400 downloads without any problems reported.
Is the phone in "fastboot USB" mode when you start the RUU.exe? Here's a post with some more RUU.exe troubleshooting tips that might help.
ramjet73
ramjet73 said:
Did you ever run the fastboot commands posted above to display your CID and mainver? If so, what were the values they returned?
Also, did you check the MD5 for the RUU.exe file after you downloaded it? I know that RUU.exe is good because there have been almost 1400 downloads without any problems reported.
Is the phone in "fastboot USB" mode when you start the RUU.exe? with some more RUU.exe troubleshooting tips that might help.
ramjet73
Click to expand...
Click to collapse
I Got SPCS_001 and 2.89.651.2,
I did not check the MD5 because I have no clue what that is,
It was in fastboot usb mode when I started it.
lxbeale said:
I Got SPCS_001 and 2.89.651.2,
I did not check the MD5 because I have no clue what that is,
It was in fastboot usb mode when I started it.
Click to expand...
Click to collapse
You have the correct CID and mainver for the Sprint ICS build, so that looks good.
Have you tried a different USB cable and/or another PC? Based on everything I've seen in this thread so far you are doing things right, but something may be corrupting the RUU as it's being flashed.
ramjet73
I have tried different cables but not different PC's, I will give it another go with my laptop
ramjet73 said:
You have the correct CID and mainver for the Sprint ICS build, so that looks good.
Have you tried a different USB cable and/or another PC? Based on everything I've seen in this thread so far you are doing things right, but something may be corrupting the RUU as it's being flashed.
ramjet73
Click to expand...
Click to collapse
I have tried a different cable but not a different PC, I will have another go with my laptop
lxbeale said:
I have tried a different cable but not a different PC, I will have another go with my laptop
Click to expand...
Click to collapse
I just tried using my laptop and got Error 170, so I tried a different cord and that didn't work, I then thought that the file may have been corrupted and re downloaded it and still got the same problems. I then went to go and see if the other RUU (2.17) would connect to the phone and it did but still got me the error 140. Would I need to use another PC or what, cause I don't know where to go from here
lxbeale said:
I just tried using my laptop and got Error 170, so I tried a different cord and that didn't work, I then thought that the file may have been corrupted and re downloaded it and still got the same problems. I then went to go and see if the other RUU (2.17) would connect to the phone and it did but still got me the error 140. Would I need to use another PC or what, cause I don't know where to go from here
Click to expand...
Click to collapse
Let's take a different approach.
Try downloading the 2.89.651.2 RUU (the first one) from this post, place it in the root of your SD card and rename it to PG86IMG.zip, then start your bootloader and press the power button once. That should give you a prompt to authorize the installation so go ahead and do that.
This approach will eliminate both the cable and the PC as possible causes of the problem.
ramjet73
ramjet73 said:
Let's take a different approach.
Try downloading the 2.89.651.2 RUU (the first one) from , place it in the root of your SD card and rename it to PG86IMG.zip, then start your bootloader and press the power button once. That should give you a prompt to authorize the installation so go ahead and do that.
This approach will eliminate both the cable and the PC as possible causes of the problem.
ramjet73
Click to expand...
Click to collapse
I performed this twice on two different computers using different cords each time and when I went into the bootloader, on the top right it went through a blue and then a brown loading bar and then went back to bootloader doing nothing
lxbeale said:
I performed this twice on two different computers using different cords each time and when I went into the bootloader, on the top right it went through a blue and then a brown loading bar and then went back to bootloader doing nothing
Click to expand...
Click to collapse
Did you try flashing the zip version that I linked in my last post from the bootloader?
ramjet73
ramjet73 said:
Did you try flashing the zip version that I linked in my last post from the bootloader?
ramjet73
Click to expand...
Click to collapse
Yes I did, do you think if I would root my phone again and then relock it, this could be fixed?
lxbeale said:
Yes I did, do you think if I would root my phone again and then relock it, this could be fixed?
Click to expand...
Click to collapse
I really don't know what the problem is but you would definitely have a better chance of fixing it if you are S-OFF. You could unlock the bootloader, flash a custom recovery and then a stock rooted ROM and try the wire trick. If you can get that to work you should definitely be able to flash the RUU.
There is a stock rooted version of the Sprint ICS ROM in this post.
ramjet73
ramjet73 said:
I really don't know what the problem is but you would definitely have a better chance of fixing it if you are S-OFF. You could unlock the bootloader, flash a custom recovery and then a stock rooted ROM and try the wire trick. If you can get that to work you should definitely be able to flash the RUU.
There is a stock rooted version of the Sprint ICS ROM in this post.
ramjet73
Click to expand...
Click to collapse
Okay so I unlocked my bootloader and put 4ext recovery on, but I am still having problems flashing firmware, it goes to a loading bar then it says it is parsing then returns back to the bootloader
lxbeale said:
Okay so I unlocked my bootloader and put 4ext recovery on, but I am still having problems flashing firmware, it goes to a loading bar then it says it is parsing then returns back to the bootloader
Click to expand...
Click to collapse
Unlocking your bootloader and installing a custom recovery is considered "rooting" and not the same as being S-OFF. If you want to flash PG86IMG.zip files from your bootloader you will have to perform the wire trick procedure to get radio S-OFF.
ramjet73
ramjet73 said:
Unlocking your bootloader and installing a custom recovery is considered "rooting" and not the same as being S-OFF. If you want to flash PG86IMG.zip files from your bootloader you will have to perform the wire trick procedure to get radio S-OFF.
ramjet73
Click to expand...
Click to collapse
But in order to do the wire trick, you have to be on a stock RUU and at the moment I am not. I tried installing the stock rom but all its getting me is to the sprint loading screen when trying to boot. Will the wire trick still work?
lxbeale said:
But in order to do the wire trick, you have to be on a stock RUU and at the moment I am not. I tried installing the stock rom but all its getting me is to the sprint loading screen when trying to boot. Will the wire trick still work?
Click to expand...
Click to collapse
According to the OP of this thread you have hboot 1.58 and should be able to boot a rooted stock Sprint ICS ROM. Did you do a wipe before you flashed it?
If you can't get the rooted stock ROM working you can try doing the wire trick with a "stockish" ROM like MeanROM 2.6. That's not supported by the JBear team but it's worked for some users.
You can't use a GB stock ROM because it won't boot with 1.58, so that's not an option.
ramjet73
I was given a phone to try to resurrect from the dead. It powers on directly to the bootloader screen and does no more. I really know nothing about this phone model. Before I start, I want to know if it is even possible. The screen says the following:
*** LOCKED ***
SHOOTER XC SHIP S-ON RL
HBOOT-1.57.0000
eMMC-boot
Apr 20 2012, 17:39:22
And then there are the normal bootloader options. Can this thing be saved?
silenthatred said:
I was given a phone to try to resurrect from the dead. It powers on directly to the bootloader screen and does no more. I really know nothing about this phone model. Before I start, I want to know if it is even possible. The screen says the following:
*** LOCKED ***
SHOOTER XC SHIP S-ON RL
HBOOT-1.57.0000
eMMC-boot
Apr 20 2012, 17:39:22
And then there are the normal bootloader options. Can this thing be saved?
Click to expand...
Click to collapse
if you can get to the bootloader screen and access the fastboot selection,plug it into a computer and get it to read fastbootusb then its fixable,first find your token and unlock the bootloader, then from there install a custom recovery , next copy the stock ROM over to your sdcard and boot into recovery... select install zip from sdcard and guide yourself to where the file is located ,select it and let it install... from there it should be able to reboot and boot up into the ROM
wloftus said:
if you can get to the bootloader screen and access the fastboot selection,plug it into a computer and get it to read fastbootusb then its fixable,first find your token and unlock the bootloader, then from there install a custom recovery , next copy the stock ROM over to your sdcard and boot into recovery... select install zip from sdcard and guide yourself to where the file is located ,select it and let it install... from there it should be able to reboot and boot up into the ROM
Click to expand...
Click to collapse
Thanks, it does show fastboot usb...find your token? Not sure what that means. I'll search around a bit when I get home. My original Evo 4G I did root, but don't remember that part.
silenthatred said:
Thanks, it does show fastboot usb...find your token? Not sure what that means. I'll search around a bit when I get home. My original Evo 4G I did root, but don't remember that part.
Click to expand...
Click to collapse
You don't need to unlock the bootloader to fix it, and you shouldn't unlock it anyways, until you have it fully booted properly.
Run the RUU EXE from a PC for the 3.28 update (or whatever the later version is) while the phone is connected via fastboot USB mode, it will re-flash the ROM and should boot properly then.
Unknownforce said:
You don't need to unlock the bootloader to fix it, and you shouldn't unlock it anyways, until you have it fully booted properly.
Run the RUU EXE from a PC for the 3.28 update (or whatever the later version is) while the phone is connected via fastboot USB mode, it will re-flash the ROM and should boot properly then.
Click to expand...
Click to collapse
RUU.EXE finds it and then gets to the restarting into bootloader step and the phone restarts. Then it just saying waiting for bootloader until it times out, but the bootloader is up on the phone.
silenthatred said:
RUU.EXE finds it and then gets to the restarting into bootloader step and the phone restarts. Then it just saying waiting for bootloader until it times out, but the bootloader is up on the phone.
Click to expand...
Click to collapse
This happens sometimes if you have a custom bootloader installed when you flash the RUU. Just cancel the Windows task and restart it and you should be fine.
ramjet73
wloftus said:
if you can get to the bootloader screen and access the fastboot selection,plug it into a computer and get it to read fastbootusb then its fixable,first find your token and unlock the bootloader, then from there install a custom recovery , next copy the stock ROM over to your sdcard and boot into recovery... select install zip from sdcard and guide yourself to where the file is located ,select it and let it install... from there it should be able to reboot and boot up into the ROM
Click to expand...
Click to collapse
Unknownforce said:
You don't need to unlock the bootloader to fix it, and you shouldn't unlock it anyways, until you have it fully booted properly.
Run the RUU EXE from a PC for the 3.28 update (or whatever the later version is) while the phone is connected via fastboot USB mode, it will re-flash the ROM and should boot properly then.
Click to expand...
Click to collapse
Couple things since I have looked into this a little more. Despite it saying Sprint on the front, it is a Virgin Mobile phone. It has the OTA that came down on it, so I can't flash the older RUU. It says it is an older version. So it looks like unlocking the bootloader is my only option? Question is, how do I do that from the bootloader? I was able to get the token and have the unlock_code.bin file, but the instructions to flash it seem to rely on having a working ROM to complete it, which I don't have. The phone is stuck in a bootloader loop. S-OFF, I have the answer. But it is S-ON, so not sure what to do.
silenthatred said:
Couple things since I have looked into this a little more. Despite it saying Sprint on the front, it is a Virgin Mobile phone. It has the OTA that came down on it, so I can't flash the older RUU. It says it is an older version. So it looks like unlocking the bootloader is my only option? Question is, how do I do that from the bootloader? I was able to get the token and have the unlock_code.bin file, but the instructions to flash it seem to rely on having a working ROM to complete it, which I don't have. The phone is stuck in a bootloader loop. S-OFF, I have the answer. But it is S-ON, so not sure what to do.
Click to expand...
Click to collapse
You are right that the Virgin Mobile RUU can't be flashed when S-ON and the OTA has been installed unless you can flash a zip to downgrade your main version (mainver) and you have to be unlocked and rooted to do that.
The unlock_code.bin file is flashed via fastboot USB mode so it might work, but if you've tried that and it doesn't you may be able to use unknownforce's hboot downgrade method to get straight to S-OFF. I don't know of anyone that's done it on an Evo V 4G but it might work if you use the RUU zip file for that model.
ramjet73
ramjet73 said:
You are right that the Virgin Mobile RUU can't be flashed when S-ON and the OTA has been installed unless you can flash a zip to downgrade your main version (mainver) and you have to be unlocked and rooted to do that.
The unlock_code.bin file is flashed via fastboot USB mode so it might work, but if you've tried that and it doesn't you may be able to use unknownforce's hboot downgrade method to get straight to S-OFF. I don't know of anyone that's done it on an Evo V 4G but it might work if you use the RUU zip file for that model.
ramjet73
Click to expand...
Click to collapse
It flashes unlock_code.bin to the phone successfully, but the next steps say to click yes on the screen to unlock on the phone. Can't access that without a working ROM. I'll try unknownforce's method when I get home, thanks for the help!
ramjet73 said:
You are right that the Virgin Mobile RUU can't be flashed when S-ON and the OTA has been installed unless you can flash a zip to downgrade your main version (mainver) and you have to be unlocked and rooted to do that.
Click to expand...
Click to collapse
Why is this? Is there not a full RUU for the latest version?
ramjet73 said:
The unlock_code.bin file is flashed via fastboot USB mode so it might work, but if you've tried that and it doesn't you may be able to use unknownforce's hboot downgrade method to get straight to S-OFF. I don't know of anyone that's done it on an Evo V 4G but it might work if you use the RUU zip file for that model.
ramjet73
Click to expand...
Click to collapse
You still have to brick the device for this and I haven't been able to brick it without using a full RUU flash, which he apparently can't do?
silenthatred said:
It flashes unlock_code.bin to the phone successfully, but the next steps say to click yes on the screen to unlock on the phone. Can't access that without a working ROM. I'll try unknownforce's method when I get home, thanks for the help!
Click to expand...
Click to collapse
Does it still say ** LOCKED ** Or does it say ** UNLOCKED ** now?
Unknownforce said:
Why is this? Is there not a full RUU for the latest version?
Click to expand...
Click to collapse
No. Virgin Mobile released an OTA update in November but there's no RUU that corresponds to it available yet. Fortunately, the bootloader version didn't change so the original RUU can be flashed with S-ON if the mainver is set low, but you need to be unlocked and rooted already to flash the zip file that does that.
You still have to brick the device for this and I haven't been able to brick it without using a full RUU flash, which he apparently can't do?
Click to expand...
Click to collapse
That would be a problem for him then. I don't know of anyway to flash the RUU with S-ON after the OTA has been installed if the bootloader is actually locked and he can't unlock it.
ramjet73
Yeah, not looking good. Thanks for the help though!
So, I have a dilemma. I am currently S-ON running TACHYON 1.2 (Android 4.3)
HBOOT 2.28.0000
Radio 2.23.10.0123/4
I updated the hboot and radio while S-ON. Now, I've decided I'd like to go S-OFF. According to JuopunutBear I need to be on a stock RUU for their S-OFF to work. I tried running the newest ICS RUU a few weeks ago and found that it would just error out when it was checking the file because the radios and hboot on the phone were newer than the ones on the RUU. Can I step backwards in HBOOT versions whlie S-ON or have I kind of screwed myself? Or is there a better option I haven't thought about?
Thanks
Just install a stock Rom to run s-off program. You are on a stock hboot, so no problem there.
Sent from my DNA using my mind.
Uzephi said:
Just install a stock Rom to run s-off program. You are on a stock hboot, so no problem there.
Sent from my DNA using my mind.
Click to expand...
Click to collapse
It's a stock hboot, yes. But the RUU won't run because it is an older version hboot.
You need s-off to downgrade. Just install a stock based Rom that is rooted and run s-off procedure. You will have no issues. After s-off if you want, you can ruu
Sent from my DNA using my mind.
Step 1 from Unlimited: Verify - You are on Stock RUU (not FreshROM, Stock Rooted, HarmonyROM - none of these will work!)
They say not to be rooted or anything. What difference does it make?
Also, what do you mean by "stock rom"? Is there a stock rom I can install that is not an RUU? (maybe that's a dumb question but I don't know lol)
jeff925 said:
Step 1 from Unlimited: Verify - You are on Stock RUU (not FreshROM, Stock Rooted, HarmonyROM - none of these will work!)
They say not to be rooted or anything. What difference does it make?
Also, what do you mean by "stock rom"? Is there a stock rom I can install that is not an RUU? (maybe that's a dumb question but I don't know lol)
Click to expand...
Click to collapse
A stock rooted RUU would work. I was in your predicament once. First, do a nandroid backup then use this guide it'll get you to s-off. If you want to downgrade, then use this guide to accomplish this.
Thanks guys for the help. Installed the rom listed in the guide and it worked great. S-OFF now!! (Took me long enough...I've had the phone for 2 years!)
It installed JuopunutBear's hboot but whatever. I'd probably rather stick with a stock hboot but I can do that later.
Restored my nandroid backup and I'm back up and running like I never left.
Just flash this ROM and boot image, and you should be able to S-OFF, I can't remember if stock recovery is needed but that can be flashed separately as well if needed, but I don't think it is.
http://forum.xda-developers.com/showthread.php?t=2260154
So, All was well until I decided to flash the stock hboot back to the phone. I put the file on the sd card and renamed it ph98img.zip and flashed it in fastboot. It said it was successful and that I was running hboot 2.28 and radio 2.23.10.0123/4. Then I rebooted and it hung up at the white screen with green htc logo. I pulled the battery and rebooted holding the power and volume buttons. It booted to fastboot so I tried a few things. I tried flashing a recovery but it said that remote was not allowed and failed. Then I tried opening the recovery I already had on the phone from fastboot and it gave me the software download icon. Nothing happened so I pulled the battery and tried to boot back to fastboot. This time it wouldn't even get to fastboot. The white screen with HTC logo comes up and then the screen goes blank. Then the software download icon comes up and then shortly there after a red triangle with an exclamation point takes its place.
That went downhill fast! Any suggestions?
EDIT: Pulling the SD card allows me to get back into fastboot! But I'm still not sure what to do. Is it because my bootloader is locked?
jeff925 said:
So, All was well until I decided to flash the stock hboot back to the phone. I put the file on the sd card and renamed it ph98img.zip and flashed it in fastboot. It said it was successful and that I was running hboot 2.28 and radio 2.23.10.0123/4. Then I rebooted and it hung up at the white screen with green htc logo. I pulled the battery and rebooted holding the power and volume buttons. It booted to fastboot so I tried a few things. I tried flashing a recovery but it said that remote was not allowed and failed. Then I tried opening the recovery I already had on the phone from fastboot and it gave me the software download icon. Nothing happened so I pulled the battery and tried to boot back to fastboot. This time it wouldn't even get to fastboot. The white screen with HTC logo comes up and then the screen goes blank. Then the software download icon comes up and then shortly there after a red triangle with an exclamation point takes its place.
That went downhill fast! Any suggestions?
EDIT: Pulling the SD card allows me to get back into fastboot! But I'm still not sure what to do. Is it because my bootloader is locked?
Click to expand...
Click to collapse
In fastboot does it say s-off? Try manually flashing the boot.img by extracting it. If you haven't setup enviroment variable for fastboot put the boot.img in the same directory as fastboot.exe and use command prompt by typing
Code:
cd C:\Android\platform-tools (or wherever it is for you)
Then type
Code:
fastboot flash boot boot.img
I was able to put an RUU on another sd card and flash that. So now I'm on ICS 4.03.605.2 and running. But I still haven't solved my recovery problems.
According to this thread: androidforums.com/rezound-all-things-root/550408-s-off-guide-info-return-stock.html
I can either use juopunutbear's hboot (which I just flashed over the top of) to flash a new recovery or I can compile a recovery in a ph98img file (which I don't know how to do or want to do).
My question is: What happens if I unlock my bootloader while S-OFF? (Yes, it says s-off on the bootloader screen.) Will that solve my problem or do I have to go back to juopunutbear's hboot?
jeff925 said:
I was able to put an RUU on another sd card and flash that. So now I'm on ICS 4.03.605.2 and running. But I still haven't solved my recovery problems.
According to this thread: androidforums.com/rezound-all-things-root/550408-s-off-guide-info-return-stock.html
I can either use juopunutbear's hboot (which I just flashed over the top of) to flash a new recovery or I can compile a recovery in a ph98img file (which I don't know how to do or want to do).
My question is: What happens if I unlock my bootloader while S-OFF? (Yes, it says s-off on the bootloader screen.) Will that solve my problem or do I have to go back to juopunutbear's hboot?
Click to expand...
Click to collapse
You can unlock when S-OFF, but there is no reason to, you can get a PH98img.zip of CWM here: http://forum.xda-developers.com/showthread.php?t=1914215 or TWRP here: http://forum.xda-developers.com/showthread.php?t=1902381 and just copy it to your sd card (remember to name it exactly PH98IMG.zip, beware the Windoze "double zip" issue) then pop it in the phone, boot into Hboot with the USB disconnected and it should recognize it and flash either CWM or TWRP. from there you can flash ANYTHING you want, being S-OFF with custom recovery allows you to flash anything, no fastboot commands required.
Also, since you are S-OFF, your Hboot is mostly irrelevant, but should be the matching version to your radios... an engineered hboot (like Juopunutbears) would allow fastboot commands well locked, but fastboot isn't generally needed once S-OFF has been obtained...
Try this. no wire even, works great.
http://forum.xda-developers.com/showthread.php?p=48911002#post48911002
i am on hboot 2.25 though. im thinking of updating my hboot still researching how exactly.
4218kris said:
Try this. no wire even, works great.
http://forum.xda-developers.com/showthread.php?p=48911002#post48911002
i am on hboot 2.25 though. im thinking of updating my hboot still researching how exactly.
Click to expand...
Click to collapse
i can help with that....its pretty easy if your already s-off
---------- Post added at 03:26 AM ---------- Previous post was at 03:22 AM ----------
jeff925 said:
I was able to put an RUU on another sd card and flash that. So now I'm on ICS 4.03.605.2 and running. But I still haven't solved my recovery problems.
According to this thread: androidforums.com/rezound-all-things-root/550408-s-off-guide-info-return-stock.html
I can either use juopunutbear's hboot (which I just flashed over the top of) to flash a new recovery or I can compile a recovery in a ph98img file (which I don't know how to do or want to do).
My question is: What happens if I unlock my bootloader while S-OFF? (Yes, it says s-off on the bootloader screen.) Will that solve my problem or do I have to go back to juopunutbear's hboot?
Click to expand...
Click to collapse
and what recovery problems are you having....flashing an hboot will not give you a recovery...and an ruu is an exe file not a ph98img file...those are OTA's.....if you need pure stock i can easily help you obtain it....i just need to know what exactly your trying to achieve
REV3NT3CH said:
i can help with that....its pretty easy if your already s-off
---------- Post added at 03:26 AM ---------- Previous post was at 03:22 AM ----------
Click to expand...
Click to collapse
i believe i can flash hboot with a ph98img yea? can you link me to the best/newest 2.28 i think.
4218kris said:
i believe i can flash hboot with a ph98img yea? can you link me to the best/newest 2.28 i think.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=40767819&postcount=33
4218kris said:
i believe i can flash hboot with a ph98img yea? can you link me to the best/newest 2.28 i think.
Click to expand...
Click to collapse
that one or the this 2nd ph98img in my downgrade/upgrade guide work as well...that one is just radios and hboot....doesnt come with stock <3e> recovery
REV3NT3CH said:
if you need pure stock i can easily help you obtain it....i just need to know what exactly your trying to achieve
Click to expand...
Click to collapse
Hey REV3NT3CH,
So, thanks to the help of so many in these parts, including you, I now think I'm S-Off and I'm very interested in bringing my phone up to the latest, completely stock OTA ROM. Can you help me with that?
Thanks!
cheers,
john
jrredho said:
Hey REV3NT3CH,
So, thanks to the help of so many in these parts, including you, I now think I'm S-Off and I'm very interested in bringing my phone up to the latest, completely stock OTA ROM. Can you help me with that?
Thanks!
cheers,
john
Click to expand...
Click to collapse
when you boot into your bootloader...does your hboot now say S-OFF....if so i can give you everything you need and what id suggest doing just prior to doing it
REV3NT3CH said:
when you boot into your bootloader...does your hboot now say S-OFF..
Click to expand...
Click to collapse
Yes it does.
REV3NT3CH said:
.if so i can give you everything you need and what id suggest doing just prior to doing it
Click to expand...
Click to collapse
That would be fantastic!
Thanks,
John
Hi All,
please help me to revive a dead Dead Verizon Droid DNA HTC6435LVW, It restarts always to ClockworkMod Recovery v6.0.2.8 (see pics).
I can go to Fastboot/Hboot but will not start to android. please guide me to solve this issue.
thanks in advance
ab1009 said:
Hi All,
please help me to revive a dead Dead Verizon Droid DNA HTC6435LVW, It restarts always to ClockworkMod Recovery v6.0.2.8 (see pics).
I can go to Fastboot/Hboot but will not start to android. please guide me to solve this issue.
thanks in advance
Click to expand...
Click to collapse
Do you want to get back to stock Sense? Download and run this RUU while in fastboot
https://docs.google.com/file/d/0B32gqnbh2ZecSHM2VXJoY2tFUU0/edit?usp=sharing
Or you can sideload a ROM .zip from CWM and install it.
Thank you duffman for reply, I downloaded the RUU and excute it but I got error 155, I tried other RUU also I got the same error, how to avoid this error?
br
ab1009 said:
Thank you duffman for reply, I downloaded the RUU and excute it but I got error 155, I tried other RUU also I got the same error, how to avoid this error?
br
Click to expand...
Click to collapse
The 155 error is because the hboot and the ruu do not corespond. You must flash the a matching pair. either find the proper hboot, or the ruu. The hboot would be quicker as it's smaller.
ibsk8 said:
The 155 error is because the hboot and the ruu do not corespond. You must flash the a matching pair. either find the proper hboot, or the ruu. The hboot would be quicker as it's smaller.
Click to expand...
Click to collapse
Exactly. Download the DNA toolkit. http://forum.xda-developers.com/showthread.php?t=2219175
Use it to flash the 3.06 hboot
After that, try the 3.06 RUU again.
ibsk8 said:
The 155 error is because the hboot and the ruu do not corespond. You must flash the a matching pair. either find the proper hboot, or the ruu. The hboot would be quicker as it's smaller.
Click to expand...
Click to collapse
duffman452001 said:
Exactly. Download the DNA toolkit. http://forum.xda-developers.com/showthread.php?t=2219175
Use it to flash the 3.06 hboot
After that, try the 3.06 RUU again.
Click to expand...
Click to collapse
thank you ibsk8 and duffman,
I treid what you wrote but I got this error: FAILED (remote: 99 unknown fail) what is my mistake??
br
ab1009 said:
thank you ibsk8 and duffman,
I treid what you wrote but I got this error: FAILED (remote: 99 unknown fail) what is my mistake??
br
Click to expand...
Click to collapse
Hmmm I just realized you're s-on. When you say you tried the other RUU, did you try the alternate 3.06 RUU or the 1.15 RUU?
1.15 RUU: https://docs.google.com/file/d/0B32gqnbh2ZecSHM2VXJoY2tFUU0/edit?usp=sharing
That really should work since you're on the 1.15 hboot and radio. If not, can you send a screenshot of the error?
Hi duffman,
I tried to Flash the 1.15 RUU but I got 155 error. please see my pics.
br
looks like you may have been trying to s-off? which did not complete.
rerun s-off and try different usb port
Thank You DJ_MiX for reply,
I used Moonshine to S-Off, I puted the Droid DNA in "Fastboot USB" mode, I did all as in instruction, I got Error: run distiller again and READ.
I used Rumrunner and I see now: "no ADB connection to device, Debugging on?" but I cannot boot the device in normal android and choose "USB debugging". I can boot to HBoot/Fastboot or Recovery Mode.
can you help me to s-off this phone (can I use RUU with s-off phone??)
br
Error 155 is due to attempting to RUU while unlocked. To apply an RUU you must be locked. In order to lock your device connect to your pc and enter fastboot usb mode. use the command "fastboot oem lock". Once you are locked you can RUU using the current version as reported by the RUU utility or a higher version.
After this is successful you should obtain s-off, as this will save you in the future from the current issue you created for yourself. Alternatively you can apply all the OTAs and fully update to kit-kat firmware.
Note: once you are locked again you will not be able to boot (no change there) and you will not be able to enter recovery due to the non-factory recovery.
Thank you all espcially TheRealDeadApe,
My phone is now alive again. I have flashed it with RUU 1.15 but with RUU 3.06 I get ERROR (158) IMAGE ERROR. now I have Android 4.1.1 can I upgrade to 4.4.2 if I live outside USA?
br
Bump. I'm in the exact same situation.
ab1009 said:
Thank you all espcially TheRealDeadApe,
My phone is now alive again. I have flashed it with RUU 1.15 but with RUU 3.06 I get ERROR (158) IMAGE ERROR. now I have Android 4.1.1 can I upgrade to 4.4.2 if I live outside USA?
br
Click to expand...
Click to collapse
As for the OTAs you can apply them anywhere you are if you download the zip files and flash them using the stock recovery. Search this forum.
Personally I would s-off. I used moonshine on the 1.15 firmware when I did it. Then you can flash RUUs without restrictions so you can update easier or update the firmware only and flash a custom rom.
For Flashing Custom ROM to Dead DNA
ab1009 said:
Hi All,
please help me to revive a dead Dead Verizon Droid DNA HTC6435LVW, It restarts always to ClockworkMod Recovery v6.0.2.8 (see pics).
I can go to Fastboot/Hboot but will not start to android. please guide me to solve this issue.
thanks in advance
Click to expand...
Click to collapse
This is for future reference since this has been solved. This method is from my own experiences and will work if you absolutely need functionality as soon as humanly possible.
What you can do is plug your phone while it is in recovery and select install zip from sideload.
find a custom rom you want with the corresponding GAPPS if needed,
put the rom.zip and your gapps.zip (if applicable) at the root directory of your adb. (rightclick adb on desktop click go to file location)
Rename your rom.zip to literally just rom.zip (makes it a lot easier later) and the gapps.zip to gapps.zip
check to see if your pc sees your device after selecting install zip from sideload by running "adb devices". you should see a long id number with SIDELOAD to the right.
If your device shows up, then run "adb sideload rom.zip", once finished do not hit reboot system until you flash gapps if needed.
for gapps run 'adb sideload gapps.zip" then reboot your phone. Your phone should now have functionality restored. :good: