Database Info

[Q] Another TF101 Boot Loop - Can use ADB for 5 seconds only

Have not found this exact same issue, so here goes. Running TWRP recovery, EOS 4.2 JB on my TF101. I rebooted to recovery and tried to restore a backup I did earlier. Note: I have done restores previously with no problem, but that was using CWM. Anyway, the restore said it was successful. I then pushed the re-boot and it said...
Updating partition details...
Formatting cache using make_extfs...
Done.
Wiping data without wiping /data/media ...
Done.
Rebooting...
And it just keeps doing this loop. I have tried to get into recovery with the power and volume down buttons, with no effect. I have tried to connect to it using ADB, and I can usually get in one command before it disconnects and reboots again. If there was a command I could issue that would stop this insanity, it sure would be great.
I know there are dozens of similar issues out here, but I have not found anything that can help due to the short duration where I can have any effect on the tablet before it loops again. Any help will be greatly appreciated

LarryPSherman said:
Have not found this exact same issue, so here goes. Running TWRP recovery, EOS 4.2 JB on my TF101. I rebooted to recovery and tried to restore a backup I did earlier. Note: I have done restores previously with no problem, but that was using CWM. Anyway, the restore said it was successful. I then pushed the re-boot and it said...
Updating partition details...
Formatting cache using make_extfs...
Done.
Wiping data without wiping /data/media ...
Done.
Rebooting...
And it just keeps doing this loop. I have tried to get into recovery with the power and volume down buttons, with no effect. I have tried to connect to it using ADB, and I can usually get in one command before it disconnects and reboots again. If there was a command I could issue that would stop this insanity, it sure would be great.
I know there are dozens of similar issues out here, but I have not found anything that can help due to the short duration where I can have any effect on the tablet before it loops again. Any help will be greatly appreciated
Click to expand...
Click to collapse
Have you tried a cold boot into the rom and then if that works you could try re-installing TWRP through the Goo app.........its a shot in the dark.

Also, try to flash the latest KatKernel by timduru
Sent from my GT-I9300 using xda app-developers app

LarryPSherman said:
Have not found this exact same issue, so here goes. Running TWRP recovery, EOS 4.2 JB on my TF101. I rebooted to recovery and tried to restore a backup I did earlier. Note: I have done restores previously with no problem, but that was using CWM. Anyway, the restore said it was successful. I then pushed the re-boot and it said...
Updating partition details...
Formatting cache using make_extfs...
Done.
Wiping data without wiping /data/media ...
Done.
Rebooting...
And it just keeps doing this loop. I have tried to get into recovery with the power and volume down buttons, with no effect. I have tried to connect to it using ADB, and I can usually get in one command before it disconnects and reboots again. If there was a command I could issue that would stop this insanity, it sure would be great.
I know there are dozens of similar issues out here, but I have not found anything that can help due to the short duration where I can have any effect on the tablet before it loops again. Any help will be greatly appreciated
Click to expand...
Click to collapse
I would recommend just flashing back to stock because I think your data partition odds corrupt right now
Sent from my Nexus 7 using Tapatalk HD

LarryPSherman said:
Have not found this exact same issue, so here goes. Running TWRP recovery, EOS 4.2 JB on my TF101. I rebooted to recovery and tried to restore a backup I did earlier. Note: I have done restores previously with no problem, but that was using CWM. Anyway, the restore said it was successful. I then pushed the re-boot and it said...
Updating partition details...
Formatting cache using make_extfs...
Done.
Wiping data without wiping /data/media ...
Done.
Rebooting...
And it just keeps doing this loop. I have tried to get into recovery with the power and volume down buttons, with no effect. I have tried to connect to it using ADB, and I can usually get in one command before it disconnects and reboots again. If there was a command I could issue that would stop this insanity, it sure would be great.
I know there are dozens of similar issues out here, but I have not found anything that can help due to the short duration where I can have any effect on the tablet before it loops again. Any help will be greatly appreciated
Click to expand...
Click to collapse
Hi. I'm having the same exact problem. Were you ever able to solve the issue?

atomicscissors said:
Hi. I'm having the same exact problem. Were you ever able to solve the issue?
Click to expand...
Click to collapse
I would try getting into APX mode (hold VOL UP and POWER for about 10 seconds and see if your computer recognizes a device). In APX mode the screen will be black on the transformer.
If so, use EasyFlasher to re-flash TWRP, or the stock ROM. If restoring the stock ROM, be sure NOT to unzip it when you put it in the asusupdate folder.
See here for instructions on EasyFlasher: http://www.transformerforums.com/forum/showthread.php?t=31927
Also, this will not work on the SL101 or TF101G, only on the TF101.

Magic
atomicscissors said:
Hi. I'm having the same exact problem. Were you ever able to solve the issue?
Click to expand...
Click to collapse
I found this solution on XDA:
http://forum.xda-developers.com/showthread.php?p=25888080
It merely overwrites /dev/block/mmcblk0p3. It's been awhile, but I remember it took a few tries because the tablet would reboot between the 'adb shell' command and the 'dd' command. After 4 or so tries, it took and my tablet went straight into recovery.

[Q]Pretty sure TWRP just bricked my N5 [RESOLVED]

So I just wiped my cache and dalvik in TWRP and now I have no radio, no IMEI, no storage.. I think it borked my partitions. Tried flashing the factory image to no avail. It failed on the radio and I still have no storage.
Is there any way to recover from this?
EDIT: I was able to fix it as easily as I caused it. Check the 4th post. More detailed instructions on the 3rd post of page 2.

_MetalHead_ said:
So I just wiped my cache and dalvik in TWRP and now I have no radio, no IMEI, no storage.. I think it borked my partitions. Tried flashing the factory image to no avail. It failed on the radio and I still have no storage.
Is there any way to recover from this?
Click to expand...
Click to collapse
There is no way you simply wiped cache and dalvik. That doesn't even come close to touching your IMEI.
Why did you go to clear your cache / dalvik in the first place? Describe anything you did in terms of installing apps, flashing, wiping, etc.

leblvin said:
There is no way you simply wiped cache and dalvik. That doesn't even come close to touching your IMEI.
Why did you go to clear your cache / dalvik in the first place? Describe anything you did in terms of installing apps, flashing, wiping, etc.
Click to expand...
Click to collapse
All I did was flash a zip to change the dpi of my navbar. I've flashed the same zip a couple times before. Wiped cache + dalvik and it hung up for a while, screen went black for 5 minutes then the phone rebooted into its current state. I realize that wiping the caches doesn't touch the IMEI or anything like that, but what if the version of TWRP I have is buggy?
So knowing that yes, that is all I did, is there any way to fix it?

After a bit of googling I got it fixed. Apparently sometimes TWRP will cause some havok with the partitions when wiping cache. I just updated to the latest TWRP, wiped the cache again and everything came back up. Weird.

Always run the very recovery latest version.
a hammerhead wrote this.

Might be worth backing up your EFS partition to be on the safe side!

Nandroid backup is your best friend

beekay201 said:
Always run the very recovery latest version.
a hammerhead wrote this.
Click to expand...
Click to collapse
Yup, didnt bother to check before.
EddyOS said:
Might be worth backing up your EFS partition to be on the safe side!
Click to expand...
Click to collapse
Agreed. First thing I'm gonna do when I get home from work.
gd6noob said:
Nandroid backup is your best friend
Click to expand...
Click to collapse
I have a recent nandroid. What good is it though if recovery can't see my storage where the nandroid was saved?
Sent from my Moto X

_MetalHead_ said:
After a bit of googling I got it fixed.
Click to expand...
Click to collapse
Well, whatever you do, don't share your find here in case someone else ever has the same problem.

GldRush98 said:
Well, whatever you do, don't share your find here in case someone else ever has the same problem.
Click to expand...
Click to collapse
I did share it. Read the rest of the post you quoted. Derp.
Sent from my Moto X

_MetalHead_ said:
lApparently sometimes TWRP will cause some havok with the partitions when wiping cache
Click to expand...
Click to collapse
I don't know about you, but this is just what I look for in a recovery
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit

rootSU said:
I don't know about you, but this is just what I look for in a recovery
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Click to expand...
Click to collapse
It's a TWRP exclusive feature.

_MetalHead_ said:
After a bit of googling I got it fixed. Apparently sometimes TWRP will cause some havok with the partitions when wiping cache. I just updated to the latest TWRP, wiped the cache again and everything came back up. Weird.
Click to expand...
Click to collapse
Big thank you for this, I thought I was boned. I was trying to flash 4.4.1 but forgot that I had modified the screen density in the build.prop and so I got an error, tried to wipe the cache, thought it had hung up, got impatient and VERY stupid and forced the phone to reboot. SDCard was entirely inaccessible, couldn't connect to AT&T, everything was screwed up and everything I could find told me that wiping everything back to stop and losing the data was my only option. I had a week-old TiBu on my dropbox, which isn't bad but not great either. Nandroid, of course, inaccessible along with the SDcard. Your trick of updating TWRP (I had 2.6.3.2, latest is 2.6.3.4) and then wiping the cache again worked perfectly.
To anyone who comes across this, here's a quick overview:
1. Download the latest TWRP at http://teamw.in/project/twrp2/205
2. Boot your phone into Fastboot mode (Vol Down + Power from off, I think...worked for me)
3. Make sure your phone is plugged in via USB.
4. Open a command prompt in the folder you put TWRP in (ADB needed, obviously), type:
fastboot flash recovery imagename.img
For example:
fastboot flash recovery openrecovery-twrp-2.6.3.4-hammerhead.img
5. Only took a couple seconds until it was finished. Used the volume buttons to highlight Restart Recovery, hit power to reboot into recovery.
Wipe > Advanced Wipe, wipe what you need to wipe, viola, it was working at this point for me. Rebooted the phone, everything's back to normal. (it went through the "Optimizing apps" things on boot-up which took a few minutes, but everything is where I left it).

reynwrap582 said:
Big thank you for this, I thought I was boned. I was trying to flash 4.4.1 but forgot that I had modified the screen density in the build.prop and so I got an error, tried to wipe the cache, thought it had hung up, got impatient and VERY stupid and forced the phone to reboot. SDCard was entirely inaccessible, couldn't connect to AT&T, everything was screwed up and everything I could find told me that wiping everything back to stop and losing the data was my only option. I had a week-old TiBu on my dropbox, which isn't bad but not great either. Nandroid, of course, inaccessible along with the SDcard. Your trick of updating TWRP (I had 2.6.3.2, latest is 2.6.3.4) and then wiping the cache again worked perfectly.
To anyone who comes across this, here's a quick overview:
1. Download the latest TWRP at http://teamw.in/project/twrp2/205
2. Boot your phone into Fastboot mode (Vol Down + Power from off, I think...worked for me)
3. Make sure your phone is plugged in via USB.
4. Open a command prompt in the folder you put TWRP in (ADB needed, obviously), type:
fastboot flash recovery imagename.img
For example:
fastboot flash recovery openrecovery-twrp-2.6.3.4-hammerhead.img
5. Only took a couple seconds until it was finished. Used the volume buttons to highlight Restart Recovery, hit power to reboot into recovery.
Wipe > Advanced Wipe, wipe what you need to wipe, viola, it was working at this point for me. Rebooted the phone, everything's back to normal. (it went through the "Optimizing apps" things on boot-up which took a few minutes, but everything is where I left it).
Click to expand...
Click to collapse
Yeah man, I was certain I was gonna need a new phone. Glad this helped you. I'm going to update the OP with a link to your post so more inexperienced users can benefit. Thanks for typing it out.

_MetalHead_ said:
So I just wiped my cache and dalvik in TWRP and now I have no radio, no IMEI, no storage.. I think it borked my partitions. Tried flashing the factory image to no avail. It failed on the radio and I still have no storage.
Is there any way to recover from this?
EDIT: I was able to fix it as easily as I caused it. Check the 4th post. More detailed instructions on the 3rd post of page 2.
Click to expand...
Click to collapse
I remember you from the HTC one forums! Figures you already messed up your Nexus 5... Lol
Sent from my Nexus 5 using Tapatalk

MrGriffdude said:
I remember you from the HTC one forums! Figures you already messed up your Nexus 5... Lol
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Hey now, it wasn't my fault! Lol
Sent from my Nexus 5 using XDA Premium 4 mobile app

Yet another boot/brick issue

Have an XT926 Maxx with an unlocked bootloader. I can wipe partitions and flash custom ROMs just fine. I can also fastboot back to stock images. But for some reason, I can't get past the boot animation. For example, on the stock rom, it'll display the 'DROID' image upon boot and play the 'DROID' sound but then suddenly freezes, then reboots (over and over again). I've gone into factory recovery and wiped data/cache and still have the same issue.
I've searched the forums and was not able to find anyone with the same issue.
Any suggestions? Am I screwed? Perfectly good phone otherwise!

TWong1200 said:
Have an XT926 Maxx with an unlocked bootloader. I can wipe partitions and flash custom ROMs just fine. I can also fastboot back to stock images. But for some reason, I can't get past the boot animation. For example, on the stock rom, it'll display the 'DROID' image upon boot and play the 'DROID' sound but then suddenly freezes, then reboots (over and over again). I've gone into factory recovery and wiped data/cache and still have the same issue.
I've searched the forums and was not able to find anyone with the same issue.
Any suggestions? Am I screwed? Perfectly good phone otherwise!
Click to expand...
Click to collapse
If all you're doing is wiping data/cache, there's a possiblity that there might be some bad data in there still. I would also format data, as this will get rid of everything. Wiping data doesn't always get rid of everything. If you are fastbooting stock ROMs, always FDR after you flash, prior to booting into OS. Also, since your BL is unlocked, you need to load up an aftermarket recovery like CWM or TWRP. None of the new ROMs will work on stock recovery.

RikRong said:
If all you're doing is wiping data/cache, there's a possiblity that there might be some bad data in there still. I would also format data, as this will get rid of everything. Wiping data doesn't always get rid of everything. If you are fastbooting stock ROMs, always FDR after you flash, prior to booting into OS. Also, since your BL is unlocked, you need to load up an aftermarket recovery like CWM or TWRP. None of the new ROMs will work on stock recovery.
Click to expand...
Click to collapse
Thanks for the reply.
Yes, I know about the need for TWRP/CWR when flashing custom ROMs. I reverted back to stock recovery when I fastbooted the factory images. Using stock recovery, I wiped Data and Cache so not sure what you mean. What's FDR?
Sent from my LG-VS980 using Tapatalk

TWong1200 said:
Thanks for the reply.
Yes, I know about the need for TWRP/CWR when flashing custom ROMs. I reverted back to stock recovery when I fastbooted the factory images. Using stock recovery, I wiped Data and Cache so not sure what you mean. What's FDR?
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
FDR is Factory Data Reset. It's generally a good idea to boot back into recovery and FDR after fastbooting.

RikRong said:
FDR is Factory Data Reset. It's generally a good idea to boot back into recovery and FDR after fastbooting.
Click to expand...
Click to collapse
Ah, yes....I've done that numerous times. Still will not boot. Is there a way to erase the partitions and rewrite them? Perhaps they're corrupted or something.
Sent from my LG-VS980 using Tapatalk

I was, for some reason, able to get it to boot up once today. I was able to get to the 'Power off and Insert SIM' screen. After powering off, though, it would no longer fully boot into the OS. Still bootlooping.
Less than an hour later, i got it to boot up yet again. Not sure how, but it's booted up and now with my SIM installed. I know if I reboot, it'll happen again.
Anyone have a clue what it could be? Anything I can do before shutting it down that could help?

TWong1200 said:
Ah, yes....I've done that numerous times. Still will not boot. Is there a way to erase the partitions and rewrite them? Perhaps they're corrupted or something.
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
you can re-write the partitions using this tool, for the 926 only
https://www.dropbox.com/s/bpjghbbv0v6r4v5/DROID_RAZR_HD_Utility_1.3.gpt fix.rar

Bootloop after Xposed module - what are my options?

Hi,
My Nexus 5 has been working pretty well until now. Earlier today I decided to disable lightflow and try the Xposed LED Control module. I installed and rebooted and it seemed to be fine. But then while using the phone shortly after unlocking it it completely froze then rebooted itself. Since then it's been stuck in a bootloop where it gets as far as the boot animation but then freezes for a few seconds and returns to the Google screen again.
I tried power off and back on and tried loading into recovery to see if wiping dalvik + cache might get me as far a boot but when it loads TWRP it asks me for a password (I've never set one nor enabled encryption of any kind) so my only option is to cancel but then it can't mount the partitions to wipe the cache.
I suspect it's the Xposed module I installed that caused this but I can't be sure it's not just coincidental. I haven't done anything else unusual on the phone today.
Is there anything I can do to fix this that won't require a complete factory reset? Is there any way I can at least backup or keep my data? Unfortunately I'm not at a computer where I can run or install ADB but if that would let me save my current setup or data I can do so at home tonight.
Thanks!

Try flash stock cache.img from fastboot
I don't see this being xposed related but who knows?!
Sent from my Nexus 5 using Tapatalk

I know clearing the cache asks for a password, but try to see if you can flash something. The something is the Xposed disabler zip file in the root of your scard.

Hi,
From the Xposed Framework thread:
In case you get into a boot loop:
You can flash the attached Xposed-Disabler-Recovery.zip by Tungstwenty. It will be copied to your (external) SD card when you install Xposed as well. The only thing it does is copying /system/bin/app_process.orig back to /system/bin/app_process
Click to expand...
Click to collapse
Maybe this..., the "Xposed-Disabler-Recovery.zip" should be at the root of /sdcard (at least for me it was the case).

You could try re-flashing recovery in fastboot mode to see if it fixes the password issue or also I believe philz touch recovery can read twrp backups if you want to switch to a different recovery.

The original bootloop seems like /data corruption to me (freeze + fsync perhaps), then the twrp password further evidences that but.... hmmmm
Sent from my Nexus 5 using Tapatalk

viking37 said:
Hi,
From the Xposed Framework thread:
Maybe this..., the "Xposed-Disabler-Recovery.zip" should be at the root of /sdcard (at least for me it was the case).
Click to expand...
Click to collapse
I think I was able to flash this. I keep getting errors about unable to open "/data/app-lib/com.h3r3t1c.onna" - rest off screen, then "Not a directory" and "unable to mount '/persist'", but it seemed to mount /system and flash successfully.
Unfortunately, this doesn't fix the bootloop.
I guess I'll try flashing the cache.img as suggested tonight and see if that works. If not, I guess I'll have to try and wipe.
If I do a factory wipe from TWRP, will I lose photos, videos I've taken? Restoring everything else will be a pain but it's really the photos that I haven't backed up yet I'm more concerned about.
Thanks!

Twrp doesn't wipe /sdcard
Sent from my Nexus 5 using Tapatalk

I just installed that module today and its working fine. I'm on the stock ROM. But doesnt Xposed put an Xposed disabler flashable zip file on your sdcard? Or is that something that maybe I just transferred over and forgot that I did. Because I dont remember transferring it to my phone or downloading it but I have it on there. If you have it, maybe try flashing that to disable Xposed and see if it boots.
EDIT: viking37 actually already suggested this.

Wiping or flashing cache didn't help either.
I tried a factory wipe, which didn't help.
Then I formatted data from TWRP and was able to boot but there were strange issues including a complete inability to connect to the cell network.
Also, TWRP kept complaining that it couldn't mount /persist
So finally I ran flash-all.bat from the factory image download to try and completely return to a factory image. It seemed to work but then I got into a bootloop where it reboots after upgrading android then apps starting.
I tried to do it again but now fastboot keeps giving me this error: FAILED (remote: flash write failure)
or if I try to wipe: FAILED (remote: failed to erase partition)
I'm starting to thing maybe it's a hardware problem with the internal flash... Is that likely or is there still something I can do?
Will I be able to RMA it in this state?
Thanks again for the help!

Bootloop due to data partition

I have been using lineage OS 14 jgcaap ROM (https://forum.xda-developers.com/oneplus-one/development/cyanogenmod-14-0-t3464337) from few months now.
Yesterday, my phone battery died while I was out. When I tried to boot it again after charging it is stuck on lineage OS logo even though the phone is fully charged by now. I didn't install any app recently or do anything with system partitions.
I went to twrp cleared cache, dalvik and system. Reflashed the ROM but still bootloop. Then I backedup data partition and cleared data as well. This time phone booted properly. So I restored data partition but then again it went into loop. Now if I clear the data partition the phone boots but if I restore the data partition there is bootloop. But I have some important data in messages, offline note taking app and whatsapp which I don't want to use.
Is there any other way to boot with all data intact or Is there any way to restore data from twrp nandroid data backup after I boot with cleared data?

1pratham said:
I have been using lineage OS 14 jgcaap ROM (https://forum.xda-developers.com/oneplus-one/development/cyanogenmod-14-0-t3464337) from few months now.
Yesterday, my phone battery died while I was out. When I tried to boot it again after charging it is stuck on lineage OS logo even though the phone is fully charged by now. I didn't install any app recently or do anything with system partitions.
I went to twrp cleared cache, dalvik and system. Reflashed the ROM but still bootloop. Then I backedup data partition and cleared data as well. This time phone booted properly. So I restored data partition but then again it went into loop. Now if I clear the data partition the phone boots but if I restore the data partition there is bootloop. But I have some important data in messages, offline note taking app and whatsapp which I don't want to use.
Is there any other way to boot with all data intact or Is there any way to restore data from twrp nandroid data backup after I boot with cleared data?
Click to expand...
Click to collapse
Try dirty flashing the rom.

Mr.Ak said:
Try dirty flashing the rom.
Click to expand...
Click to collapse
same problem here, with RR 5.8.5. With dirty flash nothing has been solved.

paolone919191 said:
same problem here, with RR 5.8.5. With dirty flash nothing has been solved.
Click to expand...
Click to collapse
Replace battery.

My battery lasts more than 25 hours, and even if I connect my phone to the wall plug it stay in bootloop. The only Rom that gave me this problem was RR.

paolone919191 said:
My battery lasts more than 25 hours, and even if I connect my phone to the wall plug it stay in bootloop. The only Rom that gave me this problem was RR.
Click to expand...
Click to collapse
You mean you don't have this issue when you flash other rom? That's quite impossible. This issue is of battery only.

With cm13 this issue doesn't appear

Repalcing the battery is the only solution....
Mr.Ak said:
Try dirty flashing the rom.
Click to expand...
Click to collapse
..time for changing battery

paolone919191 said:
With cm13 this issue doesn't appear
Click to expand...
Click to collapse
Strange.Anyway,your best bet is replacing battery.

Is there a way to enable the bootlog?

I have a quite similar issue: yesterday i restarted my Opo after activating Xposed and after reboot, the phone stuck in the lock screen (nothing works, touch ecc...). I've done a Nandroid with TWRP and after that i've made a wipe data (data partition only): now the phone starts and works as well, but if I restore the data partition it stucks in lock screen like before. Is it a battery problem too? I can upload the dmesg.log if needed.