Sorry for the long post! As a bit of background, I was running stock rom with sytemless root, EX Kernel, TWRP and I had just enabled xposed (the only new variable in my setup). So I plugged my 6P in at the gym before I play some ball. Phone proceeds to random "reboot" a few seconds later, no huge deal I thought. Then it enters The Indestructible Bootloop (IBL). It won't boot past the animated colored dots. Play for a couple hours, phone still not booted; slight to moderate anxiety setting in. I figure, worst case scenario, I have to flash a factory image when I get home. So I try to reboot it a couple times by booting into the bootloader (holding power and down vol), then recovery then reboot. I also flashed the xposed uninstaller and deleted /data/data/de.robv.android.xposed.installer/conf/modules.list: neither worked to solve the IBL. Then I just waited til I got home and tried to plug it into my Win 10 PC. Nothing. Device manager doesn't even recognize it as anything plugged in; moderate to high anxiety setting in. Note that I could previously connect it just fine and device manager doesn't see ANY kind of device connected, so I don't believe it's a driver issue or anything like that. So, through TWRP, I look to see what's on the device storage: I have an old nandroid ( I believe stock unrooted) and a custom rom, Chroma as well as some GApps and a couple custom kernels. At this point I wanted to preserve my text messages so I did a new nandroid then tried restoring the old nandroid as well as flashing Chroma without wiping data. Nothing, still won't get past the colored dot IBL. So then I tried doing a full wipe before trying the old nandroid and Chroma again. Nothing. Figured it may have been a malicious file on my sd card so I deleted a few files that I didn't immediately recognize in TWRP and tried all the above steps again. Still nothing. So I just called Google and they offered to replace it. However I would like to have my phone for the weekend and not have to have a $650 hold on my account. I'm on Project Fi so I can't use a temporary burner phone. I figure I'm probably screwed but hopefully one of you geniuses could help me out. Thanks in advance!
tl;dr: Phone randomly rebooted and entered indestructible bootloop. Windows device manager won't recognize it at all. Tried everything I can, including clean flash of custom rom and an old nandroid: phone still won't get past bootloop.
Related
Sometime last night, my AT&T G2 (D800) decided to go from being powered on and idling, to going into TWRP recovery mode. All by itself. I saw this, unplugged it from USB, and tried to reboot into system mode. But it simply won't do anything except boot into recovery. Powering off, trying to get to the bootloader, none of that works.
This is not a custom ROM, it's 4.2.2 stock from LG. I only rooted the phone, which was several weeks ago, and haven't had any problems, aside from TWRP not wanting to back up anything. I've been using Android since the original TMO G1 with JesusFreke's ROM, so I have a pretty good idea of what I'm doing, hopefully.
The only recent changes I've made are:
I updated busybox about 3 days ago (but have rebooted fine since)
I grabbed several legit apps from the market last night
Last night I also DL'ed, but did not apply, a ~50MB OTA update that has been pending. I don't think that would install without explicit permission anyway, which I didn't give it?
This phone was encrypted from the start. Maybe that;'s what prevents TWRP backups,, but right now I'm seeing TWRP errors/logs saying something like "Unable to mount \data". And yet I can browse to other folders, and see filenames in \etc for example. However, I don't see any files at all in \boot.
Since this phone has no external memory, and it's customized and has numerous configured apps, I really really don't want to have to wipe it. Although at this point, that may not even fix the problem? Even if it did, since I haven't been able to make backup images, it would be a Bad Thing™ either way. (Yes, I do have a secondary plan with Titanium, with backups going to cloud storage, but these are tedious and now a few weeks old. And wouldn't restore the ROM & system en masse.)
Please help.
Solved?
I'm not sure what caused this to occur, but I found somewhat of a solution after digging deep into my Google-fu.
I followed the instructions in this XDA thread and it actually worked. I didn't have adb access, but I was able to use dd successfully. It allowed me to boot into the device, unencrypt it, then arrive at the lock screen.
However, when I put in the lock code, it went apesh!t and played multiple notification sounds, with a blue circular wait symbol. It also flashed the LED from green to blue, as it normally only does during boot. Once I pressed the power button, I was back back into TWRP.
So then I followed Step 2 again, and once in the phone, I used terminal to run the dd command from inside the OS. This might be what it ultimately needs, because the prior attempt in TWRP had an error to the effect of "no space left on device".
I can't call it Solved yet, but it looks good to at least be able to get in and use the phone. I'm backing up with Titanium before I do anything else and will reboot and test its permanency later.
I'm gonna close this thread now that I think I have a handle on what is going on. The fix does survive a reboot, so I believe it's possible to repair the issue permanently per the instructions above. I also ran the phone for 3 hours with heavy app usage and no problems.
I believe what may have happened is my OTA decided to override my choice to NOT update the ROM, as some have reported in this Reddit thread. There's a lot of good info in that one, including how to stop getting nagged by turning the OTA notifications off, or to freeze it entirely with Titanium Backup if rooted.
Anyway, what apparently happens is that when the OTA/upgrade goes to reboot, and encounters a custom recovery, it gets confused... when you try to power cycle or reboot again, it sees the stock recovery still hasn't run whatever it wanted, so it starts recovery again Lather, rinse, repeat.
Fun times.
The last few days I had an experience that I want to share. Maybe it helps somebody else.
Last week I upgraded my Defy from Quarx's CM10.2 to CM11 version 20140724.
It ran for about two days. It was stable and the performance looked better than before.
Then, when I was outside, my battery was empty. I always have another battery with me, so I exchanged the battery.
Then, two seconds after I inserted the battery, a black screen with the following white text appeared spontaneously, without pressing a button:
Bootloader
09.10
Code Corrupt
Ready to Program
connect USB
I could not enter recovery, or anything else.
So, I decided to go back and flash the original Motorola Android 2.2 version.
On earlier occasions this worked perfectly when I bricked my phone, but this time, after flashing the SBF with RSDlite, the phone hang while booting with the android logo on the screen. Only after a few hours of trying different SBF systems, the idea popped up, that the problem was not in the SBF, but in the combination of the old Motorola system and the new CM11 data partition. So, I entered recovery and wiped the data partition.
Then the system booted normally and I could proceed with rooting the system, installing custom recovery and restoring the backup.
Everything is back to normal again.
Now, I wonder what could have caused this problem.
I am a bit suspicious about the backup method I used. I create backups with the online nandroid app. The CM11 system installed the TWRP 2.7 recovery. The first time I tried to restore a backup, I noticed that the TWRP recovery had a problem with the old (CM10) and the new (CM11) backups, because they contained files for partitions and-sec and recovery, that it could not handle. In later attempts to restore the backup I unticked these partitions and the restore seemed to work well. I rebooted it several times. Could it be that these attempts damaged the system in such a way, that only when inserting a battery, the corruption was detected?
Or should I assume that there was a hardware glitch when the battery was replaced?
F.Zwarts said:
.
Then, when I was outside, my battery was empty.
Click to expand...
Click to collapse
iirc this was one of the bugs of cm11. if you let the battery runs completely down, it may not boot again. not sure if this has been fixed with the latest cm11.
My G2 has been acting really funky lately, hanging on boot and not being able to "hold" recovery flashes. I'll start from the beginning of my little story.
On Saturday, I wanted to do a nandroid backup from TWRP (not sure which version, an older one but not terribly old). It failed several times. I went back into the OS (CM 12.1) and backed up all apps and app data to an OTG USB via Titanium Backup. This was successful. I tried to go back into TWRP a second time. Nothing. Recovery is not even there, I get a security error from what I believe is fastboot. I went back to CM and tried to re-flash TWRP. Now I get a security error on the LG screen. Nothing would boot, no recovery mode, I did have download mode although I had no PC with me so I didn't know this at the time. I was away last weekend so I had to go without a phone for a day... which was actually... kind of pleasent. Don't ask me why I carried two 32GB USBs and an OTG adapter on my keychain but no laptop, because I have no idea why I would do this, lol.
Came home Sunday afternoon and decided to nuke the whole phone with a TOT flash. Since I always wanted to try CloudyG2 since we all know AOSP-based ROMs don't do the camera justice, I went ahead and TOT flashed, re-rooted, re-AutoRec, etc. Everything worked wonderfully; I did a full wipe in TWRP, flashed in Cloudy, then the KK radio, then Xposed. Played around with things like XCam and a few Xposed modules. Everything was working awesome, so I did my restore in Titanium. Took a few hours, but Titanium says everything went fine (sans for a few CM apps which did not restore by design I guess). I checked out a few apps, all my data is there, wonderful. Titanium told me to restart so after poking around a bit, I went for the restart. Hang on boot. For several hours. Tried to go to recovery, fastboot security error. Seems it can't "hold" recovery or something else that I'm flashing?
Clearly I am doing something incorrect here with flashing and all that, but I can't figure out what. I'm not new to flashing and modding, and I've flashed regular CM updates and other goodies onto this G2 for quite a while with no issues. I'm going through the same steps I would normally with CM, and I've had plenty of success with that. Any ideas what I am doing wrong here?
Had same issue and know I hard bricked it trying to get it fixed ... Off to a different phone I guess .. Not sure why it wouldn't hold a recovery either after a few hours ... I gave up .. Good luck
Sent from my SCH-I535 using XDA Premium 4 mobile app
At this point I have completely run out of options. I AM CALLING UPON THE XDA COMMUNITY TO PLEASE HELP ME. Little bit of background info, nexus 6p was rooted and modified through xposed. Had some modules installed, mostly quality of life and visual/theme modules, as well as the latest version of SuperSU.
These past few days my Nexus 6P has completely stopped responding at times. Extremely laggy and could not do **** with it, systemui kept restarting over and over and over again for no reason. Had to keep force rebooting (holding down the power button for 10 seconds) multiple times over and over again, to the point where it suddenly stopped booting into the OS, it just kept giving me the boot animation loop, i could only access the TWRP recovery i had installed. Before all of this **** went down, I had created a TWRP backup because it would be my safety net if i could somehow miraculously get it to work. Now i have a backup of my TWRP BACKUP FILE on my desktop.
I have wiped caches more times than i can count, have tried factory restoring and formatted the data, and tried flashing the stock google image (the same one that i originally flashed at the time that I got the phone when i started to root) as well as flashed the old TWRP version i had, as well as the current latest version of TWRP, and then transferred the backup i made back onto the phone's internal storage. Tried restoring the old backup from TWRP, and each time it restores, it just reboots without reaching 100% and once it reboots, it still gives me a bootloop, this time, no boot animation, it just gets stuck at the Google text with a little "unlocked" logo at the bottom. I have completely run out of options, and have A LOT of EXTREMELY IMPORTANT information i have saved on the phone.
I will say it again. I am EXTREMELY DESPERATE to get my data back, to the point where i am even willing to offer a cash reward for any help to get my phone working back to the way it used to, or even at least to extract the information through the backup, if at all possible.
Additional information about the files and images I used:
angler-mdb08k is the name of the google image i had back when i had the phone and have flashed again
twrp-2.8.7.2-angler is the TWRP version i had back when i had the phone originally at the time
I had flashed and followed guides online through adb method.
Hello all,
I have a Nexus 6P, stock, rooted, with Xposed installed. The phone is completely functional for the better part of its life time since I bought it at release -probably first or second batch- (except for random reboots once daily on average, deemed by my investigation and exhausting all options to be a hardware issue or Xposed related).
Today, out of nowhere, the phone randomly rebooted itself and surprisingly it launched the "Android is starting..." dialogue which, if I'm not mistaken, optimize apps for ART. The battery was at 19% before it randomly rebooted, so when it started that optimize apps it went down to 0 (I assume) and it turned off. The charger wasn't connected correctly so that happened. Now the phone keeps restarting itself up to before it gives me the boot up decryption phase of the Data partition and reboots again. I assumed it can't decrypt Data for some reason, so I launched TWRP recovery to try and decrypt data and take a backup copy of my Titanium Backup folder on storage... Unfortunately, TWRP reports "failed to decrypt data" even though I'm 100% positive that the pattern is correct because I'm literally inputting it almost 10-20 times a day for the past two years...
Note: there seems to be a red blinking LED in the top left corner of the the phone. I never even knew this existed.
WHAT I WILL DO
I'll reflash everything system-wise.. I'm ok with that. I'll reflash the factory images, root it, install Xposed, no problem.
WHAT I NEED HELP WITH
I need to extract some folders from my phone storage, namely the Titanium Backup folder. I know the pattern protection of the encryption.
How do I go about doing this?
UPDATE:
Help is urgently needed now indeed: The phone doesn't even turn on to bootloader mode anymore now. It was able to, just half an hour ago. Now all I see it the red blinking LED.
UPDATE2: https://support.google.com/nexus/troubleshooter/3337561?hl=en-GB#ts=3337942
I'll try in 30 minutes.
Meanwhile, please help me with my original problem; extracting data.
I was thinking, if I boot into bootloader mode, can I use adb to pull any folder? If so, will that work in my case with decryption fails or Data partition doesn't seem to mount correctly?
Relevent:
Reviewing some other threads:
TWRP: 3.0.2-2
Bootloader: UNLOCKED
I did NOT upgrade to Android 7.0 nor was I planning to, until Xposed is available.
I did NOT flash anything **new** recently. However, Installed an Xposed module yesterday which caused a bootloop. I rebooted into TWRP, uninstalled Xposed, rebooted into system (which looped once, out of the ordinary) and I uninstalled that module, back to TWRP installed Xposed, and rebooted back into system. It worked for 12 hours and then what I wrote this post for happened as stated above.
UPDATE3:
15 minutes into charging... NOT EVEN A RED BLINKING LED ANYMORE.
Last? UPDATE:
Almost 1 and a half hour into charging and there is no longer ANYTHING. Is it hard-bricked now?
How the **** is this possible? I'm very much capable of solving any sof-brick but not a hard-brick...
Thats a really crappy scenario. Im a little busy right now (not that I can get you out of this regardless) but I sort of skimmed through your post. Are you able to connect adb? If so you might be able to use "adb pull" to get that data.
On my 6p TB is located at:
/storage/emulated/0/TitaniumBackup/
Itll probably be the same location on your phone. Good Luck
KLit75 said:
Thats a really crappy scenario. Im a little busy right now (not that I can get you out of this regardless) but I sort of skimmed through your post. Are you able to connect adb? If so you might be able to use "adb pull" to get that data.
On my 6p TB is located at:
/storage/emulated/0/TitaniumBackup/
Itll probably be the same location on your phone. Good Luck
Click to expand...
Click to collapse
I was indeed able to connect to a PC after I saw the problem (the bootloop essentially)... But I didn't at the time as I didn't have a plan of action as to how to get my data, so I turned it off. After sometime, I couldn't do anything with the phone... Not able to boot into bootloader, not recovery, the phone is essentially not turning on to anything, not even the splash screen; like a hard-brick. I'm not sure if this indeed is a hard brick as I've never seen any.. and don't currently know what to try next.
Is the LED still showing? if so, do the bootloader boot combo, and see if fastboot devices gets a response in a command prompt - or terminal if you're a linux guy.
if so, you can boot to twrp, decrypt data - try default_password -, and browse the phone's files from your computer's file browser, the phone will show up as Nexus 6P. That's my suggestion, wish you luck.
TnT_ said:
Is the LED still showing? if so, do the bootloader boot combo, and see if fastboot devices gets a response in a command prompt - or terminal if you're a linux guy.
if so, you can boot to twrp, decrypt data - try default_password -, and browse the phone's files from your computer's file browser, the phone will show up as Nexus 6P. That's my suggestion, wish you luck.
Click to expand...
Click to collapse
I honestly declared it hard-bricked.
Will Fastboot show any devices if the phone didn't show bootloader screen?
I'll try again today.
Update:
Didn't work.
check out my post
[Guide] Fool/Noob proof way to do clean installs on Nexus Devices
http://forum.xda-developers.com/nexus-6p/general/guide-fool-noob-proof-to-clean-installs-t3518311