So I just got back from thinking my phone was completely bricked since it was S-On and download mode seemed not to be working. I wanted to post this in case it proved useful for anyone else.
If it seems like you can't boot into download mode or ruu mode (is that right?), and your phone is stuck in a bootloop because something went wrong (in my case, I stupidly restored a marshmallow boot, recovery, and image after updating to nougat) then try removing the SD card from your phone. If you saw a message like GT CAN'T CONNECT on download mode once before getting stuck only being able to access the bootloader, try removing the SD card.
Here are the specifics:
I had put my marshmallow nandroid on an sd card for space reasons, and I had undone my adopted storage before updating. So I restored the marshmallow nandroid from the sd card, and rebooted (right after hitting reboot I realized my mistake). The phone then entered a bootloop and never got past the htc (powered by android) screen.
So I tried getting into download mode, and everything seemed normal for a moment, it showed the usual download mode htc screen, and the yellow/orange text at the bottom appeared like usual, but there was one line that was a little odd. Although I can't remember it perfectly, I'm fairly certain it said something along the lines of GT CAN'T CONNECT.
Not too long after that text and before the usual menu could pop up, the phone rebooted into normal mode, which was stuck in a bootloop, and any future attempts to access download mode yielded a blank screen before rebooting. It seemed like download mode had gotten corrupted or similar. I could still access the bootloader with the Volume Down and Up buttons both pressed, but since I was S-On, I couldn't do much aside from try to access download, ruu, or recovery. All three modes had the same result of the htc boot screen followed by a blank screen and a reboot (trying to sneak in a fastboot flash command never worked, it always threw an unknown error). Once, running "fastboot oem rebootRUU" seemed to actually work correctly, but fastboot was unable to communicate (unknown error) and the phone rebooted shortly after.
After many tries, I was ready to throw in the towel, but before I did, I decided to remove the sd card and try once more. This time, download mode got stuck at the htc screen, but never bootlooped, which was already a positive sign to me. I entered ruu mode from the bootloader, and from there I could flash twrp, reboot into twrp, put the sd card back in, and restore the nougat image and boot.
Underneath all this, I do have a question though... what is that message supposed to mean? GT CAN'T CONNECT?
Edit:
And why does the sd card do this? I just tried getting into download mode again after putting my sd card back in, and it failed to enter download mode (the system is working this time too).
Edit 2:
Phone information: CID: BS_US001/BS_US002 | MID: 2PS650000 | 2.38.617.6
Related
I was playing with my splash screen and boot animation, and I changed the PB31IMG file on my sd card to a custom splash image. I went to hboot (.92 i think) and it gave me the error "no image found" or something like that. I turned off the phone, and tried to boot up into hboot again by holding volume down+power. As soon as I did, my phone vibrated maybe four times and stayed at a black screen. I can't turn the phone on now, or boot into recovery. Has this happened to anyone else? More importantly, does anyone know how to fix it?
Just to add more information (Im really not sure what's relevant), I was running virtuous 2.6 with hydra #1, 2.15 radio. Also, the image error happened before when I was trying out a different splash screen. That time I deleted the file and re-transfered it my sd card. Hboot was able to recognize it as a splash screen when I rebooted it that time. I'm not sure, but my phone might have booted into clockwork recovery after hboot checked the img file.
One other thing that might be a problem was that I might've been running low on battery. I didn't check, but it was the end of the day and I'm usually almost dead by the time I charge it again.
Never mind.
(Unrevoked forever wiki)
When I try to get into Fastboot by pressing VOLUME UP and booting the phone, my phone instead buzzes three times and acts dead. What happened?
The S-OFF update also enables Qualcomm Diagnostics mode on your phone, which is entered by doing what you just did. You can exit this mode (and boot normally) by removing the battery and USB cable.
Coming from a phone with microSD extension, I had never encountered such an issue:
I bought this phone with a stock 4.2 Rom installed and tried to install a custom Rom. I first installed the latest version of touch recovery (tried it and it seemed to work fine) and did a backup using the default settings. Then I erroneously chose to format system and data, thinking that I could then "install from zip". Strangely, these steps deleted everything in the /sdcard directory and I couldnt select "external SD" (because the phone isnt equipped with it anyways?). Then I made a second mistake and restarted the phone, despite the message warning that I no longer had an OS installed. I took the battery out, and then held the power down while pressing the power button. The phone couldn't get into recovery, but instead showed a screen with the android logo, a large "Start" sign above it, and "Downloading...", "Do not turn off target !!" below it. Pressing the power button now got the phone to show just "Google" and a lock logo under it. The PC (windows 7) can not detect the phone throughout the process.
I tried the latest tool kit and samsung's USB driver but couldnt get the phone recognized by the PC.
Does this mean that the phone is doomed???
Please help!!!
Trent
Relax, it's not easy to 'doom' your Nexus. Especially with all the hard-workers in XDA
Try accessing Recovery mode by holding down BOTH vol up + vol down, as well as power. Holding just vol down + power is 'Download Mode', and at the least you can get to this. Means your phones far from doomed
Thanks a lot for the reply!
As a matter of fact, I also figured out how to get back to recovery (if only I had read your post earlier, my pain would've been much less!). But the problem remains that I can not get a target ROM onto the phone, since: 1. whatever I did seemed to have gotten rid of the nand backup supposedly stored in /data/media/TWRP/BACKUPS/ (I'm using TWRP V. 2.3.2.1). 2. I can not get my PC(or Mac, for that matter) to recognize the phone or the internal storage.
Any pointer from here?
Thanks again!!!
Trent
You can download a factory image and install with fastboot. It's quite easy and instructions are readily available on this forum. You can then install a custom ROM afterwards if stock is not your thing.
Found the answer finally!
It's the adb push method. Basically, it's to install adb drivers and execute a few commands via the command window. Not too bad... Don't know much about fastboot yet though ... If anyone else needs more details, please PM me (to save public bandwidth).
Thanks a lot anyways, whpnhp and jocalderone!!!
Trent
Hi there,
obviously I did something wrong, cause now my phone wont boot up. It is stuck on the HTC logo, and stays there for hours after hours. I can get into download mode etc, tried factory reset, but to no avail.
My phone is S-Off, but it is not recognized by adb anymore, so I cant get it to install TWRP.
My OS is 1.40.161.8 and my CID is VODAPE17
Any help would be appreciated.
Thanks,
Chris
Of course you can't get adb to work since it only works if you're booted to system. Did you try using fastboot?
(The answer of that question actually doesn't matter that much.)
To get your phone back to a working state you simply need to flash a RUU. Be aware that these methods will erase all data on your phone and it will downgrade its firmware version!
Do you have an external SD card for your phone that is not bigger than 32 gb? Format it to fat32, download this RUU and put it into the main directory of the SD card. Rename the file to "0PJAIMG.zip". (That's a zero, not an O.) Then put the SD card into your phone and boot to download mode. Follow the instructions on screen. Your phone will prompt you to power it down at the end by pushing the power button. Wait some seconds and you can restart it as you would normaly do. You can then upgrade your firmware to the latest version by using the OTA function in settings>about.
If your pc is able to detect your phone by using fastboot commands you can also use this RUU. Boot your phone to download mode, disconnect you pc from the internet (just for safety reasons because of the next step) and disable your firewall and your antivirus software (both can interfere negatively with this ruu). Then run the RUU.exe as administrator. Depending on the age of your pc it may take up to ten minutes until a new window pops up. It's recommended closing every window and programm you don't need. You don't have to do anything with your phone during this process although the ruu might say that your phone should be booted to system. At the end you need to upgrade your firmware, too, by using the OTA function.
Thanks for your help. It worked as a charm. So relieved to have it back up and running.
I have a non-rooted VS986 (probably 26A).
Recently I ran out the battery and the phone died. When I charged it and turned it back on, it stayed stuck at the Verizon boot screen.
I hadn't really changed anything recently, and I did not take the most recent OTA (27C) so this just seems like a random hardware failure.
I can boot into Recovery, but if I choose "Safe Mode" or "USB Debug Mode" the phone just hangs at the Verizon Screen.
I tried to Wipe Cache and restart, but it just hangs at the Verizon screen.
I *can* boot into Download mode.
I would really like to back up the internal SD card--photos, settings etc. if possible.
Is there anything I can do at this point just to get an ADB prompt or something that might allow me to perform a backup (even if limited)?
Sounds like a motherboard failure. You could try booting into download mode and using adb to pull your files but you'll have to know the exact path to their location. And to do that you would have had to have USB debugging activated.
If that doesn't work then your SOL. Time to use your insurance or warranty if it's still good.
A little background on the issue:
I had my phone on the charger for awhile, saw it at 100% so I unplugged it, put it into my pocket, and thought nothing of it. Next time I pull it out of my pocket(about 4-5 minutes later), I find that my phone has restarted itself and won't boot whatsoever. I then tried to boot into recovery to see what was what, and found I couldn't do that either(using vol up+power). I found out that the only way to get into my recovery is to plug into the pc, then use vol up+power(?????). After getting into the recovery, I found that every time I boot into it I'm greeted by a message saying "Keep system read only?", with option below to swipe to allow modifications. It doesn't seem to matter which I choose as neither do anything. I look at my drives and see that my internal storage is listed as 0MB. I then tried restoring a Nandroid backup I made a month previous, but I was greeted with a log saying the phone failed to mount literally everything, followed by "invalid arguement" after every line(would post logs but my phone is currently stuck in a loop in an ruu). This happens with anything I try to do in TWRP(running 3.0.0.0), whether I try to change the filesytems to FAT or try flashing a new ROM(seemed to open fine with Aroma installer, but gets stuck writing to /data). After exhausting everything I knew to try and everything on the Interwebs, I resorted to trying an RUU. It opened fine, recognized my device fine, but is now stuck doing the same process over and over(currently at 46 min). I'm running ViperOne 3.5 with an unlocked bootloader and S-on. I'm currently at a loss of what to do, and would appreciate any and all help. :3
Corrupt nand I think.. It cant find any partitions.
Beamed in by telepathy.
Any ideas on a solution?