Can't OEM Unlock, can't fastboot flashing unlock, can't boot to recovery, can't fastboot flash boot boot.img, can't fastboot flash recovery recovery.img (like twrp) due to bootloader locked
Is there any way to flash this thing and make it work? Otherwise I'm just gonna throw it on ebay dumb cheap
KaptinBoxxi said:
Can't OEM Unlock, can't fastboot flashing unlock, can't boot to recovery, can't fastboot flash boot boot.img, can't fastboot flash recovery recovery.img (like twrp) due to bootloader locked
Is there any way to flash this thing and make it work? Otherwise I'm just gonna throw it on ebay dumb cheap
Click to expand...
Click to collapse
Enable dev options(settings>about phone>build number>tap it 7 times).
Go into settings>system>advanced>dev options>oem unlocking, click the toggle.
While still in dev options scroll down a little and enable usb debugging.
Plug your phone into your pc.
if/when the phone asks you to trust the computer make sure to check the "always allow this computer" check box.
Open up command prompt type into the cmd window
adb reboot bootloader
The phone will reboot into fastboot mode.
Now type into the cmd window
fastboot devices
See if it lists a device, if not you need to install the drivers I linked to. If you had to install the drivers try the fastboot devices command again after installing them, it should list the device now.
type in
fastboot flashing unlock
You will then have to use the phone to select yes to the unlock. you use the volume keys to select and the power button to confirm.
mulperi said:
Enable dev options(settings>about phone>build number>tap it 7 times).
Go into settings>system>advanced>dev options>oem unlocking, click the toggle.
While still in dev options scroll down a little and enable usb debugging.
Plug your phone into your pc.
if/when the phone asks you to trust the computer make sure to check the "always allow this computer" check box.
Open up command prompt type into the cmd window
adb reboot bootloader
The phone will reboot into fastboot mode.
Now type into the cmd window
fastboot devices
See if it lists a device, if not you need to install the drivers I linked to. If you had to install the drivers try the fastboot devices command again after installing them, it should list the device now.
type in
fastboot flashing unlock
You will then have to use the phone to select yes to the unlock. you use the volume keys to select and the power button to confirm.
Click to expand...
Click to collapse
You didn't read my post title or post at all... There's no OS on the device. Its not possible to get into the system to enable OEM unlock. Can't fastboot flashing unlock, doesn't work, can't send via OTA ADB Sideload as it fails around 10%.
Everything you stated above, I tried
Related
Tried various possible solutions and still can't get past the Google logo. Installed adb and Samsung driver but when executing commands such as "abd remount" or "adb push file.zip \sdcard\" in cmd I get an error saying "device not found".
Does anyone know how I could resolve this issue?
I tried clearing the cache and wiping the data from the phone, and even heating the phone with a hair dryer. I'd very much appreciate any help.
looks like you still be able to get in reovery ? if so , then nothing you should worry , just flash a new ROM
Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!
nodstuff said:
Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!
Click to expand...
Click to collapse
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.
leeroy88 said:
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.
Click to expand...
Click to collapse
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...
leeroy88 said:
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...
Click to expand...
Click to collapse
Hmmm try going to cmd prompt and typing in adb devices, if you get nothing then your adb isn't set up properly and you need to go into setting and change the path on your computer.
I know the details are sketchy but gimme a min and I will find you a link
---------- Post added at 03:05 AM ---------- Previous post was at 03:00 AM ----------
http://forum.xda-developers.com/showthread.php?t=1161776
Find the Android sdk folder in your computer, move it to the root of C.
I don't think adb is where this guide says it is, there is a read me in the folder where it was saying it has moved to the platform tools folder.
So anyway find the path to the file and put it where the guide says and you should be on the ball.
Forget adb. You need to use fastboot.
Open a command prompt in the directory with fastboot or cd into it.
Put phone in fastboot mode.
On the command prompt type fastboot devices.
You will see your serial number. If you don't recheck and make sure you did everything. Sdk PDA drivers if need be etc.
Fastboot flash recovery custom recovery img name.img
Boot into recovery
Mounts and storage.
Mount SD card
Put a rom for you device on there.
Unmount
Wipe everything but sdcard from recovery.
Flash the rom by going to install zip from SD card......
Okay still stuck trying to connect to my phone. I haven't been able to get my serial number show when typing fastboot devices in cmd. adb is set up and seems to be working but the list of devices is blank when I type in adb devices. The phone was put into fastboot mode both times. I get <waiting for device> when I try
fastboot flash recovery clockwork-5.0.2-crespo.img
I think the bootloader may be locked as it does say LOCKED under lock state, which is probably the reason why I can't get the recovery image to work. I couldn't install PDANet as it wanted to connect to my phone while in debugging mode at the end of the installation. Would it be possible that fastboot oem unlock won't work with without having PDANet installed? I'd really appreciate any further help on this topic.
You need the drivers.
albundy2010 said:
You need the drivers.
Click to expand...
Click to collapse
I have the Google USB driver package installed from SDK Manager. I had tried to install some other Samsung driver found on another post but it wouldn't install.
Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?
leeroy88 said:
Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?
Click to expand...
Click to collapse
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782
ismailham said:
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782
Click to expand...
Click to collapse
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.
leeroy88 said:
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.
Click to expand...
Click to collapse
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?
nodstuff said:
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?
Click to expand...
Click to collapse
After typing fastboot oem unlock I get three dots ...
Pretty much straight away it fails and says something about "too many links".
Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?
kvaju said:
Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?
Click to expand...
Click to collapse
Thanks for your reply, I followed the steps just now and got the exact same error. Before I was trying fastboot oem unlock while in platform-tools but this time I had downloaded the nexussrootICS.zip file, and extracted it to the root of C. I tried fastboot devices and my serial shows up and after fastboot oem unlock I get "status read failed: too many links."
The only difference I seem to have is that in my device manager I have Android Device > ADB Interface, as opposed to SAMSUNG Android Device > ADB Interface.
Not a big difference but that's all I can think of.
the same issue for me. is there any working solution for that?
I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147
GnubbyaBush said:
I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147
Click to expand...
Click to collapse
Thanks! I'll try to do this fancy dancing
I just managed to unlock the bootload trough this:
1. Make sure your computer has working fastboot and adb.
2. Enable USB debugging on the device.
3. Enable OEM unlock in the Developer options settings on the device. (Note: Not all devices have this setting, so continue with next step if yours does not.)
4. Connect the device to the computer through USB.
5. From a terminal on a computer, type the following to boot the device into fastboot mode:
adb reboot bootloader
Click to expand...
Click to collapse
6. Once the device is in fastboot mode, verify your PC sees the device by typing:
fastboot devices
Click to expand...
Click to collapse
If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine. See fastboot documentation for more info.
If you see "no permissions fastboot", try running fastboot as root.
7. From the same terminal, type the following command to unlock the bootloader:
fastboot oem unlock
Click to expand...
Click to collapse
8. On some devices, a disclaimer will display on the device that must be accepted. Use the volume keys to cycle through the options. Pressing the power button should confirm your selection. If no disclaimer appears, you can run
fastboot oem device-info
Click to expand...
Click to collapse
which will tell you if the device is unlocked
9. If the device doesn't automatically reboot, reboot it from the menu. It should now be unlocked.
10. Since the device resets completely, you will need to re-enable USB debugging on the device to continue.
source wiki.cyanogenmod.org
I tried every one-click root method but no success.... could you help me???
I wrote this earlier in the Bounty page for the bootloader unlock, but just so other people can see this as well, here is it in post form! This is the way to unlock bootloader on G3 so if anyone is on lollipop and is rooted, could they try it?
-- STEP 1: Remove LG Download mode (laf)
Important! You’ll need root access to remove (laf), so make sure you’ve rooted before proceeding with the steps below:
Download ADB files:
Prepare your phone:
Enable developer options: Go to your phone’s Settings » select About phone » Scroll to the bottom and tap on “Build number” seven times to enable developer options
Enable USB Debugging: Open phone’s Settings » select Developer options » Tick the “USB debugging” checkbox (under Debugging section)
Connect your phone to PC with a USB cable and if/when a pop-up screen shows up on Phone asking you to ‘Allow USB debugging?‘ for the computer, make sure you tick the checkbox and tap OK
Now type/paste the following ADB commands to backup LG Download Mode (laf), so you can restore it later when necessary
Code:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/sdcard/laf.img
Now run the following command to remove laf and reboot your phone
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
exit
adb reboot
Your phone will now reboot
Now to go into fastboot
adb reboot bootloader
Unlock bootloader!
fastboot oem unlock
or
fastboot flashing unlock
I took this info from original source listed below and made a few changes..
http://forum.xda-developers.com/tmobile-lg-g3/general/how-to-boot-lg-g3-fastboot-mode-t3087445
Good..but there is no fastboot in g flex 2.. Even if there was no fastboot commands would work..
So thats that
adds08 said:
Good..but there is no fastboot in g flex 2.. Even if there was no fastboot commands would work..
So thats that
Click to expand...
Click to collapse
My point is that the G3 also can't go into fastboot until you do this. So I just want people to see if it'll work, cause I'm on Linux and marshmallow so I can't test it. I think the G Flex 2 is more similar to the G3 than the G4 so that's why I'm asking for people to try it out
People already managed to enter fastboot, but no fastboot commands works.
I m going to try it but I need the commands to reflash download mode.
And then how do I know I succeeded?
I mean,with bootloader unlock,is there any way to flash a custom recovery to see if it works?
Pungasul said:
I m going to try it but I need the commands to reflash download mode.
And then how do I know I succeeded?
I mean,with bootloader unlock,is there any way to flash a custom recovery to see if it works?
Click to expand...
Click to collapse
Checking Bootloader Unlock : fastboot oem device-info
reflashing download mode : dd if=/sdcard/laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf
Aboot fastboot commands are all disabled.. For g3 wasnt it bump tht unlocked the bootloader?
Bt i have already tried nuking the laf and using fastboot commands many months ago..
adds08 said:
Aboot fastboot commands are all disabled.. For g3 wasnt it bump tht unlocked the bootloader?
Bt i have already tried nuking the laf and using fastboot commands many months ago..
Click to expand...
Click to collapse
Just out of curiosity, but what commands did you use?
adds08 said:
Aboot fastboot commands are all disabled.. For g3 wasnt it bump tht unlocked the bootloader?
Bt i have already tried nuking the laf and using fastboot commands many months ago..
Click to expand...
Click to collapse
Because the Nexus 6P is known for saying unknown command if you type fastboot oem unlock instead of fastboot flashing unlock
Try it... But dont forget to backup laf in case of failure .. I have done every possible commands new or old
Hi,
I tried this and erased the LAF. Then when you hold "Vol+" and plug-in USB cable you will see "[310] Fastboot mode started".
In Windows device manager I got "Marshall London Bootloader Interface" ... can't remember that I installed any driver but this is the LG G Flex 2.
Unfortunately it seams that there are no fastboot commads are working. I tried this with Android 5.0.1 because this was the only version I got rooted.
So this looks good to me but also it seams an dead end at the moment.
Best regards
CryptMan said:
Hi,
I tried this and erased the LAF. Then when you hold "Vol+" and plug-in USB cable you will see "[310] Fastboot mode started".
In Windows device manager I got "Marshall London Bootloader Interface" ... can't remember that I installed any driver but this is the LG G Flex 2.
Unfortunately it seams that there are no fastboot commads are working. I tried this with Android 5.0.1 because this was the only version I got rooted.
So this looks good to me but also it seams an dead end at the moment.
Best regards
Click to expand...
Click to collapse
i have a 950 that died on me some months ago and now i get Fastboot mode started but no commands work .
maybe if i put the LAF back on it it will boot ?
caesar170988 said:
maybe if i put the LAF back on it it will boot ?
Click to expand...
Click to collapse
I don't think so.
But with LAF back and started you should be able to use "LG UP" to flash a new firmware.
I can't tell you how you will be able to do that if it is not booting.
*Unlocking bootloader will remove all your data!*
I'm using Windows 7, and that's the steps i did. (it should be simmilar for other systems too)
Getting code:
Code will look simmilar to this: DB1ED223C5537BA756FB0671E425D650
Method 1 (no root):
Go to
https://passwordsgenerator.net/md5-hash-generator/ copy paste serial number and click generate. Then you should see code in "MD5 Hash of your string". You can also go to simmilar md5 hash generator sites, but this site automatically converts small letters to big letters.
Method 2 (root):
Okay, this is new method that is much easier and you don't need to send IMEI and wait for @the_laser to give you code. Go to terminal emulator, type su and execute it. Then type this and execute it:
redweaver said:
Actually the command is
echo -n NE1GAM4770133666 |md5sum |tr [:lower:] [:upper:]
If you don't use the -n flag, the newline character is also passed and you get a different result
Click to expand...
Click to collapse
Unlocking bootloader:
Download platform-tools which activates adb and fastboot commands (first you need Nokia 3 driver installed if you didn't)
Nokia 3 driver: http://www.devfiles.co/download/3iK0k7Sv/Nokia_3_USB_Drivers.zip
platform-tools Windows: http://www.devfiles.co/download/KtLsN6fX/platform-tools-latest-windows.zip
platform-tools Mac: http://www.devfiles.co/download/OkrfluP0/platform-tools-latest-darwin.zip
platform-tools Linux: http://www.devfiles.co/download/vk5DudZX/platform-tools-latest-linux.zip
Enable usb debugging in Developer options before running adb. To get Developer options, go to settings, about phone and press build number 7 times. Also enable OEM unlock.
Now Connect phone to computer via usb and enable usb file transfer, run cmd as administrator, then type this command which runs adb:
chdir C:/Users/John/Desktop/platform-tools (this is just a example, you need to type your own location of platform-tools)
then type this command to check is your device connected to adb, it will show serial number of your device, if it hangs at waiting device, then you need to reinstall drivers (if you're doing this first time, then it will ask to allow usb debugging on your computer, just tick always allow from this computer and click OK)
adb devices
then type this command to reboot to recovery (you can boot to recovery by holding power on + volume up (only with usb connected) if this command doesn't works)
adb reboot recovery
when booted to recovery, choose reboot to bootloader option with volume sliders (this will boot to fastboot)
when booted to fastboot, it will show text 'FASTBOOT MODE' in down-left corner
now type this command to check is your device connected properly to fastboot.
fastboot devices
if it show characters like 0123456789ABCDEF or simmilar then it is connected properly, if it hangs on waiting device, then you need to reinstall drivers like mentioned above.
Android Nougat (7.0 & 7.1.1):
Now type these commands to unlock bootloader
fastboot.exe -i 0x2e04 oem key (type your key after oem key)
fastboot.exe -i 0x2e04 oem unlock
then press volume up, when asked
Android Oreo (8.0 & 8.1):
First download NE1-0-215H.lk.bin:
https://my.pcloud.com/publink/show?code=XZaLMs7ZclQ2wvKwSb0ofUraMmrsiHh6uk1X
Now type these commands to unlock bootloader
fastboot oem dm-verity <your_unlock_key>
fastboot flash lk NE1-0-215H.lk.bin
fastboot reboot-bootloader
Proceed your unlock procedure.
If you have problem on flashing the lk partition, you can use MTK Smart Phone Flash Tool to flash lk partition manually.
After lk partition flashed, you may encounter "Red State" when booting the phone. Ignore that and boot your phone to Fastboot mode directly with OST LA.
That is it, i tried to explain for you to understand everything i did to unlock bootloader.
Credits:
@the_laser for codes, some additional steps and corrections. Also thanks for new method. @redweaver for new method.
@Hikari_kalyx for Android Oreo method. @bigrammy for NE1-0-215H.lk.bin link.
way to enter recovery without adb -
power off phone
press and hold volume up + power on buttons, insert cable immediately
countdown will start on phone, hold both keys until countdown ends, then IMMEDIATELY release power on key, still holding volume up
you will enter recovery shortly
after installing TWRP it is very important - DO NOT allow /system modification until supersu package installation ! ( or you will require reflashing phone with OST )
another note - can't enter recovery by combination volume-up + power button, if phone not connected to computer
one man reported, that even he successfully flashed TWRP image with "fastboot flash recovery <twrp image>", he still got original recovery.
workaround is to use "fastboot boot <twrp image>" - as we need to have USB cable connected to enter TWRP recovery anyway, not big problem.
the_laser said:
way to enter recovery without adb -
power off phone
press and hold volume up + power on buttons, insert cable immediately
countdown will start on phone, hold both keys until countdown ends, then IMMEDIATELY release power on key, still holding volume up
you will enter recovery shortly
after installing TWRP it is very important - DO NOT allow /system modification until supersu package installation ! ( or you will require reflashing phone with OST )
another note - can't enter recovery by combination volume-up + power button, if phone not connected to computer
one man reported, that even he successfully flashed TWRP image with "fastboot flash recovery <twrp image>", he still got original recovery.
workaround is to use "fastboot boot <twrp image>" - as we need to have USB cable connected to enter TWRP recovery anyway, not big problem.
Click to expand...
Click to collapse
Someone told me that if you flashed twrp, that it automatically removes data encryption. Is that true?
EDIT: i find out that is not true, it asks for some password to decrypt data, but the problem is that idk what is the password
DON'T install xposed! It bootlops.
EDIT: My fault, it actually work but you need to wait more than usual to boot.
That is great guys.
Do we have a working recovery yet?
nafnist said:
That is great guys.
Do we have a working recovery yet?
Click to expand...
Click to collapse
I use this twrp https://1drv.ms/u/s!AsmTb5aqoY12mDZqDZbPOp47QVMV
I have stock recovery, but I use fastboot command 'fastboot boot recoveryname.img' when I need TWRP, and that's awesome because I don't lose stock recovery which is useful to flash OTAs and Nokia zips. I flashed SuperSu 2.79 just fine, but expect some crashes like software update, device monitor crash, but actually everything works, software update works just fine.
SkaboXD said:
Someone told me that if you flashed twrp, that it automatically removes data encryption. Is that true?
EDIT: i find out that is not true, it asks for some password to decrypt data, but the problem is that idk what is the password
Click to expand...
Click to collapse
TWRP can't handle Android 7.x default disk encryption, just press "cancel" and we need to use sdcard as storage for backups and packages because of this
Can I return the bootstrapper lock?
Where are you getting the codes from @the_laser?
abetterlie said:
Where are you getting the codes from @the_laser?
Click to expand...
Click to collapse
Yes
shokohiw said:
Yes
Click to expand...
Click to collapse
you mean to get bootloader locked again?
yes you can just instead of oem unlock type oem lock
I mean where are you getting the OEM unlock keys from?
SkaboXD said:
you mean to get bootloader locked again?
yes you can just instead of oem unlock type oem lock
Click to expand...
Click to collapse
abetterlie said:
I mean where are you getting the OEM unlock keys from?
Click to expand...
Click to collapse
idk, ask @the_laser
the bootloader I unlocked how to install root and twrp
shokohiw said:
the bootloader I unlocked how to install root and twrp
Click to expand...
Click to collapse
link for twrp
https://1drv.ms/u/s!AsmTb5aqoY12mDZqDZbPOp47QVMV
when downloaded, copy twrp to folder platform-tools and rename it to recovery.img
reboot to fastboot, then type this command:
fastboot flash recovery recovery.img
then reboot, fastboot reboot
if it didn't worked, use this command just to boot to twrp (you need to do this everytime when you are connected to PC)
fastboot boot recovery.img
To install root, first disable system modification on twrp then flash this zip for root.
This is not the latest version of SuperSU, but newest releases have some problems and crashes. (at least for me). This is last version that works for me.
That is it.
Thank you!
Is it possible after unlocking, installing twrp and root, to return the device to factory settings for ota updates? If so, how?
shokohiw said:
Is it possible after unlocking, installing twrp and root, to return the device to factory settings for ota updates? If so, how?
Click to expand...
Click to collapse
on twrp, there is a option wipe, click on it, then you will see option swipe to factory reset. then wait and reboot.
And you can now enable system modification if you want (it is recommended to enable it because some zips fails to flash because this option is disabled)
After installing TWRP and rebooting, does not want to boot Android, weighs in on the initial splash screen what to do
Your device has failed verification and may not work properly
shokohiw said:
After installing TWRP and rebooting, does not want to boot Android, weighs in on the initial splash screen what to do
Your device has failed verification and may not work properly
Click to expand...
Click to collapse
Weird, when it says your device has failed verification?
For me reboot works fine
I want to root my phone, install custom recovery and eventually a custom ROM. For this, I need to unlock the bootloader.
I have an Oppo A5 2020 CPH1931. It should go into bootloader when I press volume+ and power buttons together for 5 seconds after completely turning off the phone. But when I do this, it boots like normal. Tried all different combinations and durations. I am able to boot into recovery but not fastboot mode. I have turned on the "OEM unlocking" option in developer options.
I tried it through ADB, it says fastboot on the screen for half a second and then once again jumps back to normal booting. I also tried to already put the fastboot command "fastboot oem unlock". When it says <waiting for device> I use another terminal to try to boot into fastboot with ADB. But this does not work (also tried this with "fastboot flashing unlock").
By the way, my devices only shows up with adb devices when I select transfer files upon connecting the USB cable. When I select just charge it doesn't even show.
On computer install the suitable OPPO Android USB Driver
Download Oppo USB Driver for Windows (Latest Driver)
Download the Latest Oppo USB Driver to connect Oppo Smartphone and Tablets to the Windows Computer without PC Suite Application.
androidmtk.com
Anteino said:
I want to root my phone, install custom recovery and eventually a custom ROM. For this, I need to unlock the bootloader.
I have an Oppo A5 2020 CPH1931. It should go into bootloader when I press volume+ and power buttons together for 5 seconds after completely turning off the phone. But when I do this, it boots like normal. Tried all different combinations and durations. I am able to boot into recovery but not fastboot mode. I have turned on the "OEM unlocking" option in developer options.
I tried it through ADB, it says fastboot on the screen for half a second and then once again jumps back to normal booting. I also tried to already put the fastboot command "fastboot oem unlock". When it says <waiting for device> I use another terminal to try to boot into fastboot with ADB. But this does not work (also tried this with "fastboot flashing unlock").
By the way, my devices only shows up with adb devices when I select transfer files upon connecting the USB cable. When I select just charge it doesn't even show.
Click to expand...
Click to collapse
Having same problem bro
Anteino said:
I want to root my phone, install custom recovery and eventually a custom ROM. For this, I need to unlock the bootloader.
I have an Oppo A5 2020 CPH1931. It should go into bootloader when I press volume+ and power buttons together for 5 seconds after completely turning off the phone. But when I do this, it boots like normal. Tried all different combinations and durations. I am able to boot into recovery but not fastboot mode. I have turned on the "OEM unlocking" option in developer options.
I tried it through ADB, it says fastboot on the screen for half a second and then once again jumps back to normal booting. I also tried to already put the fastboot command "fastboot oem unlock". When it says <waiting for device> I use another terminal to try to boot into fastboot with ADB. But this does not work (also tried this with "fastboot flashing unlock").
By the way, my devices only shows up with adb devices when I select transfer files upon connecting the USB cable. When I select just charge it doesn't even show.
Click to expand...
Click to collapse
I have same issue. How did u fix it
News?oppo a5 2020 cph1931 ii have this model