Hello together,
Last week I bought two devices: Apollo (w/o LTE) + Thor (incl. LTE)
Today I installed on the Apollo device CM 14.1, but the issue is,
Issue 1: the screen does not rotate. Only apps are switching the rotation.
Issue 2 (minor): WiFi connection lost after sleep
What I did today:
- Rooted the original installation (14.3.0.2_user_302075320) with KingRoot
- Unlocked and installed TWPR based on http://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982 ( I followed all steps except of the aboot_vuln.mbn, as the firmware was below 14.3.2.3.2)
- Full wipe, Flashed CM 14.1 (first official nightly) incl. pico OpenGapps
- Noticed the problem
- Upgraded the bootloader to 14.3.2.3.2 based on http://forum.xda-developers.com/kin...p-flashable-3-2-3-bootloader-upgrade-t3025504
- Problem still there
- Flashed CM 11 from http://forum.xda-developers.com/kin...-cm-11-safestrap-20150628-unofficial-t3145547
- Problem gone (as already on original FireOS)
Any help is welcome, so that I can use CM 14.1 as others do not seem to have this problem. If you need further information (logs, retries with our custom roms, ...), I am happy to provide/do it.
Zathor said:
Hello together,
Last week I bought two devices: Apollo (w/o LTE) + Thor (incl. LTE)
Today I installed on the Apollo device CM 14.1, but the issue is,
Issue 1: the screen does not rotate. Only apps are switching the rotation.
Issue 2 (minor): WiFi connection lost after sleep
What I did today:
- Rooted the original installation (14.3.0.2_user_302075320) with KingRoot
- Unlocked and installed TWPR based on http://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982 ( I followed all steps except of the aboot_vuln.mbn, as the firmware was below 14.3.2.3.2)
- Full wipe, Flashed CM 14.1 (first official nightly) incl. pico OpenGapps
- Noticed the problem
- Upgraded the bootloader to 14.3.2.3.2 based on http://forum.xda-developers.com/kin...p-flashable-3-2-3-bootloader-upgrade-t3025504
- Problem still there
- Flashed CM 11 from http://forum.xda-developers.com/kin...-cm-11-safestrap-20150628-unofficial-t3145547
- Problem gone (as already on original FireOS)
Any help is welcome, so that I can use CM 14.1 as others do not seem to have this problem. If you need further information (logs, retries with our custom roms, ...), I am happy to provide/do it.
Click to expand...
Click to collapse
Known issue on Apollo CM 14.1 builds; developer is actively pursuing. See CM 14.1 thread for current status and possible work around (Nova launcher).
BTW - kudos on your efforts to date. Shows familiarity with the material and a willingness to read/research/self-help. Refreshing!
Davey126 said:
Known issue on Apollo CM 14.1 builds; developer is actively pursuing. See CM 14.1 thread for current status and possible work around (Nova launcher).
BTW - kudos on your efforts to date. Shows familiarity with the material and a willingness to read/research/self-help. Refreshing!
Click to expand...
Click to collapse
Thank you very much for your kind reply.
I tried the Nova launcher approach, but it does not work sadly. ggow suggested for the LTE device to install the complete firmware 14.3.2.3.2 - maybe this helps here also, as others do not seem to have the problem. How would I do that in the current state of the device? And how should I do that with the untampered Thor device (13.3.2.4_user_324002120) - let it update to 4.5.5.2 and as root seems to work unlock the bootloader from there?
Zathor said:
Thank you very much for your kind reply.
I tried the Nova launcher approach, but it does not work sadly. ggow suggested for the LTE device to install the complete firmware 14.3.2.3.2 - maybe this helps here also, as others do not seem to have the problem. How would I do that in the current state of the device? And how should I do that with the untampered Thor device (13.3.2.4_user_324002120) - let it update to 4.5.5.2 and as root seems to work unlock the bootloader from there?
Click to expand...
Click to collapse
- hold on bootloader update as there was a recent report of an unfavorable outcome (bricked device); need to see how that plays out
- for 13.3.2.4 root with TowelRoot and then proceed with bootloader unlock; keep device off network (WiFi off) except when rooting to prevent an OTA update; no need to update FireOS for bootloader unlock - root is sufficient
Ok, I will wait with the bootloader update for Thor, for Apollo I have already done it sucessfully yesterday (see first post).
I tried a few additional custom roms:
- cm-11-SAFESTRAP-20161016-UNOFFICIAL-apollo: OK
- cm-12.1-20160922-UNOFFICIAL-apollo: OK
- cm-13.0-20161108-NIGHTLY-apollo: OK
- cm-14.1-20161218-NIGHTLY-apollo: NOT OK
So the screen stuck in one orientation seems to be a CM 14.1 problem only.
To be honest I do not know why, but the problem is solved. After dirty flashing (without wipe) from cm-13.0-20161108-NIGHTLY-apollo to cm-14.1-20161218-NIGHTLY-apollo the automatic screen rotation does work now. Even after a full wipe and a clean installation of CM 14.1 (which I always did before), it does work now.
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?
DISCLAIMER: I AM IN NO WAY RESPONSIBLE FOR ANY PROBLEMS ON YOUR DEVICES CAUSED BY FLASHING THESE BUILDS. THE UPSTREAM CODE AND BUILDING IS MAINTAINED BY THE CYANOGENMOD TEAM, NOT ME. I AM NOT ASSOCIATED WITH THEIR TEAM, I AM JUST THE THREAD OWNER.
What is CyanogenMod ? It is an aftermarket firmware for a number of cell phones based on the open-source Android operating system. It offers features not found in the official Android based firmwares of vendors of these cell phones.
CyanogenMod 13.0 : Download
Changelog : Changelog
Open GApps : Download ( arm, 6.0, nano )
TWRP : Download​
CM13 Nightlies, ROM for the Sprint Galaxy S5
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Nightly, now moved to 14.1
UPDATE 6/14: Looks like there's an issue that 5ghz network doesn't work on higher bands, but it works on 36-48 and bluetooth. Hopefully it will be fixed soon.
UPDATE 6/23: There's a fix attempt on boot image. Link. Thanks to @haggertk
UPDATE 6/27: Looks like Bluetooth and Wifi issue have been fixed since 6/25 nightly.
Thanks to @haggertk
Created 2016-05-12
Last Updated 2016-11-29
Reserved
Works great!
Is there a version of SuperSU that works with CM13? All trash the ROM and have to do full restore.
I just needed confirmation on something. I'm currently running CM12.1 on a SM-G900P with firmware G900PVPU3BOK4. Does the update to CM 13.0 require a firmware update to G900PVPU3CPCA (the MM level of firmware from the stock Sprint download) or can I stay on G900PVPU3BOK4 with CM13.0?
btw: Sorry for the double post. I'm new to XDA and having trouble figuring out which forum is correct for me to ask my questions in.
Thanks!
alexclang said:
I just needed confirmation on something. I'm currently running CM12.1 on a SM-G900P with firmware G900PVPU3BOK4. Does the update to CM 13.0 require a firmware update to G900PVPU3CPCA (the MM level of firmware from the stock Sprint download) or can I stay on G900PVPU3BOK4 with CM13.0?
btw: Sorry for the double post. I'm new to XDA and having trouble figuring out which forum is correct for me to ask my questions in.
Thanks!
Click to expand...
Click to collapse
From my limited experience, it does not appear to run on CPCA. CM13 on OK4 worked for me.
e-j said:
From my limited experience, it does not appear to run on CPCA. CM13 on OK4 worked for me.
Click to expand...
Click to collapse
Excellent!! I'll just install the latest nightly for CM13 just like I was going for 12.1 and hopefully things will go smoothly!
I'm having difficulty with CM13 and Open GApps. If I flash CM13 alone everything is fine. When I install CM13 and then the ARM 6.0 pico Open GApps through the same TWRP 3.0.2-1 session (as directed here: https://github.com/opengapps/opengapps/wiki/Notes-for-Android-6.0), I either get constant force close errors after boot (with 5/19 CM & GApps zips) or an endless blue android boot screen (with 5/20 CM & GApps zips). I've tried re-downloading the zips and reinstalling after wiping (dalvik, system, data, cache) multiple times.
Any ideas?
UPDATE/PSA: USE THE NANO GAPPS AS STATED IN THE OP. NANOGAPPS INFINITY OPENS THE DOOR.
e-j said:
I'm having difficulty with CM13 and Open GApps. If I flash CM13 alone everything is fine. When I install CM13 and then the ARM 6.0 pico Open GApps through the same TWRP 3.0.2-1 session (as directed here: https://github.com/opengapps/opengapps/wiki/Notes-for-Android-6.0), I either get constant force close errors after boot (with 5/19 CM & GApps zips) or an endless blue android boot screen (with 5/20 CM & GApps zips). I've tried re-downloading the zips and reinstalling after wiping (dalvik, system, data, cache) multiple times.
Any ideas?
Click to expand...
Click to collapse
I've had similar issues; all with Google apps. When I see it, I delete the Google app in question and then immediately re-install from the App store. Once I've done that, I haven't had the Google app force quit again.
alexclang said:
I've had similar issues; all with Google apps. When I see it, I delete the Google app in question and then immediately re-install from the App store. Once I've done that, I haven't had the Google app force quit again.
Click to expand...
Click to collapse
Got it working after I realized the OP specifically mentioned the "nano" GApps variant; booted fine after a clean install of CM13 & the nano zip.
Issues w. CM13 flash
Ok... slightly frustrated here.
Basic issue: Have flashed CM13 (Nightly 5.17.16) along with the latest Gapps. Upon reboot my phone will go to the Cyanagenmod splash screen, appear to load for several seconds, and then restart. It keeps doing this for at least 10 minutes until I turn it off. I have re-flashed a couple times after reloading the backup but no change.
Process I used: First of all my phone already has Android 6.0.1 firmware installed (not sure if that's an issue). I have TWRP setup as recovery and rooted with su 2.52 (and yes I verified the root prior to flashing). To flash I boot into recovery (obviously), factory reset, install cm13, clear dalvik, and repeat process with gapps. I've done this before with older CM's successfully but for some reason I can't get past the CM splash screen.
Any assistance is appreciated. If I have made a completely stupid error in my process or this exact issue is covered in another thread don't hesitate to point that out!!
Thank you in advance.
smspenc said:
Ok... slightly frustrated here.
Basic issue: Have flashed CM13 (Nightly 5.17.16) along with the latest Gapps. Upon reboot my phone will go to the Cyanagenmod splash screen, appear to load for several seconds, and then restart. It keeps doing this for at least 10 minutes until I turn it off. I have re-flashed a couple times after reloading the backup but no change.
Process I used: First of all my phone already has Android 6.0.1 firmware installed (not sure if that's an issue). I have TWRP setup as recovery and rooted with su 2.52 (and yes I verified the root prior to flashing). To flash I boot into recovery (obviously), factory reset, install cm13, clear dalvik, and repeat process with gapps. I've done this before with older CM's successfully but for some reason I can't get past the CM splash screen.
Any assistance is appreciated. If I have made a completely stupid error in my process or this exact issue is covered in another thread don't hesitate to point that out!!
Thank you in advance.
Click to expand...
Click to collapse
Would boot loop on the latest firmware for me as well; had to Odin back to OK4.
smspenc said:
Ok... slightly frustrated here.
Basic issue: Have flashed CM13 (Nightly 5.17.16) along with the latest Gapps. Upon reboot my phone will go to the Cyanagenmod splash screen, appear to load for several seconds, and then restart. It keeps doing this for at least 10 minutes until I turn it off. I have re-flashed a couple times after reloading the backup but no change.
Process I used: First of all my phone already has Android 6.0.1 firmware installed (not sure if that's an issue). I have TWRP setup as recovery and rooted with su 2.52 (and yes I verified the root prior to flashing). To flash I boot into recovery (obviously), factory reset, install cm13, clear dalvik, and repeat process with gapps. I've done this before with older CM's successfully but for some reason I can't get past the CM splash screen.
Any assistance is appreciated. If I have made a completely stupid error in my process or this exact issue is covered in another thread don't hesitate to point that out!!
Thank you in advance.
Click to expand...
Click to collapse
You had the official MM installed from Samsung, correct?
As far as I know, the current CM13 needs LP bootloader installed.
I have no issue with LP bootloader.
lentm said:
You had the official MM installed from Samsung, correct?
As far as I know, the current CM13 needs LP bootloader installed.
I have no issue with LP bootloader.
Click to expand...
Click to collapse
Yeah that was exactly the issue. Reflashed 5.0 then made the jump and it worked perfectly. So much wasted time...
---------- Post added at 05:28 AM ---------- Previous post was at 05:25 AM ----------
e-j said:
Would boot loop on the latest firmware for me as well; had to Odin back to OK4.
Click to expand...
Click to collapse
Yeah reflashing lollipop then installing cm13 did the trick.
Does this Rom fix Bluetooth issues?
Sent from my SM-G900P using XDA-Developers mobile app
has anyone got themes to work ine keeps crashing
manolze said:
has anyone got themes to work ine keeps crashing
Click to expand...
Click to collapse
Mine works fine with Puzzled UI - CM Theme from Play Store on 5/20 build.
I have no working theme chooser on this releaese
xenokc said:
Works great!
Is there a version of SuperSU that works with CM13? All trash the ROM and have to do full restore.
Click to expand...
Click to collapse
no need just go into developer and turn on root access
---------- Post added at 03:28 PM ---------- Previous post was at 03:24 PM ----------
anyone have a solution to theme chooser yet? i have already fixed phone dial problem and time out of sync problem
xpm69420 said:
no need just go into developer and turn on root access
---------- Post added at 03:28 PM ---------- Previous post was at 03:24 PM ----------
anyone have a solution to theme chooser yet? i have already fixed phone dial problem and time out of sync problem
Click to expand...
Click to collapse
Theme chooser works great for me, not having any issues with it. I am having an issue with the time being or of sync when set to automatic... How'd you fix it? Also, what's wrong with the dialer... can't say I'm having any issues there either.
unclejuju said:
Does this Rom fix Bluetooth issues?
Sent from my SM-G900P using XDA-Developers mobile app
Click to expand...
Click to collapse
I little late here, but CM 13.0 did NOT fix the S5 bluetooth issues. Still have the skipping and studdering.
This is a port of OMNIRom 7.1.1 for the Samsung Galaxy Tab A 7.0 (2016) LTE SM-T285. OMNIRom aims to be a community based project and is a lot "lighter" than CyanogenMod/LineageOS.
5.1.1 is the best that you can get from samsung right now and it is not known if they plan to do any upgrades. I have absolutely no idea why samsung chose to stay with the outdated 5.1.1 mid 2016 when we already got 7.1 coming out. This custom rom is probably the best you can get if you want an upgrade from Lollipop. Performance on the latest build is also better, you be the judge.
Though this is stable enough that I use it currently as my daily driver, make sure you read the pending issues below and decide if this is acceptable to you before you flash this rom. This rom probably won't get much use out of some people until bluetooth is fixed.
Based off on OMNIRom 7.1.1 N4F260 sources which is based on Marshmallow.
For more information on OMNIRom and its features see their site here.
Device Tree:
=========
https://github.com/jedld/device_samsung_gtexslte.git
https://github.com/jedld/vendor_samsung_gtexslte.git
https://github.com/jedld/kernel_samsung_gtexslte.git
Omnirom Notes:
=============
- omnirom doesn't have ffmpeg libraries unlike the CM based roms, but no worries since I ported over CMs libraries here.
Works:
- Wifi/LTE/SMS (Some users report data intermittently not connecting, though toggling airplane mode on/off can fix it)
- Audio
- Graphics
- Bluetooth
- Wifi Hotspot
- MTP
Does not work:
- Calls (needs testing)
- Camera
- GPS (no fix)
- probably more (need testers)
Download
========
Remember flashing an unofficial ROM on your samsung device will probably void your warranty. Don't expect samsung to support you if you have any issues.
As always flash this at your own risk. Make sure you have a copy of the stock ROM so that you have something to fall back to, which is highly the case when using an experimental rom.
See DevDB download section for older releases. Or click below for the latest release:
https://forum.xda-developers.com/devdb/project/dl/?id=23245
Note that this rom is pure stock and does not come with the Play Store or any Gapps, I suggest you download a micro gapps package separately and install it via recovery.
There have been reports that recent versions of open gapps don't work properly, it is advised to use older versions instead (e.g. open_gapps-arm-6.0-nano-20161109.zip)
Installation Instructions
==================
Perform a backup of all of your important files. This ROM is experimental and I will not be responsible for your loss of data.
Download the zip file and extract the tar.
Use Odin/Heimdall to flash the tar file to your device. If you are coming from stock oranother rom make sure you wipe first using TWRP. Coming from a previous version of OMNIRom for SM-T285 may not require a wipe, however please perform a wipe if you encounter problems.
Root and customization
===================
This ROM is a purely based on source and is not rooted out of the box. However you can easily root it by using TWRP to install the latest version of SuperSU.
If you want to customize this ROM and repackage it you may use this guide as a reference.
XDA:DevDB Information
Omnirom 7.1.1 Galaxy Tab A 7 LTE SM-T285, ROM for the Samsung Galaxy Tab A series
Contributors
jedld
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: Omnirom
Version Information
Status: Testing
Created 2017-02-18
Last Updated 2017-02-20
Possible Hope?
Im Not A Developper But I'm The Closest Thing There Is To It. Il Be Running Some Tests To See If It Might Be Compatable With The Sm-t280 Model. Any Boot.Img I Should Install First?
thanks Jedid-did you have a link here for the ROM as I cannot see it (says status is testing so perhaps a placeholder?) as always great work!
mac231us said:
thanks Jedid-did you have a link here for the ROM as I cannot see it (says status is testing so perhaps a placeholder?) as always great work!
Click to expand...
Click to collapse
should be available now
Tinker101 said:
Im Not A Developper But I'm The Closest Thing There Is To It. Il Be Running Some Tests To See If It Might Be Compatable With The Sm-t280 Model. Any Boot.Img I Should Install First?
Click to expand...
Click to collapse
It will be a long shot, there are hardware differences, but nothing stopping you from trying it. Do note that the T280 has a padded boot.img see here, which means you need to get the boot.img from this rom and add an additional header in front of it before you flash it with heimdall or odin.
jedld said:
should be available now
Click to expand...
Click to collapse
thanks Jedid
will look in a couple of days when I the Tab back (gave it to a friend)
EDIT
tried the ROM today...calling is a problem (for me) tried multiple times of reboot and allowed rom to settle before making calls (4g and data in out activity was showing-could go to internet)
The call does not connect and sits in dialing mode forever...if you try to hang up it then sits in hanging up mode and will not terminate
(shows a call in progress as if it is still on)...sms works
With all credit to you and all due respect...I stopped there-
think your very FIRST Lineage 14.1 was the best in all the Nougat ROMs
(the next one had issues with the drives seen but not accessible even though the MTP thing was purported to have been solved in that one)-i.e no real files just drives with overall sizes shown and then the lockscreen issue made it unusable (the PIN and notification method was risky as swiping the notification accidentally would lead to an inaccessible phone or maybe demand a reboot)
Works for me
I don't use the Sim functionality at all, so can't comment on that. I had to try a few variations of GApps to get a working Google Play service, and finally managed with the Dynamic GApps 20170215 Minimal build. Once I got that going, everything worked well. I'm using this as my daily ROM on the tablet now, so will report any further issues I have. Just wanted to say a big thank you! This ROM is very fast and smooth.
home button to wake up device
hi, i just use this rom and its really fast..
just want to ask how to make home physical button to wake up device beside the power button ?
Original Link worked but the file i got
"omni-6.0-20161209-UNOFFICIAL-SMT285-BETA-3.tar"
did not flash, rejected by Odin.
The new one you have linked works
"omni-7.0-20170219-UNOFFICIAL-SMT285.tar"
Quick scan results:
Mem use 462mb of 1.4gb
Space use 2.71 of 7.28gb
Apps installed 17
Very Similar to Lineage "LINEAGE-OMS-14.1-20171209-UNOFFICIAL-SMT285.tar".
In fact almost exact other than a couple of megabytes and an app.
This is BEFORE SU And APP Remover has gone in to shred some files
Stock rom: Terrible
Mem use 5 TB of 1.4gb
Space use Smoke coming out of 7.28gb
Apps installed Still counting I was sure it would finish last week.
Stock rom: Terrible
Mem use 874mb of 1.4gb
Space use 3.7gb of 7.28gb
Apps installed 64
Vol Down Button
Home
Power
[DOWNLOAD SCREEN]
Vol Up to confirm
{Go to PC Odin}
Load AP Custom Rom (TWRP Required)
Press Start...
file explorer cannot read files in internal and external sd card, is it just me, or anyone else?
Download
thank
Can anyone send me other link this ones showing not found.
Link not found
thatha said:
Link not found
Click to expand...
Click to collapse
index - powered by h5ai v0.30.0 (https://larsjung.de/h5ai/)
index - powered by h5ai v0.30.0 (https://larsjung.de/h5ai/)
aol.zanoza.lv
Here is the link.
Reload 4 times if not loading.
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.
Hello guys,
as the title says I am currently with the mobile data connection not being established on custom ROMs, the official MIUI ROM works fine. Before trying to go to LineageOS 14.1 I ran this 13.1 ROM for quite some time successfully.
This is what I did since trying to migrate to Andoid 7.1:
I flashed the latest MIUI Global Dev ROM, this locked my bootloader again, so I tried this for installing TWRP and custom ROMs with locked bootloader and this for unlocking the bootloader unofficially. Both methods generally worked, but mobile data did work on neither of them (I checked for the correct APN).
So I tried to go back to the LineageOS 13 ROM (clean flash, since I accidentally deleted my backup) I used before, but it also does not work on that version anymore.
Does anyone have any idea what the issue could be or how I could possibly find out what causes this?
Edit: I am now actually back to the latest MIUI Global Dev and hoping that I am able to unlock the bootloader officially eventually. But any tips on the issue above would still be appreciated.
Edit 2: On the 8.0 NitrogenOS mobile data does work. I first thought that it yet had to be an APN problem, so I copied the settings from this ROM to the LineageOS 14.1 ROM and deleted all other APNs, but that actually did nothing, it still did not work. So I guess I will stay on 8.0 for now, although I wanted 7.1 because of XPosed.
Edit 3: Suddenly stopped working on Android 8. Seems to work on the first boot after flashing a Android 8 ROM and then not anymore. Going back to MIUI...
This post helped me with the issue. After a soft reboot mobile data just works fine even after enabling/disabling airplane mode.
triplec0re said:
This post helped me with the issue. After a soft reboot mobile data just works fine even after enabling/disabling airplane mode.
Click to expand...
Click to collapse
Did you find a persistent method to solve the problem?
I have the same problem but Mobile Data only works after first boot and first soft reboot - than never ever.
BTW it works on MIUI ROMS without any problem.
b0mb said:
Did you find a persistent method to solve the problem?
I have the same problem but Mobile Data only works after first boot and first soft reboot - than never ever.
BTW it works on MIUI ROMS without any problem.
Click to expand...
Click to collapse
I did just recently find a persistent method. Read here: https://forum.xda-developers.com/showpost.php?p=70887635&postcount=9