Related
Greetings!
After installing the October security updates (bringing my device to NBD90W) I decided to unlock my bootloader and install TWRP. However, I can't seem to get TWRP to "stick" - flashing seems fine, and rebooting into bootloader and into TWRP recovery all proceeds fine. However, as soon as I reboot my system, TWRP seems to disappear and the stock recovery reappears.
Am I doing something wrong here? This is the exact process I followed on my Nexus 7, without any problems.
jerethi said:
Greetings!
After installing the October security updates (bringing my device to NBD90W) I decided to unlock my bootloader and install TWRP. However, I can't seem to get TWRP to "stick" - flashing seems fine, and rebooting into bootloader and into TWRP recovery all proceeds fine. However, as soon as I reboot my system, TWRP seems to disappear and the stock recovery reappears.
Am I doing something wrong here? This is the exact process I followed on my Nexus 7, without any problems.
Click to expand...
Click to collapse
You should be able to run twrp-2.8.7 without any problems. I believe if you want one higher you might need to format data (decrypt is what I do).
Also, here is what instructions on TWRP say to make it stick.
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Tulsadiver said:
You should be able to run twrp-2.8.7 without any problems. I believe if you want one higher you might need to format data (decrypt is what I do).
Also, here is what instructions on TWRP say to make it stick.
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
Thanks for your response. I am following the directions on TWRP's website, so it must be another issue.
I will try the version you suggest to see if that works. Why would I need to format data to install a later version?
jerethi said:
Thanks for your response. I am following the directions on TWRP's website, so it must be another issue.
I will try the version you suggest to see if that works. Why would I need to format data to install a later version?
Click to expand...
Click to collapse
I believe it requires you to be decrypted. Formatting userdata will wipe your data so make a backup first.
http://forum.xda-developers.com/nexus-5x/general/guide-how-to-install-custom-recovery-t3231143
jerethi said:
Greetings!
After installing the October security updates (bringing my device to NBD90W) I decided to unlock my bootloader and install TWRP. However, I can't seem to get TWRP to "stick" - flashing seems fine, and rebooting into bootloader and into TWRP recovery all proceeds fine. However, as soon as I reboot my system, TWRP seems to disappear and the stock recovery reappears.
Am I doing something wrong here? This is the exact process I followed on my Nexus 7, without any problems.
Click to expand...
Click to collapse
Flash TWRP from bootloader.
While within bootloader use vol down to select recovery and press power to boot into recovery.
Install SuperSU.
TWRP will stick.
If you boot with stock recovery even once, TWRP will get replaced.
sfhub said:
Flash TWRP from bootloader.
While within bootloader use vol down to select recovery and press power to boot into recovery.
Install SuperSU.
TWRP will stick.
If you boot with stock recovery even once, TWRP will get replaced.
Click to expand...
Click to collapse
Thank you. What is the difference between rooting and using the method that TulsaDiver suggests above?
Tulsadiver said:
I believe it requires you to be decrypted. Formatting userdata will wipe your data so make a backup first.
http://forum.xda-developers.com/nexus-5x/general/guide-how-to-install-custom-recovery-t3231143
Click to expand...
Click to collapse
So, just to clarify, I can either flash a modified boot.img (as described in the post you linked) or I could simply flash an older version of TWRP?
Thanks again for your assistance!
jerethi said:
So, just to clarify, I can either flash a modified boot.img (as described in the post you linked) or I could simply flash an older version of TWRP?
Click to expand...
Click to collapse
If you are using NBD90W I suggest you use the unofficial TWRP 3.0.2-3 that was posted a few pages back from the last post on the TWRP thread.
TWRP 3.0.2-0 won't decrypt Android N (will decrypt MM)
TWRP 3.0.2-1 has a major EFS bug that will brick your phone on restore
TWRP 3.0.2-2 has that EFS problem fixed, but has another problem where larger parttitions don't get backed up correctly.
TWRP 3.0.2-3 has both previous problems fixed.
---------- Post added at 10:19 AM ---------- Previous post was at 10:16 AM ----------
jerethi said:
Thank you. What is the difference between rooting and using the method that TulsaDiver suggests above?
Click to expand...
Click to collapse
I didn't read the whole post but decrypted user partition isn't directly related to why your TWRP is disappearing.
When you boot with a stock image, it will replace your recovery with stock.
If there is just 1 byte change with your boot.img, it won't do that.
Installing SuperSU will patch your boot.img, thus it will no longer replace your recovery with stock.
You could flash a modified boot.img instead of SuperSU, but then you are depending on someone else creating a modified boot.img for you (or you creating it yourself). If your goal is to have root installed, then SuperSU will patch boot.img on the fly during install so no need for extra step.
Again, the overwriting of TWRP with stock recovery is not directly related to the modifications done to boot.img either by someone else or by SuperSU install. If you had done any change to boot.img even if it is off by 1 byte, TWRP won't be replaced by stock recovery.
IMO there is no reason to run decrypted with latest OS, but if you wanted to, the only requirement is you have dm-verity disabled in the boot.img. Both the custom boot.img and the SuperSU install would do this for you.
After you have dm-verity disabled (either by SuperSU install or installing custom boot.img), boot back into bootloader and do
fastboot format userdata
From that point on, as long as you *never* boot using stock boot.img your userdata will remain decrypted. If you ever boot with stock boot.img, by mistake, it will proceed to encrypt your userdata. Then you'd have to go through the same procedure again the decrypt (losing your userdata in the format step)
The proper way to upgrade is to flash boot.img, system.img, vendor.img in fastboot, then immediately (from bootloader menu) boot into TWRP recovery, and install SuperSU. Then everything will be preserved.
jerethi said:
So, just to clarify, I can either flash a modified boot.img (as described in the post you linked) or I could simply flash an older version of TWRP?
Thanks again for your assistance!
Click to expand...
Click to collapse
Listen to this guy. You can start with the old one if you want then upgrade to the new one later but Supersu modifies your boot.img for you. Like he said, after Fastboot flashing them, Fastboot reboot and before your phone boots up, boot right back into recovery. This will make TWRP stick.
Wow, this post was SO HELPFUL.... Haven't rooted in a while, recently replaced our Nexus 5's with 5x's (on NBD90W) and hadn't felt the need to root. Plus it's gotten so much trickier even with Nexuses.
Anyway totally familiar with ADB/fastboot etc to flash stuff.
I still need to oem unlock and wipe still (bleh).
But after, one thing that's confusing me, to then root is a *custom* kernel (boot.img) needed now? Made specifically for (at this point in time) NBD90W? Or can stock boot.img be flashed then boot straight into TWRP and flash whatever is the latest SuperSU? Are all SuperSI "systemless" now?
Also you stated "IMO there is no reason to run decrypted with latest OS". I have noticed VAST performance improvement with Nougat. Is this why you feel no reason? Would we not still gain even more speed back? (it was so sad watching my wife's old Nexus 5 booting 6.0.1 faster than my 5X).
sfhub said:
If you are using NBD90W I suggest you use the unofficial TWRP 3.0.2-3 that was posted a few pages back from the last post on the TWRP thread.
TWRP 3.0.2-0 won't decrypt Android N (will decrypt MM)
TWRP 3.0.2-1 has a major EFS bug that will brick your phone on restore
TWRP 3.0.2-2 has that EFS problem fixed, but has another problem where larger parttitions don't get backed up correctly.
TWRP 3.0.2-3 has both previous problems fixed.
---------- Post added at 10:19 AM ---------- Previous post was at 10:16 AM ----------
I didn't read the whole post but decrypted user partition isn't directly related to why your TWRP is disappearing.
When you boot with a stock image, it will replace your recovery with stock.
If there is just 1 byte change with your boot.img, it won't do that.
Installing SuperSU will patch your boot.img, thus it will no longer replace your recovery with stock.
You could flash a modified boot.img instead of SuperSU, but then you are depending on someone else creating a modified boot.img for you (or you creating it yourself). If your goal is to have root installed, then SuperSU will patch boot.img on the fly during install so no need for extra step.
Again, the overwriting of TWRP with stock recovery is not directly related to the modifications done to boot.img either by someone else or by SuperSU install. If you had done any change to boot.img even if it is off by 1 byte, TWRP won't be replaced by stock recovery.
IMO there is no reason to run decrypted with latest OS, but if you wanted to, the only requirement is you have dm-verity disabled in the boot.img. Both the custom boot.img and the SuperSU install would do this for you.
After you have dm-verity disabled (either by SuperSU install or installing custom boot.img), boot back into bootloader and do
fastboot format userdata
From that point on, as long as you *never* boot using stock boot.img your userdata will remain decrypted. If you ever boot with stock boot.img, by mistake, it will proceed to encrypt your userdata. Then you'd have to go through the same procedure again the decrypt (losing your userdata in the format step)
The proper way to upgrade is to flash boot.img, system.img, vendor.img in fastboot, then immediately (from bootloader menu) boot into TWRP recovery, and install SuperSU. Then everything will be preserved.
Click to expand...
Click to collapse
jb0ne said:
Wow, this post was SO HELPFUL.... Haven't rooted in a while, recently replaced our Nexus 5's with 5x's (on NBD90W) and hadn't felt the need to root. Plus it's gotten so much trickier even with Nexuses.
Anyway totally familiar with ADB/fastboot etc to flash stuff.
I still need to oem unlock and wipe still (bleh).
But after, one thing that's confusing me, to then root is a *custom* kernel (boot.img) needed now? Made specifically for (at this point in time) NBD90W? Or can stock boot.img be flashed then boot straight into TWRP and flash whatever is the latest SuperSU? Are all SuperSI "systemless" now?
Also you stated "IMO there is no reason to run decrypted with latest OS". I have noticed VAST performance improvement with Nougat. Is this why you feel no reason? Would we not still gain even more speed back? (it was so sad watching my wife's old Nexus 5 booting 6.0.1 faster than my 5X).
Click to expand...
Click to collapse
I've always decrypted but that is my personal choice. All I do to root afterwards is flash SuperSU-v2.7.8. That is it. You can adb sideload it (i use twrp for that) or flash it in twrp if you have it already on your phone).
jb0ne said:
But after, one thing that's confusing me, to then root is a *custom* kernel (boot.img) needed now? Made specifically for (at this point in time) NBD90W? Or can stock boot.img be flashed then boot straight into TWRP and flash whatever is the latest SuperSU? Are all SuperSI "systemless" now?
Click to expand...
Click to collapse
You must have a customized boot.img now for root. What customizations you absolutely need to have in boot.img is dependent on how you want root installed, but since you are modifying boot.img, you might as well just stick all the changes you need in boot.img and leave /system untouched.
The default install for SuperSU will make the required changes to whichever boot.img you currently have installed on your system. Generally that consists of disabling dm-verity (integrity check), making encryption optional (not absolutely required), making sepolicy security changes, and adding init script support to load SuperSU binaries later in the boot process.
There are configuration parameters you can feed into SuperSU install to force it to install root on /system instead of systemless, but I would just suggest systemless. It is a cleaner install IMO.
So install the stock boot.img and boot directly into TWRP from the bootloader menu, then install SuperSU and it will modify the boot.img you have installed (and back up original)
The only requirement to keep TWRP (and/or decrypted userdata) is to NEVER boot the phone using a stock boot.img. If you always immediately install SuperSU after flashing the stock boot.img that will satisfy that requirement.
jb0ne said:
Also you stated "IMO there is no reason to run decrypted with latest OS". I have noticed VAST performance improvement with Nougat. Is this why you feel no reason? Would we not still gain even more speed back? (it was so sad watching my wife's old Nexus 5 booting 6.0.1 faster than my 5X).
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-5x/general/unencrypted-faster-real-world-usage-t3365660
for some reason, when i fastboot installed twrp (after usb debug/unlocking bootloader) I kept getting mount errors when starting twrp. I tried flashing purenexus rom, wipes dalvic, system, data. then my data partition was 0. couldn't mount data part. to copy purenexus or system stock image. I ended up having to use my windows pc to wugfresh it back to life. has been a crazy night. I need coffee.
On coast of SC here, in Charleston. Wishing everybody best of luck with the hurricane.
trentag1988 said:
for some reason, when i fastboot installed twrp (after usb debug/unlocking bootloader) I kept getting mount errors when starting twrp. I tried flashing purenexus rom, wipes dalvic, system, data. then my data partition was 0. couldn't mount data part. to copy purenexus or system stock image. I ended up having to use my windows pc to wugfresh it back to life. has been a crazy night. I need coffee.
On coast of SC here, in Charleston. Wishing everybody best of luck with the hurricane.
Click to expand...
Click to collapse
Did you reboot after unlocking or go ahead and install TWRP right after unlocking?
I tried, but I kept getting the " cannot check for corrupt system because bootloader is unlocked" message, and it never fully booted. I managed to fix the 0data partition by fastboot format userdata, but pure Nexus never worked. It tried to boot, but it stuck on the spinning Google logo thing
Update: followed pure Nexus instruction; unlocked bootloader, then let it boot once to device setup. Restarted in fast boot, flashed twrp. Rebooted, went into twrp, formatted dalvic, system, user data and cache. Flashed pure Nexus from then gapps according to pure Nexus download page. Reformated dalvic and cache. Rebooted, stuck on Google logo, this time did not do its spinning thing. Have I missed a step??
---------- Post added at 03:33 PM ---------- Previous post was at 03:32 PM ----------
Update: followed pure Nexus instruction; unlocked bootloader, then let it boot once to device setup. Restarted in fast boot, flashed twrp. Rebooted, went into twrp, formatted dalvic, system, user data and cache. Flashed pure Nexus from twrp then gapps according to pure Nexus download page. Reformated dalvic and cache. Rebooted, stuck on Google logo, this time did not do its spinning thing. Have I missed a step??
trentag1988 said:
Update: followed pure Nexus instruction; unlocked bootloader, then let it boot once to device setup. Restarted in fast boot, flashed twrp. Rebooted, went into twrp, formatted dalvic, system, user data and cache. Flashed pure Nexus from then gapps according to pure Nexus download page. Reformated dalvic and cache. Rebooted, stuck on Google logo, this time did not do its spinning thing. Have I missed a step?
---------- Post added at 03:33 PM ---------- Previous post was at 03:32 PM ----------
Update: followed pure Nexus instruction; unlocked bootloader, then let it boot once to device setup. Restarted in fast boot, flashed twrp. Rebooted, went into twrp, formatted dalvic, system, user data and cache. Flashed pure Nexus from twrp then gapps according to pure Nexus download page. Reformated dalvic and cache. Rebooted, stuck on Google logo, this time did not do its spinning thing. Have I missed a step?
Click to expand...
Click to collapse
What firmware are you on?
Latest nrd90w(?) I believe
---------- Post added at 04:04 PM ---------- Previous post was at 04:04 PM ----------
NBD90W
sfhub said:
If you are using NBD90W I suggest you use the unofficial TWRP 3.0.2-3 that was posted a few pages back from the last post on the TWRP thread.
TWRP 3.0.2-0 won't decrypt Android N (will decrypt MM)
TWRP 3.0.2-1 has a major EFS bug that will brick your phone on restore
TWRP 3.0.2-2 has that EFS problem fixed, but has another problem where larger parttitions don't get backed up correctly.
TWRP 3.0.2-3 has both previous problems fixed.
---------- Post added at 10:19 AM ---------- Previous post was at 10:16 AM ----------
I didn't read the whole post but decrypted user partition isn't directly related to why your TWRP is disappearing.
When you boot with a stock image, it will replace your recovery with stock.
If there is just 1 byte change with your boot.img, it won't do that.
Installing SuperSU will patch your boot.img, thus it will no longer replace your recovery with stock.
You could flash a modified boot.img instead of SuperSU, but then you are depending on someone else creating a modified boot.img for you (or you creating it yourself). If your goal is to have root installed, then SuperSU will patch boot.img on the fly during install so no need for extra step.
Again, the overwriting of TWRP with stock recovery is not directly related to the modifications done to boot.img either by someone else or by SuperSU install. If you had done any change to boot.img even if it is off by 1 byte, TWRP won't be replaced by stock recovery.
IMO there is no reason to run decrypted with latest OS, but if you wanted to, the only requirement is you have dm-verity disabled in the boot.img. Both the custom boot.img and the SuperSU install would do this for you.
After you have dm-verity disabled (either by SuperSU install or installing custom boot.img), boot back into bootloader and do
fastboot format userdata
From that point on, as long as you *never* boot using stock boot.img your userdata will remain decrypted. If you ever boot with stock boot.img, by mistake, it will proceed to encrypt your userdata. Then you'd have to go through the same procedure again the decrypt (losing your userdata in the format step)
The proper way to upgrade is to flash boot.img, system.img, vendor.img in fastboot, then immediately (from bootloader menu) boot into TWRP recovery, and install SuperSU. Then everything will be preserved.
Click to expand...
Click to collapse
Thanks very much for the detailed assistance. If I wanted to install a custom ROM, do I have to decrypt my user data first? Or can I just install TWRP and then flash?
trentag1988 said:
Latest nrd90w(?) I believe
---------- Post added at 04:04 PM ---------- Previous post was at 04:04 PM ----------
NBD90W
Click to expand...
Click to collapse
I do not believe Pure Nexus is a Nougat Rom. Try starting over and flashing a Rom compatible with your firmware.
About :This guide is only meant for mediatek variant of Moto E4 which is SKU XT1760. Only phh's Superuser able to root Moto E4 :fingers-crossed: . SuperSU & Magisk isn't fully compatible with Moto E4 and failed to root this device .Unofficial Xposed works with Moto E4 :laugh: but not Xposed module's (force close error !)
Procedure :
Step 1 : Installing Recovery
- Install Ported TWRP recovery first
- if you haven't installed it yet ! Get it from below thread.
Thread link :
https://forum.xda-developers.com/moto-e4/development/available-moto-e4-ported-twrp-recovery-t3656286
Step 2 : Opening TWRP Recovery
- Boot into recovery
- Install phh's supersu zip file
- Select storage and locate to zip file
- Swipe to install
- Done
Download link for phh's superuser zip file:
http://www.mediafire.com/file/8h4k4enel9uh4u7/superuser.zip
Step 3 : Disable dm-verity and Force encryption
This step is crucial else you won't able to boot into system again !
It has two steps to follow whether select my modified boot image to disable
dm-verity and force encryption else use this no-verity-opt-encrypt zip file
to disable dm-verity and force encryption.
If you were going through Boot image process !
Download link for Kernel(Boot image) :
http://www.mediafire.com/file/y4160sl13ibyx8q/boot.img
- Boot your device into recovery
- Select Reboot
- Choose bootloader
- Now attach your device with laptop/desktop
Type this fastboot command :
- "fastboot flash boot boot.img"
- Wait until process finish
- Now disconnect
- Press and hold power button
- Release when you see full black screen
If you were going through zip file flashing process !
Download link for zip file :
http://www.mediafire.com/file/m0w6zu83am6z38i/no-verity-opt-encrypt.zip
- Reboot into recovery again
- Install no-verity-opt-encrypt zip file
- Reboot into system
Step 4 : Installing phh's Superuser Application
- Install phhsuperuser app (Get this app from Googleplay)
- Within phhsuperuser app < open settings
- Superuser access set to Apps and ADB
- Done
Credits :
@phhusson
Thread link :
https://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
add link of this thread there in your twrp recovery thread,
drganbds said:
add link of this thread there in your twrp recovery thread,
Click to expand...
Click to collapse
already added in step 1
Kartik bro kindly organize all of your thread from unlocking bootloader, flashing twrp and rooting our mediatek variant in a single thread because it's not confusing as it is in various sections.....thanks and I obey for the time which you spend here...
drganbds said:
Kartik bro kindly organize all of your thread from unlocking bootloader, flashing twrp and rooting our mediatek variant in a single thread because it's not confusing as it is in various sections.....thanks and I obey for the time which you spend here...
Click to expand...
Click to collapse
ok.
So, i will make a single thread in Guide & news section.
:highfive:
Kartik first of all thanks for mediatek variant works and I have successfully unlocked my bootloader and flashed twrp recovery...now I have some doubts.
1. After flashing phh's superuser do we really need to flash boot.img? Or simply install no Verity opt zip file?
2.After flashing twrp recovery is that backup of stock ROM working?
3.Do we need to install no Verity opt zip everytime when we reboot from twrp recovery?
4.After unlocking my bootloader when I reboot the start up screen shows some "orange state" "your bootloader unlocked and can't be verified" is that normal?
drganbds said:
Kartik first of all thanks for mediatek variant works and I have successfully unlocked my bootloader and flashed twrp recovery...now I have some doubts.
1. After flashing phh's superuser do we really need to flash boot.img? Or simply install no Verity opt zip file?
2.After flashing twrp recovery is that backup of stock ROM working?
3.Do we need to install no Verity opt zip everytime when we reboot from twrp recovery?
4.After unlocking my bootloader when I reboot the start up screen shows some "orange state" "your bootloader unlocked and can't be verified" is that normal?
Click to expand...
Click to collapse
@drganbds
about verity it has two simple steps:
if you were going through zip file process you may need to flash no verity zip many times for disabling dm-verity & force encryption (when using rooting method other than this). if you want to know how to use zip file, simply flash phh's superuser than reboot to recovery again and flash no verity zip file. thats it.
if you want a permanent solution than use my modified boot image. how to install... first flash boot image in fastboot mode than install phh's superuser.
backup of stockrom working well and the warning message is normal, nothing to worry.
once you flash no verity zip file you don't need to flash it everything time in twrp in order to boot into system.
if you face any problem simply flash stock boot image
Ok as for as I understood if I flash your modified boot image first then no need to flash no Verity everytime when I install something in twrp right and it's a permanent solution otherwise we need to depend on no Verity zip everytime?
drganbds said:
Ok as for as I understood if I flash your modified boot image first then no need to flash no Verity everytime when I install something in twrp right and it's a permanent solution otherwise we need to depend on no Verity zip everytime?
Click to expand...
Click to collapse
yes no need to flash no-verity-force-encrypt file every time directly install phh's superuser zip file when using boot image.
with verity zip you need to flash it once after rooting, also if you unroot your device and again going to root you have to install no verity file after rooting.
Remember if you flash boot image other than this plus you will loose root & permanent sol. of dm-verity fix.
Ok thanks then first I will flash your boot.img and reboot to twrp and flash phh's superuser and reboot to system.
drganbds said:
Ok thanks then first I will flash your boot.img and reboot to twrp and flash phh's superuser and reboot to system.
Click to expand...
Click to collapse
yes :fingers-crossed:
drganbds said:
Ok thanks then first I will flash your boot.img and reboot to twrp and flash phh's superuser and reboot to system.
Click to expand...
Click to collapse
Kartik my stock backup file shows .sha2 and .win000 file formats is that ok?
---------- Post added at 05:37 AM ---------- Previous post was at 05:32 AM ----------
kartik verma said:
yes :fingers-crossed:
Click to expand...
Click to collapse
Kindly add (or) on step 3 and mention the word as permanent solution on flashing modified boot image before flashing phh's superuser because in Kyle Qualcomm thread it's written as just flash phh's superuser, no need to flash no Verity file even again and reboot system that's it.
drganbds said:
Kartik my stock backup file shows .sha2 and .win000 file formats is that ok?
---------- Post added at 05:37 AM ---------- Previous post was at 05:32 AM ----------
Kindly add (or) on step 3 and mention the word as permanent solution on flashing modified boot image before flashing phh's superuser.
Click to expand...
Click to collapse
3rd file is the actual boot image.
drganbds said:
Kartik my stock backup file shows .sha2 and .win000 file formats is that ok?
---------- Post added at 05:37 AM ---------- Previous post was at 05:32 AM ----------
Kindly add (or) on step 3 and mention the word as permanent solution on flashing modified boot image before flashing phh's superuser because in Kyle Qualcomm thread it's written as just flash phh's superuser, no need to flash no Verity file even again and reboot system that's it.
Click to expand...
Click to collapse
you need to flash as i already tested else you won't able to boot into system !
kartik verma said:
you need to flash as i already tested else you won't able to boot into system !
Click to expand...
Click to collapse
Sorry for asking too many times but I need clear my doubts....if I flash your boot image after install of superuser then no need to flash no Verity zip right? Or I need to flash boot image and install no Verity zip both before I reboot?
drganbds said:
Sorry for asking too many times but I need clear my doubts....if I flash your boot image after install of superuser then no need to flash no Verity zip right? Or I need to flash boot image and install no Verity zip both before I reboot?
Click to expand...
Click to collapse
after installing boot image < install phh's superuser zip file
that's it.
kartik verma said:
after installing boot image < install phh's superuser zip file
that's it.
Click to expand...
Click to collapse
Done all superbly...took backup of rooted ROM and unroot ROM...next waiting for custom ROM...
drganbds said:
Done all superbly...took backup of rooted ROM and unroot ROM...next waiting for custom ROM...
Click to expand...
Click to collapse
:highfive:
kartik verma said:
:highfive:
Click to expand...
Click to collapse
Kartik twrp 3.1.1 usually take backup files in .sha2 and .win000 formats? Not in zip?
drganbds said:
Kartik twrp 3.1.1 usually take backup files in .sha2 and .win000 formats? Not in zip?
Click to expand...
Click to collapse
let me check first
I wanted to install Lineage OS and was curious if I could install it without having TWRP flashed into recovery. I mean, I'll still use fastboot boot twrp, ill just won't have it in my recovery.
I'm asking because when I tried to do fastboot flash recovery twrp it said failed antirollback check. Would like some help if possible
Once you temporarily boot twrp, you can it flash twrp image from within it.
It would work without, but you won't be able to update LOS, unless you boot twrp again.
See: - https://forum.xda-developers.com/redmi-note-5-pro/how-to/index-everything-anti-roll-t3816219
And don't downgrade MIUI firmware/rom.
corkiejp said:
Once you temporarily boot twrp, you can it flash twrp image from within it.
It would work without, but you won't be able to update LOS, unless you boot twrp again.
See: - https://forum.xda-developers.com/redmi-note-5-pro/how-to/index-everything-anti-roll-t3816219
And don't downgrade MIUI firmware/rom.
Click to expand...
Click to collapse
Thanks for your help !
Anti rollback is such a pain in the ass.
I have a Pixel 3 XL and I was following this Guide to root it.
https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
When I get to part 2-10 (The part to install Magisk) my phone wont boot into the OS. Instead I end up back at TWRP. If I reinstall TWRP from my download folder or restore a back up I can get back into the OS. I still have TWRP installed but no root. I know I'm doing something wrong but I'm not sure. Like I've said TWRP is install but not Magisk.
What Android version; Pie or Q, stock or custom? What Magisk version? Are you booting to TWRP (fastboot boot twrp.img) or did you flash twrp to the device?
ktmom said:
What Android version; Pie or Q, stock or custom? What Magisk version? Are you booting to TWRP (fastboot boot twrp.img) or did you flash twrp to the device?
Click to expand...
Click to collapse
I did this from a blank slate. Pie, stock, the newest version if Magisk 19.3. I flashed twrp to my device.
Potatochip400 said:
I did this from a blank slate. Pie, stock, the newest version if Magisk 19.3. I flashed twrp to my device.
Click to expand...
Click to collapse
Try clean fastboot flashing the stock boot.img back onto the phone. You can get it from the fastboot factory img. Then just boot TWRP to flash the Magisk zip. The Magisk zip will need to be on the device for the booted TWRP to find it just like if you were running TWRP installed on the device.
An alternative is to use Magisk manager to patch the stock boot.img and then fastboot flash that patched img to the device.
ktmom said:
Try clean fastboot flashing the stock boot.img back onto the phone. You can get it from the fastboot factory img. Then just boot TWRP to flash the Magisk zip. The Magisk zip will need to be on the device for the booted TWRP to find it just like if you were running TWRP installed on the device.
An alternative is to use Magisk manager to patch the stock boot.img and then fastboot flash that patched img to the device.
Click to expand...
Click to collapse
I tried the easiest method first, which was installing the Magik app and flashing the zip, I got the following error,
Device platform: arm64-v8a
copying image to cache
Unpacking boot image
! Unsupported/Unkown image format
! Installation failed
I'll try flashing the stock image, but should I flash twrp again after the image? I've done this before in the past because some phones require it as part of the rooting instructions. Does this order sound right, flash stock image, reboot, flash twrp reboot, then Magisk?
Potatochip400 said:
I did this from a blank slate. Pie, stock, the newest version if Magisk 19.3. I flashed twrp to my device.
Click to expand...
Click to collapse
You must use the latest magisk 19.4.
Sent from my Pixel 3 XL
Eudeferrer said:
You must use the latest magisk 19.4.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
Just tried the beta version (19.4) and I'm stuck in a standard bootloop. I'll try and get it into recovery.
No worries, I forgot to mention that I restored a back up
Eudeferrer said:
You must use the latest magisk 19.4.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
Surely not on Pie. I'm using 19.3 on the last Pie.
ktmom said:
Surely not on Pie. I'm using 19.3 on the last Pie.
Click to expand...
Click to collapse
I'm on pie, but your first suggestion was the fix. I had to flash the factory img before doing everything else. I just had to put a little more time a side and not be lazy.
Hi everyone.
I had a issue and i really want help
I had unlock the OEM,and after installing the twrp and format data (to remove the forced encrypt), i had flash the Disable_Dm-Verity_ForceEncrypt zip file.
Okay, after that i have restarted the device and configure as my away to use, after that, booted on recovery again and flashed the magisk.
But i wanna encrypt my device, and when i go to configs->security and encrypt area, says that my device its not encrypted. Okay, i followed the steps and when i gonna try to encrypt the device, the process start and... some seconds after, the phone just restart and nothing has done.
The onlys changes that i have made on system is: root and flashed a splash.img(without that stupid warning of unlocked bootloader)
I really want to encrypt my device, so, if i get stolen, the thief wont get my user data.
Can anyone help me?
Flash the stock rom and and don't flash the encryption disabler next time. You don't need to install TWRP to flash Magisk either, you can just boot it and then flash Magisk. Also you don't even need TWRP, you can just follow the guide in the forum to install Magisk by booting the magisk patched boot.img for your version of the stock ROM and then install Magisk manually via Magisk Manager.
TL;DR : Flash stock ROM and do the same things except flashing dm-verity-disabler, you don't need that for Magisk or TWRP.
marstonpear said:
Flash the stock rom and and don't flash the encryption disabler next time. You don't need to install TWRP to flash Magisk either, you can just boot it and then flash Magisk. Also you don't even need TWRP, you can just follow the guide in the forum to install Magisk by booting the magisk patched boot.img for your version of the stock ROM and then install Magisk manually via Magisk Manager.
TL;DR : Flash stock ROM and do the same things except flashing dm-verity-disabler, you don't need that for Magisk or TWRP.
Click to expand...
Click to collapse
Thanks sir, i will try!
marstonpear said:
Flash the stock rom and and don't flash the encryption disabler next time. You don't need to install TWRP to flash Magisk either, you can just boot it and then flash Magisk. Also you don't even need TWRP, you can just follow the guide in the forum to install Magisk by booting the magisk patched boot.img for your version of the stock ROM and then install Magisk manually via Magisk Manager.
TL;DR : Flash stock ROM and do the same things except flashing dm-verity-disabler, you don't need that for Magisk or TWRP.
Click to expand...
Click to collapse
Sir, i really need twrp now, its there any way i can enable encrypt after rooting the device? (to sure that, if gets stolen, the data need to be wipped out or the password must be given on twrp)
Same issue, i tried to encrypt on security menu,reboot and nothing was done.
@edit
Better, without TWRP, i can flash other zips via magisk/stock recovery?
mrkeitsuke said:
Sir, i really need twrp now, its there any way i can enable encrypt after rooting the device? (to sure that, if gets stolen, the data need to be wipped out or the password must be given on twrp)
Same issue, i tried to encrypt on security menu,reboot and nothing was done.
@edit
Better, without TWRP, i can flash other zips via magisk/stock recovery?
Click to expand...
Click to collapse
I'm not sure what you're trying to do here, do you want to have TWRP + stock encryption?
If so you can just boot TWRP and flash the TWRP installer package (.zip) inside TWRP to do that. And you don't need to change anything, currently I have TWRP installed and encryption enabled on my Stock ROM.
But if you're trying to get TWRP's own encryption, sadly that doesn't work.
You can also use TWRP without flashing/installing it, just go to the directory TWRP is stored in, open a command line, connect your phone and boot it with this command :
Code:
fastboot boot twrp.img
then flash whatever you'd like.
DO NOT lock your bootloader after you flash something on TWRP, this will most probably brick the device.
marstonpear said:
I'm not sure what you're trying to do here, do you want to have TWRP + stock encryption?
If so you can just boot TWRP and flash the TWRP installer package (.zip) inside TWRP to do that. And you don't need to change anything, currently I have TWRP installed and encryption enabled on my Stock ROM.
But if you're trying to get TWRP's own encryption, sadly that doesn't work.
You can also use TWRP without flashing/installing it, just go to the directory TWRP is stored in, open a command line, connect your phone and boot it with this command :
Code:
fastboot boot twrp.img
then flash whatever you'd like.
DO NOT lock your bootloader after you flash something on TWRP, this will most probably brick the device.
Click to expand...
Click to collapse
I want to stick with the stock rom rooted, with the twrp installed and the user data encrypted
So i can flash things through TWRP even i have encrypt enabled?
@edit
dont worry about bootloader, i will keep unlocked
It's perfectly fine to have TWRP and/or Magisk and encryption using stock ROM.
Flash stock ROM (erase user data)
Install TWRP
install Magisk
Don't flash the encryption Disabler. As its name implies, it disables the automatic encryption of the userdata partition.
a1291762 said:
It's perfectly fine to have TWRP and/or Magisk and encryption using stock ROM.
Flash stock ROM (erase user data)
Install TWRP
install Magisk
Don't flash the encryption Disabler. As its name implies, it disables the automatic encryption of the userdata partition.
Click to expand...
Click to collapse
:highfive: i had done this and... i think its working!!! :crying::crying::crying:
(crying for emotion, almost thirty factory resets to get an good result :crying::crying::crying
Anyway, if anything bad occurs, i will update here, thanks a1291762 and marstonpear