Hey,
So after a lot of observation and reading I think LOS 17.1 seems stable enough to be used for a daily driver.
Right now I am on the normal stock ROM, without any modifications, no TWRP, no root whatsoever.
However, I have unlocked the bootloader a few months ago, so that's done already.
Current state of the phone:
Code:
MIUI version: 11.0.1.0 (QFKMIXM) - Is this the global version?
Device model: Mi 9T Pro (128GB, 6GB RAM)
I want to install TWRP, I want to root the phone, I want to install all needed modules for a proper camera etc, I want to install LineageOS 17.1 (latest build) and lastly I want to install Immensity Kernel (latest build) because I have heard it works well with LOS and provides lots of battery improvements.
I did lots of tinkering with my phone a couple years back, but I haven't done so in a while, and neither have I done anything with this device, so to make sure I am not breaking anything I decided its the best to ask here.
What steps do I have to provide in which order? Can someone provide my a detailed explanation of all the needed steps?
Also, can I install MicroG on it, or do I have to use GApps?
My guess is, first TWRP and root, then ROM and then kernel?
Also, I have read about some issues with Magisk and Android 10, is that still a problem, or is that solved by now?
Anything else I need to look out for?
Cheers
KuroRyu said:
Hey,
So after a lot of observation and reading I think LOS 17.1 seems stable enough to be used for a daily driver.
Right now I am on the normal stock ROM, without any modifications, no TWRP, no root whatsoever.
However, I have unlocked the bootloader a few months ago, so that's done already.
Current state of the phone:
I want to install TWRP, I want to root the phone, I want to install all needed modules for a proper camera etc, I want to install LineageOS 17.1 (latest build) and lastly I want to install Immensity Kernel (latest build) because I have heard it works well with LOS and provides lots of battery improvements.
I did lots of tinkering with my phone a couple years back, but I haven't done so in a while, and neither have I done anything with this device, so to make sure I am not breaking anything I decided its the best to ask here.
What steps do I have to provide in which order? Can someone provide my a detailed explanation of all the needed steps?
Also, can I install MicroG on it, or do I have to use GApps?
My guess is, first TWRP and root, then ROM and then kernel?
Also, I have read about some issues with Magisk and Android 10, is that still a problem, or is that solved by now?
Anything else I need to look out for?
Cheers
Click to expand...
Click to collapse
Make sure you are in the latest version of MIUI first.
For TWRP flash the latest Mauronofrio TWRP, he has the official TWRP, but his unofficial, latest version is probably a better option at its a little bit more up to date.
Once you've flashed TWRP you will need to boot immediately in to TWRP without allowing the phone to boot into MIUI, otherwise the phone will detect that recovery had been modified and will restore stock recovery.
When you've booted into TWRP, format data (needs to be format and not only wipe), then wipe cache and dalvik.
Reboot into TWRP, to ensure that the newly formatted data partition is correctly mounted.
Now flash lineage and a GApps package. I've only used Open GApps Pico, but I believe microG should be OK. If you use Open GApps it is still in beta and packages larger than the micro package are likely to cause issues, so stick with micro, pico or nano. (For clarification, micro G is a GApps package, what you are really asking is do you need to use Open GApps or not)
The latest Magisk is fine now. It is recommended to boot into LOS first at least once before flashing Magisk. I can't remember the details but sometimes you may get issues if you flash Magisk after flashing a ROM, without booting to the ROM first. You may be fine if you don't boot the ROM first, but since I've forgotten the reasons and can no longer find it, I now boot the ROM before flashing Magisk, just to be safe.
From here, you should be OK to flash different kernels, personally I've never felt the need to, as I'm happy with the performance of things as they are. My battery life is similar to what it was on stock MIUI. If you want to try kernels other than Immensity, just double check first that it is for AOSP ROMs. There are some kernels that have been created that are only compatible with Stock MIUI.
For the camera, I believe the latest advice for ANX Cam is still version 158 along with the 48MP fix for Q ROMs. There are a few later versions, which are not appropriate for this phone. I don't believe there has been a later version for this phone.
Edit: just noticed your question in the quote.
You have the global version of the phone. AFAIK 11.0.1 is still the latest version of the global version of MIUI.
Robbo.5000 said:
Make sure you are in the latest version of MIUI first.
For TWRP flash the latest Mauronofrio TWRP, he has the official TWRP, but his unofficial, latest version is probably a better option at its a little bit more up to date.
Once you've flashed TWRP you will need to boot immediately in to TWRP without allowing the phone to boot into MIUI, otherwise the phone will detect that recovery had been modified and will restore stock recovery.
When you've booted into TWRP, format data (needs to be format and not only wipe), then wipe cache and dalvik.
Reboot into TWRP, to ensure that the newly formatted data partition is correctly mounted.
Now flash lineage and a GApps package. I've only used Open GApps Pico, but I believe microG should be OK. If you use Open GApps it is still in beta and packages larger than the micro package are likely to cause issues, so stick with micro, pico or nano. (For clarification, micro G is a GApps package, what you are really asking is do you need to use Open GApps or not)
The latest Magisk is fine now. It is recommended to boot into LOS first at least once before flashing Magisk. I can't remember the details but sometimes you may get issues if you flash Magisk after flashing a ROM, without booting to the ROM first. You may be fine if you don't boot the ROM first, but since I've forgotten the reasons and can no longer find it, I now boot the ROM before flashing Magisk, just to be safe.
From here, you should be OK to flash different kernels, personally I've never felt the need to, as I'm happy with the performance of things as they are. My battery life is similar to what it was on stock MIUI. If you want to try kernels other than Immensity, just double check first that it is for AOSP ROMs. There are some kernels that have been created that are only compatible with Stock MIUI.
For the camera, I believe the latest advice for ANX Cam is still version 158 along with the 48MP fix for Q ROMs. There are a few later versions, which are not appropriate for this phone. I don't believe there has been a later version for this phone.
Edit: just noticed your question in the quote.
You have the global version of the phone. AFAIK 11.0.1 is still the latest version of the global version of MIUI.
Click to expand...
Click to collapse
Do I also need the force encrypt file? Some people mention it needs to be flashed too?
How do I properly install twrp? I boot into fastboot mode, and then I can flash it, I assume?
In the thread it also states that one should first flash vbmeta?
EDIT: Ok, I flashed vbmeta and twrp, booted into twrp, formated data and wiped dalvik and cache.
Now should I flash LOS next and then gapps ..? Which GApp package is the right one for 17.1? It is not linked in the LOS thread?
I've read that some people had issues when flashing the wrong gapps package
EDIT2: Ok, so far I have persisted TWRP and installed magisk. I flashed LOS 17.1 (latest build) and booted into it. I did not flash gapps yet as I dont know which gapps package to use. Also I would prefer to use microG if possible, but I dont think its possible to install it easiely? If it is, please let me know.
Now, the issue is, for some reason after the clean install of LOS17.1 I still see google apps like google drive (remember, I did not flash gapps). This shouldn't be the case? I did format data and cleared dalvik and cache, so it is a bit weird that this happens...
Also I constantly get "android.process.media keeps stopping" .. I assume that is because some applications try to access google service, which are not correctly available? What did I do wrong?
So my questions are:
1) Is it possible to use microG (opensrc implementation of google services), rather than gapps? If so, how?
2) If I need to use GApps, which one to flash?
3) Why were google apps still present on my device after flashing and formatting data ..?
KuroRyu said:
Do I also need the force encrypt file? Some people mention it needs to be flashed too?
How do I properly install twrp? I boot into fastboot mode, and then I can flash it, I assume?
In the thread it also states that one should first flash vbmeta?
EDIT: Ok, I flashed vbmeta and twrp, booted into twrp, formated data and wiped dalvik and cache.
Now should I flash LOS next and then gapps ..? Which GApp package is the right one for 17.1? It is not linked in the LOS thread?
I've read that some people had issues when flashing the wrong gapps package
EDIT2: Ok, so far I have persisted TWRP and installed magisk. I flashed LOS 17.1 (latest build) and booted into it. I did not flash gapps yet as I dont know which gapps package to use. Also I would prefer to use microG if possible, but I dont think its possible to install it easiely? If it is, please let me know.
Now, the issue is, for some reason after the clean install of LOS17.1 I still see google apps like google drive (remember, I did not flash gapps). This shouldn't be the case? I did format data and cleared dalvik and cache, so it is a bit weird that this happens...
Also I constantly get "android.process.media keeps stopping" .. I assume that is because some applications try to access google service, which are not correctly available? What did I do wrong?
So my questions are:
1) Is it possible to use microG (opensrc implementation of google services), rather than gapps? If so, how?
2) If I need to use GApps, which one to flash?
3) Why were google apps still present on my device after flashing and formatting data ..?
Click to expand...
Click to collapse
There is no need to flash force encrypt files or vbmeta.
I have never used MicroG so couldn't give any answers about that, however Open GApps are open source too. For android 10 it is still in beta. The beta files can be found here https://sourceforge.net/projects/opengapps/files/arm64/beta/20191209/. Pico is the smallest package that gives Google Play, personally I recommend going with that, then installing any other Google stuff from the play store, should you want them.
No idea why you would be seeing Google apps. I can only suggest formatting data again in TWRP.
If that doesn't work I would start again. Fastboot flash the latest MIUI 11.0.1 global ROM, boot into it once, there is no need to go through the set-up. Then go through the steps given before.
This time don't flash vbmeta, it is not needed.
The fastboot ROM can be found here http://bigota.d.miui.com/V11.0.1.0....M_20191111.0000.00_10.0_global_11d3a1700a.tgz
Edit:
Having seen some of your other posts, I'll give you some more info.
vbmeta is mainly used to persist TWRP. However flashing Magisk will persist TWRP and flashing a custom ROM will persist TWRP. You would only need to flash vbmeta if you wanted to stay on MIUI and not use Magisk. (There are other uses for vbmeta, but you don't need them, so I'll not go into them)
Is widevine L1 available on the ROM? Is the FOD working well?
Related
It's been a year and a half since last time i had messed around with custom roms.
I am currently on stock 8.0 Oxygen OS. What would be the steps to install OmniROM 8.1?
I'm thinking the following.
1. unlock bootloader
2. Flash TWRP
3. Root
4. Wipe/format
5. flash OMNI rom 8.1?
Do I first need to update to 8.1 somehow?
You may want to update to the latest Open Beta firmware, which you can get the standalone files from here ( https://forum.xda-developers.com/oneplus-3t/how-to/firmware-beta-10-t3631166)
Flash this before flashing the ROM.
Also you may want to flash the Root method after flashing the ROM. Your best choice is Magisk, since it's getting ready updates and it has many extra features. SuperSU is old and not done by chainfire anymore, so don't flash SSU.
Also remember to wipe these specific partitions:
System
Data
Cache
Dalvik Cache.
I'm not sure by what you mean by "Updating to 8.1" as OOS is still on 8.0, even the Open Beta's. Flash the latest Firmware from Recovery and you should be good go.
Also, don't forget to grab NezorFlame's unofficial GAPPS, since OpenGAPPS still hasn't been updated to 8.1.
(https://sourceforge.net/projects/unofficial-opengapps-8-1/files/arm64/)
Also just keep in mind, unlocking your bootloader will wipe your internal storage. This is a security feature and cannot be bypassed.
IMO, there are better ROMs than Omni. You should try Z-Unleashed or Resurrection Remix 6.0.0. They're the best ROMs with the best customization and usage per user for now.
Good luck, and happy flashing!
You don't need to wipe data if you're going to unlock bootloader, since as mentioned earlier, unlocking BL deletes all of yor data.
Dalvik Cache isn't used anymore (we are on ART now), so no need to wipe it separately, it even reside in /data partition.
Also no need to flash firmware files if you're on OOS 5.
ROM, GApps and Magisk will be enough.
przemcio510 said:
Also no need to flash firmware files if you're on OOS 5.
Click to expand...
Click to collapse
Well, most of the ROMs recommend Open Beta 22 firmware, since this is the FW the developers build the recently updated ROMs on. He may experience issues if he's on OOS 5.0 fw.
I have the PRA-LX1 with already unlocked bootloader and got it rooted with TWRP + Magisk before the last OTA.
I'm not a beginner with rooting this phone but only got Problems with installing any Treble Rom (tried Lineage and Aosp) and every try ended with a bootloop I don't know what I'm doing wrong.
So please can anyone give me a step by step instruction?
Which Treble Rom is a good one and recommended for this phone?
Which TWRP do I need?
And how exactly do I flash them correctly? What do I wipe?
Sorry for this noob questions but I failed so many times with Treble and don't want to do the reinstall with erecovery for the 10000 time :crying:
Thanks
Try to install the stock recovery and ramdisk.
+1
I also have this problem. Wich TWRP works with treble roms? i tryed everything and everytime i get a boot loop.
Please help.
After I flashed a treble gsi, I need to flash stock recovery?
Atiqx said:
After I flashed a treble gsi, I need to flash stock recovery?
Click to expand...
Click to collapse
Yes. if u still get bootloop flash stock recovery and ramdisk first then flash gsi. make sure u factory reset on stock recovery after u flash gsi.
ppdr07 said:
Try to install the stock recovery and ramdisk.
Click to expand...
Click to collapse
ppdr07 said:
Yes. if u still get bootloop flash stock recovery and ramdisk first then flash gsi. make sure u factory reset on stock recovery after u flash gsi.
Click to expand...
Click to collapse
And which TWRP should I use for flashing?.. And how can I flash GSI with stock?
That makes no sense to me sorry
Flash via fsstboot. Stock recovery and ramdisk flash via fastboot. Im not using twrp so idk.
---------- Post added at 08:38 AM ---------- Previous post was at 08:37 AM ----------
U can see a tutorial at xda how to flash gsi without twrp. Google it.
ppdr07 said:
Flash via fsstboot. Stock recovery and ramdisk flash via fastboot. Im not using twrp so idk.
---------- Post added at 08:38 AM ---------- Previous post was at 08:37 AM ----------
U can see a tutorial at xda how to flash gsi without twrp. Google it.
Click to expand...
Click to collapse
I googled it, pretty much every source says that you require a custom recovery in order to flash a GSI or any custom ROM.
XDA XILFY said:
I googled it, pretty much every source says that you require a custom recovery in order to flash a GSI or any custom ROM.
Click to expand...
Click to collapse
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/ u will find Flash GSI without TWRP
ppdr07 said:
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/ u will find Flash GSI without TWRP
Click to expand...
Click to collapse
Oh, well that's pretty cool. Either way, I just tried flashing Official Resurrection Remix GSI with no luck. Stock recovery, attempted to flash through fastboot and it just gives me a bootloop, exactly like TWRP does. Followed the guide you linked to etc, just keeps rebooting.
XDA XILFY said:
Oh, well that's pretty cool. Either way, I just tried flashing Official Resurrection Remix GSI with no luck. Stock recovery, attempted to flash through fastboot and it just gives me a bootloop, exactly like TWRP does. Followed the guide you linked to etc, just keeps rebooting.
Click to expand...
Click to collapse
Go to openkirin.net/download download the rr beta 3
Atiqx said:
I have the PRA-LX1 with already unlocked bootloader and got it rooted with TWRP + Magisk before the last OTA.
I'm not a beginner with rooting this phone but only got Problems with installing any Treble Rom (tried Lineage and Aosp) and every try ended with a bootloop I don't know what I'm doing wrong.
So please can anyone give me a step by step instruction?
Which Treble Rom is a good one and recommended for this phone?
Which TWRP do I need?
And how exactly do I flash them correctly? What do I wipe?
Sorry for this noob questions but I failed so many times with Treble and don't want to do the reinstall with erecovery for the 10000 time :crying:
Thanks
Click to expand...
Click to collapse
Well, I finally got it all working.
You know the risks, don't blame me if something goes wrong, I did these exact steps to manage to root my phone without breaking it. C432, Dual SIM and PRA-LX1.
Have everything stock before following this short guide: Firmware, all stock recovery etc.
Installing the ROM and GApps
First, download necessary GSI files.
(Personally I got Official Oreo Resurrection Remix, here).
(Although you could find yourself using virtually any other GSI, I like the look and feel of RR, though I'll be changing my boot animation with root). Many people would probably recommend you to use something like an AOSP, or LOS which I was also considering on installing. They may also come bundled with GApps, which would negate the later need for installation or download of separate GApps.
This may include GAPPS but you should understand this from the GSI page, so for example on RR I had to download both the latest base ROM .img and the micro GApps.
So to do this I had to use the right architecture (For the P8 Lite 2017, this is ARMx64, do your good research, since my problem was getting this wrong with my PRA-LX1 (Mine was A-ONLY), this stands for the base ROM and GApps.
After this I actually didn't use TWRP as user @ppdr07 advised. I followed the guide he linked us to and did as so, without following the -u command, since it wasn't working for me (didn't affect anything, try it, if it doesn't work, just take that bit out).
The ROM ended up installing and posting through, everything set up perfectly.
After this I was like "Huh, so what now? How am I to flash GApps on this without TWRP?". I went for it and booted into fastboot where I flashed Askuccio's TWRP for hi6250 devices. At this point I worried that the ROM wouldn't post again - though it did, so from there I enabled dev options and switched on advanced power options just for ease of usage. From there I rebooted straight to recovery which posted fine, too.
At this point, you need to flash the GApps. Go for the one that the original GSI page recommends. Flash it to the System Image partition. Don't wipe anything. At this point I recommend that if you realise that you forgot to transfer any files to the SD card, you should do it from the system. It works better compared to the MTP on TWRP. Either way, that should work properly. Now, reboot the system, and it should work perfectly.
Enjoy, it took me months to get to this point lol
Rooting Your New ROM With Magisk
(Before installing this consider the other root options. I believe there's SuperSU and another possibly that I'm less aware of. Either way, in my opinion Magisk comes with the most benefits so I'll be helping you out with that).
After this I ended up flashing Magisk in order to use Snapchat and other apps similar to it. Firstly you'll want to set up Google stuff which has been newly added to the system, and then you'll want to go to chrome and download the Magisk Manager .apk from here. The main and most reliable place to get it is from the creator's project page found here, all main links stand out in the middle fairly well.
(Remember to enable downloading of unknown apps for Chrome in it's app settings, otherwise it won't download or install.)
If it still doesn't work at this point, I ended up holding down on the Magisk Manager link and pressing Download Link (or something to that effect). From this point just install it as you would any other out-of-store app.
Now, you'll need to download these two files from the Magisk page onto your computer: Stable Installer and Uninstaller. Next, while booted into Android, copy them over to either Internal or External storage and when it's done, reboot into TWRP again, either by advanced power menu or using the button commands for recovery. Personally, I think I need the power options with this phone.
In TWRP, simply go to Install, navigate to /externalsd/***[WHEREVER YOU PLACED YOUR MAGISK FILES]***, then install the Magisk installer .zip. If unchanged, the filename should be something like "Magisk-v17.1.zip". Install it, then give rebooting a go. Hopefully it'll post, if not, go back into TWRP and run the Uninstaller .zip, it's saved me a bunch of times.
Unblocking Apps That Say Something Like "Your Phone is Rooted or Modified, no access blah blah blah..."
(Snapchat is the example used here. It won't work upon login if you don't follow this step. Some apps don't work with this alone however, though somebody may have produced a separate guide or easily installable Magisk module with a solution for it. One that won't be fixed singularly with Magisk Hide is Google Pay).
After posting, if you need to unblock Snapchat or something, go to Magisk Manager (which should now be more green), open the top left context menu, tap on Magisk Hide, and search "snap" until you see the Snapchat logo pop up, then select it, then back out with the back button. It should stay selected in Magisk, and the app should now be usable and shouldn't give you any annoying errors, if not give it a reboot and see if it's solved.
Good luck!
We already know this phone is arm64,
the GSI rom AOSP v112 has support for this phone.
But how is the rom behave? What works and doesn't?
How are other GSI flavours doing? Like RR, AEX, HAVOC,....
[NOTE: For those who are interested i'll change this post to some GSI guide cepheus,
as soon as i recieve my Mi 9. But until then i'll hope for some of your feedback]
See this: https://github.com/phhusson/treble_experimentations/wiki/Xiaomi-Mi-9
and these two: https://forum.xda-developers.com/showpost.php?p=79284072&postcount=46, https://forum.xda-developers.com/showpost.php?p=79295919&postcount=53
It shoudn't be needed to write a guide
a video guide would be interesting
I usually used twrp to flash the Gsi file but now I didn't understand what steps should be taken
tried Foloko, RR trebles and it's entertaining as STDs.. couldn't add Gapps for hours and never managed to using 2 very different TWRPs we've got, tons of tricks, or adding stock system/vendor.
I don't understand the assumption "Please don't use third-party custom rom (e.g. Xiaomi.eu roms) as the base rom. Some hacky roms have wrong (unofficial) fingerprint and GSI can't detect what device you are using. ", ok, what should be in the phone then?
After some attempts Phh treble from post 60 installed, greeting me with "There's an internal problem with your device. Contact your manufacturer for details.", some vendor nonsense. After reboot i cannot log in, as fingerprint overrides the letter i need to type the password. omg. So i have to reflash.
update: since Phh was ultra vanilla with literally 2 extra settings, tried RR, same greeting, no fp, and no swipe to apps there, i don't really beg for their modifications as i have Xposed Edge for this. Finally went back to Floko knowing how to fix gapps problem, it's got best navbar solution, although with tons of bugs (contradicting navbar user actions, non responsive gestures, nonresponsive buttons), no tap2wake, AOD sucks, fp sucks too, produces blinking screen.
Looks like trebles are unusable, time to go back to XIAOMI EU... so much for "don't need device specific ROMs".
doggydog2 said:
tried Foloko, RR trebles and it's entertaining as STDs.. couldn't add Gapps for hours and never managed to using 2 very different TWRPs we've got, tons of tricks, or adding stock system/vendor.
I don't understand the assumption "Please don't use third-party custom rom (e.g. Xiaomi.eu roms) as the base rom. Some hacky roms have wrong (unofficial) fingerprint and GSI can't detect what device you are using. ", ok, what should be in the phone then?
After some attempts Phh treble from post 60 installed, greeting me with "There's an internal problem with your device. Contact your manufacturer for details.", some vendor nonsense. After reboot i cannot log in, as fingerprint overrides the letter i need to type the password. omg. So i have to reflash.
Click to expand...
Click to collapse
You have to flash *official* MIUI rom (China or Global depend on your hardware, and it's better to flash developer version to get latest update).
To install GApps, you have to do Wipe -> Advanced wipe -> Select system -> Resize, then Mount -> mount system, then install GApps zip.
dear mod please close this one, there seems to be already a conversation about this
AndroPlus said:
You have to flash *official* MIUI rom (China or Global depend on your hardware, and it's better to flash developer version to get latest update).
To install GApps, you have to do Wipe -> Advanced wipe -> Select system -> Resize, then Mount -> mount system, then install GApps zip.
Click to expand...
Click to collapse
tried to do that, tried to install arm64 Gapps, I'd get an error saying my system is arm, so i install arm gapps, they do get "installed", but when i reboot, there is no gapps at all.
edit: arm64 gapps worked when used LR.Team/wzsx150 twrp.
AndroPlus said:
You have to flash *official* MIUI rom (China or Global depend on your hardware, and it's better to flash developer version to get latest update).
To install GApps, you have to do Wipe -> Advanced wipe -> Select system -> Resize, then Mount -> mount system, then install GApps zip.
Click to expand...
Click to collapse
which Global please? this is the link http://en.miui.com/download-361.html claiming to be Full Rom, but the zip is similar to EU version, just a patch.. just tried it, then flashed EU and magisk and getting "can't connect to camera". i was thinking i need to flash some bigger package (.tgz file), but there's none published and going throught the million childish looking forums on eu.miui.com, not sure.. would like TWRP way. perhaps format system?
doggydog2 said:
which Global please? this is the link http://en.miui.com/download-361.html claiming to be Full Rom, but the zip is similar to EU version, just a patch.. just tried it, then flashed EU and magisk and getting "can't connect to camera". i was thinking i need to flash some bigger package (.tgz file), but there's none published and going throught the million childish looking forums on eu.miui.com, not sure.. would like TWRP way. perhaps format system?
Click to expand...
Click to collapse
You can find fastboot image here:
https://en.miui.com/a-234.html
AndroPlus said:
You can find fastboot image here:
https://en.miui.com/a-234.html
Click to expand...
Click to collapse
thanks but both links redirect me to http://www.miui.com/ in chinese where i can browse to quasi-full roms again. strange.
btw i'm a fan of your kernel except it causes "can't connect to camera".. after many combinations of flashing i tried skipping the kernel (v01, or v02 or any kernel), and camera is back. however without Night mode this time...
update: found stable ROM at least https://c.mi.com/thread-1907373-1-0.html
update: somehow i trust this is the legit link to develop ROM http://bigota.d.miui.com/9.3.1/ceph....1_20190301.0000.00_9.0_global_cdb3885bac.tgz
AndroPlus said:
You can find fastboot image here:
https://en.miui.com/a-234.html
Click to expand...
Click to collapse
Hey,
Could you make your magisk patch to not require pressing FP scanner twice for FP to register?
Without the patch, works fine from first try, but with it, two presses at least are needed Everytime.
Thank you!
Hi,
since many days I have a new Mi8.
The device is a chineese model, and because it was delivered with unlocked bootloader and a shop ROM, i want to use the latest Xiaomi.eu stable rom.
After flashing the TWRP, i cleared all (System, Data, Cache, internal storage) and installes the latest xiaomi.eu ROM.
Unfortunately the ROM was notstartet. Later i readed, that the xiaomi.eu ROM needs the system partition, so i tried to install some different ROMs.
All tested roms failed to install (device missmatch), so i tried to use different recoveries and at least i updated the vendor Image to MI8Global_V10.3.5.0.PEAMIXM.
After this, some Roms are able to install, mut the ROMs wont boot.
After a clean install of the xiomi global fastboot image, the phone is running, but i still have problems to install custom ROMs or the stable Xiaomi.eu ROM.
The fastboot ROM installation with mi flash tools ends with an error (Not catch checkpoint (\fastboot -s .*lock) Flash is not done (I choosed the option clean all, not the lock function)
cDroid Rom is working, but with this ROM i cant use google pay.
cDroid with update to xiaomi.eu weekly is also working, but also without google pay.
Xiaomi.eu stable - bootloops
Do you have any ideas why i cant use all ROMs?
Should i choose a chineesevendor image or something else?
I also heared, that it could be, that the device bricks, when i try to re-lock the bootloader, is this an option?
Which ROM should work fith functional google pay ?
Thanks in advance
The problem seems to be solved,
i have to flash "Disable_Dm-Verity_ForceEncrypt" after the flashing of every ROM, then I have no bootloops / boot Problems.
Now i only have the problem with google pay...
I couldn't also get Miui Eu bootable on my mi8 last time. I didn't realize what you had mentioned Disable_Dm-Verity_ForceEncrypt. But I could manage to get MiRoom Miui workable and it seems ok for now.
stevedat said:
I couldn't also get Miui Eu bootable on my mi8 last time. I didn't realize what you had mentioned Disable_Dm-Verity_ForceEncrypt. But I could manage to get MiRoom Miui workable and it seems ok for now.
Click to expand...
Click to collapse
DM verity zip removes the 'DM Verity' check that looks for modifications to the boot partitions (D-device M-mapper). You cannot boot with modifications (like root) without disabling the verity check. Also, if you are on a stock ROM, your custom recovery image file will be overwritten with stock upon reboot if you don't disable DM Verity. Hope this helps you understand more.
Found it on this topic.
I´m still looking for a ROM with google pay support, but iu think with unlocked bootloader and without root therre is no chance...
Okay. Am currently on MIUI 11.0.3 (the latest one available for RaphaelIN)
So, the problem am facing is that, when i flash a custom rom, my phone gets rebooted to recovery and sometimes to fastboot(this happens occasionally) and i just simply cant get the rom to load.
Sometimes my phone gets into a state which resembles hardbrick (none of the buttons work, even holding the power button for 10secs doesn't) and after sometimes, usually 15 to 20 mins it restarts itself. This has happened thrice till date and all while booting to system.
The Roms i have tried-
-Pixel experience (unofficial) (android Q)
- Lineage OS 17 (unofficial)
- Havoc OS (both official and unofficial) (both pie and Q versions)
-MIUI (European rom)
I have also tried flashing the chinese, indian and global vendor (all done separately) thinking it was a vendor issue, but it also doesn't work.
Recovery is TWRP latest version, have also used orange fox recovery
Bootloader unlocking was done through the official method and the official app.
Any solutions for this problem and has anyone faced these problems or is it only me?
Astrek said:
Okay. Am currently on MIUI 11.0.3 (the latest one available for RaphaelIN)
So, the problem am facing is that, when i flash a custom rom, my phone gets rebooted to recovery and sometimes to fastboot(this happens occasionally) and i just simply cant get the rom to load.
Sometimes my phone gets into a state which resembles hardbrick (none of the buttons work, even holding the power button for 10secs doesn't) and after sometimes, usually 15 to 20 mins it restarts itself. This has happened thrice till date and all while booting to system.
The Roms i have tried-
-Pixel experience (unofficial) (android Q)
- Lineage OS 17 (unofficial)
- Havoc OS (both official and unofficial) (both pie and Q versions)
-MIUI (European rom)
I have also tried flashing the chinese, indian and global vendor (all done separately) thinking it was a vendor issue, but it also doesn't work.
Recovery is TWRP latest version, have also used orange fox recovery
Bootloader unlocking was done through the official method and the official app.
Any solutions for this problem and has anyone faced these problems or is it only me?
Click to expand...
Click to collapse
Consider this an overkill solution that always works for me if I run into issues with other methods. It will wipe everything so backup your data and apps.
Download the latest fastboot Indian MIUI ROM (for anyone else reading this download the ROM that is the same region as your phone)
Fully extract the ROM and flash it - make sure, if you use the Mi Flash Tool, that you change the flash option to 'clean all'
Boot into MIUI once, you don't need to actually go through the set-up, just let it fully load.
Boot the phone into fastboot and install TWRP - I recommend the latest mauronofrio TWRP.
After installing TWRP boot immediately into TWRP.
Format the data partition - don't skip this step.
Wipe cache and dakvik - don't wipe anything else.
In TWRP goto the mount menu and unmount the data partition then mount it again - others would suggested rebooting back into TWRP, either way works, you just need to make sure the data partition is properly mounted after formatting it.
Install the ROM of your choice - either have the ROM on a USB OTG stick, or copy it onto the phone from a PC whilst still in TWRP.
If your ROM doesn't include Google apps and services and you want Google, then install GApps - at the time of writing this Android 10 GApps is still in beta and packages bigger than nano may cause issues, so stick with pico or nano, assuming your installing an Android 10 ROM.
Boot into the ROM.
If you want Magisk, once the ROM has loaded, boot back into TWRP and flash the latest Magisk installer - it is possible to flash Magisk without booting into the ROM first and you'll probably be OK, but occasionally it can cause problems, I can't remember the details, but for the sake of 30 seconds I now boot into the ROM before flashing, just to be on the safe side.
At the time of writing this people have recently reported issues flashing GApps immediately after flashing Havoc 3.0 and recommend booting Havoc before flashing GApps. Although others say they've not had any problems. So if you choose to install Havoc you 'might' have problems if you install GApps without booting into Havoc at least once first.
I've never had problems when following this method.
You didn't format data that's why your rom doesn't boot. Follow Robbos nice guide and you are good to go.:good:
Robbo.5000 said:
Consider this an overkill solution that always works for me if I run into issues with other methods. It will wipe everything so backup your data and apps.
Download the latest fastboot Indian MIUI ROM (for anyone else reading this download the ROM that is the same region as your phone)
Fully extract the ROM and flash it - make sure, if you use the Mi Flash Tool, that you change the flash option to 'clean all'
Boot into MIUI once, you don't need to actually go through the set-up, just let it fully load.
Boot the phone into fastboot and install TWRP - I recommend the latest mauronofrio TWRP.
After installing TWRP boot immediately into TWRP.
Format the data partition - don't skip this step.
Wipe cache and dakvik - don't wipe anything else.
In TWRP goto the mount menu and unmount the data partition then mount it again - others would suggested rebooting back into TWRP, either way works, you just need to make sure the data partition is properly mounted after formatting it.
Install the ROM of your choice - either have the ROM on a USB OTG stick, or copy it onto the phone from a PC whilst still in TWRP.
If your ROM doesn't include Google apps and services and you want Google, then install GApps - at the time of writing this Android 10 GApps is still in beta and packages bigger than nano may cause issues, so stick with pico or nano, assuming your installing an Android 10 ROM.
Boot into the ROM.
If you want Magisk, once the ROM has loaded, boot back into TWRP and flash the latest Magisk installer - it is possible to flash Magisk without booting into the ROM first and you'll probably be OK, but occasionally it can cause problems, I can't remember the details, but for the sake of 30 seconds I now boot into the ROM before flashing, just to be on the safe side.
At the time of writing this people have recently reported issues flashing GApps immediately after flashing Havoc 3.0 and recommend booting Havoc before flashing GApps. Although others say they've not had any problems. So if you choose to install Havoc you 'might' have problems if you install GApps without booting into Havoc at least once first.
I've never had problems when following this method.
Click to expand...
Click to collapse
Thnx for the guide. i will do this within a day or two and update you if it worked or not.
Kollachi said:
You didn't format data that's why your rom doesn't boot. Follow Robbos nice guide and you are good to go.:good:
Click to expand...
Click to collapse
I did format the data partition coz that's one thing I and my friends always do when flashing new rom. I don't exactly remember but i think, the pseudo hardbrick thingy started after i formatted the system, data, cache & internal storage.
I will follow Robbos guide adn keep you guys updated on what happened.
Astrek said:
I did format the data partition coz that's one thing I and my friends always do when flashing new rom. I don't exactly remember but i think, the pseudo hardbrick thingy started after i formatted the system, data, cache & internal storage.
I will follow Robbos guide adn keep you guys updated on what happened.
Click to expand...
Click to collapse
Format data = (you will need to type in "yes")
Note: Format data or wipe data isn't the same thing.
Robbo.5000 said:
Consider this an overkill solution that always works for me if I run into issues with other methods. It will wipe everything so backup your data and apps.
Download the latest fastboot Indian MIUI ROM (for anyone else reading this download the ROM that is the same region as your phone)
Fully extract the ROM and flash it - make sure, if you use the Mi Flash Tool, that you change the flash option to 'clean all'
Boot into MIUI once, you don't need to actually go through the set-up, just let it fully load.
Boot the phone into fastboot and install TWRP - I recommend the latest mauronofrio TWRP.
After installing TWRP boot immediately into TWRP.
Format the data partition - don't skip this step.
Wipe cache and dakvik - don't wipe anything else.
In TWRP goto the mount menu and unmount the data partition then mount it again - others would suggested rebooting back into TWRP, either way works, you just need to make sure the data partition is properly mounted after formatting it.
Install the ROM of your choice - either have the ROM on a USB OTG stick, or copy it onto the phone from a PC whilst still in TWRP.
If your ROM doesn't include Google apps and services and you want Google, then install GApps - at the time of writing this Android 10 GApps is still in beta and packages bigger than nano may cause issues, so stick with pico or nano, assuming your installing an Android 10 ROM.
Boot into the ROM.
If you want Magisk, once the ROM has loaded, boot back into TWRP and flash the latest Magisk installer - it is possible to flash Magisk without booting into the ROM first and you'll probably be OK, but occasionally it can cause problems, I can't remember the details, but for the sake of 30 seconds I now boot into the ROM before flashing, just to be on the safe side.
At the time of writing this people have recently reported issues flashing GApps immediately after flashing Havoc 3.0 and recommend booting Havoc before flashing GApps. Although others say they've not had any problems. So if you choose to install Havoc you 'might' have problems if you install GApps without booting into Havoc at least once first.
I've never had problems when following this method.
Click to expand...
Click to collapse
Ohhh *****...!!!! It ****ing worked!!!! Though i made some mistakes like clean all and lock in first step, but was able to unlock bootloader almost instantly, no idea why but i can almost instantly unlock certain mi phone's bootloader instantly. But a lot of thanx for taking your time and writing this up... You really saved me from being stuck in MIUI forever!
A lot of thnx.... and also happy new year... 1st day of 2020 went quite well for me all thnx to you and i hope yours goes well too.!
Robbo.5000 said:
Consider this an overkill solution that always works for me if I run into issues with other methods. It will wipe everything so backup your data and apps.
Download the latest fastboot Indian MIUI ROM (for anyone else reading this download the ROM that is the same region as your phone)
Fully extract the ROM and flash it - make sure, if you use the Mi Flash Tool, that you change the flash option to 'clean all'
Boot into MIUI once, you don't need to actually go through the set-up, just let it fully load.
Boot the phone into fastboot and install TWRP - I recommend the latest mauronofrio TWRP.
After installing TWRP boot immediately into TWRP.
Format the data partition - don't skip this step.
Wipe cache and dakvik - don't wipe anything else.
In TWRP goto the mount menu and unmount the data partition then mount it again - others would suggested rebooting back into TWRP, either way works, you just need to make sure the data partition is properly mounted after formatting it.
Install the ROM of your choice - either have the ROM on a USB OTG stick, or copy it onto the phone from a PC whilst still in TWRP.
If your ROM doesn't include Google apps and services and you want Google, then install GApps - at the time of writing this Android 10 GApps is still in beta and packages bigger than nano may cause issues, so stick with pico or nano, assuming your installing an Android 10 ROM.
Boot into the ROM.
If you want Magisk, once the ROM has loaded, boot back into TWRP and flash the latest Magisk installer - it is possible to flash Magisk without booting into the ROM first and you'll probably be OK, but occasionally it can cause problems, I can't remember the details, but for the sake of 30 seconds I now boot into the ROM before flashing, just to be on the safe side.
At the time of writing this people have recently reported issues flashing GApps immediately after flashing Havoc 3.0 and recommend booting Havoc before flashing GApps. Although others say they've not had any problems. So if you choose to install Havoc you 'might' have problems if you install GApps without booting into Havoc at least once first.
I've never had problems when following this method.
Click to expand...
Click to collapse
thanks for help
but no work for me
after flash rom and reboot booting to twrp auto..
Kollachi said:
Format data = (you will need to type in "yes")
Note: Format data or wipe data isn't the same thing.
Click to expand...
Click to collapse
many times the tiniest msg has the greatest significance. thanks mate!!!
Guys i need your help,, i flashed my phones custom Rom tecno 7cs using sp flashing tool.
That worked and it showed the tick icon on my pc.
The problem is that it does nothing to my phone because the software issues are still there
my phone keeps restarting itself almost all the time and sometimes won't even boot it takes longer to boot,,, apps keep on crushing and many more.AM tired am going to break it and throw it if i don't get solutions asap!
So the flashing process only wiped data on the phone nothing else whatsoever.
tecno 7cs p121 Bi safaricom ke 20151111