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.
Related
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!
Hello, I have a bricked Virgin Mobile LG LS665; here's how it happened
The LG LS665 recently got an OTA update. However, my phone was rooted, so I could not apply the update. The patch was failing because some of the system partition files had been modified. I found out that the original versions of the modified files had been backed up by the tool I used to root my phone, and thinking myself clever, I restored the original files, and applied the patch. Of course, this didn't work, and my phone got stuck at the LG logo whenever it tried to boot.
When I tried to boot it into recovery, it would give the error "Secure Boot Error 1006" and reboot to the LG logo. From what I gather, this boot error comes from the bootloader not recognizing the boot image. Dang. Not one to give up, I searched for unbrick solutions for the LG LS665, and found some. Unfortunately, the only methods I could find were for the Boost Mobile version of the phone. Reckless as I am, I decided to try the Boost Mobile unbrick process, but only managed to brick by phone harder. As a new member, I can't post a link to the unbrick process, but it involved flashing a .tot system image with LGFlashTool. I may be wrong, but my research leads me to believe the process failed because the partition tables for the Boost Mobile version and Virgin Mobile version of the phone are different.
Now my phone will not display any boot screen; I can't get it into normal, recovery, or download mode. When plugged into my computer, Windows device manager lists the phone as "Qualcomm HS-USB QDLoader 9008". Googling that device name brings up a few tutorials of how to revive devices in this dire state, but none that seem to work without a correct system image. I believe it is possible to unbrick my poor phone, but I am not knowledgeable enough to figure it out on my own. If anyone with a clue what to do is willing to help me, I would be very grateful.
In summary, what I think I need:
Some sort of system image for the Virgin Mobile version of the LS665. (I think a .tot or .kdz file)
A kind, knowledgeable soul to point me in the right direction
Thank you for hearing my lengthy plea,
Grant Moyer
Grant Moyer said:
Hello, I have a bricked Virgin Mobile LG LS665; here's how it happened
Have you found solution please. Same issue from here
Click to expand...
Click to collapse
Hello,
A friend of friend of mine unlocked bootloader on his G5, then some magical stuff probably happened, because secure boot got stuck on boot verification failrue with probably most common issue, signature length mismatch. We're trying to get it to work now, but we can't seem to find a solution to it. Fastboot doesn't work, because secure boot gets tripped in every bootmode. Does anybody have an idea which pins to short out on motherboard for boarddiag operation or something? I'd really appreciate that.
Download Mode should still work.. even with the secure boot tripped msg.. as long as they didn't mess with the download mode partition on purpose before this all happened.
The unique programmers required for the G5 for BoardDiag to work are not public so forcing your way into 9008 won't get you anywhere.
He isn't able to fire up download mode either. He says that it prints different_hash error there. I'd probably have to take another one of the same model(H850, I believe) and mirror kernel and bootloader from it, but I don't have eMMC programmer, nor physical access to that phone.
[/COLOR]
autoprime said:
Download Mode should still work.. even with the secure boot tripped msg.. as long as they didn't mess with the download mode partition on purpose before this all happened.
The unique programmers required for the G5 for BoardDiag to work are not public so forcing your way into 9008 won't get you anywhere.
Click to expand...
Click to collapse
Keij0 said:
He isn't able to fire up download mode either. He says that it prints different_hash error there. I'd probably have to take another one of the same model(H850, I believe) and mirror kernel and bootloader from it, but I don't have eMMC programmer, nor physical access to that phone.
Click to expand...
Click to collapse
Keij0 said:
He isn't able to fire up download mode either. He says that it prints different_hash error there. I'd probably have to take another one of the same model(H850, I believe) and mirror kernel and bootloader from it, but I don't have eMMC programmer, nor physical access to that phone.
Click to expand...
Click to collapse
bumping old thread, i know. Did we ever establish either board diag files for g5 or any solution to No download mode issue with it reporting Different Hash when attempting to enter it? My phone boots fine but no DL mode......backstory: I have a RS988 that i attempted to repair for a friend after they locked it with frp, i removed the frp, via creating a apparently incorrectly modified firmware via my z3x's firmware maker feature(it copies the partitions available on the device into a new firmware file). it doesn't have rs988 listed as a model available to edit so(like normally works with devices, i used vs986(or whatever verizon's variation was, i know rookie mistake) but I believe i have screwed up because since writing the modified firmware i can get into the OS fine but can not enter DL mode again without the "Different Hash" issue. I believe shortwire plus board diag fix could be resolution but could use some feed back . @autoprime Anything i can do to rewrite those partitions manually with the RS988 variant's original kdz and any type of serial connection/jtag/virtual com ports/tty/AT+/linux computer, lol anything? I'm pretty much equipped for anything except jtag but even that can be arranged lol
Hello everyone! I am in dire need of help.
So I recently decided to acquire a regular Motorola G7 because I had heard its battery is fantastic. This far, I have been loving it.
But silly me decided I wanted to explore OEM boot unlocking to eventually root the device. After successfully completing theses tasks, I installed the TWRP recovery. Sadly, something (must have) went wrong because when I tried to reboot, the phone went into hard brick. Completely unresponsive, holding both power and vol. down button for 2+ minutes did nothing. I basically have exhausted every Internet recommendations thus far and nothing has been fruitful.
I have been able to get the Qualcomm Port 9008 (COM3) to show up in device manager when I hold power and vol. down. Also, the program QPST also recognizes a phone in Sahara download mode (although I have no idea what it means nor what to do with that, if anything).
So here I am, asking for your help. I have read somewhere that a blankflash zip file could allow me to restore my phone but alas, I wasn't able to find any nor would I know what to do with it.
I would greatly appreciate any help.
Regards,
Afireblood.
Edit: I have managed to find a way to potentially salvage my bricked phone, using QIFL tool to flash a stock rom. However, to do so I need some files (which are proper to the Moto G7 - any other would not do). They are:
programmer (firehose?).mbn
rawprogram.xml
patch.xml
If anyone has any clue where I could find that (except everywhere on Google - it hasn't been helpful), I would very much appreciate it!
afireblood said:
Hello everyone! I am in dire need of help.
So I recently decided to acquire a regular Motorola G7 because I had heard its battery is fantastic. This far, I have been loving it.
But silly me decided I wanted to explore OEM boot unlocking to eventually root the device. After successfully completing theses tasks, I installed the TWRP recovery. Sadly, something (must have) went wrong because when I tried to reboot, the phone went into hard brick. Completely unresponsive, holding both power and vol. down button for 2+ minutes did nothing. I basically have exhausted every Internet recommendations thus far and nothing has been fruitful.
I have been able to get the Qualcomm Port 9008 (COM3) to show up in device manager when I hold power and vol. down. Also, the program QPST also recognizes a phone in Sahara download mode (although I have no idea what it means nor what to do with that, if anything).
So here I am, asking for your help. I have read somewhere that a blankflash zip file could allow me to restore my phone but alas, I wasn't able to find any nor would I know what to do with it.
I would greatly appreciate any help.
Regards,
Afireblood.
Edit: I have managed to find a way to potentially salvage my bricked phone, using QIFL tool to flash a stock rom. However, to do so I need some files (which are proper to the Moto G7 - any other would not do). They are:
programmer (firehose?).mbn
rawprogram.xml
patch.xml
If anyone has any clue where I could find that (except everywhere on Google - it hasn't been helpful), I would very much appreciate it!
Click to expand...
Click to collapse
Update: Now in search of the Moto G7 specific blankflash.zip
If anyone knows where I can find that I would really appreciate it!!
I am not familiar with the g7. (I own a G5+). I believe the G7 code name is "river". You can look at https://mirrors.lolinet.com/firmware/moto/river/ and they show a blank flash - but let me say something - a blank flash must be exact for your phone. Its basically the main disk partition with other partitions inside. My phone has 64GB/4GB, and 32GB/3GB-2GB models - so you see a problem. But if all the G7s are the same, then this blank flash should be OK.
Also you can download the phones original firmware at https://mirrors.lolinet.com/firmware/moto/river/official/RETUS/ , if its a US model. If its not, back up 1 directory and you can find it by either carrier or country. You can fastboot the firmware - which I would do before a blankflash,
Hope that helps.
Hi
I just got a third LMX210 today to add to my collection. Lol really im just trying to solve a problem. I bought a ulma to replace cm and i came across a ulm model and decided to just replace my cm today. The problem is that all three of these phone which normally have easily unlockable bootloaders will not boot into fastboot. The fortune 2 will not even boot into recovery. They all will boot into a blank screen with the android robot and will boot into download mode.
The natural solution would be to install an older or even plain stock firmware. But say you dont have a windows 10 or Mac computer. I havent found a way to flash lg firmware using a linux distribution yet.
On the other phones i tried removing the laff partition to force the phone into fastboot by plugging into pc while holding the volume up button. This did nothing but repeat the logo until the button released.
Yes usb debugging was enabled and adb was used to try these procedures. The drones at lg know nothing and ask to send the phones in for repair.
Short of re-installing the stock firmware there has to be way to get past this. And to tell you the truth i dont have a way to flash the stock firmware so i dont even know if that will work.
Ok guys got any ideas?
Update.
Ok spent 4 hours on a windows pc today trying to flash firmware and install qcom drivers thinking the download errors were due to the drivers. Then at the last moments went to Tecknights page and downloaded and installed the lgup dual mode program.
So the bastitches of higher android office decided to screw everyone out of bootloader unlocking. The ARB numbers have recently (like in the past 3 months) been changed to 003. Meaning you cannot flash firmware with an ARB number lower than 003.
But that doesnt stop us completely. Two ideas initially popped into my head. Hex edit the .kdz so that the ARB number matches the phone. Or lol split the .kdz into its seperate partition images then wipe the partitions and use qdl or lgup to repair the now bricked phone. No device data no ARB no problem.
Im hoping the former works over the latter but ill keep you informed.
But really guys thats extreme and i cant see too many folks going through the wipe process to enable fastboot. So we have to find an easier way.
Is there any way to know what partition the ARB protection resides in? If those parts could be wiped im thinking it might fool the flashtool into thinking that there isnt any protection.
one of your devices is MTK isn't it? can't you use SP Flash Tool like for other Mediatek devices? you should be able to flash images to emmc_user with locked bootloader, for example boot, recovery, system, ... all you need is a correct scatter file (which you could create with WwR MTK)
So your saying finish porting my recovery and use sp flash tools to install it. See i have been curious about that procedure and how not having an unlocked bootloader would effect flAshing from recovery. I was thinking brick. But its worth a try if it wont brick and i get full Root with magisk. Ty
Btw when i was porting my recovery i ran into a rather large well too large problem. When i went repack using abdroid image studio which i have used in the past with out problem, it would not shrink the image back down even though i was only trading a few files. How do i fix that
start with readback boot / recovery. then try to unpack, so you will know the scatter is right (at least, for this partitions) or compare files with your already existing backup files
no problems here with unpacking/ repacking with AIK
IDEA:::: ok so for the Qcom boards i have a solution possibly. I know that the older software versions have working fastboot and recovery going and can be boot loader unlocked. That tells me that a fota uodate is screwing things up.
PROBLEM:::: ARB my fortune 2 will not let me install at all anything before ARB3.
ARB_location:::: bootloader
Solution:::: download and extract the stock .kdz for device with working features. Wipe parts bootloader and laf using qpst and reinstall. Solves two problems in one go. Allows fastboot and and bootloader unlock and future re-install of stock firmware
may work but remember your bootloader is locked and you need to by-pass this via testpoint (or at least previously enabled oem unlocking and don't lost these setting) otherwise sahara will fail
well it was an idea. I just did some fact checking and also looked at the files dumped from the .dz dump of the fortune 2 stock rom. PBL or primary bootloader cannot be removed or flashed according to a thread it is a pernanent installation.
But upon more reading i can flash my recovery and boot.img using qfil in qpst along witn every thing else. But i need to know wether qfil reads ARB info and if so where i can find it in the firmware so i dont flash that img but instead pull it from phone as is.
i would really like to know what the twitterpating deal is with these LMX210 phones. ok when i firsr got my fortune 2 i bought it for two reasons the rootability of the device and the fact that tje msm8937 board came pre-installed with otg software by default which in my eyes meant no more freaking computer to use adb.
Well it is all there the drivers the software. but guess what. it doesnt work. i have no idea whats stopping it all from working but even lsusb doesnt bring a twitch or hint of reading any thing over the usb.
does any one know how to fix this
Yo. There is definitely ways to flash on linux using virtual machines, wine etc to run windows apps but you got ahold of a windows box to use. IF it is in EDL mode (Qualcomm mode with a driver saying 9008 in it..) then there is still faith you can revive it. You will need the firmware dumped from someone then youll need to run a program creating XML files for the phones firmware parition files. Youll next need a firehose which is what they call the programmers for EDL that send through the commands and firmware in a low low level that these programs like LGUP just do not do yet (don't know why..... Im waiting for someone to program the LGUP dev version with an EDL mode using emmcdl along with a way to create XML files too. Who knows maybe it will happen if we bring it up enough. The hardest problem youll have is getting a proper emmc programmer for the phone. I can source a lot so if teknight doesnt have something to help with EDL just get ahold of me and ill see what I have and send you some stuff.
Man i have been trying to unbrick the LMX-210 CV1 devices since last year. Tek has nothing but supports the work in hope of finding a solution. I have a ton of fire hoses and saharas all of which have cost me nothing but frustration. I have almost every qpst made and have tried them all with my firehose and saharas. Thr only thing i havent done is pull the mbns off my phones and try them. Trust me system dumps are crap.
The only sign of life i came by was flashing an sd card with the gpt and then flashing each partition manually using ubuntu. In return i got the battery logo but thats it.
Would love to figure it out though
By the way I have been compiling kernels. I call it the jokerfish kernel. Its packed full of drivers and debugging features plus gpu idlers boosters and all those crazy fishy thIngs. Its got governors and wire guard. Otg support. Io schedulars and overclocks. Cpu hotplugging and fast charge.
Now i cant figure out how to get fast charge to work but its set up for msm-otg phy-msm-otg qpnp-smbcharger and smb135x.
All that and not a single panic to reboot in over a week and 1/2 which is how long its been compiled. I used tweaks from the dragonheart kernel source and ported them over and did a lil c++ magic.
It has kcal too but n0 app supports it. All kinds of media and sound codecs as well. You think it would be slow but my compiling and coding skills are as mad as me. Hahahaha.'
But dont Take my word for as the gentle over there on your couch. See that smile? Hes as happy as fish in a pond.
Just remember Duhjoker is in no way responsible for bricked devices so try it at the risk to yourself.
This particular fishy thingy works for msm8917 cv1 devices like aristo 2 and k8+ which have been tested by the madman himself.
If you like you could thank me but the permanent smiles on your faces will be just as loved.
lol so fast_charge is working on the kernel but you have to add a custom tunable to a kernel app to get it going. Just add the path
/sys/class/power_supply/usb/uevent
Then you will get a choice of values to manipulate