Ok, From now on if i see people asking how to update / how to keep root im going to link you to this thread, im tired of answering it.
This works if you are on STOCK RECOVERY. If you are unlocked there are lots of other options for you (such as flashing a rooted kernel) so go to development and find that. Since im not unlocked i had to do it the hard way. This method works if your OTA updates are screwed up. If you HAVE OTA updates you can just use OTA rootkeeper to backup and disable root, make sure all stock apps are restored, and proceed with root.
Note for the updater: The OTA updater is a DIFFERENCE updater, if files are missing or different versions the update will fail. Best practices say to update sequentially, never skip an update. It might not cause problems now but could cause problems in the future.
If your OTA updates have failed or for whatever reason you can not get OTA's, you have a LOCKED bootloader, or for whatever reason want to manually update and keep root then this guide is for you. Also please note the process for going from .16 to .18 is the same as going from .30 to .16.
First: Make sure you have all stock apps restored, no custom build.prop, etc.
If your not sure, wipe the tablet and reinstall. Better safe than sorry.
To reset the tablet if you dont have stock apps:
Determine which version you are running. For me it was .30WW
Go to www.asus.com and download the firmware for your version
plug your tablet into the usb on your computer, unzip the firmware and put it in the root of your tablet (Dont use USB memory sticks or SD cards, just transfer it directly)
restart your tablet, it SHOULD load the file and go about resetting the tablet to stock.
If that does not work, try starting the tablet holding power and volume down, on the splash screen press volume up and reset the tablet that way.
Once your tablet is returned to stock you can proceed.
Click to expand...
Click to collapse
Make sure you are ROOTED. Use whatever method works for you.
Now would be a good time to make sure superuser is updated, mine was old so a quick update on the market and its all good.
Use OTA Rootkeeper to backup root
Download the DLPKG file apropriate for your version.
If you want to update to JB you must have .30 installed and download the .16 file, WW or US, depending on your region. Other packages are provided for convenience (This method can be used to spoof the OTA update to any version as long as you have the file)
DLPKG for .26 WW HERE
DLPKG for .30 WW HERE
DLPKG for .16 WW HERE or HERE or HERE
DLPKG for .16 US HERE or HERE
DLPKG for .18 WW HERE or HERE
DLPKG for .18 US HERE or HERE
(Make sure you only take the file for the version you want to update to, only one step at a time, so if you are on .30 WW you need .16WW before you can do .18WW)
DLPKG for US .20 HERE
DLPKG for WW .20 HERE
DLPKG for US .23 HERE or HERE or HERE or HERE
DLPKG for WW .23 HERE
DLPKG for .25 WW HERE
You will also need the command file HERE or HERE
Transfer the files to your tablet using the USB cable.
If you use a USB memory stick or SD card make sure its formatted FAT32.
Please note there have been reported problems with people using USB memory sticks or SD cards, often the files fail. I have had best success using the USB cable provided with my tablet and directly transferring the file. YMMV.
Click to expand...
Click to collapse
Once the files are on the tablet use Root Explorer or your favorite root file browser to move the two files
(NOT THE STOCK FILE BROWSER IT CANT SEE THE ROOT DIRECTORY)
"command" goes to /cache/recovery
"dlpkgfile" goes to /cache
Make sure the files are named exactly as shown above. No capitals, no file extensions, etc.
Make sure the permissions for both files are changed to RW-R-R for both.
Note: There has been a little confusion about "root directory" so i will explain a little further. The root directory is generally protected. You will have to be rooted (by definition, having root access, kind of like administrator access in windows) and use a file browser like root explorer. The stock file browser only lets you see a few specific areas and will not let you access the root directory of the tablet. Root explorer will also let you modify permissions which the stock browser will not let you do. Im sure there are other browser applications that work equally well as root explorer, thats just the one i have had success with. As always, Your Milage May Vary.
Click to expand...
Click to collapse
Go into OTA Rootkeeper and TEMP UNROOT.
Shut down the tablet. Remove the USB cord. Remove any USB memory sticks. Eject your Micro SD card. UNdock the tablet. Lets not let anything go to chance.
Press and hold both the power and volume down buttons (volume down is closest to the power button in case you forgot like me)
Soon as the splash screen comes up you should see some text on the left side, release the power and volume down buttons and press volume up.
Now just sit back and wait, this can take a while. I got myself a snack and took this time to stretch a little.
Once your all booted up you should be running JellyBean. Open OTA Rootkeeper and restore root.
Please note i did not come up with the steps in this guide. I did not originate the files. I am nowhere near smart enough to do all this on my own. I meerly collected the information and links to files and pieced it all together. I wrote this so even my father could follow these instructions so hopefully you all succeed! If something needs clarification please let me know.
- Edit -
Added notes on restoring tablet to stock.
- Edit -
Added .18 links. Thanks to xcal321 for providing them.
- Edit -
Cleaned up the guide a little. Hopefully its less wordy and easier to follow.
- Edit -
Added links to my personal google drive for nearly all the files, should have no problem for overseas users with limited access to mediafire
- Edit -
Sorry it took so long, added files for .20 US and WW. Will copy them to my personal Gdrive when i have more time.
- Edit -
Still alive, added .25 WW. Nearly all the files are uploaded to my personal google docs account so if something goes screwy let me know via PM
That is very helpfull !! Thanks for that !! Just one question: What about if I downgrade to .30 with clean system, root my device, update superuser app, then use OTA Rootkeeper to backup my root, next Temp unroot via OTA Rootkeeper and use upgrade to JB with OTA (not using files that you put above )?? It still works, any ideas ??
Regards
Doncieslacco
doncieslacco said:
That is very helpfull !! Thanks for that !! Just one question: What about if I downgrade to .30 with clean system, root my device, update superuser app, then use OTA Rootkeeper to backup my root, next Temp unroot via OTA Rootkeeper and use upgrade to JB with OTA (not using files that you put above )?? It still works, any ideas ??
Regards
Doncieslacco
Click to expand...
Click to collapse
If OTA works for you after that then use OTA. For a large portion of us OTA did not want to work so these are the steps i used. Essentially its the same thing, OTA downloads the same files and puts them in the directories mentioned. Just make sure you do the temp unroot before updating as forgetting to do that step has lost some people root.
This method never worked for me, even when it was originally posted. I keep getting the dead android bot red triangle.
It may be that I'm moving the files from win 7 NTFS to fat 32 and that is somehow modifing them???
Also is there a way on android to check/modify write permission? I just modify write permissions of the files by right clicking them and modifying them from the security tab in windows.
I'll have to examine this in further detail this week.
I'm a bit hesitant to jump to JB because of rooting and DPI setting problems. Until thats ironed out I'll stick with ICS.
Did it twice but was unsuccesful. When the whole process completed I was back on .30 and couldn't restore root. Any suggestions?
Syn010 said:
This method never worked for me, even when it was originally posted. I keep getting the dead android bot red triangle.
It may be that I'm moving the files from win 7 NTFS to fat 32 and that is somehow modifing them???
Also is there a way on android to check/modify write permission? I just modify write permissions of the files by right clicking them and modifying them from the security tab in windows.
I'll have to examine this in further detail this week.
I'm a bit hesitant to jump to JB because of rooting and DPI setting problems. Until thats ironed out I'll stick with ICS.
Click to expand...
Click to collapse
It's very possible that the issue with your sd card, make sure it's 32gb or smaller, find another sd card reformat with fat32 and try again. tf700 could read your card while it's on but not in recovery mode.
---------- Post added at 08:36 PM ---------- Previous post was at 08:35 PM ----------
john85D said:
Did it twice but was unsuccesful. When the whole process completed I was back on .30 and couldn't restore root. Any suggestions?
Click to expand...
Click to collapse
are you unlock or locked? did you try to upgrade from .30 to JB?
buhohitr said:
It's very possible that the issue with your sd card, make sure it's 32gb or smaller, find another sd card reformat with fat32 and try again. tf700 could read your card while it's on but not in recovery mode.
---------- Post added at 08:36 PM ---------- Previous post was at 08:35 PM ----------
are you unlock or locked? did you try to upgrade from .30 to JB?
Click to expand...
Click to collapse
I'm unlocked and started the process on. 30 rooted. I did downgrade from JB though and wanted to be rooted again. Should I try to upgrade to JB manually? How should it update to JB, OTA download?
buhohitr said:
It's very possible that the issue with your sd card, make sure it's 32gb or smaller, find another sd card reformat with fat32 and try again. tf700 could read your card while it's on but not in recovery mode.
Click to expand...
Click to collapse
I used a USB cable 2.0 to transfer the files directly to tablet. Also, the cache folder is created on the root level of the tablet right, because originally I never had a cache folder on the tablet at the root level. thanks and cheers.
Here's what I did, and it worked beautifully.
I had unlocked with the guide, rooted .30, ran OTA root keeper, downloaded the JB file from Asus, flashed it in twrp, never lost root
Sent from my Galaxy Nexus using xda premium
Jimmah555 said:
Here's what I did, and it worked beautifully.
I had unlocked with the guide, rooted .30, ran OTA root keeper, downloaded the JB file from Asus, flashed it in twrp, never lost root
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
TWRP implies unlocked, this method is for locked bootloaders.
If you are still getting the dead android try restoring the tablet to factory condition before proceeding. If you have any frozen apps, if you removed any stock apps, if you have a modified build.prop, etc. it can cause the update to fail.
i will update OP with instructions to return to stock.
Syn010 said:
This method never worked for me, even when it was originally posted. I keep getting the dead android bot red triangle.
It may be that I'm moving the files from win 7 NTFS to fat 32 and that is somehow modifing them???
Also is there a way on android to check/modify write permission? I just modify write permissions of the files by right clicking them and modifying them from the security tab in windows.
I'll have to examine this in further detail this week.
I'm a bit hesitant to jump to JB because of rooting and DPI setting problems. Until thats ironed out I'll stick with ICS.
Click to expand...
Click to collapse
Windows security and linux permissions are two VERY different things.
Use something like root explorer to modify the permissions of the files once they are on the tablet. Once you transfer the files to your SD card or even via USB to the tablet the permissions get changed to RW-RW-RW or similar. As far as i know you can not do this in windows.
Syn010 said:
I used a USB cable 2.0 to transfer the files directly to tablet. Also, the cache folder is created on the root level of the tablet right, because originally I never had a cache folder on the tablet at the root level. thanks and cheers.
Click to expand...
Click to collapse
Use an application like root explorer. Regular file explorers can not usually see the root directory of the tablet. If you are just using the stock file browser it will not work.
pileot said:
First: Make sure you have all stock apps restored, no custom build.prop, etc.
If your not sure, wipe the tablet and reinstall. Better safe than sorry.
Click to expand...
Click to collapse
Thanks for the OP. I am having trouble getting the JB OTA.
I am running rooted and locked at .30 with some minor tweaks using Titanium backup. Those tweaks are removing ASUS and Google bloat app. In order to get JB OTA, do I have to reinstall the bloat apps or reflash .30? Does all the stupid bloat have to be there for OTA to occur? If so, I hate that.
john85D said:
Did it twice but was unsuccesful. When the whole process completed I was back on .30 and couldn't restore root. Any suggestions?
Click to expand...
Click to collapse
I've got the same...kind of pissed. Am I just SOL without root now?
Edit: Nevermind...just ran through the whole root process again and got it back.
quartercirclebak said:
I've got the same...kind of pissed. Am I just SOL without root now?
Edit: Nevermind...just ran through the whole root process again and got it back.
Click to expand...
Click to collapse
What did you use to gain root again? As far as I know, rebuffs does not work with JB. Or are you unlocked?
everytime i do, i get back to .30 and when i check /cache
dlpkgfile still there with rw-r-r
but command in /cache/recovery/ disappear
what i mistaken?
-lukin- said:
Does all the stupid bloat have to be there for OTA to occur?
Click to expand...
Click to collapse
Yes. Since the OTA is a "difference file patcher", the original files need to be where they are expected to be, otherwise the instructions as to which areas of which files should be patched with which values will be invalid. There is no way a difference file patcher can operate if the files are missing or modified - it's in the nature of the beast.
That's why the only option for people who have modified their /system partition is to reflash the entire /system partition (ie. a full update, not one that relies on what is already there).
The reason for using a difference file patcher is that the update will be much smaller if it only contains the differences from the existing setup instead of a completely new file. The downside is that the existing contents needs to be present and unmodified.
HeartWare42 said:
Yes. Since the OTA is a "difference file patcher", the original files need to be where they are expected to be, otherwise the instructions as to which areas of which files should be patched with which values will be invalid. There is no way a difference file patcher can operate if the files are missing or modified - it's in the nature of the beast.
That's why the only option for people who have modified their /system partition is to reflash the entire /system partition (ie. a full update, not one that relies on what is already there).
The reason for using a difference file patcher is that the update will be much smaller if it only contains the differences from the existing setup instead of a completely new file. The downside is that the existing contents needs to be present and unmodified.
Click to expand...
Click to collapse
Makes sense, thanks for the the concise explanation.
Thank you so very much. kept trying to root jelly bean before, and ended up bricking tab somehow. thankfully best buy exchanged under factory defect cause after bricking, it got super HOT. I'll donate some adult beverage money when i get paid.
thank you again.
Hello !
First of all, thank you for your post.
I have a question "Yes or No". I translated your method (thank you again) in french for the french users, and I told them that they could unlock the bootloader once the firmware is back to ICS (.30). I am not sure about it, I would like you to confirm this ?
Then the method would be :
Downgrade to ICS (v9.4.5.30 WW)
Root with RootDebugfs.bat
Unlock Bootloader
Temp unroot with OTARootKeeper
Upgrade to JB (v10.4.4.16 WW) with OTA
Restore root with OTARootKeeper​
Related
This is the Stock 8.6.5.13 US update repackaged with:
* Clockworkmod support (It does not include CWM, but doesn't reflash the recovery partition either)
* Rooted (includes SuperUser.apk & su 3.0.0)
* Busybox (1.19.2)
This update worked fine on my TF101. I built it using the same method Roach2010 used to make his previous CWM-repacks so it should be ok. I have only tested this on my own tf101. Let us know when it works for yours too!
This will not work unless you have:
1. clockworkmod
2. STOCK firmware (root is fine)
3. the US or WW firmware
4. firmware 8.6.5.9
If this update will not apply, take note of which assert stopped the process. You probably applied some sort of mod to your transformer.
There was an issue in the initial release. If you downloaded it, delete it and download the new one.
CWM package for ASUS FOTA Update 8.6.5.13 US
http://bellybuttonporn.com/android/transformer/kwt-cwm-8.6.5.13-proper.zip
Problems updating? Customized Transformer? Try the Update checker.
http://bellybuttonporn.com/android/transformer/kwt-cwm-8.6.5.13-checker.zip US
The Update checker will verify all of the same files that the update verifies. It will not stop on the first error. This way, you can see ALL the files which will cause errors and fix them all at once without the tedious reboot / try update / reboot / fix problem / reboot / try update loop.
Courtesy of brk:
CWM package for ASUS FOTA Update 8.6.5.13 WW (with root and CWM recovery)
http://www.multiupload.com/KTGLKFJME5
Has this been tested yet??
Thanks
*Offtopic*
delete ffs
same here, stock but with xoom system UI and bloatware deleted.
Sorry, in my haste I didn't update the recovery binary.
Fixed version in testing now.
Updated first post, new zip is available here:
http://bellybuttonporn.com/transformer/kwt-cwm-8.6.5.13-proper.zip
cky2000 said:
for me, it did not work.
I tried from a fresh/clean install (nvflash) of US_epad-user-8.6.5.9. and got this error in CWM:
assert fail: getprop ("ro.product.device") == "EeePad" || getprop ("ro.product.device") "EeePad"
E:Error in /sdcard/kwt-cwm-8.6.13.zip
(Status 7)
Installation aborted.
bellybuttonporn
Click to expand...
Click to collapse
Seems you didn't edit the update-script to remove that check. Either way let me know how it goes. I made myself an cwm zip that I used to update my TF this afternoon. I didn't bother to add in SU seeing as though the update is just a patch and the TF should already be rooted.
@daoist If your new update.zip doesn't work let me know I'll upload mines and you can post it.
Hi,
I am still pretty new to all of this, I have rooted my TF, right now I have a US ver 8.6.5.9 rooted with CWM and I am getting the notification to update firmware.
Is this the file I need to update my TF and keep root, it looks to me like it is but I am not 100% sure, also I am not sure how to apply the patch.
To apply this do I use CWM? The step[s I think I need to do is
1. copy the file top my SD card,
2. Boot to CWM
3. choose install zip
4. pick the zip downloaded from this thread
5. then watch and make sure works, then reboot
OH, I have the netflix patch (libnvomx) file copied over the original in my TF, should I put the original back before trying ng this?
Is this correct?
thanks for any help and the file!!
John
Cordy said:
Seems you didn't edit the update-script to remove that check. Either way let me know how it goes. I made myself an cwm zip that I used to update my TF this afternoon. I didn't bother to add in SU seeing as though the update is just a patch and the TF should already be rooted.
@daoist If your new update.zip doesn't work let me know I'll upload mines and you can post it.
Click to expand...
Click to collapse
You referring to the check that goes through and looks for mods and missing apps? Is it possible someone could upload a version that doesnt run that check? I replaced SustemUI and basically deleted everything I didnt need (and didnt back up individual files, just made a full backup) so it would take me a while to track down all of the APKs.
If I recall someone posted the .9 update without the check for the existing apps.
EDIT: I actually found a backup for my stock apps and copied all of them back over and its still failing. AWS.odex, first one (and its installed).
Xerravon said:
Hi,
I am still pretty new to all of this, I have rooted my TF, right now I have a US ver 8.6.5.9 rooted with CWM and I am getting the notification to update firmware.
Is this the file I need to update my TF and keep root, it looks to me like it is but I am not 100% sure, also I am not sure how to apply the patch.
To apply this do I use CWM? The step[s I think I need to do is
1. copy the file top my SD card,
2. Boot to CWM
3. choose install zip
4. pick the zip downloaded from this thread
5. then watch and make sure works, then reboot
OH, I have the netflix patch (libnvomx) file copied over the original in my TF, should I put the original back before trying ng this?
Is this correct?
thanks for any help and the file!!
John
Click to expand...
Click to collapse
Yep, that's correct.
One note is because of how the TF handles storage, you want this in your /Removable/microSD. If you put it in /sdcard it's not actually in your sdcard.
When you reboot into CWM make sure to choose to pick a file from your sdcard, rather than just applying update.zip (in case you didn't actually name it update.zip)
ryan stewart said:
You referring to the check that goes through and looks for mods and missing apps? Is it possible someone could upload a version that doesnt run that check? I replaced SustemUI and basically deleted everything I didnt need (and didnt back up individual files, just made a full backup) so it would take me a while to track down all of the APKs.
If I recall someone posted the .9 update without the check for the existing apps.
EDIT: I actually found a backup for my stock apps and copied all of them back over and its still failing. AWS.odex, first one (and its installed).
Click to expand...
Click to collapse
The problem with removing the check is that this update is doing patching, rather than replacing files.
If you're just replacing files, you can skip the checks and it will work fine.
If you're patching files, if you skip the check, the patching process will not work (best case scenario). will leave your system in a quasi-updated state (middle case), or destroy the target file (worst case).
Maybe someone who's still on 8.5.6.9 can post their AWS.odex file for you to copy onto your device?
The issue is I have it back on my device, I found it, and the update is still hanging on that.
daoist said:
Yep, that's correct.
One note is because of how the TF handles storage, you want this in your /Removable/microSD. If you put it in /sdcard it's not actually in your sdcard.
When you reboot into CWM make sure to choose to pick a file from your sdcard, rather than just applying update.zip (in case you didn't actually name it update.zip)
Click to expand...
Click to collapse
Hi,
Thanks for the help! It worked like a charm, no problems at all.
I am wondering now, do I need to update my CWM recovery, or do I just leave it how it is?
thanks for the file and help!!!
Now I just have to figure out how to get rid of the notification...
Has anyone noticed the web browser performance? Is it still checkerboard on display? Where it displays the page in chunks... and is this android 3.2.1? or just firmware update?
Worked fine on mine, Thx.
daoist said:
The problem with removing the check is that this update is doing patching, rather than replacing files.
If you're just replacing files, you can skip the checks and it will work fine.
If you're patching files, if you skip the check, the patching process will not work (best case scenario). will leave your system in a quasi-updated state (middle case), or destroy the target file (worst case).
Maybe someone who's still on 8.5.6.9 can post their AWS.odex file for you to copy onto your device?
Click to expand...
Click to collapse
Would it be possible to remove the check and the patch? I am looking at the updater script, what I would love is to just remove its check and attempt at patching the bloatware.
For Example, the Check:
assert(apply_patch_check("/system/app/Finsky.apk", "19a70336522820f20a9e1d9f065ae56a714aa7cf", "690dc80af4303cb2df1991de9d52c269211e1dcf"));
set_progress(0.116486);
assert(apply_patch_check("/system/app/Finsky.odex", "fda5fbff54fc6c35b9210afd4a3b76b6a8862d83", "59412510a7d0a789b1e732dbffdc9feb3245e964"));
set_progress(0.119390);
And the Update:
apply_patch("/system/app/Finsky.apk", "-",
19a70336522820f20a9e1d9f065ae56a714aa7cf, 1070527,
690dc80af4303cb2df1991de9d52c269211e1dcf, package_extract_file("patch/system/app/Finsky.apk.p"));
set_progress(0.135043);
apply_patch("/system/app/Finsky.odex", "-",
fda5fbff54fc6c35b9210afd4a3b76b6a8862d83, 655760,
59412510a7d0a789b1e732dbffdc9feb3245e964, package_extract_file("patch/system/app/Finsky.odex.p"));
set_progress(0.138224);
If I didnt want it to update finksy (bad example but just one I grabbed) could I just delete everything above from the script? In the case of something like Zinio I dont even want the update since I nixed the underlying app.
I actually tried something like that but it failed immediately, no error. Im wondering if I havent zipped it up right.
Yeah, if you search through the update script for the name of the file that's erroring out, there's 2 places. First the assert, then the patch. Get rid of both and you're fine.
I'd google what those files are before you remove them from the script, just to be safe.
Just for example, Finsky is part of Market
Im wondering if there is something I am doing wrong or if there is a trick to zipping it back up. I tried removing those lines (for AWS, not Finsky ) and the update failed without an error (just aborted).
Im wondering, should I be leaving that set progress, zipping using a particular method?
The biggest problem I had was making sure the files were saved with unix line-endings. If you edited it in notepad or something like that it may have defaulted to windows line-endings.
Hi can you add this to 1st post:
CWM package for ASUS FOTA Update 8.6.5.13 WW
(with root and CWM recovery)
http://www.multiupload.com/KTGLKFJME5
If it gives you an error about some file check, edit update script and put a "#" before the line of that file.
Thought I backed up original ROM, when I opened the file today it was blank (NVFLASH).
I did copy the internal sd and have a copy of that but its not the right file type.
I also have some image files of the ROM, can I use either of these?
How about a little more information.... what file did you open that was blank?
Do you have files that look like 09_APP_raw.img? Did you use a script or just type a bunch of stuff in at the command line?
How did you copy the internal SD card that it is not the right file type?
What are these image files of the ROM?
So many questions...
The way I copied the internal sd was in the file manager, had to click show hidden files to do it.
The blank file was a file that brk asus transformer root toolkit made. Went to do a restore with it the next day and file not found,
The image files I have are ones that another version cwm m ade doing a backup a few times that I got from the market. But that version of cwm doesnt support asus.
OK- it that helps. If you just want the stock firmware, you can get that from the ASUS website. You might have to get the 8.6.5.9 version and then upgrade to 8.6.5.13 via the ota. From there you can root again and/or install CWM if you want.
There are TF specific versions of CWM- solarnz and roach each have a version in the dev section. These might allow you to flash the data partition from your backups to restore any apps that you installed. I think brk's tool uses one of the modded versions of CWM.
As far as the internal sd card, you might have to copy those over with an external SD card/adb/ftp/etc.
If you want to restore one of the CMW images you have, that might be tricky, but you can extract them with the unyaffs tool. Google should find it for you. They might be flashable with one of the modded versions of CWM, but I think the modded versions have a slight difference in the parts that they backup/restore. You can try the "advanced restore" option to restore the data.img, but I'm not sure what would happen.
I looked at asus website for the rom, all I found were firmware and kernels are those the roms? I would prefer doing it that way.
Yup- select the android OS and pick your country specific firmware (aka ROM).
It might be tricky if you are downgrading I.e., you flashed 8.6.5.13 and want to flash the stock 8.6.5.9 firmware. I'm not sure if you can downgrade the "easy" way.
The easy way is to unzip the firmware and place the whole ASUS folder on your external SD card. Turn on the TF and insert the SD card when it is running- a notification should pop up to flash. ASUS has some documentation with pictures in the Manuals section. Look for one of the "Update SOP" files.
Let me know if that works. I've never tried to downgrade that way, so I'm not sure if it will work because you might be on a higher build number. If it doesn't, there is another way if you are rooted or you can use nvflash.
Let me get this right, do I use the firmwaree or the kernel.
Use the firmware.
Thanks, I reread the firmware aka rom. I'm in the us so the us one right! Will let you know if it works, says something about downgrading in there...
If it won't let you downgrade, then you have to do it the "hard" way.... but you have to be rooted.
Download the firmware and unzip it. It should be something like ASUS/Update/some.zip
Unzip the some.zip file and it'll contain a blob. Copy the blob to your external sd card or use adb to push it to your TF.
It would be a good idea to verify the MD5 sum of the blob. The US one that I downloaded for 8.6.5.9 is
MD5(blob)= 57d4c4342277d39e523e26b943891a1f
Use terminal on the TF or adb shell from your PC and type the following:
Code:
su
dd if=/Removable/MicroSD/blob of=/dev/block/mmcblk0p4
the last three characters are zero-pee-four. It's important to get this right or you could mess up your TF.
If you copied it somewhere else, then adjust the /Removable/MicroSD/blob part.
It will take a while because it's a big file, but when it's done, type "reboot" or just turn off, then turn on your TF, and it will flash you back to stock. You should see a blue progress bar that moves very slowly. Be patient, it takes a while and should reboot when it's done. You will be unrooted with a stock recovery at this point.
Afterwards, you can verify that you have the downgraded firmware and then check updates to receive the OTA to upgrade to 8.6.5.13. Lastly, clean up and remove the blob file from your sdcard- it's 521MB!
Your awsome man! You took all that time to help me out and I won't forget it gee!
So did the downgrade work, or did you have to flash the blob?
Not gonna try tonight, thats how I lost the backup as I was tired... Will try tomorrow and will let you know what workes.
I have prime on here now so I dont think that would technically be a downgrade?
Yes I am rooted.
So while I have you, will a rooted machine get OTA updates?
Yup, the updates still download, but they usually break root or won't flash because something is not stock, such as kernels.
Of course, you can mod them so they flash and keep root.
Good idea about starting fresh tomorrow.
r u Randal in Ca?
No, sorry.
No worries, just reminded me of the big guy. Will let you know how everything goes. I try to be sure before I comet to a change I can't recover from so will have to sus up everything first.
I want to thank you again for the help, I hope you get compensated for it?
Hardy har har, and I'm still in thi situation!
We will see tomorrow!
I have tried to root my TF doing it the way trippmcnealy say and to no success. I would get the android with gears turning then it would turn into an exclamation point and after a bit boot normally.
Anyone has the same issue? If not and you successfully rooted, feed back would be great. Oh when I got it, I updated without thinking.
Build# HTK75.US_epad-8.6.5.21
Any help would be great appreciated.
You can't root a b90 on .21, you have to downgrade to .19 and root with razor claw.
Brand New said:
You can't root a b90 on .21, you have to downgrade to .19 and root with razor claw.
Click to expand...
Click to collapse
Is there a method that you are aware of at this point in time that allows you to downgrade from .21? If so could you provide a link?
CobraBytez said:
Is there a method that you are aware of at this point in time that allows you to downgrade from .21? If so could you provide a link?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=20799328
baseballfanz said:
http://forum.xda-developers.com/showthread.php?p=20799328
Click to expand...
Click to collapse
Already tried that multiple times and it didn't work.
felix8787 said:
Already tried that multiple times and it didn't work.
Click to expand...
Click to collapse
Double check your file to make sure it's not filename.zip.zip if your PC is set to hide known extension and you rename it to filename.zip you're gonna get the extra .zip behind it.
Also it seems like the 2nd method by trippmcnealy getting better results for peoples
Did that too. I caught the .zip.zip and changed it. Still nada. Will try again. Another thing, from the external sd card, you take the file and copy and paste to filemanager and not in a folder correct? Cause I wasn't putting it in a folder and just added to the filemanager.
Yes it has to be on the root of the sd card, don't put it in any folder.
It will scan the sd card but not scan inside any folder.
Seems like you need two files on the external sd card and two files on the internal sd card as per trippmcnealy's method
So I leave the USB hooked up also as it's recovering? Will try now but with the US .13 first then update to WW .19.
No you don't need the USB connected.
Also after you downloaded the file you did unzip to get
WW_epad-user-8.6.6.19.zip out of the zip file correct?
Pasted onto root of internal..........powered down......volume down/power then up when prompted...nothing.
felix8787 said:
Pasted onto root of internal..........powered down......volume down/power then up when prompted...nothing.
Click to expand...
Click to collapse
you pasting one or two files to the internal sd card?
2, EP101_SDUPDATE and the WW_epad-user-8.6.6.19, still getting the yellow triangle with the exclamation point.
felix8787 said:
2, EP101_SDUPDATE and the WW_epad-user-8.6.6.19, still getting the yellow triangle with the exclamation point.
Click to expand...
Click to collapse
You can try this to see, someone said they changed the WW to US and it worked for them. Outside of that I'm not sure what else you can do.
Thats exactly what I was getting ready to do....let you know how it goes.
Quick update, nothing, I did notice that when I do a recovery it says something about recovering kernel and not update?
wait a min...........well, this is what it tells me.
System Update
The update package is not compatible with your current software, please check your software version and version number in Settings and try the correct update package.
System is restored to previous configuration.
After you download the file, did you extract the file within or are you using the file as is?
I transfer both files without extracting anything. Going to try and do the US.13.
Well that didn't work, looks like I will have to wait for a fix, thanks for you time and help!
All credit goes to original posters- this information was compiled from a few different threads to make things easier.
Info came from the following threads:
http://forum.xda-developers.com/showthread.php?t=1803090
http://forum.xda-developers.com/showthread.php?t=1492887
** As always, this has risks. You could brick your device. Do this at your sole discretion. This worked just fine for me, but it might not work for everyone.
** What this does is replace TWRP with the stock recovery, enabling OTA updates to be applied again. It does NOT re-lock your bootloader. It also overwrites your /system image and build.prop with the original .22 image, which should enable the .26 update to be successful.
** This did NOT overwrite any of my settings or apps- that may not always be the case. It's best to expect that this will result in a factory reset, even though in my experience it didn't. Better to be prepared and pleasantly surprised.
** This assumes you installed TWRP or another recovery and need to revert to Stock recovery. Although I'd recommend running the full process anyway, as this ensures you have a fully stock /system partition, build.prop, etc. You can try skipping to step 10 if you're still on stock recovery.
1: Run a TWRP and/or Titanium backup, just in case. Grab everything including recovery if using TWRP.
1a: To be on the safe side, make sure you don't have any other update zips at the root of your external SD or internal storage.
2: Download the appropriate 9.4.5.22 file for your device from here:
3: Extract files from within zip
4: Extract files again from the extracted zip
5: Copy extracted "blob" file to root of folder of the removable Micro SD card or some other folder
6: Through ADB shell or Terminal Emulator, run the following: (May take from 5 to 20 minutes)
Code:
su
dd if=/Removable/MicroSD/blob of=/dev/block/mmcblk0p4
If copying the "blob" file to the SD card in the keyboard dock, use: dd if=/Removable/SD/blob of=/dev/block/mmcblk0p4
If copying it to the internal memory, use: dd if=/sdcard/blob of=/dev/block/mmcblk0p4
7: Reboot only if the following is displayed (exact numbers may be different):
Code:
1068769+1 records in
1068769+1 records out
547210197 bytes transferred in 153.991 secs (3553520 bytes/sec)
Update process will automatically launch
8: Once booted up, root device by using debugfs root here
9: Do not make any other changes to build.prop or the /system directory
10: Download the appropriate dlpkgfile. The US version of the update can be downloaded here. I'll add any others as they are posted.
11: Use root explorer to copy "dlpkgfile" into /cache/ directory. Alternatively you could save the "dlpkgfile" in a microSD then open up a adb shell session.
Code:
su
cat /Removable/MicroSD/dlpkgfile > /cache/dlpkgfile
12: Create the file called "command" under /cache/recovery/ directory.
13: Write this statement in the file /cache/recovery/command
Code:
--update_package=/cache/dlpkgfile
14: Finally reboot into recovery kernel by shutting down first, then press and hold "Volume down" + "Power" once it vibrates release "Power" keep holding "Volume down" until there are some text shown on the boot logo screen. Then press "Volume up" within 5 seconds after releasing "Volume down". The update process should start... wait for it to complete. (This will take a little while, as the dalvik-cache will be rebuilt and your camera firmware will be updated. Once it completes, you should have the updated firmware installed on your tablet
15: Once the update is complete and you're at your home screen, you'll need to re-root. Just follow step 8 again.
16: Once rooted again, you can reinstall TWRP according to the original instructions, or just leave stock recovery on for now to avoid having to do this again once the next OTA comes out.
thanks for taking the risk and trying all this out. i just ran through all the steps and it worked perfectly. (i also had TWRP)
Really stupid question incoming, skip this post if you're in a cranky mood...
How can I tell if I'm running TWRP? I used the unlock tool from Asus then the debugfs root method from another thread in this sub. When I boot into recovery I get a red exclamation point over my surgery table android. It just says something along the lines of Android recovery, so I assume that's stock.
Headcase_Fargone said:
Really stupid question incoming, skip this post if you're in a cranky mood...
How can I tell if I'm running TWRP? I used the unlock tool from Asus then the debugfs root method from another thread in this sub. When I boot into recovery I get a red exclamation point over my surgery table android. It just says something along the lines of Android recovery, so I assume that's stock.
Click to expand...
Click to collapse
Yeah, it sounds like you're on standard recovery, and maybe there's an update file on your SD card or in cache that's failing.
If you follow the OP, it should enable you to update if you haven't yet. It'll pretty much do everything back to default .22 except relocking the bootloader.
Oh, as an afterthought, make sure you don't have any other update zips at the root of your external SD or internal storage, just to be safe.
followed all steps and seems to work. However, in the last step after I created the command file with root explorer, I booted into stock recovery and recovery screen is now just blinking with the Android icon. This does not seem correct! Any suggestions?
rsbuffalo said:
followed all steps and seems to work. However, in the last step after I created the command file with root explorer, I booted into stock recovery and recovery screen is now just blinking with the Android icon. This does not seem correct! Any suggestions?
Click to expand...
Click to collapse
How do you mean blinking? Does the android icon have a red triangle?
i think he may have missed the part where he needs to hit volume up after volume down.
Thanks eoh7678! I did have some update zips at root sdcard that seemed to be causing an issue. I deleted the files and uninstalled busybox. Then I redid the command file. Update was successful!!! About tablet now shows IML74K.US_epad-9.4.5.26-20120720.
Nice work. I was not aware you could go back to stock recovery. I may give this a go. I'm really blown away that somebody hasn't released a flashable zip that is custom stock ready yet.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
newellj79 said:
Nice work. I was not aware you could go back to stock recovery. I may give this a go. I'm really blown away that somebody hasn't released a flashable zip that is custom stock ready yet.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
I actually have one mostly ready to go, according to what I've read, but to be honest, I've only ever made update zips for samsung or HTC phones. I've never tried this whole blob thing. TBH, I'm scared to death to try flashing my own creation.
Thank you for posting the howto (you saved me from having to write my method) I did everything from my TF700 using terminal and remote explorer to get recovery reverted and .26 OTA installed.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
I'm curious about why to root between installing .22 and upgrading to .26? Does the root method not work on .26? If you root before upgrading to .26 does it retain root natively or do you need to use voodoo root keeper?
newellj79 said:
I'm curious about why to root between installing .22 and upgrading to .26? Does the root method not work on .26? If you root before upgrading to .26 does it retain root natively or do you need to use voodoo root keeper?
Click to expand...
Click to collapse
I haven't tried the manual update with this one, as I received it OTA before this one was posted, but it erased my su. Happily RootKeeper preserved it.
newellj79 said:
I'm curious about why to root between installing .22 and upgrading to .26? Does the root method not work on .26? If you root before upgrading to .26 does it retain root natively or do you need to use voodoo root keeper?
Click to expand...
Click to collapse
For me, at least, restoring .22 from the blob removed su. Probably rootkeeper would have solved, but honestly, I figured the safest bet was just to reroot between to make it easier and less prone to problems.
eoh7678 said:
For me, at least, restoring .22 from the blob removed su. Probably rootkeeper would have solved, but honestly, I figured the safest bet was just to reroot between to make it easier and less prone to problems.
Click to expand...
Click to collapse
Kewl. Just curious. Almost done.
Edit... worked great. Thanks!
Having an issue.... Once i move dlpkgfile to cache, make the command file, and reboot to recovery i just get the android with the red triangle. Also once it reboots and i check the cache folder the command file is gone. So at the moment im stuck on 22
Sent from my unlocked and rooted TF700T using the XDA Premium App
cctaylor410 said:
Having an issue.... Once i move dlpkgfile to cache, make the command file, and reboot to recovery i just get the android with the red triangle. Also once it reboots and i check the cache folder the command file is gone. So at the moment im stuck on 22
Sent from my unlocked and rooted TF700T using the XDA Premium App
Click to expand...
Click to collapse
I was having the same problem. My issue was when I downloaded the dlpkgfile a .bin extension was added to the file name. Make sure there is no extension on the filename.
DroidEris1981 said:
I was having the same problem. My issue was when I downloaded the dlpkgfile a .bin extension was added to the file name. Make sure there is no extension on the filename.
Click to expand...
Click to collapse
Im mildly retarded cause the file was 0kb lol. Re-downloading and trying again
EDIT: every copy method i try dlpkgfile ends up as 0kb, not sure what is going on. Using root explorer and terminal fail.
Sent from my unlocked and rooted TF700T using the XDA Premium App
cctaylor410 said:
Im mildly retarded cause the file was 0kb lol. Re-downloading and trying again
EDIT: every copy method i try dlpkgfile ends up as 0kb, not sure what is going on. Using root explorer and terminal fail.
Sent from my unlocked and rooted TF700T using the XDA Premium App
Click to expand...
Click to collapse
I used ES File Explorer (make sure to check the options in settings to tell it you have a rooted phone) to do everything (including creating the file) and it worked great. ES File Explorer is *awesome* - check it out.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Hi,
I'm new here and have read all the horror stories about the VZW OTA updates and would like to block them as I have VRBMB1 and have no issues with it.
It seems that renaming some key files is a good way to do this so - I'm assuming that if in the future I wanted to allow the OTA update I could just rename them back to the original.
That said my phone is not rooted and am trying to use ES File Explorer (version 3) but when I try to rename a file (specifically the one I'm trying is /system/app/FWUpdate.apk it doesn't seem to work. It looks like everything is working fine, but when I hit OK to accept my new name (FWUpdate.apk.bak) it still shows the original name...even after hitting refresh in the file explorer.
Is there something I'm doing wrong that is keeping me from renaming files? The properties of the file do say its readable and writable.
jbsmith_05 said:
Hi,
I'm new here and have read all the horror stories about the VZW OTA updates and would like to block them as I have VRBMB1 and have no issues with it.
It seems that renaming some key files is a good way to do this so - I'm assuming that if in the future I wanted to allow the OTA update I could just rename them back to the original.
That said my phone is not rooted and am trying to use ES File Explorer (version 3) but when I try to rename a file (specifically the one I'm trying is /system/app/FWUpdate.apk it doesn't seem to work. It looks like everything is working fine, but when I hit OK to accept my new name (FWUpdate.apk.bak) it still shows the original name...even after hitting refresh in the file explorer.
Is there something I'm doing wrong that is keeping me from renaming files? The properties of the file do say its readable and writable.
Click to expand...
Click to collapse
The latest VRBMF1 ota is the fix for the previous VRBMD3 ota awhile back, so its all working "fine" now. All the horror stories would be from the VRBMD3 ota which is fixed now. Ahh, well you need to be rooted to make permanent changes to System apps/files. SU grants you access to the entire "/" folder and ability to make permanent changes to system apps as well. Is there any reason you do not want to just root?
Once rooted, all you need to rename is the system app "sdm 1.0." This file will cause your phone to not actively search for OTAs when they are pushed AND you will receive force closes if you try to manually search for an OTA via the Settings option.
SlimSnoopOS said:
The latest VRBMF1 ota is the fix for the previous VRBMD3 ota awhile back, so its all working "fine" now. All the horror stories would be from the VRBMD3 ota which is fixed now. Ahh, well you need to be rooted to make permanent changes to System apps/files. SU grants you access to the entire "/" folder and ability to make permanent changes to system apps as well. Is there any reason you do not want to just root?
Once rooted, all you need to rename is the system app "sdm 1.0." This file will cause your phone to not actively search for OTAs when they are pushed AND you will receive force closes if you try to manually search for an OTA via the Settings option.
Click to expand...
Click to collapse
Well the only reason I'd root would be to prevent the OTA update....instead of just deferring it until they force me.
I've not rooted because i'm really new here and only have Mac's at home so am trying to find the holy grail of instructions for how to root so I don't mess anything up....
jbsmith_05 said:
Well the only reason I'd root would be to prevent the OTA update....instead of just deferring it until they force me.
I've not rooted because i'm really new here and only have Mac's at home so am trying to find the holy grail of instructions for how to root so I don't mess anything up....
Click to expand...
Click to collapse
I've been rooted on this phone for nearly a year and there's very little support for Macs if you run into issues and need to return to stock software. If you have any access to a Windows machine, basically every tool here runs on Windows. Most recently, I rooted using Beanstown106's Casual 1 click tool in the dev section. Its the first stickied thread in that section and it works for Windows and Mac. It worked for me on ML 10.8.4 on my MBP.
As far as any issues that could occur after rooting, if all you want to do is root and that's it then you should not run into issues that require you to revert to stock. Odin is the preferred method for returning to stock but its Windows only. Heimdall (v1.40 was just released) is supposed to be the Mac equivalent to Odin however anyone who ever asks about how to get it working gets no response. So, Odin and Windows are quite frankly the most common terms when fixing this phone. Alternatively, mobile Odin in the Play Store is the suggested method if you have no Windows access or a broken usb port on the phone.
SlimSnoopOS said:
I've been rooted on this phone for nearly a year and there's very little support for Macs if you run into issues and need to return to stock software. If you have any access to a Windows machine, basically every tool here runs on Windows. Most recently, I rooted using Beanstown106's Casual 1 click tool in the dev section. Its the first stickied thread in that section and it works for Windows and Mac. It worked for me on ML 10.8.4 on my MBP.
As far as any issues that could occur after rooting, if all you want to do is root and that's it then you should not run into issues that require you to revert to stock. Odin is the preferred method for returning to stock but its Windows only. Heimdall (v1.40 was just released) is supposed to be the Mac equivalent to Odin however anyone who ever asks about how to get it working gets no response. So, Odin and Windows are quite frankly the most common terms when fixing this phone. Alternatively, mobile Odin in the Play Store is the suggested method if you have no Windows access or a broken usb port on the phone.
Click to expand...
Click to collapse
Given the Mac situation it sounds like I should probably just let MF1 go through...although I'll probably defer it a few more times. About how long does verizon give before they force it on you?
jbsmith_05 said:
Given the Mac situation it sounds like I should probably just let MF1 go through...although I'll probably defer it a few more times. About how long does verizon give before they force it on you?
Click to expand...
Click to collapse
It could push anytime actually and idk how many times you can defer it. The OTA will auto-install if you happen to not be paying attention though.