[Q] HTC One Bootloop - Cannot unlock bootloader - One (M7) Q&A, Help & Troubleshooting

Hi All,
My phone suddenly started doing a Bootloop, please notice that I haven't messed up with any custom ROMs, flashing, etc... the only thing that I may guess that happened here is that my phone got a little wet a couple of days ago. The screen won't came up so I dry it using a hairdryer and started working normally. Two days later I got an error that Foursquare app was failing and then I got into the Bootloop that I cannot get rid of....
I'm totally new with flashing phones, rooting, unlocking, etc... but I'm a developer, so, I can learn much easily.
I was reading some forums and solutions but I could not get it work.
Here are the details:
1- The phone is a HTC One M7
2- I'm able to enter to "Recovery mode" screen
3- If i scroll down to "Recovery" or "Factory Reset" the phone try to enter to those modes but after a few seconds of black screen I got an image with a phone with a red warning icon inside. So, I cannot enter to recovery nor do a factory reset
4- If I try to use "adb" commands looks like the bootloop is avoiding me to recognize the device. I tried "adb devices" several times while the phone is rebooting and I see the phone appearing in the list in the middle of the reboot but the status is "offline", then, it changed to "unauthorized" and then it disappears. I also tried "adb wait-for-device" but does not worked and sometimes it said that there is more than one device connected (if i tried adb devices again, appear my device a lot of times but always offline).
I also tried a .bat file to wait for the device and do a shell stop to be able to "freeze" where the phone is accessible, but did not worked neither.
I guess that I don't have debugging enable on my device and that is why i cannot use the adb commands of see the phone connected. I saw that adb will work even with debugging disabled in recovery, but like i mentioned before, i cannot enter to recovery.
5- I was able to enter to "fastboot mode" and my phone connected to USB. If i use fastboot devices, my device appears and looks fine.
6- I tried to unlock the bootloader using the htcdev.com. I followed the steps and looks simple, I don't think i messed something there. I was able to get the phone token, submit, get the Unlock_code.bin, flash the code using fastboot, I got the screen to select yes/no to unlock the bootloader, and at this point everything looks great. I selected Yes, and my phone reboot and still on bootloop (as expected), but If i enter again to recovery mode, the phone is still "*** LOCKED ***". I tried the process (get toke, submit, flash bin, etc) lot of times, but with no result, phone is still appears as Locked.
7- My idea on #6 was to flash the recovery img and try to make the recovery to work, but to be able to flash the recovery i need my bootloader to be unlocked. I tried anyways to flash the recovery but as expected if failed :
C:\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot flash recovery openrecovery-twrp-2.7.1.1-m7.img
target reported max download size of 1514139648 bytes
sending 'recovery' (9434 KB)...
OKAY [ 1.201s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.172s
8- I saw that there is another method to unlock the bootloader but is using adb, which on #4 i explained i cannot use.
Any idea? thoughts?
Thanks in advance,
Juan.

first USB debugging is only for when you are booted into a rom, it doesn't apply to recovery or bootloader.
Red triangle with exclamation mark is normal, that's the stock recovery.
next, you wont beable to adb devices whilst its bootlooping, that's why that's not working, adb is for in a rom or in recovery, fastboot commands are for when your in the bootloader
So reboot your phone to bootloader mode, this is where you saw the list with options to factory reset and reboot and recovery etc, this is the only thing you need to use for now, and only fastboot commands will work there, once plugged into your computer it should say on the screen "fastboot USB"
post your "fastboot getvar all" without quote marks

Seanie280672 said:
first USB debugging is only for when you are booted into a rom, it doesn't apply to recovery or bootloader.
Red triangle with exclamation mark is normal, that's the stock recovery.
next, you wont beable to adb devices whilst its bootlooping, that's why that's not working, adb is for in a rom or in recovery, fastboot commands are for when your in the bootloader
So reboot your phone to bootloader mode, this is where you saw the list with options to factory reset and reboot and recovery etc, this is the only thing you need to use for now, and only fastboot commands will work there, once plugged into your computer it should say on the screen "fastboot USB"
post your "fastboot getvar all" without quote marks
Click to expand...
Click to collapse
Hi Seanie, thanks for the quick response.
Here is the result of fastboot getvar all command:
C:\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.1540.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3451mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.044s
Click to expand...
Click to collapse
J.

first thing is first, remove your serial number and imei from your output, its dangerous to post them.
also get your battery charged up to 50% or more,

Seanie280672 said:
first thing is first, remove your serial number and imei from your output, its dangerous to post them.
also get your battery charged up to 50% or more,
Click to expand...
Click to collapse
Ohh, just removed.
About battery, I cannot turn off my phone (even if trying from fastboot "power off" option), that is why i keep it with low battery so it power off when it's empty.
Do you thing battery level will change my results? If yes, after charging my batter, what i should do?
Thanks,
J.

htc butterfly a 9060 bootloop
I also have something that type of problem what u said ....
By missing i delete some some files from system/bin. And after that my phone boot loop ....nothing is working..... my bootloader is working but is locked .asb not working ..fastboot working ......i have recovery and boot.img.....can can one help ....plzz ..i m crying.....its really big mistake...:crying:

Htc butterfly s 9060 bootloop
garyplaton said:
Hi All,
My phone suddenly started doing a Bootloop, please notice that I haven't messed up with any custom ROMs, flashing, etc... the only thing that I may guess that happened here is that my phone got a little wet a couple of days ago. The screen won't came up so I dry it using a hairdryer and started working normally. Two days later I got an error that Foursquare app was failing and then I got into the Bootloop that I cannot get rid of....
I'm totally new with flashing phones, rooting, unlocking, etc... but I'm a developer, so, I can learn much easily.
I was reading some forums and solutions but I could not get it work.
Here are the details:
1- The phone is a HTC One M7
2- I'm able to enter to "Recovery mode" screen
3- If i scroll down to "Recovery" or "Factory Reset" the phone try to enter to those modes but after a few seconds of black screen I got an image with a phone with a red warning icon inside. So, I cannot enter to recovery nor do a factory reset
4- If I try to use "adb" commands looks like the bootloop is avoiding me to recognize the device. I tried "adb devices" several times while the phone is rebooting and I see the phone appearing in the list in the middle of the reboot but the status is "offline", then, it changed to "unauthorized" and then it disappears. I also tried "adb wait-for-device" but does not worked and sometimes it said that there is more than one device connected (if i tried adb devices again, appear my device a lot of times but always offline).
I also tried a .bat file to wait for the device and do a shell stop to be able to "freeze" where the phone is accessible, but did not worked neither.
I guess that I don't have debugging enable on my device and that is why i cannot use the adb commands of see the phone connected. I saw that adb will work even with debugging disabled in recovery, but like i mentioned before, i cannot enter to recovery.
5- I was able to enter to "fastboot mode" and my phone connected to USB. If i use fastboot devices, my device appears and looks fine.
6- I tried to unlock the bootloader using the htcdev.com. I followed the steps and looks simple, I don't think i messed something there. I was able to get the phone token, submit, get the Unlock_code.bin, flash the code using fastboot, I got the screen to select yes/no to unlock the bootloader, and at this point everything looks great. I selected Yes, and my phone reboot and still on bootloop (as expected), but If i enter again to recovery mode, the phone is still "*** LOCKED ***". I tried the process (get toke, submit, flash bin, etc) lot of times, but with no result, phone is still appears as Locked.
7- My idea on #6 was to flash the recovery img and try to make the recovery to work, but to be able to flash the recovery i need my bootloader to be unlocked. I tried anyways to flash the recovery but as expected if failed :
C:\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot flash recovery openrecovery-twrp-2.7.1.1-m7.img
target reported max download size of 1514139648 bytes
sending 'recovery' (9434 KB)...
OKAY [ 1.201s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.172s
8- I saw that there is another method to unlock the bootloader but is using adb, which on #4 i explained i cannot use.
Any idea? thoughts?
Thanks in advance,
Juan.
Click to expand...
Click to collapse
i also have all these problem what u have with your phone..can u please tell is your problem solved or not if yes so please share with i m crying right now with this..please help

abby1996 said:
i also have all these problem what u have with your phone..can u please tell is your problem solved or not if yes so please share with i m crying right now with this..please help
Click to expand...
Click to collapse
Hi, after trying everything that I found in the forums, google, etc, without been able to work around it, I took my phone to two places where they fix cell phones but both of them told me "it can't be fixed". So, I lost my hope and currently i'm still keeping the broken phone but already got another one

Hello,
My htc butterfly s 9060 bootlooping with locked bootloader was solved.... I unlocked my bootloader by htcdev method... Its working... U also try this again and again bcoz its only method toh unlock the bootloader..... U also search all correct steps for this method....by searching on htc butterfly s unlocked bootloader threats.. And follow all steps... Bcoz i direct use htcdev site to unlock is not working... After that i used these steps for unlock bootloader...
May be help you
Abby
Sent from my HTC 9060 using XDA Free mobile app

I don't buy the 'can't be done' anymore after my issue for the past 24 hours. Your only way forward is to unlock the phone though. When I get back to the pc (using my now working phone!!) I'll put my notes up for you to work through.

I'm going to write this on the assumption that you followed the correct process to get your unlock token from HTC and you now have that.
BEFORE you do any of this, charge your phone. If you're having trouble powering it off, I found that having it connected via usb to my pc and then just holding the power off button or even the power off and volume down button (while it was on) did the trick. The LED should be lit red even if you don't have a visible indicator of what level the battery is at.
In the meantime:
#1 Go to your desktop on your pc. Set up a new folder and call it HTC.
#2 Into this folder extract everything within the attached zip. Don't put it into a further sub directory, just fill the HTC folder with the zip's contents. These are the ADB dll's and HTC's Fastboot programme. On top, I've included version 2.8.6.2 of TWRP.
#3 Put your Unlock_code.bin from the HTC email you received into this same folder.
-The contents of your folder should look like this:
{
"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"
}
#3 When your phone has charged for at least an hour (make it two to be safe) get it onto the bootloader screen and onto the fastboot menu. You should still have the phone connected to the pc and the line should now say 'fastboot usb'
#4 Open up a cmd terminal. Assuming that you know how this is done, make sure that it is reading c:\<path>\HTC (where path is whatever it is where htc is. On mine it was c:\users\username\desktop\HTC
#5 type the following in: fastboot flash unlocktoken Unlock_code.bin (then wait to see what it says.. if successful then proceed to #6)
#6 type the following in: fastboot reboot -bootloader
Tell us how you get on.

abby1996 said:
Hello,
My htc butterfly s 9060 bootlooping with locked bootloader was solved.... I unlocked my bootloader by htcdev method... Its working... U also try this again and again bcoz its only method toh unlock the bootloader..... U also search all correct steps for this method....by searching on htc butterfly s unlocked bootloader threats.. And follow all steps... Bcoz i direct use htcdev site to unlock is not working... After that i used these steps for unlock bootloader...
May be help you
Abby
Click to expand...
Click to collapse
Make sure you don't flash files from this forum (M7), dowload files only from your device forum
Butterfly S forum here: http://forum.xda-developers.com/htc-butterfly-s

Related

Boots into recovery (power button + volume down)

I have anther thread, but it's under a different subject, so here it goes..
I was having issues installing a new recovery, and now I'm afraid that I have no system at all.
If I try to just turn the phone on, it's stuck at the HTC splash screen. If I try boot into bootloader, it goes straight to recovery.
When in recovery, I have the error codes:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/command
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I have no idea what this is from or how to fix it.
I've wiped data/factory reset, wiped all cache and now I'm completely stuck :crying:
Please help!
Also, when I'm booting, the button lights at the bottom flash a number of times before it will actually boot into either screen.
I've tried to push a ROM onto the sdcard, but there aren't and devices detected. HTC Sync is installed as well as a fresh SDK. No idea why the phone can't be detected. I'm trying to detect it from the recovery.
OK, GOOD news, I think!
I finally got into the bootloader after holding it down forever. The phone is detected in fastboot.
{
"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"
}
And way I can flash a ROM from here?
Myrloc said:
I've tried to push a ROM onto the sdcard, but there aren't and devices detected. HTC Sync is installed as well as a fresh SDK. No idea why the phone can't be detected. I'm trying to detect it from the recovery.
OK, GOOD news, I think!
I finally got into the bootloader after holding it down forever. The phone is detected in fastboot.
And way I can flash a ROM from here?
Click to expand...
Click to collapse
It is possible but much harder since it would have to be in flashed in RUU mode and this can be dangerous and you will need S-off. First since you have a working fastboot, did you try flashing a new recovery from the fastboot steps I provided in post #8 of your other thread?
Do you have S-off? If so I can provide what is needed to flash the RUU in fastboot.
I have flashed a new recovery, but Clockwork is the only recovery that will work.
And no, It's not S-off
Myrloc said:
I have flashed a new recovery, but Clockwork is the only recovery that will work.
And no, It's not S-off
Click to expand...
Click to collapse
OK, well TWRP allows you to sideload a rom, but I am not sure about CWM. A Sideload is going to be easiest, but if we can't get that going we can flash a rom in fastboot using RUU. Please answer these questions: First
Since you have a custom recovery I assume you have an unlocked bootloader, correct?
Do you have s-off?
When the phone is detected in fastboot, and you issue the command:
Code:
fastboot erase cache
What is the exact console output?
When the phone is detected in fastboot, and you issue the command:
Code:
fastboot flash recovery twrp.img
(TWRP being the latest TWRP recovery img file)
What is the exact console output?
---------- Post added at 07:54 PM ---------- Previous post was at 07:48 PM ----------
OK, I saw your reply about having s-on. That's a bummer because it means we can't just flash a RUU in fastboot RUU mode.
Can you please download the latest TWRP 2.6.0.1 and rename it to twrp.img and place it in your adb/fastboot folder (platform-tools)
Now with phone connected and detected in fastboot
Code:
fastboot boot twrp.img
It should load up a working copy of the TWRP recovery without installing/flashing it to your recovery partition.
If we can get that up than maybe we can then use sideload to push a ROM.zip and install it.
I don't have S-off
This is the exact output:
C:\sdk\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>fastboot erase cache
erasing 'cache'...
OKAY [ 0.063s]
finished. total time: 0.063s
C:\sdk\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>fastboot flash recovery twrp.img
sending 'recovery' (7924 KB)...
OKAY [ 1.076s]
writing 'recovery'...
OKAY [ 0.650s]
finished. total time: 1.728s
I can't boot into recovery now with twrp. I'll to to boot in from fastboot
Trying to boot twrp from fastboot results in the splash screen and then a black screen (phone turns off)
Weird. What is the error when you try to boot into recovery now that we flashed TWRP. I know sometimes I have had to reboot several times before it would properly boot into the recovery.
There's no error, it's just the HTC splash screen with the small text on top and bottom and then the screen goes black, which I suspect is the phone turning off
Was there a working rom on the phone before the recovery troubles. I know that having the fastboot option selected in settings>power menu will not allow a proper boot to recovery.
You are disconnecting the cable after flashing the recovery before trying to boot into it? Have more than 50% battery?
If you don't have any rom installed or data on the phone you could try to erase all the partitions where roms put data:
fastboot erase boot (this will erase the kernel and initrd)
fastboot erase system
fastboot erase userdata
However be aware that we would need to install a rom or in this case flash images of those areas from a working system, backup or extracted RUU in order for it to work.
I think those are my only options now. I've tried rebooting into recovery a few times with no luck. It's normal for it to have
"Entering Recovery...
This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission. Failure to comply... etc."
On the top and bottom of the recovery HTC splash screen, right?
I really appreciate this help. This is a pretty new phone and by best phone I've had, and I'd hate to have screwed it up in a matter of minutes.
Yes normal for Entering Recovery to show at top.
Same for the red warning text, it is showing because you have custom recovery installed.
Let me think about it and lets see if any other members weigh in. You have a working fastboot, so we should be able to get you back working again.
You give me hope!
Shouldn't I be able to follow these directions..
Method 2 - flashing RUU (ROM Update Utility)
Visit this or this thread.
Find proper RUU for your device
Connect your device to the PC
Boot your device in fastboot mode (like you did during unlocking bootloader - power off the device and turn it on using power + vol down buttons and select "FASTBOOT")
Open up command prompt ( Start > Run > type cmd and hit enter ). The window that appears is called Command Prompt. <click here to see the image>
Navigate to where you unzipped "mini-sdk" package (type in Command Prompt: cd c:\mini-sdk). Note: make sure the path is not c:\mini-sdk\mini-sdk
In the Command Prompt type following command: fastboot oem lock
Flash RUU and follow on screen instructions.
You have now completely stock software on your device.
Click to expand...
Click to collapse
That just means I'm going to lock it again.
You sure you unlocked your boot loader and kept it unlocked? Did you use htcdev.com/token method or a different method.
We may be able to use a RUU. I am stupid for not asking. What are you details like: Location and carrier. If you are on one of the devices for which there is a RUU, then we can use it. If there is no RUU for your device then it is much harder to use the RUU method at all because you are S-on.
Get me this:
What country and carrier?
Output from a fastboot session where you issue the command:
Code:
getvar all
This way I can see the info needed for RUU search like CID and such.
Be sure to cut/blur/etc out your serial number and imei cause you don't want that floating around.
I think we can get you up and running.
Myrloc said:
I have flashed a new recovery, but Clockwork is the only recovery that will work.
And no, It's not S-off
Click to expand...
Click to collapse
So wait you can get cwm to work? If so you can mount usb storage and copy a Rom to it then flash the zip, I some what skimmed over this thread, your issue is you don't have a Rom installed right?
Sent from my HTC One using xda app-developers app
crushalot said:
You sure you unlocked your boot loader and kept it unlocked? Did you use htcdev.com/token method or a different method.
We may be able to use a RUU. I am stupid for not asking. What are you details like: Location and carrier. If you are on one of the devices for which there is a RUU, then we can use it. If there is no RUU for your device then it is much harder to use the RUU method at all because you are S-on.
Get me this:
What country and carrier?
Output from a fastboot session where you issue the command:
Code:
getvar all
This way I can see the info needed for RUU search like CID and such.
Be sure to cut/blur/etc out your serial number and imei cause you don't want that floating around.
I think we can get you up and running.
Click to expand...
Click to collapse
I'm with Sprint in the US. Here's my info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 1.00.20.0315
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.651.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4241mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.044s
I've downloaded the "RUU_Sprint_HTC_One_m7wls_1.29.651.7.zip" RUU from
http://forum.xda-developers.com/showthread.php?p=39588860
Think that'll work?
Ajxx16 said:
So wait you can get cwm to work? If so you can mount usb storage and copy a Rom to it then flash the zip, I some what skimmed over this thread, your issue is you don't have a Rom installed right?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Yeah, I can more or less get CMW to work and the issue is the phone won't boot up, it just sticks at the HTC splash screen, so I think the /system was formatted. I didn't see a usb storage option lat time I checked, but I do remember them having it on my EVO 3D. I'll check again if this RUU option doesn't work.
Yes. Just have your phone connected in fastboot and run the RUU.exe, it will flash everything back to stock.
PS - You should delete out these three lines from your info:
(bootloader) serialno: xxxxxx
(bootloader) imei: xxxxxx
(bootloader) meid: xxxxxx
IT WORKED! WHOO! :victory:
Thank you for all the support!!
Now the question is: do I go for the custom ROM or not?
It looks like I don't have a recovery installed..
Whenever I try to boot into recovery from bootloader, the screen goes black and shows a "phone broken" sign (exclamation above a phone).
I'm going to try to flash a custom ROM now.
Would the RUU have flashed a recovery with it?
Myrloc said:
It looks like I don't have a recovery installed..
Whenever I try to boot into recovery from bootloader, the screen goes black and shows a "phone broken" sign (exclamation above a phone).
I'm going to try to flash a custom ROM now.
Would the RUU have flashed a recovery with it?
Click to expand...
Click to collapse
For sprint phone, you need specific version the custom recovery
Take this from here
http://teamw.in/project/twrp2/171

[Q] Bricked after flashing Insertcoin 4.4 ROM (ADB can't find device)

I flashed the ROM in recovery. I thought I was S-OFF but am S-ON. It gave me error code 7 and the installation failed. Now I can't even boot into recovery (it just cycles between the HTC splash screen and then tries booting into recovery for a second. I see the recovery logo and then it reboots).
Holding down the volume down and power buttons I can get into HBOOT, but can't do a factory reset or recovery from there. I can get into the FASTBOOT menu, but my computer just tells me that the device connected has malfunctioned and can't recognize it. running "ADB Devices" returns with no devices found.
I downloaded and ran the RUU, but it can't find the phone. I'm out of ideas. I appreciate any help you guys can offer.
Caboose127 said:
I flashed the ROM in recovery. I thought I was S-OFF but am S-ON. It gave me error code 7 and the installation failed. Now I can't even boot into recovery (it just cycles between the HTC splash screen and then tries booting into recovery for a second. I see the recovery logo and then it reboots).
Holding down the volume down and power buttons I can get into HBOOT, but can't do a factory reset or recovery from there. I can get into the FASTBOOT menu, but my computer just tells me that the device connected has malfunctioned and can't recognize it. running "ADB Devices" returns with no devices found.
I downloaded and ran the RUU, but it can't find the phone. I'm out of ideas. I appreciate any help you guys can offer.
Click to expand...
Click to collapse
I'm willing to help.. but I am very busy.. can I have a look into this a bit later? Maybe someone else is going to be able to help you.. but if there isn't... I'm going to help you.
To calm down: As long as you can get into your hboot, everything is fine! You are not hardbricked!
Let me know if that's ok for you.
LibertyMarine said:
I'm willing to help.. but I am very busy.. can I have a look into this a bit later? Maybe someone else is going to be able to help you.. but if there isn't... I'm going to help you.
To calm down: As long as you can get into your hboot, everything is fine! You are not hardbricked!
Let me know if that's ok for you.
Click to expand...
Click to collapse
Hey, as long as you're willing to help, I can wait. I'm at work for the next 6 hours and don't really NEED my phone until I get off. So I've got time to wait.
Thanks.
Caboose127 said:
Hey, as long as you're willing to help, I can wait. I'm at work for the next 6 hours and don't really NEED my phone until I get off. So I've got time to wait.
Thanks.
Click to expand...
Click to collapse
Hmm.. in 3 hours I'm going to sleep.. (Switzerland time zone) And so I write some basic thing that you can test and try out.. so that we can determine what the best steps will be.
First: Give me the output from that command(while in fastboot-ubs):
fastboot getvar all
Click to expand...
Click to collapse
Second:
What hboot version do you have? 1.44/1.54/1.55
What's the stock ROM you recieved with the factory fresh phone? z.zz.XXX.z now.. what was the XXX number exactly? The international edition for example is: 1.24.401.7 I only need the 3-digit number.
Third:
Unlocked or Locked/Relocked?
LibertyMarine said:
Hmm.. in 3 hours I'm going to sleep.. (Switzerland time zone) And so I write some basic thing that you can test and try out.. so that we can determine what the best steps will be.
First: Give me the output from that command(while in fastboot-ubs):
Second:
What hboot version do you have? 1.44/1.54/1.55
What's the stock ROM you recieved with the factory fresh phone? z.zz.XXX.z now.. what was the XXX number exactly? The international edition for example is: 1.24.401.7 I only need the 3-digit number.
Third:
Unlocked or Locked/Relocked?
Click to expand...
Click to collapse
The phone is unlocked, HBOOT version is 1.44
running fastboot getvar all yields "waiting for device" Windows doesn't recognize the phone when it's plugged in. I know I have the correct drivers installed. When it tries to boot into recovery, I briefly see the device show up in Device Manager, but it disappears again. I don't know what the stock ROM was that came with the phone. I want to say it was 1.27.531.8, but I don't know for sure.
Caboose127 said:
The phone is unlocked, HBOOT version is 1.44
running fastboot getvar all yields "waiting for device" Windows doesn't recognize the phone when it's plugged in. I know I have the correct drivers installed. When it tries to boot into recovery, I briefly see the device show up in Device Manager, but it disappears again. I don't know what the stock ROM was that came with the phone. I want to say it was 1.27.531.8, but I don't know for sure.
Click to expand...
Click to collapse
Are you in the fastboot mode? I mean you booted your phone into the bootloader.. then you chose "fastboot" and after this there's written "FASTBOOT USB"? and then you got this waiting for device? because simply being in hboot doesn't allow you to use fastboot commands. Sorry if this is a noob question.. but if your device wasn't recognized.. this would be f***ing difficult to get anything running again. This bug with the recovery.. hmmm... don't boot into recovery again.. recovery is connected to adb not fastboot... and to calm down.. here we have a RUU to get back stock(don't use it right now):
http://www.androidruu.com/getdownlo...50.20_10.40.1150.04_release_324846_signed.exe
have you tried re flashing a new recovery via fastboot?
LibertyMarine said:
Are you in the fastboot mode? I mean you booted your phone into the bootloader.. then you chose "fastboot" and after this there's written "FASTBOOT USB"? and then you got this waiting for device? because simply being in hboot doesn't allow you to use fastboot commands. Sorry if this is a noob question.. but if your device wasn't recognized.. this would be f***ing difficult to get anything running again. This bug with the recovery.. hmmm... don't boot into recovery again.. recovery is connected to adb not fastboot... and to calm down.. here we have a RUU to get back stock(don't use it right now):
Click to expand...
Click to collapse
Nope, the phone is currently displaying "FASTBOOT USB" in red and I have the following selectable options on the screen:
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
khhhhris said:
have you tried re flashing a new recovery via fastboot?
Click to expand...
Click to collapse
I would flash a new recovery, but my computer doesn't seem to be recognizing my device. It does for a second during boot into recovery, but once the recovery crashes and the phone resets, the phone disappears from device manager. It doesn't show backup when I'm in FASTBOOT USB.
I'm going to try it on a coworkers computer.
Caboose127 said:
Nope, the phone is currently displaying "FASTBOOT USB" in red and I have the following selectable options on the screen:
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
Click to expand...
Click to collapse
this is weird... try another computer. Try different drivers from here:
http://forum.xda-developers.com/showthread.php?t=2191279
TRY EVERYTHING GO GET THE COMPUTER RECOGNIZING YOUR HTC ONE
---------- Post added at 07:35 PM ---------- Previous post was at 07:33 PM ----------
khhhhris said:
have you tried re flashing a new recovery via fastboot?
Click to expand...
Click to collapse
...lol this would be funny.. maybe his recovery partition is corrupt.. hmmm then we'd have to use different error handling strategies...
Progress! I was able to get fastboot working on my coworkers computer: Here's the gitvar results:
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.531.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ****************
(bootloader) imei: *****************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4267mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.047s
Click to expand...
Click to collapse
The phone shows up in Device Manager when I'm in FASTBOOT USB, but not when I'm in HBOOT. I still can't do anything with ADB.
I was able to flash a new recovery with FASTBOOT, but that recovery crashed as well.
If you are still trying for your computer to recognize the adb device and still hasn't then just buy an USB OTG then put an USB to flash a rom from there.
http://www.androidapps4u.com/temp/screenshot_3-usb-otg-cable.jpg
Define crashed? TWRP 2.6.3.0 ? or CWM ? What happens in recovery mode?
Caboose127 said:
Progress! I was able to get fastboot working on my coworkers computer: Here's the gitvar results:
The phone shows up in Device Manager when I'm in FASTBOOT USB, but not when I'm in HBOOT. I still can't do anything with ADB.
I was able to flash a new recovery with FASTBOOT, but that recovery crashed as well.
Click to expand...
Click to collapse
adb commands won't work while in fastboot mode/bootloader. fastboot needs to be used while in fastboot mode. While your in fastboot, try
fastboot erase cache
Then fastboot flash your recovery again (fastboot flash recovery nameofrecovery.img), and try to access recovery
Thanks for all of your help guys. I finally got it working.
For everyone else reference, mark your thread [SOLVED] and post a brief description how you fixed it..
Thanks guys for helping me out!

[Q] Htc One Bricked? Not sure...[SOLVED]

Not sure what had gone wrong... I believe the phone may be bricked. I rooted the device and sometime after I attempted to unroot it. Several attempts later with guides from here, htcguru, and many RUU's later it still does not work. It has reached the point where it no longer boots to any sort of rom, rather it will only boot into TRWP's recovery system. previously it would boot to an old rom that was loaded onto it with twrp from htc guru's website. it did nto have any touch compatibility and only the volume and power buttons would work.
I now also cannot access the phone from a computer, the PC (windows) recognizes it in the device manager, but it doesn't show up in windows explorer (maybe because it wont boot anything but the twrp recovery?)
No RUU's can fix it apparently, they will only say they either cannot connect to the phone, or an unknown error occurs and it simply cannot update the phone.
I've tried All-in-one kit, nothing seems to work. I am really at a loss, I spent 14 hours straight trying to unroot it, only progressively making it worse. I also could not get it to accept a mouse input from an otg cable whilst in the no touch input rom, don't know why..
Is this phone now inevitably ****ed beyond repair? I have pretty much given up all hope, I think the last time I asked for help with anything computer related was well over 3 years ago. I finally met my match in the hack and crack world, I read a lot of pages and guides, watched alot of videos, and even the HTC Dev site had me convinced this would be simple, easy, and painless work. Boy was I fooled.
I don't even know where to look anymore for answers, any I have no idea what information to give you guys, please excuse my apparent utter noobness and help me, I will provide as much information as I can, if I can.
Thanks in advance.
zoline411 said:
Not sure what had gone wrong... I believe the phone may be bricked. I rooted the device and sometime after I attempted to unroot it. Several attempts later with guides from here, htcguru, and many RUU's later it still does not work. It has reached the point where it no longer boots to any sort of rom, rather it will only boot into TRWP's recovery system. previously it would boot to an old rom that was loaded onto it with twrp from htc guru's website. it did nto have any touch compatibility and only the volume and power buttons would work.
I now also cannot access the phone from a computer, the PC (windows) recognizes it in the device manager, but it doesn't show up in windows explorer (maybe because it wont boot anything but the twrp recovery?)
No RUU's can fix it apparently, they will only say they either cannot connect to the phone, or an unknown error occurs and it simply cannot update the phone.
I've tried All-in-one kit, nothing seems to work. I am really at a loss, I spent 14 hours straight trying to unroot it, only progressively making it worse. I also could not get it to accept a mouse input from an otg cable whilst in the no touch input rom, don't know why..
Is this phone now inevitably ****ed beyond repair? I have pretty much given up all hope, I think the last time I asked for help with anything computer related was well over 3 years ago. I finally met my match in the hack and crack world, I read a lot of pages and guides, watched alot of videos, and even the HTC Dev site had me convinced this would be simple, easy, and painless work. Boy was I fooled.
I don't even know where to look anymore for answers, any I have no idea what information to give you guys, please excuse my apparent utter noobness and help me, I will provide as much information as I can, if I can.
Thanks in advance.
Click to expand...
Click to collapse
post the output of ''fastboot getvar all'' except the IMEI and SERIALNO
btw forget toolkits and work drirectly from your cmd prompt.
and post links of the ruu you tried to flash
what twrp version do you have?
14 hours.. You are stubborn! Better hope the device is recognized in fastboot as asked above
sent from my mobile device
Requested info
alray said:
post the output of ''fastboot getvar all'' except the IMEI and SERIALNO
btw forget toolkits and work drirectly from your cmd prompt.
and post links of the ruu you tried to flash
what twrp version do you have?
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.24.3263.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.531.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ***
(bootloader) imei: ***
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3834mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
RUU 1
http://d-h.st/4VH
found at http://forum.xda-developers.com/showthread.php?t=2427328
RUU 2
http://dl3.htc.com/application/RUU_...10.38m.1157.04_release_336982_signed_2(2).exe
found at http://forum.xda-developers.com/showthread.php?t=2496074
I am using TWRP v2.6.0.1 So far that is the only thing bootable to, the computer will recognize the phone, so will fastboot, however it seems impossible to drop files onto the phone. Anything will be helpful right now, even if it wipes it clean (only wiped it clean about 70 times over the last 24 hours anyway...)
SaHiLzZ said:
14 hours.. You are stubborn! Better hope the device is recognized in fastboot as asked above
sent from my mobile device
Click to expand...
Click to collapse
Stubborn is one of my middle names, along with 'determined' and 'accident prone'
Thank you both for responding, and any others who try to help, again, I normally don't request or even need help, usually I can solve problems after tinkering for 9-12 hours, this time I decided I would ask because I fear I may be a hop, skip, and jump away from owning a $300 paperweight/bonfire-material...
Additionally, I can 'fastboot oem lock' with command prompt, and 'fastboot flash unlocktoken Unlock_code.bin' done both more times than I can count now, and I can't get the t-mobile startup sound out of my head anymore da-da-duh-duh-da-duh...
zoline411 said:
RUU 1
http://d-h.st/4VH
found at http://forum.xda-developers.com/showthread.php?t=2427328
Click to expand...
Click to collapse
This RUU is a downgrade in version and require S-OFF to be flashed
zoline411 said:
RUU 2
http://dl3.htc.com/application/RUU_...10.38m.1157.04_release_336982_signed_2(2).exe
found at http://forum.xda-developers.com/showthread.php?t=2496074
Click to expand...
Click to collapse
This RUU is a downgrade in version and require S-OFF to be flashed
Afaik, there is no ruu for your phone version that can be flashed with S-ON
zoline411 said:
I am using TWRP v2.6.0.1 So far that is the only thing bootable to, the computer will recognize the phone, so will fastboot, however it seems impossible to drop files onto the phone. Anything will be helpful right now, even if it wipes it clean (only wiped it clean about 70 times over the last 24 hours anyway...)
Click to expand...
Click to collapse
TWRP 2.6.0.1 is very outdated. You'll need TWRP 2.6.3.3 to be able to flash 4.4+ roms.
zoline411 said:
Additionally, I can 'fastboot oem lock' with command prompt, and 'fastboot flash unlocktoken Unlock_code.bin' done both more times than I can count now, and I can't get the t-mobile startup sound out of my head anymore da-da-duh-duh-da-duh...
Click to expand...
Click to collapse
Woooh! Don't relock your bootloader! Its only needed to flash a RUU with s-on but there is no available for your phone!
Did you made a nandroid backup of your phone? If yes then restore it. if no, your only solution atm is to flash a custom rom (I personnaly recommend ARHD 53)
Is your bootloader still unlocked? If yes then:
Code:
fastboot flash recovery <twrp2.6.3.3>.img
fastboot erase cache [COLOR="Red"]<------ important[/COLOR]
fastboot reboot-bootloader
Download your custom rom and adb push it or adb sideload it from twrp recovery.
Faint light...
alray said:
This RUU is a downgrade in version and require S-OFF to be flashed
This RUU is a downgrade in version and require S-OFF to be flashed
Afaik, there is no ruu for your phone version that can be flashed with S-ON
TWRP 2.6.0.1 is very outdated. You'll need TWRP 2.6.3.3 to be able to flash 4.4+ roms.
Woooh! Don't relock your bootloader! Its only needed to flash a RUU with s-on but there is no available for your phone!
Did you made a nandroid backup of your phone? If yes then restore it. if no, your only solution atm is to flash a custom rom (I personnaly recommend ARHD 53)
Is your bootloader still unlocked? If yes then:
Code:
fastboot flash recovery <twrp2.6.3.3>.img
fastboot erase cache [COLOR="Red"]<------ important[/COLOR]
fastboot reboot-bootloader
Download your custom rom and adb push it or adb sideload it from twrp recovery.
Click to expand...
Click to collapse
I was getting that feeling after about 8 hours of button pressing, t-mobile jingles, and seemingly endless reading of interwebs, that there wasn't any sort of RUU for my phone, thank god. This means I can stop performing Einstein's definition of insanity...
TWRP v2.6.3.3, right... This should be the correct link for me right? (below) Also the line in command prompt should be "<openrecovery-twrp-2.6.3.3-m7>.img" without quotes, should I decide not to rename it, correct? **EDIT** Will not let me post outside links, the link in this page will take you to techerrata, I used the dl link marked 2.6.3.3, also worth noting there is a 2.7.0.0, should I bother with 2.7? or leave it be.
http://forum.xda-developers.com/showthread.php?t=2173870
Bad thing I locked the bootloader? It's currently unlocked for the hundredth time it seems, under your recommendation I will leave it unlocked. Further under your recommendation, the link below should be the version of ARHD 53 needed for my phone also, correct? **DOUBLE EDIT** No link to the outside world aloud, below there is a link to the android rev blogspot, I picked the first dl under HTC One, KitKat 4.4.2.
http://forum.xda-developers.com/showthread.php?t=2183023
As I believe I mentioned earlier, it appears, at the moment, impossible to transfer files over to the phone via usb, it shows up in device manager, but not in windows explorer under "My Computer." If you have an idea around that that would be fantastic, although not particularly needed, the HTC Sync Manager 'drive' that usually also appears also no longer shows up, however the drivers were loaded into this computer already, but the folder in the fake drive containing drivers was not copied (i iz stupidz.)
Also I don't believe I made the nandroid backup, I don't know why, actually I do, it's because I was an idiot and didn't bother to take the normal precautions.
The whole reason I ever wanted to root the device was for s-off, It only turned into a nightmare, I obviously dont even want to do that (well not right now, I'll have to talk to more intelligent types before attempting it,) so since I cannot figure out how to drag and drop (perhaps a way through command prompt?) the files to the phone, can I get a guide or a link to a guide, and please make it into kind-noob-langauge for me, to use abd to push it (ARHD) to the phone, or use it to transfer it to the phone where I can then use TWRP to flash/sideload/not perfectly sure what sideload is, into place.
Sorry for tl;dr; though, I have a feeling you guys are somewhat used to it.
Thanks greatly, I see the faint light on the other end getting brighter, lets hope I'm in a tunnel and not dying.
zoline411 said:
TWRP v2.6.3.3, right... This should be the correct link for me right? (below) Also the line in command prompt should be "<openrecovery-twrp-2.6.3.3-m7>.img" without quotes, should I decide not to rename it, correct? **EDIT** Will not let me post outside links, the link in this page will take you to techerrata, I used the dl link marked 2.6.3.3, also worth noting there is a 2.7.0.0, should I bother with 2.7? or leave it be.
http://forum.xda-developers.com/showthread.php?t=2173870
Click to expand...
Click to collapse
I'll recommend you to use 2.6.3.3 not 2.7 , there is a minor bug with 2.7 which will prevent the screen to turn off when charging the phone when powered off.
Make sure your recovery file and your rom is in the same folder were abd and fastboot are on your computer.
Boot your phone in bootloader mode, select fastboot then connect usb cable
open a cmd prompt from your adb/fastoot folder (hold shift + right click a blank space in the folder, select ''start a commend prompt here'')
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
zoline411 said:
the link below should be the version of ARHD 53 needed for my phone also, correct? **DOUBLE EDIT** No link to the outside world aloud, below there is a link to the android rev blogspot, I picked the first dl under HTC One, KitKat 4.4.2.
http://forum.xda-developers.com/showthread.php?t=2183023
Click to expand...
Click to collapse
Yes this is the correct rom
zoline411 said:
As I believe I mentioned earlier, it appears, at the moment, impossible to transfer files over to the phone via usb, it shows up in device manager, but not in windows explorer under "My Computer." If you have an idea around that that would be fantastic, although not particularly needed, the HTC Sync Manager 'drive' that usually also appears also no longer shows up, however the drivers were loaded into this computer already, but the folder in the fake drive containing drivers was not copied (i iz stupidz.)
Click to expand...
Click to collapse
You will use ADB to transfer files to your phone when booted in TWRP recovery
boot your phone in twrp 2.6.3.3
go in windows device manager and make sure your device is listed as ''android usb device ---> My HTC''. If yes your good to push to rom. If your phone is listed as ''Other Devices ---> One'' you'll need to follow that guide before:
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
2) Q: I'm using Windows 7 what should I worry about
A: when you issue the command "fastboot boot CWM.img" (now only in CWM/TWRP restore method) there's a high chance drivers won't correctly install
{
"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"
}
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone anyways​
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didnt install correct driver
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
-------------------------------------------------------------------------------------------------------------------------------------------
PUSH THE ROM
Again make sure the rom is in the adb/fasboot folder
open a command prompt from that folder
boot your phone in TWRP main menu
Code:
adb push ''name_of_rom_file''.zip /sdcard/
then in twrp select ''install'' and browse the sdcard folder to find your rom. Select it and swipe to flash.
after it flashed reboot your phone.
If something is not clear/don't work, ask me here and post screenshot of your command prompt
I'm not Dead.
alray said:
I'll recommend you to use 2.6.3.3 not 2.7 , there is a minor bug with 2.7 which will prevent the screen to turn off when charging the phone when powered off.
Make sure your recovery file and your rom is in the same folder were abd and fastboot are on your computer.
Boot your phone in bootloader mode, select fastboot then connect usb cable
open a cmd prompt from your adb/fastoot folder (hold shift + right click a blank space in the folder, select ''start a commend prompt here'')
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Yes this is the correct rom
You will use ADB to transfer files to your phone when booted in TWRP recovery
boot your phone in twrp 2.6.3.3
go in windows device manager and make sure your device is listed as ''android usb device ---> My HTC''. If yes your good to push to rom. If your phone is listed as ''Other Devices ---> One'' you'll need to follow that guide before:
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
2) Q: I'm using Windows 7 what should I worry about
A: when you issue the command "fastboot boot CWM.img" (now only in CWM/TWRP restore method) there's a high chance drivers won't correctly install
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone anyways​
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didnt install correct driver
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
-------------------------------------------------------------------------------------------------------------------------------------------
PUSH THE ROM
Again make sure the rom is in the adb/fasboot folder
open a command prompt from that folder
boot your phone in TWRP main menu
Code:
adb push ''name_of_rom_file''.zip /sdcard/
then in twrp select ''install'' and browse the sdcard folder to find your rom. Select it and swipe to flash.
after it flashed reboot your phone.
If something is not clear/don't work, ask me here and post screenshot of your command prompt
Click to expand...
Click to collapse
<Farnsworth>
Good news everyone!
</Farnsworth>
It worked! Yay. I greatly thank you from the bottom of my heart. Now it's just as good as it was before, and better. Using the sense toolkit, love it, and more importantly, the phone is actually normal now, double love it.
I really do like the area rom, I installed Xposed, and used it to update to the latest sense toolkit. Everything is wonderful. Stayed away from twrp 2.7, and we'll yeah, it's all good.
How do I give you some kind of 'kudos' or something along those lines. It's worth mentioning that this thread question can be marked as solved, not sure how to do it myself on the app. But I will try to hunt it down.
Also, I would like to see a link to anything that contains all this miraculous knowledge within your brain, without having to pull a matrix stunt. Videos for everything you think I should watch, guides to read, and pictures to stare at. I would honestly love to be able to look at the Greek I gave to you and nearly instantly be able to both understand what is wrong, and how I fix it.
Wow, just wow, thank you. I nearly turned my phone into a $300 paperweight over the course of 14 or so hours, and you solved the problem in less than 10 posts combined. Epic Android Kudos.
THANK YOU!
Sent from my HTC One using xda app-developers app
zoline411 said:
<Farnsworth>
Good news everyone!
</Farnsworth>
It worked! Yay. I greatly thank you from the bottom of my heart. Now it's just as good as it was before, and better. Using the sense toolkit, love it, and more importantly, the phone is actually normal now, double love it.
I really do like the area rom, I installed Xposed, and used it to update to the latest sense toolkit. Everything is wonderful. Stayed away from twrp 2.7, and we'll yeah, it's all good.
How do I give you some kind of 'kudos' or something along those lines. It's worth mentioning that this thread question can be marked as solved, not sure how to do it myself on the app. But I will try to hunt it down.
Also, I would like to see a link to anything that contains all this miraculous knowledge within your brain, without having to pull a matrix stunt. Videos for everything you think I should watch, guides to read, and pictures to stare at. I would honestly love to be able to look at the Greek I gave to you and nearly instantly be able to both understand what is wrong, and how I fix it.
Wow, just wow, thank you. I nearly turned my phone into a $300 paperweight over the course of 14 or so hours, and you solved the problem in less than 10 posts combined. Epic Android Kudos.
THANK YOU!
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Congrats
you can mark the thread as solved by editing your first post -> go advanced -> then you can edit the main thread title and include [SOLVED]
you can thank the people who helped you by pressing the little Thanks button, on their posts
zoline411 said:
Also, I would like to see a link to anything that contains all this miraculous knowledge within your brain, without having to pull a matrix stunt. Videos for everything you think I should watch, guides to read, and pictures to stare at. I would honestly love to be able to look at the Greek I gave to you and nearly instantly be able to both understand what is wrong, and how I fix it.
Click to expand...
Click to collapse
Guide to return stock from nkk71. There is good informationd in the FAQ.
Guide to push or sideload a rom
There is many more, but those 2 are essential to recover a soft bricked phone
There is also great guides from ARHD blogspot here
@alray
Wonderful, I've been reading and to my understanding my phone in its current state is no longer able to have S-off, is that right? I believe if has to do with an update that occurred not so long ago, and I of course not knowing well enough did opt for the update. Also I have no idea whether any sort of backup would have been helpful or not.
I'm going to spend a great deal of time reading those guides, what I should have done before ever making an attempt at rooting and S-off, so yeah... Time to hit the books.

HTC M7 - Tried to root (Installed TWRP) but now phone won't boot

I tried to use this guide to on htconeroot
Got to installing the zip for SuperSU v1.30
The phone rebooted but it said SuperSU failed
Tried to install Update Super SU v2.46
Phone no longer reboots. It shows the white HTC One loading screen but then just goes very dark grey forever.
I can still access the white menu that comes up when you hold volume down and power
Can also access the TWRP screen, however I tried factory reset there and it didn't change, it still won't boot.
Can't take out sd or battery as metal case
Anyway not sure if this is meant to be in the HTC M7 category, a TWRP category, Rooting one.
I'm not sure if it is because the guide was for 4.3 and on 5.02 or what.
I also held the power off button when it was doing some things which may have also caused it
I don't really care about it being rooted so much as having my phone back. The only reason I wanted it rooted was to install the camera change that is supposed to get rid of the green tint.
Anyway thank you for your time. And I appreciate any assistance that can be given. I have spent hours trying to figure it out, but I am still confused and figure I am likely to screw it up even more
Syrup4 said:
I tried to use this guide to on htconeroot
Got to installing the zip for SuperSU v1.30
The phone rebooted but it said SuperSU failed
Tried to install Update Super SU v2.46
Phone no longer reboots. It shows the white HTC One loading screen but then just goes very dark grey forever.
I can still access the white menu that comes up when you hold volume down and power
Can also access the TWRP screen, however I tried factory reset there and it didn't change, it still won't boot.
Can't take out sd or battery as metal case
Anyway not sure if this is meant to be in the HTC M7 category, a TWRP category, Rooting one.
I'm not sure if it is because the guide was for 4.3 and on 5.02 or what.
I also held the power off button when it was doing some things which may have also caused it
I don't really care about it being rooted so much as having my phone back. The only reason I wanted it rooted was to install the camera change that is supposed to get rid of the green tint.
Anyway thank you for your time. And I appreciate any assistance that can be given. I have spent hours trying to figure it out, but I am still confused and figure I am likely to screw it up even more
Click to expand...
Click to collapse
Since you have twrp installed, did you make a nandroid before installing the zip, if so restore it.
If you don't have a nandroid, please post output of fastboot getvar all.
mb_guy said:
Since you have twrp installed, did you make a nandroid before installing the zip, if so restore it.
If you don't have a nandroid, please post output of fastboot getvar all.
Click to expand...
Click to collapse
Thank you very much for responding.
I am not sure what a nandroid backup is. I was following a guide.
I copied every file on phone to my computer via the file manager. And I used the command prompt and typed in "adb backup -apk -all -f backup.ab". I am not sure if that is the right kind.
I don't know how to post that output you asked for. I googled it, but it sounded like I needed to use my computer, and my computer no longer recognizes my phone due to it not booting. Or is that done in TWRP? Thank you again.
PS: htconeroot .com /htc-one-root/how-to-root-htc-one-windowsmaclinux/ is the guide I was following. Got up to install SU before it went bad. In case it helps. I can't properly link as I haven't made enough posts.
Syrup4 said:
Thank you very much for responding.
I am not sure what a nandroid backup is. I was following a guide.
I copied every file on phone to my computer via the file manager. And I used the command prompt and typed in "adb backup -apk -all -f backup.ab". I am not sure if that is the right kind.
I don't know how to post that output you asked for. I googled it, but it sounded like I needed to use my computer, and my computer no longer recognizes my phone due to it not booting. Or is that done in TWRP? Thank you again.
PS: htconeroot .com /htc-one-root/how-to-root-htc-one-windowsmaclinux/ is the guide I was following. Got up to install SU before it went bad. In case it helps. I can't properly link as I haven't made enough posts.
Click to expand...
Click to collapse
A nandroid backup is actually made with in twrp, read up on for future.
You obviously have adb installed since you used it for backup.
Put the phone in bootloader mode, restart holding down power and volume down. (have you not gone into twrp?) Then plug in usb and you should see "fastboot usb"
then from the adb folder type "fastboot getvar all"
Do some google searching there are dozens of articles regarding flashing htc one and using adb and fastboot commands phone bootloader and recovery .
Delete please, forgot to quote/ reply.
mb_guy said:
Since you have twrp installed, did you make a nandroid before installing the zip, if so restore it.
If you don't have a nandroid, please post output of fastboot getvar all.
Click to expand...
Click to collapse
Hello, thanks again. is this what you were referring to posting?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.17.661.35
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Removed
(bootloader) imei: Removed
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: TELUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4165mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-eff4f609
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s
Syrup4 said:
Hello, thanks again. is this what you were referring to posting?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.17.661.35
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: removed
(bootloader) imei: removed
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: TELUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4165mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-eff4f609
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s
Click to expand...
Click to collapse
When posting a "fastboot getvar all" edit out your imei and serialno, don't post these 2 numbers on the forum (edit your above post and remove them).
You should be able to restore your phone by flashing the 7.17.631.7 7.17.661.7 RUU. You'll first need to edit your MISC partition to change your version-main from 7.17.661.35 to 7.17.661.7 then relock your bootloader and flash the RUU. Once done, you'll have to install 2 ota updates so your phone is back to the 7.17.661.35 version. When back on this version, re-unlock your bootloader, re-flash twrp and flash supersu version 2.46 (any version lower than that will not work on lollipop)
Instructions how to change your version-main at the end of post #2 of this thread (see "how to downgrade with s-on")
The RUU and instructions how to flash it in the same thread at post #1
alray said:
When posting a "fastboot getvar all" edit out your imei and serialno, don't post these 2 numbers on the forum (edit your above post and remove them).
You should be able to restore your phone by flashing the 7.17.631.7 RUU. You'll first need to edit your MISC partition to change your version-main from 7.17.631.35 to 6.17.631.7 then relock your bootloader and flash the RUU. Once done, you'll have to install 2 ota updates so your phone is back to the 7.17.631.35 version. When back on this version, re-unlock your bootloader, re-flash twrp and flash supersu version 2.46 (any version lower than that will not work on lollipop)
Instructions how to change your version-main at the end of post #2 of this thread (see "how to downgrade with s-on")
The RUU and instructions how to flash it in the same thread at post #1
Click to expand...
Click to collapse
Thank you very much. Both for the help fixing it, and letting me know to remove that info. I read the instructions however given that it won't boot. My computer won't recognize it to transfer the tool (Misc_Tool_1.00.zip) over, so I can install it in TWRP. I tried pushing it using a command with adb. But it said Device not found. Given it has no removable SD card I do not know how to move it. The manual one also required adb shell, which says device not found. I shall continue looking things up in the mean time.
Edit: Strangely HTC Sync manager pops up when it does fail to boot if I restart the phone. Given it is set to do so when the phone is plugged in. However it always says "no phone connected". As if it recognizes it for a second then stops.
Syrup4 said:
Thank you very much. Both for the help fixing it, and letting me know to remove that info. I read the instructions however given that it won't boot. My computer won't recognize it to transfer the tool (Misc_Tool_1.00.zip) over, so I can install it in TWRP. I tried pushing it using a command with adb. But it said Device not found. Given it has no removable SD card I do not know how to move it. The manual one also required adb shell, which says device not found. I shall continue looking things up in the mean time.
Edit: Strangely HTC Sync manager pops up when it does fail to boot if I restart the phone. Given it is set to do so when the phone is plugged in. However it always says "no phone connected". As if it recognizes it for a second then stops.
Click to expand...
Click to collapse
First thing you want when using adb or fastboot commands is to make sure HTC Sync is not installed or your computer because it can interfere with adb/fastboot connectivity. So go ahead and uninstall it (not closing it, uninstall for real) don't uninstall the drivers btw.
Make sure you have the latest htc drivers installed, that you are using a good usb cable (preferably the original cable or any other cable already known to work with data transfer as opposed to usb cables that can only provide power). Make sure you are using a usb 2.0 port on your computer at the back of your tower (not using front ports neither an external usb hub). Finally, adb commands will only work when booted in twrp recovery, they will not work when in bootloader mode as opposed to fastboot commands which only works in bootloader.
If using the commands to change your version-main, better to post it here before so I can confirm its the correct one. A simple typo in this command could make the situation worse (i.e: corrupting your misc partition).
alray said:
First thing you want when using adb or fastboot commands is to make sure HTC Sync is not installed or your computer because it can interfere with adb/fastboot connectivity. So go ahead and uninstall it (not closing it, uninstall for real) don't uninstall the drivers btw.
Make sure you have the latest htc drivers installed, that you are using a good usb cable (preferably the original cable or any other cable already known to work with data transfer as opposed to usb cables that can only provide power). Make sure you are using a usb 2.0 port on your computer at the back of your tower (not using front ports neither an external usb hub). Finally, adb commands will only work when booted in twrp recovery, they will not work when in bootloader mode as opposed to fastboot commands which only works in bootloader.
If using the commands to change your version-main, better to post it here before so I can confirm its the correct one. A simple typo in this command could make the situation worse (i.e: corrupting your misc partition).
Click to expand...
Click to collapse
Hello, thank you again.
I uninstalled sync. I am using the original cable, and have now plugged it in to a USB 2.0 port on the back.
I also tried to use the commands while the phone is on the TWRP screen. The one with a grey background and big touch buttons with blue on them that say "Install" "Wipe" "Backup" etc.
But it still won't recognize my device. I can type in ADB to get a list of commands.
But when I try to push anything, it says "error: device not found"
I tried the command "adb get-serialno" to see if other commands worked but it said "unknown".
Edit: Got it to show up as a device when in Fastboot USB. However it won't show up as a drive in mycomputer. ADB won't recognize it in either that mode or on TWRP. And once I access TWRP, it changes to android phone" as shown in the second pic.
{
"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"
}
Syrup4 said:
Hello, thank you again.
I uninstalled sync. I am using the original cable, and have now plugged it in to a USB 2.0 port on the back.
I also tried to use the commands while the phone is on the TWRP screen. The one with a grey background and big touch buttons with blue on them that say "Install" "Wipe" "Backup" etc.
But it still won't recognize my device. I can type in ADB to get a list of commands.
But when I try to push anything, it says "error: device not found"
I tried the command "adb get-serialno" to see if other commands worked but it said "unknown".
Edit: Got it to show up as a device when in Fastboot USB. However it won't show up as a drive in mycomputer. ADB won't recognize it in either that mode or on TWRP. And once I access TWRP, it changes to android phone" as shown in the second pic.
Click to expand...
Click to collapse
When you're in TWRP are you sure you don't see the device as a disk drive, the newer versions of twrp support mtp which allows this. You should be able just to copy paste from you PC to the device. It looks to me this is working from your second picture.
mb_guy said:
It looks to me this is working from your second picture.
Click to expand...
Click to collapse
same. Maybe re-installing the latest drivers version wouldn't hurt...
alray said:
same. Maybe re-installing the latest drivers version wouldn't hurt...
Click to expand...
Click to collapse
mb_guy said:
When you're in TWRP are you sure you don't see the device as a disk drive, the newer versions of twrp support mtp which allows this. You should be able just to copy paste from you PC to the device. It looks to me this is working from your second picture.
Click to expand...
Click to collapse
Thanks once again both of you. But even though it seems like it should be listed. It is not. And if I right click on the device that appears, it is greyed out.
Which drivers? HTC ones? Android ones? or the Universal ADB (Android Debug Bridge) Driver for Windows.? I think I am getting confused between uninstalling and installing so many drivers, as to which overwrite.
Thanks again
Edit: It is TWRP v2.6.3.0
Syrup4 said:
Thanks once again both of you. But even though it seems like it should be listed. It is not. And if I right click on the device that appears, it is greyed out.
Which drivers? HTC ones? Android ones? or the Universal ADB (Android Debug Bridge) Driver for Windows.? I think I am getting confused between uninstalling and installing so many drivers, as to which overwrite.
Thanks again
Edit: It is TWRP v2.6.3.0
Click to expand...
Click to collapse
The HTC drivers, not the universal ones.
2.6.3.0 is to old and will cause problem. Once your drivers problem is fixed, update your twrp recovery before going any further (at least 2.6.3.3 or much newer if you want MTP support)
Ill be back in a few hours good luck
alray said:
The HTC drivers, not the universal ones.
2.6.3.0 is to old and will cause problem. Once your drivers problem is fixed, update your twrp recovery before going any further (at least 2.6.3.3 or much newer if you want MTP support)
Ill be back in a few hours good luck
Click to expand...
Click to collapse
Thank you again.
I'm not sure how to update twrp.
However I tried to use a driver remover, then download and install new htc drivers, and nothing seems to have changed.
I will try and go over that video guide I was following before and see if there was something wrong in it compared to others once I get up (7:00am here and I haven't slept yet), but I thought I would update the situation before then.
Have a good day
Syrup4 said:
Thank you again.
I'm not sure how to update twrp.
However I tried to use a driver remover, then download and install new htc drivers, and nothing seems to have changed.
I will try and go over that video guide I was following before and see if there was something wrong in it compared to others once I get up (7:00am here and I haven't slept yet), but I thought I would update the situation before then.
Have a good day
Click to expand...
Click to collapse
Is fastboot connectivity working? (boot in bootloader mode and use "fastboot device" command to see if your phone is detected) Or is it only adb not working when in twrp?
You can update twrp using fastboot commands when in bootloader mode:
fastboot flash recovery file_name.img
fastboot erase cache
fastboot reboot-bootloader
(replace "file_name.img" by the file name of the recovery you want to flash.
Syrup4 said:
Thank you again.
I'm not sure how to update twrp.
However I tried to use a driver remover, then download and install new htc drivers, and nothing seems to have changed.
I will try and go over that video guide I was following before and see if there was something wrong in it compared to others once I get up (7:00am here and I haven't slept yet), but I thought I would update the situation before then.
Have a good day
Click to expand...
Click to collapse
I have good luck with these adb tools. Also did you reboot pc after removing old drivers, sometime things just magically work after.
http://forum.xda-developers.com/showthread.php?t=2317790
TWRP is updated from fastboot (fastboot flash recovery nameofrecovery.img)
https://dl.twrp.me/m7/
mb_guy said:
I have good luck with these adb tools. Also did you reboot pc after removing old drivers, sometime things just magically work after.
http://forum.xda-developers.com/showthread.php?t=2317790
TWRP is updated from fastboot (fastboot flash recovery nameofrecovery.img)
https://dl.twrp.me/m7/
Click to expand...
Click to collapse
alray said:
Is fastboot connectivity working? (boot in bootloader mode and use "fastboot device" command to see if your phone is detected) Or is it only adb not working when in twrp?
You can update twrp using fastboot commands when in bootloader mode:
fastboot flash recovery file_name.img
fastboot erase cache
fastboot reboot-bootloader
(replace "file_name.img" by the file name of the recovery you want to flash.
Click to expand...
Click to collapse
THANK YOU.
There has been progress.
So I installed the new TWRP posted, version 2.8.7.0-m7.
At first it said signature checking failed, so I booted the token thing from HTCDev again.
It then allowed me to install the new TWRP.
When the new TWRP was installed it came up with a screen with errors in red. "Can't write to Cache" or something.
I was going to write them down but it restarted itself then got stuck.
However once I turned the phone off and on again then went into recovery the new version allowed "MTP Device" to be recognized as a drive on my computer and I was able to copy over Misc_Tool_1.00.zip.
It still won't boot though. Anyway then I was re-reading the steps to use the Misc Tool and it said I should be using twrp 2.6.3.3 as newer versions hang.
So would the next step to be to reflash an older TWRP like I did the new one?
Then install Misc_Tool.zip and follow the other instructions that went along with it in that guide posted on the last page?
Are there any other things I should copy onto the phone first in case the older TWRP stops the drive from showing up on my computer again?
I just thought I would double check before proceeding so that I do not make a bigger mess of it.
Thank you both again for your time:good:
Syrup4 said:
It still won't boot though. Anyway then I was re-reading the steps to use the Misc Tool and it said I should be using twrp 2.6.3.3 as newer versions hang.
So would the next step to be to reflash an older TWRP like I did the new one?
Then install Misc_Tool.zip and follow the other instructions that went along with it in that guide posted on the last page?
Are there any other things I should copy onto the phone first in case the older TWRP stops the drive from showing up on my computer again?
I just thought I would double check before proceeding so that I do not make a bigger mess of it.
Click to expand...
Click to collapse
The tool Ive made will indeed hang if used with recent twrp version, sorry i forgot to mention that. So yes flash the 2.6.3.3 version and you should be able to use it without any problem. MTP isn't supported in 2.6.3.3 but you should be able to use "adb push" commands to transfer files, anyway I don't think you'll need any other file for now. Just change your version-main then relock your bootloader and flash the ruu.
Syrup4 said:
THANK YOU.
There has been progress.
So I installed the new TWRP posted, version 2.8.7.0-m7.
At first it said signature checking failed, so I booted the token thing from HTCDev again.
It then allowed me to install the new TWRP.
When the new TWRP was installed it came up with a screen with errors in red. "Can't write to Cache" or something.
I was going to write them down but it restarted itself then got stuck.
However once I turned the phone off and on again then went into recovery the new version allowed "MTP Device" to be recognized as a drive on my computer and I was able to copy over Misc_Tool_1.00.zip.
It still won't boot though. Anyway then I was re-reading the steps to use the Misc Tool and it said I should be using twrp 2.6.3.3 as newer versions hang.
So would the next step to be to reflash an older TWRP like I did the new one?
Then install Misc_Tool.zip and follow the other instructions that went along with it in that guide posted on the last page?
Are there any other things I should copy onto the phone first in case the older TWRP stops the drive from showing up on my computer again?
I just thought I would double check before proceeding so that I do not make a bigger mess of it.
Thank you both again for your time:good:
Click to expand...
Click to collapse
First I would download the ruu suggested by Alray to your computer (if you haven't already) have it in the adb folder
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
7.17.661.7 ruu
Then
Just flash the older twrp like you did the installed version
fastboot flash recovery nameofrecovery.img
fastboot erase cache
fastboot reboot-bootloader
then run the misc tool and change cid
Then
then flash the ruu (it will replace twrp and rom with stock versions)
use the "how to flash" instructions on the first page of ruu download page.
Note: you MUST use htc_fastboot. Download it and place in the adb folder.
phone will reboot and then continue when flashing the ruu, don't rush, will take 10-15 min

Stuck in fastboot - No running ROM, recovery , ADB

Dear Community,
I reached a state with my mobile phone where I really do not know anymore how to proceed to get back to any running ROM on my HTC Mini 2. :angel:
I read the other threads on this topic, but they did not help my situation.
Maybe someone see's what I am missing, or what I can do about it. In the end, I would like to go back to a CM 11 / CM 13 ROM, but as I understood, I should first go back to stock to enable S-off, using a nandroid recovery backup. Then flash a new custom rom. However I am stuck without any recovery running properly. Only the hboot/fastboot menu is working, and the phone will always boot there again.
Some more info:
- ADB does not work currently. I tried Win and OSX , so I believe its the phone rejecting it.
- With stock recovery, reading in the 0P8BIMG.zip RUU file containing a 2.19.401.2 or 2.18.401.3 system fails.
- Flashing recovery TWRP 2.8.5.0 / 2.8.1.0 works, but the phone will not start it.
Code:
C:\Users\USER>fastboot flash recovery "Z:\Installs\HTC Mini 2\recovery-twrp-2.8.5.0.img"
sending 'recovery' (11796 KB)...
OKAY [ 1.393s]
writing 'recovery'...
OKAY [ 0.394s]
finished. total time: 1.790s
- My bootloader is ***Unlocked*** according to the fastboot screen. However, I cannot lock it :
Code:
C:\Users\USER>fastboot oem lock
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) Start Verify: 3
(bootloader) WARM RESET: 8
(bootloader) [INFO] Reset reason in IMEM is 0x77665501
(bootloader) [INFO] Rebooting device
FAILED (status read failed (No such file or directory))
finished. total time: 1.056s
- Output of getvar all :
Code:
C:\Users\USER>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.101.1102.19.1017
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.19.401.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ...
(bootloader) imei: ...
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: mem_ul
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0P8B20000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: be7179e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Please let me know if I missed to provide important information.
Is there any way for me to start over on a lower level ? Or is a mobile shop / HTC my only solution left?
Thanks a lot for any feedback!
Greetings,
faiv
faiv said:
Dear Community,
I reached a state with my mobile phone where I really do not know anymore how to proceed to get back to any running ROM on my HTC Mini 2. :angel:
I read the other threads on this topic, but they did not help my situation.
Maybe someone see's what I am missing, or what I can do about it. In the end, I would like to go back to a CM 11 / CM 13 ROM, but as I understood, I should first go back to stock to enable S-off, using a nandroid recovery backup. Then flash a new custom rom. However I am stuck without any recovery running properly. Only the hboot/fastboot menu is working, and the phone will always boot there again.
Click to expand...
Click to collapse
you dont need S-OFF to install ROM just Bootloader unlocked.
Just because you can flash the recovery doesn't mean its the correct one, try the one in here
You need HTC drivers for ADB to work. (see link above)
After flashing recovery you can flash the rom using your preferred method.
kativiti said:
you dont need S-OFF to install ROM just Bootloader unlocked.
Just because you can flash the recovery doesn't mean its the correct one, try the one in here
You need HTC drivers for ADB to work. (see link above)
After flashing recovery you can flash the rom using your preferred method.
Click to expand...
Click to collapse
Thanks for your reply!
Unfortunately, it does not help. I flashed the recovery you suggested, and I still cannot boot into recovery.
Code:
C:\Users\oo>fastboot flash recovery C:\Users\USER\Downloads\twrp-2.8.1.0-20142812-memul.img
sending 'recovery' (10896 KB)...
OKAY [ 1.312s]
writing 'recovery'...
OKAY [ 0.378s]
finished. total time: 1.696s
I have the HTC Sync manager installed. Last time ,this was enough to get the drivers as well.
Just tested the other adb.exe plus the api as well. Does not work.
faiv said:
Thanks for your reply!
Unfortunately, it does not help. I flashed the recovery you suggested, and I still cannot boot into recovery.
Code:
C:\Users\oo>fastboot flash recovery C:\Users\USER\Downloads\twrp-2.8.1.0-20142812-memul.img
sending 'recovery' (10896 KB)...
OKAY [ 1.312s]
writing 'recovery'...
OKAY [ 0.378s]
finished. total time: 1.696s
I have the HTC Sync manager installed. Last time ,this was enough to get the drivers as well.
Just tested the other adb.exe plus the api as well. Does not work.
Click to expand...
Click to collapse
try to unlock bootloader again(just last step) , i remember having same kind of problem before, with the hboot.
and of course you are using original HTC cable?
kativiti said:
try to unlock bootloader again(just last step) , i remember having same kind of problem before, with the hboot.
and of course you are using original HTC cable?
Click to expand...
Click to collapse
I tried unlocking again already, but I must admit that you got me with the last one. I'm using other cables.....(there are many...how do I recognize the right one ? )
Will report back with the proper one, but I seriously believe that mine are fine.
Besides this, what would be your next guess ?
faiv said:
I tried unlocking again already, but I must admit that you got me with the last one. I'm using other cables.....(there are many...how do I recognize the right one ? )
Will report back with the proper one, but I seriously believe that mine are fine.
Besides this, what would be your next guess ?
Click to expand...
Click to collapse
ok we need to go step by step.
Check the shape of the cable maybe you'll get lucky. EBAY if not buy one. they are very cheap.
2nd in hboot try to enter recovery, if still error i need to know what it does, ei: black screen, red letters, etc.
kativiti said:
ok we need to go step by step.
Check the shape of the cable maybe you'll get lucky. EBAY if not buy one. they are very cheap.
2nd in hboot try to enter recovery, if still error i need to know what it does, ei: black screen, red letters, etc.
Click to expand...
Click to collapse
I'll tell you what it does, It stucks on red mark page and then black screen. So what is the problem ? If you don't answer my topic I write from another one !
blu3sm4n said:
I'll tell you what it does, It stucks on red mark page and then black screen. So what is the problem ? If you don't answer my topic I write from another one !
Click to expand...
Click to collapse
ok. so you dont have a recovery installed or its corrupted.
please be patience as every case its different and it takes trial and error until we figure out.
1-type command fastboot erase cache
2- flash stock recovery
3-relock oem. fastboot oem lock
in HBOOT enter recovery and erase phone. (NOTE: to enter recovery you need to press power+vol- after the red triangular)
4- get new token to unlock BOOTLOADER
5 -flash TWRP
all this because you need stock recovery to properly unlock bootloader.
kativiti said:
ok. so you dont have a recovery installed or its corrupted.
please be patience as every case its different and it takes trial and error until we figure out.
1-type command fastboot erase cache
2- flash stock recovery
3-relock oem. fastboot oem lock
in HBOOT enter recovery and erase phone. (NOTE: to enter recovery you need to press power+vol- after the red triangular)
4- get new token to unlock BOOTLOADER
5 -flash TWRP
all this because you need stock recovery to properly unlock bootloader.
Click to expand...
Click to collapse
Thanks for your help, first of all I can not unlock with Htcdev my bootloader. It is still locked. When I try to unlock and type unlock_code.bin, it asks me yes or no and I choose yes, it reboots and stucks on the logo screen again. I reboot again with volume down + power and see it is still "locked" .
When I try to flash stock recovery I type the flash recovery code and I get this message "writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)".. So Don't know what to do. I can not unlock, I can not flash recovery and I can not flash any stock rom because my main is : 2.19.401.2. So if I want to flash 2.18.401.3 RUU it says me your os is older. I am desperate I hope you can help dude. Thanks
blu3sm4n said:
Thanks for your help, first of all I can not unlock with Htcdev my bootloader. It is still locked. When I try to unlock and type unlock_code.bin, it asks me yes or no and I choose yes, it reboots and stucks on the logo screen again. I reboot again with volume down + power and see it is still "locked" .
When I try to flash stock recovery I type the flash recovery code and I get this message "writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)".. So Don't know what to do. I can not unlock, I can not flash recovery and I can not flash any stock rom because my main is : 2.19.401.2. So if I want to flash 2.18.401.3 RUU it says me your os is older. I am desperate I hope you can help dude. Thanks
Click to expand...
Click to collapse
ok so now you saying its LOCKED?
can yo send a hboot pic?
before trying next step..do you have an sdcard inserted in phone? if so remove and restart phone(corrupted sdcard will freeze phone logo)
if still stuck in logo try next step, if LOCKED
download RUU
- RENAME THE RUU FILE TO 0P8BIMG.zip AND PLACE IN THE ROOT OF SD CARD
- SWITCH OFF DEVICE
- HOLD VOL DOWN AND POWER KEY
- SOON AS DEVICE ENTER BOOT LOADERS IT WILL START READING THE PLACED FILE AND FLASHING SHOULD START SOON.
kativiti said:
ok so now you saying its LOCKED?
can yo send a hboot pic?
before trying next step..do you have an sdcard inserted in phone? if so remove and restart phone(corrupted sdcard will freeze phone logo)
if still stuck in logo try next step, if LOCKED
download RUU
- RENAME THE RUU FILE TO 0P8BIMG.zip AND PLACE IN THE ROOT OF SD CARD
- SWITCH OFF DEVICE
- HOLD VOL DOWN AND POWER KEY
- SOON AS DEVICE ENTER BOOT LOADERS IT WILL START READING THE PLACED FILE AND FLASHING SHOULD START SOON.
Click to expand...
Click to collapse
Yes it is LOCKED. I add HBOOT pic as atached, I tried to flash RUU but it says me "your main version is older " so i can not flash 2.18.401.3 RUU. I found this one (2.19.401.2_boot_system_2015-09-21--20-48-04_KOT49H.zip )and tried to flash but it didn't work (on boot menu it says no image found)
blu3sm4n said:
Yes it is LOCKED. I add HBOOT pic as atached, I tried to flash RUU but it says me "your main version is older " so i can not flash 2.18.401.3 RUU. I found this one (2.19.401.2_boot_system_2015-09-21--20-48-04_KOT49H.zip )and tried to flash but it didn't work (on boot menu it says no image found)
Click to expand...
Click to collapse
thx for the picture.
you hboot shows that nothing has been done to the phone. so it was NEVER unlocked as stated in original post.
At this point im gonna suggest get your self an original usb cable because the one you using its no good. its giving you wrong info and it seems some get to the phone but corrupted and thats why unlock fails.
im trying to create a new updated RUU but might take some time.
please get OTA cable and try to unlock
You are right, it is never unlocked as I told you before. My cable is original itselfs cable. My phone is never unlocked, never rooted and never made s-off. So what do you suggest now ?
HTC One_M8 cihazımdan Tapatalk kullanılarak gönderildi
blu3sm4n said:
You are right, it is never unlocked as I told you before. My cable is original itselfs cable. My phone is never unlocked, never rooted and never made s-off. So what do you suggest now ?
HTC One_M8 cihazımdan Tapatalk kullanılarak gönderildi
Click to expand...
Click to collapse
while i try to compile an ruu, try to unlock it.
Start over from scratch. get new token, this time choose "all other devices" in Dev HTC.
after clicking "yes" Wait at least 10 minutes before stress out.
let me know
Ok I'll try and let you know
HTC One_M8 cihazımdan Tapatalk kullanılarak gönderildi
kativiti said:
while i try to compile an ruu, try to unlock it.
Start over from scratch. get new token, this time choose "all other devices" in Dev HTC.
after clicking "yes" Wait at least 10 minutes before stress out.
let me know
Click to expand...
Click to collapse
I did exactly what you did. I got new token and choose "all supported other devices" in HTCdev. I took pictures of every step. It didn't work again after 3rd picture If I press volume up + power, it says "Device CW install : can't mount /data" and goes black screen and charging. If i don't press anything it goes black screen again and then chargin again as you can see on the 5th picture. So I can not unlock
By the way, If I choose recovery or factory reset on bootloader menu, I get the same result. (2nd, 3rd, 4th and 5th pictures).
blu3sm4n said:
I did exactly what you did. I got new token and choose "all supported other devices" in HTCdev. I took pictures of every step. It didn't work again after 3rd picture If I press volume up + power, it says "Device CW install : can't mount /data" and goes black screen and charging. If i don't press anything it goes black screen again and then chargin again as you can see on the 5th picture. So I can not unlock
By the way, If I choose recovery or factory reset on bootloader menu, I get the same result. (2nd, 3rd, 4th and 5th pictures).
Click to expand...
Click to collapse
1- in hboot enter recovery
when red warning shows, press power+vol up to enter recovery.
wipe data and reboot.
if recovery fails flash it
2-put this file in sdcard and update.
in hboot enter recovery, when red warning shows, press power+vol up to enter recovery.
wipe data and reboot.
kativiti said:
1- in hboot enter recovery
when red warning shows, press power+vol up to enter recovery.
wipe data and reboot.
if recovery fails flash it
2-put this file in sdcard and update.
in hboot enter recovery, when red warning shows, press power+vol up to enter recovery.
wipe data and reboot.
Click to expand...
Click to collapse
in hboot when I try to enter recovery, red warning comes and pressing power+vol up, it says "device cw install:cant mount/data" and then black screen.
I tried second step and added your file into sdcard and update. it says press power button. After that white htc screen is coming. It is waiting since 15 minutes but still nothing and still white screen [emoji21]
HTC One_M8 cihazımdan Tapatalk kullanılarak gönderildi
Sorry but it seems I'm unable to help you.
The picture shows green letters behind the red ones. It means the flashing fail, maybe it rejected the recovery or because its locked.
Either way your problem is, your system and recovery are corrupted.
My advice is contact HTC and send for repair. They usually don't charge you.
Ok dude thanks a lot. I'll contact HTC, i hope they can help ?
HTC One_M8 cihazımdan Tapatalk kullanılarak gönderildi

Categories

Resources