Hey guys,
I've been installing customs without issue on my RN10.
Then one stopped booting freezing on the logo and bootloops.
Reinstalled stock with miflash and Redmi bootloops.
Tried customs again and same thing.
Any suggestions or things to try?
Worried the system_root and vendor errors are my problem.
Thanks in advance for any help or tips.
Cheers.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
GEoMaNTiK said:
View attachment 5541321
Click to expand...
Click to collapse
Try flashing the super image through recovery.
faced this problem the solution for me was to flash fastboot miui eu rom
SubwayChamp said:
Try flashing the super image through recovery.
Click to expand...
Click to collapse
Tried this and didn't help, thanks for the suggestion
muneeb rizwan said:
faced this problem the solution for me was to flash fastboot miui eu rom
Click to expand...
Click to collapse
Hey there, I've tried flashing via Mi Flash and although it says success, still bootloops on Redmi logo, then eventually to fastboot.
Do you remember which fastboot miui EU rom or have a link ?
I'll try anything at this stage.. think I've killed my first Xiaomi phone.
GEoMaNTiK said:
Tried this and didn't help, thanks for the suggestion
Click to expand...
Click to collapse
Also, you can fix it flashing this ROM xiaomi.eu_multi_HMNote10_V13.0.5.0.SKGMIXM_v13-12-fastboot
SubwayChamp said:
Also, you can fix it flashing this ROM xiaomi.eu_multi_HMNote10_V13.0.5.0.SKGMIXM_v13-12-fastboot
Click to expand...
Click to collapse
Thanks for this, just tried, used the windows_fastboot_first_install_with_data_format.bat and all installed with an OKAY.
No failures or errors during install. Phone bootloops on Redmi and comes back to Mi Recovery screen.
Is there a way with OrangeFox, TWRP and any other tool to fix the file system or help?
Thanks in advance.
GEoMaNTiK said:
Thanks for this, just tried, used the windows_fastboot_first_install_with_data_format.bat and all installed with an OKAY.
No failures or errors during install. Phone bootloops on Redmi and comes back to Mi Recovery screen.
Is there a way with OrangeFox, TWRP and any other tool to fix the file system or help?
Thanks in advance.
Click to expand...
Click to collapse
same with me..but i reset data in recovery ..phone booting normal back
Now I'm getting a failed to mount (block device required) but still not able to get a custom to boot. When I try to reboot, I'm getting a system partition is empty.
Next question I have, do I have to force encryption in Orangefox or turn it off?
Also DM-Verity, should both options be off or on for customs?
GEoMaNTiK said:
Now I'm getting a failed to mount (block device required) but still not able to get a custom to boot. When I try to reboot, I'm getting a system partition is empty.
Next question I have, do I have to force encryption in Orangefox or turn it off?
Also DM-Verity, should both options be off or on for customs?
Click to expand...
Click to collapse
bro im facing the same problem you have... im using rn10sunny twrp will not mount system, and didnt flash custom roms... and if i flash stock rom then it will goes to bootloop... im also in the same condition now.....
can you please contact me on telegram @KAVIKING007 for discuss about the problem.. it will help both we are getting solutions....
GEoMaNTiK said:
Thanks for this, just tried, used the windows_fastboot_first_install_with_data_format.bat and all installed with an OKAY.
No failures or errors during install. Phone bootloops on Redmi and comes back to Mi Recovery screen.
Is there a way with OrangeFox, TWRP and any other tool to fix the file system or help?
Thanks in advance.
Click to expand...
Click to collapse
I assume you are formatting data, no? The long procedure for me was, installing AEX, I couldn't install it with TWRP (in this state), used OFR, boot to the recovery that AEX provides, format data, then boot to system, check that all is ok, enable USB debugging, now go to fastboot and flash the Miui 13.
In other device was fixed just flashing the super image (from the stock ROM) onto the super partition.
Keep the OFR settings as they are.
My theory is that some custom ROMs break the sizes on the super partition and some images are not matching.
Can you please explain about OFR because i couldn't used before....
KAVIYARASU KING said:
Can you please explain about OFR because i couldn't used before....
Click to expand...
Click to collapse
OFR Orange Fox recovery, is available in the forum.
SubwayChamp said:
OFR Orange Fox recovery, is available in the forum.
Click to expand...
Click to collapse
I tried in orangefox also but same problem occurs..... that was system could not mount.... On twrp,OFR the system partition could not be mounted... I tried all the way... But no result
KAVIYARASU KING said:
I tried in orangefox also but same problem occurs..... that was system could not mount.... On twrp,OFR the system partition could not be mounted... I tried all the way... But no result
Click to expand...
Click to collapse
Try, as pointed out in previous posts, format data with AEX recovery, then flash Miui.eu 13 through fastboot.
Also you can try flashing the super image (from the stock ROM through OFR).
And, finally, you can try using Mi Flash tool BUT in EDL mode.
All of these, assuming that you are permanently flashing the custom recovery, not only booting to it.
GEoMaNTiK said:
Thanks for this, just tried, used the windows_fastboot_first_install_with_data_format.bat and all installed with an OKAY.
No failures or errors during install. Phone bootloops on Redmi and comes back to Mi Recovery screen.
Is there a way with OrangeFox, TWRP and any other tool to fix the file system or help?
Thanks in advance.
Click to expand...
Click to collapse
You did not use the correct *.bat file for a complete cleanup. The *.bat you used will leave the original data on your phone even if it is not compatible. If you have a problem and want to install a new clean Miui system, use the flash_all.bat file (in MiFlash this is the "clean all" option)
StaryMuz said:
You did not use the correct *.bat file for a complete cleanup. The *.bat you used will leave the original data on your phone even if it is not compatible. If you have a problem and want to install a new clean Miui system, use the flash_all.bat file (in MiFlash this is the "clean all" option)
Click to expand...
Click to collapse
I had already tried MiFlash before that other rom and it's .bat file.
Just tried this with MiFlash - mojito_global_images_V12.5.2.0.RKGMIXM_20210731.0000.00_11.0_global_ce90f80766.tgz
I selected flash_all.bat. Received a success on completion of flash, used this MiFlash2018-5-28-0 (as I was receiving errors on the new MiFlash versions).
And still my phone bootloops on Redmi. This almost confirms to me this phone is lost now, nothing else I can think of.
However, will wait to see if any other suggestions here.
Thanks everyone for trying to help, much appreciated.
Don't worry yesterday night i get a new solution for these problem..... Almost we will get our device soon..... Today im gonna test few steps and its work i will give the solution dude.... So don't worry....
Related
Folks,
I really need your help.
I bought p9000 a week ago, and did the standard upgrades via OTA.
I read about the Android Nougat version, and I decided to install via Flash Tools, however, due to the various bugs, I decided to go back to Marshmellow version 6.0.
The problem happened after I used the flash tools, it simply bricked.
The process happened correctly, but it just does not start.
I read in other forums to try to remove the plug from the battery, and so I did, but did not solve anything, my computer simply does not recognize the device.
I use Windows 10 x64 ... Please, anyone know how to recover a braided device?
I'm waiting.
Thank you very much.
Regards
Alicio04
SOLUTION
I found the solution.
I used the Nougat version bootloader, and I connected the phone.
I uninstalled all previously installed drivers, (MTK driver) and even dead, I held the volume up button, and the PC recognized the device, installing the bootloader normally via flash tools.
I'm very happy that it worked, if anyone needs help, this is a solution.
Regards
Mind throwing quick guide on how to flash bootloader? I got similar problem. My phone is dead for over a week now and I cant seem to fix it. PC recognize it, drivers are all good. When i Click "Download" on Flashtools and connect my phone, process goes well and everything ends with "ok", but phone is not starting. It just hangs on Elephone logo. Also if this is helpful in order to determine my problem, I rebooted into recovery but recovery is not recognizing my Internal Memory when I try to Wipe Data or Wipe Cache. Even tho I can browse through my Internal and External memories. Please help and thanks in advance!
stewakg said:
Mind throwing quick guide on how to flash bootloader? I got similar problem. My phone is dead for over a week now and I cant seem to fix it. PC recognize it, drivers are all good. When i Click "Download" on Flashtools and connect my phone, process goes well and everything ends with "ok", but phone is not starting. It just hangs on Elephone logo. Also if this is helpful in order to determine my problem, I rebooted into recovery but recovery is not recognizing my Internal Memory when I try to Wipe Data or Wipe Cache. Even tho I can browse through my Internal and External memories. Please help and thanks in advance!
Click to expand...
Click to collapse
thats due to preloader, try using the updated preloader, you can find in lineage thread, it should boot normally after
Ruben Craveiro said:
thats due to preloader, try using the updated preloader, you can find in lineage thread, it should boot normally after
Click to expand...
Click to collapse
I will try that tonight. Thanks for your suggestion. What should be clicked before I click download? Ona preloader or it should be all?
stewakg said:
I will try that tonight. Thanks for your suggestion. What should be clicked before I click download? Ona preloader or it should be all?
Click to expand...
Click to collapse
i guess all except boot partition bevause i think it comes with it too, but might not make it boot if you have a different version of android, if it still doesnt work try flashing latest stock rom with latest preloader and should work
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Maybe twrp recovery will work
This picture was taken after following official guide in lineage thread. After this I have flashed stock rom 08.10 but it won't boot
stewakg said:
This picture was taken after following official guide in lineage thread. After this I have flashed stock rom 08.10 but it won't boot
Click to expand...
Click to collapse
Flash stock rom but replace preloader with the lineage os preloader, it should boot
Ruben Craveiro said:
Flash stock rom but replace preloader with the lineage os preloader, it should boot
Click to expand...
Click to collapse
Its a no go... First I flashed 10.08.2016 version and it didn't boot. Then I tried with lineage preloader (checked only preloader without rest of the options) and still won't boot. Flashed latest version 12.01.2017, still wont boot. Tried with preloader from lineage, and it still ain't booting. Am I missing something?
Thanks in advance
stewakg said:
Its a no go... First I flashed 10.08.2016 version and it didn't boot. Then I tried with lineage preloader (checked only preloader without rest of the options) and still won't boot. Flashed latest version 12.01.2017, still wont boot. Tried with preloader from lineage, and it still ain't booting. Am I missing something?
Thanks in advance
Click to expand...
Click to collapse
If it powers on, use johnnys twrp version 8, and flash lineage os, it should boot
---------- Post added at 08:45 PM ---------- Previous post was at 08:36 PM ----------
stewakg said:
Its a no go... First I flashed 10.08.2016 version and it didn't boot. Then I tried with lineage preloader (checked only preloader without rest of the options) and still won't boot. Flashed latest version 12.01.2017, still wont boot. Tried with preloader from lineage, and it still ain't booting. Am I missing something?
Thanks in advance
Click to expand...
Click to collapse
Ill just tell you the partitions i flashed in order to make it boot, i flashed lineageOS using twrp on old Preloader, which made it constantly go on reboot loop, then i used the file named "preloader for updated versions" which flashed Preloader, lk, lk2 and boot partition (i unticked recovery partition) and jt booted lineage normally. You might need to update the twrp to 3.0.2-8 if not already, after you flash the updated preloader.
Updated preloader, installed twrp 0.8 and here are results:
stewakg said:
Updated preloader, installed twrp 0.8 and here are results:
Click to expand...
Click to collapse
Hi.
Did you solved your problem?
greetings
vsrookie
Sent from my P9000 using XDA-Developers Legacy app
vsrookie said:
Hi.
Did you solved your problem?
greetings
vsrookie
Sent from my P9000 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Unfortunately not
Hi.
Did you tried to flash stock again with splashtool? With all partitions and begin from scratch?
greetings
vsrookie
Sent from my P9000 using XDA-Developers Legacy app
Kraj, tries that. All the time same result. Phone is not booting. Hangs on elephone logo.
Hi.
Which stockrom did you try?
greetings
vsrookie
Sent from my P9000 using XDA-Developers Legacy app
Latest and 10.08.2016 versions.
stewakg said:
Latest and 10.08.2016 versions.
Click to expand...
Click to collapse
Flash 20160304 preloader and keep trying. It takes a couple of attempts and hold the volume up button. flash only the preloader. Afterwards flash the latest rom
Version 10.2.26.0
Version 10.2.24.0 ------------ > Stock/Root
Version 10.2.9.0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
T4Ump said:
Version 10.2.24.0 - Link
Click to expand...
Click to collapse
so what do we do with this? fastboot it? is it like a full rom with magisk, rooted? cheers
vtec303 said:
so what do we do with this? fastboot it? is it like a full rom with magisk, rooted? cheers
Click to expand...
Click to collapse
Fastboot flash boot.img
It's only magisk for 10.2.24
You can create your own if you want, it's just 30s faster
Code:
fastboot flash boot boot.img
Thank you so much for posting this. I'd been trying for 2 days with twrp and magisk (19.1 and 19.2) and could never get past the recovery bootloop on my Mi 9.
Are you on global stable?
I am having boot loop too.
So far I haven't seen any root for 10.2.9.0
Does anyone have boot.img V10.2.9.0.PFAMIXM? I wanna try root, but only need that file
xxx
T4Ump said:
xxx
Click to expand...
Click to collapse
Hi, thanks for the patched one. Do you still have the stock one? My phone stuck at recovery mode
Edited: nvm. I'll download the fastboot ROM. Thank you anyway.
realm9thfeb said:
Are you on global stable?
I am having boot loop too.
So far I haven't seen any root for 10.2.9.0
Click to expand...
Click to collapse
I don't get it, what are you trying to achieve? Keep encryption and have root access?
Right now i'm on 10.2.9.0 running perfectly fine with root (magisk 19.1) but no encryption.
PriPhaze said:
I don't get it, what are you trying to achieve? Keep encryption and have root access?
Right now i'm on 10.2.9.0 running perfectly fine with root (magisk 19.1) but no encryption.
Click to expand...
Click to collapse
Hi, could you tell me how you root your phone? I installed magisk manager, chose boot.img then got magisk_patched.img. I flashed it via fastboot flash boot magisk_patched.img but I got stuck at stock recovery after rebooting. Did I miss any step?
syreg said:
Hi, could you tell me how you root your phone? I installed magisk manager, chose boot.img then got magisk_patched.img. I flashed it via fastboot flash boot magisk_patched.img but I got stuck at stock recovery after rebooting. Did I miss any step?
Click to expand...
Click to collapse
What i did was:
-Flash Stock Global ROM with Xiaomi Flash making sure to set the bat as clean all and NOT clean and lock!
-Once done it will automatically boot , and when it does simply reboot and hold down vol to go to the fastboot
-Flash Recovery img using minimal adb and fastboot
-Type "Fastboot reboot" and hold vol up to go to twrp
-In TWRP FORMAT data to get ride off encryption and reboot into recovery
-Again in TWRP now u can transfer files to the phone, so i patched "Disable_Dm-Verity_ForceEncrypt" and then patched Magisk 19.1
-That's it.
You can now reboot and it will start the phone configuration as normal but once you configure everything u will see that magisk is there and fully works.
Just one thing tho.... be careful if u will restore titanium back up apps...
Don't get me wrong; they do restore correctly but when you make a backup it becomes corrupted or at least that's what happened to me, so make sure to keep backups PRIOR to using the ROM saved in your PC or something.
EDIT: Maybe u should give a try to this twrp https://forum.xda-developers.com/Mi-9/development/recovery-unofficial-twrp-xiaomi-mi-9-t3905825, just got updated few hrs ago and so far seems it works really good.
syreg said:
Hi, could you tell me how you root your phone? I installed magisk manager, chose boot.img then got magisk_patched.img. I flashed it via fastboot flash boot magisk_patched.img but I got stuck at stock recovery after rebooting. Did I miss any step?
Click to expand...
Click to collapse
I have this problem too, do this steps.
1. Fastboot ROM
2. Update last version
3. Flash magisk_patched.boot
4. Factory reset
Done, you have root.
PriPhaze said:
What i did was:
-Flash Stock Global ROM with Xiaomi Flash making sure to set the bat as clean all and NOT clean and lock!
-Once done it will automatically boot , and when it does simply reboot and hold down vol to go to the fastboot
-Flash Recovery img using minimal adb and fastboot
-Type "Fastboot reboot" and hold vol up to go to twrp
-In TWRP FORMAT data to get ride off encryption and reboot into recovery
-Again in TWRP now u can transfer files to the phone, so i patched "Disable_Dm-Verity_ForceEncrypt" and then patched Magisk 19.1
-That's it.
You can now reboot and it will start the phone configuration as normal but once you configure everything u will see that magisk is there and fully works.
Just one thing tho.... be careful if u will restore titanium back up apps...
Don't get me wrong; they do restore correctly but when you make a backup it becomes corrupted or at least that's what happened to me, so make sure to keep backups PRIOR to using the ROM saved in your PC or something.
EDIT: Maybe u should give a try to this twrp https://forum.xda-developers.com/Mi-9/development/recovery-unofficial-twrp-xiaomi-mi-9-t3905825, just got updated few hrs ago and so far seems it works really good.
Click to expand...
Click to collapse
Thank you. I'll try your steps.
How do you know the titanium backup becomes corrupted?
T4Ump said:
I have this problem too, do this steps.
1. Fastboot ROM
2. Update last version
3. Flash magisk_patched.boot
4. Factory reset
Done, you have root.
Click to expand...
Click to collapse
Factort reset? You mean wipe data while stuck at stock recovery? I did. Somehow my phone rooted. But I realized when I charge my phone while turning off it shows mi logo & unlocked words instead of battery icon, even after I unplug the charger. So I have to press power button to turn it on and charge normally. Do you have this problem?
syreg said:
Thank you. I'll try your steps.
How do you know the titanium backup becomes corrupted?
Click to expand...
Click to collapse
Because once I moved back to revolution OS ( I sawp of ROMs quite often ) I realized that my entire apps restored with titanium were crashing , and the few that actually open correctly didn't hold my data.
They were as if you just download them for the first time from the store.
syreg said:
Thank you. I'll try your steps.
How do you know the titanium backup becomes corrupted?
Factort reset? You mean wipe data while stuck at stock recovery? I did. Somehow my phone rooted. But I realized when I charge my phone while turning off it shows mi logo & unlocked words instead of battery icon, even after I unplug the charger. So I have to press power button to turn it on and charge normally. Do you have this problem?
Click to expand...
Click to collapse
No, i dont have this problem.
Root images updated to 19.2 magisk.
10.9.20 require wipe all data after flash patched image, this is not practical at all.
1. you stuck in this rom unless you want to wipe all data every time there is new rom.
2. Magisk bug existed in the latest global stable rom, notification prompted everytime you open Magisk to install zip, you can only ignore it or installation zip brick the phone.
10.2.26.0 root/stock
Can I use those with locked bootloader ?
Sent from my MI 9 using Tapatalk
I receive this Android 10 update,update succeeded,but after installing Magisk,my Mi 8 stick to fastbootmode no matter how it restarted.And after some reboots,twrp recovery is not able to decrypt data anymore,so it bricked.
Luckily before bricked,I had revert it back to miui_MI8Global_V10.3.5.0 by Twrp recovery en somehow after wipe data used stock recovery it come to live again.
So anyone has any idea,how to install Magisk without problem.
Magisk version used latest 20.3.
Twrp recovery boot by fastboot boot command.
sm1232 said:
I receive this Android 10 update,update succeeded,but after installing Magisk,my Mi 8 stick to fastbootmode no matter how it restarted.And after some reboots,twrp recovery is not able to decrypt data anymore,so it bricked.
Luckily before bricked,I had revert it back to miui_MI8Global_V10.3.5.0 by Twrp recovery en somehow after wipe data used stock recovery it come to live again.
So anyone has any idea,how to install Magisk without problem.
Magisk version used latest 20.3.
Twrp recovery boot by fastboot boot command.
Click to expand...
Click to collapse
I don't have time to customise instructions for your exact issue.
But you can gleen the majority of what you need to do by following my instructions here: https://xiaomi.eu/community/threads/9-12-19.53895/post-521845 Note : Ensure that you are using latest canary, and follow the instructions precisely in regard to passwords. Next, these instructions are how to not have issues when updating.
You are probably past the point of repairing permissions, so if you do not have a backup of your previous systems boot image, you will most likely need to format user data and start clean. Finally these instructions assume that your bootloader is unlocked.
sm1232 said:
I receive this Android 10 update,update succeeded,but after installing Magisk,my Mi 8 stick to fastbootmode no matter how it restarted.And after some reboots,twrp recovery is not able to decrypt data anymore,so it bricked.
Luckily before bricked,I had revert it back to miui_MI8Global_V10.3.5.0 by Twrp recovery en somehow after wipe data used stock recovery it come to live again.
So anyone has any idea,how to install Magisk without problem.
Magisk version used latest 20.3.
Twrp recovery boot by fastboot boot command.
Click to expand...
Click to collapse
Flash Disable_Dm-Verity_ForceEncrypt_12.27.2019.zip after Magisk
Bortex19 said:
Flash Disable_Dm-Verity_ForceEncrypt_12.27.2019.zip after Magisk
Click to expand...
Click to collapse
As I mentioned he is well past fixing permissions, unless he has the linked boot image that he can reflash. Even then, there would be permission issues. DM verity will not help.
The solution is to use Magisk Canary and follow the instructions that I linked.
Remove passwords.
Extract the boot image,
place in downloads folder,
patch boot image,
boot to recovery and flash Canary magisk . Done
I had the same problem and solved it by flashing dm-verity; It is probably easier and more convenient to try this first and, if it does not work, continue with the rest of the instructions
fixed
thanks for replies.
I use the patch bootimage methode all the time,had never problem with Android 9 (Pie).
Problem only occurs on Android 10.
Fixed:
Factory reset (all data lost),data partition empty.
Flash Magisk.zip by Twrp recovery.
clean dalvik-cache.
reboot,done.
I will try the patch bootimage methode on next Android 10 update.
sm1232 said:
thanks for replies.
I use the patch bootimage methode all the time,had never problem with Android 9 (Pie).
Problem only occurs on Android 10.
Fixed:
Factory reset (all data lost),data partition empty.
Flash Magisk.zip by Twrp recovery.
clean dalvik-cache.
reboot,done.
I will try the patch bootimage methode on next Android 10 update.
Click to expand...
Click to collapse
Hi,
I have only one question: after every update must I do every time factory reset?
slave2007 said:
Hi,
I have only one question: after every update must I do every time factory reset?
Click to expand...
Click to collapse
Till now I don't know ,when the next Android 10 update comes,I will try it and tell you the result.
sm1232 said:
Till now I don't know ,when the next Android 10 update comes,I will try it and tell you the result.
Click to expand...
Click to collapse
Thanks, I hope it is enough one times?
great news
slave2007 said:
Thanks, I hope it is enough one times?
Click to expand...
Click to collapse
Today I receive miui_MI8Global_V11.0.3.0.QEAMIXM update.
Use my method installing Magisk,works without problem.
Hope come true,did it WITHOUT FACTORY RESET.
:laugh:
sm1232 said:
Today I receive miui_MI8Global_V11.0.3.0.QEAMIXM update.
Use my method installing Magisk,works without problem.
Hope come true,did it WITHOUT FACTORY RESET.
:laugh:
Click to expand...
Click to collapse
??
"your method" is dirty install, wipe cache and perhaps install "disable DM verity too? ?
slave2007 said:
??
"your method" is dirty install, wipe cache and perhaps install "disable DM verity too? ?
Click to expand...
Click to collapse
I do not need to install disable dm-verity to avoid bootloop or so.
After format my data partition,used my method installing Magisk,reboot everything works fine.In Magisk manager only keep avb 2.0 dm-verity ticked by default.
After system encrypts the data partition,because Xposed framework Magisk module cause bootloops,I uninstall Magisk used Magiskuninstaller.zip and install Magisk again.After booted in system,in Magisk manager also keep encryption ticked by default.
I guess author of Magisk has done all the works for us to make Magisk works properly automatically. :good:
sm1232 said:
Today I receive miui_MI8Global_V11.0.3.0.QEAMIXM update.
Use my method installing Magisk,works without problem.
Hope come true,did it WITHOUT FACTORY RESET.
:laugh:
Click to expand...
Click to collapse
v11.0.3.0 come out already?? im stuck at v11.0.1.0..
Actually 11.0.6.0 already
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my MI 8 using Tapatalk
That is Android 9 based...
fidows said:
Actually 11.0.6.0 alreadyView attachment 4946525
Sent from my MI 8 using Tapatalk
Click to expand...
Click to collapse
last timr mi 8 got android 10 update, there revert version to 11.0.1.0.. based on Q.. so latest version is 11.0.3.0 for Q, and 11.0.6.0 for Pie..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
We are not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at us for messing up your device, we will laugh at you.
WORKING:
Decryption userdata with eu roms
Screen brightness settings
Correct screenshot color
MTP
ADB
Vibration
Sideload
To flash the TwrpDownload the recovery and copy to adb folder
Open terminal
Code:
fastboot flash recovery nameofrecovery.img
fastboot boot nameofrecovery.img
or
fastboot reboot with vol + to boot
Source Codehttps://github.com/geoanto555/android_device_xiaomi_gauguin
https://github.com/TeamWin/android_bootable_recovery
Prebuilt Stock Kernel
Thanks to TeamWin Recovery Project
all testers and developers
Thanks to Μιχάλης (chariPower) for the information(sideload)
Download Link-stwrp_gauguin_3.5.A10_05-01-2021
twrp_gauguin_3.5.A10_07-02-2021 fixed sideload and mtp
twrp_gauguin_3.5.A10_18-02-2021 fixed backup data error 255 (/data/extm)
twrp_gauguin_3.5.A10_05-03-2021 Fixed Mtp after format data & reboot recovery. (if the MTP does not open, try reboot in twrp again)
twrp_gauguin_3.5.1.A10_30-03-2021 fixed fastbootd
it’s first time i am using xiaomi phone. my device is RMN9P5G and waiting for unlocked. can i flash your recovery and install the latest stable EU rom in mifirm.net: V12.0.8.0.QJSCNXM immediately after unlock success？i’m worry a bit because some members report that internal, user data be encrypted and cannot access..
kien_vip said:
it’s first time i am using xiaomi phone. my device is RMN9P5G and waiting for unlocked. can i flash your recovery and install the latest stable EU rom in mifirm.net: V12.0.8.0.QJSCNXM immediately after unlock success？i’m worry a bit because some members report that internal, user data be encrypted and cannot access..
Click to expand...
Click to collapse
From my experience, the recovery cannot decrypt the stock ROMs, you have to flash a custom ROM (Arrow and Lineage are the only 2 right now), or flash a xiaomi EU ROM.
Copy the rom to sdcard or usb otg.
Format data
Reboot recovery
Flash rom.
With xiaomi eu decryption works...
Decryption on stock rom works if I hotboot TWRP (fastboot boot twrp.img). If I flash it, TWRP doesn't prompt me for a password when started and keeps data encrypted.
Hi there, thank you for the TWRP. Is there any chance to decrypt also user 999 for the Dual apps on the .eu ROMs?
not for now. I will upload new version soon
ilyachelsea said:
Is there any chance to decrypt also user 999 for the Dual apps on the .eu ROMs?
Click to expand...
Click to collapse
twrp_gauguin_MI10TL-RN9P5G_MI10I_3.5.A10_18-02-2021_BL-L
Fixed backup userdata (error 255 for data/extm)
User 999 can be decrypted only with default password ( without pattern-pin-pass) for now.
Thank you, but my password is PIN, anyway the recent twrp can't decrypt user 999. It is the message in red: "Failed decrypt user 999"
Only without pin,pass,pattern can be decrypted user999
It's a pity. I intend to back up also user 999 to keep my dual banking apps with the access data. If I first remove the PIN, and backup user 999 with the TWRP, after restore I will have to set up access again. This kills the benefit of the decryption and makes backup of 999 useless.
Thank you anyway and I hope, NO PIN is the temporary requirement of this version.
Hello everybody! Last week I unlocked the bootloader of my gauguin and initially I tried the official TWRP Recovery released by TWRP official page but it didn't work correctly and I couldn't flash zips, so I tried this beta version released by geoanto555 and it worked smoothly, I flashed zips and I had root permissions... But last night the smartphone had the battery low and it turned off, when I connected it to the charger it automatically reboot in fastboot and I can only enter in recovery mode. Sorry but I'm new in the modding world and I don't know what to do.. First brick.. What I did wrong? Anybody can help me? Is there anything I can do or I have to buy a new phone? Thanks to who will answer . Good evening.
devedel said:
Hello everybody! Last week I unlocked the bootloader of my gauguin and initially I tried the official TWRP Recovery released by TWRP official page but it didn't work correctly and I couldn't flash zips, so I tried this beta version released by geoanto555 and it worked smoothly, I flashed zips and I had root permissions... But last night the smartphone had the battery low and it turned off, when I connected it to the charger it automatically reboot in fastboot and I can only enter in recovery mode. Sorry but I'm new in the modding world and I don't know what to do.. First brick.. What I did wrong? Anybody can help me? Is there anything I can do or I have to buy a new phone? Thanks to who will answer . Good evening.
Click to expand...
Click to collapse
If you have access to the recovery, or fastboot, you can flash the original firmware with fastboot, but watch out, for some reason, when i flash the original rom from Windows using fastboot, it crashes, but with Linux it just works
AnibalSP said:
If you have access to the recovery, or fastboot, you can flash the original firmware with fastboot, but watch out, for some reason, when i flash the original rom from Windows using fastboot, it crashes, but with Linux it just works
Click to expand...
Click to collapse
In my device the rom is still the original. Do I have to do it anyway? What can happen if I try to flash a custom rom? If I only do the factory reset will I lose also TWRP?
AnibalSP said:
If you have access to the recovery, or fastboot, you can flash the original firmware with fastboot, but watch out, for some reason, when i flash the original rom from Windows using fastboot, it crashes, but with Linux it just works
Click to expand...
Click to collapse
I'm trying to do this with XiaoMiTool v2.. Thanks
devedel said:
In my device the rom is still the original. Do I have to do it anyway? What can happen if I try to flash a custom rom? If I only do the factory reset will I lose also TWRP?
Click to expand...
Click to collapse
If you can boot to android, or boot to TWRP / Orangefox, you don't need to flash again miui stock
If you flash a second rom, the worst thing that can happen, is that the rom may not work, but you wipe the internal memory (dalvik cache and data) and it should be running again
If you loose twrp for some reason, you can flash it again with xiaomitoolv2, or with fastboot
I'd recommend to you to try rooting, installing roms and similars things in an old phone if you don't are confident / know what are you doing, you will learn a lot in a few days of tinkering.
Anyone know what I need? I can't finish the installation of a official xiaomi rom to unbrick my device
devedel said:
View attachment 5257349
Anyone know what I need? I can't finish the installation of a official xiaomi rom to unbrick my device
Click to expand...
Click to collapse
Hi,
Download the official stock rom
Dont use XiaoMiToolV2, instead use MiFlash (official tool). Works for me every time. Then connect your phone in fastboot and flash all, I use the clean all and lock option which relocks my bootloader but you could just clean all and leave the bootloader unlocked. Then you can start again
fizzy900 said:
Hi,
Download the official stock rom
Dont use XiaoMiToolV2, instead use MiFlash (official tool). Works for me every time. Then connect your phone in fastboot and flash all, I use the clean all and lock option which relocks my bootloader but you could just clean all and leave the bootloader unlocked. Then you can start again
Click to expand...
Click to collapse
Hi, thanks for your advice.
Do you think it can works if usb debugging is off? I'm afraid I've disabled it the night the phone bricked.
I did wrong too many things but was my first try, tomorrow I'll buy a new Mi 10t lite and I'll try again, using more precautions.
Thank you all anyway, good evening.
devedel said:
Hi, thanks for your advice.
Do you think it can works if usb debugging is off? I'm afraid I've disabled it the night the phone bricked.
I did wrong too many things but was my first try, tomorrow I'll buy a new Mi 10t lite and I'll try again, using more precautions.
Thank you all anyway, good evening.
Click to expand...
Click to collapse
Enabled debugging is needed for adb when the system is running. For fastboot it does not matter.
Hi,
after flashing TWRP 3.5.2_11-Nebrassy on my Redmi Note 10 (sunny) and flashing Havoc OS after reboot I always come back to twrp. Cannot boot Havoc OS. And I see E: Unable to decrypt FBE device. What should I do to resolve this problem?
dario-20 said:
Hi,
after flashing TWRP 3.5.2_11-Nebrassy on my Redmi Note 10 (sunny) and flashing Havoc OS after reboot I always come back to twrp. Cannot boot Havoc OS. And I see E: Unable to decrypt FBE device. What should I do to resolve this problem?
Click to expand...
Click to collapse
Always wipe dalvic cache data storage and format data before you flash any rom
It
akoaypinoy said:
Always wipe dalvic cache data storage and format data before you flash any rom
Click to expand...
Click to collapse
It was done! But still have the same error and still come back to trwp instead of the new rom (Havoc). :-(
dario-20 said:
It
It was done! But still have the same error and still come back to trwp instead of the new rom (Havoc). :-(
Click to expand...
Click to collapse
How you flash havoc? Vanilla or Gapps version?
akoaypinoy said:
How you flash havoc? Vanilla or Gapps version?
Click to expand...
Click to collapse
Gapps
If you installed a new rom, clear the data and delvik cache at the end.
StaryMuz said:
If you installed a new rom, clear the data and delvik cache at the end.
Click to expand...
Click to collapse
I did this. Every time when I reboot it always comes back to twrp. Strange! In my opinion it is a matter of error: E: Unable to decrypt FBE device. How to overcome it?
Ok, finally I found solution: Installed OrangeFox https://forum.xda-developers.com/t/orangefox-recovery-for-redmi-note-10-sunny-mojito.4293709/
and no problem! Maybe this will be helpfull for somebody else...
dario-20 said:
I did this. Every time when I reboot it always comes back to twrp. Strange! In my opinion it is a matter of error: E: Unable to decrypt FBE device. How to overcome it?
Ok, finally I found solution: Installed OrangeFox https://forum.xda-developers.com/t/orangefox-recovery-for-redmi-note-10-sunny-mojito.4293709/
and no problem! Maybe this will be helpfull for somebody else...
Click to expand...
Click to collapse
That's weird, havoc is not kind of caf rom , hnnn
akoaypinoy said:
That's weird, havoc is not kind of caf rom , hnnn
Click to expand...
Click to collapse
After this installation I cannot boot into recovery! Probably I installed twrp in wrong way for the very first time. But still don't know how to make it right. It means when I install twrp in the wright way I cannot install Havoc... Maybe tommorow I will try to come back to twrp...
The correct way to install TWRP is to run it without installing it first and then install it to the ramdisk. If you do it any other way, you will delete the boot and replace it only with the recovery one. Then the phone can't go anywhere but recovery.
only boot from twrp. dont flash it
inn0ichi said:
only boot from twrp. dont flash it
Click to expand...
Click to collapse
Thank you very much for your responses. What does it mean exactly now in my situation? What steps should be exactly taken now by me?
dario-20 said:
Thank you very much for your responses. What does it mean exactly now in my situation? What steps should be exactly taken now by me?
Click to expand...
Click to collapse
fastboot boot twrp.img
Automatic it reboot to twrp recovery ,next steps is
Go to mount and check if mtp is enable once mtp enable go to your phone storage then paste twrp.image on internal storage of your phone ,once you place that twrp. Disconnect your USB cord on phone then go to advance/flash on ramdisk/then you will click the TWRP img. And flash .
That's it
I recommend a different procedure. Take the boot.img file from the ZIP file of the installed ROM. Then flash it in fastboot with the fastboot flash boot boot.img command. This should boot the ROM normally. You will at that point have a stock recovery of the ROM. To change it you must follow the specific installation procedure, otherwise you will not start the ROM again. If you cannot get the boot.img from the ZIP file, you must reinstall the entire ROM.
akoaypinoy said:
fastboot boot twrp.img
Automatic it reboot to twrp recovery ,next steps is
Go to mount and check if mtp is enable once mtp enable go to your phone storage then paste twrp.image on internal storage of your phone ,once you place that twrp. Disconnect your USB cord on phone then go to advance/flash on ramdisk/then you will click the TWRP img. And flash .
That's it
Click to expand...
Click to collapse
Thanks but: Now I am on OrangeFox recovery (which I cannot boot - it was the last flashed recovery). Typing fastboot boot twrp.img gives back: not found
What do you suggest in this situation?
StaryMuz said:
I recommend a different procedure. Take the boot.img file from the ZIP file of the installed ROM. Then flash it in fastboot with the fastboot flash boot boot.img command. This should boot the ROM normally. You will at that point have a stock recovery of the ROM. To change it you must follow the specific installation procedure, otherwise you will not start the ROM again. If you cannot get the boot.img from the ZIP file, you must reinstall the entire ROM.
Click to expand...
Click to collapse
In the ZIP file of HAVOC ROM there were no boot.img file :-(
So I am still on OrangeFox which I cannot boot. I only can boot the ROM (HAVOC). So if I understand you well I should reinstall my ROM (loosing my data), yes?
Reinstalling the ROM will not delete the data itself. You must not delete data before or after installation.
Reinstallation should not need data deletion.
For what reason are you trying to change the recovery included in the ROM?
I can also offer to pull the boot.img from the ZIP ROM. But you would have to give me a link to the ZIP file you used.
StaryMuz said:
Reinstalling the ROM will not delete the data itself. You must not delete data before or after installation.
Reinstallation should not need data deletion.
For what reason are you trying to change the recovery included in the ROM?
I can also offer to pull the boot.img from the ZIP ROM. But you would have to give me a link to the ZIP file you used.
Click to expand...
Click to collapse
Okay but now I cannot install anything because I have no access to recovery! Maybe I explain what I did:
1. Installed TWRP in wrong way (Error: unable to decrypt FBE device and unable to mount data)
2. Installed OrangeFox (zip file through TWRP)
3. Installed Havoc OS
4. Now I have no access to OrangeFox. I have access only to recovery of Havoc OS ROM. But it is useless because I can do nothing with it.
4. How can I start the new flashing of TWRP the proper way? I don't care about the present HAVOC OS because I have a backup of my all data.
5. I want TWRP or OrangeFox recocery for installing Magisk (rooting) what is now impossible.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Reboot to recovery → I return to the same recovery as above.
dario-20 said:
In the ZIP file of HAVOC ROM there were no boot.img file :-(
So I am still on OrangeFox which I cannot boot. I only can boot the ROM (HAVOC). So if I understand you well I should reinstall my ROM (loosing my data), yes?
Click to expand...
Click to collapse
orangefox is that your recovery now. Orangefox and twrp are recovery both. The difference is that orangefox can no flash the kernel unlike twrp. Please be specific what you are doing,
Orangefox and twrp are recovery
HavocOS is a rom
Before you do make specific, or else you get messed.
dario-20 said:
Okay but now I cannot install anything because I have no access to recovery! Maybe I explain what I did:
1. Installed TWRP in wrong way (Error: unable to decrypt FBE device and unable to mount data)
2. Installed OrangeFox (zip file through TWRP)
3. Installed Havoc OS
4. Now I have no access to OrangeFox. I have access only to recovery of Havoc OS ROM. But it is useless because I can do nothing with it.
4. How can I start the new flashing of TWRP the proper way? I don't care about the present HAVOC OS because I have a backup of my all data.
5. I want TWRP or OrangeFox recocery for installing Magisk (rooting) what is now impossible.
View attachment 5449627View attachment 5449629
Reboot to recovery → I return to the same recovery as above.
Click to expand...
Click to collapse
Everytime you install a new make it read . Because other rom have own recovery. (Ex. Pixelplus) once you install that automatically you have a pe recovery once it reboot , so the proper way to maintain twrp is "flash current twrp" which you can find in advance in twrp recovery. Remember once you flash a new rom don't reboot and go to advance then flash the current twrp. After that reboot.