Related
Hi,
I got into a frustrating situation, I installed Oneplus OTA update after that phone is stuck in bootloop, only thing I can access is fastboot, after reading many articles, I found that unlocking bootloader can fix my problem.
But unlocking bootloader has become worst nightmare in OnePlus one, when I run # sudo fastboot oem unlock, it will reboot phone and goes into 1+ logo, then I reboot the phone again boot into bootloader and situation is still the same bootloader is still locked.
I also tried OnePlus toolkit, onplus toolbox and oneplus tool for linux, nothing is unlocking the bootloader.
Phone is not enabled for adb (debugging mode).
adb shows "offline" mode while phone in bootloop logo.
is there any way I can atleast force the phone to unlock boot, any help is appreciated?
I am a linux user, but I aslo tried in windows, samething.
Thanks
I think you need to sit down and re-read the guide on how to unlock your bootloader because you're not having a good understanding on what you're supposed to do.
http://forum.xda-developers.com/showthread.php?t=2788632 Read that thread and adjust accordingly to Linux unless you do it on a Windows-based machine.
zephiK said:
I think you need to sit down and re-read the guide on how to unlock your bootloader because you're not having a good understanding on what you're supposed to do.
http://forum.xda-developers.com/showthread.php?t=2788632 Read that thread and adjust accordingly to Linux unless you do it on a Windows-based machine.
Click to expand...
Click to collapse
Hi,
Thanks for reply, I have followed the complete guide to unlock bootloader, I updated the android sdk to the latest with android drivers.
Find the attachment how I have done that, but still the bootloader is locked.
In device status it shows that device temperted: true, is there any way I can change that to false using fastboot command?,
maybe that is the thing preventing me to unlock the bootloader.
Your help is appreciated.
Thanks
Dani
I only used 15 second adb installer on my PC for adb drivers. That way I don't copy paste files into SDK folder.
Anyways fastboot OEM device-info gives back tamper true and what is the other flag?
Make sure u don't put in typo like your op "ulock" lol fastboot OEM unlock should bring up wipe options on your phone :s
Sent From Bacon
ek69 said:
I only used 15 second adb installer on my PC for adb drivers. That way I don't copy paste files into SDK folder.
Anyways fastboot OEM device-info gives back tamper true and what is the other flag?
Make sure u don't put in typo like your op "ulock" lol fastboot OEM unlock should bring up wipe options on your phone :s
Sent From Bacon
Click to expand...
Click to collapse
Hi ek,
screen shots are attached with the reply to zephiK's message (all flags can been seen), however, fastboot oem unlock doesnt bring me wipe option (though I am ok to wipe).
Dani
After the fastboot OEM unlock command look at the phone, that is where the wipe stuff appears. Or it should.
Sent From Bacon
Hello everyone, I was in China recently, and bought my OPO there. Therefore, it came with colorOS.
I wanted to change it to the rom to SlimSaber. Unfortunately, I've been unable to do so.
To unlock the bootloader I'm using this set of instructions:
[GUIDE] OnePlus One - How to Unlock Bootloader, Install Custom Recovery and Root - http://forum.xda-developers.com/showthread.php?t=2788632
I think my problem is while unlocking the bootloader. I get into fastboot mode, and using the android-sdk devices I'm able to get the serial number of the phone.
But, when I run the fastboot OEM unlock, nothing happens. Everything should be erased, right? Well, that doesn't happen. After that, I enable the USB debugging, but after, when I'm supposed to disable the 'Updater recovery with system updates' I simply don't see that option.
Can anyone help me? Do you need any more info?
Tanks in advance;
Qskara said:
Hello everyone, I was in China recently, and bought my OPO there. Therefore, it came with colorOS.
I wanted to change it to the rom to SlimSaber. Unfortunately, I've been unable to do so.
To unlock the bootloader I'm using this set of instructions:
[GUIDE] OnePlus One - How to Unlock Bootloader, Install Custom Recovery and Root - http://forum.xda-developers.com/showthread.php?t=2788632
I think my problem is while unlocking the bootloader. I get into fastboot mode, and using the android-sdk devices I'm able to get the serial number of the phone.
But, when I run the fastboot OEM unlock, nothing happens. Everything should be erased, right? Well, that doesn't happen. After that, I enable the USB debugging, but after, when I'm supposed to disable the 'Updater recovery with system updates' I simply don't see that option.
Can anyone help me? Do you need any more info?
Tanks in advance;
Click to expand...
Click to collapse
Issue this command:
Code:
fastboot oem device-info
What does it return?
Transmitted via Bacon
Hi,
I recently got a brand new s6 G920A AT&T version from an authorized reseller. To my surprise the firmware on it is very old - 5.0.2 with sw version G920AUCU1AOCE
I have heard that this firmware was a pre-release/developer/engineering version of s6 and has unlocked bootloader. Is that true?
How do I find if the bootloader is locked or unlocked in my samsung s6 or for that matter in *any Samsung* phone? Is it possible to check using Odin or some other tool on whether the bootloader is unlocked?
Please let me know your thoughts or ideas! If the above is true, I could perhaps extract the unlocked bootloader and share it with everybody else!!
Thanks!
Alright Interesting...
Use ADB:
=========================================
1. Make to go to about device and tap build number 7 times.
2. Go to developer options (Above About Device)
3. Check usb debugging and oem (Just in case)
4. Connect your phone to your computer via usb cable (Of Course)
5. Download ADB Fastboot if you haven't already =====> https://forum.xda-developers.com/showthread.php?t=2317790
6. Install it and after that it should be set-up
6. Type the command fastboot devices
7. Then type fastboot oem device-info (BTW I am sorry for letting you know now but i think you might need to be in downloading mode or something to use the commands)
8. It should tell you if it is unlocked or not
==============================================
Method 2:
1. Boot up the phone normally then open the phone application and go to the dialer
2. *#*#7378423#*#*
3. Then service info --> configuration
4. Then it should say one of the following:
---------------------------------------------------------------------------------------------------------------------------------
1. Bootloader unlock allowed --Yes >> This means that your Bootloader is Locked
2. Bootloader Unlocked - Yes >> This means that your Bootloader is unlocked
I hope i was helpful to you, if not then i'm sorry to have wasted your time.
Thanks @ROOT67! Let me try both options out and get back on this thread.
ROOT67 said:
Use ADB:
=========================================
1. Make to go to about device and tap build number 7 times.
2. Go to developer options (Above About Device)
3. Check usb debugging and oem (Just in case)
4. Connect your phone to your computer via usb cable (Of Course)
5. Download ADB Fastboot if you haven't already =====> https://forum.xda-developers.com/showthread.php?t=2317790
6. Install it and after that it should be set-up
6. Type the command fastboot devices
7. Then type fastboot oem device-info (BTW I am sorry for letting you know now but i think you might need to be in downloading mode or something to use the commands)
8. It should tell you if it is unlocked or not
==============================================
Method 2:
1. Boot up the phone normally then open the phone application and go to the dialer
2. *#*#7378423#*#*
3. Then service info --> configuration
4. Then it should say one of the following:
---------------------------------------------------------------------------------------------------------------------------------
1. Bootloader unlock allowed --Yes >> This means that your Bootloader is Locked
2. Bootloader Unlocked - Yes >> This means that your Bootloader is unlocked
I hope i was helpful to you, if not then i'm sorry to have wasted your time.
Click to expand...
Click to collapse
Both the methods did not work! Please see for details below.
ROOT67 said:
Use ADB:
=========================================
1. Make to go to about device and tap build number 7 times.
2. Go to developer options (Above About Device)
3. Check usb debugging and oem (Just in case)
4. Connect your phone to your computer via usb cable (Of Course)
5. Download ADB Fastboot if you haven't already =====> https://forum.xda-developers.com/showthread.php?t=2317790
6. Install it and after that it should be set-up
6. Type the command fastboot devices
7. Then type fastboot oem device-info (BTW I am sorry for letting you know now but i think you might need to be in downloading mode or something to use the commands)
8. It should tell you if it is unlocked or not
==============================================
Click to expand...
Click to collapse
I could not put it in fastboot mode. Do we know if the Samsung s6 supports fastboot mode? If so, how to put it in fastboot mode?
Also as a side note, in developer mode under settings, I could find check box for USB debugging but not for OEM. There was another post which said that OEM checkbox was added under developer options only after bootloader lock was introduced in 5.1.1 firmware. Not sure if this is true.
Method 2:
1. Boot up the phone normally then open the phone application and go to the dialer
2. *#*#7378423#*#*
3. Then service info --> configuration
4. Then it should say one of the following:
---------------------------------------------------------------------------------------------------------------------------------
1. Bootloader unlock allowed --Yes >> This means that your Bootloader is Locked
2. Bootloader Unlocked - Yes >> This means that your Bootloader is unlocked
Click to expand...
Click to collapse
When I dial this number, nothing happened. Is there a different number for Samsung s6?
It's not a pre-release/developer/engineering firmware. It's just a really old firmware which released for public officially.
jilebi said:
Both the methods did not work! Please see for details below.
I could not put it in fastboot mode. Do we know if the Samsung s6 supports fastboot mode? If so, how to put it in fastboot mode?
Also as a side note, in developer mode under settings, I could find check box for USB debugging but not for OEM. There was another post which said that OEM checkbox was added under developer options only after bootloader lock was introduced in 5.1.1 firmware. Not sure if this is true.
When I dial this number, nothing happened. Is there a different number for Samsung s6?
Click to expand...
Click to collapse
No other number is available that i know of, like the person above stated it is a old firmware version and with that said i would highly try to prevent any updates from installing. I would love to help you out, but since i have no idea as to what would be needed to tell if the bootloader is unlocked, but i do know since Samsung is against us rooting and using our devices the way we want, it is safe to assume the bootloader is locked and because you have at&t variant. Your best bet to get your device bootloader information is to look around on the XDA forums.
Do you have any details on whether the bootloader was locked or unlocked for this old version? How can one test or check if bootloader is locked?
forumber2 said:
It's not a pre-release/developer/engineering firmware. It's just a really old firmware which released for public officially.
Click to expand...
Click to collapse
jilebi said:
Do you have any details on whether the bootloader was locked or unlocked for this old version? How can one test or check if bootloader is locked?
Click to expand...
Click to collapse
All AT&T branded nearly-new (including S6) Samsung devices has a non-unlockable locked bootloader.
There's no way to test that.
here are a couple of test scenario that i can think of. let me know your thoughts on them
- if the device is rooted, load a custom recovery like TWRP. next, try to boot into custom recovery. if it boots into custom recovery, bootloader is unlocked. if not, try to restore factory recovery using odin.
- if the device is rooted, load a custom ROM. next, try to boot into custom ROM. if it boots into custom ROM, bootloader is unlocked. if not, try to restore factory ROM using odin.
Will these test scenarios work? If not, what are the potential issues you see?
forumber2 said:
All AT&T branded nearly-new (including S6) Samsung devices has a non-unlockable locked bootloader.
There's no way to test that.
Click to expand...
Click to collapse
jilebi said:
here are a couple of test scenario that i can think of. let me know your thoughts on them
- if the device is rooted, load a custom recovery like TWRP. next, try to boot into custom recovery. if it boots into custom recovery, bootloader is unlocked. if not, try to restore factory recovery using odin.
- if the device is rooted, load a custom ROM. next, try to boot into custom ROM. if it boots into custom ROM, bootloader is unlocked. if not, try to restore factory ROM using odin.
Will these test scenarios work? If not, what are the potential issues you see?
Click to expand...
Click to collapse
- There's no custom recovery or custom kernel for SM-G920A, because of the reason I've wrote above.
- Installing a custom ROM doesn't require an unlocked bootloader unless the ROM doesn't require custom kernel. (Custom ROMs for SM-G920A don't require custom kernel (except leaked engineering/debugging kernel from Samsung for disabling dm-verity))
forumber2 said:
- There's no custom recovery or custom kernel for SM-G920A, because of the reason I've wrote above.
- Installing a custom ROM doesn't require an unlocked bootloader unless the ROM doesn't require custom kernel. (Custom ROMs for SM-G920A don't require custom kernel (except leaked engineering/debugging kernel from Samsung for disabling dm-verity))
Click to expand...
Click to collapse
Got it. Thanks. That makes sense.
Here is another option. For making custom recovery, my understanding is that partition info is needed. If the device is rooted e.g. using Pingpong (which works for this Android version), then one can get a partition info and compile TWRP for G920A. If so, can one try to install custom recovery like TWRP and verify if bootloader is locked? It feels to me that this may work. Do you see any flaws?
One possible flaw is that if bootloader is locked, it will prevent recovery from loading. So the phone will be without a working recovery. In that case, can factory recovery be re-installed using Odin?
Also, will any of the above steps trigger the KNOX flag?
jilebi said:
Got it. Thanks. That makes sense.
Here is another option. For making custom recovery, my understanding is that partition info is needed. If the device is rooted e.g. using Pingpong (which works for this Android version), then one can get a partition info and compile TWRP for G920A. If so, can one try to install custom recovery like TWRP and verify if bootloader is locked? It feels to me that this may work. Do you see any flaws?
One possible flaw is that if bootloader is locked, it will prevent recovery from loading. So the phone will be without a working recovery. In that case, can factory recovery be re-installed using Odin?
Also, will any of the above steps trigger the KNOX flag?
Click to expand...
Click to collapse
You don't have to get partition info, and compile TWRP. All S6 variants are using same partition name scheme and there are no difference on TWRP builds between S6 variants (except kernel and DTB).
The bootloader won't allow you to flash any custom recovery image (via Odin or in Android OS). If you could flash it, It won't boot it up anyway.
I don't have any idea about the KNOX trigger on AT&T variant devices, but I think it won't increase anyway.
forumber2 said:
You don't have to get partition info, and compile TWRP. All S6 variants are using same partition name scheme and there are no difference on TWRP builds between S6 variants (except kernel and DTB).
The bootloader won't allow you to flash any custom recovery image (via Odin or in Android OS). If you could flash it, It won't boot it up anyway.
I don't have any idea about the KNOX trigger on AT&T variant devices, but I think it won't increase anyway.
Click to expand...
Click to collapse
Sorry, I perhaps misunderstood from your last post that since custom recovery is not available for G920A it implied its partition info was different from other variants. If it is the same partition structure for all variants, then I guess we can use the TWRP for the G920F international version for which bootloader is unlocked.
Now that we agree that TWRP is available for use on G920A, the next question is how to load it. My thought is that if the device is rooted that means one can use dd at root shell prompt to write TWRP to the recovery partition, without using Odin or the current bootloader. Do you agree?
Not sure I understand why you say that if one could flash TWRP it would not boot anyways. If bootloader is unlocked (which is what we are testing here), then it should boot, right?
jilebi said:
Sorry, I perhaps misunderstood from your last post that since custom recovery is not available for G920A it implied its partition info was different from other variants. If it is the same partition structure for all variants, then I guess we can use the TWRP for the G920F international version for which bootloader is unlocked.
Now that we agree that TWRP is available for use on G920A, the next question is how to load it. My thought is that if the device is rooted that means one can use dd at root shell prompt to write TWRP to the recovery partition, without using Odin or the current bootloader. Do you agree?
Not sure I understand why you say that if one could flash TWRP it would not boot anyways. If bootloader is unlocked (which is what we are testing here), then it should boot, right?
Click to expand...
Click to collapse
A custom recovery is not available for G920A, because no one could try any custom recovery on G920A due to locked bootloader.
Yes you can write the recovery image via dd at root shell prompt.
And yes, If bootloader is unlocked, it will boot it up.
Sorry to ressurect this old thread, but can you (or anybody else who is knowledgeable) answer the following?
1. Since custom recovery is not available for G920A, which of the Tmobile/Sprint/International versions of TWRP custom recovery would you recommend to use for testing if bootloader is unlocked, using either ODIN or dd method?
2. If bootloader is unlocked, you are suggesting below that it should boot up. However, if it is locked, then will the phone still boot up? i.e. if one does not go into recovery mode, will it still boot up or does the bootloader check if both recovery and kernel are signed and if it finds that the recovery is unsigned, will it also prevent the signed kernel from booting up?
Thanks!
forumber2 said:
A custom recovery is not available for G920A, because no one could try any custom recovery on G920A due to locked bootloader.
Yes you can write the recovery image via dd at root shell prompt.
And yes, If bootloader is unlocked, it will boot it up.
Click to expand...
Click to collapse
I have installed the drivers and got the unlock code and enable usb debugging and oem unlock when i wrote in adb commmand "adb reboot bootloader" the phone turns off and the led light turn into blue but nothing more, i can't communicate with the phone no more..
Is the reason i'm running on oreo?
Do i have to downgrade to marshmellow?
Sorry for my bad english
fidelkhaled said:
I have installed the drivers and got the unlock code and enable usb debugging and oem unlock when i wrote in adb commmand "adb reboot bootloader" the phone turns off and the led light turn into blue but nothing more, i can't communicate with the phone no more..
Is the reason i'm running on oreo?
Do i have to downgrade to marshmellow?
Sorry for my bad english
Click to expand...
Click to collapse
Hello,
That is not how to unlock the bootloader. You need to follow the procedure described here
https://developer.sony.com/develop/...der/how-to-unlock-bootloader/#tutorial-step-3
gregbradley said:
Hello,
That is not how to unlock the bootloader. You need to follow the procedure described here
https://developer.sony.com/develop/...der/how-to-unlock-bootloader/#tutorial-step-3
Click to expand...
Click to collapse
I've tried this method too but same result .
I think i have to downgrade to marshmallow
fidelkhaled said:
I've tried this method too but same result .
I think i have to downgrade to marshmallow
Click to expand...
Click to collapse
Well that method is the correct method from Sony.
No, you do not need to downgrade, you only need to do that to back up your TA. You can unlock the bootloader on any version.
Have you checked if your phone allows the bootloader to be unlocked?
1. do u have unlock key from sony ? if yes
2. connect your device in fastboot mode
3. open FLASHTOOL
4. click the BLU button
5. enter that KEY
6. click OK
DONE
congratulations, the device is unlocked and you have just LOST YOUR DRM KEYS <3 ( i hope you have backed them up ) (using universalTAbackupv2 aka dirtycow script)
YasuHamed said:
1. do u have unlock key from sony ? if yes
2. connect your device in fastboot mode
3. open FLASHTOOL
4. click the BLU button
5. enter that KEY
6. click OK
DONE
congratulations, the device is unlocked and you have just LOST YOUR DRM KEYS <3 ( i hope you have backed them up ) (using universalTAbackupv2 aka dirtycow script)
Click to expand...
Click to collapse
The flashtool method just uses the official method from Sony in a script, so if the official way does not work neither will the flashtool method
Hey guys,
I think I found a way to unlock the bootloader on the Nokia 5.1 Plus. I didn't do it yet, but can someone please try it and see if it works?
Instructions:
1. Boot into recovery. I made a guide on how to do that in case you don't know how. Here's the link:https://forum.xda-developers.com/nokia-x5/how-to/guide-how-to-access-recovery-global-t4054561
2. Select reboot to bootloader.
3. Run fastboot oem unlock from adb terminal and see if anything happens.
PS. Running adb reboot fastboot from pc doesn't work-the phone just restarts-but rebooting to bootloader option from recovery actually gets it to fastboot mode.
If it works please tell me in a reply.
BurningGrip3 said:
Hey guys,
I think I found a way to unlock the bootloader on the Nokia 5.1 Plus. I didn't do it yet, but can someone please try it and see if it works?
Instructions:
1. Boot into recovery. I made a guide on how to do that in case you don't know how. Here's the link:https://forum.xda-developers.com/nokia-x5/how-to/guide-how-to-access-recovery-global-t4054561
2. Select reboot to bootloader.
3. Run fastboot oem unlock from adb terminal and see if anything happens.
PS. Running adb reboot fastboot from pc doesn't work-the phone just restarts-but rebooting to bootloader option from recovery actually gets it to fastboot mode.
If it works please tell me in a reply.
Click to expand...
Click to collapse
any hero? (I'm afraid of running out of phone)
BurningGrip3 said:
Hey guys,
I think I found a way to unlock the bootloader on the Nokia 5.1 Plus. I didn't do it yet, but can someone please try it and see if it works?
Instructions:
1. Boot into recovery. I made a guide on how to do that in case you don't know how. Here's the link:https://forum.xda-developers.com/nokia-x5/how-to/guide-how-to-access-recovery-global-t4054561
2. Select reboot to bootloader.
3. Run fastboot oem unlock from adb terminal and see if anything happens.
PS. Running adb reboot fastboot from pc doesn't work-the phone just restarts-but rebooting to bootloader option from recovery actually gets it to fastboot mode.
If it works please tell me in a reply.
Click to expand...
Click to collapse
Hey don't post guides for other if you don't know what it means, You will get other people phones bricked.
FYI Nokia phones requires permission to unlock bootloader.
adb oem unlock doesn't work now a days for most of the phones as you know many companies has made rooting and changing roms difficult. (excluding OnePlus and Pixel).
BurningGrip3 said:
Hey guys,
I think I found a way to unlock the bootloader on the Nokia 5.1 Plus. I didn't do it yet, but can someone please try it and see if it works?
Instructions:
1. Boot into recovery. I made a guide on how to do that in case you don't know how. Here's the link:https://forum.xda-developers.com/nokia-x5/how-to/guide-how-to-access-recovery-global-t4054561
2. Select reboot to bootloader.
3. Run fastboot oem unlock from adb terminal and see if anything happens.
PS. Running adb reboot fastboot from pc doesn't work-the phone just restarts-but rebooting to bootloader option from recovery actually gets it to fastboot mode.
If it works please tell me in a reply.
Click to expand...
Click to collapse
For me it gave an error (FAILED (remote: unknown command)), where
Code:
fastboot flashing unlock
gave me an error on the device asking me if I wanted to unlock flashing or to cancel. I don't know if this helps anyone anything but it seems to have worked because if I run
Code:
fastboot flashing get_unlock_ability
I get the message (bootloader) unlock_ability = 1
BurningGrip3 said:
Hey guys,
I think I found a way to unlock the bootloader on the Nokia 5.1 Plus. I didn't do it yet, but can someone please try it and see if it works?
Instructions:
1. Boot into recovery. I made a guide on how to do that in case you don't know how. Here's the link:https://forum.xda-developers.com/nokia-x5/how-to/guide-how-to-access-recovery-global-t4054561
2. Select reboot to bootloader.
3. Run fastboot oem unlock from adb terminal and see if anything happens.
PS. Running adb reboot fastboot from pc doesn't work-the phone just restarts-but rebooting to bootloader option from recovery actually gets it to fastboot mode.
If it works please tell me in a reply.
Click to expand...
Click to collapse
No , you cant unlock the bootloader by this way for this device
Nokia 5.1 plus bootloader unlock use mtk universal V5 tool it's easy to use
Macc40 said:
Nokia 5.1 plus bootloader unlock use mtk universal V5 tool it's easy to use
Click to expand...
Click to collapse
Sure it will work with subject device?