Hi people I recently flashed a o s IP Pizza ROM 9.0 on my mimix 2s, I have magisk 18.0 installed systemless.. using mipa kernel. The ROM is running smooth and fast no problems whatsoever when I try to back it up via TW RP and it failed lack of some folder starting with a p q. Before I try to flash magisk last time I used the unverify .zip b4 flashing magisk and it's soft bricked my phone for a while. And sometimes when I go into recovery it will show the files names is all letters and numbers is there something I'm doing wrong thanks in advance!
dirtyrott3njb said:
Hi people I recently flashed a o s IP Pizza ROM 9.0 on my mimix 2s, I have magisk 18.0 installed systemless.. using mipa kernel. The ROM is running smooth and fast no problems whatsoever when I try to back it up via TW RP and it failed lack of some folder starting with a p q. Before I try to flash magisk last time I used the unverify .zip b4 flashing magisk and it's soft bricked my phone for a while. And sometimes when I go into recovery it will show the files names is all letters and numbers is there something I'm doing wrong thanks in advance!
Click to expand...
Click to collapse
The thing with the filenames is because of the encryption, you have to enter your password to view the files
Related
I'm pretty sure i couldn't be the only one who recently updated from 16.0 to 17.0 (Stable Channel). I first updated the magisk manager and it prompted me to flash 16.0(1600) instead of a 17.0 version. Well since i flashed the 16.0(1600) version it prompted me to download, i got into a nasty bootloop and thankfully recovered with me having the stock ROM in my storage. I'm wondering if anyone else went through the bootloop i did this morning and if people should just flash the newer zips outside of the manager
HighOnLinux said:
I'm pretty sure i couldn't be the only one who recently updated from 16.0 to 17.0 (Stable Channel). I first updated the magisk manager and it prompted me to flash 16.0(1600) instead of a 17.0 version. Well since i flashed the 16.0(1600) version it prompted me to download, i got into a nasty bootloop and thankfully recovered with me having the stock ROM in my storage. I'm wondering if anyone else went through the bootloop i did this morning and if people should just flash the newer zips outside of the manager
Click to expand...
Click to collapse
I also got a bootloop but I flashed 17.0 through twrp. I had to go through the qualcomm drivers process to unbrick it because it was hard bricked lol
Flashed uninstall magisk and than magisk 17 and all worked well.
dracoboss said:
I also got a bootloop but I flashed 17.0 through twrp. I had to go through the qualcomm drivers process to unbrick it because it was hard bricked lol
Click to expand...
Click to collapse
That's horrible to have a hard bricked device. There's a hotfix that just got released right at this moment (17.1) so i'd recommend you to download that and continue the process to try getting root access back
Got the same problems as described here. Then I downloaded the latest Magisk uninstaller and Magisk 17 from the Magisk thread. The next step was to flash the uninstaller and afterwards Magisk 17 and the device booted well.
Running 17.1 and still getting the same thing with safety net check as before
The response is invalid
HighOnLinux said:
That's horrible to have a hard bricked device. There's a hotfix that just got released right at this moment (17.1) so i'd recommend you to download that and continue the process to try getting root access back
Click to expand...
Click to collapse
Yeah that's what I did and everything is fine... For now lol. Thanks
From Magisk 17.0 to Magisk 17.1, install it automatically. SafetyNet test successful
it's better and more secure deinstall first magisk manager clearing cache and data, install magisk 17.1 from twrp and if magisk manager doesnt be installed, install the apk
Good afternoon XDA.
I'm trying to get Magisk installed on my phone, but I'm really struggling.
Any hints/tips? I've followed instructions to every forum post and every Youtube video I've tried.
AFAIK, I have managed to install TWRP without issue, although after I've rebooted my phone into recovery, it encrypts the data folder, meaning if I patch any zips in TWRP, I have to first format the data to EXT2 and back to EXT4 for me to be able to mount the folder, which I think is where my problems lie.
After this, TWRP seems to look like it's installed the Magisk.zip without any issues, but when I install the magisk apk once I've booted back into Android, it says it is not installed, and is asking me to either download the zip again, or find a boot image to patch.
The ROM I have installed is also custom as far as I'm aware, as the kernel says "[email protected] #2'
Android version: 8.0.0 (I don't mind using an older ROM, like 7 if it means I can get Magisk working.
Build: 41.3.A.2.157
Thanks
Try this, download flash tool, use Xperiafirm to ? get the latest firmware for your region which is currently 171, check all the wipes, flash, then look down a few post to YasaHamed thread, follow his instructions and make use you use the correct kernel..
madladfromhalifax said:
I'm trying to get Magisk installed on my phone, ...
Click to expand...
Click to collapse
I had no problems with a patched stock kernel as described in my [Guide].
Updates of kernels and Magisk, whatever ...
I used latest TWRP, several versions
The encryption only forces you to wipe data if you set up a patched kernel the first time.
I will see how this works with a XZ1 (no TA-backup) since my XZ got stolen last week.
use AdrianDC's twrp, not the twrp official one
madladfromhalifax said:
Good afternoon XDA.
I'm trying to get Magisk installed on my phone, but I'm really struggling.
Any hints/tips? I've followed instructions to every forum post and every Youtube video I've tried.
AFAIK, I have managed to install TWRP without issue, although after I've rebooted my phone into recovery, it encrypts the data folder, meaning if I patch any zips in TWRP, I have to first format the data to EXT2 and back to EXT4 for me to be able to mount the folder, which I think is where my problems lie.
After this, TWRP seems to look like it's installed the Magisk.zip without any issues, but when I install the magisk apk once I've booted back into Android, it says it is not installed, and is asking me to either download the zip again, or find a boot image to patch.
The ROM I have installed is also custom as far as I'm aware, as the kernel says "[email protected] #2'
Android version: 8.0.0 (I don't mind using an older ROM, like 7 if it means I can get Magisk working.
Build: 41.3.A.2.157
Thanks
Click to expand...
Click to collapse
simplyfied!!!! https://forum.xda-developers.com/xperia-xz/how-to/rooted-kernels-f8332-41-3-2-588-0-t3748987
Hello everyone,
I just received my OP6 coming from the OPO and while I have been flashing LOS (sultans), magisk, twrp and co since my S1+, recent years obviously changed a lot.
So before bricking stuff or getting into bootloops, I briefly want to confirm if I miss something or got the order wrong:
update the stock OOS to the latest version
unlock bootloader
flash twrp
flash magisk
get root access to backup modemst1 & 2
decide if I wanna to with OOS, OOS open beta or LOS (didnt check yet if it is available with PIE)
flash ROM & magisk
flash gcam?! (worth it?)
figure out how to enable VoLTE & VoWIFI
check if I can get my banking ups running with the backups from Titanium (I guess the architecture will case me problems here)
Anything else e.g. in regards to tremble that I should know about? Is a backup of the stock image worth it? (guess I can download one from here anyway)
balleny said:
Hello everyone,
I just received my OP6 coming from the OPO and while I have been flashing LOS (sultans), magisk, twrp and co since my S1+, recent years obviously changed a lot.
So before bricking stuff or getting into bootloops, I briefly want to confirm if I miss something or got the order wrong:
update the stock OOS to the latest version
unlock bootloader
flash twrp
flash magisk
get root access to backup modemst1 & 2
decide if I wanna to with OOS, OOS open beta or LOS (didnt check yet if it is available with PIE)
flash ROM & magisk
flash gcam?! (worth it?)
figure out how to enable VoLTE & VoWIFI
check if I can get my banking ups running with the backups from Titanium (I guess the architecture will case me problems here)
Anything else e.g. in regards to tremble that I should know about? Is a backup of the stock image worth it? (guess I can download one from here anyway)
Click to expand...
Click to collapse
1. Settings, system, systemupdate
2. Read the big guide
3. Same as above
4. Same as 2
5. Same as above
6. Omni is good, havoc is good... All depends on your usage, you have to try the roms and decide for yourself.
7. After each rom flash you must flash twrp, then reboot to twrp then gapps then magisk if you want to use custom roms. (A/B partitions, read that info in guide section)
8. You don't flash, you install an apk. Many people like it. Up to you if you will like it. Try, just an apk.
9. For me, they worked from first boot.
10. Probably not, Google has made improvements in security and that's why titanium stopped working on bank aps etc.
This is for if you have Magisk 18.1 installed with manager version 7.1.1. Upgrading to manager 7.1.2 and then directly installing 19.1 caused my I3223 to go into a boot loop.
Image patching seems to have changed as well. With manager 7.1.1 we were able to directly patch the boot_X_FLASH_ALL-*.sin file. I had to extract boot.000 from the sin file before the new manager would patch it. Even so, the result is still a boot loop.
Reflashing older patched boot images did not restore root. In short, hold off on upgrading Magisk. If you have a solution please share. Thanks.
I was able to flash the older (v18.1) magisk patched boot image using fastboot. I will attach the image here if you need too. I had to split the RAR file into 3 parts due to limitation of XDA of RAR files to be 8MB.
Root is working fine, I was able to grant access to Titanium Backup. But seriously that was messed up. If that happened to my Shield TV and I lost all of my games I will be furious. Luckily, I tried that on the Shield TV before knowing it will mess up my Xperia 10 plus phone. What is more messed up is there is no way from Magisk Manager to keep using older APK or download older version of Magisk, I tried Custom URL in the settings to check the update from, but all I got was a spinning wheel while checking for updates.
Currently running Magisk Manager 7.1.2 and v18.1 , just ignoring the ZIP update.
Rule of thumb, if it aint broken, don't fix / update.
Thank you Rebel_X. I will try again tonight. I was hoping to retain userdata but that's probably what's giving me problems with the revert.
Has anyone tried 19.1 patched boot image on a fully reset phone? Do we know if that works?
Rebel_X said:
I was able to flash the older (v18.1) magisk patched boot image using fastboot. I will attach the image here if you need too. I had to split the RAR file into 3 parts due to limitation of XDA of RAR files to be 8MB.
Root is working fine, I was able to grant access to Titanium Backup. But seriously that was messed up. If that happened to my Shield TV and I lost all of my games I will be furious. Luckily, I tried that on the Shield TV before knowing it will mess up my Xperia 10 plus phone. What is more messed up is there is no way from Magisk Manager to keep using older APK or download older version of Magisk, I tried Custom URL in the settings to check the update from, but all I got was a spinning wheel while checking for updates.
Currently running Magisk Manager 7.1.2 and v18.1 , just ignoring the ZIP update.
Rule of thumb, if it aint broken, don't fix / update.
Click to expand...
Click to collapse
Hay, what model is your Xperia 10 plus?
My phone is I4293, i used your boot.img, when reboot, nothing is changed, just not rooted.
yishisanren said:
Hay, what model is your Xperia 10 plus?
My phone is I4293, i used your boot.img, when reboot, nothing is changed, just not rooted.
Click to expand...
Click to collapse
Mine is I3223. I don't know if it is compatible with your model, but if it flashed fine and the phone booted, try to install magisk manager apk v7.1.1 and see if you are rooted.
Rebel_X said:
Mine is I3223. I don't know if it is compatible with your model, but if it flashed fine and the phone booted, try to install magisk manager apk v7.1.1 and see if you are rooted.
Click to expand...
Click to collapse
It flashed fine, also my phone can be booted, but not rooted.
:crying::crying::crying:
Have you guys tried to summit a bug report on magisk's github issue page?
https://github.com/topjohnwu/Magisk/issues/1537
The bugreport about magisk bootloops on xperia devices
I have the GM1910 version of the OnePlus 7 Pro
Ok so I had a stock OOS 10.3 on the 7 Pro I just bought used, went home and was super excited to get a custom rom installed. From my previous experience back in the day, I knew to USB Debug, OEM unlock, Advanced Reboot for convenience and followed the Havoc Custom ROm guide that said to:
1. Download the ROM, TWRP Installer, GApps, Magisk.
2. Wipe Data, Dalvik.
3. Flash the ROM, TWRP Installer (Use Unofficial Q compatible version, starting at 3.3.1.575).
4. Reboot to Recovery.
5. Flash the ROM, TWRP Installer again.
6. Reboot to Recovery.
7. Flash GApps (Optional), Magisk (Optiona).
8. Reboot and Enjoy.
Never Wipe System or Vendor partition.
After doing so, I first ran into an issue with Fastboot Mode being indefinitely stuck, but fixed that with a TWRP 3.3.1-75 version I downloaded, and was able to boot TWRP. After that, and following the guide above, I noticed it was stuck on the Havoc boot animation. I waited a good 20 minutes before realizing its likely never going to boot. I rebooted twice after that, waiting 10 more minutes each for a total of about an hour, thinking "Hey maybe it takes time". Nothing. I then tried flashing NikGapps for Android Q compatibility as latest Gapps on the OpenGapps website allows up to Android 9. I realized afterward that it was a n00b mistake so I downloaded and flashed the Beta Android 10 Beta Pico OpenGapps and Magisk Canary that also failed.
After that, I started searching around for finding a way to return to stock Android 9 to start over, thinking Android 9 had more stable support, so I downloaded and fastboot flashed the Android 9.5..11 GM21AA - Direct Download, but while showing the OnePlus stock boot animation, it freezes and then the device turns off entirely.
I'm currently waiting for the 9.5.13 Repack (taken from the Collection of Unbrick Tools thread) to finish downloading to see if I can use MSM tool to restore stock Android 9 and kind of start over. I would prefer to root / custom rom Android 9. I have no clue what I'm doing now, but honestly recall it being so easy back in the day before this A/B partition stuff and I would have considered myself to be not so much a n00b, but at least quite "experienced" but I guess thats completely irrelevant now hey!. Can someone please guide me on how I can fix this and get a custom rom booting? Thank you very much!
Update: I managed to restore to Android 10 using the Decrypted Oxygen OS 10.3 ZIP from the "Collections of brick tools" linked above, then rooted that stock OOS using the standard guide. I got Havoc Android 9 working prior but ran into tons of bugs so I just decided to stick to stock for now.
imatts said:
Update: I managed to restore to Android 10 using the Decrypted Oxygen OS 10.3 ZIP from the "Collections of brick tools" linked above, then rooted that stock OOS using the standard guide. I got Havoc Android 9 working prior but ran into tons of bugs so I just decided to stick to stock for now.
Click to expand...
Click to collapse
Unless there is something specific you need with a custom ROM, I'd stay stock and root.
I have EdXposed installed and can tweak most things.
I really need ad blocking and some basic customization.
I don't need a full ROM to get what I want.
tech_head said:
Unless there is something specific you need with a custom ROM, I'd stay stock and root.
I have EdXposed installed and can tweak most things.
I really need ad blocking and some basic customization.
I don't need a full ROM to get what I want.
Click to expand...
Click to collapse
I would have agreed with you yesterday, but I've used the phone for a few days and cannot stand the insanely rounded corners so I tried finding a work around. So far reducing screen height and getting rid of Oxygen OS's software rounded corners is the way to go but stock OOS doesnt give you the option, I'm hoping a custom rom will. Currently in the midst of flashing RR Android 9
Which boot slot are you trying to flash the rom on and have you tried flashing other roms? I know I've tried flashing havoc a few times and no go. I'm using blissrom right now and it works great until I get the rom I'm building and configuring and have data and messaging working lol