Related
hello all, while my phone was upgrading it got stucked while upgrading and i was force to remove battery and now it is in this condition-Secure Booting Error! Cause: boot certification verify ,
i cant even flash it with flash tool.
Please any guide
unbrick your lg f460 l
the best method i think is to flash tot files.
with lg flash tool
UPSS !! said:
hello all, while my phone was upgrading it got stucked while upgrading and i was force to remove battery and now it is in this condition-Secure Booting Error! Cause: boot certification verify ,
i cant even flash it with flash tool.
Please any guide
Click to expand...
Click to collapse
Did u unbrick your 460l. My 460k is also bricked.no success uptil now
Just wait for it to finish, mine took several hours
F460k in 9008
dicecuber said:
Just wait for it to finish, mine took several hours
Click to expand...
Click to collapse
I tried to downgrde and now i hve 9008 delod mode on lg f460k
Need DeBrick.img
All you need is deBrick.img fil for that unit
http://forum.xda-developers.com/lg-g3/general/unbrick-lg-g3-qhsusbbulk-qualcomm-9008-t3072091
---------- Post added at 01:50 AM ---------- Previous post was at 01:48 AM ----------
This is the unbrick hardbrick page check this out and remeber if u find this helpful remember the thanx button and dont foget to thank the orig poster for his hard work also
TheMadScientist420 said:
http://forum.xda-developers.com/lg-g3/general/unbrick-lg-g3-qhsusbbulk-qualcomm-9008-t3072091
---------- Post added at 01:50 AM ---------- Previous post was at 01:48 AM ----------
This is the unbrick hardbrick page check this out and remeber if u find this helpful remember the thanx button and dont foget to thank the orig poster for his hard work also
Click to expand...
Click to collapse
This op is for g3 not for cat6. Bcz its chip is 8084
UPSS !! said:
hello all, while my phone was upgrading it got stucked while upgrading and i was force to remove battery and now it is in this condition-Secure Booting Error! Cause: boot certification verify ,
i cant even flash it with flash tool.
Please any guide
Click to expand...
Click to collapse
1. Download KDZ or TOT for your device
2. Download LG Flash tool
3. Flash KDZ or TOT with LG flash tool
4. Device is fixed
Im sorry i wasnt famliar with the model thought it was a g3
i'm just make my phone Super hard brick. Why dont anyone make APQ8084 model
Help please, my LG G3 F460L brick too.
Qualcomm 9008
Pio_28 said:
Help please, my LG G3 F460L brick too.
Qualcomm 9008
Click to expand...
Click to collapse
have you guys ubricked your lg G3? all need is debrick.img or dump file to put in sdcard. if you guys can join us, we can together make this success. we have solution. soultion at doorstep.. but need your support.
Not really
Kathik said:
have you guys ubricked your lg G3? all need is debrick.img or dump file to put in sdcard. if you guys can join us, we can together make this success. we have solution. soultion at doorstep.. but need your support.
Click to expand...
Click to collapse
i searched alot over the internet but nothing i found then
I paid 4000 rupees to a technician in local market to repair it.
---------- Post added at 12:46 AM ---------- Previous post was at 12:44 AM ----------
Did you get any solution for it?
muzammil457 said:
i searched alot over the internet but nothing i found then
I paid 4000 rupees to a technician in local market to repair it.
---------- Post added at 12:46 AM ---------- Previous post was at 12:44 AM ----------
Did you get any solution for it?
Click to expand...
Click to collapse
thats pretty high but does the repair done by box or by dump files, debrick image? i don;t like to use box as they solder emmc is risk life span of the device.
could you tell how he repaired? could you please make a debrick image for us? we flash it via sdcard to boot our mobile. i sent you personal message. reply to it.
Kathik said:
thats pretty high but does the repair done by box or by dump files, debrick image? i don;t like to use box as they solder emmc is risk life span of the device.
could you tell how he repaired? could you please make a debrick image for us? we flash it via sdcard to boot our mobile. i sent you personal message. reply to it.
Click to expand...
Click to collapse
I dont know how he did it. He wont tell me bcz he has to earn money too.
F460 owners soution for unbrick
F460 OWNERS . WE HAVE EASY HARD BRICK METHOD.
com port 9006 can be fixed. google partition unbrick. ubuntu method also works.
f460 : 9008 com port,, no twrp, no download mode, boot security error, verification failed. traditional lg flashtool, board diag, lg smart boot doesn;t help at all., i tried all and fed up. finally understood only 2 options on our own solutions available.
1. dump file using sd card
2. BOx method like riff, jtag, .octoplus (Risky as it shorts resistors may phone dead)
3. debrick image create ,
we our selves has to wake up and try to build by 1 and 3. 2nd option is expensive, soldering to emmc is not advisable.
for option 1, vietanmese selling dump filess, if anyone bought dumpfiles for f460, kindly upload and share with us.
option 2 by professionals repair method, option 3 debrick not yet availble for us, seniors has to look into this to create it. debrick is easy and simple and best of all.
ANY ONE HAVE DUMP FILE OR DEBRICK IMAGE FOR F460? thanks me if usefuL
Kathik said:
F460 OWNERS . WE HAVE EASY HARD BRICK METHOD.
com port 9006 can be fixed. google partition unbrick. ubuntu method also works.
f460 : 9008 com port,, no twrp, no download mode, boot security error, verification failed. traditional lg flashtool, board diag, lg smart boot doesn;t help at all., i tried all and fed up. finally understood only 2 options on our own solutions available.
1. dump file using sd card
2. BOx method like riff, jtag, .octoplus (Risky as it shorts resistors may phone dead)
3. debrick image create ,
we our selves has to wake up and try to build by 1 and 3. 2nd option is expensive, soldering to emmc is not advisable.
for option 1, vietanmese selling dump filess, if anyone bought dumpfiles for f460, kindly upload and share with us.
option 2 by professionals repair method, option 3 debrick not yet availble for us, seniors has to look into this to create it. debrick is easy and simple and best of all.
ANY ONE HAVE DUMP FILE OR DEBRICK IMAGE FOR F460? thanks me if usefuL
Click to expand...
Click to collapse
Hey, how can I contact the Vietnamese? I'm willing to pay if there's a way to solve the brick of MSM8084.
trumanh14 said:
Hey, how can I contact the Vietnamese? I'm willing to pay if there's a way to solve the brick of MSM8084.
Click to expand...
Click to collapse
i tell and help you. i have sent you private message. check it and reply.
Thank You
Kathik said:
have you guys ubricked your lg G3? all need is debrick.img or dump file to put in sdcard. if you guys can join us, we can together make this success. we have solution. soultion at doorstep.. but need your support.
Click to expand...
Click to collapse
Huge Thanks Kathik,
you saved my LG G3 F460,
now my G3 back to normal.
I follow Your instruction from Dead,Unbrick, Debrick LG G3 F460 S/K/L.
Salute to you :good:
Hello! I have a problem! I bought a LG G3 D851 refurbished ''frankstain'' in ebay
When trying to upgrade firmware to lollipop 5.1 the bricked device
His original rom is; ''LGD851AT-00-V10z-GLOBAL-COM-OCT-22-2014-32GB''
I've looked all over the internet and found nothing about it. Can someone help me?
thx!
Can you provide more details..
Is the phone able to power on.
Is the phone looping in startup screen.
Does the computer detect the phone if its connected on USB?
PonchosoftX said:
Can you provide more details..
Is the phone able to power on.
Is the phone looping in startup screen.
Does the computer detect the phone if its connected on USB?
Click to expand...
Click to collapse
When plugged-in appears '' Qualcomm HS-USB QDLoader 9008 ''
I used the TOT stock(G3 851 T-Mobile) and it does not work, it returns to '' Qualcomm '' mode. I used a TOT stock of the G3 D850 and it worked, but I do not have a network
Deanff3 said:
When plugged-in appears '' Qualcomm HS-USB QDLoader 9008 ''
I used the TOT stock(G3 851 T-Mobile) and it does not work, it returns to '' Qualcomm '' mode. I used a TOT stock of the G3 D850 and it worked, but I do not have a network
Click to expand...
Click to collapse
Not sure if was Android or LG but seems that after Upgrade to Android 6 a new feature called Antirollback was implemented on the devices preventing to Downgrade to old versions.
This Guide works very well for me, please read carefully and follow all Steps in order to get back your device.
Here.
Hope this can help.:good:
PonchosoftX said:
Not sure if was Android or LG but seems that after Upgrade to Android 6 a new feature called Antirollback was implemented on the devices preventing to Downgrade to old versions.
This Guide works very well for me, please read carefully and follow all Steps in order to get back your device.
Here.
Hope this can help.:good:
Click to expand...
Click to collapse
Thanks. I already tried this, it did not work.
@Deanff3, being in Qualcomm mode at least means you still have a chance. When I bricked my D851 I couldn't even get that via software means. Phone identified itself as Google instead of LG. Had to "short circuit" the phone so I could get Qualcomm mode to continue on.
Have you checked the following thread? Used this guide and I was back in service after weeks of almost giving up.
http://forum.xda-developers.com/showthread.php?t=3430221
[GUIDE] LG G3 D851 Unbrick Qualcomm 9008 Fully Working... Unbrickable D851!
LG G3 D851, Validus v13.5 ROM, MultiROM, Tapatalk 4.9.5
---------- Post added at 09:57 PM ---------- Previous post was at 09:24 PM ----------
BTW, searching around I see the "device" you posted. It shows up all over in old posts. Some will be almost exact except swap D851 for D855. All V10z-GLOBAL. Yet no actual info about it. Just users that got bricked. In this post it was due to trying to downgrade.
http://forum.gsmhosting.com/vbb/f799/tmobile-lg-g3-d851-after-flash-dead-2154970/
And another related post. Confusing as to what works on frankenphones.
https://www.google.com/amp/s/amp.reddit.com/r/LGG3/comments/5e3wod/dont_know_my_lg_g3_model/
Even from a firmware repository I don't think these V10z-GLOBAL things are available. Could be wrong but I can't find.
LG G3 D851, Validus v13.5 ROM, MultiROM, Tapatalk 4.9.5
marcdw said:
@Deanff3, being in Qualcomm mode at least means you still have a chance. When I bricked my D851 I couldn't even get that via software means. Phone identified itself as Google instead of LG. Had to "short circuit" the phone so I could get Qualcomm mode to continue on.
Have you checked the following thread? Used this guide and I was back in service after weeks of almost giving up.
http://forum.xda-developers.com/showthread.php?t=3430221
[GUIDE] LG G3 D851 Unbrick Qualcomm 9008 Fully Working... Unbrickable D851!
LG G3 D851, Validus v13.5 ROM, MultiROM, Tapatalk 4.9.5
---------- Post added at 09:57 PM ---------- Previous post was at 09:24 PM ----------
BTW, searching around I see the "device" you posted. It shows up all over in old posts. Some will be almost exact except swap D851 for D855. All V10z-GLOBAL. Yet no actual info about it. Just users that got bricked. In this post it was due to trying to downgrade.
http://forum.gsmhosting.com/vbb/f799/tmobile-lg-g3-d851-after-flash-dead-2154970/
And another related post. Confusing as to what works on frankenphones.
https://www.google.com/amp/s/amp.reddit.com/r/LGG3/comments/5e3wod/dont_know_my_lg_g3_model/
Even from a firmware repository I don't think these V10z-GLOBAL things are available. Could be wrong but I can't find.
LG G3 D851, Validus v13.5 ROM, MultiROM, Tapatalk 4.9.5
Click to expand...
Click to collapse
Thank you. I believe that being a ''frankstein'' it was a custom firmware, that's why we did not find it on the internet. Unbrick using the D850, please do not need to set, then emergency. : Eek:
Hello, Iam having a bricked Google Pixel XL 128GB with black screen, no fastboot, no recovery(phone only detected as HS-USB QDLoader 9008).
Is there anyway to unbrick the phone?
What was your setup before this happened? What were you trying to do before this happened?
chapelfreak said:
What was your setup before this happened? What were you trying to do before this happened?
Click to expand...
Click to collapse
Bad Flash on OTA update
Hey... Actually, there's no easy way to get the pixel back up and running. I tried to read a bit about the issue on different phones. I'm not sure it could be of some use for our device.. It also involves, either having someone to pull a full backup of his phone for you which you'll have to find... Or finding special Qualcomm files and firmware used for flashing using Qualcomm tool QFIL... I haven't found Qualcomm files/firmware on the internet yet... And i'm not 100% sure the first solution would work either, since we have now different system partitions.
If you don't have any warranty on your phone, you could try it. Otherwise, send it back. There's likely no way to recover personnal datas anyway...
Also about getting out of EDL mode, i've read in the N6P forum, someone saying you'll have to push the power button for no less than 40 seconds. Try it maybe and try to reboot into bootloader afterward...
Good luck...
5.1 said:
Hey... Actually, there's no easy way to get the pixel back up and running. I tried to read a bit about the issue on different phones. I'm not sure it could be of some use for our device.. It also involves, either having someone to pull a full backup of his phone for you which you'll have to find... Or finding special Qualcomm files and firmware used for flashing using Qualcomm tool QFIL... I haven't found Qualcomm files/firmware on the internet yet... And i'm not 100% sure the first solution would work either, since we have now different system partitions.
If you don't have any warranty on your phone, you could try it. Otherwise, send it back. There's likely no way to recover personnal datas anyway...
Also about getting out of EDL mode, i've read in the N6P forum, someone saying you'll have to push the power button for no less than 40 seconds. Try it maybe and try to reboot into bootloader afterward...
Good luck...
Click to expand...
Click to collapse
I tried QFIL, MSMToolDownloader(from OnePlus 3T), MiFlash, etc. They all ask RawProgramm0.xml, Patch0.xml, MSM8996..mbn, and xxx_firehose_emmc_8996.xxx specifically for our Google Pixel XL 128GB. None of them are available yet.
droidan said:
I tried QFIL, MSMToolDownloader(from OnePlus 3T), MiFlash, etc. They all ask RawProgramm0.xml, Patch0.xml, MSM8996..mbn, and xxx_firehose_emmc_8996.xxx specifically for our Google Pixel XL 128GB. None of them are available yet.
Click to expand...
Click to collapse
Yeah I haven't found anything either. I think it will take some time before someone share those.
Check this thread:
https://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040
This part:
2. REVIVING YOUR YU BACK
2.a NEW "Qualcomm HS-USB QDLoader 9008" MODE
As I said earlier, since our phone has a different partition layout, I don't know if the same process can be achieved. Also you'll have to pull the IMG from a working device.
You don't have a valid warranty?
5.1 said:
Yeah I haven't found anything either. I think it will take some time before someone share those.
Check this thread:
https://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040
This part:
2. REVIVING YOUR YU BACK
2.a NEW "Qualcomm HS-USB QDLoader 9008" MODE
As I said earlier, since our phone has a different partition layout, I don't know if the same process can be achieved. Also you'll have to pull the IMG from a working device.
You don't have a valid warranty?
Click to expand...
Click to collapse
Thank you for your reply and information.
I believe I have an OLD 9008 mode.
Here's what I have found:
1. The 8996 firehose is specific to the device. Other 8996 version do not work. (Oneplus 3T, ZUK, Xiaomi, LEECO)
2. Quote from Ghassani on Le Pro3 bricked thread:
"Since it was suggested to contact me about this issue, I am going to answer here what I told the OP through email:
This is a hard brick. Meaning, you probably flashed a wrong SBL partition, or you flashed in the wrong order, or in the wrong mode.
When this happens, and the device has secure boot enabled (which all production devices do) you only have two options:
1) Using a signed recovery programmer to send via emergency mode (Sahara mode), then transferring to that programmers protocol (streaming DLOAD or the newer firehose). From there you can recover the emmc.
2) JTAG on the emmc for direct recovery.
It is easy to find these programmer files, both signed and unsigned. The problem is each device is using a different private key generated by the OEM to build the SoC. Without a properly signed programmer, Sahara will reject the programmer and go into a no-interrupt loop until you power cycle the device. Pretty much all OEMs do not give out these files. The ones you can find floating around for various devices are generally leaked, or rarely given out by the OEM. For most devices, JTAG is the only option.
I have a small collection of both signed and unsigned programmer files on this github repository:
https://github.com/ghassani/openpst-assets
If anyone has properly signed files for devices I do not have, please send them in to me and I can add them or you can put in a pull request directly to the repository and add it that way."
Hopefully someone from Google/HTC can share those 3 files.(eMMc_firehose_8996.elf, rawprogram0.xml and patch0.xml for Google Pixel XL 128GB)
Or maybe I can ask Google assistant to leak the files..lol
droidan said:
Bad Flash on OTA update
Click to expand...
Click to collapse
What does that mean? Were you rooted, unlocked? If so return the device, no?
droidan said:
I tried QFIL, MSMToolDownloader(from OnePlus 3T), MiFlash, etc. They all ask RawProgramm0.xml, Patch0.xml, MSM8996..mbn, and xxx_firehose_emmc_8996.xxx specifically for our Google Pixel XL 128GB. None of them are available yet.
Click to expand...
Click to collapse
Sent from my Pixel using XDA-Developers Legacy app
droidan said:
Thank you for your reply and information.
I believe I have an OLD 9008 mode.
Here's what I have found:
1. The 8996 firehose is specific to the device. Other 8996 version do not work. (Oneplus 3T, ZUK, Xiaomi, LEECO)
2. Quote from Ghassani on Le Pro3 bricked thread:
"Since it was suggested to contact me about this issue, I am going to answer here what I told the OP through email:
This is a hard brick. Meaning, you probably flashed a wrong SBL partition, or you flashed in the wrong order, or in the wrong mode.
When this happens, and the device has secure boot enabled (which all production devices do) you only have two options:
1) Using a signed recovery programmer to send via emergency mode (Sahara mode), then transferring to that programmers protocol (streaming DLOAD or the newer firehose). From there you can recover the emmc.
2) JTAG on the emmc for direct recovery.
It is easy to find these programmer files, both signed and unsigned. The problem is each device is using a different private key generated by the OEM to build the SoC. Without a properly signed programmer, Sahara will reject the programmer and go into a no-interrupt loop until you power cycle the device. Pretty much all OEMs do not give out these files. The ones you can find floating around for various devices are generally leaked, or rarely given out by the OEM. For most devices, JTAG is the only option.
I have a small collection of both signed and unsigned programmer files on this github repository:
https://github.com/ghassani/openpst-assets
If anyone has properly signed files for devices I do not have, please send them in to me and I can add them or you can put in a pull request directly to the repository and add it that way."
Hopefully someone from Google/HTC can share those 3 files.(eMMc_firehose_8996.elf, rawprogram0.xml and patch0.xml for Google Pixel XL 128GB)
Or maybe I can ask Google assistant to leak the files..lol
Click to expand...
Click to collapse
Yeah, unless someone leaks official programmer, you are SOL...
Good luck... :good:
Hi guys,
I've opened a similar thread on google forum - related to pixel 128gb being bricked and in chipset download mode.
If there are enough bricked pixels out there perhaps google will (hopefully) share those files?
Cheers,
Dan
The deluge of bricked Pixels resulting from the Oreo update continues...
I did, however, find these pages posted in the last couple weeks, and wondering if they're the answer to the Q's posted earlier ITT (sry I'm too new to post live links, so you'll have to paste these):
- androidauthority.com/download-android-8-0-oreo-794622/
- androidauthority.com/install-android-oreo-758342/
- developers.google.com/android/ota
Earlier ITT, posters were saying that they couldn't find the firmware or other files that would allow someone to recover from the hard-bricked state...but are those 'official' factory images and OTAs what they were saying they needed, but which they couldn't find at the time? In short, might we now actually have the files necessary to save our bricked Pixels without engaging in Macguyvering that would void the warranty?
Out of curiosity, was your bootloader locked prior to running into this issue?
Pain-N-Panic said:
Out of curiosity, was your bootloader locked prior to running into this issue?
Click to expand...
Click to collapse
I assume so...I bought the Pixel directly from Google, so assumed I was getting the purest Android installation possible / no provider bloatware etc...if i'm not mistaken, the bootloader would have been Locked when I initially received the phone, right?...if so, then yes it would still have been locked when it bricked, as I didn't take any actions to unlock it (nor would i know how)
hopefully files will be shared soon for sure it is exists
I have the same problem and all I can do is rma.
Is it possible to pull the files from a working pixel?
I wonder if the files in question would hold the key to VZW Pixel XL customers to somehow use /find an exploit to gain temp root to ultimately unlock their bootloader.
mattwheat said:
I wonder if the files in question would hold the key to VZW Pixel XL customers to somehow use /find an exploit to gain temp root to ultimately unlock their bootloader.
Click to expand...
Click to collapse
Maybe that's why they aren't giving the files
This happened to mine as well
Went from 8.0 to 8.1 - wiped data and re-locked bootloader. Ran fine for two days then powered down and now I'm in this qualcomm mode. Thankfully I purchased the 2-year through Google. Unfortunately their support is dogsh**.
Update: Ok Google's support rep was actually pretty solid but their system is awful. I'm already on a refurb and it doesn't have the IMEI printed on the sim tray. Either way they worked it out and I'm down $80 for the deductible.
I have the same problem
Hello, I hope to receive some help, I tell you, I was updating my cell phone when the electricity went out in my house and my phone ended up shutting down, and when I connect it to the charger there is only a red LED flashing as seen in the video:
https://drive.google.com/file/d/1YX1FbofTtJtmXMYGc5GJERavasiIYrRH/view?usp=sharing
also I can not enter in fastboot, download, PC not recognize it, just the red light.
I do not know what to do
Should be under waranty.. Return it to LG service.
If the device is under warranty, please send it for warranty, if you do not have a warranty from LG, you can contact me, will help you save the device.
dan117chat said:
also I can not enter in fastboot, download, PC not recognize it, just the red light.
I do not know what to do
Click to expand...
Click to collapse
Try using a USB Type C cable
PjLyTam said:
If the device is under warranty, please send it for warranty, if you do not have a warranty from LG, you can contact me, will help you save the device.
Click to expand...
Click to collapse
Hi, my phone switched off( qualcomm hs-usb qdloader 9008) only, after installing the Korean firmware, G710NO20c_00_OPEN_KR_OP_0107.kdz my model is LG G7 710 TM, Tmobile. can you help me?
kacak11 said:
Hi, my phone switched off( qualcomm hs-usb qdloader 9008) only, after installing the Korean firmware, G710NO20c_00_OPEN_KR_OP_0107.kdz my model is LG G7 710 TM, Tmobile. can you help me?
Click to expand...
Click to collapse
You should have done a little more reading about your device. See this thread. https://forum.xda-developers.com/lg...how-to-install-pie-stock-treble-aosp-t3914079
netookska05 said:
You should have done a little more reading about your device. See this thread. https://forum.xda-developers.com/lg...how-to-install-pie-stock-treble-aosp-t3914079
Click to expand...
Click to collapse
This is then, I was the one who announced it. Maybe you should read it carefully, sorry.
---------- Post added at 06:36 PM ---------- Previous post was at 06:29 PM ----------
netookska05 said:
You should have done a little more reading about your device. See this thread. https://forum.xda-developers.com/lg...how-to-install-pie-stock-treble-aosp-t3914079
Click to expand...
Click to collapse
#125 post.This is then, I was the one who announced it. Maybe you should read it carefully, sorry.
kacak11 said:
This is then, I was the one who announced it. Maybe you should read it carefully, sorry.
---------- Post added at 06:36 PM ---------- Previous post was at 06:29 PM ----------
#125 post.This is then, I was the one who announced it. Maybe you should read it carefully, sorry.
Click to expand...
Click to collapse
My bad I only responded to this thread since your post was recent. Looks like you may need a replacement unless you know how to extract kdz and create a firehose file and using qfil. Your SOL. Not sure if this would work so take a look at this if your computer savy give it a try. https://www.droidsavvy.com/unbrick-qualcomm-mobiles/
netookska05 said:
My bad I only responded to this thread since your post was recent. Looks like you may need a replacement unless you know how to extract kdz and create a firehose file and using qfil. Your SOL. Not sure if this would work so take a look at this if your computer savy give it a try. https://www.droidsavvy.com/unbrick-qualcomm-mobiles/
Click to expand...
Click to collapse
Thanks for your interest.
ok
kacak11 said:
Hi, my phone switched off( qualcomm hs-usb qdloader 9008) only, after installing the Korean firmware, G710NO20c_00_OPEN_KR_OP_0107.kdz my model is LG G7 710 TM, Tmobile. can you help me?
Click to expand...
Click to collapse
ok inbox me
PjLyTam said:
ok inbox me
Click to expand...
Click to collapse
how is it now?
I successfully debrick G7 G710EM for a friend on the xda forum, he printed my own inbox on facebook @kacak11
PjLyTam said:
Unbrick Done @kacak11
Click to expand...
Click to collapse
how?
same status here someone wanna write up a fix?
unbrick G7
randomblame said:
same status here someone wanna write up a fix?
Click to expand...
Click to collapse
Using pro or octoplus pro jtag medusa, you can unbrick G7
---------- Post added at 10:07 AM ---------- Previous post was at 10:06 AM ----------
PjLyTam said:
Using pro or octoplus pro jtag medusa, you can unbrick G7
---------- Post added at 10:07 AM ---------- Previous post was at 10:06 AM ----------
Click to expand...
Click to collapse
Octopus box can't talk with the T-Mobile model as it has different bootloader
hi
LameMonster82 said:
Octopus box can't talk with the T-Mobile model as it has different bootloader
Click to expand...
Click to collapse
Yes, for the T Mobile model it is required to intervene ufs hard drive hardware
Meh I'm sending it in hopefully they will replace it. For now I have a xiaomi mi9 on the way so I will at least get to have fun with a high end unlocked device
Lg G7 thinq Tmobile hard bricked
Hello Im new here and Im stuck in a bad situation. I have Tmobile LG G7 thinq and it got hard bricked .The only thing I see when plugged into computer is Qualcomm 9008 driver and the device is completely dead and blacked out, not even red led chraging light light up. please help me out thank you..
Trying to sort out all the different models of this phone has been an exercise in frustration.
AFAIK, the two phones have nearly identical bands. W has NFC and single SIM; G has dual sim and no NFC.
My phone was purchased from Amazon. I'm trying to flash to my carrier's stock firmware to see if I can use WiFi calling. Two questions
1) Anyone tried? Does it work?
2) Can Odin unbrick from flashing a different version?
There's only one other thread I could find where people are flashing F onto G phones, but whether it will cause a hard brick is not apparent....
I personally have bricked my A50 when trying to update to August firmware while rooted lol. I thought it was done for but I was able to get to download mode by holding down both volume keys while the screen was off and plugging it in
---------- Post added at 03:05 PM ---------- Previous post was at 03:03 PM ----------
I have flashed the firmware of a different model of A50, specifically I went from FN to F. As there model doesn't support NFC, that function did not work on my device however everything else functioned correctly.
OK so it looks like it's not an out-and-out brick and I can potentially recover if flashing from G to W doesn't work out. Something to think about if I want to toy around with this phone a bit more.
felixdd said:
OK so it looks like it's not an out-and-out brick and I can potentially recover if flashing from G to W doesn't work out. Something to think about if I want to toy around with this phone a bit more.
Click to expand...
Click to collapse
Yeah, from my experiences I have always been able to recover from it.
Once while flashing an update through Odin on my A50 there was a power cut but thankfully my phone went into a recovery mode automatically because it detected the error.
I mean I gotta say the whole "your mileage may vary" thing.