Related
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.
I browsed a few other threads, and tried to update the recovery with the latest version per the advice of a member, and prior to this, it was just stuck at the green HTC screen with the red disclaimer under it. And after flashing the newest recovery TWRP it has begun to loop.
I also cannot boot into recovery now. Only fastboot is working,.
Phone info is:
***UNLOCKED****
VLE PVT SHIP S-OFF RL
CID - 11111111
HBOOT- 1.14.0005
RADIO - 1.13.50.05.25
OPENDSP-V29.1.0.45.0622
EMMC-BOOT
NOV 21, 2012, 12:17:41
I believe everything is set for the Maximus ROM to work, but if I am missing something I would appreciate the feedback and help.
Thanks
Tancred
Tancred213 said:
I browsed a few other threads, and tried to update the recovery with the latest version per the advice of a member, and prior to this, it was just stuck at the green HTC screen with the red disclaimer under it. And after flashing the newest recovery TWRP it has begun to loop.
I also cannot boot into recovery now. Only fastboot is working,.
Phone info is:
***UNLOCKED****
VLE PVT SHIP S-OFF RL
CID - 11111111
HBOOT- 1.14.0005
RADIO - 1.13.50.05.25
OPENDSP-V29.1.0.45.0622
EMMC-BOOT
NOV 21, 2012, 12:17:41
I believe everything is set for the Maximus ROM to work, but if I am missing something I would appreciate the feedback and help.
Thanks
Tancred
Click to expand...
Click to collapse
This is HTC ONE forum not ONE S , you can try with RUU.exe while you're in bootloader or " fastboot oem rebootRUU "
Vixa said:
This is HTC ONE forum not ONE S , you can try with RUU.exe while you're in bootloader or " fastboot oem rebootRUU "
Click to expand...
Click to collapse
My bad, I was following posts about this ROM and assumed they were discussing the same phone. But it appears that there isn't a S thread, only an X for this model..
This takes me to a silver HTC logo and hangs there... I have fastboot access, but i cant get ADB to talk to the phone. But with fastboot I can push a new recovery img but still not allowing me into any recovery.
If you cant get into recovery donwload a RUU and get your phone flashed with it from FASTBOOT.
Vixa said:
If you cant get into recovery donwload a RUU and get your phone flashed with it from FASTBOOT.
Click to expand...
Click to collapse
Able to get into Philz recovery and adb sideload zips, but it cant find my sdcard...what a headache this is turning into, and no closer to knowing what the problem was / is.
Tell me can you mount system or get in twrp or something to hold on?
Sent from my HTC One using Tapatalk
Vixa said:
Tell me can you mount system or get in twrp or something to hold on?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Changed TWRP to CWM which is at least allowing me into recovery mode.
Thinking I will have to transfer the files with another android phone onto the memory and try to install the rom again?
Mounting USB fails, it just makes a sound like I have added a drive to my PC non stop every few seconds, and I cant mount anything. formatted it and it seems to have settled it a bit. But I cant do anything with the storage via USB in Windows. Just updated to the latest clockwork for my model and still no success...
With latest version I cant even sideload at the moment.
Tancred213 said:
Changed TWRP to CWM which is at least allowing me into recovery mode.
Thinking I will have to transfer the files with another android phone onto the memory and try to install the rom again?
Mounting USB fails, it just makes a sound like I have added a drive to my PC non stop every few seconds, and I cant mount anything. formatted it and it seems to have settled it a bit. But I cant do anything with the storage via USB in Windows. Just updated to the latest clockwork for my model and still no success...
With latest version I cant even sideload at the moment.
Click to expand...
Click to collapse
Ok, sorted that out, apparently the drivers were having issues, and when I manually picked them I became able to communicate with the phone again like normal. This is like hour 8 of the upgrade so far...
Assuming my firmware is also outdated, and from my searching I havent found an easy way to update my hboot and others without flashing a RUU Rom from T-Mobile, any alternatives to doing that?
Pretty sure I killed it. Downloaded the latest RUU from T-Mobile, after relocking the bootloader and turning S-on, it ran fine, completed, rebooted the phone and now its totally dead. No charge light, doesnt turn on at all. And I was just thinking to myself how hard it is to brick a phone since I have yet to kill one with all of my misadventures....oops. We'll see what happens..
Had you read the HTC One S forum, you would have found out that this particular phone can get hard bricked up S-OFF with SuperCID and then a RUU update is ran.
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
Hello!
Yesterday I decided to try flashing a new rom to my HTC One, hoping to increase battery life. The rom I tried flashing was a google edition 4.4.4 rom, if that matters. My previous rom was Android Revolution HD 71.1, and I'm pretty sure that I wiped both cache and delvik cache before flashing GE.
However, now my phone is stuck in a boot loop. I've been searching and failing for hours, hoping not to have to create another thread, but I'm now completely at a loss.
Details:
adb doesn't find my phone in the bootloader, but it does in recovery and sideload
Some commands, such as 'adb usb' return 'error: closed'
I managed to sideload my last working rom, ARHD 71.1, but after flashing it, I'm still stuck in a boot loop
I have two back-ups, one from before flashing the rom altogether, and one from after I got the boot loop (I made it since it was my first time wiping the system partition and I was unsure whether this meant I'd lose my pictures etc. or not). Restoring any of these back-ups still leaves boot looped.
I really really REALLY don't want to lose my pictures, but if formating is the only solution, will my back-ups (that only exist on my phone) be spared? I want to try to pull the files from my phone through adb, but as I mentioned earlier, it only returns 'error: closed'
I've got TWRP v2.6.3.3 and I haven't tinkered with my phone in a long time, so I'm really rusty. For instance I don't remember how to replace my recovery, if I for some reason need to do this.
Code:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PBT SHIP S-OFF RH
CID-HTC__Y13
HBOOT-1.54.0000
RADIO-4A.17.3250.14
OS-
eMMC-boot 2048MB
Aug 9 2013, 16:15:36.0
If any more information is needed, don't hesitate asking, I'll be watching this thread like a hawk.
Thank you very much in advance!!
gorek2711 said:
Hello!
Yesterday I decided to try flashing a new rom to my HTC One, hoping to increase battery life. The rom I tried flashing was a google edition 4.4.4 rom, if that matters. My previous rom was Android Revolution HD 71.1, and I'm pretty sure that I wiped both cache and delvik cache before flashing GE.
However, now my phone is stuck in a boot loop. I've been searching and failing for hours, hoping not to have to create another thread, but I'm now completely at a loss.
Details:
adb doesn't find my phone in the bootloader, but it does in recovery and sideload
Some commands, such as 'adb usb' return 'error: closed'
I managed to sideload my last working rom, ARHD 71.1, but after flashing it, I'm still stuck in a boot loop
I have two back-ups, one from before flashing the rom altogether, and one from after I got the boot loop (I made it since it was my first time wiping the system partition and I was unsure whether this meant I'd lose my pictures etc. or not). Restoring any of these back-ups still leaves boot looped.
I really really REALLY don't want to lose my pictures, but if formating is the only solution, will my back-ups (that only exist on my phone) be spared? I want to try to pull the files from my phone through adb, but as I mentioned earlier, it only returns 'error: closed'
I've got TWRP v2.6.3.3 and I haven't tinkered with my phone in a long time, so I'm really rusty. For instance I don't remember how to replace my recovery, if I for some reason need to do this.
Code:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PBT SHIP S-OFF RH
CID-HTC__Y13
HBOOT-1.54.0000
RADIO-4A.17.3250.14
OS-
eMMC-boot 2048MB
Aug 9 2013, 16:15:36.0
If any more information is needed, don't hesitate asking, I'll be watching this thread like a hawk.
Thank you very much in advance!!
Click to expand...
Click to collapse
If you successfully side loaded AHRD onto your phone, then you probably need to flash a new boot.img. The command is fastboot flash boot boot.img. If you have copy of your current firmware, you can extract it from the zip.
Here is a guide for how to setup and use fastboot. ADB commands do not work in bootloader, fastboot commands work in bootloader. ADB commands work in recovery. Since you are able to hook up to a computer, you can copy your personal files off the phone and place them on the computer.
adb commands only work inside recovery or inside a working rom, fastboot commands are for in the bootloader.
Before you flashed the GPE rom, did you change your CID and MID first ? this is a requirement, you are S-OFF so the issue isn't there.
I suggest for now to get things working properly again, you just run the stock RUU, or you can try and restore your first backup, wiping system will not delete your photo's etc, however format data will, and if you go into advanced wipe, you can select the areasyou want to wipe, just don't select internal storage.
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
if you want to backup your pictures etc, just use the adb pull command from within recovery main screen
Code:
adb pull /sdcard/
will pull the entire contents of you sdcard to your adb folder
gorek2711 said:
Hello!
Yesterday I decided to try flashing a new rom to my HTC One, hoping to increase battery life. The rom I tried flashing was a google edition 4.4.4 rom, if that matters. My previous rom was Android Revolution HD 71.1, and I'm pretty sure that I wiped both cache and delvik cache before flashing GE.
However, now my phone is stuck in a boot loop. I've been searching and failing for hours, hoping not to have to create another thread, but I'm now completely at a loss.
Details:
adb doesn't find my phone in the bootloader, but it does in recovery and sideload
Some commands, such as 'adb usb' return 'error: closed'
I managed to sideload my last working rom, ARHD 71.1, but after flashing it, I'm still stuck in a boot loop
I have two back-ups, one from before flashing the rom altogether, and one from after I got the boot loop (I made it since it was my first time wiping the system partition and I was unsure whether this meant I'd lose my pictures etc. or not). Restoring any of these back-ups still leaves boot looped.
I really really REALLY don't want to lose my pictures, but if formating is the only solution, will my back-ups (that only exist on my phone) be spared? I want to try to pull the files from my phone through adb, but as I mentioned earlier, it only returns 'error: closed'
I've got TWRP v2.6.3.3 and I haven't tinkered with my phone in a long time, so I'm really rusty. For instance I don't remember how to replace my recovery, if I for some reason need to do this.
Code:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PBT SHIP S-OFF RH
CID-HTC__Y13
HBOOT-1.54.0000
RADIO-4A.17.3250.14
OS-
eMMC-boot 2048MB
Aug 9 2013, 16:15:36.0
If any more information is needed, don't hesitate asking, I'll be watching this thread like a hawk.
Thank you very much in advance!!
Click to expand...
Click to collapse
This happened to me when i tried to install cm rom via cm installer, It solved by installing new recovery and arhd rom.
I can now use the adb commands in the bootloader too. I think I updated my drivers to do this.
aladdin32 said:
This happened to me when i tried to install cm rom via cm installer, It solved by installing new recovery and arhd rom.
Click to expand...
Click to collapse
I flashed the newest version of TWRP (2.7.1.1) and tried re-installing ARHD first, then I tried restoring my back-up from when it was working, neither of these made any difference.
Seanie280672 said:
adb commands only work inside recovery or inside a working rom, fastboot commands are for in the bootloader.
Before you flashed the GPE rom, did you change your CID and MID first ? this is a requirement, you are S-OFF so the issue isn't there.
I suggest for now to get things working properly again, you just run the stock RUU, or you can try and restore your first backup, wiping system will not delete your photo's etc, however format data will, and if you go into advanced wipe, you can select the areasyou want to wipe, just don't select internal storage.
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
if you want to backup your pictures etc, just use the adb pull command from within recovery main screen
Code:
adb pull /sdcard/
will pull the entire contents of you sdcard to your adb folder
Click to expand...
Click to collapse
I didn't change my CID or MID, I don't even know what these are :$
Restoring the back-ups never works, so I guess RUU is my only option now then. If I've understood it correctly, RUU basically returns my phone back to stock, correct? So I could do the RUU thing, then unlock the bootloader and flash TWRP again(?) then restore my ARHD back-up again? I have my dogecoin wallet, b-net authenticator, bank stuff, etc. there and it would be such a hassle switching them.
Would that work, or is there anything I'm missing? Like S-off first or something?
Also, would RUU delete my personal data? Such as images, back-ups, apps, etc.
I did manage to pull the images out though, so yay! However, there's a folder where I get an error saying that the directory doesn't exist. I think the problem might be the fact there's a space after (or before, I forget) the directory name. Is there any way to solve this? It's not a very big deal, but it would be nice to keep them. I'm thinking maybe I can change the name of the directory through adb/fastboot(is there a difference between the two? Or are they basically the same thing?) or something?
majmoz said:
If you successfully side loaded AHRD onto your phone, then you probably need to flash a new boot.img. The command is fastboot flash boot boot.img. If you have copy of your current firmware, you can extract it from the zip.
Here is a guide for how to setup and use fastboot. ADB commands do not work in bootloader, fastboot commands work in bootloader. ADB commands work in recovery. Since you are able to hook up to a computer, you can copy your personal files off the phone and place them on the computer.
Click to expand...
Click to collapse
After aladdin's tip failed (re-flashing recovery), I tried flashing the boot.img too, but this didn't change anything. I used the boot.img I found in the ARHD 71.1 .zip, not sure if that meant? Also, what do you mean by firmware?
EDIT: Scratch that first part about me now being able to use adb in the bootloader. I'm now having issues using it anywhere again. I'm reinstalling drivers like crazy. When I use the 'adb devices' command, it says something along the lines of 'list of connected devices:', but it doesn't list any. Then when I try to do a command, such as 'adb pull', it says no device is found, but when I do some 'fastboot getvar' command, it works. I also tried doing the RUU and it didn't work, something about wrong version? I'm not sure, my computer screen is really messed up so I can only see one half in very unclear colours, making text hard to read..
gorek2711 said:
I can now use the adb commands in the bootloader too. I think I updated my drivers to do this.
I flashed the newest version of TWRP (2.7.1.1) and tried re-installing ARHD first, then I tried restoring my back-up from when it was working, neither of these made any difference.
I didn't change my CID or MID, I don't even know what these are :$
Restoring the back-ups never works, so I guess RUU is my only option now then. If I've understood it correctly, RUU basically returns my phone back to stock, correct? So I could do the RUU thing, then unlock the bootloader and flash TWRP again(?) then restore my ARHD back-up again? I have my dogecoin wallet, b-net authenticator, bank stuff, etc. there and it would be such a hassle switching them.
Would that work, or is there anything I'm missing? Like S-off first or something?
Also, would RUU delete my personal data? Such as images, back-ups, apps, etc.
I did manage to pull the images out though, so yay! However, there's a folder where I get an error saying that the directory doesn't exist. I think the problem might be the fact there's a space after (or before, I forget) the directory name. Is there any way to solve this? It's not a very big deal, but it would be nice to keep them. I'm thinking maybe I can change the name of the directory through adb/fastboot(is there a difference between the two? Or are they basically the same thing?) or something?
After aladdin's tip failed (re-flashing recovery), I tried flashing the boot.img too, but this didn't change anything. I used the boot.img I found in the ARHD 71.1 .zip, not sure if that meant? Also, what do you mean by firmware?
EDIT: Scratch that first part about me now being able to use adb in the bootloader. I'm now having issues using it anywhere again. I'm reinstalling drivers like crazy. When I use the 'adb devices' command, it says something along the lines of 'list of connected devices:', but it doesn't list any. Then when I try to do a command, such as 'adb pull', it says no device is found, but when I do some 'fastboot getvar' command, it works. I also tried doing the RUU and it didn't work, something about wrong version? I'm not sure, my computer screen is really messed up so I can only see one half in very unclear colours, making text hard to read..
Click to expand...
Click to collapse
Did you try to/ can you restore a stock nandroid backup in twrp?
aladdin32 said:
Did you try to/ can you restore a stock nandroid backup in twrp?
Click to expand...
Click to collapse
Is that the same as the factory reset option? If so, then yes. If it's the format data option, then no. If it's something completely different, probably not... :<
gorek2711 said:
Is that the same as the factory reset option? If so, then yes. If it's the format data option, then no. If it's something completely different, probably not... :<
Click to expand...
Click to collapse
if you format data you will erase the entire contents of your phone including sd card.
yes RUU will totally wipe your phone and restore it back to stock, however, you are already s-off and will remain s-off unless you change it yourself. (NOT ADVISED) once your s-off, never go s-on, if you go s-on then you cant run that RUU, then your totally screwed.
If your ever going to flash a google edition rom again, read the instructions first, it wont work without a CID and MID change, there are guides to do that.
if you want to save the entire contects of your sdcard, use the pull command I said above, as nothing will be left after the RUU, it will be like the first day you got it.
your problem could be the version of TWRP you are using, recommended is 2.6.3.3 ive had problem with all of the 2.7++ versions I have used.
Seanie280672 said:
if you format data you will erase the entire contents of your phone including sd card.
yes RUU will totally wipe your phone and restore it back to stock, however, you are already s-off and will remain s-off unless you change it yourself. (NOT ADVISED) once your s-off, never go s-on, if you go s-on then you cant run that RUU, then your totally screwed.
If your ever going to flash a google edition rom again, read the instructions first, it wont work without a CID and MID change, there are guides to do that.
if you want to save the entire contects of your sdcard, use the pull command I said above, as nothing will be left after the RUU, it will be like the first day you got it.
your problem could be the version of TWRP you are using, recommended is 2.6.3.3 ive had problem with all of the 2.7++ versions I have used.
Click to expand...
Click to collapse
Trouble is though, whenever I use the command: 'adb pull /sdcard/TWRP/BACKUPS' (which is the only one I actually need now), I only get 'error: device not found.' again. I don't know what went wrong.. I'm in the start screen of the recovery. It didn't work in 2.6.3.3, and it doesn't work in 2.7 either. I've re-installed the usb drivers several times, and tried a couple as well. About that, do I need HTC Sync Manager? Or does it somehow conflict with the adb thingy?
Aaaaaand, I also kind of sort of did a big bad and locked my bootloader again, because I was meaning to do the RUU once more and forgot you have to wipe everything when you unlock it again... ooops. I'm assuming RUU will still work, but does this mean I will no longer be able to use the adb commands? Or would adb pull still work, if I only could get it to work?
ADB issue details:
In the bootloader, 'fastboot devices' shows me the device, and I can (well could, before I locked it again >.<) flash recoveries and boot.img, reboot through adb etc. etc.
When I'm on the home screen of the recovery, 'adb devices' has no entries in the list of connected devices. However, 'adb getvar cid' returns my cid. 'adb pull ...' along with other commands give me 'error: device not found'.
The adb commands mentioned above do not work in sideload mode either.
In device manager, my One shows up under "Other devices". Before it used to be under "Android devices", or something. I'm running Windows 7 Ultimate 32-bit.
P.S: If any of you feel like telling me why exactly GE roms need a change or CID and MID, that would be swell c:
gorek2711 said:
Trouble is though, whenever I use the command: 'adb pull /sdcard/TWRP/BACKUPS' (which is the only one I actually need now), I only get 'error: device not found.' again. I don't know what went wrong.. I'm in the start screen of the recovery. It didn't work in 2.6.3.3, and it doesn't work in 2.7 either. I've re-installed the usb drivers several times, and tried a couple as well. About that, do I need HTC Sync Manager? Or does it somehow conflict with the adb thingy?
Aaaaaand, I also kind of sort of did a big bad and locked my bootloader again, because I was meaning to do the RUU once more and forgot you have to wipe everything when you unlock it again... ooops. I'm assuming RUU will still work, but does this mean I will no longer be able to use the adb commands? Or would adb pull still work, if I only could get it to work?
ADB issue details:
In the bootloader, 'fastboot devices' shows me the device, and I can (well could, before I locked it again >.<) flash recoveries and boot.img, reboot through adb etc. etc.
When I'm on the home screen of the recovery, 'adb devices' has no entries in the list of connected devices. However, 'adb getvar cid' returns my cid. 'adb pull ...' along with other commands give me 'error: device not found'.
The adb commands mentioned above do not work in sideload mode either.
In device manager, my One shows up under "Other devices". Before it used to be under "Android devices", or something. I'm running Windows 7 Ultimate 32-bit.
P.S: If any of you feel like telling me why exactly GE roms need a change or CID and MID, that would be swell c:
Click to expand...
Click to collapse
Try updating your adb and fastboot, sounds out of date to me, use this: http://forum.xda-developers.com/showthread.php?t=2317790
easily unlock, relock, lock your bootloader WITHOUT HTCDev: http://forum.xda-developers.com/showthread.php?t=2475914
Google Edition ROM explination: http://forum.xda-developers.com/showthread.php?t=2358781
gorek2711 said:
[*]When I'm on the home screen of the recovery, 'adb devices' has no entries in the list of connected devices. However, 'adb getvar cid' returns my cid. 'adb pull ...' along with other commands give me 'error: device not found'.:
Click to expand...
Click to collapse
This is the issue I was having with TWRP 2.7.1.1, which is why I said use 2.6.3.3, that worked for me.
Seanie280672 said:
Try updating your adb and fastboot, sounds out of date to me, use this: http://forum.xda-developers.com/showthread.php?t=2317790
easily unlock, relock, lock your bootloader WITHOUT HTCDev: http://forum.xda-developers.com/showthread.php?t=2475914
Google Edition ROM explination: http://forum.xda-developers.com/showthread.php?t=2358781
This is the issue I was having with TWRP 2.7.1.1, which is why I said use 2.6.3.3, that worked for me.
Click to expand...
Click to collapse
I'm now using the adb you recommended. In fastboot, everything works as expected. I uninstalled all the drivers I'd installed previously and only installed and updated HTC Sync Manager, since I read that once I have this the drivers will install automagically the first time I connect the phone.
In fastboot, the driver installation works, and commands work fine as well, I just can't return to 2.6.3.3 since my bootloader is locked.
In the recovery, the driver installation said it didn't find any drivers (guess they don't use the same drivers in fastboot and recovery(?)), and the adb commands don't work.
I'm not 100% sure, but I seem to recall having a familiar problem with the 2.6.3.3 version. Maybe.
I don't know. All the guides I find assume that I can actually get into the OS and activate USB debugging and stuff. Could that have something to do with it? Or is that and recovery start screen basically equal?
Thank you all for the help by the way! At least I've got my pictures, so I'm kinda halfway to doing a RUU without a care thanks to yous.
EDIT: Aha! Fixed the driver issue! I went into device manager, right clicked the 'One' entry, which was under other devices and chose the newest version of the HTC One drivers I had installed. Guess my computer just didn't realize it was my One that was plugged in and needed a little help
Right now I'm pulling the back-ups and after I will try to do the RUU thang. Thanks guys!
EDIT 2: Okay, I got my back-ups, but I cannot get the RUU to work. Apparently I no longer have an OS. Here's a screenshot showing the 'from image: to image:" thingy. I'm sorry it's in Norwegian.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried again and it's been stuck at step 1, controlling something for over an hour. The progress bar has been showing 5% all along. Could HTC Sync Manager interfere with this in any way?
*facepalm*
Finally checked what rom I actually flashed, and it seems that in my excitement I didn't even bother checking what device the rom was for...
Turns out I flashed a rom meant for the Samsung Galaxy 3... Does this help in any way in regards to finding a way to fix it again? XD
I fixed it!!!
All I had to do was to flash my firmware back, because that had somehow gone :3
I used the corresponding firmware to the RUU version I was recommended to download back on page one.
This did not end the boot loop though, so I had to do the RUU after all, but at least it works now!
Now I'm going to unlock the bootloader again, flash TWRP recovery and restore my old back-up.
Thank you again everyone! You've been really helpful!
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?