My CM 10.2.1 has become increasingly temperamental until finally it always boots to a black screen (just backlight) unless I restore the last backup from my CWM SD card. I'm guessing the boot image has frayed a little around the edges and since I didn't keep a "brand new" backup from the original flashing, the only backups I have are probably a little wonky.
So it's been a little over a year since my original installation following digixmax's excellent directions. I've been thinking of just starting fresh with 10.2.1 and rebuilding my apps so here's a couple of questions:
1. Do I have to go all the way back to Stock 1.43 to follow these same directions? I had my NT repartitioned at B&N before I flashed CM, if that makes any difference.
2. Do I need to root before I flash CM (been too long and I just don't recall)?
3. After a fresh CM flash, would it be wise to use my last backup and Advanced restore so I can skip boot and (maybe) system--or should I just man-up and rebuild my apps from scratch?
OR....since I'm going to go through all of this, should I just flash CM 11 or 12 and get a newer system in the bargain? Reading about updating from CM 10.x to CM 11 has me a little spooked because I haven't been able to track down a definitive statement on whether the partitions have been combined or what that might mean for me.
Does anyone have a favorite 11.x or 12.x build? It looks like the M4 nightly for CM 11 was pretty well-behaved, but there are just so many choices.... I've been more or less happy with 10.2.1 (except for the now almost constant boot issue and lockscreen non-function), but I also know that app updates will eventually pass me by if I stay on 10.2.1.
I'd appreciate any help
Been using 12 for the past few months, no issues.
Sent from my Sensation using XDA Free mobile app
WnG88 said:
Been using 12 for the past few months, no issues.
Sent from my Sensation using XDA Free mobile app
Click to expand...
Click to collapse
Is there a particular set of instructions you followed?
Sent from my Nook Tablet CM 10.21
nmyshkin said:
My CM 10.2.1 has become increasingly temperamental until finally it always boots to a black screen (just backlight) unless I restore the last backup from my CWM SD card. I'm guessing the boot image has frayed a little around the edges and since I didn't keep a "brand new" backup from the original flashing, the only backups I have are probably a little wonky.
So it's been a little over a year since my original installation following digixmax's excellent directions. I've been thinking of just starting fresh with 10.2.1 and rebuilding my apps so here's a couple of questions:
1. Do I have to go all the way back to Stock 1.43 to follow these same directions? I had my NT repartitioned at B&N before I flashed CM, if that makes any difference.
2. Do I need to root before I flash CM (been too long and I just don't recall)?
3. After a fresh CM flash, would it be wise to use my last backup and Advanced restore so I can skip boot and (maybe) system--or should I just man-up and rebuild my apps from scratch?
OR....since I'm going to go through all of this, should I just flash CM 11 or 12 and get a newer system in the bargain? Reading about updating from CM 10.x to CM 11 has me a little spooked because I haven't been able to track down a definitive statement on whether the partitions have been combined or what that might mean for me.
Does anyone have a favorite 11.x or 12.x build? It looks like the M4 nightly for CM 11 was pretty well-behaved, but there are just so many choices.... I've been more or less happy with 10.2.1 (except for the now almost constant boot issue and lockscreen non-function), but I also know that app updates will eventually pass me by if I stay on 10.2.1.
I'd appreciate any help
Click to expand...
Click to collapse
The "boot to black screen" is a known bug in CM10.x (you find some brief discussions of this issue in the old CM10.x development thread.
You don't need to go back to stock to upgrade from CM10 to CM11 or CM12. The general process for performing the upgrade is outlined at http://forum.xda-developers.com/showthread.php?t=2670589. (For CM12.x, you'll need to locate a compatible recovery (to use in step 1(a)) which is typically referenced/linked in the first post of the corresponding CM12.x development thread).
If you're considering CM11 builds, I'd suggest you select a build that is sufficiently recent to have incorporated fixes for the Stage Fright security vulnerability (see http://www.cyanogenmod.org/blog/more-stagefright).
digixmax said:
The "boot to black screen" is a known bug in CM10.x (you find some brief discussions of this issue in the old CM10.x development thread.
You don't need to go back to stock to upgrade from CM10 to CM11 or CM12. The general process for performing the upgrade is outlined at http://forum.xda-developers.com/showthread.php?t=2670589. (For CM12.x, you'll need to locate a compatible recovery (to use in step 1(a)) which is typically referenced/linked in the first post of the corresponding CM12.x development thread).
If you're considering CM11 builds, I'd suggest you select a build that is sufficiently recent to have incorporated fixes for the Stage Fright security vulnerability (see http://www.cyanogenmod.org/blog/more-stagefright).
Click to expand...
Click to collapse
Thanks! I've been following a couple of related threads for awhile now. The most recent post in the thread following this one finally gave me the push and info I need. Just need to pick up another microSD card tomorrow
nmyshkin said:
...
The most recent post in the thread following this one finally gave me the push and info I need. Just need to pick up another microSD card tomorrow
Click to expand...
Click to collapse
Unless you plan on using the uSD card also to backup your current ROM and setup for ease in rolling back (which is a good idea), you don't need an external uSD card to upgrade from CM10 to CM11/12.
Related
I'm sure people were getting pretty tired of hearing about the radio issues when people flashed cyanogenmod (ie, LTE worked, but no SMS, MMS, or voice calls, odin didn't fix, the only solution was to factory restore from WITHIN a TW ROM). After waiting a while for things to calm down, I'm ready to try to install Cyanogenmod again but I am naturally hesitant.
Has this issued resolved itself? I'm running rooted and unlocked MC3 with CWM installed. I heard somewhere that flashing the MJ9 radio BEFORE Cyanogenmod 10.2 / 11 fixed the problem?
I would really appreciate any input or personal experience here!
As far as I know, the issue has not resolved itself. I tried flashing the newest CM 11 a couple of days ago (I think it was the nightly build on the 22nd), and I still had the funky radio issues. However, I tried this, and it fixed all the radio issues with CM 11 (and any other Android 4.4 ROMS - I'm running Slim ROM at the moment)... Here is my post from another thread.
Hey all, I got it working (the data/network connection that is), with a little effort. Here is what I did in sequence...
1) Reflash the ORIGINAL VRALJB image via ODIN. I used the one found here. You want to make sure you get the one that replaces EVERYTHING, i.e., NOT the alternative restore.
2) I set up my phone and used it normally for about four hours. (This may or may not be necessary, I'm not entirely sure. I also rebooted the phone about five times during that time frame.)
3) I unlocked and rooted the phone via the method outlined here. After that was done, I installed CWM 6.0.4.3 via TWRP (which the unlocking process installs).
4) I then installed CM 11 and the respective Google apps. (I first did a backup, then a factory reset, then cache wipe, then dalvik wipe. The next thing I did was install CM 11, then Gapps.)
5) Restart the phone and success!
Click to expand...
Click to collapse
The reason why I found out that this method would work, is that I tried installing CM 11 on my dad's phone. He has had a TW ROM (Beans build to be exact) since the phone came out. And he has been running the stock VRALJB radio. With that said, I figured I would try flashing the stock ODIN files to restore my phone back to the VRALJB. (I think I was running the MJ9 prior to this) That worked, and the SlimROM has been working perfectly ever since!
[Also, if you wanted to check out SlimROM, you can find a link to it here.]
Still looking for some more feedback from users! Anyone successfully flashed CM 10.2 / CM 11 from MC3 without problems / fixed the problems?
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.
Hi,
I'm currently running CM11 nightly (20141206) and haven't been running stock since at least a year and a half (read: I don't remember the last stock version I were running).
I have the common issue where Android cannot connect to the camera. The often posted "camera restart" does the trick, but I've read various places that flashing the latest stock rom and opening the camera once fixes this issue permanently, even after flashing custom roms again. Since my phone is laggy and I've been dirty flashing for a long time I figure it is time for a clean flash anyways. Is it correct that this would fix the issue?
If so, how should I go about doing it? I remember reading about an upgraded EFS partition in newer roms that aren't compatible with certain modems etc. My current baseband version is I9300XXEMB6. Is this something I need to take into account? (if I backup the current EFS and something goes wrong in upgrading to the newer version, will I be able to restore it afterwards?)
Also, does the latest stock roms contain Knox (or what it's called)? I suppose I don't want that?
I know there are bits and pieces spread around on the forum, but if someone could outline the process for me, or even better, point me towards some step by step guide covering the above, that would be much appreciated.
In advance, thanks a bunch!
-AndyGizzle
Trying a tiny little bump on this one
I am currently running CM11 and dealing with a lot of the problems that cm10 had. So tried CM12. Basically dead in the water. Never got past registration.
Very sluggish and the keyboard keeps disappearing. The installation of CM11 went pretty smoothly following the install instructions. Not so with CM12.
Maybe there is something I am missing. The instructions say that repartitioning is not necessary !?!??!
Anyway followed the instructions to the letter. Got the suggested recovery and flashed it just like on cm11. The correct gapps to use is always a crap shoot so I tried several. I even installed without gapps still had problems.
So any help here would be appreciated.
thanks
I have been testing CM12 for a few weeks and have a few of the same problems. It seemed like at first it was pretty snappy, but now it's sluggish, keyboard disappears constantly, and my biggest pet peeve is that quite a few of my apps are now unavailable for this device. They worked before, so it's a bug in CM or one of the newer Android versions. I'm just going back to an older ROM for now.
Hi cosmic_kid
I'm asking these same questions in the cm12 QA and dev pages and not getting anywhere. They all tell me to go read some more or stop being rude !?!??!?!
I am currently running cm11 and only have the usual problems just like cm10 had. i.e. battery, black out, losing wallpaper.
So I thought cm12 should be a piece of cake !!! NOT SO !!
There must be something different with the install that is screwing something up.
I tried the recommended eng recovery and the latest TWRP and CWM. Same results. After gapps is installed things go to heck.
I did try running cm12 before installing gapps and it ran smooth. After gapps sluggish and never got past registration. Keyboard never came up !?!?!?
I don't know what to do so I will download the latest nightly and try again.
I Feel Your Pain!
Guys, I know exactly how you feel. I merged the partitions according to the other posts, formatted cache and userdata to f2fs and tried all the nightlies that came out, but keyboard problems, superuser problems and setup crashes just made it impossible to get anything going on my trusty 8gb Nook (BNTV250A). The closest I got to getting anywhere with CM 12 on it was when I updated the CM 12 March 26th nightly on CM 11-M12 and added pa_gapps-modular-nano-5.0.1-20150315-signed. Play store worked, I was able to get into developer options and enable root access and it looked hopeful, but alas it was so slow and lagging that I have given up for now. I used repart.img to go back to stock, (touch pad didn't work on stock since I had upgraded to 10 touch!) booted off SD and installed CMW recovery to restore my CM 11 -M12 configuration. I'm staying in touch through all the threads and hopefully we will one day have a smooth CM12 on our beloved Nooks!
CM12 is now working very smoothly on my 16gb nook. I didn't have to repartition anything. I just about got rid of my 16gb nook because it's older and slower than the newer 8gb nook. Glad I didn't.
So until there is a "how to" thread on how to get it to work on the 8gb nooks I will be using the older one.
The devs said that they didn't have a 8gb model to test their nightlys on. I'm wondering if they test them at all ???
What did you do to get it to run smoothly? I have the 16GB and it slows down all the time with CM12. I read gapps causes a lot of head-aches so I've been tempted to run without it and just side-load all my apps... :/
cosmic_kid said:
What did you do to get it to run smoothly? I have the 16GB and it slows down all the time with CM12. I read gapps causes a lot of head-aches so I've been tempted to run without it and just side-load all my apps... :/
Click to expand...
Click to collapse
pico gapps and Demetris' 16GB CM12 with the Tricker Mod stuff = faster than they day I bought it.
Now I just need 8GB working the same, since I have two of those!
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.