While I was playing with my TF700 the other day I accidentally put it upside down resulting in pressing (& holding) the power bottom & volume down .. the device restarted into "Safe Mode"
I tried to get rid of it, but apparently I did something stupid which resulting in boot logo loop (the device is stuck at the second ASUS screen and refuses to boot)
* Note my device is Unlocked & I'm running the latest CleanRom version and I am kinda' experienced user :silly:
Anyway I googled this and I tried the following steps with NO success:
- Cold boot
- Wiping caches
- I also tried to re-flash a rom
which left me only with formatting & wiping data, BUT I tried this thing and it actually worked!
From TWRP I restored my last back up (which was a bit old) But whatever, It actually worked! and I have no problems whatsoever, everything seems to run as before, I also tried to reboot the device and it's still working!
I felt I should share this info with you, it might help someone :highfive:
Related
[Update 4/3: Logs] N5 works normally -> stuck on splash screen -> have to reflash ROM
My Nexus 5 is having a problem that is just confusing the hell out of me.
To summarize the issue...
1. Phone will get stuck on "Google" splash screen (written in white) on bootup.
-at this point, I can reach bootloader and recovery
-clear cache/format cache does not alleviate problem
-factory reset does not alleviate problem
-fastboot flash-all does not normally alleviate problem
-only flashing a ROM via TWRP works
2. ROM flashed via TWRP, things work like normal for ~4-24 hours. At some point, there will be a random reboot. Usually, this is while under stress (playing a game, updating apps). It will reboot normally and continue to work like normal for some time. But it's a ticking time bomb. There will be another random reboot at some point, often while idle - definitely not workload-related. This second one will get me stuck on the Google splash screen again, with the only way of fixing being re-flashing the ROM via TWRP.
These symptoms are basically the same regardless of the ROM - I've tried factory images, a stock-ish ROM with Gapps removed from XDA, and CyanogenMod. It seems like it could be a hardware problem, but I don't have a clue what it would be since it is so consistently fixable, albeit temporarily. Does anyone have any troubleshooting suggestions or a clue as to what part of the phone is likely failing?
Post logs.
Elluel said:
Post logs.
Click to expand...
Click to collapse
Okay, so this afternoon I went to check on it after spending some time on the charger. The LED was lit, so I thought things would be fine. It just wouldn't wake up. It wasn't responding to various button presses, but the LED turned off after I held the power button. It took a lot more attempts than normal to get to fastboot, but eventually got there. I used fastboot boot to get to TWRP and retrieved last_kmsg, kernel_log, and logcat. Logcast was empty. Here are pastebins for the other outputs.
last_kmsg: http://pastebin.com/z2KG2aHW
kernel_log_output: http://pastebin.com/v7TZZKeb
Thanks for the help!
I'm going to bump this one time, since there are now logs posted which I think might provide some clear insights to those who know how to interpret them.
Hey, my phone has been playing up and generally malfunctioning lately. It seems to work fine for a day or so before freezing, and either rebooting itself or forcing me to manually reboot it using power + volume down. This seems to send it into a bootloop where it generally freezes during the Samsung animation with the pulsing squares. This sequence continues with me manually rebooting, also trying to boot to safe mode and to recovery and after various attempts, i successfully got into recovery without it freezing on the blue android.
I then decided to factory reset as a last option, having looked around on forums for solutions. However, I now do not know what to do as it seems to have frozen during the factory reset. I dont have screenshots but the script reads as follows :
dm-verity verification failed. . .
-- Wiping data. . .
Formatting /data. . .
Formatting /cache. . .
It has been on that for the past 30 minutes and so i have assumed it has frozen. I'm afraid to force another reboot in case it is accessing memory, any suggestions on what to do?
It is up to date on fully stock software, has never been rooted and i have never attempted to do so. Also only around a month old.
Any help would be appreciated, thanks
I did not try to perform a factory reset yet, but my S6 shows the same instability issues.
Random self reboots with getting stuck at the boot animation.
I furthermore cannot enter the stock recovery mode (get stuck at full cyan screen with android logo), only can access the ODIN mode atm.
Booting that device atm is a hit and miss.
(everything stock, never touched that device in the XDA way! )
Update: I had to repair my S6 as instability increased even more.
Samsung licensed repair shop exchanged the mainboard of my S6.
All is fine again (except wireless charging, but I guess they broke it while repairing)
Hi, I bought a used Nexus 5 and it has been causing quite some problem when booting. I flashed Cyanogenmod in it and it works fine for a few days. After that it keeps having the same problems in the following order:
- It would restart on its own, sometimes some random app will fail functioning (it's never the same app).
- Turns off on itself without restarting. Can still be turned on normally.
- From there it gets worse and start bootlooping. On CM it loops around the part where it initialises the apps. On stock its the colourful stuff that happens right after the Google logo.
- Finally it just gets stuck in boot. On CM it's stuck where it initialises apps while for stock it turns off right after the Google logo appears.
I have tried the following:
- The persist partition fix described at https://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
- Cleaning the power button and made sure it wasn't stuck.
- Re-flashing CM, did a checksum to make sure the files are okay
- Went back to stock, did a checksum too.
It's a used phone so I have no idea what it went through in the past. Anything I can do to fix it?
Try running the phone with a stock ROM without root. If the problem still happens, it's probably a hardware problem.
It didn't have root but I flashed a factory image (plus another round of factory reset too) and even locked the bootloader + reset the tamper flag this time. It's working fine now but the problems normally start a few hours/days later so I can't be sure at the moment.
If it does fail again which hardware is the one with the problem? The warranty's long gone so will it be easy to buy a new part and replace it myself?
The cheapest solution may be to buy a used Nexus 5 with a smashed screen and working internal components to swap out components.
Hi,
since my old M7 is having more and more annoying issues, I tried to move to a One A9.
The problem:
The phone gets stcuk on LOS boot screen. Looks like it's loading but it never finishes and I can't even turn it off by holding power button pressed for 10s, 1m or even 10m!
BUT this happens only sometimes! Last night I just left it in this state to get the battery empty and this morning it was turned off. "On the way" to recovery (TWRP 3.1.1) I pressed the wrong button and it rebooted. Without any issues! Used it all day until I wanted to reboot it to insert a microSD-card. Since then: stuck on bootscreen! Can't get out...
Any ideas?
What I did:
Unlocked the phone
Factory reset
Installed TWRP
Flashed LOS 14.1
Flashed Magisk 14.0
Help appreciated
Somehow I'd consider this thread as solved:
I went back into TWRP and:
- formatted DATA
- made a full wipe
- made another full wipe
Now suddenly I don't get neither bootloops nor "Can't mount" errors in recovery (which I forgot to mention in the opening post :silly
I write "somehow" since I have formatted DATA before, as well as made a full wipe, because I couldn't even install LOS before that
UPDATE: I have finally managed to get my phone working again! Am now currently re-downloading all my apps and transferring all my files back to my phone, running AOSPExtended (https://forum.xda-developers.com/oneplus-one/development/rom-aospextended-rom-t3732194) with OpenGApps. I'll write the steps I took to figure this mess out at the end of this post for anyone who might encounter the same problem in the future. :good:
So last night I left my phone charging overnight from 54% as I was downloading a couple of files (my internet is 1Mbps or 125KB/s). I've done this a couple of times before with no problems what so ever. But this morning I woke up and my phone was in a boot loop. I've tried everything I can think of and everything I could find on these forums, but to no luck. I am at my wits end and I have no clue what to do except to do a full factory reset, which I'd rather not do as its been a while since my last backup and I would lose a lot of precious files...
My Phone: OnePlus One 64GB Sandstone Black, purchased in August 2014.
ROM: cm-13.0-ZNH5Y-20161105-STABLE-Sultan-bacon
Recovery: TWRP+3.0.3-2-TugaPower
Firmware: bacon_firmware_update_2016_1-25_.4.0.1.c7-00011
The boot loop itself is odd, I'll describe them separately here.
-I can boot into fastboot, but not while the USB is plugged into my PC. I have to boot into fastboot, followed by plugging it into my PC. If I try to boot into fastboot while it is plugged in, the screen goes completely black and goes back into the bootloop. However, the phone shows up in Device Manager during the black screen.
- I can boot into Recovery, but the phone automatically reboots and goes back into the bootloop after a few minutes. One thing I have noticed is that if I let it reboot by itself, all the settings reset (including the confirmation to allow modifying of files when you first boot into recovery). But if I manually reboot back into recovery, the settings remain the same; atleast until it reboots automatically again.
Here, I'll list the things that I have tried to no avail:
1. Following this post - https://www.reddit.com/r/oneplus/comments/3izejg/so_youve_just_bricked_your_oneplus/, when I try to wipe Dalvik cache and cache from recovery, the phone goes right back into the bootloop
2. I tried flashing a newer version of TWRP (3.2.1-0 and 3.2.1-K2). After flashing I try to boot into recovery but the TWRP loading screen displays, and then goes right back into the bootloop. It wont even let me into the main menu.
3. I tried flashing a ROM through fastboot (via this post, https://forums.oneplus.net/threads/guide-oneplus-one-flashing-fastboot-recovery.301131/). The phone still remains in a bootloop.
HOWEVER, if I flash my previous recovery (TWRP+3.0.3-2-TugaPower replacing the stock cyanogen recovery from this method), my phone manages to get past the 1+ screen, and goes through my custom power on screen, and reaches the "Android is starting... Optimizing app 1 of 67." But it never gets past app 1, freezes, and then reboots. So now it's stuck in this "extended" bootloop thing.
What I want to know: is there anyway to fix my phone, or will I have to lose all my data and do a full factory reset through the ColorOS method? If anyone has any experience with this or knows a way to help, please don't hesitate!
Thank you in advance.
WHAT WORKED FOR ME:
After following the steps in this post (https://forums.oneplus.net/threads/guide-oneplus-one-flashing-fastboot-recovery.301131/) my phone was booting up, but was kicked back into a boot loop after freezing at the "Android is starting.. Optimizing app 1 of 67" screen. However, the recovery was now the default CyanogenMod recovery. I then re-flashed my previous recovery (TWRP+3.0.3-2-TugaPower) from fast boot, and it was now stable (no more auto-reboots). From there I made a backup off all my files onto my PC before proceeding. After that, I did what this post said (https://www.reddit.com/r/oneplus/comments/3izejg/so_youve_just_bricked_your_oneplus/) and wiped Cache + Dalvik cache. This allowed me to boot all the way past the "Android is starting" screen. However, the phone was still rendered unusable as there were non-stop notifications saying various apps had stopped working. I then booted back into recovery, downloaded and pushed a new ROM and GApps package on to my phone, wiped system, data, cache, dalvik cache, and installed the ROM and GApps pacakge, clearing the cache one more time before rebooting. Everything is working beautifully so far and I could not be happier! I hope this helps anyone else who encounters this problem, Cheers!