can I root my mi 9t temperorly - Redmi K20 / Xiaomi Mi 9T Questions & Answers

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.

Related

root 4.2.2. without flashing customer recovery

Good morning guys,
I see a lot of threads here about rooting 4.2.2, but in all of them it is recommended to root the phone by installing zip archive from a custom recovery.
I don't want to change stock recovery - is there any way to root it by flashing img from adb? I did it in this way on 4.2.1, by installing CF-Auto-Root-mako-occam-nexus4.img file from adb.
Can anyone advice how to get root without flashing custom recovery?
I have to ask,....why would you NOT want a custom recovery? What is the point in using a crippled stick recovery?
From my Evo LTE, yup.
Look at this How to thread in the general section, I copied and pasted relevant information. I kept a custom recovery and didn't try this method, but it says it will not flash a custom recovery.
E. Optional -- Root
If you want to get root access follow the steps below. (And no, this will not flash a custom recovery, and not, it will not make you "not stock".) Unlocked bootloader required. See steps above.
1) Download (to your computer) the latest version of CWM (from here) or TWRP (from here) for your device;
2) Rename the file to customrecovery.img, and make sure it is in the same directory as your fastboot.exe file;
3) Download (to /sdcard on your device) the latest version of either ChainsDD's Superuser (not currently working), or Chainfire's SuperSU;
4) Restart your device in fastboot mode and plug into computer;
5) Open a command prompt in the directory mentioned above and type: fastboot boot customrecovery.img
6) Wait for it to boot;
7) Navigate the menus the recovery menu on your device and select an option like "update zip from sdcard". Find the zip that you downloaded, and apply it.
8) Reboot. Done.
You can flash custom recovery via fastboot, use it to install su.zip and when you will choose restart after that, you will have question about you want custom recovery permanently or not, if you choose no then after restart you will have stock recovery
scottspa74 said:
I have to ask,....why would you NOT want a custom recovery? What is the point in using a crippled stick recovery?
From my Evo LTE, yup.
Click to expand...
Click to collapse
I want to make installing of future OTA as simple as possible. So I will get root and freeze all the system apps i don't want to be run, but when OTA comes I will be able to install it and will not receive any error messages which i had during this OTA.
It seems like this is a good solution:
5) Open a command prompt in the directory mentioned above and type: fastboot boot customrecovery.img
Click to expand...
Click to collapse
Do i understand correctly that this boots customer recovery on my phone from PC hard drive, but doesn't flash it to the phone? So, I'm able to install root.zip from it, but when i reboot the phone I don't have a custom recovery.
You can do as i mentioned in my post before or you can use as well command mentioned by ketjr81: fastboot boot nameofrecovery.img in both cases you will have had stock recovery after restart
Thank you guys, you have solved my issue. Now i have to find a ZIP with root to flash.
fatum2002 said:
Thank you guys, you have solved my issue. Now i have to find a ZIP with root to flash.
Click to expand...
Click to collapse
you find it in thread mentioned by ketjr81

Root stock 5.1 - Ub only

I'm no expert, so maybe a better way, but it worked for me, so try if you want...
Needed: stock ftf, (I used this https://shry.me/9L9OQ); CM boot img; TWRP img; Flashtool; fastboot, Supersu flashable zip.
1. Flash stock ftf with Flashtool, boot phone, and check 'android debugging ' and 'unknown sources'
2. Power off, hold volume up, and connect in fastboot mode
3. cd to adb directory on PC, type 'fastboot flash boot (CM file).img', and 'fastboot flash recovery (TWRP file).img'
4. disconnect phone, power on, volume up when you see led to enter recovery. Install > Supersu zip.
5. Power off, open Flashtool, and again flash ftf, but in 'exclude' box on right side, check everything except 'boot bundle, kernel, and fotakernel. (hopefully I'm remembering right).
When done, reboot, and you're rooted.
@levone1 link isn't working! pls fix.
itskapil said:
@levone1 link isn't working! pls fix.
Click to expand...
Click to collapse
Sorry, the parentheses got included in link. It's better now. By the way, I got it from here http://forum.xda-developers.com/son...al/ftf-xperia-z1-compact-d5503-5-1-1-t3201650.
Also, here's a couple more links to make it easier...
https://mega.nz/#!E4UQwIoZ!UFpur2wY3tIAU7SdjuEg5fUA6N4BAVwX_TeK_CFpTyo
https://mega.nz/#!k5E0kQpC!XdTudAe5ISAVyfQAHHMkgvjmNuY6TDxm62HzyOAEgmU
I'll post a CM boot link later if needed, or just download one.
http://forum.xda-developers.com/son...root-init-d-support-recovery-busybox-t3202799 is a nice addition to this method, (to get recovery and busybox after root). You can flash it with Rashr app on phone with root, (version 2.2.8).
levone1 said:
I'm no expert, so maybe a better way, but it worked for me, so try if you want...
Needed: stock ftf, (I used this https://shry.me/9L9OQ); CM boot img; TWRP img; Flashtool; fastboot, Supersu flashable zip.
1. Flash stock ftf with Flashtool, boot phone, and check 'android debugging ' and 'unknown sources'
2. Power off, hold volume up, and connect in fastboot mode
3. cd to adb directory on PC, type 'fastboot flash boot (CM file).img', and 'fastboot flash recovery (TWRP file).img'
4. disconnect phone, power on, volume up when you see led to enter recovery. Install > Supersu zip.
5. Power off, open Flashtool, and again flash ftf, but in 'exclude' box on right side, check everything except 'boot bundle, kernel, and fotakernel. (hopefully I'm remembering right).
When done, reboot, and you're rooted.
Click to expand...
Click to collapse
Links to these files?
NRG1975 said:
Links to these files?
Click to expand...
Click to collapse
3rd post has everything but CM boot. I'll post it if you need it. Or you could just download a ROM and extract.
NRG1975 said:
Links to these files?
Click to expand...
Click to collapse
This should work for boot IMG - https://mega.nz/#!Jh0DETBQ!E-9WTlINpfq5r3PIiKaIXRId7ar8g3c8YHTJha1N6LM
This really is not that easy .... While it may be the easiest way, it is far from easy with Win 8 or Win 10. I am gonna forego root till an easier way is found. Thank you for your efforts.
No Busybox
I was able to root my phone following your method. It was easy.. however I can't install busybox or use apps which requires busybox installation. Is there any workaround for this issue?!
aravindclpy said:
I was able to root my phone following your method. It was easy.. however I can't install busybox or use apps which requires busybox installation. Is there any workaround for this issue?!
Click to expand...
Click to collapse
Use stericson busybox from play store. I tried the other one and it didn't work, but that one worked for me. You can also manual push busybox if you have to.
aravindclpy said:
I was able to root my phone following your method. It was easy.. however I can't install busybox or use apps which requires busybox installation. Is there any workaround for this issue?!
Click to expand...
Click to collapse
You can also use this - http://forum.xda-developers.com/son...root-init-d-support-recovery-busybox-t3202799
Since this came out, I recommend it over my method, since everything is included, and it's faster than using FT a second time.
Hey,
Usually this kind of stuff isn't a problem for me, but here I'm stuck at step 4.
When I try to flash superSU.zip, TWRP reboots by itself.
Also when TWRP boots, I'm asked to choose "keep read only" or "allow modifications" for the system partition. Both choices results in a reboot of TWRP.
Any idea ?
(I tried with the method in the link above, same thing happens)
Jackhass said:
Hey,
Usually this kind of stuff isn't a problem for me, but here I'm stuck at step 4.
When I try to flash superSU.zip, TWRP reboots by itself.
Also when TWRP boots, I'm asked to choose "keep read only" or "allow modifications" for the system partition. Both choices results in a reboot of TWRP.
Any idea ?
(I tried with the method in the link above, same thing happens)
Click to expand...
Click to collapse
Only time I ever got that from twrp was after doing ta update and booting into the new recovery. I just picked 'allow' and everything was fine. Are you booting into recovery the new way, or old? Are you using all of the files I posted, or a different boot, etc? My first shot would be to try a different recovery IMG, like an older twrp,and see if it works. I did all the above with the old recovery method, (wait for LED and vol up). Let me know...
@levone1 Thanks for your answer
I redownloaded all your files, did it again (exactly as it's said in the OP) and... it worked. I've done nothing more or less than last time I tried.. Unexplainable
Thanks anyway
Jackhass said:
@levone1 Thanks for your answer
I redownloaded all your files, did it again (exactly as it's said in the OP) and... it worked. I've done nothing more or less than last time I tried.. Unexplainable
Thanks anyway
Click to expand...
Click to collapse
Great... If you want busybox, etc., see the posts before yours.
Update (.216)
Just bumping thread for new fw. After FT flash, there is no r/w access. Can't use method in this forum without busybox, so to get busybox, just download nut dual recovery 'installer' option, and run on pc. Steps are same otherwise. I posted an ftf here - http://forum.xda-developers.com/sony-xperia-z1-compact/general/216-stock-ftf-read-flashing-t3243728
levone1 said:
Just bumping thread for new fw. After FT flash, there is no r/w access.
Click to expand...
Click to collapse
The steps I took with UL BL...
Used the Flashtool and XperiFirm to download and flash 216.
Hot booted 368 kernel and flashed SU zip, confirmed root with TB and Root Explorer after reboot to stock 216 kernel.
Installed Busybox from Play Store.
Extracted kernel.sin from ftf and used @[NUT]'s Kernel Builder to add XZDualRecovery.
Extracted boot.img from zip and flashed with Fastboot.
Now I'm in the process of removing bloatware then I'm going to theme it.

Root / Unlock Bootloader without removing encryption!

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

Working root for honor 8 pro

This is only for Honor 8 Pro (DUK-L09)​
DISCLAIMER​YOUR WARRANTY IS NOW VOID. IN NO WAY AM I RESPONSIBLE FOR THE EFFECTS YOU INFLICT ON YOUR MOBILE DEVICE BY FOLLOWING THE BELOW PROCEDURE. IMPROPER USAGE OF THE METHOD MIGHT END UP BRICKING YOUR DEVICE AND RENDERING IT UNUSABLE.
PLEASE BACKUP ALL YOUR DATA BEFORE PROCEEDING.​
Purpose of this thread is to provide a working rooting method for the Honor 8 Pro. Flashing Phhsuperuser doesn't grant SYSTEM WIDE root permission.
Functions like granting -rw permissions to apps demanding them for accessing /system partition was disabled, TWRP backup wouldn't work.
With this method, you will be able to operate the phone will proper root privileges.
INSTALLATION INSTRUCTIONS
1. UNLOCK BOOTLOADER​
Assuming you have a Huawei ID, use THIS PAGE to get your Unlock code.
Once you have that, enable USB debugging on your device from Developer options menu.
Make sure "Allow OEM unlock" option is selected.
Use the following set of commands via ADB/Fastboot:
adb device (this should recognize your device)
adb reboot bootloader (this will boot your phone into fastboot mode)
fastboot oem unlock *unlock key* (the part between * is where the unlock key goes)
The device will restart and then perform factory reset itself.
2. INSTALL CUSTOM RECOVERY IMAGE (Source : TWRP Thread by OldDroid)​
Download TWRP recovery image from HERE
Rename the downloaded file to recovery.img
Copy it to the ADB folder that you are using.
Use the command "adb reboot bootloader" like in Step 1 to boot into Fastboot mode.
Flash the recovery using "fastboot flash recovery recovery.img" command (without quotes)
You have now flashed a custom recovery onto your phone.​
3. ROOTING
Download Magisk installer zip file from THIS LINK . I had personally used v 13.3 .
Copy it to your SD card(I would suggest you to use a external card).
Switch off your device.
Boot into recovery mode by pressing Volume Up and Power Button together.
Once in, swipe to allow modifications.
Go to Wipe - Format Data
Then Go to Reboot- Recovery
You should be back into the recovery mode. Go to Install menu - Select storage - Install the Magisk zip that you downloaded.
Once it is flashed, you can Reboot to system.
Note: To confirm system wide root access, you can reboot to recovery and try to take a Nandroid backup. It should now be possible.​
If anyone happens to run into a bootloop or soft bricks the device, THIS THREAD by @aKp1 will come in handy.
Thanks to @OldDroid for his TWRP thread.
I am rooted using phhs superuser, do I need to unroot first? If yes, I can't find how to unroot the Indian variant.
Going back to Stock = Unrooting
devilrulz4ever said:
I am rooted using phhs superuser, do I need to unroot first? If yes, I can't find how to unroot the Indian variant.
Click to expand...
Click to collapse
Yes you will have to unroot first. Since phhsuperuser doesn't have a option to UNROOT, you will have to flash stock ROM.
To do that, download the following: HUAWEI UPDATE EXTRACTOR and STOCK ROM .
Follow below steps:
Extract the Stock ROM
Use the Update extractor and select "Update.app" file. That should give you a list of files. Select "recovery.img" and "recovery2.img" image files and extract them.
Copy them to ADB folder. Boot your phone into fastboot mode, flash the two recovery files you copied.
Next, Copy the "dload" folder to your SD card(preferably external SD). Switch your phone off. Press Vol Up,Vol Down and Power button together. The ROM should start flashing. That brings you back to stock firmware. If you want to re-root, follow the instructions in this thread.
amulbaby said:
Yes you will have to unroot first. Since phhsuperuser doesn't have a option to UNROOT, you will have to flash stock ROM.
To do that, download the following: HUAWEI UPDATE EXTRACTOR and STOCK ROM .
Follow below steps:
Extract the Stock ROM
Use the Update extractor and select "Update.app" file. That should give you a list of files. Select "recovery.img" and "recovery2.img" image files and extract them.
Copy them to ADB folder. Boot your phone into fastboot mode, flash the two recovery files you copied.
Next, Copy the "dload" folder to your SD card(preferably external SD). Switch your phone off. Press Vol Up,Vol Down and Power button together. The ROM should start flashing. That brings you back to stock firmware. If you want to re-root, follow the instructions in this thread.
Click to expand...
Click to collapse
Thanks for your reply. I'll try this out.
The build number of the Stock ROM in Gdrive is "Duke-L09I_C675B130" while the one on the phone is "DUK-L09C675B130" are they both the same variant?
devilrulz4ever said:
Thanks for your reply. I'll try this out.
The build number of the Stock ROM in Gdrive is "Duke-L09I_C675B130" while the one on the phone is "DUK-L09C675B130" are they both the same variant?
Click to expand...
Click to collapse
Don't worry . It's the same. File name doesn't matter.
amulbaby said:
Don't worry . It's the same. File name doesn't matter.
Click to expand...
Click to collapse
Oh wait. Isn't the format data option remove some necessary apps like keyboard and others? Because that's the case before in my Honor 8. After you remove encryption, you need to reflash the region zip so that some important files will be retained.
Sent from my Honor 8 Pro using XDA Labs
adriansticoid said:
Oh wait. Isn't the format data option remove some necessary apps like keyboard and others? Because that's the case before in my Honor 8. After you remove encryption, you need to reflash the region zip so that some important files will be retained.
Click to expand...
Click to collapse
The zip I shared is for the Indian variant . As long as someone is having C675(Indian variant) installed, it shouldn't cause issues. However if you come from a different region(C432) , you will have to use region zip. I guess I mentioned that in the TWRP thread, current last post.
But formatting data can't be avoided as unlocking bootloader will wipe it in first place . More over stock ROM encrypts data on first boot, so you will have to format data(decrypt it) and proceed with rooting.
amulbaby said:
The zip I shared is for the Indian variant . As long as someone is having C675(Indian variant) installed, it shouldn't cause issues. However if you come from a different region(C432) , you will have to use region zip. I guess I mentioned that in the TWRP thread, current last post.
But formatting data can't be avoided as unlocking bootloader will wipe it in first place . More over stock ROM encrypts data on first boot, so you will have to format data(decrypt it) and proceed with rooting.
Click to expand...
Click to collapse
Wut. So you mean to tell me, that after I decrypt, I should just go ahead and flash Magisk, then reboot? No more additional zip to flash? Sorry man this is getting out of my head.
Sent from my Honor 8 Pro using XDA Labs
Tht's nice bro...u said u wll be cming up wd ths kind of thread..and u r there...thnks....really needed support for the indian variant...
i will dfntly try this....
and one more thing...currently i am facing issues with adaway..busybox...with phh superuser..since no rw permissions...can magisk solve the problem
adriansticoid said:
Wut. So you mean to tell me, that after I decrypt, I should just go ahead and flash Magisk, then reboot? No more additional zip to flash? Sorry man this is getting out of my head.
Click to expand...
Click to collapse
That's correct. As simple as that. Decrypt , flash Magisk and you are done. I don't know why many didn't try this all this while.
rexinriot said:
Tht's nice bro...u said u wll be cming up wd ths kind of thread..and u r there...thnks....really needed support for the indian variant...
i will dfntly try this....
and one more thing...currently i am facing issues with adaway..busybox...with phh superuser..since no rw permissions...can magisk solve the problem
Click to expand...
Click to collapse
Yes magisk will solve your problem. Phhsuperuser doesn't allow you to grant permissions to any app that tries fiddle with system partition. If you are already rooted , go back to stock and follow the steps outlined.
amulbaby said:
That's correct. As simple as that. Decrypt , flash Magisk and you are done. I don't know why many didn't try this all this while.
Click to expand...
Click to collapse
Dafuuuuq. I waa scared all along because of that. I didn't know things changed in Honor 8 Pro. Thanks a lot.
Sent from my Honor 8 Pro using XDA Labs
amulbaby said:
That's correct. As simple as that. Decrypt , flash Magisk and you are done. I don't know why many didn't try this all this while.
Click to expand...
Click to collapse
How to decrypt? I successfully rooted with magisk v14 but adaway is disabled after reboot, same case as phhs superuser.
devilrulz4ever said:
How to decrypt? I successfully rooted with magisk v14 but adaway is disabled after reboot, same case as phhs superuser.
Click to expand...
Click to collapse
You flashed Magisk while encrypted?
Sent from my Honor 8 Pro using XDA Labs
devilrulz4ever said:
How to decrypt? I successfully rooted with magisk v14 but adaway is disabled after reboot, same case as phhs superuser.
Click to expand...
Click to collapse
You need to wipe data (which will decrypt) and then flash Magisk.
Read point no.3 of the installation instructions.
adriansticoid said:
You flashed Magisk while encrypted?
Click to expand...
Click to collapse
Have you managed to root your device using Magisk yet?
amulbaby said:
Have you managed to root your device using Magisk yet?
Click to expand...
Click to collapse
Not yet. Maybe I'll try tomorrow.
Sent from my Honor 8 Pro using XDA Labs
amulbaby said:
You need to wipe data (which will decrypt) and then flash Magisk.
Read point no.3 of the installation instructions.
Click to expand...
Click to collapse
I wiped data, flashed Magisk v13.3 and then v14 after a successful boot (without wipe).
Hello...now i am going back to stock rom b130..from phh superuser.... i am going to follow your instructions of rooting using magisk after this...
But before that i hv one question....should i upgrade to b140 and then follow op..or should i remain in b130 rom itself and start from there..
rexinriot said:
Hello...now i am going back to stock rom b130..from phh superuser.... i am going to follow your instructions of rooting using magisk after this...
But before that i hv one question....should i upgrade to b140 and then follow op..or should i remain in b130 rom itself and start from there..
Click to expand...
Click to collapse
Stay with 130. Surprisingly, rooting by this method still allows OTA to come in.

TWRP (Boost) flash doesn't stick

Hi - I've read through almost every thread in this forum and, unless I am missing something - quite possible - I don't think that anybody has mentioned this problem.
I have a bootloader unlocked Boost Moto E4 and I can flash Squid's TWRP (I do get the "Image not signed or corrupt" message) and can boot from the bootloader after the flash into TWRP recovery. However, after I boot into the OS, the TWRP recovery gets overwritten with the stock recovery. Has anybody else bumped into this? Is there a step that I am missing somewhere to make TWRP permanent?
Thanks
D.
Hmm - okay, after a little bit more work, I've managed to make it stick. I am not entirely sure which part of the process made it successful - or if I am duplicating things - but I used Magisk to generate a new boot.img, flashed that .img through twrp, installed the magisk .zip and now twrp "sticks" as my recovery. Nice that it allows me to boot with my system as r/w.
D.
D97 said:
Hmm - okay, after a little bit more work, I've managed to make it stick. I am not entirely sure which part of the process made it successful - or if I am duplicating things - but I used Magisk to generate a new boot.img, flashed that .img through twrp, installed the magisk .zip and now twrp "sticks" as my recovery. Nice that it allows me to boot with my system as r/w.
D.
Click to expand...
Click to collapse
Your problem is the stock rom flashing the stock recovery when you reboot. If you flash twrp then reboot recovery once before booting the os, it should change a file in /system recovery-from-boot.p to recovery-from-boot.p.bak which will stop the stock recovery flash. You can also mount /system in twrp and use the file manager to change it manually.
D97 said:
Hmm - okay, after a little bit more work, I've managed to make it stick. I am not entirely sure which part of the process made it successful - or if I am duplicating things - but I used Magisk to generate a new boot.img, flashed that .img through twrp, installed the magisk .zip and now twrp "sticks" as my recovery. Nice that it allows me to boot with my system as r/w.
D.
Click to expand...
Click to collapse
after flashing recovery you have to root your device to make it
sticky. if you skip this step custom recovery will replaced on next boot *bingo*
Francesco Franz said:
after flashing recovery you have to root your device to make it
sticky. if you skip this step custom recovery will replaced on next boot *bingo*
Click to expand...
Click to collapse
Not true. You don't have to root to make twrp stick. I did just state how to do this.
Sent from my Moto E (4) using XDA Labs
amarc78 said:
Not true. You don't have to root to make twrp stick. I did just state how to do this.
Click to expand...
Click to collapse
than do this flash over default recovery and do reboot. twrp recovery removed from recovery partition on next boot.
also do this flash twrp and do allow modifications. your device ain't gonna boot. if you didn't flash no verity thing.
rooting will make it permanent. it's the same case in both marshmallow and nougat too as OP states his problem in first post.
it will permanent by doing this
fastboot erase recovery (remove default recovery from recovery partition)
than install custom recovery. it will be there no matter if your device is rooted or not.
Thanks for the replies, everybody. There is some good info in them - I have managed to "make it stick" but I'll definitely keep the advice here in mind when I need to redo things (as I am sure that I will at some point).
D.
D97 said:
Thanks for the replies, everybody. There is some good info in them - I have managed to "make it stick" but I'll definitely keep the advice here in mind when I need to redo things (as I am sure that I will at some point).
D.
Click to expand...
Click to collapse
which step actually help you?
DE SEXIEST said:
which step actually help you?
Click to expand...
Click to collapse
Whatever you do don't run "fastbootboot erase" anything unless you know for sure what by you're doing or you can screw up your partitions. I have flashed twrp many times with only running "fastboot flash recovery...", then flashing one of numerous zips to disable dmverity and forced encryption. As long as you have the option in twrp under " mount" that says "mount system read only" not checked and you may need to reboot twrp afterwards, twrp should stick. Flashing Magisk directly after the stock rom should also solve your problem and disable dmverity.

Categories

Resources