This isn't as much as a "help!" question because I got the tablet working again (by flashing a stock blob); it's more of an question to try find out if I can prevent this from happening again...
I was just browsing tapatalk when my tablet froze. I rebooted and saw the tablet kept rebooting to the Asus logo. Recovery didn't work (it kept rebooting after the recovery logo would appear) and the the ROM (KatKiss LP v29) wouldn't boot.
Flashing TWRP again with fastboot didn't work. I couldn't flash the ROM again or use my Nandroid... I ended up formatting recovery with fastboot, flashed a stock blob to get it working again, and then restored from there, but it was a pain.
So I'm curious if anyone can guess what may have happened and if there is any way to prevent it from happening again?
Related
When I flash merely anything, my tablet gets stuck on the Samsung boot logo (I have waited, and waited, and waited, until the battery dies). Sometimes even installing ClockWorkMod Recovery (official) will do this. But I managed to get the latest official CWM flashed. But I can't get ANY other rom to work. Even roms I have successfully flashed before.
Note: If it flashes it gets stuck at the Samsung boot logo. But I have also had it not flash sometimes too, giving me error code 7 in CWM which is an authentication/permission/certificate problem.
I am going to try right now using Odin to flash to stock, and work from there, maybe it will completely clean out any crap in the memory.
My tablet is the P3113 model.
Ok! So after flashing stock rom, then cleaning all the cache stuff, then attempting to install CM it fails with CWM Error code 7. And when I just reboot system, it gets stuck at the boot logo. Damn, I get stuck there without even flashing!!
Well, I may have figured it out..... ummm i guess *cough! cough!* I somehow changed kernels *cough! cough!* dang, my allergies! Hahaha, anyways, I flashed a kernel compatible with stock rom and cm10.1 and it has gotten past the flash of cm10.1 and seems to be booting up right now.
Hey guys, I've searched around and tried various things and I feel like I am just regressing this thing worse and worse.
Here's what I can recall about my situation:
SL101, rooted using nachoroot and put an ICS rom on it. not sure which. worked great.
decided I would switch ROMs one day and ran into the glitch where if you install too large of a file onto the sd card it reboots in the middle and you have a corrupt ROM.
ended up wiping a lot of stuff and I was stuck with no ROM, CWM recovery, and boot loop.
trying to get back to stock and sell the thing since I left it bricked for awhile and didn't use it much before anyway. so I tried ASUS's website for their stock file and it runs in recovery and I'm back to stock recovery but still a boot loop.
Not sure where to go from here, any ideas?
TLR- stock recovery, boot loop
Did you try APX mode?
http://forum.xda-developers.com/showthread.php?t=2089024
Root/CWM
http://forum.xda-developers.com/showthread.php?t=1689193
Last night, I downloaded the 6.0 update, copied the .zip to external storage, rebooted to CWM, and flashed it (successfully), then flashed SuperSU over it, cleared dalvik, and rebooted.
Since then, I'm stuck with the Nvidia boot screen. I can use Power/Vol Up to get in to fastboot, but when I try to boot back into recovery, the screen goes black, but goes back to the Nvidia boot screen instead of booting to recovery, even after flashing a recovery image to it via fastboot.
I can probably fix this with enough time and tinkering, but I just came back from a two week from vacation at work and don't have the time to futz around with this. Posting here in case someone already has an idea on what the problem is/how to fix this.
Update: I was able to get back into recovery using TWRP referenced in http://forum.xda-developers.com/shield-tablet/general/unofficial-update-original-shield-t3281541. Direct link is https://www.androidfilehost.com/?fid=24345424848487676.
I'm thinking this is a kernel issue.
This was a kernel issue. Flashing a older OTA (http://ota.nvidia.com/ota/data/post...wf-full_ota-36442_589.1541.20150826095201.zip) and booting normally, then rebooting to bootloader and fastbooting the CWM image worked. I'm restoring from a backup I took before flashing the update last night, then flashing TWRP, backing up, and trying this all over again.
Thank you, I was having the same issue :good:
Have the exact same issue, except that now, for some reason, I can't even get the device to turn on!
Okay I am in a situation. my Google pixel is constantly boot looping. I have tried custom roms and even stock ROMs and it keeps boot looping. I've done all the tutorials and troubleshooting threads and to no avail am I getting this to stop. My bootloader is unlocked and I cannot flash any firmware that is stock below Android 10. I thought with the unlocked bootloader you could flash almost any firmware. Does anybody have any idea on how to help me and what I could do?
After trying to flash an OTA or a factory image it keeps saying something about user data and then it says press any key to exit.
I finally fast boot twrp and sideload lineage 17.1. after flash it rebooted... usually twrp flashes and waits for you to pick reboot. Phone works but is it a matter of time before it does the bootloop again? Clicking fix bootloop recovery seemed to work.
My Phone was running Android 11 perfectly fine. Has been for about a week and a half, and I've decided that I don't like the OS. I was going to flash a custom ROM and went to create a nandroid before flashing. Literally all I did was boot into recovery and TWRP got stuck in a bootloop, the TWRP splash screen appears, crashes and then reappears about 2 seconds later, now when I try to boot back into system, TWRP appears instead and continues to bootloop. I can enter fastboot mode but that's all.
So far I've tried
Booting TWRP through fastboot. Failed another bootloop.
Rebooting through ADB. Boots into TWRP.
Rebooting Bootloader. Seems to do nothing.
Does anyone have any ideas on how to fix this ? It seems strange to me that something as simple as booting recovery could do this much harm. I also have a nandroid backup stored on the device from about a month ago, so the data loss wouldn't be THAT major, but I'm also not sure how I could access it without system or recovery access.
Hi , Which version of TWRP use? I think there is an update a new version TWRP 3.5.2 , Try to flash it. if its still not booting try to boot the original Boot of OOS11.
May be this threads will help you.
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
humood96 said:
Hi , Which version of TWRP use? I think there is an update a new version TWRP 3.5.2 , Try to flash it. if its still not booting try to boot the original Boot of OOS11.
May be this threads will help you.
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
Click to expand...
Click to collapse
New version does not work as well. Flash the stock boot img to get out of bootloop.
Jacobo123 said:
My Phone was running Android 11 perfectly fine. Has been for about a week and a half, and I've decided that I don't like the OS. I was going to flash a custom ROM and went to create a nandroid before flashing. Literally all I did was boot into recovery and TWRP got stuck in a bootloop, the TWRP splash screen appears, crashes and then reappears about 2 seconds later, now when I try to boot back into system, TWRP appears instead and continues to bootloop. I can enter fastboot mode but that's all.
So far I've tried
Booting TWRP through fastboot. Failed another bootloop.
Rebooting through ADB. Boots into TWRP.
Rebooting Bootloader. Seems to do nothing.
Does anyone have any ideas on how to fix this ? It seems strange to me that something as simple as booting recovery could do this much harm. I also have a nandroid backup stored on the device from about a month ago, so the data loss wouldn't be THAT major, but I'm also not sure how I could access it without system or recovery access.
Click to expand...
Click to collapse
Did your problem got solved?As i updated to A11 a few days ago and am facing the same problem since.Did flashing the new version of twrp worked for you?
Jacobo123 said:
My Phone was running Android 11 perfectly fine. Has been for about a week and a half, and I've decided that I don't like the OS. I was going to flash a custom ROM and went to create a nandroid before flashing. Literally all I did was boot into recovery and TWRP got stuck in a bootloop, the TWRP splash screen appears, crashes and then reappears about 2 seconds later, now when I try to boot back into system, TWRP appears instead and continues to bootloop. I can enter fastboot mode but that's all.
So far I've tried
Booting TWRP through fastboot. Failed another bootloop.
Rebooting through ADB. Boots into TWRP.
Rebooting Bootloader. Seems to do nothing.
Does anyone have any ideas on how to fix this ? It seems strange to me that something as simple as booting recovery could do this much harm. I also have a nandroid backup stored on the device from about a month ago, so the data loss wouldn't be THAT major, but I'm also not sure how I could access it without system or recovery access.
Click to expand...
Click to collapse
At first.- Stable TWRP is not available til now for OOS11
For TWRP to work your device must be decrypted.
This link will help you, will get full details
- https://forum.xda-developers.com/t/...-oneplus-7-pro.3931322/page-152#post-84727891
For more questions and help, please post in that twrp thread only
Regards