Related
I was using SR3-SuperSU-v2.79 and flashed SuperSU v2.82 but
phone wouldnt boot up , so I reflashed SR3-SuperSU-v2.79 and
phone now boots ok but I dont have root,
I'm using TWRP blu-spark 3.1.0 v26
Petesky said:
I was using SR3-SuperSU-v2.79 and flashed SuperSU v2.82 but
phone wouldnt boot up , so I reflashed SR3-SuperSU-v2.79 and
phone now boots ok but I dont have root,
I'm using TWRP blu-spark 3.1.0 v26
Click to expand...
Click to collapse
Flash your rom then supersu, Magisk is also a nice option.
Puddi_Puddin said:
Flash your rom then supersu, Magisk is also a nice option.
Click to expand...
Click to collapse
I thought I might have to do that , is there a link to the latest SuperSU that works
on oneplus 3
Petesky said:
I thought I might have to do that , is there a link to the latest SuperSU that works
on oneplus 3
Click to expand...
Click to collapse
Well you already have the version number.. Not too hard to search is it?
http://lmgtfy.com/?iie=1&q=latest+stable+supersu
Well that was clever
I already did that and tried 2 that didnt work ,
SuperSU282 and SuperSU-v2.82-SYSTEMMODE , I asked for one that worked on the oneplus 3,
But done a fresh install of 4.1.3 , flashed SR3-SuperSU-v2.79 again and its working good, updated binaries and no DM_verity error
Petesky said:
Well that was clever
I already did that and tried 2 that didnt work ,
SuperSU282 and SuperSU-v2.82-SYSTEMMODE , I asked for one that worked on the oneplus 3,
But done a fresh install of 4.1.3 , flashed SR3-SuperSU-v2.79 again and its working good, updated binaries and no DM_verity error
Click to expand...
Click to collapse
Well there is no Supersu that specially works for the Oneplus 3. That is why I always recommend to try things yourself. Take a backup of system and boot and you basically can keep trying things without risking that your phone doesn't boot or you loose data.
Good point
just update the 2.79 via playstore to 2.82
Anyone had any success flashing Magisk on the 5T yet? I've tried + it flashes fine, but WiFi doesn't work; neither mobile data.
Semi solution:
https://forum.xda-developers.com/oneplus-5t/development/rom-freedomos-2-0-2-t3709708
The ROM comes with Magisk (I can't say first hand since I don't have a phone yet)
Yes magisk working but dont Format Data.
Hmmm, I have it without issues (I think).
Followed this post: https://forums.oneplus.net/threads/oneplus-5t-unlock-bootloader-flash-twrp-root-nandroid-efs.685403/
@Theberge43 on the 5t not the 5 right? Did you flash v14 or v14.something i.e the beta version? Thanks!
madyoda said:
@Theberge43 on the 5t not the 5 right? Did you flash v14 or v14.something i.e the beta version? Thanks!
Click to expand...
Click to collapse
On the 5T indeed. Used this link (from the mentioned thread): https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
@Theberge43 magisk code 1456 + it's fully working for you? Interesting thanks - I'll try it again as it didn't work for me!
madyoda said:
@Theberge43 magisk code 1456 + it's fully working for you? Interesting thanks - I'll try it again as it didn't work for me!
Click to expand...
Click to collapse
Here is my Magisk.
@Theberge43 nice thanks! About to try
@Theberge43 yup that worked thanks! No idea what happened the first time - possible corrupt zip or faulty flash I guess!
Maybe I spoke a tad too soon. If I reboot, the modem goes again. If I then reboot, it comes back, etc etc. Weird!
Schrotty35 said:
Yes magisk working but dont Format Data.
Click to expand...
Click to collapse
At what point should not format the data? If you are on the stock rom, you have to go on recovery and directly flash magisk?
(When i flash magisk, i reboot always on recovery...and i can't flash FreedomOS with modified TWRP or Blue_spark....)à
I actually flashed the official version and not beta. Works perfectly fine on OP5T (latest OxygenOS update).
No problems at all with magisk. Not using any guide, just flashed twrp, dm-verity patch from jcadduono, magisk 14.0
Both 4G and WiFi work as expected.
v14.3 here with no issues. Was just in a badspot for the first screen shot. Went right back to LTE
mad-murdock said:
No problems at all with magisk. Not using any guide, just flashed twrp, dm-verity patch from jcadduono, magisk 14.0
Both 4G and WiFi work as expected.
Click to expand...
Click to collapse
Dm patch not need.
can't wait to get my 5t , first thing is installing magisk and adaway
Schrotty35 said:
Dm patch not need.
Click to expand...
Click to collapse
With me i must flash dm verity to start on the system
samtab37 said:
With me i must flash dm verity to start on the system
Click to expand...
Click to collapse
Ok have you a link for working version on 5t?
Schrotty35 said:
Ok have you a link for working version on 5t?
Click to expand...
Click to collapse
Is the same as OnePlus 5: https://drive.google.com/file/d/1YMHqtyILolheUuJtjpmCbL6hHKD5MQo0/view?usp=drivesdk
I try new version (v6) of no verity but don't work, for me this file is the only way to boot
Envoyé de mon ONEPLUS A5010 en utilisant Tapatalk
Managed to install it on OP3T but it won't work on OP3
Here is what i am doing, please correct me if i am doing anything wrong
Cleaning Super User from Updated UnSU.zip which works fine. Flashing Stock Boot.img (OK)
Flashing Magisk 14.3 (OK)
reboot and Stuck on oneplus logo
Doing it all again and flashing Magisk 14.5 and again Bootloop.
any help is highly appreciated Thanks
Good to know?
Sent from my OnePlus 3 using Tapatalk
Use the uninstaller and completely remove Magisk: https://forum.xda-developers.com/attachment.php?attachmentid=4339479&d=1511372903
Then install the v14.5(1456) beta: https://forum.xda-developers.com/attachment.php?attachmentid=4340290&d=1511453617
Working fine here with OOS 5.0
arcslt18 said:
Hello, i am having trouble installing Magisk 14.3 and 14.5
Click to expand...
Click to collapse
great description of your problem mate.
noone can help you if you dont tell whats your exact problem and what you did.
MarcTremonti said:
great description of your problem mate.
noone can help you if you dont tell whats your exact problem and what you did.
Click to expand...
Click to collapse
i posted that from xda app. text was missing. please check now. Thanks
Cyda said:
Use the uninstaller and completely remove Magisk: https://forum.xda-developers.com/attachment.php?attachmentid=4339479&d=1511372903
Then install the v14.5(1456) beta: https://forum.xda-developers.com/attachment.php?attachmentid=4340290&d=1511453617
Working fine here with OOS 5.0
Click to expand...
Click to collapse
Which device are you using? Twrp version? and magisk? please read my post now, as some text was missing when i posted it. i was using Xda App
Explorer23 said:
Good to know?
Sent from my OnePlus 3 using Tapatalk
Click to expand...
Click to collapse
Sorry some text was missing. please read post now. Thanks
arcslt18 said:
Which device are you using? Twrp version? and magisk? please read my post now, as some text was missing when i posted it. i was using Xda App
Click to expand...
Click to collapse
OP3, using the latest blue_spark TWRP and the version of Magisk I linked above.
Cyda said:
OP3, using the latest blue_spark TWRP and the version of Magisk I linked above.
Click to expand...
Click to collapse
Thanks for helping me, i tried Blu spark and magisk from your link, i'm getting bootloop again, No luck
for me - coming from a custom lineage 7.1.2 rom - it worked the following way (but it completely formatted the phone due to an encryption issue)
- flash blu spark TWRP for Oreo
- wipe system, data, cache, dalvik
- flash OB27 ROM
- flash blu spark again
- reboot to recovery
- flash magisk 14.3
Are you having a boot loop (phone reboots again and again) or is it booting up forever with the boot logo on the screen? you are describing both in your post.
I'm using 14.5 and ask works great here on OP27 Oreo was using 14.3 and that all worked great too and did nothing special part from install
Ok, i have the same problem, I am on OB28 and working SU root. i want to change to magisk, so I completely unrootet the phone and tried to flash magisk via newest twrp. But it stuck at bootlogo. do I really have to flash for magisk the twrp.enkgst? will it work then?
OK, solved, flashed spark twrp flashed magisk uninstaller, flashed magisk 14.5 I'm fine
I tired all arm64 custom roms for moto z play, some arm, tried mixing with all kernels and magisk/without magisk.
And i can't pass safetynet on all these configurations
That's the point of SN. Those ROMs aren't certified by Google so they don't want you to pass. That's not a problem of any ROM, that's how it's intended to work
But I have passed with magisk
Artim_96 said:
That's the point of SN. Those ROMs aren't certified by Google so they don't want you to pass. That's not a problem of any ROM, that's how it's intended to work
Click to expand...
Click to collapse
But on my old phone, i was using custom roms (not certificed), and SN was passing.
mijing said:
But I have passed with magisk
Click to expand...
Click to collapse
With ROM you using?
dawidrejowski said:
With ROM you using?
Click to expand...
Click to collapse
Im using official Validus ..you can try universal safety net fix to pass safety net.I'm using this.
dawidrejowski said:
But on my old phone, i was using custom roms (not certificed), and SN was passing.
Click to expand...
Click to collapse
How old of a phone? My last phone (HTC One M8) passed on custom ROMs because it didn't seem to report the bootloader was unlocked. But I have safety net passing on custom ROMs on my Z play thanks to magisk and universal safteynet fix beta 5.
mijing said:
Im using official Validus ..you can try universal safety net fix to pass safety net.I'm using this.
Click to expand...
Click to collapse
What do you mean by "universal..." - magisk? if so, which release are you using? Thanks!
KrisM22 said:
What do you mean by "universal..." - magisk? if so, which release are you using? Thanks!
Click to expand...
Click to collapse
Universal safetyNet Fix(v2 Beta 5) is the module of Magisk
mijing said:
Universal safetyNet Fix(v2 Beta 5) is the module of Magisk
Click to expand...
Click to collapse
That is a very old one - could you please attach it to your post for a few minutes? TIA!
KrisM22 said:
That is a very old one - could you please attach it to your post for a few minutes? TIA!
Click to expand...
Click to collapse
Yes it is too old but till now it is usefull as you can see
mijing said:
Yes it is too old but till now it is usefull as you can see
Click to expand...
Click to collapse
I found it up on
https://androidfilehost.com/?fid=673368273298984533
is that it?
I'll go try it on AOSP 8.1 Alberto97
Yes,It Is. but I dont Know about AOSP Is it will work or not
mijing said:
Yes,It Is. but I dont Know about AOSP Is it will work or not
Click to expand...
Click to collapse
lots of red messages so far - what version of magisk MANAGER are you using? (magisk/settings/about) - I tried 4.3.1 but no go.
EDIT I see you're running 16 of magisk, but have added module 14 2-5. How did you manage to add that?
KrisM22 said:
lots of red messages so far - what version of magisk MANAGER are you using? (magisk/settings/about) - I tried 4.3.1 but no go.
EDIT I see you're running 16 of magisk, but have added module 14 2-5. How did you manage to add that?
Click to expand...
Click to collapse
Yes I'm using v16 of magisk with module
Go to magisk manager - module - + bottom (for add Module) install it
If installation fail you can flash with recovery that's it.
(My English? )
mijing said:
But I have passed with magisk
Click to expand...
Click to collapse
Edit: Never mind I saw what Rom you were running.
mijing said:
Yes I'm using v16 of magisk with module
Go to magisk manager - module - + bottom (for add Module) install it
If installation fail you can flash with recovery that's it.
(My English )
Click to expand...
Click to collapse
Your English is excellent!!!
I now have a very tiny understanding of Magisk Modules...
I started with 1600 this time (it later updated the mgr).
I thought this failed before so it may be necessary to try to add module with magisk, let it fail, then boot to recovery, flash that old 2 beta 5 zip (flash goes fine) , and reboot and I find that old 2 beta 5 zip is now in magisk modules. YOU THE PERSON!!! (gender non-specific version of you da man!)
I went on to do my usual of install TBPro, restore my stuff(obviously root works), reboot to recovery to backup at this point. and test. SafetyNet passes fully, Pogo plays, Netflix shows in gpstore. And I now have a working 8.1 on my MZP.
HUGE THANKS for your patience!!!!!!!
KrisM22 said:
Your English is excellent!!!
I now have a very tiny understanding of Magisk Modules...
I started with 1600 this time (it later updated the mgr).
I thought this failed before so it may be necessary to try to add module with magisk, let it fail, then boot to recovery, flash that old 2 beta 5 zip (flash goes fine) , and reboot and I find that old 2 beta 5 zip is now in magisk modules. YOU THE PERSON!!! (gender non-specific version of you da man!)
I went on to do my usual of install TBPro, restore my stuff(obviously root works), reboot to recovery to backup at this point. and test. SafetyNet passes fully, Pogo plays, Netflix shows in gpstore. And I now have a working 8.1 on my MZP.
HUGE THANKS for your patience!!!!!!!
Click to expand...
Click to collapse
Im glad you have fix your problem
KrisM22 said:
Your English is excellent!!!
I now have a very tiny understanding of Magisk Modules...
I started with 1600 this time (it later updated the mgr).
I thought this failed before so it may be necessary to try to add module with magisk, let it fail, then boot to recovery, flash that old 2 beta 5 zip (flash goes fine) , and reboot and I find that old 2 beta 5 zip is now in magisk modules. YOU THE PERSON!!! (gender non-specific version of you da man!)
I went on to do my usual of install TBPro, restore my stuff(obviously root works), reboot to recovery to backup at this point. and test. SafetyNet passes fully, Pogo plays, Netflix shows in gpstore. And I now have a working 8.1 on my MZP.
HUGE THANKS for your patience!!!!!!!
Click to expand...
Click to collapse
Check for Bluetooth and wifi if they are working correctly. I flashed the fix on AOSP and my Bluetooth crashed, needed to restore backup.
Hi guys, I rooted my redmi note 8 yesterday. Everything went well except two things: on boot the error message said that "there is an internal problem" and the phone reboots/shuts down itself.
Any thoughts?
cicish said:
Hi guys, I rooted my redmi note 8 yesterday. Everything went well except two things: on boot the error message said that "there is an internal problem" and the phone reboots/shuts down itself.
Any thoughts?
Click to expand...
Click to collapse
You should explain the problem obviously if you want a help, if your phone still working you should flash twerp.img to be able to root it and solve any existing problem by flashing new rom
niceman2007 said:
You should explain the problem obviously if you want a help, if your phone still working you should flash twerp.img to be able to root it and solve any existing problem by flashing new rom
Click to expand...
Click to collapse
Hey thanks for answer.
Actually i did everything correctly, flashed latest twrp, tried several roms, oficial, unoficial etc., But still no result. After all these, ive flashed the stock rom which solved the problem but phone is no more rooted. So..
cicish said:
Hey thanks for answer.
Actually i did everything correctly, flashed latest twrp, tried several roms, oficial, unoficial etc., But still no result. After all these, ive flashed the stock rom which solved the problem but phone is no more rooted. So..
Click to expand...
Click to collapse
If you still want to root it again,after flasing new rom go to twero and then go to wipe then format,you should format your phone after rom flashing,try this and inform me
Yes yes! I want to root phone once again. So the steps are these:
1) booting into twrp with adb from pc.
2) from the twrp menu wiping and formating the data
3) instaling new rom
Is this true?
Thanks!
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Leeban Joseph said:
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Click to expand...
Click to collapse
You mean that its possible to have root access on stock rom?
Leeban Joseph said:
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Click to expand...
Click to collapse
Hey, I was able to flash magical using twrp but can't flash dm-verity. It gives me some error 1 with no description. I could flash magisk. What can the problem be? Thanks!
cicish said:
Hey, I was able to flash magical using twrp but can't flash dm-verity. It gives me some error 1 with no description. I could flash magisk. What can the problem be? Thanks!
Click to expand...
Click to collapse
From your stock rom extract the boot.img and place it on your SD card. Flash the boot image using twrp or you can also flash in fastboot, then reboot. Now boot to twrp recovery and flash dm-verity first and then magisk zip. Worked for me I'm having root permission with stock rom.
Leeban Joseph said:
From your stock rom extract the boot.img and place it on your SD card. Flash the boot image using twrp or you can also flash in fastboot, then reboot. Now boot to twrp recovery and flash dm-verity first and then magisk zip. Worked for me I'm having root permission with stock rom.
Click to expand...
Click to collapse
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
cicish said:
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
Click to expand...
Click to collapse
UPDATE: after another custom rom install failure, i got back to stock miui 11 with miflash tool. the problem is now that when i unlock the bootloader and try to flash magisk and disable-dm-verity, the system refuses to boot. the redmi note 8 logo is sticked on boot. i dont understand what i am doing incorrectly. if there are any suggestions im ready to try.
cicish said:
UPDATE: after another custom rom install failure, i got back to stock miui 11 with miflash tool. the problem is now that when i unlock the bootloader and try to flash magisk and disable-dm-verity, the system refuses to boot. the redmi note 8 logo is sticked on boot. i dont understand what i am doing incorrectly. if there are any suggestions im ready to try.
Click to expand...
Click to collapse
Is your bootloader unlocked right now or did you lock it while flashing using miflash tool.
Leeban Joseph said:
Is your bootloader unlocked right now or did you lock it while flashing using miflash tool.
Click to expand...
Click to collapse
the bootloader was unlocked. everything went kinda fine, until i flashed youtube vanced from magisk: when i did that, the system was unable to boot. i don't know what's happening. is there anything to do with kernel or something? really interesting what i am doing wrong.
cicish said:
the bootloader was unlocked. everything went kinda fine, until i flashed youtube vanced from magisk: when i did that, the system was unable to boot. i don't know what's happening. is there anything to do with kernel or something? really interesting what i am doing wrong.
Click to expand...
Click to collapse
I think it may be because of YouTube vanced module. If you remove the module you might be able to boot. In twrp in the advanced option select file manager and then select data/adb/magisk/ in that you will find the list of installed modules, select the one which is causing the problem and delete that folder and try to reboot.
Leeban Joseph said:
I think it may be because of YouTube vanced module. If you remove the module you might be able to boot. In twrp in the advanced option select file manager and then select data/adb/magisk/ in that you will find the list of installed modules, select the one which is causing the problem and delete that folder and try to reboot.
Click to expand...
Click to collapse
I've already flashed the stock rom but this will help me next time! Thanks!
I'll stop trying for some days cause I'm really tired with tweaking so thanks and will get back!
cicish said:
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
Click to expand...
Click to collapse
Your device reboots randomly on custom rom because probably it was made for tianma display and you have hauxing display
the_weird_aquarian said:
Your device reboots randomly on custom rom because probably it was made for tianma display and you have hauxing display
Click to expand...
Click to collapse
Hey, thanks for the answer. i've just googled about it and you are right. checked the TP version and it says that i have huaxing display. in the Lineage OS thread the moderator wrote that the next update will fix that bug. hopefully ill be able to install custom rom. also if you know, are there any custom roms for huaxing display? thank you man!
cicish said:
Hey, thanks for the answer. i've just googled about it and you are right. checked the TP version and it says that i have huaxing display. in the Lineage OS thread the moderator wrote that the next update will fix that bug. hopefully ill be able to install custom rom. also if you know, are there any custom roms for huaxing display? thank you man!
Click to expand...
Click to collapse
currently bootleggers rom,PE official and unofficial and drepfest all have reboot issues in huaxing display. Haven't tried any other rom yet..still on MIUI..waiting to get the issue fixed asap.
the_weird_aquarian said:
currently bootleggers rom,PE official and unofficial and drepfest all have reboot issues in huaxing display. Haven't tried any other rom yet..still on MIUI..waiting to get the issue fixed asap.
Click to expand...
Click to collapse
i've tried Lineage OS too and it also has reboot issue. i've checked a thread here https://forum.xda-developers.com/redmi-note-5-pro/development/derp-kernel-clang-4-4-138-t3804996 that flashing a different kernel when you have flashed a custom rom can fix the problem. idk if its safe to do
cicish said:
i've tried Lineage OS too and it also has reboot issue. i've checked a thread here https://forum.xda-developers.com/redmi-note-5-pro/development/derp-kernel-clang-4-4-138-t3804996 that flashing a different kernel when you have flashed a custom rom can fix the problem. idk if its safe to do
Click to expand...
Click to collapse
that thread is for redmi note 5 pro..and flashing different kernel probably won't solve it because I know few guys flashed genom kernel but still ended up with reboot in huaxing display. Maybe waiting for fix is better.