Database Info

So you are all experts, what about newbies?(Root, Unlock, OTA etc..)

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

unable to root/unlock bootloader after repairs?=> Solved (Answer is on page 2)

Hey guys,
I sent my device to Asus a couple of days ago for repairs.
Asus did a great job on repairing my screen, but... um..
they have undone my root access and they've also relocked my bootloader, I think, although I can't get any OTAs.
Original question was:
What can I do to get my root again, because the scripts of sparky's tool don't seem to work anymore...
Sorry for this noobish question, but I swear that this has never happened to me before (and I have unlocked and rooted numerous devices)
What kind of sorcery is going on?!
Click to expand...
Click to collapse
Then I found the answer thanks to these amazing guys answering and trying to help.
It's a strange method, but it woudn't work otherwise:
I had to unlock the device (still on that very first stock JB rom).
Then, I flashed CWM through fastboot. Have a look here. However, do not forget: in this thread the OP referenced to an unofficial CWM. Go to the TF700 Android Development page and download the official CWM in stead.
After that I flashed a CWM-suitable SuperSU.zip (flashable) which made me have whereas it was impossible with any other method! (works through TWRP as well, for those that only have the unable to root problem )
Then, I flashed TWRP (but that's just a question of preferences, I guess) => This is no obligatory step of course!
There you go, for anyone who has/will have the same issues as me: follow these steps and let me know if it worked for you!
Have fun flashing Custom Roms/Kernels and/or recoveries again!
It might seem complicated, but it really isn't.
Good uck to those who follow(ed) my path

adelancker said:
Hey guys,
I sent my device to Asus a couple of days ago for repairs.
Asus did a great job on repairing my screen, but... um..
they have undone my root access and unlocked bootloader.
Click to expand...
Click to collapse
You mean relocked your bootloader?
...or actually unlocked it?

Thats OK said:
You mean relocked your bootloader?
...or actually unlocked it?
Click to expand...
Click to collapse
Sorry for that!
I meant that they relocked my bootloader, but still I can't get any OTAs
Thanks for the answer by the way.
I'd like to get it back to CR asap, since I really like that ROM, but noone has helped be yet
That is, until you arrived!

Ah
If we can get you successfully unlocked then the flashing can begin.
Have you tried unlocking via the Asus unlock .apk?
Seem as tho some tab owners have had problems with the Asus unlock tool.

I actually have the exact same problem.
Tablet back from screen repairs and now my root is gone, clean JB is installed and I can't seem to unlock (I wasn't unlocked before though).
I tried unlocking within the newest firmware with the ASUS Unlock app, failed with the "Unknown error occured, this could be a network problem".
Then I decided to atleast fix me root so I downgraded to .30 (ICS) and RootDebugFS fixed my root access.
Still my unlocking fails.
My serial is still the same btw.

DarkFire1985 said:
I actually have the exact same problem.
Tablet back from screen repairs and now my root is gone, clean JB is installed and I can't seem to unlock (I wasn't unlocked before though).
I tried unlocking within the newest firmware with the ASUS Unlock app, failed with the "Unknown error occured, this could be a network problem".
Then I decided to atleast fix me root so I downgraded to .30 (ICS) and RootDebugFS fixed my root access.
Still my unlocking fails.
My serial is still the same btw.
Click to expand...
Click to collapse
Thanks! I guess I'll downgrade to .30 as well, root it there and maybe attempt to unlock my bootloader.
I really wish to have CR again, so there's no option that this will not work (eventually)

Thats OK said:
Ah
If we can get you successfully unlocked then the flashing can begin.
Have you tried unlocking via the Asus unlock .apk?
Seem as tho some tab owners have had problems with the Asus unlock tool.
Click to expand...
Click to collapse
Shouldn't I first have root?
Or directly try to unlock the bootloader.

adelancker said:
Shouldn't I first have root?
Or directly try to unlock the bootloader.
Click to expand...
Click to collapse
My own experience included unlocking as a first step.
The reason was that I found it ultimately easier to install the CWM recovery thru ADB.
http://forum.xda-developers.com/showpost.php?p=32293050&postcount=1 <<<< The confusing guide is here.
After some study then trial we were successful!
Are you familiar with fastboot or opening a terminal (DOS like cmd window) on the PC?
ADB (Android Development Bridge) is a command prompt that will speak to the tablet thru a USB connection.
All of this is available with Androids platform tools.
I keep a tools folder on my PCs desktop so I don't have to search for it. (Platform tools can be downloaded)
I know all this is somewhat intimidating on first encounter...hopefully we can walk thru and get things up and loaded.

Thats OK said:
My own experience included unlocking as a first step.
The reason was that I found it ultimately easier to install the CWM recovery thru ADB.
http://forum.xda-developers.com/showpost.php?p=32293050&postcount=1 <<<< The confusing guide is here.
After some study then trial we were successful!
Are you familiar with fastboot or opening a terminal (DOS like cmd window) on the PC?
ADB (Android Development Bridge) is a command prompt that will speak to the tablet thru a USB connection.
All of this is available with Androids platform tools.
I keep a tools folder on my PCs desktop so I don't have to search for it. (Platform tools can be downloaded)
I know all this is somewhat intimidating on first encounter...hopefully we can walk thru and get things up and loaded.
Click to expand...
Click to collapse
Thanks for all the help!
It's not the first time I root (and/or) unlock a bootloader. It's just that now, those super easy root command methods don't work anymore. I have done completely manual rooting in the past, but I am not sure that will work either.
Besides, I got adb running before on my Infinity, but I'll make sure to downgrade to ICS first before doing anything else.
Here's what I am going to do:
1) downgrade to .30
2) try to root (with or without sparky's tool )
3) unlock bootloader (although I'm not sure if that'll work, judging from the comment of the Dutchman above)

I'll let you know in this thread if it worked or not.
My prediction: root will work, unlocking bootloader won't, since it's already been unlocked one and therefore my serial number is already in their database!

So i got my infinity like 2 weeks ago. The first thing i tried to do was to root it. I plugged in my device, installed drivers and checked unknown sources and usb debugging. I opened debugfs and tried to root my device but it suddenly closes. Whats likely to be the problem. And no i dont have asus sync installed.
P.S i returned my infinity on amazon as there was a hardware problem. Ill get the new one in a couple of days.
Thanks in advance.

Good luck with trying to get it unlocked (again)! If it doesn't work out in the end, you might want to drop Gary Key a line. Even if he is currently serving the USA himself, he might give you a pointer or a contact inside ASUS' support division. It's likely this is a "serial number in database" issue -- I'd like to believe that with some handiwork, this should be relatively simple issue to tackle, IF the engineers have access to that database at all. (With only Gary's answers to go on, I'd say ASUS HQ seems to keep its cards close to the chest.)
There's no way around the bootloader checking the staging partitions, right? Damn shame we can't just flash to it directly, ODIN style (which admittedly was not a perfect solution, but it is better than being locked out of your on device, essentially).

MartyHulskemper said:
Good luck with trying to get it unlocked (again)! If it doesn't work out in the end, you might want to drop Gary Key a line. Even if he is currently serving the USA himself, he might give you a pointer or a contact inside ASUS' support division. It's likely this is a "serial number in database" issue -- I'd like to believe that with some handiwork, this should be relatively simple issue to tackle, IF the engineers have access to that database at all. (With only Gary's answers to go on, I'd say ASUS HQ seems to keep its cards close to the chest.)
There's no way around the bootloader checking the staging partitions, right? Damn shame we can't just flash to it directly, ODIN style (which admittedly was not a perfect solution, but it is better than being locked out of your on device, essentially).
Click to expand...
Click to collapse
Thanks for the support!
It's a strange method, but it woudn't work otherwise:
I had to unlock the device (still on that very first stock JB rom).
Then, I flashed CWM through fastboot. Have a look here. However, do not forget: in this thread the OP referenced to an unofficial CWM. Go to the TF700 Android Development page and download the official CWM in stead.
After that I flashed a CWM-suitable SuperSU.zip (flashable) which made me have whereas it was impossible with any other method! (works through TWRP as well, for those that only have the unable to root problem )
Then, I flashed TWRP (but that's just a question of preferences, I guess) => This is no obligatory step of course!
There you go, for anyone who has/will have the same issues as me: follow these steps and let me know if it worked for you!
Have fun flashing Custom Roms/Kernels and/or recoveries again!

Thing with my situation is that I can't get your first step.
I tried to unlock the boot loader in the stock JB which the tablet was returned with.
I tried to unlock the boot loader in the stock .30 ICS rom
Every single time I get the "An unknown error has occured. This could be an network issue. Try again later" message ...
I haven't unlocked my tablet before RMA'ing so my serial shouldn't be "known" anyhow.
Though I do see a [90R-OK0QMB30000Y] TF700T MAIN_BD_._1G/T33/AS part at the replaced parts list on my Service Repair paper.
To me it looks like that a motherboard/mainboard, could that replacement be my issue?

DarkFire1985 said:
Thing with my situation is that I can't get your first step.
I tried to unlock the boot loader in the stock JB which the tablet was returned with.
I tried to unlock the boot loader in the stock .30 ICS rom
Every single time I get the "An unknown error has occured. This could be an network issue. Try again later" message ...
I haven't unlocked my tablet before RMA'ing so my serial shouldn't be "known" anyhow.
Though I do see a [90R-OK0QMB30000Y] TF700T MAIN_BD_._1G/T33/AS part at the replaced parts list on my Service Repair paper.
To me it looks like that a motherboard/mainboard, could that replacement be my issue?
Click to expand...
Click to collapse
Hmm... No idea what that could be.
I managed to unlock it, but that was after I reverted to ICS .30 (not obligatory, from what I understood ) I didn't use the Unlock Tool from the Asus website itself but an older (ex-official) Unlock Tool. (v7) I think it was.
I'll have a look and see if I can find it.

That might be the same as the one from the ASUS website but if you could provide me the file or md5 sum I can compare it.

adelancker said:
Thanks for the support!
It's a strange method, but it woudn't work otherwise:
I had to unlock the device (still on that very first stock JB rom).
Then, I flashed CWM through fastboot. Have a look here. However, do not forget: in this thread the OP referenced to an unofficial CWM. Go to the TF700 Android Development page and download the official CWM in stead.
After that I flashed a CWM-suitable SuperSU.zip (flashable) which made me have whereas it was impossible with any other method! (works through TWRP as well, for those that only have the unable to root problem )
Then, I flashed TWRP (but that's just a question of preferences, I guess) => This is no obligatory step of course!
There you go, for anyone who has/will have the same issues as me: follow these steps and let me know if it worked for you!
Have fun flashing Custom Roms/Kernels and/or recoveries again!
Click to expand...
Click to collapse
So glad to read that you have been successful.
...and do have fun flashing\updating\customizing!

DarkFire1985 said:
That might be the same as the one from the ASUS website but if you could provide me the file or md5 sum I can compare it.
Click to expand...
Click to collapse
The unlock tools provided by ASUS to unlock the TF201, TF300 and TF700 have been proven to be identical files (by checksum verification) --- no need to reinvent the wheel there.
The unlock step indeed is crucial -- and it depends on ASUS' database. If you can't get past that, there'll no flashing available in terms of recoveries (and therefore no custom ROMs either). Have you tried dropping Gary a line yet?

No not yet. Will do that.
Sent from my ASUS Transformer Pad TF700T using xda premium

DarkFire1985 said:
Thing with my situation is that I can't get your first step.
I tried to unlock the boot loader in the stock JB which the tablet was returned with.
I tried to unlock the boot loader in the stock .30 ICS rom
Every single time I get the "An unknown error has occured. This could be an network issue. Try again later" message ...
I haven't unlocked my tablet before RMA'ing so my serial shouldn't be "known" anyhow.
Though I do see a [90R-OK0QMB30000Y] TF700T MAIN_BD_._1G/T33/AS part at the replaced parts list on my Service Repair paper.
To me it looks like that a motherboard/mainboard, could that replacement be my issue?
Click to expand...
Click to collapse
Maybe you should have a look here. Seems like there were a couple of guys capable of unlocking it after all, and they were in the same situation as you.
I checked and the bootloader unlock tool was indeed an offial asus one. I downgraded before unlocking, but I saw you did too...
No idea what else I can do to help.

[Q] Do you have to unlock the bootloader to install a custom ROM?

I have just bought a TF300T to replace my awful Galaxy Tab 10.1 (which I never unlocked the bootloader for, even when flashing kernels).
I know a lot about rooting/flashing but just wanted to double check that if I ever wanted to change from stock I firstly need to unlock the bootloader?
Thanks, and I can't wait to get my hands on this amazing tablet.

yes

Why is it different for each device though (some require root some don't)?
Not that I mind having to unlock the bootloader, just curious.
Soon I will be able to use my new, shiny TF300T :good:

mr.fast said:
Why is it different for each device though (some require root some don't)?
Not that I mind having to unlock the bootloader, just curious.
Soon I will be able to use my new, shiny TF300T :good:
Click to expand...
Click to collapse
Just the latitude taken by each manufacturer.

tobdaryl said:
Just the latitude taken by each manufacturer.
Click to expand...
Click to collapse
Thanks. So it's different for every device.
What's the reason, I'm just curious to know to technical reasons why?

mr.fast said:
Thanks. So it's different for every device.
What's the reason, I'm just curious to know to technical reasons why?
Click to expand...
Click to collapse
because every time you play with the system there's a chance that you fsck up and if they let you take the tablet to their repair center and fix your mess for free it would cost them money.
so a lot of phone and tablet builders will let you play with it as much you want but only -after- they indelebly branded your device as "you want to play, you pay for your errors".

Yes I know.
I just wanted to know why different devices are flashed in different ways (some using NVFlash, some don't need the bootloader unlocking, some do etc.)?
Not that it's a problem, just interested.
Thanks for all the replies so far.

If you want ROMs, you need to unlock
mr.fast said:
Yes I know.
I just wanted to know why different devices are flashed in different ways (some using NVFlash, some don't need the bootloader unlocking, some do etc.)?
Not that it's a problem, just interested.
Thanks for all the replies so far.
Click to expand...
Click to collapse
From what I have read, you can install different ROMs by either ROOTING the device or using nvflash. Most users end up unlocking the device for alternate ROMS, because from what I have read, it was necessary. The bootloader decides how to boot the tablet and when its in a locked state, you cannot modify the boot sequence. Once the tablet is unlocked, you can make changes to the bootlooader and use AndroidRoot (part of theunbrickable method). I started the "unbrickable" method and last night and no matter what I did, I could not get the tablet into fastboot mode. To get into fastboot mode, you MUST unlock the tablet first. Once unlocked, you will have the "USB" icon during boot. When you select the USB icon, the tablet will be in fastboot mode.
Once you have that kind of access, it is best to make a backup at that point. If you go forward and install JB, your options will be limited. You still could install ROMS, but you will not be able to have an "unbrickable" device, for the moment.
Facts:
I have a TF300T
This is my first time modifing an android device

usbrelic said:
From what I have read, you can install different ROMs by either ROOTING the device or using nvflash. Most users end up unlocking the device for alternate ROMS, because from what I have read, it was necessary. The bootloader decides how to boot the tablet and when its in a locked state, you cannot modify the boot sequence. Once the tablet is unlocked, you can make changes to the bootlooader and use AndroidRoot (part of theunbrickable method). I started the "unbrickable" method and last night and no matter what I did, I could not get the tablet into fastboot mode. To get into fastboot mode, you MUST unlock the tablet first. Once unlocked, you will have the "USB" icon during boot. When you select the USB icon, the tablet will be in fastboot mode.
Once you have that kind of access, it is best to make a backup at that point. If you go forward and install JB, your options will be limited. You still could install ROMS, but you will not be able to have an "unbrickable" device, for the moment.
Facts:
I have a TF300T
This is my first time modifing an android device
Click to expand...
Click to collapse
Thanks a lot. That answered my question. I also install ROMs a lot, as it's one of the beauties of Android

mr.fast said:
Thanks a lot. That answered my question. I also install ROMs a lot, as it's one of the beauties of Android
Click to expand...
Click to collapse
Unlocking is required to install custom roms, nvflash, and recovery ( cwm or twrp) also to root if you are on JB. CWM has serious issues on this unit.

[Q]

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.

[Q] [NOT ASKING FOR HOWTO] A query about CM and rooting.

Hello XDA.
For a while now I've been thinking about rooting and adding a custom ROM to my phone. It seems like fun and I'd like to get involved.
Recently (as in I have no idea) Cyanogenmod released a new update that doesn't require the user to root their phone in order to install CM. However rooting allows full administrative access which is something that I'd like to have. Does CM root in the process of installation or does CM by itself have enough capability and features so you don't require rooting at all? If not, do people still root their phones before installing CM?
For starters I'm running Android version 4.1.2, if that will help in anyway possible.

taetiem said:
Hello XDA.
For a while now I've been thinking about rooting and adding a custom ROM to my phone. It seems like fun and I'd like to get involved.
Recently (as in I have no idea) Cyanogenmod released a new update that doesn't require the user to root their phone in order to install CM. However rooting allows full administrative access which is something that I'd like to have. Does CM root in the process of installation or does CM by itself have enough capability and features so you don't require rooting at all? If not, do people still root their phones before installing CM?
For starters I'm running Android version 4.1.2, if that will help in anyway possible.
Click to expand...
Click to collapse
Could you post a link to the source saying you don't need root to install cm? You can't actually post a link because you're brand new, but post the url anyway.
CM in itself does not root the device. The process of rooting is simply granting administrative permission as you already mentioned. It has root managing applications (such as supersu) installed, and a lot of its built in features require root access. I can't think of any instance where you could install the rom without root permission because it needs to change specific files to run, such as the kernel and system partition. This by default can't be changed without rooting the device.
Rooting is very easy and has to be done first, then you have to unlock the bootloader, then you can install custom roms. As long as you aren't on the 4.3 update.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
Could you post a link to the source saying you don't need root to install cm? You can't actually post a link because you're brand new, but post the url anyway.
CM in itself does not root the device. The process of rooting is simply granting administrative permission as you already mentioned. It has root managing applications (such as supersu) installed, and a lot of its built in features require root access. I can't think of any instance where you could install the rom without root permission because it needs to change specific files to run, such as the kernel and system partition. This by default can't be changed without rooting the device.
Rooting is very easy and has to be done first, then you have to unlock the bootloader, then you can install custom roms. As long as you aren't on the 4.3 update.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
It's on the wiki under "/w/CyanogenMod_Installer"
Code:
Do I need to root my phone before installing?
No. You can have a rooted phone, or not. The installer doesn't care. However, to be in a supported configuration, you need to be running a stock ROM.

taetiem said:
It's on the wiki under "/w/CyanogenMod_Installer"
Code:
Do I need to root my phone before installing?
No. You can have a rooted phone, or not. The installer doesn't care. However, to be in a supported configuration, you need to be running a stock ROM.
Click to expand...
Click to collapse
OK, so no, this will not work on our device. Specifically because we have a locked bootloader.
A lot of the coding in the cyanogenmod wiki is extremely confusing. Even doing something as simple as installing the rom written on that website looks very unnecessary to me. There are much easier ways to do it that don't involve such complicated processes, with such potential to brick a device.
I feel like a lot of the developers know how to use heimdall which can write to any device. Our device can use Odin though which is much more user friendly. When they write guides, they write for many devices, and they're unaware of simpler methods on each phone.
In a nutshell, I'd follow guides here on xda on how to root and install custom roms. Just make sure to follow the correct guides for your baseband and you should be good to go. Once you root and unlock the bootloader, you can install any custom rom you want simply by flashing in recovery.
Sent from my SCH-I535 using Tapatalk 2

taetiem said:
It's on the wiki under "/w/CyanogenMod_Installer"
Code:
Do I need to root my phone before installing?
No. You can have a rooted phone, or not. The installer doesn't care. However, to be in a supported configuration, you need to be running a stock ROM.
Click to expand...
Click to collapse
I agreed with Badusername, to be safe you should just stay within Verizon S3 thread and here is the info how to root/unlock 4.1.2 bootloader, install custom recovery then flash custom rom http://forum.xda-developers.com/showthread.php?t=2046439