lol, just when I read your message, my phone ends Upgrading to kit kat,
I'll have to wait then, but I can do root and install recovery?
Greetings buddy
Yup
Sent from my HTC Butterfly s using XDA Premium 4 mobile app
lol, just when I read your message, my phone ends Upgrading to kit kat,
I'll have to wait then, but I can do root and install recovery?
Greetings buddy
Well I tried all the steps but the damn phone is still S-ON.
Here is my configuration:
Rooted
Android version: 4.3
Htc sense: 5.5
Software number: 2.21.708.1
Htc sdk api level: 5.65
kernel version: 3.4.10-g158f9a4 root@abm010#1
Please find below my cmd window which just hanged out and a print screen of my bootloader... Hope this helps! Thanks a lot!
View attachment 2602156
View attachment 2602157
Am I the only one having the above issue/configuration for which the s-off could not be done? Thanks!
i had that problem and it was because the screen of the cellphone was turned off, it needs to be on aaaall the time. but now you have kit kat man, sorry for that, you just need to wait!!
Well I didn't put kitkat yet I was waiting for you .....so I'll give it a try...I'll let you know...Thanks!
I don't think it is working! This S-OFF procedure works so far until version 1.55 (including)hello
I returned to the base ROM, and my HBOOT is 1.57, this method will work now?
regards
I don't think it is working! This S-OFF procedure works so far until version 1.55 (including)
hello
any idea how to get back to 1.55 HBOOT? or will I have to wait for the s-off this support?
regards
Hey guys, I just upgraded to 4.4.2 and I'm really hating it so far. Unable to move files around my own SD card, phone turns unresponsive or hangs every couple of minutes.. not fun.
Tried getting S-off and root so I can flash to a custom rom, but after issuing this command: "/data/local/tmp/temproot"
I get this:
[*] Attempting to aquire root. This will take 5-10 minutes, be patient
error in setsockopt().
Failed to get prepare_kernel_cred address.
Failed to get commit_creds address.
Failed to get ptmx_fops address.
Failed to setup variables.
If it helps, there is no actual /data/local folder on the SD card even though I issued the push commands. Or am I mistaken and push doesn't copy the files to the phone?
View attachment 2774327
OPTIONAL] Locking bootloader and clearing "tampered" flag Not OK , help
error step: echo-ne '\ x00 \ x00 \ x00 \ x00' | dd of = / dev/block/mmcblk0p3 bs = 1 seek = 33 796
>>>>>> Cannot open for write : Permission denied
NOT S-0FF hu hu hu hu hu hu hu hu hu hu
You can see that the su call failed. The character at the end of the prompt didn't change from '$' to '#'. Also, immediately after the su command, the prompt displays '1|shell@dlxpul', where the '1' at the beginning means the su command exited with an error status.
You may have failed to confirm the su command on-screen; so far every su binary I tried displayed a dialog asking for confirmation even for shells started via adb shell.
You can see that the su call failed. The character at the end of the prompt didn't change from '$' to '#'. Also, immediately after the su command, the prompt displays '1|shell@dlxpul', where the '1' at the beginning means the su command exited with an error status.
You may have failed to confirm the su command on-screen; so far every su binary I tried displayed a dialog asking for confirmation even for shells started via adb shell.
So now I have to do. I root successfully. But not S Off. .. Please help me ....:good::good:
View attachment 2776847
adb reboot
adb wait-for-device push firewater /data/local/tmp
adb push temproot /data/local/tmp
adb shell
chmod 755 /data/local/tmp/temproot
chmod 755 /data/local/tmp/firewater
/data/local/tmp/temproot
/data/local/tmp/firewater
mount -o remount,rw -t ext4 /dev/block/mmcblk0p38 /system
cat /storage/ext_sd/su > /system/xbin/su
chmod 04755 /system/xbin/su
adb devices
adb shell
su
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
exit
exit
adb reboot bootloader
adb devices
adb shell
su
echo -ne '\x00' | dd of=/dev/block/mmcblk0p7 bs=1 seek=4265988
exit
exit
adb reboot bootloader
i have one question and one comment:
1. if i was root and only did firewater, do i need to do since number 15?
2. i did this with my usb 3.0, i know is not recommended, but the device was not recognized in adb. and other thing: be really aware of the screen, if it shuts down the commands will not be working.
cheers
Am I the only one having the above issue/configuration for which the s-off could not be done? Thanks!
i had that problem and it was because the screen of the cellphone was turned off, it needs to be on aaaall the time. but now you have kit kat man, sorry for that, you just need to wait!!
Well I didn't put kitkat yet I was waiting for you .....so I'll give it a try...I'll let you know...Thanks!