Related
I have spent litterally all day trying to update my mrs g3 d855 and i have had no luck, how much of it because my computer i dont know. Im running a chromebook with a full linux distro gallumos installed, got virtual box running 32 bit windows 7. Android sdk, adb etc and got lg drivers installed to recognise the device in its various states, ptp, mtp, download. all that is working. got the official lg mobile support tool and the lg 2014 flash tool.
the problem im having is neither of these will update the phone, if i try to manaully flash the kdz using the flashtool or updating using the official one, it wont update recover either. if i try different region or enter the imei number it always fails at 4%. Iv tried different usb cables, different ports, the phone was at 100% battery the whole time, the laptop was on charge the whole time. I really dont know what else to do, i have no access to another windows machine here and its the mrs phone and she wouldnt want me to take it to work to try on another pc there. As i said earlier the drivers all seem installed correctly, the firmware downloads and extracts as it should but I really am at the point i dont know what else to try
Hello,
Did you try LGUP method? Link is here.
It's easy to use. All you need is there, try it and reply
Just TIP: Do you really have correct drivers for download mode? If LGUP see you device as "unknown", change your COM port to #41
Do "FULL WIPE AND INSTALL MM"
I think I might of, how ever before work I did download a version of lg up and some kind of other installer for it. I also got a kdz file to try and flash. The drivers should all be fine, it gets recognised in all the various modes. My fiance is on nights this week, the soonest il be able to try again is tomorrow so I will let you know it goes. Thank you for replying
The Gingerbread Man said:
I think I might of, how ever before work I did download a version of lg up and some kind of other installer for it. I also got a kdz file to try and flash. The drivers should all be fine, it gets recognised in all the various modes. My fiance is on nights this week, the soonest il be able to try again is tomorrow so I will let you know it goes. Thank you for replying
Click to expand...
Click to collapse
You can send me a PM, or just reply to this thread.
It's a common problem with various solutions. We will look at it.
halekhonza said:
You can send me a PM, or just reply to this thread.
It's a common problem with various solutions. We will look at it.
Click to expand...
Click to collapse
Thanks buddy il let you know after I can try it again. If it was a Nexus it would be fine, I know all about fastboot, unlocking bootloaders and rooting and stuff for the Nexus line. So much easier to work with
So I think I might know where I'm going wrong, i thought I had all the drivers set up but there's one I missed, for download mode
Under device manager I see when the phone is turned on with adb on
Android device- lge mobile adb interface-google Inc 4.0.0.0-working properly
Portable devices-g3-lg electronics 4.0.0.0-working properly
Ports (com & lot)-lg mobile USB serial port (com 4)-lg electronics 4.0.0.0-working properly
In download mode device manager
android device isn't there, no adb which is fair enough
Portable devices-g3 with yellow warning triangle-lg electronics 4.0.0.0- the device cannot start code 10
Ports (com & lot)-lg mobile USB serial port (com 4)-lg electronics 4.0.0.0-working properly
So I need to trouble shoot why the device cannot start. I have downloaded 2 packs of Lg drivers, lg united mobile driver & lg mobile driver. Both of which contain loads of drivers inside.
If I guide windows into either of the folders it won't install any new drivers giving an error saying that the driver software is already up to date.
I'm going to Google to find out what's going on with device cannot start error, if I'm missing something obvious please jump in
Can you please post complete screenshot with windows device manager (with open ports menu) and adb console with command "adb devices" ?
In your chromebook, do you have disabled all USB power saving bull****s? Also check VM software to see if there is such a possibility to enable/disable USB power plans.
At least, sorry for my bad english Still a lot of things to learn.
Your English is fine I understand perfectly, in fact I wouldn't of guessed it's not your native language so don't worry! Iv taken photos of my screen. You will see when the phone is turned on normally the host and client can both see the device and adb shows the device is detected and returns the serial number, all good there. The last photos shows when it's in download mode and that the driver isn't working properly, it can not start the device with a code 10 error. If I can fix that I know the lgup programming will run. The problem is because the PC can't communicate with the PC in download mode because of some driver issue.
I'm going to have to carry on tomorrow as I have to go to work and the Mrs needs her phone here while she sleeps
The Gingerbread Man said:
Your English is fine I understand perfectly, in fact I wouldn't of guessed it's not your native language so don't worry! Iv taken photos of my screen. You will see when the phone is turned on normally the host and client can both see the device and adb shows the device is detected and returns the serial number, all good there. The last photos shows when it's in download mode and that the driver isn't working properly, it can not start the device with a code 10 error. If I can fix that I know the lgup programming will run. The problem is because the PC can't communicate with the PC in download mode because of some driver issue.
I'm going to have to carry on tomorrow as I have to go to work and the Mrs needs her phone here while she sleeps
Click to expand...
Click to collapse
Please, enter download mode and change in Windows COM port from #3 to #41 and try LGUP method . It's up to you what method (upgrade, full wipe) you choose.
OK sounds straight forward enough. As I say il have to try tomorrow as I'm at work now and left the Mrs with her phone at home asleep, she will be working night shift so it will have to be when she is back home. I really appreciate the help and il post again to update how I get on
Where I am now is no further, iv tried changing the port to 41 through device manager. Iv set the port 0041 in virtual box for USB settings. Iv tried several sets of drivers. What keeps happening no matter which set of drivers I use when the phone goes into download mode mtp stops working and stops the phone communicating with the PC. When I restart it will work normally for a while but go wrong again. If I try lg up and starting the upgrade in download mode it gives me an error saying it can't change to download mode if I choose refurbish or upgrade. Lg PC suite just hangs at 0% and returns an error after a while. The 2014 flash tool will get as far as trying to flash but hangs at 4% and returns an error but doesn't specify what. I really don't know what else I can do. When these programs reboot the device into download mode it disconnects the device from the virtual machine and I can't get it connected again quick enough before errors are returned or mtp stops working which requires me to reboot the VM or phone. The only thing I can think to do is try on another machine. If it was my phone I would of thrown it out the window or under a bus. Lg software is unusable through virtual machines and I am not buying a new PC just for this lol Il see if I can use someone else's. I hate being defeated, iv have spent probably some 16 hours and got no where! Why can't they just release an ota? It only strengthens my belief in nexus and fastboot. Sorry for the rant but this really has got under my skin and I don't like giving in
Edit
I'm just as annoyed with windows as lg at this point. I really don't like using it. Grrrr
Hello friends!
New registered user here but have already read tons of threads regarding G3 troubleshooting. Anyway, have decided to post this problem and if a similar situation has already been posted (and solved), please provide link.
For some strange reason, my G3 have decided to stay in the LG logo (I understand that this is the so-called boot-loop). This happened when the phone suddenly restarted while watching a YT vid and the battery still at 30%++. The phone just keeps on restarting until such a time that it never got pass the LG logo.
Here are the things that I have already tried to no avail:
1. Enter Hard Reset page via hardware keys (Power + Vol Up buttons). Have chosen "Yes" to hard reset device but alas, it never got pass the LG logo.
2. Downloaded PC suite, KDZ flashtool, and LGUP. Installed all three software. Connected G3 to PC and entered download mode (Vol Down while inserting USB cable). Unfortunately, unable to fully use either of the three software since the PC cannot detect G3.
Number 2 is quite strange since I have downloaded and installed all G3 drivers. This I know since a friend of mine who owns a working G3 unit was detected by the computer and can sync with the PC suite.
For some strange reason, everytime I connect my broken G3 to the computer, it is not detected by the PC and was not even listed in the device manager.
Any help and advise would be highly appreciated
I already downloaded all necessary tools (KDZ, LGUP, and flashtool) to flash the ROM but I need the PC to see the G3 unit to be able to do so.
By the way, before the bootloop scenario: the debugging (or is it developer?) options are disabled and I'm not sure if the bootloader is locked or unlocked.
I hope all this info is of any use.
Thanks a lot in advance
Have you tried simpler solutions first? Like, trying another USB ? Or another USB port from your pc? This maybe hardware related rather than software. You should try that before anything else. (Maybe you did?)
neyvermore said:
Have you tried simpler solutions first? Like, trying another USB ? Or another USB port from your pc? This maybe hardware related rather than software. You should try that before anything else. (Maybe you did?)
Click to expand...
Click to collapse
Thanks for the reply. Yup, have done those. Tried a different cable, different USB port, and borrowed a working G3 unit. The good G3 unit was detected by the PC but when I connect my broken G3 (same cable and same USB port), the PC does not detect it (not even listed in device manager).
Because of this hurdle, I couldn't flash with LGUP (it states no handset was connected). The KDZ flashtool basically says the same message.
By the way, my debugging options are disabled before this whole problem started. Could that be a reason why the PC won't detect the unit?
Hello guys,
I'm using my 3T carefully as a media device just at home. But suddenly I couldn't control my system anymore. I could swipe and open settings, but couldn't turn on WiFi or start any app. So I restarted my phone but it never booted. Screen is completely black and even charging leds doesn't work anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect my phone to my computer windows plays the typical sound like when you plug in an USB stick. Windows sayed once that the connected device is buggy and cannot be detected. Nothing more. When I reconnect no more message or pop up again.
Has anyone any idea? Thanks a lot!
slev!n said:
Hello guys,
Screen unit is completely dead. It even doesn't show a charging led anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect to the computer windows registers my phone by playing the 'connected sound'. But nothing more. Has anyone any idea or know where I can discuss my issue? Thanks a lot!
Click to expand...
Click to collapse
That's weird. Sounds like your screen (if not more parts) died. Hardware issue? Water damage? Might be better to contact a repair center since if you can't even access recovery I doubt the problem is related to LOS. Never happened on my 3T over the 4 years I've had it, though it's had its fair share of damage.
knpk13 said:
That's weird. Sounds like your screen (if not more parts) died. Hardware issue? Water damage? Might be better to contact a repair center since if you can't even access recovery I doubt the problem is related to LOS. Never happened on my 3T over the 4 years I've had it, though it's had its fair share of damage.
Click to expand...
Click to collapse
But before my restart I could use the screen it just looks like something in the system doesn't work: could type on apps and settings, it just doesn't open or pop back. And the charging led is not part of the screen unit as I know.... If I could take out the battery I would do it. It often works in other phones. But I don't have tools here for my 3T. :/
knpk13 said:
That's weird. Sounds like your screen (if not more parts) died. Hardware issue? Water damage? Might be better to contact a repair center since if you can't even access recovery I doubt the problem is related to LOS. Never happened on my 3T over the 4 years I've had it, though it's had its fair share of damage.
Click to expand...
Click to collapse
slev!n said:
But before my restart I could use the screen it just looks like something in the system doesn't work: could type on apps and settings, it just doesn't open or pop back. And the charging led is not part of the screen unit as I know.... If I could take out the battery I would do it. It often works in other phones. But I don't have tools here for my 3T. :/
Click to expand...
Click to collapse
slev!n said:
Hello guys,
I've got an issue and don't know if it belongs to the build or not. I'm on the last build with my 3T and today after charging my phone I couldn't turn on WiFi or start any app. It just didn't open. So I restated my phone but it never booted. Screen unit is completely dead. It even doesn't show a charging led anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect to the computer windows registers my phone by playing the 'connected sound'. But nothing more. Has anyone any idea or know where I can discuss my issue? Thanks a lot!
Click to expand...
Click to collapse
Sounds to me like an hardware error involving (but not necessarily limited to) emmc access. That would explain, why the parts still in ram (like homescreen) were still working but apps won't start anymore, as well as the blank screen on device startup (even the logo needs emmc access to read the logo partition).
Try unbricking (I'm afraid your pc won't find the device, if my guess is correct), if that fails: rma or repair center.
slev!n said:
Has anyone any idea or know where I can discuss my issue? Thanks a lot!
Click to expand...
Click to collapse
here
You need to be more spesific about the connected sounds, does it shows up on device manager or else, in detail (with SS/photos etc to prevent misjudge)
150208 said:
here
You need to be more spesific about the connected sounds, does it shows up on device manager or else, in detail (with SS/photos etc to prevent misjudge)
Click to expand...
Click to collapse
Thanks, I'll create a post there. Just one more post here:
I used this phone just carefully at home as a media device. So this brick came totally out of nowhere. When I connect my bricked 3T now to my computer it makes the typical sound like when you plug in an USB stick. Windows sayed once that the connected device is buggy and cannot be detected. Nothing more. When I reconnect no more pop up again.
slev!n said:
I'll create a post there.
Click to expand...
Click to collapse
When you've created that post ask the moderators to move this complete conversation from this thread to the newly created on in the help forum, please. This helps to keep this thread readable and searcheble.
For your trouble: if you can't boot rom, recovery nor fastboot mode, it doesn't make sense to debug the usb connection: what should the pc connect to if none of the three is bootable? There is just nothing up to connect to. That's why I recommended unbrick tool - if that fails rma or go to a repair center.
Hello guys,
I'm using my 3T carefully as a media device just at home. But suddenly I couldn't control my system anymore. I could swipe and open settings, but couldn't turn on WiFi or start any app. So I restarted my phone but it never booted. Screen is completely black and even charging leds doesn't work anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect my phone to my computer windows plays the typical sound like when you plug in an USB stick. Windows sayed once that the connected device is buggy and cannot be detected. Nothing more. When I reconnect no more message or pop up again.
Has anyone any idea? Thanks a lot!
Post SS of the device manager after connecting the phone to the PC
150208 said:
Post SS of the device manager after connecting the phone to the PC
Click to expand...
Click to collapse
It doesn't make sense to debug the pc conmection: if neither recovery, fastboot mode nor rom is bootable, there is nothing up and running the pc can connect to (maybe unbrick tool can still access the msm hardware directly, but that's not sure - confirmation is still missing from @slev!n). I'm writing this the second time.
If none of recovery, fastboot mode nor rom is bootable, the last resource before rma or repair center is unbrick tool. I'm writing this the third time!
@slev!n: please ask the moderators to move the existing conversation to thos from the los16 thread here. If all postings have moved, ask the moderators to move this thread from op3/help to op3t/help.
@nvertigo67 I wanted to do so and was searching how to contact moderators but couldn't find it in my XDA app. Maybe someone can give me a hint? I'm kind of new on xda... Thanks!
@150208 And as I wrote: it's not possible to get any kind of message on windows anymore. Just the sound appears when I connect and disconnect.
@nvertigo67 I was also following your advice to use the unbrick tool. I followed the steps on oneplus forum:
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/
When it comes to the integrity check windows doesn't accept "TESTSIGNING ON". And so windows doesn't recognise my phone in the device manager for the next steps.
And I guess RMA or repair centres are super expensive. I don't know if it's worth it? I thought about buying a device with a broken screen on eBay and try to change the motherboard...
Log in with a web browser locate each posting of the comversation. For each posting in question use the little triangle icon at the botom on the left side, report each posting, set non-urgent and pit the link of this thread together with something like "Please move this posting to the linked thread, thanx in advance".
For disabling driver signature enforcement try method 2. from this post: http://maxedtech.com/about-testmode/
Most of tbe time xda postings are more reliable and more current then the Oneplus forums: https://forum.xda-developers.com/oneplus-3/how-to/op3-collection-unbrick-tools-t3896722, https://forum.xda-developers.com/oneplus-3/how-to/op3-collection-unbrick-tools-t3896722
slev!n said:
[MENTION=4405529]i thought about buying a device with a broken screen on eBay and try to change the motherboard...
Click to expand...
Click to collapse
If you already have a thought why do you keep asked here though? If you want another possible solution, at least put an effort to provide the information needed when asked by the one who tried to help you
I'm not into a guessing games, so i'm out
nvertigo67 said:
It doesn't make sense to debug the pc conmection: if neither recovery, fastboot mode nor rom is bootable, there is nothing up and running the pc can connect to (maybe unbrick tool can still access the msm hardware directly, but that's not sure - confirmation is still missing from @slev!n). I'm writing this the second time.
If none of recovery, fastboot mode nor rom is bootable, the last resource before rma or repair center is unbrick tool. I'm writing this the third time!
Click to expand...
Click to collapse
There are 2 possible reason when the phone is not detected by the computer, driver or hw problem.
To know it i need to look at the device manager status
If it's hw problem, i'll try not to jump on MB conclussion yet, since there are still another possible reason
When talking about MSM, you need to make sure it's available first on the device manager
Otherwise, it's a waste of data for downloading the tool in these human malware days
Oh yes, the msm guide is quite lag behind. You don't need to boot into test mode anymore with the current driver for qualcomm
I flashed a lot qualcomm devices with w10 without the need to boot into test mode
150208 said:
There are 2 possible reason when the phone is not detected by the computer, driver or hw problem.
To know it i need to look at the device manager status
Click to expand...
Click to collapse
True, if only "win is not detecting the device" is known. Since we know much more (neither rom, recovery nor fastboot mode are bootable), the debugging of the usb driver doesn't make sense. The msm tool uses it's own drivers to detect the hardware BEFORE one of the three is booted. If the msm tool has unbricked the device and booting recovery, rom and/or fastboot, you can start debugging the "nprmal" qc usb drivers, if still necessary.
For the costs of rma: maybe it's expensive - maybe oneplus will be obliging... Since you don't relay on the device as your daily driver, you can ask for an estimate of costs - so you can decide if it's worth the costs.
nvertigo67 said:
True, if only "win is not detecting the device" is known. Since we know much more (neither rom, recovery nor fastboot mode are bootable), the debugging of the usb driver doesn't make sense. The msm tool uses it's own drivers to detect the hardware BEFORE one of the three is booted. If the msm tool has unbricked the device and booting recovery, rom and/or fastboot, you can start debugging the "nprmal" qc usb drivers, if still necessary.
Click to expand...
Click to collapse
Wait, I fail to see your explanation in line with mine. I want to start debug it on the windows side, but you seems to see it on the phone side.
Do you realize there are cases where everything is black/nothing responding but it's still detected by computer? That when emmc is corrupt, but repairable if you format it.
150208 said:
Do you realize there are cases where everything is black/nothing responding but it's still detected by computer? That when emmc is corrupt, but repairable if you format it.
Click to expand...
Click to collapse
If neither fastboot mode nor recovery is bootable, you need the msm interface to refprmat somethimg on emmc. In other words: if there's no recovery nor fastboot, you can't utilize adb or fastboot to reformat or to fix the partition table. You need something to connect to to do the fixing, but without recovery or fastboot, there is nothing adb or fastboot can conmect to, no matter of the driver status on the pc/win side. Once this is fixed (at least fastboot mode is up again) you can utilize the "normal" usb connection again.
What do you want to do with the usb connection, if neither fastboot mode nor recovery is up amd running? What is your suggested next step, if the device is recognized? What should the pc recognize if neither fastboot nor adb os an option? Which command or procedure will fix the emmc?
nvertigo67 said:
If neither fastboot mode nor recovery is bootable, you need the msm interface to refprmat somethimg on emmc.
Click to expand...
Click to collapse
Yes, there are other tools but i'm not gonna bother since it's paid
nvertigo67 said:
In other words: if there's no recovery nor fastboot, you can't utilize adb or fastboot to reformat or to fix the partition table. You need something to connect to to do the fixing, but without recovery or fastboot, there is nothing adb or fastboot can conmect to, no matter of the driver status on the pc/win side.
Click to expand...
Click to collapse
This is the part where you're incorrect. There are 4 status when a device plugged into the pc.
1. detected and driver is loaded
2. detected and driver isn't loaded
3. detected but not recognized
4. no sign at all
1 and 2 is sw problem, 3 and 4 is hw problem
In order for MSM to do it's job, you need to have either problem no 1 or 2 with qualcomm qloader 9008 driver already or later detected in devmanager
So it's important to know the driver status
OP states there was sounds coming then nothing, which mean it's either 2 or 3, more like 3 but again i repeating myself i don't like guessing games
I don't understand the part why you're explaining/asking about fastboot recovery or etc, his phone is on dead state, nothing-literally-no sign of life unless he plug it to the pc and then it making sounds for the first time,
Why do you even bother thinking about it?
nvertigo67 said:
Which command or procedure will fix the emmc?
Click to expand...
Click to collapse
No procedure will fixed his phone since there are no enough information
I think your other question should be already answered. If else, i don't know what to say anymore.
150208 said:
nvertigo67 said:
In other words: if there's no recovery nor fastboot, you can't utilize adb or fastboot to reformat or to fix the partition table. You need something to connect to to do the fixing, but without recovery or fastboot, there is nothing adb or fastboot can conmect to, no matter of the driver status on the pc/win side.
Click to expand...
Click to collapse
This is the part where you're incorrect.
Click to expand...
Click to collapse
If so, please explain how you can format a partition or fix the partition table if neither fastboot mode nor recovery (or a rooted system for that matter) is bootable.
@slev!n: please give a screenshot of the device manager to @150208. I'm too curious to learn how to fix a broken emmc without recovery nor fastboot mode.
Thank you so far!
I dont want to bother someone. Just thinking about further options thats why I wrote my thought about replacing the motherboard down.
I 'm in test mode now and I did this:
"Step 4 :- Press the power button for 40 seconds to turn off the phone.
Step 5 :- Press only volume up button for a few seconds and while keeping it pressed,connect your phone to PC.Keep volume up pressed till your device shows in device manager as [Unknown Device,QHUSB_BULK (under Unknown Devices) or Qualcomm HS USB (under COMs and Ports)]."
But no device is listet in my device manager. But in msmtool my phone is connected. Does it mean I cann't continue with this tool somehow?
slev!n said:
But no device is listet in my device manager. But in msmtool my phone is connected. Does it mean I cann't continue with this tool somehow?
Click to expand...
Click to collapse
The pic is from msm tool, not the device manager. No unknown device in device manager?
Having searched far and wide for a solution for my problem (and stumbling across the fact that it is great that the ZUK Z2 is really not brickable) I wonder if there is not one...?
I was simply attempting to flash the Lineage rom (coming from AEX) but kepy getting an Error 7 (if I remember correctly), which is apparently fairly common, but for which none of the proposed solutions was working for me.
It was suggested to carry out a FULL WIPE (so I did this, including internal storage).
I then installed an alternative recovery mode to TWRP (the current one), without actually removing TWRP...so possible conflict here...?
So:
There is currently no OS on phone
I can open my phone in fastboot mode
Impossible to open recovery mode (which is the real killer)
Impossible to get phone recognised as external drive (and hence modify what is on it) - I can get it recognised by the device manager but only as QL.... not my actual phone
Impossible to communicate with phone through adb (logic, since phone not recognised
Since I cannot communicate with the phone in any way OR get the phone into recovery mode, my hands are tied as I see it...I really don't know what can be done from here :crying:
If anyone has any idea of how my phone could be saved, your help would be VERY MUCH appreciated
Thank you in advance for any feedback at all.
Charlie
chazhammer said:
Having searched far and wide for a solution for my problem (and stumbling across the fact that it is great that the ZUK Z2 is really not brickable) I wonder if there is not one...?
I was simply attempting to flash the Lineage rom (coming from AEX) but kepy getting an Error 7 (if I remember correctly), which is apparently fairly common, but for which none of the proposed solutions was working for me.
It was suggested to carry out a FULL WIPE (so I did this, including internal storage).
I then installed an alternative recovery mode to TWRP (the current one), without actually removing TWRP...so possible conflict here...?
So:
There is currently no OS on phone
I can open my phone in fastboot mode
Impossible to open recovery mode (which is the real killer)
Impossible to get phone recognised as external drive (and hence modify what is on it) - I can get it recognised by the device manager but only as QL.... not my actual phone
Impossible to communicate with phone through adb (logic, since phone not recognised
Since I cannot communicate with the phone in any way OR get the phone into recovery mode, my hands are tied as I see it...I really don't know what can be done from here :crying:
If anyone has any idea of how my phone could be saved, your help would be VERY MUCH appreciated
Thank you in advance for any feedback at all.
Charlie
Click to expand...
Click to collapse
Which recovery comes when you choose recovery option when you choose recovery by pressing start when phone is powering on before zuk logo..
You can use cable method (by shorting cable and going to edl mode) and qpst to safety.
sanjay.2704 said:
Which recovery comes when you choose recovery option when you choose recovery by pressing start when phone is powering on before zuk logo..
You can use cable method (by shorting cable and going to edl mode) and qpst to safety.
Click to expand...
Click to collapse
Thank you very much for your suggestion, Sanjay, it is very much appreciated :good:
When I choose recovery, everything just "hangs" - black screen that doesn't go anywhere (that's why I thought that maybe there was some kind of conflict, where the phone didn't know how to chose between the two options perhaps (pure specuclation!)
I have tried the solution you suggest, but it didn't work for me.
I will re-attempt this an extra ten times or so (you never know) just in case, and let you know how things go.
This one:
(https://forum.xda-developers.com/lenovo-zuk-z2/how-to/reboot-to-edl9008-modetotally-bricked-t3720932)
OK, so still no luck...
I used a method to use some tinfoil in the usb to get the device recognised in the device manager - it appears as => Android Device >> ShenQi Composite ADB Interface
The phone is in fastboot mode at this stage.
However, in ADB still no recognition of the phone
When entering "adb devices" I get "List of devices attached" and then blank
If I try "fastboot oem edl" I get < waiting for device >
"Adb reboot edl" gives me => "error: device not found"d
So essentially it still comes down to the fact that my device is not detected...although strangely there are signs of life in device manager (although I don't know what ShenQi Composite ADB Interface refers to ???)
Alternatively I see that it is possible to actually buy an EDL cable from China or something (https://www.magnetforensics.com/blog/qualcomm-phone-edl-mode/)
This appears to be restricted to other devices, but similar issue:
https://www.xda-developers.com/exploit-qualcomm-edl-xiaomi-oneplus-nokia/
Other devices can also use what’s known as a “deep flash” cable, which is a special cable with certain pins shorted to tell the system to instead boot into EDL mode. Old Xiaomi devices can utilize this method, along with the Nokia 5 and Nokia 6. Other devices will also boot into EDL mode when they fail to verify the SBL.
Does anyone know if this would actually work with an EDL cable approach???
Any other ideas out there?
I'd be willing to give someone some money if they were able to work through this issue with me, if they think that there is a solution here..else the phone is just spare parts :-/
Thank you in advance,
Charlie
For a little added information, the other recovery was: TWRP Red Wolf
(https://zukfans.eu/community/thread...r-image-error-7-installing-a-custom-rom.8347/)
While flashing this with TWRP there was an option to flash to.... I don't remember the options and can no longer consult to check, BUT at 2am, about to give up, and not knowing exactly what to select, I selected about 3 options at this stage
I believe there were something like 5 options and I selected "boot" I think, plus..?
Very stupid of course and obviously I was too confident in not creating a problem that couldn't be solved!
I have been playing around with flashing ROMs etc for the last 10 years, over 3/4 different devices and despite having read all the warnings, since over this time I have never had any issues, I kind of considered it to be almost impossible to get into a situation where things are irretrievable...so my comuppance :-/
Again, if anyone has any ideas, I would greatly appreciate
chazhammer said:
OK, so still no luck...
I used a method to use some tinfoil in the usb to get the device recognised in the device manager - it appears as => Android Device >> ShenQi Composite ADB Interface
The phone is in fastboot mode at this stage.
However, in ADB still no recognition of the phone
When entering "adb devices" I get "List of devices attached" and then blank
If I try "fastboot oem edl" I get < waiting for device >
"Adb reboot edl" gives me => "error: device not found"d
So essentially it still comes down to the fact that my device is not detected...although strangely there are signs of life in device manager (although I don't know what ShenQi Composite ADB Interface refers to ???)
Alternatively I see that it is possible to actually buy an EDL cable from China or something (https://www.magnetforensics.com/blog/qualcomm-phone-edl-mode/)
This appears to be restricted to other devices, but similar issue:
https://www.xda-developers.com/exploit-qualcomm-edl-xiaomi-oneplus-nokia/
Other devices can also use what’s known as a “deep flash” cable, which is a special cable with certain pins shorted to tell the system to instead boot into EDL mode. Old Xiaomi devices can utilize this method, along with the Nokia 5 and Nokia 6. Other devices will also boot into EDL mode when they fail to verify the SBL.
Does anyone know if this would actually work with an EDL cable approach???
Any other ideas out there?
I'd be willing to give someone some money if they were able to work through this issue with me, if they think that there is a solution here..else the phone is just spare parts :-/
Thank you in advance,
Charlie
Click to expand...
Click to collapse
Edl cable approach would work for you.. Here is the thread guide for you..
https://forum.xda-developers.com/lenovo-zuk-z2/how-to/deep-flash-revive-zuk-z2-hard-brick-t3577146..
Also I would suggest to stick to official twrp as that's more stable as compared to redwolf..
Hit thanks if it helps.
Thank you again Sanjay.
I have ordered a new lead (to cut open and attempt this intervention)!
I will let you know how I get on.
OK, I have done the cable trick and PORTS shows up in the device manager as "Qualcomm HS-USB QDLoader 9008 (COM5)", which seems to correspond with what was needed.
What should I do next exactly ?
The phone no longer actually shows any signs of life - I hope this is normal
chazhammer said:
OK, I have done the cable trick and PORTS shows up in the device manager as "Qualcomm HS-USB QDLoader 9008 (COM5)", which seems to correspond with what was needed.
What should I do next exactly ?
The phone no longer actually shows any signs of life - I hope this is normal
Click to expand...
Click to collapse
You can go ahead with qfil now.. You should see same port in qfil as well.
Once qpst is completed phone should boot up..
After some issues with the Sahara error (needed to update to edl mode and press download immediately) I finally managed to flash back to stock ROM
Thank you for all of your help!!!
Hello, and thanks in advance for for everyone's help (and patience if my post exasperates). This is my 4th OP phone and i've come to rely on MSM heavily as i tend to overflash ROMs etc. Although i've had issues (always evenutally resolved) in the past with getting MSM to restore, this is the first time i feel truly stymied. While playing around with TWRP i ended up having one of the A/B slots seemingly unrecoverable. Even during MSM it would get stuck on DSP.img. I eventually got fastboot to manually write that partition and i thought all was well. However during a flash of a custom ROM the phone crashed (i think t was an external event rather than related to my previous issues) in any event since that point the phone seems to be hard bricked. I can't get to the bootloader or the screen to come on at all. When plugged into Win 10 it is recognized and i can QDLoader 9008 to show up in the device manager. It even starts to work on MSM showing as connected when hitting enum. However after the initial "firehose download" it times out after 18-20 seconds. By unplug/replug etc i can sometimes get it go a bit father but then it stops at Param preload and will go no further.
Thoughts? Questions or detail i missed to help you help me?
re install the driver from device manager try dif port and cable.............
make sure no av shutting it down and good luck!
let me stress try a DIFFERENT PORT AND A DIFFERENT CABLE dunno how many times i can say that even if you got 3 cables go get a new one to rule it out also press hold power up 30 sec before you press hold to get in firehose
Install this on your pc Here. Add your device, use 8 PRO since 9 Pro isn't listed. Choose boot to EDL, and run MSM once your phone in EDL
Click the box to use lite firehose, then enum until it says connected, then start.
You said windows recognized it and so did msm
But I still gotta ask
Did you do the driver verification removal on the windows 10?
Also is it the right msm version/oos?
Use the original USB calbe, better if its a USB C TO A not to C as the C controllers on pcs are kind of weird with these kinda situations.
If you are using the same windows and drivers that worked on your old phones (Haven't formatted or uninstalled the drivers since) then nothing to be done here, but you have try to installing them with windows driver signature turned off. (Qualcomm drivers and oneplus drivers)
make sure the phone booted to EDL too.
These will solve 99% of msmtools problems usually.
try this