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
Related
Hi All,
I have unlocked my incredible s via htcdev, and s-on, now after flashing rom my phone is stuck on htc splash screen
i have tried recovery tool aswell still stuck splash screen
Is my phone gone ?
Thanks for any help
jaspreet13 said:
Hi All,
I have unlocked my incredible s via htcdev, and s-on, now after flashing rom my phone is stuck on htc splash screen
i have tried recovery tool aswell still stuck splash screen
Is my phone gone ?
Thanks for any help
Click to expand...
Click to collapse
You should have read and studied the procedure to unlock the boot loader and flash a custom ROM a bit more carefully!
The step you are missing is that you will need to manually flash the ROM's boot.img in FASTBOOT USB mode.
jaspreet13 said:
Hi All,
I have unlocked my incredible s via htcdev, and s-on, now after flashing rom my phone is stuck on htc splash screen
i have tried recovery tool aswell still stuck splash screen
Is my phone gone ?
Thanks for any help
Click to expand...
Click to collapse
You should have read and studied the procedure to unlock the boot loader and flash a custom ROM a bit more carefully!
The step you are missing is that you will need to manually flash the ROM's boot.img in FASTBOOT USB mode.
Click to expand...
Click to collapse
Dang beat me too it. What he said ^^^^^^^^^^^^
tpbklake said:
You should have read and studied the procedure to unlock the boot loader and flash a custom ROM a bit more carefully!
The step you are missing is that you will need to manually flash the ROM's boot.img in FASTBOOT USB mode.
Click to expand...
Click to collapse
Thanks for quick reply
Firstly just want to confirm is my phone still alive or gone ?
If can get any help to get it back to work
jaspreet13 said:
Thanks for quick reply
Firstly just want to confirm is my phone still alive or gone ?
If can get any help to get it back to work
Click to expand...
Click to collapse
Boot it into the boot loader by holding the Volume Down key and press the Power button.
Then you can enter FASTBOOT USB mode and flash the boot.img
Sorry for double posting
tpbklake said:
Boot it into the boot loader by holding the Volume Down key and press the Power button.
Then you can enter FASTBOOT USB mode and flash the boot.img
Click to expand...
Click to collapse
Sorry for double posting, was in panic state.. thats how i flashed rom by holding the Volume Down key and press the Power button.
right now the screen states unlocked in pink
s-on
jaspreet13 said:
Sorry for double posting, was in panic state.. thats how i flashed rom by holding the Volume Down key and press the Power button.
right now the screen states unlocked in pink
s-on
Click to expand...
Click to collapse
Yes, so you should be able to select FASTBOOT instead of RECOVERY to flash the boot.img.
tpbklake said:
Yes, so you should be able to select FASTBOOT instead of RECOVERY to flash the boot.img.
Click to expand...
Click to collapse
yes i have selected FASTBOOT now FASTBOOT USB is highlighted In RED
can you help me with ROM i have tried 2 rom but still phones not passing htc logo splash screen
jaspreet13 said:
yes i have selected FASTBOOT now FASTBOOT USB is highlighted In RED
can you help me with ROM i have tried 2 rom but still phones not passing htc logo splash screen
Click to expand...
Click to collapse
Read the sticky posts on this forum for the information you need.
They will explain what you need to do to flash a boot.img file.
tpbklake said:
Read the sticky posts on this forum for the information you need.
They will explain what you need to do to flash a boot.img file.
Click to expand...
Click to collapse
Just want to know phone can go on working status if i flash rom properly or phones gone ?
jaspreet13 said:
Just want to know phone can go on working status if i flash rom properly or phones gone ?
Click to expand...
Click to collapse
As long as you can get into boot loader, you can bring your phone back to life.
tpbklake said:
As long as you can get into boot loader, you can bring your phone back to life.
Click to expand...
Click to collapse
Thanks thats bit relief, do i have to s-off to flash rom or can install on s-on, its htc incredible s
jaspreet13 said:
Thanks thats bit relief, do i have to s-off to flash rom or can install on s-on, its htc incredible s
Click to expand...
Click to collapse
I suggest to go back and read the procedure that you used to learn about unlocking via HTCDEV.com and flashing a custom recovery. That thread should have everything you need to know.
You can flash a ROM in your current state, but there is a documented step that you missed about flashing the boot.img file.
Phones Dead or what ?
yeaturday night i was able to access fastboot menu(bios) of android, i left my phone in night and now it doesnt turn on so i did some research as though battery may have got discharged( which was the case ) as was not gettin amber light on.
now amber light is there but phone is not turning on
jaspreet13 said:
Thanks thats bit relief, do i have to s-off to flash rom or can install on s-on, its htc incredible s
Click to expand...
Click to collapse
you can install custom roms on your device...after installing the ROM, do not let the device to boot to the boot animation or whatever you call it..
Instead, boot to the bootloader...enter the fastboot menu (fastboot usb if your phone is already connected to your computer)...open a command prompt/terminal and type fastboot devices. If your device is recognized, the output would be your device's serial number...
Copy the boot.img file from the ROM's .zip file to some folder. open a cmd window in that folder/ navigate to that folder in cmd (if already opened)
type fastboot flash boot boot.img
if the boot.img is successfully flashed, you can reboot your device and you should be able to boot properly.
If you are s-on and unlocked via htcdev method, follow the above steps every time you flash a new rom.
If you are s-off, the above method is not needed. You can flash roms and use them without any hassle...
Hope this helps...
---------- Post added at 02:25 PM ---------- Previous post was at 02:21 PM ----------
jaspreet13 said:
yeaturday night i was able to access fastboot menu(bios) of android, i left my phone in night and now it doesnt turn on so i did some research as though battery may have got discharged( which was the case ) as was not gettin amber light on.
now amber light is there but phone is not turning on
Click to expand...
Click to collapse
Looks like the battery has discharged completely. Allow the phone to charge for sometime and then try to turn on the device
Thanks Brother
pavankumarpingali said:
you can install custom roms on your device...after installing the ROM, do not let the device to boot to the boot animation or whatever you call it..
Instead, boot to the bootloader...enter the fastboot menu (fastboot usb if your phone is already connected to your computer)...open a command prompt/terminal and type fastboot devices. If your device is recognized, the output would be your device's serial number...
Copy the boot.img file from the ROM's .zip file to some folder. open a cmd window in that folder/ navigate to that folder in cmd (if already opened)
type fastboot flash boot boot.img
if the boot.img is successfully flashed, you can reboot your device and you should be able to boot properly.
If you are s-on and unlocked via htcdev method, follow the above steps every time you flash a new rom.
If you are s-off, the above method is not needed. You can flash roms and use them without any hassle...
Hope this helps...
---------- Post added at 02:25 PM ---------- Previous post was at 02:21 PM ----------
Looks like the battery has discharged completely. Allow the phone to charge for sometime and then try to turn on the device
Click to expand...
Click to collapse
my phone was working completly fine until i flashed boot image, i think this is what i have done incorrectly.
i have rom zip file on phones sd card and unpacked files of same rom my pc in a folder,
now what i understand is to first unpack and install rom from recovery and then flash from cmd ?
jaspreet13 said:
my phone was working completly fine until i flashed boot image, i think this is what i have done incorrectly.
i have rom zip file on phones sd card and unpacked files of same rom my pc in a folder,
now what i understand is to first unpack and install rom from recovery and then flash from cmd ?
Click to expand...
Click to collapse
No, there is no need to unzip the zip file in your PC...only the boot.img file is required.
First install the ROM from the custom recovery and then boot into the bootloader by pressing the vol down button while the phone restarts. Then, flash the boot.img and you should be able to boot...
Hope this helps...
pavankumarpingali said:
No, you do need to unzip the zip file in your PC...only the boot.img file is required.
First install the ROM from the custom recovery and then boot into the bootloader by pressing the vol down button while the phone restarts. Then, flash the boot.img and you should be able to boot...
Hope this helps...
Click to expand...
Click to collapse
Oh shoot! thats what i did wrong,,..i just flashed boot img without installing rom from customer recovery and phone got stuck on HTC screen :silly:
i am waiting for phone to turn on which is not happening at all..
jaspreet13 said:
Oh shoot! thats what i did wrong,,..i just flashed boot img without installing rom from customer recovery and phone got stuck on HTC screen :silly:
i am waiting for phone to turn on which is not happening at all..
Click to expand...
Click to collapse
Charge it for an hour or so, then remove the battery, reinsert after 10-15 min and try to turn on the device again...sometimes soft reset works
do i have to relock bootloader before flashing rom and installing it
I had unlocked HTC One with Sense, which I had done 4.3 RUU install to convert it to GPe. Fast forward to now... I thought I'd sideload the 4.4 update, and during that process I got
set_metadata_recursive: some changes failed
installation aborted
I thought, great. No problem, I'll just do the traditional RUU again, I'll be fine.
BUT...
Now I can't boot into old OS. The phone keeps rebooting to the recovery. I tried to wipe-data from recovery, which didn't help. I also tried factory reset from HBOOT, and that didn't do anything either.
I am able to get into HBOOT and Stock recovery, so I know the phone is not bricked. I guess, I never had to deal with this situation before so I'm not sure how to get out of this loop. Is there a way I can get my phone to recognize on my computer, so that I can do the ADB / Fastboot commands?
Help!
PS: It might help to know what my device situation is atm. I have Unlocked bootloader with HBOOT 1.54, S-OFF
Have you tried to run the 4.3 or 4.4 RUU file from http://forum.xda-developers.com/showthread.php?t=2358781 ?
you have fastboot on your pc?
khhhhris said:
you have fastboot on your pc?
Click to expand...
Click to collapse
Yes.
SaHiLzZ said:
Have you tried to run the 4.3 or 4.4 RUU file from http://forum.xda-developers.com/showthread.php?t=2358781 ?
Click to expand...
Click to collapse
To do that, my phone would have to be recognized by the pc first, right? If I plug in via USB, and run adb devices I don't get any devices listed.
At what point should my phone be recognized by my laptop? The phone never goes to the main OS, so is there some way to get it to be recognized on my laptop USB while in HBOOT or Recovery? I have the stock recovery. The top of the recovery screen say s"Android system recovery <3e>"
I'm following along in http://forum.xda-developers.com/showthread.php?t=2544199 thread for now. A few things are similar. If I see anything different, I'll comment here again to see if anyone can help.
As you are S-Off, you can put the phone in fastboot mode, connect to computer and run the fastboot flash ruu twice.. either 4.3 or 4.4 RUU.
Update your covery twrp to v2.6.3.3 I updated after the looping problem and it worked, it installed with out the boot loops
Fastboot Flash the 4.3 boot.img
Then
Fastboot erase cache
Boot recovery
Wipe data
Flash 4.3 rom
SaHiLzZ said:
As you are S-Off, you can put the phone in fastboot mode, connect to computer and run the fastboot flash ruu twice.. either 4.3 or 4.4 RUU.
Click to expand...
Click to collapse
I got as far as flashing the RUU. I ran fastboot oem rebootRUU and then fastboot flash zip RUU-<more-stuff>.zip. The progress on my console shows the process completed successfully, but the phone is stuck at almost 99% on the progress bar. I'll wait for a while and see if it finishes. How long would be too long to wait?
drec70 said:
Update your covery twrp to v2.6.3.3 I updated after the looping problem and it worked, it installed with out the boot loops
Click to expand...
Click to collapse
I suppose I can go that route later on.
pull the plug and reboot manually..
backfromthestorm said:
Fastboot Flash the 4.3 boot.img
Then
Fastboot erase cache
Boot recovery
Wipe data
Flash 4.3 rom
Click to expand...
Click to collapse
Thanks for the help, but I guess I don't have to do this now. I'll keep this in mind in case I'm stuck again.
SaHiLzZ said:
pull the plug and reboot manually..
Click to expand...
Click to collapse
Haah! I should've followed through the complete instructions... I ended up giving the fastboot reboot and it started the boot. I couldn't reply sooner due to new-member 5-minute restriction.
Learned something good, something new today. And the phone WORKS! Thanks for your help.
Great news. Hit the thanks button if you dont mind! and keep the S-Off. that is your savior!
Cheers.
SaHiLzZ said:
Great news. Hit the thanks button if you dont mind! and keep the S-Off. that is your savior!
Cheers.
Click to expand...
Click to collapse
Aha! S-OFF shall stay intact Thanks.
Hello, I've been raking up the other xda posts all night and can't seem to find the right solution for my situation. Am a total noob so would really appreciate any instructions, whether to solve the problem or to point me to the right post. Quite lost here.
So, I've been trying to return my HTC one to stock (hk version; CID: HTC__622; modelid: PN0714000) and got into trouble. I used to have CM 10.2 with TWRP recovery. So I used TWRP to install what I thought was a stock ROM (not sure if I'm using the terms right) My current situation, in gist:
(1) Can only load into bootloader, if reboot normally then I get htc splash screen then black screen. -->Refuses to boot into the operating system!!!!!! All I get is the htc flash screen then the black screen until eternity (or I force reboot it by holding vol down and power button under strong light-- tip I got from these parts)
(2) Bootloader (top of) reads "tampered" (which I'm least concerned with) and "relocked"
(at one point it said "security warning" as well… but then that disappeared-- see below)
(3) I cannot use adb via either my Mac/ Windows, I have downloaded google SDK and updated HTC drivers on both machines-- adb devices command simply does not register my phone
(4) atm I am only communicating to my phone via fastboot commands… of which I know next to nth except what are commonly found in these forums…
(5) My machine is still S-off. Before my troubles, it was hboot 1.54, after messing around with it, it's now 1.55 if that makes any difference.
I desperate need my phone for the working week…. PLEASE HELP!!!
FYI: I'm on a Mac, but I do have access to a Windows machine running Windows 7
What I have done so far:-
(1) So I was trying to get back to stock, right? First thing I did was used HTC1guru's Guru reset. The ROM I installed was actually for the Asia WWE variant.
Anyway, so I installed it, and it worked, to the extent that I could get OTA notifications and downloaded the update. But HTC could not verify it and did not allow me to install the update. Because I wanted the Kitkat update, I looked up the net to see what could be the problem.
(2) The next mistake I made (probably a mistake) was to think that I had to relock the bootloader. So I did that. Now my Bootloader is relocked and I cannot, for the life of me unlock it again (I've tried going through the HTC dev steps and flashing the new Unlock_code.bin again but I can't unlock it)
At this point, the bootloader also read "security warning" under "relocked"
Subsequent to relocking it, I can't get into my operating system anymore. The only 2 outcomes I get on reboot are (1) HTC splash screen followed by black screen; OR (2) bootloader (if I do power + vol down)
(3) As one 'brilliant' idea followed another 'brilliant' idea, I also did the following list of silly and probably mistaken things our of sheer desperation. Throwing the kitchen sink in really. But none of them really worked because they all say sign not verified or sth to that effect-- I honestly am beginning to forget the order in which things unfolded… but if that's relevant, let me know and I'll try to recall more details.
(a) flash a recovery.img (stock, for both Asia WWE and HK version which I found on the web; and also TWRP)
(b) flash boot.img from Asia WWE
(c )tried rumrunner (can't do because adb won't work)
My latest attempt has been flash oem reboot RUU (then used zip of HK version 1.29.708 Rom zip)
and my phone is now stuck at the grey HTC on black background screen one gets after the first reboot RUU command (terminal has not prompted me to enter a second rebootRUU command yet!)
I don't know what to do. I don't even know if I should unplug the phone and redo the rebootRUU thing…
:crying: PLEASE HELP!!!!
FURTHER to the above
jaqzilch said:
...
My latest attempt has been flash oem reboot RUU (then used zip of HK version 1.29.708 Rom zip)
and my phone is now stuck at the grey HTC on black background screen one gets after the first reboot RUU command (terminal has not prompted me to enter a second rebootRUU command yet!)
I don't know what to do. I don't even know if I should unplug the phone and redo the rebootRUU thing…
:crying: PLEASE HELP!!!!
Click to expand...
Click to collapse
I've unplugged the phone, rebooted into bootloader, and made a second attempt to rebootRUU with HKvariant 1.29 zip… still gets stuck after 1st rebootRUU command (i.e. black screen with grey HTC logo)
Please do help,
jaqzilch said:
Hello, I've been raking up the other xda posts all night and can't seem to find the right solution for my situation. Am a total noob so would really appreciate any instructions, whether to solve the problem or to point me to the right post. Quite lost here.
So, I've been trying to return my HTC one to stock (hk version; CID: HTC__622; modelid: PN0714000) and got into trouble. I used to have CM 10.2 with TWRP recovery. So I used TWRP to install what I thought was a stock ROM (not sure if I'm using the terms right) My current situation, in gist:
(1) Can only load into bootloader, if reboot normally then I get htc splash screen then black screen. -->Refuses to boot into the operating system!!!!!! All I get is the htc flash screen then the black screen until eternity (or I force reboot it by holding vol down and power button under strong light-- tip I got from these parts)
(2) Bootloader (top of) reads "tampered" (which I'm least concerned with) and "relocked"
(at one point it said "security warning" as well… but then that disappeared-- see below)
(3) I cannot use adb via either my Mac/ Windows, I have downloaded google SDK and updated HTC drivers on both machines-- adb devices command simply does not register my phone
(4) atm I am only communicating to my phone via fastboot commands… of which I know next to nth except what are commonly found in these forums…
(5) My machine is still S-off. Before my troubles, it was hboot 1.54, after messing around with it, it's now 1.55 if that makes any difference.
I desperate need my phone for the working week…. PLEASE HELP!!!
FYI: I'm on a Mac, but I do have access to a Windows machine running Windows 7
What I have done so far:-
(1) So I was trying to get back to stock, right? First thing I did was used HTC1guru's Guru reset. The ROM I installed was actually for the Asia WWE variant.
Anyway, so I installed it, and it worked, to the extent that I could get OTA notifications and downloaded the update. But HTC could not verify it and did not allow me to install the update. Because I wanted the Kitkat update, I looked up the net to see what could be the problem.
(2) The next mistake I made (probably a mistake) was to think that I had to relock the bootloader. So I did that. Now my Bootloader is relocked and I cannot, for the life of me unlock it again (I've tried going through the HTC dev steps and flashing the new Unlock_code.bin again but I can't unlock it)
At this point, the bootloader also read "security warning" under "relocked"
Subsequent to relocking it, I can't get into my operating system anymore. The only 2 outcomes I get on reboot are (1) HTC splash screen followed by black screen; OR (2) bootloader (if I do power + vol down)
(3) As one 'brilliant' idea followed another 'brilliant' idea, I also did the following list of silly and probably mistaken things our of sheer desperation. Throwing the kitchen sink in really. But none of them really worked because they all say sign not verified or sth to that effect-- I honestly am beginning to forget the order in which things unfolded… but if that's relevant, let me know and I'll try to recall more details.
(a) flash a recovery.img (stock, for both Asia WWE and HK version which I found on the web; and also TWRP)
(b) flash boot.img from Asia WWE
(c )tried rumrunner (can't do because adb won't work)
My latest attempt has been flash oem reboot RUU (then used zip of HK version 1.29.708 Rom zip)
and my phone is now stuck at the grey HTC on black background screen one gets after the first reboot RUU command (terminal has not prompted me to enter a second rebootRUU command yet!)
I don't know what to do. I don't even know if I should unplug the phone and redo the rebootRUU thing…
:crying: PLEASE HELP!!!!
Click to expand...
Click to collapse
Ok...
First flash a recovery(use Case 2):
No Recovery? No Problem
Oh sh*t here we can have several kind of problems Still no problem But let's first download the recovery.
http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
(MD5 hash: 72067AEFB69541D40E8420D7AA46408D)
Case 1 - Normal error with unlocked and s off or s on:
Boot your phone into the fastboot mode
Eat a piece of cheese
Enter this command
Code:
fastboot erase cache
Followed by this command
Code:
fastboot flash recovery "C:\path_to_recovery\recovery_name.img"
And enter the recovery and follow the next piece of guide
Case 2 - For some stupid reason you are s off (that's a MUST) and Relocked:
Sorry, you need this recovery:
https://www.mediafire.com/?ni177radvko5xu7 (If it doesn't work, PM me)
(MD5 hash: F2893CDC17C788B2E49AECEA8C02DCB4)
Boot your awesome HTC One into fastboot
Change CID to superCID using this command (make sure you used 8 times a '1')
Code:
fastboot oem writecid 11111111
Enter this command
Code:
fastboot oem rebootRUU
Wait until your Pc recognized your phone again and enter this command
Code:
fastboot flash zip "C:\path_to_zip\firmware.zip"
(This may delete all your data)
Happy rebooting with this command
Code:
fastboot reboot-bootloader
Enter the recovery and let's unlock the bootloader...
You can unlock your bootloader using these commands(thanks @scotty1223 for your thread!):
[how to] lock/unlock your bootloader without htcdev(s-off required)
If this doesn't work in recovery because you get superSU or permission errors, use this tool here instead:
http://www.htc1guru.com/guides/guru-bootloader-reset/
You can simply push the ZIP file to your HTC One using one of these commands:
Code:
adb push "C:\path_to_zip\zip_name.zip" /sdcard/bootloader_reset.zip
If this one results in supersu and permission errors, try these paths(Thanks @Sneakyghost for this advice!)
Code:
adb push "C:\path_to_zip\zip_name.zip" /storage/emulated/0/bootloader_reset.zip
Code:
adb push "C:\path_to_zip\zip_name.zip" /data/media/0/bootloader_reset.zip
Case 3 - You totally ****ed up your recovery and data partition:
Right now, I am pretty busy and I don't have time to develop this, check this guide there and post your question there, but pls don't spam @mike1986.
How to: fix a corrupted DATA partition on the HTC One
now you are unlocked and s off... so what we're gonna do depends on what you want to achieve... I didn't really get what you meant in the first post.. you want to be again 100% stock on a Asian ROM ?
with the unlocked bootloader and s off and the custom recovery you are pretty much able to flash the rom you want to the device... how to do this:
http://forum.xda-developers.com/showthread.php?t=2632736
or:
Bootloop, No OS, Totally f*cked up OS? No Problem
THIS WILL DELETA ALL YOUR APPS AND APP DATA BUT NOT SDCARD!
First of all, make a factory reset in TWRP... then follow the next steps.
Now the key step here copying the rom.zip to your sdcard. You do this this way
Since you are in the recovery you should be able, no.. actually will be able to use adb commands
To copy the rom zip us this command:
Code:
adb push "C:\path_to_rom\rom_name.zip" /sdcard/rom.zip
If this one results in supersu and permission errors, try these paths(Thanks @Sneakyghost for this advice!)
Code:
adb push "C:\path_to_rom\rom_name.zip" /storage/emulated/0/rom.zip
Code:
adb push "C:\path_to_rom\rom_name.zip" /data/media/0/rom.zip
Now, in the recovery, choose install and select the rom you should've just copied and install/flash it.
After that make a factory reset, the standart when chosing wipe in TWRP.
Happy rebooting!
---------- Post added at 11:43 AM ---------- Previous post was at 11:39 AM ----------
jaqzilch said:
I've unplugged the phone, rebooted into bootloader, and made a second attempt to rebootRUU with HKvariant 1.29 zip… still gets stuck after 1st rebootRUU command (i.e. black screen with grey HTC logo)
Please do help,
Click to expand...
Click to collapse
ok, ok ok... wait with flashing RUUs... you'll mess up your phone if you continue flashing these RUUs
LibertyMarine said:
Ok...
First flash a recovery(use Case 2):
...
[/INDENT][/INDENT]
---------- Post added at 11:43 AM ---------- Previous post was at 11:39 AM ----------
ok, ok ok... wait with flashing RUUs... you'll mess up your phone if you continue flashing these RUUs
Click to expand...
Click to collapse
Hello, LibertyMarine, thanks for the response!
I've already downloaded TWRP recovery from the TWRP website, is the one you give me different?
Re: Case one-- I've actually tried flashing the TWRP recovery image before, but it doesn't seem to work. Thing is, I've idiotically relocked my HTC one now, so that might be the problem.
This is what I get when I try to flash TWRP recovery:-
fastboot flash recovery TWRPrecovery.img
target reported max download size of 1526722560 bytes
sending 'recovery' (9948 KB)...
OKAY [ 11.854s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 12.707s
as for unlocking my relocked bootloader, I've tried numerous times and I simply cannot get my relocked bootloader to unlock again. Whenever I put in the "fastboot flash unlocktoken Unlock_code.bin" (and yes, I've put the Unlock_code.bin into the same folder as fastboot and adb, the terminal gets stuck at "sending 'unlocktoken' (0 KB)…"
and nothing happens on my phone.
Re: Case two-- I'm one of those poor S-on folks so…
Re: Case 3-- looks like they need custom recovery flashed already… but (see Case one above), I can't seem to flash TWRP on my poor phone … : (
As to the last solution-- totally f-ed up OS etc…. again, I don't have TWRP… nor can I used adb
I'd be ever so grateful if I can just find a way to put twrp on my phone again! o gawd….
THanks again for all suggestions!!
jaqzilch said:
Hello, LibertyMarine, thanks for the response!
I've already downloaded TWRP recovery from the TWRP website, is the one you give me different?
Re: Case one-- I've actually tried flashing the TWRP recovery image before, but it doesn't seem to work. Thing is, I've idiotically relocked my HTC one now, so that might be the problem.
This is what I get when I try to flash TWRP recovery:-
fastboot flash recovery TWRPrecovery.img
target reported max download size of 1526722560 bytes
sending 'recovery' (9948 KB)...
OKAY [ 11.854s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 12.707s
Click to expand...
Click to collapse
yeah.. that's because you are locked ....
jaqzilch said:
as for unlocking my relocked bootloader, I've tried numerous times and I simply cannot get my relocked bootloader to unlock again. Whenever I put in the "fastboot flash unlocktoken Unlock_code.bin" (and yes, I've put the Unlock_code.bin into the same folder as fastboot and adb, the terminal gets stuck at "sending 'unlocktoken' (0 KB)…"
Click to expand...
Click to collapse
hmmm... have you tried redownloading/rerequesting a unlock token ?
try that... try requesting a new one and try flashing this one...
jaqzilch said:
and nothing happens on my phone.
Click to expand...
Click to collapse
haven't had such an issue.. I'll do some research on this topic..
jaqzilch said:
Re: Case two-- I'm one of those poor S-on folks so…
Click to expand...
Click to collapse
I don't know why.. I though you were s off... sorry... I must have commuted you with an other guy
jaqzilch said:
Re: Case 3-- looks like they need custom recovery flashed already… but (see Case one above), I can't seem to flash TWRP on my poor phone … : (
As to the last solution-- totally f-ed up OS etc…. again, I don't have TWRP… nor can I used adb
I'd be ever so grateful if I can just find a way to put twrp on my phone again! o gawd….
THanks again for all suggestions!!
Click to expand...
Click to collapse
Yeah... case 3 needs a custom recovery.. but you won't need that one anyways.. because your data partition seems to be OK
I'm on CM11 which has been working for weeks, last night my phone died completely and when I put it in the charger it wouldn’t light up no matter which outlet/cord I used. It reboots itself after a few seconds of being on, and so soon that I cant enter into recovery or select factory reset under recovery from bootloader because it selects recovery for me and then turns off. My Hboot is 1.44, S-on, its rooted as well. I have reached the edge of my competence, I'd really appreciate any and all help.
nicksperception said:
I'm on CM11 which has been working for weeks, last night my phone died completely and when I put it in the charger it wouldn’t light up no matter which outlet/cord I used. It reboots itself after a few seconds of being on, and so soon that I cant enter into recovery or select factory reset under recovery from bootloader because it selects recovery for me and then turns off. My Hboot is 1.44, S-on, its rooted as well. I have reached the edge of my competence, I'd really appreciate any and all help.
Click to expand...
Click to collapse
first try to re-flash your recovery to resolve
if not, you must flash stock ROM :
turn your phone on in bootloader mode or RUU mode (fastboot oem rebootRUU)
find your right RUU.exe from here > flash it
Note : you must flash the correct RUU that meet your CID & MID
if you can't know/find the correct RUU?, post your CID & MID
moha_moha20106 said:
first try to re-flash your recovery to resolve
if not, you must flash stock ROM :
turn your phone on in bootloader mode or RUU mode (fastboot oem rebootRUU)
find your right RUU.exe from> flash it
Note : you must flash the correct RUU that meet your CID & MID
if you can't know/find the correct RUU?, post your CID & MID
Click to expand...
Click to collapse
i dont know how to run adb commands when my phone wont turn on long enough to get registered by adb or the computer its on. it cant stay in bootloader for more than a few seconds, cant go into fastboot nor recovery. my radio is 4A 14.3250.13 and my phone is for AT&T, is that helpful?
it seems that there is nothing left to do with the phone. no fastboot, no recovery, no factory reset, no computer recognition. no adb/fastboot command gets the phone to be recognized. i have the latest htc drivers installed manually but when the computer recognizes there is a usb anything it tries to install the drivers but the phone quickly turns off and the driver installation fails. adb devices comes up empty, getvar cid keeps waiting for device forever, and trying to push files doesn’t work because it cant recognize it's there in the first place. is there anything I can do?
Here is the bootloader page I see if it helps.
nicksperception said:
Here is the bootloader page I see if it helps.
Click to expand...
Click to collapse
first, you must hit THANKS if anyone try to help you, or reply to help you
read this post if you need to learn more about ADB / Fastboot commands
Maybe my topic will help you (it's just one page back) http:// http://forum.xda-developers.com/showthread.php?t=2707187
detovenaar said:
Maybe my topic will help you (it's just one page back) http://forum.xda-developers.com/showthread.php?t=2707187
Click to expand...
Click to collapse
you link was broken
@nicksperception
try the link in my Quote above
detovenaar said:
Maybe my topic will help you (it's just one page back) http:// http://forum.xda-developers.com/showthread.php?t=2707187
Click to expand...
Click to collapse
I appreciate the help but I cant even get my phone to be recognized in fastboot or adb. It said "waiting for device" when i tried to get my cid for hours. It turns off too quickly for the computer to recognize it. Did you have this problem? If so how did you fix it?
Aight. I got me a Rooted, S-OFF HTC One rocking the most recent stock OS (can't remember which and my phone is jacked so I can't check) and twrp v2.6.3.0
Yesterday I reset my phone via the power button to clear the cache. I do this at least once a week because, well, it's a good idea right?
Wrong.
It went into a boot loop. It was weird. It would boot up and work for about 10 seconds, then reboot. Even if I caught it in time to fully shut off, it would do so. But if I went to HBoot or TWRP it wouldn't reboot. OK. Let's factory reset via TWRP, restore via Titanium, and all good.
That is until just now it flipped out after and is now in consta boot loop. Can't get into recovery, can't make it turn off, it just loads up and keeps telling me how Google Services have stopped working and then reboots again. I can get the power off function to come up but all it does is reboot again. Advice? Maybe I need to give you more info? I would have more for you but in the process of getting it off my phone to ask about the first occurrence yesterday is when it started flipping out just now.
Please, any advice at all would be fantastic.
Now I got it to stop boot looping, but my homescreen is nonexistent, can only go into stuff that is in the pull down task bar, no app tray, and the power off function still just reboots. And when it reboots, it doesn't even give me the splash pages. Just five seconds later it's back.
capn_tack said:
Now I got it to stop boot looping, but my homescreen is nonexistent, can only go into stuff that is in the pull down task bar, no app tray, and the power off function still just reboots. And when it reboots, it doesn't even give me the splash pages. Just five seconds later it's back.
Click to expand...
Click to collapse
can you please reboot in bootloader mode and post the output of ''fastboot getvar all'' (except imei/serialno) and also post a pic of bootloader screen.
btw your twrp version is outdated, latest version is 2.7.1.1.however we recommend using 2.6.3.3 or 2.6.3.4
with your phone s-off, you should consider restoring it with a fresh install using a ruu.
do you have files to backup or you are ok with loosing all data currently on your phone?
All right, I am new to rooting and s-off and all of this. First phone I've done it to, so forgive me if I ask stupid question...
alray said:
can you please reboot in bootloader mode and post the output of ''fastboot getvar all'' (except imei/serialno) and also post a pic of bootloader screen.
Click to expand...
Click to collapse
What does that mean? If by bootloader you mean when you press Vol Dwn and Pwr to get the screen that I've posted an image of...then I don't have anything there about getvar all.
How would RUU work?
And I've yet to figure out how to update TWRP, tho I haven't looked that one up yet. I am sure I could figure it out just fine. I've got this far, lol.
I fact reset my phone again, and it is working...for now. But I don't trust it to not freak out a third time. Am backing up all files to my PC as we speak.
capn_tack said:
What does that mean? If by bootloader you mean when you press Vol Dwn and Pwr to get the screen that I've posted an image of...then I don't have anything there about getvar all.
Click to expand...
Click to collapse
You need adb and fastboot installed on your computer + htc drivers
then use fastboot to do this command when phone is in bootloader:
Code:
fastboot getvar all
How would RUU work?
Click to expand...
Click to collapse
ruu restore the entire phone to stock, including software and firmware. this wipe all your data. with s-on you can only flash ruu same of higher version currently on your phone (i.e 4.18.502.7) with bootloader locked or re-locked. with s-off you can flash ruu lower or higher version, with bootloader unlocked, locked or re-locked.
And I've yet to figure out how to update TWRP, tho I haven't looked that one up yet. I am sure I could figure it out just fine. I've got this far, lol.
Click to expand...
Click to collapse
you also need fastboot to update twrp, however if you choose to restore using a ruu, no need to update twrp, it will be wiped by the ruu anyway.
I fact reset my phone again, and it is working...for now. But I don't trust it to not freak out a third time. Am backing up all files to my PC as we speak.
Click to expand...
Click to collapse
you should also try this using fastboot in bootloader:
Code:
fastboot erase cache
fastboot reboot
well you said in your first post that your phone was S-OFF but from what I see from the picture you have posted (yes this is the bootloader btw) your phone is S-ON. fortunately, there is a 4.18.502.7 ruu, so you should not need s-off.
oh and you also said you were running the most recent stock rom, but 4.18.502.7 isnt the most recent. most recent version for your phone is 5.12.502.2
Aight. I got me a Rooted, S-OFF HTC One rocking the most recent stock OS
Click to expand...
Click to collapse
Aight, I will get started on this when I get home from work. Thank you for the advice. I may be back with more questions.
Oh, why do you recommend those particular versions of TWRP over the newest?
-Tack