Whenever I attempt to unlock the bootloader it will reboot into android without any confirmation, I am on CM12S 5.0.2, USB Debugging enabled and I am on Windows, with Minimal ADB And fastboot so i didnt have to install all the other studio things, it appeared once in adb devices so I tried to unlock and it did the same as before but I lost all my data.
Issue this command:
Code:
fastboot oem device-info
What's the output?
XDA Moderator
Transmitted via Bacon
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.016s]
finished. total time: 0.021s
So according to that it has been unlocked, which doesnt make sense as I got no warning about data loss.
TheGamingBarrel said:
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.016s]
finished. total time: 0.021s
So according to that it has been unlocked, which doesnt make sense as I got no warning about data loss.
Click to expand...
Click to collapse
It was probably already unlocked before you received the phone, where did you buy it?
XDA Moderator
Transmitted via Bacon
Heisenberg said:
It was probably already unlocked before you received the phone, where did you buy it?
XDA Moderator
Transmitted via Bacon
Click to expand...
Click to collapse
I bought it brand new off their website ( https://oneplus.net/uk/one ) but i tried to install custom recovery and it was fine, so I dont really think it matters
Related
I have Photon Q from Sprint with Android 4.1.2 (9.8.2Q-122_XT897_FFW-5), bootloader 109B(*)
log
Code:
C:\>fastboot oem get_unlock_data
...
(bootloader) Could not get unlock data!
OKAY [ 0.016s]
finished. total time: 0.016s
Can I unlock this Photon Q?
a good data cable is key!
carl0 said:
I have Photon Q from Sprint with Android 4.1.2 (9.8.2Q-122_XT897_FFW-5), bootloader 109B(*)
log
Code:
C:\>fastboot oem get_unlock_data
...
(bootloader) Could not get unlock data!
OKAY [ 0.016s]
finished. total time: 0.016s
Can I unlock this Photon Q?
Click to expand...
Click to collapse
Make sure that you have a bone fide data cable. I encountered similar errors and wasted a lot of time early in my unlocking/rooting efforts.
I bought this cable from Amazon for around $5: "Motorola SKN6238 MicroUSB Data Cable", and it has been great.
Good luck ...
I have Motorola SKN6378A MicroUSB Data Cable.
Code:
C:\>fastboot getvar all
(bootloader) version-bootloader: 109B(*)
(bootloader) product: asanti_c
(bootloader) secure: yes
(bootloader) mid: 0057
(bootloader) version: 0.5
(bootloader) serialno: T0********
(bootloader) qe: qe 0/0
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) max-download-size: 31457280
(bootloader) emmc-size: 8GB
(bootloader) reason: Reboot to bootloader
(bootloader) revision-hardware: 0x82B0
(bootloader) cpu: MSM8960 CS
(bootloader) uid: 4302D30302000100000000000000
(bootloader) cid: 0x00
all:
finished. total time: 0.016s
Could it be the fault of the cable?
Has anyone else met this problem?
It's been a very long time since I unlocked my Q, but are you putting in the proper code? From your command prompt output above, it seems like you did not put in the unlock code.
First he needs the "oem_unlock_code" from the PQ, before he gets the correct unlock code from Motorola.
I think that the first thing already fails and he is not able to continue with the Motorola site.
I remember hardly that there was another way of unlocking the bootloader, but I don't remember the name.
Something only for Motorola devices I think.
edit: Was it "motochopper"? I've never used it, so I'm not sure.
Loader009 said:
First he needs the "oem_unlock_code" from the PQ, before he gets the correct unlock code from Motorola.
I think that the first thing already fails and he is not able to continue with the Motorola site.
I remember hardly that there was another way of unlocking the bootloader, but I don't remember the name.
Something only for Motorola devices I think.
edit: Was it "motochopper"? I've never used it, so I'm not sure.
Click to expand...
Click to collapse
Yes, motochopper. You could try that OP, as a way to unlock the device - albeit unofficially.
Since the OP is running 4.1.2, my guess is that motochopper won't work (because that exploit was probably repaired in 4.1.2), but one if its successors might.
Sent from my XT897 using Tapatalk
carl0 said:
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
Click to expand...
Click to collapse
This is weird.
When and where did you get this device?
@carl0 : It's indeed very strange that get_unlock_data doesn't work on your device.
But I'm pretty sure that the unofficial bootloader unlock tool Motopocalypse by Dan Rosenberg will work: http://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
Motopocalypse requires the device to be rooted, which can be easily achieved e.g. by geohot's towelroot: https://towelroot.com/
mrvek said:
This is weird.
When and where did you get this device?
Click to expand...
Click to collapse
ebay :laugh:
kabaldan said:
@carl0 : It's indeed very strange that get_unlock_data doesn't work on your device.
But I'm pretty sure that the unofficial bootloader unlock tool Motopocalypse by Dan Rosenberg will work: h**p://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
Motopocalypse requires the device to be rooted, which can be easily achieved e.g. by geohot's towelroot: h**ps://towelroot.com/
Click to expand...
Click to collapse
I've tried this another way of unlocking the bootloader and it works well. :fingers-crossed:
Thanks for all!
I've rooted and unlocked my OPO and flashed SlimSaber - absolutely love it. I'd now like to re-lock/unroot my OPO as I need to use my phone as a BYOD at work and the Maas360 MDM application won't install on a root device.
Can I get some guidance on how to accomplish this (if possible at all)?
Relocking is a simple fastboot command:
Code:
fastboot oem lock
Unrooting just involves going into SuperSU and selecting the "full unroot" option.
Transmitted via Bacon
timmaaa said:
Relocking is a simple fastboot command:
Code:
fastboot oem lock
Unrooting just involves going into SuperSU and selecting the "full unroot" option.
Transmitted via Bacon
Click to expand...
Click to collapse
Perfect, and this will allow me to keep SlimSaber and not disable any of its inherent functionality?
If I want to unlock again, I presume it's another:
Code:
fastboot oem unlock
But that this won't require a wipe?
Mhaddy said:
Perfect, and this will allow me to keep SlimSaber and not disable any of its inherent functionality?
If I want to unlock again, I presume it's another:
Code:
fastboot oem unlock
But that this won't require a wipe?
Click to expand...
Click to collapse
You'll only lose access to root apps. If you want to unlock again that's the right command, but it will completely wipe your internal storage, there's no way around that.
Transmitted via Bacon
Awesome, thanks!
Wondering if I'm missing a step ... I rebooted to fastboot mode, loaded up cmd prompt and changed to the platform-tools directory:
Code:
cd Desktop/android-sdk-windows/platform-tools
Then verified my phone was connected:
Code:
fastboot devices
Then typed
Code:
fastboot oem lock
And all I get is "..." on screen.
What have I missed?
Mhaddy said:
Wondering if I'm missing a step ... I rebooted to fastboot mode, loaded up cmd prompt and changed to the platform-tools directory:
Code:
cd Desktop/android-sdk-windows/platform-tools
Then verified my phone was connected:
Code:
fastboot devices
Then typed
Code:
fastboot oem lock
And all I get is "..." on screen.
What have I missed?
Click to expand...
Click to collapse
Give this command:
Code:
fastboot oem device-info
What does it return?
Transmitted via Bacon
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ -0.000s]
finished. total time: -0.000s
Mhaddy said:
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ -0.000s]
finished. total time: -0.000s
Click to expand...
Click to collapse
Hmm, that's odd. Not sure why it isn't locking again for you. You could try looking here:
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
There's a bootloader lock/unlock toggle script you can flash with TWRP.
Transmitted via Bacon
Be very careful!!!
If you end up with a device with
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
You might not be able to unlock it again using fastboot!!
waterdaan said:
Be very careful!!!
If you end up with a device with
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
You might not be able to unlock it again using fastboot!!
Click to expand...
Click to collapse
I won't be able to unlock it again at all or unlock it again without wiping it?
Mhaddy said:
I won't be able to unlock it again at all or unlock it again without wiping it?
Click to expand...
Click to collapse
It's hit and miss. Sometimes after locking the bootloader is unable to be unlocked again via fastboot. Keep TWRP on your phone though and you'll be able to flash the unlocker zip.
Unlocking via fastboot always wipes the device. Unlocking via the unlocker zip never wipes the device.
Transmitted via Bacon
Hello guys
I just want help from you guys in order to change Device (MI4) tampered status TRUE to FALSE. I unlocked bootloader once by command -- fastboot oem unlock then again locked it by fastboot oem lock. But Device tampered is still showing as TRUE. I just want to change it to FALSE. Will this effect anything (warranty or something) if i don't change it. Please help???
C:\Windows\system32>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.012s]
finished. total time: 0.013s
Nobody has answered this, wow. I'm having same issue
Erase all partitions via fastboot then turn off and plug in to pc. the device will appear as HS USB QDloader. use QFil to fix. then "device tampered" is gone
Beware: may brick the phone and corrupt the imei number
I used this guide... http://en.miui.com/thread-807252-1-1.html
Every issue in the (bootloader) section is showed as false. Easy guide, easy process
Ignore...
Hello, gentlemens!
I rollback RM 5 Pro from 12 to Android 11 (Realme UI 2.0). I didn't sure is bootloader unlocked or not. Last two results (false) confusing me. Here is results:
PS C:\Program Files (x86)\Minimal ADB and Fastboot> fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.016s]
finished. total time: 0.016s
Btw, I can't install TWRP again. So, I need little help about bootloader, is unlocked or not? Thank you.
Anybody know?
Hello everybody,
I need help to get my phone inbricked. Last year I installed LineageOS on my device and everything worked fine. Since I needed for some reason to relock my phone. I did via fastboot:
Bash:
fastboot oem lock
Since then my phone prints out: "The System has been destroyed ..."
I cannot flash anymore...
Code:
$ fastboot oem device-info
< waiting for any device >
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.000s]
finished. total time: 0.000s
What can I do to unlock the bootloader?