I will literally pay someone to help me out here at this point.
I have been trying to unbrick my device for the past 2 days now, I have no access to Fastboot or the Recovery mode, just EDL mode. I have been trying to use MSM to unbrick the device. I have tried every version of MSM (EU, Global and India), my version of the phone is EU, I have tried multiple different variants of the Qualcomm driver, none have worked. I'm at the situation where its telling me "Param Preload, Device not match image". I have tried turning off Sha256 Check and turning on lite firehouse, none have worked. I have looked everywhere but can't seem to find any solution for me
I bricked it by flashing something onto the phone, where it required you to flash certain files, Wipe the phone and then flash more files, but I forgot to wipe the device before flashing the rest of the files, and it hasn't turned on since, I am starting to wonder if there is any way at all at fixing this or is it gone for good. i do not want to spend another $900 for this phone, and repair service is my last option, I am going to see if anyone can help me this on e last time before I file for repair service, as I do not want to pay the repair service
I would really appreciate if anyone could even give me a clue on what to do here as I am out of options, thank you very much for reading anyways even if you weren't able to help
I have also put this on XDA in hopes someone there could help me too!
HI, once the msm tool reads "Param Preload, Device not match image" which means your phone is connected. Please use the MSM EU varient, put your phone on EDL mode, turn on the Sha256 check but "don't use the lite firehouse". This will solve "Param Preload, Device not match image" problem, and the download should proceed normally. Give it a try, hope this will help !
epcwong said:
HI, once the msm tool reads "Param Preload, Device not match image" which means your phone is connected. Please use the MSM EU varient, put your phone on EDL mode, turn on the Sha256 check but "don't use the lite firehouse". This will solve "Param Preload, Device not match image" problem, and the download should proceed normally. Give it a try, hope this will help !
Click to expand...
Click to collapse
If I tick Sha256 then it gets stuck at some "Sahara communications" or something like that, I can't remember I'm not home rn. Any other options?
It seems that you've installed too much different drivers on your computer. Uninstall all android drivers and only install the OnePlus_USB_Drivers_Setup.exe and QDLoader HS-USB Driver_64bit_Setup.exe. Then give it another try !
Another option is that because the EDL mode only holds for may be 5 to 10 seconds, you have to get the msm tool ready with the Sha256 check turn on but "don't use the lite firehouse" also with "start" turn all standby. Once you've got all the above ready, then put your phone into EDL mode and plug into the computer immediately (in a very uick action), and try it again !
Try the option first before revised the drivers ! If I remember right the "Sahara communications" is caused due to the EDL mode is off when your plug into the computer too late. The timing is very important that's why it showed communication error. Try again !
Launch the MSM tool (use the Win7 one) Choose "Others"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ensure you select the EU from the top "Target" dropdown:
Don't change any of the other options, you shouldn't really need to. Just use the default options.
Then click "Start", once you see it's started and it's looking for the phone (ensure you've connected the phone directly to your computer, not via a USB hub, it's also usually better to use a USB2.0 port for some reason) reboot your phone holding down all 3 buttons (power AND vol down AND vol up).
If the program does not jump into life when it sees the phone then you have a driver issue, I've uploaded the correct Qualcomm driver here.
They're the ones I use and it works fine for me, always use it to go back after trying custom roms out.
I'd also recommend keeping your device manager open while you're doing this cos you'll see it change if the computer recognises the phone in EDL mode. It'll show it as a different device from normal.
djsubterrain said:
Launch the MSM tool (use the Win7 one) Choose "Others"
View attachment 5677693
Ensure you select the EU from the top "Target" dropdown:
View attachment 5677699
Don't change any of the other options, you shouldn't really need to. Just use the default options.
Then click "Start", once you see it's started and it's looking for the phone (ensure you've connected the phone directly to your computer, not via a USB hub, it's also usually better to use a USB2.0 port for some reason) reboot your phone holding down all 3 buttons (power AND vol down AND vol up).
If the program does not jump into life when it sees the phone then you have a driver issue, I've uploaded the correct Qualcomm driver here.
They're the ones I use and it works fine for me, always use it to go back after trying custom roms out.
I'd also recommend keeping your device manager open while you're doing this cos you'll see it change if the computer recognises the phone in EDL mode. It'll show it as a different device from normal.
Click to expand...
Click to collapse
I have tried these drivers with EDL mode, still no luck, just the same error, do you have any idea what it could be?
Aphriz said:
I have tried these drivers with EDL mode, still no luck, just the same error, do you have any idea what it could be?
Click to expand...
Click to collapse
"Param Preload, Device not match image" would suggest you're not using the correct MSM tool
Check your box and make sure you downloaded the correct one from here :
OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)
By using these tools, you accept full responsibility for your actions. Your warranty is void should you run any of these utilities without OnePlus support present. I am not responsible for bricks, fires, nuclear war, etc. If you modified any...
forum.xda-developers.com
Even if you're in the EU, depending on who you bought it from, it might be the global version, they all work the same though, obviously choose the region in the top dropdown that matches your device once you confirm it.
If you're not sure, tell us the model number here so we can advise further, although GSM Arena is always a good site to help with that
djsubterrain said:
"Param Preload, Device not match image" would suggest you're not using the correct MSM tool
Check your box and make sure you downloaded the correct one from here :
OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)
By using these tools, you accept full responsibility for your actions. Your warranty is void should you run any of these utilities without OnePlus support present. I am not responsible for bricks, fires, nuclear war, etc. If you modified any...
forum.xda-developers.com
Even if you're in the EU, depending on who you bought it from, it might be the global version, they all work the same though, obviously choose the region in the top dropdown that matches your device once you confirm it.
If you're not sure, tell us the model number here so we can advise further, although GSM Arena is always a good site to help with that
Click to expand...
Click to collapse
I have the EU version, I was talking to OnePlus support and they told me. I have tried the EU MSM and I'm still getting the same result, any help would be great
Aphriz said:
I have the EU version, I was talking to OnePlus support and they told me. I have tried the EU MSM and I'm still getting the same result, any help would be great
Click to expand...
Click to collapse
It sounds like you're doing something wrong when connecting device /entering EDL mode at the correct time. or you haven't got Proper drivers installed,. Keep trying different configurations bro you'll get it eventually. If you haven't restarted PC since installing drivers give that a go. That stopped errors for me.
Easy way to catch EDL mode on your phone is to have your phone completely shut off and not connected. Get MSM set up how it should be and go ahead and hit start. It will begin looking for your phone. Connect your phone to the USB that is connected to your computer while holding down both volume buttons.
No fuss or trying to time anything. It will start your phone and catch the EDL mode.
Won't solve your problem, but it's an easy way to catch EDL every time.
Deleted
After all the comments from the above members, your phone should work with the msm tool. If still not, which means you didn't catch the right timing when connect the phone to the computer. Last option, leave your phone for 3 to 4 days until the phone battery is completely drained off. Then try to re-connect your phone again with the msm tool. Once your phone is connected, it should start the firmware download automatically. Give it a go !
I would also check to see if the drivers work if you disabled driver signing in Windows, there were some issues previously with the certification:
After that, try installing the driver again, just in case that's what is stopping them working.
Check it with another cable also, I've honestly had a problem with one USB cable and not another, it's rather fickle but once you confirm what setup works, just use that in future.
Try on another computer/laptop also if you have one but install those drivers before you even start. You should do that with any USB device, install the drivers first THEN attach it.
Related
Hey everyone
This mostly applies to those of us that have a bricked MediaTek device. Yes the ones amongst us that are the most desperate I am sorry to say. Some of you laugh at that cause your Flashing experience has worked perfectly from the get go and you have flashed successfully with functioning device. Well that's great. Good for you! You're awesome. Sooner or later you are going to make a mistake and panic is going to set in and you will be where I have been. I am sorry to say that is not a very nice place.
For me it was not my device which makes matters worse. I was translating a device for an older gentleman who purchased it from Alibaba; it's an MTK6589 device to be precise.
Anyway I am sure a lot of you out there are frustrated with why your device is doesn't work with SPFlashTool even though you have been following the most of the tutorials to a T? Why your device disconnects from device manager 2 seconds after you plug the thing in and it disappears out of the device list? Like WTF right? Well would you look at me strangely if I said that this is actually by design? That yup your MediaTek device is actually meant to do that?!
If you have experienced this, then I have answers for you and I have an explanation as to why your MediaTek device is doing this, and why your device has not been able to be flashed by SPFlashTool.
Really we are our own worst enemy when it comes to this MediaTek woes; Why? Cause we are impatient and we go off looking for answers in the wrong direction when in fact they are right in front of us all along. Here I will hopefully expand your understanding about these devices and why/how things work so that you can apply it in the future.
I will explain my situation and what I discovered in the process. Hopefully it sheds some light on disconnect device driver situations and lays some thing to rest....hey maybe even some of you who had given up and tossed your cheapo China phone in the bedside draw cause nothing worked and it wasn't worth the price to send back, maybe you guys might want to give this a go and revive your MediaTek device?
Follow this guide step by step BUT READ EVERY STEP EVER SO CAREFULLY.... also take note of the points below that I am going to emphasise that AREN'T emphasised anywhere in this tutorial nor any other tutorials I have followed, so pay attention.
http://forum.xda-developers.com/showthread.php?t=1982587
The part that is not emphasised is this
Turn off your phone, remove the battery and replace it after some seconds (and don't turn on the phone).
Press F9 (or hit Download button) and connect your phone into the computer via USB data cable.
The process will start and a red progress bar will appear.
Click to expand...
Click to collapse
In both cases the word 'and' should be replaced with the word 'THEN' so that people will understand.
What isn't really mentioned on any tutorials is that the MTK6589 is different to how you flash other mediatek devices with SPFlashTool; why? Because you MUST put the battery back in before you flash unlike other MTK devices where they explicitly say DO NOT put it in and/or that you should flash without the battery in place. THIS IS INCORRECT!
Next thing to emphasise is this: You must have the phone disconnected when you click on the download button inside SPFlashTool. You press download then you put the battery back in your phone with the USB connected to the phone., wait and when the download part finishes (only a few seconds) THEN you plug the phone in to the computer (yes with the battery still in place) but do not switch the phone on.
When the phone is detected by Windows and starts to load the drivers like it usually does and then disconnects...well what happens now is that when it loads drivers for a second SPFLashTool engages the phone and holds open the connection. It will pause for a couple of seconds (but you will notice it doesn't disconnect) and then SPFlashTool will show a red/orange progress bar that goes quickly....then it will write the firmware when you see the yellow progress bar.
Something to note here (I downloaded literally hundreds of drivers by the way) that you only need 1 driver and that is the one mentioned in the tutorial.
You don't need to do all the bullsh!t with device manager and removing drivers etc with USBDview....this should only be if the phone doesn't read initially as MTK65xx preloader OR doesn't end up registering as MediaTek DA USB VCOM.
So I will explain...when you plug it in on a clean WIndows 7 PC for he first time it will appear as MTK65xx preloader under device manager under unknown device and Windows will attempt to download the correct drivers and then fail. This is normal.
DO NOT GO AND INSTALL PDANET DRIVERS!!! This doesn't work.
Yes the drivers ARE more stable and don't disconnect nearly as much as the other MediTek drivers, however what this does is register the devices as an Android ADB device, and allows you to use ADB. We want to use SPFlashTool, not ADB at the moment.
Installing other MediaTek drivers after PDANet for some reason causes a conflict and interferes with communication with the device?? I suspect that this is what was causing much of the issues I was experiencing? You may use the PDANet drivers after you have flashed via SPFlashTool if you cannot get an ADB connection, however in my case once the new firmware was written to the device and it was restored and fully functional; when I plugged it in the ADB drivers loaded automatically anyway
Ok next points to make. Unplug your device. Install the drivers (I have attached the ones that worked for me). NOTE: You may need to log in allowing unsigned drivers as mentioned in other tutorials. To do this you can use EasyBCD, go into advanced settings for the Windows 7 bootmenu entry and allow the use of unsigned drivers and put a wait of say 10seconds on the menu count down (in stock form Windows has assigned 30 seconds but standard it bypasses the boot menu - this makes it harder to press the F8 key during boot up). After finishing in EasyBCD reboot and when you come to the Windows boot menu press F8 anyway and choose allow use of unsigned drivers. This is a just in case thing.
Get EasyBCD from HERE
Once in Windows, plug in your device WITH THE BATTERY IN and device switched off. Open Windows device manager (a quick way is type devmgmt.msc in Start menu or Run menu from the start menu - if you search for the management console by full file name you can right click the devmgmt.msc and pin it to the Start menu this is what I have done).
In device manager you NEED to see the device registered as MediaTek DA USB VCOM. If it is not appearing push the volume up button + but keep the phone OFF. When it appears for just a second make sure it is MediaTek DA USB VCOM. *This is important* It must NOT be registered as Preloader or any other MediaTek driver ie. Preloader USB VCOM port OR MediaTek USB VCOM (Android) etc. IT MUST BE MediaTek DA USB VCOM Just look for the one that has DA in the name and is a VCOM driver. This is the driver we want:good:
Ok here is where I will mention that USBDview removal of drivers is not necessary and does absolutely nothing anyway because Windows 7 remembers every single driver you have installed regardless of the fact that you have removed/uninstalled and even checked the box delete drivers or what ever. It doesn't matter...every driver you have ever tried will be in the device driver list. USBDview is only good for unregistering the device association with a registered driver. It doesn't remove drivers.
So now where was I? Ahh right, yep. When you plug in your device (switched off and the battery in place) and it appears momentarily in device manager it must be MediaTek DA USB VCOM, If not Or if it disappeared too fast; just push the volume up button again and this time as it appears quickly, click to expand the (PORTS COM &LPT) listing, then quickly right click the MediaTek listing and go to Update Driver Software. You may need to do this several times to get it. Unplugging the USB from the PC and plugging it back in again may help.
Resist the urge to search for new drivers as the device IS actually detected but not as a PORTS COM &LPT, and doing so will be fruitless as you will only assign the incorrect drivers to the incorrect function. So unplug and replug it in again pressing volume up.
Note: It does not matter if the device disconnects and disappears out of Device Manager when you are in the Upgrade Device Driver software menu....this is normal. The most important point here is that the correct driver is being registered to the correct device protocol (pressing the volume up button to get COM&LPT).
The device needs to appear as MediaTek DA USB VCOM and this must be registered specifically to the (PORTS COM &LPT) in device manager. If it lists elsewhere as a USB device and has the MediaTek DA USB VCOM driver assigned to it, then you need to uninstall the driver from the device listing and start again. Don't go looking for more drivers PLEASE!
Click for explanation
Ok I will digress again for a moment to explain why all this is so important and what many of us are not realising especially with all the tutorials around; the important point here is that MediaTek devices may be listed many numerous devices in device manager and this is normal. They could be an ADB android device, a MediaTek USB Port version etc and these are not the functions we want to use for flashing with SPFlashTool are they? I know when I plug in my Galaxy S3 it loads at least 5 different drivers! Same with these devices.
We need to have the (PORTS COM &LPT) registered as MediaTek DA USB VCOM and this ONLY achieved when we press the volume up button!! If the device disappears from the list after plugging it in and appears as something else and then we register the MediaTek DA USB VCOM driver to this function we are likely trying to use the MediaTek DA USB VCOM driver to load the MediaTek USB Port function and this is obviously NOT the protocol that SPFlashTool is using to communicate with the device to write new firmware.
Ok I will continue now, once you have got into the Upgrade Driver Software menu,
Go to 'Browse my computer for device software',
Then select the second option 'Let me pick from a list of device drivers on my computer', just choose the 'show all' at the top of the list
Next you *should* see MediaTek DA USB VCOM listed in amongst various MediaTek drivers., select this one.
* However if you do not see MediaTek DA USB VCOM listed in the list there then uncheck the box next to 'Show compatible drivers' and it should now show a few more drivers.
You may need to scroll in the right menu bar down to MediaTek.
You will be hit with an overwhelming list of MediaTek drivers! See Pic for reference
Select the required MediaTek DA USB VCOM driver from the list. If its not there (then and only then) you should try install another set of drivers and restart the process again. Try the drivers I have attached below first though.
At this point please resist the urge to click 'Have disk' then 'Browse' to and go scouting for a specific driver in the hopes that this will be the one; THIS IS WRONG! and should not be recommended like it is in just about every tutorial I have seen so far.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It's funny how even the drivers you previously removed are included in that list eh? You know...the ones that everyone told you, you need to delete bla bla bla...THEY ARE STILL THERE DAMN IT!
Once you have selected the driver as MediaTek DA USB VCOM and closed out of the menu you will notice that it has actually gone from the list in device manager? This is normal. The driver is only meant to appear when we do a specific thing and that is pressing the volume up button to write firmware using SPFlashTool and nothing else.
As I mentioned earlier, this is by design. You will note that MediaTek devices, have these protocols USB Mass Storage, MTP, PTP, ADB and COM &LPT.
Now unplug your device. I would at this point do a reboot of Windows (again ensuring unsigned drivers by pressing F8 - just incase)
Once you're back inside Windows, open device manager again.
Keep the device off and have the battery in.
Plug the MicroUSB end into the device first (it's easier - trust me you will understand when I explain).
Now keeping it switched off but press and hold the the volume up button and then plug the cable into the PC USB port; watch as it registers inside device manager as MediaTek DA USB VCOM.
When it does, disconnect the cable from the USB port. - You are now good to go
Now Open SPFlashTool.
Select the scatter file.
Uncheck the following from the list (Preloader, MBR1, EBR1, Uboot, Sec_Ro, Logo, EBR2 and FAT - note fat is for the internal sdcard). We want to write to system, recovery and boot pretty much. If you have ruined your device with the incorrect preloader,
Keep the device UNplugged. Click the download button. You will see the purple progress bar but for only a very brief moment. This is ok and is normal.
IF you have completely obliterated your device by flashing an incorrect preloader click below
I have been advised that you may need to first flash the Preloader, MB1, EBR1,Uboot and EBR2) to setup the partitioning again. The preloader I assume is similar to a PIT file for Samsung devices?
Now we do as we did before. Plug the MicroUSB end in first to your device. Have it switched off but with the battery in place. Press and hold the volume up + button and then plug the cable in to the PC USB port again.
At this point you will hear the device register with Windows as you normally would however you should notice that it doesn't disconnect straight away like it normally does?
This is because the MediaTek DA USB VCOM is registered to the PORTS COM &LPT and SPFlashTool is listening on this port.
Then shortly after progress with a Red/Orange bar.
It will pause for a what seems like a long time..... but please leave the device plugged in! [shouldn't be longer than 10min - if it is you've done something wrong, disconnect and do the process again and read making sure you understand every one of the points I have made in this post]
Once you see the yellow progress bar you can breath with relief.
Congratulations you have just revived your bricked device! :good:
Additional Info: After a reboot when you plug the device into the PC USB port again you should start to see Windows identify the extra protocols associated with your MediaTek device. I noted than this one I was working on appeared back as an MTP Portable device, also as an ADB Android device further up the list and as an MTK USB Port when the volume up button is pressed (I guess now Windows knows what it is it is assigning it a different driver?)
But what if it doesn't disappear? I have the problem with ZTE V967s that i cannot flash it (probably dead), because I have "ENABLE DRAM FAILED (4032)" issue.
This is probably because the phone cannot exit the VCOM status, it is visible under this state for many minutes in device manager. Do you have any ideas how to solve this problem?
How i unbricked my Lenovo K3 Note (MTK6752)
Hi,
First of all I am thanking God Jesus Christ for helping me find a solution.
My Lenovo K3 Note was hard bricked when i accidently unplugged it while sp flash tool was flashing the firmware. The screen was not at all lighting up(Not even boot logo). When battery is inside and press power button i could see a feable red colour light near the proximity sensor. When i connect my phone to PC without battery (As many sp flash tool procedures says us to remove battery and connect) , it was not at all being detected by pc. This was my condition..!!!
I searched tried a lot for 5 hrs.. Continously.. Yes literally..
At last I started my own experiments. I downloaded complete stock firmware. and loaded it to sp flashtools by selecting scatter file. I selected the format+download option in sp flash tools. I clicked download button in sp flashtool. Now sp flash tool is waiting for my phone to get connected.
I removed the battery of phone, then i pressed the volume buttons, power buttons etc.. to remove static charges if present (for 10 seconds). "Then i put the battery back to the phone. "
I connected the usb cable to phone ,keep pressed the volume up key, then the other end was connected to the computer. SP flashtool detected my phone and flashing started(Now i released volume up key press). Wait for sometime till flashing completed and we get OK pop up in sp flash tool. Wait for some 10 seconds . Dont remove phone from computer. Press and hold the power button for switching on the phone without removing from computer.
If screen doesnot light up, release the buttons, remove the phone from computer . Press the power button two three times(Dont hold). Now press and hold power button to switch ON your phone. Thank God and Be happy seeing your phone booting up. :laugh::laugh:
if cant non-removeable battery(0% battery) for mtk phone. what shoud i do? power + volup ??? or something
hello everyone.
Can anyone help me with unbricking my M8?
Its a live , its reacting on usb connection with my pc, but i can not communicate throug usb, i can not see anything on the phone screen, i can not get it in recovery/bootloader netiher download mode,
yes
Yes its possible.
Open device Manager in windows. Plug in your device an you must see for seconds a new device named qhusb.
You must be fast and right click on this for seconds pop uped device and click properties.
Then look for the Qualcomm bootloader driver With google.qhusb driver.
Then install this driver with the opened properties settings.
If you get this, make a post here.
Good luck.
Hi Konsolen,
Thanks for the reply. I connected the phone, and qualcom hs usb showed up and i have added some screenshot , but i dont exactly understand your last comments qualcom bootloader driver and so on.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/IMG]
[/IMG]
i added some picture, but where do i find the bootloader driver?
konsolen said:
Yes its possible.
Open device Manager in windows. Plug in your device an you must see for seconds a new device named qhusb.
You must be fast and right click on this for seconds pop uped device and click properties.
Then look for the Qualcomm bootloader driver With google.qhusb driver.
Then install this driver with the opened properties settings.
If you get this, make a post here.
Good luck.
Click to expand...
Click to collapse
It looks that your Windows install it automaticly.
Are the device always in the device manager or only for seconds?
I will upload some tools in my dropbox and send you a link with infos.
Gkhnnn said:
hello everyone.
Can anyone help me with unbricking my M8?
Its a live , its reacting on usb connection with my pc, but i can not communicate throug usb, i can not see anything on the phone screen, i can not get it in recovery/bootloader netiher download mode,
Click to expand...
Click to collapse
Does the M8's screen come on? Any charge LED (and what color)?
Very key detail (among others): what did you do to get the phone into this condition?
m8
the notification light flashes for a second when connecting to a charger. it flashes also when connecting to pc. also flashes when holding power butt for 15sec.
i installed cm12 but i couldnt use my navigation as the ohone couldnt find any sattelites.
so i tried several firmwares and after changing to supercid i managed to update firmware and hboot. after installing cm12 the phone asked me for a password and i found the installation was corrupt somehow. i find some commands i typed in recovery twrp but it freezed and after a forced restart i saw red triangles on each corner and has never seen anytging on scrreen since. always black.
Gkhnnn said:
the notification light flashes for a second when connecting to a charger. it flashes also when connecting to pc. also flashes when holding power butt for 15sec.
Click to expand...
Click to collapse
Red LED? I asked what color before.
Gkhnnn said:
after installing cm12 the phone asked me for a password and i found the installation was corrupt somehow. i find some commands i typed in recovery twrp
Click to expand...
Click to collapse
That is remarkably vague. What commands exactly?
m8
sorry, the color is orange.
i'm on phone now and can send the commands i have tried
but the codes never worked but i believe i managed to delete a wrong partition .
when onnecting Phone to pc, 14 disk partition shows up, only 4-5 of them has files inside.
konsolen said:
It looks that your Windows install it automaticly.
Are the device always in the device manager or only for seconds?
I will upload some tools in my dropbox and send you a link with infos.
Click to expand...
Click to collapse
Device is always in the device manager. If i remove the driver it shows up as qusb bulk with question-mark.
I tried to download several driver but i couldnt get the device in fastboot or download mode.
I look forward to your link
Thanks
m8
redpoint73 said:
Red LED? I asked what color before.
That is remarkably vague. What commands exactly?
Click to expand...
Click to collapse
TWRP after installing a rom giving me "unable to mount data" all the time.
I done a research and found out that i could type following commands and get it work.
cd /d c:\mini-sdk
adb push mkfs.ext4 /tmp
adb shell
chmod 777 /tmp/mkfs.ext4
/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext ra_isize -m 0 /dev/block/mmcblk0p37
But i heard from somebody that these codes were for HTC M7 and not M8
What carrier or region (CID)?
m8
redpoint73 said:
What carrier or region (CID)?
Click to expand...
Click to collapse
Its a Verizon , i live in Europe, but i got the phone for free from company i worked in.
This is a pic i took for a weeks ago.
[/IMG]
Why not just try and flash the RUU?
http://forum.xda-developers.com/ver...zip-ruu-m8vzw-5-0-1-s-off-onlynewest-t3047103
That might at least get it working again, as you can do it via a microSD card
m8
i have now downloaded the standalone zip and copied that to sd card, renamed to 0P6BIMG.zip
as the screen doesnt show anything, i have powered on with vol down, i assume the hboot ask for vol up for continue to installing, now i wait but i dont thing anything happens
The exe RUU says "USB error, could not connect to the phone"
m8
When connecting the phone to pc, as said before 14 disk partition opens up, and here are the folder which contains the files showed
[/IMG]
[/IMG]
[/IMG]
[/IMG]
m8
When the phone connected to my pc , its shows in device-manager:
PORTS: Qualcomm HS-USB Diagnostics 9006 (COM12)
Ah, right. Yeah you've bricked the phones internal memory. Not sure if it's repairable but if it is it's WELL over my head...
EddyOS said:
Ah, right. Yeah you've bricked the phones internal memory. Not sure if it's repairable but if it is it's WELL over my head...
Click to expand...
Click to collapse
Screen not coming on, and device showing as Qualcomm on PC is a bad sign. Agree it might not be recoverable.
Someone did the same thing (M7 internal storage "fix") a week or 2 ago. I'll see if I can find the thread, and if there was any favorable outcome.
But extreme care needs to be taken before manually messing with partitions like the OP did. A single mis-typed character can be disastrous. And there are safer ways to have recovered from the fairly common internal storage issue (format with computer or in TWRP).
redpoint73 said:
Someone did the same thing (M7 internal storage "fix") a week or 2 ago. I'll see if I can find the thread, and if there was any favorable outcome.
Click to expand...
Click to collapse
That someone is the same one
And what I know ... that's a hard brick .. corrupted partition
Hello,
I have a LG G3 d855 which is bricked while updating ROM. It is hard bricked meaning I could not see anything on the display. I went to the LG service center. They had a suggestion to replace complete mother board. I went through few forums on XDA on how to unbrick the dead phone.
Here is the procedure which I have followed,
I was not able to see "LGE AndroidNet USB serial port" and "Qualcomm HS-USB QDLoader 9008" .. The suggestions were to short the pins.
After shorting pins and replacing the battery, I am able to "LGE AndroidNet USB serial port" only.
Here are couple of links I went through,
http://forum.gsmhosting.com/vbb/f49...ts-fix-qhsusb-bulk-_-qualcomm-9008-a-2029025/
https://forum.xda-developers.com/lg-g3/general/unbrick-lg-g3-qhsusbbulk-qualcomm-9008-t3072091
How do I get "Qualcomm HS-USB QDLoader 9008" in the driver list instead of "LGE AndroidNet USB serial port" ?
Just keep trying, with no battery. You should be doing it pretty fast, in less than 30 seconds, else, windows picks your phone as an unknown device.
Also try making the shorting of the 'pins' as strong as possible with something you know it's really conductive (for me, paper staples if can't get copper) and holding it still for 5 seconds.
I have to try for about 10 times to make it right, and sometimes BoardDiag still says it's not in QDLmode and have to redo the process.
When u manage to get HS-USB in Device Manager, try boardDiag3.99a and boardDiag2.99a as I've seen that on my laptop, 3.99 says that phone is not in QDLmode, yet 2.99 work perfectly
AKAndrew41 said:
Just keep trying, with no battery. You should be doing it pretty fast, in less than 30 seconds, else, windows picks your phone as an unknown device.
Also try making the shorting of the 'pins' as strong as possible with something you know it's really conductive (for me, paper staples if can't get copper) and holding it still for 5 seconds.
I have to try for about 10 times to make it right, and sometimes BoardDiag still says it's not in QDLmode and have to redo the process.
When u manage to get HS-USB in Device Manager, try boardDiag3.99a and boardDiag2.99a as I've seen that on my laptop, 3.99 says that phone is not in QDLmode, yet 2.99 work perfectly
Click to expand...
Click to collapse
hey, thanks a lot. It worked. I could get the phone flashed using the BoardDiag.
Now. Another issue which I am facing is, I am not able to flash the phone using the LG Flash Tool.
Here are the steps which I have followed,
1. Pressed Volume UP key .. while holding the same key I can attached USB to the phone.
2. Phone went into download mode.
3. PC has also recognized that the device. But it showing Qualcomm 9008 driver (which is not expected I suppose) . I should be able to see LGE driver in the port section.
4. I have installed all necessary LG drivers.
Still, I went ahead and tried the LG flash tool. But once it shows all ports are ready. I removed the cable to for 5 sec and reattached. Now, It's showing unknown driver in the USB controllers. It should be flashing the phone on this step.
Am I missing something ? Appreciate your help.
I assume that you are not getting the "Firmware upgrade" screen. The easiest way is, in BoardDiag, select AP, EMMC and SDRAM (and the path to the extracted .tot) and press start. It should get you to the screen.
From there you should follow the normal flashing procedure using one of the flashing tools.
If in your device manager under Ports you see a AndroidNet port, you must install LG usb Drivers.
AKAndrew41 said:
I assume that you are not getting the "Firmware upgrade" screen. The easiest way is, in BoardDiag, select AP, EMMC and SDRAM (and the path to the extracted .tot) and press start. It should get you to the screen.
From there you should follow the normal flashing procedure using one of the flashing tools.
If in your device manager under Ports you see a AndroidNet port, you must install LG usb Drivers.
Click to expand...
Click to collapse
Hey Andrew,
You mean If I see the firmware upgrade screen, I should be able to see LG usb driver loaded (instead of Qualcomm 9008). I did try the the AP, EMMC and SDRAM, but did not reach to the firmware upgrade (Still I will try once again). BTW, I tried multiple tools including LGUP, LG Flash tool (2014 Mod), LG Flash tool (kdz method). I am getting weird errors like model info check failed, KDZ method abruptly stops or LGUP shows null model after detection.
Is there any way we could chat somewhere. (may be on Gmail/WebEx, if don't mind). Really appreciate you help.
rushikesh005 said:
Hey Andrew,
You mean If I see the firmware upgrade screen, I should be able to see LG usb driver loaded (instead of Qualcomm 9008). I did try the the AP, EMMC and SDRAM, but did not reach to the firmware upgrade (Still I will try once again). BTW, I tried multiple tools including LGUP, LG Flash tool (2014 Mod), LG Flash tool (kdz method). I am getting weird errors like model info check failed, KDZ method abruptly stops or LGUP shows null model after detection.
Is there any way we could chat somewhere. (may be on Gmail/WebEx, if don't mind). Really appreciate you help.
Click to expand...
Click to collapse
[update]
Hi Andrew,
I followed the steps you have mentioned (Tried AP, EMMC and SDRAM). Then disconnected from the USB. Placed Battery. and while holding the up key reattached the USB.
I can see it went into download mode.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But after that it shows blank screen( instead of firmware upgrade).
And Qualcomm driver is getting loaded. (which is not expected, I should be able to see
the firmware upgrade screen right ?).
Still I tried the LG flash tool. But it failed with model check error.
With above method I was getting Qualcomm driver loaded. (which was not expected).
I tried another way, where I booted the phone (it went into kernel panic) as written over there I pressed up key and reattached USB.
Now I can see the LGE Android drivers loaded. But still I am not seeing the firmware upgrade screen. And LG flash tools are also not working in this stage.
Am I missing something ?
Give it another try using LGUP8974.dll but you must have Firmware Upgrade screen. I don't think it will work through Qualcomm unless you flash each partition with BoardDiag but it is painfully slow.
I've read about this problem on the forum and this should have solved it. Worked for me too, most of the times.
Make sure you have a charged battery. Spend a whole day trying to get firmware upgrade screen just to found out wasn't getting it due to low battery...
AKAndrew41 said:
Give it another try using LGUP8974.dll but you must have Firmware Upgrade screen. I don't think it will work through Qualcomm unless you flash each partition with BoardDiag but it is painfully slow.
I've read about this problem on the forum and this should have solved it. Worked for me too, most of the times.
Make sure you have a charged battery. Spend a whole day trying to get firmware upgrade screen just to found out wasn't getting it due to low battery...
Click to expand...
Click to collapse
Thanks Andrew.
Not sure if this is low battery issue in my case. I am able to see LG logo without connecting it to USB. (was it the same case with you).
Still I will charge my phone again. Will do the SDRAM test again to see if phone shows firmware upgrade screen.
If this does not work, I will have to write all partitions using BoardDiag. Should I follow any sequence for the same ?
I have read on the other posts about the sequence. Would it matter ?
Let me know.
rushikesh005 said:
Thanks Andrew.
Not sure if this is low battery issue in my case. I am able to see LG logo without connecting it to USB. (was it the same case with you).
Still I will charge my phone again. Will do the SDRAM test again to see if phone shows firmware upgrade screen.
If this does not work, I will have to write all partitions using BoardDiag. Should I follow any sequence for the same ?
I have read on the other posts about the sequence. Would it matter ?
Let me know.
Click to expand...
Click to collapse
You can follow the partition order from this link(listed in steps 18 & 19)... https://forum.xda-developers.com/verizon-lg-g3/general/how-to-hardbrick-guide-using-test-t3276928
aboot, BackupGPT, boot, dbi, laf, PrimaryGPT, recovery, rpm, tz and finally sbl1 (MAKE SURE THIS IS THE LAST ONE FLASHED(it causes the phone to reboot)
*do not flash system or user data partitions with board diag - they take over an hour and they will be re-flashed once you get download mode working anyway
*if a partition fails to write you may need to erase it first
*another good guide for reference... https://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
Good luck!:good:
If you want to avoid using LG Flashtool I think(no sure) u can flash them through BoardDiag. The order is the one mentioned by startswithPendswithOOH but I thing u can add system partition and the others right befor sbl1.
I couldn't make my G3 stable even at the best GSM service in my city - due to notorious CPU/eMMC fails (overheating, protected storage etc.) and ther response was RIP. No chance to make it work again, will always crash whenever I will get the cpu reach 100%. I will never in my life buy LG phones again. Glad I won't lose more than 60$
Hello. I know that this thread is quite old but I am trying hard to revive my hard bricked LG G3 D855 these days. I have installed Qualcomm Drivers but I cannot get my device recognized on my PC. As soon as I plug in my phone I receive a "USB Device not recognized" error. I believe I am shorting the pins correctly and everything regarding drivers installation has been done as described. But I have tried too many times and I still receive that error. Please note that my phone is dead. It used to light up when I connected it on the PC but now its totally unresponsive. Could anyone please let me know what I could be doing wrong? Does the type of wire used to short the pins play significant role? Any images of a wire that I could use?
hello there guys, im new here and also desperate
unfortunately im struggling revive my beloved op3. i am getting a strange error, cant really seem to find many thing about it. so what happened is i was about to switch profile on the phone when it froze and stuck in bootloop, so i decided since nothing else worked to wipe everything off the phone. so it all went great, it was wiping data for atleast an hour when i decided to plug in to charge just in case, but the cable i used was fauilty so i ended up drained battery. ince then i am not able to recover it unfortunately.
in msm tool, it stucks at downloading chace.img, then afetr a couple of seconds i get an error:
firehose check rsp failed, errno:258
downloading chace.img failed
iam very out of ideas what to do from here. only thing is after this the led glows light green-yellowish
any suggestion?
other thing what i realised:
when it sais hold the volume up button and connect to usb, nothing happens. unless i press volume up+power button. could it be the reason? no matter how long im holding only volume up and connect it to pc, nothing will happen.
thanks for reading,
Tomi
and aslo this is what i get in the log
Device Arrival: \\?\USB#VID_05C6&PID_9008#6&2af7e5e9&0&1#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
m_ImageHwId 16: 009470E12A703DB9
m_PhoneHwId 24: 009470E12A703DB9
UFS Inquiry Command Output: SAMSUNG KLUCG4J1CB-B0B1 0800
UFS info Vendor = samsung, TotalLogicalBlocks = 124993536
[7] HANDSET_TYPE_64G:
[7] Downloading rawprogram0 Label: cache FileName: cache.img
Device Remove: \\?\USB#VID_05C6&PID_9008#6&2af7e5e9&0&1#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
Maszkos said:
hello there guys, im new here and also desperate
unfortunately im struggling revive my beloved op3. i am getting a strange error, cant really seem to find many thing about it. so what happened is i was about to switch profile on the phone when it froze and stuck in bootloop, so i decided since nothing else worked to wipe everything off the phone. so it all went great, it was wiping data for atleast an hour when i decided to plug in to charge just in case, but the cable i used was fauilty so i ended up drained battery. ince then i am not able to recover it unfortunately.
in msm tool, it stucks at downloading chace.img, then afetr a couple of seconds i get an error:
firehose check rsp failed, errno:258
downloading chace.img failed
iam very out of ideas what to do from here. only thing is after this the led glows light green-yellowish
any suggestion?
other thing what i realised:
when it sais hold the volume up button and connect to usb, nothing happens. unless i press volume up+power button. could it be the reason? no matter how long im holding only volume up and connect it to pc, nothing will happen.
thanks for reading,
Tomi
and aslo this is what i get in the log
Device Arrival: \\?\USB#VID_05C6&PID_9008#6&2af7e5e9&0&1#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
m_ImageHwId 16: 009470E12A703DB9
m_PhoneHwId 24: 009470E12A703DB9
UFS Inquiry Command Output: SAMSUNG KLUCG4J1CB-B0B1 0800
UFS info Vendor = samsung, TotalLogicalBlocks = 124993536
[7] HANDSET_TYPE_64G:
[7] Downloading rawprogram0 Label: cache FileName: cache.img
Device Remove: \\?\USB#VID_05C6&PID_9008#6&2af7e5e9&0&1#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
Click to expand...
Click to collapse
When you hold volume up and connect to the PC, it should be recognised. If not, it is either of two things viz. the required drivers are not installed or the phone is really DEAD. So follow the steps given in the Unbrick Guide scrupulously and check. I have used it and revived my phone successfully.
tnsmani said:
When you hold volume up and connect to the PC, it should be recognised. If not, it is either of two things viz. the required drivers are not installed or the phone is really DEAD. So follow the steps given in the Unbrick Guide scrupulously and check. I have used it and revived my phone successfully.
Click to expand...
Click to collapse
Okay thanks for that. I'll redo everything step by step, and I'll let you know if it worked out which I hope so.
One more question: since I had the phone bricked while restoring it to factory and ran out of battery, can it cause hardware failure? Or any idea what is the meaning of the this 258 error code? I tried to look up on the internet but didn't find anything about it.
Cheers
Tomi
Maszkos said:
Okay thanks for that. I'll redo everything step by step, and I'll let you know if it worked out which I hope so.
One more question: since I had the phone bricked while restoring it to factory and ran out of battery, can it cause hardware failure? Or any idea what is the meaning of the this 258 error code? I tried to look up on the internet but didn't find anything about it.
Cheers
Tomi
Click to expand...
Click to collapse
Did you charge the phone subsequently? Does it take the charge? If the battery is completely dead, the phone may not revive unless the battery gets some charge. You may try to charge it or with another battery if that is available.
tnsmani said:
Did you charge the phone subsequently? Does it take the charge? If the battery is completely dead, the phone may not revive unless the battery gets some charge. You may try to charge it or with another battery if that is available.
Click to expand...
Click to collapse
So I installed a fresh windows today did the whole thing from the a-z but the same issue occurs. I think the battery should be alright never had any problems with it. All I get is this man errno:258 nothing seems to work unfortunately..
Maszkos said:
So I installed a fresh windows today did the whole thing from the a-z but the same issue occurs. I think the battery should be alright never had any problems with it. All I get is this man errno:258 nothing seems to work unfortunately..
Click to expand...
Click to collapse
I hope that you are running a regular Win 10 PC that too Intel (not AMD) and not through VM. Also I hope that you disabled the check for driver signing BEFORE installing the drivers. Your issue seems to be the drivers. May be re-download the drivers. Read the entire page. Use another PC or Laptop and different USB ports especially v2.0 and not v3.0. Repeat until you succeed.
tnsmani said:
I hope that you are running a regular Win 10 PC that too Intel (not AMD) and not through VM. Also I hope that you disabled the check for driver signing BEFORE installing the drivers. Your issue seems to be the drivers. May be re-download the drivers. Read the entire page. Use another PC or Laptop and different USB ports especially v2.0 and not v3.0. Repeat until you succeed.
Click to expand...
Click to collapse
Cool I will, it's a regular win10, signature should be ok, I tried it on 3 different laptops, 2ofthem were older ones but no success. I really hope it is just a driver issue since my problem occured while formatting the phone in bootloader. I'm not sure about the usb ports I'll check that out aswell.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'll let you know if there's any update!
Ps I get a greenish light after the man tool fails to upload the cache.img
Sometimes it turns orange aswell. Is that a good sign?
Thank you tnsami for your time and effort, really appreciate it
Maszkos said:
Cool I will, it's a regular win10, signature should be ok, I tried it on 3 different laptops, 2ofthem were older ones but no success. I really hope it is just a driver issue since my problem occured while formatting the phone in bootloader. I'm not sure about the usb ports I'll check that out aswell.
View attachment 4716364
I'll let you know if there's any update!
Ps I get a greenish light after the man tool fails to upload the cache.img
Sometimes it turns orange aswell. Is that a good sign?
Thank you tnsami for your time and effort, really appreciate it
Click to expand...
Click to collapse
Did you ever solve it?
Baxter777 said:
Did you ever solve it?
Click to expand...
Click to collapse
Noo not yet unfortunately I was carried away by other things, I am about to look into it now again, might find a solution for it. Any luck over there?
Have you tried another computer
Baxter777 said:
Did you ever solve it?
Click to expand...
Click to collapse
kallum7 said:
Have you tried another computer
Click to expand...
Click to collapse
I did, but they all had usb 3.0 as far as I can remember, so ill try it with usb 2 soon, maybe next week or so. That is my last resort.
I checked the battery it takes the charge, even tough it only had approximately 3volt in it instead of 3.8v would you think a new battery is essential?
What I would do is buy another charging cable and then try and charge it up and then try and unbrick the phone
kallum7 said:
What I would do is buy another charging cable and then try and charge it up and then try and unbrick the phone
Click to expand...
Click to collapse
Yeah, did that too original cable, charger. So is this a communication error between the phone and PC is it?
Try going into the device manager on windows and go to ports and uninstall OnePlus com port drivers and reinstall them
Hi Guys,
Looks like my phone is bricked noob mistake, what exactly are my options please?
Phone is stuck in fastboot mode whatever option I choose returns to fastboot, I am on linux pc so not sure the software options are compatible?
Any help would be greatly appreciated. I was following the LineageOS on lemonadep wiki
Thanks
Daz
dazuk9269 said:
Hi Guys,
Looks like my phone is bricked noob mistake, what exactly are my options please?
Phone is stuck in fastboot mode whatever option I choose returns to fastboot, I am on linux pc so not sure the software options are compatible?
Any help would be greatly appreciated. I was following the LineageOS on lemonadep wiki
Thanks
Daz
Click to expand...
Click to collapse
Retry the flashing process again. Making sure to skip no steps. Make sure of your original os version (11, 12, 13) as needed for the img you are willing to install.
TheGhost1951 said:
Retry the flashing process again. Making sure to skip no steps. Make sure of your original os version (11, 12, 13) as needed for the img you are willing to install.
Click to expand...
Click to collapse
Tried that mate whatever I do returns to fastboot
dazuk9269 said:
Tried that mate whatever I do returns to fastboot
Click to expand...
Click to collapse
I suspect you are trying to flash the wrong version. If all else fails, you will need to MSM back to stock and start off fresh!
TheGhost1951 said:
I suspect you are trying to flash the wrong version. If all else fails, you will need to MSM back to stock and start off fresh!
Click to expand...
Click to collapse
Ok mate any tutorial for a noob lol on how to do this, just fired up a windows vm so no issues if MSM can only be used on windows, I tried installing with wine on linux but just errors
dazuk9269 said:
Ok mate any tutorial for a noob lol on how to do this, just fired up a windows vm so no issues if MSM can only be used on windows, I tried installing with wine on linux but just errors
Click to expand...
Click to collapse
You don't normally install MSM, just extract it and then open folder and start the MSM tool. This link has everything you need. Even on how to use the MSM tool. Read all instructions until you fully understand before proceeding....
OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)
By using these tools, you accept full responsibility for your actions. Your warranty is void should you run any of these utilities without OnePlus support present. I am not responsible for bricks, fires, nuclear war, etc. If you modified any...
forum.xda-developers.com
TheGhost1951 said:
You don't normally install MSM, just extract it and then open folder and start the MSM tool. This link has everything you need. Even on how to use the MSM tool. Read all instructions until you fully understand before proceeding....
OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)
By using these tools, you accept full responsibility for your actions. Your warranty is void should you run any of these utilities without OnePlus support present. I am not responsible for bricks, fires, nuclear war, etc. If you modified any...
forum.xda-developers.com
Click to expand...
Click to collapse
Will do thank you
I have a funny feeling mine is hard bricked, if the phones stays in fastboot whatever option you choose does this mean it is hard bricked guys?
Is there any linux compatible MSM program? I presume not? I tried with windows VM but with USB connected to vm it displays Android within Device manager. I installed the drivers. not looking good
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
no devices listed in MSM tool
dazuk9269 said:
I have a funny feeling mine is hard bricked, if the phones stays in fastboot whatever option you choose does this mean it is hard bricked guys?
Is there any linux compatible MSM program? I presume not? I tried with windows VM but with USB connected to vm it displays Android within Device manager. I installed the drivers. not looking good
View attachment 5892625
no devices listed in MSM tool
View attachment 5892627
Click to expand...
Click to collapse
It is not hard bricked, just need to borrow a windows PC. I don't know anything about Linux PC!
Make sure drivers are installed correctly.
Windows is only recognising it as a Android device & MSM still not displaying any device, also I followed a fastboot method at https://droidwin.com/unbrick-oneplus-9-pro-fastboot-commands/ due to MSM not displaying but it only got so far before the below error when trying to perform a fastboot reboot in fastbootd mode.
Any pro willing to help me please I would pay you for your time. But maybe its a gonna lol
Which specific driver did you install?
I recommend to use the FW-flasher from the crDroid Thread
crDroid Android - Browse /lemonadep/9.x/firmware at SourceForge.net
Highly customizable Android Platform
sourceforge.net
Also read the instruction in crDroid 9.4 for flashing.
I had the same issue but the FW-flasher fixed it for me. Good luck
AndyC76 said:
Which specific driver did you install?
Click to expand...
Click to collapse
For the fastboot method Android Bootloader Interface Drivers.
Also later installed the QUALCOMM drivers as instructed >> https://community.oneplus.com/thread/1541327
but still not recognised in my vm, QUALCOMM is COM port right?, I may have to wipe my linux pc & install windows lol
dazuk9269 said:
I have a funny feeling mine is hard bricked, if the phones stays in fastboot whatever option you choose does this mean it is hard bricked guys?
Is there any linux compatible MSM program? I presume not? I tried with windows VM but with USB connected to vm it displays Android within Device manager. I installed the drivers. not looking good
View attachment 5892625
no devices listed in MSM tool
View attachment 5892627
Click to expand...
Click to collapse
For flashing with msm tool you have to boot the phone in edl mode (power off the phone and than press and hold pressed voll down and voll up and put in the usb cable your phone boot to edl mode (( black screen )) and than you should see it on msm tool
ChrisFeiveel84 said:
For flashing with msm tool you have to boot the phone in edl mode (power off the phone and than press and hold pressed voll down and voll up and put in the usb cable your phone boot to edl mode (( black screen )) and than you should see it on msm tool
Click to expand...
Click to collapse
Unfortunately doesn't do anything mate pressing volume usd not connected, once connect usd goes straight to fastboot
dazuk9269 said:
Unfortunately doesn't do anything mate pressing volume usd not connected, once connect usd goes straight to fastboot
Click to expand...
Click to collapse
Vol up and vol down ?
yes
ChrisFeiveel84 said:
Vol up and vol down ?
Click to expand...
Click to collapse
Yes sir
When your phnoe is powered off and you press both and put in the usb your phone should boot to edl not to fastboot
ChrisFeiveel84 said:
When your phnoe is powered off and you press both and put in the usb your phone should boot to edl not to fastboot
Click to expand...
Click to collapse
Ok must be totally screwed then lol, when you say press both you mean continuously right or just once?