Database Develop

S6 Stuck on Load

Hey guys,
I have been on 5.1.1 and rooted for about 2 weeks now (pretty much since it came out) with no problems at all. A couple days ago, my Netflix app stopped working; it freezes when trying to load videos. After reinstalling, clearing data, etc. didn't fix it, I decided to boot to recovery to make a backup and reflash. I used Nandroid Manager to boot to recovery, and now my phone is in a boot loop. It has the usual message "recovery is not seandroid enforcing" at the top, but if I try to boot into download mode, the screen goes black momentarily, and the same loading screen comes up again (and is still frozen).
My only thought is to wait for the battery to drain and hope a hard reset fixes it, but my battery was at 95% at the time...and I still don't know if I'll be able to get into download mode.
Any ideas?

Clear caches from recovery and reboot.
Sent from my SM-G920T

Were you able to fix this? I just upgraded to 5.1.1 rooted and Netflix won't work anymore. Stuck on the loading screen as well. I tried wiping cache in recovery and rebooted, reinstalling, clearing cache in app manager, nothing works.

Same issue
This sucks, I have the same issue and I didn't do anything different. I was running stock 5.1.1 with root and it worked, flashed xtresolite rom and it still worked, then today all of a sudden it's just stuck on the loading screen. I've tried unrooting and reverting to stock....nothing. I even logged on to my netflix via laptop and deactivated all my devices since, I assumed I maxed out on the registered devices....still nothing. Hope someone can figure this out, I know in the past Netflix did not work with some custom Roms... But I don't think this is the case considering it doesn't even work when it's stock and unrooted.
***Netflix only works on the TV when it is casted via Chromecast from my Galaxy S6

I have a tab s2, but the same story...running stock 5.1.1 with root since xmas morning...the last 2 days I get stuck when I try to start a video. Can't seem to find an answer.

is there a fix
PWEB18 said:
Hey guys,
I have been on 5.1.1 and rooted for about 2 weeks now (pretty much since it came out) with no problems at all. A couple days ago, my Netflix app stopped working; it freezes when trying to load videos. After reinstalling, clearing data, etc. didn't fix it, I decided to boot to recovery to make a backup and reflash. I used Nandroid Manager to boot to recovery, and now my phone is in a boot loop. It has the usual message "recovery is not seandroid enforcing" at the top, but if I try to boot into download mode, the screen goes black momentarily, and the same loading screen comes up again (and is still frozen).
My only thought is to wait for the battery to drain and hope a hard reset fixes it, but my battery was at 95% at the time...and I still don't know if I'll be able to get into download mode.
Any ideas?
Click to expand...
Click to collapse
Hello....Were you ever able to find a fix for this? I have had no problems with Netflix until today. I haven't done anything new or changed anything on my phone, but all of a sudden today it won't load any shows. Netflix opens fine and I can browse, but when I try to play anything it just stays on the loading screen. I'm not having any trouble with any other apps (Hulu, YouTube, games, etc.)

I'm stuck in the same boat, stock rooted (unikernel) LP, and now stock rooted MM..

Stuck in an odd bootloop, can't get out of it (SGH-T599N)

Hello all. I have been in the Android root community for a little over three years, and even after tinkering with the various devices I've owned since, I cannot get my T599N to come out of its current bootloop.
A background: I had been checking some things in my settings app (running stock, rooted), and I ended up just force closing the settings app to get out of it quickly. Well, this action deleted all of my text messages, and later on it removed my notification bar and made my wallpaper go black. I ended up booting into recovery mode to try and clear the cache. After it cleared, I rebooted, and bam, the bootloop started.
Now, here's what's interesting. The phone is in a bootloop where it displays the first boot message (SGHT599N Galaxy Exhibit or whatever), and then it tries to boot into cwm recovery, displays the loading screen for that for 2 seconds, and just reboots again. I've tried installing a stock rom from ODIN with no success. The rom apparently loads onto the device but it's still in the bootloop. After this, I tried to install philz recovery to try to install a zipped rom to get the device to somehow boot. I tried to factory reset it for installing purposes, and it just reboots. The device will literally clear everything but /data, so that makes me think that it may be a file system problem. I really need to get it to work, as I am out of a phone right now.
Does anyone have any suggestions? I've tried everything I know.

Tried to install OTAvwith TWRP, phone boots normally but then reboots to recovery

I have a Moto G XT1072. I had unlocked the bootloader, installed TWRP and rooted it a while ago. I did not install any custom rom.
I was completely unaware of TWRP's lack of support for OTA upgrades, so when my phone notified me that there was an update available, I was like "oh, cool, okay" and downloaded it.
a) The download finished, the phone rebooted and TWRP recovery popped up.
b)"Mh, I guess I have to find the update file and flash it, probably"
c) Of course I didn't find it, so I googled and found out that if I want to install an OTA update I have to flash back the stock recovery and I might lose root. "Not worth it, thanks, maybe when 6.0 comes out"
d) So I rebooted the phone. Boot screen with motorola logo shows up, phone boots normally, I insert my sim card pin, set the alarm for tomorrow morning (6:00 am, fml) and *poof*, phone shuts down and reboots in TWRP.
e) back to point d.
Recap: I downloaded the update but I didn't install it, phone boots normally (I can even go in settings), but after 30 seconds it shuts down and reboots in TWRP. I do not care about the update, I just hope I can avoid re-rooting or even wiping.

I've got the exact same problem as you. Stupid to not have thought this could've happened with TWRP installed. Additional problem is, I have removed everything ''root-related'' (adb, fastboot), because I thought I wouldn't need it anymore. TWRP is obviously still on my mobile, but that's about it. I have already made a backup in TWRP (don't think it will help, because I'm afraid it will backup as boot trap), but who knows if it may help.
Back to the point, I'm a noob with rooting, I don't even know how I've managed to root it in the first place, but I'm stuck with the same problem as you are but without the required tools (at least, that's what I think)...
UPDATE: So my phone finished the backup, I turned it off to charge my battery, I fired it back up after an hour (normal way, not TWRP way), and it all of the sudden works again. It doesn't boot trap anymore and it seems like I'm able to use every function properly again. After those 30 seconds (where it usually rebooted), I now got the message that the installation had failed and that I should try again later. I don't know if there's any logical explanation for this or if this is pure luck, but I'm glad it's working again! I don't know if this will help for you as well ricvail, but I think it's at least worth a shot!

Need assistance reinstalling twrp

For a while I've been using the nonsense rom (provided on this forum) and it's worked fine. Just the other day however I tried turning on my phone, it would get to the boot screen with the animation of the android bot peeing on the apple logo and it would just play that animation over and over until eventually the phone turns off. I figured I just had to restart, but it was the same issue. After trying to reinstall that same rom, I had the same problem. I then tried different roms and the same issue with those, they would get to their respective boot animations and play them until the phone turns off, never going past the boot screen. The one rom that sort of worked with the cayonogenmod 12.1 rom, but the issue with that is after the boot animation, it appears to be starting the set up for the phone, but prompts me to enter a password, which I have no idea what it is. Doing a bit more research, it seems that there may be a problem with twrp and it not formatting (term?) properly.
As of right now, I've done a factory reset on the phone several times to no avail. I just need help getting this phone to work. I've tried looking at a few places and using adb, but the device wasn't found and I didn't have time to look any further because I'm busy with a project I'm working on and with moving. Some places I've looked said to put the phone into usb debug mode, which I can't do since i can't get past any of the boot screens.
Edit / Solved:
I went into twrp and instead of choosing "wipe data" i went to "format data" and that seemed to fix the problem. Although I did have an issue with the nonsense rom, it got past the boot animation, but then gave an error "unfortunately the process com.android.systemui has stopped". I instead installed the raptor rom and it's working fine.

please help a person who doesn't know much about ROMs, kernels, root and so on.

i'm in desperate need for guide please,
so i first off i had some questions (excuse my stupidity but i really couldn't find any answers around)
1) can an never-rooted android device's build number change or is it always the same? like with stock/official updates only?
2) my recovery mode (stock/system recovery) aborts every single installation file (official rom from the Asus website) without even opening the package, it's like i press 'install update from sd card' then as i press the zip file, it immediately says 'installation aborted' without even typing any other significations/steps, and the same happened for the kernals zip files too. so does that mean my recovery mode is corrupted or something is wrong with it?
3) i noticed some slight changes in my recovery since the last bootloop i had and had to use it back then, for example the dead android screen appearing after choosing the recovery mode, at first it used to say 'no command' under the dead android, but this time it doesn't say anything, just the dead android image only until i press power button and volume up to get the recovery options. so does that mean my firmware version changes since last time or my recovery is corrupted or it just means nothing?
4) is there aNYWAY to know my build number of a phone in bootloop (not rooted but bootloader unlocked)
so my initial problem is; i had my asus zenfone go zc500tg on march 2016. it was working so fine actually (using it like a default user not actually knowing anything about roms/flashing/recovery etc) until july of 2017 when i noticed my phone was a bit slow (out of the ordinary) and it used to get SO hot while using it normally and battery drained pretty faster than before, but i didn't know what to do tbh so i just kind of ignored something was off. but not long after these symptoms, the booting of my phone got slower and slower, until it reached its max by staying more than three hours just doing the 'optimizing apps' on the booting screen until it booted, so i thought it was a virus that would go away after a factory reset, and after the reset, it got worse, until it stopped booting and got into a bootloop. I panicked then because i didn't have the slightest idea what was happening until some internet searching guided me into the world of bootloops and custom roms and recovery. so i eventually managed to fix the bootloop and it worked fine for several months until it started to lag again and boot slowly and got the second bootloop, and that i fixed like the first one by installing the rom from the asus website then putting it on the sd card sand flashing it through recovery,
the third bootloop was quite the same, except that i did something additional in recovery mode, i pressed "backup user data" and that did a nandroid backup then i restored it smoothly after flashing the rom.
the fourth bootloop was a bit different, i as always downloaded the same firmware as the times before and flashed it and backed up user data too, but the odd thing that happened was me getting a message box that won't go away that said "unfortunately, the process com.android.phone has stopped" the phone worked but the sim cards weren't recognized and the message box was coming and going every second, so i noticed that the message box went away (nearly) when i got my sd card out, but still the phone app and the sim cards were corrupted,i thought the issue was from my sd card at first but i eventually, (coincidentally tbh) managed to fix it by doing the OTA update that was due, (that bootloop was fixed on the date of January 13th 2018)
then my phone was working so fine and everything was alright.
then shortly after (january 20th 2018) i was on whatsapp normally then suddenly ALL the things on my phone came crashing in front of me : TONS of endless message boxes saying things like "unfortunately, the process com.(any app on my phone) has stopped"
that i literally panicked and tears welled up in my eyes, so i rebooted the phone and while rebooting it did a (relatively quick) "optimizing apps" but as it booted everything was the dreaded same, all the apps crashing, then with the second rebooting was the current bootloop. i thought it was the same as before and just downloaded the usual zip file i use everytime but while flashing it (it did the same as mentioned in question 2 above) but it aborted instantly so i went and downloaded every rom there but it was the same so i went and tried the kernal zips too but always the same (i can't read my build number through the system recovery because it is like not fitting well in the screen si half the number isn't there that's why i asked question number 4)
so can anyone help me please? i'm in desperate need for help, i'm literally crying while typing this because i can't afford another phone and i'm so scared.

also is there a way to install custom recovery to not rooted device while in bootloop?
or if the system recovery was actually corrupted what do i do? :crying: