Develop Bugs

Successfully Unlocked Bootloader But Still Says Locked. Help needed.

EDIT: Fixed (Post #2)
After years of successfully unlocking bootloaders and rooting all my phones, I'm at a loss on this one...
I went through the process of unlocking my bootloader. And I'm able to use the basic fastboot commands (reboot bootloader and reboot). However, when I try to boot TWRP (still on Sep 5th update) it says it can'ed because my bootloader is still in the locked state.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In addition, when I'm in the bootloader it says "Devices State: Locked" - Indicating that the bootloader is not unlocked, even though it is.
Process:
1) Enabled Developer options and checked "Allow OEM Unlocking" and "USB Debugging"
2) Connect phone to computer and run "ADB Devices" using CMD
3) Accept the ADB approval pop-up on the phone
4) Confirm the computer recognizes the phone through ADB
5) "adb reboot bootloader"
6) (phone now in bootloader) "fastboot devices" to ensure CMD recognizes the phone and it does
7) fastboot boot /path/to/twrp.img
8) Fails due to "Locked State"
But when I try to unlock the phone again, it says it's already unlocked (check above screenshot).
I'm stumped.
Any ideas?

I was able to fix it. I tried fastboot flashing unlock instead of fastboot flashing unlock_critical and it fully unlocked the phone. Fastboot shows the device as unlocked and I can now boot TWRP.

sn0warmy said:
I was able to fix it. I tried fastboot flashing unlock instead of fastboot flashing unlock_critical and it fully unlocked the phone. Fastboot shows the device as unlocked and I can now boot TWRP.
Click to expand...
Click to collapse
Just want thru same thing. Yup, regular unlock command worked for me too.

Same thing happened to me I just ran the regular command and it unlocked as well.

You need a different cable, the usbc to usbc cable does not allow you to do everything. Trust me I was stuck for nearly 24 he's trying figure out why it kept saying my phone was locked even tho it wasn't.

mackentosh said:
You need a different cable, the usbc to usbc cable does not allow you to do everything. Trust me I was stuck for nearly 24 he's trying figure out why it kept saying my phone was locked even tho it wasn't.
Click to expand...
Click to collapse
It's not the cable. I used the USB-A to USB-C cable from the Google Store. I learned this lesson with issues utilizing the USB-C to USB-C cable with the original Pixel XL.
This cable:
https://store.google.com/us/product/usb_c_usb_a_2?hl=en-US

mackentosh said:
You need a different cable, the usbc to usbc cable does not allow you to do everything. Trust me I was stuck for nearly 24 he's trying figure out why it kept saying my phone was locked even tho it wasn't.
Click to expand...
Click to collapse
Usba to c used here too. C to c wouldn't work.

mackentosh said:
>>signature<<.
Click to expand...
Click to collapse
You ass, I thought that was an actual bug on my screen.

socal87 said:
You ass, I thought that was an actual bug on my screen.
Click to expand...
Click to collapse
?????????

When?
sn0warmy said:
I was able to fix it. I tried fastboot flashing unlock instead of fastboot flashing unlock_critical and it fully unlocked the phone. Fastboot shows the device as unlocked and I can now boot TWRP.
Click to expand...
Click to collapse
After what step do I enter that command?

Unable to use fastboot miui P beta

I just flashed the beta for Android p of rn5pro global. Everything works. But at the moment to go into fastboot, it goes but typing fastboot devices keep showing waiting for device. I unplugged it and try again fastboot devices using the redmi note 4 and mi 3 instantly. It only happen with the r5 any ideas ? I tried using the mi flash tool also it didn't recognize it.
What I want I to be available to use fastboot again. To flash the recovery and root it.

Place some images for the community to see how Android P is on our device.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And how exactly is that gonna help in any way??? sarcasm

Yesterday i've used fastboot just fine on pie

Make sure to install Redmi note 5 pro device driver

Jctatis said:
I just flashed the beta for Android p of rn5pro global. Everything works. But at the moment to go into fastboot, it goes but typing fastboot devices keep showing waiting for device. I unplugged it and try again fastboot devices using the redmi note 4 and mi 3 instantly. It only happen with the r5 any ideas ? I tried using the mi flash tool also it didn't recognize it.
What I want I to be available to use fastboot again. To flash the recovery and root it.
Click to expand...
Click to collapse
check for USB 2.0 instead of 3.0

lcdkhoa said:
check for USB 2.0 instead of 3.0
Click to expand...
Click to collapse
Tried this didn't work. I funny think is that phone on gr find. I when I type reboot fastboot it stop working. The phone appear after test point. I but when I go manually from os to fastboot the oh flash tool doesn't recognise it. I

edi194 said:
Yesterday i've used fastboot just fine on pie
Click to expand...
Click to collapse
Is there a possibility of the fastboot been ? or death? I
I have unlockbootloader. Just want to know is there is a possibility that the fastboot mode lock itself and stop working

SunilSuni said:
Make sure to install Redmi note 5 pro device driver
Click to expand...
Click to collapse
The drivers been always there. It just stooped working after updating to this rom. I mean the phone works I'm replying from it. Gonna try from another laptop a clean install on drivers

Jctatis said:
Is there a possibility of the fastboot been ? or death? I
I have unlockbootloader. Just want to know is there is a possibility that the fastboot mode lock itself and stop working
Click to expand...
Click to collapse
I've used fastboot mode with Pie on MIUI (both Xiaomi.eu and Global Beta) and it was fine like always, install XDA's minimal ADB&Fastboot, always used It for all of my devices

Jctatis said:
Is there a possibility of the fastboot been ? or death? I
I have unlockbootloader. Just want to know is there is a possibility that the fastboot mode lock itself and stop working
Click to expand...
Click to collapse
No, that's not possible, probably the new bootloader has a lot of bugs and that's the reason why you pc can't detect the phone, you have 3 options: reinstall everything in your PC (I mean drivers, MiFlash, etc etc [Windows is Windows you know..] and try with differents cables, ports etc), try with differents PC's or stay in Pie until Xiaomi fixes the bugs.

onliner said:
No, that's not possible, probably the new bootloader has a lot of bugs and that's the reason why you pc can't detect the phone, you have 3 options: reinstall everything in your PC (I mean drivers, MiFlash, etc etc [Windows is Windows you know..] and try with differents cables, ports etc), try with differents PC's or stay in Pie until Xiaomi fixes the bugs.
Click to expand...
Click to collapse
tried fresh install window, when typing fastboot devices, show waiting device. unplugged and plugged again but no sound of device been connected. the driver are working fine when i connect other phone (redmi note 4) theres only sound when i go to "connect to the miAs$istant" but no recognize neither with the flash mi tool. when is in the "miAs$istant it show adb driver on the device manager" but when is in fastboot it doesn't even sound or show drivers.
tried different cables.
i guess the only option now is wait for and update that may fix the fastboot. or maybe my fastboot is blocked dunno... anyway thanks for the time and the asistantance :good:

Jctatis said:
tried fresh install window, when typing fastboot devices, show waiting device. unplugged and plugged again but no sound of device been connected. the driver are working fine when i connect other phone (redmi note 4) theres only sound when i go to "connect to the miAs$istant" but no re... :good:
Click to expand...
Click to collapse
Just do as I say :
Open device manager,you will find that a driver Android is missing (which wasn't the case previously on fastboot) .Install the drivers from the link in this video description: https://youtu.be/eQSAD8tNOaA
Do the fastbooty thing....
Thank me later

You can make a bootable USB with Ubuntu and boot it from the USB without installing. Then install adb and try and see if it works. That way you can confirm if it is the phone or your windows that is causing issues.

You went to fastboot from recovery? It doesn't work. I had the same problem - full shutdown and then boot with power and volume down.
Wysłane z mojego Redmi Note 5 przy użyciu Tapatalka

Guys I have problem with adb fastboot after flash this leaked firmware.
I am stucked with this release.
CMD failed the flash of TWRP for the package size and it recognize my RN5 random.
Another users have this issue with latest release.

Jctatis said:
Is there a possibility of the fastboot been or death? I
I have unlockbootloader. Just want to know is there is a possibility that the fastboot mode lock itself and stop working
Click to expand...
Click to collapse
For me it stopped working on xiaomi.eu firmware, reflashing to global beta worked

Jctatis said:
tried fresh install window, when typing fastboot devices, show waiting device. unplugged and plugged again but no sound of device been connected. the driver are working fine when i connect other phone (redmi note 4) theres only sound when i go to "connect to the miAs$istant" but no recognize neither with the flash mi tool. when is in the "miAs$istant it show adb driver on the device manager" but when is in fastboot it doesn't even sound or show drivers.
tried different cables.
i guess the only option now is wait for and update that may fix the fastboot. or maybe my fastboot is blocked dunno... anyway thanks for the time and the asistantance :good:
Click to expand...
Click to collapse
USB debugging option enabled? If yes, then fastboot commands won't work. Try to disable it and then execute commands. It should work. I'm in the same boat as you when fastboot suddenly stopped working. Only thing I did is to enable USB debugging. So I disabled and all fine. I'm on 9.3.25 Miui Pie btw. Try it. It may or may not work..but that's how it works on my device. Wierd af

Thank for all the replies I gonna try all the options I didn't try Joe new ones you guys mention, the ubuntu one guess is os or a virtual machine

Same problem after latest update of Miui Pie , test tomorrow with my old PC , I have the doubt if the problem is my new Notebook Asus TUF FX504 GM , USB 3.0 break the fastboot.
I have used same driver of the old PC and same method.
Fastboot work but same flash error "the package size bla bla bla......"and disconnect fastboot connection random.

Bootloader driver issues on Windows 10?

I made this post to hopefully help me help you help us.
My Razer Phone is currently unable receive any commands while in fastboot mode/bootloader.
This seems to be a fairly common problem that I see some people are running into without having any concrete solution. I have tried numerous suggestions and then some. Therefore, I want to provide as much information and background to the problem to try and help anyone with more experience that is willing to get to the bottom of this.
So for some background, I successfully rooted my Razer Phone with help from both of these threads:
Rooting Android 9 December Update With Magisk (No TWRP)(Global)
and
[TWRP + MAGISK] FULLPROOF Guide for all Razers! Wifi Fix!
I primarily used the first thread listed to achieve root.
The phone is currently on the stock ROM, rooted with magisk installed. I do not have TWRP installed. It works perfectly fine under normal use.
I am trying to revert to stock and relock my bootloader using Razer's guide HERE. When using the 'flash_all' script that the guide references, the script fails, because the phone cannot receive fastboot commands.
I followed Razer's installation guide PDF to install the adb/fastboot drivers.
I have also tried using ClockworkMod's Universal ADB Driver.
EDIT: I also tried using [Tool] Latest ADB Fastboot and USB Driver installer tool for Windows
The phone is currently on the stock ROM, rooted with magisk installed. I do not have TWRP installed. It works perfectly fine under normal use.
I'm pretty sure I have installed the adb drivers correctly. I can use adb commands while android is running. It's listed when using the "adb devices" command. It successfully restarts and enters the bootloader after typing "adb reboot bootloader", but after typing "fastboot device", it only outputs "< waiting for any device >" and waits. I have also tried using the command "fastboot -i 0x1532 devices" as suggested in a related thread, but this just returns "fastboot.exe: unknown option -- i" and fails.
I have also tried selecting "Android ADB Interface", as well as "Android Bootloader Interface" when installing the google usb driver. I even tried using the third option, no luck.
Now here's why I say that I'm pretty sure that I have the drivers installed correctly:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is what is displayed in Device Manager when the phone is in fastboot mode and connected to my PC after installing the drivers.
It displays normal when android is running with or without USB debugging enabled.
I have tried this on a few Windows 10 PCs and get the same result. So, I wouldn't be able to tell if this is a Windows problem or if it is my phone:
This is what my bootloader shows. Besides the serial number I blocked out, notice how some data is missing? Could this be the problem?
I'm curious to know the method of root everyone else having this problem had used and whether their bootloader looks like this.
I understand the community for this phone isn't as active as it used to be.
So, thank you to anyone in advance for the help and your time.

This devices is tricky for sure. Everything worked just fine when I unlocked bootloader a few months back, but now when I wanted to flash LOS I just couldn't get anything working with drivers.
Then I stumbled upon this [Tool] Latest ADB Fastboot and USB Driver installer tool for Windows and it actually installed the correct driver.
Adb & fastboot all works fine after that.

tys0n said:
This devices is tricky for sure. Everything worked just fine when I unlocked bootloader a few months back, but now when I wanted to flash LOS I just couldn't get anything working with drivers.
Then I stumbled upon this [Tool] Latest ADB Fastboot and USB Driver installer tool for Windows and it actually installed the correct driver.
Adb & fastboot all works fine after that.
Click to expand...
Click to collapse
I forgot to mention that I had also tried this tool to install the drivers on a few different PCs. I did all of this (including other methods) after making sure to uninstall any drivers that were previously installed. The installation succeeds, but still has no effect on the phone being detected when it's in fastboot. Everything else, like file transfer and adb commands does.
Thank you for your time and for replying.

I've had the same problems you've had Waffle. I tried everything I could read in the forms, what ended up fixing the driver issues for me was to use Linux. I owe it to Linux's superior driver support that fixed the issue for me.

Well, I finally got it to work. I decided to try the tool tys0n mentioned again, and it worked. Not sure what I did differently this time, but I am thankful that it is now connecting properly.
Sorry for piggybacking onto my own post but now, after using the razer file to factory reset and lock the bootloader, the screen says "Your device has loaded a different operating system." on boot and some apps still say that the phone is rooted. When accessing the bootloader it says that everything is locked and the OEM Unlocking switch is disabled in developer options. Not sure what I may have done wrong, since it's just running a script for the most part or if it's just stuck like this since I rooted the phone in general.

Question Fastboot commands not working 9 pro unlocked variant not T-Mobile AA

It’s been a while since my last root project I was able to download and install one plus drivers. Got adb downloaded, my phone is recognized initially when when I try the command adb devices. Enter the command adb reboot bootloader which works flawlessly. However once in bootloader mode none of the Fastboot commands work. I keep on getting the waiting for device prompt.
I check device manager in windows 10 and the device is showing. Am I missing something? I tried 3 different cables, USB ports I can’t figure it out. Is there a special adb package I need to get or driver or something?
Quick specs
X570 chipset
AMD Ryzen 9 5900x
Gigabyte arous Master v2
I am using a usb 3.0 hub however I tried different ports on my pc and same issue
Oem unlock is enabled
Windows 10 Pro
Official one plus drivers
No other usb are connected besides the one hub.
Any help would be much appreciated.
Thanks

Make sure that you use the latest Platform tools from the Android website when using ADB or Fastboot. Also, can you show a screenshot of the device manager here when you're connected with your device in Fastboot mode?

here is a screenshot of my device manager when im in windows and my phone is at the home screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here what it shows in fastboot bootloader mode

nofroyo said:
here is a screenshot of my device manager when im in windows and my phone is at the home screen
View attachment 5665575
Here what it shows in fastboot bootloader mode
View attachment 5665577
Click to expand...
Click to collapse
You're missing the Fastboot drivers as you can see on the SS, Android connected, but it's missing the driver. Remember, OnePlus Drivers don't install the fastboot drivers, just standard ADB. Also, Fastboot uses different set of drivers, they're not the same as ADB.
I uploaded the ADB-Setup, install it, and it will install the Fastboot drivers too from Google. Make sure that your phone is connected to the PC and in fastboot (bootloader) mode when installing these.
After, restart the PC once, and you're good to go.

ekin_strops said:
You're missing the Fastboot drivers as you can see on the SS, Android connected, but it's missing the driver. Remember, OnePlus Drivers don't install the fastboot drivers, just standard ADB. Also, Fastboot uses different set of drivers, they're not the same as ADB.
I uploaded the ADB-Setup, install it, and it will install the Fastboot drivers too from Google. Make sure that your phone is connected to the PC and in fastboot (bootloader) mode when installing these.
After, restart the PC once, and you're good to go.
Click to expand...
Click to collapse
Thank you for the help I got it working, now I just need to figure out which root package I use for my phone. seem like a few different versions from what i can see. AA device is unlocked north american variant

Question Bricked OnePlus9 Pro Unlocked Options For Newbie;)

Hi Guys,
Looks like my phone is bricked noob mistake, what exactly are my options please?
Phone is stuck in fastboot mode whatever option I choose returns to fastboot, I am on linux pc so not sure the software options are compatible?
Any help would be greatly appreciated. I was following the LineageOS on lemonadep wiki
Thanks
Daz

dazuk9269 said:
Hi Guys,
Looks like my phone is bricked noob mistake, what exactly are my options please?
Phone is stuck in fastboot mode whatever option I choose returns to fastboot, I am on linux pc so not sure the software options are compatible?
Any help would be greatly appreciated. I was following the LineageOS on lemonadep wiki
Thanks
Daz
Click to expand...
Click to collapse
Retry the flashing process again. Making sure to skip no steps. Make sure of your original os version (11, 12, 13) as needed for the img you are willing to install.

TheGhost1951 said:
Retry the flashing process again. Making sure to skip no steps. Make sure of your original os version (11, 12, 13) as needed for the img you are willing to install.
Click to expand...
Click to collapse
Tried that mate whatever I do returns to fastboot

dazuk9269 said:
Tried that mate whatever I do returns to fastboot
Click to expand...
Click to collapse
I suspect you are trying to flash the wrong version. If all else fails, you will need to MSM back to stock and start off fresh!

TheGhost1951 said:
I suspect you are trying to flash the wrong version. If all else fails, you will need to MSM back to stock and start off fresh!
Click to expand...
Click to collapse
Ok mate any tutorial for a noob lol on how to do this, just fired up a windows vm so no issues if MSM can only be used on windows, I tried installing with wine on linux but just errors

dazuk9269 said:
Ok mate any tutorial for a noob lol on how to do this, just fired up a windows vm so no issues if MSM can only be used on windows, I tried installing with wine on linux but just errors
Click to expand...
Click to collapse
You don't normally install MSM, just extract it and then open folder and start the MSM tool. This link has everything you need. Even on how to use the MSM tool. Read all instructions until you fully understand before proceeding....
OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)
By using these tools, you accept full responsibility for your actions. Your warranty is void should you run any of these utilities without OnePlus support present. I am not responsible for bricks, fires, nuclear war, etc. If you modified any...
forum.xda-developers.com

TheGhost1951 said:
You don't normally install MSM, just extract it and then open folder and start the MSM tool. This link has everything you need. Even on how to use the MSM tool. Read all instructions until you fully understand before proceeding....
OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)
By using these tools, you accept full responsibility for your actions. Your warranty is void should you run any of these utilities without OnePlus support present. I am not responsible for bricks, fires, nuclear war, etc. If you modified any...
forum.xda-developers.com
Click to expand...
Click to collapse
Will do thank you

I have a funny feeling mine is hard bricked, if the phones stays in fastboot whatever option you choose does this mean it is hard bricked guys?
Is there any linux compatible MSM program? I presume not? I tried with windows VM but with USB connected to vm it displays Android within Device manager. I installed the drivers. not looking good
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
no devices listed in MSM tool

dazuk9269 said:
I have a funny feeling mine is hard bricked, if the phones stays in fastboot whatever option you choose does this mean it is hard bricked guys?
Is there any linux compatible MSM program? I presume not? I tried with windows VM but with USB connected to vm it displays Android within Device manager. I installed the drivers. not looking good
View attachment 5892625
no devices listed in MSM tool
View attachment 5892627
Click to expand...
Click to collapse
It is not hard bricked, just need to borrow a windows PC. I don't know anything about Linux PC!

Make sure drivers are installed correctly.

Windows is only recognising it as a Android device & MSM still not displaying any device, also I followed a fastboot method at https://droidwin.com/unbrick-oneplus-9-pro-fastboot-commands/ due to MSM not displaying but it only got so far before the below error when trying to perform a fastboot reboot in fastbootd mode.
Any pro willing to help me please I would pay you for your time. But maybe its a gonna lol

Which specific driver did you install?

I recommend to use the FW-flasher from the crDroid Thread
crDroid Android - Browse /lemonadep/9.x/firmware at SourceForge.net
Highly customizable Android Platform
sourceforge.net
Also read the instruction in crDroid 9.4 for flashing.
I had the same issue but the FW-flasher fixed it for me. Good luck

AndyC76 said:
Which specific driver did you install?
Click to expand...
Click to collapse
For the fastboot method Android Bootloader Interface Drivers.
Also later installed the QUALCOMM drivers as instructed >> https://community.oneplus.com/thread/1541327
but still not recognised in my vm, QUALCOMM is COM port right?, I may have to wipe my linux pc & install windows lol

dazuk9269 said:
I have a funny feeling mine is hard bricked, if the phones stays in fastboot whatever option you choose does this mean it is hard bricked guys?
Is there any linux compatible MSM program? I presume not? I tried with windows VM but with USB connected to vm it displays Android within Device manager. I installed the drivers. not looking good
View attachment 5892625
no devices listed in MSM tool
View attachment 5892627
Click to expand...
Click to collapse
For flashing with msm tool you have to boot the phone in edl mode (power off the phone and than press and hold pressed voll down and voll up and put in the usb cable your phone boot to edl mode (( black screen )) and than you should see it on msm tool

ChrisFeiveel84 said:
For flashing with msm tool you have to boot the phone in edl mode (power off the phone and than press and hold pressed voll down and voll up and put in the usb cable your phone boot to edl mode (( black screen )) and than you should see it on msm tool
Click to expand...
Click to collapse
Unfortunately doesn't do anything mate pressing volume usd not connected, once connect usd goes straight to fastboot

dazuk9269 said:
Unfortunately doesn't do anything mate pressing volume usd not connected, once connect usd goes straight to fastboot
Click to expand...
Click to collapse
Vol up and vol down ?

yes
ChrisFeiveel84 said:
Vol up and vol down ?
Click to expand...
Click to collapse
Yes sir

When your phnoe is powered off and you press both and put in the usb your phone should boot to edl not to fastboot

ChrisFeiveel84 said:
When your phnoe is powered off and you press both and put in the usb your phone should boot to edl not to fastboot
Click to expand...
Click to collapse
Ok must be totally screwed then lol, when you say press both you mean continuously right or just once?