About a month ago my prime seems to have given up the ghost. Lots of ANR and processes stopping for no known reason. At the time I was rooted but still locked, been rooted for a few years. I did a factory reset and now I can't re-setup my google account because as soon as the boot finishes I get unfortunately com.google.process.gapps has stopped message. After the factory reset I rooted this time using DebugfsRoot_Generic_v2.3 and side loaded a root checker, busybox and SuperSU which all recognizes the root. When I try to boot into recovery (stock Android 4.1.1; Build number 10.4.2.18-20121122) I get the fallen down Android with the red triangle of death.
After all this I've decided to unlock and go the custom recovery/custom ROM route. I went to Asus and downloaded the unlock tool. Side loaded it and it installed fine. When I go to run the unlock the app gives the Unfortunatly Unlock Device Tool has stopped message.
I'm not without a tablet. I have a TF700 so I just want to explore so ROM's for the Asus Transformer line. Any suggestions to get my Prime unlocked and setup for customization would be great.
Thanks
Wow, this place is dead.
Related
I have had my Droid Incredible 2 rooted for several months now and have not had any issue. I do not have a custom ROM, just rooted to mainly use the wifi tether app, among other things.
Today, the phone shut itself down and attempted to install a software update. The update stopped after about 2 seconds and switched to the droid with the exclamation point (guessing error) and stayed there until I popped the battery out and rebooted it. Each time I boot the phone, however; it goes through this same process, so my phone is essentially useless at the moment.
I assume the upgrade is not working because of the root. If that is so, how do I go about correcting this problem.
Any input will help. Thanks!
So I have a totally stock Nexus 9, never rooted, unlocked, anything. I have experience with all that, on my Nexus 5, 7, etc. but was completely happy with my 9 and content to "just use it". Anyway, had encryption enabled, took the 5.1.1 OTA update the other day, and on reboot had constant process com.android.phone stopped error messages. As soon as you acknowledge, the message reappears. Between error popups, I was able to type in my passcode for the screen lock, and try to get into settings, clear caches, etc. Nothing worked. Decided a factory reset was best. No change, still constant errors. Did a factory reset from recovery and bootloader. Still no changes, same constant error. Tried to go through setup but after joining wifi, it sits at the "checking connection" page and goes no further - all with the constant error. It will not allow me to skip setup or skip wifi setup.
Can not flash factory image or do anything from fastboot because bootloader is locked.
Device is running latest bootloader for 5.1.1 but at the top of the bootloader screen it says OS-n/a. Is this normal?
Any suggestions or do I just RMA?
I have the same problem and found not way to get this fixed. Only wiping user data and reinstalling rom works. The problem returns when rooting and after the first reboot.
Since I´ve got an nexus 9 lte, it might be related to the radio image not included?
closetredneck said:
So I have a totally stock Nexus 9, never rooted, unlocked, anything. I have experience with all that, on my Nexus 5, 7, etc. but was completely happy with my 9 and content to "just use it". Anyway, had ...
Device is running latest bootloader for 5.1.1 but at the top of the bootloader screen it says OS-n/a. Is this normal?
Any suggestions or do I just RMA?
Click to expand...
Click to collapse
regards,
Dirk
Hello,
I got this Cricket phone, and mostly successfully had it switched over to be an AT&T phone. It was working well for awhile, then started freezing up from time to time, and I had to take the battery out to get a reboot. I did a factory reset, thought I had it fixed, then did a Kingroot. It was working well, again, for a little while, then started up again with freezing up, but now it was also sometimes not using data, or it said my data was not available. My husband's was fine, so I knew my account with AT&T was fine.
My intention was to uninstall the kingroot, then restore to factory, but after the uninstall of kingroot, it got stuck in Authentication Failed Error #9.
I have successfully installed drivers on my computer, and I am able to get it into Firmware update status, but my question is, I'm not sure what I should flash to the phone to have it work best with my AT&T service. Should I start back at the Cricket initial instal, or can I skip all that and go to a nice rooted ROM?
Thanks for your help!
Cynthia
[email protected] said:
Hello,
I got this Cricket phone, and mostly successfully had it switched over to be an AT&T phone. It was working well for awhile, then started freezing up from time to time, and I had to take the battery out to get a reboot. I did a factory reset, thought I had it fixed, then did a Kingroot. It was working well, again, for a little while, then started up again with freezing up, but now it was also sometimes not using data, or it said my data was not available. My husband's was fine, so I knew my account with AT&T was fine.
My intention was to uninstall the kingroot, then restore to factory, but after the uninstall of kingroot, it got stuck in Authentication Failed Error #9.
I have successfully installed drivers on my computer, and I am able to get it into Firmware update status, but my question is, I'm not sure what I should flash to the phone to have it work best with my AT&T service. Should I start back at the Cricket initial instal, or can I skip all that and go to a nice rooted ROM?
Thanks for your help!
Cynthia
Click to expand...
Click to collapse
What say you?
Hi, I rooted my galaxy s7 from att using this method, https://www.youtube.com/watch?v=GNInTlCpv8E
It worked perfectly and I had my new rooted phone! So a couple of days after the root one of my apps stop working and I cannot get it to start working, it was a pushup workout app, so I restart my phone and it gets into a boot loop stuck on the at&t logo. I was very sad as I did not back anything up so I wiped my phone using the recovery boot and signed in and re-flashed the root rom through odin and re-installed supersu and it worked perfectly again. The next day I have the same problem but this time with snapchat and instagram so I knew what was going to happen and I restarted and it did the same thing. This time when I went into recovery boot I noticed "dm-verity verification failed" in red at the bottom. As of now I am just going to do what I did last time and wipe and re-flash as I made a backup this time and just restore my phone and hope it doesn't happen again. If someone could please explain why this is happening and maybe help me fix it I would be so happy thank you!
UPDATE 7/26/16: I re flashed the ap root file with odin without doing a factory reset and it is still stuck in a boot loop, meaning I have to do a factory reset to get it out.
Mine is doing same thing. I used chain fires root. Everything went perfect. Then couple days later apps started saying they had stopped and phone started freezing. Every app I tired to open would say they had stopped. Then it constantly kept saying Google play services had stopped. I tried to reboot and stuck into bootloop everytime. Rooted again same thing happened again. U ever find a fix or anyone no how to fix this
HI folks.
I'm the owner of a Moto G3 that I tried (unsuccessfully) to root. I managed to reflash the correct firmware to the phone so that it at least worked. I'm currently running Android 5.1, but I'd like to install Android 6 which was installed. Unfortunately, everytime I try to do the update, it downloads and starts the install, reboots (or tries to, it goes to the bootloader screen on reboot every time) several times, and ultimately says update failed. I'm assuming the two issues (booting to Bootloader screen and refusing the update) are related - but I don't know how to fix either of them!! Id like to be able to return the phone back to completely stock with Android 6 running, and with the bootloader unlocked so I can have another bash at rooting at another time.
Help please!!!