Seems like Xiaomi has started rolling out Stable beta for K20 Pro.
Recovery ROM - http://bigota.d.miui.com/V12.0.0.8.QFKMIXM/miui_RAPHAELGlobal_V12.0.0.8.QFKMIXM_7b969a8eda_10.0.zip
oof
They rolled it out like more than a week ago, but only for testers. If you flashed that and you aren't in the program you won't be getting updates (it's not like they released any anyways). Also, it's pretty much a bugfest, China closed beta is much more stable.
Beta and stable are contradictory don't you think?
It's either one or the other.
so, is it beta or stable?
Catsonvi said:
They rolled it out like more than a week ago, but only for testers. If you flashed that and you aren't in the program you won't be getting updates (it's not like they released any anyways). Also, it's pretty much a bugfest, China closed beta is much more stable.
Click to expand...
Click to collapse
Actually I figured it out later but was curious to know why XDA and GSMARENA featured these builds in their articles on 3rd June when the same were already available on 25th May.,
deta312 said:
so, is it beta or stable?
Click to expand...
Click to collapse
They(XDA, GSMARENA) are calling it Stable Beta...Ironed out the bugs from early Beta releases it seems.
This is not stable. It's full of issues. Even YouTube's picture in picture feature is broken.
I am now on MIUI 10 version, can I switch directly to MIUI12?
Help!
I have a European Mi 9t Pro and have just flashed the Global (stable ) MIUI12 rom.
So far so good, it works... but I am now unable to access extended power menu options (aka Recovery Reboot).
The option has also disappeared from the MIUI update settings.
And performing the VolumeDown+Power boot only gets me to a minimal menu with 3 options: reboot to system / wipe / connect with MIAssistant.
I tried using ADB tools to re-flash TWRP to no avail.
The fastboot flash recovery twrp.img command works fine, I get the expected successful output.
But then the fastboot boot twrp.img command returns a "no such file or directory" error.
What can I do? T_T
Issues with 12
The floating windows work only when they pop up. There's no button (there's only one for split screen) or mini list in task list. Pick up to activate front camera unlock doesn't work.
Is there a known issues list so i can check if it's specific to my device or just a known bug?
Hasimir said:
Help!
I have a European Mi 9t Pro and have just flashed the Global (stable ) MIUI12 rom.
So far so good, it works... but I am now unable to access extended power menu options (aka Recovery Reboot).
The option has also disappeared from the MIUI update settings.
And performing the VolumeDown+Power boot only gets me to a minimal menu with 3 options: reboot to system / wipe / connect with MIAssistant.
I tried using ADB tools to re-flash TWRP to no avail.
The fastboot flash recovery twrp.img command works fine, I get the expected successful output.
But then the fastboot boot twrp.img command returns a "no such file or directory" error.
What can I do? T_T
Click to expand...
Click to collapse
Those 3 options mean that you are in MIUI Recovery. When flashing official Xiaomi ROMs your custom recovery will always be replaced with the stock one. As for the error, try placing twrp.img into the adb folder and specify the location as in fastboot boot C:\adb\twrp.img.
Also, if you already managed to flash TWRP why don't you just boot into it with Vol+ and power button?
Related
I have the Redmi note 3 pro 2gb snapdragon version I have unlocked my bootloader officially. I cannot seem to be able to root/flash recovery onto my phone.
I tried the Miui India toolkit - I get an error message: error unhandled exception has occurred in your application blah blah blah Could not find file c:\1.txt
I tried following this guide, and it worked once but it also broke Wifi - wifi refused to turn on
http://xiaomitips.com/guide/root-redmi-note-3-snapdragon/
I'm on Global Stable 7.1.8.0. I've tried the China rom and Global 7.2.3.0 but both roms are much worse on my phone - I no longer get notifications from my messaging apps, Blackplayer keeps stopping and restarting from the very first song it started playing, and other random bugs
Any help would be greatly appreciated, thank you
pyro224 said:
I have the Redmi note 3 pro 2gb snapdragon version I have unlocked my bootloader officially. I cannot seem to be able to root/flash recovery onto my phone.
I tried the Miui India toolkit - I get an error message: error unhandled exception has occurred in your application blah blah blah Could not find file c:\1.txt
I tried following this guide, and it worked once but it also broke Wifi - wifi refused to turn on
http://xiaomitips.com/guide/root-redmi-note-3-snapdragon/
I'm on Global Stable 7.1.8.0. I've tried the China rom and Global 7.2.3.0 but both roms are much worse on my phone - I no longer get notifications from my messaging apps, Blackplayer keeps stopping and restarting from the very first song it started playing, and other random bugs
Any help would be greatly appreciated, thank you
Click to expand...
Click to collapse
You unlocked your bootloader on stable ROM? Are you sure? According to this post it doesn't work on stable and it didn't work for me (same model).
Check it in fastboot (power off device and boot by holding Power + Vol Down):
1. Connect your RN3 SD to PC
2. Open cmd.exe and change to your ADB/fastboot folder with "cd <X:\myADBandFASTBOOTfolder\>" (replace with whereever fastboot.exe is located)
3. Check the connection with "fastboot devices". It should show something, meaning that your PC recognizes your device being connected through fastboot.
4. Enter "fastboot oem device-info". The line where it says "Device unlocked:" should be "true". If not, your bootloader is still locked.
Anyway, I suggest going to an official Developer Version (if you are on Global Stable, install Global Dev; China Stable -> China Dev). IMPORTANT: Search through forums, if an OTA update is safe to do, when your bootloader is unlocked. It might (!) lock it again, meaning you have to wait again, since Xiaomi only allows one unlock a month per device.
When you are on Dev ROM with bootloader unlocked, follow this guide to flash TWRP and patch the boot.img (important, so it doesn't replace TWRP with stock recovery again after the next boot). Go into recovery (Power + Vol Up) immediately after flashing TWRP, without rebooting to system. If TWRP is in Chinese, check out my comment here on how to fix it.
After successful installation of TWRP make sure that it's permanent (reboot the device at least twice and enter TWRP again). If that is the case you can search for the latest SuperSU.zip and flash it through TWRP which should give you root.
Hope this helps.
Immortal68 said:
You unlocked your bootloader on stable ROM? Are you sure? According to this post it doesn't work on stable and it didn't work for me (same model).
Check it in fastboot (power off device and boot by holding Power + Vol Down):
1. Connect your RN3 SD to PC
2. Open cmd.exe and change to your ADB/fastboot folder with "cd <X:\myADBandFASTBOOTfolder\>" (replace with whereever fastboot.exe is located)
3. Check the connection with "fastboot devices". It should show something, meaning that your PC recognizes your device being connected through fastboot.
4. Enter "fastboot oem device-info". The line where it says "Device unlocked:" should be "true". If not, your bootloader is still locked.
Anyway, I suggest going to an official Developer Version (if you are on Global Stable, install Global Dev; China Stable -> China Dev). IMPORTANT: Search through forums, if an OTA update is safe to do, when your bootloader is unlocked. It might (!) lock it again, meaning you have to wait again, since Xiaomi only allows one unlock a month per device.
When you are on Dev ROM with bootloader unlocked, follow this guide to flash TWRP and patch the boot.img (important, so it doesn't replace TWRP with stock recovery again after the next boot). Go into recovery (Power + Vol Up) immediately after flashing TWRP, without rebooting to system. If TWRP is in Chinese, check out my comment here on how to fix it.
After successful installation of TWRP make sure that it's permanent (reboot the device at least twice and enter TWRP again). If that is the case you can search for the latest SuperSU.zip and flash it through TWRP which should give you root.
Hope this helps.
Click to expand...
Click to collapse
Hello
Sorry to rephrase: I flashed to China Dev rom via MiFlash and unlocked the bootloader offically, however this rom had odd errors and bugs so I went back to the older Global Stable. My understanding is that the bootloader is now unlocked regardless of what ROM i am running?
In the guide you linked, the OP mentione "no patched boot.img required" yet you recommend I patch the boot.img? Can you advise how I should do this?
pyro224 said:
Hello
Sorry to rephrase: I flashed to China Dev rom via MiFlash and unlocked the bootloader offically, however this rom had odd errors and bugs so I went back to the older Global Stable. My understanding is that the bootloader is now unlocked regardless of what ROM i am running?
In the guide you linked, the OP mentione "no patched boot.img required" yet you recommend I patch the boot.img? Can you advise how I should do this?
Click to expand...
Click to collapse
I think going from China Dev to Global Stable is giving you troubles. Since you already flashed another Official ROM after unlocking the bootloader I don't think it would make matters worse if you did it again now. Try flashing the official Global Dev Qualcom http://en.miui.com/download-301.html and check again if your bootloader is unlocked through the method I posted. After that - if it's still unlocked - you should be able to follow through with the guide.
Right, the boot.img is patched automatically through TWRP when you enter and exit it. Just flash the recovery and confirm overwriting files, so it doesn't go back to stock, when you exit TWRP. You should get a notification when you try to rebbot to system through TWRP.
Just as an update - I was able to flash Cofface's recovery on Global Stable 7.1.8.0 (since my phone refused to update me to any other rom) using the provided guide http://forum.xda-developers.com/redmi-note-3/development/recovery-kenzotwrp-cafface-3-0-0-t3369341
Hi guys,
I've purchased a Redmi 5 Plus (MEG7) as my new backup phone (2nd hand). The Mi account of the previous owner is still bound to the device, but the phone did shut down on the way (ran out of juice) and never came back. In other words it is stuck in a bootloop at the android screen.
What I already did:
Used Xiaomi ADB to sideload both global stable and global developer roms (not to mention most of the past global developer roms and some china stable/developer roms), no love.
Unlocking the bootloader didn't work either, since I can't add my account to the phone.
The test point method was able to deliver a clear flash (tried China stable, China developer, Global stable and Global developer roms and most of the past relevant roms, you get the idea) with and without persist.img edit.
Tweaking fastboot ROMs with TWRP as recovery.img, still nothing.
I'm open to any new bright ideas besides going to a Mi Center or any other "Let the store fix it" suggestion.
Thanks
exigon said:
... I'm open to any new bright ideas besides going to a Mi Center or any other "Let the store fix it" suggestion ...
Click to expand...
Click to collapse
Have you tried installing a custom ROM - eg AOSP/LOS based?
I'd like to
DarthJabba9 said:
Have you tried installing a custom ROM - eg AOSP/LOS based?
Click to expand...
Click to collapse
That's what I'd like to do in the end, but since I have a locked bootloader, xiaomi's gorgeous beast of a recovery and no way to bind my account without entering the system, it's pretty much a stalemate.
If there was another fastboot rom besides MIUI, I'd love to try it.
https://forum.xda-developers.com/re...fastboot-rom9008-edlh2osbeta19-vince-t3890747 this resulted in a MiFlash error message.
exigon said:
That's what I'd like to do in the end, but since I have a locked bootloader, xiaomi's gorgeous beast of a recovery and no way to bind my account without entering the system, it's pretty much a stalemate.
Click to expand...
Click to collapse
Did you try to flash a stock Xiaomi fastboot ROM with the mi flash tool?
yes
DarthJabba9 said:
Did you try to flash a stock Xiaomi fastboot ROM with the mi flash tool?
Click to expand...
Click to collapse
Flashing the fastboot stock stable global and fastboot stock developer roms was the first thing I did, with a bootloop as the result.
exigon said:
Flashing the fastboot stock stable global and fastboot stock developer roms was the first thing I did, with a bootloop as the result.
Click to expand...
Click to collapse
Hmm ... if flashing with the mi flash tool gives you a bootloop, then I think something is seriously amiss. Unfortunately, I am out of ideas.
exigon said:
Hi guys,
I've purchased a Redmi 5 Plus (MEG7) as my new backup phone (2nd hand). The Mi account of the previous owner is still bound to the device, but the phone did shut down on the way (ran out of juice) and never came back. In other words it is stuck in a bootloop at the android screen.
What I already did:
Used Xiaomi ADB to sideload both global stable and global developer roms (not to mention most of the past global developer roms and some china stable/developer roms), no love.
Unlocking the bootloader didn't work either, since I can't add my account to the phone.
The test point method was able to deliver a clear flash (tried China stable, China developer, Global stable and Global developer roms and most of the past relevant roms, you get the idea) with and without persist.img edit.
Tweaking fastboot ROMs with TWRP as recovery.img, still nothing.
I'm open to any new bright ideas besides going to a Mi Center or any other "Let the store fix it" suggestion.
Thanks
Click to expand...
Click to collapse
You have a serious problem here cause if you flash succesfully any miui rom then Xiaomi will ask for the password to the last account binded.
I guess that the one method to bypass this is using some box/dongle in a service center by formatting eMMc, if you are now the new owner this action will be fine.
There´s only one thing that forgot to do trying to install a custom rom when my R5+ was locked yet. A short history first: some older Xiaomi devices as one that I had as a second device; Mi Max(2016) accepted to replace TWRP instead of stock recovery and flashing it through MiFlash tool without any problem but newer devices will refuse to boot.
I don´t know if this work, maybe bootloader redirects to fastboot mode instead of try to boot but anyway; Rename TWRP.img as boot.img (not recovery.img) and replace for the boot.img in the fasboot rom folder, after of flash try to reboot normally.
The message is not working, for now, I am not sure if this was caused by version turning.
Be careful！
---
I have been using Mi8 Global beta for a long time. Sadly mi8 don't update beta anymore, I decide to switch to stable version.
I was so disappointed that xiaomi even did not offer any method for beta users to switch to the stable version
The official way needs to erase all my data, sorry but I can't do all the settings again.
I tried the same thing before, switch to beta from stable, this trick still works for me this time, so I post here if someone needs it, here are the steps:
(Bootloader must be unlocked)
1. get lastest twrp boot.img from https://twrp.me/
2. reboot to fastboot, using fastboot to flash twrp recovery
3. reboot to recovery, don't reboot to system or you will lost twrp.
4. get lastest stable ROM, flash with twrp
5. reboot(if not working, flash stock boot.img)
Nothing wried happen, for now, the animation is smooth, no app is broken...
I get the lasted rom from https://forum.xda-developers.com/mi-8/how-to/xiaomi-mi8-global-stable-miui-10-1-1-0-t3875526
version: V10.3.3.0 (PIE)
Personally, I prefer official rom for more stable experiences...
So far did you face any issue
I might flash stable from beta too
Hellboy4 said:
So far did you face any issue
I might flash stable from beta too
Click to expand...
Click to collapse
Beta-->Stable
Stable-->Beta
Nothing wrong so far.
jaysir said:
Beta-->Stable
Stable-->Beta
Nothing wrong so far.
Click to expand...
Click to collapse
Nice. I will change to stable then
Hi,
My favourite phone is the Xiaomi Redmi note 3 Pro SE with Lineage OS 13 (Yes marshmallow).
I got a new one that was in endless bootloop and I planned to get it working.
I don't know if the bootloader has been unlocked and how (last time I checked it was written locked), if a custom ROM as been flashed or anything that could been done on it before I get it.
After many tries I first succeed to install LineageOs 13 on it, what I remember:
I go to fastboot mode
I go to edl mode
I flashed it with an old MiFlash 2016.04.01.0 64 bit with an old official ROM : kate_global_images_6.9.29_20160805.0000.29_6.0_global_9aa2d85137 with recovery.img replaced by an old ZXC-TWRP 3.0.2-X. (This is the way to get a recovery with no need to unlock bootloader)
I started it directly to TWRP recovery mode (to be sure TWRP will stay it I guess?) changed the language and checked OTA checkbox in parameters
I started this old official ROM once (to get the full storage capacity)
I discovered it was a 16GB ROM / 2GB RAM version instead a 32GBROM / 3GB RAM I previously knowed
I restarted to TWRP recovery mode
I wiped david/cache
I flashed the last knowed LineageOS 13 for this phone: https://forum.xda-developers.com/re...ageos-13-0-t3533744/post83687823#post83687823
I wiped david/cache
I flashed the last radeon kerned on it
I wiped david/cache
I restarted it to LineageOS 13
I restarted to TWRP recovery mode, changed the language and checked OTA checkbox in parameters
I flashed magisk (sytemless)
I wiped david/cache
I restarted it to LineageOS 13
I could use it install a lot of things, was happy with it
Before succeeding I tried a lot of combinations of official ROM/TWRP/MiFlash versions and this couple was the only one working.
Other MiFlash versions don't detect the phone in edl mode
But 2 weeks later, just after installing a new app, the phone sudently reboots and I got stuck in bootloop again...
I could go to recovery one time, I selected reboot system, now I can't go to recovery anymore
I still can go to fastboot mode and edl mode, and I can flash a ROM, but whatever I flash I can't go away from bootloop.
What could the new bootloop come from?
Is my installation sequence good?
Why only this combination of official ROM/TWRP/MiFlash versions was working?
Why can't I start a ROM anymore after a new flash?
Why can't I go to the recovery anymore after a new flash?
How to check if the emmc memory is defective (I got no error while flashing)?
Thanks for reading, hope someone still cares on this old great phone
Sorry for my bad English
No clue what the problem may be. What app did you install? You could always try to go back to stock if you haven't already. Basically wipe phone completely and flash stock through mi flash.
JD. A said:
No clue what the problem may be. What app did you install? You could always try to go back to stock if you haven't already. Basically wipe phone completely and flash stock through mi flash.
Click to expand...
Click to collapse
Thanks for your answer.
The last app before bootloop was a sms/mms backup app on google store I get through Aurora.
I tried to flash the stock ROM (old one) kate_global_images_6.9.29_20160805.0000.29_6.0_glo bal_9aa2d85137 but it doesn't start, always bootloop.
I have no option to wipe on the only miflash version that detect my phone in edl : the 2016.04.01.0 64 bit version. so I choose flash all data/storage include, but still bootloop.
Why are you using such a old rom? Use latest miflash and latest global. On the bottom right of miflash you should have something like clean and lock. Just note that if you're unofficially unlocked you'll need to apply for unlock or unlock unofficially again.
JD. A said:
Why are you using such a old rom? Use latest miflash and latest global. On the bottom right of miflash you should have something like clean and lock. Just note that if you're unofficially unlocked you'll need to apply for unlock or unlock unofficially again.
Click to expand...
Click to collapse
Other Miflash version don't detect my phone when it is in edl mode
I could start other stock rom, I know tried this ones:
kate_global_images_7.6.8_20170608.0000.00_6.0_global_2040bd5a39
kate_global_images_8.12.13_20181213.0000.00_6.0_global_304fc0692b
But I couldn't flash my LineageOS 13 + recovery with those.
I tried so much combinations TWRP/Stock rom, I don't remember what I tested.
I just know the MiFlash 2016.04.01.0 64 bit with an old official ROM : kate_global_images_6.9.29_20160805.0000.29_6.0_glo bal_9aa2d85137 with recovery.img replaced by an old ZXC-TWRP 3.0.2-X. was the only one combination that worked for me for installing LineageOS 13 + recovery working
Now, every time I try to flash something (whatever it is) it goes to bootloop...
Only fastboot and edl mode are working
If you have other links / combinations I would be happy to try
ROUGE13 said:
Other Miflash version don't detect my phone when it is in edl mode
I could start other stock rom, I know tried this ones:
kate_global_images_7.6.8_20170608.0000.00_6.0_global_2040bd5a39
kate_global_images_8.12.13_20181213.0000.00_6.0_global_304fc0692b
But I couldn't flash my LineageOS 13 + recovery with those.
I tried so much combinations TWRP/Stock rom, I don't remember what I tested.
I just know the MiFlash 2016.04.01.0 64 bit with an old official ROM : kate_global_images_6.9.29_20160805.0000.29_6.0_glo bal_9aa2d85137 with recovery.img replaced by an old ZXC-TWRP 3.0.2-X. was the only one combination that worked for me for installing LineageOS 13 + recovery working
Now, every time I try to flash something (whatever it is) it goes to bootloop...
Only fastboot and edl mode are working
If you have other links / combinations I would be happy to try
Click to expand...
Click to collapse
This is a little bit to late to the party but the latest both dev rom and global works for me with the latest me miflash. No problems what so ever. Seems like you're facing a hardware issue.
JD. A said:
This is a little bit to late to the party but the latest both dev rom and global works for me with the latest me miflash. No problems what so ever. Seems like you're facing a hardware issue.
Click to expand...
Click to collapse
Hi,
No, not too late my phone is still waiting, so thanks for your answer
Could you tell me witch version of rom / tool did you use?
I will try on a other windows computer to be sure there is no conflict with old tools I installed before.
If it works I will flash CM13 (marshmallow), I thought I should not use a too recent dev/global ROM before flashing CM13, but I don't remember were I read this. Is this true?
ROUGE13 said:
Hi,
No, not too late my phone is still waiting, so thanks for your answer
Could you tell me witch version of rom / tool did you use?
I will try on a other windows computer to be sure there is no conflict with old tools I installed before.
If it works I will flash CM13 (marshmallow), I thought I should not use a too recent dev/global ROM before flashing CM13, but I don't remember were I read this. Is this true?
Click to expand...
Click to collapse
I'm not home this weekend so I can't say for sure. gismoZ recommends using the 8.0.2 firmware or something like that can't remember, but the latest works just fine on my kate. The latest miflash is from 20200314 and just get the latest global rom and try to flash it.
I tried with an other windows computer, I successfully used last MiFlash version
But now, whatever I flash, ROM version or recovery version, it stay in bootloop when I power it.
I expect the eMMC memory to be faulty but why doesn't I have any error while flashing?
How to be sure this comes from the eMMC chip?
Some people have successfully changed it on the mediatek version of the phone:
https://fr-fr.facebook.com/16816505...c-kmvtu-done/1821360108117225/?_fb_noscript=1
https://translate.google.com/transl.../03/service-hp-xiaomi-redmi-mi-note-mati.html
If I go on this solution I have some questions before:
Must the eMMC chip be programmed before soldering it?
If not, can I program it with MiFlash once soldered?
If not, have I to use some special touch/contact on the mainboard to program it?
How to be sure of the chip model to buy?
Will the chip come already balled? Or have I to ball it before soldering it on mainboard?
Could I buy a 32GB chip instead 16GB original one?
Something else to test before going on this crazy last chance solution?
I bought a EDL flash cable, but I think I don't need it on this phone, I alway success to go to EDL mode from fastboot mode with a small batch script.
Hello ,
Any chance I could get an answer anymore or is my problem too specific maybe?
Disclaimer:
The use and installation of this software product is at the exclusive responsibility of the user.I am not responsible for any damage that may occur to your device resulting from the use of this software.This software product is "as is". Its first goal is to allow the xiaomi.eu Rom be installed via recovery.If you have any doubts regarding the above lines, you should not use or install it.
Recovery:
Unofficial release 3.7.0 for Xiaomi Mi 10T Lite and Redmi Note 9 Pro 5G devices. Status : StableVersion : 3.7.0.4GRelease Date : 2022.12.26Features:
Android 12 decryptionAndroid 13 decryption (Not tested by myself)FlashingAdbOtg (Not tested by myself)MtpBackup / Restore to / from microSDBackup / Restore through adbSideloadDevice boot Logo changerMagisk tools and theme from @ Brigudav (Not tested by myself)
Notes:
I concluded that custom roms (without Miui) are unable to decrypt /data with this recovery.Checking LineageOS and ArrowOS, it seems that they use a different encryption mode than Miui.I haven't found how to check on Twrp booting what encryption mode /data uses and adjust to it.Therefore, I have uploaded another release for non Miui devices.Can't tested by myself, I don't know if it decrypts fine.However, it is likely the Miui variant will work correctly on the rest.
About official TWRP: The current official release https://twrp.me/xiaomi/xiaomimi10i.html does not work anymore since Miui 13. Use instead this TWRP.
Twrp not decryping on miui 14: Please, read this post
Downloads:
Last release from Xda (Post #2)
Older releases from androidfilehost
Release 3.7.0.3F for CUSTOM NOT Miui rom from Xda (Post #2)
Installation:
Updating this Twrp release:Downloaded to phone:Click on Install and locate the .zip file.Downloaded to PC (no need to copy it to the phone): On phone: start install via ADB (sideload). On PC execute: adb sideload file_name.zip
Try without installing: (does not alter the phone unless you want to do)Extract recovery.img from .zip file downloadedEnter fastboot mode.Execute: fastboot boot recovery.img
Installing this for the first time:
Your bootloader must be open. Extract recovery.img from downloaded .zip file. Enter fastboot mode Execute: fastboot flash recovery recovery.imgCredits:
Team Win RecoveryMinimal Manifest PlatformAlexander Brigudav
Latest release 3.7.0.4G for MIUI rom
Release 3.7.0.3F for CUSTOM Non Miui rom
Nice work
Flashed R2 release, but it doesn't decrypt my data (it doesn't ask about my PIN). I am Polish xiaomi.eu translator and tester, and will ask Xiaomi.eu team about recovery ROM if the storage is decrypted... but can't for now...
Also, I was unable to boot to system after flash that TWRP, I had to use OrangeFox to be able to boot.
kacskrz said:
Flashed R2 release, but it doesn't decrypt my data (it doesn't ask about my PIN). I am Polish xiaomi.eu translator and tester, and will ask Xiaomi.eu team about recovery ROM if the storage is decrypted... but can't for now...
Also, I was unable to boot to system after flash that TWRP, I had to use OrangeFox to be able to boot.
Click to expand...
Click to collapse
Hello. I'm Spanish xiaomi.eu translator and user.
I don't understand how is possible your issue...
When I boot TWRP it asks me for the PIN to decrypt.
I would not have uploaded the image without testing it first.
Also the reboot buttons do what they say..
I have so far tested it without installing, because I have not yet dumped the Stock Recovery partition.
In theory, it is supposed to work exactly the same in boot mode as in flash mode.
Can you try it without installing?
As stated in the third disclaimer lines:
"Its intention is to allow the Rom xiaomi.eu be installed via recovery."
I retired here due to lack of free time and have only become involved now for this reason.
Best regards
tuxafgmur said:
Can you try it without installing?
Click to expand...
Click to collapse
Same situation, unfortunately... (except the reboot button which boots system, as i've just booted recovery, not flashed).
Edit: removed all screen lock methods I've set, still same. Looks like it isn't able to decrypt my data even without screen lock... Maybe something works differently between beta (which I use) and stable (which you use) release?
Edit2: logs there with set PIN as screen lock method https://miuipolska.pl/d/Orjon/gauguin_twrp.zip
Edit 3 24.07. 9:00am CEST: reboot to system works fine now after flashing your recovery, maybe the fact i've used "fastboot reboot-recovery" command was the reason to fail before...
kacskrz said:
Same situation, unfortunately... (except the reboot button which boots system, as i've just booted recovery, not flashed).
Edit: removed all screen lock methods I've set, still same. Looks like it isn't able to decrypt my data even without screen lock... Maybe something works differently between beta (which I use) and stable (which you use) release?
Edit2: logs there with set PIN as screen lock method https://miuipolska.pl/d/Orjon/gauguin_twrp.zip
Click to expand...
Click to collapse
Your logs do not seem to give relevant information about the issue.
It is clear that booting are completely ignoring the security lockout..
During the night I dumped and unpacked the stock recovery.
After studying it, I found nothing significant except that the kernel is not exactly the same as in boot.img.
I'm now downloading the latest weekly release to unpack it and compare vs stable release.
kacskrz said:
Edit 3 24.07. 9:00am CEST: reboot to system works fine now after flashing your recovery, maybe the fact i've used "fastboot reboot-recovery" command was the reason to fail before...
Click to expand...
Click to collapse
I'm not sure I understand what this paragraph means..
Regards.
Pixel Experience 12 data decrypted successfully.
Thanks
Lineage os data decrypted successfully.
Unfortunately, the weekly xiaomi.eu does not decipher the date.
For @kacskrz , @nolan2112 and anyone else using weekly xiaomi.eu:
I would appreciate the test of the new Release 3 I just uploaded.
Thanks in advance.
@tuxafgmur Unfortunately, nothing changed. I've posted logs on the xiaomi.eu thread.
The latest version also cannot decode the date. firmware weekly 22.7.21
New release 3.6.2.1B uploaded
In addition to some other minor changes,
fixed decryption on xiaomi.eu weekly.
New release 3.6.2.1B-R2 uploaded
No relevant changes.
Tested to flash xiaomi.eu from storage and sideload.
tuxafgmur said:
New release 3.6.2.1B-R2 uploaded
No relevant changes.
Click to expand...
Click to collapse
Everything is fine, the recovery is fully working. Thanks Amigo!
New release 3.6.2.1B-R3 uploaded
Revision
New release 3.6.2.1C uploaded
Format: Zip file to install from TWRP.
Some reviews.
Since xiaomi.eu rom replaces boot Logo on global devices, showing "Redmi"
this release includes options to switch logo between "MI" and "Redmi".
Each has two versions to choose from:
1 - Factory stock.2 - Like stock but hiding the padlock shown when bootloader is open.
The only recovery that works (and decrypts) on the newest MIUI 13 Android 12. Thank you!
Fantastic work, congratulations!