I did every thing as it is mentioned in the Post, but after i enter
"./misc_version -s 1.31.405.6"
it says:
"permission Denied"
any thing else i can do?
There are two reasons which came into my mind:
1) psneuter did not manage to gain root access.
Otherwise you had permissions to access /dev/block/mmcblk0p17
Did you have "#" prompt when you entered "./misc_version -s 1.31.405.6" command or was the prompt "$" ?
2) there's something wrong with /data/local/tmp/psneuter file. Maybe missing execute permission so it gives "permission Denied" when you are trying to execute it?
Copy-paste of terminal session would help a lot.
Problem solved!
I tried the procedure 3 or 4 times and in all of them I got "#" sign I do not know what was the problem but this last time it worked!
Thank You Very Much
I have the same problem!
Thank You Very Much
Ive pushed all kinds of other stuff, not an nb0 though ...., i did do the add system enviromental variable so this could be my issue, though like i said its worked for other things ...
CANNOT STAT
adb push stock-hc-flyer-hboot_1.11.0006.nb0 / && adb shell dd if=/stock-hc-flyer-hboot_1.11.0006.nb0 of=/dev/block/mmcblk0p18
NO SUCH FILE OR DIRECTORY
a thourough explanation or a cut and paste to get me past this 10+ hours of fail.
Hello,
There are other unanswered posts that deal with this -- so either this is an issue that stumps or it is a simple fix that I cannot find.
Other posts --
http://forum.xda-developers.com/showthread.php?t=953119
http://forum.xda-developers.com/showthread.php?t=2075580
http://forum.xda-developers.com/showthread.php?t=743778
My posts dealing with this --
http://androidforums.com/one-s-all-things-root/705046-s-off-fail.html
I have done something to /sbin/sh it is no longer a directory -- it is still listed in /sbin but you cannot cd to it.
When trying to install apps with "adb install xxxx.apk" I get /sbin/sh pm not found
When trying to do S-off I get a similar error but saying /sbin/sh su not found.
Does anyone know can this be re written? What happens if I delete SH and attempt to recreate? How do i get the proper SH directory for T-mobile HTC one-s
rooted and super CID
As far as I know I am in a place where I cannot go back to stock because of ruu and radios versions ??? It has been awhile since exploring that route.
I am on Viper V2.1
There is most likely nothing wrong with your sh.
It is supposed to be an executable, not a directory.
Are you doing this in recovery or while fully booted?
I bet you're in recovery and I bet you have to be booted in Android.
An adb shell in recovery is already root. You don't need/have su. Both pm and su are in /system/bin/ when booted in Android, as is sh by the way. In recovery your shell is /sbin/sh (like yours is) and you have no su or pm.
That first and third one probably did the same thing you did. getprop is also in /system/bin/ when booted, and not on the recovery root fs. Their shell is /sbin/sh and not /system/bin/sh so probably in recovery. The second one actually replaced his sh executable with something else.
Thank you.
That is what I was doing and now I have S-off.
Hello guys, sup?
Well im looking for a solution (if it has) about build.prop editing with adb and the conditions for it is:
-no root (obviously since moto one vision does not have it yet)
-no recovery mode installed (obviously since moto one vision does not have it yet)
actually im trying command
adb pull
C:\adb> adb pull /system/build.prop c:\adb\new and i get adb: error: failed to copy '/system/build.prop' to 'c:\adb\new\build.prop': remote open failed: Permission denied
the intention is to edit build.prop with notepad++ and push build.prop back
tried looking into tutorials around web but no sucess , any help is welcome . :fingers-crossed:
No possibility yet, maybe try edit system.img and flash it
The novel CAT S22 Flip was released in September, and is pretty much the only of its kind. It actually has an unlocked bootloader, and I was excited to try to root it. However, there's no version of TWRP designed specifically for it! Having never rooted anything before, does anyone know my options in this case to get TWRP for this phone? (Or another method of root I'm not aware of would also be fine.) Thanks!
Shoitah said:
The novel CAT S22 Flip was released in September, and is pretty much the only of its kind. It actually has an unlocked bootloader, and I was excited to try to root it. However, there's no version of TWRP designed specifically for it! Having never rooted anything before, does anyone know my options in this case to get TWRP for this phone? (Or another method of root I'm not aware of would also be fine.) Thanks!
Click to expand...
Click to collapse
Hey. I'm in the same boat. I need to add su binary but looks like the only way to do it is with TWRP. Have you succeeded? I keep trying to find a way to do it, so far no luck.
TWRP isn't needed at all to push ( suitable ) SU binary onto Android's filesystem: you achieve this by means of ADB, too
jwoegerbauer said:
TWRP isn't needed at all to push ( suitable ) SU binary onto Android's filesystem: you achieve this by means of ADB, too
Click to expand...
Click to collapse
Sweet!!! How does it look like?
I just tried adb sideload <file.zip> while in recovery mode and i'm getting this
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
When check adb devices its shows that device is unauthorized. But it's only unauthorized in recovery mode.
Actually looks like I have a problem with recovery mode. Instead I'm getting "No command" screen. It's not even getting into recovery
To perform a ADB Sideload - what is used to flash a Stock ROM - phone must get booted into Sideload mode at 1st
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM-ZIP>
adb reboot
Oh cool. Didn't know that I could reboot stratight to sideload and bypass initial recovery menu. Thank you!
As for my previous issue with "No command" error on recovery boot, I managed to resolve it. When It's gets to "No command" screen, you need to hold Power + Volume Down just long enough to tap Volume Up. And then recovery menu will appear. So Press Power + Volume Down and then tap Volume Up.
When I tried to sideload su binary with
Code:
adb sideload <file.zip>
On the mobile screen i'm getting this error
Code:
E:failed to verify whole-file signature. Update package verification took 0.5 s ( result 1)
E:Signature verification failed
E: error: 21
Looks like recovery not allowing to install unsigned packages. Is there a way around it? Do I need to source another su binary or there is a way to sign it?
Ok. I think I'm getting closer to the core issue. I thought that I rooted the device, but I only unlocked the bootloader. So device is not rooted. As per original thread topic, looks like there is still no TWRP yet and boot.img is not accessible to modify. Tried to get boot.img directly from the device, but getting - permission denied.
Any other walkarounds i should try?
SU binary isn't a signed package. It's a ~110KB file you have to push onto Android OS, preferred to /data/local/tmp directory and afterwards have to make it executable.
I've downloaded Chainfire SuperSu Zip packages, unpacked it and got a su file from arm64 folder. As you mentioned, su file is 108.5KB =)
I've pushed it to /data/local/tmp and made it executable
Code:
S22FLIP:/ $ ls -la /data/local/tmp
total 114
drwxrwxrwx 2 shell shell 3488 2022-12-22 09:36 .
drwxr-x--x 4 root root 3488 1970-01-01 12:15 ..
-rwxrwxrwx 1 shell shell 108496 2008-02-29 03:33 su
Maybe I'm missing something, I still get
Code:
S22FLIP:/ $ su
/system/bin/sh: su: inaccessible or not found
You must tell Android where the SU binary is located
Code:
cd /data/local/tmp & su
or
Code:
/data/local/tmp/su
jwoegerbauer said:
You must tell Android where the SU binary is located
Code:
cd /data/local/tmp & su
or
Code:
/data/local/tmp/su
Click to expand...
Click to collapse
Hi. I am trying to root the phone. I tried with QFIL to get the boot.img file with no luck.... I am trying now with su. I put the su binary where you said and execute it.
Now what should I do? If you can help me, I will be grateful
IMO you can't root a phone ( a conglomerat of hardware pieces ) but only enable Android OS to run system commands as root ( will say with elevated rights if those are required ) by means of su.
Knowing this you would open a terminal window in Android and type out
Code:
<FULLPATH-TO-SU-BINARY-HERE>/su -c "<SHELL-COMMAND-THAT-REQUIRES-ELEVATED-RIGHTS-HERE>"
Example:
Code:
/data/local/tmp/su -c "mount -o remount,rw -t auto /system"
jwoegerbauer said:
IMO you can't root a phone ( a conglomerat of hardware pieces ) but only enable Android OS to run system commands as root ( will say with elevated rights if those are required ) by means of su.
Knowing this you would open a terminal window in Android and type out
Code:
<FULLPATH-TO-SU-BINARY-HERE>/su -c "<SHELL-COMMAND-THAT-REQUIRES-ELEVATED-RIGHTS-HERE>"
Example:
Code:
/data/local/tmp/su -c "mount -o remount,rw -t auto /system"
Click to expand...
Click to collapse
Doesn't work. It looks like the su binary doesn't grant system commands root
I really don't know what to do......