Related
i get and error that says " E:Error in /sdcard/Roms/update-dm-7.1.0-Faschinate-sighned.zip (Status 7) Installation aborted"? anybody now whats wrong? i cleared everything and flashed it.
ramongarza said:
i get and error that says " E:Error in /sdcard/Roms/update-dm-7.1.0-Faschinate-sighned.zip (Status 7) Installation aborted"? anybody now whats wrong? i cleared everything and flashed it.
Click to expand...
Click to collapse
could you list what rom you were on and what steps you took to flash cm7.1 please?
Im a bit of a noob and i rooted my phone using odin. i flashed a ec10_nonvoodoo.zip on my phone all it did was change my boot logo screen to say "android" sideways in blue yet everything is pretty much the same i believe. the steps i took were to to a nandroid back up, then i cleared everything it said to including the factory settings. then i installed from zip = [ROM] CyanogenMod 7 for the Samsung Fascinate :: V7.1.0 but it said a bunch of prop errors and (stage 7)? please help?
ramongarza said:
Im a bit of a noob and i rooted my phone using odin. i flashed a ec10_nonvoodoo.zip on my phone all it did was change my boot logo screen to say "android" sideways in blue yet everything is pretty much the same i believe. the steps i took were to to a nandroid back up, then i cleared everything it said to including the factory settings. then i installed from zip = [ROM] CyanogenMod 7 for the Samsung Fascinate :: V7.1.0 but it said a bunch of prop errors and (stage 7)? please help?
Click to expand...
Click to collapse
what recovery did you use to flash cm7?
Clockworkmod then later I tried rom manager. Does that answer your question?
Sent from my SCH-I500 using XDA App
follow the steps in this link.
http://forum.xda-developers.com/showthread.php?t=1212239
i loaded the Rom thank you so much man!
Got CWM installed, and CM7 installed and running. superuser is there, but doesn't show any apps yet.
I installed titanium Backup and ran it, but get this error:
Sorry, I could not acquire root privileges. This application will *not* work! etc etc..
It mentioned verifying that busybox was installed, so I went to the market and downloaded the one by jrummy16, tried to run it, but it errors out - no root access.
Then I tried the one by stephen - same issue.
superuser v3.0.5 (39) is installed. It auto-updated to that immediately after the first full boot on CM7 with the market installed.
EDIT -
I uninstalled the superuser update, but still have the same issue. Downloaded rootchecker from the market, here is the output:
Code:
Root Access is not properly configured or was not granted.
Superuser.apk - com.noshufou.android.su - version 3.0.4 is installed!
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
The adb binary is set to default shell user access as root
Standard su binary location: ls -l /system/bin/su:
ls: /system/bin/su: No such file or directory
Standard su binary location: ls -l /system/xbin/su:
ls: /system/xbin/su: No such file or directory
Alternate su binary location:
ls: /sbin/su: Permission denied
Alternate su type binary location:
ls: /system/xbin/sudo: No such file or directory
SU binary not found or not operating properly
Results provided on your SCH-I500 device by Root Checker version 3.7 from joeykrim in the Android Market - http://goo.gl/GgWae
I installed the leaked ICS update, but I have apparently lost root. I tried using Voodoo, but it just says that it has been denied Superuser permissions and that there is no root backup available.
So I tried just plain rooting it using the Motofail method again, to no avail. It says that it is successful in completing the exploit.
However, no matter what app that requires root that I open, it says that the app has been denied Superuser permissions without even prompting me. Root checker says I am not rooted.
I went into the Superuser app, and I went to update the SU Binary. It says that Superuser has been granted Superuser permissions. But then it fails out at the end and says "This updater cannot update the su binary on phones that have some kind of write protection like S-ON. You can continue to use Superuser with your outdated binary, or update su with ROM manager."
I shouldn't even need to update the binary though, since it says I have the latest one installed.
What can/should I do? It's getting kind of annoying not having root on my phone.
Something along the same line happened to me too bro,I also made a thread about it but to no avail:-/ if you find something out,let me know and I'll do the same.
Sent from my DROID RAZR using xda premium
kevintstephens said:
I installed the leaked ICS update, but I have apparently lost root. I tried using Voodoo, but it just says that it has been denied Superuser permissions and that there is no root backup available.
So I tried just plain rooting it using the Motofail method again, to no avail. It says that it is successful in completing the exploit.
However, no matter what app that requires root that I open, it says that the app has been denied Superuser permissions without even prompting me. Root checker says I am not rooted.
I went into the Superuser app, and I went to update the SU Binary. It says that Superuser has been granted Superuser permissions. But then it fails out at the end and says "This updater cannot update the su binary on phones that have some kind of write protection like S-ON. You can continue to use Superuser with your outdated binary, or update su with ROM manager."
I shouldn't even need to update the binary though, since it says I have the latest one installed.
What can/should I do? It's getting kind of annoying not having root on my phone.
Click to expand...
Click to collapse
Try this on ics terminal
Code:
./system/su-backup
mount -o remount,rw /dev/block/system /system
rm /system/bin/su
ln -s /system/su-backup /system/bin/su
Sent from my XT910 using Tapatalk 2
This also happened to me, and ive had no luck rooting either. I used the terminal trick and it says theres nothing to recover i su.
mcnabb311 said:
This also happened to me, and ive had no luck rooting either. I used the terminal trick and it says theres nothing to recover i su.
Click to expand...
Click to collapse
Of course, you need a su bkp first.
Here's mine
http://db.tt/L9TLf2xg
Cheers
Sent from my XT910 using Tapatalk 2
Thanks alot, i must try this.
---------- Post added at 07:46 PM ---------- Previous post was at 07:14 PM ----------
So if you dont have root access, will the terminal move the unzipped su file? How can you apply this to your sysytem? Voodoo doesnt give you options to search for the file either. Of course, nothing has superuser permissions without root either. I guess Im too much of a n00b.
Same here
Na dude its not noobish,im tryna figure out everything myself,I've been flashing since the hd2,so i know a couple things but this is just mind boggeling lol
I'm at a loss. I've downloaded your su-backup file, but I don't know how to move it to the /system folder, as it is write protected, and I don't have root to bypass that. And whenever I tried typing things in using the terminal, it just denied everything.
kevintstephens said:
I'm at a loss. I've downloaded your su-backup file, but I don't know how to move it to the /system folder, as it is write protected, and I don't have root to bypass that. And whenever I tried typing things in using the terminal, it just denied everything.
Click to expand...
Click to collapse
You can't move this file to system folder because you have a non-rooted device. Be patient, we are working hard on that....
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.
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