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
Related
All,
Thanks in advance for any help you can provide. I have a Nexus 4 that I rooted and installed CWM recovery on, but I never installed any new kernels, ROMs, or radios. I'm currently on 4.4.4 and I want to upgrade to Lollipop. The OTA upgrade failed. So I tried returning to stock recovery and doing both the OTA and adb sideloading the OTA zip. Both fail.
The error message is "Package expects build fingerprint of google/occam/mako:4.4.4/KTU84P/1227136:user/release-keys or google/occam/mako:5.0/LRX21T/1576899:user/release-keys; this device has google/occam/mako:4.4/KRT160/907817:user/release-keys." (But I definitely have 4.4.4 on my phone, not 4.4.0.)
The extra difficulty is that I really, really do not want to wipe my phone. I have a lot of apps with a lot of configuration and other user data. So is there anything I can do? I guess I should try unrooting somehow? Or is there some other zip I can download that, through some type of recovery, will install the OTA without doing this check and also without wiping me?
Thanks again!
moriarty00 said:
All,
Thanks in advance for any help you can provide. I have a Nexus 4 that I rooted and installed CWM recovery on, but I never installed any new kernels, ROMs, or radios. I'm currently on 4.4.4 and I want to upgrade to Lollipop. The OTA upgrade failed. So I tried returning to stock recovery and doing both the OTA and adb sideloading the OTA zip. Both fail.
The error message is "Package expects build fingerprint of google/occam/mako:4.4.4/KTU84P/1227136:user/release-keys or google/occam/mako:5.0/LRX21T/1576899:user/release-keys; this device has google/occam/mako:4.4/KRT160/907817:user/release-keys." (But I definitely have 4.4.4 on my phone, not 4.4.0.)
The extra difficulty is that I really, really do not want to wipe my phone. I have a lot of apps with a lot of configuration and other user data. So is there anything I can do? I guess I should try unrooting somehow? Or is there some other zip I can download that, through some type of recovery, will install the OTA without doing this check and also without wiping me?
Thanks again!
Click to expand...
Click to collapse
OTA wants complete stock and obviously it doesn't think so about your phone. One option could be to back up to the cloud or some place outside the phone with TiBu (or whatever backup app you trust), then flash lollipop and try restore from TiBu. Another option would be to unroot (Supersu has an option to completely unroot), then retry.
Actually, I figured out what works! This was on a stock rooted device with stock recovery, but I bet it would work with custom recovery too. Instructions modified from https://pay.reddit.com/r/nexus4/comments/1qny3f/howto_update_your_stock_w_lte_nexus_4_without/ .
1. Download the image you want from https://developers.google.com/android/nexus/images . Extract it, extract the .zip file inside it too, and collect all of the .img files into one folder.
2. adb reboot bootloader (and wait until the bootloader comes up)
3. fastboot flash bootloader bootloader-mako-makoz30f.img (or whatever file has a similar name, if you got a different image than I did)
4. fastboot reboot-bootloader (and wait until the bootloader comes back up)
5. fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.04.img (or whatever file has a similar name, if you got a different image than I did)
6. fastboot reboot-bootloader (and wait until the bootloader comes back up)
7. fastboot flash boot boot.img
8. fastboot flash recovery recovery.img
9. fastboot flash system system.img
10. fastboot format cache
11. fastboot reboot
12. Don't panic unless you've seen the startup animation for at least 15 minutes without anything else happening.
I lost root, but I imagine re-custom-recoverying and re-rooting won't be any harder than the first time around.
Hi moriarty00,
I'm going to try the same procedure, thank you for posting this.
Can you confirm that your data and app are safe after the upgrade?
moriarty00 said:
Actually, I figured out what works! This was on a stock rooted device with stock recovery, but I bet it would work with custom recovery too. Instructions modified from https://pay.reddit.com/r/nexus4/comments/1qny3f/howto_update_your_stock_w_lte_nexus_4_without/ .
1. Download the image you want from https://developers.google.com/android/nexus/images . Extract it, extract the .zip file inside it too, and collect all of the .img files into one folder.
2. adb reboot bootloader (and wait until the bootloader comes up)
3. fastboot flash bootloader bootloader-mako-makoz30f.img (or whatever file has a similar name, if you got a different image than I did)
4. fastboot reboot-bootloader (and wait until the bootloader comes back up)
5. fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.04.img (or whatever file has a similar name, if you got a different image than I did)
6. fastboot reboot-bootloader (and wait until the bootloader comes back up)
7. fastboot flash boot boot.img
8. fastboot flash recovery recovery.img
9. fastboot flash system system.img
10. fastboot format cache
11. fastboot reboot
12. Don't panic unless you've seen the startup animation for at least 15 minutes without anything else happening.
I lost root, but I imagine re-custom-recoverying and re-rooting won't be any harder than the first time around.
Click to expand...
Click to collapse
Wow, a 12-step program
I simply rolled back my changes, and applying the OTA was as simple as pressing the "restart and install" button Here are some steps:
I used the app Flashify from Play Store to flash stock 4.4.4 recovery. I downloaded the stock factory image from google's own site (this one), used 7zip to extract the archives (tgz and tar), found "recovery.img" and transfered that to my phone. Then chose that file in Flashify.
Uninstalled all apps that made system changes, like Xposed framework and mods, BetterBatteryStats etc.
Removed Root with SuperSU cleanup function
Rebooted for good measure and apply OTA from notification - wait an hour or two for it to complete
Profit (do we still say that on the internet? Getting old here...)
I don't know if certain ways to get root will break the OTA. I used towel-root, and apparently SuperSU was able to undo that completely.
DrDruge said:
Hi moriarty00,
I'm going to try the same procedure, thank you for posting this.
Can you confirm that your data and app are safe after the upgrade?
Click to expand...
Click to collapse
Yup, perfectly safe! Just make sure not to flash other images, like userdata.img.
venu123 said:
OTA wants complete stock and obviously it doesn't think so about your phone. One option could be to back up to the cloud or some place outside the phone with TiBu (or whatever backup app you trust), then flash lollipop and try restore from TiBu. Another option would be to unroot (Supersu has an option to completely unroot), then retry.
Click to expand...
Click to collapse
If I unroot with Supersu how do I get root back?
moriarty00 said:
Yup, perfectly safe! Just make sure not to flash other images, like userdata.img.
Click to expand...
Click to collapse
Thank you!
Unfortunately the steps did not work for me, maybe I had some irreversible modifications or I had followed a different rooting procedure.
Or maybe I made a mistake in the upgrading steps.
Anyway, I had to flash the whole ROM and now everything is working fine.
Hey!
Basically I have similar problem with upgrading from 4.4.4 to 5.0 using OTA. Log from TWRP says:
Package expects build fingerprint of google/occam/mako:4.4.4/KTU84P/1227136:user/release-keys or google/occam/mako:5.0/LRX21T/1576899:user/release-keys; this device has google/occam/mako:4.3/JWR66V/737497:user/release-keys.
Click to expand...
Click to collapse
Phone has been rooted using Nexus Root Toolkit. And as long as there wouldn't be a problem with flashing using adb and wiping all data, there is one setback... My nexus is somehow broken. Communication via USB does not work, at all. Neither phone nor PC sees other device. Certified LG service centre nearby said that it is problem with main board, so generally repair is unprofitable.
So question is: How do I update to 5.0 and then root, without USB connection to my PC?
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.
Since the May Security Update, there have been changes.
I won't get into that here, as there are already a number of threads where the new AVB process and what it means for updates and root is discussed at length on this forum.
For example - https://forum.xda-developers.com/an...-boot-images-android-verified-t3600606/page16
I'm just going to outline my process for installing the new security updates via full image (Not OTA) and then rooting the phone via TWRP.
A few things to bear in mind first.
You will need to have the following:
0. Know how to use ADB/Fastboot and have them installed. If not, you should please do some research first.
1. Full Image for Pixel (https://developers.google.com/android/ota)
2. TWRP boot image and zip files (https://dl.twrp.me/sailfish/)
3. Latest SuperSU by Chainfire (https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip)
4. VerifiedBootSigner by Chainfire (https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606)
Also...I don't make use of the vendor provided flashing scripts, I simply use the script commands and eliminate the '-w' flag manually.
*The SuperSu, TWRP and VerifiedBootSigner zips need to be saved to your phone*
From the bootloader ->
fastboot flash bootloader bootloader-sailfish-8996-012001-1704121145.img
fastboot reboot-bootloader
fastboot flash radio radio-sailfish-8996-012901-1702171013.img
fastboot reboot-bootloader
fastboot update image-sailfish-njh47b.zip
***The phone will automatically reboot at this phase and you will need to reboot back into the bootloader to continue either by manual means or by using "adb reboot-bootoader"
fastboot boot twrp-3.0.2-0-RC1-fastboot-sailfish.img
from TWRP (using files saved on phone) ->
TWRP install twrp-pixel-installer-sailfish-3.1.0-0RC2.zip
reboot TWRP
TWRP install SR3-SuperSU-v2.79-SR3-20170114223742.zip
TWRP install VerifiedBootSigner-v8.zip
reboot system
Edit - You should also update your SuperSU binary to 2.82 from within the app once you're booted into Android.
You're Done!
DISCLAIMER
I didn't create any of these files or take credit for them in anyway. This is simply an instructional that I hope will help many of you.
It requires some proficiency in using fastboot and TWRP.
If you don't know what you're doing and mess up your device, I take no responsibility for your actions or the results.
gonna give it a try, thanks dude.
The only issue is that after updating the system image the phone will auto reboots so you have no chance to input the fastboot command.
churchmice said:
The only issue is that after updating the system image the phone will auto reboots so you have no chance to input the fastboot command.
Click to expand...
Click to collapse
You're right.
I should update the instructions about that.
The reboot isn't really an issue, but it does add an additional step and some inconvenience.
churchmice said:
The only issue is that after updating the system image the phone will auto reboots so you have no chance to input the fastboot command.
Click to expand...
Click to collapse
phonepersonality said:
You're right.
I should update the instructions about that.
The reboot isn't really an issue, but it does add an additional step and some inconvenience.
Click to expand...
Click to collapse
fastboot has an option to skip reboot:
--skip-reboot
so the command would be something like: fastboot --skip-reboot update image-sailfish-njh47b.zip
Can't we just use ota? Like:
- sideload ota
- let reboot
- reboot bootloader
- boot twrp rc1
- flash twrp rc1
- flash bootloader signer
- reboot recovery
- flash root
- optional kernel
- flash bootloader signer
- reboot
I ask because I always did this and never got problems, so if anyone tried/wanna try just let me know
TENN3R said:
Can't we just use ota? Like:
- sideload ota
- let reboot
- reboot bootloader
- boot twrp rc1
- flash twrp rc1
- flash bootloader signer
- reboot recovery
- flash root
- optional kernel
- flash bootloader signer
- reboot
I ask because I always did this and never got problems, so if anyone tried/wanna try just let me know
Click to expand...
Click to collapse
If you'd like.
I don't like to use the OTA files, personally.
Will the OTA even work with root ? I thought OTA is like taking the update over the air and if the system files are altered it fails ? I recently re-flashed the stock image but I may try this next time. The Pixel has become more difficult to update and in the past when I have even tried to reflash the stock boot it starts wiping my phone.
mikeprius said:
Will the OTA even work with root ? I thought OTA is like taking the update over the air and if the system files are altered it fails ? I recently re-flashed the stock image but I may try this next time. The Pixel has become more difficult to update and in the past when I have even tried to reflash the stock boot it starts wiping my phone.
Click to expand...
Click to collapse
That is weird. Never had a problem with my phone being wiped except when flashing other than manually. I always flash mine one at a time, and never have a problem. I like to be in control but I am old lol! I've been wiped before.
Tulsadiver said:
That is weird. Never had a problem with my phone being wiped except when flashing other than manually. I always flash mine one at a time, and never have a problem. I like to be in control but I am old lol! I've been wiped before.
Click to expand...
Click to collapse
I did manual fastboot commands earlier, not the autoscript, automatically wiped my data.
---------- Post added at 05:43 PM ---------- Previous post was at 05:31 PM ----------
Not sure what happened. Just pretty much treated like a dirty flash and fastboot flash the image. It must have detected the prior and wiped it. Had the thing rooted which is the only thing I can think of, it was not untouched stock.
mikeprius said:
Will the OTA even work with root ? I thought OTA is like taking the update over the air and if the system files are altered it fails ? I recently re-flashed the stock image but I may try this next time. The Pixel has become more difficult to update and in the past when I have even tried to reflash the stock boot it starts wiping my phone.
Click to expand...
Click to collapse
You can update via ota, but you need to download the zip on your pc and sideload it in twrp. After booted up you can re-mod, keeping your data.
Have you deleted the "-w" near the fastboot command in the factory image "flash-all" file? This causes wipe, if you remove it'll skip wipe.
Did anyone else have to install the TWRP 3.1 zip via USB-OTG? After flashing the full factory image for June 2017, rebooting to system, rebooting to bootloader then running fastboot boot twrp3.0.2-RC1.img, I wasn't prompted to enter my password so my user data remained encrypted and I couldn't install the TWRP 3.1 zip from the internal SD card, had to load it on a usb dongle and mount USB-OTG storage.
TENN3R said:
You can update via ota, but you need to download the zip on your pc and sideload it in twrp. After booted up you can re-mod, keeping your data.
Have you deleted the "-w" near the fastboot command in the factory image "flash-all" file? This causes wipe, if you remove it'll skip wipe.
Click to expand...
Click to collapse
I've tried to take out the -w erase flag. I've also tried to reflash the stock boot in the past when reloading a new kernel. Not sure if it is triggering some kind of system default but it just auto wipes. It's not the end of the world, I have everything backed up, I just have to restore everything. Just have not had any luck
Guys I can confirm also sideload ota method works flawlessly, 7.1.2 june rooted
Does anyone know if once rooted and bootloader signed via this method Netflix becomes available again?
Coronado is dead said:
Does anyone know if once rooted and bootloader signed via this method Netflix becomes available again?
Click to expand...
Click to collapse
A phone setup according to this thread is not expected to pass the Safetynet check. I've been updating with SuperSU using FlashFire, and my phone just shows Netflix VR in the Play Store. The Magisk discussions are primarily the threads that have been active recently for having root and passing Safetynet.
Pixel discussion:
https://forum.xda-developers.com/pixel/how-to/magisk-pixel-t3573845
Pixel XL discussion:
https://forum.xda-developers.com/pixel-xl/how-to/guide-stock-7-1-2-root-safetynet-ok-t3617347
TENN3R said:
You can update via ota, but you need to download the zip on your pc and sideload it in twrp.
Click to expand...
Click to collapse
Could you please elaborate on how to sideload in TWRP? I used to use adb sideload, but maybe your method is easier.
My current steps are:
1) adb reboot recovery
2) adb sideload ota-update.zip
3 Reboot and check if everything is okay (root and TWRP are lost, data are not)
4) adb reboot bootloader
5) fastboot boot TWRP.img
6) Flash TWRP and SuperSU
7) Flash boot signer
8) Reboot
Flitskikker said:
Could you please elaborate on how to sideload in TWRP? I used to use adb sideload, but maybe your method is easier.
My current steps are:
1) adb reboot recovery
2) adb sideload ota-update.zip
3 Reboot and check if everything is okay (root and TWRP are lost, data are not)
4) adb reboot bootloader
5) fastboot boot TWRP.img
6) Flash TWRP and SuperSU
7) Flash boot signer
8) Reboot
Click to expand...
Click to collapse
I use the same method I don't think there are any others
TENN3R said:
I use the same method I don't think there are any others
Click to expand...
Click to collapse
Thanks for confirming.
Does this VerifiedBootSigner-v8.zip apply to the August security patch as well?
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.
Is there a way to get temp root for some time then disable it
Why don't you flash Magisk and then uninstall it?
Depends on what you want to achieve with getting temporary root. If you want to make a backup of your untouched phone, you could try to boot into the latest twrp (test) version or and get temporary root trough an adb shell.
for what purpose?
flamedrops said:
for what purpose?
Click to expand...
Click to collapse
Like to access net cut to remove hackers for some Intruders on my network
Medeon said:
Depends on what you want to achieve with getting temporary root. If you want to make a backup of your untouched phone, you could try to boot into the latest twrp (test) version or and get temporary root trough an adb shell.
Click to expand...
Click to collapse
No I mean on Android not twrp if correctly understood.
And that adb shell how to do this ?? Please answer me
batman957 said:
No I mean on Android not twrp if correctly understood.
And that adb shell how to do this ?? Please answer me
Click to expand...
Click to collapse
First I would like to say, do your research before you post a question here. The answers to your questions are literally one Google or XDA search away from you. Having said that, your best bet would probably be Kingoroot although I can't promise you it will work. I have tried it once on an older phone, but I did not succeed. But you could try.
If it's not working, the only way to gain root access is to unlock the bootloader of your phone. This will void your warranty. It's up to you to decide whether it's worth it or not. It will probably take a week or longer for Xiaomi to grant you to unlock the bootloader.
Here is a noob friendly guide on how to install and use adb and fastboot
Ones installed go and download this version of twrp recovery and put it inside your adb (or platform tools) folder. Download the latest version of Magisk, Magisk manager and Magisk uninstaller from here and put it inside of your phone's internal storage.
Inside your settings tap the MIUI version 7 times to "become a developer". Then go to developer options and switch adb debugging on.
Follow the adb and fastboot guide, but don't flash this recovery to your phone. Instead in your cmd or terminal type:
Code:
adb devices
Code:
adb reboot bootloader
This will boot your phone in fastboot mode, then type:
Code:
fastboot boot <your_downloaded_twrp.img>
Replace <your_downloaded_twrp.img> with the actual name of the image. This will boot you into twrp recovery without flashing it to your phone. Probably you will be welcomed with a menu with a slider that says "swipe to allow modifications" don't swipe, just choose "keep system read only". In the menu choose Install (install a zip) and flash the latest Magisk from your internal storage.
Reboot to system and you have root access. If Magisk manager is not installed yet, install the .apk file you downloaded. If you want to unroot the phone boot into twrp ones again and flash the Magisk uninstaller.
batman957 said:
Like to access net cut to remove hackers for some Intruders on my network
Click to expand...
Click to collapse
I used netcut also and i used magisk root.
Medeon said:
First I would like to say, do your research before you post a question here. The answers to your questions are literally one Google or XDA search away from you. Having said that, your best bet would probably be Kingoroot although I can't promise you it will work. I have tried it once on an older phone, but I did not succeed. But you could try.
If it's not working, the only way to gain root access is to unlock the bootloader of your phone. This will void your warranty. It's up to you to decide whether it's worth it or not. It will probably take a week or longer for Xiaomi to grant you to unlock the bootloader.
Here is a noob friendly guide on how to install and use adb and fastboot
Ones installed go and download this version of twrp recovery and put it inside your adb (or platform tools) folder. Download the latest version of Magisk, Magisk manager and Magisk uninstaller from here and put it inside of your phone's internal storage.
Inside your settings tap the MIUI version 7 times to "become a developer". Then go to developer options and switch adb debugging on.
Follow the adb and fastboot guide, but don't flash this recovery to your phone. Instead in your cmd or terminal type: This will boot your phone in fastboot mode, then type: Replace <your_downloaded_twrp.img> with the actual name of the image. This will boot you into twrp recovery without flashing it to your phone. Probably you will be welcomed with a menu with a slider that says "swipe to allow modifications" don't swipe, just choose "keep system read only". In the menu choose Install (install a zip) and flash the latest Magisk from your internal storage.
Reboot to system and you have root access. If Magisk manager is not installed yet, install the .apk file you downloaded. If you want to unroot the phone boot into twrp ones again and flash the Magisk uninstaller.
Click to expand...
Click to collapse
Alright thanks for the help an effort
batman957 said:
Alright thanks for the help an effort
Click to expand...
Click to collapse
Sure, no problem. Forgot to mention, if you decide to unlock the bootloader all your personal data (including internal storage) and apps will be wiped. So make a backup beforehand. Helium is a non root app that you could use for that purpose.
You could also relock the bootloader again, but that's a whole other tutorial by itself.
Medeon said:
Sure, no problem. Forgot to mention, if you decide to unlock the bootloader all your personal data (including internal storage) and apps will be wiped. So make a backup beforehand. Helium is a non root app that you could use for that purpose.
You could also relock the bootloader again, but that's a whole other tutorial by itself.
Click to expand...
Click to collapse
Just I forgot to ask can i use twrp temperorly as you said to install magisk then return back to the stock recovery and still have magisk available
batman957 said:
Just I forgot to ask can i use twrp temperorly as you said to install magisk then return back to the stock recovery and still have magisk available
Click to expand...
Click to collapse
Yes, you don't flash twrp recovery to the phone if you just boot into twrp recovery. It boots the image in your phone's RAM.
Medeon said:
Yes, you don't flash twrp recovery to the phone if you just boot into twrp recovery. It boots the image in your phone's RAM.
Click to expand...
Click to collapse
What about magisk
batman957 said:
What about magisk
Click to expand...
Click to collapse
When you install magisk trough twrp, you flash the zip file which cleverly patches parts of your boot and data partition. It does it systemlessly, so it won't modify the system. You can easily reverse this procedure by flashing the magisk uninstaller. It will bring your phone back in the state it was before rooting.