For those with 'partial' root after JB update - regain root!

Search This thread
By:
Advanced…
T

thekayman

Senior Member
Nov 21, 2010
216
42
Sydney
Thanks OP.... followed your steps and I have restored root after JB Update
FYI the numbered steps with a didn't work but I followed the rest and its worked.
 
R

ranwanimator

Member
Jul 23, 2009
20
1
Didn't work for me. I had access to # in adb shell, but after doing the steps now I get

1|shell@android:/ $

So I'm guessing I lost root. Very frustrating. Hopefully someone finds a method to root JB quickly.
 
R

Restorer

Senior Member
Dec 14, 2007
1,341
529
Finally got ADB to work and give me the root prompt but can't get past stage 11 : "mount: Operation not permitted". I take it this means I've lost root for good?
 
valentinrascu

valentinrascu

Senior Member
Jan 10, 2011
667
68
Asus relleased 4.1 firmware on asus support. Put on sd and update....

Inviato dal mio Transformer Prime TF201 con Tapatalk 2
 
R

Restorer

Senior Member
Dec 14, 2007
1,341
529
Big thanks to the OP for the method but please note for any lazy people like me who are copy/pasting that there are a few typos that will cause errors if you are pushing the files as named in the supplied zip:


In the lines below change the "s" to "S"

4. adb push C:\(location of attached files)\superuser.apk /data/local/tmp
8. chmod 644 /data/local/tmp/superuser.apk
18a. chmod 644 /system/app/superuser.apk


Also in the lines below change the "C"s to "c"s .

14a. Chmod 755 /system/bin/busybox
14b. Chmod 755 /system/xbin/busybox
18a. Chmod 644 /system/app/Superuser.apk
 
Last edited:
T

thenrz

Senior Member
Dec 9, 2010
162
61
I just figured something out. I found a su-backup in /system/usr/we-need-root . I have lost root again since making this guide. My permissions were screwed up on su. I was able to restore root by doing the following:

Code: 
adb shell:
$ cd /system/usr/we-need-root
$./su-backup; su  (that is a semicolon immediately after the ./su-backup)
# mount -o remount,rw /system
(do what needs to be done)
#exit
...

su-backup must have permissions as such: (get permissions by typing this into adb shell: ls -l /system/usr/we-need-root ) If you get an error, than this specifically won't work for you.

Code: 
Required su-backup permissions for manual root restore
$ ls -l /system/usr/we-need-root/su-backup
-rwsr-sr-x  root  ...

basically, if you can find a su-backup with proper permissions (and cannot restore root with voodoo or supersu), you can manually use that to repair your root access configuration. Maybe this is well known... but to those who don't this could be useful.
 
Last edited:
  • Like
Reactions: fallenczar, Maverick07r6, Bait-Fish and 1 other person
hx4700 Killer

hx4700 Killer

Senior Member
Oct 19, 2007
1,281
274
Texas
You sound like you are in the position I was in before a full wipe and reinstall of full OS from ASUS site. I had tried every method and some tinkering of my own and couldnt get a root prompt.

The key to all of this is begin able to remount the file system as rear/write so you can put files in /system/bin and system/app so you can SU at will.

Without that ability you are screwed so it essentially takes a "hack/exploit" to get root initially so you can then install the proper files to get root permanently.
 
T

thenrz

Senior Member
Dec 9, 2010
162
61
Hx do you have a su-backup kicking around? From my experience, if you have a su binary in bin or xbin even with fct permissions, su-backup with proper permissions can bring it back even if voodoo/supersu cant. Dunno if my case is unique, but worth a look.
 
hx4700 Killer

hx4700 Killer

Senior Member
Oct 19, 2007
1,281
274
Texas
thenrz said:
Hx do you have a su-backup kicking around? From my experience, if you have a su binary in bin or xbin even with fct permissions, su-backup with proper permissions can bring it back even if voodoo/supersu cant. Dunno if my case is unique, but worth a look.
Click to expand...
Click to collapse

I had an SU in /system/xbin and /android/data (something like that anyway) for some reason. Its totally gone now. While screwing around I was able to rename the new 10.4 update zip to the same name as the last 9.2 name and it popped up the update triangle in the corner and did the steps. It actually reinstalled JB. Have done a wipe since.
 
T

thenrz

Senior Member
Dec 9, 2010
162
61
Scumbag Inc. said:
When I type su at the adb command prompt nothing happens. I just gives me the same $.
Click to expand...
Click to collapse

So you aren't getting a permission denied error? If you navigate to /system/usr/ do you have a we-need-root folder? Use the command 'ls -l /system/usr' (both lowercase Ls) Basically, I am trying to find your su-backup (if you have one) I was able to re-obtain root using this idea.
 
  • Like
Reactions: Scumbag Inc.
T

thenrz

Senior Member
Dec 9, 2010
162
61
Scumbag Inc. said:
BOOM! There's my root prompt. Now what?
Click to expand...
Click to collapse

run this first so we can see what's up... it's really configuration dependent from here.

Code: 
# ls -l /system/bin
# ls -l /system/xbin
# ls -l /system/app/Superuser.apk
(Those are all lowercase Ls up there)

Post this! I will stick around and help you get that lovely superuser popup :)

I assume since you are getting su access that busybox is ok, but I want to be sure.

From here, it's easy :)
 
Last edited:
  • Like
Reactions: Scumbag Inc.
Scumbag Inc.

Scumbag Inc.

Senior Member
May 21, 2010
145
20
Austin, TX
Thanks for helping me out

1|shell@android:/system # ls -l /system/bin
ls -l /system/bin
-rwxr-xr-x root shell 96360 2012-09-27 05:16 adb
-rwxr-xr-x root shell 191 2012-05-25 02:12 am
-rwxr-xr-x root shell 9500 2012-09-27 05:16 app_process
-rwxr-xr-x root shell 49452 2012-09-27 05:16 applypatch
-rwxr-xr-x root shell 9508 2008-08-01 07:00 atrace
-rwxr-xr-x root shell 5108 2012-09-27 05:16 bluetoothd
-rwxr-xr-x root shell 199 2012-05-25 02:12 bmgr
-rwxr-xr-x root shell 21788 2012-09-27 05:16 bootanimation
-rwxr-xr-x root shell 14004 2012-09-27 05:16 brcm_patchram_plus
-rwxr-xr-x root shell 1747 2008-08-01 07:00 bt_firmware_loader.sh
-rwxr-xr-x root shell 156 2012-05-25 02:12 bu
-rwxr-xr-x root shell 954 2008-08-01 07:00 bugmailer.sh
-rwxr-xr-x root shell 5352 2012-09-27 05:16 bugreport
-rwxr-xr-x root shell 5352 2008-08-01 07:00 camera_fw_check
lrwxr-xr-x root shell 2012-05-25 02:17 cat -> toolbox
-rwxr-xr-x root shell 587981 2012-05-25 02:12 chat
lrwxr-xr-x root shell 2012-05-25 02:17 chmod -> toolbox
lrwxr-xr-x root shell 2012-05-25 02:17 chown -> toolbox
-rwxr-xr-x root shell 37 2012-05-25 02:12 cluster
-rwxr-xr-x root shell 44 2012-05-25 02:12 cluster_get.sh
-rwxr-xr-x root shell 50 2012-05-25 02:12 cluster_set.sh
lrwxr-xr-x root shell 2012-05-25 02:17 cmp -> toolbox
-rwxr-xr-x root shell 207 2008-08-01 07:00 content
-rwxr-xr-x root shell 5352 2012-09-27 05:16 dalvikvm
lrwxr-xr-x root shell 2012-05-25 02:17 date -> toolbox
-rwxr-xr-x root shell 132440 2012-09-27 05:16 dbus-daemon
-rwxr-xr-x root shell 43 2012-05-25 02:12 dcc
lrwxr-xr-x root shell 2012-05-25 02:17 dd -> toolbox
-rwxr-xr-x root shell 21736 2012-09-27 05:16 debuggerd
-rwxr-xr-x root shell 9396 2012-09-27 05:16 dexopt
lrwxr-xr-x root shell 2012-05-25 02:17 df -> toolbox
-rwxr-xr-x root shell 58788 2012-09-27 05:16 dhcpcd
lrwxr-xr-x root shell 2012-05-25 02:17 dmesg -> toolbox
-rwxr-xr-x root shell 105816 2012-09-27 05:16 dnsmasq
-rwxr-xr-x root shell 26060 2012-09-27 05:16 downloader
-rwxr-xr-x root shell 50460 2012-09-27 05:16 drmserver
-rwxr-xr-x root shell 38184 2012-09-27 05:16 dumpstate
-rwxr-xr-x root shell 9448 2012-09-27 05:16 dumpsys
-rwxr-xr-x root shell 122500 2008-08-01 07:00 e2fsck
-rwxr-xr-x root shell 26148 2012-09-27 05:16 fsck_msdos
-rwxr-xr-x root shell 605137 2012-09-27 05:16 fu
lrwxr-xr-x root shell 2012-05-25 02:17 getevent -> toolbox
lrwxr-xr-x root shell 2012-05-25 02:17 getprop -> toolbox
-rwxr-xr-x root shell 1154080 2012-09-27 05:16 glgps
-rwxr-xr-x root shell 9448 2012-09-27 05:16 gzip
-rwxr-xr-x root shell 27176 2012-09-27 05:16 hciattach
lrwxr-xr-x root shell 2012-05-25 02:17 hd -> toolbox
-rwxr-xr-x root shell 10024 2012-09-27 05:16 hdcp_test
-rwxr-xr-x root shell 272688 2012-09-27 05:16 hostapd
-rwxr-xr-x root shell 64 2012-05-25 02:12 hotplug
lrwxr-xr-x root shell 2012-05-25 02:17 id -> toolbox
lrwxr-xr-x root shell 2012-05-25 02:17 ifconfig -> toolbox
lrwxr-xr-x root shell 2012-05-25 02:17 iftop -> toolbox
-rwxr-xr-x root shell 194 2012-05-25 02:12 ime
-rwxr-xr-x root shell 201 2012-05-25 02:12 input
lrwxr-xr-x root shell 2012-05-25 02:17 insmod -> toolbox
-rwxr-xr-x root shell 22012 2012-09-27 05:16 installd
lrwxr-xr-x root shell 2012-05-25 02:17 ioctl -> toolbox
lrwxr-xr-x root shell 2012-05-25 02:17 ionice -> toolbox
-rwxr-xr-x root shell 136672 2012-09-27 05:16 ip
-rwxr-xr-x root shell 187372 2012-09-27 05:16 ip6tables
-rwxr-xr-x root shell 196260 2012-09-27 05:16 iptables
-rwxr-xr-x root shell 13596 2012-09-27 05:16 isp_fw_update
-rwxr-xr-x root shell 14232 2012-09-27 05:16 keystore
lrwxr-xr-x root shell 2012-05-25 02:17 kill -> toolbox
-rwxr-xr-x root shell 79908 2012-09-27 05:16 linker
lrwxr-xr-x root shell 2012-05-25 02:17 ln -> toolbox
lrwxr-xr-x root shell 2012-05-25 02:17 log -> toolbox
-rwxr-xr-x root shell 13600 2012-09-27 05:16 logcat
-rwxr-xr-x root shell 9516 2012-09-27 05:16 logwrapper
lrwxr-xr-x root shell 2012-05-25 02:17 ls -> toolbox
lrwxr-xr-x root shell 2012-05-25 02:17 lsmod -> toolbox
lrwxr-xr-x root shell 2012-05-25 02:17 lsof -> toolbox
-rwxr-xr-x root shell 10436 2012-09-27 05:16 make_ext4fs
lrwxrwxrwx root root 2012-09-27 05:23 md5 -> toolbox
-rwxr-xr-x root shell 259452 2008-08-01 07:00 mdnsd
-rwxr-xr-x root shell 5300 2012-09-27 05:16 mediaserver
lrwxr-xr-x root shell 2012-05-25 02:17 mkdir -> toolbox
-rwxr-xr-x root shell 153344 2012-09-27 05:16 mksh
-rwxr-xr-x root shell 217 2012-05-25 02:12 monkey
lrwxr-xr-x root shell 2012-05-25 02:17 mount -> toolbox
-rwxr-xr-x root shell 60 2012-05-25 02:12 mount_debugfs.sh
-rwxr-xr-x root shell 17856 2012-09-27 05:16 mtpd
lrwxr-xr-x root shell 2012-05-25 02:17 mv -> toolbox
lrwxr-xr-x root shell 2012-05-25 02:17 nandread -> toolbox
-rwxr-xr-x root shell 5304 2012-09-27 05:16 ndc
-rwxr-s--- root inet 5484 2012-09-27 05:16 netcfg
-rwxr-xr-x root shell 71200 2012-09-27 05:16 netd
lrwxr-xr-x root shell 2012-05-25 02:17 netstat -> toolbox
lrwxr-xr-x root shell 2012-05-25 02:17 newfs_msdos -> toolbox
lrwxr-xr-x root shell 2012-05-25 02:17 notify -> toolbox
-rwxr-xr-x root shell 5304 2012-09-27 05:16 nv_hciattach
-rwxr-xr-x root shell 13492 2008-08-01 07:00 nvcap_test
-rwxr-xr-x root shell 5424 2008-08-01 07:00 nvremotell
-rwxr-xr-x root shell 5420 2012-09-27 05:16 nvtest
-rwxr-xr-x root shell 18188 2012-09-27 05:16 pand
-rwxr-sr-x root net_raw 26056 2012-09-27 05:16 ping
-rwxr-xr-x root shell 191 2012-05-25 02:12 pm
-rwxr-xr-x root shell 141868 2012-09-27 05:16 pppd
-rwxr-xr-x root shell 141868 2012-09-27 05:16 pppd_btdun
lrwxr-xr-x root shell 2012-05-25 02:17 printenv -> toolbox
lrwxr-xr-x root shell 2012-05-25 02:17 ps -> toolbox
-rwxr-xr-x root shell 1014 2012-09-27 05:16 ps3service
-rwxr-xr-x root shell 5320 2012-09-27 05:16 python
-rwxr-xr-x root shell 166808 2012-09-27 05:16 racoon
lrwxr-xr-x root shell 2012-05-25 02:17 reboot -> toolbox
lrwxr-xr-x root shell 2012-05-25 02:17 renice -> toolbox
-rwxr-xr-x root shell 188 2008-08-01 07:00 requestsync
lrwxr-xr-x root shell 2012-05-25 02:17 rm -> toolbox
-rwxr-xr-x root shell 5376 2008-08-01 07:00 rm_ts_server
lrwxr-xr-x root shell 2012-05-25 02:17 rmdir -> toolbox
lrwxr-xr-x root shell 2012-05-25 02:17 rmmod -> toolbox
lrwxr-xr-x root shell 2012-05-25 02:17 route -> toolbox
-rwsr-s--- root shell 9448 2012-09-27 05:16 run-as
-rwxr-xr-x root shell 5304 2012-09-27 05:16 schedtest
lrwxr-xr-x root shell 2012-05-25 02:17 schedtop -> toolbox
-rwxr-xr-x root shell 9396 2012-09-27 05:16 screencap
-rwxr-xr-x root shell 34168 2012-09-27 05:16 screenshot
-rwxr-xr-x root shell 13600 2012-09-27 05:16 sdcard
-rwxr-xr-x root shell 45920 2012-09-27 05:16 sdptool
-rwxr-xr-x root shell 173 2008-08-01 07:00 send_bug
lrwxr-xr-x root shell 2012-05-25 02:17 sendevent -> toolbox
-rwxr-xr-x root shell 13492 2012-09-27 05:16 sensors-config
-rwxr-xr-x root shell 5352 2012-09-27 05:16 sensorservice
-rwxr-xr-x root shell 13544 2012-09-27 05:16 service
-rwxr-xr-x root shell 9608 2012-09-27 05:16 servicemanager
lrwxr-xr-x root shell 2012-05-25 02:17 setconsole -> toolbox
lrwxr-xr-x root shell 2012-05-25 02:17 setprop -> toolbox
-rwxr-xr-x root shell 5352 2008-08-01 07:00 setup_fs
lrwxr-xr-x root shell 2012-05-25 02:17 sh -> mksh
-rwxr-xr-x root shell 9524 2012-09-27 05:16 sixpair
lrwxr-xr-x root shell 2012-05-25 02:17 sleep -> toolbox
lrwxr-xr-x root shell 2012-05-25 02:17 smd -> toolbox
-rwxr-xr-x root shell 46364 2012-09-27 05:16 stagefright
lrwxr-xr-x root shell 2012-05-25 02:17 start -> toolbox
lrwxr-xr-x root shell 2012-05-25 02:17 stop -> toolbox
-rwxr-xr-x root shell 5352 2012-09-27 05:16 surfaceflinger
-rwxr-xr-x root shell 192 2012-05-25 02:12 svc
lrwxr-xr-x root shell 2012-05-25 02:17 sync -> toolbox
-rwxr-xr-x root shell 5300 2012-09-27 05:16 system_server
-rwxr-xr-x root shell 67096 2012-09-27 05:16 tc
-rwxr-xr-x root shell 17640 2012-09-27 05:16 tegrastats
-rwxr-xr-x root shell 13904 2012-09-27 05:16 tf_daemon
-rwxr-xr-x root shell 104964 2012-09-27 05:16 toolbox
lrwxr-xr-x root shell 2012-05-25 02:17 top -> toolbox
lrwxr-xr-x root shell 2012-05-25 02:17 touch -> toolbox
-rwxr-xr-x root shell 91820 2012-09-27 05:16 touch_fw_update
-rwxr-xr-x root shell 3391 2008-08-01 07:00 uiautomator
lrwxr-xr-x root shell 2012-05-25 02:17 umount -> toolbox
lrwxr-xr-x root shell 2012-05-25 02:17 uptime -> toolbox
-rwxr-xr-x root shell 5304 2012-09-27 05:16 vdc
lrwxr-xr-x root shell 2012-05-25 02:17 vmstat -> toolbox
-rwxr-xr-x root shell 75288 2012-09-27 05:16 vold
lrwxr-xr-x root shell 2012-05-25 02:17 watchprops -> toolbox
-rwxr-xr-x root shell 9480 2012-09-27 05:16 wifimacwriter
lrwxr-xr-x root shell 2012-05-25 02:17 wipe -> toolbox
-rwxr-xr-x root shell 45904 2012-09-27 05:16 wminput
-rwxr-xr-x root shell 608680 2012-09-27 05:16 wpa_supplicant
-rwxr-xr-x root shell 21788 2012-09-27 05:16 wvdrmserver
-rwxr-xr-x root shell 17644 2012-09-27 05:16 xaplay
shell@android:/system # ls -l /system/xbin
ls -l /system/xbin
-rwxr-xr-x root shell 59760 2012-09-27 05:19 dexdump
-rwx------ root root 5380 2012-09-27 05:19 ps3bttest
-rwxr-xr-x root shell 23592 2012-09-27 05:19 rfcomm
-rwxr-xr-x root shell 22364 2012-06-13 13:11 su
shell@android:/system # ls -l /system/Supruser.apk
ls -l /system/Supruser.apk
/system/Supruser.apk: No such file or directory
1|shell@android:/system # ls -l /system/superuser.apk
ls -l /system/superuser.apk
/system/superuser.apk: No such file or directory
1|shell@android:/system #

edit: BTW I don't have busybox or superuser installed. One of the first things I tied to do was uninstall them and reinstall.
 
Last edited:
You must log in or register to reply here.

Similar threads

flumpster
[ROM][May 13][JB 4.2.1] AndroWook Prime Hairy Bean v2.2 **Unleash The Beast!**
Replies
10K
Views
1M
S
sachinkumar1312
sparkym3
[ROOT][TOOL]Debugfs automated root [09/18/2012]
Replies
972
Views
728K
D
diaboulo
-viperboy-
[TOOL][Updated 5.9.12]viperMOD PrimeTime v4.6 | Auto Root/Unroot/Busybox/CMW Flash!
Replies
2K
Views
658K
E
evan661212000101
sparkym3
[TOOL][APK ROOT]SparkyRoot Apk root method
Replies
247
Views
453K
N
nixtip
T
[ROM] [TF201] KatKiss 5.1.1 - v30 [MultiWindow] [Stable] [RRO]
Replies
1K
Views
352K
F
Fytdyh

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 29
    T
    thenrz
    This will only work if you can access a root prompt (#) in adb shell! THIS WAS DONE AFTER DOING A WIPE FROM THE VOLUME DOWN MENU WHEN BOOTING THE PRIME! I do not know if this will work without the wipe, but it very well may. Maybe someone more knowledgeable can chime in here.

    It may be possible to restore from a su-backup if you have a su binary still in /system/bin or xbin. Even if you can't access a root prompt (#) by just typing su, read starting at page 6. Places to look for a su-backup include /system/ /system/usr/we-need-root/ and /system/bin/

    I have a batch script in the works that will determine if you can re-root and take the appropriate steps to do so if possible.

    I had to do a voldown wipe after my update to JB. My prime would reboot after 5-10 seconds into the homescreen after boot. After wiping, I thought for sure my root was screwed until a new exploit was found.

    I accessed my device through adb, and realized that I could invoke a root prompt using the su command at the $ prompt. Using ES file explorer, I could see su in /system/bin/ but no su-backup or superuser.apk in /system/app/.

    I tried simply installing superuser from the market, but it did not work. The busybox installer would not work, either.


    ATTACHED ARE THE EXACT THREE FILES I USED. I do not know if using different version will affect the process!

    Here is what worked for me:

    1. adb shell
    2. su
    (# - you should see this now! This will not work without this specific prompt!)
    3. type 'exit' press enter, and then 'exit' again. You will now be back at the regular command prompt.
    4. adb push C:\(location of attached files)\superuser.apk /data/local/tmp
    5. adb push C:\(location of attached files)\su /data/local/tmp
    6. adb push C:\(location of attached files)\busybox /data/local/tmp
    7. Access the adb shell again, and type su
    8. chmod 644 /data/local/tmp/superuser.apk
    9. chmod 755 /data/local/tmp/busybox
    10. chmod 6755 /data/local/tmp/su
    11. mount -o remount,rw /system
    12. dd if=/data/local/tmp/Superuser.apk of=/system/app/Superuser.apk
    13. dd if=/data/local/tmp/busybox of=/system/bin/busybox
    14. dd if=/data/local/tmp/busybox of=/system/xbin/busybox
    14a. Chmod 755 /system/bin/busybox
    14b. Chmod 755 /system/xbin/busybox
    15. Reserved
    16. busybox rm /system/bin/su
    17. busybox cp /data/local/tmp/su /system/bin
    18. type su once again to assure you still have access to the # prompt
    18a. Chmod 644 /system/app/superuser.apk
    18b. mount -o remount,ro /system
    19. type exit, and exit again, returning to the regular windows command prompt.
    20. type 'adb reboot' (without quotes)
    NOTE - you will not need to install the superuser.apk app in the normal sense. It will be installed upon the reboot as a system app automatically!
    21. Once your prime has rebooted, go download root checker basic or the like from the play store. Open it, and wait for your superuser prompt! :)
    22. Get the busybox installer from the play store as well, and use that to get the newest version of busybox.
    23. Get SuperSU from the market. It seems to be the safest method to keep root with JB...

    ALSO! Make sure to keep a backup root with voodoo or super su after completing this guide! I have lost root (VERY WELL may have been my own fault... too much poking around) Anyway, better safe than sorry!!!

    Thanks to daymz from the debugfs thread in development for the basic instructions of what needed to be done!! And also thanks to all before me who got us root in the first place!


    I will answer questions to the best of my ability. I am not a developer and do not try to present myself as so... I can tinker with the best, and after losing root, I set out to see if I could figure it out!

    Changes made as per tsmt971
    View
    5
    T
    tsmt971@yahoo
    I have fellow this method and it was failed at step 16 in my case because of the permission issue but I managed to make it move and regained the root. The details of the issue as below.

    Step 16 failed because step 13, 14 which will copy busybox to /system/bin and /system/xbin with a wrong executive permission.
    To correct in my case: after step 13, 14 follow those steps below:
    - chmod 755 /system/bin/busybox
    - chmod 755 /system/xbin/busybox
    - skip step 15
    - continue steps 16, 17, 18
    - chmod 644 /system/app/Superuser.apk
    - continue step 19, 20, 21, 22

    Then you will get your root back, it worked in my case. Good luck guys.
    To the OP, please verify and update those steps if necessary.
    View
    4
    T
    thenrz
    I just figured something out. I found a su-backup in /system/usr/we-need-root . I have lost root again since making this guide. My permissions were screwed up on su. I was able to restore root by doing the following:

    Code: 
    adb shell:
$ cd /system/usr/we-need-root
$./su-backup; su  (that is a semicolon immediately after the ./su-backup)
# mount -o remount,rw /system
(do what needs to be done)
#exit
...

    su-backup must have permissions as such: (get permissions by typing this into adb shell: ls -l /system/usr/we-need-root ) If you get an error, than this specifically won't work for you.

    Code: 
    Required su-backup permissions for manual root restore
$ ls -l /system/usr/we-need-root/su-backup
-rwsr-sr-x  root  ...

    basically, if you can find a su-backup with proper permissions (and cannot restore root with voodoo or supersu), you can manually use that to repair your root access configuration. Maybe this is well known... but to those who don't this could be useful.
    View
    1
    hx4700 Killer
    hx4700 Killer
    tontorus said:
    Wait, let me get this straight. You're saying right now there's no way for many of us to get a root access to our devices if the abovementioned method is not working, right?
    Click to expand...
    Click to collapse

    As far as I know, unless someone is keeping a HUGE secret.

    I should mention the unlocker from ASUS but i don't know if anyone has tried it on JellyBean
    View
    1
    hx4700 Killer
    hx4700 Killer
    Same Boat:
    shell@android:/system/xbin $ ls -l
    ls -l
    -rwxr-xr-x root shell 497964 2012-09-26 21:25 busybox
    -rwxr-xr-x root shell 59760 2012-09-27 11:18 dexdump
    -rwx------ root root 5380 2012-09-27 11:18 ps3bttest
    -rwxr-xr-x root shell 23592 2012-09-27 11:18 rfcomm
    -rwxr-xr-x root shell 380532 2012-09-26 21:04 su

    This is my output when I type SU

    shell@android:/system/xbin $ su
    su
    1|shell@android:/system/xbin $
    View

New posts