Database Info

B80 root?

Is there a method for rooting the tf101 B80 yet? I've been searching for a while but only find old methods.
Sent from my DROID3 using XDA App

Not yet, though there is work going on to try and change that.

http://forum.xda-developers.com/showthread.php?p=18868785
Sent from my Transformer TF101 using Tapatalk

If it's rootable, I would know, as I've been keeping up on Team RayDroid's blog posts. Last I heard, they are looking for an SBKv2 device that can go into APX mode. Never heard any more news after that.
Sent from Sukia, my rooted HTC Inspire.

I think whoever comes out with a root method should hold of on releasing the method until after the first batch of Primes show up because we dont want them to block the method going forward too soon.

I have my B70 rooted using Brk's root toolkit. It can use nvflash to root your device, if unable to enter apx mode. It can also flash roms too. Check it out, it might work for your pad, it's worth a try. It can't brick your pad and it only takes a couple minutes.

outerdepth said:
I have my B70 rooted using Brk's root toolkit. It can use nvflash to root your device, if unable to enter apx mode. It can also flash roms too. Check it out, it might work for your pad, it's worth a try. It can't brick your pad and it only takes a couple minutes.
Click to expand...
Click to collapse
Some of the B70 models are rootable, B70KAS1 and below should be rootable, B70KAS2 and above aren't. At least that's what I've got from reading all the threads about it.

I've completely given up on getting a root for SBKv2. If it hasn't happened by now....yeah. With the Transformer 2 hitting the shelves soon...the possibilities dwindle even further. I appreciate their effort, just don't think it's gonna happen. Shame on ASUS.

[Q] Can the B90 Transformer be downgraded from ICS to honeycomb???

Header says it all... and if the answer is YES, then a link to HOW to accomplish that would be greatly appreciated...
Many thanks...

You would need to root, install cwm recovery, flash a rooted HC ROM.

@basballfanz: how to root the 9.2.2.3 Firmware?

From my experience, once you are on ICS, re-flashing Honeycomb via CWM does NOT solve the reboot issues (you'll have them in Honeycomb too). The ONLY way that I was able to return to a stable version of Honeycom was to NVFLash a stock honeycomb image and go from there. But, since you have a B90, you can't NVFlash, so basically, I think you're screwed at this point....
There is a whole thread about returning to honeycomb via CWM and still having the reboots, etc.. Search it out...
Sent from my Transformer TF101 using Tapatalk 2

meinmichi said:
@basballfanz: how to root the 9.2.2.3 Firmware?
Click to expand...
Click to collapse
Don't think there's a way right now.

Can't you modify/use an ASUS Ota update package and use the stock recovery to 'Update' to HC. Reboot issues will still be there though.
Edit: as in when downgrading for razorclaw root etc

Thing O Doom said:
Can't you modify/use an ASUS Ota update package and use the stock recovery to 'Update' to HC. Reboot issues will still be there though.
Edit: as in when downgrading for razorclaw root etc
Click to expand...
Click to collapse
You can't downgrade on a stock tf.
The trick going from 8.6.5.21 to 8.6.6.19 to use razorclaw is technically an upgrade not downgrade. It was going from 8.6..5.21 to 8.6.6.19

Sorry I wasn't clear, I mean modifying a downgrade ASUS package to trick the Tf into Thinking that it's being updated.
Thanks for the version # clearup though X.x"

a simple rename do not work. Have taste it....
The tf see the update, reboot and start Update. But stoppt...
So what to do? Edit buildprob? Or what read the tf in Thema Update file ?

Get a hc package, unzip the ics package, delete and replace as needed. Probably need to edit build.prop too, and make sure the kernel flashes.

Or is a replace of the blob file the onky we need?
How is the chance of bricked?

Considering the kernel/os differences, higher than you'd want it to be, so I'd only do it as a last resort. Make a nandroid backup before doing any tinkering.

Cant do Backup without root. Thats why i want to downgrade...

Seems like a new method to downgrade from ICS to HC even for the non rooted users.
http://forum.xda-developers.com/showthread.php?t=1622628

THX thats works!

Can someone lead me or explain to me exactly what the s/n number means in terms of rooting and nvflashing. I have C30.
Sent from my Transformer TF101 using XDA

I think the real question here is why would you want to downgrade to HC from ICS? It's pretty well known that a full system restore fixes most issues.

miketoasty said:
I think the real question here is why would you want to downgrade to HC from ICS? It's pretty well known that a full system restore fixes most issues.
Click to expand...
Click to collapse
Why? Because ICS is completely un-stable on ALOT of TF101's (if not all). Honeycomb was rock solid.
Sent from my Transformer TF101 using Tapatalk 2

McSurge45 said:
Can someone lead me or explain to me exactly what the s/n number means in terms of rooting and nvflashing. I have C30.
Sent from my Transformer TF101 using XDA
Click to expand...
Click to collapse
First letter:
B=2011 & C=2012 manufacture year.
Second letter/number:
1=Jan 2=Feb ect till Oct which is A(hex)
So your C3O was manufacture in March 2012.
Only different is the SBK
ASUS changed the sbk mid July 2011.

miketoasty said:
I think the real question here is why would you want to downgrade to HC from ICS? It's pretty well known that a full system restore fixes most issues.
Click to expand...
Click to collapse
Except, it doesn't.

[Q]Root Void Warranty?

I am version .29 (i think, how do i tell?) and i want to root.
I don't want to flash new ROMs yet, so I don't think i need an unlocked bootloader. If I only root the tablet, will I permanently void my warranty?
Thanks
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2

No. As long as you get rid of all the root stuff, no one would be able to tell you were rooted.

sounds good.
Also, how do I tell what version tablet i have? where do i look for .29 vs .26?
Thanks

settings/about tablet and scroll down to build number...you will see a long number and .26 or .29 followed by a long number.
congrats...I'm still having some issues rooting. ota rootkeeper didn't keep my root when I upgraded from .17 to .29...still working on it

Throb1231 said:
settings/about tablet and scroll down to build number...you will see a long number and .26 or .29 followed by a long number.
congrats...I'm still having some issues rooting. ota rootkeeper didn't keep my root when I upgraded from .17 to .29...still working on it
Click to expand...
Click to collapse
Something is borked with your system my friend. I've been following your attempts to root. I rooted my system as of today with .17 using sparkys root. It didn't work the first time for whatever ryhme or reason, then after trying it a second time doing it a little differently, it worked. If there is a way for you to do a full wipe/reload and start fresh, I would do that.
Sent from my SGH-I777 using Tapatalk 2

cavsoldier19d said:
Something is borked with your system my friend. I've been following your attempts to root. I rooted my system as of today with .17 using sparkys root. It didn't work the first time for whatever ryhme or reason, then after trying it a second time doing it a little differently, it worked. If there is a way for you to do a full wipe/reload and start fresh, I would do that.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
I thought he had manually updated to .29, in which case you wouldn't be able to restore with rootkeeper.

Rooted my stock .29 300 with sparky's root tool tonight; worked first time flawlessly.

Took the update to JB, but can't get my root back

OK, need someone to tell me what I'm missing please.
Yesterday I was on stock .30 and rooted. This morning I took the JB update. My first boot was OK and I still had root, but when I rebooted, I got stuck in a loop. It kept rebooting after getting to the desktop. I assumed at least one of my apps was causing it, so I used the wipe data function with the power + vol down thing. that wiped everything, including root.
I tried to re-do the debugfs method, but that seems to fail. Strange thing is, if I use adb shell from the computer, I can su - root and get root access. That's how I was able to give read/write access to the data folder where debugfs does its' work. It's just that root check says I'm not rooted. Voodoo OTA has all boxes checked on my root check, except the one that says granted root permissions. The SU file does exist inside /system/xbin
So it's as if the tablet's user just doesn't have permission to do root. I loaded a terminal emulator on the tablet, and tried to su - root that way, and got permission denied. I would normally get the "superuser" popup when doing something like that -
So there's definitely a piece I'm missing. Can someone point me in the right direction please?

reinstall ota rootkeeper and restore root. factory reset doesnt wipe root access you just need to restore it.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2

jgaf said:
reinstall ota rootkeeper and restore root. factory reset doesnt wipe root access you just need to restore it.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
Sorry, should have mentioned that I tried that. Attaching a screenshot as to what it looks like. Notice the center checkmark stating "root permission granted" is not checked, and there's no option to restore, only to remove or temp unroot, so it's like, everything is good, except for the actual root permission
Root checker shows red (no access) and root programs like root explorer do not prompt for superuser permission before running as I would expect them to the first time.

Did you run superuser? Did you reboot after running su for the first time?
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2

Absolutely, more times than I can count. Here's another shot showing I can't execute such but it seems to have global execute...
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

Install supersu and not superuser....update the binary ...then try again
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2

pakure said:
Install supersu and not superuser....update the binary ...then try again
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
OK, uninstalled superuser, and installed superSU as you suggested and rebooted the tablet for good measure.
Ran it, and it prompted me, saying su needed updating, said yes do it, came back to me "installation failed", which I honestly expected because for whatever reason, current tablet user cannot get to su, even though it appears permissions said it should.
One other note, earlier I tried to refollow these directions: http://forum.xda-developers.com/showthread.php?t=1704209
That is how I rooted when under build .30, no issues at all. This time I hit a snag when trying to push files to /data/local - said I had no permission. now I got around it via ADB by simply typing su - root....root seems to work when I'm in ADB, but it doesn't work via tablet interface. I don't know what I'm missing here....
Just a thought.. I was considering flashing back to .30 using fastboot but I wasn't sure if that would even work. I tried loading the .30 zip into the root of storage and it detected it, as a downgrade even and asked to proceed. When done I was still on 4.1.1 not the older build.
BTW, thank you for taking the time. I really don't mean to be a pain here. I've not had this much trouble before...

Well sh++ This would explain why I couldn't redo the debugfs root process...
http://forum.xda-developers.com/showthread.php?p=27990303
I decided to go have a look at the nexus 7 area since that's native JB and saw that. So' for those just buying this, you might want to root before you update.
Still doesn't explain my problem but at least explains why I can't use the solution that WAS good.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

funnel71 said:
Well sh++ This would explain why I couldn't redo the debugfs root process...
http://forum.xda-developers.com/showthread.php?p=27990303
I decided to go have a look at the nexus 7 area since that's native JB and saw that. So' for those just buying this, you might want to root before you update.
Still doesn't explain my problem but at least explains why I can't use the solution that WAS good.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
I was able to restore my root. See this post.
http://forum.xda-developers.com/showthread.php?p=30481502#post30481502

I've really messed up now. Set perms wrong for the such that was on the tablet so now can't get root using adb either so unless there is a way to downgrade without root I'm screwed.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

I was so amped to grab JB, that I spaced that the OTA update would break root (i'm rooted but locked bootloader, b/c i was hoping 4.1.1 would come sooner than later!)
I had OTA rootkeeper installed, and while I was a little skeptical as to how easily it would work, it was 1-click simple and I just had to reinstall/update the binaries and reboot. I had the same check mark unchecked, but it worked, was straightforward, etc. It sounds like something got jacked in the JB flash, and I wonder if a full wipe/reset (&downgrade) to 4.04, re-root, then OTA update (using ota rootkeeper to hold root) might work for you?

thesuzukimethod said:
I was so amped to grab JB, that I spaced that the OTA update would break root (i'm rooted but locked bootloader, b/c i was hoping 4.1.1 would come sooner than later!)
I had OTA rootkeeper installed, and while I was a little skeptical as to how easily it would work, it was 1-click simple and I just had to reinstall/update the binaries and reboot. I had the same check mark unchecked, but it worked, was straightforward, etc. It sounds like something got jacked in the JB flash, and I wonder if a full wipe/reset (&downgrade) to 4.04, re-root, then OTA update (using ota rootkeeper to hold root) might work for you?
Click to expand...
Click to collapse
I would love to try the downgrade approach as that's the only one left I haven't tried, primarily because I have tried and haven't found a way to do it. If you know how with a locked boot loader then I'd love to hear.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

funnel71 said:
I would love to try the downgrade approach as that's the only one left I haven't tried, primarily because I have tried and haven't found a way to do it. If you know how with a locked boot loader then I'd love to hear.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
sorry, above my pay-grade at this point. I think i was overly optimistic about the "open-ness" of the device/bootloader (my other device is a galaxy nexus, so it's easy to do just about anything). I had a factory wipe or flash/img restore in my mind, but factory wipe wouldnt help (dont thinK), and If a stock 4.04 img exists, pretty sure there is a command set in fastboot that would let you restore using that image, but also pretty (99%) sure that requires an unlocked bootloader.
It sounds like there were a few changes in folder structure in JB that are limiting the root-ability, but my guess is the brainy folks around here will figure that out pretty quick, and JB will be root-able soon.

thesuzukimethod said:
sorry, above my pay-grade at this point. I think i was overly optimistic about the "open-ness" of the device/bootloader (my other device is a galaxy nexus, so it's easy to do just about anything). I had a factory wipe or flash/img restore in my mind, but factory wipe wouldnt help (dont thinK), and If a stock 4.04 img exists, pretty sure there is a command set in fastboot that would let you restore using that image, but also pretty (99%) sure that requires an unlocked bootloader.
It sounds like there were a few changes in folder structure in JB that are limiting the root-ability, but my guess is the brainy folks around here will figure that out pretty quick, and JB will be root-able soon.
Click to expand...
Click to collapse
Yes it's the /data folder where the exploit was and is causing the issue. I saw one of the commands was flash all, but I was too scared to try that. I tried the update.zip approach, but it came back with needed files weren't present in the archive.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

funnel71 said:
I would love to try the downgrade approach as that's the only one left I haven't tried, primarily because I have tried and haven't found a way to do it. If you know how with a locked boot loader then I'd love to hear.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
What did you do exactly? Details!
You can try this.... It may work... The worst case is that it just doesn't work. I have not seen a confirmation yet as to whether this method works or not yet.
https://www.dropbox.com/sh/jcpilpgoeta516e/QTl4TihVq0/Rooting-the-tf300.txt
---------- Post added at 03:09 PM ---------- Previous post was at 03:07 PM ----------
calisro said:
What did you do exactly? Details!
You can try this.... It may work... The worst case is that it just doesn't work. I have not seen a confirmation yet as to whether this method works or not yet.
https://www.dropbox.com/sh/jcpilpgoeta516e/QTl4TihVq0/Rooting-the-tf300.txt
Click to expand...
Click to collapse
Oops. This is the whole link. Sorry about that. directions are in there.
https://www.dropbox.com/sh/jcpilpgoeta516e/tCB-Ep-3YQ
---------- Post added at 03:11 PM ---------- Previous post was at 03:09 PM ----------
thesuzukimethod said:
I was so amped to grab JB, that I spaced that the OTA update would break root (i'm rooted but locked bootloader, b/c i was hoping 4.1.1 would come sooner than later!)
I had OTA rootkeeper installed, and while I was a little skeptical as to how easily it would work, it was 1-click simple and I just had to reinstall/update the binaries and reboot. I had the same check mark unchecked, but it worked, was straightforward, etc. It sounds like something got jacked in the JB flash, and I wonder if a full wipe/reset (&downgrade) to 4.04, re-root, then OTA update (using ota rootkeeper to hold root) might work for you?
Click to expand...
Click to collapse
If you have a check mark unchecked, you likely have root issues. Which check box?

calisro said:
If you have a check mark unchecked, you likely have root issues. Which check box?
Click to expand...
Click to collapse
Sorry - imprecise language on my part.
When I opened up OTA rootkeeper, it showed the same unchecked box (in rootkeeper) as others have mentioned, but I had "restore root" as an option. I did, and had no problems keeping root after updating to JB 4.1.1. OTA. I was using superuser but had checked "OTA survival" in Superuser's options, so I think that's how i kept root (seems like this "survival" option is baked in to Super Su, but a (non-default) option in Superuser).

how to go about updating

hi, im not wanting to update past the.26 update because it stops from NvFlash from being used, so my question is how do i go about updating it without know what im updating this is what im seeing right now update wise (attached photo)
Sent from my ASUS Transformer Pad TF700T using xda-developers app
btw im on the build number 9.4.5.21

ryanskeltis said:
hi, im not wanting to update past the.26 update because it stops from NvFlash from being used, so my question is how do i go about updating it without know what im updating this is what im seeing right now update wise (attached photo)
Sent from my ASUS Transformer Pad TF700T using xda-developers app
btw im on the build number 9.4.5.21
Click to expand...
Click to collapse
Once you have NvFlash installed, you can safely update to whatever version you like -- you can recover with your backups to the state it was in, as far I know. ANY update you perform at this moment in time will prevent NvFlash from being installed, so make sure you get through that procedure first. After that... no worries.

MartyHulskemper said:
Once you have NvFlash installed, you can safely update to whatever version you like -- you can recover with your backups to the state it was in, as far I know. ANY update you perform at this moment in time will prevent NvFlash from being installed, so make sure you get through that procedure first. After that... no worries.
Click to expand...
Click to collapse
If I interpret his question correctly, it's rather how to find out what exactly that update is that is "announced" at the screen shot, before he lets it update.
Either way, if you would like to unlock and flash custom ROMs AND you are still on v9.4.5.21, then you really should take the opportunity to nvflash. You never know ... and if you entered the game too late (as myself) as of right now you have no chance to do nvflash. You still have it!