Database Develop

Huawei Honor Note 8 - Unlock Bootloader, TWRP, Xposed Framework

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is my first walkthrough so I will do my best to do this properly. The Honor Note 8 does not have a forum yet, and this is the third thread for this phone. Hopefully we can get a forum up soon.
PLEASE NOTE THAT UNLOCKING BOOTLOADER WILL WIPE YOUR DEVICE AND POSSIBLY VOID YOUR WARRENTY!!!
I'M NOT RESPONSIBLE IF SOMETHING DOESN'T WORK.
Unlock Bootloader
Follow the steps here to begin the Bootloader Unlock process:
https://www.dc-unlocker.com/how-to-read-huawei-bootloader-unlock-code
1. a) Install the application
1. b) Follow the steps on the above page to put phone into "Manufacture Mode"
1. c) Under "Select Manufacturer", choose "Huawei Phones" and under "Select Model", choose the model of your phone
1. d) Click on "Buy Credits". You should end up being emailed a username and password, return to the Unlocker Client, and input those two
1. e) The Unlocker Client should return the bootloader unlock code
2. a) Enable Developer Options by clicking on the build number multiple times
2. b) Turn on USB Debugging
3. Prepare TWRP custom recovery before preceeding further. You can get it from here: https://drive.google.com/open?id=0B4xzs81XsmURVTRnUDJHdl9CQlE
3. Prepare and install ADB and Fastboot tools. I used this one http://forum.xda-developers.com/showthread.php?t=2588979
4. Go into the folder with your recovery and open a CMD (if you used system-wide ADB as linked above, otherwise place recovery in your ADB folder)
5. Put the phone into Bootloader mode with:
Code:
adb reboot bootloader
. This will take you to the bootloader mode (white screen with some small text)
6. Now type:
Code:
fastboot oem unlock <UNLOCK_CODE>
where
Code:
<UNLOCK_CODE>
is the bootloader code that the Unlocker Client gave you
Loading TWRP Custom Recovery
7. Your phone may reboot when the process is complete. We want to go back into Bootloader mode, so follow Step 5 again to go back to bootloader mode
8. Now type:
Code:
fastboot flash recovery <NAME_OF_YOUR_RECOVERY.img>
The recovery will flash over to your device. We want to reboot into the recovery mode.
9. Now type:
Code:
fastboot reboot
but just before you hit ENTER on that command, start holding VOLup and VOLdown at the same time (as explained below)
This phone has two recoveries on it, which is great since it makes it really hard to brick. In order to access custom recovery, you need to hold down both VOL buttons during boot process (from the very beginning) in order to access the custom recovery.
Once you have entered TWRP, you will most likely notice that it is in CHINESE. If you don't read chinese, follow the steps below to change to English UI in TWRP:
Change to English UI in TWRP
10. TWRP has two columns of 4 buttons, 8 buttons total. I have labeled the buttons as per their position as below:
1 2
3 4
5 6
7 8
11. Click button 6 to go to the Settings, then click on the "Globe" icon, then switch to english and click the button in the bottom right corner.
BACKUP!!
12. I highly recommend you now do a TWRP backup and place the backup on an External SD card (not the internal memory). This will save your ass if you mess anything up or it doesn't work for you. Do a full backup (select ALL of the options).
Installing Xposed
Grab the Installer APK here: http://forum.xda-developers.com/showthread.php?t=3034811
and the Framework zip here: http://dl-xda.xposed.info/framework/sdk23/arm64/
Put both files onto your SD card.
13. Boot into your rom, install the APK file (you may need to enable "unknown sources")
14. Then boot back into TWRP. Do this by restarting the phone, and just as the screen goes black, hold down both VOL buttons until you see text on the screen.
15. Install the framework, wipe cache/dalvik and reboot the phone
ROMs
There are several roms, all of which can be found here: http://forum.xda-developers.com/general/general/huawei-honor-note-8-roms-t3487575
I will try to update this post with instructions on how to install them once I have the process down properly.
Thanks to:
@benmeroff for his posting of all of those ROMs and his work on the original thread.

The link to the xposed installer is dead

jdantow said:
Installing Xposed
Grab the Installer APK here: http://forum.xda-developers.com/show....php?t=3034811
Click to expand...
Click to collapse
Just another small reminder this Xposed apk link is broken. Could I just download any Xposed apk or was this link for a specific version for the Note 8?
Thanks

remix435 said:
The link to the xposed installer is dead
Click to expand...
Click to collapse
Thank you! I updated the link, can you confirm it is working now from your end? Thanks so much!
The thread ID is 3034811 so if you take
Code:
http://forum.xda-developers.com/showthread.php
and add
Code:
?t=3034811
it should work for you

jlomein said:
Just another small reminder this Xposed apk link is broken. Could I just download any Xposed apk or was this link for a specific version for the Note 8?
Thanks
Click to expand...
Click to collapse
Thank you! I updated the link, can you confirm it is working now from your end? Thanks so much!
The thread ID is 3034811 so if you take
Code:
http://forum.xda-developers.com/showthread.php
and add
Code:
?t=3034811
it should work for you

Hopefully either a camera port or a camera hack can come about from developing. Anybody know about possible camera hack thats the only thing (IMO) this phone needs

jdantow said:
Thank you! I updated the link, can you confirm it is working now from your end? Thanks so much!
Click to expand...
Click to collapse
Thanks, downloaded Xposed 3.1.1 apk from that link now.
Cheers

hi
after i flashed trwp and did back up i stuck in bootloop
tried to flash kingvip rom - no luck. tried to recover from back up but stil in boot loop.
can anyone help me, please

Anyone happen to have the img for the modem? I believe mine may be corrupted.

hi i will my boodloader unlock my Note 8. The phone will not unlock. I have the ulock key. I hvae the Build Nummber B027.

Hi guys, a question...
The is no way I can install this drivers that are required... if I click the setup icons nothing happens at all, and if i try manually all i get is 4x "Android device" in the device manager, and locating drivers in the designated folders does not help, it still says "windows did not find the driver for your device...."
Anyone maybe had a similar problem/solution?
Thanksss

Bubreg said:
Hi guys, a question...
The is no way I can install this drivers that are required... if I click the setup icons nothing happens at all, and if i try manually all i get is 4x "Android device" in the device manager, and locating drivers in the designated folders does not help, it still says "windows did not find the driver for your device...."
Anyone maybe had a similar problem/solution?
Thanksss
Click to expand...
Click to collapse
Just google huawei drivers.... I had the same question but when i installed HiSuite the drivers was inside - it work fine, but it will always pop up when you connecting phone...

falc1 said:
Just google huawei drivers.... I had the same question but when i installed HiSuite the drivers was inside - it work fine, but it will always pop up when you connecting phone...
Click to expand...
Click to collapse
Thank you man, worked like a charm! I got the bootloader code... but since it's gonna wipe everything if I unlock it, I'm gonna wait until the next weekend most probably, too busy these days.

Hi guys,
i was able to unlock the bootloader but i can't flash the recovery and every time i try it display "remote: command not allowed".

Good morning.
I hope for Christmas to be a holder of Honor Note 8.
To unlock the bootloader you need to pay 4 euro through dc-unlocker.com program?
Thank you

m3sari0 said:
Hi guys,
i was able to unlock the bootloader but i can't flash the recovery and every time i try it display "remote: command not allowed".
Click to expand...
Click to collapse
Same thing happend to me
I relocked the bootloader then unlock it again and it works

player1990 said:
Same thing happend to me
I relocked the bootloader then unlock it again and it works
Click to expand...
Click to collapse
thanks man it worked.

TWRP - changing language
OP - thank you for this thread. Was able to follow the steps and get most of the things accomplished.
One thing that i am having trouble with is - changing the TWRP language from Chinese to English. In button #6, the globe icon is not even clickable. All others are, but that one is not. Any ideas? Thanks!
EDIT: I got it to work. It seems some icons in the corners of the screen can be a little hard or slow to respond... if you (a future reader) are having the same issue - try kind of mini swiping in circles over that icon and it will eventually respond.

Hi,
I requested the unlock code on the Huawei site but I get this error:
The Huawei ID used to apply for the unlock code has not been used on the device for more than 14 days.
How can I do?
Some might apply to me

MarkAndroid said:
Hi,
I requested the unlock code on the Huawei site but I get this error:
The Huawei ID used to apply for the unlock code has not been used on the device for more than 14 days.
How can I do?
Some might apply to me
Click to expand...
Click to collapse
You have to wait 14 days or pay for the credits on DC-unlocker app

Mi A2 - Failed to boot - after system update

Hello everyone, yesterday morning, Sunday 12/15/19, the system message "restart the device to make the system update effective".
So I do as I have always been.
The phone, an Mi A2, goes into bootloop and then a white screen appears on a black background with the title:
"<!> Failed to boot"
"Press the Volume keys to select then the Power button to continue.
RETRY
POWER OFF "
Choosing "RETRY" verifies bootloop 3 or 4 times and then the recovery mode screen appears which says:
"Can't Load Android system. Your data may be corrupted. You should get the message you need to perform at factory data reset and erase all user data stored on this device."
It gives me the choice between:
-Try again
-Factory data reset
Choosing "Try again" returns the same routine as when "RETRY" is selected In the previous black background screen, bootloop and then the black background white screen described at the beginning.
I MUST ACCESS AND SAVE THE VERY IMPORTANT CONTENT. :crying:
I have all the photos and videos of my newborn daughter. I usually backup but this inconvenience suddenly caught me.
I surfed and I saw that many people found this problem after an update .. but I never found any solutions. I called the Xiaomi center in Novara indicated by the site but they told me that they only serve as a collection center to send to the assistance in the company Xiaomi, saying that the assistance resets the phone to restore its functioning and does not save the data. I tried to start the fastboot, the device is recognized by the PC and shows the locked bootloader. The program MiFlash asks me to start to install a set of drivers and then immediately generate an unhandled exception and crash.
Attached the images.
Can you help me? I do not know what to do..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

You should try to use adb in recovery, if it works, you could digit "adb pull /sdcard".

Continue rebooting with external power on. Android One with A/B slots is supposed to reboot into previously (before OTA) active slot.

Aerobatic said:
Continue rebooting with external power on. Android One with A/B slots is supposed to reboot into previously (before OTA) active slot.
Click to expand...
Click to collapse
Thank you, can you explain me better what I should try to do?

HTCDevil said:
You should try to use adb in recovery, if it works, you could digit "adb pull /sdcard".
Click to expand...
Click to collapse
Is there any guide to do that?

pedrix82 said:
Is there any guide to do that?
Click to expand...
Click to collapse
I don't think so, when you are in recovery you should try to verify if your device is connected with "adb devices" and then you should use the command "adb pull /sdcard". But it usually works with custom recoveries, and if you have prevently enabled usb debugging.

pedrix82 said:
Thank you, can you explain me better what I should try to do?
Click to expand...
Click to collapse
First you can try to search this forum and read dozens of discussions of the same issue. Meanwhile you can plug in power adapter and reboot several times with pauses, probably sometimes switching to stock recovery and to fastboot mode, and then leave phone powered for a night.

HTCDevil said:
I don't think so, when you are in recovery you should try to verify if your device is connected with "adb devices" and then you should use the command "adb pull /sdcard". But it usually works with custom recoveries, and if you have prevently enabled usb debugging.
Click to expand...
Click to collapse
Thanks....I will try, I don't remember if I enabled the usb debugging mode, for sure I saw with fastboot that I have the bootloader Locked.

nothing to do...i tried ADB mode, but it is not enabled, only fastboot mode where i can do nothing because the bootloader is locked.
I also tried to install the Xiaomi tool, but it doesnt recognize the device.
i dont know what to do....

Did you try the factory data reset?

1N4148 said:
Did you try the factory data reset?
Click to expand...
Click to collapse
Hello...ehm...not, the aim is to recover all the data, photos and documents that are stored inside...

Same thing happened to me. You should manually switch the active partition in fastboot.

Zedsdeadbaby said:
Same thing happened to me. You should manually switch the active partition in fastboot.
Click to expand...
Click to collapse
Hi, I already tried to do what you suggest, but it is not possible with the bootloader Locked.
Anyway, can you tell me what I have to do to change the active partition? Maybe I don't do it as I should....

@pedrix82: I can only repeat, though you do not read and trust:
- the only (legal*) way to save data in bootloop with locked device is to boot;
- all other options are blocked for a locked Mi A2, - resetting, unlocking, etc. will erase user data; switching Slots and/or loading TWRP need unlocked phone; stock recovery is useless;
- Android One partitions system with A/B Slots was specifically designed to solve problems of failed OTAs, see https://source.android.com/devices/tech/ota/ab and https://android.googlesource.com/pl...ware/+/master/include/hardware/boot_control.h
Which means that: if you have bootloop after OTA on full stock (and have not tampered device yourself), after numerous attempts to boot -> the bootloader MUST detect that active Slot does not have bootable OS and MUST switch to the other Slot.
(non-legal*) - or read memory chip content at low-level and decipher encrypted data.

Aerobatic said:
@pedrix82: I can only repeat, though you do not read and trust:
- the only (legal*) way to save data in bootloop with locked device is to boot;
- all other options are blocked for a locked Mi A2, - resetting, unlocking, etc. will erase user data; switching Slots and/or loading TWRP need unlocked phone; stock recovery is useless;
- Android One partitions system with A/B Slots was specifically designed to solve problems of failed OTAs, see https://source.android.com/devices/tech/ota/ab and https://android.googlesource.com/pl...ware/+/master/include/hardware/boot_control.h
Which means that: if you have bootloop after OTA on full stock (and have not tampered device yourself), after numerous attempts to boot -> the bootloader MUST detect that active Slot does not have bootable OS and MUST switch to the other Slot.
(non-legal*) - or read memory chip content at low-level and decipher encrypted data.
Click to expand...
Click to collapse
Thanks,
It's really long time that I'm rebooting the mobile since it happened...
But cyclically and alternate I got the two image attached to the main post....

try a "fastboot continue" in adb

hello everyone, update.
unfortunately I was unable to recover anything and proceeded with the factory reset.
The phone has reset and everything is working.
So I thought to try to do a file recovery as you do for deleted files.
for the various recovery applications I need to root the device.
For this phone should be really simple but I'm still stuck in.
I followed one guide, then another, and then another .... all with the same procedures.
the result is that twrp recovery, if loaded with Vol + and pwr button hangs on the custom recovery logo.
I can only start the twrp recovery installed in the secondary partition of the phone.
but from this recovery, even if I install Magisk, with a successful results from the recovery, I do not root the device. I verified root with Magisk manager and rootchecker.
Help.... thanks

pedrix82 said:
... So I thought to try to do a file recovery as you do for deleted files.
Click to expand...
Click to collapse
I do no believe you'll be able to undelete files after factory reset.
pedrix82 said:
... for the various recovery applications I need to root the device. ... I followed one guide, then another, and then another .... all with the same procedures.
Click to expand...
Click to collapse
This guide works for everybody, except that
(1) there is obsolete "fastboot oem unlock" command stated which should better be changed to "fastboot flashing unlock", and
(2) guide does not mention that each unlock step is to be approved on phone, and
(3) guide skips step of patching stock boot.img in phone with MagiskManager, - while exactly this step creates archived copy of stock boot image in /data root, thus allowing to restore images (actually restoring stock boot image) before downloading next OTA, and
(4) only 1st variant - that is booting into patched boot image and then making "Direct Install" is safe - it allows to check that patched boot image is suitable for ROM.
pedrix82 said:
...the result is that twrp recovery, if loaded with Vol + and pwr button hangs on the custom recovery logo.
I can only start the twrp recovery installed in the secondary partition of the phone....
Click to expand...
Click to collapse
IMHO that just means that you did not do your homework (I mean you have not read guides and discussions and Google info with links I provided) well enough to understand that with A/B slots partitions structure there is no separate /recovery partition in phone (instead, recovery is embedded into /boot image), and thus we cannot just "flash TWRP" into MiA2.
Instead, TWRP can only be embedded into boot image (patching previously flashed suitable boot image), which is made by installing TWRP.zip in temporarily booted TWRP.img. Thus, if you want to have both root and permanent TWRP (I still do not see why anybody needs permanent TWRP with rooted stock), first get root with patched boot image, and then install TWRP patching this Magisk-patched boot image once more.
And I do think that "TWRP 4pda edition" is working better than so called "official TWRP".

Found the solution,
First u need to get to the recovery menu by pressing vol up + power, tap it multiple times after retry boot...you have to be quick...and eventually will get to the android robot pic with "no command"....keep pressing till you get to the full recovery menu. (this might take multiple tries)
Then go to update using adb. (you need all the files for adb, usb drivers, latest mi a2 update zip, you can find tutorials in youtube/google )
after updating it should boot up fine with all data intact.
If latest update versions dont boot, try repeating will older version.
Make sure you backup everthing afterwards! and enable oem unlocking &usb debugging for potential future issues.
Hope this helps!

[Guide] Unlock Bootloader Tutorial for realme C11 (Android 10) !

Hello Guys! This is Aryan, & In this Thread we Gonna discuss how to Unlock Bootloader in realme C11 Officially !
[Disclaimer]
First, please read the “Disclaimer” carefully.
1. After unlocking your phone ALL OF YOUR DATA WILL BE ERASED! Backup before you Proceed.
2. In-depth test may have unforeseeable impacts on your phone.
3. If you are installing Custom ROM/GSI Some functions may not operate Properly because of third-party firmware, such as the photo-taking function of the camera. It may also cause device damage.
4. Personal and confidential information on phone may leak, and security may be compromised.
5. Though You will continue to Recieve Realme UI Updates If you are Unrooted
[Preparation]
Whats Needed
1.) realme C11- with 60%+ battery
2.) 1 x USB Cable
3.) 1 x PC / MacBook
4.) In Depth Tool ( Attached With the Guide Down)
5.) A Brain
[Unlocking The Bootloader]
1.) Open Unlock Tool
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. Click “Start applying”.
3. Please read the disclaimer in detail, select the checkbox, and submit your application
4.) The Application Will be checked by realme Servers..(Wait 10 mins)
5. The unlock tool apk will show the status of the unlock request- Successful
6. You can now click “Start the in-depth test” and the device will reboot automatically. The following string will display on the screen:
Code:
fast boot_unlock_verify ok
7. Now Download and install the fastboot tool on your PC
https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/
8.) Now in Fastboot Mode type this command
Code:
fastboot flashing unlock
Press enter
9.) On your phone press the Volume Up key to select “UNLOCK THE BOOTLOADER” (or press the Volume Down key if you have changed your mind to select “DO NOT UNLOCK THE BOOTLOADER”).
When you click the Volume Up, your phone will reboot and enter the in-depth test mode - all user data on the phone will be erased - I recommend you perform a data backup prior to applying.
10.) Now type
Code:
fastboot reboot
Enjoy You have successfully unlocked Bootloader !!
Some FAQs
Q.) Does Bootloader Unlocking Void warranty?
-> In India, Bootloader Unlocking Doesnt Void Warranty But Rooting Does !!
Q.) How to flash back the official ROM after installing a custom ROM/GSI?
-> Users need to go to a service center to flash the device FREE of charge.
Q.) Will I Get Software Updates After Unlocking ?
-> Unlocking the bootloader may cause for the secure user data partition to become inaccessible. Yet if you simply unlock the bootloader (without flashing custom recoveries or rooting) you will still receive official software updates (OTAs).
Q.) I'm a Developer, Where are Kernel Sources?
-> Here https://github.com/realme-kernel-opensource/realmeC11_realmeC12_realmeC15_AndroidQ-kernel-source
--------------------------------------------------------------------------------------------------------------------------------------------------------
If You found the thread useful ! Press Thanks
~ TechyMinati

Q.) How to flash back the official ROM after installing a custom ROM/GSI without going to service centre?
-> We can download firmware file(.ozip) from Realme Software Update site and flash it from stock recovery.
Q.) Where I can find driver for Realme?
-> https://www.androidfilehost.com/?fid=10763459528675593731
Q.) How to relock the bootloader?
Flash stock rom even if you are on stock rom.
Download the unlock tool again to apply to exit the in-depth test.
Click “Apply to exit in-depth test”. You should manual operation enter the Fastboot mode(Press both the Volume down button and the Power button when power is off).
In the Fastboot mode, use the engineering command below on your PC to re-lock the bootloader.
- Enter the command: adb reboot bootloader
- Press “Enter” on your keyboard
- Enter the command: fastboot flashing lock
- Press “Enter” on your keyboard
Press the Volume Up button to select the “Lock bootloader” option (or press the Volume Down button to select “Do not lock bootloader" and keep it unlocked).
Then enter command "fastboot reboot”. The phone will reboot and exit the in-depth test mode. All user data on the phone will be erased - we recommend you perform a data backup prior to applying.
Q.) Are there any risks after unlocking the bootloader?
-> Please be aware that realme can’t guarantee the full functionality, and will not be responsible, for any third-party unsigned custom ROM being flashed onto your device after the bootloader is unlocked. An unsigned third-party custom ROM may not have gone through the thorough tests that realme run for each device and software version that realme release.​​A third-party custom ROM may not work Properly on your device, and certain functions and services may cease to work. The performance and device data may also be affected, and may damage the device permanently. In the worst case, unlocking bootloader will cause physical injuries or material damage for ex. due to device overheating.​

Cool thanks for this
Cool Info !! Thanks for bootloader relock tutorial
HemanthJabalpuri said:
{Mod edit: Quoted post shortened for better reading & scrolling experience!}
Click to expand...
Click to collapse

Hey I want to install corvus in my realme c11. But I can't find any custom recovery tools or roms for this device. Can you provide one please?

thesi47 said:
Hey I want to install corvus in my realme c11. But I can't find any custom recovery tools or roms for this device. Can you provide one please?
Click to expand...
Click to collapse
Custom ROMs need alot of efforts to bring up , I'm trying but It takes time. Thanks Hope u understand

Official tutorial for Android 10 is released at https://c.realme.com/in/post-details/1365228796868915200

where the link "4.) In Depth Tool ( Attached With the Guide Down)" stupid ass *****

Where can I get the Unlock Tool?

unlock tool in this thread
realme Community
Welcome to realme Community, your virtual playground to learn the latest tech news, win exclusive prizes, or simply chat about realme!
c.realme.com
direct link
https://download.c.realme.com/flash/Unlock_tool/DeepTest_realmeC11.apk
But I had no succes, Instaled the tool, run the tool, but when it says "Within approximately 15minutes, the unlock tool apk will show the status of the unlock request"
I had no luck, it waited indefinetly.
Is there any other way how to unlock bootloader?

Help me my device realme c11 RMX2185

How To Guide [GUIDE] [RUI3] Unlock bootloader on RealmeUI 3 with deep testing.

It is now possible to unlock bootloader using the in-depth deep testing app, however it will only work on Thailand firmware, so we are going to flash the Thailand firmware and use the in-depth app on it.
Links:
MTKClient: https://drive.google.com/file/d/13KohUUeuzVoGKxVWIuLDZx11PV8EeMBj/view?usp=sharing
SP Flash Tool: https://drive.google.com/file/d/1McZ11On8XbxGgE-hMA_nZqErHI_QwjQT/view?usp=sharing
MTK Drivers: https://drive.google.com/file/d/1UExJQxI1DmBGeDoYPul5YTXitOnsU6zx/view?usp=sharing
Thailand Firmware: https://drive.google.com/file/d/192KboBbW1eXzb6DWVlGAkGE-PEcgnHBJ/view?usp=sharing
Deep Testing APK: https://drive.google.com/file/d/1pESMmJef6Gm9YlJAE7OA_DDNnhFn3Jpz/view?usp=sharing
Libusb port filter: https://sourceforge.net/projects/li...ibusb-win32-devel-filter-1.2.6.0.exe/download
Flashing Thailand firmware:​We are going to flash this in SP flash tool, first, let's setup MTK authorization bypass (if you have already setup python and drivers then skip this)
Install python from https://www.python.org/downloads/ and make sure it's configured
Go to the Driver folder, right click cdc.acm.inf and install it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Install libusb port filter, afterwards click Next and hold volume up and down button, then choose MediaTek USB Port.
Now click install, next install UsbDK from here: https://github.com/daynix/UsbDk/releases/
Once you have done that, open a CMD/Powershell in the directory of MTKClient, write pip3 install -r requirements.txt and python mtk payload, hold the volume up and down button and plug the device in
If everything went well, you should be seeing this:
Now open SP Flash tool, go to Options > Option
Now go to Connection and select UART, set the baud rate to 921600
Now, open the scatter file (MT6785_Android_scatter.txt) from the directory of the firmware, it should load the firmware
Unselect opporeserve2 and click the Download button, it should start flashing
Once it is done flashing, you should see this:
Don't forget to reboot the device into recovery mode (volume down + power) and format data.
Updating to RealmeUI 3:​Since it is not possible to use the deep testing app on RealmeUI 2, you must update to RealmeUI 3, simply update it from the update app in settings, if you do not get the update, we can't do anything about it.
No need, replaced firmware link with RealmeUI 3 Thailand firmware, just flash that and use the in-depth app in the guide!
Using the deep testing app and unlocking the bootloader:​Download and install the deep testing app, tap "Apply Now" and accept the agreement, you should be seeing this now:
Wait 3 to 5 minutes, close the app and reopen again, tap "Query verification status" and you should see this:
This means your device now has unlocked fastboot access, tap "Start deep testing" and the device will reboot to fastboot mode
If you see this, the device is now in fastboot mode, to unlock the bootloader plug the device into a PC and write fastboot flashing unlock in Fastboot/ADB directory, you should see this:
Press the volume up button, the bootloader is now unlocked, congratulations!
NOTE: you can return to any EEA/Indian firmware you were on before and still have the bootloader unlocked.
Credits:
@bkerler for MTKClient

I tried this method on my primary Realme 8 device (Bangladeshi varaint) and it did worked.

Nice tutorial!

Also a pro tip for recovery mode can't be accessed after changing firmware and device keep rebooting after every 5 mins while stuck in realme bootanimation
download latest platform tools from google's official developer website, go to fastboot mode, enter command "fastboot reboot recovery"
you will be in recovery mode
then format data
your device will boot to OS after that

Does it work on realme UI 3.0 C.09 (bootloader locked)?

AJ⁰⁰⁷ said:
Does it work on realme UI 3.0 C.09 (bootloader locked)?
Click to expand...
Click to collapse
It shouldn't matter which firmware you are on right now, as for updating to TH RUI3 firmware it dosen't matter which C.0x it is as long as it's RealmeUI 3.

plarfman said:
It shouldn't matter which firmware you are on right now, as for updating to TH RUI3 firmware it dosen't matter which C.0x it is as long as it's RealmeUI 3.
Click to expand...
Click to collapse
Thank You

AJ⁰⁰⁷ said:
Does it work on realme UI 3.0 C.09 (bootloader locked)?
Click to expand...
Click to collapse
No. It's not working on RUI3 c.09 version. I've tried on my Bangladeshi 8/128 GB variant. And it got bricked after flashing the Thailand firmware.

ShahriarX1 said:
No. It's not working on RUI3 c.09 version. I've tried on my Indian 8/128 variant. And it got bricked after flashing the Thailand firmware.
Click to expand...
Click to collapse
Ohhz that's bad @plarfman

plarfman said:
It shouldn't matter which firmware you are on right now, as for updating to TH RUI3 firmware it dosen't matter which C.0x it is as long as it's RealmeUI 3.
Click to expand...
Click to collapse
I think you misunderstood it. I was asking that can I flash it over my Indian C.09 firmware?

plarfman said:
It shouldn't matter which firmware you are on right now, as for updating to TH RUI3 firmware it dosen't matter which C.0x it is as long as it's RealmeUI 3.
Click to expand...
Click to collapse
Was the Thailand firmware you attached in the post official??
Cause I got an error while flashing it. It says the firmware is not official.

ShahriarX1 said:
Was the Thailand firmware you attached in the post official??
Cause I got an error while flashing it. It says the firmware is not official.
Click to expand...
Click to collapse
Show a screenshot.

ShahriarX1 said:
No. It's not working on RUI3 c.09 version. I've tried on my Bangladeshi 8/128 GB variant. And it got bricked after flashing the Thailand firmware.
Click to expand...
Click to collapse
Stuck on recovery mode text? Then you should erase userdata, metadata and md_udc using mtkclient
And yes, mine is also Bangladeshi 8/128 varaint.

I don't know why after unlocking, entering recovery mode gets difficult. I wish that can be accessed while pressing buttons.
It's like recovery combo turns into fastboot combo
Also Oppo/Realme stock recovery has a problem when magisk is installed. It will bootloop forever when reboot to recovery from magisk and it's pretty hard to get into fastboot mode that moment.
The real fix for that problem is restore stock boot and dm-verity image

plarfman said:
Show a screenshot.
Click to expand...
Click to collapse

AE_Fahim said:
Stuck on recovery mode text? Then you should erase userdata, metadata and md_udc using mtkclient
And yes, mine is also Bangladeshi 8/128 varaint.
Click to expand...
Click to collapse
Flash is not completing bro. Have a check on the Screenshot and suggest.

ShahriarX1 said:
Flash is not completing bro. Have a check on the Screenshot and suggest.
Click to expand...
Click to collapse
Looks like your file got somehow corrupted. You can try downloading ofp file, manually decrypting it and merging multiple super.img using simg2img (super 2 must be Thailand) and setting super download is true from scatter file.

all set! I went to fastboot mode using deeptest tool. But i don't know what to do after that to unlock the bootloder device. Kindly help me!

Yadhevdev66 said:
all set! I went to fastboot mode using deeptest tool. But i don't know what to do after that to unlock the bootloder device. Kindly help me!
Click to expand...
Click to collapse
in fastboot mode enter
Code:
fastboot flashing unlock

can you send the fastboot drivers?

Sony Xperia XA2 - Flashing TWRP stuck on "waiting for any device"

HELP!
I installed platform-tools_r33.0.2-windows and UniversalAdbDriverSetup, now i'm trying to flash TWRP on the XA2 Phone by using this cmd command:
adb devices
- daemon not running, starting now at xxx
adb flash recovery twrp.img
- waiting for any device
What am i doing wrong?? Please help!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Boot phone in fastboot mode
Execute "fastboot flash recovery twrp.img"

LR7875 said:
Boot phone in fastboot mode
Execute "fastboot flash recovery twrp.img"
Click to expand...
Click to collapse
How? Im pressing volume up and then connecting the phone to the pc, then i see a blue light. Is this fastboot mode? Thats what im already doing for 3 hours...

Yeah just did it again... volumeup+connect phone to pc, blue light appears on phone (fastboot mode i asume).
on pc in cmd i type adb devices, it starts the daemon.
then i type "fasboot flash recovery twrp.img"
result in cmd: "waiting for any device"
Wtf?

I swear this is so cancer can't handle this ****, the F is wrong with sony? This phone is buggy AF im trying to insall TWRP for like 4 hours now, this is a ****ing joke. What a waste of time.

Try the 15 seconds adb and fastboot driver if you haven't already

LR7875 said:
Try the 15 seconds adb and fastboot driver if you haven't already
Click to expand...
Click to collapse
This? https://forum.xda-developers.com/t/...vers-15-seconds-adb-installer-v1-4-3.2588979/
I doubt it will be any different from the platformtools adb? How could this help?

LR7875 said:
Try the 15 seconds adb and fastboot driver if you haven't already
Click to expand...
Click to collapse
You mean minimal adb ? or can you provide a link?

Connect the phone in fastboot mode (LED = blue) and open the device manager. Do you see the phone under "Other Devices" or "Android" with an exclamation mark? Then you need an ADB/bootloader interface driver. Get this for example:
https://developer.sony.com/file/download/xperia-xz2-driver/
(Yes, XZ2! There is no official XA2 driver)
Unzip it somewhere and force install the driver:
Right click on the device manager entry from above, "Update driver", "Browse my computer...", "Let me pick...", "List/show all...", "Have disk...", browse to the folder from above, open the selected .inf file and install.
Fastboot should work now. At least that's how I got it to work on a new PC.
BTW, just use "fastboot devices" to check whether it works. If your device doesn't appear, you don't need to try other fastboot commands - it won't work.

I have this problem, when installing twrp to my Sony Xperia XA2 (H3123), I am trying to install several versions of Twrp, for example: twrp-3.2.2-0-pioneer.img, twrp-3.7.0_9-0 -pioneer.img, my Sony is on Android 9

Carljaynp03 said:
I have this problem, when installing twrp to my Sony Xperia XA2 (H3123), I am trying to install several versions of Twrp, for example: twrp-3.2.2-0-pioneer.img, twrp-3.7.0_9-0 -pioneer.img, my Sony is on Android 9
Click to expand...
Click to collapse

Did you unlock the bootloader ?

Carljaynp03 said:
View attachment 5734133
Click to expand...
Click to collapse
I agree with faraway, if i remember correctly when i had this issue i didn't unlock the bootloader.
I typed a specific number in the phone dial app and it said that the bootloader is unlocked, however there is another step you need to take that i had overlooked, you need a bootloader unlock code.
The code is free, not like with chinese spyware huawai they want your money for the code...
Unlock Bootloader - Open Devices - Sony Developer World
developer.sony.com
https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/how-to-unlock-bootloader/#tutorial-step-4
and use one of these commands in cmd/adb
fastboot flashing unlock
fastboot oem unlock

Carljaynp03 said:
View attachment 5734133
Click to expand...
Click to collapse
What is your end goal? To flash a custom ROM like LineageOS? Then you can temporarily flash a recovery image to the boot partition:
fastboot flash boot <recovery_filename>.img
You don't really need TWRP for this, just use the latest official LOS Recovery:
https://download.lineageos.org/pioneer
Also see: https://wiki.lineageos.org/devices/pioneer/install
Or do you want to "permanently" install TWRP on an existing system? Then you need to directly boot into TWRP and install it from its GUI:
fastboot boot <twrp_filename>.img
See: https://twrp.me/sony/sonyxperiaxa2.html
I haven't tried the latter on the XA2 yet though and don't know how permanent that installation really is. It maybe gone after an OTA update.

irgendwer2 said:
What is your end goal? To flash a custom ROM like LineageOS? Then you can temporarily flash a recovery image to the boot partition:
fastboot flash boot <recovery_filename>.img
You don't really need TWRP for this, just use the latest official LOS Recovery:
https://download.lineageos.org/pioneer
Also see: https://wiki.lineageos.org/devices/pioneer/install
Or do you want to "permanently" install TWRP on an existing system? Then you need to directly boot into TWRP and install it from its GUI:
fastboot boot <twrp_filename>.img
See: https://twrp.me/sony/sonyxperiaxa2.html
I haven't tried the latter on the XA2 yet though and don't know how permanent that installation really is. It maybe gone after an OTA update.
Click to expand...
Click to collapse
Booting a temprary image did not work when i tried it, most likely because the bootloader wasn't unlock.

Privacydroid said:
Booting a temprary image did not work when i tried it, most likely because the bootloader wasn't unlock.
Click to expand...
Click to collapse
Independent from the bootloader status: you can't flash an image directly to the recovery partition on the XA2/Pioneer (like he tried, see screenshot) because such a dedicated partition doesn't exist on this and other A/B devices. Instead the recovery is built into the boot image.
That's why you have to use fastboot flash boot instead of recovery.

irgendwer2 said:
Independent from the bootloader status: you can't flash an image directly to the recovery partition on the XA2/Pioneer (like he tried, see screenshot) because such a dedicated partition doesn't exist on this and other A/B devices. Instead the recovery is built into the boot image.
That's why you have to use fastboot flash boot instead of recovery.
Click to expand...
Click to collapse
follow the next steps you mentioned use: fastboot flash boot recovery from LineageOS, and my phone went into a constant boot shutdown and restart, then this message appeared

and the bootloader is open

Shutdown the phone after flashing the recovery image (it doesn't seem like you did that). Then hold Volume Down + Power to boot into recovery.

irgendwer2 said:
Independent from the bootloader status: you can't flash an image directly to the recovery partition on the XA2/Pioneer (like he tried, see screenshot) because such a dedicated partition doesn't exist on this and other A/B devices. Instead the recovery is built into the boot image.
That's why you have to use fastboot flash boot instead of recovery.
Click to expand...
Click to collapse
I get that the recovery is only for a temporary boot, when i tried it, it didn't work but i can't remember what the error was.