I have an HTC Vivid that I had successfully installed a couple of different ROMs on in the past. Yesterday I attempted to install VJRaider ROM, it got stuck at HTC screen on initial start up. I allowed it to run for almost 30 minutes and checked what was happening with "adb logcat", I kept seeing something about an audio failure. I decided I would give up on this ROM and try Virtuous Inquisition ROM, but encountered the same issue and even allowed start up to run for nearly one hour. After these issues I thought I would go back completely stock using the RUU from HTC. I ran it and it produced an error because I had forgotten to relock my bootloader. Using the Vivid All In One Kit v2.2 by Hanson2000 I selected relock bootloader but it said cannot find the device. I then used command line to relock the bootloader but it said it could not lock bootloader (something like that). At this point I thought I would just restore my backup and attempt to boot into recovery. The phone shows:
*** RELOCKED ***
*** Security Warning ***
Obviously the All In One Kit or my command line efforts to relock the bootloader had worked.
This brings me to where I am stuck at now. When I select "BOOTLOADER" "RECOVERY" the phone just reboots back into FASTBOOT. I think no big deal, I can plug it into my computer, do some investigating and research, and figure this out. The phone will not recognize it is plugged into the computer and show HBOOT USB (or maybe it is FASTBOOT USB I can't remember what I should see) nor will my computer recognize the phone has been plugged in.
All of the posts I have read mention similar problems but the users have been able to get to recovery or flash the RUU to return to stock. Any help that can be provided would be greatly appreciated.
Have you tried any other cables or Ports on your computer? I recommend on desktop trying a port on back directly on the motherboard. Maybe even try a different computer? Also check to make sure some lint or something didn't get stuck in the USB port preventing a connection
Sent from my HTC PH39100 using xda premium
Tried on laptop running Linux and "FASTBOOT USB" appeared. Yay. Thanks for the suggestion, I even thought about doing that but talked myself out of it because I was using the same computer, same port, and same cable the whole time. Now to do my homework on how to fix my phone since selecting recovery just reboots the phone. Thanks again.
No problem glad i could be of help
Sent from my HTC PH39100 using xda premium
So I was really dumb and tried to factory reset my phone while I was on a custom rom and now am stuck in a boot loop. I have been googling around to try and figure out what to do but nothing seems to work. When I try and Hboot an RUU stock file it gets stuck at UserData. I also cannot get into recovery only Hboot.
I am relocked and S-On. Don't know what else to do. Is it beyond repair?
Ok when you run the ruu are you selecting fastboot in the hboot screen ? Does it say USB after fastboot when connected ?
Bigtjmc said:
Ok when you run the ruu are you selecting fastboot in the hboot screen ? Does it say USB after fastboot when connected ?
Click to expand...
Click to collapse
When i hold down power and volume down it goes to the Hboot screen and it automatically looks for the PH39IMG.zip file so no I am not running fastboot but when I do select fastboot it only says fastboot no USB (i do not have it plugged into PC btw).
When you select fastboot , then plug it in the pc and it should go USB , if not you need to install the drivers
If you need the drivers you dl htc sync manager , or dl the toolkit in the dev forum and install them that way .
Fastboot USB is showing up but HTC Sync is saying there are no devices connected, not sure if thats a problem.
Ok did you do this when you ran the ruu ?
brandork said:
Fastboot USB is showing up but HTC Sync is saying there are no devices connected, not sure if thats a problem.
Click to expand...
Click to collapse
HTC sync looks for devices that are powered on...just try and run the ruu..listen to bigtjmc
AND DON'T UNPLUG ONCE IT'S GOING, THE PROCESS TAKES A WHILE...
Sent from my HTC PH39100 using Tapatalk 2
Well I was actually extracting the RUU image from my PC's temp folder then placing it on my phone to allow Hboot to find it. I am now running the actual RUU software on my PC and it seems to be working. I will update when its finished. Thanks so much for your help.
Right on ,
Let us know what happens .
The ruu is stuck at 34%...I have it plugged in still not sure what to do from here
How long has it been stuck?
Don't unplug it...just let it sit...
Sent from my HTC PH39100 using Tapatalk 2
sorry guys I was in class and couldnt respond. so right now i went through the RUU recovery steps and it allowed me to re-do the RUU setup. I just redid it thinking my PC may have messed up but I am stuck at 34% again. Any suggestions for what I should do after I recover it again?
edit: forgot to mention that I left it for a few hours while in class and it took me to the recovery setup
Can you get into recovery when it sends you there ?
no I cannot get into recovery. All i can do is get into fastboot.
Right but what recovery setup you mentioned earlier ? Maybe you got a bad ruu download try and re dl it or try a different version.
Sorry the recovery I mentioned was a recovery process the RUU takes you through when an update fails. I also have tried about 4 different downloads to no avail. I have been using this file here
Ok , what Rom did you have on the phone ?
I couldnt tell you for sure I installed it pretty quickly after the ICS update was available. I want to say I installed one of the HTC Holiday or Raider ICS roms because that was available before the Vivid one. Once that was installed I rooted.
Ok one last thing and I will see what I can come up with , the ruu screen when it stopped at 34% what was it trying or waiting on ?
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
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.
I've followed all of the steps from this guide: http://forum.xda-developers.com/showpost.php?p=56938530&postcount=1
I've got to the end where I am running the code snippets to flash everything, but everything fails. The error stated is FAILED: remote failure. I am not sure if this is related to my developer options being turned off, but I think it might be.
Is there a way to turn developer options on while in fastboot mode or perhaps a way around this error? The reason I am stuck in the fastboot is because the boot image can't be validated, I am not at the fastboot by choice, haha.
No. If your recovery is still stock, flash the Android N Preview 1 OTA or an Android 6.0.1 OTA image from Google. One of those will restore your Nexus to operating condition, and from there you can try again. If your recovery is TWRP, flash a custom ROM.
Strephon Alkhalikoi said:
No. If your recovery is still stock, flash the Android N Preview 1 OTA or an Android 6.0.1 OTA image from Google. One of those will restore your Nexus to operating condition, and from there you can try again. If your recovery is TWRP, flash a custom ROM.
Click to expand...
Click to collapse
I apologize for my ignorance since this is all new to me, but could you explain a few things to me.
Is this what you're referring to when you say Android N Preview 1 OTA: 'https://developer.android.com/preview/download.html'
Secondly, in order to flash these, am I still following the steps I was before, or should I be following a new set of steps?
You don't need the N Preview anymore. Download your Android 6.0.1 image from the Google page and flash using the instructions given on that page.
I went to the page and followed the directions. Still doesn't work. The flash-all script reboots after the first two commands, which lock the phone. But even then, it is still giving the error FAILED:remote failure.
me too!
I seem to be having the exact same issue! i just bought a Nexus 6 online that wasn't booting, it would only show a green led when plugged in. so here I am doing everything I can think of to fix the issue but then I get hit with the "remote failure" when i try to oem unlock the bootloader! (and since the phone wont't boot i can't check the "unlock bootloader" box in the developer options) so yeah I am going to keep researching this but if anyone has any good ideas about to get around the bootloader being locked please jump right in.
anyways I may have deeper issues, the battery will not charge. i know this because when i load up the fastboot menu, which i have to do by holding the buttons while plugging it in, it should say battery charging but all it says is battery ok
I also can't load recovery because when im in the fastboot menu and i choose recovery the phone freezes and the green led comes back on... *sigh*
They have the full ota packages posted on Google site now you can and push through the stock recovery
Here just make sure you get the shame version
https://developers.google.com/android/nexus/ota#hammerhead
Sent from my Nexus 6 using XDA-Developers mobile app
I have the OTA. I also installed Wugs toolkit.
My phone is in fastboot mode due to the boot image not being able to be validated. I didn't voluntarily open up fastboot using the shortcut.
The phone is UNLOCKED until bootloader is rebooted, then it is LOCKED. If I click start, it becomes UNLOCKED again. Wug's toolkit tries to UNLOCK the phone even while the phone says it is UNLOCKED. I don't think the phone is actually UNLOCKED, however whenever it tells me it is UNLOCKED, I try to proceed with flashing and it gives me a remote failure message on each command.
The next thing I am going try is the drivers and Wug's toolkit has a driver option, so I will try that. Besides the drivers, any other ideas?
You seem to be inexperienced in rooting Android devices. If you aren't, I apologize for the assumption. However, you should learn how to use adb and fastboot without relying on the toolkit. Toolkits tend to hide diagnostic messages that adb and fastboot generate while running. This missing information makes solving problems much more difficult.
Strephon Alkhalikoi said:
You seem to be inexperienced in rooting Android devices. If you aren't, I apologize for the assumption. However, you should learn how to use adb and fastboot without relying on the toolkit. Toolkits tend to hide diagnostic messages that adb and fastboot generate while running. This missing information makes solving problems much more difficult.
Click to expand...
Click to collapse
I am inexperienced, I stated that earlier. I have check a bunch of different forum posts and a bunch of different guides. Nothing seems to be helping and it seems like such a simple problem, a boot image that can't be validated. I am not trying to do anything special with my phone, I am just trying to get it to work. I woke up and it was stuck in this 'AP Fastboot Flash Mode (Secure)' mode. It is very bare bones, not even similar to the screens within videos I have seen. One moment the phone says it's UNLOCKED, the next it's LOCKED.
You are the expert, I am not. I am merely following your directions and they don't seem to be working. I did some outside research, came to a toolkit. Toolkits are great for beginners, especially since they are UI built, are built by someone who knows the area of interest, which makes researching easier and more efficient, but on top of that, it seems to be getting me much farther than your advice, although nothing is successful at this moment.
Here is a little more context into my situation. My phone seems to be recognized by Fastboot, but not ADB (From what I found, fastboot will find devices in fastboot, and adb will find devices functioning normally, don't know how true that is.). In addition, my phone seems to switch from UNLOCKED TO LOCKED after reboots, but can become UNLOCKED again if I push ANY button. Every command I issue (i.e flash bootloader, flash radio, flash system, flash userdata) result in the message, FAILED:remote failure, which I am not sure how to avoid (I have googled, checked these forums, checked other forums and there doesn't seem to be much, if any documentation on the error), but I think it is related to the fact my developer options are turned OFF. My next course of action is to install new drivers (I checked my drivers which are said to be up to date, I also installed google USB driver through the sdk, but now I am going to look into an adb or universal driver?) and attempt to rerun everything successfully.
If you have any other ideas, or don't think its the drivers, feel free to bring it up.
As a couple of fellows said before, try this:
https://developers.google.com/android/nexus/ota
Flash a FULL OTA from the link above, not a factory image. To flash any OTA you don't need to be unlocked. I think you might be confusing the terms (with the OTA you don't have to flash anything using fastboot)
In the link there are the instructions, it's pretty straight forward and easy if you have the correct drivers installed.
OTA requires that u can startup into recovery, I cannot I can startup fastboot through key combo but when I go to select recovery the green led comes back on and the screen displaying the fastboot options remains static
I think the phone freezes because it does not appear to be able to use the battery. though there is a firm battery connection it will not charge or power on without being plugged in. maybe when I select recovery I can quickly unplug and replug the USB and maybe hold the power button to try to simulate a successful reboot.. idk just thinking aloud and working with what I got..
I also can not start in recovery mode and the OTA requires ADB, which isn't recognizing my device. I have also stated that I have followed those instructions, and nothing resulted from them, except the same messages I have been stating these last few posts.
I will try this first chance I get later tonight..
http://forum.xda-developers.com/nexus-6/help/solution-stuck-bootloop-locked-t3053783
Listen the ota doesn't get installed through fast boot, you have to select recovery through the fast boot then install the update by pushing it as bootloader does not need to be unlocked!
Sent from my Nexus 6 using XDA-Developers mobile app
holeindalip said:
Listen the ota doesn't get installed through fast boot, you have to select recovery through the fast boot then install the update by pushing it as bootloader does not need to be unlocked!
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Ok, well it seems we are at an impasse. You seem to think I can do something, so I am going to show some pictures of my screen. Its going to be blurry because I had to take it with my computer, so I apologize, but I will elaborate on each picture.
Qwertyismypw said:
Ok, well it seems we are at an impasse. You seem to think I can do something, so I am going to show some pictures of my screen. Its going to be blurry because I had to take it with my computer, so I apologize, but I will elaborate on each picture.
Click to expand...
Click to collapse
The first two pictures are when the phone is 'UNLOCKED'. The second two pictures are when the phone is 'LOCKED'. The moment I press anything in 'LOCKED' mode, the little android man goes away, and it becomes the first two pictures. WHENEVER I push a button in 'UNLOCKED' mode, nothing happens, except in the bootloader logs screen says, 'FAILED TO VALIDATE BOOT IMAGE RET -1'. I have done everything on that OTA page in every way possible. It has done me no good.
Ok, I made a little progress I think. Wugs toolkit allowed me to use TWRP on my phone and ADB is recognizing my phone now. There are a lot of options within TWRP though, so I am going to look through them all for anything relevant. Anything I should keep an extra eye out for?
If you can use twrp just download a custom ROM to your phone and move it over to SD card and flash it, then you will be able to boot and unlock the bootloader in developer ootions, that is your best bet, if you keep getting force closes after flashing a custom ROM your going to have to do a factory reset from within twrp
Sent from my Nexus 6 using XDA-Developers mobile app
holeindalip said:
If you can use twrp just download a custom ROM to your phone and move it over to SD card and flash it, then you will be able to boot and unlock the bootloader in developer ootions, that is your best bet, if you keep getting force closes after flashing a custom ROM your going to have to do a factory reset from within twrp
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
I don't have an SD card, can I move it to the internal storage? And how exactly do I do this? I can't copy/paste anything into the phone (it says the phone doesn't actually exist, even though adb is recognizing it as in recovery) or do I sideload it? When I try to sideload it though, the device disappears (and device manager sees nexus 6 under other devices, but the driver isn't up to date and no drivers seem to work. I've tried the google usb driver with no luck.) and it won't allow me to sideload it.