Huawei recently shipped update B180.
They advised to unroot the phone first, but I have been stupid and updated with TWRP installed on the second recovery partition (e-recovery?) and the update failed.
My phone now won't boot. I can put it in fastboot/recovery mode and access TWRP, so I guess all I need is a stock ROM.
I cannot find anything useful for Honor 7 with Google, I would like a recent ROM (most recent I found is a B130).
I would also appreciate some advice on how to recover from this boot freeze.
Would flashing a stock ROM with TWRP be enough?
Thank you very much.
I'm kinda pissed since that phone is quite expensive.
You cannot flash a stock rom with TWRP.
You have to flash the stock recovery then a stock rom, using fastboot.
The more recent stock rom available is the B130, unfortunatly.
Have a look at my posts, I have done similar (although I had the normally recovery.img installed) you need to downgrade using the marshmallow downgrade ROM then to the full 121 or 130 ROM after putting the stock recovery back (for the version your phone was on before this happened I assume it was 170 if you were going to 180) once you are back on 130 you can then upgrade up to 180 through the usual process. I have done this a few times and it has been fine whilst experimenting with the device.
The current version of the phone appears to be burned in to it (I think curver.img is doing this inside the UPDATE.APP but I haven't found a way of flashing this file back to the phone to play around with downgrading without the MM downgrade ROM), this I think is what causes it to hang if it has a boot.img and recovery.img that does not match the version the phone thinks it is.
I am in the same boat with @rbuccia.
I can only access fastboot and recovery (twrp).
I also found that I must have something wrong with 3rdmodem because if i wipe form inside twrp I always get an error message on that partition.
Also I have a rom from Kangvip flashable with twrp but veven this has no effect.
I think that we cannot unbrick it without a completely and full stock rom but I think there is no one.
Any idea?
This method should work for the above, first we need to get your device to boot. The following should work... Extract UPDATE.APP from the B180 ROM and then extract boot.img and recovery.img using Huawei Update Extract. Now extract the UPDATE.APP from the full 130 ROM and extract system.img using the Huawei image extractor. Once you have them 3 files, place them in the same folder as your fastboot installation and do the following...
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
This should give you a working bootable phone, it will be a mess half 180 for Kernel etc... and the system itself will be 130 but it should boot. Then place the MM downgrade ROM into the dload folder on your SDCARD and run the update process, it will crash at 95% this is fine the phone will boot back up. Now place the UPDADTE.APP from 130 in the dload folder and run the update again, this should flash and give you a fully functioning normal system running version 130, then follow the update process to get back to 180.
The modem will get flashed as part of the 130 update package so hopefully that will resolve that issue for you as well.
james194zt said:
This method should work for the above, first we need to get your device to boot. The following should work... Extract UPDATE.APP from the B180 ROM and then extract boot.img and recovery.img using Huawei Update Extract. Now extract the UPDATE.APP from the full 130 ROM and extract system.img using the Huawei image extractor. Once you have them 3 files, place them in the same folder as your fastboot installation and do the following...
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
This should give you a working bootable phone, it will be a mess half 180 for Kernel etc... and the system itself will be 130 but it should boot. Then place the MM downgrade ROM into the dload folder on your SDCARD and run the update process, it will crash at 95% this is fine the phone will boot back up. Now place the UPDADTE.APP from 130 in the dload folder and run the update again, this should flash and give you a fully functioning normal system running version 130, then follow the update process to get back to 180.
The modem will get flashed as part of the 130 update package so hopefully that will resolve that issue for you as well.
Click to expand...
Click to collapse
Thanks for the tips, but
1. Where can i download the B180 full firmware?
2. I can't access the VOL+ VOL- POWer AKA updater mode, it just bootloops.
Thx :laugh:
Its on one of the threads at the top of General all the firmwares are there, no you don't need to do the vol+/- thing, just power power it down and then hold power up whilst plugging in to your PC. If this works the device will load up in fastboot and you should be able to flash what you need, to do the above the bootloader will need to be unlocked but you can do that from fastboot.
If your device is in a boot loop plug it in via USB to your PC and keep holding the volume up and when it reboots eventually it will go in to fastboot.
james194zt said:
Its on one of the threads at the top of General all the firmwares are there, no you don't need to do the vol+/- thing, just power power it down and then hold power up whilst plugging in to your PC. If this works the device will load up in fastboot and you should be able to flash what you need, to do the above the bootloader will need to be unlocked but you can do that from fastboot.
If your device is in a boot loop plug it in via USB to your PC and keep holding the volume up and when it reboots eventually it will go in to fastboot.
Click to expand...
Click to collapse
I must be blind, but i can only find the ota updates, not the full stock firmware :/
Thx tho, i'm starting to understand a bit better how it works and how i can fix it.
I'll just try to flash boot and recovery for B100 and B130 untill i cant make it work, for the system.app tho i can't take the B180 as i can't find it.
You need to use the system.img from B130 it is located here https://mega.nz/#!PlpXnLxD!azPTqEscNnwuSdrjpJJKO9zkyCpzAl7d6w3OpYx1se8 once you have this follow the above process and you should end up with a phone thats working and has the correctly matching firmware. Make sure you do it all though, just because it will boot with a mismatched boot loader and system.img doesn't mean you should keep it that way, it could be unstable and will cause issues with future upgrades.
james194zt said:
You need to use the system.img from B130 it is located here https://mega.nz/#!PlpXnLxD!azPTqEscNnwuSdrjpJJKO9zkyCpzAl7d6w3OpYx1se8 once you have this follow the above process and you should end up with a phone thats working and has the correctly matching firmware. Make sure you do it all though, just because it will boot with a mismatched boot loader and system.img doesn't mean you should keep it that way, it could be unstable and will cause issues with future upgrades.
Click to expand...
Click to collapse
Thx for the reply ! But that's what i said earlier, when i flash boot.img, system.img and recovery.img from the B130 update.app, the phone still bootloops.
I have access to the Huawei E-recovery if i do VOL+ POWER while the phone is plugged in the pc
I have access to the fastboot mode if i do VOL- POWER while the phone is plugged in he pc
I DON'T have access to the software mode upgrader if i do VOL+ VOL- POWER, no matter is the phone is plugged in or not
The phone still bootloops, plugged in or not.
:/
You need to flash boot.img and recovery.img from 180 and system.img from 130, sorry if that was not clear above! the boot loop is being caused because the boot.img doesn't match the version your phone thinks its on, if 180 doesn't work try the version before you upgraded i.e. 170 the system.img is just the android OS if you see HONOR glowing then you are booting system.img at that point but if it isn't glowing then you are still in the bootloader at that point so you need to sort out boot.img.
I've never been in 180, and as i said, i can't take the boot and recovery.img from the OTA update, i need a full stock firmware of B180 ! :/
Thx for the help tho.
I already tried to flash boot.img from B100 b121 and B130, and the phone still bootloops :/
http://forum.xda-developers.com/hon...dating-to-b180-fastboot-t3317249#post65420964
This fixed it!
Found this and it worked for me.
Download latest Official Full ROM from EMUI's site, HuaweiUpdateExtractor and adb / fastboot.
2. Unzip ROM and open UPDATE.APP with HuaweiUpdateExtractor.
3. Extract SYSTEM.img and RECOVERY.img (delete .header files that HuaweiUpdateExtractor generates you need only .img files) and put them in adb folder.
4. Boot in fastboot and conect to PC. (You can achieve this from TWRP to boot to bootloader, adb dosent work but fastboot will there is also key combination to get to bootloader/repair mode or what it is).
5. Open cmd.exe from adb folder and type (or copy-paste) the follow commands one by one:
Code:
fastboot devices
Code:
fastboot flash recovery RECOVERY.img
Code:
fastboot flash system SYSTEM.img
And finally where i had some trouble:
If you got no permissions try again or take usb cable off etc. Took me while to get back from same situtation. Few reboots to TWRP and to bootloader and USB replugging while in bootloader.
And for LINUX: i used split_updata.pl-master from github to extract the .APP/Firmware needed to sudo fastboot aswell.
Hiiiii guys
Please help me respected sir and other friends.
Anyone have twrp backup of stock rom ?
Because I want go back to stock rom and I have only twrp not pc please thanks in advance
yesterday i formatted my HONOR 5x via TWRP .
now my device without OS , and every time REBOOT it from recovery mode it says : NO OS , ARE YOU SURE YOU WANT TO REBOOT
guys i need the official ROM for my Phone so i can install it
My phone name : Huawi Honor 5x L-21
Please save me !! :crying::crying:
Trustive said:
yesterday i formatted my HONOR 5x via TWRP .
now my device without OS , and every time REBOOT it from recovery mode it says : NO OS , ARE YOU SURE YOU WANT TO REBOOT
guys i need the official ROM for my Phone so i can install it
My phone name : Huawi Honor 5x L-21
Please save me !! :crying::crying:
Click to expand...
Click to collapse
everything you need is in the Repository in my signature
if you want to reinstall the official rom {emui} you need to also install the stock recovery
Follow these steps to flash Stock ROM:
Download your phone's latest firmware and extract system.img, boot.img, recovery.img, cust.img from UPDATE.APP using Huawei Update Extractor tool.
Boot into bootloader mode by switching off the phone then pressing only the Vol DOWN button, and connecting it to PC simultaneously.
Flash recovery first, using this command.
Code:
fastboot flash recovery recovery.img
Flash all other extracted files similarly firing these commands.
Code:
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash system system.img
After doing this put that very UPDATE.APP from which you extracted the files in dload folder of your external SDCARD.
Switch off your phone, and press Vol UP + Vol DOWN + Power button simultaneously.
Your device will now get to the full stock firmware.
NOTE: If the manual flashing doesn't works or you get any errors, then first try only the force update method, i.e Putting the UPDATE.APP from which you extracted the files in dload folder of your external SDCARD and pressing Vol UP + Vol DOWN + Power button simultaneously after switching off your phone.
Hello dear people !! ^^
Since we have in a short time Android 10
We don't have recovery for it.. Sadly enough but..
I found this on a chinese forum and make a guide of it.
I don't own the Xperia 1.. Not yet but next week i have one,
So i hope all you people understand this guide because i
explained it as far i can do it.
----------------------
.. Requirements ..
Unlocked bootloader
Xperia 1 Or 5
Android 10
Knowledge howto flash
----------------------
Important !!: rename your patched boot.img what you did
with magisk to kernel.img in put it in this zip Here
1: Remember to back up all your data
2: Make a clean install of the firmware,
!! don't boot after flashing !!
3: Turn the phone into fastboot mode
and connect and type this command in cmd window:
fastboot flash boot twrp-xperia1.img
Here the fastboot twrp file
4: fastboot this command of vbmeta:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Here the vbmeta file
5: Press and hold the volume down and power at the same time,
release the powerbutton but keep
pressing volume down button till you enter twrp.
6: Copy the 3 zips:
The boot.zip where your own kernel.img is inside
what you did at the beginnig of these steps
twrp-Xperia1-3.3.x.zip: Here
Magisk-v20.1.zip: Here
to the phone storage, and flash in twrp
7: Start it up and done
Note: If you encountered
damaged internal storage, format internal memory in twrp
and all went just fine.
... Credits ...
M-Rom
Res
This doesn't lead to success with an Xperia 5. Once you try to boot into TWRP at step 5, you got a note that the device is corrupt and will shut down in 5 seconds.
Thanks ASap people try this I will install and try it! Know bug? Is this still in very testing version? For the moment I don't want to touch my device.
The clean install is necessary? Any incompatibilities with some magisk modules? Im currently using: smali patcher, taichi, youtube vanced
Why isn't there a Thread in the Xperia 5 Forums? Just found this out of Luck...
Instructions are also bit confusing... Where is the vbmeta.img from? Google? And why do i need a boot.img if we have already a TWRP boot.img? Will the one boot.img not replace the other?
Flashing a new Firmware makes also no sense if you just do "fastboot -w" to erase all Userdata. (If coming from a clean Firmware like i do, or You do right after unlocking Your Device)
Edit: So in a nutshell
-We do boot up the twrp boot.img to be able to flash Zips!?
-We do flash vbmeta to unsecure our booting!?
-We do flash our own boot.img with the Zip that the Device can work right!?
-We do flash the TWRP Zip which edits our Ramdisks to add TWRP
-We do flash Magisk (Optional!?) for only Root? Or also needed Kernel changes!?
Would be nice to also make links to XperiFirm and UnSin to get the boot images...
You could also edit the boot.zip script for "magisk_patched.img" so users don't have to rename it
Just want to support that btw. Thanks for Your work anyways!
---------- Post added at 15:47 ---------- Previous post was at 15:07 ----------
Xperia 5 booted well into TWRP but it freezes everytime i start a flash or wipe. Got the storage to work with fastboot -w after flashing the twrp and vbmeta images. Adb Sideload does also not work. Looking forward to a working version!
TWRP unable to flash zips
Well, the title says it all. I can flash the twrp image, but it freezes when flashing zips or starting sideload. I'm using a J9110. I understand you're not supporting here, but just in case you had some tips. Oh and by the way, hoi vanuit Leiden
EDIT: Found the fix: don't change the language to english before opening twrp, and it will flash just fine!
xperia 5 fix plz
I've installed this, it work but boot in chinese and cant load the usb mtp driver on my pc, I cant move the boot.zip to flash, had it put on sd card, cant find the sd card on this crappy twrp, for me is a no. I'd just stick with patched boot until something better will work.
mtp should work if you follow every instruction and boot twrp in chinese.
Having the same issue as others... it appears as though the internal storage is encrypted, but I have no lock screen enabled in the ROM. No Passwords or Fingerprint either. Tried wiping data from within TWRP froze the system. Performed a wipe from within ROM, and now the ROM shows internal data folders as though they're encrypted. Need a pinch of help here.
This method has problem if 55.1.A.3.149 is flashed. The "Start" screen freeze with no touchscreen function on reboot after the procedures completed.
Is there any update to this?
Hopefully with 3.4 will bring a more stable twrp. It includes changes for devices updated to Android 10
I hope can teach how to get your patched boot.img
It's not too much complex to make it work
download firmware from xperiFirm
unsign the boot.sin to get boot.img for your xperia 1
flash the twrp.img to your boot slot_a/b
boot into twrp
install the boot.img, twrp.zip, magisk.zip
now everything works
benben233 said:
I hope can teach how to get your patched boot.img
Click to expand...
Click to collapse
It's not too hard to get one
Get the origin boot.img from xperiFirm, twrp.zip
boot into any twrp on any device
backup your own boot paritition
install the boot.img, twrp one by one
then backup the boot partition, you get the patched-boot.img
Tenhow.XDA said:
download firmware from xperiFirm
unsign the boot.sin to get boot.img for your xperia 1
flash the twrp.img to your boot slot_a/b
boot into twrp
install the boot.img, twrp.zip, magisk.zip
now everything works
Click to expand...
Click to collapse
On latest android 10 and fw .28 it works ? @Tenhow.XDA
Any sign of Android 11 TWRP for Xperia 1?
MrMmmkay said:
Any sign of Android 11 TWRP for Xperia 1?
Click to expand...
Click to collapse
No
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