Hi,
I am using my Nextbit Robin Oem Unlock from last 1 year but today i decided to go back to stock with locked Oem.
I flashed the stock rom and locked the Oem at the same time but when i restarted the phone it got stuck at the boot.
So I went ahead with the 'fastboot oem unlock' command, and here's the problem. All flashing command returns FAILED <remote: device is locked...>.
fastboot oem device-info reads: Device tampered: false, Device unlocked: false. So bootloader is locked. At this point I assume that the bootloader is unlocked, but revert back to locked after reboot (the phone automatically rebooted after executing oem unlock command, so can't get around that).
Tried numerous other methods, using different adb files, no dice. Can't even flash TWRP. Tried adb sideload, same. Tried executing fastboot oem unlock with various different parameter, still locked after reboot. I cannot flash anything into locked bootloader.
Google researched it for few hours, same problem happened to other phones from other manufacturers that came returned from warranty replacement with modified motherboard; OR tampered/broken eMMC/NAND flash. But no such case for Nextbit Robin (yet?).
Pretty hopeless right now since I just found out that Nextbit Robin support ended on Aug 1st.
Guess I'm stuck with locked bootloader and no cell signal phone. Unless someone can help. One can always hope.
Anyway, thanks for reading.
Mukul_Meena said:
Admin Note: This is a special Q&A-formatted thread. Please follow this link to view it in your browser: http://xda.tv/post76659814
Click to expand...
Click to collapse
If you bootloader is unlocked I think you can give a try to the Nextbit's Unbrick Tool
As you want to go back to stock , I think this is a good idea.
Now if your bootloader isn't unlocked there is unfortunately nothing I can do for you , unless you unlock it .
Edit #1: If your bootloader is locked , go to bootloader mode by pressing volume down + power button for about 20 seconds and try to see the bootloader state with fastboot commands. If it is unlocked , follow the process in the @nextbitKhang's thread .
Yes that's the main issue. Oem is Locked.
Is there any Oem unlock code i can use to unlock from ADB?
I don't think so ,I'm not sure, but I hope you'll find one.
On your Robin go to settings > system > about phone > tap build number until it shows developer options.
Go into developer options which is in settings > system > developer options.
Make sure OEM unlocking is enabled. (for good measure disable then re-enable)
Also make sure usb debugging is enabled. Have the Robin plugged into a computer so you can enable to pop-up on Robin asking for access for the computer.
Once they are both enabled shut down your phone. Turn it back on while pressing vol down+power and plugged into your computer.
In adb run command fastboot oem unlock
please i'm experiencing the same issue not on nextbit but on GIonee.
i have re-activate both OEM unlocking and USB debugging several times but it all void
same error: Remote: OEM unlock is not allowed
please kindly help
Edit: Issue resolved
Hello everyone,
Pardon my lack of knowledge on rooting devices and all the related things. This is my first time attempting to root a device and I am having a lot of trouble understanding how to go about things. Through my research, I'm finding a lot of different ways to do things and I want a direct opinion on my process so I don't mess up my phone. (Through as much research as I could) My end goal is to have TWRP flashed to my phone, root my device and install a custom ROM. My understanding is that I first need to unlock the bootloader, flash TWRP, install SuperSU, then flash the custom ROM. I won this phone from a raffle and I'm trying to root from a Windows 10 laptop.
I have the TWRP and SuperSU files at the ready and have also installed Kingo root. I enabled USB debugging and allowed the bootloader to be unlocked in developer settings. I tried to boot into download and bootloader and successfully recognized my device, but when trying to use "fastboot flash recovery twrp-3.2.3-0-hima.img" it gave me the error message "FAILED (remote: cannot flash this partition in s-on state)" and "FAILED (remote: 9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKE)"
I'd assumed my phone was already unlocked but that's obviously not the case. Doing some more research I found a lot of people needed to get a bootloader unlock from HTCdev.
Is this what I need to do now to continue?
What about this "s-on state" how can I turn it off?
Will unlocking the bootloader wipe my device?
Could I just use the "root" button in the Kingo root main app?
Can anyone verify my theoretical steps and give quick notes on how I should be doing them properly?
Any help is greatly appreciated
dont worry i will help you
Download all in one Android toolkit for your PC...
https://www.google.com/url?sa=t&sou...FjAAegQIBRAB&usg=AOvVaw0sohDTlAE3UaLSgUihYhS3
and connect your phone to PC and allow USB debugging after that
go to Android all in one toolkit and select unlock bootloader....on the screen of your phone it would ask you if you want to unlock bootloader press volume up for yes
volume down for no
Select yes...but
Note:It would reset everything on your phone so back up your necessary files
Make sure you download the right twrp image for your phone (Google search)
Move the Twrp.img to your PC local directory folder and rename it to TWRP.img ....next step is to:-
next step is to go to windows command prompt on your PC and type the following commands:-
Adb devices
Adb reboot bootloader
Fastboot devices
Fastboot flash recovery TWRP.img
Note:make sure you reboot your phone to recovery before normal reboot so that it would replace your previous stock rom
Go to twrp and install the latest version of super su
https://download.chainfire.eu/696/supersu/
This steps worked for me it can work for almost all types of phone
my name is Iduh Winner
I was a root struggler like you...all thanks to God ....I love you all for more info contact me on the following social media
facebook:Iduh Winner
YouTube:Iduh Winner
hi devs
i flashed accidentially Chinese recovery rom on my whyred now i m unable to switch from Chinese to global version as i tried every method fastboot,recovery,qfil,mi flash and edl mode i mean every possible way but all in vain as every method ended with error and my fastboot command is locked.
so what can i do please suggest me
it's Chinese miui 11
guys please help me i m frustrated tried every available method on internet downloaded tons of file.
aliasgertaj said:
guys please help me i m frustrated tried every available method on internet downloaded tons of file.
Click to expand...
Click to collapse
What you are trying to do? Just switch from Chinese to Global? or your device is bricked now?
What did happen after that you flashed the Chinese recovery ROM?
What modes do you have available?
Did you unlock bootloader previously?
SubwayChamp said:
What you are trying to do? Just switch from Chinese to Global? or your device is bricked now?
What did happen after that you flashed the Chinese recovery ROM?
What modes do you have available?
Did you unlock bootloader previously?
Click to expand...
Click to collapse
i m not bricked as my device is working fine
but now no fastboot command working i m not able to flash custom recovery
i tried fastboot method , used miflash method every miflash from old to newest , qfil edl mode method with miflash and qualcomm flash tool
i m just able to switch between china stable n developer rom
if i m able to unlock ma fastboot command then i can flash atleast custom recovery .
kindly help me as all method ended up every time with diffrent error.
aliasgertaj said:
i m not bricked as my device is working fine
but now no fastboot command working i m not able to flash custom recovery
i tried fastboot method , used miflash method every miflash from old to newest , qfil edl mode method with miflash and qualcomm flash tool
i m just able to switch between china stable n developer rom
if i m able to unlock ma fastboot command then i can flash atleast custom recovery .
kindly help me as all method ended up every time with diffrent error.
Click to expand...
Click to collapse
Fastboot flashing commands won't work if you have bootloader locked.
Did you unlock bootloader previously and probably get locked again?
Did you enable all the proper options on Developer section, i.e. USB debugging and check if device is recogniced on adb commands?
What do you get with "fastboot getvar all"?
subwaychamp said:
fastboot flashing commands won't work if you have bootloader locked.
Did you unlock bootloader previously and probably get locked again?
Did you enable all the proper options on developer section, i.e. Usb debugging and check if device is recogniced on adb commands?
What do you get with "fastboot getvar all"?
Click to expand...
Click to collapse
thanks a lot dude i m on unlock boot loader .
But bootloader some time works means sometimes it shows my device name after available device command it shows only ???????? Fastboot devices
i tried all way possible but none of them worked.
And i m unable to switch from china to global.
Only i can do is switch between china stable to developer.
i tried getvar command but it gave me this
PS C:\adb> adb reboot bootloader
error: device '(null)' not found
PS C:\adb> fastboot getvar all
getvar:all FAILED (command write failed (Unknown error))
finished. total time: 5.007s
PS C:\adb>
aliasgertaj said:
i tried getvar command but it gave me this
PS C:\adb> adb reboot bootloader
error: device '(null)' not found
PS C:\adb> fastboot getvar all
getvar:all FAILED (command write failed (Unknown error))
finished. total time: 5.007s
PS C:\adb>
Click to expand...
Click to collapse
And you said you enabled USB debuging?!? you didn't. First enable it under development tools.
MAKE SURE YOUR USING RIGHT ADB/FASTBOOT TOOLS AND DRIVERS.
After 'adb reboot bootloader' use 'fastboot devices'. You can change usb cable and if you still get errors try using usb hub.
If all above fails than try it on WIN7 PC.
aliasgertaj said:
thanks a lot dude i m on unlock boot loader .
But bootloader some time works means sometimes it shows my device name after available device command it shows only ???????? Fastboot devices
i tried all way possible but none of them worked.
And i m unable to switch from china to global.
Only i can do is switch between china stable to developer.
Click to expand...
Click to collapse
aliasgertaj said:
i tried getvar command but it gave me this
PS C:\adb> adb reboot bootloader
error: device '(null)' not found
PS C:\adb> fastboot getvar all
getvar:all FAILED (command write failed (Unknown error))
finished. total time: 5.007s
PS C:\adb>
Click to expand...
Click to collapse
I think you are not properly booted to the proper state while you're trying certain commands. Just to be clear; adb works while your device is power on and fastboot commands will work only while your device is in fastboot mode not while on adb mode. A way to be sure that you are doing properly is enabling USB debugging first but while connected device with PC, a prompt will appear from device screen and then tap on "always allow", then you have to type "adb devices" and follow step by step, if device is recognized you can go to the next step with "adb reboot bootloader" then in fastboot you have to see the bunny otherwise is not properly in fastboot mode, then you can follow with "fastboot devices" and so on, keep in mind that any command will work until device is properly recognized.
SubwayChamp said:
I think you are not properly booted to the proper state while you're trying certain commands. Just to be clear; adb works while your device is power on and fastboot commands will work only while your device is in fastboot mode not while on adb mode. A way to be sure that you are doing properly is enabling USB debugging first but while connected device with PC, a prompt will appear from device screen and then tap on "always allow", then you have to type "adb devices" and follow step by step, if device is recognized you can go to the next step with "adb reboot bootloader" then in fastboot you have to see the bunny otherwise is not properly in fastboot mode, then you can follow with "fastboot devices" and so on, keep in mind that any command will work until device is properly recognized.
Click to expand...
Click to collapse
thanks bro
yesterday i used xiaomitool v2 as it reboot automatically device in fastboot mode but as i said after in fastboot mode it doesn't boot in adb mode.
and what is proper method to open fastboot mode i m doing it by holding power and volume down button.
drnightshadow said:
And you said you enabled USB debuging?!? you didn't. First enable it under development tools.
MAKE SURE YOUR USING RIGHT ADB/FASTBOOT TOOLS AND DRIVERS.
After 'adb reboot bootloader' use 'fastboot devices'. You can change usb cable and if you still get errors try using usb hub.
If all above fails than try it on WIN7 PC.
Click to expand...
Click to collapse
thanks for response bro
i did it under developer option and trusted my computer connection also and install adb fastboot devices many time changed cable and port but nothing happen. i tried fastboot files of china stable rom but it also doesn't worked
aliasgertaj said:
thanks bro
yesterday i used xiaomitool v2 as it reboot automatically device in fastboot mode but as i said after in fastboot mode it doesn't boot in adb mode.
and what is proper method to open fastboot mode i m doing it by holding power and volume down button.
Click to expand...
Click to collapse
Just trying to determine what your words exactly mean when you say "after in fastboot mode it doesn't boot in adb mode." ... without entering in more technical insights adb works when device is on, no sense to boot to fastboot to try to boot to adb after that (?)
If you can boot to fastboot what you have to try firstly is unlock bootloader or be sure that is already unlocked using
Code:
fastboot oem device-info
if your device is or get unlocked then you can try to flash or just boot to a custom recovery but if you can't determine until now if your device is really unlocked then you couldn't go further.
The hardware method to enter to fastboot is from a device off; pressing both pwr and vol down buttons but if the bunny is not displayed probably you didn't really get fastboot mode.
SubwayChamp said:
Just trying to determine what your words exactly mean when you say "after in fastboot mode it doesn't boot in adb mode." ... without entering in more technical insights adb works when device is on, no sense to boot to fastboot to try to boot to adb after that (?)
If you can boot to fastboot what you have to try firstly is unlock bootloader or be sure that is already unlocked using
Code:
fastboot oem device-info
if your device is or get unlocked then you can try to flash or just boot to a custom recovery but if you can't determine until now if your device is really unlocked then you couldn't go further.
The hardware method to enter to fastboot is from a device off; pressing both pwr and vol down buttons but if the bunny is not displayed probably you didn't really get fastboot mode.
Click to expand...
Click to collapse
i m frustrated now tried all the thing tried official flash tool official build but even official build by miflash official latest tool unable to flash image
i bought my device to official xiaomi service center they told it will be done in an hour but after couple of hour they returned my phone that it cant be updated.??????
shame on xiaomi that they implemented a method that they themselves also don't know how to revert it.
aliasgertaj said:
i bought my device to official xiaomi service center they told it will be done in an hour but after couple of hour they returned my phone that it cant be updated.??????
shame on xiaomi that they implemented a method that they themselves also don't know how to revert it.
Click to expand...
Click to collapse
Do yo use WIN10? Find PC with Win7... and install adb/fastboot app and drivers. Than try..
Is your system working now?
Just unlock your bootloader and install OrangeFox recovery than you can flash whatever you need.
Problem solved.
drnightshadow said:
Do yo use WIN10? Find PC with Win7... and install adb/fastboot app and drivers. Than try..
Is your system working now?
Just unlock your bootloader and install OrangeFox recovery than you can flash whatever you need.
Problem solved.
Click to expand...
Click to collapse
ok bro i will try today with another pc and update you
aliasgertaj said:
ok bro i will try today with another pc and update you
Click to expand...
Click to collapse
thanks installed twrp on other pc running on windows 7 but now internal storage goes 0mb unable to mount system
aliasgertaj said:
thanks installed twrp on other pc running on windows 7 but now internal storage goes 0mb unable to mount system
Click to expand...
Click to collapse
Wtf .. what's wrong with you.. you did everything we said wrong... Where and when did I told you to install TWRP????
I'm done with you...
Good luck with china ROM.
Ignorance is a bliss.
drnightshadow said:
Wtf .. what's wrong with you.. you did everything we said wrong... Where and when did I told you to install TWRP????
I'm done with you...
Good luck with china ROM.
Ignorance is a bliss.
Click to expand...
Click to collapse
thanks dude i installed twrp wipe my internal storage there is some error then some tricks goes perfect as i supposed and woohaa i installed masik port edition and now my phone works fine.
aliasgertaj said:
thanks dude i installed twrp wipe my internal storage there is some error then some tricks goes perfect as i supposed and woohaa i installed masik port edition and now my phone works fine.
Click to expand...
Click to collapse
TWRP can't bypass encryption, when you have no access to read data (0mb) then you have to format it, to avoid that is always recommended use OrangeFox, just for future reference, if you understand that you can flash OrangeFox through TWRP for better experience.
Also you can use this tool to help you to automate some stuff https://github.com/Szaki/XiaomiADBFastbootTools
I've been trying to unlock a Blu G5 - I've gotten as far as patching the disk image and all that is left to do is just flash the image onto the phone.
The issue is whenever I try to flash something onto the phone I get the following error :
Code:
FAILED (remote: Flashing Lock Flag is locked. Please unlock it first!)
.
When I go to unlock through Flashing unlock I get the error in the title - OEM unlock gives me cmd not found.
I have USB debugging and OEM unlocking both enabled inside the app settings. I'm not sure if its pertinent but on Magisk I see "Ramdisk : No". I've also been unable to get into recovery mode despite trying every combination possible except for once on accident (which I haven't been able to replicate).
Any help would be appreciated, Thanks!
yodamaul said:
I've been trying to unlock a Blu G5 - I've gotten as far as patching the disk image and all that is left to do is just flash the image onto the phone.
The issue is whenever I try to flash something onto the phone I get the following error :
Code:
FAILED (remote: Flashing Lock Flag is locked. Please unlock it first!)
.
When I go to unlock through Flashing unlock I get the error in the title - OEM unlock gives me cmd not found.
I have USB debugging and OEM unlocking both enabled inside the app settings. I'm not sure if its pertinent but on Magisk I see "Ramdisk : No". I've also been unable to get into recovery mode despite trying every combination possible except for once on accident (which I haven't been able to replicate).
Any help would be appreciated, Thanks!
Click to expand...
Click to collapse
having the same problem right now. did you get a fix?
I am trying to unlock the bootloader of the Poco F3 in order to root it.
I installed the platform tools present in the apt repositories (OS: Pop!_OS 20.10), this is the version I installed:
Bash:
$ fastboot --version
fastboot version 1:8.1.0+r23-8
Installed as /usr/lib/android-sdk/platform-tools/fastboot
Then I did this:
enabled developer options, USB debugging and OEM unlock in the device's settings
turned it off and then on again in fastboot mode (holding power and volume down buttons)
connected it to my PC through USB and then ran the following commands but when I run fastboot flashing unlock I get an unknown command error
Bash:
$ fastboot devices
████████ fastboot
$ fastboot flashing unlock
...
FAILED (remote: unknown command)
finished. total time: 0.000s
Am I missing something here?
I read somewhere that I should install device specific drivers but I couldn't find any for Linux, what do I have to do?
You need to use mitools to unlock the bootloader. Search some videos of how to do it. You will need to wait 168 hours after finish the steps.
Is that actually the only way? According to this guide mi tools isn't required. I read that it only acts as a wrapper of fastboot so if I can I'd rather use fastboot directly and avoid setting up an account just for that.
QuazarOmega said:
Is that actually the only way? According to this guide mi tools isn't required. I read that it only acts as a wrapper of fastboot so if I can I'd rather use fastboot directly and avoid setting up an account just for that.
Click to expand...
Click to collapse
One Way : Mi Unlock Tool
No other way than Mi unlock tool......yet
Oh alright, Mi unlock tool it is then, thanks for the quick help!
It's purely so Xiaomi can limit people to unlock bootloader so that you don't get companies bulk buying devices falshing custom firmware and selling them as other phones for more
QuazarOmega said:
Is that actually the only way? According to this guide mi tools isn't required. I read that it only acts as a wrapper of fastboot so if I can I'd rather use fastboot directly and avoid setting up an account just for that.
Click to expand...
Click to collapse
that guide is wrong flashing unlock would work if the bootloader didnt need a special img file as part of the unlocking process.
the miunlock tool simply does the downloading of the img file in the background once you have waited the mandatory 168 hour wait period.