Related
Hey
I’m am a regular CM9 user on my Galaxy S II. It was running very well till the last month (build 20120330). Since build 20120402 I’ve been getting weird problems. with Gapps. Gmail and News & weather crash as soon as phone starts and Play Store always gives a “Server error” message. I’ve tried build 20120317 and 20120304.
I don’t know where am I going wrong. Here are the steps that I follow while flashing CM9 update:
Flash CM9 update > then Gapps > Wipe Cache > Wipe Dalvik Cache
I’ve even tried side installing market from APK instead of flashing Gapps but that makes even the Store crash everytime I try to open it. Clearing data doesn’t work.
Further, factory resetting the phone and then flashing CM9 disables the home button. It only works for unlocking the display. The power button options get reduced to only Power Off, Restart and Airplane Mode. Screenshot, profile, sound options all disappear.
It’s hard to live with CM9, other ROMs aren’t that good. They lack in either functions or battery life. Can somebody help me please?
why not make a clean install using the resurrection edition and then update to the latest build and see if the problem persists? using the resurrection edition should solve your issues.
Hey bala_gamer, thanks for your quick reply. I'll do that right now and let you know if it solved my issue.
EDIT: Resurrection build (20120330) is too old It hasn't been updated this month. Could you tell me which version of Gapps are you using btw?
Saketme said:
Hey bala_gamer, thanks for your quick reply. I'll do that right now and let you know if it solved my issue.
EDIT: Resurrection build (20120330) is too old It hasn't been updated this month. Could you tell me which version of Gapps are you using btw?
Click to expand...
Click to collapse
its ok with the resurrection build, its just a week old
im using the latest gapps pack 17/3/12
http://goo.im/gapps/gapps-ics-20120317-signed.zip
Hey, I looks like you didn't read my post correctly. CM9 build 20120330 is already working fine for me, the builds released in this month are bugging me. :-(
Hello guys,
I tried the new version gapps-jb-20121128-signed.zip with CM10, but it is not recommended. The playstore will not work anymore and the keyboard process will stop.
Question, flash doesn't work in the browser? I installed gapps-jb-20120726-signed.zip several times but still flash is not working.
Somebody any idea how to solve this?
Foster Basic said:
Hello guys,
I tried the new version gapps-jb-20121128-signed.zip with CM10, but it is not recommended. The playstore will not work anymore and the keyboard process will stop.
Question, flash doesn't work in the browser? I installed gapps-jb-20120726-signed.zip several times but still flash is not working.
Somebody any idea how to solve this?
Click to expand...
Click to collapse
Hi,
Managed to solve this issue by reinstalling the previous gapps and then reinstalling the firmware. Hope this info helps.
gapps-jb-20121128-signed.zip - I also had problem with this update
Foster Basic said:
Hello guys,
I tried the new version gapps-jb-20121128-signed.zip with CM10, but it is not recommended. The playstore will not work anymore and the keyboard process will stop.
Question, flash doesn't work in the browser? I installed gapps-jb-20120726-signed.zip several times but still flash is not working.
Somebody any idea how to solve this?
Click to expand...
Click to collapse
I also had problem with this update!!!!!!!
Problem with 28 Nov. GooManager received update for Jandycane 1.8
(updates jandycane 20121020 and gapps 20121011 done on 09/11/12)
........................
On 28 November GooManager automatically downloaded the following: gapps-jb-20121128-signed.zip
On the 29 November I flashed this on my first gen. Kindle Fire
As follows:
first did a Backup then wiped Cache and Dalvik and then started update - gapps-jb-20121128-signed.zip
after starting update got a Dalvik cache Directories wipe complete message (then)
Verifying Filesystem....
Verifying partition sizes...
Install ........ gapps-jb-20121128-signed.zip
Finding update package
installing
......
......
(and finally)
Installation Complete!
(then once again under this the texts)
Verifying Filesystem....
Verifying partition sizes...
But there it seems to have stopped (completed?)
And under in TWRP I have the options: Wipe Cache/Dalvik - Home - Reboot System
I decided to choose Reboot system
The following happened:
I got a message "upgrading Android apps"
then it started in the normal ("turning mirror bits") loading window
then the usual password window
but the keyboard wouldn’t open!!! I couldn’t get past the password window
also I notice that the WLAN was no longer on/active (it had been on during the process)
I tried several reboots – still the same
I eventually decide to do a restore of Backup – this was successful!
I have no idea what is or went wrong
Is there something wrong with this gapps-jb-20121128-signed.zip it certainly seems like it?????????
Any other experiences?
I've had the exact problems you both describe running a clean flash of nightly with CM10 on a Nook Color. Everything is great until gapps-jb-20121128-signed.zip is loaded, then keyboard is disabled, crashes, etc.
http://goo.im/gapps/gapps-jb-20121128-signed.zip appears to have been removed from goo.im
gyrfalcon said:
I've had the exact problems you both describe running a clean flash of nightly with CM10 on a Nook Color. Everything is great until gapps-jb-20121128-signed.zip is loaded, then keyboard is disabled, crashes, etc.
http://goo.im/gapps/gapps-jb-20121128-signed.zip appears to have been removed from goo.im
Click to expand...
Click to collapse
Hi, and thanks for replying - now I know for sure it wasn't me that screwed up, wasn't sure!
Glad to hear that it has been removed - but that's really bad - sending out a really bad update like that - lucky we didn't end up with Bricked devices - really frustrating and not a nice thought at all - I'm really grateful for whoever it is that does all this work...but...putting something like that out ... that is scary ........ don't know if I will now trust the next download(s)!!!!!!!!
who is it that does these gapps anyway?
Total Noob, not sure what I did.
Long story short, rooted my Galaxy Tab 10.1 wifi (p7510) tonight.
Saw a video on how to flash 4.1 onto my tab here: http://www.youtube.com/watch?v=KRjl7zh551w
followed the instructions from the video, it linked to http://forum.xda-developers.com/showthread.php?t=1787399
downloaded the latest nightly from http://get.cm/?device=p4wifi
(cm-10.1-20130124-NIGHTLY-p4wifi.zip )
and the gapps from mirror 1 at http://forum.xda-developers.com/showthread.php?t=1787399
(gapps-jb-20120729.zip)
There was probably my mistake
In any case, i wiped everything, flashed the CM10 and gapps.
On reboot I got 2 error messages,
"Unfortunately, the process com.google.process.gapps has stopped." ok
"Unfortunately, Setup Wizard has stopped." ok (loops forever)
Now I have no idea how to recover from this point.
I tried to re-wipe and re-flash my old functioning ICS root and it still reboots into CM loading screen and setup wizard loop
Also, if i attempt to install zip from sdcard my options are:
0/
legacy/
obb/
legacy and obb contain no files and I have to navigate down a couple of layers of 0/ to reach my original root.
Probably screwed myself royally, but I guess that's how you learn. Any advice on how to salvage my tab?
Update*
Restore finds no files to restore
used odin for TWRP instead of CM, still no luck at restoring.
Won't mount USB, so I don't know how to transfer over a different gapps to see if that would solve the problem.
Revert to stock 4.0.4 through odin and start over. Probably be the easiest. I've had to a few times and yes it's how you/we all learn...
Firmware Here
nighthorns said:
Total Noob, not sure what I did.
Long story short, rooted my Galaxy Tab 10.1 wifi (p7510) tonight.
Saw a video on how to flash 4.1 onto my tab here: http://www.youtube.com/watch?v=KRjl7zh551w
followed the instructions from the video, it linked to http://forum.xda-developers.com/showthread.php?t=1787399
downloaded the latest nightly from http://get.cm/?device=p4wifi
(cm-10.1-20130124-NIGHTLY-p4wifi.zip )
and the gapps from mirror 1 at http://forum.xda-developers.com/showthread.php?t=1787399
(gapps-jb-20120729.zip)
There was probably my mistake
In any case, i wiped everything, flashed the CM10 and gapps.
On reboot I got 2 error messages,
"Unfortunately, the process com.google.process.gapps has stopped." ok
"Unfortunately, Setup Wizard has stopped." ok (loops forever)
Now I have no idea how to recover from this point.
I tried to re-wipe and re-flash my old functioning ICS root and it still reboots into CM loading screen and setup wizard loop
Also, if i attempt to install zip from sdcard my options are:
0/
legacy/
obb/
legacy and obb contain no files and I have to navigate down a couple of layers of 0/ to reach my original root.
Probably screwed myself royally, but I guess that's how you learn. Any advice on how to salvage my tab?
Update*
Restore finds no files to restore
used odin for TWRP instead of CM, still no luck at restoring.
Won't mount USB, so I don't know how to transfer over a different gapps to see if that would solve the problem.
Click to expand...
Click to collapse
I am in exactly the same situation as you, same build same gapps, same problem.
To help you out, in recovery (CWM) you can mount /data, then using adb on you computer you can push stuff to the "sdcard" via the command "adb push C:\Some\Local\File.zip /data/media/0/File.zip"
Same problem for me. I installed CM10.1 without gapps and it worked without problems. I also tried with different versions of gapps and give all the mentioned problem.
"Unfortunately, the process com.google.process.gapps has stopped." OK
"Unfortunately, Setup Wizard has stopped." ok (loops forever)
Does anyone have a solution to this problem.
Thx
Help required if possible!
Hello all, joined just to post here.
I'm having the same issues as detailed in the first post.
A lot of the solutions that I've seen recommend going into settings and turning syncing off but the error messages block me from accessing anything. It eventually just seems to crash itself and turn off anyway, which is probably due to being bombarded with error message popups.
Is there a simple way to fix this without doing a full reset back to 4.0.4 or is that my only choice?
If so then I'm in trouble because I followed the link that mrhiab provided but I can't see which firmware there is the one I need (wifi only galaxy tab 10.1 P7510 uk).
Is the cause of this problem that the version of gapps I installed is broken and causes errors as it worked fine without gapps?
If anyone can answer any of those questions then I'd really appreciate it. I've semi broken my girlfriends tab and she's not too happy lol!
UPDATE/SOLVED:
Just thought I'd comment back and say that I've solved the problem.
I simply reflashed the CM by putting the tab into install mode again but didn't add gapps. After rebooting I noticed that it worked okay so I tried to find another release of gapps and tried that...it worked perfectly - no errors no nothing!
Sorry for the initial noob-post!
same problem as you
sir ... i also have the same problem as you ... i've been searching on almost all sites ... still i can't see any issues that can solve my problem.1st was "unfortunately, google.com.pro ..." then next was "unfortunately, setup wizard has stopped." this results everytime i reboot my galaxytab 2 10.1 .. im on JB 4.1.1 .. and i just followed the guide of sir codeworkx. please lend me a solution.
BTW midgard .. how did you flash CM again w/o the gapps ? because when i go to install zip from sd card ... there's nothing in there .. just obb and stuffs said by the thread maker.
I will appreciate suggestions ... Thanks in advance
I hope some suggestions may come up eventually
I found a way on installing cyanogenmod 10 on my Galaxy tab 2 10.1 by not installing gapps at the same time while installing the CM10 .. but eventually, i found out i don't have any google playstore .. and that's when i googled on how to have one. I found a video saying i could have it by just going to there website via my tablet goo-apps .. then download the existing gapss for my JB 4.1.1 .. and then flash it .. but then again ... the error of the Unfortunately, setup wizard stopped came up again ... help
and thanks midgard !!!
Can I get help
midgar777 said:
Hello all, joined just to post here.
I'm having the same issues as detailed in the first post.
A lot of the solutions that I've seen recommend going into settings and turning syncing off but the error messages block me from accessing anything. It eventually just seems to crash itself and turn off anyway, which is probably due to being bombarded with error message popups.
Is there a simple way to fix this without doing a full reset back to 4.0.4 or is that my only choice?
If so then I'm in trouble because I followed the link that mrhiab provided but I can't see which firmware there is the one I need (wifi only galaxy tab 10.1 P7510 uk).
Is the cause of this problem that the version of gapps I installed is broken and causes errors as it worked fine without gapps?
If anyone can answer any of those questions then I'd really appreciate it. I've semi broken my girlfriends tab and she's not too happy lol!
UPDATE/SOLVED:
Just thought I'd comment back and say that I've solved the problem.
I simply reflashed the CM by putting the tab into install mode again but didn't add gapps. After rebooting I noticed that it worked okay so I tried to find another release of gapps and tried that...it worked perfectly - no errors no nothing!
Sorry for the initial noob-post!
Click to expand...
Click to collapse
I still have that "Unfortunately, Setup Wizard has stopped" loop-message, can somebody help me please!
Q&A for [ROM][CM12.0] Official CM12.0 for E970
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][CM12.0] Official CM12.0 for E970. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
wkobaint said:
Could this versions working on e975?
Click to expand...
Click to collapse
Nope, but if you choose you model from device list below, it will works.
So I dirty flashed this over my cm11 and Google play has stopped working. Won't connect at all. Any help is appreciated
Volstagg.The.Valiant said:
So I dirty flashed this over my cm11 and Google play has stopped working. Won't connect at all. Any help is appreciated
Click to expand...
Click to collapse
Did you flash 5.0 gapps?
dandrumheller said:
Did you flash 5.0 gapps?
Click to expand...
Click to collapse
Nope. Could find only old gapps
terribly sorry about the brain fart. whole problem arose because i didnt flash the correct gapps . got the gapps from xda and now its working well. but i am getting a pop up saying that google play services have not been installed on your computer etc...
will this problem go away if i just install the google play services apk?
edit : after flashing the proper gapps, an update from the play store solved everything. Now running smoothly.
since i updated to cm12,go power master has not been able to turn data off when the screen turns off. this was working flawlessly in kitkat. even the go power master widget is not working. thought there might be a problem with root,so flashed supersu 2.40 from recovery. but still it isnt working. any idea what the problem might be?
Volstagg.The.Valiant said:
since i updated to cm12,go power master has not been able to turn data off when the screen turns off. this was working flawlessly in kitkat. even the go power master widget is not working. thought there might be a problem with root,so flashed supersu 2.40 from recovery. but still it isnt working. any idea what the problem might be?
Click to expand...
Click to collapse
Has the app been updated to support LP? At times in the past, access for 3rd party apps to stuff like data connection, which requires root, sometimes changes functionality with version upgrades. Don't know if that's the case in this circumstance, but it's something to look into.
Performance drop
Flashed this rom with fulll wipe. Works well, but sometimes performance *drops* happens. It becomes VERY slow, like CPU speed drops down to 128mhz. I had the same problem on cm 11.
Who knows how to fix it?
Looking great and functions great but I am getting terrible battery life due to "miscellaneous" or "Cellular Standby" according to battery stats.
E970
1/15/2015 nightly (problem persists from previous nightly)
Same problem on stock and Solid_GEEB Kernel
PA 5.0 GAPPS
Lucky to get 12 hours of battery under normal use. Any suggestions?
Thanks,
-Nick
Any ideas how to fix my issue with the BT mac address being changed to "00:00:00:00:5A:AD"? I had the wrong address on CM11 also but it was a different incorrect address and I was able to fix it. I've posted details in my thread for fixing the issue on CM11. http://forum.xda-developers.com/showthread.php?t=2759056#post58131969<br/>
Video call issue
Video call isn't working in both skype and viber. Skype app is crashing as soon as I turn video on. Viber just doesn't turn on the video transmission. Can please somebody report about this issue to CyanogenMod team. I use video calling really often, so this is kind of issue keeps me away from using official CM12 builds. CM11 builds had this issue too and it hasn't got fixed till now.
azatheadfi said:
Video call isn't working in both skype and viber. Skype app is crashing as soon as I turn video on. Viber just doesn't turn on the video transmission. Can please somebody report about this issue to CyanogenMod team. I use video calling really often, so this is kind of issue keeps me away from using official CM12 builds. CM11 builds had this issue too and it hasn't got fixed till now.
Click to expand...
Click to collapse
Post a logcat of it happening.
Sent from my LG-ls990 using XDA Free mobile app
CM Updates
Settings - About phone - CyanogenMod updates indicates no new updates found despite new updates posted at http://download.cyanogenmod.org/?device=e970. I switched from unofficial CM12 to official CM12 several updates ago. I'm using the gapps posted here https://s.basketbuild.com/gapps. Is there a setting I need to revise to begin seeing the CM updates on my phone. It's no big deal since I can go to the CM device list and download directly.
alliance1975 said:
Settings - About phone - CyanogenMod updates indicates no new updates found despite new updates posted at http://download.cyanogenmod.org/?device=e970. I switched from unofficial CM12 to official CM12 several updates ago. I'm using the gapps posted here https://s.basketbuild.com/gapps. Is there a setting I need to revise to begin seeing the CM updates on my phone. It's no big deal since I can go to the CM device list and download directly.
Click to expand...
Click to collapse
The 1/27 update was detected and installed. I do not know what if anything i did to make it work.
Shelnutt2 said:
Post a logcat of it happening.
Sent from my LG-ls990 using XDA Free mobile app
Click to expand...
Click to collapse
Sorry for late answer. I was too busy to post logcats earlier. I hope issues will get fixed.
I installed CM12.0 (1/27 build) but any 5.0 gapps I try fails to flash on the official TWRP 2.8.3.0 for the e970. I've tried bpear, PA, and one other. I can get the ROM to boot, then it gives FC's for every Google App, and the apps are all named by their com. ... name, and say "app not installed" when clicked. I have loaded the zip files over wifi, through adb push, via usb, and through straight download to the device. I've also run them from the external SD and the internal storage.
Is there a different recovery I should be using with this? Will a Nexus 4 recovery work on the e970?
thunder2132 said:
I installed CM12.0 (1/27 build) but any 5.0 gapps I try fails to flash on the official TWRP 2.8.3.0 for the e970. I've tried bpear, PA, and one other. I can get the ROM to boot, then it gives FC's for every Google App, and the apps are all named by their com. ... name, and say "app not installed" when clicked. I have loaded the zip files over wifi, through adb push, via usb, and through straight download to the device. I've also run them from the external SD and the internal storage.
Is there a different recovery I should be using with this? Will a Nexus 4 recovery work on the e970?
Click to expand...
Click to collapse
I'm using TWRP 2.8.4.0 recovery. I initially installed the CM12 unofficial rom along with this gapps:
https://s.basketbuild.com/gapps
and had no problem. I switched to official CM12 when announced by Shelnutt2 and have made no changes to gapps. Perhaps give that gapps a try.
Audio calls problem
Hi,
I recently updated my OS from LG's Official 4.1.2 to CM12. Everything seems to be working fine but for making/receiving calls. I am not able to hear or speak over the microphone and speaker outlet unless or until I use a headphones in which case both work properly. Can anyone please help?
Details on my upgrade:
I had backed up my data and downloaded the CM12 zip files with Gapps and SuperUser into my SD card. Once they were ready, I restarted my mobile in Recovery mode and wiped the user data and installed CM12.zip followed by Gapps followed by SuperUser. Then rebooted my mobile and check everything for the working condition. It was working perfectly except for the fact that when I receive phone calls or when I make a phone call once I attend the call, I would not be able to speak to the person or hear the person in normal mode nor in speaker mode. The only way it works is if I use my headphones.
I had installed CM12 01/26/2015 version. And have tried later versions until 01/30 but I do not find that to be fixing. It would be of great help if anyone could help me.
Thanks,
Arun
arun.rama said:
Hi,
I recently updated my OS from LG's Official 4.1.2 to CM12. Everything seems to be working fine but for making/receiving calls. I am not able to hear or speak over the microphone and speaker outlet unless or until I use a headphones in which case both work properly. Can anyone please help?
Details on my upgrade:
I had backed up my data and downloaded the CM12 zip files with Gapps and SuperUser into my SD card. Once they were ready, I restarted my mobile in Recovery mode and wiped the user data and installed CM12.zip followed by Gapps followed by SuperUser. Then rebooted my mobile and check everything for the working condition. It was working perfectly except for the fact that when I receive phone calls or when I make a phone call once I attend the call, I would not be able to speak to the person or hear the person in normal mode nor in speaker mode. The only way it works is if I use my headphones.
I had installed CM12 01/26/2015 version. And have tried later versions until 01/30 but I do not find that to be fixing. It would be of great help if anyone could help me.
Thanks,
Arun
Click to expand...
Click to collapse
Make a clean flash (in TWRP wipe system, data, cache, dalvik cache and after install cm12 and gapps) and install 84/27 hybrid modem during same recovery session, after reboot to system. Modem issues with e970 are really whimsical. I hope this will help.
P.S. Find modem image in this thread:
http://forum.xda-developers.com/showthread.php?t=2584981
azatheadfi said:
Make a clean flash (in TWRP wipe system, data, cache, dalvik cache and after install cm12 and gapps) and install 84/27 hybrid modem during same recovery session, after reboot to system. Modem issues with e970 are really whimsical. I hope this will help.
P.S. Find modem image in this thread:
http://forum.xda-developers.com/showthread.php?t=2584981
Click to expand...
Click to collapse
Hey, I just tried the steps you had mentioned and it worked like a gem. Thanks a lot for your solution. I really appreciate your help. Have a great weekend.
Arun
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.