Full partitions backup directly via fastboot - Huawei P9 Plus Guides, News, & Discussion

Hi
This is just a simple tool to help people who can only access to fastboot, before traying any unbrick i suggest you to do a backup using fastboot dump-emmc methode
This will dump all your partition before you try to use any tool to unbrick, any one can use it to make a full backup to prevent any brick
Bootloader have to be unlocked
It worked with my vie-l29 but not with my nxt-al10 ( im traying to find the solution)
Need people to do a test and tel me if it worked for you
1- Extract in any folder
2- Connect your phone in fastboot mode
3- Launch recovery_fastboot.bat
4- All your backup are saved in the backup folder that you have extracted
Thank you

I am getting: (bootloader) 'dump-emmc' is not a supported oem command

Am very intreasted in this but cant see your files/bat file?

Same here, also intrested, but not files attached

Maybe it was "fastboot fetch PARTITION OUT_FILE" in the bath file but not all smartphone support this command. As my Moto G6 Plus do not.

Related

[Q] Bricked huawei Mediapad 7 X1

Hello,
This is my first android tablet and i love it, but i have bricked it, i was messing around with it and i think i wiped it all, at this moment the device is stuck at the mediapad logo, fastboot mode is working but i can not get into recovery.
I have downloaded the two official stock roms mentioned in this post http://forum.xda-developers.com/hua...rom-official-huawei-mediapad-x1-b007-t2811863 but when i try to do
Code:
fastboot update update.zip
i get the below error:
Code:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt]
The zip file contain the dload folder and the update.app file, no .txt files in mention. Any solution to this ?
I have also tried to flash a cwm/twrp recovery (tried many variants) into the device but i can not boot into them (nothing happens, still stuck at the mediapad screen).
Code:
fastboot flash recovery recovery.img
At this moment i have only fastboot available, what can i do to unbrick the device ?
Thanks alot
zertux said:
Hello,
This is my first android tablet and i love it, but i have bricked it, i was messing around with it and i think i wiped it all, at this moment the device is stuck at the mediapad logo, fastboot mode is working but i can not get into recovery.
I have downloaded the two official stock roms mentioned in this post http://forum.xda-developers.com/hua...rom-official-huawei-mediapad-x1-b007-t2811863 but when i try to do
Code:
fastboot update update.zip
i get the below error:
Code:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt]
The zip file contain the dload folder and the update.app file, no .txt files in mention. Any solution to this ?
I have also tried to flash a cwm/twrp recovery (tried many variants) into the device but i can not boot into them (nothing happens, still stuck at the mediapad screen).
Code:
fastboot flash recovery recovery.img
At this moment i have only fastboot available, what can i do to unbrick the device ?
Thanks alot
Click to expand...
Click to collapse
Use the standard ROM flashing method by copying the update.app into dload folder onto an external sdcard and reboot your device. This ought to work. If it doesn't you've truly bricked your device by screwing up the bootloader.
The only other way if you've screwed up the bootloader is to perform a bootloader unlock using the tool on 4PDA.ru. Google Translate is rather spotty though.
joytest said:
Use the standard ROM flashing method by copying the update.app into dload folder onto an external sdcard and reboot your device. This ought to work. If it doesn't you've truly bricked your device by screwing up the bootloader.
The only other way if you've screwed up the bootloader is to perform a bootloader unlock using the tool on 4PDA.ru. Google Translate is rather spotty though.
Click to expand...
Click to collapse
Will the sdcard method work if i can not boot into recovery ? also, can you point me to that tool ? i can not find it there
zertux said:
Will the sdcard method work if i can not boot into recovery ? also, can you point me to that tool ? i can not find it there
Click to expand...
Click to collapse
Sdcard method is the default update method for Huawei. There is no need to mess with any 3-button combo or hardware.
It is the easiest update method I've seen among the major phone companies.
I will post link to the 4pda tool link later as I am at work now.
Sent from my SM-N9005 using Tapatalk
joytest said:
Sdcard method is the default update method for Huawei. There is no need to mess with any 3-button combo or hardware.
It is the easiest update method I've seen among the major phone companies.
I will post link to the 4pda tool link later as I am at work now.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
I have made a little progress i think, using your post https://forum.lowyat.net/index.php?showtopic=3280093&st=840&p=70452069&#entry70452069 i have flashed the CWM recovery and i am able to boot into it (Chinese XD) and i am using the menu you translated to navigate around, i have put the stock zip that i downloaded and tried to flash the zip file but i got some erros that i did not understand (see attached screenshot)
I have noticed that when i plug the device now into the pc it shows the battery charging (something did not appear before). Also, the sdcard update method is not working (nothing happens, stays at the mediapad logo)
What should i do now ?
screenshot:
http://i59.tinypic.com/29xue0p.jpg
It says cannot open the file.
Just use the normal method of the dload folder.
You have taken a very complex route to solve a simple issue.
Sent from my Mediapad X1 7D-501L using Tapatalk HD
joytest said:
It says cannot open the file.
Just use the normal method of the dload folder.
You have taken a very complex route to solve a simple issue.
Sent from my Mediapad X1 7D-501L using Tapatalk HD
Click to expand...
Click to collapse
I have tried the dload method, i have extracted the contents of the zip file "dloadl/update.app" and put them in a 2GB memory, inserted the momeory inside the device and turned it on but nothing happens, it stays on the logo of "mediapad"
zertux said:
I have tried the dload method, i have extracted the contents of the zip file "dloadl/update.app" and put them in a 2GB memory, inserted the momeory inside the device and turned it on but nothing happens, it stays on the logo of "mediapad"
Click to expand...
Click to collapse
Then it is quite possible your download is corrupted. Try downloading again. And I think the recommendation was to use a 4Gb card.
joytest said:
Then it is quite possible your download is corrupted. Try downloading again. And I think the recommendation was to use a 4Gb card.
Click to expand...
Click to collapse
Ok, will re download and try with a 4GB memory stick, what about the bootloader unlocker that you mentioned ? do we still need that ?
zertux said:
Ok, will re download and try with a 4GB memory stick, what about the bootloader unlocker that you mentioned ? do we still need that ?
Click to expand...
Click to collapse
Just to clarify, my device is 7d-501u so i will have to download this http://www.emui.com/nsp/geturl.php?path=7D-501u_EMUI_2.0_V100R001C233B019.zip&rid=560 right ?
zertux said:
Just to clarify, my device is 7d-501u so i will have to download this http://www.emui.com/nsp/geturl.php?path=7D-501u_EMUI_2.0_V100R001C233B019.zip&rid=560 right ?
Click to expand...
Click to collapse
Yes you have to download the correct ROM for your device. 501u is the 3G version.
joytest said:
Yes you have to download the correct ROM for your device. 501u is the 3G version.
Click to expand...
Click to collapse
so i have downloaded http://www.emui.com/nsp/geturl.php?path=7D-501u_EMUI_2.0_V100R001C233B019.zip&rid=560 and it still gives me the same error in the screenshot, how can i get the correct firmware for my device ? (on the back of the device its written 7D-501u )
zertux said:
so i have downloaded http://www.emui.com/nsp/geturl.php?path=7D-501u_EMUI_2.0_V100R001C233B019.zip&rid=560 and it still gives me the same error in the screenshot, how can i get the correct firmware for my device ? (on the back of the device its written 7D-501u )
Click to expand...
Click to collapse
As far as I know, you downloaded the 501u version. Perhaps the last resort is to enable the CWM to allow ABD sideloading?
Or, you can try this "unlock bootloader" from 4PDA
http://4pda.ru/forum/index.php?showtopic=564429&view=findpost&p=34341371
It seems you just need to run the exe file. You can try this since nothing else works for you.
Appreciate if you report on the success.
joytest said:
As far as I know, you downloaded the 501u version. Perhaps the last resort is to enable the CWM to allow ABD sideloading?
Or, you can try this "unlock bootloader" from 4PDA
http://4pda.ru/forum/index.php?showtopic=564429&view=findpost&p=34341371
It seems you just need to run the exe file. You can try this since nothing else works for you.
Appreciate if you report on the success.
Click to expand...
Click to collapse
I will try the bootloader unlocker when i get home, i have tried 4 official roms for the 3G and 4G and i get this error
http://tinypic.com/usermedia.php?uo=adkBqYNLlttp9d8/5vW/a4h4l5k2TGxc
Can you tell me what does it say ? Also hoq can i re install the stock recovery of the device ? Maybe it will work ? I flashed it and installed wcm.
Update: i have downloaded the bootloader unlocker but its all in Chinese! any help is appreciated.
Update2: The bootloader is already unlocked, when i run
Code:
fastboot oem get-bootinfo
it says unlocked. however the device is not taking any rom that i try to install to it (errors in Chinese). i have extracted the system.img, boot.img and recovery.img from the update.app package, i will try to flash them into the device one by one with fastboot.
FIXED!
So for anyone who ran into the same problem, here is how i fixed it:
1. Downloaded the 7D-501u official stock ROM mentioned in this post http://forum.xda-developers.com/hua...rom-official-huawei-mediapad-x1-b007-t2811863
2. Used Huawei update.app extractor tool from http://forum.xda-developers.com/attachment.php?attachmentid=2822142&d=1403960391
3. Flashed boot.img, recovery.img and system.img
Code:
fastboot flash recovery RECOVERY.img
fastboot flash system SYSTEM.img
fastboot flash boot BOOT.img
Rebooted and it worked! the bootloader comes unlocked by default (at least for my model). Special thanks for joytest for his help.
Hello. I'm crazy. I deleted stock recovery original for my 7D-503L 4.2.2 (B008). The problem was install the stock recovery 4.4 kit Kat for error. I installed again the rom B008 and anything. Is impossible to find the stock recovery original and one CWM for my device. Somebody can I help me please? Somebody know where lies the stock recovery? I know is independently of the Rom.
Regards
Soft Brick: Stuck at Huawei logo and unbale to Boot/access Recovery.
=> Install the Universal Android USB Driver from the link below:
http://adbdriver.com/upload/AdbDriverInstaller.exe
=> Download and install ADB and Fast Boot from thebelow link.
http://fs1.d-h.st/download/00103/KIP/adb-setup-1.2.exe
=> Extract the Stock ROM using the Tool "Huawei Update Extractor" in the computer.
=>"HuaweiUpdateExtractor download link:
http://dl.xda-developers.com/attachd....7.9_Setup.zip
=> Copy and paste the Stock/TWRP Recovery and BOOT.img in the "ADB and Fast Boot" folder.
=> Connect the HAM to the computer using the supplied USB cable.
=> Press and hold the Power and Volume Down button.
=> HAM will be recognized as ABD device.
=> Leave the Power and Volume Down button.
=> Double click to open the installed "ADB and Fast Boot" from the Desktop or open the computer prompt to access the "ADB and Fast Boot" folder.
=> In the ADB and Fast Boot prompt:
=> Type: fastboot reboot-bootloader.
=> Type: fastboot flash BOOT BOOT.img
=> Type fastboot flash RECOVERY RECOVERY.img
Fastboot will flash the image and give you a success/failure notification. If successful, you're all set.
Finally, press and hold the Power button. HAM will boot now
fastboot: that's the executable tool
flash: that's the function we want the fastboot tool to perform
recovery: this is the name of the partition we want to flash into. since we are flashing a recovery image, it needs to go to the recovery partition.
recovery.img: this is the name of the actual file to flash. Your file name may be different. Just make sure it matches the actual file name.
@eennap. Ok tomorrow I will to try.
Thanks and Regards
I have a bricked (7D-501L).
1 .
I download a ROM «Huawei_MediaPad_X1_7D-501L_V100R001C170B001_Android_4.2_Russia».
I unzip ROM into root sdcard.
I use Huawei update.app extractor tool, and extract from ROM «boot» and «recovery» partitions.
I flashed a «boot» and «recovery» partitions via fastboot (from it ROM).
After, I use the standard ROM flashing method. The device start flashing, but after a few minutes the device reboot.
ROM not installed, the device not start.
2.
I download a ROM OTA_7D-503LV100R002C208B002.
I extracted this ROM, and flashed a BOOT.img, CACHE.img, CUST.img, RECOVERY.img, SYSTEM.img, USERDATA.img partitions via fastboot.
The device started, but after a few minuts my device reboot to black screen FASTBOOT.
What can i do to unbrick the device ?
P.S.: sorry for bad English
how can i make update.zip from update.app?
my device not flashing standard method.
I can flash it from recovery. I need update.zip
Please, help me

Bricked Honor 5X

Hi,
I have bricked my Honor 5x after flashing custom recovery. This these the steps I followed:
1) Unlocked the bootloader
2) Flashed TWRP recovery
3) Flashed root
4) Tried to update OTA
Now the phone is stuck at boot screen. I can enter recovery by pressing volume down and power, but now is stock recovery. And I don't know what to do.
Can someone help me?
OK u can't OTA update with twrp AND U SHOULD try adb flashing twrp through fastboot and maybe restoring a nandroid if u have one if not there's some u can download around here
Hey, my phone is bricked too. How did you manage to flash adb during twrp. How did you restore the backup and where did you get it from?
Or could someone please explain to me how I can get back to stock. I saw one thread with the .app file, but there you had to go the setting or something, which I can't do.
I have twrp installed and I have the L21 version.
Ok, I figured it out. I took the backup and the instructions from this thread: http://forum.xda-developers.com/honor-5x/development/unrooted-stock-rom-t3308902
heinzwilli6 said:
Hey, my phone is bricked too. How did you manage to flash adb during twrp. How did you restore the backup and where did you get it from?
Or could someone please explain to me how I can get back to stock. I saw one thread with the .app file, but there you had to go the setting or something, which I can't do.
I have twrp installed and I have the L21 version.
Click to expand...
Click to collapse
I was able to get my phone back to stock using the update.app file and the Huawei Update Extractor
Download stock firmware and extract the update.app file
http://forum.xda-developers.com/honor-5x/development/repository-honor-5x-file-depot-t3328288​
Download Huawei Update Extractor
http://d-h.st/wwfQ​
Use the Huawei Update Extractor to open the update.app file and extract system.img, Cust.img, boot.img, recovery.img
Copy the extracted files to your adb folder
Connect the phone to the PC in fastboot mode, to do this power off the phone hold Volume down and insert a usb cable connected to the PC
Type these commands on ADB:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cust cust.img
fastboot reboot​
After that you should be back on stock firmware
I tried to do that too. But the problem was that my adb didn't recognize my phone. Of course I had everything installed.
When I unlocked the bootloader earlier, it worked. But there I had to enable USB debugging. When my phone was broke, I couldn't enable it. Maybe that's why?
However, my phone is working right now, so thanks anyway.
fixed
jperez1132 said:
I was able to get my phone back to stock using the update.app file and the Huawei Update Extractor
Download stock firmware and extract the update.app file
http://forum.xda-developers.com/honor-5x/development/repository-honor-5x-file-depot-t3328288​
Download Huawei Update Extractor
http://d-h.st/wwfQ​
Use the Huawei Update Extractor to open the update.app file and extract system.img, Cust.img, boot.img, recovery.img
Copy the extracted files to your adb folder
Connect the phone to the PC in fastboot mode, to do this power off the phone hold Volume down and insert a usb cable connected to the PC
Type these commands on ADB:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cust cust.img
fastboot reboot​
After that you should be back on stock firmware
Click to expand...
Click to collapse
I have a practically dead honor 5x, flashed a L-24 firmware on L-22. TWRP doesnt let me do anything, no touch functions work so i cannot restore my back up.
Fastboot commands on format /data and flash cust cust.img fail with the error "Remote: Command not allowed", bootloader is unlocked, pls help.....I need to flash back the default cust.img to get it back to normal
SOLVED: Downloaded the official firmware, placed the "dload" folder which contains the update.app in the root of the sd card, went into download mode on phone (vol up + vol dow + power) and the system installed the firmware automatically.....booted back into the stock system now, next will reflash TWRP and restore back up
nandakalyan said:
I have a practically dead honor 5x, flashed a L-24 firmware on L-22. TWRP doesnt let me do anything, no touch functions work so i cannot restore my back up.
Fastboot commands on format /data and flash cust cust.img fail with the error "Remote: Command not allowed", bootloader is unlocked, pls help.....I need to flash back the default cust.img to get it back to normal
SOLVED: Downloaded the official firmware, placed the "dload" folder which contains the update.app in the root of the sd card, went into download mode on phone (vol up + vol dow + power) and the system installed the firmware automatically.....booted back into the stock system now, next will reflash TWRP and restore back up
Click to expand...
Click to collapse
WORKED: update.app in dload folder WORKED !!! Thanks a lot
narengowda said:
WORKED: update.app in dload folder WORKED !!! Thanks a lot
Click to expand...
Click to collapse
Glad it worked! did you figure out what caused the issue?
jperez1132 said:
I was able to get my phone back to stock using the update.app file and the Huawei Update Extractor
Download stock firmware and extract the update.app file
http://forum.xda-developers.com/honor-5x/development/repository-honor-5x-file-depot-t3328288​
Download Huawei Update Extractor
http://d-h.st/wwfQ​
Use the Huawei Update Extractor to open the update.app file and extract system.img, Cust.img, boot.img, recovery.img
Copy the extracted files to your adb folder
Connect the phone to the PC in fastboot mode, to do this power off the phone hold Volume down and insert a usb cable connected to the PC
Type these commands on ADB:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cust cust.img
fastboot reboot​
After that you should be back on stock firmware
Click to expand...
Click to collapse
Is your fingerprint ID working good?
---------- Post added at 09:14 AM ---------- Previous post was at 08:46 AM ----------
fastboot flash cust CUST.img
target max-download-size: 254MB
sending 'cust' (196335 KB)...
OKAY [ 6.493s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 6.493s
Cant flash cust. How did you do that?
sad1996 said:
Is your fingerprint ID working good?
---------- Post added at 09:14 AM ---------- Previous post was at 08:46 AM ----------
fastboot flash cust CUST.img
target max-download-size: 254MB
sending 'cust' (196335 KB)...
OKAY [ 6.493s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 6.493s
Cant flash cust. How did you do that?
Click to expand...
Click to collapse
Yes, it is working perfectly.
Hi, sorry for hijacking a thread but I thought it'd be better than making a new one.
I did pretty much the same as the OP, unlocked the bootloader, flashed TWRP recovery, rooted and then stupidly tried to do an official update on the phone (I believe it was kiw-l21c432b140)
The phone is just now stuck at the boot screen, I can get into fastboot mode but cannot use ADB, says device isn't found no matter what I try. I also tried putting stock firmware on the SD card and going into download mode (EMUI) but it just says software install failed.. Any help appreciated, only got the phone today and have spent longer trying to fix it than I have using it..
Thanks!
tomblast66 said:
Hi, sorry for hijacking a thread but I thought it'd be better than making a new one.
I did pretty much the same as the OP, unlocked the bootloader, flashed TWRP recovery, rooted and then stupidly tried to do an official update on the phone (I believe it was kiw-l21c432b140)
The phone is just now stuck at the boot screen, I can get into fastboot mode but cannot use ADB, says device isn't found no matter what I try. I also tried putting stock firmware on the SD card and going into download mode (EMUI) but it just says software install failed.. Any help appreciated, only got the phone today and have spent longer trying to fix it than I have using it..
Thanks!
Click to expand...
Click to collapse
As long as you are able to boot into fastboot you still have hope
Are you able to get into TWRP? (Power + Vol up) If yes, download the L-21 stock rom in the file repository thread and flash it. In all likelihood, that will solve any corruption of system files. If not, read on.
Did you check if you have installed the ADB drivers? I am assuming it should have been installed considering you flashed TWRP, but better to check and reinstall. Device not found is usually a driver error. Alternatively, you can install HiSync, it refreshes and replaces the drivers needed for Honor 5X. Further to installing that, try adb fastboot commands and flash the stock recovery using the steps in this post:
http://forum.xda-developers.com/showpost.php?p=65659088&postcount=5
nandakalyan said:
As long as you are able to boot into fastboot you still have hope
Are you able to get into TWRP? (Power + Vol up) If yes, download the L-21 stock rom in the file repository thread and flash it. In all likelihood, that will solve any corruption of system files. If not, read on.
Did you check if you have installed the ADB drivers? I am assuming it should have been installed considering you flashed TWRP, but better to check and reinstall. Device not found is usually a driver error. Alternatively, you can install HiSync, it refreshes and replaces the drivers needed for Honor 5X. Further to installing that, try adb fastboot commands and flash the stock recovery using the steps in this post:
http://forum.xda-developers.com/showpost.php?p=65659088&postcount=5
Click to expand...
Click to collapse
When I do power and vol up I get EMUI recovery, not TWRP I put the stock rom on the SD card and tried to install it and it just says "Software install failed" and the only option is to shut the phone down again.
I had all the ADB drivers installed, will reinstall it all and see if it helps. When I run adb now and use the "adb devices" command it just says "List of devices attached" and doesn't show anything..
tomblast66 said:
When I do power and vol up I get EMUI recovery, not TWRP I put the stock rom on the SD card and tried to install it and it just says "Software install failed" and the only option is to shut the phone down again.
I had all the ADB drivers installed, will reinstall it all and see if it helps. When I run adb now and use the "adb devices" command it just says "List of devices attached" and doesn't show anything..
Click to expand...
Click to collapse
Oh then you have stock recovery, are you using the update.app provided by Huawei? Or using any ROMs/images posted here? It is possible that you may have a corrupted download, look up the Huawei site for downloads in the support section for your region and download the official update.app, try with that
nandakalyan said:
Oh then you have stock recovery, are you using the update.app provided by Huawei? Or using any ROMs/images posted here? It is possible that you may have a corrupted download, look up the Huawei site for downloads in the support section for your region and download the official update.app, try with that
Click to expand...
Click to collapse
It wasn't stock recovery before, after the phone updated it went back to stock and wouldn't boot. I downloaded the firmware from http://forum.xda-developers.com/honor-5x/development/stock-kiw-l24-l21-t3312684 and that's what I try to install through recovery and it says there's an error, a load of other texts flashes up before it says error but it's too quick to read. When I have better internet I'll re-download it in case it was corrupt. Thanks for your help, hopefully I can get it fixed as I only just got this to replace my old phone. Would be a shame to spend the money on it and have no use from the device.. Just wish the computer would detect through adb as I can get into fastboot easily enough.
tomblast66 said:
It wasn't stock recovery before, after the phone updated it went back to stock and wouldn't boot. I downloaded the firmware from http://forum.xda-developers.com/honor-5x/development/stock-kiw-l24-l21-t3312684 and that's what I try to install through recovery and it says there's an error, a load of other texts flashes up before it says error but it's too quick to read. When I have better internet I'll re-download it in case it was corrupt. Thanks for your help, hopefully I can get it fixed as I only just got this to replace my old phone. Would be a shame to spend the money on it and have no use from the device.. Just wish the computer would detect through adb as I can get into fastboot easily enough.
Click to expand...
Click to collapse
Sure, we all help each other
BTW, just to be sure, you using the single "Update.app" file, that runs into a couple of gigs or the extracted one? You can't flash extracted Update.app through stock recovery.
HiSync (the official Huawei tool) also provides an option to recover the phone, tried that?
nandakalyan said:
Sure, we all help each other
BTW, just to be sure, you using the single "Update.app" file, that runs into a couple of gigs or the extracted one? You can't flash extracted Update.app through stock recovery.
HiSync (the official Huawei tool) also provides an option to recover the phone, tried that?
Click to expand...
Click to collapse
It's the single one, about 2.66GB I believe, I tried the recovering through the Huawei tool and it says "Your device is not supported for system recovery".
tomblast66 said:
It's the single one, about 2.66GB I believe, I tried the recovering through the Huawei tool and it says "Your device is not supported for system recovery".
Click to expand...
Click to collapse
Oops! I am no techie, so am at the end of my wits, but thing I do suspect is a corrupted download, so if you can try downloading the file again from a stable connection and try is all I can think of. I've had this corrupted file thing quite a few times, so suggesting.

Problem solved. Thanks!

Problem already solved. Thanks!
Hi everyone, this is Sarry. I got my new huawei mate 9 pro on Wednesday this week, the version is LON-L29C636, I was trying to flash a custom ROM into the phone, but unfortunately I was too careless, flashed a different version ROM into it and cause immediate start up loop. As I finally boot into fastboot and twrp rec mode, I noticed that the computer won't recognize the USB portal of the device. So I went in eRecovery mode and tried to download an updated version but it failed to find any useful version.
Since mate 9 pro doesn't support SD card, I brought a USB-OTG cable and also usb type-c microSD adapter, when I connected the sd card to the phone, twrp reads the information, but when I tried to flash the update.zip file, it failed. I tried to copy the dload folder with update.app by twrp into phone storage, even if I got successful, the file just disappeared when i refresh the page. So now I don't have any idea on how to unbrick the phone, felt really bad.
Feel free to ask me any question or information needed, I really hope to unbrick the phone, I've been using huawei cellphone for more then 2 years and love it very much. Thanks for the help!!
Hello,
well the situation isn't that hard actually, you may just get the stock image and flash it from fastboot then start the custom rom installation from scratch.
what is the error number or statement?
EDIT: you will need huawei update extractor to pull out the img files and flash them through fastboot
Another Edit:
in the file path choose the update.app
you will need the following partitions:
Boot
System
Recovery
^select these then right click and press `extract selected` and flash them using the following commands:
1- fastboot devices > to check the device
2- fastboot flash boot boot.img
3- fastboot flash recovery recovery.img
4- fastboot flash system system.img
hope this helps you
good luck!
TheShadowMC said:
Hello,
well the situation isn't that hard actually, you may just get the stock image and flash it from fastboot then start the custom rom installation from scratch.
what is the error number or statement?
EDIT: you will need huawei update extractor to pull out the img files and flash them through fastboot
Another Edit:
in the file path choose the update.app
you will need the following partitions:
Boot
System
Recovery
^select these then right click and press `extract selected` and flash them using the following commands:
1- fastboot devices > to check the device
2- fastboot flash boot boot.img
3- fastboot flash recovery recovery.img
4- fastboot flash system system.img
hope this helps you
good luck!
Click to expand...
Click to collapse
Thank you so much for the help! The fastboot script isn't really working because when I tried to run it in cmd, it shows 'error can't find device', so I tried to flash the img files with twrp, the boot.img and recovery.img works well, but the system.img cannot be flashed, and the error message shows 'E:\cannot flash system.img'. I also tried to download the full version firmware and created dload folder in my SD card, copied UPDATE.APP into the folder, tried the 3 button force update, still nothing worked. Now the seller send me an Email said I can return the product, they are going to charge me for some ROM re installation fee.
However what error does it give during flashing system.IMG I would like to know, also as well as twrp custom ROM flashing?
Aquarius_2333 said:
Thank you so much for the help! The fastboot script isn't really working because when I tried to run it in cmd, it shows 'error can't find device', so I tried to flash the img files with twrp, the boot.img and recovery.img works well, but the system.img cannot be flashed, and the error message shows 'E:\cannot flash system.img'. I also tried to download the full version firmware and created dload folder in my SD card, copied UPDATE.APP into the folder, tried the 3 button force update, still nothing worked. Now the seller send me an Email said I can return the product, they are going to charge me for some ROM re installation fee.
Click to expand...
Click to collapse
well brother about the driver issue, sorry about being late, you must have downloaded the fastboot drivers and installed them.

[TUTORIAL] Manually Install / Flash 7.11 NOUGAT Even To Unbrick A ZE553KL Zenfone

MANUALLY INSTALLING FULL NOUGAT 7.11 FIRMWARE 2018/03/15(security_patch 2018-02-05) (RECOVERY, BOOT, SYSTEM) Even If Its Soft Bricked Because You Messed Up Somewhere. Files Here Are For Asus Zenfone 3 Zoom ZE553KL Z01HD WW Sku .
Its The Last Nougat Update Before Oreo Was Released.
MORE FIRWARES HERE
Story Time:
As I Remember It.....Condensed Version, This Was Over A Few Days Of Trial And Error, Mainly Because Adb SideLoad Refused To Flash Asus's Stock Firmware Zip Files.
I Messed Up My Friends Asus Zenfone 3 Zoom, ZE553KL.
He Bought Used, He Quickly Updated To Oreo From Within The Phones Update But Was Having Missed Texts And Slow Lte(4g) Speeds, He Wasnt Sure If It Happened On Nougat Which The Phone Was On Originally.
Downgraded To 6.01, Installed Twrp, Magisk, Still Having Same Issues, Flashing An Update Zip W/a Modded Updater Script Via Twrp Caused A Soft Bricked Phone, It Never Completed The Flash, Twrp Backup Didnt Work, Factory Reset A No Go, Couldn't Manually Flash Stock Rom As Adb Sideload Always Gave Errors, Fastboot System images Didnt Help For One Reason Or Another, Phone Was Just Bootlooping Back To The Unlocked Bootloader Menu.
Down Loaded Alot Of Stuff, Read Countless Pages, And Somehow Got The Right Firmware Files(recovery, boot, system img files) That Was Flashable Via Fastboot Extracted From A Zip, My Fix Is Below. These Are Not My Files But I Cant Remember Where I Got Them From As I Dl-ed Alot Of Stuff Trying To Get This Phone To A Running State. No I Havent Tried Oreo Yet, He Has His Phone Back Now And Not Sure When He'll Let Me Play With It Again, Lol.
UPDATE TO THIS STORY
HOWTO FLASH
PREREQUISITES:
Make A Nandroid Backup
If Bootable Remove/Signout Of Google Account
(Might Work With Locked Bootloader, IDK)
Ze553kl(Zenfone3 Zoom) Phone With Unlocked Bootloader(used unlocker apk from asus website when phone was in running state)
Unlocking Bootloader App Available From Asus - was for upto nougat 7.11
Usb Asus Drivers
Usb Debugging Enabled On Phone, Maybe Not But Wont Hurt To Try
Adb Fastboot Program(Included)
Recovery, Boot, And System Img Files Of Nougat 7.11(Included)
Computer Running Windows
Usb Data Cable For Phone
ON PHONE-
If Bootable Enable Usb Debugging, Uncheck Verify Apps Via Usb, Install From Unknown Sources, Remove Google Account
Backup Internal Sdcard - Most Def
Remove Sdcard, Just In Case
Put Phone Into Fast Boot Mode- Unplugged, Phone Powered Off - Vol Up + Power Button Pressed, Hold Both Until Screen Comes On.
Plug Usb In Cable To Phone From Pc.
ON COMPUTER-
From The Download Section Below Dl ADB_FASTBOOT_1.4.1.ZIP File And Extract It Into A New Empty Folder.
Download And Copy The Three .Img Files From The Download Section Below Into This New Adb Folder
HOW TO RUN ADB VIA COMMAND PROMPT? -
From Within Adb-fastboot Folder You Created, Nothing Selected, Hold Down The Shift Key Then Use The Right Mouse Button To Click In Empty Space In The Adb-fastboot Folder, Select "Open Command Window Here" From The Menu That Pops Up.
From Within Command Prompt Type-
Adb Devices
It Should Output A Device With A String Of Letters And Numbers, Thats Your Phone.
Next Steps Will Install Nougat 7.11 And Consequently Wipe Your Phone
Run These 5 "fastboot" Commands One At A Time.
When Each Step Is Completed Run The Next Command, You Can Copy And Paste These Five (5) Fastboot Commands Into The Command Prompt Window
----------------------------------------------------------------------
1.
Code:
fastboot flash recovery recovery-zoom-7.11.img
2.
Code:
fastboot flash boot boot-zoom-7.11.img
3.
this one @ ~4gb will take awhile to initialize and complete, patience needed
CAN REDO THIS SYSTEM FLASH NOW TO MAKE SURE IT "STICKS"
Code:
fastboot flash system system-zoom-7.11.img
4.
wipes internal sdcard
Code:
fastboot format userdata
5.
Code:
fastboot reboot
-------------------------------------------------------------------------------------------
if you were successfull it will boot into 7.11, takes about 3-5 mins to boot.
IF DID NOT FLASH PROPERLY OR ODD BEHAVIOR AFTER REBOOT THEN REDO STEPS AGAIN....ELSE KEEP READING!
------------------------------------------------------------------------
IF STILL BRICKED OR ODD BEHAVIOR BUT CAN BOOT TO BOOTLOADER/FASTBOOT THEN DO THESE COMMANDS WHEN IN FASTBOOT MODE
Code:
fastboot erase system
fastboot erase recovery
fastboot erase boot
fastboot erase userdata
fastboot -w
fastboot erase splash
fastboot erase cache
THEN RE-BOOT BACK INTO BOOTLOADER AND DO THE FLASH FOR 7.11 FIRMWARE
STILL HAVING ISSUES, RESTORE USING TECH FW THAT REFLASHES ALL MDMS, RADIOS, DRIVERS ETC FROM HERE
[FW] 7.1.1 & 6.0.1 Service Tech Firmwares - Debrick - Upgrade - Downgrade
- -------------------------------------------------------------------------------------
disclaimer im not responsible for yours or anyone elses devices, do at your own risk
DOWNLOADS
PHONE FILES ARE FROM A Asus Zenfone 3 Zoom ZE553KL WW SKU FIRMWARE Version WW-71.60.139.30 2018/03/15
RECOVERY-ZOOM-7.11.IMG
md5 03d8358e1341a73b5a492c12e3dbe39e
BOOT-ZOOM-7.11.IMG
md5 1ad55f9852d56b79a95654173af5649a
SYSTEM-ZOOM-7.11.IMG
md5 7217f778701c988271739ab18fb0fb30
ADB_FASTBOOT_1.4.1.ZIP
..
Thanks for the information...
I can provide you latest system,boot, recovery.img files if you want...
Do you know how to make raw firmware?? Because that could come handy for hard bricked phones.
Deleted. Double post
Naman Vashishth said:
Thanks for the information...
I can provide you latest system,boot, recovery.img files if you want...
Do you know how to make raw firmware?? Because that could come handy for hard bricked phones.
Click to expand...
Click to collapse
What do u mean by raw. In what format is it in.
I've converted oreo stock firmware .dat files to .img files but I can't test them as I don't have the phone. My friend seems happy on nougat and I don't think he'll let me flash it on his phone.
I haven't tried dl-ing official stock and seeing if phone will see it as an update to manually self install via nougat recovery or maybe to try adb sideload again.
Naman Vashishth said:
I can provide you latest system,boot, recovery.img files if you want...
Click to expand...
Click to collapse
Please do - I could sure use them.
Work very well !
ciao
God bless you! You made my quite dead phone, live again!
Thank you
I can't update to Oreo via ota... do you know why?
the op here. lol, my friend dropped the phone and now its dead screen, no display/no touch but phone still works.
he doesnt want to get a screen for it as it will cost almost as much as he paid for it.......so its mine now.
been flashing stuff to it, gave it a very hard soft brick, still dealing with that.
my goal was to run it remotely but get adb/usb debugging enabled and get pc trusted by phone. i thought he wanted to sell it as is but decided to give to me to do whatever i want to it
got out of the hard soft brick, installed twrp, use twrp cli, twrp backups and restore, rooted w/magisk, installed 6.0.1 (fluked it), 7.11 using my method above with the extra erase commands, removed frp, got adb /usb debugging enabled and device adb authorized by hacking , got vysor, a remote control mirroring app running, all without a working screen.
i'll write up a tut for any1 else that needs help. fyi, weak screen if dropped even short distance, but he had no cover, but pretty to hard to brick it, imo, ymmv
So can i downgrade my phone from android 8 to 7.1.1 following this process.
kingairtel08 said:
So can i downgrade my phone from android 8 to 7.1.1 following this process.
Click to expand...
Click to collapse
yes, i went from 8.0 to 7.11 then to 6.01
more fw here https://forum.xda-developers.com/ze...fw-7-11-6-0-1-service-tech-firmwares-t3850000
Bro i am on 8.0 and want to unlock bootloader and root it n enable cam2api in it, as unlocker nt working in android 8.0 so i want to back to 7.1.1. thank u bro,i will try it tonight.
Bro installed successfully 7.1.1 but microphone sound stopped.when calling cant hear anything.what to do ?unlock tool not working on it.
kingairtel08 said:
Bro installed successfully 7.1.1 but microphone sound stopped.when calling cant hear anything.what to do ?unlock tool not working on it.
Click to expand...
Click to collapse
after flashing did u, in stock recovery, do a factory reset and wipe caches aka wipe user data in fastboot.
else do a complete wipe as outlined in op
yes bro i m on stock recovery ,did wipe cache etc.
kingairtel08 said:
yes bro i m on stock recovery ,did wipe cache etc.
Click to expand...
Click to collapse
does etc mean factory reset?
did u do the extra procedure to completely erase everything as posted in op in the section of when still having issues
yes bro. i followed all steps .
kingairtel08 said:
yes bro.
Click to expand...
Click to collapse
yes to which
this?
fastboot erase system
fastboot erase recovery
fastboot erase boot
fastboot erase userdata
fastboot -w
fastboot erase splash
fastboot erase cache
if yes then do a full restore of radio, mdm etc from here using method 1 or 2
https://forum.xda-developers.com/att-s7-edge/how-to/fw-7-11-6-0-1-service-tech-firmwares-t3850000
i did all this steps then flash firmware img.
kingairtel08 said:
i did all this steps then flash firmware img.
Click to expand...
Click to collapse
which method did u use from the link i posted
bro i dnt have the 7.1..1 zip file ,i used ur 7.1.1.img file,used method 2.
i will try once again ,wil reply within 2hours.
bro i want to unlock my phone whats why i downgrade,but after downgrading checked official unlock tool gives the same network error that gives on android 8.0.is there any way to unlock it on this 7.1.1 firmware?

Rmx2086 full brick (resolved)

Hello,
My realme x3 superzoom is fully bricked.
I got some luck, it is detected as qualcomm 9008
So basicall,if someone have the .mbn file and all the RAW Program and Patch files in .XML, it could greatly help me..
Anyway thanks for your help or even an advice.
Hello,
A little update.
Rn i can go in fastboot but still not in recovery
Im stuck pls help
Hello everyone,
Big update,
I finally made it...
Disclaimer :
I'm not responsible of anything happening to your phone, you are taking those steps at your own risk ...
So if like me you were having a hardbricked phone, follow those steps ( /!\ only if not possible to go to fastboot or bootloader mode, if possible go to next steps) :
- Install QFil ( search for tutorial to know how to set it up good)
- Download the original firmware file ( /!\ NOT THE OZIP BUT THE OFP)
- Extract the ofp file ( need the installation of ofp extractor and python 3)
- Put the phone in EDL mode ( if i remember correctly, you need to press all three button for like more than 20 sec)
- You will need qualcomm driver since your phone will be detected as a com port (Qualcomm HS-USB QDLoader 9008).
- Once you did all those steps, start qfil ( do the firehose config before => select ufs in storage type ), select the
prog_firehose_ddr.elf of YOUR DEVICE in the build selection, then select the rawprogram.xml and the patch.xml
(there should be 5 file for each, select them all)
- Once you did this reboot your phone in EDL mode and as soon as you saw the port is dectected, select download.
- If u get a firehose error => not the good files
- If u get a sahara error then do all of this again but make sur to reboot your phone in EDL mode two
seconds before downloading in QFIL
- If it works => your phone is supposed to boot
If like me for an unknow reason it doesnt work then next steps (FASTBOOT).
For some reason it didnt work fully but it restored fastboot ( got some luck i guess)
So i was able to boot my phone in fastboot/bootloader mode
Once you are in fastboot mode :
- Download the original firmware file ( /!\ NOT THE OZIP BUT THE OFP)
- Extract it with the same method as described earlier.
- You should see a lot of .img, dont worry
- You will need vbmeta.img, recovery.img, boot.img, dtbo.img AND ALL THE super****.img
- Once you find those files, copy past them to a clean folder in order to not mess up.
- On the firmware i found, its a total of 14 super***.img and vbmeta.img, recovery.img, boot.img and dtbo.img.
- Once its in a clean folder, start a cmd and go to this folder ( cd diskname:\..\foldername )
For myself, i flashed the super file in the "order it was given" in the ProFile.xml
- Then you will have to flash all those files
- To flash the super : fastboot flash super super**.img
- To flash the recovery : fastboot flash recovery recovery.img
- To flash the boot : fastboot flash boot boot.img
- To flash dtbo : fastboot flash dtbo dtbo.img
- To flash vbmeta : fastboot flash vbmeta vbmeta.img
Once you are finished flashing those files, your phone should be able to boot ( first go to recovery and wipe
all data in order to not have broken/corrupted files ).
If you have any question, feel free to ask ^^
Please make a video...it has too many complicated step...
Mrinal Mondal said:
Please make a video...it has too many complicated step...
Click to expand...
Click to collapse
Will maybe do it in august if I have time
Plahad said:
Hello everyone,
Big update,
I finally made it...
Disclaimer :
I'm not responsible of anything happening to your phone, you are taking those steps at your own risk ...
So if like me you were having a hardbricked phone, follow those steps ( /!\ only if not possible to go to fastboot or bootloader mode, if possible go to next steps) :
- Install QFil ( search for tutorial to know how to set it up good)
- Download the original firmware file ( /!\ NOT THE OZIP BUT THE OFP)
- Extract the ofp file ( need the installation of ofp extractor and python 3)
- Put the phone in EDL mode ( if i remember correctly, you need to press all three button for like more than 20 sec)
- You will need qualcomm driver since your phone will be detected as a com port (Qualcomm HS-USB QDLoader 9008).
- Once you did all those steps, start qfil ( do the firehose config before => select ufs in storage type ), select the
prog_firehose_ddr.elf of YOUR DEVICE in the build selection, then select the rawprogram.xml and the patch.xml
(there should be 5 file for each, select them all)
- Once you did this reboot your phone in EDL mode and as soon as you saw the port is dectected, select download.
- If u get a firehose error => not the good files
- If u get a sahara error then do all of this again but make sur to reboot your phone in EDL mode two
seconds before downloading in QFIL
- If it works => your phone is supposed to boot
If like me for an unknow reason it doesnt work then next steps (FASTBOOT).
For some reason it didnt work fully but it restored fastboot ( got some luck i guess)
So i was able to boot my phone in fastboot/bootloader mode
Once you are in fastboot mode :
- Download the original firmware file ( /!\ NOT THE OZIP BUT THE OFP)
- Extract it with the same method as described earlier.
- You should see a lot of .img, dont worry
- You will need vbmeta.img, recovery.img, boot.img, dtbo.img AND ALL THE super****.img
- Once you find those files, copy past them to a clean folder in order to not mess up.
- On the firmware i found, its a total of 14 super***.img and vbmeta.img, recovery.img, boot.img and dtbo.img.
- Once its in a clean folder, start a cmd and go to this folder ( cd diskname:\..\foldername )
For myself, i flashed the super file in the "order it was given" in the ProFile.xml
- Then you will have to flash all those files
- To flash the super : fastboot flash super super**.img
- To flash the recovery : fastboot flash recovery recovery.img
- To flash the boot : fastboot flash boot boot.img
- To flash dtbo : fastboot flash dtbo dtbo.img
- To flash vbmeta : fastboot flash vbmeta vbmeta.img
Once you are finished flashing those files, your phone should be able to boot ( first go to recovery and wipe
all data in order to not have broken/corrupted files ).
If you have any question, feel free to ask ^^
Click to expand...
Click to collapse
Good evening!
I've got my device bricked and i follow your guide hoping to fix it, on qfil i got errors so I try with the fastboot method, but after installing all the .img i still can't boot the phone,
Something changed anyway, before I was only able to enter the fastboot mode, now after this if I turn on the phone normally it remains stuck on the first "realme" logo, and pressing - or + can I access fastboot mode or recovery, so things are getting better but still no boot on system, before follow your guide I wasn't even able to format or flash the partition system because it was telling me it wasn't existing, now it exists, but if I try to flash a stock firmware trough fastboot it telling me that there's not enough space on device... I'm a bit stuck too! What can I try?
Bob45ultras said:
Good evening!
I've got my device bricked and i follow your guide hoping to fix it, on qfil i got errors so I try with the fastboot method, but after installing all the .img i still can't boot the phone,
Something changed anyway, before I was only able to enter the fastboot mode, now after this if I turn on the phone normally it remains stuck on the first "realme" logo, and pressing - or + can I access fastboot mode or recovery, so things are getting better but still no boot on system, before follow your guide I wasn't even able to format or flash the partition system because it was telling me it wasn't existing, now it exists, but if I try to flash a stock firmware trough fastboot it telling me that there's not enough space on device... I'm a bit stuck too! What can I try?
Click to expand...
Click to collapse
Hello,
It seems that the storage partition is corrupted
If u can access recovery, try to format the phone and then try again the steps
If u still have no luck with this, reply and I'll try to help u more
Best
Plahad said:
Hello,
It seems that the storage partition is corrupted
If u can access recovery, try to format the phone and then try again the steps
If u still have no luck with this, reply and I'll try to help u more
Plahad said:
Hello,
It seems that the storage partition is corrupted
If u can access recovery, try to format the phone and then try again the steps
If u still have no luck with this, reply and I'll try to help u more
Best
Click to expand...
Click to collapse
Thanks for your reply! I format from the recovery and I repeated the steps but same problem!
Click to expand...
Click to collapse
Plahad said:
Hello,
It seems that the storage partition is corrupted
If u can access recovery, try to format the phone and then try again the steps
If u still have no luck with this, reply and I'll try to help u more
Best
Click to expand...
Click to collapse
Thanks for your reply! I format from recovery and I repeated the steps but same problem!
Bob45ultras said:
Thanks for your reply! I format from recovery and I repeated the steps but same problem!
Click to expand...
Click to collapse
Be very carefull with those next command, it will wipe out completely your devices :
fastboot erase system
fastboot erase userdata
fastboot erase boot
fastboot erase cache
Plahad said:
Be very carefull with those next command, it will wipe out completely your devices :
fastboot erase system
fastboot erase userdata
fastboot erase boot
fastboot erase cache
Click to expand...
Click to collapse
I tried to do that, but it gave me an error when I was trying to erase system and cache, anyway I access fastbootd and I format from them successfully, anyway normal fastboot still can't format system partition.
After that I tried again your guide trough fastboot, re-flashed all files and it still doesn't work,
don't really know what to do, I found a stock firmware flashable trough fastboot and I tried also with that to see if it can solve the problems, but also that it fail, when I try to flash system I receive an error
Bob45ultras said:
I tried to do that, but it gave me an error when I was trying to erase system and cache, anyway I access fastbootd and I format from them successfully, anyway normal fastboot still can't format system partition.
After that I tried again your guide trough fastboot, re-flashed all files and it still doesn't work,
don't really know what to do, I found a stock firmware flashable trough fastboot and I tried also with that to see if it can solve the problems, but also that it fail, when I try to flash system I receive an error
Click to expand...
Click to collapse
Hello,
You can try to install a custom recovery like ofox
Were you on android 10 or 11 ?
Plahad said:
Hello,
You can try to install a custom recovery like ofox
Were you on
Click to expand...
Click to collapse
I'm on Android 11
I followed your steps with the fastboot way but now my phone can't enter both fastboot and recovery,is there anything i can still do?
Or I should just take it to somewhere to repair?
Plahad said:
Hello everyone,
Big update,
I finally made it...
Disclaimer :
I'm not responsible of anything happening to your phone, you are taking those steps at your own risk ...
So if like me you were having a hardbricked phone, follow those steps ( /!\ only if not possible to go to fastboot or bootloader mode, if possible go to next steps) :
- Install QFil ( search for tutorial to know how to set it up good)
- Download the original firmware file ( /!\ NOT THE OZIP BUT THE OFP)
- Extract the ofp file ( need the installation of ofp extractor and python 3)
- Put the phone in EDL mode ( if i remember correctly, you need to press all three button for like more than 20 sec)
- You will need qualcomm driver since your phone will be detected as a com port (Qualcomm HS-USB QDLoader 9008).
- Once you did all those steps, start qfil ( do the firehose config before => select ufs in storage type ), select the
prog_firehose_ddr.elf of YOUR DEVICE in the build selection, then select the rawprogram.xml and the patch.xml
(there should be 5 file for each, select them all)
- Once you did this reboot your phone in EDL mode and as soon as you saw the port is dectected, select download.
- If u get a firehose error => not the good files
- If u get a sahara error then do all of this again but make sur to reboot your phone in EDL mode two
seconds before downloading in QFIL
- If it works => your phone is supposed to boot
If like me for an unknow reason it doesnt work then next steps (FASTBOOT).
For some reason it didnt work fully but it restored fastboot ( got some luck i guess)
So i was able to boot my phone in fastboot/bootloader mode
Once you are in fastboot mode :
- Download the original firmware file ( /!\ NOT THE OZIP BUT THE OFP)
- Extract it with the same method as described earlier.
- You should see a lot of .img, dont worry
- You will need vbmeta.img, recovery.img, boot.img, dtbo.img AND ALL THE super****.img
- Once you find those files, copy past them to a clean folder in order to not mess up.
- On the firmware i found, its a total of 14 super***.img and vbmeta.img, recovery.img, boot.img and dtbo.img.
- Once its in a clean folder, start a cmd and go to this folder ( cd diskname:\..\foldername )
For myself, i flashed the super file in the "order it was given" in the ProFile.xml
- Then you will have to flash all those files
- To flash the super : fastboot flash super super**.img
- To flash the recovery : fastboot flash recovery recovery.img
- To flash the boot : fastboot flash boot boot.img
- To flash dtbo : fastboot flash dtbo dtbo.img
- To flash vbmeta : fastboot flash vbmeta vbmeta.img
Once you are finished flashing those files, your phone should be able to boot ( first go to recovery and wipe
all data in order to not have broken/corrupted files ).
If you have any question, feel free to ask ^^
Click to expand...
Click to collapse
my phone just open bootloader and apply the second step but no thing repair, my phone is RMX2086 any one can help me please
Do you have the Firehose , rawprogram and patch files that you can post to try to do it by qfil ?
Plahad said:
Hello everyone,
Big update,
I finally made it...
Disclaimer :
I'm not responsible of anything happening to your phone, you are taking those steps at your own risk ...
So if like me you were having a hardbricked phone, follow those steps ( /!\ only if not possible to go to fastboot or bootloader mode, if possible go to next steps) :
- Install QFil ( search for tutorial to know how to set it up good)
- Download the original firmware file ( /!\ NOT THE OZIP BUT THE OFP)
- Extract the ofp file ( need the installation of ofp extractor and python 3)
- Put the phone in EDL mode ( if i remember correctly, you need to press all three button for like more than 20 sec)
- You will need qualcomm driver since your phone will be detected as a com port (Qualcomm HS-USB QDLoader 9008).
- Once you did all those steps, start qfil ( do the firehose config before => select ufs in storage type ), select the
prog_firehose_ddr.elf of YOUR DEVICE in the build selection, then select the rawprogram.xml and the patch.xml
(there should be 5 file for each, select them all)
- Once you did this reboot your phone in EDL mode and as soon as you saw the port is dectected, select download.
- If u get a firehose error => not the good files
- If u get a sahara error then do all of this again but make sur to reboot your phone in EDL mode two
seconds before downloading in QFIL
- If it works => your phone is supposed to boot
If like me for an unknow reason it doesnt work then next steps (FASTBOOT).
For some reason it didnt work fully but it restored fastboot ( got some luck i guess)
So i was able to boot my phone in fastboot/bootloader mode
Once you are in fastboot mode :
- Download the original firmware file ( /!\ NOT THE OZIP BUT THE OFP)
- Extract it with the same method as described earlier.
- You should see a lot of .img, dont worry
- You will need vbmeta.img, recovery.img, boot.img, dtbo.img AND ALL THE super****.img
- Once you find those files, copy past them to a clean folder in order to not mess up.
- On the firmware i found, its a total of 14 super***.img and vbmeta.img, recovery.img, boot.img and dtbo.img.
- Once its in a clean folder, start a cmd and go to this folder ( cd diskname:\..\foldername )
For myself, i flashed the super file in the "order it was given" in the ProFile.xml
- Then you will have to flash all those files
- To flash the super : fastboot flash super super**.img
- To flash the recovery : fastboot flash recovery recovery.img
- To flash the boot : fastboot flash boot boot.img
- To flash dtbo : fastboot flash dtbo dtbo.img
- To flash vbmeta : fastboot flash vbmeta vbmeta.img
Once you are finished flashing those files, your phone should be able to boot ( first go to recovery and wipe
all data in order to not have broken/corrupted files ).
If you have any question, feel free to ask ^^
Click to expand...
Click to collapse
Does your guide only apply to Realme with unlocked Bootloader or to all?
Ian94y said:
I followed your steps with the fastboot way but now my phone can't enter both fastboot and recovery,is there anything i can still do?
Or I should just take it to somewhere to repair?
Click to expand...
Click to collapse
If u cant enter fastboot, i'll suggest that u either find a way arounds with QFIL or else if not comfortable go to repair it somewhere
aliabdullah1230 said:
my phone just open bootloader and apply the second step but no thing repair, my phone is RMX2086 any one can help me please
Click to expand...
Click to collapse
Hello, did u download the good firmwares for your phone ?
I have an rmx2086 too, and i managed to made it work by doing what i did with those commends
felixpaz1992 said:
Do you have the Firehose , rawprogram and patch files that you can post to try to do it by qfil ?
Click to expand...
Click to collapse
I'm sorry, I'm not currently in my home, i'll try do find those when i'll get back, in 4 months

Categories

Resources