I have an LG V30 (LG-H933, Android 8.0.0, no root) and I'm trying to view the log using "adb logcat" from a Mac. The device shows up when I connect it with a USB cable and I can adb shell into, pull files off, etc. However, adb logcat does not show any output. There are no errors or warnings or anything like that. I have tried restarting the device and restarting the adb server but that didn't fix anything. Have any of you run into this issue or know how to fix it?
EvilBoz said:
I have an LG V30 (LG-H933, Android 8.0.0, no root) and I'm trying to view the log using "adb logcat" from a Mac. The device shows up when I connect it with a USB cable and I can adb shell into, pull files off, etc. However, adb logcat does not show any output. There are no errors or warnings or anything like that. I have tried restarting the device and restarting the adb server but that didn't fix anything. Have any of you run into this issue or know how to fix it?
Click to expand...
Click to collapse
What are you trying to see on ADB?
LG has removed most of that ADB/fastboot functionality on North American variants -- which is why you have to Frankenstein Canada H933 to US998 (at least temporarily) for bootloader unlock.
I understand you may not be interested in bootloader unlock and root, but that's probably why you can't see anything on ADB.
I don't know anything about Macs, so that's my best guess.
Sent via open market LG US998 V30/V30+
ChazzMatt said:
What are you trying to see on ADB?
LG has removed most of that ADB/fastboot functionality on North American variants -- which is why you have to Frankenstein Canada H933 to US998 (at least temporarily) for bootloader unlock.
I understand you may not be interested in bootloader unlock and root, but that's probably why you can't see anything on ADB.
I don't know anything about Macs, so that's my best guess.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
I am able to use adb, it's only the logcat command that's not properly working. "adb devices", "adb shell", "adb pull", etc., all work as expected so it's not the case that nothing is working through ADB.
EvilBoz said:
I am able to use adb, it's only the logcat command that's not properly working. "adb devices", "adb shell", "adb pull", etc., all work as expected so it's not the case that nothing is working through ADB.
Click to expand...
Click to collapse
I can't tell by your posts, but u do know how logcat works? You need to start it, then stop it. Then look at the output. There are parameters for starting it which can control what to log (errors, warnings, etc). Usually people start the log, then do the sequence of events (that aren't working and they want to see a log for), then stop it. Then view the log for reasons it's not working.
Not sure if that's any help, but if it does, it's better explained by searching for something like 'android how to do a logcat'.
Cheers
AsItLies said:
I can't tell by your posts, but u do know how logcat works? You need to start it, then stop it. Then look at the output. There are parameters for starting it which can control what to log (errors, warnings, etc). Usually people start the log, then do the sequence of events (that aren't working and they want to see a log for), then stop it. Then view the log for reasons it's not working.
Not sure if that's any help, but if it does, it's better explained by searching for something like 'android how to do a logcat'.
Cheers
Click to expand...
Click to collapse
I appreciate the reply but yes, I do know how logcat works
I was able to get past this issue by using the version that comes with Xamarin Forms.
Non-working:
adb --version
Android Debug Bridge version 1.0.41
Version 29.0.1-5644136
Working:
adb --version
Android Debug Bridge version 1.0.40
Version 4797878
Related
So I've been trying to root my thunderbolt for about a week with no success.
At first I used the method here: http://forum.xda-developers.com/showthread.php?t=1005292
It has continually failed on step 2, tried on different computer also. No luck.
I gave up on rooting it for a few days/
Since the first step went through I am downgraded, running 1.03.605. It's got quite a few bugs and when I try to software update from the phone nothing is found. All I really wanted was to get it to the current firmware to fix connectivity bugs but after searching high and low I still have no idea how to/if it is possible.
I assumed I may have to just root it at this point, so I gave the manual root on theMikMik a shot. While setting up my ABD everything runs smooth until I try to enter commands into abd. I get permissions denied, every time. I've tried looking for an answer to this with no luck. Guide I used found here: http://www.themikmik.com/forums/viewtopic.php?f=66&t=256
So my main question, is there any way to get the latest firmware onto my phone without rooting? I've tried downloading an update, naming it update.zip then updating from bootloader with no luck.
If not, what the hell am I doing wrong that is denying me permission in ABD. I've turned anti-virus off, rebooted etc.
assuming adb is properly set up (drivers working), you've checked Debugging and unchecked Fastboot (under setting->apps->dev), plugged the phone into your computer, and typing "adb devices" acknowledges your phone is connected, and you are in fact on the downgrade as you said you were. Make sure PG05IMG.zip is removed from your sdcard then...
Go here and start at step 5: http://forum.xda-developers.com/showthread.php?t=996616
You were getting permission denied errors with those adb commands on mikmik because you are not rooted yet hence the "rooted evo" under requirements.
Edit:
While that may should work, I believe you could start from the beginning with Step 1 using the link I just posted as well. Just don't flash the old firmware (1.0.3.605 that you currently have) after you go through that for any reason (see: http://forum.xda-developers.com/showthread.php?t=1008824).
Absolute_Zero said:
assuming adb is properly set up (drivers working), you've checked Debugging and unchecked Fastboot (under setting->apps->dev), plugged the phone into your computer, and typing "adb devices" acknowledges your phone is connected, and you are in fact on the downgrade as you said you were. Make sure PG05IMG.zip is removed from your sdcard then...
Go here and start at step 5: http://forum.xda-developers.com/showthread.php?t=996616
You were getting permission denied errors with those adb commands on mikmik because you are not rooted yet hence the "rooted evo" under requirements.
Click to expand...
Click to collapse
*Facepalm*
So I tried what you said from that guide, step 5 failed for me. So I tried from the beginning...still failed.
So, I decided to record it and hopefully you can tell me what I'm doing wrong.
Link: http://www.youtube.com/watch?v=o2AFZEIVIio
Figured that'd be a better way to get the help I need with less reading on your part.
Sorry, I was commuting home from work.
According to the output of "adb shell" you're either already rooted or psneuter has already been run since boot. (note the "#" output instead of "$").
There's no reason to run psneuter to gain permroot again. So once you see that pound sign, start from a two steps down where it says "/data/local/busybox md5sum /data/local/misc.img". IOW, skip that particular "/data/local/psneuter" step.
And I would highly recommend that if you are going to copy/paste, only copy one line at a time to prevent errors.
Off to grab dinner. I'll check back later when I can but hopefully you will be good from here on out.
Edit:
I'm perfectly happy with walking you through it (and I believe you should be fine after this post anyway) but if you still wanted to use that easyroot method that you started with you might want to read this if you haven't http://bit.ly/qsvOkN. I didn't use that easyroot method but it looks like if a step fails, people just run it again until it works. /shrug
I like adb and people should know how to use it anyway.
I have an LG Enlighten (Verizon Wireless), not an LG Optimus Slider (Virgin Mobile), running Android 2.3.4 (Gingerbread). I am in desperate need of a root solution. I have searched the online forums to no avail. I have put the phone up for sale for fear that this device may never be rooted. I am calling on XDA Developers to produce a working root before I ultimately rid myself of this thing. To add, I tried running Android SDK (adb). No go. The instructions threw me even after trying them repeatedly on several different occasions. It could be that my laptop
has no internet access, but I'm not entirely sure.
I really enjoy this phone and have customized it to the point of
exhaustion. All I'm waiting for now is ROOT! Please help ASAP...
Have you attempted to root it? Have you tried Superoneclick, z4root, and/or Gingerbreak?
Re: Have you tried to root it?
Yes, I have. Unfortunately, with no success. Results are as follows:
Z4Root - The end result is my phone takes me back to the previous screen (internet, home, games, music, etc.). It begins the rooting process... acquiring shell root. Then it just sticks for approximately 30 seconds and then closes. I have repeated the process on several occasions in the event that something unusual happened the first time around. But the result is always the same.
Gingerbreak - This app just ultimately hangs, endlessly. Approximately two hours worth before I just quit in frustration. But all online forums claim it should take no more than 15 minutes tops. I should also note that I read Z4Root and Gingerbreak will not work on rooting Android 2.3.4 due to the patching of an exploit. However, I did not update my phone to this firmware. It came preinstalled. And I have not found a procedure for downgrading (sbf'ing) an LG Enlighten.
SuperOneClick - This is the one I'm currently trying still. I can't recall the website, but in addition to SOC, it also requires the use of adb from Android SDK. The problem I'm coming across is the laptop I'm using to perform this action is without internet access (which I've tried feverishly to restore to no avail). And I'm thinking this is what the issue may be, but I'm not entirely sure. The only access I have to the internet currently is on my phone. However, I make a weekly trip to the college library (no restrictions on installing, downloading, etc.). So maybe I can try something there.
For the past month, I've been doing extensive research online trying to find any and all information in regards to resolving this matter. A few sites have blamed Verizon for crippling their Android devices from performing certain functions. For instance, this particular device has no "boot into recovery mode" (which I confirmed with a Verizon tech support person). Had it, I easily could've updated with the .zip file from my SD card (which I've now deleted since it's rendered useless).
I did read today that the next version of SuperOneClick v2.3 (to come out at a later date) will include the option for the forced inclusion of adb debugging/android files which could be the solution to my problems. Possibly.
I apologize if this reply post seems a little long-winded. But I wanted to provide you with all the information I have available in order to better recieve instruction as how to proceed forward. I will continue to try the SuperOneClick in hopes that I will acquire root. But if not, I will rely on the expertise of those in the XDA community.
Thanks,
Centim6
Rooting LG Enlighten
Ok. I found the solution. There is a video on youtube which shows you how to do it. And it works. I now have a rooted device! Finally. Thank you for your assistance.
centim said:
Ok. I found the solution. There is a video on youtube which shows you how to do it. And it works. I now have a rooted device! Finally. Thank you for your assistance.
Click to expand...
Click to collapse
Hi, I too have an LG Enlighten from Verizon wireless. I was just wondering how your root process went? Did the phone work well afterwards? Also do you by any chance have a link to or at least remember the name of the video you watched which helped you to get your phone rooted.
thanks in advance, Angel
centim said:
Ok. I found the solution. There is a video on youtube which shows you how to do it. And it works. I now have a rooted device! Finally. Thank you for your assistance.
Click to expand...
Click to collapse
Can you link to the video?
Sparky42 said:
Can you link to the video?
Click to expand...
Click to collapse
seeing as there is no link, I would say no.
secondly, the video posted and my own research indicates that root was possible only if it was v. 2.3.3. There isn't anything available for 2.3.4.
I have rooted my LG Enlighten which was on Gingerbread 2.3.4. I made a tutorial over at phandroids forums since xda does not let me post links to outside sources. Just google Lg Enlighten root and you will find it in the first or second link. Enjoy.
PS: If you do not believe me I made a video of my phone rooted on youtube. My user name there is the same as xda and I posted pictures at the end of my tutorial. Gingerbread 2.3.4 is fully exploitable on the LG Enlighten.
fsdfgasgfisd said:
I have rooted my LG Enlighten which was on Gingerbread 2.3.4. I made a tutorial over at phandroids forums since xda does not let me post links to outside sources. Just google Lg Enlighten root and you will find it in the first or second link. Enjoy.
PS: If you do not believe me I made a video of my phone rooted on youtube. My user name there is the same as xda and I posted pictures at the end of my tutorial. Gingerbread 2.3.4 is fully exploitable on the LG Enlighten.
Click to expand...
Click to collapse
I think it would a great idea to include which firmware you used this on. I kbow for a fact that it fails on v4 and v5.
And its not that I don't believe you (I do btw) its just the lack of specifics are going to excite someone and they'll leave you a nasty message cause they thought it would work. So, just a heads up:
Android version:
Firmware version:
Sent from my LG-VS700 using xda premium
I can confirm that the new VS700ZV5 update crippled the ability of this phone to root. I just tried the gingebreak and it didnt work. Any way around this?
Same here, android 2.3.4; firmware VS700ZV5.
I haven't been able to get root to work with SoC....
Any chance someone will figure a way around this update?
please reply to root on you tube PLEASE!
centim said:
Ok. I found the solution. There is a video on youtube which shows you how to do it. And it works. I now have a rooted device! Finally. Thank you for your assistance.
Click to expand...
Click to collapse
Extremely frustrated and hoping you will share this link. I to have tried everything to root my Enlighten to no avail and would appreciate your help more than I can explain! Please! Thank you and congats!
I had my phone rooted, then verizon put out an update, and now I can't root it. I think we're screwed until sombody figures out a new method.
Model: LGVS700
Firmware: VS700ZV5
im not sure if this will help but here, i found this claiming to be able to root the phone.
First, you need the file hboot_2.xx_soff-V8.9.zip, download it.
Unzip it into c:evoroot on your pc.
Second, put your LG Enlighten into development mode by
going to Settings->Applications->Development and turn USB
debugging on.
Third, connect your LG Enlighten to your computer and set
your USB to Just charge.
Fourth, if you get errors with drivers, install their HTC drivers.
(You can also install HTC Sync, but it is bulky!)
Fifth, open up a command prompt by typing cmd.
Sixth, type the following commands: (Or copy and paste,
easier!)
Code:
cd evoroot
adb push root/unrevoked-forever.zip /sdcard/
adb push root/mtd-eng.img /sdcard/
adb push pc36img/PC36IMG-ENG.zip /sdcard/PC36IMG.zip
adb push pc36img/PC36IMG-MR.zip /sdcard/PC36IMG-MR.zip
adb push root/flash_image /data/local/
adb -d install -r root/z4root.apk
Seventh, go to your phone and launch Z4Root app. Then select
temp root and wait until its done.
Eighth,go back to command prompt and type:
Code:
adb shell
su
If you get a pound(#) sign, that means you have temp root,
which just gives you temporary root so we can now install
permanent root.
ninth, go back to command prompt and type the following:
Code:
chmod 0755 /data/local/flash_image
./data/local/flash_image misc /sdcard/mtd-eng.img
sync
And reboot to bootloader mode by typing:
Code:
reboot bootloader
When bootloader mode starts up, it will look for PC36IMG.zip
and after about 3 minutes ask you if you want to install
PC36IMG.zip.
Say Yes by hitting the volume up button, it should now install
the new zip file, should take about 10 minutes. Go grabs some
coffee and come back.
Eleventh, reboot when its done by hitting the volume up
button.
It will reboot into the OS and we dont want that so takes the
battery out and puts it back in it. Then go back to the
bootloader by hitting the power button while holding down
the volume down button.
Choose Bootloader and wait until you get the triangle sign and
type:
Code:
adb push recovery /
adb shell busybox Cinstall /sbin
adb shell nohup /sbin/recovery
&
Go back to your LG Enlighten and you should see green
menus.
Choose install zip from sd card and choose unrevoked-
forever.zip
After that installs, Choose MS-USB
Go to your computer and delete PC36IMG.zip, then rename
PC36IMG-MR.zip to PC36IMG.zip.
Then power off your LG Enlighten, power back on by pressing
Power Button while holding down the Volume Down button,
this should get you back into bootloader mode.
Simply wait and when it asks to install the update, hit the
Volume Up button.
then reboot your LG Enlighten, your device should now be
rooted with Recovery menu then you can flash new ROMs for
LG Enlighten.
LG Enlighten root
I have lg enlighten running 2.3.4 and it is rooted with super user and rom toolbox working. I used POOT.APK which can be found on google. It worked well and everything went smooth. It is a simple and easy to use application. (You can use either SU or SSU)
any way to update it to ics? i have one
Hello guys i ported rom 4 my device and i have bootloop. When in cmd type "adb devices" i have message 4 verifing. But when i type "adb logcat", "adb logcat -f logcat.txt" or etc. i have message -waiting for device-. I tried with AIO Logcat but, i get this : http://prntscr.com/1rp25l
with adb logcat i gotta this http://prntscr.com/1rp2h6
Any help ? Thanks in advance.
As you can see, when you type adb devices, your device appears offline. Maybe this is caused by your ROM, maybe not, but you need to solve it first (I dunno how to do it, sorry).
Maybe you can find the problem with the Dalvik Debug Monitor (DDMs). It's part of the Android SDK.
See this thread:
http://forum.xda-developers.com/showthread.php?t=2304122
Thanks but not working "DDM"
As long you keep getting offline when you type adb devices, anything will work. As I said before, you need to fix that problem first.
I don't know how to do that !
Just a quick question in case anyone knows:
At my place of work we have an old nexus 9 that's in pretty much perfect condition, but it was originally used in demo mode to for the display and as such, has been stuck in demo mode since coming off display.
One of the technicians claims he had a go at removing the demo mode a couple of months ago but with no success, I presume he tried at least a factory reset on it.
I'm not sure exactly what methods he tried but I was wondering if anyone here happened to know if this was possible?
It's basically sitting in a corner unused so worth a crack.
M1kesky said:
Just a quick question in case anyone knows:
At my place of work we have an old nexus 9 that's in pretty much perfect condition, but it was originally used in demo mode to for the display and as such, has been stuck in demo mode since coming off display.
One of the technicians claims he had a go at removing the demo mode a couple of months ago but with no success, I presume he tried at least a factory reset on it.
I'm not sure exactly what methods he tried but I was wondering if anyone here happened to know if this was possible?
It's basically sitting in a corner unused so worth a crack.
Click to expand...
Click to collapse
Is demo mode enabled in the system UI tuner under settings?
I would suggest flashing the latest factory images in fastboot.
cam30era said:
I would suggest flashing the latest factory images in fastboot.
Click to expand...
Click to collapse
Would be a great idea, except I'm not sure you can get into Developer Options to enable Allow OEM Unlock while in Demo Mode, which would make unlocking the bootloader (which has to be done before fastboot can function properly) quite difficult.
borxnx said:
Would be a great idea, except I'm not sure you can get into Developer Options to enable Allow OEM Unlock while in Demo Mode, which would make unlocking the bootloader (which has to be done before fastboot can function properly) quite difficult.
Click to expand...
Click to collapse
You're right, in that I'm not sure either (about enabling Developer Options). But it's worth a try.
M1kesky said:
Just a quick question in case anyone knows:
At my place of work we have an old nexus 9 that's in pretty much perfect condition, but it was originally used in demo mode to for the display and as such, has been stuck in demo mode since coming off display.
One of the technicians claims he had a go at removing the demo mode a couple of months ago but with no success, I presume he tried at least a factory reset on it.
I'm not sure exactly what methods he tried but I was wondering if anyone here happened to know if this was possible?
It's basically sitting in a corner unused so worth a crack.
Click to expand...
Click to collapse
This ADB command should do the trick:
Code:
adb shell am broadcast -a com.android.systemui.demo -e command exit
Edit:
In case that sounded overwhelming and/or to help others with this issue, here's more more info about how to do that.
You must first install the ADB drivers to your PC. I suggest using Minimal ADB rather than installing the entire Android SDK, then use Command Prompt to navigate to your ADB directory (the folder where your ADB application is installed. Use the cd command to change directories [get it, cd?] to the complete filepath to the folder containing your ADB program in Windows. I put my Minimal ADB folder that I extracted from the zip directly onto the C:\ drive so the filepath is "C:\adb". I open my command prompt and type "cd C:\adb" and it's ready to roll. Super easy), once it says C:\adb> or whatever your filepath is, copy the command code above exactly into the prompt and press Enter.
To ensure your device is properly connected, after using "cd C:\adb" to get to your ADB application, run the command "adb devices". The daemon will start and it will either list your device number if it's successfully connected or will remain blank and go back to the "C:\adb>" prompt if it's not connected properly.
There may be a notification on the device when you try to connect ADB, but i may be getting this confused with ADB Debugging. If you see a notification pop up with warnings or aging your precision to connect to your PC just click the "chill out bro it's cool, I got this" button.
I hope you get it up and running properly and can enjoy your Nexus 9!
Sent from my XT1575 using Tapatalk
Thanks guys, I'm in work tomorrow so i'll take my laptop in and give it a try, thanks for all these suggestions!
I'll tell you the results afterwards.
Hi!
I am one of many who are trying to solve the problem with updates for the American version of LG V60 from AT&T operator outside the USA.
My experience comes from smartphones from samsung s6 active, then we manually with the help of luck found a link for updates that could be installed manually from recovery.
Now I have a V60 and I thought: and why shouldn't this method work with LG?
We need the help of one v60 owner who has android 10 of any version. The task is simple - to find out the URL through logcat.
For the result, just follow this instruction:
1. When you get the OTA update notification, do not download the update. Also, and do not reboot your phone.
2. Setup ADB and Fastboot environment on your PC and enable USB debugging on your Android device. (settings>development>enable USB debugging)
3. Now plug in your device to the PC using a USB cable. (not a front port)
4. Now open the command prompt or terminal by holding the shift key on your PC and press the right mouse button. Alternatively, go to start>accessories>cmd or type cmd in the search under the start menu.
5. Now issue the following command in the cmd window: adb logcat
6. Once done, it should display a whole bunch of text below the command. It may take some time to get the full logcat as it will be a long text. If it takes long, you can disconnect the device from PC. The
7. Once you get the full logcat, copy and paste everything from the terminal into a notebook text document.
8. You will certainly find the OTA URL for your device. Check out the image below to see how the URL looks like.
9. Now that you have the OTA URL, you can start with downloading the OTA.
10. Now you can reboot your phone and install the update.
Perhaps all this is a waste of time and in the near future someone will unlock the bootloader. I believe in the best, but I live for today.
I don't think anyone is really to help. It's sad how development community is dying. My stick on Android 10. I guess there is not hope for ATT users so I'm gonna sell my att and get a different model of v60 aside the att
AT&T ota updates are shipped through Google, not LG themselves, so you won't receive any updates that aren't for your device. If you're hoping to sideload an OTA, it may actually work, but I'm not sure anyone's tried it that way yet.