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?
Related
I managed to get myself stuck in a locked bootloader with no way to get back into android or flash a rom from recovery. Would I be able to flashboot a .img file from being bootloader locked or will I have to run the RUU.
I am only saying this because I can't get windows 8 to find my phone even with the drivers installed. I am guessing it has something to do with being USB 3.0 and on a MBP. The only way I can seem to get fastboot to work is in OS X, Wine hasn't been able to run past the initial loading screen so that idea was shot. Any ideas would be greatly appreciated.
Unlock the bootloader..if memory serves me correctly you only need to be in fastboot for that. Once you're done with that, flash your corresponding RUU (since you don't have s-off and supercid).
Or you could flash recovery by putting it in the same folder as adb and typing "fastboot flash recovery recovery.img" and go from there.
And lastly just factory reset from bootloader..that could also work
Sent from my HTC One using xda app-developers app
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?
Lately my phone has been rebooting itself quite a bit. It seems to be getting progressively worse to the point where if I open any app for more than a minute or two then my phone will reboot. I've tried uninstalling quite a few third party apps but that didn't do the trick. Whenever I try to do a hard reset (whether it's through settings or the HBOOT menu) the phone will shut down and then instead of getting the picture of a phone with the green thing in the middle and a status bar below that indicating the phone is resetting, I get a picture of a phone with a red symbol similar to a hazard sign that will last for about 30 seconds then the phone just boots back up to my home screen. I had put an incorrect custom ROM on this phone about 5-6 months ago but I was able to get the stock Sprint ROM back on the phone and relock the boot loader and the phone functioned fine ever since up until about a week ago when it started rebooting randomly. I have a feeling this may be part of the reason why the factory reset is not working. Does anyone have any ideas on how to proceed? Can I do a factory reset by pushing a ROM to the phone through my computer?
If u are s-off then I suggest u download the ruu and run it. If s-off all u have to do is go to hboot and select fast boot and run the program it will reset the phone back to whatever software version it is for the ruu. If your not s-off you will need to get the ruu that matches your firmware. That should fix your troubles if not then you have something faulty with the hardware itself
Sent from my iPad using Tapatalk
Ok I am S-ON and here is what I am trying to do. I downloaded the RUU that matches my phone current software from the link below and placed the file in the platform-tools folder after renaming it. When I run the fastboot oem rebootRUU command in the cmd prompt, my phone just reboots rather than booting to the black screen with the silver HTC logo. Any suggestions on how to proceed?
http://forum.xda-developers.com/showthread.php?t=2687690
Also, my bootloader shows that it is relocked
coppertop4646 said:
Ok I am S-ON and here is what I am trying to do. I downloaded the RUU that matches my phone current software from the link below and placed the file in the platform-tools folder after renaming it. When I run the fastboot oem rebootRUU command in the cmd prompt, my phone just reboots rather than booting to the black screen with the silver HTC logo. Any suggestions on how to proceed?
http://forum.xda-developers.com/showthread.php?t=2687690
Also, my bootloader shows that it is relocked
Click to expand...
Click to collapse
That is a firmware flashing that will do nothing for u. Here is a link to the newest RUU I can find http://forum.xda-developers.com/showthread.php?t=2658910
Sent from my One using Tapatalk
luigi311 said:
That is a firmware flashing that will do nothing for u. Here is a link to the newest RUU I can find http://forum.xda-developers.com/showthread.php?t=2658910
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Ok I tried that RUU yesterday and couldn't seem to get anywhere because I kept getting error 170 (tried updating drivers, installing HTC sync, etc). Tried again today and got error 170 again, so then I went in my bootloader, then fastboot, connected USB cable, fastboot usb. I then ran the RUU and it said it was going to update my phone. The status bar then said "Waiting for bootloader" and my phone just rebooted itself to the home screen and then I got like error 171 or something (another USB error). I'm kind of running out of ideas at this point. I believe something is wrong with my recovery or I have some sort of bug because I attempted to flash a custom recovery today (TWRP) but when I unlocked my bootloader, I restarted the phone and entered my bootloader again but it still said relocked (even though the prompt on my phone came up giving me the warnings asking if I was sure I wanted to unlock the bootloader) so when I run the command fastboot flash recovery twrp.img I get something along the lines of can't read twrp.img or can't open twrp.img (yes I made sure the file is in the same folder that I am running the adb out of). Willing to try any recommendations at this point because my phone is pretty useless as of right now because it restarts every couple minutes. HTC wants $150 to fix it which I told them I'm not willing to pay, rather buy a new phone.
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.
I have a verizon htc one m7 that will boot to the verizon logo then restart. i can access the bootload/fastboot and recovery. when i issue the fastboot command of fastboot oem rebootRUU the command completes and phone goes black then the green htc logo appears and continues to try and boot normally. does anybody have any suggestions on how to get to the RUU mode? bootloader is locked and s-on is active. this is a completly stock phone.
I think you need unlocked bootloader (but I'm not sure). So try unlocking it (keep in mind that you'll loose the guarantee)
suchauser said:
I think you need unlocked bootloader (but I'm not sure). So try unlocking it (keep in mind that you'll loose the guarantee)
Click to expand...
Click to collapse
1- no need for an unlocked bootloader
2- he's on Verizon so he can't use HTCdev to unlock, and sunshine won't work without a booted phone
idragoncell said:
I have a verizon htc one m7 that will boot to the verizon logo then restart. i can access the bootload/fastboot and recovery. when i issue the fastboot command of fastboot oem rebootRUU the command completes and phone goes black then the green htc logo appears and continues to try and boot normally. does anybody have any suggestions on how to get to the RUU mode? bootloader is locked and s-on is active. this is a completly stock phone.
Click to expand...
Click to collapse
how about some background info, how you ended in this situation... if it's a complete stock phone (so you weren't messing around with flashing things), then it could very well be a hardware problem... but the above info isnt enough, you need to provide more details of how this came to be
it's also good practice to copy/paste the entire command prompt output, so we can take a look of what was typed and what the output generated
Customer bought the phone too me in a boot loop state.. he claims he was using it and it just went black then came back on but never fully booted kept restarting at the verizon logo. htc told him to try and factory reset the phone but that was a no go as well. i have tried a RUU utility and when the program says rebooting to bootloader it doesnt go into bootloader just trys to boot up normally. the same thing happens when i attempt to put it in RUU mode it just reboots and trys to boot normally.
idragoncell said:
Customer bought the phone too me in a boot loop state.. he claims he was using it and it just went black then came back on but never fully booted kept restarting at the verizon logo. htc told him to try and factory reset the phone but that was a no go as well. i have tried a RUU utility and when the program says rebooting to bootloader it doesnt go into bootloader just trys to boot up normally. the same thing happens when i attempt to put it in RUU mode it just reboots and trys to boot normally.
Click to expand...
Click to collapse
sorry, dont get me wrong, but since i've been back (for a few hours), people are ... let's just say, not very forthcoming
what would help:
a screenshot of bootloader
a "fastboot getvar all" (excluding the last 6 digits of IMEI, MEID, and serial number... those need not be shared)
possibly a fastboot oem last_dmesg
though if the phone is completely stock, never been tampered with, then you have a high chance it's a hardware problem
http://imgur.com/73JGfka
https://goo.gl/photos/hkdxnmNtB7ctd2XA9
http://imgur.com/El0SNkj
idragoncell said:
http://imgur.com/73JGfka
https://goo.gl/photos/hkdxnmNtB7ctd2XA9
http://imgur.com/El0SNkj
Click to expand...
Click to collapse
thanks for the details, nothing "looks" wrong from those, but the "fastboot oem last_dmesg" has to be done after attempting to flash something, after a (non flashing reboot) it will just be empty.
couldn't find much, but have you tried this RUU:
http://forum.xda-developers.com/verizon-htc-one/help/exe-ruu-vzw-m7-4-4-3-s-users-t2919442
EDIT:
1- RUU.EXE will leave a log (before you close the .exe), in c:\ruu_log\.......txt
2- command prompt copy/paste is preferred to a screenshot, since it's much easier to read
good luck