Related
Information: If you're experienced with ADB/Fastboot or Manual Android Rooting, you could read this thread and see if you find something that seems wrong and report to me, thanks!
IntroductionHello there!
I decided to create a new Nexus 7 Rooting Guide, I know that there are some guides already, but I have a few reasons to make this guide.
Unlike many rooting guides, this one doesn't use an automated program (a.k.a Toolkit) and it works for both Nexus 7 Wi-Fi and Nexus 7 3G.
This guide has been tested with a Nexus 7 3G Edition, running Android 4.2.1/4.2.2.
Last Topic Update: Never
Last Minor Topic Update: Check thread edit date!
Requirements:
Nexus 7 (Wi-Fi or 3G Edition)
Android SDK
ADB/Fastboot Drivers
Unlocked Bootloader
If you don't have ADB/Fastboot drivers installed, please check out this thread:
http://forum.xda-developers.com/showthread.php?t=1907796
See Basic Knowledge and Driver Installation parts.
If you have Android SDK and ADB/Fastboot drivers installed and working, you can continue reading.
Make sure you have USB Debugging enabled in your Nexus 7.
Don't forget to unlock the bootloader!
Warning: You're the only one responsible if something bad happens to your device!
Nothing bad is going to happen, but there is always a small risk.
Personally, I recommend having +60% of Battery during ROM Changes (Flashing and etc).
I also recommend you to learn how to do a Factory Image Restore (Flash Stock ROM) before attempting to root...
Rooting your Nexus 7
To root our device, we're simply going to put in our tablet a small program called "SuperSU", you might want to download it now to your PC:
SuperSU v1.04
Basically, we´re going to put SuperSU in /system partition, the file you downloaded is a "Flashable ZIP".
We're going to use TWRP (Team Win Recovery Project) to flash the Flashable ZIP (In this case, SuperSU), after flashing SuperSU you get root privileges!
Now, go to your Android SDK Folder where Fastboot (fastboot.exe) is located (platform-tools), open a command prompt and change directories to your Fastboot location, if you need help just search on Google.
Now, you have CMD (Command Prompt) open with the Android SDK Directory, and we need to reboot your device into Fastboot mode, to do that just type the following:
adb reboot-bootloader
Click to expand...
Click to collapse
You're now in Fastboot Mode (a.k.a Bootloader), type the following to make sure you're in Fastboot Mode:
fastboot devices
Click to expand...
Click to collapse
You should see something like this:
Code:
> fastboot devices
# the following output should be returned
<device serial number> fastboot
Type "fastboot reboot" to reboot the device, then copy the SuperSU.zip you downloaded to your Nexus 7.
I also forgot to tell you to download TWRP, if you have the Nexus 7 Wi-Fi Edition, your board codename is Grouper, if you have the 3G Edition, your board codename is Tilapia.
TWRP for Nexus 7 [grouper]
TWRP for Nexus 7 3G [tilapia]
Copy the correct TWRP Edition to your Nexus 7, then boot into the bootloader.
Temporarily boot TWRP using the following command:
fastboot boot TWRP.img
Click to expand...
Click to collapse
Replace "TWRP.img" with the correct file name.
You can also flash TWRP instead of temporarily booting.
Inside TWRP click "Install" and select the SuperSU ZIP File, then Confirm Flash.
After flashing, reboot your device and you should have SuperSU installed. (Open SuperSU just to test)
Congratulations! You now have a Rooted Device!
To make sure you have rooted, download "Root Checker" from Google Play.
ConclusionAs you can see, this tutorial is a little different from others, I explained what we were going to do and also explained the commands instead of giving you directly the commands.
This tutorial was written to teach the basics of ADB/Fastboot, I hope you rooted your device without problems and learnt/learned something, have a good day!
Feel free to give suggestions or corrections!
This work is licensed under a Creative Commons Attribution-NonCommercial 3.0 Unported License.
Just for newbies wondering what this really means:
1. install and boot into TWRP/CWM recovery means you boot up a 'mini' linux which can do whatever it wants(as root) to any of the partition on the device(including the /system one)
2. the supersu package contains 2 files(an APK and the more importantly 'su') plus some update scripts that (1) would run and copy them to the appropriate places(mainly the 'su' which is the only file that is critical)
I think you need to mention the bootloader unlock someplace.
Perhaps you can find those specific instructions in another good reference thread; but if not then, at a minimum you should put it in your prerequisites list.
In the narrative as it stands, you casually mention the other thread
[GUIDE] Flashing a Factory Image with fastboot / return to stock
but don't insist that your reader looks at that thread.
But the time for doing the unlock sequence follows the begginers first (fastboot) driver installation, so unless someone reads that thread pretty thoroughly, they will skip it in your description here, and will get stopped out at
Code:
fastboot boot TWRP.img
which needs the privileges of an unlocked bootloader. Since unlocking the bootloader currently entails performing a full-phone wipe, the consequences of that are pretty significant and shouldn't be skipped over.
cheers. Thanks.
bftb0 said:
I think you need to mention the bootloader unlock someplace.
Perhaps you can find those specific instructions in another good reference thread; but if not then, at a minimum you should put it in your prerequisites list.
In the narrative as it stands, you casually mention the other thread
[GUIDE] Flashing a Factory Image with fastboot / return to stock
but don't insist that your reader looks at that thread.
But the time for doing the unlock sequence follows the begginers first (fastboot) driver installation, so unless someone reads that thread pretty thoroughly, they will skip it in your description here, and will get stopped out at
Code:
fastboot boot TWRP.img
which needs the privileges of an unlocked bootloader. Since unlocking the bootloader currently entails performing a full-phone wipe, the consequences of that are pretty significant and shouldn't be skipped over.
cheers. Thanks.
Click to expand...
Click to collapse
Hello!
Thanks for your answer, I completely forgot about the "Unlocking Bootloader" part, tomorrow when I get some time I will edit the thread...
Have a good day/night.
Edit: Added "Unlocked Bootloader" to the requisites list and a small note after "Make sure you have USB Debugging enabled in your Nexus 7", tomorrow I may edit the thread again.
Edit 2: I think the essential part is written, and because I'm a little busy, I will leave (temporarily) this thread. You're free to enhance this guide and re-publish it following Creative Commons Attribution-NonCommercial 3.0 Unported License.
I'm trying to install TWRP via ADB on my Galaxy S5 LTE but after rebooting into bootloader mode TWRP can't be flashed.
Current OS is an unofficial Cyanogenmod 13 from xda-developers.
What I did so far ( from this guide: https://www.xda-developers.com/how-to-install-twrp/):
- installed ADB and Fastboot
-downloaded the newest version of TWRP for my device (twrp-3.2.1-0-kccat6.img)
-USB-Debugging turned on
-Connected phone with PC and started cmd.exe as admin in the same folder as the TWRP-file
- typed adb reboot bootloader and device asked for permission to grant USB-Debugging, after allowing it, I had to send the command again
- Device boots into bootloader and Windows installed a new driver
- after the new driver is installed, I entered fastboot flash recovery twrp-3.2.1-0-kccat6.img into the command prompt
No further process is possible at this point, command prompt is stating "waiting for device" and the device just stays in the bootloader without displaying any process.
Kolon22 said:
I'm trying to install TWRP via ADB on my Galaxy S5 LTE but after rebooting into bootloader mode TWRP can't be flashed...
Click to expand...
Click to collapse
I don't have this device but, your best bet is to take a look at (and, if needed, post your question for some member guidance) the following Official TWRP thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3350160
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Thanks for your help.
I was able to install TWRP by using Odin3.
Help me to wake up my dead huawei y3 2017
Dulanjana Udekantha said:
Help me to wake up my dead huawei y3 2017
Click to expand...
Click to collapse
I don't have this device but, you may be able to obtain locate what you need or obtain some member guidance within the following thread.
https://forum.xda-developers.com/showthread.php?t=3440664
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Possible fix for you
Hi all.
This may or may not work.. But I have managed to recover a couple of different phone makes using the following method:
This is my method offered, not taken from any other post on the net.
****NB-if your computer does not recognise your device once plugged into the USB port, skip this whole tutorial and have a good day further?
Basically, download the entire firmware file, which must include a system.img and or a boot.img file.
Once downloaded, extract all the info to a folder, and move the system.img and boot.img to your adb local file folder(where you run your adb.exe from).
Open command prompt with elevated Admin rights and navigate to your adb folder, and run the following commands:
Adb start-server
This should state something like, server is running..... With port nr. Blah blah
Now enter the following commands:
adb reboot fastboot
Fastboot flash system.img
and wait for this to complete.
Now enter command:
Fastboot flash boot.img
***Note-this command may not always work and is not always necessary depending on the level of bricked-Ness done to your device.
And now enter the following command:
Adb reboot
And hopefully, this may (or may not) resolve the issue at hand.
Thank you kindly.
Wynand Rühle
Not even going to keep this for the learning experience, it's not worth it.
Hi! Tks for you suport.
I have 2 questions if you can help me. I´m a noob for this phone, but i used to update mu Xperia with Remix and i unsdestand a little bit of installing costum firmware.
1- Do we need after this to install again stock boot.img? Because i read in were and MIUI forum that patch boot.img will not give OTA updates.
But installing stock will not remove Camera2api also?
2- I Have V9.6.13.0.ODIMIFE ( second september update) i try to seach for patch boot.img for A2 in were, but i only find the full stock image
in https://forum.xda-developers.com/mi-a2/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824849
I read what you said about teaching to fishing rather give a fish, but if for this thime you could put the link, in future updates we all will be more confortable do do other updates.
Kind regards
ki69 said:
1- Do we need after this to install again stock boot.img? Because i read in were and MIUI forum that patch boot.img will not give OTA updates.
But installing stock will not remove Camera2api also?
Click to expand...
Click to collapse
Ki, this is a great example of where one needs to look carefully at the command, and do some research. If you look closely the code says "boot" patched_boot. The point there is that it doesn't say "flash". Booting it won't flash it. That command will read it from your hard drive into rom memory of the device, and NOT write it to the flash memory of the device. I.E. The boot.img on the device will not change, so no reason to flash it again.
ki69 said:
2- I Have V9.6.13.0.ODIMIFE ( second september update) i try to seach for patch boot.img for A2 in were, but i only find the full stock image
in https://forum.xda-developers.com/mi-a2/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824849
Click to expand...
Click to collapse
Bring up all the topics in the MiA2 Guide(s) forum. At the top right is "Search This Forum". So... obviously... type in; patched_boot.
The first thread, OTA Jasmine (etc) has many posts with links to specific versions of (magisk) patched_boot images. (hint; search that thread also if you don't want to page through the posts!) - and don't forget to thank (use thank button!) cpkv5 for his efforts of extracting the boot.img and patching it for everyone, and making it available for easy download!
AsItLies said:
So to enable Cam2API w/out root, and continue to get OTA updates;
1) You need to be familiar with using ADB and FASTBOOT. Pls look at easily searchable documentation for them. Have them installed and usable on your pc / laptop. Try some of the commands out before using this guide, to get use to them / verify working.
2) You have to unlock the bootloader, which will wipe the device. It will also have to stay unlocked, which means your phone will be considered 'uncertified' in Play Store. Because we don't have NFC, and I don't do any banking apps on my phone... no worries for me.
3) You need the patched_boot.img for your current software version. The patched image (and the original boot image) are readily available. Just search the MiA2 forums and you'll find numerous links to new and previous images for the various software versions that have existed for our MiA2's.
So, you should already know how to enable adb and to OEM unlock in developer options (pls SEARCH if not!). So make an adb connection to do:
Code:
adb devices
The above will verify your pc sees the phone, obviously.
Code:
adb reboot bootloader
The above is an easy way to get to fastboot mode.
Code:
fastboot devices
The above will verify fastboot sees our device
Code:
fastboot oem unlock
The above unlocks the bootloader and wipes / reboots device. Again recheck to be sure in Dev options adb is on.
Code:
adb reboot bootloader
Above to get back to fastboot mode.
Code:
fastboot boot patched_boot.img
The above will now boot the device. Be sure the patched boot image is in the directory you are issuing the command from, and again, it needs to be the patched image that corresponds to the current software version you are using.
At this point, I'd recommend to not do anything with the device. It should be booted and appear normal. Back at our command prompt;
Code:
adb devices
Assuming we still see our device:
Code:
adb shell
The above will now put our command prompt into a linux shell, and then type the following:
Code:
setprop persist.camera.HAL3.enabled 1
and then
Code:
setprop persist.camera.eis.enable 1
At this point, it's about done. The above settings will get propagated to the appropriate tables after rebooting the device. They won't change system settings. So OTA updates should work.
Next, we just type 'exit' in the command prompt to exit the adb shell. Lastly we again issue 'adb reboot bootloader' and once we're back into fastboot, just issue 'fastboot reboot'.
That's it. We never flashed anything, only booted the patched image. So nothing really gets touched, that could inhibit OTA updates. When we do the reboot, it will read the original (untouched) boot image and boot as normal. This also keeps us from touching the other 'Slot' (not really needed). This is much simpler than using TWRP imho.
Click to expand...
Click to collapse
THANKS MATE, I REACHED TO FINAL STAGE & BOOTED IN TO THE PATCHED IMAGE BUT
AFTER putting command prompt into a linux shell it gives error failed to set property. please help i am awiting your reply.
Abbey Bhatt said:
THANKS MATE, I REACHED TO FINAL STAGE & BOOTED IN TO THE PATCHED IMAGE BUT
AFTER putting command prompt into a linux shell it gives error failed to set property. please help i am awiting your reply.
Click to expand...
Click to collapse
Yes I saw that Abbey, just updated the original post. At this point pls use the TWRP method I mentioned in similar thread. That works for sure.
I thought the Magisk patched boot image would have the same abilities (in this sense) as twrp, but it seems it does not. Will update if I find a solution.
Abbey Bhatt said:
THANKS MATE, I REACHED TO FINAL STAGE & BOOTED IN TO THE PATCHED IMAGE BUT
AFTER putting command prompt into a linux shell it gives error failed to set property. please help i am awiting your reply.
Click to expand...
Click to collapse
hey mate after rebooting, magisk appeared in app drawer, did i flashed patched boot image. by using this code? please advise
AsItLies said:
Ki, this is a great example of where one needs to look carefully at the command, and do some research. If you look closely the code says "boot" patched_boot. The point there is that it doesn't say "flash". Booting it won't flash it. That command will read it from your hard drive into rom memory of the device, and NOT write it to the flash memory of the device. I.E. The boot.img on the device will not change, so no reason to flash it again.
Click to expand...
Click to collapse
Yes, i didn´t read carefully, but my question has because i read that we need magisk after put patche boot.img, then enable, then remove magisk then flash stock boot.img
I read that you update the firt post informing of the need of that.
AsItLies said:
Bring up all the topics in the MiA2 Guide(s) forum. At the top right is "Search This Forum". So... obviously... type in; patched_boot.
The first thread, OTA Jasmine (etc) has many posts with links to specific versions of (magisk) patched_boot images. (hint; search that thread also if you don't want to page through the posts!) - and don't forget to thank (use thank button!) cpkv5 for his efforts of extracting the boot.img and patching it for everyone, and making it available for easy download!
Click to expand...
Click to collapse
Sorry, i only find this one:
https://forum.xda-developers.com/showpost.php?p=77295065&postcount=22
that have magisk, but with that like i said before i will mess with system/root, the thing i did´t want. so for me is not the path i want to take. I prefer the patch you give in:
https://forum.xda-developers.com/mi-a2/how-to/guide-enable-cam2api-root-t3848058
And because is a diferente path i think that that thread should be reopen by mods.
Abbey Bhatt said:
hey mate after rebooting, magisk appeared in app drawer, did i flashed patched boot image. by using this code? please advise
Click to expand...
Click to collapse
It shouldn't have flashed it, should have just booted it. I just uninstalled the magisk in app drawer myself. It looks as though a part of the magisk patched boot image installs that 'stub' part of magisk, to then allow a full install I'm sure. So that seems to happen whether you flash it or boot it.
ki69 said:
Yes, i didn´t read carefully,
Sorry, i only find this one:
Click to expand...
Click to collapse
You're looking in the ROM forums, not the indicated GUIDES forum.
AsItLies said:
It shouldn't have flashed it, should have just booted it. I just uninstalled the magisk in app drawer myself. It looks as though a part of the magisk patched boot image installs that 'stub' part of magisk, to then allow a full install I'm sure. So that seems to happen whether you flash it or boot it.
Click to expand...
Click to collapse
hey i am now wish to follow method presented in this thread
https://forum.xda-developers.com/mi-a2/how-to/guide-enable-cam2api-root-t3848058
but at stage of fastboot getvar currdent-slot
it showing failed. no any partition showed
Abbey Bhatt said:
hey i am now wish to follow method presented in this thread
https://forum.xda-developers.com/mi-a2/how-to/guide-enable-cam2api-root-t3848058
but at stage of fastboot getvar currdent-slot
it showing failed. no any partition showed
Click to expand...
Click to collapse
Not sure what's going on. When I do the same the result is:
fastboot getvar current-slot
current-slot: b
Finished. Total time: 0.000s
Did you flash it by mistake instead of boot it? Have you tried to do a 'fastboot set_active' ?
AsItLies said:
Not sure what's going on. When I do the same the result is:
fastboot getvar current-slot
current-slot: b
Finished. Total time: 0.000s
Did you flash it by mistake instead of boot it? Have you tried to do a 'fastboot set_active' ?
Click to expand...
Click to collapse
Humble request,
If you don't know about device or appropriate procedure don't post irrelevant things. As I know this device is tricky and more chances for hard brick if something goes wrong.
Abbey Bhatt said:
Humble request,
If you don't know about device or appropriate procedure don't post irrelevant things. As I know this device is tricky and more chances for hard brick if something goes wrong.
Click to expand...
Click to collapse
out and out flagrant request, if you can't follow directions, don't even try what is suggested.
There's no way anything I indicated would brick a phone. I've done it. Mine is not bricked. As indicated the setprop commands won't work with patched boot image. Then all you have to do is exactly what the procedure says and it's back to normal.
You're the reason people don't bother to post guides.
I do know about device and relevant procedure, it's not irrelevant. Your inability is what's irrelevant.
AsItLies said:
out and out flagrant request, if you can't follow directions, don't even try what is suggested.
There's no way anything I indicated would brick a phone. I've done it. Mine is not bricked. As indicated the setprop commands won't work with patched boot image. Then all you have to do is exactly what the procedure says and it's back to normal.
You're the reason people don't bother to post guides.
I do know about device and relevant procedure, it's not irrelevant. Your inability is what's irrelevant.
Click to expand...
Click to collapse
Hero how's your age how long been in this you are the people who doesn't know things and phones and wage all around being as op. Now cut this crappy out and first learn and then come for advice.
Abbey Bhatt said:
Hero how's your age how long been in this you are the people who doesn't know things and phones and wage all around being as op. Now cut this crappy out and first learn and then come for advice.
Click to expand...
Click to collapse
I'm sorry you screwed up your device. But it's not my fault. Nothing I indicated, if followed, would have caused that.
I'd suggest quitting the childish attempts at personal attacks. Your problems are not my fault.
@oka1 Hi again, sorry, this is the 2nd time! Please close this thread, and delete if possible. It' no longer provides any benefit.
Thanks! Won't happen again.
Hello,
After unlocking my bootloader, I managed to install TWRP. As indicated in the tutorial in fastboot mode (volume + and input) I managed to enter TWRP mode, except during a new boot impossible to start in TWRP mode I find the recovery of MI, after looking on the net, I didn't find anything really concrete I wouldn't want to brick my phone, does anyone have a solution?
Thanking you for your collaboration
(Sorry if this topic has already been covered in this forum but I couldn't find anything concerning the MI 9T), thank you if possible to detail the manipulation, I know nothing about it
This is from the twrp website https://twrp.me/xiaomi/xiaomimi9t.html
Note many devices will replace your custom recovery automatically during first boot.
Click to expand...
Click to collapse
After flashing the recovery :
Code:
fastboot flash recovery twrp.img
enter the code to reboot in recovery :
Code:
fastboot oem reboot-recovery
DELLINSPIRON1958 said:
Hello,
After unlocking my bootloader, I managed to install TWRP. As indicated in the tutorial in fastboot mode (volume + and input) I managed to enter TWRP mode, except during a new boot impossible to start in TWRP mode I find the recovery of MI, after looking on the net, I didn't find anything really concrete I wouldn't want to brick my phone, does anyone have a solution?
Thanking you for your collaboration
(Sorry if this topic has already been covered in this forum but I couldn't find anything concerning the MI 9T), thank you if possible to detail the manipulation, I know nothing about it
Click to expand...
Click to collapse
U have to flash the modified vbmeta.img in order to keep a custom recovery..
Hello ,
There is no other solution ?
DELLINSPIRON1958 said:
Hello ,
There is no other solution ?
Click to expand...
Click to collapse
Have you tried by forcing reboot to Recovery/TWRP right after flashing TWRP (answer from another user, post #2):
>>fastboot oem reboot-recovery
Are you using e.g. the official TWRP 3.4.0, and did you enter in TWRP your Android screen unlock code, for TWRP to be able to properly work with File Systems on Data and Internal memory?
I am a neophyte, can you give me precise details of the method, thanking you
DELLINSPIRON1958 said:
I am a neophyte, can you give me precise details of the method, thanking you
Click to expand...
Click to collapse
Read post #2 - if you are not familiar with Fastboot, please search by Google and read - but how else did you flash TWRP than from Fastboot.
After flashing TWRP from Fastboot (1st command), use 2nd command to force direct rebooting to TWRP - without pinpointing with Vol+&Pow buttons, etc.
But really, nothing else, just that
Search here for thread about Official TWRP 3.4.0, download and flash that TWRP for davinci
When you enter to TWRP, it will ask you for your Android screen unlock pin/password (you should know your own one you use when booting to Android and when you are unlocking the locked screen in Android), enter that one when TWRP prompts you and wait few seconds (it should report success)
There is no rocket science here to teach more about ?, you just need to follow and try
Thanks for the information, I'll try. However, are you sure that I will have TWRP as a start-up recovy and that every time I do Volume + Enter? ( translate google)
DELLINSPIRON1958 said:
Thanks for the information, I'll try. However, are you sure that I will have TWRP as a start-up recovy and that every time I do Volume + Enter? ( translate google)
Click to expand...
Click to collapse
Try as described above:
- download official TWRP for davinci
- flash from Fastboot and reboot to TWRP with the given command
- in TWRP, enter your Android screen unlock code and check does TWRP correctly read your files on Internal memory (e.g. seeing proper file names in Download, not some garbage names)
- try to reboot to recovery (by TWRP command or by using Vol+) and check if it reboots to TWRP, not to stock Recovery
Please don't waste time by further endless questions, until you first try and have concrete questions/results (can't expect that people will pay attention to answer if you at least don't even try - why should then anybody waste the time)
I can't guarantee you 100% but I always have bootable TWRP, properly reading Storage (I also have boot.img patched by Magisk, hence not 100% same environment like you)
Thank you for your "kindness" If I ask myself several questions it is not when the phone is blocked on it is necessary to ask questions
I had the same issue, I tried everything event then wasnt able to boot to Ofox recovery. But someone suggested, to flash the recovery, get into it WITHOUT booting to system, then flash magisk. Now reboot to system and uninstall magisk/Flash/do whatever you want! That worked for me.
thank you for your reply. while searching on the net, I noticed that there are several answers to this problem, but which one is the right one?
without the phone being out
DELLINSPIRON1958 said:
Thank you for your "kindness" If I ask myself several questions it is not when the phone is blocked on it is necessary to ask questions
Click to expand...
Click to collapse
For each member you can simply judge the credibility of his posts by his 'degree' on XDA forum, for which devices and topics he mostly diiscusses about and how many people thanked his posts
E.g. if I ask how to flash Xiaomi, Mi 9T and receive a suspicious 'guide' from somebody who only participated in discussions about Nokia phones, and who even did not get Thanks there for his participation, I will probably fully ignore and not risk to brick my phone
But if I get an answer from somebody who maybe participated for a year or two in topics on Poco and Redmi Note but who got hundreds of Thanks for his posts there, I will consider that he likely very well knows about flashing Xiaomi phones, although maybe never had Mi 9T in his hands.
Moreover, if I see that two or more people guide me in the same direction.
So I would at least google myself for more info (and then ask if still something not clear), and try - specially if that what was suggested does not sound as something to potentially brick my phone
After all, this is hackers forum and everybody is responsible himself for his phone. But on the other side, nobody was born with the knowledge but learnt by searching, reading and trying things herself
Also, everybody helps for free and by his good will, and sooner or later finds useless to waste time to answer for something that was already answered by his best (what else/new to answer), but the other one did not even want to try
Of course (as also in my previous post), things work for me as you wanted but yes, I always immediately flash together the boot image patched by Magisk.
So you can try would it work with the fully stock Boot - if yes, good for you.
If not, you can consider going to root by Magisk (although, being so cautious, it would probably take much more time and many, many more new questions before ?)
Kaiwalya said:
I had the same issue, I tried everything event then wasnt able to boot to Ofox recovery. But someone suggested, to flash the recovery, get into it WITHOUT booting to system, then flash magisk. Now reboot to system and uninstall magisk/Flash/do whatever you want! That worked for me.
Click to expand...
Click to collapse
So just tested the following on my MIUI 12.0.2 QFJEUXM, with (unofficial) TWRP 3.4.0.2 from brigudav and Canary Magisk 20424
- Booted to TWRP and flashed stock 12.0.2 eea Boot.img
- Immediately rebooted back to Recovery - that is to TWRP and (that step is also important!) entered my Android screen unlock pin to assure that TWRP 'touched' the Data
- Rebooted to Android (System), where ofc, Magisk Manager showed that Magisk was no more installed
Then rebooted to Recovery (by keeping pressed Vol+) and phone booted to TWRP, not to the stock Recovery!!!
Hence the stock Boot image did not overwrite my TWRP with stock Recovery (although without having Magisk flashed at the time), because of properly doing each and every step as above!
(At the end, flashed back my patched Boot.img from TWRP, rebooted to Android and continued to use Magisk with all previously installed modules, etc)
Btw, I have never flashed any VBMeta, decrypted storage or so
PS:
And believe me, I lost myself TWRP many times (having to reflash it from Fastboot again and again when I was uninstalling Magisk, updating MIUI from TWRP and so), before learning that every step counts?.