I Install Magisk in Android 8.0, but boot loop. Is there any one success install Magisk in Android 8.0?
LazyCountry said:
I Install Magisk in Android 8.0, but boot loop. Is there any one success install Magisk in Android 8.0?
Click to expand...
Click to collapse
https://forum.xda-developers.com/z2-force/how-to/oreo-nougat-how-to-root-z2-t3756669
41rw4lk said:
https://forum.xda-developers.com/z2-force/how-to/oreo-nougat-how-to-root-z2-t3756669
Click to expand...
Click to collapse
Thanks, I update from N, I failed because I don't format data. After format data, I install success.
LazyCountry said:
Thanks, I update from N, I failed because I don't format data. After format data, I install success.
Click to expand...
Click to collapse
Please could you detail how you did to install Magisk 16.x on Moto Z2 Play with Android 8?
I already used Magisk on Android 7.1.1, but after I upgraded to Android 8.0, Magisk stopped working, so I uninstalled it and tried to install again, but it gets bootloop.:crying:
marcelodsp said:
Please could you detail how you did to install Magisk 16.x on Moto Z2 Play with Android 8?
I already used Magisk on Android 7.1.1, but after I upgraded to Android 8.0, Magisk stopped working, so I uninstalled it and tried to install again, but it gets bootloop.:crying:
Click to expand...
Click to collapse
after flashing magisk on 8.0, you need to wipe user data
Uzephi said:
after flashing magisk on 8.0, you need to wipe user data
Click to expand...
Click to collapse
wipe user data still not work...
rakee said:
wipe user data still not work...
Click to expand...
Click to collapse
Are you following this root guide? It works, and chances are that any issue you have has been addressed and resolved there. If not, then post some info about your phone, what steps are you taking when you flash. You're not giving anyone much to work with to help you.
41rw4lk said:
Are you following this root guide? It works, and chances are that any issue you have has been addressed and resolved there. If not, then post some info about your phone, what steps are you taking when you flash. You're not giving anyone much to work with to help you.
Click to expand...
Click to collapse
Yes ,i following that,,my device is moto z. Griffin
rakee said:
Yes ,i following that,,my device is moto z. Griffin
Click to expand...
Click to collapse
That's your problem. Go to the Z section. This is for the Nash/Z2 force
marcelodsp said:
Please could you detail how you did to install Magisk 16.x on Moto Z2 Play with Android 8?
I already used Magisk on Android 7.1.1, but after I upgraded to Android 8.0, Magisk stopped working, so I uninstalled it and tried to install again, but it gets bootloop.:crying:
Click to expand...
Click to collapse
Did you make friend?
También me dió problema instalar magisk, bootloop
No me sirvió limpiar data ni hacer factory reset
Tal vez el problema esté en TWRP 3.2, ya que desde fastboot solo le di "boot" a TWRP (no lo instalé) y desde allí instalé Magisk v15.3 (tal vez no tenga nada que ver), después actualicé a v16.3 desde el teléfono ya funcionando.
Instalé el firmware antes de cada prueba
Google translator
It did not help me to clean data or do factory reset
Maybe the problem is in TWRP 3.2, since from fastboot I only gave "boot" to TWRP (I did not install it) and from there I installed Magisk v15.3 (maybe it has nothing to do), then I updated to v16.3 from the phone already working.
I installed the firmware before each test
Im still getting bootloops when trying to install Magisk on Oreo with Moto Z2 Play. Wiped /data after flashing Magisk to no avail. What am I doing wrong?
Mrm0rbid_99 said:
Im still getting bootloops when trying to install Magisk on Oreo with Moto Z2 Play. Wiped /data after flashing Magisk to no avail. What am I doing wrong?
Click to expand...
Click to collapse
A: you're in the wrong area. This forum is for the Z2 Force. The Majority of us don't have the Z2 Play to assist with that. Please try the Z2 play section.
I must be getting old... I've been here long enough to know to check if I'm in the right forum or not.
Thanks anyways!
Uzephi said:
after flashing magisk on 8.0, you need to wipe user data
Click to expand...
Click to collapse
No you don't. You just need to read the manual and turn on KEEPVERITY and KEEPFORCEENCRYPT - https://www.didgeridoohan.com/magisk/MagiskInstallationIssues
Doesn't matter if you're on a Yoga Tab 3 Plus, a Z2 Force, a Z2 Play - you need to turn those on if you're installing Magisk in an existing install.
Related
Did anyone managed to install xposed on LETV LE1 PRO US version?
Sent from my Le 1 Pro using Tapatalk
Yes, I did. I am on Cuoco 11S v4 ROM, though. I tried Gravitybox and App Settings.
Obviously not all functions in all modules work, as this is not a pure android ROM.
jerzyjerzy said:
Yes, I did. I am on Cuoco 11S v4 ROM, though. I tried Gravitybox and App Settings.
Obviously not all functions in all modules work, as this is not a pure android ROM.
Click to expand...
Click to collapse
How did you install the framework sdk21 arm64 Version 85 ? If I try this via TWRP 3.0.2 I get an error 1. Which version did you installed on your LeEco Le1 Pro US ?
I installed xposed-v85-sdk21-arm64.zip, no problems, no error messages. Installed via TWRP (X800_TWRP_3.0.2-0_Le1Pro_US).
Maybe download again?
http://dl-xda.xposed.info/framework/sdk21/arm64/
work
Confirmed, this worked on my Le 1 Pro - US. Some modules might not work since its ROM is heavily customized.... I guess. Good luck flashing guys.
I tried this twice and both times got stuck in an endless EUi loading screen bootloop. Did anyone else have this problem and solve it? I'm on Cuoco 12s
sosilly said:
I tried this twice and both times got stuck in an endless EUi loading screen bootloop. Did anyone else have this problem and solve it? I'm on Cuoco 12s
Click to expand...
Click to collapse
Did you clear the caches? I have it installed on 12s and have had no problems..I used these files :
XposedInstaller_3.0_alpha4.apk
xposed-v85-sdk21-arm64.zip
tc0566 said:
Did you clear the caches? I have it installed on 12s and have had no problems..I used these files :
XposedInstaller_3.0_alpha4.apk
xposed-v85-sdk21-arm64.zip
Click to expand...
Click to collapse
For me it worked on 12S but it does not work on 14S.
triplexone said:
For me it worked on 12S but it does not work on 14S.
Click to expand...
Click to collapse
you probably want sdk22 for 14s, as it's M
The 14s is not M, you should use sdk21 but maybe another version will work
Letv 1pro
Hey guys,
I successfully flashed HavocOs the other day and everything was working just fine.
Then i decided to flash Resurrection Remix and everything went bad.
After the flash, the phone booted but the wifi won't connect. Even after restart it won't connect.
The symbol lights up but then it doesn't turn on and i can't find any networks. 4G data and Bluetooth is working but Wifi isn't.
After the custom roms i decided to flash the original recovery and the ozip for RMX1991.
Unfortunately with the same result. Flash is successful, 4G and Bluetooth are working but wifi won't find any networks.
Also tried to format everything and flashed all the parts with Fastboot using this: https://forum.xda-developers.com/realme-x2/how-to/stock-fastboot-flashable-images-realme-t4054855
But still the same result.
I have run out of options to try...
Anyone has any ideas?
Thanks!
maybe this will help,realme official cable flash tool.
realme flash,using rom package as ofp,
for cable flash tool,
https://r11.realme.net/CN/thread-attachment/1273935417841823744.zip
roms in ofp pack
url：https://pan.baidu.com/s/1E2iYVN8TmUp__at18iydwg
share code：9bk7
zhengye75 said:
maybe this will help,realme official cable flash tool.
realme flash,using rom package as ofp,
for cable flash tool,
roms in ofp pack
url：
share code：9bk7
Click to expand...
Click to collapse
Thanks for the help!
Can you maybe upload one of the images from the Baidu link to Mediafire or Zippyshare or something?
I can't access Baidu. I tried to but it keeps telling me to make an account and i can't do that without a chinese phone number.
Thanks for your assistance!
http://www.mediafire.com/file/n2wzdt9f71cq7ai/RMX1991_C.17.ofp/file
x2 c17rom
ofg packaged
Thanks man! You are a real hero
timbo2567 said:
Thanks man! You are a real hero
Click to expand...
Click to collapse
Unfortunately it did not work for me.
hola necesito ayuda tengo un realme x2 rmx1991 y no encuentro ninguna rom compatible
hola necesito ayuda tengo un realme x2 rmx1991 y no encuentro ninguna rom compatible y ya formate el sistema
Does anyone have a link for RMX1993 RUI ofp file?
i am facing the same problem, almost tried every possible things but it not worked
TonmoyD. said:
i am facing the same problem, almost tried every possible things but it not worked
Click to expand...
Click to collapse
You´re right. RMX 1993 don't has ofp file that works with realme tool. I tried tons of tricks, nothing works. Today I sent my device to sc, they have other ways to flash UI. We´ll see...
MODERATOR EDIT: ENGLISH TRANSLATION ADDED
I'm a beginner in the world of roms, I've never installed any on my moto g5 (cedric) and I intend to install it, I saw that twrp apparently doesn't get fixed on the system and it has a force encrypt file that works perfectly on android 7 but on 8.1 it doesn't work and the loop. Does anyone tell me if this file is mandatory? From what I've seen it fixes the Recovery on the moto g5.
----------------------------
Eu sou iniciante no mundo das roms,nunca instalei nenhuma no meu moto g5(cedric)e pretendo instalar,vi que o twrp aparentemente não fica fixado no sistema e tem um arquivo de force encrypt que funciona perfeitamente no android 7 mas no 8.1 não funciona e da loop.Alguem me diz se é obrigatório mesmo esse arquivo?Pelo que vi ele fixa o Recovery no moto g5.
Sun0507 said:
MODERATOR EDIT: ENGLISH TRANSLATION ADDED
I'm a beginner in the world of roms, I've never installed any on my moto g5 (cedric) and I intend to install it, I saw that twrp apparently doesn't get fixed on the system and it has a force encrypt file that works perfectly on android 7 but on 8.1 it doesn't work and the loop. Does anyone tell me if this file is mandatory? From what I've seen it fixes the Recovery on the moto g5.
----------------------------
Eu sou iniciante no mundo das roms,nunca instalei nenhuma no meu moto g5(cedric)e pretendo instalar,vi que o twrp aparentemente não fica fixado no sistema e tem um arquivo de force encrypt que funciona perfeitamente no android 7 mas no 8.1 não funciona e da loop.Alguem me diz se é obrigatório mesmo esse arquivo?Pelo que vi ele fixa o Recovery no moto g5.
Click to expand...
Click to collapse
I believe you are talking about dm_verity
If you are flashing a custom rom you don't need to worry about this
Also if you are sticking with stock rom but flash magisk to root you also don't need to worry about this
If you are not doing any of the above then there's no need to flash twrp in the first place
Just make sure you have flashed the lastet stock retail firmware if you are flashing the latest roms (android 10 custom roms and above)
TheFixItMan said:
I believe you are talking about dm_verity
If you are flashing a custom rom you don't need to worry about this
Also if you are sticking with stock rom but flash magisk to root you also don't need to worry about this
If you are not doing any of the above then there's no need to flash twrp in the first place
Just make sure you have flashed the lastet stock retail firmware if you are flashing the latest roms (android 10 custom roms and above)
Click to expand...
Click to collapse
Yes, I'm talking about Dm verity. And because I kind of saw in some tutorials that the moto g5 on Android 8.1 has complications in installing twrp (They say that twrp is not fixed in the system and disappears every time you restart the device) and how I really want to install the lineage but I'm a little afraid, in terms of Dm verity and the complications when installing this custom recovery. My moto g5 cedric is all right in stock rom and with the latest security patch also updated (at least the last one released by the manufacturer).
Twrp never disappears if you flash it
You have two options
Flash twrp - replaces stock recovery
Boot to twrp - temporarily load twrp but it doesn't replace stock recovery
DM-verity only applies to the stock kernel
If you flash twrp and swipe to make modifications your phone will not boot if on stock kernel
This is why you either flash magisk to root phone (patches boot image (kernel) so phone will boot
Or flash a custom rom which will have a patched kernel anyway
There would be no reason to flash twrp unless you were rooting or flashing a custom rom anyway so as mentioned before dm-verity doesn't matter
TheFixItMan said:
Twrp never disappears if you flash it
You have two options
Flash twrp - replaces stock recovery
Boot to twrp - temporarily load twrp but it doesn't replace stock recovery
DM-verity only applies to the stock kernel
If you flash twrp and swipe to make modifications your phone will not boot if on stock kernel
This is why you either flash magisk to root phone (patches boot image (kernel) so phone will boot
Or flash a custom rom which will have a patched kernel anyway
There would be no reason to flash twrp unless you were rooting or flashing a custom rom anyway so as mentioned before dm-verity doesn't matter
Click to expand...
Click to collapse
If possible, could you tell me how I can flash this twrp? so I can replace the recovery please.
Sun0507 said:
If possible, could you tell me how I can flash this twrp? so I can replace the recovery please.
Click to expand...
Click to collapse
All instructions are in the official twrp thread in the dev section
TheFixItMan said:
All instructions are in the official twrp thread in the dev section
Click to expand...
Click to collapse
ok thanks for this help
Oneplus just release MT2111_11_F.07 rom based on OOS13.
I am upgrading to it now. And I am just wondering how to extract boot.img from my phone.
I am afraid that a direct patch from Magisk after OTA before reboot may brick my phone because it's a major update. Has anyone tested it? Or already have F.07 boot.img?
xiaowang0131 said:
Oneplus just release MT2111_11_F.07 rom based on OOS13.
I am upgrading to it now. And I am just wondering how to extract boot.img from my phone.
I am afraid that a direct patch from Magisk after OTA before reboot may brick my phone because it's a major update. Has anyone tested it? Or already have F.07 boot.img?
Click to expand...
Click to collapse
Do you have a link for that ROM?
gscherulli said:
Do you have a link for that ROM?
Click to expand...
Click to collapse
You may receive it directly if you are joining the open beta program.
Besides since I am in mainland of China, I have difficulty uploading the rom to mega or google drive.
xiaowang0131 said:
Você pode recebê-lo diretamente se estiver participando do programa beta aberto.
Além disso, como estou na China continental, tenho dificuldade em enviar a rom para o mega ou google drive.
xiaowang0131 said:
You may receive it directly if you are joining the open beta program.
Besides since I am in mainland of China, I have difficulty uploading the rom to mega or google drive.
Click to expand...
Click to collapse
I understood. I'm in Brazil. I will wait for the open beta 13 by the Oxygen Update. Thanks
Click to expand...
Click to collapse
After Open Beta 2 (MT2111_11_F.08) for 9RT Fastboot has been blocked by OnePlus, No more access to fastboot and recovery, while getting into fastboot Phone will boot to system directly.
Very dirty trick by OnePlus for blocking fastboot, now it has become like 10 Series, only EDL with MSM for flashing Phone both upgrading and downgrading.
Rolling back to A12 is possible, but fastboot flashing is bricking the device as fastbootd is not apearing anymore... and its A/B Partition....
gonetask said:
Rolling back to A12 is possible, but fastboot flashing is bricking the device as fastbootd is not apearing anymore... and its A/B Partition....
Click to expand...
Click to collapse
Fastbootd should work. If you unlocked bootloader before flashing beta, you can flash using fastbootd.
penguinus said:
Fastbootd should work. If you unlocked bootloader before flashing beta, you can flash using fastbootd.
Click to expand...
Click to collapse
Havent tried but yes I did unlock bootloader before flashing OOS13
Me gustaría saber si habéis visto o conseguido un TWRP para este terminal ya que es muy útil para todo en general, tanto de instalar el root magic, como copias de Seguridad sin usar el pc, instalación de rooms, uso de adb...
Mod translation: I would like to know if you have seen or obtained a TWRP for this terminal since it is very useful for everything in general, both installing the magic root, as well as Backup copies without using the pc, installing rooms, using adb...
GitHub - BigfootACA/device_nubia_nx729j: TWRP device tree for Nubia RedMagic 8 Pro (NX729J)
TWRP device tree for Nubia RedMagic 8 Pro (NX729J) - GitHub - BigfootACA/device_nubia_nx729j: TWRP device tree for Nubia RedMagic 8 Pro (NX729J)
github.com
DarkestSpawn said:
GitHub - BigfootACA/device_nubia_nx729j: TWRP device tree for Nubia RedMagic 8 Pro (NX729J)
TWRP device tree for Nubia RedMagic 8 Pro (NX729J) - GitHub - BigfootACA/device_nubia_nx729j: TWRP device tree for Nubia RedMagic 8 Pro (NX729J)
github.com
Click to expand...
Click to collapse
One question, what happens if instead of inserting the command to flash the recovery with: fastboot flash recovery_ab out/target/product/nx729j/recovery.img You put the command fasboot flash recovery recovery.img , what would happen would stay in the stuck logo, since I have always put twrp in that way and never had problems, maybe with these terminals it is necessary to insert fastboot flash recovery_ab, I would like to know what happens.
DarkestSpawn said:
GitHub - BigfootACA/device_nubia_nx729j: TWRP device tree for Nubia RedMagic 8 Pro (NX729J)
TWRP device tree for Nubia RedMagic 8 Pro (NX729J) - GitHub - BigfootACA/device_nubia_nx729j: TWRP device tree for Nubia RedMagic 8 Pro (NX729J)
github.com
Click to expand...
Click to collapse
What also happens if you add the magic by zip file, that is, the file that causes it to be rooted, without patching the ini_boot file, I see it annoying... and then to unroot it, what happens if you do it from magick? I rotated all my Xiaomi like this, but since I've never had a red magic, I don't know... you always install the twrp and then zip the magisk there and it would rotate the terminal without patching files like the ini_boot that many have problems.
jaimele said:
One question, what happens if instead of inserting the command to flash the recovery with: fastboot flash recovery_ab out/target/product/nx729j/recovery.img You put the command fasboot flash recovery recovery.img , what would happen would stay in the stuck logo, since I have always put twrp in that way and never had problems, maybe with these terminals it is necessary to insert fastboot flash recovery_ab, I would like to know what happens.
Click to expand...
Click to collapse
I used "fastboot flash recovery [imagenamehere].img" and flashed with no issue.
jaimele said:
What also happens if you add the magic by zip file, that is, the file that causes it to be rooted, without patching the ini_boot file, I see it annoying... and then to unroot it, what happens if you do it from magick? I rotated all my Xiaomi like this, but since I've never had a red magic, I don't know... you always install the twrp and then zip the magisk there and it would rotate the terminal without patching files like the ini_boot that many have problems.
Click to expand...
Click to collapse
Im assuming the one you used for Xiaomi patched the init_boot and not boot, in which should work in theory. Its always best to extract the init_boot image and patch via the magisk app tho.
jaimele said:
What also happens if you add the magic by zip file, that is, the file that causes it to be rooted, without patching the ini_boot file, I see it annoying... and then to unroot it, what happens if you do it from magick? I rotated all my Xiaomi like this, but since I've never had a red magic, I don't know... you always install the twrp and then zip the magisk there and it would rotate the terminal without patching files like the ini_boot that many have problems.
Click to expand...
Click to collapse
The redmagic 8 pro has a separate recovery partition. The Xiaomi device your referring to probably patched the boot.img.
Btw a new recovery build was posted today.
DarkestSpawn said:
Usé "fastboot flash recovery [nombre de la imagen aquí].imfastboot flash recovery [nombre de la imagen aquí].img" y parpadeé sin problemas.
Supongo que el que usaste para Xiaomi parcheó el init_boot y no el arranque, en el que debería funcionar en teoría. Siempre es mejor extraer la imagen init_boot y parchear a través de la aplicación magisk aunque.
Click to expand...
Click to collapse
Regarding use"fastboot flash recovery [name of the image here].img , as I have seen an extension of flashing " flash recovery_ab" I would like to know what that extension is
If you dont call any slot to flash, it will flash to the active slot.
Example. "fastboot flash recovery [imagenamehere].img" would flash to my slot b because that is my active slot
So it is not necessary to add the flash recovery_ab extension
jaimele said:
So it is not necessary to add the flash recovery_ab extension
Click to expand...
Click to collapse
If you want to flash to the active slot, no its not necessary.
DarkestSpawn said:
Ok, I really understand but on xiaomi mobiles and others that do not have a separation.So if you install magick apk and zip file by twrp and it works correctly, then if I unroot it through magick apk, is it possible that it stays in bootloop?, that is, without using ini_boot patching and also not for unrooting install again the imi_boot without patching? Doing it this way would something happen without doing it as it really has to be done? I would like to know this since you use this system more and I am learning
Click to expand...
Click to collapse
DarkestSpawn said:
GitHub - BigfootACA/device_nubia_nx729j: TWRP device tree for Nubia RedMagic 8 Pro (NX729J)
TWRP device tree for Nubia RedMagic 8 Pro (NX729J) - GitHub - BigfootACA/device_nubia_nx729j: TWRP device tree for Nubia RedMagic 8 Pro (NX729J)
github.com
Click to expand...
Click to collapse
Have you tried to backup and restore data yet?
JWnSC said:
Have you tried to backup and restore data yet?
Click to expand...
Click to collapse
No. I only tried other xiaomi terminals with other twrp and without problems, but I have never done it with this terminal, I would like to know what would happen as mentioned above. Like I also bought a 165w charger for this model but for the 16 gb one and it doesn't charge at 165... ocea it's for nothing, according to what they told me the support is for the terminal pro 8 basic version of 12 gb;(
jaimele said:
No. I only tried other xiaomi terminals with other twrp and without problems, but I have never done it with this terminal, I would like to know what would happen as mentioned above. Like I also bought a 165w charger for this model but for the 16 gb one and it doesn't charge at 165... ocea it's for nothing, according to what they told me the support is for the terminal pro 8 basic version of 12 gb;(
Click to expand...
Click to collapse
It works. default language is Chinese. Has anyone tried to restore a data backup yet? I tried super.img, that worked. My device is global redmagic 8 pro 16/512gb.
JWnSC said:
It works. default language is Chinese. Has anyone tried to restore a data backup yet? I tried super.img, that worked.
Click to expand...
Click to collapse
Where did you download that version of twrp as I have seen is 0.1
jaimele said:
Where did you download that version of twrp as I have seen is 0.1
Click to expand...
Click to collapse
Release v0.2 · BigfootACA/device_nubia_nx729j
everything except data encryption and haptics should work fine compared with v0.1, touch screen unusable caused by haptics has been fixed android hal of haptics still needs to be fixed 除了数据加密和振动之外的...
github.com
JWnSC said:
Release v0.2 · BigfootACA/device_nubia_nx729j
everything except data encryption and haptics should work fine compared with v0.1, touch screen unusable caused by haptics has been fixed android hal of haptics still needs to be fixed 除了数据加密和振动之外的...
github.com
Click to expand...
Click to collapse
funciona muy mal , tiene lag este recovery y muy lento....te pasa a ti¿?
jaimele said:
funciona muy mal , tiene lag este recovery y muy lento....te pasa a ti¿?
Click to expand...
Click to collapse
No lag for me on the latest build. I'm running decrypted so everything is working, except data restore. First version did lag because haptics were enabled and Android hal problem.
JWnSC said:
Release v0.2 · BigfootACA/device_nubia_nx729j
everything except data encryption and haptics should work fine compared with v0.1, touch screen unusable caused by haptics has been fixed android hal of haptics still needs to be fixed 除了数据加密和振动之外的...
github.com
Click to expand...
Click to collapse
cuando voy a instalar en twrp no sale mi almacenamiento interno...Solo la direccion " / " alguna solucion¿
jaimele said:
cuando voy a instalar en twrp no sale mi almacenamiento interno...Solo la direccion " / " alguna solucion¿
Click to expand...
Click to collapse
My data is decrypted (encryption disabled) like I already said.. Which is why it works fine for me ..