think i hard bricked my optimus f6 after an attempt of installing unlocked bootloader. no emergency download mode, no boot of any kind. managed to get "qhsusb_dload drivers installed. do not know what to do???? any help please....
No one with any ideas about this situation ?
i'm stuck there too,i think there is a way with qpst tool but we need necessary .xml,.hex,.mbn files
That's a tough one. It's one of those situations that happens often enough, however, since not many people know how to fix something like this, most people don't even bother and just send it in to LG or write it off as a loss. The EASIEST way would be to find a shop with a RIFF box that can perform a JTAG service on that. But finding a shop that has the tool and knows how to use it (especially for your model) might be tricky depending on where you are. If you are wanting to try it yourself, you might try this thread as a reference point to maybe at least get you pointed in the right direction:
http://forum.cyanogenmod.com/topic/71825-hard-brick-to-hell-and-back-guide-to-recovery/
Obviously it is not for your phone, and the OP specifically says he does not know how to perform this on other phones, but it is the most detailed thread about it I could find. It should at least give the ideas to what kinds of files you need to find to get started. Good luck!
This post was closed and i was told to ask it here. I posted it in the wrong area and im sorry about that.
I really need some serious help and advice. Could anybody who is experienced it this filed please help me, or even put me in the right direction.
I am stuck in the qualcomm download mode with my device as QHSUSB_Dloader9008.
Yes it is a hard brick and 99% of the google searches have just confused me.
So here is the story.
I was developing for the Lg Vista D631, and trying to port a rom from the v10lte tablet due to the exact same architecture. The only main difference was the screen size.
Anyhow i was using fastboot to mess arount with the LG Security Error but nothing worked.
I didnt find out that much. So i just flashed back stock and then restored from cwm.
Well i went back to fastboot to try some more and i typed fastboot erase aboot, all went well. Then as i was in the middle of typing fastboot flash aboot my dang phone battery fell out my phone. And this is what i recieved... It Took it off my cmd prompt screen, i now have a nice crack in the screen, and a wonderful bricked phone....
It read up as Android Net USB, and it also came up as a removable disk with 64mb free on it. so i looked and i looked for something just to flash the aboot partiton back to the phone. But nothing came up. I even tried win32 imager.
I googled jtag and read that there are test points which would i could short to reset the devices bootloader to the wualcomm safe bootloader to flash the emmc chip and partition table back to stock. Which would thus repair the partition and open up recovery and or download mode.
I attempted to trace the circut to find out what point to short' and yea i even tried a few which only reset the phone. So i said screw it and formatted the removable disk....... And bam my pc detected a new device and installed the qhsusb dload9008 driver.
So now im in qpst fail safe download mode, i have it set to com41, and qpst detects it too.
And now th issue and question at hand.. I need the files to flash an msm8296. As the mbn, hex, and what nots are all not working with me. Do
When i try to use eMMC downloader I just kept getting the same response from qpst 4.0.2.
"Download failed could not communicate with flash programmer"
then in software download i keep recieving that the hex file is invalid, and could not detect the hex scrambling method. The file is invalid.
I have the lg d631 and have many unofficial kdz files i compiled. I could use the vs88010b for any other ones needed too. As i found out which ones are compatible through my testing phase.
When thia gets fixed though, the development for this phone will skyrocket, as anything will be possible.
So i am stuck. I messed up. And need to fix my mistake.
Guys, the phone went into brick mode simply while charging. Please help me with links or ideas on how to find / create a debricking .zip or folder to flash this Qualcomm Snapdragon 400 - 8930AB device.
Why would a service get use of my money when I know it is possible to reanimate this small evil by myself? People keep talking on russian forums about using tools like xPRG ... HEX/ MBN files... Miflash for Qualcomm... QPST software.. and stuff like this... but they are very general in explaning things... Help me!
Thanks!
Same problem here please help anyone
Mango Polo said:
Guys, the phone went into brick mode simply while charging. Please help me with links or ideas on how to find / create a debricking .zip or folder to flash this Qualcomm Snapdragon 400 - 8930AB device.
Why would a service get use of my money when I know it is possible to reanimate this small evil by myself? People keep talking on russian forums about using tools like xPRG ... HEX/ MBN files... Miflash for Qualcomm... QPST software.. and stuff like this... but they are very general in explaning things... Help me!
Thanks!
Click to expand...
Click to collapse
Take care
I hope this is not necroposting, but what do you mean for brick? Explain, is it hardware or software? And how is it going now?
L-K said:
I hope this is not necroposting, but what do you mean for brick? Explain, is it hardware or software? And how is it going now?
Click to expand...
Click to collapse
Necroposting at its finest, but i thought i would write here, so the thread creator might find something useful.
Here is my problem, samsung galaxy express 2 aka sm g3815, gone bricked while charging, i had custom recovery installed, although i do not seem to be able to remember the version, and root, flashed with Odin, everything worked perfectly for...almost a year, i guess. One day, my lil hero died. :crying: My computer seems to detect something plugged in, saying that it some QHUSB_DLOAD device. On some research I understood the Qualcomm reverted or switched to some sort of fail-safe state where it requires files to be written back in the device(correct me if im wrong). It`s been in deep coma for a few months now, everyone said "just buy a new phone and save yourself the hassle". Nope, my mind is set on repairing my hero. On other threads i found out it is possible to revive a phone in this state, using a class 10 or above microSD card and writing a debrick image. Problem was, i searched the seas of gold for the darn debrick image, none found. Until a few days ago, one of my workmates has a Galaxy Express 2, and said he can hand it to me so that i can copy what i need from it after the holidays. Both phones run on 4.4.2, his phone is all stock rom, no cwm or twrp, no root no nothing. It is coming in my hands in a few days. Does anyone have the patience to clearly write what must i do to get my hero working again? It`s been sucky here without it, currently stuck with a samsung Star 3 i reflashed myself, but that lil thing ain`t no Android. I have two class 10 microSD cards, one 8 Gb, one 16 Gb,with backup done, and i saw on other threads that i need to use the 8 gb one, since the phone`s internal was 8 gb. Anyway, sorry for the long novel, it`s my style tho, give as much info as you can so the people helping you know what they`re messing with haha feel free to ask for any extra information. If we ever meet, I`ll buy you a beer or two.....dozens
Cheers!
Alright, i have searched for months at this point. I have tried several potential fixes on this site and others. I have an LG Gpad 7.0 for sprint otherwise known as the LG LK430. After weeks of searching, i have obtained bother the TOT and KDZ files for this device. I'm not able to use the board-diag software due to not having the proper AP Chipset files, at least from what I'm able to understand. I have no bootloader or recovery as well as no system, but the device is able to be seen from the Qualcomm chipset. I can't use the LG software to fix it because the software isn't able to find the device, and won't let me select a port. I tried partitioning an sd card like one gentleman said in a post the DD the img files to each partition. I'm so lost and I don't want to give up on this. There has to be a way. Any advice would help. If anyone knows of a way to at least flash the bootloader back to it then that will get me the rest.... Ugh. Sadly I'm in a "please bro" state here.
hi
the other day i tried to dd in a bootloader to add fastboot to my K8+ (2018) LMX210ULMA and wiped my preloader. The device uses an mt6750 chipset and i had made a back up so i have the approriate software to restore it, i even have the scatter file.
The problem is that there is no da_pl.bin file for lg phones to use sp flashtool, i have no download mode and no fastboot.
i have two pc`s one running ubuntu the other windows 7.
i would appreciate any help
any help at all
ok so ive found some versions of sp flash tool that are supposed to get around the authorization stuff and i have an auth file but i keep getting brom errors. the same one in fact. on linux ifs 0x00. ive been looking at and following the tutorials ivs made android rules and all kinds of things but i cant get it to flash. it started to befote i added the stuff in the tutorials. The red line would go acrross the bottom but now i just get the brom errots.
Thumb up for boldness... :good:
Now you have some interesting project there.
Keep us update if you manage to find out any solution.
No idea how to help but Good luck!
https://blog.hovatek.com/so-whats-all-this-talk-about-meditek-secure-boot-and-da-files/
https://ifindhub.com/download-mtk-secure-boot-da-loader-files-mtk-devices.html
ill get there eventually. I have been looking at all the config and ini files and i hate to say it but security might be essier than you think to overcome. just have to erase a few lines here and there and teplace some as needed. idk ty. Dont worry ill keep you guys posted
i really think sometime we over think and see past the easiest solutions. but what do i know im trying to flash an mtk preloader on an lg phone.
im actually trying to unbrick a few phones. two qc `s and the mtk. I kinda bricked one of my lmx210`s on purpose not thinking it would brick. well jokes on me.
Im have a couple questions maybe somebody can help with. In the past couple months on my journey through madness i have tried a few hindred different ways and more flashtools than you could imagine. So far nothing has worked but ive learned alot of theory.
so far though i know that the mtk board is in bootrom mode. We will get back to that as i have an idea....
ok on the qc boards we have the dreaded 9008 mode. I made some progress today. i wanted to see if the LMX210 could boot from SD card instead of the internal. I believe it can but im having trouble with what to do next. p
i used dd to flash the gpt on my sdcard then formatted the partitions to the proper filesystem. when i plugged it in to the usb it lit up but did not boot. But it lit up for the first time since bricking.
But it only lights up with usb plugged in. Add the batrery and it goes dead. It also doesnt show 9008 mode any more.
i went back and changed the boot and recovery images to reflect using the mmcblk system and now windows device manager can see it. But no boot. im wondering first if i might need a special boot loader to boit from sd and two if i might be able to use the same trick to get the mtk running
Some LG firmwares include some files for SPFT, like LGX240ARAT and LGX230HAT.
but do they work with MT6750? In LGX240ARAT there is a dll that mentions MT6755,
but not MT6750. Newer versions probably needed. Or maybe you could hack it. ??...
part of my problem is not knowing what scatter file to use. these phones have thier info all twaktup. the mtk gives several different board/chip types. like we have 6722, 6755, 6750, 6736 and so on. im pretty sure though its a 6750 board with 6755 chipset but do i use the scatter for the board or the chipset.
Ok idea!!
I can pick the phone up as bootrom mode on port in my ubuntu as /dev/ttyACM0.
That means i can write to it. How can i dd the preloader.bin to the right place on there
Duhjoker said:
Ok idea!!
I can pick the phone up as bootrom mode on port in my ubuntu as /dev/ttyACM0.
That means i can write to it. How can i dd the preloader.bin to the right place on there
Click to expand...
Click to collapse
As I don't know much about but have played a bit with these.
https://gitlab.com/zeroepoch/aftv2-tools
https://forum.xda-developers.com/hd...fire-hd-8-2018-downgrade-unlock-root-t3894256
And there is tools like eMMC Pro, etc. that might work too... ?
I think the m250 did answer to some handshake but there was some problems
because I didn't continue testing those py scripts...
I would try what I could read from it first. From those scatter files I guess that
preloader is on its own partition. The other one should start with partition table, pgpt .. ??
CXZa said:
As I don't know much about but have played a bit with these.
https://gitlab.com/zeroepoch/aftv2-tools
https://forum.xda-developers.com/hd...fire-hd-8-2018-downgrade-unlock-root-t3894256
And there is tools like eMMC Pro, etc. that might work too... ?
I think the m250 did answer to some handshake but there was some problems
because I didn't continue testing those py scripts...
I would try what I could read from it first. From those scatter files I guess that
preloader is on its own partition. The other one should start with partition table, pgpt .. ??
Click to expand...
Click to collapse
Hi,
If you can reach bootROM mode by pressing any of the volume keys while you connect the phone (Mediatek Inc. MT6627) you should be able write and read the EMMC with amonet.
The tool needs some modifications in order to make it work to MT6750. You can probably try with the mt6753 version which may work for MT6750:
https://github.com/Dinolek/amonet
For reference, use this commit:
https://github.com/R0rt1z2/amonet/commit/6b57d0a99f42739d3b3b2ce962b32ecb8fefd950
Contains all the stuff that needs to be edited in order to make it work for that phone
Regards!
Thank you i can give it a try. Its already in bootrom mode though and accepts the handshake. The problem is that the py command that flashes the preloader and stuff on it also wants to flash other stuff as well that i dont have or does not work with the board.
The py command needs to be modified to only flash the preloader, lk.bin, laf and twrp. If those items only could be flashed i could bring the rest of the device up using lgup
I have tried to modify the commands myself to include just those items but it errors. I dont know enough about the python language to be able to do it on my own.
Duhjoker said:
Thank you i can give it a try. Its already in bootrom mode though and accepts the handshake. The problem is that the py command that flashes the preloader and stuff on it also wants to flash other stuff as well that i dont have or does not work with the board.
The py command needs to be modified to only flash the preloader, lk.bin, laf and twrp. If those items only could be flashed i could bring the rest of the device up using lgup
I have tried to modify the commands myself to include just those items but it errors. I dont know enough about the python language to be able to do it on my own.
Click to expand...
Click to collapse
PM me if you need help editing the python script
Regards.
I really appreciate your offer for help. I was looking at the reference for porting and now that i can see the things that would need changing why not go ahead and unlock the bootloader while we are at it. We could save a ton of devices and at the same time give them th3 extra value of being able to twrp and root them.
I have been looking for some way to unLock the bootloader on these phones for days and though it will be some work being able to reflash the preloader AND unlock the bootloader which was my main intent when i bricked it would be worth the extra effort.
Rortiz2 said:
PM me if you need help editing the python script
Regards.
Click to expand...
Click to collapse
I couldnt post the main.py script in the pm but i can attach it here. Thank you so much.
Here is the raw preloader extracted using salt on my pc.
Ok so i went through your source code for the meizu m2 amonet to match it with source code for the mt6750 and i only had to change a couple things. Its pretty much identical to the commit you pointed me too.
As far as i can see your amonet should work just fine with the sp200/lm-x210ulma boards. I did add my .img files to the bin folder though.
Any way i keep getting errors.
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 501, in read
'device reports readiness to read but returned no data '
serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
During handling of the above exception, another exception occurred:
Rortiz2 said:
Hi,
Contains all the stuff that needs to be edited in order to make it work for that phone
Regards!
Click to expand...
Click to collapse
Hi,
Didn't continue experiments but now also @Duhjoker might be interested about this last new development...
[EXPLOIT] [BOOTLOADER] Mediatek based LG K10 2017 M250 bootloader secure boot bypass. by @OficerX
https://forum.xda-developers.com/lg-k10/how-to/exploit-mediatek-based-lg-k10-2017-m250-t4183545
MT6755 and MT6750 are essentially the same, MT6750 is cheaper and slower version of MT6755, these are compatible, you can use tools for 6755 on 6750.
Here (https://github.com/arturkow2000/lgk10exploit) you have tools that can help you flash preloader (write_boot0.py), these should work on your device.
Open config.py set BR_DEV_PATH to /dev/ttyACM0
then write: python write_boot0.py --brom path_to_your_preloader_bin
This is slow process, may take few minutes (you will see progress while flashing).