Develop Bugs

I think ive bricked my phone?

Sup everyone
ive completly done a **** up whist trying to flash my phone with android hd rom.
ive actually put the wrong zip on to the phone and now has wiped my phone and wont boot up.
i can access recovery mode but the phone will not boot up. it gets stuck on google.
if i try to mount usb storage i get a error :
Unable to open ums lunfile (no such file or directory)
Is there a way around this PLS?

jeezy85 said:
Sup everyone
ive completly done a **** up whist trying to flash my phone with android hd rom.
ive actually put the wrong zip on to the phone and now has wiped my phone and wont boot up.
i can access recovery mode but the phone will not boot up. it gets stuck on google.
if i try to mount usb storage i get a error :
Unable to open ums lunfile (no such file or directory)
Is there a way around this PLS?
Click to expand...
Click to collapse
How this post belongs in dev area???
Go to android hd rom and ask your question or post it in Q&A!!!!
Come on

how do i delete this thread?

jeezy85 said:
how do i delete this thread?
Click to expand...
Click to collapse
Mods going to move it or if you ask they are going to delete it.Please read forum rules before posting

Flash stock images in fast boot. You can't mount USB storage on this phone anyways.
Sent from my Galaxy Nexus using xda premium

happen to me too....
I flashed an Pauls update instead of core and messed my phone up.
flash stock image then use ADB and push the rom to the sd/update.zip - then flash.
That should fix it.

You're phone is not bricked. Reflash the factory images using fastboot. http://groups.google.com/group/andr...hread/2dde45a058a737b9/43c3a418144fc6c5?pli=1

thanks for the replies really appreciate it
just to clarify
is fastboot mode recovery mode?

jeezy85 said:
thanks for the replies really appreciate it
just to clarify
is fastboot mode recovery mode?
Click to expand...
Click to collapse
Hold the Volume Up Key + Volume Down Key and then press the Power button.

jeezy85 said:
thanks for the replies really appreciate it
just to clarify
is fastboot mode recovery mode?
Click to expand...
Click to collapse
fastboot is fastboot recovery is recovery
Yeah, what Stea1thmode said
fastboot is a bit more lower level [i think] than recovery

pulling my hair out lol
im completly lost
ive downloaded the stock image... just dont know how to flash it

First of all naughty naughty please do not post questions in the development forum. I moved it over to Q&A
Ok now thats over with follow *THIS* guide to get fastboot drivers set up on your pc. Some users spend hours trying to figure it out (myself included the first time) and that guide is detailed. Install the pdanet program on your comp to get the needed drivers then boot your phone into fastboot mode and connect to your pc via usb cable. If it doesnt install the automatically then you can do it manually via the Device Manager.
Once the drivers are installed open up a command prompt and goto the folder you put the fastboot.exe file in. Type fastboot devices and it should return a number which means your phone is recognised.
Next goto *THIS* thread and follow the instructions to fastboot the Stock images back to your device and restore your phone.
Once everything is back and working READ every instruction thoroughly before doing anything in future Luckily this phone is next to impossible to brick
Mark.

thank you so much for pointing me in the right direction...
things seem to be getting worse..
im having trouble installing drivers.. (windows 7)
it keeps failing :S

jeezy85 said:
thank you so much for pointing me in the right direction...
things seem to be getting worse..
im having trouble installing drivers.. (windows 7)
it keeps failing :S
Click to expand...
Click to collapse
I have windows 7 too so it will work its just a pain to get them on.
Did you install the pdanet drivers to your pc? Did you update the drivers in the Device Manager? Please list your exact procedure you followed and where you are getting stuck.
Mark.

ok my phone gets stuck on the google sign...
if plug in my phone the comp detects it.. it starts installing the drivers Samsung mobile MTP Drivers.. then all of a sudden it says failed....i also installed Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0.exe
still no luck
i tried installing the pdanet program but it doesnt detect the phone as it doesnt boot up?

jeezy85 said:
ok my phone gets stuck on the google sign...
if plug in my phone the comp detects it.. it starts installing the drivers Samsung mobile MTP Drivers.. then all of a sudden it says failed....i also installed Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0.exe
still no luck
i tried installing the pdanet program but it doesnt detect the phone as it doesnt boot up?
Click to expand...
Click to collapse
Why are you trying to boot up the phone if you know it doesnt boot?
You need to do everything through the fastboot screen. Hold Volume Up and Volume Down buttons while pressing the power button until the big green Android icon appears and it will say fastboot on the screen.
Have your Device Manager open (from settings on your pc) so that you can dee the item pop up in the list that you need to update the driver for.
PdaNet drivers are the best ones that work for fastboot.
Mark.

when i go into fastboot mode.. then go to device manager the only thing i can see with a explanation mark is android 1.0.....
theres no samsung device or nothing

jeezy85 said:
when i go into fastboot mode.. then go to device manager the only thing i can see with a explanation mark is android 1.0.....
theres no samsung device or nothing
Click to expand...
Click to collapse
Yes thats the item you need to update the driver for.
Make sure you have installed the samsung drivers (and maybe pdanet drivers if you want to be safe) on your pc first. Then double click on the Android 1.0 item and then select Driver, Update Driver. Click Browse My Computer and then Let me pick from a list.
It should give you a few options. If you see it then select Android Adb Device but if not try one odf the samsung adb interface drivers.
Mark.

mskip i LOVE YOU!!!
starting to get somewhere got the drivers installed...
ok i typed this command in cmd where the stock img is
fastboot-windows flash all flash-all.sh
i get this
sending 'all'<0 KB>....OKAY
writing 'all'.....FAILED <remote : Unkown Partition>
Any ideas?

try just flashing the image zip.
Code:
fastboot -w update image-yakju-itl41f.zip

[Q] Can't boot phone after upgrade - CyanogenMod 10.2 Stable

Hey guys,
So the problem I'm experiencing is that my HTC One X is stuck in a boot loop after I applied an update to CyanogenMod 10.2 Stable that I saw in the settings menu. Dumb mistake.
I've tried reading up on the issue but I'm posting here because I want to make sure I don't brick the phone. I bought the phone second hand, already rooted and flashed, so my knowledge on this stuff is extremely limited.
So here's some info:
1. I can access a boot menu when I hold the power and volume down button.
2. From there I can access ClockworkMod Recovery v5.8.4.0
3. I've tried restoring the phone
4. I found and applied the 2 zips that are already in the sd card. The old one: CM 10.1 and CM 10.2. - Both of them get stuck in boot.
5. I've downloaded Fastboot and ADB to my computer.
6. I tried to follow the instructions in this thread: http://forum.xda-developers.com/showthread.php?t=2617301. Fastboot can't find my device (fastboot getvar cid -> waiting for device). I should mention that I mounted /sdcard and also tried mounting 'USB storage' but that didn't seem to do anything.
I also found this thread that might be of help once I get the computer to see my phone: http://forum.cyanogenmod.com/topic/...01-to-102-if-you-get-stuck-at-boot-animation/

ChrisGiggles said:
Hey guys,
So the problem I'm experiencing is that my HTC One X is stuck in a boot loop after I applied an update to CyanogenMod 10.2 Stable that I saw in the settings menu. Dumb mistake.
I've tried reading up on the issue but I'm posting here because I want to make sure I don't brick the phone. I bought the phone second hand, already rooted and flashed, so my knowledge on this stuff is extremely limited.
So here's some info:
1. I can access a boot menu when I hold the power and volume down button.
2. From there I can access ClockworkMod Recovery v5.8.4.0
3. I've tried restoring the phone
4. I found and applied the 2 zips that are already in the sd card. The old one: CM 10.1 and CM 10.2. - Both of them get stuck in boot.
5. I've downloaded Fastboot and ADB to my computer.
6. I tried to follow the instructions in this thread: http://forum.xda-developers.com/showthread.php?t=2617301. Fastboot can't find my device (fastboot getvar cid -> waiting for device). I should mention that I mounted /sdcard and also tried mounting 'USB storage' but that didn't seem to do anything.
I also found this thread that might be of help once I get the computer to see my phone: http://forum.cyanogenmod.com/topic/...01-to-102-if-you-get-stuck-at-boot-animation/
Click to expand...
Click to collapse
Download htc sync it will install the drivers required ,then you're good to go

When you install drivers..Go to recovery wipe everything except battery stats and storage..Then flash cm10.2 zip and then gapps..Then flash boot.img and erase cache..
Sent from my HTC One X using Tapatalk 2

Muksleo said:
Download htc sync it will install the drivers required ,then you're good to go
Click to expand...
Click to collapse
Ok, I'm back from trying that. On my old PC laptop the software just failed to install. I'm trying again... takes forever to install.
I also downloaded it for my Mac, that worked fine but it doesn't actually find the phone when connected.
EDIT: POS computers... The Windows one throws up a weird error, no explanation, just a bunch of numbers. The Mac one is just incompetent...

What windows do you have?? 7,8.1 install drivers automatically..

big noob said:
What windows do you have?? 7,8.1 install drivers automatically..
Click to expand...
Click to collapse
The PC is running Windows 7... but neither of my computers recognize the phone (or mount the storage) through the USB.
I'm f*cked I think.
EDIT: Yep, I got the HTC sync to install finally on the Windows PC. And as I suspected, it doesn't recognize my phone.

So I guess my problem now is that the phone doesn't actually mount. I've never connected it to a computer before so I don't know if this is a new problem or not.
I've tried 2 computers and 2 different cables. I guess the phone is essentially bricked now? So much for "stable" update...

ChrisGiggles said:
So I guess my problem now is that the phone doesn't actually mount. I've never connected it to a computer before so I don't know if this is a new problem or not.
I've tried 2 computers and 2 different cables. I guess the phone is essentially bricked now? So much for "stable" update...
Click to expand...
Click to collapse
Restart your computer after driver installation
after that go where u have fastboot folder press shift and right click and click on open command window here
there u can give fastboot commands

Muksleo said:
Restart your computer after driver installation
after that go where u have fastboot folder press shift and right click and click on open command window here
there u can give fastboot commands
Click to expand...
Click to collapse
Thanks but that's exactly what I've been doing.

Well,did you try to remove all installed drivers..And let Windows install drivers..That always works for me..
Sent from my HTC One X using Tapatalk 2

[Q] Can't boot normally with TWRP

Hi. I recently rooted my phone Xperia S (LT26i) and unlocked its bootloader. I had installed CWM and TWRP recovery in the phone and I have ADB and Fastboot(Android SDK) in my computer. I had earlier flashed CWM but it wasn't working so I flashed TWRP. I had downloaded a custom ROM and Gapps in the PC and I extracted the zip files and copied them into the phone (this was a mistake). I went into TWRP and did factory reset, erased cache and wiped dalvik cache unknowingly:silly: Now I can't flash ROM or Gapps and I cannot boot normally. Earlier, ADB used to recognize the device and now it doesn't. When I turn on the phone, the Sony logo appears and pink light glows. But it doesn't go beyond that. It repeatedly restarts the phone till the splash screen. Now I can't boot the phone normally Please help, guys.
P.S. I saw a post suggesting to enter a code in the Terminal module of TWRP but it's not working.

Megaiamepic said:
Hi. I recently rooted my phone Xperia S (LT26i) and unlocked its bootloader. I had installed CWM and TWRP recovery in the phone and I have ADB and Fastboot(Android SDK) in my computer. I had earlier flashed CWM but it wasn't working so I flashed TWRP. I had downloaded a custom ROM and Gapps in the PC and I extracted the zip files and copied them into the phone (this was a mistake). I went into TWRP and did factory reset, erased cache and wiped dalvik cache unknowingly:silly: Now I can't flash ROM or Gapps and I cannot boot normally. Earlier, ADB used to recognize the device and now it doesn't. When I turn on the phone, the Sony logo appears and pink light glows. But it doesn't go beyond that. It repeatedly restarts the phone till the splash screen. Now I can't boot the phone normally Please help, guys.
P.S. I saw a post suggesting to enter a code in the Terminal module of TWRP but it's not working.
Click to expand...
Click to collapse
I'v got almost similar problem right now, but beyond that I'v flashed custom kernel to mine.
I hope someone will post here soon
edit: the kernel name is Open SEMC
but I think I can get to fast boot, so changing kernel should not be problem. But how to get some ROM to the phone, when I can't connect it anyhow?

Megaiamepic said:
Earlier, ADB used to recognize the device and now it doesn't. When I turn on the phone, the Sony logo appears and pink light glows. But it doesn't go beyond that. It repeatedly restarts the phone till the splash screen. Now I can't boot the phone normally Please help, guys.
P.S. I saw a post suggesting to enter a code in the Terminal module of TWRP but it's not working.
Click to expand...
Click to collapse
What do You menan by now not recognizing in adb? While being in adb? Are You able to boot to twrp?
fipsix said:
I'v got almost similar problem right now, but beyond that I'v flashed custom kernel to mine.
I hope someone will post here soon
edit: the kernel name is Open SEMC
but I think I can get to fast boot, so changing kernel should not be problem. But how to get some ROM to the phone, when I can't connect it anyhow?
Click to expand...
Click to collapse
If You both are able to boot into recovery(twrp), I recommend You boot into twrp, connect the phone to pc. Then Let the drivers install. After it, start the adb, use this command to command to check if Your device is connected:
Code:
adb devices
Copy the ROM zip to the folder of adb.
Then push the file to sdcard using:
Code:
adb push finlename.zip /sdcard
where filename.zip is Your ROM.

Mirhawk said:
What do You menan by now not recognizing in adb? While being in adb? Are You able to boot to twrp?
If You both are able to boot into recovery(twrp), I recommend You boot into twrp, connect the phone to pc. Then Let the drivers install. After it, start the adb, use this command to command to check if Your device is connected:
Code:
adb devices
Copy the ROM zip to the folder of adb.
Then push the file to sdcard using:
Code:
adb push finlename.zip /sdcard
where filename.zip is Your ROM.
Click to expand...
Click to collapse
I tried using the adb command but it says "error device not found"

Megaiamepic said:
I tried using the adb command but it says "error device not found"
Click to expand...
Click to collapse
You are using windows, right? Do You see the phone connected in the "Device Manager"? It might but under "Other Devices" by the name "Sony Xperia S"

Mirhawk said:
You are using windows, right? Do You see the phone connected in the "Device Manager"? It might but under "Other Devices" by the name "Sony Xperia S"
Click to expand...
Click to collapse
That's what I've done in the end. Bud I had problem with drivers for my xperia, it seemed that drivers were wrong or something. So I uninstalled them, downloaded new one and voila :good:

fipsix said:
That's what I've done in the end. Bud I had problem with drivers for my xperia, it seemed that drivers were wrong or something. So I uninstalled them, downloaded new one and voila :good:
Click to expand...
Click to collapse
Do post which drivers You installed with a link. It might help the other member.

Mirhawk said:
Do post which drivers You installed with a link. It might help the other member.
Click to expand...
Click to collapse
Ooh sorry, totally forgot about that. I dont have direct link, but I will upload them somewhere tommorow.

drivers
I hope those are the right ones, because I donwloaded tons of em
http://ulozto.cz/x4tSiM6N/drivers-fastboot-adb-flashtool-by-velcis-ribeiro-rar

HTC One Won't Start Up

So I was running a custom ROM for a while and decided to switch back to the stock ROM. After doing that, I flashed the stock recovery so that I could install the OTA update from version 4.28.502.2 to version 6.20.502.5. During installation, the phone got stuck in a bootloop, so I wiped the cache and tried to start it again. After that didn't work, I factory reset it (in the bootloader, and then in recovery after it didn't work), and it still doesn't work. ADB and fastboot doesn't detect my device even though I had USB debugging on before I tried to update it (I'm guessing that the factory reset disabled that?). I can access the bootloader and recovery, and my phone has an unlocked bootloader with S-On. I have the AT&T HTC One M8 if that helps. Can someone help me please?

Hi,
Can you go to boot loader and then connect your phone into your computer after that you flash the recovery like TWRP, wipe all the data and reflash your rom, you can find it on XDA. After that you have to find the correct recovery for your device (see the website of Mike1987), find the correct recovery for your device and then flash the stock recovery and it have to work. Waiting for your news.
Have a nice day

BelDev said:
Hi,
Can you go to boot loader and then connect your phone into your computer after that you flash the recovery like TWRP, wipe all the data and reflash your rom, you can find it on XDA. After that you have to find the correct recovery for your device (see the website of Mike1987), find the correct recovery for your device and then flash the stock recovery and it have to work. Waiting for your news.
Have a nice day
Click to expand...
Click to collapse
I'm saying that my computer doesn't recognize my phone, and that's why I can't flash a custom recovery like TWRP

Have you got the right drivers installed, have you tired another hub ? Is your battery fully charged ?

BelDev said:
Have you got the right drivers installed, have you tired another hub ? Is your battery fully charged ?
Click to expand...
Click to collapse
Yes, I have the right drivers installed. Yes, I have tried a different USB port. Yes, my battery is fully charged.

Try to uninstall the drivers and download the HTC drivers, fastboot and adb from Internet and try again. Do you have another PC? Because one time i have got the same problem than you and when i take another PC it's worked.

BelDev said:
Try to uninstall the drivers and download the HTC drivers, fastboot and adb from Internet and try again. Do you have another PC? Because one time i have got the same problem than you and when i take another PC it's worked.
Click to expand...
Click to collapse
The drivers fail to install everytime, and I've tried on three different PCs

Your problem is not the phone cause it detected by the PC but the drivers failed to detect you HTC. Can you say if you boot your phone in the boot loader, the phone show you if is in boot loader connected by usb or not?

BelDev said:
Your problem is not the phone cause it detected by the PC but the drivers failed to detect you HTC. Can you say if you boot your phone in the boot loader, the phone show you if is in boot loader connected by usb or not?
Click to expand...
Click to collapse
In fastboot on the phone, it shows that it is connected with USB, but ADB says that there is no device connected

Jhaleefi said:
In fastboot on the phone, it shows that it is connected with USB, but ADB says that there is no device connected
Click to expand...
Click to collapse
adb won't work on bootloader/fastboot mode. Only fastboot does.
When on fastboot, type command fastboot devices, do you get your device serial no. ?
On bootloader/fastboot, what is x the OS-x.xx.502.x now ?
See : http://forum.xda-developers.com/showpost.php?p=66886759&postcount=23

ckpv5 said:
adb won't work on bootloader/fastboot mode. Only fastboot does.
When on fastboot, type command fastboot devices, do you get your device serial no. ?
On bootloader/fastboot, what is x the OS-x.xx.502.x now ?
See : http://forum.xda-developers.com/showpost.php?p=66886759&postcount=23
Click to expand...
Click to collapse
I followed the instructions in that link, and everything works perfectly now. It's updated to 6.20.502.5. Thanks

Jhaleefi said:
I followed the instructions in that link, and everything works perfectly now. It's updated to 6.20.502.5. Thanks
Click to expand...
Click to collapse
Seems like your main issue was not properly using fastboot mode for fastboot, and realizing that adb doesn't work in bootloader mode? That, and having the proper firmware and RUU files.

Soft bricked OPO3, Fastboot with no recovery

Hi guys,
Rooted Oneplus 3 is soft bricked. Please help me!!! :crying:
:crying:Quick desription: Fastboot formatted it. My PC detects it.
Tried to Fastboot flash latest TWRP ("twrp-3.0.2-0-oneplus3.img") via CMD Prompt.
After that I get a message saying that the processed was "finished" (within 0.802s!).
Now I reboot+volume down and bootloop continues. Phone starts, I see the normal warnings I used to get after rooting it. Then I see the Oneplus logo for a fraction of a second and then it boots again and the process repeats itself.
I think it may be worth mentioning that the reason all this happened is an encryption problem that occurred while I was flashing a rom update with TWRP: After the flashing finished, got an error saying "unable to mount storage". Wiped cache+dalvik and then restarted. Got a black screen that did not display any signs of life after several minutes. Then turned it off and on by long press on the power button. Then I got an error saying that the encyption process was disrupted and that I have to wipe my phone (strange given that I did not select any encryption button in TWRP). Anyhow, then I fastboot formatted the phone and that's it.
Thank so much for anyone who can help!!!

fastboot flash recovery recovery.img (I recommend blu_spark's TWRP) reboot to recovery, if it doesn't work, try:
fastboot boot recovery recovery.img
See if you boot to recovery and then try flashing a custom ROM.

Hi Fobos, thanks for responding quickly.
I tried using fastboot boot command (with twrp-3.0.2-0-oneplus3.img). No luck with that.
Also, didn't find a downloadable blu_spark *.img version for twrp recovery. would you be so kind to add a link?
Thank you.

Now I think it's hard bricked ( Help!!!
Phone just stopped responding. Mostly doesn't respond. Occasionaly turns on for a nano second, flashes the +1 logo and turns off. Most of the time it doesnt even do that any more when I press (long / short press) the power button!
Somebody help, please!!

ppppp44 said:
Phone just stopped responding. Mostly doesn't respond. Occasionaly turns on for a nano second, flashes the +1 logo and turns off. Most of the time it doesnt even do that any more when I press (long / short press) the power button!
Somebody help, please!!
Click to expand...
Click to collapse
Keep calm and breath in. I was in the same situation.
Take a breath.
So, you have 2 ways depending on what you want. You can either go back to full stock with a flashing tool or you can install a custom recovery and then installing a custom rom (or stock one). I suggest the flashing tool.
Just follow the steps here: https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306 and if you have any question come back here and ask them.
Good luck.

Recoveryhttps://forum.xda-developers.com/devdb/project/dl/?id=24575
First format recovery by using command
fastboot format recovery
then flash recovery using
fastboot flash recovery "recovery.img"

Kayembe said:
Keep calm and breath in. I was in the same situation.
Take a breath.
So, you have 2 ways depending on what you want. You can either go back to full stock with a flashing tool or you can install a custom recovery and then installing a custom rom (or stock one). I suggest the flashing tool.
Just follow the steps here: https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306 and if you have any question come back here and ask them.
Good luck.
Click to expand...
Click to collapse
Hey Keyembe, thanks for the reply...
Tried to follow the instructions you posted. Did everything to allow unsigned drivers to be installed. Disabled it on from the advanced boot settings, and - when that didn't work, also running on test mode. Neither options work:
In the device manager I right click the android device (currently in fastboot mode), which is installed with Google drivers. I try to update the driver software to the unsigned driver and I get an error saying it's not compatible with my system (Win10 Pro) and that I should make sure it is compatible with an x64 based system.
What now?
Tx
Hey! Thanks for the reply...

anup807 said:
Recoveryhttps://forum.xda-developers.com/devdb/project/dl/?id=24575
First format recovery by using command
fastboot format recovery
then flash recovery using
fastboot flash recovery "recovery.img"
Click to expand...
Click to collapse
Hi Anup!
Thanks for the link to the Blu_Spark version of TWRP.
On CMD Prompt, tried to format recovery, console stopped responding. "Fastboot format recovery"...Just stops responding
Also tried "Fastboot delete recovery". I get a message saying "deleting recovery..." then also stops responding. Nothing happens from there.
I tried to use the OPO3 Root Toolkit. It does detect the fastboot device, but when I try to flash or boot or do anything else other than detection, it is unable to find the device. Says operation failed.
What now? :crying:

You could look through this post if nothing else helps.
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/

Machiel187 said:
You could look through this post if nothing else helps.
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Click to expand...
Click to collapse
Check your cable (try another one), even reinstall your adb drivers on your machine (if Windows).
Let the device charge for 30 minutes at least then retry (charge with new cable too).

ppppp44 said:
Hey Keyembe, thanks for the reply...
Tried to follow the instructions you posted. Did everything to allow unsigned drivers to be installed. Disabled it on from the advanced boot settings, and - when that didn't work, also running on test mode. Neither options work:
In the device manager I right click the android device (currently in fastboot mode), which is installed with Google drivers. I try to update the driver software to the unsigned driver and I get an error saying it's not compatible with my system (Win10 Pro) and that I should make sure it is compatible with an x64 based system.
What now?
Tx
Hey! Thanks for the reply...
Click to expand...
Click to collapse
Firstly, plug your phone on your computer in recovery mode or fastboot mode.
When you go in cmd and you type "adb devices" do you get anything?
If that works and you still can access recovery, you can install stock rom available on the OnePlus site. Here's a link : http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.1.3/
Boot into recovery, then install from adb.

Machiel187 said:
You could look through this post if nothing else helps.
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Click to expand...
Click to collapse
Thanks mate, followed the instructions on this post. I never get the device to be detected as Qualcomm. All I get is "Android Phone". I did install the Qualcomm drivers despite the warning I got for installing unsigned drivers. Installation went OK. When I go to the device manager again I still identifies the device as android phone. Also when I click "Have Disk" and select the qualcomm drivers I get an error saying they are incompatible with the device or with an x64 based system (regardless of them being signed or not).
Any ideas?
thanks again..

Kayembe said:
Firstly, plug your phone on your computer in recovery mode or fastboot mode.
When you go in cmd and you type "adb devices" do you get anything?
If that works and you still can access recovery, you can install stock rom available on the OnePlus site. Here's a link : http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.1.3/
Boot into recovery, then install from adb.
Click to expand...
Click to collapse
Hey Kayembe,
I only get to fastboot mode. No Adb device detected. No recovery mode available.

ppppp44 said:
Thanks mate, followed the instructions on this post. I never get the device to be detected as Qualcomm. All I get is "Android Phone". I did install the Qualcomm drivers despite the warning I got for installing unsigned drivers. Installation went OK. When I go to the device manager again I still identifies the device as android phone. Also when I click "Have Disk" and select the qualcomm drivers I get an error saying they are incompatible with the device or with an x64 based system (regardless of them being signed or not).
Any ideas?
thanks again..
Click to expand...
Click to collapse
Strange. Are you sure you turned off Driver Signature Enforcement?
When you hold the power button 10 seconds and plug the phone in, it should not be on. The screen should stay black. (looks like its off)
So make sure it's not trying to boot, because then it probably shows up as Android Phonee again.

Machiel187 said:
Strange. Are you sure you turned off Driver Signature Enforcement?
When you hold the power button 10 seconds and plug the phone in, it should not be on. The screen should stay black. (looks like its off)
So make sure it's not trying to boot, because then it probably shows up as Android Phonee again.
Click to expand...
Click to collapse
That's exactly what happens but when it's not in fastboot mode [ either after 10 seconds power button press or after i see the +1 logo (black screen)] - phone is not detected by my pc.
Yeah I'm sure about the driver signature enforcement. It's definitely off.
What am I doing wrong?
Thanks

ppppp44 said:
That's exactly what happens but when it's not in fastboot mode [ either after 10 seconds power button press or after i see the +1 logo (black screen)] - phone is not detected by my pc.
Yeah I'm sure about the driver signature enforcement. It's definitely off.
What am I doing wrong?
Thanks
Click to expand...
Click to collapse
I'm going to do a unbrick in a few hours.. Make sure Driver Enforcement is off. If you go to device manager and right click on it you can change the drivers somewhere so it shows up as described in the post..
Make sure you use method 2.

Puddi_Puddin said:
I'm going to do a unbrick in a few hours.. Make sure Driver Enforcement is off. If you go to device manager and right click on it you can change the drivers somewhere so it shows up as described in the post..
Make sure you use method 2.
Click to expand...
Click to collapse
ok I somehow managed to flash Blu_Spark Twrp and got it to work.
Within TWRP, flashed OnePlus3Oxygen_16_OTA_051_all_1704112009_2521.zip
and also SuperSU.zip, and no_verity.zip.
Getting some errors.
Device still doesn't boot.
Attaching the log TXT here.
I am desperate... please help.,..

Puddi_Puddin said:
I'm going to do a unbrick in a few hours.. Make sure Driver Enforcement is off. If you go to device manager and right click on it you can change the drivers somewhere so it shows up as described in the post..
Make sure you use method 2.
Click to expand...
Click to collapse
BTW, Now when I enter recovery mode on TWRP I am asked to put in a password to decrypt data. I don't have any such password any tried to go over the process of reformatting the device and flashing twrp again. that didn't make this decryption message go away...
((

ppppp44 said:
BTW, Now when I enter recovery mode on TWRP I am asked to put in a password to decrypt data. I don't have any such password any tried to go over the process of reformatting the device and flashing twrp again. that didn't make this decryption message go away...
((
Click to expand...
Click to collapse
try "default_password" for the password

ppppp44 said:
BTW, Now when I enter recovery mode on TWRP I am asked to put in a password to decrypt data. I don't have any such password any tried to go over the process of reformatting the device and flashing twrp again. that didn't make this decryption message go away...
((
Click to expand...
Click to collapse
Go to Fastboot type 'fastboot erase userdata' (you have to reflash OOS tho.. Make sure you are on the latest TWRP. I'm not a fan of Bluspark but his TWRP is currently more up 2 date.