I have a Verizon S5 rooted with towel root and no safe strap.
Twice I've tried to restore white user apps and green user data with titanium like I've done with every device I've upgraded to. Both times I've gotten stuck in boot loops where it gets fully booted and to my launcher screen and then reboots. I can't seem to get it into safe mode either.
I haven't done a second restore yet, so it's still stuck in a boot loop right now.
Thanks in advance for any help.
Related
I rooted my phone awhile back and everything has been good so far until i tried to install a google wallet apk that has left my phone unable to boot. I know my phone isn't bricked as it charges and still boots but only up to the att logo and then its frozen there. Im kinda a noob when it comes to android as this is my first one. Is there anything I can do?
I tried restoring it back to factory data and it still doesn't boot past the ATT Logo.
NVM: Just had to wipe cache partition and it booted right up.
Last night after a good night of working with my tablet out on the job I came home and noticed it was running a little sluggish so I rebooted it. It then proceeded to hang on the bootloader screen. I tried flashing into recovery and wiping and reinstalling but it still stays hung up on the bootloader screen. Getting into the recovery boot loader it says the secondary kerlel akb has an issue or something. Is there a way to Odin this thing back to stock? It's not totally bricked I can still get into recovery just can't get it to boot into the second kernel or whatever it means. I can get the exact terminology if someone needs it but I have been bricked worse than this before its just weird it won't fix itself after I re install a new ROM.
Sent from my A100 using Tapatalk
I am on the Skillraz V8 boot loader to be exact, and thats the first screen it gets stuck on..
I just tried flashing a stock un rooted ics zip but it still hangs on the first screen after rebooting after the install, which seemed to take ok... and it doesnt change my recovery or anything back to stock.
So I was running CWM (Philz) I believe, and I had been running into issues while on rooted 4.2.2 D800 stock ROM. There were force closes and random reboots, etc. I've only installed xposed mods. I've also used android tuner to adjust some of the build.prop and kernel presets.
However, after my phone got stuck in what I thought was a boot loop, I finally got it up and running. What happened next was odd. I tried booting into recovery -> the "LG" splash screen showed up and it went into another infinite boot loop.
I'm assuming I somehow corrupted or lost my recovery. Any advice on what to do? I don't know if I should follow the original instructions for flashing a recovery here - http://forum.xda-developers.com/showthread.php?t=2633150.
Edit: Jesus christ my phone infuriates and confuses the hell out of me. After attempting to enter the recovery again, I am now stuck in a permanent boot loop. The last time I fixed it was by turning my phone off....and then *WAITING*.
What? That doesn't make sense you say? Of course it doesn't. But that's still what worked. I waited 12 hours, and then tried turning it on again. When I did, oh look, the AT&T screen!
CONFUSING. help please...
Double edit (Hard Mode): Going into download mode when I'm in this constant bootloop = nothing happens. That little icon that says "Download Mode" with the 5 blue circles just stays there, and my laptop ends up not recognizing anything. This happened the last time too, and all I was able to see on my laptop was "QHSUSB_BULK". I thought this meant that I would have to do a complete wiping process through Linux (found on another thread somewhere), but apparently waiting 12 hours also fixed the problem.
I have Cyanogenmod 11 installed in my device, and I tried encrypting it. Everything was ok, it went til 100 % and passed the Samsung Galaxy S3 Neo startup screen, but now it's stuck in bootloop, with the Cyanogenmod blue arrow going in circles. It's been like that for more than 20 minutes, so I know it exceeded it's time of booting. I encrypted my phone 2 times already, the first time with the settings in Cyanogenmod, and it got stuck in bootloop, so I took out the battery and put it back on booting my phone in recovery mode (I use TWRP), and formatting the data on my phone. All the data was wiped. the second time I encrypted the phone using terminal emulator, and the same thing happened: it's stuck in bootloop. Now, I'm not asking how to unbrick my device, because that I know, I'm asking how can I encrypt it without it getting stuck in bootloop.
So pissed off and annoyed now....
Attempted to upgrade to marshmallow, then tried root over and over again. I get that it's a wip, but no such luck. Eventually I got annoyed and decided to just wait so I tried downgrading back to 5.1.1. For some reason now trying to root that results in boot loop as well (even tried older supersu). After a couple attempts with no such luck, tried to install stock back and now before even trying to root, the device doesn't want to boot up properly anymore.
I tried fastbooting bootloader, boot, recovery, and system, once I try to staRte up normally, android boot logo goes through but the first startup "upgrading apps" goes through its list and right after finishes, says "starting apps" but almost immediately boots back to the boot splash screen, where the process repeats itself over and over.
Trying to reflash everything results in same issue now. I've tried at lEast 4 times. Have I bricked my brand new nexus player?
Hoping for some answers so I can sleep on it. Pissed off and annoyed now. Ugh.
Figured it out. Didn't know how to bring up commands in recovery mode. Had to factory wipe system and cache.
Sorry for the wasted post. Mod please delete this if possible. Thanks.