Working on this for 2 straight days. I was previously running ViperRom and decided to switch over to SolidRom. I tried everything to get Solidrom working. "fastboot flash boot" command doesn't seem to flash anything for me and gives me the FAILED (remote: not allowed) message.
As of now i'm running:
Hboot 1.58 "locked"
S-off
Installed the link on SolidRom's forum: /RUU_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1.09.00.0706__NV_SPCS_1.43_release_271101_signed.exe
When i try to get into recovery (revolutionary cwm) it just gives me the htc error screen with a phone and an exclaimation mark.
when i boot my phone up, it looks like its on a stock rom: htc sense 3.6, android 4.0.3, kernel 3.0.16
SOMEONE HELP I'M DYING!
standing by for instructions....
frostyrice said:
Working on this for 2 straight days. I was previously running ViperRom and decided to switch over to SolidRom. I tried everything to get Solidrom working. "fastboot flash boot" command doesn't seem to flash anything for me and gives me the FAILED (remote: not allowed) message.
...
Click to expand...
Click to collapse
It is like that because your HBOOT doesn't allow some fastboot commands. I think you unlocked your phone with "wire-trick", so all you need is to use some HBOOT (like JuoponutBear HBOOT for your phone - CDMA right?, which you can find on www.unlimited.io, or other ones which allow those commands). When you do that, you will be able to use fastboot flash, erase etc...
Also, check http://forum.xda-developers.com/showthread.php?t=1978652, you might find something useful
Sent from my Evo 3D GSM using xda premium
frostyrice said:
When i try to get into recovery (revolutionary cwm) it just gives me the htc error screen with a phone and an exclaimation mark.
when i boot my phone up, it looks like its on a stock rom: htc sense 3.6, android 4.0.3, kernel 3.0.16
SOMEONE HELP I'M DYING!
standing by for instructions....
Click to expand...
Click to collapse
When you flashed the RUU it replaced your CWM recovery with the stock recovery and your Revolutionary hboot with the stock 1.58 bootloader. You need to reflash your Revolutionary bootloader and CWM recovery, although it might be worth considering an upgrade to 4EXT recovery.
Edit: This post is a guide to change your hboot and you should be able to flash a recovery with fastboot after that.
ramjet73
frostyrice said:
Working on this for 2 straight days. I was previously running ViperRom and decided to switch over to SolidRom. I tried everything to get Solidrom working. "fastboot flash boot" command doesn't seem to flash anything for me and gives me the FAILED (remote: not allowed) message.
As of now i'm running:
Hboot 1.58 "locked"
S-off
Installed the link on SolidRom's forum: /RUU_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1.09.00.0706__NV_SPCS_1.43_release_271101_signed.exe
When i try to get into recovery (revolutionary cwm) it just gives me the htc error screen with a phone and an exclaimation mark.
when i boot my phone up, it looks like its on a stock rom: htc sense 3.6, android 4.0.3, kernel 3.0.16
SOMEONE HELP I'M DYING!
standing by for instructions....
Click to expand...
Click to collapse
the command by the way is
"fastboot flash boot boot.img"
try that and if not try back
but that wont fix the recovery screen problem....you have to bkot into hboot ad then go to fastboot ....hook up the usb cable and then type in this : "fastbotr flash recovery (name of your recovery).img"...no spaces...
from there you should get to your old recovery screen
Related
please help...ive rooted phones for awhile now and im trying to do my buddies 3d. I did the htc unlock and installed recovery. The problem is no matter what rom we do it just keeps boot looping...it gets so close to booting up and everytime it boot loops. Weve tried 5 different roms now and im at my witts end. Any info on what to do would be greatly appreciated.
On a side note...my two other buddies have 3ds with hboot 1.5 and everything went fine with them when i rooted and installed rom
newtonfb said:
please help...ive rooted phones for awhile now and im trying to do my buddies 3d. I did the htc unlock and installed recovery. The problem is no matter what rom we do it just keeps boot looping...it gets so close to booting up and everytime it boot loops. Weve tried 5 different roms now and im at my witts end. Any info on what to do would be greatly appreciated.
On a side note...my two other buddies have 3ds with hboot 1.5 and everything went fine with them when i rooted and installed rom
Click to expand...
Click to collapse
Are you sure you are using fastboot to boot recovery, since the phone has hboot 1.50 ? You should use fastboot to flash ROMs with Custom Kernels. And dont forget to wipe Everything before flashing any ROM.
And what is the "Software Number" on that phone? If it is 2.17.651.5 then you can only use the Roms that are based on that Software AFAIK.Otherwise you can try any ROM if you are on Software number "2.08.***.*"
Or
You can try any AOSP or Sense 3.5 ROMS.
I just got a replacement phone last week that had the dreaded 1.5, after having 1.4 since the phones release...i had the same problem, and i had to use flash image GUI to flash the kernel, then reboot to recovery to flash the ROM.
Sent from my PG86100 using Tapatalk
mnomaanw said:
Are you sure you are using fastboot to boot recovery, since the phone has hboot 1.50 ? You should use fastboot to flash ROMs with Custom Kernels. And dont forget to wipe Everything before flashing any ROM.
And what is the "Software Number" on that phone? If it is 2.17.651.5 then you can only use the Roms that are based on that Software AFAIK.Otherwise you can try any ROM if you are on Software number "2.08.***.*"
Or
You can try any AOSP or Sense 3.5 ROMS.
Click to expand...
Click to collapse
Not sure...at the top of the screen it says"unlocked" "shooter xc ship s-on rl"
I press fastboot and then bootloader and it just says "no pmgimg "in green lettering for a few lines
Like i said..i can get into the recovery i loaded but nothing will load.
HTC unlock method will only unlock your bootloader, you still have s-on in fact and flashing some roms give you problems.
That is why I made it s-off after using the HTC method. Did you try leedroid rom? That rom worked for me after using HTC unlock method, but you need to flash the boot.img via fastboot to after that.
That's why I made it s-off so I don't need to do that anymore and can run roms the way they meant to be.
DexterMorganNL said:
HTC unlock method will only unlock your bootloader, you still have s-on in fact and flashing some roms give you problems.
That is why I made it s-off after using the HTC method. Did you try leedroid rom? That rom worked for me after using HTC unlock method, but you need to flash the boot.img via fastboot to after that.
That's why I made it s-off so I don't need to do that anymore and can run roms the way they meant to be.
Click to expand...
Click to collapse
How did you made it S-OFF? which hboot you are on and what was the previous hboot version? Are you GSM or CDMA user?
mnomaanw said:
How did you made it S-OFF? which hboot you are on and what was the previous hboot version? Are you GSM or CDMA user?
Click to expand...
Click to collapse
I used revolutionary-0.4pre4. In fact first I used HTC unlock method and after that I used Free 3VO to downgrade to Hboot version 1.49.0007.
And after that I unlocked it again using HTC method and flashed recovery and after that leedroid rom and i flashed the boot.img from leedroid rom.
And after that I was able to make it s-off with revolutionary.
im done. I just installed CWM and tried to install a couple roms and same thing....they install fine and right when they get past the loadup screen and about to load...they reboot to the htc screen. Now im just going to find how to go back to stock...hopefully
newtonfb said:
im done. I just installed CWM and tried to install a couple roms and same thing....they install fine and right when they get past the loadup screen and about to load...they reboot to the htc screen. Now im just going to find how to go back to stock...hopefully
Click to expand...
Click to collapse
You might be doing something wrong, you should always flash ROMs and Kernels by using your computer.
Boot your phone in bootloader > Select fastboot > connect to PC >phone should say fastboot-USB > open cmd > navigate to fastboot folder > put your recovery in that folder > pull the boot.img from the ROM you are trying to flash and put it in fastboot folder > then type "fastboot flash boot boot.img" > then type "fastboot boot recovery.img (your recovery name might be different so use that name instead) > Your recovery will boot > Wipe everything first > then flash the ROM.....
To go back to stock completely , relock your bootloader by "fastboot oem lock" (this command will lock your bootloader but it will say RE-LOCKED on the top of the bootloader screen. Then run a RUU.exe of a specific software version.
@DexterMorganNL
Check your PM.
mnomaanw said:
You might be doing something wrong, you should always flash ROMs and Kernels by using your computer.
Boot your phone in bootloader > Select fastboot > connect to PC >phone should say fastboot-USB > open cmd > navigate to fastboot folder > put your recovery in that folder > pull the boot.img from the ROM you are trying to flash and put it in fastboot folder > then type "fastboot flash boot boot.img" > then type "fastboot boot recovery.img (your recovery name might be different so use that name instead) > Your recovery will boot > Wipe everything first > then flash the ROM.....
To go back to stock completely , relock your bootloader by "fastboot oem lock" (this command will lock your bootloader but it will say RE-LOCKED on the top of the bootloader screen. Then run a RUU.exe of a specific software version.
@DexterMorganNL
Check your PM.
Click to expand...
Click to collapse
WOW I cant thank you enough man!! I tried that and it worked...i have no idea what i was doing wrong but going through cmd made it work. THANK YOU SIR!!!
newtonfb said:
WOW I cant thank you enough man!! I tried that and it worked...i have no idea what i was doing wrong but going through cmd made it work. THANK YOU SIR!!!
Click to expand...
Click to collapse
No problem.
Glad I could help.
And dont call me SIR lol, I'm a kid.
Hey all,
so i had cleanrom ics installed on my 3vo. i installed it without freizas firmware.
anyways, due to pink camera issues, i needed to get the phone replaced, so i tried downgrading with the 1.13 pg86img (this was before i learned about the downgrade issues).
the system part of the update failed, which made my phone not able to boot past the initial HTC screen.
i then tried installing freizas pg86img to get my phone in working order again. the installation worked, but i still cant boot past the htc screen.
i can boot into the bootloader and access recovery (although its the stock htc recovery so i cant use it), and still have s-off.
any help would be greatly appreciated
alexjzim said:
Hey all,
so i had cleanrom ics installed on my 3vo. i installed it without freizas firmware.
anyways, due to pink camera issues, i needed to get the phone replaced, so i tried downgrading with the 1.13 pg86img (this was before i learned about the downgrade issues).
the system part of the update failed, which made my phone not able to boot past the initial HTC screen.
i then tried installing freizas pg86img to get my phone in working order again. the installation worked, but i still cant boot past the htc screen.
i can boot into the bootloader and access recovery (although its the stock htc recovery so i cant use it), and still have s-off.
any help would be greatly appreciated
Click to expand...
Click to collapse
Use adb to push a recovery.img to your phone then boot into it and flash a nandroid back up.
ehurt152 said:
Use adb to push a recovery.img to your phone then boot into it and flash a nandroid back up.
Click to expand...
Click to collapse
after trying to push the latest clockworkmod with fastboot, i got this:
sending 'recovery' (4726 KB)...
OKAY [ 1.118s]
writing 'recovery'
FAILED (remote:not allowed)
finished. total time: 1.151s
im stuck
If your s-off try running an ruu with the same hboot you have. If it boots up go check usb debugging. Then try to push the recovery via adb or fastboot flash one.
#Root-Hack_Mod*Always\
laie1472 said:
If your s-off try running an ruu with the same hboot you have. If it boots up go check usb debugging. Then try to push the recovery via adb or fastboot flash one.
#Root-Hack_Mod*Always\
Click to expand...
Click to collapse
will an ruu run if i cant boot into the system? if so what should i boot into to get it working
edit: after doing lots of flashing, i was able to boot into the system with the 2.08 ruu. it upgraded my hboot to 1.5 and locked my bootloader, but i still have s-off. i was unable to change the recovery image, it kept failing, so i tried flashing an older ruu to unlock my bootloader. again i got the hboot back to 1.4, but the system part of the update still failed.
any help would be greatly appreciated
You should just flash a recovery threw hboot. Here's the latest twrp hboot.zip
http://db.tt/Zw4KCyW2
Drop it on your sd. Then power the phone off. Then press and hold the volume up button. Then tap/press the power button. Continue to hold the volume up button untill you see a white screen. Then wait you phone should recognize the zip. Follow the on screen instructions from there.
#Root-Hack_Mod*Always\
Ok, so i s-offed my phone using wiretrick. After that i flashed my hboot to 1.49.0007 using this method: http://forum.xda-developers.com/showthread.php?t=1906172
I succesfully s-offed and the hboot works fine.
Everytime i simply try to boot (using only the power button) i get the juopunotbear sign: http://imageshack.us/f/189/brickedevo.jpg/
Note: i can boot into recovery, 4ext says it is in safe mode and that i need to wipe all partitions (i do, the error stays).
I can install anything from my recovery but nothing seems to work.
Any ideas? Downloading the latest EU ICS RUU as we speak.
edit: When trying to flash stuff via fastboot i get the error: FAILED (remote: not allowed)
Edit: Oke serious problem right now, i tried the restore from unlimited.IO whilst i had my normal sd-card in it (32gb) and now it shows only 2gb on my computer, and has the same files as the 2gb. im sure this is the 32gb. any ideas on how to get it back to 32gb?
klect said:
Ok, so i s-offed my phone using wiretrick. After that i flashed my hboot to 1.49.0007 using this method: http://forum.xda-developers.com/showthread.php?t=1906172
I succesfully s-offed and the hboot works fine.
Everytime i simply try to boot (using only the power button) i get the juopunotbear sign: http://imageshack.us/f/189/brickedevo.jpg/
Note: i can boot into recovery, 4ext says it is in safe mode and that i need to wipe all partitions (i do, the error stays).
I can install anything from my recovery but nothing seems to work.
Any ideas? Downloading the latest EU ICS RUU as we speak.
edit: When trying to flash stuff via fastboot i get the error: FAILED (remote: not allowed)
Edit: Oke serious problem right now, i tried the restore from unlimited.IO whilst i had my normal sd-card in it (32gb) and now it shows only 2gb on my computer, and has the same files as the 2gb. im sure this is the 32gb. any ideas on how to get it back to 32gb?
Click to expand...
Click to collapse
I had the same problem,then i relocked my bootloader and flashed stock ruu(u can't flash ruu with unlocked bootloader). If u unlocked bl with htc method it is easy to relock it again- just type in fastboot mode : fastboot oem lock . This should work for u
Sent from my HTC EVO 3D X515m using xda app-developers app
My.hboot is locked,.but s off. I unlocked it before I went to work. Trying fastboot again tomorrow
Sent from my HTC EVO 3D X515m using xda app-developers app
edit: I flashed the stock rom, so i had stock ics yesterday. tried to flash recovery via fastboot with unlocked bootloader few minutes ago, worked!!! So i can flash everything again.
Still weird that i had to unlock my bootloader whilst im s-off...
Fixed it by flashing stock, unlocking bootloader, flashing recovery and flashing super user.
Now booting viper3D!
Hello everybody.
Before posting this thread I have read lots of similar threads, but no answer...
My evo was running fine on Mwakious3D rom v.15.3, I was s-off, 4ext recovery, Hboot 1.49.1107, kernel coolexe (integrated in Mwakious rom).
Yesterday night I had network connection problems, so I tried to switch from GSM only to GSM/CDMA auto and back.
My device freezed and I could not get back it responding, so I pulled the battery out.
Then I put back the battery in and tried to turn it on.
From that moment, when I try to turn it on, it shows the HTC splash screen, then after about 10 seconds it turns off by itself and starts bootlooping.
I tried to enter recovery trough Hboot, but even recovery gets stuck on HTC splash screen and the device gets very very hot, then a bootloop starts. I have to pull the battery out because I fear I can damage it.
So I tried to flash again the boot.img from the rom I was on, through Fastboot in command line. The operation succeeded, but when I tried to reboot, I always got bootloop.
So I tried to fastboot flash a new recovery becaue I thought mine was broken. I tried to flash 4ext, cwm and twrp.
Even this didn't fix the problem: I can't get past HTC splash screen either in normal rebooting nor recovery.
So I tried to flash the P86img.zip contained in this thread at letter E: ht_tp://forum.xda-developers.com/showthread.php?t=1743466 (sorry, I can't post URLs).
Even after flashing that, no way I can get past the HTC splash.. I can't access recovery, even if I try to boot it from fastboot.
I don't know what to do anymore.
Please help!!!
My configuration at the moment:
Hboot 1.49.0007 s-off
Radio: 10.13.9020.08_2m
Recovery: 4ext
Please, help me as soon as possible, you are my only hope to unbrick my Evo 3D!!!
Another information: I try to access the device also via adb.
It returns me empty devices list.
If I run adb usb, it returns me error:no device connected.
I have the HTC drivers v.3.007 installed. I tried both on XP x86 and W7 x64.
Fastboot instead recognizes the device, so that I can flash *.img.
relock hboot and run an RUU. then flash recovery and rom again.
EM|NEM said:
relock hboot and run an RUU. then flash recovery and rom again.
Click to expand...
Click to collapse
Thanks a lot... i'm trying in a couple of hours...
I will feedback if it's working.
Bad news dude!!!
I relocked hboot then ran the latest RUU.
Flashing process proceeds well and completes, but after it the phone keeps bootlooping. Always stuck to HTC splash logo.
In the bootloader menu "recovery" is still there. I can't boot into recovery either because I get the usual bootloop.
Any further ideas?
At the moment I am on
Hboot 1.53.0007 relocked s-on
radio -11.25.3504.06_m
RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed
when I run adb usb it still responds error: device not found
Now I unlocked back Hboot and succeeded in flashing recovery (4ext).
Anyway that f***ing bootloop is still there... I can't access recovery...damnit:crying:
Take out your sdcard and see if you can boot into recovery, taking a shot in the dark but could be a corrupt sdcard
(Don't ask me for help as I couldn't care if your phone explodes, eh!
try "fastboot boot recovery.img" in cmd. but the real problem is that running RUU didnt work. are you sure it flashed completely? I'd say run it again
Sorry, friends, I tried both methods without success...always that bootloop after... Even trying fastboot boot recovery.img... I can't get into recovery menu. Only hboot menu... Maybe I could try once again to flash the RUU.exe after relocking bootloader...any better ideas than mine? I'm starting to lose hope...
Hi,
I have nearly the same issue.
i played to much with reroot and unroot.
Now my evo gsm austria is:
shooter_u pvt shp s-off rl
hboot 1.53.0007
radio 10.13.9020.08_2m
eMMC boot
I can access recovery, but it doesn't matter which rom i flash i always have the bootloop. I even flashed different recoveries and the extracted boot,img from the roms (via fastboot). But i'm stuck in the Bootloop.
When i try to flash an RUU as PG86IMG i get the message CID incorrect.
CID is VODAP120
I hope someone has the answer.
thanx michael
---------- Post added 9th December 2012 at 12:05 AM ---------- Previous post was 8th December 2012 at 11:37 PM ----------
I changed my CID now:
fastboot oem writecid HTC__01
moved a non branded pg86img to the root of my sdcard and it ran through
now my phone is back to hboot 1.49.0007
looks good at the moment
i want to get back to full stock, to get original ICS
but i can't get updates, they always fail during the installation . even when i was locked and s-on
It runs again - back to life
So what did i do next.
The official OTA Update to ICS came down!
But wouldn't install
So i extracted the firmware.zip moved to PG86IMG.zip and flashed over the bootloader.(just 24MB - Boot,Bootloader)
It installed rebooted and at the moment a very long black screen, lets see how long
---------- Post added at 06:45 AM ---------- Previous post was at 06:27 AM ----------
No bootloop, but nothing else too
Next step
extract the rom.zip from "RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed"
moved as PG86IMG.zip to root of SDCARD
and flashing over Bootloader
lets wait
---------- Post added at 06:53 AM ---------- Previous post was at 06:45 AM ----------
YEAH
Android 4.0.3
Sense 3.6
Software
3.28.401.1
And its running
Still S-OFF and unlocked
with H-BOOT 1.53.0007
Radio 11.25.304.06_M
I hope the 12hrs i invested the last 3 days will repay
gianborrello said:
Sorry, friends, I tried both methods without success...always that bootloop after... Even trying fastboot boot recovery.img... I can't get into recovery menu. Only hboot menu... Maybe I could try once again to flash the RUU.exe after relocking bootloader...any better ideas than mine? I'm starting to lose hope...
Click to expand...
Click to collapse
Extract the rom zip file and rename it to PG86IMG.zip , put in root of sdcard and flash in bootloader.
I'm running out of ideas here. Running an RUU is a last failsafe method of restoring your phone to stock but that isnt working for you. Maybe try another ruu(the one which was on your phone when you purchased it)
I'm having some issues aswell.
I flashed 4ext because some roms would get stuck on the htc logo screen for half an hour..
Flashed the NonSense rom, worked fine, made a backup of it.
Then i wanted to test Viper's latest rom with sense 4.0, flashed it with 4ext, successful.
I found NonSense better in my opinion so i went to backup, and restored the ROM. After that i couldn't get any further than the htc logo screen.
I switched to clockwork, twrp but no result. I tried even other ROMs but i still can't get pass that cursed splash screen.
And yes, i deleted cache and dalvik etc..
The only thing i haven't tried is getting the stock rom and flashing it to see if it works.
Also, would some of you be kind enough to give me the recovery.img of the latest version of 4ext? I can't find it anywhere, not even on my sd card.
Thanks, looking forward to your answers.
my advice would be to do a clean install of nonsense rom. Wipe data+factory reset, wipe dalvik cache, install rom.
btw are you s-off or s-on? be sure to turn on smart flash in case you're s-on.
I've attached 4EXT RC5
EM|NEM said:
Extract the rom zip file and rename it to PG86IMG.zip , put in root of sdcard and flash in bootloader.
I'm running out of ideas here. Running an RUU is a last failsafe method of restoring your phone to stock but that isnt working for you. Maybe try another ruu(the one which was on your phone when you purchased it)
Click to expand...
Click to collapse
Alredy tried also this method... always that bootloop...
I'm starting to lose my hopes.
flash boot.img in fastboot again and try
EM|NEM said:
flash boot.img in fastboot again and try
Click to expand...
Click to collapse
I tried... I'm s-on and hboot relocked.
That's what I get:
Code:
C:\Android>fastboot flash boot boot_signed.img
sending 'boot' (4310 KB)...
OKAY [ 0.883s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.466s
Code:
Damnit!!!
you need to unlock bootloader again before flashing boot.img or recovery
EM|NEM said:
you need to unlock bootloader again before flashing boot.img or recovery
Click to expand...
Click to collapse
done...unlocked, flashed boot_signed.img and tried to boot. Always bootloop.
Then flashed recovery_signed.img and tried to boot... again that f***ed bootloop. Starting to hate HTC splash screen!!!!
do you still get the "FAILED (remote: signature verify fail)" error? If so theres something wrong here. And do flash a custom recovery like 4EXT. it should then be recovery.img not the signed one
[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