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
Related
This has been brought up in:
http://forum.xda-developers.com/showthread.php?t=1486926
I figured it would be time to start a new thread on it to discuss work-arounds.
Is it possible to revert to .11? I assume we would need to re-root.
EDIT* Since I didn't mention it, I am unable to OTA on 11.1. I live in Colorado which people from the other thread have stated they are able to update from.
redpoint13 said:
This has been brought up in:
http://forum.xda-developers.com/showthread.php?t=1486926
I figured it would be time to start a new thread on it to discuss work-arounds.
Is it possible to revert to .11? I assume we would need to re-root.
EDIT* Since I didn't mention it, I am unable to OTA on 11.1. I live in Colorado which people from the other thread have stated they are able to update from.
Click to expand...
Click to collapse
No, you can't go back until we have working recoveries and proper backups can be made. Only choice is to wait for manual version of .13, install it (should be up in 1-3 days), and likely after that the Kernel numbers will be in the right line for OTA's again
*EDIT: I too am on 11.1, just have to wait either for ASUS to update the firmware downloads on their website or for one of our fellow xda'ers to capture the update and upload it for us
Don't you love those Asus emails telling you to flash things without any indication of consequences? That's why I didn't flash the one I was pmed.
yep this kinda blows. went 11.1 because I considered rooting, but didnt.
Just didnt see any benefit for me at this point since there were no ROMS, boot ubnlock etc.
Oh well, hopefully it will be up on Asus soon.
Also hopefully when we do manually update to .13 any future OTA's will be available to us?
Seems to be a firmware update today just got it
Commodore 64
buxtahuda said:
No, you can't go back until we have working recoveries and proper backups can be made. Only choice is to wait for manual version of .13, install it (should be up in 1-3 days), and likely after that the Kernel numbers will be in the right line for OTA's again
*EDIT: I too am on 11.1, just have to wait either for ASUS to update the firmware downloads on their website or for one of our fellow xda'ers to capture the update and upload it for us
Click to expand...
Click to collapse
So it sounds like we are guaranteed to lose root then?
GreginNH said:
yep this kinda blows. went 11.1 because I considered rooting, but didnt.
Just didnt see any benefit for me at this point since there were no ROMS, boot ubnlock etc.
Oh well, hopefully it will be up on Asus soon.
Also hopefully when we do manually update to .13 any future OTA's will be available to us?
Click to expand...
Click to collapse
The biggest thing for rooting to me was being able to install/use an ad-block program.
redpoint13 said:
So it sounds like we are guaranteed to lose root then?
Click to expand...
Click to collapse
Yeah but should be no issue for those who made sure to use voodoo OTA rootkeeeper. The update breaks root but I easily restored it. VOODOO OTA ROOTKEEPER IS A MUST HAVE NOW!
Been working great for me last few updates. Saves me Hassell of having to worry about manually rooting sgain
Does it not work downloading and flashing 9.4.2.11 from asus' site and aquiring the .13 OTA that way?
redpoint13 said:
So it sounds like we are guaranteed to lose root then?
Click to expand...
Click to collapse
Absolutely!
I don't know how OTA's work, but it seems that the 11.1 just isn't in their timeline and so the servers aren't pushing to those devices. If ASUS could rectify this and somehow make it available, your OTA Rootkeeper will work.
Most likely, will have to manually update to .13 and then re-root for (third for me) second time. Don't worry, Viper and everyone will update quickly I'm sure.
---------- Post added at 11:17 AM ---------- Previous post was at 11:15 AM ----------
demandarin said:
Yeah but should be no issue for those who made sure to use voodoo OTA rootkeeeper. The update breaks root but I easily restored it. VOODOO OTA ROOTKEEPER IS A MUST HAVE NOW!
Been working great for me last few updates. Saves me Hassell of having to worry about manually rooting sgain
Click to expand...
Click to collapse
No, 'darin. It's OTA Rootkeeper. Not just Rootkeeper.
Manual updates wipe out your /system/ and so your subackup folder and any others relating to Rootkeeper's backup get removed.
*EDIT: Also, sorry, didn't meant to sound like a d'bag lol just trying to make sure some poor soul doesn't do a manual update thinking rootkeeper will work for them
buxtahuda said:
Absolutely!
I don't know how OTA's work, but it seems that the 11.1 just isn't in their timeline and so the servers aren't pushing to those devices. If ASUS could rectify this and somehow make it available, your OTA Rootkeeper will work.
Most likely, will have to manually update to .13 and then re-root for (third for me) second time. Don't worry, Viper and everyone will update quickly I'm sure.
---------- Post added at 11:17 AM ---------- Previous post was at 11:15 AM ----------
No, 'darin. It's OTA Rootkeeper. Not just Rootkeeper.
Manual updates wipe out your /system/ and so your subackup folder and any others relating to Rootkeeper's backup get removed.
Click to expand...
Click to collapse
Good point..lmfao wasn't really thinkn of that. Exit stage right. Lol
demandarin said:
Yeah but should be no issue for those who made sure to use voodoo OTA rootkeeeper. The update breaks root but I easily restored it. VOODOO OTA ROOTKEEPER IS A MUST HAVE NOW!
Been working great for me last few updates. Saves me Hassell of having to worry about manually rooting sgain
Click to expand...
Click to collapse
AFAIK when you manually install "OTA" root keeper does not work, and seems like others are confirming this.
I just hope someone is able to quickly find another root exploit as fast as they did for .11.
Hopefully they'll rectify this in the next couple of days, don't want to be without root again .
On a different note, did anyone notice the screen would take longer to come on from standby after the 11.1 update? Mine takes about a second longer than I THINK it did before updating, but I'm not sure.
I noticed that as well. 1st few times I hit it twice due to the delay which would end up turning it on and then back to standby/sleep
Moothead2 said:
Hopefully they'll rectify this in the next couple of days, don't want to be without root again .
On a different note, did anyone notice the screen would take longer to come on from standby after the 11.1 update? Mine takes about a second longer than I THINK it did before updating, but I'm not sure.
Click to expand...
Click to collapse
Yes, also noticed it. We'll see if the .13 goes back to the quicker.
Duh!
Just tried something on my 11.1 that I manually updated. If you already have root, use a build.prop editor to change:
ro.build.display.id to IML74K.US_epad-9.4.2.11-20120117
ro.build.version.incremental to US_epad-9.4.2.11-20120117
Save, then reboot. Once it boots up, don't unlock the device. Turn the screen off until it connects to the network, then unlock. It may hot-reboot a couple of times, but just keep trying.
Once you've got it up, go check for a firmware update. You should be able to get it.
isantop said:
Just tried something on my 11.1 that I manually updated. If you already have root, use a build.prop editor to change:
ro.build.display.id to IML74K.US_epad-9.4.2.11-20120117
ro.build.version.incremental to US_epad-9.4.2.11-20120117
Save, then reboot. Once it boots up, don't unlock the device. Turn the screen off until it connects to the network, then unlock. It may hot-reboot a couple of times, but just keep trying.
Once you've got it up, go check for a firmware update. You should be able to get it.
Click to expand...
Click to collapse
What are the risks of this? I want to do this myself but I'm worried.
isantop said:
Just tried something on my 11.1 that I manually updated. If you already have root, use a build.prop editor to change:
ro.build.display.id to IML74K.US_epad-9.4.2.11-20120117
ro.build.version.incremental to US_epad-9.4.2.11-20120117
Save, then reboot. Once it boots up, don't unlock the device. Turn the screen off until it connects to the network, then unlock. It may hot-reboot a couple of times, but just keep trying.
Once you've got it up, go check for a firmware update. You should be able to get it.
Click to expand...
Click to collapse
Trying now.
*RETARDED found both
isantop said:
Just tried something on my 11.1 that I manually updated. If you already have root, use a build.prop editor to change:
ro.build.display.id to IML74K.US_epad-9.4.2.11-20120117
ro.build.version.incremental to US_epad-9.4.2.11-20120117
Save, then reboot. Once it boots up, don't unlock the device. Turn the screen off until it connects to the network, then unlock. It may hot-reboot a couple of times, but just keep trying.
Once you've got it up, go check for a firmware update. You should be able to get it.
Click to expand...
Click to collapse
Even if this seems to work, I would be very worried about messing up the system. The OTAs are basically a patch file, and they only contain the changed bits of system files, not the whole files. (It's using bsdiff, if anyone cares.)
What this means is, if it's patching the wrong file because you lied about your version, it will very likely mess up your system - maybe even make it unbootable until you fix it with a full update.
Now, it's possible this update doesn't touch any files which changed between .11 and. 11.1, so it would be safe. But I wouldn't assume that.
buxtahuda said:
Trying now.
Click to expand...
Click to collapse
Any news? I.e. does it work or not?
Is it possible to downgrade to .15 (i'm on .21)
By downloading the asus update .15 and extract is and rename it to .22 (above .21) so android recognize it as an update and proceed without bricking my TF201.
Or isn't it a very smart thing to do?
Or will it just not work?
If it was that simple that would be sweet but I doubt it
Sent from my Transformer Prime TF201 using Tapatalk
SickQuilver said:
Is it possible to downgrade to .15 (i'm on .21)
By downloading the asus update .15 and extract is and rename it to .22 (above .21) so android recognize it as an update and proceed without bricking my TF201.
Or isn't it a very smart thing to do?
Or will it just not work?
Click to expand...
Click to collapse
If it did work, from your logic, you'd have trouble putting 21 back on....and if the next one was 22, it might also give problems.
Sounds interesting, but I'm not trying it until it's proven to be safe.
I'm not talking about changing the internal code just the zip from the update otherwise android won't see it as a (up)grade.
But i'm not sure if it will work and if it is safe it's just a quick suggestion.
no i dont think this will work, the updater script will more than likely check .apk versions etc
This will not work, and you may have to factory reset after trying it to get rid of the files that it will attempt to place to stage the device for an update, thus causing an update message to constantly pop up until you do. (Unless, of course, you know what files to get rid of. ) Either way, this isn't going to work.
I have a TF201 with the "Unknown Serial"
Recently I found that I could root it with the SparkyRoot app
My question is, does the Voodoo OTA Root Keeper app still keep root if I do a manual update (since OTA updates don't work for me)?
I tried the manual update from .15 to .21 with "Wolf's ultimate flash and downgrade guide" and I couldn't keep root. It kept over writing the root..
ShyTownFantasy said:
I tried the manual update from .15 to .21 with "Wolf's ultimate flash and downgrade guide" and I couldn't keep root. It kept over writing the root..
Click to expand...
Click to collapse
Right. I learned a couple of posts above yours that you lose root doing manual update. "Root keeper " tool does not recover root because of the exploit gets patch unlike doing an OTA
Sent from my Transformer Prime TF201 using xda premium
http://forum.xda-developers.com/showthread.php?t=1648296
if your US, or im looking at when i get mine back from rma, ill try to post the ww version.
try it, you can allways downgrade
xn1337 said:
http://forum.xda-developers.com/showthread.php?t=1648296
if your US, or im looking at when i get mine back from rma, ill try to post the ww version.
try it, you can allways downgrade
Click to expand...
Click to collapse
Yes, US version.
So I just put that file in /cache/ and reboot or something? And it will automatically try to update? Or I go to check for updates?
How well does that method work? Since I am on .15, that should be safe, right?
See this post：
http://forum.xda-developers.com/showthread.php?t=1648296
It can make sn problem pad upgrade 21 ok and root keep with voodo rootkeeper.
So I copied that file to /cache/ and I saw some notification that there was an update. Then I wanted to make sure OTA Root Keeper was setup first and also I wanted to double check my version. I realized I was on .14, so I did a manual update to .15 and got root again.
Now I can't get the dlpkgfile to be recognized. I've tried removing it and copying again. I've done numerous power down, power on, cycles, as well as a "hard reboot" by holding vol up before holding the power to turn it on.
I'm not really sure what to do. Is there some way to make it recognize that there is a dlpkgfile in /cache?
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.