Related
Yeah, I wasn't thinking at all. I ran my update check, got excited and just did it. It wasn't until after the fact that I really realized what I might have done.
Well, here's everything that happened/is happening.
I was trying to root my pad and get cwm. The pad was running stock 3.1 at the time this.
Well, after a bit of reading and looking around, I decided the easiest way would be to use the batch script located here: http://forum.xda-developers.com/showthread.php?t=1185104
After setting everything up, I ran the script. My tablet was rooted, I could gain superuser access, and busybox was installed as well...however, I could not get into recovery. At all.
In the zip for the rootkit there are two versions of recovery.img, one to use if the other doesn't work...
Well they both didn't work.
So I play around on my tablet for a while and read about 3.2, check my updates and see that I can get the 3.2 update. I do it, install it.
Stupid.
Now the pad is stuck on the Eee Pad screen with the Asus and nVidia Tegra logo.
I can get into APX mode as well as make the tablet attempt to boot into recovery (though it just hangs on "Booting recovery kernel image").
Can't even turn it all the way off, it just hangs.
I tried downloading the v5 (now v6) script from the above thread, and used all of the options included within, including the 3.2 root & recovery. To no avail.
Seems pretty grim.
My phone is a Samsung Epic which I've rooted, flashed roms, upgraded/downgraded Android... With the phone there's a program to completely unroot and flash back to stock. Is there something like that with tablets?
I might've dived into rooting my tablet before reading enough, I read a significant amount before I did anything to my phone, but I convinced myself the prior experience would make this easy. Obviously not the case.
So...any help would be hugely appreciated. Even if it's just telling me that there's not really anything I can do, because I'll be able to take it back for another (though that can be complicated and is preferably avoided).
since you can get to apx mode try nvflash with stockrom to 8.4.4.5 by following these instructions.
http://tabletroms.com/forums/showthread.php?1071-Factory-3.1-NVFlash-Recovery-Roms&p=9968
You'll then need to upgrade to 8.4.4.11 then to 8.6.5.6 before attempting to root using the v5 beta batch root script http://forum.xda-developers.com/showthread.php?t=1185104
That should get you out of trouble. good luck.
IMHO the problem is the recovery.
The ota updates rely on the stock recovery image for doing its dirty work; for what you wrote, it seems that you have installed cwm...
In the batch script hit "5" to reinstall stock boot+recovery us images.
If this won't work, try the woonie's hint.
Hope this helps.
woonie said:
since you can get to apx mode try nvflash with stockrom to 8.4.4.5 by following these instructions.
http://tabletroms.com/forums/showthread.php?1071-Factory-3.1-NVFlash-Recovery-Roms&p=9968
You'll then need to upgrade to 8.4.4.11 then to 8.6.5.6 before attempting to root using the v5 beta batch root script http://forum.xda-developers.com/showthread.php?t=1185104
That should get you out of trouble. good luck.
Click to expand...
Click to collapse
Woonie is correct, I did this to myself last week. After using NVFlash to get back to stock 8.4.4.5, do not let the pad restore settings from your gmail account. Wait for that until after you have it upgraded to 8.6.5.6 and rooted it again to sync up to your account.
http://forum.xda-developers.com/showthread.php?t=1192072&page=2
I follow jhanford's post and get this done.
I've successfully recovered my tablet using this method. I was trying to update my TF using the batch script method and somehow managed to flash an outdated kernel. I know this because Asus tech support told me that was the reason my TF wasn't receiving the ota to 3.2. However, Asus tech support also told me that I could flash a new kernel by downloading the source code onto my tablet, then the TF would automatically recognize the [.rar] file and install my new kernel; which didn't work out as you might imagine.
I am now on official 3.1 8.4.4.11.and my kernel is v 2.6.36.3-00011-g3eb19ex And I can't get the OTA update. At one time I had official 3.2 [after previously flashing stock 3.1] but decided to try to root when I found out Netflix wasn't officially supported like the EEE pad site says it does.
Every time I try the batch script method, I end up stuck on the eee pad logo screen. Adb is working as well as apx drivers. Ultimate goal here is stock 3.2 rooted with netflix, but at this point I'd settle for stock official 3.2.
Any ideas? Tia
You may get help if you post your QUESTIONS in the correct forum.
This is the development forum....not Q&A.
Sent from my Jailbroken iPhone 4 using Tapatalk.
Thanks for the input. I just felt that that based on the content of the question, it would be better suited here.
you could try the zip file from the thread titled [OTA]Stock 3.2 zip file
And +1 on wrong section. This is not related to developing a new ROM or features for the Eee Pad.
I'm trying to avoid flashing CWM, that's where I end up bricking it.
jdmnash said:
I'm trying to avoid flashing CWM, that's where I end up bricking it.
Click to expand...
Click to collapse
I would suggest you to try Nvflash. it is the easiest way to root that tf.
I think the relationship between nvflash and the TF is complicated.
There are a few bootloaders out there, including the one used by custom roms, as well as the 4 stock ones.
My theory is that the kernel images in the boot and recovery images have to match the bootloader that is on the TF.
Throw in the fact that the bootloader is only written using the nvflash --create command or during the OTA update, and we have TFs with all kinds of different bootloaders going around that won't match what people are flashing. I think this is why CWM breaks whenever there is a stock OTA that rewrites the bootloader. I think most people brick trying to go back to stock from a custom rom. Going from stock to custom usually isn't a problem because the compatible bootloader is flashed in the rooting process.
Is this the first time we've seen an completely unlocked bootloader on Android?
sent from my cyanogen(mod) vision
jdmnash said:
Thanks for the input. I just felt that that based on the content of the question, it would be better suited here.
Click to expand...
Click to collapse
No. Android Development is for "DEVELOPMENT" does this thread have any kind of release? No.
That's why there's a sticky thread that says,
[REF] SEARCH BEFORE POSTING!! All Questions Go In The Q&A FORUM!!
Originally Posted By: mskip
Click to expand...
Click to collapse
ok folks i get it. I'm sorry. Is there anything I can do right now about accidently posting this in the wrong forum? Please forgive me. Mods feel free to move the thread or ban me or both. Whatever the normal punishment is.
Use the NVFlash unroot method here:
http://tabletroms.com/forums/showthread.php?1071-Asus-Transformer-NVFlash-Stock-3.1-Recovery-Roms
That will get it back to stock everything with 8.4.4.5. Then, you can manually install 8.4.4.11 with the download on the Asus website. After that it will recognize the OTA update to 8.6.5.6. Once you've done all that, use the Batch Script for a quick root, and you're done. I did this today. As long as you follow all the steps, it's a breeze.
I don't think it will recognize the OTA update to 8656. Roach's update will work, but not the stock update.
sent from my cyanogen(mod) vision
It will recognize it, because if you follow all the steps I listed, you're completely stock until you run the batch script to root 3.2. I did this myself on my transformer today.
My OP is not very clear, but that is exactly the steps I've followed to get to where I am today. I've given it 2 days to detect the new update and i've got nothing. I'm currently sitting on stock 8.4.4.11 waiting for the OTA.
kingwp1 said:
It will recognize it, because if you follow all the steps I listed, you're completely stock until you run the batch script to root 3.2. I did this myself on my transformer today.
Click to expand...
Click to collapse
How did you root before and what were you running before you went back to stock 8445?
sent from my cyanogen(mod) vision
stock 3.2. I was trying to get rooted 3.2 to get netflix
jdmnash said:
stock 3.2. I was trying to get rooted 3.2 to get netflix
Click to expand...
Click to collapse
Did you ever make a backup with CWM when you had 3.2?
no it was stock 3.2 firmware/recovery
I'm making progress. I'm now on rooted 8.4.4.11... still trying to get to 3.2
Dear friends,
as i have been hanging out in this forum, i have learnt a lot. But still, i cannot understand the attitude why people treat, reply or explain everything in a way that assumes all of us are android experts.
TF700 is my first android device(have been using Apple before) so I really need to improve-or create- fundamental knowledge. Just for your information, replying messages like; "ok now Unlock the Root system instead OTA .21 and blablablabla?" (btw. i am well aware of the fact that this sentence is totally meaningless)
Whatever, my point is it would be wonderful to have a fundamental knowledge thread, also keeping your great posts too at the same time.
Cheers!!
archonur said:
Dear friends,
as i have been hanging out in this forum, i have learnt a lot. But still, i cannot understand the attitude why people treat, reply or explain everything in a way that assumes all of us are android experts.
TF700 is my first android device(have been using Apple before) so I really need to improve-or create- fundamental knowledge. Just for your information, replying messages like; "ok now Unlock the Root system instead OTA .21 and blablablabla?" (btw. i am well aware of the fact that this sentence is totally meaningless)
Whatever, my point is it would be wonderful to have a fundamental knowledge thread, also keeping your great posts too at the same time.
Cheers!!
Click to expand...
Click to collapse
I am a newbie too -- bought the tf101 a couple of months ago - loved it -- told my husband he could have it - I was buying the 700 ! and was lucky enough to be able to order one (we live in Canada..... Tiger Direct.ca had them)
I have learned a lot from this forum -- glad I found it --- but I won't be "unlocking" anything ! the only thing I know how to "root" are my house plants !!! lol !! we don't even own smart phones yet -- we still have dumb phones !!! but I have my TF700 !!!
You mean sth like this?
seems hard, but it's not.
It seems tough in the beginning for noob, but actually you're going to get it. You should read the "Index" pointing out by d14b0ll0s to gain some basic knowledge and familiar with the terminology then you should be fine. Couple key words I want to point out that you should know. Currently TF700 came with a locked boot loader, meaning you not able to flash (install) custom firmware from our developers. This is a biggest issue at the moment. Sure there're workaround but it's a pain in the as...and unstable(could brick your pad if you not doing it right). When you see numbers like 21,22,26, they are firmware version number. The latest should be 26. OTA stands for "over the air" and we referred to firmware push to our pad by Asus, not manually download and install ourselves. Rooted is a process that you gain access as a administrator on your pad (you have full access to your phone), with rooted privilege you can almost do anything with your pad, like uninstall Asus embed software, do a full backup of your entire OS (operating system), modified system files etc... CWM is a tool you installed on your pad in order to flash (install) custom firmware. So at the minimum you should have root, and in the future when new custom firmware arrived, you can install cwm and used this tool to flash them. Keep in mind that with locked boot loader, you can't flash custom firmware. Finally, once you're rooted or have custom firmware installed, your pad will no longer can accepted OTA firmware (firmware push to your pad by Asus). In this case you need to roll back to stock (re installed factory firmware and no root), before you can do OTA update. Currently, I suggest you should stay on the side line and waiting for the OTA 4.1.1 JB (new Operating System called Jelly Bean, version 4.1.1 will be push to your pad by Asus). After reading this post you should be ready to play... good luck!
Sorry, but I don't get it, what is it about Verizon? Is it because you bought yours from Verizon? Mine comes from ASUS and I believe the OTA updates are from ASUS servers. Is it the US-specific thing that you mentioned?
Yeah... Everything is pretty easy even for people that have no clue what they are doing. My suggestion right now is to root but not unlock. Rooting is as simple as running the .bat file and following on screen directions (assuming you are using Windows). The only thing you need to do after the program is finished is to open up the Superuser app (might be SuperSU) and restart after that for safe measure.
Unlocking does VOID YOUR MANUFACTURERS WARRANTY (and possibly all others you may have purchased). Make sure you know what you want to do with an unlocked device before you do it. Personally, I am waiting for a stable JB build before I unlock. But the choice is ultimately up to you.
d14b0ll0s said:
Sorry, but I don't get it, what is it about Verizon? Is it because you bought yours from Verizon? Mine comes from ASUS and I believe the OTA updates are from ASUS servers. Is it the US-specific thing that you mentioned?
Click to expand...
Click to collapse
Sorry you're right, must not awake yet. ASUS that is. Thanks bro.
Your going to be fine try learning how to build aosp from source in a time limit
Sent from my Galaxy Nexus using xda premium
Skullmonkey said:
Yeah... Everything is pretty easy even for people that have no clue what they are doing. My suggestion right now is to root but not unlock. Rooting is as simple as running the .bat file and following on screen directions (assuming you are using Windows). The only thing you need to do after the program is finished is to open up the Superuser app (might be SuperSU) and restart after that for safe measure.
Unlocking does VOID YOUR MANUFACTURERS WARRANTY (and possibly all others you may have purchased). Make sure you know what you want to do with an unlocked device before you do it. Personally, I am waiting for a stable JB build before I unlock. But the choice is ultimately up to you.
Click to expand...
Click to collapse
I agree with Skullmonkey on this. Until you are ready for really hacking the system, all you really need is to root the system (run the DebugFS) to get "administrator access to your device".
You might want to read what buhohitr wrote several times as there is much to be gleaned from it. If it helps, copy/paste the contents of buhohitr's repsonse to a notepad text document and go through it word-for-word, isolate those that you find questionable or troublesome, then research what those words are. Anything that is "super difficult" you can just post back here in the Q&A section and I'm sure someone will help you in no time.
another noob question: does rooting the device void manufacturing warranty?
It does not. Only unlocking the device does.
Sent from my Transformer Infinity!
So if I root my Infinity...
...which pre-included apps can I get rid of?
Also which preloaded apps are best to bump off if I dare a root?
I have never dabbled with android down in the file system much for fear of doing something irreparable.
Well, to the OP: we already have quite a few 'basic' threads going on here, and no one forces you to embark on the more advanced stuff, do we? Just read up on it, and when you feel like you can make the jump, pick it up little by little. We're not all experts in here, but most of us can follow directions of the gurus really good, and we have the advantage of knowing how to save our butts when the excrement impacts the ventilator. (And most of us learnt it the hard way, by bricking and breaking...)
You should be fine in the regular forums, and as the others have said, stay out of the development sections until you feel secure enough to dabble around with unlocking and so on.
Sent from my ASUS Transformer Pad TF700T
buhohitr said:
Currently, I suggest you should stay on the side line and waiting for the OTA 4.1.1 JB (new Operating System called Jelly Bean, version 4.1.1 will be push to your pad by Asus). After reading this post you should be ready to play... good luck!
Click to expand...
Click to collapse
What's the method for unrooting/reflashing to stock at the moment? I rooted because I wanted to use Titanium Backup right after I got back up to .26. If we haven't figured out how to custom flash roms by the time jellybean comes out, I'll need to go back to stock. I would *hate* to have to lose all my apps, and its possible that titanium backup from 4.0.3 to 4.1.1 might royally screw up the system in doing a restore. So, if that's the case, I guess I'll reflash someway and lose everything? Doh.
spinaldex said:
What's the method for unrooting/reflashing to stock at the moment? I rooted because I wanted to use Titanium Backup right after I got back up to .26. If we haven't figured out how to custom flash roms by the time jellybean comes out, I'll need to go back to stock. I would *hate* to have to lose all my apps, and its possible that titanium backup from 4.0.3 to 4.1.1 might royally screw up the system in doing a restore. So, if that's the case, I guess I'll reflash someway and lose everything? Doh.
Click to expand...
Click to collapse
Anyone figure out a way to go back from root back to stock yet so that when Jelly Bean comes out we can upgrade?
spinaldex said:
Anyone figure out a way to go back from root back to stock yet so that when Jelly Bean comes out we can upgrade?
Click to expand...
Click to collapse
One method to get rid of root would be factory reset (power on while holding both the power and volume down while booting and running a factory reset.) But you could probably temporarily unroot with voodoo ota root keeper and then reroot once you install the upgrade to jelly bean with its root keeper.
Sent from my DROIDX using xda app-developers app
ekalb10 said:
One method to get rid of root would be factory reset (power on while holding both the power and volume down while booting and running a factory reset.) But you could probably temporarily unroot with voodoo ota root keeper and then reroot once you install the upgrade to jelly bean with its root keeper.
Click to expand...
Click to collapse
That's not true. Funny I've been responding to the same kind of "advice" a few minutes ago in another thread.
Temporarily unrooting through Root Keeper should work, but rooting has prevented updating firmware only for some users. I was rooted and installed updates both manually and through OTA without experiencing any issues. Getting to stock /system partition basically means restoring stock configuration files (like build.prop etc.), removing /system/xbin/su and any copies made by RootKeeper, as well as things that install to /system like BusyBox.
Even if you're rooted you should be able to update firmware manually through stock recovery (power down, power up, hold power and volume down, release, press volume up, etc., with microSD formatted FAT32 and with EP201_768_SDUPDATE on it, it's already in the how-to threads in the general section).
d14b0ll0s said:
That's not true. Funny I've been responding to the same kind of "advice" a few minutes ago in another thread.
Temporarily unrooting through Root Keeper should work, but rooting has prevented updating firmware only for some users. I was rooted and installed updates both manually and through OTA without experiencing any issues. Getting to stock /system partition basically means restoring stock configuration files (like build.prop etc.), removing /system/xbin/su and any copies made by RootKeeper, as well as things that install to /system like BusyBox.
Even if you're rooted you should be able to update firmware manually through stock recovery (power down, power up, hold power and volume down, release, press volume up, etc., with microSD formatted FAT32 and with EP201_768_SDUPDATE on it, it's already in the how-to threads in the general section).
Click to expand...
Click to collapse
I guess I was just misinformed on the factory reset, sorry if I confused anyone.
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app
d14b0ll0s said:
That's not true. Funny I've been responding to the same kind of "advice" a few minutes ago in another thread.
Temporarily unrooting through Root Keeper should work, but rooting has prevented updating firmware only for some users. I was rooted and installed updates both manually and through OTA without experiencing any issues. Getting to stock /system partition basically means restoring stock configuration files (like build.prop etc.), removing /system/xbin/su and any copies made by RootKeeper, as well as things that install to /system like BusyBox.
Even if you're rooted you should be able to update firmware manually through stock recovery (power down, power up, hold power and volume down, release, press volume up, etc., with microSD formatted FAT32 and with EP201_768_SDUPDATE on it, it's already in the how-to threads in the general section).
Click to expand...
Click to collapse
+ 1 I have rooted several tablets/phone over the last two years and backed it up using voodoo rootkeeper with ZERO issues updating firmware/OTAS. The only thing that happens after updating is that I loose root, but that's where voodoo OTA rootkeeper comes to play. Only a handful of people have had problems. Some are legit while others have messed/modded their device prior to updates. (like removeing system apps or modding build. Props)
"60% of the time, it works everytime. "
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Unroot it again ??
If there are problems with the tablet and it must be repaired on warranty, then I need to unroot it again.
How do I unroot it again ??
Regards Peder
Before anybody says to use the search function, I've been looking through the general topics non-stop for one that applies to my situation, and either it slipped through the cracks (likely) or it doesn't exist (not likely).
Basically, my tablet is rooted and unlocked, and I'm on ICS; the first one that had face unlock in it. I'd really like to update my tab to JB, but I need to be pointed toward directions for updating a rooted and unlocked tab. But on top of that, I also need recent instructions, because I know that earlier attempts at getting this thing updated have resulted in lots of bricked tabs.
If anybody could tell me if it's possible to update my tablet to JB right now, I'd appreciate it, and if someone has figured out how to do it, can you please point me toward that thread? I'd really appreciate it.
-Tim
I'm in the same configuration, custom-ics-rom with twrp recovery on unlocked device.
I believe the first thing to do is enabling NVFLASH, that will make things safer also in the worst cases.
I did that and now hopefully I have an unbrickable device.
I'm a bit confused on how to go forward, I know that there are two versions of twrp, maybe I should install the JB version, booting inside it and then flash the downloaded JB update from ASUS site, or use the twrp for ICS for flashing and after that install the JB version ?
Anyone knows what is the correct option ?
Giuseppe
Tim 13 said:
Before anybody says to use the search function, I've been looking through the general topics non-stop for one that applies to my situation, and either it slipped through the cracks (likely) or it doesn't exist (not likely).
Basically, my tablet is rooted and unlocked, and I'm on ICS; the first one that had face unlock in it. I'd really like to update my tab to JB, but I need to be pointed toward directions for updating a rooted and unlocked tab. But on top of that, I also need recent instructions, because I know that earlier attempts at getting this thing updated have resulted in lots of bricked tabs.
If anybody could tell me if it's possible to update my tablet to JB right now, I'd appreciate it, and if someone has figured out how to do it, can you please point me toward that thread? I'd really appreciate it.
-Tim
Click to expand...
Click to collapse
Keep ICS, as JB will cause much trouble especially if you are rooted, trying to OC and is generally slowein my opinion
I prefer to try it anyway, tomorrow I will try flashing, after all if something will go wrong I should be able to recover with nvflash.
[
QUOTE=grimsonfart;32974661]Keep ICS, as JB will cause much trouble especially if you are rooted, trying to OC and is generally slowein my opinion[/QUOTE]
Thank you, Grim. That's disappointing to hear about JB, but if you think that my current build is better than that (which makes sense considering I've seen at least one thread about downgrading from JB to ICS), then I will keep my tab on ICS for now, and thank you for your input, I appreciate it.
-Tim
If you have twrp recovery, can't you download the jb ROM from the Asus site for your region and flash it in? I'm unlocked and that's how I upgraded one version of jb to another, but my ICS to jb was ota, so in your case I can't speak from experience. There is a full upgrade, and root guide in the general section.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
I just managed to do what you re looking to achieve.
I m pretty noob so it tok me a whole day to figure it out.
So first download jb update on asus website (pick the right one for ur type of tf300)
Flash it through adb
At that point i got jb installation working but bootloop
So i flashed jb version of twrp (adb)
I then went in recovery and flashed clean rom 2.5 which worked flawlessly
Just for the fun i did factory reset afetrwards and stock jb eventually launched right
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
gst0098 said:
I'm in the same configuration, custom-ics-rom with twrp recovery on unlocked device.
I believe the first thing to do is enabling NVFLASH, that will make things safer also in the worst cases.
I did that and now hopefully I have an unbrickable device.
I'm a bit confused on how to go forward, I know that there are two versions of twrp, maybe I should install the JB version, booting inside it and then flash the downloaded JB update from ASUS site, or use the twrp for ICS for flashing and after that install the JB version ?
Anyone knows what is the correct option ?
Giuseppe
Click to expand...
Click to collapse
I successfully installed jb following the guide on this site, the only thing that was not working was the flashing of the stock rom, neither given options worked (fastboot flash recovery or fastboot flash system) , I discovered that our eepad has a partition nmed staging used for firmware installs. I then flashed with
fastboot flash staging blolb
and all went good.
Btw I find the JB better than ics, more responsive and smoother, and also if it is not yet overcooked.
Hi everyone
First off I would like to thank everyone who contributes on this board, I have been lurking for quite awhile even though I dont have any android devices, the reading is very interesting.
I have just got my first android device today delivered from BH Photo (I am in Australia) and have charged and powered it up. I have been reading on the forums about rooting and then unlocking. The android version appears to be 4.0.3 (ICS).
My questions are these:
Should I root this device and unlock the bootloader with ICS, then install TWRP and make a backup of it. Once this is done then update to JB? The firmware of the tablet is (I think this is right) IM74K:US_epad_9.4.5.26-20120720 and the kernel is 2.6.39.4 [email protected] #1
or
Update the device to JB then root it, but Im a bit confused with the unlocking part here what program is used to unlock the bootloader? Is it the Asus one? Also with rooting programs which one is more commonly used for both ICS and JB? Can I apply a manual update of JB using the Ausrtalian version instead of the US one.
Sorry for all the noob questions. I have read the index and after reading it still had some questions.
Thank you for your time
deathwalker01 said:
Hi everyone
First off I would like to thank everyone who contributes on this board, I have been lurking for quite awhile even though I dont have any android devices, the reading is very interesting.
I have just got my first android device today delivered from BH Photo (I am in Australia) and have charged and powered it up. I have been reading on the forums about rooting and then unlocking. The android version appears to be 4.0.3 (ICS).
My questions are these:
Should I root this device and unlock the bootloader with ICS, then install TWRP and make a backup of it. Once this is done then update to JB? The firmware of the tablet is (I think this is right) IM74K:US_epad_9.4.5.26-20120720 and the kernel is 2.6.39.4 [email protected] #1
or
Update the device to JB then root it, but Im a bit confused with the unlocking part here what program is used to unlock the bootloader? Is it the Asus one? Also with rooting programs which one is more commonly used for both ICS and JB? Can I apply a manual update of JB using the Ausrtalian version instead of the US one.
Sorry for all the noob questions. I have read the index and after reading it still had some questions.
Thank you for your time
Click to expand...
Click to collapse
Welcome to the Community!
There are a few on-going threads regarding this same topic. You might want to read those and make sure you understand the lingo/jargon being used (like: fastboot, bootloader, Recovery, adb. etc) as well as what it's for before you start your hacking.
Some things to keep in mind
Currently to have Root access in JB, you need to get root in ICS then use OTA Keeper to maintain Root for JB update.
The Bootloader unlocker tool is from ASUS and needs to communicate with ASUS servers for it to unlock.
Unlocking the bootloader will void your warrenty. Make sure you have a good device before you do it.
You have a version of tablet (9.4.5.26) that is able to use NVFlash that can help recover your tablet during a soft brick.
You should use an update that is appropriate for your device. If it comes with US, stay with US. Installing an update for a different region might not cause problems but there is no guarantee. Best to avoid the possibility by staying with the region it comes with.
For some reading material, I think that my blog post might help give you some additional details. However, I highly suggest that it be used for research only until you are aware of exactly what you are trying to accomplish. Remember to ask questions if things are confusing or if you are wondering what needs to be done next. 'Tis better to ask and be delayed than to be over-eager and bricked.
Hope this helps you during your first steps of XDA Android hacking!
I just got my TF700 last week and I wanted cleanrom on it and this is the order of stuff I did:
1. Unlocked bootloader
2. Nvflash setup
3. Installed TWRP
4. Flashed official Asus update
5. I lost TWRP so I installed it again
6. Flashed cleanrom
Probably not the most efficient way, but it was easy to do and didn't take too long.
hong90 said:
I just got my TF700 last week and I wanted cleanrom on it and this is the order of stuff I did:
1. Unlocked bootloader
2. Nvflash setup
3. Installed TWRP
4. Flashed official Asus update
5. I lost TWRP so I installed it again
6. Flashed cleanrom
Probably not the most efficient way, but it was easy to do and didn't take too long.
Click to expand...
Click to collapse
It's the most efficient way.
I have nothing to add except for the remark that NvFlash is key -- GET IT WHILE YOU STILL CAN!
I'm not even kidding here. It gives you 100% flexibility in doing whatever you wish (up- as well as downgrading, even the bootloader!) and provides a key benefit in recovering your device when that whale-sized piece of excrement hits the large ventilator running at top speed.
Thanks to everyone that has replied to my post. I have successfully rooted the tablet and unlocked the bootloader. Before I do anything else Im going to run NVflash and back it up. I have a quick question though. I have download NVFlash to my computer and extracted it. Do I need to copy it across to the tablet and then enter fastboot? I havent got an extenal sd card will it save the images to the tablet's hard drive?
Cheers
Deathwalker
i followed this video:
https://www.youtube.com/watch?v=J3ypzUaKxvo&feature=youtube_gdata_player
i watched it before i actually did it once or twice to make sure i know what to do. you don't need an external sd card. following the fastboot steps will pull the files that you need onto the internal one in a folder
Last night I used NVFlash to make backup of the tablet. A big thank you to alienedd as I followed his blog and also the guide from androidmobi team and managed to get the img files done. Is there anyway to test bar for wiping the tablet?
Now all I have left to do is install OTA RootKeeper and TWRP, back up the existing tablet and then flash a custom ROM (Im thinking cleanrom)
You don't need OTA Rootkeeper anymore because you have unlocked you're bootloader. And custom roms like Cleanrom are already pre-rooted so after flashing the cleanrom you will have root anyway.