Database Users

Fastboot discussion.

I have searched and couldn't find a fastboot thread. So here it is.
I found out fastboot is working on Linux.
Bad news is Windows seems to need another driver for fastboot.
Please help look for a windows driver or make one.
The fastboot commands all seem to work fine.
Here you guys go! Enjoy.
Code:
[SIZE=5][SIZE=3][SIZE=5][SIZE=3]adb reboot-bootloader
fastboot -i 0x1949 command_here[/SIZE][/SIZE][/SIZE][/SIZE]
Just noticed pokey9000 said this but it was overlooked.
pokey9000 said:
That's it. And you're running fastboot as "fastboot -i 0x1949 your_command_here", and you have udev set to allow permissions for that VID (or are running as root) in Linux?
Click to expand...
Click to collapse
Thank you.
Still don't believe me, look at the last picture.
I'm having issues with some commands. Please test it out and enjoy!

shimp208 said:
In the Fire TV section a fastboot cable was created by splicing two USB A to B cables together, so that the A to A ends were together which when connected from your computer to the Fire TV on bootup put the device in fastboot mode, in the process then your computer recognized (Running Windows 8 was the example given) the device and installed the proper drivers. Since the devices are similar, a potential solution would be use the cable, have the computer recognize it and install the drivers, then backup the drivers, and share them here for others to use.
Click to expand...
Click to collapse
I'm quite sure the cable isn't the issue. Also that's just it, I can't get windows to recognize it or find much info about it. The adb driver for the device isn't enough I guess. The funny thing is windows says it's working properly as 'Kindle' for a little while when you plug it in (while in bootloader) then device manager refreshes and reports 'cannot start'. I tried launching 'fastboot devices' many times but still nothing. I think it needs a software fix and not a hardware one but I have no past experience using fastboot. So... noob alert.
btw the driver windows tries to use is ms_comp_mtp(Generic driver installed=true) and adb uses the Amazon one on the fourm here.
DevNode status Value:
01802400
DN_HAS_PROBLEM
DN_DISABLEABLE
DN_NT_ENUMERATOR
DN_NT_DRIVER
Also Bus reported device description Value:
fastboot
VID=1949 & PID=000C
(0x1949 && 0x000c)
Current Driver files:
\system32\DRIVERS\UMDF\WpdMtpDr.dll
\system32\DRIVERS\winusb.sys
\system32\DRIVERS\WUDFRd.sys
\system32\WpdMtp.dll
\system32\WpdMtpUS.dll
We need someone good on this.

I have a problem

I don't think there's ever been a question of getting into fastboot mode by using the adb reboot-bootloader command.
The issue is how to enter fastboot if the device is semi-bricked.
The device has source in the original bootloader to boot into fastboot mode if both volume buttons are pressed while powering on the device. But this has since been altered and now will only work if the device is unlocked.

Hashcode said:
I don't think there's ever been a question of getting into fastboot mode by using the adb reboot-bootloader command.
The issue is how to enter fastboot if the device is semi-bricked.
The device has source in the original bootloader to boot into fastboot mode if both volume buttons are pressed while powering on the device. But this has since been altered and now will only work if the device is unlocked.
Click to expand...
Click to collapse
Is flashing the stock .bin file any different than doing a factory reset?
I am bricked, have root, have adb, can get fastboot using adb reboot-bootloader in windows 8. I also have a Linux box if necessary.

saphi95 said:
I have a problem
Click to expand...
Click to collapse
I would recommend taking a look at this thread here, specifically the "Fixing No Permissions Error" section which should allow you to fix the problem your encountering.

dcoig1 said:
Is flashing the stock .bin file any different than doing a factory reset?
I am bricked, have root, have adb, can get fastboot using adb reboot-bootloader in windows 8. I also have a Linux box if necessary.
Click to expand...
Click to collapse
Fastboot works with win8? Not with win7.1 If you have fastboot working with win8 please go to device manager (when your in the bootloader) click properties on the device then look for what driver it uses.
Hashcode said:
I don't think there's ever been a question of getting into fastboot mode by using the adb reboot-bootloader command.
The issue is how to enter fastboot if the device is semi-bricked.
The device has source in the original bootloader to boot into fastboot mode if both volume buttons are pressed while powering on the device. But this has since been altered and now will only work if the device is unlocked.
Click to expand...
Click to collapse
My main reason is to get fastboot working with windows. I just can't. Linux seems to work with fastboot but I can't access it via windows.

Just uninstall the kindle driver and replace it with the generic fastboot one

hello all,
i've kindle fire hdx 7" , no adb, grey screen logo then shutdown and goes to black screen.
when connected using cable, it show new devices... QHSUSB_BULK and sometime unknown devices.
press hold power button and volume up only go to recovery mode, but cannot recovery the system..
always go to grey screen logo...
sorry for my bad english language...
hope all of you, understand what i mean here
i need solution for fix the problem soon. thanks

I think all that works is reboot into fastboot mode. Windows 8 says no drivers are loaded. I tried a command (can't remember what) and it just went out to lunch so... I guess windows 8 isn't working either. Only to put the device in fastboot.

there are three oem commands:
oem device-info
oem idme
oem relock
Click to expand...
Click to collapse
but it doesn't support oem unlock so there must be another way of unlocking the bootloader, when you try some of the commands the device returns "not allowed for locked hw". Does anyone know what the "hw" is ?

hw = hardware?

MaximilianOzora said:
hello all,
i've kindle fire hdx 7" , no adb, grey screen logo then shutdown and goes to black screen.
when connected using cable, it show new devices... QHSUSB_BULK and sometime unknown devices.
press hold power button and volume up only go to recovery mode, but cannot recovery the system..
always go to grey screen logo...
sorry for my bad english language...
hope all of you, understand what i mean here
i need solution for fix the problem soon. thanks
Click to expand...
Click to collapse
Read up on this bud.

Hi,
I have a bricked kindle hdx 8.9 that stops at "Kindle Fire" boot screen. I am a newbie at these things.
Just discovered that it still respond to some adb queries. Sounds like there is still hope to recover... Could it be the bootloader is messed up? Anyway to reload an image boot file to repair?
Also "fastboot reboot-bootloader" puts it into fastboot mode...with the status "ready"....and i just dont know how to proceed. Any one can help?

uhg
Facepalm

just back a little: was rooted in April but with subsequent amazon auto updates - didn't have su status. But I was able to load apps & files, installed vpns, quite a few docs,mp4 files, etc. Not really using much of the new freedom or whatever was left of it... Nothing exciting.
Was working well until one fine sunday afternoon, just 2 weeks ago when it just simply stopped after rebooting from a previous low battery charge. Was told it could be an interrupted routine update when the battery power just fell below threshold - but thot it wouldn't have erase the previous image before the new update is effective. Or it could possibly be a deleted file that is related to the booting process as I did a bit of clean up prior to the last reboot?
In the meantime, I did some adb shell/pull to explore or extract the files, photos,etc in /sdcard & other places back to my PC just in case they were not backup by the cloud. Maybe it was not bricked...but just lost a boot file or something...

In a bad situation, have absolutely zero ADB access as my build.prop is botched (bad permissions) and I did a factory reset in hopes of recovering. There is a "fastboot cable" on amazon that says it will reboot a hdx into fastboot mode, but I'm unsure of it's legitimacy. Help?

here try
Tumbtack said:
In a bad situation, have absolutely zero ADB access as my build.prop is botched (bad permissions) and I did a factory reset in hopes of recovering. There is a "fastboot cable" on amazon that says it will reboot a hdx into fastboot mode, but I'm unsure of it's legitimacy. Help?
Click to expand...
Click to collapse
This thread.read read read http://forum.xda-developers.com/showthread.php?t=2588608

I don't quite understand. Why is a special cable required for this? What makes it any different from the standard one that comes with the device?

I don't know if this will add anything to the discussion...but I can confirm fastboot is working on Ubuntu 14.04. I am using a kindle fire HDX 7" and it detects it on devices..and most commands work. Sometimes the terminal must be closed and reopened for commands to go through..
fastboot oem unlock works..or rather it says "Okay" but I'm unable to flash anything.

[Q] Permanent problem with Unlocking Bootloader Nexus S

Hi guys,
I searched forums, web with no positive results. So I start a new thread. Here is the situation: one day my Nexus S (Worldwide edition) froze on restarting with the Google Logo on the screen. Every time I try to turn the phone on it stacks at Google logo. When in the fastboot mode the status is Locked. Every time I try fastboot oem unlock I get Phone’s prompt with Yes or Not to unlock bootloader and after choosing Yes, the status doesn’t change to Unlock. Tried on Linux, Mac, Windows (drivers installed successfully), the same result. Tried to force Flash Stock + Unroot in Wugfresh, doesn’t work due to the Locked Bootloader.
typing "adb devices" in cmd (should return the device number) shows:
List of devices attached
......
Empty line above
Any word of advise how to force Unlocking the Bootloader would be greatly appreciated. Please help. Thank you!

alpheus said:
Hi guys,
I searched forums, web with no positive results. So I start a new thread. Here is the situation: one day my Nexus S (Worldwide edition) froze on restarting with the Google Logo on the screen. Every time I try to turn the phone on it stacks at Google logo. When in the fastboot mode the status is Locked. Every time I try fastboot oem unlock I get Phone’s prompt with Yes or Not to unlock bootloader and after choosing Yes, the status doesn’t change to Unlock. Tried on Linux, Mac, Windows (drivers installed successfully), the same result. Tried to force Flash Stock + Unroot in Wugfresh, doesn’t work due to the Locked Bootloader.
typing "adb devices" in cmd (should return the device number) shows:
List of devices attached
......
Empty line above
Any word of advise how to force Unlocking the Bootloader would be greatly appreciated. Please help. Thank you!
Click to expand...
Click to collapse
It looks like your device is not recognized in Fastboot mode...
Have you turned on USB Debugging while connecting PC and Allow in Device when Prompt some message ..
Go to fastboot mode and write this command... fastboot devices
If it will give you a message like this
List of devices
1235456785164
Then your devices is successfully recognized...:good:

It is not recognized by adb devices, but:
fastboot devices - gives the following output:
ERROR: could not get pipe properties
3331E6EBCA6000EC fastboot
Click to expand...
Click to collapse
fastboot oem unlock - gives the following:
ERROR: could not get pipe properties
...
FAILED (remote: Erase Fail)
finished. total time: 4.753s
Click to expand...
Click to collapse

alpheus said:
It is not recognized by adb devices, but:
fastboot devices - gives the following output:
fastboot oem unlock - gives the following:
Click to expand...
Click to collapse
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data

demkantor said:
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data
Click to expand...
Click to collapse
Thanks, I tried 3 different cables on 3 different operating systems, with the same problem unlocking the fastboot. When I send fastboot oem unlock the device opens a prompt with Yes or No choice, but after choosing Yes, it stays Locked

Something indeed is strange...
So fastboot is for bootloader and adb is for within os and in recovery.
Try booting into recovery and see if adb works, also boot normal into your bootloop and see if adb works there too

demkantor said:
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data
Click to expand...
Click to collapse
demkantor said:
Something indeed is strange...
So fastboot is for bootloader and adb is for within os and in recovery.
Try booting into recovery and see if adb works, also boot normal into your bootloop and see if adb works there too
Click to expand...
Click to collapse
Loading into basic recovery and trying to wipe data/factory reset - doesn't work. adb devices returns the following output:
./adb-linux devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
****empty line here****
Somehow, adb doesn't recognize the device, whereas fastboot devices shows it.
Is there a way to flash new bootmode with the currently locked bootloader?
Thank you!

alpheus said:
Loading into basic recovery and trying to wipe data/factory reset - doesn't work. adb devices returns the following output:
./adb-linux devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
****empty line here****
Somehow, adb doesn't recognize the device, whereas fastboot devices shows it.
Is there a way to flash new bootmode with the currently locked bootloader?
Thank you!
Click to expand...
Click to collapse
I am damn Sure What's Your problem is, ADB is not working..
PROCEDURE:-
1) Download My attachement and unzip it and Place it in Folder...
See image 1.png
2) Go to that folder and Press CTRL+SHIFT+ Right click on mouse and Select Open Command Window here..
See image 2.png
3) Now type here Fastboot devices and Now you will get Those list of devices Number..
See image 3.png
If Everything will be done as Procedure and you will get List of devices Number... Now, You type those command for Unlocking bootloader and Root Your Devices...:good:
Hope this Guide will help..

UPDATE (resolved)
Here is an update. Hope this would help others with similar issue, as I've read many threads and folks complaining that they weren't able to unlock fastboot and further root their Nexus S, and who can't boot the phone, which stacked with Google Logo (soft loop). This was the case with my device and finally I got it resolved. I've read some guy tried to hit the phone and after that he was able to boot phone normally. It related to some hardware electrical circle issue. Anyways, I tried to hit my phone by placing it under the direct sun in balcony for some time until the phone got hot and then power it on. And ooops, my phone started booting passed by that Google Logo which was the good sign. Once the phone booted up, I went ahead and activated USB debugging and restarted the phone into the Fastboot mode. while the phone was still hot and in Fastboot mode I run "fastboot oem unlock" and hey, fastboot is Unlocked! Again, this was done while the phone was hot, any previous attempts (read above) weren't successful. From that point, I went ahead and rooted my Nexus S by Nexus Root Toolkit, available on wugfresh.com/nrt, without a slightest problem. Now my phone is fully rooted, bootable and working fine. I thank all who replied to my thread and tried to help and hope this info would help someone with the similar issue.

Rushabh22 said:
I am damn Sure What's Your problem is, ADB is not working..
PROCEDURE:-
1) Download My attachement and unzip it and Place it in Folder...
See image 1.png
2) Go to that folder and Press CTRL+SHIFT+ Right click on mouse and Select Open Command Window here..
See image 2.png
3) Now type here Fastboot devices and Now you will get Those list of devices Number..
See image 3.png
If Everything will be done as Procedure and you will get List of devices Number... Now, You type those command for Unlocking bootloader and Root Your Devices...:good:
Hope this Guide will help..
Click to expand...
Click to collapse
Thank you for your help and suggestions.

Q Mobile X 32
bootloader oem unlock problem
plz help

Q-mobile said:
Q Mobile X 32
bootloader oem unlock problem
plz help
Click to expand...
Click to collapse
Wrong device thread..
Try here..
https://forum.xda-developers.com/showthread.php?t=2363923

Setting.Out said:
Wrong device thread..
Try here..
https://forum.xda-developers.com/showthread.php?t=2363923
Click to expand...
Click to collapse
can you help me in rooting Qmobile x32

Q-mobile said:
can you help me in rooting Qmobile x32
Click to expand...
Click to collapse
That thread didn't help?

Here's what the guide says...

Phone boots normally but can't enter Fastboot, no recovery.

Hi guys, I'm having a weird problem with my zenfone 5 (a501cg). I have searched a lot but still can't find out a proper solution So I post it here and try to provide as much information as possible so hopefully developers at xda can help me.
My phone is rooted and I'm currently using modded rom called "bazzrom pinaslang" in the forum. Recently I want to use another rom so I decide to use adb sideload again.
However, the problem occurs: using adb sideload only show "error" message". BUT Adb devices show the phone.
Then I decide to use adb reboot fastboot to enter fastboot. But the phone only show a usb icon, and using "fastboot devices" doesn't show the device anymore.
I try other way by enter recovery mode "adb reboot recovery". The phone show resting android with "no command" message. I also try hold power and press down volumn after that but nothing happend. I try anything with that "power" + "volumn" combo but nothing happend (or it just shutdowns the phone).
Also, using "power" + "up volumn" to enter Droid boot doesn't work.
Driver is install. In device manager it shows "Android composite adb interface".
The only good news is my phone still boots normally and I can use it. Please help me get back my fastboot so I can upgrade my phone to Lollipop and other modded ROM.
Thank you so much !!!!

techgeard said:
Hi guys, I'm having a weird problem with my zenfone 5 (a501cg). I have searched a lot but still can't find out a proper solution So I post it here and try to provide as much information as possible so hopefully developers at xda can help me.
My phone is rooted and I'm currently using modded rom called "bazzrom pinaslang" in the forum. Recently I want to use another rom so I decide to use adb sideload again.
However, the problem occurs: using adb sideload only show "error" message". BUT Adb devices show the phone.
Then I decide to use adb reboot fastboot to enter fastboot. But the phone only show a usb icon, and using "fastboot devices" doesn't show the device anymore.
I try other way by enter recovery mode "adb reboot recovery". The phone show resting android with "no command" message. I also try hold power and press down volumn after that but nothing happend. I try anything with that "power" + "volumn" combo but nothing happend (or it just shutdowns the phone).
Also, using "power" + "up volumn" to enter Droid boot doesn't work.
Driver is install. In device manager it shows "Android composite adb interface".
The only good news is my phone still boots normally and I can use it. Please help me get back my fastboot so I can upgrade my phone to Lollipop and other modded ROM.
Thank you so much !!!!
Click to expand...
Click to collapse
Hi,
Have you tried to boot into your system, enable USB debugging and run
Code:
adb reboot-bootloader
?

dgadelha said:
Hi,
Have you tried to boot into your system, enable USB debugging and run
Code:
adb reboot-bootloader
?
Click to expand...
Click to collapse
Hi dgadelha, thanks for your reply.
I have tried your suggestion before but phone only reboots and display usb icon. I also try power volumn combi like i did in my post but still nothing happened.
Usb debugging is enabled.
Techgeard.

techgeard said:
Hi dgadelha, thanks for your reply.
I have tried your suggestion before but phone only reboots and display usb icon. I also try power volumn combi like i did in my post but still nothing happened.
Usb debugging is enabled.
Techgeard.
Click to expand...
Click to collapse
In that case, follow the "Last resort" part of this guide http://www.asus.com/zentalk/forum.php?mod=viewthread&tid=33800
It will reinstall your fastboot when the USB icon appears

dgadelha said:
In that case, follow the "Last resort" part of this guide
It will reinstall your fastboot when the USB icon appears
Click to expand...
Click to collapse
Hi dgadelha,
I have seen your link before my post, but I still wonder because the "last resort" in the link is used for "bricked" phone or the one that doesn't start up or stuck in somewhere. My phone can still boot and use quite normal : ( except one thing that my sd card always unmounted in this Pinaslang modded rom.
TG.

UPDATE I decide to try xFSTK but my computer still recognizes the device as "adb..." . if I turn off developer mode it becomes "portable device" in Window Device Manager.
The xFSTK can't recognize any Cloverfieldplus. (it shows "CLOVERFIELDPLUS...: 0")
TG.

techgeard said:
Hi dgadelha,
I have seen your link before my post, but I still wonder because the "last resort" in the link is used for "bricked" phone or the one that doesn't start up or stuck in somewhere. My phone can still boot and use quite normal : ( except one thing that my sd card always unmounted in this Pinaslang modded rom.
TG.
Click to expand...
Click to collapse
Hi,
Because the last resort will use a hardware function (xFSTK way) to update your dnx, ifwi and fastboot images. This way you can restore your fastboot.
Thanks.
techgeard said:
UPDATE I decide to try xFSTK but my computer still recognizes the device as "adb..." . if I turn off developer mode it becomes "portable device" in Window Device Manager.
The xFSTK can't recognize any Cloverfieldplus. (it shows "CLOVERFIELDPLUS...: 0")
TG.
Click to expand...
Click to collapse
You must instal the drivers it mentioned.
Also it will appear as Cloverview when the USB logo appears
Thanks!

dgadelha said:
Hi,
Because the last resort will use a hardware function (xFSTK way) to update your dnx, ifwi and fastboot images. This way you can restore your fastboot.
Thanks.
You must instal the drivers it mentioned.
Also it will appear as Cloverview when the USB logo appears
Thanks!
Click to expand...
Click to collapse
Hi dgadelha,
After a while I can start the xFSTK and begin download. However, after some attempts it always say error. The same messages show up as below:
Code:
start
sending dner
writeoutpipe dner
writeoutpipe 0
write----> dner
windriver Error: 0x20000015, Timeour expired
LogError
Error Code:1 - Connection Error
Failed to start Dldr state matchine, aborting...
void CloverviewPlusDownloader::do_abort()
Abott
FAIL
.....

techgeard said:
Hi dgadelha,
After a while I can start the xFSTK and begin download. However, after some attempts it always say error. The same messages show up as below:
Click to expand...
Click to collapse
Hi techgeard,
Looks like it's a driver timeout.
Which OS are you using? I see they used Windows 7 or before on the tests.
Also you should try getting xFSTK developers (on SourceForge) to help about this issue.
Thanks.

dgadelha said:
Hi techgeard,
Looks like it's a driver timeout.
Which OS are you using? I see they used Windows 7 or before on the tests.
Also you should try getting xFSTK developers (on SourceForge) to help about this issue.
Thanks.
Click to expand...
Click to collapse
Iam using Win7x64. The same with the guy posting in the link.
TG.

I ruined my phone and i need help

Hi i need to unroot and factory reset the phone. Oneplus 2 What ive already done or tried: I started to try unrooting it through superSU but that didnt work i just waited waited and nothing hapened. so then i tried to fastboot img but just got error the device is locked even though i did enable oem unluck and usb debuging. so then i wrote in cmd: fastboot oem unlock and now the phone starts up to the op logo then restard into it again after a second D'=
Im not familiar with forums and very stressed to get my phone working so i would be very very gratefull for help.

now i cant even charge it the batery logo doesnt come up after i did fasboot oem unlock again.... rip

spacebite said:
Hi i need to unroot and factory reset the phone. Oneplus 2 What ive already done or tried: I started to try unrooting it through superSU but that didnt work i just waited waited and nothing hapened. so then i tried to fastboot img but just got error the device is locked even though i did enable oem unluck and usb debuging. so then i wrote in cmd: fastboot oem unlock and now the phone starts up to the op logo then restard into it again after a second D'=
Im not familiar with forums and very stressed to get my phone working so i would be very very gratefull for help.
Click to expand...
Click to collapse
spacebite said:
no i cant even charge it the batery logo doesnt come up after i did fasboot oem unlock again.... rip
Click to expand...
Click to collapse
Got to OnePlus support center and go in download section and download official ROM. Hold power and volume up bottons and connect it to PC. After that go in folder where adb files are located on your PC (If you don't have them, search on Google for "adb install 15 sec"). Hold left shift on your keyboard and right click your mouse in that folder on an empty space. Click something related with command window and type "fastboot devices". If you get some kind of feedback it's 2minute of work! If you don't have anything come up, try to start your device in fastboot mode again (second sentence in this post). After you got a feedback from command "fastboot devices" flash custom recovery (I suggest TWRP, Google it and download the .IMG file for your device). To flash a custom recovery type this in command line: "fastboot flash recovery IMAGE_NAME.img"
*replace IMAGE_NAME with actual image name...
After that boot in recovery by disconnecting the phone and powering off the phone. Press and hold power button and volume down buttons till blue TWRP logo appears. After that connect your device on PC and transfer your .Zip file(ROM) to internal memory of your device. You should go back to main menu of recovery and select wipe>advanced wipe, select everything BUT INTERNAL STORAGE!!!***IMPORTANT***
Then you just install ROM like you would normally do...
Press thanks it i helped! Hope I didn't missed something.
This is written in mind with that you have unlocked bootloader like you have written in your post...

x8Cooler said:
Got to OnePlus support center and go in download section and download official ROM. Hold power and volume up bottons and connect it to PC. After that go in folder where adb files are located on your PC (If you don't have them, search on Google for "adb install 15 sec"). Hold left shift on your keyboard and right click your mouse in that folder on an empty space. Click something related with command window and type "fastboot devices". If you get some kind of feedback it's 2minute of work! If you don't have anything come up, try to start your device in fastboot mode again (second sentence in this post). After you got a feedback from command "fastboot devices" flash custom recovery (I suggest TWRP, Google it and download the .IMG file for your device). To flash a custom recovery type this in command line: "fastboot flash recovery IMAGE_NAME.img"
*replace IMAGE_NAME with actual image name...
After that boot in recovery by disconnecting the phone and powering off the phone. Press and hold power button and volume down buttons till blue TWRP logo appears. After that connect your device on PC and transfer your .Zip file(ROM) to internal memory of your device. You should go back to main menu of recovery and select wipe>advanced wipe, select everything BUT INTERNAL STORAGE!!!***IMPORTANT***
Then you just install ROM like you would normally do...
Press thanks it i helped! Hope I didn't missed something.
This is written in mind with that you have unlocked bootloader like you have written in your post...
Click to expand...
Click to collapse
thanks i will try when i get home

Fallow this and don't trust any guides written out of memory with likely any mistakes.. (no offense)
This guide has various approaches to recover your phone, remember to research first and don't type carelessly any adb commands, it's not enough to just tick "oem unlock" in developer options, you'd have to type command on fastboot too, to unlock the bootloader.. there are many guides and youtube tutorials on this subject, absolutely unnecessary to blindly kill it, anyways I'll never understand how you can be so reckless with your phone..
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Edit: the state you brought your phone into is called "hard bricked" - have fun..
Sent from my OnePlus2 using XDA Labs

spacebite said:
thanks i will try when i get home
Click to expand...
Click to collapse
Don't!
If you get no joy from following the instructions in the link given by @Sam Nakamura, try @fareed_xtreme's Official OP2 Stock Reset to OOS 3.0.2

Sam Nakamura said:
Fallow this and don't trust any guides written out of memory with likely any mistakes.. (no offense)
This guide has various approaches to recover your phone, remember to research first and don't type carelessly any adb commands, it's not enough to just tick "oem unlock" in developer options, you'd have to type command on fastboot too, to unlock the bootloader.. there are many guides and youtube tutorials on this subject, absolutely unnecessary to blindly kill it, anyways I'll never understand how you can be so reckless with your phone..
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Edit: the state you brought your phone into is called "hard bricked" - have fun..
Sent from my OnePlus2 using XDA Labs
Click to expand...
Click to collapse
Aight thank you i had some suspicion it might be ...-bricked didnt know which though so thank you

If you can get in the bootloader then possibly the device is still OK. Just need to get the right ROM.
Try different TWRP versions. Sometimes, one particular version can save the world.

Huawei P9 lite Vns L23 bricked

Hello, im new to the forums and i would like to get some help with this huawei on what to do. I recieved this phone already bricked from a friend, so i would like to see if i can make it work again. I dont know how the phone got bricked and i have no idea of what to do. The problem is that the phone starts in the huawei logo and then goes to a black screen and turns itself off again. The phone doesnt make it past that point. I tried to make a reset from recovery, but it doesnt work. In download mode i tried to download the latest recovery, but it says failed to download. In fastboot mode the phone says "Phone unlocked" in red letters and "FRP locked" in green letters.
Any idea of what to do in order to recover the phone ?.

BrattPitlord said:
Hello, im new to the forums and i would like to get some help with this huawei on what to do. I recieved this phone already bricked from a friend, so i would like to see if i can make it work again. I dont know how the phone got bricked and i have no idea of what to do. The problem is that the phone starts in the huawei logo and then goes to a black screen and turns itself off again. The phone doesnt make it past that point. I tried to make a reset from recovery, but it doesnt work. In download mode i tried to download the latest recovery, but it says failed to download. In fastboot mode the phone says "Phone unlocked" in red letters and "FRP locked" in green letters.
Any idea of what to do in order to recover the phone ?.
Click to expand...
Click to collapse
Hello and welcome !
Just thinking you should try to start a fresh & clean install
rolling back to android 6 regardless of the current firmware.
Took a look inside the UNIFIED HELP THREAD but didn't find
any L23 rollback package...
However, I found another LINK that looks promising.
Good luck :fingers-crossed:
For further explanations try asking here.

Dadditz said:
Hello and welcome !
Just thinking you should try to start a fresh & clean install
rolling back to android 6 regardless of the current firmware.
Took a look inside the UNIFIED HELP THREAD but didn't find
any L23 rollback package...
However, I found another LINK that looks promising.
Good luck :fingers-crossed:
For further explanations try asking here.
Click to expand...
Click to collapse
Nice, i will try this and inform back later.

Dadditz said:
Hello and welcome !
Just thinking you should try to start a fresh & clean install
rolling back to android 6 regardless of the current firmware.
Took a look inside the UNIFIED HELP THREAD but didn't find
any L23 rollback package...
However, I found another LINK that looks promising.
Good luck :fingers-crossed:
For further explanations try asking here.
Click to expand...
Click to collapse
Well it didnt work. It says "incompatibility with this version"

BrattPitlord said:
Well it didnt work. It says "incompatibility with this version"
Click to expand...
Click to collapse
Hi,
you should use the follovinq commands in fastboot mode and then post the results please:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar version
fastboot getvar vendorcountry
Can you access Recovery ? (Power + Volume Up)

-Alf- said:
Hi,
you should use the follovinq commands in fastboot mode and then post the results please:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar version
fastboot getvar vendorcountry
Can you access Recovery ? (Power + Volume Up)
Click to expand...
Click to collapse
im new to this, so i put those commands in windows CMD with the phone connected or how ?
I can get to the stock recovery from huawei.

BrattPitlord said:
im new to this, so i put those commands in windows CMD with the phone connected or how ?
I can get to the stock recovery from huawei.
Click to expand...
Click to collapse
Use ADB commands.
Open developers option and turn on the USB debugging. Connect your device to PC in MTP/FILES mode. Run command
ADB reboot bootloader
(the device will reboot to fastboot mode)
Now you can type fastboot commands.

-Alf- said:
Use ADB commands.
Open developers option and turn on the USB debugging. Connect your device to PC in MTP/FILES mode. Run command
ADB reboot bootloader
(the device will reboot to fastboot mode)
Now you can type fastboot commands.
Click to expand...
Click to collapse
How do i turn debugging if the phone is bricked ? I cant get past the huawei logo. However, i do have access to fastboot mode.

BrattPitlord said:
How do i turn debugging if the phone is bricked ? I cant get past the huawei logo. However, i do have access to fastboot mode.
Click to expand...
Click to collapse
Oh, sorry, my mistake . Okay, install on your PC "Minimal ADB and fastboot" , open it , connect the device in fastboot mode, and run commands.