Hello !
I've discovered a new way to root oppo a5s ( CPH1909) after the new security update which removed the mtk-easy-su root
(NOTE : YOU WILL REQUIRE :
1- THE LATEST FRIMWARE UPDATE TO OPPO A5S
2- A PC / Laptop
3- MTK Client Tool -link will be sent here in comments <uploaded by me>
4 - mediatek driver auto installer (link is provided)
5 - SP flash tool <link is provided>
6 - a usb cable
6 - Scatter File (WILL BE UPLOADED HERE IN COMMENTS )
7 - Magisk Manager for your phone (v.26) <from github>
8 - UNLOCK BOOTLOADER USING MTK CLIENT TOOL (No data wipe needed + STEPS WILL BE PROVIDED HERE TOO)
9 - ( optional) MCT MTK BYPASS REV4 ( BUT DOWNLOAD IT IF THERE IS A PROBLEM FLASHING IN SP FLASH TOOL) + <link is provided>
NOTE BEFORE STARTING : If links have problems or it is inaccessible , please tell me to send new links in comments .
also , MAKE SURE YOUR DEVICE IS UPDATED TO THE LATEST VERSION (A.46) BECAUSE IF YOU FLASHED THE BOOT.IMG (you will know what does this file do here later ) WHICH IT IS FOR THE LATEST UPDATE AND YOUR DEVICE IS OLDER THAN IT , YOUR DEVICE MAY BRICK , AND I AM NOT RESPNSIBLE FOR ANY DAMAGES FOR YOUR DEVICE
but , if anything happens , tell me , i might help you .
BIG ULTRA NOTE BEFORE STARTING : If you will share these steps in your website, your youtube video, or anything else , please do not forget to mention the source !!!
So , let's start
STAGE 1 : PATCHING BOOT.IMG
1 - download the latest frimware here
2 - choose the latest version (a.46)
3 - after downloading and extracting the file , you will find many folders > Enter the folder (frimware) , find and copy the boot.img file to your phone
4- patch it by magisk manager
5 - copy the patched boot.img ( usually located in Downloads folder in your phone)to your pc ( note : you will need it later )
6 - replace the patched boot.img with the original one in the folder you have extracted the rom in ( but before it, please backup the original one in an external folder , and also change the patched boot.img to ( "boot.img")
Note : I uploaded the boot.img file if you want to save time instead of downloading the whole rom !
STAGE 2 : Installing MEDIATEK usb Drivers
7- open Mediatek driver auto installer
8 - while the program is opening , a window appears which asks yo if you allow the installer to make changes ... blabla , just click allow (ok)
STAGE 3 : UNLOCKING BOOTLOADER
(NOTE BEFORE STARTING : THERE IS NO DATA WILL BE LOST , AND DO NOT ENABLE THE OEM UNLOCK IN DEVELOPER OPTIONS , THE MTK CLIENT TOOL WILL GIVE AN ERROR DURING UNLOCKING , JUST KEEP IT DISABLED !!!!)
8 - After the program installed the drivers , go to MTK CLIENT TOOL , choose the device name ("OPPO A5S") , choose "UNLOCK BOOTLOADER"
{
"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"
}
9 - turn your phone off , and then press these keys (" VOLUME UP + VOLUME DOWN <<in the same time>> ") and plug your phone in using the usb cable , once you hear a sound from your pc ( the usb connection sound) , you can stop pressing , because the phone is in BROM mode ( which you can flash anything but when you unlock the bootloader first
10 - click "Start" button in MTK CLIENT TOOL in your pc , when you see messages appear on the right of the MTK CLIENT TOOL APP , DON'T UNPLUG YOUR PHONE !!!!
When the progress bar achieves 100% in the program , unplug your phone and press power button , if you found a warning message while booting , so , unfortunately....
YOU SUCCESSFULLY UNLOCKED YOUR BOOTLOADER !!!!! XD
So , do not panic if it appears !
The message will say (" your device is unlocked and cannot be trusted , rebooting in 5 seconds ") and then another message appears (" dm-verity error,
Your android system / device is corrupted, please select whether you want to boot in E10 mode or RESTART mode ")
It will give you two choices , you SHOULD choose the RESTART mode by pressing VOLUME DOWN , and tadaaaa your phone is booting normally and the data DIDN'T LOST AT ALL ( like me )
BIG ULTRA NOTE : IF THE WARNING MESSAGE DIDN'T APPEAR , SO YOUR BOOTLOADER ISN'T UNLOCKED Successfully , I ADVICE YOU TO DO THE STAGE 3 STEPS AGAIN AND KEEP AN EYE ON THE MESSAGES APPEARANCE ON THE RIGHT OF THE MTK CLIENT TOOOOL ( IF IT SHOWS THE DEVICE MODEL , THE PROCESSOR , ETC ) SO , CONTINUE THE STEPS UNTIL YOU FINISH STAGE 3 STEPS ! (as this error appears usually when unlocking bootloader)
STAGE 4 ( optional) : BYPASS
Note : you might need this stage if you found an error in sp flash tool (" VERIFIED BOOT IS ENABLED") as it is usually doesn't appear in an unlocked device !
1- open MCT MTK BYPASS , choose the chipset ( MT6765 )
2 - REBOOT your phone into brom mode ( vol up + vol down)
3 - connect your device and click start , and done !
Stage 5 ( the last stage) : Flashing
1- open SP FLASH TOOL
2 - locate the scatter file that I'll provide it in comments here !
NOTE ABOUT THE SCATTER FILE : the scatter file which comes with the frimware is CORRUPTED , I've tried to fix it and it worked !
because when I worked with this corrupted scatter file , it gave me an error while flashing !! , just editing it on my way has solved it anyway
3 - you will see a list of many files , just untick EVERY THING EXCEPT FOR THE BOOT.IMG (Make sure it is the patched one)
4 - BOOT your phone into brom mode (turn it off , press volume up + volume down , connect it with your pc)
5- once you hear the usb connection sound from your pc , click on "DOWNLOAD" button , and wait until a correct sign (√) appears in a window
6 - REBOOOOT
7 - let's Celebrate!
--thanks to the user @Anonymous V for being online when i applied these steps , he was answering every question i ask.
-- if you want anything , or need some help , type in comments here , and I and Anonymous V will be available .
(First time typing a thread )
IMPORTANT NOTE : Please put the boot.img + preloader.bin + the scatter file in a folder , then locate the scatter file using SP Flash Tool, Untick the preloader.bin to avoid bricking the device
ALSO , PLEASE DO NOT PUT THE BOOT.IMG AND THE SCATTER FILE AND FLASH THE BOOT.IMG WHILE PRELOADER.BIN IS NOT AVAILABLE IN THE SAME FOLDER , AN ERROR WILL APPEAR ( ERROR_INVALID_PRELOADER)
REPEAT : DO NOT FLASH PRELOADER.BIN , ONLY PUT IT IN THE SAME FOLDER WITH THE PATCHED BOOT.IMG AND SCATTER FILE, AND FLASH ONLY BOOT.IMG
Another note : Please install the MTK Drivers using MTK Driver Auto Installer + the drivers which comes with MTK Client Tool (UsbDK and choose your arch. 64bit or 32bit(86bit)
+Please ignore the x that i made in the MTK Client Tool screenshot
Thanks for @jimenezshown for providing this info !
MTK DRIVER AUTO INSTALLER : here
Scatter File : here
MTK CLIENT TOOL : here
MCT MTK AUTH BYPASS TOOL (uploaded by Mobile RTX website ) :here
SP FLASH TOOL : here
the patched boot.img file ( to save your time instead of getting the original file from the frimware (rom) and patch it , i thought that providing a patched boot.img by magisk app may help !) : here
note : it is patched by the latest magisk manager app (v.26)
Thank you for creating the thread @Zezo 089 , I am using Oppo A5s and now I found a way to root the phone.
I've already download all the requirements first to prepare.
But, I could not run the "MTK CLIENT TOOL V5.2".
It was just nothing appear when I double click the application.
I use Windows 11. Did it caused by the Windows?
Other question is what step is the boot.img file needed?
fb.hikmawan said:
Thank you for creating the thread @Zezo 089 , I am using Oppo A5s and now I found a way to root the phone.
I've already download all the requirements first to prepare.
But, I could not run the "MTK CLIENT TOOL V5.2".
It was just nothing appear when I double click the application.
I use Windows 11. Did it caused by the Windows?
Other question is what step is the boot.img file needed?
Click to expand...
Click to collapse
Bruh
Just turn off your Windows Defender Real-Time protection and it will work
Just , patch it using Magisk Manager (v.26)
fb.hikmawan said:
Thank you for creating the thread @Zezo 089 , I am using Oppo A5s and now I found a way to root the phone.
I've already download all the requirements first to prepare.
But, I could not run the "MTK CLIENT TOOL V5.2".
It was just nothing appear when I double click the application.
I use Windows 11. Did it caused by the Windows?
Other question is what step is the boot.img file needed?
Click to expand...
Click to collapse
fb.hikmawan said:
Thank you for creating the thread @Zezo 089 , I am using Oppo A5s and now I found a way to root the phone.
I've already download all the requirements first to prepare.
But, I could not run the "MTK CLIENT TOOL V5.2".
It was just nothing appear when I double click the application.
I use Windows 11. Did it caused by the Windows?
Other question is what step is the boot.img file needed?
Click to expand...
Click to collapse
Get it from the rom file ( link is provided in replies) and patch it yourself from magisk manager , or you can get the patched boot.img file ( link in replies, too) and continue these steps as nothing happened
fb.hikmawan said:
Thank you for creating the thread @Zezo 089 , I am using Oppo A5s and now I found a way to root the phone.
I've already download all the requirements first to prepare.
But, I could not run the "MTK CLIENT TOOL V5.2".
It was just nothing appear when I double click the application.
I use Windows 11. Did it caused by the Windows?
Other question is what step is the boot.img file needed?
Click to expand...
Click to collapse
Also , try to open this program in windows 10
Because it did these steps using windows 10 , not 11
bro this guide is so long and boring and not safe
the best way to root this phone is through mtk client (github)
with that tool you can
1.backup the whole firmware in case of an error or a malfunction
2. unlock bootloader of any mediatek phone including oppo a5s
3. rooting this device without any risk
4. you can flash any partition if something happened within this tool without the use of SP Flash tool
the link: https://github.com/bkerler/mtkclient
Khalyl22 said:
bro this guide is so long and boring and not safe
the best way to root this phone is through mtk client (github)
with that tool you can
1.backup the whole firmware in case of an error or a malfunction
2. unlock bootloader of any mediatek phone including oppo a5s
3. rooting this device without any risk
4. you can flash any partition if something happened within this tool without the use of SP Flash tool
the link: https://github.com/bkerler/mtkclient
Click to expand...
Click to collapse
Bro
I made this guide with all of its details to help advanced people , especially The Beginners
+ Bro, i concerned using MTK Client Tool to unlock bootloader , Warned people to backup the WHOLE DATA and flash the boot.img after patching (using SP flash tool)
But it is also a good point to flash any partitions if a brick happened or something else using SP flash tool
Khalyl22 said:
bro this guide is so long and boring and not safe
the best way to root this phone is through mtk client (github)
with that tool you can
1.backup the whole firmware in case of an error or a malfunction
2. unlock bootloader of any mediatek phone including oppo a5s
3. rooting this device without any risk
4. you can flash any partition if something happened within this tool without the use of SP Flash tool
the link: https://github.com/bkerler/mtkclient
Click to expand...
Click to collapse
NOTE THAT I WARNED PEOPLE BEFORE DOING THIS
Khalyl22 said:
bro this guide is so long and boring and not safe
the best way to root this phone is through mtk client (github)
with that tool you can
1.backup the whole firmware in case of an error or a malfunction
2. unlock bootloader of any mediatek phone including oppo a5s
3. rooting this device without any risk
4. you can flash any partition if something happened within this tool without the use of SP Flash tool
the link: https://github.com/bkerler/mtkclient
Click to expand...
Click to collapse
+ Why tf they backup the rom ?
as they can download the Flashable Official rom , and flash it using SP FLASH TOOL ( consider that you should untick preloader before flashing to avoid bricking your device)
Khalyl22 said:
bro this guide is so long and boring and not safe
the best way to root this phone is through mtk client (github)
with that tool you can
1.backup the whole firmware in case of an error or a malfunction
2. unlock bootloader of any mediatek phone including oppo a5s
3. rooting this device without any risk
4. you can flash any partition if something happened within this tool without the use of SP Flash tool
the link: https://github.com/bkerler/mtkclient
Click to expand...
Click to collapse
@Anonymous V What are your comments about that ?
Zezo 089 said:
@Anonymous V What are your comments about that ?
Click to expand...
Click to collapse
actually he is just saying about what can you do using the MTK client tool not "what to do about it " and i dont know if he really read your tutorial because this guy " @Khalyl22 "
sounds that he just wants to sounds smart and also boring? i dont know why he said that but its better to give a long and detailed tutorial to give people more info and understanding about what to do to avoid error and to give comfort to people while doing it and i dont fcking know why he said that its not safe although you give all the necessary steps to avoid error while doing it including the warning " Please Backup you Phone before Doing This " and also i think his not aware about the MTK client Gui version which you used in your tutorial i recommend the Gui version for the people who cant handle the terminal version because they are afraid in getting error i think he is pointing about the MTK client terminal version which i often used, also bro there is a reason why he said backup your whole firmware before doing it and actually his right about that when you backup your whole firmware in your phone you can backup all the data,apps,system preferences,imei and other things which you can restore if the phone fcked up where as the stock flashable rom is different its because its already set by default or factory default by the manufacturer which means its back to old state when you bought the phone well it depends though if you dont care about the data in your phone you can just reflash the stock flashable rom and if you care about the data in your phone you can backup your phones firmware and use that later to restore your phone.
Mine doesn't want to let me enter in BROM mode, I can only hear a plug and unplug loop sound when I try to hold Vol UP + Vol down.
Related
Hi, I have a Huawei Mate 10 pro BLA-L29 C432 with unlocked bootloader frp unlocked that is hard bricked.
Reason why it was hard bricked was using HWota and flashing the wrong files
The device shows up in device manager as USB COM 1.0 (COM4) along with COMMUNICATIONS PORT (COM 1).
I have purchased the DC Phoneix + HCU timed license for 3 days ending on 3/4/2019 at 9 AM.
I have downloaded the "BLA-AL00B_1.0.0.35_Board_Software_China_Nonspecific_An droid_8.0.0_EMUI_8.0.0_05022FPT.dgtks" board firmware directly from DC Phoenix
I have also downloaded the "BLA-L29C_8.0.0.115(C432)_Firmware_Lithuania_Latvia_Norway_Romania_Hungary_Greece_Austria_Czech_Republic_Bulgaria_Poland_Slovenia_Croatia_Serbia_Nonspecific.app" appfile directly from DC Phoenix
I begin by selecting the "BLA-AL00B_1.0.0.35_Board_Software_China_Nonspecific_An droid_8.0.0_EMUI_8.0.0_05022FPT" file in the update file selection. Then i select the "BLA-L29C_8.0.0.115(C432)_Firmware_Lithuania_Latvia_Norway_Romania_Hungary_Greece_Austria_Czech_Republic_Bulgaria_Poland_Slovenia_Croatia_Serbia_Nonspecific.app" file in the update app file selection.
I click update and am provided with the following error message to the left of the screen
File to update: BLA-AL00B_1.0.0.35_Board_Software_China_Nonspecific_An droid_8.0.0_EMUI_8.0.0_05022FPT.dgtks
Device detected:
COM4: HUAWEI USB COM 1.0 (COM4)
Writing bootloader...
Writing BLA-AL00B_1.0.0.35_Board_Software_China_Nonspecific_An droid_8.0.0_EMUI_8.0.0_05022FPT_3.dtwork...
Error writing Bootloader
3/1/2019 1:09:05 PM Writing device finished - INCOMPLETE
I then proceeded to try the "use bootloader" option under the udpate oeminfo tab and chosen the Kiring970_T2_A8.0_V3
and i have successfully gotten my device to be recognized as follows
Looking for a device in fastboot mode
Device found: AQH7N17B29009368
SN:AQ********************* <- i have censored the following information intentionally
IMEI:866******************* <- i have censored the following information intentionally
IMEI1:86******************* <- i have censored the following information intentionally
MEID:A******************** <- i have censored the following information intentionally
Build number: :BLA-L29 8.0.0.158(C432)
Model: BLA-L29
Battery state: 0
When writing the board file, I get the following
Erasing nvme partition
ERASE partition nvme : FAIL failed to erase partition
Device with unsupported security patch
3/2/2019 11:47:18 AM Writing device finished OK
when writing the update.app file directly from dc-phoenix i get the following error
Extracting partition XLOADER...
Writing XLOADER partition
XLOADER partition UPDATE :FAIL download elf_xloader image verification error
Device with unsupported security patch
3/2/2019 12:02:09 PM Writing device finished - INCOMPLETE
i then though, okay let me try another more rescent .app file, so i downloaded the 8.0.0.158 BLA-L29 c432 "update.zip" file from the internet. I extracted the "UPDATE.APP" file and then selected it in DC-Phoneix and now i get the following message
Attention, this is OTA type file and can't be written via software. Writing it via fastboot may damage the phone. Please use files from our support area.
so I select no, because of this error. I chose to download more "update.zip" files from the internet, and they all give me this attention message.
i then proceeded to use huawei extractor tool to extract kernel,ramdisk,recovery_ramdisk, recovery_vbmeta, and recovery_vendor. I flashed them through fastboot successfully, but no life from the device. As a matter of fact, when i disconnect the device, I have to start from scratch again.
I am really running out of ideas here. =(
Chito307 said:
Hi, I have a Huawei Mate 10 pro BLA-L29 C432 with unlocked bootloader frp unlocked that is hard bricked.
Reason why it was hard bricked was using HWota and flashing the wrong files
The device shows up in device manager as USB COM 1.0 (COM4) along with COMMUNICATIONS PORT (COM 1).
I have purchased the DC Phoneix + HCU timed license for 3 days ending on 3/4/2019 at 9 AM.
I have downloaded the "BLA-AL00B_1.0.0.35_Board_Software_China_Nonspecific_An droid_8.0.0_EMUI_8.0.0_05022FPT.dgtks" board firmware directly from DC Phoenix
I have also downloaded the "BLA-L29C_8.0.0.115(C432)_Firmware_Lithuania_Latvia_Norway_Romania_Hungary_Greece_Austria_Czech_Republic_Bulgaria_Poland_Slovenia_Croatia_Serbia_Nonspecific.app" appfile directly from DC Phoenix
I begin by selecting the "BLA-AL00B_1.0.0.35_Board_Software_China_Nonspecific_An droid_8.0.0_EMUI_8.0.0_05022FPT" file in the update file selection. Then i select the "BLA-L29C_8.0.0.115(C432)_Firmware_Lithuania_Latvia_Norway_Romania_Hungary_Greece_Austria_Czech_Republic_Bulgaria_Poland_Slovenia_Croatia_Serbia_Nonspecific.app" file in the update app file selection.
I click update and am provided with the following error message to the left of the screen
File to update: BLA-AL00B_1.0.0.35_Board_Software_China_Nonspecific_An droid_8.0.0_EMUI_8.0.0_05022FPT.dgtks
Device detected:
COM4: HUAWEI USB COM 1.0 (COM4)
Writing bootloader...
Writing BLA-AL00B_1.0.0.35_Board_Software_China_Nonspecific_An droid_8.0.0_EMUI_8.0.0_05022FPT_3.dtwork...
Error writing Bootloader
3/1/2019 1:09:05 PM Writing device finished - INCOMPLETE
I then proceeded to try the "use bootloader" option under the udpate oeminfo tab and chosen the Kiring970_T2_A8.0_V3
and i have successfully gotten my device to be recognized as follows
Looking for a device in fastboot mode
Device found: AQH7N17B29009368
SN:AQ********************* <- i have censored the following information intentionally
IMEI:866******************* <- i have censored the following information intentionally
IMEI1:86******************* <- i have censored the following information intentionally
MEID:A******************** <- i have censored the following information intentionally
Build number: :BLA-L29 8.0.0.158(C432)
Model: BLA-L29
Battery state: 0
When writing the board file, I get the following
Erasing nvme partition
ERASE partition nvme : FAIL failed to erase partition
Device with unsupported security patch
3/2/2019 11:47:18 AM Writing device finished OK
when writing the update.app file directly from dc-phoenix i get the following error
Extracting partition XLOADER...
Writing XLOADER partition
XLOADER partition UPDATE :FAIL download elf_xloader image verification error
Device with unsupported security patch
3/2/2019 12:02:09 PM Writing device finished - INCOMPLETE
i then though, okay let me try another more rescent .app file, so i downloaded the 8.0.0.158 BLA-L29 c432 "update.zip" file from the internet. I extracted the "UPDATE.APP" file and then selected it in DC-Phoneix and now i get the following message
Attention, this is OTA type file and can't be written via software. Writing it via fastboot may damage the phone. Please use files from our support area.
so I select no, because of this error. I chose to download more "update.zip" files from the internet, and they all give me this attention message.
i then proceeded to use huawei extractor tool to extract kernel,ramdisk,recovery_ramdisk, recovery_vbmeta, and recovery_vendor. I flashed them through fastboot successfully, but no life from the device. As a matter of fact, when i disconnect the device, I have to start from scratch again.
I am really running out of ideas here. =(
Click to expand...
Click to collapse
sorry bro i never ran into situation like this
only pray for you
Anyone? =(
Chito307 said:
Anyone? =(
Click to expand...
Click to collapse
you already done what may be possible to recover
huawei can do it if it is in warranty
It's seems that the error is right there , the security patch isn't supported so it won't finish writing the files, it is stated in DC locker that some devices like mate 10 pro and newer devices are not supported the same reason why there are no new unlocked codes for bootloader on DC unlock and no new unlocked codes for sim also, have your tried flashing those files yourself through fastboot method ? With out the hcu from DC
?
I had same problème
Now phone is OK but IMEI 000000000000
This worked for me, it requires IDT and unencrypted board firmware (these are usually paid). dtgks might work if you only flash board firmware, but you have to be careful so it doesn't wipe oeminfo (if you still want to unlock after. You can still get unlock code through HCU on board firmware so it doesn't really matter).
Edit xml that comes with unencrypted board so it doesn't erase oeminfo.
Flash bootloader files with DC, phone is put in fastboot mode.
Open up IDT.
Select xml in both settings of IDT and in settings of USBMAP. In USBMAP, select com port in the list and click on Skip.
Now start flashing using IDT.
When flashing is done phone will boot to board firmware.
When on board firmware, follow this guide to get your imeis and that stuff back:
1)Flash board (already done)
2)Flash oeminfo from fastboot (own backup if available, if you edited xml you will still have your own oeminfo flashed)
3) Dump modemnvm_system, modemnvm_factory and modemnvm_backup partitions using dd and adb shell ('dd if=/dev/block/bootdevice/by-name/modemnvm_system of=/sdcard/modemnvm_system.img' and so on), board firmware has global root so you don't need to flash Magisk or anything like that (which is impossible anyway, board fw will only accept board or stock images)
4)Flash dumped modemnvm_system, modemnvm_factory and modemnvm_backup using fastboot
5)Modify and brand with HCU (check all checkboxes except the last 2, fill in any missing info)
6)Unlock Sim network with HCU
7)If you previously used HCU to get unlock code you need to generate it again (HCU patches oeminfo so their unlock code works). Also if you forgot to edit xml you'd have to generate a new code, your old code will not work if oeminfo was wiped.
8)Use dload with Service Firmware from androidhost.ru, regular update.zip does not work in dload mode.
And make sure the firmware you dload is newer than GPU Turbo firmware. (XLOADER needs to be 02, else you brick again)
Please note that you only have one shot at this... If you, for example, flash dload but forget to generate unlock code and don't have your own oeminfo flashed you will not be able to repair device without opening it up to get testpoint.
ante0 said:
it requires IDT
Click to expand...
Click to collapse
What is IDT ?
badmania98 said:
What is IDT ?
Click to expand...
Click to collapse
Image Download Tool, some leaked tool (like Odin for Samsung).
It's available on androidhost.ru iirc
I need dload with Service Firmware please
I flashed with many firmware no seccess
ante0 said:
This worked for me, it requires IDT and unencrypted board firmware (these are usually paid). dtgks might work if you only flash board firmware, but you have to be careful so it doesn't wipe oeminfo (if you still want to unlock after. You can still get unlock code through HCU on board firmware so it doesn't really matter).
Edit xml that comes with unencrypted board so it doesn't erase oeminfo.
Flash bootloader files with DC, phone is put in fastboot mode.
Open up IDT.
Select xml in both settings of IDT and in settings of USBMAP. In USBMAP, select com port in the list and click on Skip.
Now start flashing using IDT.
When flashing is done phone will boot to board firmware.
When on board firmware, follow this guide to get your imeis and that stuff back:
1)Flash board (already done)
2)Flash oeminfo from fastboot (own backup if available, if you edited xml you will still have your own oeminfo flashed)
3) Dump modemnvm_system, modemnvm_factory and modemnvm_backup partitions using dd and adb shell ('dd if=/dev/block/bootdevice/by-name/modemnvm_system of=/sdcard/modemnvm_system.img' and so on), board firmware has global root so you don't need to flash Magisk or anything like that (which is impossible anyway, board fw will only accept board or stock images)
4)Flash dumped modemnvm_system, modemnvm_factory and modemnvm_backup using fastboot
5)Modify and brand with HCU (check all checkboxes except the last 2, fill in any missing info)
6)Unlock Sim network with HCU
7)If you previously used HCU to get unlock code you need to generate it again (HCU patches oeminfo so their unlock code works). Also if you forgot to edit xml you'd have to generate a new code, your old code will not work if oeminfo was wiped.
8)Use dload with Service Firmware from androidhost.ru, regular update.zip does not work in dload mode.
And make sure the firmware you dload is newer than GPU Turbo firmware. (XLOADER needs to be 02, else you brick again)
Please note that you only have one shot at this... If you, for example, flash dload but forget to generate unlock code and don't have your own oeminfo flashed you will not be able to repair device without opening it up to get testpoint.
Click to expand...
Click to collapse
Hello
I do every thing on the tuto but i have 1 problem
I have no network it still no service
hello please advice! How do I unlock the bootloader at this point and do root with magisk? please describe step by step instructions or link to instructions. sorry because this thread must be here, but I didn't find anything current. I think it's better to get advice than to do wrong and then look for how to restore your phone from a broken state.
my build: Andoid 8.0.0 Emui 8.0.0 PRA-LX1 8.0.0.401 (C432)
Phone locked, FRP unlocked
Thank you very much
niki.rsb said:
hello please advice! How do I unlock the bootloader at this point and do root with magisk? please describe step by step instructions or link to instructions. sorry because this thread must be here, but I didn't find anything current. I think it's better to get advice than to do wrong and then look for how to restore your phone from a broken state.
my build: Andoid 8.0.0 Emui 8.0.0 PRA-LX1 8.0.0.401 (C432)
Phone locked, FRP unlocked
Thank you very much
Click to expand...
Click to collapse
Huawei doesn't unlock bootloader's any more.
You'll have to find a pay service that supports your model.
Sent from my HD1907 using Tapatalk
@niki.rsb
In order to root device's Android unlocking device's boot-loader isn't a pre-requisite.
Rooting a phone's Android means giving user and/or applications administrative rights, will say unrestricted access to Android's system files.
jwoegerbauer said:
@niki.rsb
In order to root device's Android unlocking device's boot-loader isn't a pre-requisite.
Rooting a phone's Android means giving user and/or applications administrative rights, will say unrestricted access to Android's system files.
Click to expand...
Click to collapse
Wrong... you can't flash a patched boot.img without an unlocked bootloader
the only way to root the device is with a Magisk_patched boot.img
clsA said:
Wrong... you can't flash a patched boot.img without an unlocked bootloader
the only way to root the device is with a Magisk_patched boot.img
Click to expand...
Click to collapse
You should carefully read instead of replying nonsense.
I don't understand English well. I don't understand it now. I think everyone writes something different. i need root via magisk to be able to connect google pay with credit card. so the bootloader only goes through the paid service? and then proceed to root?
niki.rsb said:
I don't understand English well. I don't understand it now. I think everyone writes something different. i need root via magisk to be able to connect google pay with credit card. so the bootloader only goes through the paid service? and then proceed to root?
Click to expand...
Click to collapse
You can only unlock bootloader with a paid service.
Once the bootloader is unlocked you can use magisk and patch and then flash a rooted boot.img
Instructions for making the patched boot.img are here > https://topjohnwu.github.io/Magisk/install.html
you get the correct stock boot.img from a full firmware update.zip for your version
Bootloader Unlock Instructions found here > https://techelucid.com/unlock-bootloader-huawei/
Pre-Requisites for unlocking bootloader
Enable USB Debugging
Install USB Drivers for Huawei 98 Lite:
USB Debugging:
Goto Settings> About Phone Tap 7 Times on Build Number
Then In Settings>Developer Options and enable USB Debugging
Tick The “Oem Unlock” Checkbox
Download the following things for Huawei Device
Get and Install USB Drivers on your computer from here
Download DC Huawei Bootloader Codes from here.
Get DC Unlocker client app from here.
Buy Dc Unlocker Credit With Android App
Download and install “DC Huawei Bootloader Codes Android app“ from the link given above in downloads section.
Open the downloaded apk file and install it on your device.
Click on DC Unlocker Account.
Type your email id and complete the payment processes.
After successful payment; save the user password. You will need this while using DC unlocker pc app.
Get Huawei Bootloader Unlock Code With Dc Unlocker
Extract the downloaded DC Unlocker client app zip file.
Double click or Run dc-unlocker2client.exe.
Move to the server tab and log in. use the user password which you got in DC Huawei Bootloader Codes Android app.
Connect your device to pc and enable Manufacturer Mode (You can easily enable manufacturer mode by Typing *#*#2846579#*#* in the dial pad. After that click on Background settings > USB port settings > Manufacturer Mode).
Select the Manufacturer type “Huawei Phones” Model “Auto Detect”. After that click on the search button.
Click on Unlocking Tab. After that choose Read Bootloader Code.
Wait for some time to Unlock code to arrive. When it does, copy the data and save it in a notepad file.
Last step to Unlock Bootloader
Turn off your device.
Put it in Fastboot mode by pressing Volume down + Power button at the same time.
Connect your device to a PC with the USB cable.
Enter The Unlock Code In Code In Command prompt Window and press Enter.
Wait for a few seconds and your device will restart.
You can now go ahead and customize your device by installing TWRP or then flash SuperSu Magisk to root it. So you have succeeded to unlock your Huawei bootloader. .
Click to expand...
Click to collapse
with the bootloader unlocked you don't actually need TWRP
you can fastboot flash the patch_boot.img
just use the command
fastboot flash boot patched_boot.img
thank you for the instructions. But unfortunately the bootloader is still locked. I followed the instructions. it wrote me the bootloader number. But when I opened the command line and wrote the number, then nothing did. where should i open the dashboard? classic C: \ Windows \ system32>?
I will also provide a transcript of the dc unlocker
Check account status
User: bl21816
Credits left: 4
Activated features:
Software debugger
=============================================== ================
Before detection Huawei Android phones, enable 'Manufacture' mode:
in dial pad type * # * # 2846579 # * # * for Qualcomm and Kirin based models, or * # * # 14789632 # * # * for MTK, then select
'ProjectMenu',
'Background settings',
'USB ports settings',
'Manufacture mode'.
Step by step guide for other Huawei phone unlock:
https://www.dc-unlocker.com/huawei_phones_detect_unlock_tutorials
=============================================== ================
DC - Unlocker 2 Client 1.00.1431
Detecting phone:
selection:
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Applications port COM7
=============================================== ================
Check account status
User: bl21816
Credits left: 4
Activated features:
Software debugger
Unlock Auto detect (recommended) cost 4 Cr
Service text tutorial: https://www.dc-unlocker.com/huawei-android-hisilicon-unlock-guide
=============================================== ================
=============================================== ================
DC - Unlocker 2 Client 1.00.1431
Detecting phone:
selection:
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Applications port COM7
=============================================== ================
Reading bootloader code ...
Bootloader code: 9x9x2x2x2x8x5x3x
=============================================== ================
=============================================== ================
DC - Unlocker 2 Client 1.00.1431
Detecting phone:
selection:
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Phone: PRA-LX1
Model: Huawei phone in fastboot mode
IMEI: 866386030063396
Serial NR. : 9DC7N17728006152
Firmware: PRA-LX1 8.0.0.401 (C432
IMEI1: 866386030090407
FB LockState: LOCKED
USER LockState: LOCKED
locked
Battery state: 4068mv
=============================================== ================
Check account status
User: bl21816
Credits left: 0
Activated features:
Software debugger
Unlock Huawei phone in fastboot mode (866386030063396) cost 15 cr
Server message:
Check prices at: https://www.dc-unlocker.com/buy/user_prices
Insufficient credits!
=============================================== ================
niki.rsb said:
i need root via magisk to be able to connect google pay with credit card. so the bootloader only goes through the paid service? and then proceed to root?
Click to expand...
Click to collapse
Right after you root Android OS, Google Pay will stop working. How to bypass this in detail is explained here.
Again:
It's a misconception if people like you think the bootloader of a device has to be unlocked in order to root device's Android OS. These people just don't know what role the bootloader has, just don't know what rooting Android OS means.
niki.rsb said:
I will also provide a transcript of the dc unlocker
Check account status
User: bl21816
Credits left: 4
Activated features:
Software debugger
=============================================== ================
Before detection Huawei Android phones, enable 'Manufacture' mode:
in dial pad type * # * # 2846579 # * # * for Qualcomm and Kirin based models, or * # * # 14789632 # * # * for MTK, then select
'ProjectMenu',
'Background settings',
'USB ports settings',
'Manufacture mode'.
Step by step guide for other Huawei phone unlock:
https://www.dc-unlocker.com/huawei_phones_detect_unlock_tutorials
=============================================== ================
DC - Unlocker 2 Client 1.00.1431
Detecting phone:
selection:
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Applications port COM7
=============================================== ================
Check account status
User: bl21816
Credits left: 4
Activated features:
Software debugger
Unlock Auto detect (recommended) cost 4 Cr
Service text tutorial: https://www.dc-unlocker.com/huawei-android-hisilicon-unlock-guide
=============================================== ================
=============================================== ================
DC - Unlocker 2 Client 1.00.1431
Detecting phone:
selection:
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Applications port COM7
=============================================== ================
Reading bootloader code ...
Bootloader code: 9x9x2x2x2x8x5x3x
=============================================== ================
=============================================== ================
DC - Unlocker 2 Client 1.00.1431
Detecting phone:
selection:
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Phone: PRA-LX1
Model: Huawei phone in fastboot mode
IMEI: 866386030063396
Serial NR. : 9DC7N17728006152
Firmware: PRA-LX1 8.0.0.401 (C432
IMEI1: 866386030090407
FB LockState: LOCKED
USER LockState: LOCKED
locked
Battery state: 4068mv
=============================================== ================
Check account status
User: bl21816
Credits left: 0
Activated features:
Software debugger
Unlock Huawei phone in fastboot mode (866386030063396) cost 15 cr
Server message:
Check prices at: https://www.dc-unlocker.com/buy/user_prices
Insufficient credits!
=============================================== ================
Click to expand...
Click to collapse
Simply getting the code isn't enough you have to flash it see below and see the tutorial for dc unlocker here > https://forum.xda-developers.com/honor-7x/how-to/how-to-unlock-huawei-bootloader-removal-t3780903
Using your Unlock Code:
1. Turn off your phone, Boot your device into Fastboot mode with Vol down and power button.
2. CD to where you downloaded ADB/Fastboot Tools
Run these commands when inside ADB tools directory
a) fastboot devices. (your device should bee listed. If not reinstall drivers/reboot)
b) fastboot oem get-bootinfo (just to confirm everything is detected correctly
c) fastboot oem unlock 9x9x2x2x2x8x5x3x
3. Acknowledge the prompt on your phone. Device will be WIPED!
4. Once the wipe finishes it will take several minutes for phone to boot up. Do not panic. Once you See Huawei logo you are OK!
Click to expand...
Click to collapse
Note: I just read that whole thread (below) and the tutorial is out of date.
it's much easier to root now using the magisk patched_boot.img
see my post earlier on how it's done
instructions for unlocking and rooting your phone here > https://forum.xda-developers.com/p8lite/general/guide-unlock-bootloader-root-device-t3977067
He even has a free method to get the bootloader unlock code (Seems you already have yours above)
Other useful links I found during my search
HiSuite 5.0.2.300 - https://androidmtk.com/download-huawei-hisuite
Multi-Tool for Huawei - https://pro-teammt.ru/multi-tool-for-huawei-honor/
Firmware Database > https://pro-teammt.ru/en/online-firmware-database-ru/
Huawei update extractor > https://firmwarecare.com/huawei-update-extractor-v0-9-9-5
How to extract Huawei firmware and its UPDATE.APP > https://nerdschalk.com/extract-huawei-firmware-update-app/
jwoegerbauer said:
Right after you root Android OS, Google Pay will stop working. How to bypass this in detail is explained here.
Again:
It's a misconception if people like you think the bootloader of a device has to be unlocked in order to root device's Android OS. These people just don't know what role the bootloader has, just don't know what rooting Android OS means.
Click to expand...
Click to collapse
Yes you're right. I don't know exactly how it works and I don't understand it. But that's why I turned here and ask for advice on how to proceed. If I had knowledge, I wouldn't bother anyone to help me. I don't think this is anything new.
clsA said:
Simply getting the code isn't enough you have to flash it see below and see the tutorial for dc unlocker here > https://forum.xda-developers.com/honor-7x/how-to/how-to-unlock-huawei-bootloader-removal-t3780903
Note: I just read that whole thread (below) and the tutorial is out of date.
it's much easier to root now using the magisk patched_boot.img
see my post earlier on how it's done
instructions for unlocking and rooting your phone here > https://forum.xda-developers.com/p8lite/general/guide-unlock-bootloader-root-device-t3977067
He even has a free method to get the bootloader unlock code (Seems you already have yours above)
Other useful links I found during my search
HiSuite 5.0.2.300 - https://androidmtk.com/download-huawei-hisuite
Multi-Tool for Huawei - https://pro-teammt.ru/multi-tool-for-huawei-honor/
Firmware Database > https://pro-teammt.ru/en/online-firmware-database-ru/
Huawei update extractor > https://firmwarecare.com/huawei-update-extractor-v0-9-9-5
How to extract Huawei firmware and its UPDATE.APP > https://nerdschalk.com/extract-huawei-firmware-update-app/
Click to expand...
Click to collapse
Yes there are a lot of versions and procedures for how to root them on the internet. Some don't work, others worked, but currently they don't either. Or there may be new better practices. For a person who does not have much knowledge, it is very difficult to choose the right one. If what you are saying is new and mainly functional, I will look and try to proceed
niki.rsb said:
Yes there are a lot of versions and procedures for how to root them on the internet. Some don't work, others worked, but currently they don't either. Or there may be new better practices. For a person who does not have much knowledge, it is very difficult to choose the right one. If what you are saying is new and mainly functional, I will look and try to proceed
Click to expand...
Click to collapse
first just get the bootloader unlocked
I'll show you how to extract and create a rooted boot.img
clsA said:
first just get the bootloader unlocked
I'll show you how to extract and create a rooted boot.img
Click to expand...
Click to collapse
I have the bootloader unlocked. Is it now necessary to install twrp for magisk? and how do you please proceed?
niki.rsb said:
I have the bootloader unlocked. Is it now necessary to install twrp for magisk? and how do you please proceed?
Click to expand...
Click to collapse
Excellent !!
We need your firmware version to get the correct ramdisk.img
look in settings / about phone for the firmware version or just post a screen shot of that screen
this is your file (I got it from your first post) > PRA-LX1 8.0.0.401 (C432) FullOTA-MF > https://pro-teammt.ru/en/online-fir...mware_model=PRA-LX1+8.0.0.401&firmware_page=0
download the update.zip (I'm downloading it also)
Next download the Huawei update extractor > https://firmwarecare.com/huawei-update-extractor-v0-9-9-5
I posted the guide here for using the extraction tool > https://nerdschalk.com/extract-huawei-firmware-update-app/
and then follow this guide to root the ramdisk.img
Huawei
Huawei devices using Kirin processors have a different partitioning method from most common devices. Magisk is usually installed to the boot partition of the device, however Huawei devices do not have this partition. Depending on what EMUI version your device is running, the instructions will be slightly different.
Obtain Stock Images
Huawei does not release official factory images, however most firmware zips can be downloaded from the Huawei Firmware Database. To extract images from UPDATE.APP in the zip, you have to use Huawei Update Extractor (Windows only!)
EMUI 8
For EMUI 8 devices, your device has a partition named ramdisk, which is where Magisk is going to be installed.
If you plan to use custom recoveries, simply follow the instructions for custom recovery and you’re all set.
If you plan not to use custom recoveries, you will have to extract RAMDISK.img from your firmware. Follow the instructions for boot image patching above, but use the RAMDISK.img file instead of a boot image.
To flash the patched image to your device, here is the fastboot command:
fastboot flash ramdisk /path/to/magisk_patched.img
Be aware you are flashing to ramdisk, not boot!
Click to expand...
Click to collapse
Boot Image Patching
You would want to choose this method if either your device does not have custom recoveries, your device is A/B and you don’t want to mix recovery and boot images, or your device is using system-as-root without A/B partitions.
To use this method, you are required to obtain a copy of the stock RAMDISK.img, which can be found by extracting OEM provided factory images or extracting from OTA update zips. If you are unable to obtain one yourself, you might be able to find it somewhere on the internet. The following instructions will guide you through the process after you have the copy of boot/recovery image.
Copy the RAMDISK.img to your device
Download and install the latest Magisk Manager
If you are patching a recovery image, manually check “Recovery Mode” in Advanced Settings!
Press Install → Install → Select and Patch a File, and select your stock RAMDISK.img file
Magisk Manager will patch the image, and store it in [Internal Storage]/Download/magisk_patched.img
Copy the patched image from your device to your PC. If you can’t find it via MTP, you can pull the file with ADB:
adb pull /sdcard/Download/magisk_patched.img
Flash the patched RAMDISK.img to your device and reboot. For most devices, here is the fastboot command:
fastboot flash ramdisk magisk_patched.img
fastboot flash boot /path/to/magisk_patched.img or
fastboot flash recovery /path/to/magisk_patched.img if you are patching a recovery image
Click to expand...
Click to collapse
now use fastboot reboot
at this point your phone should be rooted
I uploaded the patched ramdisk.img here if you have trouble > https://www.androidfilehost.com/?fid=8889791610682890848
the unpatched RAMDISK.IMG is also their > https://www.androidfilehost.com/?w=files&flid=314978
You also have TWRP 3.11 available for your phone > https://androidfilehost.com/?fid=1899786940962602140
it's ease to flash TWRP and then root your phone with a Magisk.zip in TWRP
it's also nice if you like to flash roms or make backups of your system and data
clsA said:
this is your file (I got it from your first post) > PRA-LX1 8.0.0.401 (C432) FullOTA-MF > https://pro-teammt.ru/en/online-fir...mware_model=PRA-LX1+8.0.0.401&firmware_page=0
download the update.zip (I'm downloading it also)
Click to expand...
Click to collapse
I did not find a download file or a link where I can download, so I download here
https://androidhost.ru/1iXE is it ok?
yes build number is PRA-LX1 8.0.0.401 (C432) Emui 8, Android 8
And what is the difference between when I run through that ramdisk.img or when I make a flash twrp and install magisk.zip??
niki.rsb said:
I did not find a download file or a link where I can download, so I download here
https://androidhost.ru/1iXE is it ok?
yes build number is PRA-LX1 8.0.0.401 (C432) Emui 8, Android 8
And what is the difference between when I run through that ramdisk.img or when I make a flash twrp and install magisk.zip??
Click to expand...
Click to collapse
I posted the patched ramdisk.img for you
all you need to do is copy it to your adb/fastboot folder and reboot your phone to fastboot mode and flash it
fastboot flash ramdisk magisk_patched.img
their is no difference in the end result, either method will work to Root your phone
clsA said:
I posted the patched ramdisk.img for you
all you need to do is copy it to your adb/fastboot folder and reboot your phone to fastboot mode and flash it
fastboot flash ramdisk magisk_patched.img
their is no difference in the end result, either method will work to Root your phone
Click to expand...
Click to collapse
I did exactly and just what you wrote. the flash completed without error, but I don't know what the result should have been. I don't even have root, magisk, I didn't know the change.
niki.rsb said:
I did exactly and just what you wrote. the flash completed without error, but I don't know what the result should have been. I don't even have root, magisk, I didn't know the change.
Click to expand...
Click to collapse
Install magisk manager if it's not in your app drawer
Select Format all + Download in SP tool and flash my phone. Now my phone ............
{
"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"
}
Sâdíqûlllah said:
Select Format all + Download in SP tool and flash my phone. Now my phone ............
View attachment 5582549View attachment 5582551View attachment 5582553
Click to expand...
Click to collapse
Bruh say rip to your phone cause you done format all
It's never gonna boot now or by chance if it does you have already lose your IMEI so you can't able to use internet and service better go service centre and ask for a new phone to them xD
iamshubh69 said:
Bruh say rip to your phone cause you done format all
It's never gonna boot now or by chance if it does you have already lose your IMEI so you can't able to use internet and service better go service centre and ask for a new phone to them xD
Click to expand...
Click to collapse
bro is there any way to make it work
I have the same problem with my realme c21
also, I did format all
please say buy a new phone
Zartazor said:
bro is there any way to make it work
I have the same problem with my realme c21
also, I did format all
please say buy a new phone
Click to expand...
Click to collapse
Buy iPhone 13 pro max or samsung s22 plus
iamshubh69 said:
Buy iPhone 13 pro max or samsung s22 plus
Click to expand...
Click to collapse
Sorry my mistake
"please don't say buy a new phone"
By the way I have fixed it
Locked bootloader won't allow some partitions to be flashed
So I unlocked the bootloader and flashed again
And it worked
Zartazor said:
Sorry my mistake
"please don't say buy a new phone"
By the way I have fixed it
Locked bootloader won't allow some partitions to be flashed
So I unlocked the bootloader and flashed again
And it worked
Click to expand...
Click to collapse
please help me
Sâdíqûlllah said:
please help me
Click to expand...
Click to collapse
Use mtk client to unlock the bootloader
Then try to flash that again
Mtk client link:
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
Zartazor said:
Use mtk client to unlock the bootloader
Then try to flash that again
Mtk client link:
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
Click to expand...
Click to collapse
How to fix download not complete please press volume..............
Sâdíqûlllah said:
How to fix download not complete please press volume...........
Click to expand...
Click to collapse
To start this process you need to install python and mtk driver first
1. Download the zip file I gave you
2. Extract it
3. Force shutdown phone by pressing all three buttons together
4. Open the file you extracted in pc
5. Type cmd in address bar
6. Type python mtk_gui and hit enter
7. Hold volume up and down and plug it to your pc
8. When it shows all of your partitions, click on Flash Tools
9. click on Unlock bootloader
10. Now flash it again with SP Flash Tool
I am facing the same problem, I managed to flash everything (even super.img xD) through MTKClient + SP Flash Tool, but I still have the message with no signs of recovery/fastboot/booting past the logo.
Can you walk me through what you did please? starting with the exact firmware you used?
mouradsme said:
I am facing the same problem, I managed to flash everything (even super.img xD) through MTKClient + SP Flash Tool, but I still have the message with no signs of recovery/fastboot/booting past the logo.
Can you walk me through what you did please? starting with the exact firmware you used?
Click to expand...
Click to collapse
.
Sâdíqûlllah said:
Select Format all + Download in SP tool and flash my phone. Now my phone ............
View attachment 5582549View attachment 5582551View attachment 5582553
Click to expand...
Click to collapse
Help me, i also haved done this format all + downlod but now i cant flash anymore and right now my phone is nothing no vibration and etc just a blackscreen and i dont know what to do because i cant even flash and it gets errored whenever i flash it stucks at red bar DA 100% in spflashtool PLEASE SOMEONE HELP ME
My phone is Realme Narzo 20 (7iEU)
Please Help i will never buy Realme
Edit Scatter File
partition_name: oppo_custom
file_name: oppo_custom.img
is_download: true
Use Mtk Auth Bypass Tool > Disable Auth
Flash with SP Flash Tool without opporeserve2, oppo_custom, cdt_engineering, special_preload and my_custom
Use Mtk Client > mtk_gui > unlock bootloader
Use Mtk Auth Bypass Tool > Disable Auth
Flash all with SP Flash Tool
Download from Realme official site RMX2191_11_OTA_0330.ozip > copy to sdcard
Enter in recovery mode > install from storage > sdcard > RMX2191_11_OTA_0330.ozip > Wipe > Restart
x2s7 said:
My phone is Realme Narzo 20 (7iEU)
Please Help i will never buy Realme
Click to expand...
Click to collapse
Friend you were able to get your equipment I have a realme 7i Eu rmx2193 with the problem of download not completed I can't get it out of there can you help me you were able to get yours I can't even find the official ROMFriend you were able to get your equipment I have a realme 7i Eu rmx2193 with the problem of download not completed I can't get it out of there can you help me you were able to get yours I can't even find the official ROM
x2s7 said:
Edit Scatter File
partition_name: oppo_custom
file_name: oppo_custom.img
is_download: true
Use Mtk Auth Bypass Tool > Disable Auth
Flash with SP Flash Tool without opporeserve2, oppo_custom, cdt_engineering, special_preload and my_custom
Use Mtk Client > mtk_gui > unlock bootloader
Use Mtk Auth Bypass Tool > Disable Auth
Flash all with SP Flash Tool
Download from Realme official site RMX2191_11_OTA_0330.ozip > copy to sdcard
Enter in recovery mode > install from storage > sdcard > RMX2191_11_OTA_0330.ozip > Wipe > Restart
Click to expand...
Click to collapse
Friend you were able to get your equipment I have a realme 7i Eu rmx2193 with the problem of download not completed I can't get it out of there can you help me you were able to get yours I can't even find the official ROMFriend you were able to get your equipment I have a realme 7i Eu rmx2193 with the problem of download not completed I can't get it out of there can you help me you were able to get yours I can't even find the official ROM
Hello, someone help me, I have a realme 7i Eu rmx2193 with the problem of downloading not completed due to deleting everything with flashtool, I have tried flashing it but it still has the same problem and its stock rom appears for realme March 20 when someone searched for it, help me with thatHello, someone help me, I have a realme 7i Eu rmx2193 with the problem of downloading not completed due to deleting everything with flashtool, I have tried flashing it but it still has the same problem and its stock rom appears for realme March 20 when someone searched for it, help me with that
By the way don't waste your time to repair this google trash system.
google is a cyber weapon.
Better use Plasma Mobile or some arm emmc os
You have to extract oppo_custom.img from the ofp file
You can find ofp from google
FrankOlivers said:
Hello, someone help me, I have a realme 7i Eu rmx2193 with the problem of downloading not completed due to deleting everything with flashtool, I have tried flashing it but it still has the same problem and its stock rom appears for realme March 20 when someone searched for it, help me with thatHello, someone help me, I have a realme 7i Eu rmx2193 with the problem of downloading not completed due to deleting everything with flashtool, I have tried flashing it but it still has the same problem and its stock rom appears for realme March 20 when someone searched for it, help me with that
Click to expand...
Click to collapse
Do you have telegram? If so, I can help you (of course for free)
CHANGELOG:
Guide v1.0 - Warn that Lineage cannot be flashed on A12 firmware.
Guide v1.1 - Update guide for flashing Lineage after complete conversion and updates so phone is fully converted first.
There are THREE firmware versions for the N200.
DE2118 - Carrier infected phones for T-Mobile and MetroPCS in US.
DE2117 - Retail US OEM firmware that is 100% compatible with US carriers and fully supports 5G, 4G, 3G (gone), 2G, VoLTE, and VoWIFI.
This guide is intended to remove the carrier virusware that the carrier uses to wipe/spy on the user as well as branding bloat like the bootup/shutdown graphic/sound.
DE2117AA - International version of the phone. This has a different modem/firmware, supports 2 sim cards, and is NOT compatible with US N200 hardware.
WARNINGS:
1. Do NOT flash Intl. DE2117AA firmware or use msmtool for DE2117AA on any US phone or you will no longer make/receive voice or text calls until you flash back to US firmware with Fastboot Enhance!
2. You must NOT stop the guide after you flash DE2117 onto the first slot as the phone will NOT be fully converted until it takes the OTA update to Android 12 and one more to C_17.
If you go to the about screen before the Android 12 OTA update, you will still see DE2118.
3. A You should take ALL OTA updates to Android 12 C_17 and then follow the root guide for Dummies if you want to test drive the latest and very stable current OEM firmware.
B Flash back to DE2117 Android 11 final with my downgrade guide to go back to the final Android 11 DE2117 US before you install current N200 Lineage.
Lineage requires you to be on Android 11 or it will soft brick when you flash Lineage boot.img.
4. Finally, I have had enough people use my N200 guides that they are proven to work very well, but I take no responsibility if you abort the flashing process or skip parts of the guide and manage to boot loop/brick your phone!
However, I will work with you to get you going again. This phone cannot be fully bricked with the Qualcomm chipset and EDL recovery mode. You will create a full backup of your phone in the guide, so you can restore it 100% even if you walk away and your cat manages to fully wipe the entire firmware area of the phone with Fastboot Enhance.
PREREQUISITES: (see other guides)
1. You must have your boot loader unlocked.
2. Request and receive your unlock token from OP website to unlock boot loader.
(This takes exactly one week from requesting on Oneplus Website until OnePlus delivers the unlock token.)
If your phone is still sim subsidy locked and you cannot move the "OEM unlocking in dev options to on as it's greyed out, follow steps (20-24) to bypass this and turn on OEM unlocking so you can get unlocking code without being sim unlocked.
3. Install latest Android Platform Tools installed on PC. Currently v33.0.3
Old versions platform tools will cause fastboot commands to FAIL!!
4. Fastboot Enhance tool
Download and unzip folder into working directory.
This tool is Windows only and requires .net framework 4.5 (can be ran in VM with enough free ram for experienced linux users) This tool also needs a good amount of ram as someone with a old Windows 7 machine with very limited ram had the program hang when unpacking the firmware. They then switched to a newer machine resolved the issue.
5. Backup your phone data as this guide will wipe your phone in the process.
I recommend you put a MicroSD card in your N200 and select MicroSD card as backup location in Swift/APP Manager as all data on MicroSD will survive a phone wipe/reset.
A. The most simple backup tool is Swift Backup with a rooted phone to save all your app, data, phonebook, texts, and wifi passwords for easy restore after you are converted, upgraded and re-rooted.
B. For power users I highly recommend using App Manager to back up your apps.
The App Manager instructions are worth reading like a book as this tool is very complex and powerful.
This tool will backup APK source files/splits, internal/ext data/obb and media/cache, app permissions, battery savings,data usage, Magis khide status, SSAID, rules set up in App Manager. It will also import backups fromOAndBackup, Titanium and Swift (3.0-3.2) and keep multiple version backups of same app.
It's also an Interceptor, Manifest viewer, Scanner (API key from virus total), Enhanced Package installer with version upgrade/downgrade information and library add/remove info on install, Usage, Log viewer with colors/filters, App explore and much more.
-----------------------------------------------------------------------------------------
Begin GUIDE
-----------------------------------------------------------------------------------------
1. Place your phones unlock key into Platform Tools directory.
(You can download it again by logging into OnePlus site and going to this page.)
2. Download Tmobile/MetroPCS OnePlus MSMtool for V11.0.1.7 and unzip to working folder of your choice.
3A. Download FINAL Android V11 Update Image .
If installing Lineage,You MUST flash Lineage boot.ini from Android 11 or you WILL go into a soft boot loop from Android 12!
3B. If you are going to re-flash your phone that is already flashed to DE2117 and on A12 due to a bad update (in a soft boot loop) or installed other A12 rom and need to flash back, Download Full US OEM A12 C_16 Update Image and keep as .zip file and place in working folder instead.
(See Downgrade Guide if you are already running US OEM A12 and want to go back to A11 to install Lineage.)
4. Go to working folder you unzipped msmtool and open folder "dre8t_10_O.07_211014_repack"
5. A. Execute program as Administrator "MsmDownloadTool V4.0.exe" if your running Windows 10 or 11.
B. Execute program as administrator "MsmDownloadTool V4.0_Win7.exe" if your running Windows 7.
6. At login prompt, change user type to:
"User Type: Others" & Hit Next button.
7. At main page of MsmDownload Tool hit "F8"
A new window will pop-up that is called Firehose Readback:
(Ignore my crazy Windows theme colors - Yours will look different)
{
"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"
}
8. Locate Password box at bottom of pop-up and enter lowercase password: oneplus
9. Make sure the box is still active window and hit <cntrl-a> and every box in the list will then become checked.
10. hit OK to close box.
11. Click new "Read Back" button.
13. Place phone in special EDL recovery mode:
A. Since ADB is working, it is easier to simply open your Android Platform tools folder in Explorer and type cmd in location box to open dos prompt and type:
C:\platform-tools>adb reboot edl
B. You can turn phone off and then hold both volume buttons down and power on to force phone into EDL mode if phone is not working properly.
NOTE: When phone is in EDL mode the screen on the phone will be BLANK.
This is NORMAL.
14. As soon as the command is entered switch back to MSMtool window and watch it make a FULL backup of your phone including all firmware (slot a/b) and phone identifying information areas. When this is complete your phone will reboot.
15. Go to root of system drive (Default C:\) in explorer and sort files by date (Double Click on the Date Modified) and move all the new files just created ending in .bin, .img, .elf, and .mbn to a folder and name it to identify this exact phone if you have more than one N200 and store in a safe place like a USB flash drive. You can zip the folder first to save space.
See: Firehose backup files.txt attached for full list.
Do NOT share this backup with anyone online as they can clone your phones IMEI/SN with this PRIVATE backup data!
16. Re-run msmtool again. It will remember user type option: others. Click Next.
17. This time at main screen simply press start. and place phone in EDL mode as in step 13.
18. Watch the tool flash V11.0.1.7 firmware and most importantly the older fastbootd that is proven to perform the conversion firmware flash.
(Phone will reboot wiped/locked and in out of box condition.)
19. Do phone setup offline without entering wifi and as soon as you are out of setup turn off data to prevent phone from starting to download firmware update from OTA.
20. Goto Settings -> About Device -> Version -> build number and click until developer again.
21. Goto Settings -> System Settings -> Developer Options and turn on USB debugging and then exit settings.
22. Go back to dos box and send command to remove software that prevents OEM Unlock from being turned on:
C:\platform-tools>adb shell pm uninstall --user 0 com.qualcomm.qti.uim
23. On Phone: Go to Settings -> System Settings -> Developer Options
Turn ON "OEM Unlocking"
24. Go back to dos box and type:
C:\platform-tools>adb reboot fastboot
25. Send your unlock code to phone again.
(Assuming the file is called unlock_code.bin)
C:\platform-tools>fastboot flash cust-unlock unlock_code.bin
26. Unlock Bootloader:
C:\platform-tools>fastboot oem unlock
27. Follow on screen directions and phone will unlock bootloader, erase data and enter new phone setup again.
Do steps 19-21 again (developer/adb debugging on) and step 24 (Reboot to fastboot)
Now visually verify your phone is in Fastboot mode and unlocked.
28. Go to working folder in explorer and open folder "Fastboot_EnhanceV1.3.0" and execute "FastbootEnhance.exe"
29. On Fastboot Visualization tab, Double click on your device that will be shown.
30. Now you have two tabs, "Basic Properties" and Partitions.
31. Click on Partitions tab and scroll to bottom of the partitions list and verify that there are none that end in "_cow"
(They are creeated when you do OTA upgrades. They are left over and need to be deleted if present otherwise there may not be enough room to write new image.)
32. Highlight EVERY file ending in "_cow" and click the erase button.
They are always at the bottom of the list.
Repeat until there are NO files ending in "_cow"
33. Click the button bottom left corner called "Reboot to Fastbootd"
34. Your phone willl now reboot into special fastbootd mode.
35. Click English on phone to see this. Do NOT click any other options on phone.
36. Tick the box on right Show Logs to watch it's progress. A log box will pop up. Drag it over to the side to watch.
37. Tick the box Ignore Unknown Partitions
(fastbootd will NOT flash over newer modem firmware with older, if flashing older firmware and required for flash to still work)
38A. Click Flash Payload Bin box and select file "DE2117-A11-Final-OnePlusN200Oxygen_10.O.11_OTA_011_all_2203021426_downgrade_66cde69fe1e342db.zip" from working directory.
38B. For Android 12 USS OEM Reflash-Restore, Select file "(US_RETAIL_A12_C_16_FULL_ROM)DE2117_11.C.15_0150_202205192325.zip"
39. Click Flash Payload bin button.
It will unpack all the partitions from the .zip file first.
It will then delete old partitions and re-create partition with new required size and flash each .bin file of firmware one at a time automatically.
40. WAIT.....Watch the log output window and DO NOTHING until complete.
A. Fastboot Enhance will unpack all the partitions from the .zip file first.
B. It will then delete old partitions and re-create partition with new required size and flash each .bin file of firmware one at a time automatically.
41. When process is finished click "Reboot to recovery" button.
42. on phone, tap English.
43. on phone, tap "wipe data" and follow prompts to wipe and restart.
You will now boot up on US OEM DE2117 Android 11 Final.
WARNING: Do NOT stop the guide at this point, as your phone is not fully converted yet!
If you go to about info you will still see DE2118 and the boot area and other slot is still on carrier firmware! (Even if you are going to install Lineage, you must continue OTA upgrades to Android 12 C_17 and then downgrade to Android 11 afterwards)
44. Perform system setup with wifi and go to settings -> about device and perform system update and you will update to A12 (C_16) and proceed to second partial OTA update to latest OTA (C_17) before following the root guide for dummies
WELL DONE MY GOOD SIR!
Thanks for the thorough write-up for this dummy! So once this procedure is completed I can assume that everything that works for the DE2117 (like LineageOS) will be OK for a DE2118?
My fastboot enhance keeps stopping once i select the payload.bin to flash
I have all the correct files but it seems like windows keeps stopping the program from continuing further...
So say you run through this guide, everything goes correctly and you end up with a DE2117. Is it for all intents and purposes a DE2117 or would you still run the DE2118 MSM Tool should you run into a problem and need to reset?
Maatt_OG said:
My fastboot enhance keeps stopping once i select the payload.bin to flash
I have all the correct files but it seems like windows keeps stopping the program from continuing further...
Click to expand...
Click to collapse
Are you seeing anything in the log window?
What is the error message Windows is giving you, and how is it stopping the program?
It sounds like you have Windows issues.
Are you running this in a VM or under very low memory conditions?
You may want to refresh your Windows installation.
Link575 said:
So say you run through this guide, everything goes correctly and you end up with a DE2117. Is it for all intents and purposes a DE2117 or would you still run the DE2118 MSM Tool should you run into a problem and need to reset?
Click to expand...
Click to collapse
That is a very good question.
Once you have flashed DE2117 to one slot and then taken an OTA upgrade, then both slots are converted and your phone is for all practical reason a US OEM. Your IMEI is still in the T-mobile/MetroPCS range so the OP will not give you credits for registering a new OEM phone at Red Cable Club and will say that IMEI is invalid.
I tell people to take OTA updates so they are not half cross flashed as we have had one person try to use msmtool and bricked phone when in this half converted state.
msmtool re-locks the boot loader so it's not the first thing I would do. It's best to use fastboot enhance and re-flash from fastbootd again and wipe if you fail with a GSI or installing another rom.
scanman0 said:
That is a very good question.
Once you have flashed DE2117 to one slot and then taken an OTA upgrade, then both slots are converted and your phone s for alll practical reason a US OEM. Your IMEI is still in the Tmobile range so OP site login will not give you register credit for registering new phone at store.
I tell people to take OTA updates so they are not half cross flashed as we have had one person try to use msmtool and bricked phone when in this half converted state.
msmtool re-locks the boot loader so it's not the first thing I would do. It's best to use fastboot enhance and re-flash from fastbootd again and wipe if you fail with a GSI or installing another rom.
Click to expand...
Click to collapse
it says extracting files in the log but i have eeven waited and ignored the windows pop up error saying , Program has stopped working, we will let you know if theres a solution, but it doesnt proceed any further.
AND... DO NOT USE MSM TOOL AFTER CONVERTING. modem and core-nhlos and a few other partitions are a bit different along with the hardware versions and all and youll bootloop.
scanman0 said:
Are you seeing anything in the log window?
What is the error message Windows is giving you, and how is it stopping the program?
It sounds like you have Windows issues.
Are you running this in a VM or under very low memory conditions?
You may want to refresh your Windows installation.
Click to expand...
Click to collapse
as for memory, i am running pretty low tbh....
scanman0 said:
That is a very good question.
Once you have flashed DE2117 to one slot and then taken an OTA upgrade, then both slots are converted and your phone s for alll practical reason a US OEM. Your IMEI is still in the Tmobile range so OP site login will not give you register credit for registering new phone at store.
I tell people to take OTA updates so they are not half cross flashed as we have had one person try to use msmtool and bricked phone when in this half converted state.
msmtool re-locks the boot loader so it's not the first thing I would do. It's best to use fastboot enhance and re-flash from fastbootd again and wipe if you fail with a GSI or installing another rom.
Click to expand...
Click to collapse
I see thanks for that. So one more follow up, I'm not even sure if you would know this but I installed Lineage 19 on my DE2118 and after that About phone states its a 2117. I'm assuming this is just because that's what this ROM was made for and it's not actually converting to a DE2117. I did MSM after Lineage and had no problems going back to stock DE2118.
scanman0 said:
13. Place phone in special EDL recovery mode:
Click to expand...
Click to collapse
This dummy had never seen EDL mode before and because my MSMDownload tool for Win7 seemed to require running as administrator the tool did not automatically connect so all I saw was a black screen in Step 14.
We shall not talk about how long nor how many different reboot combinations were required for me to understand that I needed to run the tool as administrator and that the black screen was normal. Really funny.
Even funnier was that I never did find the backup files after the Download was complete. Not on C:, not on D:, none found with the Explorer search function. Somehow I made them vanish even after your careful description.
katooom said:
Even funnier was that I never did find the backup files after the Download was complete.
Click to expand...
Click to collapse
And the only reasonable explanation for this is that among my many confused attempts to make things work this was the time that I did not actually do the backup, just pressed the start button. I would hate to think that I made such a ridiculous blunder but what else could it be. Oh my .....
Maatt_OG said:
as for memory, i am running pretty low tbh....
Click to expand...
Click to collapse
You need to have enough memory free for the program to unpack the .zip file in ram. If Windows is crashing the process with "program is not responding" then your pc (or is it a vm?) does not have enough memory.
Link575 said:
I see thanks for that. So one more follow up, I'm not even sure if you would know this but I installed Lineage 19 on my DE2118 and after that About phone states its a 2117. I'm assuming this is just because that's what this ROM was made for and it's not actually converting to a DE2117. I did MSM after Lineage and had no problems going back to stock DE2118.
Click to expand...
Click to collapse
Lineage has one build that is compatible with both versions and reports that either is DE2117.
katooom said:
This dummy had never seen EDL mode before and because my MSMDownload tool for Win7 seemed to require running as administrator the tool did not automatically connect so all I saw was a black screen in Step 14.
We shall not talk about how long nor how many different reboot combinations were required for me to understand that I needed to run the tool as administrator and that the black screen was normal. Really funny.
Even funnier was that I never did find the backup files after the Download was complete. Not on C:, not on D:, none found with the Explorer search function. Somehow I made them vanish even after your careful description.
Click to expand...
Click to collapse
I have updated the guide to reflect that you need to run as administrator on Windows 7 and to run the windows 7 .exe file.
I have only tested under Windows 10 and Windows 11 and the program demanded administrator mode to run.
The msmtool always dumps to the root of the working system boot drive that is usually C:
I made a screen shot of the F8 windows as you must select the boxes and place the password to place the tool in the backup mode.
I never said in the guide to look at the phone when in EDL mode as the screen is black.
I have updated the guide to inform people that are not familiar with EDL mode to expect that it is blank.
This is the reason I had people go to EDL mode with the pc with adb is the fact that it is a blank screen mode and people can be confused if the phone is in EDL or off.
I cannot tell by your condescending comments if you actually did the F8 procedure correctly to place msmtool in backup mode.
There is no indicator before it starts (other than the window closing without an error) and the tool will indicate as shown in the screenshot that it is "Reading back <Partition name>" as it reads the partitions from the phone.
If you simply press start as you implied you "tried" the tool will flash the phone to default factory state and NOT do a backup.
You do realize I wrote this guide to try to help people and cannot test every possible configuration as I don't have Windows 7 anymore.
People with your poor attitude is the reason there are fewer hand holding guides present on XDA.
scanman0 said:
Lineage has one build that is compatible with both versions and reports that either is DE2117.
Click to expand...
Click to collapse
Got it, thanks.
scanman0 said:
People with your poor attitude is the reason there are fewer hand holding guides present on XDA.
Click to expand...
Click to collapse
Whoa, I have to apologize for making you think that I was in any way critical or dissatisfied! I was merely making fun of myself for messing up the process in spite of how well you explained it. I actually hoped that you would be amused by my errors and the silly reasons that I made them. It is deeply upsetting to me to have offended someone who puts so much effort into helping. I can only apologize again for expressing myself so poorly.
@scanman0 Dumb question probably, but after completing this, would it be possible to downgrade to Android 11 OEM?
rcartaz09 said:
@scanman0 Dumb question probably, but after completing this, would it be possible to downgrade to Android 11 OEM?
Click to expand...
Click to collapse
Nothing dumb about this question!
I have updated the guide to INCLUDE converting to last Android 11 US OEM Firmware
And put warning to only install Lineage with Android 11 firmware.
I also posted a separate downgrade guide so people will not miss this fact if they already upgraded to Android 12 and want to install Lineage:
Downgrade US OEM (DE2117) Android 12 firmware to Android 11 BEFORE installing Lineage!
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to: DE2117 OEM...
forum.xda-developers.com
After completing this, would it be possible
scanman0 said:
Nothing dumb about this question!
I have updated the guide to INCLUDE converting to last Android 11 US OEM Firmware
And put warning to only install Lineage with Android 11 firmware.
I also posted a separate downgrade guide so people will not miss this fact if they already upgraded to Android 12 and want to install Lineage:
Downgrade US OEM (DE2117) Android 12 firmware to Android 11 BEFORE installing Lineage!
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to: DE2117 OEM...
forum.xda-developers.com
Click to expand...
Click to collapse
You are awesome! Thank you!
Hello guys,
i tried to flash an EU ROM on my Chinese Xiaomi Pad 5 Pro. Unfortunately, it failed
Symptoms:
Pad has full black screen.
It can not start into fast boot mode
cant be found by Xiaomi flash tool.
When i connect it to my computer and hold Power + Volume up or down, the computer beeps after a while
What happened:
i downloaded EU fastboot rom and unpacked with 7zip
unlocked bootloader of Xiaomi Pad
connected to xiaomi flash tool
copied unpacked rom files on C:\EU
start flash_all
after having an error "crclist or sparsecrclist" (Link), i added REM into the flash file, as mentioned on youtube and started again
at the end of the flash process it showed a problem with the "REM" line, that i added and the flash failed
I cant flash again because i cant get into the fastboot mode... Do you have any clue what i can do now?
Thanks a lot!
nappi
nappi90 said:
Hello guys,
i tried to flash an EU ROM on my Chinese Xiaomi Pad 5 Pro. Unfortunately, it failed
Symptoms:
Pad has full black screen.
It can not start into fast boot mode
cant be found by Xiaomi flash tool.
When i connect it to my computer and hold Power + Volume up or down, the computer beeps after a while
What happened:
i downloaded EU fastboot rom and unpacked with 7zip
unlocked bootloader of Xiaomi Pad
connected to xiaomi flash tool
copied unpacked rom files on C:\EU
start flash_all
after having an error "crclist or sparsecrclist" (Link), i added REM into the flash file, as mentioned on youtube and started again
at the end of the flash process it showed a problem with the "REM" line, that i added and the flash failed
I cant flash again because i cant get into the fastboot mode... Do you have any clue what i can do now?
Thanks a lot!
nappi
Click to expand...
Click to collapse
It seems to me that there is no EEA version for your device.
What code name, elish, dagu, enuma?
nappi90 said:
Hello guys,
i tried to flash an EU ROM on my Chinese Xiaomi Pad 5 Pro. Unfortunately, it failed
Symptoms:
Pad has full black screen.
It can not start into fast boot mode
cant be found by Xiaomi flash tool.
When i connect it to my computer and hold Power + Volume up or down, the computer beeps after a while
What happened:
i downloaded EU fastboot rom and unpacked with 7zip
unlocked bootloader of Xiaomi Pad
connected to xiaomi flash tool
copied unpacked rom files on C:\EU
start flash_all
after having an error "crclist or sparsecrclist" (Link), i added REM into the flash file, as mentioned on youtube and started again
at the end of the flash process it showed a problem with the "REM" line, that i added and the flash failed
I cant flash again because i cant get into the fastboot mode... Do you have any clue what i can do now?
Thanks a lot!
nappi
Click to expand...
Click to collapse
I guessed you downloaded and flashed the wrong firmwares/ROM to your device. This caused serious brick (the hardest brick) to your device. All the wrong firmwares have been flashed to every single partitions of your device. That's why your device can neither boot up nor enter fastboot mode. I got my Lenovo Yoga Tab 13 and some other Qualcomm devices into this serious brick. I got my Lenovo Yoga Tab 13 this brick by relocking bootloader. The only method that can fix your device error is to use QPST QFIL.
Requirements:
1.Windows 10 x64 preferred or above with WSL (Windows Subsystem for Linux) enabled. Because QFIL in QPST requires Sahara server (Linux) to run on your Windows.
2.Download and install HS-USB QDLoader 9008 driver for your Windows version.
3.Download and install QPST to your PC.
4.Download and unzip the correct fastboot ROM for your device to your PC. There are files with .img inside the zipped file. For example, boot.img, recovery.img and many others.
I am not sure if Mi Pad 5 Pro requires Provision process to flash via QPST or not? Some Qualcomm devices, for example Chuwi Hi Pad Pro, require Provision before getting permission to flash via Download mode using QPST.
Watch this tutorial to see the how-to-use-QFIL video. This video is quite old. There may be some chages in QFIL. You can google the newer tutorial about QFIL.
While your device does not show nothing but the black screen, follow the steps below:
1.Assumingly you have completed all the requirements above, open QFIL.
2.Connect USB from your PC to your device.
3.Load XML by matching all the files of rawprogram#.xml with patch#.xml. For example, If there are 6 files of rawprogram0.xml to rawprogram5.xml. You have to add rawprogram0.xml matching patch0.xml until rawprogram5.xml matching with patch5.xml to the Download list.
4.Press Download button in QFIL.
5.Hold volume Down (Some Qualcomm devices are volume UP and some are both volume at the same time) and press power button many times until the download process of QFIL starting up. This means your device has entered Download Mode.
6.Wait until the download process completed. Hopefully there is no error or no Provision process required.
7.Disconnect the USB from your device.
8.Your device should boot up showing Mi logo. If not, hold power button to try booting up your device.
Hope you can fix this. Or your device will turn into one of the most expensive paper weight.
Before step 3, i have to choose one programmer out of these:
{
"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"
}
In step 3 I matched one by one rawprogram and patch file, but in the box it only shows the last pair. Do I have to click every time on download e.g. I choose rawporgram1.xml and patch1.xml and then press download or do I match all of them first like below, then there is only the last one visible.
In the end I get some failed to open com port handle messages. Do you know where this comes from?
NOSS8 said:
It seems to me that there is no EEA version for your device.
What code name, elish, dagu, enuma?
Click to expand...
Click to collapse
unfortunately, it seems you are right... this is the reason.....
nappi90 said:
Before step 3, i have to choose one programmer out of these:
View attachment 5770983
In step 3 I matched one by one rawprogram and patch file, but in the box it only shows the last pair. Do I have to click every time on download e.g. I choose rawporgram1.xml and patch1.xml and then press download or do I match all of them first like below, then there is only the last one visible.View attachment 5770981
In the end I get some failed to open com port handle messages. Do you know where this comes from?
Click to expand...
Click to collapse
1.Choose prog_ufs_firehose_sm8250_ddr_5.elf
2.Have you enabled WSL on your Windows 10 or above? Read requirement #1 of my post.
siamese007 said:
1.Choose prog_ufs_firehose_sm8250_ddr_5.elf
2.Have you enabled WSL on your Windows 10 or above? Read requirement #1 of my post.
Click to expand...
Click to collapse
to 2: yes, i did.
About the rawprogram1 - rawprogram5: Do you know, if i need to download after matching each pair e.g. rawprogram1 = patch 1; click download; rawprogram2 = patch 2; click download etc.
nappi90 said:
to 2: yes, i did.
About the rawprogram1 - rawprogram5: Do you know, if i need to download after matching each pair e.g. rawprogram1 = patch 1; click download; rawprogram2 = patch 2; click download etc.
Click to expand...
Click to collapse
Add all the rawprogram0.xml to rawprogram5.xml matching with patch0.xml to patch5.xml files to the Download list at once and press download button.
My experiment:
I have put my Mi Pad 5 Pro 5G into Download Mode (EDL) and run QFIL > Partition Manager. QFIL cannot access the partitions of my device. This probably means my device may require Provision to do this. So it may mean yours requires Provision to flash the firmware with QFIL also.
Now it's come to my most fear that you will need the Provision file which is not included in the fastboot firmware/ROM. You have to ask this file from Xiaomi Customer Services. And your device's warranty has been voided since you have unlocked bootloader.
Try 1 of the following methods.
1.Ask someone who has the same device as yours to ask Xiaomi Customer Services for Provision file. Tell them you need the file to back up partition of your device. The Customer Services may ask the serial number and other info about that person's device for verify the customer warranty.
2.Ask Xiaomi Customer Services for the Provision file for your deivce by yourself. Tell them that your device got brick and can be accessed only by Download Mode (EDL) via QPST or QFIL.
3.Google to find the Provision file for your device on the internet. It's very difficult. I still cannot find the Provision file for my old Redmi K30 5G released in Jan 2020, around 3 years ago.
4.Google the method to work around your Sahara error. And hope your device does not need Provision to flash the firmware via Download Mode (EDL).
5.No offense. If you have extra money, buy the new one and ask Xiaomi Customer Services for the Provision file. Or buy Lenovo devices. They are not required Provision to flash firmware via Download Mode (EDL).
If you have the Provision file, ask me again of how to do Provision. Or google the way to do Provision on the internet.
Wish you best luck.
siamese007 said:
Add all the rawprogram0.xml to rawprogram5.xml matching with patch0.xml to patch5.xml files to the Download list at once and press download button.
My experiment:
I have put my Mi Pad 5 Pro 5G into Download Mode (EDL) and run QFIL > Partition Manager. QFIL cannot access the partitions of my device. This probably means my device may require Provision to do this. So it may mean yours requires Provision to flash the firmware with QFIL also.
Now it's come to my most fear that you will need the Provision file which is not included in the fastboot firmware/ROM. You have to ask this file from Xiaomi Customer Services. And your device's warranty has been voided since you have unlocked bootloader.
Try 1 of the following methods.
1.Ask someone who has the same device as yours to ask Xiaomi Customer Services for Provision file. Tell them you need the file to back up partition of your device. The Customer Services may ask the serial number and other info about that person's device for verify the customer warranty.
2.Ask Xiaomi Customer Services for the Provision file for your deivce by yourself. Tell them that your device got brick and can be accessed only by Download Mode (EDL) via QPST or QFIL.
3.Google to find the Provision file for your device on the internet. It's very difficult. I still cannot find the Provision file for my old Redmi K30 5G released in Jan 2020, around 3 years ago.
4.Google the method to work around your Sahara error. And hope your device does not need Provision to flash the firmware via Download Mode (EDL).
5.No offense. If you have extra money, buy the new one and ask Xiaomi Customer Services for the Provision file. Or buy Lenovo devices. They are not required Provision to flash firmware via Download Mode (EDL).
If you have the Provision file, ask me again of how to do Provision. Or google the way to do Provision on the internet.
Wish you best luck.
Click to expand...
Click to collapse
Thanks a lot for your big effort to help me. Seems like i need this EDL mode. Currently, i am in Beijing in lockdown and its not the best time to go around and find a mi customer service. Meanwhile, i look for a solution for the sahara problem (see point 4).
@siamese007 hi,
I tried your method to unbrick a Mi pad 5, but unfortunately an authorization is needed...
I am trying to ask Xiaomi help. I don't have any answer for the moment...
If I try to ask them the Provision file, what I should do with ?
Could you explain me your method ? Do you think it’s a file they’re capable of giving away?
Thank you in advance,
Nicolas
Heavymistick said:
@siamese007 hi,
I tried your method to unbrick a Mi pad 5, but unfortunately an authorization is needed...
I am trying to ask Xiaomi help. I don't have any answer for the moment...
If I try to ask them the Provision file, what I should do with ?
Could you explain me your method ? Do you think it’s a file they’re capable of giving away?
Thank you in advance,
Nicolas
Click to expand...
Click to collapse
Hello,
What happened with your device? Is your device Mi pad 5 nabu? Why can you not flash your device with Mi Flash Tool?
If you want to flash your device with QFIL in EDL mode, all Xiaomi devices require provision files to do it. Provision file is not supposed to be secret of company use only. Some devices have done provision for users at their factories. Otherwise users will be required to do provision by themselves. IMO provision files should be added to the firmware zip file for EDL mode.
For normal case, users can use Mi Flash tool to flash firmware. So Xiaomi might think provision files are not needed.
siamese007 said:
Hello,
What happened with your device? Is your device Mi pad 5 nabu? Why can you not flash your device with Mi Flash Tool?
If you want to flash your device with QFIL in EDL mode, all Xiaomi devices require provision files to do it. Provision file is not supposed to be secret of company use only. Some devices have done provision for users at their factories. Otherwise users will be required to do provision by themselves. IMO provision files should be added to the firmware zip file for EDL mode.
For normal case, users can use Mi Flash tool to flash firmware. So Xiaomi might think provision files are not needed.
Click to expand...
Click to collapse
Thanks a lot for your answer,
I brick my tablet by corrupting UFS files after a fake manip by following a tutorial. It is indeed a tablet pad 5 with as code name "nabu".
Only EDL works, i can't boot fastboot or recovery (black screen). Mi Flash tool needs a Xiaomi authorization to flash with EDL mode. I don't know if Xiaomi can give me a temporary permission for that ?
I tried to flash the ROM with QFIL in EDL but i had an error "Only nop and sig tag can be recevied before authentication.".
So I guess I have to get the file you were talking about to go further?
Heavymistick said:
Thanks a lot for your answer,
I brick my tablet by corrupting UFS files after a fake manip by following a tutorial. It is indeed a tablet pad 5 with as code name "nabu".
Only EDL works, i can't boot fastboot or recovery (black screen). Mi Flash tool needs a Xiaomi authorization to flash with EDL mode. I don't know if Xiaomi can give me a temporary permission for that ?
I tried to flash the ROM with QFIL in EDL but i had an error "Only nop and sig tag can be recevied before authentication.".
So I guess I have to get the file you were talking about to go further?
Click to expand...
Click to collapse
I tested with my device to access its partition tables but could not. And got error saying something about "authentication". So I guess yes you need to do provision before being able to flash the ROM in EDL mode with QFIL.
From my experience, the provision file is xml with some code to access the system on the chip that allows QFIL to flash firmware in EDL mode. Not sure if this provision for the SoC can be used widely across any devices with the same chipsets. You may look for the provision file from other devices with the same chipset as your device's. I will explain how to do provision later.