Related
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
THIS RECOVERY IS FOR STOCK ROM AND WILL NOT WORK ON CUSTOM ROMS
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this recovery
* before using it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Bugs:
- The "fastboot boot twrp.img" doesn't work, if you use the hardware buttons to open the blue fastboot bootloader mode. Only use adb, twrp or the android system to reboot into blue fastboot bootloader mode or flash the twrp.img, boot the device, reboot into bootloader and flash the original boot.img back, before booting into twrp.
You can also "fastboot reboot bootloader" in the blue fastboot mode.
This is a bootloader bug, maybe it gets fixed with the stock Q bootloader.
- Decrypt is not working for now (Is probably because the current stock firmware is still on May security patch - will be fixed with June/July patch)
- Touch not working when installed
- Please report any other bugs
Install guide:
Installing is currently not recommended because touch is not working on the installed version!
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode from adb
3. Unlock your bootloader
4. Run "fastboot boot twrp.img" in command line
6. Enjoy it
Optional (if you want to install it):
1. Boot from it (see the guide above)
2. Go to advanced -> Install recovery ramdisk
3. Choose the twrp img
4. Wait
5. You can now boot it with vol- and power button
If it keeps booting into TWRP and not System try
Code:
adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc
Download
Changelogs:
3.3.1-0 03.08.2019
- Initial Release
Source code:
https://github.com/Schritti/device-sony-mermaid
https://github.com/Schritti/device-sony-ganges
If you like my work, press thanks
I would appreciate your Donation
Thanks to:
@MartinX3 for helping me developing the TWRP
@Oshmoun for providing device trees for Ganges and Mermaid
@naoki2010 for Testing
XDA:DevDB Information
TWRP, ROM for the Sony Xperia X10 Plus
Contributors
Schritti, MartinX3, Oshmoun, Marijn
ROM OS Version: 9.x Pie
ROM Firmware Required: Stock Pie Firmware
Version Information
Status: Beta
Current Beta Version: 3.3.1-0
Beta Release Date: 2019-08-03
Created 2019-08-03
Last Updated 2019-08-05
Reserved
Reserved
Woohooo!
First!
My computer is down at the moment but I have a question does this supports the North American unlocked variant i3223? I looked at your sources and I don't see the i3223 variant.
sickkside13 said:
My computer is down at the moment but I have a question does this supports the North American unlocked variant i3223? I looked at your sources and I don't see the i3223 variant.
Click to expand...
Click to collapse
All variants are supported
I am having the worst time trying to get this device (i3223 variant) into recovery or into fastboot mode so I can boot into recovery via adb. The device is pattern locked and wasnt adb enabled before hand. I can get to where the light flashes blue after holding vol up while inserting usb but screen is blank then goes to a charging screen. I want to erase and test on this device. Its been a couple days and drivers are correct emma doesnt work and the sony companion wont recognize the device only that its locked. any help?
clothtalklp said:
I am having the worst time trying to get this device (i3223 variant) into recovery or into fastboot mode so I can boot into recovery via adb. The device is pattern locked and wasnt adb enabled before hand. I can get to where the light flashes blue after holding vol up while inserting usb but screen is blank then goes to a charging screen. I want to erase and test on this device. Its been a couple days and drivers are correct emma doesnt work and the sony companion wont recognize the device only that its locked. any help?
Click to expand...
Click to collapse
It's normal, that the screen is black in fastboot mode. If the LED is Blue then it's alright.
When you're in fastboot mode (Blue LED) check the windows device manager, you might install the driver again for fastboot. If it shows a device called "Android" you have to right click it and install the correct driver.
I just got the phone unlocked so i will boot into TWRP and install it and debug the touch. I have the feeling that it might be just missing file.
I just tested the installed version of TWRP and touch works just fine. The TWRP on itself is little slow. Decryption is broken and we see just bunch of junk folders in internal storage as expected.
But decryption shoudlnt be an issue after i bake TWRP into my AOSP images.
Rebooting into OS is totally broken and even cleaning misc doesnt help. Boots to TWRP all the time. Again most likely just an issue that it was not installed in boot.img right away but had to be added.
So about unlocking - my device/version isn't supported to unlock. Any hints?
mad-murdock said:
So about unlocking - my device/version isn't supported to unlock. Any hints?
Click to expand...
Click to collapse
You cant unlock bootloader. Thats just it. Did you buy the device from carrier ? If so they have usually not unlockable devices.
Haxk20 said:
You cant unlock bootloader. Thats just it. Did you buy the device from carrier ? If so they have usually not unlockable devices.
Click to expand...
Click to collapse
bought it used super cheap, wanted to play with it and maybe help a bit with development. but määä - seems like not.
do you think the device might become unlockable with a future firmware update? i am more a oneplus user and have little experience with sony.
mad-murdock said:
bought it used super cheap, wanted to play with it and maybe help a bit with development. but määä - seems like not.
do you think the device might become unlockable with a future firmware update? i am more a oneplus user and have little experience with sony.
Click to expand...
Click to collapse
Sadly I do not think so. We would love another dev helping on SonyOpenSourceDevices or even custom ROMs but sadly if the phone is not unlockable there is nothing you can do sadly. I heard stories of people having carrier phones sim locked and after unlocking that they were able to unlock BT so you could possibly try that if the phone is locked to 1 carrier. If not then there i s really nothing you can do. I'm sorry.
Hi,
first off a big thank you!
I would like to root my xperia 10 plus I4213. I tried to do my homework before posting here, but since I am not knowledgeable on the subject, can someone confirm that these are the right steps:
1. Enable in phone third party apps, unlock developer settings, enable adb.
2. Boot in fastboot mode. That can be done in terminal, not by using buttons as it used to.
3. unlock bootloader . My understanding if that now, that can be achieved either via terminal or via windows newsflasher program.
4. Flash recovery from this thread
4. Boot into system and install magisk manager .
5. Install via recovery Magisk zip.
6, Boot into system and use magisk manager to enable root and set settings.
Should I install latest magisk 20.1 or an earlier version?
Thank you.
Problem with TWRP
Why is the device memory data encrypted even though the device doesn 't have a password?
reintal said:
Why is the device memory data encrypted even though the device doesn 't have a password?
Click to expand...
Click to collapse
That is how your internal storage looks like when encryption is just Ffkjgh up.
This recovery dont have any updates and well its just broken for now. sadly.
Haxk20 said:
That is how your internal storage looks like when encryption is just Ffkjgh up.
This recovery dont have any updates and well its just broken for now. sadly.
Click to expand...
Click to collapse
It sounds sadly 'cause in that case it is not possible for me to install magisk on the standard firmware and I cannot use gpay anyway.
reintal said:
It sounds sadly 'cause in that case it is not possible for me to install magisk on the standard firmware and I cannot use gpay anyway.
Click to expand...
Click to collapse
We are mainly focus on making AOSP 10 stable now and TWRP is not on top of the list to fix now. And TWRP doesn't support Android 10 yet so we can't even begin.
New From A-TEAM: lehmancurtis147
ALCATEL IDOL 5 : 6060CACCESS FASTBOOT
UNLOCK BOOTLOADER
INSTALL TWRP
Special thanks to the mVirus Team for the reboot tool.
Ok, here we go!!!
Start fastboot:
1.*Unpack and launch the boot mode tool.
2.*Power off your 6060C.
3.*While holding vol- plug in device to PC.
4.*While continuing to hold vol- press power until the device starts and release power (not vol-).
5.*Once you see fastboot at the bottom of the device you can release vol-.
Unlock Bootloader:
Now that you are in fastboot mode, we need to unlock the bootloader.
Code:
fastboot oem unlock
Install Custom Recovery:
I forgot to mention I also built a working TWRP.img for this device.
1.*Unzip the recovery.zip.
2.*To install it.
Code:
fastboot flash recovery recovery.img
3.*then...
Code:
fastboot oem reboot-recovery
4.*Welcome to team win recovery!
DOWNLOADS:
This is the boot-mode tool:
https://androidforums.com/attachments/mtk-bootmode-tool-zip.153347/
twrp link:
https://drive.google.com/file/d/1teI23ASm2IbIy_r4xV0jlzz_TzS3cvTc/view?usp=sharing
NOTE:
Unless you remove verity (and a handful of other annonyances) you will loose twrp. Luckily, I've already built a replacement system.img to solve this. Once its working right I'll share it.
I have the system image working, but it's huge. Probably why system and vendor were split in android 8. It's a 4.6 gigabyte image so as soon as I decide the best way to host it I will post it.
In the mean time, the way to keep updated is our telegram group.
A-Team General Discussion
Anything Alcatel, AIO ToolKit, Android, CricketRom
https://t.me/Android_General_Chat
Recoveries
!!!ANNOUNCEMENT!!!
New Recovery Options Available
I now have managed to build a fully functional Pitch Black Recovery Image and and Orange Fox Recovery Image (the later is built from mostly 9.0 branch) and will be making them available soon if I see that anyone is actually interested.
The recovery image files are compiled from source and not a Frankenstein type. So I can address any recovery issues (within the scope of reason).
Thanks for the thread!! I don't have this device but to my amazement, this utility booted my Alcatel 3t 8 tablet into fastboot mode and I was bootloader unlocked in seconds! I can't thank you enough. This tool should be shared around. It may just be the key to unlocking the bootloader on a plethora of 2018+ MTK devices.
mickeybeats said:
Thanks for the thread!! I don't have this device but to my amazement, this utility booted my Alcatel 3t 8 tablet into fastboot mode and I was bootloader unlocked in seconds! I can't thank you enough. This tool should be shared around. It may just be the key to unlocking the bootloader on a plethora of 2018+ MTK devices.
Click to expand...
Click to collapse
Hi mickeybeats, I happen to have the Alcatel 3t 8 as well! I've been looking for a copy of the stock ROM/firmware everywhere and I'm unable to find it. Is it possible that you have a copy/know where I could download it? My tablet starting throwing up the feared "System UI has stopped" error and it seems reflashing stock ROM is the only way to fix it
I can confirm that the bootloader thing works for the 6058D model (MTK 6753)
For stock ROMs on Alcatel mtk devices, you need Sugar-mtk from Alcatel. It goes through the reflash process and as a bonus you can grab the firmware file from inside the flash tools program folders. The files don't use human readable formatting for the names but they end in either .bin or .mbn. A once over with a hexeditor should be enough to get a general idea of what they are. All the ones I've delt with had the boot.img label with a b at the beginning of the name and r for recovery, but gets a bit scattered from there.
stevegsames said:
I can confirm that the bootloader thing works for the 6058D model (MTK 6753)
Click to expand...
Click to collapse
Post your boot.img if you don't already have a custom recovery and I will build one for yours.
lehmancurtis said:
Post your boot.img if you don't already have a custom recovery and I will build one for yours.
Click to expand...
Click to collapse
I did make one, thank you though. If anyone's interested, here it is:
Idol 5 6058D TWRP
So, I recently revisited this phone and saw that there was a new exploit to access the bootloader. I tried it and it worked. After some time of trial and error, I was able to dump the stock recovery. With this, I started to port TWRP to it. This...
forum.xda-developers.com
stevegsames said:
I did make one, thank you though. If anyone's interested, here it is:
Idol 5 6058D TWRP
So, I recently revisited this phone and saw that there was a new exploit to access the bootloader. I tried it and it worked. After some time of trial and error, I was able to dump the stock recovery. With this, I started to port TWRP to it. This...
forum.xda-developers.com
Click to expand...
Click to collapse
Good to hear.
Hi all!
Is there anything similar to 'boot-mode too'l for Linux machines?
What would be a proper command-foo for this task?
The usual method with adb/fastboot obviously doesn't work with
Alcatel IDOL 5 (6058D/MT6753).
To install TWRP on Alcatel Idol 5, you first need to unlock the bootloader.The process is a bit more involved for this device than it is on most others.
Click to expand...
Click to collapse
Thanks!
elocnix said:
Hi all!
Is there anything similar to 'boot-mode too'l for Linux machines?
What would be a proper command-foo for this task?
The usual method with adb/fastboot obviously doesn't work with
Alcatel IDOL 5 (6058D/MT6753).
Thanks!
Click to expand...
Click to collapse
I don't know if it will work with wine. But you should be able to run it from a VM.
Don't be a idiot like me and accidently flash the recovery image on the Alcatel 3T 8. it will permanently brick the device and sugar-mtk will not restore .
Hi,
My phone is actually dying and I don't know how to recover it this time.
I had a perfectly working setup with latest weekly update of Xiaomi eu MIUI , TWRP and magisk, and know even fastboot is not responding.
I usually don't like when people say that, but I think a malware did it, as my apps started not responding in a few minutes, and the reboot finished the job.
Now it won't boot anymore, when it's plug the notification led is red, and fastboot is detected but commands are stuck.
Also, TWRP is neither accessible from "power + vol up" since last miui eu update, nor from fastboot since the "accident"
If someone have any advice on how to unlock fastboot, flash back the rom or any other way to recover my phone, please help
Also, if you want to know the rest of the story, it's here...
I was using my phone as usual, trying to setup a bridge openvpn connection. (like everyone :laugh: )
The issue is that the only app claiming to do that isn't free, and I want to be sure I can make it work before spending any money.
So I tried to patch it and different apks (I know it's bad...), and while transferring an apk from my laptop to my phone, I noticed the transfer was kinda slow for a few seconds (nothing worrying, but unusual)
Then some of my apps didn't want to launch and, back to the app drawer, most of my apps had their package names, with no icons...
It was at this moment Jackson I knew I screwed up...
I then tried rebooting, and the phone stayed a few minutes on the MIUI screen, then shut off.
After a reboot, I noticed the red led, the absence of boot animation, and the bootloop.
Obviously, if I had a fastboot access, it would be easy to boot on TWRP and then flash back my rom properly but I can't...
EDIT: to make this clearer (I know the post above is a little bit messy), I have the following issues:
- No access to TWRP (for flashing)
- Fastboot is accessible but broken enough so flash/boot to twrp is not possible
- I just though of EDL mode, but "fastboot oem edl" doesn't seems to work
- I prefer to avoid opening my phone (to access to the EDL test points)
EDIT2: You can't flash anything in EDL mode without specific autorisations from xiaomi, so this mode becomes way more useless than on my previous Mi A1. I managed to miraculously flash some things by using miflash in fastboot mode. Maybe working on a windows os instead of gnu/linux helped somehow...
Thelm76 said:
Hi,
My phone is actually dying and I don't know how to recover it this time.
I had a perfectly working setup with latest weekly update of Xiaomi eu MIUI , TWRP and magisk, and know even fastboot is not responding.
I usually don't like when people say that, but I think a malware did it, as my apps started not responding in a few minutes, and the reboot finished the job.
Now it won't boot anymore, when it's plug the notification led is red, and fastboot is detected but commands are stuck.
Also, TWRP is neither accessible from "power + vol up" since last miui eu update, nor from fastboot since the "accident"
If someone have any advice on how to unlock fastboot, flash back the rom or any other way to recover my phone, please help
Also, if you want to know the rest of the story, it's here...
I was using my phone as usual, trying to setup a bridge openvpn connection. (like everyone :laugh: )
The issue is that the only app claiming to do that isn't free, and I want to be sure I can make it work before spending any money.
So I tried to patch it and different apks (I know it's bad...), and while transferring an apk from my laptop to my phone, I noticed the transfer was kinda slow for a few seconds (nothing worrying, but unusual)
Then some of my apps didn't want to launch and, back to the app drawer, most of my apps had their package names, with no icons...
It was at this moment Jackson I knew I screwed up...
I then tried rebooting, and the phone stayed a few minutes on the MIUI screen, then shut off.
After a reboot, I noticed the red led, the absence of boot animation, and the bootloop.
Obviously, if I had a fastboot access, it would be easy to boot on TWRP and then flash back my rom properly but I can't...
Click to expand...
Click to collapse
Hi
I had a similar situation
I comfigured an app and during configuration the phone start framing
I rebooted and stucked at miui screen
I tried to reboot in recovery ,nothing
I downloaded latest miui for europe 12.0.3 and mi flash
For me fastboot worked to flash latest firmware from xiaomi
And now is working and my bootloader is locked
Thelm76 said:
Hi,
My phone is actually dying and I don't know how to recover it this time.
[/hide]
Click to expand...
Click to collapse
Xiaomi.eu has TWRP issue...
Go to https://www.androidfilehost.com/?w=files&flid=50678 and find your recovery (lmi) and flash it with fastboot and boot to recovery.
fastboot flash recovery twrp.img
fastboot boot twrp.img
Now download the new ROM 20.10.16, push it to the internet storage and install it dirty... Wipe Cache and reboot....
My problem is almost same, i unlock the bootloader to flash xiaomi.eu rom from global rom, unlocking and flashing custom recovery was done smoothly, when i tried to flash xiaomi.eu rom version 12.0.8 it booted back to recovery, and i format the data partition and booted to system, and same result. I tried global its same result.
Then i tried miflash tool, " antirollback error ".
Now i don't know what to do. Hope my precious poco f2 pro is not bricked, coz i can still manage to boot in custom recovery, and can use miflash tool but error.
Can someone out there help me please. Thanks in advance.
Eldybug said:
My problem is almost same, i unlock the bootloader to flash xiaomi.eu rom from global rom, unlocking and flashing custom recovery was done smoothly, when i tried to flash xiaomi.eu rom version 12.0.8 it booted back to recovery, and i format the data partition and booted to system, and same result. I tried global its same result.
Then i tried miflash tool, " antirollback error ".
Now i don't know what to do. Hope my precious poco f2 pro is not bricked, coz i can still manage to boot in custom recovery, and can use miflash tool but error.
Can someone out there help me please. Thanks in advance.
Click to expand...
Click to collapse
Since you have access to a properly working fastboot and recovery, I believe there is always a way to recover your phone.
I'll be glad to help you but for now, I'm more focused on my issue.
Only thing, while using miflash, be careful to never lock your bootloader since you would have to open your phone to access EDL mode in case of bootloop
(but you can lock it afterwards if you want)
Enricosteph said:
Xiaomi.eu has TWRP issue...
Go to https://www.androidfilehost.com/?w=files&flid=50678 and find your recovery (lmi) and flash it with fastboot and boot to recovery.
fastboot flash recovery twrp.img
fastboot boot twrp.img
Now download the new ROM 20.10.16, push it to the internet storage and install it dirty... Wipe Cache and reboot....
Click to expand...
Click to collapse
Well, the main issue here is that fastboot seems to be broken too...
i found this for you on the LOS rom for poco f2 pro (am not the autor) this is for the "Anti-rollback error" (i hope that can help you):
romabah said:
Gentlemen with EU versions of Poco F2 pro, could you help me out?
Right now i am running 12.0.2.0 QJKEUXM.
To flash Lineage i first need to flash MIUI V12.0.3.0.QJKMIXM via MiFlash. I tried to do that but got an Anti-rollback error.
Checking via fastboot i saw that my phones anti rollback value is 1, but MIUI V12.0.3.0.QJKMIXM firmware has an anti rollback of 0.
Some folks say to delete first 5-6 lines in text editor from .bat file, but at the same time people tell everywhere to NOT flash firmware with lower value that your current anti rollback.
Any advice? How did other EU folks fix this?
Edit: I fixed it! I will NOT and cannot claim that this will fix all rollback error's, but it fixed mine.
0) This is applicable to fastboot version of MIUI V12.0.3.0.QJKMIXM (aka tgz file that you need to extract twice)
1) Move the extracted firmware directory imi_global_images_V12.0.3.......ets.ets. ( map with flash_all.bat, images ) to C: directory and rename to something short, like xiaomiFirm.
This will solve a lot of weird error's as MiFlash doesnt like long directories
2) Within the moved map open flash_all.bat with text editor and delete everything starting and including "::check anti_version" to and including "echo %..."
This removes the anti rollback check somehow. The reason for only editing flash_all.bat is because this is the .bat file that is run when you choose clean all option in MiFlash, i assume you dont want to clean all and lock now do you?
3) After finishing flashing mine gave error Not catch checkpoint flash is not done, but booted normally. Gave me a heart attack.
Sanity check: When running cmd "fastboot getvar anti" it returned "anti: 1"
Meaning i just flashed a ROM with anti of 0 on a phone with a anti value of 1. At least i believe so.
In any case, thank all for giving feedback for other ways of fixing this.
Click to expand...
Click to collapse
I'll try to make a type C deep flash cable to flash fastboot, and edit this message to explain if this works
Thelm76 said:
Well, the main issue here is that fastboot seems to be broken too...
Click to expand...
Click to collapse
Try to hold down only Vol Down and connect it to your computer
Enricosteph said:
Try to hold down only Vol Down and connect it to your computer
Click to expand...
Click to collapse
I don't know if this was my cable or fastboot oem edl, but windows recognised the phone as qualcomm qdloader 9008. I'll now try to update fastboot, install twrp and check the extent of the damages.
Fangstergangsta said:
i found this for you on the LOS rom for poco f2 pro (am not the autor) this is for the "Anti-rollback error" (i hope that can help you):
Click to expand...
Click to collapse
Indeed, OP, try to flash everything from the start thep by step.
You must stop therapeutic relentlessness!!!
Just plug out the charger and let him die softly...
Put him back in his sweet box after his last breathe
Bury him in your garden with a decent burial : he deserve it!!!!
It's HIS TIME, dude....
Regards
Mastakony said:
You must stop therapeutic relentlessness!!!
Just plug out the charger and let him die softly...
Put him back in his sweet box after his last breathe
Bury him in your garden with a decent burial : he deserve it!!!!
It's HIS TIME, dude....
Regards
Click to expand...
Click to collapse
Haha it's not therapeutic relentlessness when you're sure it will live again in a few days (and fully working!)
It just need a good memory wipe and android replacement
As I managed to get to emergency mode, I can now easily replace its software
EDIT: I didn't know that for these xiaomi devices, you need very specific autorisations to flash something with EDL... Fortunately, after messing around with miflash, I managed to unlock myself out of this infinite loop
As I managed to get to emergency mode, I can now easily replace its software
Click to expand...
Click to collapse
How are you going to flash the software?
Well,
By using edl mode and miflash, I got some errors as I was not authorised to do this operation, so I rebooted to fastboot, reused miflash, and I don't know which kind of magic did that but after some files flashed and an error, I was able to boot on TWRP. With this done, I tried to keep my data but didn't worked, and as I have everything constantly backup, I dicided to do a flashall.
now, I think I have a good MIUI base to flash MIUI EU back
Thelm76 said:
Well,
By using edl mode and miflash, I got some errors as I was not authorised to do this operation, so I rebooted to fastboot, reused miflash, and I don't know which kind of magic did that but after some files flashed and an error, I was able to boot on TWRP. With this done, I tried to keep my data but didn't worked, and as I have everything constantly backup, I dicided to do a flashall.
now, I think I have a good MIUI base to flash MIUI EU back
Click to expand...
Click to collapse
I have the same situation plus no fastboot or recovery at all.. Please tell me how did you resolve it?
ghannaiem said:
I have the same situation plus no fastboot or recovery at all.. Please tell me how did you resolve it?
Click to expand...
Click to collapse
Is the phone detected by the pc in usb?
And when you press power+ sound + or - What is happening?
NOSS8 said:
Is the phone detected by the pc in usb?
And when you press power+ sound + or - What is happening?
Click to expand...
Click to collapse
Yes , detected by usb but as qcom 9008,
And when holding down power button with + or - vol it restarts again to 9008 .
So it is not detected by any means, but only detected in edl mode
ghannaiem said:
Yes , detected by usb but as qcom 9008,
And when holding down power button with + or - vol it restarts again to 9008 .
So it is not detected by any means, but only detected in edl mode
Click to expand...
Click to collapse
how did it happen?
My imei got lost so I tried to flash eng rom through MI flash to fix it. It flashes all except certain file called (aop. Mbn) so I tried to flash it by cmd commands via fastboot and then the phone bricked.. No booting to fastboot anymore , no recovery. even with disconnecting battery and reconnecting again... Phone only recognized in Edl mode and when flashing through MI flash it asks for edl authorization... Account login successful but then flash fail cuz account is not authorized. So I think The only solution will be authorized account or patched prog_ufs file
Code:
By Doing this, You may Void your warranty..
Neither Me nor XDA is Responsible for any Damage Caused for Your Mobile..
If you show Finger at me, I'll laugh at you..
Why there is need for this Guide?
When I got my Realme 5, I wanted to Unlock the Bootloader, Install the TWRP Recovery, root it and finally Install a Custom ROM. So, I've Searched for it and Finally Disappointed B'coz many Guides were wrong and some were Very Old and Outdated Guides.. So I've Researched and now with many problems, Finally I've Unlocked the Bootloader, installed TWRP and finally Flashed LineageOS 17.1.. So, this Guide saves your time, I've Included the Steps What I did, you guys can simply follow it..
This Guide is only applicable for Realme 5(rmx1911) and not for Realme 5i, Realme 5s or Realme 5 Pro..
Click to expand...
Click to collapse
Things You need to Continue :
A Windows Laptop/PC (Windows because, I am showing the Procedure with Windows)
Minimal ADB and FastBoot
Recovery (I've flashed PitchBlack Recovery, but you can also do this procedure with TWRP recovery)
Of course a Realme5 (rmx1911)
In-Depth Test apk
All the Download Links of above files are in Attachments..
Click to expand...
Click to collapse
Procedure :
Steps to Downgrade from RealmeUI 1 to ColorOS 6
If you're in Latest android 10 RealmeUI, first you need to downgrade to ColorOS 6 android pie.
To do so, download ColorOS package(.ozip package) from below link.
Open this .ozip package with File Manager app and Locate this package.
Click on that package, A pop-up will appear, In that Select "Upgrade Now" or something like that..
It will wipe your data and It will boot into ColorOS setup, Complete the Setup..
Users who are in ColorOS 6, need not to follow above Steps!
Click to expand...
Click to collapse
Steps to Unlock Bootloader:
Enable developer options in settings and enable OEM Unlocking, USB Debugging from Developer Options from Settings.
Download and Install In-Depth apk from attachments.
Open it and Click on Start Applying.
After 20min Open app and click on "Query Verification Status" .(if you dont see like this wait for some moretime, maximum it will take upto 24hours only)
If you see something like "Review Successful", You are good to go..
Select "Start the in-depth test", You will be forwarded to fast boot mode..
Connect the mobile to PC.
Now comes the role of PC/Laptop, Download the Fastboot and Minimal ADB, Recovery.img and vbmeta.img From the attachments.
Extract that fastboot zip in some Directory, Copy the recovery.img and vbmeta.img to the fastboot folder.
Open the Minimal ADB and Fastboot and in that open "cmd-here.exe"
Type "fastboot devices", then enter, You should see something like serial number.
Type "fastboot flashing unlock", then enter, now check ur phone you will see something like "Unlock" or similar to something..
You need to select the Unlock with the help of volume button and select with power button.
After Selecting "Unlock" all data will be deleted and Your Phone will be unlocked..
HURRAY, YOUR PHONE IS UNLOCKED
Installing Pitchblack Recovery :
After Unlocking Phone all the Data will be deleted, complete the setup wizard and enable USB Debugging.
Connect the Phone to PC via USB.
Open ADB Fastboot folder and select "cmd-here.exe".
Type "adb devices" you should see something like Serial Number.(If you did not see, re-insert the phone cable to another port and check)
Type "adb reboot fastboot", You will be forwarded to Fastboot mode.
Type "fastboot flash recovery recovery.img"
Type "fastboot flash vbmeta vbmeta.img"
Disconnect the Mobile from PC, then click on Volume down Button Until you get Something Like "Recovery" and Select using Power Button.
HURRAY! YOU'VE INSTALLED RECOVERY
IF YOU WANT TO ROOT YOUR DEVICE, DOWNLOAD MAGISK AND INSTALL IT FROM RECOVERY
Click to expand...
Click to collapse
IF YOU WANT TO GO TO RECOVERY AGAIN JUST BOOT INTO FASTBOOT(Power-off Your device, click on volume down button and power button simultaneously, within few seconds you will boot into fastboot) THEN CLICK ON VOL- BUTTON UNTIL YOU GET RECOVERY OPTION, THEN SELECT IT USING POWER BUTTON
Click to expand...
Click to collapse
You've Unlocked BL, flashed RECOVERY, Installed Magisk, Now what? Go and Search for your Favourite ROMs and flash them
Realme 5 Downgrade package link
{Mod edit}
triplr_dev_users
Test forum for ROM Builders !
All roms Welcome, All devices welcome!
Samsung Note 3,4 Qualcomm and exynos 5433
Galaxy Tab S2
Realme 5(rmx1991)
All things RPi 4 Family
An open discussion on Tech, Dev and Life
Welcome .
Rule 1. Have fun
Rule 2. Be nice
{Mod edit}
Reserved
supper sir i have very usefull i have flashed a lineage 17.1
with ur guide and i have unlocked boot lodder also thank u very much well done sir
Sensui--moksha said:
supper sir i have very usefull i have flashed a lineage 17.1
Click to expand...
Click to collapse
Glad, this helped!!
Why happend like this in depth test ?
Bebe's said:
Why happend like this in depth test ?
Click to expand...
Click to collapse
Sorry for the delay bro, I think you can't unlock the bootloader of Your Phone, bcoz it is not directly from the realme, I mean the phone which u bought is customized by your sim(carrier) company
Hello. The Downgrade file is not in the attachments thanks
nezuxiv said:
Hello. The Downgrade file is not in the attachments thanks
Click to expand...
Click to collapse
dude I have updated the post with the link to downgrade package, by the way thanks for informing
bro by installing pictblack recovery my phone got in a recovery bootloop and internal storgae is not showing ay files help pls
smarty7880 said:
bro by installing pictblack recovery my phone got in a recovery bootloop and internal storgae is not showing ay files help pls
Click to expand...
Click to collapse
Did you flash vbmeta.img ?
does the downgrade firmware supports realme in philippines ? thank you so much sir.
I am at color os v7 I also need to downgrade fast reply will be appreciated
Dar_shan_11 said:
I am at color os v7 I also need to downgrade fast reply will be appreciated
Click to expand...
Click to collapse
Yes, You need to downgrade...
I unlocked my bootloader ..than I installed recovery and after than I installed vbmeta.img
After that I tried to install Havoc Os.
Now I'm stuck at bootloop, can you help me
I must be blind but I can't find the downgrade file in your attachments...
(Edit) Never mind, it's not in the attachments. ^^;
Is there any guide to do it on realms UI?
i have RMX1911ex_11_A.31.
i should follow steps from Unlock Bootloader
correct?
It dœsn't work: my phone just comes back to the fastboot…
Hi,
After updating my OnePlus Nord (EU) to OxygenOS 12 and noticing how full of bugs it is, I've decided to flash PixelExperience on it.
I followed the official PixelExperience install guide: I successfully unlocked my bootloader, and then went ahead to flash the recovery.
Exactly as written in the guide, I performed a fastboot flash recovery recovery.img.
The command finished as expected without any errors, so I rebooted into the recovery with fastboot reboot recovery, only to get an error screen, with a title in Chinese and an error message: "The current image(boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it.", so my device got soft-bricked.
I tried flashing it again - didn't work.
So I tried flashing TWRP - also didn't work.
I tried to flash a stock recovery from this thread - also didn't work.
I at least tried to recover it back to stock, so I downloaded the MSM tool and Qualcomm drivers and tried to get my device into Qualcomm EDL mode.
I tried many combinations of button pressings, I tried fastboot oem edl, but I just couldn't get it into EDL mode, it just booted into fastboot every time.
How could I fix this - flashing a recovery or at least revert it back to stock?
Bro, OOS 12 Update messed everything, bc boot img in oos 12 doesnt work for flashing
U need to Switch Back to android 11 in order to flash anything..
U can use Edl mode to switch back to OOS android 11 then unlock bootloader and then everything works good
I'm too using Pixel Experience Rom after using edl for OOS 11 and now every Custom recovery and rom works
krish-ag said:
Oo, OOS 12 Update messed everything, bc boot img in oos 12 doesnt work for flashing
U need to Switch Back to android 11 in order to flash anything..
U can use Edl mode to switch back to OOS android 11 then unlock bootloader and then everything works good
I'm too using Pixel Experience Rom after using edl for OOS 11 and now every Custom recovery and rom works
Click to expand...
Click to collapse
Oh, I didn't know that!
It wasn't mentioned in any of the guides I read...
Anyways I tried for a week to get it into EDL mode without any success...
I installed the Qualcomm drivers, pressed the volume up + down buttons for 40 seconds then while pressing connecting it to my PC, then every time it just booted into fastboot.
How could I get it into edl mode?
AmitGold said:
Oh, I didn't know that!
It wasn't mentioned in any of the guides I read...
Anyways I tried for a week to get it into EDL mode without any success...
I installed the Qualcomm drivers, pressed the volume up + down buttons for 40 seconds then while pressing connecting it to my PC, then every time it just booted into fastboot.
How could I get it into edl mode?
Click to expand...
Click to collapse
In edl mode, u will not see anything on the phone screen.
To use edl mode, press vol up and down simultaneously (without power botton) for 10 secs and then connect it to pc via usb cable
Then u will hv to use the MSM tool according to ur nation (like India, EU etc) for a specific OOS version
Yeah I did exactly that, but my phone booted into fastboot
Kinda lost, tried this many times
AmitGold said:
Yeah I did exactly that, but my phone booted into fastboot
Kinda lost, tried this many times
Click to expand...
Click to collapse
Is adb working?
U can use adb reboot edl to reboot to edl...
but first prepare ur msm tool so that device dont reboot on timeout..
krish-ag said:
Is adb working?
U can use adb reboot edl to reboot to edl...
but first prepare ur msm tool so that device dont reboot on timeout..
Click to expand...
Click to collapse
Tried that also... Didn't work
AmitGold said:
Tried that also... Didn't work
Click to expand...
Click to collapse
did it just reboot or boot into bootloader again?
Also can u share a recorded video of the process i hv told u?
It booted into the bootloader.
Attaching a video of this process
Bro first thing, it should be of 10 secs not 30. I m pretty sure that's what preventing to to boot to edl
Second, i want a video of those adb method steps that i told u but now first try ur method only but for 10 secs
AmitGold said:
It booted into the bootloader.
Attaching a video of this process
Click to expand...
Click to collapse
I have the same issue, did you fix that?
Use a USB2 port if not already obvious. (I fought getting into EDL mode for hours the first time - maybe you already know this, sorry if redundant. 10 seconds, 40 seconds, doesn't matter, adl, fastboot, key presses - everyone focuses on the that. Finally with red cable and USB-2 port, it works easily.)