hey,
I wanted to root my nexus 5x too, first I tried to do so with the nexus tool kit....
it was all working until it came to the root process:
it said in the log:
Rooting....
Waiting for your device....
and nothing else happened anymore.
So I tried it manually with a guide.
As the bootloader was already unlocked, I continued with flashing the recovery (twrp 2.8.7.2) in fastboot.
Then it rebooted into the recovery.
Then twrp asked me for a password, (Mount) decrypt Data. I skip it without entering a password. And I didn't add a pattern or PIN to unlock my phone at the first boot up.
I allowed the system modification then... so then before rebooting, twrp wasn't asking me if I want to flash the SuperSu.
Since this I'm stuck in a bootloop.
I can boot into the bootloader and recovery, I also tried to do a factory wipe or also formating data. But none of them worked for me. I'm still stuck in the bootloop...
I have no idea what to do now....
I'm really thankfull for every kind of help!
sorry wrong subforum...
Try to reflash TWRP over adb-console(on your pc) and then Root- Systemless version.
If you have any questions ask!!
Vulkaistos said:
Try to reflash TWRP over adb-console(on your pc) and then Root- Systemless version.
If you have any questions ask!!
Click to expand...
Click to collapse
I have to add something which i forgot to mention.....after I flashed the recovery and booted into it for the first time, twrp asked me for a password, (Mount) decrypt Data. I skip it without entering a password. And I didn't add a pattern or PIN to unlock my phone at the first boot up.
I'm not able boot my phone up anymore.... I can try to flash the recovery with fastboot again...if this is what you mean?
okay i pushed the supersu zip onto the phone, and just flashed it. And my phone is booting normally now
thank you very very much. you saved me and my phone
That's nice to hear.
Have Fun with your Phone!!!!!!!!!!!!!!
I've just screwed up, big time. Was trying to un-root using the SuperSU app's "Full unroot" function, unaware that my device was encrypted.
Soo, now it won't boot. I can access both recovery and bootloader, but not the internal memory, which is the big problem here (pictures etc.).
When trying to boot I got the dm-verity error, and then the phone shuts off. In twrp I can't access the internal memory, so I can't backup my stuff.
I tried flashing stock boot, (does it have to be from the exakt OOS version as i have?), stock recovery and also re-flashing SuperSU, but nothing works. When flashing SuperSU i can boot my phone, but then I get the message "Can't encrypt your phone", and it tells me that I have to do a factory reset (which I don't want to atm)
Is there any hope of fixing this?
Thank you!
Try using adb to pull your files on your computer. Though since TWRP can't access internal storage, I doubt adb will.
You could also try to dirty flash the full ROM of whatever version of OOS you were using before (flash full rom in TWRP, wipe cache/dalvik, flash SuperSU or Magisk). This should restore most of your corrupted system and boot images. Since you tripped DM-verity, you will have to root again before rebooting. The no-verity/encript zip that's floating around the forums might also work? This shouldn't delete any of your user data, though I can't be certain if the dirty flashed ROM would be able to decrypt it.
Anova's Origin said:
Try using adb to pull your files on your computer. Though since TWRP can't access internal storage, I doubt adb will.
You could also try to dirty flash the full ROM of whatever version of OOS you were using before (flash full rom in TWRP, wipe cache/dalvik, flash SuperSU or Magisk). This should restore most of your corrupted system and boot images. Since you tripped DM-verity, you will have to root again before rebooting. The no-verity/encript zip that's floating around the forums might also work? This shouldn't delete any of your user data, though I can't be certain if the dirty flashed ROM would be able to decrypt it.
Click to expand...
Click to collapse
Try to dirty flash the rom you have now instaled. If you can't from TWRP, then try sideloading it. Good luck
Thank you for your tips, but didn't work
Tried wipe cache/dalvik -> sideload 4.0.2 -> sideload SuperSU -> fastboot twrp 3.0.3-0 (all of these I had before). And also only wipe cache/dalvik with a sideload of just the ROM, but I still get "Can not encrypt phone" when booting.
What does the SuperSU change in the system? And why does it not trigger dm-verity when flashing SuperSU, but when i remove it? I'm so confused. Is it even possible to get the phone in the same state as before uninstalling SuperSU, so it's bootable?
Systemless SuperSU modifies the /boot partition. Scripts have been added to the SuperSU installer to prevent dm-verity from detecting changes, which is why it doesn't get triggered when you root your phone after enabling system access in TWRP. Whenever you flash OOS (which has dm-verity enabled by default), you must root immediately before rebooting or it will replace TWRP with the stock recovery. Future attempts to enable TWRP without rooting will trigger dm-verity.
It's odd that you phone states that it cannot encrypt storage rather than decrypt it at boot. If you still have access to TWRP, try clean flashing OOS on your phone (use the wipe feature in TWRP). This will wipe /data and all your apps, but leave behind user files such as music and photos. Then flash OOS and immediately root before rebooting. Both SuperSU and Magisk will prevent OOS from attempting to encrypt /data on boot, which it does by default.
You didn't by any chance make a nandroid backup before unrooting did you?
Anova's Origin said:
Systemless SuperSU modifies the /boot partition. Scripts have been added to the SuperSU installer to prevent dm-verity from detecting changes, which is why it doesn't get triggered when you root your phone after enabling system access in TWRP. Whenever you flash OOS (which has dm-verity enabled by default), you must root immediately before rebooting or it will replace TWRP with the stock recovery. Future attempts to enable TWRP without rooting will trigger dm-verity.
It's odd that you phone states that it cannot encrypt storage rather than decrypt it at boot. If you still have access to TWRP, try clean flashing OOS on your phone (use the wipe feature in TWRP). This will wipe /data and all your apps, but leave behind user files such as music and photos. Then flash OOS and immediately root before rebooting. Both SuperSU and Magisk will prevent OOS from attempting to encrypt /data on boot, which it does by default.
You didn't by any chance make a nandroid backup before unrooting did you?
Click to expand...
Click to collapse
Sorry, I was wrong there, of course it's decrypt, NOT encrypt
I can flash twrp with fastboot and use it partially (says phone is encrypted, so limited options). I do not have access to /data or /system i belive, but I can sideload with the ADB function in TWRP. Tried to access files from twrp, but no go.
If dm-verity is not triggered when just flashing for example 4.0.2, why do I need to root it and install twrp? Is that so that I in some way could get it "un-triggered"?
Yep, I did a nandroid before, but was so stupid that I didn't backup to my computer. It's sitting inside the phone, encrypted
Dude I tried to unroot the N5X of my girlfriend the other day as snapchat didn't let us login with root. Phone was also decrypted, but after you boot it it will encrypt. If you stop the process (because you thought it was bootlooping, as those little motherf*****s don't tell when they are busy encrypting) and I am sure you did, the data is lost. That's exactly what happened to me. Don't try to encrypt or rescue anything. It wont work. Wipe the filesystem and start all over.
I am sorry though.
EDIT: I might be a little late, didn't check the date. But that encrypting stuff is serious, It should at least display a text with "ENCRYPTING..." or so. I let my phones encrypted since that day.
orreborre said:
I've just screwed up, big time. Was trying to un-root using the SuperSU app's "Full unroot" function, unaware that my device was encrypted.
Soo, now it won't boot. I can access both recovery and bootloader, but not the internal memory, which is the big problem here (pictures etc.).
When trying to boot I got the dm-verity error, and then the phone shuts off. In twrp I can't access the internal memory, so I can't backup my stuff.
I tried flashing stock boot, (does it have to be from the exakt OOS version as i have?), stock recovery and also re-flashing SuperSU, but nothing works. When flashing SuperSU i can boot my phone, but then I get the message "Can't encrypt your phone", and it tells me that I have to do a factory reset (which I don't want to atm)
Is there any hope of fixing this?
Thank you!
Click to expand...
Click to collapse
I don't understand why unrooting will have any problem with phone being encrypted.
I have done this unrooting process without a hiccup and my phone is also factory-encrypted so there's that.
What version of TWRP were you using? Try flashing the full OOS zip in TWRP but please flash the latest TWRP before doing so.
mharis05 said:
I don't understand why unrooting will have any problem with phone being encrypted.
I have done this unrooting process without a hiccup and my phone is also factory-encrypted so there's that.
What version of TWRP were you using? Try flashing the full OOS zip in TWRP but please flash the latest TWRP before doing so.
Click to expand...
Click to collapse
I believe what they meant was they were unaware their phone was decrypted. Unrooting will cause the phone to begin encrypting on boot, and I imagine OP cancelled it (as the phone does not say when it is encrypting)
orreborre said:
I've just screwed up, big time. Was trying to un-root using the SuperSU app's "Full unroot" function, unaware that my device was encrypted.
Soo, now it won't boot. I can access both recovery and bootloader, but not the internal memory, which is the big problem here (pictures etc.).
When trying to boot I got the dm-verity error, and then the phone shuts off. In twrp I can't access the internal memory, so I can't backup my stuff.
I tried flashing stock boot, (does it have to be from the exakt OOS version as i have?), stock recovery and also re-flashing SuperSU, but nothing works. When flashing SuperSU i can boot my phone, but then I get the message "Can't encrypt your phone", and it tells me that I have to do a factory reset (which I don't want to atm)
Is there any hope of fixing this?
Thank you!
Click to expand...
Click to collapse
I had a different issue but same like this....
i unrooted my phone and my device was decrypted.....
after reboot the phone encrypted automatically and all my datas were lost...
the dm-verity was are triggered....
I come from a Nexus. So I am bit confused regarding the process of flashing TWRP on the Z2 play. On Nexus devices I could flash TWRP but did not have to decrypt anything. However in the TWRP post (dev forum) I could read:
"Force encryption is enabled by default in stock OS and twrp will successfully decrypt /data at first boot if all goes well"
Why does TWRP (have to) decrypt /data on the Z2 play?
TWRP supports encrypted phones. The early versions required you to leave the phone decrypted or you couldn't read anything in recovery. DM verity seems to go both ways too.
Thanks for your response! Yes, TWRP supports encrypted phones (I did that on my Nexus). However in the TWRP topic you can read:
twrp will successfully decrypt /data at first boot if all goes well
Click to expand...
Click to collapse
So I am wondering whether it is possible to disable decryption when you flash twrp on the z2p?
Normally I would have tried it already and re-flashed the stock image if something went wrong (but there is no stock-image yet ...)
I've installed TWRP on many Samsung devices but this is my first time on the S III. I know to uncheck the auto reboot option in Odin and booting into TWRP before allowing a system boot. I've done that and even used TWRP to make a backup. But after rebooting to system, shutting down, and then booting to recovery, the phone has still re-written the recovery and I no longer have TWRP. What am I doing wrong?????
lewmur said:
I've installed TWRP on many Samsung devices but this is my first time on the S III. I know to uncheck the auto reboot option in Odin and booting into TWRP before allowing a system boot. I've done that and even used TWRP to make a backup. But after rebooting to system, shutting down, and then booting to recovery, the phone has still re-written the recovery and I no longer have TWRP. What am I doing wrong?????
Click to expand...
Click to collapse
edit: Found out I had to flash SuperSU on the first boot into TWRP to keep it from being over-written.
Hi,
I downgraded my Nexus 5X from stock 8.1 (OTA) to the latest stock 6.0.1 firmware (via fastboot), and booted up to make sure it's working. All is fine. Device is wiped to a factory state.
I then flashed the latest TWRP recovery, and then rebooted to recovery to try and flash Magisk. At this stage, TWRP asks me for a password to decrypt data, and I didn't set any password at all. If I click on Cancel to continue, I'm able to see the zip file that I placed in /sdcard, presumably coz it's encrypted and TWRP can't read it? What's the password though?
I notice upon Android bootup, under Settings->Security, that my phone is encrypted. I tried factory resetting the phone to disable encryption, but it shows up encrypted even after factory reset.
Also noticed that when I try to reboot, it always reboots back to TWRP rather than Android. Once I flash it back to the stock recovery, then I can boot to Android.
How can I get TWRP to work on an encrypted phone without a password?
I had a similar issue with 8.1. I reset my phone, waited booting and setup is done, then I tried different versions of TWRP and finally no password required!
Which version of TWRP worked for you?
I ended up using 3.0.2-2, which was released around the same time as the 6.0.1 image that my N5X is running on. Formatted data and wiped everything but system in TWRP, rebooted to TWRP, and it worked after that. Weird how fastboot format userdata didn't work.