With the coming update to .28 dont make the same mistake many of us did with .21. Use rootkeeper, takes a minute and saves a hassle. I've read that .28 fixed the workaround to downgrade so you really dont want to forget to use rootkeeper unless you want to go without root or unlock for a while.
nyijedi said:
Another important reminder before applying the update: If you manually removed or renamed any stock .apks to disable them, be sure to put them back before doing the update, or your Prime could be screwed up
Click to expand...
Click to collapse
Thanks, forgot that!
Just a general shoutout, dont say you werent warned!
(If you have experiences with the .28 update why not keep it in this thread? no use having a dozen threads about the same thing like we do most updates )
EDIT
felisen said:
So I have been meaning to factory reset my prime to get rid of some of the bugs from the HC to ICS update. My plan was to do it after this next update, but your post just reminded me that I would lose root when I reset. Is that correct? Any way to keep it?
Can we root the current update? I'm wondering if I should reset now and root before this upcoming update?
Any info is welcome, thanks!
Click to expand...
Click to collapse
If you want to revert to stock and KEEP ROOT do the following (worked for me, ymmv)
Download the firmware you are CURRENTLY ON (for me its .21)
Put that firmware in the ROOT DIRECTORY of your prime (not the removable SD card)
Restart your prime, it should detect that there is an update available and update you to .21 (the same FW you are on)
NOW that you are stock (all stock apps are there) you can go about reverting back to .15 (or your favorite pre-.21 update), use wolf's guide:
http://forum.xda-developers.com/showthread.php?t=1622628
Get blob file for firmware (download firmware, extract, find blob file. I used .15) MAKE SURE ITS FOR YOUR AREA (Mine is WW)
copy blob file to root dir of the prime
In shell execute: ADB Reboot
let it reboot, dont touch anything
In shell execute: dd if=/sdcard/blob of=/dev/block/mmcblk0p4
it will appear nothing is happening for 3 to 10 minutes. Mine took closer to 15 minutes. BE PATIENT THIS BIT TAKES A WHILE
when you see records in/out in how many seconds you know its done.
in shell execute: ADB Reboot
you should now have a clean, freshly installed prime on .15 Root with your flavor of root tools, use OTA rootkeeper and OTA to .21, then when the OTA to .28 is ready in your area your good to go!
Credit to wolf, go to his thread, hit the thanks button.
Hit my thanks button if i helped! Good luck and i will try to bring forward important info as it happens.
Unless of course Asus do a **** move and completely overwrite /system or rm the voodoo rootkeeper backup specifically in the update script.
Thanks for the reminder.
Maybe Demandarin tells us how he lost his root. Clumbsyness or override by Asus?
Tell us the story bro.
131313 said:
Thanks for the reminder.
Maybe Demandarin tells us how he lost his root. Clumbsyness or override by Asus?
Tell us the story bro.
Click to expand...
Click to collapse
If I had to guess it would be because he had to manually install the update from his micro-SD card. OTA Rootkeeper won't work that way.
Hi everyone
I rooted .15 and use OTA Rootkeeper and then OTA to .21.
When the .28 will be released do I have to do something with Rootkeeper or I just OTA to .28...then open Rootkeeper and recover root from .15?
Thx for answer and sorry for my english
phree1 said:
If I had to guess it would be because he had to manually install the update from his micro-SD card. OTA Rootkeeper won't work that way.
Click to expand...
Click to collapse
ouch !!
Edit:
Let's see; I am on my forth prime since early april now. Three of them on .21 and I had to update all the three via an update.zip from the micro-sd. Do I remember this? Or is it wishful thinking??
... Yeah, I did it from the micro-sd card.... Pure speculation: otarootkeeper will work... Also Demandarin mentioned that GK asked him to do whatever test on his formerly rooted device, so this implies it should still work...but then GK probably doesn't even know how to power on the prime..........................................hell.................
@
lukcinek said:
Hi everyone
I rooted .15 and use OTA Rootkeeper and then OTA to .21.
When the .28 will be released do I have to do something with Rootkeeper or I just OTA to .28...then open Rootkeeper and recover root from .15?
Thx for answer and sorry for my english
Click to expand...
Click to collapse
You shouldn't have to do anything, but to be safe, open the app and ensure that it says something along the lines of "Root backed up/protected."
Another important reminder before applying the update: If you manually removed or renamed any stock .apks to disable them, be sure to put them back before doing the update, or your Prime could be screwed up
nyijedi said:
Another important reminder before applying the update: If you manually removed or renamed any stock .apks to disable them, be sure to put them back before doing the update, or your Prime could be screwed up
Click to expand...
Click to collapse
Say what? This is true?
cam30era said:
Say what? This is true?
Click to expand...
Click to collapse
Your prime won't be screwed up, but you will be unable to load the update.
I speak from personal experience.
I have heard it looks at the 'preinstall' folder.
Where else I do not know? Help
razr maxx - stock rom
cam30era said:
Say what? This is true?
Click to expand...
Click to collapse
phree1 said:
Your prime won't be screwed up, but you will be unable to load the update.
I speak from personal experience.
Click to expand...
Click to collapse
I never made this mistake, so I can't speak from personal experience, but I thought I remember people having problems as a result of this. However, I very well may have just been thinking of being unable to load the latest update.
Regardless, you don't want to experience either of these issues
phree1 said:
Your prime won't be screwed up, but you will be unable to load the update.
I speak from personal experience.
Click to expand...
Click to collapse
Which .apk's have to be "in place" for the update load? All of the Google and Asus ones?
So I have been meaning to factory reset my prime to get rid of some of the bugs from the HC to ICS update. My plan was to do it after this next update, but your post just reminded me that I would lose root when I reset. Is that correct? Any way to keep it?
Can we root the current update? I'm wondering if I should reset now and root before this upcoming update?
Any info is welcome, thanks!
cam30era said:
Which .apk's have to be "in place" for the update load? All of the Google and Asus ones?
Click to expand...
Click to collapse
I think the simple rule of thumb is that anything that cannot be uninstalled the normal way (e.g., through the settings menu without rooting and deleting/renaming .apks) must be present.
Where is the backup file made by Root Keeper saved?
Mine is rooted and su file is saved, but will the OTA delete the restore file when installing the new fw?
Should the Ota RK file be saved on the SD Card instead?
bimbobo said:
Where is the backup file made by Root Keeper saved?
Mine is rooted and su file is saved, but will the OTA delete the restore file when installing the new fw?
Should the Ota RK file be saved on the SD Card instead?
Click to expand...
Click to collapse
You will be fine unless you choose to factory data wipe.
I saved a copy on the SD, just in case.
Appreciate the reminder. Rootkeeper looks to be in order and I think all I changed was the build.prop mod and the gps mod. I just put them back to stock so hopefully I'll be okay. Now comes the wait.
For those who forget how to revert to stock i wrote up a quick guide and posted it to OP.
Basically:
Download current FW
Install current FW
Use Wolf's guide to revert
Root
Use OTA rootkeeper
OTA to current version.
Good luck!
If I disabled some apps in app info will that be OK when updating
Or do I have to enable them all again
Sent from my Transformer Prime TF201 using Tapatalk 2
Related
Picked up an NT finally now that the CM9 looks like it is around the corner.
NT came OOB with 1.4.1... but I'm confused as to which way to best root it? Mind you I've never rooted a device before, JB iPhones yes... first real Android device (other than my Android running over WM on my HTC Touch Pro 2).
From the DEV section it looks like 1.4.1 can be rooted without having flash back to 1.4.0... but it appears it's not 100%. I try to avoid flashing whole updates as much as possible... I'm an old school electronics guy where EEPROMs were good for 20-30 writes before they went in the bin.
So if it's possible I would rather root a 1.4.1 and block OTA... or should I just do the 1.4.0 downgrade that also installs CWM?
IMHO I would revet back to 1.4.0 using This
And then Root using This
From your comments I believe you have already visited the the 2nd thread I linked. Do NOT use any of the files from the OP. Brianf21 posted a file yesterday that is the zero'd out image (smaller) with his latest Update.zip all in one file. It's the only file you will need. Use that file and skip any steps that say to copy update.zip to the Root of the SD card.
There is controversy as to if rooting 1.4.1 using that method leaves side-loading intact. Some say yes, some no. Avoid the controversy and REVERT to 1.4.0.
My .02
Edit: I spoke incorrectly. You will need the file linked in post 14 if you will be using the windows method as it contains the Image Flashing routine. Just use Brian's file when the instructions tell you to browse for the image.
I ended up just using Brian's image from yesterday over 1.4.1... so far so good, have the GApps, can DL from the market, etc.
If anything gets weird, I'll drop down to 1.4.0 and re-root.
quid246 said:
I ended up just using Brian's image from yesterday over 1.4.1... so far so good, have the GApps, can DL from the market, etc.
If anything gets weird, I'll drop down to 1.4.0 and re-root.
Click to expand...
Click to collapse
Can you side-load app's?
Does the unknown sources toggle remain checked?
Is NTHiddenSettings functioning properly?
Thanks!
Edit: Saw your post in the other thread. Guess the answer to the above is NO...
Yeah, I think the 1.4.1 sideloading isn't a 100% guarantee. Perhaps if the NT was at 1.4.0 and then upgraded, there might be something that allows it to be re-opened.
But for a factory fresh 1.4.1... I think it's a no-go.
Will revert to 1.4.0 tomorrow and re-root.
Do I still need to block OTA with Brianf's image or does it cover that?
quid246 said:
Do I still need to block OTA with Brianf's image or does it cover that?
Click to expand...
Click to collapse
I did .... using the Titanium Method (3 files). My version now shows 9.9.9
I too am running 1.4.1 and rooted using Brian's update.zip. The Unknown Sources doesn't stay ticked, and the hack to get it working doesn't work. But I can sideload apps using adb, no problems. I've gotten several live wallpapers I'd be collecting over the last few weeks installed.
I managed to sideload SQLite Editor and manually did the FOTA changes and also edit the "Install_Non_Market_Apps" key in the Settings.db file.
Managed to install Amazon and side-load a bunch of other stuff since. Dunno if the key setting will survive a reboot, will try later tonight.
EDIT: It appears as if doing a manual edit in Settings.db will allow sideloading even after reboot.
OK, I'm a noob and made the noob mistake of deleting (rather than freezing) some system apps after rooting. Won't make that mistake again.
I do not have backups nor am I completely sure which apps are missing. As a result of these missing apps I cannot complete the latest OTA update.
I downloaded a system dump and noted a few apk files in it that were not on my system though I believe that there are other apk files missing which are not in the system dump (MyLibrary, WebStorage etc) so I am not sure the particular system dump I got is up to date.
Copying the apk files to my system\app folder did not help, the update still fails.
I seem to recall seeing instructions somewhere for manual installation via power/down volume which would allow you to see a text dump of the update with reports of missing files or mismatched CRC's. I cannot find this again but such a thing would help me determine what is missing so that I can then attempt to find replacement apk files.
Sorry for being such a noob. Can anyone help?
Thanks
Made the same mistake when upgrading to ICS from Honeycomb...
If you get the previous update (the one your running now) from the Asus website, extract the update file and place it in one of the folders on the tablet, (I forgot which folder, sorry...) reboot and the tab will recognize it and prompt you to update. Once that update is finished installing, you should have all your bloat back. Delete the update file from the tab since you don't need it anymore, and then try to update to the most recent OTA Update.
Just do a search in the TFP forums and you should find complete instructions on how to do this.
I'm just assuming this will work for ICS to ICS... because it worked for me when I updated to ICS to Honeycomb...
Hope this method works for you.
I had the same issue.
Download:
http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF201/US_epaduser9_4_2_11UpdateLauncher.zip
Once downloaded, extract the contents of the zip file (yes, its another zip file of the same name inside) to your MICRO SD. put your micro SD in your TF201 (or eject and re-insert if you copied via cable)
Once the card is mounted you will see a triangle with an "!" in the notification area. Touch the notification and it will open a dialogue to install the manual update.
You will lose root, even with OTA Rootkeeper.
Re-root your device. Install OTA Rootkeeper if you have not already. Run Voodoo OTA Rootkeeper. Protect your su.
Check for updates. Install .13 OTA.
$$$
Should be a lesson learned. Stop messing with system apps. Always causes problems one way or another. The apps included are nothing to even be considered bloat. I still have everything installed n prime super fast. If anything just freeze the apps, never delete them unless u always want to have failed OTA.
demandarin said:
Should be a lesson learned. Stop messing with system apps. Always causes problems one way or another. The apps included are nothing to even be considered bloat. I still have everything installed n prime super fast. If anything just freeze the apps, never delete them unless u always want to have failed OTA.
Click to expand...
Click to collapse
I agree completely, and my lesson is learned. But why on earth would a freaking E-reader app be a system app?
That was my hangup. AsusReader a/k/a the My Library app.
And mine was backed up with Titanium, which obviously bungled it since it would not restore.
phree1 said:
I agree completely, and my lesson is learned. But why on earth would a freaking E-reader app be a system app?
That was my hangup. AsusReader a/k/a the My Library app.
And mine was backed up with Titanium, which obviously bungled it since it would not restore.
Click to expand...
Click to collapse
I went through the same thing on my Atrix phone. Rooted n went messing around deleting at&t bloatware. It killed my OTA updating. That's why now I'm still on froyo on it. Never bothered to manually update it. Still works great on froyo though. But I learned my lesson from that.
demandarin said:
I went through the same thing on my Atrix phone. Rooted n went messing around deleting at&t bloatware. It killed my OTA updating. That's why now I'm still on froyo on it. Never bothered to manually update it. Still works great on froyo though. But I learned my lesson from that.
Click to expand...
Click to collapse
Your still on froyo... why not just flash a sbf file to return to stock? Or better yet, unlock the boot loader and get yourself CM7 already.
Messing with system files isn't a big deal, as long as you have a backup.
Sent from my Transformer Prime TF201 using xda premium
Yep, this did the trick. Thanks very much.
Lesson learned, don't mess with the system apps.
Im getting the problem that a lot of people have gotten, that the android market is no longer working (try to start it; You must add an account to the device to continue. Do you want to add one now?), probably due to an auto update. I had rolled back to 1.4.1 to root (which i later learned was unecessary), so the device updated itself a few weeks after my root. I used albert's method on a 4gb microSD.
Do I need to reroot the device? my concern is, will I lose all my apps, and all the settings of those apps? what all is lost / how should I go about fixing this?
anyone else have or know how to fix this issue?
go back to 1.4.0 and use albert's root sdcard method.
Will this cause it to try to update to 1.4.2 again in the future? Or will this fix it because the root was meant for blocking updates on 1.4.0?
I'll lose all my apps correct?
brutalmouse said:
Will this cause it to try to update to 1.4.2 again in the future? Or will this fix it because the root was meant for blocking updates on 1.4.0?
I'll lose all my apps correct?
Click to expand...
Click to collapse
It all depends which root method you use to root but what you can do is always once rooted apply the the block separately by using titanium backup (indirect's method) that way you won't get the update, so far that is the most reliable way.
Sent from XDA premium using my Nook Tablet
My bad if this is a dumb question, but where can i find documentation on the indirect method? Instructions files etc.. Ready to try this one
brutalmouse said:
My bad if this is a dumb question, but where can i find documentation on the indirect method? Instructions files etc.. Ready to try this one
Click to expand...
Click to collapse
In the development section.
How do i roll back to 1.4.0 with out any back updates and fastboot is not working with the adb fix?
My prime came with 9.4.2.15.
Viper's tool work great. Rooted.
Installed OTA Rootkeeper from the market.
Let the OTA 9.4.2.21 update run.
Restored root with great success.
So those who are still locked(with warranty) should know that 9.4.2.21 update and rootkeeper seem to work.
Now... I have to give this tablet back to my girlfriend and I'm worried about loosing root with a wipe. How should I go about wiping or switching the main user account? Or should superuser and root be immune to wipe? Could I just download rootkeeper again and restore?
thanks in advance... long time android tinker-er but new to rootkeeper and locked bootloaders.
junglizste said:
My prime came with 9.4.2.15.
Viper's tool work great. Rooted.
Installed OTA Rootkeeper from the market.
Let the OTA 9.4.2.21 update run.
Restored root with great success.
So those who are still locked(with warranty) should know that 9.4.2.21 update and rootkeeper seem to work.
Now... I have to give this tablet back to my girlfriend and I'm worried about loosing root with a wipe. How should I go about wiping or switching the main user account? Or should superuser and root be immune to wipe? Could I just download rootkeeper again and restore?
thanks in advance... long time android tinker-er but new to rootkeeper and locked bootloaders.
Click to expand...
Click to collapse
I wish Rootkeeper would include the option of choosing where you put your backup..
Anyway, the wipe will eradicate any and all data on the Prime, including the SU backup that Rootkeeper creates. *Root stays intact, just not the backup.*
But, lucky for you, sparkym3 has graced us with a root app that you can keep ready to go in your ASUS WebStorage or DropBox or external mSD card, whatever you want.
But again, everything on the internal SD card will be lost when you wipe so be sure to back up your apps and their data (don't do system apps and data, restoring these usually just causes problems) to a location other than /sdcard along with any movies, music, and other personal files.
*EDIT:
Actually, no root methods currently work on .21, ASUS patched the exploit (badly I may add)
Factory reset should not touch root and you have root keeper so your good.
Blackwidowman said:
Factory reset should not touch root and you have root keeper so your good.
Click to expand...
Click to collapse
this is true as I had trouble trying to unroot on. 21 after using root keeper, as a factory data reset does not remove root
JSale said:
this is true as I had trouble trying to unroot on. 21 after using root keeper, as a factory data reset does not remove root
Click to expand...
Click to collapse
This is true. But it does remove the backup and all other files, so you need to be sure and back up as well as run Rootkeeper again after the wipe.
Why trying to unroot? You could try reverting to .15 either through an "emergency update" or with the .blob method, both of which are in my signature, then remove root and upgrade again to .21.
At this point however, you'll be at the mercy of time for the next root method; you won't be able to revert again I don't think since you won't have root.
I installed .21 and my root access was intact. I did not use OTA rootkeeper. Do I need to use it?
---
Sorry . I mixed up with HTC sensation upgrade. I used OTA rootkeeper to restore root.
If you have safestrap go into the app, select the uninstall feature and re try the install. No need to download anyones utility or no need to factory reset.
do you happen to know the download path of the ota? Due to safestrap mine failed.. hate to download it again..
Should be in setting/ about phone/ updates
yeah thats to download it again.. i was hoping it would just install it if the system saw the file there. oh well at 55% i can wait a little longer..
After the phone reboots, if the install takes really really slow then ur on the right path
What if I have installed BootStrap recovery????
kanagadeepan said:
What if I have installed BootStrap recovery????
Click to expand...
Click to collapse
I dont have bootstrap but from what im gathering unistall that as well
then uninstall it.. my install failed with it. That is what the OP is saying you will need to uninstall them for the update to install
mine failed for a second time :/
Did you use voodoo ota and temp unroot? You need to do that as well i just figured that was a given by now
cheatthepocket said:
Did you use voodoo ota and temp unroot? You need to do that as well i just figured that was a given by now
Click to expand...
Click to collapse
Arrgh i swear i did.. While i was doing tb backups it slipped my mine i reckon.. really wish i could find the dl path for the update... hopefully third time will work!
Whether uninstalling the "Razr BootStrap" using "Managa Applications" is enough... Or I have to do some extra steps too????
Please help me... I don't care much about root, as the update usually unroots it and I can root again easily...
Bootstrap may be a dif problem. Like i said i used safestrap. I dunno what else you have done to urvphone. You might need the dev team to help you. I never used roms so i was stock i also never froze any bloatware.
Ummm. You're welcome....
Sent from my DROID RAZR MAXX via XDA Premium
I think i thanked you last night lol.
arrgh 3rd time failed no bloat removed just stock rooted.. temp unrooted safestrap uninstalled.. any ideas? guess i might need to restore back to stock..
Sounds like you have something breaking the install. I know ive done very little to my phone. Factory reset may be your option but i would get hold of a tech here b4 u do anything
kanagadeepan said:
Whether uninstalling the "Razr BootStrap" using "Managa Applications" is enough... Or I have to do some extra steps too????
Please help me... I don't care much about root, as the update usually unroots it and I can root again easily...
Click to expand...
Click to collapse
You need to first uninstall the razr bootstrap app through "manage apps" (look under the all apps tab - clear data first while you're there).
Then, with root explorer or such, go to the /system/bin folder, mount r/w, and delete the following files:
hijack
logwrapper
Then, rename logwrapper.bin to simply logwrapper (just remove the .bin)...
Reboot, and it should be all cleaned out.
I would also recommend using voodoo ota rootkeeper to backup your root, then temporarily un-root (hide root) before doing the OTA install.
If you still get ota install errors, then you probably removed some system apps that are verified before installation... check /cache/recovery/last_log for errors.. then either replace those apk/odex files, or flash the fxz..
Sent from my phone's mind
alteredlikeness said:
You need to first uninstall the razr bootstrap app through "manage apps" (look under the all apps tab - clear data first while you're there).
Then, with root explorer or such, go to the /system/bin folder, mount r/w, and delete the following files:
hijack
logwrapper
Then, rename logwrapper.bin to simply logwrapper (just remove the .bin)...
Reboot, and it should be all cleaned out.
I would also recommend using voodoo ota rootkeeper to backup your root, then temporarily un-root (hide root) before doing the OTA install.
If you still get ota install errors, then you probably removed some system apps that are verified before installation... check /cache/recovery/last_log for errors.. then either replace those apk/odex files, or flash the fxz..
Sent from my phone's mind
Click to expand...
Click to collapse
Thanks so much for the info. That logwrapper file was withholding me from updating.
I tried deleting and renaming the files with no success updating. I eventually just ended up doing a factory wipe and using Matt's Utility and flashing back to stock. It was a little frustrating, but the Verizon backup utility combined with Google services saved me. I guess i need to learn how to use Titanium backups. lol
this thread should be titled "How I got my Safestrapped RAZR to install ICS OTA successfully", as your issue was more to do with safestrap then specifically just being rooted.