So I've googled around trying to figure this out but so far no dice.
Things I've tried include changing the build.prop things, turning off okay google, and flashed the newest modem
Back story is I did a full official cos 13.1 unrooted and everything. Then later decided I wanted to go back to the ROMs y'all make. I noticed the issue after going to cos 13.1 but been trying to fix on my own for a few days now.
I'm on the newest modem, using tugapower twrp and on tugapower ROM (w/e the newest version is).
Am I missing something?
did a clean install and nothing. still broken
Related
Hi everybody,
I decided to go back to Cyanogenmod, because i had some issues with the ROM I used before. First I flashed the CM 10.1.3 stable, everything worked fine, but I couldn't connect to any WiFi. So i tried flashing the nightly 10.2 10.2 2013111 over the Updates in the preferences. Still, i couldn't connect to any WiFi. I tried it two more times with full wipes and flashing the nightly over my Recovery, but couldn't make it work.
All these times i flashed the boot.img after flashing the nightly. I don't really know what to do anymore and thought anyone might have an idea for me?!
I didn't have any major issues until today, so i don't know what Information you might need to help me, so please tell me if I should say something more about the system or how I flashed it etc.
Thanks in Advance!
Edit: Same Problem with CM11...
Edit 2: Tried to flash the Bubba Kernel, because i read something about it...now i can't even turn the wifi on. -.-
So...I have had a captivate and SGS3 and have never had so much trouble with a phone. This infuse is frustrating and complicated to work with. I have blue CWM which was acquired by using Entropy's guide and the other numerous helpful tips out there. I had rootbox running which would eventually start FC'ing and acting dumb. I wiped everything the other day and flashed unofficial CM 10.2, it worked perfect then random reboots to stuck at samsung then cyanogen mod then back again. Sometimes it would randomly reboot in CWM, which has never happened to me on other phone. I feel like going back to stock and back again is the only answer, but it seems like a lot of work and I already did that and it was fine.
So, all you guys that understand whats going on behind that scenes, what do you think the issue is?
UPDATE: I found a video that may link this behavior to a hardware issue caused by poor design by Samsung having too many contacts that can get gunked up and causing issues.
Might be a problem with the version of the Gapps you're using. Consider changing and even going back to older versions. I found v 12/12 signed very stable on cm10.1.
If still stuck, consider Odin back to stock in download mode and flash cm9 and cm10.2 again!
Hey all, need a quick hand with my T-Mo LG G2 d801- 4.4.2 stock rom.
Process so far: towelroot>supersu>autorec>twrp>...
Tried flashing CM11, but after about 20min I figured I did something wrong, lol.
What version of cyanogenmod should I be flashing, 10 or 11? From the description of what AutoRec does to deal with the bootloader, it downgrades to the last vulnerable rom to install/enable custom recovery, correct? If so, does it stay downgraded or is that just to get the custom recovery in place?
Don't want to brick my phone experimenting, so here I am. Thanks in advance!
Also should have waited till after work, as I have no more time tonight to mess with it unfortunately. Back in 8hrs! :silly:
Nevermind, I got it working.
fleshybits said:
Nevermind, I got it working.
Click to expand...
Click to collapse
Consider that while others might not have had an answer to your question, your thread could have been frequented in order to see the answer.
So, how did you resolve your issue? ?
fleshybits said:
Hey all, need a quick hand with my T-Mo LG G2 d801- 4.4.2 stock rom.
Process so far: towelroot>supersu>autorec>twrp>...
Tried flashing CM11, but after about 20min I figured I did something wrong, lol.
What version of cyanogenmod should I be flashing, 10 or 11? From the description of what AutoRec does to deal with the bootloader, it downgrades to the last vulnerable rom to install/enable custom recovery, correct? If so, does it stay downgraded or is that just to get the custom recovery in place?
Don't want to brick my phone experimenting, so here I am. Thanks in advance!
Also should have waited till after work, as I have no more time tonight to mess with it unfortunately. Back in 8hrs! :silly:
Click to expand...
Click to collapse
Autorec just flashes an older boot loader, with a stock based KK kernel that's compatible. Once up and running any stock based kernel can be flashed if running a stock ROM. It also supports running any after market ROM, however, if running a jb based ROM one needs to be on a jb modem, and if running KK a compatible modem. These are pretty much the only prerequisites.
Sorry, that was rather rude of me wasn't it? Apologies. Not fair to ask for help if I can't return the favor when I can.
Well, instead of looking around on the CM downloads page to get the most stable release, I just got the most recent snapshot of CM 11. Silly me
Turns out the right file to flash first was, of course, the last stable release for the G2 D801, which was CM 10.2.0 (at least at the time of this writing, as far as I know.) After getting the right file and trying again, I was rocking my first custom ROM. Go me! :good:
I have not yet tried the snapshot again to see if I could upgrade to CM11, as I hit another snag: I can't connect to my carrier anymore. I can see T-Mobile in the list for networks but selecting them does nothing, I get no service. Restoring the stock ROM works just fine, its like nothing happened, but running CM I can't connect. Any suggestions?
Hi guys,
Tried to flash OxygenOS 1.03 through twrp 2.8.7 after getting some annoying problems with OPO on the latest CM11s.
Done many flashes before so didn't really expect much problems. Then OPO couldn't boot up at all with black screen. I followed the instruction here to unbricked with factory tool to clash an old edition of ColorOS and I thought that was the end of it. Flash OxygenOS again, bricked again.
Then I recovered and flashed COS 12.1. Didn't really want to make the jump but I had too. I immediately noticed I am unable to connect to 4G. Thinking that the OS 1.03 from OP didn't contain any modem update and thus the hard brick, I flashed 1.03 again and worked. Again no 4G or any cellular connection. I went out side and finally got a very weak 4G connection (I usually have full bar around my home). Really desperate, I flashed back to official CM12s, and flashed the correct radio for it. Same thing.
It has been a week now. I could get some connection if force it to 3G but still very spotty. It is hard to use. I tried different modems, even one from ColorOS because I am in China and I got the phone in US.
Any tips on solving this?
I fixed it by reflash raido of xnph52q found here. The zip contains more than the radio firmware.
http://forum.xda-developers.com/oneplus-one/development/rom-stock-rooted-xnph52q-t3025399
I flashed it before but it didn't work. The only difference is I used TWRP 2.8.6. I remember reading somewhere online that 2.8.7 has issue with OPO.
I will changed it to resolved and save it as reference for others
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.