Someone have studies "Kexec" solution for locked bootloader ?
Kexec : http://en.wikipedia.org/wiki/Kexec
We keep our stock kernel with bootloader locked (not unlocked allowed), but at start (early), we run the kexec process witch kill in memory the stock kernel, and run custom kernel and custom rom
It's elegant, and like CWM process.
Someone have informations ?
Well, i answer myself.
Kexec need 2 parts to run.
1/ A patched stock kernel, or a patch for stock to be flashed by recovery.
This patch is needed to reinitialize CPU without a full memory scratch.
This is necessary to keep kexec alive in memory and finish to load new kernel.
A example of patch here : https://gist.github.com/Tasssadar/6687647
and here : https://gist.github.com/4558647
These patch are for S4Pro APQ8064 CPU
Config Option :
•CONFIG_KEXEC=y
•CONFIG_KEXEC_HARDBOOT=y
•CONFIG_ATAGS_PROC=y
•CONFIG_GROUPER_HARDBOOT_RECOVERY=n
2/ Kernel loader
It is a userspace binary.
The command to boot is :
kexec --load-hardboot zImage --initrd=initrd.img --mem-min=0x85000000 --command-line="$(cat /proc/cmdline)"
kexec -e
This binary "kexec" drop the memory from current stock kernel (even with a locked bootloader),
and load new kernel "initrd.img" to boot.
The command interpreter is called by command-line
To work, we need to dev a patch for stock current kernel.
The rest is easy... "just" modify a CWM to create userspace for kernels and roms on sdcard1, and the load option to boot onto
Please help us to found documentations
I think the devs will be more interested in making the camera work after an unlock.
DooMLoRD is working hard (As he always does for xperia devices) on making a recovery for LB, then I think he will spend time updating DooMKerneL to the same level as it is for other devices, then if he gets time he will work on Kexec, but he has said its low down on his todo list...
I'm waiting for a long time when you are able to load other kernel on my phone locked, if you find a solution I would be very grateful, I'm even willing donate for it
Google translator
I have the same Situation, and i would donate too
Mod Edit: closed per OP request
I'M NOT RESPONSIBLE FOR ANY DAMAGE AND/OR DATA LOSS AS A RESULT OF FLASHING THIS ROM !!!
PLEASE PERFORM FULL BACKUP IN THE MICRO SD CARD OR IN AN EXTERNAL STORAGE BEFORE YOU TRY !!!
Do you need reliability and predictability? Then better stay with THIS ROM
I have decided to create a separate thread because:
- I would like to distinguish PIE BETA bug reports from my normal (OREO stable) thread, mentioned above
- It is normal that there will be definitely much more "bad reports" here, because most of them will be "beta related"
This thread will be closed when Samsung will release stable Android Pie (One UI)
Everything you will need to know about DevBase ROM in general - you will find in my stable thread (mentioned above)
Differences comparing to stable Oreo DevBase ROM:
- No AppLock (yet)
- No Xposed (we need to wait for rovo89)
S9 (SM-G960F/DS/FD):
>> G960FXXU2ZRLF_DevBase_v6.0.RC8.zip << (updated Dec-19, more info in post #49)
Click to expand...
Click to collapse
S9+ (SM-G965F/DS/FD):
>> G965FXXU2ZRLF_DevBase_v6.0.RC8.zip << (updated Dec-19, more info in post #49)
Click to expand...
Click to collapse
Dirty flash over my Oreo DevBase ROM SHOULD WORK WITHOUT ISSUES but before you try - I would highly recommend you to set default (stock) theme and default (stock) icons !!! However - I would recommend you clean install (Wipe -> Swipe to Factory Reset is enough)
Known issues:
- [CLEAN INSTALL] Magisk Manager may not appear after clean install despite Magisk has been installed without errors during install - if you notice that there is no Magisk Manager - DO NOT flash Magisk, it is enough to (re)install Magisk Manager as normall app - use ATTACHMENT (it is original apk from Magisk v17.3)
- OEM unlock toggle seems to be disabled in the Developer Options but it is not true (otherwise you would not be able to use TWRP and this ROM). It is side effect of protection I put in the kernel against "KG State: Prenormal" in the DM mode. It is not real issue, just ignore it.
Thanks to:
- all users mentioned in my main thread
- @ASHLEY117 for G960F dumps
- @geiti94 who first provided me update.zip and dump for G965F
- @SoLdieR9312 for ZRKA update.zip for G960F containing BL/CP
I know nothing
Got no stones lol
Great work to you as well! ??
Just flashed the rom , clean install. Does not let me finish the setup screen because it is stating that a file has been removed ( regarding security or health ) in an unauthorized way . Not able to access anything after the setup screen only an option of emergency call is available.
bobandar said:
Just flashed the rom , clean install. Does not let me finish the setup screen because it is stating that a file has been removed ( regarding security or health ) in an unauthorized way . Not able to access anything after the setup screen only an option of emergency call is available.
Click to expand...
Click to collapse
No problem here (according to screenshots), but I have an idea... Please place attached options.prop file (decompress zip first) in the root directory of /sdcard or /external_sd and then try again
EDIT: Attachment removed! Please try updated ROM (r2) available in post #1. Please remove previously shared options.prop from /sdcard (/data/media/0) and/or from /external_sd before you try v.5.9_r2 !!!
_alexndr said:
No problem here (according to screenshots), but I have an idea... Please place attached options.prop file (decompress zip first) in the root directory of /sdcard or /external_sd and then try again
Click to expand...
Click to collapse
Will surely do and let you know.
This is what I had got earlier. Will try flashing now with the solution you gave.
nah mate, still getting the same problem
bobandar said:
nah mate, still getting the same problem
Click to expand...
Click to collapse
Still wondering how it is possible that for me it works...
Is there a person who managed it to work after clean install?
Thread has been updated. If you used options.prop file from post #4 - please remove it from /sdcard (/data/media/0) and/or from /external_sd before you try v.5.9_r2 !!!
Dirty flash. Working fine.
mevorach said:
Dirty flash. Working fine.
Click to expand...
Click to collapse
Which rom?
saxena1 said:
Which rom?
Click to expand...
Click to collapse
Coming from 5.9 j8 g965f
Samsung thems not working
mevorach said:
Coming from 5.9 j8 g965f
Samsung thems not working
Click to expand...
Click to collapse
They won't yet as its a Beta ROM. Stuff like that will be sorted out of Beta.
Hi,
I use ledcover, is it working with the beta ?
Thank you for your work.
Maglisr
Sent from my SM-G965F using XDA Labs
Gallery dose not present the photos from camera on sd card.
mevorach said:
Gallery dose not present the photos from camera on sd card.
Click to expand...
Click to collapse
Again, known bug in Samsung software. I'm running stock beta and have this problem
Due to the fact that I am still reading here and there with a high risk of FRP/RMM lock in Pie, the precise circumstances of which are still unknown - I have decided to upload v5.9_r3 which still contains Pie modem but does NOT contain Pie BL anymore.
Precise circumstances of FRP/RMM lock in Pie are unknown, but I believe that probability will be significantly reduced with Oreo BL (at least for those people who never flashed Pie BL yet) especially, that Pie beta seems to work well with Oreo bootloader & Pie modem.
>> G965FXXU2ZRKA_DevBase_v5.9_r3.zip << (updated Nov-22)
Click to expand...
Click to collapse
Advice for those who have Pie bootloader already - DON'T mess with it - let it be still Pie !!! Also - I would NOT recommend you to jump beetween Pie -> Oreo if it is not absolutely necessary! After several attempts of restoring Oreo ROM & BL, which passed successfully, then updating again to Pie ROM & BL, then restoring again... - unexpectedly, the problem has become to me (my device is RMM locked - I lost OEM unlock toggle for 7 days, I hope...)
At the moment we can confirm only 2 scenarios which should end without problems:
- Dirty flash Pie DevBase over Oreo DevBase (thanks to @mevorach for the try & report), but I would highly recommend you to set default (stock) theme and default (stock) icons before you try
- Clean flash (tested personally) but only if you never jumped beetween Pie -> Oreo in the past (no matter if it was clean downgrade or restoring Oreo backup)
IMO you should also assume following scenarios as risky:
- Jumping from Pie DevBase ROM -> SoLdieR9312's Pie ROM
- Jumping from SoLdieR9312's Pie ROM -> Pie DevBase ROM
EDIT: Vaultkeeper service has been removed from the kernel (starting from v5.9_r4). Should be more safe now, despite BL/CP are flashed again
So you don't suggest to switch over from SoLdieR9312's Pie ROM v1.1 to yours(dirty flash) & sdcard problem fixed v r3? I am on at
SoLdieR9312's Pie ROM v1.1.
saxena1 said:
So you don't suggest to switch over from SoLdieR9312's Pie ROM v1.1 to yours(dirty flash) & sdcard problem fixed v r3? I am on at
SoLdieR9312's Pie ROM v1.1.
Click to expand...
Click to collapse
Nothing has been changed in sdcard support comparing to stock beta - such kind of issues should be solved by Samsung.
IMHO if you are still on Oreo BL (never flashed Pie bootloader in the meantime) and never jumped Pie -> Oreo then should be OK after flashing r3 (r3 also does not contain Pie BL)
Please let us know if you decide to try
Flashing your 5.9 r2 , from oreo(j8) did not include the pie BL ?
Hi guys ! I have my k20 pro from 2019 and I never had access to any apps like netflix or mcdonals cause of some insecure software idrk to be honest. Anyways I want to use nfc and I actually can't . Did some research and just found out about eu rom might work but I'm new to this type of things and I need some help to flash the new rom and where to get it from .
These are some phone specs :
I have raphaelin ( aida64 )
K20pro 64 gb rom and 6gb ram
MIUI 12.0.5 Stable - Global rom
Model : M1903F11A
Kernel vers : 4. 14.117-perf-g97c1088
If someone can help I will be more than thankful !
My bootloader is unlocked btw but I don't have TWRP
where did u purchase your k20 pro from.
In India only 6-128 and 8-256 variants are there not 6-64 and also indian variant or model has no nfc.
As per phone codename raphaelin is indian device codename but how come u have 6-64gb model.
It doesn't matter whichever rom u install if ur device doesn't have nfc hardware it won't work and indian model has no nfc support...
I already found out it's 100% percent a Chinese device flashed with India rom. Now I need help to change it
OK, so just to clarify things to avoid future confusion.
Xiaomi label any MIUI version that is not Chinese as 'Global'. This is when you look in the about phone section and see MIUI x.y.z Global ROM. However this description covers 4 separate versions - India, EU/EEA, Russia and everywhere else (true Global).
In order to change region you need to flash the appropriate fastboot ROM. This is the official guide to flashing fastboot ROMs.
https://c.mi.com/oc/miuidownload/detail?guide=2
You will need to view the page in desktop mode on a mobile device, otherwise you'll just see a blank page.
The guide has download links for the latest versions for all devices, however it's probably easiest to find the ROM you want from here
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Select the EEA fastboot ROM.
WARNING
You can not lock the bootloader of a Chinese phone when flashing a non-Chinese ROM. Trying to do this will hard brick the phone. See this from the official forums.
https://c.mi.com/thread-2584760-1-0.html
WARNING
The Mi Flash Tool default flashing option is to flash the ROM and lock the bootloader. If you do not pay attention when flashing you could easily hard brick the phone.
The Mi Flash Tool runs batch scripts contained in the ROM to flash the ROM. The easiest way to avoid bricking the phone is to manually delete the batch script from the ROM before running the tool.
In order to flash the fastboot ROM, it needs to be fully extracted. After extracting it browse the contents of the extracted folder. You'll see a bunch of .bat and .sh files.
Delete the flash-all-lock.bat and flash-all-lock.sh files before doing anything else. (Names of the files might not be exact but you'll know which ones I mean when you see them).
When running the Mi Flash Tool, before hitting the flash button, change the option at the bottom of the app to 'clean all'. If you leave it on the default option and you've deleted the batch scripts above then you'll only get an error that it can't find the batch file.
So now after updating to the EU ROM, you'll have NFC working, but you are still going to have a bunch of issues with financial and tap to pay apps. The security problems you've seen so far have not been around insecure software, but because the bootloader is unlocked, and this is still going to cause you problems. There is something called the SafetyNet test, within android, which fails when run on phones with an unlocked bootloader. Apps that care about security will call the test and fail to run if it fails. To get around these issues you will need to install Magisk. Currently Magisk can spoof the test to give a positive result.
You'll also need to setup Magisk to hide itself from apps that perform security checks before launching, such as financial apps.
Only download Magisk from the official source.
GitHub - topjohnwu/Magisk: The Magic Mask for Android
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
You should find all the info needed to set up Magisk within the documentation links.
Hey guys,
as my last phone was an OPO where flashing custom roms was pretty simple, I don't understand the principle of flashing the Mi 9T Pro, where you always have to consider and install separately the right version of firmware, vendor etc. I would be thankful if someone could explain it to me.
I try to order my questions:
Why are ROM, firmware and vendor separated and don't come together in a single file?
How do I find out the correct version of firmware for my phone? And what is the difference between those versions, eg. China, Global and EU? And is EU the same as EEA?
The recommendation is always to update the firmware when flashing a ROM - but for vendor it is not (like for LineageOS 18.1) - why? Wouldn't it be beneficial to update vendor, too? As I understand, vendor contains necessary proprietary binaries.
Is it recommended to regularly update the firmware even if there is no update for my ROM? And what is the most comfortable way, is something like OTA possible?
What is different about TWRP images with a "_9"? (twrp-3.5.0_9-0-raphael.img vs. twrp-3.4.0-0 or -1). Recently broke the recovery of my OPO when I installed its latest twrp version which had the 9
Thank you for helping an interested person with little IT/android knowledge
oriped said:
Hey guys,
as my last phone was an OPO where flashing custom roms was pretty simple, I don't understand the principle of flashing the Mi 9T Pro, where you always have to consider and install separately the right version of firmware, vendor etc. I would be thankful if someone could explain it to me.
I try to order my questions:
Why are ROM, firmware and vendor separated and don't come together in a single file?
How do I find out the correct version of firmware for my phone? And what is the difference between those versions, eg. China, Global and EU? And is EU the same as EEA?
The recommendation is always to update the firmware when flashing a ROM - but for vendor it is not (like for LineageOS 18.1) - why? Wouldn't it be beneficial to update vendor, too? As I understand, vendor contains necessary proprietary binaries.
Is it recommended to regularly update the firmware even if there is no update for my ROM? And what is the most comfortable way, is something like OTA possible?
What is different about TWRP images with a "_9"? (twrp-3.5.0_9-0-raphael.img vs. twrp-3.4.0-0 or -1). Recently broke the recovery of my OPO when I installed its latest twrp version which had the 9
Thank you for helping an interested person with little IT/android knowledge
Click to expand...
Click to collapse
If you stick with stock ROMs, you don't need to worry anout firmware, vendor, etc.
You update by OTA or by downloading the so-called zip/recovery package that can be installed by the stock recovery or from TWRP
Only in rare occasions (usually when people screw something, want to go back from custom ROMs and so), you would need Xiaomi Flash tool and the so-called tgz/fastboot packages.
They include vendor and again, you don't need to worry about downloading and flashing vendor
How (and do you really) need downloading and flashing vendor for LOS, I have no idea (I don't use AOSP ROMs)
What do you mean by Eu?
If you mean Xoaomi.eu ROMs - they are not the same as stock EEA ROMs.
Actually, Xiaomi.eu IS NOT stock or even not an official ROM endorsed by Xiaomi Inc.
Personally, I started on my Mi 9T two years ago with A9/MIUI 10 (I think). Mine was EEA and I followed the updates till A10/MIUI 11.
From the beginning I unlocked Bootloader, played with various versions and incarnations of TWRP, I always rooted my phone with the latest (Canary) Magisk, played with debloating, various Magisk modules, etc.
I also played with Kali Nethunter at the time
Never in my carrier I needed to use Xiaomi Flash tool and tgz/fastboot firmwares (specially not vendor packages), always only zip/recovery ROM packages were enough for me
A year ago I moved to Xiaomi.eu weeklies. A month ago I decided it was enough and settled to Xiaomi.eu but Stable.
Xiaomi.eu, both weeklies and stable are built on A11/MIUI 12.5 (recently stock was finally also updated to A11/MIUI 12+ but I didn't return to stock)
Since 'official' Magisk is kind of 'dead' for 5 or so months, for the last two months I play with Magisk Alpha (recently incl. Zygisk and so)
Again, I have no experience (and no interests at all) about AOSP and GSI ROMs, particularly the LOS (in my past life with another phone, I used an earlier version of LOS for quite some time there)
Some links maybe of interest for you to read/learn from:
https://c.mi.com/thread-1857937-1-1.html
How to Flash Xiaomi Firmware using MIUI Fastboot and Recovery ROM
Ever since the dawn of affordable smartphones in countries like India and China, the demand for more has increased. The consumers now, more than ever, are
www.getdroidtips.com
How-to use Xiaomi Flash Tool to flash or install Firmware
Step-by-Step guidelines to use Xiaomi Flash Tool to Flash Stock Firmware on Xiaomi Smartphone and Tablets.
xiaomiflashtool.com
Xiaomi's Anti-Rollback Protection Explained: How to avoid bricking your phone
All Xiaomi smartphones and tablets will have anti-rollback protection enabled. What is it and how do you avoid bricking your device because of it?
www.xda-developers.com
[INFO] Widevine L1 Support
This thread should answer most of your questions regarding Widevine L1 support on your device(s). I will try to keep it maintained and up-to-date. Notes: * This list includes only supported Android 10+ devices that either support Widevine L1 officially, or support it unofficially by Xiaomi.eu...
xiaomi.eu
What the letters in the MIUI version designation mean
MIUI V12.0.5.0. QFJMIXM - Android version M - Android 6.x (Marshmallow) N - Android 7.x (nugát) O - Android 8.x (Oreo) P - Android 9.x (Pie) Q - Android 10.x R - Android 11.x S - Android 12.x - device code (phone model) JA - Xiaomi Mi 10 Pro JB - Xiaomi Mi 10 JC - Redmi 9 JO - Redmi Note 9 JZ...
xiaomi.eu
PS: Yeah, I am from Mi 9T (not Pro) world, but your questions and my comments and links are common and more general (not limited to Mi 9T Pro or plain, or to MI 9 *** range of models, but general for Xiaomi devices)
But if you meant EU letters in the stock ROM name - then yes, EU means European and that is EEA stock ROM
Similarly like MI letters (probably abbreviated from MIUI) in the stock ROM name mean International - see the attachement
Btw, this app might be also useful (not only for newbies):
MIUI Downloader - Apps on Google Play
MIUI upgrade app for Mi users.
play.google.com
Open your Settings/My Device/MIUI Version (top left), aka System Updater app, read the full name of your stock ROM and compare against the attached chart
Thank you!
One more question: How do I change magisk to vvb2060 alpha version?
oriped said:
Thank you!
One more question: How do I change magisk to vvb2060 alpha version?
Click to expand...
Click to collapse
His Github page where you can download the 'latest official' Alpha:
GitHub - vvb2060/magisk_files
Contribute to vvb2060/magisk_files development by creating an account on GitHub.
github.com
Newer, unofficial (I'm on the latest) can be downloaded here:
Magisk alpha
带遥测的第三方Magisk版本，比Canary通道更加不稳定，与上游行为有较大不同，无安全性保证，无可用性保证，无隐私协议。 问题反馈请加群发送日志文件，非alpha独有问题建议先在GitHub反馈。
t.me
You download and install Magisk (Alpha) apk (formerly, in Magisk v22 it was Magisk mngr)
If you are already rooted, you can take then Direct install to 'upgrade' to the same Magisk Alpha version
If you were not rooted yet, you can patch your boot.img (it can be extracted from your zip/recovery or tgz/fastboot stock ROM), later you will flash that patched img by Fastboot.
Instead of boot.img, you can patch boot.emmc.win Boot backup from TWRP
You can also rename magisk apk file (that Magisk Alpha app you downloaded) to install.zip and flash through TWRP (old school for those who are accustomed to flash Magisk zip through TWRP).
If you have the latest 3.5.-9 official TWRP, you don't even need to rename, you can flash as it was downloaded as magisk apk file
But be aware that Magisk Alpha has no more MagiskHide, instead it is now DenyList.
And configuring DenyList to pass SafetyNet is another (short) story
zgfg said:
If you stick with stock ROMs, you don't need to worry anout firmware, vendor, etc.
You update by OTA or by downloading the so-called zip/recovery package that can be installed by the stock recovery or from TWRP
Only in rare occasions (usually when people screw something, want to go back from custom ROMs and so), you would need Xiaomi Flash tool and the so-called tgz/fastboot packages.
They include vendor and again, you don't need to worry about downloading and flashing vendor
How (and do you really) need downloading and flashing vendor for LOS, I have no idea (I don't use AOSP ROMs)
What do you mean by Eu?
If you mean Xoaomi.eu ROMs - they are not the same as stock EEA ROMs.
Actually, Xiaomi.eu IS NOT stock or even not an official ROM endorsed by Xiaomi Inc.
Personally, I started on my Mi 9T two years ago with A9/MIUI 10 (I think). Mine was EEA and I followed the updates till A10/MIUI 11.
From the beginning I unlocked Bootloader, played with various versions and incarnations of TWRP, I always rooted my phone with the latest (Canary) Magisk, played with debloating, various Magisk modules, etc.
I also played with Kali Nethunter at the time
Never in my carrier I needed to use Xiaomi Flash tool and tgz/fastboot firmwares (specially not vendor packages), always only zip/recovery ROM packages were enough for me
A year ago I moved to Xiaomi.eu weeklies. A month ago I decided it was enough and settled to Xiaomi.eu but Stable.
Xiaomi.eu, both weeklies and stable are built on A11/MIUI 12.5 (recently stock was finally also updated to A11/MIUI 12+ but I didn't return to stock)
Since 'official' Magisk is kind of 'dead' for 5 or so months, for the last two months I play with Magisk Alpha (recently incl. Zygisk and so)
Again, I have no experience (and no interests at all) about AOSP and GSI ROMs, particularly the LOS (in my past life with another phone, I used an earlier version of LOS for quite some time there)
Some links maybe of interest for you to read/learn from:
https://c.mi.com/thread-1857937-1-1.html
How to Flash Xiaomi Firmware using MIUI Fastboot and Recovery ROM
Ever since the dawn of affordable smartphones in countries like India and China, the demand for more has increased. The consumers now, more than ever, are
www.getdroidtips.com
How-to use Xiaomi Flash Tool to flash or install Firmware
Step-by-Step guidelines to use Xiaomi Flash Tool to Flash Stock Firmware on Xiaomi Smartphone and Tablets.
xiaomiflashtool.com
Xiaomi's Anti-Rollback Protection Explained: How to avoid bricking your phone
All Xiaomi smartphones and tablets will have anti-rollback protection enabled. What is it and how do you avoid bricking your device because of it?
www.xda-developers.com
[INFO] Widevine L1 Support
This thread should answer most of your questions regarding Widevine L1 support on your device(s). I will try to keep it maintained and up-to-date. Notes: * This list includes only supported Android 10+ devices that either support Widevine L1 officially, or support it unofficially by Xiaomi.eu...
xiaomi.eu
What the letters in the MIUI version designation mean
MIUI V12.0.5.0. QFJMIXM - Android version M - Android 6.x (Marshmallow) N - Android 7.x (nugát) O - Android 8.x (Oreo) P - Android 9.x (Pie) Q - Android 10.x R - Android 11.x S - Android 12.x - device code (phone model) JA - Xiaomi Mi 10 Pro JB - Xiaomi Mi 10 JC - Redmi 9 JO - Redmi Note 9 JZ...
xiaomi.eu
PS: Yeah, I am from Mi 9T (not Pro) world, but your questions and my comments and links are common and more general (not limited to Mi 9T Pro or plain, or to MI 9 *** range of models, but general for Xiaomi devices)
Click to expand...
Click to collapse
Hi I'm K20pro/Mi 9t pro user currently on latest 12.5.1.0 raphael stock rom, can you give bit of advice about going to eu stable rom(12.5.6.0 latest) from stock miui. I do have orange fox recovery installed but confused about what to wipe(dalvik/cache/...other options) or format data(yes confirmation option) and if rom flash needs to be in clean internal storage via format data(yes confirmation option), will i need latest firmware with it or just eu rom.
After that i will install magisk
I'm pretty much new custom roms with just a week of 35-40 hours of research, I will be glad if you or anyone reading this, willing to clear my doubts.
Thank you in advance
jacksterky said:
Hi I'm K20pro/Mi 9t pro user currently on latest 12.5.1.0 raphael stock rom, can you give bit of advice about going to eu stable rom(12.5.6.0 latest) from stock miui. I do have orange fox recovery installed but confused about what to wipe(dalvik/cache/...other options) or format data(yes confirmation option) and if rom flash needs to be in clean internal storage via format data(yes confirmation option), will i need latest firmware with it or just eu rom.
After that i will install magisk
I'm pretty much new custom roms with just a week of 35-40 hours of research, I will be glad if you or anyone reading this, willing to clear my doubts.
Thank you in advance
Click to expand...
Click to collapse
When switching to Xiaomi.eu (and generally when switching the ROMs) it's required to Format Data (not just to Wipe Data - fornatting does more than wiping)
More about downloading and installing Xiaomi.eu ROMs find on their forum, in the OP posts:
MIUI 12.0 - MIUI 12.0/12.1/12.2/12.5 STABLE RELEASE
STABLE RELEASE RULES WHEN POSTING 1. If a ROM is not published DONT ASK ABOUT ITS ETA 2. If a ROM is not published DONT ASK why! 3. If a ROM is available, download it and use it 4. If a ROM has bugs, post the bug to the bug section if the BUG is not already listed 5. If you use any form of...
xiaomi.eu
Better also Wipe Cache (Dalwik will be wiped as part of Data partition hence you can wipe it too but it won't matter)
You can use OF but make sure you use a recent/latest version, or use the latest official TWRP. More about the suitable custom recoveries can be found in the Forum/thread as above
Generally:
- backup your photos, docs, etc (transfer to PC)
- use Google to backup, some apps like Whatsapp provide backing up to clouds, etc
- With Xiaomi Cloud you can backup installed apps and their settings, Contacts, Call History, SMS, even WiFi passwords
- Download the ROM to Internal memory
- reboot to OF/TWRP and install (flash) the downloaded zip
- Wipe Dalwik and Cache (TWRP automatically offers upon installing)
- Do not reboot to System but go back in OF/TWRP and do Format Data (do not Format Data before flashing the zip because Formatting Data will wipe your Internal memory, hence it would also wipe your downloaded zip - although you could, but then flash the zip from OTG stick)
Then reboot to System, setup your new Android/MIUI, restore things...
zgfg said:
When switching to Xiaomi.eu (and generally when switching the ROMs) it's required to Format Data (not just to Wipe Data - fornatting does more than wiping)
More info about downloading and installing Xiaomi.eu ROMs find on their forum, in the OP posts:
MIUI 12.0 - MIUI 12.0/12.1/12.2/12.5 STABLE RELEASE
STABLE RELEASE RULES WHEN POSTING 1. If a ROM is not published DONT ASK ABOUT ITS ETA 2. If a ROM is not published DONT ASK why! 3. If a ROM is available, download it and use it 4. If a ROM has bugs, post the bug to the bug section if the BUG is not already listed 5. If you use any form of...
xiaomi.eu
Better also Wipe Cache (Dalwik will be wiped as part of Data partition hence you can wipe it too but it won't matter)
You can use OF but make sure you use a recent/latest version, or use the latest official TWRP. More about suitable custom recoveries can be found on the Forum/thread as above
Generally:
- backup your photos, docs, etc (transfer to PC)
- use Google to backup, some apps like Whatsapp provide backing up to clouds, etc
- With Xiaomi Cloud you can backup installed apps and their settings, Contacts, Call History, SMS, even WiFi passwords
- Download the ROM to Internal memory
- reboot to OF/TWRP and install (flash) the downloaded zip
- Wipe Dalwik and Cache (TWRP automatically offers upon installing)
- Do not reboot to System but go back in OF/TWRP and do Format Data (do not Format Data before flashing the zip because Formatting Data will wipe your Internal memory, hence it would also wipe your downloaded zip - although you could, but then flash the zip from OTG stick)
Then reboot to System, setup your new Android/MIUI, restore things...
Click to expand...
Click to collapse
I'll follow your instructions step by step.
Again thank you for your quick support, really appreciate your help
jacksterky said:
I'll follow your instructions step by step.
Again thank you for your quick support, really appreciate your help
Click to expand...
Click to collapse
Do not wipe any other partition, specially not Persist (you would loose DRM L1), modem, and so on.
Since you are on stock, all that is good and Xiaomi.eu will actually flash only to System and Vendor
You probably use pin or pattern for screen unlocking, you will need to enter the same when you boot to OF/TWRP that it can read Internal memory (later, when you Format Data it will be gone and you will have to setup your pin/pattern again once you boot to your new System)
First time you boot to the new System give it some time (might be slow at first, doing things in the background)
Xiaomi.eu 'hides' that Bootloader is unlocked, hence you will pass SafetyNet (i e., Device will be certified in Playstore) right away
You will also have DRM L1 (you may need to download the certificate, but that's easy)
When you later need to reboot to OF/TWRP, you don't need to struggle with key combos - in Xiaomi.eu, from System updater, when you open the top-right menu, you have Reboot to recovery option (root not needed)
Later you can think about rooting with Magisk, installing nodules, additionally debloating, etc
Be aware that raphael is on the end-of-line and it's not clear would it receive any more Xiaomi.eu updates (or if, then just a newer Security Patch).
But that's also the case with stock
zgfg said:
Do not wipe any other partition, specially not Persist (you would loose DRM L1), modem, and so on.
Since you are on stock, all that is good and Xiaomi.eu will actually flash only to System and Vendor
You probably use pin or pattern for screen unlocking, you will need to enter the same when you boot to OF/TWRP that it can read Internal memory (later, when you Format Data it will be gone and you will have to setup your pin/pattern again once you boot to your new System)
First time you boot to the new System give it some time (might be slow at first, doing things in the background)
Xiaomi.eu 'hides' that Bootloader is unlocked, hence you will pass SafetyNet (i e., Device will be certified in Playstore) right away
You will also have DRM L1 (you may need to download the certificate, but that's easy)
When you later need to reboot to OF/TWRP, you don't need to struggle with key combos - in Xiaomi.eu, from System updater, when you open the top-right menu, you have Reboot to recovery option (root not needed)
Later you can think about rooting with Magisk, installing nodules, additionally debloating, etc
Be aware that raphael is on the end-of-line and it's not clear would it receive any more Xiaomi.eu updates (or if, then just a newer Security Patch).
But that's also the case with stock
Click to expand...
Click to collapse
Okay i'll follow your given directions, I'll update you after installation, Thank you
I'm now on latest weekly build on eu rom, and it's butter smooth and i know this might be the last beta version for the raphael but experience is just flawless and new features work perfectly fine, again thanks for your instructions i'll remember them for future installations.
jacksterky said:
I'm now on latest weekly build on eu rom, and it's butter smooth and i know this might be the last beta version for the raphael but experience is just flawless and new features work perfectly fine, again thanks for your instructions i'll remember them for future installations.
Click to expand...
Click to collapse
Doesn't matter if it's last Weekly as long as you are satisfied with.
Btw, I thought you'd be little more conservative and go for Stable, but probably differences are minor
Stable is MIUI 12.6 (also A11) with Security patch Oct 1 - what are your parameters?
Also, check Widewine L1 certificate and update if neccessary:
Settings / Passwords and security / Fingerprint unlock / Fingerprint payments
Check do you have Widevine L1 cert.
If necessary, take Certificate update
Btw, you are ready now for Magisk, AdAway, Vanced YT, Viper4Android, CustoMIUIzer and so