Related
I saw that there was a similar thread in the Epic 4G forum, but I wanted to make sure before I start trying something that might mess up the phone even further. My wife's vibrant will start having everything force close on her after a few weeks. This has happened on 2 or three different ROMs, and I'm not sure what's causing it. I saw the similar thread where it might be related to "journaling", but we don't change her battery out at all or even reboot the phone that often, so I'm not sure if its the same issue. I've done a reset of her phone a few times, but I'm on a GB ROM so it doesn't go completely back to factory. Should I try to ODIN to stock? Any ideas why this happens? Thanks in advance.
Try fixing permissions in CWM first and see if that helps.
Sent from my SGH-T959 using xda premium
Fix permissions worked for a while, but not anymore. Everything's force closing again. Will the journaling fix help?
Anybody have any ideas? Gonna wipe then install a newer ROM, but I want to make sure this doesn't happen again.
Only titanium the "necessary" apps that you wanna keep your data from. Then uninstall it - often I find that this helps for some odd reason.
Sent from my SGH-T959 using xda premium
chairhome said:
I saw that there was a similar thread in the Epic 4G forum, but I wanted to make sure before I start trying something that might mess up the phone even further. My wife's vibrant will start having everything force close on her after a few weeks. This has happened on 2 or three different ROMs, and I'm not sure what's causing it. I saw the similar thread where it might be related to "journaling", but we don't change her battery out at all or even reboot the phone that often, so I'm not sure if its the same issue. I've done a reset of her phone a few times, but I'm on a GB ROM so it doesn't go completely back to factory. Should I try to ODIN to stock? Any ideas why this happens? Thanks in advance.
Click to expand...
Click to collapse
Get into recovery:
wipe dalvik
wipe cache
fix permissions
reboot
wait 10 mins reboot into recovery again
fix permissions
reboot
open rom manager [worth its weight in gold!]
fix permissions
reboot
Thats what I did with my cm7.1.0.1 but I also installed eugenes streamline 110411 ver and [knock on wood] havnt had any more issues with fc's.
And yes even if you follow the installs to a "T" some of us still have the FC issue!
Good luck!
3 weeks later and I'm back to square one. I'll try the above, if it doesn't work, i'll have to wipe and reinstall. thanks. What's eugene's streamline?
Id flash to stock, flashing different roms wont help if theres a ghost in the machine, what launcher are you running...touchwiz sucks on my wimpy replacement phone.
Sugartibbs said:
Id flash to stock, flashing different roms wont help if theres a ghost in the machine, what launcher are you running...touchwiz sucks on my wimpy replacement phone.
Click to expand...
Click to collapse
MIUI's launcher. I'll probably try flashing to stock soon. :-(
No go. I'll have to look into Eugene's streamlined 110411
ok just for future sake, 3 rule's of flashing,
it's better to reinstall your applications manually then to trust titanium when bouncing between roms with different frameworks, versions, partitions, etc.
always flash from stock unless your updating a weekly rom ie cm7/miui
after flashing power off screen and have a cup of coffee/beer/shower. give the OS time to do all it's background configurations and setup.
now if you follow those 3 rules you "should" have no real issues.
I had used the amaze 4g all in one tool kit to unlock my bootloader, install a custom recovery, and then installed a custom rom (bullet proof 2.5) along with the provided kernel to go with it.
The phone worked great for a few days, then I noticed that it was acting like the wireless network radios were turned off in the software. They were still enabled so I rebooted and it fixed the problem for a little while.
Now my phone will only give me the com.android.phone has stopped working error and will not let me turn on the wireless network radios.
I have tried complete wipe of the phone and re-installation of the custom rom. I have tried different, yet still recommend, custom kernels, as well as different recoveries all with the same issue.
Any help would be greatly appreciated. I tried searching with out any good results.
Thanks.
Are you a Tmobile user?
Double0EK said:
Are you a Tmobile user?
Click to expand...
Click to collapse
Yeah. Even tried a new simcard even though I didnt think it would do any good.
toyoter91 said:
I had used the amaze 4g all in one tool kit to unlock my bootloader, install a custom recovery, and then installed a custom rom (bullet proof 2.5) along with the provided kernel to go with it.
The phone worked great for a few days, then I noticed that it was acting like the wireless network radios were turned off in the software. They were still enabled so I rebooted and it fixed the problem for a little while.
Now my phone will only give me the com.android.phone has stopped working error and will not let me turn on the wireless network radios.
I have tried complete wipe of the phone and re-installation of the custom rom. I have tried different, yet still recommend, custom kernels, as well as different recoveries all with the same issue.
Any help would be greatly appreciated. I tried searching with out any good results.
Thanks.
Click to expand...
Click to collapse
are you running joes "one good rom"? dude it says right in the op
Attention 2: on the first start "com.android.phone" process will FC, it is normal.
It's because of Toggle2G app. Just open that app and give it permission to run.
mrmako777 said:
are you running joes "one good rom"? dude it says right in the op
Attention 2: on the first start "com.android.phone" process will FC, it is normal.
It's because of Toggle2G app. Just open that app and give it permission to run.
Click to expand...
Click to collapse
I actually stated in my first post what rom I was running when all this happened.
I have tried Joes "one good rom" and followed all his kernel and set up instructions with no luck. On his rom I don't get the error message, but all of the wireless network options are grayed out. I am starting to think it might be something hardware.
toyoter91 said:
I actually stated in my first post what rom I was running when all this happened.
I have tried Joes "one good rom" and followed all his kernel and set up instructions with no luck. On his rom I don't get the error message, but all of the wireless network options are grayed out. I am starting to think it might be something hardware.
Click to expand...
Click to collapse
doh! shame on me for not seeing that i would say if worse comes to worse, reflash the stock rom and see if youre up and running. if its still not working, then id say maybe send it in for warranty
mrmako777 said:
doh! shame on me for not seeing that i would say if worse comes to worse, reflash the stock rom and see if youre up and running. if its still not working, then id say maybe send it in for warranty
Click to expand...
Click to collapse
No worries. I am actually in the process of finding and flashing the stock rom back onto it, going to try and put everything back to stock and see what happens.
Having a similar problem
toyoter91 said:
No worries. I am actually in the process of finding and flashing the stock rom back onto it, going to try and put everything back to stock and see what happens.
Click to expand...
Click to collapse
Hi. I decided to add to this thread instead of starting a new one since i am having a similar problem. The originator never said if he was able to solve the problem. I was using the Energy ROM (http://forum.xda-developers.com/showthread.php?t=1362759) (ICS, S-ON) and everything was fine. I decided to try the Speed ROM (project "butter" http://forum.xda-developers.com/showthread.php?t=1623184) which is Jellybean based. I did a full wipe, and after installing it I got the same com.android.phone error. I got it to stop, but then started having other issues like Superuser, BusyBox, and Titanium Backup unable to get root access. Unable to find any other solutions, I decided to restore to stock, which went fine (well I had to try a few times as I haven't done it before). After that, and having the phone working fine back at stock ICS I reflashed the Speed ROM. I ended up with the same issue. I wiped again and returned to the Energy ROM and it seems to be working fine. My quesiton is, why is the Speed ROM not working on my phone? When it flashed there were no issues, and I followed the instrucitons exactly.
I would post in the Speed ROM forum but I don't have enough posts yet since I am usually able to find answers by searching.
BillyD325 said:
Hi. I decided to add to this thread instead of starting a new one since i am having a similar problem. The originator never said if he was able to solve the problem. I was using the Energy ROM (http://forum.xda-developers.com/showthread.php?t=1362759) (ICS, S-ON) and everything was fine. I decided to try the Speed ROM (project "butter" http://forum.xda-developers.com/showthread.php?t=1623184) which is Jellybean based. I did a full wipe, and after installing it I got the same com.android.phone error. I got it to stop, but then started having other issues like Superuser, BusyBox, and Titanium Backup unable to get root access. Unable to find any other solutions, I decided to restore to stock, which went fine (well I had to try a few times as I haven't done it before). After that, and having the phone working fine back at stock ICS I reflashed the Speed ROM. I ended up with the same issue. I wiped again and returned to the Energy ROM and it seems to be working fine. My quesiton is, why is the Speed ROM not working on my phone? When it flashed there were no issues, and I followed the instrucitons exactly.
I would post in the Speed ROM forum but I don't have enough posts yet since I am usually able to find answers by searching.
Click to expand...
Click to collapse
That's a common problem with SpeedRom and some other as well. Re-flash the SpeedRom, after it boot-up, go to Google Play store and download SuperSU -not Superuser -, open SuperSU and update binary. After that you can install busy box and run Titanium ....
antiquezip said:
That's a common problem with SpeedRom and some other as well. Re-flash the SpeedRom, after it boot-up, go to Google Play store and download SuperSU -not Superuser -, open SuperSU and update binary. After that you can install busy box and run Titanium ....
Click to expand...
Click to collapse
Thank you! After I posted I ran across somehting in the speed rom thread that made me go back to the original post. Sure enough, there is a download link for SuperSU which it says you need to flash to gain root after installng the ROM. I guess I read the instructions above, scrolled down to the rom download link, and then stopped. I will try this again with what you suggested when I have time in the next day or two.
BillyD325 said:
Thank you! After I posted I ran across somehting in the speed rom thread that made me go back to the original post. Sure enough, there is a download link for SuperSU which it says you need to flash to gain root after installng the ROM. I guess I read the instructions above, scrolled down to the rom download link, and then stopped. I will try this again with what you suggested when I have time in the next day or two.
Click to expand...
Click to collapse
I had this error factory reset stop the error.
This belongs in Q&A.
Thread Moved.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"If you choose not to decide, you still have made a choice"
Sent from my Galaxy Note (i717), using XDA Premium.
Hello.
I know that you are all incredibly busy and I sincerely hope that this does not inconvenience anyone.
Yesterday, I was following this very helpful guide for my Samsung Fascinate, (http://forum.xda-developers.com/showthread.php?t=1238070), and I encountered a big problem.
On Section 4, Step 18 ("Once the rom finishes installing reboot."), I did not get the option to immediately reboot. With this Jelly Bean rom, Super Nexus (http://forum.xda-developers.com/showthread.php?t=2238075), I immediately found myself in Team Win Recovery 2.5.0.0.
After initially failing to install Super Nexus via this new Recovery software, I found out that I must have both the "Inject TWRP after Install" and the "Zip file signature verification" options disabled before it will succeed.
However, even after doing this, I noticed that the phone would not restart into the Super Nexus ROM properly. For some reason, it went right back to Team Win Recovery Project 2.5.0.0. Powering off the phone, removing the battery, and then putting it back in and starting the phone again allowed me to access the Rom properly. Afterward, I was able to install the GAPPS file which was provided by the Super Nexus thread (http://forum.xda-developers.com/showthread.php?t=2238075), but rebooting the phone via the power menu did not send me back into Clockwork Mod. Again, I was directed to TWRP and had to install it through there. Frankly, it seems this is all I can access now and Clockwork Mod is simply gone forever. This isn't really a problem I guess, but it is rather strange.
Besides this, my only real functional problem is that Google Search is unworkable. I get the infamous "Unfortunately Google Search has stopped" error message, but everything else seems to run fine. (It is certainly much faster than the Stock Gingerbread ROM.)
My question then is simply this: Why is this ROM so very different from all the others? The guide linked above (http://forum.xda-developers.com/showthread.php?t=1238070) seems to work for 99% of all users....
Why was I so different? Did I do something obviously wrong that anyone can think of? I tried to follow the steps slowly and accurately but I'm still left with a broken Google Search and tons of confusion.
Have you updated the Google Search app using the Play Store? Updating usually fixes any issue I have with it
Sent from my SCH-I500 using Tapatalk 4
SimplyShane said:
Hello.
I know that you are all incredibly busy and I sincerely hope that this does not inconvenience anyone.
Yesterday, I was following this very helpful guide for my Samsung Fascinate, (http://forum.xda-developers.com/showthread.php?t=1238070), and I encountered a big problem.
On Section 4, Step 18 ("Once the rom finishes installing reboot."), I did not get the option to immediately reboot. With this Jelly Bean rom, Super Nexus (http://forum.xda-developers.com/showthread.php?t=2238075), I immediately found myself in Team Win Recovery 2.5.0.0.
After initially failing to install Super Nexus via this new Recovery software, I found out that I must have both the "Inject TWRP after Install" and the "Zip file signature verification" options disabled before it will succeed.
However, even after doing this, I noticed that the phone would not restart into the Super Nexus ROM properly. For some reason, it went right back to Team Win Recovery Project 2.5.0.0. Powering off the phone, removing the battery, and then putting it back in and starting the phone again allowed me to access the Rom properly. Afterward, I was able to install the GAPPS file which was provided by the Super Nexus thread (http://forum.xda-developers.com/showthread.php?t=2238075), but rebooting the phone via the power menu did not send me back into Clockwork Mod. Again, I was directed to TWRP and had to install it through there. Frankly, it seems this is all I can access now and Clockwork Mod is simply gone forever. This isn't really a problem I guess, but it is rather strange.
Besides this, my only real functional problem is that Google Search is unworkable. I get the infamous "Unfortunately Google Search has stopped" error message, but everything else seems to run fine. (It is certainly much faster than the Stock Gingerbread ROM.)
My question then is simply this: Why is this ROM so very different from all the others? The guide linked above (http://forum.xda-developers.com/showthread.php?t=1238070) seems to work for 99% of all users....
Why was I so different? Did I do something obviously wrong that anyone can think of? I tried to follow the steps slowly and accurately but I'm still left with a broken Google Search and tons of confusion.
Click to expand...
Click to collapse
Twrp should be the recovery that is included with this ROM.
If you want a cwm recovery,, look at my thread in the general section.
Unjustdev said inject doesn't work.
For Google search:
I would try wiping dalvik cache and fixing permissions from recovery.
skepticmisfit said:
Have you updated the Google Search app using the Play Store? Updating usually fixes any issue I have with it
Sent from my SCH-I500 using Tapatalk 4
Click to expand...
Click to collapse
This did indeed fix the issue. :laugh:
Now, why it was there to begin with...I don't know. The Super Nexus thread makes no mention of this...
SimplyShane said:
This did indeed fix the issue. :laugh:
Now, why it was there to begin with...I don't know. The Super Nexus thread makes no mention of this...
Click to expand...
Click to collapse
I think Google just automatically updates for most people since they may have other devices running JB or they ran other ROMs. Starting with 4.1, Google automatically backs up every app you install, and when you set up a new device, it'll restore all the apps you had installed previously and it usually updates apps as well.
I take that back, you have to update all system apps manually. But I think most people know to do that.
Sent from my SCH-I500 using Tapatalk 4
skepticmisfit said:
I think Google just automatically updates for most people since they may have other devices running JB or they ran other ROMs. Starting with 4.1, Google automatically backs up every app you install, and when you set up a new device, it'll restore all the apps you had installed previously and it usually updates apps as well.
I take that back, you have to update all system apps manually. But I think most people know to do that.
Sent from my SCH-I500 using Tapatalk 4
Click to expand...
Click to collapse
Thanks for the info.
Galaxy Note 3 Can't send SMS or phone calls, but was receive SMS and calls at first
Hangouts was combined with SMS originally
Device was saying “No APN specified for the device”. When trying to go to Settings>Mobile network settings>Access Point Names, I get error message “Unfortunately, the process com.android.phone has stopped”
Was running cm-11-20140905-NIGHTLY-hltespr.zip at time of problem
Tried wipe/factory reset to 'clean' install of CM11, did not resolve issue
Tried updating to the most recent CM11 nightly: cm-11-20140908-NIGHTLY-hltespr.zip
This did not resolve the issue
Tried going back to an older nightly: cm-11-20140904-NIGHTLY-hltespr.zip
Did not resolve issue
Tried flashing a rooted stock ROM: http://stockroms.net/file/GalaxyNote3/SM-N900P/rooted/SM-N900P-HLTESPR-MJ4-Odex-v2.zip[1]
Did not resolve issue, this put the device into a boot loop, would not get past the Galaxy Note 3 splash screen
Flashed back to the cm-11-20140905-Nightly-hltespr.zip, this fixed the boot loop, but now I'm getting a different message
Wiped data and cache in between each flashing of a new ROM
When trying to call from the phone, it says “Mobile network not available”, and still can't get SMS to send. It no longer gives me any message about “No APN specified”, but the same error happens if I go to Settings>Mobile network settings>Access Point Names
I've found this thread but it only seems to be related to the S3/S4 http://forum.xda-developers.com/showthread.php?t=2657822[2]
Also found this: http://www.reddit.com/r/cyanogenmod/comments/1zlsrk/cant_send_sms_after_fresh_cm11_install/[3]
Google Voice is not installed, and I can't find anything in the settings about Voice+
I can't go back to CM10 because there doesn't appear to be a CM ROM for the Note 3 earlier than CM11
I've found threads with similar issues, but they are all for either Galaxy S phones, or for the Note 2. There seems to be little to no information about the Note 3 regarding this issue
At this point, the Note 3 can't send or receive any mobile data, can't make calls, and can't send messages. It's basically a WiFi only device at this point
Perhaps I need to try updating the radio? I'm honestly not sure. But there again, I can't seem to find much on the Note 3
If someone could help me out with this it would be much appreciated, as its my sister's phone and she's going to go crazy without it
EDIT:
One thing I forgot about, somewhere in there I also tried flashing a ROM for hlte, as opposed to hltespr. I think that at point is when all data stopped working
Some have suggested flashing a stable version of CyanogenMod, but there doesn't appear to be one for the Note 3, unless I'm missing something
Warlock0187 said:
Galaxy Note 3 Can't send SMS or phone calls, but was receive SMS and calls at first
Hangouts was combined with SMS originally
Device was saying “No APN specified for the device”. When trying to go to Settings>Mobile network settings>Access Point Names, I get error message “Unfortunately, the process com.android.phone has stopped”
Was running cm-11-20140905-NIGHTLY-hltespr.zip at time of problem
Tried wipe/factory reset to 'clean' install of CM11, did not resolve issue
Tried updating to the most recent CM11 nightly: cm-11-20140908-NIGHTLY-hltespr.zip
This did not resolve the issue
Tried going back to an older nightly: cm-11-20140904-NIGHTLY-hltespr.zip
Did not resolve issue
Tried flashing a rooted stock ROM: http://stockroms.net/file/GalaxyNote3/SM-N900P/rooted/SM-N900P-HLTESPR-MJ4-Odex-v2.zip[1]
Did not resolve issue, this put the device into a boot loop, would not get past the Galaxy Note 3 splash screen
Flashed back to the cm-11-20140905-Nightly-hltespr.zip, this fixed the boot loop, but now I'm getting a different message
Wiped data and cache in between each flashing of a new ROM
When trying to call from the phone, it says “Mobile network not available”, and still can't get SMS to send. It no longer gives me any message about “No APN specified”, but the same error happens if I go to Settings>Mobile network settings>Access Point Names
I've found this thread but it only seems to be related to the S3/S4 http://forum.xda-developers.com/showthread.php?t=2657822[2]
Also found this: http://www.reddit.com/r/cyanogenmod/comments/1zlsrk/cant_send_sms_after_fresh_cm11_install/[3]
Google Voice is not installed, and I can't find anything in the settings about Voice+
I can't go back to CM10 because there doesn't appear to be a CM ROM for the Note 3 earlier than CM11
I've found threads with similar issues, but they are all for either Galaxy S phones, or for the Note 2. There seems to be little to no information about the Note 3 regarding this issue
At this point, the Note 3 can't send or receive any mobile data, can't make calls, and can't send messages. It's basically a WiFi only device at this point
Perhaps I need to try updating the radio? I'm honestly not sure. But there again, I can't seem to find much on the Note 3
If someone could help me out with this it would be much appreciated, as its my sister's phone and she's going to go crazy without it
EDIT:
One thing I forgot about, somewhere in there I also tried flashing a ROM for hlte, as opposed to hltespr. I think that at point is when all data stopped working
Some have suggested flashing a stable version of CyanogenMod, but there doesn't appear to be one for the Note 3, unless I'm missing something
Click to expand...
Click to collapse
If all else fails try flasing back to stock, update profile, update prl then reroot and flash the ROM. Please follow the OP to the "T" and you should be good!
flynhawn2002 said:
If all else fails try flasing back to stock, update profile, update prl then reroot and flash the ROM. Please follow the OP to the "T" and you should be good!
Click to expand...
Click to collapse
Do you know where I can find a stock ROM? The one I have been able to find has not worked. Also, does reinstalling a stock room cause the phone to be unrooted? I thought I read somewhere that there has not been an unroot for the Note 3 released yet
I will attempt to locate a stock ROM on my own and attempt to update Profile and PRL and go from there. Thanks for the assistance!
Warlock0187 said:
Do you know where I can find a stock ROM? The one I have been able to find has not worked. Also, does reinstalling a stock room cause the phone to be unrooted? I thought I read somewhere that there has not been an unroot for the Note 3 released yet
I will attempt to locate a stock ROM on my own and attempt to update Profile and PRL and go from there. Thanks for the assistance!
Click to expand...
Click to collapse
In the development section you should be able to find a stock rom. Yes, by installing a stock rom you will loose root its as if you just got it from the store, lol.
flynhawn2002 said:
In the development section you should be able to find a stock rom. Yes, by installing a stock rom you will loose root its as if you just got it from the store, lol.
Click to expand...
Click to collapse
I was under the impression that you could be running the stock ROM and still have root access, I guess this is incorrect?
Warlock0187 said:
I was under the impression that you could be running the stock ROM and still have root access, I guess this is incorrect?
Click to expand...
Click to collapse
No, when I say stock its fresh, no root. It will be the same stockness as when you first purchase your phone!
flynhawn2002 said:
No, when I say stock its fresh, no root. It will be the same stockness as when you first purchase your phone!
Click to expand...
Click to collapse
Hmm interesting. I always thought that what software you're running and whether or not you have root access are two separate things. Don't they have rooted Stock ROMs?
Anyway, its irrelevant at this point. I've found a stock ROM I'm hoping will work, will update either way
Warlock0187 said:
Hmm interesting. I always thought that what software you're running and whether or not you have root access are two separate things. Don't they have rooted Stock ROMs?
Anyway, its irrelevant at this point. I've found a stock ROM I'm hoping will work, will update either way
Click to expand...
Click to collapse
Did you ever find a solution to this problem? I am having the same issue. I flashed a hlte rom rather than a hltespr and lost SMS and voice, but my data is still working. I tried to restore my backup and it still isn't working. Any help is appreciated.
would flashing a correct modem solve their problem?
kakiesz said:
Did you ever find a solution to this problem? I am having the same issue. I flashed a hlte rom rather than a hltespr and lost SMS and voice, but my data is still working. I tried to restore my backup and it still isn't working. Any help is appreciated.
Click to expand...
Click to collapse
Just flash an htlespr ROM and you'll be fine.
Flashed back to a Stock ROM, and everything works fine again.
Waiting until a milestone is released to try re-rooting and flashing CM again
After migrating to a custom ROM (i tried both CM13 and Resurrection Remix) I seem to have corrupted some stock files that i can't reset. I can get back to TWRP no problem, but despite wiping every partition and installing a stock ROM--i still get crashes whenever i open the "Lock Screen Settings" in the Setting App I get the "unfortunately lock screen settings has stopped". All the stock restore files i seem to find are for MM, i just want to get back to LP.
The link from the other thread: http://forum.xda-developers.com/tmobile-lg-v10/help/trying-to-revert-to-stock-t3276181 looks like it might solve my issue, but it doesn't work for me. https://www.androidfilehost.com/?fid=24269982086988331
Will happily bestow "Thanks!" on anyone who can help me get this resolved or for that matter tries. Thanks in advance for helping a wayward noob.
jaysonic88 said:
After migrating to a custom ROM (i tried both CM13 and Resurrection Remix) I seem to have corrupted some stock files that i can't reset. I can get back to TWRP no problem, but despite wiping every partition and installing a stock ROM--i still get crashes whenever i open the "Lock Screen Settings" in the Setting App I get the "unfortunately lock screen settings has stopped". All the stock restore files i seem to find are for MM, i just want to get back to LP.
The link from the other thread: http://forum.xda-developers.com/tmobile-lg-v10/help/trying-to-revert-to-stock-t3276181 looks like it might solve my issue, but it doesn't work for me. https://www.androidfilehost.com/?fid=24269982086988331
Will happily bestow "Thanks!" on anyone who can help me get this resolved or for that matter tries. Thanks in advance for helping a wayward noob.
Click to expand...
Click to collapse
Since all the "stock" ROMs i found continued to have the problem, i ended up taking the plunge and using the method described here http://forum.xda-developers.com/tmobile-lg-v10/development/rom-v10h901v20estock-customized-t3360240 to migrate to Marshmallow with root. Worked like a charm! Only issue is it seems to have broke my Wifi Calling as i now get REG99 error. Overall a small price to pay, but if anyone has any thoughts would love to hear them.
jaysonic88 said:
Since all the "stock" ROMs i found continued to have the problem, i ended up taking the plunge and using the method described here http://forum.xda-developers.com/tmobile-lg-v10/development/rom-v10h901v20estock-customized-t3360240 to migrate to Marshmallow with root. Worked like a charm! Only issue is it seems to have broke my Wifi Calling as i now get REG99 error. Overall a small price to pay, but if anyone has any thoughts would love to hear them.
Click to expand...
Click to collapse
Which Part 2 did you flash?
Double0EK said:
Which Part 2 did you flash?
Click to expand...
Click to collapse
I believe i used the newer of the part 2's---V10_H901_V20E_Stock_MM_P2-3.zip
Now that you brought it up i googled it and it looks like there's some known issues there. Is **P2-2.zip the correct one to use then? Can i go reload part 1 and the new part 2 in TWRP? The latest thread is like 50 pages so reading through it now. Sorry if this question is redundant.
jaysonic88 said:
I believe i used the newer of the part 2's---V10_H901_V20E_Stock_MM_P2-3.zip
Now that you brought it up i googled it and it looks like there's some known issues there. Is **P2-2.zip the correct one to use then? Can i go reload part 1 and the new part 2 in TWRP? The latest thread is like 50 pages so reading through it now. Sorry if this question is redundant.
Click to expand...
Click to collapse
Re-read the OP, looks like there's been some changes. I'll reflash the new part2 and see how that works. thanks!
jaysonic88 said:
Re-read the OP, looks like there's been some changes. I'll reflash the new part2 and see how that works. thanks!
Click to expand...
Click to collapse
That fixed it! Also like the Android boot image/graphic better than the white Tmo screen.
Thanks Double0EK!
jaysonic88 said:
That fixed it! Also like the Android boot image/graphic better than the white Tmo screen.
Thanks Double0EK!
Click to expand...
Click to collapse
Uhhh..I didnt do much. But you're welcome.