Related
Situation:
yota3 in bootloop caused by fastboot command "fastboot flashing lock" with installed TWRP recovery and rooted. (don't ask me why)
Now i have only access to fastboot.
No recovery access
Bootloader locked
I tried flashing stock recovery (+ttp://www.mediafire.com/file/6hvldb...806223.7z/file) with MIFLASH, QFIL and TOOL STUDIO in EDL mode 9008 (fastbood oem edl) but without success.
Qualcomm com 9008 drivers ok
Have you any other idea?
Thank you.:good:
(SOLVED)
Re-flash following exactly the instructions.
Pay attention that during the first flash you have to select the 2 xml files and the second
time flash only one xml indicated.
https://forum.xda-developers.com/yot...-news-t3862999
Does anyone have a different recovery rom to try?
You have tried to unlock another time?
fastboot flashing unlock ?
skirep said:
You have tried to unlock another time?
fastboot flashing unlock ?
Click to expand...
Click to collapse
Thanks for the reply. I was starting to feel lonely and lost.:laugh:
Yes, I think I tried every fastboot command but no boot, no erase, no flash .. is allowed.
QFIL errors logs
Programmer Path:C:\Users\paolo\Downloads\YOTA3\qfil\Qualcomm_Flash_Image_Loader_v1.0.0.3\images\prog_emmc_firehose_8953_ddr.mbn
Image Search Path: C:\Users\paolo\Downloads\YOTA3\qfil\Qualcomm_Flash_Image_Loader_v1.0.0.3\images
PATCH file path ignored: C:\Users\paolo\Downloads\YOTA3\qfil\Qualcomm_Flash_Image_Loader_v1.0.0.3\images\patch0.xml
PATCH file path:C:\Users\paolo\Downloads\YOTA3\qfil\Qualcomm_Flash_Image_Loader_v1.0.0.3\images\patch0.xml
Image Search Path: C:\Users\paolo\Downloads\YOTA3\qfil\Qualcomm_Flash_Image_Loader_v1.0.0.3\images
Invalid RAWPROGRAM file path ignored: C:\Users\paolo\Downloads\YOTA3\qfil\Qualcomm_Flash_Image_Loader_v1.0.0.3\images\rawprogram_unsparse_without_QCN.xml Ignored
Invalid RAWPROGRAM file path ignored: C:\Users\paolo\Downloads\YOTA3\qfil\Qualcomm_Flash_Image_Loader_v1.0.0.3\images\rawprogram2.xml Ignored
Invalid PATCH file path ignored:C:\Users\paolo\Downloads\YOTA3\qfil\Qualcomm_Flash_Image_Loader_v1.0.0.3\images\patch2.xml
PATCH file path ignored: C:\Users\paolo\Downloads\YOTA3\qfil\Qualcomm_Flash_Image_Loader_v1.0.0.3\images\patch0.xml
PATCH file path:C:\Users\paolo\Downloads\YOTA3\qfil\Qualcomm_Flash_Image_Loader_v1.0.0.3\images\patch0.xml
Start Download
Program Path:C:\Users\paolo\Downloads\YOTA3\qfil\Qualcomm_Flash_Image_Loader_v1.0.0.3\images\prog_emmc_firehose_8953_ddr.mbn
Binary build date: May 13 2015 @ 14:41:37
QSAHARASERVER CALLED LIKE THIS: 'C:\Users\paolo\Downloads\YOTA3\qfil\Qualcomm_Flash_Image_Loader_v1.0.0.3\QSaharaServer.exe -p \\.\COM10 -s 13:C:\Users\paolo\Downloads\YOTA3\qfil\Qualcomm_Flash_Image_Loader_v1.0.0.3\images\prog_emmc_firehose_8953_ddr.mbn 'Current working dir: C:\Users\paolo\AppData\Roaming\Qualcomm\QFIL
Sahara mappings:
2: amss.mbn
6: apps.mbn
8: dsp1.mbn
10: dbl.mbn
11: osbl.mbn
12: dsp2.mbn
16: efs1.mbn
17: efs2.mbn
20: efs3.mbn
21: sbl1.mbn
22: sbl2.mbn
23: rpm.mbn
25: tz.mbn
28: dsp3.mbn
29: acdb.mbn
30: wdt.mbn
31: mba.mbn
13: C:\Users\paolo\Downloads\YOTA3\qfil\Qualcomm_Flash_Image_Loader_v1.0.0.3\images\prog_emmc_firehose_8953_ddr.mbn
18:30:22: ERROR: function: sahara_rx_data:194 Unable to read packet header. Only read 0 bytes.
18:30:22: ERROR: function: sahara_main:854 Sahara protocol error
18:30:22: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
Click to expand...
Click to collapse
This is the FILES LIST of the "RECOVERY ROM" i have.
adspso.bin
boot.img
cdt.img
cmnlib.bin
cmnlib64.mbn
custom.img
ddr.img
devcfg.mbn
dummy.img
emmc_appsboot.mbn
filelist.txt
gpt_backup0.bin
gpt_both0.bin
gpt_main0.bin
junklog.img
keymaster.mbn
letvconfig.img
lksecapp.img
lksecappbak.img
logdump.img
mcfg.img
mota.img
NON-HLOS.bin
oem.img
params.img
partition.xml
patch0.xml
persist.img
prog_emmc_firehose_8953_ddr.mbn
rawprogram0.xml
rawprogram0_BLANK.xml
recovery.img
recoverybp.img
rpm.mbn
sbl1.mbn
splash.img
syscfg.img
system.img
tz.mbn
wipe_rawprogram_PHY0.xml
wipe_rawprogram_PHY1.xml
wipe_rawprogram_PHY2.xml
wipe_rawprogram_PHY4.xml
wipe_rawprogram_PHY5.xml
wipe_rawprogram_PHY6.xml
wipe_rawprogram_PHY7.xml
Click to expand...
Click to collapse
jelixsu
Today, 02:59 AM |#78
Junior Member24 posts Thanks: 2
first write firmware, this step can save your phone in most brick situation.
*ttp://download1518.mediafire.com/rvo7la5b5ohg/6hvldbq5lojxlgn/yota3_images_Y3XSCN06A1000MPX1806223.7z
then extricating the file
fastboot
*ttps://forum.xda-developers.com/attachment.php?attachmentid=4651886
driver Qualcomm_USB_Driver_V1.0.zip
*ttps://forum.xda-developers.com/attachment.php?attachmentid=4651890&d=1543200054
twrp rec.img
*ttps://drive.google.com/drive/folders/14MO7_WUwOkVl94apC29YMzbuWKePjjTV
fastboot flashing unlock
fastboot flash recovery RECOVERY.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flashing lock
-------------------------------------------
into original recovery
press up+POWER then start ,still press up
double clean the date and devil-cache
-------------------------------------------
<only want root>will get twrp and magisk
fastboot flashing unlock
fastboot flash recovery rec.img
fastboot flash recoverybp rec.img
-------------------------------------------
flash new rom(R05 link)
*ttps://1drv.ms/u/s!Ak8Mx9Xz2kf8b0M0UXQ6zMkLPSU
press up+POWER into twrp
then triple clean
install R05
-------------------------------------------
in the middle of time
PIN LOCK,I have the same problem, try many way the solve it but.........
after unlock even brick the cell phone
follow those step by step can save brick phone again!!
Click to expand...
Click to collapse
If this replay in one other tread is for me i tell you that i cannot "fastboot flash, unlock, boot... anything" because i have bootloader locked.
Anybody has the original -prog_emmc_firehose_8953_ddr.mbn- for our YOTA3 ?
Thanks
paolinger said:
If this replay in one other tread is for me i tell you that i cannot "fastboot flash, unlock, boot... anything" because i have bootloader locked.
Click to expand...
Click to collapse
i have the same question with you.
yesterday i try to restore system, but forget press 7 times develop option then open oem unlock.
last time i remember after reset don`t open oem unlock .........it's ok. this time brick......
https://item.taobao.com/item.htm?id=562597407389
i will try to connecet the seller to solve the problem. have any news will tell you
jelixsu said:
i will try to connect the seller to solve the problem. have any news will tell you
Click to expand...
Click to collapse
I am not so experienced but i think we need the ORIGINAL STOCK ROM with SIGNED PROGRAMMER to flash with QFIL.
paolinger said:
I am not so experienced but i think we need the ORIGINAL STOCK ROM with SIGNED PROGRAMMER to flash with QFIL.
Click to expand...
Click to collapse
the seller try one day fail....he say need takethe emmc chip away then direct write something.
---------- Post added at 11:04 AM ---------- Previous post was at 11:04 AM ----------
paolinger said:
I am not so experienced but i think we need the ORIGINAL STOCK ROM with SIGNED PROGRAMMER to flash with QFIL.
Click to expand...
Click to collapse
the seller try one day fail....he say need take the emmc chip away then direct write something.
jelixsu said:
the seller try one day fail....he say need takethe emmc chip away then direct write something.
---------- Post added at 11:04 AM ---------- Previous post was at 11:04 AM ----------
the seller try one day fail....he say need take the emmc chip away then direct write something.
Click to expand...
Click to collapse
Wow! A radical intervention!?
Do you think that exists a FACTORY CODE to unlock the bootloader of our yota3? Like "FASTBOOT OEM UNLOCK 123456ABCD"?
jelixsu said:
the seller try one day fail....he say need takethe emmc chip away then direct write something.
---------- Post added at 11:04 AM ---------- Previous post was at 11:04 AM ----------
the seller try one day fail....he say need take the emmc chip away then direct write something.
Click to expand...
Click to collapse
Did the seller solved your problem?
Finally recovered the device and succesfully ugraded to yota 3+
Great work of China team
paolinger said:
Finally recovered the device and succesfully ugraded to yota 3+
Great work of China team
Click to expand...
Click to collapse
Could you please provide instructions how to achieve this? HexaDog deleted his post, regarding the upgrade of the y3 to y3+...
leser12 said:
Could you please provide instructions how to achieve this? HexaDog deleted his post, regarding the upgrade of the y3 to y3+...
Click to expand...
Click to collapse
Yes i will upload the files at:
https://forum.xda-developers.com/yotaphone-3/development/yota-3-firmware-news-t3862999
For the moment you can read the tutorial by Yunyao shopkeeper
and team.
paolinger said:
Finally recovered the device and succesfully ugraded to yota 3+
Great work of China team
Click to expand...
Click to collapse
How did you manage to unbrick your phone? I can only boot in qfil and don't know if bootloader is unlocked things got messy during the upgrade.
Woud be great if ou could help or at least tell what you did.
killsers said:
How did you manage to unbrick your phone? I can only boot in qfil and don't know if bootloader is unlocked things got messy during the upgrade.
Woud be great if ou could help or at least tell what you did.
Click to expand...
Click to collapse
Re-flash following exactly the instructions.
Pay attention that during the first flash you have to select the 2 xml files and the second
time flash only one xml indicated.
https://forum.xda-developers.com/yotaphone-3/development/yota-3-firmware-news-t3862999
paolinger said:
Re-flash following exactly the instructions.
Pay attention that during the first flash you have to select the 2 xml files and the second
time flash only one xml indicated.
https://forum.xda-developers.com/yotaphone-3/development/yota-3-firmware-news-t3862999
Click to expand...
Click to collapse
Thanks for the reply. I did that i forgot to check reset after download in the first time and the installation failed. now i get the following error message every time.
Edit: HvMES from the other thread had the solution just try it if you are stuck like me. Love you all guys really great community!
Hello!
Posting here because the model doesn't have its forum.
My phone is currently unlocked with phh-trebmble android 9 and the rom has rather crucial problems - apps crashing, no auto brightness, unable to connect to networks with hidden SSID and some more.
Unfortunately I cannot find a guide showing a working method [atleast for my case] to flash the stock rom.
I got the stock rom from firmwarex .net and tried flashing it with QFIL. At first the program couldn't locate a usable file for the "programmer path". After seeing multiple guides for the program I saw that everyone is using the same file "prog_emmc_firehose_8936.mbn" so I got the file, placed it in the rom folder and selected it from the QFIL. When i start the download proccess it returns Sahara error so I am unable to complite the recovery.
As it is somewhat scuffed method with spare parts from here and there could anyone point me to somthing that I am missing or doing wrong.
P.S. Phone is in download mode when I'm trying to flash trough QFIL, QFIL is seeng the phone on the port.
Flash stock rom lenovo k5
try turning off your internet connection and flash sorry for my inglis I'm using google translate
Nox.BG said:
Hello!
Posting here because the model doesn't have its forum.
My phone is currently unlocked with phh-trebmble android 9 and the rom has rather crucial problems - apps crashing, no auto brightness, unable to connect to networks with hidden SSID and some more.
Unfortunately I cannot find a guide showing a working method [atleast for my case] to flash the stock rom.
I got the stock rom from firmwarex .net and tried flashing it with QFIL. At first the program couldn't locate a usable file for the "programmer path". After seeing multiple guides for the program I saw that everyone is using the same file "prog_emmc_firehose_8936.mbn" so I got the file, placed it in the rom folder and selected it from the QFIL. When i start the download proccess it returns Sahara error so I am unable to complite the recovery.
As it is somewhat scuffed method with spare parts from here and there could anyone point me to somthing that I am missing or doing wrong.
P.S. Phone is in download mode when I'm trying to flash trough QFIL, QFIL is seeng the phone on the port.
Click to expand...
Click to collapse
I'm stuck on the "fire hose" file. QFIL seems to not detected the phone.
Did you managed to solve the problem?
Lenovo K5 Pro ROM
After flashing IMG file (using TWRP 3.3.1) the phone (Lenovo k5 pro) always starts in bootloader mode. Everyone can help?
ShmuelCohen said:
After flashing IMG file (using TWRP 3.3.1) the phone (Lenovo k5 pro) always starts in bootloader mode. Everyone can help?
Click to expand...
Click to collapse
Did you get any solution, I have the same problem.
Instead of using qpst I solved this by using a qfil unsparse tool which made a single raw image file of system.img, vendor.img and userdata.img and I then used img2simg to make sparse images of the newly created files that I flashed using the command:
fastboot flash system system.img
and so on with vendor.img, boot.img, cache.img and userdata.img (in my case i had overwritten vendor files) from platform-tools.
anonym34 said:
Instead of using qpst I solved this by using a qfil unsparse tool which made a single raw image file of system.img, vendor.img and userdata.img and I then used img2simg to make sparse images of the newly created files that I flashed using the command:
fastboot flash system system.img
and so on with vendor.img, boot.img, cache.img and userdata.img (in my case i had overwritten vendor files) from platform-tools.
Click to expand...
Click to collapse
Thank you so much for this post.
After many many many attempts to repair my device through qfil without success, I tried what you wrote in the post and thank God I finally succeeded so thank you very much.
However for some reason I can not update the system version because he thinks I have root, no matter what I did I could not fix it.
Any ideas?
I also wanted to ask, for what should a userdata partition be flashed? It is always built on its own. I'm wrong?
anonym34 said:
Instead of using qpst I solved this by using a qfil unsparse tool which made a single raw image file of system.img, vendor.img and userdata.img and I then used img2simg to make sparse images of the newly created files that I flashed using the command:
fastboot flash system system.img
and so on with vendor.img, boot.img, cache.img and userdata.img (in my case i had overwritten vendor files) from platform-tools.
Click to expand...
Click to collapse
Resuscitated my K5 Pro, thank you very much your comment saved me!:victory::victory:
help me what is the correct file to download to flash android 10 on lenovo k5 pro. Gapps and custom rom please help. Im stock the google pixel logo boot screen for almost an hour.
anonym34 said:
Instead of using qpst I solved this by using a qfil unsparse tool which made a single raw image file of system.img, vendor.img and userdata.img and I then used img2simg to make sparse images of the newly created files that I flashed using the command:
fastboot flash system system.img
and so on with vendor.img, boot.img, cache.img and userdata.img (in my case i had overwritten vendor files) from platform-tools.
Click to expand...
Click to collapse
.
shisho585 said:
Thank you so much for this post.
After many many many attempts to repair my device through qfil without success, I tried what you wrote in the post and thank God I finally succeeded so thank you very much.
However for some reason I can not update the system version because he thinks I have root, no matter what I did I could not fix it.
Any ideas?
I also wanted to ask, for what should a userdata partition be flashed? It is always built on its own. I'm wrong?
Click to expand...
Click to collapse
.
iugleafar said:
Resuscitated my K5 Pro, thank you very much your comment saved me!:victory::victory:
Click to expand...
Click to collapse
anonym34 said:
Instead of using qpst I solved this by using a qfil unsparse tool which made a single raw image file of system.img, vendor.img and userdata.img and I then used img2simg to make sparse images of the newly created files that I flashed using the command:
fastboot flash system system.img
and so on with vendor.img, boot.img, cache.img and userdata.img (in my case i had overwritten vendor files) from platform-tools.
Click to expand...
Click to collapse
.
I installed EMUI 9 on my p20 lite and didn't like it, so I tried one of the openkirin 9.0 beta roms. There was some features that didn't work so I decided I wanted to go back. I followed the guide on openkirin's website about going back to stock by flashing system.img, ramdisk.img, kernel.img and recovery_ramdisk.img however trying to flash ramdisk.img gives "partition length get error". Now, the phone only is able to boot into fastboot and eRecovery mode. In eRecovery the options to backup and to factory reset are grayed out however, and the "update to latest version" doesn't work. When I plug the charger in from being turned off it shows the white error screen with error 10 (boot image) and error 2 (load failed). I have a suspicion that flashing kernel.img is what causing the problem, but I don't really know enough to be sure and I don't want to do anything to make it worse since it seems like this should be fixable.
This is the only phone I have which properly worked so any help is greatly appreciated.
Hi there
Don't worry, it's fixable
There's way bigger mess than that, so the best solution for you and the easiest one is to flash a signed dload package, which you can find for your model and build number in this website:
https://androidhost.ru/search.html
Search in this format "ANE-LX1C66".
Then extract it and copy the "dload" folder to the root of your sd card.
Then power off your device if it isn't and then press POWER + Volume Plus + Volume Minus at the same time until a circle with EMUI appears.
That will erase all data and lock your bootloader.
Cheers!
AS
ars_chelsea said:
Hi there
Don't worry, it's fixable
There's way bigger mess than that, so the best solution for you and the easiest one is to flash a signed dload package, which you can find for your model and build number in this website:
https://androidhost.ru/search.html
Search in this format "ANE-LX1C66".
Then extract it and copy the "dload" folder to the root of your sd card.
Then power off your device if it isn't and then press POWER + Volume Plus + Volume Minus at the same time until a circle with EMUI appears.
That will erase all data and lock your bootloader.
Cheers!
AS
Click to expand...
Click to collapse
Ah, yeah, forgot to mention I already tried that. Unfortunately it doesn't work. It just says "software install failed". I'm genuinely about to throw this f***ing thing into orbit
Thanks for your help though.
Afifus said:
Ah, yeah, forgot to mention I already tried that. Unfortunately it doesn't work. It just says "software install failed". I'm genuinely about to throw this f***ing thing into orbit
Thanks for your help though.
Click to expand...
Click to collapse
That's weird, are you sure you are installing the right package for your device? It's rare to fail with a correct package.
What's your build number and model ?
ars_chelsea said:
That's weird, are you sure you are installing the right package for your device? It's rare to fail with a correct package.
What's your build number and model ?
Click to expand...
Click to collapse
Tried Oreo build 150 for ane-lx1c432 and ane-lx1c782 since those are the only models my phone could be.
Although, when I do the get-build-number command in fastboot it still says I'm on a Pie build. I'm gonna try doing a Pie build and I'll get back to you.
ars_chelsea said:
That's weird, are you sure you are installing the right package for your device? It's rare to fail with a correct package.
What's your build number and model ?
Click to expand...
Click to collapse
Yeah, pie didn't work either.
Afifus said:
Yeah, pie didn't work either.
Click to expand...
Click to collapse
But there is no signed package for those models yet, what dload files did you use?
Cheers,
AS
ars_chelsea said:
But there is no signed package for those models yet, what dload files did you use?
Cheers,
AS
Click to expand...
Click to collapse
I got it off of firmware finder. Are those not signed?
Afifus said:
I got it off of firmware finder. Are those not signed?
Click to expand...
Click to collapse
No, those are not signed, you need the dload files from Androidhost.ru since it's the only place you can get them for free, here's a link for both the versions you showed:
Single SIM ANE-LX1C432: https://androidhost.ru/Utm
Dual SIM ANE-LX1C432: https://androidhost.ru/Utn
Single SIM ANE-LX1C782: https://androidhost.ru/29Zn
Dual SIM ANE-LX1C782: https://androidhost.ru/1jzD
Choose the right one, and follow the procedure I sent you in a reply above.
ars_chelsea said:
No, those are not signed, you need the dload files from Androidhost.ru since it's the only place you can get them for free, here's a link for both the versions you showed:
Single SIM ANE-LX1C432: https://androidhost.ru/Utm
Dual SIM ANE-LX1C432: https://androidhost.ru/Utn
Single SIM ANE-LX1C782: https://androidhost.ru/29Zn
Dual SIM ANE-LX1C782: https://androidhost.ru/1jzD
Choose the right one, and follow the procedure I sent you in a reply above.
Click to expand...
Click to collapse
Cheers, but unfortunately neither of those worked. I'm at a loss on what else I could try.
Afifus said:
Cheers, but unfortunately neither of those worked. I'm at a loss on what else I could try.
Click to expand...
Click to collapse
at less you back to emui 9.1 only to save your phone
first download the firmware from tm team database search the right firmware for your phone
after that unzip the two files then use huawei extractor to extract files from update.app
and follow this instructions
Copy to the following partitions to the adb fastboot folder:
recovery_ramdisk
recovery_vbmeta
recovery_vendor
cust
kernel
system
userdata
product
vendor
Then boot your device in fastboot mode.
note if you dont found recovery ramdisk then rename recovery ramdis to previous name
The commands for fastboot:
fastboot flash recovery_ramdisk recovery_ramdisk.img
fastboot flash recovery_vbmeta recovery_vbmeta.img
fastboot flash recovery_vendor recovery_vendor.img
fastboot flash cust cust.img
fastboot flash kernel kernel.img
fastboot flash system system.img
aftet that make a wipe / factory reset
what happen to you happen to me the same thing if this work after that then be patience until we get official emui, the last news that i read that huawei postpone release until july
Thanks to kilroystyx
Try this and tell me
yassine2217 said:
at less you back to emui 9.1 only to save your phone
first download the firmware from tm team database search the right firmware for your phone
after that unzip the two files then use huawei extractor to extract files from update.app
and follow this instructions
Copy to the following partitions to the adb fastboot folder:
recovery_ramdisk
recovery_vbmeta
recovery_vendor
cust
kernel
system
userdata
product
vendor
Then boot your device in fastboot mode.
note if you dont found recovery ramdisk then rename recovery ramdis to previous name
The commands for fastboot:
fastboot flash recovery_ramdisk recovery_ramdisk.img
fastboot flash recovery_vbmeta recovery_vbmeta.img
fastboot flash recovery_vendor recovery_vendor.img
fastboot flash cust cust.img
fastboot flash kernel kernel.img
fastboot flash system system.img
aftet that make a wipe / factory reset
what happen to you happen to me the same thing if this work after that then be patience until we get official emui, the last news that i read that huawei postpone release until july
Thanks to kilroystyx
Try this and tell me
Click to expand...
Click to collapse
Holy f*** thank you. That seems to have worked. It also seems to have fixed the sms problem I had with 9.1.
Afifus said:
Holy f*** thank you. That seems to have worked. It also seems to have fixed the sms problem I had with 9.1.
Click to expand...
Click to collapse
great happy for you
Hi! can someone help me, My moto e5 play does not turn on properly. It only goes into Ap fastboot flash mode. So i am trying to flash my firmware on it with rsd lite but i get an error saying system img sparsechunk 0 failed. and the boot loader says invalid piv signed image
greggie134 said:
Hi! can someone help me, My moto e5 play does not turn on properly. It only goes into Ap fastboot flash mode. So i am trying to flash my firmware on it with rsd lite but i get an error saying system img sparsechunk 0 failed. and the boot loader says invalid piv signed image
Click to expand...
Click to collapse
Are using the same commands as in the .xml ?
Open it with a text program like notepad+
Sent from my mata using XDA Labs
Yes I am. I actually had to remove some code from the flashfile.xml and delete some of the img files like the boot.img in order to get it to flash properly, but when I erase the "System.Img_sparsechunk.0" code Rsd lite gives me an error saying "Invalid xml file" I dont know what to do now. I dont know if I am flashing the proper firnware or maybe its because my phone is oem locked.
Also I am using wordpad to edit my xml file.
greggie134 said:
Also I am using wordpad to edit my xml file.
Click to expand...
Click to collapse
Wordpad likely isn't keeping the correct format, it works to see the text but not great for editing an .xml
I prefer notepad++
https://notepad-plus-plus.org/
Which firmware file are you using?
Sent from my mata using XDA Labs
the firmware file i am using is XT1921-3_JAMES_TMO_8.0.0_ I am going to re edit this xml file using notepad++ and see what happens.
greggie134 said:
the firmware file i am using is XT1921-3_JAMES_TMO_8.0.0_ I am going to re edit this xml file using notepad++ and see what happens.
Click to expand...
Click to collapse
This one?
https://mirrors.lolinet.com/firmwar...ubsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml.zip
Sent from my mata using XDA Labs
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).