Related
Hello,
I'm new here and i have a problem with my wifi.
I'm running Cyanogenmod 7.1 and i never had problems with original rom.
The problem is that it makes a connection and keeps it when idling, but then when
i need to use it the connection falls away and doesn't reconnect automatically.
When i go to the wifi settings it does automatically tries to reconnect.
I found a fix here: http://forum.xda-developers.com/showthread.php?t=1177650
and i think that one should work. I tried to install the zip but it uses an older script version. I also tried to put the files on the cyanogenmod rom and flash it all again but i also get an error.
Is there any option to get it to the newer script version so I don't get errors anymore?
Erwin
CM7.1 is old now. flash a newer version (the nightlies)
here:
Captivate: http://download.cyanogenmod.com/?type=nightly&device=captivatemtd
Fascinate: http://download.cyanogenmod.com/?type=nightly&device=fascinatemtd
Vibrant: http://download.cyanogenmod.com/?type=nightly&device=vibrantmtd
i9000: http://download.cyanogenmod.com/?type=nightly&device=galaxysmtd
download the newest file
I always thought that the nightly builds are like the experimental builds with possibly some glitches or something.
When i flash the newest version, do i lose all the settings and stuff or will it just update some files?
Erwin
000Erwin000 said:
I always thought that the nightly builds are like the experimental builds with possibly some glitches or something.
When i flash the newest version, do i lose all the settings and stuff or will it just update some files?
Erwin
Click to expand...
Click to collapse
They are experimental...that's what makes them better. You get all the new features in it. Nd no they shouldnt wipe any of your data. Always make a backup though !!
They usually don't have any glitches...usually just new feature.
You should start looking at I cs roms though...they now pretty much all work flawlessly.
I'm on JellyBeans right now, Build 22. I flashed it yesterday no problems, before that I was on build 20. I want to use the PAC-Man rom but whenever I try to flash it in Aroma it fails and the error is Status 7. I've tried the latest milestone build as well as the latest nightly, on both the internal and external SD and I still keep getting the same error.
Anyone know how I can remedy this?
Baderkadonk said:
I'm on JellyBeans right now, Build 22. I flashed it yesterday no problems, before that I was on build 20. I want to use the PAC-Man rom but whenever I try to flash it in Aroma it fails and the error is Status 7. I've tried the latest milestone build as well as the latest nightly, on both the internal and external SD and I still keep getting the same error.
Anyone know how I can remedy this?
Click to expand...
Click to collapse
What recovery are you using, TWRP? If so, sounds like you need to update versions.
jcollier said:
What recovery are you using, TWRP? If so, sounds like you need to update versions.
Click to expand...
Click to collapse
Thank you I did that and it installed fine. Although now that I'm using the rom I keep getting AOSP Keyboard force closed errors whenever I have to type something, do you know what could be causing this?
Baderkadonk said:
Thank you I did that and it installed fine. Although now that I'm using the rom I keep getting AOSP Keyboard force closed errors whenever I have to type something, do you know what could be causing this?
Click to expand...
Click to collapse
Honestly no idea, as I use Beans and have not tried PACMan on this phone. Even though you can't post in that thread yet, it wouldn't hurt to search through it and see if anyone else has had a similar experience.
I have just recently tried to install the official cm11 images for my g3. They worked fine. Then, when I installed gel x-posed settings and activated it, I would get said error. It would pop up again and again. This would lead me to reflash my ROM. Then, I do not know what happened, when I would flash a ROM, I would get the error from the start. I eventually fixed this error. But then, when I tried to upgrade the nightly, I got the error again. So I flashed the ROM again, and let it sit. After a little while of perfection, the error came back up!
Here's what I have tried:
-reflashing the boot.IMG (unzipped)
-clearing cache (recovery)
-clearing Sim tool cache/data (said they were non existent when trying)
-reflashing stock, then reflashing cm11
I really want cm11 on my g3, but with these issues, I don't know whether I can now.
Any help would be appreciated!
Sent from my Nexus 7 using XDA Free mobile app
CM Nightlies are working perfect for me with no errors. Here is the process I went through:
I am still using TWRP 2.8.0 which is the version I installed when I originally Bumped! my phone.
I downloaded CM and Gapps to root of my internal SD storage
I chose to Wipe in TWRP
I chose Advance Wipe
I picked every option except for Internal Storage and External SD Card/Storage
I then Wiped
Out of habit, I do this 3 times (don't ask why, I just do it from when I had older android devices)
I then go back to wipe main screen and slide to do the standard wipe, 3 times
Yes, this is probably overkill!
I then go to install in TWRP
I install CM, then I install gapps (using the gapps that are on this list: https://itvends.com/gapps/
Yes, the date of those gapps are a little older, but that is what worked for me per OP'S instructions
I went through setup of my phone, fixing APN, Setting WIFI to USA, signing into Google after first loading into Rom instead of signing into Google on first bootup. Did a reboot
Installed Xposed, and the modules needed, reboot
I never received any error
I have done 3 nightly updates so far, as of 11/30. I am sure 12/1 will be ready in an hour or so.
I always click on about phone, download said update and let the process do its thing automatically, walk away and the phone is ready to use
Still no errors whatsoever. In fact, this has been the first version of AOSP I have used for the G3 with 0 errors. It is perfect, for me - No issues.
Hope that helps.
mwest316 said:
CM Nightlies are working perfect for me with no errors. Here is the process I went through:
I am still using TWRP 2.8.0 which is the version I installed when I originally Bumped! my phone.
I downloaded CM and Gapps to root of my internal SD storage
I chose to Wipe in TWRP
I chose Advance Wipe
I picked every option except for Internal Storage and External SD Card/Storage
I then Wiped
Out of habit, I do this 3 times (don't ask why, I just do it from when I had older android devices)
I then go back to wipe main screen and slide to do the standard wipe, 3 times
Yes, this is probably overkill!
I then go to install in TWRP
I install CM, then I install gapps (using the gapps that are on this list:
Yes, the date of those gapps are a little older, but that is what worked for me per OP'S instructions
I went through setup of my phone, fixing APN, Setting WIFI to USA, signing into Google after first loading into Rom instead of signing into Google on first bootup. Did a reboot
Installed Xposed, and the modules needed, reboot
I never received any error
I have done 3 nightly updates so far, as of 11/30. I am sure 12/1 will be ready in an hour or so.
I always click on about phone, download said update and let the process do its thing automatically, walk away and the phone is ready to use
Still no errors whatsoever. In fact, this has been the first version of AOSP I have used for the G3 with 0 errors. It is perfect, for me - No issues.
Hope that helps.
Click to expand...
Click to collapse
I did everything exactly as you did, including the 3 wipes, also out of habit. I too however, get the same error with the latest nightly. It starts popping up as I try to add my Gmail account at the initial setup. Previously, the 'unofficial' builds did not do this to me. This is the only rom that does this, I have tried them all out. I have yet to try to flash a different gapps package to see if that makes a difference. Apparently I dont get the data issues with cm12, but get phone issues with cm11.
I'm a bit relieved to see I'm not the only one having this problem. Been updating every night to see if maybe it's fixed, but I still get the same error. Didn't happen on the first nightly I flashed, though. It lol seems to be happening at random for me. Sometimes I'll set my phone down for a couple hours, working perfectly fine. Then I pick it up to check something and I suddenly start getting that error. I've tried every "solution" I find and none of them work for me. Even thought it was an issue with reading my sim card because when I get the error, it shows that my sim card isn't being read. But I still get it when I take it out. A normal factory reset doesn't fix it either. I have to do a complete data format to remove the error.
I found a quick little fix where i make a backup earlier in the day and just restore it whenever I start getting the error, but it's still very annoying.
Same issue
Hey bros,
Same thing here. It's a baseband radio issue. Notice in settings under About Phone it says 'Baseband Version: Unknown'. Either TWRP is flashing over our baseband (not likely, calls and texts can be made before the error message attacks come), or CM11 has some issue on certain builds with reading our SIM cards. I think having an official 10B or 11C flashable baseband radio to install at the time of the ROM install will fix this problem. Waiting on CM to patch the code will take too long. Let me know if you find one of these basebands or can find out how to extract it (from file manager or somewhere?) as I have not been able to find this info on XDA or anywhere.
EDIT: I FIXED IT
I'm a new member, and XDA won't allow me to post links..... look in the OP for JasmineROM (all credit to author for posting this 11C modem and fabulous stock LG debloated ROM) under downloads, you'll find the 11C modem. Download it.
1. Place 11C modem.zip on external or internal, whichever you want. I prefer external.
In TWRP:
2. Backup, unless youre livin' life on the edge.
3. Wipe it all except for external (or internal, if you prefer to flash from your internal storage)
4. Add to Install zip que in order:
a) latest CM11 nightly
b) 11C modem found in JasmineROM OP of main thread
c) GAPPs of your choice (I like nano PA GAPPs, and just install whatever else i want after)
5. FLASH
6. profit
7. PHAP
I have heard the 10B radio works great too. holler back and post results between the 2 stock radios for VS985.
Please hit thanks, as I am new and want to be helpful, where possible. Please share this so others know that we can overcome this nonsense.
CM11!!! Phappin' so hard right now!
Got it again.... totally blowed right now. maybe reconfig APN to match VZW and it will work?
Thanks for all the responses, it currently seems that the problem is cm11. I will probably wait for a stable build. For now, I'm using an unofficial cm12 ROM. Thanks for all the help!
Sent from my LG-VS985 using XDA Free mobile app
8pscott said:
Thanks for all the responses, it currently seems that the problem is cm11. I will probably wait for a stable build. For now, I'm using an unofficial cm12 ROM. Thanks for all the help!
Sent from my LG-VS985 using XDA Free mobile app
Click to expand...
Click to collapse
Are you using that PA GAPPs package that's in alpha? I think i'm going to give up and go to 12 too... I do know that the first official nightly of CM11 doesn't give me any errors, but Trebuchet is so buggy it won't take widgets. Had to download Nova
It makes me cry. My phone lasted through the night. Woke up at around 7 and it was fine. Went back to sleep and woke up at around 8:30 and I was crushed to see the problem happening again. There doesn't seem to actually be anything thy triggers it. :/
Yeah I think I'm gonna just try out cm12 and see how that goes.
Double check to make sure the phone isn't running in art. That fixed my problems! Xposed and art do not work together!![emoji2]
Im getting the same error on my phone usually a few says after using any of the nightlies. When i go to make a phone call it gives me the force close and doesnt stop. Ive since moved back to stock hoping someone had more info on the issue. My phone was not using Art but I did have xposed installed.
Hello
Maybe I will start from begining, I am the happy owner of SGS2 GT-9100 (I very like this phone, I had no problems with it). Once I installed cyanogenmod 11 without any problems, but after the stagefright hole in almost every Android distro I was trying to go for a fix and install the newest CM12.1 (cm-12.1-20150807-NIGHTLY-i9100.zip). Everything would be perfect except few bugs (I could not do a factory reset on example). By trying to go back to CM11 I have found a lot of problems, like:
- 404 error on official CM11 download page for GT-9100, I don't know why they have cleaned CM11 releases from FTP download; I need a little help there, because CM12.1 is not working as intended (File Manager have a big problems with reading internal and external disks )
Edit: Oh I think I was looking for bad links, the nightly editions seems to be removed day by day, but the snapshots are still possible to download. I will tell if this will work
- CWMR installation (I could not do this with the .zip format so I managed to work with Odin which was hard, I had to download CWMR from not really trusted source because official download links are not in .tar or .img format). Now my stock firmware (yes, I went back to stock for a while) won't boot and I have to find yet another solution to upgrade my phone
At now everything I have is a CWMR actually, but I don't have any CM11 zip copy :~( I have been looking for nighties instad of snapshots
I will tell if my problems will go away
Problem fixed, I just had to go little out of official page for CWM 6.0.4.5+ to install few zips. I usually don't like this kind of solutions but this was the only way to go back. At now I am testing CM12.1 and reinstall fixed the problem with File Manager :~~)
If you are after the latest nightly CM11(recommended over the M12 snapshot), you can download it from HERE. Be sure to hit the thanks button for @Acid0057 and @KOR_ALien for providing the links/downloads
Hi everyone,
My phone has this restarting loop issue after flashing either Candy7 or CM13 ROM. Not sure if this is bootloop error because It got pass the Huawei booting logo, but as soon as it finish loading the Google App and go to the OS home screen it restart again and again. Worth noting that the phone restart from ROM loading logo (the blue face for CM13 or the Google Dot for Candy7), not all the way back from Huawei booting logo.
First I use TWRP to factory reset wipe, then advance wipe /system, /data, /cache / Dalvik, then install new ROM + Gapp, and got the sucess message, then reboot to system.
I also tried with out Gapp to save loading time, and it restart again when get to OS home screen.
Please advise what may cause this.
No issue when i restore back to B322 EMUI 3.1
I have US version unlocked MT2-L03, B322 version, unlocked bootloader, rooted, TWRP 3.1.1.0 installed.
I made a video clip of the looping: https://www.youtube.com/watch?v=Y7kRpdGN2qA
I'm going through the EXACT same thing. I tried CM13, CM14 and even CandyRom, and the same thing happened more or less. Even if I got the ROMs running for a while, eventually that LOD (Loop of Death) would hit and I'd have to again reflash. I'm now back to B322 (Lollipop) for stability.
Given that the SAME thing is happening on all those ROMs, it's leading me to think that perhaps there is a software issue with my phone. Not sure if this helps, but I do think it could be the way I updated to Lollipop (B322) from the original Jelly Bean (B148). I've done a LOT of digging, and it looks like the way I did it was not quite right, even though my phone has worked fine all this time.
Here is the XDA post that seems to detail the correct upgrade path to B322:
https://forum.xda-developers.com/ascend-mate2/help/how-to-update-unlocked-mt2-l03-to-t3422775
Basically, it looks like the correct path should be B148 (Jelly Bean) --> B309 (Lollipop) --> B322 (Lollipop)
Being rather new, I just flashed to B322 right off of B148. I am now wondering if this could be the source of my problems. Especially since I keep getting the "Error 7" for "unknown bootloader" whenever I use TWRP 3.1.1 to flash LineageOS or CandyRom.
But, if you successfully used TWRP 3.1.1 to flash, that means your bootloader was recognized (I got the Error 7). If that's the case, then we're both having the same issue and something else is indeed the culprit.
I strongly suspect that "something else" could be GAPPS. I've experimented with several GAPPS packages, and noticed that right before crashing and the dreaded infinite loop, something glitched involving Google apps.
Desperately want to leave Lollipop since Oreo is about to drop meaning we Android L users are in for a world of hurt if we can't migrate soon. :-\
I upgrade my phone B148-B309-B322. I also get error 7 whenever I flashed the ROM, so I have to manually delete '"assert" command line from ROM script to flash successfully.
Error screen shot: http://imgur.com/zzTbjRJ
hondaman82 said:
I upgrade my phone B148-B309-B322. I also get error 7 whenever I flashed the ROM, so I have to manually delete '"assert" command line from ROM script to flash successfully.
Error screen shot: http://imgur.com/zzTbjRJ
Click to expand...
Click to collapse
My phone has been rooted for over a year now, I've had many roms on it doing that time. This loop started with a app I updated from the play store. Not sure it may be substratum will look into it when I have more time..
These problems is because of the room. Try to install lineageOs.
Thanks Kevinoriej,
Same looping issue on LineageOS, after loading to OS homescreen , phone restart.
Also get error 7, and manually remove "assert" lines in the ROM script in order to flash.
hondaman82 said:
I upgrade my phone B148-B309-B322. I also get error 7 whenever I flashed the ROM, so I have to manually delete '"assert" command line from ROM script to flash successfully.
Error screen shot: http://imgur.com/zzTbjRJ
Click to expand...
Click to collapse
I believe the Error 7 message is because your bootloader is showing as "unknown". I downloaded an app from the Playstore that gave me my device's technical info, and sure enough, my bootloader is listed as "unknown". I forwarded a question to Huawei's EMUI team asking them if that happened due to unlocking it (using Huawei's official unlocking request). Still waiting for a replay. In order to get any of the ROMs to install, I had to downgrade TWRP to 2.8.7.0. Any version above that would trigger Error 7.
Out of curiosity, I then downgraded and flashed CandySix (with a corresponding GAPPS package) - and sure enough, the same looping happened. And again when I flashed CM13 AND LineageOS. The phone would successfully boot, get to the actual Start screen, and then boot again. I could NEVER predict exactly what triggered this. Also, I tried installing ROMs without GAPPS, and that didn't go well for me (couldn't get any of them to load properly without flashing a GAPPS package for some reason).
Something goofy seems to be happening between Google services and the custom ROMs on this phone. I'm not sure what's triggering it, but given the sheer number of different ROMs I've tried - ALL of which have the EXACT SAME ISSUE - I strongly suspect there is indeed a GAPPS problem lurking somewhere.
As a side note - I reflahsed B322 (restoring from backup) and the phone is again as stable as it has always been.
Is there an EMUI GAPPS package for Marshmallow and/or Nougat (i.e., pulled from Mate 7, 8 or 9) available for download? I'm game for testing.
RE: MT2 boot loop
(*** SEE POST #25 FOR UPDATED FIX!***)
I just noticed this thread, wish I found it earlier. I recently posted my discussion of the boot loop (and fix) here:
https://forum.xda-developers.com/ascend-mate2/orig-development/cm-nougat-mt2-t3478345/page14
Bratzilla was right when he said in his post, "I strongly suspect there is indeed a GAPPS problem lurking somewhere".
Thanks EndlessFall,
please help to check this link: github(dot)com/opengapps/arm/releases/download/20170811/open_gapps-arm-7.1-pico-20170811.zip
no files listed.
RE: dead link for Open GApps previous versions & boot loop fix
Strange, it seems that in the past day Open GApps has purged their GitHub archive. The "Older Releases" button at their website still redirects to the GitHub repo, but it no longer displays any version other than the current one.
As long as it does not violate any policy, I can always post a copy of the Open GApps 08/11/17 ARM 7.1 Pico package.
Although I have not tried other GApps distributions (Delta, Beans, etc), in theory there is no reason why they shouldn't work, as long as Google Play Services is not newer than v11.3.02. I recommend the minimal GApps available. Installing "pico" was an important part of isolating, and simplifying the search for, the culprit.
As I mentioned in my original post, I tested all versions of Google Play Services on apkmirror newer than v11.3.02 (build format 436 for MT2L03), up until 08/26. All newer builds induced an immediate boot loop. A future version may resolve the boot loop issue and work fine on the MT2L03, but it does not seem to be available as of today.
Have been running custom ROMs on my MT2L03 for years. Boot looping problem began for me two weeks ago when I completely wiped/formatted my CandyROMs v7.1.2 06/15 install and flashed MDMower's 08/19 LineageOS. Began digging deep into the cause (knowing MDMower would not release garbage) and discovered the connection to Play Services. Have been running MDMower's LineageOS & CandyROMs v7.1.2 ever since without any issues.
Remember to use MDMower's TWRP v3.1N0-0, it is much more stable on the MT2L03.
Thanks again Endless,
I follow your instruction to flash Candie ROM and the matching GAPP from 6/15, all went well, no more bootloop. I will check the phone from time to time to see if the Loop of death come back, maybe once GAPP get updated it may come back. LOL... hopefully not though.
RE: MT2 boot loop fix (workaround)
Great, hondaman82 - so glad it worked for you. Funny, the exact same environment that you are using (06/15 CandyROMs with the matching 06/15 Open GApps) is what served as my "proof of concept" that current Open GApps with updated Play Services was likely the problem.
Although the proper GApps package resolves the boot loop issue, it is important to point out that it's more of a workaround than a fix. The root cause might be a bug in the AOSP/LineageOS source code itself, preventing MT2L03 compatibility with the latest versions of Play Services.
MDMower has just released a new build of LineageOS dated 08/29/17. I'll continue to test the latest ROMs with the latest GApps & Play Services to see if new commits/updates fix the problem...
hondaman82 said:
Thanks again Endless,
I follow your instruction to flash Candie ROM and the matching GAPP from 6/15, all went well, no more bootloop. I will check the phone from time to time to see if the Loop of death come back, maybe once GAPP get updated it may come back. LOL... hopefully not though.
Click to expand...
Click to collapse
EndlessFall said:
Great, hondaman82 - so glad it worked for you. Funny, the exact same environment that you are using (06/15 CandyROMs with the matching 06/15 Open GApps) is what served as my "proof of concept" that current Open GApps with updated Play Services was likely the problem.
Although the proper GApps package resolves the boot loop issue, it is important to point out that it's more of a workaround than a fix. The root cause might be a bug in the AOSP/LineageOS source code itself, preventing MT2L03 compatibility with the latest versions of Play Services.
MDMower has just released a new build of LineageOS dated 08/29/17. I'll continue to test the latest ROMs with the latest GApps & Play Services to see if new commits/updates fix the problem...
Click to expand...
Click to collapse
Have you had the chance to try 0829 Build of Lineage OS with newer GApps? TIA.
Oh nooo.. the LOD (loop of death) come back, after 3 days of working OK... sigh.... back to EMUI stock
RE: new ROM builds, GApps, & boot loop issue
Yes, I tested MDMower's LineageOS 08/29 last night using the 08/29 Open GApps package. Unfortunately, the boot loop bug persists. However, the 08/29 LineageOS runs great with Open GApps 08/11 and is worth installing (at least for me). Hopefully MDMower will keep up the good work and release a build in the next week or two with the Sept security patch.
I'll continue to test and report back if there is any progress...
MT2-User said:
Have you had the chance to try 0829 Build of Lineage OS with newer GApps? TIA.
Click to expand...
Click to collapse
EndlessFall said:
Yes, I tested MDMower's LineageOS 08/29 last night using the 08/29 Open GApps package. Unfortunately, the boot loop bug persists. However, the 08/29 LineageOS runs great with Open GApps 08/11 and is worth installing. Hopefully MDMower will keep up the good work and release a build in the next week or two with the Sept security patch.
I'll continue to test and report back if there is any progress...
Click to expand...
Click to collapse
Thanks!
RE: return of boot loop
Sorry to hear that Hondaman82.
I can only speak from my own experience, which is that my MT2L03 has been stable for the past 2 weeks using Open GApps pico dated no later than 08/11. It is possible that your Google Play Services was auto-updated to a version newer than v11.3.02 (inducing the loop), but you won't be able to tell because you can't boot the corrupted OS to read the version number in app settings. If my boot loop returns, I'll do an ADB pull from TWRP to examine the Play Services package version (curious to see if there is an update correlation).
Goes to show what I mentioned yesterday, which is that the root cause is likely some incompatibility between the ROMs customized for MT2L03 and Play Services that can only be fixed by a commit to the ROM source code, a script, patch, or change to Play Services.
Let's see what happens, perhaps MDMower would be willing to offer his expertise? I visited Matt's website, GitHub and XDA profile, but it seems difficult to contact him directly....
hondaman82 said:
Oh nooo.. the LOD (loop of death) come back, after 3 days of working OK... sigh.... back to EMUI stock
Click to expand...
Click to collapse
RE: preventing Google Play Services auto-update
(***SEE UPDATED FIX IN POST #25!***)
For those of you willing to experiment further, there is a method that supposedly disables Google Play Services from updating. This might allow you to "lock in" v11.3.02 until there is a proper fix for the boot loop:
https://forum.xda-developers.com/android/help/delete-disable-downgrade-prevent-update-t3091832
Basically, this involves using a root file manager to create two empty folders entitled "com.google.android.gms-1.apk" and "com.google.android.gms-2.apk" in the "\data\app" directory, causing auto-update to fail.
I haven't used this hack, try at your own risk!
Of course, this works off of the assumption that updating Google Play Services beyond v11.3.02 is the only factor involved in the boot loop. I just haven't dug deep enough...
Mine (Candy 0725 build) went into LOD by itself a moment ago
Does anyone have a B322 TWRP backup ZIP? I as of this morning have 2 MT2 phones dead. One went into LOD about 3am and the other about 4am.