Related
My phone it's bricked, I rooted my w100 yesterday and to celebrate I installed the ifont app from the market, but at the third change didn't reboot any more, I have searched for the rom but seems to be very new... Neither the recovery or something help me out, I was looking for the preloader or somethin ... I'm just desperate.
Some help will be very appreciated!
How did you root it?
Uri997 said:
How did you root it?
Click to expand...
Click to collapse
its pretty easy, you can use the motochopper tool, instal the mtk6589 driver and connect your phone to the pc, then hit the runme.bat file and follow the instructions, very easy!
Here you have a very simple and good post that surely will help you.
http://forum.xda-developers.com/showthread.php?t=2247537
Best wishes!
josepbennet said:
My phone it's bricked, I rooted my w100 yesterday and to celebrate I installed the ifont app from the market, but at the third change didn't reboot any more, I have searched for the rom but seems to be very new... Neither the recovery or something help me out, I was looking for the preloader or somethin ... I'm just desperate.
Some help will be very appreciated!
Click to expand...
Click to collapse
here u go:
kokuo81 said:
Here you have it
THL W100 rooted ROM:
https://mega.co.nz/#!SEYFlbxT!LYK3Rw231-M6eA0O75ccZRgEQ7JLvBrZDm_MDqdLvBU
(credits to josemdg90 on htcmania)
Originally taken from:
http://4pda.ru/forum/index.php?showtopic=462368&st=200
Hope it helps
Cheers
kok
Click to expand...
Click to collapse
josepbennet said:
My phone it's bricked, I rooted my w100 yesterday and to celebrate I installed the ifont app from the market, but at the third change didn't reboot any more, I have searched for the rom but seems to be very new... Neither the recovery or something help me out, I was looking for the preloader or somethin ... I'm just desperate.
Some help will be very appreciated!
Click to expand...
Click to collapse
You must be the absolute first to brick your w100.
Did you succeed installation of kok's rom ?
I bricked my phone too...
First I installed a partitioning app to my device, my plan was to merge the two inner partition into one.
Then i become frozen boot.
After that I tried reflash with sp Flash Tool, I made a "format" and a reflash, and now the W100 is in boot loop.
When I try to do a factory reset in recovery it says: "Mount /data error"
Could you guys help me please? What the hell can I do now...?
I've succesfully unbricked my THL W100
josepbennet said:
My phone it's bricked, I rooted my w100 yesterday and to celebrate I installed the ifont app from the market, but at the third change didn't reboot any more, I have searched for the rom but seems to be very new... Neither the recovery or something help me out, I was looking for the preloader or somethin ... I'm just desperate.
Some help will be very appreciated!
Click to expand...
Click to collapse
salaksalak said:
I bricked my phone too...
First I installed a partitioning app to my device, my plan was to merge the two inner partition into one.
Then i become frozen boot.
After that I tried reflash with sp Flash Tool, I made a "format" and a reflash, and now the W100 is in boot loop.
When I try to do a factory reset in recovery it says: "Mount /data error"
Could you guys help me please? What the hell can I do now...?
Click to expand...
Click to collapse
Hi everyone,
Few days ago, I've also bricked my THL W100... My mistake was one of the most stupid one: instead of click on Download in SP Flash Tool, I click on Format and accept the operation without reading the warning message. Result: first boot I got the white THL logo in bootloop, and second attempt give me only a black screen with only a faint red light on the front LED.
I've read many threads about unbricking MediaTek based devices, made many manipulations without success. I've even disassemble my device in search of a secret 'test point' dedicated to full memory flash.
Unbricking THL W100 in far more simple than all this. You'll need one of the 'THL W100 original ROM'. I've choosen the May 16th edition (130516) on NeedRom (http://www.needrom.com/phone-roms/thl/thl-w100/). And off course, you'll need SP Flash Tool, also available on NeedRom.
Unpack the Rom files, launch SP Flash Tool, and load Scatter file, and press 'Download' button
The 'deep memory flash mode' require activation of the 'MTK DA USB VCOM' driver. To activate this mode, you'll have to:
1) disconnect the battery
2) keep the Vol+ down and connect the USB cable (without battery)
These are the main operations...
For my problem, I've tried to flash:
- the whole Rom except Preloader... but it fails,
- the whole Rom including Preloader... but it fails too,
The solution came by using first 'Format' function, and select 'Format whole flash' option, before flashing Rom as previously described. But, I used this format function with classic flash connection, e.g.: connecting the THL W100 to the PC via USB cable without the battery, and inserting the battery (and no use of Vol+ button, off course).
Be carreful: before trying this kamikaze procedure, try to unbrick your device by simply flashing the Rom without/with Preloader.
hi
Who have THL W100 firmware upgrade, please send a link to me, thank you
Lindsay02 said:
hi
Who have THL W100 firmware upgrade, please send a link to me, thank you
Click to expand...
Click to collapse
here it is : http://www.needrom.com/mobile/thl-w100-official/
pigot said:
The solution came by using first 'Format' function, and select 'Format whole flash' option, before flashing Rom as previously described. But, I used this format function with classic flash connection, e.g.: connecting the THL W100 to the PC via USB cable without the battery, and inserting the battery (and no use of Vol+ button, off course).
Click to expand...
Click to collapse
Afraid I don't understand...
The format is what you had done to brick it in the first place isn't it ?
So you needed to format again using 'Format whole flash' option ?
Is that correct ?
ch-vox said:
here it is : http://www.needrom.com/mobile/thl-w100-official/
Click to expand...
Click to collapse
Thank you
Lindsay02 said:
Thank you
Click to expand...
Click to collapse
you're welcome
intrax said:
Afraid I don't understand...
The format is what you had done to brick it in the first place isn't it ?
So you needed to format again using 'Format whole flash' option ?
Is that correct ?
Click to expand...
Click to collapse
True: I've bricked my device by using 'Format' with the option 'Format whole flash except Bootloader". At the first reboot, I got a THL white logo bootloop. After second reboot, nothing but a black screen and a faint red light from the front Led. I've tried 'Download' and 'Upgrade' SP Flash Tool functions to reinstall ROM(s) with or without 'Preloader' partition: got lots of sybilin error messages, and correct download.upgrade achievements, but my device remains bricked.
I've also tried 'Format whole flash except Bootloader' function + immediate Rom download, but it fails... until I use 'Format whole flash' function (USB cable connected + battery insertion) and immediately after whole ROM (130529) 'Download' (no battery inserted + Vol+ pushed + USB cable). First boot took about 4 minutes... but everithing works after that.
Need help please
please help me !!! I THINK MY DEVICE IS BRICK I NEED THE OFFICIAL ROM
please help me i BOUGHT THL W300 befor 5 days ago ...i try to update the recovery but the divice is died and black screen it is no work and no start up no charging . now i want for your help
it is new divce but no support here in saudi arabia..
when I conict the computer there is no logo no show any thing gust black screen gust I heard some sound when I plunge with computer . I try to flashing ROM(thl w100) it is show message error 4023 in flashtools.
now I need file to flashing ROM also file for bootloader.or any help to start up agin
iam sorry my english languge is not ok
I can't do it!!
pigot said:
True: I've bricked my device by using 'Format' with the option 'Format whole flash except Bootloader". At the first reboot, I got a THL white logo bootloop. After second reboot, nothing but a black screen and a faint red light from the front Led. I've tried 'Download' and 'Upgrade' SP Flash Tool functions to reinstall ROM(s) with or without 'Preloader' partition: got lots of sybilin error messages, and correct download.upgrade achievements, but my device remains bricked.
I've also tried 'Format whole flash except Bootloader' function + immediate Rom download, but it fails... until I use 'Format whole flash' function (USB cable connected + battery insertion) and immediately after whole ROM (130529) 'Download' (no battery inserted + Vol+ pushed + USB cable). First boot took about 4 minutes... but everithing works after that.
Click to expand...
Click to collapse
Hi everyone!
When I got my w100 I tried to put an other ROM with sp flash tool, flash tool process completed perfectly but when I tried to boot my phone, the pone it started up but the screen only showed white lines. I even heard the sound of the boot.. But screen remained black with white and other colours lines.
I tried to flash it again with diferents many ROMs..W100_130912_backup_131001-214504, W100_130504_ForFlashtoolFromReadBack_130605-170952, ThL.W100.130701.JBV2.HD.EN.COM.8P32_MT6589.
Even though the process got complete, the perfomance of the phone was the same as I said.
As I got tired of flash it once and again, then I followed your advice, so I did a "Format whole flash", I got it, but after I tried the "Download" I always get the same error, after first red bar it's 100% sp flash tool always shows the same message:
BROM ERROR: S_FT_ENABLE_DRAM_FAIL (4032)
[EMI] Enable DRAM Failed!
HINT:
Please check your load matches to your target which is to be downloaded.
Now when I tried to do whole format or download, I got the same error.
I tried by vol+ pushed + cable usb and cable usb conected without battery then I put de battery. But still the same result.
I'm starting to think that can be a motherboard damage or samthing!!
Can anyone help me please!!?
I found the solution!!
I did it by using Windows xp!!! Then the error message disappeared!! And i've got my phone working!!
---------- Post added at 07:38 PM ---------- Previous post was at 07:02 PM ----------
I found the solution!!
I did it by using Windows xp!!! Then the error message disappeared!! And i've got my phone working!!
pigot said:
True: I've bricked my device by using 'Format' with the option 'Format whole flash except Bootloader". At the first reboot, I got a THL white logo bootloop. After second reboot, nothing but a black screen and a faint red light from the front Led. I've tried 'Download' and 'Upgrade' SP Flash Tool functions to reinstall ROM(s) with or without 'Preloader' partition: got lots of sybilin error messages, and correct download.upgrade achievements, but my device remains bricked.
I've also tried 'Format whole flash except Bootloader' function + immediate Rom download, but it fails... until I use 'Format whole flash' function (USB cable connected + battery insertion) and immediately after whole ROM (130529) 'Download' (no battery inserted + Vol+ pushed + USB cable). First boot took about 4 minutes... but everithing works after that.
Click to expand...
Click to collapse
Great! That work for my friend phone after a lot of trying , Thank you.
Sent from my GT-I9000 using Tapatalk
Brom error: S_ft_enable_dram_fail (4032)
Hello,
my THL W100 arrived yesterday and i was immediatelly interested in some custom rom so i began flashing it not knowing properly, what i was doing, so firstly i ended up in boot loop, then completely bricked with device refusing to boot (black screen).
I tried recovering using SP Flash Tool these builds, but nothing worked for me:
thl.w100.130529.jbv2.hd.en.com.8p32_mt65
ThL.W100.130701.JBV2.HD.EN.COM.8P32_MT65
ThL.W100.130802.JBV2_.HD_.EN_.COM_.8P32_MT65892
W100_130504_ForFlashtoolFromReadBack_130605-170952
I also tried using different versions of SP Flash Tool (.119, .139 .150), but all showed error BROM ERROR: S_FT_ENABLE_DRAM_FAIL (4032)
As said here before, tried on Win XP and Win 7 64bit and it showed same error.
So then being despred for several hours I actually dig up a lot on internet and found up some information:
1) There are apparently some hardware revisions, according to beginning of serial code:
BFYSG94W - Rev. 1
BFYSG9410 - Rev. 2
But my phone has CFYSGM4W - maybe its a new Rev. 3?
2) Based on many other mtk6589 phones having the same problem, you should look for firmware released by date of manufacture. It should be written somewhere, but I didn't find any information on device no package, so I decide to look for latest.
3) The phone shows up in device manager as "alcatel RNDIS" under network cards, I had to manually update the driver selecting "Preloader for Flash SP.Flash" .ini file manually from a disk. It may tell that the device may not work or something, but don't worry, reconnecting it shows up as MTK USB Port under COM and LPT ports and it should be fine.
4) I also had to disassemble to device and short LCOLO test pin to ground - here is the original post with image http://forum.xda-developers.com/showthread.php?p=44208574#post44208574 I soldered a single wire of hdd ribbon cable to lcolo, the other side being wrapper around USB cable. I flashed without battery, shorted all the time. The Flash Tool immediatelly discovered the device, when the lcolo pin is shorted, then when progress bar turned from red to violet the MTK USB Port device changed to 'MediaTek Preloader USB VCOM Port' so the preloader was owerwrited and phone successfully flashed back to factory state.
(before you lose your warranty try connecting usb > inserting battery or connecting usb without battery + holding volume up, it does practically the same job)
5) There are lot of stock roms here - http://www.needrom.com/phone-roms/thl/thl-w100/
So finally the version that worked for me was: ThL.W100.130912.JBV2.QHD.EN.COM.V01.8P32-kol
I even managed to get CWM working, (used same scatter, checked only recovery and doble clicked and selected recovery-cwm-6037-w100-130912).
To make it easier for people having the same problem I put up the things that worked for me and uploaded it, includes:
ThL.W100.130912.JBV2.QHD.EN.COM.V01.8P32-kol
SP_Flash_Tool_v3.1316.0.150
recovery-cwm-6037-w100-130912
and drivers for ADB and Preloader for Flash with SP.Flash
http://www.4shared.com/archive/FjP0asvJ/thl_w100_rev3.html
I hope you will find my first post useful, sorry for my bad english
Regards,
Umakarton
I also received a THL W100 with a CFYSGM4W serial today.
I flashed a different stock rom to it and it refused to boot (just showed some black and white lines). Google led me here and your package worked great . I tried a few different roms but the one you provided seems to be the only one to work.
Thanks
Snippo said:
I also received a THL W100 with a CFYSGM4W serial today.
I flashed a different stock rom to it and it refused to boot (just showed some black and white lines). Google led me here and your package worked great . I tried a few different roms but the one you provided seems to be the only one to work.
Thanks
Click to expand...
Click to collapse
I am glad it worked for you too, I don't found any complete info in one place so i decided to write this essay. It feels nice to help other people! :good:
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?
So basically monky, windows crapped on my boot partition trough fastboot, i dont have anymore acces to recovery or fastboot to reflash the boot partition.
I was trying to fix it trough the mighty SP Flash Tool since i have an MT6750(T) board but any tutorials ive looked up so far require an MTK DA USB device connected wich i dont see even if i unplug the batter, hold volume / whatever.
Only Preload and USB show up in devices. I tried to flash when Preload was connected but the only problem is that Preload device disconnects after a very short amount of time : SP Flash Tool doesn't have time to go in the flash state, it just goes to 100% DA wich after it errors due to the Preload diseapearing, and i can't flash while the MTK USB device is on, i don't know what can i do with it, any advice for that MT6750(T) board ?
(the errors generated by the tool were either, Preload file invalid (?) or disconnet battery and retry while holding volume down wich obv didnt work)
Gigaset GS270+
Android 8.1
Hello
I tried to flash a custom rom on my Nord N10 --> [ROM][UNOFFICIAL] LineageOS 18.1 [OnePlus Nord N10/billie] <--
At 47%, the flash stopped. I tried it a several times but always with the same result.
I did a factory reset in twrp, since then all was gone from internal storage.
And now I'm unable to flash ANY rom on the device.
I tried a lot of ways: flashing stock rom with stock recovery, flashing different custom roms in twrp and other recoveries, Msmtool, extracting payload.bin and flash all the images in fastboot (I followed the commands at the bottom of this page), ... but I haven't got the result I wanted.
I even got into "Qualcom crash dump mode". That's when I tried to use the MsmDownloadTool but it wouldn't recognize any COM port.
I can transfer .zip files to the internal storage when using twrp, but flashing always fails (see attached file).
Sideloading in PE or Lineage recovery works, but flashing fails (2nd attached file).
Overview:
Positives:
bootloader is unlocked
fastboot is accessible
fastboot commands are working so I'm able to flash by fastboot command
recovery is accessible and different versions can be flashed
internal storage is accessible and copying files is possible (though, folders like Android, DCIM, downloads, etc... are all gone)
Negatives
Msmtool doesn't recognize the COM ports
some images (like vendor.img) can't be flashed in fastboot when extracted from the rom by using Payload Dumper
error shown in twrp (file attached)
neither can a rom be flashed in PE recovery or Lineage recovery
Anyone able and wanting to help or provide a link to a tutorial? I don't care which rom is installed, I just want to get the phone working again and at this point I fail to see what I'm doing wrong.
Kind regards
Its been a while since I used the N10, but I can at least help with the MSM tool: note that the MSM tool uses what is called EDL mode, which is basically a hardware (ROM) backed loader. If the phone isn't physically damaged, EDL should work no matter what you did to the partitions. It is lower level than the bootloader lock, so that shouldn't matter.
(Disclaimer: each EDL mode phone uses a signed loader, which can restrict what memory is read or written to... so technically, you could brick the phone and not be able to get it back if the loader won't let you write to a particular block. That said, I've never seen OnePlus phones unrecoverable, and if you can get the bootloader and fastboot back, you can then write to anything from FB that the partition table lets you, although that is subject to unlocking the bootloader at that point. It's why I'm probably OnePlus for life unless they do something stupid.)
Anyway, you have to get the phone in EDL mode. Off the top of my head, power it off, hold both volume keys down, then insert the USB cable. You will have a ** SHORT ** time period- like 5 sec - where the USB port will be identified as a Qualcomm 9008 (or whatever) and the MSM tool will see it. Have the tool running, and put your mouse over the "start" button, so you hit it in the window.
To be clear, EDL mode is NOT the same as crashdump mode, and any other mode than EDL will NOT be recognized by the MSM tool as valid.
Hope that helps!
I'll look into it and give it a try. Thanks!
SomeRandomGuy said:
Its been a while since I used the N10, but I can at least help with the MSM tool: note that the MSM tool uses what is called EDL mode, which is basically a hardware (ROM) backed loader. If the phone isn't physically damaged, EDL should work no matter what you did to the partitions. It is lower level than the bootloader lock, so that shouldn't matter.
(Disclaimer: each EDL mode phone uses a signed loader, which can restrict what memory is read or written to... so technically, you could brick the phone and not be able to get it back if the loader won't let you write to a particular block. That said, I've never seen OnePlus phones unrecoverable, and if you can get the bootloader and fastboot back, you can then write to anything from FB that the partition table lets you, although that is subject to unlocking the bootloader at that point. It's why I'm probably OnePlus for life unless they do something stupid.)
Anyway, you have to get the phone in EDL mode. Off the top of my head, power it off, hold both volume keys down, then insert the USB cable. You will have a ** SHORT ** time period- like 5 sec - where the USB port will be identified as a Qualcomm 9008 (or whatever) and the MSM tool will see it. Have the tool running, and put your mouse over the "start" button, so you hit it in the window.
To be clear, EDL mode is NOT the same as crashdump mode, and any other mode than EDL will NOT be recognized by the MSM tool as valid.
Hope that helps!
Click to expand...
Click to collapse
Couldn't get into EDL mode (I tried EVERYTHING). I updated/repaired the Qualcomm drivers, re-flashed another version of twrp and was able to flash this rom in twrp after I copied the rom to the sd card. It worked, the N10 is back alive again.
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.