I'm currently on .21 unrooted, so I used the .15 update and renamed it .22, when I inserted it the tab it recognised it as an update. Do you think it would downgrade if I follow through?
Blackwidowman said:
I'm currently on .21 unrooted, so I used the .15 update and renamed it .22, when I inserted it the tab it recognised it as an update. Do you think it would downgrade if I follow through?
Click to expand...
Click to collapse
My guess is that it will either:
A) Fail to update if you try, saying it is a lower version than what you have installed.
or
B) Brick your Prime.
And I haven't heard about anyone else doing this, so I don't believe it'll work I'm afraid.
I suggested it last Saturday had no positive response.
I did not try it because of the possibility of above option B
Try it! Tell us if it works. You would be a hero to all of us who are stuck with unrooted .21.
If undying adulation of nameless, faceless, anonymous masses is not worth the risk of brick, I do not know what is!
Just hoping for some recommendations of more experience persons
Blackwidowman said:
I'm currently on .21 unrooted, so I used the .15 update and renamed it .22, when I inserted it the tab it recognised it as an update. Do you think it would downgrade if I follow through?
Click to expand...
Click to collapse
U tried via external sd? can u give more details?
Cheers
All I did so far is extract the .15 update from Asus to my sd using my pc then went to the sd and renamed the .15 to .22. I inserted the sd into the tap and the update notification comes up. I stopped there.
Blackwidowman said:
I'm currently on .21 unrooted, so I used the .15 update and renamed it .22, when I inserted it the tab it recognised it as an update. Do you think it would downgrade if I follow through?
Click to expand...
Click to collapse
Hey look at my thread.
http://forum.xda-developers.com/showthread.php?t=1584180
No good you unlocked your device thus voiding your warranty. I want to downgrade to be able to root.
Edit: And keep my warranty
Blackwidowman said:
All I did so far is extract the .15 update from Asus to my sd using my pc then went to the sd and renamed the .15 to .22. I inserted the sd into the tap and the update notification comes up. I stopped there.
Click to expand...
Click to collapse
So you get the actual Asus Upgrade message when you place it in your SD?
Blackwidowman said:
All I did so far is extract the .15 update from Asus to my sd using my pc then went to the sd and renamed the .15 to .22. I inserted the sd into the tap and the update notification comes up. I stopped there.
Click to expand...
Click to collapse
I did the same way and did go further and the Prime reboot to the upgrade process.
After 3-4 mins it says fail to upgrade and got stuck at the Android Robot Icon red error declaimer.
Wait for 3-5 mins the Prime automatically boot back to .21.
When it completely boots, you can see, the error message in the notification bar with saying that "Fail to upgrade, restore previous configuration"
After 1-2 reboot, it is functioning as normal, but fail to downgrade.
IF anyone who has different experience or successful to downgrade, please share.
Johnny0906 said:
So you get the actual Asus Upgrade message when you place it in your SD?
Click to expand...
Click to collapse
Tried the same thing last night, TFP showed an android on his back with a red exclamation, that method is a no go for me, BUT a few others I've read had better luck
Maybe this way maybe not?
Idk if this is right but from what I see when I boot up my prime it doesn't tell me that its unlocked either I found a hole where you can unlock your prime and hide it or something. I unlocked my prime via vipersmod, and voided the warranty but I could careless. Well anyway I downgraded to .15 rooted it went to root keeper so I could update. I didn't realize that my downgrade would still pop up as an update and I updated it to .15 again not thinking O crap that's whats on their already, I bricked my prime kept booting up to clockwork mod recovery. I unbricked it through adb (pain in the a$$) but once fixed rebooted the prime saw that it doesn't say the device is unlocked and I'm still rooted. Soo what happened?
I am not responsible if you mess your device up trying this process I was lucky it bricked the way it did and not hard bricked it
Related
Ok, I know there are a lot of posts already on updating to 2.3.6 and root, but there appears to be a lot of different situations and limited information that is causing me some confusion.
So, what I want to do is get some clear details about probably the second most common situation: A Motorola Atrix 4G running the stock ROM with root access and an unlocked bootloader.
With regards to updating, aside from the obvious actions (i.e. TiBu, maybe a Nandroid), is there anything else that needs to be done to perform the update?
Additionally, I would like to keep root/unlocked even with the update, but I am willing to re-do root after the update. I can't find clear information on what methods work to keep root or to restore root after updating.
That is pretty much all that I am trying to do. I can not afford to brick my phone, so I want to make sure that I understand everything before I update.
P.S. Curse Motorola and it's stupid locked bootloaders!
I'm in the same shoes and looking to do the same thing...I want to keep root, not brick my phone...Apply the 141 update. I don't mind a little work (re-root, re-modify some files)
I'm running an unlocked bootloader, AT&T Atrix with 4.5.91 which is rooted with some custom changes (tethering, 2g/3g toggle, unlock APNs, agps)
Seems it could be possible to rebuild Blur_Version_91.4.5.141.MB860ATT.en.US available from Motorola and exclude the bootloader portions to keep the phone from bricking?
psychephylax said:
I'm in the same shoes and looking to do the same thing...I want to keep root, not brick my phone...Apply the 141 update. I don't mind a little work (re-root, re-modify some files)
I'm running an unlocked bootloader, AT&T Atrix with 4.5.91 which is rooted with some custom changes (tethering, 2g/3g toggle, unlock APNs, agps)
Click to expand...
Click to collapse
Yeah, I used the script that applied the tethering/hotspot tweak. That's about it. I haven't had to use any agps or anything, it's got amazing gps as it is.
Glad I'm not the only one though
If you have a stock rom unlocked bootloader with root don't do the ota update.I just soft bricked my phone.
Sadly, I did just that. I just wasn't paying attention.
Update: resorted to a factory reset. Now I have 2.3.6 running. Just going to take some time to restore my apps and settings.
Looks like I'm in the same boat. What's the best way to recover from a soft-brick in this situation?
thatguy193 said:
If you have a stock rom unlocked bootloader with root don't do the ota update.I just soft bricked my phone.
Click to expand...
Click to collapse
Yeah, this is exactly why I have asked. I read at least one post somewhere where someone tried both the SD Card and the OTA update and the SD didn't work, but the 2nd OTA try did. I don't know if they said they had unlocked or not.
Johnston212 said:
Yeah, this is exactly why I have asked. I read at least one post somewhere where someone tried both the SD Card and the OTA update and the SD didn't work, but the 2nd OTA try did. I don't know if they said they had unlocked or not.
Click to expand...
Click to collapse
Well I found this threadhttp://forum.xda-developers.com/showthread.php?t=1498856 was trying the auto updater as suggested but my phone wont stay on long enough for it to work.It does the auto shutdown and tries re-installing the OTA update which gives me the android triangle guy.
I recently made an update of my Atrix 4G's System from 2.3.4 to 2.3.6.
My 2.3.4 version was unlocked and rooted. It is on ATT.
Initially I received a notification in my phone about the new System update available. I tried three times OTA, but each time the process failed. When it was booting up always gave me the Android Icon with an Exclamation mark inside of a triangle. But nothing else happens. My phone continued working but with the 2.3.4 version.
Then I went to this page:
Because I haven't less than 8 post in this site I can't post any URL.
But, go for the "Motorola software update" in the Motorola's web page or Google it and get it.
And installed the "Motorola Software update" application. I had to restart my PC in order to make the software to recognize and connect to my Atrix 4G. When the Atrix was connected, by USB port, I had to select the "Windows media Sync" in the USB connection options list to make the connection to work.
Then, all that I had to do was wait until the process got completed.
I hadn't see nothing different with the new update.
I conserved my "unlocked" condition but I lost my "Rooted" condition. But that is not a big issue, there are several thread in the web that help you to get rooted again.
Hope this can help, It works for me.
cjfermin said:
I conserved my "unlocked" condition but I lost my "Rooted" condition. But that is not a big issue, there are several thread in the web that help you to get rooted again.
Hope this can help, It works for me.
Click to expand...
Click to collapse
You have an unlocked bootloader? Or sim-unlocked phone?
I'm in the same situation of @cjfermin and the 2.3.6 was flashed without any problem.
Of course I've lost ROOT, but I've followed simple instructions on the web (using Fasboot) and I've re-rooted the Atrix in 3 minutes.
PS: my Atrix was/is sim-unlocked and with unlocked bootloader.
emandt said:
I'm in the same situation of @cjfermin and the 2.3.6 was flashed without any problem.
Of course I've lost ROOT, but I've followed simple instructions on the web (using Fasboot) and I've re-rooted the Atrix in 3 minutes.
PS: my Atrix was/is sim-unlocked and with unlocked bootloader.
Click to expand...
Click to collapse
Thanks, that is exactly what I was needing to find out. I've heard yes and no's on different re-rooting methods. Could you link the one that you used? I was thinking about using Gingerbreak or OneClickRoot
I was trying to apply the OTA 4.5.141, on my rooted AT&T Motorola Atrix stock rom 2.3.4 and after the first reboot, following the instructions from the update, I am getting the message “failed to boot 2 starting rds mode” and just sit there. After removing the battery and booting up again, the phone seems to booting up normally and then when the phone finishes loading most of the widgets, I get a message saying “turning off” and the same cycle keeps repeating.
This is my primary phone and I am really desperate right now and I do not know what to do.
Please I need some help,
Johnston212 said:
Could you link the one that you used?
Click to expand...
Click to collapse
Here: http://www.android-advice.com/2012/root-the-motorola-atrix-4g-running-4-5-141/
Hope that helps you!
Alverik said:
I was trying to apply the OTA 4.5.141, on my rooted AT&T Motorola Atrix stock rom 2.3.4 and after the first reboot, following the instructions from the update, I am getting the message “failed to boot 2 starting rds mode” and just sit there. After removing the battery and booting up again, the phone seems to booting up normally and then when the phone finishes loading most of the widgets, I get a message saying “turning off” and the same cycle keeps repeating.
This is my primary phone and I am really desperate right now and I do not know what to do.
Please I need some help,
Click to expand...
Click to collapse
Ok, is your bootloader unlocked as well? I googled the "failed to boot 2 starting RSD mode" that you mentioned and there are a number of posts on it from over the years. It seems that you may need to flash a SBF file, but I don't know enough about your situation to competently tell you more than that.
Johnston212 said:
Ok, is your bootloader unlocked as well? I googled the "failed to boot 2 starting RSD mode" that you mentioned and there are a number of posts on it from over the years. It seems that you may need to flash a SBF file, but I don't know enough about your situation to competently tell you more than that.
Click to expand...
Click to collapse
I am on stock rom 2.3.4 and have only rooted my phone nothing else. It seems that because it was a rooted phone the update could not finish the process.
Now I don’t know what to do.
Should I try to flash to 2.3.4 using RDS lite and then update using OTA 4.5.141 or flash using 4.5.141 (I don’t know where to find it)?
Help please, this is my only phone.
Alverik said:
I am on stock rom 2.3.4 and have only rooted my phone nothing else. It seems that because it was a rooted phone the update could not finish the process.
Now I don’t know what to do.
Should I try to flash to 2.3.4 using RDS lite and then update using OTA 4.5.141 or flash using 4.5.141 (I don’t know where to find it)?
Help please, this is my only phone.
Click to expand...
Click to collapse
If the only thing you've ever done to the phone is root then flashing the official 2.3.4 (not fruitcake) with RSDlite and then applying the 141 OTA update should be ok. Things to note:
1) Make sure the phone is fully charged
2) Apply the 141 OTA update from sd card. Go to motorola's website . I've had mixed results when applying previous updates when downloading over wifi.
3) Be VERY sure you've done nothing else to your phone other than root, i.e. unlock, mess with the bootloader and/or recovery (unlock, ROMs).
gnahc79 said:
If the only thing you've ever done to the phone is root then flashing the official 2.3.4 (not fruitcake) with RSDlite and then applying the 141 OTA update should be ok. Things to note:
1) Make sure the phone is fully charged
2) Apply the 141 OTA update from sd card. Go to motorola's website . I've had mixed results when applying previous updates when downloading over wifi.
3) Be VERY sure you've done nothing else to your phone other than root, i.e. unlock, mess with the bootloader and/or recovery (unlock, ROMs).
Click to expand...
Click to collapse
The only thing that I have done other than rooting my phone it’s unlocking the sim card.
I don't have a SIM unlocked phone, so I can't with 100% certainty say you will be ok. You should be fine though. Maybe others with SIM unlocked phones will chime in.
gnahc79 said:
I don't have a SIM unlocked phone, so I can't with 100% certainty say you will be ok. You should be fine though. Maybe others with SIM unlocked phones will chime in.
Click to expand...
Click to collapse
I am not able to copy the update file to the SD card because I get a message saying “turning off” a little bit after the phone loads the sd card and then I get the "failed to boot 2 starting RSD mode" and after that the only way to take it out of that mode, it’s by removing the battery.
What options do I have now?
Thank you,
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.
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 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
My situation:
.28 Rooted (not unlocked) with a few tweaks such as keyboard and browser2ram.
Tried to JB update via OTA and manual method and got red andy.
Said screw it, took the factory .28 image from asus and loaded it onto my tablet before and after doing a factory reset/data wipe.
So I'm now completely stock and when I check for updates it says not found.
Tried clearing DM and CM CLient as well as cold booting linux [Pow + Vol Dn] and still says "no update found"
So is the WW JB Update still avail or did asus pull it?
Thanks
I'm having the same problem. Can anyone confirm that they have successfully downloaded the JB update OTA in the last few hours?
Happened to me as well, i think after you got red andy once you dont get the ota anymore. I went ahead and used manual upgrade method.
clouds5 said:
Happened to me as well, i think after you got red andy once you dont get the ota anymore. I went ahead and used manual upgrade method.
Click to expand...
Click to collapse
Same problem here. Rooted, locked, stock.
Had the notification bar give me the JB update once, that install failed.
I then checked the f/w update manually, found it, redownloaded it, that install failed.
Now I can no longer get the update via the f/w update checker. (tried many times last night and this morning)
Clouds... is the JB update available to be installed manually? Can you point me in the right direction?
mothman0 said:
Same problem here. Rooted, locked, stock.
Had the notification bar give me the JB update once, that install failed.
I then checked the f/w update manually, found it, redownloaded it, that install failed.
Now I can no longer get the update via the f/w update checker. (tried many times last night and this morning)
Clouds... is the JB update available to be installed manually? Can you point me in the right direction?
Click to expand...
Click to collapse
I think the files you want are linked here, but they take an age to download:
forum.xda-developers.com/showthread.php?t=1909820
I had a completely stock ICS .28 and got a dead droid (DMClient error). I manually downloaded the .28 from asus put it on a micro sd and it found this on reboot and installed OK. Now I am watching the green bar slooooowwwwwlly download the WW rom. The file has no extension, so I can't tell yet whether it is a blob file or the required zip.
ClevaTreva said:
I think the files you want are linked here, but they take an age to download:
forum.xda-developers.com/showthread.php?t=1909820
I had a completely stock ICS .28 and got a dead droid (DMClient error). I manually downloaded the .28 from asus put it on a micro sd and it found this on reboot and installed OK. Now I am watching the green bar slooooowwwwwlly download the WW rom. The file has no extension, so I can't tell yet whether it is a blob file or the required zip.
Click to expand...
Click to collapse
Well, I just finished downloading that file, and whatever it is, and I renamed it as a zip (which it is) and my TFP ignored it. Maybe it needs a specific name to work.
The many of us for which the OTA failed will have to wait for Asus to list the files on their download site.
ClevaTreva said:
Well, I just finished downloading that file, and whatever it is, and I renamed it as a zip (which it is) and my TFP ignored it. Maybe it needs a specific name to work.
The many of us for which the OTA failed will have to wait for Asus to list the files on their download site.
Click to expand...
Click to collapse
Alrighty, thanks.
This is the first time I've had any issues with updates, so was/am hesitant to dive in with the suggested workarounds posted in various places... don't know enough about the whole 'adb shell' stuff, etc, and don't want to make things worse.
I'm assuming that manually updating is relatively simple once Asus provides the files.
mothman0 said:
Alrighty, thanks.
This is the first time I've had any issues with updates, so was/am hesitant to dive in with the suggested workarounds posted in various places... don't know enough about the whole 'adb shell' stuff, etc, and don't want to make things worse.
I'm assuming that manually updating is relatively simple once Asus provides the files.
Click to expand...
Click to collapse
Hi
I had the same problem with the move from Honeycomb to ICS. The OTA would not do it and I got the red/dead droid. I have tried EVERY method to get Jelly Bean. The first attempt was OTA, and this loaded the file and tried to update but failed. Before I did it I back up root and unrooted. I have made no changes to the core system files. I have tried each method posted and none work. It goes straight to a dead driod. I re-installed .28 from the Asus site and still it would not work.
I shall have to wait until Asus decide that those like me 'deserve' JB and post the manual update files on the download page:
http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_Prime_TF201/#download
Indeed.
Once the update is available there, is a pretty straight forward process? Or does it still require terminal commands, etc?
glad to see i'm not the only one.
Guess i'll have to wait for Asus to post the JB files.
after hearing about some of the bricks I'm patient enough to wait a few more days.