Database Info

Bootloop - Can access Recovery

Hey everyone,
So earlier this evening I attempted to flash a new ROM to my Transformer. Unfortunately, something went wonky during the Factory Reset and it froze for about an hour. Not knowing what else to do, I ended up resetting the tablet and booting back into Recovery.
Long story short, I currently have TWRP v2.6.3.2 installed and accessible. Unfortunately I am unable to boot into any ROM I flash. I am able to go through the setup process just fine (have tried CROMi-X 5.4 and CROMi-X 5.2.3), but once the tablet restarts after installing, I am stuck at a boot loop on the ASUS splash screen. Did I inadvertently delete some system files that aren't replaced with a new ROM?
I'm out of ideas at this point and am hoping someone out there can help guide me in the right direction. My current plan is to try reverting to the stock Android provided by ASUS on their website (4.2.1). I really appreciate any advice/help anyone can provide, and thank you in advance!

If you want to know what the problem is, get a logcat. If you just want to fix it, do another Factory Reset. If that doesn't work, run "Format Data" in TWRP (this may take 1-2 hours). Note that this will delete all your user data on the tablet.

_that said:
If you want to know what the problem is, get a logcat. If you just want to fix it, do another Factory Reset. If that doesn't work, run "Format Data" in TWRP (this may take 1-2 hours). Note that this will delete all your user data on the tablet.
Click to expand...
Click to collapse
Thank you so so much for your help _that. I had no luck after doing another Factory Reset, but a second run through TWRP's "Format Data" worked like a charm. Kudos to XDA for being the savior of my sanity!

[Q] I've tried everything and looked everywhere

Hey everyone, I'm using a GT-P5100 (3G + Wifi) O2 UK rooted tablet and for the last month it has been broken. It started rebooting itself randomly every now and then, and then suddenly it wouldn't even boot up for 15 seconds before it would restart itself again.
I am able to get into safe mode and I can get into the boot options, but when I factory reset it does nothing, I've tried from the boot menu, from safe-mode options and even from the dial up code.
I tried to connect my tablet to my PC as a media device and format it but that didn't work either; I can't connect it as a disk then format it that way because they took out 'mass storage mode' on this firmware.
I then tried to flash a stock ROM in Odin but every time I tried it would fail until I used Odin.v1.3, but guess what, it rebooted itself and my entire tablet is still exactly the same.
(the option was on AP ram in v1.3 not AP nand I don't know if that makes a difference.)
If anyone can point me in the right direction I would appreciate it so much. I have been trying for weeks to fix this and I just don't know what to do anymore, I tried on another forum but nobody answered me.

Everyone else gets replies and I get zilch; amazing. I don't know what it is that is preventing my tablet from wiping itself but it refuses to clear the current data no matter what way I try (ROM, factory reset, computer format). If someone could just tell me what that is and what I have to do about it that would be grand.

You mention "rooted " but you don't mention what current rom or past roms that you may have flashed, you could have some sort of rom cluster [email protected]$k going on in your tab but NO one else will ever be able to help because of lack of INFO or history.
Pp.

I standard rooted it from Odin. This is my first ROM I am trying to flash. I just need to know what would prevent a tablet from rebooting itself properly. Factory reset, format and flash is not working so I must assume that rebooting is the issue here.

If you are running stock rooted rom and having issues like this the only way out is reflashing the stock firmware complete (not just a rom) and see if that fixes it before you try any other roms.
If you can get into download mode thats the fix.
Pp.

To flash it completely do I need more than an MD5 file? (I also have the partition file for my model). Another question, if the tablet is having issues with the reboot after a flash, will updating from a microSD with a zip help? Thanks for the advice.

Cant flash Cyanogen, recovery faulty & weird crashes in stock on refurbished Nexus 5

Cant flash Cyanogen, recovery faulty & weird crashes in stock on refurbished Nexus 5
Hey guys,
so I recently got a "refurbished" replacement for my Nexus 5 and I decided since im starting out fresh (can't access the data on the old one), I'll try out Cyanogen mod.
I can assure you that I followed all the instructions exactly. At some point I checked every download for his checksums and all were ok.
Each time I started the process by flashing a factory image (flash-all.bat), to have a clean start.
I also tried to wipe cache/dalvik cache/data afterwards, but not always. This didn't change the behavior.
These things happened to me while trying to accomplish the task, and working around the issues as they arised:
Flashing TWRP: High (3 of 4) chance that TWRP wouldn't even start up, the phone would hang and just flash the TWRP background picture on screen.
When I did get through to TWRP, applying the Cyanogenmod .zip got stuck at "patching system image unconditionally". Let it go on for hours.
I figured that TWRP was broken and tried Clockworkmod instead. CWM at least always started after flashing it. But same as TWRP, it failed in installing the Cyanogenmod .zip. I tried putting it onto the phone by going into the stock android and then through adb push command, but also through sideloading directly into CWM.
What I noticed when going into the stock ROM was, that a lot of Google processes were failing during the initial setup (where it wants to know ur WiFi, date, Google acc, etc), like Maps, Settings, Play Services, and some others. Sometimes they were failing so hard it was impossible to type in the WiFi passphrase because the notifications of different "xxx has stopped working" were coming to fast, sometimes not a single one was failing. I could not find any pattern to this. When they were failing so hard I couldn't get through the initial setup I would just flash the stock again, until I got only some of them failing, or none at all.
Back to CWM and installing the Cyanogenmod .zip:
It failed with different errors. I got status 0, status 1, I think I once got status 6 or 7, but half of the time it hanged exactly where TWRP was hanging. The errors were random. After getting status X, I would sideload it right again, to get other status Y, sideload again, to get the hang. Could not recognize a pattern.
During this I switched USB ports, and cables, and even tried using my laptop instead of the desktop. One of the cables was faulty, it didn't even allow a connection, but any other setup showed the same behaviour.
Is there anything else I can/should try? Is it my fault, or is the phone bad?
Assuming the phone is bad, I suppose I still could get a stock running without the crashes, so it would _feel_ like the phone is alright (which is what Google probably did before sending it out again as "refurbished"), but I think there would be errors in the future, also I don't want a phone with such an uncertainty. Would they swap it? Also, it is a LG-D820, which means it might have issues with european LTE, haven't gotten to trying that out since I don't use LTE right now, nor will I in the near future.
Best regards,
napster

napstr said:
Hey guys,
so I recently got a "refurbished" replacement for my Nexus 5 and I decided since im starting out fresh (can't access the data on the old one), I'll try out Cyanogen mod.
I can assure you that I followed all the instructions exactly. At some point I checked every download for his checksums and all were ok.
Each time I started the process by flashing a factory image (flash-all.bat), to have a clean start.
I also tried to wipe cache/dalvik cache/data afterwards, but not always. This didn't change the behavior.
These things happened to me while trying to accomplish the task, and working around the issues as they arised:
Flashing TWRP: High (3 of 4) chance that TWRP wouldn't even start up, the phone would hang and just flash the TWRP background picture on screen.
When I did get through to TWRP, applying the Cyanogenmod .zip got stuck at "patching system image unconditionally". Let it go on for hours.
I figured that TWRP was broken and tried Clockworkmod instead. CWM at least always started after flashing it. But same as TWRP, it failed in installing the Cyanogenmod .zip. I tried putting it onto the phone by going into the stock android and then through adb push command, but also through sideloading directly into CWM.
What I noticed when going into the stock ROM was, that a lot of Google processes were failing during the initial setup (where it wants to know ur WiFi, date, Google acc, etc), like Maps, Settings, Play Services, and some others. Sometimes they were failing so hard it was impossible to type in the WiFi passphrase because the notifications of different "xxx has stopped working" were coming to fast, sometimes not a single one was failing. I could not find any pattern to this. When they were failing so hard I couldn't get through the initial setup I would just flash the stock again, until I got only some of them failing, or none at all.
Back to CWM and installing the Cyanogenmod .zip:
It failed with different errors. I got status 0, status 1, I think I once got status 6 or 7, but half of the time it hanged exactly where TWRP was hanging. The errors were random. After getting status X, I would sideload it right again, to get other status Y, sideload again, to get the hang. Could not recognize a pattern.
During this I switched USB ports, and cables, and even tried using my laptop instead of the desktop. One of the cables was faulty, it didn't even allow a connection, but any other setup showed the same behaviour.
Is there anything else I can/should try? Is it my fault, or is the phone bad?
Assuming the phone is bad, I suppose I still could get a stock running without the crashes, so it would _feel_ like the phone is alright (which is what Google probably did before sending it out again as "refurbished"), but I think there would be errors in the future, also I don't want a phone with such an uncertainty. Would they swap it? Also, it is a LG-D820, which means it might have issues with european LTE, haven't gotten to trying that out since I don't use LTE right now, nor will I in the near future.
Best regards,
napster
Click to expand...
Click to collapse
Hi.
According to what you say, it seems an hardware problem of you phone. Don't know if it may help but you can try installing an older factory image (for example kitkat) and seeing if the "force closing" problems are still there. If your phone is ok it should be able to run a factory image at least.

Download the nexus root toolkit, create a nandroid backup, then when either in CWM or TWRP wipe everything off the phone then try to flash a ASOP rom like Cataclysm if nothing else works then I don't know how to help sorry-.-

So I tried to get the stock ROM up and running again, and it seems even that is not possible. Several processes keep crashing during various tasks, even when idling. After having a short chat with Google Support about the issues I got an RMA offered, so things are cool. I locked the phone again, set the tamper-bit to false and wiped everything.

One PlusOne recovery loop- Help needed

Hello, I need serious help with my phone.
So, after a long while of having my phone rooted, and had a case of boot loop with twrp, I decided to go back to stock os and hung up the root days. I thought i did it right by getting a stock os and flashed it, and it worked for couple months, until yesterday.
My phone keeps going into Cyanogen Recovery, I tried rebooting so many times, once it did boot up to OS, but it went back after i restarted phone or it died.
Now I can't no longer get back, I thought factory resetting will work but it didn't. (Tried both wipe cache partition and Full factory reset option from the recovery) I found unroot your phone toolkits, thinking it could help fix my problem and just unroot/ give me back to OS (I wished i found this before flashing that custom stock rom).
But the toolkit doesn't work for me, it finds adb devices, but it cant find fast boot devices, because my phone cant even go into fast boot.
I tried manual, and the option from the recovery, it keeps going back to recovery. I have an option for apply update, and then apply from ADB, that was the only way for my pc to recognize my phone from adb devices. Any clues on how to fix?

Hi !
I may suggest you this thread https://forum.xda-developers.com/oneplus-one/general/tool-oneplus-one-return-to-stock-t2970390
Good luck !

xanthrax said:
Hi !
I may suggest you this thread https://forum.xda-developers.com/oneplus-one/general/tool-oneplus-one-return-to-stock-t2970390
Good luck !
Click to expand...
Click to collapse
Will try, Ill respond back if anything happens!

Hmm I'm still having trouble because, I can't get into fast boot for some reason. It's keep going back to Cyanogen recovery. It has the option to reload into bootloader, but goes into cyanogen recovery again.

There is an option in dev options, uncheck the "update cyanogen recovery" and flash twrp again
Sent from my SHIELD Tablet using Tapatalk

Stuck at cyanogenmod animation

Hello,
I am brand new to this forum and to android problems.... so forgive "silly questions".
I got a used tf300t which was reset back to factory settings.
I installed the dolphin browser and the last thing I did was installing the opera mobile browser.
Since that the cyanogenmod animation pops up right at the boot process and now and then it finishes booting, but when I wipe the screen in order to unlock it the cy-animation appears again.
Yesterday I got an error message that a system process was shutdown with a java null pointer exception for ..... any language process. (did not note the error message unfortuanately).
This brought to my mind that I changed some keyboard setting for the german keyboard layout and this is very likely the cause of the problem.
Now I wanted to reset the device back to it's factory settings, but I cannot boot into the recovery mode. Pressing power- and volume down button just flashes the screen with the asus logo but when I release the buttons, the cyanogenmode animation again appears.
So how can I "hard-reset" the device and btw. is this cyanogenmod thing really necessary?
thanks a bunch in advance and cheers
sabine
update: can now boot into TWRP
update#2: I killed it
I used the wipe option (think it was called this way) for a factory reset - and now it is stuck at the asus logo while booting.

Connect to a PC with cable, see if ADB recognizes it.
If it does, issue (in terminal/command line):
Code:
adb reboot bootloader
Wait for it reboot.
Verify fastboot connection
Code:
fastboot devices
If it is recognized, you need to re-flash latest stock firmware (blob), that can be found on Asus website. Make sure you get the right (geo)version for your device (ie: US/JP/WR...)
To flash the stock firmware, find the directions on this forum.
Sent from my TF300T using Tapatalk

sorry for the delayed answer, but thank you soooo much, I will try it out immediately. However befor I got that troubles I connected it to a PC but it did't get recognized.
Well we'll see...
to be continued
I got it, I got it, I got it
the problem was a different one called cyanogenmod.
When resetting the device the cyanogenmod got uninstalled and therefore restarting was not possible.
I found a backup file of the cyanogenmod and reinstalled it ... and it works
thanks a bunch for your help