Related
For people who came for an answer, here it is.
download android sdk
download fastboot drivers
get clockworkmod img and rename to imgfile.img
put img in adb tools
put adb, adbwinapi, fastboot, and the img file in c:/Android
plug your phone to the computer
enter the bootloader
click on recovery or fastboot doesnt matter since both will now take you to fastboot
goto computer
type in run in start menu
type cmd in run and hit enter
type cd c:\Android
type fastboot boot imgfile.img
you are now in recovery
go to mounts and storage and mount your device as a disk drive
download any rom to your computer doesnt really matter and put in on your sdcard. If you already have a rom on there then just use that.
unmount your phone
go to wipe data/factory reset and when it finishes flash the rom
once rom is done flashing reboot into android again.
your phone is partially fixed
now go to the market (if you flashed cm then flash the gapps.zip) and download "rom manager"
Then click on download clockworkmod 5.0.0.2 or something like that (first option)
Now go to rom manager and restore your backup that u made (If there was 1 before)
now it will be fixed and your bootloader will take u to recovery instead of fastboot when you click recovery xD
thanks xda
I flashed a rom and the rom must have been corrupted or something and now my phone is stuck rebooting and when I try to go to recovery or any option it takes me to fastboot so now my phone is basically bricked
Your phone is not bricked since your still able to turn it on.
Can you enter fasboot USB?
Send from my Evo 3D using Tapatalk
well it doesnt really turn on its a boot loop but whatever and fastboot is weird it doesnt want to work.
If your bootloader is unlocked make sure you flash the boot.img through fastboot and make sure you wipe
Sent from my ADR6425LVW using XDA
fastboot doesnt work I already tried too flash it
Guys please help!!!!!!!!!!!!!!!!!!
What do you mean by fastboot is wierd. Did you pull the battery?
fastboot doent work cmd always says waiting for device
if i click recovery it takes me to fastboot, btw.
Have you tried an ruu?
anobahar said:
fastboot doent work cmd always says waiting for device
Click to expand...
Click to collapse
Do you have the proper drivers installed
Sent from my ADR6425LVW using XDA
Are you S-Off or S-On? If S-Off, download a PG86IMG.zip of a recovery, and use your bootloader to flash recovery. From that point, just restore a backup or reflash a ROM. If you're not S-Off, I'd say you should try running an RUU, since you can't get fastboot to work. But I think you need to relock your device to run an RUU (if you're S on/ HTC Unlocked), so you'd still need fastboot. Do you have a different USB cable to try? I've seen them fail before even though they still work to charge.
k2buckley said:
Are you S-Off or S-On? If S-Off, download a PG86IMG.zip of a recovery, and use your bootloader to flash recovery. From that point, just restore a backup or reflash a ROM. If you're not S-Off, I'd say you should try running an RUU, since you can't get fastboot to work. But I think you need to relock your device to run an RUU (if you're S on/ HTC Unlocked), so you'd still need fastboot. Do you have a different USB cable to try? I've seen them fail before even though they still work to charge.
Click to expand...
Click to collapse
Sounds like the drivers arn't installed right.. Like you said if he is S-ON and relocked he can run a RUU exe if he is CDMA...
If you are s off then you just need to reload another recovery. And then access a backup of a rom! Or just flash a new one. I had a issue just like this yesterday where my recovery was broken for some reason and had to go from twrp. 2.1 back to 1.1.1 and load another rom.
Sent from my PG86100 using xda premium
Well i put the sdcard in a bberry but a pg6img.img in my sdcard but bootloader doesnt do anything
I am cdma, s-off unlocked with revolutionary kernel 1.4
oops not kernel hboot
Ok, fail, i dont think i hav fastboot drivers downloading now
now cmd is stuck on "sending recovery"
Did you place a copy of the img into your fast boot folder and one in your adb tools folder ???
#Root-Hack_Mod*Always\
it's my first time I flashed my htc
I made a hboot flash to my htc amaze I got in to recovery mode and I received a red triangle I pulled the battery cause I couldn't cancel it.
and now it boot loops I can't get in the fastboot with vol down+power
but the USB charge it and I see 2 removeale device but I can't open this device
am I bricked my htc?
Thanks
I think as long as your computer can recognize your phone, it can be saved. Maybe you can try the unbricking project?
Try this command with adb
fastboot reboot-bootloader
And see if it boots into bootloader. If not then you can try to flash a recovery.img using fastboot commands. But it might not write the image if it doesn't have a proper hboot.
-------------------------------------------------
We are guinea pigs for smart phone technology.
-------------------------------------------------
The red triangle is the symbol you get when you don't have a recovery I believe.
Try flashing a recovery using a toolkit
Sent from my HTC_Amaze_4G using Tapatalk 2
It might be helpful if you provided some more information.
Examples are:
What hboot did you flash?
How did you flash it? What command was used?
What version was your phone running? Gingerbread or ICS?
Is your phone S-OFF'd? (Your phone is probably S-OFF'd already, or else you wouldn't be able to flash the hboot)
Stuff like that can make a world of difference.
Keylogger_0 said:
It might be helpful if you provided some more information.
Examples are:
What hboot did you flash?
How did you flash it? What command was used?
What version was your phone running? Gingerbread or ICS?
Is your phone S-OFF'd? (Your phone is probably S-OFF'd already, or else you wouldn't be able to flash the hboot)
Stuff like that can make a world of difference.
Click to expand...
Click to collapse
I didn't remember I need to check
The command was fastboot flash boot boot.img
Android 2.3.4 sense 3. Gingerbread
it's. S-on .
I cant send command from the computer now, it works like charge mode.
amitvak said:
I didn't remember I need to check
The command was fastboot flash boot boot.img
Android 2.3.4 sense 3. Gingerbread
it's. S-on .
I cant send command from the computer now, it works like charge mode.
Click to expand...
Click to collapse
wait, are you SURE about the command? Are you SURE it wasn't something like this:
fastboot flash hboot hboot.img
because "fastboot flash hboot" and "fastboot flash boot" are 2 different commands.
I recently had this issue with my one xl. I had flashed a wrong recovery, and my boot image was ****ED, couldnt recognize by pc. U need to find ur stock ruu, and run it. Ul get a boot_signed.IMG and a recovery_signed.IMG. flash both in fastboot.
Fastboot flash boot boot_signed.IMG
Fastboot flash recovery recovery_signed.IMG
Eventho web won't recognize it and other things won't, fastboot commands seemed to work, I learned this yesterday.
when I insert fastboot command ...
when I insert fastboot commands it wait for device
http://www.android-dev.us/showthrea...ne-Toolkit-V3-1-4-9-2012-PERM-ROOT-Noob-Proof
use this toolkit... just boot into bootloader (volume down + power) then select the recovery you want.
boot loader is the white screen
i cant get in to the boot loader
I see only the htc white screen and it boot again
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
i cleared everything and i have 2 different roms on the sd but when i install one i get htc boot logo i can get into recovery and hboot which is 1.50 by the way so what do i do? i have no backup and im just confused?
Since you are s-on, you need to make sure you're flashing the kernel separately. Most people have good luck using 4ext with its Smart Flash option.
You have likely hosed up the boot partition/kernel preventing 4ext's Smartflash feature from working. If u enter your recovery via fastboot command prompt you should be able to flash normally and get the rom's kernel to load.
The HTC Unlock/hboot 1.5x Guide (my signature) should help.
Sent from my "Up all night, Sleep all day" EVO3D!
mpgrimm2 said:
You have likely hosed up the boot partition/kernel preventing 4ext's Smartflash feature from working. If u enter your recovery via fastboot command prompt you should be able to flash normally and get the rom's kernel to load.
The HTC Unlock/hboot 1.5x Guide (my signature) should help.
Sent from my "Up all night, Sleep all day" EVO3D!
Click to expand...
Click to collapse
what does that mean and how do i do that?
larikeal said:
what does that mean and how do i do that?
Click to expand...
Click to collapse
It means put your phone in "fastboot usb" mode and from the directory on your PC that contains adb and fastboot issue the following command:
fastboot boot recovery.img
The "recovery.img" parameter is the file name of whatever custom recovery you flashed to root.
After the phone boots up in recovery, just make sure SmartFlash (S-ON) is disabled in the tools menu if you are using 4EXT, then flash the ROM the same way you normally would. This method of starting recovery allows you to flash the boot partition (kernel) from recovery even though you are S-ON.
If you need more information than that, look at the links in the mpgrimm2's signature.
ramjet73
ramjet73 said:
It means put your phone in "fastboot usb" mode and from the directory on your PC that contains adb and fastboot issue the following command:
fastboot boot recovery.img
The "recovery.img" parameter is the file name of whatever custom recovery you flashed to root.
After the phone boots up in recovery, just make sure SmartFlash (S-ON) is disabled in the tools menu if you are using 4EXT, then flash the ROM the same way you normally would. This method of starting recovery allows you to flash the boot partition (kernel) from recovery even though you are S-ON.
If you need more information than that, look at the links in the mpgrimm2's signature.
ramjet73
Click to expand...
Click to collapse
guys same problem here hboot 1.53 S-on and im sure this is the rite rom for my model : 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
but i can complete the process upto 65% flash goes normal then suddenly shows up 100% process complete still stuck on bootloop and i can't able to find the rom anywhere and i donno whether there is problem with rom or phone.
phone status: ***relocked***, s-on, hboot 1.53 RL
any suggestion pls.................
mobileplazza said:
phone status: ***relocked***, s-on, hboot 1.53 RL
any suggestion pls.................
Click to expand...
Click to collapse
You can't flash with a relocked bootloader. Since the phone is S-ON you need to htcdev unlock the bootloader again after flashing the RUU, then install a custom recovery and you should be able to flash successfully or restore a previous nandroid backup.
ramjet73
It's not clear to me, but it almost sounds like MobilePLazza's problem is that he can't flash the full RUU to get back to stock and not sure if he even has the correct RUU.
Same outcome as the OP, but different problem. Perhaps he will clarify.
mpgrimm2 said:
It's not clear to me, but it almost sounds like MobilePLazza's problem is that he can't flash the full RUU to get back to stock and not sure if he even has the correct RUU.
Same outcome as the OP, but different problem. Perhaps he will clarify.
Click to expand...
Click to collapse
ok this is the issure phone is in bootloop now...............i relocked and flashed stock rom (ruu) as i said process 65% goes normal then suddenly shows 100% process complete but still phone in bootloop and im sure nothing is changed in my phone....but i can goto bootloader and even i can unlock phone again.....and i can run fastboot commands ....phone still in s-on.....
@ramjet : even if i flash custom rom after unlocking still my s-on is there to block and its not letting me to process it (no backup is taken b4 im so stupid here)
plz help me to solve this problem i just want this phone to run normally
It looks like you are on a GSM version of the 3d but the process is the same as the Sprint CDMA version we have, just different files (have to trust u on having the right Ruu, recovery, & Rooted Rom files).
Did u put the phone into "fastboot USB" mode, connect to pc and run the Ruu.exe from Windows OS when u did it?
As Ramjet73 was suggesting...
After u unlock the bootloader, are you able to use fastboot commands to flash a recovery.img? ie..
fastboot flash YourRecoveryFileName.img (to install recovery)
Then
fastboot boot YourRecoveryFilename.img (to boot the custom recovery)
Then flash a Rooted Rom from your sdcard with the recovery and reboot.
* keep in mind that you must enter the recovery via the above "fastboot boot.." command prompt every time you want to flash a Rom/kernel with S-on or you will bootloop because the kernel never gets loaded *
Sent from my "Up all night, Sleep all day" EVO3D!
Alright, I might as well post in this semi-fresh topic. I tried to change roms tonight and got stuck in a boot loop. It loads the HTC white screen, starts a little past that and then resets. I've tried wiping my data, and both caches. I've made sure SmartFlash is enabled on 4EXT because I'm S-On. I've tried it with SmartFlash disabled, too. I tried fastboot boot recovery.img to install my rom and my kernel. I can't seem to get out of this loop. Any advice?
Glee, please state your full phone/carrier /specs / recovery/rom if you want help. If you are CDMA/Sprint, I suggest you read through the HTC Unlock/Hboot 1.5x Guide (in my signature), specifically the linked post about flashing Roms/kernels via Fastboot/Recovery. Then you will be better prepared to explain what you've done so far.
Sent from my "Up all night, sleep all day" HP CM9 Touchpad