yashsingh1/xdaforums huggingface dataset:
[Asus  Eee Pad Transformer Prime] miloj:
Can you send me the result of the commands (in adb shell):

ls -l /system/*/su

echo $PATH

---------- Post added at 05:46 PM ---------- Previous post was at 05:45 PM ----------

Oh ok, I see what it is. Let me find a way to solve this quickly.

EDIT: The problem comes from OTA RootKeeper in my opinion, it does a "chattr +i /system/xbin/su" to prevent Asus OTA to overwrite or delete the file.

Here is the trick to solve it, very simple, insert the command "rm su" before the write command, like this:

debugfs: cd xbin

debugfs: rm su

debugfs: write /data/local/su su

debugfs: set_inode_field su mode 0104755

debugfs: set_inode_field su uid 0

debugfs: set_inode_field su gid 0

debugfs: quit

Will update my OP.
[Asus  Eee Pad Transformer Prime] sparkym3:
Yes, it would be interesting to see these permissions. Normally I would say, if "su" already exists in xbin, you could always write the new "su" file to bin instead. Then, call it explicitly to get a root terminal and remove the one from xbin.

Theoretically, you should be able to do everything in the manual process, but skip the line "cd xbin", this way you stay in the /system directory. It should then write su to that directory and give it permission. Once you reboot, you should then be able to call "/system/su" and get a root terminal (then remove the su files from the other bin folders, which would allow you to copy the correct one into those folders and set their permissions).
[Asus  Eee Pad Transformer Prime] Gremlin001:
Here you go miloj:

C:\rooting>adb shell

shell@android:/ $ ls -l /system/*/su

ls -l /system/*/su

-rwxr-xr-x root shell 22364 2012-03-05 16:03 su

shell@android:/ $ echo $PATH

echo $PATH

/sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin

shell@android:/ $

update: just saw miloj's update - I'll give it a shot and report back.
[Asus  Eee Pad Transformer Prime] bimbobo:
I am rooted, and SU is also installed, do I have to uninstall or delete anything before using your tool?
[Asus  Eee Pad Transformer Prime] SteveG12543:
Got it to work on the .28 beta, thanks!
[Asus  Eee Pad Transformer Prime] Gremlin001:
Seemed to work - New log file:

C:\rooting>adb shell

shell@android:/ $ ls -l /system/*/su

ls -l /system/*/su

-rwxr-xr-x root shell 22364 2012-03-05 16:03 su

shell@android:/ $ echo $PATH

echo $PATH

/sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin

shell@android:/ $ exit

exit

C:\rooting>adb push debugfs /data/local/

881 KB/s (1862336 bytes in 2.062s)

C:\rooting>adb push su /data/local/

1397 KB/s (22364 bytes in 0.015s)

C:\rooting>adb shell

shell@android:/ $ cd /data/local/

cd /data/local/

shell@android:/data/local $ mv tmp tmp.back

mv tmp tmp.back

shell@android:/data/local $ ln -s /dev/block/mmcblk0p1 tmp

ln -s /dev/block/mmcblk0p1 tmp

shell@android:/data/local $ exit

exit

C:\rooting>adb reboot

C:\rooting>adb shell

shell@android:/ $ cd /data/local

cd /data/local

shell@android:/data/local $ rm /data/local/tmp

rm /data/local/tmp

shell@android:/data/local $ mv /data/local/tmp.back /data/local/tmp

mv /data/local/tmp.back /data/local/tmp

shell@android:/data/local $ chmod 755 /data/local/debugfs

chmod 755 /data/local/debugfs

shell@android:/data/local $ /data/local/debugfs -w /dev/block/mmcblk0p1

/data/local/debugfs -w /dev/block/mmcblk0p1

debugfs 1.42 (29-Nov-2011)

debugfs: cd xbin

cd xbin

debugfs: rm su

rm su

ext2fs_block_alloc_stats: Illegal block number: 1937339183

ext2fs_block_alloc_stats: Illegal block number: 795698548

ext2fs_block_alloc_stats: Illegal block number: 1852400248

ext2fs_block_alloc_stats: Illegal block number: 1937072687

ext2fs_block_alloc_stats: Illegal block number: 2020565625

debugfs: write /data/local/su su

write /data/local/su su

Allocated inode: 8514

debugfs: set_inode_field su mode 0104755

set_inode_field su mode 0104755

debugfs: set_inode_field su uid 0

set_inode_field su uid 0

debugfs: set_inode_field su gid 0

set_inode_field su gid 0

debugfs: quit

quit

shell@android:/data/local $ exit

exit

C:\rooting>adb reboot

C:\rooting>adb shell

shell@android:/ $ /system/xbin/su

/system/xbin/su

shell@android:/ # id

id

uid=0(root) gid=0(root) groups=1003(graphics),1004(input),1007(log),1009(mount),

1011(adb),1015(sdcard_rw),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw

_stats)

shell@android:/ # exit

exit

shell@android:/ $ rm /data/local/su

rm /data/local/su

shell@android:/ $ rm /data/local/debugfs

rm /data/local/debugfs

shell@android:/ $ exit

exit

C:\rooting>

Superuser still says it does not have permission and Root Checker says it is still not rooted. I'm going to do a manual reboot. BRB

Update: Nope, no root here.
[Asus  Eee Pad Transformer Prime] sparkym3:
If you really did see a version of the su file in the bin directory also, you will want to run the rm command on it as well.
[Asus  Eee Pad Transformer Prime] Gremlin001:
I'll give that a try. Thanks Sparky.
[Asus  Eee Pad Transformer Prime] sparkym3:
Now that I know that the rm command works, I will add it to the default flow so that it tries to delete su before trying to write it again. This should catch the cases where su is left behind but not working, and the command should just fail for those who don't have it left behind.
[Asus  Eee Pad Transformer Prime] Gremlin001:
We need a "fat guy happy dance" smiley. Miloj and Sparkym3, you guys are tops!! I now have root. Thanks for all the help.

*whew*

It was the "su" in the /system/bin/ folder that f*$%ed it up. One of the best parts of this exercise was I pretty much have that manual method memorized now. Next step is to understand it. :D nahhhhh .... I don't wanna git all techie on me bad self...:eek:

Update with some advice: Heed the advice to use VooDoo Rootkeeper. Once rooted you have to run it to protect the root. Just don't ask me how I know! :o
[Asus  Eee Pad Transformer Prime] aznmode:
I updated my Prime via US_epaduser9_4_2_28UpdateLauncher.zipfrom asus website ( since it originally failed on OTA due to modded build.prop) and tried rooting with your v1.7 and got this result.

I had to run the 1.7 several times till I decided to the following:

Checked OTA rootkeeper and it said I wasnt rooted and no superuser so I went to market and installed superuser and busybox. Opened superuser and it asked if I wanted to allow superuser request. Allowed it and did the same for busybox (just incase). Went to OTA rootkeeper and protected root.

Thanks OP. Glad I have root again.

I had to run the 1.7 several times till I decided to the following:

Checked OTA rootkeeper and it said I wasnt rooted and no superuser so I went to market and installed superuser and busybox. Opened superuser and it asked if I wanted to allow superuser request. Allowed it and did the same for busybox (just incase). Went to OTA rootkeeper and protected root.

Thanks OP. Glad I have root again.
[Asus  Eee Pad Transformer Prime] sparkym3:
Thanks for the info, I have added a tip about it in the OP.
[Asus  Eee Pad Transformer Prime] bazzio:
just rooted my TF300T .29 ww successfully after some trouble this morning, so big thanks to miloj and sparky.... Needed to terminate Asus sync in PC.

just one question: is Rootkeeper necessary?
[Asus  Eee Pad Transformer Prime] sparkym3:
Rootkeeper is needed to keep the root on the next update if Asus patches the exploit that is being used.

If they don't patch the update, then you would be able to re-root, but why take that chance.
[Asus  Eee Pad Transformer Prime] livin.legend:
Thanks man.. worked like a charm. Prime is rooted :)
[Asus  Eee Pad Transformer Prime] lartomar2002:
I am still on .26 firmware though I still get prompts every hour or so to update even though I have selected to postpone for 1 day, any way to turn this off? When you say uninstall the drivers you are talking about the ones in the Asus on the Device mgr ? I believe I will unlock the bootloader and install nvflash if I can ever figure it out. I installed it on my Viewsonic G tab and it saved my but a couple of times.
[Asus  Eee Pad Transformer Prime] lt thistle:
The version I used would prompt you too install drivers even if you already had them installed. But an easy way to check is to open a cmd window and adb devices, if it's listed you know your drives are good.
[Asus  Eee Pad Transformer Prime] Bait-Fish:
I froze DMClient with Titanium Backup on my Prime. Haven't had an update message since.
[Asus  Eee Pad Transformer Prime] louiscar:
Also as you don't mention it, did you enable usb debugging? If you didn't then check enable it in developer options and in the folder with debugfs open a command window and confirm that adb can see your device. Type : adb devices.
[Asus  Eee Pad Transformer Prime] dhonzik:
Any news on a root method for JB yet?
[Asus  Eee Pad Transformer Prime] taaz69:
I'd be interested in knowing as well. I have the TF700 on 4.1.1. Doesn't seem to be a method to root this out there.
[Asus  Eee Pad Transformer Prime] lartomar2002:
yep, I had usb debug enabled. Anyways, I. am now unlocked, rooted and have TWRP recovery installed. I am still on version. 28 because I want to install nvflash. I. am still having issues with adb. My device manager shows that I have the most up to date adb drivrrs and. I would not have been able to use debugfs to root. When I. open the command window and type "adb devices' it says it does not recognize the command. Open to any suggestions. I will not be moving on to other roms until. I have nvflash installed. I have it set up for my other android tablet and it has saved my butt a couple of times.
[Asus  Eee Pad Transformer Prime] sparkym3:
I have been away, but I wanted to make sure false information was not getting out there and to answer a question.

NO, you do not need to be unlocked to root with this method, that statement was false.

This method only works on ICS not JB. The only current way I have seen to root JB directly would be to unlock and just flash the root update.

If another root method is found, I will make sure to post that update to this thread so that those watching the thread will know.
[Asus  Eee Pad Transformer Prime] lartomar2002:
Thanks, that worked:D
[Asus  Eee Pad Transformer Prime] jwebster:
OP Sparkm3 this tool made the rooting step in the ascension of my TF3T a snap! Thanks much!! Have a cold one on me! 7UF19701S06023736.
[Asus  Eee Pad Transformer Prime] louiscar:
Well that sounds very much like adb isn't in the path. You can add your adb.exe to the path or make sure you open a command window in the same folder as adb. You should not get a 'not recognized' message. If adb can't see your device it'll just return a blank line.
[Asus  Eee Pad Transformer Prime] JerseySprint:
Deleted after I finished my morning cofee and actualy read the instructions again:)
[Asus  Eee Pad Transformer Prime] sparkym3:
Some were seeing this if they run the .bat as administrator. The .bat does not need to be run as administrator.
[Asus  Eee Pad Transformer Prime] Flashben:
The reason i choose your tool is because it does not require to unlock in order to root. Many of us just want to root in order to use some of the apps that works only on root devices...

I just got back one of my tf300tg after repair and asus update it to jb and remove my root.... waiting for your tool to update to be able to root jb....
[Asus  Eee Pad Transformer Prime] Lock-N-Load:
I "had" root with this tool on my ICS TF201 since day 1.. then the JB release bricked my Prime and thus, killed my root as I had to send the POS tablet back to Asus to fix it (love to see them loosing money on all of the cost and time and effort to fix tablets they bricked with that update). The point is, I don't want to unlock my bootloader until after warranty is up because here is a prime example where if I had, I would have been asked to pay to fix my Prime that their updater bricked just for being unlocked.

So, I don't plan to use any root method that requires unlocking. Just want root.

(but then again, I have been thinking about selling my Prime and getting out from under it)
[Asus  Eee Pad Transformer Prime] atamig:
I have open the bootloader and bricked my tf700 and pay 400.--€ to asus. Now i want only root without open the bootloader. I hope for the new

rootdebug method for JB
[Asus  Eee Pad Transformer Prime] louiscar:
and to atamig

It is a piece of cake to downgrade to ICS. It'll take you both 10 mins, once you've done that, factory reset and root. Load Voodoo OTA and preserve root, then upgrade to JB, download Voodoo and restore root. Done.

Otherwise you may have to wait a long time to see a root method for JB.
[Asus  Eee Pad Transformer Prime] fuzzynco:
How does one do the downgrade to ics??

I thought one had to unlock the boot loader to change the firmware?

Currently on JB with locked (never unlocked) boot loader and rooted

via OTA root keeper from ICS. I'd never have updated, if I'd known the

JB issues, :(

I didn't / don't want to unlock boot loader and get black listed for

warranty purposes though. Personally, I think that is a bad service

policy :(.

I think hardware that fails due to defects in materials, regardless of'

firmware / software should still be covered, :confused:

PS: I have adb.exe (and its DLLs) and fastboot.exe in my path.

I have 2 HTC Android phones (ICS and GB) [both are s-off / rooted]

and 1 HTC tablet (HC) [s-off / rooted], as well as a TF300T (JB)

[NOT unlocked / rooted]. All drivers for all Android devices

seem to find the appropriate device (adb boot / adb recovery

adb bootloader / fastboot bootloader) modes all as expected.
[Asus  Eee Pad Transformer Prime] vittogn:
Can you please link me to the instructions to go from JB to ICS. I can only find an old one that allow to move between various ICSs and go back to HC from ICS.

I'm now on a rooted JB, but I want to wipe to see if performance will improve.

Thanks.
[Asus  Eee Pad Transformer Prime] Lock-N-Load:
I would also like to investigate this. I get my TF201 back from Asus today as JB bricked it and I assume they will have upgraded it to JB and thus, killed my root.

So, I would like to go back to ICS. Wipe. Root. Save root. Upgrade to JB. Return root.
[Asus  Eee Pad Transformer Prime] Flashben:
Thx for the suggestion but i don't want to unlock my bootloader it order to get root since i dont want to Change my ROM.

I have change the ROM for my htc sensation, end up nt very stable recently. So i wont want to touch any rom for tf pad....
[Asus  Eee Pad Transformer Prime] lartomar2002:
I know it is probably very simple but I have never learned about "something not being in the path" or how add something to a path or how to open a command window from within a folder. A friend installed adb for me before but my HDD died and I did not have that backed up.
[Asus  Eee Pad Transformer Prime] thekayman:
just make sure you are running the command in the same directory as to where adb is i.e. if you have adb in c:\android then make sure you change to c:\android by typing CD \ANDROID
[Asus  Eee Pad Transformer Prime] louiscar:
No you don't have to unlocked.

Follow the instructions here:

http://xdaforums.com/showthread.php?t=1833212

---------- Post added at 05:51 AM ---------- Previous post was at 05:50 AM ----------

No you don't have to unlocked.

Follow the instructions given in this thread:

http://xdaforums.com/showthread.php?t=1833212

---------- Post added at 05:53 AM ---------- Previous post was at 05:51 AM ----------

Follow the instructions in this thread, choose the method depending on what your circumstances are:

http://xdaforums.com/showthread.php?t=1833212

---------- Post added at 05:56 AM ---------- Previous post was at 05:53 AM ----------

You don't have to unlock. Go here, read and perform the factory reset / revert to .30 section.

http://xdaforums.com/showthread.php?t=1833212

I am locked and did it in about 10 mins and went back to JB after factory resetting and re-rooting.

---------- Post added at 06:03 AM ---------- Previous post was at 05:56 AM ----------

If you are running windows 7 I believe you can right click and choose open a command window here. Do that in the folder where adb is.

If running windows xp or earlier you can make a little batch file for convenience. Fire up your text editor and type the following two lines:

cmd

cd .

Then save the file as cm.bat or anything other (but NOT cmd.bat). Make sure that is saved in the same folder as adb. Double click the bat file.

Adb doesn't require installation, if you don't know where it is or don't have it you can get it from this forum in a form which can just be run from a folder. I believe it comprises of 3 files, 1 .exe and 2 .dlls. The other way is to get the sdk and install that but that's overkill just to get at the 3 files you need.

**** Apologies to all for lumping all replies in one post - I don't actually know why it's happening or how to turn it off :) ***
[Asus  Eee Pad Transformer Prime] beckzz:
As i wrote in the other thread:

Atm you cant switch back to ICS after updating to jb, unless you have the following prerequisites:

- unlocked device

- nvflash files created while you were on ics

The bootloader changed with the JB update, and you cant flash that without nvflash...

And currently nvflash is not working in JB...so youll have to wait...

Grz
[Asus  Eee Pad Transformer Prime] kerapil:
so, who's right? You or the previous poster?
[Asus  Eee Pad Transformer Prime] beckzz:
so i took a look at the facts again and im pretty sure that i'm right ^^

So this is, what you can read in the linked threads too:

NVFlash:

- to use nvflash you definetly need an unlocked device

Root ICS-Stock (locked device):

- Use the method described in the linked thread, there is no problem at all

Root JB-Stock (locked device):

- IF you backed up your root with OTARootkeeper while on ICS, you can restore it after the JB Update

- IF NOT you have no more options as long as your device is locked

Root JB-Stock (unlocked device):

- maybe there is a method to flash it via recovery, but im not sure ..

- IF you have NVFlash enabled while you were on ICS, and backed up your files, you can switch back to ICS with this, root ICS, backup with OTA rootkeeper, update to JB again and restore root

All in all: IF your device is on stock jb, locked and root not backed up in ics there is NO method atm to get root OR go back to ICS

or IF your device is on stock jb, unlocked but you dont have nvflash-ics-backup-files, there is no way to go back to ICS

So i really read a lot about it, i have no nvflash-ics-backup-files myself, and i never read anything else than what i described above.

So if i missed something, correct me, but im pretty sure thats not the case.

Btw: IF you are unlocked, why are you still using stock-rom? i'm unlocked myself and first thing i did, was wiping the crappy stock-rom...im "stuck" in JB bootloader too, but AndroWook-HairyBean is working like a charm, so there is no need to switch back to ICS in my eyes..
[Asus  Eee Pad Transformer Prime] vittogn:
Can I rephrase in this way?

"- IF you backed up your root with OTARootkeeper while on ICS, you can restore it after the JB OTA Update"

and add:

- IF you backed up your root with OTARootkeeper while on ICS and restored it after JB OTA Update, you can not do a full wipe if u want to keep root

Is it correct?
[Asus  Eee Pad Transformer Prime] beckzz:
hey,

"- IF you backed up your root with OTARootkeeper while on ICS, you can restore it after the JB OTA Update"

-> you can restore root even after manual flash of JB-Update, did it myself (Trekest method)

"- IF you backed up your root with OTARootkeeper while on ICS and restored it after JB OTA Update, you can not do a full wipe if u want to keep root"

-> yes, i think thats the way it is, at least if you use "factory reset" from settings.

But i remember, that i wiped the device after jb update and was able too restore root again with this:

boot with power and volume down, selected "wipe data" from the 4 icons,booted system again and then was able to restore root with ota rootkeeper. but please dont try this if nobody can confirm, im not 100% sure, cause its been a while and i did so much flashing since then...its poosible that i mess things up at this point..
[Asus  Eee Pad Transformer Prime] fuzzynco:
Still confused TF300T / JB / Locked with Root from ICS (Rootkeeper)

I've seen various answers and I'm still confused. The Wheelie / NVRAM tool set only

operates on unlocked stock ICS if I understood correctly. I'm guessing there is a

way unlock and flash ICS complete system (like an OOB)? That would have the

ICS bootloader and ROM that Wheelie needs?

One of the posts replies said reverting to ICS was simple (I think it said a 10 min process)?

I thought locked devices could not go backwards? I'm guessing, again, the poster was

referring to an unlocked bootloader on jellybean?

My intent was to use NVRAM to low level backup the pad, If I understand correctly I need

to be unlocked and on ICS for the tool set to work? Is that correct? :confused:

I currently am on JB, never unlocked, with root from OTA Rootkeeper, after update to JB.

Is there a path for me? :confused: Is a JB solution possible?

[rant]

Ideally, I'd have preferred not to unlock, as I really only need root for various root apps.

I do not like ASUS's warranty rules regarding unlocked devices. I understand the

reason for the idea, for it for firmware / software induced issues, but true factory

defects have absolutely nothing to do to firmware / software issues. Mechanical

failures should still be covered. The blacklisting is really bad policy.

[/rant]
[Asus  Eee Pad Transformer Prime] vittogn:
Thanks for the hope!!

As after a wipe there will be nothing on my tab, what have I to do (a part from installing Voodoo OTA RootKeeper from the market)?

Have I to save a specific folder on a separate drive and copy it back to the prime memory?

OT: I hope the Nexus 10 will have the rumors screen resolution, to get rid of the Prime!!!
[Asus  Eee Pad Transformer Prime] beckzz:
"The Wheelie / NVRAM tool set only operates on unlocked stock ICS if I understood correctly."

-> correct (but the right term would be: unlock & ICS Bootloader is required, the OS can be stock, or custom rom...)

"I'm guessing there is a way unlock and flash ICS complete system (like an OOB)? That would have the ICS bootloader and ROM that Wheelie needs? "

-> you are answering your question correctly: "I understand correctly I need to be unlocked and on ICS for the tool set to work" -> Yes, at least the very first time - to create the nvflash-files

"I thought locked devices could not go backwards? I'm guessing, again, the poster was referring to an unlocked bootloader on jellybean"

-> Yes, he referres to an unlocked Bootloader and he assumes you have your nvflash-files from ics...

"I currently am on JB, never unlocked, with root from OTA Rootkeeper, after update to JB."

-> depends on what you want to to...you can still unlock with the unlock tool, even with jb, but you can only use roms based on the new JB-Bootloader - you'll not be able to go back to ICS or backup your prime with nvflash

Backup everything you need from your internal memory (pictures, music, porn...stuff like that ;)).

All the Asus Apps and other bloatware will be installed after wipe...everything thats included inthe stock-rom.

but as i said before, atm im not sure, if you'll be able to restore root after wiping the way i described it.

So try it on your own risk, if you want to.

Grz
[Asus  Eee Pad Transformer Prime] vittogn:
Thanks beckzz.

It is more than clear to me to back all my data.

The only doubt I have is related to OTA RootKeeper. This app is able to copy an obtained root and restore it. If I wipe the prime, it will not be able to restore a root that it never copied before! I was wondering if I can save what the app currently backed up (a folder??) and restore after full wipe to allow OTA RootKeeper to restore root.