[Q] Bootloader Locking/Unlocking, Stock ROM Backup with minimum changes - Xiaomi Redmi 4X Questions & Answers

Hello people. Recently i got my first qualcomm device redmi-4x (v8.2.12.0) global (previously i used/worked-for mtk devices), and from past few days i have been reading/learning about this qualcomm device.
I have checked almost all redmi-4x forums (miui, xda, 4pda etc) and still have some questions in my mind.
Q1:
I want to backup my redmi-4x before unlocking/rooting/FlashingTWRP. I know in mtk devices, even if the device is unrooted/untouched we can easily backup firmware/complete-emmc (each and every partition) by readback methods using SP-FlashTool/Miracle-Box etc...
i read somewhere, we can do same thing, i.e readback qualcomm device's emmc in edl-mode but unfortunately, xiaomi has disabled fastboot edl mode in new devices and the only way left to open edl mode is test point method which requires disassembly. though i can but i don't want to disassemble it (warranty will be void). Another solution i saw was Deep Flash Cable, which isn't working either, personally tested... Now, having no other option, i decided to unlock it to make stock rom backup using TWRP. Actually i wanted to make backup with minimum changes to original firmware, so if anyone here knows any other solution to make backup without unlocking bootloader, (or unlocked_bootloader + no_other_changes, i.e without TWRP) please share... Thanks!
Q2:
From what i have learned so far, i think MiUI bootloader unlock tool doesn't work with non-miui firmwares, right? so the question is, if we manually relock our redmi 4x using fasboot when there is some non-miui rom installed in the device. what can be the possible solution to unlock it again? (except reflashing miui by test point method and then unlocking bootloader). Thanks!

EnerJon said:
i wanted to make backup with minimum changes to original firmware, so if anyone here knows any other solution to make backup without unlocking bootloader, (or unlocked_bootloader + no_other_changes, i.e without TWRP) please share... Thanks!
Click to expand...
Click to collapse
Hi, I do it this way:
- unlocked bootloader
- copy http://www.mediafire.com/file/pj0qh1ccj4h2a2a/p0.zip to FAT32 flash drive
- fastboot boot twrp.img (TWRP is not flashed, boots from RAM, not eMMC, so no_other_changes)
- attach the flash drive to R4X on OTG adapter
- in TWRP "install" p0.zip
- entire eMMC will be compressed and saved on the flash drive
My new R4X 32GB was compressed down to 2GB within around half an hour. Later I mounted the disk image on a PC and erased OS/data partitions: system, cache, userdata, cust, recovery, boot, and now the entire 32GB with bootloader, support and firmware is 80MB compressed.
Have you tried QPST backup in EDL mode?

k23m said:
- unlocked bootloader
- copy http://www.mediafire.com/file/pj0qh1ccj4h2a2a/p0.zip to FAT32 flash drive
- fastboot boot twrp.img (TWRP is not flashed, boots from RAM, not eMMC, so no_other_changes)
- attach the flash drive to R4X on OTG adapter
- in TWRP "install" p0.zip
- entire eMMC will be compressed and saved on the flash drive
My new R4X 32GB was compressed down to 2GB within around half an hour. Later I mounted the disk image on a PC and erased OS/data partitions: system, cache, userdata, cust, recovery, boot, and now the entire 32GB with bootloader, support and firmware is 80MB compressed.
Click to expand...
Click to collapse
Thanks for The Guide, it Will Surely be Helpful for New R4X Users :good: Just Wondering Why No One Made Such a Guide For R4X Earlier... Or Did i Missed it Somewhere?
k23m said:
Have you tried QPST backup in EDL mode?
Click to expand...
Click to collapse
No, But i Used another Tool Which i Think Uses Same Technique as QPST in EDL Mode. i Unlocked My R4X and Then Booted into EDL Mode, Used This Tool (With "prog_emmc_firehose_8937_ddr.mbn" From R4X Fastboot Firmware) To Take Complete EMMC Backup, it Also Converted The Backup into Fastboot ROM...

EnerJon said:
Thanks for The Guide, it Will Surely be Helpful for New R4X Users :good: Just Wondering Why No One Made Such a Guide For R4X Earlier... Or Did i Missed it Somewhere?
Click to expand...
Click to collapse
I made the guide and script for Nexus 7'13 but it works well on R4X too. There is no known method of QPST backup on the Nexus but Xiaomi always had more options thanks to freely available "firehose" files. Thank you for the emmcdl link, it is a very simple and convenient tool.
We could use emmcdl for unlocking. I found some pre-patched "persist" partitions here http://blog.regenerationmm.com/2017/03/emmc-dl-အသုံးျပဳျပီး-mi-account-bypass-ျပဳလုပ္/
:highfive:

k23m said:
I made the guide and script for Nexus 7'13 but it works well on R4X too. There is no known method of QPST backup on the Nexus but Xiaomi always had more options thanks to freely available "firehose" files. Thank you for the emmcdl link, it is a very simple and convenient tool.
We could use emmcdl for unlocking. I found some pre-patched "persist" partitions here http://blog.regenerationmm.com/2017/03/emmc-dl-အသုံးျပဳျပီး-mi-account-bypass-ျပဳလုပ္/
:highfive:
Click to expand...
Click to collapse
Hello. Do you have more information on this? I have a Redmi 4x that I really want to unlock the bootloader, but the official method doesn't work for me.
I found this site showing a method for the redmi 4a that uses the emmcdl tool:
Rolex Instant UBL (Unofficial Unlock Bootloader for Redmi 4A) Tested! - OmBob Opreker
Complete Tutorial how to bypass your Redmi 4A (rolex) lock bootloader, the unofficial way. tested And Work for all rolex version
ombob.my.id
Is this what you mentioned?

unluckyuser said:
Hello. Do you have more information on this? I have a Redmi 4x that I really want to unlock the bootloader, but the official method doesn't work for me.
I found this site showing a method for the redmi 4a that uses the emmcdl tool:
Rolex Instant UBL (Unofficial Unlock Bootloader for Redmi 4A) Tested! - OmBob Opreker
Complete Tutorial how to bypass your Redmi 4A (rolex) lock bootloader, the unofficial way. tested And Work for all rolex version
ombob.my.id
Is this what you mentioned?
Click to expand...
Click to collapse
Hi, I have files from the defunct link, but never tested them as my R4X is unlocked officially.
The R4A is indeed using the unlock method I speculated about.

k23m said:
Hi, I have files from the defunct link, but never tested them as my R4X is unlocked officially.
The R4A is indeed using the unlock method I speculated about.
Click to expand...
Click to collapse
I would like to have the files and experiment, thank you.
I already messed up my phone and I'm trying to flash the stock rom via edl first.

Related

Mi 8 soft brick

Hi guys
Sorry for my bad English
My device was running Android 10
miui 11
After I accidentally used an application to raise the screen frequency to 84Hz
The devics did a reboot and then stopped on the fastboot logo
I tried to enter recovery mode but was back to fastboot mode
I tried to flash twrp via adb and fastboot but the method did not work and the device returned to fastboot mode
Finally I downloaded the ROM file global Version Android 9
miui 11 and when i flashed the system via "xiaomi flash tool " the operation was successful until it reached the end of the process it showed me an error and the flash failed
I restarted the process and noticed that the flashing process gives me the error when the download arrives at "flashing boot"
I searched a lot for the version of Android 10 miui 11 but I did not find
What is the problem!
Can anyone explain what the problem is?
Thank you very much
Edit : solved With the help of my friend and brother @tsongming thanks bro
You likely damaged the phone, myself and others have posted numerous warning about flashing mods to increase the refresh rate.
I would recommend trying the Flashall.bat method.
Follow my instructions here : https://forum.xda-developers.com/showpost.php?p=80825243&postcount=2
tsongming said:
You likely damaged the phone, myself and others have posted numerous warning about flashing mods to increase the refresh rate.
I would recommend trying the Flashall.bat method.
Follow my instructions here : https://forum.xda-developers.com/showpost.php?p=80825243&postcount=2
Click to expand...
Click to collapse
When i flash device with edl mod in xiaomi mi tool i got these error
What i can due
ahmadbasher said:
When i flash device with edl mod in xiaomi mi tool i got these error
What i can due
Click to expand...
Click to collapse
See this thread : https://c.mi.com/thread-2121755-1-0.html
Also, I read about some people getting past these recent issues by using a USB hub extender. These decrease the amount of power to the port which may be causing a conflict. Try other ports and only use a usb 2 port. Further, I would recommend temporarily disabling firewall and antivirus if all else fails. Worst case use another computer.
If this helps come back and let us know what finally resolved it.
tsongming said:
See this thread : https://c.mi.com/thread-2121755-1-0.html
Also, I read about some people getting past these recent issues by using a USB hub extender. These decrease the amount of power to the port which may be causing a conflict. Try other ports and only use a usb 2 port. Further, I would recommend temporarily disabling firewall and antivirus if all else fails. Worst case use another computer.
If this helps come back and let us know what finally resolved it.
Click to expand...
Click to collapse
I solved and my device life agin
I flash these rom http://bigota.d.miui.com/V9.5.11.0....EACNFA_20180703.0000.00_8.1_cn_64c55c8438.tgz
With mi flash tool older version (2016)
In fastboot mode
But now i need back to global rom and after i flash latest global rom in fastboot the device bricking again
And stay in fastboot
What is the problem
ahmadbasher said:
I solved and my device life agin
I flash these rom http://bigota.d.miui.com/V9.5.11.0....EACNFA_20180703.0000.00_8.1_cn_64c55c8438.tgz
With mi flash tool older version (2016)
In fastboot mode
But now i need back to global rom and after i flash latest global rom in fastboot the device bricking again
And stay in fastboot
What is the problem
Click to expand...
Click to collapse
You still have encryption on your device, use the tool all in one and install TWRP ( You may need to use a different/maybe older computer, I think possibly windows 10 is part of the issue. ( Because I have had this exact issue that you are having)
Install the tool, and update ADB but not the tool itself, there will be a popup, asking to update. ignore it or the update will be flagged a sbeinga virus ( Actually a Windows issue) However, yes the program is unsigned.
Use all in One tool to remove encryption from device and flash TWRP
Boot to recovery, immediately flash root, Flash Su if you must.
Reboot to recovery, then flash a recovery rom. the boot to system , may take up to 10 minutes.
use ports from the back of the PC and you may need to use a usb hub.
tsongming said:
You still have encryption on your device, use the tool all in one and install TWRP ( You may need to use a different/maybe older computer, I think possibly windows 10 is part of the issue. ( Because I have had this exact issue that you are having)
Install the tool, and update ADB but not the tool itself, there will be a popup, asking to update. ignore it or the update will be flagged a sbeinga virus ( Actually a Windows issue) However, yes the program is unsigned.
Use all in One tool to remove encryption from device and flash TWRP
Boot to recovery, immediately flash root, Flash Su if you must.
Reboot to recovery, then flash a recovery rom. the boot to system , may take up to 10 minutes.
use ports from the back of the PC and you may need to use a usb hub.
Click to expand...
Click to collapse
thanks for replay bro i will tri it
tsongming said:
You still have encryption on your device, use the tool all in one and install TWRP ( You may need to use a different/maybe older computer, I think possibly windows 10 is part of the issue. ( Because I have had this exact issue that you are having)
Install the tool, and update ADB but not the tool itself, there will be a popup, asking to update. ignore it or the update will be flagged a sbeinga virus ( Actually a Windows issue) However, yes the program is unsigned.
Use all in One tool to remove encryption from device and flash TWRP
Boot to recovery, immediately flash root, Flash Su if you must.
Reboot to recovery, then flash a recovery rom. the boot to system , may take up to 10 minutes.
use ports from the back of the PC and you may need to use a usb hub.
Click to expand...
Click to collapse
I tri it and no change
Again reboot to fastboot
ahmadbasher said:
I tri it and no change
Again reboot to fastboot
Click to expand...
Click to collapse
While its possible that you have a hardware issue. Unless the phone has been exposed to moisture, or exposed to a great deal of force I doubt that you have a hardware problem. Again, I too have had a similar issue, it's just took a while to finally get it working, in my case my computer was part of the problem, since you have fastboot the number one goal at the moment should be with getting TWRP recovery installed, and then root.
Did you happen to make any TWRP backups?
Hopefully so, specifically if you have a TWRP backup that includes the persist image files, you need to try flashing those to the persist partition. If you can successfully restore the persist image then try the flashall.bat method again.
Another option is to use QPST, but try the above first.
Edit
Finally, After re-reading you initial post. I had forgotten that you attempted to improve the refresh rate of the display. If all you can get is fastboot after following all of the steps that I have mentioned than I am certain that you have a burned chip. Ignore the people who claim that you can't fry the chip they have no idea what they are talking about. The chip can absolutely be fried. It's still worth trying a few more times, you could have just simply corrupted partition images. When you flash the stock rom, or even when using the flashall.bat method not every partition is over written.
@ahmadbasher
When you flashed the file to increase the refresh rate you likely overwrote a partition called DTBO, See if you can flash a Mi8 DTBO image to the DTBO partition. If you have the full recovery backup, you can extract the file from there. i need to research exactly how that file works and I will try to help you will getting the image if you don't have it in a backup.
tsongming said:
While its possible that you have a hardware issue. Unless the phone has been exposed to moisture, or exposed to a great deal of force I doubt that you have a hardware problem. Again, I too have had a similar issue, it's just took a while to finally get it working, in my case my computer was part of the problem, since you have fastboot the number one goal at the moment should be with getting TWRP recovery installed, and then root.
Did you happen to make any TWRP backups?
Hopefully so, specifically if you have a TWRP backup that includes the persist image files, you need to try flashing those to the persist partition. If you can successfully restore the persist image then try the flashall.bat method again.
Another option is to use QPST, but try the above first.
Edit
Finally, After re-reading you initial post. I had forgotten that you attempted to improve the refresh rate of the display. If all you can get is fastboot after following all of the steps that I have mentioned than I am certain that you have a burned chip. Ignore the people who claim that you can't fry the chip they have no idea what they are talking about. The chip can absolutely be fried. It's still worth trying a few more times, you could have just simply corrupted partition images. When you flash the stock rom, or even when using the flashall.bat method not every partition is over written.
@ahmadbasher
When you flashed the file to increase the refresh rate you likely overwrote a partition called DTBO, See if you can flash a Mi8 DTBO image to the DTBO partition. If you have the full recovery backup, you can extract the file from there. i need to research exactly how that file works and I will try to help you will getting the image if you don't have it in a backup.
Click to expand...
Click to collapse
All thanks to you my friend, I do not know how I can give all thanks and gratitude to you for helping me ? But my friend unfortunately I do not have a backup of it Will wait for you
Thanks again
Is it possible that this is part of the problem..!
I can't check it
@tsongming
ahmadbasher said:
All thanks to you my friend, I do not know how I can give all thanks and gratitude to you for helping me But my friend unfortunately I do not have a backup of it Will wait for you
Thanks again
Click to expand...
Click to collapse
No problem, after reading some various post on GitHub, CNX, and source android.com, I found out that the Mi8 DTBO is in the boot. Image.
So you should be able to flash a boot image, root, and then recovery and hopefully boot to TWRP.
If that doesn't work then send me a pm and I will share my personal dtbo with you privately. But again you shouldn't need mine since dtbo is nothing more than the device tree and the boot image should suffice, because it has the exact same file.
ADB command : fastboot flash boot c:\boot.img
ahmadbasher said:
Is it possible that this is part of the problem..!
I can't check it
@tsongming
Click to expand...
Click to collapse
No that is just encryption, if the issue was related to encryption the flashall.bat method would have resolved it.
If you had a persist issue, you would see specific messages about not being able to mount the persist partition.
tsongming said:
No problem, after reading some various post on GitHub, CNX, and source android.com, I found out that the Mi8 DTBO is in the boot. Image.
So you should be able to flash a boot image, root, and then recovery and hopefully boot to TWRP.
If that doesn't work then send me a pm and I will share my personal dtbo with you privately. But again you shouldn't need mine since dtbo is nothing more than the device tree and the boot image should suffice, because it has the exact same file.
ADB command : fastboot flash boot c:\boot.img
Click to expand...
Click to collapse
Thank you I will now try to do this
Yesterday I flashed the pixle rom on the device and I took off the device without problems but every period of time the device was doing a reboot, I do not know if it is the problem of the ROM or there is something wrong with the device
I tell you so that you know only that
Now I will flash the latest version of miui 11 android 9 global version, and flash the boot.img and then Root and finally Recovery True ?
ahmadbasher said:
Thank you I will now try to do this
Yesterday I flashed the pixle rom on the device and I took off the device without problems but every period of time the device was doing a reboot, I do not know if it is the problem of the ROM or there is something wrong with the device
I tell you so that you know only that
Now I will flash the latest version of miui 11 android 9 global version, and flash the boot.img and then Root and finally Recovery True ?
Click to expand...
Click to collapse
Hey sorry for the delay in getting back to you, I sent you the link for the file via PM.
Also, I would strongly suggest using the stock miui initially. Just until you know it's resolved. Also while Miui is installed make a full TWRP backup and save it to your desktop. This way you always have a full backup to resolve any serious issues.
Then once you know everything is working as it should then go back to what you prefer..
For the record this issue was solved. Anyone reading this, make sure that you have a full working TWRP backup of your working device, it will save you a lot of headaches. The solution for the refresh rate is issue is restoring stock DTBO, and then flashing Miui Stock.

[GUIDE] Back to stock ROM howto / Downgrade howto

There maybe a number of reasons to go back to the stock ROM. We do not discuss them here
But what to do if you flashed something, wanting to go back to stock, and did not brick your Realme X2 yet? Here is super quick howto guide. There are other possible ways and sequences to perform the task, but the one listed below is tested.
The same procedure applys for a case when you want to downgrade you phone (when its bootloader unlocked). Say, current custom ROMs are based on ColorOS 6.1/Android 9 vendor contents but you have realmeUI/Android 10 already. In order to try one of those custom ROMs you should downgrade to the latest Android 9 stock firmware first.
The essential part of the customized phone is custom recovery. Currently Realme OZIP file does not contain stock recovery inside. It is being generated as explained below, in the post #2, see EDIT3. It means you need to find somewere PROPER stock recovery corresponding to your ROM to put it back. See Realme X2 stock recovery links below, post #2, EDIT4.
Which stock recovery to use? The one for your model and which version is not newer than the ROM version you are flashing. For example, you need A.17 stock ROM for CN model (RMX1991). Then any recovery of A.12, A.14, A.16, A.17 for RMX1991 will work for you.
Download and unzip the stock recovery partition image from the next post, this will be a file like rmx1991-sde20-stock_recovery.img.
Download stock ROM ozip file (for example, from here). Put it to a SD card with a filesystem which supports files more than 2GB (ext4 works fine. Stock recovery, but not ColorOS, supports it). Put the SD card into the phone.
Start (reboot) phone into fastboot mode
From a computer perform fastboot flash recovery rmx1991-sde20-stock_recovery.img
From the fastboot mode by means of volume buttons select 'Recovery mode' and push Power button
From the stock recovery select language needed (there are three only), then 'Install from storage device', then 'From SD card', tap the OZIP file with your ROM
When the update process is done, phone reboots. Most likely, it will not be able to boot normally because you need to wipe out data. Either help the phone with keeping Vol Down button pressed during reboot, or it will boot recovery by itself. Now wipe data (confirm by entering random 4-digit code), select 'Format data'. Phone will reboot
Here it is. Enjoy (or sell your Realme X2 with its shiny stock experience...
If you want to lock bootloader after all above mentioned steps (you have to make them all unless you wanna get a brick ), boot fastboot mode, perform fastboot flashing lock. This will wipe your data again. Then optionally lock 'OEM Unlock' option in 'Developer Options'. Even further, you can install In-DepthTest.apk and sign out from In-Depth Test program.
2022-12-25 EDIT: For downgrade from Android 11 to 10 read this post
I have found out that in fact stock recovery does not exist as a prebuilt file It is being created by the script /system/bin/install-recovery.sh on a basis of stock boot partition and a patch file /system/recovery-from-boot.p
It means in theory you can recreate stock recovery having only Realme ozip file.
EDIT1 The command to do it in Linux shell is
Code:
bspatch boot.img selfmade_stock_recovery.img recovery-from-boot.p
Cool! Tested.
EDIT2. For the current moment when unlocked bootloader breaks fingerprint sensor: as soon as the bootloader is locked again, fingerprint starts functioning as it should.
EDIT3 Becomes clear that each ROM release has its own stock recovery which is generated automatically on the basis of boot.img and recovery-from-boot.p . Not only boot.img is being changed each release, but recovery-from-boot.p is changing as well. If the wrong stock recovery is installed, you might not be able to decrypt data and connect to WiFi from within recovery. Seemingly it may bring you serious problems if locking back bootloader (thus bricking the device). Good thing (as I understood, but not checked yet) is that after flashing stock ROM with a help of a stock recovery next reboot should replace your stock recovery with an up-to-date version of it. So to be on a safe side make sure that you rebooted to system and that your recovery reflashed by the system before you lock bootloader.
EDIT4 In order to combine everything in one place:
Stock recoveries for RMX1991 (China version): here
Stock recoveries for RMX1992 (India version): here
Stock recoveries for RMX1993 (Euro version): here
EDIT5 In later ROM releases patch and script files are relocated into vendor partition, they are /bin/oppo-install-recovery.sh and /recovery-from-boot.p there.
EDIT6 Please note that the method above is working with officially downloaded ROMs from realme support site (read here why).
So this method works if you brick your phone trying to install a global rom to china variant..
Hi,
does only works with SDcard insert.
Because the internal storage is decrypted.
And it does not work on X2.
But why?
Installation failed?
This method will bring back my FP working again right?
Can you please confirm this method https://boycracked.com/2019/10/26/official-realme-x2-rmx1991-stock-rom/
SkyeJace said:
This method will bring back my FP working again right?
Click to expand...
Click to collapse
You have to lock bootloader for this. See the very last part of the howto, post #1
AldRezaine said:
Can you please confirm this method https://boycracked.com/2019/10/26/official-realme-x2-rmx1991-stock-rom/
Click to expand...
Click to collapse
The site provides generalized instructions for everything
As for Realme X2, there are two methods claimed, one is for ozip file, another for ofp file; last one is not yet publicly available somewhere (the link is replaced by the Coming soon promise).
If you find there something certain regarding ozip procedure for Realme X2, give me the link, please. I couldn't
why I back to stock rom, apps i uninstalled it is don't auto reinstall?
hello guys, how can i get the 1993ex stock recovery? i screwd up big time !
hammerheading said:
hello guys, how can i get the 1993ex stock recovery? i screwd up big time !
Click to expand...
Click to collapse
Read the post #2 in this thread, it contains ample info needed for this. If you are requesting ready-to-flash stock recovery file, you should tell the version of the ROM you are going to flash and powerful word please to it
BaDuc said:
why I back to stock rom, apps i uninstalled it is don't auto reinstall?
Click to expand...
Click to collapse
I am not 100% sure I understand you right. If you are about some stock apps missing after wiping the userdata partition, this is true: some of the apps were preinstalled onto data space (some of them are Weather app, One-Tap Lockscreen). I could find only some of them in a form of apk files.
yakovpol said:
Read the post #2 in this thread, it contains ample info needed for this. If you are requesting ready-to-flash stock recovery file, you should tell the version of the ROM you are going to flash and powerful word please to it
Click to expand...
Click to collapse
Thanks a lot for the attention. I tryed to recreate the recovery but with no success because i dont know the proper method, it's a bit over my android skills as i can only root unlock bl and do some minor stuff and GSI is a new thing for me. AS for the version it is the a17 of the 1993ex(eu).
yakovpol said:
I am not 100% sure I understand you right. If you are about some stock apps missing after wiping the userdata partition, this is true: some of the apps were preinstalled onto data space (some of them are Weather app, One-Tap Lockscreen). I could find only some of them in a form of apk files.
Click to expand...
Click to collapse
yes, right my mind, including my Breeno is faulty, and now I can't click to setting Breeno in the settings, do you have apk of app, can you send me?
hammerheading said:
Thanks a lot for the attention. I tryed to recreate the recovery but with no success because i dont know the proper method, it's a bit over my android skills as i can only root unlock bl and do some minor stuff and GSI is a new thing for me. AS for the version it is the a17 of the 1993ex(eu).
Click to expand...
Click to collapse
For the moment I have one for the EU A.16 version only, look here. Eventually A.17 will be added there too.
BaDuc said:
yes, right my mind, including my Breeno is faulty, and now I can't click to setting Breeno in the settings, do you have apk of app, can you send me?
Click to expand...
Click to collapse
Those I have are uploaded to here.
yakovpol said:
Those I have are uploaded to here.
Click to expand...
Click to collapse
thanks you very much
yakovpol said:
For the moment I have one for the EU A.16 version only, look here. Eventually A.17 will be added there too.
Click to expand...
Click to collapse
Thank you so much, that did the trick!! i was able to flash the a17 and the phone is working fine now . But i'm not trully satisfied, i can't find a away to flash a GSI rom successfully, but that's another topic ... Thank you again and keep up the good work !
can u plsss provide stock recovery for realme x2 rmx1992, i bricked my phone trying to install stock os since 2 days, cant find a way..if some has the recovery pls provide it. im able to boot to twrp, bootloader is unloced and with the other recoveries im not able to intsall the stock rom.pls help.
Can send me 1992 stcok recovery file ozip please.

[RECOVERY] Unofficial TWRP 3.3.1-0 recovery for Xiaomi Redmi (olive)

There is now an official version available (xda post). Go use that.
Thanks for your work
---------- Post added at 10:43 PM ---------- Previous post was at 10:37 PM ----------
seprode said:
I compiled TWRP for my own Redmi 8 (olive) and thought I would share. Based on the devicetree for the Redmi 8a (olivelite) by milankragujevic.
I have the global variant with a Tianma display. I can't test if it works on any other variant, use with precaution.
I used it successfully to flash the xiaomi.eu rom and magisk.
You can find the device tree on my GitHub: here
And the image in the release section: here
Installation:
Unlock Bootloader if not already done (Official Tool)
Boot in to fastboot (Powerbutton + volume down)
Run fastboot flash recovery recovery.img (for Windows use Minimal ADB and Fastboot)
Boot in to recovery (Powerbutton + volume up)
If something breaks you can use MiFlash and the stock fastboot rom to go back to reset your phone (phone will also be locked again) or use fastboot to flash the stock recovery (can also be found in the stock fastboot rom).
You can download the fastboot rom here.
Click to expand...
Click to collapse
How can I know if my device Tianma display or not?
yamabokra1 said:
How can I know if my device Tianma display or not?
Click to expand...
Click to collapse
Go in to the phone app and dial *#*#6484#*#*. Under 1 and then LCD you can then find the manufacturer.
I don't know if it actually matters. I read here that it affects devices when using the Redmi 8a recovery. Since I forked the code and have a Tianma display I can't really look in to the problem.
Have you got MTP working while at TWRP? I can't seem to get it right, Windows don't see my phone (adb and fastboot are working). While using adb-sideload I've got error that my mi-globe.zip rom cannot be installed through that method
------ EDIT -----
So, I flashed fastboot stock ROM and recovery. Then flashed this recovery. Booted into stock ROM, copied my custom ROM, rebooted into recovery and still couldn't install - after half of the installation process TWRP shouted that it couldn't mount /system partition. How did you get it to work? And thanks for work!
pulka103 said:
Have you got MTP working while at TWRP? I can't seem to get it right, Windows don't see my phone (adb and fastboot are working). While using adb-sideload I've got error that my mi-globe.zip rom cannot be installed through that method
------ EDIT -----
So, I flashed fastboot stock ROM and recovery. Then flashed this recovery. Booted into stock ROM, copied my custom ROM, rebooted into recovery and still couldn't install - after half of the installation process TWRP shouted that it couldn't mount /system partition. How did you get it to work? And thanks for work!
Click to expand...
Click to collapse
Can you check your LCD is it Tianma display?
"Go in to the phone app and dial *#*#6484#*#*. Under 1 and then LCD you can then find the manufacturer."
pulka103 said:
Have you got MTP working while at TWRP?
Click to expand...
Click to collapse
I recompiled TWRP with MTP enabled and it seems to show up as a device but i can't access data from the device.
I installed the image via a sd-card, but usb-otg or adb push should also work.
pulka103 said:
TWRP shouted that it couldn't mount /system partition.
Click to expand...
Click to collapse
Okay I changed the default mounting point of the system partition. Try again with the new image.
yamabokra1 said:
Can you check your LCD is it Tianma display?
"Go in to the phone app and dial *#*#6484#*#*. Under 1 and then LCD you can then find the manufacturer."
Click to expand...
Click to collapse
I do have a Tianma display. Problem isn't with controls but with the TWRP itself in my case.
Just tried new image, same problem "Checking /system. /system is not mounted! Trying to mount /system RW. /system cannot be mounted. [...] Installation will be aborted."
I am using Mi-Globe right now, gonna try with "clean" Xiaomi.eu.
And still can't access storage through Windows Explorer (but device itself is seen, tested with adb).
So Xiaomi.eu installed kinda. No errors and stuff but won't boot up. After one try it just goes back into TWRP. Using V11.0.3.0 for HM8 (as described by Xiaomi.eu)
luckily, mine has TIANMA display, I'll try while my rm8 is unlocked, thanks bro
@seprode, Reading your post and seen your work, I decided and today I ordered a Redmi 8 (olive) for my self , too.
I am very thankful that there are people like you, pioneers, who open the path, for all of us to follow.
Thank you again for what you are doing for us.
I hope, soon enough, some developer will pay attention to our new phone and , maybe , we will be also able to see new Android (Q ?) roms for it.
I am active involving so far in Samsung NOTE 2(exynos) and Note 4 (snapdragon) and also Xiaomi Redmi 5 plus community
I will do my best and see, if any of these groups will be able , in the future, to do something for our little brother here.
But the path you have open, is the very important first step to it.
KUDOS
:good::good:
@pulka103 You want to try again? I made some changes and got MTP working.
seprode said:
I compiled TWRP for my own Redmi 8 (olive) and thought I would share. Based on the devicetree for the Redmi 8a (olivelite) by milankragujevic.
I have the global variant with a Tianma display. I can't test if it works on any other variant, use with precaution.
I used it successfully to flash the xiaomi.eu rom and magisk.
You can find the device tree on my GitHub: here
And the image in the release section: here
Installation:
Unlock Bootloader if not already done (Official Tool)
Boot in to fastboot (Powerbutton + volume down)
Run fastboot flash recovery recovery.img (for Windows use Minimal ADB and Fastboot)
Boot in to recovery (Powerbutton + volume up)
.
Click to expand...
Click to collapse
Thank for your work !
What about vbmeta as mentioned at milankragujevic ?
And do we need something against dm_verity ?
Edit:
I did the described "simple" way and it works !!!
No need to flash anything else !!!
Great job, Thanks again :good:
seprode said:
I compiled TWRP for my own Redmi 8 (olive) and thought I would share. Based on the devicetree for the Redmi 8a (olivelite) by milankragujevic.
I have the global variant with a Tianma display. I can't test if it works on any other variant, use with precaution.
I used it successfully to flash the xiaomi.eu rom and magisk.
You can find the device tree on my GitHub: here
And the image in the release section: here
Installation:
Unlock Bootloader if not already done (Official Tool)
Boot in to fastboot (Powerbutton + volume down)
Run fastboot flash recovery recovery.img (for Windows use Minimal ADB and Fastboot)
Boot in to recovery (Powerbutton + volume up)
If something breaks you can use MiFlash and the stock fastboot rom to go back to reset your phone (phone will also be locked again) or use fastboot to flash the stock recovery (can also be found in the stock fastboot rom).
You can download the fastboot rom here.
Click to expand...
Click to collapse
I have a problem and maybe some of you can help me. I flashed last recovery.img. After flashing phone reboot itself and boot to system. Next, perform reboot to recovery and it boot to mi-recovery, not twrp. Then I cant boot to system. I have to flash again and then it boot to system.
===EDIT====
Ok, I managed this. After "fastboot flash recovery recovery.img" you have to type "fastboot reboot"
Great Great work I hope you continue updating. Thank you ?
good afternoon, this twrp this worked on redmi 8 olive, if it worked I will for now, obg and thank you already.: D
Ok, so ive tried to install latest xiaomi.eu rom for the redmi olive after flashing twrp, following all the steps from here and other posts, and all I get was reboot everytime. how do i go back to stock? miflash is not working and i dont find any .img to flash back
seprode said:
@pulka103 You want to try again? I made some changes and got MTP working.
Click to expand...
Click to collapse
hey man i fixed up novatek touchscreens on a repack version of your twrp i will include here
Download also i did a PR on your github with the needed changes so your next version will have this fix
Thank for twrp i hope it works on my device but what about custom rom wee need to custom rom ..miui contains lots of ads so that we need some good custom room..and brother replay me as soon as possible.
[email protected] said:
Thank for twrp i hope it works on my device but what about custom rom wee need to custom rom ..miui contains lots of ads so that we need some good custom room..and brother replay me as soon as possible.
Click to expand...
Click to collapse
you should try miui eu
unlock Bootloader
how can i unlock Bootloader for Redmi 8 with out Official Tool

Question [Solved] Help with fixing my phone back to Normal after playing with Roms & Twrp

Got the bootloader unlocked..should've read more & implemented over a proper guide.
long story short:
stared with magisk apk..when phone was fine.. then got into bootloop;
quickly downloaded & flashed the global (lime) MIUI V12.0.5.0.QJQMIXM;
installed twrp; should've done this before.
wasn't able to copy anything into internal storage.
Used Twrp to wipe phone.. & flashed the stock_global_miui_(lime)12.0.5 boot.img in fastboot
because twrp was saying "unable to decrypt fbe device" on internal storage
formatted using twrp.
booted properly but setup says device is locked because associated with existing mi account can't open wifi but was able to activate device upon entering password on mobile data setup completes but device restarts frequently & still unable to access wifi
I think it has something to do with "unable to decrypt fbe device"..
should I try flashing custom rom boot img?
please don't ban me..tell if I did something wrong, I'll correct that..
..
Edit:
MiFlash-tool Worked
Flashing other compaitable custom Rom also worked
..
Had twrp wipe the whole phone and the format the partions
& then flashed in fastboot & everything was normal.
..
FBE device encryption is basically storage encryption that prevents dirty flashing miui rom via fastboot.
this can be avoided by implementing proper procedure of magisk & use of lazypatcher.
Thank you so much.. @Cursader & @zoel.fahmi for pointing me in the right direction.. godbless
[solved]
Currently I'm running Miui just like a new device.
I will make another guide thread on rooting systemlessly & flashing other custom rooms... if I succeed I will link it here..
Try to reboot bootloader
then flash twrp
wipe everything and format the data partition
reboot to twrp again
then flash custom rom
If you're flashing miui again, your phone bootloader will be lock again and you need something like lazy2flasher if you wanna keep miui with twrp and magisk etc.
zoel.fahmi said:
Try to reboot bootloader
then flash twrp
wipe everything and format the data partition
reboot to twrp again
then flash custom rom
If you're flashing miui again, your phone bootloader will be lock again and you need something like lazy2flasher if you wanna keep miui with twrp and magisk etc.
Click to expand...
Click to collapse
first of all thank you for taking out the time to read & respond..
I found an article with lazy 2 flasher earlier, I'll look into it..
is there any where I should look to find a suited custom rom for my phone..
xhykari said:
first of all thank you for taking out the time to read & respond..
I found an article with lazy 2 flasher earlier, I'll look into it..
is there any where I should look to find a suited custom rom for my phone..
Click to expand...
Click to collapse
you can use custom rom from Poco M3 since it's used the same SoC (662)
here : https://forum.xda-developers.com/f/poco-m3-roms-kernels-recoveries-other-develop.11969/
check the thread name Poco M3 / Redmi 9T or unified or codename like citrus and lime
whats the difference between Lime, Citrus, & Juice..
Mine is Lime
Juice is Lime & Citrus I think..
So will Juice work on a device which previously ran Lime?
..
basically can I install PixelPlusUi_Juice
or should I first try the lazy2flasher.. & @zoel.fahmi
where do I get lazy2flasher
If anything goes for me (RedmiNote9Pro) i just use miflash to flash original miui and start all over from there, might not be the quickest method but is easy and reliable
Cursader said:
If anything goes for me (RedmiNote9Pro) i just use miflash to flash original miui and start all over from there, might not be the quickest method but is easy and reliable
Click to expand...
Click to collapse
THERE IS AN MI FLASH TOOL too.. :O
whydoinotknowofthis.. What the heck..
can it bypass dm verity as well? like does it apply flash without lazypatcher?
do we need to provide it rom or can it fetch itself?
would you be please share some links for me?
..
xhykari said:
THERE IS AN MI FLASH TOOL too.. :O
whydoinotknowofthis.. What the heck..
can it bypass dm verity as well? like does it apply flash without lazypatcher?
do we need to provide it rom or can it fetch itself?
would you be please share some links for me?
Click to expand...
Click to collapse
If the bootloader unlocked and you can go into fastboot you can flash stock rom and It's just like it came from the store! Here you have link for your convinience: https://c.mi.com/oc/miuidownload/detail?guide=2
MiFlash-tool Worked..
(its the best tool for bringing mi devices from rom mess back to scratch new)
Flashing other Rom also worked..(pixelui)
juice = lime + citrus (works for both)
Thank you so much.. @Cursader & @zoel.fahmi for pointing me in the right direction..

Question SM-X205 32/3 How to install GSI?

Hello everyone. Can You please explain how to install GSI to SM-X205? I'm new to fastboot methods. I can't find proper TWRP for this particular model. I have achieved to unlock bootloader which took two steps (In old Android phone it was just easy with switch in developer options). I have installed TWRP from SM-X200 but it's not working. Restored everything by flashing Official Firmware. The main reason why I'm going to this is shortage of storage. I want to format external SD Card as Internal which is not allowed in new Andoirds. Thank you before hands and respect for ones who contribute their knowledge for community.
If TWRP is not available for your device, you can try using this to enable fastbootd. It won't have any TWRP specific features though.
As far as installing a GSI, you simply flash the system.img to /system. It's that simple. Make sure you wipe data.
SukhrobR said:
Hello everyone. Can You please explain how to install GSI to SM-X205? I'm new to fastboot methods. I can't find proper TWRP for this particular model. I have achieved to unlock bootloader which took two steps (In old Android phone it was just easy with switch in developer options). I have installed TWRP from SM-X200 but it's not working. Restored everything by flashing Official Firmware. The main reason why I'm going to this is shortage of storage. I want to format external SD Card as Internal which is not allowed in new Andoirds. Thank you before hands and respect for ones who contribute their knowledge for community.
Click to expand...
Click to collapse
SM-X205 installs the same as SM-X200 - I've followed all the instructions for any TWRP, root, GSI, etc and it all works as others X200's. I've not lost anything on the X205.
Piggybacking on this thread to drop some much needed general resources. I installed LineageOS on my s5e last year but struggled to find resources w/ GSI.
I appreciate all the hard work that the devs do, and typically documentation is not their strong suit, so in the future, maybe those of us who benefit from their work can create clearer documentation to spread around the burden a bit:
FAQ that covers topics like what is Treble, what is GSI, what is the naming conventions for GSI files: https://github.com/phhusson/treble_experimentations/wiki/Frequently-Asked-Questions-(FAQ)
Where as example of a GSI I can download : https://github.com/phhusson/treble_experimentations/releases/tag/v416
What should I know going in: Android 13 versions of GSI still have a few compatibility issues as per the first post in this thread. Android 12 is functioning 100% correctly.
Where can I see a more complete list of the GSI options available to me: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
w00tnezz said:
SM-X205 installs the same as SM-X200 - I've followed all the instructions for any TWRP, root, GSI, etc and it all works as others X200's. I've not lost anything on the X205.
Click to expand...
Click to collapse
I have followed all the instructions. But I'm stuck at stage where rebooting to fastboot from TWRP. Touchscreen stops to respond and I can't enable ADB.
SukhrobR said:
I have followed all the instructions. But I'm stuck at stage where rebooting to fastboot from TWRP. Touchscreen stops to respond and I can't enable ADB.
Click to expand...
Click to collapse
You don't need to enable ADB. When the screen says "Entering fastboot mode" then you are connected. You can check this by entering "fastboot devices" from your PC.
lewmur said:
You don't need to enable ADB. When the screen says "Entering fastboot mode" then you are connected. You can check this by entering "fastboot devices" from your PC.
Click to expand...
Click to collapse
Device list is empty after entering fastboot mode in twrp
SukhrobR said:
Device list is empty after entering fastboot mode in twrp
Click to expand...
Click to collapse
Do you have the latest version of the Samsung USB drivers? Earlier versions don't have the fastboot driver.
lewmur said:
Do you have the latest version of the Samsung USB drivers? Earlier versions don't have the fastboot driver.
Click to expand...
Click to collapse
Yes I do. I think it dependable on firmware version.
w00tnezz said:
SM-X205 installs the same as SM-X200 - I've followed all the instructions for any TWRP, root, GSI, etc and it all works as others X200's. I've not lost anything on the X205.
Click to expand...
Click to collapse
Does this allow me to use this (https://forum.xda-developers.com/t/...0-for-2021-galaxy-tab-a8-10-5-sm-x200.4488691) for my SM-X205?

Categories

Resources