I flashed ViperONE which completed successfully. On initial boot though I am stuck on the bootloader menu. If I try to enter recovery the screen goes black and returns to the bootloader. I can get to the fastboot screen but my computer will not detect the device fastboot only says "waiting for device". fastboot menu does not change to fastboot usb. I am assuming since it was a new rom install that debugging is NOT turned on. Doing a factory reset through the bootloader did not help. My bootloader is unlocked and I am S-Off. Any helpers?
EDIT: Upon more research the fact that my HBOOT is 1.44 and not 1.55 as well as my computer running windows 8.1 I might have some troubles here. Is there hope for an RUU?
Related
I've got an HTC One with Sprint running 4.2.2 (3.05.651.6). I unlocked the bootloader and rooted it using qbking77's tutorial. I haven't flashed any ROMs on my phone.
Everything has been working fine until yesterday. I took my phone out of my pocket and it was dead. I charged it up and when I turned it on it was stuck in a boot loop on the htc screen. I can get into bootloader fine and fast boot usb shows up on my phone when connected to the computer, but I can't access my TWRP recovery. It shows TeamWin screen then boot loops again.
I have re flashed the recovery and erased the cache. I have also tried to lock the bootloader using Hasoon2000's HTC One All-In-One Toolkit and by connecting to fastboot and typing in "fast boot oem lock. For the toolkit i get device not found and an error and when using the command prompt I get FAILED (status read failed (No such file or directory)). I think its possible my usb debugging may be off since I can't find any devices using adb but my pdanet can find my phone (which needs usb debugging) so I'm not sure.
If I can get it locked, I can use RUU to get back to stock.
I'm running out of options. I'm thinking I can still flash a non-stock rom to get the phone running again and then relock and go to stock. Any ideas on what my issue is and how to fix it? Any input is appreciated.
Hi all, I was flashing a downloaded RUU after trying to going back to stock, then I got an error.
Now I'm on RUU mode (that seems to be fastboot, but with HTC flashing image on screen). Fastboot commands works. I managed to unlock it again via HTCUnlock so now I can flash unsigned files.
However, I can't get past the RUU mode: it doesn't boot on classic bootloader or in recovery.
Any idea?
I took some photos but my connection is very slow.
If I remember right there was a fastboot command to exit RUU mode, but couldn't find anything about that right now.
EDIT: managed to boot with "fastboot oem boot". But when I reboot, it comes back in RUU mode. Bootloader and fastboot still seems to be unavaliable :\
Solved, I'll write an article about that
Here is it, in case someone finds in the same situation: http://www.francescocrema.it/telefonia/unbrick-htc-one-htc-black-screen-with-warning-signs-on-edges/
I have a question now, just to understand what happened: if my original phone's CID is XXX, if I set it to YYY, then install a RUU for YYY, lock the bootloader and S-ON, should that work?
If not, how can the phone know that it's original CID is not YYY?
So I bought this HTC One M7, the guy claims its soft bricked and hes not able to fix it because hes technically challenged. So I take it home boot it up, its stuck in a boot loop so I boot it into fastboot the bootloader is locked so I try to connect it to adb, no luck, there is no driver on this internet that I have found that will connect to adb. So I resort to fastboot, I "fastboot devices" and sure enough it connects (wicked), first I try to flash recovery, I try to boot recovery, I tried to update zip, no luck in flashing anything because I either get a signature fail or a "remote: not allowed" then I realize my bootloader is locked, I try to unlock it "fastboot oem unlock" and of course I get a "INFO [ERR] command error". I also tried to change my cid to 11111111 and no luck. I have actually tried everything I can think of I cant get s-off to work my recovery is stock as well so theres no possibility of OTG cable plus a usb. My fastboot will not flash anything in fastboot, I cant push any files to the phone, I cant connect to adb, I cant use my recovery. So what in the actual can I do? I think i'm f**ked.
Thank you in advance for anything you can help me with.
jonrogers61 said:
So I bought this HTC One M7, the guy claims its soft bricked and hes not able to fix it because hes technically challenged. So I take it home boot it up, its stuck in a boot loop so I boot it into fastboot the bootloader is locked so I try to connect it to adb, no luck, there is no driver on this internet that I have found that will connect to adb. So I resort to fastboot, I "fastboot devices" and sure enough it connects (wicked), first I try to flash recovery, I try to boot recovery, I tried to update zip, no luck in flashing anything because I either get a signature fail or a "remote: not allowed" then I realize my bootloader is locked, I try to unlock it "fastboot oem unlock" and of course I get a "INFO [ERR] command error". I also tried to change my cid to 11111111 and no luck. I have actually tried everything I can think of I cant get s-off to work my recovery is stock as well so theres no possibility of OTG cable plus a usb. My fastboot will not flash anything in fastboot, I cant push any files to the phone, I cant connect to adb, I cant use my recovery. So what in the actual can I do? I think i'm f**ked.
Thank you in advance for anything you can help me with.
Click to expand...
Click to collapse
You can't use adb unless you're booted to OS or custom recovery. Also you can't unlock bootloader with "fastboot oem unlock" unless your phone is GPE version. For Sense you need unlock token from htcdev. In order to flash anything, you need custom recovery, and you can flash it only if your bootloader is unlocked
donkeykong1 said:
You can't use adb unless you're booted to OS or custom recovery. Also you can't unlock bootloader with "fastboot oem unlock" unless your phone is GPE version. For Sense you need unlock token from htcdev. In order to flash anything, you need custom recovery, and you can flash it only if your bootloader is unlocked
Click to expand...
Click to collapse
I unlocked my htc with the unlocktoken from htc dev but it still says locked in bootloader. I can flash the unlock_code.bin but it does not restart nor does it come up with a message that says I would like to unlock bootloader etc.
jonrogers61 said:
I unlocked my htc with the unlocktoken from htc dev but it still says locked in bootloader. I can flash the unlock_code.bin but it does not restart nor does it come up with a message that says I would like to unlock bootloader etc.
Click to expand...
Click to collapse
can you post the output of "fastboot getvar all" (remove your imei and serialno). Sometimes, reflashing the stock firmware can solve some bootloader unlock problem but I need to know you getvar all before I can tell you which one you should flash.
Hi all,
Any help I can get would be greatly appreciated. I have a Sprint HTC One M7 that was previously rooted. Currently it is relocked with S-On, but at some point an OTA update was downloaded and now my phone keeps restarting itself and boots to this "android is upgrading..." screen. It keeps doing this loop over and over. It restarts itself, and then goes to this "android is upgrading..." I've spent hours in the forum this afternoon and I've tried numerous things and nothing seems to be working. Everything I've tried keeps giving me errors. At this point I would simply like to go back to the stock ROM and have a working phone. Can anyone help?
FYI...
I've tried using the .exe method from an RUU, but that isn't working because when it reboots to bootloader at the very beginning of the process my phone boots to android and I get the "android is upgrading..." message.
I've tried extracting the rom.zip and sideloading it, but I can't sideload because installing the TWRP.img recovery fails every time.
I've tried a factory reset and that fails. Again, I get the "android is upgrading..." loop.
Basically, everything I've done to run RUU fails because my phone reboots to android instead of rebooting to the bootloader, and everything I've tried to work around that problem fails.
I'm currently running 6.23.651.7 and I'm trying to flash 6.23.651.10.
Again, any help would be massively appreciated. I'm desperate...
johnnycr said:
I've tried extracting the rom.zip and sideloading it, but I can't sideload because installing the TWRP.img recovery fails every time.
Click to expand...
Click to collapse
You can't flash a rom.zip extracted frin a ruu.exe using TWRP, it must be flashed using fastboot with the phone booted in RUU mode.
Basically, everything I've done to run RUU fails because my phone reboots to android instead of rebooting to the bootloader
Click to expand...
Click to collapse
Holding power and volume down doesn't work? This should get you in bootloader mode. If your phone can't boot to a stable bootloader there is nothing you can do. Once in bootloader there are many options to unbrick your phone.
alray said:
You can't flash a rom.zip extracted frin a ruu.exe using TWRP, it must be flashed using fastboot with the phone booted in RUU mode.
Holding power and volume down doesn't work? This should get you in bootloader mode. If your phone can't boot to a stable bootloader there is nothing you can do. Once in bootloader there are many options to unbrick your phone.
Click to expand...
Click to collapse
I first tried flashing the rom.zip using fastboot, but when the phone is supposed to display the HTC logo screen my phone just reboots and goes back to the "android is upgrading..." page.
I can get into bootloader when I hold power and volume down, but I haven't been able to successfully do anything from there. I tried flashing TWRP so that I could attempt to sideload a ROM, but I got an error when flashing TWRP.img.
johnnycr said:
I first tried flashing the rom.zip using fastboot, but when the phone is supposed to display the HTC logo screen my phone just reboots and goes back to the "android is upgrading..." page.
I can get into bootloader when I hold power and volume down, but I haven't been able to successfully do anything from there. I tried flashing TWRP so that I could attempt to sideload a ROM, but I got an error when flashing TWRP.img.
Click to expand...
Click to collapse
What is the error when flashing twrp?
fastboot oem rebootRUU doesnt work?
Is your bootloader still relocked? If it is, you can't flash custom recovery. The only thing you can do is run RUU in that state
alray said:
What is the error when flashing twrp?
fastboot oem rebootRUU doesnt work?
Click to expand...
Click to collapse
Well, I was just going to try and do this again, but now my PC can't even find it when I run "fastboot devices." I have the SDK and ADB driver installed, so I don't know why it can't find it all of a sudden.
I can't install the RUU by running the .exe, because when I do and it gets to the "waiting for bootloader..." screen my phone reboots and loads android and goes to the "android is upgrading" screen. So I need to flash the RUU via fastboot, but now my PC isn't recognizing my device in CMD...
Okay... so I finally got adb and fastboot working again. When I run "fastboot oem rebootRUU" the phone reboots to Android and goes to the "android is upgrading..." screen.
Update: So... I was able to successfully use adb and fastboot to unlock my HTC One again. I then tried to flash a custom recovery via fastboot, but I kept getting "FAILED (remote: signature verify fail)". I tried flashing TWRP, CWM, and stock HTC recovery and got the same failed message for each one. I'm just trying to find a way to break this stupid boot loop... HELP!
Update: So, my phone even restarts itself when I boot into safe mode... not good. Can anyone help me out?
Hi I've a pixel5, it was reset to V11 software for compatibility with my son's medical device. Now with added security the app wont work because the bootlaoder is open. When I boot it say sits unlocked and to visit g.co/ABH
I've tried but cannot get it closed
When I go to fastboot I get the 'no command'.. on tring to flash it allows me to see the device and reboot the bootloader BUT then it will not respond to the cmd fastboot devices. when I try fastboot flashing lock it just says <waiting for device>
Any help? !
Billy
Try installing the usb driver https://developer.android.com/studio/run/win-usb
billyedit said:
Hi I've a pixel5, it was reset to V11 software for compatibility with my son's medical device. Now with added security the app wont work because the bootlaoder is open. When I boot it say sits unlocked and to visit g.co/ABH
I've tried but cannot get it closed
When I go to fastboot I get the 'no command'.. on tring to flash it allows me to see the device and reboot the bootloader BUT then it will not respond to the cmd fastboot devices. when I try fastboot flashing lock it just says <waiting for device>
Any help? !
Billy
Click to expand...
Click to collapse
I'm confused about "sits unlocked" and if this means you're stuck on the unlocked bootloader warning screen. If the phone hangs you're better off keeping the bootloader unlocked until that problem is sorted out. If it's starting, on the other hand...
Waiting for device means fastboot isn't communicating with the phone. Could be USB drivers. But if you flashed Android 11 from the same computer, drivers were working then, right?
In Developer options make sure USB debugging is enabled. While there, and while the bootloader is still unlocked, make sure OEM unlock is in the On position; it will flip back to Off when the bootloader is locked again.
Use Platform Tools 33.0.3 when trouble shooting USB to avoid trouble shooting Platform Tools 34.x.x.
As long as you get serial number output from commands adb devices and fastboot devices, fastboot flashing lock should work to re-lock the bootloader. Remember to finalize locking with the phone buttons.
Thank you both is was indeed the USB driver that needed the google update... All is well! thanks