Database Develop

[Q] ADB remount: operation not permitted

Hey Samsung Galaxy tab users and devs.
So im' having a bit of a problem here trying to remount my galaxy tab so i can read/write to it. My cache size is the famous and well hated 25 MB file size limit so i wanted to change it by using this method:
http://forum.xda-developers.com/showpost.php?p=18840882&postcount=227
Im currently running gingerbread 2.3 with root priviliges, and Clockworkmod 3.0.5
{
"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"
}
[/URL] [/IMG]
Whenever i've try to use the remount command it get this error:
http://imageshack.us/photo/my-images/600/androidadb.jpg/
So what am im doing wrong? running WIn 7 64 bit and my tablet is set to usb debugging mode.
Been searching Google and XDA the couple of days but haven't found any solution.
In advance thanks, jakk212

Jakk212 said:
Hey Samsung Galaxy tab users and devs.
So im' having a bit of a problem here trying to remount my galaxy tab so i can read/write to it. My cache size is the famous and well hated 25 MB file size limit so i wanted to change it by using this method:
http://forum.xda-developers.com/showpost.php?p=18840882&postcount=227
Im currently running gingerbread 2.3 with root priviliges, and Clockworkmod 3.0.5
[/URL] [/IMG]
Whenever i've try to use the remount command it get this error:
http://imageshack.us/photo/my-images/600/androidadb.jpg/
So what am im doing wrong? running WIn 7 64 bit and my tablet is set to usb debugging mode.
Been searching Google and XDA the couple of days but haven't found any solution.
In advance thanks, jakk212
Click to expand...
Click to collapse
Hi Jakk,
I'm not a developer, but, the error seems indicate that adb can't remount as RW the /system, so:
1) adb shell work? (you must see a "#" if you are root)
2) have you installed busybox?
3) the 01newcache script in init.d directory work if you have a rom/kernel that suppor init.d
I use the script and i can confirm that work very fine
Bye
Idk

1) How am i able to see that? Should i see a # at the ADB CMD box? Root checker veryfies that my device is rooted.
2) Yes it's installed using V1.16.2androidminimal - updating now.
3) How can i check if my ROM supports that? My rom is the Stock safe Rom provided when flashing to Overcome.

Using the "adb shell" command in ADB gives me a $

using the adb shell command gives me the $ as i said.
When using the command su it gives me the # you're where talking about.

Jakk212 said:
using the adb shell command gives me the $ as i said.
When using the command su it gives me the # you're where talking about.
Click to expand...
Click to collapse
Though im still not capable of remounting my galaxy tab

Jakk212 said:
using the adb shell command gives me the $ as i said.
When using the command su it gives me the # you're where talking about.
Click to expand...
Click to collapse
Hi Jakk,
Yes, so you have a working superuser thats ok, but if you have stock kernel (i think) there isn't any init.d support so the only way is to try manually.
Another way is installing a custom rom (boca, overcome, etc..) or custom kernel that have init.d support.
Bye
Idk
---------- Post added at 02:01 PM ---------- Previous post was at 01:55 PM ----------
Jakk212 said:
Though im still not capable of remounting my galaxy tab
Click to expand...
Click to collapse
There is some errore message when you try to remount via adb? Try to remount filsystem directly in a root shell, here :
http://forum.xda-developers.com/showthread.php?t=859712
there is, at the end of first post, the instruction to mount r/o the /system
Bye
Idk

Hmm actually not sure that there is a custom kernel installed (i don't suppose since it's a stock firmware, then the kernel should be stock - dosen't allow me to overglock however xD )
I've get this message:
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
30336CA087D400EC device
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb remount
remount failed: Operation not permitted
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
$ su
# adb remount
adb remount
adb: not found
# remount
remount
remount: not found
#
Gonna try with to remount it directly in a root shell as you've said - see if that works.
I'll suppose that this is what im gonna write in adb?
Code:
> adb shell
# mount -o remount,rw -t rfs /dev/block/stl9 /system
# exit

Tried to flash the overcome kernel v3.3.1
Also i've connected the tab while in recovery mode now i get a ~$ when entering adb shell.

Jakk212 said:
Hmm actually not sure that there is a custom kernel installed (i don't suppose since it's a stock firmware, then the kernel should be stock - dosen't allow me to overglock however xD )
I've get this message:
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
30336CA087D400EC device
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb remount
remount failed: Operation not permitted
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
$ su
# adb remount
adb remount
adb: not found
# remount
remount
remount: not found
#
Gonna try with to remount it directly in a root shell as you've said - see if that works.
I'll suppose that this is what im gonna write in adb?
Code:
> adb shell
# mount -o remount,rw -t rfs /dev/block/stl9 /system
# exit
Click to expand...
Click to collapse
Hi Jakk,
1) adb is use only from PC (windows or linux), there isn't any adb command into android OS...
2) My mistake: read this links: http://android-tricks.blogspot.com/2009/01/mount-filesystem-read-write.html and http://forum.xda-developers.com/showthread.php?t=685146; the above command is about rfs (Samsung Robust File System); if you have converted the filesystem into ext4, i'm not sure that above command work....
sorry
Bye
Idk

Im am able to mount using the
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Command you told me about but when i try to push the newcache file
Code:
adb push 01newcache /system/etc/init.d/
it simply says:
adb: Not found
When trying to copy it outside the shell it says:
failed to copy "01newcache" to "system/etc/init.d/": Is a directory.

Jakk212 said:
Im am able to mount using the
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Command you told me about but when i try to push the newcache file
Code:
adb push 01newcache /system/etc/init.d/
it simply says:
adb: Not found
When trying to copy it outside the shell it says:
failed to copy "01newcache" to "system/etc/init.d/": Is a directory.
Click to expand...
Click to collapse
Hi,
if you try the adb into android phone shell, simply don't work because adb is a windows command (adb = android debug bridge).
The good is seems you have the init.d directory, so try this:
go to android phone shell and remount /system
in a windows cmd shell do this:
adb push 01newcache /system/etc/init.d/
return into android phone shell:
adb shell
cd /system/etc/init.d
chmod 777 01newcache
ls -l /system/etc/init.d (to show the contend of init.d)
exit
Bye

So you mean that i'll just simply open a cmd box without refering to adb and then use the adb push 01newcache /system/etc/init.d/ command? How's that gonna work?
If you've got the time could you please assist me over teamwiever or something similair?

Jakk212 said:
So you mean that i'll just simply open a cmd box without refering to adb and then use the adb push 01newcache /system/etc/init.d/ command? How's that gonna work?
If you've got the time could you please assist me over teamwiever or something similair?
Click to expand...
Click to collapse
Hi Jakk,
Rollback, read this:
http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
The operation is in 2 steps, pc and android terminal: adb is pc side the rest in android terminal.
I'm sorry, i prefer forum support, i've no time at this moment.....
If i'm not clear enough please tell me, i don't know your skill level...
Bye
Idk

pretty skilled, gonna start my IT-technician education after christmas, and i've know a bit bat programming from working with windows server and also a bit html and php.
capable of flashing ROMS, unbricking etc but haven't used ADB before. I've configured adb the exact same way as the tut you've sent me.
However i still just get's error codes like adb not found, remount not found, Is a directory, or are you sure you are rooted?

Jakk212 said:
pretty skilled, gonna start my IT-technician education after christmas, and i've know a bit bat programming from working with windows server and also a bit html and php.
capable of flashing ROMS, unbricking etc but haven't used ADB before. I've configured adb the exact same way as the tut you've sent me.
However i still just get's error codes like adb not found, remount not found, Is a directory, or are you sure you are rooted?
Click to expand...
Click to collapse
Is working ?:
Code:
adb shell
If yes then:
Code:
su
mount -o remount rw /system
then - if you are not able to use "push" - copy the file in your SDcard then, while in adb shell:
Code:
cp /sdcard/yourfile /your-destination/
Seem easy

then which one am i going to choose? The overwrite?
and am i just supposed to write it like this:
cp /mnt/sdcard/01newcache /system/etc/init.d/
Because then i've get a cp can't create /system/etc/init.d/: Is a directory

Jakk212 said:
then which one am i going to choose? The overwrite?
and am i just supposed to write it like this:
cp /mnt/sdcard/01newcache /system/etc/init.d/
Because then i've get a cp can't create /system/etc/init.d/: Is a directory
Click to expand...
Click to collapse
Try this:
cp /mnt/sdcard/01newcache /system/etc/init.d/01newcache
Bye

If you have the init.d folder then just manul copy "01newcache" to your sd card and from your tab, with a root explorer (i use esfile explorer with root option enabled from option menu) copy it to system/etc/init.d.

...to solve the original problem...
I fixed this on my device from a windows command prompt by typing "adb root" , which restarts the daemon on the device with root permissions.

[Q] [Help needed] Fastboot doesn't provide token ID to unlock the bootloader

Guys, I have a problem with my HTC One M7. I am trying to unlock the bootloader using the HTCDev guide (available at htcdev site).
But suddenly I am not able to complete Step 8 (running command "fastboot oem get_identifier_token").
Command "fastboot devices" shows my phone in a fastboot mode:
\> fastboot devices
mt6589_phone_720pv2 fastboot
But none of fastboot oem commands executes successfully (including "get_identifier_token").
Instead I get only three dots ("...") and nothing changes after that:
\> fastboot oem get_identifier_token
...
Other commands (like fastboot reboot) function, but not "fastboot oem get_identifier_token". I can't unlock my bootloader, could you please help!

andrey o said:
Guys, I have a problem with my HTC One M7. I am trying to unlock the bootloader using the HTCDev guide (available at htcdev site).
But suddenly I am not able to complete Step 8 (running command "fastboot oem get_identifier_token").
Command "fastboot devices" shows my phone in a fastboot mode:
\> fastboot devices
mt6589_phone_720pv2 fastboot
But none of fastboot oem commands executes successfully (including "get_identifier_token").
Instead I get only three dots ("...") and nothing changes after that:
\> fastboot oem get_identifier_token
...
Other commands (like fastboot reboot) function, but not "fastboot oem get_identifier_token". I can't unlock my bootloader, could you please help!
Click to expand...
Click to collapse
Never seen that before but since we have S-off now you can unlock the bootloader without HTCDev
check out the revone thread in the Original Development section.

If you're using Windows 8, I would use the following link that I've seen floating around here"
http://plugable.com/2012/12/01/windows-8-and-intel-usb-3-0-host-controllers
I had issues getting the token for mine until I used that guide to convert my Microsoft USB 3.0 drivers into Intel drivers.

gunnyman said:
Never seen that before but since we have S-off now you can unlock the bootloader without HTCDev
check out the revone thread in the Original Development section.
Click to expand...
Click to collapse
Thanks for this advice, I am now trying to do it with revone.
I have successfully pushed the file to the phone, but when executing adb shell commands I get a error:
"- exec '/system/bin/sh' failed: No such file or directory"
How to fix it?

andrey o said:
Thanks for this advice, I am now trying to do it with revone.
I have successfully pushed the file to the phone, but when executing adb shell commands I get a error:
"- exec '/system/bin/sh' failed: No such file or directory"
How to fix it?
Click to expand...
Click to collapse
Not sure, but the folks in that thread are super helpful
you're in an ADB shell when you execute the command?

gunnyman said:
Not sure, but the folks in that thread are super helpful
you're in an ADB shell when you execute the command?
Click to expand...
Click to collapse
Yes, I am now reading that thread to find the answer.
Here's what i do and what I get:
> adb devices
List of devices attached
0123456789ABCDEF recovery
> adb push revone /data/local/tmp/
4584 KB/s (648208 bytes in 0.138s)
>adb shell cd /data/local/tmp
- exec '/system/bin/sh' failed: No such file or directory (2) nRet(-1) -

Start the shell. Then do the cd command separately

gunnyman said:
Start the shell. Then do the cd command separately
Click to expand...
Click to collapse
same result
> adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) nRet(-1) -

Is the phone in recovery or booted up? Needs to be booted

gunnyman said:
Is the phone in recovery or booted up? Needs to be booted
Click to expand...
Click to collapse
It was in recovery mode - my mistake, thank you for pointing.
I have booted it and executed the needed commands, but still another mistake:
>sudo adb shell
[email protected]:/ # cd /data/local/tmp
[email protected]:/data/local/tmp # chmod 755 revone
[email protected]:/data/local/tmp # ./revone -P
revone v0.2.1
revone failed (error code = 1)
1|[email protected]:/data/local/tmp #
Step by step I am coming closer to the result, thanks so much for your help

[Q] 4.3 reset my phone. never installed

I downloaded and installed the OTA today .I have a stock rooted installation.I clicked install and the phone went to perform the install but instead restarted quickly and reset all my settings back to factory. I checked and still on 4.1..
Help!

I would suggest getting S-OFF before updating

bigdaddy619 said:
I would suggest getting S-OFF before updating
Click to expand...
Click to collapse
Thanks.that would have been super helpful to know before hand lol. Anyway, here is how to resolve this problem for anyone else experiencing it:
http://qbking77.com/development/how-to-gain-s-off-on-the-htc-one-with-revone/
Revone Download:
http://revolutionary.io/revone
Big thanks to the Revolutionary dev team. The original thread can be found here.
Written instructions:
Download the Revone file above and transfer it to your phone (or download on your phone)
Use a root file explorer and paste the file inside the /data/local/tmp folder
Open a terminal emulator and type of the following:
su (enter)
cd /data/local/tmp (enter)
chmod 755 revone (enter) (IF revone doesn’t work, type revone.bin)
./revone -P (enter)
Reboot
Open terminal again and type:
su (enter)
cd /data/local/tmp (enter)
./revone -s 0 -u (That would be a ZERO) (enter)
Reboot
That’s it! To get rid of the tampered, or relock, follow instructions below
To remove “tampered”
open terminal
cd /data/local/tmp
su
./revone.bin -t
These are other commands that you can fill in above to
-u – Unlock the device
-l – Lock the device (as if it was never unlocked)
-r – Relock the device (mark the device as relocked)
-t – Reset the device’s tamper flag.
Click to expand...
Click to collapse

[GUIDE] Obtaining S-OFF on Sprint HTC One HBOOT 1.57

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.

[Q] htc one m8 help at firewater

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 ?