Related
hi all
Forgot to charge my EVO 3D (CDMA) and battery completely drained. Even after using another fully charged battery my phone goes to bootloop - just shows the HTC logo and reboots again and again. Here is what I have:
hboot : 1.5 (S-ON)
radio : 1.06.00.1216
ota : 2_17.651_5
(I am using this phone in India activated on Reliance)
As the phone doesn't boot I can't access it thru adb to give command 'adb reboot bootloader'
I can get bootloader by pressing vol_down+power
When I run the 2_17.651_5 RUU (exe) from my computer while phone is on fastboot, it completes successfully without errors. But still on reboot it just stays at the htc screen and reboots (guess it's becoz stock kernel not getting flashed as the phone is s-on)
kindly help to get back my phone boot again
thanks and regards
ananth
R.I.P
Sent from my HTC.EVO.3D.Xda Premium
Don't listen to the previous guy. Try using fastboot OEM lock and then ruuing. Or, try getting freezas stock kernel and extracting the boot.IMG and flashing it thru fastboot. Or, you could use fastboot flash recover recovery.IMG to get twrp or clockworkmod and do a superwipe and try flashing a new Rom. There are tons of options if you still have fastboot.
Sent from my HTC popout book.
jdeoxys said:
Don't listen to the previous guy. Try using fastboot OEM lock and then ruuing. Or, try getting freezas stock kernel and extracting the boot.IMG and flashing it thru fastboot. Or, you could use fastboot flash recover recovery.IMG to get twrp or clockworkmod and do a superwipe and try flashing a new Rom. There are tons of options if you still have fastboot.
Sent from my HTC popout book.
Click to expand...
Click to collapse
Thanx for responding. As I mentioned earlier,I have already relocked and RUU'd the exe file,but though it runs without errors doesn't solve problem. Again as it is s-on doesn't permit to flash boot.img. Though I am able to flash twrp recovery, not able to get into recovery from fastboot. Thanks again, really appreciate your help.
ananth001 said:
Thanx for responding. As I mentioned earlier,I have already relocked and RUU'd the exe file,but though it runs without errors doesn't solve problem. Again as it is s-on doesn't permit to flash boot.img. Though I am able to flash twrp recovery, not able to get into recovery from fastboot. Thanks again, really appreciate your help.
Click to expand...
Click to collapse
You don't need to relock once you unlock the HTC way. Just unlock the phone then flash via fastboot the boot.img and then ruu if you want.
Sent from my PG86100 using Tapatalk
megabiteg said:
You don't need to relock once you unlock the HTC way. Just unlock the phone then flash via fastboot the boot.img and then ruu if you want.
Click to expand...
Click to collapse
thanks. extracted boot.img from freeza's kernel and flashed from fastboot after unlocking. But still doesnt solve problem. Can you give me a link for boot.img
Pleassssssse HELP !!!!!!
I have the exactly the same problem, a full reboot result in boot loop, and can not fix it by now.
I guest the phone is rooted before OTA, so OTA can not flash kernel successfully because the wrong signature, and the phone will not boot because the wrong kernel.
I have tried ruu, fastboot boot recovery.img and etc, all failed.
The key point is that, the phone is rooted and you tried OTA. HTC OTA must have a stupid bug, it can not recovery from a partial update, or automatically roll back becasuse of the partial update, dem!
Please have a look at the guide/flashing notes in my signature. If u r unlocked u are likely not entering recovery correctly.
If u are trying to flash the Ruu u have to be locked or relocked. If u cant boot to android, run the xhausx's full Ruu zip from bootloader.
Sent from my PG86100 using Tapatalk
mpgrimm2 said:
Please have a look at the guide/flashing notes in my signature. If u r unlocked u are likely not entering recovery correctly.
If u are trying to flash the Ruu u have to be locked or relocked. If u cant boot to android, run the xhausx's full Ruu zip from bootloader.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
1) flashed RUU (exe) after relocking - flash completed without errors
2) ran xhausx's full RUU zip (PG86IMG_2.17.651.5.zip) from bootloader (could get into bootloader by pressing volum_up + power button. adb cannot connect to phone (as phone does not boot), to run 'adb rebooot bootloader')
But still doesn't solve problem and phone keeps rebooting, apparently kernel has not flashed properly.
Please help !!!1
ananth001 said:
1) flashed RUU (exe) after relocking - flash completed without errors
2) ran xhausx's full RUU zip (PG86IMG_2.17.651.5.zip) from bootloader (could get into bootloader by pressing volum_up + power button. adb cannot connect to phone (as phone does not boot), to run 'adb rebooot bootloader')
But still doesn't solve problem and phone keeps rebooting, apparently kernel has not flashed properly.
Please help !!!1
Click to expand...
Click to collapse
You need to use the RUU 2.17 exe after you relock your phone... Then flash a copy of CWM or TWRP on it..
Then adb
fastboot boot recovery.img
Wipe and flash whatever you want
Just noticed u said India & carrier is reliance. Why would u be using a Sprint USA CDMA Ruu? Shouldn't u be using a GSM RUU version?
Sent from my PG86100 using Tapatalk
mpgrimm2 said:
Just noticed u said India & carrier is reliance. Why would u be using a Sprint USA CDMA Ruu? Shouldn't u be using a GSM RUU version?
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
I wonder the same thing all I saw was 1.5
Sent from my PG86100 using xda premium
mpgrimm2 said:
Just noticed u said India & carrier is reliance. Why would u be using a Sprint USA CDMA Ruu? Shouldn't u be using a GSM RUU version?
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Reliance has both CDMA as well as GSM service in India. Mine is a Reliance CDMA MDN.
thanks and regards
reaper24 said:
You need to use the RUU 2.17 exe after you relock your phone... Then flash a copy of CWM or TWRP on it..
Then adb
fastboot boot recovery.img
Wipe and flash whatever you want
Click to expand...
Click to collapse
Yeah , as I mentioned earlier, I also tried using the RUU 2.17 exe after relocking (RUU completed successfully without errors) , and flashed twrp recovery from fastboot . But still it's a no go.
(Again would like to repeat that I can't boot into bootloader from adb - adb cannot connect as phone doesn't android boot. I get into fastboot by pressing vol_down + power)
thanks all for your responses and help, hope you all will continue guiding me till I get this done.
ananth001 said:
Yeah , as I mentioned earlier, I also tried using the RUU 2.17 exe after relocking (RUU completed successfully without errors) , and flashed twrp recovery from fastboot . But still it's a no go.
(Again would like to repeat that I can't boot into bootloader from adb - adb cannot connect as phone doesn't android boot. I get into fastboot by pressing vol_down + power)
thanks all for your responses and help, hope you all will continue guiding me till I get this done.
Click to expand...
Click to collapse
Have you tried to just run the RUU like you said boot turn debug on .... Then go to hboot flash your recovery...
Then fastboot boot recovery.img.
This should work I have unrooted my phone 3 times already in the past month Trial and Error on my part adb always found my phone...
I am tryin to figure out what is going wrong on the last part with TWRP...
Since you said after you do that it was a no go? What happend ? Adb should still be working since you just flashed the recovery...
Anyways I hope you get it solved man I am tryin to figure this problem out.
Do you have a rom already ready to be flashed on your SD card?
Problem is, since i’m not able to android boot I can't reboot bootloader from adb, as I can't connect adb without the phone normal booting. When I boot it just stays at the HTC white screen.
I have flashed twrp recovery from fastboot, but when I give command 'fastboot boot <twrpxxxxx>.img it just boots back to the HTC splash screen
You can go back to complete stock if you rename the RUU file PG86IMG.zip and load onto the root of sd card. Get into bootloader with [power+volume down] and it will automatically detect and load the zip file. This can only be done if you are relocked. I did this in order to get the latest update. After you get back to stock you can unlock and root again.
Android Cowboy said:
You can go back to complete stock if you rename the RUU file PG86IMG.zip and load onto the root of sd card. Get into bootloader with [power+volume down] and it will automatically detect and load the zip file. This can only be done if you are relocked. I did this in order to get the latest update. After you get back to stock you can unlock and root again.
Click to expand...
Click to collapse
As I mentioned in earlier post, have tried flashing PG86IMG.zip from bootloader, but still phone doesn't boot properly and is in a bootloop.
You've used the following file and done these exact steps and allowed the phone to boot to full stock OS? (assuming 2.17.651.5 is correct version)
OPTION 2 - RUU.zip info:
I prefer the .exe version but xHausx’s “FULL” PG86IMG_2.17.651.5.zip may work for you (must be renamed PG86IMG.zip). Make sure you have plenty of battery/charge left!
- (XDA) Xhausx full PG86IMG.zip RUU images (651.5 zips)
PG86IMG_2.17.651.5.zip http://forum.xda-developers.com/showpost.php?p=21593454&postcount=564
MD5: 8F82C2D8F98C077AF775266064BACB5D
From Scrosler's zip Directions : http://forums.androidcentral.com/htc-evo-3d-rooting-roms-hacks/107641-how-return-100-stock-all-versions.html
Scrosler; said:
USE ONLY FOR EMERGENCY PURPOSES. THIS OVERWRITES EVERYTHING!!!!
**THIS WILL RETURN YOU TO FRESH OUT OF THE BOX**
You will not need any special drivers loaded, etc...
1.Download the stock ROM ZIP image from here: and rename it "PG86IMG.zip"
2.Copy it to SD Card
3.Reboot phone into hboot mode by holding volume down and then press power.
Keep volume down held until you boot into hboot mode.
4.In hboot mode the phone will scan the SD card with the image. Once it finds it will ask you if you want to update. Press "Power" to update.
5.Wait.... For a while. When it gets to "system" it will loop a few times. Its quite nerve wracking actually but after about 5 or 6 times it will complete.
6.Once the entire flash is complete it will prompt you to "press power to reboot." Press power and your phone will reboot to 100% stock ROM.
Click to expand...
Click to collapse
For people who came for an answer, here it is.
download android sdk
download fastboot drivers
get clockworkmod img and rename to imgfile.img
put img in adb tools
put adb, adbwinapi, fastboot, and the img file in c:/Android
plug your phone to the computer
enter the bootloader
click on recovery or fastboot doesnt matter since both will now take you to fastboot
goto computer
type in run in start menu
type cmd in run and hit enter
type cd c:\Android
type fastboot boot imgfile.img
you are now in recovery
go to mounts and storage and mount your device as a disk drive
download any rom to your computer doesnt really matter and put in on your sdcard. If you already have a rom on there then just use that.
unmount your phone
go to wipe data/factory reset and when it finishes flash the rom
once rom is done flashing reboot into android again.
your phone is partially fixed
now go to the market (if you flashed cm then flash the gapps.zip) and download "rom manager"
Then click on download clockworkmod 5.0.0.2 or something like that (first option)
Now go to rom manager and restore your backup that u made (If there was 1 before)
now it will be fixed and your bootloader will take u to recovery instead of fastboot when you click recovery xD
thanks xda
I flashed a rom and the rom must have been corrupted or something and now my phone is stuck rebooting and when I try to go to recovery or any option it takes me to fastboot so now my phone is basically bricked
Your phone is not bricked since your still able to turn it on.
Can you enter fasboot USB?
Send from my Evo 3D using Tapatalk
well it doesnt really turn on its a boot loop but whatever and fastboot is weird it doesnt want to work.
If your bootloader is unlocked make sure you flash the boot.img through fastboot and make sure you wipe
Sent from my ADR6425LVW using XDA
fastboot doesnt work I already tried too flash it
Guys please help!!!!!!!!!!!!!!!!!!
What do you mean by fastboot is wierd. Did you pull the battery?
fastboot doent work cmd always says waiting for device
if i click recovery it takes me to fastboot, btw.
Have you tried an ruu?
anobahar said:
fastboot doent work cmd always says waiting for device
Click to expand...
Click to collapse
Do you have the proper drivers installed
Sent from my ADR6425LVW using XDA
Are you S-Off or S-On? If S-Off, download a PG86IMG.zip of a recovery, and use your bootloader to flash recovery. From that point, just restore a backup or reflash a ROM. If you're not S-Off, I'd say you should try running an RUU, since you can't get fastboot to work. But I think you need to relock your device to run an RUU (if you're S on/ HTC Unlocked), so you'd still need fastboot. Do you have a different USB cable to try? I've seen them fail before even though they still work to charge.
k2buckley said:
Are you S-Off or S-On? If S-Off, download a PG86IMG.zip of a recovery, and use your bootloader to flash recovery. From that point, just restore a backup or reflash a ROM. If you're not S-Off, I'd say you should try running an RUU, since you can't get fastboot to work. But I think you need to relock your device to run an RUU (if you're S on/ HTC Unlocked), so you'd still need fastboot. Do you have a different USB cable to try? I've seen them fail before even though they still work to charge.
Click to expand...
Click to collapse
Sounds like the drivers arn't installed right.. Like you said if he is S-ON and relocked he can run a RUU exe if he is CDMA...
If you are s off then you just need to reload another recovery. And then access a backup of a rom! Or just flash a new one. I had a issue just like this yesterday where my recovery was broken for some reason and had to go from twrp. 2.1 back to 1.1.1 and load another rom.
Sent from my PG86100 using xda premium
Well i put the sdcard in a bberry but a pg6img.img in my sdcard but bootloader doesnt do anything
I am cdma, s-off unlocked with revolutionary kernel 1.4
oops not kernel hboot
Ok, fail, i dont think i hav fastboot drivers downloading now
now cmd is stuck on "sending recovery"
Did you place a copy of the img into your fast boot folder and one in your adb tools folder ???
#Root-Hack_Mod*Always\
This phone has never been rooted and has never had s-off. Phone will not boot into recovery or system. Only bootloops HTC logo or hboot. I used hboot and fastboot to get the bootloader unlocked. I have tried stock, ext4, and custom recoveries and none will boot. I have tried every ruu.exe and PG86IMG.zip from 1.17 to 2.89. None will work. I have used fastboot to flash boot and still will not boot up. When I try to run ControlBear it just
======== ControlBear 0.7 beta for JuopunutBear S-OFF ==========
Rebooting from bootloader
Waiting...
...Waiting
Detecting...Starting up......
Connecting to device...
Searching device.....
Connect device and install drivers
Press ENTER to exit.....
Nothing else.
I have seen a couple others with this issue in 1.50 and another with 1.58 but he was LOCKED and hasn't responded to his thread in a couple of days after suggesting having sprint look into it. I unfortunately have a crack in my touchscreen so sprint does nothing to help. Any idea or suggestions would be great.
PS sorry for any double posts or answered questions. I have been looking since 11 and trying different things with nothing working yet.
EDIT: I have looked into trying the unknownforce hboot downgrade but 2.17 will not install since its an older version. 2.89 files I find will load but when it trys to parse the phone just goes back to the bootloader menu.
I suggest you lock the bootloader first and then run the 2.17 ruu.exe. This will put you back to stock GB. Then you can unlock again and get s-off if you choose.
Save the Drama for your Mama with Tapatalk 2
coal686 said:
I suggest you lock the bootloader first and then run the 2.17 ruu.exe. This will put you back to stock GB. Then you can unlock again and get s-off if you choose.
Click to expand...
Click to collapse
I have tried that and I tried it again. Relocked the phone, ran the update and got a bootloader version error and the phone says RUU Update Fail! Going to try to PG86IMG.zip version of the update now and see if its any different.
EDIT: PG86IMG.zip fails with
Main Version is older!
Update Fail!
Press <power> to reboot.
any .zip files I have found with 2.89 will get to parsing then just go straight to bootloader menu.
I have the same issue, I update to ICS with the OTA update, then did the HTC Dev unlock. But with every rom I tried to flash It just stays stuck at the splash screen. If I try to use the RUU, it gives error 140 I believe, If I try to flash PG86IMG It gives me a main version older failure. S-On
Currently phoneless for the past few days :$
TheSeanR said:
I have the same issue, I update to ICS with the OTA update, then did the HTC Dev unlock. But with every rom I tried to flash It just stays stuck at the splash screen. If I try to use the RUU, it gives error 140 I believe, If I try to flash PG86IMG It gives me a main version older failure. S-On
Currently phoneless for the past few days :$
Click to expand...
Click to collapse
Got this from Tribulattifather page :
1st, ReLock Your bootloader.:
1. Enter FASTBOOT, and then connect to your computer (FASTBOOT USB will be shown).
To do this, hold your volume down key while pressing power. when you've seen the bootloader. Then hook up the phone to the computer. Make sure you have android usb drivers installed.
2. Open command prompt in your computer
3. Relock your device by typing "fastboot oem lock", device will reboot.
4. Enter FASTBOOT again (you will see *** RELOCKED ***)
Then get yourself flashed to a stock rom - <--place on sd card
..Download this one:
http://shipped-roms.com/download.ph...08_NV_SPCS_1.31_003_release_208230_signed.exe
Then press the power button on your phone and you should see Fastboot USB. Once you see this, runn the RUU.exe
Let that work it's way through.
Once that is done then it will boot to the rom.
From here, you can accept the OTA'
Read the rest here:
http://forum.xda-developers.com/showthread.php?t=1808332
^^^ Exactly what I said in post 2 but with more detail.
Save the Drama for your Mama with Tapatalk 2
finally past
I was TOTALLY stuck in the same area, Trib's method didn't work because no RUU would run against hboot 1.58.
After 3 hours of searching, I found Gonzo's post here:
http://forum.xda-developers.com/showthread.php?t=1813542
basically, extract the boot.img from the rom you are trying to flash, and use fastboot to flash the img
fastboot flash boot boot.img
this worked for me when NOTHING else would, thanks again to Gonzo320!
kuroyoma said:
This phone has never been rooted and has never had s-off. Phone will not boot into recovery or system. Only bootloops HTC logo or hboot. I used hboot and fastboot to get the bootloader unlocked. I have tried stock, ext4, and custom recoveries and none will boot. I have tried every ruu.exe and PG86IMG.zip from 1.17 to 2.89. None will work. I have used fastboot to flash boot and still will not boot up. When I try to run ControlBear it just
======== ControlBear 0.7 beta for JuopunutBear S-OFF ==========
Rebooting from bootloader
Waiting...
...Waiting
Detecting...Starting up......
Connecting to device...
Searching device.....
Connect device and install drivers
Press ENTER to exit.....
Nothing else.
I have seen a couple others with this issue in 1.50 and another with 1.58 but he was LOCKED and hasn't responded to his thread in a couple of days after suggesting having sprint look into it. I unfortunately have a crack in my touchscreen so sprint does nothing to help. Any idea or suggestions would be great.
PS sorry for any double posts or answered questions. I have been looking since 11 and trying different things with nothing working yet.
EDIT: I have looked into trying the unknownforce hboot downgrade but 2.17 will not install since its an older version. 2.89 files I find will load but when it trys to parse the phone just goes back to the bootloader menu.
Click to expand...
Click to collapse
Try the following steps,
1. go to recovery > wipe & factory reset, wipe cache, wipe dalvik, go to mounts and storage, wipe system, data, cache, sd card... everything u can find there... wipe all..
2. in recovery DO NOT REBOOT, turn off phone
3. go to android development of evo 3d gsm, find a rom, for example mikrunny 1.06, open the archive extract the boot.img from the kernel folder.
4. assuming u have android sdk installed on ur computer, make a new folder and from the android sdk tools copy adb.exe, fastboot.exe, adbwinapi.dll (exact same files u used to unlock bootloader). also in this folder put that boot.img you extracted from the rom
5. put that folder in C:\
6. get back to phone , still DO NOT BOOT UP YET, and power up phone in bootloader mode (vol down & power) and go to fastboot
7. connect phone to pc in fastboot usb mode
8. open command prompt, type cd c:\"folder" ("folder" = folder u created with the sdk tools)
9. type in cmd: fastboot flash boot boot.img
10. after it's completed, go to recovery, still do not boot up phone
11. in recovery go to mounts and storage, usb storage and now copy the whole rom and nothing but the rom on the sd card
12. install zip from sdcard, select rom and let it install, it should boot up automatically
steps were given by SeptimiuB, I am just replying to your query because I've gone through the same mess and recovered as well.
Just unlock your bootloader and install a recovery before trying the above steps.
Cheers.
Yea listen to that dude connect yur phone up fastboot boot boot.img and do the wire trick till it works. It will it takes several times and a lot of cursing but it'll work
EVO 3DIZZLE
S-OFF
HBOOT 1.58
Xsavior said:
I was TOTALLY stuck in the same area, Trib's method didn't work because no RUU would run against hboot 1.58.
After 3 hours of searching, I found Gonzo's post here:
http://forum.xda-developers.com/showthread.php?t=1813542
basically, extract the boot.img from the rom you are trying to flash, and use fastboot to flash the img
fastboot flash boot boot.img
this worked for me when NOTHING else would, thanks again to Gonzo320!
Click to expand...
Click to collapse
After flashing the boot.img, will it be OK to flash the rom from the img it is taken from?
I'm having the same problem as the OP.
---------- Post added at 07:19 PM ---------- Previous post was at 07:09 PM ----------
Xsavior said:
I was TOTALLY stuck in the same area, Trib's method didn't work because no RUU would run against hboot 1.58.
After 3 hours of searching, I found Gonzo's post here:
http://forum.xda-developers.com/showthread.php?t=1813542
basically, extract the boot.img from the rom you are trying to flash, and use fastboot to flash the img
fastboot flash boot boot.img
this worked for me when NOTHING else would, thanks again to Gonzo320!
Click to expand...
Click to collapse
Duuuuude, you totally saved me from minor stress and the headache I was going through. If you had PayPal, I'd send you $1. x-)
Sent from my Xoom using xda app-developers app
I am trying to restock Verizon Droid DNA
Followed all the guided method , got to a point of where Relocked/S-ON
Unable to use RUU downloaded , check MD5 all correct
Try moonshine to enable S-OFF
flashed firmware and now stuck at 2.06 firmware
How do i restock?
I am unable to boot anything just the bootloader
fastboot is working fine
Unable to flash any zip hboot downloaded , keep getting signature fail
Unable to Unlocked the bootloader too
I am unable to execute adb commad tho
any suggestion?
BloodRaven2011 said:
I am trying to restock Verizon Droid DNA
Followed all the guided method , got to a point of where Relocked/S-ON
Unable to use RUU downloaded , check MD5 all correct
Try moonshine to enable S-OFF
flashed firmware and now stuck at 2.06 firmware
How do i restock?
I am unable to boot anything just the bootloader
fastboot is working fine
Unable to flash any zip hboot downloaded , keep getting signature fail
Unable to Unlocked the bootloader too
I am unable to execute adb commad tho
any suggestion?
Click to expand...
Click to collapse
You said you tried moonshine to get s-off? did it not work?
You need to be a bit more clear. You are trying to go complete stock or use moonshine to unlock and soff? What error do you get when trying to use ruu?
Hit thanks if I helped! Check out my site at www.circuitsaviors.com
Use moonshine to s off. Go to the thread on how to go back to stock. Follow the directions. The signature is obviously failing because you are s on...
Sent from my HTC6500LVW using xda app-developers app
You might want to check out my thread (http://forum.xda-developers.com/showthread.php?t=2438199), but it's not good news...
jtag is ur only answer. I have a htc dna sitting in my drawer because of this very same reason. I've looked and looked. Sorry
People, you need to RUU BEFORE issuing any s-on commands. I'm seeing this repeatedly.
Phaded said:
People, you need to RUU BEFORE issuing any s-on commands. I'm seeing this repeatedly.
Click to expand...
Click to collapse
This is where the problem rise
I did not realize that is no way to downgrade to stock HBOOT
and the worst part now is i cant do anything
yes , option is to JTAG
BloodRaven2011 said:
This is where the problem rise
I did not realize that is no way to downgrade to stock HBOOT
and the worst part now is i cant do anything
yes , option is to JTAG
Click to expand...
Click to collapse
You could've downgraded your hboot... This also needs to be done before issuing any s-on commands
I am unable to issue a new hboot , i got the signature verification failed. If anyone know how to , it be great , JTAG is my last option tho
Check your PMs. I'd be interested in your results.
I think I had the same signature error a few days ago u need to be on the 1.15 Hboot I couldn't figure it out until i read somewhere not to add a .zip when you rename the hboot zip file and it will flash correctly thru adb hope this helps
http://forum.xda-developers.com/showthread.php?p=42352912
Sent from my HTC6435LVW using Tapatalk 2
xaalfx said:
I think I had the same signature error a few days ago u need to be on the 1.15 Hboot I couldn't figure it out until i read somewhere not to add a .zip when you rename the hboot zip file and it will flash correctly thru adb hope this helps
http://forum.xda-developers.com/showthread.php?p=42352912
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
i am unable to use adb command.
I've been reading thru that before i ask this question
try flashing this is fastboot http://www.mediafire.com/download.php?pj2lknq5gr0jkmf
rename to just PL83IMG.zip
then try to execute
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip PL83IMG.zip
and this will return you to stock hboot let me know how it works out and ill try to help you from there
I'm confused. Maybe someone can answer.
He flashed the 2.06 firmware successfully. That will flash a the new hboot, radio and recovery.
Unless he has a custom splash screen, why would RUU'ing fail.
What happens if the 2.06 firmware it's flashed again?
Does it pass the checks?
Nvm: he can't RUU because the hboot has to 1.15.
Gungrave223 said:
try flashing this is fastboot http://www.mediafire.com/download.php?pj2lknq5gr0jkmf
rename to just PL83IMG.zip
then try to execute
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip PL83IMG.zip
and this will return you to stock hboot let me know how it works out and ill try to help you from there
Click to expand...
Click to collapse
all the above failing due to higher fw
and this causing sgnature verification fail
Gungrave223 said:
try flashing this is fastboot http://www.mediafire.com/download.php?pj2lknq5gr0jkmf
rename to just PL83IMG.zip
then try to execute
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip PL83IMG.zip
and this will return you to stock hboot let me know how it works out and ill try to help you from there
Click to expand...
Click to collapse
fr4nk1yn said:
I'm confused. Maybe someone can answer.
He flashed the 2.06 firmware successfully. That will flash a the new hboot, radio and recovery.
Unless he has a custom splash screen, why would RUU'ing fail.
What happens if the 2.06 firmware it's flashed again?
Does it pass the checks?
Nvm: he can't RUU because the hboot has to 1.15.
Click to expand...
Click to collapse
YEAP ,
It need 1.15
anyhow i can fake this to accept a lower hboot?
with a different sgnature?
BloodRaven2011 said:
YEAP ,
It need 1.15
anyhow i can fake this to accept a lower hboot?
with a different sgnature?
Click to expand...
Click to collapse
It's not a signature issue, it's encryption issue. Newer hboots are unable to decrypt the older ruu zip. If you have a "stockish" rom, you can reflash the 2.06 firmware zip. this will flash a signed kernel and recovery and allow the device to _attempt_ to boot to android. If you can get to android, you can then attempt to s-off again.
If moonshine repeatedly fails (don't drink and shine) and also revone repeatedly fails try this:
In moonshine folder you'll see dnashellroot.apk package
1.) adb install dnashellroot.apk
2.) adb shell
3.) am start -n c.fyf/.MainActivity
4.) (wait 10 seconds)
5.) /dev/sh ($ should turn into #)
6.) echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
^do NOT screw that command up, copy/paste it or risk a brick
7.) exit
8.) exit
9.) adb reboot bootloader
10.) fastboot getvar cid
if it's 22222222, you are good. Proceed to htcdev to unlock, then you can s-off using facepalm.
beaups said:
It's not a signature issue, it's encryption issue. Newer hboots are unable to decrypt the older ruu zip. If you have a "stockish" rom, you can reflash the 2.06 firmware zip. this will flash a signed kernel and recovery and allow the device to _attempt_ to boot to android. If you can get to android, you can then attempt to s-off again.
If moonshine repeatedly fails (don't drink and shine) and also revone repeatedly fails try this:
In moonshine folder you'll see dnashellroot.apk package
1.) adb install dnashellroot.apk
2.) adb shell
3.) am start -n c.fyf/.MainActivity
4.) (wait 10 seconds)
5.) /dev/sh ($ should turn into #)
6.) echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
^do NOT screw that command up, copy/paste it or risk a brick
7.) exit
8.) exit
9.) adb reboot bootloader
10.) fastboot getvar cid
if it's 22222222, you are good. Proceed to htcdev to unlock, then you can s-off using facepalm.
Click to expand...
Click to collapse
I wish i can execute adb command
What seems to be an issue
i dont have any ROM installed now , and the only thing that i can use is fastboot command
I am familiar with adb , and plus i've created custom ROM before but not for HTC
trying to help a cousin but hell , JTAG here is unfamiliar with this model ( not available in Malaysia )
so i would think , this is a deadend but i never gave hope.
Will try to figure something and all help is much appreaciated.
I have experience with HTC EVO phones, but the Rezound is new to me. it's root and s-off are different, and I've gotten myself stuck.
Before I make things worse, I want to ask for some help. I tried flashing the newest CM ROM, while s-on, and now can't get past the HTC boot screen. I can get into the bootloader, and into recovery, but I'm not sure what to flash to get the phone bootable again. I can't mount the USB from TWRP (well I can, but can't see the SD card in either windows on Linux), so I have to take the card, but it into another phone to copy files to it, then put it back into this phone.
So, here is where I am now, how should I proceed?
*** UNLOCKED ***
VIGOR PVT SHIP S-ON RL
HBOOT-2.11.0000
eMMC-boot
TWRP recovery works fine, but I'm not sure what to install from here to fix me up. I have 3 RUU files, (1.02.605.6, 2.01.605.11 and 3.14.605.12 ICS) but can't get the USB connection to work so I need to flash from recovery. I could try connecting to a windows 7 machine (I'm running windows 8 and Ubuntu 13.10)
My goal is to get back to something stock, so I can s-off, so I can install a recent ICS build and use a Verizon phone with the Telcel GSM network in Mexico.
All help is much appreciated!!
JustinChase said:
I have experience with HTC EVO phones, but the Rezound is new to me. it's root and s-off are different, and I've gotten myself stuck.
Before I make things worse, I want to ask for some help. I tried flashing the newest CM ROM, while s-on, and now can't get past the HTC boot screen. I can get into the bootloader, and into recovery, but I'm not sure what to flash to get the phone bootable again. I can't mount the USB from TWRP (well I can, but can't see the SD card in either windows on Linux), so I have to take the card, but it into another phone to copy files to it, then put it back into this phone.
So, here is where I am now, how should I proceed?
*** UNLOCKED ***
VIGOR PVT SHIP S-ON RL
HBOOT-2.11.0000
eMMC-boot
TWRP recovery works fine, but I'm not sure what to install from here to fix me up. I have 3 RUU files, (1.02.605.6, 2.01.605.11 and 3.14.605.12 ICS) but can't get the USB connection to work so I need to flash from recovery. I could try connecting to a windows 7 machine (I'm running windows 8 and Ubuntu 13.10)
My goal is to get back to something stock, so I can s-off, so I can install a recent ICS build and use a Verizon phone with the Telcel GSM network in Mexico.
All help is much appreciated!!
Click to expand...
Click to collapse
the reason you are stuck is because you have to fastboot flash the boot.img exctracted from that rom via fastboot usb in the bootloader...you must also have an unlocked bootloader to do this....if you need further instructions ill be glad to help.....as for the RUU's you need to be s-off and have a relocked bootloader for them to work or you can brick the device
REV3NT3CH said:
the reason you are stuck is because you have to fastboot flash the boot.img exctracted from that rom via fastboot usb in the bootloader...you must also have an unlocked bootloader to do this....if you need further instructions ill be glad to help.....as for the RUU's you need to be s-off and have a relocked bootloader for them to work or you can brick the device
Click to expand...
Click to collapse
Thanks. Considering my goal for now is to get back to a stock ROM so I can get s-off, would it be better to rename an RUU to PH98IMG.zip, then relock my bootloader, then flash the PH98IMG from the bootloader, to get me to a stock/updated/known ROM all in one shot, or do I have to figure out how to flash the boot.img file from the CM ROM, then flash the RUU after that's done. Either way, I need to relock the bootloader to flash or install an RUU, correct?
My Windows 8 computer just seems to have given up on reading/identifying the phone while the phone is in recovery, and I've spent too many hours trying to fix that stupid problem, that I'm almost ready to dump windows 8, and install 7 on this new laptop. I have another w7 laptop in the house that I could use, but if there's a simple HTC drivers for windows 8 fix that actually works, I'd probably rather keep windows 8 and do it all with this machine.
thanks again.
JustinChase said:
Thanks. Considering my goal for now is to get back to a stock ROM so I can get s-off, would it be better to rename an RUU to PH98IMG.zip, then relock my bootloader, then flash the PH98IMG from the bootloader, to get me to a stock/updated/known ROM all in one shot, or do I have to figure out how to flash the boot.img file from the CM ROM, then flash the RUU after that's done. Either way, I need to relock the bootloader to flash or install an RUU, correct?
My Windows 8 computer just seems to have given up on reading/identifying the phone while the phone is in recovery, and I've spent too many hours trying to fix that stupid problem, that I'm almost ready to dump windows 8, and install 7 on this new laptop. I have another w7 laptop in the house that I could use, but if there's a simple HTC drivers for windows 8 fix that actually works, I'd probably rather keep windows 8 and do it all with this machine.
thanks again.
Click to expand...
Click to collapse
ruu is an exe file... ota is a .zip.....your best option to do s-off is install amon ra recovery and install a stock based rom found in Rezound Android Developement....if you follow my s-off guide here in the Rezound [email protected] youll find links to everything you will need.....windows 8 requires special drivers for anything to work....i suggest downgrading to windows 7 if you can as 8 has way too many compatibility issues with anything that requires legacy stuff
REV3NT3CH said:
ruu is an exe file... ota is a .zip.....your best option to do s-off is install amon ra recovery and install a stock based rom found in Rezound Android Developement....if you follow my s-off guide here in the Rezound [email protected] youll find links to everything you will need.....windows 8 requires special drivers for anything to work....i suggest downgrading to windows 7 if you can as 8 has way too many compatibility issues with anything that requires legacy stuff
Click to expand...
Click to collapse
Yeah, I saw someone suggest to rename the RUU.exe file to PH98IMG.zip file to flash it with the bootloader. it this would work, it seems the easiest thing to do from here, but you suggest that it might brick the phone, so I'm not ready to try that yet.
Yes, I was trying to follow your "how to" guide, and you say to flash a stock ROM, and point to one as an example (Global OTA RED-1.0) ROM, but that ROM points to another thread on how to flash ROM with s-on, and it's not particularly clear what one should do, so I'm not sure how to proceed from here, exactly. Here are the steps that are unclear to me...
-adb reboot bootloader
-fastboot erase cache
-fastboot oem lock
-fastboot oem rebootRUU (is this the exact text to type, or do they mean -fastboot oem Global_OTA_RED-v1.0.zip or do they mean -fastboot oem RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed.exe or something else entirely?)
-fastboot flash zip firmware.zip (where am I getting "firmware.zip or is this another example of me needing to replace firmware.zip with something else, and if so, what?)
(it will fail for with pre-update flush again immediately error). So do it again -->
-fastboot flash zip firmware.zip
(it will finish)
when its done:
-fastboot reboot-bootloader
-fastboot flash unlocktoken Unlock_code.bin
-pull the battery and replace.
Once this is done, I think I could then proceed to the s-off process.
[Stupid windows 8 drivers - I will have to install Windows 7 on another partition now ]
JustinChase said:
Yeah, I saw someone suggest to rename the RUU.exe file to PH98IMG.zip file to flash it with the bootloader. it this would work, it seems the easiest thing to do from here, but you suggest that it might brick the phone, so I'm not ready to try that yet.
Yes, I was trying to follow your "how to" guide, and you say to flash a stock ROM, and point to one as an example (Global OTA RED-1.0) ROM, but that ROM points to another thread on how to flash ROM with s-on, and it's not particularly clear what one should do, so I'm not sure how to proceed from here, exactly. Here are the steps that are unclear to me...
-adb reboot bootloader
-fastboot erase cache
-fastboot oem lock
-fastboot oem rebootRUU (is this the exact text to type, or do they mean -fastboot oem Global_OTA_RED-v1.0.zip or do they mean -fastboot oem RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed.exe or something else entirely?)
-fastboot flash zip firmware.zip (where am I getting "firmware.zip or is this another example of me needing to replace firmware.zip with something else, and if so, what?)
(it will fail for with pre-update flush again immediately error). So do it again -->
-fastboot flash zip firmware.zip
(it will finish)
when its done:
-fastboot reboot-bootloader
-fastboot flash unlocktoken Unlock_code.bin
-pull the battery and replace.
Once this is done, I think I could then proceed to the s-off process.
[Stupid windows 8 drivers - I will have to install Windows 7 on another partition now ]
Click to expand...
Click to collapse
no an ruu.exe you run in windows and is a program....a ph98img is an ota update file or something custom made like a recovery and when flashing a rom you have to extract that particular rom with lets say 7 zip...pull the boot.img file out of it and place it in the fastboot folder on your pc.. boot into bootloader on the phone and select the fastboot option then plug it into pc....once the phone says fastboot usb in command prompt direct it using cd C:\yourfastbootdirectory then once you are in fastboot folder in command prompt typt fastboot flash boot boot.img....you only do this after flashing a rom in custom recovery
Edit: btw this is your only option to have a usable rom while s-on including getting to a stock rom again....running the ruu.exe while s-on will brick you....a ph98img.zip with a version of android older than what you are on will brick also or give you a main version is older error
REV3NT3CH said:
no an ruu.exe you run in windows and is a program....a ph98img is an ota update file or something custom made like a recovery and when flashing a rom you have to extract that particular rom with lets say 7 zip...pull the boot.img file out of it and place it in the fastboot folder on your pc.. boot into bootloader on the phone and select the fastboot option then plug it into pc....once the phone says fastboot usb in command prompt direct it using cd C:\yourfastbootdirectory then once you are in fastboot folder in command prompt typt fastboot flash boot boot.img...you only do this after flashing a rom in custom recovery
Edit: btw this is your only option to have a usable rom while s-on including getting to a stock rom again....running the ruu.exe while s-on will brick you....a ph98img.zip with a version of android older than what you are on will brick also or give you a main version is older error
Click to expand...
Click to collapse
Thanks again. I thought it was weird to rename an RUU to the img file, which is why I asked before proceeding. So, since I flashed the CM ROM, I need to pull the boot.img from that same ROM, put it in the android SDK folder on my machine (which is now running Windows 7), then run the fasboot flash boot boot.img and then I should have a functioning phone again.
Then, do the s-off procedure, then I can flash the newest RUU to get everything updated/current, then I can run any ICS ROM from that point.
Sound about right?
Oh, I had to wipe the machine to install windows 7, so I no longer have Ubuntu installed for dual boot. The unlimited site says it only works with Ubuntu 32-bit, and doesn't work with Live USB. I don't want to install 32 bit Ubuntu (rather install 64 bit). What is the best method for s-off, considering these limitations?
thanks again for all your help!!
JustinChase said:
Thanks again. I thought it was weird to rename an RUU to the img file, which is why I asked before proceeding. So, since I flashed the CM ROM, I need to pull the boot.img from that same ROM, put it in the android SDK folder on my machine (which is now running Windows 7), then run the fasboot flash boot boot.img and then I should have a functioning phone again.
Then, do the s-off procedure, then I can flash the newest RUU to get everything updated/current, then I can run any ICS ROM from that point.
Sound about right?
Oh, I had to wipe the machine to install windows 7, so I no longer have Ubuntu installed for dual boot. The unlimited site says it only works with Ubuntu 32-bit, and doesn't work with Live USB. I don't want to install 32 bit Ubuntu (rather install 64 bit). What is the best method for s-off, considering these limitations?
thanks again for all your help!!
Click to expand...
Click to collapse
ive done it on ubuntu 12.04 64 bit....those on higher versions have had to instal the 32bit libs on 64bit which in the comments in my s-off guide a guy posted on how to do just that
REV3NT3CH said:
ive done it on ubuntu 12.04 64 bit....those on higher versions have had to instal the 32bit libs on 64bit which in the comments in my s-off guide a guy posted on how to do just that
Click to expand...
Click to collapse
Worked great!!! I'm now s-off.
Now I just need to figure out how to get updated to the most recent radios and firmware, then pick a new ROM.
Thanks for all your help!
JustinChase said:
Worked great!!! I'm now s-off.
Now I just need to figure out how to get updated to the most recent radios and firmware, then pick a new ROM.
Thanks for all your help!
Click to expand...
Click to collapse
in my downgrade/upgrade guide the ph98img ota's are the updates to most recent hboot and radios...