Develop Bugs

[RECOVERY][MT6735] TWRP-3.0.2 for Lenovo Tab3 7 (TB3-730X)

Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired. Please
* do some research if you have any concerns about features included in this Recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
{
"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"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
[/CENTER]
Credits:
- TWRP Team
Device: Lenovo Tab3 7 Tablet - TB3-730X
Do not flash this on TB3-730F. The F model has different chipset and this recovery will softbrick it.
@sun_dream reported that 730F is working. So you can probably flash it, but be prepared with OFW, in case something goes wrong.
Instructions:
IMPORTANT: read all instructions at least once, before starting.
Note: If you're are a newbie, you can read more detailed instructions by honzazkrumlova here
- Download from link below.
- Enable "USB debugging" from developer options.
- Enable "OEM Unlocking" from developer options.
- Reboot device in Fastboot Mode (Bootloader mode), either with "adb reboot bootloader" or with VolDown+Power, to enter Recovery mode and then select "Reboot into bootloader"
- Unlock the bootloader with "fastboot flashing unlock" or "fastboot oem unlock" and follow the instructions on the tablet. (WARNING: This will erase all your data - Factory Reset)
- Once unlocked, you can use "fastboot boot TWRP_3.0.2_Lenovo_TB3-730X_Android-6.0_recovery.img" to start TWRP.
- When TWRP ask to modify system partition, answer "NO". Otherwise you will soft-brick your device and you will have to flash the original firmware and start from the beginning.
- If you want root - flash SuperSU, or as the user @Kellicros reported, you can flash Magisk 11.1.
- If you want XPosed, get it here.
- If you want to permanently flash the recovery, use "fastboot flash recovery TWRP_3.0.2_Lenovo_TB3-730X_Android-6.0_recovery.img".
- If you use it on any other Lenovo Tab3 7 device, please post the model.
- Thanks is always welcome.
Downloads:
TWRP_3.0.2_Lenovo_TB3-730X_Android-6.0_recovery.zip (well tested, consider it stable)
TWRP_3.1.1_Lenovo_TB3-730X_Android-6.0_recovery.zip
Unbrick your device:
Follow this thread

Hello
I have the same tablet (TB3-730X) and I tried this recovery, but something I did wrong.
Recovery by my works without problems, but now I can no longer boot into the system, I probably deleted it ...
After restarting the tablet always I return to Recovery and you can not flash the firmware because they can not find a version of the 730X (MTK MT8735P)
Can I use the firmware version for TB3-710 or 730F (MTK MT8161P)
Thanks for any advice, and thanks for Recovery.)

beldy said:
Hello
I have the same tablet (TB3-730X) and I tried this recovery, but something I did wrong.
Recovery by my works without problems, but now I can no longer boot into the system, I probably deleted it ...
After restarting the tablet always I return to Recovery and you can not flash the firmware because they can not find a version of the 730X (MTK MT8735P)
Can I use the firmware version for TB3-710 or 730F (MTK MT8161P)
Thanks for any advice, and thanks for Recovery.)
Click to expand...
Click to collapse
Hi.
When TWRP is started for the first time, it asks to modify the system partition.
I answered NO, NEVER. I saw some posts about other MTK devices and other people seems to have problems like yours when TWRP modify the system partition.
Is this your case?
If yes, then you need to download the original firmware and flash it on the device. After that you need to flash the recovery again.
I've downloaded the original firmware from Russian forum (this post: http://4pda.ru/forum/index.php?showtopic=731493&st=20#entry52434543). Here is direct link: https://cloud.mail.ru/public/Fjd9/u7e8mUbhq )
This is the last TB3-730X firmware. Do not try 710 firmwares, they should not work and it is probably dangerous to flash it. I dont know for 730F, this one could work, but anyway, download the the 730X firmware from the link above.
I guess you will need the SPFlash Tool to flash the firmware.
Hope this helps.

Thank you for the link ...
so probably it is my case that TWRP modify the system partition ... try this firmware and send the result ..
Thanks again for your help, I appreciate it.

I can confirm that Tab3 730x is checking if even TWRP is running (fastboot boot twrp.bin) and delete/modify system partition. TWRP not ask for modify system partition after first boot. Tablet stay on Lenovo logo forever. My firmware version is TB3-730X_S030_160509_ROW. Also in my model is not possible to read/write flash by FlashTool. I always get error 0x7D4, no matter what version I use, even after unlock bootloader. I have also try descibed firmware TB3-730X_S033_160707_ROW but this one cannot be flashed in fastboot mode. It says wrong binary (all files have in name _signed so probably different structure). It's seems that Polish Tab3 tb3-730X tablets are better protected than Russian.
0xAF can You post link to FlashTool what you used to flash your tablet?
[EDIT]
This time i get it working 0xAF are you mean first screen when TWRP start and there is swipe button? I Always swipe and this killed system partition I think. Btw do you both can flash this tablet with FlashTool?

DonKapselo said:
I can confirm that Tab3 730x is checking if even TWRP is running (fastboot boot twrp.bin) and delete/modify system partition. TWRP not ask for modify system partition after first boot. Tablet stay on Lenovo logo forever. My firmware version is TB3-730X_S030_160509_ROW. Also in my model is not possible to read/write flash by FlashTool. I always get error 0x7D4, no matter what version I use, even after unlock bootloader. I have also try descibed firmware TB3-730X_S033_160707_ROW but this one cannot be flashed in fastboot mode. It says wrong binary (all files have in name _signed so probably different structure). It's seems that Polish Tab3 tb3-730X tablets are better protected than Russian.
0xAF can You post link to FlashTool what you used to flash your tablet?
[EDIT]
This time i get it working 0xAF are you mean first screen when TWRP start and there is swipe button? I Always swipe and this killed system partition I think. Btw do you both can flash this tablet with FlashTool?
Click to expand...
Click to collapse
When you start the TWRP for the first time, it will ask to do something on system partition. I cannot remember if it was "Yes/No" answer, or a swipe. Just don't let TWRP touch the system partition.
After unlocking the bootloader with fastboot, you can flash the recovery with fastboot if you want, but first try to boot it, as described in the first post.
If you're going to flash the original firmware from the links above, then you will need SPFlash Tool, because the images (dumps) are made with SPFlash Tool and you cannot directly flash them with fastboot.
For bootloader unlocking, you can try this command: "fastboot oem unlock", while you're in the bootloader.
Did you enabled the "OEM Unlocking" from the "Developer Options" menu?
On my device, I was able to unlock it (after enabling "OEM Unlocking" option) with "fastboot flashing unlock".

"I have also try descibed firmware TB3-730X_S033_160707_ROW but this one cannot be flashed in fastboot mode. "
not to flash, always ends with an error 0x7D4 .....

beldy said:
"I have also try descibed firmware TB3-730X_S033_160707_ROW but this one cannot be flashed in fastboot mode. "
not to flash, always ends with an error 0x7D4 .....
Click to expand...
Click to collapse
Is your bootloader unlocked?
see the "fastboot" command manual, to check if it is unlocked.

0xAF said:
When you start the TWRP for the first time, it will ask to do something on system partition. I cannot remember if it was "Yes/No" answer, or a swipe. Just don't let TWRP touch the system partition.
After unlocking the bootloader with fastboot, you can flash the recovery with fastboot if you want, but first try to boot it, as described in the first post.
If you're going to flash the original firmware from the links above, then you will need SPFlash Tool, because the images (dumps) are made with SPFlash Tool and you cannot directly flash them with fastboot.
For bootloader unlocking, you can try this command: "fastboot oem unlock", while you're in the bootloader.
Did you enabled the "OEM Unlocking" from the "Developer Options" menu?
On my device, I was able to unlock it (after enabling "OEM Unlocking" option) with "fastboot flashing unlock".
Click to expand...
Click to collapse
Thanks. Now all working I just swipe button thinking that is locking button.
About flashing problem. I cannot flash with FlashTool because I have 0x7D4 error, same as beldy. I have try different cables, 3 computer, Windows 7, Windows 8 and Windows 10 - same.
I have unlocked bootloader with "fastboot oem unlock". Without it TWRP cannot be installer or booted. Before I enabled "OEM Unlocking" from the "Developer Options" menu. After it, phone format byself but still cannot flash.
I killed pcs one and send to service. Tablet cannot go into recovery. When it back I see some scratches on cover, like was opened. Maybe they used TestPoint to fix it.

DonKapselo said:
Thanks. Now all working I just swipe button thinking that is locking button.
About flashing problem. I cannot flash with FlashTool because I have 0x7D4 error, same as beldy. I have try different cables, 3 computer, Windows 7, Windows 8 and Windows 10 - same.
I have unlocked bootloader with "fastboot oem unlock". Without it TWRP cannot be installer or booted. Before I enabled "OEM Unlocking" from the "Developer Options" menu. After it, phone format byself but still cannot flash.
I killed pcs one and send to service. Tablet cannot go into recovery. When it back I see some scratches on cover, like was opened. Maybe they used TestPoint to fix it.
Click to expand...
Click to collapse
I'm glad you've solved the problem. I dont know what is 0x7D4 error. It could be some sort of extra locking of the device, but I doubt it. It's more likely to be something related to SPFlash Tools. It could be also a broken firmware, I haven't tried to flash the firmware from the links I've provided. I only used the Original Firmware to extract the original recovery from there. I needed the original kernel from the recovery to be able to start the TWRP.
A fast look in google gives this:
Error 0×7D4
Message: BROM ERROR: S_BROM_DOWNLOAD_DA_FAIL
Meaning: SP Flash tool encountered an error writing to the phone
Solution
* Try using a different USB cord, PC port and PC
* Use the latest version of SP flash tool
* Ensure the battery is well charged and the phone's USB port isn't faulty
Click to expand...
Click to collapse
But I guess it's not very helpful.

0xAF said:
I'm glad you've solved the problem. I dont know what is 0x7D4 error. It could be some sort of extra locking of the device, but I doubt it. It's more likely to be something related to SPFlash Tools. It could be also a broken firmware, I haven't tried to flash the firmware from the links I've provided. I only used the Original Firmware to extract the original recovery from there. I needed the original kernel from the recovery to be able to start the TWRP.
A fast look in google gives this:
But I guess it's not very helpful.
Click to expand...
Click to collapse
Just try to read flash, it's safe. I can bet You will get error 0x7D4 or 2004 (depend of version of flashtool). It's extra locked for sure. Btw. why You need original recovery to start TWRP? Maybe You mean that You need it to compile TWRP for this tablet model?

DonKapselo said:
Just try to read flash, it's safe. I can bet You will get error 0x7D4 or 2004 (depend of version of flashtool). It's extra locked for sure. Btw. why You need original recovery to start TWRP? Maybe You mean that You need it to compile TWRP for this tablet model?
Click to expand...
Click to collapse
The easiest way to port TWRP is to get it from another device with the same chipset and cpu. I did not wanted to prepare a toolchain/crosscompiler and start from the beginning to compile TWRP. So I took a TWRP from another tablet (DOOGEE_X6pro_Android6.0_20160707). Since it has a recent version of TWRP and is compiled for android 6.
Then all you need is to replace the kernel in this recovery, so we are booting with the kernel for our device. I needed the kernel from our original recovery for that. Then I've touched some files inside the recovery, fixed the fstab and default.prop and repackaged the recovery image.
This is the easiest way to port the recovery IMO. Took me 15-20 mins with all the testing.
This procedure work for any recovery, not only TWRP.
I guess, I could have dumped the original recovery from the device, but since I was looking for custom recovery for some time, I found the dump in the russian forum and downloaded it. So when I decided to port TWRP, I already had the recovery from the dump.

Thanks for info Any link to step by step how to replace kernet, what data change?

DonKapselo said:
Thanks for info Any link to step by step how to replace kernet, what data change?
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=hwMFBuCY-5k
I saw this video and decided to follow the steps.
You will need some intuition about the files you need to change inside the new recovery, as the video shows that only the fstab is needed, but you need more files, like default.prop and some other device dependent files from the original recovery (mostly in root folder).
In this recovery, I've used the default.prop from the original recovery.
As for the fstab, you will need to convert it by hand to a format understandable by TWRP. I've used the TWRP fstab file from the other device (from which I took the recovery in first place) and adopted it to our device. IIRC, almost nothing had to be changed.
I've copied some other device dependent files from the original recovery too.
Since I'm on linux, I've used these tools:
https://github.com/osm0sis/Android-Image-Kitchen.git
https://github.com/osm0sis/mkbootfs/
https://github.com/osm0sis/mkbootimg/
The tools are also available for windows (as the video shows) and for android itself (I believe the CF-SuperSU uses them on android to repack the boot.img).
These tools can repack recovery.img and boot.img.

Many thanks!

0xAF said:
Is your bootloader unlocked?
see the "fastboot" command manual, to check if it is unlocked.
Click to expand...
Click to collapse
yes bootloader is unlocked by command fastboot oem unlock...
It managed to someone already listed above to flash firmware in fastboot mode?
When you turn on the tablet remains lit Lenovo logo, and that's the end ...
Tablet can not even charged because, in the power cable connection tablet immediately turn on and loading TWRP or Lenovo logo screen
I am not progressed and I would appreciate if someone added original recovery or something what my tablet to function again
thx

beldy said:
yes bootloader is unlocked by command fastboot oem unlock...
It managed to someone already listed above to flash firmware in fastboot mode?
When you turn on the tablet remains lit Lenovo logo, and that's the end ...
Tablet can not even charged because, in the power cable connection tablet immediately turn on and loading TWRP or Lenovo logo screen
I am not progressed and I would appreciate if someone added original recovery or something what my tablet to function again
thx
Click to expand...
Click to collapse
Hi.
I'll make a dump of my system partition and post a link.
Unfortunately my system partition is not like in the original from the OTA ROM.
I've patched it with xposed and removed some ****ty apps from the OTA ROM.
Meanwhile if someone have OTA ROM, I would appreciate a link.
(you could try asking the Lenovo support for the OTA ROM).

0xAF said:
Hi.
I'll make a dump of my system partition and post a link.
Unfortunately my system partition is not like in the original from the OTA ROM.
I've patched it with xposed and removed some ****ty apps from the OTA ROM.
Meanwhile if someone have OTA ROM, I would appreciate a link.
(you could try asking the Lenovo support for the OTA ROM).
Click to expand...
Click to collapse
Thanks for the answer and advice to try anything that can help me
Thx
//EDIT: I add a few screens that I made an attempt to flash ... maybe you help someone ..

beldy said:
Thanks for the answer and advice to try anything that can help me
Thx
//EDIT: I add a few screens that I made an attempt to flash ... maybe you help someone ..
Click to expand...
Click to collapse
You should try to flash the dump with "fastboot flash system <file>"

Hello,
Got the Lenovo TAB3-730M.
What SuperSU.zip do I have to take to get "root"?
The "SR3-SuperSU-v2.78-SR3-20161103171345.zip" does not work.

Stuck in Bootloader Fastboot Mode

Dear All,
I was trying to install a customer ROM in my Asus Zenfone 5z. I was able to unlock the bootloader using official asus app. Then i managed to install a TWRP recovery. there was some partition issue so i flashed recovery in both partitions. the recovery worked fine and i managed to install the pixel rom. after that i wiped dalvik cach and some other items throgh recovery and restarted the phone.
After restart, it is stuck in bootloader. If i select start, recovery mode or power off, it gets rebooted and come back to bootloader again. Seems like a brick scenario.
So i tried the following:
1. Downloaded AFT tool and tried to flash the latest firmware version.. It gave a FPT error and then error on unable to load into recovery mode
2. Tried to run flashall_aft.cmd in directory containing latest firmware.. it said to internal/external command exists
3. Sideload using adb sideload command.. the error was could not read the file..
I am not sure what i can try next.. could you please help.. The details on bootloader screen are:
Fastboot mode
Product name _ ZS620KL
Bootloader version - WW_user_90.10.138.157
Secure Boot - yes
Active Slot A
Device State Unlocked

Help Required - Soft brick - Stuck in bootloader
Dear All, Would really appreciate if you can help me with this thread..
Thanks
Regards
Tarun
TG87 said:
Dear All,
I was trying to install a customer ROM in my Asus Zenfone 5z. I was able to unlock the bootloader using official asus app. Then i managed to install a TWRP recovery. there was some partition issue so i flashed recovery in both partitions. the recovery worked fine and i managed to install the pixel rom. after that i wiped dalvik cach and some other items throgh recovery and restarted the phone.
After restart, it is stuck in bootloader. If i select start, recovery mode or power off, it gets rebooted and come back to bootloader again. Seems like a brick scenario.
So i tried the following:
1. Downloaded AFT tool and tried to flash the latest firmware version.. It gave a FPT error and then error on unable to load into recovery mode
2. Tried to run flashall_aft.cmd in directory containing latest firmware.. it said to internal/external command exists
3. Sideload using adb sideload command.. the error was could not read the file..
I am not sure what i can try next.. could you please help.. The details on bootloader screen are:
Fastboot mode
Product name _ ZS620KL
Bootloader version - WW_user_90.10.138.157
Secure Boot - yes
Active Slot A
Device State Unlocked
Click to expand...
Click to collapse

Try to switch the slot to B and then boot

Download qfil,
Scrap fz*.mbn from CSC_8.02 and put to raw file of your interest. Ifu don't do so, it will throw error as that file is required and only available in CSC_eng_8.02 version. Never ever touch any other file in CSC 8.02 , it will make it impossible to run any fastboot and adb command and entering EDL is a bit tricky.
Extract the firmware, make sure to have system,vendor,userdata in root path as if u don't remove last few line of Python extraction code it will be deleted.
Go to TWRP Recovery, and reboot to EDL from there.
select all raw program XML and Patch xml and begin Image download.
Doesn't matter whether anything is accessible or not u get new image of ur choice.
If u get sahara error you are not immediately beginning download as ur phone enters into EDL.
Suggestion: Once u get back image sell the [email protected] quarter of cost as it's impossible to run the device in the way you want. The tools are not supported for open source development. The device is fragile, a little tweak and you lose IMEI,SN and soforth your phone network. This is not a device to temper, if u still do so, you will never come out from situation your stuck now.

amusing_ankesh said:
Download qfil,
Scrap fz*.mbn from CSC_8.02 and put to raw file of your interest. Ifu don't do so, it will throw error as that file is required and only available in CSC_eng_8.02 version. Never ever touch any other file in CSC 8.02 , it will make it impossible to run any fastboot and adb command and entering EDL is a bit tricky.
Extract the firmware, make sure to have system,vendor,userdata in root path as if u don't remove last few line of Python extraction code it will be deleted.
Go to TWRP Recovery, and reboot to EDL from there.
select all raw program XML and Patch xml and begin Image download.
Doesn't matter whether anything is accessible or not u get new image of ur choice.
If u get sahara error you are not immediately beginning download as ur phone enters into EDL.
Suggestion: Once u get back image sell the [email protected] quarter of cost as it's impossible to run the device in the way you want. The tools are not supported for open source development. The device is fragile, a little tweak and you lose IMEI,SN and soforth your phone network. This is not a device to temper, if u still do so, you will never come out from situation your stuck now.
Click to expand...
Click to collapse
I also struck in the fastboot mode, All i have done is flashed android q image from asus official site , worked fine with few bugs, then i thought return to stock stable rom, downloaded image from the same page and tried the procedure given, but i got some error initially and struck in fastboot. Iam able to flash latest firmware by connecting to PC in fastboot, all files are able to flash and after restart, a message is appearing with red exclamatory symbol that my device is no longer boot, its not trustable etc and after few seconds restated to fastboot mode. I have tried this in both active slot A and B. I tried to flash android q image too. same error popping up. and iam struck in fastboot now, no recovery nothing, phone doest even switched off, if i longpress power key, restarts again to fastboot.
I want to try your solution, but iam not so expert in sdk things, i did't understand few points in your reply, can you please elaborate step by step procedure, which tools should i download how should i proceed etc. please iam going nuts wasting time behind this phone. or please refer any guide or website to unbrick my asus zenfone 5z.
Thanks in advance.

same
ashok20205 said:
I also struck in the fastboot mode, All i have done is flashed android q image from asus official site , worked fine with few bugs, then i thought return to stock stable rom, downloaded image from the same page and tried the procedure given, but i got some error initially and struck in fastboot. Iam able to flash latest firmware by connecting to PC in fastboot, all files are able to flash and after restart, a message is appearing with red exclamatory symbol that my device is no longer boot, its not trustable etc and after few seconds restated to fastboot mode. I have tried this in both active slot A and B. I tried to flash android q image too. same error popping up. and iam struck in fastboot now, no recovery nothing, phone doest even switched off, if i longpress power key, restarts again to fastboot.
I want to try your solution, but iam not so expert in sdk things, i did't understand few points in your reply, can you please elaborate step by step procedure, which tools should i download how should i proceed etc. please iam going nuts wasting time behind this phone. or please refer any guide or website to unbrick my asus zenfone 5z.
Thanks in advance.
Click to expand...
Click to collapse
same problem any solution for that

ashok20205 said:
I also struck in the fastboot mode, All i have done is flashed android q image from asus official site , worked fine with few bugs, then i thought return to stock stable rom, downloaded image from the same page and tried the procedure given, but i got some error initially and struck in fastboot. Iam able to flash latest firmware by connecting to PC in fastboot, all files are able to flash and after restart, a message is appearing with red exclamatory symbol that my device is no longer boot, its not trustable etc and after few seconds restated to fastboot mode. I have tried this in both active slot A and B. I tried to flash android q image too. same error popping up. and iam struck in fastboot now, no recovery nothing, phone doest even switched off, if i longpress power key, restarts again to fastboot.
I want to try your solution, but iam not so expert in sdk things, i did't understand few points in your reply, can you please elaborate step by step procedure, which tools should i download how should i proceed etc. please iam going nuts wasting time behind this phone. or please refer any guide or website to unbrick my asus zenfone 5z.
Thanks in advance.
Click to expand...
Click to collapse
same problem any solution for that ?

TG87 said:
Dear All,
I was trying to install a customer ROM in my Asus Zenfone 5z. I was able to unlock the bootloader using official asus app. Then i managed to install a TWRP recovery. there was some partition issue so i flashed recovery in both partitions. the recovery worked fine and i managed to install the pixel rom. after that i wiped dalvik cach and some other items throgh recovery and restarted the phone.
After restart, it is stuck in bootloader. If i select start, recovery mode or power off, it gets rebooted and come back to bootloader again. Seems like a brick scenario.
So i tried the following:
1. Downloaded AFT tool and tried to flash the latest firmware version.. It gave a FPT error and then error on unable to load into recovery mode
2. Tried to run flashall_aft.cmd in directory containing latest firmware.. it said to internal/external command exists
3. Sideload using adb sideload command.. the error was could not read the file..
I am not sure what i can try next.. could you please help.. The details on bootloader screen are:
Fastboot mode
Product name _ ZS620KL
Bootloader version - WW_user_90.10.138.157
Secure Boot - yes
Active Slot A
Device State Unlocked
Click to expand...
Click to collapse
fastboot --cmdline "lge.kcal=0|0|0|x" boot customrecovery.img

I also have the same problem. Tried installing TWRP but got stuck in Fastboot mode. Says phone is corrupted and cannot be trusted.
Product Name: ZS620KL
Bootloader Version: WW_user_100.10.107.70
Secure Boot: Yes
Active Slot: b
Device State: locked

kristoff07 said:
I also have the same problem. Tried installing TWRP but got stuck in Fastboot mode. Says phone is corrupted and cannot be trusted.
Product Name: ZS620KL
Bootloader Version: WW_user_100.10.107.70
Secure Boot: Yes
Active Slot: b
Device State: locked
Click to expand...
Click to collapse
Your bootloader is relocked, and vertified boot is enabled, if I had not misunderstanded the information you have given. Try unlocking your bootloader first.

TG87 said:
Dear All,
I was trying to install a customer ROM in my Asus Zenfone 5z. I was able to unlock the bootloader using official asus app. Then i managed to install a TWRP recovery. there was some partition issue so i flashed recovery in both partitions. the recovery worked fine and i managed to install the pixel rom. after that i wiped dalvik cach and some other items throgh recovery and restarted the phone.
After restart, it is stuck in bootloader. If i select start, recovery mode or power off, it gets rebooted and come back to bootloader again. Seems like a brick scenario.
So i tried the following:
1. Downloaded AFT tool and tried to flash the latest firmware version.. It gave a FPT error and then error on unable to load into recovery mode
2. Tried to run flashall_aft.cmd in directory containing latest firmware.. it said to internal/external command exists
3. Sideload using adb sideload command.. the error was could not read the file..
I am not sure what i can try next.. could you please help.. The details on bootloader screen are:
Fastboot mode
Product name _ ZS620KL
Bootloader version - WW_user_90.10.138.157
Secure Boot - yes
Active Slot A
Device State Unlocked
Click to expand...
Click to collapse
secure boot yes? you may have vertified boot, you can try flash patched magisk boot.img to disable that

jjgvv said:
Your bootloader is relocked, and vertified boot is enabled, if I had not misunderstanded the information you have given. Try unlocking your bootloader first.
Click to expand...
Click to collapse
I checked the info and it gave me this:
{
"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"
}

(Guide) How to fix a hard bricked Redmi Note 9 (Merlin) (Hard Brick)

{
"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"
}
A how-to guide of restoring a completely bricked Redmi Note 9​
Hi, In this guide, I will teach you how to fix a hard-bricked Redmi Note 9 (merlin) and bring it back to its original state.
How does a hard-bricked Redmi Note 9 look like? it's stuck in an infinite boot loop showing only the Redmi logo,
Can't access recovery with power+vol down, can't enter fastboot, can't connect it to a computer either.
If this is your phone here's how you can solve it without the need for service.
Following this guide keep in mind that everything would be erased from your phone including custom Recovery or ROM obviously. Also the bootloader would get locked again.
(I mean at this point you either have a useless brick or a working phone, you are choosing).
This is tested by me, and it works as long as you follow the steps carefully and you don't skip anything.
(I did this on Windows 10 btw)
You gonna need to download, Python and the official Xiaomi fastboot image for Redmi Note 9. Also the zip file I'm attaching bellow. the zip file contains the MTK Drivers, SP Flash Tool, and some additional scripts like MI auth bypass etc,
Get thefastboot image from here select your version (I picked the latest global) click download scroll down where it says "type:fastboot" and click "download: full Rom" the file name should look like this "merlin_images....tgz" or "merlin_global_images....tgz", etc, NOT miui_Merlin.zip,
Get python from the official website site, I tested it with 3.9.7 but the latest version should work fine. Now, you have all the necessary files to start.
Let the phone's battery die so the boot looping completely ends. (else you'll get error STATUS_EXT_RAM_EXCEPTION (0xC0050005) when using SP Flash Tool). ( I also tried it with a full battery and still worked so idk for sure how necessary this step is).
Install Python select the "add to PATH" option, you can test if it was installed correctly by opening cmd and writing "python" or "py" it should output the python version.
Extract the attached zip file and the fastboot image each into their folders.
Enter the MTK Driver folder Install the MTK Driver for MTK SP flash tool.MTK_Driver_Auto_Installer_SP_Drivers_20160804.exe, Reboot your computer.
Enter the python folder, run the "install pyusb pyserial json5.bat" when it's done close the terminal.
Enter the driver folder, this folder contains a USB to COM driver for MTK Devices, right-click the "cdc-acm.inf" click install.
Enter the libusb folder, run the libusb-win32-devel-filter-1.2.6.0.exe file, click next,next...install, when it's done it would prompt you to launch "filter installer wizard" click finish, when the wizard shows up, select "Install a device filter" it would show you your connected USB devices,
Get your phone and a USB cable, connect the USB cable to your computer,while holding the volume up button on your phone connect your phone to the computer (Based on community feedback you might need to hold both up and down volume buttons AND power button!) once your phone turns on you would see your phone listed as "MediaTek USB Port" at the libusb filter installer before your phone reboots click at the "MediaTek USB Port" and then click install if you don't do it on time, your phone will get disconnected because of rebooting, try again re-plugging your phone. once you click install, You should get a pop-up message saying "...device filter successfully installed for MediaTek USB port..." click ok and exit, then remove your phone from the computer.
Enter the bypass folder (This folder contains scripts to bypasses the Mi auth) double click the "1ST RUN THIS.bat" when it says "waiting for device" hold volume up and plug your phone into the computer (btw: You can let the button when it's recognized by the script). now most likely it would say "RuntimeError: unexpected output, expected 0xfd got 0xfe", if it does close the script and disconnect your phone, Try the "2ND RUN THIS.bat" when it shows "Waiting for device" hold volume up and connect your phone to the computer, wait till the console recognizes your phone, (At this part it might take few tries to make it work, try reconnecting your phone without holding any buttons or try holding volume down while reconnecting your phone) Once it gets recognized it would output "Found port = COM3" and Protection disabled. At this part your phone has stopped boot looping which is good but, DO NOT TOUCH YOUR PHONE, DO NOT DISCONNECT IT FROM THE COMPUTER, set your phone aside, and continue with the guide.
Enter the SP Flash Tool folder run the flash_tool.exe at the Download-Agent click choose and select the DA_6765_6785_6768_6873_6885_6853.bin file which is included in the SP flash tool folder.
At the Authentication File, click choose and select the auth_sv5.auth included in the SP flash tool folder.
At the Scatter-loading File, click choose, go to the fastboot image extraction folder (Step 4) then enter the images folder and select the MT6768_Android_scatter.txt file (Fastbootimage/images/MT6768_Android_scatter.txt)
On the drop-downbox below the "Authentication File" label change the option from Download Only to Firmware Upgrade.
At the toolbar above click Options -> Option... go to Connection check the UART option and set the Baud rate to 921600, make sure the com port option is set to com 3, then close the window.
Click Download with the green arrow, now wait till it finished flashing your phone this would take quite of time, at this part DO NOT TOUCH ANYTHING LET IT FINISH TO AVOID ANY CURROPTION ON YOUR PHONE. (If you get "Error : STATUS_STOR_LIFE_EXHAUST" go to options-> general and uncheck Storage life cycle check).
When it's done it would show you a pop-up window "Download Ok" with a green background and a checkmark, click the X to close, and now you can also close the SP Flash tool app.
Disconnect your device from your computer and press the power buttonto start your phone, connect it to a charger or back to the computer since there was no charge so it won't die suddenly now.
Your phone now should boot normally showing the MIUI logo, because its first boot it would take few minutes for the phone to boot, wait patiently and you would see the "first setup" screen.
That's it! You successfully brought back to life a hard-bricked Redmi Note 9 (merlin). A huge weight now has lifted from you hf.
Credits:
Bypass script and payload included in the attachment file is provided by (chaosmaster, xyzz) github

Very good guide, my friend.
Thank you very much for details and contribution

My device was brick yesterday, OTA update pixel plus ui rom and get boot loop at redmi logo. I do exactly your tutor but in step 11 my device is not recognized. Any solution for me? Thanks.

aries.1482 said:
My device was brick yesterday, OTA update pixel plus ui rom and get boot loop at redmi logo. I do exactly your tutor but in step 11 my device is not recognized. Any solution for me? Thanks.
Click to expand...
Click to collapse
If you did step 9 it should recognize it, try to reboot your computer if you didn't already. Also your phone would be visible only for a second before it gets disconnected so you have to act fast.

vagelis199 said:
If you did step 9 it should recognize it, try to reboot your computer if you didn't already. Also your phone would be visible only for a second before it gets disconnected so you have to act fast.
Click to expand...
Click to collapse
Your window is 32 or 64 bit, I use windows 10 64 bit and did all step, one by one but no effect.

Finally, done it. I found this:
- Hold both vol up and down when plug in so the device recognize.
- You must choose right fastboot image (origin stock rom), if not devices can't boot in to miui rom cause bootloader locked after sp flash
And at last, thank you very much, you saved my day.

aries.1482 said:
Finally, done it. I found this:
- Hold both vol up and down when plug in so the device recognize.
- You must choose right fastboot image (origin stock rom), if not devices can't boot in to miui rom cause bootloader locked after sp flash
And at last, thank you very much, you saved my day.
Click to expand...
Click to collapse
Cool ill update the guide!

Hi, My device is recognized as "Qualcom HS-USB QDLoader 9008" not the "MediaTek USB Port" on step 11 and it seems not recognized on step 12. Do you have any solutions for me. Thanks!

lionfishes said:
Hi, My device is recognized as "Qualcom HS-USB QDLoader 9008" not the "MediaTek USB Port" on step 11 and it seems not recognized on step 12. Do you have any solutions for me. Thanks!
Click to expand...
Click to collapse
I think you are on a wrong guide, That's a guide for a Redmi Note 9, not the Pro version

vagelis199 said:
I think you are on a wrong guide, That's a guide for a Redmi Note 9, not the Pro version
Click to expand...
Click to collapse
My phone is Redmi Note 9. I tried to restart it yesterday and couldn't power on again. So I'm looking for some solutions to see if it can be fixed. Thanks!

lionfishes said:
My phone is Redmi Note 9. I tried to restart it yesterday and couldn't power on again. So I'm looking for some solutions to see if it can be fixed. Thanks!
Click to expand...
Click to collapse
There's no qualcomm version of Redmi Note 9

i made a mistake,when i clicked to download the fastboot at the xiaomi site,i clicked the fastboot link to download,but i didnt see that it brings you to a page where it has all the downloads again,so i stopped the operation and restarted it with the correct scatter this time.
Now im waiting to see what will happen,how long does it usually take for the spflash to finish?
Also at the bottom of spflash where it says 0b/s,emmc etc. should it stay at 0 when you start the download?
edit:
managed to make it work,one important thing for me was at the option/option,had to select com port com 3

nikosefs said:
i made a mistake,when i clicked to download the fastboot at the xiaomi site,i clicked the fastboot link to download,but i didnt see that it brings you to a page where it has all the downloads again,so i stopped the operation and restarted it with the correct scatter this time.
Now im waiting to see what will happen,how long does it usually take for the spflash to finish?
Also at the bottom of spflash where it says 0b/s,emmc etc. should it stay at 0 when you start the download?
edit:
managed to make it work,one important thing for me was at the option/option,had to select com port com 3
Click to expand...
Click to collapse
Thanks i updated the guide including this

i'm having an ERROR notification : STATUS_EXT_RAM_EXCEPTION (0xC0050005) help me

Looking for some info/help if possible: apologies i'm not trying to derail your thread.
I had bricked my RN9 but managed to unbrick and have it working ok now however I am wanting to restore it/lock the bootloader to allow for using banking apps. But I am encountering an issue. I had tried using MiFlash Tool but during the flash, I get a mismatch error and it doesn't succeed in flashing the Fastboot rom.
If i was to follow your guide from step 13, would this work for me? Or which steps do I need to skip in your list?
Thank you for any advice/help
** I finally managed to get it sorted ** used the EDL flash guide and then flashed in SPFT.
[GUIDE] How To bypass authentication and flash in EDL with NO auth for FREE
Thanks to: chaosmaster / k4y0z: GitHub / XDA xyzz / xyz`: GitHub / XDA Dinolek: GitHub / XDA How to install: 1. Download the attached file: VD171_MTK-bypass.zip. 2. Extract the file and open the folder. 3. Run and install python...
forum.xda-developers.com

vagelis199 said:
Hi, In this guide, I will teach you how to fix a hard-bricked Redmi Note 9 (merlin) and bring it back to its original state.
How does a hard-bricked Redmi Note 9 look like? it's stuck in an infinite boot loop showing only the Redmi logo,
Can't access recovery with power+vol down, can't enter fastboot, can't connect it to a computer either.
If this is your phone here's how you can solve it without the need for service.
Following this guide keep in mind that everything would be erased from your phone including custom Recovery or ROM obviously. Also the bootloader would get locked again.
(I mean at this point you either have a unless brick or a working phone, you are choosing).
This is tested by me, and it works as long as you follow the steps carefully and you don't skip anything.
(I did this on Windows 10 btw)
You gonna need to download, Python and the official Xiaomi fastboot image for Redmi Note 9. Also the zip file I'm attaching bellow. the zip file contains the MTK Drivers, SP Flash Tool, and some additional scripts like MI auth bypass etc,
Get the fastboot image from here select your version (I picked the latest global) click download scroll down where it says "type:fastboot" and click "download: full Rom" the file name should look like this "merlin_images....tgz" or "merlin_global_images....tgz", etc, NOT miui_Merlin.zip,
Get python from the official website site, I tested it with 3.9.7 but the latest version should work fine. Now, you have all the necessary files to start.
Let the phone's battery die so the boot looping completely ends. (I'm not sure if this is completely necessary but that's how I did it).
Install Python select the "add to PATH" option, you can test if it was installed correctly by opening cmd and writing "python" or "py" it should output the python version.
Extract the attached zip file and the fastboot image each into their folders.
Enter the MTK Driver folder Install the MTK Driver for MTK SP flash tool. MTK_Driver_Auto_Installer_SP_Drivers_20160804.exe, Reboot your computer.
Enter the python folder, run the "install pyusb pyserial json5.bat" when it's done close the terminal.
Enter the driver folder, this folder contains a USB to COM driver for MTK Devices, right-click the "cdc-acm.inf" click install.
Enter the libusb folder, run the libusb-win32-devel-filter-1.2.6.0.exe file, click next,next...install, when it's done it would prompt you to launch "filter installer wizard" click finish, when the wizard shows up, select "Install a device filter" it would show you your connected USB devices,
Get your phone and a USB cable, connect the USB cable to your computer, while holding the volume up button on your phone connect your phone to the computer (Based on community feedback you might need to hold both up and down volume buttons) once your phone turns on you would see your phone listed as "MediaTek USB Port" at the libusb filter installer before your phone reboots click at the "MediaTek USB Port" and then click install if you don't do it on time, your phone will get disconnected because of rebooting, try again re-plugging your phone. once you click install, You should get a pop-up message saying "...device filter successfully installed for MediaTek USB port..." click ok and exit, then remove your phone from the computer.
Enter the bypass folder (This folder contains scripts to bypasses the Mi auth) double click the "1ST RUN THIS.bat" when it says "waiting for device" hold volume up and plug your phone into the computer (btw: You can let the button when it's recognized by the script). now most likely it would say "RuntimeError: unexpected output, expected 0xfd got 0xfe", if it does close the script and disconnect your phone, Try the "2ND RUN THIS.bat" when it shows "Waiting for device" hold volume up and connect your phone to the computer, wait till the console recognizes your phone, (At this part it might take few tries to make it work, try reconnecting your phone without holding any buttons or try holding volume down while reconnecting your phone) Once it gets recognized it would output "Found port = COM3" and Protection disabled. At this part your phone has stopped boot looping which is good but, DO NOT TOUCH YOUR PHONE, DO NOT DISCONNECT IT FROM THE COMPUTER, set your phone aside, and continue with the guide.
Enter the SP Flash Tool folder run the flash_tool.exe at the Download-Agent click choose and select the DA_6765_6785_6768_6873_6885_6853.bin file which is included in the SP flash tool folder.
At the Authentication File, click choose and select the auth_sv5.auth included in the SP flash tool folder.
At the Scatter-loading File, click choose, go to the fastboot image extraction folder (Step 4) then enter the images folder and select the MT6768_Android_scatter.txt file (Fastbootimage/images/MT6768_Android_scatter.txt)
On the drop-down box below the "Authentication File" label change the option from Download Only to Firmware Upgrade.
At the toolbar above click Options -> Option... go to Connection check the UART option and set the Baud rate to 921600, make sure the com port option is set to com 3, then close the window.
Click Download with the green arrow, now wait till it finished flashing your phone this would take quite of time, at this part DO NOT TOUCH ANYTHING LET IT FINISH TO AVOID ANY CURROPTION ON YOUR PHONE.
When it's done it would show you a pop-up window "Download Ok" with a green background and a checkmark, click the X to close, and now you can also close the SP Flash tool app.
Disconnect your device from your computer and press the power button to start your phone, connect it to a charger or back to the computer since there was no charge so it won't die suddenly now.
Your phone now should boot normally showing the MIUI logo, because its first boot it would take few minutes for the phone to boot, wait patiently and you would see the "first setup" screen.
That's it! You successfully brought back to life a hard-bricked Redmi Note 9 (merlin). A huge weight now has lifted from you hf.
Credits:
Bypass script and payload included in the attachment file is provided by (chaosmaster, xyzz) github
Click to expand...
Click to collapse
Hi thanks a lot for your help. I accidentally flashed a redmi 10x miui 11, wanted to downgrade my Redmi 9 from 12.5, bad perfomance, resulting in your hard-bricked version. Flashing last fastboot version doesn't help, do i have a chance to fix it?

vagelis199 said:
Get the fastboot image from here select your version (I picked the latest global) click download scroll down where it says "type:fastboot" and click "download: full Rom" the file name should look like this "merlin_images....tgz" or "merlin_global_images....tgz", etc, NOT miui_Merlin.zip,
Click to expand...
Click to collapse
Hi and thanks for this detailed guide.
I bricked my merlin trying to root it (long history trying to get TWRP to stick)
I am now in the redmi logo loop and i am trying to follow this with great care.
however in the step above, no matter what I choose in "Yshasalger" page, i end up with a Recovery ROM and the file name contains the miui prefix as opposed to what you clearly state.
see image:
I am asking because i am scared of making more mistakes.
So i guess my question is if someone can check it happens to them (maybe the page changed since the writting of this guide)
If i should try with that ROM zip file or if there is another place i can get the proper one
I want to if possible to flash an older MIUI / Android than the latest 12 xxx / Android 11 as i find the phone to be really slow since the last OTA update.

Coroneln said:
Hi and thanks for this detailed guide.
I bricked my merlin trying to root it (long history trying to get TWRP to stick)
I am now in the redmi logo loop and i am trying to follow this with great care.
however in the step above, no matter what I choose in "Yshasalger" page, i end up with a Recovery ROM and the file name contains the miui prefix as opposed to what you clearly state.
see image:
View attachment 5476667
I am asking because i am scared of making more mistakes.
So i guess my question is if someone can check it happens to them (maybe the page changed since the writting of this guide)
If i should try with that ROM zip file or if there is another place i can get the proper one
I want to if possible to flash an older MIUI / Android than the latest 12 xxx / Android 11 as i find the phone to be really slow since the last OTA update.
Click to expand...
Click to collapse
That's because you are choosing recovery and not fastboot, choose fastboot as type scroll down it has two links for recovery and for fastboot image. Check the file name

vagelis199 said:
That's because you are choosing recovery and not fastboot, choose fastboot as type scroll down it has two links for recovery and for fastboot image. Check the file name
Click to expand...
Click to collapse
i promise i am choosing fastboot but it ends up in the recovery i have tried several different versions in case it was a file wrongly indexed.

TL|DR
Python errors, step 8 and 12 on Windows 10
Go to -> "start" and type "Manage App Execution Aliases". Go to it and turn off "Python"
=========================
Now read....
Just in case someone has trouble with step: 8
Escenario: the BAT file calls `python` and in some windows 10 this will result in a message about the windows store (Even if the path is added)
Python was not found; run without arguments to install from the Microsoft Store, or disable this shortcut from Settings
but `py` works, so just edit the BAT file and replace the call for `python` with `py` it will install all the python modules with no errors.
EDIT:
This also affects step: 12
Found a solution here: https://stackoverflow.com/questions...arguments-to-install-from-the-microsoft-store
Go to -> "start" and type "Manage App Execution Aliases". Go to it and turn off "Python"
The error:
After editing the BAT file replacing `python` with `py`

How To Guide Flashing ColorOs 12 on Oppo reno6 5G CPH2251

Hey Guys,
Many users downgraded their ColorOs12 to ColorOs11.3 on oppo reno6 5G device due to many bugs on it, they want to install ColorOs12 but they are not getting OTA update, they are wandering how can they install ColorOs 12 back on their phone, So, here I have come up with a method to directly flash ColorOS12.
Note: Data will(or might) be erased in this method so please take backup of you data on phone.
This has been tested on Indian version, I am not sure if it will work for other countries.
I strongly recommend to take full firmware backup using method below before proceeding
Backup full firmware(ROM) of any MediaTek device using MTK client| Oppo reno6 5G | MT6877
Hello Guys, Many times we encounter a situation where we need to do some software update, flash custom ROM, install stock ROM etc, so it is advisable to take full firmware/ROM backup of your device. If required then you can flash this backup to...
forum.xda-developers.com
Step1: Pre-requisite -Installing required drivers and setup
From link below download drivers and setup.
Install mediatek driver.
Install python (during installation of python please select "install for all user" from customization and tick add path to system variable)
install usbdk.
download extarct Mtk client tool.
go to folder where you extract mtk client
View attachment 5541629
open cmd here and run below command
cd mtkclient
pip3 install -r requirements.txt
In default setting it takes 2 hour to flash but after change it takes 13 min. If you want to increase flashing speed then open mtk_daxflash.py file from library folder, search "dsize = min(length, 0x200)" and replace it with "dsize = min(length, 0x2004)" , save and close the file.
You need to close command prompt in order to take effect of change.
Reference(https://github.com/bkerler/mtkclient/issues/271)
New Qcom Mtk Driver V3.0.5.1.rar | by TUSER HP for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Download Python
The official home of the Python Programming Language
www.python.org
GitHub - bkerler/mtkclient: MTK reverse engineering and flash tool
MTK reverse engineering and flash tool. Contribute to bkerler/mtkclient development by creating an account on GitHub.
github.com
Releases · daynix/UsbDk
Usb Drivers Development Kit for Windows. Contribute to daynix/UsbDk development by creating an account on GitHub.
github.com
Step2: Download and extract the ColorOs 12 firmware
{
"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"
}
CPH2251_11_C.27_ColorOS12_Android12_Latest.rar
drive.google.com
Step3: Flash the firmware
on cmd type below command to flash the firmware
python mtk wl "ROM location full path"
it will wait for devices.. Power off the phone, wait 10 sec then press vol up + vol down together and then plug the usb cable.
Once device detected , it will display devices information and start flashing
View attachment 5541639
View attachment 5541641
View attachment 5541645
While flashing it will dump the preloader, this file is very important so, please keep this file safely. this file may require in future.
View attachment 5541661
Step4: Boot the phone
Once flashing completed, press vol up + power button together for 30 sec. Wait for device to boot.
Step5: Flashing the preloader.bin (only if required)
In case, even after flashing completed successfully but some time device does not boot, only black screen, no charging sign either then don't panic, device has entered into emergency download mode, if you face the same then it's time to flash preloader.bin file. Follow below steps
1) download SP flash tool specific version v5.2148. (https://androidmtk.com/smart-phone-flash-tool)
2) download attached preloader.bin, scatter file and auth file from link below and place all these files at same folder.
MT6877_flashing_preloader.zip
drive.google.com
3) open sp flash tool, select download agent files from mtk folder as shown on image and load scater file and auth files respectively.
View attachment 5581171
4) In cmd run command "python mtk payload". Now press and hold vol+ vol- or all the buttons together, it should show payload sent successfully.
5) Now in sp flash tool click on Download button, it should flash the preloader successfully.
6) once preloader is flash successfully you can turn on the phone by pressing vol+ and power button together for 20 sec. If attached preloader does't flash then you can try flashing your device backup preloader.bin created/shown on step3.
so by this way we directly flashed ColorOS 12 on oppo reno6 5G.
Tips: If due to some reason flashing did not completed successfully then please press vol up and power button together for 30-40 sec to boot the phone (exit the brom mode).
Disclaimer: I have tested this method on my phone, it's 100% working but I will not responsible if damage any damage happens to your device while doing this. So do it at your own risk.

thanx nand for helping me in upgrading to coloros 12 again,this process worked successfully.

Thanks for the info.
My question is: can I use this method to remove phone branding using stock firmware image you pointed in your post?

macslui said:
Thanks for the info.
My question is: can I use this method to remove phone branding using stock firmware image you pointed in your post?
Click to expand...
Click to collapse
Hi, i didn't understand your question. Can you explain more.

Nand kumar said:
Hi, i didn't understand your question. Can you explain more.
Click to expand...
Click to collapse
Sorry. Try to better explain: I have a Vodafone branded reno 6 that accept any sim card. I only want to remove Vodafone branding (boot logo and custom app that are present only in branded phone).

Yes, you can try. I recommend you to take full firmware backup before doing this as explained in guide.

bonjour a tous quand j'écrit pip3 install -r requirements.txt j'ai une erreur :
ERROR: could not open requirements file :[Errno2] no such file or directory: requirements.txt
merci de m'aider

Please run this command from mtk folder

Nand kumar said:
Yes, you can try. I recommend you to take full firmware backup before doing this as explained in guide.
Click to expand...
Click to collapse
Hi Nand, I've done everything as you pointedout in this document and backup document.
Unfortunately I was able to flash the phone with success but now it do not turn it on anymore.
I've tried to every button combination but it remain off.
I also cannot enter brom mode anymore.
Have you some suggestion?
Thanks!

macslui said:
Hi Nand, I've done everything as you pointedout in this document and backup document.
Unfortunately I was able to flash the phone with success but now it do not turn it on anymore.
I've tried to every button combination but it remain off.
I also cannot enter brom mode anymore.
Have you some suggestion?
Thanks!
Click to expand...
Click to collapse
I was able to reenter brom mode. Now I'm reflashing again.

Hi all, everything ok now. I've flashed COS12 and now my phone is non more brand (vodafone) related.

Nand kumar said:
Please run this command from mtk folder
Click to expand...
Click to collapse
ok merci je ne savais pas comment ouvrir cmd a partir d'un fichier fonctionne très bien merci

macslui said:
Hi all, everything ok now. I've flashed COS12 and now my phone is non more brand (vodafone) related.
Click to expand...
Click to collapse
macslui said:
Glade to hear that you removed brand using thus method.
Click to expand...
Click to collapse

Unfortunatly COS12 in my opinion Is very laggy. I'm trying tio rollback to COS11 but, after flashing using your guide, the phone do not boot anymore. So I have to go back to 12. It's only my experience on COS12?

Hi, for many peoples, Color os12 was not laggy but have some bugs like battery draining etc.
For your device is not booting on color 11 then you have to flash preloader using Sp flash tool version v5.2148

Thanks Nand, allways ready to answer, thanks! Can please explain how to flash preloader with SP flash tool please? I have preloader from backup. Thanks again for your support.

Removed ...

macslui said:
Thanks Nand, allways ready to answer, thanks! Can please explain how to flash preloader with SP flash tool please? I have preloader from backup. Thanks again for your support.
Click to expand...
Click to collapse
Removed my contact details as I was getting to many message/calls on phone.

macslui said:
Hi Nand, I've done everything as you pointedout in this document and backup document.
Unfortunately I was able to flash the phone with success but now it do not turn it on anymore.
I've tried to every button combination but it remain off.
I also cannot enter brom mode anymore.
Have you some suggestion?
Thanks!
Click to expand...
Click to collapse
Same happen with me.. My phone is not bootibg up , no logo, no charging logo, not even single sign for alive please help me out help help

Cosmicsh said:
Same happen with me.. My phone is not bootibg up , no logo, no charging logo, not even single sign for alive please help me out help help
Click to expand...
Click to collapse
Removed my contact details as I was getting to many message/calls on phone.

nv data corrupted redmi note 9 (merlin)

Hi everyone, days ago I posted on the forum that I had a bootloop, I could not enter fastboot or recovery, well, I managed to install the rom by sp flash tool without errors, but now I get the error "nv data is corrupted" as seen in the video that I attach, anyone know of a viable solution? What is free and do not have any other problem and my phone back to normal? Because I can enter fastboot and maybe download or twrp or download pixel experience or a rom, What do you recommend?
Your browser is not able to display this video.

I have the same problème did u solve it ?

with me we are in 3, please share if you find something !
you reached a solution so wished and few seconds later you get into nightmare back again !

Same here, but on redmi 9. I guess i made a mistake thaough, i tried to install EU rom and then this happened. Did you make this mistake too?

after otg update of miui 13 it happens. maybe @VD171 help us ?

same here
after updates got a boot loop with no access to recovery or fastboot,
after successful flashing, i got NV corruption.
every year a redmi phone with updates problem
redmi phones are a mess with updates

coliotte said:
same here
after updates got a boot loop with no access to recovery or fastboot,
after successful flashing, i got NV corruption.
every year a redmi phone with updates problem
redmi phones are a mess with updates
Click to expand...
Click to collapse
Me too
We need to send a message to Xiaomi support and let them know about this issue so that they can provide a solution for this problem in the future. They are the producer of this phone and can provide a remote tool for nvram repair
Redmi note 9 merlin will receive the MIUI 14 update and still supported by Xiaomi

Found a good solution I sold it to a repair shop for parts and got an iPhone already updated that iPhone and guess what IMEI is still there .

Recovered by simple way first install Engineering rom after that downgrade to 12.5

devjmi said:
Recuperado de manera simple primero instalar la ROM de ingeniería después de esa degradación a 12.5
Click to expand...
Click to collapse
Have you tried this method?
I already put it to the test to see if it revived my redmi note 9 but apparently it continues the same without any result, what's more, it is not capable of flashing the engineering ROM either.

coliotte said:
same here
after updates got a boot loop with no access to recovery or fastboot,
after successful flashing, i got NV corruption.
every year a redmi phone with updates problem
redmi phones are a mess with updates
Click to expand...
Click to collapse
Yes I did, you can try searching how to flash engineering rom on dead phone on youtube

Good news people, I found how to revive our bricks with nv data corrupted, it is a simple solution, but that is if our device is going to be left without IMEI, or baseband, but it will turn on and work again, staying with MIUI 11 as a system, in the next comment I will leave the step by step and from now on I will continue investigating how to restore the IMEI and the base band of the equipment.

Relive redmi note 9 / redmi 10x 4G from NV DATA CORRUPTED error
STEP 1:
We download the file from the link that I am going to attach, there we unzip it and leave it in a location on our PC that we want, after these we perform the ByPass to be able to flash with the SP Flash Tool) if you do not have the ByPass I leave the link, remember that for it to run you have to download Python).
download links:
Necessary files: https://drive.google.com/file/d/1dUy8j9jHofv0NoYeyYWNiwFnP-n04QGz/view
ByPass: https://www.mediafire.com/folder/a68qyu0m7mr2i/AUTH+BYPASS+V3
Once the files have been extracted, we prepare the device (VERY IMPORTANT WE USE THE SP FLASH TOOL VERSION THAT COMES IN THE ZIP FILE, IF WE USE ANOTHER DIFFERENT VERSION IT WILL NOT FLASH THE DEVICE)
We perform the ByPass of the device (vol - y and connect the USB cable with the phone turned off).
Once the ByPass is done, what we do is open the sp flash tool and from there we load the Scatter that is in the folder of step 1 and then we load the DA files that are in the sp flash tool folder that was with the file Zip that we downloaded, from there we click on download and the flashing will begin (If it asks us for AUTH file, it means that the ByPass has not been carried out since that file is not required for flashing)
After those files are flashed we proceed to open the en sp flash tool the Scatter that is in the folder of step 2, and before flashing we must change the option from Download Only to Firmware Update if we do not do this it will give us error during flashing, and that's it, our redmi note 9 / redmi 10X 4G will have already revived from that NV DATA CORRUPTED error, and as I indicated at the beginning, the phone revives with MIUI 11 without baseband or IMEI, if I manage to find out how restore the IMEI and the base band I will be informing you, have an excellent day and I hope this method works for you, it worked for me
(Files from HALABTECH)

mrdeivid said:
Relive redmi note 9 / redmi 10x 4G from NV DATA CORRUPTED error
STEP 1:
We download the file from the link that I am going to attach, there we unzip it and leave it in a location on our PC that we want, after these we perform the ByPass to be able to flash with the SP Flash Tool) if you do not have the ByPass I leave the link, remember that for it to run you have to download Python).
download links:
Necessary files: https://drive.google.com/file/d/1dUy8j9jHofv0NoYeyYWNiwFnP-n04QGz/view
ByPass: https://www.mediafire.com/folder/a68qyu0m7mr2i/AUTH+BYPASS+V3
Once the files have been extracted, we prepare the device (VERY IMPORTANT WE USE THE SP FLASH TOOL VERSION THAT COMES IN THE ZIP FILE, IF WE USE ANOTHER DIFFERENT VERSION IT WILL NOT FLASH THE DEVICE)
We perform the ByPass of the device (vol - y and connect the USB cable with the phone turned off).
Once the ByPass is done, what we do is open the sp flash tool and from there we load the Scatter that is in the folder of step 1 and then we load the DA files that are in the sp flash tool folder that was with the file Zip that we downloaded, from there we click on download and the flashing will begin (If it asks us for AUTH file, it means that the ByPass has not been carried out since that file is not required for flashing)
After those files are flashed we proceed to open the en sp flash tool the Scatter that is in the folder of step 2, and before flashing we must change the option from Download Only to Firmware Update if we do not do this it will give us error during flashing, and that's it, our redmi note 9 / redmi 10X 4G will have already revived from that NV DATA CORRUPTED error, and as I indicated at the beginning, the phone revives with MIUI 11 without baseband or IMEI, if I manage to find out how restore the IMEI and the base band I will be informing you, have an excellent day and I hope this method works for you, it worked for me
(Files from HALABTECH)
Click to expand...
Click to collapse
Helo, what's the pass for the file? Thank's

Password plz

mrdeivid said:
Relive redmi note 9 / redmi 10x 4G from NV DATA CORRUPTED error
STEP 1:
We download the file from the link that I am going to attach, there we unzip it and leave it in a location on our PC that we want, after these we perform the ByPass to be able to flash with the SP Flash Tool) if you do not have the ByPass I leave the link, remember that for it to run you have to download Python).
download links:
Necessary files: https://drive.google.com/file/d/1dUy8j9jHofv0NoYeyYWNiwFnP-n04QGz/view
ByPass: https://www.mediafire.com/folder/a68qyu0m7mr2i/AUTH+BYPASS+V3
Once the files have been extracted, we prepare the device (VERY IMPORTANT WE USE THE SP FLASH TOOL VERSION THAT COMES IN THE ZIP FILE, IF WE USE ANOTHER DIFFERENT VERSION IT WILL NOT FLASH THE DEVICE)
We perform the ByPass of the device (vol - y and connect the USB cable with the phone turned off).
Once the ByPass is done, what we do is open the sp flash tool and from there we load the Scatter that is in the folder of step 1 and then we load the DA files that are in the sp flash tool folder that was with the file Zip that we downloaded, from there we click on download and the flashing will begin (If it asks us for AUTH file, it means that the ByPass has not been carried out since that file is not required for flashing)
After those files are flashed we proceed to open the en sp flash tool the Scatter that is in the folder of step 2, and before flashing we must change the option from Download Only to Firmware Update if we do not do this it will give us error during flashing, and that's it, our redmi note 9 / redmi 10X 4G will have already revived from that NV DATA CORRUPTED error, and as I indicated at the beginning, the phone revives with MIUI 11 without baseband or IMEI, if I manage to find out how restore the IMEI and the base band I will be informing you, have an excellent day and I hope this method works for you, it worked for me
(Files from HALABTECH)
Click to expand...
Click to collapse
Pass- HALAB_HT_TECH

I have 3 Solutions for this problem :
1) - After flash firmware to latest MIUI with official file, use Unlocktool [https://unlocktool.net/] to flash the firmware and restore nvram data (if already backup the NVRAM config)
VIDEO :
- IF NOT use Pandora tool [https://z3x-team.com/products/pandora/] (for repair imei (if didn't have nvram data *but need to search for new IMEI)
VIDEO :
- THIS IS FREE VERSION FOR REPAIR IMEI
VIDEO :
2) (if still bootloop or stuck) Remove plate
video :
OR
3) This is the last options, need to disassemble the device, and replace the capacitor next to CPU
VIDEO :

i hope that help

HackerSecMY said:
i hope that help
Click to expand...
Click to collapse
thanks man, but I have a question, the unlock tool is paid. Second, if I do and fix that, can I go back to MIUI 13?

mrdeivid said:
Relive redmi note 9 / redmi 10x 4G from NV DATA CORRUPTED error
STEP 1:
We download the file from the link that I am going to attach, there we unzip it and leave it in a location on our PC that we want, after these we perform the ByPass to be able to flash with the SP Flash Tool) if you do not have the ByPass I leave the link, remember that for it to run you have to download Python).
download links:
Necessary files: https://drive.google.com/file/d/1dUy8j9jHofv0NoYeyYWNiwFnP-n04QGz/view
ByPass: https://www.mediafire.com/folder/a68qyu0m7mr2i/AUTH+BYPASS+V3
Once the files have been extracted, we prepare the device (VERY IMPORTANT WE USE THE SP FLASH TOOL VERSION THAT COMES IN THE ZIP FILE, IF WE USE ANOTHER DIFFERENT VERSION IT WILL NOT FLASH THE DEVICE)
We perform the ByPass of the device (vol - y and connect the USB cable with the phone turned off).
Once the ByPass is done, what we do is open the sp flash tool and from there we load the Scatter that is in the folder of step 1 and then we load the DA files that are in the sp flash tool folder that was with the file Zip that we downloaded, from there we click on download and the flashing will begin (If it asks us for AUTH file, it means that the ByPass has not been carried out since that file is not required for flashing)
After those files are flashed we proceed to open the en sp flash tool the Scatter that is in the folder of step 2, and before flashing we must change the option from Download Only to Firmware Update if we do not do this it will give us error during flashing, and that's it, our redmi note 9 / redmi 10X 4G will have already revived from that NV DATA CORRUPTED error, and as I indicated at the beginning, the phone revives with MIUI 11 without baseband or IMEI, if I manage to find out how restore the IMEI and the base band I will be informing you, have an excellent day and I hope this method works for you, it worked for me
(Files from HALABTECH)
Click to expand...
Click to collapse
Thank you so much! I've spent months trying to find a solution and this one was the only one that worked
I've still got the IMEI issue, but at least it works now.