I tried to by this instruction https://forum.xda-developers.com/t/bootloader-unlock-realme-gt-neo-2-rmx3370-all-variants.4391679/ But I don't have "Apply" as in paragraph 4) but there is as in the picture. What does this mean and how to unlock the bootloader in this case?
it says that you already joined in depth-test programm. So just boot your device into the fastboot mode and connect it to the pc. Then open up the "adb programm" whit the cmd/terminal and type: "fastboot flashing unlock". Them your device will reboot and show warning and use the volume button to select "Yes Unlock Bootloader"
Topo's said:
it says that you already joined in depth-test programm. So just boot your device into the fastboot mode and connect it to the pc. Then open up the "adb programm" whit the cmd/terminal and type: "fastboot flashing unlock". Them your device will reboot and show warning and use the volume button to select "Yes Unlock Bootloader"
Click to expand...
Click to collapse
If it looks like this, is the bootloader unlocked? I did not do anything with the phone, it is like that from the box.
yes it is unlocked!
Topo's said:
yes it is unlocked!
Click to expand...
Click to collapse
thanks for the help
make sure to leave a like for the support it will help me!
Related
i'm in the process of re-locking my bootloader in order to send it to Samsung for repair (home button not working). when i run the command line "fastboot oem lock", it just keeps hanging at "waiting on device" and nothing happens. i have the correct drivers installed. when i run "adb devices", it shows up the device. however, when i run "fastboot devices", it does not show up anything. any help on relocking my bootloader would be appreciated. Thanks!
Probably shouldn't be answering this here buuuuut...
adb reboot bootloader
and THEN
fastboot oem lock.
See what happens. You have to be in boot loader mode. Please move your questions to the Q&A section sir.
i did enter that command in order to get into fastboot. after that , i ran the command "fastboot oem lock" but it gets stuck at "waiting on device"
Update your drivers
Yea at this point I'd say its a connectivity problem. Drivers and or cable, but since you are getting adb devices to recognize, its not your cable. You should really use ubuntu, you would save yourself a lot of time, because you don't really have to deal with drivers like windows.
'sudo fastboot oem lock'
You need to be super user.
sure you went into bootloader and not recovery? because adb is seen in recovery and doesnt work in bootloader!
Hi!
I unlocked my phone - but when i type in the command "adb reboot bootloader"
it goes in to fastboot for a second, and then I get "bootloader unlocked" warning and after that it boots in to android.
How can I stop at fastboot to flash a custom recovery ?
Cheers!
EDIT:
NVM fixed
I am sure it was the right way.
How did you get it fixed?
I turned it off completely and after that, it accepted the command and stayed in fastboot.
Good to know, thanks for the information.
Bought this device and everything works great and I have root. When I try to unlock the boot loader by going to "Developer Options" and checking the "Oem Unlock", I then
Code:
adb reboot-bootloader
At this point I do a
Code:
fastboot oem unlock
Which then the device asks me to use the volume buttons to confirm, Volume up for yes and volume down for no. The problem I'm running into is in fastboot mode it seems my volume up and power key are completely ignored. They work in recovery and in android but not in the boot loader itself.
I have tried unplugging the phone after sending the command over to see if that is a factor but it doesn't seem so. I'm only allowed to use volume down which denies unlocking the boot loader.
Another thing if anybody can get me a scatter file that would be much appreciated.
Bump
Studio One Plus S0130uu
frodoswaggins said:
Bought this device and everything works great and I have root. When I try to unlock the boot loader by going to "Developer Options" and checking the "Oem Unlock", I then
Code:
adb reboot-bootloader
At this point I do a
Code:
fastboot oem unlock
Which then the device asks me to use the volume buttons to confirm, Volume up for yes and volume down for no. The problem I'm running into is in fastboot mode it seems my volume up and power key are completely ignored. They work in recovery and in android but not in the boot loader itself.
I have tried unplugging the phone after sending the command over to see if that is a factor but it doesn't seem so. I'm only allowed to use volume down which denies unlocking the boot loader.
Another thing if anybody can get me a scatter file that would be much appreciated.
Click to expand...
Click to collapse
How did you root the phone?
Hoping for an answer to the bootloader question as well. For root I'm going to attempt kingoroot and replace with supersu
First I am sorry for long post because of details and my poor English.
I have a L Bello D335 running on stock Rom(updated to Lollipop via OTA) and it is unrooted.
Yesterday I tried to unlock bootloader, I typed command [fastboot oem unlock] in Fastboot mode, and my phone went to Bootloader Unlock Screen. It said to press Vol+ button to confirm unlocking bootloader or press Vol- button to cancel. I picked up the phone and press Vol+, but USB cable connection was disconnected accidently because of loose micro USB plug:crying: (that is what I've noticed after 5 minutes, it was disconnected and reconnected on moving the phone). Then phone screen stayed in Bootloader Unlock Screen and it didn't responded to pressing keys.
On computer cmd windows, after [fastboot oem unlock] it said:
FAILED (Status read failed (Too many links))
fastboot: error: Command failed
Click to expand...
Click to collapse
Then I typed command [fastboot reboot]
and it said:
Rebooting FAILED (Device sent unknown status code: e)
fastboot: error: Command failed
Click to expand...
Click to collapse
Then I typed command [fastboot devices]
and it showed strange code like:
[email protected]???^?l?l fastboot
Click to expand...
Click to collapse
I didn't check [fastboot devices] before and I don't know how the result is.
Then I've noticed loose micro USB plug and thought bootloader unlock process was interrupted.
And I disconnected phone and boot up and the phone is working well and all app/data remain like before.
But now, if I type [fastboot devices] in Fastboot mode, it is showing a strange code instead of an alphanumeric code. It is a different code every time, like:
[email protected]???*?G?G fastboot
Click to expand...
Click to collapse
(or)
[email protected]???▼?╟?╟ fastboot
Click to expand...
Click to collapse
I tried different cable and ports but always the same.
And fastboot commands [fastboot reboot], [fastboot getvar unlocked], [fastboot getvar all] are working. Bootloader is still locked. ADB command [adb devices] returns alphanumeric code.
Is it something corrupted or because of locked bootloader?
If it is corrupted,
What are the possible damages? and
How to fix it?
Thanks in Advance
Reply
You could try unlocking the bootloader again, BUT first the cable needs to be held in place with some tape (on the phone around the left display corner and back to the cable) and THEN unlock the bootloader via PC.
Good luck! :good:
Please how to unlock bootloander and Root oneplus 8 in OS 11.0.8.8 ?
Thanks
To unlock bootloader download platform tools on you pc and boot into fastboot mode. Then connect your device to the pc and open cmd in your platform tools directory and run fastboot oem unlock. Then use volume buttons to navigate and power button to select.
Ps: All your data will be lost when you unlock bootloader. So backup all your data before you proceed.
Pranjalpc said:
To unlock bootloader download platform tools on you pc and boot into fastboot mode. Then connect your device to the pc and open cmd in your platform tools directory and run fastboot oem unlock. Then use volume buttons to navigate and power button to select.
Ps: All your data will be lost when you unlock bootloader. So backup all your data before you proceed.
Click to expand...
Click to collapse
You'll also need to enable "OEM unlocking" in the developer settings.
Canny1913 said:
You'll also need to enable "OEM unlocking" in the developer settings.
Click to expand...
Click to collapse
Yes, forgot to mention that. Thanks mate