Database Users

No data and poor signal on ANY ROM except stock.

Hey guys.
Im having a problem connecting to the Verizon mobile network when Im on ANY ROM besides Stock 4.1.2.
Im guessing this is a radio/baseband problem?
Any help on the subject is MUCH appreciated.

I've seen various posts where folks on non-stock ROMs have signal issues. On my previous RAZR and now RAZR M only on stock do I get a solid signal. Non-stock gives me only fair 4G and drops to nothing when venture into 3G. Argggh's kernel based off stock I believe did help some but not give me as good a connection as stock. Suspect Moto propriety source would be needed. So for a solid connection and best battery life I stay on stock.

Maybe try MIUI?
cvhovey said:
I've seen various posts where folks on non-stock ROMs have signal issues. On my previous RAZR and now RAZR M only on stock do I get a solid signal. Non-stock gives me only fair 4G and drops to nothing when venture into 3G. Argggh's kernel based off stock I believe did help some but not give me as good a connection as stock. Suspect Moto propriety source would be needed. So for a solid connection and best battery life I stay on stock.
Click to expand...
Click to collapse
Although this may be true, I have experienced great battery life and few signal issues with the MIUI v5 ROM for our device.

So flashing a different Radio wouldnt help at all?

bad reception on any rom other than stock
lukkypuggy said:
So flashing a different Radio wouldnt help at all?
Click to expand...
Click to collapse
Hi lukkypuggy, I am having the same problem. Did you ever resolve it? Please let me know, I am really struggling to get any other rom other than stock to work!

kevin01sb said:
Hi lukkypuggy, I am having the same problem. Did you ever resolve it? Please let me know, I am really struggling to get any other rom other than stock to work!
Click to expand...
Click to collapse
Read
http://forum.xda-developers.com/showthread.php?t=2346623
---------- Post added at 12:39 PM ---------- Previous post was at 12:35 PM ----------
No matter what custom rom you flash you must restore the stock partition first.
http://forum.xda-developers.com/showthread.php?t=2391641

Don't know if it's placebo or not, but I've found the.4.4 bases Roms seem to be a bit better than 4.2 and 4.3 or CM 10.1 or CM 10.2.
As a matter of fact, I just went back to a DST stock ROM to rule that out as a problem. Back on CM11 and there's virtually no difference.
Sent from my XT907 using Tapatalk

aviwdoowks said:
Read
http://forum.xda-developers.com/showthread.php?t=2346623
---------- Post added at 12:39 PM ---------- Previous post was at 12:35 PM ----------
No matter what custom rom you flash you must restore the stock partition first.
http://forum.xda-developers.com/showthread.php?t=2391641
Click to expand...
Click to collapse
Thanks for the fast response aviwdoowks! I ended up using Matts Util to flash back to stock rom. Then re flashed CWM recovery. 4g is back, wifi works great. All is working perfect !!!!! Backup has been made, so this time I will not get into trouble and can just flash back to stock if anything happens.
When I have some time I will try loading CM10.1 on it again and see If I can get the phone to work with a custom rom and maintain good 4g reception. If not, then I guess there is more to do... Thanks again!

kevin01sb said:
Thanks for the fast response aviwdoowks! I ended up using Matts Util to flash back to stock rom. Then re flashed CWM recovery. 4g is back, wifi works great. All is working perfect !!!!! Backup has been made, so this time I will not get into trouble and can just flash back to stock if anything happens.
When I have some time I will try loading CM10.1 on it again and see If I can get the phone to work with a custom rom and maintain good 4g reception. If not, then I guess there is more to do... Thanks again!
Click to expand...
Click to collapse
Twrp & cwmr both do not restore all of the partitions.
That is why I made my restore thread.
You can be on a custom ROM & have no data you still have to go back to Rsd to fix!!!!!
But data must be wiped before Rsd.
BTW
Rant
I am on bone stock to fix my SD swap...
Does it ever suck! Aosp keyboard & my favorite browser maxthon HD. Day & night.
Advice: get mhous33's DST at least, smart keyboard & maxthon hd !!
Tapatalk & xda app are not as good.
I cannot edit the last line!
keyboard,
---------- Post added at 10:31 AM ---------- Previous post was at 10:21 AM ----------
& get host ad blocking.
End rant.
...the op may have your same problem.
More rant : the aosp KB sucks, bone stock rom sucks, WiFi is better on mhous33's DST
OK I will post a new thread bout it...

6.0 vs 6.0.1

Hey guys,
Considering that there is much controversy and curiosity as to what so far seems to be the best update to have, 6.0 or 6.0.1, what were your experiences?
6.0.1 is not yet available for many devices as it seems, and the only way to get it is with custom ROMS. However, 6.0 is readily available, with just root needing to be installed.
With this said, is it worth updating to 6.0.1 through a custom ROM then, and can you possibly give some suggestions?

Well, I personally am kind of OCD about it and don't feel right if I don't have the latest version of android, so having 6.0.1 is sort of an imperative, especially after you experience things like the lack of a delay in the "paste" popup when copying & pasting text, the new emojis (considering 3/4 of what I do on my phone is texting honestly), stuff like that.
However I've had a hell of a time with finding functional AOSP ROMs. Out of the ones that aren't dead with their devs totally MIA (which is half of them), the ones that flash OK usually have some sort of radio problem which I've been struggling with on multiple ROMs even just today, and finally the ones that run mostly ok as a daily driver still have little quirks like random reboots. So try some out but if you end up pulling your hair out like me, might wanna just jump ship and stick to stock, that's what I'm seriously considering at this point.

jDally987 said:
Well, I personally am kind of OCD about it and don't feel right if I don't have the latest version of android, so having 6.0.1 is sort of an imperative, especially after you experience things like the lack of a delay in the "paste" popup when copying & pasting text, the new emojis (considering 3/4 of what I do on my phone is texting honestly), stuff like that.
However I've had a hell of a time with finding functional AOSP ROMs. Out of the ones that aren't dead with their devs totally MIA (which is half of them), the ones that flash OK usually have some sort of radio problem which I've been struggling with on multiple ROMs even just today, and finally the ones that run mostly ok as a daily driver still have little quirks like random reboots. So try some out but if you end up pulling your hair out like me, might wanna just jump ship and stick to stock, that's what I'm seriously considering at this point.
Click to expand...
Click to collapse
Thank you! I cannot press the Thank button as I'm limited to 8 a day Do you see any performance difference between 6.01 and 6.0.1 though?
I think I will just stick to stock. But most likely going to go with TruPure XMM 2.9. It seems to be stable, and the developer seems to be active! Props to him.

Stock 6.0.1 with franken kernel is better then any custom ROM so far.

lafester said:
Stock 6.0.1 with franken kernel is better then any custom ROM so far.
Click to expand...
Click to collapse
How is the battery life (SOT) doing for you, relative to your personal usage habits? The only reason why I'm staying on TruPureX 2.9 with 6.0 and Frankenkernel is because of the debloating the ROM contains while keeping the stock Moto features.

lafester said:
Stock 6.0.1 with franken kernel is better then any custom ROM so far.
Click to expand...
Click to collapse
Are you running the version in this thread? http://forum.xda-developers.com/mot...rom-stock-rooted-debloated-x1575-6-0-t3262242
If not, which version of 6.0.1 do you recommend? I am losing hope that there is going to be another stock release for this device, which sucks since I have only had it since March...

lafester said:
Stock 6.0.1 with franken kernel is better then any custom ROM so far.
Click to expand...
Click to collapse
Stock 6.01 with the stock kernel working fine here. Don't see the point in installing a custom kernel when you need to downgrade the modem back to the one included in MM6.0, makes no sense.

You must not have a 1575. Franken is also much better then stock kernel.
---------- Post added at 04:40 PM ---------- Previous post was at 04:38 PM ----------
jdgesmlls said:
Are you running the version in this thread? http://forum.xda-developers.com/mot...rom-stock-rooted-debloated-x1575-6-0-t3262242
If not, which version of 6.0.1 do you recommend? I am losing hope that there is going to be another stock release for this device, which sucks since I have only had it since March...
Click to expand...
Click to collapse
No I'm running the one posted in general, currently Eu version but I started with Asia. I don't think there is any difference though.

lafester said:
You must not have a 1575. Franken is also much better then stock kernel.
---------- Post added at 04:40 PM ---------- Previous post was at 04:38 PM ----------
No I'm running the one posted in general, currently Eu version but I started with Asia. I don't think there is any difference though.
Click to expand...
Click to collapse
You have a link? There are a few in General... Is it just a stock image or rooted/busybox etc.?

Stock image.

Downgrade to Marshmallow to avoid bootloop?

My old Nexus 5X has already died with the bootloop issue, now I don't want to my Nexus 6P to die too..
Should I downgrade it to marshmallow?
I know that most people are claiming this as an hardware issue, but I actually don't believe on it, since both 5X and 6P with two completely different brands are getting the same problem, at the same time.
I'm also thinking of moving to CyanogenMod 14.1 (Not sure if anything changes..)
Curently I'm on Stock 7.1.1 NMF26F + FLASH-N6P Kernel

No! Suit yourself, but I would simply upgrade to N4F26I and enjoy your phone. There is nothing wrong with running stock and you have a good kernel. Viva! Saúde!

Until it boot loops like so many of us have had happen. If you are in warranty, the company is swapping them out with little aggravation. If you are not in warranty then maybe you have a good point. I for one will be running RR 6.0.1 until some real info comes out. Once was enough for me.
Sent from my Nexus 6 using XDA-Developers Legacy app

rcoliveirajr said:
My old Nexus 5X has already died with the bootloop issue, now I don't want to my Nexus 6P to die too..
Should I downgrade it to marshmallow?
I know that most people are claiming this as an hardware issue, but I actually don't believe on it, since both 5X and 6P with two completely different brands are getting the same problem, at the same time.
I'm also thinking of moving to CyanogenMod 14.1 (Not sure if anything changes..)
Curently I'm on Stock 7.1.1 NMF26F + FLASH-N6P Kernel
Click to expand...
Click to collapse
You realize that CyanogenMod is dead and that there will be no further development? People have been having the boot loop problems with custom ROMs as well as stock. Mine bootloops every time I flash updates, switch ROMs or try to restore a backup. So far I've always been able to get out of it. If your bootloader is unlocked every boot loop isn't necessarily the boot loop of death. But if your bootloader is locked you have pretty limited options to try and fix the phone. If you feel more comfortable on Marshmallow then just stay on your current ROM. But if you are going to flash a custom ROM I would stay away from CyanogenMod.

jhs39 said:
You realize that CyanogenMod is dead and that there will be no further development? People have been having the boot loop problems with custom ROMs as well as stock. Mine bootloops every time I flash updates, switch ROMs or try to restore a backup. So far I've always been able to get out of it. If your bootloader is unlocked every boot loop isn't necessarily the boot loop of death. But if your bootloader is locked you have pretty limited options to try and fix the phone. If you feel more comfortable on Marshmallow then just stay on your current ROM. But if you are going to flash a custom ROM I would stay away from CyanogenMod.
Click to expand...
Click to collapse
I know that CM is dead, but probably there will be unofficial development. I was thinking about it, because I would still have Nougat instead of Marshmallow..
My January OTA has just arrived, and I just blocked the notification, but I'm really thinking to flash the stock Marshmallow..

rcoliveirajr said:
I know that CM is dead, but probably there will be unofficial development. I was thinking about it, because I would still have Nougat instead of Marshmallow..
My January OTA has just arrived, and I just blocked the notification, but I'm really thinking to flash the stock Marshmallow..
Click to expand...
Click to collapse
CM will be replaced by Lineage OS.
Sent from my Nexus 6P using Tapatalk

Does anyone downgrade to Marshmallow?
Would you guys recommend me to do it?

jhs39 said:
You realize that CyanogenMod is dead and that there will be no further development? People have been having the boot loop problems with custom ROMs as well as stock. Mine bootloops every time I flash updates, switch ROMs or try to restore a backup. So far I've always been able to get out of it. If your bootloader is unlocked every boot loop isn't necessarily the boot loop of death. But if your bootloader is locked you have pretty limited options to try and fix the phone. If you feel more comfortable on Marshmallow then just stay on your current ROM. But if you are going to flash a custom ROM I would stay away from CyanogenMod.
Click to expand...
Click to collapse
Why do you say stay away from CM? It is actually very stable. I've had no issues with it besides the battery crap on N. The dedicated CM maintainers are working on Lineage OS still. They have released a few nightly builds, but not sure if they are going to try and get a automatic build server up and running again for the OTA nightly builds.

Jammol said:
Why do you say stay away from CM? It is actually very stable. I've had no issues with it besides the battery crap on N. The dedicated CM maintainers are working on Lineage OS still. They have released a few nightly builds, but not sure if they are going to try and get a automatic build server up and running again for the OTA nightly builds.
Click to expand...
Click to collapse
Lineage is starting from scratch. My understanding is that CM ceased to be open source after it was sold and Lineage can't simply update CM ROMs because that code is owned by the company that owns CM. There will be no more official development of current CM ROMs so I can't understand why anyone would want to use their ROMs. There are other ROMs that are in active development and are updated regularly so why not use them instead of CM?

I know this thread hour into the weeds regarding CM but in reference to downgrading, as I said before it's a judgement call. The boot loop of death does not appear to be happening on 6.0.1 so it's all about what you can deal with if it goes south on 7.x.x
Sent from my Nexus 6 using XDA-Developers Legacy app

CyberpodS2 said:
I know this thread hour into the weeds regarding CM but in reference to downgrading, as I said before it's a judgement call. The boot loop of death does not appear to be happening on 6.0.1 so it's all about what you can deal with if it goes south on 7.x.x
Click to expand...
Click to collapse
Some people have said it has happened to them on MM. Not sure how true it is but who knows.
---------- Post added at 03:13 PM ---------- Previous post was at 03:08 PM ----------
jhs39 said:
Lineage is starting from scratch. My understanding is that CM ceased to be open source after it was sold and Lineage can't simply update CM ROMs because that code is owned by the company that owns CM. There will be no more official development of current CM ROMs so I can't understand why anyone would want to use their ROMs. There are other ROMs that are in active development and are updated regularly so why not use them instead of CM?
Click to expand...
Click to collapse
Lineage IS CM. It literally is only a name change. If you go to the GIT you'll see, or even go to the CM thread. It's just the company and name is dead. All the source files were moved by maintainers and it was all rebranded to be called LineageOS. They just no longer have the pockets to run things the way it used to be.
And as far as custom Roms go, they are all the same. They are all either based on AOSP, or the Stock(Google) firmware of the device. They all carry the same features that they renamed to whatever the name of the ROM is. That has always been the problem with stock Android devices.

I have a 6p that does not know Nougat yet, I'll stick to MM until further clarification.
No issues - latest MM, SuperSU 2.79, Xposed v87 and Franco v28.

jhs39 said:
Lineage is starting from scratch. My understanding is that CM ceased to be open source after it was sold and Lineage can't simply update CM ROMs because that code is owned by the company that owns CM. There will be no more official development of current CM ROMs so I can't understand why anyone would want to use their ROMs. There are other ROMs that are in active development and are updated regularly so why not use them instead of CM?
Click to expand...
Click to collapse
Do some more research before releasing false information. Lineage OS isnt starting from scratch lol. Do you follow their threads or github? Cyanogen 7 was my first ROM on HTC Inspire...and it was BEASTMODE. They were pioneers on a digital frontier, and in my book OG. The name may be dead but Lineage is here to stay and they have all the OPENSOURCE code. Long live Cyanogen!!!!!

Well I downgraded as soon as the bootloop threads started to pop. Sorry to say it died in a week. Signs before the bootloop death, heat up, battery discharges rapidly, then whilst I was in a middle of a call, it rebooted to bootloop of death.

Uggg
Sent from my Nexus 6 using XDA-Developers Legacy app

Bad news, and there isnt official answer from Google

I was running MM and never once upgraded to N or used any beta previews always on MM. And mine started the bootloop of death 2 days ago. So I would say no don't downgrade it won't improve your chances of avoiding it

seand88 said:
I was running MM and never once upgraded to N or used any beta previews always on MM. And mine started the bootloop of death 2 days ago. So I would say no don't downgrade it won't improve your chances of avoiding it
Click to expand...
Click to collapse
That's actually good to know since the overwhelming majority of people on these threads seem certain that Nougat is to blame. Were you doing anything in particular when the boot loop hit?
---------- Post added at 11:50 PM ---------- Previous post was at 11:48 PM ----------
dogmatism said:
Well I downgraded as soon as the bootloop threads started to pop. Sorry to say it died in a week. Signs before the bootloop death, heat up, battery discharges rapidly, then whilst I was in a middle of a call, it rebooted to bootloop of death.
Click to expand...
Click to collapse
Hopefully your phone was still under warranty. Sounds like you got a lemon.

jhs39 said:
That's actually good to know since the overwhelming majority of people on these threads seem certain that Nougat is to blame. Were you doing anything in particular when the boot loop hit?
Sorry for the late reply. I was not doing anything at all. It was sitting in a cup holder as I was driving and thats when I noticed it looping.
Click to expand...
Click to collapse

CyberpodS2 said:
Until it boot loops like so many of us have had happen. If you are in warranty, the company is swapping them out with little aggravation. If you are not in warranty then maybe you have a good point. I for one will be running RR 6.0.1 until some real info comes out. Once was enough for me.
Sent from my Nexus 6 using XDA-Developers Legacy app
Click to expand...
Click to collapse
i do not understand what this thread is supposed to be about, are you people saying that a stock nexus 6p with no kernel mods or custom rom can just spontaneous go into a boot loop? and now people saying it can happen on MM and it is not just a N issue? or is this only for modded devices? or is it mainy something that ahppens on stock N?
my 6p has major battery issues and drains at about 1% per minute on stock MM, i need to RMA the phone now and it is on MM
i want to root it and install xposed so i do not want N , i found this thread looking to find out if a downgrade from N to MM is possible
so if my phone gets returned to me on N or if they send a new phone to me and it is on N, then am i stuck with N or can i downgrade in back to stock MM?
phone is not modded to root no TWRP no backup will i be able to get on MM if they return my phone on N or send a new one on N?

Magisk ROM for the J3 Emerge SM-J327P ( Boost Mobile, Sprint, Sprint XAS, and Virgin

**No longer being maintained**
IF YOU HAVE NOT READ AND FOLLOWED THIS POST COMPLETELY BEFORE FLASHING MY ROMS, I DO NOT WANT TO SEE ANY COMPLAINTS!!!
For your SuperSU ROMs go to @Sands207 thread :
https://forum.xda-developers.com/ga...custom-rom-j3-emerge-sm-j327p-t3634206/page83
Magisk ROMs AFH
https://www.androidfilehost.com/?w=files&flid=232990
BOOST MOBILE VARIANT ONLY, AT THE MOMENT.
If anyone wants a magisk build, take the ARG2 stock update and go through intial setup. When you do take the update, you WILL NOT, I repeat you WILL NOT be able to downgrade to the ARF2,ARC1 AQJ3,APL1, AQF4 , and AQB6 versions or you will risk bricking your device.
From now on, ALWAYS, I repeat, ALWAYS, keep Gapps( arm, 6.0, stock) on hand!!!
There is no need to check any of the checkboxes when using the aroma as you should have already wiped dalvik,system,data, and cache prior to flashing the ROM. I have also integrated the no verity ashyx zip into my ROM, so unless data cant be mounted then before flashing rom, there is NO reason to flash the no verity ashyx zip manually. After flashing rom, wipe cache , dalvik and then reboot.
If you like what I do, feel free to donate here:
https://www.paypal.me/DpAmC
Go join this discord for support and announcements for my magisk ROMs and @Sands207 rom family. https://discord.gg/cYVqjBk
Don't forget to join a rank in the #request-a-role channel by reaction.
If you have no carrier then you would use Uncarrier as your carrier.
This is so we can help you easier.
DSP Manager is now working again, so anyone who was having problems with it fc'ing, just re-download from my afh, as i will be replacing the zip with the one that doesnt fc.
If you're having problems with Google dialer, make sure it is set as the default dialer.
**ROM has now been updated with Good Lock as systemUI**
DISCLAIMER!!!!!!!
I am NOT, I repeat NOT responsible for bricked devices!!!
I am gonna say it one more time!! I am NOT responsible for bricked devices!!!

Nothing is free
I guess not

jlrockafella said:
I guess not
Click to expand...
Click to collapse
@Sands207 is doing one.

SonderTech said:
@Sands207 is doing one.
Click to expand...
Click to collapse
I finally pulled us out of alpha and the first beta is ready. She's a little rough around the edges but overall it's pretty nice. I'll update the OP in a few. Once we can get the stock from stable I'll build a device tree and take a crack at compiling and building lineage os and probably others too, hang in there

@jlrockafella and @SonderTech beta will be live soon here https://drive.google.com/folderview?id=0Bz99NuhE3XwmcHUzcmhpZXJ4Sms i included stock boot.img so those who would like to use it instead of supersu can do so. This will be less complicated @SonderTech i included your boot animation too. i have slow upload so hang tight and thank you so much for all the contributions you've made!! ??I'll update the op with simple directions for us in a bit but it's close to stable now

New build up!! ROM is now stable
Sent from my Samsung SM-J327P using XDA Labs

I'm trying to download from Google drive but it says I need permission? I requested access yesterday and it said to wait for an email. Nothing yet.

ExecuterSedriss said:
I'm trying to download from Google drive but it says I need permission? I requested access yesterday and it said to wait for an email. Nothing yet.
Click to expand...
Click to collapse
Newest build is here https://drive.google.com/file/d/0Bz99NuhE3XwmLTZyZnVIaGN3U00/view?usp=drivesdk

I'm a little new to custom roms but I'm learning pretty quick. I can throw the img onto my sd card, factory reset and flash it over in twrp right? Had to do the same **** to root my phone and all that jazz.

ExecuterSedriss said:
I'm a little new to custom roms but I'm learning pretty quick. I can throw the img onto my sd card, factory reset and flash it over in twrp right? Had to do the same **** to root my phone and all that jazz.
Click to expand...
Click to collapse
How you flash this is your choice ? I prefer to flash my ROM's as zips

Sands207 said:
How you flash this is your choice ? I prefer to flash my ROM's as zips
Click to expand...
Click to collapse
I think that's what I meant. The zip is what I would flash over in twrp and then I reboot and wala. Now does this ROM include root, supersu and all that?

ExecuterSedriss said:
I think that's what I meant. The zip is what I would flash over in twrp and then I reboot and wala. Now does this ROM include root, supersu and all that?
Click to expand...
Click to collapse
Yes. All the info is here at the OP https://forum.xda-developers.com/ga...nt/wip-custom-rom-j3-emerge-sm-j327p-t3634206

Thanks so much you've been more than helpful. I do have a final question, though. I don't have boost/sprint but my model is indeed a j327p. It's a virgin mobile phone, I know that might affect it just curious if this was made for all variants.

ExecuterSedriss said:
Thanks so much you've been more than helpful. I do have a final question, though. I don't have boost/sprint but my model is indeed a j327p. It's a virgin mobile phone, I know that might affect it just curious if this was made for all variants.
Click to expand...
Click to collapse
You have twrp on your device now correct? I have successfully built one for boost. Tonight I'm working on the sprint version for a friend and if you like I could make one for Virgin if firmware is available, im doing this in my extra time so it make take me a few days but I'll certainly try if you want me to.

I do have twrp. I'm glad I asked before bricking my phone haha. I'll check up on it next week. I can't thank you enough, these are not bad little phones. I'm baffled there aren't more people working on projects like this for these samsungs.
---------- Post added at 12:37 AM ---------- Previous post was at 12:27 AM ----------
Sands207 said:
You have twrp on your device now correct? I have successfully built one for boost. Tonight I'm working on the sprint version for a friend and if you like I could make one for Virgin if firmware is available, im doing this in my extra time so it make take me a few days but I'll certainly try if you want me to.
Click to expand...
Click to collapse
And I would very much like that ROM on my virgin mobile device. I would owe you big. I'm not fond of the touchwiz interface and many of the other features that come on the stock firmware.

ExecuterSedriss said:
I do have twrp. I'm glad I asked before bricking my phone haha. I'll check up on it next week. I can't thank you enough, these are not bad little phones. I'm baffled there aren't more people working on projects like this for these samsungs.
---------- Post added at 12:37 AM ---------- Previous post was at 12:27 AM ----------
And I would very much like that ROM on my virgin mobile device. I would owe you big. I'm not fond of the touchwiz interface and many of the other features that come on the stock firmware.
Click to expand...
Click to collapse
Excellent I'll have it finished in a day or so I'll update the OP so others can find it as well, I'm almost done with the sprint version now. I appreciate the support and input, thank you
-sands

ExecuterSedriss said:
I do have twrp. I'm glad I asked before bricking my phone haha. I'll check up on it next week. I can't thank you enough, these are not bad little phones. I'm baffled there aren't more people working on projects like this for these samsungs.
---------- Post added at 12:37 AM ---------- Previous post was at 12:27 AM ----------
And I would very much like that ROM on my virgin mobile device. I would owe you big. I'm not fond of the touchwiz interface and many of the other features that come on the stock firmware.
Click to expand...
Click to collapse
I built this today for you https://drive.google.com/folderview?id=0Bz99NuhE3XwmajBNY0IyZ2FFWkk I understand you are not fond of touchwiz and neither am I, what i suggest is to install xposed to use gravity box and use the firefds kit along side it to make the ROM however you want. Your ROM is in testing phase so I dont want to tear things apart and replace them until we know whats good and not good. Thank you for your support. Enjoy and follow along as we improve on this base ROM. I used Virgin Firmware so make a backup please first and let me know what you think. It's uploading now so please wait an hour or so for it to finish
-sands

Is the boost mobile ROM, touchwiz?

SonderTech said:
Is the boost mobile ROM, touchwiz?
Click to expand...
Click to collapse
It is for the time being, pulling touchwiz caused ALOT of confusion for folks im working on using a different one but setup is affected without it. Honestly i wish i could use evie as the base without borking the rom

Sands207 said:
It is for the time being, pulling touchwiz caused ALOT of confusion for folks im working on using a different one but setup is affected without it. Honestly i wish i could use evie as the base without borking the rom
Click to expand...
Click to collapse
Ah, I see, you could try making it aosp and see what happens

What Roms is everyone running?

What ROM's are people running on their Verizon LG V20? Im getting ready to root mine and go through that process. Looking over the ROM's though and they seem to be lacking. Back in the day we had tons of options, now we have a handful on XDA. Are there ROM's people are running that arent listed?

Using the LineageOS weekly builds and they've been pretty good. Mostly just missing out on the second screen though.

Ashalinia said:
Using the LineageOS weekly builds and they've been pretty good. Mostly just missing out on the second screen though.
Click to expand...
Click to collapse
Ive been trying to find screenshots as Im pretty particular on my OS. I used to love MIUI when it was around.

Lineage for ls997 is horrible I'm using emotion build 4-16

pbedard said:
Lineage for ls997 is horrible I'm using emotion build 4-16
Click to expand...
Click to collapse
Why is it horrible? And why is Emotion better?

Depend on what device u using

pbedard said:
Depend on what device u using
Click to expand...
Click to collapse
That's true for anything. Just going out on a limb here, I'm guessing since we are in the LG V20 forum its safe to assume we are using that device.
Next time come prepared with proof of your claim. With no proof and bold claims you sound like a fool.

as Android goes further the ROM field is super small now KK had the biggest amount of ROMS not a lot of this model I have this version too we have RR DU is coming down the line Lineage WETA AOKP Here is a list of ROMS https://www.androidfilehost.com/?w=search&s=us996&type=files

I have a ls997 and im running Paranoid Android.

I have a vs995 and I'm running XOSP ?

Did i pick the wrong phone i cant seem to find a whole lot of roms for the verizon variant I want a debloated stock or a twrp stock flashable that i can use magisk on it is inexcuseable how much verizon pushed onto this phone is it such a tall task do i really have to choose between having no root with a carrier bloated rom and a working 2nd screen to use a asop type rom?

mirrin said:
Did i pick the wrong phone i cant seem to find a whole lot of roms for the verizon variant I want a debloated stock or a twrp stock flashable that i can use magisk on it is inexcuseable how much verizon pushed onto this phone is it such a tall task do i really have to choose between having no root with a carrier bloated rom and a working 2nd screen to use a asop type rom?
Click to expand...
Click to collapse
The Verizon build of not so stock is probably what you're looking for. Stock based so everything works minus all the bloat. Has static at boot, search some of the other kernels, there is a few that fix static at boot.

mkfryan said:
The Verizon build of not so stock is probably what you're looking for. Stock based so everything works minus all the bloat. Has static at boot, search some of the other kernels, there is a few that fix static at boot.
Click to expand...
Click to collapse
that is what i tried first but the rom was not rooted...

Gre thanks

mirrin said:
that is what i tried first but the rom was not rooted...
Click to expand...
Click to collapse
Did you flash supersu or magisk? Not all roms come rooted...

None I had issues getting it to work had issues booting found weta it worked it has a janky root but it worked and Pokemon go worked and I don't even get the static lines on the screen...

BroeknOs to be
Currently I'm running stock OS on LightningZap! kernel (still in beta, but looking like I'll have a release soon).
I have gotten BrokenOs running quite well and smoothly. But lacking the second screen is what's holding me back.
On LG V20 AT&T (H910), btw...