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
Related
Hi,
It's my first Android tablet... so pls be gentle.
I got the Transformer last night and I rooted it based on the guide :
[GUIDE] ROOT for ASUS eee pad transformer (TF101)
http://forum.xda-developers.com/showthread.php?t=1035197
I got it working with BLOB_V5.
But I just found out my back camera is not working (front working fine)
I think the reason is my Build number HRI66.US_epad-8.2.2.6.1-20110325.
I didnt update to the latest one which is 8329.
So, I would like to know how can I update it to 8329?
I tried just put the zip file in and ran it, then it reboots and goes into the CWM Recovery. And seems like it wont allow me to update...
So, my guess is to remove CWM and unroot it.
BUt how can I get back to the stock?
It's my first time rooting... so I am not sure what should I do next...
Thanks in advance
Bump
10 characters
I believe you have to download the official update off the asus site push the blob included in the update and run the dd command using the asus blob instead of the cwm blob
Also the easiest way to fix the camera is to just flash a rom (prime or titx) my camera and bluetooth were shot after i rooted. Flashing prime fixed and is running great
lordgodgeneral said:
I believe you have to download the official update off the asus site push the blob included in the update and run the dd command using the asus blob instead of the cwm blob
Click to expand...
Click to collapse
^This and I just did it.
Sent from my HTC Eva 4G using Tapatalk
toni8284 said:
Hi,
It's my first Android tablet... so pls be gentle.
I got the Transformer last night and I rooted it based on the guide :
[GUIDE] ROOT for ASUS eee pad transformer (TF101)
http://forum.xda-developers.com/showthread.php?t=1035197
I got it working with BLOB_V5.
But I just found out my back camera is not working (front working fine)
I think the reason is my Build number HRI66.US_epad-8.2.2.6.1-20110325.
I didnt update to the latest one which is 8329.
So, I would like to know how can I update it to 8329?
I tried just put the zip file in and ran it, then it reboots and goes into the CWM Recovery. And seems like it wont allow me to update...
So, my guess is to remove CWM and unroot it.
BUt how can I get back to the stock?
It's my first time rooting... so I am not sure what should I do next...
Thanks in advance
Click to expand...
Click to collapse
hmm... Maybe, you can try reset to default of TF101 as following step.
settings -> Privacy -> personal data -> factory data reset
Just to be clear...
lordgodgeneral said:
I believe you have to download the official update off the asus site push the blob included in the update and run the dd command using the asus blob instead of the cwm blob
Also the easiest way to fix the camera is to just flash a rom (prime or titx) my camera and bluetooth were shot after i rooted. Flashing prime fixed and is running great
Click to expand...
Click to collapse
I just want to be clear before I attempt to unroot. If I understand the above post correctly, I would modify the instructions to read:
Code:
Return to the shell from step 6 and do the following commands:
11. run “dd if=/data/local/blob of=/dev/block/mmcblk0p4″
12. reboot the device, on reboot you should see a progress bar indicating the flashing of the “blob”
That is, of course, after downloading the zip from Asus and unzipping it to get to the actual blob named "blob" and pushing that to /data/local with adb. Am I correct? And someone has done this successfully? I just want to be 100% clear.
Buee said:
I just want to be clear before I attempt to unroot. If I understand the above post correctly, I would modify the instructions to read:
Code:
Return to the shell from step 6 and do the following commands:
11. run “dd if=/data/local/blob of=/dev/block/mmcblk0p4″
12. reboot the device, on reboot you should see a progress bar indicating the flashing of the “blob”
That is, of course, after downloading the zip from Asus and unzipping it to get to the actual blob named "blob" and pushing that to /data/local with adb. Am I correct? And someone has done this successfully? I just don't want to be 100% clear.
Click to expand...
Click to collapse
Yup. That's exactly what you do.
seshmaru said:
Yup. That's exactly what you do.
Click to expand...
Click to collapse
I purchased a previously rooted transformer and wish to unroot it. This is my first android device so I have read up and done my homework and now I believe I am ready to un root the device. These questions may be redundant, but all I have to do is push the blob from the most recent asus firmware update to the transformer, and then run it as outlined in step 11? Or do I have to follow steps 6 through 11 to a T in order for it to un root properly. I am fairly sure I can disregard the steps 1-5, correct? I just need a little (lot) of clarification since I am an Android virgin so to say.
edit: deleted because it's not working
followed it to a tee and it is boot looping now what?????/
Oh No!
fullthrottleenergy said:
Yup. First thing is download the asus firmware and extract the blob and then push it to data/local
7. run “adb push blob /data/local”
This takes about 5-10 minutes as it's a pretty big file.
Once that's complete type in adb shell and you should be in root (#). then just type or copy and paste from below and reboot.
11. run “″
flashing of the “blob”
Optional but I did it. After it reboots I reset it to factory (in settings). Then I copied the Asus folder (newest firmware) and placed it on my microsd card and let it do its thing. Remember to back up anything on the internal memory as it's going to get wiped when you do a factory reset.
Click to expand...
Click to collapse
I pushed the blob with no problem then typed "adb shell" to get to root and copied and pasted "dd if=/data/local/blob of=/dev/block/mmcblk0p4" and pressed enter. Upon reboot, I saw the progress bar fill up and then the Transformer rebooted. Now it is in a continual loop where it restarts (and my windows xp recognizes it), makes a click noise, shows the EEE Pad with the ASUS below start up screen, then after about ten seconds restarts to the home screen all over again. If i try to start in recovery mode it attempts it enter it, then I get the triangle with the exclamation point in it next to the android logo. I seriously think I'm fuc*ed. I knew I shouldn't have tried this. AND I REALLY NEED HELP! please I'm begging anyone. I've only had the thing for a week!
this is how I fixed mine.
same issue.
put on your micro sd card in the root of the card the update normally found in the asus/update/ folder you download from asus. I used the .9 us update worked fine, you must then rename it to EP101_SDUPDATE make sure you leave it a zip dont change the extension make sure it is on the root of the card.
then put your card in your transformer, hold the down volume and power till it prompts you in the upper left let go and push down on the volume again, which will load the factory recovery and will begin to flash the update do not bother it. it will restart and your good.
For anyone else that wants to unroot, the step mentioned previously work, I've done it myself and my Transformer no longer has root or CWM and it kept all of my information intact. You just download the firmware from Asus, extract to the point that you get a large file (mine was ~500MB) named 'blob', push that to your SD card, run the dd command swapping out the name of the file. My dd command if section looked like this "if=/sdcard/blob" and change nothing else of that command, reboot and it'll do its thing. Not sure about the bootloops. That is the ONLY command I modified and issued, nothing else from the tutorial, just that command.
2nd update today! 4th Jan
Thanks to GLS9 and Baseballfanz for the info. It seems we have a universal root. 'Nachoroot'.
Check it out here if you were left stuck with the other methods. http://forum.xda-developers.com/showthread.php?t=1427838
Mangraa posted this. Hopefully it will help those who have been stuck so far. 4th Jan 2012
- Get Razorclaw and install it, no root needed.
- Get the recovery installer and do the same.
- Check your version info. You'll see a pair of letter which are like the "WW", "UK", "US" pairs in the various update files. It appears, at least when I was trying to do this, that you cannot use unmatched pairs (I don't know about the "WW" one, since I started with US and (accidentally) went to .13 US version).
- Follow the instructions regarding downloading the .13 update (WW version and/or whatever letter pair your tablet uses, in case the WW doesn't work). Unzip, slap on external SD, power off, power on with down volume, volume up to go to recovery, bang. Done.
- Do the same thing with the megaupload file (.19). The second option did fix the problem I had, which was trying to update to a WW.19 firmware from a US.13 - DO THE DOUBLE FILE/RENAME TRICK. It works perfectly.
- Run razorclaw, run recovery installer, and gloat.
Seriously, now knowing how the paired-letters-not-compatible-with-other-letters thing works, the whole process would take maybe 10-15 minutes tops. Thanks for the post!
update. Success does seem to vary and some people have managed to make this work with a different SD and other variations. If my method or Trip's doesn't work for you have a look at some of the tweaks that other guys have used. If you did something different and it works let us know. Thanks.
I have a UK transformer and I lost root after the OTA 8.6.5.21 update. Yes, should have checked before applying.
Wasn't able to root with NVFlash so I downloaded http://www.multiupload.com/X65RBVD2MB the 8.6.6.19 file that was posted by Lizard here http://forum.xda-developers.com/showthread.php?t=1393953&page=3
I unzipped it until I had the WW_epad-user-8.6.6.19.zip file. I placed this on the root directory of the external SD card and when I rebooted it gave me the option to install.
This installed OK so I just re-ran Razorclaw and sorted. I have superuser back.
Warnings and all. This would seem to be the US update but is working fine on my UK B70 (presumably SBK2 pad). I've installed CWM and backed up too. No promises that this won't destroy your pad/steal your gal or boy/shoot your dog.
Card formatting?
Originally Posted by elek_it
For all the people having problem:I was on b80 .21, and tried both methods with no success. Always the green android with yellow exclamation mark.Then, I noticed that when copying files to the sd from windows, it always asked for "permissions". That was formatted with NTFS.Tried another microSD in FAT32, just copied the WW_epad-user-8.6.6.19.zip file and VOILA', all worked flawlessy (method 1).
Step by step
1) Download http://www.multiupload.com/X65RBVD2MB
2) Unzip so you have just have WW_epad-user-8.6.6.19.zip. Keep this zipped and copy to root of external micro SD.
3) Reboot with card in place, don't enter recovery.
4) When it booted back into the OS I had a triangle in the notification bar. I clicked this and it offered to install the update.
5) After tab updated as usual I just re-ran Razorclaw and I had root back.
Update. trippmcnealy had success with a tweak to this. If it doesn't work you might want to follow his method.
1) Download http://www.multiupload.com/X65RBVD2MB
2) Unzip so you have just have "WW_epad-user-8.6.6.19.zip". Keep this zipped and copy to root of external SD.
3) Put another copy of the same file on your external SD card and name it "EP101_SDUPDATE.zip"
4) Put both files "EP101_SDUPDATE.zip" and "WW_epad-user-8.6.6.19.zip" on the root of your internal SD card.
5) Power down your TF
6) Power up into recovery - by pressing the power button and volume down button. Then press volume up when instructed by the screen.
7) You should now see the Android guy with some gears turning. This is good, actually this is GREAT! This will go on for a minute or so and then the device will reboot on its own. It will then go to the boot screen and you should see a bar showing you the progress of the update.
8) Once it has completed, install RazorClaw and root your device.
Tips from Baseballfanz
For those not able to get it working, a few things to check.
1-Make sure you actually extract the WW_epad-user-8.6.6.19.zip within the zip. Inside the file you download is an Asus folder, inside that is an Update folder, inside that is the WW_epad-user-8.6.6.19.zip file you'll be working with.
2-When renaming, if your PC is set to "hide known extension", you'll not see the .zip so if you type in .zip you'll get filename.zip.zip The file manager on the TF should show you the extension
3-Make sure it's on the root of the sd card and not within any folder.
4-Check spelling of files
WW_epad-user-8.6.6.19.zip EP101_SDUPATED.zip
5-Micro sd card is in FAT32 format. Try a different card or format again (after saving your stuffs)
6-File manager on the TF sdcard is internal and Removable/MicroSD is the external sd card.
Suggestions
It would be useful for people to report info with posts about success or not. What SBK, serial number (B70 etc) and current firmware are you on? I'm no dev but hopefully we can make things easier for others.
Resources
Razorclaw
http://forum.xda-developers.com/showthread.php?t=1346180 Gnufabio's recovery installer, suggested by Baseballfanz
Reboot to Recovery Makes it easier to enter recovery after installing CWM.
Please let me know if any info is missing and I'll update.
Ah, this seems interesting! I also have a uk transformer and will give it a go.
So you don't need anything else but stock? I will try this now, and does it wipe your data? Used asus backup just in case.
Cool
Hi,
thanks for the info. As far as I know the WW-version is not US only, but should match the version you have (you can check that in the settings/about tablet).
As far as I know WW stands for WorldWide and actually means US and (most of) Europe. There are special versions for Taiwan, Germany and Canada though...
I will try this later with my transformer (bought in switzerland) - i should work!
Regards, Thomas
Yeah I was thinking that. It comes with all the country files anyway.
I tried this a couple of days ago and it didn't work, turns out I unzipped the wrong file.
Unzip the .19 update to the root of your sdcard and reboot the transformer if it doesn't detect the update.
Now I haz root.
whitekidney said:
I tried this a couple of days ago and it didn't work, turns out I unzipped the wrong file.
Unzip the .19 update to the root of your sdcard and reboot the transformer if it doesn't detect the update.
Now I haz root.
Click to expand...
Click to collapse
So external or internal? And just reboot or recovery? Vol down+power then vol up? Thanks, sorry for the questions!
Hi there,
I unzipped to external and rebooted with the card in place. I didn't use recovery. The OS detected the update and offered to install. Just proceeded from there.
I mentioned the US update as the file is 8.6.6.19 not 8.6.5.19
Good luck.
I'm still getting the dreaded triangle when trying this fix, any suggestions?
Hi Samuel
Can you talk us through what you did and your setup? I'm no expert but hopefully we can find out what's awry.
Nice 1 m8. Do yo think this will work with B40 model? Where in leeds are you from? I in pudsey.
Should this work with the TF101G (B90 / DE / 8.6.6.10) too?
Gesendet von meinem HTC Desire mit Tapatalk
pjfriend said:
Hi there,
I unzipped to external and rebooted with the card in place. I didn't use recovery. The OS detected the update and offered to install. Just proceeded from there.
I mentioned the US update as the file is 8.6.6.19 not 8.6.5.19
Good luck.
Click to expand...
Click to collapse
But is it ok/safe? Guessing it is. Just popped up saying there is an update for me as well, going to give it a go now.
The honeycomb upgrading 'droid is so cool! I think its working fine!
If anyone could make a Uk one, that would be great. I am thinking the reason why this is working is because of the increase in firmware numbers, from x.x.5 to x.x.6.
Hi Seg2012
Only tried on mine until others can update to say it worked. You should be able to root with NVFlash though.
I'm from Morley but live nearer to Dewsbury now. Small world!
Going to flash this to my B90 US tablet, will report back-
This is great, worked perfectly! Now onto a custom rom! Revolver I think!
First off I downloaded the WW_epad-user-8.6.6.19.zip file. I placed this on the root directory of the micro SD card. Secondly I reboot my new baby using the power button and the down rocker of the volume button.I then pressed the up rocker to get into the recovery mode, now I only then get the green android with the yellow triangle with exclamation. My Asus tf is HTK7.WW.EPAD-8.6.521-20111216 any help would most appreciated.
I didn't use recovery. Just rebooted and the tab detected it. I clicked the triangle in the bar, it offered to update and went from there.
Sent from my GT-I9100 using xda premium
I didn't even need to reboot!
If you clear up the op with slightly clearer instructions this is sticky worthy. Helpful!
pjfriend said:
I didn't use recovery. Just rebooted and the tab detected it. I clicked the triangle in the bar, it offered to update and went from there.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Not working here, I've an italian TF101g updated w/ 8.8.6.23, I've unzipeed the 8.6.6.19 firmware to the root of my microSD but I've got any update notification
pjfriend said:
Hi Seg2012
Only tried on mine until others can update to say it worked. You should be able to root with NVFlash though.
I'm from Morley but live nearer to Dewsbury now. Small world!
Click to expand...
Click to collapse
Cheers anyway m8. Ill give it a go shortly and post back.
Yeah it is a very small world. Lol
Seg
Here are the files and instructions to get root and CWM on a Samsung Conquer 4G with the FC17 update. To enter Download Mode on the phone, make sure the phone is turned off and plugged into the wall charging. You should also make sure the phone has a good charge on it. Then turn the phone on by pressing the volume down and camera button and holding them while pressing the power button for a few seconds.
Here are the files you will need -
CONQUER-ROOT.zip
Unzip all the files on your computer and follow these steps.
1) Enter download mode on the phone and plug it into your computer. Open up the Odin program. Then press the OPS button and select the SPH-D600_FC17_CWM.ops file. Then press the PDA button and select the SPH-D600_FC17_CWM.tar.md5 file. The press the Start button, the images should install and the phone reboot. Congrats, your phone now has a stock FC17 image with a CWM Recovery.
2) Next, copy the Superuser-3.0.7-efghi-signed.zip and su-bin-3.0.3.2-efghi-signed.zip files to the root of your SD Card after booting up.
3) Once the phone boots up, go into settings, select Applications, then Development, then turn on USB debugging. Now you can restart the phone into recovery mode with adb. If you don't want to use adb, you can plug the phone into the wall and turn it on while holding the volume down and power button. Either way is fine, as long as you now get the phone into recovery mode.
4) The phone should now go into CWM recovery. Go to install zip from sdcard and select the Superuser-3.0.7-efghi-signed.zip file you put on the sdcard and install that. Next select the su-bin-3.0.3.2-efghi-signed.zip file from your sdcard and install that.
5) Congratulations, you now have a rooted phone with the FC17 update. If you had CWM installed before, you can now do an advanced back-up, and just restore the data from your most recent backup and get all your data back.
I've created a new custom ROM here - http://forum.xda-developers.com/showthread.php?p=29369141
You can just download the new files and follow those instructions if you haven't installed this yet.
it work like charm thank you very much sir very good job done..........
---------- Post added at 04:47 AM ---------- Previous post was at 04:38 AM ----------
there is any custom rom kool one ...
I know on the E4GT, sfhub is able to make tar's that do not wipe user data. The file difference between the 2 images are
removed: boot.bin, sbl.bin, param.lfs, cache.img, data.img
intact: recovery.bin, hidden.img, factoryfs.img(largest file) modem.bin and zImage(contains the kernel)
The Question I'm posing to you is which of the files in the conquer tar.md5 might be the counterparts to the above files, making them the ones to strip out in order to make it not wipe data?
My wife never wanted me to root her phone until recently, so no cwm backup that's pre-OTA, and there are some apps that don't work when re-installed (a security key-gen app)
Any help would be much appreciated.
AestenD said:
I know on the E4GT, sfhub is able to make tar's that do not wipe user data. The file difference between the 2 images are
removed: boot.bin, sbl.bin, param.lfs, cache.img, data.img
intact: recovery.bin, hidden.img, factoryfs.img(largest file) modem.bin and zImage(contains the kernel)
The Question I'm posing to you is which of the files in the conquer tar.md5 might be the counterparts to the above files, making them the ones to strip out in order to make it not wipe data?
My wife never wanted me to root her phone until recently, so no cwm backup that's pre-OTA, and there are some apps that don't work when re-installed (a security key-gen app)
Any help would be much appreciated.
Click to expand...
Click to collapse
Take out userdata.yaffs to retain your data, BUT you will have to rebuild the tar file and remake the OPS file by removing the line that reads -
Code:
9,userdata
If you need the Linux commands to rebuild the image, let me know.
brienj said:
Take out userdata.yaffs to retain your data, BUT you will have to rebuild the tar file and remake the OPS file by removing the line that reads -
Code:
9,userdata
If you need the Linux commands to rebuild the image, let me know.
Click to expand...
Click to collapse
Crap, and me with no Linux box lol
I'll figure something out, I have a live CD around here somewhere.
AestenD said:
Crap, and me with no Linux box lol
I'll figure something out, I have a live CD around here somewhere.
Click to expand...
Click to collapse
Just install Cygwin and use that and then extract all the files out of the .md5 file, it's just a regular tar file with md5 sums in it. WinZip, WinRAR, etc. will easily extract the files from it. Then use these commands to rebuild the image without the userdata.yaffs file.
tar -H ustar -c adsp.mbn amss.mbn appsboot.mbn boot.img cache.yaffs mibib osbl recovery.img system.yaffs > package_name.tar
md5sum -t package_name.tar >> package_name.tar
mv package_name.tar package_name.tar.md5
Click to expand...
Click to collapse
You can replace each package_name with whatever you want it called.
brienj said:
Just install Cygwin and use that and then extract all the files out of the .md5 file, it's just a regular tar file with md5 sums in it. WinZip, WinRAR, etc. will easily extract the files from it. Then use these commands to rebuild the image without the userdata.yaffs file.
You can replace each package_name with whatever you want it called.
Click to expand...
Click to collapse
Thanks for your help, took me a bit, because I mistakenly flashed the non-CWM image first, and the bootloader version just wasn't letting me in. Luckily I have a jig for my SGS2, and I'm up and running now. Hopefully just the fact that it's the full image, rather than OTA upgraded will fix some of the issues she's been having. If not, then having root gives me so many more troubleshooting options.
give me an error says the SPH-D600_FC17_CWM.tar.md5 is invalid image type please help
sromero619 said:
give me an error says the SPH-D600_FC17_CWM.tar.md5 is invalid image type please help
Click to expand...
Click to collapse
"known issue" just keep going, it'll work just fine.
Sent from my SPH-D710 using Tapatalk
sromero619 said:
give me an error says the SPH-D600_FC17_CWM.tar.md5 is invalid image type please help
Click to expand...
Click to collapse
It says this, even with an official Sprint Odin image. It will still work, like AestenD mentioned.
i did all the step but when i hit start on the odin it says please connect phones what can else can i do. loaded the drive from super one click because my laptop running windows seven wasn't reading my phone. Its reading my phone I downloaded the usb driver from this link http://r2doesinc.bitsurge.net/leaked/
now when i run odin now it say """an unnamed file was not found""" whats to do please help
brienj said:
It says this, even with an official Sprint Odin image. It will still work, like AestenD mentioned.
Click to expand...
Click to collapse
i got the phone to be read but now when i hit the start button a window pops out says "unnamed file is not found"
It worked for me.
Question
I have been reading up on this phone since I ordered it from my new provider. I should get the phone sometime later today and wanted to get everything ready to root it as soon as I get it. I've read JWhip804's tutorial on how to root the Conquer. I've also been keeping up with chrystal0925's efforts at making a working themed ROM.
My question is, if I want to have a recovery of my stock phone just in case I have to send it back to my carrier, should I use the method described in this thread or use JWhip804's thread?
I have a brand new Samsung Conquer SPHD600BKS on the Sprint network using a new provider to my area called Ting.
Android Version: 2.3.4
Baseband Version: S: D600.12 x.EG15
Kernel Version: 2.6.35.7-perf
Build Number: GINGERBREAD.EG15
Hardware Version: D600.12
Thanks.
roofus1812 said:
I have been reading up on this phone since I ordered it from my new provider. I should get the phone sometime later today and wanted to get everything ready to root it as soon as I get it. I've read JWhip804's tutorial on how to root the Conquer. I've also been keeping up with chrystal0925's efforts at making a working themed ROM.
My question is, if I want to have a recovery of my stock phone just in case I have to send it back to my carrier, should I use the method described in this thread or use JWhip804's thread?
I have a brand new Samsung Conquer SPHD600BKS on the Sprint network using a new provider to my area called Ting.
Android Version: 2.3.4
Baseband Version: S: D600.12 x.EG15
Kernel Version: 2.6.35.7-perf
Build Number: GINGERBREAD.EG15
Hardware Version: D600.12
Thanks.
Click to expand...
Click to collapse
Super-One-Click only works on EC15, and you can not do an OTA update to FC17 with root, and once you do update to FC17, Super-One-Click will no longer work to root your phone, so you must use the method I have made in this thread, or a similar one to it. You MUST get a stock FC17 image with the CWM recovery to push root onto your phone, as the OTA update has recovery updating scripts, etc. in it, and it's just easier to use the FC17 image and not bother with making the OTA able to be rooted. In order to get the phone back to a stock image, you can easily find the stock Odin image that is floating around, or change the recovery image in the Odin file I have in this thread, with a stock recovery image.
Finished
brienj said:
Super-One-Click only works on EC15, and you can not do an OTA update to FC17 with root, and once you do update to FC17, Super-One-Click will no longer work to root your phone, so you must use the method I have made in this thread, or a similar one to it. You MUST get a stock FC17 image with the CWM recovery to push root onto your phone, as the OTA update has recovery updating scripts, etc. in it, and it's just easier to use the FC17 image and not bother with making the OTA able to be rooted. In order to get the phone back to a stock image, you can easily find the stock Odin image that is floating around, or change the recovery image in the Odin file I have in this thread, with a stock recovery image.
Click to expand...
Click to collapse
I just finished backing up my Conquer using this guide. It was really easy. Thanks.
Hi guys. Anyone use tethering with this? I had tethering working on the old rom fine and another unrooted phone with the ota update. I got a replacement phone and tethering does not work. It only works for google sites - with any tethering app i tried. Is it the hardware or maybe its the stock fc17? I tried reflashing and clearing everything and the problem persists.
I tried using Odin today to root my Samsung Conquer and had a bit of trouble. When I attached the .tar file it gave me an error but as I read this thread I just kept going as if there was no issue. About half way through the Odin installation my phone just rebooted, I tried again and it rebooted it the same spot. I tried putting my phone back into download mode and continue the process, which it did, and I got a "Pass" message at the end. But I don't have CWM and I'm almost positive its still not rooted. Any suggestions?
Any chance of an update with the new OTA included?
Sent from my SPH-D710 using xda premium
There is a new ota fe17. Does anyone know if it will break root? Will it install?
Sent from my SPH-D600 using XDA
Make sure you are using CWM version 6.0.1.0
I am not responsible for whatever happens to your device because everyone else puts this in their threads too! get over it
Be sure to click that Thanks button if this helped you. this also appears in everyone else's thread's! deal with it
1. download the update file for your region from paugustin's thread here:
http://forum.xda-developers.com/showthread.php?t=1720157
2. unzip it inside any folder.
3. open the file called updater-script which is located at:
/META-INF/com/google/android
4. delete the line and the blank space left afterwards then save changes to the file. the line for the US version looks like this:
assert(getprop("ro.product.name") == "a700_pa_cus1");
5. highlight everything that came out of the download from step 1, zip it, and rename it to update.zip
6. place in the root of an SD card, not internal storage!
Note: a few users have recommended placing the update.zip on internal storage. i tried it again from a SD card and it worked just fine. if you're having issues with this try internal.
7. reboot to recovery mode. if you need this guide you've had to do it in the past, nuff said! :silly:
8. select Apply update.zip
9. after you select Reboot System, you will be given two options:
Yes will keep CWM recovery but you wont be able to use recovery mode at all until you unlock the bootloader again!
No will allow the update to restore stock recovery, and you will need to re-flash CWM.
10. if you chose Yes from step 9, unlock your bootloader and do the root process again. DONE!
if you chose No, unlock your bootloader, flash CWM again, and do the root process again. DONE!
there are already guides on how to do that.
BONUS FOR USA TAB OWNERS!
This is ONLY FOR UPDATING FROM the Acer_A700_AV043.RV00RC00_AV043.RV07RC06_PA_CUS1.zip file from the link in Step 1 at the top of the page.
If you are on any other version, and / or from any other country, DO NOT TRY THIS!
This is the latest update with the power option added in settings & touch sensitivity improvements, with the getprop line already deleted from the script!
A. Download this directly to your tab.
B. Reboot to recovery mode.
C. Install.
D. After selecting Reboot System you will be given two options. Refer to Step 9 above.
E. After making your choice, you will be given the option to prevent the update from deleting root :victory:
F. Unlock your bootloader again.
G. If you chose No. from Step 9, re-flash CWM 6.0.1.0
H. If you chose No. from Step E, root again if you wish.
DONE!!
I've try this, but when I do point 8 (select Apply update.zip), the update is aborded.
I'm on SDs_Acer_AV043_A700_RV07RC06_EMEA_FR.zip with the root by patched boot.
I want install Acer_A700_AV043.RV07RC06_AV043.RV23RC04_EMEA_FR.zip.
I don't know why update fail.
imtheyoyo said:
I've try this, but when I do point 8 (select Apply update.zip), the update is aborded.
I'm on SDs_Acer_AV043_A700_RV07RC06_EMEA_FR.zip with the root by patched boot.
I want install Acer_A700_AV043.RV07RC06_AV043.RV23RC04_EMEA_FR.zip.
I don't know why update fail.
Click to expand...
Click to collapse
i think i know why.
i revised step 5, check it out
That's what I had done, zip and rename in update.zip.
imtheyoyo said:
That's what I had done, zip and rename in update.zip.
Click to expand...
Click to collapse
hmm... did you put it on an sd card?
and what error is it giving you?
Sterist said:
hmm... did you put it on an sd card?
and what error is it giving you?
Click to expand...
Click to collapse
Yes, and the message was "Update aborted"
Just a question. I have unlocked my A700 via method 2, so without CWM install.
If I follow this guide, placing the update.zip on the card, and restart with Volume-down+Power, will it execute the update.zip as well?
The update.zip in fact is the altered Acer_A700_AV043.RV07RC04_AV043.RV23RC05_WW_GEN1.zip according to the instructions.
If using Root Explorer, where would I have to place the update.zip file?
---------- Post added at 10:57 PM ---------- Previous post was at 10:52 PM ----------
CheopsChefren said:
Just a question. I have unlocked my A700 via method 2, so without CWM install.
If I follow this guide, placing the update.zip on the card, and restart with Volume-down+Power, will it execute the update.zip as well?
The update.zip in fact is the altered Acer_A700_AV043.RV07RC04_AV043.RV23RC05_WW_GEN1.zip according to the instructions.
If using Root Explorer, where would I have to place the update.zip file?
Click to expand...
Click to collapse
Thanks for any advice.
CheopsChefren said:
Just a question. I have unlocked my A700 via method 2, so without CWM install.
If I follow this guide, placing the update.zip on the card, and restart with Volume-down+Power, will it execute the update.zip as well?
The update.zip in fact is the altered Acer_A700_AV043.RV07RC04_AV043.RV23RC05_WW_GEN1.zip according to the instructions.
If using Root Explorer, where would I have to place the update.zip file?
Click to expand...
Click to collapse
I'm not sure if a modified update script would run on the stock recovery. you can try it, the worst that would happen is it will decline to run the update. i would recommend you always have CWM recovery regardless of any flashing/updating plans you may or may not have.
and the location for the update.zip does not change regardless of what you use to get the file there lol it doesn't matter if you use a Toyota or Lamborghini to get to work. silly question lol..
Thanks for your answer. The problem is, an unmodified update script wont run either on my unlocked A700.
And, I am scared about using CWM, as I hear stories it will possibly brick your A700, and that is something I am not too keen about.
But, with Root Explorer compared to ES File Explorer you have more possibilities. But I agree, it was abit a silly question.
So now, how to update my unlocked A700 with the OTA delivered by Acer? That's the question.....
CheopsChefren said:
Thanks for your answer. The problem is, an unmodified update script wont run either on my unlocked A700.
And, I am scared about using CWM, as I hear stories it will possibly brick your A700, and that is something I am not too keen about.
But, with Root Explorer compared to ES File Explorer you have more possibilities. But I agree, it was abit a silly question.
So now, how to update my unlocked A700 with the OTA delivered by Acer? That's the question.....
Click to expand...
Click to collapse
by my understanding, the CWM versions to avoid are 5.4.0.0 (something like that) and the touch version(s)
unlocking your bootloader and not installing CWM is like alcohol-free-beer... pointless.
When trying the above mentioned procedure, i first got an error 6, which i solved by editing the updater-script the second time with notepad++, so i could keep the unix-like line-ends.
Then when i tried to run the update.zip from within cwm, i got error status 7.
(On both the downloaded update file from the thread mentioned above, and from the original from Acer received OTA update file)
As far as i know, after googling error status 7 has to do with the update zip not for the system trying to update. But i am sure, as i also tried with the Acer received OTA (after deleting the first line in the updater-script), i used the correct update file.
What could cause this?
Hi. Link for U.S. tab owners (www.sendspace.com) is dead. Can you post again?
eman01 said:
Hi. Link for U.S. tab owners (www.sendspace.com) is dead. Can you post again?
Click to expand...
Click to collapse
LOL stupid mistake on my part
the link wasn't really dead, i just screwed up in how i posting it lol thanks for mentioningit
Got it. Thanks.
OK. I finally tried above method to update rooted U.S. A700.
Started with:
Image Acer_AV043_A700_RV07RC06_PA_CUS1
Build Acer_AV043_A700_1.029.00_PA_CUS1
CWM Recovery 6.0.1.1
I tried both methods above- initially using the update.zip specifically provided for U.S. A700 owners in the 2nd part of 1st post of this thread
IN "BONUS FOR USA TAB OWNERS!".
Tried it on 1st external SD, then internal SD.
Both ways I get RED TRIANGLE with exclamation point and message:
"Can't open /sdcard/update.zip
(bad)"
OR
"Can't open /emmc/update.zip
(bad)"
I am, of course, sure I copied the update.zip directly from Downloads to the root of the external and internal cards;
I also made sure to use "Choose zip from SD card" in CWM to find the Update.zip file right where I put it.
Not ready to quit, I tried again using the original Update zip file and modifying updater.script myself, exactly as described in the 1st part of the 1st post. I also tried this update.zip with modified updater.script on both the external and internal SD, without success.
This time I did get further, receiving:
Finding update package...
Opening update package...
Installing update...
Mount Data success
Verifying current system...
assert failed: apply_patch_check_("EMMC:\dev\block\platform\sdhci-tegra.3/by-name/LNX:4065536:95
Then a bunch of letters/numbers
E:Error in sdcard/update.zip
(Status 7)
Installation aborted.
P.S. I verified I have the assert line deleted in the updater.script before I tried this.
I should mention that I have stock ROM, have and have NOT deleted any system apps
(I have inactivated a few like VirusScan within Android).
Luckily I was able to reboot without any problems after all these attempts, but now I am stuck.
Any ideas?
hmmm that's an error i haven't seen before. try deleting the update and downloading it again, or disabling assert check
I'm not a developer, that's the best i can suggest. you'd have to ask someone with a bit more knowledge
it might have something to do with the root method you used originally
Well, I tried yIur modified update.zip multiple times (downloaded it 3 different times, and tried both internal and external SD). As mentioned, I also tried modifying the updater.script myself (used JOTA text editor; maybe that was an issue with respect to how it saves a file, etc.).
How does one disable assert check, as you describe? A link, perhaps?
Interestingly, today I was able to flash the original1.029 update (1st A700 OTA update) after modifying it's updater.script in exactly the same fashion you describe. It put me back to stock 1.029, which I then updated to stock 1.057 (2nd A700 OTA update). I then re-unlocked bootloader, re-rooted and re-installed CWM recovery 6.0.1.1 easily and successfully as described in the threads in A700 development in this forum. Still holding out on CM ROM, as it seems fairly buggy. Thanks for trying. My way definitely took longer; don't know why your direct method would not work on my tab. Thanks.
disable asset check should be one of about 4 or 5 options to choose from, right next to ''choose from internal'' / external
it actually might not be available on this device it's been a while since I've used CWM
i do these modifications right from my tab with ES file explorer.
glad you were able to get it working
[solved] US A700 rooted OTA update
hi all,
after few days of messing about I finally managed to update a rooted US A700. I will try to guide you through what I did.
After initially booting up the A700 I upgraded it OTA to AV043_A700_RV07RC06_PA_CUS1 and after that rooted it using method #2 in the rooting thread (method #1 didn't work for some reason)
Got OTA notification saying that AV043.RV23RC03_PA_CUS1 was available (performance update, 35.72MB in size) but that wouldn't install giving error Status 7.
Installed CWM 6.1.1, still tthe same results, it wouldn't even install any of the other ROM's that are posted in this forum.
I probably should mention that I saved the original OTA update for installation later.
here is the solution (at least in my case)
Downloaded ROM Acer_A700_AV043.RV00RC00_AV043.RV07RC06_PA_CUS1.zi p from http://forum.xda-developers.com/showthread.php?t=1720157
Extracted boot.img and flashed via fastboot flash boot boot.img
Rebooted into CWM recovery and flashed the earlier saved OTA update no problem (was saved on internal memory but external memory card should work as well)
Then all that needed to be done was to root the A700 again (I used method #2 again)
Hope that helps someone.
eman01 said:
OK. I finally tried above method to update rooted U.S. A700.
assert failed: apply_patch_check_("EMMC:\dev\block\platform\sdhci-tegra.3/by-name/LNX:4065536:95
Then a bunch of letters/numbers
E:Error in sdcard/update.zip
(Status 7)
Installation aborted.
Any ideas?
Click to expand...
Click to collapse
You are not using the original bootloader so checking failed.
Simply delete this line to fix it (it happened to me last week when I created my homemade OTA update). Don't forget to unlock your bootloader after that !
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