So I flashed LineageOS on my Sony Xperia Tablet Z Wi-Fi and after flashing the os, opengapps and magisk I booted into the os and set everything up and installed some Magisk modules. After that I rebooted and then NFC started to crash around every second so I tried to disable NFC in Settings but when I tried that the system shut down and now it won't start, not to normal, recovery(TWRP) or fastboot mode. Screen black and none of the buttons do something, I can't even charge it. Any ideas how to fix this?
gamemaster2030 said:
So I flashed LineageOS on my Sony Xperia Tablet Z Wi-Fi and after flashing the os, opengapps and magisk I booted into the os and set everything up and installed some Magisk modules. After that I rebooted and then NFC started to crash around every second so I tried to disable NFC in Settings but when I tried that the system shut down and now it won't start, not to normal, recovery(TWRP) or fastboot mode. Screen black and none of the buttons do something, I can't even charge it. Any ideas how to fix this?
Click to expand...
Click to collapse
Stock nightlies of LOS have issue with Magisk and recovery. Furthermore magisk modules can break things. Reflash via fastboot, like usual.
Rootk1t said:
Stock nightlies of LOS have issue with Magisk and recovery. Furthermore magisk modules can break things. Reflash via fastboot, like usual.
Click to expand...
Click to collapse
If you read the post, you read that I couldn't boot to fastboot. But I can boot again, will reflash it.
Related
Hi,
android 7.1.1
Just installed TWRP 3.1.1-0. this works fine and I can still boot in TWRP.
After Installation the tablet worked,
but now I always stuck in the SONY XPERIA screen
I was about to install Magisk 19.3. That didn't work, so I tried different version which all failed. Somehow I pressed the button to delete cache/dalvik
With this, I think I did sthg wrong.
I have a backup for Xperia Companion and MyPhoneExplorer, but I can't get the software to recognize the device anymore.
Is there a way I can revive my tablet
What are my options to do?
any help is welcome,
thanks
siggel
finally I could flash SGP712_32.4.A.1.54_1295-4711_R1E.ftf with Xperia flashing Tool 0.9.26.0, so the thing is working.
But what did I wrong?
- deleting the cache within TWRP?
What am I supposed to do to get Magisk working?
As far as I read, I've to install a custom ROM, is it right?
Which one is preferrable?
And will the newest Magisk work with it?
Is there an "all I need to know about Z4 tablet thread"?
siggel said:
finally I could flash SGP712_32.4.A.1.54_1295-4711_R1E.ftf with Xperia flashing Tool 0.9.26.0, so the thing is working.
But what did I wrong?
- deleting the cache within TWRP?
What am I supposed to do to get Magisk working?
As far as I read, I've to install a custom ROM, is it right?
Which one is preferrable?
And will the newest Magisk work with it?
Is there an "all I need to know about Z4 tablet thread"?
Click to expand...
Click to collapse
Afaik Magisk requires LineageOS on this tablet. I'm running both successfully.
How do I have to install Magisk on the xperia z sgp311 tablet? Once I had managed to install MAgisk just by flashing Magisk.zip but it doesn't work anymore. I tried changing the name of magisk.apk to magisk.zip. It doesn't work either. didn't work either
novatosuper said:
How do I have to install Magisk on the xperia z sgp311 tablet? Once I had managed to install MAgisk just by flashing Magisk.zip but it doesn't work anymore. I tried changing the name of magisk.apk to magisk.zip. It doesn't work either. didn't work either
Click to expand...
Click to collapse
Hi, which TWRP version are you using ? Allowed system partition modification ?
install lineage os microg when I do it it returns twrp with more basic options I have tried flashing the latest twrp with lineage os microg but it doesn't boot the system and makes me flash lineage os microg again when I do it it modifies more basic twrp I don't know why that happens
novatosuper said:
How do I have to install Magisk on the xperia z sgp311 tablet?
Click to expand...
Click to collapse
Edit: what I wrote below is wrong. You're likely running into a Magisk 24.3 bug
-------------------------
This probably doesn't answer your question - but installing Magisk permanently may not be possible. My unscientific opinion (based on my recent experiences) is you may need to install everything in one shot - i.e. no reboot. I recently managed in install Lineage 15.1 from stock using twrp by:
rebooting into fastmode
installing twrp
rebooting into recovery (the one shot I had - if I rebooted at this stage, twrp would be gone! So avoid rebooting from here on out. )
Install lineage zip, then microg & any other packages you want
Reboot into lineage - twrp no longer available
I couldn't get twrp to stay installed even when I tried to install it to system, I figured that's because pollux_windy doesn't have a recovery partition. Also - I'm going off memory, so I may have gotten things wrong. However, it took me about 3 attempts to get things right (at times lineage wouldn't boot, IIRC, I may have forgotten to wipe the cache). I was following the steps in the wiki and used the following versions, accoding to my downloads folder:
twrp v3.6.1_9-0-pollux_windy.img
open_gapps-arm-8.1-nano20220215.zip
lineage-15.1-202000220-nightly-pollux_windy-signed.zip
sangnoir said:
Edit: what I wrote below is wrong. You're likely running into a Magisk 24.3 bug
-------------------------
Click to expand...
Click to collapse
Fixed in recently released v25.0.
Good evening dear members, I ask for your kind advice, as I have done something wrong to my Oneplus 5t.
I upgraded my Oneplus 5t with "lineage for microG" 19.1 (from lineage 18).
I had installed TWRP 3.5.0_9 (phone encrypted).
It booted fine the first time into system.
The problem arose after I tried to install Magisk 21.4 from TWRP.
Now the phone only boots in recovery, but it doesn't enter TWRP's menu. It stays on the first TWRP screen (where it shows the version number).
The good thing (I hope) is that I can enter fastboot mode.
I tried flashing TWRP again from fastboot to no avail.
I tried flashing boot.img from fastboot (taken from the original firmware), but still no luck.
Is there a way to install the original firmware from fastboot?
I think starting from scratch would be a step into the right direction.
Please give any suggestion which I fill follow to the letter.
Thank you, thank you, thank you!
You have to be decrypted or flash DMverity for A12. I assume You mean Magisk 24.1 the current version is 24.3
Hi. This is what I did:
I downloaded and installed original firmware through fastboot (fastboot was still on).
I also installed original recovery through fastboot.
After that my oneplus 5t was in stock condition, apart from the bootloader, which was unlocked.
After that I managed to install TWRP through fastboot, and then lineage 19.
The thing is that TWRP doesn't support lineage 19, for one reason or another. Or it could be the other way around (lineage 19 doesn't support TWRP). In any case I had a phone which would only go in fastboot mode.
At least I knew what to do, as I did it already: reinstall stock firmware and recovery.
Long story short, I installed LOS recovery and lineage 19, and everything works fine.
Thanks everyone, and especially thaidroid, for the support.
Have a nice day.
miclombardo said:
Good evening dear members, I ask for your kind advice, as I have done something wrong to my Oneplus 5t.
I upgraded my Oneplus 5t with "lineage for microG" 19.1 (from lineage 18).
I had installed TWRP 3.5.0_9 (phone encrypted).
It booted fine the first time into system.
The problem arose after I tried to install Magisk 21.4 from TWRP.
Now the phone only boots in recovery, but it doesn't enter TWRP's menu. It stays on the first TWRP screen (where it shows the version number).
The good thing (I hope) is that I can enter fastboot mode.
I tried flashing TWRP again from fastboot to no avail.
I tried flashing boot.img from fastboot (taken from the original firmware), but still no luck.
Is there a way to install the original firmware from fastboot?
I think starting from scratch would be a step into the right direction.
Please give any suggestion which I fill follow to the letter.
Thank you, thank you, thank you!
Click to expand...
Click to collapse
Its not working cus you need to format data in recovery and then reboot it.
kirknado18 said:
Its not working cus you need to format data in recovery and then reboot it.
Click to expand...
Click to collapse
It wont boot cus your encrypted formatting data will allow op5t to boot.
latest lineage + magisk = stuck on boot logo, I tried an older version of lineage + magisk (known to work), same thing.. what did I do?
paradoxiumwind said:
latest lineage + magisk = stuck on boot logo, I tried an older version of lineage + magisk (known to work), same thing.. what did I do?
Click to expand...
Click to collapse
What recovery are you on? TWRP?
I use the one posted alongside each version: https://download.lineageos.org/dumpling
can you help?
I need to root so I can titanium backup everything. but I can't root. I suspect I might need to fully format and wipe and start again, I tried wiping data and doing a fresh install, but after sideloading magisk it just fails to boot every time now.
Does it boot regularly BEFORE installing magisk? I am trying to define the source of the problem.
I have installed lineage 19 and magisk, and I confirm you that it's possible
Yes. It boots fine if I just install lineage then nevermindthegapps. problem only occurs if I flash magisk. I tried installing the .apk and patching the .boot image manually in it and then fastboot flashing that, but same thing.
oh - one possible thing that it may be - is that I had a couple of modules loaded (I think a gcam fix mod and something similar) in magisk, and I read somewhere about people having them stuck 'installed' despite demoving all traces of magisk app. whether that is the problem I don't know.
This is very strange. That's what I did:
Sideload lineage recovery
Sideload lineage 19
Download magisk apk
Patched boot image from lineage 19.zip
Sideload the patched boot image
And that's it it all worked
May I suggest you to start all over again?
is wiping system data sufficient or do I need to format it? I'd rather not lose my appdata- but I can't rescue it without root / titanium backup :/
Try first without formatting, and see how it goes
I wiped system/cache, installed lineage-19.1-20220719-nightly-dumpling-signed.zip / mindthegapps, phone booted up fine - rebooted fine.
ok, good. Now download latest magisk app and patch the boot img.
do I click patch vbmeta in image?
Yes.
First extract the file called boot.img from lineage.zip you just installed.
Then in magisk select "patch vbmeta in image".
Magisk should produce a file named something like " magisk_pached-24300_f41h3.img".
That patched file should be sideloaded.
Installation is explained really well by topjohnwu
it wouldn't flash without selecting vbmeta, so tried with, flashed it, now i'm sitting looking at the boot logo.
I got bootloop after Magisk update.
Device is:
Samsung Tab S7 T870, Android 11, Unlocked Bootloader, Without TWRP
I can get into recovery mode. There's a green text Set warranty bit kernel being showed briefly before everything, then proceeds to Samsung Logo.
What now? I really don't wanna lose my photos and work files
[update]
Can't sideload magisk since it's Samsung stock recovery won't allow it
Thanks!
Test to disable the magisk modules. https://forum.xda-developers.com/t/...les-without-magisk-and-twrp-recovery.4394991/
Maybe a module problem
joke19 said:
Test to disable the magisk modules. https://forum.xda-developers.com/t/...les-without-magisk-and-twrp-recovery.4394991/
Maybe a module problem
Click to expand...
Click to collapse
Thanks! Sadly adb can only be used in recovery mode, and only for sideload. Also can't sideload Magisk since, apparently, Samsung stock recovery won't let me.
I was running stock MIUI with root and TWRP recovery. After flashing the Pixel Experience Android 11 ROM, I didn't flash TWRP again. I tried many attempts (I haven't mentioned everything here to keep the post shorter) to install TWRP again, and I managed to do it successfully once. However, now when I boot into TWRP and select the A partition, it can't decrypt with my password and reboots the system, always opening the bootloader. When selecting the B partition, if I format the data and flash Magisk, it opens up the system (it opens the bootloader without flashing Magisk). But after booting into the system, if I boot TWRP again and reboot into the system without doing anything, my settings app and Bluetooth stop working. Then I have to boot into TWRP again, format the data, and flash Magisk again to boot the system normally. I can't install any Magisk modules either. However, the root is working.
Do you have any suggestions on what I can do?"
AhmedRadowan25 said:
Do you have any suggestions on what I can do?
Click to expand...
Click to collapse
flash stock miui according to your region with mi flash (don't lock the bootloader!)
this generally solves any problem and you can go back to custom roms after booting into miui.
Anyway , i recommend you to use the recovery provided with the rom itself as twrp can give issues sometimes.
AhmedRadowan25 said:
I was running stock MIUI with root and TWRP recovery. After flashing the Pixel Experience Android 11 ROM, I didn't flash TWRP again. I tried many attempts (I haven't mentioned everything here to keep the post shorter) to install TWRP again, and I managed to do it successfully once. However, now when I boot into TWRP and select the A partition, it can't decrypt with my password and reboots the system, always opening the bootloader. When selecting the B partition, if I format the data and flash Magisk, it opens up the system (it opens the bootloader without flashing Magisk). But after booting into the system, if I boot TWRP again and reboot into the system without doing anything, my settings app and Bluetooth stop working. Then I have to boot into TWRP again, format the data, and flash Magisk again to boot the system normally. I can't install any Magisk modules either. However, the root is working.
Do you have any suggestions on what I can do?"
Click to expand...
Click to collapse
Here's a complete explanation what I have done:
Initially, I was running stock MIUI with root access and TWRP recovery. However, I decided to switch to the Pixel Experience ROM. I downloaded the Pixel Experience Android 11 version and flashed it directly from TWRP since I didn't have access to a PC at that time. I only flashed the ROM file and didn't install the Pixel Experience recovery image, assuming that my TWRP would remain intact. But when I rebooted into recovery after the ROM installation, it booted into the Pixel Experience recovery instead. I couldn't find an option to flash the recovery image, only an option to apply an update through ADB sideload.
Fortunately, I managed to use a friend's computer and installed all the necessary ADB and Fastboot drivers. The computer could detect my phone in ADB sideload mode, but when I tried to boot into the bootloader, the PC couldn't detect my phone. Despite multiple attempts of booting into the Pixel Experience recovery and enabling ADB sideload, the PC couldn't recognize the fastboot mode. Strangely, every time I booted into the bootloader, my phone automatically powered off after displaying the Redmi logo. Holding the power button didn't help as it consistently powered off after showing the logo, without accessing the bootloader or recovery mode. I was afraid my phone had become completely unresponsive.
After numerous attempts, my phone unexpectedly booted into the bootloader again. This time, I connected my phone to another device using BugJagger, which successfully detected my phone. I used the command "fastboot flash recovery twrp.img" followed by "fastboot boot twrp.img" to open TWRP. However, I couldn't decrypt it using my password. I then flashed TWRP again and tried to boot into the system, but it always reverted back to the bootloader. I went back into recovery, selected partitions A to B, and flashed Magisk ZIP, DM variety ZIP, and LazyFlasher ZIP (without fully understanding their purpose).
Finally, my phone successfully booted into the system. However, upon rebooting into TWRP and then rebooting the system without any changes, my settings app and bluetooth stoped working. To resolve this, I had to boot into TWRP once again, format the data, and flash Magisk to restore normal operation.
alonsoj636MW said:
flash stock miui according to your region with mi flash (don't lock the bootloader!)
this generally solves any problem and you can go back to custom roms after booting into miui.
Anyway , i recommend you to use the recovery provided with the rom itself as twrp can give issues sometimes.
Click to expand...
Click to collapse
yes i am also thinking that it is the only solution.But I have tampered almost everything of my phone.Will flash stock miui rom can solve all problem?I have writen everything what i have done details in reply.you can read it if you want.
AhmedRadowan25 said:
yes i am also thinking that it is the only solution.But I have tampered almost everything of my phone.Will flash stock miui rom can solve all problem?I have writen everything what i have done details in reply.you can read it if you want.
Click to expand...
Click to collapse
yes i think you messed up with your phone for real. there was a lot of things that was incorrect.
don't mess with the slots and don't flash things you don't know about... you can ask here if you have doubts...
follow my advice and reflash stock miui with miflash to start from 0
and don't do all those things again... once you are done with miui... just tell what do you want to do and we'll guide you properly
alonsoj636MW said:
yes i think you messed up with your phone for real. there was a lot of things that was incorrect.
don't mess with the slots and don't flash things you don't know about... you can ask here if you have doubts...
follow my advice and reflash stock miui with miflash to start from 0
and don't do all those things again... once you are done with miui... just tell what do you want to do and we'll guide you properly
Click to expand...
Click to collapse
alonsoj636MW said:
yes i think you messed up with your phone for real. there was a lot of things that was incorrect.
don't mess with the slots and don't flash things you don't know about... you can ask here if you have doubts...
follow my advice and reflash stock miui with to start from 0
and don't do all those things again... once you are done with miui... just tell what do you want to do and we'll guide you properly
Click to expand...
Click to collapse
Thank you very much.Flashing miui will solve all probem?what do you think?
AhmedRadowan25 said:
what do you think?
Click to expand...
Click to collapse
it should
at least when i mess up with my phone flashing stock fixes all problems
Hi mate! Did you resoved the problem? What about the rom? All good?
gabsvm1 said:
Hi mate! Did you resoved the problem? What about the rom? All good?
Click to expand...
Click to collapse
No.I am running pixel experience 11 rom with these problems.No problem will appear untill i boot into recovery.Sorry i can't check and tell you that if 13 rom's recovery can flash 11 rom.
AhmedRadowan25 said:
No.I am running pixel experience 11 rom with these problems.No problem will appear untill i boot into recovery.Sorry i can't check and tell you that if 13 rom's recovery can flash 11 rom.
Click to expand...
Click to collapse
No problem mate, besides that everything is working good? You have tried a13 roms before?
gabsvm1 said:
No problem mate, besides that everything is working good? You have tried a13 roms before?
Click to expand...
Click to collapse
No
Who told you to flash DM Verity and Lazy Flasher
We don't need these things in our device
Don't mess up with Active Slot
If you try to change your Active slot into Inactive slot, once you Reboot to system, you will go straight to fastboot
You need Android Bootloader Interface to detect your phone in bootloader and ADB Composite to detect your phone in ADB, such as : Google USB Driver r13
Why you don't ask before doing anything, we have global community chat in telegram, for sure, we will help you in possible way
I assume you need back to stock rom to fix this issue
hit me on tele t.me/super_img