Hi all...
Please could someone help me?
I am running the latest UK Sim Free ICS Stock ROM - and yesterday I updated the kernel as I wasn't best pleased with battery life.
Initially, I flashed Siyah 3.1.1 via Odin - and after initial boot up, "android upgrading" etc... I rebooted phone, went into recovery, and loaded the "Battery" profile.
The only other adjustment I made was turning off Auto-root and changed USB charging to 650mA in ExTweaks so that it charges via USB at the same speed as AC.
I made no other changes.
Then, the Siyah 3.1.2 Kernel was released, just a couple of hours after. So, I downloaded the CWM zip version this time, and also the Kernel cleaning script that is available on here (more for cleaning up the old stock kernel files than the Siyah)...
I rebooted into CWM and did the Update from zip - ran the Kernel cleaning script first, then flashed Siyah 3.1.2. I rebooted - let it do its "Android Upgrading" stuff and so on, then rebooted, loaded "Battery" profile, and made the same changes as originally - nothing more.
However, now, whenever phone reboots or powers on - I briefly get the "Android Upgrading" screen up for a few seconds. I didnt have this with the 3.1.1 - and am wondering how I can resolve this? I have definitely turned off Auto-Root, so it cant be this.
Another question, I recall reading, but cant find the post anywhere, that to disable the Siyah boot-animation that comes on just before the default Galaxy S2 one (in the same way a Carriers logo's does) - you need to create a file somewhere called .nobootanimation or something?
Does anybody know how to disable this so it just starts up like a stock S2 would? I love the kernel, but I personally prefer my phone to "appear" and feel as stock as possible.
Any help much appreciated - Thanks!
EDIT: I managed to find the post regarding the boot logo and have sorted that - but still found nothing on the Android Upgrading issue - Ive just reset ExTweaks profile through recovery options, no joy...
shadow2981 said:
Hi all...
Please could someone help me?
I am running the latest UK Sim Free ICS Stock ROM - and yesterday I updated the kernel as I wasn't best pleased with battery life.
Initially, I flashed Siyah 3.1.1 via Odin - and after initial boot up, "android upgrading" etc... I rebooted phone, went into recovery, and loaded the "Battery" profile.
The only other adjustment I made was turning off Auto-root and changed USB charging to 650mA in ExTweaks so that it charges via USB at the same speed as AC.
I made no other changes.
Then, the Siyah 3.1.2 Kernel was released, just a couple of hours after. So, I downloaded the CWM zip version this time, and also the Kernel cleaning script that is available on here (more for cleaning up the old stock kernel files than the Siyah)...
I rebooted into CWM and did the Update from zip - ran the Kernel cleaning script first, then flashed Siyah 3.1.2. I rebooted - let it do its "Android Upgrading" stuff and so on, then rebooted, loaded "Battery" profile, and made the same changes as originally - nothing more.
However, now, whenever phone reboots or powers on - I briefly get the "Android Upgrading" screen up for a few seconds. I didnt have this with the 3.1.1 - and am wondering how I can resolve this? I have definitely turned off Auto-Root, so it cant be this.
Another question, I recall reading, but cant find the post anywhere, that to disable the Siyah boot-animation that comes on just before the default Galaxy S2 one (in the same way a Carriers logo's does) - you need to create a file somewhere called .nobootanimation or something?
Does anybody know how to disable this so it just starts up like a stock S2 would? I love the kernel, but I personally prefer my phone to "appear" and feel as stock as possible.
Any help much appreciated - Thanks!
EDIT: I managed to find the post regarding the boot logo and have sorted that - but still found nothing on the Android Upgrading issue - Ive just reset ExTweaks profile through recovery options, no joy...
Click to expand...
Click to collapse
You would be better asking this question on the SiyahKernel thread
Thanks, I tried there first, and it said I couldnt post as i had less than 10 posts... :/
If this helps:
I re-flashed the 3.1.2 Kernel, this time via Odin (so no Kernel cleaning script run this time prior to flash), but I have the same problem.
I cleared dalvik cache afterwards, and as expected at first boot after clearing I get the:
Android Upgrading:
Optimising Applications
prompt.
Rebooted after this - but still get the:
Android Upgrading:
Starting Apps
at every bootup...
I tried "Fix Permissions" (even though I know this is not what it is for, on the off-chance)... but made no difference.
I reboot phone a lot - and whilst this doesnt effect the functionality of the phone, it does get quite irritating
My phone keeps rebooting randomly (sometimes repeatedly) even after doing a full wipe and installing CM 10.1.2 and the latest gapps. I was told on the cyanogen mod forum that I could find the latest boot loader and radio here, and it might fix my problem. However, I have no idea where to get them on here, and searching didn't give me any obvious result.
Thanks!
Bootloader is inconsequential once you have booted. And the modem wouldn't cause reboots either.
Tis most likely a kernel issue.
studacris said:
Bootloader is inconsequential once you have booted. And the modem wouldn't cause reboots either.
Tis most likely a kernel issue.
Click to expand...
Click to collapse
How do I fix the kernel issue? Is the kernel in the CM 10.1.2 ROM? Is there a better one I should install afterward? Could this be from an app I installed recently? It's strange because CM 10.1.2 was fine for a while, but suddenly it is almost unusable.
Kernel is contained in the rom zip, yes.
Separate kernels are in the development sections... I'm running uber.
It could be an app running crazy with your ram and causing a kernel panic/reboot
Hi everyone,
I recently have a problem on my (old) TF201. The touch screen works fine, except the right and left edge. When I turn on Developer options and enable 'Show touches' i clearly see that when I move my finger to the right or left it sort of 'snaps' to the edge. So there a small stroke (left and right) that doesn't respond to input. Very frustrating when trying to point out something on the very right or left of the screen
I've opened my TF201 to see it wasn't a loose cable; but everything is in place. No difference.
Anyone an idea?
I did replace the factory ROM with a custom recovery (TWRP) and used
http://forum.xda-developers.com/devdb/project/dl/?id=6853 to install once a CROMBi-kk ROM for TF300t. Maybe this generates this screen edge fault? If so; how do I revert back to TF201? My TF201 thinks it's a TF300 now.
Thanks for reading this problem.
Hi,
Same problem here. It looks like it started after installing KatKiss. I was previously using Cyanogenmod without any problem. I thought that this could be caused by the new bootloader, but the problem persisted even after reverting back to the stock BL and ROM.
I even tried to replace the touch screen, no luck.
Have you been able to fix the issue?
In case somebody else with the same problem finds this post, here is how I fixed the problem
http://forum.xda-developers.com/tran...2#post62361792
Unfortunately this apparently doesn't work for everybody...
[email protected] said:
In case somebody else with the same problem finds this post, here is how I fixed the problem
http://forum.xda-developers.com/tran...2#post62361792
Unfortunately this apparently doesn't work for everybody...
Click to expand...
Click to collapse
I tried ur method but may I know which Kernel did u reflash to? U mentioned default kernel so u mean grimlock lite 5.1?
altya said:
I tried ur method but may I know which Kernel did u reflash to? U mentioned default kernel so u mean grimlock lite 5.1?
Click to expand...
Click to collapse
I am not sure exactly which kernel it was. But as I explained, I first installed Androwook AiryBean 2.31.
Then I used the "Androwook airyBean 2.31 Kernel Installer" to reinstall the default Androwook kernel, meaning the default kernel shipped with the kernel installer. That probably not Grimlock lite 5.1... See this page to download the kernel installer (and the Androwook ROM): http://forum.xda-developers.com/showthread.php?t=2407248
Maybe I should clarify a bit:
1. I completely wiped the tablet and did a clean installation of Androwook, following the instructions to the letter, including the 30 to 60 minutes wait "for the system to cache itself", followed by a restart. At that point, I still had the issue with the screen edges.
2. I then re-installed the kernel, again following the instructions to the letter. After the final reboot, the problem was gone.
3. And I finally re-installed KatKiss (v26). Since then I enjoyed my TF201 without any issues.
The reason why I tried to re-install the default kernel is because of the following quote:
HairyBean 2.31 Kernel Installer will allow you to try different kernel options without re-flashing the rom. It will also clean up bits left behind by the previous kernel before installing a new one
Click to expand...
Click to collapse
I am not sure that this is what solved the problem, but this is definitely a software issue. And since wiping the tablet multiple time, downgrading to stock and trying various ROMs didn't do anything, this was my last hope. It worked for me, and I hope that it will work for you too...
I can confirm that this is a software issue. After installing the reverse axis kernel of Hairy bean, the unresponsive areas in the touch screen was also reversed! I tried the solution provided above, unfortunately without success. Is it right to assume that everyone got this issue after installing Katkiss version after V26?
jan3586 said:
Is it right to assume that everyone got this issue after installing Katkiss version after V26?
Click to expand...
Click to collapse
I don't think so. I got the problem with an earlier version of KatKiss, and I believe (but may be mistaken) from the research I did in the past that a few people ran into this problem with other custom ROMs.
Thanks, are you using ver 2 of the kernel installer?
Sent from my Nexus 4 using XDA Free mobile app
jan3586 said:
Thanks, are you using ver 2 of the kernel installer?
Click to expand...
Click to collapse
Yes, it was version 2 that I used.
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.