[GUIDE] How to fix "Find Device storage corrupted. Your device is unsafe now".
How to fix "Find Device storage corrupted. Your device is unsafe now" ?
(At your own risk... I'm not responsible for damage or brick)
Required :
- Be rooted and have TWRP installed !
- Miui Fastboot ROM : xiaomifirmwareupdater.
Tutorial :
- Download the Miui Fastboot ROM corresponding to your current Miui version.
- Extract files from the archive downloaded, open "images" folder and copy "persist.img" file in your smartphone Internal Storage (past the file directly in Internal Storage, not in folder !).
- Reboot in Recovery Mode.
- In your TWRP, open the Terminal (in "Advanced").
- Enter this two commands :
Code:
simg2img /sdcard/persist.img /sdcard/persist_EXT4.img
Code:
dd if=/sdcard/persist_EXT4.img of=/dev/block/bootdevice/by-name/persist
- Reboot your smartphone.
More information :
I got this problem when I restored my Miui backup after try a Custom Android 10 ROM. At each smartphone boot, I got the message "Find Device storage corrupted. Your device is unsafe now", fingerprint unlock was set on "Off", and registered fingerprint(s) was deleted. When I added a new fingerprint, it was registered (until the next boot), but didn't work.
If you do a little research, you can find a other method on some websites where you use fastboot to flash persist.img. I tried and sadly it not work ("FAILED (remote: Error: This image isn't allow download)"):
{
"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"
}
Credit :
- Muz_paray.
My English isn't that good, but thankyou, works great for me, i´m using orange fox not twrp
SkullDead said:
[GUIDE] How to fix "Find Device storage corrupted. Your device is unsafe now".
How to fix "Find Device storage corrupted. Your device is unsafe now" ?
(At your own risk... I'm not responsible for damage or brick)
Required :
- Be rooted and have TWRP installed !
- Miui Fastboot ROM : xiaomifirmwareupdater.
Tutorial :
- Download the Miui Fastboot ROM corresponding to your current Miui version.
- Extract files from the archive downloaded, open "images" folder and copy "persist.img" file in your smartphone Internal Storage (past the file directly in Internal Storage, not in folder !).
- Reboot in Recovery Mode.
- In your TWRP, open the Terminal (in "Advanced").
- Enter this two commands :
Code:
simg2img /sdcard/persist.img /sdcard/persist_EXT4.img
Code:
dd if=/sdcard/persist_EXT4.img of=/dev/block/bootdevice/by-name/persist
- Reboot your smartphone.
More information :
I got this problem when I restored my Miui backup after try a Custom Android 10 ROM. At each smartphone boot, I got the message "Find Device storage corrupted. Your device is unsafe now", fingerprint unlock was set on "Off", and registered fingerprint(s) was deleted. When I added a new fingerprint, it was registered (until the next boot), but didn't work.
If you do a little research, you can find a other method on some websites where you use fastboot to flash persist.img. I tried and sadly it not work ("FAILED (remote: Error: This image isn't allow download)"):
View attachment 4877981
Credit :
- Muz_paray.
Click to expand...
Click to collapse
it doesn't work anymore its says " Invalid spars file format at header magic failed to read spars file" what should do now . tried in orange fox recovery
Svg.Sakib said:
it doesn't work anymore its says " Invalid spars file format at header magic failed to read spars file" what should do now . tried in orange fox recovery
Click to expand...
Click to collapse
I had the same error and found 2 ways to solve it:
1st:
I had flashed the MIUI 11 Rom from August 27 2019. I simply replaced it by the latest stable EU Rom and the error disappeared . Next I flashed the Rom from August 27th back.
2nd:
Find device storage corrupted your device is unsafe now
1. You need Unlocked Bootloader and TWRP. You can boot in TWRP instead of flashing it.
2. Download the fastboot ROM for the device. Extract it and copy persist.img file to the internal memory of the phone. Make sure put the file in internal storage rather than in any folder.
3. Put the phone in fastboot Mode, Power Button and Volume Down key.
4. Boot in TWRP by "fastboot boot twrp.img" command.
5. In the TWRP Main Menu. Go to Advanced ------ Terminal
6. Write the below 2 lines:
simg2img /sdcard/persist.img /sdcard/persist_EXT4.img
dd if=/sdcard/persist_EXT4.img of=/dev/block/bootdevice/by-name/persist
7. Reboot the Phone and check.
Svg.Sakib said:
it doesn't work anymore its says " Invalid spars file format at header magic failed to read spars file" what should do now . tried in orange fox recovery
Click to expand...
Click to collapse
Directly flash it it persist partiton
I have a Xiaomi Redmi 4x with the latest version Miui Global 11.0.2 (NAMMIXM) on Android 7.1.2 N2G47H.
The device is locked and has error: find device storage is corrupted so because of that I can`t add my Xiaomi account to Mi Unlock status and this mean I can't unlock the bootloader, I tried to flash the official ROM again with Mi Flash but is giving me errors so can`t flash the ROM again....
What I can do?
Shepherd_47 said:
I have a Xiaomi Redmi 4x with the latest version Miui Global 11.0.2 (NAMMIXM) on Android 7.1.2 N2G47H.
The device is locked and has error: find device storage is corrupted so because of that I can`t add my Xiaomi account to Mi Unlock status and this mean I can't unlock the bootloader, I tried to flash the official ROM again with Mi Flash but is giving me errors so can`t flash the ROM again....
What I can do?
Click to expand...
Click to collapse
Also booting to twrp is not possible....
Any suggestions?
Shepherd_47 said:
Also booting to twrp is not possible....
Any suggestions?
Click to expand...
Click to collapse
The current recovery is stock recovery
Shepherd_47 said:
The current recovery is stock recovery
Click to expand...
Click to collapse
Did you get any solution, I am sailing on the same boat?
prasanth1947 said:
Did you get any solution, I am sailing on the same boat?
Click to expand...
Click to collapse
Yes
So the solution is to log in to the device on Mi account with the mi account used to unlock the device. So basically you can unlock again the device but with the same Mi account used on the first attempt. If normal log in to Mi account is not possible, try to log in using google (press google icon on the bottom-you must have Google account in the phone, and it must be linked with mi account. After that i just launched miflash_unlock-en-5.5.224.24 and it worked instantly.
I didn't add mi account to mi unlock status even and still was working.
So the key is mi account used for device unlock for the first time- ( DIDN`T WORKED WITH OTHER MI ACCOUNTS)
Shepherd_47 said:
Yes
So the solution is to log in to the device on Mi account with the mi account used to unlock the device. So basically you can unlock again the device but with the same Mi account used on the first attempt. If normal log in to Mi account is not possible, try to log in using google (press google icon on the bottom-you must have Google account in the phone, and it must be linked with mi account. After that i just launched miflash_unlock-en-5.5.224.24 and it worked instantly.
I didn't add mi account to mi unlock status even and still was working.
So the key is mi account used for device unlock for the first time- ( DIDN`T WORKED WITH OTHER MI ACCOUNTS)
Click to expand...
Click to collapse
I will try to post more info about this later, contact me if you need help
Shepherd_47 said:
I will try to post more info about this later, contact me if you need help
Click to expand...
Click to collapse
buy the way this is the solution for UNLOCKING DEVICE, after that is easy, just install Minimal ADB and Fastboot and download recovery for your phone, put recovery in the Minimal ADB and Fastboot folder and open Minimal ADB and Fastboot and run command: fastboot flash recovery recovery.img
after that fastboot boot recovery.img
and you are in TWRP - from there is easy to ,,fix find device storage is corrupt" if you have that error...
working for Redmi Note 7/7S Lavender
Had the same issue with my F3. I know this thread is a bit old. But I am in no really luck. I tried this method but it doesn't work. It says an error " invalid sparse file format at header magic
Failed to read sparse".
ram1MB said:
Had the same issue with my F3. I know this thread is a bit old. But I am in no really luck. I tried this method but it doesn't work. It says an error " invalid sparse file format at header magic
Failed to read sparse".
Click to expand...
Click to collapse
Alternatively, you can flash it with twrp. Copy persist image to internal storage, boot to twrp, select "Flash Image" by pressing the big button located at lower right, select the image file and upon selection the twrp shows another window to choose what are you flashing. Choose "Persist" and slide to flash, it takes just one or two seconds and after that just reboot. I had this problem earlier and fixed by completing these steps.
This thread is very useful. Many thanks to @SkullDead and Muz_paray
ammaralidj said:
Alternatively, you can flash it with twrp. Copy persist image to internal storage, boot to twrp, select "Flash Image" by pressing the big button located at lower right, select the image file and upon selection the twrp shows another window to choose what are you flashing. Choose "Persist" and slide to flash, it takes just one or two seconds and after that just reboot. I had this problem earlier and fixed by completing these steps.
This thread is very useful. Many thanks to @SkullDead and Muz_paray
Click to expand...
Click to collapse
I had this issue as well, thanks a lot for this thread! Fix worked, and I had safely returned to stock.
Worked for me on redmi y1 UGG no sensor, wifi, BT and location was not working post doing this everything started working again, thanks a lot.
taratay said:
I had this issue as well, thanks a lot for this thread! Fix worked, and I had safely returned to stock.
Click to expand...
Click to collapse
i cannot find presist.img file for redmi note 10 mojito. it is not present in rom folder. where to find it
haris43242 said:
i cannot find presist.img file for redmi note 10 mojito. it is not present in rom folder. where to find it
Click to expand...
Click to collapse
Hi haris43242 try this topic https://forum.xda-developers.com/t/persist-file-redmi-note-10.4312093/
my device is MI 11x and I'm facing this issue. I tried all these methods but nothing happens, the error is still there.
also, MI 11x has A/B partition, and TWRP and OrangeFox both don't show the persist partition.
can anyone help me with this?
Related
{
"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"
}
TWRP Collection for Redmi Pro
DISCLAIMER
Code:
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you
GUIDE FOR TWRP install & ROOT
Xiaomi Redmi Pro {ALL VERSIONS} TWRP download and Redmi Pro root
This guide will help you install TWRP and root Redmi Pro, the first step is to install TWRP custom recovery on the Redmi Pro. The process contains quite a few steps, but most of them take just a few seconds.
If it looks daunting, don’t worry, take each step one by one and you’ll come through with TWRP and a rooted Redmi Pro within just a few minutes.
Prerequisites and note
You must have an unlocked bootloader to follow this guide; flashing through fastboot requires an unlocked bootloader. If your Redmi Pro bootloader isn’t unlocked yet, go to the official Xiaomi unlock page to begin the process.
You need to backup anything you don’t want lost to your PC or a TF SD card; for TWRP to work, you may need to factory reset. You will lose all user data. Backup all important data BEFORE you flash the TWRP.{only if you choose twrp 3.0.20}
1. WHATS INCLUDED
PASSWORD IS"kristi6.9"
a.Auto installer for adb commands, adb drivers and fastboot commands– These are the tools that will allow your PC to communicate with your mobile.
View attachment adb-setup-1.4.2.zip
b.Redmi Pro TWRP custom recovery used for rooting and flashing custom ROMs onto Redmi Pro.-links below
c.Redmi Pro root SuperSU.zip– The SuperSU.zip used for rooting Redmi Pro through TWRP recovery(extract it to get supersu binary +supersuapk+supersu premium)link below
2. Install the adb drivers and fastboot commands
Extract the above download.
Run “adb-setup.exe”.
Hit “Y” to all 3 questions.
The Google adb driver installer will then popup. Go ahead and allow and install.
3. Prepare your Xiaomi Redmi Pro
Settings >> About phone >> Tap “MIUI Version” seven times.
Hit the back button. You should then be at the main settings menu.
Go to “Additional settings” >> “Developer options” >> “USB Debugging”.
A warning will pop up. Go ahead and allow.
Plug your phone to PC via USB cable.
You should then see a pop up request on your Redmi Pro to give your PC USB debugging permissions. Go ahead and allow.
4. Copy the TWRP and open the command window
Open Windows Explorer and go to “c:/adb”.
Copy “twrp.img” to “c:/adb”.
IN A BLANK SPACE (not on a filename etc…), hold SHIFT while RIGHT-CLICK
Select “Open command window here”. You should then see a small black window open.
5. Boot into bootloader and fastboot flash the TWRP
In the black command window type “adb reboot bootloader”. Hit Enter. Wait about 10 seconds and you should then see your Redmi Pro says “Fastboot” along with the Xiaomi Mascot.
In the black command window type “fastboot flash recovery twrp.img”. Hit Enter.
You should then see that the file has flashed successfully (OKAY). It all takes just a second. (see pic and video)
6. Boot into TWRP
In the black command window, type “fastboot reboot”. Do not hit Enter yet.
Hold Volume Up on the Xiaomi Redmi Pro while hitting Enter on your PC.
Continue holding Volume Up for about 30 seconds until you see TWRP has booted.
BAM! You’re now booted into TWRP
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Method 2: If you have twrp already installed
1.Put twrp.img in the phone storage
2.Boot on twrp recovery
3. Press install
4.Then install image
5.Check twrp.img in your phone storage
6.And slide to install it.
TWRP 3.0.2-0
Download this zip and extract it
View attachment twrp.3.0.2.0.zip
or download from here
Link here
BUGS
Code:
FIRST RUN CAN SHOW {error mounting}-can be fixed by formatting data
TWRP 3.0.2-2
Download this zip and extract it
View attachment twrp.3.0.2.2.zip
or Download Mega apk from play store
Link on Mega
BUGS
Code:
1.DOESN'T SUPPORT 4GB/128GB VERSION
2.CAN'T SEND FILES WITH MTP
TWRP 3.0.3-0
Download this zip and extract it
View attachment twrp.3.0.3.0.zip
or download
Link here
BUGS
Code:
Yuo tell me
TWRP 3.0.2-0 by @end222
Note: It is ported from Vernee Apollo Lite by @end222-[thanks for everything].
To download go HERE
TWRP 3.1.0 by @end222
Note: THIS IS THE MOST RECOMMENDED version.
To download go https://xiaomi.eu/community/threads/twrp-3-1-0-by-end222.39179/
ATTENTION AFTER INSTALLING TWRP YOU SHOULD INSTALL SUPERSU OR FLASH A CUSTOM ROM ( xiaomi.eu for example)
Root your Xiaomi Redmi Pro
Now that your TWRP is functioning, you can easily root your Xiaomi Redmi Pro.
Download this View attachment SuperSu.zip
Connect Redmi Pro to your PC.
TWRP main menu >> Mount >> Mount USB storage. The Redmi Pro should then show up in Windows File Explorer under This PC / My Computer.
Copy the SuperSU.zip to the root of your Redmi Pro. and extract it.
Now you have supersu apks +supersu2.79.zip (that should be flashed)
TWRP main menu >> Install
Assuming you have the Supersu.2.79.zip. in the base of the internal storage, you should see it at /sdcard. If it’s in another directory, then navigate to whichever directory you extracted the Supersu.2.79.zip to.
Select the Supersu2.79.zip
Swipe to confirm the flash
Credits:
@kristi6.9 #Me for posting ---HIT THANKS
#hanuma50 for twrp 3.0.3.0
Xda Developers #for the forum
BrianAbad #for posting twrp 3.0.2.2 on Miui Forums
@daohoa #for it's first twrp build
Upgrade from TWRP => INSTALL > INSTALL IMAGE >>> check Recovery
any bug fixes ?
The bug fixes:
criszz said:
Upgrade from TWRP => INSTALL > INSTALL IMAGE >>> check Recovery
any bug fixes ?
Click to expand...
Click to collapse
-No more need to format data
-It starts directly in english language
this twrp does not suits for 4/128 version.
on 128g, twrp can not recognize data and storage partitions so it can not make a full wipe to these partitions. So after installing xiaomi.eu rom from any official rom, a lot of programs crashes and gives error. no possiblity to use phone.
thanks for information
sokomind said:
this twrp does not suits for 4/128 version.
on 128g, twrp can not recognize data and storage partitions so it can not make a full wipe to these partitions. So after installing xiaomi.eu rom from any official rom, a lot of programs crashes and gives error. no possiblity to use phone.
Click to expand...
Click to collapse
I use a 3/32gb version and didnt know this problem..I will re-edit post
just noticed i cannot copy twrp bakup, created with this version, from internal to pc with mtp(phone on)
working if backup is on sd-card but not on internal
working when use mtp from twrp
i switced back to first twrp.
criszz said:
just noticed i cannot copy twrp bakup, created with this version, from internal to pc with mtp(phone on)
working if backup is on sd-card but not on internal
working when use mtp from twrp
i switced back to first twrp.
Click to expand...
Click to collapse
I'm sorry but I dont own this project Im just posting it .
not a problem mate, just for people to know
Can we flash incremental OTA update with this TWRP? Also do we need to flash any additional zip file while flashing OTA update?
criszz said:
not a problem mate, just for people to know
Click to expand...
Click to collapse
ok?? thanks for sharing
sakibshahriyar98 said:
Can we flash incremental OTA update with this TWRP? Also do we need to flash any additional zip file while flashing OTA update?
Click to expand...
Click to collapse
? I dont know if we can flash OTAs but I believe not.......if you want you can test it and reply me...?
twrp 3.0.3.0 is out but i don't have account ( i have account but i cannot read capcha, i'm not russian) to download >>> https://translate.googleusercontent...JrhiSRckpRu0LTM8MC6hL3AaPTVYapA#entry57345595
criszz said:
twrp 3.0.3.0 is out but i don't have account ( i have account but i cannot read capcha, i'm not russian) to download >>> https://translate.googleusercontent...JrhiSRckpRu0LTM8MC6hL3AaPTVYapA#entry57345595
Click to expand...
Click to collapse
You can download twrp 3030 from 4pda below
I have not tested it, just sharing.
http://www.filedropper.com/twrpomega3030
kremmit said:
You can download twrp 3030 from 4pda below
I have not tested it, just sharing.
http://www.filedropper.com/twrpomega3030
Click to expand...
Click to collapse
any changelog from previous build??
kristi6.9 said:
any changelog from previous build??
Click to expand...
Click to collapse
Can't find the changelog for the new version.
But it seems to be green in color.
kremmit said:
Can't find the changelog for the new version.
But it seems to be green in color.
Click to expand...
Click to collapse
ok...thanks however?
Error mounting memory via recovery. Thanks for corrected
fays91 said:
Error mounting memory via recovery. Thanks for corrected
Click to expand...
Click to collapse
what version.....
try formating data....
I use your rom version and install
But if I go into recovery and I upgrade the memory can not copied files on
fays91 said:
I use your rom version and install
But if I go into recovery and I upgrade the memory can not copied files on
Click to expand...
Click to collapse
i didnt understood u...
can you tell me the twrp version 3.0.2.0~3.0.2.2~3.0.3.0
......and describe your problem better
{
"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"
}
TWRP 3.3.1 + Root
This topic is the result of work mehanik6 (4PDA) my greetings to him
Tested on Android 9
1 - Remember that everything you do, you do at your own risk
2 - to install TWRP, we will have to unlock the bootloader, all data will be erased, Your device becomes out of warranty
3 - the you need to be installed adb driver For connecting your device to a computer (15 Second ADB Installer v1.5.3.zip)
How to install Best Android ADB Driver on your computer
How to Install Google USB Driver for Windows | ADB and FastBoot
installation
- download the archive delete_verity_key.zip without unpacking put on the sdcard (Attached file) delete_verity_key.zip (130.56 KB)
- download file Fix_vendor.zip without unpacking on the sdcard (Attached file) Fix_vendor.zip (347.64 KB)
- download file Magisk-v20.1.zip without unpacking on the sdcard (Attached file) Magisk-v20.1.zip (5.22 MB)
- download file adb.zip. unzip to your computer desktop adb.zip (22.02 MB)
- Enable developer options in Android
GO to Settings > Swipe down and tap on About Phone Keep tapping on the build number for 7 times
-Enable the USB debugging option
GO to Settings >System -> Developer options on your Android device and enable the USB debugging option.
-Enable “OEM Unlocking”
GO to Settings > Developer options on your Android device and enable the OEM Unlocking option.
when you plug the device into an PC, it will prompt you to allow USB debugging (as seen in the screenshot below).
- allow unlocking of the bootloader
- Decompress a folder adb.zip
- Open a command prompt inside a folder adb. right mouse button l menu, select to open a command window
- copy and paste command [adb devices] (Check Device by Sending below Command)
Example of making sure to connect to the phone
1
Code:
adb devices
2
Code:
adb reboot-bootloader
3
Code:
fastboot devices
If the device does not recognize the phone, it is on "fastboot" android adb interface
Installing [Google ADB Drivers] To Windows 7/8/8.1/10/XP/Vista
- download file Google ADB Drivers.zip
- unlock the bootloader
4
Code:
fastboot flashing unlock
- on the screen text appears, press the Volume + button (all data will be erased)
Attention
The following files(fileFix_vendor.zip+delete_verity_key.zip+Magisk-v20.1.zip) must be placed in an external card, because all phone data will be deleted
Then long press buttons (Power) to turn off the phone
- The bootloader is unlocked. You should see the Orange State (text).
Then turn ON the phone
one more time
- Enable developer options in Android
GO to Settings > Swipe down and tap on About Phone Keep tapping on the build number for 7 times
-Enable the USB debugging option
GO to Settings >System -> Developer options on your Android device and enable the USB debugging option.
when you plug the device into an PC, it will prompt you to allow USB debugging (as seen in the screenshot below).
- Open a command prompt inside a folder adb. right mouse button l menu, select to open a command window
1
Code:
adb devices
2
Code:
adb reboot-bootloader
3
Code:
fastboot devices
- Sew vbmeta.img (the error does not pay attention)
4
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
5
Code:
fastboot flash recovery recovery.img
-After completing:
*Long press buttons (Power) to turn off the phone And quickly Boot into TWRP (buttons Power + Volume Up )
By pressing the volume up selects: recovery mode
and pressing the( volume down) to start TWRP
Changes will not be saved language and settings in (TWRP) Only after all stages have been completed
- Back to the section mount
And put a tick next to all sections on which are placed
- go to the section wipe
- click Format the Data
- In the terminal, Type "yes" and confirm (format action) by click the check mark in the lower right corner
- then you need to reboot again in TWRP
Boot into twrp buttons (Power + Volume Up )
By pressing the volume up selects: recovery mode
and pressing the( volume down) to start TWRPone more time
- Go to the section mount
And put a tick next to all sections on which are placed
Back to install
- Flash archive delete_verity_key.zip
- Flash archive Fix_vendor.zip
- Flash archive Magisk-v20.1.zip (Data again to not encrypt)
- Restart the phone
Like everything, use
NEXT
[GUIDE] CUBOT X19
I just rooted my phone and this guide was very helpful.
- After formatting your phone, boot into recovery through TWRP as my phone keeps bringing up the "no command" error screen if I use "Vol Up + Power"
- When that happens, hold power button for 10 secs, your phone will either turn off or reboot, flash TWRP again and continue.
Successfully Installed TWRP 3.3.1 with SP tool what is did After selecting scatter file from stock firmware i replaced the stock recovery and edit the partition size in the scatter fie for recovery and changed the default path from sp tool default was Recovery-verified i switch it to the Recovery.img that i replaced it with.
Having issues: At the top of the screen its written in red letters as overlay: "TEE key not write Google key not write"
I already applied the "fix Orange state" fix.
Any ideas?
Actually I am using a CubotX19 S and finally I went back to stock rom. That fixed the issue.
However, when I flashed Stockrom I noticed at loading of MT6763 scatterfile, that there are 2 sections having "tee" in their names (see screenshot).
Maybe it would be enough to just flash one or both of those two sections.
I did not do any further research, but maybe this hint os of help for others .
BTW: my screenshot says "Download only" in the Droplist. Actually I flashed using "Firmware Upgrade"
best regards,
bul
where do i get the vbmeta file from?
brezzz said:
where do i get the vbmeta file from?
Click to expand...
Click to collapse
recovery.img + vbmeta.img in folder adb.zip above
or https://www.mediafire.com/file/owuv9h2444w264y/adb.zip/file
flashing vbmeta failed "this partition doesnt exist"
kusti420 said:
flashing vbmeta failed "this partition doesnt exist"
Click to expand...
Click to collapse
Try the following at your own risk
You might have a problem partitioning the phone memory
format your phone
flash your phone
select : format all + download
the latest firmware for CUBOT X19 upgrade 2020-04-21
format your phone
Then try again according to the instructions in the next topic
TWRP 3.3.1 + Root CUBOT X19
karim.a said:
Try the following at your own risk
You might have a problem partitioning the phone memory
format your phone
flash your phone
select : format all + download
View attachment 5188523
the latest firmware for CUBOT X19 upgrade 2020-04-21
format your phone
Then try again according to the instructions in the next topic
TWRP 3.3.1 + Root CUBOT X19
Click to expand...
Click to collapse
hmm, i tried it just like it said, still cant see a vbmeta partition
karim.a said:
Try the following at your own risk
You might have a problem partitioning the phone memory
format your phone
flash your phone
select : format all + download
View attachment 5188523
the latest firmware for CUBOT X19 upgrade 2020-04-21
format your phone
Then try again according to the instructions in the next topic
TWRP 3.3.1 + Root CUBOT X19
Click to expand...
Click to collapse
also i saw someone say that this vbmeta is android 9 thing, but cubot x19 came with android 8.1, should it even have the vbmeta partition? how could i create that partition?
My friend kusti420, follow the instructions below, including upgrading the phone to Android 9 . If your phone has a android 8
Try the following at your own risk
You might have a problem partitioning the phone memory
format your phone
flash your phone
select : format all + download
the latest firmware for CUBOT X19 upgrade 2020-04-21
format your phone
Then try again according to the instructions in the next topic
TWRP 3.3.1 + Root CUBOT X19
For one reason or another, my serial number of my phone is 0123456789ABCDEF and I can't flash the recovery, neither boot from it, nor flash the modified firmware with it.
I tried to flash vbmeta, but it did not do anything.
chartek1 said:
For one reason or another, my serial number of my phone is 0123456789ABCDEF and I can't flash the recovery, neither boot from it, nor flash the modified firmware with it.
Click to expand...
Click to collapse
How to find phones serial number or IMEI number
Step 1. Open the Phone app.
Step 2. Dial *#06# on the keypad.
Step 3. Details about your devices IMEI and serial number will automatically appear on the screen.
chartek1 said:
I tried to flash vbmeta, but it did not do anything.
Click to expand...
Click to collapse
format your phone
flash your phone if model number CUBOT X19
the latest firmware for CUBOT X19 upgrade 2020-04-21
select : format all + download
format your phone
Then try again according to the instructions in the next topic
TWRP 3.3.1 + Root CUBOT X19
karim.a said:
format your phone
flash your phone if model number CUBOT X19
the latest firmware for CUBOT X19 upgrade 2020-04-21
select : format all + download
format your phone
Then try again according to the instructions in the next topic
TWRP 3.3.1 + Root CUBOT X19
Click to expand...
Click to collapse
Trash, description on two pages, but no link to TWRP, much to do, nothing to get from./translate/
user132 said:
Successfully Installed TWRP 3.3.1 with SP tool what is did After selecting scatter file from stock firmware i replaced the stock recovery and edit the partition size in the scatter fie for recovery and changed the default path from sp tool default was Recovery-verified i switch it to the Recovery.img that i replaced it with.
Click to expand...
Click to collapse
How do i adjust the file?
karim.a said:
format your phone
flash your phone if model number CUBOT X19
the latest firmware for CUBOT X19 upgrade 2020-04-21
select : format all + download
format your phone
Then try again according to the instructions in the next topic
TWRP 3.3.1 + Root CUBOT X19
Click to expand...
Click to collapse
Should I tick the preloader? I have heared that it might brick the device.
chartek1 said:
Should I tick the preloader? I have heared that it might brick the device.
Click to expand...
Click to collapse
I tick the preloader? NOIf the current Firmware (Stock ROM) for the phone is android 9Instructions to InstallCharge the device battery up to 50%
Make sure you follow and download all the required files and flash tools on your PC.
Open the flash tool exe file to open the SP Flash Tool User Interface
Tap on the Download option and load both the download agent and the scatter text file in the scatter-loading section.
Once you load the file, click the Download button
To start the upgrade process of stock ROM on your Cubot X19, you need to turn off your device and hold the Volume Down and Volume Up key together and Connect your Phone to PC/Laptop using USB Cable (Keep the Volume Down and Volume Up button until your computer detects the phone.)
When the phone connects, your device will start upgrading the stock firmware
Wait for a few minutes, If you see a green button on your flash tool which means the upgrading process has been completed.
That’s it! You can reboot your Cubot X19
It haves antirollback active.
CN Thread with info.
Direct Download Drive Mirror MEGA Mirror
Can someone make a tutorial post on how to install it?
souma_rox said:
Can someone make a tutorial post on how to install it?
Click to expand...
Click to collapse
It can be installed by original cn recovery, but i didn't try cause of anti-rollback
I hope they make global one to because its already 6 months with no updates...
is it global or chinese version?
Questafa said:
is it global or chinese version?
Click to expand...
Click to collapse
Chinese version.
Has anyone try whether gapps and twrp work on this rom?
I installed this ROM it has almost all languages, very good ROM only the gyroscope that didn't work
Enviado de meu Pixel 2 XL usando o Tapatalk
The installation's process and some details [TWRP, ROOT, GAPPS]
Hey!
I finally install and run the beta on my device. The process is very simple and easy to follow:
1. Get the stock rom on your device without root. You will have to do a full wipe of your data and cache from the Recovery. If you have installed a GSI (as me) you can simply use the Unbrick Tool shared on XDA. After that, just flash from a OTG device in the stock recovery the rom. It should install normally (I did it about three times). Let the device restart normally and configure it.
2. At this point, you will have your device working with the android 10 beta without Google Services and root. To get them, follow the next steps. In the developer's settings enable the usb depuration and reboot into the bootloader menu (if you are here, you don't need a guide to do this).
Once in the bootloader, you will have to type the next commands from a PC:
Code:
fastboot oem nubia_unlock NUBIA_NX629J
Code:
fastboot flash recovery [URL="https://forum.xda-developers.com/red-magic-3/development/recovery-unofficial-twrp-nubia-red-t3962482"]twrp.img[/URL]
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
You can extract the vbmeta.img from the package of the beta.
You should can boot the custom recovery without problems. There is an importante failure at this point. I can't acces to the data of the sdcard of my device. It could be a problem if you flash a wrong module in magisk and you can't delete it from the recovery.
To get the gapps working and root in the device, flash the "pico" package from the open gapps project page and flash the last version of magisk (maybe this could be the cause of the encrypted data in the twrp, I will be experimenting other options (the most evident thing is that the recovery is not the correct ones for this rom).
3. Just reboot the device and enjoy the new android 10 experience on Red Magic 3. You shold be able to proceed to finish the setup and install all the apps you want. The are some things that didn't work for me: some syncs with the google account (Google Keep, Calendar, etc.), auto-rotation (gyroscope), the music notification panel, various notifications, etc. You can't recover your apps and data from a past backup, the rom doesn't give the storage permission to the Google Play Services, so that's the problem. Just install them from the playstore. You will have to reboot one time before use the play store normally.
I hope the developers of Nubia could make a fully working global rom for this great device. Until then, we have this new option to get the best experience of RM3.
Important: If you just don't like the rom and you would like to downgrade to android 9, you will have to use the unbrick tool in order to avoid a softbrick caused by the anti-rollback system. I tried and it works, but after the program finished the unbrick process the phone started to boot into a black screen, only lighting up the led in a green colour. It was strange and I believed that my phone was bricked without possibility to recover it. After a few tries to reboot the device pressing the power button, I was able to boot without problems into the 2.07 global rom europe version.
{
"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"
}
Perseo99 said:
Hey!
I finally install and run the beta on my device. The process is very simple and easy to follow:
1. Get the stock rom on your device without root. You will have to do a full wipe of your data and cache from the Recovery. If you have installed a GSI (as me) you can simply use the Unbrick Tool shared on XDA. After that, just flash from a OTG device in the stock recovery the rom. It should install normally (I did it about three times). Let the device restart normally and configure it.
2. At this point, you will have your device working with the android 10 beta without Google Services and root. To get them, follow the next steps. In the developer's settings enable the usb depuration and reboot into the bootloader menu (if you are here, you don't need a guide to do this).
Once in the bootloader, you will have to type the next commands from a PC:
You can extract the vbmeta.img from the package of the beta.
You should can boot the custom recovery without problems. There is an importante failure at this point. I can't acces to the data of the sdcard of my device. It could be a problem if you flash a wrong module in magisk and you can't delete it from the recovery.
To get the gapps working and root in the device, flash the "pico" package from the open gapps project page and flash the last version of magisk (maybe this could be the cause of the encrypted data in the twrp, I will be experimenting other options (the most evident thing is that the recovery is not the correct ones for this rom).
3. Just reboot the device and enjoy the new android 10 experience on Red Magic 3. You shold be able to proceed to finish the setup and install all the apps you want. The are some things that didn't work for me: some syncs with the google account (Google Keep, Calendar, etc.), auto-rotation (gyroscope), the music notification panel, various notifications, etc. You can't recover your apps and data from a past backup, the rom doesn't give the storage permission to the Google Play Services, so that's the problem. Just install them from the playstore. You will have to reboot one time before use the play store normally.
I hope the developers of Nubia could make a fully working global rom for this great device. Until then, we have this new option to get the best experience of RM3.
Important: If you just don't like the rom and you would like to downgrade to android 9, you will have to use the unbrick tool in order to avoid a softbrick caused by the anti-rollback system. I tried and it works, but after the program finished the unbrick process the phone started to boot into a black screen, only lighting up the led in a green colour. It was strange and I believed that my phone was bricked without possibility to recover it. After a few tries to reboot the device pressing the power button, I was able to boot without problems into the 2.07 global rom europe version.
Click to expand...
Click to collapse
Can I install this on red magic 3s?
does anyone know gyro solution for this ROM just missing that so you can use as daily ROM
Enviado de meu Pixel 2 XL usando o Tapatalk
Hi. I just installed the rom without formatting the phone and the code of the screen lock that was previously 6 figures has become 4 and they are not the first 4 of the previous one.
Does anyone know what it can be or am I going to have to format it?
Questafa said:
Hi. I just installed the rom without formatting the phone and the code of the screen lock that was previously 6 figures has become 4 and they are not the first 4 of the previous one.
Does anyone know what it can be or am I going to have to format it?
Click to expand...
Click to collapse
I don't see another option for your situation
---------- Post added at 05:42 PM ---------- Previous post was at 05:40 PM ----------
akashc3303 said:
Can I install this on red magic 3s?
Click to expand...
Click to collapse
No. it's for RM3... I don't know if there is an android 10 beta for 3S
akashc3303 said:
Can I install this on red magic 3s?
Click to expand...
Click to collapse
For red magic 3s is that ROM https://bbs.nubia.com/thread-2578208-1-2.html
http://romdownload.nubia.com/红魔3S/V3.01/NX629J-update.zip
Enviado desde mi NX629J mediante Tapatalk
Thank you for your useful post. After reading it, I tried the ROM myself, with about the same results. Then I used the unbrick tool to reverse to Android 9.
Things that didn't work for me in the beta:
- Bluetooth kept restarting every 10 seconds, I couldn't use my Bluetooth headset
- Some incompatibility between the ROM and GAPPS, Google Play working only on occasions; after installing some stuff some apps refused to start ( Phone, Settings, Outlook etc).
It was an interesting experience, but it can't be used as the daily driver, at least not for me.
Detection 10 error
hoichemgio9x said:
Detection 10 error
Click to expand...
Click to collapse
What does it mean?
Nightpwish said:
What does it mean?
Click to expand...
Click to collapse
Button touch in YouTube, time screen , etc
Try V3.25
Perseo99 said:
Hey!
I finally install and run the beta on my device. The process is very simple and easy to follow:
1. Get the stock rom on your device without root. You will have to do a full wipe of your data and cache from the Recovery. If you have installed a GSI (as me) you can simply use the Unbrick Tool shared on XDA. After that, just flash from a OTG device in the stock recovery the rom. It should install normally (I did it about three times). Let the device restart normally and configure it.
2. At this point, you will have your device working with the android 10 beta without Google Services and root. To get them, follow the next steps. In the developer's settings enable the usb depuration and reboot into the bootloader menu (if you are here, you don't need a guide to do this).
Once in the bootloader, you will have to type the next commands from a PC:
Code:
fastboot oem nubia_unlock NUBIA_NX629J
Code:
fastboot flash recovery [URL="https://forum.xda-developers.com/red-magic-3/development/recovery-unofficial-twrp-nubia-red-t3962482"]twrp.img[/URL]
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
You can extract the vbmeta.img from the package of the beta.
You should can boot the custom recovery without problems. There is an importante failure at this point. I can't acces to the data of the sdcard of my device. It could be a problem if you flash a wrong module in magisk and you can't delete it from the recovery.
To get the gapps working and root in the device, flash the "pico" package from the open gapps project page and flash the last version of magisk (maybe this could be the cause of the encrypted data in the twrp, I will be experimenting other options (the most evident thing is that the recovery is not the correct ones for this rom).
3. Just reboot the device and enjoy the new android 10 experience on Red Magic 3. You shold be able to proceed to finish the setup and install all the apps you want. The are some things that didn't work for me: some syncs with the google account (Google Keep, Calendar, etc.), auto-rotation (gyroscope), the music notification panel, various notifications, etc. You can't recover your apps and data from a past backup, the rom doesn't give the storage permission to the Google Play Services, so that's the problem. Just install them from the playstore. You will have to reboot one time before use the play store normally.
I hope the developers of Nubia could make a fully working global rom for this great device. Until then, we have this new option to get the best experience of RM3.
Important: If you just don't like the rom and you would like to downgrade to android 9, you will have to use the unbrick tool in order to avoid a softbrick caused by the anti-rollback system. I tried and it works, but after the program finished the unbrick process the phone started to boot into a black screen, only lighting up the led in a green colour. It was strange and I believed that my phone was bricked without possibility to recover it. After a few tries to reboot the device pressing the power button, I was able to boot without problems into the 2.07 global rom europe version.
View attachment 5030877
View attachment 5030879
View attachment 5030881
View attachment 5030883
View attachment 5030885
View attachment 5030887
Click to expand...
Click to collapse
Hey Buddy,
You are on V3.22, Why don't you try V3.25 the latest one and share us your experiences.
I like your review. Thumbs up brother.
V3.25
jlorf7 said:
It haves antirollback active.
CN Thread with info.
Direct Download Drive Mirror MEGA Mirror
Click to expand...
Click to collapse
Could you provide us the latest update v3.25 link?
Thank you.
Thanks to:
chaosmaster / k4y0z: GitHub / XDA
xyzz / xyz`: GitHub / XDA
Dinolek: GitHub / XDA
How to install:
1. Download the attached file: VD171_MTK-bypass.zip.
2. Extract the file and open the folder.
3. Run and install python: python-3.9.1-amd64.exe.
Keep atention: You need to select "Add Python to PATH" before starting the installation.
{
"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"
}
4. Open cmd or powershell and execute this command:
pip install pyusb pyserial json5
5. Go to the Driver folder and right-click on the cdc-acm.inf file, then click Install and then, close window.
6. Run and install filter wizard: libusb-win32-devel-filter-1.2.6.0.exe.
7. Launch filter wizard.
8. Select Install a device filter and click Next.
9. Connect powered off phone with volume- button to boot in EDL mode.
10. Once you see new MediaTek USB Port in the list, select it and click Install.
Now, you are ready for bypassing EDL !
How to bypass:
1. Go to the Bypass folder. Run the script: bypass.bat.
2. Connect powered off phone with volume- button to boot in EDL mode.
3. Once you get "Protection disabled" at the end, without disconnecting phone and usb, run SP Flash Tool.
4. Once the SP Flash Tool opens, click Options > Options > Connection.
5. Select UART mode and select Baud rate to 921600.
Now, you are ready for flashing !
How to update:
1. Download latest release of the tool: https://github.com/MTK-bypass/bypass_utility/releases/latest
2. Download latest release of payloads: https://github.com/MTK-bypass/exploits_collection/releases/latest
3. Extract the content of both files to the Bypass folder.
Now, you are updated !
How does the bypass work?
Dissecting a MediaTek BootROM exploit
A bricked Xiaomi phone led me to discover a project in Github that uses a MediaTek BootROM exploit that was undocumented. The exploit was found by Xyz, and implemented by Chaosmaster. The initial exploit was already available for quite a while. Since I have managed to revive my phone, I am documenti
tinyhack.com
All Credits To:
chaosmaster / k4y0z: GitHub / XDA
xyzz / xyz`: GitHub / XDA
Dinolek: GitHub / XDA
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
#NoAuth #NoAuthentication #No-Auth #No-Authentication #MediaTek #Xiaomi
#MiAuth #MiAuthentication #Mi-Auth #Mi-Authentication #XiaoMiAuth #free
#XiaoMiAuthentication #XiaoMi-Auth #XiaoMi-Authentication #unbricking
#unbricked #unbrick #unbrickingru #unbrickedru #unbrickru #remoterepair98
#MTK #MT6572 #MT6735 #MT6737 #MT6739 #MT6750 #MT6765 #MT6762
#MT6761 #MT6768 #MT6771 #MT6785 #MT8127 #MT8163 #MT8173 #MT8695
Redmi 10x 5 (ATOM) still not supported
[2021-02-07 06:26:57.702746] Waiting for bootrom
[2021-02-07 06:27:05.293534] Found port = COM3
Traceback (most recent call last):
File "C:\Users\Administrator\Downloads\VD171_MTK-bypass-v1.3\VD171_MTK-bypass-v1.3\Bypass\main.py", line 169, in <module>
main()
File "C:\Users\Administrator\Downloads\VD171_MTK-bypass-v1.3\VD171_MTK-bypass-v1.3\Bypass\main.py", line 44, in main
device.handshake()
File "C:\Users\Administrator\Downloads\VD171_MTK-bypass-v1.3\VD171_MTK-bypass-v1.3\Bypass\src\device.py", line 88, in handshake
self.check(self.read(1), to_bytes(0x5F))
File "C:\Users\Administrator\Downloads\VD171_MTK-bypass-v1.3\VD171_MTK-bypass-v1.3\Bypass\src\device.py", line 84, in check
raise RuntimeError("Unexpected output, expected {} got {}".format(gold, test))
RuntimeError: Unexpected output, expected 0x5f got 0xa0
Press any key to continue . . .
kurosaberex said:
Redmi 10x 5 still not supported
Click to expand...
Click to collapse
Unhappy, MT6875 is not supported yet.
Probably it will be supported too soon
VD171 said:
Unhappy, MT6875 is not supported yet.
Probably it will be supported too soon
Click to expand...
Click to collapse
will gladly wait for it hope it comes soon
kurosaberex said:
will gladly wait for it hope it comes soon
Click to expand...
Click to collapse
I hope to see all existing devices supported as well.
This EDL authenticated mode is really disappointing.
We love Xiaomi.
But, we are hostages to Xiaomi. Sad...
Should I Format All + Download??
-glyne- said:
Should I Format All + Download??
Click to expand...
Click to collapse
NO.
Never try to flash in "format all" mode.
Or you will lose all identifications of your device, like imei and mac.
If you are facing "PMT changed" message, your device has an older scatter file inside it.
This is because there is any modification to the scatter file you are using to the scatter file used before.
There are some minor changes to the MIUI 11 scatter file for MIUI 12, but nothing significant.
You can flash using "firmware upgrade" mode.
But, bootloader will be LOCKED again and userdata will be erased.
If you want to backup the state of unlocked bootloader and then restore it.
Just follow this guide before the "firmware upgrade": https://forum.xda-developers.com/t/...omi-redmi-10x-4g-xiaomi-redmi-note-9.4221065/
VD171 said:
NO.
Never try to flash in "format all" mode.
Or you will lose all identifications of your device, like imei and mac.
If you are facing "PMT changed" message, your device has an older scatter file inside it.
This is because there is any modification to the scatter file you are using to the scatter file used before.
There are some minor changes to the MIUI 11 scatter file for MIUI 12, but nothing significant.
You can flash using "firmware upgrade" mode.
But, bootloader will be LOCKED again and userdata will be erased.
If you want to backup the state of unlocked bootloader and then restore it.
Just follow this guide before the "firmware upgrade": https://forum.xda-developers.com/t/...omi-redmi-10x-4g-xiaomi-redmi-note-9.4221065/
Click to expand...
Click to collapse
Or if firmware upgrade doesn't work, he can backup IMEI, after format and flash is done, He can flash the persist, protect1 protect2 nvdata and nvcfg partitions which he backup-ed, this way he doesn't lose IMEI, successfully unbricks device.
Communos said:
Or if firmware upgrade doesn't work, he can backup IMEI, after format and flash is done, He can flash the persist, protect1 protect2 nvdata and nvcfg partitions which he backup-ed, this way he doesn't lose IMEI, successfully unbricks device.
Click to expand...
Click to collapse
Don't forget to backup seccfg partition.
It controls the state of locked/unlocked bootloader: https://forum.xda-developers.com/t/...omi-redmi-10x-4g-xiaomi-redmi-note-9.4221065/
Here, you can find the full list of the most important partitions to backup: https://forum.xda-developers.com/t/...lin-device-redmi-10x-4g-redmi-note-9.4229633/
VD171 said:
Don't forget to backup seccfg partition.
It controls the state of locked/unlocked bootloader: https://forum.xda-developers.com/t/...omi-redmi-10x-4g-xiaomi-redmi-note-9.4221065/
Here, you can find the full list of the most important partitions to backup: https://forum.xda-developers.com/t/...lin-device-redmi-10x-4g-redmi-note-9.4229633/
Click to expand...
Click to collapse
Thanks
@VD171 sir i'm on Miui china 12.0.8 when i run libusb and turn off my phone and hold volume - button then connect the cable it boot into fastboot mode instead of booting into edl mode pls help
MerliinTop1 said:
@VD171 sir i'm on Miui china 12.0.8 when i run libusb and turn off my phone and hold volume - button then connect the cable it boot into fastboot mode instead of booting into edl mode pls help
Click to expand...
Click to collapse
Try other combinations, like vol up or vol up + vol down.
I'm not sure, I'm on global 12.0.6.0 and the combination for EDL mode is just vol down.
VD171 said:
Try other combinations, like vol up or vol up + vol down.
I'm not sure, I'm on global 12.0.6.0 and the combination for EDL mode is just vol down.
Click to expand...
Click to collapse
Tried em all still not working sir
MerliinTop1 said:
Tried em all still not working sir
Click to expand...
Click to collapse
Are you sure your device is properly detected?
Are you sure usb driver is properly installed?
VD171 said:
Are you sure your device is properly detected?
Are you sure usb driver is properly installed?
Click to expand...
Click to collapse
Yeah its detected i can hear the detecet sound and i installed the driver u attached
MerliinTop1 said:
Yeah its detected i can hear the detecet sound and i installed the driver u attached
Click to expand...
Click to collapse
Then, I have no ideia what is the problem.
You need to keep trying.
VD171 said:
Then, I have no ideia what is the problem.
You need to keep trying.
Click to expand...
Click to collapse
Ok sir thx for ur attention
MerliinTop1 said:
Ok sir thx for ur attention
Click to expand...
Click to collapse
Try another cable.
Try another usb port.
Try usb 2.0. Try usb 3.0.
Try another computer.
If results are exactly same, probably you have a problem with your device.
VD171 said:
Try another cable.
Try another usb port.
Try usb 2.0. Try usb 3.0.
Try another computer.
If results are exactly same, probably you have a problem with your device.
Click to expand...
Click to collapse
I tried diff ports still same result and i'm using the original cable its still new
I didnt try another computer tbh
But i think the miui china 12.0.8 have something diff.....they may f**kd the edl mode cuz they know its bypass-able however ill wait the new update (A11) which should come soon(1 or 2 days) and try again since it has a new firmware than the previous 12.0.6 firmware and see whats gonna happen
Btw I'm trying to do this just to flash Eng rom and fix imei which i lost when i was trying to flash miui china with sp tool.....imei being lost doesn't effect on edl mode no?
MerliinTop1 said:
I tried diff ports still same result and i'm using the original cable its still new
I didnt try another computer tbh
But i think the miui china 12.0.8 have something diff.....they may f**kd the edl mode cuz they know its bypass-able however ill wait the new update (A11) which should come soon(1 or 2 days) and try again since it has a new firmware than the previous 12.0.6 firmware and see whats gonna happen
Btw I'm trying to do this just to flash Eng rom and fix imei which i lost when i was trying to flash miui china with sp tool.....imei being lost doesn't effect on edl mode no?
Click to expand...
Click to collapse
If you lost your imei, you can't recover it forever.
Only Xiaomi Centre can recover it.
I'm sorry.
Thanks for @urbanman2004 guide for Poco X3 Pro. Some sentences still needed, so keeping it similar.
This guide provides photos & screenshots.
Simulate all process and reduce misunderstanding.
Spoiler: Disclaimer
* May loose warranty after unlock according to Xiaomi policy of the country you bought phone from. Check it yourself.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected users.
Section 1: Unlock bootloader
(Works for most Xiaomi/Redmi/Poco phones)
Keep phone with more than 60% battery.
Spoiler: Click to show
1. Register Xiaomi account on PC or Phone doesn't matter. (Use same account in all steps)
Might ask SMS verification. Keep phone number for this Mi Account until all unlock process done and successfully booted into MIUI after step 21.
Click to expand...
Click to collapse
2. On phone, sign in your Mi Account from setting. (Use same account in all steps)
Spoiler
{
"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"
}
3. Turn on Developer option:
Spoiler
Settings→ About Phone (My Device)→ tap on MIUI version (For POCO) until it says Developer options enabled at the bottom.
4. Turn ON "Find my device"
Spoiler
5. Back out to Settings, Additional Settings→ Developer options→ Mi Unlock status.
Spoiler
6. DON'T DO STEP 6 ANYMORE after done it ONCE. Will reset countdown timer if you do that.
DON'T DO STEP 6 ANYMORE after done it ONCE. Will reset countdown timer if you do that.
SIM card inside phone with mobile data doesn't need to be the one linked to Mi-account. Can put a different SIM card as long as it can use mobile data.
Only during step 6 you turn off WIFI and turn on mobile data.
Can do whatever you want to WIFI and mobile data anytime before and after step 6. There's no restriction other than step 6.
Can remove your SIM card once step 6 was done. But you still need the number linked to Mi-Account accessible to receive SMS if Mi-Account ask for verification.
7. Wait for 7 days (Day 1). DO NOT LOG OUT your Mi-Account on your phone.
Try not to use phone too much as later will do factory reset and loose all data.
Or backup manually. Not gonna write how to backup.
No need to connect internet (mobile data and WIFI) all the time.
Can use your phone
Can even power off phone in the meantime. (Thanks for @kamild_ answer)
Spoiler
8. Wait for 7 days (Day 2). DO NOT LOG OUT your Mi-Account on your phone.
9. Wait for 7 days (Day 3). DO NOT LOG OUT your Mi-Account on your phone.
10. Wait for 7 days (Day 4). DO NOT LOG OUT your Mi-Account on your phone.
11. Wait for 7 days (Day 5). DO NOT LOG OUT your Mi-Account on your phone.
12. Wait for 7 days (Day 6). DO NOT LOG OUT your Mi-Account on your phone.
13. Wait for 7 days (Day 7). DO NOT LOG OUT your Mi-Account on your phone.
14. Download Xiaomi Unlock tool for Windows PC.
Direct download link (English Version 5.5.224.55)
Spoiler
Spoiler: Linux and macOS users
XiaoMiTool (v2)
https://www.xiaomitool.com/
https://github.com/francescotescari/XiaoMiToolV2
15. Extract all files into short-named folder. Go into folder and double click on miflash_unlock.exe
Different versions, double click on batch_unlock.exe
Spoiler
16. Sign in your Mi Account. (Use same account in all steps)
Spoiler
17. Connect phone with official USB cable to PC. Check on PC if see device.
Turn OFF all locks (screen lock, face lock, fingerprint, pin, bluetooth lock.)
Turn ON "Find my device"
Logout Google
If not detected, do as in spoiler:
Spoiler
Double click on MiUsbDriver.exe
Should see your phone now.
Reboot your PC.
or Google's latest USB drivers for Windows if it else fails
NOTE: If Windows does not recognize the device due to it automatically installing the wrong "Kedacom Device Driver" then you will have to manually install the drivers for "Android ADB Interface/Android Bootloader Interface".
Backup your data from your phone now. You will loose ALL your data on your phone after step 20.
Click to expand...
Click to collapse
18. Shutdown/ Power off phone normally manually.
When screen turns all black for about 30 seconds, hold Vol down + Power button together to enter Fastboot mode.
(Picture from GSMarena)
Should see Fastboot on phone screen
Spoiler
19. Connect your phone with official USB cable to PC. Should see on PC a device listed. (Locked)
Spoiler
If not detected, do as in spoiler:
Spoiler
Double click on MiUsbDriver.exe
Connect phone to computer via official USB cable, and confirm your phone shows up recognized as "Android Bootloader Interface" (in Device Manager)
Reboot your PC.
or Google's latest USB drivers for Windows if it else fails
NOTE: If Windows does not recognize the device due to it automatically installing the wrong "Kedacom Device Driver" then you will have to manually install the drivers for "Android ADB Interface/Android Bootloader Interface".
WARNING !!! From the step later, you will loose ALL your data on your phone. Backup your data from your phone.
Click to expand...
Click to collapse
Take out microSD card from device in case something went wrong and destroy microSD card.
Click to expand...
Click to collapse
20. Press Unlock, Unlock, Unlock anyway, Unlock anyway. (If you are worried of what it's warning you, don't unlock and don't think of custom Roms or root.)
Spoiler
If see this or some hours left, wait for remaining countdown hours (count it yourself) and start from step 17 again.
The countdown is done on Xiaomi server. Can close the unlock program during the meantime.
Exit Fastboot mode:
Spoiler
Unplug phone from PC and hold power button until screen turns black. Will boot into MIUI.
21. Wait phone boot up, or press Reboot phone if it did not reboot itself.
If you see this after boot up, use Wifi or insert SIM card with mobile data access and enter your Mi Account password.
##End of Unlock Bootloader process
Donate if you find it helpful: paypal.me/pl1992aw
Updated to work with MIUI 12~13 or Android 11~12.0/12.1 custom ROMs
Unlock bootloader to do the followings.
Keep phone with more than 60% battery.
Section 2: Clean Flash custom ROMs
(Official Recovery ROMs can be flashed with same method)
Spoiler: Click to show
Make it simple using program mentioned in INDEX thread.
XiaomiADBFastbootTools (Java)
https://github.com/Szaki/XiaomiADBFastbootTools
If you don't trust the tools or link below,
upload files to Virus Total
or turn on Antivirus
or do manual way urbanman2004 written.
1. Download here:
https://androidfilehost.com/?fid=8889791610682940341
Original github source: (not maintained anymore)
https://github.com/Szaki/XiaomiADBFastbootTools/releases
Spoiler
2. For this program to work, install Oracle Java or OpenJDK (Mentioned in Readme)
Spoiler
Here use Windows to as demo.
Oracle Java download here or here (Choose either one to install)
Spoiler
Double click and install that on your Windows.
3. Keep PC connected to internet, find XiaomiADBFastbootTools.jar downloaded and double click on it.
Spoiler
4. Will automatically download SDK Platform Tools.
5. Turn ON USB debugging in Developer options (access mentioned in Unlock bootloader step 5)
Spoiler
Logout Mi Account, Google, all accounts.
Remove all fingerprint, PIN, password, picture password.
Turn OFF Find My Device function.
Backup your data from your phone.
Click to expand...
Click to collapse
6. Connect phone to PC, swipe down notification on phone and tap MTP/ File transfers
Spoiler
Or
If it's your first time doing this, should see this screen. Choose "Always allow from this computer" and press OK.
7. Confirm on PC to see information of your device.
8. Find custom ROM and read all reply and original thread of the Custom ROM. Sometimes firmware requirement and updated info is in replies.
(Step 8, 9 and 12 and links are POCO X3 pro specific)
Click to expand...
Click to collapse
ArrowOS as example: Download on PC Official ArrowOS -vayu ROM for POCO X3 Pro [direct link here].
Check the date and version as well.
Spoiler
If phone is not on MIUI version for required firmware, do additional as spoiler:
Spoiler
Download on PC official MIUI Recovery ROM or MIUI by Xiaomi.eu ROM ZIP (2~6 GB) of POCO x3 pro.
EEA is official ROM
Xiaomi.eu is custom ROM
Click to expand...
Click to collapse
9. Download recovery TWRP from here by Nebrassy for POCO x3 pro.
10. On PC, press "Device" -> "Reboot to" -> "Fastboot"
Should see Fastboot on phone
Spoiler
11. Program on PC should jump to Fastboot tab
If it did not jump to that tab,
Spoiler
click on Fastboot tab and choose "Option" -> "Reload device"
Warning !!! Look at the Anti version:
This is important for Xiaomi/Redmi/Poco phones.
Spoiler: About Anti version
Only Official MIUI ROMs may have ARB index.
Customs ROMs should not have ARB index.
If your device is Anti version: 2,
1) you can flash Rom with Anti Roll Back (ARB) index: 3, 4, 5, 6... etc. and the Anti version will become 3, 4, 5, 6... etc.
2) you can flash Rom with ARB index 2, and the Anti version will remain 2.
3) you CANNOT flash Rom with ARB index 1. Don't use that ROM in anyway, flashing through custom recovery will likely brick your phone.
4) If ARB index is 0, that means no ARB of that ROM. It will not check or change your device Anti version.
Make sure look at ARB index of MIUI ROM and Anti version of your phone. I don't have your phone. You decide to flash.
How to check ROM ARB index is written in the Source.
Source:
https://www.xda-developers.com/xiaomi-anti-rollback-protection-brick-phone/
12. Assume confirm MIUI ROM safe from ARB, click
Choose
for Poco X3 pro.
Change next drop down menu to "recovery".
Do not choose wrong option, or may be in BIG trouble.
Press Flash Image (Some device cannot do this step, check at your device XDA tutorial)
Confirm at the Status " Writing 'recovery' Okay "
13. Boot to TWRP
Phone should boot into TWRP.
Spoiler
14. Copy or Drag MIUI and custom Rom zip into phone Download folder for easy finding.
If PC did not see any folders in your phone from "My Computer" or "This PC", use either options:
Spoiler: microSD card or USB OTG
Copy the ROM zip file in and [put microSD into / connect USB OTG to] your phone, then continue to step 15
Spoiler: ADB sideload
A)
B) Connect phone USB cable to PC.
C) On PC, navigate to folder C:\user\your user name\XiaomiADBFastbootTools\platform-tools\
D) Copy or drag the ROMs.zip files into the folder.
E) Hold keyboard Shift and mouse Right Click in the folder blank space, left click Open command window here
F) In the Command enter the following code in the command window:
adb sideload custom_ROM_name.zip
G) After it's done (shown on phone screen), skip to step 16
15. In TWRP on phone, tap Install
Spoiler
If Firmware did not meet needs of custom ROM, do additional in spoiler
Spoiler
Choose Download folder, or press Select Storage and choose microSD card or USB OTG where you put the ROM, then tap on MIUI ROM zip.
Swipe to confirm Flash
After it's done, press back.
In Download folder, or press Select Storage and choose microSD card or USB OTG where you put the ROM, tap on custom ROM zip.
Swipe to confirm Flash
Wait until it's done
16. Press back, back, until you see Wipe, tap it and then tap Format Data.
Type yes, press enter.
17. Press Reboot System. Wait for like 10~15 minutes until initialization setup shows.
## End of Clean Custom Rom flashing.
Dirty Flash / ROM update
Do this only when developer or users said it can.
Spoiler: Click to show
Spoiler: If using Magisk, do this as well
First disable all Magisk module and reboot to prevent issues.
α) Remove ALL fingerprint, PIN, password, picture password, ALL locks
β) Do Section 2 step 15 with the update custom ROM zip file in your phone storage.
If TWRP or OrangeFox cannot see any folders in your phone, use either options:
Spoiler: microSD card or USB OTG
Copy the ROM zip file in and [put microSD into / connect USB OTG to] your phone and do Section 2 step 15 with the update custom ROM zip file, then do step γ
Spoiler: ADB sideload
A)
B) Connect phone USB cable to PC.
C) On PC, navigate to folder C:\user\your user name\XiaomiADBFastbootTools\platform-tools\
D) Copy or drag the ROMs.zip files into the folder.
E) Hold keyboard Shift and mouse Right Click in the folder blank space, left click Open command window here
F) In the Command enter the following code in the command window:
adb sideload custom_ROM_name.zip
G) After it's done (shown on phone screen), continue step γ
γ) When done, do the following:
δ) Then Reboot System.
## End of Dirty flashing.
Donate if you find it helpful: paypal.me/pl1992aw
Unlock bootloader to do the followings.
Keep phone with more than 60% battery.
Section 3: Install Magisk (Root)
Install steps and methods were written by topjohnwu (Magisk author) here, but still putting picture guide for POCO X3 Pro.
Spoiler: Click to show
1. Download Magisk on you phone, click and install.
Spoiler
Or find this and tap it once
A) the Easy traditional custom recoveries way :
(PC/Computer is not needed)
Spoiler
2A. Rename the downloaded APK file extension to ZIP.
Magisk-vXX.X.apk
↓
Magisk-vXX.X.zip
Click to expand...
Click to collapse
3A. Reboot to custom recoveries (TWRP, OrangeFox, etc)
3A-α) manually
Spoiler
Power off your phone, wait until screen turns black,
press and hold Vol+ and Power button Together (most Xiaomi/Redmi/Poco phones) until screen turns on.
(Picture from GSMarena)
keep holding Vol+ button, release Power button until booted into recovery.
3A-β) or with PC program/command
Spoiler
4A. In custom recovery on phone, tap Install
Spoiler
5A. In Download folder, tap on Magisk-vXX.X.zip.
Swipe to confirm Flash
Wait until it's done
6A. Wipe cache/dalvik
Then Reboot System
B) the Pro Patch image way :
(PC/Computer used)
Spoiler
2B. Choose boot.img and extract from custom Rom/MIUI Rom on PC which match current phone OS.
Connect phone to PC and copy that boot.img into phone Download folder.
3B. In Magisk app, click Install. Select and Patch a file.
Spoiler
4B. Copy the patched file to PC somewhere easy to find.
5B. Open PC program XiaomiADBFastbootTools
1) Select image magisk_patched-*****_*****.img
2) confirm selecting the patched image file name
3) choose boot partition in next drop down menu
4) Flash Image into boot partition, Yes.
Wait for "Writing 'boot' OKAY"
6B. Reboot to system
7. Go into Magisk app and check if it's installed.
Spoiler
8. Voila... or can do something more (Didn't feel the difference, though it said Recommended)
9. Reboot. Voila! Enjoy Magisk
##End of Magisk (Root) installation.
Section 3.5: Update Magisk
For Poco X3 Pro, repeat Section 3.
Donate if you find it helpful: paypal.me/pl1992aw
Reserved... Maybe for troubleshoot
Q. Why not use Mi-Flash?
A. Because one may easily accidently Clean All and Lock with different region MIUI and brick the device.
Go Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40 and see how many users brick their device using Mi-Flash.
Be sure to check ARB index of MIUI.
Q. Why flash MIUI with TWRP not Fastboot?
A. To check you actually had unlocked bootloader. Without unlocked bootloader, you shouldn't be able to boot into TWRP.
Q. Widevine issues?
A. Read threads in spoiler:
Spoiler
You can have Widevine L1 on custom Roms.
https://forum.xda-developers.com/t/4267263/page-2#post-84919939
You can lost Widevine L1 on official MIUI Roms even without unlocking or root.
https://forum.xda-developers.com/t/4281695/
Devices supporting Widevine L1 certificate renewal officially:
POCO X3 Pro (vayu) [Stable V12.5.1.0.RJUMIXM+]
* Cetain devices have been losing Widevine L1 certificate randomly. The reason is unknown to us.
* Certificate renewal is done via Settings -> Passwords & security -> Fingerprint unlock -> Fingerprint payments -> Widevine (L1)
https://xiaomi.eu/community/threads/info-widevine-l1-support.61064/
If your device haven't officially receive MIUI update to 12.5.1.0, try Xiaomi.eu
Read also:
https://xiaomi.eu/community/threads/info-widevine-l1-support.61064/#post-606155
Thanks for your efforts bro..
i just unlocked the bootloader of my poco x3 pro 6/128 global stable(VAYU) and tired to root it with Magisk method before that i found a patched file of boot image from a post and i just directly did the flashing now its stuck in the MIUI logo dont know what to do next anyone can help me out with this,,, and im going to attached the boot image aswell try to look at it if its fine and what should i do next.
Faysal_khan_070 said:
i just unlocked the bootloader of my poco x3 pro 6/128 global stable(VAYU) and tired to root it with Magisk method before that i found a patched file of boot image from a post and i just directly did the flashing now its stuck in the MIUI logo dont know what to do next anyone can help me out with this,,, and im going to attached the boot image aswell try to look at it if its fine and what should i do next.
Click to expand...
Click to collapse
Are you sure your phone is Global? Which country?
What version of MIUI?
How did you flash your boot image?
What partition did you flash the boot image into?
Were you using this one? If yes, flash the boot.img from here into your phone boot partition and see if your phone can boot up.
Boot your phone into Fastboot or TWRP. If you can, there's still hope. Do the step in above Unlock bootloader step 18.
pl1992aw said:
Are you sure your phone is Global? Which country?
What version of MIUI?
How did you flash your boot image?
What partition did you flash the boot image into?
Were you using this one? If yes, flash the boot.img from here into your phone boot partition and see if your phone can boot up.
Boot your phone into Fastboot or TWRP. If you can, there's still hope. Do the step in above Unlock bootloader step 18.
Click to expand...
Click to collapse
YES, im dam sure its GLOBAL and im from Pakistan.
it was the MIUI 12.0.4 BUT Before unlocking it i updated to MIUI 12.0.6
ok so i just followed the MAGISK method and i downloaded a patched file from a post now i don't know where to find that post but it was for the MIUI 12.0.6 so i started to flash it through fastboot mode with a PC and i was done with it but when i pass on the command to reboot my phone it took so much time and then i released that it was stuck there in the LOGO . now im downloading the full ROM of miui 12.0.6(fasboot) to see if i can patch the boot image from there and hope it work.
Faysal_khan_070 said:
YES, im dam sure its GLOBAL and im from Pakistan.
it was the MIUI 12.0.4 BUT Before unlocking it i updated to MIUI 12.0.6
ok so i just followed the MAGISK method and i downloaded a patched file from a post now i don't know where to find that post but it was for the MIUI 12.0.6 so i started to flash it through fastboot mode with a PC and i was done with it but when i pass on the command to reboot my phone it took so much time and then i released that it was stuck there in the LOGO . now im downloading the full ROM of miui 12.0.6(fasboot) to see if i can patch the boot image from there and hope it work.
Click to expand...
Click to collapse
How you going to patch boot image if you cannot get into MIUI and use Magisk to patch boot.img?
You will need another phone to do that though.
Safe way is to do a complete clean data format and flash MIUI Rom.
i have another phone to patch it but the problem is what version should be used for patching magisk 22 or the latest one? how to flash miui rom and can i now go back to miui 12.0.4?
pl1992aw said:
Are you sure your phone is Global? Which country?
What version of MIUI?
How did you flash your boot image?
What partition did you flash the boot image into?
Were you using this one? If yes, flash the boot.img from here into your phone boot partition and see if your phone can boot up.
Boot your phone into Fastboot or TWRP. If you can, there's still hope. Do the step in above Unlock bootloader step 18.
Click to expand...
Click to collapse
i flashed the boot image from this attachment and its still stuck in there.
Faysal_khan_070 said:
i have another phone to patch it but the problem is what version should be used for patching magisk 22 or the latest one? how to flash miui rom and can i now go back to miui 12.0.4?
Click to expand...
Click to collapse
Now my suggestion is to do a Clean complete Rom install. So all your data and files will be gone.
If you agree to clean all your data, follow above Clean Flash custom ROMs. Start from step 8. When you need to get into Fastboot, do it manually.
You don't need to download ArrowOS. Download MIUI 12.0.6.0 Recovery Rom and flash through TWRP.
Don't think of Magisk and MIUI 12.0.4.0 just yet. First get back to be able to see MIUI working.
Do I have to keep a SIM card in the phone throughout the entire unlock process? I would be taking it out of my actual daily driver phone so I'm just curious
spookykidmm said:
Do I have to keep a SIM card in the phone throughout the entire unlock process? I would be taking it out of my actual daily driver phone so I'm just curious
Click to expand...
Click to collapse
You don't have to keep that SIM card after you done Unlock bootloader step 6.
You can remove your SIM card once step 6 was done. But you still need to have the number accessible to receive SMS if Mi-Account ask for verification.
Did you lose anything by unlocking bootloader? Like Widevine or something. Also, any special partition or file one should backup before unlocking (Not counting user data)? In Sony phones user have to backup TA partition or they will lose some features.
Thanks in advance
Rapier- said:
Did you lose anything by unlocking bootloader? Like Widevine or something. Also, any special partition or file one should backup before unlocking (Not counting user data)? In Sony phones user have to backup TA partition or they will lose some features.
Thanks in advance
Click to expand...
Click to collapse
Loss from Unlocking bootloader is written in above tutorial.
Partition backup is generally not needed if you do things correctly. For now, even if you have full backup of qcn, maybe can't even restore.
Read here: https://forum.xda-developers.com/t/4276823/post-85014473
Widevine issue, Read both:
You can have Widevine L1 on custom Roms.
https://forum.xda-developers.com/t/4267263/page-2#post-84919939
You can lost Widevine L1 on official MIUI Roms even without unlocking or root.
https://forum.xda-developers.com/t/4281695/
How can I use the Xiaomi Unlock tool on GNU/Linux? I tried using Wine, but I cannot log in.
wertguygywe said:
How can I use the Xiaomi Unlock tool on GNU/Linux? I tried using Wine, but I cannot log in.
Click to expand...
Click to collapse
Third party unlock tools that claim works on Linux and Mac. Trust it or not is your decision, can't tell you about it since it's 3rd party. Didn't use it before.
[TOOL][WIN/LIN/MAC] MiUnlockTool - Unlock bootloader of xiaomi devices on mac & linux
[TOOL][WIN/LIN/MAC] MiUnlockTool - Unlock bootloader of xiaomi devices on mac & linux Ciao xda users, I'm here to introduce a new tool of mine, MiUnlockTool. MiUnlockTool is an unofficial tool used to unlock bootloader on Xiaomi devices. This...
forum.xda-developers.com
Or find a Windows PC.
Or find USB drive and make a Windows To Go bootable disk. With this, you can boot from USB that contains Windows inside while not removing your Linux and MacOS.
Xiaomi Unlock tool (provided by Xiaomi officially) had only designed for Windows.
I have the latest arrow os on poco x3 pro now. But magisk failed to be installed.
It rebooted fastboot mode repeatedly after flashing magisk_patched_[random_strings].img.
If I flash original boot.img, it can be rebooted to system.
Below are some error in magisk install log I think:
cp: can't preserve ownership of 'busybox': Operation not permitted
cp: can't preserve ownership of 'magisk32': Operation not permitted
cp: can't preserve ownership of 'magisk64': Operation not permitted
cp: can't preserve ownership of 'magiskboot': Operation not permitted
cp: can't preserve ownership of 'magiskinit': Operation not permitted
This does not work due to a bad Java dependency. @
pl1992aw