Hey guys,
So the last time I flashed ROMs was before the ICS update rolled out for the EVO3D. I want to start playing with the new ICS roms, but I'm not quite sure on how to proceed. I was hoping for some instruction. Here's what I have:
JBear Hboot (so S-OFF)
HBOOT - 1.50.5050
RADIO - 1.06.00.1216 (also S-OFF)
Any help would be much appreciated. Thank you
In my impatience, I flashed a stock ICS RUU.exe. I now have HBOOT 1.58 (but not JBear - I believe it is still S-OFF). However, when I try to access Recovery, I get an image of a black phone with a red triangle with an exclamation mark inside of it. Help!
your recovery is wiped. flash it again.
btw what does your bootloader say? s-off? if you're s-on then unlock bootloader then flash recovery
erjune said:
In my impatience, I flashed a stock ICS RUU.exe. I now have HBOOT 1.58 (but not JBear - I believe it is still S-OFF). However, when I try to access Recovery, I get an image of a black phone with a red triangle with an exclamation mark inside of it. Help!
Click to expand...
Click to collapse
You're fine. Since you are S-OFF you just need to download and flash a custom bootloader and then reflash your recovery via the "fastboot flash recovery recovery.img" command, then you can flash or restore a rooted ROM.
The stock 1.58 bootloader you have now won't let you run that fastboot command without doing the htc unlock, and the custom bootloader is a better choice. Once you unlock the bootloader, it will show "***RELOCKED***" instead of "***LOCKED***" if you return to stock, and that flags to HTC/Sprint that your phone has been unlocked. You could also flash a custom recovery using a PG86IMG.zip file if that's easier.
BTW, the next time you start a thread with a question it should be in the Q&A forum.
ramjet73
Thanks for the help, ramjet (and for your post on how to change hboot when S-OFF)! I thought I did post this in Q/A - sorry! If a mod could move this thread there, that would be great.
I think my problems should be solved, but I'll post again if I run into any problems. Thanks again
Related
While trying to restore my Rezound to Stock, I was able to Relock the bootloader but then I haven't been able to get past the Hboot or Fastboot screens to load the ROM. I can't get to recovery or anything. I've tried loading the recovery by using "fastboot flash recovery recovery.img". For some reason it fails. I have the recovery file in the same place as the fastboot file. I'm not sure why it doesn't work. What should I do next, been trying for hours now to get a ROM to boot up... Thanks for your help!
alphaman0606 said:
While trying to restore my Rezound to Stock, I was able to Relock the bootloader but then I haven't been able to get past the Hboot or Fastboot screens to load the ROM. I can't get to recovery or anything. I've tried loading the recovery by using "fastboot flash recovery recovery.img". For some reason it fails. I have the recovery file in the same place as the fastboot file. I'm not sure why it doesn't work. What should I do next, been trying for hours now to get a ROM to boot up... Thanks for your help!
Click to expand...
Click to collapse
you cant flash a recovery file while the bootloader is locked.
Are you on the latest OTA? ICS Leak?
You probably don't have the correct kernel installed. Coming from ICS to GB I'm assuming?
Sent from my Transformer TF101 using Tapatalk 2
You need to unlock again before flashing a recovery
Sent from my Dinc... I mean Rezound
Thanks! It's working now...
Thanks guys! I just had to unlock again and the phone booted up fine! Now I just have to find where I went wrong trying to go back to stock. I believe I may have the wrong "tools" in my root folder?
Go into hboot and type in everything starting at the top. With this info we can help you further.
Sent from my ADR6425LVW using XDA
If you want to go back to stock, you can lock the bootloader and RUU. You'll have to use whatever version your firmware is currently on (so if you flashed the ICS firmware, you would have to use that RUU, if you're on older firmware, flash whatever GB one you're on).
Edit: You can flash to a newer RUU too, obviously, you just won't be able to go backwards again later.
If you have a custom boot image (kernel) or recovery (I think) then the stock locked hboot will have a ***SECURITY WARNING*** and will not allow you to boot. You can still RUU from this state. Unlocking the bootloader will allow you to boot. I believe you cannot RUU from an unlocked bootloader, but I don't remember for sure.
Snuzzo said:
Go into hboot and type in everything starting at the top. With this info we can help you further.
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
Here's what's at the top since I got it unlocked again...
***UNLOCKED***
VIGOR PVT SHIP S-ON RL
HBOOT-2.10.0000
eMMC-boot
Oct 5, 2011, 21:18:48
Hey guys. A while back my phone got screwed up I had to flash the ruu to get it going again. Originally I was on hboot 1.4 rooted/s off via revoked. After I updated with the ruu for the newer radio it now has hboot 1.5 but still says s off. I wasn't able to flash a Rom via clockwork or twrp. So I have a stock Rom without root and I can't figure out where to go from here.
Any ideas?
Bowdowntozoltan said:
Hey guys. A while back my phone got screwed up I had to flash the ruu to get it going again. Originally I was on hboot 1.4 rooted/s off via revoked. After I updated with the ruu for the newer radio it now has hboot 1.5 but still says s off. I wasn't able to flash a Rom via clockwork or twrp. So I have a stock Rom without root and I can't figure out where to go from here.
Any ideas?
Click to expand...
Click to collapse
don't know for sure but IMO you will have to unlock via HTC dev.com, then you will be able to flash anything like you did before . And to root your ROM, just flash a zip file containing superuser apk and binary after doing the above steps.
Also you can revert back to hboot 1.4 ( don't know how exactly ) but don't follow the downgrade thread by unknownforce as you are already s-off
S-Off supercedes being locked. You should still be able to flash roms and have superuser. I was on unlocked on 1.4 with s-off and went to 1.5 showing locked but with s-off and everything still flashes and superuser works fine.
s-off should allow you to do as you please with your phone.. you should still be able to flash w/e recovery you want and w/e rom you want w/o fastboot into recovery..
having s-on in 1.5 is a pain.. but if you already have s-off.. you can just as easily flash back down to 1.4 or even to 1.04 the eng hboot..
but once you're s-off, which you already are, you can do as you please with your device.. you don't need htc dev for it..
EDIT: you might just have to reflash your recovery.. use fastboot flash recovery recovery.img and then boot into it... recovery.img has to be in the same folder as your adb and fastboot files..
hello everyone
I recently installed KingCobra3D ICS 1.2 ROM on my EVO 3D, and it was running well until all of a sudden it started having many issues of turning off while the screen is sleeping (it wont turn back on until I do a battery pull), rebooting, and wont turn on until I do multiple battery pulls. First I thought it was the kernel, so I reflashed the kernel along with the ROM many times, and it still does those issues. My question is, how dp I go back to the original stock Gingerbread firmware without relocking the bootloader? I flashed the ICS ROM, not firmware.
EDIT: I tried restoring my backup from the recovery, but the phone didn't boot after that
any help is greatly appreciated. thanks
extra helpful info:
ROGERS HTC Evo 3D
GSM, Carrier Unlocked
unlocked bootloader via HTCDev method, S-ON, H-BOOT-1.49.0008
madmajd said:
hello everyone
I recently installed KingCobra3D ICS 1.2 ROM on my EVO 3D, and it was running well until all of a sudden it started having many issues of turning off while the screen is sleeping (it wont turn back on until I do a battery pull), rebooting, and wont turn on until I do multiple battery pulls. First I thought it was the kernel, so I reflashed the kernel along with the ROM many times, and it still does those issues. My question is, how dp I go back to the original stock Gingerbread firmware without relocking the bootloader? I flashed the ICS ROM, not firmware.
EDIT: I tried restoring my backup from the recovery, but the phone didn't boot after that
any help is greatly appreciated. thanks
extra helpful info:
ROGERS HTC Evo 3D
GSM, Carrier Unlocked
unlocked bootloader via HTCDev method, S-ON, H-BOOT-1.49.0008
Click to expand...
Click to collapse
Hello madmajd,
S-ON as your phone is you can not flash boot.img(kernel) from the recovery.
Extract boot.img from your gingerbread rom.zip and flash-it from fastboot
Code:
fastboot flash boot boot.img
reboot in recovery, do a full wipe
and flash your rom
sincerely,
fxjumper said:
Hello madmajd,
S-ON as your phone is you can not flash boot.img(kernel) from the recovery.
Extract boot.img from your gingerbread rom.zip and flash-it from fastboot
Code:
fastboot flash boot boot.img
reboot in recovery, do a full wipe
and flash your rom
sincerely,
Click to expand...
Click to collapse
While its true YOU CAN flash the kernel that way its not needed with HTC Unlock...
If u enter your recovery via fastboot command prompt ( fastboot boot your recoveryfilename.img), roms And KERNELS WILL flash like normal from the recovery. Here's some extra info I pm'd to another gsm user...
mpgrimm2 said:
Some key points:
- The ICS /ICS Leaked roms (3.6/4.0) typically have trouble booting the stock kernel on several HTC Unlocked phones. This doesn't seem to occur on S-off phones. (Boot loops are usually a sign of a kernel issue).
- I am on a Sprint CDMA EVO3D & have no idea how to s-off your gsm version/downgrade the bootloader.
- I do have an HTC Unlocked guide in my signature that covers many of the basics for the CDMA version. It's the same process/steps for gsm, but the files used need to be gsm specific from the gsm threads (recovery, kernel, roms, etc).
- If u decide to run an Ruu (exe or zip), you must be locked/relocked & run the same or higher firmware version as currently installed. The exe will work with the phone booted to android or with the bootloader in "fastboot usb". The zip must be renamed exactly PG86IMG.zip and put directly on the root of the sdcard & boot into the bootloader.
- If the phone boots to the bootloader, you can use fastboot command prompt to " unlock" the phone again with your unlock code. Then fastboot flash the recovery again (4ext or Cwm 4.0.1.4 gsm versions recommended), then fastboot boot the recovery, run a superwipe (or format system, data & cache), & flash a gingerbread Rom or one of your nand backups.
- The correct HTC unlocked flashing process (ICS or GB) is to enter recovery via fastboot command prompt, format/superwipe, & flash the Rom (and/or kernel) as you normally would. (4ext Recovery is a solid workaround to using fastboot commands)
Click to expand...
Click to collapse
Sent from my PG86100 using Tapatalk
Sprint HTC EVO 3D
Unlocked
Shooter XC SHIP S-ON RL
HBOOT 1.50.0000
cMMC-boot
Recovery - TWRP 1.1.1
Stuck in bootloop. How do I fix?
wbpo5l said:
Sprint HTC EVO 3D
Unlocked
Shooter XC SHIP S-ON RL
HBOOT 1.50.0000
cMMC-boot
Recovery - TWRP 1.1.1
Stuck in bootloop. How do I fix?
Click to expand...
Click to collapse
Doing what?
You might want to consider upgrading your firmware and getting S-OFF status. I have a guide here that can help.
ramjet73
Too late!
Ok so I followed someone's note to me that said I needed to relock the phone first. So following the instructions for relocking I did the "fastboot oem lock" and now I am "Relocked" but the phone only boots now to Bootloader/Fastboot.
What do I do now?
All I really want to do at this point is get the phone back working. I don't care about root as this phone is going to someone else.
Thanks
wbpo5l said:
What do I do now?
All I really want to do at this point is get the phone back working. I don't care about root as this phone is going to someone else.
Thanks
Click to expand...
Click to collapse
Just do step1 of the guide I linked in my previous post and you will be back to stock.
ramjet73
wbpo5l said:
Sprint HTC EVO 3D
Unlocked
Shooter XC SHIP S-ON RL
HBOOT 1.50.0000
cMMC-boot
Recovery - TWRP 1.1.1
Stuck in bootloop. How do I fix?
Click to expand...
Click to collapse
Hi
I think you need to downgrade to HBOOT 1.49.007 Because versions 1.50.00 and above have a restart issue with custom ROMS
The bad new is that you must spend your HTC EVO 3D S-OFF
I followed this thread to downgrade
http://forum.xda-developers.com/showthread.php?t=17434661
Follow this thread to return to 1.49.007 version of hboot
http://forum.xda-developers.com/showthread.php?t=1906172
If you really want to s-on your phone after this downgrade, you can enter
fastboot oem writesecureflag 3
in fastboot mode, but i don't recommend it
Pay attention to these manipulations and does not hesitate to completely read all the tutorials and all comments.
goodbye,
fxjumper said:
Hi
I think you need to downgrade to HBOOT 1.49.007 Because versions 1.50.00 and above have a restart issue with custom ROMS
The bad new is that you must spend your HTC EVO 3D S-OFF
Click to expand...
Click to collapse
I know he didn't say that, but I think the hboot 1.5 indicates that he has a CDMA model.
ramjet73
Thank you
ramjet73 said:
I know he didn't say that, but I think the hboot 1.5 indicates that he has a CDMA model.
ramjet73
Click to expand...
Click to collapse
ok
Thank you everyone for your help.
Was able to re-lock it and find and install through the correct RUU.exe.
Now my wife has a phone again.
Thanks for taking the time. I've been working at fixing this for hours now, and to no avail. I was following the instructions found here (http://forum.xda-developers.com/showthread.php?t=1808332&highlight=reboot) ...but the short of it was I was upgrading my Hboot so that I could flash a JB ROM. Here's where the problem is, I have no recovery. When I try to access my 4EXT from fastboot, it shows a picture of a phone lying down with the app update symbol (an arrow pointing down with two or three, cant remember right now, around it) over it. Then after a short while it is replaced by a picture of a phone with an exclamation in a triangle. When I try to load a new recovery with SDK it says FAILED (remote: not allowed). I also tried loading back to Hboot 1.50, still nothing. If it matters, my phone came with 1.50.
I greatly appreciate any advice. Here's my current setup.
CDMA Evo 3d
Hboot 1.58 locked S-OFF
Radio 1.09.00.0706
Software 2.89.651.2 710RD
I would download the zip from here: http://forum.xda-developers.com/showthread.php?t=1889438
Then lock the bootloader in fastboot using fastboot oem lock. Run the ruu.exe to put your phone at stock (you'll still be s-off). Hopefully phone will boot.
You would then flash whichever hboot and recovery you want and flash a ROM.
No worries, all the stock hboots (if not unlocked using htcdev) won't allow you to use fast boot to flash recovery/boot partition even though you are s-off.
You can use a custom hboot like revolutionary / juopunutbears / eng hboot to use those commands. To flash another hboot, and just download the respective PG86IMG.zip and put it on the root of sdcard.
OR
If you current ROM is rooted, go to 4ext.net and download the free version and use it to install 4ext recovery on your phone or use flash image gui by joeykrim to flash recovery.
Those two apps will work on any hboot but your ROM should be rooted.
Hope this helps...
How did I know Coal would come to my rescue. Well after more work, and your great advice, I got it working again. The trick was I needed a JBear Hboot zip. Thanks again Coal, you are a legend.
Edit: Thanks mnomaanw, we posted that at the same time hahaha.
Hey everyone I have a problem I just flashed CyanogenMod 10 - GANGNAM STYLE - Nov. 11, 2012 and I am stuck in a boot loop. I am on HBOOT 1.58 with S-OFF but I noticed my bootloader is locked but it use to be unlocked. I came from Mean Rom and I am guessing thats where my bootloader got locked but I am not sure. Anyway even my nandroid backups get me stuck in a boot loop and anything I flash boot loops as well, is that because my bootloader is locked? If so whats the best way to go about unlocking it?
Thanks in advance for any help.
Konfuzion said:
Hey everyone I have a problem I just flashed CyanogenMod 10 - GANGNAM STYLE - Nov. 11, 2012 and I am stuck in a boot loop. I am on HBOOT 1.58 with S-OFF but I noticed my bootloader is locked but it use to be unlocked. I came from Mean Rom and I am guessing thats where my bootloader got locked but I am not sure. Anyway even my nandroid backups get me stuck in a boot loop and anything I flash boot loops as well, is that because my bootloader is locked? If so whats the best way to go about unlocking it?
Click to expand...
Click to collapse
See the "?" in the title of your thread? And the two "?'s" in the last line of your post. We have have a forum for questions called, oddly enough, the Q&A Forum.
Your bootloader is probably locked because you did the wire trick to get S-OFF and that's fine. Don't unlock it. It's better to flash a custom bootloader than using the htcdev method to unlock it again, and that will give you access to same fastboot commands.
For most ROM's you need an hboot lower than 1.58 so I'll refer you to this post and suggest you go with the JBear 1.50.5050 bootloader unless you decide to run a ROM such as Cool ICS or Viper3D that currently requires the 1.58 bootloader.
ramjet73
ramjet73 said:
See the "?" in the title of your thread? And the two "?'s" in the last line of your post. We have have a forum for questions called, oddly enough, the Q&A Forum.
Your bootloader is probably locked because you did the wire trick to get S-OFF and that's fine. Don't unlock it. It's better to flash a custom bootloader than using the htcdev method to unlock it again, and that will give you access to same fastboot commands.
For most ROM's you need an hboot lower than 1.58 so I'll refer you to this post and suggest you go with the JBear 1.50.5050 bootloader unless you decide to run a ROM such as Cool ICS or Viper3D that currently requires the 1.58 bootloader.
ramjet73
Click to expand...
Click to collapse
Thanks for the help, my bad on posting in the wrong section.