Well, it seems my daughter has been the unfortunate one of many that has been hit by her Pixel 3 being "bricked" for no apparent reason.
After a full afternoon of research, I now understand the state it's in and that it's sitting in EDL and won't cycle out of it. I'm a Linux guy, and can plainly see that lsusb is reporting it being 05c6:9008 in "QDL" mode. So I've got the QDL tool for Linux, I understand fastboot and adb, etc. HOWEVER, I'm rather foggy about how to acquire, or perhaps create, a "blankflash" for the Pixel 3. (Or maybe I'm just tired...) In any case, is there anyone here that might point me in the right direction of how to get, or even create, a blankflash for this phone?
So ANY pointers in the right direction on a blankflash for the Pixel 3 would be appreciated. Thanks all!
TechnicalJohn said:
Well, it seems my daughter has been the unfortunate one of many that has been hit by her Pixel 3 being "bricked" for no apparent reason.
After a full afternoon of research, I now understand the state it's in and that it's sitting in EDL and won't cycle out of it. I'm a Linux guy, and can plainly see that lsusb is reporting it being 05c6:9008 in "QDL" mode. So I've got the QDL tool for Linux, I understand fastboot and adb, etc. HOWEVER, I'm rather foggy about how to acquire, or perhaps create, a "blankflash" for the Pixel 3. (Or maybe I'm just tired...) In any case, is there anyone here that might point me in the right direction of how to get, or even create, a blankflash for this phone?
So ANY pointers in the right direction on a blankflash for the Pixel 3 would be appreciated. Thanks all!
Click to expand...
Click to collapse
I believe this is the best thread for anyone with this issue to be reading. The issue is discussed and unfortunately, there is no resolution.
That said, I've never heard of a 'blank flash'. But, what we do know is that a device that is stuck in edl mode means u can't get to the normal recovery utilities like fastboot or adb. And because google won't release the 'programmer firehose' so that qfil can access the device in edl mode, there's really no way to 'flash' anything, blank or otherwise.
I wish I was wrong, but am quite sure this is the unfortunate situation, unless google releases the firehose.
(When u say 'QDL tool for linux', do u mean the bkerler edl python utilities? Unfortunately, they too will of course require the programmers firehose. If that's available somewhere, would luv to know about it).
cheers
AsItLies said:
I believe this is the best thread for anyone with this issue to be reading. The issue is discussed and unfortunately, there is no resolution.
That said, I've never heard of a 'blank flash'. But, what we do know is that a device that is stuck in edl mode means u can't get to the normal recovery utilities like fastboot or adb. And because google won't release the 'programmer firehose' so that qfil can access the device in edl mode, there's really no way to 'flash' anything, blank or otherwise.
I wish I was wrong, but am quite sure this is the unfortunate situation, unless google releases the firehose.
(When u say 'QDL tool for linux', do u mean the bkerler edl python utilities? Unfortunately, they too will of course require the programmers firehose. If that's available somewhere, would luv to know about it).
cheers
Click to expand...
Click to collapse
Hey, thanks for the input as well as the move of my post to a more appropriate forum. I felt like I had hit the end of the road, but was hopeful maybe there was an off-road path
Here are a couple sources for my references...
I found this XDA post mentioning the EDL and QDL:
[GUIDE] unbrick and flash Official ROM in EDL on linux
I'm running Kubuntu 20.04, and you can install QDL using snap: https://snapcraft.io/qdl
The "blank flash" reference came from this guide for a Moto G7:
Hard Bricked My Moto G7 Plus after Downgrade: How to Fix
LOL, ironically the blankflash.zip is hosted here on XDA somewhere.
I'm in the process of evaluating "new to her" phones for her to replace this Pixel 3... but I'm still hoping to resurrect this thing, since the knowledge would be invaluable.
TechnicalJohn said:
Hey, thanks for the input as well as the move of my post to a more appropriate forum. I felt like I had hit the end of the road, but was hopeful maybe there was an off-road path
Here are a couple sources for my references...
I found this XDA post mentioning the EDL and QDL:
[GUIDE] unbrick and flash Official ROM in EDL on linux
I'm running Kubuntu 20.04, and you can install QDL using snap: https://snapcraft.io/qdl
The "blank flash" reference came from this guide for a Moto G7:
Hard Bricked My Moto G7 Plus after Downgrade: How to Fix
LOL, ironically the blankflash.zip is hosted here on XDA somewhere.
I'm in the process of evaluating "new to her" phones for her to replace this Pixel 3... but I'm still hoping to resurrect this thing, since the knowledge would be invaluable.
Click to expand...
Click to collapse
I certainly understand the desire to fix the device, I mean, there's nothing wrong with them, they work fine, normally.
But, even the first link you mention has the following pre-reqs: and it's the 3rd item listed that no one has (afaik). The patch xml isn't needed, the rawprogram xml can be created / modified from another source, but not the firehose file. It's specific to the device, and google, as said, won't release it. So just to clarify, I've used edl mode on numerous LG devices (as their firehose file is available), I've used both qfil and bkerler edl utilities (python based), and neither of them can access a device without the firehose file, it's just not possible.
Truly wish that if anyone has that file, pls let us know, because without it, these devices are bricks.
patch0.xml
rawprogram_unparse0.xml,
prog_firehose_ddr.elf (could have also a .mbn file extension, it's the same)
AsItLies said:
I certainly understand the desire to fix the device, I mean, there's nothing wrong with them, they work fine, normally.
But, even the first link you mention has the following pre-reqs: and it's the 3rd item listed that no one has (afaik). The patch xml isn't needed, the rawprogram xml can be created / modified from another source, but not the firehose file. It's specific to the device, and google, as said, won't release it. So just to clarify, I've used edl mode on numerous LG devices (as their firehose file is available), I've used both qfil and bkerler edl utilities (python based), and neither of them can access a device without the firehose file, it's just not possible.
Truly wish that if anyone has that file, pls let us know, because without it, these devices are bricks.
patch0.xml
rawprogram_unparse0.xml,
prog_firehose_ddr.elf (could have also a .mbn file extension, it's the same)
Click to expand...
Click to collapse
Yeah, I was just giving reference to what lead me to the awareness of the QDL and the fact that it's possible to flash these Qualcomm devices. I could see that I was missing a piece there, and now that you've pointed me in the direction of the other thread I see things a bit more clearly after a sleep.
All good info, and perhaps we'll get the needed piece at some point! Too bad we can't construct that file from a dump or something.
Related
I am convinced I have bricked my phone. My Windows 7 x64 machine can "talk" with the device- it refers to my bricked phone as QHUSB_DLOAD. Upon installing QPST, it acquires a driver named HS-USB Diagnostics 9008, introducing it to my machine as a COM port. My installation of Software Update Tool LR is able to give the approval that my device exists and is ready to receive files, but none of the nb0 files work.
Here are some details about my situation:
My Motorola Triumph is unable to reach download mode nor recovery mode in the traditional sense. The Software Update Tool claims it is in "Emergency Download Mode".
There is no screen activity on the phone. The only way I know my device is somewhat alive is by the notification Windows gives me when I insert new hardware.
If I could extract the contents of an NB0 file, I might be able to try something that may or may not work, but the only tool that exists on the planet was uploaded to MegaUpload, which was taken down by the Feds.
I don't have a stock Motorola Triumph NB0 file, but if I were to acquire one, I might be able to try something else that may or may not work.
I flashed the MMC block device under /dev/block/emmcblk0.
Any help is appreciated, as I am desperate for any help- feel free to ask questions. I won't get frustrated in answering them as I may have missed a few, important details.
Remember guys, if there is a will, there is a way. Help me out so if someone else ever comes across this problem, they will know EXACTLY what to do!
My rom is stock. Where is that file? Perhaps I could find and copy it using root explorer and send you a copy? Worth a shot.
Sent from my MOTWX435KT using xda premium
caHarkness said:
I am convinced I have bricked my phone. My Windows 7 x64 machine can "talk" with the device- it refers to my bricked phone as QHUSB_DLOAD. Upon installing QPST, it acquires a driver named HS-USB Diagnostics 9008, introducing it to my machine as a COM port. My installation of Software Update Tool LR is able to give the approval that my device exists and is ready to receive files, but none of the nb0 files work.
Here are some details about my situation:
My Motorola Triumph is unable to reach download mode nor recovery mode in the traditional sense. The Software Update Tool claims it is in "Emergency Download Mode".
There is no screen activity on the phone. The only way I know my device is somewhat alive is by the notification Windows gives me when I insert new hardware.
If I could extract the contents of an NB0 file, I might be able to try something that may or may not work, but the only tool that exists on the planet was uploaded to MegaUpload, which was taken down by the Feds.
I don't have a stock Motorola Triumph NB0 file, but if I were to acquire one, I might be able to try something else that may or may not work.
I flashed the MMC block device under /dev/block/emmcblk0.
Any help is appreciated, as I am desperate for any help- feel free to ask questions. I won't get frustrated in answering them as I may have missed a few, important details.
Remember guys, if there is a will, there is a way. Help me out so if someone else ever comes across this problem, they will know EXACTLY what to do!
Click to expand...
Click to collapse
There is no triumph nbo file available.
Check this post; it may be helpful:
http://androidforums.com/triumph-al...-experiment-thread-caution-2.html#post4243388
Well, thanks for the input!
I eventually worked up the motive to send it in under warranty. However, I did end up calling Motorola as opposed to Virgin Mobile. The guys at Motorola said they would be happy to fix it as long as it wasn't physically damaged or submerged in liquids. Forget about paying Virgin Mobile for the phone insurance- Motorola wants to keep their customers happy.
Just thought I would introduce myself and see how everyone is doing.
Well I've gotten as far as getting qualcomm tools to recognize the device but I'm a little afraid to push anything since as far as I can tell we don't have a firehose or rawprogram0xml for our devices! (mine is sprint 996)
I don't actually use this phone for anything but a multimedia device so if someone had any ideas is be willing to try them.
Also I was wondering, I only seem to be able to access downloads mode via by vol up and insert cable... I can't get any other mode to work...
So many toolsets that just arent there... Seems we are so close to being able to fix this but missing like one or two files... So far the closest I can get is with QFIL I have the zv8 tot, rawprogram0.xml and the 8994 programner. All its asking for is a patch0.xml now... Ive no clue how to make that one .
I just leave it here forum.gsmhosting.com/vbb/f672/worlds-first-lg-ls996-dead-boot-repair-done-2087401/
It's only way to repair
Sent from my Galaxy Tab S2 using XDA Labs
Thanks for the link and I had read it... But I just can't see that being the only way... I can see my phone and manipulate that data via tools like qfil and such.... There has to be a method of rewriting the bootloader to enable it to start again. I would even be a tester for anyone.
I don't know if this was known or not but this could help some users if they could possibly make some program to fix hard bricks.
https://www.reddit.com/r/lgv20/comm...mm_9008_test_point/?utm_source=reddit-android
I'm gessing it's too late for this development.
faeterov said:
I'm gessing it's too late for this development.
Click to expand...
Click to collapse
No!! It's still not too late. Qualcom 9008 hack will save v20 community.
CrUxXxX said:
No!! It's still not too late. Qualcom 9008 hack will save v20 community.
Click to expand...
Click to collapse
How?
faeterov said:
How?
Click to expand...
Click to collapse
I'm not sure how? I'm not developer. Here's link
https://www.google.com/search?q=ins...#imgdii=IFxd7gUm4M6ZWM:&imgrc=ezDFnWnop-1xqM:
This sounds like the useless firehouse that people have been posting on xda for months and it's already been stated by several respected devs it won't work on the V20 and or it will put your phone in a state that is less than desirable
Sent from my LG-H910 using XDA Labs
Only in very rare cases will a hardbrick not result in 9008-mode. For those that have that problem, and if the phone can be restored with a "gps fix box" - then this will be helpful.
I'm wondering if it's possible to manipulate this TP to enter 9006-mode. Disturbingly I've never seen it mentioned anywhere a msm8996+ soc (or perhaps it's about the UFS storage) which has entered 9006.
Yes, the test point for 9008 on LG V20 is actually working....i tried on my phone....I need to find firehose for LG V20 to restore my phone....I accidentally chose wrong aboot version and hard bricked it.... Then tried this test point and it detected.
If any one has 8996 lge elf file, please share....
DroneJC said:
Yes, the test point for 9008 on LG V20 is actually working....i tried on my phone....I need to find firehose for LG V20 to restore my phone....I accidentally chose wrong aboot version and hard bricked it.... Then tried this test point and it detected.
If any one has 8996 lge elf file, please share....
Click to expand...
Click to collapse
I have no idea if you'll be able to get one if you aren't working for LG. Hopefully there's a 3rd party tool for sale or something
askermk2000 said:
Only in very rare cases will a hardbrick not result in 9008-mode. For those that have that problem, and if the phone can be restored with a "gps fix box" - then this will be helpful.
I'm wondering if it's possible to manipulate this TP to enter 9006-mode. Disturbingly I've never seen it mentioned anywhere a msm8996+ soc (or perhaps it's about the UFS storage) which has entered 9006.
Click to expand...
Click to collapse
Yea, 9006 mode is a thing of the past -- I want to say the 8x74 (SD800) was the last model to have it, but the 8992 (SD808) may have as well. Bottom line is that SD820 does not.
DroneJC said:
Yes, the test point for 9008 on LG V20 is actually working....i tried on my phone....I need to find firehose for LG V20 to restore my phone....I accidentally chose wrong aboot version and hard bricked it.... Then tried this test point and it detected.
If any one has 8996 lge elf file, please share....
Click to expand...
Click to collapse
Is that ALL you flashed was aboot? Is you abootbak still valid? If so, there is a firehose that you can use to change the boot LUN to boot from the *bak partitions. You don't want to use it to flash your phone, or, well, you won't really have a phone anymore. It would boot, but that would be about it.
EDIT: also, the firehose will work on any model v20 *except* the H918. Firehoses are RSA signed, just like the firmware.
-- Brian
runningnak3d said:
Yea, 9006 mode is a thing of the past -- I want to say the 8x74 (SD800) was the last model to have it, but the 8992 (SD808) may have as well. Bottom line is that SD820 does not.
Is that ALL you flashed was aboot? Is you abootbak still valid? If so, there is a firehose that you can use to change the boot LUN to boot from the *bak partitions. You don't want to use it to flash your phone, or, well, you won't really have a phone anymore. It would boot, but that would be about it.
EDIT: also, the firehose will work on any model v20 *except* the H918. Firehoses are RSA signed, just like the firmware.
-- Brian
Click to expand...
Click to collapse
Yes I have flashed aboot and device config also from other model rom, just usual fiddling with phone like any other
When phone booted, blank screen...only boot vibration felt.
You said that a RSA signed firehose is available, Mine is H990DS. If possible can you share the file or the link???
Cheers!!!
DroneJC said:
Yes I have flashed aboot and device config also from other model rom, just usual fiddling with phone like any other
When phone booted, blank screen...only boot vibration felt.
You said that a RSA signed firehose is available, Mine is H990DS. If possible can you share the file or the link???
Cheers!!!
Click to expand...
Click to collapse
Here you go...
So, good news, and bad news. I hadn't looked at this thing in a while -- so I figured I would take one more look now that I have a far greater understanding of Quallcomm security.
It turns out this is NOT a debug firehose -- it is perfectly normal firehose that can be used to rescue any v20 (except the H918 -- RSA mismatch, and LS997 (if it is ARB 1) -- this is an ARB0 firehose) with zero side effects.
Now the bad news.... because it isn't a debug firehose, you can't use it to change the boot LUN, so you will have to completely reflash your device. Well, you don't have to, but it is just as easy to make the files for a single partition as it is for the entire device.
Now the really bad news. This is just the programmer -- you are still going to need partition layout XML files, and I don't have time to make them for you.
-- Brian
runningnak3d said:
Now the really bad news. This is just the programmer -- you are still going to need partition layout XML files, and I don't have time to make them for you.
-- Brian
Click to expand...
Click to collapse
Apparently you don't have to. With QFIL you can fetch the partition table automatically from the phone, and manually select each partition to flash. Kind of like LGUP.
Here's a demonstration video: https://www.youtube.com/watch?v=gwMpDXPQLo8
It's by that aaya888 guy. Someone told me he "bought" firehoses from lg factory, and that he can unbrick H918, but he never replied to my inquiries.
Anyway that method above should work if the firehose works.
runningnak3d said:
Here you go...
So, good news, and bad news. I hadn't looked at this thing in a while -- so I figured I would take one more look now that I have a far greater understanding of Quallcomm security.
It turns out this is NOT a debug firehose -- it is perfectly normal firehose that can be used to rescue any v20 (except the H918 -- RSA mismatch, and LS997 (if it is ARB 1) -- this is an ARB0 firehose) with zero side effects.
Now the bad news.... because it isn't a debug firehose, you can't use it to change the boot LUN, so you will have to completely reflash your device. Well, you don't have to, but it is just as easy to make the files for a single partition as it is for the entire device.
Now the really bad news. This is just the programmer -- you are still going to need partition layout XML files, and I don't have time to make them for you.
-- Brian
Click to expand...
Click to collapse
Thanks Mate!!! thats a good help from your end. Do you have program that can create partition xml files....may be from the firmware i would try doing that...
If you have software from your end which could help me in creating the files....it would be great!!!
Cheers Mate!!!:good::good:
DroneJC said:
Thanks Mate!!! thats a good help from your end. Do you have program that can create partition xml files....may be from the firmware i would try doing that...
If you have software from your end which could help me in creating the files....it would be great!!!
Cheers Mate!!!:good::good:
Click to expand...
Click to collapse
Watch the video that @askermk2000 linked to in the post above. I had never used QFIL in flat mode before ... gotta love learning things.
The bottom line is as long as you haven't wiped out your partition tables, you don't need the XML partition definition files.
-- Brian
runningnak3d said:
Watch the video that @askermk2000 linked to in the post above. I had never used QFIL in flat mode before ... gotta love learning things.
The bottom line is as long as you haven't wiped out your partition tables, you don't need the XML partition definition files.
-- Brian
Click to expand...
Click to collapse
askermk2000 said:
Apparently you don't have to. With QFIL you can fetch the partition table automatically from the phone, and manually select each partition to flash. Kind of like LGUP.
Here's a demonstration video: https://www.youtube.com/watch?v=gwMpDXPQLo8
It's by that aaya888 guy. Someone told me he "bought" firehoses from lg factory, and that he can unbrick H918, but he never replied to my inquiries.
Anyway that method above should work if the firehose works.
Click to expand...
Click to collapse
runningnak3d said:
Here you go...
So, good news, and bad news. I hadn't looked at this thing in a while -- so I figured I would take one more look now that I have a far greater understanding of Quallcomm security.
It turns out this is NOT a debug firehose -- it is perfectly normal firehose that can be used to rescue any v20 (except the H918 -- RSA mismatch, and LS997 (if it is ARB 1) -- this is an ARB0 firehose) with zero side effects.
Now the bad news.... because it isn't a debug firehose, you can't use it to change the boot LUN, so you will have to completely reflash your device. Well, you don't have to, but it is just as easy to make the files for a single partition as it is for the entire device.
Now the really bad news. This is just the programmer -- you are still going to need partition layout XML files, and I don't have time to make them for you.
-- Brian
Click to expand...
Click to collapse
Finally, I restored my V20 H990DS, thanks to Brian and askermk2000 for sharing the right firehose and the tutorial.
Really, I love my V20, and restoring it through your help...made my day
Cheers to Both!!!:good::good::good::good::good::good::highfive::highfive::highfive::highfive::highfive:
DroneJC said:
Finally, I restored my V20 H990DS, thanks to Brian and askermk2000 for sharing the right firehose and the tutorial.
Really, I love my V20, and restoring it through your help...made my day
Cheers to Both!!!:good::good::good::good::good::good::highfive::highfive::highfive::highfive::highfive:
Click to expand...
Click to collapse
Thank you for verifying that all ARB 0 v20s (except the H918) are now unbrickable. Even if you mess up your phone so bad that it won't go into 9008 mode, we now have the test points.
I will be genning up the XML files that are needed in case someone messes their phone up SO BAD that they blow away the partition tables.
Glad you got your phone back!
-- Brian
RESTORE BRICKED-QDLOADER-9008-LG V20 H990DS, H990N, and other H990 Mobos.
Hi all V20 Owners...
CREDITS: ALL THE POINTS, REFERENCES, LINKS MENTIONED HERE ARE COLLECTION OF THREADS THROUGH WHICH I RESTORED. ALL CREDITS GO TO THE ORIGINAL AUTHORS OF RESPECTIVE THREADS AND DEVELOPERS.
If any one had fiddled with their phone and hard bricked them, here is the solution, which I rtried and Succedded in bringing back my phone.
Scenario: Being impatient for Oreo release for H990DS Indian variant, I have flashed H990N Oreo rom. Then VOLTE did not work. In order to gain that, i tried flashing modem from Nougat rom, then finger print stopped working... Then i flashed aboot, thinking that it would restore any security related issue and my FPR could be restored.
Boom!!! Device did not boot.
Then my research started from this XDA and Google. Found this below thread and tried everything in the order as described.
1. FINDING TEST POINT:
https://www.reddit.com/r/lgv20/comm...mm_9008_test_point/?utm_source=reddit-android
2. FINDING FIRE HOSE FOR V20 8996 SIGNED.
Googled all other forums on net and youtube. It was found that only latest QFIL can program it. But for that I needed firehose file.
Then followed everything on this link....
https://forum.xda-developers.com/v20/how-to/9008-test-t3855777
My special thanks to Brian for sharing the firehose file.....
BUT BE CAREFUL IN SHORTING THE TEST POINTS. ANY LITTLE TOUCH TO DIODES OR CPU HEAT SHIELD BESIDE MAY RENDER BOARD USELESS. I USED COPPER LEAD FROM NETWORK CABLE, WHICH EXACTLY MATCHES THE SPACE AND SHORT POINTS.
I know little knowledge on it so tried it.
Once again....I thank everyone who helped me to restore my Fav Phone...and Good Luck to all who would try this!!!!
I am getting hopeful about my download mode - stuck H910PR with "unknown device" error on patched LGUP.
I'd love to get my phone back up and running like a normal again. Is there a way out yet? I still have the v20... I even ordered AT&T board for it but that came with its own antenna connectors and has no service for GSM/3G/4G.
I stuck with no cellular H910 board or download-mode-stuck H910PR board. If there is a clear guide on how to do things to recover the H910PR board back up and running I'll be immensely grateful!
dark_prince said:
I am getting hopeful about my download mode - stuck H910PR with "unknown device" error on patched LGUP.
I'd love to get my phone back up and running like a normal again. Is there a way out yet? I still have the v20... I even ordered AT&T board for it but that came with its own antenna connectors and has no service for GSM/3G/4G.
I stuck with no cellular H910 board or download-mode-stuck H910PR board. If there is a clear guide on how to do things to recover the H910PR board back up and running I'll be immensely grateful!
Click to expand...
Click to collapse
How is your device getting recognised as in the windows device manager??? In ports&LPT, if it is shown as "
AndroidNet USB serial port", then follow this guide...
https://forum.xda-developers.com/v20/how-to/guide-lg-v20-to-life-t3827732
Cus, if LGUP recognises your device as Unknown, then the device must be recognised as above.
Try going through the process, you should be able to succeed.
Ive uploaded signed Qualcomm driver's I found that install on windows and don't turn on test mode. These work. Then afterwards toggle USB options with device plugged in PC ,change from charging to PTP and let it automatically install drivers. Rebooted and opened msm tool and Is connecting and now showing 2 ports. Hope this works for anyone having trouble ; as earlier I had no Qualcomm driver's installed and no ports showing on msm tool after many attempts to install drivers. I'm now ready when something comes along to flash. After rebooting PC use cmd window adb reboot edl. Will then show up on msm tool as connected. When installing Qualcomm driver's choose first option Wwan is not used to get Ip address. If this works for you hit the like button "it's free". I've seen many people complaining they can't connect to msm tool. This fixed my issues. Tested on windows 10 pro
Driver's. https://drive.google.com/file/d/1AOeuMj6D5f6H4yhAC1QKGN437qV9YmJs/view?usp=drivesdk
Mattie69 can you explain how to work the MSMTool to me? It wants a login and i dont understand exactly what to do.
Do these overwrite existing drivers (used for rooting), or just add additional drivers to Windows?
XNine said:
Do these overwrite existing drivers (used for rooting), or just add additional drivers to Windows?
Click to expand...
Click to collapse
No additional driver's need to make Qualcomm devices/one plus phones to connect to msm tool.
illusiveairforce said:
Mattie69 can you explain how to work the MSMTool to me? It wants a login and i dont understand exactly what to do.
Click to expand...
Click to collapse
You don't use the factory one use the one above or below. It's a tool that relocks bootloader and flashes device to original firmware that it was shipped with. It's an anti-brick tool so to speak.
I still cant get it to work. the driver looks to be working and MSM identifying it
but no matter what i do it wont progress. i cant adb reboot because adnb nor fastboot are responsive. the phone just disconnectes and reconnects USB over and over and thats it. no button combo of volume keys and power being held for along time seems to work either.
I finally got it functional and now at "Image does not match" tried on 3 other machines with 3 seperate MSm installs.
9 5G LE2115 is my phone I bought directly form OnePlus. Idk what to do from here.
Usually kicks up that warning if your trying to use the wrong msm tool.?
i tried this one, the one from reddits backup area and the offical one linked to me by the angriest technician alive. it just boots and reboots and reboots. no matter the cable, version, cord. port, usb standard, serial setting or any combination of drivers form signed, unsigned and official, everything always leads to that same error.
its insane. the tech said "i didnt say run that (MSM he linked me) , were not liable to what it did"
I replied with " it didnt flash anything, thats why im contacting you and its qualcomms software, youre the company official making customers download altered /unofficial builds of another companies intellectual property. Im sure theyll be so happy to find out what you are doing"
he just logged after that. The balls on that guy. They Qualcomm didnt incorporate region based logins and VM Protect into MSM because its fun.
So yeah, hopefully i fix it before qualcomm returns my my emails.
applyscience said:
i tried this one, the one from reddits backup area and the offical one linked to me by the angriest technician alive. it just boots and reboots and reboots. no matter the cable, version, cord. port, usb standard, serial setting or any combination of drivers form signed, unsigned and official, everything always leads to that same error.
its insane. the tech said "i didnt say run that (MSM he linked me) , were not liable to what it did"
I replied with " it didnt flash anything, thats why im contacting you and its qualcomms software, youre the company official making customers download altered /unofficial builds of another companies intellectual property. Im sure theyll be so happy to find out what you are doing"
he just logged after that. The balls on that guy. They Qualcomm didnt incorporate region based logins and VM Protect into MSM because its fun.
So yeah, hopefully i fix it before qualcomm returns my my emails.
Click to expand...
Click to collapse
What about that global fastboot rom I linked you to?
mattie_49 said:
What about that global fastboot rom I linked you to?
Click to expand...
Click to collapse
man, sorry super tired. yeah no fastboot at all.no screen activity ever, all i get is usb plug in and out sounds every 3 seconds on my computer.
no fastboot, no adb. nothing.
applyscience said:
man, sorry super tired. yeah no fastboot at all.no screen activity ever, all i get is usb plug in and out sounds every 3 seconds on my computer.
no fastboot, no adb. nothing.
Click to expand...
Click to collapse
You were able to get back from aospa though right? Via msm
mattie_49 said:
You were able to get back from aospa though right? Via msm
Click to expand...
Click to collapse
i always had fastboot access during that, i just was too stupid to extract my own img files form the paylod dumps (theres so many guides online, i just suck with it) anyhow, after you hooked me up with download i just ran the the imgs in a flash-all bat file to clean up both slots of the phone and it was wonderful. as soon as i went to the unofficial lineage my phone just gave up. 2 reboots later.
im not sure what im going to do. its been a long day and not too pleased with myself so im trying to just procrastinate it till tmw or sunday.
[17784][07-04 07:23:08.893]<4> [3] [CSerialCommHelper] No data in buffer to be sent 0
[17784][07-04 07:23:11.061]<4> [3] [SP][195] Check cmd done status failed. 1
this is the 2 lines in the log that have ruined my weekend.
I'm investigating possible solutions to common MSM errors that prevent flashing.
See the following thread and feel free to try the steps outlined if you're brave enough.
Please report back your findings.
[ADVANCED] [UNTESTED] Possible Fix - MSM Errors (Sahara, Param info, etc)
WARNING: THE FOLLOWING IS FOR INFORMATIONAL PURPOSES ONLY AND MAY FURTHER DAMAGE YOUR DEVICE. EXERCISE EXTREME CAUTION. USE ONLY AS A LAST RESORT. This was tested with a Global OnePlus 9 LE2115 Overview So I was encountering an error with MSM...
forum.xda-developers.com
Can you re-up these? I'm getting a 404 on the google drive link.
Ethanadams642 said:
Can you re-up these? I'm getting a 404 on the google drive link.
Click to expand...
Click to collapse
Index of /list/Unbrick_Tools
I was following a guide on unlocking the bootloader and rooting my v450 device, this was using QFIL to load the abl_a and abl_b files but made a mistake and accidentally loaded the file to the MPT partition on the device. I made a backup of the abl_a partition but not of any other partitions.
Now the device gets stuck on the LG V50 boot screen and I can't get it to boot into any mode other than EFL.
One way I feel might work is by obtaining a backup of the MPT file, if this is correct does anyone know where I can find this,
Does anyone know whether this is something I can fix or if the phone is dead, any help is appreciated.
Thanks.
The phone is not necessarily dead!
Search google for your models QFIL dump, I found someone has uploaded a set of files for the Sprint 450. Download all, or the file you need and write using QFIL. I would download all and replace with all. Just in case there is a miss-match across versions, for example you might have one date version of boot and a different one for the MPT.
It is very difficult to fully break any android phone, time and effort will find you a solution. I broke mine for a short time trying to do the same process and ultimately fixed by trying a whole bunch of troubleshooting before I found what I needed to do.
In your case if you can find a set of files online and write each partition one by one, I think you will be good. Of course you will have to restart the whole process of bootloader changes if you want that.
Good luck
feyd2blak said:
The phone is not necessarily dead!
Search google for your models QFIL dump, I found someone has uploaded a set of files for the Sprint 450. Download all, or the file you need and write using QFIL. I would download all and replace with all. Just in case there is a miss-match across versions, for example you might have one date version of boot and a different one for the MPT.
It is very difficult to fully break any android phone, time and effort will find you a solution. I broke mine for a short time trying to do the same process and ultimately fixed by trying a whole bunch of troubleshooting before I found what I needed to do.
In your case if you can find a set of files online and write each partition one by one, I think you will be good. Of course you will have to restart the whole process of bootloader changes if you want that.
Good luck
Click to expand...
Click to collapse
Thank you man, this is reassuring to hear, I'm going to look for a QFIL dump now, will update this post if I find any success.
T
feyd2blak said:
The phone is not necessarily dead!
Search google for your models QFIL dump, I found someone has uploaded a set of files for the Sprint 450. Download all, or the file you need and write using QFIL. I would download all and replace with all. Just in case there is a miss-match across versions, for example you might have one date version of boot and a different one for the MPT.
It is very difficult to fully break any android phone, time and effort will find you a solution. I broke mine for a short time trying to do the same process and ultimately fixed by trying a whole bunch of troubleshooting before I found what I needed to do.
In your case if you can find a set of files online and write each partition one by one, I think you will be good. Of course you will have to restart the whole process of bootloader changes if you want that.
Good luck
Click to expand...
Click to collapse
This worked, I manually replaced every partition and the phone is working now. thank you so much, I probably wouldn't have tried this without the info you provided.
link to dump used: https://drive.google.com/file/d/13AJ8SnKmpOrTQF2EQ1odJK7-4qfUTIdF/view
doublespicc said:
T
This worked, I manually replaced every partition and the phone is working now. thank you so much, I probably wouldn't have tried this without the info you provided.
link to dump used: https://drive.google.com/file/d/13AJ8SnKmpOrTQF2EQ1odJK7-4qfUTIdF/view
Click to expand...
Click to collapse
Glad I could help!
Tell me, in the dump that is uploaded there are files rawprogram0.xml, rawprogram1.xml, etc. How to flash them?