Question Lenovo Legion Duel 2 Stuck on Fastboot screen after QFIL (Bootloop) - Lenovo Legion Phone Duel 2

Can anyone help? For the life of me I can't get it to go into recovery mode or anything of the like after attempting a flash of official firmware.

It's not being picked up by ADB, fastboot OR Lenovo's smart recovery crap.

brownie96 said:
Can anyone help? For the life of me I can't get it to go into recovery mode or anything of the like after attempting a flash of official firmware.
Click to expand...
Click to collapse
This also happened to my Legion Duel 2 after using RSA.. its stuck on FastBoot.. tried connecting to RSA again and an error saying "Doesn't match the appropriate software"

my Duel 2 is now stucked on FastBoot and cant select other options like START or Recovery Mode..
Now im trying to use QFil but im having an error:
"Download fail: Sahara Fail: QSaharaServer Fail: Process Fail"
Btw these are the files in the ROM 12.5.188ST thats appearing when selecting PROGRAMMER:
and on the XML:
Patch:
Tried:
prog_firehose_ddr.elf
rawprogram_unparsed0 (also tried selecting all files)
patch0 (also tried selecting all files)
Sorry this is my 1st time doing this stuff and i have no idea..
Hope someone can help me fix my Duel 2. Thank you

try flashing a meta build with the ddr firehose, then fastboot flash your persist image. its worked for me twice now

ฉันลองทุกขั้นตอนแล้วแต่ทำไม่ได้ โปรดอธิบายโดยละเอียดว่าคืออะไร

ฉันลองทุกขั้นตอนแล้วแต่ทำไม่ได้ โปรดอธิบายโดยละเอียดว่าคืออะไร

ฉันลองทุกขั้นตอนแล้วแต่ทำไม่ได้ โปรดอธิบายโดยละเอียดว่าคืออะไร

waabby said:
Duel 2 ของฉันติดอยู่ที่ FastBoot และไม่สามารถเลือกตัวเลือกอื่น ๆ เช่น START หรือ Recovery Mode..
ตอนนี้ฉันกำลังพยายามใช้ QFil แต่มีข้อผิดพลาด:
"การดาวน์โหลดล้มเหลว: Sahara ล้มเหลว: QSaharaServer ล้มเหลว: กระบวนการล้มเหลว"
View attachment 5518121
นี่เป็นไฟล์ใน ROM 12.5.188ST ที่ปรากฏขึ้นเมื่อเลือกโปรแกรมเมอร์:
View attachment 5518125
และใน XML:
View attachment 5518129
ปะ:
View attachment 5518131
พยายาม:
prog_firehose_ddr.elf
rawprogram_unparsed0 (ลองเลือกไฟล์ทั้งหมดด้วย)
patch0 (ลองเลือกไฟล์ทั้งหมดด้วย)
ขออภัย นี่เป็นครั้งแรกที่ฉันทำสิ่งนี้และฉันไม่รู้ ..
หวังว่าใครบางคนสามารถช่วยฉันแก้ไข Duel 2 ของฉันได้ ขอบคุณ
Click to expand...
Click to collapse
ใน Qfil การกำหนดค่า ให้ใน UFS

try going into your firehose options and select erase all before flashing. other than that im uploading all the partitions ive made copies of using qfil. You can try flashing them over one by one in qfil or see if fastboot flash will work . https://mega.nz/folder/TqxSjYrD#l3GM8SQgJcxhVrSeXMLW7Q

tinman4209333 said:
try going into your firehose options and select erase all before flashing. other than that im uploading all the partitions ive made copies of using qfil. You can try flashing them over one by one in qfil or see if fastboot flash will work . https://mega.nz/folder/TqxSjYrD#l3GM8SQgJcxhVrSeXMLW7Q
Click to expand...
Click to collapse
great work, its really appreciated. will these work on cn and global roms? or are they rom specific? and would it be possible to write a fastboot flashable script to make flashing the partitions easier? (for noobs like me who don't know how to flash them all manually) thanks again

Lizzo said:
great work, its really appreciated. will these work on cn and global roms? or are they rom specific? and would it be possible to write a fastboot flashable script to make flashing the partitions easier? (for noobs like me who don't know how to flash them all manually) thanks again
Click to expand...
Click to collapse
completely forgot to specify which rom it was lol. its global
if you use fastboot flash commands you just go off of the file name . fastboot flash boot boot_a.bin fastboot flash vbmeta vbmeta_a.bin . im pretty sure you can reuse the same file for both partitions. fastboot flash boot_a boot.bin | fastboot flash boot_b boot_a.bin etc. to make a windows script you'd write out each command in notepad then save it as a bat file.
You can also install them all manually using qfil.
-1. put phone into edl mode
-2. select firehose_ddr under the flatbuild section
-3. click on tools / partition manager
-4. right click a partition
-5. manage partition data
-6. load image (if you want you can erase the partition before loading the image )
-7. pick matching file, it immediately flashes it to your phone
-8. rinse and repeat
how i got out of the bootlop was using the file from rescue smart assistant. id flash it in qfil using the meta build option, and ddr firehose. then boot up into the bootloader and flash a persist image I had previously saved. if it doesnt work for you I can upload that image and see if that helps

tinman4209333 said:
completely forgot to specify which rom it was lol. its global
if you use fastboot flash commands you just go off of the file name . fastboot flash boot boot_a.bin fastboot flash vbmeta vbmeta_a.bin . im pretty sure you can reuse the same file for both partitions. fastboot flash boot_a boot.bin | fastboot flash boot_b boot_a.bin etc. to make a windows script you'd write out each command in notepad then save it as a bat file.
You can also install them all manually using qfil.
-1. put phone into edl mode
-2. select firehose_ddr under the flatbuild section
-3. click on tools / partition manager
-4. right click a partition
-5. manage partition data
-6. load image (if you want you can erase the partition before loading the image )
-7. pick matching file, it immediately flashes it to your phone
-8. rinse and repeat
how i got out of the bootlop was using the file from rescue smart assistant. id flash it in qfil using the meta build option, and ddr firehose. then boot up into the bootloader and flash a persist image I had previously saved. if it doesnt work for you I can upload that image and see if that helps
Click to expand...
Click to collapse
thanks a lot. i can try that. are you in the legion group on telegram? we could sure use your help lol
Lenovo legion pro duel comentarios y más
You can view and join @lenovolegiongamers right away.
t.me

tinman4209333 said:
try going into your firehose options and select erase all before flashing
Click to expand...
Click to collapse
I would not recommend that step.

&(*) said:
I would not recommend that step.
Click to expand...
Click to collapse
I had the same issue of it not flashing and it fixed the problem . When your stuck with a $500+ paperweight and nothing else works ya get kind of desperate after awhile lol. Figured it'd have a better chance of working with a clean slate then trying to write over something that's broken

tinman4209333 said:
try flashing a meta build with the ddr firehose, then fastboot flash your persist image. its worked for me twice now
Click to expand...
Click to collapse
how do you fast boot flash. mine not connecting to fast boot
my qfil flashes work but still no boot

kofijordan said:
how do you fast boot flash,
Click to expand...
Click to collapse
Make sure the device is off, hold the volume down button and turn it on, will boot into the loader menu, plug in to usb side port and type fastboot reboot fastboot, it will reboot into fastbootd and now can flash through fastboot.

&(*) said:
Make sure the device is off, hold the volume down button and turn it on, will boot into the loader menu, plug in to usb side port and type fastboot reboot fastboot, it will reboot into fastbootd and now can flash through fastboot.
Click to expand...
Click to collapse
i tried both qfil and fast boot same issue

Windows or Linux? If windows, look in Device manager when you do fastboot reboot fastboot and see if there is an exclamation in the list of devices, if so you will need to update the driver manually to android adb device (which is also the driver for fastboot). Which model do you own, Duel 2 or Pro 2? Have you tried Lenovo's RSA software tool since adb works? Use RSA only if it is a Duel 2, if it's a Pro 2 you will have to gather the right bundle posted on another thread (do not use it if you don't know as it can cause further issues).

kofijordan said:
i tried both qfil and fast boot same issue
Click to expand...
Click to collapse
Windows or Linux? If Windows, look in Device manager when you do fastboot reboot fastboot and see if there is an exclamation in the list of devices, if so you will need to update the driver manually to android adb device (which is also the driver for fastboot). Which model do you own, Duel 2 or Pro 2? Have you tried Lenovo's RSA software tool since adb works? Use RSA only if it is a Duel 2, if it's a Pro 2 you will have to gather the right bundle posted on another thread (do not use it if you don't know as it can cause further issues).

Related

[FIXED] So I bricked Mate 10 lite

Hi,
Here is a long story of bricking my device, I wanted to downgrade my device from Oreo to Nougat, and somehow I installed wrong software, mine is RNE-L21 and after successful downgrade with this method:
https://www.youtube.com/watch?v=_3vqb8hPZIQ
version of software I installed: RNE-L21C461B153CUSTC461D001
my device was NEO-something, in settings it showed 3GB of RAM instead of 4GB, screen resolutution 1280x720 instead of fullHD and 32GB of internal memory instead of 64, so I wanted to change that.
This time I downloaded (not so sure about this now) proper version of firmware: RNE-L21C432B135CUSTC432D001, and used another method because previous method didnt work, link:
https://forum.xda-developers.com/showpost.php?p=76503686&postcount=46
the HuRUpdater scrpit worked fine, I booted up the device and nothing was changed, so I was like, well, ok then.
but then I noticed that my bootloader was locked, so I wanted to unlock it, and after typing the *fastboot oem unlock code* and selecting yes on my device, It rebooted and just stuck at the "Powered by andriod" logo.
I was trying to enter TWRP but id doesnt work, its stuck at the loading screen, I was unable to enter fastboot, but now I figured out that when I discharge it, I'm able to enter fastboot.
So now I'm stuck, I don't know what should I do.
I saw a guide for flashing .img files from UPDATE.APP, but that guide was for Oreo, and I've got diffrent .img files inside my Nougat UPDATE.APP so I don't want to risk:
https://forum.xda-developers.com/mate-10/help/mate-10-lite-bricked-t3794236
sentavn said:
you should format by using fastboot. First download your stock ROM and extract with Huawei Firmware Extracter. Select UPDATE.APP and extract following files:
erecovery_kernel.img
erecovery_ramdisk.img
erecovery_vbmeta.img
cust.img
erecovery_vendor.img
kernel.img
ramdisk.img
recovery_vbmeta.img
recovery_vendor.img
system.img
Reboot your device in to fastboot mode (recovery mode) and flash those files one by one:
fastboot flash erecovery_kernel erecovery_kernel.img
...
fastboot flash system system.img
//
Erase your userdata space:
fastboot -w
//reboot
fastboot reboot
Now go to your stock recovery and do factory reset, wide cache.
Now your device back to stock OREO
Click to expand...
Click to collapse
Any Ideas?
HOW I FIXED:
I downloaded this EMUI 5 Nougat, Thanks to bozka1:
https://androidhost.ru/5SZ
I extracted UPDATE.APP file using Huawei Update Extractor.
I was trying to flash everything via fastboot: BOOT.img, RECOVERY.img, RECOVERY2.img, CUST.img, SYSTEM.img but nothing helped me.
I found out what you can flash via fastboot here:
https://forum.xda-developers.com/general/general/huawei-fastboot-commands-t3850123
There was no hope for me, so I tried to flash USERDATA.img
fastboot flash userdata USERDATA.img
Click to expand...
Click to collapse
And then cmd promped something unusual:
target reported max download size of 471859200 bytes
sending 'userdata' (24576 KB)...
OKAY [ 0.646s]
writing 'userdata'...
(bootloader) success to erase cryypt info in oeminfo
OKAY [ 1.401s]
finished. total time: 2.049s
Click to expand...
Click to collapse
Then I proceeded to flash: BOOT.img, RECOVERY.img, RECOVERY2.img and CACHE.img
I didn't flash SYSTEM.img because I flashed it before like 1500 times.
My phone didn't work yet so I used the DLOAD method because RECOVERY finally worked, so I shut down the device and used three buttons combo:
First holding Volume Up, Volume Down and then pressing Power Button.
There is a documentation in the firmware I downloaded, SDcard must be in exFAT format.
Thank You bozka1.
voltzero2 said:
Hi,
Here is a long story of bricking my device, I wanted to downgrade my device from Oreo to Nougat, and somehow I installed wrong software, mine is RNE-L21 and after successful downgrade with this method:
https://www.youtube.com/watch?v=_3vqb8hPZIQ
version of software I installed: RNE-L21C461B153CUSTC461D001
my device was NEO-something, in settings it showed 3GB of RAM instead of 4GB, screen resolutution 1280x720 instead of fullHD and 32GB of internal memory instead of 64, so I wanted to change that.
This time I downloaded (not so sure about this now) proper version of firmware: RNE-L21C432B135CUSTC432D001, and used another method because previous method didnt work, link:
https://forum.xda-developers.com/showpost.php?p=76503686&postcount=46
the HuRUpdater scrpit worked fine, I booted up the device and nothing was changed, so I was like, well, ok then.
but then I noticed that my bootloader was locked, so I wanted to unlock it, and after typing the *fastboot oem unlock code* and selecting yes on my device, It rebooted and just stuck at the "Powered by andriod" logo.
I was trying to enter TWRP but id doesnt work, its stuck at the loading screen, I was unable to enter fastboot, but now I figured out that when I discharge it, I'm able to enter fastboot.
So now I'm stuck, I don't know what should I do.
I saw a guide for flashing .img files from UPDATE.APP, but that guide was for Oreo, and I've got diffrent .img files inside my Nougat UPDATE.APP so I don't want to risk:
https://forum.xda-developers.com/mate-10/help/mate-10-lite-bricked-t3794236
Any Ideas?
Click to expand...
Click to collapse
What is your original location, C461?
Which oeminfo you have flashed?
bozka1 said:
What is your original location, C461?
Which oeminfo you have flashed?
Click to expand...
Click to collapse
My original location is C432, I don't remember flashing any oeminfo
voltzero2 said:
My original location is C432, I don't remember flashing any oeminfo
Click to expand...
Click to collapse
Single SIM/dual SIM ?
Try reboot your phone into fastboot mode and use command
fastboot oem get-build-number
you'll see the number of your current firmware
bozka1 said:
Single SIM/dual SIM ?
Try reboot your phone into fastboot mode and use command
fastboot oem get-build-number
you'll see the number of your current firmware
Click to expand...
Click to collapse
It's dual sim,
the number of current firmware: System 5.1.0.98(08K5)
voltzero2 said:
It's dual sim,
the number of current firmware: System 5.1.0.98(08K5)
Click to expand...
Click to collapse
Okay, phone still locked ? What shows the screen in fastboot mode - phone and FRP ?
bozka1 said:
Okay, phone still locked ? What shows the screen in fastboot mode - phone and FRP ?
Click to expand...
Click to collapse
It says its unlucked:
https://imgur.com/a/LEDKWFr
I hope this link works
Download oeminfo
https://mega.nz/#!w4cX1QwT!TuFmfultDMDPt2b5yekrWREls7o5tSpveQFiWkBX6zg
Copy it to SD card.
Download TWRP
https://mega.nz/#!IodXAKBB!_VrqsMSxVw_NkXwfUIQb32mG_QAMd4HQ8_BtqmeHI94
and Service ROM
https://androidhost.ru/5SZ
. Extract dload folder from Service ROM and copy it to SD card.
Try to install TWRP: Copy the downloaded TWRP file to the Minimal ADB and fastboot folder, reboot to fastboot mode . Launch Minimal ADB , In the command window, enter the following commands one by one
- fastboot devices - this command will verify connection in fastbot mode (you will see your serial number)
-fastboot flash recovery2 TWRP-MATE.img
-fastboot reboot - the device will reboot
Now you can boot into TWRP mode using button Volume Up after rebooting.
Reboot to TWRP, Select Install, navigate to oeminfoRNE-L21C432 and confirm. Go back to the TWRP main menu, select Reboot and Power Off.
Now you can try flash the Service ROM with three buttons combo. GL!
bozka1 said:
Download oeminfo
https://mega.nz/#!w4cX1QwT!TuFmfultDMDPt2b5yekrWREls7o5tSpveQFiWkBX6zg
Copy it to SD card.
Download TWRP
https://mega.nz/#!IodXAKBB!_VrqsMSxVw_NkXwfUIQb32mG_QAMd4HQ8_BtqmeHI94
and Service ROM
https://androidhost.ru/5SZ
. Extract dload folder from Service ROM and copy it to SD card.
Try to install TWRP: Copy the downloaded TWRP file to the Minimal ADB and fastboot folder, reboot to fastboot mode . Launch Minimal ADB , In the command window, enter the following commands one by one
- fastboot devices - this command will verify connection in fastbot mode (you will see your serial number)
-fastboot flash recovery2 TWRP-MATE.img
-fastboot reboot - the device will reboot
Now you can boot into TWRP mode using button Volume Up after rebooting.
Reboot to TWRP, Select Install, navigate to oeminfoRNE-L21C432 and confirm. Go back to the TWRP main menu, select Reboot and Power Off.
Now you can try flash the Service ROM with three buttons combo. GL!
Click to expand...
Click to collapse
So I'll have to wait a little before I'll download Service ROM, my internet connection isn't the greatest, but I flashed Your TWRP and unfortunately it doesn't work;
If I hold the Power button and Volume Up - the same story as before, I see the loading TWRP screen and nothing happends,
If I let the device to boot up and then press only the Volume Up button - it says "Your device is booting up" and nothing happens.
By the way, what can happen when I'll use "fastboot flash recovery something.img" instead of recovery2?
EDIT:
I did some testing and Your TWRP doesn't boot at all on my device, I flashed another one, Catuva21 3.1.1 Nougat, and that is the one that I had before - it is booting but never loads.
voltzero2 said:
By the way, what can happen when I'll use "fastboot flash recovery something.img" instead of recovery2?
Click to expand...
Click to collapse
TWRP will automatically overwrite Stock recovery, it's impossible to flash something from dload without Stock recovery .
Using command "recovery2" you will install TWRP over eRecovery .
Try flash Service ROM from SD card without TWRP & oeminfo flashing, but Im not sure... your system is heavily damaged and incomplete .
bozka1 said:
TWRP will automatically overwrite Stock recovery, it's impossible to flash something from dload without Stock recovery .
Using command "recovery2" you will install TWRP over eRecovery .
Try flash Service ROM from SD card without TWRP & oeminfo flashing, but Im not sure... your system is heavily damaged and incomplete .
Click to expand...
Click to collapse
So the phone would boot up the TWRP without pressing anything? Damn, I might have done that typo error... Do You know if I can restore the stock recovery from the UPDATE.APP file? I mean flash it
voltzero2 said:
So the phone would boot up the TWRP without pressing anything? Damn, I might have done that typo error... Do You know if I can restore the stock recovery from the UPDATE.APP file? I mean flash it
Click to expand...
Click to collapse
Use Huawei Update Extractor and extract RECOVERY.img , copy it to the "Minimal ADB and fastboot" folder . Command :
fastboot flash recovery RECOVERY.img
bozka1 said:
Use Huawei Update Extractor and extract RECOVERY.img , copy it to the "Minimal ADB and fastboot" folder . Command :
fastboot flash recovery RECOVERY.img
Click to expand...
Click to collapse
Yeah, I've done it already, unfortunately nothing changed. How about BOOT.img? Can this influence something?
EDIT:
I also wonder about just following the steps in my first post, I've got UPDATE.APP for Oreo, but I don't know if it will only make it worse.
bozka1 said:
Download oeminfo
https://mega.nz/#!w4cX1QwT!TuFmfultDMDPt2b5yekrWREls7o5tSpveQFiWkBX6zg
Copy it to SD card.
Download TWRP
https://mega.nz/#!IodXAKBB!_VrqsMSxVw_NkXwfUIQb32mG_QAMd4HQ8_BtqmeHI94
and Service ROM
https://androidhost.ru/5SZ
. Extract dload folder from Service ROM and copy it to SD card.
Try to install TWRP: Copy the downloaded TWRP file to the Minimal ADB and fastboot folder, reboot to fastboot mode . Launch Minimal ADB , In the command window, enter the following commands one by one
- fastboot devices - this command will verify connection in fastbot mode (you will see your serial number)
-fastboot flash recovery2 TWRP-MATE.img
-fastboot reboot - the device will reboot
Now you can boot into TWRP mode using button Volume Up after rebooting.
Reboot to TWRP, Select Install, navigate to oeminfoRNE-L21C432 and confirm. Go back to the TWRP main menu, select Reboot and Power Off.
Now you can try flash the Service ROM with three buttons combo. GL!
Click to expand...
Click to collapse
Do I have to install oeminfo to be able to use the "three buttons combo"? Because I tried it today and it doesn't work, phone is just stuck at "Your device is booting.." screen, guess I'm out of luck
I fixed it, solution will be attached to first post.
Thanks to bozka1 who gave me this helpful link:
https://androidhost.ru/5SZ
voltzero2 said:
I fixed it, solution will be attached to first post.
Thanks to bozka1 who gave me this helpful link:
https://androidhost.ru/5SZ
Click to expand...
Click to collapse
You're welcome
Hi help me
Bozka1
My huawei mate 10 lite is brick stock on erecovery what can i do now
Lj08 said:
My huawei mate 10 lite is brick stock on erecovery what can i do now
Click to expand...
Click to collapse
Hi, have you tried to do something with your phone? Can you provide some info?
voltzero2 said:
Hi, have you tried to do something with your phone? Can you provide some info?
Click to expand...
Click to collapse
Voltzero2
I try factory reset wipe catch and no result just going back to erecovery
Lj08 said:
Voltzero2
I try factory reset wipe catch and no result just going back to erecovery
Click to expand...
Click to collapse
Alright, so did it just happened randomly or did you tried to do something with your phone? Did you unlocked bootloader or flashed custom recovery etc? You need to explain what happened, that's quite important if you want someone to help you.

Is my phone harbricked? No fastboot, no recovery

Hi All,
I've been crawling the web the past few days to find a solution to my problem and unfortunately I didn't...
I have a Asus Zenfone 3 Max ZC520TL MT6737M, I never did a custom OS installation before and didn't know anything about how phone works except the Linux kernel
After 2 or 3 weeks playing with custom rom and recovery, softbrick, fastboot and adb I finally successfully intalled a custom OS, I wanted lineageOS but only found an Himax image working properly (with bluetooth., etc) for my phone and TWRP as custom recovery.
I setted my parameters for all my applications and after inserting my SIM card the network was not working, I tried a factory reset from the phone and then I got stuck in twrp however the way I booted, I tried flashing the os again, the recovery again wiping/formatting data, I was still stuck in TWRP
Then I executed :
fastboot format:ext4 cache
fastboot format:ext4 boot
And now I can't boot nor in twrp nor in fastboot, I can't access the bootloader using power and volume up, and my phone bootloop
Is there a way to get to fastboot to reinstall the recovery and then from here the os or is my phone hardbricked with no future, ready for trash?
Thank you
rominail said:
then I executed :
fastboot format:ext4 boot
Click to expand...
Click to collapse
You completely destroyed phone's boot-loader, what is comparable to a computer's BIOS.
What do you expect? IMO phone is case for the e-waste.
rominail said:
Hi All,
I've been crawling the web the past few days to find a solution to my problem and unfortunately I didn't...
I have a Asus Zenfone 3 Max ZC520TL MT6737M, I never did a custom OS installation before and didn't know anything about how phone works except the Linux kernel
After 2 or 3 weeks playing with custom rom and recovery, softbrick, fastboot and adb I finally successfully intalled a custom OS, I wanted lineageOS but only found an Himax image working properly (with bluetooth., etc) for my phone and TWRP as custom recovery.
I setted my parameters for all my applications and after inserting my SIM card the network was not working, I tried a factory reset from the phone and then I got stuck in twrp however the way I booted, I tried flashing the os again, the recovery again wiping/formatting data, I was still stuck in TWRP
Then I executed :
fastboot format:ext4 cache
fastboot format:ext4 boot
And now I can't boot nor in twrp nor in fastboot, I can't access the bootloader using power and volume up, and my phone bootloop
Is there a way to get to fastboot to reinstall the recovery and then from here the os or is my phone hardbricked with no future, ready for trash?
Thank you
Click to expand...
Click to collapse
You NEVER format your boot partition as ext4 it's a raw boot.img which holds the kernel and ramdisk. You should really do research and follow instructions alittle better than that.. unfortunately I don't think your device can be saved and if you flashed aboot or sbl1/2/3 then your SOL
Thanks
Thank you for your answers!
I don't know why I did that (sometimes I have crazy bad ideas), I didn't see that on internet
rominail said:
Thank you for your answers!
I don't know why I did that (sometimes I have crazy bad ideas), I didn't see that on internet
Click to expand...
Click to collapse
That's okay! Please so make sure you do some research if your new to the custom OS scene.. it's always good to learn new things
maybe you can flash again like from the factory by using the default flashing and ROM tools.
BryanHafidz said:
maybe you can flash again like from the factory by using the default flashing and ROM tools.
Click to expand...
Click to collapse
If your in a Qualcomm chipset and you have an EDL programmer that works for your device I have custom tools in my cloud storage to create an EDL firmware if you don't ready have one. If your on MTK then there is Sugar MTK or SP flash tool that can work. If your an another one you may be out of luck as it seems nobody has been able to restore those chipsets
EDIT: I do have a whole zip file of programmers and one that I use for my LG Zone 2 (msm8x10.mbn)
TheExploitedOne said:
You NEVER format your boot partition as ext4 it's a raw boot.img which holds the kernel and ramdisk. You should really do research and follow instructions alittle better than that.. unfortunately I don't think your device can be saved and if you flashed aboot or sbl1/2/3 then your SOL
Click to expand...
Click to collapse
we have the same problem but I didn't do like you.
I entered these commands
*fastboot flash recovery boot.img (I'm stupid lol)
*fastboot flash boot boot.img
*fastboot reboot*
mahirab23 said:
we have the same problem but I didn't do like you.
I entered these commands
*fastboot flash recovery boot.img (I'm stupid lol)
*fastboot flash boot boot.img
*fastboot reboot*
Click to expand...
Click to collapse
What seems to be going on after the flash?
TheExploitedOne said:
What seems to be going on after the flash?
Click to expand...
Click to collapse
the biggest problem is i have reset the phone and i am stuck with this message: "to start android enter your password". I entered the correct password but another message appears with a reset phone option.
Since the recovery.img file is no longer in the system, the phone keeps making this loop.
mahirab23 said:
the biggest problem is i have reset the phone and i am stuck with this message: "to start android enter your password". I entered the correct password but another message appears with a reset phone option.
Since the recovery.img file is no longer in the system, the phone keeps making this loop.
Click to expand...
Click to collapse
If you can get into fastboot run the following:
fastboot erase recovery
fastboot erase userdata
fastboot format:ext4 userdata
Then reflash your recovery
TheExploitedOne said:
If you can get into fastboot run the following:
fastboot erase recovery
fastboot erase userdata
fastboot format:ext4 userdata
Then reflash your recovery
Click to expand...
Click to collapse
I can't get into fastboot.
another solution?????
mahirab23 said:
I can't get into fastboot.
another solution?????
Click to expand...
Click to collapse
Can you access EDL mode?
TheExploitedOne said:
Can you access EDL mode?
Click to expand...
Click to collapse
thank you for your attention and suggestions.
I haven't tried this method yet.
I'm not good with EDL mode
Can SP tools and MiracleBox help me?
mahirab23 said:
thank you for your attention and suggestions.
I haven't tried this method yet.
I'm not good with EDL mode
Can SP tools and MiracleBox help me?
Click to expand...
Click to collapse
MiracleBox and QPST yes
TheExploitedOne said:
MiracleBox and QPST yes
Click to expand...
Click to collapse
good !!!: o: o
can you develop the method with Miracle Box and QPST ? please!!!
mahirab23 said:
good !!!: o: o
can you develop the method with Miracle Box and QPST ? please!!!
Click to expand...
Click to collapse
I have the tools needed in my cloud I can make into a zip file. You'll need to also do some research on your part but I can also write a readme file too so you have a basic understanding. Just give me a few to get the link
EDIT:
Here you go this has all you'll need for flashing your device in EDL as well as create the firmware if needed
https://mega.nz/file/rc8CVIiB#qnM3_ZzrvCJtp_M7Y9ZftZqDtGgWeN0tqFrLlT30pws
TheExploitedOne said:
MiracleBox and QPST yes
Click to expand...
Click to collapse
thank you
I finally managed to reset the phone thanks to SoftwareDownload
thank you really. you are really kind and available:bien::bien::bien:
mahirab23 said:
thank you
I finally managed to reset the phone thanks to SoftwareDownload
thank you really. you are really kind and available:bien::bien::bien:
Click to expand...
Click to collapse
Absolutely good sir! I'm glad that I can help
TheExploitedOne said:
If your in a Qualcomm chipset and you have an EDL programmer that works for your device I have custom tools in my cloud storage to create an EDL firmware if you don't ready have one. If your on MTK then there is Sugar MTK or SP flash tool that can work. If your an another one you may be out of luck as it seems nobody has been able to restore those chipsets
EDIT: I do have a whole zip file of programmers and one that I use for my LG Zone 2 (msm8x10.mbn)
Click to expand...
Click to collapse
Thank you for your help, unfortunately it's a mediatek

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

Question Unable to mount storage when trying to ADB sideload

I can't install any rom, ADB sideload fails with this error:
Unable to mount storage.
Devices on super may not mount until rebooting recovery.
To flash additional zips, please reboot recovery to switch to the updated slot.
I already tried to switch the slots many times.
I also tried to format data, but it tells me:
E: unable to check merge status
Updating partition details...
...done
Unable to mount storage
I can access the recovery and the factory-reset android, but i can't do anything more.
I think the problem is relative to encryption but I can't even format data, so I don't know how to escape this...
Now I can't even access the rom, I can only access TWRP and fastboot. The problem is that format data does not work, with the same error:
E: unable to check merge status
I tried repairing and changing filesystem, now I don't really know what to do...
just install rom using fast boot tool and
format data after that
muneeb rizwan said:
just install rom using fast boot tool and
format data after that
Click to expand...
Click to collapse
I have never used fastboot tool. I'm on linux. Is this the program i must install?
And also, do I need a fastboot rom?
[Tool] Flash Custom ROMs through Fastboot [mojito / sunny]
Are you struggling to install custom roms on this device? Lots of recovery errors? Can't boot to any rom? Don't worry. Fastboot is a good way to avoid such nonsense... Install any custom rom & miui recovery rom through fastboot Steps: 1...
forum.xda-developers.com
USE THIS TOOL AND YOU DONT NEED FASTBOOT ROM
Ok, i installed CrDroid with fastboot tool, then format data and then re-flashed the rom with adb, but the phone starts just on the CrDroid recovery (slot b) or on fastboot (slot a)...
What is the correct process to install a ROM? This A/B thing gets me mad
Now I managed to install an old MIUI fastboot rom from this link with XiaomiADBFastbootTools (a kind of mi flash tool for linux) and this rom now it is working, so I think I had some problems with the fastboot tool you suggested. But I don't really know what was the problem, the installation process seemed to work, It restarted to recovery, I rebooted to system but then it kept returning to recovery or to fastboot without entering in the system...
Switching slots directly in recovery is not functional. Just look after switching what the active slot is and you will see that it has not changed. Do the slot switching with the fastboot command from the PC.
fastboot --set-active=a
fastboot --set-active=b
StaryMuz said:
Switching slots directly in recovery is not functional. Just look after switching what the active slot is and you will see that it has not changed. Do the slot switching with the fastboot command from the PC.
fastboot --set-active=a
fastboot --set-active=b
Click to expand...
Click to collapse
yes, I was using these commands to switch slots. but when it is necessary to switch slots in the flashing process? I mean, what is the correct order? format - flash rom with adb - reboot to fastboot - switch slot - reboot to system...is this correct?
Slot swapping may not be required. Do it only when it is requested or when the boot crashes into recovery.
StaryMuz said:
Slot swapping may not be required. Do it only when it is requested or when the boot crashes into recovery.
Click to expand...
Click to collapse
OK, so is this the correct order?
Format - flash rom with adb - reboot to system
Now I have a problem with fastboot...I don't know why but it can't boot any recovery...
"fastboot boot recovery.img" remains stuck at:
Sending 'boot.img' (131072 KB)
Click to expand...
Click to collapse
and nothing happens! I tried with TWRP and OrangeFox.
I also tried to change slot but it fails:
fastboot --set-active=a
Setting current slot to 'a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Click to expand...
Click to collapse
The command 'Fastboot reboot' gives me a black screen with a white message: 'any key to shutdown', then the phone reboots to system...
What is the full designation of your phone?
StaryMuz said:
What is the full designation of your phone?
Click to expand...
Click to collapse
what is the designation?
Xiaomi Redmi Note .....
All of it, exactly.
StaryMuz said:
Xiaomi Redmi Note .....
All of it, exactly.
Click to expand...
Click to collapse
Redmi Note 10 64GB/4GB, I think the codename is sunny because I have the global/european version. Do you need more?
I think the best step is to upload the original Miui using MiFlash with the "clear all" setting.
Use this version of MiFlash.
You can get the right Miui here.
Before using MiFlash, I recommend loading the boot.img included in the downloaded Miui into your phone in fastboot mode.
Use the command:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Then use MiFlash and don't play Miui. Wait until the phone starts itself, then you can disconnect it.
If anything is not clear, ask questions.
StaryMuz said:
I think the best step is to upload the original Miui using MiFlash with the "clear all" setting.
Use this version of MiFlash.
You can get the right Miui here.
Before using MiFlash, I recommend loading the boot.img included in the downloaded Miui into your phone in fastboot mode.
Use the command:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Then use MiFlash and don't play Miui. Wait until the phone starts itself, then you can disconnect it.
If anything is not clear, ask questions.
Click to expand...
Click to collapse
Actually I'm already in a original MIUI and it is working. My pc is on linux so I can't use MiFlash but I used XiaomiADBFastbootTools (a kind of MiFlash tool for linux). Can I start from here or I have to install the MIUI version you linked?
The only thing is that I didn't specifically load the boot.img
Unfortunately I don't know the Linux version of MiFlash. They may not work equivalently. It needs to properly clean all the partitions of the phone and load all the files supplied in the ROM.
I recommend to use the Miui listed by me.

[SOLVED] Realme 5i stuck on fastboot after flashing custom ROM no recovery or OS

Yes, Im stuck. Im on realme 5i and I flashed PixelExperience+ with TWRP, clean flash, made sure to wipe data and clear cache before and after flashing. I rebooted and boom, stuck on fastboot/bootloader. I can't go back to recovery mode or to system, it just takes me back to fastboot/bootloader. I backed up my files btw.
Supposed fixes that did not work:
1: Fastboot erase boot && fastboot erase dtbo && fastboot erase recovery && fastboot erase vbmeta && fastboot erase system && fastboot erase userdata and fastboot flash recovery TWRP.img && fastboot flash dtbo dtbo.img && fastboot flash vbmeta vbmeta.img && fastboot reboot-bootloader.
- it brings me back to fastboot when I try to go to recovery mode.
2: Push volume down/up and power button.
- it brings me back to fastboot when I try to go to recovery mode. (2)
3: flash stock recovery (I can't go to recovery so I cant flash stock ROM too)
- it brings me back to fastboot when I try to go to recovery mode. (3)
What else do I do? Am I missing something from the fixes I've tried above?? I am in need of urgent help.
Update: I've tried realme flash tool, for stock ROM and it says cannot find central directory.
I've tried putting the ofp to AppData/Roaming/flashtool/temp as said from another thread. I've also tried running in administrator but none work. I've ran out of luck today, please help.
Phone: Realme 5i
Story: I had my phone get a custom recovery, TWRP. Got it rooted. Before I rooted it I rolledback to android 9, ColorOS, bw. Then decided why not use a custom ROM? So I did. PixelExperiencePlusEdition ANDROID 12. I flashed it with TWRP, factory reset and cleared cache, in other words, clean flash. I'm hopeless cause once I rebooted, I got sent to fastboot then when I tried to go to recovery mode, it sends me back to fastboot! What do I do? I need help. please.
Update: So maybe I am doing the 1st method wrong. I got all the img files wrong, cause I need them from my stock firmware right? So I tried programs to extract those img from their new.dat.br files right? I did and the extractors keep giving me something is missing, line this and that is incorrect or something like that. I'm really hopeless. Can someone give me the img files of RMX2030EX_11_OTA_0210_all_1hZhuZlgVC1t? system.img, boot.img, vendor.img, vbmeta.img, dtbo.img? What else am I missing to manually flash it?
I am facing the same issue as well, I had downloaded the RMX2030EX_11_C.75_210917_1b9832bb file and extracted using https://github.com/bkerler/oppo_decrypt but the first method still didn't work. was is the wrong file? or did the decryptor didn't work properly idk.
koarc lkas said:
Update: So maybe I am doing the 1st method wrong. I got all the img files wrong, cause I need them from my stock firmware right? So I tried programs to extract those img from their new.dat.br files right? I did and the extractors keep giving me something is missing, line this and that is incorrect or something like that. I'm really hopeless. Can someone give me the img files of RMX2030EX_11_OTA_0210_all_1hZhuZlgVC1t? system.img, boot.img, vendor.img, vbmeta.img, dtbo.img? What else am I missing to manually flash it?
Click to expand...
Click to collapse
I can't find a file on realme software page with this name where did you get the file? plus does your variant has Qualcomm or Mediatek CPU? I saw a video where it stated that this phone has two variants one with Qualcomm and other with Mediatek(Helio) CPU.
Edit: Do an MD5 check maybe your file got corrupt..
I managed to fix, you will need download these files from telegram. one of them should work for me the ColorOS file worked. Follow the instruction given in the readme file and that should do. I am installing DotOS now it showing the splash animation from last 5 minutes, if it works i'll update the comment or will provide further instructions to fix.
FastbootFix-Realme-5-5i-5s~RUI.zip
FastbootFix-Realme-5i~Color OS.zip
Edit: the reason it was taking so long to bootup and was stuck on splash animation is that I forgot to format (type yes).
yasir.r said:
I can't find a file on realme software page with this name where did you get the file? plus does your variant has Qualcomm or Mediatek CPU? I saw a video where it stated that this phone has two variants one with Qualcomm and other with Mediatek(Helio) CPU.
Edit: Do an MD5 check maybe your file got corrupt..
Click to expand...
Click to collapse
I got it from this:
This is what I used to rollback to android 9 cause another video said I had to do this first before rooting. It worked though then custom ROM happened and now phone's bricked. Hasn't been used ever since.
I'll do MD5 if your fix didn't work.
Hey um, Im a turtle and Im reading the .txt from the link you gave the color os one specifically. So Im at the step where I have to Double Click "Open This to Proceed" file to start the process. What is this "Open This to Proceed" exactly?
Edit: Never mind. I should've looked more before asking..
IT WORKED!!!!!!! THANK YOU SO MUCH! YOU'RE A LIFESAVER!
koarc lkas said:
IT WORKED!!!!!!! THANK YOU SO MUCH! YOU'RE A LIFESAVER!
Click to expand...
Click to collapse
Now if you want to flash the stock rom you will have to flash firmware first.
flash fw c.xx
wipe 5
flash rom
flash vbmeta disabler
format (type yes)
reboot
You can download the firmware file form here. https://github.com/realme-trinket-organization/firmware_files_RMX1911/releases and the vbmeta disabler from here. https://t.me/r5notes/52
yasir.r said:
Now if you want to flash the stock rom you will have to flash firmware first.
flash fw c.xx
wipe 5
flash rom
flash vbmeta disabler
format (type yes)
reboot
You can download the firmware file form here. https://github.com/realme-trinket-organization/firmware_files_RMX1911/releases and the vbmeta disabler from here. https://t.me/r5notes/52
Click to expand...
Click to collapse
!!! Im having a problem with flashing my stock rom cause it keeps getting bricked. Thank you so much for giving me this!
yasir.r said:
Now if you want to flash the stock rom you will have to flash firmware first.
flash fw c.xx
wipe 5
flash rom
flash vbmeta disabler
format (type yes)
reboot
You can download the firmware file form here. https://github.com/realme-trinket-organization/firmware_files_RMX1911/releases and the vbmeta disabler from here. https://t.me/r5notes/52
Click to expand...
Click to collapse
How do I know my exact build number? I just know that it's realme 5i and it is RMX2030, not those C69 thingies.
koarc lkas said:
How do I know my exact build number? I just know that it's realme 5i and it is RMX2030, not those C69 thingies.
Click to expand...
Click to collapse
I just used the latest version c.73 it worked. I do have to same phone. R5i, RMX2030 with SD665 CPU.
How do I flash the firmware I downloaded from your link? and the vbmeta disabler img is in the firmware-update file, correct?
koarc lkas said:
How do I flash the firmware I downloaded from your link? and the vbmeta disabler img is in the firmware-update file, correct?
Click to expand...
Click to collapse
no no not the image, vbmeta-disabler.zip from here https://t.me/r5notes/52 and flash them in pbrp like you flash the rom.
ohh both zip files, okay
yasir.r said:
no no not the image, vbmeta-disabler.zip from here https://t.me/r5notes/52 and flash them in pbrp like you flash the rom.
Click to expand...
Click to collapse
Upon flashing the firmware zip, my phone keeps getting stuck on bootloop, it doesnt even let me go to recovery mode. It keeps restarting too?
Edit: is this normal??
The tool you gave me to fix fastboot doesnt work anymore :<
koarc lkas said:
Upon flashing the firmware zip, my phone keeps getting stuck on bootloop, it doesnt even let me go to recovery mode. It keeps restarting too?
Edit: is this normal??
Click to expand...
Click to collapse
did you follow the process, properly?? don't tell you flashed just the firmware and nothing else..
yasir.r said:
did you follow the process, properly?? don't tell you flashed just the firmware and nothing else..
Click to expand...
Click to collapse
I only got to step one which you said to get firmware and flash it. I flashed it and my phone rebooted but it keeps restarting. I can still flash images but I cant seem to fix this "reboot loop" and the tool you gave doesnt fix it either. What Im guessing is C73 isnt my firmware version since this phone is years old? Do you know how to delete the firmware so maybe the tool you gave me would work again and I can start over once more?
Edit: Im once again stuck in fastboot btw.
Edit: I fixed the rebooting loop with the stock recovery.bat from the file you gave me but when I do the "open this to proceed" it goes back to rebooting automatically. I still want to remove the C73 firmware though.

Categories

Resources