Related
So I wanted to create a thread dedicated to performing this function. I know as someone who does this quite often, I like to have all my ducks in a row to ensure everything works perfectly. I'm not big on fragging my phone and then frantically trying to find a way to undo all the chaos. I do a lot of research and ask a lot of questions before doing anything.
On that note I would like to first thank all the amazing people on here, whether they be developers or just experienced Tech Guru's, everyone is always a big help. I take absolutely no credit for any of the awesomeness that can be found on XDA, I'm just creating a thread that I hope will help folks find everything in one place for this function. So here we go, I'm going to explain the way I did it, which is the way I have been doing stuff like this for years. I have a preferred method as it has always resulted in perfect flashes and no bricks, not even soft bricks. So I feel it works pretty well.
Just so it is understood, this is for the Moto X Pure, which has been bootloader unlocked and has TWRP and root installed. Also it should be noted that you need to have Developer Options enabled and USB Debugging enabled. You should also be familiar with the ADB process, to some extent, maybe you have at least heard of it.
Steps to follow:
1. Use Titanium Backup and backup all your User Apps, NOT SYSTEM APP's, system apps will not restore across updates and will most often corrupt your new install.
2. Make a Nandroid backup using TWRP, I backed up system, boot, data, and EFS, but I don't think EFS is necessary.
3. Make sure you have the Motorola Drivers installed, get them from here http://www.motorola.com/getmdmwin
4. Get Shawn5162's Restore to Stock Tool, I know others have said it's not necessary to perform a complete restore, but this is part of my process that I have always done, and it's always worked. Get it here by using one of the mirror's created by patt2k in post 6, and don't forget to thank him for the mirrors http://forum.xda-developers.com/moto-x-style/development/windows-tool-moto-x-style-pure-edition-t3199905
5. Unzip Shawn5162's zip to a folder on your desktop, and before you move onto the next step, make sure you have backed up everything valuable on your phone, such as pictures, messages, etc..., because everything is going to be erased in the next step, except for the stuff on your MicroSD. I'm so anal, I even remove the MicroSD before flashing. Connect your phone to your computer using a USB and make sure you have USB debugging enabled under Developer Options.
6. Inside the folder you created run the FLASH-ALL.bat, which will reboot your device to the bootloader and begin the restore to stock flash. This will remove root and TWRP, but will not remove the fact you have an unlocked bootloader. Your phone will reboot when complete and should boot back into your system within a short period of time.
7. Once you are rebooted, you may need to do a little setup before you get the message that a System Update is available. DO NOT waste your time installing any apps, wait until you have full root on MM before doing any of that. Once the Update message appears, accept it and download the MM update file, then install it once it is finished downloading and asks if you want to install.
8. The update takes about 20 - 25 minutes so be patient. Once complete your phone will once again boot back to system, now you have MM in it's complete unrooted greatness.
9. Now go into settings, about phone, and tap on build number a bunch of times to enable Developer Options. Then go into developer options and enable USB Debugging.
10. Next download a bunch of stuff from the following links, if you desire to install TWRP and regain root.
TWRP 2.8.7.1 here https://dl.twrp.me/clark/twrp-2.8.7.1-clark.img
Modified Boot Image from here, required to perform systemless root , not sure about the Cowboy hat dude, but click on him, it will download the file.
SuperSU 2.52 from here https://download.chainfire.eu/743/SuperSU/BETA-SuperSU-v2.52.zip?retrieve_file=1
11. Next copy the modified boot file and SuperSU file directly to your internal or external SD on your phone, either works fine, although I prefer my External SD.
12. Next copy the TWRP file you downloaded into the same folder you made for Shawn5162's files. This folder has all the adb and fastboot files you need to perform the TWRP flash. Now hold shift and right click and choose open a command window here. Then ensure your device is detected by running the command adb devices, it should show your phones S/N and the word device. If it doesn't, you may need to look at your phone and respond to the prompt about allowing your computer to have access to adb. Try the command again after that. Then run the command adb reboot bootloader, which should reboot your phone to bootloader fastboot mode.
13. Once it fastboot mode run fastboot devices just to make sure your device is still detected, then run the command fastboot flash recovery twrp-2.8.7.1-clark.img. That will flash TWRP to your recovery partition. Then type the command fastboot reboot twrp-2.8.7.1-clark.img or use the volume rocker to toggle to recovery then select the power key to boot to it. Make sure you choose the slider at the bottom to allow modification. Once on the main screen you can choose reboot and then select recovery. This makes sure that you have booted to TWRP at least once, and ensures by rebooting to it, you can get back to it.
14. Now perform a Nandroid Backup, using the TWRP Backup option, of your completely stock MM system, data, boot, and EFS partitions. Enable compression if you like and store it to your External SD if you have one. This allows you to have an unrooted backup on your SD, which is good for future updates. After the Nandroid is complete now flash the modified boot image zip using the TWRP Install feature, and when it's complete, then flash the SuperSU zip file. After I always perform the option to erase Dalvik and Cache, I just think it is a good thing to do, it's probably placebo, but I do it anyhow.
15. Go back to TWRP Home and choose reboot and select system. Your device will reboot and you now have a fully updated and rooted Moto X Pure on MM.
Thanks go out to all the folks who have contributed to the many threads that contain this information. Special thanks to Shawn5162, DaMadOne, Chainfire, and Hashbang173 for their awesomeness. Hope this helps folks that are concerned about performing these procedures. I can say that it worked perfectly for me with no issues at all, but of course I take no responsibility if it doesn't work for you and causes your device to fail. Again these are similar steps I have taken in the past with other devices and I have never had a single brick, so hopefully it works for others as well.
Enjoy!!
I have a Moto X Pure as described with the bootloader unlocked and rooted. The popup message to upgrade to MM comes up constantly now - what happens if you just let it try to update?
I think I am in way over my head. I am receiving my phone Friday and was looking to unlock to root but from the looks of it, I will not be able to do that.
I've never unlocked & rooted a phone before. So all that looks like the bible to an uneducated man "me".
superkev72 said:
I have a Moto X Pure as described with the bootloader unlocked and rooted. The popup message to upgrade to MM comes up constantly now - what happens if you just let it try to update?
Click to expand...
Click to collapse
If I'm not mistaken it will download to your phone but not be able to be installed because of an error
Is there no way to upgrade from LP to MM without a wipe?
superkev72 said:
Is there no way to upgrade from LP to MM without a wipe?
Click to expand...
Click to collapse
Yeah, if you rooted already, you must reflash the original boot.img. Then update, and then restore your root. Read here:
http://forum.xda-developers.com/mot...t-moto-x-style-xt1572-br-marshmallow-t3259380
At the bottom of the post, you get the original file you need and it is mentioned here:
And enjoy!
Now you have a rooted MotoX Style Marshmallow. To apply any OTAs, you only need reflash stock boot.
K?
Why would you want to update without a wipe? You must like sluggish performance
i have no wifi after this
No WIFI either
I ended up with no WIFI after following these steps also.
is it true, we cannot downgrade from 601 to 6.0 or 5.1.1?
skimaniaz said:
I ended up with no WIFI after following these steps also.
Click to expand...
Click to collapse
Same here. Anybody got a fix?
So the last three posts complain of no wifi yet people keep using this method?
The modified boot zip breaks the wifi. You can root by flashing superSU 2.62, I think, or any SuperSU zip that is specifically systemless.
ilovemeow said:
is it true, we cannot downgrade from 601 to 6.0 or 5.1.1?
Click to expand...
Click to collapse
Not true.
lafester said:
Not true.
Click to expand...
Click to collapse
coz i tried before, it fail in first 2 flash steps
Are you unlocked?
ilovemeow said:
coz i tried before, it fail in first 2 flash steps
Click to expand...
Click to collapse
The partition always fails. Just ignore it. You should be able to downgrade the bootloader. I have been able to so I don't know why you would be having issues with that unless your bootloader is locked/re-locked.
Sent from my XT1575 using XDA Labs
So is this safe or not?
lafester said:
Are you unlocked?
Click to expand...
Click to collapse
yup, it's unlocked, but currently fine for using android M at this moment
Disclaimer: I have done these steps multiple times and haven't come across any issues
Read All Step carefully. Any issues or damage to your phone that occurs while doing this I am not responsible.
If TWRP asks you for Password to decrypt data & maybe you have important data in you device, So you can't format data.
Follow these steps:
1. Download the OxygenOS full zip file (tested on 4.0.1 & above)
2. Open TWRP.
3. When It asks for password, cancel it.
4. Click "Read Only" button.
5. Install the OxygenOS zip file.
6. Reboot.
7. The OS may misbehave.
8. Open TWRP again. & Boom! No encryption password.
9. Connect to PC and copy the Important data.
10. Flash Any ROM now.
Thanks!
Recently I had to type in the password but I didn't know that it is possible to bypass it with this...
svandasek said:
Thanks!
Recently I had to type in the password but I didn't know that it is possible to bypass it with this...
Click to expand...
Click to collapse
Glad it helped you
ah.... if i only knew :crying:
That's good from a data recovery point of view... but it just sucks from a security point of view.
Not sure if I should be happy or concerned
TWRP Encryption ByPass
maddler said:
That's good from a data recovery point of view... but it just sucks from a security point of view.
Not sure if I should be happy or concerned
Click to expand...
Click to collapse
Agree .... that seems like a gaping security vulnerability. :-/
maddler said:
That's good from a data recovery point of view... but it just sucks from a security point of view.
Not sure if I should be happy or concerned
Click to expand...
Click to collapse
There's no need to be concerned (about this, specifically).
tk8lm6 said:
Agree .... that seems like a gaping security vulnerability. :-/
Click to expand...
Click to collapse
Actually, this is a case where this device is more secure than previous devices. The encryption key for your user data is divided into two parts. First is the part you type in when booting. The other half is stored in the "secure element" (TrustZone) inside the processor, and is unique to your phone. How the OP3 improves this is that it actually stores two versions of the device-specific key. One is used when the system is trusted (the kernel is signed and dm-verity passes), and the other is used when it is untrusted. This is part of what wipes your data when you unlock the bootloader. The security benefit comes from the SoC locking down the encryption keys when verification fails. Going back to the stock ROM causes all of the verification to pass, and the keys stored in the TrustZone are allowed to unlock your data partition.
On the other hand, if this allows you to bypass manually-enabled encryption, that would be a major security problem.
What interests me is that installing OOS should replace TWRP with the stock recovery image, but this appears not to have happened. Or did you have to flash TWRP again from fastboot after booting into OOS?
smaeul said:
There's no need to be concerned (about this, specifically).
Actually, this is a case where this device is more secure than previous devices. The encryption key for your user data is divided into two parts. First is the part you type in when booting. The other half is stored in the "secure element" (TrustZone) inside the processor, and is unique to your phone. How the OP3 improves this is that it actually stores two versions of the device-specific key. One is used when the system is trusted (the kernel is signed and dm-verity passes), and the other is used when it is untrusted. This is part of what wipes your data when you unlock the bootloader. The security benefit comes from the SoC locking down the encryption keys when verification fails. Going back to the stock ROM causes all of the verification to pass, and the keys stored in the TrustZone are allowed to unlock your data partition.
On the other hand, if this allows you to bypass manually-enabled encryption, that would be a major security problem.
What interests me is that installing OOS should replace TWRP with the stock recovery image, but this appears not to have happened. Or did you have to flash TWRP again from fastboot after booting into OOS?
Click to expand...
Click to collapse
No arguing that previous versions were less secure. But, still, as long as there's a way to bypass encryption that's a security failure.
Encrypted data shouldn't be made available unless proper key(s) or passwords have been provided.
If that's the way that's meant to work, then that's flawed by design.
smaeul said:
There's no need to be concerned (about this, specifically).
Actually, this is a case where this device is more secure than previous devices. The encryption key for your user data is divided into two parts. First is the part you type in when booting. The other half is stored in the "secure element" (TrustZone) inside the processor, and is unique to your phone. How the OP3 improves this is that it actually stores two versions of the device-specific key. One is used when the system is trusted (the kernel is signed and dm-verity passes), and the other is used when it is untrusted. This is part of what wipes your data when you unlock the bootloader. The security benefit comes from the SoC locking down the encryption keys when verification fails. Going back to the stock ROM causes all of the verification to pass, and the keys stored in the TrustZone are allowed to unlock your data partition.
On the other hand, if this allows you to bypass manually-enabled encryption, that would be a major security problem.
What interests me is that installing OOS should replace TWRP with the stock recovery image, but this appears not to have happened. Or did you have to flash TWRP again from fastboot after booting into OOS?
Click to expand...
Click to collapse
I've tried many times. OOS replaces TWRP only on CLEAN Instal for me.
hey guys, i tried to flash oos 5.0 zip, before that i was on another rom. wiped data, system, cache and flashed oos 5.0. and now internal storage is encrypted. how do i flash the zip in twrp now?
manchitro said:
hey guys, i tried to flash oos 5.0 zip, before that i was on another rom. wiped data, system, cache and flashed oos 5.0. and now internal storage is encrypted. how do i flash the zip in twrp now?
Click to expand...
Click to collapse
Just flash it.
Wait, are you saying by just installing a zip, the encrypion hardware pass is gone? WTF.. Is such "hack" available on other devices? Xiaomi redmi(s) for example?
hey i am not able to see any of my files or the zip itself within? is there anything to resolve that?
i can boot into os but for whatever reason cant get to twrp. i have the backup .imgs on my pc now too can i sideload a restore?
im stuck not able to get twrp to see any of my storage and i cant get into twrp twice in a row, so if i fastboot and flash twrp thru adb and then boot into twrp, it asks me for the password, if i hit cancel it just shows 0 storage. ive tried to go to adb sideload but it just sits there. I have the backup i made thru twrp before trying to update.
SourPower said:
hey i am not able to see any of my files or the zip itself within? is there anything to resolve that?
i can boot into os but for whatever reason cant get to twrp. i have the backup .imgs on my pc now too can i sideload a restore?
im stuck not able to get twrp to see any of my storage and i cant get into twrp twice in a row, so if i fastboot and flash twrp thru adb and then boot into twrp, it asks me for the password, if i hit cancel it just shows 0 storage. ive tried to go to adb sideload but it just sits there. I have the backup i made thru twrp before trying to update.
Click to expand...
Click to collapse
Yeah same issue here, as soon as I go in twrp and can't type the password, I can't access my files which is expected behavior, so I don't understand how you can access the file to flash from twrp.
Can someone detail please?
---------- Post added at 07:06 PM ---------- Previous post was at 06:40 PM ----------
Actually I just found a way out to get to previous twrp version, and all is back to normal
From your running ROM, you can download the application twrp (root needed oc)
Then you can use it to flash recovery.
I always keep former version file so I could revert to bluspark twrp that was working before. All worked as expected!
Still not solving the encryption password issue when flashing new recent twrp..
Android 10 Encryption / Security Issue - ADB Encryption Bypass?
rahulrs0029 said:
Disclaimer: I have done these steps multiple times and haven't come across any issues
Read All Step carefully. Any issues or damage to your phone that occurs while doing this I am not responsible.
If TWRP asks you for Password to decrypt data & maybe you have important data in you device, So you can't format data.
Follow these steps:
1. Download the OxygenOS full zip file (tested on 4.0.1 & above)
2. Open TWRP.
3. When It asks for password, cancel it.
4. Click "Read Only" button.
5. Install the OxygenOS zip file.
6. Reboot.
7. The OS may misbehave.
8. Open TWRP again. & Boom! No encryption password.
9. Connect to PC and copy the Important data.
10. Flash Any ROM now.
Click to expand...
Click to collapse
Does this only affect the TWRP -encryption, because when you set your lockscreen password (for the auto-encrypted userdata partition in Android 10, for example) the data can't be decrypted without this password..?
I have discovered another security issue however on a rooted device:
On my Magisk-rooted and encrypted Note 10+/Exynos (Android 10) I just found out, that the userdata (data/data ) partition is UNENCRYPTED and fully readable when viewed with an ADB viewer from my PC although the device is in lockscreen mode / locked!
This doesn't happen after reboot before the first unlock! After the device has been unlocked, accessed via ADB and re-locked (but not rebooted) it is (still) unencrypted, even after rebooting the PC!
Here the lockscreen password would not make much sense at every screenlock - it just unlocks the screen which can be bypassed and all data can be read via ADB anyway - it would only make sense once at boot. Is there a way to have two passwords (1 at boot and an easier one at screenlock) for example?
Is this issue related to Magisk? And can it be fixed?
monicaONxda said:
Does this only affect the TWRP -encryption, because when you set your lockscreen password (for the auto-encrypted userdata partition in Android 10, for example) the data can't be decrypted without this password..?
I have discovered another security issue however on a rooted device:
On my Magisk-rooted and encrypted Note 10+/Exynos (Android 10) I just found out, that the userdata (data/data ) partition is UNENCRYPTED and fully readable when viewed with an ADB viewer from my PC although the device is in lockscreen mode / locked!
This doesn't happen after reboot before the first unlock! After the device has been unlocked, accessed via ADB and re-locked (but not rebooted) it is (still) unencrypted, even after rebooting the PC!
Here the lockscreen password would not make much sense at every screenlock - it just unlocks the screen which can be bypassed and all data can be read via ADB anyway - it would only make sense once at boot. Is there a way to have two passwords (1 at boot and an easier one at screenlock) for example?
Is this issue related to Magisk? And can it be fixed?
Click to expand...
Click to collapse
Anyone with thoughts on this...?
monicaONxda said:
Anyone with thoughts on this...?
Click to expand...
Click to collapse
There are two, separate passwords. One for the encryption and one for the lock screen. And they don't have to be the same.
If you remove the encryption by formatting /data and then boot up on stock OOS, it will encrypt /data with a default password. TWRP can decrypt /data because it knows the default password that's used.
When you set the lock screen password you have the option to set the encryption password to be the same or not.
So, you could set the lock screen and encryption password to be something and then change the lock screen password only to be something different.
ADB can only access /data after it has been decrypted, ie the phone has booted up. But only if: 1. ADB is enabled, 2. You have given permission on your phone to trust the PC connecting to the phone.
So, there's no back doors here. If you have set an encryption password, you can't access the data without having entered the password. And you can't access the phone data without entering the lock screen password. And you can't access the data via ADB unless you have given the specific PC permission from your phone.
Of course, if you use the default encryption password and have TWRP installed, you might just as well not have a password at all. But that's up too you.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
When you set the lock screen password you have the option to set the encryption password to be the same or not.
So, you could set the lock screen and encryption password to be something and then change the lock screen password only to be something different.
Click to expand...
Click to collapse
For which roms is this working? I guess this behaviour is rom spefic. E.g. for all lineageos 15.1 and 16.0 roms and all roms based on tje same code base, the above procedure (setting the lockscreen passphrase without the boot passphrase checkbox set) will reset the boot passphrase to "default_password".
The only way I know of to get a seperate passphrase for boot and lockscreen on los15, los16 and roms based on these is this:
https://forum.xda-developers.com/on...eplus-3-3t-t3866517/post80390263#post80390263
nvertigo67 said:
For which roms is this working? I guess this behaviour is rom spefic. E.g. for all lineageos 15.1 and 16.0 roms and all roms based on tje same code base, the above procedure (setting the lockscreen passphrase without the boot passphrase checkbox set) will reset the boot passphrase to "default_password".
The only way I know of to get a seperate passphrase for boot and lockscreen on los15, los16 and roms based on these is this:
https://forum.xda-developers.com/on...eplus-3-3t-t3866517/post80390263#post80390263
Click to expand...
Click to collapse
'setting the lockscreen passphrase without the boot passphrase checkbox set) will reset the boot passphrase to "default_password"' - Ah, sorry, I didn't realise that. I was saying this based on what I had done on another phone.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
'setting the lockscreen passphrase without the boot passphrase checkbox set) will reset the boot passphrase to "default_password"' - Ah, sorry, I didn't realise that. I was saying this based on what I had done on another phone.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
I'm pretty sure this behavior is rom dependent and not device dependent. E.g.: in los14 and early los15 builds the user was able to set lockscreen passphrase and boot passphrase seperately from rom's settings. This has been removed from aosp (officially because of "security concerns"; but I guess these "concerns" has been too many users with too less knowledge have locked up the boot process).
For me the cryptfs cli is perfectly ok, for the average user the behaviour you've expirienced may feel more comfortable. But the longer I think about, the more I like the seperate setting... YMMV.
Just updated with the February full image using fastboot, editing out the -w from flash-all.bat. Fastboot booted TWRP, and then queued up TWRP, Kernel, Magisk and let all 3 rip. No hitches and back up running rooted and everything working normally. Be sure and read the entire Security Bulletin as there were loads of functional updates not always a part of the monthly updates. :good:
Mine wouldn't flash because unlock_critical reset, now my phone is wiped and won't boot the latest update.
Tb0n3 said:
Mine wouldn't flash because unlock_critical reset, now my phone is wiped and won't boot the latest update.
Click to expand...
Click to collapse
Give Deuces script a try. It has helped a lot of people recover their device from similar situations.
I haven't tried it on Feb update though.
You can get it from Development section. Good luck.
Tb0n3 said:
Mine wouldn't flash because unlock_critical reset, now my phone is wiped and won't boot the latest update.
Click to expand...
Click to collapse
what do you mean "because unlock_critical reset?"
Tb0n3 said:
Mine wouldn't flash because unlock_critical reset, now my phone is wiped and won't boot the latest update.
Click to expand...
Click to collapse
Did you ever unlock critical before you tried the update? Or did this happen after the update?
Can someone here confirm the correct way to upgrade from rooted Jan security update without losing data? Would I
reflash stock recovery
fastboot OTA img
fastboot boot twrp.img
flash twrp.zip
flash kernel
flash magisk last?
Or can I use the full image from the dev site, remove the -w and run the flash-all.bat, then use the steps above? Same result, or is one better than the other? Am I missing any steps here?
Is xposed module working on Feb update?
RampageRR said:
Can someone here confirm the correct way to upgrade from rooted Jan security update without losing data? Would I
reflash stock recovery
fastboot OTA img
fastboot boot twrp.img
flash twrp.zip
flash kernel
flash magisk last?
Or can I use the full image from the dev site, remove the -w and run the flash-all.bat, then use the steps above? Same result, or is one better than the other? Am I missing any steps here?
Click to expand...
Click to collapse
See the OP. Use the full image then add back recovery,kernel,magisk in that order. Yes magisk last.
v12xke said:
Just updated with the February full image using fastboot, editing out the -w from flash-all.bat. Fastboot booted TWRP, and then queued up TWRP, Kernel, Magisk and let all 3 rip. No hitches and back up running rooted and everything working normally. Be sure and read the entire Security Bulletin as there were loads of functional updates not always a part of the monthly updates. :good:
Click to expand...
Click to collapse
Quick question - I have performed the flash-all part and at the end it rebooted and everything is fine (except for no root) - it asks for the encryption password and it works with my normal password.
Then I boot TWRP with "fastboot boot twrp-3.2.1-0-taimen.img" and that again works just fine but only to the point where it asks for the password - which here is NOT working? Just a few hours ago the same twrp was working fine with the exact same password (since I did a full backup in advance), and the password is obviously working fine in Android itself, it is only in TWRP where is no longer working???
xclub_101 said:
Quick question - I have performed the flash-all part and at the end it rebooted and everything is fine (except for no root) - it asks for the encryption password and it works with my normal password. Then I boot TWRP with "fastboot boot twrp-3.2.1-0-taimen.img" and that again works just fine but only to the point where it asks for the password - which here is NOT working? Just a few hours ago the same twrp was working fine with the exact same password (since I did a full backup in advance), and the password is obviously working fine in Android itself, it is only in TWRP where is no longer working???
Click to expand...
Click to collapse
I don't really know what went wrong. What do you mean it asks for the encryption password?? If you have some kind of boot encryption set, maybe that is is. My encrypted unit never asks me for a password. I have an unlock screen PIN and that is all. When I flash-all, I wait for the flash to finish (knowing it will reboot) and at the right time hold the volume down button to get me right back into the bootloader. I do not allow it to boot into the OS until I fastboot boot twrp and have never had TWRP refuse my password. Maybe it has something to do with you allowing it to boot into the OS first? Anyway from that "booted" instance of TWRP, I then queue up twrp.zip, kernel.zip, magisk.zip and once they are added, I let TWRP flash all 3. You may want to take this over to the TWRP thread where others have had the PIN issue as well. Some are confirming temporarily removing your PIN/fingerprints fixes it. I have never removed my PIN or fingerprints before or after flashing?
v12xke said:
I don't really know what went wrong. What do you mean it asks for the encryption password?? If you have some kind of boot encryption set, maybe that is is. My encrypted unit never asks me for a password. I have an unlock screen PIN and that is all. When I flash-all, I wait for the flash to finish (knowing it will reboot) and at the right time hold the volume down button to get me right back into the bootloader. I do not allow it to boot into the OS until I fastboot boot twrp and have never had TWRP refuse my password. Maybe it has something to do with you allowing it to boot into the OS first? Anyway from that "booted" instance of TWRP, I then queue up twrp.zip, kernel.zip, magisk.zip and once they are added, I let TWRP flash all 3. You may want to take this over to the TWRP thread where others have had the PIN issue as well. Some are confirming temporarily removing your PIN/fingerprints fixes it. I have never removed my PIN or fingerprints before or after flashing?
Click to expand...
Click to collapse
Yes, it is quite weird.
A few more questions - when you boot your normal Android - do you first get a question about any password there? Since if you don't - your system probably uses the default Android encryption password (which last time when I was looking was literally "default_password" without the quotes).
Why do you still need to flash the kernel - are you using a custom kernel?
xclub_101 said:
Yes, it is quite weird.
A few more questions - when you boot your normal Android - do you first get a question about any password there? Since if you don't - your system probably uses the default Android encryption password (which last time when I was looking was literally "default_password" without the quotes). Why do you still need to flash the kernel - are you using a custom kernel?
Click to expand...
Click to collapse
I never get prompted for a password upon booting, and my phone is encrypted. I think you are probably on to the real reason your twrp is not accepting your PIN. Older Nexus phones had boot encryption with a password but since the Pixel line I thought it was removed? When discussing this further in the TWRP thread I think you should be comparing notes with others on this boot encryption, because I don't have it. I'm reading something now about direct boot and fbe.
Yes I use a custom kernel, always have. I like being able to monitor and control my system and gestures, vibration, etc. I like the kernel monitor (and battery monitor) that goes along with EX Kernel. Highly recommended. Good luck to you.
i sideloaded the update to my verizon version pixel 2 xl, and havent noticed anything, mainly just a run of the mill security update. i read that pixel core has been extended to a few apps.
v12xke said:
I never get prompted for a password upon booting, and my phone is encrypted. I think you are probably on to the real reason your twrp is not accepting your PIN. Older Nexus phones had boot encryption with a password but since the Pixel line I thought it was removed? When discussing this further in the TWRP thread I think you should be comparing notes with others on this boot encryption, because I don't have it. I'm reading something now about direct boot and fbe.
Yes I use a custom kernel, always have. I like being able to monitor and control my system and gestures, vibration, etc. I like the kernel monitor (and battery monitor) that goes along with EX Kernel. Highly recommended. Good luck to you.
Click to expand...
Click to collapse
Thank you for the info!
The encryption is still a weird point - and I believe is still linked by default to the "screen lock password" as described at https://www.xda-developers.com/how-to-manually-change-your-android-encryption-password/ - but I am not yet convinced that I should remove my existing password since the system is telling me that removing it will remove all fingerprints that I have added and mark the system as unsecure for Pay.
What I wonder is if I should go ahead with just writing Magisk without decrypting the user data partition - after all Magisk should not be touching either the system nor the user data partition, so it could work just fine?
Did they remove the setting to turn on Pixel Visua Core in Developer settings?
xclub_101 said:
Thank you for the info!
The encryption is still a weird point - and I believe is still linked by default to the "screen lock password" as described at https://www.xda-developers.com/how-to-manually-change-your-android-encryption-password/ - but I am not yet convinced that I should remove my existing password since the system is telling me that removing it will remove all fingerprints that I have added and mark the system as unsecure for Pay.
What I wonder is if I should go ahead with just writing Magisk without decrypting the user data partition - after all Magisk should not be touching either the system nor the user data partition, so it could work just fine?
Click to expand...
Click to collapse
I guess my question is why do you have an encryption password at boot? My phone boots up to a lockscreen. I enter my PIN and that's it. Maybe I'm misunderstanding and you are calling my PIN your boot encryption password.... do you then have a lockscreen and enter a separate PIN? As for Magisk it doesn't decrypt the data partition or anything else. I always install it by flashing the zip file in TWRP and you have no options there. It just does it's thing and installs Magisk Manager as an app, so when you boot up System, MM is in your app drawer. You can configure it from there. My setup has always passed SafetyNet but I don't use/want Pay.
v12xke said:
I guess my question is why do you have an encryption password at boot? ...
Click to expand...
Click to collapse
Good question - I would normally expect that to be required when Android itself needs to decrypt first time after boot the user data partition? Which up to that point during the boot process is not otherwise needed?
The fact that on some systems is not required suggests to me that Android (like maybe also TWRP) first tries "default_password" and that works?
Mikulec said:
Did they remove the setting to turn on Pixel Visua Core in Developer settings?
Click to expand...
Click to collapse
yes.
djkinetic said:
i sideloaded the update to my verizon version pixel 2 xl, and havent noticed anything, mainly just a run of the mill security update. i read that pixel core has been extended to a few apps.
Click to expand...
Click to collapse
Its quite a bit more than the run of the mill security update.
visual core is now extended to any app, not just a few (so long as they target API level 26, Oreo).
i sideloaded the update like I always do. All updated normally and all functioning as expected. After sideloading the update I booted the twrp-3.2.1-0-taimen.img, it booted and when I entered my pin, which i have been using, in TWRP it would not accept my pin. I rebooted into the boot.img 3 times same issue. I removed my pin and TWRP functioned as expected. I installed TWRP.zip and rebooted recovery. Back in TWRP flashed Kernel, and Magisk and no issues. This was the first time I had issues entering my pin on booting TWRP.img
Good evening,
I have the following situation in TWRP:
1. I have waited 7 days to release the OEM.
2. After that I installed TWRP via ODIN, and logged into Recovery.
3. As usual the DATA folder was unavailable (Encrypted) and had to do FORMAT DATA, placing yes, etc ....
4. After that I was able to access, I installed Magisk and RMM STATE.
*********I also tested using SuperSu, NO-VERITY, and RMM STATE, and the same thing happened.
5. Everything wonderful, I accessed the system, the OEM remains unlocked, in the download mode has no PRE NORMAL, I can access ROOT softwares a marvel.
6. But here comes the problem, whenever I enter the TWRP it is with the DATA folder unavailable, that is, I have to redo FORMAT DATA.
7. If you do FORMAT, it restarts the procedure from the beginning.
The version of TWRP that I use is correct, the ROM is last STOCK Brazil ZTO.
I have no idea what to do.
Link to TWRP I'm downloading
https://twrp.me/samsung/samsunggalaxys8.html
I read the link below the information below, it would have some connection with the problem:
This device uses dm-verity!
This means that if you allow the system to be modified, it will prevent you from being able to boot if you are using the kernel stock. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has disabled dm-verity in the fstab.
Problem solved through link:
https://forum.xda-developers.com/ga...-twrp-oreo-t3769254/post76036701#post76036701
You are asking for help, and it just so happens that there is a forum meant specifically for that.
SirSoviet said:
You are asking for help, and it just so happens that there is a forum meant specifically for that.
Click to expand...
Click to collapse
Good afternoon.
Would you link to it?
'Cause I thought I'd go in with recovery.
I have tested everything I read in the forum and it is not right.
Problem solved through link:
https://forum.xda-developers.com/ga...-twrp-oreo-t3769254/post76036701#post76036701
Is anyone able to run TWRP on P580 running Oreo?
Im having problems with my Tab stuck on a black screen instead of recovery mode.
Please help.
Thanks!!
I found a solution if you don't need TWRP, only Magisk or Root. (Using sm-p580 german version P580KXU1CRJ7)
Short Version:
Install Magisk without TWRP with odin in AP section(google it)
Problem is: Once booted up it will tell you that you have to reset your device because the system recognizes that you modified something.
Solution: Just click on the reset button( Magisk will still be there afterwards).
Long Version
Flash the Oreo firmware onto your device.
Set it up (turn on USB debugging) (or dont, I believe you dont need it for download mode ?)
Unzip the AP part of the firmware you have flashed. You may need a modified version of 7-zip, I needed it, because it couldn't unzip lz4.
Google mcmilk 7 zip and download the github release (I hope I'm allowed to reference it, CREDIT goes to MILKY)
You need the boot.img.
Now install Magisk Manager apk.
Under its settings check " .img.tar" under "return of patched boot-images" (Something like that, mine is german)
Click on install in Magisk Manager apk.
Select make thing with boot img, use the boot.img you have extracted and copied onto your phone.
Magisk will create new patched boot img automatically, copy the finished one u find under your main storage in downloads to your pc.
Go into download mode and flash new boot.img with odin using the AP tab.
Now do the things I described in the Short Version
Afterwards install Magisk Manager Apk.
You need internet connection, because it will prompt you to allow installing additional stuff.
A message from some Security App will appear, that something is wrong.
And your device will get laggy and restart.
After that the lag will disapear
I like to use Bk disabler to remove bloatware/ other stuff to flash or back up your device
(Please dont remove any of the 3 phone apks, on Nougat it worked to remove two of them, but oreo will continuously give an error message <- I found out that you can uninstall two of them, but dont uninstall the storagedial-programm thats what gives the errormessage.)
Hope it will help you!
Worked !!!
Thank you dear. Its worked for mine in p585 oreo android....
Anyone can search mcmilk 7zip in google and download program to extract boot.img.lz4 and get boot.img :good:
use the last TWRP for Oreo.
old version makes black screen or red stripes.
go in download-mode (power+home+vol-) and install the last TWRP over with Odin.
for Oreo use the last Odin 3.13
it tested, i had the same problem :fingers-crossed:
Latest twrp dose not worked on my device but this solution work fine
I can confirm that this method does work. I used it on my SM-P580 yesterday. I would suggest that you first backup your all of your apps, contacts, photos, etc using SmartSwitch. You will need to restore everything after the tablet tells you that it needs to be reset because it wipes everything. After the restore, you will need to enter all of your accounts and passwords again but at least all of the data will be back.
amosdinh said:
I found a solution if you don't need TWRP, only Magisk or Root. (Using sm-p580 german version P580KXU1CRJ7)
Short Version:
Install Magisk without TWRP with odin in AP section(google it)
Problem is: Once booted up it will tell you that you have to reset your device because the system recognizes that you modified something.
Solution: Just click on the reset button( Magisk will still be there afterwards).
Long Version
Flash the Oreo firmware onto your device.
Set it up (turn on USB debugging) (or dont, I believe you dont need it for download mode ?)
Unzip the AP part of the firmware you have flashed. You may need a modified version of 7-zip, I needed it, because it couldn't unzip lz4.
Google mcmilk 7 zip and download the github release (I hope I'm allowed to reference it, CREDIT goes to MILKY)
You need the boot.img.
Now install Magisk Manager apk.
Under its settings check " .img.tar" under "return of patched boot-images" (Something like that, mine is german)
Click on install in Magisk Manager apk.
Select make thing with boot img, use the boot.img you have extracted and copied onto your phone.
Magisk will create new patched boot img automatically, copy the finished one u find under your main storage in downloads to your pc.
Go into download mode and flash new boot.img with odin using the AP tab.
Now do the things I described in the Short Version
Afterwards install Magisk Manager Apk.
You need internet connection, because it will prompt you to allow installing additional stuff.
A message from some Security App will appear, that something is wrong.
And your device will get laggy and restart.
After that the lag will disapear
I like to use Bk disabler to remove bloatware/ other stuff to flash or back up your device
(Please dont remove any of the 3 phone apks, on Nougat it worked to remove two of them, but oreo will continuously give an error message <- I found out that you can uninstall two of them, but dont uninstall the storagedial-programm thats what gives the errormessage.)
Hope it will help you!
Click to expand...
Click to collapse
Im not sure if this post belongs here, you link to the T580 TWRP, not the P580.
Is that one compatible with P580?
nill3bor said:
use the last TWRP for Oreo.
old version makes black screen or red stripes.
go in download-mode (power+home+vol-) and install the last TWRP over with Odin.
for Oreo use the last Odin 3.13
it tested, i had the same problem :fingers-crossed:
Click to expand...
Click to collapse
If I do this, will I be able to mount my SD Card as internal storage? 16gb just isnt enough on this tablet.
Do you have to be on oreo already for this to work I'm still on 7.0 and with my system modified I can't upgrade normally
This method root my P585 device but the sim card not working anymore until I odin official rom
also twrp-3.2.3-4-gtaxllte-OMNI6 not work and freeze on Samsung logo
there is no method to root android Oreo P585 Realllllly????
khatkhatik said:
This method root my P585 device but the sim card not working anymore until I odin official rom
also twrp-3.2.3-4-gtaxllte-OMNI6 not work and freeze on Samsung logo
there is no method to root android Oreo P585 Realllllly????
Click to expand...
Click to collapse
This one worked for me on a P585Y. You just have to skip the steps below.
A message from some Security App will appear, that something is wrong.
And your device will get laggy and restart.
After that the lag will disapear
Click to expand...
Click to collapse
It will also show on the Device Maintenance, just ignore the warning.
You can freeze some of the system apps to prevent it from showing on the notification again.
amosdinh said:
I found a solution if you don't need TWRP, only Magisk or Root. (Using sm-p580 german version P580KXU1CRJ7)
Short Version:
Install Magisk without TWRP with odin in AP section(google it)
Problem is: Once booted up it will tell you that you have to reset your device because the system recognizes that you modified something.
Solution: Just click on the reset button( Magisk will still be there afterwards).
Long Version
Flash the Oreo firmware onto your device.
Set it up (turn on USB debugging) (or dont, I believe you dont need it for download mode ?)
Unzip the AP part of the firmware you have flashed. You may need a modified version of 7-zip, I needed it, because it couldn't unzip lz4.
Google mcmilk 7 zip and download the github release (I hope I'm allowed to reference it, CREDIT goes to MILKY)
You need the boot.img.
Now install Magisk Manager apk.
Under its settings check " .img.tar" under "return of patched boot-images" (Something like that, mine is german)
Click on install in Magisk Manager apk.
Select make thing with boot img, use the boot.img you have extracted and copied onto your phone.
Magisk will create new patched boot img automatically, copy the finished one u find under your main storage in downloads to your pc.
Go into download mode and flash new boot.img with odin using the AP tab.
Now do the things I described in the Short Version
Afterwards install Magisk Manager Apk.
You need internet connection, because it will prompt you to allow installing additional stuff.
A message from some Security App will appear, that something is wrong.
And your device will get laggy and restart.
After that the lag will disapear
I like to use Bk disabler to remove bloatware/ other stuff to flash or back up your device
(Please dont remove any of the 3 phone apks, on Nougat it worked to remove two of them, but oreo will continuously give an error message <- I found out that you can uninstall two of them, but dont uninstall the storagedial-programm thats what gives the errormessage.)
Hope it will help you!
Click to expand...
Click to collapse
this works great! thanks!
2 side notes on the process:
1. Magisk no longer provides " .img.tar" patched files, so a tool like "Tar-tool" is required to convert the file from the ".img" type. The patched file should be renamed "boot.img" before conversion in order to be succesfully flashed by Odin.
2. like f4vr said, freeze the apps that give the error notification or just disable the specific notification. Hiding them in Magisk Hider does not seem to work
Cheers, and thanks again for the guide!
Hello Gyus,
I managed to root the device with the method posted by @amosdinh (Thank you so much). Now I'm trying to configure adoptable storage. So far I didn't achieve this goal. ADB commands doesn't work and I can't install the ASPlugin.zip needed by Root Essentials to set adoptable storage by the app.
TWRP for P585 is corrupted, gives blue/red lines screen. The dev that maintains the code is absent since march. I'm out of luck on this. If anyone have a idea to get adoptable storage on this device while using Oreo, please comment.
Thanks!
---------- Post added at 11:17 AM ---------- Previous post was at 11:11 AM ----------
artaeun said:
this works great! thanks!
2 side notes on the process:
1. Magisk no longer provides " .img.tar" patched files, so a tool like "Tar-tool" is required to convert the file from the ".img" type. The patched file should be renamed "boot.img" before conversion in order to be succesfully flashed by Odin.
2. like f4vr said, freeze the apps that give the error notification or just disable the specific notification. Hiding them in Magisk Hider does not seem to work
Cheers, and thanks again for the guide!
Click to expand...
Click to collapse
Just renaming magisk_patched.img to boot.img and adding to .tar file by 7zip worked for me.
We should ask a dev to update twrp for android 8.1
khatkhatik said:
This method root my P585 device but the sim card not working anymore until I odin official rom
also twrp-3.2.3-4-gtaxllte-OMNI6 not work and freeze on Samsung logo
there is no method to root android Oreo P585 Realllllly????
Click to expand...
Click to collapse
Same freeze for me with the Omni - can't do anything outside of access download mode
Same Problem
cmzizi said:
Is anyone able to run TWRP on P580 running Oreo?
Im having problems with my Tab stuck on a black screen instead of recovery mode.
Please help.
Thanks!!
Click to expand...
Click to collapse
I have the same problem. It just keep getting to the bad TWRP, it seems that it does not work with the SM-P580. I had to flash stock firmware to get it back to work.
luinkazofeifa said:
I have the same problem. It just keep getting to the bad TWRP, it seems that it does not work with the SM-P580. I had to flash stock firmware to get it back to work.
Click to expand...
Click to collapse
Really wish this wasn't the case. I'd actually keep this thing if it had a working TWRP.
On my SM-P580 I used Odin and TWRP I don't get the black screen but when I reboot to get into TWRP recovery mode it shows the padlock and says swipe to unlock. Tried many times bit cannot swipe and cannot get past this. All I want is to be able to use the SD card as internal storage. HELP???? Thanks!!
luinkazofeifa said:
I have the same problem. It just keep getting to the bad TWRP, it seems that it does not work with the SM-P580. I had to flash stock firmware to get it back to work.
Click to expand...
Click to collapse
thanks in advanced
where can i find stock firmware?
I've just installed magisk using TWRP via command line. P580
I've just installed magisk using TWRP via command line.
Read the entire post before trying this yourself.
I installed the latest TWRP, the one that bugs and doesn't display anything, this allows to root without wiping data. I'm running the latest korean firmware for P580.
Just do this:
1. Launch TWRP and INMEDIATELY LOCK YOUR SCREEN. (I got ghost stripes that disappeared after 2 days when testing this, work with low light so you can notice your screen whenever it tuens on) Please don't forget this point, don't [temporarily] damage your screen as I did.
2. adb push Magisk-v[Current version].zip external_sd
3. adb shell
4. twrp install external_sd/Magisk-v[Current version].zip
After this you just need to install MagiskManager-v[Current version].apk and you will be all done.
But there is one thing...
If you ever get into recovery mode, there is no way out without using adb as far as I know. You can launch download mode and cancel it but you'll boot back to TWRP.
When in twrp touching your screen or any button will wake the device up and will start burning the ghost image to your screen.
So if you know of a method for rebooting to system without using adb, please let me know.
Also a solution for this would be to flash back the stock recovery, wich may or may not force to wipe system, that something that needs to be tested tho.
Update: Ok so, you can use a handy tool called MTKroot on recovery.img.lz4 to get recovery.img, then use 7z to pack it into a tar file and flash that tar file with odin (AP, same as TWRP)
This way you will not have a 0.001% chance of random boot into recovery mode and damage your screen