I was stock 4.4.2 with the latest update D80120e I have root and twrp and flashed a debloat stock ROM. I'm bored already... Are there any roms with extra features like tethering and stuff I cannot already do? I've been searching tmobile section for 2 days. Thanks in advance.
Sent from my LG-D801 using XDA Premium 4 mobile app
This is not my guide/info, just quoting the dev because it seems to apply to your question. You can try some G3 & G Flex ROMs to cure your boredom, but make sure you read all the information and do not forget to flash a D801 kernel!
Sacrosaint said:
Background:
As an owner of the T-Mobile D801, I realize the apparent lack of specially catered ROMs for the device. As far as I've found, all functions on D802 ROMs work fine on the TMO D801 device. You'll just need to flash a D801 kernel over the D802 ROM.
Issues:
PAC ROM for D802 doesn't work using this method.
Data may not work initially due to bad settings. First, check to make sure that your APN Settings are correct. If your APN settings are all set and you're still having issues with LTE vs. UMTS/HSPA+, try changing your network mode to include LTE. Of note, a build of Vanir was having issues with data at the time of writing, so if you cannot fix your issue, try another ROM.
The only thing that I've not seen in custom ROMs based off of anything other than LG's D801 stock is WiFi calling. If you use WiFi calling, following this advice will take away that feature. To retain WiFi calling, you will need to stick to near stock.
Your device's build.prop will identify as a D802 from now on. You may choose to edit this back to D801. Either way, don't trust OTAs or device-specific quirks like open-recovery scripts. It's your job to be a little cautious, and avoid automation that could brick your device. Always have at least one NANDroid backup to return to.
How this works:
Very simply, the most device-specific aspect of these ROMs is the kernel (boot.img). It controls very base-level functions such as managing where boot pointers lead to and providing hardware control. G2 kernels do not mix-and-match from one device to the other. After installing a D802 ROM, you now have a completely incompatible D802 kernel. You must install a D801 kernel to fix that. Afterwards, everything generally seems to work fine.
HOWTO: Install an International LG G2 D802 ROM on the T-Mobile LG G2 D801 device.​Requirements:
You must have a custom recovery (like TWRP) installed.
As far as I've seen, you also need to be rooted before installing a custom recovery on this device.
Instructions:
Download the D802 ROM of your choice. [Warning: PAC ROM for D802 doesn't work]
Download a kernel made for the D801.
For stability, you may use your stock kernel for LG ROMs (backing up/restoring just "boot" in recovery --> that's the kernel), or an AOSP-friendly stock, as built by Houstonn
For features, Custom G2 is a great modified kernel. It includes a D801 version for both Stock LG-based ROMs, as well as AOSP-based ones.​
Reboot into recovery.
[Optional, but strongly recommended] Perform a NANDroid Backup, in case anything goes awry. Backup at least System, Boot, and Data.
Perform a Factory Reset, then wipe cache & dalvik cache.
Install the D802 ROM, including Gapps if needed. DO NOT REBOOT.
Immediately install the D801 kernel.
Reboot.
Enjoy.*
If you ever update your D802 ROM, through .zip or per-ROM OTA, you must always flash a D801 kernel afterwards.
Troubleshooting:
*It may take a while to get by your first boot. I've personally never had the first boot take longer than 2 minutes or so. If it takes upwards of 10 minutes, then try forcing a reboot by holding the power button. If the device still won't boot, something must have gone wrong. Reboot into recovery by holding the power button until the screen goes black, then hold Vol-Down & Power, and when the LG logo appears, release and re-press/hold this key combination. You will arrive at a screen offering a factory reset. Just press the power button twice, ignoring the warnings, and you will boot into recovery. Restore the NANDroid backup you made earlier.Your phone should boot now. You may attempt to try the whole thing again.
An issue I could see is attempting to use an AOSP-friendly kernel with an LG Stock-based ROM, or vice-versa.
If you are having issues with data, see the "Issues" section above for my recommendation: APN Settings.
If you have White Lines issue you might be limited to cloudyfa's D801 jdi kernal
Click to expand...
Click to collapse
Related
Hello everyone,
Ive seem to run into some trouble, that I cant find a solution too.
I rooted my phone with Gingerbreak V1.20, and flash my recovery with CWM.
I proceeded to add the Nightly Four E rom, than the trouble began.
My colors on the phone display are diffused and distorted, mainly showing the color green and blue.
I read thatI need to flash the stock 2.2 rom again and it would fix it but it didnt.
Can someone help me with this, its quite annoying.
Trytohaxme said:
Hello everyone,
Ive seem to run into some trouble, that I cant find a solution too.
I rooted my phone with Gingerbreak V1.20, and flash my recovery with CWM.
I proceeded to add the Nightly Four E rom, than the trouble began.
My colors on the phone display are diffused and distorted, mainly showing the color green and blue.
I read thatI need to flash the stock 2.2 rom again and it would fix it but it didnt.
Can someone help me with this, its quite annoying.
Click to expand...
Click to collapse
It's a kernel issue. From what you've stated, stock 2.2, your device never got it's official 2.3 update. So, you have an old baseband P505. You should be able to flash ROMs made specificially for the P505 as well as P500 ROMs. Since your device is old baseband, you also have the option to flash P509 ROMs. P509 never got an official GB update so it's always an old baseband device, same with the P506. The catch with P500 ROMs and most P505 ROMs is they are build for new baseband so an additional patch, old baseband, will need to be applied after flashing the ROM. P506 devices use a different touchscreen than the others so you'll have issues installing one of those ROMs.
The old baseband patch is to get your radio, cell signal, working with new baseband ROMs. I hope this wasn't information overload If you used ROM Manager, it's possible that is screwed up the radio too. ROM Manager is not friendly to the Optimus One device family. Android Flash Recovery, link in my signature, is designed for flashing recoveries via fastboot and fastboot mode. You may, especially if color banding is an issue with your recovery, want to reflash your recovery too.
Oh, and have you seen the LG Optimus One FAQ?
I appreciate the reply you've giving, but this is my first time using the Optimus One.
You stated its a kernel issue, how would I go upon fixing a kernel issue?
You also stated I should reflash the recovery, is there a specific recovery I should be using?
Trytohaxme said:
I appreciate the reply you've giving, but this is my first time using the Optimus One.
You stated its a kernel issue, how would I go upon fixing a kernel issue?
You also stated I should reflash the recovery, is there a specific recovery I should be using?
Click to expand...
Click to collapse
For the kernel issue, you can search the forums here to find some that are compatible with your device. The kernel you need will depend on the version of Android you are wanting to install since there isn't a universal kernel for all Android versions. Most of the newer kernels are for ICS( Android 4.0 ) and JB( Android 4.1, 4.2 ). I've never used it but they say Franco has a kernel for GB ( Android 2.3 ). SweetnSour has a kernel for JB and the AndroidArmv6 Team has a new 3.0 kernel for JB.
If you like GB, then you may want to look at this CM7.2 ROM( Direct download ). It is for a P500, so you will need the old baseband patch from post #9 in the LG Optimus One FAQ. I''m using that ROM on my P509 ATM.
As for the recovery, I only suggest reflashing it if you are experiencing color issues with it too. I use CWM 5.0.2.7 Touch, but it will only allow P500 ROMs to be flashed. It's no big deal for me, but for someone new to the game it can be troublesome. CWM 5.0.2.0 is also a good recovery. I don't recommend using ROM Manager to flash anything. If you should decide to reflash your recovery, I would recommend using Android Flash Recovery for Windows( in my signature ) or FlashImage GUI which can be found in the Play Store.
It seems no matter what I do, the color will not correct.
I've tried switching roms, flashing a new kernel and recovery nothing seems to be working..
Trytohaxme said:
It seems no matter what I do, the color will not correct.
I've tried switching roms, flashing a new kernel and recovery nothing seems to be working..
Click to expand...
Click to collapse
Do you still have a backup of your stock ROM? I mean a backup that was made while in recovery mode. If you do you can try booting in to recovery and then try wiping and formatting everything but your sdcard. Then restore the backup you made and reboot the device. Other than that, I hate to say it, but I'm at a loss.
I just flashed the CM 7.2 ROM, and franco.Kernel | 2.6.35.10.
I just about did everything, but the color remains distorted once the actual ROM boots up.
Note* If the phone is off and I power it on, the first LG logo has perfect color and clarity but once the ROM kicks in the colors wacks out.
Edit - The phone no longer allows me to access CWM it's just a black screen.
Trytohaxme said:
I just flashed the CM 7.2 ROM, and franco.Kernel | 2.6.35.10.
I just about did everything, but the color remains distorted once the actual ROM boots up.
Note* If the phone is off and I power it on, the first LG logo has perfect color and clarity but once the ROM kicks in the colors wacks out.
Click to expand...
Click to collapse
The kernel is part of the boot image. It's possible that somehow your partitions have been damaged.
---------- Post added at 06:30 PM ---------- Previous post was at 06:27 PM ----------
Trytohaxme said:
I just flashed the CM 7.2 ROM, and franco.Kernel | 2.6.35.10.
I just about did everything, but the color remains distorted once the actual ROM boots up.
Note* If the phone is off and I power it on, the first LG logo has perfect color and clarity but once the ROM kicks in the colors wacks out.
Edit - The phone no longer allows me to access CWM it's just a black screen.
Click to expand...
Click to collapse
Hmm. I'm about convinced there's something wrong with your partition tables. Your data is getting corrupted.
So basically I just ruined the phone?
Trytohaxme said:
So basically I just ruined the phone?
Click to expand...
Click to collapse
Yes and no. If you can find or get a hold of the partition.mbn for your device you can use LGMDP to repair the partitions. The P500 one might work too, I'm not sure tho.
EDIT:
You can also install a recovery and ROM in the same process with LGMDP
shinobisoft said:
Yes and no. If you can find or get a hold of the partition.mbn for your device you can use LGMDP to repair the partitions. The P500 one might work too, I'm not sure tho.
EDIT:
You can also install a recovery and ROM in the same process with LGMDP
Click to expand...
Click to collapse
Yeah, I'm screwed I have no idea how to do that so I'm just gonna have to buy a new phone.. :crying:
Im sorry didn't read too well, bad luck, i didn't read your posts before, i knew how to fix the blue colors on your screen
gabo_lope said:
Im sorry didn't read too well, bad luck i didn't read your posts before i knew how to fix the blue colors on your screen
Click to expand...
Click to collapse
Well how exactly do you fix the screen color than?
Trytohaxme said:
Well how exactly do you fix the screen color than?
Click to expand...
Click to collapse
you only had to flash this on your p505 after the rom https://code.google.com/p/sweetnsour-kernel/downloads/list; one of these
kernel-20130224_1312.zip version4-CFS-P505-P506 for battery life
kernel-20130224_1306.zip version4-BFS-P505-P506 for performance
You have saved my phone my good sir, and I thank you greatly!
Now that I have the correct kernel, can I install different roms now?
Yes, but only ics and jellybean roms , if you use the kernel on gingerbread you will get a lot of troubles...
I just flashed the unofficial CM 10.1, and booted the phone and the color was diffused again.
So I flashed the kernel again and booted the phone, and everything is working perfectly.
Thank you so much!
P.S - CM 10.1 doesn't come with Google Apps or Rom manager, how do I get that back?
To get the google apps you will need to flash a gapps.zip, but first you need to trim the cm 10.1 rom, because
The recommended gapps package is not quite small enough to fit along with the rom in our limited /system partition. The size of the rom can be trimmed by deleting or converting some system apps to user apps, deleting unwanted ringtones and fonts.
Click to expand...
Click to collapse
Also
Take off anything that can be installed from Play, same for gapps.zip!!
Click to expand...
Click to collapse
There is a tool designed for that, is in shinobisoft's signature, oone rom editor, download that tool and in the help docs you will find information about trimming, and what can be removed safely... Here it is http://forum.xda-developers.com/showthread.php?t=1959023
If this the first time you are installing roms, i will recommmend you to stay in ice cream sandwich, because is more stable, and it has a lot better battery life than jellybean...
Hi there, I have been trying for countless hours to make a custom ROM work on my P920 with no results, always some issues. I've managed to brick my phone in different ways a billion times now, then spent billion hours unbricking it and in the end I'm always back to where I started. I would really love some help please.
My phone is P920.
The android version I'm running is: 2.3.5
Kernel version: 2.6.35.7+
Software version: V21E
Rooting method: megatron
Now I would like a ROM that uses Android 4 and that can still use the 3D features such as 3D camera, the ROM calledthe Darkroom International would be an example I imagine.
While that's one of the ROMs that I would want, I've tried many, and always encountering issues, let me clarify.
First of all my device has to be rooted and since SuperOneClick doesn't work for me as it gets stuck on step 7, I use megatron which works well. I even double check if my phone is rooted with the Root Checker from the Android store. Now according to the guides I've read I need a custom recovery system, so I install Clockworkmod. I then place the ROM on the SD card, in the recovery menu I delete cache, that other cache, format it, format system, data, everything those guides tell me to. Afterwards, I install the ROM by selecting the zip and then I reboot. I've tried like 3 different ROMs, jellybem, cyanogenmod and some other. Yes I know none of them support 3D features - I didn't know at the time. Anyway, the issue was always the same, right after the LG logo there would be a screen with some weird colors showing the display of what happened before the phone crashed. Before it crashed? Yes, the phone would actually boot into the ROM but only for a few minutes, crashing afterwards. The next time I would boot, it would show that weird screen with those fancy colors with what happened just before it crashed. So I followed some steps and I got back to the original 2.3.5 ROM, everything back to normal.
I tried doing some more research and I came across the Darkroom Intentional ROM which had a bit different instructions. It asked me to install TWRP recovery with a bootloader, so I did, successfully, then did all the clean cache etc, installed ROM, bam, wouldn't boot at all. Oh boy have I had issues here, I couldn't even get it back to the default 2.3.5 stock ROM because my phone wasn't even recognized in the device manager. So I did some more research, found a solution, managed to flash back to 2.3.5 stock and I'm back to square one.
Now, could someone please help and explain to me what exactly have I done wrong and how I can make it right? I've spent countless hours now trying to install a custom ROM with no success. Sorry about the long read. If you need me to supply some more information please let me know. Thank you.
First of all if u want to use an ICS ROM then u need to update to ICS FIRST u can't flash it directly from 2.3.5 u can use xbsalls thread to update......
Next if cm based Roms are crashing then u need to flash bootloaders which means u should use os_hacking tool to flash ICS bootladers if u wanna update
Or flash GB bootloaders
So first update if u want
Root
Flash bootloaders
Flash recovery
Flash Roms
Sent from my Nexus 4 using xda app-developers app
Hi Guys,
I have a few questions about cyanogenmod, safestrap, and the lovely ATT MF3 bootlocker that is ruining my day. By the way, thanks for all the information you all give, it's helped me understand this process. Even though many people don't post, I'm sure they're glad to have your opinions as well. I have an ATT MF3 SGH-I337. I'm trying to install Cyanogenmod 10.2 using safestrap 3.65. I run into difficulty when I install the 10.2 zip file on the second partition. I've installed the kernel module and was able to successfully install 10.2 (according to SafeStrap), however when I restarted my phone it simply sat on the "Samsung Galaxy S4" screen. It was only soft bricked and I was able to reinstall the stock ROM. I'm about to start the entire process over and I thought that it would be really nice to get an expert opinion on where I'm going wrong.
I have a few questions:
1. Does CyanogenMod 10.2 work with Safestrap 3.65? If not, will 10.1?
2. Should I also install the kernel module on my stock partition?
3. Is there any way that I can limit the stock partition to barely usable? I plan on going Cyano and never looking back.
Thanks in advance,
Grija
I ended up getting SafeStrap on my phone, but I still can't get cyanogenmod on there. Also, my phone's 4G on the stock rom isn't working, despite having the kernel modules.
Any thoughts?
Grija said:
I ended up getting SafeStrap on my phone, but I still can't get cyanogenmod on there. Also, my phone's 4G on the stock rom isn't working, despite having the kernel modules.
Any thoughts?
Click to expand...
Click to collapse
Alright, I've got the modem back. I had to Odin my modem (phone) and CSC. This killed the settings I just set up, but it did fix the modem issue. Back to Cyanogenmod.
I should just be grabbing the latest RC, installing a new virtual ROM, applying the kernals, and flashing the ZIP... correct?
Thanks,
Brandon
No longer own this phone, and no longer have a copy of the rom so this is no longer being developed.
Thanks to @shifattk and @FitAmp for the overclock
Thanks to @Restl3ss, who is working on a rooted and overclocked, otherwise bone stock ROM
Thanks to @atmu5fear, who made the first flashable rom for the S730M, I based my Rom off your original release.
changes I made from the stock 4.04 image
Rooted
BusyBox
Overclocked to 1000mhz
Nova Launcher
Default Ringtone: Crank
Disabled power on and power off boot sounds
Bloat Removed
Theme Changes
Zipaligned
Replaced Samsung keyboard with the google keyboard (much better IMHO)
Stable
Working and tested. Tested on a S730M as well as a S730G
Flashing instructions:
1. Use CWM 6.0.3.1 Get it here https://docs.google.com/file/d/0B1BxFtN0QItNUExLMHBWT1loQjg/edit?usp=sharing, flash with Odin)
2. Make a backup, if things go wrong for you, you cause use the backup to restore your phone's original firmware.
3. WIPE DATA/CACHE
4. Flash
5. Wipe Dalvik.
6. Reboot
NOTE: I can not and will not be responsible for any damage this rom could potentially cause on your phone, http://en.wikipedia.org/wiki/Caveat_emptor
Download Version 1.0 here
Good to see someone still working on this device
Sent from my HTC One using Tapatalk
FitAmp said:
Good to see someone still working on this device
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
It's a nifty little phone. I personally think it's better than a Nexus S but just suffers from the typical Samsung pump and dump routine where they sold all their inventory to the carriers then stopped supporting it with any updates.
Good job! I have 3 versions of the stock ROM available for this device as well, may have been more appropriate for a base, there's stock, stock + root + Busybox, stock + root + Busybox + overclock. Find them here
http://forum.xda-developers.com/showthread.php?t=2677332
Sent from my SGH-T989D using XDA Premium 4 mobile app
r740c
Will these ROMS work with the Cricket version?
kadeleblanc said:
Will these ROMS work with the Cricket version?
Click to expand...
Click to collapse
If the cricket model you have is a GSM version then yes it should so long as its a S730M or S730G. If its a CDMA model then no.
CDMA
doctor_evil said:
If the cricket model you have is a GSM version then yes it should so long as its a S730M or S730G. If its a CDMA model then no.
Click to expand...
Click to collapse
It doesnt take a sim card so no GSM. Is there any other ROMs that you would know of? We are kind of stuck out with this model, it kinda sucks lol.
kadeleblanc said:
It doesnt take a sim card so no GSM. Is there any other ROMs that you would know of? We are kind of stuck out with this model, it kinda sucks lol.
Click to expand...
Click to collapse
You may be able to use the same CWM recovery on that model,
you should be able to probably use the same kernel to overclock your model too, and you can probably use the kitchen app we used to cook these different version roms for the 730M and 730G models to do your own custom rom, just remember before you start working, to do a full nandroid backup of the current rom so you can restore it back to the original (mostly stock except for the cwm recovery) firmware if you need to later on.
By any chance this will unlock it or do you know a way for me to get the unlock using hex?
Thanks to doctor evil for this ROM I was able to flash my phone but not before removing more apps (bell apps and oothers ).
I was wondering if anyone was successful in unlocking the tethering? Tried a few things out there and the best I could get was Bluetooth tethering with foxfi.
And it works!
@doctor_evil: I flashed your set after having played with @atmu5fear's version (http://forum.xda-developers.com/showthread.php?t=2673097). I like them both very much and am still looking which one I will keep. I have not wiped data/cache (i.e. Factory Reset) before overlaying your version over @atmu5fear's one, and it did not hurt. I noticed the following:
Flashing your ROM did not again trip the ROM counter after applying the triangleaway script after @atmu5fear's ROM load (it did go off then).
When having a SIM in the S730M and after putting in the phone unlock password, the keyboard stays on top (this does not happen when no SIM is present)
My Battery-drain problem when having the phone powered fully off with a SIM installed is still there. Probably need to await a cooked custom ROM for this to be solved
The triangleaway script for the S730M can be found at http://forum.xda-developers.com/showthread.php?t=2420184
The Battery-Drain S730M issue has been noticed by quite a few people (TELUS and BELL, both in Canada), and is unexplainable. When the phone is on (with SIM installed), power usage is normal, but when you power off the phone (with SIM still installed) the power-drain goes up dramatically (draining the battery completely within a few hours). When the SIM is removed, or when the battery is removed there is no abnormal drain perceived. The other thing is, that, when the device, with SIM and battery installed, is powered off, both the battery area and the SIM area get warm (not really hot), indicating SIM activity WHILE THE DEVICE IS OFF... Very odd. I am hoping that a new KK custom ROM would fix this issue as both 'custom' 4.0.4 ROMS I have tried now show the same issue, indicating it is either a hardware or a 4.0.4 implementation issue...
I am sorry I never responded back to you. I had my Cygwin install with my kitchen build environment running on a SSD hard drive with my OS and the drive crapped out on me and had to be sent in for a RMA. I had a easus todo workstation backup of my drive I was able to restore, but the backup wasn't current so I lost my kitchen environment. I never tried to set it up again as I had hoped that someone would have ported Cyanogenmod to the phone.
I may give it a try again as I just setup a vmware ESX host server here at home and I can allocate multiple cores and plenty of ram to the linux Virtual Machine I created on it once I figure out the best build environment and how to actually go about building CM successfully. Anyone know of a porting cyanogenmod for dummies guide I can use? LOL
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.