Hi
Here is the ota update i have just received on my azerty ChaCha :
http://www.megaupload.com/?d=JK8WZOY3
Maybe you can use it by copying it at the root of your sdcard, renaming it as update.zip and rebooting the ChaCha in recovery mode throw adb
geek78 said:
Maybe you can use it by copying it at the root of your sdcard, renaming it as update.zip and rebooting the ChaCha in recovery mode throw adb
Click to expand...
Click to collapse
I tried to update from Europe_1.13.401.1. Get error status7 and can't update.
This update is only for devices under 1.15 this is a diff patcher from 1.15 to 1.18.
Have you been able to get root access with this. This came on the device I won from htc at work and superuser keeps crashing. Im considering attempting a downgrade as I got the recovery menu installed as it came s-off
Just follow this guide :
http://forum.xda-developers.com/showthread.php?t=1184118
geek78 said:
Just follow this guide :
http://forum.xda-developers.com/showthread.php?t=1184118
Click to expand...
Click to collapse
thats the one that doesnt work. It force closes everytime an app requests access.
have you tried to update superuser (on the market) ?
geek78 said:
have you tried to update superuser (on the market) ?
Click to expand...
Click to collapse
yeah it doesn't work. im wondering if its a problem with the app
Please try the following procedures.
(1) Delete Superuser's update and clear data.
(2) Reinstall update.
(3) Enable 'Auto-rotate screen' on the Display settings.
(4) Change the screen to the portrait mode.
(5) Run Superuser and allow permission to update its own.
I solved a same problem in this procedure.
osahiro said:
Please try the following procedures.
(1) Delete Superuser's update and clear data.
(2) Reinstall update.
(3) Enable 'Auto-rotate screen' on the Display settings.
(4) Change the screen to the portrait mode.
(5) Run Superuser and allow permission to update its own.
I solved a same problem in this procedure.
Click to expand...
Click to collapse
Yeah this is what worked for me in the end. its a bit fiddley though isnt it. Oh well sorted now at least. Maybe this should be added to the rooting thread.
Have you noticed that you can move apps to the sd in manage applications. It seems that some people have been supprised that it does it.
FCW said:
Yeah this is what worked for me in the end. its a bit fiddley though isnt it. Oh well sorted now at least. Maybe this should be added to the rooting thread.
Have you noticed that you can move apps to the sd in manage applications. It seems that some people have been supprised that it does it.
Click to expand...
Click to collapse
isn't the option to move apps to sd in manage applications a feature way back in froyo?
Superuser crashed on me first time with every app that asked, either the button was cropped so rotating shows true button, or it worked fine after a reboot.
Sent from my HTC ChaCha A810e using Tapatalk
Related
Once you have achieved root (see other thread), to update the Superuser.apk to the latest version, run these commands:
Code:
adb shell
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
rm /system/app/Superuser.apk
pm uninstall com.noshufou.android.su
Then search on the market for Superuser and download the one by ChainsDD. Confirmed working on latest Droid2 2.2 ota.
EDIT: To be safe, go to Settings>Applications>Manage Applications and find Superuser. Then clear the data. This should prevent any of the Superuser issues discussed.
sorry..new to the whole android scene. are there any advantages to updating the superuser app the the latest version and can this command be input on the droid itself through the terminal app?
metman87 said:
sorry..new to the whole android scene. are there any advantages to updating the superuser app the the latest version and can this command be input on the droid itself through the terminal app?
Click to expand...
Click to collapse
i like the interface much more and its got a new autoaccept after 10 seconds if you arent paying attention when the popup shows. it's up to you. i'm sure future root tools will just include it.
alright thanks. is it as simple as installing the new version and uninstalling the old? or does one need to enter the command prompts listed above?
metman87 said:
alright thanks. is it as simple as installing the new version and uninstalling the old? or does one need to enter the command prompts listed above?
Click to expand...
Click to collapse
that is what the commands do. unfortuantely, the old version is on the system partiton. this means that we must first mount the system and read/write and then manually delete the old version ourself. then the new version can be easily downloaded through the market. anyways, adb shell means it's done via your computer so its very easy to copy and paste like 3 commands.
Instructions work perfectly... thanks!
I need Mac instructions
Sent from my DROID2 using XDA App
greg25 said:
I need Mac instructions
Click to expand...
Click to collapse
These instructions are not specific to the OS on your computer, they work with anything.
Perfect!
Worked great! Thank you!
Instructions worked fine (I just made them up for Linux), but the newest SuperUser is giving me weird results. Every program that requests root access will ask me numerous times, like it never remembers that I gave the app access. Like removing one app with titanium will it will ask me 4 seperate times to accept or deny permission. Other apps do this also. Anyone have a copy of the old apk I could reinstall? Anyone have any ideas or suggestions?
Thanks
n0yd said:
Instructions worked fine (I just made them up for Linux), but the newest SuperUser is giving me weird results. Every program that requests root access will ask me numerous times, like it never remembers that I gave the app access. Like removing one app with titanium will it will ask me 4 seperate times to accept or deny permission. Other apps do this also. Anyone have a copy of the old apk I could reinstall? Anyone have any ideas or suggestions?
Thanks
Click to expand...
Click to collapse
I had the same thing happen to me. Launch the new superuser app and go to settings. Unselect and reselect Notifications. Apparently it shows it being checked, but you have to recheck it for the actual setting to get saved.
After I did this, it only asks once for a program, and then I never see it again.
facelessuser said:
I had the same thing happen to me. Launch the new superuser app and go to settings. Unselect and reselect Notifications. Apparently it shows it being checked, but you have to recheck it for the actual setting to get saved.
After I did this, it only asks once for a program, and then I never see it again.
Click to expand...
Click to collapse
Nice, thanks!
I had that issue too. I ironically un-installed superuser and re-installed it and it worked fine too
I used Root Explorer to delete the old Superuser.apk from /system/app. Then I rebooted and installed the new version from the market. Worked great.
jmonte345 said:
I used Root Explorer to delete the old Superuser.apk from /system/app. Then I rebooted and installed the new version from the market. Worked great.
Click to expand...
Click to collapse
that works too though without having the superuser apk and rebooting, that could be a little dangerous for others hence my adb tutorial. no need for a restart either. could easily just use root explorer, delete the old, download new from market.
Worked great
I just renamed Superuser.apk to .bak then tried to install. Don't forget the last step. I had to adb (I was using terminal emulator) to do the last step then installed fine and removed Superuser.bak.
Thanks I like the New look.
yeah i can't get superuser from the market to install, keeps telling me unsuccessful
jerseyh22accord said:
yeah i can't get superuser from the market to install, keeps telling me unsuccessful
Click to expand...
Click to collapse
I had the same problem. I rebooted my phone and then it installed fine. Not sure if it's risky to reboot once you remove the apk or not. However, it didn't cause any problems for me.
jmonte345 said:
I used Root Explorer to delete the old Superuser.apk from /system/app. Then I rebooted and installed the new version from the market. Worked great.
Click to expand...
Click to collapse
I basically did the same thing except I renamed instead of deleting it. Well, once I installed SU from the market, I can't find the .apk file even though it's running and launching correctly. I assumed it would be called superuser.apk in the system/app folder but only my old renamed superuser.bak is there. I'm just worried if there is an update in the future, I won't be able to rename since I can't find the .apk file. Anyone know where the .apk file is for this new version of superuser?
facelessuser said:
I had the same thing happen to me. Launch the new superuser app and go to settings. Unselect and reselect Notifications. Apparently it shows it being checked, but you have to recheck it for the actual setting to get saved.
After I did this, it only asks once for a program, and then I never see it again.
Click to expand...
Click to collapse
Tried this, and it didn't work for me. With Titanium Backup in particular, it will literally ask upwards of twenty times for permission. It's insanely annoying. Any other tips?
Sent from my DROID2 using XDA App
I have installed today new custom rom with sense 3.5
Superuser worked fine and also daemon controller.
Market auto updated superuser and then I got always error when I try to open daemon controller this error :
The application superuser (proces com.noshufou.android.su
I also uninstalled the update but still same error..
Yeah the new superuser have that problem, with FC. Try the version 3 or the version 3.0.2
1. Go to settings==>applications
2. Find superuser and tap "uninstall updates". You should be back on 3.0.2
3. Go into your market app and search for superuser. Open the app listing and uncheck "allow automatic updates".
Sent from my HTC Sensation Z710e using xda premium
moviewatch said:
I also uninstalled the update but still same error..
Click to expand...
Click to collapse
moto211 said:
1. Go to settings==>applications
2. Find superuser and tap "uninstall updates". You should be back on 3.0.2
3. Go into your market app and search for superuser. Open the app listing and uncheck "allow automatic updates".
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
Did you read it and just was not paying attention or did you just not read it? The OP said they had already don what you suggested.
Right now I am on the latest superuser..
When I open daemon controller works fine also overclocking working.
But when I want to give Es file explorer root acces..
I get again that error.. driving me crazy right now
looks like my phone is not rooted or what
Have you thought about seeing if you can update your Busy Box too? It is a shot in the dark but I know Superuser and Busy Box are closely tied together. Also have you tried to uninstall and then re install the app in question?
moviewatch said:
I have installed today new custom rom with sense 3.5
Superuser worked fine and also daemon controller.
Market auto updated superuser and then I got always error when I try to open daemon controller this error :
The application superuser (proces com.noshufou.android.su
I also uninstalled the update but still same error..
Click to expand...
Click to collapse
Hi,
May I suggest you try to restore to SU 3.0.2
Make a nandroid backup,and flash in recovery.
I installed busybox.. but when it ask for root acces
I click on Allow then the error from superuser comes again...
Do you have apk file for superuser 3.0.2 ??
malybru said:
Hi,
May I suggest you try to restore to SU 3.0.2
Make a nandroid backup,and flash in recovery.
Click to expand...
Click to collapse
In recovery get this error :
E: error /sdcard/su-3.0.2.zip
(status 0)
installation aborted
I had to go into the su app and delete app data, then totally uninstall it completely. Then install an earlier version. That is the only way it stopped force closing for me, uninstalling updates did not work. After you install earlier version go in and update binary, even if it's already up to date. If it updates it and you can press the back button and it does not Fc, then you should be fine .
Sent from my HTC Sensation 4G using XDA App
Download Root Checker from the Android Market. Install it and open it then click on the check for root button. This will tell you if you are rooted.
moviewatch said:
In recovery get this error :
E: error /sdcard/su-3.0.2.zip
(status 0)
installation aborted
Click to expand...
Click to collapse
Hi,
Someone had the same problem and tried again a few times until it worked.
masondoctorjt said:
I had to go into the su app and delete app data, then totally uninstall it completely. Then install an earlier version. That is the only way it stopped force closing for me, uninstalling updates did not work. After you install earlier version go in and update binary, even if it's already up to date. If it updates it and you can press the back button and it does not Fc, then you should be fine .
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse
How did you completely uninstall it..
and then how did you install an earlier version..
I have adb shell on my pc..
malybru said:
Hi,
Someone had the same problem and tried again a few times until it worked.
Click to expand...
Click to collapse
after 3 times.. installation succesfull, hehe
But not helped my problem with the error
also for root checker you need root acces.. I click allow.
and then boom error
moviewatch said:
after 3 times.. installation succesfull, hehe
But not helped my problem with the error
also for root checker you need root acces.. I click allow.
and then boom error
Click to expand...
Click to collapse
Hi,
Worth a try.
Go to all apps>super user>preferences>automatic response>click allow and see if that helps.
T-Macgnolia said:
Did you read it and just was not paying attention or did you just not read it? The OP said they had already don what you suggested.
Click to expand...
Click to collapse
Wow dude, calm down. Yes, I did read the op's post. I'm sorry if my missing that part has offended you.
To the OP, try manually deleting superuser and all related files through adb, the flash 3.0.2 from recovery.
Sent from my HTC Sensation Z710e using xda premium
malybru said:
Hi,
Worth a try.
Go to all apps>super user>preferences>automatic response>click allow and see if that helps.
Click to expand...
Click to collapse
I re-installed my custom rom..
and then did what you told above..
Right now es file explorer working..
and daemon controller had just 1 time that error of superuser.
I will let it so.. will check it out tomorrow
Maybe the phone has now enough of all we did
Thanks !
malybru said:
Hi,
Worth a try.
Go to all apps>super user>preferences>automatic response>click allow and see if that helps.
Click to expand...
Click to collapse
People need to STOP suggesting this. This is way unsafe and defeats the purpose of the app even having an asking prompt in the first place. It might be a "temp" fix, but it shouldn't even be used!
Sent from my HTC Sensation 4G using XDA App
This solution worked for me, no more FCs
h/t theraver and homersp
to solve the SU problems try this su binary
binary: http://dl.dropbox.com/u/11494687/superuser/su
to install do this:
Update to superuser 3.0.5 in the market (if you didn't do this)
adb remount
adb push su /system/bin/
adb shell chmod 06755 /system/bin/su
adb shell rm /data/data/com.noshufou.android.su/databases/permissions.*
This sollution comes from the home site of superuser by ChainsDD, and was posted by HomerSp. credits to HomerSp!
Rom Manager, fix permission, problem sorted for me.
Cheers Hammyinc
Hello,
I need to root a CAT b10 telephone. I tried using superuser program but it didn't work. I can't find any documentation for this phone in Internet.
Do you know a method to root this phone?
Thanks.
cabrerachaparro said:
Hello,
I need to root a CAT b10 telephone. I tried using superuser program but it didn't work. I can't find any documentation for this phone in Internet.
Do you know a method to root this phone?
Thanks.
Click to expand...
Click to collapse
You have to root this phone via RECOVERY. Use attached file and UPDATE FROM SDCARD.
Also you must not update (after recovery root) SUPERUSER app via android-market to newer version!!! If you'll do it, then it all comes broken. And you have to do it once again.
ninr said:
You have to root this phone via RECOVERY. Use attached file and UPDATE FROM SDCARD.
Also you must not update (after recovery root) SUPERUSER app via android-market to newer version!!! If you'll do it, then it all comes broken. And you have to do it once again.
Click to expand...
Click to collapse
Hi,
I followed the instructions but I'm getting Force Close message for superuser app. Even applying factory reset.
cabrerachaparro said:
Hi,
I followed the instructions but I'm getting Force Close message for superuser app. Even applying factory reset.
Click to expand...
Click to collapse
OK, that's no problem.
Attached package contains few another packages....(update.zip is the same like I uploaded here before)
1. Try to use "Superuser-3.1.3-arm-signed.zip" (this should be enough but I don't know why it isn't)
2. Reboot
3. Look at Superuser app
4. If Superuser app doesn't work then use "update.zip" once again
5. Reboot
6. Look at Superuser app
7. Now it should be working if not you can update Superuser app from market and try above procedure once again
Root this phone is really long term job. But never give up!! This phone is useless without root. I have been rooting this phone more then week.
Good luck and post if will you be successful.
just wondering since you have some experience with the phone.is there a custom rom for this phone or just the original one?
All of a sudden the superuser on my TF700 stopped working; all rooted apps are now being denied superuser status. Worse, Superuser won't reinstall, and Rootchecker.apk tells me the tablet isn't rooted anymore. Voodoo OTA rootkeeper still has the saved root files, but won't reinstall them on account of the borked superuser, I'm assuming.
I should add that NONE of the available Superuser apps will install; not the original Superuser, Koush's Superuser, or SuperSU.
So I tried the whole rooting procedure by trying to downgrade to ICS. But although the tablet sees the file it won't install it; on reboot all I get is the dead Android with a big red X. When I tried it a second time, the tablet now doesn't even acknowledge the presence of the downgrade file.
I need help here. I just rooted this tablet but never installed recovery (wasn't interested in unlocking it at the time). How do I proceed from here?
mudge
iCurmudgeon said:
All of a sudden the superuser on my TF700 stopped working; all rooted apps are now being denied superuser status. Worse, Superuser won't reinstall, and Rootchecker.apk tells me the tablet isn't rooted anymore. Voodoo OTA rootkeeper still has the saved root files, but won't reinstall them on account of the borked superuser, I'm assuming.
I should add that NONE of the available Superuser apps will install; not the original Superuser, Koush's Superuser, or SuperSU.
So I tried the whole rooting procedure by trying to downgrade to ICS. But although the tablet sees the file it won't install it; on reboot all I get is the dead Android with a big red X. When I tried it a second time, the tablet now doesn't even acknowledge the presence of the downgrade file.
I need help here. I just rooted this tablet but never installed recovery (wasn't interested in unlocking it at the time). How do I proceed from here?
mudge
Click to expand...
Click to collapse
Hard for me to understand where you're at exactly.
Did you actually boot into ICS before trying to re-root?
Sometimes when SuperSU updates you will have to go back into the application and reset permissions for all rooted applications.
If you can boot and if the previous SU is still there go into settings for the tablet and uninstall any updates for SuperSU then try to reset permissions in the app.
iCurmudgeon said:
All of a sudden the superuser on my TF700 stopped working; all rooted apps are now being denied superuser status. Worse, Superuser won't reinstall, and Rootchecker.apk tells me the tablet isn't rooted anymore. Voodoo OTA rootkeeper still has the saved root files, but won't reinstall them on account of the borked superuser, I'm assuming.
I should add that NONE of the available Superuser apps will install; not the original Superuser, Koush's Superuser, or SuperSU.
So I tried the whole rooting procedure by trying to downgrade to ICS. But although the tablet sees the file it won't install it; on reboot all I get is the dead Android with a big red X. When I tried it a second time, the tablet now doesn't even acknowledge the presence of the downgrade file.
I need help here. I just rooted this tablet but never installed recovery (wasn't interested in unlocking it at the time). How do I proceed from here?
mudge
Click to expand...
Click to collapse
Go into settings -> recovery- factory reset. Try one or both if needed:
1. Download the full Asus ICS .30 zip, verify MD5 (ensure file is not corrupted), unzip the file then copy the unzipped file called US_epad-user-9.4.5.30.zip to the root of your internal, boot into stock recovery and let it flash.
or
2. Reformat your micro sdcard.
1) Download and unzip US_epad_user_9_4_5_30_20120907_UpdateLauncher.zip and got US_epad-user-9.4.5.30.zip. Copied it to root of microsdcard, reboot your tablet and check your notification for software update.
or
3) unzip US_epad_user_9_4_5_30_20120907_UpdateLauncher.zip and got US_epad-user-9.4.5.30.zip. Rename this file to EP201_768_SDUPDATE.zip then copy this to root of microsdcard. Power off your device, boot into recovery by hold power + vol down buttons, when you see white text release both buttons, you should see 4 icons. The icon "RCK" should be highlighted by default, just wait a few seconds and it should start flashing.
then renamed US_epad-user-9.4.5.30.zip to EP201_768_SDUPDATE.zip and
Thats OK said:
Hard for me to understand where you're at exactly.
Did you actually boot into ICS before trying to re-root?
Sometimes when SuperSU updates you will have to go back into the application and reset permissions for all rooted applications.
If you can boot and if the previous SU is still there go into settings for the tablet and uninstall any updates for SuperSU then try to reset permissions in the app.
Click to expand...
Click to collapse
I finally managed to get back to ICS, then ran the rooting procedure. However, it always failed when it came to testing Superuser. Tried it four or five times. Then I tried installing the other Superuser apks. Every last one of them said the su binary needed to be updated, but every one of them failed to do so.
That's where I am right now. Unrooted ICS.
buhohitr said:
Go into settings -> recovery- factory reset. Try one or both if needed:
1. Download the full Asus ICS .30 zip, verify MD5 (ensure file is not corrupted), unzip the file then copy the unzipped file called US_epad-user-9.4.5.30.zip to the root of your internal, boot into stock recovery and let it flash.
or
2. Reformat your micro sdcard.
1) Download and unzip US_epad_user_9_4_5_30_20120907_UpdateLauncher.zip and got US_epad-user-9.4.5.30.zip. Copied it to root of microsdcard, reboot your tablet and check your notification for software update.
or
3) unzip US_epad_user_9_4_5_30_20120907_UpdateLauncher.zip and got US_epad-user-9.4.5.30.zip. Rename this file to EP201_768_SDUPDATE.zip then copy this to root of microsdcard. Power off your device, boot into recovery by hold power + vol down buttons, when you see white text release both buttons, you should see 4 icons. The icon "RCK" should be highlighted by default, just wait a few seconds and it should start flashing.
then renamed US_epad-user-9.4.5.30.zip to EP201_768_SDUPDATE.zip and
Click to expand...
Click to collapse
Thanks for the info. I managed to get back into ICS (see previous msg) using your number 1 (took three tries) but I can't complete the root procedure because for some unknown reason superuser won't install correctly.
iCurmudgeon said:
Thanks for the info. I managed to get back into ICS (see previous msg) using your number 1 (took three tries) but I can't complete the root procedure because for some unknown reason superuser won't install correctly.
Click to expand...
Click to collapse
Is there a previous version of SU installed or leftover?
See if it's still in running apps under settings.
If you're on ICS I'd try a factory reset and go from there.
iCurmudgeon said:
Thanks for the info. I managed to get back into ICS (see previous msg) using your number 1 (took three tries) but I can't complete the root procedure because for some unknown reason superuser won't install correctly.
Click to expand...
Click to collapse
After you flashed superuser, did you launch the app?? you need to launch the app and it should prompt to update, do the update. Once done now you can test for root.
buhohitr said:
After you flashed superuser, did you launch the app?? you need to launch the app and it should prompt to update, do the update. Once done now you can test for root.
Click to expand...
Click to collapse
I did launch the app and it did tell me the su binary needed to be updated. So I told it to go ahead with a normal install. Installation failed. Also tried the SU update fixer from the play store, and that failed as well.
You need to reflash your ROM... I get this often. I'm maintaining 6 devices for my family.
Lim Wee Huat said:
You need to reflash your ROM... I get this often. I'm maintaining 6 devices for my family.
Click to expand...
Click to collapse
Yes, I would agree, this is the only way left for what to do next!
buhohitr said:
Yes, I would agree, this is the only way left for what to do next!
Click to expand...
Click to collapse
Ouch. But didn't I do this when I downgraded from Jellybean back to ICS?
Can someone point me to a post how to do this?
iCurmudgeon said:
Ouch. But didn't I do this when I downgraded from Jellybean back to ICS?
Can someone point me to a post how to do this?
Click to expand...
Click to collapse
Just do a factory reset, then follow my number 3 post. Also make sure you verify MD5 on the ICS .30 rom before flashing.
buhohitr said:
Just do a factory reset, then follow my number 3 post. Also make sure you verify MD5 on the ICS .30 rom before flashing.
Click to expand...
Click to collapse
Well, I tried, but when I rebooted with the power and vol-down buttons, I only got an "Android" icon and something else to its left, no RCK at all. The pad rebooted eventually and I was stunned when Superuser started working! I immediately ran Voodoo OTA Rootkeeper, then let the tablet update to 4.1.1. I then ran SuperSU and it said the su binary needed to be updated. I told it to do a normal install. "Installation failed." Said bad words in several languages and tried again. Update of SU binary succeeded.
Restored root. Success. Now restoring last Titanium backup backup.
I'm still worried, though. The symptoms would seem to point to flaky or at least unstable flash memory. What do you think?
I gotta decide whether to get a Samsung Galaxy Note tablet (7-inch) or the updated Nexus 7 tablet when they come out. I don't trust this TF700 anymore..
mudge
I have the same problem, but didn't downgrade!
I have the same problem, except I have not tried to downgrade.
The first problem I noticed after the OTA update was that Bluetooth simply would not turn on. Going through the steps to fix this problem I noticed that OTA Rootkeeper "kept root", but any time I try to use su, it fails to work.
I managed to fix bluetooth using ADB, but I am still left with su and superuser that do not work. Is there a way to fix this from ADB by twiddling with permissions somehow?
IT Wannabe said:
I have the same problem, except I have not tried to downgrade.
The first problem I noticed after the OTA update was that Bluetooth simply would not turn on. Going through the steps to fix this problem I noticed that OTA Rootkeeper "kept root", but any time I try to use su, it fails to work.
I managed to fix bluetooth using ADB, but I am still left with su and superuser that do not work. Is there a way to fix this from ADB by twiddling with permissions somehow?
Click to expand...
Click to collapse
Seems like now there is a way to root if you already on JB, no need to downgrade to root.http://forum.xda-developers.com/showthread.php?t=2228613 .
buhohitr said:
Seems like now there is a way to root if you already on JB, no need to downgrade to root.http://forum.xda-developers.com/showthread.php?t=2228613 .
Click to expand...
Click to collapse
The su and busybox binares and SuperSU.apk get installed, but any time I try to use root permissions I get an Access/Permission Denied error. I used the root method you gave me and everything seemed to work properly... The only thing I see that may be wrong is that the su binary is owned by "root root" rather than "root shell" like everything else is. If I try to chmod it using ADB I get permission denied errors.
Now I'm just frustrated and don't know what to do. Nothing seems to work with the 4.2.1 stock ROM. I don't want to have to unlock the bootloader because I chose not to void the warranty (didn't enable nvflash) when I first got my tablet.
I think I'm just screwed at this point. Does anyone have any ideas? I did manage to get bluetooth working, but I still can't seem to get my TF700 rooted. Without root, Titanium Backup can't restore my apps...
IT Wannabe said:
The su and busybox binares and SuperSU.apk get installed, but any time I try to use root permissions I get an Access/Permission Denied error. I used the root method you gave me and everything seemed to work properly... The only thing I see that may be wrong is that the su binary is owned by "root root" rather than "root shell" like everything else is. If I try to chmod it using ADB I get permission denied errors.
Now I'm just frustrated and don't know what to do. Nothing seems to work with the 4.2.1 stock ROM. I don't want to have to unlock the bootloader because I chose not to void the warranty (didn't enable nvflash) when I first got my tablet.
I think I'm just screwed at this point. Does anyone have any ideas? I did manage to get bluetooth working, but I still can't seem to get my TF700 rooted. Without root, Titanium Backup can't restore my apps...
Click to expand...
Click to collapse
Since motochopper has the ablility to root JB, you should remove superuser root (open supersuser and select remove root then reboot), then re root using motochopper if needed.
I finally managed to fix the problem, though I did it the long way...
I downloaded the stock 9.4.5.30 US ROM zip file, extracted it, renamed the extracted zip file to EP201_768_SDUPDATE.zip, and copied it to a microSD card. I booted to recovery and installed the zip file. Once it was installed, I went to Settings --> About Tablet --> System Update --> Check Update. I had to update this way twice to get to a clean, stock JellyBean 4.2.1 (US_epad-10.6.1.14.4-20130329).
Once I was up to date, I ran the Motochopper root tool and it worked! I have no idea what it was about my tablet that prevented su from working after the update to 4.2, but thanks to everyone for your suggestions.
IT Wannabe said:
I finally managed to fix the problem, though I did it the long way...
I downloaded the stock 9.4.5.30 US ROM zip file, extracted it, renamed the extracted zip file to EP201_768_SDUPDATE.zip, and copied it to a microSD card. I booted to recovery and installed the zip file. Once it was installed, I went to Settings --> About Tablet --> System Update --> Check Update. I had to update this way twice to get to a clean, stock JellyBean 4.2.1 (US_epad-10.6.1.14.4-20130329).
Once I was up to date, I ran the Motochopper root tool and it worked! I have no idea what it was about my tablet that prevented su from working after the update to 4.2, but thanks to everyone for your suggestions.
Click to expand...
Click to collapse
Can you tell us what the owner,group and permissions of the /system/bin/su binary are now ?
sgtrwe said:
Can you tell us what the owner,group and permissions of the /system/bin/su binary are now ?
Click to expand...
Click to collapse
Oh, sure!
After a search through my PATH, I've found that 'su' no longer lives in /system/bin, but in /system/xbin, with busybox and dexdump and every POSIX command you can think of symlinked to busybox. It is owned by root:root.
I guess that's just the way the JB root method does it...
Hi, i have a oneplus 6 rooted with magisk running twrp recovery and last night i was messing around with a mock location spoofer and everything was going okay but after a reboot my phone started only going into safe mode and i couldnt access anything basically my phone screen would flash on then off then on and off again constantly.
i Followed this tutorial https://www.reddit.com/r/PokemonGoSpoofing/comments/8ytjz5/expert_mode_for_fake_gps_and_routes/
then after that i had trouble using systemizer to make the app a system app so i used lucky patcher instead.
after all this my phone was working fine
the final thing i done what wasnt on the tutorial was used a package manager app to disable all location services from a very low software level. after that the safe mode thing started happening.
what i have tried so far -
i have tried going into the root and deleteing the app folder for the APK MANAGER app hoping that this would remove any changes it caused.
i have also tried using the magisk uninstaller to try and remove root.
now my phone wont even boot. i get a screen on start up saying my phone is corrupt and it just loops on this screen.
Before i do a full reflash and loose everything i thought id put my last hope on here and see if anyone can help me resolve this without a reflash.
Thanks for any help i'm stupid and didn't back up before hand
https://forum.xda-developers.com/oneplus-6t/how-to/guide-how-to-fix-red-boot-screen-device-t3891479
mauronofrio said:
https://forum.xda-developers.com/oneplus-6t/how-to/guide-how-to-fix-red-boot-screen-device-t3891479
Click to expand...
Click to collapse
thanks when i follow instructions it says too many symbolic links. can you help?
Shaun98 said:
thanks when i follow instructions it says too many symbolic links. can you help?
Click to expand...
Click to collapse
If you are root, install terminal app from playstore
open terminal, type : su, hit enter > grant root permission
then type : reboot "dm-verity enforcing", hit enter