Help how can i fix my g2 mini, while im playing games on my phone suddenly my phone restart automatically then it stuck in lg logo like bootloop. I try to flash stock firmware but it keeps looping on lg logo. What do you think is the problem guys? Is it in hardware?
Have you tried a hard reset?
( It will delete all the data on your phone )
Yah i try nothing happen it keeps looping
Try a CSE Flash on the flash tool.
Vagelis1608 said:
Try a CSE Flash on the flash tool.
Click to expand...
Click to collapse
Il already try it my phone open then when i charge my phone it will bootloop again and again
eicrag123 said:
Il already try it my phone open then when i charge my phone it will bootloop again and again
Click to expand...
Click to collapse
How long have you let it bootloop?
Vagelis1608 said:
How long have you let it bootloop?
Click to expand...
Click to collapse
If the phone start bootloop it will not stop the looping you need to remove the battery to turn off. Sometimes if the phone have rest a longer the phone will open then if i charge it or restart it will bootloop again
eicrag123 said:
If the phone start bootloop it will not stop the looping you need to remove the battery to turn off. Sometimes if the phone have rest a longer the phone will open then if i charge it or restart it will bootloop again
Click to expand...
Click to collapse
Grab a log with adb ( adb wait-for-device shell logcat >> logcat.log ) and give it to me.
Use Google to set up adb and use LG's universal drivers.
You have to enable adb on the device and grant permission to your PC. Do this while booted.
Vagelis1608 said:
Grab a log with adb ( adb wait-for-device shell logcat >> logcat.log ) and give it to me.
Use Google to set up adb and use LG's universal drivers.
You have to enable adb on the device and grant permission to your PC. Do this while booted.
Click to expand...
Click to collapse
Ok, how can i get the logcat.log? Google drivers? Can you give me steps how to do it
eicrag123 said:
Ok, how can i get the logcat.log? Google drivers? Can you give me steps how to do it
Click to expand...
Click to collapse
There are many tutorials online on how to set up adb. Just Google something like "how to set up adb".
For device drivers use LG's universal drivers.
Related
I'm trying my hand at porting a ROM to my device (S4 HTC One X/XL, Evita) and I've gotten as far as the bootscreen, but it hangs there (with the bootanim still running). I'd like to take a look at what's happened on the device, but I can't seem to use adb with it at this point. I've made sure drivers are installed and used multiple USB ports. ADB works in recovery and fastboot works in fastboot, but adb returns Offline when I run adb devices while the phone is sitting at the bootscreen.
Found this on StackExchange: http://android.stackexchange.com/que...-for-debugging
According to some of the replies, it's possible to use adb at boot, so I'm not sure why adb returns offline. I tried running adb logcat while the phone is off and letting it boot, but adb never establishes a connection to the phone. Not sure why it can't. Hopefully it's not another adb driver issue. I've already spent a ton of time getting adb working with this phone while booted/in recovery.
Try this it should capture a logcat of the phone booting up, power off the phone while still connected to the usb and enter the following it should say - waiting for device -
Power on the phone then cross your fingers if all goes well you should capture the logcat to bootlog.txt file in your temp directory.
Code:
adb -d logcat>c:\temp\bootlog.txt
Sent from my PACman GT-i9100 using Xparent ICS Tapatalk 2
AuSSiELaMbChOpS said:
Try this it should capture a logcat of the phone booting up, power off the phone while still connected to the usb and enter the following it should say - waiting for device -
Click to expand...
Click to collapse
Protogon said:
I tried running adb logcat while the phone is off and letting it boot, but adb never establishes a connection to the phone. Not sure why it can't. Hopefully it's not another adb driver issue. I've already spent a ton of time getting adb working with this phone while booted/in recovery.
Click to expand...
Click to collapse
The ROM is 4.2.1-based, so if the USB Debug Whitelist was implemented in that version, that might be the problem. Running adb logcat from power off with a ROM that boots fine reveals that adb starts pretty much as soon as the bootscreen comes on and logcat should start spitting out data just as quickly.
If it's not a whitelist issue, something is preventing even adb from starting on the phone.
This is a problem I too have run into while porting a ROM to my GiONEE Dream D1 (MTK 6589) Device. Have you had any luck?
Wish there was a field in build.prop to say "boot with verbose remote logging"
RickyGoldsmith said:
This is a problem I too have run into while porting a ROM to my GiONEE Dream D1 (MTK 6589) Device. Have you had any luck?
Wish there was a field in build.prop to say "boot with verbose remote logging"
Click to expand...
Click to collapse
Replying to self.
You need to modify the init shipped on your OS and instruct it to start adbd asap.
Protogon said:
I've gotten as far as the bootscreen, but it hangs there (with the bootanim still running). I'd like to take a look at what's happened on the device, but I can't seem to use adb with it at this point.
Click to expand...
Click to collapse
You can try to reboot into a working system right after (e.g. the recovery) and retrieve the last kernel boot messages by:
adb shell cat /proc/last_kmsg > last_kmsg
and then see whether you can figure out what happens by reading this log file
hello friends i have lg optimus vu F100L,my mobile is not going into recovery mode by pressing volume- & power button, when i use this method it simply switch, gingerbread is installed in it and i want to update that but due to this unable to do that. help me please.
sami789 said:
hello friends i have lg optimus vu F100L,my mobile is not going into recovery mode by pressing volume- & power button, when i use this method it simply switch, gingerbread is installed in it and i want to update that but due to this unable to do that. help me please.
Click to expand...
Click to collapse
Does you phone boot up fully into android? If it does you can access recovery mode by running the following adb command:
Code:
adb reboot recovery
Let me know if you still have question's I'll be happy to answer them.
shimp208 said:
Does you phone boot up fully into android? If it does you can access recovery mode by running the following adb command:
Code:
adb reboot recovery
Let me know if you still have question's I'll be happy to answer them.
Click to expand...
Click to collapse
my phone is not rooted, i check it on root checker app,where it is saying your phone is not rooted, i was trying to root that but many of them are saying go to the recovery mode,but am unable to do that,
sami789 said:
my phone is not rooted, i check it on root checker app,where it is saying your phone is not rooted, i was trying to root that but many of them are saying go to the recovery mode,but am unable to do that,
Click to expand...
Click to collapse
Regardless of whether your device is rooted or not you can access recovery by booting the phone normally into the Android OS, and running the ADB command "adb reboot recovery" using ADB on your computer to boot your phone into recovery mode.
shimp208 said:
Regardless of whether your device is rooted or not you can access recovery by booting the phone normally into the Android OS, and running the ADB command "adb reboot recovery" using ADB on your computer to boot your phone into recovery mode.
Click to expand...
Click to collapse
thanks buddy now i just need a english jeally beam rom for lg vu f100l, if you have some link then it ll be great.
sami789 said:
thanks buddy now i just need a english jeally beam rom for lg vu f100l, if you have some link then it ll be great.
Click to expand...
Click to collapse
This is the only info I could find on an English Jelly Bean ROM for your device, I warn you the site seems quite sketchy and the service seems sketchy as well. They charge you for the ROM or service to install the ROM from what I can tell which in itself raises all kinds of red flags, but I figured I would share what I found with you.
I'm trying to update my G Watch by sideloading a zip file.
I installed the sdk tools and usb driver as usual.
On debugging mode and bootloader, the watch is detected as an ADB device normally. 'adb devices' command works.
But when I reboot and get on recovery mode, the watch disappears on the device manager and never get detected again. So I cannot use 'adb sideload' command.
I've never experienced this kind of issue with smartphones.
Do you have any solutions?
osikiri said:
I'm trying to update my G Watch by sideloading a zip file.
I installed the sdk tools and usb driver as usual.
On debugging mode and bootloader, the watch is detected as an ADB device normally. 'adb devices' command works.
But when I reboot and get on recovery mode, the watch disappears on the device manager and never get detected again. So I cannot use 'adb sideload' command.
I've never experienced this kind of issue with smartphones.
Do you have any solutions?
Click to expand...
Click to collapse
My watch is now bricked because I have no way to get out of "adb sideload" mode...how did you get out of that mode? please tell me.
TjPhysicist said:
My watch is now bricked because I have no way to get out of "adb sideload" mode...how did you get out of that mode? please tell me.
Click to expand...
Click to collapse
I pushed the reset button on the back(the silver one right above the charging connectors) with a pen for about 10 seconds, and it rebooted.
osikiri said:
I pushed the reset button on the back(the silver one right above the charging connectors) with a pen for about 10 seconds, and it rebooted.
Click to expand...
Click to collapse
Wow ok, that's a LOT longer than I'm used to with other devices...THANK GOD I thought I had bricked it completely.
Anyway, now i have to figure out a way to get adb to work in sideload,...i mean CLEARLY it's possible lots of others doing it..
---------- Post added at 08:26 AM ---------- Previous post was at 07:41 AM ----------
TjPhysicist said:
Wow ok, that's a LOT longer than I'm used to with other devices...THANK GOD I thought I had bricked it completely.
Anyway, now i have to figure out a way to get adb to work in sideload,...i mean CLEARLY it's possible lots of others doing it..
Click to expand...
Click to collapse
Ok, does anyone know how to get my computer to recognise my watch in recovery mode? It's not about 'driver' the computer plain doesn't recognise that anything is plugged in at all.
I know the post is quite old already, but I experience exactly the same phenomenon...
I tried multiple PCs Linux and Windows,but non of them recognized the watch (neither on 4.4W1 nor on 4.2W2).
Anyone any idea?
Wikiwix said:
I know the post is quite old already, but I experience exactly the same phenomenon...
I tried multiple PCs Linux and Windows,but non of them recognized the watch (neither on 4.4W1 nor on 4.2W2).
Anyone any idea?
Click to expand...
Click to collapse
I believe u need to update the drivers.....I always go-to device manager...update driver..hit select from list..and choose android adb....
Sent from my LGLS990 using XDA Free mobile app
mrkrabs said:
I believe u need to update the drivers.....I always go-to device manager...update driver..hit select from list..and choose android adb....
Sent from my LGLS990 using XDA Free mobile app
Click to expand...
Click to collapse
The problem, as @osikiri stated, is that the device does not get recognized at all (no unknown devices in devicemanager and the sound that comes on plugging in a device does not come as well). Furthermore, afaik Linux does not even need any drivers
Had the same issue today... and the only way out way battery death and recharge
JaceAlvejetti said:
Had the same issue today... and the only way out way battery death and recharge
Click to expand...
Click to collapse
If this really helps (seems weird): I guess the exact setting could be necassary:
You simply ran out of battery while the watch was running(not recovery or fastboot) and then plugged it in and went directly (or not?) to the recovery?
Thanks in advance, would be really great to fix this!
Anyone ever find a fix to this? I'm trying to manually install the 5.0 update and I'm having the same issue. Every post I find with search tells me to update drivers but I'm on a Mac that doesn't even use ADB drivers. I've updated the SDK.
MSigler said:
Anyone ever find a fix to this? I'm trying to manually install the 5.0 update and I'm having the same issue. Every post I find with search tells me to update drivers but I'm on a Mac that doesn't even use ADB drivers. I've updated the SDK.
Click to expand...
Click to collapse
I'm doing the same thing and having the same issues!
Yeah, same issue for me as described.
Windows (Win7 x64 for me) doesn't even realise that the device is connected when it is in recovery mode. Although it will connected properly when booted normally.
+1 Any ideas?
Same issue for me. I've tried removing and replacing it on the cradle, killing and restarting the adb server, entering recovery by the touchscreen or by the adb/fastboot commands, clearing debugging keys, etc... Anybody have any other ideas?
---------- Post added at 07:25 PM ---------- Previous post was at 06:46 PM ----------
Ok, so it appears that the recovery img on 4.4w2 broke adb support or something. There are a few threads that suggest you can root and flash it or just wait for the OTA. We'll see whether I get the OTA before I have time to try this out.
Lollipop OTA Update: Download and How-To (Root Required)
I made a script that roots and updates your watch to 5.0.1 in a click.
[UTILITY][RESTORE][UNLOCK][ROOT] LG G Watch Tool
My way of doing it
osikiri said:
I'm trying to update my G Watch by sideloading a zip file.
I installed the sdk tools and usb driver as usual.
On debugging mode and bootloader, the watch is detected as an ADB device normally. 'adb devices' command works.
But when I reboot and get on recovery mode, the watch disappears on the device manager and never get detected again. So I cannot use 'adb sideload' command.
I've never experienced this kind of issue with smartphones.
Do you have any solutions?
Click to expand...
Click to collapse
I've similar problem, and I've spent almost 3 hours to find the solution. I found that following solution work for me:
http://forum.xda-developers.com/g-watch-r/development/manual-ota-update-root-t2969845
I've changed the step slightly according to the comments inside the thread:
- Enter Bootloader (swipe top left-bottom right as soon as the LG logo pops up on boot)
- Unlock bootloader (fastboot oem unlock) and boot the watch normally once
- Turn off and re-enter bootloader
- Flash 5.0.1 Stock Recovery (fastboot boot recovery.img)
// Do Not Flash 5.0.2 stock recovery
- Enter recovery and ADB sideload the update (tap the android, select install update from ADB and enter adb sideload filename.zip)
//you might have to reinstall the ADB drivers, just follow the simple step to install ADB driver
Done.
fi thought it was finally the solution, but fastboot oem unlock bricked my sony smartwatch3. I see tomorrow if with my windows pc i can fix with sony companion, otherwise i'll have to use the warranty
willisc said:
I've similar problem, and I've spent almost 3 hours to find the solution. I found that following solution work for me:
http://forum.xda-developers.com/g-watch-r/development/manual-ota-update-root-t2969845
I've changed the step slightly according to the comments inside the thread:
- Enter Bootloader (swipe top left-bottom right as soon as the LG logo pops up on boot)
- Unlock bootloader (fastboot oem unlock) and boot the watch normally once
- Turn off and re-enter bootloader
- Flash 5.0.1 Stock Recovery (fastboot boot recovery.img)
// Do Not Flash 5.0.2 stock recovery
- Enter recovery and ADB sideload the update (tap the android, select install update from ADB and enter adb sideload filename.zip)
//you might have to reinstall the ADB drivers, just follow the simple step to install ADB driver
Done.
Click to expand...
Click to collapse
Hi guys. I got the Tmobile LG G2 and it was running on Android 4.4.2 LG G2 D80110c. Then I changed the dpi by editing the build.prop via root explorer up but when the device reboots, it shows system force close and I basically cannot do anything. I realized that my TWRP recovery hadn't installed successfully and also I think download mode is not working. Computer recognizes the device when it is on... Can someone please tell me how to unbrick my device? Is there a way to install TWRP at the current condition of the phone? I think I cannot use lg flashtool because that requires the phone to be in download mode, while mine can't get in download mode...please help! thank you!
Edit: also when I try to hard factory reset the device it shows: ERROR: boot certification error and it gets stuck in black screen.
What I can think of is a way to manually install TWRP via adb or manually flash a kernel that supports custom dpi, but the only problem is that I don't know how to do that...
brickedvice said:
Hi guys. I got the Tmobile LG G2 and it was running on Android 4.4.2 LG G2 D80120c. Then I changed the dpi by editing the build.prop via root explorer up but when the device reboots, it shows system force close and I basically cannot do anything. I realized that my TWRP recovery hadn't installed successfully and also I think download mode is not working. Computer recognizes the device when it is on... Can someone please tell me how to unbrick my device? Is there a way to install TWRP at the current condition of the phone? I think I cannot use lg flashtool because that requires the phone to be in download mode, while mine can't get in download mode...please help! thank you!
Edit: also when I try to hard factory reset the device it shows: ERROR: boot certification error and it gets stuck in black screen.
What I can think of is a way to manually install TWRP via adb or manually flash a kernel that supports custom dpi, but the only problem is that I don't know how to do that...
Click to expand...
Click to collapse
theres several things you could do.. try srk tools to try and fix twrp, or fix download mode using nuke download.. i dont know how to i just know theres a way to do it.. if other fails and it doesn not go into download mode then you must short circuit the motherboard.... then look at thread g2 hard brick fix..
here but try other first as this one you have to open phone..
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
raptorddd said:
theres several things you could do.. try srk tools to try and fix twrp, or fix download mode using nuke download.. i dont know how to i just know theres a way to do it.. if other fails and it doesn not go into download mode then you must short circuit the motherboard.... then look at thread g2 hard brick fix..
here but try other first as this one you have to open phone..
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
Click to expand...
Click to collapse
thanks for the prompt reply! is this the srk tools you are referring to: http://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076 ?
also what is nuke download? Thanks in advance.
Edit: nvm I read what nuke download mode is (when no recovery and can't boot). I will try it now and see if it helps...
brickedvice said:
thanks for the prompt reply! is this the srk tools you are referring to: http://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076 ?
also what is nuke download? Thanks in advance.
Click to expand...
Click to collapse
yes.. and its a way to force or fix device to enter download mode.. like i said ive never used it but i know it might help. if it fails then you must open the phone .. and short circuit the motherboard.. good luck. :fingers-crossed:
raptorddd said:
yes.. and its a way to force or fix device to enter download mode.. like i said ive never used it but i know it might help. if it fails then you must open the phone .. and short circuit the motherboard.. good luck. :fingers-crossed:
Click to expand...
Click to collapse
I don't think my phone is hard bricked. USB debbuging is on and computer recognizes the device when it boots up. I simply don't know how to install twrp via adb commands or alternative methods ... or how to manually flash a custom kernel that would allow normal device boot up when dpi is changed.
brickedvice said:
I don't think my phone is hard bricked. USB debbuging is on and computer recognizes the device when it boots up. I simply don't know how to install twrp via adb commands or alternative methods ... or how to manually flash a custom kernel that would allow normal device boot up when dpi is changed.
Click to expand...
Click to collapse
well me neithe LOL.. but i think you can fix recovery with srk. i think.. read and i think you can fix that.. ive never used it..
raptorddd said:
well me neithe LOL.. but i think you can fix recovery with srk. i think.. read and i think you can fix that.. ive never used it..
Click to expand...
Click to collapse
lol I used the srk tool but now i got this error:
Critical Error!
---------------------------------------------------------------------------
DemiGod Crash Handler : Critical Error!
Press Key to Choose Dload Mode or Reboot
1) Volume up : Dload Mode.
2) Volume Down: Reboot.
If u choose Dload Mode.
please do following action.
1) Dload Mode. please Connect USB
2) Get the Ram Dump image using QPST Configuration.
phone is in bootloop if I decide to reboot; while if I decide to go in download mode, it doesn't do anything...
brickedvice said:
lol I used the srk tool but now i got this error:
Critical Error!
---------------------------------------------------------------------------
DemiGod Crash Handler : Critical Error!
Press Key to Choose Dload Mode or Reboot
1) Volume up : Dload Mode.
2) Volume Down: Reboot.
If u choose Dload Mode.
please do following action.
1) Dload Mode. please Connect USB
2) Get the Ram Dump image using QPST Configuration.
phone is in bootloop if I decide to reboot; while if I decide to go in download mode, it doesn't do anything...
Click to expand...
Click to collapse
http://forum.xda-developers.com/lg-g2/help/demigod-crash-handler-critical-error-t3108512/page2
https://www.youtube.com/watch?v=x1mUpwfEeDo
raptorddd said:
http://forum.xda-developers.com/lg-g2/help/demigod-crash-handler-critical-error-t3108512/page2
https://www.youtube.com/watch?v=x1mUpwfEeDo
Click to expand...
Click to collapse
I saw those I just can't get it to be recognized by the computer. Did the guy in the video try the hard brick fix from XDA? It is not very clear how he gets his laptop to recognize the device
brickedvice said:
I saw those I just can't get it to be recognized by the computer. Did the guy in the video try the hard brick fix from XDA? It is not very clear how he gets his laptop to recognize the device
Click to expand...
Click to collapse
i do not know either.. shortening the mother board is to enter download mode..
brickedvice said:
Hi guys. I got the Tmobile LG G2 and it was running on Android 4.4.2 LG G2 D80110c. Then I changed the dpi by editing the build.prop via root explorer up but when the device reboots, it shows system force close and I basically cannot do anything. I realized that my TWRP recovery hadn't installed successfully and also I think download mode is not working. Computer recognizes the device when it is on... Can someone please tell me how to unbrick my device? Is there a way to install TWRP at the current condition of the phone? I think I cannot use lg flashtool because that requires the phone to be in download mode, while mine can't get in download mode...please help! thank you!
Edit: also when I try to hard factory reset the device it shows: ERROR: boot certification error and it gets stuck in black screen.
What I can think of is a way to manually install TWRP via adb or manually flash a kernel that supports custom dpi, but the only problem is that I don't know how to do that...
Click to expand...
Click to collapse
This thread here : http://forum.xda-developers.com/showthread.php?t=2449670 might help you installing twrp via adb
Hi, I tried root on my phone, I was on android nougat and I installed twrp, then perform a data factory reset and restart does not go from the boot screen and shows the legend "bad key", custom recovery works but not I get nothing, please help me!
Check this out
rolas96 said:
Hi, I tried root on my phone, I was on android nougat and I installed twrp, then perform a data factory reset and restart does not go from the boot screen and shows the legend "bad key", custom recovery works but not I get nothing, please help me!
Click to expand...
Click to collapse
I had the same problem and this post helped me.
samvictorino said:
I had the same problem and this post helped me.
Click to expand...
Click to collapse
Cmd does not recognize fastboot mode, usb debugging is disabled and I can not find a way to activate it, adb sideload from twrp works but will work from there?
rolas96 said:
Cmd does not recognize fastboot mode, usb debugging is disabled and I can not find a way to activate it, adb sideload from twrp works but will work from there?
Click to expand...
Click to collapse
Sorry, actually when I did it I accidentally wiped the system partition and this post helped me, not the previous one.
I didn't need to enable unknown sources or usb debug because there was no system to begin with. I hope it helps you.
rolas96 said:
Cmd does not recognize fastboot mode, usb debugging is disabled and I can not find a way to activate it, adb sideload from twrp works but will work from there?
Click to expand...
Click to collapse
Fastboot doesn't need USB debugging to be enabled. You have some other issue.
Sent from my XT1650 using Tapatalk
In twrp just ignore encrypt pass and not modify system allowed (slider)