How to update ROOTED TF300 to Jelly Bean

[rightonred]

I posted this comment while xda was updating and it got borked.

 

[rightonred]

If you lost root because you didn't use supersu, can you at least get root in an adb shell?

Try doing:

adb shell
/system/usr/we-need-root/su-backup
id

do you get this line:

uid=0(root) gid=0(root)

 

[erniejazz]

If you lost root because you didn't use supersu, can you at least get root in an adb shell?

Try doing:

adb shell
/system/usr/we-need-root/su-backup
id

do you get this line:

uid=0(root) gid=0(root)

HI, I do get

uid=0(root) gid=0(root) groups=1003(graphics),1004(input),1007(log),1009(mount),
1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(in
et),3006(net_bw_stats)
[email protected]:/ #

Seems that we can get root in adb. But is there any way to fix the issue from here? Thanks in advance

 

[rightonred]

HI, I do get

uid=0(root) gid=0(root) groups=1003(graphics),1004(input),1007(log),1009(mount),
1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(in
et),3006(net_bw_stats)
[email protected]ndroid:/ #

Seems that we can get root in adb. But is there any way to fix the issue from here? Thanks in advance

You're in luck!:victory: I'll see if I can help you later though. It's really late here where I live.

 

[zzzk]

Lost root with 4.1.1 upgrade. Had superuser and ota root keeper.

I used the miloj method to root my asus tf300t. This is the post:
http://forum.xda-developers.com/showthread.php?t=1704209

I used superuser and ota root keeper. I did NOT use supersu. When I upgraded to 4.1.1, I lost root. I tried to restore it with ota, it said restored, but did not restore root. I tried the following commands with adb shell and got the following:

[email protected]:/ $ /system/usr/we-need-root/su-backup
/system/usr/we-need-root/su-backup
/system/bin/sh: /system/usr/we-need-root/su-backup: not found
127|[email protected]:/ $ /system/xbin/su
/system/xbin/su
/system/bin/sh: /system/xbin/su: not found
127|[email protected]:/ $ id
id
uid=2000(shell) gid=2000(shell) groups=1003(graphics),1004(input),1007(log),1009
(mount),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt)
,3003(inet),3006(net_bw_stats)
[email protected]:/ $

Please let me know. Thank you.

 

[rightonred]

try this if you lost root, but have a backup:

Get the supersu su binary from chainfire.eu or from the attachment. extract it to the root of the device's internal memory. (/sdcard)
open an adb shell by doing:

adb shell

now obtain a root shell by doing:

/system/usr/we-need-root/su-backup

If there was a "not found" error, try:

/system/su-backup

if you still get an error, try replacing the dash in su-backup with an under score.
now, for the dirty work...

mount -o remount,rw /dev/block/mmcblk0p1 /system
cd /system/xbin
rm su

may give an error.

dd if=/sdcard/su of=su
chmod 6755 su
chown 0.0 su
mount -o remount,ro /dev/block/mmcblk0p1 /system

uninstall superuser and install supersu from play.
test your root. If it works, delete your voodoo backup and back root up again.
as a general disclaimer: I do not own a tf300. do this at your own risk.
let me know if you encounter any issues.

 

[Tequila.CZ]

He's asking if he needs both applications installed. The answer is no, coquipr. If you had Superuser installed first, just open SuperSU for the first time and Superuser will ask you to grant it root access. Accept, and then go into SuperSU's settings and make sure "Enable Superuser" is turned on. This will make it so that SuperSU is now the primary system SU. To test it, just open a program that needs root (like OTA Rootkeeper) and you should see the new access prompt from SuperSU. After that, you can remove Superuser from your tablet.

So in fact to be able to restore root with Voodoo OTA Rootkeeper we need to replace Superuser with SuperSU?
If I already have Superuser installed, Voodoo OTA Root backup created and no SuperSU, should I:
1) Install SuperSu app (grant an Superuser access and enable Superuser option)
2) Uninstall Superuser app
3) Delete old Voodoo OTA Root backup
4) Make a fresh root backup using Voodoo
5) Update to JB
6) Restore root using Vodoo app

Could anyone confirm this worked?

Many thanks!

 

[mrpierrec]

where is this backup file ?
I can't find it.

 

[Tequila.CZ]

If this is refering to the post above:
3) Delete old Voodoo OTA Root backup

Then there should be an option "Delete su backup" directly in the Voodoo OTA RootKeeper app.

 

[pakure]

Steps 2,3,4.. are not required

Sent from my HTC HD2 using Tapatalk 2

 

[erniejazz]

try this if you lost root, but have a backup:

Get the supersu su binary from chainfire.eu or from the attachment. extract it to the root of the device's internal memory. (/sdcard)
open an adb shell by doing:

adb shell

now obtain a root shell by doing:

/system/usr/we-need-root/su-backup

If there was a "not found" error, try:

/system/su-backup

if you still get an error, try replacing the dash in su-backup with an under score.
now, for the dirty work...

mount -o remount,rw /dev/block/mmcblk0p1 /system
cd /system/xbin
rm su

may give an error.

dd if=/sdcard/su of=su
chmod 6755 su
chown 0.0 su
mount -o remount,ro /dev/block/mmcblk0p1 /system

uninstall superuser and install supersu from play.
test your root. If it works, delete your voodoo backup and back root up again.
as a general disclaimer: I do not own a tf300. do this at your own risk.
let me know if you encounter any issues.

Hi, all the step in adb shell sucess expcept there is not su in xbin folder.
However in the end I can't uninstall superuser in my TF300 since for some reason it is a system app.
I try to disable it and install supersu, and I got a "su binary needs to be updated" prompt.
After I click continue, it said "installation failed!"

I try enter adb shell and use su command directly, I got

[email protected]:/ $ id
id
uid=2000(shell) gid=2000(shell) groups=1003(graphics),1004(input),1007(log),1009
(mount),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt)
,3003(inet),3006(net_bw_stats)
[email protected]:/ $ su
su
[email protected]:/ # id
id
uid=0(root) gid=0(root) groups=1003(graphics),1004(input),1007(log),1009(mount),
1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(in
et),3006(net_bw_stats)

Seems su command works in adb shell, but supersu still can't use it. It look really promising though.
It there anything I can try next? Thanks a lot!:good:

 

[rightonred]

...Seems su command works in adb shell, but supersu still can't use it. It look really promising though.
It there anything I can try next? Thanks a lot!:good:

Hmm. uninstalling superuser isn't mandatory. you can do that using the root uninstaller once root is restored.
try repeating the fix using miloj's insecure su: http://forum.xda-developers.com/showthread.php?t=1704209
just be sure to update the binary in supersu.

 

[erniejazz]

Hmm. uninstalling superuser isn't mandatory. you can do that using the root uninstaller once root is restored.
try repeating the fix using miloj's insecure su: http://forum.xda-developers.com/showthread.php?t=1704209
just be sure to update the binary in supersu.

I can't use adb push for those files so I put those files in sd card and move it in adb shell.
All the process works except I can't update binary in the last part and can't grain root acess.
I think something must be different between ICS and JB otherwise this must work though.

: Extra finding:
in adb shell if I use /system/xbin/su seems not working

[email protected]:/ $ /system/xbin/su
/system/xbin/su
[email protected]:/ $ id
id
uid=2000(shell) gid=2000(shell) .......
[email protected]:/ $ su
su
[email protected]:/ # id
id
uid=0(root) gid=0(root) ......
[email protected]:/ # which su
which su
/system/bin/su

is it might be the problem??

 

[TDMVP73]

Hmm. uninstalling superuser isn't mandatory. you can do that using the root uninstaller once root is restored.
try repeating the fix using miloj's insecure su: http://forum.xda-developers.com/showthread.php?t=1704209
just be sure to update the binary in supersu.

Rightonred, do you have any ideas on how to force a downgrade to 9.4.3.30 ICS from Jelly Bean?

If so, then maybe we can reroot, install SuperSU, backup root, etc.

I think waiting for an exploit in Jelly Bean will take much longer than doing that.

 

[rightonred]

I can't use adb push for those files so I put those files in sd card and move it in adb shell.
All the process works except I can't update binary in the last part and can't grain root acess.
I think something must be different between ICS and JB otherwise this must work though.

: Extra finding:
in adb shell if I use /system/xbin/su seems not working

[email protected]:/ $ /system/xbin/su
/system/xbin/su
[email protected]:/ $ id
id
uid=2000(shell) gid=2000(shell) .......
[email protected]:/ $ su
su
[email protected]:/ # id
id
uid=0(root) gid=0(root) ......
[email protected]:/ # which su
which su
/system/bin/su

is it might be the problem??

hmm. you did chmod 6755 /system/xbin/su?(after remounting of course)
It appears that the problem is that the su command atuomatically invokes /system/bin/su instead of /system/xbin/su , and the /system/bin/su is the superuser su binary. also the supersu su binary(which is now at /system/xbin/su) has not been chmoded correctly and can't give root access.
try chmoding the /system/xbin/su again and see if you can get root access through it.
If you can then do:
rm /system/bin/su
to get rid of the old superuser binary.

Rightonred, do you have any ideas on how to force a downgrade to 9.4.3.30 ICS from Jelly Bean?

If so, then maybe we can reroot, install SuperSU, backup root, etc.

I think waiting for an exploit in Jelly Bean will take much longer than doing that.

nope. Thats where a catch 22 comes in: you can't force downgrade without root.
If you really want root, you can always do a bootloader unlock, flash cwm recovery, then flash chainfire's supersu zip. (or wait for an exploit)
EDIT: wait a second, I just got a thunk...
if you can get root in adb you can force downgrade if all else fails.
just download the old firmware from asus's website, extract the blob to the root of /sdcard/(it's double zipped), give yourself a root adb shell using the backup su using the commands I posted earlier, then do:
dd if=/sdcard/blob of=/dev/block/mmcblk0p4
this will appear to do nothing for several minutes
now do:
reboot
the tablet should now flash the older firmware,

 

[calisro]

I was in this same situation and I SOLVED my root issue.

In my case, I was able to logon with adb and then su to root from adb which means I still had root. If you have this access, your golden EVEN if the superuser app and the supersu app isn't working.

Do this:
1) Download the insure su from here (This is a WIDE OPEN su without any controls). (sparky root i believe?)
https://www.dropbox.com/sh/jcpilpgoeta516e/tCB-Ep-3YQ

2) logon to adb
3) su -
4) remount system as RW:
mount -o remount,rw /dev/block/mmcblk0p1 /system
5) make a backup of current su just in case in adb
cp /system/bin/su /system/bin/su1
6) push the su binary from step 1 to system
adb push su /system/bin/
7) Change permissions for SU
chmod 6755 /system/bin/su
8) download superuser (NOT SUPERSU) from play store if you do not have it already.
9) have superuser upgrade the su binary
10) congrats. your now rerooted.

 

[funnel71]

I was in this same situation and I SOLVED my root issue.

In my case, I was able to logon with adb and then su to root from adb which means I still had root. If you have this access, your golden EVEN if the superuser app and the supersu app isn't working.

Do this:
1) Download the insure su from here (This is a WIDE OPEN su without any controls). (sparky root i believe?)
https://www.dropbox.com/sh/jcpilpgoeta516e/tCB-Ep-3YQ

2) logon to adb
3) su -
4) remount system as RW:
mount -o remount,rw /dev/block/mmcblk0p1 /system
5) make a backup of current su just in case in adb
cp /system/bin/su /system/bin/su1
6) push the su binary from step 1 to system
adb push su /system/bin/
7) Change permissions for SU
chmod 6755 /system/bin/su
8) download superuser (NOT SUPERSU) from play store if you do not have it already.
9) have superuser upgrade the su binary
10) congrats. your now rerooted.

I must try this when I get home because I have root via adb

Sent from my ASUS Transformer Pad TF300T using xda app-developers app

 

[TDMVP73]

hmm. you did chmod 6755 /system/xbin/su?(after remounting of course)
It appears that the problem is that the su command atuomatically invokes /system/bin/su instead of /system/xbin/su , and the /system/bin/su is the superuser su binary. also the supersu su binary(which is now at /system/xbin/su) has not been chmoded correctly and can't give root access.
try chmoding the /system/xbin/su again and see if you can get root access through it.
If you can then do:
rm /system/bin/su
to get rid of the old superuser binary.


nope. Thats where a catch 22 comes in: you can't force downgrade without root.
If you really want root, you can always do a bootloader unlock, flash cwm recovery, then flash chainfire's supersu zip. (or wait for an exploit)
EDIT: wait a second, I just got a thunk...
if you can get root in adb you can force downgrade if all else fails.
just download the old firmware from asus's website, extract the blob to the root of /sdcard/(it's double zipped), give yourself a root adb shell using the backup su using the commands I posted earlier, then do:
dd if=/sdcard/blob of=/dev/block/mmcblk0p4
this will appear to do nothing for several minutes
now do:
reboot
the tablet should now flash the older firmware,

It's working as we speak!

Looks like we found an easy solution.

Downgrade, exploit again, install SuperSU, back-up with Voodoo OTA Rootkeeper, then upgrade to JB and restore root.

 

[calisro]

It's working as we speak!

Looks like we found an easy solution.

Downgrade, exploit again, install SuperSU, back-up with Voodoo OTA Rootkeeper, then upgrade to JB and restore root.

Glad you got it working and glad the exploit works on JB but I doubt you needed to downgrade. You still had root with adb and could have just used the *special* su to regrant permissions to superuser (see my post). Just mentioning for others.

But congrats anyway.:good:

 

[rightonred]

I was in this same situation and I SOLVED my root issue.

In my case, I was able to logon with adb and then su to root from adb which means I still had root. If you have this access, your golden EVEN if the superuser app and the supersu app isn't working.

Do this:
1) Download the insure su from here (This is a WIDE OPEN su without any controls). (sparky root i believe?)
https://www.dropbox.com/sh/jcpilpgoeta516e/tCB-Ep-3YQ

2) logon to adb
3) su -
4) remount system as RW:
mount -o remount,rw /dev/block/mmcblk0p1 /system
5) make a backup of current su just in case in adb
cp /system/bin/su /system/bin/su1
6) push the su binary from step 1 to system
adb push su /system/bin/
7) Change permissions for SU
chmod 6755 /system/bin/su
8) download superuser (NOT SUPERSU) from play store if you do not have it already.
9) have superuser upgrade the su binary
10) congrats. your now rerooted.

Awesome!
Don't forget to remount system as read only for security when you are done. you can do this by rebooting or:
mount -o remount,ro /dev/block/mmcblk0p1 /system:good: