Hello. Has anyone got Magisk to work? I've installed Magisk in recovery, downloaded Magisk manager, removed su completely. Also turned off debugging, But get safety net fail (cts profile mismatch).
So just wondering if anyone else has it working with z4 Tablet?
asjstian said:
Hello. Has anyone got Magisk to work? I've installed Magisk in recovery, downloaded Magisk manager, removed su completely. Also turned off debugging, But get safety net fail (cts profile mismatch).
So just wondering if anyone else has it working with z4 Tablet?
Click to expand...
Click to collapse
I am also trying to get Magisk to work. After flashing Magisk 12.0 it will boot and let me log in with pin code, but after about 10 seconds it will reboot itself. So you have Magisk 12 working without this reboot loop?
Yes it seems to work. No bootloops,
But as mentioned I can't pass safteynet, I guess it's not compitable with the Z4 tab.
Flashed latest version in recovery and downloaded Magisk manager from playstore.
Even 13.3 and some beta works:they install well, but no root...
Is anyone using Magisk on a stock ROM? The latest Magisk version I have got working is 12. Every version after 12 just gives me a bootloop. Has anyone come up with a solution for this?
Thanks!
asjstian said:
Hello. Has anyone got Magisk to work? I've installed Magisk in recovery, downloaded Magisk manager, removed su completely. Also turned off debugging, But get safety net fail (cts profile mismatch).
So just wondering if anyone else has it working with z4 Tablet?
Click to expand...
Click to collapse
I am having bootloop issues after flashing magisk (16.0)
Did you do any modification on the boot.img before flashing?
thanks in advance for you answer.
torben5247 said:
I am having bootloop issues after flashing magisk (16.0)
Did you do any modification on the boot.img before flashing?
thanks in advance for you answer.
Click to expand...
Click to collapse
Didn't make any modifications. Don't have magisk installed anymore.
Support for this amazing tablet is not so good anymore, so I'm thinking of selling it ?
asjstian said:
Didn't make any modifications. Don't have magisk installed anymore.
Support for this amazing tablet is not so good anymore, so I'm thinking of selling it
Click to expand...
Click to collapse
Thanks for you answer.
I have tried with clean stock boot.img.
Tried modfied kernel using ta_poc.
tried modified kernel using rootkernel tool. And it works with rootkernel saying yes to all modifications, but the touchscreen is not working....
I am trying to get magisk working on stock .154, the latest one.
Can you remember what stock version you got magisk working?
thanks in advance
FWIW: I have the latest LineageOS on my pollux_windy.
Magisk 16 works fine.
SafetyNet test:
ctsProfile false (I do not bother but have ideas how to fix it)
basicIntegrity true
torben5247 said:
Thanks for you answer.
I have tried with clean stock boot.img.
Tried modfied kernel using ta_poc.
tried modified kernel using rootkernel tool. And it works with rootkernel saying yes to all modifications, but the touchscreen is not working....
I am trying to get magisk working on stock .154, the latest one.
Can you remember what stock version you got magisk working?
thanks in advance
Click to expand...
Click to collapse
Have you tried modifying AndroPlusKernel? I want Magisk on rooted stock as well.
jelbo said:
Have you tried modifying AndroPlusKernel? I want Magisk on rooted stock as well.
Click to expand...
Click to collapse
I´ll never got stock firmware working with magisk.
i used rootkernel tool answered yes to the 2 first questions and no to the 2 last questions.
After that i flashed supersu.
That is the only way i got stock rooted.
I am using lineage os and that work with magisk.
torben5247 said:
I´ll never got stock firmware working with magisk.
i used rootkernel tool answered yes to the 2 first questions and no to the 2 last questions.
After that i flashed supersu.
That is the only way i got stock rooted.
I am using lineage os and that work with magisk.
Click to expand...
Click to collapse
Thanks for the info. I'm tempted to switch to LineageOS but for the battery drain when using WiFi. Is it still bad for you? It was fine for DHGE.
I am not sure to be honest what causes the heating.....
I have removed som apps.... And it is a little bit better, i think that macrodroid has caused some heating.
I still think that stock has less battery consumption when tablet is used.
But stock is much more battery consuming compaired to los when not in use.....
I love los, it is fast.
So maybe you should give it a go and see if you have the same experience as i have.
torben5247 said:
I am not sure to be honest what causes the heating.....
I have removed som apps.... And it is a little bit better, i think that macrodroid has caused some heating.
I still think that stock has less battery consumption when tablet is used.
But stock is much more battery consuming compaired to los when not in use.....
I love los, it is fast.
So maybe you should give it a go and see if you have the same experience as i have.
Click to expand...
Click to collapse
So, I have the same experience. Battery drain when in use is significantly higher that the stock ROM I was running: 32.2.A.0.305 (Android 6). That was the best one; the 32.4.A.1.54 Android 7 build was a big step back battery wise from what I've heard.
On topic: Magisk is running great on LineageOS, of course.
I have magisk installed on stock 32.4.A.1.54.
I prepared tk kernel using tapoc. After taht i disbaled RIC using rootkernel tool .
And i finally flashed this magisk.zip
https://forum.xda-developers.com/crossdevice-dev/sony/patched-magisk-v12-sony-devices-t3582331
And updated magisk.
Kind Regards
Torben5247
torben5247 said:
I have magisk installed on stock 32.4.A.1.54.
I prepared tk kernel using tapoc. After taht i disbaled RIC using rootkernel tool .
And i finally flashed this magisk.zip
https://forum.xda-developers.com/crossdevice-dev/sony/patched-magisk-v12-sony-devices-t3582331
And updated magisk.
Kind Regards
Torben5247
Click to expand...
Click to collapse
How's your battery life when using it and idle?
In idle it is the same as Los. 1% pr 14\16 hours. So i am happy ?
Please help me.After flashing Z4 tablet docomo, my tablet still on logo and blank screen .anybody know how to fix it. Which stock ROM can compatible for my my device. Thanks
Related
HI I've found tutorials on many websites (for example here : https://forum.xda-developers.com/honor-7/general/guide-beginners-how-to-root-update-fix-t3255452) to root the honor 7 but these tutorials are pretty old and I would like to know how to do it with the last version of android/emui (b370) because I've already bricked (and unbricked) my phone by following a 2016 tutorial wich is now outdated.
So right now I have TWRP installed and that would be nice if you could tell me what version of supersu I need to install.
PS : https://forum.xda-developers.com/honor-7/development/rom-6-0-x-yodarom-v1-0-mm-rooted-ads-t3338179
I found that guy using the same version as me but I don't want another kernel and everything I just want root.
(sorry for my poor english, I'm french)
Thanks in advance
I'd recommend flashing Yoda ROM but keeping everything stock except from root (when you flash it in twrp it gives you an options menu). I wouldn't recommend using the latest version of emui becuase it has worse battery life and the phone gets hotter than b370 the only advantage b380 have over b370 is the security patch.
0v3r cl0ck3d said:
I'd recommend flashing Yoda ROM but keeping everything stock except from root (when you flash it in twrp it gives you an options menu). I wouldn't recommend using the latest version of emui becuase it has worse battery life and the phone gets hotter than b370 the only advantage b380 have over b370 is the security patch.
Click to expand...
Click to collapse
Actually for now I don't see the b380 on the update app.
Yoda ROM is a pretty big file and I don't have a really good conexion
Do I need a custom boot/fixed boot (like in yoda rom) to be able to install Supersu ? or is there a flashable version of supersu that I can flash without fixed/custom boot ?
EDIT : are you sure that you can install only root and not everything with yoda rom? and is it erasing everything or not ?
Cordially,
Latest version of supersu is systemless and also disables or bypasses dm-verity check . So it should work fine.
Ps: dont forget to take a twrp backup .if anythings gets messedup u can restore the backup
gopinaidu77 said:
Latest version of supersu is systemless and also disables or bypasses dm-verity check . So it should work fine.
Ps: dont forget to take a twrp backup .if anythings gets messedup u can restore the backup
Click to expand...
Click to collapse
hi gopi ... i have an honor 7 which i want to root. i alerady tried to get bootloader code from dc unlocker as suggested by one of the members here but something's wrong and that driver doesn't even get installed. can you tell me (from the beginning), how to root my honor 7?
Hi, I recently flashed the newest B23 Oreo using EDL method, everything works perfect. But after flashing magisk 16.7, which worked well with ROM A2017X_V1.3.0B01_0_Universal, I'm having boot loop now.
Follow the guide on axon 7 forums.
You need boot.img,magisk 18 and custom module zip for magisk
You may want to try the latest canary build of Magisk. They've been fixing this issues lately. I don't think it will take all of the workarounds now.
I tried the 18.2 and debug release, still not work. Anything missing?
sean_han said:
I tried the 18.2 and debug release, still not work. Anything missing?
Click to expand...
Click to collapse
follow this https://forum.xda-developers.com/axon-7/development/kernel-magisk-17-stock-roms-t3856809
this works on b20 firmware and higher (b20-b23)
Yes, I am just reading this thread and download the two mods. Thank you!
Safety net is failing in stock miui rom 10.3.8.0
The phone is not rooted,no custom recovery installed, just a plain old stock miui rom
Any help, please??
thisisarjun said:
Safety net is failing in stock miui rom 10.3.8.0
The phone is not rooted,no custom recovery installed, just a plain old stock miui rom
Any help, please??
Click to expand...
Click to collapse
I have exactly the same problem. I have not flashed anything, i only unlocked bootloader
DaveCZ said:
I have exactly the same problem. I have not flashed anything, i only unlocked bootloader
Click to expand...
Click to collapse
U will have to flash magisk in order to pass safety net. That's the only way...
thisisarjun said:
U will have to flash magisk in order to pass safety net. That's the only way...
Click to expand...
Click to collapse
How's that the only way? What's the cause? Anyway can you kindly provide me with a guide on how to install magisk on MIUI 11 A9?
Thanks.
Can you please try with the latest/different version of Safety Net checker app?
I have come across many posts like these where a small bug in the app can cause it to show as "FAIL".
DaveCZ said:
How's that the only way? What's the cause? Anyway can you kindly provide me with a guide on how to install magisk on MIUI 11 A9?
Thanks.
Click to expand...
Click to collapse
Install twrp and then install magisk canary apk and then install the canary magisk version from the app...
thisisarjun said:
Install twrp and then install magisk canary apk and then install the canary magisk version from the app...
Click to expand...
Click to collapse
Does it necessary have to be Magisk Canary? Also which TWRP do you recommend? The official one from TWRP.me or some other.
PS: The installation of TWRP is through cmd with command „fastboot flash recovery *file_name*” right?
Thanks for your help and time
Hi,
I tried to install Magisk by first unlocking the bootloader, installing a custom recovery (TWRP) and later flashing Magisk. Unfortunately during the installation of TWRP I got hit with boot loop and used Sony's flash tool to get the stock ROM and get booted. But the ROM offered by flash tool is 6.01 (Marshmallow). Then I tried to install the latest Magisk 20.4 both by using TWRP and by using Magisk manager. But both resulted in the 'Unsupported/Unknown image format' error. These are the logs I see are:
- Device platform: arm64-v8a
- Copying image to cache
- Unpacking boot image
! Unsupported/Unknown image format
! Installation failed
Basically I want to:
1) Install Magisk
2) Upgrade from Marshmallow to the latest Android stock.
Any guidance is highly appreciated.
Thanks,
Karthik
Karthik.V.M said:
Hi,
I tried to install Magisk by first unlocking the bootloader, installing a custom recovery (TWRP) and later flashing Magisk. Unfortunately during the installation of TWRP I got hit with boot loop and used Sony's flash tool to get the stock ROM and get booted. But the ROM offered by flash tool is 6.01 (Marshmallow). Then I tried to install the latest Magisk 20.4 both by using TWRP and by using Magisk manager. But both resulted in the 'Unsupported/Unknown image format' error. These are the logs I see are:
- Device platform: arm64-v8a
- Copying image to cache
- Unpacking boot image
! Unsupported/Unknown image format
! Installation failed
Basically I want to:
1) Install Magisk
2) Upgrade from Marshmallow to the latest Android stock.
Any guidance is highly appreciated.
Thanks,
Karthik
Click to expand...
Click to collapse
Hi, first install the latest stock android rom and then flash magisk with twrp. Also you can try the stable versions, not canary.
Good luck, zaqm
zaqm said:
Hi, first install the latest stock android rom and then flash magisk with twrp. Also you can try the stable versions, not canary.
Good luck, zaqm
Click to expand...
Click to collapse
Hi Zaqm,
Thanks for your reply. I am a newbie in this whole process. Can you point me where can I get the latest stock android rom? Also should I use TWRP to install it? Your help is much appreciated. :good:
Regards,
Karthik
Karthik.V.M said:
Hi Zaqm,
Thanks for your reply. I am a newbie in this whole process. Can you point me where can I get the latest stock android rom? Also should I use TWRP to install it? Your help is much appreciated. :good:
Regards,
Karthik
Click to expand...
Click to collapse
Hi Zaqm,
I have managed to flash the latest stock android (8.0) using flashtool and xperifirm tool. When I tried to install magisk using TWRP on the latest stock android, I still get the same error message 'Unsupported/Unknown image format'. Any pointers are welcome.
Thanks,
Karthik
Karthik.V.M said:
Hi Zaqm,
I have managed to flash the latest stock android (8.0) using flashtool and xperifirm tool. When I tried to install magisk using TWRP on the latest stock android, I still get the same error message 'Unsupported/Unknown image format'. Any pointers are welcome.
Thanks,
Karthik
Click to expand...
Click to collapse
Hi, sorry for the late reply. Which magisk version did you try to flash? You can try v18 or 18.1 which I think are compatible with Android 8.
Good luck, zaqm
zaqm said:
Hi, sorry for the late reply. Which magisk version did you try to flash? You can try v18 or 18.1 which I think are compatible with Android 8.
Good luck, zaqm
Click to expand...
Click to collapse
HI Zaqm,
I tried the latest Magisk 20.4 and few other previous versions but I don't remember giving v18 or v18.1 a try. I will do that.
Also, I would like to share that I did not allow TWRP to modify the system partition. I opted to keep the system partition 'Read Only'. The reason I did this is that whenever I allow TWRP to modify the system partition, I get stuck at the SONY boot logo and my phone would not boot and I need to reflash the stock ROM again.
I also came to know that I need to flash a rooted kernel to avoid the bootloop or I should flash the drm fix if I want to keep the stock kernel. Can you comment on that?
Thanks,
Karthik
Karthik.V.M said:
HI Zaqm,
I tried the latest Magisk 20.4 and few other previous versions but I don't remember giving v18 or v18.1 a try. I will do that.
Also, I would like to share that I did not allow TWRP to modify the system partition. I opted to keep the system partition 'Read Only'. The reason I did this is that whenever I allow TWRP to modify the system partition, I get stuck at the SONY boot logo and my phone would not boot and I need to reflash the stock ROM again.
I also came to know that I need to flash a rooted kernel to avoid the bootloop or I should flash the drm fix if I want to keep the stock kernel. Can you comment on that?
Thanks,
Karthik
Click to expand...
Click to collapse
Hi, I'm sorry but I don't own myself a Xperia X and can't tell such specific things related to it. Let someone else answer these questions.
Good luck, zaqm
zaqm said:
Hi, I'm sorry but I don't own myself a Xperia X and can't tell such specific things related to it. Let someone else answer these questions.
Good luck, zaqm
Click to expand...
Click to collapse
Hi Zaqm,
Sorry for my delayed reply. I appreciate your pointers. I will update this thread with my findings. Will keep you posted.
Thanks,
Karthik
Karthik.V.M said:
Hi Zaqm,
Sorry for my delayed reply. I appreciate your pointers. I will update this thread with my findings. Will keep you posted.
Thanks,
Karthik
Click to expand...
Click to collapse
Hi, did you solve the error? i face the exactly same problem but mine is xperia sp.
same problem without solve
Hello! I've been trying to install a custom ROM on my SM-J400M for a while now and none worked, recently i tried installing Magisk on it and now it is in a bootloop . Is there any custom ROM compatible with my device? Or it is impossible to install a custom ROM on it? At the moment it seems like it is not even rootable...
Also the version of TWRP that i installed on my device says that it is an SM-J400F instead of a SM-J400M which is the actuall name of the model. Is that a problem? If so please tell me how to unistall it, i wasnt able to find any way to uninstal TWRP on a soft-bricked phone.
Thanks in Advance!
TheChadGamer said:
Hello! I've been trying to install a custom ROM on my SM-J400M for a while now and none worked, recently i tried installing Magisk on it and now it is in a bootloop . Is there any custom ROM compatible with my device? Or it is impossible to install a custom ROM on it? At the moment it seems like it is not even rootable...
Also the version of TWRP that i installed on my device says that it is an SM-J400F instead of a SM-J400M which is the actuall name of the model. Is that a problem? If so please tell me how to unistall it, i wasnt able to find any way to uninstal TWRP on a soft-bricked phone.
Thanks in Advance!
Click to expand...
Click to collapse
I've managed to un-brick my phone! Still found no way to install a custom ROM on it tho...
TheChadGamer said:
Hello! I've been trying to install a custom ROM on my SM-J400M for a while now and none worked, recently i tried installing Magisk on it and now it is in a bootloop . Is there any custom ROM compatible with my device? Or it is impossible to install a custom ROM on it? At the moment it seems like it is not even rootable...
Also the version of TWRP that i installed on my device says that it is an SM-J400F instead of a SM-J400M which is the actuall name of the model. Is that a problem? If so please tell me how to unistall it, i wasnt able to find any way to uninstal TWRP on a soft-bricked phone.
Thanks in Advance!
Click to expand...
Click to collapse
Is There Any Custom ROM for Samsung Galaxy J4?
YES!
Although, this is not specific Custom ROM for this device. This ROM is GSI (Generic System Image), and J4 is greatly support it! (Because it has Android Oreo out-of-box)
How to install it?
Easy, install TWRP from TwrpBuilder's Github, flash GSI Image as usual, flash magisk (if bootloop, flash this might help), and done!
Please note that this is GSI, bugs are widely open. But, as far as I use J4, the only bug I feel are Camera and MTP (fixed by using custom kernel)
Edit: For your TWRP, which version you install?
RedLine_27 said:
Is There Any Custom ROM for Samsung Galaxy J4?
YES!
Although, this is not specific Custom ROM for this device. This ROM is GSI (Generic System Image), and J4 is greatly support it! (Because it has Android Oreo out-of-box)
How to install it?
Easy, install TWRP from TwrpBuilder's Github, flash GSI Image as usual, flash magisk (if bootloop, flash this might help), and done!
Please note that this is GSI, bugs are widely open. But, as far as I use J4, the only bug I feel are Camera and MTP (fixed by using custom kernel)
Edit: For your TWRP, which version you install?
Click to expand...
Click to collapse
Thanks for the reply!
I recently discovered that my Samsung J4 is carrier locked so i don't think it is possible to flash a custom ROM in it...
I really tried many things since this post but in the end it would always get stuck in a boot loop and i would have to flash the official firmware in it to restore it.
What TWRP version did i use?
I honestly don't remember but it probably was a unofficial TWRP 3.2.3 or something similar, not sure if it was unofficial or not but it seemed to work...
Also, how would i go around getting a custom kernel to use on the device that would fix those problems?
Again, thanks for replying!
-TheChadGamer
TheChadGamer said:
Thanks for the reply!
I recently discovered that my Samsung J4 is carrier locked so i don't think it is possible to flash a custom ROM in it...
I really tried many things since this post but in the end it would always get stuck in a boot loop and i would have to flash the official firmware in it to restore it.
What TWRP version did i use?
I honestly don't remember but it probably was a unofficial TWRP 3.2.3 or something similar, not sure if it was unofficial or not but it seemed to work...
Also, how would i go around getting a custom kernel to use on the device that would fix those problems?
Again, thanks for replying!
-TheChadGamer
Click to expand...
Click to collapse
I use TWRP 3.2, and flashed MY builded custom kernel (Only for GSI!) https://forum.xda-developers.com/galaxy-j/development/kernel-redline-kernel-samsung-galaxy-j4-t4188199/
You need to update to Android 10 Stock then flash the A64 A/B GSI. And remember to flash dm verity disabler then flash Magisk. Magisk is important too.
For more info about this, feel free to join our telegram group : https://t.me/SamsungGalaxyJ4
In there we have detail instruction to flash GSI for J4. And other issue discussion
I can't write the steps here, because the steps is little complicated. Cheers!
Thank you for your help!
Soon i will be giving it another attempt then !
Sorry for taking so long, even the site had a upgrade!
I actually am using Linux now but i am dualbooting with Windows to be able to use Odin. I have just now entered the Telegram group,
NamaSayaHendra said:
In there we have detail instruction to flash GSI for J4.
Click to expand...
Click to collapse
Where can i find those instructions in the group? I have never used Telegram before so i don't know where to look for them