Database Develop

[Q] my hero can't boot into recovery .. Can anyone help me

my hero cdma can't boot into recovery and can't work only in the normal position after use (fastboot oem boot)
when i power the device and unplug USB cable show me in the screen this lines
Code:
HERO XC SHIP S-OFF
HBOOT-1.47.0000 (HERO20000)
MICROP-0110
TOUCH PANEL-SYN0104
RADIO-2.41.05.02.99
Mar 1 2010, 16:02:39
RUU
Even when I press volume down + power .. the screen remains black and does not show anything
I tried a lot to work root and flash recovery.img again by (recovery-RA-heroc-v1.6.2.img) .. but every time i enter ((reboot recovery)) does not appear to me anything except previous message ..
my software v2.27.651.5
pardon me because i can't speak english well .. and I ask for your immediate help

Place this on the root of your sdcard. Boot into hboot (fastboot) and press the down volume key, that's hboot mode. It'll find the HERCIMG.zip, which is just the RUU and after it flashes you're phone will be back to stock.

DoonRoman said:
my hero cdma can't boot into recovery and can't work only in the normal position after use (fastboot oem boot)
when i power the device and unplug USB cable show me in the screen this lines
Code:
HERO XC SHIP S-OFF
HBOOT-1.47.0000 (HERO20000)
MICROP-0110
TOUCH PANEL-SYN0104
RADIO-2.41.05.02.99
Mar 1 2010, 16:02:39
RUU
Even when I press volume down + power .. the screen remains black and does not show anything
I tried a lot to work root and flash recovery.img again by (recovery-RA-heroc-v1.6.2.img) .. but every time i enter ((reboot recovery)) does not appear to me anything except previous message ..
my software v2.27.651.5
pardon me because i can't speak english well .. and I ask for your immediate help
Click to expand...
Click to collapse
Im having the same exact error
what i did first is that i accessed the recovery mode without knowing and i did the wipe/factory default settings
it brought me to a black screen with only the top slider while that the recovery mode was working
later i installed the ruu software 2.27.651.6 and downloaded it from htc website , at the end of the installing it showed file error cant open
i thought i was just that software (and i didnt download it right) later i tried installing the 1.27 , 1.56 , 2.27.651.5 and the 2.27.651.6 again and it still gave me the same error
after searching on the net i found the command fastboot oem boot which works only with 2.27.651.5 and the 2.27.651.6 version now i cant open my htc hero sprint without this command ,
is there a way to fix it ? please help

It sounds to me like the only way you'll be able to fix your phone is through adb. I'm not sure of the exact steps, but read up on the procedures that have been written up on using adb and you should be able to find what you need. That's all I can think of...

cytherian said:
It sounds to me like the only way you'll be able to fix your phone is through adb. I'm not sure of the exact steps, but read up on the procedures that have been written up on using adb and you should be able to find what you need. That's all I can think of...
Click to expand...
Click to collapse
im already familiar to the adb and fastboot commands , tho i dont know the exact steps to fix my problem , because the other steps i found on the net crashes at a point such as flash_image says it cant find the image , and the fastboot flash update.zip says image is not supported

mrxuser said:
im already familiar to the adb and fastboot commands , tho i dont know the exact steps to fix my problem , because the other steps i found on the net crashes at a point such as flash_image says it cant find the image , and the fastboot flash update.zip says image is not supported
Click to expand...
Click to collapse
Bummer... well, sorry I don't know what else to tell you at this point. If you follow the steps for putting your phone completely back to stock and it crashes before it completes, then your phone may have a hardware problem. Did you overclock it at all?

cytherian said:
Bummer... well, sorry I don't know what else to tell you at this point. If you follow the steps for putting your phone completely back to stock and it crashes before it completes, then your phone may have a hardware problem. Did you overclock it at all?
Click to expand...
Click to collapse
what do u mean by overclocking

mrxuser said:
what do u mean by overclocking
Click to expand...
Click to collapse
Overclocking makes the phone faster, in simple terms. It's risky. I assume that you didn't?

ElementalBeatz said:
Overclocking makes the phone faster, in simple terms. It's risky. I assume that you didn't?
Click to expand...
Click to collapse
yes never done it before, would the phone be fixed if i did?

No, I only brought it up because overclocking can challenge the hardware and if it overheats then you might run into functional issues. If you didn't overclock then this isn't a factor.
I don't have my main computer handy with all of my browser shortcuts (I've got quite a library from researching rooting, modding, etc), but I know for certain that there are at least 3+ ways to load a new recovery program onto your phone, or get back to a stock ROM even if you brick your phone. You'll have to take the time to search the forums for those earlier guides, the ones before programs were developed to make rooting and flashing ROM's easier (not needing to know much about adb). AndroidForums has quite a few good ones. Check out their FAQ for the HTC Hero.
One other thing... I noticed your bootloader is 1.47. I had issues with that bootloader, with trying to set S-OFF. I had to override with 1.46. You might want to try an earlier bootloader.

cytherian said:
No, I only brought it up because overclocking can challenge the hardware and if it overheats then you might run into functional issues. If you didn't overclock then this isn't a factor.
I don't have my main computer handy with all of my browser shortcuts (I've got quite a library from researching rooting, modding, etc), but I know for certain that there are at least 3+ ways to load a new recovery program onto your phone, or get back to a stock ROM even if you brick your phone. You'll have to take the time to search the forums for those earlier guides, the ones before programs were developed to make rooting and flashing ROM's easier (not needing to know much about adb). AndroidForums has quite a few good ones. Check out their FAQ for the HTC Hero.
One other thing... I noticed your bootloader is 1.47. I had issues with that bootloader, with trying to set S-OFF. I had to override with 1.46. You might want to try an earlier bootloader.
Click to expand...
Click to collapse
If u dont mind can u show me how to install earilier bootloaders ?

Since you can't get your phone fully booted, you won't be able to use ADB. But if you can load the bootloader into Fastboot USB, then use "fastboot". Read up on the Fastboot Wiki and Flash Tutorial. The only caveat is that I've seen two variations on flashing the bootloader using fastboot. Whereas the Wiki I linked shows "fastboot flash boot boot.img", I've also seen "fastboot flash hboot.img" (but I think that may be a typo--certainly it'll let you know).
If you have a ZIP file instead of an IMG file, there will be an "hboot.img" within the ZIP file. I think the fastboot is intelligent enough to know that it needs to be applied to the boot partition. So, you can also do this:
* fastboot oem rebootRUU //Boot into RUU, which lets you flash HBOOT, radio, etc.
* fastboot flash zip [zipname.zip] //Replace zipname.zip with the actual name of the file you are flashing
-- or --
* fastboot flash boot [boot.img]
However, if your current bootloader state is S-ON, you may not be able to execute those commands successfully. I know for myself I had to install ROM Manager to override the hboot 1.47 S-ON that I had installed, which downgraded the hboot. From there I was able to override and flash hboot 1.46 S-OFF.

cytherian said:
Since you can't get your phone fully booted, you won't be able to use ADB. But if you can load the bootloader into Fastboot USB, then use "fastboot". Read up on the Fastboot Wiki.
Click to expand...
Click to collapse
I already told u that i can use Adb and fastboot , i cant open my phone unless i use this command fastboot oem boot ,

Well good luck with that...

cytherian said:
Since you can't get your phone fully booted, you won't be able to use ADB. But if you can load the bootloader into Fastboot USB, then use "fastboot". Read up on the Fastboot Wiki and Flash Tutorial. The only caveat is that I've seen two variations on flashing the bootloader using fastboot. Whereas the Wiki I linked shows "fastboot flash boot boot.img", I've also seen "fastboot flash hboot.img" (but I think that may be a typo--certainly it'll let you know).
If you have a ZIP file instead of an IMG file, there will be an "hboot.img" within the ZIP file. I think the fastboot is intelligent enough to know that it needs to be applied to the boot partition. So, you can also do this:
* fastboot oem rebootRUU //Boot into RUU, which lets you flash HBOOT, radio, etc.
* fastboot flash zip [zipname.zip] //Replace zipname.zip with the actual name of the file you are flashing
-- or --
* fastboot flash boot [boot.img]
However, if your current bootloader state is S-ON, you may not be able to execute those commands successfully. I know for myself I had to install ROM Manager to override the hboot 1.47 S-ON that I had installed, which downgraded the hboot. From there I was able to override and flash hboot 1.46 S-OFF.
Click to expand...
Click to collapse
here is the problem while flashing using fastboot
fastboot flash radio radio1.img
sending 'radio' (21376 KB)...
OKAY [ 24.089s]
writing 'radio'...
FAILED (remote: image type not support)
finished. total time: 24.108s
or here when i use flash the zip
fastboot flash zip update.zip
sending 'zip' (118067 KB)...
OKAY [129.171s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 132.015s
why does the (remote: image type not support) or the (remote: 24 parsing android-info fail) appear

Have you tried what I posted yet?

Shelnutt2 said:
Have you tried what I posted yet?
Click to expand...
Click to collapse
the problem is that i cant no more enter the hboot menu but i can use the fastboot commands while the Htc silver Logo appears
> fastboot devices
HT9BEHF03035 fastboot
and when i used this command
>fastboot flash zip HERCIMG.zip
sending 'zip' (114210 KB)...
OKAY [129.813s]
writing 'zip'...
its stuck on writing 'zip' and havent done anything for more than 20 min , whats wrong here ??!!

mrxuser said:
the problem is that i cant no more enter the hboot menu but i can use the fastboot commands while the Htc silver Logo appears
> fastboot devices
HT9BEHF03035 fastboot
and when i used this command
>fastboot flash zip HERCIMG.zip
sending 'zip' (114210 KB)...
OKAY [129.813s]
writing 'zip'...
its stuck on writing 'zip' and havent done anything for more than 20 min , whats wrong here ??!!
Click to expand...
Click to collapse
so there's nothing to help

Guys , Arent there anything to do to my program ,,, if somebody knows ,,,, please tell me

[Q] My One won't boot up, no OS?

Hi Guys
I'm in need of urgent help. I rooted my phone and unlocked the bootloader and was going to flash a couple of modded files, one was a more transparent weather widget. Anyways, I somehow ended up with my phone stuck at the "HTC, Quietly Brilliant" screen and it won't boot up. It say's there is no OS installed and I am completely at a loss on what to do because I can't for the life of me understand what RUU I need. I'm in the UK and I bought the phone sim free but none of the resources I've checked seem to be clear. Obviously I am unable to put a ROM on my SDCard as I can't access it so I have no clue how to just get my phone back to stock ... I came from an Xperia Ray where things were so simple. Why isn't there any software from HTC like there is with Sony that lets me reinstallt firmwares? I am at my wits end here with a two day old, £500 phone that I can't even turn on!
PLEASE can someone help me, I know it can be donw but I have no experience with cmd really and there doesn't seem to be any standalone tools to sort it out.
Thanks in advance.

AllAboutTheCore said:
Hi Guys
I'm in need of urgent help. I rooted my phone and unlocked the bootloader and was going to flash a couple of modded files, one was a more transparent weather widget. Anyways, I somehow ended up with my phone stuck at the "HTC, Quietly Brilliant" screen and it won't boot up. It say's there is no OS installed and I am completely at a loss on what to do because I can't for the life of me understand what RUU I need. I'm in the UK and I bought the phone sim free but none of the resources I've checked seem to be clear. Obviously I am unable to put a ROM on my SDCard as I can't access it so I have no clue how to just get my phone back to stock ... I came from an Xperia Ray where things were so simple. Why isn't there any software from HTC like there is with Sony that lets me reinstallt firmwares? I am at my wits end here with a two day old, £500 phone that I can't even turn on!
PLEASE can someone help me, I know it can be donw but I have no experience with cmd really and there doesn't seem to be any standalone tools to sort it out.
Thanks in advance.
Click to expand...
Click to collapse
Can you access the hboot screen on boot up and get into recovery?
If you can, try using the all in one toolkit to sideload a ROM.
http://forum.xda-developers.com/showthread.php?t=2183942
Sent from my HTC One using xda premium

redbull123 said:
Can you access the hboot screen on boot up and get into recovery?
If you can, try using the all in one toolkit to sideload a ROM.
http://forum.xda-developers.com/showthread.php?t=2183942
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Cheers for your reply ... Yes I can get into recovery and for further info I follwed a guide on how to install a stock ROM which I downloaded and follwed the re locking of the bootloader which worked but when it comes to installing the firmware.zip file it works but when it gets to the checking bootloader signature part it always fails and says remote 12 signature verify fail, I'm out of my depth here lol This is what I did:
How to flash?
(bootloader needs to be relocked)
Re-lock your bootloader (this will most probably wipe content of your device)
Copy downloaded .zip to fastboot.exe location (e.g. c:/SDK/platform-tools/fastboot.exe)
Re-name .zip file to firmware.zip
Open command prompt
Boot your device in fastboot mode (vol down + power ===> fastboot)
Connect device to the PC
In command prompt cd to fastboot.exe location
Make sure you have correct modeid and cidnum (type: fastboot getvar all)
Type: fastboot oem lock (if your device is not relocked yet)
Type: fastboot oem rebootRUU and wait for device to reboot
Type: fastboot flash zip firmware.zip and wait for process to complete
Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
Type: fastboot flash zip firmware.zip and wait for process to complete
Type: fastboot reboot
Unlock your bootloader and flash custom recovery if you are going to use custom ROM.
I followed that but when it gets to step 11 it always comes back with this error message:
sending 'zip' (955862 KB)...
OKAY [ 44.588s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 161.891s

Decided to take it back to the shop and they just replaced it luckily enough so problem solved ... Thank f**k, I was getting worried and I'd certainly gone past the point of me being able to resolve the issues as even I'd lost track of what I'd done lol .. Cheers to redbull123 for even trying to help

I need HELP, HTC One (M7wls) Sprint

Okay, first thing first. (INFO ON PHONE) I have a HTC One (M7wls) Sprint 36GB phone. Phone is ROOTED.
bootloader:
*** TAMPERED ***
*** UNLOCKED ***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.55.0000
OpenDSP-v32.120.274.0909
OS-3.05.651.6
eMMC boot 2048MB
What can I access:
Fastboot
ADB Sideload
Recovery - I am using custom recovery - openrecovery-twrp-2.6.3.0-m7wls
Now the problem is:
When I install a ROM. Every ROM that I use didn't fully complete installing. When it boot up, can't access home screen, like i can't even do nothing, If I'm not making any sense what I'm trying, basically I don't have no OS-install. And when I install a ROM and do the ADB sideload and install em I just can't get to the home screen , farthest I can go is the lockscreen, but then that don't even act right, as in either it don't want to slide up (by the way my screen work and digitizer) or its blank/black and I can even slide it up, or as i should say froze for about few sec, AND when i can slide up the lockscreen it goes to the white HTC logo screen and stays there about 45-60sec and Reboot over and over, until i go into either recovery or bootloader and power it down.
ROMs that I've downloaded and install but don't completely works:
- Android_Revolution_HD-One_51.0
- One_4.19.401.8_odexed
- Sprint_HTC_One_1.29.651.10_Stock_Odexed_05.17.13
- Sprint_HTC_One_Stock_Rooted_Odexed_3.05.651.6
- viperROM_One_v1.0.4
What I'm saying is that, for example of What I do to install:
-Boot in Recovery
-Format Data (so i can mount data)
-Erase cache
-Reboot recovery (so the updating partition data can refresh)
-Access ADB Sideload
-Install a ROM (once complete) i reboot the phone
-After all the boot up LOGOs, WHEN I get to the lockscreen it either , 1. don't want to slide up, 2. when do slide up goes to white HTC logo screen get stays about 60sec, then Reboot itself , and 3. Just done want to boot up
Also have Tried RUUs: and Yes I unzip to run the Ruu.exe
- Sprint_HTC_One_m7wls_3_04_651_2_RUU.zip
- Sprint_HTC_One_m7wls_1.29.651.10_RUU.zip
Also and Yes I re-lock my bootloader to run the RUU , still doesn't happen
I'm not sure which one have this problem, but one of em, Do go through the process and once I get to the part to update Image (I realized my phone image is newer than the RUU image) so i proceed anyways, then it comes to a screen where it say ERROR find the latest Update for RUU. THE second one of em , once i run the program and pop-up screen comes where you accept the terms & conditions, once I do accept it; It closes OUT by itself.
I'VE DONE THE BEST I CAN DO , and I'm very frustrated right now. I've look and look and research, But nothing solve my problem, and I APOLOGIZE FOR THIS LONG ARTICLE/QUESTION. But I'm asking for anyone help who can help me get back this phone back on its feet and I will very appreciate for your help !
P.S. I can't get S-OFF , I want to use my AT&T sim card in it.

ilovetechnology123 said:
Okay, first thing first. (INFO ON PHONE) I have a HTC One (M7wls) Sprint 36GB phone. Phone is ROOTED.
bootloader:
*** TAMPERED ***
*** UNLOCKED ***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.55.0000
OpenDSP-v32.120.274.0909
OS-3.05.651.6
eMMC boot 2048MB
What can I access:
Fastboot
ADB Sideload
Recovery - I am using custom recovery - openrecovery-twrp-2.6.3.0-m7wls
Now the problem is:
When I install a ROM. Every ROM that I use didn't fully complete installing. When it boot up, can't access home screen, like i can't even do nothing, If I'm not making any sense what I'm trying, basically I don't have no OS-install. And when I install a ROM and do the ADB sideload and install em I just can't get to the home screen , farthest I can go is the lockscreen, but then that don't even act right, as in either it don't want to slide up (by the way my screen work and digitizer) or its blank/black and I can even slide it up, or as i should say froze for about few sec, AND when i can slide up the lockscreen it goes to the white HTC logo screen and stays there about 45-60sec and Reboot over and over, until i go into either recovery or bootloader and power it down.
ROMs that I've downloaded and install but don't completely works:
- Android_Revolution_HD-One_51.0
- One_4.19.401.8_odexed
- Sprint_HTC_One_1.29.651.10_Stock_Odexed_05.17.13
- Sprint_HTC_One_Stock_Rooted_Odexed_3.05.651.6
- viperROM_One_v1.0.4
What I'm saying is that, for example of What I do to install:
-Boot in Recovery
-Format Data (so i can mount data)
-Erase cache
-Reboot recovery (so the updating partition data can refresh)
-Access ADB Sideload
-Install a ROM (once complete) i reboot the phone
-After all the boot up LOGOs, WHEN I get to the lockscreen it either , 1. don't want to slide up, 2. when do slide up goes to white HTC logo screen get stays about 60sec, then Reboot itself , and 3. Just done want to boot up
Also have Tried RUUs: and Yes I unzip to run the Ruu.exe
- Sprint_HTC_One_m7wls_3_04_651_2_RUU.zip
- Sprint_HTC_One_m7wls_1.29.651.10_RUU.zip
Also and Yes I re-lock my bootloader to run the RUU , still doesn't happen
I'm not sure which one have this problem, but one of em, Do go through the process and once I get to the part to update Image (I realized my phone image is newer than the RUU image) so i proceed anyways, then it comes to a screen where it say ERROR find the latest Update for RUU. THE second one of em , once i run the program and pop-up screen comes where you accept the terms & conditions, once I do accept it; It closes OUT by itself.
I'VE DONE THE BEST I CAN DO , and I'm very frustrated right now. I've look and look and research, But nothing solve my problem, and I APOLOGIZE FOR THIS LONG ARTICLE/QUESTION. But I'm asking for anyone help who can help me get back this phone back on its feet and I will very appreciate for your help !
P.S. I can't get S-OFF , I want to use my AT&T sim card in it.
Click to expand...
Click to collapse
I had a similar problem. Turned out to be a firmware issue.
Boot into fastboot and connect to your computer.
run "fastboot getvar all"
See what firmware you are running.
Pull the firmware from post #3 on Bad Boyz thread
http://forum.xda-developers.com/showthread.php?t=2635051
and run.. the flash is there twice, make sure and do it twice.. it's not a typo.
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip
Fastboot flash zip firmware.zip
Fastboot reboot-bootloader
If you still have trouble, try flashing an older firmware from here..
http://forum.xda-developers.com/showthread.php?t=2503646
In my situation, I flashed to 3.05.651.6 and it would boot, but once I connected to the PC and tried to access the storage on the phone, it would reboot the phone.
Flashing to 4.06.651.4 fixed everything.

Look HERE for the 3.05.651.6 RUU or you can go thru the steps to fix your phone.
From now on stay in the Sprint section to find roms

Puff1911 said:
I had a similar problem. Turned out to be a firmware issue.
Boot into fastboot and connect to your computer.
run "fastboot getvar all"
See what firmware you are running.
Pull the firmware from post #3 on Bad Boyz thread
http://forum.xda-developers.com/showthread.php?t=2635051
and run.. the flash is there twice, make sure and do it twice.. it's not a typo.
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip
Fastboot flash zip firmware.zip
Fastboot reboot-bootloader
If you still have trouble, try flashing an older firmware from here..
http://forum.xda-developers.com/showthread.php?t=2503646
In my situation, I flashed to 3.05.651.6 and it would boot, but once I connected to the PC and tried to access the storage on the phone, it would reboot the phone.
Flashing to 4.06.651.4 fixed everything.
Click to expand...
Click to collapse
Do I need a RUU

Puff1911 said:
I had a similar problem. Turned out to be a firmware issue.
Boot into fastboot and connect to your computer.
run "fastboot getvar all"
See what firmware you are running.
Pull the firmware from post #3 on Bad Boyz thread
http://forum.xda-developers.com/showthread.php?t=2635051
and run.. the flash is there twice, make sure and do it twice.. it's not a typo.
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip
Fastboot flash zip firmware.zip
Fastboot reboot-bootloader
If you still have trouble, try flashing an older firmware from here..
http://forum.xda-developers.com/showthread.php?t=2503646
In my situation, I flashed to 3.05.651.6 and it would boot, but once I connected to the PC and tried to access the storage on the phone, it would reboot the phone.
Flashing to 4.06.651.4 fixed everything.
Click to expand...
Click to collapse
When doing the fastboot commands, it gives me error twice when doing the firmware and YES I renamed it to "firmware.zip"
gives me error message saying "cannot open" and also re-type in command again , same error

hmm.. let me try to duplicate my error later today on one of my test phones and i'll get back to you.
What ROM are you trying to install?

ilovetechnology123 said:
When doing the fastboot commands, it gives me error twice when doing the firmware and YES I renamed it to "firmware.zip"
gives me error message saying "cannot open" and also re-type in command again , same error
Click to expand...
Click to collapse
Make sure it's firmware.zip and not firmware.zip.zip
Window hides extentions as least on my machine it does.
So rename it just firmware and see if that helps

BD619 said:
Make sure it's firmware.zip and not firmware.zip.zip
Window hides extentions as least on my machine it does.
So rename it just firmware and see if that helps
Click to expand...
Click to collapse
That was my mistake, but rename it to "firmware" . now its working. Phone is back up on its feet. lol.
Just want to say thank you for your support and help. Phone is flawless, Thanks you so much again.
HAVE A BLESSED DAY !

I did the same thing by accident. Flashed the old firmware instead of the new by accident and then kept trying to update with the same problems. Since only the first and last digits of the firmware are different and I had them in the same folder I just grabbed the wrong one. All was fixed as with you when I corrected my firmware.

bootloader bricked. Ruu Failed. Need HELP!!!

Hi guys,
I am feeling quite panicked right now since I flash the wrong firmware (lower version) which leads me to failed RUU "Too many links" and then when i reboot to bootloader it constantly boot into four triangles and unable to fastboot oem rebootRUU at all to reflash and my bootloader are in a messed.
I have the same exact problem as this guy http://forum.xda-developers.com/showthread.php?t=2459221 but i don't really understand to solve the problem as i'm not an expertise in this type of problem.
I can still access my phone by manually using "Fastboot oem boot" but other than that i can't power up my phone or boot into bootloader as i have four triangles in each edge of my phone and orange-colored "RUU". I cant flash any rom or firmware or going into my TWRP.
My Phone is S-OFF and Unlocked bootloader.
Here's My partition 19 if needed to solve this issue.
Help me please !

ander427 said:
Hi guys,
I am feeling quite panicked right now since I flash the wrong firmware (lower version) which leads me to failed RUU "Too many links" and then when i reboot to bootloader it constantly boot into four triangles and unable to fastboot oem rebootRUU at all to reflash and my bootloader are in a messed.
I have the same exact problem as this guy http://forum.xda-developers.com/showthread.php?t=2459221 but i don't really understand to solve the problem as i'm not an expertise in this type of problem.
I can still access my phone by manually using "Fastboot oem boot" but other than that i can't power up my phone or boot into bootloader as i have four triangles in each edge of my phone and orange-colored "RUU". I cant flash any rom or firmware or going into my TWRP.
My Phone is S-OFF and Unlocked bootloader.
Here's My partition 19 if needed to solve this issue.
Help me please !
Click to expand...
Click to collapse
First before sending you the modified misc partition, can you please tell us what you have flashed exactly (provide link) and more info about your devices (fastboot getvar all) or at least your CID, MID, Version number you was on before flashing?
I see in your misc partition that the RUU flag is indeed active.
---------- Post added at 04:39 PM ---------- Previous post was at 04:24 PM ----------
however here it is: https://dl.dropboxusercontent.com/u/77459918/p19noRUUflag.img
Code:
fastboot oem boot
then copy the file to the root of your sdcard or you can push it using
Code:
adb push p19noRUUflag.img /sdcard
then to restore it to your misc partition
Code:
adb shell
su
dd if=/sdcard/p19noRUUflag.img of=/dev/block/mmcblk0p19
exit
adb reboot-bootloader
and then flash your RUU.zip and make sure to flash it correctly.
Code:
fastboot oem rebootRUU
fastboot flash zip name_of_ruu.zip
fastboot flash zip name_of_ruu.zip
fastboot reboot
Don't know what ruu you need, if you need help choosing one then post your "fasboot getvar all".
And be very very careful with the "dd" command. If you make a typo, you can brick your phone foor good (writing to the wrong parititon)

IT WORKED !! My Bootloader went back to normal !!! You are a savior and making my day better
Thanks !! Your explanations are really clear and very easy to understand that i able to follow all the steps correctly with ease : )
Well I was using ARHD 71.1 and planning to dirty flash to ARHD 90.0 if possible. Then I was using 5.x.401.x firmware that was used in ARHD 71.1. I have seen that the new ARHD 90.0 are using the latest 7.15.401.1 so i flash to that firmware directly before I plan to install the ROM. And I forgot to place the ROM to the SDCard which then requries me to boot to the O.S in order to access the storage. Then suddenly when i restart my phone, My Phone soft bricked where the phone is stuck at black screen constantly while usually the phone should properly goes to the "HTC One" Phrase and then goes to the O.S but in my case, It first boot into the htc green logo and after a while the screen goes black screen.
I thought the firmware is incompatible with my arhd 71.1 so i downgrade it again 5.x.401.x and then while updating the RUU, I receive "Failed : Too many Links" which quite made my worried so I restart the phone to try if downgrading to the older firmware would fix the issue. But then, the "Four Triangle" issue rise.
I am grateful that you have solve my issue regarding this matter and I cannot be more happier than this that everything went back to normal. Thank You So Much! :good: You are the best !

ander427 said:
IT WORKED !! My Bootloader went back to normal !!! You are a savior and making my day better
Thanks !! Your explanations are really clear and very easy to understand that i able to follow all the steps correctly with ease : )
Well I was using ARHD 71.1 and planning to dirty flash to ARHD 90.0 if possible. Then I was using 5.x.401.x firmware that was used in ARHD 71.1. I have seen that the new ARHD 90.0 are using the latest 7.15.401.1 so i flash to that firmware directly before I plan to install the ROM. And I forgot to place the ROM to the SDCard which then requries me to boot to the O.S in order to access the storage. Then suddenly when i restart my phone, My Phone soft bricked where the phone is stuck at black screen constantly while usually the phone should properly goes to the "HTC One" Phrase and then goes to the O.S but in my case, It first boot into the "Quietly Brilliant" htc green logo and after a while the screen goes black screen.
I thought the firmware is incompatible with my arhd 71.1 so i downgrade it again 5.x.401.x and then while updating the RUU, I receive "Failed : Too many Links" which quite made my worried so I restart the phone to try if downgrading to the older firmware would fix the issue. But then, the "Four Triangle" issue rise.
I am grateful that you have solve my issue regarding this matter and I cannot be more happier than this that everything went back to normal. Thank You So Much! :good: You are the best !
Click to expand...
Click to collapse
you're welcome!

alray said:
you're welcome!
Click to expand...
Click to collapse
damn.. I create another mistake.. I flash the RUU into 7.15.401.1 and I wanted to flash the ARHD 90.0 ROM but suddenly its still in stock recovery, forgot to flash the TWRP.. Now I restart the phone wanting to boot into bootloader fastboot and now i unable to get into the bootlaoder and constantly forced to go into the HTC Green logo screen. And Now It stays on the "Red Triangle Exclamation Mark". What did i do wrong ??

ander427 said:
damn.. I create another mistake.. I flash the RUU into 7.15.401.1 and I wanted to flash the ARHD 90.0 ROM but suddenly its still in stock recovery, forgot to flash the TWRP.. Now I restart the phone wanting to boot into bootloader fastboot and now i unable to get into the bootlaoder and constantly forced to go into the HTC Green logo screen. And Now It stays on the "Red Triangle Exclamation Mark". What did i do wrong ??
Click to expand...
Click to collapse
hold power and volume down until you are in bootloader mode then reflash your custom recovery and after arhd 90

alray said:
hold power and volume down until you are in bootloader mode then reflash your custom recovery and after arhd 90
Click to expand...
Click to collapse
I have tried doing that countinously and the phone wont boot into the bootloader mode in fact it keep restarting normally somehow goes to the HTC Green Logo. Now after continous restart, I able to boot the phone normally into the O.S with Safe Mode. Which Step should I do? to be able to boot into the bootloader.

ander427 said:
I have tried doing that countinously and the phone wont boot into the bootloader mode in fact it keep restarting normally somehow goes to the HTC Green Logo. Now after continous restart, I able to boot the phone normally into the O.S with Safe Mode. Which Step should I do? to be able to boot into the bootloader.
Click to expand...
Click to collapse
when booted in safe mode, open a command prompt and type
Code:
adb reboot bootloader

alray said:
when booted in safe mode, open a command prompt and type
Code:
adb reboot bootloader
Click to expand...
Click to collapse
Thanks For Reminding the way, I forgot that part haha
Thanks now my phone is back to normal !! ThankYou once again Sir !

ander427 said:
Thanks For Reminding the way, I forgot that part haha
Thanks now my phone is back to normal !! ThankYou once again Sir !
Click to expand...
Click to collapse
So your firmware is 7.15.401.1 and you have flashed arhd 90 and everything works fine now?

alray said:
So your firmware is 7.15.401.1 and you have flashed arhd 90 and everything works fine now?
Click to expand...
Click to collapse
Yes! Everything works fine the way it should now

HTC Desire 510 can't do anything with it. Stuck

So here's the story... this is an HTC Desire 510 purchased from Telus here in Canada. I've been messing around with different kernels, ROMs, etc. None of them really worked well for me, so I decided to go back to stock, unlock and try to sell it. Now I'm stuck at the bootloader and I can't figure out what to do. I tried to re-lock the bootloader so I could flash the stock ROM (those were the instructions I read)...
Whenever it boots, it gets to the recovery screen. ("Fastboot USB" / HBOOT) it says *Tampered* and *Relocked* at the top.
Then, when I try to unlock it with Unlock_code.bin (I have tried every method available), and say "Yes", I get the Fastboot USB screen with an overlay that says - at the top: Entering Recovery...
at the bottom it says: This build is for development purposes only, etc.
Then it just stays there until I remove the USB cable and the battery.
I reboot and I get the same thing every time.
Is there any way to fix this? I've tried many an adb command with no avail. I'm ready to throw this thing into the river.

cjmitchell said:
So here's the story... this is an HTC Desire 510 purchased from Telus here in Canada. I've been messing around with different kernels, ROMs, etc. None of them really worked well for me, so I decided to go back to stock, unlock and try to sell it. Now I'm stuck at the bootloader and I can't figure out what to do. I tried to re-lock the bootloader so I could flash the stock ROM (those were the instructions I read)...
Whenever it boots, it gets to the recovery screen. ("Fastboot USB" / HBOOT) it says *Tampered* and *Relocked* at the top.
Then, when I try to unlock it with Unlock_code.bin (I have tried every method available), and say "Yes", I get the Fastboot USB screen with an overlay that says - at the top: Entering Recovery...
at the bottom it says: This build is for development purposes only, etc.
Then it just stays there until I remove the USB cable and the battery.
I reboot and I get the same thing every time.
Is there any way to fix this? I've tried many an adb command with no avail. I'm ready to throw this thing into the river.
Click to expand...
Click to collapse
Is it 64 bit or 32 bit? And what type of recovery did you have on it before?

MrMike2182 said:
Is it 64 bit or 32 bit? And what type of recovery did you have on it before?
Click to expand...
Click to collapse
It's 32 bit and it had TWRP.

cjmitchell said:
It's 32 bit and it had TWRP.
Click to expand...
Click to collapse
What you need to do first of all is find an RUU for your device and then find the original recovery, not the twrp recovery but the actual recovery that was on the phone when you first got it. If you don't flash the original recovery then the RUU will refuse to continue and that's basically HTC's way of trying to prevent us from breaking the phone.. The unlock code you got from HTC you should have kept and whenever you sell the phone pass it along to the new owner.. So to help you understand everything I said first unlock your bootloader again and then flash the original recovery and then lock the bootloader again then run the RUU on the PC.. Some times you have to run the RUU a few times to finally get it to finish completely cause some times it'll hang and just sit there so just end the process and restart it but before ending it be sure you gave it enough time to try before thinking it's stuck because it may not be... After the RUU finishes, the phone will totally be stock again the same way it was the day you bought it..

MrMike2182 said:
What you need to do first of all is find an RUU for your device and then find the original recovery, not the twrp recovery but the actual recovery that was on the phone when you first got it. If you don't flash the original recovery then the RUU will refuse to continue and that's basically HTC's way of trying to prevent us from breaking the phone.. The unlock code you got from HTC you should have kept and whenever you sell the phone pass it along to the new owner.. So to help you understand everything I said first unlock your bootloader again and then flash the original recovery and then lock the bootloader again then run the RUU on the PC.. Some times you have to run the RUU a few times to finally get it to finish completely cause some times it'll hang and just sit there so just end the process and restart it but before ending it be sure you gave it enough time to try before thinking it's stuck because it may not be... After the RUU finishes, the phone will totally be stock again the same way it was the day you bought it..
Click to expand...
Click to collapse
HTC or Telus don't provide a RUU for the Telus version of the phone so I've been trying the Cricket version, doesn't work. It gives me the message: ERROR [131]: CUSTOMER ID ERROR.
There is some russian website that seems to have it for Telus, but you have to pay to access it, and I don't even know if it's what I need. ir-file.com (I can't post links)
So I'm not going down that rabbit hole.
I can't flash any recovery I find...
"fastboot getvar platform" gives me hTCBmsm2886
"fastboot flash recovery (*.img)" gives me a message saying FAILED (remote: signature verify fail) for every single recovery image I can find. Nothing works.

cjmitchell said:
HTC or Telus don't provide a RUU for the Telus version of the phone so I've been trying the Cricket version, doesn't work. It gives me the message: ERROR [131]: CUSTOMER ID ERROR.
There is some russian website that seems to have it for Telus, but you have to pay to access it, and I don't even know if it's what I need. ir-file.com (I can't post links)
So I'm not going down that rabbit hole.
I can't flash any recovery I find...
"fastboot getvar platform" gives me hTCBmsm2886
"fastboot flash recovery (*.img)" gives me a message saying FAILED (remote: signature verify fail) for every single recovery image I can find. Nothing works.
Click to expand...
Click to collapse
Did you try to reflash twrp? If I was in your predicament I'd flash twrp and then there is a rom that I configured to work great on the 32 bit phones it's the Modded CM11 and I'm pretty sure it'll work on yours albeit the cameras aren't working yet at least it's a start and you can find the CM11 I configured here ----> Modded CM11

MrMike2182 said:
Did you try to reflash twrp? If I was in your predicament I'd flash twrp and then there is a rom that I configured to work great on the 32 bit phones it's the Modded CM11 and I'm pretty sure it'll work on yours albeit the cameras aren't working yet at least it's a start and you can find the CM11 I configured here ----> Modded CM11
Click to expand...
Click to collapse
Yeah, I tried to reflash TWRP, I get that message "FAILED: (remote: signature verify fail)"
That is after I type in the C:\adb\ folder "fastboot flash recovery twrp-2.8.7.0-a11.img"
and every other recovery image I can find, including older versions of TWRP.
This is why I'm frustrated, nothing works. If I could flash a ROM that'd be cool, but I can't get out of the bootloader, I can't even get into recovery.

cjmitchell said:
Yeah, I tried to reflash TWRP, I get that message "FAILED: (remote: signature verify fail)"
That is after I type in the C:\adb\ folder "fastboot flash recovery twrp-2.8.7.0-a11.img"
and every other recovery image I can find, including older versions of TWRP.
This is why I'm frustrated, nothing works. If I could flash a ROM that'd be cool, but I can't get out of the bootloader, I can't even get into recovery.
Click to expand...
Click to collapse
I need you to type everything you see on your HBoot screen when you pull the battery and put it back in and then hold the volume down button and then press the power button at the same time and when the screen comes up type everything you see in here so I can see it... I think the reason you're getting the remote signature failure is because the bootloader is still locked and you have to make sure it really is unlocked.. Try that then get back to me.

Yeah, the bootloader is still locked. here's what it says:
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
A11_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.101.1372.19.1121
OpenDSP-v28.2.2.00546.0331
OS-
eMMC-boot 1024MB
Aug 19 2015,21:13:29.0
Then the regular menu.
I can't seem to unlock the bootloader.

cjmitchell said:
Yeah, the bootloader is still locked. here's what it says:
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
A11_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.101.1372.19.1121
OpenDSP-v28.2.2.00546.0331
OS-
eMMC-boot 1024MB
Aug 19 2015,21:13:29.0
Then the regular menu.
I can't seem to unlock the bootloader.
Click to expand...
Click to collapse
Well if you had the boot unlocked before, why can't you send the unlock_code.bin to it and have it unlock again? Or did you lose the key? Because you're supposed to keep that key.. Did you use some sort of program to try and root the phone? Like them 1 click root apps...
---------- Post added at 06:44 PM ---------- Previous post was at 06:40 PM ----------
Go download this to a computer/laptop whatever and connect the phone to it and try to run this RUU on the PC while the phone is connected to it and turned on in HBoot/fastboot... Do this before trying to unlock the boot again and if it hangs try it again because some times it can take 3 or 4 tries to get it to work... Download Cricket RUU - http://dl3.htc.com/application/RUU_A11_UL_K44_DESIRE_SENSE60_AIO_Aio_Wireless_US_1.11.506.8.exe
Edit: I know you said your carrier is Telus and I know that's a Cricket RUU that I listed, but they are both the same so run it!!
Edit again: Never mind don't bother running the RUU because you're not s-off and you can't change your CID so I suggest you find a way to unlock your bootloader again somehow and then flash the CM11 to test out.

MrMike2182 said:
Well if you had the boot unlocked before, why can't you send the unlock_code.bin to it and have it unlock again? Or did you lose the key? Because you're supposed to keep that key.. Did you use some sort of program to try and root the phone? Like them 1 click root apps...
---------- Post added at 06:44 PM ---------- Previous post was at 06:40 PM ----------
Go download this to a computer/laptop whatever and connect the phone to it and try to run this RUU on the PC while the phone is connected to it and turned on in HBoot/fastboot... Do this before trying to unlock the boot again and if it hangs try it again because some times it can take 3 or 4 tries to get it to work... Download Cricket RUU - http://dl3.htc.com/application/RUU_A11_UL_K44_DESIRE_SENSE60_AIO_Aio_Wireless_US_1.11.506.8.exe
Edit: I know you said your carrier is Telus and I know that's a Cricket RUU that I listed, but they are both the same so run it!!
Edit again: Never mind don't bother running the RUU because you're not s-off and you can't change your CID so I suggest you find a way to unlock your bootloader again somehow and then flash the CM11 to test out.
Click to expand...
Click to collapse
I have the unlock_code.bin, I've been trying to send it to the phone but it doesn't work. I've tried the WinDroid app and the command line "fastboot flash unlocktoken unlock_code.bin" and I get to the screen that asks if I want to unlock the bootloader, but when I select "Yes" it hangs and sticks on that screen, but at the top it says: "Entering Recovery..." and at the bottom it says "This build is for development purposes only", etc.
If I can't flash anything then I'm guessing it's perma-bricked... :/

cjmitchell said:
I have the unlock_code.bin, I've been trying to send it to the phone but it doesn't work. I've tried the WinDroid app and the command line "fastboot flash unlocktoken unlock_code.bin" and I get to the screen that asks if I want to unlock the bootloader, but when I select "Yes" it hangs and sticks on that screen, but at the top it says: "Entering Recovery..." and at the bottom it says "This build is for development purposes only", etc.
If I can't flash anything then I'm guessing it's perma-bricked... :/
Click to expand...
Click to collapse
Right it hung there because there was no recovery flashed so right after you unlock that no matter what just flash twrp to it the second after you tap yes to unlock the bootloader send the recovery to it.

MrMike2182 said:
Right it hung there because there was no recovery flashed so right after you unlock that no matter what just flash twrp to it the second after you tap yes to unlock the bootloader send the recovery to it.
Click to expand...
Click to collapse
as soon as I hit the "Yes" option on the "Unlock bootloader?" screen, it tries to go into recovery. And it's instant. There is no window where I can flash the recovery - I've tried it multiple times.
So I can't unlock it and I can't flash a recovery.
I'm afraid this thing is done for...

cjmitchell said:
as soon as I hit the "Yes" option on the "Unlock bootloader?" screen, it tries to go into recovery. And it's instant. There is no window where I can flash the recovery - I've tried it multiple times.
So I can't unlock it and I can't flash a recovery.
I'm afraid this thing is done for...
Click to expand...
Click to collapse
You are supposed to be unlocking it from a PC and flashing the recovery from the PC also not trying to flash the recovery from the phone you cant do that unless the phones working.. Don't you have minimal ADB and Fastboot installed on a Windows PC?