so i have no mods on my prime besides root and atp tweak and it keeps failing....tried 3 times......i restored the scheduler and all but it still is failing....what gives. anyone else dealing with this??
also im getting this image...
http://www.box.com/s/d91b69252908ff677506
I'm also getting this. Tried a factory reset, d/l update and still fails.
verdikt said:
so i have no mods on my prime besides root and atp tweak and it keeps failing....tried 3 times......i restored the scheduler and all but it still is failing....what gives. anyone else dealing with this??
also im getting this image...
http://www.box.com/s/d91b69252908ff677506
Click to expand...
Click to collapse
Is your bootloader unlocked? If it is, you'd have to relock the bootloader and flash the stock recovery image.
babymatteo said:
Is your bootloader unlocked? If it is, you'd have to relock the bootloader and flash the stock recovery image.
Click to expand...
Click to collapse
no its not. i havent done much with it not even cwm.this is so gay.i hope they get it fixxed
verdikt said:
no its not. i havent done much with it not even cwm.this is so gay.i hope they get it fixxed
Click to expand...
Click to collapse
try downloading Voodoo OTA Root Keeper then redo the process of updating. This might help, as it did with many rooted users.
My bootloader is not unlocked, and I have rootkeeper. I still get the dead android, even after a full system wipe.
Did you guys install the new google play market 3.1.5? If so try uninstalling the mareket update and then install the Prime update.
Updated perfectly fine for me from .15 -> .21
Used OTA Rootkeeper to keep my root
Only thing i've done is root, everything else is stock
C10 Serial if that helps
i thought the update isn't till tomorrow? ;o
http://forum.xda-developers.com/showpost.php?p=23409128&postcount=1
i checked anyways and i don't have any updates
-- Canada
edit:
never mind there is an update now...
IT seems like the Update isn't available for German devices, maybe others are also affected
Sent from my HTC Desire using XDA
To: babymatteo
Per your previous post. How do I re-lock booloader? I have a rooted prime, unlocked bootloader, and running a custom ROM. I have HDMI out problem which have recently materialized, can you post a link for a how to in this thread? Also, do you know if you relock bootloader, remove root, and install the orginal OTA update, can ASUS tell I had an unlocked bootloader with root if I RMA due to a faulty HDMI out?
Thoughts?
Thanks in advance.
Wave.
verdikt said:
so i have no mods on my prime besides root and atp tweak and it keeps failing....tried 3 times......i restored the scheduler and all but it still is failing....what gives. anyone else dealing with this??
also im getting this image...
http://www.box.com/s/d91b69252908ff677506
Click to expand...
Click to collapse
Probably OC and ATP tweak causing the trouble, because some system files (checked during install updated) are not standard any more
If you are rooted and you changed anything like deleting bloatware or changed your systemUI the update will fail... has to be stock
I have the same exact issue down to the dead android logo during 30% update process.
Again, NOT unlocked but ROOTED.
I have not modded any of the system file EXCEPT for the AGPS patch in the dev forum. I do not have the original files before the patch...someone help please.
Thanks,
babymatteo said:
Is your bootloader unlocked? If it is, you'd have to relock the bootloader and flash the stock recovery image.
Click to expand...
Click to collapse
You can't relock the bootloader and flashing a stock recovery would brick your tablet.
experiencing the same issue here I own a C2 model with locked bootloader, ota rootkeeper, ez overclock and some debloating, so I got no idea what to do lol
Same here.
Stock, rooted, bootloader locked.
I backed up *some* of the crap arrived with the device, tried to titanium them back, no dice.
Are we forever doomed to walk the planet with .15 when everyone will flash there <something-yummy-starting-with-Z-here>.350?
Meh.
is it possible to flash a stock .15 ruu from asus which would allow us to update? although that way I'm afraid we would lose root and would need to backup our data beforehand..
I had this problem on the .14 to .15 update also. Just reinstall the .15 update manually using this method you can get the .15 update from asus site just make sure you get the right version
Then try the OTA again after redoing the .15 and it finally should worked
I did what this person did on his post.
http://forum.xda-developers.com/showpost.php?p=23039742&postcount=1
Solved
gdavis480 said:
I had this problem on the .14 to .15 update also. Just reinstall the .15 update manually using this method you can get the .15 update from asus site just make sure you get the right version
Then try the OTA again after redoing the .15 and it finally should worked
Click to expand...
Click to collapse
Dude, you're awesome as sniffing cocaine off a stripper's behind.
Per your advice, I followed asus manual update guide (would have post link, but xda says I'm too noob to do so) after which I OTA'ed like a champ.
Thx mate.
Related
Hi guys,
first of all i'm sorry for my bad English,
second, i'm looking for solutions for 2 weeks in every part of forum without success!
i explain all the steps i've done before the trouble with my TF201 European version (32gb)
rooted with UnlockRoot v.2.3 success
installed all my apps.
trying to update to official update 9.4.2.21 (always fail)
i decided to unlock device with official asus app - success
again fail to update.
i decide to install CWM success
i load update 9.4.2.21.zip in my MicroSd (like a tutorial i read)
once i reboot in recovery, obviously, i can't acces to my MicroSd to load the .zip file
Panic---Solved learning adb command
i pushed .zip file into sdcard and update.
success with all update io've done but everytime loop recovery
http://forum.xda-developers.com/showthread.php?t=1514088
i solved with this guide...
try to Root the Tf201 with all of tools, like vipermodPrimeTimev4.5 (fail), UnlockRootv2.3 (fail), Sparkyroot (fail), TransformerPrimeIcsNew (fail)
the message is alway the same
i tried to reupdate OS but nothing, always it's impossibile to found busybox and su
tried to rerun Asus Unlock Device App
fail for possible internet connection (impossible)
is there any flash downloadMode like Odin for my GalaxyS, for every problems i had Odin was always the answer, the last but my MR.WOLF!
now i got my TF201 Unlocked (no more warranty) but Unrooted.
i love to use custom roms like i did with my galaxyS but now it's impossible to install CWM cause i'm not rooted.
any suggestion?
second step is to bring device to Assistance and pay what i need to have it clear (unlocked but clear) but i know that you got the solution.
thankyou all
Bad luck my friend
jacopone80 said:
...........................
thankyou all
Click to expand...
Click to collapse
Yeah man, that's bolex!! & you are out of luck.
I missed the OTA rootkeeper as well before I updated . No way yet to root 21, as far as yesterday midnight from what I remenber.
I did bring the unit back to the shop and exchanged it into the last showmodel ( still on HC)
Now it is updated and rooted.
Hopefully -vipervoy_ will find a new solution.
Edit: follow this thread: http://forum.xda-developers.com/showthread.php?t=1571828
re
ehi thankyou for quick answer...but...
you're telling me that there no way to root yet 9.4.2.21 update and in your signature I see rooted 9.4.2.21 @viperboy
i can't understand
jacopone80 said:
ehi thankyou for quick answer...but...
you're telling me that there no way to root yet 9.4.2.21 update and in your signature I see rooted 9.4.2.21 @viperboy
i can't understand
Click to expand...
Click to collapse
1. With Prime on .15 update (or earlier), get root
2. Install OTA rootkeeper
3. Upgrade to .21
4. Use OTA rootkeeper to get root back
This is the only way to have root on a stock .21 build.
If you upgrade to .21 before rooting and installing OTA rootkeeper, your cannot root (currently).
jacopone80 said:
you're telling me that there no way to root yet 9.4.2.21 update and in your signature I see rooted 9.4.2.21 @viperboy
i can't understand
Click to expand...
Click to collapse
It's really simple, you must root before updating to .21, save your root with something like Voodoo RootKeeper, and then restore your root after updating. There is currently no way to do an original root on .21.
re
perfectly understood right now
the problem is that i'm already on .21 and i think i can't donwgrade right?
so i've to wait for next root system
thanks all
Dave_S said:
It's really simple, you must root before updating to .21, save your root with something like Voodoo RootKeeper, and then restore your root after updating. There is currently no way to do an original root on .21.
Click to expand...
Click to collapse
And sometimes even this way is not working.
I'm using the .17 firmware,Is it possible to root?
rogeriok said:
I'm using the .17 firmware,Is it possible to root?
Click to expand...
Click to collapse
Yes
http://forum.xda-developers.com/showthread.php?t=1427125
I have a Transformer Prime with an Unknown Serial Number. My tablet can NOT be pushed OTA Updates by ASUS. Do NOT suggest going to ASUS's website and downloading their update file, you can NOT keep Root using those files. OTA RootKeeper ONLY Works on OTA Updates PUSHED by ASUS to your tablet.
Do NOT suggest going to ASUS's website and downloading their update file. Do NOT suggest any blob file that has been linked to on these forums, UNLESS it is from someone who has actually COPIED the OTA Update from ASUS AS IT WAS BEING PUSHED to their tablet. These blob files are NOT OTA Updates.
Okay, so if you have an unknown serial on your Transformer or Transformer Prime you can't get OTA Updates. I am one of these people and it sucks because I actually like 9.4.2.21. I want root.
Now my question is, is it possible for someone with a TF101/TF201 to use some ADB or some other software to intercept the package that ASUS is pushing to the tablet and make it available to others?
I would try to figure out how to do it myself, but as I mentioned earlier. I don't have a tablet with a serial number, it shows unknown. So no OTA Updates for me.
slayvus said:
Okay, so if you have an unknown serial on your Transformer or Transformer Prime you can't get OTA Updates. I am one of these people and it sucks because I actually like 9.4.2.21.
Now my question is, is it possible for someone with a TF101/TF201 to use some ADB or some other software to intercept the package that ASUS is pushing to the tablet and make it available to others?
I would try to figure out how to do it myself, but as I mentioned earlier. I don't have a tablet with a serial number, it shows unknown. So no OTA Updates for me.
Click to expand...
Click to collapse
You can manually update it using wolf849 method, which is really used to downgrade but im more then certain it would work to manually upgrade.
Ill go step by step.
1. If you want root, and are on 9.4.2.15 now, root it now! then backup root with OTA ROOTKEEPER
2.Download latest .21 FW here http://support.asus.com/Download.aspx?SLanguage=en&p=20&s=16&m=Eee+Pad+Transformer+Prime+TF201&os=32 you likely want US build, not WW (check in settings under about this tablet)
3. Download my modded ViperMOD tool from here http://forum.xda-developers.com/showpost.php?p=25508554&postcount=52 this allows for one click downgrade.
4. Extract the .21 fw you download and find the file named "blob" and put blob on the root of you primes INTERNAL MEMORY
5. Make sure all prime drivers are installed (should install by themselves , mine did) then open my modded viperMOD (thanks viperboy) and connect transformer prime. Select option 1 in modded viperMOD tool to downgrade tablet (in your case upgrade, it just manually apply's the blob file (firmware) )
6. Should reboot to .21 then restore root with OTA Rootkeeper if wanted
Hope it works
You can't manually update or you'll lose root. Unless you have tested this yourself I'll stick with where I am. I was on 9.4.2.15, manually upgraded to .21 as I have Unknown Serial problems, LOST ROOT. Currently downgraded to 9.4.2.14.
Aka, downgrade to 9.4.2.XX. Root. Protect Root, Use the tool to upgrade to .21. Restore Root. If you can show me video evidence of this, I will do it. Otherwise, it would be a waste of my time as I would have to downgrade AGAIN and stay where I am.
slayvus said:
You can't manually update or you'll lose root. Unless you have tested this yourself I'll stick with where I am. I was on 9.4.2.15, manually upgraded to .21 as I have Unknown Serial problems, LOST ROOT. Currently downgraded to 9.4.2.14.
Aka, downgrade to 9.4.2.XX. Root. Protect Root, Use the tool to upgrade to .21. Restore Root. If you can show me video evidence of this, I will do it. Otherwise, it would be a waste of my time as I would have to downgrade AGAIN and stay where I am.
Click to expand...
Click to collapse
I was on .21 downgraded to .15, then rooted, then installed OTA rootkeeper to backup root, updated to .21 OTA then restored root with OTA rootkeeper, and im now on .21 rooted with out a unlocked prime. This has also been stated by many others.
The Blob files are NOT the OTAs as far as I can tell from what I have read.
I can NOT receive OTA Updates from ASUS while connected to the internet on my Tablet. I have an UNKNWON SERIAL NUMBER on my TF201.
An Unknown Serial Number prohibits me from being pushed OTAs by ASUS.
slayvus, im with you, im gonna get my prime replaced or rma'd on thursday if i cant find exactly what your looking for!.
slayvus said:
The Blob files are NOT the OTAs as far as I can tell from what I have read.
I can NOT receive OTA Updates from ASUS while connected to the internet on my Tablet. I have an UNKNWON SERIAL NUMBER on my TF201.
An Unknown Serial Number prohibits me from being pushed OTAs by ASUS.
Click to expand...
Click to collapse
doing the manual update is like doing the OTA updates
you keep all your information on your prime hence you can just use the root keeper to restore root
of course we're just trying to help you but if you refuse to listen to us and want us to spend time to prove to you that something works when you can always try your self, then never mind just stay on your firmware that you're on @[email protected];
This is getting tiresome of repeating this. So I let you hear it from someone who MADE Primetime, -viperboy-.
http://forum.xda-developers.com/showpost.php?p=25495366&postcount=1634
-viperboy- said:
Assdikes said:
How come I can't root or how come vipermod is not getting the job done anymore? Also I don't really know how to make real use of the OTA root keeper, because everytime I updated I made a SU backup, and then I think this is where I mess up, Then I would install the update manually from my sd card and everything is out of whack the root is messed up in a half root state sometimes, and my apps are gone, and blah blah blah...... someone help!?!?!?!?!?!?!?!?
Click to expand...
Click to collapse
Dear God, can you read?! DIRECTLY from the OP:
THIS WILL NOT ROOT .21 AT THIS TIME!!
Click to expand...
Click to collapse
There is no root method for .21, only a downgrade procedure. The reason why OTA Root Keeper didn't work is because...
maatsby said:
...it's called "OTA rootkeeper", not "manual update rootkeeper".
Click to expand...
Click to collapse
...when you update it from the sdcard, it's the full install, not the OTA that only makes certain changes. You are wiping out the OS and your su-backup.
Click to expand...
Click to collapse
Again, lets go over this ONE more time since people can not seem to read and think EVERYONE on the internet is wrong.
THE BLOB FILES ARE NOT OTA UPDATES! THEY ARE MANUAL UPDATES AND YOU CAN NOT KEEP ROOT IF YOU USE THEM!
If someone can show a know developer saying different, THAN I will believe you. Until than, I will go with the assumption that, again, BLOB files are manual updates. I do NOT want to waste time to have to do everything over again on my Prime and risk bricking it AGAIN. I already risked it once by downgrading.
bimbobo said:
It worked finally, but I wasted my time.
I installed WW15, rooted it, save the root with OTA RK, reinstalled 21WW but OTA RK did not restore the saved root. Either I cannot OTA RK correctly, or you cannot root 21 at all. I do not get that somebody reported they could restore 21 root, maybe they are unlocked.
I need to decide to stay with 15 or rest in peace with 21 not rooted.
Click to expand...
Click to collapse
bimbobo said:
I installed using the guide in the dev forum, sd card and blob.
Then I do not know.
I just clicked on "backup root", I have no idea where it's installed.
But you can eventually explain how to use it correctly.
Click to expand...
Click to collapse
b.huss2 said:
No, I'm asking how you went from 15 to 21. Did you let it update over the air or did you manually update via an SDcard update? Just wondering because Root Keeper only works for OTA updates from what I understand. For example, I was on version 15, rooted with this tool, installed Root Keeper, backed up root, and when the update came it installed automatically, and I just had to go back into Root Keeper and restore root.
EDIT: just noticed this
I think this is your problem. It's an OTA Root Keeper. You did not update OTA
Click to expand...
Click to collapse
Now PLEASE, stop suggesting that I install .21 using a BLOB file off my SDCard. It's making me feel bad having to prove you wrong. All I want to know is if it is possible to intercept ASUS' OTA Updates so that people like ME can make use of them.
Could be a way
slayvus,
This guy managed to intercept this us one, now it would be nice if they could do it for my ww version.
http://forum.xda-developers.com/showthread.php?t=1437274
im downloading this old firmware to comare it to the manual blob to see if its just a case of putting the blob in the cache folder :S
we would just need someone with a non .21 prime to download the ota for us
It looks promising, but it doesn't seem like anyone has contributed to that method in over a month.
without trying to get your hopes up im returning mine tomorrow if i dont find a solution tonight i did find this http://forum.xda-developers.com/showthread.php?p=22928122
a direct link to asus ota update for 8.6.5.21 -> 9.2.1.11 US
im going to check out whats in this zip, and see if i can find an ota link for ww, if i find one for .21 its worth you trying, you can allways downgrade again.
i went from .21 to .11 to .21 to 8.8.3.33 now im back at .15, lol
You can download FOTAKILL.apk and install it in /system/data and it will no longer OTA.
Did it for the Xoom on 4.0.3 Team EOS 1.0. Works perfect. Will work on the Lemon TF201 as well.
slayvus said:
Okay, so if you have an unknown serial on your Transformer or Transformer Prime you can't get OTA Updates. I am one of these people and it sucks because I actually like 9.4.2.21.
Now my question is, is it possible for someone with a TF101/TF201 to use some ADB or some other software to intercept the package that ASUS is pushing to the tablet and make it available to others?
I would try to figure out how to do it myself, but as I mentioned earlier. I don't have a tablet with a serial number, it shows unknown. So no OTA Updates for me.
Click to expand...
Click to collapse
You can go to Asus.com and download the .21 updated zip file. If you unzip it you will find the blob file there. You will have to manually update but you will lose root. OTA root keeper wont work for this method.
If you want to intercept, accept the OTA download but dont install it. Go to your cache folder (I forget the sub folder maybe someone can chime in) and there you will find the dlpkxxxxx file. I assume if you copy that file into another Prime in the same directory that the tab will assume you have just downloaded an update and will install it as if it were OTA. Then you may be able to use OTA rootkeeper to restore root afterwards. I haven't tried this myself so just a theory.
Sent from my Transformer Prime TF201 using Tapatalk 2
slayvus
im going to get mine rma'd or replaced this afternoon,
when i get a working one back ill get a copy of the OTA from my cache folder, i feel this may be a way for unknown serial number units to get .21 with root!
i may be getting mine fixed but i will still strive to get a fix for this situation.
Believe me ive upgraded and downgraded to and from .21 about 10 times sofar so its still worth trying.
Again, the updates from ASUS on their website, which are the blob files people are passing around for things like downgrades and such ARE NOT THE SAME THING AS AN OTA UPDATE.
An OTA Update is smaller than the blob files by a LOT. The OTAs are like less than 100 MB for the incremental updates. The updates on ASUS's website are over 300MB.
calm down, im sorry if i didnt say it right, im only human, i am going to get the ota update that downloads to the cache folder which as you say is smaller than the asus blob, i fully understand this, i spent all last night looking for the asus OTA 9.4.2.21 update, the best i could find is one to update to 9.4.2.11.
I repeat, I do not mean the one from asus.com, i am refering to the ones the units automaticly notifys you that they are availble and you then download direct to device, allowing you to use ota root keeper.
i upgraded to .21 using wolfs method last night and confirm that root is not kept if you do it that way.
when i get a working unit i will help intercept where the update downloads to and get a copy from my device, even if it means downgrading multiple times till we get it right!
I have no problem with what you said XN, the problem is with people like aznmode.
Who said
aznmode said:
You can go to Asus.com and download the .21 updated zip file.
Click to expand...
Click to collapse
slayvus said:
I have no problem with what you said XN, the problem is with people like aznmode.
Who said
Click to expand...
Click to collapse
Did you see my 2nd paragraph? Did that not answer your question? I try to help and you have a problem with it. Get that stick out of your ass dude.
Sent from my PG86100 using Tapatalk 2
Did you even read my OP before I updated it? I have no problem with reading.
I can NOT receive OTA Updates. My Prime has an Unknown Serial Number. ASUS refuses to push OTA Updates to Primes that have the Unknown Serial Number.
I understand you cant receive OTA and thats a known problem ever since the first ICS build came around and Asus is well aware of it and I've been in this ATP forums since this tablet was release so I am well aware of that issue as well. My 1st prime was in Dec of last year. Anyway I was generalizing when I said "you" and I didnt mean YOU cause obviously you cant get the OTA. My main point was how it can be done. I have intercepted an OTA before and I have some saved and I've done it with my Acer a100 as well. We're all here to help each other out so you should be thankful instead of being an ass about it. People will less likely to help you in the future. Not gonna waste anymore time..but good luck and hope you get your problem sorted out.
Sent from my Transformer Prime TF201 using Tapatalk 2
Hi,
I just downgraded from .21 to .15, rooted and installed OTA Rootkeeper.
Now I want to upgrade to .21 again, but my TFP doesnt find any updates...
When I check manually via the "About"-Menu in Settings, it says there's no update available for my device.
Has anyone else had similar problems?
Do you know any solution?
Can i upgrade manually to .21 and restore root successfuly?
I have heard of this before. You might want to read Wolf downgrade thread as solutions was posted in there. You might need to install a different reigon version of the firmware. Its a matter of installing a firmware THST will look for the update. That's what I read in there.
No way to manually upgrade and restore root. At least at the moment. The only other way is to just unlock your prime, install TWRP or CWM, then flash a custom rom that's already rooted that's based off of .21. Please post back up anything you find out or a solution. AS I'm testing the new .28 beta build and will likely need a similar solution in order to root. What you posted is what I was afraid of going the downgrading route. That once downgraded, it won't even see a new update in order to update to latest firmware and voodoo can't work its magic on it. Keep us posted.
demandarin said:
I have heard of this before. You might want to read Wolf downgrade thread as solutions was posted in there. You might need to install a different reigon version of the firmware. Its a matter of installing a firmware THST will look for the update. That's what I read in there.
No way to manually upgrade and restore root. At least at the moment. The only other way is to just unlock your prime, install TWRP or CWM, then flash a custom rom that's already rooted that's based off of .21. Please post back up anything you find out or a solution. AS I'm testing the new .28 beta build and will likely need a similar solution in order to root. What you posted is what I was afraid of going the downgrading route. That once downgraded, it won't even see a new update in order to update to latest firmware and voodoo can't work its magic on it. Keep us posted.
Click to expand...
Click to collapse
Thanks for your response.
I read the whole Thread with Wolf's Tutorials.
I found some posts of guys having the exact same issue, but I did not find a single reply with any solution
No more ideas on this problem?
That's what I did installed .15 rooted and installed virtuous prime basically a stock .21 rom that's rooted and very stable ..... currently i'm running Andro Wook custom v1.0 works very well and speedier than stock but if you're looking for completely stock virtuous prime or Andro wook also has stock rooted roms as well
I did the same thing yesterday but it worked for me.
Make sure you're downgrading with the correct country SKU matching your original one. (WW, US, DE, etc...)
The procedure I used ONLY works on a locked bootloader. If you have unlocked with the Asus tool you cannot get OTA updates.
Asus has pulled all the old firmware!
So, I did not have a US V9.4.2.15 blob but found one (http://d-h.st/hGK) from this post - http://forum.xda-developers.com/showpost.php?p=25503960&postcount=47
Also notice what hajalie24 is replying in that post: "Probably because you used WW on a US prime.."
Downgraded from .21 to .15 using wolf849's method 2 - http://forum.xda-developers.com/showthread.php?t=1622628
DO NOT USE THIS METHOD ON AN UNLOCKED DEVICE.
Rooted using viperMOD_PrimeTime_v4.6 - http://forum.xda-developers.com/showthread.php?t=1427125
Installed OTA RootKeeper and backed su - https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper
Checked for update in About tablet / System Firmware Update. It saw .21 and upgraded successfully.
Used RootKeeper and restored root successfully.
I understand you might have done the same steps, but I wanted to post the exact procedure I used because it worked.
yanni5 said:
I did the same thing yesterday but it worked for me.
Make sure you're downgrading with the correct country SKU matching your original one. (WW, US, DE, etc...)
The procedure I used ONLY works on a locked bootloader. If you have unlocked with the Asus tool you cannot get OTA updates.
Asus has pulled all the old firmware!
So, I did not have a US V9.4.2.15 blob but found one (http://d-h.st/hGK) from this post - http://forum.xda-developers.com/showpost.php?p=25503960&postcount=47
Also notice what hajalie24 is replying in that post: "Probably because you used WW on a US prime.."
Downgraded from .21 to .15 using wolf849's method 2 - http://forum.xda-developers.com/showthread.php?t=1622628
DO NOT USE THIS METHOD ON AN UNLOCKED DEVICE.
Rooted using viperMOD_PrimeTime_v4.6 - http://forum.xda-developers.com/showthread.php?t=1427125
Installed OTA RootKeeper and backed su - https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper
Checked for update in About tablet / System Firmware Update. It saw .21 and upgraded successfully.
Used RootKeeper and restored root successfully.
I understand you might have done the same steps, but I wanted to post the exact procedure I used because it worked.
Click to expand...
Click to collapse
Thanks for your detailled post.
I have done it exactly this way.
There are many people facing the problems with missing OTAs and not being able to unlock their devices.
MartiniMoe said:
Thanks for your detailled post.
I have done it exactly this way.
There are many people facing the problems with missing OTAs and not being able to unlock their devices.
Click to expand...
Click to collapse
I've done it the same way as you and others 1 month ago and could update to .21 without problem.
But I know 1 person who downgraded and rooted his locked TF201 few days ago (following the exactly same steps with correct blob) and can't update.
He tried everything after downgrade: waiting 1 or 2 days / wiping data / uninstalling updates of google apps. He does not get OTA update.
if someone has a solution....
EDIT: probably reason for the user i mentionned: he had unlocked his tablet weeks ago. Then he sent it to support because it was bricked. The tablet came back with .21 and relock. It seems that now he can't update after downgrade nor unlock his device. Maybe because of the serial number registered by Asus.
pnoire said:
EDIT: probably reason for the user i mentionned: he had unlocked his tablet weeks ago. Then he sent it to support because it was bricked. The tablet came back with .21 and relock. It seems that now he can't update after downgrade nor unlock his device. Maybe because of the serial number registered by Asus.
Click to expand...
Click to collapse
Yes, I would not be surprised if Asus service re-flashes the tablet back to life and "forgets" to reset that serial number in their database so it can get updates again
I downgraded to .15 from .21 using wolfs method and then rooted my device but now I can't seem to update OTA, I just get the 'no updates available' message. I don't think an processes are frozen or anything. Any ideas?
Thanks.
Moothead2 said:
I downgraded to .15 from .21 using wolfs method and then rooted my device but now I can't seem to update OTA, I just get the 'no updates available' message. I don't think an processes are frozen or anything. Any ideas?
Thanks.
Click to expand...
Click to collapse
download direct from asus and follow their instructions to install. That's what I had to do when I forgot to replace my modified build prop and asus locked me out from ota.
Do you keep root that way? Only reason I downgraded was to get root back.
Moothead2 said:
Do you keep root that way? Only reason I downgraded was to get root back.
Click to expand...
Click to collapse
You do not, however there arel very easy root methods now that work no matter what. I used sparkys after the update.
Can you do that without unlocking the device? If so, can you link please .
Moothead2 said:
Can you do that without unlocking the device? If so, can you link please .
Click to expand...
Click to collapse
Just use this tool and it'll root your tablet, even on the most recent release (.28). You don't need to be unlocked or anything. I ran it on the .28.5 beta build a while ago and it worked flawlessly.
Thanks a lot .
Edit - I've been a bit of an idiot. When I downgraded using Wolf's method I dowgraded to .15 WW edition on my US tab. I can't seem to update either OTA or manually with both WW and US edition of the .28 update. Anyone know if I can use Wolf's method to flash the .28 us update?
I have gone WW -> US -> WW with this method all on .21 and I was still able to get .28 update, so it shouldn't be a problem.
whycali said:
download direct from asus and follow their instructions to install. That's what I had to do when I forgot to replace my modified build prop and asus locked me out from ota.
Click to expand...
Click to collapse
so you can confirm modding the build.prop will stop OTA updates?
When you then pull the update manually, I assume it then replace the build.prop back to stock.
has anyone tried putting back the build.prop file and seeing if the OTA is then triggered.
I lost my OTA update ability and I never knew build.prop file edits was the reason until now... news to me
AFAIK (correct me if i'm wrong): If you have modded build.prop, you should see ota update, but when you try updating, it will fail. But if you rever changes in build.prop, it should be fine. Same goes if you modify/remove any of stock apps.
When yoh do full update (downloaded from asus website) it should be fine.
Sent from my PadFone using Tapatalk 2
qery said:
AFAIK (correct me if i'm wrong): If you have modded build.prop, you should see ota update, but when you try updating, it will fail. But if you rever changes in build.prop, it should be fine. Same goes if you modify/remove any of stock apps.
When yoh do full update (downloaded from asus website) it should be fine.
Sent from my PadFone using Tapatalk 2
Click to expand...
Click to collapse
After I failed the first ota because I forgot to unmod the build.prop the ota never worked again. It had to be done manually.
As per the title, I read something somewhere to the effect that from here on out, OTA updates will fail on most phones if they have been rooted, and this seems to be true for the Z Ultra GPE. So, what changed when I rooted my phone, and how do I undo it so that I can do the OTA update? I have looked through the forum, but nobody seems to answer it. I am rooted with Supersu using the Towelroot method. I am hoping to not have to unlock the bootloader or anything, just want to do this the official way. (I did backup my TA partition though).
jeraldjunkmail said:
As per the title, I read something somewhere to the effect that from here on out, OTA updates will fail on most phones if they have been rooted, and this seems to be true for the Z Ultra GPE. So, what changed when I rooted my phone, and how do I undo it so that I can do the OTA update? I have looked through the forum, but nobody seems to answer it. I am rooted with Supersu using the Towelroot method. I am hoping to not have to unlock the bootloader or anything, just want to do this the official way. (I did backup my TA partition though).
Click to expand...
Click to collapse
If your GPe is rooted only, the OTA should install just fine. If you made any system changes, you'll need to revert those though. I ran the OTA while I was rooted and didn't have any problems.
Visa Declined said:
If your GPe is rooted only, the OTA should install just fine. If you made any system changes, you'll need to revert those though. I ran the OTA while I was rooted and didn't have any problems.
Click to expand...
Click to collapse
Not so. See:
http://bgr.com/2014/11/14/android-5-0-lollipop-updates-and-root/
As mine is rooted, no dice, the OTA fails. So, how to unroot it so that the update takes?
jeraldjunkmail said:
Not so. See:
http://bgr.com/2014/11/14/android-5-0-lollipop-updates-and-root/
As mine is rooted, no dice, the OTA fails. So, how to unroot it so that the update takes?
Click to expand...
Click to collapse
well at the moment that doesn't effect the GPe, and may never. There will have to be a system image flashed to put the block device in a known state before the new way could ever be used, and if there is a system.img we can always flash that to get the OTA to work... no big deal I don't think.
jeraldjunkmail said:
Not so. See:
http://bgr.com/2014/11/14/android-5-0-lollipop-updates-and-root/
As mine is rooted, no dice, the OTA fails. So, how to unroot it so that the update takes?
Click to expand...
Click to collapse
First of all, BGR is a garbage site, and I wouldn't believe anything they say, ever. Second, that article is talking about avoiding root AFTER Lollipop is installed.
Having root will not cause the OTA to fail. If your OTA is failing, it's because you made a system change on your device.
*edit
If you were using Xposed, then that is more than likely why your OTA is failing.
What is Xposed? How would I check to see if it has affected my device? Only thing I did was Towelroot and running SuperSU. I may have done something to allow writing to the external SD card, but forget how I did that. I was intentionally trying to keep this phone basically stock so that it would easily update to Lolipop. I did a Titanium backup to the externalSD card and reset it to factory and the OTA update still fails though. I assume this was due to the fact that I rooted it. The bootloader is still unmodified, secureboot is still green - yes, lock state is locked. Only other thing I can think of is I installed an app that allowed me to set permissions by app (turn off location settings by app, etc) Sorry I can't give any more details than that...
jeraldjunkmail said:
I may have done something to allow writing to the external SD card, but forget how I did that.
Click to expand...
Click to collapse
jeraldjunkmail said:
Only other thing I can think of is I installed an app that allowed me to set permissions by app (turn off location settings by app, etc) Sorry I can't give any more details than that...
Click to expand...
Click to collapse
If you can't figure out what system change you made to your phone, just factory reset it, and run the OTA again. There was multiple people(me included) that took the OTA successfully, our phones were rooted and SuperSU was installed.
Visa Declined said:
If you can't figure out what system change you made to your phone, just factory reset it, and run the OTA again. There was multiple people(me included) that took the OTA successfully, our phones were rooted and SuperSU was installed.
Click to expand...
Click to collapse
As mentioned before, I factory reset this and wiped the cache from the stock recovery mode. Update won't take, stops shortly after it fails with "system update error". Since my last reset (been done a few times) it won't prompt me to get the OTA update, after my last reset last night. Any help is appreciated. Thanks!
{Damn thing won't work... (*&^&%^$$#}
jeraldjunkmail said:
As mentioned before, I factory reset this and wiped the cache from the stock recovery mode. Update won't take, stops shortly after it fails with "system update error". Since my last reset (been done a few times) it won't prompt me to get the OTA update, after my last reset last night. Any help is appreciated. Thanks!
{Damn thing won't work... (*&^&%^$$#}
Click to expand...
Click to collapse
The only fail-safe way I can see is to:
root
back up TA
unlock BL
hotboot custom kernel with recovery
flash 4.4.2
OTA to 4.4.3
OTA to 4.4.4
root and restore TA if you want a working camera
OTA to 5.0
blueether said:
The only fail-safe way I can see is to:
root
back up TA
unlock BL
hotboot custom kernel with recovery
flash 4.4.2
OTA to 4.4.3
OTA to 4.4.4
root and restore TA if you want a working camera
OTA to 5.0
Click to expand...
Click to collapse
As often happens, I sometimes see a solution I don't care to implement and begin to procrastinate. So, haven't looked at this problem for a while. I may have found the solution to my problems, but want to know if anyone has experience with it before proceeding. I re-installed superSU and went through the options. Buried in the options list is a box that offers "Full unroot, Cleanup for permanent unroot". What happens when I do this? does it just remove superSU or does it restore the phone back to factory status, before it was rooted? Thanks!
PS: @ blueether the solution is fine and I am sure it would work (I was going to go ahead with it until I saw that option in superSU), but have been hesitant to unlock the bootloader, etc, due to my unfamiliarity with hacking Sony products, and only want to do it as a last, final, no other option solution. Thanks for your help!
jeraldjunkmail said:
As often happens, I sometimes see a solution I don't care to implement and begin to procrastinate. So, haven't looked at this problem for a while. I may have found the solution to my problems, but want to know if anyone has experience with it before proceeding. I re-installed superSU and went through the options. Buried in the options list is a box that offers "Full unroot, Cleanup for permanent unroot". What happens when I do this? does it just remove superSU or does it restore the phone back to factory status, before it was rooted? Thanks!
PS: @ blueether the solution is fine and I am sure it would work (I was going to go ahead with it until I saw that option in superSU), but have been hesitant to unlock the bootloader, etc, due to my unfamiliarity with hacking Sony products, and only want to do it as a last, final, no other option solution. Thanks for your help!
Click to expand...
Click to collapse
That's fine and I take no offence at you not wanting to unlock the BL.
I haven't tried the full unroot option in supersu so I'm not sure what the outcome is. One of the other GPe users care to comment?
Well, turns out that the solution to unrooting the phone is to install superSU and than look inthe settings. It will offer you an option to completely uninstall root. It did what it says, and than you can check it with a check root app from the market. It reports that the phone is not rooted. Now the question is, will it pick up the OTA update... No luck with that after a clean factory reset, so not sure what to do next.
2 questions: If I unrooted my phone, and it says it is unrooted, is this true, in the fullest extent? Does towelroot do anything more than adding some permissions ans the superuser file?
If the phone won't pick up the OTA update, why? What went wrong?
Thanks!
jeraldjunkmail said:
Well, turns out that the solution to unrooting the phone is to install superSU and than look inthe settings. It will offer you an option to completely uninstall root. It did what it says, and than you can check it with a check root app from the market. It reports that the phone is not rooted. Now the question is, will it pick up the OTA update... No luck with that after a clean factory reset, so not sure what to do next.
2 questions: If I unrooted my phone, and it says it is unrooted, is this true, in the fullest extent? Does towelroot do anything more than adding some permissions ans the superuser file?
If the phone won't pick up the OTA update, why? What went wrong?
Thanks!
Click to expand...
Click to collapse
It sounds like the OTA is not being pushed at the moment/anymore. You could copy it to there the recovery can see it and manually install it
blueether said:
It sounds like the OTA is not being pushed at the moment/anymore. You could copy it to there the recovery can see it and manually install it
Click to expand...
Click to collapse
Can you point me inthe right direction for instructions on this process? Thanks!
Visa Declined said:
First of all, BGR is a garbage site, and I wouldn't believe anything they say, ever. Second, that article is talking about avoiding root AFTER Lollipop is installed.
Having root will not cause the OTA to fail. If your OTA is failing, it's because you made a system change on your device.
*edit
If you were using Xposed, then that is more than likely why your OTA is failing.
Click to expand...
Click to collapse
Your post is two years ago but i think you can help me,there is a new update for my phone and i am rooted i also have xposed installed so this mean i cannot update my sytem? Do i need to uninstall xposed? Im on stock rom and with TWRP recovery it would be a big help if you reply thanks.