Related
I'm going crazy here and I need my phone to work!
I have an LG G3 on Verizon.
I rooted it and edited a part of build.prop to change the DPI which got the phone stuck in a boot loop and kept popping up "the process com.android.systemui has stopped.
I tried clearing cache
I tried booting in safe mode
I then did a factory reset
My phone boots up to the Setup Wizard screen but I am STILL getting that systemui error and a com.android.phone and I can't get any further than that screen.
I then tried to use the LG FlashTool to just wipe the entire ROM and replace it with the stock one from Verizon.
This gave me a "Model Information Check FAIL!" error but I DO have the right ROM for my phone. There's only one for the Verizon G3 as far as I can tell
This led me to realizing that there is something in the build.prop that's making LGFlashTool think the proper rom actually isn't right.
I then installed the Android SDK so I can ADB into my phone. but whenever I run "abd devices" nothing shows up in the list.
I was told USB Debugging needs to be turned on in order for this to work, I don't remember if it's turned on or not with my phone and I can't get past the Setup Wizard to edit anything. I wonder if ADB is even running properly on my phone or if these errors are stopping it?
I will gladly paypal someone $20 if they can get this working for me.
Did you tried this?
http://forum.xda-developers.com/showthread.php?t=2772199
droidhd said:
Did you tried this?
http://forum.xda-developers.com/showthread.php?t=2772199
Click to expand...
Click to collapse
yes I did, that's where I got the "Model Information Check FAIL!" error
And what about this guide (if you can enter download mode):
http://forum.xda-developers.com/showthread.php?t=2785089
8) When the firmware is downloaded, boot your LG G3 into Download Mode. To do this, press and hold the Volume Up key and then plug the USB cable.
Click to expand...
Click to collapse
One of my friends saved his phone by this guide
Download mode - LG PC Suite - Restore update error.
1. Remove battery
2. Boot phone into download mode
3. Open LG PC Suite - restore update error
This method have saved me a few times.
Will adb work in one of the recovery modes even if it wasn't enabled in the full boot mode? If so, start there.
Sent from my LGLS990 using XDA Free mobile app
Regarding your USB debugging question, you would have had to turn it on in order to root the phone originally, right? If so I imagine it would still be on unless you unchecked it. You have the proper drivers set up? Anytime I've encountered issues with adb devices not returning any results the issue has been drivers.
Good luck.
droidhd said:
And what about this guide (if you can enter download mode):
http://forum.xda-developers.com/showthread.php?t=2785089
One of my friends saved his phone by this guide
Click to expand...
Click to collapse
Yup! I tried that. I got the "Model Information Check FAIL!" error
robalm said:
Download mode - LG PC Suite - Restore update error.
1. Remove battery
2. Boot phone into download mode
3. Open LG PC Suite - restore update error
This method have saved me a few times.
Click to expand...
Click to collapse
Hey thank, I haden't tried this but just gave it a go and the program is giving me errors when I try to restore update error. I don't think it's connecting to the phone.
SilverZero said:
Will adb work in one of the recovery modes even if it wasn't enabled in the full boot mode? If so, start there.
Sent from my LGLS990 using XDA Free mobile app
Click to expand...
Click to collapse
What do you mean recovery modes? You mean like Safe mode? I actually haven't tried that. I'll give it a go.
Rodeojones said:
Regarding your USB debugging question, you would have had to turn it on in order to root the phone originally, right? If so I imagine it would still be on unless you unchecked it. You have the proper drivers set up? Anytime I've encountered issues with adb devices not returning any results the issue has been drivers.
Good luck.
Click to expand...
Click to collapse
I believe I have the proper drivers, I installed drivers and the phone is showing up in device manager as Alright.
Try hooking it up to the lg support tool and select uprade recovery.
Download and install support tool
Open tool
Plug in phone with phone on.
Top right select options/upgrade recovery
Let it do its thing.
Lg support tool
https://www.dropbox.com/s/1ckig41xdqoi2u1/B2CAppSetup.exe?dl=0
When you looked for phone in device manager did you change the port to com41? I forgot to do that and got the error in LG Flash Tool
Bro your motherboard is done with take it to service center
Hey everyone...it ended up being a stupid fix, I just tried flashing it on another computer and I didn't get the error? I have no idea why it worked.
jpf566 said:
Hey everyone...it ended up being a stupid fix, I just tried flashing it on another computer and I didn't get the error? I have no idea why it worked.
Click to expand...
Click to collapse
Oh man should've told you that. Sometimes its just a driver acting up and you have to manually delete them in the device manager. Sometimes there marked with a symbol .
please hit thanks if i helped in any way. send from my g3 d852 beast
jpf566 said:
Hey everyone...it ended up being a stupid fix, I just tried flashing it on another computer and I didn't get the error? I have no idea why it worked.
Click to expand...
Click to collapse
Sometimes it's the simplest solution that's hardest to find. Glad it all worked out for you.
So who won the 20 bucks? XD
Money's not important. The problem' fixed, this is what's important ; )
Ferindel said:
Money's not important. The problem' fixed, this is what's important ; )
Click to expand...
Click to collapse
True! that's what this forum is about :highfive:
Hi,
I tried to install a custom rom on my LG G3 d858hk model. I was in twrp recovery and trying to install rom. Suddenly the phone got stuck. I waited for some time and then pulled the battery out and reinserted it. But still no light etc. Even nothing happens when I plug in charger. Looks like its completely dead. Any body any idea, how can i recover it from the black screen.
Regards,
Khurram.
http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359 follow this guide just download ure files
Hi. am facing the same issue. Is there any other way to fix it, that doesn't include opening up the phone?
antony990 said:
Hi. am facing the same issue. Is there any other way to fix it, that doesn't include opening up the phone?
Click to expand...
Click to collapse
Do you have a warranty for you phone ? do you tried to download mode, fastboot mode and not working? In case the phone is completely dead, I can suggest you the option boarddiag (open phone) and jtag.
cesarandres_8911 said:
Do you have a warranty for you phone ? do you tried to download mode, fastboot mode and not working? In case the phone is completely dead, I can suggest you the option boarddiag (open phone) and jtag.
Click to expand...
Click to collapse
Yes I have a warranty. But I had installed a custom ROM (cloudy g3), so I guess that violates mine. The phone is dead, and shows up in device manager as LGE AndroidNet USB Serial Port. Don't even know why its showing up like that
Okay, am i'm searching for any available software fix that's gonna work for me at least before I resort to opening up the phone
Let me shed some light on what caused my phone to go dark, to save someone else from repeating the same mistake... I was trying to upgrade twrp from version 2.8 to 3.0. I thought using autorec would help me achieve that. But once it had finished, I attempted to boot to recovery and since then my phone has gone completely dark
OK, you could try to carry the cellphone to LG support and you can tell that after an upgrade, your phone has not returned to turn on. Usually, they change the motherboard. If you want to do it through BoardDiag, here is an explanation:
http://forum.xda-developers.com/showpost.php?p=65003040&postcount=300
cesarandres_8911 said:
OK, you could try to carry the cellphone to LG support and you can tell that after an upgrade, your phone has not returned to turn on. Usually, they change the motherboard. If you want to do it through BoardDiag, here is an explanation:
http://forum.xda-developers.com/showpost.php?p=65003040&postcount=300[/url]
Click to expand...
Click to collapse
Thanks for your help. Ive been able to get my phone to 9008 mode. So, am getting the part where I have to use the boarddiag tool, but am abit confused. What should be the value of my target dir, and AP chipset?. For the chipset, i'm thinking I should use the value that's similar to the one at this guide
http://forum.xda-developers.com/spr....
My phone is an LG g3 d855, so please guide
antony990 said:
Thanks for your help. Ive been able to get my phone to 9008 mode. So, am getting the part where I have to use the boarddiag tool, but am abit confused. What should be the value of my target dir, and AP chipset?. For the chipset, i'm thinking I should use the value that's similar to the one at this guide
http://forum.xda-developers.com/spr...and "TARGET DIR" should be the same location.
Click to expand...
Click to collapse
cesarandres_8911 said:
The first thing you should do is download the .tot file corresponding to your Variant (D855), I think that you can find it here: http://forum.xda-developers.com/lg-g3/help/tot-dll-file-d855-t2859828
Follow this guide to use boarddiag:
http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
In the "Image EXTRACTION" sections, in "BIN" must locate the file .tot that you downloaded.
In "DIR" you put the location where will be extracted the content of the .tot file.
Note that "DIR" and "TARGET DIR" should be the same location.
Click to expand...
Click to collapse
Yes. Iam following the guide you provided. But am stuck at this error. Check the image attached
antony990 said:
Yes. Iam following the guide you provided. But am stuck at this error. Check the image attached
Click to expand...
Click to collapse
And then, every time I unplug the device and plug it back into the PC, the device ends up being undetected by windows, and I have to redo the shorting procedure again. Is this normal behaviour, or something is wrong??
Also, when I put the battery back, and plug the device, it shows up as LGE androidnet usb
Anyone explain to me what this means. Please check the image attached
antony990 said:
Anyone explain to me what this means. Please check the image attached
Click to expand...
Click to collapse
I have the same error, and have tried about everything including 4 different computers and OSs, different cables, different versions of BoardDiag 2.99a - 3.99c, and still the same error.
singingandroid said:
I have the same error, and have tried about everything including 4 different computers and OSs, different cables, different versions of BoardDiag 2.99a - 3.99c, and still the same error.
Click to expand...
Click to collapse
It could also mean your device isn't in EDL mode 9008.
TheMadScientist said:
It could also mean your device isn't in EDL mode 9008.
Click to expand...
Click to collapse
I believe I am in the right 9008 mode. Screenshot is attached.
singingandroid said:
I believe I am in the right 9008 mode. Screenshot is attached.
Click to expand...
Click to collapse
I had be not dealt with edl on LG in a long time been on Samsung for a while that being said i could suggest maybe be uninstall the current 9008 driver and try to find a different source or updated and or try other usb ports. We on s8 have a lot of issues with usb 3.0 ports on pc's
TheMadScientist said:
I had be not dealt with edl on LG in a long time been on Samsung for a while that being said i could suggest maybe be uninstall the current 9008 driver and try to find a different source or updated and or try other usb ports. We on s8 have a lot of issues with usb 3.0 ports on pc's
Click to expand...
Click to collapse
Yeah, I've tried pretty much everything, but thank you for the reply.
i was trying to flash lollipop rooted stuck room via qpst i was in download mood connected the phone and it reads as 9008 and i press download .. everything was fine it was loading system.img and i got this error
it says download fail firehose fail firehose fail download finish .
after this the phone is not responding to any key i press and it doesn't show when i connect it to pc and qpst can't see the device also .. i don't know what to do to unbrick it .. pls help
mohamed_ragab09 said:
i was trying to flash lollipop rooted stuck room via qpst i was in download mood connected the phone and it reads as 9008 and i press download .. everything was fine it was loading system.img and i got this error
it says download fail firehose fail firehose fail download finish .
after this the phone is not responding to any key i press and it doesn't show when i connect it to pc and qpst can't see the device also .. i don't know what to do to unbrick it .. pls help
Click to expand...
Click to collapse
Can you get into download mode?
i tried to press power + volume uo or down but nothing happen
mohamed_ragab09 said:
i tried to press power + volume uo or down but nothing happen
Click to expand...
Click to collapse
Press voulme up and connect to pc.
is there a way to get into fastboot other than power+volume down ?
via adb or something ?
mohamed_ragab09 said:
i tried to press power + volume uo or down but nothing happen
Click to expand...
Click to collapse
Try volume up+connect phone to PC. If it isn't detected try charging it for 30 minutes and then the same thing. If that doesn't work try a different USB cable and/or different USB port on your PC.
i will try and get back to you .. thank you so much i appreciate your help
mohamed_ragab09 said:
i will try and get back to you .. thank you so much i appreciate your help
Click to expand...
Click to collapse
Any news?
NeptunePH said:
Try volume up+connect phone to PC. If it isn't detected try charging it for 30 minutes and then the same thing. If that doesn't work try a different USB cable and/or different USB port on your PC.
Click to expand...
Click to collapse
i tried with no luck the phone cant be detected although it was being detected before the failed flashing attempt .. can windows 10 64 bit be the problem here ? what else can i do to unbrick the phone ?
and i get a message that the usb not recognized or malfunctioned
mohamed_ragab09 said:
and i get a message that the usb not recognized or malfunctioned
Click to expand...
Click to collapse
That sounds exactly like the situation I had. Your motherboard is probably fried. Get it to your service center. Especially if you have the warranty.
NeptunePH said:
That sounds exactly like the situation I had. Your motherboard is probably fried. Get it to your service center. Especially if you have the warranty.
Click to expand...
Click to collapse
im out of warranty .. is there is another way ? what did you do ?
in another note : i gave it to a friend who understand some maintenance and he managed make the device readable when you connect it to pc .. and it was showing 9008 on his pc .. but when i took it home and connect it to mine it shows the first time but then it started to show me usb not recognized again after i removed it .. i don't know what this means .. i gave it back to him to try make it readable again .. his pc is win 7 .. mine is win 10 .. what do you make of that ?
mohamed_ragab09 said:
im out of warranty .. is there is another way ? what did you do ?
in another note : i gave it to a friend who understand some maintenance and he managed make the device readable when you connect it to pc .. and it was showing 9008 on his pc .. but when i took it home and connect it to mine it shows the first time but then it started to show me usb not recognized again after i removed it .. i don't know what this means .. i gave it back to him to try make it readable again .. his pc is win 7 .. mine is win 10 .. what do you make of that ?
Click to expand...
Click to collapse
I was in the same situation. For me sometimes I got port 9008 and sometimes USB device not recognized. However every time I got a Sahara Fail. Keep trying to flash the s288 row with different cables/ports. That's all I can think of.
NeptunePH said:
I was in the same situation. For me sometimes I got port 9008 and sometimes USB device not recognized. However every time I got a Sahara Fail. Keep trying to flash the s288 row with different cables/ports. That's all I can think of.
Click to expand...
Click to collapse
what exactly did work for you ?
mohamed_ragab09 said:
what exactly did work for you ?
Click to expand...
Click to collapse
I tried every method possible but nothing worked. Since I was under warranty I took it to a service center where they told me the Motherboard was fried.
Oppssss mother board fried.... Im listening this first time.
he managed to make it readable again and we flashed the rom on his pc .. it went will and my p1 is on again .. thank you for the help
hi can you be speciific
mohamed_ragab09 said:
he managed to make it readable again and we flashed the rom on his pc .. it went will and my p1 is on again .. thank you for the help
Click to expand...
Click to collapse
HI.. can you get from your friend a step by step guide so that it can be useful for everyone facing the same problem..??
venkat7117 said:
HI.. can you get from your friend a step by step guide so that it can be useful for everyone facing the same problem..??
Click to expand...
Click to collapse
he just said he heated on the memory chips or something like that .. apparently the flashing problem was my win 10 device . because once the phone show 9008 com on flashing software the flash process went ok on his win 7 device
There's another thing that I would like to add. When the flashing fails and phone becomes dead(seems dead), it is not in a powered off state i.e. it actually is in a dormant state in some occasions. That is, it doesn't respond to any actions performed like plugging to pc, plugging charger e.t.c.
For older phones with a removable battery, we could simply remove the battery and turn the phone off completely before trying to flash again.
But since newer phones like our Vibe P1 doesn't have a removable battery, we need to switch the phone off manually.
There is a method for that given in this link.
Hi Guys,
Yesterday during an official update of my oneplus 5t (using the update manager from the phone itself), the phone got bricked and i dont know why....
So after some research i found it is hard bricked ( basically i cant do nothing, power on i cant, power +volume UP/DOWN too, and even when i plug the charge cable i have neither vibrations nor LED on)
So i follow this tutorial to unbrick the phone:
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
I could get the phone recognize by the PC by pressing UP to see the phone as QUSB-BULK and then QUALCOMM QD LOADER after driver's update.
But when i run MSMDownloadTool ( V4.0.27 dumpling 43_0.36_180613) as administrator and click on start, the process get stuck in "waiting for device"
the status of connection before click on start was "connected" and after click and some process it turn to N/A
the status of communication is "memory size....."
status of last communication is "waiting for device"
I have tried several time and always the same result..... stuck in the waiting device
does someone have an idea on how to solve this? because i really need to unbrick the phone....
thank you in advance
EDIT:
I tried another version of MsmDownloadTool (dumpling_43_O.06_171206) and this time, the downloading of cache image failed....
I dont know what to do
You were in a custom rom or kernel when you tried to update from the official channel?
Your phone was rooted? Magisk installed?
Battery percentage?
DaRk-L0rD said:
You were in a custom rom or kernel when you tried to update from the official channel?
Your phone was rooted? Magisk installed?
Battery percentage?
Click to expand...
Click to collapse
Thanks for reply.
No i was on official oxygen OS, not rooted or custom installed and when i start to download the update, i was 80%.
rokusho32 said:
Thanks for reply.
No i was on official oxygen OS, not rooted or custom installed and when i start to download the update, i was 80%.
Click to expand...
Click to collapse
Thing are much easier with the unlocked bootloaders!
Charge your phone all night long even if you don't see any sign of life (green or red led light).
Then hold together the Volume UP button and the power button for few seconds into the fastboot mode (hold both buttons for at least 10 seconds) and let me know.
DaRk-L0rD said:
Thing are much easier with the unlocked bootloaders!
Charge your phone all night long even if you don't see any sign of life (green or red led light).
Then hold together the Volume UP button and the power button for few seconds into the fastboot mode (hold both buttons for at least 10 seconds) and let me know.
Click to expand...
Click to collapse
I tried this before and nothing happened....
then when i connect to the pc by pressing UP+ power button, the pc detected it as QUSB_BULK then i install the qualcomm driver and finally i could see the phone in the usb device.
But after MSMDownloadTool step, the process got stuck and display "memory size" as explained in the thread.
rokusho32 said:
Thanks for reply.
No i was on official oxygen OS, not rooted or custom installed and when i start to download the update, i was 80%.
Click to expand...
Click to collapse
rokusho32 said:
I tried this before and nothing happened....
then when i connect to the pc by pressing UP+ power button, the pc detected it as QUSB_BULK then i install the qualcomm driver and finally i could see the phone in the usb device.
But after MSMDownloadTool step, the process got stuck and display "memory size" as explained in the thread.
Click to expand...
Click to collapse
Go here:
https://forum.xda-developers.com/showpost.php?p=74504343&postcount=3
Follow the instructions for the adb drivers installation.
Once done that, let me know
DaRk-L0rD said:
Go here:
https://forum.xda-developers.com/showpost.php?p=74504343&postcount=3
Follow the instructions for the adb drivers installation.
Once done that, let me know
Click to expand...
Click to collapse
I have installed the ADB drivers
which version of MSMDownloadTool should i use?
DaRk-L0rD said:
You were in a custom rom or kernel when you tried to update from the official channel?
Your phone was rooted? Magisk installed?
Battery percentage?
Click to expand...
Click to collapse
I know this is an old thread, but I'm hoping you have an idea. I have bricked my rooted OnePlus6. I did have Magisk installed. Bootloader was unlocked. I was able to factory reset the phone, but the bootloader was still locked (I had TWRP installed and factory reset using it). I then used Fastboot to relock the bootloader, and that's when my troubles started. I could only get into Fastboot. I found a solution on the web, installed the Qualcomm drivers (and they recognize my device, which I connected by holding down the volume up button before connecting to the USB cable), and started the OnePlus 6 (MSM) unbrick tool. However, it just sits there saying "waiting for device". I actually seem to have two entries for the device, one saying Index and one saying "1" (although I think the device is on COM3). Should it take forever? How can I get it past "Waiting for device". Thanks.
rcbjr2 said:
I know this is an old thread, but I'm hoping you have an idea. I have bricked my rooted OnePlus6. I did have Magisk installed. Bootloader was unlocked. I was able to factory reset the phone, but the bootloader was still locked (I had TWRP installed and factory reset using it). I then used Fastboot to relock the bootloader, and that's when my troubles started. I could only get into Fastboot. I found a solution on the web, installed the Qualcomm drivers (and they recognize my device, which I connected by holding down the volume up button before connecting to the USB cable), and started the OnePlus 6 (MSM) unbrick tool. However, it just sits there saying "waiting for device". I actually seem to have two entries for the device, one saying Index and one saying "1" (although I think the device is on COM3). Should it take forever? How can I get it past "Waiting for device". Thanks.
Click to expand...
Click to collapse
I have same situation.. did you resolve this problem?
piechu11 said:
I have same situation.. did you resolve this problem?
Click to expand...
Click to collapse
I contacted OnePlus and I sent them the phone and they reinstalled the operating system. I was never able to fix it myself. I even had an online session with OnePlus and they couldn't get the MSM software to recognize the phone (even though it was truly connected to my laptop). I also had an issue with my OnePlus 8T that got messed up doing something with Magisk, and OnePlus reinstalled the operating system as well. I still can't boot from the A partition though; just the B partition.
piechu11 said:
I have same situation.. did you resolve this problem?
Click to expand...
Click to collapse
Okay, for anyone facing same problem as me, i found solution (working for me). Before using MSM Tool, you need to install Qualcomm USB Drivers.
During instalation you need to choose second option "ETHERNET-DHCP"!
At first, I chose WWAN-DHCP - which caused problem with connection
piechu11 said:
Okay, for anyone facing same problem as me, i found solution (working for me). Before using MSM Tool, you need to install Qualcomm USB Drivers.
During instalation you need to choose second option "ETHERNET-DHCP"!
View attachment 5511425
At first, I chose WWAN-DHCP - which caused problem with connection
Click to expand...
Click to collapse
Thank you this solved my problem exactly.
i was restoring my metro by tmobile oneplus nord n10 BE2025 model with build tag BE88CF
I was doing some experiment with DriveDroid and now I am in big mess.
I think I messed up with drivedroid settings and I was not able to see my phone (oneplus 3 rooted LOS 15.1 ) on my computers.
I have tried different computers but all cant detect my phone.
I have tried drivedroid wizard, different usb systems, different usb settings and no luck.
I have tried uninstalling the drivedroid and still no luck.
The phone was going in charging mode only. Its was not going to MTP mode so I can see the phone internal storage in computer
I have tried to do factory reset also but no luck.
Now I mistakenly wiped data partition also and now the phone is with
No OS
No USB detection on phone while in TWRP
No OTG detection
No any ROM.zip file in phone memory.
When I am on TWRP and connect my phone in computer I am seeing same error message and cant see my phone interenal storage.
Now what to do? Any way to flash ROM ?
I am in big mess, and I dont want to spend money on new phone as of now
I hope someone will be my angle and suggest me something to recover and save me from this mess...
Crying out loud now...
Hi, i think you can use adb sideload with twrp
Uruloki64 said:
Hi, i think you can use adb sideload with twrp
Click to expand...
Click to collapse
Phone is not recognized in computer while in twrp mode so it is not able to connct to adb via USB.
Just get os flashed at OnePlus service center.
I did something same in my previous Samsung phone. I took it to service center and told em that it's not booting up and I don't know the reason. They flashed the firmware from scratch, charged me 250 INR and my phone was back to being normal.
aj141 said:
Just get os flashed at OnePlus service center.
I did something same in my previous Samsung phone. I took it to service center and told em that it's not booting up and I don't know the reason. They flashed the firmware from scratch, charged me 250 INR and my phone was back to being normal.
Click to expand...
Click to collapse
Ya.. going there tomorrow. Lets see what they say about it.
amit3880 said:
Ya.. going there tomorrow. Lets see what they say about it.
Click to expand...
Click to collapse
have u tried hard bricked tool for OP3? if not then try it
https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Hayatzada said:
have u tried hard bricked tool for OP3? if not then try it
https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Click to expand...
Click to collapse
I am not able to follow this as phone is not even coming in USB mode. So its actually soft bricked because can go to twrp and fastboot mode and booting up without OS but USB is not able to detect on my computer.
now the service center guys saying I need to change the motherboard which I dont think is the issue, mother board is not going gone for sure as I can boot up in twrp and fastboot mode. its just may be the usb host controller gone.
Cant decide if I should go ahead with mother board replacement at cost of 10k INR ( phone cost was 28K INR) .
amit3880 said:
I am not able to follow this as phone is not even coming in USB mode. So its actually soft bricked because can go to twrp and fastboot mode and booting up without OS but USB is not able to detect on my computer.
now the service center guys saying I need to change the motherboard which I dont think is the issue, mother board is not going gone for sure as I can boot up in twrp and fastboot mode. its just may be the usb host controller gone.
Cant decide if I should go ahead with mother board replacement at cost of 10k INR ( phone cost was 28K INR) .
Click to expand...
Click to collapse
If you use the Method 2 of the Unbrick Guide, you don't need normal adb/usb mode recognition. Follow that guide scrupulously and step by step. Don't skip any and don't rush.
tnsmani said:
If you use the Method 2 of the Unbrick Guide, you don't need normal adb/usb mode recognition. Follow that guide scrupulously and step by step. Don't skip any and don't rush.
Click to expand...
Click to collapse
We are giving an advice of 10K InR in free and he is not even interested according to his opinion,
Hayatzada said:
We are giving an advice of 10K InR in free and he is not even interested according to his opinion,
Click to expand...
Click to collapse
I even tried that but somehow it is not even recognized as QHUSB_BULK device.
believe me I have tried all things to revive the phone but its not hard brick in my opinion, it can boot into twrp but the when I connect the phone in computer it shows the error message I shown as attachment in my first post.
yes, I have tried 2 different computers and few usb cables.
amit3880 said:
I even tried that but somehow it is not even recognized as QHUSB_BULK device.
believe me I have tried all things to revive the phone but its not hard brick in my opinion, it can boot into twrp but the when I connect the phone in computer it shows the error message I shown as attachment in my first post.
yes, I have tried 2 different computers and few usb cables.
Click to expand...
Click to collapse
Your phone need not be hardbricked to use the Guide. It will work even on a normal perfectly working phone. If your phone is not recognised while following the Guide, it only means one of two things: either it is a hardware fault or you are not following the Guide properly.
amit3880 said:
I even tried that but somehow it is not even recognized as QHUSB_BULK device.
believe me I have tried all things to revive the phone but its not hard brick in my opinion, it can boot into twrp but the when I connect the phone in computer it shows the error message I shown as attachment in my first post.
yes, I have tried 2 different computers and few usb cables.
Click to expand...
Click to collapse
reviewed post
tnsmani said:
Your phone need not be hardbricked to use the Guide. It will work even on a normal perfectly working phone. If your phone is not recognised while following the Guide, it only means one of two things: either it is a hardware fault or you are not following the Guide properly.
Click to expand...
Click to collapse
tried to follow the unbrick guide on windows 10 but phone is not seen as QSBULK device in device manager.
I am going to try on windows 7 as few post said that windows 7 would be better for unbricking than windows 10.
finger crossed, right now flashing windows 7 live iso on USB.
so finally I am declaring my op3 as hardware failure as one of my other phone (yureka) easily identified as 9008 mode in my computer but my op3 is not. so all drivers are installed correctly but somehow my op3's usb hub is failed.
i guess time to move on..
thank you everyone for spending time to help me. it really is supportive and encouraging...
amit3880 said:
so finally I am declaring my op3 as hardware failure as one of my other phone (yureka) easily identified as 9008 mode in my computer but my op3 is not. so all drivers are installed correctly but somehow my op3's usb hub is failed.
i guess time to move on..
thank you everyone for spending time to help me. it really is supportive and encouraging...
Click to expand...
Click to collapse
So sorry about that .... Sad news
@Ammit3880
have you tried plugging in a usb in you phone trough the usb OTG cable? see if twrp recognizes the usb. and just put the needed files on there. maybe windows is just breing ignorant as always
BADA 187 said:
@Ammit3880
have you tried plugging in a usb in you phone trough the usb OTG cable? see if twrp recognizes the usb. and just put the needed files on there. maybe windows is just breing ignorant as always
Click to expand...
Click to collapse
ya.. tried all the ways including various OTG cabel/dongle,, various OS windows 7/8/8.1/10 all the way..
nothing working...
amit3880 said:
ya.. tried all the ways including various OTG cabel/dongle,, various OS windows 7/8/8.1/10 all the way..
nothing working...
Click to expand...
Click to collapse
damn sorry to hear man.
BADA 187 said:
damn sorry to hear man.
Click to expand...
Click to collapse
Got 6T yesterday.... .. Yay!!
Couldnt find other phone competative in the price range.
Time to change the xda signature...
Although I bought 6T now and am kind of happy with that, but I am still missing my oneplus 3 and want to experiment on getting it revived.
By any chance someone can help me answering my doubts.. I would be greatful..
1. Is it ok to replace oneplus3's motherboard with oneplus 3t motherboard ? If by any chance i get any resell op3 or op3t in dirt cheap price I want to know if its ok to use 3T's motherboard.
2. Is there any way I can turn on the wifi from within TWRP and so I can connect to phone via adb over wifi/tcpip ??
Thank you all in advance.