Database Info

[Q] how to update rooted Xoom to 3.1 or 3.2

dears,
i have rooted 3G Xoom (MZ601).. 3.0.1
now i want to update it to 3.1 or 3.2
and i want to activate the US market ..
please, any one can guide me to do it ..

Simplest way i know.
1. Relock your zoom and go back to stock:
http://forums.androidcentral.com/xo...stboot-official-system-images.html#post708799
2. Update through the system update on your xoom.
3. Once you get up to 3.2 unlock and reroot your xoom:
http://forum.xda-developers.com/showthread.php?t=1170760
+ this way now you can reset it back to stock completely if you ever need too. Step by step guides are very easy to follow. Mostly copy and paste commands into notepad if your lazy like me. The whole process takes maybe 20 minutes.

is3od said:
dears,
i have rooted 3G Xoom (MZ601).. 3.0.1
now i want to update it to 3.1 or 3.2
and i want to activate the US market ..
please, any one can guide me to do it ..
Click to expand...
Click to collapse
Hi ,
I think you can go directly from 3.01 to 3.2 using this guide:
http://forum.xda-developers.com/showthread.php?t=1183416
If you don't already have ClockworkMod recovery v3.2.0.0 R4c installed, pay attention to post #7.
Good luck!

incase you dont have sdk installed put all files in a folder on your C:/ directory with a name you can find. Youll need these in addition to be able to use adb on your computer File name: SDK ADB.zip File size: 359.93 KB put them all in a folder called rootxoom or something.

prowlex said:
1. Relock your zoom and go back to stock:
http://forums.androidcentral.com/xo...stboot-official-system-images.html#post708799
2. Update through the system update on your xoom.
3. Once you get up to 3.2 unlock and reroot your xoom:
http://forum.xda-developers.com/showthread.php?t=1170760
+ this way now you can reset it back to stock completely if you ever need too. Step by step guides are very easy to follow. Mostly copy and paste commands into notepad if your lazy like me. The whole process takes maybe 20 minutes.
Click to expand...
Click to collapse
His Xoom is 3G there is no OTA update to 3.2 for 3G.
I really would not relock and go back to stock. He's rooted and that's more than half the battle.
is3od, the method I posted is for non-US Xooms as long as they are rooted.

i'll try it
prowlex said:
1. Relock your zoom and go back to stock:
http://forums.androidcentral.com/xo...stboot-official-system-images.html#post708799
2. Update through the system update on your xoom.
3. Once you get up to 3.2 unlock and reroot your xoom:
http://forum.xda-developers.com/showthread.php?t=1170760
+ this way now you can reset it back to stock completely if you ever need too. Step by step guides are very easy to follow. Mostly copy and paste commands into notepad if your lazy like me. The whole process takes maybe 20 minutes.
Click to expand...
Click to collapse
thank you for your help... today i'll try it and will inform you about the result.

Dear friends
Could you please confirm that above tutorial can be applied for 3G version of xoom?
I see some of guide with noted that applying for wifi version only.
Regards,

okantomi said:
Hi ,
I think you can go directly from 3.01 to 3.2 using this guide:
http://forum.xda-developers.com/showthread.php?t=1183416
If you don't already have ClockworkMod recovery v3.2.0.0 R4c installed, pay attention to post #7.
Good luck!
Click to expand...
Click to collapse
first i will relock my xoon then i'll update it ..
thank you,

prowlex said:
incase you dont have sdk installed put all files in a folder on your C:/ directory with a name you can find. Youll need these in addition to be able to use adb on your computer put them all in a folder called rootxoom or something.
Click to expand...
Click to collapse
ok
thanks...

k66473 said:
Dear friends
Could you please confirm that above tutorial can be applied for 3G version of xoom?
I see some of guide with noted that applying for wifi version only.
Regards,
Click to expand...
Click to collapse
it should be, because my Q is for 3G Xoom.

is3od said:
it should be, because my Q is for 3G Xoom.
Click to expand...
Click to collapse
You have ignored my posts which are for non-US 3G Xoom. Pleease check them again. I was not the one to tell you to go back to stock, unroot and relock. Please don't do that...no need.
Just try to follow the guide I posted in #3. Good luck.

thanks a lot
okantomi said:
You have ignored my posts which are for non-US 3G Xoom. Pleease check them again. I was not the one to tell you to go back to stock, unroot and relock. Please don't do that...no need.
Just try to follow the guide I posted in #3. Good luck.
Click to expand...
Click to collapse
I really appreciate your help .. thanks a lot ..

adb devices returns no devices
I have followed the tutorial after reading through it several time to unlock and root stock xoom 3.2. when i get to the adb devices command it returns me to the prompt with no devices returned or shown. i have android sdk windows in root of C:. i have rootboot.img, superuser.apk & su binary in a xoom folder in my downloads folder. i open the cmd in the download folder wherein resides rootboot.img, superuser.apk & su binary and type adb devices and nothing. i can see the xoom in explorer so i assume the usb drivers are there. i do have a yellow flag in other devices in device manager-other devices that says MZ604. but i can find no drivers anywhere for it though i have scoured the web for 2 days. i am at a loss as i have tried to perform this root for 2 days using all of my adb noob skills, but have had no luck as of yet. any suggestions? win7, stock xoom 3.2 wifi, pretty computer savvy except for adb
Thanks for any help as i only have 4 days of return left in case of brickage, which i am not so sure i would do inasmuch as it would be my fault...

big flamingo said:
I have followed the tutorial after reading through it several time to unlock and root stock xoom 3.2. when i get to the adb devices command it returns me to the prompt with no devices returned or shown. i have android sdk windows in root of C:. i have rootboot.img, superuser.apk & su binary in a xoom folder in my downloads folder. i open the cmd in the download folder wherein resides rootboot.img, superuser.apk & su binary and type adb devices and nothing. i can see the xoom in explorer so i assume the usb drivers are there. i do have a yellow flag in other devices in device manager-other devices that says MZ604. but i can find no drivers anywhere for it though i have scoured the web for 2 days. i am at a loss as i have tried to perform this root for 2 days using all of my adb noob skills, but have had no luck as of yet. any suggestions? win7, stock xoom 3.2 wifi, pretty computer savvy except for adb
Thanks for any help as i only have 4 days of return left in case of brickage, which i am not so sure i would do inasmuch as it would be my fault...
Click to expand...
Click to collapse
Make sure USB Debugging is checked under Settings/Applications/Development. If it is checked, then there is something wrong with your drivers.

big flamingo said:
I have followed the tutorial after reading through it several time to unlock and root stock xoom 3.2. when i get to the adb devices command it returns me to the prompt with no devices returned or shown. i have android sdk windows in root of C:. i have rootboot.img, superuser.apk & su binary in a xoom folder in my downloads folder. i open the cmd in the download folder wherein resides rootboot.img, superuser.apk & su binary and type adb devices and nothing. i can see the xoom in explorer so i assume the usb drivers are there. i do have a yellow flag in other devices in device manager-other devices that says MZ604. but i can find no drivers anywhere for it though i have scoured the web for 2 days. i am at a loss as i have tried to perform this root for 2 days using all of my adb noob skills, but have had no luck as of yet. any suggestions? win7, stock xoom 3.2 wifi, pretty computer savvy except for adb
Thanks for any help as i only have 4 days of return left in case of brickage, which i am not so sure i would do inasmuch as it would be my fault...
Click to expand...
Click to collapse
Check the thread you started...people have answered there.

okantomi said:
Hi ,
I think you can go directly from 3.01 to 3.2 using this guide:
http://forum.xda-developers.com/showthread.php?t=1183416
If you don't already have ClockworkMod recovery v3.2.0.0 R4c installed, pay attention to post #7.
Good luck!
Click to expand...
Click to collapse
I'd like to do the same as OP, update a rooted stock 3.0.1 euro 3G to 3.2 - I've already come across the thread you link to, but there's something I don't get.
pienut (user whose post you linked to) is saying that he went from 3.0.1 to 3.2, but in step 3 he writes:
Step 3 - Install 3.2 EURO rom:
Just copied the Euro 3.2 update from this post to my SD Card and flashed it from recovery.
Just to be sure, I did a full wipe after flashing.
Click to expand...
Click to collapse
Am I missing something, or is the SD card not disabled in 3.0.1? I know it is for me, afaik it only started working with 3.1 and up. I can't wrap my mind around going from 3.0.1 -> 3.2 using the SD card method, and yet it's mentioned in quite a few more threads and posts.
Ideally, I'd like to update to the Xoom ROM 2.1 Hammerhead (http://forum.xda-developers.com/showthread.php?t=1203635), but in those instructions, too, step 2 says
Download the 2.1 rom zip file and place it on your external sdcard
Click to expand...
Click to collapse
How, if I can't access it in the first place? Should I install 3.1 first before I install Hammerhead? If so, do you know about any step-by-step I can follow?
Sorry to jump in on this thread like this... it was the closest I could find related to my problem after hours of searching and reading. Thanks.

Alright, I figured it out on my own... I took a leap of faith and installed the ClockworkMod Recovery 3.2.0.0 (R4c), booted to recovery, and in there it's possible to mount the SD card under mounts and storage > mount usb storage. It will then appear in Windows as an external drive (as usual).
Yay, learned something new today. Now on to the next battle

[Q] where to begin root and roms?

hello...
i have an eee pad transformer TF101...
with stock rom on it...
here is the about tablet in setting...
Android version : 3.2.1
kernel version : 2.6.36.3-00001-g9a21fc1 [email protected]#1
Build number : HTK75.WW_epad-8.6.5.21-20111216
i want to root it and install custom rom for it...i know that because it's .21 it's hard to root it...and some method doesn't work...
so...i want to know which method and way is the best and the easiest way to root my tablet???
i read this method in this topic...
but i didn't under stand anything...
i don't understand nothing...
i know some of those thing were commands...but i don't where should i write them and other things...
so if somebody could just help me and give me the starting point and the ending point i'll appreciate...
(i don't care about officials update.... and keeping my data on tablet...i just want to root it...and install custom rom...if the root is permanent it would be better...)(i have read other Q thread....but don't get anything...)

NachoRoot should work for you.
First thing you need to do is have ADB set up on your PC.
This is a good thread to see how that's done.
http://forum.xda-developers.com/showthread.php?t=1071584&highlight=adb
Once you have that done, download the files in the NachoRoot thread, put it in the platform-tools folder inside the Android/android-sdk folder.
Open command windows and type in the commands. (You could copy/paste line per line into the cmd window)
Alternatively you can try these different methods:
GUI one click root
http://forum.xda-developers.com/showthread.php?t=1445882
ViperMod
http://forum.xda-developers.com/showthread.php?t=1427125

And next step is install CWM. See here
Remember no ASUS OTA update will happen after installing CWM.
But if you continue with other rom this is not a problem (or use OTA update with using CWM, see developers forum).

[Q] Regarding what all are possible in an SBKv2 eeePad Transformer

I have an eeePad TF101 (no G) and its serial number starts with B80, so I guess that makes it an SBKv2. My questions are whether the following are possible and what some terms mean.
1) What does SBKv2 mean? Why is nvflash incompatible with it?
2) What is the homepage of nvflash? Is there any other flasher that is compatible with SBKv2?
3) Is it possible to install any custom rom?
4) I read it's possible to run Ubuntu with chroot after rooting. Will that make it slower? Is it possible to get a full linux bash terminal with the option to install stuff?
5) Will rooting give me complete system access? (I once had a Galaxy gt-i5510 which gave me 'permission denied' error even after rooting, for stuff like copying files to system folders running apps etc).
6) Is it possible to use a USB modem (ZTE MG478/AC8700, EvDO) using:
a) wvdial from chrooted linux and then use from android (I know it's crazy).
b) wvdial directly.
c) Any other method.
7) Will rooting cause any problems or 'side effects'?
Sorry if I asked questions that were already asked.

Uh...this is way too many questions to answer when all of the answers can be found by searching. This is your first lesson..you need to search. These are all common questions.

Ok i've only recently got a transformer but ill try answer these questions...If i've got something wrong feel free to correct me.
1) SBKv2 is the newer model of the transformer, Nflash isn't compatible because it runs on a newer bootloader.
2) I'm not sure...
3) Yes.
4) Yes you can run linux ubuntu, but only for the older model :/
5) Yes it will.
6) I'm not entirely sure, You'll have to wait for someone else to answer this
7) Probably not

1. the guy above is not quite right it is that the sbk (secure book key) is diferent and was leaked for the original rom but not the 2nd version
2. wait what? use cwm
3. yes
4. it runs a virtual immage vnc'd within android so ya it is slower
5. as long as you make the system r/w instead of r/o
6. maby try the usbethernet drivers
7. it will casue ota's to fail and you will not be able to purchase movies from the market
Every piece of information here is already here learn to search

mrevankyle said:
1. the guy above is not quite right it is that the sbk (secure book key) is diferent and was leaked for the original rom but not the 2nd version
2. wait what? use cwm
3. yes
4. it runs a virtual immage vnc'd within android so ya it is slower
5. as long as you make the system r/w instead of r/o
6. maby try the usbethernet drivers
7. it will casue ota's to fail and you will not be able to purchase movies from the market
Every piece of information here is already here learn to search
Click to expand...
Click to collapse
2) So custom roms work, dual booting doesn't?
4) But I will still get a full linux bash terminal with the option to install apps and all right?
5) How do you get r/w access? Is that the default mode in nachoroot?
6) Usb modem not ethernet!
7) Movies? What about everything else? OTA? That will be resolved if I use OTA Rootkeeper right? What about the updates from asus website?
I kinda did search. But I guess I'll search more next time....

phoenixv5 said:
2) So custom roms work, dual booting doesn't?
4) But I will still get a full linux bash terminal with the option to install apps and all right?
5) How do you get r/w access? Is that the default mode in nachoroot?
6) Usb modem not ethernet!
7) Movies? What about everything else? OTA? That will be resolved if I use OTA Rootkeeper right? What about the updates from asus website?
I kinda did search. But I guess I'll search more next time....
Click to expand...
Click to collapse
the only way to dual boot is nvflash ubuntu/andorid and that requires nvvflash so no you cannot dualboot
you should but be wary as it is ubuntu arm and not all apps are compatable
it is in the file manager you use ubt in consol you will have system access and if in root explorer you click read/write
i know you said usb. it may work by default not garenteed .you can increace the likleyhood of it working with the 3g dongle drivers and the usb internet drivers (Usb etherent)
it depends if you have a custom recovery installed (CWM) if you do not get cwm you need otarootkeeper and ota's will work if you do install cwm then you will not get the ota's installed

mrevankyle said:
you should but be wary as it is ubuntu arm and not all apps are compatable
it is in the file manager you use ubt in consol you will have system access and if in root explorer you click read/write
if you do install cwm then you will not get the ota's installed
Click to expand...
Click to collapse
Won't the installer (apt or synaptic) auto detect arm like it did in N900 and all?
What's ubt? Do you mean manually add r/w permission to all files?
What about update files downloaded directly from asus website? Will I still get market?

phoenixv5 said:
Won't the installer (apt or synaptic) auto detect arm like it did in N900 and all?
What's ubt? Do you mean manually add r/w permission to all files?
What about update files downloaded directly from asus website? Will I still get market?
Click to expand...
Click to collapse
i am not sure probably though
its a mistype i ment "but"
no in root explorer there is a buton at the top to change mount type it says "mounted as r/0" by default and there is a buton beside it to "Mount R/W"
they may work as they are the same files as the OTA's so it is the same case as the ota's.
Yes the market does not change besides the inability to purchase videos

So lemme summarize.
Nvflash doesn't work, CWM recovery does, so flashes using that also works.
OTA updates or (maybe) the ones downloaded won't work. But OTA's can be modified into ones that are recognized by cwm and retains root (with supercurio's script?).
Rooting without installing cwm doesn't interfere with OTAs.
Use OTA Rootkeeper to retain root after updates (not needed with cwm as cwm flashable stock upgrades are already rooted).
And root+cwm is undo-able.
Did I get all that right?

Please, before you ask any more questions, read THIS GUIDE;
Asus Transformer EPIC NOOB GUIDE
Almost every question you have asked is answered for you now. And probably a lot of future questions. And practice searching before posting new threads, most things you will find are already dealt with by now and the answers are just a search away no need to wait for people to answer you.

luna_c666 said:
Please, before you ask any more questions, read THIS GUIDE;
Asus Transformer EPIC NOOB GUIDE
Almost every question you have asked is answered for you now. And probably a lot of future questions. And practice searching before posting new threads, most things you will find are already dealt with by now and the answers are just a search away no need to wait for people to answer you.
Click to expand...
Click to collapse
I did. Right before posting my previous reply.
BTW thanks for the guide.
Edit: I guess that's it. Close / delete the thread!

[Q] custom rom for my tf300t ?

hi,
I'm afraid that installing a custom rom on my asus tf300 would break compatibility
with the keyboard dock. Also mine is azerty .
I'm looking for cyanogenmod in particular, what do you think ?
Also there are other consideration for a custom rom:
- my main motivation to install a custom is to get rid of the bloatware.
I just do not wish to spend time with every added apps to understand their purpose,
and they take space.
- ads. I've installed overcome rom in my previous tablet (unfortunately bricked),
and one thing I really liked, is how lot of ads in apps were filtered.
Too much ads popping from nowhere now , which discourage the use of "free" apps.
- if there's some built in mechanism to limit the risk of bricking that would be nice.
My previous tablet was bricked without any reason, perhaps because I didn't use the original charger.
- somehow all the updates that pop up frequently, nags me.
To summarize, I'm looking for a custom rom, that is compatible with my azerty keyboard dock of the tf300;
and preferably all the criteria mentioned above ( no bloat, blocked ads, anti bricking mechanism, less updates).
Thanks

extrabigmehdi said:
hi,
I'm afraid that installing a custom rom on my asus tf300 would break compatibility
with the keyboard dock. Also mine is azerty .
I'm looking for cyanogenmod in particular, what do you think ?
Also there are other consideration for a custom rom:
- my main motivation to install a custom is to get rid of the bloatware.
I just do not wish to spend time with every added apps to understand their purpose,
and they take space.
- ads. I've installed overcome rom in my previous tablet (unfortunately bricked),
and one thing I really liked, is how lot of ads in apps were filtered.
Too much ads popping from nowhere now , which discourage the use of "free" apps.
- if there's some built in mechanism to limit the risk of bricking that would be nice.
My previous tablet was bricked without any reason, perhaps because I didn't use the original charger.
- somehow all the updates that pop up frequently, nags me.
To summarize, I'm looking for a custom rom, that is compatible with my azerty keyboard dock of the tf300;
and preferably all the criteria mentioned above ( no bloat, blocked ads, anti bricking mechanism, less updates).
Thanks
Click to expand...
Click to collapse
Curious AZERTY Keyboard is french layout? But still ASUS Brand Keyboard Dock correct?

Lummers said:
Curious AZERTY Keyboard is french layout? But still ASUS Brand Keyboard Dock correct?
Click to expand...
Click to collapse
yes. With US keyboard the first letters you see in top left are QWERTY, while for french keyboard it' s AZERTY.
If I set improperly the local, I guess I'll get the Q letter when I type A on keyboard and so on.
I think the layout of keyboard was selected, with first run (choose you language , hour etc...).
My guess is that asus use a "standard rom" despite the different keyboards , but I'm not 100% sure.
Maybe cyanogenmod handle this ?
Annoying, with my samsung P1000 using a custom rom, was more straightforward.

Finally used CROMi-Xenogenesis mod.
It was harder than I thought, with silly unexpected problems from time to time.
For instance, you can't use the bootloader unlocker from asus, if you set the font size of system to max (try if you don't see why).
The dos shell that refused to change dir once in administartor mod , in order to use that fastboot thing ( weird, but worked after typing a drive letter ). Twrp that refused to mound the sd card even with fat32 system (I realized later I could reset while keeping the rom to install).
And finally , no f***** step by step manual, to install the custom rom.
Overcome was more newbie friendly.
No problem with locals, as already announced before by the author of rom.
Now it seems : less bloated, and I have ads blocked .
Will customize more later.

extrabigmehdi said:
Finally used CROMi-Xenogenesis mod.
It was harder than I thought, with silly unexpected problems from time to time.
For instance, you can't use the bootloader unlocker from asus, if you set the font size of system to max (try if you don't see why).
The dos shell that refused to change dir once in administartor mod , in order to use that fastboot thing ( weird, but worked after typing a drive letter ). Twrp that refused to mound the sd card even with fat32 system (I realized later I could reset while keeping the rom to install).
And finally , no f***** step by step manual, to install the custom rom.
Overcome was more newbie friendly.
No problem with locals, as already announced before by the author of rom.
Now it seems : less bloated, and I have ads blocked .
Will customize more later.
Click to expand...
Click to collapse
I'm using Comi-X a well, I didn't know you were looking for that I had a post earlier that I had great help from people on the board.
I'm using Hund's Kernel so I'm overclocking a little on that machine.
No more lag!! It's amazing how much faster it is with the rom.
Please let me know if you need a hand with anything, I'm still a noob but I'll try my best to help you out.

extrabigmehdi said:
Finally used CROMi-Xenogenesis mod.
It was harder than I thought, with silly unexpected problems from time to time.
For instance, you can't use the bootloader unlocker from asus, if you set the font size of system to max (try if you don't see why).
The dos shell that refused to change dir once in administartor mod , in order to use that fastboot thing ( weird, but worked after typing a drive letter ). Twrp that refused to mound the sd card even with fat32 system (I realized later I could reset while keeping the rom to install).
And finally , no f***** step by step manual, to install the custom rom.
Overcome was more newbie friendly.
No problem with locals, as already announced before by the author of rom.
Now it seems : less bloated, and I have ads blocked .
Will customize more later.
Click to expand...
Click to collapse
I would suggest doing the NvFlash for your tablet so it becomes unbrickable now that you have a custom ROM. Link in sig

cmendonc2 said:
I would suggest doing the NvFlash for your tablet so it becomes unbrickable now that you have a custom ROM. Link in sig
Click to expand...
Click to collapse
Unfortunately I just find this nvfash thing just too much confusing.
For miscellaneous reasons:
1) there's no "official" tutorial to restore bricked tablet with nvflash
2) I don't understand what nvflash (or the steps to create "nvflash backup files" ) will exactly change to my current install, if there's a risk of incompatibility/conflict, if I'll need to re-install twrp afterward. Would the bootloader be changed ? Its there a nvflash bootloader ? Unclear.
3) Sorry the part " you will need to flash the AndroidRoot patched custom bootloader" is just Chinese to me.
4) If I install in future , a new rom based on a new android version (and I guess a new bootloader ?) , would I loose the ability to use nvflash ?
5) which file do I need to keep exactly, and where. Let's say I want to save space, do I need to keep blob files etc inside tablet ?
6) ironically there's a risk of bricking my tablet while following this "anti-brick" tool, and with the not so clear tutorial, I have reasons to hesitate.

extrabigmehdi said:
Unfortunately I just find this nvfash thing just too much confusing.
For miscellaneous reasons:
1) there's no "official" tutorial to restore bricked tablet with nvflash
2) I don't understand what nvflash (or the steps to create "nvflash backup files" ) will exactly change to my current install, if there's a risk of incompatibility/conflict, if I'll need to re-install twrp afterward. Would the bootloader be changed ? Its there a nvflash bootloader ? Unclear.
3) Sorry the part " you will need to flash the AndroidRoot patched custom bootloader" is just Chinese to me.
4) If I install in future , a new rom based on a new android version (and I guess a new bootloader ?) , would I loose the ability to use nvflash ?
5) which file do I need to keep exactly, and where. Let's say I want to save space, do I need to keep blob files etc inside tablet ?
6) ironically there's a risk of bricking my tablet while following this "anti-brick" tool, and with the not so clear tutorial, I have reasons to hesitate.
Click to expand...
Click to collapse
1.) Google NvFlash Commands, or read original NvFlash thread, or ask a dev at AndroidRoot
2.)NvFlash files are backups. It doesnt change the BL. The BL just needs to be jellybean
3.) NvFlash is done using a custom version of CWM recovery, so it runs all the scripts for u. You just have to press a few buttons
4.) If you've done NvFlash once, it doesnt matter what you do to your tablet like changing BL
5.) The blob file is about 2 MB, the other backups that are recommended are about 10MB. You wont run out of space. The files that need to be saved are listed in the guide, as well as the way to save them
6.) If you follow the guide down to the word, there is no problem. Unlocking your bootloader and and flashing a rom has the same risk of bricking. If you have any questions ALWAYS ask before proceeding.

cmendonc2 said:
1.) Google NvFlash Commands, or read original NvFlash thread, or ask a dev at AndroidRoot
2.)NvFlash files are backups. It doesnt change the BL. The BL just needs to be jellybean
3.) NvFlash is done using a custom version of CWM recovery, so it runs all the scripts for u. You just have to press a few buttons
4.) If you've done NvFlash once, it doesnt matter what you do to your tablet like changing BL
5.) The blob file is about 2 MB, the other backups that are recommended are about 10MB. You wont run out of space. The files that need to be saved are listed in the guide, as well as the way to save them
6.) If you follow the guide down to the word, there is no problem. Unlocking your bootloader and and flashing a rom has the same risk of bricking. If you have any questions ALWAYS ask before proceeding.
Click to expand...
Click to collapse
I was reading about the NvFlash as it was just recently released.
Couple of questions (sorry if hijacked this thread)
Does it work with TWRP? Or will I have to use CWM?
I've read the NvFlash Guide but I'm still unsure of the necessities.

Lummers said:
I was reading about the NvFlash as it was just recently released.
Couple of questions (sorry if hijacked this thread)
Does it work with TWRP? Or will I have to use CWM?
I've read the NvFlash Guide but I'm still unsure of the necessities.
Click to expand...
Click to collapse
So to get TWRP, u flash a custom CWM, but after you have your backups and blobs, you can flash back TWRP

cmendonc2 said:
1.) Google NvFlash Commands, or read original NvFlash thread, or ask a dev at AndroidRoot
2.)NvFlash files are backups. It doesnt change the BL. The BL just needs to be jellybean
3.) NvFlash is done using a custom version of CWM recovery, so it runs all the scripts for u. You just have to press a few buttons
4.) If you've done NvFlash once, it doesnt matter what you do to your tablet like changing BL
5.) The blob file is about 2 MB, the other backups that are recommended are about 10MB. You wont run out of space. The files that need to be saved are listed in the guide, as well as the way to save them
6.) If you follow the guide down to the word, there is no problem. Unlocking your bootloader and and flashing a rom has the same risk of bricking. If you have any questions ALWAYS ask before proceeding.
Click to expand...
Click to collapse
All right , basically you replace the "recovery tool" with one custom that allows to save the nvflash files (how I interpret it).
I tried to follow the steps but not without problems.
I tried to install "Universal Naked Driver" , but it didn't work.
I uninstalled the asus official driver first , but the universal naked driver wasn't recognized.
Reading some discussions, suggested that it doesn't work with win 7 x64 anyways.
So I re-installed again the "ASUS Pad PC Suite" in order to get the driver again, but also all the stuff I don't care , such like asus clouds and asus sync (if I try to skip, the setup freeze).
Then I followed the step for nvflash, and I got a problem at step where I type "adb pull /data/media/AndroidRoot " . I got the error "device not recognized" .
I retyped again the menu command to generate the blob ; thinking it might help, and all I got is a new wifi error.
So I searched a bit on the web, some discussion suggesting I do the adb command in regular android mode, and after enabling "debug mode".
But enabling the debug mode is not anymore straightforward, you must do some kind of magical trick, where you tap seven time the version build :crying:. I'm happy I didn't install the java sdk, some people suggest to install it in order to use the adb thing :silly:.
So I finally got 8 files .
Reboot in "APX mode" , I get this time the error in windows that the driver is missing. This time I used "universal naked driver " for this,
driver recognized. Reboot of windows, just in case.
Finally I got a frightening black screen, making you think that the tablet might be bricked (they say "blank screen" in tutorial , but I was hoping a white background ).
But fortunately I ended all the nvflash steps successfully.
And then I reflashed TWRP.

extrabigmehdi said:
All right , basically you replace the "recovery tool" with one custom that allows to save the nvflash files (how I interpret it).
I tried to follow the steps but not without problems.
I tried to install "Universal Naked Driver" , but it didn't work.
I uninstalled the asus official driver first , but the universal naked driver wasn't recognized.
Reading some discussions, suggested that it doesn't work with win 7 x64 anyways.
So I re-installed again the "ASUS Pad PC Suite" in order to get the driver again, but also all the stuff I don't care , such like asus clouds and asus sync (if I try to skip, the setup freeze).
Then I followed the step for nvflash, and I got a problem at step where I type "adb pull /data/media/AndroidRoot " . I got the error "device not recognized" .
I retyped again the menu command to generate the blob ; thinking it might help, and all I got is a new wifi error.
So I searched a bit on the web, some discussion suggesting I do the adb command in regular android mode, and after enabling "debug mode".
But enabling the debug mode is not anymore straightforward, you must do some kind of magical trick, where you tap seven time the version build :crying:. I'm happy I didn't install the java sdk, some people suggest to install it in order to use the adb thing :silly:.
So I finally got 8 files .
Reboot in "APX mode" , I get this time the error in windows that the driver is missing. This time I used "universal naked driver " for this,
driver recognized. Reboot of windows, just in case.
Finally I got a frightening black screen, making you think that the tablet might be bricked (they say "blank screen" in tutorial , but I was hoping a white background ).
But fortunately I ended all the nvflash steps successfully.
And then I reflashed TWRP.
Click to expand...
Click to collapse
Woah....
Totally sounds like a little bit of a challenge for people that are new to the android scene..
I'm going to give this a whirl this week sometime and get it backed up.

Im also looking into NVflash, my bootloader is unlocked but I have yet to root and pick a rom. I am also looking for something that will work with a keyboad, I have yet to buy one but my birthday is coming up.

[Q] Looking for root basics, list etc.

As the title states, I need help with understanding the basic steps on rooting the ASUS TF300.
I am not a programmer, I do not know the lingo or terms, and searching on the site has yielded very confusing results.
Basic steps?
1. Unlock boot loader - Why? What does this do?
2. TWRP? I have no clue, but I see references all over the place
3. Custom Recovery - What does this do? Do I need it?
4. Kernel - What is this?
5. ROM - What is this?
6. Install Super SU or SuperUser (what's the difference?, what does this do?
7. Install a root check app (to check if rooted I presume)
8. Install some form of file explorer (I have Fx File Explorer) and backup/control app (I have Titanium backup)- both paid forms
9. De-bloat with caution!
Where does the OEM firmware/software fit in this scheme? Does it exist as a backup or is it over-written? Do I have a choice?
As you can guess I'm lost. Reading threads after searching for "root TF300" or even the guides or the very good index, I have more questions than answers. How does one know what to do if the acronyms used are cryptic? (example TWRP~ what does this even stand for?)
I believe that not all steps are required, but I also believe the order I do things is important, and I'm concerned about bricking my TF300 by doing something wrong. I also don't want to assume that this is the same for every device or phones. (what steps work for a phone may not be the best for a tablet)
All I want to do is root and remove bloat. After I get this, I may consider upgrading the OS (kernel? Rom?) to something better.
Any links would be greatly appreciated. Please just bear in mind I'm so noob to this I don't know a ROM from a Kernel yet. (When I search, all answers are overly complicated developer definitions.)
Thank you!

Here is a "simple Step by Step" with notes in red as to how my mind tries to grasp this:
1. Upgrade your tablet to the desired firmware: 4.1 or 4.2 I assume they mean any OTA upgrade~ my tablet is current with JB 4.2.1 and I do not believe ASUS will plan on upgrading this anytime soon)
2. Be sure the correct drivers for your tablet are installed!! Installed where? on my PC? How do I know what are the correct drivers? Where can I get them?
3. Download the updated rooting toolkit: Updated Motochopper rooting toolkit -OK, I can do this!
4. Download TWRP for your firmware version:
- 4.1: TWRP 2.5.0.0 for Jellyeban 4.1
- 4.2: TWRP 2.5.0.0 for Jellybean 4.2 -This makes sense to me, as I am jellybean 4.2.1
5. Rename the downloaded TWRP blob file to twrp.blob and copy it to the root of your sdcard -what is a blob file? Is there a size requirement for the SD card? Does the SD have to be blank?
5. Extract the rooting toolkit to a place you like. -I assume the above mentioned motochopper? Does this answer my question above about the SD card?
== Part 2 - Rooting ==
1. Open up the folder where you placed the rooting toolkit. - with what program? A simple file explorer I assume?
2. Open the run file and follow the instructions -I hope there aren't any cryptic/over my head choices to make!
After installation the tablet should reboot and you should be rooted. -Does this install all the SuperSu stuff or is this it? What about customer recovery? Can I go back? what are the limitations of doing it this way assuming it works....
And this is just PART of the process!

I'll answer in logical order:
broderp said:
5. ROM - What is this?
Click to expand...
Click to collapse
That's the Operating System that's running on your tablet, i.e. what is called Lollipop or KitKat, or even further what makes the difference between Android and iOS.
Your ROM may come with some preinstalled apps, but with some ROMs they are separate (i.e. the Google apps).
broderp said:
1. Unlock boot loader - Why? What does this do?
2. TWRP? I have no clue, but I see references all over the place
3. Custom Recovery - What does this do? Do I need it?
Click to expand...
Click to collapse
On your ASUS tablet you can, by default, only install ASUS supplied ROMs (i.e. updates).
In order to install a new ROM you need to unlock your device. You do that by unlocking the boot loader. Once you have unlocked the boot loader, you can install a custom recovery, such as TWRP (there are many custom recoveries, but for your device TWRP is recommended).
Once you have a custom recovery, installing a new ROM, or rooting your device, becomes a lot easier. No need to type in commands, but you can now use touch.
broderp said:
4. Kernel - What is this?
Click to expand...
Click to collapse
Your kernel is the most important part of your ROM. It's the software between apps and your actual hardware, the lowest level actually. The kernel determines if you can talk to certain pieces of hardware or not. If the kernel does not support certain hardware, that's it, you can't use it.
When your tablet boots up, the first thing it loads its the kernel, the kernel loads all other programs. Another responsibility of the kernel is to allow you to run multiple programs at once.
broderp said:
6. Install Super SU or SuperUser (what's the difference?, what does this do?
Click to expand...
Click to collapse
They allow you to execute programs with root privileges (i.e. no limit to privileges, can do anything), but also give you some protection so malicious programs cannot become root: you have to give explicit permissions for every app.
broderp said:
7. Install a root check app (to check if rooted I presume)
Click to expand...
Click to collapse
Yes.
broderp said:
8. Install some form of file explorer (I have Fx File Explorer) and backup/control app (I have Titanium backup)- both paid forms
Click to expand...
Click to collapse
Optional, pick whatever you like.
broderp said:
9. De-bloat with caution!
Click to expand...
Click to collapse
No clue!
broderp said:
Where does the OEM firmware/software fit in this scheme? Does it exist as a backup or is it over-written? Do I have a choice?
Click to expand...
Click to collapse
Firmware often is part of the hardware: it gets written to special memory, and "sticks", i.e. when you reboot it stays there. If you get a T300 you should let ASUS run all the updates as it installs new firmware. Some firmware gets written when your device boots, meaning the special program, the kernel, starts, and at some point writes updated firmware to hardware.
So firmware is software that makes hardware a bit more flexible: else everything is hard-wired, if there's a problem you can't fix it, but with software you sometimes can fix a hardware issue.
Hope this helps!

First, to unlock the bootloader, you need to go the asus site and register your tablet. Then you can download the unlock app from the asus site as well. Next, move the unlock app from where ever it downloaded on your pc to your tablet. You can put it on the tablet RAM or on an SD card, it doesn't matter. On your tablet, go into the settings menu. under security(I think it is there) and enable 'unknown sources' for app installation. I haven't had the stock ROM for so long, I can't recall where that option is. Run the unlock app. It may take a couple times to unlock the tablet. WARNING! this will void your warrenty! So if your tablet is relatively new, think hard about this. Once your tablet is unlocked, then you can worry about TWRP and ROMS
TWRP is a custom recovery. It is officially Team Win Recovery Project, hence TWRP. It is a program that will allow you to back up your tablet before you make changes(very important in case you screw something up) and a host of other things including flashing custom ROMs. If you go into the LP 5.1 for the TF300 thread in the development area, it will have all the links for stuff like the current TWRP, Gapps packages and the newest LP ROM. It is great for our tablets and really wakes it up. Oh yeah, the TWRP site will have instructions for flashing TWRP on your newly unlocked tablet as well.
All this seems very intimidating for noobs, I was one about 4 months ago. I now feel sort of not-noobish. To install TWRP you will need either Fastboot or ADB on your computer. Google Fastboot or ADB and you should find plenty of answers. There are also 'lite' versions of Fastboot out there too. If you are on Windows 8 or 8.1 you will need one of those. Windows doesn't like fastboot or ADB for some reason
HTH