Related
i am goin through a really big problem! i was trying to permanently root my phone! but during the revolutionary step it says hboot 1.40.0000 or 1.30.0000 it says 1.40.0000 and it also says it is not supported yet! please help me!
Hi,
you dont need S-OFF for evrything. If you cannot S-OFF,
still you can flash roms, and do most of the things without a problem,
Only thing is you cannot just install custom roms using the recovery menu.
You need to download and installed Android Framework tools and fastboot in your PC to fire ADB Dos commands to your phone via USB to flash the updates.
Let me know.
theRocker_007 said:
Hi,
you dont need S-OFF for evrything. If you cannot S-OFF,
still you can flash roms, and do most of the things without a problem,
Only thing is you cannot just install custom roms using the recovery menu.
You need to download and installed Android Framework tools and fastboot in your PC to fire ADB Dos commands to your phone via USB to flash the updates.
Let me know.
Click to expand...
Click to collapse
You can flash ROMs through recovery on S-on too and it will work fine as long as the new ROM contains the same kernel as your current kernel. And if it contains another kernel use flash Image GUI app or fastboot command to flash tha kernel.
Provided your bootoader is unlocked via www.htcdev.com
mnomaanw said:
You can flash ROMs through recovery on S-on too and it will work fine as long as the new ROM contains the same kernel as your current kernel. And if it contains another kernel use flash Image GUI app or fastboot command to flash tha kernel.
Provided your bootoader is unlocked via www.htcdev.com
Click to expand...
Click to collapse
Most of the time, ROMs does not have the same kernal,
So most of the users who are s-on and new to flashing get stuck on boot loops. Other thing is flash image gui app is a paid application
So best way is to use fastboot commands to flash the kernal after installing the ROM zip file
Cheers..
You could update to hboot 1.50, use the HTCDev unlock and use the Wiretrick to get s-off
[FIX] & [DOWNGRADE HBOOT] - Stupid Bootloop with HBOOT 1.58 EVO 3D - UPDATED 1-7-13
My friend's phone had the annoying bootloop problem. I'm posting this because after a lot of searching, I found nothing to fix the bootloop, just people asking about it. Here's a simply fix.
BOOTLOOP FIX:
If you already tried unlocking/ and you're still S-On, then set everything back to stock:
Flash the attached stock recovery,
fastboot oem lock to be locked again.
Use the latest RUU to update the phone.
At this point the stock, locked phone should function normally.
I have busted this phone a ton of times trying to get different recoveries and roms to work, and this method has always fixed the bootloop.
At this point you can try whatever tutorial you like to downgrade or customize the phone...and if it breaks, hopefully this method will still work for you. If it doesn't work the first time, try running the RUU a second time. Or third.
CUSTOM RECOVERY:
If you want to unlock and install custom stuff:
Use the HTC Dev unlock method.
Fastboot install CWM Recovery v5.8.0.1 from their website -
The ONLY recovery that I've found to be compatible with HBOOT 1.58 is CWM v5.8.0.1. Everything else leaves the phone in an infinite bootloop. Maybe others have had different experiences.
To fastboot install the CWM recovery, rename the file to recovery.img (for simplicity) and type in a command prompt (same directory as fastboot and recovery.img):
fastboot flash recovery recovery.img
Then, to enter into recovery, either pull the battery and enter recovery through the bootloader menu, or type in:
fastboot boot recovery.img
This should get you into the working CWM recovery. If it doesn't, it's because HTC hates people that buy their phones.
If you feel like giving up and running stock, all you need to do is reflash the stock recovery, and relock the phone using fastboot oem lock - and now it should run the stock rom...and if it doesn't, then rerun the RUU. Tedious.
HBOOT Downgrade & S-Off:
If you have: Stock 2.89 RUU / Locked / S-On
Unlocked with HTC Dev method
Flash CWM 5.8.0.1 from the CWM website:
fastboot flash recovery recovery.img - then
fastboot boot recovery.img (to enter recovery)
Flash the SetMainVersionLOW.zip file attached (thanks ramjet73)
Relock the phone with: fastboot oem lock
Use the Unknownforce/closeone hboot downgrade with live CD using the 2.89 RUU's rom.zip (from windows temp folder) renamed to PG86IMG.zip - go to the Unknownforce/closeone thread for this part: http://forum.xda-developers.com/showthread.php?t=1563342
Then flash the standard 1.13 RUU on your windows system (may also work with the PG86IMG.zip method, have not tested)
Then use revolutionary 0.4pre4 to S-Off
Finally, you need to flash a custom recovery which you can do from revolutionary, or from fastboot as listed above. Once the recovery is installed, you should be able to install a compatible custom rom and kernel.
You bootloader screen should now say REVOLUTIONARY on top instead of UNLOCKED or RELOCKED etc... and show HBOOT 1.40.1100.
Thanks to Unkownforce, closeone, and ramjet73 for making this possible.
PS. Screw up your phone at your own risk.
In case anybody was wondering, the RUU I've been using is the latest one at the time of this post: RUU_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1.09.00.0706__NV_NV_SPCS_1.43_release_271101_signed.exe
If by "reset s-on" you mean to switch s-off to s-on using the "write secureflag 3" command, then there is no need to do that., you can directly run RUU.exe on S-OFF and any recovery (hboot needs to be one of the stock versions I guess, I dont know for sure).
And I dont know if theres any relation with hboot version and recovery but TWRP and 4ext recovery works for every hboot. And if you are s-on, you dont always have to flash boot.img seperately using fastboot if you turn smartflash on.
mnomaanw said:
If by "reset s-on" you mean to switch s-off to s-on using the "write secureflag 3" command, then there is no need to do that., you can directly run RUU.exe on S-OFF and any recovery (hboot needs to one of the stock versions, I dont know for sure).
And I dont know if theres any relation with hboot version and recovery but TWRP and 4ext recovery works for every hboot. And if you are s-on, you dont always have to flash boot.img seperately using fastboot if you turn smartflash on.
Click to expand...
Click to collapse
Yeah, don't ever do the write secure flag command. That's bad news. Running a ruu will not s- on, and you're better staying s-off
Sent from my PG86100 using xda app-developers app
Reset s-on, and
fastboot oem lock to be locked again.
Click to expand...
Click to collapse
As others have mentioned, this is completely unnecessary. Once you're s-off htc's unlock is a non-issue and you can run any RUU you wish to at any time.
I know of no reason whatsoever where someone would need to set S-ON once it's off.
xHausx said:
As others have mentioned, this is completely unnecessary. Once you're s-off htc's unlock is a non-issue and you can run any RUU you wish to at any time.
I know of no reason whatsoever where someone would need to set S-ON once it's off.
Click to expand...
Click to collapse
@xHausX
Totally agree. The only reason to set S-ON once S-OFF is achieved is to return to 100% stock for warranty service or to sell the phone.
Nice to see you in these parts again and Happy New Year!
@joshdv
The CWM recovery version (6.0.1.4) you attached to the OP gives an error about accessing mmcblk0p34 when used with the engineering (ENG) bootloader, which a lot of Evo 3D users have installed to run GB or AOSP based ROM's. The current version of TWRP2 (2.3.3.0) has a similar error about the misc partition and I don't know if those errors will affect anything else or not. Apparently those errors are caused by variations in the emmc partition layouts with different bootloaders.
I prefer to use 4EXT which doesn't show any errors once cache+dalvik are formatted.
ramjet73
I updated the OP. I read somewhere else that it was necessary, this phone was never S-Off, so I wasn't sure.
Thanks
Everytime i run the ruu for my 3d it will finish as it has completed and boot. But whenever i remove my battery to switch it with a secondary, i used to do this before bed every night, i get a bootloop and cant boot untill i boot into bootloader and select the recovery option which wipes the phone and boots untill then next time i remove the battery. Why wont the RUU fix this? ive ran it multiple times. And also whenever im in the stock recovery and i select factory reset or any of the options i get "invalid option" "sucess rebooting by reason oem-00" what does this mean!?! can this be my sd? cause i cant mount cache recovery command or mount anything in recovery for that matter. if i need an sd ill buy one. just dont wanna find out its not my sd. and ive run the RUU about 7 times in total and nothing helps. thanks
ramjet73 said:
@joshdv
The CWM recovery version (6.0.1.4) you attached to the OP gives an error about accessing mmcblk0p34 when used with the engineering (ENG) bootloader, which a lot of Evo 3D users have installed to run GB or AOSP based ROM's. The current version of TWRP2 (2.3.3.0) has a similar error about the misc partition and I don't know if those errors will affect anything else or not. Apparently those errors are caused by variations in the emmc partition layouts with different bootloaders.
I prefer to use 4EXT which doesn't show any errors once cache+dalvik are formatted.
ramjet73
Click to expand...
Click to collapse
Yeah, I put WIP because it still never worked right, it was just the only one that ever actually loaded. I still hate this phone, I wish HTC was as nice as Samsung. It's so easy to work with Samsung, I always get mad trying to work around HTC's crippling B.S. Still better than Motorola though.
bootloop in my Htc Evo 3D hboot 1.53.007
How do you flash the stock recovery?
jcthelight said:
How do you flash the stock recovery?
Click to expand...
Click to collapse
put your phone into the bootloader by holding the volume down key while turning it on.
Assuming you have the sdk tools, or some basic set like QADERSO.zip:
select fastboot from the bootloader menu, then connect it to your computer with a usb cable (should change to fastboot usb)
in a command prompt (or terminal window, depending on your OS)
Go into the folder containing both fastboot and the recovery.
Type in: fastboot flash recovery recovery.img (rename the stock recovery included in the OP to just recovery.img)
Once that is complete, you will have the stock recovery.
joshdv said:
put your phone into the bootloader by holding the volume down key while turning it on.
Assuming you have the sdk tools, or some basic set like QADERSO.zip:
select fastboot from the bootloader menu, then connect it to your computer with a usb cable (should change to fastboot usb)
in a command prompt (or terminal window, depending on your OS)
Go into the folder containing both fastboot and the recovery.
Type in: fastboot flash recovery recovery.img (rename the stock recovery included in the OP to just recovery.img)
Once that is complete, you will have the stock recovery.
Click to expand...
Click to collapse
i have hboot 1.53 with s-on stuck on bootloop and i did as u said i flashed stocked recovery from temp folder from ruu-ics-35-ara.exe still my phone is in boot loop. Even i tried oem lock and run ruu.exe file upto 65% process goes fine then suddenly shows 100% process complete and reboot device(still stuck on bootloop).... plz give me suggestion to get rid of this thing.....
"RUU_SHOOTER_U_ICS_35_S_HTC_ARA_3.28.415.2_Radio_11.77.3504.00U_11.25.3504.06_M_release_264795_signed.exe"
joshdv said:
put your phone into the bootloader by holding the volume down key while turning it on.
Assuming you have the sdk tools, or some basic set like QADERSO.zip:
select fastboot from the bootloader menu, then connect it to your computer with a usb cable (should change to fastboot usb)
in a command prompt (or terminal window, depending on your OS)
Go into the folder containing both fastboot and the recovery.
Type in: fastboot flash recovery recovery.img (rename the stock recovery included in the OP to just recovery.img)
Once that is complete, you will have the stock recovery.
Click to expand...
Click to collapse
I'm a little confused. I've never rooted this phone so it's completely stock. My phone keeps powercycling. When I type in "fastboot flash recovery recovery.img" my cmd prompt tells me FAILED (remote: signature verify fail).
Any suggestions?
Re: [FIX] & [DOWNGRADE HBOOT] - Stupid Bootloop with HBOOT 1.58 EVO 3D - UPDATED 1-7-
Dang it! Why does it seem like developers have quit developing fully functioning roms for this phone? I live in a good 4g area so those roms without it are out of the question for me. And the others are having major issues with cameras, video playing, text messaging that keep it from being a daily....
And after using jellybean these ICS roms feel very incomplete even though they're more functional. I know you developers are busy people but please, can ICS get freshened up. Or just ignore me if y'all think the camera/text thing will be resolved very soon.
Sent from my PG86100 using xda premium
Does anyone know how to root a HTC Evo 3D without HTCDev website. For some reason it doesn't work with my device, I have tried a zillion times and always get the Error 170 CID not supported.
Error Code:
Error Code: 170.
Error Reason: CID Not Allowed.
Phone Specs:
android version: 4.0.3
Software Number: 2.29.970.7
hboot: 1.63
Hell Bomb said:
Does anyone know how to root a HTC Evo 3D without HTCDev website. For some reason it doesn't work with my device, I have tried a zillion times and always get the Error 170 CID not supported.
Error Code:
Error Code: 170.
Error Reason: CID Not Allowed.
Phone Specs:
android version: 4.0.3
Software Number: 2.29.970.7
hboot: 1.63
Click to expand...
Click to collapse
You can not because your CID is 170.
You read this to do : http://forum.xda-developers.com/showthread.php?t=2158836.;)
After do this :
1. Your new hboot is : 1.63.2211 ( no longer 1.63.0000) and hboot name : JuopunutBear ( with this hboot you no need unlock bootloader HTCdev).
2. S-Off (no longer S-on) --> now you can change your CID become super CID : 11111111.
3. Now you can Root and up any rom you want.:good:
bttruc said:
You can not because your CID is 170.
You read this to do : http://forum.xda-developers.com/showthread.php?t=2158836.;)
After do this :
1. Your new hboot is : 1.63.2211 ( no longer 1.63.0000) and hboot name : JuopunutBear ( with this hboot you no need unlock bootloader HTCdev).
2. S-Off (no longer S-on) --> now you can change your CID become super CID : 11111111.
3. Now you can Root and up any rom you want.:good:
Click to expand...
Click to collapse
I finally have it unlocked (s-off) but i can't for the life of me figure out how to root it now >.> I used juopunutbear trick after doing temp root to get it perm unlocked.
One issue I have now is when i boot into the bootloader and I click recovery my phone instantly restarts until it goes to the regular lock screen...
[edit]
can't even do a factory reset.
Flash a custom recovery. You can download the TWRP recovery.img here: http://teamw.in/project/twrp2/87
Then go get superSU here: http://forum.xda-developers.com/showthread.php?t=1538053 and put it on your sd card and flash it through recovery! Then you should have root.
Edit: If you don't have a rom installed you will need to flash a rom instead of superSU... I won't suggest one for you as I am on the CDMA version and I don't know what's compatible with your setup.
For recovery though, try reflashing through fastboot usb mode: fastboot flash recovery recoveryname.img
or try booting the recovery with: fastboot boot recoveryname.img
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...