So last night my phones wifi was working fine. That's until I made a few modifications to it.
Things I did:
Installed TWRP Recovery Menu Moto G port
Installed CM13 Osprey Nightly 20160704
Installed SuperSU
Installed Gapps
Right after all that I realized my WiFi wouldn't connect during the CM13 setup. It just said saved after I entered the password. I tried manually connecting it, it went from full bars to one bar then goes back to saved.. When my phone actually connects to the WiFi it is running extremely slower than normal. It also disconnects at random times.
Things I've tried to fix the problem:
Reinstalling ROM w/wo Gapps & w/wo SuperSU
Trying new router
Allowing all permissions that were not allowed
Enabled legacy DHCP client (saw on a forum)
Contacting ISP to see the strength of modem
If anybody has a solution it would be appreciated. I am not sure what to do. Also im in the same room as the router so the connection strength should be solid. If any other information is needed I'll provide it asap. Thank you.
Try Resurrection Remix, Turbo, CandySix or another ROM... there was grumblings of WiFi issues on the last few CM nightlies in various forums (not just Moto G, but not all devices).
Just flash Resurrection Remix (or whichever ROM) and Mini or smaller gapps package, should be better.
acejavelin said:
Try Resurrection Remix, Turbo, CandySix or another ROM... there was grumblings of WiFi issues on the last few CM nightlies in various forums (not just Moto G, but not all devices).
Just flash Resurrection Remix (or whichever ROM) and Mini or smaller gapps package, should be better.
Click to expand...
Click to collapse
I just finished flashing a new ROM. The ROM was called Turbo. But the sad news is I am still having the issue with the WiFi. Its extremely slow and sometimes I will lose connection to it.
Question: is it possible when I flashed a new recovery/ROM and rooted the device of ruined the WiFi adapter?
itzrishi said:
I just finished flashing a new ROM. The ROM was called Turbo. But the sad news is I am still having the issue with the WiFi. Its extremely slow and sometimes I will lose connection to it.
Question: is it possible when I flashed a new recovery/ROM and rooted the device of ruined the WiFi adapter?
Click to expand...
Click to collapse
It shouldn't. If you are using a case check by removing it. Otherwise flashing firmware via fastboot again may help. I was having a problem of phone rebooting when sim was inserted, I flashed firmware and was good to go. It can solve issues with phone radio and subsequently (maybe) your wifi.
Broadcasted from Zeta Reticuli
itzrishi said:
I just finished flashing a new ROM. The ROM was called Turbo. But the sad news is I am still having the issue with the WiFi. Its extremely slow and sometimes I will lose connection to it.
Question: is it possible when I flashed a new recovery/ROM and rooted the device of ruined the WiFi adapter?
Click to expand...
Click to collapse
Very odd... Flashing a ROM or recovery doesn't touch the modem/radio firmware, although the WiFi on the Moto G 2015 is largely driven by the kernel modules that are compiled with it. Both CM and Turbo, and most roms for the G3 are based on CyanogenMod.
My next step would be to try another kernel, I use squid and WiFi works fine, but any newer kernel has the latest kernel drivers. If the results are the same, might be time to step back and reflash the latest stock Marshmallow image completely and work backwards... Root, test, Flash kernel, test, flash rom, test, etc.
You were in marshmallow before starting the whole thing, right?
Sent from my MotoG3 using Tapatalk
acejavelin said:
Very odd... Flashing a ROM or recovery doesn't touch the modem/radio firmware, although the WiFi on the Moto G 2015 is largely driven by the kernel modules that are compiled with it. Both CM and Turbo, and most roms for the G3 are based on CyanogenMod.
My next step would be to try another kernel, I use squid and WiFi works fine, but any newer kernel has the latest kernel drivers. If the results are the same, might be time to step back and reflash the latest stock Marshmallow image completely and work backwards... Root, test, Flash kernel, test, flash rom, test, etc.
You were in marshmallow before starting the whole thing, right?
Click to expand...
Click to collapse
I was on marshmallow before I did everything. Before I proceed with flashing the original Marshmallow image, is there anything I should take not of during the processes? Also this will make me sound like a noob but what do you mean flash the kernel?
Gravemind2015 said:
It shouldn't. If you are using a case check by removing it. Otherwise flashing firmware via fastboot again may help. I was having a problem of phone rebooting when sim was inserted, I flashed firmware and was good to go. It can solve issues with phone radio and subsequently (maybe) your wifi.
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
I do not have a case on my phone. But I will try to remove my sim card while I go back to the original Marshmallow image. Hopefully it works out
itzrishi said:
I was on marshmallow before I did everything. Before I proceed with flashing the original Marshmallow image, is there anything I should take not of during the processes? Also this will make me sound like a noob but what do you mean flash the kernel?
Click to expand...
Click to collapse
Restoring the stock images is pretty simple, just log the process... It will return to compete stock.
In the Original Development area there are custom kernels, you can flash them with TWRP to replace the stock ROM kernel. Squid is my personal favorite, we'll balanced without tweaks.
Sent from my MotoG3 using Tapatalk
acejavelin said:
Restoring the stock images is pretty simple, just log the process... It will return to compete stock.
In the Original Development area there are custom kernels, you can flash them with TWRP to replace the stock ROM kernel. Squid is my personal favorite, we'll balanced without tweaks.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
I am using squids twrp recovery. I have a question. How do I go back to stock android? Or do I just flash the stock android rom?
itzrishi said:
I am using squids twrp recovery. I have a question. How do I go back to stock android? Or do I just flash the stock android rom?
Click to expand...
Click to collapse
Either restore the nandroid you (should) have from before rooting/flashing, or use lost101's guide and rom images to flash via fastboot. The threads are in general.
Sent from my MotoG3 using Tapatalk
acejavelin said:
Either restore the nandroid you (should) have from before rooting/flashing, or use lost101's guide and rom images to flash via fastboot. The threads are in general.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
I don't have a backup because I don't have enough storage. But I did follow lost101s guide.
The bad news is I am still having issues with the wifi. It's not as bad though the speed is decent and it disconnects a lot and just shows saved.
Therefore the problem shouldn't be with the custom rom and I tried using a different device to see if it's my internet but it worked fine.
My conclusion is either the wifi/Bluetooth adapter needs to be replaced.
Although my problem was not solved thank you for trying to help me solve the issue! Much appreciated.
Oh a post after a long time.
I have been having exactly same issues but only with nougat roms.
If I restore my rr marshmallow backup wifi works just fine.
Is flashing stock firmware the only solution?
nikhilsnigam said:
Oh a post after a long time.
I have been having exactly same issues but only with nougat roms.
If I restore my rr marshmallow backup wifi works just fine.
Is flashing stock firmware the only solution?
Click to expand...
Click to collapse
Make sure you have the latest radio stack installed.
acejavelin said:
Make sure you have the latest radio stack installed.
Click to expand...
Click to collapse
Yes I just downoaded the stock package and flashed modem(Older 1)
Seems to work. Haven't had any disconnects till now.
Related
Hi all,
Did anyone able to use gps with custom rom ( I would say CM base). I research and try everything that's I could find here but not success.
Every time I do clean wipe everything including a internal storage. So that will nothing left behind.
I know that stock is work fine with gps. some said that install and replace stock but I have no idea that what file will left in our device when we delete all.
Always had the same problem when running Paranoid Android (not tried other ROMs). Had to return to stock, where GPS runs fine. Would also love to kknow how people have got it functioning.
I am trying too. I modified gps.conf files, tried some workarounds mentioned in cm11 thread like restoring GPS Status backup from stock with titanium so far with no success. Some people say that it works but it doesn't on mine whatever I do.
I run on CM and I don't have any problem. Everything works fine with gps and I didn't use any fix or something similar.
I'm on CM 11-20140627 and I have 1032 phone.
Interesting, why does it work on some while it doesn't on others? Maybe some variants are having problems...
I have xt1033 asia version.
spajdo said:
I run on CM and I don't have any problem. Everything works fine with gps and I didn't use any fix or something similar.
I'm on CM 11-20140627 and I have 1032 phone.
Click to expand...
Click to collapse
Which recovery did you use?
CWM
As I wonder is about library missing or some partition need from stock ?
I've also been using the micro gapps package, would this matter?
I had problems with Paranoid Android and GPS too... If anyone know something about that, please comment!
TMaxtor said:
I had problems with Paranoid Android and GPS too... If anyone know something about that, please comment!
Click to expand...
Click to collapse
Hey i found a solution, you have do this flash following in this order.
- flash stock 4.4.4 (depend on your current)
- flash cm
- flash gapp
I try this twice and work like a charm.
Sent from my Moto G using XDA Free mobile app
thestory101 said:
Hey i found a solution, you have do this flash following in this order.
- flash stock 4.4.4 (depend on your current)
- flash cm
- flash gapp
I try this twice and work like a charm.
Sent from my Moto G using XDA Free mobile app
Click to expand...
Click to collapse
I am having he same problem on XT1032 running Carbon ROM. GPS worked fine on stock, no signal with Carbon.
I found many answers saying to flash stock and then reflash custom ROM. I will try it, but I wonder, how does this help? Isn't the phone restoring the whole system? Do I have to keep the gps.conf from stock?
I've read in some CM thread on here you need to flash stock ROM then enable GPS and get a lock. Once you've done that then flash your custom rom. Sounds STUPID and dosent make sense I know, but a lot of people say this is how they got it to work.
EDIT: I can confirm. I've just flashed stock 4.4.4 and played around with google maps. Flashed CM11 nightly and my GPS is now working ok
am05 said:
I've read in some CM thread on here you need to flash stock ROM then enable GPS and get a lock. Once you've done that then flash your custom rom. Sounds STUPID and dosent make sense I know, but a lot of people say this is how they got it to work.
EDIT: I can confirm. I've just flashed stock 4.4.4 and played around with google maps. Flashed CM11 nightly and my GPS is now working ok
Click to expand...
Click to collapse
Did you wipe anything, like Dalvik, Cache and Data, or you just flashed it over?
am05 said:
I've read in some CM thread on here you need to flash stock ROM then enable GPS and get a lock. Once you've done that then flash your custom rom. Sounds STUPID and dosent make sense I know, but a lot of people say this is how they got it to work.
EDIT: I can confirm. I've just flashed stock 4.4.4 and played around with google maps. Flashed CM11 nightly and my GPS is now working ok
Click to expand...
Click to collapse
Sorry people, I was so happy to have my phone back working, I forgot to write it back here.
Yes it worked indeed, all I did was flashing back the stock, going outside to have a gps lock with gmaps, then re-flashing back the Carbon. I also kept a copy of the gps.conf, but I never needed it, the GPS got a fix quickly. Working fine so far, it only takes some tens of seconds to fix, from time to time.
I can't remember if I also did all the wiping, I think I didn't, but I made so many trials in a couple days, I am not sure.
Thanks a lot guys!
am05 said:
I've read in some CM thread on here you need to flash stock ROM then enable GPS and get a lock. Once you've done that then flash your custom rom. Sounds STUPID and dosent make sense I know, but a lot of people say this is how they got it to work.
EDIT: I can confirm. I've just flashed stock 4.4.4 and played around with google maps. Flashed CM11 nightly and my GPS is now working ok
Click to expand...
Click to collapse
Yes, this worked for me too on PA.
I couldn't even see a single sat (it wasn't just a lock problem). No matter with gps patch, gpx fix app, or gps.conf I used.
What I did?: Back to stock, lock GPS, flash again the custom ROM (but don't wipe /system!).
Good luck on that guys, it should work for you too.
thestory101 said:
Hi all,
Did anyone able to use gps with custom rom ( I would say CM base). I research and try everything that's I could find here but not success.
Every time I do clean wipe everything including a internal storage. So that will nothing left behind.
I know that stock is work fine with gps. some said that install and replace stock but I have no idea that what file will left in our device when we delete all.
Click to expand...
Click to collapse
GPS works fine on this unofficial CM11 rom for me. Stable daily driver rom for me, YMMV.
General advice is to:
- make sure you get a GPS lock on stock rom first
- flash CM11 (or other custom rom)
There may not be a file left on the device. it may just be that stock contains the code to initialize the GPS functionality on the SoC or chipset firmware. Whatever, it works...
Hello, sorry if this has been asked before but my phone has been having trouble connecting to LTE for some reason. I'm assuming it has something to do with my radios or something along those lines. My friend is able to connect just fine and he is on the same rom as I and he also has the same phone.
If someone could point me in the right direction that would be awesome!
Thanks!
iFrostyy said:
Hello, sorry if this has been asked before but my phone has been having trouble connecting to LTE for some reason. I'm assuming it has something to do with my radios or something along those lines. My friend is able to connect just fine and he is on the same rom as I and he also has the same phone.
If someone could point me in the right direction that would be awesome!
Thanks!
Click to expand...
Click to collapse
Are you stock? S-off? Which firmware are you on?
brholt6 said:
Are you stock? S-off? Which firmware are you on?
Click to expand...
Click to collapse
I am s-off and I am on a GPE 5.0.1 ROM.
iFrostyy said:
I am s-off and I am on a GPE 5.0.1 ROM.
Click to expand...
Click to collapse
Did you flash the custom firmware with it too? If so that's likely the problem. Been hearing of a lot of radio issues from L gpe roms lately.
A factory reset in stock recovery (stock vzw recovery) usually fixes it.
Sent from my HTC6525LVW using Tapatalk
dottat said:
Did you flash the custom firmware with it too? If so that's likely the problem. Been hearing of a lot of radio issues from L gpe roms lately.
A factory reset in stock recovery (stock vzw recovery) usually fixes it.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
The custom firmware seems to cause the issue worse than the 4.4.4 firmware. Most everyone seems to be having this issue but overlook. It also makes loading web pages really slow. Flashing the stock RUU and factory reset did not change anything, it seems the firmware is not right for Verizon phones.
LibertyMonger said:
The custom firmware seems to cause the issue worse than the 4.4.4 firmware. Most everyone seems to be having this issue but overlook. It also makes loading web pages really slow. Flashing the stock RUU and factory reset did not change anything, it seems the firmware is not right for Verizon phones.
Click to expand...
Click to collapse
If you flashed the vzw ruu you are no longer on custom firmware.
dottat said:
If you flashed the vzw ruu you are no longer on custom firmware.
Click to expand...
Click to collapse
That was just to start over, I then tried the custom firmware a few more times on multiple ROM's with the same results. Constant signal loss and slow data speeds.
LibertyMonger said:
That was just to start over, I then tried the custom firmware a few more times on multiple ROM's with the same results. Constant signal loss and slow data speeds.
Click to expand...
Click to collapse
That custom firmware should not be flashed to a vzw phone. I have no idea why he posted that firmware to be flashed. You can tell by the info.txt file that it was not.
The included wcnss was never intended to be used on a vzw phone for cdma/lte access.
Wireless connectivity networking subsystem.
OP, your best bet is to flash a stock Verizon RUU (this one works great and is for S-OFF devices), then once it is fully flashed, go into stock recovery and then do a factory reset (this is an important step, this is where you get your proper Verizon radio settings/files back!).
After that, you can go ahead and flash back to DH GPE without using custom firmware and you should be fully functional again with LTE.
And to repeat, you MUST do a factory reset from stock recovery, don't skip this step!
Croak said:
OP, your best bet is to flash a stock Verizon RUU (this one works great and is for S-OFF devices), then once it is fully flashed, go into stock recovery and then do a factory reset (this is an important step, this is where you get your proper Verizon radio settings/files back!).
After that, you can go ahead and flash back to DH GPE without using custom firmware and you should be fully functional again with LTE.
And to repeat, you MUST do a factory reset from stock recovery, don't skip this step!
Click to expand...
Click to collapse
Think that horse was beat dead already lol
Sent from my SM-T320 using Tapatalk
dottat said:
That custom firmware should not be flashed to a vzw phone. I have no idea why he posted that firmware to be flashed. You can tell by the info.txt file that it was not.
The included wcnss was never intended to be used on a vzw phone for cdma/lte access.
Wireless connectivity networking subsystem.
Click to expand...
Click to collapse
Now I am lost lol. Why is it even posted in the Verizon Forum? Too many carriers in that thread i can't keep up with it all I work too much.
LibertyMonger said:
Now I am lost lol. Why is it even posted in the Verizon Forum? Too many carriers in that thread i can't keep up with it all I work too much.
Click to expand...
Click to collapse
It was made for the gpe version phones. They weren't sold for vzw.
dottat said:
It was made for the gpe version phones. They weren't sold for vzw.
Click to expand...
Click to collapse
Yeah I think most who are using it are either lucky or do not care or notice the dropped, weak signals. I've tried everything more than once to get it working right and the results are always the same, it acts like it's the wrong firmware, cause it is lol. Some claim to have the same issues but ignore them. I need my phone to work no matter what ROM it is. Thanks for all your help bro I see you are willing to help us when in need, that is greatly appreciated. I hope users send donations your way, I sure will once i get ahead again.
Have you set your APP correctly.
So I just tried this and cannot get back into stock recovery to wipe data. Had to factory reset from hboot, that worked but not sure if it does the same thing as the one in stock recovery, please advise. Then tried to flash the stock recovery and it's still taking me to the darn red triangle with an exclamation point. I am going to continue and install LiquidSmooth 4.0 1-02 nightly after I flash custom recovery. I have searched but cannot find anything on our variant. Thank you all in advance.
kj13569 said:
So I just tried this and cannot get back into stock recovery to wipe data. Had to factory reset from hboot, that worked but not sure if it does the same thing as the one in stock recovery, please advise. Then tried to flash the stock recovery and it's still taking me to the darn red triangle with an exclamation point. I am going to continue and install LiquidSmooth 4.0 1-02 nightly after I flash custom recovery. I have searched but cannot find anything on our variant. Thank you all in advance.
Click to expand...
Click to collapse
When you get the red triangle, you press volume up and power to enter stock recovery. Keep practicing.
LTE drops on and off
I think I have the same issue as OP. However, I'll go further and note that I notice this on ALL AOSP roms as well as the GPe rom. It's not so much that the connection is bad, it looks good. But it drops on and off randomly. I followed the instructions here to factory reset the firmware using the 4.4.4 ruu. It definitely seems to be better but I still have this issue in DH's GPe (stock kernel). Any further ideas?
Flylowguy said:
I think I have the same issue as OP. However, I'll go further and note that I notice this on ALL AOSP roms as well as the GPe rom. It's not so much that the connection is bad, it looks good. But it drops on and off randomly. I followed the instructions here to factory reset the firmware using the 4.4.4 ruu. It definitely seems to be better but I still have this issue in DH's GPe (stock kernel). Any further ideas?
Click to expand...
Click to collapse
That signal drop off issue happens to me on gpe ROMs. So far all the cm12 ROMs out there have had a perfect signal with good speeds for me. I think the signal drop off issue is something to do with the gpe ROMs.
Currently running blisspop newest nightly with 4.4.4 straight from RUU.
I'm having major issues with reception in my house, and only on my 16 GB OnePlus One. When switching to my Windows Lumia 635 or my HTC One X+, I get fine reception-- but as soon as my SIM's in my OnePlus One, I start receiving texts extremely late, which is a problem with apps like WhatsApp which require text verification.
I'm running stock ROM. That's CM 12.0-YNG1TAS17L. Stock kernel, unrooted even (ever since I flashed it back to stock to try and fix the reception issues). I've also tried OxygenOS, BlissPop, and Exodus and none of those have fixed my reception woes. Thanks in advance!
toohsieh said:
I'm having major issues with reception in my house, and only on my 16 GB OnePlus One. When switching to my Windows Lumia 635 or my HTC One X+, I get fine reception-- but as soon as my SIM's in my OnePlus One, I start receiving texts extremely late, which is a problem with apps like WhatsApp which require text verification.
I'm running stock ROM. That's CM 12.0-YNG1TAS17L. Stock kernel, unrooted even (ever since I flashed it back to stock to try and fix the reception issues). I've also tried OxygenOS, BlissPop, and Exodus and none of those have fixed my reception woes. Thanks in advance!
Click to expand...
Click to collapse
You ever get this fixed? I recently took a trip to San Diego and noticed the poor reception there.. a friend of mine, who's also on T-Mobile, has excellent reception with his new HTC One. I, on the other hand, had horrible reception; sometimes none at all. I've manually flashed the latest radio and still no dice.
silentcovenant said:
You ever get this fixed? I recently took a trip to San Diego and noticed the poor reception there.. a friend of mine, who's also on T-Mobile, has excellent reception with his new HTC One. I, on the other hand, had horrible reception; sometimes none at all. I've manually flashed the latest radio and still no dice.
Click to expand...
Click to collapse
Yeah-- here's what I did:
1. Flash stock ROM.
2. Update to latest stock ROM version via the CM updater.
3. Install TWRP again if needed.
4. Followed steps here: http://forum.xda-developers.com/oneplus-one/help/fix-cm12-calls-sms-mms-deep-sleep-t3103193
I flashed both the modem and proximity packages after updating to latest stock, and I reflash every time there's a new stock update. Hopefully this works for you!
toohsieh said:
Yeah-- here's what I did:
1. Flash stock ROM.
2. Update to latest stock ROM version via the CM updater.
3. Install TWRP again if needed.
4. Followed steps here: http://forum.xda-developers.com/oneplus-one/help/fix-cm12-calls-sms-mms-deep-sleep-t3103193
I flashed both the modem and proximity packages after updating to latest stock, and I reflash every time there's a new stock update. Hopefully this works for you!
Click to expand...
Click to collapse
Wait, isn't the stock from still on 4.4 or something? How does that fix 5.0+ issues? Anyways, I'll give it a try, can't hurt, right? Thanks, I'll let you know how it goes.
silentcovenant said:
Wait, isn't the stock from still on 4.4 or something? How does that fix 5.0+ issues? Anyways, I'll give it a try, can't hurt, right? Thanks, I'll let you know how it goes.
Click to expand...
Click to collapse
Well, stock is 4.4, but when you use the stock CM updater you'll be brought to CM12, 5.0.2. You don't have to stay on 4.4
silentcovenant said:
Wait, isn't the stock from still on 4.4 or something? How does that fix 5.0+ issues? Anyways, I'll give it a try, can't hurt, right? Thanks, I'll let you know how it goes.
Click to expand...
Click to collapse
(Though presumably you could just try flashing modem and prox packages without flashing back to stock-- I just wanted to be sure as possible that nothing would interfere with the packages.)
toohsieh said:
(Though presumably you could just try flashing modem and prox packages without flashing back to stock-- I just wanted to be sure as possible that nothing would interfere with the packages.)
Click to expand...
Click to collapse
Flashed an old backup of stock, baseband stayed the same. Also, when I check for ROM updates, it says there are none. Currently on 4.4.4
silentcovenant said:
Flashed an old backup of stock, baseband stayed the same. Also, when I check for ROM updates, it says there are none. Currently on 4.4.4
Click to expand...
Click to collapse
That's really odd. You're on XNPH05Q? Or another one?
I used http://www.droidviews.com/restore-oneplus-one-stock/ to restore to stock instead of using a backup.
toohsieh said:
That's really odd. You're on XNPH05Q? Or another one?
I used http://www.droidviews.com/restore-oneplus-one-stock/ to restore to stock instead of using a backup.
Click to expand...
Click to collapse
The stock version they gave me was: XNF9XBS28K
silentcovenant said:
The stock version they gave me was: XNF9XBS28K
Click to expand...
Click to collapse
I can't say I've ever seen that version before but it looks like someone else had the same issue: https://forums.oneplus.net/threads/xnf9xbs28k-ota-updates.315441/
I've done everything correctly, followed every tutorial, and I'm still not having any luck. I started on stock rooted Lollipop, and all I was getting as installation aborted errors with using Lollipop Autorec. I've since flashed back to stock rooted Kitkat, which I've got the closest with. I've been trying to flash one of the newer nightly updates from Cyanogenmod (20150709 specifically). I've also tried using the first stable release, to no avail. I used one click root to root, which worked fine, and Autorec Kitkat installer for TWRP, which also installs fine, and I can get into recovery no problem. I wipe, I flash, and it boots up, but then it never loads. It ends up being stuck on a boot loop, and it's very frustrating because of how close I'm getting. A Cyanogenmod 11 snapshot flashed correctly, but I'd like to figure out the newer update problem. I'm on LG D800. I'm a complete noob at this stuff, and need a sensei to guide me, please. Thanks in advance.
(Update): I've just now tried installing the newest Resurrection Remix for LG G2, and that sticks me in a boot loop as well, so I have no idea what I have to do. Will update again in a moment because I'm going to try downloading stock Lollipop and the newest TWRP.
(Update 2): So, I've just done what I said I'd do earlier. I flashed the LP bootstack, then Resurrection Remix, then Gapps, and I'm getting a bootloop for that, as well, so I'm calling it a night, and going to bed. Someone please respond. I really need help.
Did you update TWRP? You need to be on the latest version, 2.8.7.1 to flash the newest roms. http://blastagator.ddns.net/twrp.html Put this on your phone and go into recovery and flash it. No wipes needed. Don't reboot when it's done, back arrow to the first screen and select reboot and then select recovery. After that reboots you'll be on the latest TWRP and can flash the LP roms and necessary files or just reboot system and you'll boot up the rom you currently have installed.
Yeah, I ended up trying that, and flashing Resurrection Remix, and I was still getting a boot loop on that, as well.
Really now said:
Did you update TWRP? You need to be on the latest version, 2.8.7.1 to flash the newest roms. http://blastagator.ddns.net/twrp.html Put this on your phone and go into recovery and flash it. No wipes needed. Don't reboot when it's done, back arrow to the first screen and select reboot and then select recovery. After that reboots you'll be on the latest TWRP and can flash the LP roms and necessary files or just reboot system and you'll boot up the rom you currently have installed.
Click to expand...
Click to collapse
I just read what you said again, and no, I didn't actually try that version. I'm on TWRP normal version 2.8.6.1. I will probably try what you said, soon, and report back when I do.
(EDIT): Also, am I supposed to flash a baseband and/or a different bootloader? I'm really new to this stuff, and I don't 100% know everything to do, and some tutorials aren't 100% clear, because I guess they're assuming the viewer knows what they're doing.
Wezurii4694 said:
I just read what you said again, and no, I didn't actually try that version. I'm on TWRP normal version 2.8.6.1. I will probably try what you said, soon, and report back when I do.
Click to expand...
Click to collapse
Yeah, from what I'm reading in all the latest LP threads you have to be on the latest TWRP. I am and I've had zero issues flashing the different roms. Follow the OP of each one exactly and you'll be fine.
Really now said:
Yeah, from what I'm reading in all the latest LP threads you have to be on the latest TWRP. I am and I've had zero issues flashing the different roms. Follow the OP of each one exactly and you'll be fine.
Click to expand...
Click to collapse
Alright, man, thanks a lot! I'll report back when I test this out. Also, am I supposed to flash a baseband and/or a different bootloader? I'm really new to this stuff, and I don't 100% know everything to do, and some tutorials aren't 100% clear, because I guess they're assuming the viewer knows what they're doing.
Wezurii4694 said:
Alright, man, thanks a lot! I'll report back when I test this out. Also, am I supposed to flash a baseband and/or a different bootloader? I'm really new to this stuff, and I don't 100% know everything to do, and some tutorials aren't 100% clear, because I guess they're assuming the viewer knows what they're doing.
Click to expand...
Click to collapse
No baseband, just the bootloader the OP specifies. You just need to read, read and read some more. It may be confusing at first but you'll figure it out. A good thing to have on your computer is here, http://forum.xda-developers.com/showthread.php?t=2663369 . It makes it very easy to go back to KK and start over if you need to. I've used this a number of times and have gone back from LP without a problem. Once again, read the OP until you understand what you need to do.
Really now said:
No baseband, just the bootloader the OP specifies. You just need to read, read and read some more. It may be confusing at first but you'll figure it out. A good thing to have on your computer is here, http://forum.xda-developers.com/showthread.php?t=2663369 . It makes it very easy to go back to KK and start over if you need to. I've used this a number of times and have gone back from LP without a problem. Once again, read the OP until you understand what you need to do.
Click to expand...
Click to collapse
What if the OP doesn't specifie? Because I didn't even know I needed to flash that, till this point, haha. Yeah, I've used that, and have that. This past weekend I soft bricked my phone, probably around 10 times, and I used that each time, haha.
Wezurii4694 said:
What if the OP doesn't specifie? Because I didn't even know I needed to flash that, till this point, haha. Yeah, I've used that, and have that. This past weekend I soft bricked my phone, probably around 10 times, and I used that each time, haha.
Click to expand...
Click to collapse
I don't know of any of the caff LP versions that don't state that you need to flash the correct bootstack. If in doubt, don't flash it. If you were trying to install cyanogenmod 12 it doesn't require a bootstack flash but 12.1 does. You have to be sure of what you're trying to install. You might try running this http://forum.xda-developers.com/att-g2/development/rom-stock-lollipop-30b-stripped-t3144195 . Same dev that builds TWRP that I sent you to put this together. It's an all in one flash! And since it's in the at&t section it's not bloated with issues from users of different G2 variants. Just a thought.
Really now said:
I don't know of any of the caff LP versions that don't state that you need to flash the correct bootstack. If in doubt, don't flash it. If you were trying to install cyanogenmod 12 it doesn't require a bootstack flash but 12.1 does. You have to be sure of what you're trying to install. You might try running this http://forum.xda-developers.com/att-g2/development/rom-stock-lollipop-30b-stripped-t3144195 . Same dev that builds TWRP that I sent you to put this together. It's an all in one flash! And since it's in the at&t section it's not bloated with issues from users of different G2 variants. Just a thought.
Click to expand...
Click to collapse
Alright. I got around to trying what you suggested. Still a boot loop on Resurrection Remix, and I don't know why. I flashed the bootstack for my phone, that the post said to, then the rom, then Gapps. So I have no idea what I have to do to get this to work.
Wezurii4694 said:
Alright. I got around to trying what you suggested. Still a boot loop on Resurrection Remix, and I don't know why. I flashed the bootstack for my phone, that the post said to, then the rom, then Gapps. So I have no idea what I have to do to get this to work.
Click to expand...
Click to collapse
I'm assuming that you're on stock rooted LP and you've only tried flashing the RR rom. I haven't flashed that one in a long time but I see on the last few pages of the thread that there are several people getting stuck in bootloops. Is it the rom or their installation? I don't know but I'd seriously try a different rom. The latest Cloudy G2 3.3 is an excellent rom and everything works. It's my go to backup rom. The least confusing way to install it is to follow this,
http://forum.xda-developers.com/showpost.php?p=61396344&postcount=465 although you'd be flashing the 3.3 version not the 3.1. On the aosp side, I've been using Vanir https://androidfilehost.com/?w=files&flid=28988 with TK Gapps https://www.androidfilehost.com/?w=files&flid=31524 and this bootstack https://androidfilehost.com/?fid=24052804347760740 . Right now I'm running Slim Saber http://forum.xda-developers.com/lg-g2/development/rom-slimlp-alpha-0-4-t3135141 . It's a very nice rom too. Other than that I don't know how else to help.
Really now said:
I'm assuming that you're on stock rooted LP and you've only tried flashing the RR rom. I haven't flashed that one in a long time but I see on the last few pages of the thread that there are several people getting stuck in bootloops. Is it the rom or their installation? I don't know but I'd seriously try a different rom. The latest Cloudy G2 3.3 is an excellent rom and everything works. It's my go to backup rom. The least confusing way to install it is to follow this,
http://forum.xda-developers.com/showpost.php?p=61396344&postcount=465 although you'd be flashing the 3.3 version not the 3.1. On the aosp side, I've been using Vanir https://androidfilehost.com/?w=files&flid=28988 with TK Gapps https://www.androidfilehost.com/?w=files&flid=31524 and this bootstack https://androidfilehost.com/?fid=24052804347760740 . Right now I'm running Slim Saber http://forum.xda-developers.com/lg-g2/development/rom-slimlp-alpha-0-4-t3135141 . It's a very nice rom too. Other than that I don't know how else to help.
Click to expand...
Click to collapse
Alright, I'll try it out. You've been really helpful. I'll let you know how it goes. I had to reflash Kitkat, so I'm about to update to Lollipop again.
Wezurii4694 said:
Alright, I'll try it out. You've been really helpful. I'll let you know how it goes. I had to reflash Kitkat, so I'm about to update to Lollipop again.
Click to expand...
Click to collapse
Good luck! One other thing I was going to say is that if you want a great camera/video and a stock like experience with a lot of features then go with the Cloudy G2 3.3. It's based on the LG firmware so it's a good place to start and get rid of all of the at&t bloatware.
Wezurii4694 said:
Alright, I'll try it out. You've been really helpful. I'll let you know how it goes. I had to reflash Kitkat, so I'm about to update to Lollipop again.
Click to expand...
Click to collapse
Really now said:
Good luck! One other thing I was going to say is that if you want a great camera/video and a stock like experience with a lot of features then go with the Cloudy G2 3.3. It's based on the LG firmware so it's a good place to start and get rid of all of the at&t bloatware.
Click to expand...
Click to collapse
Oh, in what order do I do everything? Just to make sure.
Edit: Never mind.
Wezurii4694 said:
Oh, in what order do I do everything? Just to make sure.
Edit: Never mind.
Click to expand...
Click to collapse
One other thing that occurred to me, are you doing full wipes in TWRP? You have to select Wipe-Advanced Wipe-then check off Dalvik,System,Data,Cache (DO NOT check off Internal Storage) and then swipe the slider. I always do it 3 times, press the back button and Factory Reset 3 times. Probably overkill but it works for me. Then go back and do the install.
Really now said:
One other thing that occurred to me, are you doing full wipes in TWRP? You have to select Wipe-Advanced Wipe-then check off Dalvik,System,Data,Cache (DO NOT check off Internal Storage) and then swipe the slider. I always do it 3 times, press the back button and Factory Reset 3 times. Probably overkill but it works for me. Then go back and do the install.
Click to expand...
Click to collapse
I've always only ever done the advanced wipe. I'll do the three times thing, this time.
Wezurii4694 said:
I've always only ever done the advanced wipe. I'll do the three times thing, this time.
Click to expand...
Click to collapse
I do it 3 times because on my old Galaxy Note I noticed a few times that when I flashed a new rom a few things that I hadn't installed were still there. So I got in the 3 wipe habit.
Really now said:
I do it 3 times because on my old Galaxy Note I noticed a few times that when I flashed a new rom a few things that I hadn't installed were still there. So I got in the 3 wipe habit.
Click to expand...
Click to collapse
Oh, okay. Oh, when do I flash the kernal?
Wezurii4694 said:
Alright. I got around to trying what you suggested. Still a boot loop on Resurrection Remix, and I don't know why. I flashed the bootstack for my phone, that the post said to, then the rom, then Gapps. So I have no idea what I have to do to get this to work.
Click to expand...
Click to collapse
Well you're bound and determined to keep flashing the same rom over and over and it doesn't work. If it were me I'd move on to a different rom.
Really now said:
Well you're bound and determined to keep flashing the same rom over and over and it doesn't work. If it were me I'd move on to a different rom.
Click to expand...
Click to collapse
I meant on Cloudy. I'm trying that out.
Hey guys, I just flashed the CM13 nightly from stock 5.0 and now I'm showing no sim card. I saw a couple threads saying that newer twrp builds have issues with flashing radios, so I reverted to twrp 2.8.6 and did a clean flash, with no love. Tried flashing the radio zip, no love. Tried flashing the 3 most recent radios through fastboot, no love.
Any assistance would be greatly appreciated
Are you flashing both the bootloader and radio? If this doesn't work, I suggest flashing the latest stock MM to make sure the phone is working, then flash CM13.
Good call, trying it now
okay, flashed to stock 6.0.1, worked like a champ, flashed back to cm, now it connects to the network, but drops to no service after a second or two. Progress! Now that I know that you have to flash bootloader and radio, i'll try some different combos and see if i can get something to work. If nothing else, i can always go back to stock MM
Thanks!
Have you tried CM13 with a custom kernel? This may solve the issue.
You need to do alot of reading, no insult intended. Don't run b4 you can walk. If you didn't know to flash the radio and bootloader you need to learn alot. Luckily it's a bullet proof phone. Nightlies are not stable and not for daily drivers. They are works in progress and buggy as a result. Not for noobies, IMHO
The OP did flash different radios. It is not always necessary to flash a modem and bootloader to have a working phone.