Related
I need to get qpst v2.7 build 323. Where can I find it?
kench33 said:
I need to get qpst v2.7 build 323. Where can I find it?
Click to expand...
Click to collapse
Google works really well.. Just saying
http://www.x-drivers.com/catalog/flash/mobile_phones/companies/qualcomm/models/qpst/12051.html
Thanks. I was on a different site and it kept giving me bad links. To back up imei do you guys save it to the phone or your computer?
I saved it to my computer, beings you need your computer to restore if needed.
jaben2 said:
I saved it to my computer, beings you need your computer to restore if needed.
Click to expand...
Click to collapse
Couldn't you use a terminal on the phone? Its just a adb dd command. I keep it in both places
piiman said:
Couldn't you use a terminal on the phone? Its just a adb dd command. I keep it in both places
Click to expand...
Click to collapse
The adb way you posted I believe was the old way. I did that previously as well. Then they said the best way to do it was through the qpst program.
I maybe wrong I just know that when they were looking for the files to troubleshoot, they needed the qpst version not the adb version.
I do have both versions though.
Now if only I could communicate with the phone from the PC. Finally got to the hidden menu, but then I lose the com port connection.
jaben2 said:
Google works really well.. Just saying
http://www.x-drivers.com/catalog/flash/mobile_phones/companies/qualcomm/models/qpst/12051.html
Click to expand...
Click to collapse
funny i got to this thread by searching on google, "qpst download" this was the second link google gave.
dcmargush said:
Now if only I could communicate with the phone from the PC. Finally got to the hidden menu, but then I lose the com port connection.
Click to expand...
Click to collapse
Try this guide here and see if you stay connected : http://droidmodderx.com/galaxys3/?page_id=79
---------- Post added at 07:08 AM ---------- Previous post was at 06:18 AM ----------
kench33 said:
Thanks. I was on a different site and it kept giving me bad links. To back up imei do you guys save it to the phone or your computer?
Click to expand...
Click to collapse
I have mine saved on my sd card and computer. It's also not a bad idea to sign up for a dropbox and/or copy account and keep them there as anything can happen to your computer. Maybe I've gone off the deep end but some online storage is good too.
kench33 said:
I need to get qpst v2.7 build 323. Where can I find it?
Click to expand...
Click to collapse
Here is Build 422 I need higher. Anyone know where to find the higher builds? There are 2 that I know of.
rekamyenom said:
Here is Build 422 I need higher. Anyone know where to find the higher builds? There are 2 that I know of.
Click to expand...
Click to collapse
im having my GN2 and my HTC ONE connect to Qpst so i tried to download the build 422 you posted but its asking for a password ??? PLEASE ADVISE thanks!
sdwyz74 said:
im having my GN2 and my HTC ONE connect to Qpst so i tried to download the build 422 you posted but its asking for a password ??? PLEASE ADVISE thanks!
Click to expand...
Click to collapse
The Password is right there on the Devhost Download page, but here it is
PASSWORD IS: screwasurion
Hello, fellow QPST users.
QPST 2.7 Build 4.2.2 is a fake version with keylogger.
Some a$$hole downloaded latest public QPST build (4.0.2) and decompiled MSI installer package, then edited all "4.0.2" to "4.2.2", added "fake changelog", added keylogger (qualcomm.exe), then repackaged and spread around web!
Everyone who downloaded QPST build "4.2.2" should change all his passwords.
More info about malware from fake 4.2.2 build (QPST.2.7.422.msi)
MSI package (QPST.2.7.422.msi) was embedded/tampered with qualcomm.exe which is a .NET based malware that logs your keystrokes and sends it to attacker's server.
How to delete the actual malware from your system?
Look at the startup from msconfig or CCleaner, there should be a file called qualcomm.exe thats set to start everytime system starts. Delete both registry and file.
If you wanted to see what data thief was stolen from you. Just open the .dc file (in "dclogs" folder) with Notepad and see for yourself.
In XP, dc file is located here!
C:\Documents and Settings\Administrator\Application Data\dclogs
there should be a file called "201X-XX-XX-X.dc
if you open that DC files with Notepad, you'll see all your keystrokes.
Here is mine. I've intentionally entered paypal site with fake info.
:: Run (3:01:51 AM)
Script kiddie. NET Based malware, huh?[ESC]
:: Program Manager (3:02:14 AM)
e
:: Firefox (3:02:18 AM)
www.paypal.com
[email protected][TAB]
mypaypalpass
[ENTER]
:: Documents and Settings (3:02:19 AM)
[UP]
:: Administrator (3:02:28 AM)
[DOWN][DOWN][DOWN][DOWN][DOWN][DOWN][DOWN][DOWN][DOWN][DOWN]
[DOWN][DOWN][DOWN][DOWN][DOWN][DOWN][DOWN][DOWN][DOWN][DOWN][DOWN][DOWN][DOWN]
d
:: (3:02:34 AM)
:: Administrator (3:02:34 AM)
d
:: (3:03:11 AM)
mmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm
:: [Release] QPST 2.7 BUILD 422 - Download Here - Enjoy - Mozilla Firefox (3:03:57 AM)
crap
How to delete?d
:: Clipboard Change : size = 16 Bytes (3:03:57 AM)
QPST.2.7.422.msi
:: (3:04:23 AM)
cccccc
Click to expand...
Click to collapse
Keylogger sends the logs from keylogger to "qpst.hopto.me"
So please report about this incident where and when you encounter QPST 4.2.2 somewhere (forums, posts, sharing-sites, etc)
Copy my whole post and paste it where you see 4.2.2 mentioned.
Bonus: Fake Changelog
If you've installed this 422 build, then open the Readme.txt in C:\Program Files\Qualcomm\QPST\Documents
Scroll down and see the "6/12/13 QPST 2.7.422 changelog"
6/12/13 QPST 2.7.422
1) EFS Hello commands will not be sent unless the device is in a compatible mode. Sending this command when the
device is in download mode can cause a "server busy" message for a few seconds because of command retries.
2) Support for the Sahara device protocol (see 80-N1008-1 or equivalent) is now built in to the QPST server process.
This protocol is only supported by USB Serial ports, not TCP/IP connections. In QPST Configuration a device in
this mode will display as "Q/QCP-XXX (Sahara Download)". This mode can only be detected (1) when the QPST server
process starts or a COM port in this mode added to QPST, or (2) when a device enters Sahara mode on a port assigned
to QPST. This is because the device only sends its Hello message once, as soon as the COM port is opened.
Click to expand...
Click to collapse
Changelog above is actually cloned from QPST 2.7.394 Just scroll down and see Build 2.7.394 changelog. Its same!
So forget about Build 422. It doesn't exist.
Use QPST 2.7 Build 402. It's the latest public build
Sorry about my english
Best Regards
AnycallMongolia
Thanks!
anycallmongolia said:
Hello, fellow QPST users.
QPST 2.7 Build 4.2.2 is a fake version with keylogger.
Some a$$hole downloaded latest public QPST build (4.0.2) and decompiled MSI installer package, then edited all "4.0.2" to "4.2.2", added "fake changelog", added keylogger (qualcomm.exe), then repackaged and spread around web!
Everyone who downloaded QPST build "4.2.2" should change all his passwords.
More info about malware from fake 4.2.2 build (QPST.2.7.422.msi)
MSI package (QPST.2.7.422.msi) was embedded/tampered with qualcomm.exe which is a .NET based malware that logs your keystrokes and sends it to attacker's server.
How to delete the actual malware from your system?
Look at the startup from msconfig or CCleaner, there should be a file called qualcomm.exe thats set to start everytime system starts. Delete both registry and file.
If you wanted to see what data thief was stolen from you. Just open the .dc file (in "dclogs" folder) with Notepad and see for yourself.
In XP, dc file is located here!
C:\Documents and Settings\Administrator\Application Data\dclogs
there should be a file called "201X-XX-XX-X.dc
if you open that DC files with Notepad, you'll see all your keystrokes.
Here is mine. I've intentionally entered paypal site with fake info.
Keylogger sends the logs from keylogger to "qpst.hopto.me"
So please report about this incident where and when you encounter QPST 4.2.2 somewhere (forums, posts, sharing-sites, etc)
Copy my whole post and paste it where you see 4.2.2 mentioned.
Bonus: Fake Changelog
If you've installed this 422 build, then open the Readme.txt in C:\Program Files\Qualcomm\QPST\Documents
Scroll down and see the "6/12/13 QPST 2.7.422 changelog"
Changelog above is actually cloned from QPST 2.7.394 Just scroll down and see Build 2.7.394 changelog. Its same!
So forget about Build 422. It doesn't exist.
Use QPST 2.7 Build 402. It's the latest public build
Sorry about my english
Best Regards
AnycallMongolia
Click to expand...
Click to collapse
I have Build 411, haven't installed and tried it yet.
Is there anything you know about this one?
WackyJoe said:
I have Build 411, haven't installed and tried it yet.
Is there anything you know about this one?
Click to expand...
Click to collapse
Yeah, it seems someone recently leaked build 411.
I've checked it and it seems legit!
anycallmongolia said:
Yeah, it seems someone recently leaked build 411.
I've checked it and it seems legit!
Click to expand...
Click to collapse
How do i unistall this **** is not letting me
did you manage to uninstall it???
---------- Post added at 05:32 PM ---------- Previous post was at 05:31 PM ----------
mocoyombiflash said:
How do i unistall this **** is not letting me
Click to expand...
Click to collapse
Did you manage to uninstall it???
Any new version available?
For those reaching this thread looking for Qualcomm Product Support Tool (QPST). Please also take note that there is also the same discussion in thread:
[QPST 2.7 build 402]
https://forum.xda-developers.com/showthread.php?t=2263391
Because a problem with an app and supersu right after entering the Sim pin, I'd need to post a logcat dump, but honestly I never did it.
How can I do that?
Does logcat contains private information like imei, tel numbers contact and so on?
zooster said:
Because a problem with an app and supersu right after entering the Sim pin, I'd need to post a logcat dump, but honestly I never did it.
How can I do that?
Does logcat contains private information like imei, tel numbers contact and so on?
Click to expand...
Click to collapse
Logcat doesnt give any private information away and it is done via the adb command:
adb logcat > log.txt
This will save the logcat to log.txt file. Or there is a tool in the Sensation Themes and Apps section that gets logcats easyily - search for it
zooster said:
Because a problem with an app and supersu right after entering the Sim pin, I'd need to post a logcat dump, but honestly I never did it.
How can I do that?
Does logcat contains private information like imei, tel numbers contact and so on?
Click to expand...
Click to collapse
i found it for you man http://forum.xda-developers.com/showthread.php?t=1838323
But it's always needed a computer... Isn't there a way to save it directly on the phone?
zooster said:
But it's always needed a computer... Isn't there a way to save it directly on the phone?
Click to expand...
Click to collapse
Download alogcat from Play Store
zooster said:
But it's always needed a computer... Isn't there a way to save it directly on the phone?
Click to expand...
Click to collapse
You could run "logcat > log.txt" (ignoring the quotes) from a terminal on the phone.
Make sure you go to a sensible directory first so you know where it's been saved. I'd suggest "cd /sdcard".
Script removed/Effort "canceled" (see release notes)!
Dear fellow XDA'ers, i have written a quick and simple script to tie in all of the great work done by jcase and beaups that helps you root your Moto X. This script simply follows the instructions written by jcase and beaups and automates those scripts with a simple menu.
This script should technically work for "any" Moto X on "any" carrier, provided the methods contained within have the same success rate across all carriers. I do not have the capacity, nor experience, to trap for all situations.
This script ASSUMES that you already have the Motorola drivers installed and your device has successfully connected to your computer via USB Debugging Mode. If you need the drivers, they can be found here.
Instructions:
Download and extract this script on to your Windows Desktop.
Download ALL of the following to the same folder as the GO!.CMD ("640k's Moto X Root Script" Folder). These files should NOT be unzipped:
your specific 4.2.2 factory image.and/or 4.4 factory images (if you are on 4.4, you will need BOTH images).
jcase's RockMyMoto (4.2.2) and SlapMyMoto (4.4).
beaups' MotoWpNoMo.
Saurik's Cydia Impactor
Execute Go!.CMD and follow the on-screen prompts.
Links:
Moto X Firmware Page
jcase's RockMyMoto Thread
jcase's SlapMyMoto Thread
beaups' MotoWpNoMo Thread
Saurik's Cydia Impactor Page
Disclaimers:
I make no warranties of any kind regarding the accuracy or efficiency of this script or the processes contained within. This script was tested on a single device and was written based off of the instructions provided within these forums. You can perform these steps yourself!
jcase will NOT support the use of this script. Should you run in to issues with any of the functionality/procedures written specifically by jcase, you will not be supported by jcase unless you are following his methods.
beaups will NOT support the use of this script. Should you run in to issues with any of the functionality/procedures written specifically by beaups, you will not be supported by beaups unless you are following his methods.
Because I have compiled other's hard work into a command-line script, i have decided to distribute my script uncompiled. That way, in the event of major changes, significant errors, etc., that I don't have time to address, the user community can lend a hand. If you find my work useful, please Thank Me.
WARNING
Make sure your device is fully charged before beginning!
Some people have reported an inability to flash their device, have received "unknown errors", weird partition errors and general chaos during the flashing/imaging process. If this happens to you, try a different USB port. I have read threads/seen reports where sometimes USB 3.0 ports cause failures during this process. Change to a USB 2.0 port and try again.
[*]In general, it is difficult to completely brick your device using this method. As long as you can get to the fastboot menu, your device is recoverable. If your phone will not power on, you did not follow one of the two warnings above.
TIPS:
If "Waiting for device" seems to be taking a really long time (your device is ready, but the script hasn't picked it up yet), try either turning off USB Debugging and then back on, or try removing the USB cable and re-inserting it.
If you are on 4.4, looking for root, your device will be re-imaged two times with 4.2.2. Don't input your details until the 2nd time, to avoid having to repeat your effort.
Connect to your WiFi before enabling USB Debugging Mode to avoid IP Address errors. The batch script tends to get funny on some of the retries. I've tried working out most of the bugs.
I'm confident I haven't worked out 100% of the bugs in this script, although I've tried very hard. I've only tested it with one device, the XT1060. If you have issues, please do not PM me, post them here in the thread.
If for some reason the script abnormally ends or you close out of it, without running the cleanup process at the end, ADB will remain present and cause an error in the script, which will cause the script to fail. Browse to the folder with the CMD prompt and type "ADB kill-server" (kill-server is case-sensitive). This will get the script running again.
Thanks jcase, beaups, saurik and anyone else who has contributed to this effort!
Changelog:
1/9/2014: Initial Release. Only tested on one device. Better bug management within each step, more options at advanced menu, including ADB Debug Window. Removed auto-upgrade to 4.4. I suspect this is where my woes were.
1/9/2014: Removed ADMINISTRATOR requirement. I don't think this will do any harm, but it was creating conflicts with Windows 8.
1/9/2014: Changed TELNET conditions to trap for user interaction.
1/14/2014: Adjusted initial TELNET session.
1/14/2014: Corrected a type on line 366 (would have given an error).
1/15/2014: Re-worked TELNET routine again.
1/16/2014: Simplified menu options, included automated checking for write protection. This check will skip steps once WP has already been turned off.
1/16/2014: Included additional instruction, including more messaging and better message waiting.
1/16/2014: Added additional messaging for troubleshooting purposes.
1/16/2014: Corrected a bug related to BATCH language that was ending the TELNET steps.
1/17/2014: Made another adjustment to TELNET handling.
1/17/2014: Added additional error checking.
1/17/2014: Added some wait time on the second TELNET phase.
2/28/2014: Canceled script effort (ran out of time). With 4.4.2 released, none of the current root methods are valid or work.
BEFORE YOU START WITH ANY METHOD THAT REQUIRES YOU TO WIPE YOUR DEVICE, MAKE SURE YOUR DEVICE IS 100% FULLY CHARGED!! IF YOUR DEVICE SHUTS DOWN WHILE THE SYSTEM IS FLASHING YOU WILL BRICK YOUR DEVICE!!!
heck yes!!!!!!!!!!!!!!!!!!!
Hold the phone. The script at the very last step isn't working. Can't fix right now. My personal device doesn't have root, so it failed. Will need to troubleshoot.
Appreciate the effort put into this for the community
Sent from my XT1060 using xda app-developers app
ok so the script seems to be doing what it's designed to do, which is good. but i've borked my device testing it, which is bad. but i was able to trap for more conditions and provide a better menu system, which is good.
as soon as i can figure out if i can un-bork my device, i'll post the script back up.
My device has root. Script is back online.
I really appreciate your hard work. I've had trouble getting this to work by myself. I'd love to give this a shot later today. I had a few questions though.
You said to "install the script" after it is downloaded but what exactly needs to be installed? Also you said to put all the files in the install folder, but I'm not seeing an install folder in the extracted .rar.
I want to make sure the script runs smoothly so it would be best if I could see exactly how your files are set up. Would you perhaps be able to upload a screenshot?
Thanks!
flipfreak said:
I really appreciate your hard work. I've had trouble getting this to work by myself. I'd love to give this a shot later today. I had a few questions though.
You said to "install the script" after it is downloaded but what exactly needs to be installed? Also you said to put all the files in the install folder, but I'm not seeing an install folder in the extracted .rar.
I want to make sure the script runs smoothly so it would be best if I could see exactly how your files are set up. Would you perhaps be able to upload a screenshot?
Thanks!
Click to expand...
Click to collapse
so my original intention was to distribute this as a self-extracting EXE but because i wanted to share my work and XDA's attachment policy, i changed it to a rar.
just unzip it (anywhere). you'll get a "640k's Moto X Root Script" folder. make sure your .zips from the links above are in the same folder as the Go!.CMD and you'll be good to go.
640k said:
so my original intention was to distribute this as a self-extracting EXE but because i wanted to share my work and XDA's attachment policy, i changed it to a rar.
just unzip it (anywhere). you're get a "640k's Moto X Root Script" folder. make sure your .zips from the links above are in the same folder as the Go!.CMD and you'll be good to go.
Click to expand...
Click to collapse
Thank you! That clears things up. I'll give this a try later and let you know how it went
flipfreak said:
Thank you! That clears things up. I'll give this a try later and let you know how it went
Click to expand...
Click to collapse
based on my testing, unless something goes completely wrong, it should be pretty hard to completely bork your phone. if you get into a bootloop, the advanced menu can help you restore your system files as long as you can get in to the bootloader (usually you can).
640k said:
based on my testing, unless something goes completely wrong, it should be pretty hard to completely bork your phone. if you get into a bootloop, the advanced menu can help you restore your system files as long as you can get in to the bootloader (usually you can).
Click to expand...
Click to collapse
Hmm, well I tried it but it keeps telling me that 7za.exe is not in the folder, even though it is sitting right above Go!.CMD. Any idea why it would say this? I ran it as an administrator
flipfreak said:
Hmm, well I tried it but it keeps telling me that 7za.exe is not in the folder, even though it is sitting right above Go!.CMD. Any idea why it would say this? I ran it as an administrator
Click to expand...
Click to collapse
can you screen shot the window and your folder where the files are?
thanks.
640k said:
can you screen shot the window and your folder where the files are?
thanks.
Click to expand...
Click to collapse
Sure
flipfreak said:
Sure
Click to expand...
Click to collapse
did you extract the contents to your desktop? i'm guessing it's failing because you're technically not running the cmd file in the same folder. for example, windows will allow you to run files directly from a .zip, but it caches that file in to a temp folder somewhere. if you haven't unzipped the files, the script won't see any of the files.
i'm here to help, i want this to be successful.
640k said:
did you extract the contents to your desktop? i'm guessing it's failing because you're technically not running the cmd file in the same folder. for example, windows will allow you to run files directly from a .zip, but it caches that file in to a temp folder somewhere. if you haven't unzipped the files, the script won't see any of the files.
i'm here to help, i want this to be successful.
Click to expand...
Click to collapse
Yeah, the files are all extracted to my desktop. If I run it as an administrator, it gives me the error telling me that that 7za.exe is not in the folder. If I don't run it as an administrator, it tells me that it will abort and to press any key to continue. When I press any key, it brings me to the menu where it asks me what I want to do.
I'm not sure what I could be doing wrong. Maybe we should just wait and see if anyone else has this problem. It could be on my end.
flipfreak said:
Yeah, the files are all extracted to my desktop. If I run it as an administrator, it gives me the error telling me that that 7za.exe is not in the folder. If I don't run it as an administrator, it tells me that it will abort and to press any key to continue. When I press any key, it brings me to the menu where it asks me what I want to do.
I'm not sure what I could be doing wrong. Maybe we should just wait and see if anyone else has this problem. It could be on my end.
Click to expand...
Click to collapse
ok i'm seeing the same issue. it's isolated to Windows 8. troubleshooting now.
Windows 8 is running the CMD prompt from /WINDOWS/SYSTEM32... which is the exact problem i detailed earlier. i'm going to remove the admin requirement. i don't think it's necessary.
flipfreak said:
Yeah, the files are all extracted to my desktop. If I run it as an administrator, it gives me the error telling me that that 7za.exe is not in the folder. If I don't run it as an administrator, it tells me that it will abort and to press any key to continue. When I press any key, it brings me to the menu where it asks me what I want to do.
I'm not sure what I could be doing wrong. Maybe we should just wait and see if anyone else has this problem. It could be on my end.
Click to expand...
Click to collapse
download the new file and try it again.
640k said:
download the new file and try it again.
Click to expand...
Click to collapse
That got it working. I'm now stuck at attempting a telnet session. Should I restart? Here's a screenshot
flipfreak said:
That got it working. I'm now stuck at attempting a telnet session. Should I restart? Here's a screenshot
Click to expand...
Click to collapse
i was afraid of that. open the TELNET.ERR file with notepad and show me the contents. jcase stuck some user interaction in there that only occurs one time, so i was never able to trap it again.
thanks for your help.
640k said:
i was afraid of that. open the TELNET.ERR file with notepad and show me the contents. jcase stuck some user interaction in there that only occurs one time, so i was never able to trap it again.
thanks for your help.
Click to expand...
Click to collapse
No problem.
ÿýÿý ÿûÿû
~ $ [6ndalvikvm -cp /sdcard/RockMyMoto.jar RockMyMoto
RockMyMoto 1.0
by Justin Case
PayPal Donations maybe sent to: [email protected]
Special thanks to saurik, you rock!
System is write protected...
Executing step 1...
To use RockMyMoto you most solve a
simple equation. This helps ensure
you are paying attention, and also
amuses JesusFreke and myself.
Solve for a:
a/24=70
Please type a whole number as your answer:
Click to expand...
Click to collapse
Description:
Andy Log is a small tool that dumps necessary logs for bug reporting without hassle.
Just choose what you'd like to include in your log file and click on LOG.
Supported (so far):
1. Logcat
2. Buildprop
3. CPU info
4. Sysctl
5. Kmsg
6. Last kmsg
7. Dmesg
8. Uptime
Logs are saved to /{MAIN STORAGE}/Android/data/{PACKAGE NAME}/Logs folder.
Download:
Andy Log (ROOT)
Change log
Reserved for change log:
v2.0
Fixed crashes on Android 6+
v1.4
Android N support (please work)
Fixed log folder chooser on Android 6
v1.3
Added:
Last crash option, useful for extracting the minimum required data for crash reporting.
(PRO) Logcat:
radio & events buffers.
Formating.
Filtering ( tag:level ex: AndroidRuntime:E )
v1.2
Fixed:
1. Problem with Italian date format.
Added:
1. Confirm and show log files' names before clearing them.
2. Share log option.
3. An option to change default logs folder.
v1.1
Fixed:
1. CLEAR LOGS bug.
2. Force close when no option is checked.
3. Force close during dumping logs due to DOCUMENTS field being undeclared in some devices' framework.
v1.0
Initial release.
@deeplyyoung try out this app bro , its just awesome. @Bassel Bakr good handy app which saves time. It also helps a lot of noobs around here to provide proper logs
Great work. :good:
Great!!! This is the most awaited app for newbies.
Nice, I'll have to try this out. I currently have SysLog & Logcat Extreme installed for their various functions. This might be a replacement for SysLog.
EDIT: Trying it now, it's been sitting on "Dumping KMSG" for about 5 minutes. I checked them all, by the way. Shall I use one of the aforementioned apps I use to record a logcat while it happens? Seems a bit ironic, I know.
yochananmarqos said:
Nice, I'll have to try this out. I currently have SysLog & Logcat Extreme installed for their various functions. This might be a replacement for SysLog.
EDIT: Trying it now, it's been sitting on "Dumping KMSG" for about 5 minutes. I checked them all, by the way. Shall I use one of the aforementioned apps I use to record a logcat while it happens? Seems a bit ironic, I know.
Click to expand...
Click to collapse
I'd be grateful if you did. ?
I'll make sure next update less prone to this problem.
Bassel Bakr said:
I'd be grateful if you did. ?
I'll make sure next update less prone to this problem.
Click to expand...
Click to collapse
I let it sit for about 5 minutes, so it's almost 10 thousand lines.
https://dl.dropboxusercontent.com/u/67194527/Log_2014-10-19_23-46-59.txt
Great app. Command lines made handy. Now users can easily submit logs to respective developers and contribute in smoother development :good:
@Bassel Bakr Could you add Dmesg feature?
Great, thank you, logs have always baffled me - this has made them much easier for me to understand.
Problem I'm facing is that I can't find the logs in the file path /0/android/data/com.bassel.andylog/files/documents/.....
When I get to documents there is nothing in that file.
I can see them when I first take the log and open it though?
Great app, just one thing. After taking a Logcat the log says “
Unable to open log device '/dev/log/main': No such file or directory ”. All other logs seem to work fine.
Bassel Bakr said:
Description:
Andy Log is a small tool that dumps necessary logs for bug reporting without hassle.
Just choose what you'd like to include in your log file and click on LOG.
Supported (so far):
1. Logcat
2. Buildprop
3. CPU info
4. Sysctl
5. Kmsg
6. Last kmsg
7. Uptime
Logs are saved to /{MAIN STORAGE}/Android/data/{PACKAGE NAME}/Documents folder.
Download:
Andy Log (ROOT)
Click to expand...
Click to collapse
I couldn't find this app on F-Droid. Is there a github repo or other link to the source?
@Bassel Bakr very useful app thanks but i think you should change the Default directory or add an option let us to choose saving directory.
iko11 said:
@Bassel Bakr very useful app thanks but i think you should change the Default directory or add an option let us to choose saving directory.
Click to expand...
Click to collapse
+1
I was thinking the exact same thing
Nice!
Cool App. Could You please include radio log dump (adb logcat -b radio -v time -d)?
filters possible for specific app?
Thanks everyone for your feedback. ?
New update v1.1 check second post change log.
yochananmarqos said:
I let it sit for about 5 minutes, so it's almost 10 thousand lines.
https://dl.dropboxusercontent.com/u/67194527/Log_2014-10-19_23-46-59.txt
Click to expand...
Click to collapse
Check v1.1
Al Arsyadi said:
@Bassel Bakr Could you add Dmesg feature?
Click to expand...
Click to collapse
It's already there but i forgot to include it in the description, sorry. ?
Jimsilver73 said:
Great, thank you, logs have always baffled me - this has made them much easier for me to understand.
Problem I'm facing is that I can't find the logs in the file path /0/android/data/com.bassel.andylog/files/documents/.....
When I get to documents there is nothing in that file.
I can see them when I first take the log and open it though?
Click to expand...
Click to collapse
Strange! Log file can't be opened unless it is already there! ?
Anyway, I'll look into it. ?
p1eter said:
Great app, just one thing. After taking a Logcat the log says “
Unable to open log device '/dev/log/main': No such file or directory ”. All other logs seem to work fine.
Click to expand...
Click to collapse
Do you get the same thing if you executed logcat command in a terminal emulator?
MiyagiSan said:
I couldn't find this app on F-Droid. Is there a github repo or other link to the source?
Click to expand...
Click to collapse
No, it's closed source.
iko11 said:
@Bassel Bakr very useful app thanks but i think you should change the Default directory or add an option let us to choose saving directory.
Click to expand...
Click to collapse
Thanks for your suggestion, I'll work on it.
ArdnoS75 said:
Cool App. Could You please include radio log dump (adb logcat -b radio -v time -d)?
Click to expand...
Click to collapse
Thanks for your suggestion, I'll work on it.
starbase64 said:
filters possible for specific app?
Click to expand...
Click to collapse
Thanks for your suggestion, I'll work on it.
Bassel Bakr said:
Thanks everyone for your feedback. ?
New update v1.1 check second post change log.
Check v1.1
Click to expand...
Click to collapse
It successfully saves the logs now. However, I noticed it saves them all to one file when selecting multiple. Also, if different logs are chosen using the default filename choice, there's no way to tell which one is which without opening them. Would it be possible to automatically generate the first part of the filename based on the type of log? i.e., kmsg--(Date)--(Time).txt, etc? Thanks!
Bassel Bakr said:
Do you get the same thing if you executed logcat command in a terminal emulator?
Click to expand...
Click to collapse
Logcat command gives me “Unable to open log device '/dev/log/main': No such file or directory ”
When I tried to create the folders /log/main terminal returned “logcat read: Is a directory”
This problem has been bothering me all day. My phone is always out of memory and I've found out that it's the logcat files that are causing this. I've managed to root my phone and connect it to the adb shell on my PC but I have no idea how to remove the logcat files. I would appreciate if you could help me!
Zablas said:
This problem has been bothering me all day. My phone is always out of memory and I've found out that it's the logcat files that are causing this. I've managed to root my phone and connect it to the adb shell on my PC but I have no idea how to remove the logcat files. I would appreciate if you could help me!
Click to expand...
Click to collapse
Check out this article. There's an app linked in it as well.
http://www.androidpolice.com/2014/0...r-enhanced-privacy-and-performance-root-only/
Thank You for your time but I've managed to find an older version of the App since it's no longer on the Play store. It only blocked the Main logs. But how do I delete the old logs which take up gigabytes? Anyway to do it through the ADB shell?
Zablas said:
Thank You for your time but I've managed to find an older version of the App since it's no longer on the Play store. It only blocked the Main logs. But how do I delete the old logs which take up gigabytes? Anyway to do it through the ADB shell?
Click to expand...
Click to collapse
Logs taking up Gigabytes
Are those tree logs?
What device are you using? IIRC some MTK devices have an engineering mode. I've used it to disable logging before.
If you just want to clear them, download 3C System Tuner from the Playstore. It'll give you that option.
Freewander10 said:
Logs taking up Gigabytes
Are those tree logs?
What device are you using? IIRC some MTK devices have an engineering mode. I've used it to disable logging before.
If you just want to clear them, download 3C System Tuner from the Playstore. It'll give you that option.
Click to expand...
Click to collapse
Additionally, if you can locate the folder in which they're stored, you can just go ahead and delete them manually.
Not sure if this will work on android's shell, but it works on the linux's. You can do this via adb.
Adb shell
Then su to get root access
find / (make sure to add a space!) and then .log I guess
RAZERZDAHACKER said:
Not sure if this will work on android's shell, but it works on the linux's. You can do this via adb.
Adb shell
Then su to get root access
find / (make sure to add a space!) and then .log I guess
Click to expand...
Click to collapse
The commands didn't work sorry :/ it said "not found" for them
Freewander10 said:
Logs taking up Gigabytes
Are those tree logs?
What device are you using? IIRC some MTK devices have an engineering mode. I've used it to disable logging before.
If you just want to clear them, download 3C System Tuner from the Playstore. It'll give you that option.
Click to expand...
Click to collapse
I'm using LG G2 Mini running Android 5.0.2