Related
I need to understand how to update to the new Stock merged partition. Have been reading general advice in various threads that we need to flash new China developer rom. Can someone elaborate regarding how to do this and where to get this rom? Do we need to re-root? Do we need to reflash recovery?
I see that many new MM roms are using this new Stock partition like Matoxxi's newest RR rom. So want to know. Detailed help is highly appreciated... Thanks...
+1
I too would like to see a proper procedure..
This is what I personally did. Was on extended partition. With TWRP as recovery.
1) Flash the cwm r11( or any working cwm) recovery. Needed to flash the repartition zip!! Don't use TWRP. Did this once and had a dead phone. Reboot to recovery. You'll be on CWM.
2) Flash the back to stock partition zip. Choose the one with "el pierro verde" in it.
3) Flash TWRP recovery. Boot to recovery.
4) Flash the 5/12/17 miui zip. This is the ROM which merges the partitions. At this point the partitions are not merged yet!
4.1) Boot the phone up. Reboot to recovery
5) Repeat step 4. Now the partitions are merged.
6) Flash any ROM that you desire.
Of you are on stock partition with TWRP skip steps 1-3.
Good luck.
If you are on MIUI ROM, install 5.12.17 first to merge partitions and then 6.2.4 via Updater app. Xiaomi.eu version is tuned for europe/outside china, Google Apps are included in rom.
https://www.androidfilehost.com/?fid=24369303960690691
https://www.androidfilehost.com/?fid=24415232478676696
Or you can just MiFlash 6.2.4 chinese developer rom factory image from en.miui.com.
Thanks for the details. I did try this out, am on original stock partition... Flashed 5.12.17, two times as per step 4. Rebooted but the partition remains resolute at old stock and does not merge. Am using twrp 2.8.7. Tried this twice, no success... Need advice... Thanks
The only quick way to setup the new partition for now is to fastboot flash the Chinese Dev ROM, as you yourself already stated. You can flash it by fastboot flashing it using Mi PCSuite and choosing the Beta ROM.
On my experience, after the flash I got my bootloader locked ("fastboot oem device-info" resulted in Device unlocked = false), but I can simply unlock it through fastboot without any problem.
From that point, you can easily flash any custom ROM.
Or even MIUI V6, with manual, per partition fastboot flash rather than using MiFlash/Mi PCSuite because of different partition layout; V6 and lower got two boot, modem and system partitions for TDB, while the new has only one.
anshude1 said:
Thanks for the details. I did try this out, am on original stock partition... Flashed 5.12.17, two times as per step 4. Rebooted but the partition remains resolute at old stock and does not merge. Am using twrp 2.8.7. Tried this twice, no success... Need advice... Thanks
Click to expand...
Click to collapse
Can you boot the phone after the first flashing? Than reboot to recovery and try step 4 again.
Have a look to
http://en.miui.com/thread-209941-1-1.html
there you can find a zip (cancro_merge_partition(2).zip) and the guideline how to use. For me it worked fine.
It does the repartitioning through fastboot by executing 1 shell script. Afterwards you might want to update your recovery rom to an English version.
anshude1 said:
Thanks for the details. I did try this out, am on original stock partition... Flashed 5.12.17, two times as per step 4. Rebooted but the partition remains resolute at old stock and does not merge. Am using twrp 2.8.7. Tried this twice, no success... Need advice... Thanks
Click to expand...
Click to collapse
Im using Pallmali method to flash, however 1st i try to repeat flash on step 4, it didnt work, then i download MIUI china dev 6.2.4 and flash, wait for a while and it is updated to MIUI 7 MM with merged partition.
anshude1 said:
Thanks for the details. I did try this out, am on original stock partition... Flashed 5.12.17, two times as per step 4. Rebooted but the partition remains resolute at old stock and does not merge. Am using twrp 2.8.7. Tried this twice, no success... Need advice... Thanks
Click to expand...
Click to collapse
I believe you have to use default Mi Recovery. One time flash of 5.12.17 was enough on my Mi4.
ksloh1 said:
Im using Pallmali method to flash, however 1st i try to repeat flash on step 4, it didnt work, then i download MIUI china dev 6.2.4 and flash, wait for a while and it is updated to MIUI 7 MM with merged partition.
Click to expand...
Click to collapse
It got auto updated? So did you flash stock recovery? Or used twrp
I downloaded 6.2.4 into my phone and then choose the file to update from miui itself, and it will reboot to twrp recovery and install. After fully install and reboot. Only then it will have merged partition and MM miui. And back to stock recovery automatically.
I just fastboot 6.2.4 rom successfully... Now will flash twrp...
And made my first big mistake going in for 6.2.4 beta... It has locked bootloader and a load of Chinese **** you can't make sense of and have to forcefully bear it. Please can anyone help me to unlock the bootloader without begging to the ****ty miui folks?
anshude1 said:
I just fastboot 6.2.4 rom successfully... Now will flash twrp...
And made my first big mistake going in for 6.2.4 beta... It has locked bootloader and a load of Chinese **** you can't make sense of and have to forcefully bear it. Please can anyone help me to unlock the bootloader without begging to the ****ty miui folks?
Click to expand...
Click to collapse
First of all, if you planned to stay on MIUI MM, you don't have any options than requesting an unlock permission to Xiaomi.
If you just want the merged partition and prepared to flash any custom ROM or MIUI V6, enter fastboot then send this command:
Code:
fastboot oem unlock
The reason is that when you unlocks the bootloader through fastboot, it automatically wipes out your phone. IDK why, but possibly inherent to Android's design for security reasons.
rxl.noir said:
First of all, if you planned to stay on MIUI MM, you don't have any options than requesting an unlock permission to Xiaomi.
If you just want the merged partition and prepared to flash any custom ROM or MIUI V6, enter fastboot then send this command:
Code:
fastboot oem unlock
The reason is that when you unlocks the bootloader through fastboot, it automatically wipes out your phone. IDK why, but possibly inherent to Android's design for security reasons.
Click to expand...
Click to collapse
I tried this out, the phone got all wiped but the OEM unlocking button does not work still. So how would I know if the bootloader is unlocked?
anshude1 said:
I tried this out, the phone got all wiped but the OEM unlocking button does not work still. So how would I know if the bootloader is unlocked?
Click to expand...
Click to collapse
OEM Unlocking button? You meant on the Developer Options? That button is currently useless with no function at all. If you want to ascertain if your bootloader is unlocked or not, try sending
Code:
fastboot oem device-info
via fastboot. If the "Device unlocked" comes out as true, then your bootloader is already unlocked.
Ooooor just try to flash any custom recovery/ROM. If it works, then your bootloader is already unlocked.
rxl.noir said:
OEM Unlocking button? You meant on the Developer Options? That button is currently useless with no function at all. If you want to ascertain if your bootloader is unlocked or not, try sending
Code:
fastboot oem device-info
via fastboot. If the "Device unlocked" comes out as true, then your bootloader is already unlocked.
Ooooor just try to flash any custom recovery/ROM. If it works, then your bootloader is already unlocked.
Click to expand...
Click to collapse
Great, big thanks to you... It worked. Device unlocked is True
Funnily it also quoted device tampered is True :laugh:
anshude1 said:
Great, big thanks to you... It worked. Device unlocked is True
Funnily it also quoted device tampered is True :laugh:
Click to expand...
Click to collapse
Yeah, it might be set to true once you had flashed another unsigned image to the eMMC (or when you disconnect the battery, IDK), probably for the warranty checks :q.
knoxwalles said:
Have a look to
http://en.miui.com/thread-209941-1-1.html
there you can find a zip (cancro_merge_partition(2).zip) and the guideline how to use. For me it worked fine.
It does the repartitioning through fastboot by executing 1 shell script. Afterwards you might want to update your recovery rom to an English version.
Click to expand...
Click to collapse
Worked for me
Thank you very much.
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.
I have a Alcatel 1s (5024D) and i cant find any custom recovery for it can someone help me PLEASE
Hello @Xander20190
Have you tried ROM from this website: romprovider.com/alcatel-5024d-firmware-support
Sorry for the link structure, but my account is too young and I cannot paste the full link...
brt80 said:
Hello @Xander20190
Have you tried ROM from this website: romprovider.com/alcatel-5024d-firmware-support
Sorry for the link structure, but my account is too young and I cannot paste the full link...
Click to expand...
Click to collapse
I ment a custom recovery sorry for not putting custom before recovery
Xander20190 said:
I ment a custom recovery sorry for not putting custom before recovery
Click to expand...
Click to collapse
I am sorry, I believe I don't understand you. What does it mean "custom recovery"? You mean TWRP?
You possibly can't install custom recovery on Alcatel 1, as it doesn't allow you to flash anything other than System partition. TWRP is a recovery tool and needs to be flashed on the recovery partition.
sachb_htc said:
You possibly can't install custom recovery on Alcatel 1, as it doesn't allow you to flash anything other than System partition. TWRP is a recovery tool and needs to be flashed on the recovery partition.
Click to expand...
Click to collapse
If you are able to unlock bootloader with these commands, you should be able to flash whatever you want.
Code:
fastboot flashing unlock
fastboot flashing unlock_critical
I was successfull unlocking bootloader of my Alcatel 1S (2020) 5028D-EEA at least but I cant find anything to flash for my device, no stock rom out there anywhere.
RavZ75 said:
If you are able to unlock bootloader with these commands, you should be able to flash whatever you want.
Code:
fastboot flashing unlock
fastboot flashing unlock_critical
I was successfull unlocking bootloader of my Alcatel 1S (2020) 5028D-EEA at least but I cant find anything to flash for my device, no stock rom out there anywhere.
Click to expand...
Click to collapse
Even if you managed to unlock the bootloader, I bet you can't write on boot, & recovery partition.
I have the Alcatel 1 5033D, I can only flash files on the so called "system partition".
Therefore making it useless for anything apart from installing roms.
Lineage is an alternative OS for Alcatel 1 but comes without Google apps (gapps).
Sent from my LM-G710 using Tapatalk
I'll repeat... I cant find anything to flash for my device, no stock rom out there anywhere.
This means if I do flash anything random not suited for my device and it does succeeds with the flash, I could brick my device byebye and no way of unbricking it.
When I unlocked my bootloader with fastboot flashing unlock command, I can't run the same command again without it telling me error already unlocked.
I was however able to run the fastboot flashing unlock_critical command just fine and it again asked if I'm sure to unlock.
What unlock_critical does is as simply as it states, unlocks for flashing of those partitions that the manufacturer have set/locked as "critical" partitions.
I know of LineageOS yes and indeed it doesn't come with GApps...
With no stock rom so I can revert mistakes if being made, I am not myself gonna touch and poke around with that.
You who have an Alcatel 1 5033D are more than welcome to actually give it a try, maybe then you have something of value to add here.
Like if it does work... or even if it doesn't, this is of interest. Instead of "oh I bet"...
Bcuz as far as I have seen it, everyone here have gone with the old command flasboot oem unlock. That command doesn't unlock critical partitions.
RavZ75 said:
I'll repeat... I cant find anything to flash for my device, no stock rom out there anywhere.
This means if I do flash anything random not suited for my device and it does succeeds with the flash, I could brick my device byebye and no way of unbricking it.
When I unlocked my bootloader with fastboot flashing unlock command, I can't run the same command again without it telling me error already unlocked.
I was however able to run the fastboot flashing unlock_critical command just fine and it again asked if I'm sure to unlock.
What unlock_critical does is as simply as it states, unlocks for flashing of those partitions that the manufacturer have set/locked as "critical" partitions.
I know of LineageOS yes and indeed it doesn't come with GApps...
With no stock rom so I can revert mistakes if being made, I am not myself gonna touch and poke around with that.
You who have an Alcatel 1 5033D are more than welcome to actually give it a try, maybe then you have something of value to add here.
Like if it does work... or even if it doesn't, this is of interest. Instead of "oh I bet"...
Bcuz as far as I have seen it, everyone here have gone with the old command flasboot oem unlock. That command doesn't unlock critical partitions.
Click to expand...
Click to collapse
I have flashed "Lineage 16 treble" OS on my Alcatel 1 and it worked, but I've been unsucessfull in flashing the custom recovery, "TWRP" as even after unlocking the bootloader, only partition which can be flashed is the "System partition", so I flashed the original Alcatel 1 firmware back on it for gaaps.
So, this device is pretty much useless even if you have it unlocked, as you're limited to flashing the system partition only.
Sent from my LM-G710 using Tapatalk
well you don't seem to even gonna bother...
guess I'll have to do a flash myself once I find a rom for my device.
What I am specifically asking you is if you have unlocked critical partitions. Am I being unclear about that?
Could be that it is only your device model, maybe we'll see if other devices of Alcatel have better "flashability" then.
If I get hold of a stock rom to my device 5028D-EEA, I could try flash stock recovery or boot images myself only to try out and see if it does flash.
I didn't know there is an TWRP recovery for 5033D and it shouldn't even exist if it isn't possible to flash it.
This is the one, correct? No mention about "fastboot flashing unlock_critical" here either.
https://unofficialtwrp.com/twrp-3-3-0-root-alcatel-5033d/
RavZ75 said:
well you don't seem to even gonna bother...
guess I'll have to do a flash myself once I find a rom for my device.
What I am specifically asking you is if you have unlocked critical partitions. Am I being unclear about that?
Could be that it is only your device model, maybe we'll see if other devices of Alcatel have better "flashability" then.
If I get hold of a stock rom to my device 5028D-EEA, I could try flash stock recovery or boot images myself only to try out and see if it does flash.
I didn't know there is an TWRP recovery for 5033D and it shouldn't even exist if it isn't possible to flash it.
This is the one, correct? No mention about "fastboot flashing unlock_critical" here either.
https://unofficialtwrp.com/twrp-3-3-0-root-alcatel-5033d/
Click to expand...
Click to collapse
It's unbelievable, that you can't seem to get the point. No matter, what command you use, the only accessible partition for alcatel 1 will be the"System Partition".
I have tried all the commands, including unlock_critical, and still I'm unable to flash anything apart from system partition.
If you don't believe me, here is another user with the same issue:
https://r.tapatalk.com/shareLink/to...1&share_fid=3793&share_type=t&link_source=app
Sent from my LM-G710 using Tapatalk
What exactly is so unbelieveble about it? I spew out a whole lot about unlocking critical partitions and in vain for that matter, what I get back is LineageOS 16 treble and unlocked bootloader you say. It's not being very clear about your point as people type in command fastboot oem unlock and say yeah I unlocked bootloader..
"I have tried all the commands, including unlock_critical, and still I'm unable to flash anything apart from system partition." <- This is very good. This is exactly what I wished was clear about from the beginning and now it is.
Now finally done with this, I am gonna admit that I see your point and that It's not gonna work. So I'll withdraw that argument that it all should be unlocked with those commands as this is not the case for your device.
Can anyone give me a pac file for the 1se. my phone is stuck on a bootloop and I need to flash it
You can root it but it's a long journey: https://forum.hovatek.com/thread-32678.html
Also, you can port TWRP but you need to modify it for the touchpad to work: https://forum.hovatek.com/thread-32743.html
KikoPlays44 said:
Can anyone give me a pac file for the 1se. my phone is stuck on a bootloop and I need to flash it
Click to expand...
Click to collapse
A package installer file? What is pac? you have sys as root and a only partition that's treble supported and Vulcan supported.you need a clean sys image.xz
Realme XT Wiki
For convenience : https://www.androidfilehost.com/?w=files&flid=304989
First things first.
DISCLAIMER : Use this guide at your own risk. I won't be responsible for you bricking your device due to following this guide. It's also necessary to back up your data before you attempt anything.
Realme XT is not really a developer friendly device as they claim to be for the following reasons.
- Bootloader restricts flashing critical partitions and certain fastboot options are disabled like
Code:
fastboot boot recovery.img
- The flash tool is only available to service centres.
- Kernel sources are not actively updated by realme.
- Nil response to developer's queries.
Code:
[B][U]Table of contents :[/U][/B]
- Unlocking the bootloader
- Unbrick guide
- TWRP guide
- Upgrade guide
- Downgrade guide
- Project Treble for Realme XT
- Links
For unlocking the bootloader, follow the official instrutions from here :
https://c.realme.com/in/post-details/1184740422732218368
As of 28/03/20, you can unlock the bootloader in Realme UI. The official guide for XT is still not updated by realme, but the bootloader unlock app tool that was released for realme3pro works for XT.
UNBRICK GUIDE FOR REALME XT : (FASTBOOT)
Most bricks that happen with devices are softbricks. This means you can boot into stock recovery using key combination or you can access fastboot.
Hardbricks are where your device basically does nothing no matter what you do.
If you are on Color OS 6 or realme UI on locked bootloader :
- Switch off your device
- Press volume up + power button hold it until it finishes starting up.
- You will see the recovery menu now
- Press online update and connect it to wifi and follow instructions
If you are on color os 6 on unlocked bootloader :
Prerequisite:
1. You need to have unlocked bootloader
2. Platform tools setup and added to system environmental variables under windows
OR
Just install this : https://forum.xda-developers.com/showthread.php?t=2317790
Since custom ROMS don't deal with critical partitions, there is very less chance that the critical partitions are messed up. Majority of the times you would be fine with just flashing the boot image, system image, vendor image, vbmeta.
Instructions for color os 6 (Android pie firmware) :
Download the stock pie A16 fastboot image from the links section and extract it :
Just flash by executing the following commands :-
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash vbmeta vbmeta.img
fastboot flash dtbo dtbo.img
fastboot flash oppo_sec oppo_sec.img
fastboot flash modem modem.img
fastboot flash splash splash.img
fastboot flash DRIVER DRIVER.img
fastboot reboot
If you are on Realme UI on unlocked bootloader :
Prerequisite :
Download the stock Realme UI fastboot image from the links section and extract it :
Note : The zip file has other partitions too. Hopefully, you shouldn't need them.
Just flash the boot,system,vendor and vbmeta by executing the following commands
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash vbmeta vbmeta.img
fastboot flash dtbo dtbo.img
fastboot flash oppo_sec oppo_sec.img
fastboot flash modem modem.img
fastboot flash splash splash.img
fastboot flash DRIVER DRIVER.img
fastboot reboot
Guide to Custom Recovery:
Prerequisite:
1. You need to have unlocked bootloader
2. Platform tools setup and added to system environmental variables under windows
OR
Just install this : https://forum.xda-developers.com/showthread.php?t=2317790
TWRP Recovery
Orangefox Recovery
Instructions to install TWRP recovery:
Run this command
Code:
fastboot flash recovery TWRP.img
You can install orangefox recovery by flashing it via TWRP recovery or by extracting the recovery.img from orangefox recovery.zip file.
Upgrade guide :
You can always find the latest update from here : https://www.realme.com/in/support/software-update
Upgrading from android pie to android 10 carries the risk of bricking your device. Be it locked or unlocked. Thus proceed with caution and ONLY use stock recovery to update from android pie to android 10.
If you are on locked bootloader,
Step 1 :Simply download the update of your choice from the Links section and try to open it in stock file manager.
Note : If it doesn't show the update option in stock file manager, just rename the file from *.zip to *.ozip and try again
Step 2 : Press reboot immediately after the flashing is done
Step 3 (Very important) : Pray that everything works. Bricks can happen to anyone.
If you are on unlocked bootloader,
Step 1:In case you already have TWRP working on pie, simply flash the official stock android pie A16 through twrp and let it boot.
Step 2:Now, let it fully boot into the system
Step 3: Go to stock file manager and follow similar instructions as is for locked bootloader that's written above.
Downgrade guide :
Prerequisite:
In case you are in realme UI (Android 10) and want to roll back to android pie for any reason, you need to backup your data and flash stock pie A16 via TWRP
Step 0 : Back up your data and download stock A16 firmware from the links section below
Step 1 : Go to TWRP and flash stock pie
Step 2 : Flash stock pie again
Step 3 : Format data and reboot
Project Treble for Realme XT :-
You could refer here for what works and what doesn't
https://github.com/phhusson/treble_experimentations/wiki/realme-XT
Prerequisite :
1. You need to have unlocked bootloader
2. Platform tools setup and added to system environmental variables under windows
OR
Just install this : https://forum.xda-developers.com/showthread.php?t=2317790
3. You need to be on realme UI (Android 10)
Typically, you could install GSI without even using TWRP.
Step 1: Download any A/B arm64 GSI of your choice
Step 2: Erase userdata using the command
Code:
fastboot -w
Step 3: Flash system.img using fastboot command
Code:
fastboot erase system && flash system system.img
Step 4: Flash RUI vbmeta with flags
Code:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Optional : Flashing TWRP helps with installing magisk and device specific treble fixes and is highly recommended.
USEFUL LINKS :
Recovery (Both stock and TWRP), Fastboot images and Official Updates
https://www.androidfilehost.com/?w=files&flid=304989
Realme XT Android 10 C01 (Realme UI)
https://download.c.realme.com/osupdate/RMX1921EX_11_OTA_1010_all_yuEH87qmmZhw.ozip
Realme XT Android pie A16
https://download.c.realme.com/osupdate/RMX1921EX_11_OTA_0160_all_CcmkxwAnmByA.ozip
Realme XT stock vbmeta Android 10 C01 (Realme UI)
Help!!
I am on coloros 6 (a16) and i have unlocked bootloader (twrp not installed) so how can i update it to rui. Via stock file manager method or just install twrp in a16 and flash rui(c_02) ozip in twrp. So, Which will be a better and safe way to update and avoid bricking the phone according to you.
mehtakush007 said:
I am on coloros 6 (a16) and i have unlocked bootloader (twrp not installed) so how can i update it to rui. Via stock file manager method or just install twrp in a16 and flash rui(c_02) ozip in twrp. So, Which will be a better and safe way to update and avoid bricking the phone according to you.
Click to expand...
Click to collapse
Use the stock recovery for update and wait for official OTA.
Reset Device
My device is locked and now i forgot my password and when i am trying to wipe data from realme ui recovery its asking for password again is there anyway to bypass that security and reset my device please help i cant go to sevice centers right now due to lockdown in my country.
Leamusex said:
My device is locked and now i forgot my password and when i am trying to wipe data from realme ui recovery its asking for password again is there anyway to bypass that security and reset my device please help i cant go to sevice centers right now due to lockdown in my country.
Click to expand...
Click to collapse
So u must wait for that. . Me waiting for tutorial to downgrade realme ui to a16 or. How to unlock bootloader with realmeui firmware.
Leamusex said:
My device is locked and now i forgot my password and when i am trying to wipe data from realme ui recovery its asking for password again is there anyway to bypass that security and reset my device please help i cant go to sevice centers right now due to lockdown in my country.
Click to expand...
Click to collapse
Unfortunately no. you must input password or your data is a lost cause.
krizhiel said:
So u must wait for that. . Me waiting for tutorial to downgrade realme ui to a16 or. How to unlock bootloader with realmeui firmware.
Click to expand...
Click to collapse
The tutorial is already there in the wiki. Although make sure you backup your data first.
PS C:\adb> fastboot flash recovery C:\adb\TWRP_RMX1921_pjgowtham_290320.img
sending 'recovery' (65536 KB)...
it did not flash it just stayed there forever
I have bricked my device. I have a bootloop. Combinations of keys don't work, recovery doesn't show up. Bootloader is locked. Can anyone help?
dmmas21 said:
I have bricked my device. I have a bootloop. Combinations of keys don't work, recovery doesn't show up. Bootloader is locked. Can anyone help?
Click to expand...
Click to collapse
Same problem i have..Any help please..
dmmas21 said:
I have bricked my device. I have a bootloop. Combinations of keys don't work, recovery doesn't show up. Bootloader is locked. Can anyone help?
Click to expand...
Click to collapse
You locked manually?
akashavel said:
You locked manually?
Click to expand...
Click to collapse
yes, me too. And now i have hardbrick and dont know how to fix this without service centre
bro Did You fixed it ?
I am on RMX1921_11_C.04 is there anyway to install custom recovery?
I bought a realme xt and upgraded it to realme ui version c04 but I get some random crash reports I don't know what is it they just randomly pop up 1-2 times per day along with a screenshot I am uploading those please can someone check.
My device bootloop'ed after following your downgrade tutorial. Tried boot unbrick it like your tutorial to no avail
Anyone who is now used to with this device and have done all these steps from Unlocking bootloader to flashing recoveries to installing custom & Stock Roms, can you please tell me what are the senarios in which this device can brick and only restored by Realme service center? I mean what possible error we can make that gives error of boot/recovery destroyed and only needs to visit realme service center?
I am very new to realme, before getting started with unlocking bootloader, i want to be sure about my steps, actually all i need is to use titanium backup for old data transfer of apps, my phone records etc, and most importantly using viper4android. This is all i am going to do after unlocking bootloader.
Raju Sah said:
Same problem i have..Any help please..
Click to expand...
Click to collapse
A reply this late isnt probably useful. But for others who refer this thread, once locked, it can be saved only by flashtool if you cant access stock recovery.
Fastboot commands not working
Hey there.
I am using realme xt with realme UI and i tried to unlock the bootloader. The bootloader is unlocked successfully but the fastboot commands arent working now on the device. This is whats happened while relocking the bootloader and same error for flashing recovery.
D:\Root\platform-tools>adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
f40db298 device
D:\Root\platform-tools>adb reboot bootloader
D:\Root\platform-tools>fastboot devices
f40db298 fastboot
D:\Root\platform-tools>fastboot flashing lock
FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
D:\Root\platform-tools>fastboot flashing lock
< waiting for any device >
^C
D:\Root\platform-tools>fastboot devices
D:\Root\platform-tools>
this also happened while flashing recovery also. And I am kind of stuck i cant relock the bootloader and cant install custom recovery to root the device.
Kindly, guide me to solve this problem. Thanks in Advance.
Hi, anybody can help me? I want to sell my phone so i wanted to flash stock rom and lock the bootloader. But i dont find any post or something like that to do so... Do you know how can i flash the stock rom and relock the bootloader like we can do with xiaomi phones?
Situation:
I tried rooting my phone. I extracted the boot.img with payloaddumper from the latest android 11 Zenfone 8 image from the Asus website (the same version I have on my phone). I patched that image file with Magisk. Flashed that file to my phone with fastboot which succeeded. But after rebooting this is the message I get:
"Your device is corrupted and cannot be trusted and will not boot" and than a link to g.co/ABH
There is no option to "press power to continue" as seen on other screenshots of this problem on YouTube. So I am stuck. I cannot enter recovery. It tries to boot a few times but than stays at the "start" screen while booting.
What I tried to fix this:
Internet states that I have to disable DM check with: adb reboot "dm-verity enforcing". But ADB does not see my device. Fastboot does! So I tried flashing back the original/unpatched boot.img but the result stays the same.
Question:
What can I do to fix this? Also flash Vendor_boot.img? At this moment I rather not do too much but wait for advice/tips in this forum.
And a few "stupid" questions:
- When trying to root the method described here in this forum..... does the bootloader have to be unlocked? My is not.
- IF the bootloader has to be open.... I know I have to use an Asus tool.... but is there a way to do it with ADB/Fastboot?
- When it is necessary to flash my whole device.... is there a way to save my data? (for example flash trwp first and back up data to a thumbdrive)
Any help much appreciated!
>>does the bootloader have to be unlocked
Yes
>>but is there a way to do it with ADB/Fastboot?
No. Only to relock. Or at least I haven't seen such method.
>>When it is necessary to flash my whole device
What do you mean?
>>is there a way to save my data?
If you have root and mean apps data - Swift backup. For me it is failed to restore only few apps (banking + Signal messenger) all other apps are ok.
dron39 said:
>>does the bootloader have to be unlocked
Yes
Click to expand...
Click to collapse
Ok.... bummer..... the device was not unlocked....... So NOT being unlocked did not prevent the flashing I guess. And a locked bootloader is preventing disabling the DM check?
dron39 said:
>>When it is necessary to flash my whole device
What do you mean?
Click to expand...
Click to collapse
If undoing my flash/error (= no unlocked bootloader) is not possible. I have to do a complete reflash I guess. So that would wipe all data. I was wondering if I could flash only parts of the system so some partitions would be spared (so I could save some data..... or install TWRP and maybe save some data)
dron39 said:
>>is there a way to save my data?
If you have root and mean apps data - Swift backup. For me it is failed to restore only few apps (banking + Signal messenger) all other apps are ok.
Click to expand...
Click to collapse
Root was the goal. But that did not happen yet because of the locked bootloader as I understand it now. So no root = no backup/saving data?
If I download the last OTA update my phone recieved, extract boot.img from it and flash that to my phone with fastboot will that restore my phone to a bootable state? If not,what will?