Related
As the title says I am unable to boot after flashing Magisk (tried v16 and v15.3). It boots fine without magisk but of course no root and no custom recovery. Any help would be appreciated. Didn't have any problems on the previous stable build.
You need to first flash OOS 5.1 let it boot, then go to fastboot and flash twrp then go to twrp and flash magisk, only way to get root
hello, that's what I did and it worked well
this has happened here since 5.0.4
Try to use lastest blu-spark's TWRP, then flash 5.1 & Magisk without extra boot in the middle.
Things I noticed when upgrading:
A) The latest TWRP for dumpling appears to be broken. I get an error mounting /vendor when I use it. I switched to the previous version (20180309) and the error went away and everything seems to work.
B) You may very well have Xposed installed. If you do, there is an SDK bump between OOS 5.0.x and 5.1.x (26 -> 27). You'll need to disable this module either before you install the update (or assuming you already have) remove the module using something like Magisk Manager for Recovery to remove it (reboot to recovery, install module, run mm from terminal, follow prompts).
-Toucan
ToucanSam said:
Things I noticed when upgrading:
A) The latest TWRP for dumpling appears to be broken. I get an error mounting /vendor when I use it. I switched to the previous version (20180309) and the error went away and everything seems to work.
B) You may very well have Xposed installed. If you do, there is an SDK bump between OOS 5.0.x and 5.1.x (26 -> 27). You'll need to disable this module either before you install the update (or assuming you already have) remove the module using something like Magisk Manager for Recovery to remove it (reboot to recovery, install module, run mm from terminal, follow prompts).
-Toucan
Click to expand...
Click to collapse
It's not broken. The vendor error message is because it was recently updated to work better with Project treble, which uses a hidden partition for the vendor. You can simply ignore the error and it will work fine. Or if you flash a treble ROM, the error will then go away.
I just got the phone. Format it in recovery.
Flash latest blu spark twrp (v.8.73).
Flash the Oos ob06.
Reboot to system. Set the phone, instal apps from Play.
Reboot to Fastboot.
Reflash recovery.
Reboot to recovery.
Flash Magisk 15.3. Reboot to system. OK.
Updated Magisk with Magisk.
Hi, Can anyone help me. in my oneplus 5T after installing new rom it is working smooth but i can't upgrade to new updates. in recovery mode the files seems to be decrypted and cant find any folders where i copied the updation . instead new files are found and can't access and find any of the folders of my own. this happened after i input the security lock. i wiped the entire data and installed new roms still it seems so. somebody please help me to find a solution for this
Hello everyone,
I have the Xiaomi Redmi 5A.
Currently I am running Official Pixel Experience ROM (8.1.0, oreo) https://forum.xda-developers.com/xiaomi-redmi-5a/development/rom-pixel-experience-t3801702 on it. It so happens that when I try to flash SuperSU latest zip, the flashing goes fine but the device doesn't get rooted on checking in a root checker app and also no SuperSU app comes in the app drawer after flashing. I am not sure why this happens. But flashing magisk roots the device. Why not SuperSU?
In the Pixel Experience ROM thread they told to use vendor TWRP and not the Official TWRP but even on vendor TWRP I don't get root access after flashing SuperSU...
Previously I was using Unofficial Lineage OS (14.1, nougat) https://forum.xda-developers.com/xi.../unofficial-lineage-os-14-1-redmi-5a-t3773985 on my device. In Lineage OS when I flash SuperSU I get root access and also the SuperSU app comes in the app drawer. Why not in Pixel Experience?
Is the kernel responsible for this?
Is it something related to "mount"?
I come across this "mount" word in TWRP but I'm not sure what does this mean...
In TWRP while flashing SuperSU I saw "ramdisk restore failed, aborting". What does that mean?
Also is it related to SuperSU being a system-less root software and magisk being a system-based one?
Please help me... It's driving me nuts!:crying:
P.S. I know magisk is better but I want SuperSU, so don't suggest me to use magisk and forget SuperSU.:laugh:
Thanks.
Shakti Panda said:
Hello everyone,
I have the Xiaomi Redmi 5A.
Currently I am running Official Pixel Experience ROM (8.1.0, oreo) https://forum.xda-developers.com/xiaomi-redmi-5a/development/rom-pixel-experience-t3801702 on it. It so happens that when I try to flash SuperSU latest zip, the flashing goes fine but the device doesn't get rooted on checking in a root checker app and also no SuperSU app comes in the app drawer after flashing. I am not sure why this happens. But flashing magisk roots the device. Why not SuperSU?
In the Pixel Experience ROM thread they told to use vendor TWRP and not the Official TWRP but even on vendor TWRP I don't get root access after flashing SuperSU...
Previously I was using Unofficial Lineage OS (14.1, nougat) https://forum.xda-developers.com/xi.../unofficial-lineage-os-14-1-redmi-5a-t3773985 on my device. In Lineage OS when I flash SuperSU I get root access and also the SuperSU app comes in the app drawer. Why not in Pixel Experience?
Is the kernel responsible for this?
Is it something related to "mount"?
I come across this "mount" word in TWRP but I'm not sure what does this mean...
In TWRP while flashing SuperSU I saw "ramdisk restore failed, aborting". What does that mean?
Also is it related to SuperSU being a system-less root software and magisk being a system-based one?
Please help me... It's driving me nuts!:crying:
P.S. I know magisk is better but I want SuperSU, so don't suggest me to use magisk and forget SuperSU.:laugh:
Thanks.
Click to expand...
Click to collapse
Hello,
I don't know exactly what you are encountering but SuperSU should work on this ROM and run fine. I ran this ROM before and SuperSU works fine. I now switched to Magisk because I need ViPER4Android to work on Oreo.
Unless you are running a Treble based ROM, that is a different story. If you are running a Treble based ROM, please refer to this https://forum.xda-developers.com/showpost.php?p=76937637&postcount=24 thread to get root working.
CONTINUE TO READ IF YOU ARE NOT RUNNING A TREBLE BASED ROM,
I need to get some things straight. Android with version 6.0 (Marshmallow) and above (should) and (only) run systemless mode (including SuperSU). I came across a thread and read that root with Marshmallow and above would not work without patching bootloader and make system unmodified.
SuperSU and Magisk are almost the same. Magisk just offers extra module repository and SuperSU just offers root. SuperSU works both in system mode and systemless mode but Magisk only works in systemless mode.
This might help you:
- Do a clean flash (Wipe System, Data and Cache)
- Try using this latest version of SuperSU: https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 (SuperSU v2.82 SR5 released by Chainfire himself)
- If it doesn't work then something might be wrong with the boot partition.
- If you really need root and SuperSU REALLY DOESN'T WORK, (spoiler) try Magisk...
Growtopia Jaw said:
Hello,
I don't know exactly what you are encountering but SuperSU should work on this ROM and run fine. I ran this ROM before and SuperSU works fine. I now switched to Magisk because I need ViPER4Android to work on Oreo.
Unless you are running a Treble based ROM, that is a different story. If you are running a Treble based ROM, please refer to this https://forum.xda-developers.com/showpost.php?p=76937637&postcount=24 thread to get root working.
CONTINUE TO READ IF YOU ARE NOT RUNNING A TREBLE BASED ROM,
I need to get some things straight. Android with version 6.0 (Marshmallow) and above (should) and (only) run systemless mode (including SuperSU). I came across a thread and read that root with Marshmallow and above would not work without patching bootloader and make system unmodified.
SuperSU and Magisk are almost the same. Magisk just offers extra module repository and SuperSU just offers root. SuperSU works both in system mode and systemless mode but Magisk only works in systemless mode.
This might help you:
- Do a clean flash (Wipe System, Data and Cache)
- Try using this latest version of SuperSU: https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 (SuperSU v2.82 SR5 released by Chainfire himself)
- If it doesn't work then something might be wrong with the boot partition.
- If you really need root and SuperSU REALLY DOESN'T WORK, (spoiler) try Magisk...
Click to expand...
Click to collapse
Thanks man.
I'll try that for sure but later i.e., doing a clean flash and trying to flash SuperSU again...
I'll let you know once I've done that.
Thanks again man!!!:angel:
Shakti Panda said:
Thanks man.
I'll try that for sure but later i.e., doing a clean flash and trying to flash SuperSU again...
I'll let you know once I've done that.
Thanks again man!!!:angel:
Click to expand...
Click to collapse
Sure, no problem
My goal is to get a GSI with Android 11 or higher installed with the corresponding Mint Kernel. The reason being is I can't Magisk root a GSI (tried various methods like: Magisk patch TWRP recovery, install Magisk zip in recovery) and I believe the ramdisk=no is the problem on the SM-A505W variant of the Galaxy A50. I have rooted Pixel phones easily in the past.
I read a suggestion somewhere that installing Mint Kernel could help make rooting easier since Magisk is pre-installed (true?), but I can't get any GSI + Mint Kernel to boot.
GSIs attempted = lineage 18.1, 19.1, Palladium (android 11), SparkOS, Pixel Experience (android 11, 12)
I've then gone to fetch the corresponding Mint Kernel from https://github.com/FreshROMs/android_kernel_samsung_exynos9610_mint/releases
Is my variant just not able to work with Mint Kernel? I'm sure someone, somewhere knows a GSI and Mint Kernel combo that works and allows for Magisk rooting. If so, pls identify versions and any methods you used.
frustrated
p.s. Magisk 25.2 is my preference as I like this version best so far
p.s.s. I do use the key combo to boot from recovery vs system when trying to boot with Magisk when using only a GSI. Only been able to root stock firmware by Magisk patching AP file and flashing with ODIN, then using key combo VOL_UP + POWER (hold a few seconds) when powering phone to boot.
If you're able to boot a GSI with the stock kernel but not the Mint kernel, it sounds like the latter has some dependencies that a GSI does not provide.
Not having ramdisk should not prevent root. Using the stock kernel and a GSI, flash Magisk in TWRP following the GSI; once you install the Magisk app, you should have root access. This is the method I use on my Tab A 8.0, running the AOSP 13 GSI with the CUK4 kernel.
V0latyle said:
If you're able to boot a GSI with the stock kernel but not the Mint kernel, it sounds like the latter has some dependencies that a GSI does not provide.
Not having ramdisk should not prevent root. Using the stock kernel and a GSI, flash Magisk in TWRP following the GSI; once you install the Magisk app, you should have root access. This is the method I use on my Tab A 8.0, running the AOSP 13 GSI with the CUK4 kernel.
Click to expand...
Click to collapse
After GSI is installed, with stock kernel, once I flash Magisk 25.2 in TWRP (tried several TWRP versions I could find 3.5, 3.6, 3.7...) when I boot with VOL_UP + POWER (held for a few seconds) I either boot into recovery again OR dont have root when booted into android.
I believe this is the procedure (from what I've read).
With stock firmware, I get root holding VOL_UP + POWER (for a few seconds prior to booting). I dont use TWRP in this case, rather ODIN to flash Magisk patched AP file.
GreekFire123 said:
After GSI is installed, with stock kernel, once I flash Magisk 25.2 in TWRP (tried several TWRP versions I could find 3.5, 3.6, 3.7...) when I boot with VOL_UP + POWER (held for a few seconds) I either boot into recovery again OR dont have root when booted into android.
I believe this is the procedure (from what I've read).
Click to expand...
Click to collapse
If you're flashing Magisk in TWRP, you don't need to boot into recovery. The recovery hijack is only for use with the stock recovery; no key combo is needed to enable root.
Again, the Ramdisk field does not have anything to do with whether or not you have root. When in the Magisk app, the Installed field should show the Magisk verision (25200). If it says N/A, you don't have root.
If you continue to have issues, this is what I suggest:
Use Odin to reflash everything back to stock
Flash the latest TWRP build for your device
Boot into TWRP, format both /system and /data (do NOT wipe /boot)
Install GSI to /system
Install Magisk
Reboot to system
V0latyle said:
If you're flashing Magisk in TWRP, you don't need to boot into recovery. The recovery hijack is only for use with the stock recovery; no key combo is needed to enable root.
Again, the Ramdisk field does not have anything to do with whether or not you have root. When in the Magisk app, the Installed field should show the Magisk verision (25200). If it says N/A, you don't have root.
If you continue to have issues, this is what I suggest:
Use Odin to reflash everything back to stock
Flash the latest TWRP build for your device
Boot into TWRP, format both /system and /data (do NOT wipe /boot)
Install GSI to /system
Install Magisk
Reboot to system
Click to expand...
Click to collapse
thanks for the reply.
Followed the above steps, "installed" field = N/A so no root
Can't believe how hard it is to get root on this device with a GSI...
Using TWRP from: https://www.recovery-mode.com/twrp/twrp-3-7-0-for-samsung-galaxy-a50-a505x-update-20221026.html
TWRP file/version download=TWRP_v3.7.0-Unofficial_a50-1666700564.tar
GreekFire123 said:
thanks for the reply.
Followed the above steps, "installed" field = N/A so no root
Can't believe how hard it is to get root on this device with a GSI...
Using TWRP from: https://www.recovery-mode.com/twrp/twrp-3-7-0-for-samsung-galaxy-a50-a505x-update-20221026.html
TWRP file/version download=TWRP_v3.7.0-Unofficial_a50-1666700564.tar
Click to expand...
Click to collapse
Weird. Do you get any errors in TWRP when flashing Magisk?
Were you able to root the stock ROM?
V0latyle said:
Weird. Do you get any errors in TWRP when flashing Magisk?
Were you able to root the stock ROM?
Click to expand...
Click to collapse
Installation completed (appeared) successfully in TWRP. No errors when I read line-by-line. I installed it as a zip.
I can root the stock ROM, but didn't do it on this attempt before installing GSI. I followed the instructions above to a tee just to make sure.
To root the stock ROM I have to magisk patch the AP file (from stock) and flash that with ODIN. Then use special key combo to boot (VOL_UP + POWER) with root.
GreekFire123 said:
Installation completed (appeared) successfully in TWRP. No errors when I read line-by-line. I installed it as a zip.
I can root the stock ROM, but didn't do it on this attempt before installing GSI. I followed the instructions above to a tee just to make sure.
To root the stock ROM I have to magisk patch the AP file (from stock) and flash that with ODIN. Then use special key combo to boot (VOL_UP + POWER) with root.
Click to expand...
Click to collapse
you can't flash magisk as zip to the recovery on old samsung devices "read magisk FAQs for samsung devices". Check out the fresh discord server so that you can get more assistance directly from the dev.
Hi, I got myself an used Motorola Moto G7 play (XT1952-1) with Android 10 Stock update (Build QPYS30.52-22-8-9) and just can't successfully install TWRP on it. What I did:
- Bootloader unlocked
- TWRP temporary loaded with fastboot (fastboot boot twrp.img)
- In TWRP 'Iinstall' selected the matching TWRP .zip and it said it was installed in both slots a and b.
But then, when I select 'restart to bootloader' and try to launch recovery, I get a bootloop (black screen with (N/A) in the top left corner. The OS as such still starts normally. So I guess the main problem here is the bootloop when trying to launch recovery...?
I tried installing over booted TWRP with unmodified boot.img and with Magisk patched boot.img, same result. The G7 play does not have a separate revovery partition, recovery is included in the boot.img
I used the TWRP files (EU) and instructions from here:
Motorola Moto G7 Play
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
My stock firmware is XT1952-1_CHANNEL_RETEU_10_QPYS30.52-22-8-9_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip from here:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Am I missing something? I've now searched for days (most info is outdated, taken from other places/Motorola phones with just 'G7 play' added, or is ambiguous); so can anyone *PLEASE* help me? Does anyone have a G7 play of the same type with Android 10 Stock who has successfully installed TWRP and was able to access the Recovery afterward without being stuck in a loop?
I also can't create a TWRP backup with a fastboot booted TWRP because system (and internal SD too) seems to be encrypted, and I don't seem to be able to deactivate this in the phone. Is this normal? Some places say that TWRP can decrypt when it's installed permanently...
Or could anybody patch the boot.img in above Firmware and add TWRP for me so I can just flash the boot.img?
Thanks in advance... please reply noob-friendly.
Still need a patched boot.img? Attached you'll find a boot.img with TWRP installed. I followed your links to get boot.img + twrp.img.
NO MAGISK INSTALLED!!!Please patch before flashing if Magisk is already installed.
I put a log of the repack command into the zip that is showing the checksums of the boot header. Just to have a proof.
WoKoschekk said:
Still need a patched boot.img? Attached you'll find a boot.img with TWRP installed.
Click to expand...
Click to collapse
Thanks for trying to help, but this boot.img behaves exactly like the one I made by following the installation instructions on the TWRP website. I flashed it, restarted bootloader, then tried to go into recovery, and it bootloops (black screen with N/A in the top left corner).
But what I need is a boot.img with a WORKING TWRP recovery (that can actually be launched when recovery is selected...
Any idea why this won't work, why TWRP won't start?
@Alonso_Quixana Try the attached one. It's a boot.img patched with twrp + recovery_dtbo. The recovery_dtbo is part of the twrp.img but TWRP's installer.zip doesn't take it into account while repacking the patched boot.img. Maybe (hopefully!) that's the reason why you're able to boot TWRP but not to install it permanently.
Please try also - in any case! - the patched installer.zip that comes with a recovery_dtbo.
Sadly, you can't flash TWRP on stock ROM, in case you did sucessfully, ROM will not boot and that can cause SIM and VoLTE issues, i did flash it on mine and now VoLTE doesn't work on my phone, you can only boot it in case you want to flash an custom ROM, flash it then reboot into recovery to install GApps on the Custom Recovery that the ROM does install, but since all of the ROMs are arm64, i don't recommend it since you will have constant app restarting when changing from one app to another app
chuy19312 said:
Sadly, you can't flash TWRP on stock ROM, in case you did sucessfully, ROM will not boot and that can cause SIM and VoLTE issues, i did flash it on mine and now VoLTE doesn't work on my phone, you can only boot it in case you want to flash an custom ROM, flash it then reboot into recovery to install GApps on the Custom Recovery that the ROM does install, but since all of the ROMs are arm64, i don't recommend it since you will have constant app restarting when changing from one app to another app
Click to expand...
Click to collapse
Thanks for replying...
I've seen so-called tutorials on Youtube where someone actually succeeded in installing TWRP on his Moto G7 play (but did not mention which Android version was on the phone), and the TWRP developers too claim that their version for Moto G7 play would work, it even got an official update for Android 10 (alas they never reply to direct e-mails, those snooty guys)... some on XDA even said the flashing of a 'dirty port' worked for them. Were they all mistaken? Or did it work on Android 9? Are all XDA threads and internet posts / Youtube videos misleading / lying?
Are you REALLY sure that there is no way to install TWRP on a Moto G7 play (to be able to create a working backup of the encrypted data partition)? A 'full restorable backup of everything' is what I need...
I'm not sure about Android 10 Stock Rom, but it seems to be a 32bit system on a 64bit Kernel?
Alonso_Quixana said:
I'm not sure about Android 10 Stock Rom, but it seems to be a 32bit system on a 64bit Kernel?
Click to expand...
Click to collapse
It's a 32bit system on a 64bit CPU (Snapdragon 632). That's not unusual for Motorola devices. Open a terminal app and execute uname -a.
Alonso_Quixana said:
Thanks for replying...
I've seen so-called tutorials on Youtube where someone actually succeeded in installing TWRP on his Moto G7 play (but did not mention which Android version was on the phone), and the TWRP developers too claim that their version for Moto G7 play would work, it even got an official update for Android 10 (alas they never reply to direct e-mails, those snooty guys)... some on XDA even said the flashing of a 'dirty port' worked for them. Were they all mistaken? Or did it work on Android 9? Are all XDA threads and internet posts / Youtube videos misleading / lying?
Are you REALLY sure that there is no way to install TWRP on a Moto G7 play (to be able to create a working backup of the encrypted data partition)? A 'full restorable backup of everything' is what I need...
I'm not sure about Android 10 Stock Rom, but it seems to be a 32bit system on a 64bit Kernel?
Click to expand...
Click to collapse
I think it only works on certain Moto G7 Play variations or even only on Android 9, also, another way to install TWRP is installing an Custom ROM then flashing an flashable zip of TWRP_11 by SyberHexen on Custom ROM's Recovery
Link to TWRP_11 Flashable Zip
channel-twrp-installer-3.6.2_11.0_RC-1.0.zip | by SyberHexen for Moto G7 Play
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
In my case, flashing TWRP, even by following some tutorials made my MetroPCS Moto G7 Play to stop booting and also, VoLTE stopped working, fortunately, i had an EFS backup to restore my IMEI
Android 10 Stock Rom is an Arm (32 bits) ROM, every Custom ROM i tested are Arm64, but i don't recommend any of them since you will get constant app rebooting and notification problems since this is an 2 GB RAM device
I successfully unlocked my bootloader, then I tried flashing the twrp by following munchy's tutorial from YouTube (as someone recommended here). I also used the twrp recovery file he provided in the description, by using the latest platform tools from the official website. It was going pretty good. I even got the TeamWin logo, and also loaded up the twrp interface, and was able to navigate through it. But the problem was my internal storage wasn't showing up. So I booted back to my system normally to see If I can find a solution. Then I think I tried again after restarting to see if it fixes itself, but the same problem was persisting. The next time when I tried again, I used the latest twrp version which I downloaded from the official twrp website.
But since my 3rd attempt, I am not able to see any TeamWin recovery come up on my phone, when I connect I do the "fastboot boot (twrp filename)" command in cmd. When I do the command, nothing shows up. The device remains in the Fastboot mode, or just turns off. When I switch it back on, It turns on normally and boots into the phone without any issues, and I can use it. I've tried switching back to the original twrp version munchy used in the above linked video, but same result.
What did I do wrong here? How do I make my phone get into the twrp recovery when I enter the fastboot boot (twrp filename) command thru my PC? How do I make my Internal Storage available to view int he TWRP recovery so I can install it from my Downloads folder? I am on MIUI 14.0.4 If that helps. My end goal is to install Magisk.
Any tips/guides/suggestions are appreciated.
Installing TWRP and root does not erase your data.
Remove security from the lock screen. (decryption).Normally the latest TWRP decrypts the data.
Install Platform tools ,put the TWRP in the folder and run the commands from the folder.
TWRP SKK, Use A12 if your system is in A12/A13 if system A13.
Rename it to twrp.img
CMD
fastboot boot twrp.img
Powershell
./fastboot boot twrp.img
Once booted, go to Advanced -> Press "Flash current TWRP"
If offered, both slots.
NOSS8 said:
Installing TWRP and root does not erase your data.
Remove security from the lock screen. (decryption).Normally the latest TWRP decrypts the data.
Install Platform tools ,put the TWRP in the folder and run the commands from the folder.
TWRP SKK, Use A12 if your system is in A12/A13 if system A13.
Rename it to twrp.img
CMD
fastboot boot twrp.img
Powershell
./fastboot boot twrp.img
Once booted, go to Advanced -> Press "Flash current TWRP"
If offered, both slots.
Click to expand...
Click to collapse
Thank you. I had put backed the screen lock after the first 2 attempts because someone said to to that on a YT video after they faced the same problem. Now I tried again by removing the screen lock and the latest twrp for my device also boots up just fine. Now the problem Is I still can't access my internal storage .
Still having removed the screen security?
Which rom(fullname)?
Which TWRP?
Try to mount storage.
NOSS8 said:
Still having removed the screen security?
Which rom(fullname)?
Which TWRP?
Click to expand...
Click to collapse
Yes, I removed the screen security, though I can enter TWRP, I can't read the internal storage. MIUI 14.0.4.
I just watched a YT video where the dude does the following:
-TWRP Recovery
- Wipe
- Format Data
- Types 'yes'
then
-TWRP Recovery
- Reboot
- Recovery
- Do not Install
After coming back to recovery after rebooting, he gets a pop up, which at the swipe says "Swipe to allow for modifications" which he swipes, then now after checking the Internal Storage, It's readable now. Is this a possible solution?
Twrp A13, obviously if you don't want to keep the data.
Twrp/wipe format data type yes/reboot TWRP.
If error red lines, reboot TWRP and repeat the operation.
Sideload roms or use OTG.
NOSS8 said:
Twrp A13, obviously if you don't want to keep the data.
Twrp/wipe format data type yes/reboot TWRP.
If error red lines, reboot TWRP and repeat the operation.
Sideload roms or use OTG.
Click to expand...
Click to collapse
what's twrp A13? Also, I just unlocked my bootloader a few hours ago, so my phone has already done a factory reset and i don't have anything to lose except the Magisk APK and .img file in my phone.
But I have a question, will doing the format data just do a factory reset, or will I lose my ROM? Because I'm not trying to install a custom ROM, I just want to Install Magisk as the end goal with my current ROM.
MIUI 14 Android 13 so use this TWRP
plugged the phone into the PC when it is on the TWRP, you will have access to the internal storage. (works on my 12 pro aves twrp A13 Skk).
twrp-3.7.0_12-v7.5_A13-alioth-skkk.img
I'm using the latest one I could find on the TWRP website for my device. Not aware If it supports Android 13 though as it isn't mentioned on the website. Just asking my prev question, will doing the format data from TWRP just do a factory reset, or do I lose the ROM and will have to install a custom ROM?
second question I forgot to ask in my prev post, after i do the format data and put the Magisk APK and twrp img file again on my device, will my device stay decrypted as I formatted the data, or will the problem persist?
sorry If i sound dumb
zoinksy said:
I'm using the latest one I could find on the TWRP website for my device. Not aware If it supports Android 13 though as it isn't mentioned on the website. Just asking my prev question, will doing the format data from TWRP just do a factory reset, or do I lose the ROM and will have to install a custom ROM?
second question I forgot to ask in my prev post, after i do the format data and put the Magisk APK and twrp img file again on my device, will my device stay decrypted as I formatted the data, or will the problem persist?
sorry If i sound dumb
Click to expand...
Click to collapse
Use this TWRP(officiel).
twrp-3.7.0_12-v7.5_A13-alioth-skkk.img
thank you, this is the one I was looking for. Sorry to bother you again, now I installed the Magisk V26.1 apk from TWRP. And when I boot back to system and try opening the magisk manager, this happens. It says downloading, forever. I think I shouldn't have directly downloaded the latest version. So probably have to downgrade it a bit. For that, what will I have to do?
Can I just hold the Magisk icon, and uninstall it simply like any other app? Or do I have to do it from the TWRP? Also, Is it necessary for me to uninstall it before downgrading, or can I just download the apk of older magisk version and flash it from twrp just like I did previously?
It was on my first post.
Installation
The Magic Mask for Android
topjohnwu.github.io
TWRP + Root
Hi all. Hope you are good and safe from Covid-19. If you like TWRP as your recovery and want to keep root access as well, I am going to show you how to do that. Because if you take the stock boot.img and patch it via magisk, you will lose TWRP...
forum.xda-developers.com
Try OrangeFox. I never had problems with it. Been using it for half a year and constantly flash new ROM builds as a tester
Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40 (alioth) build releases | OrangeFox Recovery Downloads
Orangefox recovery for Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40 (alioth)
orangefox.download
cyanGalaxy said:
Try OrangeFox. I never had problems with it. Been using it for half a year and constantly flash new ROM builds as a tester
Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40 (alioth) build releases | OrangeFox Recovery Downloads
Orangefox recovery for Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40 (alioth)
orangefox.download
Click to expand...
Click to collapse
Sure, but currently only in A12.
NOSS8 said:
Sure, but currently only in A12.
Click to expand...
Click to collapse
I use ArrowOS 13
cyanGalaxy said:
I use ArrowOS 13
Click to expand...
Click to collapse
I don't doubt it, the Twrp A12 also works for certain operations on an A13 system but for certain Miui roms some bootloop.
NOSS8 said:
I don't doubt it, the Twrp A12 also works for certain operations on an A13 system but for certain Miui roms some bootloop.
Click to expand...
Click to collapse
Hm ok.
Welp for me on AOSP, it works nicely. I flash a new build (or two) every week. Backup/Restore works as should. UI is nice and modern, imo better than TWRP. That's why I'm recommending it.
Haven't heard anyone saying that they can't view Phone storage on OrangeFox.
Hi,
@NOSS8 , I'd like to ask : I've only some hours to wait to unlock the BL. But one question, as it's yet the stock rom (FW V13.0.11.0, A12), wich twrp should I use ? I want to install a A13 rom (that supposes FW V 14.xxx !)
So :
- fastboot boot twrp (but wich one ?? A12 or 13 ?? ; skkk ? Or ?) (+ "flash current twrp" OR "install it in ramdisk"?)
- reboot recovery
- flash FW V14.xxx
- flash rom
- format data
- reboot system
- flash magisk (last version ? Seems to be 'big' changes ?)
- flash what I need (V4A, DFE (??), ....)
What do you think ?
Thanks a lot ! Main question is about what version of twrp.. Help will be very appreciated !
néonaloj said:
Hi,
@NOSS8 , I'd like to ask : I've only some hours to wait to unlock the BL. But one question, as it's yet the stock rom (FW V13.0.11.0, A12), wich twrp should I use ? I want to install a A13 rom (that supposes FW V 14.xxx !)
So :
- fastboot boot twrp (but wich one ?? A12 or 13 ?? ; skkk ? Or ?) (+ "flash current twrp" OR "install it in ramdisk"?)
- reboot recovery
- flash FW V14.xxx
- flash rom
- format data
- reboot system
- flash magisk (last version ? Seems to be 'big' changes ?)
- flash what I need (V4A, DFE (??), ....)
What do you think ?
Thanks a lot ! Main question is about what version of twrp.. Help will be very appreciated !
Click to expand...
Click to collapse
Instead, use Miflash with a Fastboot rom, you can extract the boot img for root.(don't re lock the bootloader).
You can root without TWRP, but according to this thread, if you root you lose the TWRP and vice versa, I don't know if this is still relevant.(I don't have this device).
If you need ,install the TWRP A13 after flashing the A13.
See this thread for instructions
[Recovery] [13] [12] TWRP & OrangeFox
Since recoveries play a crucial role in flashing firmwares, custom ROMs and offline updates, it is of importance to have access to them. This post is about sources and instructions to working versions of recoveries for Alioth. Platform Tools (aka...
forum.xda-developers.com
***Note:
Use the TWRP SKKK.
Advantage with Miflash, the Fastboot roms contain all the imgs.
EDIT:
omitted link
TWRP + Root
Hi all. Hope you are good and safe from Covid-19. If you like TWRP as your recovery and want to keep root access as well, I am going to show you how to do that. Because if you take the stock boot.img and patch it via magisk, you will lose TWRP...
forum.xda-developers.com
NOSS8 said:
Instead, use Miflash with a Fastboot rom, you can extract the boot img for root.(don't re lock the bootloader).
You can root without TWRP, but according to this thread, if you root you lose the TWRP and vice versa, I don't know if this is still relevant.(I don't have this device).
If you need install the TWRP A13 after flashing the A13.
See this thread for instructions
[Recovery] [13] [12] TWRP & OrangeFox
Since recoveries play a crucial role in flashing firmwares, custom ROMs and offline updates, it is of importance to have access to them. This post is about sources and instructions to working versions of recoveries for Alioth. Platform Tools (aka...
forum.xda-developers.com
***Note:
Use the TWRP SKKK.
Advantage with Miflash, the Fastboot roms contain all the imgs.
Click to expand...
Click to collapse
I'm very greatfull for your quick reply ! Thanks
The device is too a Poco f3, sorry.. This doesn't need to flash magisk for twrp to stick (I had another one I've broken)
But I don't understand what's the advantage to first flash a fastboot rom..? As you say to flash twrp would loose root and vice versa... (I've read the thread you're talking about ofox)
So I wanted to go trough +- the way I mentionned, as A13 as well as ofox 'seems' to work (but I'm carefull with that twrp on stock MIUI A12, and I never used ofox..)
So you do think it's a bad idea ?? The rom I want to flash is crdroid.
I'm more lost now ...
Thanks again !