Related
Just flash the zip in the attachment, and then flash SuperSU. No more messing with Terminal Emulator!
Note: if you installed SuperSU first, and got a bootloop, install the fixer then SuperSU again. All will be good.
Please don't redistribute this, just link to the thread.
Thanks. Phone wouldn't boot after SuperSU install. This worked perfectly.
Note: if you installed SuperSU first, and got a bootloop, install the fixer then supersu again. All will be good.
mx597turbo said:
Thanks. Phone wouldn't boot after SuperSU install. This worked perfectly.
Note: if you installed SuperSU first, and got a bootloop, install the fixer then supersu again. All will be good.
Click to expand...
Click to collapse
I'll add your note to the op
Life saver
Yay! I was in that bootloop, and then I couldn't find an ADB driver that worked, to load this fix. The obvious solution was to put the fix on a Micro-SD card but it didn't come to me for a bit - my other current phone has no external card slot - but once I did this, the fix worked perfectly. Many thanks to whomever came up with this!!!
No need to flash SuperSu for root, phh's SuperUser works perfect
Can I ask what this script exactly does?
Is this only for flashing SuperSU on to stock? or is this something I need to use every time I flash SuperSU on any rom, even on lineageOS?
I just am confused what this script does and when exactly I would need to use it. Thanks!
BigNaes said:
Can I ask what this script exactly does?
Is this only for flashing SuperSU on to stock? or is this something I need to use every time I flash SuperSU on any rom, even on lineageOS?
I just am confused what this script does and when exactly I would need to use it. Thanks!
Click to expand...
Click to collapse
This is for roms on stock and also roms that do not support native root. If you flash LineageOS, all you have to do is flash their SU package in their Extras section on the website. Some of the roms in the development section have native root built in under development settings, and some do not.
fireball0093 said:
This is for roms on stock and also roms that do not support native root. If you flash LineageOS, all you have to do is flash their SU package in their Extras section on the website. Some of the roms in the development section have native root built in under development settings, and some do not.
Click to expand...
Click to collapse
Thank you for your reply. I understand. I prefer to use SuperSu as opposed to the LineageOS SU package.
When I installed LineageOS I flashed this zip first and then SuperSU after and it works perfectly, I am just not sure if I needed this zip first when using Lineage OS.
Also one last question is I believe I found a post which explains what this fix does, can anyone confirm this is the fix being performed? https://forum.xda-developers.com/moto-g4/how-to/how-to-root-g4-fix-bootable-attempted-t3417592
Thanks again for all the help, always learning on XDA :good:
If anybody wants the manual method, type this is Terminal in TWRP Recovery:
echo SYSTEMLESS=true>>/data/.supersu
Ashutosh Sundresh said:
If anybody wants the manual method, type this is Terminal in TWRP Recovery:
echo SYSTEMLESS=true>>/data/.supersu
Click to expand...
Click to collapse
What's that for??
Sanjay parsi said:
What's that for??
Click to expand...
Click to collapse
SuperSU, if you don't type this, your device WILL bootloop
download link isn't working for me.
Edit: everything is fine my brain is the one not working
Hi everyone. These packs are for A2017 and A2017G for now. A2017U will be added soon.
Full stock ROM. You can make your phone fully original.
You can unbrick your device with this ROM.
You are responsible for everything.
Your data will be erased. Backup all your stuffs.
Backed up by @asderdd from forum.turkdevs.com
Download:
MiFlash 20160401.exe [url]https://drive.google.com/file/d/0B065LdNGqJLGM2xfSkZMbVYwc3M/view[/URL]
ADB Installer 1.4.3.exe [url]https://drive.google.com/open?id=0B065LdNGqJLGWUtFczMyTUdTTTQ[/URL]
A2017 (Chinese Version)
ZTE_A2017V2.0.0B13_FULL_EDL_PACKAGE_BY_TURKDEVS
https://www.androidfilehost.com/?fid=889764386195932870
ZTE_A2017V2.0.0B08_FULL_EDL_PACKAGE (Android 7.1.1 - MiFavor UI 5.0) [url]https://drive.google.com/open?id=0B065LdNGqJLGaUpXRV9WRVNkUEk[/URL]
A2017G (Global European Version)
ZTE_A2017GV1.2.0B06_FULL_EDL_PACKAGE_BY_TURKDEVS.7z [url]https://www.androidfilehost.com/?fid=745425885120758978[/URL]
ZTE_ZTE A2017GV1.2.0B09_FULL_EDL_PACKAGE_BY_TURKDEVS.zip
https://androidfilehost.com/?fid=962021903579497293
A2017U (US Version)
https://www.androidfilehost.com/?fid=673368273298988889
Instructions:
- Install MiFlash. Driver will be installed automatically.
- Install ADB
- Enable USB Debugging.
- Reboot edl.
- Make sure you see to device as "Qualcomm HS-USB QDLoader 9008"
- Open MiFlash. Browse and choose folder you've downloaded.
- Click Refresh. You should see your device on list.
- Flash and wait until installation is done.
- You can turn on your device.
To install a ROM to another model. (Ex: B08 Chinese ROM to U devices.)
1. Download Chinese ROM
2. Download latest bootstack zip for your device from @DrakenFX topic.
3. Move NHLOS.bin from bootstack to ROM folder.
4. Flash ROM as guide.
You can not get signal if you don't do these steps.
Thanks.
@asderdd
Source: [url]https://forum.turkdevs.com/konu/edl-unbrick-zte-axon-7-all-stock-roms.13629/[/URL]
Please hit the thanks button if I help you.
i put supersu 2.82 and when restarted, stopped in axon door
Just to be clear, Is this stock b08? I mean, it is not modified or pre-rooted? Thanks.
yes, its a stock rom
What does that mean, it is just a stock rom? Did you did any modifications to it? Why can't we flash through TWRP?
iker84 said:
yes, its a stock rom
Click to expand...
Click to collapse
Thanks.
Raffikie said:
What does that mean, it is just a stock rom? Did you did any modifications to it? Why can't we flash through TWRP?
Click to expand...
Click to collapse
It's not for twrp. The OP said to flash it in miflash.
i read in other forum, magisk and supersu, causes bootloop, i probe to install supersu and have bootloop
iker84 said:
i read in other forum, magisk and supersu, causes bootloop, i probe to install supersu and have bootloop
Click to expand...
Click to collapse
I'm using magisk 13.6 only on B08 and I don't have any problems. All passed on safetynet.
Magisksu is working fine + I can also hide root from any app I choose.
If it helps, this is how I installed magisk on my stock chinese unit.
1. Reboot to twrp.
2. Flash unSu to remove all traces of root.
3. Restore original boot.img
4. Flash magisk 13.6
5. Reboot
otaconremo said:
Just to be clear, Is this stock b08? I mean, it is not modified or pre-rooted? Thanks.
Click to expand...
Click to collapse
Fully stock. As first day when you buy the phone.
i dont have signal in my 2017g
iker84 said:
i dont have signal in my 2017g
Click to expand...
Click to collapse
Because this rom is for A2017. install a2017g bootstack from twrp or delete nhlos.bin from folder. Extract nhlos from 2017g bootstack and reinstall rom.
WesTD said:
Because this rom is for A2017. install a2017g bootstack from twrp or delete nhlos.bin from folder. Extract nhlos from 2017g bootstack and reinstall rom.
Click to expand...
Click to collapse
thanks!
otaconremo said:
I'm using magisk 13.6 only on B08 and I don't have any problems. All passed on safetynet.
Magisksu is working fine + I can also hide root from any app I choose.
If it helps, this is how I installed magisk on my stock chinese unit.
1. Reboot to twrp.
2. Flash unSu to remove all traces of root.
3. Restore original boot.img
4. Flash magisk 13.6
5. Reboot
Click to expand...
Click to collapse
not for me!
bootloop in axon window
WesTD said:
Hi everyone. This ROM is for A2017 for now. Other variants will be added soon.
Full stock ROM. You can make your phone fully original.
You can unbrick your device with this ROM.
You are responsible for everything.
Your data will be erased. Backup all your stuffs.
Backed up by @asderdd from forum.turkdevs.com
Download:
MiFlash 20160401.exe https://drive.google.com/file/d/0B065LdNGqJLGM2xfSkZMbVYwc3M/view
ADB Installer 1.4.3.exe https://drive.google.com/open?id=0B065LdNGqJLGWUtFczMyTUdTTTQ
ZTE_A2017V2.0.0B08_FULL_EDL_PACKAGE (Android 7.1.1 - MiFavor UI 5.0) https://drive.google.com/open?id=0B065LdNGqJLGaUpXRV9WRVNkUEk
Instructions:
- Install MiFlash. Driver will be installed automatically.
- Install ADB
- Enable USB Debugging.
- Reboot edl.
- Make sure you see to device as "Qualcomm HS-USB QDLoader 9008"
- Open MiFlash. Browse and choose folder you've downloaded.
- Click Refresh. You should see your device on list.
- Flash and wait until installation is done.
- You can turn on your device.
Thanks.
@asderdd
Source: https://forum.turkdevs.com/konu/edl-unbrick-zte-axon-7-all-stock-roms.13629/
Click to expand...
Click to collapse
Can we root post flashing ? Please let me know the procedure too.
I am getting 'cannot read hello packet' when trying to flash
Raffikie said:
I am getting 'cannot read hello packet' when trying to flash
Click to expand...
Click to collapse
Reboot edl on every try to flash. If you still can't install it try on another pc. I was getting same error, i did it on another PC
In B06 my LED isn't working. How about this ROM? Any issues?
Gesendet von meinem ZTE A2017G mit Tapatalk
otaconremo said:
I'm using magisk 13.6 only on B08 and I don't have any problems. All passed on safetynet.
Magisksu is working fine + I can also hide root from any app I choose.
If it helps, this is how I installed magisk on my stock chinese unit.
1. Reboot to twrp.
2. Flash unSu to remove all traces of root.
3. Restore original boot.img
4. Flash magisk 13.6
5. Reboot
Click to expand...
Click to collapse
How did you flash TWRP. Once on B08 it won't let me...
ultramag69 said:
How did you flash TWRP. Once on B08 it won't let me...
Click to expand...
Click to collapse
I used tenfar's tool which I had since MM. I don't know why but there are already two users who got bricked using tenfar's tool on b08 but mine is okay.
Also, i have mine BL unlocked since MM and OTA'd till b08.
If I install this via edl will it restore stock recovery. I have twrp with a locked bootloader and can't install otas. Want to go completely back to stock in order to continue to receive updates
Hi. Maybe some of you have these files but i'll share mod i use on custom roms and LOS 15.1.
I can add to OP more if you share on this topic
Original LOS 15.1 Thread by @OrdenKrieger https://forum.xda-developers.com/axon-7/development/unofficial-lineageos-15-1-zte-axon-7-t3800214
Google Camera for HDR+ and Portrait Mode on Front Camera
https://drive.google.com/open?id=1CZAoa_9HQDnrM-F1qIYDpczuHmZXrfZw
Use pico gapps to use GCam.
Change buttons back and recent. Thanks @kevte89
https://drive.google.com/open?id=1SjY1-uIZ0kTayJ0vouHP2LyaKWPHN_SV
Magisk 16.4 to Root.
https://github.com/topjohnwu/Magisk/releases/download/v16.4/Magisk-v16.4.zip
To Fix Daydream. Thanks to @LuccoJ
https://forum.xda-developers.com/showpost.php?p=76806563&postcount=303
Add the addonsu to root with Magisk (and remove addonsu) https://download.lineageos.org/extras
or
Just root within twrp 3.2.17 (@NFound) - tested by @DarkQuark
@WesTD why the need to use pico gapps? Can't you choose aroma and not install Google Camera or use gapps config to disable it being installed.
@raystef66 you need to install the addonsu, remove it and then install magisk? Why can't you just install magisk?
Dodgexander said:
@WesTD why the need to use pico gapps? Can't you choose aroma and not install Google Camera or use gapps config to disable it being installed.
@raystef66 you need to install the addonsu, remove it and then install magisk? Why can't you just install magisk?
Click to expand...
Click to collapse
You can install magisk when on 3217 as i heard without addonsu but this one runs 3216.
Just use the addonsu and then flash 16.4 and you'll be good to go.
EDIT : maybe 3.2.1.6 can root too without the addonsu but i never tested that. But like said no harm done to use the addonsu
Dodgexander said:
@WesTD why the need to use pico gapps? Can't you choose aroma and not install Google Camera or use gapps config to disable it being installed.
@raystef66 you need to install the addonsu, remove it and then install magisk? Why can't you just install magisk?
Click to expand...
Click to collapse
IDK why but camera has stopped if I install mini or higher
raystef66 said:
You can install magisk when on 3217 as i heard without addonsu but this one runs 3216.
Just use the addonsu and then flash 16.4 and you'll be good to go.
EDIT : maybe 3.2.1.6 can root too without the addonsu but i never tested that. But like said no harm done to use the addonsu
Click to expand...
Click to collapse
I'll have to try when I install it and report back here.
WesTD said:
IDK why but camera has stopped if I install mini or higher
Click to expand...
Click to collapse
Very strange when mini doesn't include camera. The only apps in mini that have anything to do with the camera are face detect and photos.
WesTD said:
Google Camera for HDR+ and Portrait Mode on Front Camera
https://drive.google.com/open?id=1CZAoa_9HQDnrM-F1qIYDpczuHmZXrfZw
Click to expand...
Click to collapse
Is HDR+ and Portrait Mode only working on the front camera?
Any news about the stock camera?
There have been flashable zips in the path if I'm not mistaken, none for oreo after all I know, right?
joaocandeias said:
Is HDR+ and Portrait Mode only working on the front camera?
Click to expand...
Click to collapse
Both rear and front
Just to update here with my findings.
1. Magisk 16.4 works fine installing straight, no reason to install addonsu.
2. Installed aroma gapps from open gapps and it works fine apart from bizarre occasional "Google has stopped " messages.
3. I can't comment on the Google camera shared here but the latest recommend pixel mod camera from here: https://www.celsoazevedo.com/files/android/google-camera/dev-arnova8G2/#apk285 works relatively well, crashed on me once trying slow motion but everything else seems to work. I did not come across the problem mentioned here where certain gapps break gcam.
This is all fresh install, unencrypted, A2017U using universal bootstack and U modem and Nfound TWRP .6.
Is there any reason you chose that exact version of Gcam @WesTD ?
I have been using the latest version arnovas mod and today it crashed quite often taking photos. It also didn't work well recording UHD video and lagged during one of my recordings.
WesTD said:
Hi. Maybe some of you have these files but i'll share mod i use on custom roms and LOS 15.1.
I can add to OP more if you share on this topic
Click to expand...
Click to collapse
You should add this magisk mod to fix issues with DayDream:
https://forum.xda-developers.com/showpost.php?p=76806563&postcount=303
Liquid5n0w said:
You should add this magisk mod to fix issues with DayDream:
https://forum.xda-developers.com/showpost.php?p=76806563&postcount=303
Click to expand...
Click to collapse
Thanks, added OP
Just a general, unimportant question. What's the deal with LOS-based ROMs and cLock? cLock displays weather with the aid of weather providers since Marshmallow I think.
On Oreo none of them seem to work. They install normally but the systems don't see them as providers. Not even Chronus which also acts as a provider.
Just wondering (out loud) why cLock is still included if it's not fully functional anymore.
ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HellsGate Kernel, Multiboot, Tapatalk 4.9.3
Whenever I install magisk the device can't boot in the OS. It just boots in fastboot mode every time and the only way to get it back is re-install the OS from recovery mode (TWRP). So far I have tested with version 16.0 and 16.4, and got the same results on both.
Any idea why this is happening?
laglink said:
Whenever I install magisk the device can't boot in the OS. It just boots in fastboot mode every time and the only way to get it back is re-install the OS from recovery mode (TWRP). So far I have tested with version 16.0 and 16.4, and got the same results on both.
Any idea why this is happening?
Click to expand...
Click to collapse
Yes, it's normal. It was mentionened in other threasds already, that this happens. 16.7 should work though, only hide does not work properly.
WesTD said:
Change buttons back and recent. Thanks @kevte89
https://drive.google.com/open?id=1SjY1-uIZ0kTayJ0vouHP2LyaKWPHN_SV
Click to expand...
Click to collapse
The "swap back and recent" doesn't seem to be working. I'm running the 09/25 build of Lineage 15.1. After a flash and reboot, the buttons work exactly as before.
I tried finding the source of that file, but the user you linked doesn't seem to have any posts here. Could you link the source thread?
orangeisnon said:
The "swap back and recent" doesn't seem to be working. I'm running the 09/25 build of Lineage 15.1. After a flash and reboot, the buttons work exactly as before.
I tried finding the source of that file, but the user you linked doesn't seem to have any posts here. Could you link the source thread?
Click to expand...
Click to collapse
Or try this, mount Vendor : https://androidfilehost.com/?fid=1322778262903999789
raystef66 said:
Or try this, mount Vendor : https://androidfilehost.com/?fid=1322778262903999789
Click to expand...
Click to collapse
I've been pulling my hair out for the last few days trying to get the back button on the right side. Unfortunately, this one didn't work for me either. Am I doing something wrong? I reboot into TWRP 3.2.1-8, go to mount, select vendor, go to install, select file, voila. Everything says it installs, no errors, etc, and then there's no change when I boot into system again.
orangeisnon said:
The "swap back and recent" doesn't seem to be working. I'm running the 09/25 build of Lineage 15.1. After a flash and reboot, the buttons work exactly as before.
I tried finding the source of that file, but the user you linked doesn't seem to have any posts here. Could you link the source thread?
Click to expand...
Click to collapse
bradyarz said:
I've been pulling my hair out for the last few days trying to get the back button on the right side. Unfortunately, this one didn't work for me either. Am I doing something wrong? I reboot into TWRP 3.2.1-8, go to mount, select vendor, go to install, select file, voila. Everything says it installs, no errors, etc, and then there's no change when I boot into system again.
Click to expand...
Click to collapse
It should work under /verdor
Or do it manualy in /vendor/usr/keylayout/synaptics_dsx.kl or search that file
Code:
key 158 APP_SWITCH
key 102 HOME
key 187 BACK
key 143 WAKEUP
I used it in LOS16 and all other Pie roms and working ok. Never tried it on LOS15
After a few failed attempts (using Audio Modification module etc.) I found a way to get Viper working on the Mi 9. installed on the rooted Xiaomi.eu rom via TWRP and Magisk.
1. Download the Viper4Android_FX-v3.4.2.zip via Magisk but don't install it via Magisk
2. Boot to TWRP and flash the Viper zip and then adhere to the following:
- Press a volume button when prompted to do so
- Volume down (to choose vol key installation method)
- Vol up (for new 2.5.0.5)
- Vol up (for material, if preferred)
- Vol up (for system app)
- Vol up (for lib workaround to be installed)
3. Reboot
4. Via Magisk find and install "Init.d injector" and then reboot
Viper4Android should now be processing your audio!
Rommco05 said:
Installation from Magisk doesn't work? Just curious
Click to expand...
Click to collapse
Not the usual way. On my Pixel 2 XL, either the magisk module would work out of the box or using the Audio Modification Library module would make it work. I tried both of these ways, with no success the driver just wouldn't install. Tried the XDA labs apk, along with the Audio Modification Library, didn't work. Was even waiting a few minutes after boot as I know sometimes/some roms it takes a few minutes to initialise.
After lots of playing around of different versions, I tried that additional installation step of the lib workaround, which states that init.d support is needed too. With the use of that extra init.d module, it works!
I spent some time doing this and figured I'd help out others when they come to do it too!
I managed to install via Magisk?? Maybe due to a Magisk update?
*justintime* said:
I managed to install via Magisk?? Maybe due to a Magisk update?
Click to expand...
Click to collapse
Ahh yeah that's fair enough! Probably flashing via TWRP isn't necessary, so long as the additional init module is there too
Rommco05 said:
Installed init and after Viper4 from Magsik and didn't work, need flash ot trough twrp, today...
Click to expand...
Click to collapse
Ah tgats handy to know! My initial istructions remain valid then
Rommco05 said:
Installed init and after Viper4 from Magsik and didn't work, need flash ot trough twrp, today...
Click to expand...
Click to collapse
Funny with twrp it wasn't working for me...... Magisk had an update. "Check updates canary build' in manager.
And it was a straight away. Flash.... Only no equalizer in usb/dock out though for Android auto
Rommco05 said:
btw after last Magisk update I was able install Viper4 over manager. I also installed that last option (fix)
Click to expand...
Click to collapse
Thanks, that's handy to know!
I simply couldn't get viper4android to work and didn't have much luck with the init.d injector... I ended up following your steps and installed a custom kernel and emulated init.d via the kernel auditor app.... Now its working perfectly!
Have any of you tried the ainur sauron mod on the mi 9?
hi is it possible to get viper4android work with magisk flash? because i don't want twrp and loosing encryption.
when i flash trough magisk viper4android app doesn't appear?
thank you
(sorry for bad english)
dffhgg said:
hi is it possible to get viper4android work with magisk flash? because i don't want twrp and loosing encryption.
when i flash trough magisk viper4android app doesn't appear?
thank you
(sorry for bad english)
Click to expand...
Click to collapse
Possibly...
Have you tried rebooting? Otherwise I'm unsure I'm afraid....
cd993 said:
Possibly...
Have you tried rebooting? Otherwise I'm unsure I'm afraid....
Click to expand...
Click to collapse
yes for sure i rebooted many times but no success..
always viper4android doesn't appear
i also tried install via apk download viper4android then install there also not work, after reboot it reask to install driver.
dffhgg said:
yes for sure i rebooted many times but no success..
always viper4android doesn't appear
i also tried install via apk download viper4android then install there also not work, after reboot it reask to install driver.
Click to expand...
Click to collapse
And this is with the init d module as well?
with init.d injector module from magisk? yes i installed it alredy
dffhgg said:
with init.d injector module from magisk? yes i installed it alredy
Click to expand...
Click to collapse
And you're on the latest eu rom?
Hmm all I can suggest is to remove fully uninstall viper, the init d module and make sure no other audio mods are installed, reboot, then install viper again (ensuring to choose yes to the lib workaround) and the init d module.
If that doesn't work, then unfortunately I'm out of ideas as I tried lots 9f things and this was the only method that worked for me.
Good luck
yes i'm on 10.2.17
i will give it a try and let you know.
hope will work thank you
dffhgg said:
yes i'm on 10.2.17
i will give it a try and let you know.
hope will work thank you
Click to expand...
Click to collapse
I'm on the latest weekly 9.4.11, if that makes any difference
can i flash this version whithout data loss?
i tried reinstall everything but no succes
hi guys my problem is solved!
what i did:
change selinux to permissive with this tool: Kernel SEPolicy patcher https://zackptg5.com/android.php
now viper4android is detect driver its full work!
dffhgg said:
hi guys my problem is solved!
what i did:
change selinux to permissive with this tool: Kernel SEPolicy patcher https://zackptg5.com/android.php
now viper4android is detect driver its full work!
Click to expand...
Click to collapse
Great! I'll save that just in case I ever need it
keep getting the following error
Checking for Digest files
Skipping Digest check: no digest file found
on twrp 3.3.0 b8 and latest EU rom
I'm currently running Android 11 based Wave OS on my Redmi Note 9 Pro (Curtana). I have OrangeFox recovery installed. I want to flash latest stock ROM which is also based on Android 11.
So, can anyone help me with the correct procedure for the flashing of Stock MIUI 12 based on Android 11 on my Curtana with OF recovery installed?
Azamsm said:
I'm currently running Android 11 based Wave OS on my Redmi Note 9 Pro (Curtana). I have OrangeFox recovery installed. I want to flash latest stock ROM which is also based on Android 11.
So, can anyone help me with the correct procedure for the flashing of Stock MIUI 12 based on Android 11 on my Curtana with OF recovery installed?
Click to expand...
Click to collapse
You can flash this directly from ofox. It's the current updated Android R stock firmware which is stable. Just format your data, flash the recovery rom (not the fastboot rom) and reboot.
But I highly recommend you to try EU rom from xiaomi.eu website.
MPK99 said:
You can flash this directly from ofox. It's the current updated Android R stock firmware which is stable. Just format your data, flash the recovery rom (not the fastboot rom) and reboot.
But I highly recommend you to try EU rom from xiaomi.eu website.
Click to expand...
Click to collapse
So, I can flash this one by the same method?
Azamsm said:
So, I can flash this one by the same method?
Click to expand...
Click to collapse
Ys. It's the eu one that I mentioned.
But note that eu roms are always little behind the latest versions.
Right now, eu rom is 12.0.1 & stock is 12.0.4.
But don't worry, differences are very minor. Go with EU.
MPK99 said:
Ys. It's the eu one that I mentioned.
But note that eu roms are always little behind the latest versions.
Right now, eu rom is 12.0.1 & stock is 12.0.4.
But don't worry, differences are very minor. Go with EU.
Click to expand...
Click to collapse
Hi @MPK99
I successfully flashed eu rom 12.0.1. Thanks for the guidance.
Can you also help me gaining root. I flashed Magisk 22.0 zip via OFox, it's successfully installed, root checker shows phone is rooted and even able to grant apps root access but it actually doesn't seem to be working. I can't modify system files and root apps don't do what they are supposed to do. Please help.
Thanks in advance!
Azamsm said:
Hi @MPK99
I successfully flashed eu rom 12.0.1. Thanks for the guidance.
Can you also help me gaining root. I flashed Magisk 22.0 zip via OFox, it's successfully installed, root checker shows phone is rooted and even able to grant apps root access but it actually doesn't seem to be working. I can't modify system files and root apps don't do what they are supposed to do. Please help.
Thanks in advance!
Click to expand...
Click to collapse
What method you used to root? Boot Patch or Recovery flash? Also check & tell whether device is encrypted or not.
MPK99 said:
What method you used to root? Boot Patch or Recovery flash? Also check & tell whether device is encrypted or not.
Click to expand...
Click to collapse
Recovery flash and device in not encrypted.
Can I have your telegram?
Azamsm said:
Recovery flash and device in not encrypted
Click to expand...
Click to collapse
Get latest Magisk (magisk-v22.0.zip), flash it as a module under Magisk app itself. Reboot.
MPK99 said:
Get latest Magisk (magisk-v22.0.zip), flash it as a module under Magisk app itself. Reboot.
Click to expand...
Click to collapse
Didn't work. Thanks for the help btw.
Azamsm said:
Didn't work. Thanks for the help btw.
Click to expand...
Click to collapse
There's no root problems btw. Try to enable root permissions for the explorer manually under magisk. Also check whether you allowed root under your explorer settings.
MPK99 said:
There's no root problems btw. Try to enable root permissions for the explorer manually under magisk. Also check whether you allowed root under your explorer settings.
Click to expand...
Click to collapse
I checked and it's enabled. But it's not working anyhow. Stock MIUI doesn't get rooted too. There's this wave OS rom which I could successfully root so far. But it had heating issue while charging. Maybe I should forget about rooting for a whilr
Azamsm said:
I checked and it's enabled. But it's not working anyhow. Stock MIUI doesn't get rooted too. There's this wave OS rom which I could successfully root so far. But it had heating issue while charging. Maybe I should forget about rooting for a whilr
Click to expand...
Click to collapse
Is root not working for just solid explorer or other root apps too? If root works on other apps, try Mixplorer instead of Solid.
MPK99 said:
Is root not working for just solid explorer or other root apps too? If root works on other apps, try Mixplorer instead of Solid.
Click to expand...
Click to collapse
Not working on any app.
While I retried flashing Magisk through OFox, I saw these lines
Code:
-System as root, keep dm/avb verity
- Encrypted data, keep force encryption
Is this the encryption you were talking about
Azamsm said:
While I retried flashing Magisk through OFox, I saw these lines
Code:
-System as root, keep dm/avb verity
- Encrypted data, keep force encryption
Is this the encryption you were talking about
Click to expand...
Click to collapse
Maybe. Because, Encryption & rooting together doesn't go well.
On Encryption, you have to follow boot patch method. Recovery flashing won't work.
Extract boot.img from your stock firmware (or EU rom firmware), patch that file from magisk patch method. You'll get patched_boot.img. Flash that as boot under recovery.
MPK99 said:
Maybe. Because, Encryption & rooting together doesn't go well.
On Encryption, you have to follow boot patch method. Recovery flashing won't work.
Extract boot.img from your stock firmware (or EU rom firmware), patch that file from magisk patch method. You'll get patched_boot.img. Flash that as boot under recovery.
Click to expand...
Click to collapse
Tried this method too, still can't delete that miui_mod_icons folder. Root isn't working yet.
Azamsm said:
Tried this method too, still can't delete that miui_mod_icons folder. Root isn't working yet.
Click to expand...
Click to collapse
Well, you have some specific reason to root. To remove some system apps right. You can do that on recovery too. Leave rooting, caz it's encrypted.
MPK99 said:
Well, you have some specific reason to root. To remove some system apps right. You can do that on recovery too. Leave rooting, caz it's encrypted.
Click to expand...
Click to collapse
Hey dude, first of all, I'm thankful to you for keeping calm and helping me
But actually both TWRP and OFox recoveries show nothing inside /system except for 4 folders which has nothing inside them. So I can't even see the files I want to delete.
Maybe it's because of the dynamic system partition or super partitions in android 11, idk I'm just super disappointed
Hey, @MPK99
One thing I noticed that system can be mounted read-only in OFox. If I want to mount it read-write, it just won't.