I forgot my new Pattern lock. I had TWRP but it is not working now. Volume Down + Power button just gives a blank screen. After the Oxygen OS latest update, the developer options have been disabled which means OEM unlock and USB debugging are disabled.
Android Device Manager is not helping. I try erasing from the ADM but phone says rebooting and just switches off.
This is what happens when I boot into fastboot using volume up + power:
Code:
fastboot oem unlock
...
FAILED (remote: oem unlock is disabled)
finished. total time: 0.016s
fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Device is_verified: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_ locked: 1
(bootloader) exec_console_unconsole: 0
OKAY[0.08s]
finished. total time: 0.078s
Code:
adb devices
List of devices attached
adb does not detect any devices either.
What do I do?
The procedure mentioned in Technobuzz Unbrick oneplus 2 is not working either. Nothing seems to be happening after step 8. (Cannot post outside link as I am newbie)
http://forum.xda-developers.com/one...k-to-solve-t3325419/post65579304#post65579304
Similar case, refer to solutions posted
ciber05 said:
http://forum.xda-developers.com/one...k-to-solve-t3325419/post65579304#post65579304
Similar case, refer to solutions posted
Click to expand...
Click to collapse
Found this method in the above quoted post which worked like a charm.
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
Thanks
Hi,
Earlier on today I was trying to root my phone (Well at least put TWRP on so I could mount a rom) and somehow the bootloader got locked during the process this has prevented me to install any roms....
I know it's locked because of -
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Device is_verified: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_locked: 1
(bootloader) exec_console_unconsole: 0
OKAY [ 0.079s]
finished. total time: 0.080s
I've tried to recover it back to normal during the "Fastboot Mode" state but not had any luck I believe the phones bricked? -
C:\Users\Liam\Desktop\One Plus Recovery\A2001_14_A.03_150805>fastboot flash user
data userdata_64G.img
target reported max download size of 536870912 bytes
erasing 'userdata'...
FAILED (remote: device is locked. Cannot erase)
finished. total time: 0.003s
I need this sorting as I don't have a phone to use, and would really apreiciate if someone could help me as i've spent like 8 hours today trying to sort it but not had any luck i've downloaded drivers (Qualcom), Android SDK, this Qualcom-download-tool for recovery and nothing seems to work
It will only boot into "Fastboot Mode"
i recommand you to ask this on OnePlus forums there is more people that answer
otherwize did you tried fastboot oem unlock and is your phone recognize by your computer ?
Use the Qualcomm recover method mentioned many times over in this forum.
try fastboot oem unlock.
did u enabled oem unlock option in dev settings while unlocking bl?
what exactly steps you followed?
I have a OnePlus 2 phone which has its boot-loader unlocked at some point and I accidentally re-locked the bootloader and was unable to flash through fast-boot and I'm now unable to root the phone.
I have TWRP ready because I flashed it earlier before i re-locked the bootloader.
I am able to boot to the OS, fastboot and TWRP recovery mode.
However rooting seems impossible for now.
Whenever I tried to unlock bootloader it shows:
C:\adb>fastboot oem unlock
...
OKAY [ 0.122s]
finished. total time: 0.122s
However, after trying to check if the device is unlocked, it shows that I didn't actually unlocked the device, rather:
C:\adb>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device is_verified: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_locked: 1
(bootloader) exec_console_unconsole: 0
OKAY [ 0.063s]
finished. total time: 0.063s
This is the only problem that I've received from my other phone, I used to root my 1+1 and it went well without a single problem.
And this is my first post (not like you guys care anyways) and I don't really know where to post my troubles so I apologize if I posted this in the wrong place.
Any suggestions / help would be very much appreciated.
Thanks in advance~
Kev.
[EDIT]
I have tried various methods to restore the phone when soft-bricked with SuperSU, and it works, however it doesn't allow me to reset the bootloader's status and I'm not capable of doing so.
Did you enable OEM unlocking in Developer settings?
Hi everyone,
I went back to stock recovery and stock ROM (5.9.020S) in order to use Android Pay.
But I am facing one last issue for locking the device. Each time I go into fast boot mode, I lock the device, I check with device-info, it confirms it is locked. However after reboot I check again it has reverted back as unlocked.
How can I lock the persistently?
It is as if there is a script somewhere at boot that automatically unlock the device bootloader.
- flash the aboot from stock ROM
- flash the xbl from stock ROM
- do not reboot to keep the bootloader still unlocked
- boot in TWRP (do not flash)
- wipe, factory reset, format, reboot system
In order to do what you suggest, I flashed TWRP recovery first. Then I followed all the steps. Then I tried to flash the stock recovery back and tried to lock. Unfortunately, it did not help, still the same issue.
In fastboot, I do "fastboot flashing lock" or "fastboot oem lock". Then I check the status with "fastboot oem device-info". Right after, I always get "Device unlocked: false" which is good and confirm the lock has worked at first.
But if I reboot the bootloader and try again, then the status is back to "Device unlocked: true" and the device is unlocked again. It keeps unlocking after reboot if I attempt to lock.
I need to have the device NOT unlocked in order to use Android Pay. So now, I am not sure what to do to be able to lock the device...
You don't need to flash TWRP in fact sometimes you don't need it (if there is no encryption but do it to be sure) right after flashing
fastboot flash xbl xbl.elf
fastboot flash aboot emmc_appsboot.mbn
These were indeed the files I flashed previously for aboot and xbl.
I tried again to flash the files in fastboot mode, then lock the device with "fastboot oem lock". After reboot, it is unlocked again.
Did you extract those files from 20s or any official OTA zip? Flashing those files are guaranteed to lock the bootloader again. I've tried it many times already so not sure what else could be missing.
What is being displayed when you do right after the flashing and TWRP steps?
Like this?
fastboot oem device-info
...
(bootloader) Device product name: [le_zl1_oversea]
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.097s]
finished. total time: 0.098s
---------- Post added at 02:39 PM ---------- Previous post was at 02:37 PM ----------
See this thread if it will help...
https://forum.xda-developers.com/le-pro3/how-to/guide-return-to-stock-lock-bootloader-t3539513
I got the files from 20S. It really does not work for me.
I do:
fastboot flash xbl xbl.elf
fastboot flash aboot emmc_appsboot.mbn
Click to expand...
Click to collapse
After this when I check, it is like this (before and after reboot):
(bootloader) Device product name: [le_zl1_whole_netcom]
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.110s]
finished. total time: 0.111s
Click to expand...
Click to collapse
Anyway, thanks for trying to help me!
Old thread: Unrooting gives me bootloop?
Hi there everyone,
After upgrading to Oreo, I unlocked my bootloader, flashed TWRP and Magisk. After that I did a backup of my System and Boot partitions on my currently active slot B. For some reason Slot A doesn't really boot up, so I don't really know what's up with that.
The problem is, before rooting everything was perfect and after the root I feel the instability. I've been using rooted devices for years now and I've never really had problems with the stock ROM being rooted.
So how do I unroot? Well, it's as simple as clicking Complete Unroot in Magisk. Yeah, that bootloops. Trying to flash MagiskUninstaller zip? That bootloops too. The only thing that saved me from those bootloops was that backup I did with TWRP. Yeah, that was after Magisk already had take a crap on my boot image.
Any suggestions that don't involve me losing my 30 Gigs of precious data? I would like to try with Mi Flash Tool but I'm scared from bootlooping for long periods of time (I don't have all day, after all).
New question: How to lock bootloader without wiping?
Hi there again!
I tried flashing the original system.img and boot.img from a fastboot Oreo ROM I found online. I just wanted to lock my bootloader, since currently I don't really need Root access anymore and I don't want this poor security a phone with an unlocked bootloader brings. The problem is, when I type fastboot oem lock it doesn't want to boot anymore, even without Magisk.
Does anybody know a fastboot ROM out there that can be locked? At the official MIUI.com website the fastboot ROM hasn't been updated for a very long time and I don't want to wipe my data. Does anybody have a perfectly working Oreo image that can be locked?
It bootloops, because you:
1. installed TWRP (first mod of boot.img)
2. installed Magisk (it backed up your boot.img with TWRP already installed)
3. when you uninstalled Magisk, you effectively restored boot image with TWRP, which as far as I know doesn't disable dm-verity which in turn doesn't allow boot of modified system/boot image
The safest method of unrooting is to flash stock Oreo boot.img directly via fastboot. Next time try to avoid installing TWRP (it's not needed for installing Magisk). Don't try to flash Nougat system, your data can't be read by old system anymore.
For a quick solution it should be enough to install Magisk again.
_mysiak_ said:
It bootloops, because you:
1. installed TWRP (first mod of boot.img)
2. installed Magisk (it backed up your boot.img with TWRP already installed)
3. when you uninstalled Magisk, you effectively restored boot image with TWRP, which as far as I know doesn't disable dm-verity which in turn doesn't allow boot of modified system/boot image
The safest method of unrooting is to flash stock Oreo boot.img directly via fastboot. Next time try to avoid installing TWRP (it's not needed for installing Magisk). Don't try to flash Nougat system, your data can't be read by old system anymore.
For a quick solution it should be enough to install Magisk again.
Click to expand...
Click to collapse
Thank you very much for the help! I'm gonna try this now. I'm pretty new to this A/B partitioning scheme, I knew that there isn't a recovery partition but I didn't know that TWRP is stored in Boot.img
Thanks again! Have a wonderful day/night!
_mysiak_ said:
It bootloops, because you:
1. installed TWRP (first mod of boot.img)
2. installed Magisk (it backed up your boot.img with TWRP already installed)
3. when you uninstalled Magisk, you effectively restored boot image with TWRP, which as far as I know doesn't disable dm-verity which in turn doesn't allow boot of modified system/boot image
The safest method of unrooting is to flash stock Oreo boot.img directly via fastboot. Next time try to avoid installing TWRP (it's not needed for installing Magisk). Don't try to flash Nougat system, your data can't be read by old system anymore.
For a quick solution it should be enough to install Magisk again.
Click to expand...
Click to collapse
Hey there again!
I tried to boot from the stock boot.img but it bootloops again! The backup from before is, again, what saved me.
Am I stuck now? Is there something wrong with my system.img? Or my /data partition? I'm scared of even reflashing clean.
nicolasmart said:
Hey there again!
I tried to boot from the stock boot.img but it bootloops again! The backup from before is, again, what saved me.
Am I stuck now? Is there something wrong with my system.img? Or my /data partition? I'm scared of even reflashing clean.
Click to expand...
Click to collapse
Which stock boot.img exactly did you use?
_mysiak_ said:
Which stock boot.img exactly did you use?
Click to expand...
Click to collapse
The one from the Oreo fastboot ROM. Got it from here.
nicolasmart said:
The one from the Oreo fastboot ROM. Got it from here.
Click to expand...
Click to collapse
When you ran TWRP for the first time, it asked you if you want to allow system modification (mount as R/W) - did you allow it? If yes, it has tampered your system partition and you won't be able to boot with stock boot.img due to dm-verity. Either install Magisk again or reflash stock Oreo system.img (from the link you provided).
_mysiak_ said:
When you ran TWRP for the first time, it asked you if you want to allow system modification (mount as R/W) - did you allow it? If yes, it has tampered your system partition and you won't be able to boot with stock boot.img due to dm-verity. Either install Magisk again or reflash stock Oreo system.img (from the link you provided).
Click to expand...
Click to collapse
OK, I can reinstall the system.img and boot.img via Fastboot. It won't delete any data, right?
Edit: Thanks for all your support again! You're the saviour of my Mi!
nicolasmart said:
OK, I can reinstall the system.img and boot.img via Fastboot. It won't delete any data, right?
Edit: Thanks for all your support again! You're the saviour of my Mi!
Click to expand...
Click to collapse
Your data is safe as long as you don't run incorrect command (DON'T flash userdata.img and DON'T run fastboot command with "-w" switch)
fastboot flash boot boot.img
fastboot flash system_a (and/or system_b) system.img
and you are good to go. Don't panic when system flashing will appear as stuck, it takes some time while it splits 3gb file into 6 smaller ones and starts the actual flashing.
_mysiak_ said:
Your data is safe as long as you don't run incorrect command (DON'T flash userdata.img and DON'T run fastboot command with "-w" switch)
fastboot flash boot boot.img
fastboot flash system_a (and/or system_b) system.img
and you are good to go. Don't panic when system flashing will appear as stuck, it takes some time while it splits 3gb file into 6 smaller ones and starts the actual flashing.
Click to expand...
Click to collapse
Thank you! But why should I run fastboot flash boot boot.img?? Isn't it fastboot flash boot_b boot.img? I'm on slot B currently.
nicolasmart said:
Thank you! But why should I run fastboot flash boot boot.img?? Isn't it fastboot flash boot_b boot.img? I'm on slot B currently.
Click to expand...
Click to collapse
You are right, for restore you should "fastboot flash boot_b boot.img". I was probably thinking about rooting procedure where you should use "fastboot boot boot.img"
_mysiak_ said:
You are right, for restore you should "fastboot flash boot_b boot.img". I was probably thinking about rooting procedure where you should use "fastboot boot boot.img"
Click to expand...
Click to collapse
Well, I did all that and I now have a perfectly working system with stock recovery and I think it doesn't boot loop anymore with a stock boot image. Thank you!
However, I tried to lock my bootloader via fastboot oem lock, the first time I was using some shady boot image which should be "stock" but it really wasn't, and it said "The system has been destroyed." I really laughed at this label and went into fastboot to unlock my bootloader again. I switched the boot image to a legit one which has Magisk installed, tried to lock again but this time it flashed the Mi logo for a split second and then a dark screen appeared (can somebody please explain this weird behaviour?). I really scared because the PC wasn't detecting the phone but I held the Volume Down + Power buttons for 10 seconds hoping I will see the Mi Bunny on the Fastboot. Yeah, it worked. I unlocked the bootloader again (lol) and my phone was working again!
Don't worry! My phone's still OK and 100% functioning.
The only reason I tried to lock my bootloader with Magisk installed is because somebody said it worked for them. However, now I realize how risky would that be. Whenever an OTA appears you should hope you don't get locked out of your phone.
So, people with a rooted Mi A1 - don't lock your bootloader unless you fully unroot and revert to stock!!!
How can I lock my bootloader again without wiping? (See the updated first post for more information)
nicolasmart said:
How can I lock my bootloader again without wiping? (See the updated first post for more information)
Click to expand...
Click to collapse
Just wait for an official Xiaomi fastboot Oreo ROM and either use MiFlash or included script "flash_all_except_storage.bat". It will lock bootloader at the end of flashing procedure. Though you probably won't gain much added security as you can unlock the bootloader without data wipe at any time (some reports say that you even don't need "allow oem unlock" in developer settings, but I haven't tried that).
nicolasmart said:
How can I lock my bootloader again without wiping? (See the updated first post for more information)
Click to expand...
Click to collapse
For more detailed instructions have a look over here: https://forum.xda-developers.com/mi-a1/how-to/ota-official-fastboot-image-n2g47h-7-12-t3728929
flash_all_except_storage = Keep your data, bootloader gets re-locked is the variant you are looking for.
Please keep in mind, that downgrading is not recommended. So this solution is absolutely fine when you are at 7.12.19 or below.
If you are not, you have to wait for the next fastboot update package to become available (like me)
It’s better to do a clean flash using the ROM and MiFlash provided on Xiaomi Website to ensure that the system is unmodified and you won’t get errors or bricks during a future OTA.
I don't want to clean flash. It will take forever for Xiaomi to release the new fastboot ROM
nicolasmart said:
I don't want to clean flash. It will take forever for Xiaomi to release the new fastboot ROM
Click to expand...
Click to collapse
Fastboot ROM should be out in a couple of days, usually it's released one week after first OTA update (the one from 19th December was online on 26th or 27th if I remember correctly).
Edit: Clean flash is not necessary, only full flash of all stock images, except user data.
_mysiak_ said:
Though you probably won't gain much added security as you can unlock the bootloader without data wipe at any time
Click to expand...
Click to collapse
As an old Nexus user (Nexus 7, Nexus 7 2013, Nexus 5X) I was shocked when I have found this.
_mysiak_ said:
(some reports say that you even don't need "allow oem unlock" in developer settings, but I haven't tried that).
Click to expand...
Click to collapse
Even this is true for Mi A1 in Nougat and Oreo too. So two critical security omissions by XIAOMI. One must ask himself if it is bug or strange feature
Code:
Developer options / OEM unlocking
Alow the bootloader to be unlocked - option is switched off
C:\>adb devices
List of devices attached
******** device
C:\>adb reboot bootloader
C:\>fastboot devices
******** fastboot
C:\>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.070s]
finished. total time: 0.073s
C:\>fastboot oem unlock
...
OKAY [ 0.153s]
finished. total time: 0.158s
C:\>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.069s]
finished. total time: 0.073s
C:\>fastboot reboot
rebooting...
finished. total time: 0.021s
Developer options / OEM unlocking
Bootloader is already unlocked - option is switched off
C:\>adb devices
List of devices attached
******** device
C:\>adb reboot bootloader
C:\>fastboot devices
******** fastboot
C:\>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.070s]
finished. total time: 0.074s
C:\>fastboot oem lock
...
OKAY [ 0.088s]
finished. total time: 0.091s
C:\>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.070s]
finished. total time: 0.074s
C:\>fastboot reboot
rebooting...
finished. total time: 0.020s
C:\>
_jis_ said:
As an old Nexus user (Nexus 7, Nexus 7 2013, Nexus 5X) I was shocked when I have found this.
Even this is true for Mi A1 in Nougat and Oreo too. So two critical security omissions by XIAOMI. One must ask himself if it is bug or strange feature
Code:
Developer options / OEM unlocking
Alow the bootloader to be unlocked - option is switched off
C:\>adb devices
List of devices attached
******** device
C:\>adb reboot bootloader
C:\>fastboot devices
******** fastboot
C:\>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.070s]
finished. total time: 0.073s
C:\>fastboot oem unlock
...
OKAY [ 0.153s]
finished. total time: 0.158s
C:\>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.069s]
finished. total time: 0.073s
C:\>fastboot reboot
rebooting...
finished. total time: 0.021s
Developer options / OEM unlocking
Bootloader is already unlocked - option is switched off
C:\>adb devices
List of devices attached
******** device
C:\>adb reboot bootloader
C:\>fastboot devices
******** fastboot
C:\>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.070s]
finished. total time: 0.074s
C:\>fastboot oem lock
...
OKAY [ 0.088s]
finished. total time: 0.091s
C:\>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.070s]
finished. total time: 0.074s
C:\>fastboot reboot
rebooting...
finished. total time: 0.020s
C:\>
Click to expand...
Click to collapse
Thanks for the confirmation. I consider it as a serious security flaw and was really surprised as well. I would like to know Xiaomi's reason to do it this way.. Users should be aware that they have to keep data encrypted with good PIN/pattern and request it on each boot to keep information secure.