Database Info

[Q] Transformer (B60) Android 3.2 Rooting Issue?

I've just followed the guide to rooting the TF101 in One Click, via the Linux Boot method. It really is a brilliant application that was put together with the intention to save one a lot of time, however, although it tells me it has successfully completed and asks that I reboot the unit and to ensure that USB debugging is enabled, when I load Rom Manager it complains that it is not rooted. When I try to access terminal, I get the $, instead of the # and this does not change whether I Su, Sudo Su, Sudo Bash etc. In fact, I get Access Denied. Has anyone any recommendation?

Do you have the app "superuser" installed? If not, go to the market downlod and install it.
Sent from my Revolver powered Asus Transformer

Ah! I have not. There's always something missing Thanks much, I will give it a shot!

No Joy
Ouch...I was certain that that would have done the trick.

...
I think the problem is that the superuser app wants to install an SU update but it fails and tells me that the zip file has been placed on my SD and to flash it, of course, that's kind of counter productive, considering that I need superuser to work, in order to be able to flash the superuser update.

[Q] My phone obviously has root... but not according to the shell. Need some help!

Hello xda, I have a bit of a problem:
I have a Samsung Exhibit which I rooted using the zergRush method found here on the forums. At first everything worked fine. But recently I was trying to push a modified system app to my phone using adb and it told me the action wasn't permitted. Checking the shell, and terminal emulator on my phone to see if I had superuser permissions failed. So I went about trying to root my phone again, which according to the zergRush script said was successfull, but checking the shell once again showed that I still did not have superuser permissions. I did a factory wipe of my phone in hopes of trying to get it to root again with no success. But here's the weird part, although it doesn't appear I have root access all my apps that require root access (titanium backup, my screenshot app, and some of widgetlocker's features) still fully function.....
Does anyone have any idea what's going on here? I would love my system folder access back
Thanks in advance.

Dumb question, but your H-Boot shows S-Off? Just covering the bases... Also, do you have Super User installed and functional?

To be honest... I don't know what H-Boot or S-Off means. Pretty new to all of this. Mind giving me a walkthrough? I have superuser installed yes. It's granting programs superuser permissions. But I can't access su in terminal emulator or in the shell.

Well, I'm not the top tier technical person here, so I'm not exactly sure on how to get your problem resumed, since I've not heard of that. On the other hand, there might be a different way to accomplish what you are trying to do.
What are you trying to achieve, pushing a modified system app to do what and where? My suggestion, might be to just put it on your phone through USB to the root folder and then move it in ES File manager, or w/e you use. If all you are doing is pushing.
Obviously ADB shell detects your device, but I'm not sure why it is saying it doesn't have SU access. My other suggestion is to redo the ADB/Android SDK installs. I had a problem where I installed them wrong, by installing too much and ADB did not work properly. So, there might be a chance your phone is fine, but the ADB/SDK are not proper, somehow.
Let me know.

If that were the case, and my phone was fine, wouldn't I be able to access super user through terminal emulator on my phone? Right now when typing su in terminal emulator, the pop up to grant superuser permissions appears but when you allow it to have su permission the # doesn't turn to a $ like it should. The more I think about it the more I think it's a problem with superuser. I've seen people talking about an update to superuser that can break your root? Mehhhh.

Seems like other have had this problem too... Not sure if a nandroid recovery will fix this, otherwise you might have to try to unroot, and then reroot.
Sorry, just might have to do a little more digging than I was able to. Good luck

TF700t and rooting

I've read the dedicated thread on rooting the TF700t with DebugfsRoot_v1.9 (http://forum.xda-developers.com/showthread.php?t=1706588&page=48).
I did successfully root a TF700t with 9_4_5_22.
Now I tried the same method after upgrading another TF700t from stock to 9_4_5_26.
Everything works fine during rooting (I've tried both manual and automated DebugfsRoot 1.9) with the following exceptions:
1. during the 3rd stage of rooting, I get
/system/bin/sh: /system/xbin/su: not executable: magic 7F45
2.
Superuser access does not seem to be active after rooting. I did uninstall and re-install Superuser with no superuser access success.
I tried both under XP and 7/32 on the same device, no errors but root does not seem to be active. Between rooting attempts, I restored stock ROM.
Other details:
Asus USB drivers installed (off Asus website)
Asus synch is disabled and prevented from launching.
Security/Unknown sources is checked.
Developer options / USB debugging is ON/checked.
What do you think goes wrong?
Any help is appreciated. Thx

the same..
I have nearly the same problem...
I have updated my rooted .21 to .26, then unlocked it and as it seems have lost root. I dont really know if it happened afted updating or afted unlocking...
None of my R-applications can get root, and so on...
I've tried to use the same method i used to get root on .21 and got this:
Step 2 - Rooting...
debugfs 1.42 (29-Nov-2011)
debugfs: rm: File not found by ext2_lookup while trying to resolve filename
debugfs:
debugfs: debugfs: Allocated inode: 1469
debugfs: debugfs: debugfs: debugfs:
Rebooting...
Testing superuser...
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)
uid and gid should both be 0.
Are they? (y/n):
Click to expand...
Click to collapse
And still no root...
What am i doing wrong? What to do next?
Thanks!

Is it a superuser problem?
EnginesRun said:
2.
Superuser access does not seem to be active after rooting. I did uninstall and re-install Superuser with no superuser access success.
Any help is appreciated. Thx
Click to expand...
Click to collapse
Can't help yet but I am having a similar problem with SU; its presence suggest I have root but it denies everyone else SU permissions...

After rooting, run SuperUser explicitly from the applications menu. Then try your apps that require root access. I noticed that I had the issue of running the DebugFS root batch and then later was not able to properly run Adaway. Ran SuperUser, then everything went smooth.
I think someone already mentioned this in another thread.

alienedd said:
After rooting, run SuperUser explicitly from the applications menu. Then try your apps that require root access. I noticed that I had the issue of running the DebugFS root batch and then later was not able to properly run Adaway. Ran SuperUser, then everything went smooth.
I think someone already mentioned this in another thread.
Click to expand...
Click to collapse
nope. doesnt help in my case..
---------- Post added at 10:17 AM ---------- Previous post was at 09:37 AM ----------
ok, i've solved my problem.
the idea mentioned by alienedd helped me to see that i could have a working root but faulty superuser app.
so i started with installing it from market.
then i ran DebugfsRoot_v1.9.
till it got to this point:
Testing superuser...
uid=0(root) gid=0(root) groups=1003(graphics),1004(input),1007(log),1009(m ount),1011(adb),
1015(sdcard_rw),3001(net_bt_admin),3002(net_bt),30 03(inet),3006(net_bw_stats)
uid and gid should both be 0.
Are they? (y/n):
Click to expand...
Click to collapse
then i have cleared all the data held by superuser app through settings\apps, stopped it and uninstalled.
after that i continued with the script and it installed me superuser app again.
after installing i've launched it and then ckecked my root-needed apps. they are ok now.

Ahhh, yeah. Read about that in the DebugFS thread that sometimes one needs to uninstall superuser then reinstall for it to run properly. Didn't think about that. Glad that its all working now for yas.

I have tried all of this with 4 different packages (3 of the automated root from here and 1 from a link in the [RESOURCES] thread in the dev forum. every time, each package says that I have root, but when I check I do now. I followed what masseselev said and it failed as well. I have spent the better part of 5 hours trying to root. I guess I should say that I just got my infinity last night...and like a crackhead applied .26 ota without thinking about it. but I have read where the automated works fine with .26. I am pulling my hair out trying to figure out why I cant get root on this thing. the packages always say that they were successful and that I have root, but I do not. no apps can gain root. terminal emulator still shows $ after trying to enter "su". I have tried several different root checkers and they all say I do not have root. any other ideas? I should also say that I have not unlocked the bootloader.

henbone11 said:
I have tried all of this with 4 different packages (3 of the automated root from here and 1 from a link in the [RESOURCES] thread in the dev forum. every time, each package says that I have root, but when I check I do now. I followed what masseselev said and it failed as well. I have spent the better part of 5 hours trying to root. I guess I should say that I just got my infinity last night...and like a crackhead applied .26 ota without thinking about it. but I have read where the automated works fine with .26. I am pulling my hair out trying to figure out why I cant get root on this thing. the packages always say that they were successful and that I have root, but I do not. no apps can gain root. terminal emulator still shows $ after trying to enter "su". I have tried several different root checkers and they all say I do not have root. any other ideas? I should also say that I have not unlocked the bootloader.
Click to expand...
Click to collapse
What exactly are you doing as its kind of hard to determine what has gone wrong?
DebugFS works with .26 OTA and you don't need an unlocked bootloader for it to work (though having root might cause problems for getting OTAs and the unlocker to work).

alienedd said:
What exactly are you doing as its kind of hard to determine what has gone wrong?
DebugFS works with .26 OTA and you don't need an unlocked bootloader for it to work (though having root might cause problems for getting OTAs and the unlocker to work).
Click to expand...
Click to collapse
just trying to run the debugFS automated tool. it runs fine, and gives all indications that it works successfully. but I still dont have root. its driving me crazy. I have run 2.0, 2.1 and 2.2 packages and all said I was rooted...but I dont think I am. I have installed and uninstalled superuser and rebooted numerous times. I went ahead and unlocked the bootloader and it still wont work. I can open a command prompt from within the package folders (2.0, 2.1 and 2.2) and run adb shell, then su and it shows #. but if I do it from terminal on the infinity it shows $ when i do su. sorry if im vague, im just brain fried at this point and dont know what else to do.

henbone11 said:
just trying to run the debugFS automated tool. it runs fine, and gives all indications that it works successfully. but I still dont have root. its driving me crazy. I have run 2.0, 2.1 and 2.2 packages and all said I was rooted...but I dont think I am. I have installed and uninstalled superuser and rebooted numerous times. I went ahead and unlocked the bootloader and it still wont work. I can open a command prompt from within the package folders (2.0, 2.1 and 2.2) and run adb shell, then su and it shows #. but if I do it from terminal on the infinity it shows $ when i do su. sorry if im vague, im just brain fried at this point and dont know what else to do.
Click to expand...
Click to collapse
Yeah, I understand. Um, I know I've repeated this several other times but I don't see it in your list of things you've done. Were you able to open up the superuser application? It seems that if it opens, you have root, and in some cases might not work until it is opened. It's both fortunate and unfortunate that I did not encounter many problems while rooting so my experience with possible errors isn't that expansive. However, you've run the package(s) completely so it's not a driver issue and you can adb and see su access. It just seems like the tablet isn't recognizing that it does have it.

yeah, I ran superuser immediately after rooting. then rebooted each time. http://forum.xda-developers.com/showpost.php?p=29951628&postcount=494
lol thats everything that I have tried. kinda sucks, but im sure someone will figure it out at some point.
weird thing is, if I run a command prompt from within the package folders I see that its rooted. if I run terminal on the device it says permission denied and prompt is still $. just odd.

I'm sure that sparky can give you help in the main thread as he has a whole lot more knowledge about the possible failings. Also, read over some of the other threads here as there seem to be quite a few people with errors that I don't even understand why they are happening. Maybe a something like simply the drivers? http://forum.xda-developers.com/showpost.php?p=29974269&postcount=9
Other then that, I'm at a loss bud. Do mention the fruits of your research though as I'm sure it would definitely be helpful to others.

alienedd said:
I'm sure that sparky can give you help in the main thread as he has a whole lot more knowledge about the possible failings. Also, read over some of the other threads here as there seem to be quite a few people with errors that I don't even understand why they are happening. Maybe a something like simply the drivers? http://forum.xda-developers.com/showpost.php?p=29974269&postcount=9
Other then that, I'm at a loss bud. Do mention the fruits of your research though as I'm sure it would definitely be helpful to others.
Click to expand...
Click to collapse
yeah, we have been trying to figure it out...no joy. I have seen quite a few people with the same issue. hopefully someone can sort out why its happening soon. even if I cant root, at least knowing why would somewhat appease me.

henbone11 said:
yeah, we have been trying to figure it out...no joy. I have seen quite a few people with the same issue. hopefully someone can sort out why its happening soon. even if I cant root, at least knowing why would somewhat appease me.
Click to expand...
Click to collapse
Perhaps this then?

d14b0ll0s said:
Perhaps this then?
Click to expand...
Click to collapse
Ok, I followed this http://forum.xda-developers.com/showpost.php?p=28519641&postcount=11 and was successful in rooting mine and my gf's infinity's.
one thing though. after manually rooting, after the final reboot, go into the Superuser app. DO NOT UPDATE IT FROM WITHIN THE APP. for some reason, updating from within Superuser borks the app. at least it did for mine and my gf's.
optional:
close Superuser. go to the play store and download busybox installer (needed to run titanium backup), root checker (there are a ton, just pick one of the top ones), adaway, ota rootkeeper and titanium backup. doesnt matter what order. I would run busybox installer first though once you have everything installed. after busybox installs, you can run root checker, adaway or titanium to check root. I say after you install busybox because some apps do require busybox to be installed before they consider you rooted. if you get the superuser prompt to allow/deny, everything is working fine. once you know that you have root and everything is working ok, run ota rootkeeper.
my only question at this point is regarding OTA updates. to my understanding, simply rooting will allow you to continue to receive OTA updates, but unlocking the bootloader will prevent you from getting OTA updates...is this correct?

New Root Method for AT&T Samsung Galaxy S 4 (OTA MF3 + Safe update to MK2)

HOWTO:
Use a card reader to format the micro SD card to exFAT (FAT32 or other formats does not work) in Windows. I haven't tried Linux or MacOS X, so they may not work.
Download the attached file (Root_for_ATTSG4_FM3.rar) and extract it into the root of your EXTERNAL microSD card using the card reader in Windows. (You can do the extraction using WinRAR or 7-zip).
Put the SD card back to the phone and download the Android Terminal Emulator app.
Open the Terminal Emulator app and run below 3 commands:
Code:
cd /mnt/extSdCard
./pwn
./script.sh
Then, open SuperSU and check everything looks good.
Then open a root app and it should be working properly.
Reboot your device once to confirm root is still working after reboot.
Come back to the post and press the THANKS button
Notes:
I uploaded a screenshot from the Terminal screen where the instructions are entered. Yours should be the same except you don't need to enter the "ls -l" command. It's just to show what files I have on the SD card. Ignore LOST.DIR directory.
Remove any SuperSU apps from your phone before following the above steps. script.sh installs it automatically.
You can use adb shell instead of a terminal app which is more convenient but requires Android SDK. Follow these steps only if you are about to use adb:
Download and install all Samsung Galaxy S 4 drivers from here.
Activate Developer options -> USB Debugging mode. To have the phone show the Developer options, go to Settings -> More -> About device. Tap on "Build number" 6 times.
You have to use an external SD card. No other alternative have been found yet. Using the device storage, i.e. /mnt/sdcard, or /data/local/tmp, DOES NOT work.
Warning (suggested by rushi.1986): "We have root for MF3 but we neither have a working recovery, nor an ODIN back to stock package. Be very careful what you do with your root. At this point, there is no way to recover even from a soft brick. (unless you know exactly what caused the soft brick and can correct it using adb)"
For those who do not know how to format an SD card on Windows (thanks to jee'sgalaxy):
Insert the micro SD into the computer (may have to use a reader or a micro SD adapter).
Go to "My Computer".
Right click on your SD card that showed up.
Click Format.
Choose exFAT as the format.
Click "OK".
Stopping AT&T Auto Software Update
Since AT&T just rolled out the new update (4.3), I add this short guide on how to stop it before it becomes late! Note that these steps require root, so you should follow the rooting steps first.
Download and install "App Quarantine ROOT/FREEZE" from Play Store.
Open the app and go to settings by tapping on the wrench icon at the top right of the screen.
Uncheck the "Hide system services" option.
Go back to the app and select "AT&T Software update".
Tap on the lock icon on the top right of the screen.
It may ask you to enable the USB debugging.
Feel safe from AT&T's new attack
How to get MK2 without losing root
I have tested this approach and it worked for myself. You should consider the risk of losing the root access and follow these steps on your on risk:
Root your MF3 phone using the approach described earlier in this post.
Stop AT&T from pushing the update as described above.
Install Super SU Pro. Note that this is not a free app and it is an add-on for Super SU.
Run Super SU. Go to Settings and check the "Survival Mode". If you don't have this option, probably you don't have the Pro version.
Disable your guard against the AT&T update by enabling "AT&T Software update".
Let the device update itself and hope for the best.
Don't forget to press the THANKS button.
Credits:
***Exploit adapted for AT&T by Jortex***
***Original Guide by Open1Your1Eyes0 for Verizon Galaxy S 4***
***Original Exploit by DooMLoRD***

MF3

Can't wait to try it...
Sent from my SAMSUNG-SGH-I337 using xda premium

I get permission denied. In terminal emulator I type
CD /mnt/extSdCard
./pwn
Then it says permission denied
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

Billsfan99 said:
I get permission denied. In terminal emulator I type
CD /mnt/extSdCard
./pwn
Then it says permission denied
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Same here

Nick James said:
Same here
Click to expand...
Click to collapse
Sorry guys. I missed one step. You should format the external SD card to exFAT. Windows supports it.

Question
Does this mean that we can flash Google Edition rom on the MF3 AT&T S4?
Or do we have to wait until more exploits are discovered?
I was rocking GE rom until I went back to the stock Samsung ROM to SIM unlock my phone.
I got screwed by the OTA MF3 and have been following this forum everyday for a new root method.

ddslee said:
Does this mean that we can flash Google Edition rom on the MF3 AT&T S4?
Or do we have to wait until more exploits are discovered?
I was rocking GE rom until I went back to the stock Samsung ROM to SIM unlock my phone.
I got screwed by the OTA MF3 and have been following this forum everyday for a new root method.
Click to expand...
Click to collapse
This only allows you to root your device. No method to use custom ROM has been found yet.

So my phone WAS rooted, stock ROM.
I installed the OTA update on accident.
Ran the new exploit
Installed SuperSU
It asked me if I wanted to update the binary, I told it "Continue" and it comes back with "failed"
I suspect this is because of my previous root?

Nick James said:
So my phone WAS rooted, stock ROM.
I installed the OTA update on accident.
Ran the new exploit
Installed SuperSU
It asked me if I wanted to update the binary, I told it "Continue" and it comes back with "failed"
I suspect this is because of my previous root?
Click to expand...
Click to collapse
No need to install anything yourself. Uninstall everything and run SuperSU. Let it update itself. If that doesn't work, a reboot may help.
Also try to make sure that you have root.

jortex said:
No need to install anything yourself. Uninstall everything and run SuperSU. Let it update itself. If that doesn't work, a reboot may help.
Also try to make sure that you have root.
Click to expand...
Click to collapse
I never had SuperSU installed though.
You're talking about this, https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
Right?

Nick James said:
I never had SuperSU installed though.
You're talking about this, https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
Right?
Click to expand...
Click to collapse
Yes. It is being installed by the script.sh. You just need to update it. That's it.

jortex said:
Yes. It is being installed by the script.sh. You just need to update it. That's it.
Click to expand...
Click to collapse
I'm not following you. What do you mean I just need to update it? The script never installed it. I had t download it from the market and once I did that it asked me, upon opening it for the first time, "The SU binary needs to be updated. Continue?" and when I hit Continue it then says "If you have a custome recovery like TWRP or CWM, that can be used to (try to) install the SU binary. this is recommended for HTC devices. How would you like to install the SU binary? Normal or TWRP/CWM
I've tried both options with no luck.

When I run the exploit, it also says my device isnt supported but stays it obtained root?

Nick James said:
When I run the exploit, it also says my device isnt supported but stays it obtained root?
Click to expand...
Click to collapse
Mine said the same thing. I just kept going and typed the ./script.sh and thats it.

Nick James said:
When I run the exploit, it also says my device isnt supported but stays it obtained root?
Click to expand...
Click to collapse
That's fine. It tries several exploits. The first one does not apply to your device (SG4), but the last one does.
UPDATE: You already "obtained root". Look at the prompt which is changed from $ to #. As wahbob suggested, continue running script.sh. This file installs SuperSU for you. Then you can run it without explicitly getting it from Play Store.

jortex said:
This only allows you to root your device. No method to use custom ROM have been found yet.
Click to expand...
Click to collapse
Ahhh Thanks for the root though!

Thanks! Just tried it and I have Root again

thanks for this

Sorry for the noob question but when I run the cd/mnt/extsdcard command I get a "not found". Does anybody know what I'm doing wrong?

[Q] Softwinerevb -0.0mb stucked after updating the Busybox

Helo,im new here.. iam exploring the whole day exploring the web in getting root my device, but then after i succesfully rooted my device. i got a lot of errors like "unfortunately , the 'certain app' stop working". And when everytime i install the ROM manager, my device suddenly reboot on it self. I decided to have a factory reset on my device to check if the error will fix. And the error was actually fixed. I installed busybox pro, on the device and tried to update the busybox, and now my device has a 0.00b internal storage. I cant install any applications anymore. While doing self investigation, i removed also my Superuser privileges, thinking it would fix the issue. I also unrooted my device again. now im stucked -.- since i read about some forums that i just need to restore the busybox to the right directory. Anyone can help me? Iam running a tablet with Softwinerevb device name- i know there is a less support about this device. Running on a stock ROM JB 4.1.1. Well cross-fingers if someone could help me here.

crigz said:
Helo,im new here.. iam exploring the whole day exploring the web in getting root my device, but then after i succesfully rooted my device. i got a lot of errors like "unfortunately , the 'certain app' stop working". And when everytime i install the ROM manager, my device suddenly reboot on it self. I decided to have a factory reset on my device to check if the error will fix. And the error was actually fixed. I installed busybox pro, on the device and tried to update the busybox, and now my device has a 0.00b internal storage. I cant install any applications anymore. While doing self investigation, i removed also my Superuser privileges, thinking it would fix the issue. I also unrooted my device again. now im stucked -.- since i read about some forums that i just need to restore the busybox to the right directory. Anyone can help me? Iam running a tablet with Softwinerevb device name- i know there is a less support about this device. Running on a stock ROM JB 4.1.1. Well cross-fingers if someone could help me here.
Click to expand...
Click to collapse
I can install an emulator on it, and a root explorer. Is there anyway that you can provide some commands so i can gain root access using root commands and transfer the busybox from system\xbin to system\bin??

any solution
did you find a solution to this? I have a similar problem, but on a generic tv box. I have tried flashing a multitude of roms, but have only got 1 to slightly work

Try to change default install location to SD
Use ADB and try to change default install location to SD card. By this u can install some apps. Hope this will work for you.:highfive:

Late response, but I thought I'd put the answer here since I encountered it myself on a generic AllWinder/Softwiner tablet and found the answer on TabletRepublic. (Sorry, I'm not allowed to post links yet.)
There's something about busybox that prevents it from mounting the /data partition, so you don't have any storage available and all your personal settings vanish.
The solution is to copy busybox from /system/xbin to /system/bin. If you have ADB access (I did it from Linux) or can copy a terminal emulator to the SD card and install it do this:
Code:
mount -o rw,remount /system
cp /system/xbin/busybox /system/bin
reboot
Or if you can download RootExplorer.apk to the SD card, you can install that and copy the file with it.