This is just a little guide I wanted to make for those that dont know how to get logcats if you're running windows 7
So theres 2 ways to get a logcat from your phone.
1- ADB
or
2- Logcat apps in the playstore
https://play.google.com/store/search?q=logcat&c=apps
Method #1
if you don't have the HTC drivers or ADB set up you can go here to get them.
http://forum.xda-developers.com/showthread.php?p=24717512 thanks blue6IX
Main things to look for in a logcat file are:
E/ errorr
F/ Fatal
V/ Verbose (lowest priority)
D/ Debug
I/ Info (default priority)
W/ Warning
S/ Silent (highest priority, on which nothing is ever printed)
E/ stands for error and F/ means Fatal. These are the two main things that will break a system.
1- Go to the folder where you have ADB set up, this is where mine is.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2- Hold shift and right click the folder and select “open command window here”. It will look like this
3- Next type “ADB logcat” and Press enter
When your done getting your logcat hit “ctrl c” This will stop the logging and you will be able to type in the next command. *type "adb logcat -d > logcat.txt” *only if you typed "adb logcat" This will create a file named "logcat.txt" in your current directory where you opened your command prompt.
**You can also type "adb logcat -v long > name of problem.txt"
You can rename "name of problem" to anything you want this just names the logcat file
[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.i think thiis way makes it look neater and it shows timestamp.]
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.
This will create a file named "" in your current directory where you opened your command prompt.
Running adb logcat without any options will display the contents of LogCat in your terminal window.
From there you can copy and paste whats in the txt file to pastebin and post the link that pastebin gives you
Method #2
If my guide didn't help you There is one more way to get a logcat from your phone
https://play.google.com/store/search?q=logcat&c=apps
alogcat
https://play.google.com/store/apps/details?id=org.jtb.alogcat
pastebin
https://play.google.com/store/apps/details?id=com.jmz.pastedroidapp
Method #3
Logcat tool (i did not try this yet, can someone confirm that it works)
http://forum.xda-developers.com/showthread.php?t=1747544 thanks FuzzyMeep Two
when i run a logcat i just open terminal to where my sdk is= [email protected] ~ $ cd android/android/platform-tools then i run adb logcat > logcatname.txt and hit enter and let the logcat run. once im done i hit Ctrl c and it stops and inside platform-tools is a txt file for that one whole logcat.
just chipping in my 2 cents worth.
Glad you made this tutorial here so people who want to aid in the development of the ROMs currently under development CAN help now, thanks.
Sticky?
Sent from my RubiX ICS Infused using Tapatalk 2
So this is the way your supposed get a logcat? Mine usually gets mailed in a print out via UPS nice visual guide
How do you know when the logcat is done?
When I did it a couple times before, it just kept running and running. It would have went for hours if I didn't CTRL+C it.
CZ Eddie said:
How do you know when the logcat is done?
When I did it a couple times before, it just kept running and running. It would have went for hours if I didn't CTRL+C it.
Click to expand...
Click to collapse
it dosent finish, It'll keep going as long the phone is connected to your pc, everything that happens on the phone is shown on the logcat so as long as the logcat is running and the phone is powered on and connected things will always show in the command prompt. basically logcat will run until you end the session
ac3theone said:
it dosent finish, It'll keep going as long the phone is connected to your pc, everything that happens on the phone is shown on the logcat so as long as the logcat is running and the phone is powered on and connected things will always show in the command prompt. basically logcat will run until you end the session
Click to expand...
Click to collapse
I guess that is my question. How long should I leave it running?
CZ Eddie said:
I guess that is my question. How long should I leave it running?
Click to expand...
Click to collapse
you should run it when your having a problem, for ex if you have wifi problems run logact and type "adb logcat :WifiStateMachine:E" when you do that itll only show errors wiith wifi. and you dont have to leav it running, just long enough the the error is outputted on the log
ac3theone said:
you dont have to leav it running, just long enough the the error is outputted on the log
Click to expand...
Click to collapse
How do I know how long is long enough?
Are we talking 5 seconds? 5 minutes? 5 hours?
not long id say about 2min since the files and get big quickly
Related
Hi guys,
Just got my SNS and have been lurking on here trying to figure out how to ROOT it. There are plenty of guides, and I was using this one
http://forum.xda-developers.com/showthread.php?t=895545
For some reason, and at risk of sounding like an idiiot, SDK doesnt have fastboot (or I cant find it) and I cant even use Command Prompt to execute any commands such as "ADB Devices". It also wont let me change the driver to Android Bootloader Interface in Device Manager.
I basically need to start from scratch and Im tearing my hair out trying to figure it out. Sorry about the FRAT
Cheers
Bertrum said:
Hi guys,
Just got my SNS and have been lurking on here trying to figure out how to ROOT it. There are plenty of guides, and I was using this one
http://forum.xda-developers.com/showthread.php?t=895545
For some reason, and at risk of sounding like an idiiot, SDK doesnt have fastboot (or I cant find it) and I cant even use Command Prompt to execute any commands such as "ADB Devices". It also wont let me change the driver to Android Bootloader Interface in Device Manager.
I basically need to start from scratch and Im tearing my hair out trying to figure it out. Sorry about the FRAT
Cheers
Click to expand...
Click to collapse
http://jaxov.com/2011/02/how-to-root-android-2-3-3-gingerbread-on-nexus-s/
I liked this guide. First time rooting.
On command prompt, you have to go to the Android\android-sdk\tools folder then execute those fastboot command.
Your command prompt probably says C:\Users\Your User Name.. [I have Windows 7]
Type 'cd..' (without ' ') until your line says C:\>
Then type the following cd Program Files\Android\android-sdk\tools
It could be Program Files (x86) not Program Files.. depends which bit you have. You can type those fastboot command from there.
Thanks for that info. Worked a treat right upto the part where I have to put the clockwork image on. command prompt keeps saying it cannot load it. Any ideas?
Bertrum said:
Thanks for that info. Worked a treat right upto the part where I have to put the clockwork image on. command prompt keeps saying it cannot load it. Any ideas?
Click to expand...
Click to collapse
Did you download ClockWorkMod img and paste it into android-sdk\tools folder? You can do that my opening My Computer folder -> C:\ -> Program Files -> Android -> android-sdk -> tools folder.
Then open command prompt and type like that. I just did the first line for you.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yours could be Program Files, not Program Files (x86) though. I downloaded 32-bit version accidentally and I didn't wanted to do it over.
After that you use your Nexus S to boot into bootloader [which the instruction says] and continue on.
thanks all sorted now. now to reinstall all my data as i didnt root straight away. ha!
Thanks for all your help.
Bertrum said:
thanks all sorted now. now to reinstall all my data as i didnt root straight away. ha!
Thanks for all your help.
Click to expand...
Click to collapse
I'm glad I helped. I had hard time rooting yesterday but it's all good now
I finished everything last night. All unlocked and rooted. Also running CM7 rc2 with the n14 kernel.
Its soo fast compared to my old blackberry and my friends galaxy.
Many thanks to the people who worked on the roms and kernels. Your knowledge astounds me.
Sent from my Nexus S using XDA Premium App
HOW-TO Fix **ADB is not recognized in the CMD**
Navigate to & Left_Click on Start >
Right_Click on Computer >
Left_Click on Advance System Settings >
Left_Click on Environment Variables >
Left_Click on New ( User Variables ) >
Variables Name: ADB ( Or anything you want )
Variables Value: ;C:\SDK\tools ( Just like this, This is the Path of my adb.exe )
You must put a ; in front of ;C:\ ( adb Path goes here / Variables Value: )
That's it.. You now have set up adb to work Global via cmd prompt on win7
~Eugene
eugene373 said:
HOW-TO Fix **ADB is not recognized in the CMD**
Navigate to & Left_Click on Start >
Right_Click on Computer >
Left_Click on Advance System Settings >
Left_Click on Environment Variables >
Left_Click on New ( User Variables ) >
Variables Name: ADB ( Or anything you want )
Variables Value: ;C:\SDK\tools ( Just like this, This is the Path of my adb.exe )
You must put a ; in front of ;C:\ ( adb Path goes here / Variables Value: )
That's it.. You now have set up adb to work Global via cmd prompt on win7
~Eugene
Click to expand...
Click to collapse
That should help with a lot of the issues I see being posted, not only here but on many Threads. Simple path statement 101
Better: Chose "Path" in "Systemvariables" and put it at the end of this line, i.e. like this: ";C:\android\platform-tools;C:\android\tools". Because then it'll even work if u run the cmd as administrator, which won't work if you do it as described above. Atleast its been the way on my W7 Ultimate 64
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi,
another way (and very useful for other reasons) is to change registry like this:
Code:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Folder\shell\Command Prompt]
@="open cmd here"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Folder\shell\Command Prompt\Command]
@="cmd.exe /k pushd %L"
Afterwards you are - by right-clicking the adb-folder - directly in the right folder.
Don´t know if you have to restart, i´m using it just a long time.
Greets
idephili
or just put the tools folder and adb binarys in C:\Windows or C:\Widnows\System32 ;-)
done
I know this is of topic but thanks Eugene for all of your contributions
Sent from my HTC Sensation 4G using XDA Premium App
Eugene373, I am so happy you're devving on the Sensation! Thanks for the ADB how-to...it really helped! Will you continue to develop and make ROM's for this device?
Alternatively you can also copy the ADB and Fastboot.exe files over to System32 or SysWOW64 folders and they work fine as well.
as google shows up this thread here my two cents...
the mentioned methods don't work for me nor anyone else('s computer) running windows 7 professional 64 bit i know. here's what in fact works perfectly on any computer i tried it on:
copy the path to your adb.exe wherever it is, put a semicolon in front of the path and attach it to the existing entry in the PATH variable. no matter if you add it as an user oder system variable. last one is only to recommend as you're dealing with multiple users which all need to access adb via cmd
is there a way to convert the twrp file backup on my pc to get it back on to my phone to install the backup everytime i try to put it back on my phone via adb it errors out and im stuck at this point ive been at this for over 10 hours just trying to restore my backup i have the backup file on the pc and ive backed it up earlier but now it errors there has to be a way to get this backup back onto my phone in a way that it will recognize it and install it please help lol im familiar with custom roms and the like not a expert but i kinda know what im doing and ive loaded custom roms on many phones in the past with no issues but this one is proving to be a real pain using a note 4 n910t
for more info i was trying to install petbede's rom and i managed to get to the reboot stage and he states it could take anywhere from 7-10 mins on average for it to boot up but mine was going on 20 mins plus and was getting really hot so i pulled the plug and as long as ive been trying to do this in one sitting i just want my backup installed and to be done with it for a few days untill i can muster the courage to try it again but this time i will be backing up on a seperate sd card that i can just pop into the phone to restore from since the pc copy is not playing nice with me
im sure most people wont need adb at school but some people might not know how and want to use adb at school if needed.
so at school (high school for myself) we don't have admin rights so we are unable to access cmd which is "sort of" needed for adb here is a quick guide with my very little knowledge.
1.How to get CMD:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
as shown above if you where to try to open the admin has disabled it. now what your going to want to do is this
right click on desktop and open a new text document. (it can be notepad or another program not sure if word will work with it)
open it and type this into it:
@ECHO off
command
comand.com
pause
then hit file, save as: Start.bat to the desktop as show in this image:
now on your desktop you should see a new file called start with some cogs on the icon and if you open it your get our honorable CMD.exe! (note, they disabled it for a reason dont be messin with school computers)
2.How to get ADB:
now the process to do this as well is not very hard, now we all know adb is a few hundred megabytes and we will never be able to
download it in time. we don't need all that sdk crap we just want to good ol adb. download the zip from this users thread here:
Be sure to give her a Thanks! : http://forum.xda-developers.com/showthread.php?t=926486
now your going to want to unzip it and when you try to open adb:
Dang it school why you do this
Now after your done sobbing its a pretty easy and simple fix, pretty much did what you did last time. instead, right click on RunMe that's in the miniADB folder and hit edit. (if you didn't extract it, it wont let you edit it) and type in what you typed in last time only deleting the cmd.exe in the line, you can keep it there but when you run RunMe it will say its disabled but when you hit a key on your keyboard, it will get rid of that.
there we go, now that we have adb start hacking away! happy Flashing!
Mine!
Trozzul said:
im sure most people wont need adb at school but some people might not know how and want to use adb at school if needed.
so at school (high school for myself) we don't have admin rights so we are unable to access cmd which is "sort of" needed for adb here is a quick guide with my very little knowledge.
1.How to get CMD:
as shown above if you where to try to open the admin has disabled it. now what your going to want to do is this
right click on desktop and open a new text document. (it can be notepad or another program not sure if word will work with it)
open it and type this into it:
@ECHO off
command
comand.com
pause
then hit file, save as: Start.bat to the desktop as show in this image:
now on your desktop you should see a new file called start with some cogs on the icon and if you open it your get our honorable CMD.exe! (note, they disabled it for a reason dont be messin with school computers)
2.How to get ADB:
now the process to do this as well is not very hard, now we all know adb is a few hundred megabytes and we will never be able to
download it in time. we don't need all that sdk crap we just want to good ol adb. download the zip from this users thread here:
Be sure to give her a Thanks! : http://forum.xda-developers.com/showthread.php?t=926486
now your going to want to unzip it and when you try to open adb:
Dang it school why you do this
Now after your done sobbing its a pretty easy and simple fix, pretty much did what you did last time. instead, right click on RunMe that's in the miniADB folder and hit edit. (if you didn't extract it, it wont let you edit it) and type in what you typed in last time only deleting the cmd.exe in the line, you can keep it there but when you run RunMe it will say its disabled but when you hit a key on your keyboard, it will get rid of that.
there we go, now that we have adb start hacking away! happy Flashing!
Click to expand...
Click to collapse
Very nice thread. I am willing to use it to install ADB. I really think its very important.Thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hey guys,since VanirAOSP is the best ROM ever,i wanted to make a Discussion thread here,because the Development thread has low activity and we shouldn't fill it with spam.
WHAT TO DISCUSS HERE:
-Bugs
-Features
-Development
-Other Things related to Vanir
-The original development thread can be found here
Personally,i think that Vanir is pretty underrated here on Moto G section,and i think that more people could try it and say their thoughts,because i've tried many many ROM's through my history here on XDA,and i've never been so satisfied. The ROM is as it's title says; Clean,Fast and organized. But that's just me and my two cents, Try it yourself and say your thoughts here!
The bug posting tutorial is the post below,and connecting your phone through ADB is two posts below,if you need something else explained don't hesitate to ask!
Repost:::
[SIZE="+2"]How to report bugs, the proper way ![/SIZE]
http://therealmofu.com/wp/?p=644
Credit:: by TheRealMofu
Credits:
Indirect for his guide
FuzzyMeep Two for his Windows Logcat Tool
B][SIZE="+2"]These are the options for reporting a bug:[/SIZE][/B]
[SIZE="+1"]Section 1 | Logcat:[/SIZE]
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
http://pastebin.com/
http://logcat.us/
http://paste.ubuntu.com/
and provide the link in the thread/post.
It’s really that simple!
For Windows users i found an self explaining noob friendly program called Windows Logcat tool 4.0
[SIZE="+1"]Section 2 | Dmesg:[/SIZE]
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!
[SIZE="+1"]Section 3 | last_kmsg:[/SIZE]
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.
And hhp_211 posted this in his thread,and i copied it from him,i hope he won't mind,so thanks @hhp_211
[SIZE="+2"]
Connecting your device through adb on Windows/Ubuntu:[/SIZE]
[SIZE="+1"]Windows:[/SIZE]
On your PC you need to be logged in as an administrator for doin this and make sure that you activated “USB Debugging” in Settings/Developer Options on your phone !!!
Connect your phone with the USB cable to the PC and select MTP mode
Open the Windows command prompt, which you also can open through pressing Win + R on your keyboard
Now type:
Code:
cmd
Now change into the folder you installed adb, for example:
cd c:\adb
Now were we are in the correct folder, type:
Code:
adb
Now you see a lot of commands appering, and when done, type:
Code:
adb devices
and your phone (Device-ID) should be listed in there, that’s it
[SIZE="+1"]Ubuntu:[/SIZE]
Make sure that you activated “USB Debugging” in Settings/Developer Options on your phone !!!
Connect your phone with the USB cable to the PC and select MTP mode
In terminal type:
Code:
cd (TOOLS_PATH)/android-tools
Then issue the following:
Code:
./adb devices
That’s it
Again,thanks to @hhp_211
Reserved 3 to be shure.
Being used to the back button on the right side and the recent items on the left i noticed there is no option to set that in the settings menu.
Or at least i could not find it.....
You will need ADB on the PC/Laptop and connect the phone to it.
Download of ADB can be found here: https://forum.xda-developers.com/showthread.php?t=2588979
So i found a nice post https://forum.xda-developers.com/pixel-xl/help/swap-recent-button-oreo-t3687721 that enables it.
NO ROOT required, just enable ADB in developer settings.
Then start ADB shell
Enter this command and you are done.
settings put secure sysui_nav_bar "space,recent;home;back,space"
All happy now.
Thanks !
Do you know if we can change long press action with this method ?
rqdb said:
Thanks !
Do you know if we can change long press action with this method ?
Click to expand...
Click to collapse
If we can find the command for it i suppose we can. Not sure how we can find this.
Verstuurd vanaf mijn Nokia 7 plus met Tapatalk
Thanks for sharing and one stupid question....OTA still work after ADB shell?
supremeee said:
Thanks for sharing and one stupid question....OTA still work after ADB shell?
Click to expand...
Click to collapse
It should. No modification is done to the file system.
Verstuurd vanaf mijn Nokia 7 plus met Tapatalk
Brotuck said:
Then start ADB shell
Enter this command and you are done.
settings put secure sysui_nav_bar "space,recent;home;back,space"
All happy now.
Click to expand...
Click to collapse
Doing this you'll loose the keyboard switching icon that appears when you have multiple virtual keyboards. The command including this icon is:
settings put secure sysui_nav_bar "space,recent;home;back,menu_ime"
I'm having difficulties getting ADB to work(authorization popup does not appear). Any ideas?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
:edit:
Any chance this feature is hidden in the global built (albeit hidden) and can be pulled out using adb?
Answer by Nokia assistance:
Thank you for contacting Nokia Mobile Care and your interest in Nokia mobile devices.
Regarding your request, we would like to inform you that this option does not exist.
We remain at your disposal if you have other questions or need our help.
Does the switch remain after rebooting the phone ? Or do i have to do this every time i reboot ?
Inpain said:
Does the switch remain after rebooting the phone ? Or do i have to do this every time i reboot ?
Click to expand...
Click to collapse
The change remains after reboot
After put in the command through adb shell, with Nokia 7 plus attached to the pc, I got a system ui error, phone does start up, but after that I got a black screen only , had to do a hard reset, lost all data.
riseandshine32 said:
After put in the command through adb shell, with Nokia 7 plus attached to the pc, I got a system ui error, phone does start up, but after that I got a black screen only , had to do a hard reset, lost all data.
Click to expand...
Click to collapse
Same
OC-Freak said:
Same
Click to expand...
Click to collapse
Working fine here, on Build number: 00WW_2_22A (May security patch build).
Did you type in the commands correctly (semicolons and commas) ?
Just did the command again on a fresh installed version with the May patches and all is fine.
Please make sure you type exact the correct syntax.
I always do a copy / paste on my laptop from the text on a adb shell
Excellent mate. worked like a charm on my Nokia 7 plus with latest system update
Nokia 7 Plus
Hey, I got the same phone like you!
But my phone is not in the devices list (adb devices)
Please help
Hello, I tried this but I'm always getting this error in adb command line:
C:\adb>settings put secure sysui_nav_bar "space,recent;home;back,menu_ime"
'settings' is not recognized as an internal or external command, operable program or batch file.
The underlined text I copy pasted it from this xda thread. When I do adb devices I see my device in the list, its the only android device thats connected to my computer. I don't have an idea how to fix it.
After some further experimenting I've gotting it done
In the adb command line you type folllowing command
1. adb devices
2. adb shell
3. settings put secure sysui_nav_bar "space,recent;home;back,menu_ime"
4. that's all
Wuter said:
Hello, I tried this but I'm always getting this error in adb command line:
C:\adb>settings put secure sysui_nav_bar "space,recent;home;back,menu_ime"
'settings' is not recognized as an internal or external command, operable program or batch file.
The underlined text I copy pasted it from this xda thread. When I do adb devices I see my device in the list, its the only android device thats connected to my computer. I don't have an idea how to fix it.
After some further experimenting I've gotting it done
In the adb command line you type folllowing command
1. adb devices
2. adb shell
3. settings put secure sysui_nav_bar "space,recent;home;back,menu_ime"
4. that's all
Click to expand...
Click to collapse
After Step 2 press ENTER
then the command prompt should enter a shell (you will see b2n_sprout:/)
in the shell you paste the command
See attached screenshot
Its there a way to change the icons to vanilla?