I downloaded a stock KDZ for my device and LGUP got stuck at 99% and eventually, it turned itself off but then nothing happened after that. Now it doesn't boot up at all and when I plug it in, it shows "unrecognized USB device" from windows. I tried to boot back into download mode but I can't do that and the screen is still black. Any help would be appreciated.
jimmysofat6864 said:
I downloaded a stock KDZ for my device and LGUP got stuck at 99% and eventually, it turned itself off but then nothing happened after that. Now it doesn't boot up at all and when I plug it in, it shows "unrecognized USB device" from windows. I tried to boot back into download mode but I can't do that and the screen is still black. Any help would be appreciated.
Click to expand...
Click to collapse
You need to download Qualcomm drivers for HS_qdloader9008 mode. Your phone is in emergency download mode. You'll also need a qfil style rom for the flash programer (emmc_firehose_MSM8909.mbn). Use emmcdl.exe to install rom.
lehmancurtis said:
You need to download Qualcomm drivers for HS_qdloader9008 mode. Your phone is in emergency download mode. You'll also need a qfil style rom for the flash programer (emmc_firehose_MSM8909.mbn). Use emmcdl.exe to install rom.
Click to expand...
Click to collapse
So I got the ROM and extracted it and made appropriate programmable files and proper patch0.xml files. Now where can I get the flash programmer file (emmc_firehose_MSM8909.mbn) (Firehose File/Programmer File)? Also where can I get a QFIL style ROM for my phone? with the flash programmer file and the other xml files? I tried a bunch of mbn files for MSM8909 that I found for the flash programmer and I'd end up with these errors.
2019-04-11 17:02:52.223 13: E:\LG K7\DZ Extractor With Combined System.bin\prog_emmc_firehose_8909_ddr.mbn
2019-04-11 17:02:52.227
2019-04-11 17:02:52.227 17:02:52: ERROR: function: rx_data:247 Error occurred while reading from COM port
2019-04-11 17:02:52.231
2019-04-11 17:02:52.231 17:02:52: ERROR: function: sahara_main:924 Sahara protocol error
2019-04-11 17:02:52.231
2019-04-11 17:02:52.231 17:02:52: ERROR: function: main:303 Uploading Image using Sahara protocol failed
2019-04-11 17:02:52.235
2019-04-11 17:02:52.235
2019-04-11 17:02:52.235 Download Fail:Sahara Fail:QSaharaServer Failrocess fail
2019-04-11 17:02:52.235 Finish Download
Most oem flashers have been leaked. You just have to keep looking. It'll be named prog_emmc_firehose_msm8909.mbn roughly. That with the patch xml and you'll need rawprogram0.xml.
lehmancurtis said:
Most oem flashers have been leaked. You just have to keep looking. It'll be named prog_emmc_firehose_msm8909.mbn roughly. That with the patch xml and you'll need rawprogram0.xml.
Click to expand...
Click to collapse
I've been looking around for quite a while and I haven't found it. Is there a way to make a firehose file from the kdz file? If not, then can you help me find it?
lehmancurtis said:
Most oem flashers have been leaked. You just have to keep looking. It'll be named prog_emmc_firehose_msm8909.mbn roughly. That with the patch xml and you'll need rawprogram0.xml.
Click to expand...
Click to collapse
I used a file that was similarly named to that or exactly named that and the flash still failed with the same error from before. Would you happen to have a functional firehose file?
I don't have it but I'm trying to find one also. Or another option
---------- Post added at 03:49 PM ---------- Previous post was at 03:47 PM ----------
Sometimes if you hold power and volume+ for over 30 seconds it triggers a reset from edl.
lehmancurtis said:
I don't have it but I'm trying to find one also. Or another option
---------- Post added at 03:49 PM ---------- Previous post was at 03:47 PM ----------
Sometimes if you hold power and volume+ for over 30 seconds it triggers a reset from edl.
Click to expand...
Click to collapse
Ok I tried using Tool Studio and inputed the files but there's a problem. There's no RAM or BOOT image for me to flash and the program wont continue without it. If possible, would you happen to have the RAM or BOOT image for the LGMS330? All the files are there except for those two files. It's that and if you know any other tools I can use to flash my phone besides qfil and tool studio.
I do have a boot image. I'll post it asap. When you get things working please post your findings.
#UPDATE
I am uploading a folder with the stock boot.img and the split image / ramdisk produced from using [email protected]
Heres the link. Best of luck to ya.
https://drive.google.com/folderview?id=1i7FTfCD04gvT_SGSBahrAIbwVhjZcvva
lehmancurtis said:
I do have a boot image. I'll post it asap. When you get things working please post your findings.
#UPDATE
I am uploading a folder with the stock boot.img and the split image / ramdisk produced from using [email protected]
Heres the link. Best of luck to ya.
https://drive.google.com/folderview?id=1i7FTfCD04gvT_SGSBahrAIbwVhjZcvva
Click to expand...
Click to collapse
Do you know how to put the ramdisk image into a mbn file? The tool I'm using seems to only accept those types of files for the ramdisk.
Edit: Also would you happen to know if you can also put the boot image into a mbn file as well?
If you have busybox or a linux machine run this on the boot.img
Code:
dd if=/path/to/boot.img of=/path/you/save/boot.mbn
Be sure to use ur paths.
lehmancurtis said:
If you have busybox or a linux machine run this on the boot.img
Code:
dd if=/path/to/boot.img of=/path/you/save/boot.mbn
Be sure to use ur paths.
Click to expand...
Click to collapse
Would you happen to know how to turn the ramdisk image into a mbn or img file?
It's Something But Back to Square One
I decided to use eMMC software download and flash the os to a micro sd card as I saw other people do it for other phones as I saw no other way out of qloader mode. After I did that, I put the sd card into the phone and plugged it in, the screen is still black but now it comes up as LGE AndrodNet USB Serial Port. When that came up, I thought I could use LGUP but there's a problem with every LG tool I used
LGUP Would Show unknown model and show a com port number and nothing after it. When I did select that port it would say "you have to select a known model please"
When I used LG FlashTool 1.8.1, every time I would load a firmware and press the yellow arrow, It would say "Failed PreviousLoad()". (I know this software works because I have tried it on different phones and it would work)
When I use LG Bridge, I'd select update error recovery and it would go on "checking device information" and would return back with "connect your mobile device to the USB port. If it is already connected, contact LG customer service.
When I use LG Flash Tool 2014, It would say "problem with communication between cell phone and PC"
Does anybody have any other ideas for me to try or any other tools to use? All help is appreciated
The mkboot binaries are available on github. If I remember correctly one of the output files when you split a boot image with mkboot can be used for that. Also, dd is a file conversion tool. I've been playing with the lglaf.py tool. But you would would need to be able to access laf. First you have to overcome edl. The flash programmer is out there somewhere.
Something I just discovered that work on a 8909 ZTE device might help you also. If you have the rawprogram0.xml file.
Code:
emmcdl -p COM"your port" -x rawprogram0.xml
You need all ur files in the same folder (ROM & emmcdl.exe).
## I'm going to play aroung with LGUP and see if some of the modded versions can find edl.
lehmancurtis said:
Something I just discovered that work on a 8909 ZTE device might help you also. If you have the rawprogram0.xml file.
Code:
emmcdl -p COM"your port" -x rawprogram0.xml
You need all ur files in the same folder (ROM & emmcdl.exe).
## I'm going to play aroung with LGUP and see if some of the modded versions can find edl.
Click to expand...
Click to collapse
Well I tried this and all that happens is that it gets stuck in sectors remaining and that's it. Im assuming this is the correct emmcdl that I found in my windows folder.
Code:
E:\LG K7\DZ Extractor With Combined System.bin>emmcdl -p COM"5" -x rawprogram0.xml
Version 2.16
Programming image
Finding all devices in emergency download mode...
Qualcomm HS-USB QDLoader 9008 (COM5)
Finding all disks on computer ...
\\.\PhysicalDrive5Successfully opened disk
start_sector: 34 physical_partition_number: 0 num_partition_sectors: 131072 filename: NON-HLOS.bin file_sector_offset: 0
Sparse image not detected -- loading binary
In offset: 0 out offset: 34 sectors: 101376
Sectors remaining: 99328
jimmysofat6864 said:
Something I just discovered that work on a 8909 ZTE device might help you also. If you have the rawprogram0.xml file.
Well I tried this and all that happens is that it gets stuck in sectors remaining and that's it. Im assuming this is the correct emmcdl that I found in my windows folder.
Click to expand...
Click to collapse
Try this
Code:
emmcdl.exe -p COM5 -x rawprogram0.xml SetActivePartition=0
lehmancurtis said:
Try this
Code:
emmcdl.exe -p COM5 -x rawprogram0.xml SetActivePartition=0
Click to expand...
Click to collapse
It appears the same thing happens even with that. If you have this phone can you send the files instead because it might be because my rom files are wrong. I don't think so but it's a possibility. Even with that the same thing happened.
Code:
E:\LG K7\DZ Extractor With Combined System.bin>emmcdl.exe -p COM5 -x rawprogram0.xml SetActivePartition=0
Version 2.16
Programming image
Finding all devices in emergency download mode...
Qualcomm HS-USB QDLoader 9008 (COM5)
Finding all disks on computer ...
0. \\.\PhysicalDrive0 Size: 244198MB, (500118192 sectors), size: 512 Mount:C:, Name:[]
1. \\.\PhysicalDrive1 Size: 14944MB, (30605312 sectors), size: 512 Mount:E:, Name:[]
\\.\PhysicalDrive5Successfully opened disk
start_sector: 34 physical_partition_number: 0 num_partition_sectors: 131072 filename: NON-HLOS.bin file_sector_offset: 0
Sparse image not detected -- loading binary
In offset: 0 out offset: 34 sectors: 101376
Sectors remaining: 99328
D o you have metro or TMobile?
lehmancurtis said:
D o you have metro or TMobile?
Click to expand...
Click to collapse
I have the MS330 Model so it's definitely a Metro PCS model.
Related
Anyone know about any custom room or kernel or recovery that works on Asus Live (G500TG / Z00YD) ?
I searched everywhere and didn't found anything custom for this model.
Please help.
I need recovery image of this model. Could you provide me a copy of your recovery?
ralp5628 said:
I need recovery image of this model. Could you provide me a copy of your recovery?
Click to expand...
Click to collapse
I'm using all stock.
You can get it from http://dlcdnet.asus.com/pub/ASUS/ZenFone/G500TG/UL-G500TG_ASUS_Z00YD-WW-12.0.0.41-user.zip
I didn't find a recovery image within that file. The only thing I can access is fastboot. My recovery is broken, my system doesn't boot (bootloop). :crying: :crying:
personal HELLO I also need recovery.img Asus Live (G500TG) Z00YD
I've managed to extract the system files (and kernel) from the zip, but no luck in flashing it back using fastboot. I think the problem is in the conversion from raw image to sparse (that fastboot uses).
To extract system raw ext4 partition from zip:
http://forum.xda-developers.com/and...-conver-lollipop-dat-files-to-t2978952/page11
To unpack boot.img:
http://forum.xda-developers.com/showthread.php?t=443994
The idea now is trying to boot from a ramdisk in the pc, to start adb service.
Guys, I figured out how to reverse the situation of hard brick.
1) First you need to download the kernel source code on the asus website. The file name is: ASUS Live (G500TG) Kernel Code (V12.0.0.26). Here is:
http :// dlcdnet.asus .com/pub/ASUS/ZenFone/G500TG/G500TG_Kernel_V12_0_0_26.zip?_ga=1.213911127.1348745149.1467264204
Inside it there are the images of all partitions, including scatter file.
2) You will need to download a program called SP Flash tool. Here: http :// spflashtool .com/. I'm currently using v5.1628
3) Open the tool flash sp as administrator (on Windows) or administrator privileges (using sudo on linux).
4) Extract the downloaded file and select the scatter file in sp flash tool.
5) Select download only.
6) Leave the phone without the battery for 30 seconds before connecting it to your computer. Put the battery again. Holding the - button (lower volume) connect it to the computer. Wait a bit and release the button. Click download in flash tool sp.
7) Wait until all the transfer is completed. After finishing connect the phone and put it to charge on power supply.
no select format+download, possible DTV problem in upgrade for new version
Alguém saber fazer alguma modificação no asus live? Bota outra rom, qualquer coisa? Entre em contato cmg 75988302133
ralp5628 said:
Guys, I figured out how to reverse the situation of hard brick.
1) First you need to download the kernel source code on the asus website. The file name is: ASUS Live (G500TG) Kernel Code (V12.0.0.26). Here is:
http :// dlcdnet.asus .com/pub/ASUS/ZenFone/G500TG/G500TG_Kernel_V12_0_0_26.zip?_ga=1.213911127.1348745149.1467264204
Inside it there are the images of all partitions, including scatter file.
2) You will need to download a program called SP Flash tool. Here: http :// spflashtool .com/. I'm currently using v5.1628
3) Open the tool flash sp as administrator (on Windows) or administrator privileges (using sudo on linux).
4) Extract the downloaded file and select the scatter file in sp flash tool.
5) Select download only.
6) Leave the phone without the battery for 30 seconds before connecting it to your computer. Put the battery again. Holding the - button (lower volume) connect it to the computer. Wait a bit and release the button. Click download in flash tool sp.
7) Wait until all the transfer is completed. After finishing connect the phone and put it to charge on power supply.
Click to expand...
Click to collapse
I don't get it, Where i put the extracted folder from the kernel source?
You need to extract the G500TG_Kernel_V12_0_0_26_zip.zip file and with the SP Flash Tool point to the scatter file inside the extracted folder. It will load all the partitions you just extracted.
ralp5628 said:
I didn't find a recovery image within that file. The only thing I can access is fastboot. My recovery is broken, my system doesn't boot (bootloop). :crying: :crying:
Click to expand...
Click to collapse
You fixed it?
vitorMndC said:
You fixed it?
Click to expand...
Click to collapse
Yessssss!! A long time ago.
Hello.
I'm struggling with this for days now without any result, so I decided to ask for some help.
I had this phone staying in my closet for a few months. A couple of days ago when I tried to charge it, I got the logo saying "Powered by Android" and get stuck there. (the phone was working perfectly before)
Interesting thing was, that most of the time I was not able to power it up at all.
Sometimes I managed to got it into Fastboot Mode TA, but not always.
Reading post here, I tried to reflash with stock ROM using YGDP.
It went smoothly, but now the bootloader is completely corrupted. Not able to get into Fastboot Mode anymore. Doesn't respond to any key at all.
It is recognised as Qualcomm hs-usb qdloader 9008.
After reading some more, I tried to get yhe bootloader back using QFIL without success.
No matter what I try, I get:
13: C:\Qualcomm\QPST\bin\NewFolder\prog_emmc_firehose_8916.mbn
14:37:07: Requested ID 13, file: "C:\Qualcomm\QPST\bin\NewFolder\prog_emmc_firehose_8916.mbn"
14:37:07: ERROR: function: is_ack_successful:988 SAHARA_NAK_INVALID_DEST_ADDR
14:37:07: ERROR: function: sahara_start:825 Exiting abruptly
14:37:07: ERROR: function: sahara_main:854 Sahara protocol error
14:37:07: 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
Same errors with prog_emmc_firehose_8936.mbn
It doesn't even get any acknowledge back from the phone?
Any help is highly appreciated.
Thanks.
Hi , I think you need a full emmc backup.img from working device in order to put your device in fastboot mode and be able to normaly flash stock firmware ....
https://forum.xda-developers.com/general/general/guide-unbrick-coolpad-dazen1-qualcomm-t3362253
Where to get an eMMC dump from?
I've tried with that dump in that post, but absolutely no change at all.
Will the phone read the SD card while it's off? At least that's what that post is telling me to do.
• After successful completion of writing eMMC backup image to SD card, insert the MicroSD card in your device and remove all sim cards. Insert battery into your device now. Do not power it on yet.
• Now you can boot to fastboot mode with the eMMC image on SDCARD.
Click to expand...
Click to collapse
I don't really get this part...
Hi you can't use backup from another device so you need to have the same working device it need to be rooted in order to do make debrick.img which you will make it bootable on micro sd card with Win32DiskImager tool . So then you should put your device in fastboot mode and flash normaly official stock firmware with YGDP tool ... If you don't know someone who can do that for you , check on the internet or YouTube who has device like your to make full emmc dump .
But it you don't have it then you can try Qualfast flash tool , but it required device to be into fastboot mode also you need to extract CPB firmware
Qualfast flash tool
https://androiddatahost.com/asaew
Download firmware from here :
http://www.mediafire.com/file/b3xdr59s6roj0jz/Coolpad_7576U_4.4.230.33.T3.140715.7576U.zip
Example how to extract CBP firmware files .
https://www.youtube.com/watch?v=OEbWKkzfiSA
Example how to use Qualfast flash tool :
https://www.youtube.com/watch?v=R4Bvy0Sax6Q
Just select path from extracted firmware for example C:/Users/SZabio/Desktop/Coolpad 7576U estracted firmware/ , wait all bars to be colored ....
Another option what you can try is one chinese app called COOLPAD DOWNLOAD ASSISTANT SETUP :
Download from here :
English language:
https://drive.google.com/file/d/0B5vyMGZJJmcnclVJb2Y2cHNNQkU/view
Chinese language
http://www.mediafire.com/file/e28degd1vjvevh3/Coolpad+Download+Assistant+Setup+V1.89_141231.rar
add path of CPB firmware (4.4.230.33.T3.140715.7576U.vf_ro.CPB) on number 2 ( browse) and click on green button ( Check Rom) , from up will be 100% loaded , now connect your device without the battery once the app detect your tool it will start writing files to your device .
Example how it should be :
https://www.youtube.com/watch?v=ZhWtvNVlqzE
Good Luck my friend , I hope you will finally get him to work again .
Thank you for trying to help, but as I said, the phone cannot be put into FastBoot mode.
It is completely dead, does not react to any button presses, does not even charge the battery anymore.
It is detected by the PC as "Qualcomm hs-usb qdloader 9008".
That's all.
I know nobody to get a full eMMC dump from unfortunately.
I've found out, that the phone's CPU is a Qualcomm MSM8210 Snapdragon 200, so I tried prog_emmc_firehose_8x10.mbn programming file.
Now QFIL is able to communicate with the phone, but all I'm getting is a bunch of errors, because the configuration .xml files are wrong.
I need rawprogram0.xml patch0.xml and partition.xml for this phone.
I don't understand why the bootloader was not blocked, so it could not have been overwritten by mistake.
Does anyone have some info on how the partitions are organised? Would be enough to write the bootloader in correctly, to get fast boot mode working again?
Hi everyone,
Recently I messed up something causing most of the sensors not to work anymore, only proximity and light sensor were working.
After hours of trial and error I found the solution to restore functions that have been lost due to corrupted partitions.
Remember I am not responsible if anything goes wrong or gets worse, we are going to use EDL mode (Emergency Download Mode) so be careful! YOU WILL LOSE YOUR DATA!
This guide is intended for the Redmi 5A (riva), but I am pretty sure it will work with other models!
To sum it up, we are going to edit (if needed for your model) and flash the official Xiaomi fastboot rom via EDL mode to the phone.
First make sure your bootloader is unlocked. If not, follow the steps at https://en.miui.com/unlock/
Downloading and installing the required tools and drivers
First, download all the tools you need to start the process:
From http://en.miui.com/a-234.html download the MIUI ROM flashing tool, and the correct fastboot rom (I chose Stable, that worked for me).
From https://gsmusbdriver.com/xiaomi-redmi-5a download the Qualcomm driver (you can browse the website for drivers for other models).
Now, extract the rom file. You will get another compressed folder, extract that one again.
Extract and install the Qualcomm driver.
Extract and open the MI flash tool.
In the flash tool, on the upper-left click 'Driver' and 'Install', now preferably reboot your computer to be sure all drivers are loaded properly.
Editing the downloaded ROM
In my case, the 'Persist' partition was included in the rom, but not included in the flash script of the Redmi 5A rom.
By adding a few lines to the scripts I was able to include the 'Persist' partition so that the flash tool used it:
1a
Navigate to the extracted rom folder, you will find a file named 'flash_all.bat'. Open this file with notepad, and check if there is any mention of the word 'Persist'. If there is, continue from section 1b below. If not, please continue here.
Add the line that refers to 'Persist' like the other lines at the end of the script. In my case I had to add the following line just above the line that contains 'flash system':
Code:
fastboot %* flash persist "%~dp0images\persist.img" || @echo "Flash persist error" && exit /B 1
Now save and close the file.
1b
There is another file to be edited, this time inside the 'images' folder within the rom folder. Here find the file named 'rawprogram0.xml'
In this file, about halfway down you will find a line that has 'label=persist' in it, but no location to this file.
Currently it will look like this:
Code:
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="" label="persist" num_partition_sectors="65536" physical_partition_number="0" size_in_KB="32768.0" sparse="true" start_byte_hex="0xf4000000" start_sector="7995392"/>
Now edit the line to look like this:
Code:
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="[B]persist.img[/B]" label="persist" num_partition_sectors="65536" physical_partition_number="0" size_in_KB="32768.0" sparse="true" start_byte_hex="0xf4000000" start_sector="7995392"/>
Do not copy and replace this line from here, instead just type in 'persist.img'! The values at the end of this line may vary between my and your rom!
1c
The last file that needs an edit is the file named 'crclist.txt' in the 'images' folder.
First, go to https://emn178.github.io/online-tools/crc32_checksum.html and drag the 'persist.img' file into the rectangle box. Copy the result you get.
Next, open the 'crclist.txt' file with notepad. At the bottom, add 'persist 0x' followed by the value you copied (use lower-case characters), for example;
Code:
persist 0x8932e19d
Save and close the file.
Now the rom is prepared to include 'Persist.img' in the flash script.
Booting the phone into EDL mode and flashing the rom
Flashing in normal fastboot mode didn't work, but in EDL mode it does.
To boot in EDL mode, hold both 'Power' and 'Volume-down' buttons until you see the 'Fastboot' screen. Connect the phone to the PC.
Next, open the flash tool folder and open the Mi flash tool. Click the left button and select the folder where the extracted and edited rom is.
Now make sure in the bottom-right to select 'flash_all.bat' and not 'flash_all_lock.bat. If you leave it on 'flash_all_lock.bat' it will not flash 'persist.img' and will also lock the bootloader. 'flash_all.bat' does not lock the bootloader.
Go back to the flash tool folder and navigate to 'MI-FLASH 2018-5-28\MiFlash2018-5-28-0\Source\ThirdParty\Google\Android'. Copy the path to this folder.
Open CMD (Win-key + R, type cmd, hit enter) and type
Code:
cd "Paste copied path here"
and hit enter. You should be able to type 'fastboot devices' and see one line appear.
When you see the device is listed, type
Code:
fastboot oem edl
and hit enter. The fastboot screen on the phone should go away.
Next go to the opened flash tool, click 'refresh' on the right. You should see one line starting with 'COM' and a number. Now you can click 'flash' to start the flashing process.
Note that you may get an error about 'hello message', that is because there is a time limit between booting in EDL mode and flashing. Try again by holding 'Power' and 'Volume-down' until you see the 'fastboot' screen again, then type 'fastboot oem edl' again.
After some time the status in the flash tool turns green and flashing is complete. Hold 'Power' and 'Volume-down' until the phone reboots and wait for first boot (this can take a while).
I hope you were able to solve the issues you had with your phone! If anything is unclear, please let me know.
Hey there,
The accelerometer on my Redmi 5A was messed up badly after a few miui.eu rom flashes and none of the other custom roms would boot up too. I found your guide to be very helpful and to the point. I was able to flash the stable rom successfully which fixed the sensors. Huge thanks to you! .
---------- Post added at 07:08 AM ---------- Previous post was at 06:58 AM ----------
Hey there,
The accelerometer on my Redmi 5A was messed up badly after a few miui.eu rom flashes and none of the other custom roms would boot up too. I found your guide to be very helpful and to the point. I was able to flash the stable rom successfully which fixed the sensors. Huge thanks to you! .
sanchaz12 said:
Hi everyone,
Recently I messed up something causing most of the sensors not to work anymore, only proximity and light sensor were working.
After hours of trial and error I found the solution to restore functions that have been lost due to corrupted partitions.
Remember I am not responsible if anything goes wrong or gets worse, we are going to use EDL mode (Emergency Download Mode) so be careful! YOU WILL LOSE YOUR DATA!
This guide is intended for the Redmi 5A (riva), but I am pretty sure it will work with other models!
To sum it up, we are going to edit (if needed for your model) and flash the official Xiaomi fastboot rom via EDL mode to the phone.
First make sure your bootloader is unlocked. If not, follow the steps at https://en.miui.com/unlock/
Downloading and installing the required tools and drivers
First, download all the tools you need to start the process:
From http://en.miui.com/a-234.html download the MIUI ROM flashing tool, and the correct fastboot rom (I chose Stable, that worked for me).
From https://gsmusbdriver.com/xiaomi-redmi-5a download the Qualcomm driver (you can browse the website for drivers for other models).
Now, extract the rom file. You will get another compressed folder, extract that one again.
Extract and install the Qualcomm driver.
Extract and open the MI flash tool.
In the flash tool, on the upper-left click 'Driver' and 'Install', now preferably reboot your computer to be sure all drivers are loaded properly.
Editing the downloaded ROM
In my case, the 'Persist' partition was included in the rom, but not included in the flash script of the Redmi 5A rom.
By adding a few lines to the scripts I was able to include the 'Persist' partition so that the flash tool used it:
1a
Navigate to the extracted rom folder, you will find a file named 'flash_all.bat'. Open this file with notepad, and check if there is any mention of the word 'Persist'. If there is, continue from section 1b below. If not, please continue here.
Add the line that refers to 'Persist' like the other lines at the end of the script. In my case I had to add the following line just above the line that contains 'flash system':
Now save and close the file.
1b
There is another file to be edited, this time inside the 'images' folder within the rom folder. Here find the file named 'rawprogram0.xml'
In this file, about halfway down you will find a line that has 'label=persist' in it, but no location to this file.
Currently it will look like this:
Now edit the line to look like this:
Do not copy and replace this line from here, instead just type in 'persist.img'! The values at the end of this line may vary between my and your rom!
1c
The last file that needs an edit is the file named 'crclist.txt' in the 'images' folder.
First, go to https://emn178.github.io/online-tools/crc32_checksum.html and drag the 'persist.img' file into the rectangle box. Copy the result you get.
Next, open the 'crclist.txt' file with notepad. At the bottom, add 'persist 0x' followed by the value you copied (use lower-case characters), for example;
Save and close the file.
Now the rom is prepared to include 'Persist.img' in the flash script.
Booting the phone into EDL mode and flashing the rom
Flashing in normal fastboot mode didn't work, but in EDL mode it does.
To boot in EDL mode, hold both 'Power' and 'Volume-down' buttons until you see the 'Fastboot' screen. Connect the phone to the PC.
Next, open the flash tool folder and open the Mi flash tool. Click the left button and select the folder where the extracted and edited rom is.
Now make sure in the bottom-right to select 'flash_all.bat' and not 'flash_all_lock.bat. If you leave it on 'flash_all_lock.bat' it will not flash 'persist.img' and will also lock the bootloader. 'flash_all.bat' does not lock the bootloader.
Go back to the flash tool folder and navigate to 'MI-FLASH 2018-5-28\MiFlash2018-5-28-0\Source\ThirdParty\Google\Android'. Copy the path to this folder.
Open CMD (Win-key + R, type cmd, hit enter) and type
and hit enter. You should be able to type 'fastboot devices' and see one line appear.
When you see the device is listed, type
and hit enter. The fastboot screen on the phone should go away.
Next go to the opened flash tool, click 'refresh' on the right. You should see one line starting with 'COM' and a number. Now you can click 'flash' to start the flashing process.
Note that you may get an error about 'hello message', that is because there is a time limit between booting in EDL mode and flashing. Try again by holding 'Power' and 'Volume-down' until you see the 'fastboot' screen again, then type 'fastboot oem edl' again.
After some time the status in the flash tool turns green and flashing is complete. Hold 'Power' and 'Volume-down' until the phone reboots and wait for first boot (this can take a while).
I hope you were able to solve the issues you had with your phone! If anything is unclear, please let me know.
Click to expand...
Click to collapse
We can just flash the sensorfix zip via twrp
NaAnBcEhEuL9A8K7 said:
We can just flash the sensorfix zip via twrp
Click to expand...
Click to collapse
link >???
ahked.ragab said:
link >???
Click to expand...
Click to collapse
I dont have link, got it from https://t.me/Redmi_5a
this method worked, at first I was confused, I was looking for ways to fix it. after I found this, this worked. thanks man
hi, can I flash the persist.img file via adb in fastboot.
Here is the link for sensorfix.xip
https://drive.google.com/file/d/1ZgaWydW4c7Eo5vuRw_Vhc6EVmBFThNV2/view
Give me thanks
---------- Post added at 08:46 AM ---------- Previous post was at 08:40 AM ----------
sanchaz12 said:
Hi everyone,
Recently I messed up something causing most of the sensors not to work anymore, only proximity and light sensor were working.
After hours of trial and error I found the solution to restore functions that have been lost due to corrupted partitions.
Remember I am not responsible if anything goes wrong or gets worse, we are going to use EDL mode (Emergency Download Mode) so be careful! YOU WILL LOSE YOUR DATA!
This guide is intended for the Redmi 5A (riva), but I am pretty sure it will work with other models!
To sum it up, we are going to edit (if needed for your model) and flash the official Xiaomi fastboot rom via EDL mode to the phone.
First make sure your bootloader is unlocked. If not, follow the steps at https://en.miui.com/unlock/
Downloading and installing the required tools and drivers
First, download all the tools you need to start the process:
From http://en.miui.com/a-234.html download the MIUI ROM flashing tool, and the correct fastboot rom (I chose Stable, that worked for me).
From https://gsmusbdriver.com/xiaomi-redmi-5a download the Qualcomm driver (you can browse the website for drivers for other models).
Now, extract the rom file. You will get another compressed folder, extract that one again.
Extract and install the Qualcomm driver.
Extract and open the MI flash tool.
In the flash tool, on the upper-left click 'Driver' and 'Install', now preferably reboot your computer to be sure all drivers are loaded properly.
Editing the downloaded ROM
In my case, the 'Persist' partition was included in the rom, but not included in the flash script of the Redmi 5A rom.
By adding a few lines to the scripts I was able to include the 'Persist' partition so that the flash tool used it:
1a
Navigate to the extracted rom folder, you will find a file named 'flash_all.bat'. Open this file with notepad, and check if there is any mention of the word 'Persist'. If there is, continue from section 1b below. If not, please continue here.
Add the line that refers to 'Persist' like the other lines at the end of the script. In my case I had to add the following line just above the line that contains 'flash system':
Code:
fastboot %* flash persist "%~dp0images\persist.img" || @echo "Flash persist error" && exit /B 1
Now save and close the file.
1b
There is another file to be edited, this time inside the 'images' folder within the rom folder. Here find the file named 'rawprogram0.xml'
In this file, about halfway down you will find a line that has 'label=persist' in it, but no location to this file.
Currently it will look like this:
Code:
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="" label="persist" num_partition_sectors="65536" physical_partition_number="0" size_in_KB="32768.0" sparse="true" start_byte_hex="0xf4000000" start_sector="7995392"/>
Now edit the line to look like this:
Code:
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="[B]persist.img[/B]" label="persist" num_partition_sectors="65536" physical_partition_number="0" size_in_KB="32768.0" sparse="true" start_byte_hex="0xf4000000" start_sector="7995392"/>
Do not copy and replace this line from here, instead just type in 'persist.img'! The values at the end of this line may vary between my and your rom!
1c
The last file that needs an edit is the file named 'crclist.txt' in the 'images' folder.
First, go to https://emn178.github.io/online-tools/crc32_checksum.html and drag the 'persist.img' file into the rectangle box. Copy the result you get.
Next, open the 'crclist.txt' file with notepad. At the bottom, add 'persist 0x' followed by the value you copied (use lower-case characters), for example;
Code:
persist 0x8932e19d
Save and close the file.
Now the rom is prepared to include 'Persist.img' in the flash script.
Booting the phone into EDL mode and flashing the rom
Flashing in normal fastboot mode didn't work, but in EDL mode it does.
To boot in EDL mode, hold both 'Power' and 'Volume-down' buttons until you see the 'Fastboot' screen. Connect the phone to the PC.
Next, open the flash tool folder and open the Mi flash tool. Click the left button and select the folder where the extracted and edited rom is.
Now make sure in the bottom-right to select 'flash_all.bat' and not 'flash_all_lock.bat. If you leave it on 'flash_all_lock.bat' it will not flash 'persist.img' and will also lock the bootloader. 'flash_all.bat' does not lock the bootloader.
Go back to the flash tool folder and navigate to 'MI-FLASH 2018-5-28\MiFlash2018-5-28-0\Source\ThirdParty\Google\Android'. Copy the path to this folder.
Open CMD (Win-key + R, type cmd, hit enter) and type
Code:
cd "Paste copied path here"
and hit enter. You should be able to type 'fastboot devices' and see one line appear.
When you see the device is listed, type
Code:
fastboot oem edl
and hit enter. The fastboot screen on the phone should go away.
Next go to the opened flash tool, click 'refresh' on the right. You should see one line starting with 'COM' and a number. Now you can click 'flash' to start the flashing process.
Note that you may get an error about 'hello message', that is because there is a time limit between booting in EDL mode and flashing. Try again by holding 'Power' and 'Volume-down' until you see the 'fastboot' screen again, then type 'fastboot oem edl' again.
After some time the status in the flash tool turns green and flashing is complete. Hold 'Power' and 'Volume-down' until the phone reboots and wait for first boot (this can take a while).
I hope you were able to solve the issues you had with your phone! If anything is unclear, please let me know.
Click to expand...
Click to collapse
You don't need to this much sh*t !
Just flash the provided zip via twrp.
You won't loose data
thank you Asif the legend ?. however i found a alternate way to fix it. fastboot or edl mode or normal twrp are not able to access the persist location. i flashed orage fox recovery to mount persist location. then in miui official fastboot rom i got persist image. and i am able to flash it via new recovery. all sensors are working fine now.
Welcome
Atif the legend sir you are truly legend thank uh so much. I tryed many things to fix this problem but now all sensors working fine. Thanks for your help.
How to quit edl mode? i received the hello error, and then even when i do press power and vol down i cant reboot it
---------- Post added at 12:35 PM ---------- Previous post was at 12:10 PM ----------
sanchaz12 said:
Hi everyone,
Recently I messed up something causing most of the sensors not to work anymore, only proximity and light sensor were working.
After hours of trial and error I found the solution to restore functions that have been lost due to corrupted partitions.
Remember I am not responsible if anything goes wrong or gets worse, we are going to use EDL mode (Emergency Download Mode) so be careful! YOU WILL LOSE YOUR DATA!
This guide is intended for the Redmi 5A (riva), but I am pretty sure it will work with other models!
To sum it up, we are going to edit (if needed for your model) and flash the official Xiaomi fastboot rom via EDL mode to the phone.
First make sure your bootloader is unlocked. If not, follow the steps at https://en.miui.com/unlock/
Downloading and installing the required tools and drivers
First, download all the tools you need to start the process:
From http://en.miui.com/a-234.html download the MIUI ROM flashing tool, and the correct fastboot rom (I chose Stable, that worked for me).
From https://gsmusbdriver.com/xiaomi-redmi-5a download the Qualcomm driver (you can browse the website for drivers for other models).
Now, extract the rom file. You will get another compressed folder, extract that one again.
Extract and install the Qualcomm driver.
Extract and open the MI flash tool.
In the flash tool, on the upper-left click 'Driver' and 'Install', now preferably reboot your computer to be sure all drivers are loaded properly.
Editing the downloaded ROM
In my case, the 'Persist' partition was included in the rom, but not included in the flash script of the Redmi 5A rom.
By adding a few lines to the scripts I was able to include the 'Persist' partition so that the flash tool used it:
1a
Navigate to the extracted rom folder, you will find a file named 'flash_all.bat'. Open this file with notepad, and check if there is any mention of the word 'Persist'. If there is, continue from section 1b below. If not, please continue here.
Add the line that refers to 'Persist' like the other lines at the end of the script. In my case I had to add the following line just above the line that contains 'flash system':
Code:
fastboot %* flash persist "%~dp0images\persist.img" || @echo "Flash persist error" && exit /B 1
Now save and close the file.
1b
There is another file to be edited, this time inside the 'images' folder within the rom folder. Here find the file named 'rawprogram0.xml'
In this file, about halfway down you will find a line that has 'label=persist' in it, but no location to this file.
Currently it will look like this:
Code:
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="" label="persist" num_partition_sectors="65536" physical_partition_number="0" size_in_KB="32768.0" sparse="true" start_byte_hex="0xf4000000" start_sector="7995392"/>
Now edit the line to look like this:
Code:
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="[B]persist.img[/B]" label="persist" num_partition_sectors="65536" physical_partition_number="0" size_in_KB="32768.0" sparse="true" start_byte_hex="0xf4000000" start_sector="7995392"/>
Do not copy and replace this line from here, instead just type in 'persist.img'! The values at the end of this line may vary between my and your rom!
1c
The last file that needs an edit is the file named 'crclist.txt' in the 'images' folder.
First, go to https://emn178.github.io/online-tools/crc32_checksum.html and drag the 'persist.img' file into the rectangle box. Copy the result you get.
Next, open the 'crclist.txt' file with notepad. At the bottom, add 'persist 0x' followed by the value you copied (use lower-case characters), for example;
Code:
persist 0x8932e19d
Save and close the file.
Now the rom is prepared to include 'Persist.img' in the flash script.
Booting the phone into EDL mode and flashing the rom
Flashing in normal fastboot mode didn't work, but in EDL mode it does.
To boot in EDL mode, hold both 'Power' and 'Volume-down' buttons until you see the 'Fastboot' screen. Connect the phone to the PC.
Next, open the flash tool folder and open the Mi flash tool. Click the left button and select the folder where the extracted and edited rom is.
Now make sure in the bottom-right to select 'flash_all.bat' and not 'flash_all_lock.bat. If you leave it on 'flash_all_lock.bat' it will not flash 'persist.img' and will also lock the bootloader. 'flash_all.bat' does not lock the bootloader.
Go back to the flash tool folder and navigate to 'MI-FLASH 2018-5-28\MiFlash2018-5-28-0\Source\ThirdParty\Google\Android'. Copy the path to this folder.
Open CMD (Win-key + R, type cmd, hit enter) and type
Code:
cd "Paste copied path here"
and hit enter. You should be able to type 'fastboot devices' and see one line appear.
When you see the device is listed, type
Code:
fastboot oem edl
and hit enter. The fastboot screen on the phone should go away.
Next go to the opened flash tool, click 'refresh' on the right. You should see one line starting with 'COM' and a number. Now you can click 'flash' to start the flashing process.
Note that you may get an error about 'hello message', that is because there is a time limit between booting in EDL mode and flashing. Try again by holding 'Power' and 'Volume-down' until you see the 'fastboot' screen again, then type 'fastboot oem edl' again.
After some time the status in the flash tool turns green and flashing is complete. Hold 'Power' and 'Volume-down' until the phone reboots and wait for first boot (this can take a while).
I hope you were able to solve the issues you had with your phone! If anything is unclear, please let me know.
Click to expand...
Click to collapse
Help plz? it shows the qualcomm on devices manager but i cant quit edl mode and gives me that error from hello message, holding power plus anything does not reboots it
jasonhelene said:
How to quit edl mode? i received the hello error, and then even when i do press power and vol down i cant reboot it
---------- Post added at 12:35 PM ---------- Previous post was at 12:10 PM ----------
Help plz? it shows the qualcomm on devices manager but i cant quit edl mode and gives me that error from hello message, holding power plus anything does not reboots it
Click to expand...
Click to collapse
You may have to hold the buttons for up to 30 seconds for the phone to reset, longer than usual.
Mimax 3
Hi, I need to know if this process is valid for a MiMax 3 with Chinese rom and with closed bootloader.
I have the phone without being able to activate Wi-Fi, sim and bluettoh and I think it's because of the persist partition ...
I can put the phone in edl mode. Please help
I wasn't aware lol
Hi,
I have no idea how to extract the MIUI11 beta file to MI 6X, I wanted to use its tutorials but the download link doesn't open, could you tell me which program used to edit this persist.img file? Or if you can make this file available. I have but it works only with MIUI 10 and I'm on MIUI 11.
Is using EDL mode without unlock bootloader?
I have same issue.
I get same issue error (find device is…. your device unsafe)
But , All the sensors are not work.
#proximity sensor
#Auto rotation
#Camara(full Black Screen)
#Youtube
#Flash light
Are not working….
Please help me.
_______________________________________
Is i am using flash the phone without unlock bootloader Using EDL mode.
Please help me.
_____________________________________
thankyou so much sir it worked can you help me with lost imei and simcards not working
i cant make it work
Vinod Banwala said:
thankyou so much sir it worked can you help me with lost imei and simcards not working
Click to expand...
Click to collapse
what did you do? at me says comething like cant do, cause its only read disk, when goes to the persist drive help
How can i do to make my own sensorsfix.zip?
Give me thanks
---------- Post added at 08:46 AM ---------- Previous post was at 08:40 AM ----------
You don't need to this much sh*t !
Just flash the provided zip via twrp.
You won't loose data[/QUOTE]
Friend i want to make my own file to flash in other device (MI 9T Pro), can you show us how try it. I did extracted the files into persist.img, but i didn't find the sns.reg, file included in your .zip.
This instruction could help to many people with this problem.
Thank u so much. :good:
the phone reboots into recovery (I install the wrong recovery, that's why the bootloop), it does not enter the fastboot and when you enter the recovery it just turns off on the boot screen. I can't get into the system either. The bootloader is unlocked. I tried the SP flash tool and it gave me an error brom. And mtk-client, as I understand it, was fixed on miui 14. because there is also an error there. help me please
Hi, did you manage to solve this problem?
What have you tried with mtk client?
hi, I still haven't solved the problem. In mtkclent, I tried to flash the "boot.img" file through brom mode
If the boot flash was successful but you still cant access fastboot or recovery try reflashing the stock rom using brom mode
Step1: Setting up the files
Download the stock rom for your device (I prefer miuirom website)
Extract the downloaded rom
Check if Mediatek USB VCOM Drivers and UsbDK are installed correctly.
Set up mtkclient (follow official guide)
TIP:
After some research i found out that you can speed up the mtk process by modifying the mtk_daxflash.py file. (Source)
Open the file using notepad and search for this line:
Python:
dsize = min(length, 0x200)
And replace it with this:
Python:
dsize = min(length, 0x2004)
Step2: Fix your device
Open the command prompt in the mtk folder
Run this command WITHOUT your device plugged in:
WARNING! This will erase all data on the device
py -3 mtk wl <extractedrompath>\images\
(py -3 or python depending on the installed python version)
plug in your phone and put it in brom mode. the procedure should start immediately
This will flash all the files inside the images folder in the correct partitions (may take a while)
In the procedure you may see some partitions error but thats normal
When the first command is done run this second command:
py -3 mtk w boot_a "<extractedrompath>images\boot.img"
And this command:
py -3 mtk w boot_b"<extractedrompath>images\boot.img"
This will write the boot image to the boot_a and boot_b partition.
Now if everything succeded you should be able to boot into miui.
If not you should be able at least to boot into fastboot, try following step3
Step3: Flash the rom in fastboot (If required)
In the extracted rom path you should see a .bat and a .sh named flash_all.
Put your phone in fastboot mode and run the bat (Windows) or the sh (macOS/Linux) file.
If everything succeded you should have your phone working again .
Hope that your device will work again!
Tria13 said:
the phone reboots into recovery (I install the wrong recovery, that's why the bootloop), it does not enter the fastboot and when you enter the recovery it just turns off on the boot screen. I can't get into the system either. The bootloader is unlocked. I tried the SP flash tool and it gave me an error brom. And mtk-client, as I understand it, was fixed on miui 14. because there is also an error there. help me please
Click to expand...
Click to collapse
Please PM me if you want your device to be flashed using authorised Xiaomi Server.
I have the same device and I bricked it a while ago by flashing twrp and booting to recovery
From my understanding edl flashing can only be done with an authorized xiaomi account. I don't have one so I had to pay someone on telegram who had one and who could unbrick it. He used a modified version of SP Flash Tool. Although he struggled a bit he got it fixed the next day after I downgraded to windows 10. If you want to avoid bricking this device I recommend you don't use twrp altogether or be very cautious and only use twrp builds from the official telegram group. Compatibility depends on the kernel and android version. For now aosp-based roms have issues with the gpu anyways. (always under 100% load)
Also there is a mtk bootprotect magisk module which might help. (I don't think it will if you flash wrong twrp tho)
I hope these informations are somewhat useful
WolfnHex said:
If the boot flash was successful but you still cant access fastboot or recovery try reflashing the stock rom using brom mode
Step1: Setting up the files
Download the stock rom for your device (I prefer miuirom website)
Extract the downloaded rom
Check if Mediatek USB VCOM Drivers and UsbDK are installed correctly.
Set up mtkclient (follow official guide)
TIP:
After some research i found out that you can speed up the mtk process by modifying the mtk_daxflash.py file. (Source)
Open the file using notepad and search for this line:
Python:
dsize = min(length, 0x200)
And replace it with this:
Python:
dsize = min(length, 0x2004)
Step2: Fix your device
Open the command prompt in the mtk folder
Run this command WITHOUT your device plugged in:
WARNING! This will erase all data on the device
py -3 mtk wl <extractedrompath>\images\
(py -3 or python depending on the installed python version)
plug in your phone and put it in brom mode. the procedure should start immediately
This will flash all the files inside the images folder in the correct partitions (may take a while)
In the procedure you may see some partitions error but thats normal
When the first command is done run this second command:
py -3 mtk w boot_a "<extractedrompath>images\boot.img"
And this command:
py -3 mtk w boot_b"<extractedrompath>images\boot.img"
This will write the boot image to the boot_a and boot_b partition.
Now if everything succeded you should be able to boot into miui.
If not you should be able at least to boot into fastboot, try following step3
Step3: Flash the rom in fastboot (If required)
In the extracted rom path you should see a .bat and a .sh named flash_all.
Put your phone in fastboot mode and run the bat (Windows) or the sh (macOS/Linux) file.
If everything succeded you should have your phone working again .
Hope that your device will work again!
Click to expand...
Click to collapse
hello, thanks for the answer, but I already tried this and I got an error with kamakiri. In the git mtk client, the person was told that it was fixed for 14 miui.
Tria13 said:
hello, thanks for the answer, but I already tried this and I got an error with kamakiri. In the git mtk client, the person was told that it was fixed for 14 miui.
Click to expand...
Click to collapse
The thing is ---- Auth bypass is not yet available for your chipset type MT6895.
We have to wait until we can bypass auth to flash using SP Flash tool.
Tria13 said:
hello, thanks for the answer, but I already tried this and I got an error with kamakiri. In the git mtk client, the person was told that it was fixed for 14 miui.
Click to expand...
Click to collapse
im sorry to hear this
mvikrant97 is right. MT6895 is currently unsupported. you just have to wait
mvikrant97 said:
Please PM me if you want your device to be flashed using authorised Xiaomi Server.
Click to expand...
Click to collapse
Hi, sorry I didn't see your post earlier. Can you solve your phone problem with an authorized Xiaomi Server? You can write your telegram or something else by which I can write to you. Thanks for the answer
Hi everyone, I bought this phone working from second hand but the seller told me he tried to unlock the bootloader without success and the phone still loose the fingerprint sensor, so I decided to unlock the bootloader successfully following THIS thread and made a downgrade to Android 9 according to THIS other tutorial hopping to get it work again but I wasn't able to do it, so I decided to just use LGUP to install the same Android 12 that I had but the problem started at this point because once the KDZ was installed successfully, the deviced got a bootloop but I still was able to get into EDL, Fastboot and Download Mode, so I tried the steps from THIS other thread to unbrick it but it got even worse at this point, I flashed all the abl, xbl, etc. partitions and the "rawprograme files" via QFIL and then the phone won't even gave any life signals. I contacted someone that some months ago had the same problem and he told me that I could get into EDL by short pining the test point on the motherboard, which actually worked, so I extracted the KDZ Android 9 rom that I flashed in the first place to get the original abl, xbl, etc. partitions that I crossflashed from a v50 (Which I downloaded from the corresponding thread for unbrick), in other words I flashed the same partitions with the correct v50s files instead other model ones. So now this is where I'm right now, the phone don't turns on at all but when I connect it to the PC it gets recognized as LGE Android Platform USB Serial Port (COM11) and the buttons combinations don't work at all, so still can't get into Download mode by any method or even turn off the device, but I still can disconnect the battery and short pin the Qualcomm 9008 mode to use QFIL.
Would someone please be so kind of telling me how could I recover the Download Mode to use the COM4 and COM5 ports to flash the phone via LGUP?. According to THIS other thread, I could get the correct XML "rawprograme files" for my device (which I crossflashed with the v50) from a KDZ using some tools and Python, but I have to be honest: I DON'T KNOW HOW, even with the step by step tutorial.
At this point I think this would be the right step, to flash all the original files for my model and get the Download Mode back to be able to flash the KDZ rom via LGUP and update via OTA to Android 12 again to avoid the bootloop problem.
try to reflash(QFIL method) modified abl should get the download mode back
darrelama said:
try to reflash(QFIL method) modified abl should get the download mode back
Click to expand...
Click to collapse
Thanks for replying, but I have some questions:
1. The abl file you mean is the engineering one? And...
2. Would you be so kind of telling me how to flash via QFIL? I've seen that it's possible but as far as I know, I need a specific type of rom files to do it, and I don't know how to convert a KDZ or where to download a QFIL ROM.
Thanks!
iMarzateD said:
Thanks for replying, but I have some questions:
1. The abl file you mean is the engineering one? And...
2. Would you be so kind of telling me how to flash via QFIL? I've seen that it's possible but as far as I know, I need a specific type of rom files to do it, and I don't know how to convert a KDZ or where to download a QFIL ROM.
Thanks!
Click to expand...
Click to collapse
yes, engineering one mentioned here （THIS）
QFIL>Tools > Partition Manager
read abl_a and abl_b to backup then load abl engineering file to both
basically the same steps up to the following:
"Go back to Partition Manager and right click on abl_a again then select Manage Partition Data, then Select Load and choose the abl engineering file.
Do the same for abl_b."
then try download mode
darrelama said:
yes, engineering one mentioned here （THIS）
QFIL>Tools > Partition Manager
read abl_a and abl_b to backup then load abl engineering file to both
basically the same steps up to the following:
"Go back to Partition Manager and right click on abl_a again then select Manage Partition Data, then Select Load and choose the abl engineering file.
Do the same for abl_b."
then try download mode
Click to expand...
Click to collapse
Hello again, already tried flashing the engineering abl but I still can't get into download mode. The phone keeps off the whole time and by plugging in the USB cable, no matter what button combination, the PC always recognizes it as the same LGE Android Patform USB Serial Port (COM11), the only other state of the device is the Qualcomm 9008 by pinning the motherboard. This specific COM11 state never was able to flash anything by PC, I don't know what actual mode is, but when I was able to set the devide in Download Mode the PC always showed 2 devices in the Device Manager, the COM5 and the COM4, that way I knew I was able to use the LGUP to flash. I'm thinking that I'm not setting the phone on the correct state to flash by any method, but since the buttons seems not to work, I don't know how could I do it.
While on this mode "LGE Android Patform USB Serial Port (COM11)", try to hold both power and vol- for some seconds until the "LGE Android Patform USB Serial Port (COM11)" disappear from your PC device manager and immediately release both and now hold vol+ button to get into download mode.
You can do it while on the 9008 mode too though.
Maybe that can help.
I have LUNs backup for v50s but I can't upload it due to my internet plan quota limit.
ardian1899 said:
While on this mode "LGE Android Patform USB Serial Port (COM11)", try to hold both power and vol- for some seconds until the "LGE Android Patform USB Serial Port (COM11)" disappear from your PC device manager and immediately release both and now hold vol+ button to get into download mode.
You can do it while on the 9008 mode too though.
Maybe that can help.
I have LUNs backup for v50s but I can't upload it due to my internet plan quota limit.
Click to expand...
Click to collapse
Thanks, I'll try that for sure to see if I can get into the Download Mode or something. I would appreciate so much if you could share your backup, since I think I could restore the whole firmware with it, but I don't have any experience on the "LUNs" tho. I'm any case, I don't have too much time every week to give it a try, so I hope tomorrow I could test the combo you say.