Related
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
[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
Hi, I recently got a rezound off ebay to replace a broken galaxy nexus. I'm still S-On, cause I can't find the windows software anymore to walk you through it, but I'm htcdev unlocked and rooted. I've tried to install a few different roms, and they flash fine, but trying to flash the boot.img is where I keep getting stuck. The only 2 ways I know how to do it are through fastboot and through hboot as a ph98img file.
In fastboot, the first time I try to flash it, I get a failure message. If I try it again right after, it gets stuck sending the file to the phone and I have to unplug, pop the battery out and restart.
In hboot, it goes through it's thing, then for a second when it should be flashing, it says "parsing," and then goes through the rest of it's thing and nothing happens.
Any ideas? Thanks for any help, and I'm sorry if this has been covered... I've been searching for a few days now and can't find anything similar.
If you're s-off you shouldn't need to fastboot or go through a ph98img.
I'm sorry... that shoulda said S-On. I'll edit the OP.
waldo22 said:
I'm sorry... that shoulda said S-On. I'll edit the OP.
Click to expand...
Click to collapse
I find that the easiest way to flash a ROM is to do
adb reboot bootloader
fastboot boot recoveryname.img
Wipe
Flash ROM
Reboot
Enjoy
By booting into your custom recovery through fastboot, you are essentially in temporary "S-Off" mode so you can flash a ROM without the need to manually flash the boot.img
Of course, if you boot into recovery normally, you will need to do
fastboot flash boot boot.img
But that seems to be giving you problems.
Full guide here:
http://androidforums.com/rezound-all-things-root/587430-s-want-flash-roms-read.html#post4704462
gleggie said:
I find that the easiest way to flash a ROM is to do
adb reboot bootloader
fastboot boot recoveryname.img
Wipe
Flash ROM
Reboot
Enjoy
By booting into your custom recovery through fastboot, you are essentially in temporary "S-Off" mode so you can flash a ROM without the need to manually flash the boot.img
Of course, if you boot into recovery normally, you will need to do
fastboot flash boot boot.img
But that seems to be giving you problems.
Full guide here:
http://androidforums.com/rezound-all-things-root/587430-s-want-flash-roms-read.html#post4704462
Click to expand...
Click to collapse
Interesting... I'll definitely try that method. Thanks!
When I go to flash the recovery through fastboot, it's still freezing the same way it froze when I tried to flash the boot.img file. Seems I have a fastboot issue. I don't know how to begin to fix this. Any help? Thanks in advance!
Info would be greatly appreciated; please reply with all the version #'s you see in the upper left of hboot.
Snuzzo said:
Info would be greatly appreciated; please reply with all the version #'s you see in the upper left of hboot.
Click to expand...
Click to collapse
Thanks for the interest!
Vigor PVT Ship S-ON RL
HBOOT 2.28.0000
Radio 2.23.10.0123r/2.23.10.0124r
OpenDSP v14.6.0.7708.00.0507
eMMC-boot
To me it sounds like its not allowing remote communications, may need to start using ph98img zips. :/
I am still working on LunarTools and they will be ready soon and should completely resolve the issue at hand.
Sent from my Nexus 7 using Tapatalk HD
HTC One (Rogers)
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
S-ON
HBOOT-1.44.0000
Things kinda went sideways when I tried flashing a MOD without making a backup. I know what you're thinking, you can make fun of me all you want lol.
I'm only writing this post after having spent hours reading other posts. I'm kind of confused at this point, what is the easiest way to get my phone working again.
At the moment, I don't have a working ROM installed and I don't have access to my clockworkmod custom recovery. I only have Fastboot to work with. My understanding is that I have the following options:
Somehow Unlock my RELOCKED bootloader and flash a custom ROM
Find the original Rogers Stock ROM for my phone
I'm not sure how to go about doing the first option. And I don't know where I can find the Stock ROM for my phone.
If you have any info you can shed my way, I'd really appreciate it! And if there are similar posts already existing, I apologize for making a new one. I just didn't find anything that speaks to my exact problem out there.
UPDATE: I figured it out! Thank God!! I just had to "fastboot oem rebootRUU" then unlock bootloader, then install custom recover, then custom ROM.
mozer0 said:
HTC One (Rogers)
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
S-ON
HBOOT-1.44.0000
Things kinda went sideways when I tried flashing a MOD without making a backup. I know what you're thinking, you can make fun of me all you want lol.
I'm only writing this post after having spent hours reading other posts. I'm kind of confused at this point, what is the easiest way to get my phone working again.
At the moment, I don't have a working ROM installed and I don't have access to my clockworkmod custom recovery. I only have Fastboot to work with. My understanding is that I have the following options:
Somehow Unlock my RELOCKED bootloader and flash a custom ROM
Find the original Rogers Stock ROM for my phone
I'm not sure how to go about doing the first option. And I don't know where I can find the Stock ROM for my phone.
If you have any info you can shed my way, I'd really appreciate it! And if there are similar posts already existing, I apologize for making a new one. I just didn't find anything that speaks to my exact problem out there.
UPDATE: I figured it out! Thank God!! I just had to "fastboot oem rebootRUU" then unlock bootloader, then install custom recover, then custom ROM.
Click to expand...
Click to collapse
im in the same boat now and have no idea what to do
can you help?
shanewilliamson said:
im in the same boat now and have no idea what to do
can you help?
Click to expand...
Click to collapse
Hi shanewilliamson,
1. Reboot your phone to fastboot mode
2. Connect to PC (assuming you have the fastboot kit on your PC)
3. On the CMD window, type "fastboot oem rebootRUU" and hit Enter.
4. Your phone will ask you if you want to unlock the bootloader. Choose YES
5. Reboot back into fastboot mode. Download your favorite Recovery from the internet, i.e. Clockworkmod or TWRP.
6. Flash Recovery into your phone (tons of tutorials out there on how do this)
7. Reboot your phone into Recovery.
8. Flash your favorite ROM
Hope this helps!
mozer0 said:
Hi shanewilliamson,
1. Reboot your phone to fastboot mode
2. Connect to PC (assuming you have the fastboot kit on your PC)
3. On the CMD window, type "fastboot oem rebootRUU" and hit Enter.
4. Your phone will ask you if you want to unlock the bootloader. Choose YES
5. Reboot back into fastboot mode. Download your favorite Recovery from the internet, i.e. Clockworkmod or TWRP.
6. Flash Recovery into your phone (tons of tutorials out there on how do this)
7. Reboot your phone into Recovery.
8. Flash your favorite ROM
Hope this helps!
Click to expand...
Click to collapse
hi,
thanks for getting back to me but its not working
phone just has a black screen with silver htc logo on it when i do this
shanewilliamson said:
hi,
thanks for getting back to me but its not working
phone just has a black screen with silver htc logo on it when i do this
Click to expand...
Click to collapse
Try fastboot oem boot
Then fastboot oem rebootRUU
Your phone is RELOCKED right?
mozer0 said:
Try fastboot oem boot
Then fastboot oem rebootRUU
Your phone is RELOCKED right?
Click to expand...
Click to collapse
hi,
fastboot oem rebootRUU runs through a load on the cmd prompt
last line is failed (status read failed (too many links))
how do i know if the phone is unlocked or relocked now?
shanewilliamson said:
hi,
fastboot oem rebootRUU runs through a load on the cmd prompt
last line is failed (status read failed (too many links))
how do i know if the phone is unlocked or relocked now?
Click to expand...
Click to collapse
First line on the bootloader screen (highlighted in purple)
mozer0 said:
First line on the bootloader screen (highlighted in purple)
Click to expand...
Click to collapse
yes its unlocked
says
tampered
unlocked
shanewilliamson said:
yes its unlocked
says
tampered
unlocked
Click to expand...
Click to collapse
Oh... you're good then, you don't need "fastboot oem rebootRUU".
Do you have a custom recovery installed too? TWRP or Clockworkmod?
mozer0 said:
Oh... you're good then, you don't need "fastboot oem rebootRUU".
Do you have a custom recovery installed too? TWRP or Clockworkmod?
Click to expand...
Click to collapse
i had twrp installed before i flashed the wrong rom
now all i have is the boot loader screen
im trying to install a custom recovery and cant
process goes through ok on the cmd p
shanewilliamson said:
i had twrp installed before i flashed the wrong rom
now all i have is the boot loader screen
im trying to install a custom recovery and cant
process goes through ok on the cmd p
Click to expand...
Click to collapse
Have a look here >> http://forum.xda-developers.com/showthread.php?t=2529225
clsA said:
Have a look here >> http://forum.xda-developers.com/showthread.php?t=2529225
Click to expand...
Click to collapse
i have the twrp image file and use fastboot to put on the phone but i wont work
so cant get any further
shanewilliamson said:
i have the twrp image file and use fastboot to put on the phone but i wont work
so cant get any further
Click to expand...
Click to collapse
type the steps you use to flash TWRP
clsA said:
type the steps you use to flash TWRP
Click to expand...
Click to collapse
first rename the twrp recovery to recovery
then enter the bootloader
connect to pc and open up a CMD window where your adb and fastboot commands are," shift and left mouse to open up CMD "
type fastboot devices. if a random serial no is returned your ok
put your recovery into the adb/fastboot folder and
fastboot flash recovery recovery.img
once done
fastboot erase cache
reboot into bootloader and choose recovery
shanewilliamson said:
first rename the twrp recovery to recovery
then enter the bootloader
connect to pc and open up a CMD window where your adb and fastboot commands are," shift and left mouse to open up CMD "
type fastboot devices. if a random serial no is returned your ok
put your recovery into the adb/fastboot folder and
fastboot flash recovery recovery.img
once done
fastboot erase cache
reboot into bootloader and choose recovery
Click to expand...
Click to collapse
and what happen's when you reboot to the bootloader and choose recovery ?
clsA said:
and what happen's when you reboot to the bootloader and choose recovery ?
Click to expand...
Click to collapse
it just goes back to the boot loader menu
shanewilliamson said:
it just goes back to the boot loader menu
Click to expand...
Click to collapse
Did you do this step ?
Download Canadian 1.55 HBOOT recovery: http://goo.gl/2Kntxz
Make sure you're in the bootloader go into fastboot and make sure the downloaded image is in the same folder as your fastboot.
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
Go into bootloader and then choose Factory Reset - let that finish running <<< Important!
Phone will go out and start bootlooping. Now power off and go back to bootloader mode:
Go into fastboot
fastboot flash recovery <custom recovery>.img
fastboot erase cache
fastboot reboot-bootloader
Now you can go into custom recovery and you should be good to go now.
Click to expand...
Click to collapse
clsA said:
Did you do this step ?
Click to expand...
Click to collapse
just tried all that again in case but exactly the same result
shanewilliamson said:
just tried all that again in case but exactly the same result
Click to expand...
Click to collapse
Seems hopeless
your only hope is someone can rebuild your partitions but with s-on it won't be easy
I'm in the same exact position as the original poster. However, when I'm in the bootloader and connected to my PC. typing
fastboot oem rebootRUU
Click to expand...
Click to collapse
puts the phone into a black screen with a silver HTC logo. Nothing happens afterwards. Any help is appreciated. My end goal is to get this phone back to stock AT&T rom (4.4.2) with Sense 6)
My phone is
Tampered
Relocked
S-On
HBoot 1.44