[Q] Regarding what all are possible in an SBKv2 eeePad Transformer - Eee Pad Transformer Q&A, Help & Troubleshooting

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!

Related

[Q] What should I DO

Hey all
So i had my transformer for a while no, since the summer.
my version is 8.4.4.5.2 i never pushed an update couse i knew that eventually i will root the transformer
What kind of root methods do i have in order to root it? do i need t oupgrade the version or the stock?
my kernal version is 2.6.36.3 and it still on 3.1
and then what kind of rom should i install?
Thank you all for answering the question
Just look in the development forum and all your questions will be answered within 3 to 15 minutes.
Sent from my Transformer Prime TF201 using Tapatalk
Becoming root on most recent version is still possible with Nachoroot/Vipermod.
No reason at this moment not to update because of root.
If you have serialnumber <B70 you can always become root by using nvflash.
the thing is what i see in the development is for stock roms with version 8.6 and others
i don't find any reference for the 8.4
so i am confused for what i need to do
a
oh and my serial begin with B60
I saw the Razorclaw and Nachoroot methods. but as i mentioned they talk about 8.6 versions.
should i use the nvflash then?
xenocid3r said:
the thing is what i see in the development is for stock roms with version 8.6 and others
i don't find any reference for the 8.4
so i am confused for what i need to do
a
oh and my serial begin with B60
I saw the Razorclaw and Nachoroot methods. but as i mentioned they talk about 8.6 versions.
should i use the nvflash then?
Click to expand...
Click to collapse
NVFlash will wipe all of your data but it is fine to use other than that. otehrwise just upgrade to the .21 or .19 (not sure which) and use nachoroot
If you want to root, install CWM and install ROMs without having to connect to a PC, upgrade to the 8.6.5.19 or 8.6.6.19 (depending on if you are TF101 or TF101G respectively).
Download Razorclaw apk (google it, it comes right up)
Download RecoveryInstaller apk (can be found on this site with a quick search)
Download Titanium Backup from the market.
Download whatever ROM you wish to flash (I suggest go with Krakd or Revolver) and put that file on your external SD card in the root.
Install Razorclaw, click "Root me nao!"
MAKE A BACKUP with Titanum Backup (launch, give it superuser permission and unknown source permission, press settings key and choose 'batch', find "RUN Backup all apps + data" and run that, it will create a folder called 'titanum backup' on your TF internal, leave it there it will be fine.)
Launch "RecoveryInstaller" and click "Install Recovery"
Now you are rooted with CWM recovery, although it is an older version, once rooted and CWM'd it is easy to flash the newer recovery (called Rogue XM) and now you can flash your ROM of choice, reinstall titanium backup and run "batch"-"RUN Restore all apps + data"
IMHO, I would rather be able to flash and mod from the device itself rather than through ADB from a PC..then you have to deal with drivers, pc software, etc. and I don't know about you but my PC isn't even as fast as my TF. So using it is a 'last resort'.
I have used the method above more times than I could count. And, honestly, I think it is more user-friendly for noobs.
Hey thanks for the replies
is there any big difference between rooting through the adb or using an app?
lets assume my PC is fast enough to do all these things
I m just curiud to know that?
luna_c666 said:
If you want to root, install CWM and install ROMs without having to connect to a PC, upgrade to the 8.6.5.19 or 8.6.6.19 (depending on if you are TF101 or TF101G respectively).
Download Razorclaw apk (google it, it comes right up)
Download RecoveryInstaller apk (can be found on this site with a quick search)
Download Titanium Backup from the market.
Download whatever ROM you wish to flash (I suggest go with Krakd or Revolver) and put that file on your external SD card in the root.
Install Razorclaw, click "Root me nao!"
MAKE A BACKUP with Titanum Backup (launch, give it superuser permission and unknown source permission, press settings key and choose 'batch', find "RUN Backup all apps + data" and run that, it will create a folder called 'titanum backup' on your TF internal, leave it there it will be fine.)
Launch "RecoveryInstaller" and click "Install Recovery"
Now you are rooted with CWM recovery, although it is an older version, once rooted and CWM'd it is easy to flash the newer recovery (called Rogue XM) and now you can flash your ROM of choice, reinstall titanium backup and run "batch"-"RUN Restore all apps + data"
IMHO, I would rather be able to flash and mod from the device itself rather than through ADB from a PC..then you have to deal with drivers, pc software, etc. and I don't know about you but my PC isn't even as fast as my TF. So using it is a 'last resort'.
I have used the method above more times than I could count. And, honestly, I think it is more user-friendly for noobs.
Click to expand...
Click to collapse
these are some really good instructions for a new user.. .just use these instructions and if you need further help with each step look up each step how its done in the development sections.... good luck
Sent from my Revolver Powered Asus Transformer

How to Root and upgrade from ice cream sandwich to jelly bean??

Dear all,
I received an Asus Transformer Tf101 for Christmas, 16gb internal RAM,
OS 4.0.3 (ice cream). Can someone please guide me how to enable root and upgrade the os?
I tried to rooted with Sparkyroot but, kept getting " exploit not found". Please help!
Sent from my Transformer TF101 using xda app-developers app
Check to make sure the rooting method works with your device. Have you checked out the sticky threads here about it ? I remember that I tried three different ways of rooting (all from here) before it worked - I think it was a PC driver issue and a lack of support for one.
After that, you will need to install a custom recovery in order to flash from. I really like TWRP, and was advised to download "Goomanager" from the Play Store - from there you can go to the menu dots in the upper right and choose "Install OpenRecoveryScript" and it will install it. I also like the "Reboot2Recovery" app, although it's not as useful on a custom ROM that includes the feature, but is easier than holding down buttons just right for that first time.
After that, you can flash a ROM via that custom recovery you installed (on TWRP it is very user-friendly and very obvious what you need to do as long as you know what you need to "wipe" beforehand - all you need is to use the "Install" button and thereafter).
ROM+Kernel(optional)+GAPPS(Google proprietary apps) . You need to wipe both caches, /system and internal data. You could use Titanium Backup prior to this to backup apps and of course back up data to an external source. A Kernel is sort of an underlayer of the "OS" that works on a low level with the hardware. You can read about some of the available ones in the Development section and see why people are using them, what possible benefits they get, et cetera.
arabic support
do custom roms support foreign languages and fonts, i use to visit arabic web sites and arabic tweets, do CM10, AOSP or Teom eos support such fonts
Pennycake said:
Check to make sure the rooting method works with your device. Have you checked out the sticky threads here about it ? I remember that I tried three different ways of rooting (all from here) before it worked - I think it was a PC driver issue and a lack of support for one.
After that, you will need to install a custom recovery in order to flash from. I really like TWRP, and was advised to download "Goomanager" from the Play Store - from there you can go to the menu dots in the upper right and choose "Install OpenRecoveryScript" and it will install it. I also like the "Reboot2Recovery" app, although it's not as useful on a custom ROM that includes the feature, but is easier than holding down buttons just right for that first time.
After that, you can flash a ROM via that custom recovery you installed (on TWRP it is very user-friendly and very obvious what you need to do as long as you know what you need to "wipe" beforehand - all you need is to use the "Install" button and thereafter).
ROM+Kernel(optional)+GAPPS(Google proprietary apps) . You need to wipe both caches, /system and internal data. You could use Titanium Backup prior to this to backup apps and of course back up data to an external source. A Kernel is sort of an underlayer of the "OS" that works on a low level with the hardware. You can read about some of the available ones in the Development section and see why people are using them, what possible benefits they get, et cetera.
Click to expand...
Click to collapse
You should be fine with foreign languages as the custom rom is generally built on what Android uses, so if you can do it on stock than you should be fine on custom.
I use a different recovery than the above post, but if you follow his steps then you should be fine. You don't NEED a custom kernel to run JB per say, but it does give you a bit more power if you want to get into overclocking etc. Also, I try to stress, once you have custom recovery and are ready to flash whatever rom you chose, wipe everything. My first and only real panic was a bootloop from not wiping everything.
Like somebody mentioned above, make sure your device is compatible with each tool. Look at your serial number on the bottom of the tablet next to the usb port. Should see B60blahblah or B70blahblah, or maybe something higher (if it's newer).
I use a nice tool put together by whitekidney called EasyFlasher. It's an all in one package where you can root, install custom recovery, and install new firmware. Check this thread. It works very well for me, and is super easy.
whitekidney says:
Works for:
ANY TF101:
SBK1 (B10-B70)
SBK2 (B70,B80,B90++)
Some B70 models are SBK1, some newer B70 are SBK2, if you don't know which one you have, try both!
Click to expand...
Click to collapse
It's real easy to use. Put your tablet into apx mode by holding the power button and the volume up button. The screen will look like it's off but if you plug it into your Windows computer, you should hear the sound when a device is plugged it. Then it'll try to install the drivers for an apx device, or some MTP drivers, I believe. If they fail to install, download PDAnet and install it. This will correctly install your drivers. There's also another method of getting your drivers to install correctly. Here's a universal driver package that 1wayjonny put together. To clarify, only use PDAnet or the universal driver package if your drivers didn't install correctly when you plugged your transformer (which should be in apx mode) into your computer.
Now you can use EasyFlasher to install a custom recovery. I left it on the very first option, (a touch recovery, so you don't have to use your buttons to change your selection). During this process, EasyFlasher should first open up a command prompt (it might pop up behind your current programs running so you won't see it until you minimize everything except for EasyFlasher). The cmd prompt will ask you to overwrite some files on your device, just type a for "always" and let it do it's thing. It's really running NVflash which you should also get familiar with too.
After you have a custom recovery installed, flash your ROM of choice. Here's a nice JB 4.1 that I've tried out. Download that file, put it on a micro sd card, pop it in your transformer, and reboot into recovery by holding volume down and the power button. When it reboots, press volume up to enter your new custom recovery (like it should say on the screen). If you installed the same recovery that I recommended above (hopefully these are the correct steps, as I don't have my device in front of me), click on flash .zip, then click on from sd card. You should see the zip that you transferred from your computer, click on it, and it should install.
Once that's finished, reboot your transformer, let it load the new rom, either set it up or skip all the junk in the beginning. Once you're on the main home screen, remove your micro sd card and transfer the superuser zip that you can find inside the tools folder in EasyFlasher's directory (on your computer) to your sd card. Reboot into recovery, and now flash that super user zip the same way you flashed the rom.
Now you have a brand new, 4.1.2 JB rooted device!
Quick question, do i need to connect my asus eee transformer pad tf101 to my windows xp pc to root it? Or can i used my ibook g3. The reason i ask is because i keep getting an error about MTP error. I have search everywhere for this error and i cant find a solution.
Sent from my Transformer TF101 using xda app-developers app
jbusti75 said:
Quick question, do i need to connect my asus eee transformer pad tf101 to my windows xp pc to root it? Or can i used my ibook g3. The reason i ask is because i keep getting an error about MTP error. I have search everywhere for this error and i cant find a solution.
Sent from my Transformer TF101 using xda app-developers app
Click to expand...
Click to collapse
I am sure it can be done, but most of the tools (like EasyFlasher) use Windoze.
Even if you are getting an MTP error, it should not matter as you will be using the APX device. Just make sure you have the APX driver and update the unknown device that appears after you boot to APX mode.

[Q]B2B market : Create an Android app in dedicated Hardware with specific rights

Hi,
I'm working on a project where I would sale an android tablet with dedicated App. (not for consumer market but Business to business)
the chosen tablet is Asus TF300T with the Ethernet port.
The problem I have is :
I would like my Application would have access in read/Write to the Ethernet Card settings (not Wifi)
This is relatively easy to do if the tablet is rooted -> but the rooting is something we can't do for many reasons.
by a work around, we succeeded to change the Ethernet IP address but didn't success to apply it (caused by the custom "apply" Asus button in ethernet settings page)
to apply the IP Adress we have to ask to the application user to go to the Settings page and push by himself the "apply" button ..... it's not the best.
My question is :
Is it possible to build a auto-signed flashable zip containing my Application, This flashable zip would install the App and give it the right access to the Ethernet card settings, without root rights needs?
or
Does exist a way that the Application reboot a tablet without root rights?
Thanks a lot for your help
You won't be able to flash anything without unlocking the device as you need a custom recovery installed. You don't need to be rooted to do what you require.
Thanks for your reply,
I understand that the device needs to be unlocked, However, I didn't know a custom recovery was needed to do that.
do you confirm I cannot do it from the standard recovery?
Underscan said:
Thanks for your reply,
I understand that the device needs to be unlocked, However, I didn't know a custom recovery was needed to do that.
do you confirm I cannot do it from the standard recovery?
Click to expand...
Click to collapse
The device won't accept anything from the stock recovery unless it is signed by Asus.
Ah I just got what you are saying - you want to try and flash something on the stock recovery on an unlocked device? How will you do that?
Why can't you put TWRP onto the device and flash your app?
"you want to try and flash something on the stock recovery on an unlocked device? How will you do that?"
I don't know
"Why can't you put TWRP onto the device and flash your app?"
we would like to reduce at maximum the number of TF300T handling between the Asus tablet reception and the shipping to our customer.
If we had found a solution to just flash theTF300 with a flashable zip -> that it ! the App is installed with the good user right (only for our App). -> it would be awesome!
It seems the only way to have it, is to get the Asus signature... seems impossible...
In essence you are wanting to put a custom stock ROM on it.
There are two ways to achieve this
1: unlock, flash twrp via fast boot and then flash the app.
2: root using moto chopper and manually place your app in /system/app
Alternatively you could just ask the user to sideload your app by allowing that through the settings on the device.
sbdags said:
In essence you are wanting to put a custom stock ROM on it.
There are two ways to achieve this
1: unlock, flash twrp via fast boot and then flash the app.
2: root using moto chopper and manually place your app in /system/app
Alternatively you could just ask the user to sideload your app by allowing that through the settings on the device.
Click to expand...
Click to collapse
Doesn't look like the sideloading would grant sufficient privileges though, at least if you're referring to the sideloading I'm thinking of.

[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

Categories

Resources