Database Develop

Help devs and add a LOGCAT next to your BUG report

Hi there.... yeah, Im a newb too in this business, but the only one thing that I know, that the DEVS gett pissed off when we report bugs without LOGCATs
We dont understand it but they do SO LETs hear them and do it like we should do it.
Every time when you get into the thread and post something like "aaaaaa, the power button doesent work, or Play Store wont open...", this is just a cup of crapy words for the devs (correct me if Im wrong).
Of course theres a ADB version for doing logs, but I think for the START, this one is just fine.
Click to expand...
Click to collapse
What is logcat?
Logcat is the command to view the internal logs of the Android system. Viewing logs is often the best way to diagnose a problem, and is required for many issues. This way you'll find out what apps are doing in the background without you noticing.
Advantages of Logcat
Debugging
Debug your apps. Find error stacktraces. See what your phone is saying about you behind your back. It's all there in the system log, aka logcat!
Click to expand...
Click to collapse
DOWNLOAD APP
I was googleing around and I found the best app for doing it for us newbs.
Download the FREE app called CATLOG.
Click to expand...
Click to collapse
HOW TO USE IT
After you installed it, RUN it and click the options button, there youll get a record options. Click on the record button and let it run in the background. If you had problems with Play Store, just run the PS again and when the ERROR comes, the CATLOG recorder is recording. After you did that, just go back to the app, hit the options key and press STOP RECORDING. There you GO, you have a .txt catlog of your problem.
This is just a example with the PLAY STORE fc...
Use some file manager or something like that so you can go into your sdcard / catlogs / and there should be your TXT saved log. Now just select it, press on share and put it on the FORUM or the DEVs mail. It depends on each developer. (Correct me again if Im wrong.)
Click to expand...
Click to collapse
Hope it helps out!
DO IT PEOPLE !

Heres is the more advanced but not so hard way to LOGCAT!
All credits goes to paxChristos who made this awesome tutorial HOW TO LOGCAT!
Original post: http://forum.xda-developers.com/showthread.php?t=1726238
paxChristos said:
Here's how to use logcat:
There are two main ways to do a logcat, within android, and through adb.
Logcat within android can be done one of two ways, through a Logcat app:
Here are two good examples are either: aLogcat or Catlog
I prefer catlog, because in my opinion it has a little bit nicer UI. Both of these programs can dump their logs to a txt file, which is very useful for debugging. Or, you can do it in terminal emulator (same rules as running through adb(see below))
From Moscow Desire:
On the other hand, using adb to run logcat, in my opinion is much more useful, because you can start using it when android boots (i.e. once the boot animation appears.)
The code for logcat to output to a file is
Code:
adb logcat > name of problem.txt
you can also do
Code:
adb logcat -f name of problem.txt
how I prefer to do it is this way:
Code:
adb logcat -v long > name of problem.txt
with the -v flag & the long argument, it changes output to long style, which means every line of logcat will be on its own line (makes it a little neater, imo)
Note: When outputting to a file, you will see a newline, but nothing printed, this is normal. To stop logcat from writting to a file, you need to press ctrl+c.
Here's where using logcat (via adb makes life really easy)
Lets say you find a problem you're having after looking at a logcat.
For example:
When I was trying to use a different ramdisk, wifi wouldn't work so I got a logcat that's almost 1300 lines long (a lot of stuff happens in the background)
So if you are searching for an error in the logcat file (it's always e/ for error, f/ for fatal. Those are the two main things that will break a system.)
Code:
D/dalvikvm( 871): GC_CONCURRENT freed 472K, 6% free 10224K/10823K, paused 1ms+6ms
V/AmazonAppstore.DiskInspectorServiceImpl( 871): Available blocks: 21981, Block size: 4096, Free: 90034176, Threshold: 5242880, withinThreshold? true
D/AmazonAppstore.UpdateService( 871): Received action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
W/AmazonAppstore.UpdateService( 871): Confused about why I'm running with this intent action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
D/dalvikvm( 890): GC_CONCURRENT freed 175K, 4% free 9375K/9671K, paused 2ms+3ms
V/AmazonAppstore.ReferenceCounter( 871): Reference (MASLoggerDB) count has gone to 0. Closing referenced object.
E/WifiStateMachine( 203): Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon
V/AmazonAppstore.UpdateService( 871): runUpdateCommand doInBackground started.
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateCommand( 871): Not updating key: digitalLocker from: 1334228488057
V/AmazonAppstore.UpdateService( 871): Finished UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: serviceConfig
V/AmazonAppstore.MASLoggerDB( 871): performLogMetric: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
V/AmazonAppstore.MASLoggerDB( 871): onBackgroundTaskSucceeded: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
W/CommandListener( 118): Failed to retrieve HW addr for eth0 (No such device)
D/CommandListener( 118): Setting iface cfg
D/NetworkManagementService( 203): rsp
D/NetworkManagementService( 203): flags
E/WifiStateMachine( 203): Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to interface setcfg - com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg eth0 0.0.0.0 0 [down]} failed with code 400 : {Failed to set address (No such device)}
W/PackageParser( 203): Unknown element under : supports-screen at /mnt/asec/com.android.aldiko-1/pkg.apk Binary XML file line #16
D/wpa_supplicant( 930): wpa_supplicant v0.8.x
D/wpa_supplicant( 930): random: Trying to read entropy from /dev/random
D/wpa_supplicant( 930): Initializing interface 'eth0' conf '/data/misc/wifi/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
D/wpa_supplicant( 930): Configuration file '/data/misc/wifi/wpa_supplicant.conf' -> '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): Reading configuration file '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): ctrl_interface='eth0'
D/wpa_supplicant( 930): update_config=1
D/wpa_supplicant( 930): Line: 4 - start of a new network block
D/wpa_supplicant( 930): key_mgmt: 0x4
(mind you, that's 29 lines out of 1300ish, just for example)
I then could do the following with logcat:
Code:
adb logcat WifiStateMachine:E *:S -v long > name of problem.txt
and this will only print out any errors associated with WifiStateMachine, and anything which is fatal, which makes it about a million times easier to figure out what's going on!
In WifiStateMachine:E, the :E = to look for Errors, the full list of options is as follows:
V — Verbose (lowest priority)
D — Debug
I — Info (default priority)
W — Warning
E — Error
F — Fatal
S — Silent (highest priority, on which nothing is ever printed)
You can replace the :E with any other letter from above to get more info.
In order to filter out anything other than what you are looking for (in this case, WifiStateMachine) you must put a *:S after your last command (i.e. WifiStateMachine:E ThemeChoose:V ... ... AndroidRuntime:E *:S)
Sources: http://developer.android.com/tools/help/logcat.html
http://developer.android.com/tools/help/adb.html
Update for windows users:
Thank go to FuzzyMeep Two, Here's what he's posted for windows
(If you used his tool, here's his post, thank him for his work!)
Click to expand...
Click to collapse

Adding some LogCats for CM10 nightly
Powerbutton
http://forum.xda-developers.com/showpost.php?p=33593548&postcount=1130
no sound - poor in/out sound on CALLs
http://forum.xda-developers.com/showpost.php?p=33630013&postcount=1395
blinking screen on "screen off"
http://forum.xda-developers.com/showpost.php?p=33629455&postcount=1391
Hope it helps!

Good thread.
My favourite app for logs on the go is Lumberjack.
For logcatting at the PC I think "adb logcat" via cmd / terminal is better than an app (see torq1337's second post).
What's important: A normal logcat can be useless in some cases.
For audio, calls and anything else radio related you should add a radio logcat as well. (adb logcat -b radio).
If you got a bsod, kernel panic, or sth else that results in a bsod or phone restarting than you should post the last_kmsg.
Get it with Lumberjack or manually in the Terminal by typing "su" and "cat /proc/last_kmsg > /sdcard/last_kmsg.txt"

Dont forget to logcat

I updated my previous post now.
I am posting again to push this thread as I personally belive that most people are unable to do so because that some people out there in our nation don't have maps and that I belive that our education people who are flashing custom ROMs should know how to give developers some valid feedback - and you can learn how to logcat in 5 minutes.

tonyp said:
I updated my previous post now.
I am posting again to push this thread as I personally belive that most people are unable to do so because that some people out there in our nation don't have maps and that I belive that our education people who are flashing custom ROMs should know how to give developers some valid feedback - and you can learn how to logcat in 5 minutes.
Click to expand...
Click to collapse
Im gonna cry xDxDxDxD
Sent from my LG-P990 using xda app-developers app

Hi, maybe you would like to include my tool as well, AIOlog, as it not only logs logcat(with the -b radio for radio issues as well), but dmesg, kmsg and last_kmsg as well

tonyp said:
If you got a bsod, kernel panic, or sth else that results in a bsod or phone restarting than you should post the last_kmsg.
Get it with Lumberjack or manually in the Terminal by typing "su" and "cat /proc/last_kmsg > /sdcard/last_kmsg.txt"
Click to expand...
Click to collapse
What /proc/last_kmsg? (It doesn't appear to exist, on my phone at least.)

withoutwings said:
What /proc/last_kmsg? (It doesn't appear to exist, on my phone at least.)
Click to expand...
Click to collapse
It would be removed in a restart but still, you can retrieve the /proc/kmsg instead(better than none, I suppose, just more work for the devs )

wcypierre said:
It would be removed in a restart but still, you can retrieve the /proc/kmsg instead(better than none, I suppose, just more work for the devs )
Click to expand...
Click to collapse
No, /proc/kmesg is reset upon a restart. The whole point of last_kmesg is in the case of a crash, it is there upon the next boot so you can find out what happened. But on CM10 it doesn't appear to exist. I read somewhere this could mean the RAM Console isn't set up properly?

[Q] Cannot get root on Xperia Z1

I've been trying this for most of the day, having read everything here about doing it, and even watching the video.
Unfortunately, I let the phone update to 14.1.G.2.257, but I found the instructions on how to flash back to the previous 1.534. The flashing worked perfectly.
I am trying to use Root_with_Restore_by_Bin4ry_v32 having read how to and watched the tutorial. USB debugging is enabled, as is Unknown Sources, and the 'adb devices' command in the stuff folder of the aforementioned program lists the phone.
However, it does not seem to work. I get the following output:
Code:
C:\xpe>runme
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (20.11.2013) v32 =
======================================================================
Device type:
0) Xperia Z1 14.1.G.1.534 Root by cubeundcube
1) New Standard-Root (thx Ariel Berkman)
2) New Xperia Root by Goroh_kun (Xperia Z, Xperia V [JellyBean] ...)
3) Old
4) Old-Special (for example: Sony Tablet S, Medion Lifetab)
G) Google Glass Mode (thx Saurik for the ab file)
x) Unroot
Make a choice: 0
Please connect your device with enabled USB-Debugging ...
Copy needed files ...
error: protocol fault (no status)
2881 KB/s (2242263 bytes in 0.760s)
error: protocol fault (no status)
error: protocol fault (no status)
133 KB/s (1230 bytes in 0.009s)
error: protocol fault (no status)
Unable to chmod /data/local/tmp/busybox: No such file or directory
Running Exploit
error: protocol fault (no status)
rm failed for /data/local/tmp/getroot, No such file or directory
error: protocol fault (no status)
error: protocol fault (no status)
Rebooting now, after reboot all should be done!
You can close all open command-prompts now!
After reboot all is done! Have fun!
Bin4ry
Press any key to continue . . .
The phone reboots, but there is no SuperUser app. I have re-run the program many times, reflashed the stock firmware again to make sure, and banged my head against my desktop several times to no avail.
Please help...
Rick.

Have you enabled usb debugging
have you allowed unkoown sources
Have you installed drivers
please send a screen shot of your about phone in the settings

gregbradley said:
Have you enabled usb debugging
have you allowed unkoown sources
Have you installed drivers
please send a screen shot of your about phone in the settings
Click to expand...
Click to collapse
Yes thanks, USB debugging and unknown sources are enabled. Is this the screenshot you need to see?
**Edit**
I got it to work!
I just pulled out my laptop which had a clean install of Windows 7 as of a few days ago, installed the above stuff (plus ADB drivers from pdanet) on that, and it worked.
Why it didn't work on my main PC I have no idea, but it is probably an issue with some driver somewhere messing things up. I did try reinstalling all of them, but to no avail.
Anyway, got it now. Thanks!

“Unable to open log device '/dev/log/main': No such file or directory”

Hello guys, i post this cuz i have no way just to ask you,
i have CM11-13012014Nightly and Semaphore KK 3.4.0s
i tried all the ways to enable Log Setting
Code:
Dial this: *#*#2846579#*#*
Service menu will appear.
Go to "ProjectMenu" -> "Background Setting" -> "Log Setting"
Open "Log switch" and set it to ON.
Open "Log level setting" and set the log level you wish.
Reboot the phone.
the number is not work
Code:
Open: /system/etc/init.d/××× （not the same file on different ROMs, find the right file）
Find the line that says: rm /dev/log/main
Change the line to: # rm /dev/log/main (comments out the line, rm = remove, in case you were wondering)
Save and reboot
not work- i found nothing
Code:
[IMG]http://i.stack.imgur.com/Ly4M1.jpg[/IMG]
Restart and the logcat should be working
Code:
Open up CMD or Terminal and type:
adb shell
logcat-enable
reboot
this too not work....
what can i do.... any ideas please

some help @pawitp @stratosk !!!?

sycolon said:
some help @pawitp @stratosk !!!?
Click to expand...
Click to collapse
First of all, wrong section.
Secondly, you need to load the logger module, by insmod system/lib/modules/logger.ko.

ts1506 said:
First of all, wrong section.
Secondly, you need to load the logger module, by insmod system/lib/modules/logger.ko.
Click to expand...
Click to collapse
I did it normal and in su mod and it give me
Code:
insmod: init_module 'system/lib/modules/logger.ko' failed (Exec format error)

@pawitp @stratosk @ts1506
I did it in normal and in su mod and it give me error
insmod: init_module 'system/lib/modules/logger.ko' failed (Exec format error)

sycolon said:
@pawitp @stratosk @ts1506
I did it in normal and in su mod and it give me error
insmod: init_module 'system/lib/modules/logger.ko' failed (Exec format error)
Click to expand...
Click to collapse
Logged module have to be loaded during early boot in order to work properly. You have to enable it in Semaphore manager (logger option) and reboot your phone.

sycolon said:
I did it normal and in su mod and it give me
Code:
insmod: init_module 'system/lib/modules/logger.ko' failed (Exec format error)
Click to expand...
Click to collapse
stratosk said:
Logged module have to be loaded during early boot in order to work properly. You have to enable it in Semaphore manager (logger option) and reboot your phone.
Click to expand...
Click to collapse
I have tried to make it but still not work and Semaphore manager gives that it's enabled but its not !!! :crying:

Thanks for all type of help
i found big problem with CM11 nightly 17012014 and semaphore kk and system was so slow and have troubles with apps and gapps
i flashed Makay kernel and all work little bit better even the logcat too
Thanks for all your work guy i wish you keep updated with your work and the semaphore kernel

Back to the htc one stock rom

Is the only way to go stock rom by changing mainboard?? htc malaysia sent "only way is changing the mainboard. Mainboard is too expensive for me. Is any idea to back stockrom??

Check this http://forum.xda-developers.com/showthread.php?p=51151301
Sent from my HTC One

Help this company said:
Is the only way to go stock rom by changing mainboard?? htc malaysia sent "only way is changing the mainboard. Mainboard is too expensive for me. Is any idea to back stockrom??
Click to expand...
Click to collapse
This is now your 4 thread for the same problem. Please quit making new threads and follow the advice folks have already given you for your issue.

Thread 1
Thread 2 <----------------- there were people who helped you here but you have not answered and you left
Thread 3 <----------------- there were people who helped you here but you have not answered and you left
I guess it will be the same thing here...

Back to stock.
Hi. I am Superpulla and i like go to stock from Maximus HD rom. i have 4.19.401.8 Version. I don't know witch ruu.zip i must download. all of them are meant to be on JB??!. If someone could help me with this, i be so thankfull.
I allready get my cid back to stock: HTC__Y13
HTC One m7_ul kitkat 4.4.2 Sense 5.5
Main guestions are: 1. What i do now?
2. Witch Ruu.zip i can flash

Superpulla said:
Hi. I am Superpulla and i like go to stock from Maximus HD rom. i have 4.19.401.8 Version. I don't know witch ruu.zip i must download. all of them are meant to be on JB??!. If someone could help me with this, i be so thankfull.
I allready get my cid back to stock: HTC__Y13
HTC One m7_ul kitkat 4.4.2 Sense 5.5
Main guestions are: 1. What i do now?
2. Witch Ruu.zip i can flash
Click to expand...
Click to collapse
U should repost in your own thread, it's easier to track.
Also post output from fastboot getvar all

A
alray said:
Thread 1
Thread 2 <----------------- there were people who helped you here but you have not answered and you left
Thread 3 <----------------- there were people who helped you here but you have not answered and you left
I guess it will be the same thing here...
Click to expand...
Click to collapse
I need Thread 1,2,3. Each thread different..

Help this company said:
I need Thread 1,2,3. Each thread different..
Click to expand...
Click to collapse
Why? Is it a different device?

Help this company said:
I need Thread 1,2,3. Each thread different..
Click to expand...
Click to collapse
Hmmmm no
To summarize:
Thread #2 (initial thread) -----> phone soft bricked, explained you how to install adb/fastboot/drivers to post a ''getvar all'', determined that you can not use your stock rom atm because of this. So I have suggested you to try this. You did not answered.
Thread #1 ------> phone soft bricked, you are asking again to flash your stock rom (adb sideload) even after reading this. no body answered in this thread.
Thread #3 --------> phone soft bricked, you are asking direction how to use adb sideload.
Thread #4 (here) ----> phone soft bricked you are asking how to return stock again.
Your issue is: Phone soft bricked. You don't have to create a new thread for each problem you encounter with un-bricking your phone. You could simply update the information in your initial thread so its easier for people to help and for YOU to understand. Now read back those threads and ask questions about what you don't understand (not in a new thread) and I'll (we) be pleased to help you.
---------- Post added at 07:23 PM ---------- Previous post was at 07:08 PM ----------
Help this company said:
Is the only way to go stock rom by changing mainboard?? htc malaysia sent "only way is changing the mainboard. Mainboard is too expensive for me. Is any idea to back stockrom??
Click to expand...
Click to collapse
So again, you can return to stock using a ''guru reset rom''. This is a stock rom that when installed will reset your phone back to stock (stock rom, stock recovery, stock radio). The rom is pushed to your sd card via TWRP or sideloaded via TWRP. The problem is the guru reset rom version you need have a bad file that will prevent you to get ota updates (discussed here)
this Reset ROM is supposed to install 3.63.707.4 software on the phone but it installs 3.63.707.3 instead , the software information under settings shows 3.63.707.3 while OS in "fastboot getvar all" shows 3.63.707.4. i went ahead and tried to OTA update it with this ROM but it gave variant error because of fw and sw number not matching
Click to expand...
Click to collapse
. So you will not be 100% stock because of this but at least your phone will boot.
Option 2 is to flash a custom rom like ARHD. It really looks and feels like the stock rom. This is a rock stable rom, always up to date. Again you'll need to push or sideload the rom
Option 3 is to go back to stock using a RUU. Unfortunately the only RUU for you phone version is DECRYPTED which means it required S-OFF to be flashed. So to use this RUU you'll need to S-OFF your phone which require to flash ARHD rom before.
Hope its clear, ask any questions if not, or choose which option you prefer and we will assist you but please for the love of god, no more threads :victory:

a
alray said:
Hmmmm no
To summarize:
Thread #2 (initial thread) -----> phone soft bricked, explained you how to install adb/fastboot/drivers to post a ''getvar all'', determined that you can not use your stock rom atm because of this. So I have suggested you to try this. You did not answered.
Thread #1 ------> phone soft bricked, you are asking again to flash your stock rom (adb sideload) even after reading this. no body answered in this thread.
Thread #3 --------> phone soft bricked, you are asking direction how to use adb sideload.
Thread #4 (here) ----> phone soft bricked you are asking how to return stock again.
Your issue is: Phone soft bricked. You don't have to create a new thread for each problem you encounter with un-bricking your phone. You could simply update the information in your initial thread so its easier for people to help and for YOU to understand. Now read back those threads and ask questions about what you don't understand (not in a new thread) and I'll (we) be pleased to help you.
---------- Post added at 07:23 PM ---------- Previous post was at 07:08 PM ----------
So again, you can return to stock using a ''guru reset rom''. This is a stock rom that when installed will reset your phone back to stock (stock rom, stock recovery, stock radio). The rom is pushed to your sd card via TWRP or sideloaded via TWRP. The problem is the guru reset rom version you need have a bad file that will prevent you to get ota updates (discussed here)
. So you will not be 100% stock because of this but at least your phone will boot.
Option 2 is to flash a custom rom like ARHD. It really looks and feels like the stock rom. This is a rock stable rom, always up to date. Again you'll need to push or sideload the rom
Option 3 is to go back to stock using a RUU. Unfortunately the only RUU for you phone version is DECRYPTED which means it required S-OFF to be flashed. So to use this RUU you'll need to S-OFF your phone which require to flash ARHD rom before.
Hope its clear, ask any questions if not, or choose which option you prefer and we will assist you but please for the love of god, no more threads :victory:
Click to expand...
Click to collapse
thank you. I want to go back perfect stock rom. So I have to s-off... But how to s-off??
And I don't want to use any custom rom.
Last, I have a question, Do I not to send htc malaysia center to change mainboard??
Now, I'll not use any fixing ways but i will use only ur ways. I believe you!!
*Information.
my hboot is 1.56. radio ; 4A.23.3263.28 OS; 4.20.707.6 S-ON TAMPERED UNLOCKED.

Help this company said:
thank you. I want to go back perfect stock rom. So I have to s-off... But how to s-off??
And I don't want to use any custom rom.
Click to expand...
Click to collapse
Help this company said:
my hboot is 1.56.
Click to expand...
Click to collapse
You can s-off your phone using rumrunner tool or firewater tool. However many users reported not being able to s-off on hboot 1.56. You'll have to try it. You'll need to use a custom even if you don't want. A working rom is needed to achieve s-off. If you can't s-off you'll have no choice using a custom rom or the guru reset rom
Help this company said:
Last, I have a question, Do I not to send htc malaysia center to change mainboard??
Click to expand...
Click to collapse
If you phone still able to boot in bootloader mode, you don't have to send the phone for repair.

A
alray said:
You can s-off your phone using rumrunner tool or firewater tool. However many users reported not being able to s-off on hboot 1.56. You'll have to try it. You'll need to use a custom even if you don't want. A working rom is needed to achieve s-off. If you can't s-off you'll have no choice using a custom rom or the guru reset rom
If you phone still able to boot in bootloader mode, you don't have to send the phone for repair.
Click to expand...
Click to collapse
adb reboot (<--- important!!!!)
adb wait-for-device push firewater /data/local/tmp
adb shell su
chmod 755 /data/local/tmp/firewater /data/local/tmp/firewater
Shoud I input that code at cmd??? For example adb reboot. And Why important "adb reboot"?
And Shoud I add the file "firewater" at existing adb folder??
Last, To use adb command, what I have to prepare? Stay twrp recovery or bootloader or fastboot??
I'm so sorry about my short root knowledge...

Help this company said:
adb reboot (<--- important!!!!)
adb wait-for-device push firewater /data/local/tmp
adb shell su
chmod 755 /data/local/tmp/firewater /data/local/tmp/firewater
Shoud I input that code at cmd??? For example adb reboot. And Why important "adb reboot"?
And Shoud I add the file "firewater" at existing adb folder??
Last, To use adb command, what I have to prepare? Stay twrp recovery or bootloader or fastboot??
I'm so sorry about my short root knowledge...
Click to expand...
Click to collapse
Do you have arhd rom installed on your phone?

a
alray said:
Do you have arhd rom installed on your phone
Click to expand...
Click to collapse
No, Could you write download link?? And 1st install arhd 2nd go back to stock rom??
How to s-off by using firewater?? I downloaded file, and just type "adb reboot (<--- important!!!!)*adb wait-for-device push firewater /data/local/tmp*adb shell su*chmod 755 /data/local/tmp/firewater /data/local/tmp/firewater" ????

Help this company said:
No, Could you write download link??
Click to expand...
Click to collapse
Easy to find on the forum. ARHD is the second thread listed under the ''ROMs'' tab or a simple search on google using ''ARHD'' and ''HTC ONE'' key words will brings you at the right place.
Help this company said:
And 1st install arhd 2nd go back to stock rom??
Click to expand...
Click to collapse
flash arhd first then if you can achieve s-off you'll be able to run the ruu to go back to stock. If you can't s-off then use arhd rom.
Help this company said:
How to s-off by using firewater?? I downloaded file, and just type "adb reboot''
Click to expand...
Click to collapse
Hmmmm, so your phone is softbricked which mean it can't boot. How can you reboot a phone that is not booted?! You need a working rom before. Then follow the guide I have posted above to s-off.
Honestly, making your phone boot should be your absolute priority. You are at step #1 -----> making your phone boot by flashing a rom. S-off is like step #10.

alray said:
Easy to find on the forum. ARHD is the second thread listed under the ''ROMs'' tab or a simple search on google using ''ARHD'' and ''HTC ONE'' key words will brings you at the right place.
flash arhd first then if you can achieve s-off you'll be able to run the ruu to go back to stock. If you can't s-off then use arhd rom.
Hmmmm, so your phone is softbricked which mean it can't boot. How can you reboot a phone that is not booted?! You need a working rom before. Then follow the guide I have posted above to s-off.
Honestly, making your phone boot should be your absolute priority. You are at step #1 -----> making your phone boot by flashing a rom. S-off is like step #10.
Click to expand...
Click to collapse
1. Should I check the radio,etc of ARHD ROM??
2. If I downloaded Arhd, Should I use "adb sideload arhdname.zip"??
3. I entered adb sideload and Swipe it, it shows me "Failed". What's the problem???
Thank U Mr.alray helping me. I'll do that at night(korea time).
Sincerely, I appreciate ur help.

Help this company said:
1. Should I check the radio,etc of ARHD ROM??
2. If I downloaded Arhd, Should I use "adb sideload arhdname.zip"??
3. I entered adb sideload and Swipe it, it shows me "Failed". What's the problem???
Thank U Mr.alray helping me. I'll do that at night(korea time).
Sincerely, I appreciate ur help.
Click to expand...
Click to collapse
1. just flash the rom
2. adb sideload it or adb push it.
3. Maybe a driver issue. When in twrp sideload mode, open a command prompt from your adb/fastboot folder and type ''adb devices''. What is the output?

a
alray said:
1. just flash the rom
2. adb sideload it or adb push it.
3. Maybe a driver issue. When in twrp sideload mode, open a command prompt from your adb/fastboot folder and type ''adb devices''. What is the output?
Click to expand...
Click to collapse
when I typed adb devices,it shows "my serial name sideload". and I did adb sideload arhd.zip. it shows 100% but I can't find the file.
also, I did adb push,this shows me this.↓
-a - directs adb to listen on all interfaces for a c
onnection
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <specific device> - directs command to the device or emulator with
the given
serial number or qualifier. Overrides ANDROID_S
ERIAL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
-H - Name of adb server host (default: localhost)
-P - Port of adb server (default: 5037)
devices [-l] - list all connected devices
('-l' will also list device qualifiers)
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devic
es.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward --list - list all forward socket connections.
the format is a list of lines with the followin
g format:
<serial> " " <local> " " <remote> "\n"
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb forward --no-rebind <local> <remote>
- same as 'adb forward <local> <remote>' but fail
s
if <local> is already forwarded
adb forward --remove <local> - remove a specific forward socket connection
adb forward --remove-all - remove all forward socket connections
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] [--algo <algorithm name> --key <hex-encoded key> --
iv <hex-encoded iv>] <file>
- push this package file to the device and instal
l it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
('--algo', '--key', and '--iv' mean the file is
encrypted already)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb backup [-f <file>] [-apk|-noapk] [-obb|-noobb] [-shared|-noshared] [-all]
[-system|-nosystem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is wr
itten
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks
themselves
in the archive; the default is noapk.)
(-obb|-noobb enable/disable backup of any insta
lled apk expansion
(aka .obb) files associated with each applic
ation; the default
is noobb.)
(-shared|-noshared enable/disable backup of the
device's
shared storage / SD card contents; the defau
lt is noshared.)
(-all means to back up all installed applicatio
ns)
(-system|-nosystem toggles whether -all automat
ically includes
system applications; the default is to inclu
de system apps)
(<packages...> is the list of applications to b
e backed up. If
the -all or -shared flags are passed, then t
he package
list is optional. Applications explicitly g
iven on the
command line will be included even if -nosys
tem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup
archive
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb get-devpath - prints: <device-path>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.

Help this company said:
when I typed adb devices,it shows "my serial name sideload". and I did adb sideload arhd.zip. it shows 100% but I can't find the file.
also, I did adb push,this shows me this.↓
Click to expand...
Click to collapse
You need to add the file name you want to push and its destination on the phone! Not only ''adb push''
Code:
adb push <name_of_rom>.zip /sdcard/
then your rom will be on your sdcard folder.
or
adb sideload using this command:
Code:
adb sideload <name_of_rom>.zip
Btw use the sideload command when in twrp sideload mode (''adb devices'' must output your s/n + sideload)
use adb push when in twrp recovery main menu (''adb devices'' must output your s/n + recovery)
---------- Post added at 07:06 PM ---------- Previous post was at 07:05 PM ----------
and the long text you posted is the help page. Every time you see that page means you did not typed a valid command.
-a - directs adb to listen on all interfaces for a c
onnection
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <specific device> - directs command to the device or emulator with
the given
serial number or qualifier. Overrides ANDROID_S
ERIAL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
etc etc etc.....
Click to expand...
Click to collapse

a
alray said:
You need to add the file name you want to push and its destination on the phone! Not only ''adb push''
Code:
adb push <name_of_rom>.zip /sdcard/
then your rom will be on your sdcard folder.
or
adb sideload using this command:
Code:
adb sideload <name_of_rom>.zip
Btw use the sideload command when in twrp sideload mode (''adb devices'' must output your s/n + sideload)
use adb push when in twrp recovery main menu (''adb devices'' must output your s/n + recovery)
---------- Post added at 07:06 PM ---------- Previous post was at 07:05 PM ----------
and the long text you posted is the help page. Every time you see that page means you did not typed a valid command.
Click to expand...
Click to collapse
WOW, Finally, I did !!!!!!! I hadn't supersu in my device. I was deleted it. I installed supersu by adb sideload today,It works well.!!!!!!!!
Thank U !!!! thank u very much(x100).!!!!!!!!!!!! U save my money and life.!!!!
Now, Should I s-off to go back to stock rom???
And If I clicked the Thanks, Can't I ask this inquiry???
Anyway Thanks Mr.alray. Ur perfert Guy!!!!!!:good:

Question: How to add route with busybox (for specified destination and gateway)?

THIS IS THE SOLUTION:
Code:
/dev/busybox/route add -net 1.0.1.0 netmask 255.255.255.0 gw $(getprop net.dns1)
-----THE ORIGINAL POST BELOW-----
Is it just me or the busybox doesn't work well?
Here is my code:
alias netstat='/system/xbin/busybox netstat'
alias grep='/system/xbin/busybox grep'
alias awk='/system/xbin/busybox awk'
alias route='/system/xbin/busybox route'
gateway=`netstat -rn | grep ^0\.0\.0\.0 | awk '{print $2}'`
route add -net 1.0.1.0 netmask 255.255.255.0 gw $gateway
Click to expand...
Click to collapse
Apparently busybox doesn't recognize `route add -net 1.0.1.0 netmask 255.255.255.0 gw $gateway`...
Update: I tried to update to magisk 12.0, and now it just shows applet not found instead...
BTW, what's SafetyNet?
Deic said:
You are using a built-in Busybox binary with your ROM not the Magisk's Busybox probably.
Try
Code:
/data/magisk/busybox route
or
Code:
/dev/busybox/route
and:
https://www.howtogeek.com/241012/sa...y-and-other-apps-dont-work-on-rooted-devices/
Click to expand...
Click to collapse
So I did try
Code:
/data/magisk/busybox route
This gives me applet not found again. Then I tried
Code:
/dev/busybox/route
It prints '/dev/busybox/route not found'. I checked and the file '/dev/busybox/route' exists (as a shortcut), so I am not sure what is going on anymore. BTW, I did run su before I tried to run these commands.
Also this is very funny, if I run these commands line by line, I will get different error message than "not found" when I put them in a .sh file and run
Code:
sh script.sh
under root folder.
Solution provided on top.

You are using a built-in Busybox binary with your ROM not the Magisk's Busybox probably.
Try
Code:
/data/magisk/busybox route
or
Code:
/dev/busybox/route
and:
https://www.howtogeek.com/241012/sa...y-and-other-apps-dont-work-on-rooted-devices/

Deic said:
You are using a built-in Busybox binary with your ROM not the Magisk's Busybox probably.
Try
Code:
/data/magisk/busybox route
or
Code:
/dev/busybox/route
and:
https://www.howtogeek.com/241012/sa...y-and-other-apps-dont-work-on-rooted-devices/
Click to expand...
Click to collapse
So I did try
Code:
/data/magisk/busybox route
This gives me applet not found again. Then I tried
Code:
/dev/busybox/route
It prints '/dev/busybox/route not found'. I checked and the file '/dev/busybox/route' exists (as a shortcut), so I am not sure what is going on anymore. BTW, I did run su before I tried to run these commands.

aeroxy said:
So I did try
Code:
/data/magisk/busybox route
This gives me applet not found again. Then I tried
Code:
/dev/busybox/route
It prints '/dev/busybox/route not found'. I checked and the file '/dev/busybox/route' exists (as a shortcut), so I am not sure what is going on anymore. BTW, I did run su before I tried to run these commands.
Click to expand...
Click to collapse
Have you got installed Magisk v12? Would be usefull know what is your device, Android version, etc.. And other relevant info, log, etc...

Deic said:
Have you got installed Magisk v12? Would be usefull know what is your device, Android version, etc.. And other relevant info, log, etc...
Click to expand...
Click to collapse
Yes, I think I mentioned it in the update.
I have two devices, Samsung S6 and Samsung S7, both reported identical error message. Can anyone try to run the same command and see if they get the same result? :fingers-crossed:
Nevermind, I figured it out, check the OP for updated solution.

Deic said:
Have you got installed Magisk v12? Would be usefull know what is your device, Android version, etc.. And other relevant info, log, etc...
Click to expand...
Click to collapse
I figured it. The code had problem. Check out the OP for the solution.