Hello everyone!
Pls help me on this one...
I have:
- unlocked Boot loader
- installed Twrp 3.2.1 vendor patch
- installed Magisk 16.0
- flashed DotOs 2.4 treble ROM
- installed Franco kernel (fk6)
on my Redmi Note 4 (mido).
The problem is:
- whenever I reboot my device a message appears from DotOs System which says: There is an internal problem in your device. Please contact your manufacturer.
- whenever I play Pubg mobile, my phone usually reboots... And these random reboots occur not only in pubg but also in other apps if I try to multitask or click the buttons fastly or try to use my phone very quickly.
Please help me guys.
-Thank You:good:
Shoury_Jain55 said:
Hello everyone!
Pls help me on this one...
I have:
- unlocked Boot loader
- installed Twrp 3.2.1 vendor patch
- installed Magisk 16.0
- flashed DotOs 2.4 treble ROM
- installed Franco kernel (fk6)
on my Redmi Note 4 (mido).
The problem is:
- whenever I reboot my device a message appears from DotOs System which says: There is an internal problem in your device. Please contact your manufacturer.
- whenever I play Pubg mobile, my phone usually reboots... And these random reboots occur not only in pubg but also in other apps if I try to multitask or click the buttons fastly or try to use my phone very quickly.
Please help me guys.
-Thank You:good:
Click to expand...
Click to collapse
This is caused due to franco kernel on an older patch. Nothing really worth worrying about.
MyNameIsRage said:
This is caused due to franco kernel on an older patch. Nothing really worth worrying about.
Click to expand...
Click to collapse
Umm okay, so what should I do now? By the way, thanks...
Shoury_Jain55 said:
Umm okay, so what should I do now? By the way, thanks...
Click to expand...
Click to collapse
I wouldn't trust my life (android device) on franco kernel for now. If I were you I'd download latest Lineage Rom, latest gapps, Magisk vcustom version that supports treble enabled roms, then kud kernel. Put them on an external sd or file storage, completely wipe my phone except the external part of it, then flash them in the said order. Franco kernel been updated quite a while ago. Since then lots of things have changed in the aosp based roms. The kernel might cause those problems of yours. Also first of all, before doing anything I'd flash latest Orange Fox Treble enabled recovery R6 beta, which solves some flashing issues. This is what I'd do to solve those problems of yours within 10 minutes. But it's just me, a purist being real and being safe than sorry.
greenys' said:
I wouldn't trust my life (android device) on franco kernel for now. If I were you I'd download latest Lineage Rom, latest gapps, Magisk vcustom version that supports treble enabled roms, then kud kernel. Put them on an external sd or file storage, completely wipe my phone except the external part of it, then flash them in the said order. Franco kernel been updated quite a while ago. Since then lots of things have changed in the aosp based roms. The kernel might cause those problems of yours. Also first of all, before doing anything I'd flash latest Orange Fox Treble enabled recovery R6 beta, which solves some flashing issues. This is what I'd do to solve those problems of yours within 10 minutes. But it's just me, a purist being real and being safe than sorry.
Click to expand...
Click to collapse
Wow. Thanks, I would definitely try those...
greenys' said:
I wouldn't trust my life (android device) on franco kernel for now. If I were you I'd download latest Lineage Rom, latest gapps, Magisk vcustom version that supports treble enabled roms, then kud kernel. Put them on an external sd or file storage, completely wipe my phone except the external part of it, then flash them in the said order. Franco kernel been updated quite a while ago. Since then lots of things have changed in the aosp based roms. The kernel might cause those problems of yours. Also first of all, before doing anything I'd flash latest Orange Fox Treble enabled recovery R6 beta, which solves some flashing issues. This is what I'd do to solve those problems of yours within 10 minutes. But it's just me, a purist being real and being safe than sorry.
Click to expand...
Click to collapse
Bro noting hepled me... What's should I do now, it was working fine for a few days but now I m back with the same problem...
Shoury_Jain55 said:
Bro noting hepled me... What's should I do now, it was working fine for a few days but now I m back with the same problem...
Click to expand...
Click to collapse
Did you try everything I wrote above? These steps should work in case you badly messed up your system. I mean, I fiddle and meddle with my OS all the time, often rendering my phone unusable. As much that I have to clean wipe and reinstall the whole OS following the steps I provided. There was no case when a whole, system wide wipe and a clean install wouldn't solve.
greenys' said:
Did you try everything I wrote above? These steps should work in case you badly messed up your system. I mean, I fiddle and meddle with my OS all the time, often rendering my phone unusable. As much that I have to clean wipe and reinstall the whole OS following the steps I provided. There was no case when a whole, system wide wipe and a clean install wouldn't solve.
Click to expand...
Click to collapse
Yep...
Installed lineage 15.1
Kud kernel
Magisk 16.7
Orange fox recovery
Still it redboots randomly sometimes...
Shoury_Jain55 said:
Yep...
Installed lineage 15.1
Kud kernel
Magisk 16.7
Orange fox recovery
Still it redboots randomly sometimes...
Click to expand...
Click to collapse
Perhaps I can give you one more tip that you can try.
First, if you have an external SD card make sure to copy latest stable global MiUi ROM, latest Lineage OS for mido, latest open gapps, kud kernel, Magisk 16.0 treble enabled and orange fox onto it. If not then download these to your pc or laptop.
1) Make a full wipe including system, data, vendor, cache, dalvik and internal storage.
2) From TWRP flash latest MiUi stable global rom.
(if you have external SD do it from there, if you don't, since you made a full wipe, your internal SD is empty. Through USB sideload copy MiUi onto your internal SD and flash it from there if you don't have an external SD with the flashable zips on it)
3) Boot up the system, make sure everything is working.
4) Reboot to TWRP and do a full wipe again.
5) Flash Lineage OS from your external SD or copy the required zip onto your internal SD through USB sideload.
6) Now flash latest gapps (pico is far enough)
7) Flash Kud Kernel
8) Flash Magisk 16.0 treble enabled or magisk vcustom, they are the same but more stable than 16.7 which is still beta.
9) Reboot to system and see for yourself if everything is working.
I hope this solves your problem. Sometimes if you flash back MiUi it solves some crash perhaps firmware related problems. I don't know but this helped me a few times. If you messed up something USB sideload is always an option to copy any flashable zip onto your internal SD, however I always use external SD for it's easy to trust and use.
In case your data/internal SD shows 0 kb/mb free space do a data wipe and a partition from special settings in TWRP with all sizes set to 0.
I don't have any more tips to help you. Sorry.
I would say get Orangefox or Redwolf recovery if you dont have them already. Try flashing any rom and see if your problem persists,if not flash magisk and custom kernels. With the process of elimination you should know the source of the problem which i think is francokernel as it was mentioned.
greenys' said:
Perhaps I can give you one more tip that you can try.
First, if you have an external SD card make sure to copy latest stable global MiUi ROM, latest Lineage OS for mido, latest open gapps, kud kernel, Magisk 16.0 treble enabled and orange fox onto it. If not then download these to your pc or laptop.
1) Make a full wipe including system, data, vendor, cache, dalvik and internal storage.
2) From TWRP flash latest MiUi stable global rom.
(if you have external SD do it from there, if you don't, since you made a full wipe, your internal SD is empty. Through USB sideload copy MiUi onto your internal SD and flash it from there if you don't have an external SD with the flashable zips on it)
3) Boot up the system, make sure everything is working.
4) Reboot to TWRP and do a full wipe again.
5) Flash Lineage OS from your external SD or copy the required zip onto your internal SD through USB sideload.
6) Now flash latest gapps (pico is far enough)
7) Flash Kud Kernel
8) Flash Magisk 16.0 treble enabled or magisk vcustom, they are the same but more stable than 16.7 which is still beta.
9) Reboot to system and see for yourself if everything is working.
I hope this solves your problem. Sometimes if you flash back MiUi it solves some crash perhaps firmware related problems. I don't know but this helped me a few times. If you messed up something USB sideload is always an option to copy any flashable zip onto your internal SD, however I always use external SD for it's easy to trust and use.
In case your data/internal SD shows 0 kb/mb free space do a data wipe and a partition from special settings in TWRP with all sizes set to 0.
I don't have any more tips to help you. Sorry.
Click to expand...
Click to collapse
Still didn't work
Maybe there is some hardware problem...
Well, thanks for the help! ?
Shoury_Jain55 said:
Still didn't work
Maybe there is some hardware problem...
Well, thanks for the help!
Click to expand...
Click to collapse
Oh, well. Perhaps you're right. I do this every week and works. I'm sorry I couldn't help you.
Shoury_Jain55 said:
Hello everyone!
Pls help me on this one...
I have:
- unlocked Boot loader
- installed Twrp 3.2.1 vendor patch
- installed Magisk 16.0
- flashed DotOs 2.4 treble ROM
- installed Franco kernel (fk6)
on my Redmi Note 4 (mido).
The problem is:
- whenever I reboot my device a message appears from DotOs System which says: There is an internal problem in your device. Please contact your manufacturer.
- whenever I play Pubg mobile, my phone usually reboots... And these random reboots occur not only in pubg but also in other apps if I try to multitask or click the buttons fastly or try to use my phone very quickly.
Please help me guys.
-Thank You:good:
Click to expand...
Click to collapse
Wrong forum.
Go to DotOs forum, and ask your question.
Mybe your rom not compatible for mido.
Shoury_Jain55 said:
Yep...
Installed lineage 15.1
Kud kernel
Magisk 16.7
Orange fox recovery
Still it redboots randomly sometimes...
Click to expand...
Click to collapse
Probably Cpu throttling service asks for increase in cpu frequency due to the requirement , but when the cpu frequency is scaled up high , but due to some internal problem (temperature sensor failure or faulty processor etc...) the temperature detected is too high that the phone reboots.
TBH I have no idea about how android devices work but this happens on PS4 due to burnt capacitors , this can be fixed sometimes.
Buddy I will help u...
Just download the build.prop editor from playstore and grant root permission and search for ro.treble.enabled line and change it to false:fingers-crossed:
rc chanu said:
Buddy I will help u...
Just download the build.prop editor from playstore and grant root permission and search for ro.treble.enabled line and change it to false:fingers-crossed:
Click to expand...
Click to collapse
Thank you bro, works for me.
Very nice!!!
Hi dears
I have one BIG problem with MIUI 10 rom in note 4x. (as same as 9.6) When i delete a file (always with 3rd file managers like solid exolorer and sometimes with Mi file manager) the free space doesn't change till i reboot the phone. It happens with internal memory, sdcard and even otg drive!
I flashed miui 10 firmware with miflash software (in ''clean all'' mode)
I exactly had this problem in Miui 9 (since nougat) and i fixed that with this guide for oneplus (disabling sdcardfs with magisk module)
https://www.xda-developers.com/io-bug-on-oxygenos-4-is-causing-deleted-files-to-still-take-up-space/
but now this trick doesn't work anymore, although my android version is still 7.0
also in build.prop i don't have any phrase about "sdcardfs" please help ... My memory is always full and i should restart my phone every hour :crying:
I suggest you report this issue to the official Miui forum for developers to fix in future releases.
Lots n lots of issues with MIUI 10.X LATEST rom..
mi Forums are cluttered with SPAM and not many great contriuBtors here to support this device..
We are nowhere..
Chinese people dont understand English.. :/
Make something and let us suffer..
Is there any Q rom that has
1. Safety Net passing without magisk
2. Supports encryption ( so that if I lose my phone, someone can't access data easily. Earlier P elms used to support encryption)
3. Selinux enforcing
Strangely a few months ago, there were many P roms that had all of the above, but I can't find Q roms that have these features. Is it something about Q. Also, even the recent update of Los 16 don't pass Safety Net. Has something changed about android/google that is causing it?
Thanks
Android Q has File based Encryption (FBE) not Full Disk encryption. And at present TWRP cannot decrypt FBE. And this it cannot Mount /data partition to do OTA updates or anything of the sort. The main TWRP maintainer is presently busy with other very important things in his life so FBE for TWRP may take a while.
Plus Xiaomi has not yet released Android 10 for Poco so it could also be that some firmware component is missing to support FBE (I'm not sure). If so it could be why the ROMs have trouble implementing it.
Regarding selinux, it will be a while before ROMs become really stable.
@ziglar24 if you're willing to learn you can contribute to twrp at Gerrit Code Review TWRP