Database Users

Marshmallow ROMs freeze and crash = Hardware Problem?

Hello everyone!
I have been experiencing a strange issue with almost all the Marshmallow ROMs currently in the development section. The Phone boots, Setup Wizard runs, and in between, the screen freezes/hangs and after 5-10 seconds the phone reboots. Again the setup wizard runs and even if i'm able to complete the wizard, the phone frequently hangs and then reboots.
I had been running Paranoid Android 5.1 ROM before flashing the Marshmallow ROM and this strange issue suddenly started. I have tried to flash stock rom and then flash twrp, then flash the ROM, even wiped everything several times. Still the same issue persists. This is really getting annoying as i have tried 3-4 different ROMs and 2 GApps and still the screen freezes and then phone reboots.
And this happens only on Marshmallow ROMs as i again have currently installed Chroma 5.1.1 ROM and its running smoothly. I am beginning to think of it to be a hardware issue. Can anyone help me solve this?

imrock0 said:
Hello everyone!
I have been experiencing a strange issue with almost all the Marshmallow ROMs currently in the development section. The Phone boots, Setup Wizard runs, and in between, the screen freezes/hangs and after 5-10 seconds the phone reboots. Again the setup wizard runs and even if i'm able to complete the wizard, the phone frequently hangs and then reboots.
I had been running Paranoid Android 5.1 ROM before flashing the Marshmallow ROM and this strange issue suddenly started. I have tried to flash stock rom and then flash twrp, then flash the ROM, even wiped everything several times. Still the same issue persists. This is really getting annoying as i have tried 3-4 different ROMs and 2 GApps and still the screen freezes and then phone reboots.
And this happens only on Marshmallow ROMs as i again have currently installed Chroma 5.1.1 ROM and its running smoothly. I am beginning to think of it to be a hardware issue. Can anyone help me solve this?
Click to expand...
Click to collapse
Flash Frank ROM, Flash Tuxi Gapps from Frank's OP, no one is having any issues now. Also don't forget to do a factory reset if you can even the Internal data.

sidnoit22 said:
Flash Frank ROM, Flash Tuxi Gapps from Frank's OP, no one is having any issues now. Also don't forget to do a factory reset if you can even the Internal data.
Click to expand...
Click to collapse
I have done factory reset several times. Even flashed stock via fastboot multiple times. Done the exact same steps you mentioned. Its not only with Frank ROM actually, i tried another Marshmallow ROM and the same thing happened again.
How is it that Lollipop ROMs are running smooth and Marshmallow ROMs are crashing?

imrock0 said:
I have done factory reset several times. Even flashed stock via fastboot multiple times. Done the exact same steps you mentioned. Its not only with Frank ROM actually, i tried another Marshmallow ROM and the same thing happened again.
How is it that Lollipop ROMs are running smooth and Marshmallow ROMs are crashing?
Click to expand...
Click to collapse
seems like it's Gapps/ ROM problem (with setup wizard)
this my only suggestions:
1. try to flash Frank's M without Gapps > reboot normaly
if this worked, then it's related to Gapps issue...
if it still remains, then
2. Flash ROM, Gapps, wipe, etc.
after that back to home of TWRP > Mount > Mount system > back > Advanced > File manager > go to /system/priv-app
search for folder name related to Setup wizard/ Google setup wizard (NOT GooglePartnerSetup) > delete it > reboot
3. fingercrossed it will bring you to home screen without any problem...
good luck then :fingers-crossed:

yayakuya said:
seems like it's Gapps/ ROM problem (with setup wizard)
this my only suggestions:
1. try to flash Frank's M without Gapps > reboot normaly
if this worked, then it's related to Gapps issue...
if it still remains, then
2. Flash ROM, Gapps, wipe, etc.
after that back to home of TWRP > Mount > Mount system > back > Advanced > File manager > go to /system/priv-app
search for folder name related to Setup wizard/ Google setup wizard (NOT GooglePartnerSetup) > delete it > reboot
3. fingercrossed it will bring you to home screen without any problem...
good luck then :fingers-crossed:
Click to expand...
Click to collapse
Thanks i'll try this out when i get back home. Although i did try flashing just the ROM to see if GApps were causing the issue. Without GApps, the phone booted to the homescreen, but then after 5-10 mins would reboot itself. I don't know may be it has got something to do with temperature? Because i've noticed that the phone becomes very hot when it first boots up on a new ROM(i know its normal for it to get hot). But when i used the phone on a Marshmallow ROM when the phone was NOT hot, it went on pretty well for 20-30 mins and then again rebooted.

yayakuya said:
seems like it's Gapps/ ROM problem (with setup wizard)
this my only suggestions:
1. try to flash Frank's M without Gapps > reboot normaly
if this worked, then it's related to Gapps issue...
if it still remains, then
2. Flash ROM, Gapps, wipe, etc.
after that back to home of TWRP > Mount > Mount system > back > Advanced > File manager > go to /system/priv-app
search for folder name related to Setup wizard/ Google setup wizard (NOT GooglePartnerSetup) > delete it > reboot
3. fingercrossed it will bring you to home screen without any problem...
good luck then :fingers-crossed:
Click to expand...
Click to collapse
Here's another update. I tried the new Chroma Marshmallow ROM and it too had the same issue. The phone hangs/freezes randomly and then reboots. After trying so many ROMs, i think the issue is with hardware itself. None other has reported this issue, nor could i find it anywhere else. I guess i can say that my(and only my) nexus 4 is not compatible with Marshmallow officially and unofficially.

I don't know what kernel Frank's uses but you could always try to flash an alternate kernel. I haven't taken the jump to Marshmallow yet, but it seems TaUrUs and hellsCore support M (I currently use hellsCore with stock L).

bjb2 said:
I don't know what kernel Frank's uses but you could always try to flash an alternate kernel. I haven't taken the jump to Marshmallow yet, but it seems TaUrUs and hellsCore support M (I currently use hellsCore with stock L).
Click to expand...
Click to collapse
I'll try another kernel and ping back.

Probably lacked boot the system before you install GApps.

imrock0 said:
I'll try another kernel and ping back.
Click to expand...
Click to collapse
The FC of Setup Wizard is discussed in the ROM thread of Chroma.
You can try this because it is advised by the Dev of Chroma and supported by many others and I have succeeded with this.
Flash stock L and boot up.
Boot into TWRP (make sure you have the latest) and factory reset.
Flash Chroma 1/11/2015 and Bank's Gapps without boot/reboot in between and no wipe afterwards.
Reboot.
---------- Post added at 07:03 PM ---------- Previous post was at 07:00 PM ----------
webg3brasil said:
Probably lacked boot the system before you install GApps.
Click to expand...
Click to collapse
At least for Chroma, that is a wrong approach. No boot between ROM and Gapps flash.

Make sure you have permissions granted to all of the apps. I had similar issues, and had to do with Location and apps making calls to GPS. Would cause a reboot, and not just a force close. Try amending the Location settings as well. All else fails, capture a logcat.

Everyone thanks for your time!
I found the solution. bjb2's suggestion did the trick. I flashed TaUrUs-Mallow Kernel after Frank Marshmallow ROM and everything seems fine now. Have been running Marshmallow since a day without any issues. Still it's curious why the stock kernel gave such errors.
Thanks everyone again for your suggestions and help

All apps stop constantly and in random way -SM-N910F

Hello.
At first, I am new in the forum, so hi to everybody and thanks for the job in this site.
I have a very big problem with Note 4 ( I can't use it right now). Since I rooted the phone and changed the rom (to Cyanogenmod 12) all apps stop constantly and in random way. I have tried everything (I think so), return to the stock rom (android 5.0.1), make wipes (cache, data...) and reinstall the rom from Samsung switch.
I don't know what to do.
More info: All apps stop but the gapps stop with more frequency. I sent the device to the technical service but they take it back because I have modified the software (knox 0x1).
Sorry for my english. I am from Spain.
Thanks.

Third party apps or system apps?
Did you install any battery saving or ram booster apps?

GrippingSphere said:
Third party apps or system apps?
Did you install any battery saving or ram booster apps?
Click to expand...
Click to collapse
All of them
No, I don't believe in those apps. The only thing that I did for imrpoving the performance was to intall CM12 (It works fine at first)
I thought that CM12 doesn't work well with the Fast Charging... Could it be?
Thanks.

It seems like you might've flashed a gApps package for an earlier version of Android than what Cm12 is (5.1.1).
Try a full device wipe, reflashing CM12 & a gapps for 5.1.1

Jishy420 said:
It seems like you might've flashed a gApps package for an earlier version of Android than what Cm12 is (5.1.1).
Try a full device wipe, reflashing CM12 & a gapps for 5.1.1
Click to expand...
Click to collapse
I tried that and It didn't solve the problem. I also reflashed the stock rom (with Odin). Without effect, the problem was not resolved...
Thanks for your help.

CM reboots when making or receiving calls :confused:

Hi guys, I had to give up using CM Roms since the phone reboots every time I try making a call or receive one, I understand there is some king of bug with the dialer framework included in the GAPPS package and that installing the Google Dialer from the play store should solve it but in my case i hasn't. This is what I've tried to no avail:
- Intalled Google DIaler from PlayStore/APK and set it default with all the permissions enabled.
- Installed Google Dialer apk as system app and set it default with all the permissions enabled.
- Installed the full GAPPS package.
- Removed the stock dialer and did all things above.
Hope someone can help me out here,
Thanks.

This happens when you have multiple phone dialer apps enabled. To use any other dialer than the included (when you flash Gapps Tiny or Micro which is recommended since the bigger packs replaces the CM app).
If you don't like the CM one, you should still flash a smaller Gapps and then disable CM dialer and download the one you want. If you already flashed a bigger Gapps, you should format system, cache and dalvik/arts partition and then reflash CM and then the smaller Gapps.

Should be enough to go settings, apps, click the gear weel (next to 3 dot menu), choose standard apps from this menu and determine your dailer as standard app..
This is a classical issue..
Sent from my OnePlus2 using XDA Labs

Sam Nakamura said:
Should be enough to go settings, apps, click the gear weel (next to 3 dot menu), choose standard apps from this menu and determine your dailer as standard app..
This is a classical issue..
Sent from my OnePlus2 using XDA Labs
Click to expand...
Click to collapse
Hi Sam, that's what I mean when I've set it as default.

pitrus- said:
This happens when you have multiple phone dialer apps enabled. To use any other dialer than the included (when you flash Gapps Tiny or Micro which is recommended since the bigger packs replaces the CM app).
If you don't like the CM one, you should still flash a smaller Gapps and then disable CM dialer and download the one you want. If you already flashed a bigger Gapps, you should format system, cache and dalvik/arts partition and then reflash CM and then the smaller Gapps.
Click to expand...
Click to collapse
Hey pitrus, this issue actually started while only having CM dialer installed since I mainly flash pico gapps.
Will try it again since its been like a month since I gave up on it. Let you know later.

J3RI3L said:
Hi Sam, that's what I mean when I've set it as default.
Click to expand...
Click to collapse
Well, okay.. Thanks for clarification :good:
Maybe you'd like to give Banks a shot, I think it's worth to try...
https://download.dirtyunicorns.com/gapps/Banks/
I never had this specific problem, only when it wasn't set to be default but a also only use one dailer.. The one that is default on cm based roms..
Sent from my OnePlus2 using XDA Labs

Guys I've had no luck, tried with a clean install of CM14 and still facing the same problem. Just today did a CM14.1 install and it is still present for me.
I guess that I could flash just CM and not gapps but I rely on Google services for a lot of stuff. Will keep trying though.

I'm having the exact same problem, random reboots during calls only, sometimes I don't even have time to answer. I'm running CM13 and only have one phone app, also set as default. When running stock and Cyanogen all was fine, this only started after flashing CM13.
Developemt for Cyanogen stopped that's why I switched, maybe coming from another rom is causing this? I did a full wipe when flashing and have updated to several nightlies and the problem remains. Maybe I'll try another rom and test it for a while.

Installed Dirty Unicorns a few days ago and the problem seemed to have been fixed, but yesterday it started acting out again. Is there a way to check if this problem is hardware related?
I'm now doing a factory reset and installing Oxigen hoping that'll fix this once and for all.

It's a problem related to Gapps
rtorresz said:
Installed Dirty Unicorns a few days ago and the problem seemed to have been fixed, but yesterday it started acting out again. Is there a way to check if this problem is hardware related?
I'm now doing a factory reset and installing Oxigen hoping that'll fix this once and for all.
Click to expand...
Click to collapse
It is not a hardware problem, I don't have this issue when running Oxygen OS, it only happens to me when running any AOSP based rom with Gapps installed.
Flash Oxygen from here http://downloads.oneplus.net/devices/oneplus-2/ and it will fix it, it's not the same as running CM though.

J3RI3L said:
It is not a hardware problem, I don't have this issue when running Oxygen OS, it only happens to me when running any AOSP based rom with Gapps installed.
Flash Oxygen from here http://downloads.oneplus.net/devices/oneplus-2/ and it will fix it, it's not the same as running CM though.
Click to expand...
Click to collapse
Sounds like you flashed the full version of Gapps instead of the recommended Nano or Micro which does not replace the dialer app with Googles own, try the smaller Gapps and you should be ok.

pitrus- said:
Sounds like you flashed the full version of Gapps instead of the recommended Nano or Micro which does not replace the dialer app with Googles own, try the smaller Gapps and you should be ok.
Click to expand...
Click to collapse
I've installed them all with the same result, last time I was using Pico Gapps with Seraph's CM14 and it happened eandomly, sometimes I could make and receive calls normally but a most of the time it would reboot as soon as the phone started ringing.
Currently I've tried a lot of solutions so I'm not really sure of what's wrong.

J3RI3L said:
It is not a hardware problem, I don't have this issue when running Oxygen OS, it only happens to me when running any AOSP based rom with Gapps installed.
Flash Oxygen from here http://downloads.oneplus.net/devices/oneplus-2/ and it will fix it, it's not the same as running CM though.
Click to expand...
Click to collapse
I flashed the latest OOS and now things are only a little bit better, instead of reboots I get dropped calls and a "No available network" message. This seems to happen only when I'm on a 3G or 4G network, if I change to a 2G network I can make calls without problems. This is driving me crazy, I've tried almost everything and I can't see what I'm missing.

rtorresz said:
I flashed the latest OOS and now things are only a little bit better, instead of reboots I get dropped calls and a "No available network" message. This seems to happen only when I'm on a 3G or 4G network, if I change to a 2G network I can make calls without problems. This is driving me crazy, I've tried almost everything and I can't see what I'm missing.
Click to expand...
Click to collapse
Its happening to me as well just as you describe it. It is very weird. In thinking of flashing the stock OOS 2.2.0 just to check whether it makes any diference.

Yesterday I restored my phone back to stock, but the problen remains.
This definitely has something to do with mobile data. If I disconnect mobile data I can make calls without any problem, when I'm connected to a wifi network too (I'm guessing because the phone has no need to use mobile data).
Some suggest that this might be related to VoLTE and operators not supporting it, but I can't find anyway to see if this is even exists or if its activated in OOS.
Later today I'll try Hydrogen and see what happens.
UPDATE: Flashing Hyrogen didn't solve the issue, calls keep dropping when mobile data is activated on LTE network.
UPDATE 2: Going back to OOS 2.2.1 didn't solve the problem either.

Kinda solved now
rtorresz said:
Yesterday I restored my phone back to stock, but the problen remains.
UPDATE: Flashing Hyrogen didn't solve the issue, calls keep dropping when mobile data is activated on LTE network.
UPDATE 2: Going back to OOS 2.2.1 didn't solve the problem either.
Click to expand...
Click to collapse
It seems I have solved my problem with the reboots and I think might help with your droped calls as well.
Firstly I flashed this OOS 3 firmware https://www.androidfilehost.com/?fid=24591020540821656, it comes with a hybrid TWRP, after that flashed the official CM14.1 and pico Open Gapps.
I think the firmware file did the trick or maybe it was the recovery since I haven't had a reboot in the past 2 days when receiving calls or making them.
Hope it helps

It's been a few days since I tried the last solution and so far my problem seems to be solved.
What worked for me was flashing the latest modem from H2OS 2.5 which also is supposed to enable VoLTE, but I can't confirm this since my carrier does not support VoLTE yet. To do this I first flashed CM 14.1 and then the modem, it worked fine since the first boot. Since my battery life wasn't the best in Nougat I went back to CM13 and the phone is still working fine.

OnePlus 5 Slowy, Lags..

Hi, I'm here to ask for your help because I don't know what to do.
Since the update to xXx 9.6 no limits my Oneplus 5 runs in slow motion, the applications take a lot of time to open it is unusable. Even the startup animation is slow.
I've already reformatted everything, flash with unbrick tool but it's the same.
I have the impression that only when I format in F2FS it works normally but I can't find a compatible Rom. Thank for your help.

Have you tried another aosp rom or just the stock rom some tweaks of the xxx might be causing some issues

Thesuprememonkey said:
Have you tried another aosp rom or just the stock rom some tweaks of the xxx might be causing some issues
Click to expand...
Click to collapse
I have try xXx, Stock Rom and Lineage OS

mrsachou said:
I have try xXx, Stock Rom and Lineage OS
Click to expand...
Click to collapse
That's weird do you have any heavy syncing apps ?? When did you start noticing the problem ? immediately after 9.6xxx update or after installing a certain app ? Have you tried changing the kernels ? Try decrypting and then Omni since it's a stable 8.1 rom

Thesuprememonkey said:
That's weird do you have any heavy syncing apps ?? When did you start noticing the problem ? immediately after 9.6xxx update or after installing a certain app ? Have you tried changing the kernels ? Try decrypting and then Omni since it's a stable 8.1 rom
Click to expand...
Click to collapse
I start notice when i install the new Snapchat.
I'm gonna try thanks

You formatted the data (which wipes everything on your device ) or just wiped the partitions? If you completely formatted and are experiencing the exact same issue on LOS and xXx there are several possibilities -- 1) You have a hardware issue; 2) You are using corrupt or mismatched firmware; 3) A third party app is causing the issue. The last one is very easy to check--just boot your OP5 into Safe Mode and see if the issue persists. If you encountered the issue on stock OOS and did a clean install after formatting your data then it shouldn't be a firmware issue.
It's very important that you completely format all the data on your phone--not wipe the partitions or format them individually because you need a fresh start in case it's just an issue with corrupted data. My guess based on everything you wrote is that you have a hardware problem and need to have your phone serviced.

(Please reply)Facing a strange problem while flashing miui Pro

Last few days I tried to use custom ROM. Volte doesn't work. I've given up on that issue now. Now problem is Miui pro.
After flashing it keeps showing boot logo ( I waited for more than 30 minutes) but the older version (7... Something) flashes without any problem.
How long should I wait to complete it's booting process( more than an hour??!!!!!)
P.s- device encryption is enabled [ but I don't think it's causing the problem cuz older version is doing fine]

http://miuiid.blogspot.in/p/rom.html?m=1
Download this and flash like normal rom.
First clear data, dv-cache, system,
Then flash this along with magisk
After flash don't clear dv-cache, not even after flashing magisk and dont change anythink in the system partition untill first boot u can also flash the magisk modules straight ahead.
This is miui id best, u get paid themes free, also volte working and it does have split screen.
Note:- don't forget to flash magisk, don't clear cache after flashing the rom and i mean anytime don't do it it will take a lot of time then.
First boot will take 15 min, dont wait for it once it gets past the boot logo and enters the bootanimation wait for 2 min then again do force reboot by long pressing the power button, do it one more time this time wait for 5 min if it opens then good or again reboot. This time it will happen.
The rom is stable and totally worth the trouble.
This process is just to reduce the first booting time.
Thanks ?

Also check this post for more information.
Link:- https://forum.xda-developers.com/xi...t/arvanasoft-miui-9-7-10-20-redmi-3s-t3694036
Thanks.

Im running Miui 9.2 global stable 9.2.2.0
Can i do dirty install? I dont wanna lose apps data

Im using stock miui global stable 9.2.2. Android 6.0
If i wanna install miui id, do i need to wipe all , as in format my handset. Or is it ok to just wipe system, cache dv? I dont wanna lose my apps data

@Trovies hi,
Just do titanium or swiftbackup search the apk in google, and u can do dirty flash but i will not recommend it.
Note :- download the premium version of the swiftbackup from the internet.
Thanks

Flash lazyflasher.zip

Sagar_zac said:
http://miuiid.blogspot.in/p/rom.html?m=1
Download this and flash like normal rom.
First clear data, dv-cache, system,
Then flash this along with magisk
After flash don't clear dv-cache, not even after flashing magisk and dont change anythink in the system partition untill first boot u can also flash the magisk modules straight ahead.
This is miui id best, u get paid themes free, also volte working and it does have split screen.
Note:- don't forget to flash magisk, don't clear cache after flashing the rom and i mean anytime don't do it it will take a lot of time then.
First boot will take 15 min, dont wait for it once it gets past the boot logo and enters the bootanimation wait for 2 min then again do force reboot by long pressing the power button, do it one more time this time wait for 5 min if it opens then good or again reboot. This time it will happen.
The rom is stable and totally worth the trouble.
This process is just to reduce the first booting time.
Thanks
Click to expand...
Click to collapse
very well explained. As per habit I was clearing both dv cache and cache and due to this rom was taking too much time to boot. But after reading your post I have made clear pretty much everything. This is the best MIUI rom I have ever used. Performance, battery life, smoothness everything is spot on. I just wish it would had double tap to wake feature and recent apps menu would had icon mode option. Audio through earphones is also low. other than that its fantastic rom.
https://forum.xda-developers.com/xi...t/arvanasoft-miui-9-7-10-20-redmi-3s-t3694036

Vinayakn73 said:
very well explained. As per habit I was clearing both dv cache and cache and due to this rom was taking too much time to boot. But after reading your post I have made clear pretty much everything. This is the best MIUI rom I have ever used. Performance, battery life, smoothness everything is spot on. I just wish it would had double tap to wake feature and recent apps menu would had icon mode option. Audio through earphones is also low. other than that its fantastic rom.
https://forum.xda-developers.com/xi...t/arvanasoft-miui-9-7-10-20-redmi-3s-t3694036
Click to expand...
Click to collapse
Well u don't get everything but the things you mentioned i don't use it. So... Good for me right. ?For the audio problem use Dolby from the magisk repo the lenovo A7000 one the others don't work. Just flash the settings zip after flashing the rom and don't clear cache

Sagar_zac said:
Well u don't get everything but the things you mentioned i don't use it. So... Good for me right. For the audio problem use Dolby from the magisk repo the lenovo A7000 one the others don't work. Just flash the settings zip after flashing the rom and don't clear cache
Click to expand...
Click to collapse
well I'm using viper4android but with it audio quality increased but volume decreased further, I think I can live up with it. After flashing settings zip I did everything as you mentioned (did not clear dvk cache or cache) but now rom is stuck on mi logo (almost 20 to 25 minutes) can I dirty flash rom again???? Or do I need to do clean install??

Vinayakn73 said:
well I'm using viper4android but with it audio quality increased but volume decreased further, I think I can live up with it. After flashing settings zip I did everything as you mentioned (did not clear dvk cache or cache) but now rom is stuck on mi logo (almost 20 to 25 minutes) can I dirty flash rom again???? Or do I need to do clean install??
Click to expand...
Click to collapse
Just do a clean flash, rom + settings zip, together like do a batch. Then no clear cache boot and do the process

Sagar_zac said:
Just do a clean flash, rom + settings zip, together like do a batch. Then no clear cache boot and do the process
Click to expand...
Click to collapse
yup I'm not noob and doing exactly as you are saying but still I'm struggling with this rom
1st attempt wipe dalvik, system, data cache - flashed rom - flashed settings zip - flashed magisk - tried to flash magisk modules (failed) - reboot without any wipe - rom didn't boot
2nd attempt - clean installed with only rom and settings zip - booted normally - went to bootloader again installed magisk - reboot system - went in bootloader again - flashed app systemizer module- rebooted successfully - went to magisk manager and added module youtube advanced - reboot stuck on mi logo
3rd attempt - reinstalled clean as described in 2nd attempt till the setup of app sytemizer on reboot - went to app systemizer module and ticked gps app- module asked to reboot boooooom stuck on mi logo
Everything I wrote above is my common practice with every miui rom but I don't know why It is not working with this rom. anyways thanks for your help I am moving to global stable as I can't live without these modules. n sorry for bad english

Vinayakn73 said:
yup I'm not noob and doing exactly as you are saying but still I'm struggling with this rom
1st attempt wipe dalvik, system, data cache - flashed rom - flashed settings zip - flashed magisk - tried to flash magisk modules (failed) - reboot without any wipe - rom didn't boot
2nd attempt - clean installed with only rom and settings zip - booted normally - went to bootloader again installed magisk - reboot system - went in bootloader again - flashed app systemizer module- rebooted successfully - went to magisk manager and added module youtube advanced - reboot stuck on mi logo
3rd attempt - reinstalled clean as described in 2nd attempt till the setup of app sytemizer on reboot - went to app systemizer module and ticked gps app- module asked to reboot boooooom stuck on mi logo
Everything I wrote above is my common practice with every miui rom but I don't know why It is not working with this rom. anyways thanks for your help I am moving to global stable as I can't live without these modules. n sorry for bad english
Click to expand...
Click to collapse
Ya i know modules can be a pain in the ass only one suggestion when ever after flashing a module if its stuck in the bootloop then just use magisk Uninstaller then again install Magisk or use magisk for recovery to remove the particular module which is causing boot loop also use root youtube valence and use universal installer it will not cause bootloop. Also use minimal module only what you need. Ok then. Also do as u discreet i am fine in this rom. And its great. ?

See my modules

I too use YouTube vanced.
Man u got to find solutions not give up and change only after a few attempts. U know how many times i got bootloop because of this rom and it's compatibility issues with the modules. After many attempts i got it. Now its the best custom miui rom ever also the dev is constant and hops to bring miui 10. Also if u have used this rom only for a few hours u can realize the difference.

Sagar_zac said:
I too use YouTube vanced.
Man u got to find solutions not give up and change only after a few attempts. U know how many times i got bootloop because of this rom and it's compatibility issues with the modules. After many attempts i got it. Now its the best custom miui rom ever also the dev is constant and hops to bring miui 10. Also if u have used this rom only for a few hours u can realize the difference.
Click to expand...
Click to collapse
yup there is no doubt this is best custom miui rom out there. But this bootloop and boot time driving me nuts. I wonder why all this problems are popping up though the rom is based on official firmware and I've never faced such problem with official roms. I will give it a try again after two days. I just hope that time it will go smooth.