I have a Samsung Galaxy S4 (verizon SCH-I545) running android 5.0.1
I have already rooted my device using KingRoot
I have been trying to flash the xposed zip file for several days now and I'm not having any luck. I've tried a few different tools to flash but they all kick me to bootloader but fail to flash the zip. I get the following error when bootloader is verifying the update package:
Code:
E:footer is wrong
E:signature verification failed
I've tried putting the zip file on my device and on SD to see if that might help, but still no dice. Does anyone have suggestions or know what I'm doing wrong? I'm using the most recent zip from XDA (xposed-v86-sdk21-arm.zip updated 08-Jul-2016 15:25... I've also tried arter97's package and dkcldark's package as well as Magisk v1)
Deleted
Anyone have any suggestions?
Bump
Someone has to have some sort of suggestions I could try... would flashing a custom rom on do anything or is this related to the KNOX security stuff?
Are you using twrp? if so, did you turn off zip verification and md5 verification?
Nergal di Cuthah said:
Are you using twrp? if so, did you turn off zip verification and md5 verification?
Click to expand...
Click to collapse
i am using twrp manager 9.0 (from the play store) but i didn't see a place/option to disable the verification. is there a different app i should be using or am i overlooking something obvious?
edit: I've also tried CWM and i get the same errors
lordofbeond said:
i am using twrp manager 9.0 (from the play store) but i didn't see a place/option to disable the verification. is there a different app i should be using or am i overlooking something obvious?
edit: I've also tried CWM and i get the same errors
Click to expand...
Click to collapse
Not in manager in actual twrp
Nergal di Cuthah said:
Not in manager in actual twrp
Click to expand...
Click to collapse
I wasn't aware of the install twrp step which answers most of the questions I have about this.
I tried it and softbricked my device. Did a little more research and it looks like the kernel I have won't allow me to install TWRP. I'm trying to use verizion's recovery tool to downgrade/repair the device and I'll see if I can get this device rolled back and TWRP installed.
Thank you for the info, this gives me a launching point at least. I'll check back here if/when I get TWRP installed and I try to disable the validation.
This thread is probably your answer
lordofbeond said:
I wasn't aware of the install twrp step which answers most of the questions I have about this.
I tried it and softbricked my device. Did a little more research and it looks like the kernel I have won't allow me to install TWRP. I'm trying to use verizion's recovery tool to downgrade/repair the device and I'll see if I can get this device rolled back and TWRP installed.
Thank you for the info, this gives me a launching point at least. I'll check back here if/when I get TWRP installed and I try to disable the validation.
Click to expand...
Click to collapse
http://forum.xda-developers.com/xposed/xposed-framework-install-galaxy-s4-sch-t3425615
lordofbeond said:
I have a Samsung Galaxy S4 (verizon SCH-I545) running android 5.0.1
I have already rooted my device using KingRoot
I have been trying to flash the xposed zip file for several days now and I'm not having any luck. I've tried a few different tools to flash but they all kick me to bootloader but fail to flash the zip. I get the following error when bootloader is verifying the update package:
I've tried putting the zip file on my device and on SD to see if that might help, but still no dice. Does anyone have suggestions or know what I'm doing wrong? I'm using the most recent zip from XDA (xposed-v86-sdk21-arm.zip updated 08-Jul-2016 15:25... I've also tried arter97's package and dkcldark's package as well as Magisk v1)
Click to expand...
Click to collapse
Hola. i just did this on vz GS4 i545:
use FlashFire for everything. make sure you have a titanium backup of your apps and data for after you flash new ROM. here are the steps:
1. Flash Fire Zip or OTA stock of1 deodexed ROM from here: http://forum.xda-developers.com/gal...1-keeproot-t3182544/post62413212#post62413212
it will spend 10 to 15 minutes on the red Verizon splash screen.
2. reload from titanium at this point.
3. install xposed 3.0alpha4.apk from the xposed forum page.
4. flashfire zip or ota Arter97's xposed v65 sdk21 arm arter97 V5 krait.zip
this last step took about 35 minutes to upgrade all 260 plus apps i have.
make sure you have the proper uninstaller loaded too just in case. i put mine on the ext sd card in case i needed to load it from recovery. though that might not work because of the unsigned issue.
Related
i have been downloading CM nightlys to my pc, copying them to my phone's internal storage, then flashing the zip using recovery (twerp v2.6.3.0) successfully for 3 or 4 months. I found CM Downloader app on the app store and down loaded that. I set the setting to automatically check for a new build, and download it. it did download the new builds although they failed to flash. 3 days after this started happening, CM came out with a 'snapshot' version. that one flashed ok. but the 'nighly' builds no longer flash. I have uninstalled CM downloader, and tried downloading them to the PC and copying them to the phone, that no longer works either. I have reinstalled CM downloader no change. so I think there is something changed on the phone that needs to be fixed, or reset or something. I appreciate any ideas here, I am still entry level skill level, so be gentle
blairman
TWERP failed flash message
blairan said:
i have been downloading CM nightlys to my pc, copying them to my phone's internal storage, then flashing the zip using recovery (twerp v2.6.3.0) successfully for 3 or 4 months. I found CM Downloader app on the app store and down loaded that. I set the setting to automatically check for a new build, and download it. it did download the new builds although they failed to flash. 3 days after this started happening, CM came out with a 'snapshot' version. that one flashed ok. but the 'nighly' builds no longer flash. I have uninstalled CM downloader, and tried downloading them to the PC and copying them to the phone, that no longer works either. I have reinstalled CM downloader no change. so I think there is something changed on the phone that needs to be fixed, or reset or something. I appreciate any ideas here, I am still entry level skill level, so be gentle
blairman
Click to expand...
Click to collapse
Updating partition details
Processing OpenRecoveryScript file
unable to locate zip file "/CyanogenRob_Downloa
E:Error installing zip file "/CyanogenRob_Downloa
Don processing script file
Installing ' /sdcar/CyanogenRob_Downloader/cm1
skipping MD5 check: no MD5 file found
E:Error executiong updater binary in ' /sdcar/CyanogenRob_Downloader/cm1
Error flashing zip ' /sdcar/CyanogenRob_Downloader/cm1
updating partition details
then under that in red letters "Failed'
blairan said:
Updating partition details
Processing OpenRecoveryScript file
unable to locate zip file "/CyanogenRob_Downloa
E:Error installing zip file "/CyanogenRob_Downloa
Don processing script file
Installing ' /sdcar/CyanogenRob_Downloader/cm1
skipping MD5 check: no MD5 file found
E:Error executiong updater binary in ' /sdcar/CyanogenRob_Downloader/cm1
Error flashing zip ' /sdcar/CyanogenRob_Downloader/cm1
updating partition details
then under that in red letters "Failed'
Click to expand...
Click to collapse
TWRP that works:
http://forum.xda-developers.com/showpost.php?p=50383573&postcount=3
Why (changelog):
http://forum.xda-developers.com/showpost.php?p=50383578&postcount=4
i'm part way there...
tdhite said:
TWRP that works:
http://forum.xda-developers.com/showpost.php?p=50383573&postcount=3
Why (changelog):
http://forum.xda-developers.com/showpost.php?p=50383578&postcount=4
Click to expand...
Click to collapse
OK, I have downloaded the 2 files. placed them in a directory near my root directory on my pc. placed the phone in fastboot usb, opened a command prompt window from that directory. typed in fastboot flash recovery openrecovery-m7wls-2.7.0.9-05-01-2014
and I get error: cannot load 'fastboot flash recovery openrecovery-m7wls-2.7.0.9-05-01-2014'
per a video showing how to flash recovery, I also tried the command adb reboot bootloader I get error : device not found
back to my pc, I open device manager, and I show a device labeled android device that is working properly.
stumped at this point.
is updating recovery the same as the initial install of a custom recovery?
do I need updated drivers for win 7? where are the latest? all videos say they are the latest, but that was when they were recorted.
thanks for help!
Yes u need updated drivers....any easy solution however is go and get the app flashify u will need root of course...it allows u to flash recovery that is on ur sd card. Just choose the img and flash recovery in the app then reboot into recovery and u will be good to go.
Sent from my HTCONE using Tapatalk
Thank you!
Thanks to both of you, updated TWERP did the trick and Flashify allowed me to install it without the fastboot, and PC hookup which was not working. Latest nightly installed, I am a happy camper!
Ok, let me get this straight, snag this Flashify, then snag TWRP 2.7.1.1, flash it with Flashify and I am golden????
(I am unlocked and S-Off running CM-11)
Slagathor01 said:
Ok, let me get this straight, snag this Flashify, then snag TWRP 2.7.1.1, flash it with Flashify and I am golden????
(I am unlocked and S-Off running CM-11)
Click to expand...
Click to collapse
All u have to do is update your recovery. So u can grab the latest TWRP and flash it any method u wish. Fastboot is best but flashify is the most convenient. After u flash your recovery the CM Rom should flash perfectly. Note: If u experience any failures in flashing any Rom that u know is good just downgrade your recovery via which ever method u prefer and that should flash fine now. You can always use the recovery zip floating around on the android development thread I'll see if I can find it for u.
Here u go bud http://forum.xda-developers.com/showthread.php?t=2656065
Note if the flash fails try a older zip until it works and flash the twrp by TD. Don't forget to thanks rootlinux for the zips. Might also want to keep the zips in handy on the phone storage incase the Note situation appears.
Sent from my HTCONE using Tapatalk
luigi311 said:
All u have to do is update your recovery. So u can grab the latest TWRP and flash it any method u wish. Fastboot is best but flashify is the most convenient. After u flash your recovery the CM Rom should flash perfectly. Note: If u experience any failures in flashing any Rom that u know is good just downgrade your recovery via which ever method u prefer and that should flash fine now. You can always use the recovery zip floating around on the android development thread I'll see if I can find it for u.
Here u go bud http://forum.xda-developers.com/showthread.php?t=2656065
Note if the flash fails try a older zip until it works and flash the twrp by TD. Don't forget to thanks rootlinux for the zips. Might also want to keep the zips in handy on the phone storage incase the Note situation appears.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
I got it with fastboot, I forgot I re installed windows since I did it initially, so I was pulling my hair out wondering why fastboot wouldnt see it, and I couldnt even get files to or from it till I installed HTC sync.....heh
thanks for the info.....
I managed to get TWRP 2.7.0.0 using AutoRec. I'm trying to get it upgraded to version 2.8.x.x but can't do it manually using adb or with TWRP manager, or any other methods.
I'm trying to install CM11 and it fails every time, from what I've read, I need a higher version of TWRP to achieve this without getting the error executing update binary in zip msg.
Anyone else running into this problem?
Verizon LG G2
VS98026A baseband
4.4.2 stock rom
EDIT: One thing I noticed, the only versions that show up as compatible using an app like TWRP Manager are the one's labeled with g2vzw
Example - The techerrata downloads for twrp
All the downloads that work are the g2vzw downloads. All the new downloads labeled vs980.zip won't work. I've tried renaming and still have the same problem.
centrix said:
I managed to get TWRP 2.7.0.0 using AutoRec. I'm trying to get it upgraded to version 2.8.x.x but can't do it manually using adb or with TWRP manager, or any other methods.
I'm trying to install CM11 and it fails every time, from what I've read, I need a higher version of TWRP to achieve this without getting the error executing update binary in zip msg.
Anyone else running into this problem?
Verizon LG G2
VS98026A baseband
4.4.2 stock rom
EDIT: One thing I noticed, the only versions that show up as compatible using an app like TWRP Manager are the one's labeled with g2vzw
Example - The techerrata downloads for twrp
All the downloads that work are the g2vzw downloads. All the new downloads labeled vs980.zip won't work. I've tried renaming and still have the same problem.
Click to expand...
Click to collapse
You should be able to flash the version posted here in recovery.
http://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705
mjones73 said:
You should be able to flash the version posted here in recovery.
http://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705
Click to expand...
Click to collapse
That did it, thanks!
Nightly build of CM11 still won't install, know anything about that?
centrix said:
That did it, thanks!
Nightly build of CM11 still won't install, know anything about that?
Click to expand...
Click to collapse
Nevermind, I forgot to wipe first. All is well.
Thanks again!
Hey all,
So I posted what I did to **** everything up the other day: https://forum.xda-developers.com/ta...ie-tried-to-root-device-t3655848?goto=newpost
I read about 70 different forums posts and concluded (somehow) that i needed to try and flash "twrp_3.1.0" for my T810. Well, for some reason it worked. I now have twrp on my boot-looped device.
Now, I'm trying to install a different recommendation which is the "SuperSU-v2.76" ROM through dragging it onto my tablet via My Computer (Since Odin refuses to load it)
Guess what? Ran into another problem when doing this. My T810 will no longer connect with my PC. It is stating "Device driver software was not successfully installed"... throwing out an error message MTP USB Device Failed.
I came up with the wise idea to simply put the SuperSU file on my brand new 128gb micro SD card. I found a USB adaptor for the card, plugged it into my PC and now My Computer is stating that the Micro SD card only has 1.67mb of space available. Did a bunch of research and found out that the USB adaptor actually has a limitor pre programmed into it so that you cannot adapt large SD cards..
I'm striking out guys. I need help. I'm able to navigate the twrp menu.. is there an option on this screen that will help me? I cannot think of what needs to be done next to get this Tab working....
also
.... yes I have the Samsung USB driver installed for my particular device....
So I ended up running to the store and I bought a 16gb micro SD. It worked, I was able to run the SuperSU-v2.76 flash on my device. Geuss what happened next?
Bootloop again.
Currently trying another suggestion which calls for restoring the tablet to an original OEM flash. Going to try installing the "5.0.2_T810XXU1AOG6_T810XAR1AOG6_XAR" flash and ill post what happens........
NOPE! No good. twrp does not recognize booting MD5 files.... I'm stuck again.
dyrewolv said:
Click to expand...
Click to collapse
You need to flash this version of SuperSU.
http://download.chainfire.eu/1122/SuperSU/SR3-SuperSU-v2.82-SR3-20170813133244.zip
ashyx said:
You need to flash this version of SuperSU.
http://download.chainfire.eu/1122/SuperSU/SR3-SuperSU-v2.82-SR3-20170813133244.zip
Click to expand...
Click to collapse
Hey ashyx,
How does that version of SuperSU differ from the one I just tried to flash?
What causes the tab to bootloop in the first place?
Thanks for your help!!
dyrewolv said:
Hey ashyx,
How does that version of SuperSU differ from the one I just tried to flash?
What causes the tab to bootloop in the first place?
Thanks for your help!!
Click to expand...
Click to collapse
Difficult to explain, but it should prevent the bootloop.
Samsung and Google's updates can break root, so new patched versions need to be released to overcome the issue.
You should consult the Supersu beta thread for the changelog.
ashyx said:
Difficult to explain, but it should prevent the bootloop.
Samsung and Google's updates can break root, so new patched versions need to be released to overcome the issue.
You should consult the Supersu beta thread for the changelog.
Click to expand...
Click to collapse
gotcha. I'm 100% brand-new to rooting. After I get SuperSU rooted onto my tab... Can I proceed with installing other custom ROMs?
What's the standard procedure for rooting/flashing devices from one ROM to the next?
I must be ****ing up bad because the last (4) ROM's I've tried have all bootlooped.
I did notice that I forgot to enable developers options when my tab was still OEM.. haven't been able to boot into a menu to change it though
dyrewolv said:
gotcha. I'm 100% brand-new to rooting. After I get SuperSU rooted onto my tab... Can I proceed with installing other custom ROMs?
What's the standard procedure for rooting/flashing devices from one ROM to the next?
I must be ****ing up bad because the last (4) ROM's I've tried have all bootlooped.
I did notice that I forgot to enable developers options when my tab was still OEM.. haven't been able to boot into a menu to change it though
Click to expand...
Click to collapse
You don't need root to be able flash custom roms but you must enable OEM UNLOCK in developer settings or you will encounter FRP Lock and won't be able to boot until you flash the stock firmware.
You will also need to patch dm-verity before installing anything custom. SuperSU and Magisk already do this or you can can flash my boot patch which also disables forced encryption.
ashyx said:
You don't need root to be able flash custom roms but you must enable OEM UNLOCK in developer settings or you will encounter FRP Lock and won't be able to boot until you flash the stock firmware.
You will also need to patch dm-verity before installing anything custom. SuperSU and Magisk already do this or you can can flash my boot patch which also disables forced encryption.
Click to expand...
Click to collapse
I tried flashing stock firmware in Odin via the file "5.0.2_T810XXU1AOG6_T810XAR1AOG6_XAR" which I found on the stock firmware forum for the T810. Odin failed during the flash...
If I get SuperSU working can I enable OEM UNLOCK?
What is dm-verity?
dyrewolv said:
I tried flashing stock firmware in Odin via the file "5.0.2_T810XXU1AOG6_T810XAR1AOG6_XAR" which I found on the stock firmware forum for the T810. Odin failed during the flash...
If I get SuperSU working can I enable OEM UNLOCK?
What is dm-verity?
Click to expand...
Click to collapse
I suggest you flash the latest Marshmallow or Nougat update.
Dm-verity is a security mechanism.
http://updato.com/firmware-archive-select-model?q=Sm-t810&exact=1
ashyx said:
I suggest you flash the latest Marshmallow or Nougat update.
Dm-verity is a security mechanism.
http://updato.com/firmware-archive-select-model?q=Sm-t810&exact=1
Click to expand...
Click to collapse
I'm confused. So I should continue with trying to get the correct version of SuperSU flashed first..right? Then figure out what I need; Marshmallow or Nougat? I haven't even got the tablet to get past the Samsung logo, I cannot enable OEM Unlock.. Last night when I tried flashing stuff Odin did not want to cooperate. I get a "FAIL! Complete (Write) operation failed" message. Tried to flash the stock ROM file I listed below with both re-partition unchecked and checked with no success.
dyrewolv said:
I'm confused. So I should continue with trying to get the correct version of SuperSU flashed first..right? Then figure out what I need; Marshmallow or Nougat? I haven't even got the tablet to get past the Samsung logo, I cannot enable OEM Unlock.. Last night when I tried flashing stuff Odin did not want to cooperate. I get a "FAIL! Complete (Write) operation failed" message. Tried to flash the stock ROM file I listed below with both re-partition unchecked and checked with no success.
Click to expand...
Click to collapse
It probably fails because you can't downgrade.
It's up to you to whether to flash MM or NN.
You will need to update first and then flash twrp and then supersu.
Why does it always say 'only official binaries are allowed to be flashed' after rebooting my rooted note 8(n950f/ds)
After installing twrp recovery and flashing magisk, rebooting the phone would always result in a bootloop with the error message (only official binaries are allowed to be flashed)
any solutions for this?
creastwell95 said:
Why does it always say 'only official binaries are allowed to be flashed' after rebooting my rooted note 8(n950f/ds)
After installing twrp recovery and flashing magisk, rebooting the phone would always result in a bootloop with the error message (only official binaries are allowed to be flashed)
any solutions for this?
Click to expand...
Click to collapse
You HAVE to delete "securitylogagent" in system/app on the first boot after flashing TWRP.
stonedpsycho said:
You HAVE to delete "securitylogagent" in system/app on the first boot after flashing TWRP.
Click to expand...
Click to collapse
I had the same problem, even after flashing the rmm fix. after wanting to install a module finish on reboot and flashing stock ROM. I believe that the rmm fix should always be used after installing something.
I do not think that deleting the security log agent makes a difference, that's why the Samsung root removal fix is anyway
cogelindo said:
I had the same problem, even after flashing the rmm fix. after wanting to install a module finish on reboot and flashing stock ROM. I believe that the rmm fix should always be used after installing something.
I do not think that deleting the security log agent makes a difference, that's why the Samsung root removal fix is anyway
Click to expand...
Click to collapse
Use this zip instead. You can get it link on dr.ketan' rooting guides
anwar amu said:
Use this zip instead. You can get it link on dr.ketan' rooting guides
Click to expand...
Click to collapse
Yes thank you, I have had it for a while and I already used it, but I still distrust having to restart for some reason. If I have to do it I turn it off and go to the recovery to flash that zip before restarting. The problem of official binaries has already happened to me before, and it is very uncomfortable ...
I used this to install lineage and it worked out great – the tablet runs a lot better. But I have an app I'd like to use that requires root, and this unofficial version of lineage does not come with a boot.img to patch with magisk. Is there some other way to root this that I'm missing, or is it not possible?
itscryptic said:
I used this to install lineage and it worked out great – the tablet runs a lot better. But I have an app I'd like to use that requires root, and this unofficial version of lineage does not come with a boot.img to patch with magisk. Is there some other way to root this that I'm missing, or is it not possible?
Click to expand...
Click to collapse
If you originally patched the Samsung firmware and rooted under OneUI, that same version of Magisk will show up once you flash any GSIs.
Besides that, there's no other way that I know of since you can't simply sideload Magisk through TWRP for this device
You'll have to start over by patching the firmware and flashing through Odin to get back to stock. From there, set up Magisk like you'd normally do. Once that's done, you can proceed and use the same guide to get LOS back and be fully rooted with Magisk
itscryptic said:
I used this to install lineage and it worked out great – the tablet runs a lot better. But I have an app I'd like to use that requires root, and this unofficial version of lineage does not come with a boot.img to patch with magisk. Is there some other way to root this that I'm missing, or is it not possible?
Click to expand...
Click to collapse
You just need to install the magisk apk and run it. There is no need to patch anything.
lewmur said:
You just need to install the magisk apk and run it. There is no need to patch anything.
Click to expand...
Click to collapse
I have the magisk apk installed, but not sure what you mean by run it. I open it and it shows N/A for installed.
itscryptic said:
I have the magisk apk installed, but not sure what you mean by run it. I open it and it shows N/A for installed.
Click to expand...
Click to collapse
Simply installing the Magisk APK is not the same. To install Magisk completely to your system you must patch the image.
For this device, you need to complete the patching process first with Samsung's firmware under OneUI. Once that's done, you can return back to LOS and a patched version of Magisk will be waiting for you to install
itscryptic said:
I have the magisk apk installed, but not sure what you mean by run it. I open it and it shows N/A for installed.
Click to expand...
Click to collapse
Yes, but with stock, your only option is to patch a file. But with LOS you also have the option to install direct. Choose that and it will root.
lewmur said:
Yes, but with stock, your only option is to patch a file. But with LOS you also have the option to install direct. Choose that and it will root.
Click to expand...
Click to collapse
I didn't root initially when installing LOS. So it appears I need to restart the process, which isn't that big of a deal. But I don't know how to get back to stock to perform the patch. It's been almost a year since I originally installed LOS so I'm a little rusty with how everything works again
itscryptic said:
I didn't root initially when installing LOS. So it appears I need to restart the process, which isn't that big of a deal. But I don't know how to get back to stock to perform the patch. It's been almost a year since I originally installed LOS so I'm a little rusty with how everything works again
Click to expand...
Click to collapse
Again!!!! There is no need for that. LOS has replaced stock. Just do as I said, run Magisk but instead of choosing a file, choose the DIRECT install option. LOS doesn't need to be patched and stock didn't need to be rooted before flashing LOS. I just happened that I did root stock first but that was just to test if it worked with the latest stock ROM. But there is no need to do it if you are going to flash a GSI.
lewmur said:
Again!!!! There is no need for that. LOS has replaced stock. Just do as I said, run Magisk but instead of choosing a file, choose the DIRECT install option. LOS doesn't need to be patched and stock didn't need to be rooted before flashing LOS. I just happened that I did root stock first but that was just to test if it worked with the latest stock ROM. But there is no need to do it if you are going to flash a GSI.
Click to expand...
Click to collapse
I do not see a direct option, it is only showing select a file to patch when I tap install...
itscryptic said:
I do not see a direct option, it is only showing select a file to patch when I tap install...
Click to expand...
Click to collapse
If you are only seeing "Select a file", something is wrong but it has nothing to do with needing to patch. Try uninstalling magisk and then flashing the apk with TWRP.
lewmur said:
If you are only seeing "Select a file", something is wrong but it has nothing to do with needing to patch. Try uninstalling magisk and then flashing the apk with TWRP.
Click to expand...
Click to collapse
That did the trick, thanks a bunch! I keep getting this message though, even after rebooting, and I'm not sure if it makes a difference since the root checker shows my device is rooted.
itscryptic said:
That did the trick, thanks a bunch! I keep getting this message though, even after rebooting, and I'm not sure if it makes a difference since the root checker shows my device is rooted.
Click to expand...
Click to collapse
That's normal. Ignore it.
itscryptic said:
That did the trick, thanks a bunch! I keep getting this message though, even after rebooting, and I'm not sure if it makes a difference since the root checker shows my device is rooted.
Click to expand...
Click to collapse
How did you flash the Magisk.apk with twrp?
gguman said:
How did you flash the Magisk.apk with twrp?
Click to expand...
Click to collapse
Use the "Install" button to flash as if it were a zip file.
lewmur said:
Use the "Install" button to flash as if it were a zip file.
Click to expand...
Click to collapse
I didn't find the apk file in the tablet when I push the Install button in the twrp... .Should the file be in a specific path?
gguman said:
I didn't find the apk file in the tablet when I push the Install button in the twrp... .Should the file be in a specific path?
Click to expand...
Click to collapse
So long as you know where it is, you should be able to browse to it. You might have to "Select storage" to switch between Internal and Micro SD. If it doesn't show, try renaming it from .apk to .zip.
gguman said:
I didn't find the apk file in the tablet when I push the Install button in the twrp... .Should the file be in a specific path?
Click to expand...
Click to collapse
You have to rename it as a ZIP, you cannot flash APK files
kevinco1 said:
You have to rename it as a ZIP, you cannot flash APK files
Click to expand...
Click to collapse
Not necessarily so. I've installed apk files in TWRP many times. It depends upon the version of TWRP. Some will, some won't. Most later versions will. I have v 3.7.0_12.2 on mine and it installs the apk just fine.
lewmur said:
Not necessarily so. I've installed apk files in TWRP many times. I depends upon the version of TWRP. Some will, some won't. Most later versions will. I have v 3.7.0_12.2 on mine and it installs the apk just fine.
Click to expand...
Click to collapse
Just curious, what other apps can you do this besides Magisk?
lewmur said:
Not necessarily so. I've installed apk files in TWRP many times. I depends upon the version of TWRP. Some will, some won't. Most later versions will. I have v 3.7.0_12.2 on mine and it installs the apk just fine.
Click to expand...
Click to collapse
Successfully installed apk:
0) stock firmware
1) install TWRP
2) Formated data
3) Wipe all data
4) adb push magisk.apk to /
5) Install apk from TWRP
6) reboot to fastboot
7) flash LOS20