Related
Yeah, I wasn't thinking at all. I ran my update check, got excited and just did it. It wasn't until after the fact that I really realized what I might have done.
Well, here's everything that happened/is happening.
I was trying to root my pad and get cwm. The pad was running stock 3.1 at the time this.
Well, after a bit of reading and looking around, I decided the easiest way would be to use the batch script located here: http://forum.xda-developers.com/showthread.php?t=1185104
After setting everything up, I ran the script. My tablet was rooted, I could gain superuser access, and busybox was installed as well...however, I could not get into recovery. At all.
In the zip for the rootkit there are two versions of recovery.img, one to use if the other doesn't work...
Well they both didn't work.
So I play around on my tablet for a while and read about 3.2, check my updates and see that I can get the 3.2 update. I do it, install it.
Stupid.
Now the pad is stuck on the Eee Pad screen with the Asus and nVidia Tegra logo.
I can get into APX mode as well as make the tablet attempt to boot into recovery (though it just hangs on "Booting recovery kernel image").
Can't even turn it all the way off, it just hangs.
I tried downloading the v5 (now v6) script from the above thread, and used all of the options included within, including the 3.2 root & recovery. To no avail.
Seems pretty grim.
My phone is a Samsung Epic which I've rooted, flashed roms, upgraded/downgraded Android... With the phone there's a program to completely unroot and flash back to stock. Is there something like that with tablets?
I might've dived into rooting my tablet before reading enough, I read a significant amount before I did anything to my phone, but I convinced myself the prior experience would make this easy. Obviously not the case.
So...any help would be hugely appreciated. Even if it's just telling me that there's not really anything I can do, because I'll be able to take it back for another (though that can be complicated and is preferably avoided).
since you can get to apx mode try nvflash with stockrom to 8.4.4.5 by following these instructions.
http://tabletroms.com/forums/showthread.php?1071-Factory-3.1-NVFlash-Recovery-Roms&p=9968
You'll then need to upgrade to 8.4.4.11 then to 8.6.5.6 before attempting to root using the v5 beta batch root script http://forum.xda-developers.com/showthread.php?t=1185104
That should get you out of trouble. good luck.
IMHO the problem is the recovery.
The ota updates rely on the stock recovery image for doing its dirty work; for what you wrote, it seems that you have installed cwm...
In the batch script hit "5" to reinstall stock boot+recovery us images.
If this won't work, try the woonie's hint.
Hope this helps.
woonie said:
since you can get to apx mode try nvflash with stockrom to 8.4.4.5 by following these instructions.
http://tabletroms.com/forums/showthread.php?1071-Factory-3.1-NVFlash-Recovery-Roms&p=9968
You'll then need to upgrade to 8.4.4.11 then to 8.6.5.6 before attempting to root using the v5 beta batch root script http://forum.xda-developers.com/showthread.php?t=1185104
That should get you out of trouble. good luck.
Click to expand...
Click to collapse
Woonie is correct, I did this to myself last week. After using NVFlash to get back to stock 8.4.4.5, do not let the pad restore settings from your gmail account. Wait for that until after you have it upgraded to 8.6.5.6 and rooted it again to sync up to your account.
http://forum.xda-developers.com/showthread.php?t=1192072&page=2
I follow jhanford's post and get this done.
Hey guys,
I sent my device to Asus a couple of days ago for repairs.
Asus did a great job on repairing my screen, but... um..
they have undone my root access and they've also relocked my bootloader, I think, although I can't get any OTAs.
Original question was:
What can I do to get my root again, because the scripts of sparky's tool don't seem to work anymore...
Sorry for this noobish question, but I swear that this has never happened to me before (and I have unlocked and rooted numerous devices)
What kind of sorcery is going on?!
Click to expand...
Click to collapse
Then I found the answer thanks to these amazing guys answering and trying to help.
It's a strange method, but it woudn't work otherwise:
I had to unlock the device (still on that very first stock JB rom).
Then, I flashed CWM through fastboot. Have a look here. However, do not forget: in this thread the OP referenced to an unofficial CWM. Go to the TF700 Android Development page and download the official CWM in stead.
After that I flashed a CWM-suitable SuperSU.zip (flashable) which made me have whereas it was impossible with any other method! (works through TWRP as well, for those that only have the unable to root problem )
Then, I flashed TWRP (but that's just a question of preferences, I guess) => This is no obligatory step of course!
There you go, for anyone who has/will have the same issues as me: follow these steps and let me know if it worked for you!
Have fun flashing Custom Roms/Kernels and/or recoveries again!
It might seem complicated, but it really isn't.
Good uck to those who follow(ed) my path
adelancker said:
Hey guys,
I sent my device to Asus a couple of days ago for repairs.
Asus did a great job on repairing my screen, but... um..
they have undone my root access and unlocked bootloader.
Click to expand...
Click to collapse
You mean relocked your bootloader?
...or actually unlocked it?
Thats OK said:
You mean relocked your bootloader?
...or actually unlocked it?
Click to expand...
Click to collapse
Sorry for that!
I meant that they relocked my bootloader, but still I can't get any OTAs
Thanks for the answer by the way.
I'd like to get it back to CR asap, since I really like that ROM, but noone has helped be yet
That is, until you arrived!
Ah
If we can get you successfully unlocked then the flashing can begin.
Have you tried unlocking via the Asus unlock .apk?
Seem as tho some tab owners have had problems with the Asus unlock tool.
I actually have the exact same problem.
Tablet back from screen repairs and now my root is gone, clean JB is installed and I can't seem to unlock (I wasn't unlocked before though).
I tried unlocking within the newest firmware with the ASUS Unlock app, failed with the "Unknown error occured, this could be a network problem".
Then I decided to atleast fix me root so I downgraded to .30 (ICS) and RootDebugFS fixed my root access.
Still my unlocking fails.
My serial is still the same btw.
DarkFire1985 said:
I actually have the exact same problem.
Tablet back from screen repairs and now my root is gone, clean JB is installed and I can't seem to unlock (I wasn't unlocked before though).
I tried unlocking within the newest firmware with the ASUS Unlock app, failed with the "Unknown error occured, this could be a network problem".
Then I decided to atleast fix me root so I downgraded to .30 (ICS) and RootDebugFS fixed my root access.
Still my unlocking fails.
My serial is still the same btw.
Click to expand...
Click to collapse
Thanks! I guess I'll downgrade to .30 as well, root it there and maybe attempt to unlock my bootloader.
I really wish to have CR again, so there's no option that this will not work (eventually)
Thats OK said:
Ah
If we can get you successfully unlocked then the flashing can begin.
Have you tried unlocking via the Asus unlock .apk?
Seem as tho some tab owners have had problems with the Asus unlock tool.
Click to expand...
Click to collapse
Shouldn't I first have root?
Or directly try to unlock the bootloader.
adelancker said:
Shouldn't I first have root?
Or directly try to unlock the bootloader.
Click to expand...
Click to collapse
My own experience included unlocking as a first step.
The reason was that I found it ultimately easier to install the CWM recovery thru ADB.
http://forum.xda-developers.com/showpost.php?p=32293050&postcount=1 <<<< The confusing guide is here.
After some study then trial we were successful!
Are you familiar with fastboot or opening a terminal (DOS like cmd window) on the PC?
ADB (Android Development Bridge) is a command prompt that will speak to the tablet thru a USB connection.
All of this is available with Androids platform tools.
I keep a tools folder on my PCs desktop so I don't have to search for it. (Platform tools can be downloaded)
I know all this is somewhat intimidating on first encounter...hopefully we can walk thru and get things up and loaded.
Thats OK said:
My own experience included unlocking as a first step.
The reason was that I found it ultimately easier to install the CWM recovery thru ADB.
http://forum.xda-developers.com/showpost.php?p=32293050&postcount=1 <<<< The confusing guide is here.
After some study then trial we were successful!
Are you familiar with fastboot or opening a terminal (DOS like cmd window) on the PC?
ADB (Android Development Bridge) is a command prompt that will speak to the tablet thru a USB connection.
All of this is available with Androids platform tools.
I keep a tools folder on my PCs desktop so I don't have to search for it. (Platform tools can be downloaded)
I know all this is somewhat intimidating on first encounter...hopefully we can walk thru and get things up and loaded.
Click to expand...
Click to collapse
Thanks for all the help!
It's not the first time I root (and/or) unlock a bootloader. It's just that now, those super easy root command methods don't work anymore. I have done completely manual rooting in the past, but I am not sure that will work either.
Besides, I got adb running before on my Infinity, but I'll make sure to downgrade to ICS first before doing anything else.
Here's what I am going to do:
1) downgrade to .30
2) try to root (with or without sparky's tool )
3) unlock bootloader (although I'm not sure if that'll work, judging from the comment of the Dutchman above)
I'll let you know in this thread if it worked or not.
My prediction: root will work, unlocking bootloader won't, since it's already been unlocked one and therefore my serial number is already in their database!
So i got my infinity like 2 weeks ago. The first thing i tried to do was to root it. I plugged in my device, installed drivers and checked unknown sources and usb debugging. I opened debugfs and tried to root my device but it suddenly closes. Whats likely to be the problem. And no i dont have asus sync installed.
P.S i returned my infinity on amazon as there was a hardware problem. Ill get the new one in a couple of days.
Thanks in advance.
Good luck with trying to get it unlocked (again)! If it doesn't work out in the end, you might want to drop Gary Key a line. Even if he is currently serving the USA himself, he might give you a pointer or a contact inside ASUS' support division. It's likely this is a "serial number in database" issue -- I'd like to believe that with some handiwork, this should be relatively simple issue to tackle, IF the engineers have access to that database at all. (With only Gary's answers to go on, I'd say ASUS HQ seems to keep its cards close to the chest.)
There's no way around the bootloader checking the staging partitions, right? Damn shame we can't just flash to it directly, ODIN style (which admittedly was not a perfect solution, but it is better than being locked out of your on device, essentially).
MartyHulskemper said:
Good luck with trying to get it unlocked (again)! If it doesn't work out in the end, you might want to drop Gary Key a line. Even if he is currently serving the USA himself, he might give you a pointer or a contact inside ASUS' support division. It's likely this is a "serial number in database" issue -- I'd like to believe that with some handiwork, this should be relatively simple issue to tackle, IF the engineers have access to that database at all. (With only Gary's answers to go on, I'd say ASUS HQ seems to keep its cards close to the chest.)
There's no way around the bootloader checking the staging partitions, right? Damn shame we can't just flash to it directly, ODIN style (which admittedly was not a perfect solution, but it is better than being locked out of your on device, essentially).
Click to expand...
Click to collapse
Thanks for the support!
It's a strange method, but it woudn't work otherwise:
I had to unlock the device (still on that very first stock JB rom).
Then, I flashed CWM through fastboot. Have a look here. However, do not forget: in this thread the OP referenced to an unofficial CWM. Go to the TF700 Android Development page and download the official CWM in stead.
After that I flashed a CWM-suitable SuperSU.zip (flashable) which made me have whereas it was impossible with any other method! (works through TWRP as well, for those that only have the unable to root problem )
Then, I flashed TWRP (but that's just a question of preferences, I guess) => This is no obligatory step of course!
There you go, for anyone who has/will have the same issues as me: follow these steps and let me know if it worked for you!
Have fun flashing Custom Roms/Kernels and/or recoveries again!
Thing with my situation is that I can't get your first step.
I tried to unlock the boot loader in the stock JB which the tablet was returned with.
I tried to unlock the boot loader in the stock .30 ICS rom
Every single time I get the "An unknown error has occured. This could be an network issue. Try again later" message ...
I haven't unlocked my tablet before RMA'ing so my serial shouldn't be "known" anyhow.
Though I do see a [90R-OK0QMB30000Y] TF700T MAIN_BD_._1G/T33/AS part at the replaced parts list on my Service Repair paper.
To me it looks like that a motherboard/mainboard, could that replacement be my issue?
DarkFire1985 said:
Thing with my situation is that I can't get your first step.
I tried to unlock the boot loader in the stock JB which the tablet was returned with.
I tried to unlock the boot loader in the stock .30 ICS rom
Every single time I get the "An unknown error has occured. This could be an network issue. Try again later" message ...
I haven't unlocked my tablet before RMA'ing so my serial shouldn't be "known" anyhow.
Though I do see a [90R-OK0QMB30000Y] TF700T MAIN_BD_._1G/T33/AS part at the replaced parts list on my Service Repair paper.
To me it looks like that a motherboard/mainboard, could that replacement be my issue?
Click to expand...
Click to collapse
Hmm... No idea what that could be.
I managed to unlock it, but that was after I reverted to ICS .30 (not obligatory, from what I understood ) I didn't use the Unlock Tool from the Asus website itself but an older (ex-official) Unlock Tool. (v7) I think it was.
I'll have a look and see if I can find it.
That might be the same as the one from the ASUS website but if you could provide me the file or md5 sum I can compare it.
adelancker said:
Thanks for the support!
It's a strange method, but it woudn't work otherwise:
I had to unlock the device (still on that very first stock JB rom).
Then, I flashed CWM through fastboot. Have a look here. However, do not forget: in this thread the OP referenced to an unofficial CWM. Go to the TF700 Android Development page and download the official CWM in stead.
After that I flashed a CWM-suitable SuperSU.zip (flashable) which made me have whereas it was impossible with any other method! (works through TWRP as well, for those that only have the unable to root problem )
Then, I flashed TWRP (but that's just a question of preferences, I guess) => This is no obligatory step of course!
There you go, for anyone who has/will have the same issues as me: follow these steps and let me know if it worked for you!
Have fun flashing Custom Roms/Kernels and/or recoveries again!
Click to expand...
Click to collapse
So glad to read that you have been successful.
...and do have fun flashing\updating\customizing!
DarkFire1985 said:
That might be the same as the one from the ASUS website but if you could provide me the file or md5 sum I can compare it.
Click to expand...
Click to collapse
The unlock tools provided by ASUS to unlock the TF201, TF300 and TF700 have been proven to be identical files (by checksum verification) --- no need to reinvent the wheel there.
The unlock step indeed is crucial -- and it depends on ASUS' database. If you can't get past that, there'll no flashing available in terms of recoveries (and therefore no custom ROMs either). Have you tried dropping Gary a line yet?
No not yet. Will do that.
Sent from my ASUS Transformer Pad TF700T using xda premium
DarkFire1985 said:
Thing with my situation is that I can't get your first step.
I tried to unlock the boot loader in the stock JB which the tablet was returned with.
I tried to unlock the boot loader in the stock .30 ICS rom
Every single time I get the "An unknown error has occured. This could be an network issue. Try again later" message ...
I haven't unlocked my tablet before RMA'ing so my serial shouldn't be "known" anyhow.
Though I do see a [90R-OK0QMB30000Y] TF700T MAIN_BD_._1G/T33/AS part at the replaced parts list on my Service Repair paper.
To me it looks like that a motherboard/mainboard, could that replacement be my issue?
Click to expand...
Click to collapse
Maybe you should have a look here. Seems like there were a couple of guys capable of unlocking it after all, and they were in the same situation as you.
I checked and the bootloader unlock tool was indeed an offial asus one. I downgraded before unlocking, but I saw you did too...
No idea what else I can do to help.
Hi there,
i was searching for quite some time now, but didnt find anything describing my problem.
I have a rooted tf700 with 10.4.4.20 (jelly bean). Because of the poor performance of the tablet i want to try different roms, to boost its performance. I have done this serveral times with my phone.
I'm just wondering if the unlocking process is any different with a rooted JB device, than to all the guides out there.
http://forum.xda-developers.com/showthread.php?t=1795156 (which works for JB devices too)
then i'll install twrp and from here on i can flash the roms as usual.
hope to clarify this quickly.
p4nDafk said:
Hi there,
i was searching for quite some time now, but didnt find anything describing my problem.
I have a rooted tf700 with 10.4.4.20 (jelly bean). Because of the poor performance of the tablet i want to try different roms, to boost its performance. I have done this serveral times with my phone.
I'm just wondering if the unlocking process is any different with a rooted JB device, than to all the guides out there.
http://forum.xda-developers.com/showthread.php?t=1795156 (which works for JB devices too)
then i'll install twrp and from here on i can flash the roms as usual.
hope to clarify this quickly.
Click to expand...
Click to collapse
In your case, it's pretty simple, just download the apk and unlock your device, then download goomanager from the market to use it to install twrp, then use twrp to flash what ever you want.
buhohitr said:
In your case, it's pretty simple, just download the apk and unlock your device, then download goomanager from the market to use it to install twrp, then use twrp to flash what ever you want.
Click to expand...
Click to collapse
Unfortunately it is not that simple. I'm in the same boat and have been trying for weeks to unlock as have others. The unlocking tool seems to not work for many right now. See these threads:
http://forum.xda-developers.com/showthread.php?t=2017727
http://forum.xda-developers.com/showthread.php?t=1795156 (Last few pages)
If you have success unlocking, PLEASE POST IT HERE so that others will have hope.
But, if you have success unlocking, then buhohitr is correct, should be simple.
I also can confirm that it seems not to work anymore as simply as previously. I think goomanager no longer is able to install twrp. I went to the twrp site and they stated that they have temporarily turned off that feature due to problems.
However you can still get it to work, you just have to unock with the Asus unlock tool, then manually use fastboot to flash over twrp.
Yes, but it's the unlocking that is also not working anymore. At least for a lot of people.
eesingd rocks
Sorry that it took me that long to respond.
In fact it all worked perfectly fine (on 4th december). I did exactly what buhohitr suggested. The unlockingprocess went through with no problems at all. As it was already rooted, i just got the goomanager from the market, installed the recovery and from there on it was business as usual.
I flashed the cleanmod inheritance(?) mod. And after using it for quite some time now. I LOVE IT.
I modified the dpi, now everything is smooth and small and i love (again) all the possibilities to modify the tablet. It supports the browser2ram feature, which gives the browser a huge performance boost.
Just to emphasize this one more time.
If you have any performance issues with the infinity (lags/unresponsiveness/etc) unlock it and try the custom roms, ofc after reading about the whole process.
For the past two days, I've been constantly struggling to find a way to update my phone to android 5.0. When trying to download the OTA update, it will download fine, but once it goes to install and reboot, it will stop halfway through and the same screen you see when you enter what i believe is called bootloader mode. On this screen i see clockworkmod and other words such as error which really confuses me because i do not believe I ever worked with that. Ill then be met by a message asking if i want to trust the untrusted zip to install. Upon clicking no, the phone will either reboot normally or go to another screen, where the android icon is now on his back with a red triangle above him and ill be asked if i would like to keep root access. Choosing either yes or no will result in the phone booting normally. If i click yes when asked if i want to download the untrusted zip, the result will be the same except the android will not get the red triangle. After being asked if i would like to keep root access, choosing either option will just reboot the phone.
Ive spent countless hours searching the web for solutions, and on the phone with google. I tried to flash a new image but I lack the skill and knowledge, to do this. My method of root was towerroot which i realize now was a mistake, because here i am with no knowledge on what ive actually done and no knowledge on how to fix it. I did not install a custom rom. So far, ive tried a factory reset, flashing a factory image (unsuccessful), using supersu to unroot my device, and deleting all root files in ex file explorer. I'm using windows if that helps.
The biggest kicker here now is that my phone tells me that i do not have root access any longer if i download a root checker, but when trying to install the update it asks me if i would like to keep root access. I also still have custom navigation keys stuck on my phone from the "softkeyz" app. As far as i know, there are no other traces of root on my device. I have almost no knowledge on how android os functions and am unfamiliar with terms I've been met with recently such as "custom image" "bootloader" "apk" "sdk" etc.
I completely understand that being this uninformed and rooting was a mistake, but what is done is done. If anybody has any idea at all on what i need to do to be able to update to lollipop please let me know. Any suggestions would be greatly appreciated as well. I may have left out key imformation but i've included all i can think of. If any other information is needed i can likely provide it.
1) you must be fully stock to accept OTA
2) various methods to update to and root lollipop are in my signature
3) this is the problem with one-click root methods. People don't get to learn what they need to know.
Please read my adb and fastboot thread. Again, you can get to it via my signature. Its in sticky roll-up
By the way, lack of paragraphs made your post a nightmare to read
Upgrading to 5.0
Though you don't know it, you most likely just dodged a bullet. 5.0 is not yet ready for prime time, or visa versa. Puzzle and Dragons can't launch under it (and probably won't for months.) My bank's app likewise won't launch under 5.0, and there are other impositions and quirks and annoyances. So maybe better that you couldn't do so.
I just put mine back to 4.4 and am very glad to have my old friend back. Installing 5.0 reminded me of installing Windows 8, and then wondering why the F*** I did so.
Good luck... enjoy 4.4 as long as possible. If you're not up for fixing the root issue you just described, you're also not ready for putting the phone back to 4.4 if, like me, you find 5.0 intolerable.
tthomas12 said:
For the past two days, I've been constantly struggling to find a way to update my phone to android 5.0. When trying to download the OTA update, it will download fine, but once it goes to install and reboot, it will stop halfway through and the same screen you see when you enter what i believe is called bootloader mode. On this screen i see clockworkmod and other words such as error which really confuses me because i do not believe I ever worked with that. Ill then be met by a message asking if i want to trust the untrusted zip to install. Upon clicking no, the phone will either reboot normally or go to another screen, where the android icon is now on his back with a red triangle above him and ill be asked if i would like to keep root access. Choosing either yes or no will result in the phone booting normally. If i click yes when asked if i want to download the untrusted zip, the result will be the same except the android will not get the red triangle. After being asked if i would like to keep root access, choosing either option will just reboot the phone. . Ive spent countless hours searching the web for solutions, and on the phone with google. I tried to flash a new image but I lack the skill and knowledge, to do this. My method of root was towerroot which i realize now was a mistake, because here i am with no knowledge on what ive actually done and no knowledge on how to fix it. I did not install a custom rom. So far, ive tried a factory reset, flashing a factory image (unsuccessful), using supersu to unroot my device, and deleting all root files in ex file explorer. I'm using windows if that helps. The biggest kicker here now is that my phone tells me that i do not have root access any longer if i download a root checker, but when trying to install the update it asks me if i would like to keep root access. I also still have custom navigation keys stuck on my phone from the "softkeyz" app. As far as i know, there are no other traces of root on my device. I have almost no knowledge on how android os functions and am unfamiliar with terms I've been met with recently such as "custom image" "bootloader" "apk" "sdk" etc.. I completely understand that being this uninformed and rooting was a mistake, but what is done is done. If anybody has any idea at all on what i need to do to be able to update to lollipop please let me know. Any suggestions would be greatly appreciated as well. I may have left out key imformation but i've included all i can think of. If any other information is needed i can likely provide it.
Click to expand...
Click to collapse
I have the EXACT same problem as you. I rooted my phone with towel root, then i flashed a custom recovery with an app called flashify. after that i flashed the proper supersu.zip file with the custom recovery. Next i rebooted my phone. I used an app called root checker to see if my root was working, and it was. Then i flashed my custom recovery back on. I tried updating my phone with the OTA Android 5, it was updating until around 25% once it hit that stage it just said error. Then i un rooted my phone and tried it again i got the same error. I did a factory reset and tried it again but i got the same result? i dont know why this is happening i need help!
---------- Post added at 07:27 PM ---------- Previous post was at 07:13 PM ----------
rootSU said:
1) you must be fully stock to accept OTA
2) various methods to update to and root lollipop are in my signature
3) this is the problem with one-click root methods. People don't get to learn what they need to know.
Please read my adb and fastboot thread. Again, you can get to it via my signature. Its in sticky roll-up
By the way, lack of paragraphs made your post a nightmare to read
Click to expand...
Click to collapse
Hello rootSU, you seem pretty experienced when it comes to stuff like flashing custom roms and rooting... My nexus 5 is on stock android 4.4.4, i have the stock recovery,i never flashed a rom....
When i try to use the OTA update and update to android 5.0 it always says error when its flashing. When the notification pops up i click it, then i click the button to start the download. once its downloaded and verified i click install. It takes me to my recovery and shows the android flashing logo thing and it says updating, when the progress bar reaches to 25% give or take a few percent an android logo pops up with a warning sign and it says error. I've tried multiple times and i got the same result. I even factory reseted my nexus and it still didn't work. Help ASAP please.
Regards,
cyberusman
Can't help with OTA. I refuse to use them. You can follow other advice from me in my thread in my signature
cyberusman said:
I have the EXACT same problem as you. I rooted my phone with towel root, then i flashed a custom recovery with an app called flashify. after that i flashed the proper supersu.zip file with the custom recovery. Next i rebooted my phone. I used an app called root checker to see if my root was working, and it was. Then i flashed my custom recovery back on. I tried updating my phone with the OTA Android 5, it was updating until around 25% once it hit that stage it just said error. Then i un rooted my phone and tried it again i got the same error. I did a factory reset and tried it again but i got the same result? i dont know why this is happening i need help!
---------- Post added at 07:27 PM ---------- Previous post was at 07:13 PM ----------
Hello rootSU, you seem pretty experienced when it comes to stuff like flashing custom roms and rooting... My nexus 5 is on stock android 4.4.4, i have the stock recovery,i never flashed a rom....
When i try to use the OTA update and update to android 5.0 it always says error when its flashing. When the notification pops up i click it, then i click the button to start the download. once its downloaded and verified i click install. It takes me to my recovery and shows the android flashing logo thing and it says updating, when the progress bar reaches to 25% give or take a few percent an android logo pops up with a warning sign and it says error. I've tried multiple times and i got the same result. I even factory reseted my nexus and it still didn't work. Help ASAP please.
Regards,
cyberusman
Click to expand...
Click to collapse
Did you ever remove any of the system apps? If you did, you will need to put them back or you will get an error with the OTA.
rootSU said:
1) you must be fully stock to accept OTA
2) various methods to update to and root lollipop are in my signature
3) this is the problem with one-click root methods. People don't get to learn what they need to know.
Please read my adb and fastboot thread. Again, you can get to it via my signature. Its in sticky roll-up
By the way, lack of paragraphs made your post a nightmare to read
Click to expand...
Click to collapse
xda6969 said:
Did you ever remove any of the system apps? If you did, you will need to put them back or you will get an error with the OTA.
Click to expand...
Click to collapse
Thanks for taking the time out of your busy life to help me, i already found a solution but thanks.
---------- Post added at 01:56 AM ---------- Previous post was at 01:49 AM ----------
tthomas12 said:
For the past two days, I've been constantly struggling to find a way to update my phone to android 5.0. When trying to download the OTA update, it will download fine, but once it goes to install and reboot, it will stop halfway through and the same screen you see when you enter what i believe is called bootloader mode. On this screen i see clockworkmod and other words such as error which really confuses me because i do not believe I ever worked with that. Ill then be met by a message asking if i want to trust the untrusted zip to install. Upon clicking no, the phone will either reboot normally or go to another screen, where the android icon is now on his back with a red triangle above him and ill be asked if i would like to keep root access. Choosing either yes or no will result in the phone booting normally. If i click yes when asked if i want to download the untrusted zip, the result will be the same except the android will not get the red triangle. After being asked if i would like to keep root access, choosing either option will just reboot the phone.
Ive spent countless hours searching the web for solutions, and on the phone with google. I tried to flash a new image but I lack the skill and knowledge, to do this. My method of root was towerroot which i realize now was a mistake, because here i am with no knowledge on what ive actually done and no knowledge on how to fix it. I did not install a custom rom. So far, ive tried a factory reset, flashing a factory image (unsuccessful), using supersu to unroot my device, and deleting all root files in ex file explorer. I'm using windows if that helps.
The biggest kicker here now is that my phone tells me that i do not have root access any longer if i download a root checker, but when trying to install the update it asks me if i would like to keep root access. I also still have custom navigation keys stuck on my phone from the "softkeyz" app. As far as i know, there are no other traces of root on my device. I have almost no knowledge on how android os functions and am unfamiliar with terms I've been met with recently such as "custom image" "bootloader" "apk" "sdk" etc.
I completely understand that being this uninformed and rooting was a mistake, but what is done is done. If anybody has any idea at all on what i need to do to be able to update to lollipop please let me know. Any suggestions would be greatly appreciated as well. I may have left out key imformation but i've included all i can think of. If any other information is needed i can likely provide it.
Click to expand...
Click to collapse
Okay, like i said in one of my previous posts i had the same problem as you. But i looked around and found out how to fix it. The new android OTA update checks if every single file and system app is there, if u make any changes you cant use the OTA lolipop update.To fix this you have to flash a factory image. Flashing the factory image maks your nexus have a stock android rom on it. The instructions are really easy...
https://developers.google.com/android/nexus/images
^^go on this website^^ and look for the android 4.4.4 or 5.0 factory image. There are instructions on how to flash it.
Hello Cyberusman. This isn't new in Android. Even in past versions of Android, if you removed or renamed apps or if you changed app permissions, the OTA would fail. Flashing the factory image is one way of fixing it but you could also put any removed apps back with correct permissions and that would work as well.
Guys, my son messed up and followed instructions off the Max "HighOnAndroid" at www.galaxynote5root.com
He flashed twrp 3.0.2-1
He followed step by step. After flashing twrp, he booted back into recovery and flashed
No-verify-opt-encrypt
And
Update-SuperSU-v2.46
When he booted it back up, its stuck on the sprint splash screen. It is specifically in the screen that says LTE Plus More spectrum better network.
After I got off from work, I came home to him crying.
Ok, I have started to download the factory ROM from Sammobile but I am wondering if maybe there isnt an easier fix. I am not to familiar with changing kernels. Ive never needed to worry about them. Could I maybe just need to flash a new kernel?
From looking on here, really all he needed to do was flash twrp then SuperSU... Does anyone know a way to fix this faster than waiting 6 hours for the Sammobile stock rom?
Please help
Edit....
Ok guys...
I got the file downloaded from sammobile. I installed it and got it installed and working. Then I tried to do the root myself. I followed the guide on this site. However I still couldn't get it working. It was still bootlooping. But not the same bootloop. This time around, it didn't get past the very 1st screen. I again flashed back the stock ROM and again everything works fine.
The files I tried to install are:
Twrp-3.0.2-1nobleltespr.tar.md5
Then I did the twrp install boot deal, booted into twrp and installed:
BeastMode-Stock-N920P-1.3-O16.tar.md5
BETA-Flashable_SuperSU-2.52
I now take it that the issue is my twrp says noble while I read not to use the noble kernel to use BeastMode. But I could be way off...
Man alive, I didn't know just how much I appreciated CF Auto Root until just now...
You probably already figured this out by now but follow the instructions and links in my thread. You should only reboot directly to twrp from download mode after flashing twrp btw in case you haven't figured it out by now.
The method you are using is from a very old thread. Follow the instructions in the thread below.
[How-to] Root your SM-N920P Device - all versions
tdunham said:
You probably already figured this out by now but follow the instructions and links in my thread. You should only reboot directly to twrp from download mode after flashing twrp btw in case you haven't figured it out by now.
The method you are using is from a very old thread. Follow the instructions in the thread below.
[How-to] Root your SM-N920P Device - all versions
Click to expand...
Click to collapse
Thank you for responding. I was able to get the factory ROM installed and working fine.
I have downloaded the MOAR for the device and plan on giving it a go.
I still haven't been able to root the phone. EVERYTHING I tried resulted in bootloop. So I just decided to stick to stock on his phone until I can actually get it figured out...
As far as the SuperSu being old, I got it directly from the website of the maker. https://download.chainfire.eu/696/supersu/
I REALLY want to get this phone rooted for him, as I am certain he is going to keep trying following random YouTube videos regardless of my instruction.
Like I said in my last post, I have never missed cf auto root so badly...
Sent from my SM-N900T using Tapatalk
auburn2eugene said:
Thank you for responding. I was able to get the factory ROM installed and working fine.
I have downloaded the MOAR for the device and plan on giving it a go.
I still haven't been able to root the phone. EVERYTHING I tried resulted in bootloop. So I just decided to stick to stock on his phone until I can actually get it figured out...
As far as the SuperSu being old, I got it directly from the website of the maker. https://download.chainfire.eu/696/supersu/
I REALLY want to get this phone rooted for him, as I am certain he is going to keep trying following random YouTube videos regardless of my instruction.
Like I said in my last post, I have never missed cf auto root so badly...
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Root on stock is relatively simple.
TWRP + SuperSU only.
But as you saw, it's still easy to get it wrong.
tdunham said:
Root on stock is relatively simple.
TWRP + SuperSU only.
But as you saw, it's still easy to get it wrong.
Click to expand...
Click to collapse
Ok, so since I have flashed TWRP and SuperSU, and all it ever does it bootloop, would I be able to install TWRP, then flash MOAR on top of it? Then I would have a rooted MOAR if I understand correctly. My issue is that ive always had root accomplished before installing a custom ROM.
If all I have to do is flash twrp then SuperSU, I dont understand what I could be doing wrong.
But I'm going to take a look at your link you provided and see if I can't get root 1st.
auburn2eugene said:
Ok, so since I have flashed TWRP and SuperSU, and all it ever does it bootloop, would I be able to install TWRP, then flash MOAR on top of it? Then I would have a rooted MOAR if I understand correctly. My issue is that ive always had root accomplished before installing a custom ROM.
If all I have to do is flash twrp then SuperSU, I dont understand what I could be doing wrong.
But I'm going to take a look at your link you provided and see if I can't get root 1st.
Click to expand...
Click to collapse
Old habits are hard to break. A properly deodexed rom that is pre-rooted only requires twrp and a proper wipe before installing.
For rooting stock, it really is fairly simple. The instructions I provided are probably a little overly detailed but I had to cover as much as possible for those that have never done it before so it 'looks' complex but once you've done it a few times you will see that its really not that hard to do.
tdunham said:
Old habits are hard to break. A properly deodexed rom that is pre-rooted only requires twrp and a proper wipe before installing.
For rooting stock, it really is fairly simple. The instructions I provided are probably a little overly detailed but I had to cover as much as possible for those that have never done it before so it 'looks' complex but once you've done it a few times you will see that its really not that hard to do.
Click to expand...
Click to collapse
Thank you for pointing me to your thread. I was able to get root on my sons phone. Hard to believe the SuperSU was the problem... But it was... I was using the one from chainfires site, but yours worked when his created bootloops.
Thanks again!
Is there a root method for pk1