Related
Hi,
I've been searching through posts for help. But I might have run into a combination of bad luck and noobness, and I can't perform any suggested recovery procedure that I've found smoothly. If you think my problem can be solve by another answered post please link.
My phone was rooted (from the HTCDev tool) and sim unlocked. This morning I started the Update pushed from HTC (that should be the ICS update???). The update last more than 40 minutes (I wasn't watching) and stuck on the HTC boot screen. I thought it's problem hanged, unplugged the battery (maybe I noobed out here? shouldn've waited 4 hours? or do a hard reset instead?).
Anyway, from that point onward it's hang on boot.
I boot it up the the hboot menu. Go to recovery, tried wiping the cache, tried the factory reset. No luck.
Here is what I have on HBOOT
*** UNLOCKED ***
SHOOTER_U PVT SHIP S-ON RL
HBOOT_1.49.0008
eMMC-boot
Jul 15 2011, 14:39:25
When I tried to run the "update from SD card" in the recovery mode I always get the
E:can't open /cache/recovery/command
no matter what I've put in the SD card
When I try to use 4EXTRecovery, it always says error: device not found
I also tried to use revolutionary to turn S-OFF but it always stuck on waiting for device
the fastboot command line from HTC Dev however, can talk to the phone slightly...
fastboot devices
HT17WV302432 fastboot
fastboot oem unlock
...
(bootloader) [ERR] Command error !!!
fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.142s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.007s]
finished. total time: 0.150s
But the phone doesn't turn to the unlock agreement page, phone remains S-ON.
I don't have CWM installed on my phone yet. And I don't know how to get it onto my phone with market place. Putting update.zip in SD card doesn't seem to trigger the phone in any way.
At this point, I think I should?
S-OFF my phone?
See if I can use fastboot to flash any workable ROM / boot / Recovery onto the phone?
Any help would be great.
Thanks a lot.
Gil
If I remember correctly to update to the official OTA you need to put the stock recovery back on your phone and re-lock it.
I don't really care whether it is official OTA or not. I just want to get my phone back to work. Do you have any link to where I can get the OTA and how to do it?
Does it require turning S-OFF? I'm under the impression it is blocking me to do anything. And because my phone is already in a bad state a lot of the tools is not communicating with the phone right now...
No luck with the OTA. I was able to get CWM onto recovery through fastboot, and also tried flashing King Cobra. But the phone still won't be with King Cobra, I'm still on S-ON. Revolutionary still won't connect.
u dont need s-off with 4ext recovery
I had an unlocked EVO3D (htcdev method) and the problem you had happened to me too. The phone stuck at the initial splashscreen and iI had to pull the battery off.
To have my phone back it was enough to use 4ext to restore a saved backup I had
done previously.
If you dont have backups then installing KingCobra (1.5, I have issues with 1.6) should be enough to solve. Copy the rom to the sdcard and then install it via 4EXT.
If you want to go S-OFF i recommend to use the wire-trick method
unlimited.io/juopunutbear-public-beta-0-1/instructions
It's tricky indeed but works very well.
kernBeros said:
I had an unlocked EVO3D (htcdev method) and the problem you had happened to me too. The phone stuck at the initial splashscreen and iI had to pull the battery off.
To have my phone back it was enough to use 4ext to restore a saved backup I had
done previously.
If you dont have backups then installing KingCobra (1.5, I have issues with 1.6) should be enough to solve. Copy the rom to the sdcard and then install it via 4EXT.
If you want to go S-OFF i recommend to use the wire-trick method
unlimited.io/juopunutbear-public-beta-0-1/instructions
It's tricky indeed but works very well.
Click to expand...
Click to collapse
How do you get 4EXT onto the phone? Is there anyway to flash it to recovery? Or do you already have it flashed before? I was trying to find a 4EXT recovery flash but no luck.
I tried using CWM flashed to the recovery and installed King Cobra, it installed but still doesn't boot up. I also tried flashing boot.img onto boot (by using fastboot) but the phone still doesn't boot up. The firmware (PG86IMG.zip) wouldn't flash tho, so maybe I need either S-OFF or 4EXT to do that.
Thanks.
gyt2wong said:
How do you get 4EXT onto the phone? Is there anyway to flash it to recovery? Or do you already have it flashed before? I was trying to find a 4EXT recovery flash but no luck.
I tried using CWM flashed to the recovery and installed King Cobra, it installed but still doesn't boot up. I also tried flashing boot.img onto boot (by using fastboot) but the phone still doesn't boot up. The fireware (PG86IMG.zip) would flash tho, so maybe I need either S-OFF or 4EXT to do that.
Thanks.
Click to expand...
Click to collapse
=================================================================================
DISCLAIMER: I AM NOT RESPONSIBLE IF YOU BRICK / RUIN YOUR PHONE IN ANY WAY.
=================================================================================
4Ext was already flashed. However what you did should be ok. Are you sure that the boot.img that you flashed is the correct one for the ROM that you installed?
The boot.img on the KingCobra main page belongs to the 1.6 version.
You can extract the correct one for the 1.5 version from the ROM zip file.
The path in the zip file is Custom/Kernels/Stock/boot.img
I used the 1.5 version with the original radio without problems.
Fixed this by:
1) Getting the official RUU on ICS.
2) Connect USB in HBOOT
3) Use fastboot to relock the bootloader
4) Run RUU on Windows and successfully flashed everything
So seems like S-ON pluse unlocked bootloader means no no to both official rom and custom rom.
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
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
Hey guys, Little background info, i am on MeanBean (December 2012), i am currently s-on, hboot 2.09 radio 1.12.11
i was looking for some help,i want to install Captain_Throwback so i could eventually use Moonshine and get s-off and than get the new cyanogenmod 11 update. So i transferred Captain_Throwback to my sd card and boot into twrp 2.6.3.0 i used Super wipe and than flash Captain_throwback, it completes fine but when it begins to reboot, i get a bootloop on the htc screen and am stuck here
Thanks for the help
Since you're s-on you'll need to fastboot flash the kernel to get past the bootloop. If you're not familiar, here's a quick guide on getting fastboot setup on your pc:
http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
Once you've got it, just pull the boot.img file out of the rom zip and run
Code:
fastboot flash boot boot.img
at the command prompt from the folder you extracted the boot image to.
You shouldn't need to do it anymore once you're s-off but fastboot and adb are still incredibly useful for other things so they're good to have anyway.
Sent from my EVO LTE