I got an M9. Wanted to root it to remove bloatware. Everything was going fine until I flashed supersu zip through TWRP. I didn't let TWRP install supersu as per instructions but I ran into the bootloop issue and decided to just go back to stock. Well I made a noob mistake and relocked the bootloader. Now the phone fails to enter recovery and when I reboot, it boots directly into the bootloader. I've been researching for hours and hours trying to find a resolution to just flash the stock RUU but when I run the file it comes up with the error no device is attached. The phone shows up in my device manager just fine but won't connect to ADB or when I tried running the RUU exe even that said there were no devices attached Also my phone is now not able to be found in adb or fastboot. If you could lend any assistance as to what I might be able to do just to even get it back to stock I would greatly appreciate it.
It's a T-Mobile HTC M9
bootloader is showing relocked.
S-On
Thanks for any help.
Update. I tried using Squabbi M9 toolkit but again the same issue with no devices attached. I'm guessing it has to do with usb debugging not being enabled? I'm not sure. It was enabled when I started the whole process but now that I can't boot into the phone itself I can't check anything. If anyone could offer at least a little assistance I would greatly appreciate it.
Related
I feel like I have used up all my resources on trying to get my Sprint HTC One back to stock.
Last night I was able to unlock it with no trouble. I didn't realize this would wipe out all my media as well. (not the issue)
So I was going to go and install Benny's Cleanrom and I used Superwipe to clear all the cache and everything that was being restored from the back up. I flashed the Superwipe Rom and it seemed to have gotten the job done, but it also wiped out my OS.
So now I have been stuck with the ability of accessing bootloader and recovery, I am using TWRP right now. None of my pc's recognize my phone when I try to mount it. The phone also shows errors when I try to do so, coming up stating that it cannot mount anything except usb otg. I don't have a USB OTG cable right to use, so that option is still out the window.
I have tried this method
I have tried this method multiple times but ADB was not working. http://forum.xda-developers.com/showthread.php?t=2317989
I have tried the Fastboot method, which had me relocking the phone and running the ruu. Though since I am on the latest version 1.3, the 1.2.9 RUU I was trying to use kept on failing. When doing it through Hasoon's AIO tool it seems that the ruu works when I flash the ruu zip. Though running it the first time it would show up that it failed, but when I re-flash it the second time on the cmd line it shows successful though on the phone the green bar never completes it and it stays at like 95% and doesn't complete the install on the phone.
If someone knows how to get my phone back to stock I would be very appreciative. I am new to rooting on the HTC One, I previously rooted my Evo 3D and my girls SG2.
If someone wants to help me out with team viewer, I will gladly allow anyone to assist me in that matter. I am just hoping that this can be resolved.
Now I see when I type ADB devices in cmd, it shows FA33ZS907479 recovery. I don't know if this has any relevance in that it sees the TWRP recovery.
BiGsMiLeSKyLe said:
I feel like I have used up all my resources on trying to get my Sprint HTC One back to stock.
Last night I was able to unlock it with no trouble. I didn't realize this would wipe out all my media as well. (not the issue)
So I was going to go and install Benny's Cleanrom and I used Superwipe to clear all the cache and everything that was being restored from the back up. I flashed the Superwipe Rom and it seemed to have gotten the job done, but it also wiped out my OS.
So now I have been stuck with the ability of accessing bootloader and recovery, I am using TWRP right now. None of my pc's recognize my phone when I try to mount it. The phone also shows errors when I try to do so, coming up stating that it cannot mount anything except usb otg. I don't have a USB OTG cable right to use, so that option is still out the window.
I have tried this method
I have tried this method multiple times but ADB was not working. http://forum.xda-developers.com/showthread.php?t=2317989
I have tried the Fastboot method, which had me relocking the phone and running the ruu. Though since I am on the latest version 1.3, the 1.2.9 RUU I was trying to use kept on failing. When doing it through Hasoon's AIO tool it seems that the ruu works when I flash the ruu zip. Though running it the first time it would show up that it failed, but when I re-flash it the second time on the cmd line it shows successful though on the phone the green bar never completes it and it stays at like 95% and doesn't complete the install on the phone.
If someone knows how to get my phone back to stock I would be very appreciative. I am new to rooting on the HTC One, I previously rooted my Evo 3D and my girls SG2.
If someone wants to help me out with team viewer, I will gladly allow anyone to assist me in that matter. I am just hoping that this can be resolved.
Click to expand...
Click to collapse
BiGsMiLeSKyLe said:
Now I see when I type ADB devices in cmd, it shows FA33ZS907479 recovery. I don't know if this has any relevance in that it sees the TWRP recovery.
Click to expand...
Click to collapse
Check pm :thumbup:
Sent from my HTCONE using xda app-developers app
I need help too
bigdaddy619 said:
Check pm :thumbup:
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
Im having the same problem I have nothing on my phone and adb sideload wont work and I also tried the RUU and I have the .31 version so i can't use it either
rj54271 said:
Im having the same problem I have nothing on my phone and adb sideload wont work and I also tried the RUU and I have the .31 version so i can't use it either
Click to expand...
Click to collapse
I work weird hours so if you can wait and I'll help or you can try to do it yourself look here Q21
Hi,
I had unlocked boot loader through HTCdev on latest GB stock ROM. So, obviously I was S-ON.
Meanwhile, I tried many ROMs but manually flashing boot image in hastboot.
I had following status of last running mobile when I tried to get S-OFF
Bootloader status: unlocked
S-ON
HBOOT 2.00.0000
Recovery: CWM
ROM: CynovivoX (JB 4.1.2)
Yesterday, I tried to get S-off by downgrading as per following thread
http://forum.xda-developers.com/showthread.php?t=1705913
There were lots of error while script was running, but one I remember was related to goldcard.
While running RUU, It goes well till I find something Error 131, Customer ID related and than exit.
After trying script and RUU many times, my status is
Bootloader status: Relocked
S-ON
HBOOT 2.00.0000
Recovery: ? (can't see or access anymore)
ROM: -
when running fastboot devices, my device is appearing
but in adb devices, nothing there
So, is there still any possibility to recover from this bricked state?
Desperately looking for expert help as I am not developer but somehow....tried this thinking would not be that difficult business....so help.
Try running the latest RUU and restarting everything over. Make sure to pick the right RUU for your region. The latest build number should be 4.14.XXXXX...
Also, in fastboot, your device isn't supposed to be visible with command of adb devices.
Another thing u could try is to unlock the bootloader again and see if u can access recovery again. Adb works in recovery
Sent from the head of the Hammer
If you can get into fastboot but don't have a recovery installed, can't you just flash a new recovery? E.g. grab clockworkmod, connect your phone to your computer via usb and:
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-vivo.img
(obviously replace above code with actual name of .img file)
err this might be stupid, but click on bootloader > recovery.
Looks like you are already in a sub menu when you boot the bootloader.
The error while downgrading is related to you not relocking your phone before downgrading. Always relock before downgrading with an RUU.
Sent from my Nexus 5
Thanks all guys.
But problem fixed. I have unlocked the bootloader again through htcdev and it worked.
Now let me share issue for all other nondevelopers like me who may also face such issue...
runme script is suppose to push some files through adb commands and then reboot to fastboot mode to lock bootloader.
I had adb drivers installed as I got prompt from statusbar.
However still, while running downgrade script (runme), phone was not detected in adb mode and hence no file was pushed to phone. After reboot, phone detected in fastboot and OEM successfully relocked.
I am really surprised why device not found error not appeared and script not stopped. Later I came to know this by running the script without connecting phone and it ran with asking Q&A with found device, and also reading log file.
Then I ran RUU who wiped everything.
So, my device left without any ROM and with OEM locked. I can't access or install recover, ROM etc and RUU was having goldcard error.
Somehow tried to unlock again through token provided by HTCDev earlier (around 2 years back).
And thing become normal and in my control.
My advise: always check "adb devices" before running the script as I found script is misleading of found device and finally locking device. And if such thing happen, easiest one is to get in unlocked from HTCDev and restart whole process.
RmatriX1218 said:
Thanks all guys.
But problem fixed. I have unlocked the bootloader again through htcdev and it worked.
Now let me share issue for all other nondevelopers like me who may also face such issue...
runme script is suppose to push some files through adb commands and then reboot to fastboot mode to lock bootloader.
I had adb drivers installed as I got prompt from statusbar.
However still, while running downgrade script (runme), phone was not detected in adb mode and hence no file was pushed to phone. After reboot, phone detected in fastboot and OEM successfully relocked.
I am really surprised why device not found error not appeared and script not stopped. Later I came to know this by running the script without connecting phone and it ran with asking Q&A with found device, and also reading log file.
Then I ran RUU who wiped everything.
So, my device left without any ROM and with OEM locked. I can't access or install recover, ROM etc and RUU was having goldcard error.
Somehow tried to unlock again through token provided by HTCDev earlier (around 2 years back).
And thing become normal and in my control.
My advise: always check "adb devices" before running the script as I found script is misleading of found device and finally locking device. And if such thing happen, easiest one is to get in unlocked from HTCDev and restart whole process.
Click to expand...
Click to collapse
From what I'm reading, I'm getting a much clearer image of what happened. I believe your problem to be just driver errors...
The script itself is supposed to run regardless of whether phone is properly connected with proper drivers and whatnot. After all, it's just a set of commands in cmd.
But seeing as you ONLY got Error 131, you could have solved this by simply creating a goldcard.
072665995 said:
From what I'm reading, I'm getting a much clearer image of what happened. I believe your problem to be just driver errors...
The script itself is supposed to run regardless of whether phone is properly connected with proper drivers and whatnot. After all, it's just a set of commands in cmd.
But seeing as you ONLY got Error 131, you could have solved this by simply creating a goldcard.
Click to expand...
Click to collapse
Phone was connected in adb mode. This I can say by checking notifications in android and statusbar prompt in windows 7. While running script only, something got wrong getting adb mode not detected.
Anyway, Goldcard was also in my next line of action, but not sure even after creating Goldcard, I may stuck as version-main was not downgraded to 2. However, tried and got resolved with much simpler effort of unlocking through htcdev.
May be, I am also not that competent to understand developing world and only good enough to simply flash ROMs and updates as per instructions.
Anyway, thanks.
Seeking some help here.
I am from Singapore and using the HTC international version.
It is (was?) rooted but the camera was giving problems and I sent it in for servicing. Even though the hardware fault has nothing to do with the rooting, I was asked to unroot it into stock and they will service it for me.
Ok, fair enough. So this is what I did.
1. I relocked the bootloader using Fastboot
2. Tried to run the RUU which and it didn't run. I used
RUU_M7_UL_JB_50_hTC_Asia_WWE_1.26.707.5_Radio_4A.13.3231.20_10.30.1131.05_release_309365_signed_2_4.exe
3. Realised that I need to turn S-off before the RUU may work, I tried running the Rumrunner but couldn't get it to work.
4. Rumrunner says I need to check USBdebugging but since I couldn't get the phone running, I couldn't have checked that.
5. I decided to just unlock the bootloader and install a custom rom (was using CM11). Tried to push the Zip by ADB but it fails. The computer recognises the device but after pushing the file, the TWRP screen reads ADB Sideload Complete Failed
6. Possibly unrelated, but I tried to do a wipe on TWRP, it reads Factory Reset Complete Failed
So now I can stuck with a bootloop and can't seem to get anything installed or restored.
Would love to know what should I do in such a situation. Thanks guys.
Heya!
Totally new to all of this, so please be gentle. My M9 is now bootlooping and the past hour of research hasn't helped me.
I've just done the following with my Tmobile marshmallow M9:
1) Used HTC's dev tools to unlock the bootloader
2) Flashed twrp-2.8.7.1_CPTB-B1-hima.img using fastboot
3) Immediately after flashed BETA-SuperSU-v2.66-20160103015024.zip using twrp
4) Backed up everything using twrp
My phone is now boot looping. I tried clearing cache/dalvik/data with no luck. Honestly, I'm fine with either loading a stock rom or going to viper like I originally intended, but I don't know how - I don't have either of those on my SD card and I know that I need to get them off of my computer onto the phone, but ADB and my device manager don't see the phone when I'm in TWRP. When I'm in the bootloader, I see "My HTC" in device manager and HTC sync picks up like it sees the phone.
I just want a working phone again. I hear that SuperSU 2.65 is probably more stable, but I don't care whether I root and viper or go back to stock as long as the phone works. I would have figured driver issues if not for the perfectly functional/device manager viewable fastboot. Without ADB seeing the device in twrp, I can't sideload, push files or mount storage to get a new rom on there to fix it. I'm not even sure whether it's TWRP or the SuperSU flash that boot looped me, though I figured that by clearing /data/dalvik/cache I killed SuperSU so it might be twrp.
All solutions I've found so far assume that ADB is working/the device can be seen or assume that simple driver reinstalls will fix the problem, but I haven't had any luck with that so far even though I've tried uninstalling/reinstalling drivers a few times.
Any ideas? Please help me - I'm stumped!
Relock bootloader and run an RUU.
HTC One M9
Jtsessions said:
Heya!
Totally new to all of this, so please be gentle. My M9 is now bootlooping and the past hour of research hasn't helped me.
I've just done the following with my Tmobile marshmallow M9:
1) Used HTC's dev tools to unlock the bootloader
2) Flashed twrp-2.8.7.1_CPTB-B1-hima.img using fastboot
3) Immediately after flashed BETA-SuperSU-v2.66-20160103015024.zip using twrp
4) Backed up everything using twrp
My phone is now boot looping. I tried clearing cache/dalvik/data with no luck. Honestly, I'm fine with either loading a stock rom or going to viper like I originally intended, but I don't know how - I don't have either of those on my SD card and I know that I need to get them off of my computer onto the phone, but ADB and my device manager don't see the phone when I'm in TWRP. When I'm in the bootloader, I see "My HTC" in device manager and HTC sync picks up like it sees the phone.
I just want a working phone again. I hear that SuperSU 2.65 is probably more stable, but I don't care whether I root and viper or go back to stock as long as the phone works. I would have figured driver issues if not for the perfectly functional/device manager viewable fastboot. Without ADB seeing the device in twrp, I can't sideload, push files or mount storage to get a new rom on there to fix it. I'm not even sure whether it's TWRP or the SuperSU flash that boot looped me, though I figured that by clearing /data/dalvik/cache I killed SuperSU so it might be twrp.
All solutions I've found so far assume that ADB is working/the device can be seen or assume that simple driver reinstalls will fix the problem, but I haven't had any luck with that so far even though I've tried uninstalling/reinstalling drivers a few times.
Any ideas? Please help me - I'm stumped!
Click to expand...
Click to collapse
Go back to TWRP and flash the stable SuperSU 2.65. Beta bootlooped for me too and then I went back to TWRP and flashed 2.65 and it was fine.
When you're in TWRP you should be able to connect the device to your computer and copy the 2.65 to phone storage and then be able to flash it.
Hello,
I have a 626s that is recognized in its normal boot state, but not in Download Mode. Fastboot gives "Waiting for Device"; ADB gives "Device Not Found"; and HTC Sync gives "No device connected."
The phone does have an unlocked bootloader and USB debugging is turned on.
The phone's history:
Bootloader unlocked, TWRP flashed, SuperSU installed.
Root uninstalled by SuperSU app. (It asks if I want the original bootloader [?] flashed. Clicked "No". This is where problems started.)
Made a backup of my phone through TWRP, in which it refuses to backup the System partition in any way.
Decided to revert phone to stock through RUU.
Need to replace misc.img to do so.
ADB cannot find the device.
And this is where I'm stuck. I don't know if any of what I just listed is what is causing the main problem, but it could help. If anyone knows of a way I could revert the phone to the stock ROM any easier, it would be appreciated. I don't care about loss of any data.
Thanks.
Eh, I explained this to another guy earlier so I'll just dumb it down a bit.
Download the RUU for you specific carrier and such from the HTC site.
Go through the .exe until it prompts the install to the phone, but don't start it.
Go to %temp% in Windows Explorer and find rom.zip
Rename the .zip to "0PM9IMG.zip" and place it in the root of your external sd.
From here you can do as you please with it. I used the bootloader to install it. :laugh: