EDIT: I attached a zip with AIDA64's reports for this phone. One report has Magisk hidden from AIDA64, the other doesn't.
This mostly a copy of _cab13_'s Rooting the UMI F2 post as the same instructions for rooting that phone are how I rooted the S5 Pro. So please give _cab13_ thanks here if this helped you root your phone. I'll take a thanks for removing the orange state warning if I helped you with that
Please be patient when posting questions, I will get back to you as quickly as I can. I just have many responsibilities which take up a great deal of my time.
Rooting the S5 Pro
Disclaimers
This is important, please read thoughtfully.
whatever you do, NEVER EVER use SP Flash Tool in "Format All+Download" mode. This will wipe your IMEI['s]s and some other bad stuff will happen like loss of fingerprint sensor. This cannot be reversed by us.
Once bootloader is unlocked, warranty is considered void. By following this guide, you consent to that happening. Safety net CTS will not pass anymore unless you flash Magisk which hides the unlocked bootloader.
Never re-lock your bootloader while running anything unofficial as the phone will not boot until you unlock again.
And, once again, a lot of bad things can happen like boot loops, if that happens to you, don't freak out! Simply re-flash the stock ROM, redoing the rooting process from the start. It might be time consuming, but that's your safest bet!
More important even, have fun rooting, it's before all a hobby!
Various Resources
>>> Latest official stock ROM <<<
[Non European] UMIDIGI_S5Pro_20210107.V3.04
[European] UMIDIGI_S5Pro.E_20201130.V3.04
Minimal ADB and Fastboot by shimp208
> Magisk (and Manager) by topjohnwu <
Mediatek SP Flash Tool
UMIDIGI Community Forum S5 Pro Thread
Unlocking Bootloader
ATTENTION!! After unlocking the bootloader, all user data in the phone's memory will be lost, so do not forget to throw all the most important things on your computer or flash drive!
1) Activate "Developer options" through Settings > About Phone > Tap Build Number multiple times.
2) Open "Developer options" in Settings > System > Tap Advanced.
Enable "OEM Unlocking" and enter your password to confirm. Enable "USB Debugging" as well.
3) On Windows, download and install Minimal ADB and Fastboot by shimp208
On Linux, use your package manager to install android-tools-adb and android-tools-fastboot
4) Open command prompt (Win + R > type cmd) or a terminal on linux.
5) Plug your phone, accept the prompt about adb and the PC signature.
6) Type adb reboot bootloader to reboot in fastboot mode. Unplug your cable from your phone
and replug it after fastboot is printed at the bottom of the screen.
THESE NEXT TWO STEPS WILL COMPLETELY WIPE YOUR DATA
7) Unlock the bootloader using fastboot flashing unlock and pressing Vol+
8) Unlock the secure partitions using fastboot flashing unlock_critical and pressing Vol+
9) Restart using fastboot reboot
You will now always see "Orange State" at boot; this is completely fine and will only delay your boot by 5 seconds.
Rooting using Magisk patched boot.img
This is "experimental" and is probably overkill, but everyone managed to install Magisk with it.
1) Clean install UMIDIGI_S5Pro_20200702.V3.02 (or the European one) with SPFT by selecting the scatter file, pressing download an rebooting the phone
(Make sure it is in "Download Mode" and not "Format + Download")
2) Patch boot.img by copying it to your device, using Magisk Manager to patch it, and get back the magisk_patched.img in the Download folder back to your PC.
3) Start ADB while booted; run adb reboot bootloader. Alternative is to reboot to recovery and selecting "reboot to bootloader"
4) unlock if not already done with fastboot flashing unlock followed by fastboot flashing unlock_critical
5) In the following code, the vbmeta.img and the recovery.img are the stock files from the ROM you downloaded and extracted.
Code:
fastboot erase boot
fastboot --disable-verity --disable-verification flash boot magisk_patched.img
fastboot --disable-verity --disable-verification flash recovery recovery.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot reboot
When rebooting, install Magisk Manager. It will prompt to finalize the installation, you can do so.
Congratulations ! You are now a proud Magisk user ! All credits goes to @topjohnwu he's the real MVP here.
Returning to stock / Resolving issues
The best way to resolve any issue is to return to stock. Here is the method.
1) Download latest stock ROM on UMIDIGI's forums
2) Download SP Flash Tool if you don't have it yet (Windows only)
3) Extract stock ROM in SP Flash Tool directory. Refer to Flash Tool guide if needed.
4) Open SP Flash Tool, Download Tab, "Choose" in Scatter-loading file, select the scatter file in the stock ROM directory.
5) If you want to keep your data, untick "userdata" partition. MAKE SURE FORMAT IS NOT SELECTED!
6) Press Download and connect your device via USB. Reboot the phone or turn it off and everything will be flashed.
7) If you want a full stock experience, I recommend relocking the bootloader so that SafetyNet will pass. Get into fastboot mode by using adb reboot bootloader and use fastboot flashing lock_critical followed by fastboot flashing lock. This will wipe your data once more.
You should be good to go.
ONE LAST THING
Get rid of your orange state warning.
Download the attached zip file and extract.
Put your phone into fastboot and:
Code:
fastboot erase lk
fastboot erase lk2
fastboot flash lk lk_patched.img
fastboot flash lk2 lk_patched.img
fastboot reboot
No more orange state warning! Reflash the stock lk before unrooting, though.
ATTACHED LK FILE IS FOR UMIDIGI S5 Pro ONLY.
Thank you for re-posting this as an option to root the S5. I did get stuck on flashing the recovery. I have tried a few times and every time it just flashes orange , restarts and loads normally. I have verified root.
i have used the recovery found here
https://forum.xda-developers.com/android/general/guide-rooting-umidigi-s5-pro-magisk-t4151183
I have no success installing TWRP. Do you know if twrp has a recovery that will work?
Hey guys it's me again !
Got some good news : I bought a S5 Pro as well
And I ABSOLUTELY LOVE IT !
I might get into rooting it soon, idk.
Thanks for the shout-out @zerosava
hermeez said:
Thank you for re-posting this as an option to root the S5. I did get stuck on flashing the recovery. I have tried a few times and every time it just flashes orange , restarts and loads normally. I have verified root.
i have used the recovery found here
https://forum.xda-developers.com/android/general/guide-rooting-umidigi-s5-pro-magisk-t4151183
I have no success installing TWRP. Do you know if twrp has a recovery that will work?
Click to expand...
Click to collapse
No luck for me finding a custom recovery (twrp or anything else.)
If you have any exp with them, see if you can make the F2's (found in the F2 root thread) work. It SHOULD only need a minumum of tweaking, just to account for the (afaik) slight soc differences. i'm not gonna hold my breath. there seems to be a void when it comes to enthusiasm for this phone. by my serial no, i have the 4832nd phone manufactured. compared to serials ranging from 22000- 189000 for my other umis (f1play, s3pro, f2, power3)
I think I'll try making TWRP soon for it.
The F2 TWRP would not be usable this easily, it's easier to start fresh.
If anyone wants to try, download the sources for the F2 TWRP on my GitHub, then you need to extract the stock kernel and replace the F2's with the S5pro's
root working thanx
Hi guys ,i lost the imei on my phone and have the" Googlekeystate:fail", how can i fix them, thanks for you help.
QUICKLARA said:
Hi guys ,i lost the imei on my phone and have the" Googlekeystate:fail", how can i fix them, thanks for you help.
Click to expand...
Click to collapse
Sorry, but I made this clear in the original post:
Disclaimers
This is important, please read thoughtfully.
whatever you do, NEVER EVER use SP Flash Tool in "Format All+Download" mode. This will wipe your IMEIs and some other bad stuff will happen like loss of fingerprint sensor. This cannot be reversed by us.
I do not know how to help you. My only suggestion is to post your problem in UMIDIGI's forum here: UMIDIGI Forum
If anyone can help you, that's where to find them.
Please I need your help I reset it wrong with SP Flash Tool and now I get Googlekeystate: fail and it doesn't grab my fingerprint I'm desperate I need a solution please
Ruiz702 said:
Please I need your help I reset it wrong with SP Flash Tool and now I get Googlekeystate: fail and it doesn't grab my fingerprint I'm desperate I need a solution please
Click to expand...
Click to collapse
I am sorry, but you will have to contact UMIDIGI support. Only they can help you as far as I know. I feel for you, I really do. I did this when I was a newbie with my F1 Play.
QUICKLARA said:
Hi guys ,i lost the imei on my phone and have the" Googlekeystate:fail", how can i fix them, thanks for you help.
Click to expand...
Click to collapse
hello, good and bad news.. fix but fingerprints are lost for good
https://community.umidigi.com/forum.php?mod=viewthread&tid=19722&extra=&page=1
Ruiz702 said:
Please I need your help I reset it wrong with SP Flash Tool and now I get Googlekeystate: fail and it doesn't grab my fingerprint I'm desperate I need a solution please
Click to expand...
Click to collapse
hello, good and bad news.. fix but fingerprints are lost for good
https://community.umidigi.com/forum.php?mod=viewthread&tid=19722&extra=&page=1
i followed the instructions but i got stuck after step 4 it would be nice if this had a video walkthrough thanks for the guide though =w= 10/10 would try to root again lol
hello folks,
This message is not about rooting s5 but rather about downgrading. I posted on the umidigi forum but have not received an answer. So the problem is the new OTA update that they pushed out yesterday. After update I lost 4G connectivity and i am unable to restore it. I want to roll back to the previous update. They have the roms available on the forum and I downloaded one but what I am not sure is can I use SP flash tool to just download the older ROM version on top of the new one?
I see lots of manuals on how to update but how do I safely downgrade?
Any help is greatly appreciated.
Sticks
stick2020 said:
hello folks,
This message is not about rooting s5 but rather about downgrading. I posted on the umidigi forum but have not received an answer. So the problem is the new OTA update that they pushed out yesterday. After update I lost 4G connectivity and i am unable to restore it. I want to roll back to the previous update. They have the roms available on the forum and I downloaded one but what I am not sure is can I use SP flash tool to just download the older ROM version on top of the new one?
I see lots of manuals on how to update but how do I safely downgrade?
Any help is greatly appreciated.
Sticks
Click to expand...
Click to collapse
Do a "download only" flash of the "super", " vbmeta_system", and "vbmeta_vendor" partitions only (uncheck all other partitions) from the previous ROM. That should do it.
ZeNNoP said:
i followed the instructions but i got stuck after step 4 it would be nice if this had a video walkthrough thanks for the guide though =w= 10/10 would try to root again lol
Click to expand...
Click to collapse
What precisely stuck you?
There is a new update firmware please make a rooting tutorial on youtube.,
Somebody made a custom TWRP and posted it on here. So if that'll help anyone out and get them to make a tutorial video, that be great. 'Cause I'm reading this over and over again, and I think I can do it, but I'm being very hesitant about it. And it's getting me all frustrated. I had it on "Flash Mode". And when I continued typing it out, it didn't go through and that had me on a raging panic attack. Luckily, it didn't mess up. But now I'm more hesitant. Please make a quick tutorial, doesn't even have to be perfect...
TWRP is at the bottom of this page:
[MT6785]How To Root Umidigi S5 Pro And Install TWRP 3.4.0 Recovery ~ Techswizz
To Root Umidigi S5 Pro, we will be using the Adb Tool Mode with TWRP recovery for Umidigi S5 Pro. It will be wise to read the post very well before flashing the recovery to avoid any Device errors or brick.
www.techswizz.com
Thanks for this guide. I am completely lost with step 7 and 8. What does the Unlock the bootloader using fastboot flashing unlock and pressing Vol+ mean?????? Where do you enter the unlock code and what is it?
bmaz121 said:
Thanks for this guide. I am completely lost with step 7 and 8. What does the Unlock the bootloader using fastboot flashing unlock and pressing Vol+ mean?????? Where do you enter the unlock code and what is it?
Click to expand...
Click to collapse
I am able to get FastBoot Mode on my screen (through step 6). I plug the phone back in per directions & I hear the Windows device connected chime.
I type: fastboot flashing unlock in the same cmd window
and I get "<waiting for any device>" in the cmd window and it hangs.
Every few seconds I hear the Windows device disconnected noise, but no device connect chime. This lasts indefinitely.
I repeated step 7 several times with variations with the Vol+ button: pressing first, holding down while pressing enter in cmd window, pushing afterward, holding down afterward, etc. Same results as described above.
Any help available? Should I not unplug my phone from the PC? The F2 directions did not require that.
thanks!
Related
Hello there,
this is my first thread so maybe I can make some mistakes.
I tried to install Lineage in my Mi A1, with their wiki guide. Then the device bootlooped, I tried with a lot of guides, tutorials, I used Cosmic Dan's TWRP for formating partitions, installed vendor images...
But the phone was ****ed up... I tried to install a fastboot ROM but the phone didnt have signal, or it was stucked in the SIM password...
If someone is facing some similar problem, I would like to help you. Like I said before, I tried with a lot of methods, a lot of different recoveries, I tried https://forum.xda-developers.com/mi-a1/development/twrp-stock-8-1-0-t3856328 this one too, all tipes of fastboot or TWRP stock ROMs... but no clue of how solving it.
So THIS is the only way(for me at least) for solving it. It is in Indian, but you can follow his steps if you flashed any ROM before, is quite easy.
1. - You need your phone to be unlocked, if you dont have it, just use the command "fastboot oem unlock" while you are in fastboot mode. There are plenty of guides for this.
2- You have to run MiFlash. If you dont have it HERE you have the version that I used.
3. Download and extract THIS Rom. Then copy the link to MiFlash like he does in the video, or browse for the folder.
4. Plug your phone in Fastboot mode, and click reflresh, till you see a device in the MiFlash tool. Check that you have the "clean all" option in the bottom of the app. DONT CHOOSE THE LOCK ONE.
After this your phone still wont work, dont worry, just press Vol Down+Power again till' the phone enters fastboot again.
5. Download TWRP and boot the phone with the recovery using the command "bootloader boot twrp-3.2.3-1-tissot.img.html" in the adb folder(same steps that the other TWRP versions with temporal boot)
6. Download this Backup and copy the folder inside the 7z to the device(not to the sd) and replace the TWRP folder.
7. Use the restore option in TWRP for restoring the backup, and the go to Reboot -> Bootloader and you will be in Fastbood mode again.
8. REPEAT the "4" step, but THIS TIME use the FLASH ALL AND LOCK option.
I hope it works!
Ps. Im from Spain, so it could be some grammatical mistakes xd
Hi there just incase someone else who had problems [like me]
who is hesitant or looking for a guide on how to install Blu_Spark TWRP and Root the device.
The guide below will work 99.9% of the time. just follow the instructions carefully
Necessary Files:
Install OnePlus 6 Driver
Install Fastboot Drivers
TWRP Image
Magisk 20.1
twrp-3.3.1-x_blu_spark_v9.107_op6
Stock boot image thanks [URL="https://forum.xda-developers.com/member.php?u=6994095" @Akhil701[/URL]
Step 1: [dont do this if you have installed ADB and Fastboot already]
Install Oneplus 6, ADB and Fastboot Drivers from the link above
* Reboot PC after installing
Step 2:
Put
Code:
Stock Boot Image [boot.img]
twrp-3.3.1-x_blu_spark_v9.107_op6.zip and
Magisk-v20.1.zip
on your internal storage
Also Put
Code:
twrp-3.3.1-11-enchilada-Q-mauronofrio.img
on your desktop
Step 3: Reboot device in fastboot/bootloader mode
Step 4: Connect Device to PC Via USB Cable
Step 5: On your desktop Press Shift Right Click then click the [Open Command Prompt Here]
Step 6: on the CMD Windows Type
Code:
fastboot devices
Press enter and see if your device shows up.
Step 7: type in the CMD Window
Code:
fastboot flash boot twrp-3.3.1-11-enchilada-Q-mauronofrio.img
press enter then after that on your phone screen use volume up or down button to reboot to recovery
Step 8:
Once you have the TWRP Screen
flash the stock boot image [boot.img] in boot partition [DO NOT Reboot!]
now go back and flash the Blu_Spark TWRP and then reboot to recovery
Step 9: Rooting
Flash Magisk 20.1.zip then reboot to system.
Thats it! no data will be wiped as long as your bootloader is already unlocked.
thanks to
@Funk Wizard for the initial instruction on how to install twrp and root
@eng.stk for the Blu_Spark TWRP
@mauronofrio for the initial TWRP Image
@Akhil701 for the stock boot.img
@remewer for inspiration to build this guide.
Patched boot.img or why we need the boot image after flashing OOS10 via local update?
Sh0X31 said:
Patched boot.img or why we need the boot image after flashing OOS10 via local update?
Click to expand...
Click to collapse
im not sure about that also. im just hesitant to skip that step. it might break something. thats why i added that step on this guide
Thnx, this was a very easy walkthrough.
Only thing I want to say is that not everyone knows how to flash the 'boot.img' through TWRP. Maybe you can explain that in more detail.
no patched boot.img you need
1. connect your OP6 to PC
2. flash TWRP (from mauronofrio) by fastboot from PC
3. reboot from fastboot to recovery
4. in TWRP flash stock img OOS, don´t reboot
5. in TWRP flash TWRP (blu_spark 9.107)
6- reboot to TWRP to another slot
7. in TWRP flash Magisk 20.1
8. reboot to system
I have noticed this too, probably they have changed somehow the system, even fastboot boot doesn't work anymore....
I had to install magisk via boot.img patching
Functionally on OOS 10.0.1 OP6 ?
So I was unable to flash the new OTA through twrp running on my rooted OP6.
As such, I opted to install the new OTA through the "local install" option.
That worked great. Settings area all the same. Bootloader still unlocked (I double checked).
Drivers are all installed on my Windows 10 PC.
However, no matter what I attempt to flash from command prompt I always get:
FAILED (remote: unkown command)
Does anyone know of a solution yet?
I have been reinstalling drivers and rebooting my PC with no luck thus far.
Any ideas?
Thanks in advance.
Update:
Whelp now that it is upgraded to Android 10 (and was wiped of all data when I locked and then unlocked the bootloader again) it will not allow me to downgrade back to Andriod 9 through the local upgrade option and since I can not get fastboot to accept any commands I am stuck now in Andriod 10 without the ability to change anything at the moment.
Brisky86 said:
So I was unable to flash the new OTA through twrp running on my rooted OP6.
As such, I opted to install the new OTA through the "local install" option.
That worked great. Settings area all the same. Bootloader still unlocked (I double checked).
Drivers are all installed on my Windows 10 PC.
However, no matter what I attempt to flash from command prompt I always get:
FAILED (remote: unkown command)
Does anyone know of a solution yet?
I have been reinstalling drivers and rebooting my PC with no luck thus far.
Any ideas?
Thanks in advance.
Update:
Whelp now that it is upgraded to Android 10 (and was wiped of all data when I locked and then unlocked the bootloader again) it will not allow me to downgrade back to Andriod 9 through the local upgrade option and since I can not get fastboot to accept any commands I am stuck now in Andriod 10 without the ability to change anything at the moment.
Click to expand...
Click to collapse
i knew it while reading but thanks to the screenshot you provided you saved me from sounding "user error" once again and piss of so many who prefer to blame things and others LOL
in short, wrong command, it's fastboot flash boot <image name>
BTW and since i'm already at it, if anyone has a Mac runniing 10.15 "Catalina" and fastboot is working from terminal, i'd like to learn how he/she's done it
just came to my mind to ask here since i have to use windows 10 under parallels desktop to fastboot flash my android stuff at the moment and of course that's just an "Emergency" choice for me, everyone using both platforms will understand
magnamentis said:
i knew it while reading but thanks to the screenshot you provided you saved me from sounding "user error" once again and piss of so many who prefer to blame things and others LOL
in short, wrong command, it's fastboot flash boot <image name>
BTW and since i'm already at it, if anyone has a Mac runniing 10.15 "Catalina" and fastboot is working from terminal, i'd like to learn how he/she's done it
just came to my mind to ask here since i have to use windows 10 under parallels desktop to fastboot flash my android stuff at the moment and of course that's just an "Emergency" choice for me, everyone using both platforms will understand
Click to expand...
Click to collapse
Wow. Okay.
This is becoming a comedy of errors on my part.
Oh boy now I am getting Qualcom flashdump messages...
Huh now it is just booting normal but not letting me get into the new recovery flash...
I got it all fixed.
Thank you everyone for your help and patience with my posts.
Does 10.0.1 still have the ability to do screen-off gestures for music? I like 10 but on my wife's 7t, either she didn't turn them on, our it didn't have them so I'm curious if there same thing is happening with this? I also noticed on her 7t, constant data problems when's switching from WiFi to data. Sometimes data won't come back and only a reboot solves. I know it's a bug on OOS 10 on 7t but wondering if it's a device specific bug or an Android 10 bug? Anyone having op6 issues with data not coming back when switching from WiFi?
WIFI problem solved!
Below OOS 10.0.1 back inTWRP
Wipe: cache, system and vendor
Flash OOS 10
Flash boot img
Flash TWRP
Flash Magisk
Reboot system
Reboot recovery
Flash OOS 10.0.1
Flash boot img
Flash TWRP
Flash Magisk
Reboot system
Wifi works
After rooting 10.0.1 with magisk 20.1 mobile network is gone. no sim pin, no metwork. after unroot everything is fine
Hello Mates,
i updated my rooted oneplus 6 from 10 to 10.01 and after that use this method to root again. But there is a Problem now: My WiFi doesnt work? I cant activate it.
Do anybody know how i can fix that Problem?
Thank you in Advance
Best Regards
Coktail
As above. No wifi, no sound. What's going on?
Coktail said:
Hello Mates,
i updated my rooted oneplus 6 from 10 to 10.01 and after that use this method to root again. But there is a Problem now: My WiFi doesnt work? I cant activate it.
Do anybody know how i can fix that Problem?
Thank you in Advance
Best Regards
Coktail
Click to expand...
Click to collapse
cubic25 said:
As above. No wifi, no sound. What's going on?
Click to expand...
Click to collapse
Look 2 posts up...
ryanallaire said:
Look 2 posts up...
Click to expand...
Click to collapse
Unroot doesn't work for me. Still no wifi and audio.
Hi guys, sorry to resurrect this thread. I did everything in the correct order using 10.0.3.0 and after step 8 (reboot after flashing blu_spark) my phone gets stuck on blu_spark splash screen without any option to boot into twrp. Normal boot results in bootloop... Any ideas? Do I need to use different versions of twrp.img and .zip?
dynamode said:
Hi there just incase someone else who had problems [like me]
who is hesitant or looking for a guide on how to install Blu_Spark TWRP and Root the device.
The guide below will work 99.9% of the time. just follow the instructions carefully
@Funk Wizard for the initial instruction on how to install twrp and root
@eng.stk for the Blu_Spark TWRP
@mauronofrio for the initial TWRP Image
@Akhil701 for the stock boot.img
@remewer for inspiration to build this guide.
Click to expand...
Click to collapse
Hello.
I´m on 10.3.0 op6, I followed all the steps and when i finish the step 8 and reboot, i stuck on the recovery message. I repeat all the steps flashing clean rom and always have the same problem.....
Can someone help me? Because i don´t know another way for installing magisc....
Thanks!!!
loggstar said:
Hi guys, sorry to resurrect this thread. I did everything in the correct order using 10.0.3.0 and after step 8 (reboot after flashing blu_spark) my phone gets stuck on blu_spark splash screen without any option to boot into twrp. Normal boot results in bootloop... Any ideas? Do I need to use different versions of twrp.img and .zip?
Click to expand...
Click to collapse
I am in exactly the same position here.
Followed all the steps and am now stuck on the blu_spark boot screen for the past 15 minutes
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…
Lenovo Tab P11 (2021г.) - Обсуждение - 4PDA
Lenovo Tab P11 (2021г.) - Обсуждение, Планшет, 11"
4pda.to
Translator from Russian: https://www.deepl.com/translator
Basically
1. Enable OEM Unlock in Developers Settings
2. (Your host PC should have LMSA installed) Open command window, and go to where ADB is
3. Turn your tablet off. Press and hold volume down and power buttons to enter bootloader
4. Enter the following in command window
Code:
fastboot flashing unlock
. Answer yes to unlock bootloader
warning: your tablet is wiped during the process!!![/B]
5. Reboot
To root, patch boot with Magisk
You can use LMSA to download matching ROM, and use rescue to update ROM if necessary. You can get needed boot at c:/program data/LMSA/download/romfiles/
Copy boot.img to your phone and use Magisk to patch, and copy patched_boot.img back to host computer.
Turn your tablet off and enter bootloader
Switch to fastbootd
Code:
fastboot reboot fastboot
Flash the patched boot
Code:
fastboot flash boot
Press spacebar once and drag and drop the patched boot onto command window, and press enter
Reboot
does this work with Lenovo Pad Pro 2021 (SD870) ?
Thanks for the guide, I've successfully unlocked the bootloader and rooted with Magisk.
I also installed the unofficial TWRP from here: https://unofficialtwrp.com/twrp-3-4-2-root-lenovo-tb-j606f/
However I didn't flash the provided vbmeta.img and everything still seems to be working fine, including booting into TWRP.
Anyone know if not flashing it may cause issues to appear?
The reason I didn't flash it is because someone else on another thread here said they got stuck in a boot loop after flashing it and that after restoring they decided not to flash it and everything worked fine, which seems to be my experience too, but maybe there are implications I'm not aware of with not flashing it.
I had this issue too, I had to run the command:
Code:
fastboot flashing unlock
aurelienlux said:
Thanks for the guide, I've successfully unlocked the bootloader and rooted with Magisk.
I also installed the unofficial TWRP from here: https://unofficialtwrp.com/twrp-3-4-2-root-lenovo-tb-j606f/
However I didn't flash the provided vbmeta.img and everything still seems to be working fine, including booting into TWRP.
Anyone know if not flashing it may cause issues to appear?
The reason I didn't flash it is because someone else on another thread here said they got stuck in a boot loop after flashing it and that after restoring they decided not to flash it and everything worked fine, which seems to be my experience too, but maybe there are implications I'm not aware of with not flashing it.
Click to expand...
Click to collapse
I flashed vbmeta.img and now I can't boot into system/fastboot/recovery. Do you know how to restore ? I also tried LMSA, device cannot be detected.
cyatsl said:
I flashed vbmeta.img and now I can't boot into system/fastboot/recovery. Do you know how to restore ? I also tried LMSA, device cannot be detected.
Click to expand...
Click to collapse
DO IT ON YOUR OWEN RISK! I HAVE NOT TESTED ON A LENOVO TAB P11 YET!
These are the steps for rooting a Lenovo Tab M8 FHD!
I think essential are the points 19 to 21, to flash the boot.img ONCE AGAIN after vbmeta.img.
It discribes ... this part is key, otherwise you'll bootloop!
Fully charge tablet
Turn tablet on
Skip as much of the initial setup process as possible, however you MUST be connected to the WiFi in order to allow unlocking of your bootloader (Start -> More/Accept -> no wifi/Set-Up Offline -> skip setting current time set -> Choose reporting options / Hit Accept -> Skip Pin -> Skip Lenovo ID -> Lenovo User Experience Program (choose if you want to skip or not) -> Choose navigation etc) Get to the home screen
Swipe down from top of screen and open Settings
Developer Tools (enable dev tools if you don't yet have access) -> Enable USB Debugging
Developer Tools -> Enable OEM Unlocking (again, if you're not on WiFi, it may not allow you to do this)
Connect tablet usb and usb to computer (Click "allow" when the usb debugging popup comes up)
./adb devices (Make sure the computer can see the tablet)
./adb reboot bootloader
./fastboot devices (Make sure the computer can see the tablet)
./fastboot flashing unlock then press volume-up on the device
./fastboot reboot`
On the Lenovo loading splash screen, you should now get the Orange State alert that the device is unlocked. It may take a bit to reboot as you've just wiped all data again and it must do initial setup
Device boots up normally. Now you can do real setup steps if you like, or you can ignore everything like in Step 3 above.
Enable USB Debugging again (Step 4-5)
Grab the boot.img and vbmeta.img from the LMSA TB_8505FS_S300025_201015_BMP update. Copy the boot.img to the tablet, taking note of the location (e.g., ./adb push boot.img /sdcard/)
Install latest version of Magisk Manager (doesn't need to be the Canary version, can be the regular version) and patch the boot image.
Clicked on "Install" on the righthand top in magisk manager
Clicked on "Next" Righthand top.
Selected "Select and Patch a File".
picked the boot.img file I had copied in step 1. Take note of the location of the patched image (magisk_patched.img), and copy it to your PC.
Reboot into bootloader again (./adb reboot bootloader)
Flashed the magisk patched boot.img ./fastboot flash boot path/to/magisk_patched.img
Flash the VB meta with the disable-verification flag ./fastboot --disable-verification flash vbmeta path/to/vbmeta.img
Flashed the magisk patched boot.img AGAIN!!!!!! (this part is key, otherwise you'll bootloop) ./fastboot flash boot path/to/magisk_patched.img
Reboot, you should now be rooted (can confirm in Magisk Manager) ./fastboot reboot
Is it ok/safe to flash this to TB-J606L?
It is the same model but with sim card and 4G.
Sometimes WiFi vs 4G models have the same software and detect differences on startup and sometimes not... Not sure about this model. I would prefer to not (soft)brick it.
Hi there. First time boot-unlocker needing help. I also have the P11 TB-J606F and would like to root it. I believe I need to do this first. I cannot seem to get any response from the tablet when doing this. In "regular tablet" mode I can connect and do ADB-commands, but in this "bootloader" mode I cannot seem to connect. I just get "Waiting for any device"
Could it be a driver issue? In device manager there is an Android device with an exclamation mark? I have no clue how to update this? Automatic doesn't work and I can't seem to find any drivers that work. I am not sure if this indeed is the problem, but you know - help needed, please.
skodkassen said:
Hi there. First time boot-unlocker needing help. I also have the P11 TB-J606F and would like to root it. I believe I need to do this first. I cannot seem to get any response from the tablet when doing this. In "regular tablet" mode I can connect and do ADB-commands, but in this "bootloader" mode I cannot seem to connect. I just get "Waiting for any device"
Could it be a driver issue? In device manager there is an Android device with an exclamation mark? I have no clue how to update this? Automatic doesn't work and I can't seem to find any drivers that work. I am not sure if this indeed is the problem, but you know - help needed, please.
Click to expand...
Click to collapse
Not sure if it helps. I had a similar issue with my Lenovo Tab M8 FHD.
The big issue was to get the android driver for win10, fastboot was not working. I found it under win10 update >> optional updates >>driver updates >> there was a medi.... as installable update. Afterthem fastboot was working fine.
sc00ter98 said:
Not sure if it helps. I had a similar issue with my Lenovo Tab M8 FHD.
The big issue was to get the android driver for win10, fastboot was not working. I found it under win10 update >> optional updates >>driver updates >> there was a medi.... as installable update. Afterthem fastboot was working fine.
Click to expand...
Click to collapse
And thus my problems were solved. It took me a few hours going nowhere and thanks to you everything is now cool
sc00ter98 said:
Not sure if it helps. I had a similar issue with my Lenovo Tab M8 FHD.
The big issue was to get the android driver for win10, fastboot was not working. I found it under win10 update >> optional updates >>driver updates >> there was a medi.... as installable update. Afterthem fastboot was working fine.
Click to expand...
Click to collapse
Solution
Download and install LMSA and use Motorola ADB driver Device Manager
You should see P11 with no driver. Update driver > Let me choose > Android ADB > choose Motorola ADB driver
aurelienlux said:
Thanks for the guide, I've successfully unlocked the bootloader and rooted with Magisk.
I also installed the unofficial TWRP from here: https://unofficialtwrp.com/twrp-3-4-2-root-lenovo-tb-j606f/
However I didn't flash the provided vbmeta.img and everything still seems to be working fine, including booting into TWRP.
Anyone know if not flashing it may cause issues to appear?
The reason I didn't flash it is because someone else on another thread here said they got stuck in a boot loop after flashing it and that after restoring they decided not to flash it and everything worked fine, which seems to be my experience too, but maybe there are implications I'm not aware of with not flashing it.
Click to expand...
Click to collapse
Be aware: The link above is not the right TWRP for the P11 Pro. I lost two days an bricked my tablet to find out that. The TWRP for P11 Pro is at https://unofficialtwrp.com/twrp-3-4-2-root-lenovo-tb-j706f/
37_ said:
does this work with Lenovo Pad Pro 2021 (SD870) ?
Click to expand...
Click to collapse
Did you try it ? I think this method can work on Pad Pro 2021 SD870
mingkee said:
Basically
1. Enable OEM Unlock in Developers Settings
2. (Your host PC should have LMSA installed) Open command window, and go to where ADB is
3. Turn your tablet off. Press and hold volume down and power buttons to enter bootloader
4. Enter the following in command window
Code:
fastboot flashing unlock
. Answer yes to unlock bootloader
warning: your tablet is wiped during the process!!![/B]
5. Reboot
Click to expand...
Click to collapse
does work with me . it repeat the same error:
C:ladb>adb reboot bootloader
error: device '(null)' not found
Two questions:
1. Did anyone lose their Widevine level when unlocking, installing Magisk and/or rooting? I currently have L1 and would hate to lose that (to L3).
2. Is it possible to use the TWRP version for the TB-J706F for the TB-J716F as well? Basically, they are very similar devices, but the screen (90 Hz OLED) and processor (Snapdragon 870 instead of Snapdragon 730G) are different, but I don't know what is relevant for TWRP. Otherwise, could I also root without TWRP?
Thanks in advance!
HANN1860BAL said:
Two questions:
1. Did anyone lose their Widevine level when unlocking, installing Magisk and/or rooting? I currently have L1 and would hate to lose that (to L3).
2. Is it possible to use the TWRP version for the TB-J706F for the TB-J716F as well? Basically, they are very similar devices, but the screen (90 Hz OLED) and processor (Snapdragon 870 instead of Snapdragon 730G) are different, but I don't know what is relevant for TWRP. Otherwise, could I also root without TWRP?
Thanks in advance!
Click to expand...
Click to collapse
1. Yes you will lose L1 when unlock bootloader
2. No , TWRP with very different hardware so don't hope so much .
I see there is no reason to root TB-J716F now, current firmware is stable and smooth
luizkun said:
1. Yes you will lose L1 when unlock bootloader
2. No , TWRP with very different hardware so don't hope so much .
I see there is no reason to root TB-J716F now, current firmware is stable and smooth
Click to expand...
Click to collapse
Thanks for the fast reply!
Is it possible to lock bootloader after rooting again and gaining L1 back with keeping device rooted?
That's true, but I want to use some rooted apps, like Titanium Backup and AdAway ;-)
HANN1860BAL said:
Thanks for the fast reply!
Is it possible to lock bootloader after rooting again and gaining L1 back with keeping device rooted?
That's true, but I want to use some rooted apps, like Titanium Backup and AdAway ;-)
Click to expand...
Click to collapse
you can root after unlock bootloade by patching boot.img from stock rom (by magisk ) and install magisk without TWRP
So if anyone is interested in booting a GSI Image Here is the guide: also thanks to @Dollscythe I just updated it as he forget to write me a step for flashing the vbmeta.img..
1. you need to download the firmware file for your model
2. you need to open it with your zipping software of choice (i use 7zip) And after it unzips you need to unzip AP file to get to the recovery.img.lz4
3. you extract the recovery.img and you patch it to enable fastbootd https://github.com/Johx22/Patch-Recovery you will also find the info how to patch it on the link, it is easy if you know how to follow it) - Currently is NOT working, the dev said to me that he will fix this once his exams are over. (If you know how to Decompress the Iz4.img to get just the .img it will probably work - didn't try tho.
4. this step will wipe your device so make sure to back up (unlocking the bootloader) And it will also trigger your Knox!
To unlock the bootloader you need to go to settings, about phone - software info and press on the build number like 7times to enable developer options. After that go to developer options and enable OEM unlock.
Turn off the phone, put the USB C cable into the phone (but not into the computer yet!) Then hold the volume + and volume - button at the same time and put the cable into the phone.
When you are in the download mod you will see the instructions on how to unlock the bootloader.
5. Boot into the system and do the first time setup (make sure to connect to wifi, but skip any prompts to register or login to accounts)
6. double check if the oem unlock toggle is still on, then reboot to download mode
7. you need to flash the patched bootloader using odin - you flash your patched recovery in AP window in Odin. Then you immediately boot into the recovery (you gotta boot to your new recovery immediately after the flash is complete, make sure to hold the key combination for recovery immediately after pressing start in odin to get it right. otherwise, the system will wipe your newly flashed recovery and you'll have to do step 7 again)
8. You will now notice that your recovery has a new option: fastbootd mode (yes there's a d in there, it's not a typo, it stands for fastbootdynamic mode) 9. once you're in, your device now officially supports fastboot. you just do "fastboot flash system *the_name_of_the_system_image_you_downloaded.img", RIGHT AWAY AFTER THAT flash vbmeta.img (it can be found in the telegram group) and once that is done flashing just exit fastbootd mode back to the recovery, then format data and then then reboot for system images, i recommend pixel experience https://github.com/ponces/treble_bu...4-ab-vndklite-12.1-20220518-UNOFFICIAL.img.xz 10. you'll be greeted by a google bootlogo and thats a success.
Good luck!
Bucika said:
RIGHT AWAY AFTER THAT flash vbmeta.img (it can be found in the telegram group)
Click to expand...
Click to collapse
I'd just add that the proper command to flash vbmeta.img is ./fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (I don't use "./" though, as I've included platform-tools in my path env variable).
Not disabling verity/verification sent me to a bootloop from hell after rebooting... I began reading more carefully the Telegram chat, found the proper command and I'm now setting my PixExp as I write.
One thing I wish people on here would give more instructions than they do it's not easy on button the recovery image I don't know why you say it's easy cause it's not that makes no sense you don't put no links into the description of where to ago why don't somebody do like they used to do and actually give a s*** about what they put on this website
jdg007 said:
One thing I wish people on here would give more instructions than they do it's not easy on button the recovery image I don't know why you say it's easy cause it's not that makes no sense you don't put no links into the description of where to ago why don't somebody do like they used to do and actually give a s*** about what they put on this website
Click to expand...
Click to collapse
The purpose of XDA "Developers" was actually to share knowledge between developers, you know, people who actually know how the most basic stuff works. It's open up for the public, sure, but most of the stuff you can find here are not meant for the average noob that doesn't know how to unlock a bootloader.
The instructions are pretty clear for people who can use a google search. Don't expect everything to be spoon fed, put in a little effort.
There's a difference between saying "OMG this is too complicated why don't you explain it with a video or why don't you tell me step by step on how to flash custom firmware on my phone" and saying "Hey I'm stuck in step 3, I don't understand the part here. This is what I've tried so far..."
I bet for the most part, the first person would be ignored while the second person would more likely get a response.
That means to offend you in any way or whatever I just wished people would give more explanations on what they post because you know I don't make no sense on how you patch the recovery I'm new at this it's my it's my fault I do know how to unlock bootloaders not bootleggers and I do know how to install TWRP and Flash zip balls but as when it comes to patching something the only thing I know how to pack is using magisk That's the boot image I'm sorry hope Hope you can help me out
If you don't mind email me a copy of that recovery image that you got Text I sure would appreciate it Just looking forward For your reply
Thanks @Bucika, here's a guide that might be a bit more noob friendly. Also a big thanks to @Dollscythe for their help.
Files can be found here.
These are the latest GSIs.
1. Unlock bootloader by opening developer options and flipping the "unlock bootloader" switch.
2. Boot into download mode (press and hold vol + and - while plugging into computer).
Press and hold vol + to enter unlock mode. Accept and click enter. Your phone will reset.
3. Using Odin, flash fastbootd through AP. (recovery.img).
4. Press and hold volume + key as the phone reboots, as when you restart again it will reverse this step. You should be in recovery now.
Click on fastboot.
5. Get fastboot working on your computer. Test connection by using the command "fastboot devices" to see if your device is there.
6. Run the command fastboot flash system [name of gsi file]. (without square brackets)
7. When you're done, run ./fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
8. Go back to recovery and wipe your phone.
9. Go back into fastboot, flash magisk file if you would like root: fastboot flash boot magisk
10. Wipe again, reboot.
11. Once you are fully booted in, open settings > phh settings (first entry) > misc settings > then scroll down until you find "force fps"
Change that to the @120fps option.
Hope this helps! Note that this is unofficial and WiFi hotspot doesn't work, Samsung Health has issues too. I couldn't get my watch 4 working with GSI.
This will blow your Knox bit fuse!
Ivan Fuentes Hagar said:
I'd just add that the proper command to flash vbmeta.img is ./fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (I don't use "./" though, as I've included platform-tools in my path env variable).
Not disabling verity/verification sent me to a bootloop from hell after rebooting... I began reading more carefully the Telegram chat, found the proper command and I'm now setting my PixExp as I write.
Click to expand...
Click to collapse
I find myself in a bootloop too after this step, how did you get out of the bootloop?
edit, answer to my own question in case it helps someone in the future: plug phone into a pc and then hold `volume up + volume down` buttons to enter download mode.
edit 2 if after flashing a GSI rom your device wont boot, plug it into power and wait a few minutes.
I know I am kind of late but after flashing the pixel experience GSI, it is stuck in the google logo. What do I do?
ActuallyJammy said:
I know I am kind of late but after flashing the pixel experience GSI, it is stuck in the google logo. What do I do?
Click to expand...
Click to collapse
flash another gsi this gsi doesn't work on a53 unless you use pixel experience 12
TringQuack said:
flash another gsi this gsi doesn't work on a53 unless you use pixel experience 12
Click to expand...
Click to collapse
Alright, so I got an old build of PE 13 to work, but somewhy the newer security patches don't work. Is there any reason, or is it just not compatible at all? Also, there's a problem with the fingerprint; it detects it as if the fingerprint scanner is in the back when it is on the screen. Is there any fix? Mainly because it's my primary phone.
ActuallyJammy said:
Alright, so I got an old build of PE 13 to work, but somewhy the newer security patches don't work. Is there any reason, or is it just not compatible at all? Also, there's a problem with the fingerprint; it detects it as if the fingerprint scanner is in the back when it is on the screen. Is there any fix? Mainly because it's my primary phone.
Click to expand...
Click to collapse
new patch was introduced in trebledroid that fixes this fingerprint issue, you can either use another gsi built on trebledroid on the date of jan 31 or later, or wait for Ponces to make a new PE build for A13
TringQuack said:
new patch was introduced in trebledroid that fixes this fingerprint issue, you can either use another gsi built on trebledroid on the date of jan 31 or later, or wait for Ponces to make a new PE build for A13
Click to expand...
Click to collapse
Could you give me a GSI rom with a patch and similar to PE?
@TringQuack What's your current state with A53?
Running GSI? Stock?
ThugMaster said:
@TringQuack What's your current state with A53?
Running GSI? Stock?
Click to expand...
Click to collapse
Stock
@TringQuack How do I know if the build is compatible with A13?