The night In 2012/07/23.One Notice is OTA updata in 9.20.1.22.
I forget the need to first install the root "Voodoo OTA RootKeeper", and therefore can no longer root.
Please...help
Have you tried the below rooting method?
http://forum.xda-developers.com/showthread.php?t=1706588
kokopuphz said:
Have you tried the below rooting method?
http://forum.xda-developers.com/showthread.php?t=1706588
Click to expand...
Click to collapse
That is my first.Is Failure........
Can you post the output from the debugfs script? Is your ADB working properly?
kokopuphz said:
Can you post the output from the debugfs script? Is your ADB working properly?
Click to expand...
Click to collapse
show time!
the command show
Waiting for device to be detected...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Step 1 - Pushing files...
failed to copy 'debugfs' to '/data/local//debugfs': Permission denied
failed to copy 'su' to '/data/local//su': Permission denied
failed to copy 'debugfsinput' to '/data/local//debugfsinput': Permission denied
failed on '/data/local/tmp' - Permission denied
link failed File exists
Rebooting...
Step 2 - Rooting...
Unable to chmod /data/local/debugfs: No such file or directory
/system/bin/sh: cannot open /data/local/debugfsinput: No such file or directory
rm failed for /data/local/tmp, Permission denied
failed on '/data/local/tmp.bak' - No such file or directory
rm failed for /data/local/su, No such file or directory
rm failed for /data/local/debugfs, No such file or directory
rm failed for /data/local/debugfsinput, No such file or directory
Rebooting...
Testing superuser...
/system/bin/sh: /system/xbin/su: not found
Do not update
I had the CHT 9.18 too, I had Rootkeeper backup but cannot restore root after updated.
DO NOT update to 9.20 if you want too stay rooted!
I have to flash back old firmware and factory reset to start from scrach again but I had Titanium backup on MicroSD.
Don't try it till there is root method for CHT 9.20
Thanks for the log.
From your log, it appears the /data/local permissions have been changed in the latest update, thus the Debugfs method as it is currently will no longer work.
Your only possible options would be to downgrade the firmware, reapply the root, run OTA rootkeeper, and try the OTA again... however as your device is the padfone, I'm not exactly sure in what ways you need to go about doing this.
There's some discussion on the subject in the below thread around page 221ish, however there's no new root solution given as of yet.
http://forum.xda-developers.com/showthread.php?t=1106545&highlight=root
Sorry, I couldnt be of more help.
hoyin007 said:
I had the CHT 9.18 too, I had Rootkeeper backup but cannot restore root after updated.
DO NOT update to 9.20 if you want too stay rooted!
I have to flash back old firmware and factory reset to start from scrach again but I had Titanium backup on MicroSD.
Don't try it till there is root method for CHT 9.20
Click to expand...
Click to collapse
Just out of interest, did you apply the OTA or did you download the 500MB file from the ASUS support site and install that from the SD card?
Does anyone have the ~146MB OTA file? And if not, does anyone have the exact file name?
Thanks.
Related
all i get is a error like this
"---------------------------------------------------------------
One-Click Root ToolKit For Evo 4G LTE!
Script by Max Lee from OneXRoot.com
Credits go to XDA users sparkym3 and Dan Rosenburg for exploit.
---------------------------------------------------------------
[*] This script will:
(1) root your Evo 4G LTE on ICS
(2) install Busybox
(3) install SU files
[*] Before u begin:
(4) Make sure to read full instructions at HTCEvoHacks.com!
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Please hit Enter when ready.
Press any key to continue . . .
Rooting...
* daemon not running. starting it now *
* daemon started successfully *
Start Rooting...
failed on '/data/local/tmp' - Permission denied
link failed File exists
reboot #1 - DO NOT DISCONNECT YOUR DEVICE!
/system/bin/sh: cannot create /data/local.prop: Permission denied
reboot #2 - DO NOT DISCONNECT YOUR DEVICE!
remount failed: Operation not permitted
failed to copy 'su' to '/system/bin/su': Read-only file system
Unable to chmod /system/bin/su: No such file or directory
Unable to chmod /system/bin/su: No such file or directory
rm failed for /system/xbin/su, No such file or directory
link failed Read-only file system
failed to copy 'Superuser.apk' to '/system/app/./Superuser.apk': Read-only file
system
rm failed for /data/local.prop, No such file or directory
rm failed for /data/local/tmp, Permission denied
failed on '/data/local/tmp.bak' - No such file or directory
5384 KB/s (1075144 bytes in 0.195s)
mount: permission denied (are you root?)
/system/xbin/busybox: cannot open for write: Read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
/system/bin/sh: /system/xbin/busybox: not found
rebooting
All Done rooting Evo 4G LTE, check out OneXRoot.com for more cool stuff like ROM
s, hacks, tips, and more!
Press any key to continue . . ."
can any body help ?
Use regawmod...or if your on 1.13 use lazy panda
Sent from the depths of hell
wileout said:
Use regawmod...or if your on 1.13 use lazy panda
Sent from the depths of hell
Click to expand...
Click to collapse
whast lazy panda ?
One, this should have been posted in the q&a thread.
Two, lazy panda is a method to achieve s-off. Make sure your not on hboot 1.15. If you are, just kick it for a bit.
You can also unlock it through HTC dev, load a custom Rom that's already rooted (I like meanrom), and wait further development for hboot 1.15
Sent from my EVO using xda premium
foobz said:
One, this should have been posted in the q&a thread.
Two, lazy panda is a method to achieve s-off. Make sure your not on hboot 1.15. If you are, just kick it for a bit.
You can also unlock it through HTC dev, load a custom Rom that's already rooted (I like meanrom), and wait further development for hboot 1.15
Sent from my EVO using xda premium
Click to expand...
Click to collapse
how can i root my phone and get super user to get roms on my phone is thier any way i can get help ?
read read read read!!!!!!!
evo401 said:
read read read read!!!!!!!
Click to expand...
Click to collapse
ok how can i root my phone ?
slagle96 said:
how can i root my phone and get super user to get roms on my phone is thier any way i can get help ?
Click to expand...
Click to collapse
Look in this thread. There's no need to panic
http://forum.xda-developers.com/showthread.php?t=1690919
volk9029 said:
Look in this thread. There's no need to panic
http://forum.xda-developers.com/showthread.php?t=1690919
Click to expand...
Click to collapse
when i did that way of rooting i all i get is that it switches from login good then signs out real quick like 50 times
slagle96 said:
ok how can i root my phone ?
Click to expand...
Click to collapse
By reading and researching and posting in the correct section.
uninstall htc sync
Hi,
I would like to know if voodoo rootkeeper is able to restore the root after the JB update ?
Greamlive said:
Hi,
I would like to know if voodoo rootkeeper is able to restore the root after the JB update ?
Click to expand...
Click to collapse
Worked for me
Does anyone know if the built in "OTA Root keeper" in SuperSU works too?
Sent from my Galaxy Nexus using Tapatalk 2
Unfortunately rootkeeper did not work for me. TPSparkyRoot and Debugfs were unsuccessful. Does anyone know of a root method for JB? The method used for TF300 perhaps?
Greamlive said:
Hi,
I would like to know if voodoo rootkeeper is able to restore the root after the JB update ?
Click to expand...
Click to collapse
Worked fine for me. FYI if you are using EZOverclock.apk freeze or remove it.
Scumbag Inc. said:
Unfortunately rootkeeper did not work for me. TPSparkyRoot and Debugfs were unsuccessful. Does anyone know of a root method for JB? The method used for TF300 perhaps?
Click to expand...
Click to collapse
Currently (to the best of my knowledge), the only way they could have root on the TF300 with JB was to restore root using both SuperSU and OTA Rootkeeper. There haven't been any new exploits as far as I know.
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app.
Rootkeeper did not work for me. The only apps I was using that required root were Titanium Backup and Samba Fileshare, plus obviously Super User and Busy Box. Anyway I can't use them now, with no root after updating to 4.1.1 despite Rootkeeper.
Something to take note of. Prior to the update I deleted my su backup and did it over again. Don't know if that made a difference or not but that was the only thing I did prior to the JB update.
Rooted, stock, locked bootloader.
My Transformer Prime just finished the update successfully!
Took several minutes to do whatever it does.
Lost root when updated, but Voodoo OTA RootKeeper restored root.
Nice to have JB on my Prime and Nexus 7.
Darkseider said:
Something to take note of. Prior to the update I deleted my su backup and did it over again. Don't know if that made a difference or not but that was the only thing I did prior to the JB update.
Click to expand...
Click to collapse
I checked and I have no /system/su_backup file, despite OTA RootKeeper telling me it was there before I installed the JB OTA. I wonder if my doing a cold boot before installing the OTA somehow erased the su_backup? I wish I had copied it somewhere else.
So I Do Have Su Backup File in sys but it doesnt work any thoughts? root keeper says it works but doesnt acually work
Updateing now.
I just erased and recreated my su backup with Voodo's OTA Rootkeeper.
back in a minute.
-------------
EDIT:
no dice.
installs .
restores the su binary at /system/bin/su
but it does not work.
-------------
Update got root access though adb using the backup su binary at /system/usr/we-need-root/su-backup
i just used the full path at the commad line...
copied the binary to /system/bin/su
more later.
-------------
Update:
got root working using
Root MANY ANDROID! [Upd: 20.09.2012]
I use linux so i just followed the steps in the batch file ( following the GOTO jumps for normal install) .
Problems:
this is the script i followed. it is in the zip at the link.
These are the command i used from the file. on linux i just replaced the stuff\adb.exe part with adb at the command line.
The files would not push to /data/local/tmp directly so i pushed the files to /sdcard/tmp then used adb shell and su'ed to cp (mv gave errors) them to /data/local/tmp
Code:
:START
echo Pushing busybox....
stuff\adb.exe push stuff/busybox /data/local/tmp/.
echo Pushing su binary ....
stuff\adb.exe push stuff/su /data/local/tmp/.
echo Pushing Superuser app
stuff\adb.exe push stuff/Superuser.apk /data/local/tmp/.
echo Making busybox runable ...
stuff\adb.exe shell chmod 755 /data/local/tmp/busybox
When i launched the backup app from adb it did not appear to ever stop. so i closed it after about 5 minutes and rebooted then continued.
Code:
stuff\adb.exe restore stuff/fakebackup.ab
echo Please look at your device and click RESTORE!
echo If all is successful i will tell you, if not this shell will run forever.
echo Running ...
stuff\adb.exe shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done" > NUL
echo Successful, going to reboot your device!
stuff\adb.exe reboot
echo Waiting for device to show up again....
ping -n 10 127.0.0.1 > NUL
stuff\adb.exe wait-for-device
The busybox binary did not work so i just used regular commands at adb shell prompt. Some of the commands required me to su first.
Code:
echo Going to copy files to it's place
stuff\adb.exe shell "/data/local/tmp/busybox mount -o remount,rw /system && /data/local/tmp/busybox mv /data/local/tmp/su /system/xbin/su && /data/local/tmp/busybox mv /data/local/tmp/Superuser.apk /system/app/Superuser.apk && /data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox && chown 0.0 /system/xbin/su && chmod 06755 /system/xbin/su && chmod 655 /system/app/Superuser.apk && chmod 755 /system/xbin/busybox && rm /data/local.prop && reboot"
:FINISH
echo You can close all open command-prompts now!
echo After reboot all is done! Have fun!
echo Bin4ry
pause
I may have left out some steps but if you follow the script and use su at the adb shell prompt you can get most of the steps to work. If there is enough demand i may put together a shell/bat script.
Greamlive said:
Hi,
I would like to know if voodoo rootkeeper is able to restore the root after the JB update ?
Click to expand...
Click to collapse
I had no issues. restored root perfectly
I lost root. Before i updated I deleted my backed up root in root keeper then protected again. Then updated to jb with file. Lost root but voodoo says I have a protected copy. But pressing restore does not bring it back. Hope there's a way to bring it back.
Edit: I did not temp unroot b4 update. Maybe my problem?
Sent from my DROID RAZR using xda app-developers app
Shinare said:
I lost root. Before i updated I deleted my backed up root in root keeper then protected again. Then updated to jb with file. Lost root but voodoo says I have a protected copy. But pressing restore does not bring it back. Hope there's a way to bring it back.
Click to expand...
Click to collapse
If i remember correctly from one of the previous updates, updating using a file is what caused voodoo to not be able to restore the root.
I had to wait until they found a new exploit to get it back.
x-web said:
I may have left out some steps but if you follow the script and use su at the adb shell prompt you can get most of the steps to work. If there is enough demand i may put together a shell/bat script.
Click to expand...
Click to collapse
I appreciate you pointing this out but here's the problem I'm running into. "mount: permission denied"
I can't su because I don't have root.
Here's what I do.
1. After knowing Superuser could very possibly be failed to restore root, I downloaded SuperSu in Google Play and installed it. Updated new binary of SuperSU.
2. Deleted the old backup in OTA Rootkeeper and protect the new root.
3. Went through OTA.
4. restored root from OTA Rootkeeper. Voila.
Something strange is going on here, i restored root with OTA root keeper, everything worked well and when i check status it states that my device is rooted and root permission granted.
Titanium Backup works perfectly as well, but other apps like Gesture Control are unable to get root access and when i run a root checker app it says that I dont have proper root access. Is there a way to fix this? Or is my root lost? I still have some hope as it works fine with TB
Stuff i'm still able to do:
-Temp unroot/reroot with OTA root keeper
-delete SU backup and make a new one
-Use Titanium Backup
-Use any root explorer i've tested so far, i can also access /data folder!
-Use Terminal emulator
-Also the file system/bin/SU is present.
What i cant do:
-app: gesture control
-update my SU binary with superuser app
-update my busybox using BusyBox free from play store
there must be a way!
Damn pissing on my sunny day. I want to see JB but am afraid of what problems it will cause. Thanks to all that posted saying OTA worked I hope it works for me too.
iamhcg said:
Here's what I do.
1. After knowing Superuser could very possibly be failed to restore root, I downloaded SuperSu in Google Play and installed it. Updated new binary of SuperSU.
2. Deleted the old backup in OTA Rootkeeper and protect the new root.
3. Went through OTA.
4. restored root from OTA Rootkeeper. Voila.
Click to expand...
Click to collapse
I did the same and can confirm that I successfully restored root.
I'm trying to root my tablet once again after I accidently unrooted it. I done tried three diffrent rooting methods: "SparkyRoot" "debugfs" and "Primetime" and all came unsuccessful. I keep getting a message in the command prompt saying access denied when it try to copy files to root it.
It look like this:
Found system partition at: /dev/block/mmcblk0p1
Step 1- pushing files...
failed to copy ' debugfs' to ' /data/local//debugfs'ermission denied
failed to copy' su' to /data/local//su': Permission denied
failed to copy' debugfsinput' to '/data/ local// debugfsinput': Permission denied
failed on '/date/ local/tmp'- Permission denied
^^^^I get that everytime.....what could be the problem, how do I fix it. Before you ask YES android debugging is enable and YES Unknown Sources is enable. So please tell me what I need to do to fix this problem.
You have to be able to obtain root permissions to mount the file system with RW so you can move/copy files to then get root all the time.
The permission denied is because you arent root and/or havent remounted teh filesystem read write (possibly because you can't get the access you need) and this the file move/copies fail.
How do you root? Good question. One I have been struggling with for days.
I have the same issue with my infinity
TF201 Root Fix
I was having the same problem when trying to regain root access after update to JB from ICS. Try Urkel's Fresh Root or Urkel's Fresh Start, see the thread on this site.
alexmojo said:
I was having the same problem when trying to regain root access after update to JB from ICS. Try Urkel's Fresh Root or Urkel's Fresh Start, see the thread on this site.
Click to expand...
Click to collapse
i do believe urkels requires unlocked bootloader.
This works flawlessly!!
http://forum.xda-developers.com/showthread.php?p=32825557
I dont get it
hx4700 Killer said:
You have to be able to obtain root permissions to mount the file system with RW so you can move/copy files to then get root all the time.
The permission denied is because you arent root and/or havent remounted teh filesystem read write (possibly because you can't get the access you need) and this the file move/copies fail.
How do you root? Good question. One I have been struggling with for days.
Click to expand...
Click to collapse
Your answere is the closed i ever come to solveing this issue on My infinity, yet i dont know if what you just Said was à statment or answere to the question. Please elaborate for à stupid noob who is sick of trying to find the answere on the web...i am desperat
qiuness said:
This works flawlessly!!
http://forum.xda-developers.com/showthread.php?p=32825557
Click to expand...
Click to collapse
I am having the same issues. Has anyone figured this out? I have the asus tf700t.
Thanks
I am wondering if anyone knows of a way to take the latest ota zip for the Xperia S, decrypt it, edit the version, repack it, then be able to flash it. Right now it will not let me flash over the current version r5 because it is the same version. I am stuck on the blue wave animation perpetually after screwing up my services.jar. I have no adb access and my only hope is to flash in recovery or wait until the next update comes out...
I was told by a Sony tech yesterday the Jelly Bean update for the Xperia S will not be until January...
EDIT: There is a way to fool the recovery. Does anyone have a modified r5 ota for the Xperia edited for a higher incremented version they could share?
bjanice44 said:
I am wondering if anyone knows of a way to take the latest ota zip for the Xperia S, decrypt it, edit the version, repack it, then be able to flash it. Right now it will not let me flash over the current version r5 because it is the same version. I am stuck on the blue wave animation perpetually after screwing up my services.jar. I have no adb access and my only hope is to flash in recovery or wait until the next update comes out...
I was told by a Sony tech yesterday the Jelly Bean update for the Xperia S will not be until January...
EDIT: There is a way to fool the recovery. Does anyone have a modified r5 ota for the Xperia edited for a higher incremented version they could share?
Click to expand...
Click to collapse
If it is the same as Sony Tab S then you would need to disable the signature check to flash a modded update. To add to the bad news, that is no longer able to work with new recovery (that came with r5, for older tab anyway)
Any chance you can take it in under warrantly?? They may not be able to tell that you messed with it
stifilz said:
If it is the same as Sony Tab S then you would need to disable the signature check to flash a modded update. To add to the bad news, that is no longer able to work with new recovery (that came with r5, for older tab anyway)
Any chance you can take it in under warrantly?? They may not be able to tell that you messed with it
Click to expand...
Click to collapse
Thanks for the response. Yeah I guess I am going to have to send it in or .. the other option is to wait for another update, but not knowing when that will be sucks. The Sony tech told me yesterday (when I called to find out my options..and I can send it in) that the Jelly Bean update is coming in January..So the question is will Sony have another update to ICS before then. Perhaps..
bjanice44 said:
Thanks for the response. Yeah I guess I am going to have to send it in or .. the other option is to wait for another update, but not knowing when that will be sucks. The Sony tech told me yesterday (when I called to find out my options..and I can send it in) that the Jelly Bean update is coming in January..So the question is will Sony have another update to ICS before then. Perhaps..
Click to expand...
Click to collapse
The funny thing is that I know which file is corrupted in the system. Its the services.jar. If only there was a way for me to replace that file....It would boot.
bjanice44 said:
The funny thing is that I know which file is corrupted in the system. Its the services.jar. If only there was a way for me to replace that file....It would boot.
Click to expand...
Click to collapse
Yeh guttered. Can you check if you can get adb shell in recovery??? I know it is late now but this is why the AIO tool changes the incremental to a lower one... So we can flash same update if it turns to custard
stifilz said:
Yeh guttered. Can you check if you can get adb shell in recovery??? I know it is late now but this is why the AIO tool changes the incremental to a lower one... So we can flash same update if it turns to custard
Click to expand...
Click to collapse
No ADB shell. I guess I'll send it in. Watch.. 2 days after I send it in there will be an update..
bjanice44 said:
No ADB shell. I guess I'll send it in. Watch.. 2 days after I send it in there will be an update..
Click to expand...
Click to collapse
Lol. That would be awesome
stifilz said:
If it is the same as Sony Tab S then you would need to disable the signature check to flash a modded update. To add to the bad news, that is no longer able to work with new recovery (that came with r5, for older tab anyway)
Any chance you can take it in under warrantly?? They may not be able to tell that you messed with it
Click to expand...
Click to collapse
stifilz is there really no other way we can revert back to the old Recovery? I mean like finding someone who is still on HC 3.2? and asking him to prepare the needed stuffs like the decrypt one? sorry but im really desperate on fixing the issue my tab is experiencing. and can we still hope for an updated AIO tool that might even work with the latest recovery mode?
mawnstermew said:
stifilz is there really no other way we can revert back to the old Recovery? I mean like finding someone who is still on HC 3.2? and asking him to prepare the needed stuffs like the decrypt one? sorry but im really desperate on fixing the issue my tab is experiencing. and can we still hope for an updated AIO tool that might even work with the latest recovery mode?
Click to expand...
Click to collapse
I have tried to flash 11000 (3.2), 0035(3.2.1), 0042(3.2.1R2), ICS, R1A and NONE of these change the recovery back, i also tied NZ and US files, I was lucky enough to locate US files and had the NZ files saved to my PC. I have looked into AIO tool and read through the code, it runs a certain command in adb shell in recovery (WHICH WE NO LONGER HAVE GRR) so it can not be done ATM.
Maybe there is some file we can change on the tab to enable shell in adb again. From memory shell does not work with non-root devices and when we root we can use adb shell. (Can someone verify this, bad memory lol)
Anyway there could be something I am missing, well hoping anyway
You know you can change the incremental in vendor/vendor.prop to a lower one to flash an OLDER OTA.... Right??
Stifilz
stifilz said:
I have tried to flash 11000 (3.2), 0035(3.2.1), 0042(3.2.1R2), ICS, R1A and NONE of these change the recovery back, i also tied NZ and US files, I was lucky enough to locate US files and had the NZ files saved to my PC. I have looked into AIO tool and read through the code, it runs a certain command in adb shell in recovery (WHICH WE NO LONGER HAVE GRR) so it can not be done ATM.
Maybe there is some file we can change on the tab to enable shell in adb again. From memory shell does not work with non-root devices and when we root we can use adb shell. (Can someone verify this, bad memory lol)
Anyway there could be something I am missing, well hoping anyway
You know you can change the incremental in vendor/vendor.prop to a lower one to flash an OLDER OTA.... Right??
Stifilz
Click to expand...
Click to collapse
-.- sadly i dont know how to change such things. can you please tell me how to do it? ive been looking for ways to downgrade to HC but iim getting prohibit basebrand or SKU version or something like that
mawnstermew said:
-.- sadly i dont know how to change such things. can you please tell me how to do it? ive been looking for ways to downgrade to HC but iim getting prohibit basebrand or SKU version or something like that
Click to expand...
Click to collapse
Use AIO tool. Tweaks and mods then install rescue backdoor
Or
Download root explorer or similar. Open riot exolorer and navigate to vendor folder.
Long click vendor.prop and then select edit with text editor
Change the number to a lower one. Take of the last digit will do.
Click three dots for options and save
All done flash what you like
stifilz said:
Use AIO tool. Tweaks and mods then install rescue backdoor
Or
Download root explorer or similar. Open riot exolorer and navigate to vendor folder.
Long click vendor.prop and then select edit with text editor
Change the number to a lower one. Take of the last digit will do.
Click three dots for options and save
All done flash what you like
Click to expand...
Click to collapse
That one needs a rooted tablet right? Im having troubles rootig my tab even with b4narys script. If I choose to downgrade to 3.2 what no should I chane the las t two digits to?
mawnstermew said:
That one needs a rooted tablet right? Im having troubles rootig my tab even with b4narys script. If I choose to downgrade to 3.2 what no should I chane the las t two digits to?
Click to expand...
Click to collapse
Needs root yes. Just delete the last digit
stifilz said:
Needs root yes. Just delete the last digit
Click to expand...
Click to collapse
thanks! BTW im still able to flash to ICS updates right? BTW im not able to install pre rooted ics if i try to reflash to lower versions due to the inability of AIO tool to decrypt?
From AIO you can decrypt and flash anything lol. Except if you have the r5 recovery it wont work at all
i tried with B4nary's script again but all im getting is the terminal emulator. did you do something with the backupandrestore.apk? cuz i tried installing it and im getting forced close everytime i try to open it.
BTW im on r5 so i wont be able to downgrade? im still stuck at rooting it
mawnstermew said:
i tried with B4nary's script again but all im getting is the terminal emulator. did you do something with the backupandrestore.apk? cuz i tried installing it and im getting forced close everytime i try to open it.
BTW im on r5 so i wont be able to downgrade? im still stuck at rooting it
Click to expand...
Click to collapse
You are typing in /data/local/tmp/onload.sh and then /data/local/tmp/onload2.sh????
You can change incremental after root and flash a ICS or R1A or even HC if you have the file
Stifilz
stifilz said:
You are typing in /data/local/tmp/onload.sh and then /data/local/tmp/onload2.sh????
You can change incremental after root and flash a ICS or R1A or even HC if you have the file
Stifilz
Click to expand...
Click to collapse
i just followed the instrucions stated here http://forum.xda-developers.com/showthread.php?t=1886460 i used the normal mode to unlock but then im getting the on the "mount: permission denied and then i tried using special mode to root and finally after everything was done all that was installed in my tablet is a terminal emulator, some applications were lost in the process such as my avast anti virus and play store.
stifilz said:
You are typing in /data/local/tmp/onload.sh and then /data/local/tmp/onload2.sh????
You can change incremental after root and flash a ICS or R1A or even HC if you have the file
Stifilz
Click to expand...
Click to collapse
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[email protected]:/ $ /data/local/tmp/onload.sh
Unable to chmod /data: Operation not permitted
Unable to chmod /data/local/tmp/mkdevsh: Operation not permitted
failed on 'property' - Permission denied
mkdir failed for property, File exists
link failed Permission denied
link failed Permission denied
rm failed for property, Permission denied
failed on 'property.org' - Permission denied
255|[email protected]:/ $ data/local/tmp/onload2.sh
Unable to chmod /data: Operation not permitted
Unable to chmod /data/local/tmp/remount.sh: Operation not permitted
failed on 'property' - Permission denied
mkdir failed for property, File exists
link failed Permission denied
link failed Permission denied
rm failed for property, Permission denied
failed on 'property.org' - Permission denied
255|[email protected]:/ $
btw stifilz, can you share to me your edited bin4ry's script? the one with the re-signed vpnfaker? it tried signing it but it still doesnt work saying something about the vpnfaker. I think there was something wrong with the way i signed it. it might work if i try to use the one you made.
mawnstermew said:
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[email protected]:/ $ /data/local/tmp/onload.sh
Unable to chmod /data: Operation not permitted
Unable to chmod /data/local/tmp/mkdevsh: Operation not permitted
failed on 'property' - Permission denied
mkdir failed for property, File exists
link failed Permission denied
link failed Permission denied
rm failed for property, Permission denied
failed on 'property.org' - Permission denied
255|[email protected]:/ $ data/local/tmp/onload2.sh
Unable to chmod /data: Operation not permitted
Unable to chmod /data/local/tmp/remount.sh: Operation not permitted
failed on 'property' - Permission denied
mkdir failed for property, File exists
link failed Permission denied
link failed Permission denied
rm failed for property, Permission denied
failed on 'property.org' - Permission denied
255|[email protected]:/ $
btw stifilz, can you share to me your edited bin4ry's script? the one with the re-signed vpnfaker? it tried signing it but it still doesnt work saying something about the vpnfaker. I think there was something wrong with the way i signed it. it might work if i try to use the one you made.
Click to expand...
Click to collapse
Ok doubt it will work but it is attached. I have zipped it up to add as attachment.
Please unzip it and then replace the file (of same name) in the 'stuff' directory of bin4ry's tool.
Good luck once again
Hey Guys -
After being an iPhone fanboy for years, I recently went to Android to try something new. For two months, I've been running Revolution HD (4.3) on my HTC One - but - yesterday decided to give Venom ViperOne a try. I downloaded the latest version, booted to recovery (TWRP) wipred cache, and applied new ROM.
Everything seemed to work great, but after getting many things set up, I found out that I didn't have full root access. When laucnhing SuperSU, it said something like the binaries were not installed, but I finally got that to go away. Re-installing the binary via Recovery didn't fix everything, though.
I installed Root Checker Pro and here is what it said about my phone:
Root Access is not properly configured or was not granted.
Super User Application Status:
SuperSU application - version 1.69 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwxr-xr-x root root 104556 2013-11-17 20:25 su
Analysis: Setuid attribute is NOT present BUT root user ownership is present. Root access is NOT correctly configured for this file!
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: root user - ro.secure=0
I have tried many suggestions and now have 3 different zip files for SuperSU that I've tried. I'm still researching, but any suggestions would be fantastic... Thanks!
Click build number at setting 7 times until it appear developer option, change root access to app and adb, see if that can solved your problem
Sent from my Yuga powered by Asyluminator CM10.2 by chasmodo.
Thanks for your reply. Fortunately, I finally fixed it by doing the following:
1. Uninstalled SuperSU via Play Store
2. Downloaded the 1.69 SuperSU update file and installed it through Recovery.
3. Re-installed SuperSU via Play Store
Once I did this, it verified working 100% again in apps as well as passed verification.
Thanks again for your help!
No sweat, Glad you've solved your problem
Sent from my Yuga powered by Asyluminator CM10.2 by chasmodo.
THANKS!
bzowk said:
Thanks for your reply. Fortunately, I finally fixed it by doing the following:
1. Uninstalled SuperSU via Play Store
2. Downloaded the "" and installed it through Recovery.
3. Re-installed SuperSU via Play Store
Once I did this, it verified working 100% again in apps as well as passed verification.
Thanks again for your help!
Click to expand...
Click to collapse
Thanks man I was stuck with no root access for the longest. This worked!
Su not found
Thanks again for your help![/QUOTE]
Error in tmp/sideload/package.zip (Status 255)
McNaireP said:
Thanks again for your help!
Error in tmp/sideload/package.zip (Status 255)
Click to expand...
Click to collapse
why are you sideloading superSU ?
just copy it to your phone storage and flash it with TWRP /CWM
http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
clsA said:
why are you sideloading superSU ?
just copy it to your phone storage and flash it with TWRP /CWM
"1.93"
Click to expand...
Click to collapse
Using CWM to do just that, flash 1.93 update to fix the fact that 'su' disappeared after KDZ update to ICS, trying go back to GB KDZ Stock has me stuck at LG logo. tried re-flashing a number of times...just going around in circles...
pls delete - wrong thread SRY!
azliazmi said:
Click build number at setting 7 times until it appear developer option, change root access to app and adb, see if that can solved your problem
Sent from my Yuga powered by Asyluminator CM10.2 by chasmodo.
Click to expand...
Click to collapse
You saved my skin. Thanks so much!
Sudo password