Database Info

Weird adb ls output

After installing the JH2 ROM and using unleash the beast, I'm getting weird output from the ls command in the adb shell. Apparently, I can't post links or pictures, yet. So, here's a sort of link:
picasaweb. google. com/ lh/ photo/ VQKACQqA9i7u8ZWG3OmRGQ?feat=directlink
I'm getting listings of entries like [1;34mcache [0m
and [0;0mdefault.prop [0m
before each of the square brackets, there is a left-pointing arrow.
What's causing this? It seems to be an expanded version of the directory listing. How do I turn it off?

belyle said:
After installing the JH2 ROM and using unleash the beast, I'm getting weird output from the ls command in the adb shell. Apparently, I can't post links or pictures, yet. So, here's a sort of link:
picasaweb. google. com/ lh/ photo/ VQKACQqA9i7u8ZWG3OmRGQ?feat=directlink
I'm getting listings of entries like [1;34mcache [0m
and [0;0mdefault.prop [0m
before each of the square brackets, there is a left-pointing arrow.
What's causing this? It seems to be an expanded version of the directory listing. How do I turn it off?
Click to expand...
Click to collapse
thats normal...

designgears said:
thats normal...
Click to expand...
Click to collapse
When I was using the original kernel and the one-click root, my adb shell ls was only file names, not the extra stuff. When I use the ls command in terminal emulator on the phone, it's just the file names.
Also, when I grep the output of ls, the output of grep doesn't have the info in the square brackets, just the file name(s) that meet the criterion.

Thats the ls command sending color codes. It looks nice on a terminal that supports it but weird on windows.
To temporary solve it, after adb shell do this:
alias ls='ls --color=never'
It will fix the problem until you exit adb.
Sent from my SAMSUNG-SGH-I897 using XDA App

LGSilva said:
Thats the ls command sending color codes. It looks nice on a terminal that supports it but weird on windows.
To temporary solve it, after adb shell do this:
alias ls='ls --color=never'
It will fix the problem until you exit adb.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
This was it. Thank you very much. I'm not sure why I didn't see the extra info on my other ROM, but there it is.
I don't suppose there's a different terminal/command prompt for windows that would show the colors?

ls -l
will just give you a standard list of files.

ok I have the supernoob question of the day. can you type adb commands via the terminal emulator on the phone, or do you have to be connected to a computer via usb? I downloaded adb wireless, but im thinking that i have to have the sdk set up on my comp first? Im just a little confused as you can tell

The terminal is the equivalent of doing 'adb shell'. You will have to download the android SDK to get the actual adb tool if you want to do push/pull etc. with it.

belyle said:
This was it. Thank you very much. I'm not sure why I didn't see the extra info on my other ROM, but there it is.
I don't suppose there's a different terminal/command prompt for windows that would show the colors?
Click to expand...
Click to collapse
http://code.google.com/p/puttycyg/ this does.

very old post that got bumped to the top. If you didn't try puttycyg and not interested in colors you can try this: http://forum.xda-developers.com/showpost.php?p=8036010&postcount=7
It works for me.

[Q] Why do I get bash-4.1# instead of [email protected]:~# ?

[deleted]
[deleted]

Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A

if i'm not mistaken, there is no big difference whether it displays bash# or [email protected] as long as you see the hash tag, you are under the super user or root.

The bash prompt probably was not exported so it back to it's default when you open another shell.
The prompt can be changed to whatever you want, using PS1="my_prompt".
You want your prompt to be export PS1="\[email protected]\h:\W\$ ". You can add it to the initial command (add an semicolon as a separator if you have other initial command). Don't forget to left an space to the final of PS1 or your commands will appear concatenated with the prompt.
As conectix said, the only important character is the last one: if it is a sharp the shell is executing as user, and if it is a dollar then you have root privileges.
---------- Post added at 06:05 PM ---------- Previous post was at 05:30 PM ----------
Another thing to observe is that in the post you mentioned was said that a shell is open, what fits on what I said above.
Another observation is that sh and bash are different shells. On my Terminal Emulator the default shell is sh. So if I type 'bash' it enters on bash shell and the prompt changes. Once I exit (typing 'exit') of bash it returns to sh with a simple dollar prompt (which is wrong because I'm running as a user).
You can verify your prompt by typing 'echo $PS1'. On mine it just have a dollar with an space.

Oke sure thank you for this, but why can't I use "ui" ?
it will say that the command is not found but in the tutorials and videos on youtube you can see that after they do this they immediately get a red "[email protected]:~#" instead of the "bash-4.1" and after they enter "ui" it works for them. I do exactly the same but get to command not found error.

F4LLCON said:
Oke sure thank you for this, but why can't I use "ui" ?
it will say that the command is not found but in the tutorials and videos on youtube you can see that after they do this they immediately get a red "[email protected]:~#" instead of the "bash-4.1" and after they enter "ui" it works for them. I do exactly the same but get to command not found error.
Click to expand...
Click to collapse
Probably the command ui isn't in your path. The path is where your shell searches for the binaries to execute.
You need to locate the ui binary (his path) and export a new path:
Code:
export PATH=$PATH:[B]ui-binary-path[/B]
Where ui-binary-path is the path (directory) where the ui binary is located.
PS: You need to reply me so I'll be notified of your response.

This can help you to get solution
Try executing list of following commands:
cd /etc/profile.d/
vi bash_prompt.sh and type: export PS1='[\[email protected]\h \W]$ '
su - root
Hope so the problem is fixed :fingers-crossed:
Regards,
Abhishek Kalekar

Tutorial: How to properly post a bug

Alright guys, I was on an irc channel when I considered posting this since it's rather important. There has been a lot of disappointing posts all over the forum with people complaining about bugs, while not providing any kind of information for the developers aside from "X doesn't work" or "I get random reboots".
Well, without the proper knowledge, how are we going to fix it? We don't know what kernel you may be running, what version number you're on, or any information that the system spits out to let you know there's an error. So, I decided to start this thread, to hopefully teach newbies how to give us (developers) proper knowledge when complaining about issues.
This thread will have 3 sections, Logcat (App / system debug log.), Dmesg (active kernel output) and last_ksmg (Typically if you get a random reboot or something of that sort {this is the same as dmesg except it gets the info from the last shutdown [like a kernel panic]})
Section 1: Logcat
This log should almost always be included just because it provides more info than just saying something doesn't work. It will essentially tell you which apps are crashing and why and it also gives output of what they're doing. (Your system is running through apps, the dialer, wireless radio's, etc are all ran through apps.) so, if something is general, like a system force close, please just include a logcat.
How to get a logcat:
Well, this is REALLY simple, all you need to do is just get adb up and running (google how to do that, I don't feel like writing a 'how to use adb' tutorial for everyone's phone.) and then type
Code:
adb logcat
then you just right click, select, and paste to the thread. It's really that simple!
Section 2: Dmesg
This is getting into issues such as wifi not working, sleep of death, etc. Basically, things that make us go "OH F***" when we use our devices. Note: You will need adb access for this to work, same as logcat.
What this will do is get us live kernel output so we can know things like "What driver is the kernel loading {or not loading for that matter}" and similar things. This is linux, so kernel output is important if a hardware aspect isn't working right.
How to get a dmesg:
This is simple as well, no matter what operating system you're on (mac, windows, linux) just type
Code:
adb shell dmesg > dmesg.txt
and then it will have written the output to a .txt file in your current directory. Either paste the contents to the thread, or attach it to your post.
You can also get the dmesg by using terminal emulator. Instead though, you dont type adb shell, you need to also include it to somewhere you will be able to save it. Like /sdcard so, the command goes
Code:
dmesg > /sdcard/dmesg.txt
Just get it off your sdcard and get the contents to the developer!
Section 3: last_kmsg
Ok, the last thing is last_kmsg. When android kernels crash, they right to last_kmsg so then you can find out what's going on. This is usually for issues such as random reboots and other various kernel panic symptoms. A kernel panic happens when the kernel tries to do something it can't. It doesn't mean wrong permissions, it could just have errored out on something and died which can cause a few things. Anyway, developers REALLY need this if debugging a kernel because it gives us a viable way to see WHAT it's trying to do instead of trying to guess what it is trying to do
How to get a last_kmsg:
This is super simple and the same on all phones no matter what, what you need is adb up and running (or terminal emulator) and either in adb shell, or terminal emulator just type
Code:
cat /proc/last_kmsg > /sdcard/last_kmsg.txt
or you can do
Code:
adb shell cat /proc/last_kmsg > kmsg.txt
and that will write it to your current working directory from cmd.
Hopefully, this way we developers can have our lives be a little bit easier and you can learn more about android.
I'm glad to have written this and devs, feel free to link to this guide as a "bug reporting FAQ"

HALP! I BRICKD MY FONE!!1!
I JAILBROKED IT LAST NIGHT AND NOW I NO GET SIGNEL!! PLASE HALP!!!1
but on a more serious note, good tut

Thanks dude!!! I was looking for some kind of guide. Only thing I still don't understand is when are we supposed to give dmesg and when do we give the logcat? I understand the last_kmsg is for kernel panics and random reboots, but the rest two are still ambiguous to me... Could you please explain the other two in a simpler way with an easy example for each?... Sorry.. I'm a noob... but am trying to learn these things..

There also is this app called 'Bootlog Uptime' that tries to auto-detect a crash and subsequently exports the log to sdcard.

When I get in to cmd in bootloader mode and type adb shell cat /proc/last_kmsg > kmsg.txt, I get a message Error: Device not found. I checked the ADB drivers, the are loading well. Am I doing something wrong?

If you're in boot loader mode, that's not adb.
Sent from my Full Android on Crespo4G using xda premium

anshumandash said:
When I get in to cmd in bootloader mode and type adb shell cat /proc/last_kmsg > kmsg.txt, I get a message Error: Device not found. I checked the ADB drivers, the are loading well. Am I doing something wrong?
Click to expand...
Click to collapse
You need to boot into the ROM, then grab the logs.
Sent from my GT-I9100 using xda app-developers app

Thank you for this
Sent from my Nexus 4 using Xparent BlueTapatalk 2

Can someone help me please.
I am from the HTC One S (Ville C2) community. I am testing a new kernel by one of the devs who doesnt have the phone. Now after installing the new kernel the phone is on bootloop. I need to extract the last_kmsg. the only way I can get out of the boot loop to do anything is by pressing the power button and simulate battery out. This it seems erases the last_kmsg cuz when I enter recovery to get it. It either says no such file or sometimes ends up showing me the recovery kernels last_kmsg. I am at a total loss as to how I the last_kmsg file.
There is also no way to install a working boot image as the kernel uses a zip to install files on the phone so we must use recovery to restore to previous state. This leads to the original condition. I tried looking for a solution but cant find it anywhere.

I tried the above method (via the Terminal Emulator) for finding the last_kmsg (my phone had just rebooted) and it says "/system/bin/sh: cat: /proc/last_kmsg: No such file or directory"
And Indeed, there is no last_kmsg file in my proc folder. Is there something I have to do to create it in the first place?
Thanks!

piyush_soni said:
I tried the above method (via the Terminal Emulator) for finding the last_kmsg (my phone had just rebooted) and it says "/system/bin/sh: cat: /proc/last_kmsg: No such file or directory"
And Indeed, there is no last_kmsg file in my proc folder. Is there something I have to do to create it in the first place?
Thanks!
Click to expand...
Click to collapse
I have the same problem.
Nexus 7-16 GB, PA 3.00, faux kernel 16 ultimate

Just solved the last kmsg problem. Instead of making the terminal do the job and getting "there is no such directory", just go above one level from sdcard and find proc folder. There will be a file named last_kmsg.
Hope it helps someone
Nexus 7-16 GB, PA 3.00, faux kernel 16 ultimate
---------- Post added at 10:13 AM ---------- Previous post was at 10:08 AM ----------
piyush_soni said:
I tried the above method (via the Terminal Emulator) for finding the last_kmsg (my phone had just rebooted) and it says "/system/bin/sh: cat: /proc/last_kmsg: No such file or directory"
And Indeed, there is no last_kmsg file in my proc folder. Is there something I have to do to create it in the first place?
Thanks!
Click to expand...
Click to collapse
Wait a few minutes it will be there
Nexus 7-16 GB, PA 3.00, faux kernel 16 ultimate

Kaiyes said:
Just solved the last kmsg problem. Instead of making the terminal do the job and getting "there is no such directory", just go above one level from sdcard and find proc folder. There will be a file named last_kmsg.
Click to expand...
Click to collapse
Kaiyes said:
Wait a few minutes it will be there
Click to expand...
Click to collapse
Nope. It's still not there for me ... I have a file called kmsg, but not last_kmsg.

Good stuff!

I'm on JB 4.3, Galaxy Note 2 and I've Flash Davil Kernel.
Two Bugs for me:
1) when the Phone, in switch off, is charging... the LED will not light. No Red Light (when in charging), nor Green one, when it has reached the 100%.
2) When Phone is connect to PC it isn't recognized by the PC in any way. To transfer files I have to use some app via Wi-Fi.
Are Two knows Bugs? Thanks in advance.

Hey glowerita I have this same problem minus the devil kernel. I don't think devil works with the FTW rom
Sent from my SPH-L900 using Tapatalk

Aquarius169 said:
Hey glowerita I have this same problem minus the devil kernel. I don't think devil works with the FTW rom
Sent from my SPH-L900 using Tapatalk
Click to expand...
Click to collapse
Hi! About PC recognize I've done so and now it's ok.
With Terminal emulator digit;
su
Press Enter.
Now digit; setprop persist.sys.usb.config mtp,adb
Enter, exit and reboot device and PC. [emoji1]
About led light... have you same problem like me?
Inviato dal mio GT-I9100 utilizzando Tapatalk

Take a look at
https://play.google.com/store/apps/details?id=com.bassel.andylog
... [email protected]

dmesg kmsg not permitted
Here's the dmesg.txt file when issuing C:\platform-tools>adb shell dmesg > dmesg.txt
"klogctl: Operation not permitted"
So I tried:
"C:\platform-tools>adb shell
←7←[r←[999;999H←[[email protected]:/ $ su
su
←7←[r←[999;999H←[[email protected]:/ # dmesg > dmesg.txt
dmesg > dmesg.txt
sh: can't create dmesg.txt: Read-only file system"
Results of issuing "C:\platform-tools>cat /proc/last_kmsg > /sdcard/last_kmsg.txt
The system cannot find the path specified.
C:\platform-tools>adb shell cat /proc/last_kmsg > kmsg.txt
/system/bin/sh: cat: /proc/last_kmsg: Operation not permitted"
Same results running terminal on phone also.
-Running PecanCM's CM11 Beta10 on LG L5 e610-

So neat and simple. Thanks for clarifying that.

Need help to get Tom Tom working on Intel device

Hi Guys,
As we all know Tom Tom does not work on the intel units.
For the MTCB devices there is a way to get it working: https://forum.xda-developers.com/an...lution-tomtom-connection-to-internet-t3368026 To get that working you need xposed installed. Since we can not install xposed we can not use that methode.
If we look at this post: https://forum.xda-developers.com/showpost.php?p=69772506&postcount=109 someone already tried to put a serial into the default.prop file but that does not work.
I found this page: http://stackoverflow.com/questions/19368712/where-is-ro-boot-serialno-and-ro-serialno-stored that does not work neither.
http://forum.odroid.com/viewtopic.php?f=94&t=12243
This page says we need to extract the boot.file and use the CarlivImageKitchen tool to extract it so we can modified the file.
I could find the boot.img in the latest update from joying: https://www.carjoying.com/Joying-blog/59.html location: 5009_20.zip.
I tried to extract the boot.img and unpack it with the Kitchen tool and found the init.rc file. Also found the on boot section and added the following lines:
Code:
# Set serial number.
setprop ro.serialno 1234567812345678
setprop ro.boot.serialno 1234567812345678
setprop ril.serialnumber 1234567812345678
Also added those lines to the default.prop file.
Repacked the file and put everything together.
We know that if we put a usb stick with the latest firmware in the usb input from the device it will automatic update and so also the new serial numbers.
The point is, i only wrote a android program a few times and i do not know much about boot files etc.
My question to your developers (because you are 100x times better then i am) would this work? What could probably go wrong if we add 3 lines in the ini.rc file?
Hoping to get some help from you guys!

According to the steps you need to do to get root i found the command to copy the boot.img to the device:
Code:
adb shell dd if=/mnt/usb_storage/USB_DISK0/udisk0/boot.img of=/dev/block/mmcblk0p9
I used the boot.img from the root steps. Added the command in the init.rc file and default.prop. Copied it back to the device and booted.
No luck with the ro.serialno and ro.boot.serialno. serialno was changed to what i have set.
The values of ro.serialno are overwritten somewhere else

Hi,
Have you been able to change the serial no. yet? I'm also waiting for a solution to install Tomtom GO on to this intel headunit

Nope still no success.
I don't have any idea what i can do to fix it.

Put here photo whit error tomtom go please and model headunit and android .

[Guide] [Android 6.0+] Change Device Model Name (Additional Steps Required)

Starting from Android Marshmallow and above, simply changing the ro.product.model entry in /system/build.prop will not change the device's name everywhere. The build.prop change can only be seen in Settings > About phone.
Introduced in 6.0, Android stores your device name in an additional location, in addition to the build.prop entry. It is stored in a database in your phone's memory. The value in the database is populated the first time you boot up your device (after installing ROM for example), so even if you alter the device name in build.prop, apps can still detect your "old" device name through the database entry.
In the past, the database was stored in a file, but since Marshmallow Settings Storage (com.android.providers.settings) stores a bunch of your phone's settings in memory. Here is how you can change your device's model name.
1. You should modify the ro.product.model entry your /system/build.prop if you haven't already:
Example:
Code:
ro.product.model=My Phone Model Name
2. Next, connect your device to the computer, make sure you have ADB installed.
Alternatively, you can use Terminal Emulator on your device. Run the commands below as root user, but do not include the adb shell part.
3. Execute the following to see the device name stored in the device's Settings database:
Code:
adb shell settings get global device_name
It should return your current device name, <DEVICE_NAME>.
4. Replace the existing model name with a new one:
Code:
adb shell settings put global device_name "<NEW_DEVICE_NAME>"
For example, if I want to change my device name to My Phone Model Name, I would issue the following command:
Code:
adb shell settings put global device_name "My Phone Model Name"
6. Now check to see the device name is updated (same as first command)
Code:
adb shell settings get global device_name
It should now return the updated device name. E.g, My Phone Model Name
Next, reboot your device and apps should correctly detect your new device name.
I hope this helps! Feel free to leave any questions or comments in this thread.
Additional Resources:
@piit79 has a similar tutorial for changing your device's ID, also for Marshmallow and above:
https://forum.xda-developers.com/ne...android-id-t3219345/post63168322#post63168322

Good tutorial, but I would recommend using simpler ADB commands.
For example, change this:
adb shell content insert --uri content://settings/global --bind name:s:device_name --bind value:s:<DEVICE_NAME>
to this:
adb shell settings put global device_name <DEVICE_NAME>

MishaalRahman said:
Good tutorial, but I would recommend using simpler ADB commands.
For example, change this:
adb shell content insert --uri content://settings/global --bind name:s:device_name --bind value:s:<DEVICE_NAME>
to this:
adb shell settings put global device_name <DEVICE_NAME>
Click to expand...
Click to collapse
Thanks, that makes it much simpler. Seems like the put command overwrites the existing value for you.

wow, good job, this looks really good (though i don't need it right now, it is good to know it's possible). my question is, would something similar be possible for the name of the rom and kernel? i'd like my bank's app to think i'm on stock, it does check safetynet but even with magisk and passed safetynet it doesn't work on any other rom than stock.. thanks in advance for your answer!

Google Photos
Will this enable Google Photos full size backup if I rename my 6P to Pixel XL?

This looks like it only changes the device name, that we can change through settings anyways. Editing the build.prop changed the model, but nothing else has changed that I can tell. For example, my Note 3 is running an S7 Edge port, the device and model name have been changed back to SM-900V (for the Note 3) but the product is still showing hero2ltexx. I realize that's just another build.prop line.
There is a huge possibility that this is doing just what it was intended to do and I daydreamed some imaginary far off results, but I figured I'd list it in case it was any help...thank you

bombaglad said:
wow, good job, this looks really good (though i don't need it right now, it is good to know it's possible). my question is, would something similar be possible for the name of the rom and kernel? i'd like my bank's app to think i'm on stock, it does check safetynet but even with magisk and passed safetynet it doesn't work on any other rom than stock.. thanks in advance for your answer!
Click to expand...
Click to collapse
Hi, the ROM and kernel information are not stored in the global settings database. However, you can try modifying your ROM name in the /system/build.prop file.

prwnd said:
Will this enable Google Photos full size backup if I rename my 6P to Pixel XL?
Click to expand...
Click to collapse
I'm not sure, but I think the device name must be set to Pixel XL when you set up your device for the first time. This is why full-size Photo backups work on custom "Pixel" ROMs (for non-Pixel devices).

I'm sure you can do it with terminal emulator on rooted device, so no ADB and PC is needed.

minimale_ldz said:
I'm sure you can do it with terminal emulator on rooted device, so no ADB and PC is needed.
Click to expand...
Click to collapse
You are right, if using Terminal on your device, you must be root user and use the same commands but remove the adb shell part.

I got this:
Too many arguments
usage: settings [--user NUM] get namespace key
settings [--user NUM] put namespace key value
settings [--user NUM] delete namespace key
settings [--user NUM] list namespace
namespace' is one of {system, secure, global}, case-insensitive
If '--user NUM' is not given, the operations are performed on the owner user.
Xperia M4 Aqua E2303
EDIT: OK; old method worked for me. Successfuly changed it. New method didn't work.

srdjanLeo said:
I got this:
Too many arguments
usage: settings [--user NUM] get namespace key
settings [--user NUM] put namespace key value
settings [--user NUM] delete namespace key
settings [--user NUM] list namespace
namespace' is one of {system, secure, global}, case-insensitive
If '--user NUM' is not given, the operations are performed on the owner user.
Xperia M4 Aqua E2303
EDIT: OK; old method worked for me. Successfuly changed it. New method didn't work.
Click to expand...
Click to collapse
Which command did you use? Make sure your device name is surrounded by double quotes.

JBNex said:
Which command did you use? Make sure your device name is surrounded by double quotes.
Click to expand...
Click to collapse
Forgot qoutes
I tried with Terminal Emulator and it works So, my mistake.

it needs root ??
I want a way to get google assistant without root or custom recovery on htc 10 ?

elawady.2014 said:
it needs root ??
I want a way to get google assistant without root or custom recovery on htc 10 ?
Click to expand...
Click to collapse
You can't use this to get Google Assistant, but yes it does work without root.

JBNex said:
I'm not sure, but I think the device name must be set to Pixel XL when you set up your device for the first time. This is why full-size Photo backups work on custom "Pixel" ROMs (for non-Pixel devices).
Click to expand...
Click to collapse
.
i had the same question. in fact this is the main reason I wanna change my device model number now my question is... If i wanna change my device model from "oneplus 3" to "Google pixel" i just need to use the command "Pixel XL 9000"? right?
.
and another question... what's with the" Pixel XL 9000"??? can't i just simply use "pixel/ Google pixel" cause, as far as i know, Google also offer full size photo backup for both pixel and pixel xl.

sahed01 said:
.
i had the same question. in fact this is the main reason I wanna change my device model number now my question is... If i wanna change my device model from "oneplus 3" to "Google pixel" i just need to use the command "Pixel XL 9000"? right?
.
and another question... what's with the" Pixel XL 9000"??? can't i just simply use "pixel/ Google pixel" cause, as far as i know, Google also offer full size photo backup for both pixel and pixel xl.
Click to expand...
Click to collapse
Oh that was just an example to show that you could change it to any name you want. Simply Pixel XL would work!

JBNex said:
Oh that was just an example to show that you could change it to any name you want. Simply Pixel XL would work!
Click to expand...
Click to collapse
.
okay. wish me luck! I'm gonna change my device name "oneplus 3" to "Pixel" let's see if full size unlimited photo backup works!

there is no such code as "ro.product.model" in my oneplus 3 device. only "ro.product.brand=oneplus" and "ro.product. manufacturer" what should I do?

Error
Yeah bro
I have changed it using build.prox but now my device is Automatically switching off and on how to solve it.....