Let me just start by saying that I really don't know what I'm doing. There was a lot of bloatware on this phone that I wanted to remove and apparently the only way to remove it was to root. I downloaded kingroot and after deleting some apps I rebooted my phone but it did not go past the blu loading page. I then figured out how to get into recovery mode where I reset to factory and cleared cache and tried rebooting. This time I got past the blu loading screen and into phone setup however as soon I click the final next it brings me back to the blu screen. Anyone have any suggestions on where to go from here?
Related
So I was modding framework-res, and somewhere I did something wrong and my phone will no longer boot. I can go into recovery but I did not install any extra recovery apps, so I can't do many things but wipe data, restart, etc. I've tried every option in the recovery but nothing works, it still doesn't boot.
I would go to the att store to have it exchanged but my screen is cracked so I can't do that.
is there anything I can do? I just got this phone and I don't want to have to buy another one. Please, any help would be greatly appreciated.
http://forum.xda-developers.com/showthread.php?t=1535769
Thanks, I'll try that and report back. Hopefully that ones works, I've tried other tutorials but none seem to do a thing
put that beast in download mode, and reflash a kdz...should bring it to a stock form.
just make sure after your flash, boot into recovery if you are getting a boot loop, and clear data / cache option...then reboot.
Let me start by saying,this isn't my first rodeo,i've been rooting since the beginning of the G1,but this one has me stumped.
Ive got a Moto Atrix HD, rooted and bootloader unlocked running Batakangs Deodexed stock. It started feeling kinda laggy so I decided to jump into recovery (CWM 6) and delete the Devlik cache Battery stats etc. basically everything but user data so I didn't have to start from scratch. Ive done it in the past and it speed things up considerably with no ill side effects. So I did it thins time and immediately got the "unable to access recovery log/command" error. So I decided to reboot recovery and try it again and the same error came up as soon as it booted into it. I decided to just use rsd and do a complete fresh stock att install,but it wouldn't go to fastboot and rsd didn't see the phone neither did adb.So I tried a full wipe. Didn't work. So idecided to do a rom reinstall and see if that fixed it.nothing. So I tried another wipe and this time it wouldn't boot back into recovery,stays stuck on the first boot screen. I even went through the trouble to remove the back and unscrew the battery and do a battery pull with no luck. During all this I had RSD pulled up and it never saw the phone to give me something to work with. Im kinda stumped on this one,i can normally figure it out without issues,searched here and I didn't see anyone with the same issue exactly. Im open for ideas. Thanks
Updatek so I managed to get PhilzTouch recovery installed,and got Carbon installed. But still getting the error in recovery.Its finally booting at least tho....Finally got to use MythTools to reinstall the recovery and all is fixed..
TabascoTX said:
Let me start by saying,this isn't my first rodeo,i've been rooting since the beginning of the G1,but this one has me stumped.
Ive got a Moto Atrix HD, rooted and bootloader unlocked running Batakangs Deodexed stock. It started feeling kinda laggy so I decided to jump into recovery (CWM 6) and delete the Devlik cache Battery stats etc. basically everything but user data so I didn't have to start from scratch. Ive done it in the past and it speed things up considerably with no ill side effects. So I did it thins time and immediately got the "unable to access recovery log/command" error. So I decided to reboot recovery and try it again and the same error came up as soon as it booted into it. I decided to just use rsd and do a complete fresh stock att install,but it wouldn't go to fastboot and rsd didn't see the phone neither did adb.So I tried a full wipe. Didn't work. So idecided to do a rom reinstall and see if that fixed it.nothing. So I tried another wipe and this time it wouldn't boot back into recovery,stays stuck on the first boot screen. I even went through the trouble to remove the back and unscrew the battery and do a battery pull with no luck. During all this I had RSD pulled up and it never saw the phone to give me something to work with. Im kinda stumped on this one,i can normally figure it out without issues,searched here and I didn't see anyone with the same issue exactly. Im open for ideas. Thanks
Updatek so I managed to get PhilzTouch recovery installed,and got Carbon installed. But still getting the error in recovery.Its finally booting at least tho....Finally got to use MythTools to reinstall the recovery and all is fixed..
Click to expand...
Click to collapse
I just jumped in and read your post. unfortunately, I had no chance to reply to you after I read the last line But it's nice to know my tools is helpful.
I factory reset my Glass today because it wouldn't connect to my phone (I switched roms so I needed to pair Glass again). After I did the reset it went into a boot loop. When it's on the "Glass is Updating" screen it can't be accessed via ADB, but I managed to figure out how to get it into the bootloader via the buttons.
From the bootloader I've tried erasing and flashing 16.2, 16.11, and 16.0 but it just returns to the same "Glass is Updating" screen when I reboot.
When I erase, I erase boot, recovery, system, userdata, and cache. When I flash, I flash boot, recovery, and system. I've tried with and without flashing userdata.
Does anyone have any ideas as to what could be wrong?
EDIT: Something really weird is going on. I ran the erase without flashing anything back on and did a reboot. I expected it to stop at the bootloader since there should be nothing to load, but instead it continues to go into the "Glass is Updating" boot loop.
EDIT 2: I've been doing a lot of reading and it sounds like there are more partitions than just the bootloader and the 5 that I have been erasing. My guess right now is that my device downloaded the 16.2 update into some other partition before I did the factory reset and now every time it boots it's running that update. I can't get much info from the device because I can't use adb.
I had the same issue when I tried flashing 16.2. I went back to XE12 and it resolved the issue. The whole point was to get away from the train wreck that is XE16.x anyway, so I'm just going to stay on 12 until the XE17 images are available - then we'll see if that release is any more stable.
davezack said:
I had the same issue when I tried flashing 16.2. I went back to XE12 and it resolved the issue. The whole point was to get away from the train wreck that is XE16.x anyway, so I'm just going to stay on 12 until the XE17 images are available - then we'll see if that release is any more stable.
Click to expand...
Click to collapse
That did it! I didn't try a version back that far because as far as I know mine had XE16 on it when I first got it.
Thanks!
So let me explain my situation. I decided to factory reset because I needed to clean up my tablet quite a bit. I did this and it decided to freeze on reboot. I waited 30ish minutes and it was still stuck, so I shut it off. It would not boot after that, it would get stuck at the second asus screen with load wheel. I went into recovery and did data/cache wipe. That allows me to boot once after everytime I wipe otherwise it will be a bootloop. I tried sideloading the firmwares on asus's support page NONE of them worked. I tried fastboot and adb and none of them were successful. I have a bunch of errors in the bootloader. I also have pictures of what it boots to. Aswell as the bootloader errors. What should I do, asus said I should rma but I dont have the money and I also rooted this thing which can be seen whenever I do su in adb it still asks for root. I have very few options anybody's word would probably be a help. Thanks
How I recovered
applerulez1 said:
So let me explain my situation. I decided to factory reset because I needed to clean up my tablet quite a bit. I did this and it decided to freeze on reboot. I waited 30ish minutes and it was still stuck, so I shut it off. It would not boot after that, it would get stuck at the second asus screen with load wheel. I went into recovery and did data/cache wipe. That allows me to boot once after everytime I wipe otherwise it will be a bootloop. I tried sideloading the firmwares on asus's support page NONE of them worked. I tried fastboot and adb and none of them were successful. I have a bunch of errors in the bootloader. I also have pictures of what it boots to. Aswell as the bootloader errors. What should I do, asus said I should rma but I dont have the money and I also rooted this thing which can be seen whenever I do su in adb it still asks for root. I have very few options anybody's word would probably be a help. Thanks
Click to expand...
Click to collapse
Please see what worked for me, when i got it a similar situation.
http://forum.xda-developers.com/memo-pad-7/help/unbrick-memo-pad-me176cx-t2987068#post58231184
ardluc said:
Please see what worked for me, when i got it a similar situation.
http://forum.xda-developers.com/memo-pad-7/help/unbrick-memo-pad-me176cx-t2987068#post58231184
Click to expand...
Click to collapse
I have given you the nickname android jesus in my household, my tablet is fixed now! I love you, thanks so much! This thread can be closed.
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..