Database Develop

Moto G 2014 stuck at "warning bootloader unlocked" screen

Ok so i unlocked the bootloader, installed twrp 2.7.1.1, and when i flashed SuperSU.zip file it is stuck on the "warning bootloader unlocked screen." I can get back to the trwp bootloader and clear cache and data, but every time i try to boot to system it stays on the warning bootloader unlocked screen. please help..
running marshmallow 6.0

KyleSaki714 said:
Ok so i unlocked the bootloader, installed twrp 2.7.1.1, and when i flashed SuperSU.zip file it is stuck on the "warning bootloader unlocked screen." I can get back to the trwp bootloader and clear cache and data, but every time i try to boot to system it stays on the warning bootloader unlocked screen. please help..
running marshmallow 6.0
Click to expand...
Click to collapse
You should read the threads about installing custom recoveries and rooting in the general section.
TWRP 2.7.1.1 is wayyy to old, you should use TWRP 3.0.0.0 when you're flashing things in marshmallow.
And you should give more info, which version of superSU did you flash?
There is only one beta version which is able to root marshmallow without a modified Boot.img, it's BETA-SuperSU-v2.62-3-20151211162651.
http://download.chainfire.eu/751/SuperSU/BETA-SuperSU-v2.62-3-20151211162651.zip
Read the thread about "[Simplified] [Root Method] [Titan] [Marshmallow 6.0] Without Modifying boot.img" : http://forum.xda-developers.com/moto-g-2014/general/simplified-modifying-boot-img-t3317605
and "[GUIDE] [Titan] [MM, LP, KK] [Unlock + Root + Backup + Restore + Downgrade" : http://forum.xda-developers.com/moto-g-2014/general/xt1063-t3018818 .
Flash twrp 3.0.0.0 ( https://dl.twrp.me/titan/ )and then the BETA-SuperSU-v2.62-3-20151211162651, you can try to flash the beta superSU above with your old recovery but it's not recommended. Your choice but then change recovery afterwards.
Sent with somewhat

Wolfcity said:
You should read the threads about installing custom recoveries and rooting in the general section.
TWRP 2.7.1.1 is wayyy to old, you should use TWRP 3.0.0.0 when you're flashing things in marshmallow.
And you should give more info, which version of superSU did you flash?
There is only one beta version which is able to root marshmallow without a modified Boot.img, it's BETA-SuperSU-v2.62-3-20151211162651.
http://download.chainfire.eu/751/SuperSU/BETA-SuperSU-v2.62-3-20151211162651.zip
Read the thread about "[Simplified] [Root Method] [Titan] [Marshmallow 6.0] Without Modifying boot.img" : http://forum.xda-developers.com/moto-g-2014/general/simplified-modifying-boot-img-t3317605
and "[GUIDE] [Titan] [MM, LP, KK] [Unlock + Root + Backup + Restore + Downgrade" : http://forum.xda-developers.com/moto-g-2014/general/xt1063-t3018818 .
Flash twrp 3.0.0.0 ( https://dl.twrp.me/titan/ )and then the BETA-SuperSU-v2.62-3-20151211162651, you can try to flash the beta superSU above with your old recovery but it's not recommended. Your choice but then change recovery afterwards.
Sent with somewhat
Click to expand...
Click to collapse
Ok thanks, I did actually find out twrp was an old version so I flashed a lollipop 5.0.2 Titan rom to escape the bootloop, then rooted with Kingroot(I was lazy to install SuperSU) then installed the latest version of twrp.
It's actually my first time attempting rooting and unlocking the bootloader, so yea at least I learned something from this. :good:

KyleSaki714 said:
Ok thanks, I did actually find out twrp was an old version so I flashed a lollipop 5.0.2 Titan rom to escape the bootloop, then rooted with Kingroot(I was lazy to install SuperSU) then installed the latest version of twrp.
It's actually my first time attempting rooting and unlocking the bootloader, so yea at least I learned something from this. :good:
Click to expand...
Click to collapse
Good to hear that you fixed your problem. One thing: Don't use Kingroot.
It's a very unstable way to root your device and a suspicious app.
Just flash superSU, it's stable and easy to do and it doesn't send data to unknown sources. Just an advice.
Sent with somewhat

How to unroot and lock bootloader on OOS 5.0.5?

Is there any alternative method to lock bootloader and unroot the device? I have read other topics that it will required to flash back to 4.0.1 version and install stock recovery.
Possible to have adb lock bootloader and reflash latest OOS 5.0.5 without flashing Magisk module?
Sent from my [device_name] using XDA-Developers Legacy app

Switched last week from Pixel Experience 9.0 (unencrypted) to OOS 5.0.5 and locked the bootloader.
Flashed the latest OOS from TWRP (with all wipes done before);
Waited for the phone to boot OOS 5.0.5 once - without root the TWRP is gone ,replaced with stock recovery;
Rebooted to stock recovery and performed another factory reset;
Waited for the phone to boot OOS 5.0.5 again (to be sure everything it's fine);
Rebooted to bootloader (fastboot) and executed: fastboot oem lock command;
Done!
P.S. - Backup your files before any wipe or bootloader re-lock.

[d]amour said:
Is there any alternative method to lock bootloader and unroot the device? I have read other topics that it will required to flash back to 4.0.1 version and install stock recovery.
Click to expand...
Click to collapse
Do what the previous response says. Just flash the 5.0.5 full zip, reboot to wipe TWRP. Then relock bootloader.
I suspect the only reason the guide you mention, says to flash 4.0.1, is because the guide is old, and 4.0.1 was just the latest version at the time. There isn't any requirement to "downgrade" to an older version, to return to stock/unrooted/locked bootloader.

lesbianu said:
Switched last week from Pixel Experience 9.0 (unencrypted) to OOS 5.0.5 and locked the bootloader.
Flashed the latest OOS from TWRP (with all wipes done before);
Waited for the phone to boot OOS 5.0.5 once - without root the TWRP is gone ,replaced with stock recovery;
Rebooted to stock recovery and performed another factory reset;
Waited for the phone to boot OOS 5.0.5 again (to be sure everything it's fine);
Rebooted to bootloader (fastboot) and executed: fastboot oem lock command;
Done!
P.S. - Backup your files before any wipe or bootloader re-lock.
Click to expand...
Click to collapse
Didn't you face DM-verity warning?
If yes, then how you removed it:-by
"ADB sideload" command or by any other means?
Please specify..........

If I had extra problems, for sure I would warn you about them. No warning, no problem, full stock "like out of the box"!

lesbianu said:
If I had extra problems, for sure I would warn you about them. No warning, no problem, full stock "like out of the box"!
Click to expand...
Click to collapse
As per my knowledge, if you flash oxygen OS OTA without magisk then DM verity flag must be triggered, which only goes by sideloading the same OTA file or updated OTA zip file.

No idea, I told you the steps I made few days ago. They worked for me! Want to believe, good. Don't want to believe, even better.
Was on OOS 5.0.4 (bootloader unlocked), decrypted to test Pixel Experience 9.0 for 2 days and then returned to "full stock" OOS 5.0.5 (bootloader locked) to send the phone in service for upper speaker problems. I know it was not necessary to lock the bootloader, but it was my personal choice.
P.S. - Stop quoting the previous post, it's not necessary.

ersandeepkr said:
As per my knowledge, if you flash oxygen OS OTA without magisk then DM verity flag must be triggered, which only goes by sideloading the same OTA file or updated OTA zip file.
Click to expand...
Click to collapse
DM verity is triggered when changes are made to the system/kernel. If you flash a stock OTA file (with no Magisk or other changes) then DM verity is not triggered. Maybe it will be triggered when TWRP is still on the device (not 100% on that), but that will be taken care of when TWRP is overwritten.
You can sideload the OTA as described on the OnePlus website, if you like. But I don't think the result will be any different.

Global Stable 10.0.3.0 and TWRP Encryption

Hello guys. Yesterday ( October 30th) I had a notification about upgrading from 10.0.2.0 to 10.0.3.0. I was rooted with Magisk, and after the update the root privileges were gone. I tried to boot to TWRP again, but it stays encrypted without asking for password as usual, so I am unable to flash the zip and root again. Is it ok if I use the boot.img in order to install via patched_boot?As for now there isn't 10.0.3.0 firmware available for download in order to extract it. Thank you for your time.

I am also interested about update with Magisk

GeorgeKatsi said:
Hello guys. Yesterday ( October 30th) I had a notification about upgrading from 10.0.2.0 to 10.0.3.0. I was rooted with Magisk, and after the update the root privileges were gone. I tried to boot to TWRP again, but it stays encrypted without asking for password as usual, so I am unable to flash the zip and root again. Is it ok if I use the boot.img in order to install via patched_boot?As for now there isn't 10.0.3.0 firmware available for download in order to extract it. Thank you for your time.
Click to expand...
Click to collapse
You can flash patched_boot to get the TEMP magisk working before the new twrp available for 10.0.3.0
Code:
fastboot boot patched_boot.img
The boot image can be patched via magisk by yourself or you can use mine from 20181104_mi8_10.0.3.0_patched_boot.img
Remember this TEMP solution fails after rebooting. Or you fastboot boot patched_boot.img every rebooting.

Hello ich have the Same Problem, can U Tell step by step how to do that?
Ich want to flash custom Rom

same issue im on miui.eu 10.0.8.0 with encryption enabled.
Booting into recovery TWRP does not ask for passcode to decrypt data

mikefallen said:
same issue im on miui.eu 10.0.8.0 with encryption enabled.
Booting into recovery TWRP does not ask for passcode to decrypt data
Click to expand...
Click to collapse
I flashed the patched_boot made by magisk, but I am still unable to decrypt twrp. I hope they support 10.0.3.0 soon so I can use twrp again.

Few questions regarding rooting and flashing.

Hello XDA fam, I just picked up a 3T and unlocked the bootloader.
I was just wondering what the general flashing process was for this
device (A3000). Also a tad confused about this dm-verity ...
disabler zip, is this and format data required every time you flash a
new ROM?

MoistPicklez said:
Hello XDA fam, I just picked up a 3T and unlocked the bootloader.
I was just wondering what the general flashing process was for this
device (A3000). Also a tad confused about this dm-verity ...
disabler zip, is this and format data required every time you flash a
new ROM?
Click to expand...
Click to collapse
Dm-verity warnings are similar to the unlocked bootloader screen you get, but are red. You get them if you are running stock OOS and modify the system partition.
You don't need the dm-verity disabler unless you've got a dm-verity warnings screen.
Note that you cannot disable the unlocked bootloader warning you get every time the phone boots except by re-locking the phone.
Another thing to note: if you are running stock OOS and flash TWRP, then TWRP will be replaced by the stock recovery when your reboot the phone unless you:
- use a patched boot image like the one from @Xennet's thread https://forum.xda-developers.com/oneplus-3t/how-to/dm-verity-disable-oxygen-os-t3922324/post79357241
- use a custom kernel, or
- use Magisk.
Flashing using TWRP is just like any other phone. If you're changing ROMs then you need to do a clean install (wipe /data and/system).
Some ROMs don't handle an encrypted phone (most Android 10 ones except for Los and PE), so you you have to remove the encryption before using those ROMs (TWRP>wipe>format data).
Finally if your phone is unlocked and running OOS 5.x or lower, and you want to upgrade to OOS 9.x then you'll either have to:
- remove the encryption (but can re-encrypt after installing 9.x) or
- use the modded firmware (that keeps the 5.x bootloader and keys) so that you don't have to remove the encryption. See https://forum.xda-developers.com/on...-5-0-8-firmware-barrier-t3941164/post79758055
Sent from my OnePlus3T using XDA Labs

BillGoss said:
Dm-verity warnings are similar to the unlocked bootloader screen you get, but are red. You get them if you are running stock OOS and modify the system partition.
You don't need the dm-verity disabler unless you've got a dm-verity warnings screen.
Note that you cannot disable the unlocked bootloader warning you get every time the phone boots except by re-locking the phone.
Another thing to note: if you are running stock OOS and flash TWRP, then TWRP will be replaced by the stock recovery when your reboot the phone unless you:
- use a patched boot image like the one from @Xennet's thread https://forum.xda-developers.com/oneplus-3t/how-to/dm-verity-disable-oxygen-os-t3922324/post79357241
- use a custom kernel, or
- use Magisk.
Flashing using TWRP is just like any other phone. If you're changing ROMs then you need to do a clean install (wipe /data and/system).
Some ROMs don't handle an encrypted phone (most Android 10 ones except for Los and PE), so you you have to remove the encryption before using those ROMs (TWRP>wipe>format data).
Finally if your phone is unlocked and running OOS 5.x or lower, and you want to upgrade to OOS 9.x then you'll either have to:
- remove the encryption (but can re-encrypt after installing 9.x) or
- use the modded firmware (that keeps the 5.x bootloader and keys) so that you don't have to remove the encryption. See https://forum.xda-developers.com/on...-5-0-8-firmware-barrier-t3941164/post79758055
Click to expand...
Click to collapse
Wow thank you for the detailed info, I really appreciate the insight.
I am currently running the latest OOS update 9.0.6 I believe.
Once I have TWRP installed do I swipe and enable modifications?
Flashing Magisk afterwards avoids the bootloop and allows me to
keep TWRP in place of the stock recovery as you said, correct?
So installing most ROMs seems fairly straightforward, following
the flashing instructions. However if I were to install an Android
10 ROM wouldn't formatting data remove all zips and everything
from the internal storage? So at that point I'd have to copy back
all my ROMs and zips back to the phone in TWRP and flash from
this point correct?
Sorry for the loads of questions, my most recent device was a
Note 9, which has a locked bootloader, so it has been a while since
I have flashed anything or used TWRP.

MoistPicklez said:
Wow thank you for the detailed info, I really appreciate the insight.
I am currently running the latest OOS update 9.0.6 I believe.
Once I have TWRP installed do I swipe and enable modifications?
Flashing Magisk afterwards avoids the bootloop and allows me to
keep TWRP in place of the stock recovery as you said, correct?
Click to expand...
Click to collapse
You don't need you enable modifications of the system partition. Any zip you flash will make the system writable if required.
So, just flash Magisk.
MoistPicklez said:
So installing most ROMs seems fairly straightforward, following the flashing instructions. However if I were to install an Android
10 ROM wouldn't formatting data remove all zips and everything from the internal storage? So at that point I'd have to copy back all my ROMs and zips back to the phone in TWRP and flash from this point correct?
Click to expand...
Click to collapse
Correct. So it's best to take a backup of your current system and backing up everything on internal storage (/sdcard) to an external drive or PC.
The fastest way to take the backup is to use ADB.
Code:
adb pull /sdcard
MoistPicklez said:
Sorry for the loads of questions, my most recent device was a
Note 9, which has a locked bootloader, so it has been a while since
I have flashed anything or used TWRP.
Click to expand...
Click to collapse
You'll find that nearly all the rom, kernel, and recovery development threads are under the OnePlus 3 forum in https://forum.xda-developers.com/oneplus-3/oneplus-3--3t-cross-device-development as they are unified: good to flash on both the 3 and 3T.
Sent from my OnePlus3T using XDA Labs

BillGoss said:
You don't need you enable modifications of the system partition. Any zip you flash will make the system writable if required.
So, just flash Magisk.
Correct. So it's best to take a backup of your current system and backing up everything on internal storage (/sdcard) to an external drive or PC.
The fastest way to take the backup is to use ADB.
You'll find that nearly all the rom, kernel, and recovery development threads are under the OnePlus 3 forum in https://forum.xda-developers.com/oneplus-3/oneplus-3--3t-cross-device-development as they are unified: good to flash on both the 3 and 3T.
Click to expand...
Click to collapse
Awesome info, big thanks to you my good sir. Finally
on Havoc 2.9 and decrypted. Now just gotta get a feel
for this phone and keep on reading. Cheers!

Switch from LOS recovery to TWRP

Hello everybody,
I'm little outdated on Android things, so please excuse my stupid questions. But I want to be sure my process is OK.
I was on LOS 16.1 / TWRP / superSU and updated to 17.1 / LOS recovery / Magisk. After a LOS Update I noticed that I have no more root. I wanted to install Magisk root again via recovery and noticed I can't do that from LOS recovery. Is that normal?
To get back root my plan is to flash again TWRP (https://androidfilehost.com/?fid=4349826312261695823), so I am again able to flash the magisk zip. Will this process keep my data an ROM as it is before? Is there any disadvantage? LOS recommends the LOS recovery. That's because I installed it...
Thanks a lot for your help!

dbsoundz said:
Hello everybody,
I'm little outdated on Android things, so please excuse my stupid questions. But I want to be sure my process is OK.
I was on LOS 16.1 / TWRP / superSU and updated to 17.1 / LOS recovery / Magisk. After a LOS Update I noticed that I have no more root. I wanted to install Magisk root again via recovery and noticed I can't do that from LOS recovery. Is that normal?
To get back root my plan is to flash again TWRP (https://androidfilehost.com/?fid=4349826312261695823), so I am again able to flash the magisk zip. Will this process keep my data an ROM as it is before? Is there any disadvantage? LOS recommends the LOS recovery. That's because I installed it...
Thanks a lot for your help!
Click to expand...
Click to collapse
what is your current setup? as long as you have OEM unlock,unlocked boot loader., you can just flash TWRP via ADB followed by magisk in general

Muralidharc22 said:
what is your current setup? as long as you have OEM unlock,unlocked boot loader., you can just flash TWRP via ADB followed by magisk in general
Click to expand...
Click to collapse
Hello and thanks for your answer. Yes, it's OEM unlocked and unlocked boot loader. It's encrypted. But encryption shouldn't be a problem for that.

Thanks, Muralidharc22. All done!