Related
Question 1: Is this normal, if yes, then how can i find my CID?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Question 2: S-OFF or HTCDev unlock?
Question 3: If S-OFF, which method is easier/better revolutionary or moonshine?
Asad_612 said:
Question 1: Is this normal, if yes, then how can i find my CID?
View attachment 2091535
Question 2: S-OFF or HTCDev unlock?
Question 3: If S-OFF, which method is easier/better revolutionary or moonshine?
Click to expand...
Click to collapse
1 Yes this is normal until you change it.
2 For me, s-off then you can always relock the bootloader without htc knowing you have ever unlocked it for warranty purposes.
3 Both do the same thing so personal preference. I used revone which was very easy but cannot comment on revolutionary as I have not tried it.
bobsie41 said:
1 Yes this is normal until you change it.
2 For me, s-off then you can always relock the bootloader without htc knowing you have ever unlocked it for warranty purposes.
3 Both do the same thing so personal preference. I used revone which was very easy but cannot comment on revolutionary as I have not tried it.
Click to expand...
Click to collapse
If we relocked the bootloader, it will show 'relocked' instead of 'locked' right?
Sent from my HTC One using xda app-developers app
randykzc said:
If we relocked the bootloader, it will show 'relocked' instead of 'locked' right?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
That is only if you do it with the instructions on HTCDEV. With S-OFf you can relock and it will show LOCKED.
fastboot oem readcid
randykzc said:
If we relocked the bootloader, it will show 'relocked' instead of 'locked' right?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
There is an ADB command to change it to 'locked' instead of 'relocked'. It's mentioned in revone's thread:
http://forum.xda-developers.com/showthread.php?t=2314582
I used revone to S-OFF and it was quite easy.
Code:
./revone -l
bobsie41 said:
1 Yes this is normal until you change it.
2 For me, s-off then you can always relock the bootloader without htc knowing you have ever unlocked it for warranty purposes.
3 Both do the same thing so personal prefierence. I used revone which was very easy but cannot comment on revolutionary as I have not tried it.
Click to expand...
Click to collapse
1. I saw other devices pictures which showed CID in bootloader mode, and also my previous HTC OneX had such information available.
2. I'be read somewhere users having issues with S-Off with HTC one. Previously I had Inc S and I S-Off it using revolutionary.
Thanks.
Asad_612 said:
1. I saw other devices pictures which showed CID in bootloader mode, and also my previous HTC OneX had such information available.
2. I'be read somewhere users having issues with S-Off with HTC one. Previously I had Inc S and I S-Off it using revolutionary.
3. Can you provide me the link of renove S-Off?
Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2314582
TarekElsakka said:
There is an ADB command to change it to 'locked' instead of 'relocked'. It's mentioned in revone's thread:
http://forum.xda-developers.com/showthread.php?t=2314582
I used revone to S-OFF and it was quite easy.
Code:
./revone -l
Click to expand...
Click to collapse
while using adb, i keep getting this error:
Code:
1|[email protected]:/ $ adb push revone /data/local/tmp/
adb push revone /data/local/tmp/
error: device not found
1|[email protected]:/ $
any clue how to fix this?
I've updated all the HTC drivers, and adb drivers. My device is turned On, connected to PC via USB, with USB Debugging enabled.
Asad_612 said:
while using adb, i keep getting this error:
Code:
1|[email protected]:/ $ adb push revone /data/local/tmp/
adb push revone /data/local/tmp/
error: device not found
1|[email protected]:/ $
any clue how to fix this?
I've updated all the HTC drivers, and adb drivers. My device is turned On, connected to PC via USB, with USB Debugging enabled.
Click to expand...
Click to collapse
Uncheck in settings/energy/fastboot and close (at the bottom). That may help.
gee2012 said:
Uncheck in settings/energy/fastboot and close (at the bottom). That may help.
Click to expand...
Click to collapse
unchecked, but still the same error :/
Asad_612 said:
unchecked, but still the same error :/
Click to expand...
Click to collapse
Is usb debugging enabled and is HTC Sync manager not running?
gee2012 said:
Is usb debugging enabled and is HTC Sync manager not running?
Click to expand...
Click to collapse
usb debuggin enabled and sync manager updated and running as well...still device not connected error
Asad_612 said:
usb debuggin enabled and sync manager updated and running as well...still device not connected error
Click to expand...
Click to collapse
You have to close sync manager (best is to uninstall except the drivers).
gee2012 said:
You have to close sync manager (best is to uninstall except the drivers).
Click to expand...
Click to collapse
Tried that too, still nothing ... is there any shortcup sort of adb files?
I dont know if there is an issue with my adb files or something else...cause i can start adb shell, but im having problem with it detecting my device...
Asad_612 said:
Tried that too, still nothing ... is there any shortcup sort of adb files?
I dont know if there is an issue with my adb files or something else...cause i can start adb shell, but im having problem with it detecting my device...
Click to expand...
Click to collapse
There is a problem with your drivers somehow, go to device manager in windows and delete the phone from the list. Reboot the pc and try again.
Asad_612 said:
while using adb, i keep getting this error:
Code:
1|[email protected]:/ $ adb push revone /data/local/tmp/
adb push revone /data/local/tmp/
error: device not found
1|[email protected]:/ $
any clue how to fix this?
I've updated all the HTC drivers, and adb drivers. My device is turned On, connected to PC via USB, with USB Debugging enabled.
Click to expand...
Click to collapse
"adb push" command is not shell command!
you need type: adb push revone /data/local/tmp/ before you entered into shell by "adb shell".
1) adb push revone /data/local/tmp/
2) adb shell
3) and so on..
tash2013 said:
"adb push" command is not shell command!
you need type: adb push revone /data/local/tmp/ before you entered into shell by "adb shell".
1) adb push revone /data/local/tmp/
2) adb shell
3) and so on..
Click to expand...
Click to collapse
yea i figured that, but still got error, see this:
Code:
C:\fastboot>adb push revone /data/local/tmp/
2048 KB/s (648208 bytes in 0.309s)
C:\fastboot>cd /data/local/tmp
The system cannot find the path specified.
C:\fastboot>adb shell chmod 755 /data/local/tmp/revone
C:\fastboot>adb shell
[email protected]:/ $ busybox df -h
busybox df -h
/system/bin/sh: busybox: not found
127|[email protected]:/ $
Asad_612 said:
yea i figured that, but still got error, see this:
Code:
C:\fastboot>adb push revone /data/local/tmp/
2048 KB/s (648208 bytes in 0.309s)
C:\fastboot>cd /data/local/tmp
The system cannot find the path specified.
C:\fastboot>adb shell chmod 755 /data/local/tmp/revone
C:\fastboot>adb shell
[email protected]:/ $ busybox df -h
busybox df -h
/system/bin/sh: busybox: not found
127|[email protected]:/ $
Click to expand...
Click to collapse
"C:\fastboot>cd /data/local/tmp" What is it??? You need here to specify a way to yours adb.exe file.
if youer adb.exe in c:\fastboot folder you need
1) c:\fastboot> adb shell
2) [email protected]:/ $ cd /data/local/tmp
3) [email protected]:/ $ chmod 755 revone
4) and so on ..regarding s-off thread
tash2013 said:
"C:\fastboot>cd /data/local/tmp" What is it??? You need here to specify a way to yours adb.exe file.
if youer adb.exe in c:\fastboot folder you need
1) c:\fastboot> adb shell
2) [email protected]:/ $ cd /data/local/tmp
3) [email protected]:/ $ chmod 755 revone
4) and so on ..regarding s-off thread
Click to expand...
Click to collapse
My adb files are in c:\fastboot folder, i followed the process and this is the result, its still not detecting the device:
Code:
C:\fastboot>
C:\fastboot>adb shell
[email protected]:/ $ cd /data/local/tmp
cd /data/local/tmp
[email protected]:/data/local/tmp $ chmod 755 /data/local/tmp/revone
chmod 755 /data/local/tmp/revone
[email protected]:/data/local/tmp $ adb devices
adb devices
List of devices attached
[email protected]:/data/local/tmp $ ./revone -P
./revone -P
revone v0.2.1
Gaining root access (thanks to Dan's motochopper)...[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
251|[email protected]:/data/local/tmp $
Hi guys......
I have Butterfly s 901e with HBOOT 1.57, when I tried to s-off with firewater, I didn't get anything while in the process..... when I made the last step ([email protected]:/ # chmod 755 /data/local/tmp/firewater then [email protected]:/ # /data/local/tmp/firewater), I got nothing.... I tried to check data/local/tmp manually in ES File Explorer to see what is going on, I noticed that after pushing firewater through adb it will appear in the TMP folder and after executing [email protected]:/ # chmod 755 /data/local/tmp/firewater then [email protected]:/ # /data/local/tmp/firewater the firewater file just disappear from TMP folder, and nothing is starting....
please help.
I had some trouble getting S-OFF using HBOOT 1.57, and I finally got it. Here is what I did in hopes someone may find it useful:
Before you Begin:
If you get stuck at the white HTC Logo when booting or you get "Process com.htc.dialer isn't responding" at any point in this guide, or even before it, you are likely missing your Radio. (I don't know exactly how this happens, but it apparently does sometimes.) I had this problem once, and flashing the latest radio from here in recovery fixed it.
Steps:
Flash this ROM. (Other ROMs may work, but this one gave me no trouble at all)
Flash this Kernel. <-- Important! Firewater will fail if you don't do this!
Follow the Firewater Instructions to obtain S-OFF. It should work the very first time. (Use the "normal, rooted device method" set of instructions.)
You should now be S-OFF! After this, you can proceed to flash your favorite ROMs Kernels, and HBOOTs. If you would like to downgrade to HBOOT 1.44 (I did), you can find the files here.
Please post if this works for you or if you need help. Thanks to all the developers who made this possible!
Thank you very so much
thank you very much you helped me save my htc was like brick but since I got resurrect from your guide
Branchys said:
thank you very much you helped me save my htc was like brick but since I got resurrect from your guide
Click to expand...
Click to collapse
Awesome! Glad I could help.
Question
Pew446 said:
I had some trouble getting S-OFF using HBOOT 1.57, and I finally got it. Here is what I did in hopes someone may find it useful:
Before you Begin:
If you get stuck at the white HTC Logo when booting or you get "Process com.htc.dialer isn't responding" at any point in this guide, or even before it, you are likely missing your Radio. (I don't know exactly how this happens, but it apparently does sometimes.) I had this problem once, and flashing the latest radio from here in recovery fixed it.
Steps:
Flash this ROM. (Other ROMs may work, but this one gave me no trouble at all)
Flash this Kernel. <-- Important! Firewater will fail if you don't do this!
Follow the Firewater Instructions to obtain S-OFF. It should work the very first time. (Use the "normal, rooted device method" set of instructions.)
You should now be S-OFF! After this, you can proceed to flash your favorite ROMs Kernels, and HBOOTs. If you would like to downgrade to HBOOT 1.44 (I did), you can find the files here.
Please post if this works for you or if you need help. Thanks to all the developers who made this possible!
Click to expand...
Click to collapse
Hi, what specific ROM and Kernel version did you use to get Firewater to work? I have flashed rom Bad_Boyz_Sprint_ONE_Sense_6_v1.0 and Kernel ElementalX-sprint-m7-13.1 but USB debugging is not working and Firewater is not working properly, I am guessing its a kernel issue. I leave everything on default while installing Kernel thru TWRP. Can you confirm? I appreciate the help
DanielGalan said:
Hi, what specific ROM and Kernel version did you use to get Firewater to work? I have flashed rom Bad_Boyz_Sprint_ONE_Sense_6_v1.0 and Kernel ElementalX-sprint-m7-13.1 but USB debugging is not working and Firewater is not working properly, I am guessing its a kernel issue. I leave everything on default while installing Kernel thru TWRP. Can you confirm? I appreciate the help
Click to expand...
Click to collapse
Did you check if your fastboot drivers are working?
StormyNight said:
Did you check if your fastboot drivers are working?
Click to expand...
Click to collapse
Yes, I did fastboot devices and I got the device listed there. Although I could see that in the phone it does not appear the 4 bars of USB debugging. I had it checked in the Dev Options. When I do the same with the stock 4.4.2 I do get those 4 bars and the indication that the USB debugging is active.
DanielGalan said:
Yes, I did fastboot devices and I got the device listed there. Although I could see that in the phone it does not appear the 4 bars of USB debugging. I had it checked in the Dev Options. When I do the same with the stock 4.4.2 I do get those 4 bars and the indication that the USB debugging is active.
Click to expand...
Click to collapse
Does fastboot devices work in the bootloader?
StormyNight said:
Does fastboot devices work in the bootloader?
Click to expand...
Click to collapse
Yes it gets recognized. But when I turn on the phone and try to run the firewater commands it does nothing. No error nor the prompt of the disclaimer. I thought I better asked you and see if you have any idea of what could be wrong.
DanielGalan said:
Yes it gets recognized. But when I turn on the phone and try to run the firewater commands it does nothing. No error nor the prompt of the disclaimer. I thought I better asked you and see if you have any idea of what could be wrong.
Click to expand...
Click to collapse
firewater, I believe runs with the phone booted into android, not fastboot.
Aldo101t said:
firewater, I believe runs with the phone booted into android, not fastboot.
Click to expand...
Click to collapse
Yeah. I just booted to fastboot to check the drivers. When I push the firewater file I get success. Its just the last command that does no action.
DanielGalan said:
Yeah. I just booted to fastboot to check the drivers. When I push the firewater file I get success. Its just the last command that does no action.
Click to expand...
Click to collapse
Verify if the file access permissions changed.. it might be that chmod isn't working.
StormyNight said:
Verify if the file access permissions changed.. it might be that chmod isn't working.
Click to expand...
Click to collapse
Hi. I meant adb devices. And I was wondering how do I check the file permissions. Can I try to copy firewater with a root file manager ? Thank you
This is what I get in adb
C:\Program Files (x86)\Minimal ADB and Fastboot>adb wait-for-device push firewat
er /data/local/tmp
5927 KB/s (4522136 bytes in 0.745s)
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
[email protected]:/ $ su
su
[email protected]:/ # chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]:/ # /data/local/tmp/firewater
/data/local/tmp/firewater
[email protected]:/ #
After this, there is no action from firewater. I should get a warning prompt, but I don't.
DanielGalan said:
Hi. I meant adb devices. And I was wondering how do I check the file permissions. Can I try to copy firewater with a root file manager ? Thank you
This is what I get in adb
C:\Program Files (x86)\Minimal ADB and Fastboot>adb wait-for-device push firewat
er /data/local/tmp
5927 KB/s (4522136 bytes in 0.745s)
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
[email protected]:/ $ su
su
[email protected]:/ # chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]:/ # /data/local/tmp/firewater
/data/local/tmp/firewater
[email protected]:/ #
After this, there is no action from firewater. I should get a warning prompt, but I don't.
Click to expand...
Click to collapse
Are you doing adb reboot before doing adb wait-for-device? Also make sure that your device has no lock mechanism enabled (pattern lock etc).
StormyNight said:
Are you doing adb reboot before doing adb wait-for-device? Also make sure that your device has no lock mechanism enabled (pattern lock etc).
Click to expand...
Click to collapse
I do, this is what I found weird. Screenshot 1 is stock rom 4.4.2 and it says USB debugging enabled. Screenshot 2&3 is Bad_Boyz_Sprint_ONE_Sense_6_v1.0 ROM with its default kernel, it shows no USB debugging enabled even when its selected
DanielGalan said:
I do, this is what I found weird. Screenshot 1 is stock rom 4.4.2 and it says USB debugging enabled. Screenshot 2&3 is Bad_Boyz_Sprint_ONE_Sense_6_v1.0 ROM with its default kernel, it shows no USB debugging enabled even when its selected
Click to expand...
Click to collapse
No idea :S You might want to uncheck Verify apps over USB in Screenshot 3 btw.
StormyNight said:
No idea :S You might want to uncheck Verify apps over USB in Screenshot 3 btw.
Click to expand...
Click to collapse
I tried but no luck. Is there any other ROM I could try firewater with? I was thinking maybe the Venom.
DanielGalan said:
I tried but no luck. Is there any other ROM I could try firewater with? I was thinking maybe the Venom.
Click to expand...
Click to collapse
Try following the instructions on this post.
StormyNight said:
Try following the instructions on this post.
Click to expand...
Click to collapse
Thank you for bearing with me.
I did as indicated on that post, but still having issues with firewater. This is what I get:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
FA34MS906354 device
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot
C:\Program Files (x86)\Minimal ADB and Fastboot>adb wait-for-device push firewat
er /data/local/tmp
4533 KB/s (4522136 bytes in 0.974s)
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
←7←[r←[999;999H←[[email protected]:/ $ su
su
←7←[r←[999;999H←[[email protected]:/ # chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]:/ # /data/local/tmp/firewater
/data/local/tmp/firewater
[email protected]:/ #
There is no action after this
DanielGalan said:
Thank you for bearing with me.
I did as indicated on that post, but still having issues with firewater. This is what I get:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
FA34MS906354 device
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot
C:\Program Files (x86)\Minimal ADB and Fastboot>adb wait-for-device push firewat
er /data/local/tmp
4533 KB/s (4522136 bytes in 0.974s)
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
←7←[r←[999;999H←[[email protected]:/ $ su
su
←7←[r←[999;999H←[[email protected]:/ # chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]:/ # /data/local/tmp/firewater
/data/local/tmp/firewater
[email protected]:/ #
There is no action after this
Click to expand...
Click to collapse
Try flashing an older release of CyanogenMod - I'd try Snapshot M8.
StormyNight said:
Try flashing an older release of CyanogenMod - I'd try Snapshot M8.
Click to expand...
Click to collapse
Hi, I tried but I had the same results, the commands are accepted but there is no action after the last one . I'm gonna do a last attempt on my other computer and see if it works.
I am despeartely in need of your help here guys, I got this brand new HTC one m8 from sprint and am stuck during the process of getting the s-off while following this guide thread to sim unlock the device. I kept getting this same output after following all the steps for rooted m8
Code:
C:\HTC\adt-bundle-windows-x86-20130522\sdk\platform-tools>adb shell
[email protected]_m8whl:/ $ su
su
[email protected]_m8whl:/ # chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]_m8whl:/ # /data/local/tmp/firewater
/data/local/tmp/firewater
/data/local/tmp/firewater
[email protected]_m8whl:/ #
thats all I get after following all the steps.
am so confused and stuck cause am sure without s-off I cant get it to work. and I kept getting this handsfree activation whenever I boot the phone. Please help
cuteomar said:
I am despeartely in need of your help here guys, I got this brand new HTC one m8 from sprint and am stuck during the process of getting the s-off while following this guide thread to sim unlock the device. I kept getting this same output after following all the steps for rooted m8
Code:
C:\HTC\adt-bundle-windows-x86-20130522\sdk\platform-tools>adb shell
[email protected]_m8whl:/ $ su
su
[email protected]_m8whl:/ # chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]_m8whl:/ # /data/local/tmp/firewater
/data/local/tmp/firewater
/data/local/tmp/firewater
[email protected]_m8whl:/ #
thats all I get after following all the steps.
am so confused and stuck cause am sure without s-off I cant get it to work. and I kept getting this handsfree activation whenever I boot the phone. Please help
Click to expand...
Click to collapse
Did you do "adb reboot, then adb wait-for-device push firewater /data/local/tmp" before the other commands?
gstanke said:
Did you do "adb reboot, then adb wait-for-device push firewater /data/local/tmp" before the other commands?
Click to expand...
Click to collapse
Also, if you did any updates with your OTA, this will not work!
I used Sunshine, and paid the $25 to have them help me, it was the best 5 mins of my life!
After you get frustrated and try Firewater a few dozen times... head over to theroot.ninja and pay the $25 dollars... TOTALLY WORTH IT!!
cuteomar said:
I am despeartely in need of your help here guys, I got this brand new HTC one m8 from sprint and am stuck during the process of getting the s-off while following this guide thread to sim unlock the device. I kept getting this same output after following all the steps for rooted m8
Code:
C:\HTC\adt-bundle-windows-x86-20130522\sdk\platform-tools>adb shell
[email protected]_m8whl:/ $ su
su
[email protected]_m8whl:/ # chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]_m8whl:/ # /data/local/tmp/firewater
/data/local/tmp/firewater
/data/local/tmp/firewater
[email protected]_m8whl:/ #
thats all I get after following all the steps.
am so confused and stuck cause am sure without s-off I cant get it to work. and I kept getting this handsfree activation whenever I boot the phone. Please help
Click to expand...
Click to collapse
I fought and fought with adb, rooting, and s-off and Im well versed in adb etc. Just do yourself a favor, pay the $25 fee and go with sunshine. Its expensive but will save you so much headache
Success100 said:
I fought and fought with adb, rooting, and s-off and Im well versed in adb etc. Just do yourself a favor, pay the $25 fee and go with sunshine. Its expensive but will save you so much headache
Click to expand...
Click to collapse
I had no problem dropping the 25 bones for the S off. Those guys work hard and I was having a headache trying firewater which wouldn't work for me. It's easy and imo the $25 was worth it.
At&t user here saying "just do it"
You will sleep better after spending $25 and easily gain S-OFF
at the last line :
"adb reboot
adb wait-for-device push firewater /data/local/tmp
adb shell
su
chmod 755 /data/local/tmp/firewater
/data/local/tmp/firewater <.----
it says to me "firewater[2]: syntax error: '(' unexpected" after I press enter
edit : that says my cmd :
Code:
C:\android-sdk\platform-tools>adb reboot
C:\android-sdk\platform-tools>adb wait-for-device push firewater /data/local/tmp
218 KB/s (670 bytes in 0.003s)
C:\android-sdk\platform-tools>adb shell
[email protected]_m8:/ # su
su
[email protected]_m8:/ # chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]_m8:/ # /data/local/tmp/firewater
/data/local/tmp/firewater
/data/local/tmp/firewater[2]: syntax error: '(' unexpected
1|[email protected]_m8:/ #
Htconem8user said:
at the last line :
"adb reboot
adb wait-for-device push firewater /data/local/tmp
adb shell
su
chmod 755 /data/local/tmp/firewater
/data/local/tmp/firewater <.----
it says to me "firewater[2]: syntax error: '(' unexpected" after I press enter
edit : that says my cmd :
Code:
C:\android-sdk\platform-tools>adb reboot
C:\android-sdk\platform-tools>adb wait-for-device push firewater /data/local/tmp
218 KB/s (670 bytes in 0.003s)
C:\android-sdk\platform-tools>adb shell
[email protected]_m8:/ # su
su
[email protected]_m8:/ # chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]_m8:/ # /data/local/tmp/firewater
/data/local/tmp/firewater
/data/local/tmp/firewater[2]: syntax error: '(' unexpected
1|[email protected]_m8:/ #
Click to expand...
Click to collapse
Firewater is dead ... they abandoned it last week sometime
clsA said:
Firewater is dead ... they abandoned it last week sometime
Click to expand...
Click to collapse
oh :/
I've read that somewhere else too.
But I thought it should be still working.
is there any other method then sunshine ? Because currently I can't buy it now.
And I don't want to wait...
Why should there be only one option ( sunshine) to take s off ?
Is it that hard to code a working programm ?
Htconem8user said:
is there any other method then sunshine ?
Click to expand...
Click to collapse
unfortunately,no (unless you have an old hboot version)
Why should there be only one option ( sunshine) to take s off ?
Is it that hard to code a working programm ?
Click to expand...
Click to collapse
No disrespect mate but it looks like you underestimate the amount of work, time and knowledge needed to:
find a security hole and how to exploit it so you can grant s-off
do it again everytime HTC updates their firmware to patch these security holes
code everything so the average user can achieve s-off using an automated program
maintain everything (program, servers, website)
This have nothing to do with C# programming you can learn at high school to make your own calculator
So to answer your question, Yes its probably hard to do
alray said:
find a security hole and how to exploit it so you can grant s-off
do it again everytime HTC updates their firmware to patch these security holes
code everything so the average user can achieve s-off using an automated program
maintain everything (program, servers, website)
Click to expand...
Click to collapse
okay I got it. thanks for the reply^^
My Hboot is 3.19.0.0000 <- is it old ?