magisk - Nexus 7 (2013) Q&A

Is available for nexus 7 2013?

Using v16 here with no issues.

all43 said:
Using v16 here with no issues.
Click to expand...
Click to collapse
What version of twrp are u running? I tried to flash 16 but came up with an error

TWRP 3.2.1-0 bud

Running fine on mine, now. Had it working on my old flo. Couldn't get it to work on my deb previously, but SuperSU worked. Wiped and Magisk went in again.

Tried downloading again and now have two 3.2.1.0 installed too but just keep getting this error

acidspider said:
Tried downloading again and now have two 3.2.1.0 installed too but just keep getting this error
Click to expand...
Click to collapse
Do you have another super user installed? If this is the case, make sure you uninstall the other SU by doing a full unroot and return to the stock boot image before you flash Magisk.

I'm having problems with booting after installing lineageos with Gapps and addonsu.
I want to try magisk. But I am having some issues determining which method to use with Nexus 7 2013. The installation page of Magisk is so confusing.
Can someone enlighten me as to which method to use to install Magisk?

Related

Install ROOT and/or ROM on bone stock Nexus 7 running 6.0.1

So here is the deal. I'm not new to flashing and rooting and whatnot... I've been doing this for a while and I've never been stumped like this.
I just got a Nexus 7 for Christmas and after using it for all of 5 minutes, I realized that CM just has a lot of features that are just missing from the stock Nexus experience. I also want to get ROOT access. Now, like a complete moron, the first time I booted up my new tablet, I let it run through all the OTAs, so now I'm on 6.0.1.
From what I've read and what I've seen, things have changed quite a bit for Marshmallow. But here is where I'm at and hopefully someone can help me out.
I've unlocked the bootloader using ADB (so you can assume I know how to use ADB and fastboot on it own without any other toolkits)
I've downloaded TWRP, SuperSU and the latest nightly of CM13.
I used fastboot to flash TWRP and this is where things get crazy.
- First if I reboot after flashing TWRP and reboot back into recovery, TWRP is gone and stock recovery is restored.​- I believe that the OEM ROM is re-flashing my recovery at startup... no problem... flashing CM13 should fix that​- Second. If I flash TWRP, then boot into TWRP immediately without booting the ROM, TWRP doesn't recognize any of my partitions.​If I tell TWRP to reboot, it actually tells me that there is no ROM installed.​
So, that's where I'm stuck.
Do I flash TWRP, then just flash CM13 and SuperSU and like magic everything works? Is there a step I'm missing? Is there some special version of a zip I'm missing...
I've got downloaded right now:
TWRP: twrp-2.8.7.0-flo
CM13: cm-13.0-20151229-NIGHTLY-flo
GAPPS: open_gapps-arm-6.0-nano-20151225
SuperSU: UPDATE-SuperSU-v2.46
I was in a similar situation to you I managed to root my new nexus 7 with the Nexus Root Toolkit then had to use an app called flashify for installing TWRP hope this helps.
Figured it out. Turns out Google started using a new flash part in the Nexus 7 that I got. Using the MultiRom version of TWRP I was able to flash CM13.
Source:
http://forum.xda-developers.com/nexus-7-2013/nexus-7-2013-qa/mount-recovery-t3064562
i'm working on the same thing. did you have any luck installing open gapps? I'm getting an error system is out of space
cursixx said:
i'm working on the same thing. did you have any luck installing open gapps? I'm getting an error system is out of space
Click to expand...
Click to collapse
Yea I'm having the same issue, I flashed pure nexus and gapps with no issue, but when I tried to flash CM13, I got the "out of space" error when installing gapps
^Is the CM rom bigger? Maybe system is low on space.
Can you flash a smaller version of open gapps?
yosmokinman said:
^Is the CM rom bigger? Maybe system is low on space.
Can you flash a smaller version of open gapps?
Click to expand...
Click to collapse
yes I was able to flash the nano package
I flashed the Open GAPPS nano package right off the bat and I had no such problems. I prefer the minimum package anyways since I don't care about such apps as Google Newsstand and such. Anything I want, I just download off the Play store.
According to what I have read, you should have a custom kernel in order for you to root Marshmallow.

Lost Root

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

root with Magisk on Oreo.

I was trying to get help on Reddit but I wasn't able to get any help.
I was able to find the Twrp image to Boot into but Magisk isn't installing when I go to try to install it.
I'm using 13.4 for my pixel XL and I tried 13.3
Any ideas why they aren't working? No errors in Twrp when installing.
DudeThatsErin said:
I was trying to get help on Reddit but I wasn't able to get any help.
I was able to find the Twrp image to Boot into but Magisk isn't installing when I go to try to install it.
I'm using 13.4 for my pixel XL and I tried 13.3
Any ideas why they aren't working? No errors in Twrp when installing.
Click to expand...
Click to collapse
Hello,
Not sure if Magisk is even working on O but you would want to flash a kernel like ElementalX first or the modified stock. Flash the kernel, then Magisk but again I am not sure if it is actually working yet. If you do get it installed and working be sure to report back to all. Also if you had SU + SUhide prior then you will want to flash the Magisk remover first, then kernel then Magisk.
Cheers
jschill31 said:
Hello,
Not sure if Magisk is even working on O but you would want to flash a kernel like ElementalX first or the modified stock. Flash the kernel, then Magisk but again I am not sure if it is actually working yet. If you do get it installed and working be sure to report back to all. Also if you had SU + SUhide prior then you will want to flash the Magisk remover first, then kernel then Magisk.
Cheers
Click to expand...
Click to collapse
Yup. Just verified it doesn't work. I booted into twrp, installed ElementalX, then Magisk 13.4 and rebooted, still doesn't work.
Then I booted into twrp, installed ElementalX and Magisk 13.3 and rebooted. Nothing.
I also installed TWRP RC2 and it works fine. If you want I can upload the bootable image for twrp and RC2 that I used. At least now I have a way of testing it out (well, to keep testing it out, when I'm at work).
DudeThatsErin said:
Yup. Just verified it doesn't work. I booted into twrp, installed ElementalX, then Magisk 13.4 and rebooted, still doesn't work.
Then I booted into twrp, installed ElementalX and Magisk 13.3 and rebooted. Nothing.
I also installed TWRP RC2 and it works fine. If you want I can upload the bootable image for twrp and RC2 that I used. At least now I have a way of testing it out (well, to keep testing it out, when I'm at work).
Click to expand...
Click to collapse
So you have twrp installed with no issues?
humdrum2009 said:
So you have twrp installed with no issues?
Click to expand...
Click to collapse
Correct
I'm using a 6p with a pixel on the way. I had it working on the 6p with Oreo. I'm pretty sure I had to download an apk as well as flash the zip. Have you done this?
the pixel has a special magisk version because of boot a/b system stuff from my understanding. So it doesn't matter if it works on any other google phone.
It sucks too because i heavily rely on magisk due to how good it is on hiding...goodwin_c is my only hope. hanging on a thread here...
If you mention other root hiding methods just know that no...they all suck lol
j_mullet said:
I'm using a 6p with a pixel on the way. I had it working on the 6p with Oreo. I'm pretty sure I had to download an apk as well as flash the zip. Have you done this?
Click to expand...
Click to collapse
Zizzy2020 said:
the pixel has a special magisk version because of boot a/b system stuff from my understanding. So it doesn't matter if it works on any other google phone.
It sucks too because i heavily rely on magisk due to how good it is on hiding...goodwin_c is my only hope. hanging on a thread here...
If you mention other root hiding methods just know that no...they all suck lol
Click to expand...
Click to collapse
What Zizzy2020 said. It is annoying. I can't wait for the next magisk to be released.
Check out this post, it works like a charm.

Oreo and Magisk

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

Magisk needs to be installed after every reboot?

I've installed latest Magisk via TWRP. All works well until I reboot, then it's no longer installed. I need to go back into TWRP to install it again.
I'm on Pixel OS rom.
Any ideas?
boland said:
I've installed latest Magisk via TWRP. All works well until I reboot, then it's no longer installed. I need to go back into TWRP to install it again.
I'm on Pixel OS rom.
Any ideas?
Click to expand...
Click to collapse
Flash magisk v18.1 and it will work fine. Don't update Magisk. Some roms have this bug.
boland said:
I've installed latest Magisk via TWRP. All works well until I reboot, then it's no longer installed. I need to go back into TWRP to install it again.
I'm on Pixel OS rom.
Any ideas?
Click to expand...
Click to collapse
If you reboot it should reappear (it does for me).
I don't know what's the root cause, I'll just wait patiently for a fix. Unfortunately I don't have time to troubleshoot or provide logs to whoever to help the investigation.
PS: in your description be more accurate "latest version of xyz" means nothing. Specify exactly which version. Especially there is stable and beta!

Categories

Resources