Related
I tried flashing magisk V7 and Phh's magisk root but the system says no root. I was on stock MM. I tried to search this forum but no results on Magisk.
Tikerz said:
I tried flashing magisk V7 and Phh's magisk root but the system says no root. I was on stock MM. I tried to search this forum but no results on Magisk.
Click to expand...
Click to collapse
The same goes for my honor 7, it fails at patching boot image, could not flash SuperSU even after that.
Flashed boot, Cust and system again, only then I could flash SuperSU again.
Guess our devices are not supported...
Sent from my PLK-L01 using XDA Labs
Magisk does work on honor 5x L24.
Sent from my KIW-L24 using Tapatalk
I tried magisk once and it worked, still don't remember what version
PalakMi said:
I tried magisk once and it worked, still don't remember what version
Click to expand...
Click to collapse
I tried Magisk 6 one month ago on Lollipop. Yesterday tried v7 with marshmallow and no luck
not working on marshmallow:crying:
GmorkLTE said:
I tried Magisk 6 one month ago on Lollipop. Yesterday tried v7 with marshmallow and no luck
Click to expand...
Click to collapse
Tried v7 also on MM, nothing
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
After i switched from miui 9 to pixel experience rom,
My phone was unrooted. I tried to root it again using super su and magisk, but it didn't work. Please help.?
Pranavsingal said:
After i switched from miui 9 to pixel experience rom,
My phone was unrooted. I tried to root it again using super su and magisk, but it didn't work. Please help.
Click to expand...
Click to collapse
SuperSU doesn't work anymore.
Update your recovery to one which is Treble compatible and use the latest beta version of Magisk.
It should all be explained in the Pixel Experience ROM thread
Can you give me the link to that thread.....
Try this recovery;it works for treble and non-treble roms so you wont bother changing recoveries again: (https://forum.xda-developers.com/re.../recovery-orangefox-recovery-project-t3775933)
And try this magisk for treble as well: (https://androidfilehost.com/?fid=890129502657597190)
Make a clean flash of your rom, first flash firmware if needed then rom then gapps. I would advice you to reboot after that setup your phone then reboot to recovery and flash magisk. Your choice good luck.
RapGodS said:
Try this recovery;it works for treble and non-treble roms so you wont bother changing recoveries again: (https://forum.xda-developers.com/re.../recovery-orangefox-recovery-project-t3775933)
And try this magisk for treble as well: (https://androidfilehost.com/?fid=890129502657597190)
Make a clean flash of your rom, first flash firmware if needed then rom then gapps. I would advice you to reboot after that setup your phone then reboot to recovery and flash magisk. Your choice good luck.
Click to expand...
Click to collapse
Thanks buddy...
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
Hi guys.
I'm on MIUI Global 12.5.1.0 RKIEUOR. Already unlocked the device and would like to root with Magisk, so I'm looking for boot.img to patch it with Magisk app, but the only rom version I can find to extract boot.img for 12.5.1.0 is RKIEUXM.
Would it matter if I use this one?
Why can't you just download twrp (I know it's in development but it works) and just flash magisk via it?
mejsi said:
Why can't you just download twrp (I know it's in development but it works) and just flash magisk via it?
Click to expand...
Click to collapse
Is there really a working twrp for renoir? Having trouble finding one that works for this phone.
Scroll down for it. It has a few issues but it works. I have rooted Mi 11 Lite 5g Touchscreen may not work for a few seconds but after that it works perfectly.
Rejerf said:
Is there really a working twrp for renoir? Having trouble finding one that works for this phone.
Click to expand...
Click to collapse
that's the last one who works correctly TWRP-3.5.2-renoir-Nebrassy
Rejerf said:
Hi guys.
I'm on MIUI Global 12.5.1.0 RKIEUOR. Already unlocked the device and would like to root with Magisk, so I'm looking for boot.img to patch it with Magisk app, but the only rom version I can find to extract boot.img for 12.5.1.0 is RKIEUXM.
Would it matter if I use this one?
Click to expand...
Click to collapse
My phone was is running an EMEA ROM, once the latest 12.5 update popped there was no archive version with .img files inside, so I downloaded the ROM for a different region (similar version, though), extracted the boot.img, patched it with Magisk and flashed it to the phone. Everything works fine, no issues.
ZeroCGTI said:
My phone was is running an EMEA ROM, once the latest 12.5 update popped there was no archive version with .img files inside, so I downloaded the ROM for a different region (similar version, though), extracted the boot.img, patched it with Magisk and flashed it to the phone. Everything works fine, no issues.
Click to expand...
Click to collapse
imo the easiest way is just booting twrp (not flashing) and install magisk
I need the boot patch image image please help
rayman95 said:
that's the last one who works correctly TWRP-3.5.2-renoir-Nebrassy
Click to expand...
Click to collapse
What's wrong with official 3.6.0?
Rejerf said:
Hi guys.
I'm on MIUI Global 12.5.1.0 RKIEUOR. Already unlocked the device and would like to root with Magisk, so I'm looking for boot.img to patch it with Magisk app, but the only rom version I can find to extract boot.img for 12.5.1.0 is RKIEUXM.
Would it matter if I use this one?
Click to expand...
Click to collapse
https://xiaomifirmwareupdater.com should have it.
By use of MIUI Downloader from Google Play, you can easily locate/download all kinds of stock (and Xiaomi eu) ROMs and TWRP for your Xiaomi device
testguest said:
What's wrong with official 3.6.0?
Click to expand...
Click to collapse
It was 3 months ago..3.6 was not created
rayman95 said:
It was 3 months ago..3.6 was not created
Click to expand...
Click to collapse
Download TWRP for renoir
Download TWRP Open Recovery for renoir
eu.dl.twrp.me
testguest said:
Download TWRP for renoir
Download TWRP Open Recovery for renoir
eu.dl.twrp.me
Click to expand...
Click to collapse
I know, why post you the link???
rayman95 said:
I know, why post you the link???
Click to expand...
Click to collapse
rayman95 said:
It was 3 months ago..3.6 was not created
Click to expand...
Click to collapse
22.1.5 doesn't work that way for me, by the way.
Neither with Magsik Stable/Beta, nor with Magisk Canary. Phone keeps ending in a bootloop. 21.12.29 was fine.
testguest said:
22.1.5 doesn't work that way for me, by the way.
Neither with Magsik Stable/Beta, nor with Magisk Canary. Phone keeps ending in a bootloop.
Click to expand...
Click to collapse
Sorry, I don't understand. You did root Xiaomi.eu 22.1.5 by flashing Magisk through TWRP 3.6, or by patching boot.img and flashing the patched img through Fastboot?
And by using Magisk Stable v23 or Canary 23016?
Or you tried but you got a bootloop?
In that case again, which Magisk version and by which method (TWRP or patching & flashing)?
zgfg said:
Sorry, I don't understand. You did root Xiaomi.eu 22.1.5 by flashing Magisk through TWRP 3.6, or by patching boot.img and flashing the patched img through Fastboot?
And by using Magisk Stable v23 or Canary 23016?
Or you tried but you got a bootloop?
In that case again, which Magisk version and by which method (TWRP or patching & flashing)?
Click to expand...
Click to collapse
Patched boot.img, as mentioned using Stable/Beta and Canary.
testguest said:
Patched boot.img, as mentioned using Stable/Beta and Canary.
Click to expand...
Click to collapse
Sorry I have no renoir yet - hence I could not test myself (asking while waiting for the phone)
With previous Weekly MIUI 13/A12 you were able to install Magisk (or this is now the first MIUI 13/A12 Xiaomi.eu Weekly)?
I.e, wondering if problem with rooting started with MIUI 13 and A12
PS: I see now also MIUI 13 Stable for renoir: xiaomi.eu_multi_MI11Lite5G_V13.0.4.0.SKICNXM_v13-12-fastboot.zip
Downloads for : -Android- Generic Device/Other | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
MIUI 13 - MIUI 13 STABLE RELEASE
Status: RELEASED RULES WHEN POSTING 1. If a ROM is not published DONT ASK ABOUT ITS ETA 2. If a ROM is not published DONT ASK why! 3. If a ROM is available, download it and use it 4. If a ROM has bugs, post the bug to the bug section if the BUG is not already listed 5. If you use any form of...
xiaomi.eu
zgfg said:
[...]
Click to expand...
Click to collapse
The previous one (21.12.29) also was A12.
I think I won't go stable for now.