I used the xposed armv74 zip to install. It gives me an error "No space left on device" when I tried to flash it. After that it went into bootloop. I installed stock lollipop back LY48YM. Any help how to install it?
TIA
Chotu90 said:
I used the xposed armv74 zip to install. It gives me an error "No space left on device" when I tried to flash it. After that it went into bootloop. I installed stock lollipop back LY48YM. Any help how to install it?
TIA
Click to expand...
Click to collapse
If that was the only error, it is simple to solve. It means that your system partition does not have sufficient space. So uninstall some unimportant Google stuff like maps, news stand, books etc and then install Xposed. Afterwards you can install the uninstalled Google Apps from Play Store, if you want.
Also check that you are installing the correct version of Xposed, SDK21 vs SDK22.
Im trying to install xposed too but it throws an error stating arm version is not compatible. Im on lollipop stock rom and kernel with root and unlocked bootloader.
Sent from my Nexus 4
My N7 originally is nonrooted with 5.1.1. wifi only and factory reset
Yesterday i used "WugFresh Nexus Root Toolkit NRT_v2.0.5" to unlock the bootloader, root and flash Dmitry Grinbergthe's "grouper-M-TWRP_v1.1.zip" (http://forum.xda-developers.com/nexus-7/development/rom-aosp-6-0-grouper-t3225584). Everything seems okay and it restarted and shows Android 6. Then i installed Gapp.zip it stuck at "Android starts, Optimizing app xx/xx" windows and finally got "Set up wizard stops" error when reboot. I tried two different Gapp zip files: "working-marshmallow-gapps.zip" and "benzo-gapps-M-20151011-signed-chroma-r3.zip" both got the same error. I have to restored it without Google apps.
Please help me to eliminate the error and install Google apps to the custom rom.
Thank you very much !!
SLo
Hello!
I have spent around 5-6 hours tonight fixing my phone. Before it had CM13 working just fine but my recovery didn't work (got an error when trying to enter recovery). I manged to solve that problem by doing lots of things I have already forgotten about now and to be honest I didn't really have any idea what I was doing as I am very new to this and have no knowledge about it.
Right now my CM13 works just fine. No problems booting. My recovery works just fine. I have CAF bootstack and the latest TWRP recovery that was mentioned in the guide. However, my SuperSU doesn't want to work properly. At first, I had to download the SuperSu app from Play Store. I don't know if that's how it is supposed to be. When I start the app it says "The SU binary needs to be updated. Continue?". I press Continue and it says "If you have a custom recovery like TWRP or CWM, that can be used to (try to) install the SU binary. This is recommended for HTC devices. How would you like to install the SU binary?". I have two options: "NORMAL" and "TWRP/CWM". If I press "NORMAL" it proceeds to installing and the circle is spinning and spinning... "Installing, please wait..." After about 30 seconds it says "Installation failed! Please reboot and try again". Rebooting and trying again doesn't help. If I try the TWRP/CWM option it reboots me into TWRP Recovery but nothing happens there. If I reboot system from recovery the problem remains. I googled a bit and found some thread where they said I needed to download some SuperSU zip-file and install it from recovery. I did that but that just broke it even more giving me some error saying SuperSu wasn't installed at all, or something like that. I ended up re-rooting the device and installing bootstack, CM, and GAPPS again.
I have enabled root access in the CM developer options menu, for both apps and ADB. I have downloaded Root Checker and it says i am rooted. In download mode it also says rooted.
Is there some step I have missed? Please help me. I just want CM13, Recovery, and SuperSU to all be working at the same time. Not just pick two, like I have done before.
I had the same problem on my d802. That thing you did in development settings worked for me. Is supersu so neccesary?
Has anyone been able to get magisk to work appropriately? I attempted and the magisk apk kept fc'ing. I read about LG devices needing a boot.img "bump". Is this true or has anyone got it working in their own way?
There Is no root method for variants that don't have a unlocked bootloader. You would know this if you read the forums before asking
Sent from my VS995 using Tapatalk
mrtruckincowboy said:
There Is no root method for variants that don't have a unlocked bootloader. You would know this if you read the forums before asking
Click to expand...
Click to collapse
So, quite frankly, if you read, another user has it working. Further more, with the TMO variant, I do have an unlocked bootloader. Root application works with magisk, however the APK itself fc's.
I thought cowboys were polite ; )
I misread your post thought you were the typical person asking for a update on root I apologize.
Sent from my VS995 using Tapatalk
Thats what you get for not reading posts Cowboy... Smh...
I have the H918/tmo and I was able to get magisk running with phh's superuser. I'm kinda iffy on magisk-hide, as i had issues with it initially ( random reboots with it enabled). I turned off magisk hide for about a week, then turned it back on last night with no reboots since.. but haven't tested it with apps.
After running the easy recowvery + root script, i got rid of SuperSU. I believe all i did was a Full Unroot in the options, with no changes to the recovery. (I also may have done a format /data when rebooting to recovery again, but i dont recall fully, so take that into consideration if it didnt work at first (followed by the no-verity-opt-encrypt zip).)
After getting rid of SuperSU/su binary, what i remember doing was:
1 ) Flash magisk v9.zip -> reboot to system to make sure it boots, then adb reboot recovery.
2 ) Flash phh's superuser r266-2.zip -> reboot to system
3 ) install magisk manager via apk, and phh's superuser via playstore.
4 ) test out root.
has anyone been able to get Phh's superuser to work on the Sprint v20 / LS997 ?? If so, how? Thanks in advance.
If you can't get this working there is an app called RootSwitch. It can successfully hide root on the V20 with a toggle.
HiddenKnight said:
Has anyone been able to get magisk to work appropriately? I attempted and the magisk apk kept fc'ing. I read about LG devices needing a boot.img "bump". Is this true or has anyone got it working in their own way?
Click to expand...
Click to collapse
ive got 1 working and 1 in testing that uses magisk and phh.
the phh superuser seems to be casusing the systemui to force close often when in hide mode and the random reboots and loss of service, otherwise it was working fine.
but yeah, just flash version 10.2 on your current rom and see what happens!
btw this was on DEC sec patch, on oct builds i never tried it, but this is latest DEC sofware, didnt even use rootswitch
slayerh4x said:
If you can't get this working there is an app called RootSwitch. It can successfully hide root on the V20 with a toggle.
Click to expand...
Click to collapse
Is this the App you used?
https://forum.xda-developers.com/android/apps-games/play-pokemon-root-switch-method-patched-t3483179
remix435 said:
Is this the App you used?
https://forum.xda-developers.com/android/apps-games/play-pokemon-root-switch-method-patched-t3483179
Click to expand...
Click to collapse
I am using the one from this rom thread;
https://forum.xda-developers.com/v20/development/h819-nrd90m-modded-stock-rom-t3503658
Just follow the directions in the OP and you'll be g2g.
slayerh4x said:
If you can't get this working there is an app called RootSwitch. It can successfully hide root on the V20 with a toggle.
Click to expand...
Click to collapse
Tried RootSwitch w/ SuperSU. Didn't pass SafetyNet if that's what you were referring to.
Tried it again last night. Had the 1st 3 options turned on. Soon as I opened Android Pay my phone hot booted and got stuck on the VZW splash screen. Had to pull the battery. Won't try that again with supersu.
I have a VS995 this is how I got my phone to finally take magisk and pass the safetynet check. I'm running software version VS99513A I performed dirty santa to get unlocked bootloader and root access. Now I tried to uninstall supersu threw the app and I got a failed message. I tried going into recovery and flashing the supersu unistaller and that would fail. I tried flash magisk v12.0 and keep getting error message. I got stock in twrp recovery several times and used LGUP and flash either VS99512A KDZ or the VS99513A KDZ. Am not a developer but it seemed as if the boot.img won't take by the magisk zip. Those where my failed attempts for about a week or two. Now on to the success story
Performed Dirty Santa on software version VS99513A. I decide to flash modstock kernaI update v1.1 because it seem to work well with a stock rooted VS995. I flashed busy box in recovery and downloaded the app and also downloaded quick reboot so I could reboot into recovery easier. After reading @poixninja thread on modstock kernal - stocked with goodies he mention flash a boot.img that was patched with magisk. So I but the phone into fastboot mode and flashed his boot.img onto the phone with cmd (command prompt). I think I might have tried to uninstall supersu threw the app and I think it didn't work after flash the boot.img. So I put the phone into recovery mode the to wipe and then to advance wipe and clear dalvik and cache. After that I went to install and flashed the supersu unistaller and it took. After flashing I wipe the cache that twrp ask after most flashes. I then rebooted into recovery to make sure my twrp was not affected because I had and issue with that in previous supersu unistaller attempts. Rebooted ito twrp recovery then rebooted into system. I think whenever I flashed the verzion logo stayed up longer than normal but the phone fully started up. I clicked on supersu and it said no root access. Turned of the phone and did the steps to get to recovery mode. Once in I first wiped dalvik and cache. Then I flashed magisk unistaller and it went threw with no issue. I wiped dalvik and cache then rebooted into recovery. After getting into recovery I rebooted to system.
Sidenote: I recommend after wiping supersu and flashing magisk unistaller. Once you boot up install magisk apk. I didn't install the apk until after I flashed the magisk v12.0 in recovery. I noticed when I reboot the magisk icon was on the phone but when I clicked it it said go to playstore to download. I had the magisk manager apk on my SD card so I just installed it. The install to longer than normal I think it was because I didn't install it prior to flash the zip in recovery. I didn't get a chance to verify it yet.
Once the phone boot and I installed the magisk app manager I open it up and got green checks for installed magisk v12 and properly rooted. I went to setting and turned on enable busy box, magisk hide, and systemless. But when I clicked safetynet I got cts mismatch. Did some research and read on other XDA magisk thread that it maybe because of custom roms, modified kernals and possible supersu somewhere on the system. The only root accessible apps I had installed during this process was busybox and quick reboot. I did notice the first time I ran quick reboot after getting magisk it did give it root access then it did after I opened it again.
I decide to uninstall quick reboot and busy box. I uninstalled both apps. I rebooted into recovery mode the manual way. First thing I did was wipe dalvik and cache. Then I flashed busy box uninstaller. When the flash was running I say in the command lines that it found supersu. Which I thought was odd so I also flashed supersu unistaller. I rebooted into recovery wipe dalvik and cache and flashed uninstall magisk. Then reboot into recovery. I ran busy box uninstaller one more time to see if it would pick up supersu again and the command lines did not mention it. I flashed back magisk v12.0 rebooted into recovery. Then rebooted into system
Opened magisk went to setting to turn on enable busy box, magisk hide and systemless. Check safetnet and failed I found a magisk XDA thread that talks about common issue. It said I had to check magisk core only mode. Once I did that he requested a reboot which I did. Once back up I first cleared in app manager under show system I cleared all data for google play store, google play service for instant app, google play services. I opened magisk clicked safetynet check and I passed it. I went to search for netflix in play store and it pop up I installed it and it working fine so far. I tried logging into snapchat and I got threw.
Hope this maybe help full to anyone having issues
https://forum.xda-developers.com/v20/development/kernel-modstock-kernel-stock-goodies-t3563887 (boot img and modstock v1.1)
https://forum.xda-developers.com/showpost.php?p=71154562&postcount=4 (Magisk common issues)
Easier than that...?
sentra10550 said:
I have a VS995 this is how I got my phone to finally take magisk and pass the safetynet check. I'm running software version VS99513A I performed dirty santa to get unlocked bootloader and root access...
...
...Hope this maybe help full to anyone having issues
Click to expand...
Click to collapse
If I may be so bold, I played around with the rooting process on mine (I have a VS995 on 13A, too), and found a much easier (and possibly cleaner?) way to do this. Of course, the way I'm about to suggest would require a full KDZ to stock and a factory reset...
Here's mine:
Follow this thread:
https://forum.xda-developers.com/v20/how-to/lgv20-vs995-verizon-aio-post-06-19-2017-t3624326
Note: For noobs: After step 13, it's a bit misleading, because it doesn't boot DIRECTLY into TWRP, but boots to the white-screen "stock" recovery. The trick is to tell it "Yes" to both reset prompts. (It doesn't actually reset your stuff.) After this, it will take you to the TWRP menu.
When you get to step 14E, DO NOT FLASH SuperSU!
Instead, flash the ReStock zip.
After flashing ReStock, follow step 14G, and then flash Magisk 13.3 (latest stable, haven't tested others) from here:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
I tried this out of order a couple of other times and ended up either having Magisk not following through with install, or developing issues installing certain apps. (Either getting a -504 error from Play Store, or having valid APKs reply that they were "corrupt" when directly installing.)
Of course, all of the stereotypical disclaimers apply-- YMMV, and I'm not responsible if you brick your device, yadda yadda...
No offense, intended, sentra10550. While I'm glad you managed to get things working, the directions were a bit convoluted and I hope my humble findings might help yourself, in the future(?), and any others that may have a VS995.
Good luck, everybody!
)O( NeoHiPPy )O(
Think I'll wait until an easier method comes out for the VS995 to run Magisk lol..
I was UNABLE to do full unroot on my V20 from SuperSu settings menu. It would say "uninstallation failed"
I tried running UPDATE-unSU.zip from TWRP and it did not help. Magisk keeps on complaining about modified boot file.
I am unlocking boot loader, trying to flash Magisk in TWRP instead of SuperSu as per DirtyStanta root method instructions.
I will also flash restock 1.3 right after to stop static and vibration issue.
If it works, ill update my post.
---------- Post added 21st February 2018 at 12:28 AM ---------- Previous post was 20th February 2018 at 11:48 PM ----------
Ok i got it working. It was easier then i thought it would be.
These are the steps i did the very first time i got into TWRP after bootloaded unlock process as per DirtySanta rooting instructions.
Entered TWRP
DID NOT format data>yes
Installed Restock1.3 and Magisk.zip
Wipe cache and dalvik. Says Failed to wipe Dalvik (dont know why but what ever)
Reboot.
Result: Asking for unlock password 9 attempts left. So i have to Format Data>Yes
Re-entered TWRP
Format Data>yes
Reboot.
Root works. No SuperSu needed.
Conclusion:
You have to format DATA not for the root to work, but to be able to get into the phone. If there was a way to bypass that, there would be no need to factory reset to root. Root method would not require you to wipe the phone.
How ever, some apps that i use still do not support systemless root. They fail to do their work such as removing system apps. I cant remove any of my system apps for some reasons. I get "failed" messageevery time.
I was told i need modules for Magisk, but i have yet understood what that even means.
Other apps that use root, work fine. Such as AdAway.org
Hi there! I'm having issues to update OTA, this is my scenario:
Phone came with Android 8.0.0 Oreo (OPR1.170623.026.V9.5.9.0.ODHMIFA) so I did the following
1. Installed TRWP, then Magisk.
2. Installed Xposed (systemless) (Magisk Module)
3. Profit.
All good till here, the problem came when I tried to do the May OTA, it gives me the "Installation Problem" in the first step. I have read over the forum but I cant decide what to do. First I tried the " Uninstall -> Restore Image" in Magisk, but FAILED, and then:
1. Uninstalled Xposed Module.
2. Via TRWP uninstalled Magisk.
3. Update Failed.
Root Check says I'm rootless
Xposed Installer says "Xposed Framework is not installed". But OTA still fails.
So by now I'm thinking that maybe I have to flash stock system image, but not sure about this, actually NOT SURE WHAT TO DO, I just want to be able to have root and Xposed systemless, and then when an OTA arrives uninstall everything, do the update, reinstall Root/Xposed, and be happy.
Any guidance for me? Will I be OK if I flash JUST and ONLY the system image (OPR1.170623.026.V9.5.9.0.ODHMIFA)? Or do I have to flash ALL the stock images? What are the best option for me right now? Basically I'm trying to avoid reinstall all the apps and customization already done.
TL,DR:
Installed root/Xposed.
Uninstalled following different options.
Tried to do OTA, failed.
Not sure what to do now, I want to do OTAs and have root/Xposed.
Thinking into flash stock system image.
Thanks in advance!
Unistal twrp
panjivegency said:
Unistal twrp
Click to expand...
Click to collapse
But why some people can do the OTAs without uninstalling TWRP? Anyways I'll try this. Thanks. :good: