Related
I am not very good at making good step by step instructions but Lots of others are.
Here are the steps that I used.
Unlock bootloader via normal means
Flash chainfire boot img from here
Flash Twrp
Boot into Twrp and click mount and mount /system/
ADB Push supersu Zip file to /system/
Twrp install SuperSu.zip
Reboot
Profit
Are you sure you're encrypted? What's it say under security in your settings under encryption? I assumed that kernel you flashed disabled the automatic encryption. Or did that just allow you to disable it later?
Hi
Evo_Shift said:
Are you sure you're encrypted? What's it say under security in your settings under encryption? I assumed that kernel you flashed disabled the automatic encryption. Or did that just allow you to disable it later?
Click to expand...
Click to collapse
Wish I tried that first, turned off encryption now, although could re-encrypt.
Yes this should work. TWRP doesn't support decryption, which means any files copied to the phones user storage that we might want to install by TWRP (such as SuperSU), can't be seen by TWRP, as it can't decrypt the user data, so it can't be installed from recovery.
However, the system partition isn't encrypted, so pushing a file to the system, will allow TWRP to read it and install SuperSU. Of course you can't do things like full back ups as there probably isn't enough space on the system file system, so you need the user storage area for that, so you would need that decrypted for larger files so that TWRP can gain access.
Regards
Phil
Don't forget adb sideload for installing zips without using internal storage
Use Oem Unlock?
fastboot oem unlock
Yes
How does this affect using Android Pay?
Rado_vr6 said:
How does this affect using Android Pay?
Click to expand...
Click to collapse
Same as other rooted/unlocked devices it doesn't work.
So you can root while keeping encryption enabled? I need encryption for work, but root is a MUST have. Would like to verify before I order. Thanks.
I was under the impression that flashing the chainfire boot img disables encryption?
Did you fastboot into TWRP (no flashing/installing needed) Code = fastboot boot twrp-2.8.7.0-bullhead.img and then adb push supersu?
I've done what the op had and I have root with encryption.
Sent from my Nexus 5X using XDA Free mobile app
I also want to agree. I just tried to unlock tethering without full root, but ran into issues. So to fix my issues, I just decided to follow the ops steps and root the phone. After adding the image, I was unable to push supersu due to adb not working in twrp. However, I rebooted the phone and saw the encryption password on boot. Once the os was loaded, I went into settings -> security and noticed the phone was set to encrypted. Looking through the program list, supersu installer was in the list and worked perfectly. Thanks op.
Sent from my Nexus 5X using XDA Free mobile app
How long does the device take to boot up? I've been sitting at the boot animation for a while now.
You can have root access through SuperSU with encryption enabled. I have it running just fine with encryption enabled. What you do have to have turned off is dm-verity. With dm-verity enabled, modification to the system partition are "not allowed".
And Chainfire's modified boot image has 3 main modifications:
1. A modified sepolicy with SELinux provisioning for SuperSU
2. dm-verity turned off
3. forceencrypt for data partition disabled. Basically disabled forced default encryption, but you can still encrypt.
Is there a way to root MDA build numbers at all? Whether it be encrypted or decrypted?
Camp As A Champ said:
Is there a way to root MDA build numbers at all? Whether it be encrypted or decrypted?
Click to expand...
Click to collapse
I'm not sure why you would want to. I ran the mda89f build for an hour or so before the ota to mdb08i. Phone seemed to run much smoother after the update. Possibly this was just related to timing.
Also, if you root on either of the mda builds, you won't be able to flash the ota to mdb08i. You'll be stuck. If you're waiting on the ota, just download the image and flash the system and boot, then follow OP / Chainfire's instructions.
dbrohrer said:
I'm not sure why you would want to. I ran the mda89f build for an hour or so before the ota to mdb08i. Phone seemed to run much smoother after the update. Possibly this was just related to timing.
Also, if you root on either of the mda builds, you won't be able to flash the ota to mdb08i. You'll be stuck. If you're waiting on the ota, just download the image and flash the system and boot, then follow OP / Chainfire's instructions.
Click to expand...
Click to collapse
Oh I'm special, I didn't know it was on OTA. When I go to check for system updates though, it shows that I'm up to date already. I've unlocked the bootloader and installed TWRP if that affects anything.
Should I just manually flash it to my device?
Camp As A Champ said:
Oh I'm special, I didn't know it was on OTA. When I go to check for system updates though, it shows that I'm up to date already. I've unlocked the bootloader and installed TWRP if that affects anything.
Should I just manually flash it to my device?
Click to expand...
Click to collapse
Since you already have trwp, you will have to update manually (unless you flash the stock recovery and wait for the ota, but who knows how long that will take). I would download the 80i image and just flash system.img and boot.img. That should be the equivalent of you getting the ota. Reboot and confirm that it will boot and you are on the new build. Then follow OPs instruction to root and/or decrypt.
Download, Extract everything.
Fastboot flash system system.img
fastboot flash boot boot.img
Reboot, check OP for further instruction.
This worked for me too - I tried to:
>adb push supersu.zip /system/
... Then in TWRP install -> select /system/supersu.zip
But this failed for some reason... However, this worked:
>adb sideload supersu.zip
Then reboot, and restore Thanks a lot! Didn't want to give up encryption either...
dbrohrer said:
Since you already have trwp, you will have to update manually (unless you flash the stock recovery and wait for the ota, but who knows how long that will take). I would download the 80i image and just flash system.img and boot.img. That should be the equivalent of you getting the ota. Reboot and confirm that it will boot and you are on the new build. Then follow OPs instruction to root and/or decrypt.
Download, Extract everything.
Fastboot flash system system.img
fastboot flash boot boot.img
Reboot, check OP for further instruction.
Click to expand...
Click to collapse
Will I be able to do this through TWRP or should I just use ADB to flash the image files? Sorry for all the questions, this is my first nexus phone and I'm getting used to all the new methods
Nevermind, got everything to work, thanks for the help though
I unlocked my bootloader, flashed Chainfire's systemless boot.img, flashed TWRP twrp-2.8.7.1-angler.img and when I took into recovery TWRP is asking me for a password to decrypt. I don't remember setting a password and don't know if there is a default one.
Can anyone help?
exSD said:
I unlocked my bootloader, flashed Chainfire's systemless boot.img, flashed TWRP twrp-2.8.7.1-angler.img and when I took into recovery TWRP is asking me for a password to decrypt. I don't remember setting a password and don't know if there is a default one.
Can anyone help?
Click to expand...
Click to collapse
Give this a shot?
Dees_Troy said:
When you set up a lock screen PIN / pattern / password, you are presented with an option to require a password when turning on the device. If you say no to this option, your device is encrypted using "default_password" as the password.
Click to expand...
Click to collapse
RojoNinja said:
Give this a shot?
Click to expand...
Click to collapse
I tired both a pin/default_password. Neither seems to work.
Do I need to format userdata to decrypt?
Your device is likely encrypted and TWRP can't read the contents of your SD card unless you format /userdata first. This will wipe everything on your phone. The nexus 6P rooting guide will explain this in detail. I'd link it here but I'm new on here and I don't really know how. Look in the Nexus 6P general section. It should be stickied at the top.
Here's the link to the rooting guide: http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
What happens if you boot up and set a password? Does that password work for TWRP?
Cares said:
What happens if you boot up and set a password? Does that password work for TWRP?
Click to expand...
Click to collapse
I flashed the stock image and redid the process.
I booted the phone and did not set any password/pin/fingerprint/etc. No security. Then I redid the boot.img, recovery.
I was then able to reboot into TWRP without the password prompt. Flashed systemless SuperSU and rebooted.
Now I'm stuck in the Google loading screen and has been there for a while. Looks like maybe it's not liking the new boot.img?
exSD said:
I flashed the stock image and redid the process.
I booted the phone and did not set any password/pin/fingerprint/etc. No security. Then I redid the boot.img, recovery.
I was then able to reboot into TWRP without the password prompt. Flashed systemless SuperSU and rebooted.
Now I'm stuck in the Google loading screen and has been there for a while. Looks like maybe it's not liking the new boot.img?
Click to expand...
Click to collapse
You're likely not on the latest build, so you'll have to use the images on Google to put yourself on the MDB08K (or higher) build before proceeding with the modified boot img (unless your devices can get the OTA). Many of the devices shipped with MDA89D out of the box.
Kusanagi Fire said:
You're likely not on the latest build, so you'll have to use the images on Google to put yourself on the MDB08K (or higher) build before proceeding with the modified boot img (unless your devices can get the OTA). Many of the devices shipped with MDA89D out of the box.
Click to expand...
Click to collapse
Is D or K the latest?
exSD said:
Is D or K the latest?
Click to expand...
Click to collapse
Latest is M. Modified boot was created based on K, but I believe has no problems working on M.
Kusanagi Fire said:
Latest is M. Modified boot was created based on K, but I believe has no problems working on M.
Click to expand...
Click to collapse
For some reason I thought D was the latest and flashed that. I'll upgrade to M and use the modified K boot.img.
That should clear it all up. Thanks for your help bud. I appreciate it. Let me know if I can ever help you sometime.
exSD said:
For some reason I thought D was the latest and flashed that. I'll upgrade to M and use the modified K boot.img.
That should clear it all up. Thanks for your help bud. I appreciate it. Let me know if I can ever help you sometime.
Click to expand...
Click to collapse
No worries. Happy to help. I had this problem when trying to root my phone, as well. It happens to the best of us. Hope that clears everything up for you and you're able to enjoy this beauty.
Is this normal for TWRP to ask for a password if you have pattern password turned on. So do I need to turn off all of my security before flashing TWRP 2.8.7.1
Right now my bootloader is unlocked, M6.0 all stock. I’ve been waiting for the source code to be release by Google so we can get a official root SU
boxcar8028 said:
Is this normal for TWRP to ask for a password if you have pattern password turned on. So do I need to turn off all of my security before flashing TWRP 2.8.7.1
Right now my bootloader is unlocked, M6.0 all stock. I’ve been waiting for the source code to be release by Google so we can get a official root SU
Click to expand...
Click to collapse
I'm not sure how TWRP would handle the pattern password. You can flash TWRP 2.8.7.1 and give it a shot. If it doesn't work, just download the stock image and extract the recovery.img from it and flash it back to stock.
Kusanagi Fire said:
No worries. Happy to help. I had this problem when trying to root my phone, as well. It happens to the best of us. Hope that clears everything up for you and you're able to enjoy this beauty.
Click to expand...
Click to collapse
Hey, FYI, that was my issue. Flashed the M image, then the K systemless root boot.img and all is working well now. No password prompt on latest TWRP either.
Resetting the pin worked for me
was having the same problem on Nexus 6P- had previously TWRP/rooted with no problem, don't remember being asked for a password.
After flashing recovery/radio/ROM back to stock and then later deciding to root again ran into this.
Android was still booting up OK so just set a new pin in Settings-->Security-->ScreenLock and selected the require PIN to start option. This PIN then worked as the password in TWRP to decrypt.
I was having the same issue with TWRP 2.8.7.2, I decided to flash TWRP 3.0.0.1 and I did not get prompted for the password. Not sure if this a true solution so at some point I may just decrypt data.
From another forum, This worked for me and couple of other people too
I found a better way.
I found a way around. Boot into ROM, create a 4 digit pin screen lock, then use flashify to flash recovery, then boot into new recovery and use pin.
Boom, you have decrypted recovery. You can boot back into your rom and change the passcode to "none" and twrp won't ask for a pin.
This is because when twrp initially boots it sees a "default_password" but if you go into twrp and try to type default password it will not work because there isn't a default password it just sees there is one except its unlisted it's kind of a double negative but a way around that is to create a password.
rdskhalsa said:
I found a better way.
I found a way around. Boot into ROM, create a 4 digit pin screen lock, then use flashify to flash recovery, then boot into new recovery and use pin.
Boom, you have decrypted recovery. You can boot back into your rom and change the passcode to "none" and twrp won't ask for a pin.
This is because when twrp initially boots it sees a "default_password" but if you go into twrp and try to type default password it will not work because there isn't a default password it just sees there is one except its unlisted it's kind of a double negative but a way around that is to create a password.
Click to expand...
Click to collapse
Tnx mate, your method worked like a charm for me.
I think I'm having a twist on this problem.
After using Lineage for a while I tried another rom (carbon) which I now think has encrypted my data. I tried going back to lineage but now I cannot access my data, nor the backups I made for both Lineage and Carbon.
I think that if I can put the backup of carbon back I should also have my files back. But with and encrypted file system I can not get back to Carbon.
I think I did set "ask for password at boot" in Lineage but I took off the pattern+ finger prints before making the backup and I did not set pattern or fingerprint after installing carbon.
Is there a way to get back to carbon?
Your data is no longer accessible. Once your storage has been encrypted, the only way to un-encrypt is to flash a full stock Google image, and then do a factory reset from the stock recovery. If you had any backups on PC, you could then restore them and be back in business. This USUALLY only happens to you one time and you never forget. Think of it as a housecleaning day.
Hey guys! I've having some trouble getting my device set up with root and encryption, while ending with a locked bootloader. I hope I can find some help.
Here is the procedure I tried:
Unlocked the bootloader
Did a full restore to MHC19I through fastboot
Flashed this boot.img
( This is so I can encrypt the user data partition after getting into Android, and it also allows a system-root without getting a boot loop )
Flashed the twrp-3.0.0-1-angler.img recovery
Locked the bootloader
Booted into TWRP without ever going into Android yet
Sideloaded BETA-SuperSU-v2.68-20160228150503.zip
Booted into Android and setup with my Google account, I used a fingerprint and set a PIN, and selected "PIN required on startup"
Update all the stock apps, with some reboots in between
Then encrypted the phone through security settings
Now here is where I'm having trouble.
When I boot into TWRP after having encrypted the user data partition, it asks for my password, as it should, but it won't take my PIN. It tells me "Password failed, please try again" and "Failed to decrypt data." Is the password prompt not asking for the PIN I set? Does TWRP only support decryption with a password, or something? Can I not use a fingerprint to lock the device? What am I missing here?
Is there perhaps another procedure to getting Android setup with TWRP, root, and user data encryption while ending with a locked bootloader?
Thank you in advance for all your help!
You need a modified Twrp for this new Base. Just have a look around
Gorgtech said:
You need a modified Twrp for this new Base. Just have a look around
Click to expand...
Click to collapse
Is the "twrp-3.0.0-1-angler.img" image here not the new modified TWRP for MHC19I?
edit: According to this post, I'm using the correct version of TWRP.
Yes, this one should fit. I had the same problem before.
mylios101 said:
Hey guys! I've having some trouble getting my device set up with root and encryption, while ending with a locked bootloader. I hope I can find some help.
Here is the procedure I tried:
Unlocked the bootloader
Did a full restore to MHC19I through fastboot
Flashed this boot.img
( This is so I can encrypt the user data partition after getting into Android, and it also allows a system-root without getting a boot loop )
Flashed the twrp-3.0.0-1-angler.img recovery
Locked the bootloader
Booted into TWRP without ever going into Android yet
Sideloaded BETA-SuperSU-v2.68-20160228150503.zip
Booted into Android and setup with my Google account, I used a fingerprint and set a PIN, and selected "PIN required on startup"
Update all the stock apps, with some reboots in between
Then encrypted the phone through security settings
Now here is where I'm having trouble.
When I boot into TWRP after having encrypted the user data partition, it asks for my password, as it should, but it won't take my PIN. It tells me "Password failed, please try again" and "Failed to decrypt data." Is the password prompt not asking for the PIN I set? Does TWRP only support decryption with a password, or something? Can I not use a fingerprint to lock the device? What am I missing here?
Is there perhaps another procedure to getting Android setup with TWRP, root, and user data encryption while ending with a locked bootloader?
Thank you in advance for all your help!
Click to expand...
Click to collapse
First: Why did you re-lock the bootloader? You cant flash any twrp updates or update with factory images.
Second: You should have just flashed supersu in twrp before any booting?
When clean installing I personally follow these:
fastboot flash bootloader
fastboot reboot-bootloader
fastboot flash radio radio-angler-angler-02.50.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot erase cache
fastboot format userdata
fastboot flash cache cache.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash recovery twrp
fastboot reboot-recovery
While in twrp I:
adb push supersu to /sdcard/
then flash supersu in recovery
then wipe dalvik/cache in twrp
finally let the phone boot and set up normally. Leaving bootloader unlocked
Gorgtech said:
Yes, this one should fit. I had the same problem before.
Click to expand...
Click to collapse
You've had the same issue before that I'm having now? What was your fix?
I've flashed system, boot and vendor before. Also updated the bootloader and the radio and was asked for a password which I could not get rid off. I had to sideload supersu and also flash a modified Twrp after. Now I can access the recovery like I was used to. It's the latest Base which causes trouble.
thepoetlives89 said:
First: Why did you re-lock the bootloader? You cant flash any twrp updates or update with factory images.
Second: You should have just flashed supersu in twrp before any booting?
Click to expand...
Click to collapse
I lock the bootloader for obvious security reasons, but it leads to the user data partition being wiped, which prevents the partition from encrypting on initial Android setup.
I do flash Supersu through TWRP before my first boot to Android, otherwise TWRP gets wiped out.
I'll give your procedure a try! Thank you.
mylios101 said:
I lock the bootloader for obvious security reasons, but it leads to the user data partition being wiped, which prevents the partition from encrypting on initial Android setup.
I do flash Supersu through TWRP before my first boot to Android, otherwise TWRP gets wiped out.
I'll give your procedure a try! Thank you.
Click to expand...
Click to collapse
As far as i know with 6.0.1 with the stock boot.img it automatically encrypts on first boot, even with an unlocked bootloader.
thepoetlives89 said:
As far as i know with 6.0.1 with the stock boot.img it automatically encrypts on first boot, even with an unlocked bootloader.
Click to expand...
Click to collapse
No, I believe the problem is that it does not automatically encrypt on first boot when I lock the bootloader. My work around was using a modded boot.img so I can encrypt post-setup through the security settings menu, but I can't decrypt with TWRP. Without the boot.img and a locked bootloader, it sits in a bootloop and never encrypts. through the security settings option.
I have to confirm this, but it looks like the only way to get the device encrypted, rooted, and TWRP accessible is to not use the modded boot.img and leave the bootloader unlocked, which I'd rather not. Regardless, I'll give it a try and report back.
mylios101 said:
No, I believe the problem is that it does not automatically encrypt on first boot when I lock the bootloader. My work around was using a modded boot.img so I can encrypt post-setup through the security settings menu, but I can't decrypt with TWRP. Without the boot.img and a locked bootloader, it sits in a bootloop and never encrypts. through the security settings option.
I have to confirm this, but it looks like the only way to get the device encrypted, rooted, and TWRP accessible is to not use the modded boot.img and leave the bootloader unlocked, which I'd rather not. Regardless, I'll give it a try and report back.
Click to expand...
Click to collapse
I was able to encrypt with the modified boot.img that supersu makes when you flash it over the one that comes with the factory image. Bootloader unlocked.
Gorgtech said:
I've flashed system, boot and vendor before. Also updated the bootloader and the radio and was asked for a password which I could not get rid off. I had to sideload supersu and also flash a modified Twrp after. Now I can access the recovery like I was used to. It's the latest Base which causes trouble.
Click to expand...
Click to collapse
How did you sideload supersu? I have the same problem as you
Fastboot format userdata in terminal.
kunal_07 said:
How did you sideload supersu? I have the same problem as you
Click to expand...
Click to collapse
I'm using the "adb sideload" function under "advanced" in TWRP. Another user suggested doing an "adb push" and then using the regular TWRP install instead. I'm going to try that and see what happens.
edit: sideloading vs pushing supersu made no difference. Android is still not encrypting the user data partition on first boot.
edit 2: After some testing, it looks like flashing the latest beta of Supersu is what is preventing Android from encrypting, which is obviously a problem. Without flashing Supersu, TWRP doesn't persist and I can't get root access.
I was able to root using RC SuperSU 2.69 using chainfire auto root
Easy solve.
1. Create 4 digit screen lock pin code when booted in rom settings>security
2. Use flashify to flash newest twrp
3. Boot into new twrp and use new pin code to decrypt data
When flashing new version of TWRP it automatically encrypt the data with "default_password" but if you try to use that as your password it will not work. If you create a pin, then use that pen to decrypt the password it will work. Then if you go back into your booted up rom and change the password to none TWRP will not ask you for a password.
Can't remember steps 1. And 2. Might be switched
i just updated to the mch19i build via fastboot (since i'm rooted and can't take an ota apparently - has anyone made twrp-able zips for those updates yet?) and am having this same problem. what's different about this build that we need a different twrp for?
asj0422 said:
i just updated to the mch19i build via fastboot (since i'm rooted and can't take an ota apparently - has anyone made twrp-able zips for those updates yet?) and am having this same problem. what's different about this build that we need a different twrp for?
Click to expand...
Click to collapse
Well for one thing twrp 3.0.0.1 allows for vendor images to be flashed to the vendor partition. The previous ones you can't. That's why I updated with flashify. Two seconds of easiness. Just set a 4 digit lock screen pin before because twrp encrypts with unknown password upon first boot that's why you assign it one.
The only way for otas is to side load or fast boot flash.
Or. Run a custom ROM and get flashable zips for updates, these work great with all these Google update releases
Hi everyone, I hate to bring back an old post but I am new to XDA today so I'm getting used to it.
Well, I'm a first time ROM user, PureNexus + ElementalX kernal (amazing). But I had a question regarding this encryption and TWRP. I know older versions of TWRP had issues with entering the encryption password, I want to encrypt mine but I want to be sure that this issue has been fixed. I can't find anything online regarding it either. Can anyone help me out?
Device: Nexus 6P
ROM: PureNexus 7.1.2_r24
Kernal: ElementalX 5.03
TWRP: 3.1.1
Any information would be helpful! Before I encrypt! Just don't wanna do it then be stuck.
Ayeeebroham said:
Hi everyone, I hate to bring back an old post but I am new to XDA today so I'm getting used to it.
Well, I'm a first time ROM user, PureNexus + ElementalX kernal (amazing). But I had a question regarding this encryption and TWRP. I know older versions of TWRP had issues with entering the encryption password, I want to encrypt mine but I want to be sure that this issue has been fixed. I can't find anything online regarding it either. Can anyone help me out?
Device: Nexus 6P
ROM: PureNexus 7.1.2_r24
Kernal: ElementalX 5.03
TWRP: 3.1.1
Any information would be helpful! Before I encrypt! Just don't wanna do it then be stuck.
Click to expand...
Click to collapse
Not sure what you are asking. If you've set a PIN, use it when promoted by TWRP.
I did modified build.prop once, everything worked fine, but after updating my phone, build.prop reset to default. Now I tried to modify build.prop again, and I'm stuck in bootloop.
I can boot my phone by changing active slot from A to B, so it's only A slot stuck in bootloop. This is what I did:
Boot into bootloader
Unlock bootloader
Boot into twrp recovery
Pull build.prop, edit, push it back
I forgot to chmod build.prop, so after rebooting my phone, it failed, stuck in bootloop. After I chmod build.prop, it still won't boot. How do I fix it?
Try flashing system.img to slot a using fastboot, if it's only A that is a problem.
Just flash newest system image from official site using MiFlash tool without wiping the data
And there's no other way to fix this problem without flashing system image? I mean, I just modified build.prop, nothing else, isn't there faster and easier way to fix it? What if I boot twrp with B slot, pull build.prop, then boot twrp with A slot, and push build.prop?
matcho13579 said:
Just flash newest system image from official site using MiFlash tool without wiping the data
Click to expand...
Click to collapse
Will it delete apps and do I need to setup android again, i.e. login with google account again, setup fingerprint and etc?
druckis3000 said:
And there's no other way to fix this problem without flashing system image? I mean, I just modified build.prop, nothing else, isn't there faster and easier way to fix it? What if I boot twrp with B slot, pull build.prop, then boot twrp with A slot, and push build.prop?
Will it delete apps and do I need to setup android again, i.e. login with google account again, setup fingerprint and etc?
Click to expand...
Click to collapse
Flashing system, as long as that is all you do, will not remove anything like your stuff. I've done it before many times, even used miflash but made sure I did select to save user data. Everything there as before, except it completely removed root (Magisk), and relocked the bootloader.
goofball2k said:
Flashing system, as long as that is all you do, will not remove anything like your stuff. I've done it before many times, even used miflash but made sure I did select to save user data. Everything there as before, except it completely removed root (Magisk), and relocked the bootloader.
Click to expand...
Click to collapse
I need to flash it while in bootloader or recovery? And will it flash to both slots, or only active slot?
druckis3000 said:
I need to flash it while in bootloader or recovery? And will it flash to both slots, or only active slot?
Click to expand...
Click to collapse
MiFlash or flashing system, you need to put your phone in fastboot mode.
MiFlash will flash both slots.
if you manually flash, you can decide which slot you flash to.
fastboot flash system_a system.img
goofball2k said:
MiFlash or flashing system, you need to put your phone in fastboot mode.
MiFlash will flash both slots.
if you manually flash, you can decide which slot you flash to.
fastboot flash system_a system.img
Click to expand...
Click to collapse
I'm on Linux, so I can't install MiFlash tool, so if I flash via fastboot, would it save my data?
druckis3000 said:
I'm on Linux, so I can't install MiFlash tool, so if I flash via fastboot, would it save my data?
Click to expand...
Click to collapse
Nevermind, already did it and everything works fine, all data were saved. But I still got one question, why can't I edit build.prop file? Few minutes ago I tried to pull build.prop from slot B and push it to slot A, then slot B also stopped working, stuck in bootloop, even though I just pulled build.prop from slot B, and didn't modified it.
druckis3000 said:
Nevermind, already did it and everything works fine, all data were saved. But I still got one question, why can't I edit build.prop file? Few minutes ago I tried to pull build.prop from slot B and push it to slot A, then slot B also stopped working, stuck in bootloop, even though I just pulled build.prop from slot B, and didn't modified it.
Click to expand...
Click to collapse
Easier method is to use Magisk module (I guess you want to enable Camera2 API)
druckis3000 said:
Nevermind, already did it and everything works fine, all data were saved. But I still got one question, why can't I edit build.prop file? Few minutes ago I tried to pull build.prop from slot B and push it to slot A, then slot B also stopped working, stuck in bootloop, even though I just pulled build.prop from slot B, and didn't modified it.
Click to expand...
Click to collapse
You might have messed up owner or rights of the file. That's usually the main culprit. Simple file pull should not do anything wrong. Maybe you were still booting into the slot A? For the future I would suggest using Magisk systemless mods, it's much easier to apply and remove and you won't break anything (Safetynet for example).
Yes I want to enable Camera2 API. I don't wanna use Magisk, because of rooting, I do not need root. That's why I boot into TWRP recovery and edit build.prop using adb pull/push, but now I'm afraid to edit it again, due to previous issues.
druckis3000 said:
Yes I want to enable Camera2 API. I don't wanna use Magisk, because of rooting, I do not need root. That's why I boot into TWRP recovery and edit build.prop using adb pull/push, but now I'm afraid to edit it again, due to previous issues.
Click to expand...
Click to collapse
You can use Magisk and disable root (auto reply set to deny root access).
Edit: stock kernel should have dm-verity enabled, so as soon as you mount system as read write, it fails the safe boot verification. This might be the reason of your bootloops.
_mysiak_ said:
You can use Magisk and disable root (auto reply set to deny root access).
Edit: stock kernel should have dm-verity enabled, so as soon as you mount system as read write, it fails the safe boot verification. This might be the reason of your bootloops.
Click to expand...
Click to collapse
But I already modified build.prop successfully previously, how it passed safe boot verification? Using Magisk I'll not get OTA updates anymore, so I don't want to install Magisk.
edit: Ok, I did another test, I just booted into TWRP and rebooted into system, and phone stuck in bootloop, so I guess that's TWRP causing that issue?
druckis3000 said:
But I already modified build.prop successfully previously, how it passed safe boot verification? Using Magisk I'll not get OTA updates anymore, so I don't want to install Magisk.
Click to expand...
Click to collapse
Well, it's of course totally up to you, but with Magisk you need to restore only boot.img. If you modify build.prop directly, you have to reflash whole system partition to apply OTA. In both cases OTA is going to fail until you restore all partitions to stock.
If you know what you did before, just repeat the steps..[emoji846] If you can't/don't know, use verified and easy method (Magisk).
_mysiak_ said:
Well, it's of course totally up to you, but with Magisk you need to restore only boot.img. If you modify build.prop directly, you have to reflash whole system partition to apply OTA. In both cases OTA is going to fail until you restore all partitions to stock.
If you know what you did before, just repeat the steps..[emoji846] If you can't/don't know, use verified and easy method (Magisk).
Click to expand...
Click to collapse
I edited my last reply, take a look at it. I do everything correctly, but I guess it's problem with TWRP recovery. Before installing OTA update I edited build.prop successfully, now after update if I boot into TWRP, I instantly get bootloop, no need to edit build.prop.
druckis3000 said:
I edited my last reply, take a look at it. I do everything correctly, but I guess it's problem with TWRP recovery. Before installing OTA update I edited build.prop successfully, now after update if I boot into TWRP, I instantly get bootloop, no need to edit build.prop.
Click to expand...
Click to collapse
I use TWRP without any issues, so I doubt that it's caused by it. Do you flash TWRP or boot it only? Do you allow system mounting as RW in TWRP?
_mysiak_ said:
I use TWRP without any issues, so I doubt that it's caused by it. Do you flash TWRP or boot it only? Do you allow system mounting as RW in TWRP?
Click to expand...
Click to collapse
I don't flash TWRP, I only boot into it. Yesterday when I did that test, I didn't even mounted system partition, but usually yes, I mount it as RW.
I'm using older TWRP version, it's 3.1.1-1, TWRP has newer version, 3.2.1, but that one wont boot, phone boots into system when I try to boot TWRP. Maybe newer version wouldn't cause bootloop
No idea then, I am on December update and can boot into TWRP and system without any issues (though I don't mount system as RW).
_mysiak_ said:
No idea then, I am on December update and can boot into TWRP and system without any issues (though I don't mount system as RW).
Click to expand...
Click to collapse
You use TWRP image from their official website? Weird.. It never worked for me, the one I used before was downloaded from other website, not TWRP.
I tried to remove root.
First, I used supersu and used the full unroot setting. However, after rebooting back to android, it is still showing root.
Therefore, I used magisk uninstall. After that my phone is in boot loop with dm-verity error.
Tried to go into TWRP (still works) to install no-verity 6.0 zip but it says boot cannot be found.
So, I am now trying to install recovery.img and boot.img. However, I am unable to find recovery file for WW_15.0410.1807.75 (Android O).
Can anyone help shed some light? How can I restore back the phone without losing data?
If all else fail, what are my last resort to get the phone back to working?
Appreciate any input. Thanks!
Ok, I tried a few things and all failed. Now the phone keep looping into fastboot when I plug in the usb.
I would like to just flash to latest firmware will do. Data recovery is secondary now.
I tried AFT 1.0.0.45 but it only allow zip files. I cannot select the raw file. I tried renaming the raw to zip but it still refuse to flash. I get error saying unable to unzip. However, before that I can see the app is trying to connect to somewhere for verification. I think something about FRP. Don't know what is that.
Appreciate any input on this. Thanks.
abubin said:
So, I am now trying to install recovery.img and boot.img. However, I am unable to find recovery file for WW_15.0410.1807.75 (Android O).
Click to expand...
Click to collapse
if you flash stock ROM, recovery is restored automatically.
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZE552KL/UL-ASUS_Z012D-WW-15.0410.1807.75-user.zip
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZE520KL/UL-ASUS_Z017D_1-WW-15.0410.1807.75-user.zip
aIecxs said:
if you flash stock ROM, recovery is restored automatically.
View attachment 5825195
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZE552KL/UL-ASUS_Z012D-WW-15.0410.1807.75-user.zip
View attachment 5825209
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZE520KL/UL-ASUS_Z017D_1-WW-15.0410.1807.75-user.zip
Click to expand...
Click to collapse
Thanks! I manage to flash the stock ROM and it is able to boot into the OS again.
However, I am still seeing this "DM-verity in EID" screen whenever I boot up. Is this okay? Cause I remember this screen wasn't shown previously. It supposed to show a screen saying bootloader is unlocked and some security thing. Now it's showing this EID screen. Anyway to fix it?
if there is something like vbmeta partition, flash vbmeta.img otherwise I don't know. the screen ask for locking bootloader, but I do not recommend this. usually locking bootloader only works if every partition is stock, I doubt the locking process will fix anything.