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"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.
ใน Qfil การกำหนดค่า ให้ใน UFSDuel 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 ของฉันได้ ขอบคุณ
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 againtry 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
thanks a lot. i can try that. are you in the legion group on telegram? we could sure use your help lolcompletely 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
I would not recommend that step.try going into your firehose options and select erase all before flashing
how do you fast boot flash. mine not connecting to fast boottry flashing a meta build with the ddr firehose, then fastboot flash your persist image. its worked for me twice now
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.
i tried both qfil and fast boot same issueMake 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.
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).
okay i checked the imei its the pro 2Windows 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).
i checked the imei and it came up as the legion 2 pro. can you link the treads for that model and how to get it back up. IT will be greatly appreciatedWindows 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).
I've been helping try and diagnose the issue on another thread with him. It seems to be an issue with a partition that has been wiped or is missing. I directed him to the folder with the partitions that you provided and assume there might be something of use there for him. If you could provide a permission (ls -l) list of your partitions within /by-name/ for reference it should help for any of those with the same issue like he is facing. Once the partitions are dd' a little permission changing is pretty simple. Perhaps it will make a good tutorial so people can save their devices from becoming a paper weight or construction site material.The first time I bricked my phone it took a couple tries before it seemed to work
can you help me with this. i am new with this, my duel 2 was stuck at fastboot after RSA. tried QFIL and download worked but now my phone is going in qualcomm crash dump. how can i fix this?I've been helping try and diagnose the issue on another thread with him. It seems to be an issue with a partition that has been wiped or is missing. I directed him to the folder with the partitions that you provided and assume there might be something of use there for him. If you could provide a permission (ls -l) list of your partitions within /by-name/ for reference it should help for any of those with the same issue like he is facing. Once the partitions are dd' a little permission changing is pretty simple. Perhaps it will make a good tutorial so people can save their devices from becoming a paper weight or construction site material.
I've been helping try and diagnose the issue on another thread with him. It seems to be an issue with a partition that has been wiped or is missing. I directed him to the folder with the partitions that you provided and assume there might be something of use there for him. If you could provide a permission (ls -l) list of your partitions within /by-name/ for reference it should help for any of those with the same issue like he is facing. Once the partitions are dd' a little permission changing is pretty simple. Perhaps it will make a good tutorial so people can save their devices from becoming a paper weight or construction site material.The first time I bricked my phone it took a couple tries before it seemed to work