Database Users

Locked bootloader & No OS | What could be done?

Hi all,
I'd been using my rooted Nexus 6P on stock ROM+kernel. Unfortunately, I locked the bootloader after installing TWRP and installing SuperSU. I know, it was a huge mistake but it happened.
Yesterday I wanted to unroot and factory reset the phone. I forgot that my bootloader was locked so I didn't flick that "enable oem unlocking" button. I tried "flash-all" directly on bootloader. Obviously it didn't work and after reboot it got stuck on Google screen. I waited for a while but nothing happened. I wiped system, vendor, cache... etc on TWRP upon a tutorial in this forum with the intention to flash stock ROM but again : my bootloader was locked.
Now, I can still use TWRP and push files through adb but cannot use any fastboot commands. I get this error:
Code:
FAILED (remote: device is locked. Cannot flash images)
I tried installing the whole "image-angler-mdb08l" on TWRP but I get this error:
Code:
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled
Installing '/sdcard/image-angler-mdb08l.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
E:Could not find 'META-INF/com/google/android/update-binary' in the zip file.
Error flashing zip image-angler-mdb08l.zip'
Updating partition details...
...done
Is there any way to flash stock ROM with TWRP or should I try flashing a custom ROM and hoping to boot so I can enable that troublesome OEM unlock switch?
Compared to similar situations in 6P forum, I have the advantage of working adb and TWRP but I don't know if they even make a difference. Thanks for sparing time to read and your help.

You cannot flash factory image with TWRP. Download any custom ROM, flash it with TWRP. Let it boot and enable unlock in Developer Options.

Witek_M said:
You cannot flash factory image with TWRP. Download any custom ROM, flash it with TWRP. Let it boot and enable unlock in Developer Options.
Click to expand...
Click to collapse
You restored my faith in saving this phone. Is there any custom ROM in particular that won't mess with the recovery partition? It seems that if I loose TWRP, I have nothing to hold on to.

afaruky said:
You restored my faith in saving this phone. Is there any custom ROM in particular that won't mess with the recovery partition? It seems that if I loose TWRP, I have nothing to hold on to.
Click to expand...
Click to collapse
I believe that CyanogenMod wouldn't corrupt TWRP recovery. I've flashed official CM on my Galaxy S4 so many times, and CM never replace TWRP with something else. ????

LeoYL said:
I believe that CyanogenMod wouldn't corrupt TWRP recovery. I've flashed official CM on my Galaxy S4 so many times, and CM never replace TWRP with something else. ????
Click to expand...
Click to collapse
:victory: It worked like a charm. Thanks a lot. :victory:

afaruky said:
:victory: It worked like a charm. Thanks a lot. :victory:
Click to expand...
Click to collapse
Now unlock the bootloader, and leave it unlocked.

afaruky said:
:victory: It worked like a charm. Thanks a lot. :victory:
Click to expand...
Click to collapse
metaphz said:
Now unlock the bootloader, and leave it unlocked.
Click to expand...
Click to collapse
And maybe bookmark my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
A bit of research and knowledge would have avoided this issue in the first place.

Heisenberg said:
And maybe bookmark my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
A bit of research and knowledge would have avoided this issue in the first place.
Click to expand...
Click to collapse
Your guide is amazing and helped a lot.
I had been using N5 with locked bootloader and never encountered any problem but when I switched to 6P I read some articles explaining how dangerous leaving the bootloader unlocked is, so I locked it. Obviously, it was a mistake. I'm glad I didn't have to RMA.

afaruky said:
Your guide is amazing and helped a lot.
I had been using N5 with locked bootloader and never encountered any problem but when I switched to 6P I read some articles explaining how dangerous leaving the bootloader unlocked is, so I locked it. Obviously, it was a mistake. I'm glad I didn't have to RMA.
Click to expand...
Click to collapse
There is risk in involved in having an unlocked bootloader, but as long as you take care of your phone and don't let it fall into the wrong hands you'll be perfectly fine. To say it's dangerous would be a pretty big overstatement.

I'm in the same situation, need some help
Sent from my GT-I9500 using Tapatalk
---------- Post added at 02:30 PM ---------- Previous post was at 02:29 PM ----------
I have twrp working fine with no os
Sent from my GT-I9500 using Tapatalk

So why not do exactly what the OP did? Download a custom ROM, flash it with TWRP then unlock your bootloader?

Pain-N-Panic said:
So why not do exactly what the OP did? Download a custom ROM, flash it with TWRP then unlock your bootloader?
Click to expand...
Click to collapse
Its not connecting to bootloader to transfer custom rom.
Sent from my GT-I9500 using Tapatalk

[GUIDE] [OSPREY] [MM] 【6.0/6.0.1】Install TWRP, Root and Xposed successfully on 6.0

[GUIDE] [OSPREY] [MM] 【6.0/6.0.1】Install TWRP, Root and Xposed successfully on 6.0
1) Unlock your bootloader . for complete unlocking process go here.
https://m.youtube.com/watch?v=sw675ipX-ds&feature=youtu.be
IT WILL RESET ALL YOUR DATA.
2) Turn on USB debugging on
3) Boot your device into bootloader mode
4) flash TWRP recovery v2.8.7 r5. http://forum.xda-developers.com/devdb/project/?id=11051#downloads
5) Boot into TWRP recovery
6) Flash supersu zip v2.62-3. http://download.chainfire.eu/751/SuperSU/BETA-SuperSU-v2.62-3-20151211162651.zip
7) After succsesfull flashing wipe cache/dalvik cache . reboot system. If it asks to install Root. DO NOT INSTALL ROOT AT THIS STAGE.
8) wait till Boot finishes.
9) If you want to install Xposed Boot into TWRP recovery.
10) Flash Xposed installer xposed-v79-sdk23-arm.zip. http://forum.xda-developers.com/showthread.php?t=3034811.
Thanks for contributors of TWRP, Supersu and Xposed.

I am G-Root...ed
Thanks man!, being trying a lot with no succes... till now... Excelent Work :good:

abhijeetc9762 said:
1) Turn on USB ) .
Click to expand...
Click to collapse
do we have twrp for moto g turbo?

The phone has to have the bootloader unlocked?
The whole thing will completely reset the device?

abhijeetc9762 said:
3) flash TWRP recovery v2.8.7 r5.
Click to expand...
Click to collapse
Will this work without flashing TWRP? Can I just boot TWRP using fastboot, then flash SuperSU 2.62-3 and reboot? In that way, after reboot it will be system recovery and as SuperSU 2.62-3 is a systemless root, there won't be any modification in /system. Thus, I can receive OTA updates in future directly.
Did anybody try this with XT1550?

soumyajit_nayak said:
Will this work without flashing TWRP? Can I just boot TWRP using fastboot, then flash SuperSU 2.62-3 and reboot? In that way, after reboot it will be system recovery and as SuperSU 2.62-3 is a systemless root, there won't be any modification in /system. Thus, I can receive OTA updates in future directly.
Did anybody try this with XT1550?
Click to expand...
Click to collapse
You don't have chance anyway after rooting. You have to have Flash the firmware again to receive OTA
Sent from my MotoG3 using XDA Premium 4 mobile app

soumyajit_nayak said:
Will this work without flashing TWRP? Can I just boot TWRP using fastboot, then flash SuperSU 2.62-3 and reboot? In that way, after reboot it will be system recovery and as SuperSU 2.62-3 is a systemless root, there won't be any modification in /system. Thus, I can receive OTA updates in future directly.
Did anybody try this with XT1550?
Click to expand...
Click to collapse
Yes, you can do it that way, I've done it several times. Like someone said though, it's simpler to just flash TWRP and be done with it rather than wait for OTA's that you probably can't flash anyway.

Tel864 said:
Yes, you can do it that way, I've done it several times. Like someone said though, it's simpler to just flash TWRP and be done with it rather than wait for OTA's that you probably can't flash anyway.
Click to expand...
Click to collapse
In an earlier post you indicated that you can simply do a full unroot with SuperSU and receive OTA updates. Did that only apply to 5.1.1 and not 6.0?
Tel864 said:
I was able to d/l the update, but had to unroot to install the update. If you're using SuperSU to root, it's a simple matter to use the SuperSU app and do a full unroot, then just root again after the update.
Click to expand...
Click to collapse

Kakaroth89 said:
The phone has to have the bootloader unlocked?
The whole thing will completely reset the device?
Click to expand...
Click to collapse
Same question. Coming from a Nexus 4 phone, it was necessary to unlock the bootloader first. According to the instructions here, that is unnecessary?
EDIT (01-20-2016): Thanks for adding the missing unlock bootloader step to the instructions. I just ordered a Moto G yesterday.

pjc123 said:
Same question. Coming from a Nexus phone, it was necessary to unlock the bootloader first. According to the instructions here, that is unnecessary?
Click to expand...
Click to collapse
To root you will need an unlocked bootloader.

Any one?
Rooted xt1550 with supersu 2.62 and then deleted moto bloatware, now phone stuck on black screen after rebooting. Any help abt deleting bloatware?

Seems fine..but
just done this and boot up looks normal but seems forever to boot up. It has not boot up yet, what is the estimated time to wait?

Does it matter if TWRP is configured as "Read Only" or not?

Tel864 said:
To root you will need an unlocked bootloader.
Click to expand...
Click to collapse
And this procedure will do a factory reset?
I mean all the procedure, not just unlocking the bootloader

Kakaroth89 said:
And this procedure will do a factory reset?
I mean all the procedure, not just unlocking the bootloader
Click to expand...
Click to collapse
No, all your data and apps will still be there.

Tel864 said:
No, all your data and apps will still be there.
Click to expand...
Click to collapse
I lost all apps and data when I unlocked bootloader.. I did not unlock until after the 6.0 upgrade.

MrTooPhone said:
Does it matter if TWRP is configured as "Read Only" or not?
Click to expand...
Click to collapse
Do no tick as read only.
Sent from my MotoG3 using XDA Premium 4 mobile app

OP updated for bootloader unlocking procedure
Sent from my MotoG3 using XDA Premium 4 mobile app

abhijeetc9762 said:
5) Boot into TWRP recovery
Click to expand...
Click to collapse
@abhijeetc Excellent instructions. One recommendation is to address the issue with the "read only" TWRP option. I am sometimes presented with this option during TWRP boot (not sure why this option is not presented every time since I never check "don't show again"). I am not sure if "read only" makes a difference or not. But I can confirm I was soft bricked after enabling read only and flashing 2.66. I did not wipe Dalvik/Cache either. I was successful with 2.62-3 but was not presented "read only" option either. Also, you may want to recommend a Nandroid back up prior to any attempt flashing root. Just a recommendation.

I notice under developer settings (tap Build Number a bunch of times in the "About Phone" section to access developer mode) it has the option "OEM unlocking - Allow bootloader to be unlocked" as an option. Does that make this process any easier or is it necessary? I bought my phone straight from motomaker.

Secure Boot Error after trying to install TWRP

Hi. I was trying to install Cyanogenmod on my LG Leon. First, I rooted my phone using KingRoot and then replaced it with SuperSU. Then, I proceeded to install TWRP. But, because I was installing it my first time in my life, I made a mistake and tried do install it using TWRP Manager, without doing a backup of the stock recovery. After rebooting, secure boot error popped up and I had to take out the battery. Now whatever I do I cannot do anything custom rom related. Do you have any hints?

bokjezd said:
Hi. I was trying to install Cyanogenmod on my LG Leon. First, I rooted my phone using KingRoot and then replaced it with SuperSU. Then, I proceeded to install TWRP. But, because I was installing it my first time in my life, I made a mistake and tried do install it using TWRP Manager, without doing a backup of the stock recovery. After rebooting, secure boot error popped up and I had to take out the battery. Now whatever I do I cannot do anything custom rom related. Do you have any hints?
Click to expand...
Click to collapse
You have to enable OEM unlock in Developer Options to prevent the secure boot error, then flash the recovery using Flashify and reboot.

adefesio said:
You have to enable OEM unlock in Developer Options to prevent the secure boot error
Click to expand...
Click to collapse
I already found an advise like this, but I still cannot find that option. I think I have a little bit too old android. Do you know in which version of android it was introduced? I have 5.0.1. Maybe there is another hidden switch simular to the one enabling developer options used to enable OEM unlock?

bokjezd said:
I already found an advise like this, but I still cannot find that option. I think I have a little bit too old android. Do you know in which version of android it was introduced? I have 5.0.1. Maybe there is another hidden switch simular to the one enabling developer options used to enable OEM unlock?
Click to expand...
Click to collapse
Check if there's a software upgrade available from your provider. I can also suggest flashing back the original stock recovery image. Let me know if you need a download link. Which variant is your Leon?

adefesio said:
Check if there's a software upgrade available from your provider. I can also suggest flashing back the original stock recovery image. Let me know if you need a download link. Which variant is your Leon?
Click to expand...
Click to collapse
Yes, there is an update but currently I can't do it because updating reboots to recovery to update something. I would really like to flash back the original recovery, but I don't have the image, so can I have the link, please? My Leon is LG H340n.

bokjezd said:
Yes, there is an update but currently I can't do it because updating reboots to recovery to update something. I would really like to flash back the original recovery, but I don't have the image, so can I have the link, please? My Leon is LG H340n.
Click to expand...
Click to collapse
I am sending a private message with the link. Let me know if it works.

adefesio said:
I am sending a private message with the link. Let me know if it works.
Click to expand...
Click to collapse
Thanks, it seems to work now, but it refuses to update because it detects root. Is there a way to hide it or do I have to do a full unroot? I already tried the "Hide my Root" app.
Edit: Never mind, I will just do the unroot and then update.

Ok, I've downloaded recovery-H340N.img, but when I try to update, it shows that updating screen and then error 0x1125000 pops up. The phone reboots and then it tells me it detected root, however I did a full unroot... Do you know what that error means? And how does LG check for the root?

bokjezd said:
Ok, I've downloaded recovery-H340N.img, but when I try to update, it shows that updating screen and then error 0x1125000 pops up. The phone reboots and then it tells me it detected root, however I did a full unroot... Do you know what that error means? And how does LG check for the root?
Click to expand...
Click to collapse
Reset to factory settings, do the update, root with Kingroot (DON'T replace with SuperSU), restart, enable OEM unlock, install TWRP using Flashify.

adefesio said:
Reset to factory settings, do the update, root, enable OEM unlock, install TWRP using Flashify.
Click to expand...
Click to collapse
Wait, I need to do a backup of all my data, right?

bokjezd said:
Wait, I need to do a backup of all my data, right?
Click to expand...
Click to collapse
Google backs up most of your data, but not all. If you know other ways then do it.
---------- Post added at 03:53 PM ---------- Previous post was at 03:49 PM ----------
Google backs up most of your data but not all. If you know other ways then do it, then:
Reset to factory settings, do the update, root with Kingroot (DON'T replace with SuperSU), restart, enable OEM unlock, install TWRP using Flashify.

adefesio said:
Google backs up most of your data, but not all. If you know other ways then do it.
---------- Post added at 03:53 PM ---------- Previous post was at 03:49 PM ----------
Google backs up most of your data but not all. If you know other ways then do it, then:
Reset to factory settings, do the update, root with Kingroot (DON'T replace with SuperSU), restart, enable OEM unlock, install TWRP using Flashify.
Click to expand...
Click to collapse
I've reset my phone to factory settings, but it still refuses to update with error code 0x1125000 and after rebooting to home screen it says it detected root. I think I'm gonna update with LG Mobile Support Tool.

Wait, does my mobile operator affect what recovery should I flash? If yes, it is P4, often referred to as PLAY. Or maybe I should also flash the boot image you've sent to me? My PC doesn't detect my phone, so I have to repair the updates...

bokjezd said:
Wait, does my mobile operator affect what recovery should I flash? If yes, it is P4, often referred to as PLAY. Or maybe I should also flash the boot image you've sent to me? My PC doesn't detect my phone, so I have to repair the updates...
Click to expand...
Click to collapse
Too many complications. Just reflash the entire ROM with the most recent kdz. Root with Kingroot and don't replace it with SU. You know the rest.

Still nothing. Now it says it's the newest software available, but I cannot find that oem unlock. Are you sure it's available on Leon? I've read some manufacturers remove it...

How to fix DM-VERITY issue for 7.0 flashed updates

Here is how you fix it.
Step 1. download OnePlus3t toolkit (note: don't attach the phone to PC yet)
step 2. reboot your phone into bootloader (if in twrp hit restart -> bootloader) if not in twrp try turning phone on and as you see the oem unlock screen hit volume up and down and choose fastboot (or bootloader)
step 3. open oneplus3t toolkit
step 4. choose option 8 (flash stock recovery)
step 5. hit enter and when it says waiting 4 devices attach your device to pc
step 6. let it finish
step 7. when recovery comes up, hold power button for 10 seconds or hit exit (if you can choose it) and reboot into system
step 8. if it keeps rebooting into a stock recovery and you cant decrypt... then when your phone first boots and goes into oem-unlock error hit volume up and click restart.
step 9. Reflash TWRP and SuperSU if needed
Step 10. Enjoy!

Did not work for me. Stock recovery, stock nougat, locked bootloader and I still have dm-verity error.

Skwerl23 said:
Here is how you fix it.
Step 1. download OnePlus3t toolkit (note: don't attach the phone to PC yet)
step 2. reboot your phone into bootloader (if in twrp hit restart -> bootloader) if not in twrp try turning phone on and as you see the oem unlock screen hit volume up and down and choose fastboot (or bootloader)
step 3. open oneplus3t toolkit
step 4. choose option 8 (flash stock recovery)
step 5. hit enter and when it says waiting 4 devices attach your device to pc
step 6. let it finish
step 7. when recovery comes up, hold power button for 10 seconds or hit exit (if you can choose it) and reboot into system
step 8. if it keeps rebooting into a stock recovery and you cant decrypt... then when your phone first boots and goes into oem-unlock error hit volume up and click restart.
step 9. enjoy!
Click to expand...
Click to collapse
Can TWRP be installed afterwards or will it come back when TWRP is installed?

Michalko5896 said:
Did not work for me. Stock recovery, stock nougat, locked bootloader and I still have dm-verity error.
Click to expand...
Click to collapse
Try flashing TWRP and back to stock recovery.
If all keeps happening you may need to follow the guide to unbrick the phone.
I'd personally keep flashing different things if data is important. Sorry to hear this happened. Sounds like dm-verity should never have been a thing. So frustrating. Please update us on what you find. You can always erase system and all then reflash image.

Skwerl23 said:
Try flashing TWRP and back to stock recovery.
If all keeps happening you may need to follow the guide to unbrick the phone.
I'd personally keep flashing different things if data is important. Sorry to hear this happened. Sounds like dm-verity should never have been a thing. So frustrating. Please update us on what you find. You can always erase system and all then reflash image.
Click to expand...
Click to collapse
I have tried everything. DM-verity error every fricking time.. Tbh, I really hate oneplus. They are not releasing factory images, with factory images I could fix every issue in 5 minutes.

I feel your frustration. There is this forum
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306

Michalko5896 said:
I have tried everything. DM-verity error every fricking time.. Tbh, I really hate oneplus. They are not releasing factory images, with factory images I could fix every issue in 5 minutes.
Click to expand...
Click to collapse
Go to TWRP>Wipe>Advanced Wipe>Select system>Repair or change file system>Change filesystem>EXT4>Flash your ROM
That fixed it for me

Michalko5896 said:
I have tried everything. DM-verity error every fricking time.. Tbh, I really hate oneplus. They are not releasing factory images, with factory images I could fix every issue in 5 minutes.
Click to expand...
Click to collapse
I used the hard brick fix to go back to 3.5.1? I let the system update to 3.5.4. Go into developer settings and check allow oem unlock. Went into bootloader and oem unlocked. It will erase everything. Downloaded and put the OTA patch(940gb~not full) and supersu 2.79 on the device somewhere and did a local update with the patch through stock recovery. Went into bootloader and flashed TWRP 3.0.2.0(not 3.0.3.0). Do not exit bootloader. In bootloader I fastboot BOOT the 3.0.2.0 TWRP(3.0.3.0 would not boot up and screwed the dm-verity). If it(3.0.2.0) doesn't want to boot then quickly hold the power button in and wait till it starts rebooting and go into recovery menu option). Swipe to allow modifications and flash the supersu 2.79 that was placed on the device somewhere. This worked for me and no dm-verity error with f2fs.
Long process but it worked.

does dm-verity error mean anything? I have it also currently but nougat seems to be running fine...

PaKii94 said:
does dm-verity error mean anything? I have it also currently but nougat seems to be running fine...
Click to expand...
Click to collapse
https://source.android.com/security/verifiedboot/
In a nutshell, extra security on the boot partition to "ensure chain of trust" one of the possible requirements for Android Pay backend.
********EDIT***********
This method didn't work on the newest beta, and the OP3T ToolKit way has never worked for me on any version of OOS.

card13 said:
https://source.android.com/security/verifiedboot/
In a nutshell, extra security on the boot partition to "ensure chain of trust" one of the possible requirements for Android Pay backend.
********EDIT***********
This method didn't work on the newest beta, and the OP3T ToolKit way has never worked for me on any version of OOS.
Click to expand...
Click to collapse
I see thanks. I guess it doesn't matter to me cause I haven't started using android Pay and since I'm rooted currently

What causes the dm-verity issue in the first place?

guys if my device is unlocked will i still get the ota updates?
how about root ? if my device rooted willi still get ota updates?

saberzaid said:
guys if my device is unlocked will i still get the ota updates?
how about root ? if my device rooted willi still get ota updates?
Click to expand...
Click to collapse
Yes to first. No to second, It will try but will fail.
Sent from my ONEPLUS A3000 using Tapatalk

Mine is unlocked and rooted. The update failed. Then it redownloaded the full 1.4gb. That's how I found the URL. Then it flashed fine but brought recovery to stock and wiped root. Had to use the toolkit to get TWRP and root back.
So yes, even rooted gets the update

noahvt said:
Go to TWRP>Wipe>Advanced Wipe>Select system>Repair or change file system>Change filesystem>EXT4>Flash your ROM
That fixed it for me
Click to expand...
Click to collapse
I did a system restore previously and it set system to ext4. Maybe that's why I didn't have issues.
This dm-verity issue could be showing the instability of f2fs. Hmmm

Hello, just reset original rom under 6.0.1 and the problems and then twrp then flash rom custom

jejemc said:
Hello, just reset original rom under 6.0.1 and the problems and then twrp then flash rom custom
Click to expand...
Click to collapse
Hi guy, I followed your instruction, however, it still has the problem.
When I use the stock recovery to flash the beta1 package, it could not be flashed in.

lanbingxuanyi said:
Hi guy, I followed your instruction, however, it still has the problem.
When I use the stock recovery to flash the beta1 package, it could not be flashed in.
Click to expand...
Click to collapse
Hello, I am going under the beta with the message in red dm-verity for the removed I returned under original rom then I handed twrp then rom custom

card13 said:
https://source.android.com/security/verifiedboot/
In a nutshell, extra security on the boot partition to "ensure chain of trust" one of the possible requirements for Android Pay backend.
********EDIT***********
This method didn't work on the newest beta, and the OP3T ToolKit way has never worked for me on any version of OOS.
Click to expand...
Click to collapse
PaKii94 said:
I see thanks. I guess it doesn't matter to me cause I haven't started using android Pay and since I'm rooted currently
Click to expand...
Click to collapse
I'm running 7.0 stable, unlocked bootloader and dm-verity warning. Android Pay still functions with the workaround.

Unable to install OTA after rootless pixel camera install

Hello,
A while back I enabled camera2 api and Eis via
https://forum.xda-developers.com/showpost.php?p=75541654&postcount=98
This method.
Only difference in method was that I could not use ADB shell while in twrp (device not detected) so I used the console available in twrp. (I booted from twrp, did not flash it.)
Now I can not install my February OTA. (bootloader is locked)
It downloads but while installing it gives me error. (couldn't update, installation error)
What am I doing wrong?
More info: Ever since I did above process, it asks me for pattern every time I reboot. I think this is related to the issue.

Only difference in method was that I could not use ADB shell while in twrp (device not detected) so I used the console available in twrp. (I booted from twrp, did not flash it.)
Click to expand...
Click to collapse
This is the problem, if you touch your phone in twrp the ota will fail
Boot into twrp. (don't touch the phone in twrp).
Click to expand...
Click to collapse

bobbyfarrell66 said:
This is the problem, if you touch your phone in twrp the ota will fail
Click to expand...
Click to collapse
Well it was not being detected in adb or fastboot. The phone just sat there and nothing happened.
So I had to do it using manual method.
What is the reason behind if I touch during twrp it won't work?
Is there any way to reverse it?

When twrp boot if you "swipe to allow modifications" OTA will fail
You have to use Miflash to restore your mi A1 :good:

bobbyfarrell66 said:
When twrp boot if you "swipe to allow modifications" OTA will fail
You have to use Miflash to restore your mi A1 :good:
Click to expand...
Click to collapse
That's too bad, never worked with stock roms before.
Does mi flash tool allow reflash without losing data?
Also what to do when pc is not detecting phone in adb mode when booted in twrp in above method?

I have to enter pin at boot now as well after installing Gcam, but I was able to update to Feb no problems.

xeltos said:
Hello,
A while back I enabled camera2 api and Eis via
https://forum.xda-developers.com/showpost.php?p=75541654&postcount=98
This method.
Only difference in method was that I could not use ADB shell while in twrp (device not detected) so I used the console available in twrp. (I booted from twrp, did not flash it.)
Now I can not install my February OTA. (bootloader is locked)
It downloads but while installing it gives me error. (couldn't update, installation error)
What am I doing wrong?
More info: Ever since I did above process, it asks me for pattern every time I reboot. I think this is related to the issue.
Click to expand...
Click to collapse
I m facing the same problem. is it for installations of gcam or unlocking bootloader? is there any solution to update normally

i am also facing same ,but some of my friends used the tool to install gcam and their ota updates were successful so i think its the manual method which is the problem

Flash using mi flash.
Theres option for save user data if you dont want to lose anything. Now you can update.
And gcam also work after that..

blackxmafia said:
Flash using mi flash.
Theres option for save user data if you dont want to lose anything. Now you can update.
And gcam also work after that..
Click to expand...
Click to collapse
Have u tried this? because I already did this, installed entire rom without wiping anything.But no use again same problem for ota

25vikasp said:
Have u tried this? because I already did this, installed entire rom without wiping anything.But no use again same problem for ota
Click to expand...
Click to collapse
Yeah tried it already..
Problem fixed

I am. Also facing the same issue. I accidently allowed modification while installing gcam. And now the bootloader is unlocked. And installation of ota fails every time I do it. Please help me out of it. Will relocking the bootloader help?? Or resetting phone to factory settings relock the bootloader and ota will be installed??