Hi!
I recently unlocked my bootloader and installed LineageOS on my LG G7, successfully.
I wanted to go back to stock, and I followed this guide:
https://forum.xda-developers.com/lg-g7-thinq/how-to/guide-how-to-flash-stock-firmware-lock-t3820888
After flashing with LGUP, the phone booted to stock firmware with no problems, so I executed:
adb reboot bootloader
fastboot oem lock
At this point, the phone rebooted and it was bricked, since now it shows:
"Your device has failed a routine safety check and will not boot."
I found this thread of a guy with the same problem:
https://forum.xda-developers.com/lg-g7-thinq/help/how-recover-phone-red-warning-boot-t3931975
Someone at the end of the thread claims to have solved it:
I successfully recovered from this by getting the v35 engeneering bootloader flashed dump someones frp partition with oem unlock toggled flash it to my phone with fastboot reboot to bootloader, do fastboot flashing unlock, use lgup to refurbish and you're unlocked and good to go again
Click to expand...
Click to collapse
One of the problems is indeed that I cannot unlock the bootloader again because I can't boot and check oem unlock in developer options (fastboot gives an explicit error).
The point is: could anyone describe this procedure a little better and tell me how to get this dump with oem unlock toggled and how to flash it with fastboot?
Other guys already asked on that thread, but he didn't answer...
Thank you in advance!
i have a problem after crossflash my g710pm and i have no 3g or 4g internet enabled, i change the apn and i reset all and flashed a different firmware and no lucky.
Try geting it to boot to download mode and flash kdz with lgup. It might be hard to try to time the reboot with volume and USB cable, I manage after maby 15 attempts
maydayind said:
Try geting it to boot to download mode and flash kdz with lgup. It might be hard to try to time the reboot with volume and USB cable, I manage after maby 15 attempts
Click to expand...
Click to collapse
I'm already able to boot both into download mode and fastboot mode, I tried flashing various kdz with LGUP... I think I'm going to take the phone to customer service.
@Emmeggi95 I can help! Send me a P.M.
I did the same thing a few weeks ago. I had a guy on here fix it for me with his octoplus, and then i ended up buying an octoplus medusa pro for myself for any future mistakes i make hahaha
The only way to fix this is with the octoplus jtag and unlocking the bootloader again through 9008 mode.
^^^sirbow2 is right. On my phone, I had only locked bootloader fastboot available, (It would boot to download mode for about half a second, then revert to the useless fastboot) and would not boot to system. I had to disassemble it (use heat gun and warm up back cover then carefully pull it off). Then remove the wireless charging coil. Then disconnect battery connector from the mainboard Then with tweezers touch the two test points and plug usb cable in while holding the tweezers to the test points, this caused the 9008 mode driver to install into the ports section of device manager. At that point, I was able to install the ULM11G ROM and go through the steps in loonycbg2's tutorial to bootloader unlock again. I installed the KDZ with octoplus pro, battery still disconnected, in emergency dl mode.
Hopefully, you wont have to go through all that, that's the most work anyone would have to do to unbrick one of these.
sirbow2 said:
I did the same thing a few weeks ago. I had a guy on here fix it for me with his octoplus, and then i ended up buying an octoplus medusa pro for myself for any future mistakes i make hahaha
The only way to fix this is with the octoplus jtag and unlocking the bootloader again through 9008 mode.
Click to expand...
Click to collapse
way2aware said:
^^^sirbow2 is right. On my phone, I had only locked bootloader fastboot available, (It would boot to download mode for about half a second, then revert to the useless fastboot) and would not boot to system. I had to disassemble it (use heat gun and warm up back cover then carefully pull it off). Then remove the wireless charging coil. Then disconnect battery connector from the mainboard Then with tweezers touch the two test points and plug usb cable in while holding the tweezers to the test points, this caused the 9008 mode driver to install into the ports section of device manager. At that point, I was able to install the ULM11G ROM and go through the steps in loonycbg2's tutorial to bootloader unlock again. I installed the KDZ with octoplus pro, battery still disconnected, in emergency dl mode.
Hopefully, you wont have to go through all that, that's the most work anyone would have to do to unbrick one of these.
Click to expand...
Click to collapse
Would love if yall would attempt to find the firehose used for the lg g7 thinq..
This would fully kill out the need for those boxes
loonycgb2 said:
Would love if yall would attempt to find the firehose used for the lg g7 thinq..
This would fully kill out the need for those boxes
Click to expand...
Click to collapse
Isn't that an internal LG thing? It's nearly impossible to obtain besides a leak, right?
way2aware said:
^^^sirbow2 is right. On my phone, I had only locked bootloader fastboot available, (It would boot to download mode for about half a second, then revert to the useless fastboot) and would not boot to system. I had to disassemble it (use heat gun and warm up back cover then carefully pull it off). Then remove the wireless charging coil. Then disconnect battery connector from the mainboard Then with tweezers touch the two test points and plug usb cable in while holding the tweezers to the test points, this caused the 9008 mode driver to install into the ports section of device manager. At that point, I was able to install the ULM11G ROM and go through the steps in loonycbg2's tutorial to bootloader unlock again. I installed the KDZ with octoplus pro, battery still disconnected, in emergency dl mode.
Hopefully, you wont have to go through all that, that's the most work anyone would have to do to unbrick one of these.
Click to expand...
Click to collapse
You dont have to disassemble the phone to get into 9008 mode. Hold power and vol down while quickly mashing vol up until you hear the device connect or see it in device manager. The screen stays black so, if you see the logo, you missed it.
sirbow2 said:
Isn't that an internal LG thing? It's nearly impossible to obtain besides a leak, right?
Click to expand...
Click to collapse
Firehose is a qualcomm file thats usually signed by the brand(oem).
Yes most of the time it either leaks or someone privately buys it from a dev of the oem for a good amount of money.
sirbow2 said:
Isn't that an internal LG thing? It's nearly impossible to obtain besides a leak, right?
You dont have to disassemble the phone to get into 9008 mode. Hold power and vol down while quickly mashing vol up until you hear the device connect or see it in device manager. The screen stays black so, if you see the logo, you missed it.
Click to expand...
Click to collapse
My phone was not capable of it, or I was incapable of it. Believe me I tried about 50 times, one after another.
way2aware said:
My phone was not capable of it, or I was incapable of it. Believe me I tried about 50 times, one after another.
Click to expand...
Click to collapse
ooohf, sorry. Yeah it is a pain. The time frame has to be a very small fraction of a second right after it shuts off and just starts to boot. Im probably hitting 4 or 5 presses a second could definitely be model dependent as well.
hellp
loonycgb2 said:
Would love if yall would attempt to find the firehose used for the lg g7 thinq..
This would fully kill out the need for those boxes
Click to expand...
Click to collapse
me puedes decir cual caja compraste
Related
I have been trying to get this thing upgraded to 5.0 for a day and half now, and i just flashed it for like the 10th time with lg flash tool to try to take it to stock. The rom i flashed that bricked the device I found in this thead: http://forum.xda-developers.com/showthread.php?t=2698267
All of a sudden it won't turn on, won't respond to adb or enter recovery with the volume down + power combo.
All i can see in device manager is qhsusb with an exclamation point. I struggled to update this and once i finally did, the device still isn't recognized by the computer in any lg programs or by adb and wont turn on What can/should i do at this point??
Did you maybe exhaust the battery?
ASW1 said:
Did you maybe exhaust the battery?
Click to expand...
Click to collapse
I did not, it was 70% when it died, and i left it plugged in all night. I'm really at a loss here
ASW1 said:
Did you maybe exhaust the battery?
Click to expand...
Click to collapse
I managed to find out that the phone is in something called bulk mode and even found a tool that gets lg phones out of bulk mode. The program located in this thread here: http://forum.xda-developers.com/lg-g...s-usb-t2933830.
It has my chipset in it(The APQ8064) and can connect with the phone. It passes the first two tests (AP, and EMMC) and fails the SDRAM test. If i can figure how to fix the last test and make it succeed, the tablet won't be bricked anymore. Any ideas?
Hi, today i installed android 6.0 on my g3 d855 then rooted it and i tried to flash recovery with AutoRec from google play, but unfortunately it was only for 5.0 so i rebooted phone and it.. just didn't wake up. Now my phone is showing lg logo sometimes. I can't get into download mode and my pc can't even see my g3. When i plug my phone with battery in it pc doesn't see phone but when i take out the baterry in devices manager i see " unknown usb device (device descriptor request failed) " . What the heck am i supposed to do? Searching for the solution for 8hrs and still nothing.
HELP ME PLEASE...
PS. sorry for my bad english
http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
Try entering download mode(it probably wont show anything on screen) and flash kdz or tot
TheMadScientist420 said:
http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
Click to expand...
Click to collapse
i did it but i am stuck on board diag thing. when i connect cable to pc and click START i get "device was not found in dload trying flash programmer"
Does it show up in device manager as qusb bulk mode qloader 9008 or any thing
TheMadScientist420 said:
Does it show up in device manager as qusb bulk mode qloader 9008 or any thing
Click to expand...
Click to collapse
ok i somehow made it, flashed all imgs in board diag but my phone still cant get into download mode, phone should reboot but it doesnt
EDIT: I made it. I've been doing so many mistakes. admin can now close the thread. thanks @TheMadScientist420 !
dombro22 said:
ok i somehow made it, flashed all imgs in board diag but my phone still cant get into download mode, phone should reboot but it doesnt
EDIT: I made it. I've been doing so many mistakes. admin can now close the thread. thanks @TheMadScientist420 !
Click to expand...
Click to collapse
Help. I have the same problem.
Gollow the guide. Or are u stuck in steps
Did same thing lal, funk me, im idiot, but, mine is not showing lg screen never, can you tell me exactly what you did?
Im not good at english, can someone explain me what ´´ short the pins ´´ means?
Di4N said:
Did same thing lal, funk me, im idiot, but, mine is not showing lg screen never, can you tell me exactly what you did?
Im not good at english, can someone explain me what ´´ short the pins ´´ means?
Click to expand...
Click to collapse
take a small metal wire, and touch with him in the 2 red dots at the same time (connect between them using something made of metal)
omer323 said:
take a small metal wire, and touch with him in the 2 red dots at the same time (connect between them using something made of metal)
Click to expand...
Click to collapse
Which dots you mean? these?
imgur.com/qwMjdtX.png (with blue)
There are any pins at GND that i need to connect with or is just an pin? ( I did not opened the phone for now, im considering to send it to warranty, since phone have 1 year and 9 months of warranty... i mean, i bought it in november, you think they will repair it? Or will send it back as it is? if i open it i lose the warranty so..
And one more thing, where can i get the tot of marshmallow? Or which one you used? In the main post it says ´´ The tot file of the rom that you were running. (not older not newer same version) ´´
Di4N said:
Which dots you mean? these?
imgur.com/qwMjdtX.png (with blue)
There are any pins at GND that i need to connect with or is just an pin? ( I did not opened the phone for now, im considering to send it to warranty, since phone have 1 year and 9 months of warranty... i mean, i bought it in november, you think they will repair it? Or will send it back as it is? if i open it i lose the warranty so..
And one more thing, where can i get the tot of marshmallow? Or which one you used? In the main post it says ´´ The tot file of the rom that you were running. (not older not newer same version) ´´
Click to expand...
Click to collapse
a. yes, this exact blue points
b. just those 2 pins! connect between them, and while they are connected, connect the USB. (you'll probably need a 2nd person help to that, unless you are very skilled with your hands)
c. i don't think any repair store will get to that level, but i don't know the level of support at your country... also, the process is pretty simple, took me about 2 hours of work to get my phone from really hard brick to fully functional rooted CM device
d. i don't know about MM tots... i would suggest using this guide: http://open-freax.fr/guide-unbrick-your-lg-g3/ it worked for me and many others for sure! it provides you all the files you need. just make sure you have efs backup or at least know your IMEI number (which suppose to be on a sticker under your battery)
Also try another cable, 2 months ago I tried it, was sure I did everything correct but nothing...changed cable and boom
Poslano sa mog LG-H815 koristeći Tapatalk
omer323 said:
a. yes, this exact blue points
b. just those 2 pins! connect between them, and while they are connected, connect the USB. (you'll probably need a 2nd person help to that, unless you are very skilled with your hands)
c. i don't think any repair store will get to that level, but i don't know the level of support at your country... also, the process is pretty simple, took me about 2 hours of work to get my phone from really hard brick to fully functional rooted CM device
d. i don't know about MM tots... i would suggest using this guide: http://open-freax.fr/guide-unbrick-your-lg-g3/ it worked for me and many others for sure! it provides you all the files you need. just make sure you have efs backup or at least know your IMEI number (which suppose to be on a sticker under your battery)
Click to expand...
Click to collapse
I have the IMEI on the phone box, i don t have any EFS backup, but i don´t think i can do it.
Wait, found something in my SDCard, i remember i did it time ago, this is the backup?
imgur.com/dgR1BBq
Di4N said:
I have the IMEI on the phone box, i don t have any EFS backup, but i don´t think i can do it.
Wait, found something in my SDCard, i remember i did it time ago, this is the backup?
imgur.com/dgR1BBq
Click to expand...
Click to collapse
yep. this suppose to be the backup i was talking about!
but if you have your IMEI number so everything is good anyway,
you can go ahead with this guide: http://open-freax.fr/guide-unbrick-your-lg-g3/
i'm sure you can do it, just read it carefully before you begin and do exactly as it sais
I actually grounded at a common ground point the main pin is the upper pin if im not mistaken but i did ground to the frame makes it a hell of a lot easier and i used anlong piece of small gauge speaker wire frayed back with about 4 or 5 strands of copper and if i. Not mistaken u must use firmware tot that u were on before brick
I´ve soldered an "connector" to fix a side at ground and the other side a needle to exactly point the pin. "Connector"
And here´s the pin which must be pinned: Here is the Pin
And if you are opening your G3, just a few screws more and you can fix your temparatures: Tutorial with Video
I also reccomend the thermal mod i record at least 10 to 15 degree cooler temps your rite there any ways
Hi there, I'm in a similar situation: I shorted that pin with GND and tried to flash through BoardDiag (I followed this guide). That's a problem. Before I had this issue, I had a fully working stock KitKat (I flashed the tot with LG Flash Tool) but I made some mistakes and tried to wipe through TWRP and to install other ROM (here's my thread). My phone died. I just think that the problem is with the TOT I am trying to flash with BoardDiag.
My D855 is currently with black screen and no led blinking (only QDLoader 9008 mode).
Any help? Thanks and happy New Year.
Try my guide here http://forum.xda-developers.com/lg-g3/general/guide-boot-recovery-download-mode-t3273824
Hi guys!
I tried to put the android 10 korean beta on my LG G7 ThinQ g710TM T-Mobile, and now it doesn't turn on, the laptop recognizes it as QUALCOMM 9008 MODE I just need to know if its trash already or there's a way that can unbrick the phone (really stupid I know)
Thank you in advance!
If the phone wasn't a T-Mobile:
May be able to flash v35.eng img onto the phone's abl_a partition (make sure this is backed up), then use fastboot commands to copy over the laf_a/_b files of the stock img. Then use download mode to revert back to Android 8/oreo.
May need to use, fastboot boot laf.img, to get onto download mode, as suggested here.
It was a t mobile damn never go for a t mobile again REALLY
paxar331 said:
If the phone wasn't a T-Mobile:
May be able to flash v35.eng img onto the phone's abl_a partition (make sure this is backed up), then use fastboot commands to copy over the laf_a/_b files of the stock img. Then use download mode to revert back to Android 8/oreo.
May need to use, fastboot boot laf.img, to get onto download mode, as suggested here.
Click to expand...
Click to collapse
It was a t mobile damn never go for a t mobile again REALLY
Pocketjam347 said:
It was a t mobile damn never go for a t mobile again REALLY
Click to expand...
Click to collapse
You can try my method to fix it?
https://forum.xda-developers.com/lg...to-recover-hardbrick-9008-mode-boxes-t4052841
I
I don't understand one part
Awesomeslayerg said:
You can try my method to fix it?
https://forum.xda-developers.com/lg...to-recover-hardbrick-9008-mode-boxes-t4052841
I
Click to expand...
Click to collapse
I tried this method 2 days ago but for some reason when I try STEP 7: It says "Extracting kdz to ..." so I tried to wait a WHILE but after 4 hours of wait nothing happened so I was unable to do the next steps
Does it matter if the Phyton says that it was the end of its life?
Thank you so much for your post tho I believe you helped other people
Don't throw it away, I think there's a fix with QFIL.
I'm having a similar problem, but in my case I managed to accidentally erase laf_b from QFIL and this has corrupted my GPT. Now the QFIL partitioner can't see my partitions. Can you help? I may need a flat pack or something? I'm stuck in 9008 mode. The bootloader was unlocked but I couldn't get into fastboot to install TWRP and Lineage OS, so I ended up trying to erase laf_a and laf_b like it says to do in the V40 Qfil guide. Big mistake. Qfil and windows both recognize it as a 9008 device on Com3, but can't access the partitions.
I got the phone from a friend and i'm in the same position. The method from Awesomeslayerg just gives me sahara error
THE KHAMELEON said:
I got the phone from a friend and i'm in the same position. The method from Awesomeslayerg just gives me sahara error
Click to expand...
Click to collapse
See the FAQ in that guide.
Restart edl when connected to qfil or try different USB port or different PC.
lefttobleed said:
See the FAQ in that guide.
Restart edl when connected to qfil or try different USB port or different PC.
Click to expand...
Click to collapse
I don't have another PC to try it on. I been trying other ports and nothing. As I use my tweezers to put the phone in EDL I press download and still the error.
I don't know if this phone is T-Mobile or not. The IMEI shows T-Mobile but inside the phone shows numbers for Verizon
THE KHAMELEON said:
I don't have another PC to try it on. I been trying other ports and nothing. As I use my tweezers to put the phone in EDL I press download and still the error.
I don't know if this phone is T-Mobile or not. The IMEI shows T-Mobile but inside the phone shows numbers for Verizon
Click to expand...
Click to collapse
Not sure what's wrong with your phone...
Once I got out of this error by quickly pressing download when phone enters edl. Need to be fast.
Try that.
lefttobleed said:
Not sure what's wrong with your phone...
Once I got out of this error by quickly pressing download when phone enters edl. Need to be fast.
Try that.
Click to expand...
Click to collapse
To be honest I think it could be me just having the files in the wrong place or something else I'm doing wrong. All I get is Sahara error
Pocketjam347 said:
Hi guys!
I tried to put the android 10 korean beta on my LG G7 ThinQ g710TM T-Mobile, and now it doesn't turn on, the laptop recognizes it as QUALCOMM 9008 MODE I just need to know if its trash already or there's a way that can unbrick the phone (really stupid I know)
Thank you in advance!
Click to expand...
Click to collapse
Same problem with my phone.
I also try these things.
If you solved that problem then please share with me.
So, I soft bricked my TMO OP9P. I can still access Fastboot but can't access anything else. After leaving fastboot, when the phone is rebooting, I just get a black screen.
On plugging it in, It shows up in ADB as unauthorized, and with no prompts to authorize, I can't get any further.
Any ideas?
I did that to an HTC U11 once - Never got it recovered, had to toss it...
Never dared relock a bootloader since...
I had the same thing happen to me.
The only thing that worked for me is to boot recovery and wipe system. Good luck
Jhoopes517 said:
So, I soft bricked my TMO OP9P. I can still access Fastboot but can't access anything else. After leaving fastboot, when the phone is rebooting, I just get a black screen.
On plugging it in, It shows up in ADB as unauthorized, and with no prompts to authorize, I can't get any further.
Any ideas?
Click to expand...
Click to collapse
i have the same problem let me know if you figure out a way around this !
For all of you having this issue, simply use the msm for your respective device by unplugging your phone, select power off, enter edl mode with cable plugged in and run the tool. I know another solution, but please PM me if this one doesn't work.
I had this issue as well, but you better not have messed with the sensitive partitions without a backup, otherwise there's no way to repair it.
razercortex said:
For all of you having this issue, simply use the msm for your respective device by unplugging your phone, select power off, enter edl mode with cable plugged in and run the tool. I know another solution, but please PM me if this one doesn't work.
Click to expand...
Click to collapse
i cannot figure out how to run the msm tool properly it always throws an error message
KidSudo6969 said:
i cannot figure out how to run the msm tool properly it always throws an error message
Click to expand...
Click to collapse
what is the error message? Maybe you dont have the correct one.
Jhoopes517 said:
So, I soft bricked my TMO OP9P. I can still access Fastboot but can't access anything else. After leaving fastboot, when the phone is rebooting, I just get a black screen.
On plugging it in, It shows up in ADB as unauthorized, and with no prompts to authorize, I can't get any further.
Any ideas?
Click to expand...
Click to collapse
Here is the msm tool
This was fixed via MSM. But I had another issue come up where MSM doesn't work.
Jhoopes517 said:
This was fixed via MSM. But I had another issue come up where MSM doesn't work.
Click to expand...
Click to collapse
What do you mean doesnt work? What did it do?
its not responding at all. no boot loop, no logo, no nothing. just a blackscreen no matter how long i charge it or hold the buttons down.
Aleena1217 said:
its not responding at all. no boot loop, no logo, no nothing. just a blackscreen no matter how long i charge it or hold the buttons down.
Click to expand...
Click to collapse
Did you try booting your phone into EDL mode? Hold down both the volume buttons, and while holding them down, plug in the USB cable (Connect with the PC). If you're on Windows, check the device manager in the control panel, and check if the PC recognized the phone (you might need to install the drivers too).
ekin_strops said:
Did you try booting your phone into EDL mode? Hold down both the volume buttons, and while holding them down, plug in the USB cable (Connect with the PC). If you're on Windows, check the device manager in the control panel, and check if the PC recognized the phone (you might need to install the drivers too).
Click to expand...
Click to collapse
after installing driver it recognized it in EDL mode. Im also JUST seeing that this is for the 9 and not the 9 pro. im guessing thats the issue? ii cant believe i missed that
Aleena1217 said:
after installing driver it recognized it in EDL mode. Im also JUST seeing that this is for the 9 and not the 9 pro. im guessing thats the issue? ii cant believe i missed that
Click to expand...
Click to collapse
Yes, it's for the Pro, but the procedure is the same. A good thing is that EDL works. Now just grab the MSM Tool for your model and flash it.
ekin_strops said:
Yes, it's for the Pro, but the procedure is the same. A good thing is that EDL works. Now just grab the MSM Tool for your model and flash it.
Click to expand...
Click to collapse
thank you so much. msm is downloading now. while I have you, do you have a link for the 9 pro conversion files? id really like to get that xpan update finally...
ekin_strops said:
Did you try booting your phone into EDL mode? Hold down both the volume buttons, and while holding them down, plug in the USB cable (Connect with the PC). If you're on Windows, check the device manager in the control panel, and check if the PC recognized the phone (you might need to install the drivers too).
Click to expand...
Click to collapse
im sorry i just realized i jumped in the middle of a different thread. This happened while trying to flash tmobile oneplus 9 pro to global firmware and after trying to enter recovery mode. Im guessing it happened because the files are for one plus 9, so im looking for the files for a 9 pro conversion but only am finding msm tool downloads for conversion instead of flashbin files.
Aleena1217 said:
im sorry i just realized i jumped in the middle of a different thread. This happened while trying to flash tmobile oneplus 9 pro to global firmware and after trying to enter recovery mode. Im guessing it happened because the files are for one plus 9, so im looking for the files for a 9 pro conversion but only am finding msm tool downloads for conversion instead of flashbin files.
Click to expand...
Click to collapse
Before I jump to conclusions, could you explain exactly which model you have and what is your goal?
ekin_strops said:
Before I jump to conclusions, could you explain exactly which model you have and what is your goal?
Click to expand...
Click to collapse
i have the le 2127 from tmobile because i didnt know any better. i dont want to root or do anything crazy. I just want to be able to flash to global or eu firmware so i can upgrade as oneplus releases the updates and not be a year behind on tmobiles schedule. I have the sim and bootloader unlocked successfully. I started to flash to the one plus 9 firmware because i somehow missed that it did not say pro. So now my phone in unresponsive except for QDL 9008 mode. MSM tool recognizes it and begins to update it but then gets a param preload "device not image match" message in red and stops. So once i figure out how to get past that and get this set to factory, i want to properly flash it to global or eu, whichever is available, and upgrade it to the latest version.
Aleena1217 said:
i have the le 2127 from tmobile because i didnt know any better. i dont want to root or do anything crazy. I just want to be able to flash to global or eu firmware so i can upgrade as oneplus releases the updates and not be a year behind on tmobiles schedule. I have the sim and bootloader unlocked successfully. I started to flash to the one plus 9 firmware because i somehow missed that it did not say pro. So now my phone in unresponsive except for QDL 9008 mode. MSM tool recognizes it and begins to update it but then gets a param preload "device not image match" message in red and stops. So once i figure out how to get past that and get this set to factory, i want to properly flash it to global or eu, whichever is available, and upgrade it to the latest version.
Click to expand...
Click to collapse
Are you getting the mismatch on the global/eu MSM or are you trying to flash back to stock T-Mobile? You're getting a mismatch because you're most likely using the wrong version of a firmware (msm).
Hello peeps.
My Poco F3 got hard bricked after update froze (was doing clean install of stable EU rom). Phone won't boot into any mode, and won't appear on pc. I've tried sorting the Test Pins 50 different ways and it still doesn't get picked up by the pc. Qualcomm Drivers are installed. Device is connected with working data transfer USB cable. It definitely is getting charge cause Battery and CPU are hotter than the rest of the phone. I'm at complete loss, I have no idea what I'm doing wrong or if I screwed up my phone that bad that EDL also doesn't work. Thanks for anyhelp!
1. Disconnect the battery
2. Make USB-Cable ready for Insertion
3. While shorting the 2 Test-pins, connect the USB-Cable
This is how I had to do it. ^^ This can be difficult and may require multiple trials, but this should work!
Windows should make the "Hardware connected"-Sound directly after connecting the USB-Cable, and show "Qualcomm 9008" in Device Manager.
If not, you need to repeat it: disconnect USB, short the 2 Test-pins and connect USB again. All while leaving battery unplugged.
Note: EDL Mode can't be bricked. This read-only Mode resides inside the Qualcomm SOC. There would have to be physical (hardware) damage for this to not function.
If you need more assistance or so, I can give you my Discord. Though you already seem quite far. Good luck dud.
cyanGalaxy said:
1. Disconnect the battery
2. Make USB-Cable ready for Insertion
3. While shorting the 2 Test-pins, connect the USB-Cable
This is how I had to do it. ^^ This can be difficult and may require multiple trials, but this should work!
Windows should make the "Hardware connected"-Sound directly after connecting the USB-Cable, and show "Qualcomm 9008" in Device Manager.
If not, you need to repeat it: disconnect USB, short the 2 Test-pins and connect USB again. All while leaving battery unplugged.
Note: EDL Mode can't be bricked. This read-only Mode resides inside the Qualcomm SOC. There would have to be physical (hardware) damage for this to not function.
If you need more assistance or so, I can give you my Discord. Though you already seem quite far. Good luck dud.
Click to expand...
Click to collapse
I'd love it if you added me on discord. Please do give me your name
sumurtugu said:
I'd love it if you added me on discord. Please do give me your name
Click to expand...
Click to collapse
cyanGalaxy#3161
Hello , Can someone help me please, edl mode ok but nothing more on my Poco F3....
gregdeberg33 said:
Hello , Can someone help me please, edl mode ok but nothing more on my Poco F3....
Click to expand...
Click to collapse
I am assuming the phone screen does not light up at all, no fastboot or recovery mode.
This would mean the phone's hard bricked. It will require EDL flashing which can be done by someone with an authorised Xiaomi account.
user0u said:
I am assuming the phone screen does not light up at all, no fastboot or recovery mode.
This would mean the phone's hard bricked. It will require EDL flashing which can be done by someone with an authorised Xiaomi account.
Click to expand...
Click to collapse
Hello Indeed and it has been done just to relock the bootloader, i have to use miflash with the same rom used and choose flash all with lock ?
gregdeberg33 said:
Hello Indeed and it has been done just to relock the bootloader, i have to use miflash with the same rom used and choose flash all with lock ?
Click to expand...
Click to collapse
Yes. Just to be safe I would flash the rom with "clean all" instead of "clean all and lock" if I were you. Then after booting up the phone you can later lock the bootloader safely using "fastboot oem lock" in adb.
^
user0u said:
Yes. Just to be safe I would flash the rom with "clean all" instead of "clean all and lock" if I were you. Then after booting up the phone you can later lock the bootloader safely using "fastboot oem lock" in adb.
Click to expand...
Click to collapse
Ok thanks but why ? Fastboot oem lock is better ?
gregdeberg33 said:
Ok thanks but why ? Fastboot oem lock is better ?
Click to expand...
Click to collapse
In case of "clean all and lock" if something goes wrong during flashing, the bootloader will be locked and you will not be able to fix the phone. So it is safer to flash the rom first without locking the bootloader and then lock it after booting up.
user0u said:
In case of "clean all and lock" if something goes wrong during flashing, the bootloader will be locked and you will not be able to fix the phone. So it is safer to flash the rom first without locking the bootloader and then lock it after booting up.
Click to expand...
Click to collapse
It will not.
If the Flash aborts, it won't even get to the stage of locking the bootloader.
gregdeberg33 said:
Ok thanks but why ? Fastboot oem lock is better ?
Click to expand...
Click to collapse
just clean & lock
cyanGalaxy said:
It will not.
If the Flash aborts, it won't even get to the stage of locking the bootloader.
Click to expand...
Click to collapse
I meant in case of a bootloop.
gregdeberg33 said:
Ok thanks but why ? Fastboot oem lock is better ?
Click to expand...
Click to collapse
Because if you lock bootloader while flashing a rom with a different region than what came in the box, you will hard brick your phone