Database Users

[Q] Bricked and clueless ..

ok have an Iconia tab a500 here from a friend, he tells me he put in wrong adapter.
I think its bricked ..
ALready read alot of stuff here and did try some things but cant seem to find the correct solution .
I can connect in apx or fastboot and adb recognizes it also these all come up as hardware..
i dont have cpuid and thing is locked also and have usb debugging prob and isnt rooted ...
Bootloader = V0.0312-ics
if i start up i get " boot veriefied failed"
i found some downgrading method on here "method 2" but when i do it and he reboots i get the message "abort illegal blabla"
I would really appreciate if someone could help me point me in the right direction to start.
Using win7
also .. for repairing this thing ... i never came across such a complicated tablet .. djeez
Thx in advance
Grtz

Dhont said:
ok have an Iconia tab a500 here from a friend, he tells me he put in wrong adapter.
I think its bricked ..
ALready read alot of stuff here and did try some things but cant seem to find the correct solution .
I can connect in apx or fastboot and adb recognizes it also these all come up as hardware..
i dont have cpuid and thing is locked also and have usb debugging prob and isnt rooted ...
Bootloader = V0.0312-ics
if i start up i get " boot veriefied failed"
i found some downgrading method on here "method 2" but when i do it and he reboots i get the message "abort illegal blabla"
I would really appreciate if someone could help me point me in the right direction to start.
Using win7
also .. for repairing this thing ... i never came across such a complicated tablet .. djeez
Thx in advance
Grtz
Click to expand...
Click to collapse
how do you get fastboot with the ics bootloader??? Just wondering out loud!
you can try fastboot first see this thread and try flashing the recovery.img there
http://forum.xda-developers.com/showthread.php?t=2092414
run fastboot devices command and see if it returns you a ?
if it does go ahead and run the erase commands for userdata and cache
then flash cwm_recovery.img

kk
dibb_nz said:
how do you get fastboot with the ics bootloader??? Just wondering out loud!
you can try fastboot first see this thread and try flashing the recovery.img there
http://forum.xda-developers.com/showthread.php?t=2092414
run fastboot devices command and see if it returns you a ?
if it does go ahead and run the erase commands for userdata and cache
then flash cwm_recovery.img
Click to expand...
Click to collapse
Yes in fastboot it ruturn the "? fastboot"
my Bootloader that shows up when in fastboot says on acer screen :bootloader v0.03.12-ics rest of screen is black
in fastboot when i do oem unlock says in my terminal that it worked .. and on the pad the acer logo apears ..
if i ask for version it says 4.0
if i ask for serial he says : Kal-E1001
i read on site here that yer usb\UID has much to do with cpuid... my usb\uid is something like SB\VID_0502&PID_3201\5&1dd2df13&0&1 if fastboot connected i see it with usbdeview
if connected in usb recovery i see USB\VID_0955&PID_7820\5&1dd2df13&0&1 in deview
how to these relate to cpuid? or they have something to do with the kal-E1001?
Also i live in Belgium ... so i cant figure out wich or what packages to download but i got several yes .. prolly all ...
JUst info i wanted to give ..
But thx for the File gonna try that 1 now

Dhont said:
Yes in fastboot it ruturn the "? fastboot"
my Bootloader that shows up when in fastboot says on acer screen :bootloader v0.03.12-ics rest of screen is black
in fastboot when i do oem unlock says in my terminal that it worked .. and on the pad the acer logo apears ..
if i ask for version it says 4.0
if i ask for serial he says : Kal-E1001
Click to expand...
Click to collapse
bootloader version v0.03.12-ics this is the stock bootloader which is locked
i read on site here that yer usb\UID has much to do with cpuid... my usb\uid is something like SB\VID_0502&PID_3201\5&1dd2df13&0&1 if fastboot connected i see it with usbdeview
if connected in usb recovery i see USB\VID_0955&PID_7820\5&1dd2df13&0&1 in deview
how to these relate to cpuid?
Click to expand...
Click to collapse
This is what you need to see "0502" under VendorID and 3325 "ProductID", so again the numbers you posted arent the right ones
you need Linux to get your cpuid - there IS no other way for you now
see eppeP's method in the guide or the sticky in general by srbeen
Until you do this your tab will remain bricked -
Last resort - you might ask your friend to run usbdeview from his PC

dibb_nz said:
bootloader version v0.03.12-ics this is the stock bootloader which is locked
This is what you need to see "0502" under VendorID and 3325 "ProductID", so again the numbers you posted arent the right ones
you need Linux to get your cpuid - there IS no other way for you now
see eppeP's method in the guide or the sticky in general by srbeen
Until you do this your tab will remain bricked -
Last resort - you might ask your friend to run usbdeview from his PC
Click to expand...
Click to collapse
There is also the option of building against the Windows Driver Kit using MSVC.
This have the slight disadvantage of having to download about 1300MB (MSVC+WDK) and no instructions if you don't have any idea how to compile.
Besides having to have Windows...

Unlock bootloader on Axon 7 G latest B05

Hi guys,i was looking for guide how to unlock Axon 7 with latest update 1.2.0B05 but can't find anything. Can someone please help? I want to flash resurrection remix rom and not to brick phone...or is there better roms?

I cannot believe you're asking this question.
YOU HAVEN'T READ ANYTHING.
This board is full with uncountable guides.
https://forum.xda-developers.com/showthread.php?t=3573108

Not working....error: Length cannot be less than zero. Parameter name: length

salle25 said:
Not working....error: Length cannot be less than zero. Parameter name: length
Click to expand...
Click to collapse
Really, the last thing this forum needs is people unable to find guides on their own...
Ask @bkores about the error

WTF is wrong with you ppl?? I came to ask for help and you told me i'm retarded and stupid in nice way! If you don't wan't to help anyone then don't post reply or help and don't QQ about that! Thanx a lot!

salle25 said:
WTF is wrong with you ppl?? I came to ask for help and you told me i'm retarded and stupid in nice way! If you don't wan't to help anyone then don't post reply or help and don't QQ about that! Thanx a lot!
Click to expand...
Click to collapse
I'm sry but there's nobody here who will tell you're stupid,
People here are willing to help, but if you are too lazy to search for the guides (yes more then one is available) people will tell you that you are lazy.
Now I link a working guide for you
https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
If you want it easier, search for the toolkit, it will make the most work for you.

Nope....not working. axon7tool.exe keeps crashing: "This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information."
Toolkit is useless too,MiFlash doesn't see phone when in EDL mode,reinstaled every possible driver i found and not even Zadig helped. I had custom roms on every singe phone i had,but this one is pain in the ...

Got it sorted....renaming to .bin was problem,thanx

question
me too

salle25 said:
Got it sorted....renaming to .bin was problem,thanx
Click to expand...
Click to collapse
Yes it's a bit harder to unlock and flash, good you managed that, I forgot to tell you that there are two toolkits win32 and win64.

Help cant repair my Axon 7 G latest B05
coremania said:
Yes it's a bit harder to unlock and flash, good you managed that, I forgot to tell you that there are two toolkits win32 and win64.
Click to expand...
Click to collapse
I try to use both method and still withaut succes also have message before run my phone "Your device software can't be checked for corruption, Please lock the bootloader"
I try almost evrything and nothing.

Bizon86 said:
I try to use both method and still withaut succes also have message before run my phone "Your device software can't be checked for corruption, Please lock the bootloader"
I try almost evrything and nothing.
Click to expand...
Click to collapse
So what don't you understand on this message? It tells you that your bootloader is already unlocked [emoji779] [emoji779]

marcus.linkenbach said:
So what don't you understand on this message? It tells you that your bootloader is already unlocked [emoji779] [emoji779]
Click to expand...
Click to collapse
No is not unlocked Axontooolkit says something oposit. I try both guides from this topic and:
- twrp dosent instal
- cant allow oem unllock
- when use UNLOCK BOOTLOADER Miflash dosent see my devices

Bizon86 said:
I try to use both method and still withaut succes also have message before run my phone "Your device software can't be checked for corruption, Please lock the bootloader"
I try almost evrything and nothing.
Click to expand...
Click to collapse
Your bootloader is unlocked, you only got to managed the rest, read this thread here, you will see it's familiar to your situation, read to the end.
https://forum.xda-developers.com/axon-7/help/to-date-guide-rooting-a2017g-b04-t3666808

I try this and still. nothing

Bizon86 said:
I try this and still. nothing
Click to expand...
Click to collapse
This is a bit thin.
A bit more details, you don't manage to go to edl mode ?
Did you try zadig to to get the right drivers working ?
What do see in device manager ?
Can you boot to stock recovery?
Did you tried to start from scratch with the guide, not the toolkit ?
No detail, no help
Edit: if you use only the toolkit, may ask in the toolkit thread for help ???

coremania said:
This is a bit thin.
A bit more details, you don't manage to go to edl mode ?
Did you try zadig to to get the right drivers working ?
What do see in device manager ?
Can you boot to stock recovery?
Did you tried to start from scratch with the guide, not the toolkit ?
No detail, no help
Edit: if you use only the toolkit, may ask in the toolkit thread for help ???
Click to expand...
Click to collapse
Zadig works for axon7tool only, MiFlash uses COM while axon7tool uses usb protocol

- The edl is dont working because phone go blank after use command and computer dosent see it.
- i try zading and try another driver effect is the same.
- in device menager i see android device but only when smartfon is running
- i start from the scratch the effect is the same
- i cant turn allow oem
the problem is with phone if i use adb reboot computer dont see phone

Bizon86 said:
Then what i must do any idea?
Click to expand...
Click to collapse
First of all, understand what you just did. If you don't explain it in an understandable way, we won't get any of it...
So:
-You unlocked the bootloader.
-axon7toolkit failed somewhere, and you didn't tell us exactly where
-you didn't try to use any guide to retake from where it ended up failing
-you didn't try to enter any mode
So just try to get to recovery or fastboot, using the 5 sec screen. After that we'll see

Bizon86 said:
- The edl is dont working because phone go blank after use command and computer dosent see it.
- i try zading and try another driver effect is the same.
- in device menager i see android device but only when smartfon is running
- i start from the scratch the effect is the same
- i cant turn allow oem
the problem is with phone if i use adb reboot computer dont see phone
Click to expand...
Click to collapse
If you go to edl, by adb command or by pressing both volume buttons while connecting usb the screen goes blank, that's ok, it has to be this way.
Why you want to turn on allow oem, you are already unlocked.
Your issue seems to be the driver, I guess.
Edit: try this maybe, from the toolkit FAQ
The toolkit says my device is connected through ADB but adb commands don't work?
Your device may be unauthorized. Unlock your device, open a cmd window, type in "adb devices" and then accept the "Allow USB debugging" prompt on your phone. Make sure to check the "Always allow from this computer" box as well. If you don't get the prompt, try retoggling USB debugging, replugging your device in, and revoking all USB debugging authorizations in developer options.

Need help unlocking bootloader

I've tried several times to unlock the bootloader and it will not respond to any commands once in fastboot mode. I've tried to follow this guide https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/ but whenever I type "fastboot oem unlock" it just says "waiting for any device" and nothing happens. I have usb debugging enabled and oem unlocking on so I don't know what I'm doing wrong. I have the platform tools from Google installed. I can run adb and type "adb reboot bootloader" and it responds, but after that, no fastboot commands work. I mainly just wanted to root so I could restore my apps and data via Titanium Backup. Is there a temp root solution I can use? Or has anyone else experienced this?
Let me know if you need more info. Hopefully this is an easy one.

What do you get if you run "adb devices"?

thedrizzle said:
What do you get if you run "adb devices"?
Click to expand...
Click to collapse
ADB: USAGE: unknown command DEVICES
Or do you mean run it while it's in fastboot?

I feel like it's something simple I'm missing. I've never had trouble figuring this stuff out. I've been rocking an HTC M8 on VenomRom since forever ago so it was time for an upgrade. I've looked at several different guides, but some of them seem to be incomplete. Like the guide at the official TWRP page says to power off the phone. Then it says to hold volume up to go into fastboot mode. I tried following those instructions to a T, but that didn't actually do anything. It doesn't say where to put the twrp.img file, it just says to run the command to boot the .img. Getting into fastboot isn't a problem. It's that no matter what I do once it's in fastboot, I just get "waiting for any device". I've tried the OnePlus6t Manager because I thought maybe I needed a one-click method. But again, it gets to fastboot and goes nowhere from there.

blockhead428 said:
I feel like it's something simple I'm missing. I've never had trouble figuring this stuff out. I've been rocking an HTC M8 on VenomRom since forever ago so it was time for an upgrade. I've looked at several different guides, but some of them seem to be incomplete. Like the guide at the official TWRP page says to power off the phone. Then it says to hold volume up to go into fastboot mode. I tried following those instructions to a T, but that didn't actually do anything. It doesn't say where to put the twrp.img file, it just says to run the command to boot the .img. Getting into fastboot isn't a problem. It's that no matter what I do once it's in fastboot, I just get "waiting for any device". I've tried the OnePlus6t Manager because I thought maybe I needed a one-click method. But again, it gets to fastboot and goes nowhere from there.
Click to expand...
Click to collapse
Do not forget to enable OEM Unlocking in Developer options
Sent from my ONEPLUS A6013 using Tapatalk

Just my 2 cents I'm not an expert but it Might be your drivers or when you installed adb did you do it with administrator rights? The first time tried I couldn't get it to work it wasn't detecting the device in fastboot so I reinstalled adb and then it worked
I just rooted mines today but I went off a YouTube video I looked up and they had everything you needed to download in the description. Took about ten minutes ? I'm not sure if I can put a link on here

DinarQ8 said:
Do not forget to enable OEM Unlocking in Developer options
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
I've done that also. Developer options are enabled, USB debugging, and OEM unlocking. Are there newer drivers I need? But if that was an issue, it wouldn't allow me to do "adb reboot bootloader". It'll reboot to fastboot mode, but after typing "fastboot oem unlock" it just says waiting for any device.

blockhead428 said:
ADB: USAGE: unknown command DEVICES
Or do you mean run it while it's in fastboot?
Click to expand...
Click to collapse
In the picture it shows you typed your commands all capitals letters

Dr8ven said:
Just my 2 cents I'm not an expert but it Might be your drivers or when you installed adb did you do it with administrator rights? The first time tried I couldn't get it to work it wasn't detecting the device in fastboot so I reinstalled adb and then it worked
I just rooted mines today but I went off a YouTube video I looked up and they had everything you needed to download in the description. Took about ten minutes I'm not sure if I can put a link on here
Click to expand...
Click to collapse
Try and post it. It let me post the link to the guide in the initial posting. You could be on to something.
This is where I got my version of ADB. https://developer.android.com/studio/releases/platform-tools It's not so much an "install" as it is unpacking a zip archive.

twinnfamous said:
In the picture it shows you typed your commands all capitals letters
Click to expand...
Click to collapse
I did not know it was case-sensitive. I just tried again and it seems to show my devices (I'm transferring files off of my m8 which is why it shows two).
Good call, brother! Where do I go from here?

blockhead428 said:
I did not know it was case-sensitive. I just tried again and it seems to show my devices (I'm transferring files off of my m8 which is why it shows two).
Good call, brother! Where do I go from here?
Click to expand...
Click to collapse
you need to be careful in fastboot. One wrong command can lead to a catastrophe.

I used the adb installer from the same video. Once you unzip it. It's an .exe file which I granted administrator rights to install... it installs adb and drivers and it worked for me
That's the video and did it to a T
Another thing don't use power shell use command

twinnfamous said:
you need to be careful in fastboot. One wrong command can lead to a catastrophe.
Click to expand...
Click to collapse
I'm following a video now. I'm thinking I didn't have the ADB drivers installed so I'm trying that now.

Let us know how it turned out ?

Dr8ven said:
Let us know how it turned out
Click to expand...
Click to collapse
Still getting nowhere. I thought my problem was that I didn't intall the drivers as administrator. So I did it again, following this video https://www.youtube.com/watch?v=B-XZy27wy5o When I reboot into bootloader, I type "fastboot devices" and it just goes right back to the command prompt. Nothing happens. I guess I'm going to try the old fashioned computer restart and see what happens. If all else fails, I can unplug it from the wall and blow on it, lol.
I swear, I've never been this simple before.

blockhead428 said:
Still getting nowhere. I thought my problem was that I didn't intall the drivers as administrator. So I did it again, following this video https://www.youtube.com/watch?v=B-XZy27wy5o When I reboot into bootloader, I type "fastboot devices" and it just goes right back to the command prompt. Nothing happens. I guess I'm going to try the old fashioned computer restart and see what happens. If all else fails, I can unplug it from the wall and blow on it, lol.
I swear, I've never been this simple before.
Click to expand...
Click to collapse
::sigh:: Still no joy. Restarted pc, ran adb devices and it showed my phone. So i reboot into bootloader, typed fastboot devices and it still took me right back to the command prompt.

blockhead428 said:
::sigh:: Still no joy. Restarted pc, ran adb devices and it showed my phone. So i reboot into bootloader, typed fastboot devices and it still took me right back to the command prompt.
Click to expand...
Click to collapse
I was thinking that maybe the latest OTA broke the bootloader unlock process, but someone else in this thread said they just unlocked theirs. I don't understand what the issues is. I've followed this video so closely I could re-enact it in my sleep.

Got it! I had two sets of drivers installed so I uninstalled both and it finally recognized my phone in fastboot. My old drivers from my m8 from 2014 were probably interfering with it. I knew it was something simple. I feel like Carl in Sling Blade when they bring him the lawn mower engine and he says "ain't got no gas in it, mmhmmm".

Nice! For a noob I wasn't too far off lol it just had to be one of those two issues
Enjoy happy rooting ?

blockhead428 said:
Got it! I had two sets of drivers installed so I uninstalled both and it finally recognized my phone in fastboot. My old drivers from my m8 from 2014 were probably interfering with it. I knew it was something simple. I feel like Carl in Sling Blade when they bring him the lawn mower engine and he says "ain't got no gas in it, mmhmmm".
Click to expand...
Click to collapse
Hi I have the same problem, when fastboot it says waiting device. I also had rooted my other phone, so how to find my other driver phone in device manager because I can't find it

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.

trouble with unlocking my bootloader

hey guys,
i just got my 8 pro in the mail, and need to unlock my bootloader. i turned on usb debugging, installed the usb drivers on my pc, and the platform tools.
i pulled up this guide to help: https://forum.xda-developers.com/oneplus-8-pro/how-to/guide-unlocking-bootloader-rooting-t4151823
this is indeed an EU model
im able to run .\ adb devices, and see my device
then, after running .\ adb reboot boatloader, i reach a screen where i am given three language options, and my device shows up under .\fastboot devices
after running .\fastboot unlock oem, i get this message
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
PS C:\Users\FPSReach\Downloads\platform-tools_r30.0.5-windows\platform-tools>
does anyone have any idea what i can do?
sorry if this has been covered before, i did some light searching but really couldnt understand much

FPSReach said:
hey guys,
i just got my 8 pro in the mail, and need to unlock my bootloader. i turned on usb debugging, installed the usb drivers on my pc, and the platform tools.
i pulled up this guide to help: https://forum.xda-developers.com/oneplus-8-pro/how-to/guide-unlocking-bootloader-rooting-t4151823
this is indeed an EU model
im able to run .\ adb devices, and see my device
then, after running .\ adb reboot boatloader, i reach a screen where i am given three language options, and my device shows up under .\fastboot devices
after running .\fastboot unlock oem, i get this message
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
PS C:\Users\FPSReach\Downloads\platform-tools_r30.0.5-windows\platform-tools>
does anyone have any idea what i can do?
sorry if this has been covered before, i did some light searching but really couldnt understand much
Click to expand...
Click to collapse
Shouldn't it be "fastboot oem unlock"?

Yes, that's correct "fastboot oem unlock"

Just follow my guide bud
https://forum.xda-developers.com/oneplus-8-pro/how-to/guide-unlocking-bootloader-rooting-t4151823
Easy step by step

Kollachi said:
Shouldn't it be "fastboot oem unlock"?
Click to expand...
Click to collapse
Yes, my bad, i typed it wrong on here
Just to make sure, i gave it another go right now and got the same " Unable to open fastboot HAL" message

dladz said:
Just follow my guide bud
https://forum.xda-developers.com/oneplus-8-pro/how-to/guide-unlocking-bootloader-rooting-t4151823
Easy step by step
Click to expand...
Click to collapse
Hi sir
You guide is actually the one i found for this
After performing step 3, and reaching the screen with a green START above it, my device no longer responds to fastboot commands, and does not show up after i enter .\fastboot devices (i do still see "fastboot mode" in red text though, weirdly enough)
The only time that my device shows up after entering .\fastboot devices is at the start of step 3, on the language selection screen
What do i do to fix this?

FPSReach said:
Hi sir
You guide is actually the one i found for this
After performing step 3, and reaching the screen with a green START above it, my device no longer responds to fastboot commands, and does not show up after i enter .\fastboot devices (i do still see "fastboot mode" in red text though, weirdly enough)
The only time that my device shows up after entering .\fastboot devices is at the start of step 3, on the language selection screen
What do i do to fix this?
Click to expand...
Click to collapse
? Never had that issue myself. The steps are taken from verified sources and I ran through it myself when I unlocked mine, no one else has said this.
Potentially a driver issue, you using Windows 10 ? Usb 2 or 3? Sometimes people have issues with 3, 2 seems to work for them..
It's been a while since I was on that screen...but the process should be as written.
See if fastboot mode is an option in the start screen (after you've used the ADB reboot bootloader command)

dladz said:
? Never had that issue myself. The steps are taken from verified sources and I ran through it myself when I unlocked mine, no one else has said this.
Potentially a driver issue, you using Windows 10 ? Usb 2 or 3? Sometimes people have issues with 3, 2 seems to work for them..
It's been a while since I was on that screen...but the process should be as written.
See if fastboot mode is an option in the start screen (after you've used the ADB reboot bootloader command)
Click to expand...
Click to collapse
I am on windows 10 and downloaded the usb drivers for the 8 pro beforehand. I just tried again with a usb 2 port, the results are the same.
After using the .\adb reboot bootloader command, my phone screen says "fastboot mode" with the green "start" on top (i just took a pic, to confirm, this is my screen https://imgur.com/tduDZsz ) but at this stage my phone is no longer detected and does not show up under .\fastboot devices or .\adb devices
just for funsies, i downloaded an third party app on my pc called reiboot to get me into fastboot mode
again, it got my phone to this same screen and then said it "failed to enter fastboot" and could no longer detect my phone
this is a brand new model too, a european one, i made this thread within a couple hours of it coming

dladz said:
? Never had that issue myself. The steps are taken from verified sources and I ran through it myself when I unlocked mine, no one else has said this.
Potentially a driver issue, you using Windows 10 ? Usb 2 or 3? Sometimes people have issues with 3, 2 seems to work for them..
It's been a while since I was on that screen...but the process should be as written.
See if fastboot mode is an option in the start screen (after you've used the ADB reboot bootloader command)
Click to expand...
Click to collapse
....oh my god.
I am so sorry, the mistake was on my end.
I followed the instructions meticulously, don't get me wrong.
In a last ditch attempt though, I repeated the process on my old windows 7 laptop with a command prompt
It worked. Im sorry to have disturbed you over this.
If anyone else ever finds this thread while looking for answers, use another computer, i should have tried that earlier.

FPSReach said:
....oh my god.
I am so sorry, the mistake was on my end.
I followed the instructions meticulously, don't get me wrong.
In a last ditch attempt though, I repeated the process on my old windows 7 laptop with a command prompt
It worked. Im sorry to have disturbed you over this.
If anyone else ever finds this thread while looking for answers, use another computer, i should have tried that earlier.
Click to expand...
Click to collapse
So it was a driver issue. Because I did it with Win10 and USB 3.

Kollachi said:
So it was a driver issue. Because I did it with Win10 and USB 3.
Click to expand...
Click to collapse
It probably was, i have no idea what else it could be, honestly

FPSReach said:
....oh my god.
I am so sorry, the mistake was on my end.
I followed the instructions meticulously, don't get me wrong.
In a last ditch attempt though, I repeated the process on my old windows 7 laptop with a command prompt
It worked. Im sorry to have disturbed you over this.
If anyone else ever finds this thread while looking for answers, use another computer, i should have tried that earlier.
Click to expand...
Click to collapse
Yep windows 7 has caused issues in the past, shame really as it's still got it's uses as an OS.
Glad you're sorted.
---------- Post added at 05:46 PM ---------- Previous post was at 05:45 PM ----------
Kollachi said:
So it was a driver issue. Because I did it with Win10 and USB 3.
Click to expand...
Click to collapse
That's correct as 7 chooses the wrong one. Don't think the 10 driver would work.
Haven't looked into it.

dladz said:
Yep windows 7 has caused issues in the past, shame really as it's still got it's uses as an OS.
Glad you're sorted.
---------- Post added at 05:46 PM ---------- Previous post was at 05:45 PM ----------
That's correct as 7 chooses the wrong one. Don't think the 10 driver would work.
Haven't looked into it.
Click to expand...
Click to collapse
Driver issue is sometimes hard to figure out.