Hello everyone, so I'm having a hard time with my G3, I do not know if I was drawn .. or it could be something else, plus the fact and that, I got a LG G3 recently, and since then I'm trying to install a custom room other than Stock, so I'm having an error, after I install any room, my device is in bootloop, I reinstalled the factory system, via KDZ, I practically tested all that are possible to perform root access, but without success, the only ROM I can install and Tekcafe, that at some point, time restarts the device, or heats the same one more than normal.
I did a very intense search, and I could not find a probable cause for this problem. I ask for your help.
current device information
this is with Tekcafe 5.5, the wifi and bluetooth does not work, (I believe it is a physical problem) battery is not problem, I did not notice any other error that could cause such problem.
Remembering, I tried to change the file extension from ext4 to f2fs, even without success.
I tried installing lineage the 15, Crdroid, and ..
I am very grateful if anyone can help me with this problem.:crying::crying::crying::crying:
Related
Hi All,
Having some issues with my Galaxy Note 10.1 which I've had for quite a while now. It's rooted but with Android 5.0 stock rom and a custom kernel.
Just now (like 20mins ago) I tried to enable Adblock plus app, the app said it can't automatically change the settings - even though SuperSU was installed and had no issues with it previously. So like all things thought I'd give it a reboot that ought to clear it out. That didn't work, so tried clearing cache (Dalvik/ART/Cache), Still no joy.
I'm a s/w engineer, but not and android/bootloader expert, so I've tried to grab the dmesg and boot logs which I've attached, I've got some stuff on the internal SD (app data) which I'd like to keep, hence I'm not going for the full wipe.
Please take a look at the logs and see if you can determine how to fix this issue, my initial thoughts were there are some issues with the flash storage (bad sectors/partition table?), if I could grab the image and dd the image again I'd be OK - but I don't know much about about android boot loader/kernel etc so can't say.
Ok it has been fixed by wiping data - but I've lost my data and installed apps!
Is there anyway to find out which file/app is causing the boot loop so I can restore data, delete the offending file?
Well, I shall give a bump to this topic, with a little more info. Though probably not really useful.
First I had stock 5.1.1 deodex pre root etc ROM that, after I tried to insert a nano sim card (mine is a 601 3G model) that got stuck, it entered on a bootloop, I had to open it, take the sim card out, and it was still on a boot loop. Tried to install another image, still bootloop, tried to reinstall the original one I had, still bootloop, wiped data, worked fine.
Then almost 2 weeks later, everything worked fine, went to watch a video, the sound was mute, tried to turn it on but everything looked fine, decided to restart because it would probably fix the problem. Got a bootloop. Wiped the data, everything was fine again.
Now, a little more than 2 weeks later, seems like the wifi is not working, thought all my other devices are, guess it's the same problem, decided to restart it, and bootloop again. I'm currently trying to update my TWRP, and gonna try a different ROM, and wait to see if something like that happens, until then, I wonder what could be happening... I remembered an Asus Device that I had that had different firmware versions for 4.4 and 4.1, so if I tried to flash a 4.4 on a 4.1 firmware it wouldn't work, and for downgrade, the same problem happened, and wondered if Samsung has some difference between versions 4 and 5.
ssj4maiko Let me know if you find a more stable rom - I went back to pretty much stock, but with root as I wanted to use all the Samsung apps, but this constant random bootloops are annoying!
New to the world of Custom ROMs. A week ago I installed CM 13 which took great courage on my part and wanted to share my experience, issues and discuss possible solutions.
My phone had the latest lollipop on it. And McCafee locked. The steps that worked for me where
1) Did a factory reset and bumped into mccafee.
2) Tried download mode but kill switch was enabled.
3) Rebooted the phone to face mccafee, tried 123465 pin which worked.
4) Disengaged McCafee but not before transferring ownership to my email.
5) Tried rooting didnt work with any method.
6) Rolled back to d software version stock lollipop.
7) Rooted with PurpleDrake
8) Replaced with CM recovery didnt work.
9) Replaced with TWRP and rebooted directly to recovery
10) Installed CM and gapps mini. Worked fine. Voila!
Issues:
1) No Custom recovery sticks, whenever I flash with a custom recovery like TWRP or Clockwork. I have to reboot into recovery immediately or the custom recovery is replaced by stock. It happens on every second reboot.
My concern is here if I get stuck into bootloop and dont have a custom recovery I might not have any other option than the stock ROM which does a full reset. How can make TWRP stick forever?
2) After installation of Custom ROM there have been random reboots, I suspect there is something here with phone app or voice. So far the reboots have been when I try to call using fb messenger, appear.in and phone app itself.
Is there a guide that tells me how to track this down?
Can I install a newer Nightly and hope this get fixed?
How can I retain my apps and data when installing a newer nightly? since all guides ask to wipe everything :S
I have a backup of system and data partitions, can I use that with other ROMs.
What ROMs have a better chance of fixing this issue?
Coudnt find Stock M for D850. Why arent those available?
Should an Official ROM be more reliable than CM for this?
3) Bad signal reception so far. It may be a generic g3 issue.
Can I hope that this issue be fixed with a different ROM or updates from Cynogen?
Someone said you may have to flash the radio partition. My question is where can I get a brief understanding of what partitions there are in android and which are risky. Which ones can be replaced, backedup and replaced back.
4) Whenever the phone reboots, it gets stuck into bootloop unless I remove the SIM card. Then I power off and install SIM Card and reboot and it boots fine.
I am already tracking CM changelog for something important. Cant post urls as of now :S
Hello guys,
I managed again to brick my phone.
I flashed Fulmics as I wanted to swap from those not fully stable nougat roms. Well, I have no idea what caused my problem - Fulmics run without prolbems for a 2 or 3 days including xposed etc.
Then today I changed my ChromePie options and that's when the reboots began. I don't know if this the real cause was though.
So I tried to flash another rom but always got random reboot even in recovery after few minutes/seconds. So I went all the way back to stock rom (4.4.2) with LG Flash tool - which worked after a few tries. Then I installed MM rom via .kdz file and flash tool 2014, which also worked after a few more tries. But then the reboots started again. Can't say if the 4.4.2 rom was without boots because I updated to 6.0 quite quickly.
The strange thing is that after some reboots phone won't boot again and I have to take and leave out the battery for some time to boot the phone again.
Any solutions for my problems?
Best regards
..bumped into the same 1/2 year ago. Didn't want to put to much effort so,..went to stock and back, worked for me.
Good luck.
Gerhard.M said:
..bumped into the same 1/2 year ago. Didn't want to put to much effort so,..went to stock and back, worked for me.
Good luck.
Click to expand...
Click to collapse
Which stock and how did you go back?
As mentioned I already went back to stock but the issue kept occuring.
Hi, got the same problem with my G3
wi fi and bluetooth didn't work and phone loop rebooted
Here below the steps I followed to solve
1) First attempt (didn't solve): had cloudy rom, got back to stock official but still rebooting, tried fulmics and other rom but problem persisted.
2) second attempt (didn't solve): went back to stock and changed battery (found somewhere in internet), now I have a brand new battery but a phone still loop rebooting
3) third attempt (SOLVED): found that the wi-fi / bluetooth chip (one for both) copuld have unwelded and solved so (it appears I can't post outside link, delete spaces to have the correct link):
youtube .com / watch?v=1zWpzYh2DPI&t=15s"
youtube .com/ watch?v=6_0jzp65eLY&t=256s
Now i'm on fulmics and no more loop reboot
Hope you can solve
[sorry for my english]
frosty234 said:
Which stock and how did you go back?
As mentioned I already went back to stock but the issue kept occuring.
Click to expand...
Click to collapse
http://stockroms.net/file/LGG3/D855/European/BIN_LGD855AT-00-V10e-EUR-XX-JUL-08-2014-32G-0.zip
http://storagecow.eu/index.php?dir=Xda/LG+G3/Stock/D855/
used flashtool
have to say restoring and/or flashing isn't always that stable. I've experienced it sometimes needs a 2nd try.
Hopefully it isn't a hardware issue in your case.
So I tried all of oyur suggestions but nothing seems to work.
On the contrary I ended up in a status where I can't even flash a new firmware.
In LG Flash Tool 1.8.1 I get the error
"Donwload Fail!!!"
PID: NULL
IMEI: NULL
MODEL:
DLL: D855
BIN: LGD855AT.....
SWV:
SWOV:
Model Information Check Fail!
000000000
Click to expand...
Click to collapse
In LG Flash Tool 2014 (flashing MM with kdz file) phone shuts down in middle of process.
But I can still access Download Mode.
No more ideas?
I really think I finally broke my phone... But the fact that I can still access download mode keeps my hopes up.
So, after 2 months I just tried to reawaken my phone. Still the exact same problem. It just keeps shutting down aber some while, but just when I start flashing something. If it stays connected to computer whitout doing anything it can stay on for like ever.
Can anyone confirm that this could be a hardware defect?
So I have a T-Mobile LG G4 that like every other G4 had the bootloop problem when I got it. I sent it to LG and they promptly fixed the issue. My current issue has nothing to do with the bootloop I believe.
Because the G4 wasn't getting the Android N update fast enough and also because I wanted to play around with Android's full potential, I decided to root the phone a little over two weeks ago. The process worked and I decided to install a custom ROM. That also worked. I have installed four or five custom ROMs built on Android 7.1 without issue, or at least without any major issue.
However last night I decided to flash Genysis ROM on Android 6.0 because I wanted to play with Xposed. I made a full Nandroid backup of the CRdroid ROM it had been running and then wiped and flashed it using TWRP. When I installed the ROM it didn't work for whatever reason, freezing up and frequently becoming unresponsive. Over about 30 minutes I managed to enable USB debugging and reboot it to recovery (why I didn't shut factory wipe it from bios I'm not sure).
Now any ROM I try to install doesn't boot up. It never gets past the OS loading screen with the ROM logo. On 6.0 ROMs it says it has optimized the apps but gets stuck on starting them. The Nandroid backup I made does the same thing, even ones I made early that day and one from several days ago.
The backups had that one app installed that shows the logcat while booting up and while I'm no expert it seems to get a loop loading the audio drivers. I don't know if that's the cause or if it's just coincidental, as I've never heard of audio drivers preventing a boot, albeit my experience is with Windows PCs.
If it would help I can attempt to take a picture of the screen while stuck, although the text moves very fast. I can access the TWRP recovery just fine but don't know how to/if you can dump logs.
Any help would be much appreciated! I can attempt to supply an information that may be needed as well.
merger3 said:
So I have a T-Mobile LG G4 that like every other G4 had the bootloop problem when I got it. I sent it to LG and they promptly fixed the issue. My current issue has nothing to do with the bootloop I believe.
Because the G4 wasn't getting the Android N update fast enough and also because I wanted to play around with Android's full potential, I decided to root the phone a little over two weeks ago. The process worked and I decided to install a custom ROM. That also worked. I have installed four or five custom ROMs built on Android 7.1 without issue, or at least without any major issue.
However last night I decided to flash Genysis ROM on Android 6.0 because I wanted to play with Xposed. I made a full Nandroid backup of the CRdroid ROM it had been running and then wiped and flashed it using TWRP. When I installed the ROM it didn't work for whatever reason, freezing up and frequently becoming unresponsive. Over about 30 minutes I managed to enable USB debugging and reboot it to recovery (why I didn't shut factory wipe it from bios I'm not sure).
Now any ROM I try to install doesn't boot up. It never gets past the OS loading screen with the ROM logo. On 6.0 ROMs it says it has optimized the apps but gets stuck on starting them. The Nandroid backup I made does the same thing, even ones I made early that day and one from several days ago.
The backups had that one app installed that shows the logcat while booting up and while I'm no expert it seems to get a loop loading the audio drivers. I don't know if that's the cause or if it's just coincidental, as I've never heard of audio drivers preventing a boot, albeit my experience is with Windows PCs.
If it would help I can attempt to take a picture of the screen while stuck, although the text moves very fast. I can access the TWRP recovery just fine but don't know how to/if you can dump logs.
Any help would be much appreciated! I can attempt to supply an information that may be needed as well.
Click to expand...
Click to collapse
why not start from 0 and flash latest KDZ with LGUP.
https://forum.xda-developers.com/tmobile-g4/development/h811-kdz-file-t3607807
For sure I'll try that. I'll let you know if it works, thanks!
Follow up- I eventually found the free time to work on this and flashing the kdz worked! I actually had to use LG Bridge as LGUP only found my device as unknown.
Thanks for the help! Back to flashing ROMs for me.
Hello guys, this thread is for you all to share your experience of dealing with your LG G3 problems, including software or hardware
Whether the problem is critical or not, or even just a tip, they're all welcome!
You can post your ideas now, they can help many people!
If you think your phone with stock rom is glitchy or reboots and hangs randomly, this can help!
Solution
First, boot to recovery and factory reset your phone.
Second, boot back to os, then SET THE DATE TO 2014, and about the date when LG g3 was released.
Do not connect the phone to the internet or do not let the phone knows the current time and date.
Third, please root and install a custom rom ASAP, like lineageOs, NOT stock rom based.
What is planned obsolescence? And why it's related to these problems?
Planned Obsolescence is extremely prevalent in smartphones. Phone companies such as LG, wanted their customers to stop using their phones after warranties, and buy a new phone so they can earn more interest. Therefore they embed software "time bomb" in android phones(usually embed in the stock ROM)These were counting down to the right time after a few weeks of warranty, then your phone would start doing "suicide"(causing problems and damaging itself) resulting lag, freezes, random reboot, bootloops, and even bricked at last.
In the solution, it intercepted that "time bomb", so it will think the phone is still in warranty and stop causing problems to your phone.
This solution can also WORK ON OTHER devices.
Before my stock rom android 4.4 LG G3 F400S had a constant reboot, so I reset it, set the date to 2014/9/12, and installed lineage os 18.1 on it. Everything works again, or even better.
Please share this to everyone, I bet this can help many people and most of them don't know it. Thx
refer: https://forum.xda-developers.com/t/stock-rom-freezes-and-bugs-please-help.4234773/