So I rooted and installed LineageOS 14.1 on my LG L70 (LG-MS323), I had rooted and installed CWM 6.0.5. I then used the latest nightly version of LineageOS 14.1 along with Micro GAPPS, to install the ROMs, I had wiped and formatted everything, from the cache to the system, then did an install.
Once I flashed the ROM, and went through setting up everything, it seems to run fine, but I have two issues as of right now: my SIM card is not being recognized, when I go to the Cellular Networks page to manually set this all up, it then displays an error that "com.android.phone has stopped working". No idea why I am receiving this error message.
Second - for some reason, I have enabled root to be accessible for both apps and ADB, but apps are unable to verify the root. The normal popup when allowing root access to an app is not appearing, so I have no idea why this isn't working either.
This is my first time rooting this device, and I am suspecting that maybe because I used CWM and not TWRP that is the reason my issues above (and others I may not be aware of yet) are appearing? Can anyone help me figure out what I should do? Or is there another ROM out there that I should consider? I was using this device as a daily, so being able to use the phone with all functionality is very appreciated.
darkgiant said:
So I rooted and installed LineageOS 14.1 on my LG L70 (LG-MS323), I had rooted and installed CWM 6.0.5. I then used the latest nightly version of LineageOS 14.1 along with Micro GAPPS, to install the ROMs, I had wiped and formatted everything, from the cache to the system, then did an install.
Once I flashed the ROM, and went through setting up everything, it seems to run fine, but I have two issues as of right now: my SIM card is not being recognized, when I go to the Cellular Networks page to manually set this all up, it then displays an error that "com.android.phone has stopped working". No idea why I am receiving this error message.
Second - for some reason, I have enabled root to be accessible for both apps and ADB, but apps are unable to verify the root. The normal popup when allowing root access to an app is not appearing, so I have no idea why this isn't working either.
This is my first time rooting this device, and I am suspecting that maybe because I used CWM and not TWRP that is the reason my issues above (and others I may not be aware of yet) are appearing? Can anyone help me figure out what I should do? Or is there another ROM out there that I should consider? I was using this device as a daily, so being able to use the phone with all functionality is very appreciated.
Click to expand...
Click to collapse
Have you seen the following thread?
http://forum.xda-developers.com/showthread.php?t=2698621
Peace and Love!
Peace and Love!
~Ringo Starr~
Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
********************************************
**IF I WAS HELPFUL IN ANY WAY THEN**
**PLZ THANK ME WITH A THUMBS UP!**
********************************************
Ibuprophen said:
Have you seen the following thread?
http://forum.xda-developers.com/showthread.php?t=2698621
Peace and Love!
Peace and Love!
~Ringo Starr~
Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
********************************************
**IF I WAS HELPFUL IN ANY WAY THEN**
**PLZ THANK ME WITH A THUMBS UP!**
********************************************
Click to expand...
Click to collapse
Yeah I tried that, but the problem is, when I go to cellular networks so I can enter a custom APN, it just gives me an error, which is essentially not allowing me to really access any of that portion within the ROM.
I also am having issues with ROOT access with the ROM, so no idea why that's not working properly
Related
This would probably be better placed in the Development forum but since I haven't posted here before I am not allowed. Anyhow...
I truly love the Infamous Resurrection and used the Infamous ROMs prior to this one. I have been having problems recently debugging my applications via Eclipse/ADB with this phone. I knew I had everything set up right and put it down to some incompatibility with something I had installed. So today I ran a test and flashed back to a rooted 2.3.6 ROM. I skipped adding any accounts or programs, set up for USB Debugging and Unknown Sources and, yes, it all worked great. I then did a factory reset and re-flashed Infamous Resurrection. Again I skipped adding any accounts, setup debugging and unknown sources. And it did NOT work.
I am getting two errors over and over again in the LogCat until it gives up:
cannot open CUSTOMER_XML
cannot open FEATURES_XML
Looking for a little help or at least to have someone pass this on to the developer.
adb T989 > 2.3.6 doesn't work
FWIW, I just tried the Jedi ROM and it through hundreds of more errors than IR. I guess I will need to be content with re-flashing down to 2.3.6 whenever I need to debug... unles someone has an answer.
bitlizard said:
This would probably be better placed in the Development forum but since I haven't posted here before I am not allowed. Anyhow...
I truly love the Infamous Resurrection and used the Infamous ROMs prior to this one. I have been having problems recently debugging my applications via Eclipse/ADB with this phone. I knew I had everything set up right and put it down to some incompatibility with something I had installed. So today I ran a test and flashed back to a rooted 2.3.6 ROM. I skipped adding any accounts or programs, set up for USB Debugging and Unknown Sources and, yes, it all worked great. I then did a factory reset and re-flashed Infamous Resurrection. Again I skipped adding any accounts, setup debugging and unknown sources. And it did NOT work.
I am getting two errors over and over again in the LogCat until it gives up:
cannot open CUSTOMER_XML
cannot open FEATURES_XML
Looking for a little help or at least to have someone pass this on to the developer.
Click to expand...
Click to collapse
First off putting this in development would of been a no-no. You are asking a question and this is Q&A so its in the right spot, now whenever I have had issues with adb its usually a kernel issue. Have you tried flashing a compatible kernel and then checking adb again. Also, this may or may not help your issue but try adbd Insecure by chainfire
Thanks for the response. I flashed the stock 4.0.3 kernel and still receive the CUSTOMER_XML and FEATURE_XML errors. And ADB does not work. There are a few additional mesages out of dalvikvm that may just be a fallout from the missing files.
class lookup Ljava/lang/Daemons; attempted with exception pending
VM Aborting
I have looked at the other kernels but nobody seems to be calling out ADB compatibility as a feature. Given that the stock kernel did not fix the problem, do you have any other advice? I am off to look for adbd Insecure.
playya said:
First off putting this in development would of been a no-no. You are asking a question and this is Q&A so its in the right spot, now whenever I have had issues with adb its usually a kernel issue. Have you tried flashing a compatible kernel and then checking adb again. Also, this may or may not help your issue but try adbd Insecure by chainfire
Click to expand...
Click to collapse
Actually, installing adbd Insecure did the trick. The errors I mentioned still happen but somehow it keeps on going. Thanks again!
bitlizard said:
Thanks for the response. I flashed the stock 4.0.3 kernel and still receive the CUSTOMER_XML and FEATURE_XML errors. And ADB does not work. There are a few additional mesages out of dalvikvm that may just be a fallout from the missing files.
class lookup Ljava/lang/Daemons; attempted with exception pending
VM Aborting
I have looked at the other kernels but nobody seems to be calling out ADB compatibility as a feature. Given that the stock kernel did not fix the problem, do you have any other advice? I am off to look for adbd Insecure.
Click to expand...
Click to collapse
bitlizard said:
Actually, installing adbd Insecure did the trick. The errors I mentioned still happen but somehow it keeps on going. Thanks again!
Click to expand...
Click to collapse
I have a new release out.
shnn2011 said:
I have a new release out.
Click to expand...
Click to collapse
Great, I'll check it out!
I upgraded Lineage OS 20170214 to 20170223 after the install the tablet boots through the splash screen the screen just turns black and hangs. I have waited up to 30 minutes and still just hangs on a black screen. Any ideas? I have to boot to recovery and install from backup.
Lineage 20170214 and earlier seemed to work except for the error listed bellow.
I imagine this is a carry over bug from CM 14.1 but I cant play any DRM videos from Google Play Movies. I can play trailers but anything purchased will not play. It does not matter if I download it or stream it. Usually it stops and just gives a "there was an error" prompt with out any specific error code. I say this was a carry over because I had the same problem in CM14.1.
Thank you for your time in reading this.
Kevinws42 said:
I upgraded Lineage OS 20170214 to 20170223 after the install the tablet boots through the splash screen the screen just turns black and hangs. I have waited up to 30 minutes and still just hangs on a black screen. Any ideas? I have to boot to recovery and install from backup.
Lineage 20170214 and earlier seemed to work except for the error listed bellow.
I imagine this is a carry over bug from CM 14.1 but I cant play any DRM videos from Google Play Movies. I can play trailers but anything purchased will not play. It does not matter if I download it or stream it. Usually it stops and just gives a "there was an error" prompt with out any specific error code. I say this was a carry over because I had the same problem in CM14.1.
Thank you for your time in reading this.
Click to expand...
Click to collapse
I believe that the following link can be very helpful regarding your issue:
[ANNOUNCEMENT] Important Lineage/LineageOS Information To Know... by Ibuprophen
I wish you the best of luck!
Peace and Love!
Peace and Love!
~Ringo Starr~
Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
********************************************
**IF I WAS HELPFUL IN ANY WAY THEN**
**PLZ THANK ME WITH A THUMBS UP!**
********************************************
Yes, I tried going from CM to Linage on this device using the 20170223 build. It was obviously bad and looks like it has been yanked off the downloads page as of today.
Unfortunately, I did not find Ibuprophen's answer to be terribly helpful. I looked at those references and it did explain to do an advanced wipe, but of course it never changed the outcome.
Just wanted you to know that I got the same results as you, and that you are not going crazy.
Thanks all who responded I really appreciate it.
Kevinws42 said:
I upgraded Lineage OS 20170214 to 20170223 after the install the tablet boots through the splash screen the screen just turns black and hangs. I have waited up to 30 minutes and still just hangs on a black screen. Any ideas? I have to boot to recovery and install from backup.
Lineage 20170214 and earlier seemed to work except for the error listed bellow.
I imagine this is a carry over bug from CM 14.1 but I cant play any DRM videos from Google Play Movies. I can play trailers but anything purchased will not play. It does not matter if I download it or stream it. Usually it stops and just gives a "there was an error" prompt with out any specific error code. I say this was a carry over because I had the same problem in CM14.1.
Thank you for your time in reading this.
Click to expand...
Click to collapse
The DRM issue has been resolved with the latest build. 14.1-20170317
A big thank you to all involved,
Kevinws42 said:
The DRM issue has been resolved with the latest build. 14.1-20170317
A big thank you to all involved,
Click to expand...
Click to collapse
I have installed lineage 14.1 with a tutorial every thing was ok but the wifi hotspot can't be activavted . that's why i want to install Marshmallow 6. To probe a tutorial that says works with android 6, in LG devices. Any tutorial you can sugest for the downgrade? Sorry for my bad english. Tank you in advance.
Hello, I am about to try something strange.
My Tablet VF 1497 won't boot up anymore. I can still get into recovery, but there is no firmware available for flashing.
Now I've found a tool from Alcatel, Mobile Upgrade Q, that flashes the latest stock firmware on the device. It works fine until software version check, then stops saying latest firmware already installed.
So my idea is to mess up the firmware on purpus, to get Mobile Upgrade Q working. But I have no idea how to "destroy" the installed firmware.
Any help is highly appreciated.
tkuemmel said:
Hello, I am about to try something strange.
My Tablet VF 1497 won't boot up anymore. I can still get into recovery, but there is no firmware available for flashing.
Now I've found a tool from Alcatel, Mobile Upgrade Q, that flashes the latest stock firmware on the device. It works fine until software version check, then stops saying latest firmware already installed.
So my idea is to mess up the firmware on purpus, to get Mobile Upgrade Q working. But I have no idea how to "destroy" the installed firmware.
Any help is highly appreciated.
Click to expand...
Click to collapse
Just because the device won't boot up into the firmware doesn't mean that its missing.
Boot into recovery and you should locate an option to restore to factory defaults.
The recovery of a device always has the factory firmware for restoring a devices firmware. Only on a few occasions this cannot be done that depends on what was done by the individual.
Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
**IF I WAS HELPFUL IN ANY WAY THEN**
**PLZ THANK ME WITH A THUMBS UP!**
Hello Ibuprophen, thanks for the answer.
Unfortunally factory reset doesn't change anything, I should have mentioned.
All the other options, clearing cashes and stuff, don't work either.
tkuemmel said:
Hello Ibuprophen, thanks for the answer.
Unfortunally factory reset doesn't change anything, I should have mentioned.
All the other options, clearing cashes and stuff, don't work either.
Click to expand...
Click to collapse
You may have to go to the forum.vidafone.uk
Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
**IF I WAS HELPFUL IN ANY WAY THEN**
**PLZ THANK ME WITH A THUMBS UP!**
Thank you, but I have done all this. It appears like a lot of users have the same problem, no solution until now.
May be there is a little chance 4pda.ru, but I need a better translation.
Before the bootloop I dumped the original system, boot and recovery, but I'm not able to make a flashable zip of it. May be this would still be a better chance to bring the tablet back to life...
tkuemmel said:
Thank you, but I have done all this. It appears like a lot of users have the same problem, no solution until now.
May be there is a little chance 4pda.ru, but I need a better translation.
Before the bootloop I dumped the original system, boot and recovery, but I'm not able to make a flashable zip of it. May be this would still be a better chance to bring the tablet back to life...
Click to expand...
Click to collapse
The Firefox browser has addons that will translate the whole web page.
I have an Asus tablet that I had recieved a replacement touchscreen for about 6 months ago but, i can't remember for the life of me where i had put all the screws. So everything for it is just in a protective case till i can find it. LOL!!!
Did your system come with windows?
My tablet had an android version of Windows in it and thought that yours may have had the same.
Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
**IF I WAS HELPFUL IN ANY WAY THEN**
**PLZ THANK ME WITH A THUMBS UP!**
Thanks for the tip, I'll try the addon. Hopefully its better than google translate (actually my russian should be pretty good as I learned it for 8 years in shool).
What is a android version of windows? I can't even thimk of something like that.
The tablet came with Lollipop and has a qualcomm chipset. I'd love to see some kind of bios and just flashing debian on it.
I'll try the russians again, may be I can manageto ask for a firmware package.
Good luck with the screws.
PS: Now I know, you mean something like windows rt?
So i'm currently on 6.0 and can't root it. Kingroot just doensn't work for me. I also tried to downgade it with lgup and flashtool but that also doesn't work, it stops arond 4%... so I performed a fix that clearly hasn't worked for me. Can anyone help me to root my phone? Thx
j_ras12 said:
So i'm currently on 6.0 and can't root it. Kingroot just doensn't work for me. I also tried to downgade it with lgup and flashtool but that also doesn't work, it stops arond 4%... so I performed a fix that clearly hasn't worked for me. Can anyone help me to root my phone? Thx
Click to expand...
Click to collapse
If you don't mind losing your data (or dirty flashing, I guess), then you could flash a custom recovery (https://forum.xda-developers.com/lg...mp-unlock-lg-g3-twrp-d852-d852g-f400-t2900614) , then a custom rom like CM13, AICP, or any other rom with root support built in. If downgrading doesn't work, I don't think there is any way to root on 6.0.
Also, I'm new here. :3
I have this problem too. My version is v30g Turkey stock. You can try adb method for root. Google it. I dont have computer so i didnt try.
Centrailic said:
If you don't mind losing your data (or dirty flashing, I guess), then you could flash a custom recovery (https://forum.xda-developers.com/lg...mp-unlock-lg-g3-twrp-d852-d852g-f400-t2900614) , then a custom rom like CM13, AICP, or any other rom with root support built in. If downgrading doesn't work, I don't think there is any way to root on 6.0.
Also, I'm new here. :3
Click to expand...
Click to collapse
Do i need to have root for the first option or can i just connect the phone to the PC and do the commands without root?
j_ras12 said:
Do i need to have root for the first option or can i just connect the phone to the PC and do the commands without root?
Click to expand...
Click to collapse
No, you don't need root for the first one, you just need to go to developer options (enable by going in to 'About Phone' section of settings, and tapping on the 'Build Number' row 7 times) and enable ADB/USB Debugging (it might be called either). Then, you need an ADB interface for your computer (Follow here: https://forum.xda-developers.com/showthread.php?t=2317790) so you can use ADB. After this, just connect your phone to your computer and open up a command prompt (admin isn't required, but use it anyways) and type 'adb devices' to verify your device is up and running. When you do this, your phone should ask whether it should allow debugging from you computer in a small popup, so all you need to do is press 'allow.' Then, all you need to do is flash a custom recovery (Follow the instructions in the 'Bump!' link in the first post), and then flash a rom that has root. I'd recommend AICP (android ice cold project) or CRDroid, as they are both super stable and are on 7.1 nougat. Hope this helped.
Hello everyone!
I have a problem with my Samsung s4 mini LTE version, i was installing LineageOS 14.1 on it, but when i flash GApps 7.1 Aroma, the phone boots and a popup pops up and says "Setup wizard has stopped"! I have read on other threads that you need to pull down the notification panel to get into the settings, but the problem is, IT'S IMPOSSIBLE TO PULL DOWN THE NOTFICATION PANEL!
I have tried to flash it all over again and again and again, but it dosen't help :crying:
If someone have a solution for this, I would be so happy to hear what is is
PS. Sorry for my bad English it isn't my primary language...
Olivgamer05 said:
Hello everyone! I have a problem with my Samsung s4 mini LTE version, i was installing LineageOS 14.1 on it, but when i flash GApps 7.1 Aroma, the phone boots and a popup pops up and says "Setup wizard has stopped"!...
Click to expand...
Click to collapse
Your best bet is to post this question within the following Official LineageOS thread for your device.
https://forum.xda-developers.com/showthread.php?t=3471761
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
This may help or may not, but it could be one possible cause:
Did you boot lineageOS once before flashing gapps?
AFAIR for gapps to work properly, it needs to be flashed right after flashing a custom rom, without starting the custom rom in-between.
Or put another way, when the phone starts up normally for the first time, gapps already needs to be installed. otherwise it can't run its setup wizard correctly.
also, a common problem for crashes like this is missing permissions for system apps. And i think the setup wizard not running correctly on first boot can cause some. (note that lineageOS also has a setup wizard. not sure how they're chained today)
note that i'm intentionally fuzzy on the details. It is what I vaguely remember, and I'm just writing this as some help may be better than none.
I had this same problem but with a different device. Followed the directions to a T, but still no go. Also tried the 'pull down notifications' supposed 'fix', while I guess that worked for some, didn't work for me (and you) either.
Here's what did work: And yes, it goes against the directions (but I tried it anyway), **don't** install gapps before booting the new rom, install after booting and doing as minimal set up as you can.
I'm not certain why this worked for me, but it seems to be because of the 2 diff 'set up' wizards, and the way they communicate to ea other and other apps. If you look in the bug logs (for both Los and Gapps), this problem goes way back, with numerous fix attempts.
It worked for me to install them separately, I suppose it might for you also. Good Luck.
Olivgamer05 said:
Hello everyone!
I have a problem with my Samsung s4 mini LTE version, i was installing LineageOS 14.1 on it, but when i flash GApps 7.1 Aroma, the phone boots and a popup pops up and says "Setup wizard has stopped"! I have read on other threads that you need to pull down the notification panel to get into the settings, but the problem is, IT'S IMPOSSIBLE TO PULL DOWN THE NOTFICATION PANEL!
I have tried to flash it all over again and again and again, but it dosen't help :crying:
If someone have a solution for this, I would be so happy to hear what is is
PS. Sorry for my bad English it isn't my primary language...
Click to expand...
Click to collapse
Aroma is to big you can only use micro or nano or pico gapps on S4 Mini