Related
How to Flash TWRP & Root Samsung Galaxy A10 series (Unlocked Exynos Only, A10s (A107F/M) not supported)
NOTICE :
Before you move further, make clear that rooting device -
- Your warranty will be void
- Some of functions may not work on rooted device, some function may get back with un rooting, some may never.
- All your data on device will be lost
- Flashing custom binaries may brick (Usually soft but can be hard brick too) your device, so follow it on your own risk!
If you are ready with condition, move further -
Click to expand...
Click to collapse
Before moving to root device, must read every single instruction given below as any small mistake can lead to fail to achieve root or may brick the device.
A. Unlocking Bootloader
This is a basic step to root device. Go to settings - about phone - Software Information - tap multiple times on "Build number" - This will open developer option.
Now in settings at the end, you will have new option "Developer options" - look for OEM unlocking - Enable it.
(PS : If you don't see this option then you may need to wait up to 7 days or more to appear or may be on some operator you will get it never. Without this option you can not root your device, sorry!).
How to get OEM Unlock option back?
1. Open the Settings app. Tap on General Management → Date and time.
2. Use the toggle button to disable Automatic date and time.
3. Set date option will be enabled now. Tap on it, and set the date to about 10-20 days earlier.
4. Enable developer options.
4.a Go to your device Settings.
4.b Select ‘About phone’ » tap seven times on ‘Build number’.
└ This will enable Developer options under Settings.
4.c Go back to Settings » scroll down to the bottom and you’ll see Developer options menu.
5. Open developer options (in the Settings app itself), and find the option called ‘Auto update system‘. Use the toggle button to disable it.
6. Now, go back to the main screen of Setting, and then tap on Software update.
7. Disable the option ‘Download updates automatically‘.
8. Tap on ‘Download updates manually‘ option, but it will give you an error because of the wrong date, so it’s fine.
9. Restart the device.
10. Go to Settings > Developer options. The OEM unlock option should be enabled now.
Once you have enable OEM unlock option, switch off your device and reboot to download mode.
To put device in download mode - Press Volume Up & then Press Volume Down (Keep holding both) and connect device to PC with USB cable
When device start to download mode, long press volume up to unlock the bootloader. This will wipe your data and automatically reboot
Now let finish setup and again enable developer options (as said above), and confirm that the OEM unlocking option exists and grayed out!
If it is not then you can not root device!
Once you see this option and greyed out, you are ready to flash custom binary and root your device.2. setup the phone by skipping the wizard.
B. Disabling Android Verified Boot
1. Reboot to DOWNLOAD mode.
2. Download Odin 3.14.4 or newer and make sure Samsung USB drivers are installed.
3. Open Odin and put the vbmeta_disabled.tar into USERDATA slot and click "Start"
4. Your device will reboot but it will not boot into system as vbmeta signature has changed.
5. Your device will reboot into RECOVERY mode automatically and prompt "You have to reset your device to factory settings". Use "Volume Up" or "Volume Down" button to move and "Power" button to select. Confirm and reset the device to factory settings.
6. This is the last time the data on the device has to be cleared. Afterwards, if you don't re-lock bootloader or re-enable the Android Verified Boot, you will not lose your data. Be aware, a stock firmware package contains a Android Verified Boot Metadata Image (vbmeta.img) with verifications enabled. You will need to flash the vbmeta_disable image (put into USERDATA slot) along with the stock firmware (use BL, AP, CP, CSC slots) to make sure AVB is not re-enabled and the data is preserved.
C. Flashing TWRP/Magisk
link
Important :
Due to the fact that some devices no longer uses ramdisk in boot images, Magisk has no choice but to be installed in the recovery partition. For these devices, you will have to boot to recovery every time if you want Magisk. Since both Magisk and recovery lives in the same partition, what you actually end up getting when you choose to boot to recovery will be determined by how long you press volume up.
(Powering up normally) → (System with NO Magisk)
(OEM Recovery Key Combo) → (Splash screen) → (Release all buttons) → (System with Magisk)
(OEM Recovery Key Combo) → (Splash screen) → (Keep pressing volume up) → (Actual recovery)
Thanks and credit
For more details read Installation guide by @topjohnwu from Here.
All credit and thanks go to @topjohnwu for magisk & guide.
@dr.ketan for this guide from Here
@jesec for rooting guide Here
@ianmacd for multidisabler from here
Me
reserved.
Hi
Thanks for putting out the details guide!
I followed the steps carefully but got stuck at step 12 - the device boots to download mode and says: "error verifying vbmeta image..."
Luckily I was able to flash it back to stock - but the magisk_patched.tar looks faulty (I copied it using adb) so no root for me
Any ideas?
dani3ltony said:
Hi
Thanks for putting out the details guide!
I followed the steps carefully but got stuck at step 12 - the device boots to download mode and says: "error verifying vbmeta image..."
Luckily I was able to flash it back to stock - but the magisk_patched.tar looks faulty (I copied it using adb) so no root for me
Any ideas?
Click to expand...
Click to collapse
Unplug USB and replug it then make sure the size of tar file almost the same as origin.
for step 6, can we transfer the file via SD card?
afaneh92 said:
Unplug USB and replug it then make sure the size of tar file almost the same as origin.
Click to expand...
Click to collapse
Hi
I triple did it, but no luck
s_ryan said:
for step 6, can we transfer the file via SD card?
Click to expand...
Click to collapse
Sure.
dani3ltony said:
Hi
I triple did it, but no luck
Click to expand...
Click to collapse
Flash AP file only for some reason the BL tar include vbmeta.img but you can patch it too.
I also hit the same problem that soft-brick my phone.. just to confirm, the AP.md5 file u said to use, its name is this? AP_A105GDXU2ASE3_CL15918313_QB23932289_REV00_user_low_ship_meta_OS9.tar
afaneh92 said:
Sure.
Flash AP file only for some reason the BL tar include vbmeta.img but you can patch it too.
Click to expand...
Click to collapse
s_ryan said:
I also hit the same problem that soft-brick my phone.. just to confirm, the AP.md5 file u said to use, its name is this? AP_A105GDXU2ASE3_CL15918313_QB23932289_REV00_user_low_ship_meta_OS9.tar
Click to expand...
Click to collapse
yes
will try to make patched tar for all bootloaders when I got some free time.
Guide updated with more details
Hey dude,
Thanks for the update, I have a problem with step 7
7) Open Magisk Manager - Magisk (first one) - Install - select to "Select and Patch file" - Navigate file you have copied to device (BL_[device_model_sw_ver].tar.md5).
I followed but magisk says No Boot image found, process error, installation failed
afaneh92 said:
Guide updated with more details
Click to expand...
Click to collapse
s_ryan said:
Hey dude,
Thanks for the update, I have a problem with step 7
7) Open Magisk Manager - Magisk (first one) - Install - select to "Select and Patch file" - Navigate file you have copied to device (BL_[device_model_sw_ver].tar.md5).
I followed but magisk says No Boot image found, process error, installation failed
Click to expand...
Click to collapse
My bad I didnt test this, the BL file contain vbmeta.img and need to be patched. Will try to find better solution.
You can flash stock BL file only then reboot again to bootloader and flash the rest files.
I see.. no worries.. I tried to flash the patched ap file with the stock bl, it soft brinked my phone the last time I did it.. anyway, I will wait for your workaround..
Appreciate your help!
s_ryan said:
I see.. no worries.. I tried to flash the patched ap file with the stock bl, it soft brinked my phone the last time I did it.. anyway, I will wait for your workaround..
Appreciate your help!
Click to expand...
Click to collapse
Can you replace vbmeta.img from patched AP with BL using 7zip.
remove md5 extension from BL file.
Guide updated and added flash TWRP instructions
afaneh92 said:
2.Download A10_multidisabler-*-1.41.zip from here and copy to Ext Storage (Because once you flash TWRP, Int storage will not be readable)
Click to expand...
Click to collapse
I think it would be helpful to users if there were a single multi-disabler for all Samsung devices. To that end, I've incorporated your changes for the A10 into my multidisabler and attached a test version to this posting.
Will you please test it? If it works for you, I'll issue a new release.
ianmacd said:
I think it would be helpful to users if there were a single multi-disabler for all Samsung devices. To that end, I've incorporated your changes for the A10 into my multidisabler and attached a test version to this posting.
Will you please test it? If it works for you, I'll issue a new release.
Click to expand...
Click to collapse
Thanks for the update, I was thinking to make pull request with changes. After make sure every thing is working as it should.
afaneh92 said:
Thanks for the update, I was thinking to make pull request with changes. After make sure every thing is working as it should.
Click to expand...
Click to collapse
Thanks. In your case, it's easier now if you just verify that the script I attached is working, since I've already integrated the changes you made in your clone.
Anyone who wants multidisabler support for a new device, however, can either send me a pull request against the latest code, or run the following script on a live, rooted device:
Code:
#!/bin/sh
getprop ro.boot.bootloader
echo --
ls -l /vendor/etc/init/pa_daemon*.rc /vendor/etc/fstab.exynos*
echo --
cat /vendor/etc/fstab.exynos*
echo --
su -c cat /init.rc
Hi dude..
I tried it.. unfortunately I still have problems.. here are some of the problems
1) my 7zip does not allow me to mod the BL files within the md5 extension, so I extracted them out and replaced the file manually then zip it to Tar.. (the VBmeta file is only 1kb) is that right?
2) after flashing via odin, I did a reboot, I encountered a VBMEta error, "Error verifying vbmeta image" Verification_disabled bit is (cant see it, block by the camera module)
In the end, i restored the firmware and got everything back.
s_ryan said:
Hi dude..
I tried it.. unfortunately I still have problems.. here are some of the problems
1) my 7zip does not allow me to mod the BL files within the md5 extension, so I extracted them out and replaced the file manually then zip it to Tar.. (the VBmeta file is only 1kb) is that right?
2) after flashing via odin, I did a reboot, I encountered a VBMEta error, "Error verifying vbmeta image" Verification_disabled bit is (cant see it, block by the camera module)
In the end, i restored the firmware and got everything back.
Click to expand...
Click to collapse
Try using this vbmeta.img (inside the tar file). It worked for me on the A20 with similar error. This file normally seems to be a checksum checker and if it doesn't match what the phone wants to see it gives you that error. But this file was modified to essentially be blank so there is nothing to give the phone an error.
Hi there.
I screwed up my MediaPad M5 Lite (Wifi edition: BAH2-W19, EMUI 8 installed. It's a treble compatible device) yesterday and need help.
I did the following steps before it all went down the gutter:
1. I successfully unlocked the bootloader using the DC Unlocker method
2. I downloaded the latest a-only AOSP release of "phhusson AOSP 9.0 v119": system-arm64-aonly-vanilla-nosu.img.xz (https://github.com/phhusson/treble_experimentations/releases)
3. I rebooted into bootloader and flashed the unzipped .img file to the device. The flash was successful as all 4 steps of copieing stuff tot he system partition said "OKAY"
4. now I used "fastboot reboot" and the trouble started. The tablet froze in fastboot mode. It just didn't restart.
5. I turned it of using a long push on the power button. Then it restarted and got stuck at the start screen. I'll attach a screenshot so you know what I am seeing.
6. From now on I was only able to boot into fastboot mode and into the stock recovery. There I did factory reset and cache formatting several times but with no effect.
7. Only thing that still worked was the eRecovery function in the EMUI stock recovery. With this I was able to download some official firmware from Huawei automatically and the tablet was back to stock
8. This night the OS did an auto update to v215.
9. So this morning I repeated the step 2. from above but with a different a-only custom rom and again it didn't work out
10. I tried to use the eRecovery function to get back to stock, but now the recovery is broken and throws an error "Getting package info failed".
I also tried to download older firmware from https://androidhost.ru/ and flash it with the dload method. Without success of course. While doing it I receive an error "Software install failed!". I will attach a screenshot.
Can anybody give me a hint what I could do next to approach the problem?
Best
rob
Well, you didn't had TWRP as recovery, so no nandroid backup available. From one of my experiences with flashing a stock rom for acer, I had to delete some lines of code from the meta inf folder relating the version of the phone, in order to successfully flash it. Maybe the stock ROM you are trying has some lines of code detecting if bootloader unlocked.
Im also having trouble getting a good tutorial for getting rid of the os or just to have magisk on the tablet
You dowoad latest rom and flash stock via hru and. Twrp search xda
unbrick Huawei MediaPad M5 Lite
r0b said:
Hi there.
I screwed up my MediaPad M5 Lite (Wifi edition: BAH2-W19, EMUI 8 installed. It's a treble compatible device) yesterday and need help.
I did the following steps before it all went down the gutter:
1. I successfully unlocked the bootloader using the DC Unlocker method
2. I downloaded the latest a-only AOSP release of "phhusson AOSP 9.0 v119": system-arm64-aonly-vanilla-nosu.img.xz (https://github.com/phhusson/treble_experimentations/releases)
3. I rebooted into bootloader and flashed the unzipped .img file to the device. The flash was successful as all 4 steps of copieing stuff tot he system partition said "OKAY"
4. now I used "fastboot reboot" and the trouble started. The tablet froze in fastboot mode. It just didn't restart.
5. I turned it of using a long push on the power button. Then it restarted and got stuck at the start screen. I'll attach a screenshot so you know what I am seeing.
6. From now on I was only able to boot into fastboot mode and into the stock recovery. There I did factory reset and cache formatting several times but with no effect.
7. Only thing that still worked was the eRecovery function in the EMUI stock recovery. With this I was able to download some official firmware from Huawei automatically and the tablet was back to stock
8. This night the OS did an auto update to v215.
9. So this morning I repeated the step 2. from above but with a different a-only custom rom and again it didn't work out
10. I tried to use the eRecovery function to get back to stock, but now the recovery is broken and throws an error "Getting package info failed".
I also tried to download older firmware from https://androidhost.ru/ and flash it with the dload method. Without success of course. While doing it I receive an error "Software install failed!". I will attach a screenshot.
Can anybody give me a hint what I could do next to approach the problem?
Best
rob
Click to expand...
Click to collapse
Unbrick using Huawei Multi tool .
---------- Post added at 03:14 PM ---------- Previous post was at 03:10 PM ----------
r0b said:
Hi there.
I screwed up my MediaPad M5 Lite (Wifi edition: BAH2-W19, EMUI 8 installed. It's a treble compatible device) yesterday and need help.
I did the following steps before it all went down the gutter:
1. I successfully unlocked the bootloader using the DC Unlocker method
2. I downloaded the latest a-only AOSP release of "phhusson AOSP 9.0 v119": system-arm64-aonly-vanilla-nosu.img.xz (https://github.com/phhusson/treble_experimentations/releases)
3. I rebooted into bootloader and flashed the unzipped .img file to the device. The flash was successful as all 4 steps of copieing stuff tot he system partition said "OKAY"
4. now I used "fastboot reboot" and the trouble started. The tablet froze in fastboot mode. It just didn't restart.
5. I turned it of using a long push on the power button. Then it restarted and got stuck at the start screen. I'll attach a screenshot so you know what I am seeing.
6. From now on I was only able to boot into fastboot mode and into the stock recovery. There I did factory reset and cache formatting several times but with no effect.
7. Only thing that still worked was the eRecovery function in the EMUI stock recovery. With this I was able to download some official firmware from Huawei automatically and the tablet was back to stock
8. This night the OS did an auto update to v215.
9. So this morning I repeated the step 2. from above but with a different a-only custom rom and again it didn't work out
10. I tried to use the eRecovery function to get back to stock, but now the recovery is broken and throws an error "Getting package info failed".
I also tried to download older firmware from https://androidhost.ru/ and flash it with the dload method. Without success of course. While doing it I receive an error "Software install failed!". I will attach a screenshot.
Can anybody give me a hint what could do next to approach the problem?
dnrob
Click to expand...
Click to collapse
You can install these roms only if you can downgrade to update v177 and lower
Like me you need to Unbrick your mediapad m5 lite
First place need to go back in Fastboot mode.
So UNPLUG , turn off , wait a second and turn on with volume Down , when screen blink release power button and keep volume down pressed a second until Fastboot mode
Or, try to boot in Fastboot with volume down + power AND USB plugged in goes into fastboot, or TWRP if you flashed TWRP to RECOVERY2 instead to RECOVERY.
If doesnt work try the same plug or unplug cuz we have Recovery_ramdisk , eRecovery and eRecovery2
WHEN its okay and you can turn on fastboot mode
Second prepair the img's for unbricking
The LEGIT methods its come back stock rom , then you'll be able to do what you want.
Download Huawei Multi-Tools , Huawei Update Extractor and update.zip of your stock ROM and update_data_full
Then use Huawei Update Extractor to extract
system.img ramdisk.img recovery_ramdisk.img From update.app\update.zip and
Cust.img from update.app\update_full_public.zip.
If you have backup of your userdata.img its the time to put all together in the same directory before go futher.
If all its good , you just need to click unbrick.
Maybe i'll soon do a guide for unbrick and prevent brick , and how install twrp without losing data or encryption data
helmuth said:
And just for the complete list:
Volume up + power AND USB plugged in goes into eRecovery (or TWRP, if you flashed TWRP to RECOVERY2 instead to RECOVERY)
Volume up and down + power and USB plugged in forces update via USB (indicated by a little USB-like icon in the recovery circle. The progess bar goes to 5% and waits for input from your PC)
Click to expand...
Click to collapse
RAMDISK238.img, Disable_Dm-Verity_ForceEncrypt_12.21.2019.zip and twrp8.img you will find at
android-hilfe.de->forum huawei-mediapad-m5-lite -> custom-roms-mediapad page-5
Theese custom roms should work:
Andy Yan's LineageOS 17 (Android 10) -> lineage-17.0-20191231-UNOFFICIAL-treble_arm_avN.img.xz
Pierre-Hugues Husson AOSP 10.0 v209 -> system-quack-arm64-aonly-vanilla.img.xz
Following this guide you will loose all your data so be sure to have a backup
This should work for a Mediapad M5 lite BAH2-W19OCEC432-238
Precondition: Unlocked Bootloader / OEM Unlocked / USB Debugging active
1. if you brick your device don`t blame me
2. check, if the version B238 is installed
3. back up your data
4. copy Disable_Dm-Verity_ForceEncrypt_12.21.2019.zip on SD card
Fastboot:
5. boot into Fastboot Mode.
6. flash TWRP -> fastboot flash recovery_ramdisk twrp8.img
7. fastboot reboot recovery (the first time booting should show up the twrp menu)
if the boot message "2. Press Volume up for 3 seconds" appears must do a Factory Reset in the Stock Recovery. After a reboot the TWRP menu shows up. In lineageos you can activate advanced reboot in developer settings to boot in TWRP menu by pressing recovery mode
TWRP:
8. Wipe -> Advanced Wipe -> select data + cache + dalvik-cache -> Swipe to wipe -> back to start menu
9. Install -> Select Storage -> select Mircro SD card -> OK -> select Disable_Dm-Verity_ForceEncrypt_12.21.2019.zip -> Swipe to confirm Flash
10. Reboot -> Bootloader (not System!!!)
Fastboot:
11. fastboot flash ramdisk RAMDISK238.img
12. fastboot flash system lineage-17.0-20191231-UNOFFICIAL-treble_arm64_avN.img
(or AOSP 10.0 v209)
13. fastboot reboot
LineageOS should start.
other custom roms could work as well.......
Edit:
There´s a new version of LineageOS available:
https:######sourceforge.net###projects###andyyan-gsi###files###lineage-17.x###lineage-17.1-20200111-UNOFFICIAL-treble_arm64_avN.img.xz###download
replace ### with /
It works well on my m5lite
It did not work on B239
I am trying now to get back to the stock rom.
I think the problem is with RAMDISK238.img :/
Do you know how to get one for 239?
Thanks !
BesterTrainer said:
RAMDISK238.img, Disable_Dm-Verity_ForceEncrypt_12.21.2019.zip and twrp8.img you will find at
android-hilfe.de->forum huawei-mediapad-m5-lite -> custom-roms-mediapad page-5
Theese custom roms should work:
Andy Yan's LineageOS 17 (Android 10) -> lineage-17.0-20191231-UNOFFICIAL-treble_arm_avN.img.xz
Pierre-Hugues Husson AOSP 10.0 v209 -> system-quack-arm64-aonly-vanilla.img.xz
Following this guide you will loose all your data so be sure to have a backup
This should work for a Mediapad M5 lite BAH2-W19OCEC432-238
Precondition: Unlocked Bootloader / OEM Unlocked / USB Debugging active
1. if you brick your device don`t blame me
2. check, if the version B238 is installed
3. back up your data
4. copy Disable_Dm-Verity_ForceEncrypt_12.21.2019.zip on SD card
Fastboot:
5. boot into Fastboot Mode.
6. flash TWRP -> fastboot flash recovery_ramdisk twrp8.img
7. fastboot reboot recovery (the first time booting should show up the twrp menu)
if the boot message "2. Press Volume up for 3 seconds" appears must do a Factory Reset in the Stock Recovery. After a reboot the TWRP menu shows up. In lineageos you can activate advanced reboot in developer settings to boot in TWRP menu by pressing recovery mode
TWRP:
8. Wipe -> Advanced Wipe -> select data + cache + dalvik-cache -> Swipe to wipe -> back to start menu
9. Install -> Select Storage -> select Mircro SD card -> OK -> select Disable_Dm-Verity_ForceEncrypt_12.21.2019.zip -> Swipe to confirm Flash
10. Reboot -> Bootloader (not System!!!)
Fastboot:
11. fastboot flash ramdisk RAMDISK238.img
12. fastboot flash system lineage-17.0-20191231-UNOFFICIAL-treble_arm64_avN.img
(or AOSP 10.0 v209)
13. fastboot reboot
LineageOS should start.
other custom roms could work as well.......
Edit:
There´s a new version of LineageOS available:
https:######sourceforge.net###projects###andyyan-gsi###files###lineage-17.x###lineage-17.1-20200111-UNOFFICIAL-treble_arm64_avN.img.xz###download
replace ### with /
It works well on my m5lite
Click to expand...
Click to collapse
sasuke988 said:
It did not work on B239
I am trying now to get back to the stock rom.
I think the problem is with RAMDISK238.img :/
Do you know how to get one for 239?
Thanks !
Click to expand...
Click to collapse
https://
pro-teammt.ru/
en/
online-firmware-database/
?firmware_model=BAH2-W19&firmware_page=0
Check out your model (C432C431/...)
Use the huawei extractor to extract the images
Can someone check if this is legit? https://romprovider.com/2019/09/9-1-0-151-b151-firmware-jordan2-l09b/amp/
Raresh T said:
Can someone check if this is legit? https://romprovider.com/2019/09/9-1-0-151-b151-firmware-jordan2-l09b/amp/
Click to expand...
Click to collapse
It's for the 8" screen variant. It won't work on our 10.1"
is there any current custom house for this model because no links work. And on the stock, I have a problem with 5ghz Wi-Fi
You'd better install TWRP,flash FBE-disabler and format data partition
Anyway,firmware can be found at professorjtj.github.io and I recommend you rebrand and update it to EMUI9 to get better treble compatibility
SkipM4 said:
You'd better install TWRP,flash FBE-disabler and format data partition
Anyway,firmware can be found at professorjtj.github.io and I recommend you rebrand and update it to EMUI9 to get better treble compatibility
Click to expand...
Click to collapse
thats an interesting suggestion. could you post some guides on how could someone rebrand their device ?
Hi everybody,
I'm stuck in a pretty damn mess here. I have an Galaxy S20+ G985F device which is stuck in Download Mode with no ROM installed, a locked bootloader, and a changed recovery and vbmeta (one that came with a working TWRP image) image flashed. :/
Is thee any way to get out of this situation of which I don't know how exactly the phone got there? Seems like a mistakenly locked boot loader by long pressing the Vol Up button once in the Booloader Lock/Unlock menu.
When trying to flash with heimall the phone says, ie.:
Custom Binary (VBMETA) Blocked By OEM Lock
Any chance on recovering the device? There should actually no ROM be installed at the moment. Cannot boot anything, the device always goes into Download mode only showing an entry for "Vol Down + Side Key for 7 seconds: Cancel (restart phone)" which results in the device going to the screen again...
Flashing with "odin4" on Linux says:
odin4 -b BL_G985FXXU1ATD3_CL18335124_QB30559577_REV01_user_low_ship_MULTI_CERT.tar.md5 -a AP_G985FXXU1ATD3_CL18335124_QB30559577_REV01_user_low_ship_MULTI_CERT_meta_OS10.tar.md5 -c CP_G985FXXU1ATCT_CP15511927_CL18335124_QB30141694_REV01_user_low_ship_MULTI_CERT.tar.md5 -s CSC_OMC_OXM_G985FOXM1ATD3_CL18335124_QB30559577_REV01_user_low_ship_MULTI_CERT.tar.md5
Check file : BL_G985FXXU1ATD3_CL18335124_QB30559577_REV01_user_low_ship_MULTI_CERT.tar.md5
Check file : AP_G985FXXU1ATD3_CL18335124_QB30559577_REV01_user_low_ship_MULTI_CERT_meta_OS10.tar.md5
Check file : CP_G985FXXU1ATCT_CP15511927_CL18335124_QB30141694_REV01_user_low_ship_MULTI_CERT.tar.md5
Check file : CSC_OMC_OXM_G985FOXM1ATD3_CL18335124_QB30559577_REV01_user_low_ship_MULTI_CERT.tar.md5
/dev/bus/usb/001/054
/dev/bus/usb/001/054
Setup Connection
Set Partition
Receive PIT Info
success getpit
Upload Binaries
Binary arrange fail. Binary is invalid
Fail uploadBinaries
Kind regards and thanks for any help,
Marc
try with samsung smart switch with emergency software recovery
kosique said:
Hi everybody,
I'm stuck in a pretty damn mess here. I have an Galaxy S20+ G985F device which is stuck in Download Mode with no ROM installed, a locked bootloader, and a changed recovery and vbmeta (one that came with a working TWRP image) image flashed. :/
Is thee any way to get out of this situation of which I don't know how exactly the phone got there? Seems like a mistakenly locked boot loader by long pressing the Vol Up button once in the Booloader Lock/Unlock menu.
When trying to flash with heimall the phone says, ie.:
Custom Binary (VBMETA) Blocked By OEM Lock
Any chance on recovering the device? There should actually no ROM be installed at the moment. Cannot boot anything, the device always goes into Download mode only showing an entry for "Vol Down + Side Key for 7 seconds: Cancel (restart phone)" which results in the device going to the screen again...
Flashing with "odin4" on Linux says:
odin4 -b BL_G985FXXU1ATD3_CL18335124_QB30559577_REV01_user_low_ship_MULTI_CERT.tar.md5 -a AP_G985FXXU1ATD3_CL18335124_QB30559577_REV01_user_low_ship_MULTI_CERT_meta_OS10.tar.md5 -c CP_G985FXXU1ATCT_CP15511927_CL18335124_QB30141694_REV01_user_low_ship_MULTI_CERT.tar.md5 -s CSC_OMC_OXM_G985FOXM1ATD3_CL18335124_QB30559577_REV01_user_low_ship_MULTI_CERT.tar.md5
Check file : BL_G985FXXU1ATD3_CL18335124_QB30559577_REV01_user_low_ship_MULTI_CERT.tar.md5
Check file : AP_G985FXXU1ATD3_CL18335124_QB30559577_REV01_user_low_ship_MULTI_CERT_meta_OS10.tar.md5
Check file : CP_G985FXXU1ATCT_CP15511927_CL18335124_QB30141694_REV01_user_low_ship_MULTI_CERT.tar.md5
Check file : CSC_OMC_OXM_G985FOXM1ATD3_CL18335124_QB30559577_REV01_user_low_ship_MULTI_CERT.tar.md5
/dev/bus/usb/001/054
/dev/bus/usb/001/054
Setup Connection
Set Partition
Receive PIT Info
success getpit
Upload Binaries
Binary arrange fail. Binary is invalid
Fail uploadBinaries
Kind regards and thanks for any help,
Marc
Click to expand...
Click to collapse
And also you cannot turn off your phone? )
Prepare a recovery tar file with vbmeta and recovery in it. Flash with odin and reboot. Then disable encription.
Then redo the initial process of flashing tar file with or without the rest of the rom files.
If ur alao flashing rom files put your recovery tar file to others section in odin.
DISCLAIMERS:
This help is specific for MERLIN devices only !
(Xiaomi Redmi Note 9 and Xiaomi Redmi 10X 4G)
Keep atention. This is an UNOFFICIAL thread.
This thread was based on the thread by Agent_fabulous. Thank you very much !
DON'T ask by PM. If you have any question, reply to this thread.
Keep in mind, nothing is 100% perfect, so you need to read careful
and keep trying before to ask an already answered question.
Keep your backup files safe and secure ! If you can, encrypt them.
If you try to flash in "firmware upgrade" mode, bootloader will be LOCKED again !
Never try to flash in "format all" mode ! Otherwise, you will LOSE all secure and identifying infos for your device. Like IMEI and MAC.
Never try to share your backups or your security and privacy will be compromised.
USE AT YOUR OWN RISK. I AM NOT RESPONSIBLE FOR YOUR ACTIONS.
Sorry for my bad english.
GOOD LUCK
1. Where can I find official and untouched STOCK FIRMWARES ROMS?Here, you can find latest releases: https://xiaomifirmwareupdater.com/miui/merlin/Here, you can find archive of releases: https://xiaomifirmwareupdater.com/archive/miui/merlin/
2. Where can I find some useful tools?Xiaomitool: https://www.xiaomitool.com/V2/Miflashpro: https://miflashpro.com/Miflashtool: https://xiaomiflashtool.com/Sp Flash Tool: https://spflashtools.com/category/windowsMi PC Suite: http://pcsuite.mi.com/
3. There are useful tools for LINUX or Mac OS?Xiaomitool (Linux & MacOS): https://www.xiaomitool.com/V2/Sp Flash Tool (Linux): https://spflashtools.com/category/linux
4. My pc can't detect my phone. What to do?Probably, you need to install appropriate usb drivers.Try this: https://androidmtk.com/download-mtk-usb-all-drivers
5. Where can I find custom ROMs?Here, you can find the collection of custom ROMs for MERLIN: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4291423/
6. How can I root?First and obviously, you need to unlock your bootloader. Once you unlock your bootloader, you can root your device flashing magisk patched boot.img.Here, you can find magisk patched boot images: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/KEEP ATENTION: you need to disable verification for vbmeta too.Here, you can find patched vbmeta with disabled verification: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218909/
7. Where can I find TWRP & PBRP?There is only ONE recovery project with open source for MERLIN.But, there are other twrp and pbrp with closed source.If you use it, you can cause damages to your device, use at your own risk and DON'T ask about it.KEEP ATENTION: you need to IGNORE misc partition, if you flash the misc partition, your phone can be stucked in boot loop.Here, you can find recovery projects images: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4227751/KEEP ATENTION: you need to disable verification for vbmeta too.Here, you can find patched vbmeta with disabled verification: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218909/
8. How can I restore the state of UNLOCKED BOOTLOADER?You need to restore your backup of SECCFG partition.Please, read this: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4220013/
9. How to make TWRP V11.0.4.0 work on MIUI V12.0.5.0 or higher?If you are using MIUI V12.0.5.0 or higher, TWRP V11.0.4.0 will not work.Please, read this: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4223077/You will need to flash an older LK partition.Here, you can find lk images: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218925/
10. How can I disable TWRP?You will need to flash original stock recovery.img.Here, you can find original stock recovery images: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
11. How to flash using SP FLASH TOOL without EDL and authentication?If you want to use flash tool on MIUI V12.0.5.0 or higher, it will requires EDL and authentication.Please, read this: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4223089/
12. I am on MIUI V12.0.5.0 or higher, how can I flash using SP FLASH TOOL without EDL and authentication?You will need to flash an older PRELOADER binary.Here, you can find preloader binaries: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218929/
13. I am on MIUI V12.0.4.0 or lower, how can I flash using SP FLASH TOOL without EDL and authentication?You will need the specific DA (download-agent) file for it without authentication (#NoAuth #NoAuthentication #No-Auth #No-Authentication).Please, read this: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209765/
14. How can I downgrade MIUI version?For downgrading your miui, you need unlocked bootloader.After unlocked bootloader, you can flash older firmware rom using fastboot or sp flash tool.
15. My phone is booting to a black screen after flashed misc partition together twrp. What to do?If your phone is booting to a black screen, you need to erase MISC partition.Please, read this: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
16. My phone got bootlop after installed a Magisk module or Xposed module. How can I disable it?You will need to uninstall the module. You have two methods for this.For first method, you can disable Magisk (read question 17).For second method, you need to boot in emergency mode (rescue mode).For booting in emergency mode, you need to press Vol+ (volume up) after boot starts. (YES, I mean AFTER you see boot logo.)And then, you can uninstall the module.
17. My phone got bootlop after flashed Magisk. How can I disable it?You will need to flash original stock boot.img.Here, you can find original stock boot images: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
18. My phone got bootloop, I am on MIUI V12.0.4.0 or lower and I can't enter in fastboot mode or recovery mode. What to do?You need to flash stock rom using sp flash tool.Please, read question 13.
19. My phone got bootloop, I am on MIUI V12.0.5.0 or higher and I can't enter in fastboot mode or recovery mode. What to do?For this, you will need to bypass authentication and flash in EDL mode with NO auth for FREE.Here, you can find the guide for bypassing EDL authenticated mode for FREE: https://forum.xda-developers.com/t/...d-flash-in-edl-with-no-auth-for-free.4229683/For this, you will need an authorized account for flashing in EDL mode.You need to go the service centre for professional assistance.Please, read this: https://www.xda-developers.com/xiaomi-edl-unbrick-authorized-mi-accounts/
20. There is any other way for flashing or unbricking?Yes. You can try any useful tool (read question 2 and 3).But, this help is not for how use them.You can find a huge amount of videos in youtube about it.
21. I want to keep with original stock boot.img together TWRP, but TWRP is removed at every reboot. What to do?You will need to flash patched boot image without overwrite of recovery.Please, read this: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209263/KEEP ATENTION: you need to disable verification for vbmeta too.Here, you can find patched vbmeta with disabled verification: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218909/
22. Where can I find scatter files to flash using flash tool?Here, you can find scatter files: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4223097/
23. Where can I find readback file to backup using flash tool?Here, you can find read back file: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4223109/
24. How can I know what is working on my phone before installing?If you want to know what is working for MERLIN, read this: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204873/
25. How can I disable preinstalled apps without uninstalling them?You need to perform this in command line:pm disable-user --user 0 com.android.chrome(Change com.android.chrome to desired package name to disable.)
26. Where can I find source code of the kernel?Here, you can find the OFFICIAL source code of the kernel: https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/merlin-r-oss and https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/lancelot-q-ossHere, you can find the OFFICIAL source code of the kernel modules: https://github.com/MiCode/MTK_kernel_modules/tree/merlin-r-oss and https://github.com/MiCode/MTK_kernel_modules/tree/lancelot-q-oss
27. Where can I find device tree and other sources codes of MT6768?-> https://github.com/Jebaitedneko/omni_device_xiaomi_merlin-> https://github.com/Redmi-MT6768/android_device_xiaomi_merlin-> https://github.com/Redmi-MT6768/android_kernel_xiaomi_mt6768-> https://github.com/Redmi-MT6768/android_vendor_xiaomi_merlin-> https://github.com/AndroidBlobs/device_xiaomi_merlin-> https://github.com/AndroidBlobs/vendor_xiaomi_merlin-> https://github.com/SparXFusion/android_device_xiaomi_merlin-> https://github.com/SparXFusion/android_kernel_redmi_mt6768-> https://github.com/JamieHoSzeYui/android_device_xiaomi_merlin-> https://github.com/surblazer/android_device_xiaomi_merlin-> https://github.com/surblazer/android_kernel_xiaomi_mt6768-> https://github.com/ZyCromerZ/android_kernel_xiaomi_mt6768-> https://github.com/Box-boi/android_kernel_xiaomi_mt6768-> https://github.com/Box-boi/omni_device_xiaomi_merlin-> https://github.com/Box-boi/android_device_xiaomi_merlin-> https://github.com/Box-boi/android_vendor_xiaomi_merlin-> https://sourceforge.net/projects/zyc-kernels/files/Merlin
28. How to pass SafetyNet?You will need to have Xposed installed. After it, everything you need to do is install HiddenCore-Module, active it on Xposed Manager and reboot.Here, you can find the HiddenCore-Module: https://repo.xposed.info/module/com.cofface.ivaderKEEP ATENTION: it is making android to keep on activity forever and never suspends screen.You can use the patched apk by Evengard: https://forum.xda-developers.com/t/hiddencore-module-what-was-it-doing.3903984/post-81982121.
29. How to disable ads (advertising)?You will need to have Xposed installed. After it, everything you need to do is install AdBlocker-Reborn, active it on Xposed Manager and reboot.Here, you can find the AdBlocker-Reborn: https://repo.xposed.info/module/com.aviraxp.adblocker.continuedKEEP ATENTION: some people said it can get troubles to google apps.
30. How to restore IMEI, Baseband, MAC, fix NVRAM WARNING and fix NVDATA CORRUPTED?KEEP ATENTION: never try to restore partitions from a different device, or you can brick and cause damages to your device.Here, you can find the guide: https://forum.xda-developers.com/t/...-on-merlin-redmi-note-9-redmi-10x-4g.4230423/
31. How to disable ads (advertising) without xposed?For unrooted devices, you need to perform this in command line:pm disable-user --user 0 com.miui.msa.globalFor rooted devices, you need to debloat your system and then remove the "MSA" app.
32. What should I backup before trying to customize my device?Here, you can find the list of what partitions you need to backup for avoiding mistakes without risking all of your device's identification details, like IMEI, WiFi MAC, Bluetooth MAC, calibration data, NVDATA, NVRAM, RADIO/MODEM/BASEBAND and others: https://forum.xda-developers.com/t/...lin-device-redmi-note-9-redmi-10x-4g.4229629/
33. How to bypass authentication and flash in EDL with NO auth for FREE?Here, you can find the guide for bypassing EDL authenticated mode for FREE: https://forum.xda-developers.com/t/...d-flash-in-edl-with-no-auth-for-free.4229683/
34. How to install XPOSED?1. You need to unlock your bootloader.2. You need to root using Magisk.3. You need to install magisk manager.4. You need to install the magisk module: RIRU. (Only Riru in the name).5. You need to choose between EDXPOSED or LSPOSED and then install the magisk module: "Riru Edxposed" or "Riru Lsposed".6. You need to install the properly manager: "Edxposed Manager" or "Lsposed Manager".7. Reboot.Done. Enjoy !
35. How to remove and clear GOOGLE ACC and Mi ACC / MiCloud?Here, you can find the guide for removing google account and xiaomi account: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4233977/
36. How can I flash a CUSTOM ROM?Here, you can find the guide for flashing custom roms by c.whoopee: https://forum.xda-developers.com/t/...rom-on-a-redmi-note-9-global-variant.4234151/(Thanks to c.whoopee)Here, you can find the guide for installing a Lineage 17.1 ROM by ma259: https://forum.xda-developers.com/t/...eage-17-1-rom-in-redmi-note-9-merlin.4235003/(Thanks to ma259)
37. How to properly use the SP Flash Tool?Here, you can find the guide how to configure correctly the SPFlashTool: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4229937/Here, you can find common errors of the SPFlashTool: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4238161/
38. How to solve "LIB DA not match" error?Please, follow the guide "How to properly solve the errors of the SP FLASH TOOL": https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4238161/
39. How to solve "PMT changed for the ROM" error?Please, follow the guide "How to properly solve the errors of the SP FLASH TOOL": https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4238161/
40. How to solve "STATUS_BROM_CMD_STARTCMD_FAIL" error?Please, follow the guide "How to properly solve the errors of the SP FLASH TOOL": https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4238161/
41. How to solve "STATUS_SEC_AUTH_FILE_NEEDED" error?Please, follow the guide "How to properly solve the errors of the SP FLASH TOOL": https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4238161/
42. How to solve "STATUS_BROM_CMD_FAIL" error?Please, follow the guide "How to properly solve the errors of the SP FLASH TOOL": https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4238161/
43. How to solve "STATUS_BROM_CMD_SEND_DA_FAIL" error?Please, follow the guide "How to properly solve the errors of the SP FLASH TOOL": https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4238161/44. Where can I find official ENGINEERING ROMs?Here, you can find ENGINEERING ROM V1: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4227933/Here, you can find ENGINEERING ROM V2: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4246891/
45. Where can I find extracted FIRMWARES?Here, you can find the thread of the EXTRACTED FIRMWARE by yshalsager: https://forum.xda-developers.com/t/...-4g-redmi-note-9-merlin-auto-updated.4250261/Here, you can find latest releases: https://xiaomifirmwareupdater.com/firmware/merlin/Here, you can find archive of releases: https://xiaomifirmwareupdater.com/archive/firmware/merlin/
46. Where can I find extracted VENDORS?Here, you can find latest releases: https://xiaomifirmwareupdater.com/vendor/merlin/Here, you can find archive of releases: https://xiaomifirmwareupdater.com/archive/vendor/merlin/
47. How can I mount system RW (read-write) ?Here, you can find the guide and the script by lebigmac for mounting system as read-write (RW): https://forum.xda-developers.com/t/...unt-system-read-write-super-no_super.4247311/
48. How to write and recover the IMEI for SLOT 1 and SLOT 2?Here, we are discussing about the possibilities of how to recover the IMEI for SLOT1 and SLOT2: https://forum.xda-developers.com/t/...-in-merlin-redmi-note-9-redmi-10x-4g.4258779/Here, you can find md1img images of the baseband/modem/radio: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4258919/49. Where can I find custom KERNEL?-> https://sourceforge.net/projects/zyc-kernels/files/Merlin/-> https://github.com/JamieHoSzeYui/dream/releases-> MOD EDIT: Link Removed50. How to skip & avoid EDL auth bypass and FLASH in DOWNLOAD MODE?Here, you can find the guide: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4322631/
Full List of My Own Threads:
[V12.5.2.0][Android 11.0] New Update: Download Files for Merlin V12.5.2.0.RJOMIXM
https://forum.xda-developers.com/t/...-0-rjomixm-redmi-note-9-redmi-10x-4g.4357045/
[V12.5.1.0][Android 11.0] New Update: Download Files for Merlin V12.5.1.0.RJOMIXM
https://forum.xda-developers.com/t/...-0-rjomixm-redmi-note-9-redmi-10x-4g.4321093/
[V12.0.1.0][Android 11.0] New Update: Download Files for Merlin V12.0.1.0.RJOMIXM
https://forum.xda-developers.com/t/...-0-rjomixm-redmi-note-9-redmi-10x-4g.4295435/
[V12.0.8.0] New Update: Download Files for Merlin V12.0.8.0.QJOMIXM
https://forum.xda-developers.com/t/...-0-qjomixm-redmi-note-9-redmi-10x-4g.4285863/
[V12.0.7.0] New Update: Download Files for Merlin V12.0.7.0.QJOMIXM
https://forum.xda-developers.com/t/...-0-qjomixm-redmi-note-9-redmi-10x-4g.4245351/
[BOOT][PATCHED] Boot Image Partition without OVERWRITE OF RECOVERY for MERLIN
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209263/
[DA][FLASH] DA files for flashing to MERLIN using FLASH TOOL
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209765/
[V1][ENGINEERING][ROM] OFFICIAL Egineering Firmware for MERLIN
https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4227933/
[V2][ENGINEERING][ROM] OFFICIAL Egineering Firmware for MERLIN
https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4246891/
[FAQ][GUIDE][HELP] Assistance Solution Centre for MERLIN
https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4225163/
[DISCUSSION][ROM][CUSTOM] What is the BEST CUSTOM ROM for MERLIN ?
https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4291423/
[GUIDE] How to bypass authentication and flash in EDL with NO auth for FREE
https://forum.xda-developers.com/t/...d-flash-in-edl-with-no-auth-for-free.4229683/
[GUIDE]How to properly solve the errors of the SP FLASH TOOL for MERLIN
https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4238161/
[GUIDE] How to properly use the SP FLASH TOOL for MERLIN ?
https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4229937/
[GUIDE] How to remove and clear GOOGLE ACC and Mi ACC / MiCloud for MERLIN
https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4233977/
[GUIDE] How to restore IMEI, Baseband, MAC, fix NVRAM WARNING and fix NVDATA CORRUPTED on MERLIN ?
https://forum.xda-developers.com/t/...-on-merlin-redmi-note-9-redmi-10x-4g.4230423/
[GUIDE] What should I backup before trying to customize my MERLIN device ?
https://forum.xda-developers.com/t/...lin-device-redmi-note-9-redmi-10x-4g.4229629/
[GUIDE][FLASH] How to keep flashing without AUTH or EDL on V12.0.5.0 or higher MIUI versions in MERLIN ?
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4223089/
[GUIDE][TWRP] How to keep TWRP V11.0.4.0 working on MIUI V12.0.5.0 or higher MIUI versions in MERLIN ?
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4223077/
[DISCUSSION] How to write and recover the IMEI for SLOT 1 and SLOT 2 in MERLIN ?
https://forum.xda-developers.com/t/...-in-merlin-redmi-note-9-redmi-10x-4g.4258779/
[GUIDE][UNBRICK] How unbrick your bootloop in MERLIN after flashing TWRP
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
[GUIDE][UNLOCK] How to restore the state of UNLOCKED BOOTLOADER in MERLIN
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4220013/
[LK][STOCK] LK Image Partition for MERLIN
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218925/
[BASEBAND][STOCK][MD1IMG] MODEM Image Partition for MERLIN
https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4258919/
[MAGISK][XPOSED] What is working for Magisk and Xposed in MERLIN ?
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204873/
[PRELOADER][STOCK] PRELOADER Partition Binary for MERLIN
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218929/
[READBACK][FLASH] Read Back file for backuping using flash tool from MERLIN
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4223109/
[SCATTER][FLASH] Scatter file for flashing using flash tool to MERLIN
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4223097/
[STOCK][PATCHED] Boot, Vbmeta and Recovery: Images Partitions for MERLIN
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
[RECOVERY PROJECT] Collection of TWRP & PBRP & SHRP & ORANGEFOX for MERLIN
https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4227751/
[VBMETA][PATCHED] VBMETA Image Partition: Disabled verity & Disabled verification for MERLIN
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218909/
[GUIDE] How to skip & avoid EDL auth bypass and FLASH in DOWNLOAD MODE for MERLIN
https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4322631/
TWRP does work above 12.0.5, I have tested.
New build: https://tdrive.elytra8.workers.dev/image-new.img
Flash like you flash any other custom recovery.
For ADS in MIUI, using debloat tool and removing MSA does the job.
Communos said:
TWRP does work above 12.0.5, I have tested.
New build: https://tdrive.elytra8.workers.dev/image-new.img
Flash like you flash any other custom recovery.
For ADS in MIUI, using debloat tool and removing MSA does the job.
Click to expand...
Click to collapse
Thank you very much.
Both were added on FAQ & GUIDE.
Here, you can find unofficial recovery project with closed source: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4227751/
Uhm... hello, newbie here and hopefully in the right thread.
I have a Redmi Note 9 and wanted to install LineageOS. What I have done so far:
Jumped through all the hoops to unlock the bootloader.
Since that erases all user data, I did not bother setting a password in the setup. Just went through it as quickly as possible.
Installed TWRP 12.0.6
Used that to install lineage-17.1-20210209-UNOFFICIAL-merlin.zip from here.
Result: The new system does not boot. I always end up in TWRP again. Even if I specifically go to Reboot -> System, it'll boot into recovery. I think the first boot fails and then it goes into recovery (if I power the device off and on again, it vibrates, the logo comes on, the screen goes black, it vibrates again, the logo shows again, and then I'm in TWRP).
What I have tried unsuccessfully:
Flashing the vbmeta from here.
Erasing the misc partition.
Flashing the old lk from here.
Closing the AVB2.0 after flash (with and without closing DM verity).
Wiping cache, dalvik, data, internal storage, and cache before reinstalling LOS.
Replacing TWRP with PBRP and trying again.
Probably some other things I don't remember. I've been chasing red herrings through this rabbit hole all day.
I also tried to install the ArrowOS build (from here), just to have one more datapoint. After that, the device boot-loops into the bootloader, and I have to manually go into recovery via VolUp+Power. This leads me to believe that it's not the LOS build at fault. It seems more likely that I am a moron and am doing something wrong. I just can't figure out what it is.
Any help would be appreciated.
MyBrainIsAStrainer said:
Uhm... hello, newbie here and hopefully in the right thread.
I have a Redmi Note 9 and wanted to install LineageOS. What I have done so far:
Jumped through all the hoops to unlock the bootloader.
Since that erases all user data, I did not bother setting a password in the setup. Just went through it as quickly as possible.
Installed TWRP 12.0.6
Used that to install lineage-17.1-20210209-UNOFFICIAL-merlin.zip from here.
Result: The new system does not boot. I always end up in TWRP again. Even if I specifically go to Reboot -> System, it'll boot into recovery. I think the first boot fails and then it goes into recovery (if I power the device off and on again, it vibrates, the logo comes on, the screen goes black, it vibrates again, the logo shows again, and then I'm in TWRP).
What I have tried unsuccessfully:
Flashing the vbmeta from here.
Erasing the misc partition.
Flashing the old lk from here.
Closing the AVB2.0 after flash (with and without closing DM verity).
Wiping cache, dalvik, data, internal storage, and cache before reinstalling LOS.
Replacing TWRP with PBRP and trying again.
Probably some other things I don't remember. I've been chasing red herrings through this rabbit hole all day.
I also tried to install the ArrowOS build (from here), just to have one more datapoint. After that, the device boot-loops into the bootloader, and I have to manually go into recovery via VolUp+Power. This leads me to believe that it's not the LOS build at fault. It seems more likely that I am a moron and am doing something wrong. I just can't figure out what it is.
Any help would be appreciated.
Click to expand...
Click to collapse
Hey, Custom roms for Redmi Note 9 need MIUI 12.0.1 Indonesia, or MIUI 12.0.3 global vendor.
Downgrade your phone to the specific MIUI vendor, and then try flashing custom rom.
Here's the link for global 12.0.3
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
And before you downgrade your miui version, please erase system and vendor to bypass anti roll back.
Use these commands after connecting device in fastboot mode:
fastboot reboot fastboot
fastboot erase system
fastboot erase vendor
fastboot reboot bootloader
Then flash the 12.0.3 global/12.0.1 Indonesia miui version through MiFlash.
Or
You could give flashing 12.0.1 Indonesia vendor in TWRP, and then flashing rom.
If after fastboot reboot fastboot it shows waiting for device, install this driver. https://drive.google.com/file/d/1JFYCZ3mu_Y_xpnS7QrmtwqOeFnWg6DO2/view?usp=sharing
Please note that you need to be on stock recovery for fastboot reboot fastboot to work.
Happy flashing
Thank you very much! With that info, I think I finally have it working!
I case it's helpful for future users, here are some issues I encountered along the way:
Communos said:
fastboot reboot fastboot
fastboot erase system
fastboot erase vendor
Click to expand...
Click to collapse
Code:
$ fastboot reboot fastboot
fastboot: usage: unknown reboot target fastboot
$ fastboot erase system
erasing 'system'...
FAILED (remote: Partition table doesn't exist)
finished. total time: 0.013s
$ fastboot erase vendor
erasing 'vendor'...
FAILED (remote: Partition table doesn't exist)
finished. total time: 0.012s
Is that normal? I do have a partition named 'super' that I can see in the TWRP backup module. Judging from its size, that could be the system partition. I think there's also a vbmeta_system and vbmeta_vendor, did you mean those?
Then flash the 12.0.3 global/12.0.1 Indonesia miui version through MiFlash.
Or
You could give flashing 12.0.1 Indonesia vendor in TWRP, and then flashing rom.
Click to expand...
Click to collapse
Ok, so I downloaded the full ROM for 12.0.3 global. I'm using Linux, so MiFlash won't work. But the ROM archive I downloaded contained a bunch of partition images and a shell script that would flash them using the fastboot command. I just ran that script. Windows users probably could have run the .bat file that was also included. There were no errors. And after a reboot, MIUI started to boot and presented me with the setup procedure.
I did not complete the setup (I suspect it would have just auto-updated MIUI to something that would have caused problems again) and used the power button to go into the bootloader.
From there, I flashed TWRP again (since it got overwritten by the script mentioned above), went into recovery mode, and tried to install LOS again. First, flashing seemed to hang. The last messages in the log were:
Code:
Installing file '/external_sd/Download/lineage-17.1-20210209-UNOFFICIAL-merlin.zip'
Checking for Digest file...
Target: Redmi/merlin_eea/merlin:10/QP1A.190711.020/V11.0.2.0.QJOEUXM:user/release-leys
And that was it. The border around the progress bar was doing it's busy animation thing and after waiting for 10 minutes, I used the power button to reset the device.
The second attempt went through fine, and now I have LineageOS running on the device. I still need to play around with it some more to see if there are any issues, but the flashing itself seems to have worked.
Again, thank you for your help!
MyBrainIsAStrainer said:
Thank you very much! With that info, I think I finally have it working!
I case it's helpful for future users, here are some issues I encountered along the way:
Code:
$ fastboot reboot fastboot
fastboot: usage: unknown reboot target fastboot
$ fastboot erase system
erasing 'system'...
FAILED (remote: Partition table doesn't exist)
finished. total time: 0.013s
$ fastboot erase vendor
erasing 'vendor'...
FAILED (remote: Partition table doesn't exist)
finished. total time: 0.012s
Is that normal? I do have a partition named 'super' that I can see in the TWRP backup module. Judging from its size, that could be the system partition. I think there's also a vbmeta_system and vbmeta_vendor, did you mean those?
Ok, so I downloaded the full ROM for 12.0.3 global. I'm using Linux, so MiFlash won't work. But the ROM archive I downloaded contained a bunch of partition images and a shell script that would flash them using the fastboot command. I just ran that script. Windows users probably could have run the .bat file that was also included. There were no errors. And after a reboot, MIUI started to boot and presented me with the setup procedure.
I did not complete the setup (I suspect it would have just auto-updated MIUI to something that would have caused problems again) and used the power button to go into the bootloader.
From there, I flashed TWRP again (since it got overwritten by the script mentioned above), went into recovery mode, and tried to install LOS again. First, flashing seemed to hang. The last messages in the log were:
Code:
Installing file '/external_sd/Download/lineage-17.1-20210209-UNOFFICIAL-merlin.zip'
Checking for Digest file...
Target: Redmi/merlin_eea/merlin:10/QP1A.190711.020/V11.0.2.0.QJOEUXM:user/release-leys
And that was it. The border around the progress bar was doing it's busy animation thing and after waiting for 10 minutes, I used the power button to reset the device.
The second attempt went through fine, and now I have LineageOS running on the device. I still need to play around with it some more to see if there are any issues, but the flashing itself seems to have worked.
Again, thank you for your help!
Click to expand...
Click to collapse
Oh you're using Linux, for Linux the commands is
/.fastboot reboot fastboot
Great to know you were able to flash successfuly. Note that first boot in all roms is a bootloop, you just have to force reboot after a minute of bootlogo showing up or so.
hi i flashed a wrong twrp and now the phone keeps bootlooping, cannot enter recovery or fastboot by power + vol (+ or -)
adb from computer doesn't detect
sp flash tool doesn't move when i hit "download" button
bootloader unlocked, root yes
pc notificates a device connection by sound
phone redmi note 9
thank you for the help really cannot figure it out
Kain105 said:
hi i flashed a wrong twrp and now the phone keeps bootlooping, cannot enter recovery or fastboot by power + vol (+ or -)
adb from computer doesn't detect
sp flash tool doesn't move when i hit "download" button
bootloader unlocked, root yes
pc notificates a device connection by sound
phone redmi note 9
thank you for the help really cannot figure it out
Click to expand...
Click to collapse
Apparentely, you need to flash in EDL mode.
So, you need to bypass the authentication in EDL mode first.
Read this: https://forum.xda-developers.com/t/...d-flash-in-edl-with-no-auth-for-free.4229683/
Newbie Android user here, hopefully i’m on the correct thread...i have a Redmi Note 9 with MIUI Global version 11.0.5 and Magisk version 20.4.
I tried updating Magisk to the latest version using the direct install option but I keep getting an error. I was told I need manually patch the boot.img and flash it but I need to create a magisk_patch.img first from the boot.img.
I read some of the guides on this thread but I’m not sure which one to follow. Also the steps to create the magisk_patch.image shows I need to click the Install button on Magisk then Select and Patch a file. I only have the Update button on Magisk, can I use that instead?
Or if you have other suggestion how to fix my issue. I attached the error I’m getting when I’m updating Magisk.
Thank you in advance for the assistance.
E77en12 said:
Newbie Android user here, hopefully i’m on the correct thread...i have a Redmi Note 9 with MIUI Global version 11.0.5 and Magisk version 20.4.
I tried updating Magisk to the latest version using the direct install option but I keep getting an error. I was told I need manually patch the boot.img and flash it but I need to create a magisk_patch.img first from the boot.img.
I read some of the guides on this thread but I’m not sure which one to follow. Also the steps to create the magisk_patch.image shows I need to click the Install button on Magisk then Select and Patch a file. I only have the Update button on Magisk, can I use that instead?
Or if you have other suggestion how to fix my issue. I attached the error I’m getting when I’m updating Magisk.
Thank you in advance for the assistance.
Click to expand...
Click to collapse
You can't install the magisk using the direct option.
You need to the patch the boot.img file and then flash the magisk_patched.img using fastboot (or spflashtool).
VD171 said:
You can't install the magisk using the direct option.
You need to the patch the boot.img file and then flash the magisk_patched.img using fastboot (or spflashtool).
Click to expand...
Click to collapse
Thank you, it worked. Now my magisk is updated
E77en12 said:
Thank you, it worked. Now my magisk is updated
Click to expand...
Click to collapse
Good work, my friend.
You are welcome
HELP PLS
i first flashed the patched_magisk.img then i got in a twrp boot loop. When i try to reboot into the system i get back to twrp menu.
Then i panicked and went to WIPE and factory reseted,
but it got stuck again. Then i powered it off.
How do i get out of this? I wanted to flash the stock boot.img but the storage folders has strange names
EDIT:
i figured it out what i have done. The data was ecrypted so i formated the data. But now i have another problem:
I installed linageOS from here, but when want to reboot back to system it says
No OS Installed! Are you sure you wish to reboot? i don't undertand why the custom rom didn't install.
I just copied the .zip file with the custom rom in the phone and hit install in TWRP. What did i do wrong?
George528 said:
HELP PLS
i first flashed the patched_magisk.img then i got in a twrp boot loop. When i try to reboot into the system i get back to twrp menu.
Then i panicked and went to WIPE and factory reseted,
but it got stuck again. Then i powered it off.
How do i get out of this? I wanted to flash the stock boot.img but the storage folders has strange names
View attachment 5289089
EDIT:
i figured it out what i have done. The data was ecrypted so i formated the data. But now i have another problem:
I installed linageOS from here, but when want to reboot back to system it says
No OS Installed! Are you sure you wish to reboot? i don't undertand why the custom rom didn't install.
I just copied the .zip file with the custom rom in the phone and hit install in TWRP. What did i do wrong?
Click to expand...
Click to collapse
Did you flash the patched vbmeta too?
VD171 said:
Did you flash the patched vbmeta too?
Click to expand...
Click to collapse
do you have a full step-by-step guide for this? i am feeling lost rn. I only have your FAQ but it doesnt cover everything
George528 said:
do you have a full step-by-step guide for this? i am feeling lost rn. I only have your FAQ but it doesnt cover everything
Click to expand...
Click to collapse
Steps for flashing vbmeta are same for every device.
You may try to use the search.
Here, you can find patched vbmeta for MERLIN:
[VBMETA][IMG][PATCHED] VBMETA Image Partition: Disabled verity & Disabled verification for MERLIN (Xiaomi Redmi Note 9 / Xiaomi Redmi 10X 4G)
PATCHED VBMETA.IMG for MERLIN by VD171 For what do I need it ? If you try to flash any custom partition, your device can bricks or gets in bootloop. This patch with disabled verity and disabled verification avoid it and need to be flashed once...
forum.xda-developers.com
VD171 said:
Steps for flashing vbmeta are same for every device.
You may try to use the search.
Here, you can find patched vbmeta for MERLIN:
[VBMETA][IMG][PATCHED] VBMETA Image Partition: Disabled verity & Disabled verification for MERLIN (Xiaomi Redmi Note 9 / Xiaomi Redmi 10X 4G)
PATCHED VBMETA.IMG for MERLIN by VD171 For what do I need it ? If you try to flash any custom partition, your device can bricks or gets in bootloop. This patch with disabled verity and disabled verification avoid it and need to be flashed once...
forum.xda-developers.com
Click to expand...
Click to collapse
no, i mean a full guide for rooting from the beggining to end, for redmi note 9. For example i missed the vbmeta and this resulted in an error. Now i have to flash the stock firmware and wait for another 7 days for it to unlock. For newbies like me, this looks like a mess. If you don't have one, can you please create one? Do it for us, newcomers. Thanks
I am not responsible for any damage to your device, when you root you lose the Warranty
This guide collects A107F development info, but with the files ported to the A107M.
Thanks to the Galaxy A10s Development team for the original files.
You need to be on Android 10, if you are on android 11, there are tutorials to downgrade.
[BootLoader Unlock]
- Backup all your media, this process will delete your internal media including music and photos
- Go to developer settings and enable [OEM Unlock]
- Reboot to download mode (Turn off, press VOL- & VOL+ and connect the USB)
- When prompted, press and hold VOL + to enter bootloader unlock mode
- Press VOL + to confirm you want to unlock bootloader, this will wipe your data
- If you think the bootloader is fully unlocked, it is actually not! Samsung introduced VaultKeeper, meaning the bootloader will still reject any unofficial partitions before VaultKeeper explicitly allows it.
- Go through the initial setup. Skip through all the steps since data will be wiped again later when we flash TWRP and magisk
- Enable developer options, and confirm that the OEM unlocking option exists and is grayed out. This means the VaultKeeper service has unleashed the bootloader. This step is MANDATORY
- Perfect! Your bootloader now accepts unofficial images in download mode.
[Twrp Install]
At this point, you will need to install Odin on your PC.
Bootloader unlocked is OBLIGATORY.
On your MicroSD, put the "A10s-encryption-disabler.zip" file.
Boot to download mode, load "VBMeta" file in AP and "TWRP Ported to A107M" file in BL
- Disable [Auto Reboot] in Odin
- Flash
- Force a reboot by pressing VOL+, VOL - and POWER buttons at the same time
- With the USB connected, and after the screen goes black, IMMEDIATELY let go of all buttons and IMMEDIATELY press and hold VOL+ and POWER button at the same time to boot to TWRP Recovery
NOTE: TWRP on this phone is not perfect, after booting to it, the screen will remain black after the Samsung logo disappears, simply wait 10 seconds and press the power button 2 times to have acces to it.
- After booting to TWRP successfully, go to WIPE in TWRP
- At the bottom, you should see an option to FORMAT DATA. After you select it, you will be asked to type "yes" in your keyboard. If you do not see this, you probably selected the wrong option.
- After formatting data, flash the "A10s-encryption-disabler.zip" with TWRP. This is done to avoid future bootloops.
- Optional, flash "Magisk.zip" if you want to keep on Stock ROM with root.
- After doing this, boot back to system and you are done
- Wait patiently for the device to boot for the first time
[Custom ROMs Install]
Bootloader unlocked and TWRP isntalled are OBLIGATORY.
Most of the GSI ROMs of this forum works fine on this device.
Only download a64 ROMs, do not confuse with ARM64.
On your MicroSD, put the ROM image.
- Boot to TWRP
- Go to Wipe > Advanced
- Wipe ONLY the System partition
- Go to Install
- At the bottom, select option "Install Image"
- Search for your GSI. It should be something that ends in .img. If it ends in .xz instead, you need to extract the image first
- Optional, if you want Root, flash the "Magisk.zip" file
- Go to recovery main menu
- Go to Reboot
- Reboot to Recovery
- After that, go to Wipe and perform a Factory Reset
- Reboot to System and enjoy!
[Downloads]
>Everything you will need<
I had a problem in Odin an "RQT-CLOSE" error occurred
Lukas203 said:
I had a problem in Odin an "RQT-CLOSE" error occurred
Click to expand...
Click to collapse
I GOT THE SAME THING WHATS HAPPENNING?
Worked perfectly on a107m with binary 6
Alexander_SlowD said:
Worked perfectly on a107m with binary 6
Click to expand...
Click to collapse
If it worked for you, what procedure did you follow? What rom did you use for bit 6? what tools did you use?
It worked for me at first time I see TWRP menu but I didnt followed the instructions correctly , I've tried to do it by myself after that , then I got a unnoficial bootloader error and RQT_CLOSE error when trying to do the Odin process again .
Any working solution are welcome and I will be thankfully , please !
Luciannus said:
It worked for me at first time I see TWRP menu but I didnt followed the instructions correctly , I've tried to do it by myself after that , then I got a unnoficial bootloader error and RQT_CLOSE error when trying to do the Odin process again .
Any working solution are welcome and I will be thankfully , please !
Click to expand...
Click to collapse
The TWRP is slready working for me , now I trying the Magisk part , I did this on Android 11 binary 6 trough A107MUBS6CWA3_ZTO firmware ...