Develop Bugs

[Guide] Re-lock and Un-root **3G & 4G** Xoom

##PLEASE NOTE##
These files are from Motorola's Development site and I take no liability with anything that happens with your device if something goes wrong.
DO NOT ATTEMPT TO FLASH THIS FILE ON ANYTHING BUT THE VERIZON WIRELESS MOTOROLA XOOM Z600 (3G MODEL) OR YOU WILL HAVE A SHINEY PAPER WEIGHT!!!!
Click to expand...
Click to collapse
You're going to need to have the Android SDK installed. You can download it here:
ANDROID SDK - DOWNLOAD
XOOM Firmware Downloads:
[3G|MZ600-HRI66]
[4G|MZ602-HLK75D]
Unzip the files in MZ600_HRI66.zip and move or copy them to the /platform-tools folder in your SDK folder.
Connect your Xoom to your computer. Type:
Code:
adb reboot bootloader
Wait for it to reboot into the bootloader.
Type the following commands, waiting for each to finish before continuing:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
You've now successfully flashed your Xoom back to stock. Now it's time to relock the device. Type
Code:
fastboot oem lock
wait for the menu
then press the volume-down button.
Then press the volume up button.
It'll take a minute or so, then reboot. You're now completely back to stock and ready for the update.

So if you are on Three . One you can use this to revert back to out of the box freshness?

Brenardo said:
So if you are on Three . One you can use this to revert back to out of the box freshness?
Click to expand...
Click to collapse
Yes. That is correct. This will return your XOOM to 100% stock.

word!
I have already been thru the LNX 0x0004 debacle and it was absolutely no fun whatsoever.

well I got a stuck at moto logo for 10 minutes
I am going to try to fastboot oem unlock, reflash images again and fastboot lock to see if I get out of moto logo

second install fix it

jlouang said:
second install fix it
Click to expand...
Click to collapse
So that means that you got it working, correct?
>.>

So the HRI66 is the latest version on the Motorola site? I really need to get a grasp of their version numbers.
EDIT:
Never mind looks like HRI66 is the latest version Thanks anyway.

i was thinking that with the change to the bootloader in the 3.1 update we couldn't use previous versions img's. But I am glad we can return to stock and get this 4G update!

I'm following all those steps directly. Once I type in adb reboot bootloader, it says starting Fastboot protocol support. Once I try to type any other command it says not recognized in adb. Any ideas?

Dead link...

dchurch85 said:
I'm following all those steps directly. Once I type in adb reboot bootloader, it says starting Fastboot protocol support. Once I try to type any other command it says not recognized in adb. Any ideas?
Click to expand...
Click to collapse
Did you extract all of the files in the ZIP into the 'tools' folder? The same one that adb is in.

Could someone help me,
After the rebooting device I got this massage :
Failed to boot LNX 0x0004
Starting RSD mode 2
Then stuck on Motorola logo. I can't enter the recovery mode.
What should I do ?
My Xoom is H.6.1-38-9 International version

CakraMas said:
Could someone help me,
After the rebooting device I got this massage :
Failed to boot LNX 0x0004
Starting RSD mode 2
Then stuck on Motorola logo. I can't enter the recovery mode.
What should I do ?
My Xoom is H.6.1-38-9 International version
Click to expand...
Click to collapse
This is what I was afraid of..... try searching the error you are getting. Not many options on how to fix.

i am curious about the LNX 0x0004 error. I know it comes from trying to relock with non-factory img's but what exactly does that mean? I am curious what actually causes the device to soft brick.

Finally I made it, .
I can enter to bootloader by fastboot method, flash the stock image, then relock my device.

Kinda having the same issue as dchurch... "adb reboot bootloader" reboots Xoom to the "M" logo with "Starting Fastboot protocol support," but I can't continue with nay further commands. My computer no longer recognizes the presence of my Xoom and my Xoom doesn't progress past this screen. I can boot it normally with no problem. I've extracted all of the necessary files into my platform tools folder with adb.. any input?

gatorhater73 said:
Kinda having the same issue as dchurch... "adb reboot bootloader" reboots Xoom to the "M" logo with "Starting Fastboot protocol support," but I can't continue with nay further commands. My computer no longer recognizes the presence of my Xoom and my Xoom doesn't progress past this screen. I can boot it normally with no problem. I've extracted all of the necessary files into my platform tools folder with adb.. any input?
Click to expand...
Click to collapse
You can try manually going into fastboot as well... there are two ways to do this:
No matter what, power off the Xoom. Then, 1) Power on the Xoom and as soon as you see it turn on (within a second or two of the power on), press the Volume Down button, which kicks it into Fastboot. 2) If you miss the 1st couple of seconds and press Volume Down after 3-5 seconds, it will say "Android Recovery." You can then press Volume Down until you get to Fastboot, then press Volume Up.
My guess is that you have a different issue, something to do with your Fastboot image. Not sure if booting the Xoom into the OS and connecting with USB Debugging on will work or not to flash the files, perhaps maybe just the boot.img?

I also believe that when the Xoom says "Starting Fastboot protocol support", it is in fastboot mode and you can send the fastboot commands to the Xoom. If your PC does not show the Xoom as a device in your PC's Device manager, then you will probably need to load new/correct drivers onto your PC.

Did you make sure that adb recognized your device? Adb devices in the camaned prompt
Sent from my Xoom using Tapatalk

DESPERATE need help!! one x recovery failure??

so i had just htc dev unocked my one x, now i was using hasoons tool, and when i tried to flash a recovery in fastboot with commands, everything in the prompt said okay.. flashed successful and so on, and the bar on the top right hand side of my phone flickered as if to load, but didint. now when i go to recovery mode, it gives me the splash screen with some red letter **** about distrabution, then reboots. ive tried flashing every possible recovery for the one x, including stock, and seems to do nothing, help??
pic is the screen rite b4 reboot (thats what i get when i reboot into recovery)

EDIT:: now im stuck at the screen in the picture, will not boot into anything else, will not be recognized by adb. PLEASE HELP!!!!
EDIT EDIT: i can power off, and get back into fast boot with volume off, but im almost asuming i just have no recovery..... and it will NOT! boot into the phone no matter what, only booting into that screen... what the **** do i do lol this is kind of a panic now

Have you tried reflashing stock recovery? Also shouldn't you be in the AT&T One X forum unless of course you have the international version of the One X.

I have tried the stock recovery, but now its in fastboot and won't get recognized by adb on my pc as it did. It just boot loops now at that screen and won't get recognized. And this isn't at. &t

ixi_devo_ixi said:
I have tried the stock recovery, but now its in fastboot and won't get recognized by adb on my pc as it did. It just boot loops now at that screen and won't get recognized. And this isn't at. &t
Click to expand...
Click to collapse
You're suppose to flash stock recovery in fastboot.

I know, I tried when it was getting recognized, now I can't even pick it up with adb

so its telling me to flash the stock RUU, but i cant use adb commands it wont recognize in fastboot, the computer dings when i plug it in, but adb devices comes up with nothing, i tried every usb port on my pc and everything

ixi_devo_ixi said:
so its telling me to flash the stock RUU, but i cant use adb commands it wont recognize in fastboot, the computer dings when i plug it in, but adb devices comes up with nothing, i tried every usb port on my pc and everything
Click to expand...
Click to collapse
First of all ADB only works in RECOVERY mode not directly in bootloader. So do the following steps & instal custom rom (Any1 u like).
1. You need recovery.img in your fastboot directory
2. Go into bootloader and connect phone
3. Then use: "fastboot boot recovery.img" (thus booting your image from pc and not the installed recovery).
4. When in recovery, you can use the adb commands.
5. You can try with "adb devices" which should show you serial of phone.
6. command: adb push rom_rom.zip /sdcard
credits to broncogr for finding that adb works if you use fastboot boot command and to Jotha for helping me out!

[Q] Please help -- phone dead

Have I bricked my xperia-zl?
(originally posted in the wrong place, one of the members directed to repost it here)
1. My Phone is xperia-zl C6502 build 10.4.1.B.0.101
2. Successfully unlocked the bootloader
3. Used Flashtool to Iinstall CWM
4. Now my phone
a. does not boot: tried all combination of switches, including the yellow button next to the SD Card
b. is not recognized by flashtool any more
c. not recognized by Sony PC companion
d. no light/indication when put to charge.
5. I cannot flash stock firmware and then reboot the device as the device is no more recognized by flashtool?
Want help, desperately.

r_s_dhar said:
Have I bricked my xperia-zl?
(originally posted in the wrong place, one of the members directed to repost it here)
1. My Phone is xperia-zl C6502 build 10.4.1.B.0.101
2. Successfully unlocked the bootloader
3. Used Flashtool to Iinstall CWM
4. Now my phone
a. does not boot: tried all combination of switches, including the yellow button next to the SD Card
b. is not recognized by flashtool any more
c. not recognized by Sony PC companion
d. no light/indication when put to charge.
5. I cannot flash stock firmware and then reboot the device as the device is no more recognized by flashtool?
Want help, desperately.
Click to expand...
Click to collapse
I'm sorry to say that, but you're still in the wrong place, you need to go there:
http://forum.xda-developers.com/xperia-zl/help
Anyways, did you flash the correct kernel? Or did you just try to flash a recovery?

St.Jimmy90 said:
I'm sorry to say that, but you're still in the wrong place, you need to go there:
http://forum.xda-developers.com/xperia-zl/help
Anyways, did you flash the correct kernel? Or did you just try to flash a recovery?
Click to expand...
Click to collapse
St.Jimmy,
I am a first time member, joined only yesterday (that is after my tail caught fire!); sorry to be still in the wrong place. Could moderators please relocate my post to the right location? Thanks a million to this wonderful site.
Thanks for the reply. I think installing CWR required flashing a "boot.img" file. The device gave up its ghost after flashing the boot.img file. As of now, there seems to be a slight improvement -- there is a red LED indicator that has come on when put to charging; it is faint, but it is there alright! Any chances of resurrection or is my phone really gone to its Heavenly Kingdomo?

I suggest u first charge it for 1-2 hours and then try using flashtool
Sent from my MT25i

kedar a.k.a. 3K said:
I suggest u first charge it for 1-2 hours and then try using flashtool
Sent from my MT25i
Click to expand...
Click to collapse
Kedar,
Thanks. I have charged my phone overnight (10 hours). Still LED glows red. For a while I could connect in flashboot mode (LED=blue). Any help?

r_s_dhar said:
Kedar,
Thanks. I have charged my phone overnight (10 hours). Still LED glows red. For a while I could connect in flashboot mode (LED=blue). Any help?
Click to expand...
Click to collapse
I can now sometimes connect in flashboot mode; flashtool initially recognizes the phone but when I try to flash a stock ROM, asks the phone to be connected (as if it has not already recognized the phone)! HELP PLEASE!!

r_s_dhar said:
Have I bricked my xperia-zl?
(originally posted in the wrong place, one of the members directed to repost it here)
1. My Phone is xperia-zl C6502 build 10.4.1.B.0.101
2. Successfully unlocked the bootloader
3. Used Flashtool to Iinstall CWM
4. Now my phone
a. does not boot: tried all combination of switches, including the yellow button next to the SD Card
b. is not recognized by flashtool any more
c. not recognized by Sony PC companion
d. no light/indication when put to charge.
5. I cannot flash stock firmware and then reboot the device as the device is no more recognized by flashtool?
Want help, desperately.
Click to expand...
Click to collapse
might have a solution for the recovery if the fastboot is working
download minimal adb and fast boot from here
place boot.img in minimal adb and fast boot folder after installation
Put your phone in fastboot( hold power up key and plug usb)
open minimal adb and fast boot application
it will open a cmd window
type fastboot flash boot boot.img
after that type fastboot reboot
your phone will restart now
PS: your phone is refusing to boot because the recovery is corrupted

What if you fastboot a custom kernel with inbuilt recovery and then flash a Rom with the recovery?
Since you have fastboot working
Sent from my MT25i
---------- Post added at 07:53 AM ---------- Previous post was at 07:49 AM ----------
What if you fastboot a custom kernel with inbuilt recovery and then flash a Rom with the recovery?
Since you have fastboot working
You may try the method by @androidtweaker mentioned above as it is similar :thumbup:
Sent from my MT25i

First, what exactly did you flash to your phone and where did you get it from?
Sent from my C6603 using Tapatalk

Androidtweaker1: Thanks. Cannot connect in fastboot mode. The blue LED comes on but the device is not recognized (adb drviers etc. no problem, all correctly installed, all set).
kedar: cannot connect in the fastboot mode. See reply to Androidtweaker1 above. Thanks
kingvortex: Thanks. I was trying to follow the following tutorial:
After downloading Z_DooMLoRD_AdvStkKernel_FW-4.3-101_v12.zip, place it in external SD Card of your smartphone
Now extract Z_DooMLoRD_AdvStkKernel_FW-4.3-101_v12.zip on your PC’s desktop and copy boot.img
Paste this file inside the folder where you have installed Minimal ADB and Fastboot
Now turn off your smartphones completely
Plug in mobile’s USB in cable in PC port only
Hold Volume up button and plug in USB cable in mobile’s port
LED will turn blue (If it does not remain blue for long, then read Optional part in bootloader unlocking method explained above
Once you are successfully in fastboot mode, then you can continue
Now type Fastboot flash boot boot.img and press Enter
It will flash boot.img file on your device
Now unplug the device and boot it up
As soon as you see purple colored LED, start pressing volume up and down buttons repeatedly, until you are in CWM mode
In CWM Mode, select “Install Zip”
Now select the storage you have put that zip file in and just confirm its installation
There are two ways to navigate in this CWM recovery
You can navigate with volume buttons and make a selection with power button
Another way of navigating is by swiping your finger on empty area in recovery
Swipe up to move up, swipe down tp move down, swipe right to make a selection and swipe left to go back
After installation is complete, go back to main menu and reboot your smartphone
Congrats! You have successfully installed CWM custom recovery on your smartphones

I have a similar situation and I'm stuck.
Q: is working the minimal adb if in the settings was not checked the debug mode?
In my case I can go in fastboot mode each time but not help.
When I try to go in flash mode, there is strange because the flashtool say it it connected in flash mode , even the PCC say this, but the LED it's not green, is off, first is try to go green after get red and after off, but the software say is in flash mode.
I can try to flash any ftf, it's working without erors but my phone it's still dead after restart, even SONY logo is not appear, just vibrate once.
Other strange think, each time when I made a new flahing, there is a status message of device, it say that the version of ftf is 230 even if last time I was tring to flash 101 for ex and was finished without errors. Always show the same ftf version like nothing is changing inside. The only thing can change is the BL, lock or unlock and I can see this in the status device, this is made in fastboot mode and there I have the blue LED.
Can anybody give me some ideeas to fix this?
have the log of flahtool attached.
Thanks.

SOLUTION
remav said:
I have a similar situation and I'm stuck.
Q: is working the minimal adb if in the settings was not checked the debug mode?
In my case I can go in fastboot mode each time but not help.
When I try to go in flash mode, there is strange because the flashtool say it it connected in flash mode , even the PCC say this, but the LED it's not green, is off, first is try to go green after get red and after off, but the software say is in flash mode.
I can try to flash any ftf, it's working without erors but my phone it's still dead after restart, even SONY logo is not appear, just vibrate once.
Other strange think, each time when I made a new flahing, there is a status message of device, it say that the version of ftf is 230 even if last time I was tring to flash 101 for ex and was finished without errors. Always show the same ftf version like nothing is changing inside. The only thing can change is the BL, lock or unlock and I can see this in the status device, this is made in fastboot mode and there I have the blue LED.
Can anybody give me some ideeas to fix this?
have the log of flahtool attached.
Thanks.
Click to expand...
Click to collapse
Hey, have you already solved your problem? I had the same as you and I could fix it, I will try to submit a post here explaining the steps I followed

I solved but in other way. I bought another Zl with the battery dead and I replaced the motherboard. I have it now working from gew months without any problems. The old motherboard is still broken.

[Q] Wiped Nexus, new rom didnt work, have nothing to restore to.

So I'm an idiot. I deleted everything off my Nexus 7 then I was going to flash to a new ROM, didn't work, I don't know why but it won't install. I have nothing else to install, not any other ROMs and no backups. To make the whole entire thing worse, my Nexus wont connect to my computer. Before you say to reinstall the drivers or plug it into another computer, I have, I've tried everything and nothing works. So my question is; Am I screwed or is there somehow a way to install a new ROM (seems impossible) or put the stock ROM back on? I tried the adb sideload method but I was completely unsuccessful as well as every other method I've seen/could come up with. After trying weeks to get anything back on my Nexus 7 I'm just about ready to toss this paperweight in my drawer and forget abaout it

Which modes can you get into?
TWRP allows you to mount USB OTG. Try flashing something from there.
Press Thanks If I Helped You!
Sent from my dead Nexus 7 2013 LTE! ???

Yes, like aniket0317 wrote: if all else has failed, put a ROM on a flash drive, connect it with a USB OTG adapter, and use TWRP.
I've lately had trouble getting my N7 recognized while in recovery mode, though everything's fine while in the bootloader and Android. But with TWRP it's easy to mount external flash storage and install from that.

RecklessBrandon said:
So I'm an idiot. I deleted everything off my Nexus 7 then I was going to flash to a new ROM, didn't work, I don't know why but it won't install. I have nothing else to install, not any other ROMs and no backups. To make the whole entire thing worse, my Nexus wont connect to my computer. Before you say to reinstall the drivers or plug it into another computer, I have, I've tried everything and nothing works. So my question is; Am I screwed or is there somehow a way to install a new ROM (seems impossible) or put the stock ROM back on? I tried the adb sideload method but I was completely unsuccessful as well as every other method I've seen/could come up with. After trying weeks to get anything back on my Nexus 7 I'm just about ready to toss this paperweight in my drawer and forget abaout it
Click to expand...
Click to collapse
are you able to go into fastboot mode? if so you still have hope

kmaq said:
are you able to go into fastboot mode? if so you still have hope
Click to expand...
Click to collapse
I'm not allowed to post pictures yet but I believe I can get in fastboot mode and I am sure that I can get into ClockworkMod Recovery

RecklessBrandon said:
So I'm an idiot. I deleted everything off my Nexus 7 then I was going to flash to a new ROM, didn't work, I don't know why but it won't install. I have nothing else to install, not any other ROMs and no backups. To make the whole entire thing worse, my Nexus wont connect to my computer. Before you say to reinstall the drivers or plug it into another computer, I have, I've tried everything and nothing works. So my question is; Am I screwed or is there somehow a way to install a new ROM (seems impossible) or put the stock ROM back on? I tried the adb sideload method but I was completely unsuccessful as well as every other method I've seen/could come up with. After trying weeks to get anything back on my Nexus 7 I'm just about ready to toss this paperweight in my drawer and forget abaout it
Click to expand...
Click to collapse
RecklessBrandon said:
I'm not allowed to post pictures yet but I believe I can get in fastboot mode and I am sure that I can get into ClockworkMod Recovery
Click to expand...
Click to collapse
download the 4.4.4 image
go to fastboot mode, connect the usb cable to laptop/pc
open command prompt and go to the folder where you have extracted the 4.4.4 image
fastboot oem unlock
type flash-all.bat
if all goes well device should reboot (initally will take some time) if it took more time, reboot again into fastboot mode
this time you can try manually commands one by one
in the folder where you have extracted the 4.4.4 image you will fine "image-razor-ktu84p.zip", extract this zip file as well
execute the following commands one by one:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot reboot-bootloader
fastboot flash bootloader bootloader-flo-flo-04.02.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot reboot
device should reboot and if it displays language screen then cool complete the wizard, reboot in to fastboot mode again to lock the bootloader
fastboot oem lock
fastboot reboot
and enjoy!!! do report back what happens.

fastboot -w update stockrom.zip

I'm a little confused on the instructions, also, as mentioned, my Nexus isn't recognized by my computer no matter what I try.

How does it appear in Device Manager? Have you downloaded and installed the drivers?
http://developer.android.com/sdk/win-usb.html

RecklessBrandon said:
I'm a little confused on the instructions, also, as mentioned, my Nexus isn't recognized by my computer no matter what I try.
Click to expand...
Click to collapse
in the fastboot mode, after connecting your device to laptop/pc,
if you type "fastboot reboot-bootloader" in the command prompt
what happens?

I am having the exact same problem, it was installing got stuck on "erasing userdata" for over 2 hours and now nothing will work except for fastboot, and some how the device locked itself again. Only thing i can get to is fastboot mode, the computer recognizes the device. When I try to unlock it, it gets stuck in "erasing userdata" I let it run over night last night hoping it would some how work with no luck. I am unsure of what to do. Is there anyway to install a factory OS without unlocking? Every guide I've searched for has me doing an fastboot oem unlock and then the tablet freezes on erasing userdata. Any help would be greatly appreciated. Thanks!

kmaq said:
in the fastboot mode, after connecting your device to laptop/pc,
if you type "fastboot reboot-bootloader" in the command prompt
what happens?
Click to expand...
Click to collapse
Reread your initial instructions, and it worked! Thank you so much!!!

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.