Develop Bugs

[Q] What to do if someone asks for my specific problem log file?

Folks, i really don't know what to do to get a specific problem log file to be sent/showed to someone to fix my problem, any help or suggestions will be really appreciated here

If you just had a hard reboot, once booted up, from pc
Adb pull /proc/last_kmsg
This will get last kmsg file related to the last boot session to your pc.
If no hard reboots but freezes etc, then
Adb shell dmesg > /sdcard/dmesg.txt
To see what's been going on since the boot at kernel level. File gets created on sdcard. Use
Adb pull /sdcard/dmesg.txt
To get it to your pc.
To get a log of something, before trying it, start the logcat with
Adb logcat > logcat.txt
File will be created on the pc.
This is from my post 6843 in official cm10 thread. You can also use
Adb shell cat /proc/kmsg > /sdcard/kmsg.txt
To see kernel logs since last boot.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Edit: /proc was missing 3 lines above

eyosen said:
If you just had a hard reboot, once booted up, from pc
Adb pull /proc/last_kmsg
This will get last kmsg file related to the last boot session to your pc.
If no hard reboots but freezes etc, then
Adb shell dmesg > /sdcard/dmesg.txt
To see what's been going on since the boot at kernel level. File gets created on sdcard. Use
Adb pull /sdcard/dmesg.txt
To get it to your pc.
To get a log of something, before trying it, start the logcat with
Adb logcat > logcat.txt
File will be created on the pc.
This is from my post 6843 in official cm10 thread. You can also use
Adb shell cat /kmsg > /sdcard/kmsg.txt
To see kernel logs since last boot.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
thanks eyosen you are the best
what if i already rebooted it several times due to weird signal loss? please check this http://forum.xda-developers.com/showthread.php?p=32791585#post32791585
does this means i've lost the latest log? if no, then how to extract the specific problem log from it such as the signal loss? or shall i send the whole log?

Hossam.Abdelsalam said:
thanks eyosen you are the best
what if i already rebooted it several times due to weird signal loss? please check this http://forum.xda-developers.com/showthread.php?p=32791585#post32791585
does this means i've lost the latest log? if no, then how to extract the specific problem log from it such as the signal loss? or shall i send the whole log?
Click to expand...
Click to collapse
use "adb logcat -b radio"
Press the thanks button if you want to thank me

You are welcome.
Just send the whole log. Best practice is to post it to pastebin and post the link in the forum.
After every reboot you will lose the previous last_ksmg.
Sent from a gadget on my balcony.

wcypierre said:
use "adb logcat -b radio"
Press the thanks button if you want to thank me
Click to expand...
Click to collapse
i already pressed it
but it seems this shows you the log at the run time, but what am trying to get is the log of my weird signal loss for incidents happened yesterday, is this even possible?

No that's not possible. You can start a logcat, repeat the steps that caused the problem, after the problem , post logcat and kmsg.
Sent from a gadget on my balcony.

Hossam.Abdelsalam said:
i already pressed it
but it seems this shows you the log at the run time, but what am trying to get is the log of my weird signal loss for incidents happened yesterday, is this even possible?
Click to expand...
Click to collapse
well, it should be able to trace back if the time duration is not that long, but you can just try and do what eyosen had suggested

[Q] How to install from unknown sources without ADB?

So, by going into the settings menu of the FTV and toggling the ADB Debug flag, this allows for installing via a push from ADB.
The text that is displayed when changing this value also says that by enabling the setting, it allows for package installs from unknown sources.
Is this not quite the case though?
Using ES File Manager, when selecting an apk package located in the downloads folder on the device, the message shown in the attached screenshot appears.
Since there's no way to do so from the front-end, I am assuming that we will need root to change the flag to truly allow installing from any source?
Any possible way to do this without root?

mkhopper said:
So, by going into the settings menu of the FTV and toggling the ADB Debug flag, this allows for installing via a push from ADB.
The text that is displayed when changing this value also says that by enabling the setting, it allows for package installs from unknown sources.
Is this not quite the case though?
Using ES File Manager, when selecting an apk package located in the downloads folder on the device, the message shown in the attached screenshot appears.
Since there's no way to do so from the front-end, I am assuming that we will need root to change the flag to truly allow installing from any source?
Any possible way to do this without root?
Click to expand...
Click to collapse
Yeah, this isn't currently possible for the public. There is a root exploit(s) already developed but they have not been released yet. The developer, jcase, said he will release an exploit on the same day the upcoming Fire TV update is pushed (the exploit will not be compatible with the update so if you want it you'll need to follow the instructions in the other thread for blocking OTA updates).

mkhopper said:
Any possible way to do this without root?
Click to expand...
Click to collapse
Are you having issues with ADB? We can probably help you get those resolved.

Chahk said:
Are you having issues with ADB? We can probably help you get those resolved.
Click to expand...
Click to collapse
Thanks, but no. I use the automatic tool to push packages with no problems. I was just looking for other methods of package installation that could be done directly while on the FTV.

mkhopper said:
Thanks, but no. I use the automatic tool to push packages with no problems. I was just looking for other methods of package installation that could be done directly while on the FTV.
Click to expand...
Click to collapse
Not at this time. Amazon disabled side-loading of APKs from the device itself. Root would be the only way to get around that.

mkhopper said:
Thanks, but no. I use the automatic tool to push packages with no problems. I was just looking for other methods of package installation that could be done directly while on the FTV.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2715315
Sent from my MZ617 using XDA Premium 4 mobile app

Kramar111 said:
http://forum.xda-developers.com/showthread.php?t=2715315
Click to expand...
Click to collapse
several days ago it occurred to me to alternatively use sshd for terminal access, because:
-a) I feel a little unsafe leaving adb wifi enabled all the time (ok it's only a small thing to turn it on and off, but still) - and for security reasons there is no way to enable/disable it programmatically e.g. from a script/shell/terminal/app (well theoretically this is not exactly true, but practically it is)
-2) some people (i.e. me) would like to do shell/terminal remotely sometimes, rather than on the AFTV (and other people don't have/want a keyboard)
ssh access makes a great alternative to Term.apk, but the problem is:
- Term.apk and/or (pick your favorite android ssh server) don't have permission to run e.g. "pm install foo.apk" - it will fail. (btw 'pm' is a great command, take a look sometime at all the options. it shares a lot of functions as the adb command itself. 'am' is another fun command...)
- so, the hilarious workaround of enabling adb wifi, "adb connect", and then finally "adb shell" or "adb install" etc., is still required. (b/c the adb user is in the 'shell' group, among others - giving it permission to run /system/bin/pm) - oh well.
for random reference:
Code:
127|[email protected]:/ $ id
uid=2000(shell) gid=2000(shell) groups=1004(input),1007(log),1009(mount),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats)
[email protected]:/ $ exit
[email protected]:/ $ id
uid=10009(app_9) gid=10009(app_9) groups=1015(sdcard_rw),1028,3003(inet),50009(app_40009)
(also note it appears the adb shell user might possibly have 'mount' abilities, but since the /dev/block/sd* nodes permissions' are really locked up, who knows...)

Generating a new adb key

Hi,
Not sure if this is the right place (but only place I can post) I've been trying to root my phone in order to install TWRP on my Pixel XL, in order to do so I need to unlock my bootloader.
Now this won't work as in ADB it shows my device as unauthorised, and I've tried everything! Revoking permissions USB debugging, rebooting, the other solution involces deleteing the adb key in .android, but my only .android folder is under c:\\users\MyName\.android and has no adbkey here, only 3 folders -> avd, cache and studio, all of these being empty!
I'm at a real loss to authorise my device so I can continue to root my device.
Any help would be appreciated.
Kind regards

MunkeyBoy14 said:
Hi,
Not sure if this is the right place (but only place I can post) I've been trying to root my phone in order to install TWRP on my Pixel XL, in order to do so I need to unlock my bootloader.
Now this won't work as in ADB it shows my device as unauthorised, and I've tried everything! Revoking permissions USB debugging, rebooting, the other solution involces deleteing the adb key in .android, but my only .android folder is under c:\\users\MyName\.android and has no adbkey here, only 3 folders -> avd, cache and studio, all of these being empty!
I'm at a real loss to authorise my device so I can continue to root my device.
Any help would be appreciated.
Kind regards
Click to expand...
Click to collapse
Have tried to delete the whole .android folder ? and do you have the latest adb / fastboot files. but to unlock your bootloader you actualy dont need adb just fastboot ?

After revoking permissions did you kill and restart the adb server:
adb kill-server
adb start-server
Sent from my Pixel XL using Tapatalk

ahent said:
After revoking permissions did you kill and restart the adb server:
adb kill-server
adb start-server
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Yes I did, and nothing changed.

Hogyoku said:
Have tried to delete the whole .android folder ? and do you have the latest adb / fastboot files. but to unlock your bootloader you actualy dont need adb just fastboot ?
Click to expand...
Click to collapse
I used the adb installer by Snoop05 and using that installed latest drivers too! I shall delete the folder and see what happens I guess?

MunkeyBoy14 said:
I used the adb installer by Snoop05 and using that installed latest drivers too! I shall delete the folder and see what happens I guess?
Click to expand...
Click to collapse
Not sure if the link will work but try these this is straight from Google
https://plus.google.com/+YamaniMondt/posts/AjgC41SYT9h

When I run the "adb shell" commad I get the following:
C:\adb>adb shell
adb server is out of date. killing...
* daemon started successfully *
error: device unauthorized.
This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Not sure if this helps at all

Hogyoku said:
Not sure if the link will work but try these this is straight from Google
https://plus.google.com/+YamaniMondt/posts/AjgC41SYT9h
Click to expand...
Click to collapse
Thank you so much! Running adb using the attached link caused me to get the pop up to approve the RSA. And is now showing as authorised. THank you!

MunkeyBoy14 said:
Thank you so much! Running adb using the attached link caused me to get the pop up to approve the RSA. And is now showing as authorised. THank you!
Click to expand...
Click to collapse
No problem

Samsung secret codes, need halp asap!

I just noticed that Samsung secret codes doesn't work o nougat. I don't know if it's in nougat but in the custom ROM? Can anyone teach me how to access secret codes. I've tried everything. Need help, asap.

Launch a simple code like *#06# and check
Code:
logcat -s XMLParser
or
Code:
logcat -b all -s XMLParser:V
in a system wide logcat like adb or root.
If there's a "file not found" error search /system/csc/CSC/system/etc/CSC_keystrings.dat. Rename and copy that file to whatever fits that file not found error. It's possible to use a file meant for another device or CSC to unlock *#2263#, *#2683662#, etc. If without root, try to fully apply the CSC, maybe a stock recovery is required.

[help] imei 0 moto g5 xt1671 dual sim

Hello people, I come to ask for help that I need urgently. Well at the beginning of the year install pixel experiencie and I did not backup the efs folder, when I returned to stock I lost it and from there every day I searched for solutions and I am still looking for some. If anyone knows any effective method or not, you can help me. Thanks greetings
(Sorry for the English, I use the google translator)

TioNacho said:
Hello people, I come to ask for help that I need urgently. Well at the beginning of the year install pixel experiencie and I did not backup the efs folder, when I returned to stock I lost it and from there every day I searched for solutions and I am still looking for some. If anyone knows any effective method or not, you can help me. Thanks greetings
(Sorry for the English, I use the google translator)
Click to expand...
Click to collapse
There's a possible fix until the moment you flash persist or restore EFS from another phone to yours.
ONCE AGAIN, DON'T TRY TO FLASH PERSIST OR RESTORE EFS FROM ANOTHER PHONE!!!
Just root your phone using Magisk and execute these commands using adb on your PC/laptop:
Things to note before you start executing commands below:
1. Make sure that USB debugging in your phone is turned on.
2. If everything is set properly and "adb devices" has been executed, u should see popup window about ADB allow on your phone BUT ONLY IN CASE YOU ARE USING ADB ON PC WHICH WASN'T USED FOR ADB YET. Make sure "Always allow from this PC" is checked and click "OK". Re-run command one more time. You should be able to see your device in cmd window now.
3. After "su" command, you have to grant root access to adb shell within 10 seconds.
4. "adb reboot" command will immediately reboot your phone, don't panic.
5. You are doing this at your own risk.
Code:
adb devices
adb shell
su
chown -R rfs:rfs /persist/rfs
chown -R rfs:rfs_shared /persist/hlos_rfs
adb reboot
Commands have been used from this thread: https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147

Good morning!
Look I was able to recover the signal (h +) with that command but not imei. Will not you know other commands that will make him recover or some method? regards