This is my first time dealing with LG in my rooting career.
I got my OGP Home and rooted it quickly and easily and flashed Slimkat 4.2.2. I had constant issues with dropping and losing signal. Convinced that it was an issue with KitKat, I flashed Vanir 4.2.1 and the modem that was suggested. This resulted in me COMPLETELY losing mobile data.
I called AT&T and they worked fixed some IMEI issues that I had, but it still didn't fix my mobile data. I decided that I would just restore from backup to the original Slimkat that at least worked most of the time.
I flashed back to slimkat and had no signal issues (so I am assuming that whatever the AT&T rep did to my account fixed the issue to slimkat)
I took the opportunity to reflash Vanir, and lost data services again. So I restored yet another time to slimkat, and my data worked again.
After all this I was so digusted that I unrooted and flashed back to stock last night and updated the firmware and broke the ability to re-root for now.
I like this phone, but I am considering switching back to Samsung.
Does anyone know what could have caused all of these issues with LG. Is this a common issue?
Similar issues have been reported on almost all ROMS, from lost service, no GPS to no working sensors. Until a proper bootloader unlock is discovered/developed, these problems will persist. I'm running G2 V5 right now, seems to be the most stable but not KitKat though.
I flashed CyanogenMod and it seems to be doing well. It's important to back up your efc and restore it if you have issues. I thought I was seasoned on this stuff, but this phone made me feel like a novice
Sent from my LG-E980 using XDA Premium 4 mobile app
Related
My GNex (yakju) is losing data connection so often now since I received 4.2.0 it's not even funny. I updated to 4.2.1 and problem is still there. The only way to get connection back is to toggle airplane mode a few times or reboot.
Background: I had this problem when I purchased the phone which was on 4.0.1 originally. I eventually found out about this site and updated to 4.1.1 using mskip's GNex TOOLKIT. Miracle, no more data connection loss! I could now fully enjoy the GNex and has been functioning flawlessly for several months. When 4.1.2 came out, I updated OTA and phone was still working perfectly.
Now 4.2.0 came out, received it OTA - horror: my connection loss problems are worse than ever So I though OK I will just go back to 4.1.2, but problem remains. OK then I'll go back to 4.1.1, but problem remains! Reset factory settings, flashed phone several more times re-trying 4.1.1, 4.1.2, 4.2.0, 4.2.1... no success. Checked APN, reset APN as per provider settings (Telus in Canada) but without success.
My connection now drops all the time. I miss about 90% of my calls, notifications, etc. Google search finds several people with similar problems and indicate some GNex have hardware problems and the solution is to ask Samsung for an exchange until you get a good one but often takes 3-4-5 phone swaps before getting a good one.
I just find it is a very strange coincidence that my phone "broke" immediately after updating to 4.2.0. Anyone has any ideas how I could solve this problem (other than going to Samsung for a swap because this is a nightmare road I'd which to avoid)?
Had a similar issue lost service altogether, used mskips gnex toolkit to wipe all then download and flash stock google image, immediately fixed issue so did one click root busybox etc and regained root then flashed a custom rom, no dramas since and smooth as butter.
Hope this helps am somewhat of a noob so dont know tech stuff but toolkit did the job and fixed it, its a software bug methinks, many thanks to mskip and xda
sent via xda app from my yakju gnex 4.2.1 paranoid android 2.99 beta 6
Dan Demonic said:
Had a similar issue lost service altogether, used mskips gnex toolkit to wipe all then download and flash stock google image, immediately fixed issue so did one click root busybox etc and regained root then flashed a custom rom, no dramas since and smooth as butter.
Hope this helps am somewhat of a noob so dont know tech stuff but toolkit did the job and fixed it, its a software bug methinks, many thanks to mskip and xda
sent via xda app from my yakju gnex 4.2.1 paranoid android 2.99 beta 6
Click to expand...
Click to collapse
I already re-flashed my phone countless times with with the latest gnex toolkit trying various ROM setup such as 4.1.1, 4.1.2, 4.2.0, 4.2.1 with no success. Then I tried flashing several different recent or older radios (UGKL1, UGLC1, UGLH1, XXLF1, XXLH1) with again no success. Now pretty much anytime I wake my phone, my connection is grayed out whichever ROM (stock) or radio I tried.
I haven't tried is trying all radios on older ROMs yet and I only tried the different radios on 4.2.1. Then again I feel I shouldn't have to do all this and think its getting ridiculous, I mean the latest build should be reliable.
Yesterday my gps wasnt working at all. It would not lock on no matter what I did. I was on a custom rom and I tried wiping my data/cache, reinstalling maps (just for giggles), and a multitude apps from the market that help deal with gps problems (gps fix, gps status, toolbox, etc).
When all this didn't work I decided to odin back to the last official JB update and still no gps. On a whim I decided to odin back to an ICS firmware and that made my gps work. I have no idea but it did. I then odin to UVDLJC, installed TWRP's most recent and restored my backup of the custom rom I was using in the first place and gps now worked.
While I'm happy as heck that my gps is now working and that it was not a hardware issue I'm extremely curious what happened.
I have flashed many roms lately and I cannot think what a custom rom can do to gps to hose it or if it was just one of those things. I would of thought that when I originally did an odin to UVDLJC that would fix the issue but that didn't. Whatever the flash to ICS did fixed it but what in the heck could that of been?
I figure if I can find out or get an idea what happened then I can steer away from flashing certain roms, or just be prepared that flashing any roms at all can make this happen again.
Same here.
Hello, ddcoh.
I am currently having the same issue you had with GPS not working. I've tried everything from trying tedious Play store apps to trying many different roms and kernels (clean installing every time) to completely reverting back to stock including using TriangleAway in case that did any help. Nothing worked. I have been thinking about going back to ICS to see if that worked but the last time I tried to downgrade from 4.1.1 to 4.0.4 I ended up soft bricking my phone even though I followed the steps word for word.
Can you tell how you went about downgrading to ICS and then back to JB, please? I use my GPS a lot and I would hate to find out it's a hardware issue.
Typically, it's been when people are going from 4.2 to 4.1.
Zza1989 said:
Hello, ddcoh.
I am currently having the same issue you had with GPS not working. I've tried everything from trying tedious Play store apps to trying many different roms and kernels (clean installing every time) to completely reverting back to stock including using TriangleAway in case that did any help. Nothing worked. I have been thinking about going back to ICS to see if that worked but the last time I tried to downgrade from 4.1.1 to 4.0.4 I ended up soft bricking my phone even though I followed the steps word for word.
Can you tell how you went about downgrading to ICS and then back to JB, please? I use my GPS a lot and I would hate to find out it's a hardware issue.
Click to expand...
Click to collapse
Well I used odin to flash an T999_UVALEM which was a prerooted ICS rom. After booting it up I checked to see if GPS was working and it was.
I then used odin again to flash T999_UVDLJA which is a JB rom and booted it up also and saw that gps was working. Then I just restored a backup of a room I had been using and GPS still worked.
I've been out of town and noticed that after flashing a few roms that gps wasn't working so instead of doing all the above stuff I just flashed a cm10 rom. I believe I either used a cm10 nightly (or maybe 10.1, memory is hazy) or LiquidRom and that got the GPS working by just doing that. Not sure if that will work for you but you could always backup your setup using TWRP's latest and then flashing a cm10 rom and seeing if gps is working and if that fixes it then you could then just reboot and restore the rom you are currently on and that might fix your gps for you.
http://forum.xda-developers.com/showthread.php?t=1949687
I did some searching, and found other people having issues with their Galaxy S3 rebooting randomly, but they were having that issue with CM 11. Since I'm still on 10.2, though, the methods that they suggest (mainly installing the updated gapps for CM 11) won't work.
Heres's the background info:
I'm on Sprint, and have been having issues with LTE reception ever since I switched from Touch Wiz to CM back in October. The issue started a couple weeks ago when I found out that the MK3 modem was available. I was still on MD4, and having issues with LTE reception, I thought this new modem would help. I downloaded an install zip file I found on this site and used CWM to install it. That same day I also found out about an updated apns-config.xml file that had helped out other people that used Sprint/Ting with LTE reception. I found that file here (I'm still considerd a new user, so replace _ with a period):
help_ting_com/entries/23423026
The install zip that I downloaded from that site didn't work, so I backed up the original apns-config.xml, and manually replaced it with the new one. I had to change permissions on a couple folders in order to replace it, too.
That day is when the random reboots started happening. I've since reverted back to the MD4 modem, and have also reverted to a backup of the old apns-conf.xml. I've also changed the permissions to the system and system/etc folders to what they were before, as well. The random reboots keep happening, though.
Any help would be amazing.
cbellk said:
I did some searching, and found other people having issues with their Galaxy S3 rebooting randomly, but they were having that issue with CM 11. Since I'm still on 10.2, though, the methods that they suggest (mainly installing the updated gapps for CM 11) won't work.
Heres's the background info:
I'm on Sprint, and have been having issues with LTE reception ever since I switched from Touch Wiz to CM back in October. The issue started a couple weeks ago when I found out that the MK3 modem was available. I was still on MD4, and having issues with LTE reception, I thought this new modem would help. I downloaded an install zip file I found on this site and used CWM to install it. That same day I also found out about an updated apns-config.xml file that had helped out other people that used Sprint/Ting with LTE reception. I found that file here (I'm still considerd a new user, so replace _ with a period):
help_ting_com/entries/23423026
The install zip that I downloaded from that site didn't work, so I backed up the original apns-config.xml, and manually replaced it with the new one. I had to change permissions on a couple folders in order to replace it, too.
That day is when the random reboots started happening. I've since reverted back to the MD4 modem, and have also reverted to a backup of the old apns-conf.xml. I've also changed the permissions to the system and system/etc folders to what they were before, as well. The random reboots keep happening, though.
Any help would be amazing.
Click to expand...
Click to collapse
When I 1st flashed a cm11 based rom, I had random reboots. I solved the problem by changing kernel governor from interactive to on demand. I have not had a single reboot in months. All phones are built differently though. I've had mine since they 1st came out.
sent from my GS3
Jessooca said:
Does your phone get to the Samsung logo and reboot?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Nope, it's the CM logo.
joeyhdownsouth said:
When I 1st flashed a cm11 based rom, I had random reboots. I solved the problem by changing kernel governor from interactive to on demand. I have not had a single reboot in months. All phones are built differently though. I've had mine since they 1st came out.
sent from my GS3
Click to expand...
Click to collapse
Thanks. I tried this, and it didn't seem to work. Phone's still randomly rebooting. I'm on 10.2, btw. Haven't moved to 11 yet.
Jessooca said:
The best way to truly fix your issue is to start back over at square 1... Odin it back to stock with the tar or MD5 file. The last thing you want to do is make things worse trying too many things.
If you can get back into recovery wipe everything, (but not your Sd card ) as long as you've got a Rom on your Sd card to flash. Don't flash the same rom again, your issue could be a number of things.
- If you made a backup before flashing then revert back to it. Then try to download the rom again, or if you can download the latest slimkat on another pc and copy it to your sd card it's small a quick download and it will get you back up and running.
That is, if you don't feel like using Odin.
Click to expand...
Click to collapse
So I wiped, and started over, and then restored data, but the random reboots are still happening. Should I not have restored data? I'd like to avoid losing everything if I could.
cbellk said:
So I wiped, and started over, and then restored data, but the random reboots are still happening. Should I not have restored data? I'd like to avoid losing everything if I could.
Click to expand...
Click to collapse
Data restore could very well be the culprit.
sent from my GS3
joeyhdownsouth said:
Data restore could very well be the culprit.
sent from my GS3
Click to expand...
Click to collapse
So I'd have to start from scratch? Is there any way I could keep my data?
This has randomly happened three times to me so far on different roms. I searched Google and XDA forums and maybe i am searching for the wrong terms so i will ask here.
I had Hyperdrive installed on my phone for 3 weeks with no problem, i was texting last night no problem. In the morning i woke up and could not send/recieve messages or calls but i could surf the web, check facebook, and everything. This was on and off of wifi. Reboot several times, Full wipe and restored to a previous nandroid, same problem. Another full wipe and reinstalled hyperdrive from scratch, same problem. Finally spoke with Tmobile, no help. Grabbed Carbon rom and then everything worked fine! Why?! Does anyone know why that happens? Same thing happend with the 4.4 Google edition rom. Worked for days then no network. Went back to carbon and it worked fine.
TLDR:Hyperdrive worked great for a week then lost all mobile except internet. Full wipe several times and problem persisted. Changed to Carbon Rom and it worked fine
Used Google Edition 4.4 for days and then it also lost all mobile except internet. Full wipe several times and problem persisted. Changed to Carbon Rom and it worked fine.
What is your modem?
Baseband version shows
M919UVUAMDL
Update it
You can grab the new nh7 modem from Shinyside in development, I ran with my MDL rom no problem.
Pp.
I updated to the NB4 and it seems to be working again. Ill see in a few days if the problem comes back. Its weird that it works great and then out of nowhere it acts up. Thank you for your help!
I will try the nh7 modem from Shinyside if i have the problems again. Or i will just stick with Carbon Rom, it works great but i wanted to try something different.
Nh7 modem has improved my signal all around, I noticed it on my previous rom and going to nh7 stock rom has been a good move for now.
Pp.
So it happened again with the updated modem. After 2 weeks of using Hyperdrive i lost service again. Reboot, wiped and used a backup. Still no service. Wiped and re-installed from scratch, still no service. Updated to the newer version of Hyperdrive, still no service. Wiped and reloaded Carbon and i have service again. I do not get it.
You might have to update your bootloader
serio22 said:
You might have to update your bootloader
Click to expand...
Click to collapse
Ditto, for Serio, that has been a common issue between KK roms and latest KK firmware.
Go for the nh7 bootloader , don't stress knox.
Pp.
DON'T PANIC!
I own two Verizon note 4 devices. You could call me a flash-a-holic. I love this stuff and really love my Note 4. It's the best phone I've ever seen with great features that many newer ones do not have. However, you already know that ... so I'll dispense with the speech. Before any of you think I'm new to this stuff, I should say I've been flashing devices since 2005 with my old Windows Mobile devices. I also manage a total of seven Note 4 devices from Verizon, five of which are on my own plan. My neighbor has the other two because they loved mine so much.
Recently, I've been playing around with some of the International ROMS, particularly the Note 7 and S8 ports in the Snapdragon section. I really love those for the scrolling snapshots and S8 launcher (even though I use Nova on my daily device). However, after flashing so many of those and having to use a variety of data fixes to get 4G working, I seemed to have messed up my device. I was having really odd issues, like going from 1X, 3G, 4G, to disabled for several minutes before it would settle and finally connect. I also had issues with text messaging. It would work fine, for a while. Then it stopped receiving messages, but I could still send. I messed with APN settings, which didn't help. I flashed more data fixes and APN fixes I found. Nothing really fixed it. So I figured it was the SIM card. I went to Verizon and admitted it was a custom ROM, but he could see that obviously. He gave me a new SIM card, yet I still had the same trouble. After a reboot, it wouldn't settle on a connection for about three minutes, sometimes more. I still was unable to receive text messages (including MMS) on that device. Even a Nandroid backup did not fix the problem.
Here's what I did to fix it.
I decided it was probably best for me to restore back to stock and go through the rooting process again. Ugh... but I love my phones. I'd do anything to keep them going. Instead of using ODIN to restore back to the original stock, I used the Safe Upgrade for 6.0.1 found below. It's been fixed so it does not lock the bootloader again, but restores everything else to stock, but you get to keep TWRP recovery.
https://forum.xda-developers.com/no...firmware-safe-upgrade-to-marshmallow-t3402727
I let it boot and go through the process (without signing into anything). Immediately, I realized that my data/4G problems went away. It never flickered even once. I let it sit for 15 minutes once it finished it's initial setup and rebooted back into RECOVERY to flash Kevin's Flashpoint kernel. That gave me root again with Magisk. After a full reboot, I then went into DOWNLOAD MODE and flashed the newest modem (CQI2) using ODIN. Then it was time to settle on a ROM for my use. This time I decided to go back to another International ROM and it appears I'm good to go. Just remember, the Verizon Voicemail app won't be included and usually won't work with an International ROM. I've tried and only was able to get it to work on one of them. It runs, but just will not connect to Verizon properly to access your voicemail. I'd love to find a real fix for that.
Ah... it's good to be working again. Now I can use Titanium Backup to restore my apps and data. BUT I DO NOT RECOMMEND RESTORING SYSTEM DATA. It can only cause problems.
Just a few suggestions for anyone having issues. ALWAYS keep several files on your PC/Device for this type of recovery.
1. Keep the Safe Upgrade to Marshmallow 6.0.1. image. It will be your lifesaver in case something goes wrong.
2. Keep a good working kernel (of your choosing). I prefer @kevintm78 Flashpoint Kernel. It restores Magisk v14 and almost always passes SafetyNet. I keep both stock and port versions on hand (just in case).
3. Keep a good ROM or two (also of your choosing) in order to reinstall a ROM you prefer to use.
4. Keep a working data fix to flash if you're using one of the ported ROMs. Not all are created equal, nor the same at all. Not all of them work. I recommend the Aurora N7 Data fix (Alpha 5 for my N910V): https://forum.xda-developers.com/showpost.php?p=69066109&postcount=2681
5. Keep the latest version of ODIN around. You'll need it from time to time.
Last but not least ... try this fix before you start blowing up the forums with questions and complaints about problems you have. I've found that most of the odd problems people experience are caused by using Titanium Backup to restore system settings created from another ROM, or trying to add different mods, which cause issues. Don't blame the developer for issues that you have that no one else has reported. Most likely, it has nothing to do with their software. It's probably something you installed or restored from a previous backup. You can let those old text messages and phone history go.
If you use Titanium Backup, only store system data IF you are using the exact same ROM as before. Otherwise you will experience problems.
I was sure my Note 4 was ready for disposal after the cellular issues I was experiencing. However I'm happy to report it's good as gold now. I'm not sure how much longer these devices will work for us, but I'll never freely get rid of mine. Besides, who else can fix the TV in the bar when the bartender loses the remote? Not very many devices these days have IR Blasters installed. I've used mine at least a hundred times for that very reason. But that's only one reason for loving this device. I could go on, but you already know that Samsung made the best device with the Note 4 models.
I hope this info helps anyone having problems after flashing so many different ROMs. I know, it's hard to settle on only one. Happy flashing and remember ... DON'T PANIC!