[Q] From .26 to JB: Order of operations? - Asus Transformer TF700

I just bought a brand-new TF700 and it is fortunately still on .26 - I haven't even removed the wrapper from the tablet itself.
I want to (safely) end up rooted and on JB when I am finished, but some of the steps between are confusing, for example:
I see that there are issues with .30 and the nvflash backup procedure, correct?
I also am on the fence about unlocking. I guess I would be willing to void the warranty (gulp) but I really do not plan to run anything but a stock rom. On the other hand, having an nvflash backup appeals to me very much but if I understand it correctly, I have to be unlocked first?
But, while not crazy about a custom ROM, I do want to use a custom recovery because I like being able to do a nandroid backup. I see TWRP isn't ready for JB yet, but a modified CWM is?
So, I have downloaded several files, and read the various guides as to root, unlock, etc. But, what I still don't understand is what steps I should perform in what order. I understand that rooting .26 is probably the first step, but here are some of my questions:
1. At what point do I unlock? before .30? Do I even install .30 if I want to end up on JB
2. I know I need to root, update su, and then use Voodoo to preserve it prior to the JB update
So, I suppose what I really need the most help with is what order to perform what steps in. All the guides are helpful, but the info seems to contradict in some places.
With the clean slate on what I have with .26, what order do I do what to avoid a soft or hard brick?
Thanks in advance!
-Rob

robroy90 said:
I just bought a brand-new TF700 and it is fortunately still on .26 - I haven't even removed the wrapper from the tablet itself.
I want to (safely) end up rooted and on JB when I am finished, but some of the steps between are confusing, for example:
I see that there are issues with .30 and the nvflash backup procedure, correct?
I also am on the fence about unlocking. I guess I would be willing to void the warranty (gulp) but I really do not plan to run anything but a stock rom. On the other hand, having an nvflash backup appeals to me very much but if I understand it correctly, I have to be unlocked first?
But, while not crazy about a custom ROM, I do want to use a custom recovery because I like being able to do a nandroid backup. I see TWRP isn't ready for JB yet, but a modified CWM is?
So, I have downloaded several files, and read the various guides as to root, unlock, etc. But, what I still don't understand is what steps I should perform in what order. I understand that rooting .26 is probably the first step, but here are some of my questions:
1. At what point do I unlock? before .30? Do I even install .30 if I want to end up on JB
2. I know I need to root, update su, and then use Voodoo to preserve it prior to the JB update
So, I suppose what I really need the most help with is what order to perform what steps in. All the guides are helpful, but the info seems to contradict in some places.
With the clean slate on what I have with .26, what order do I do what to avoid a soft or hard brick?
Thanks in advance!
-Rob
Click to expand...
Click to collapse
Do not upgrade to .30 before you do the following (very important and life saving).
Make a full backup of all your apps. (not system apps)
1. Root and unlock bootloader then install custom recovery and Voodoo OTA root keeper from the market.
2. Use NVflash to backup your bootloader (very important, can recover from brick)
3. Use Voodoo OTA root keeper to temporary unroot and save a copy
4. Upgrade to .30 then restore root using OTA root keeper, download "root checker" from the market and verify that you still have root
5. Upgrade to JB then install latest custom recovery CWM (twrp is not working with JB)
6. Restore your apps.
here is the detail how to link:
http://forum.xda-developers.com/showpost.php?p=30223822&postcount=1

buhohitr said:
Do not upgrade to .30 before you do the following (very important and life saving).
Make a full backup of all your apps. (not system apps)
1. Root and unlock bootloader then install custom recovery and Voodoo OTA root keeper from the market.
2. Use NVflash to backup your bootloader (very important, can recover from brick)
3. Use Voodoo OTA root keeper to temporary unroot and save a copy
4. Upgrade to .30 then restore root using OTA root keeper, download "root checker" from the market and verify that you still have root
5. Upgrade to JB then install latest custom recovery CWM (twrp is not working with JB)
6. Restore your apps.
here is the detail how to link:
http://forum.xda-developers.com/showpost.php?p=30223822&postcount=1
Click to expand...
Click to collapse
Is there any benefit in going to .30 before going to JB?
Reason I ask is that I went from .26 straight to JB (using the 444MB download from the Asus website).
Is the intermediate step only for those that want the OTA update?

Nope. You should be fine since there is no advantage.
Sent from my ASUS Transformer Pad TF700T using xda premium

Galaxea said:
Is there any benefit in going to .30 before going to JB?
Reason I ask is that I went from .26 straight to JB (using the 444MB download from the Asus website).
Is the intermediate step only for those that want the OTA update?
Click to expand...
Click to collapse
If you install using the file on Asus's website you will likely lose root indefinately. Better to root and use OTA Rootkeeper and use the dlpkgfile method to keep root for the future.
an extremely easy step by step guide i put together (including files for WW and US tablets) is linked here

Related

Should I update to 8.6.5.13 then root?

I just received my Asus back from being repaired for light bleed. It still has bleed but what can i do? It came back loaded with 8.6.5.9. Should I try to OTA update to 8.6.5.13 and root with the universal root? It is a B30 rooted previously.
Thanks
As far as the light bleed...I would say let it go. Most of us are dealing with the light bleed as well....its not a great thing but it really isn't a big deal either. Be happy that you have a TF that's rootable at this point. The root kit v7.1 claims to be able to root 8.6.5.x. So if all you want is root, then go ahead and update first, then root using that method. If you do not install clockworkmod recovery, you may be able to receive OTA updates, but will loose root and will have to be re-rooted. Another option is to root, install clockworkmod recovery, and update via a zip flash posted in the dev section. Once you install clockworkmod reovery, you won't be able to receive OTA updates and will have to rely on getting a cwm recovery flashable zip for updates. Or you can root, ainstall CWM recovery, and install a custom rom, which they will always include the latest OTA update builds. Its up to you.
Thank you. I should have known, but I did not know that the CVM was the reason I could not OTA update. I always thought it was the root itself.
Thanks for this info. I'm on it.
Yes you should be able to get it to work correctly
frankc123 said:
Yes you should be able to get it to work correctly
Click to expand...
Click to collapse
Thanks frankc123. Did it. Rooted and back in business!

Will i be able to update to ICS?

Hey guys i have a TF101G still on original Asus android honeycomb 3.2.1. I'm waiting for the OTA ICS update, but i was wondering if i will be able to do it, beacuse i rooted the tab with nachoroot.
I just have Superuser, no clockwork, no modded roms etc.
Thanks for any help
Are you asking if you can install the official Asus update via OTA? If so, I don't see why not but you'll have to wait for them to release it. If rooting is the only thing you've done then OTA updates should install fine but you will lose root after the upgrade. I would recommend you wait for a custom tf101g rom to come out.
ambertx said:
Are you asking if you can install the official Asus update via OTA? If so, I don't see why not but you'll have to wait for them to release it. If rooting is the only thing you've done then OTA updates should install fine but you will lose root after the upgrade. I would recommend you wait for a custom tf101g rom to come out.
Click to expand...
Click to collapse
So long as you did not remove (or freeze) any pre-installed apps and still have stock recovery it should update. You may want to grab the VooDoo OTA Rootkeeper to back up your root and then run it after the update to restore root. You will probably have to use Titanium Backup to restore permissions to SuperUser. The other option is to do NachoRoot (or ViperMod Option 1) after the ICS update.

Rooting Xoom Wifi with JB 4.1.1?

Sorry, I'm a bit cautious when dealing with rooting and whatnot...
I currently have ICS installed on my US Wifi Xoom. It has been rooted after the last update before JB, but is using the stock ROM otherwise.
What I'm wondering first is: Do I NEED to unroot before attempting the OTA update to JB, or is it just recommended? And then after I update to JB, do I use the same method to root? I believe I used this guide: http://www.xoomforums.com/forum/mot...ooting-flashing-unrooting-under-one-roof.html
Thanks!
You don't have to unroot to receive the ota. Get vodoo ota root keeper app it will protect root during the update
The Universal Root Method does not work on 4.1.1 does anyone have a fix.....
gmanunited said:
The Universal Root Method does not work on 4.1.1 does anyone have a fix.....
Click to expand...
Click to collapse
ok,,after many tries i finally figured a way to get to stock rooted Jb with the Ota...it was a long process but i was able to do it.
step 1. i re flashed the xoom stock images HC 3.0
step 2. update the xoom from 3.0 to 4.0.4 using the over the air updates.
step 3. fastboot flash the eos r6 recovery while still on 4.0.4
step 4 create a nandroid of the stock 4.0.4 system
step 5. install the Universal Xoom root zip
step 6. log into google account to have access to market
step 7 update superuser app, download ota rootkeeper
step 8 use ota and create a copy of su, then click temp unroot
IMPORTANT
make sure that you have a copy of the jelly bean ota on your internal sd(http://forum.xda-developers.com/showthread.php?t=1736634)
step 9 turn off xoom, then boot into eos recovery
NEXT FEW STEPS ARE CRUCIAL
step 10 choose advance restore from internal (not regular restore option) and select the nandroid of the stock 4.0.4
step 11 select the option to restore only the boot.img
step 12 now install the JB Ota ( when it boots you will lose the eos reovery and the stock recovery will be flashed back,, so you can always fastboot flash back the eos recovery, just make sure to delete the recovery boot.p file in the system folder using root explorer or something similar.)
step 13 once you have flashed the JB ota, boot back into android, open the ota rootkeeper app and restore the su,, then use titanium backup or some other root app to verify that you have root.
optional step 14 after verifying that you do indeed have root access perform a factory wipe so you can start fresh. that's what i did and all was good.
hope that helps some people.
edit : if you are on a stock 4.0.4 than you can continue from step 3 as basically you need to be there in order to follow the rest.
Thanks. I will try this method.
I used the method above with one minor change and it worked perfectly. In place of step 12, I powered down and then booted into fastboot and flashed the stock recovery image. After that I rebooted and was then able to accept the JB 4.1.1 OTA directly without having to download and install it manually. The statement in parenthesis in step 12 still applies.
Tito2007 said:
ok,,after many tries i finally figured a way to get to stock rooted Jb with the Ota...it was a long process but i was able to do it.
step 1. i re flashed the xoom stock images HC 3.0
step 2. update the xoom from 3.0 to 4.0.4 using the over the air updates.
step 3. fastboot flash the eos r6 recovery while still on 4.0.4
step 4 create a nandroid of the stock 4.0.4 system
step 5. install the Universal Xoom root zip
step 6. log into google account to have access to market
step 7 update superuser app, download ota rootkeeper
step 8 use ota and create a copy of su, then click temp unroot
IMPORTANT
make sure that you have a copy of the jelly bean ota on your internal sd(http://forum.xda-developers.com/showthread.php?t=1736634)
step 9 turn off xoom, then boot into eos recovery
NEXT FEW STEPS ARE CRUCIAL
step 10 choose advance restore from internal (not regular restore option) and select the nandroid of the stock 4.0.4
step 11 select the option to restore only the boot.img
step 12 now install the JB Ota ( when it boots you will lose the eos reovery and the stock recovery will be flashed back,, so you can always fastboot flash back the eos recovery, just make sure to delete the recovery boot.p file in the system folder using root explorer or something similar.)
step 13 once you have flashed the JB ota, boot back into android, open the ota rootkeeper app and restore the su,, then use titanium backup or some other root app to verify that you have root.
optional step 14 after verifying that you do indeed have root access perform a factory wipe so you can start fresh. that's what i did and all was good.
hope that helps some people.
edit : if you are on a stock 4.0.4 than you can continue from step 3 as basically you need to be there in order to follow the rest.
Click to expand...
Click to collapse
Based on your steps it sounds like the only real important piece is the rooted boot.img file from ICS.
If someone were to post it, I'd imagine people could simply do this for rooting JB
fastboot oem unlock (unlock bootloader if not already done)
fastboot flash boot /path/to/<boot>.img
Click to expand...
Click to collapse
No guarantees this would work, but in theory it seems right to me.
Are you serious ? the traditional root method doesn't work anymore on JB ??
kinder771 said:
Are you serious ? the traditional root method doesn't work anymore on JB ??
Click to expand...
Click to collapse
Honestly not really a big surprise. Things change and what security flaw that allowed rooting on previous versions of Android for a device may be patched in future releases.
Okay completed this method and worked fine.
I also on step 12 flashed the stock recovery then performed the update through OTA and after verifying ROOT access with Titanium Backup I OEM unlocked which wipes the device but not Root Access. Its a lot OTA's but a good way to keep root on JellyBean 4.1.1.....
Thanks
kinder771 said:
Are you serious ? the traditional root method doesn't work anymore on JB ??
Click to expand...
Click to collapse
After doing the traditional root method, flash the latest super user using cwr, that is what i did and i now have root.
Sent from my SAMSUNG-SGH-I747 using xda premium
Great to know there maybe an easier method.
JB update
So wait the officials JB OTA is out already?! And if it did how come I can't update on my rooted xoom. Anybody
dough30i said:
So wait the officials JB OTA is out already?! And if it did how come I can't update on my rooted xoom. Anybody
Click to expand...
Click to collapse
Yes, i have been on official 4.1.1 for 2 weeks now, i say official because i updated via OTA.
Sent from my Xoom using xda premium
I think Universal Root Method and flashing latest Superuser working. I have not tried but would love to know if it works.

Lost root access after firmware

Hello guys,
I have an ASUS TF700T running ICS. I used motochopper to root it successfully.
Yesterday, I upgraded the firmware when prompted and lost root access; SuperSu app is still there but show an error when I run it because no more root.
I tried to run motochopper again but still I can't get root.
Can someone please help me step by step how I can restore root access? Do i have to update ROM?
Thanks.
androidofan said:
Hello guys,
I have an ASUS TF700T running ICS. I used motochopper to root it successfully.
Yesterday, I upgraded the firmware when prompted and lost root access; SuperSu app is still there but show an error when I run it because no more root.
I tried to run motochopper again but still I can't get root.
Can someone please help me step by step how I can restore root access? Do i have to update ROM?
Thanks.
Click to expand...
Click to collapse
upgrading removes root, always, your su executable will still be there but not usable as when rooted.
for this there is a nice app called OTA RootKeeper, which you should install right after rooting, and which lets you make a backup of your root, so that you can temp-unroot when upgrading and restore root when you finished.
you'll have to get rooted again, how, i guess will depend on what version you got upgraded to.
androidofan said:
Hello guys,
I have an ASUS TF700T running ICS. I used motochopper to root it successfully.
Yesterday, I upgraded the firmware when prompted and lost root access; SuperSu app is still there but show an error when I run it because no more root.
I tried to run motochopper again but still I can't get root.
Can someone please help me step by step how I can restore root access? Do i have to update ROM?
Thanks.
Click to expand...
Click to collapse
If you upgraded to 10.6.1.14.10 you're out of luck with Motochopper. Asus seems to have plugged the hole that exploit used. Check your firmware version under About Tablet > Build Number
You can downgrade to 10.6.1.14.8, root with Motochopper and then use OTA Rootkeeper as described above.
Dwnld the .8 firmware for your SKU from the Asus Support Downloads site, unzip the file once (resulting in another zip), put that zip into the root of your internal storage, reboot and you should get a notification to downgrade.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Thanks for your help.
I still have problem. I unzipped the file and get another zip jb-mr1-t30-r1-10.6.1.14-10.6.1.14.8-20130514-1751-foss.tar.gz. I copied it into the root of the sd internal storage, but no pop-up window showed-up telling me there is an update , I rebooted the device with no notification and I even tried a cold boot with no sucess.
Is there something i do wrong?
Will all the data be lost when performing a firmware downgrade from .10 to .8 ?
androidofan said:
Will all the data be lost when performing a firmware downgrade from .10 to .8 ?
Click to expand...
Click to collapse
Yes, I just had to do that. Make sure you have a good Titanium backup or similar. Also, backup any other things like pictures and etc.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
androidofan said:
I still have problem. I unzipped the file and get another zip jb-mr1-t30-r1-10.6.1.14-10.6.1.14.8-20130514-1751-foss.tar.gz. I copied it into the root of the sd internal storage, but no pop-up window showed-up telling me there is an update , I rebooted the device with no notification and I even tried a cold boot with no sucess.
Is there something i do wrong?
Click to expand...
Click to collapse
You need to download the firmware, not the source code. Also make sure you get the correct firmware for your SKU (WW, US, etc.).
I made a mistake I downloaded source code instead of firmware, my bad.
Well I think I will give up to try to get back my root access, that too much risk to downgrade and lost all my data. I hope a new motochopper version will implement another exploit to fix that!
androidofan said:
I made a mistake I downloaded source code instead of firmware, my bad.
Well I think I will give up to try to get back my root access, that too much risk to downgrade and lost all my data. I hope a new motochopper version will implement another exploit to fix that!
Click to expand...
Click to collapse
MotoChopper wasn't designed for the TF700T, it was just pure luck that it worked so i don't think that a new version will be out soon, but maybe we will be lucky enough to get some other tool which can root the new firmware... time will tell.

[Q] Just want to use the "Titanium Backup" app

I am using Stock Kernel and CM 12.1 on my Oneplus One. I just want to use the "Titanium Backup" app (that running on Root device only). What exactly I need to do with my phone: ???
Just Unlock my Bootloader and run SuperSU ?
Can I still be able to use Rom OTA with the Unlock Bootloader ?
Thanks!
Too late for Titanium backup now!
Please read this guide very carefully. It covers everything you need to know: [GUIDE] Unlock/Root/Flash for OnePlus One
To answer your question briefly, in order to use Titanium Backup, you need a rooted device.
To root your device you need:
unlocked bootloader
custom recovery (i.e. TWRP )
When you unlock your bootloader, you will lose all your data - your phone will be wiped!
Long story short, it is now too late for you to use Titanium backup to backup your apps & data.
Please note that there are methods to backup your apps which do not require root access, but you will have to use adb & the command line - not for everyone, and not what you had in mind I imagine.
You might just want to make a list of your favourite apps, backup their data & settings as much as you can, and then once you've got some sort of backup done, proceed to unlock your bootloader (and wipe your device), install TWRP, gain root, and profit.
Once again: Please read this guide very carefully. It covers everything you need to know: [GUIDE] Unlock/Root/Flash for OnePlus One
ohussain said:
Please read this guide very carefully. It covers everything you need to know: [GUIDE] Unlock/Root/Flash for OnePlus One
To answer your question briefly, in order to use Titanium Backup, you need a rooted device.
To root your device you need:
unlocked bootloader
custom recovery (i.e. TWRP )
When you unlock your bootloader, you will lose all your data - your phone will be wiped!
Long story short, it is now too late for you to use Titanium backup to backup your apps & data.
Please note that there are methods to backup your apps which do not require root access, but you will have to use adb & the command line - not for everyone, and not what you had in mind I imagine.
You might just want to make a list of your favourite apps, backup their data & settings as much as you can, and then once you've got some sort of backup done, proceed to unlock your bootloader (and wipe your device), install TWRP, gain root, and profit.
Once again: Please read this guide very carefully. It covers everything you need to know: [GUIDE] Unlock/Root/Flash for OnePlus One
Click to expand...
Click to collapse
First thanks for your answer! Do I lose the rom OTA Update after unlock my bootloader and install TWRP ? Do I must change to the TWRP recover or I can use the stock one?
Sent from my A0001 using xda premium
You're welcome. You cannot use the stock recovery, and you will not receive OTAs once you've unlocked your bootloader, installed TWRP, and rooted.
Trust me, you are not missing out on anything - OTAs will be rare, and the quality of the OS provided by Cyanogen is low.
Once you have TWRP installed, you can choose to install other ROMs. I highly recommend XenonHD. Light, stable, AOSP-based (not a CM clone), with full layers support, and a balanced feature-set.
There are many ROMs available for the OnePlus One for you to choose from, and you could also run CM or OxygenOS - it's up to you.
Just make sure you read & follow Heisenberg's guide, and you'll be fine. :good:
Since you're coming from Cyanogen's lollipop build, you should pay special attention to the note at the end of section 2 of Heisenberg's guide ('How To Install A Custom Recovery On Your Device').
xperia_88 said:
First thanks for your answer! Do I lose the rom OTA Update after unlock my bootloader and install TWRP ? Do I must change to the TWRP recover or I can use the stock one?
Sent from my A0001 using xda premium
Click to expand...
Click to collapse
Unlocking your bootloader has no effect on the ability to take OTA updates. However, having a custom recovery and root do. If you want to take an OTA in future you just need to flash the stock recovery and the stock system.img and OTA's will work perfectly.
ohussain said:
You're welcome. You cannot use the stock recovery, and you will not receive OTAs once you've unlocked your bootloader, installed TWRP, and rooted.
Click to expand...
Click to collapse
This isn't entirely true, the unlocked bootloader doesn't matter.
Heisenberg said:
This isn't entirely true, the unlocked bootloader doesn't matter.
Click to expand...
Click to collapse
You're God damn right.
That's what I meant, but thank you for clearing up precisely what precludes one from receiving OTA updates. :good:
Heisenberg said:
Unlocking your bootloader has no effect on the ability to take OTA updates. However, having a custom recovery and root do. If you want to take an OTA in future you just need to flash the stock recovery and the stock system.img and OTA's will work perfectly.
Click to expand...
Click to collapse
Thanks for your clear answer!!!
Since I just want to use my favorite Titanium Backup but still using OTA update I would appreciate if you'LL guide me what is the easier way to do that.
I know now that to Unlocking my bootloader has no effect on the ability to take OTA but the custom recovery and root do so where I can find link to the stock recovery and the stock system.img and do I must to flash them after the Unlocking my bootloader ?
10X
xperia_88 said:
Thanks for your clear answer!!!
Since I just want to use my favorite Titanium Backup but still using OTA update I would appreciate if you'LL guide me what is the easier way to do that.
I know now that to Unlocking my bootloader has no effect on the ability to take OTA but the custom recovery and root do so where I can find link to the stock recovery and the stock system.img and do I must to flash them after the Unlocking my bootloader ?
10X
Click to expand...
Click to collapse
In order to use Titanium you need to unlock your bootloader, then flash TWRP recovery, then use TWRP recovery to flash SuperSU. You'll have root now and Titanium will work. Once you get to the point where you want to take an OTA you can extract the system.img and the recovery.img from the fastboot zip which you'll find here:
http://forum.xda-developers.com/showthread.php?t=2906746
Flash them and then OTA updates will work. There are detailed instructions in my guide:
http://forum.xda-developers.com/showthread.php?t=2839471

Categories

Resources