-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Update 02/03/2015
This guide I posted is well out of date, there are other methods to follow now days.
Please use http://www.aftvnews.com/tag/guide/ as it is up to date and current.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Thanks to Geohot, we now have root access
1. A) Go to: http://towelroot.com/ and click the red button to download the APK:
or
1. B) Download from this MediaFire mirror I made: http://goo.gl/DQ6xXF
2. Download the Chainfire SU APK from the Playstore: http://apps.evozi.com/apk-downloader/?id=eu.chainfire.supersu
3. Sideload both APKs.
4. Run Towelroot, hit "Make it Ra1n" and then your FTV will reboot.
5. After reboot install SU and set default access to "Grant" in it's settings.
Setup SSH after SU install:
1. Download Busybox APK: http://apps.evozi.com/apk-downloader/?id=stericson.busybox
2. Download SSH Daemon APK: http://apps.evozi.com/apk-downloader/?id=web.oss.sshsftpDaemon
3. Sideload both APKs.
4. Configure SSH Daemon to your liking and to start on boot
5. SSH with username root and password abc123 (configurable in SSH Daemon)
How to disable the FireTV Updater :
1. Connect via ADB and type "su" (without quotes)
2. pm disable com.amazon.dcp
3. If done correctly it should say "Package com.amazon.dcp new state: disabled".
OR
1. Just disable the OTA portion (Thanks JPDeckers)
Code:
pm disable "com.amazon.dcp/.ota.OTAUpdateMessageHandler"
pm disable "com.amazon.dcp/.ota.OTAService"
pm disable "com.amazon.dcp/.ota.CheckForOTAUpdatesService"
pm disable "com.amazon.dcp/.ota.OTAStatusActivity"
pm disable "com.amazon.dcp/.ota.ResetOTAMessageHandler"
pm disable "com.amazon.dcp/.ota.OTAService$OTAWakeupReceiver"
pm disable "com.amazon.dcp/.ota.OTAService$OTADedupeReceiver"
pm disable "com.amazon.dcp/.ota.OTAService$OTAInstallNowReceiver"
2. If done correctly it should say "Package xxx.xxxxxx.xxx new state: disabled".
How to Enable installations from "Unknown Sources":
http://forum.xda-developers.com/showthread.php?t=2784173
Here are some guides with pictures and step by step instructions:
How to root the Amazon FireTV:
http://www.aftvnews.com/how-to-root-the-amazon-fire-tv/
How to block OTA updates to keep root:
http://www.aftvnews.com/how-to-block-ota-update-for-amazon-fire-tv-and-keep-root-access/
How to install the Google Play Store on the Amazon FireTV:
http://www.aftvnews.com/how-to-install-the-google-play-store-on-the-amazon-fire-tv/
How to mount external usb storage devices:
http://www.aftvnews.com/how-to-play-media-files-from-external-usb-storage-on-amazon-fire-tv/
How to run FireTV apps from an External USB Drive:
http://www.aftvnews.com/how-to-move-and-run-amazon-fire-tv-apps-from-an-external-usb-storage-drive/
How to manually upgrade/downgrade your Amazon FireTV:
http://forum.xda-developers.com/showthread.php?t=2796067
How to install ClockworkMod Custom Recovery on the Amazon Fire TV
http://www.aftvnews.com/how-to-insta...mazon-fire-tv/
How to install a Custom ROM Image on the Amazon Fire TV
http://www.aftvnews.com/how-to-insta...mazon-fire-tv/
How to update a Rooted Amazon Fire TV to the Latest Version Without Losing Root
http://www.aftvnews.com/how-to-updat...t-losing-root/
How to boot into recovery mode and fix a softbricked FireTV:
http://www.aftvnews.com/how-to-unbr...ry-mode-and-factory-reset-the-amazon-fire-tv/
Fix PS4 DualShock 4 button mapping on the Fire TV:
http://www.aftvnews.com/fix-ps4-dualshock-4-button-mapping-on-the-fire-tv/
How to trick Google Play Store into allowing All Apps
http://www.aftvnews.com/how-to-trick-google-play-store-into-allowing-all-apps/
How to connect a Wii Remote (Wiimote) to the Fire TV:
http://www.aftvnews.com/how-to-connect-a-wii-remote-wiimote-to-the-fire-tv/
How to setup a new Fire TV without blocking Root:
http://www.aftvnews.com/how-to-setup-a-new-fire-tv-without-blocking-root/
How to remove unwanted Home Screen Menu Items:
http://www.aftvnews.com/how-to-remove-unwanted-home-screen-menu-items/
How to setup Plex (and XBMC) for Surround Sound Audio:
http://www.aftvnews.com/how-to-setup-plex-and-xbmc-for-surround-sound-audio/
More to come....
Changelog:
21-09-2014 - Added more links to guides including how to flash custom recovery and pre-rooted images
13-09-2014 - Added more links to guides added Towelroot v3 to mirror.
28-07-2014 - Added more links to guides.
23-07-2014 - Updated links to new http://www.aftvnews.com/ site.
30-06-2014 - Added link to guide on booting to recovery mode and fixing a softbrick
26-06-2014 - Added link to guide on manually upgrade/downgrade to different firmware versions
24-06-2014 - Added mediafire mirror for towelroot apks
24-06-2014 - Added link to guide for running apps from external drive
22-06-2014 - Added link to guide for installing playstore on the FireTV
hell yeah
wavrunrx said:
wait, what ?! is this real
Click to expand...
Click to collapse
Yep.
FYI, you should probably link to the main site instead of deeplinking the APK, same goes for SuperSU, the official download can be found here: http://download.chainfire.eu/supersu
People can just pull the superuser.apk from the zip file.
Worked for me. Quick and easy.
Now what do I do with it? Can I install Google play now?
FISKER_Q said:
Yep.
FYI, you should probably link to the main site instead of deeplinking the APK, same goes for SuperSU, the official download can be found here: http://download.chainfire.eu/supersu
People can just pull the superuser.apk from the zip file.
Click to expand...
Click to collapse
holy crap amazing !
i was thinking root wait waiting till amazon releases the new update to thwart any last minute attempt for amazon to 'fix' it...
is this safe or like the other exploit?
The towel root link does not allow hotlinking,so you should just change it to the DOT com webpage.
Also,click the red-ish symbol on their page to download the tr apk.
retroben said:
The towel root link does not allow hotlinking,so you should just change it to the DOT com webpage.
Also,click the red-ish symbol on their page to download the tr apk.
Click to expand...
Click to collapse
Hi! I'm still a beginer, so .. can you explain how to change it to the DOT com webpage?
Thanks
Ninja'd!
Was DP for more attention.
How do we add the OTA links to Fire TV's HOSTS file for blocking the update?
Also,how do I ensure that root is working without having to install another app?
Edit:
I was talking about the OP with towelroot.
*Piccard facepalm*
By DOT com,I meant just the website by itself,and not linking to the apk directly.
I also now know root is working because seeder was granted lag reduction access.
Added some more info.
Hopefully now we will see in influx of custom launchers, removable of bloatware, overclock etc Today is a good day :highfive:
Amazing! I've been waiting for this.
Anywhere besides ebay where a Canadian can pick this up?
can edit that host file with your instructions
---------- Post added at 02:09 PM ---------- Previous post was at 02:01 PM ----------
USB Storage working download [root] StickMount 3.01
Rooted and took some pictures as proof installed Root Browser and made a change to hosts file.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is a guide with screenshots for anyone interested.
SSH to your device then run the following:
Code:
su
mount -o rw,remount /dev/block/platform/msm_sdcc.1/by-name/system /system
chmod +w /etc/hosts
vi /etc/hosts
127.0.0.1 firs-ta-g7g.amazon.com
127.0.0.1 amzdigitaldownloads.edgesuite.net
:wq!
mount -o ro,remount /dev/block/platform/msm_sdcc.1/by-name/system /system
reboot
This step can also be done through a gui, root browser lite or other such.[/QUOTE]
Editing hosts for me failed at chmod. Instead I side loaded root browser and modified the hosts file directly on the Fire TV.
Someone else posted in another thread that this will disable the FireTV updater:
Code:
su
pm disable com.amazon.dcp
I checked the amz site after undoing OpenDNS and setting my two router DNS' to Google's two servers.
After two attempts of loading my google bookmark,it errored on one and worked on two,so internet is fine.
I tried loading the amz page and it gave me an error instead of file not found,which must mean it worked from the hosts file!
I also did that adb shell function through terminal app directly on Fire TV as an extra measure.
Landmark!
We have root. Brilliant.
Next, Safestrap? Rom Slots? Stripped AOSP Rom?
We're on our way.
http://blog.hash-of-codes.com/downloads/safestrap/
Anybody willing to try the Amazon Kindle*versions?
Sent from my Galaxy Nexus using Tapatalk
FYI, to install APKs directly from your Fire TV without the sideloading nonsense, grab a SQLite editor and meander your way through Settings Storage/Settings/Global to change the value of "install_non_market_apps" from 0 to 1.
Related
THIS POST IS CLOSED, IT MOVED!
HERE
Thanks goes to: fi01 for finding the bug, Jcase for making the exploit, Moronig for modifying the exploit, slayer615 for making the original batch bundle.
Help please http://forum.xda-developers.com/showpost.php?p=47883338&postcount=41
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EniGmA1987 said:
http://forum.xda-developers.com/showpost.php?p=47883338&postcount=41
Click to expand...
Click to collapse
I have root. I'm on version 13.3.1.0 on my 7" HDX. If you follow the tutorial it should work. (It did for me) What version are you running?
Says 13.3.0.2_user_302075320. Installed on Monday Jul, 29th, 2013 5:01 PM
Just got the tablet today and have not updated anything at all. My tablet cant check for updates since before I turned it on I blacklisted the IP addresses from my router that Amazon uses to push updates to Kindles
Hurry, update to 13.3.1.0 before a newer update comes (or download the update here and for directions to manually install the update). Don't blacklist those IP's until you root it. Update first.
Once you get root you can configure iptables on the tablet to blacklist it but im testing this. I got root 2 hours ago. Once I get it working I'll post a tut.
But you need to be on version 13.3.1.0
Alright I am downloading it now on the tablet, but it seems to be taking a while so I doubt I will get a chance to try for root again tonight.
EniGmA1987 said:
Alright I am downloading it now on the tablet, but it seems to be taking a while so I doubt I will get a chance to try for root again tonight.
Click to expand...
Click to collapse
That's fine. It's a over 700mb. I will be downloading it too, for a backup if Amazon decides to take it down. Good luck!
Faznx92 said:
1: Download Minimal ADB and Fastboot and install it. here
2: Get the adb drivers and install. here
3: Download latest Busybox to your HDX and install it. (It will not run untill you have root, this is for later.)(I got it from 1mobile market here)
4: Download jcase/fi01 code here
5: Download Moronig redone code http://goo.gl/4gBmq5
6: Enable adb on the Kindle
7: Connect Kindle to computer
8: Goto Device Manager in Control Panel
9: Look for the unsupported adb device (if not found safely remove hardware the kindle on the taskbar)
10: Click the unsupported device and click update driver then point it to the android_winusb file in the driver install directory
11: Unpack the files, rename Moroning's file to exploit and copy to the Minimal ADB and Fastboot install base directory, copy jcase's code EXCEPT the exploit file there as well.
12: Run Minimal ADB and Fastboot, make sure your device is connect first
Code:
adb devices
If not listed go back to step 6
13: Copy and paste this into the cmd prompt. Ignore if it says it fails
Code:
adb push su /data/local/tmp/
adb push rootme.sh /data/local/tmp/
adb push exploit /data/local/tmp/
adb shell chmod 755 /data/local/tmp/rootme.sh
adb shell chmod 755 /data/local/tmp/exploit
adb shell /data/local/tmp/exploit -c "/data/local/tmp/rootme.sh"
At this point you should be rooted. You can now finish installing Busybox on your HDX. To check if you have root if your unsure type
Code:
adb shell
then type
Code:
su
If not, reply. Remember this is tested to work on my Kindle Fire HDX 7" 13.3.1.0
Notes:
If the Hdx is updated past this point Amazon may patch the exploit and so you loose root.
We need to start a thread on how to stop/block Amazon from pushing updates to the HDX.
Click to expand...
Click to collapse
Do we need a Superuser app installed after root is gained like SuperSu. Also is it possible to unroot using SuperSu script in the settings.
Android Cowboy said:
Do we need a Superuser app installed after root is gained like SuperSu. Also is it possible to unroot using SuperSu script in the settings.
Click to expand...
Click to collapse
Never tried it yet, but you should. You have full root access.
Faznx92 said:
Never tried it yet, but you should. You have full root access.
Click to expand...
Click to collapse
Have confirmed that SuperSu does work and it will also unroot using the option in the settings.
Android Cowboy said:
Have confirmed that SuperSu does work and it will also unroot using the option in the settings.
Click to expand...
Click to collapse
Yes sir. SuperSU is working. Spread the word lol. I got to get some shut eye. I downloaded supersu from 1mobile market.
Someone got the playstore to work?
Gesendet von meinem Nexus 4 mit Tapatalk
Android Cowboy said:
Do we need a Superuser app installed after root is gained like SuperSu. Also is it possible to unroot using SuperSu script in the settings.
Click to expand...
Click to collapse
If you don't install a superuser app, root will still work, but any app that requests it, gets it, and no notification.
Supersu works with that binary, but you can install superuser and let it update the su binary and it will work as well.
---------- Post added at 09:08 AM ---------- Previous post was at 09:04 AM ----------
cebulank said:
Someone got the playstore to work?
Gesendet von meinem Nexus 4 mit Tapatalk
Click to expand...
Click to collapse
Some people are claiming to have it working, but they won't share how they did it...
Moronig said:
If you don't install a superuser app, root will still work, but any app that requests it, gets it, and no notification.
Supersu works with that binary, but you can install superuser and let it update the su binary and it will work as well.
---------- Post added at 09:08 AM ---------- Previous post was at 09:04 AM ----------
Some people are claiming to have it working, but they won't share how they did it...
Click to expand...
Click to collapse
SuperSU works, busybox works, I got root, I will be running test soon.
-update Play store does not work
Google play services works
Can this tutorial be used to root the Kindle Fire HDX 8.9 too?
lanegan said:
Can this tutorial be used to root the Kindle Fire HDX 8.9 too?
Click to expand...
Click to collapse
I'm posting that soon(to this thread). I do not have one so I can't confirm it works. Check back here shortly.
-Update I have it posted on the main thread.
Questions about Amazon updates
Has anyone tried to see if you can block the OTA updates like the kindle fire hd.
Using ES File Explorer app, navigate to the /system/etc/security folder. Rename or move the otacerts.zip file.
-credit goes to androidcowboy
Thanks For the Root it works Great
fr09n said:
Has anyone tried to see if you can block the OTA updates like the kindle fire hd.
Using ES File Explorer app, navigate to the /system/etc/security folder. Rename or move the otacerts.zip file.
-credit goes to androidcowboy
Thanks For the Root it works Great
Click to expand...
Click to collapse
I'll try it out.
-UPDATE- I can't confirm if it works or not. Someone else needs to try this up to see if it stops updates.
I'm running iptables.
This worked for me once I updated to 13.3.1. Guess the bug is either not present in the older kernel or it is at a different memory address.
EniGmA1987 said:
This worked for me once I updated to 13.3.1. Guess the bug is either not present in the older kernel or it is at a different memory address.
Click to expand...
Click to collapse
Yah. I think that's what lead someone to port the 8.9" 14.3.1 hdx exploit to 7" 13.3.1
Guide: Getting Xposed RunningThis morning, I finally managed to get Xposed up and running on my Turbo. So I thought I'd write up a guide as to how!
What you'll need:
A paid copy of Mofo (obviously)
Either a modified system image containing Xposed already, or if you like, you can modify one yourself as described in this tutorial. I've already created a modified system image to include Xposed as well as Wifi Tethering and a modified hosts file for ad blocking.
The Xposed Installer apk
Xposed Installer needs to be installed on your phone
Terminal Emulator and ES File Explorer from the play store need to be installed on your phone
A rooted image flashed to your phone
Before flashing anything, this is what you need to do:
On your computer, find your de.robv.android.xposed.installer_v33_36570c.apk and rename it to be a .zip file.
Open this .zip file and extract /assets/XposedBridge.jar and, if you're modifying your own system image, extract /assets/arm/app_process_xposed_sdk16 as well.
Put XposedBridge.jar somewhere on your phone, I like to use the Downloads folder so I don't lose track of it later.
In ES File Explorer, navigate to /data (NOT SDCARD/DATA)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Make sure it doesn't say sdcard > data!
Create a folder called "xposed"
Long press the folder, select properties, and set permissions to 755
Set the owner of the folder to root and the group to shell
Move XposedBridge.jar into the xposed folder we just created.
Make the permissions of XposedBridge.jar 644
As before, make the owner root and the group shell.
Open the Xposed Installer app on your phone.
Open terminal emulator and type
Code:
ps | grep xposed
This will return a pattern like the following. Make a note of the first seven characters, as shown (the first is a lowercase u)
Return to /data/xposed
Create two new files: modules.list and modules.whitelist
Make the permissions on both files 644 as above
Set the owner to the seven characters we noted down earlier and the group to shell on both files
If you're flashing a pre-compiled image with Xposed, you're done here! Go ahead and flash, and enjoy!
If you're modifying your own system image, you've got some more work to do. Take app_process_xposed_sdk16 from the Xposed apk and rename it to app_process.
In your turbo system image, navigate to /bin/ and replace app_process with the one from Xposed Framework. Make sure its permissions are set to 755:
Code:
sudo chmod 755 /path/to/img/bin/app_process
Linux does not allow setting the group of a file to a nonexistent group, so on your pc you'll have to make a shell group:
Code:
sudo groupadd shell
Change the group of app_process to shell:
Code:
sudo chgrp shell /path/to/img/bin/app_process
You're ready to flash!
NOTE: If XposedBridge.jar reports problems, try setting installation mode in the Xposed installer app to recovery (flash manually) and hitting install, then reboot.
You're done! Xposed should show up as installed! Don't use any modules that require system write access, such as replacing system icons, but most modules (ie GravityBox) work fine without it.
Ekkoria said:
This morning, I finally managed to get Xposed up and running on my Turbo. So I thought I'd write up a guide as to how!
Click to expand...
Click to collapse
Gahhh I was working all day on getting Xposed baked in
Thanks for the write up! I'm finding modifying the image file and flashing it to be just as addictive if not more than flashing someones prebuilt roms on other devices. I never got into compiling android so this feels like a way to tinker on my own without jumping into the deep end of code.
ntxct said:
Gahhh I was working all day on getting Xposed baked in
Thanks for the write up! I'm finding modifying the image file and flashing it to be just as addictive if not more than flashing someones prebuilt roms on other devices. I never got into compiling android so this feels like a way to tinker on my own without jumping into the deep end of code.
Click to expand...
Click to collapse
Same here! When I finally opened Xposed Installer and saw it read the framework as installed, I've almost never been so excited about something Android.
i dont need it but its a great guide, easy, short and with pictures!
Does the phone need to be flashed with a rooted image, like that in the tutorial of how to modify system images? I can't write to /data, presumably because I don't have the rooted image flashed yet. Also my /data directory is empty.
I have a copy of mofo, and copies of the rooted system image and your already compiled system image. Is there something I am missing? Thank you in advance.
Thanks so much man, about to flash. Will let you know how it goes.
Ah damn, I actually just did a bit different process of installing Xposed on a image for myself, (which involved baking it into the rom that didn't have it) totally got it working and I've rebooted 3 times so far and everything sticks. Loving having battery percentage now! I can write a quick tutorial writing xposed files into a fresh rooted image via Virtualbox and such... Took me a few hours
It did not work for xposedbridge.jar
aven1357 said:
Does the phone need to be flashed with a rooted image, like that in the tutorial of how to modify system images? I can't write to /data, presumably because I don't have the rooted image flashed yet. Also my /data directory is empty.
I have a copy of mofo, and copies of the rooted system image and your already compiled system image. Is there something I am missing? Thank you in advance.
Click to expand...
Click to collapse
Yes, you will need to be rooted first to perform these actions. Apologies for not originally including this. OP updated
savagebunny said:
Ah damn, I actually just did a bit different process of installing Xposed on a image for myself, (which involved baking it into the rom that didn't have it) totally got it working and I've rebooted 3 times so far and everything sticks. Loving having battery percentage now! I can write a quick tutorial writing xposed files into a fresh rooted image via Virtualbox and such... Took me a few hours
Click to expand...
Click to collapse
Yes please do so. I'd be very interested.
Sent from my XT1254 using XDA Free mobile app
I am having trouble with es file explr it tells me the operation failed when trying to do anything I have root and I enabled root for ES it seemed to work on root browser fine (I reset my device and just installed es so far)
edit checked and the root enhancement options are greyed out?
After following directions for all files and then subsequent flashing of your pre-built image xposed installer still reports framework problem. I've gone back and double checked the user:group and perm masks and everything looks good. Any ideas what else I should check?
I am having same problem as u smokie
smokie75 said:
After following directions for all files and then subsequent flashing of your pre-built image xposed installer still reports framework problem. I've gone back and double checked the user:group and perm masks and everything looks good. Any ideas what else I should check?
Click to expand...
Click to collapse
What's reporting a problem? Is it XposedBridge.jar?
If so, try setting the installation mode to recovery (flash manually) and hitting install, then reboot.
Ekkoria said:
What's reporting a problem? Is it XposedBridge.jar?
If so, try setting the installation mode to recovery (flash manually) and hitting install, then reboot.
Click to expand...
Click to collapse
Thanks! That worked!
Thanks for this , works great , now we just need one with busybox preinstalled
Stuck at this point any help?[/ATTACH]
Ekkoria said:
What's reporting a problem? Is it XposedBridge.jar?
If so, try setting the installation mode to recovery (flash manually) and hitting install, then reboot.
Click to expand...
Click to collapse
so will doing this enable gravitybox to work on the turbo?
hmltnjrmy7 said:
Stuck at this point any help?[/ATTACH]
Click to expand...
Click to collapse
You should be able to foloow the instruction you quoted from that point. You should go back and check your permissions, ownership and group for the 4 files. first
Do the change in install mode to manual. Hit install and go to recovery
recovery should give you the dead droid an then reboot
Also don't worry if the group "shell" shows up as something else in app_proces
rayjr13 said:
You should be able to foloow the instruction you quoted from that point. You should go back and check your permissions, ownership and group for the 4 files. first
Do the change in install mode to manual. Hit install and go to recovery
recovery should give you the dead droid an then reboot
Also don't worry if the group "shell" shows up as something else in app_proces
Click to expand...
Click to collapse
Lol the dead droid freaked me out at first, but I'm so happy xposed finally works!!!
This method is not mine. Original thread is HERE. I am simply making it work for our Verizon LG x8.3 VK815.
With the introduction to the newer OTA update, rooting ability using the old method has been broken. This means we have to follow the new method for achieving root similar to the LG G4. This requires pulling the system image, injecting root, pushing the system image back to the device.
Here are the steps to Root your Verizon LG x8.3 VK815
Follow JUST the first step here to get setup with the Download Mode and send_command:
http://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586
It has links to the VERIZON drivers and the resources to get this done.
Here is the specifics for the LG VK815 to backup SYSTEM image:
STEP 1: BACKUP SYSTEM IMAGE said:
From Download Mode, using the send_command.exe
Code:
dd if=/dev/block/mmcblk0 bs=8192 skip=44992 count=458752 of=/data/media/0/system.img
Once that is done, we have to change permissions
Code:
mv /data/media/0/system.img /data/media/0/Download
Code:
chown media_rw:media_rw /data/media/0/Download/system.img
Code:
chmod 664 /data/media/0/Download/system.img
Code:
chcon "u:object_r:media_rw_data_file:s0" /data/media/0/Download/system.img
Type LEAVE to reboot back into Android. Open a ADB terminal and copy the System.img to your PC
Code:
adb pull /storage/sdcard0/Download/system.img .
Click to expand...
Click to collapse
STEP 2: INJECT ROOT (SKIP STEP IF VERSION ISN'T LISTED BELOW) said:
You need a Linux environment for this.
I used VirtualBox and this Ubuntu 12.10 Image:
http://sourceforge.net/projects/vir...untu Linux/12.10/ubuntu-12.10-desktop-i386.7z
user/pass: ubuntu/reverse
Load up Ubuntu and Log in. Download Inject Root Files. Copy system.img and contents of Inject_Root_G4.zip to desktop.
Load up a Terminal and "cd Desktop"
Code:
sudo chmod +x autoroot.sh
sudo ./autoroot.sh
Your "system.img" should change to "rootedsystem.img"
Copy this out of your VM and copy back to the root of your internal storage on your LG G Tab x8.3 VK815
Click to expand...
Click to collapse
I am uploading the 11A Stock OTA System Image Here:
StockSystem
Code:
MD5:cda4e8ce36f009403a45f00f29c58fff
Here is the ROOTED 11A OTA System Image:
Download Rooted System Image - Mirror
Code:
MD5: 165bc9152f20e66623477870c574500b
STEP 3: PUSH ROOTED SYSTEM IMAGE said:
Boot back into Download Mode. Now we copy and install the rootedsystem.img into our operating system partition:
Code:
dd if=/data/media/0/rootedsystem.img bs=8192 seek=44992 count=458752 of=/dev/block/mmcblk0
Type LEAVE and reboot.
Click to expand...
Click to collapse
ENJOY!
Special Thanks to @smason for help and @hackarchive for the original walkthrough!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Wrong device, wrong Forum.
Please ask in the Q and Forum for your device - thanks.
Yea the new update breaks the existing root methods. There currently is no way TO root, but I think we can root it similarly like we do on the G4.
You basically pull the system image (using the command I posted), open it up on the PC, copy in the root files, and push the whole root system image (3.5gb) back to the phone.
I would recommend doing a factory reset and do not sign in to google, install apps, etc. The tablet is 16gb and you'll have both images on your G4. You might not have enough internal storage space with apps installed.
I do not have the UPDATE installed, nor do I want the update unless I KNOW it can be rooted. So if you can pull the system image for me and upload it, I will try to inject the root and you can try it. You'll have BOTH system images on your tablet, so if the rooted one doesn't work, you can just flash the original.
Anyone on the OTA able to pull a stock system image to upload?
I have no intention of taking the OTA if it cannot be rooted. I will help anyone looking to root the new update.
player911 said:
Anyone on the OTA able to pull a stock system image to upload?
I have no intention of taking the OTA if it cannot be rooted. I will help anyone looking to root the new update.
Click to expand...
Click to collapse
Hi there, im now trying to root it using this method. If its right i would update my img :cyclops:
I am having problems copying the image off of the device. I tried doing it though adb pull and shell and just a straight copy. Keep getting permission errors. I rerooted my 11A tab to try permissions.
player911 said:
I am having problems copying the image off of the device. I tried doing it though adb pull and shell and just a straight copy. Keep getting permission errors. I rerooted my 11A tab to try permissions.
Click to expand...
Click to collapse
I have the same problem too, i can't move/copy the system.img. Any solutions of this?
Update to pull system.img
Code:
#mv /data/media/0/system.img /data/media/0/Download
#chown media_rw:media_rw /data/media/0/Download/system.img
#chmod 664 /data/media/0/Download/system.img
#chcon "u:object_r:media_rw_data_file:s0" /data/media/0/Download/system.img
#ls -laZ /data/media/0/Download/system.img
-rw------- media_rw media_rw u:object_r:media_rw_data_file:s0 system.img
#
Thanks to @smason for the help.
I have pulled the stock OTA system image, injected root, and about to flash it now. If successful, I will upload the rooted system.img.
The OP is sort of a mess right now while I am adding notes and steps. If I am successful, I will organize it better. The steps for flashing is 1 line
EDIT!
SUCCESS!
Another thread that should be stickied.
Agreed as this method will probably be the standard for all updates going forward unless LG blocks it.
Unlike the G4, additional steps need to be taken to get the image off your device because they locked down permissions.
I am interested in hearing of how this works for others. I've been all over this for a while and my instructions may skip details.
Is the link for the rooted system file broken?
Skizzy034 said:
Is the link for the rooted system file broken?
Click to expand...
Click to collapse
I confirm that the download link doesn't work for me. Like you said in the other thread, it just takes me to the site's main page.
roirraW "edor" ehT said:
I confirm that the download link doesn't work for me. Like you said in the other thread, it just takes me to the site's main page.
Click to expand...
Click to collapse
=/ That sucks.
This worked for me. I FINALLY got my x8.3 rooted. Uploading the rootedsystem.img file to FileDropper right now. Will share the link as soon as it is uploaded.
Edit:
FileDropper wouldn't hand over the link to the file so I'm uploading it to MediaFire now. Will post link as soon as it is uploaded.
Edit:
File is uploaded (Remove spaces): www . mediafire .com /download/ qnx4f9bzxage96o/ rootedsystem.img
Cool!
I'll update the OP links with your mirror.
Can you provide a MD5 checksum? I think I zipped the original to save file size so the MD5 will be different.
Looks like both of my links have died. I'll reupload the Original and Rooted images up to other services tonight. I was excited when I finally got it and threw it up on the first host that would support the size.
player911 said:
Cool!
I'll update the OP links with your mirror.
Can you provide a MD5 checksum? I think I zipped the original to save file size so the MD5 will be different.
Looks like both of my links have died. I'll reupload the Original and Rooted images up to other services tonight. I was excited when I finally got it and threw it up on the first host that would support the size.
Click to expand...
Click to collapse
I'd be glad to post the MD5... as soon as I figure out how to get that... I have no idea, never done that before. xD Normally I just wait for everyone else to fix things like this and I download their hard work but I decided it was time for me to step up to the plate.
EDIT:
I believe I got the MD5 for it. I used WinMD5Free v1.20 so I hope I'm not just being an idiot here (Never learn until you stick your neck out.)
MD5: 5e151c2126263423a1602fd39eb2db47
So the only step we need to do is push the system image you provided?
I would back up your system image too, but not needed.
You should just copy the rootedsystem.img to your internal storage and use the DD command from Download mode to copy it over.
player911 said:
I would back up your system image too, but not needed.
You should just copy the rootedsystem.img to your internal storage and use the DD command from Download mode to copy it over.
Click to expand...
Click to collapse
Will an android terminal work?
Marshmallow root has been much more difficult than simply flash a zip in recovery, because it also requires a modified boot image to work.
I've done all the work for you, this root is achieved with SELinux enforced using Chainfire's method.
The original RUU/Stock rom is here.
In this post you can find the followings:
Aroma Stock Rom
Root Info
GPE Marshmallow on All Models
Disable S-ON System Write Protection
Sweep to sleep module
FAQ
Aroma Stock Rom (All models support with selectable root)
Simplest way to dive in GPE Marshmallow, the installer will guide you to the right direction.
If you want root, take a look at the next section for some info about root methods.
Choose your model in the installer, it also includes proper support for Sprint and Verizon device,
This will NOT convert your device into GPE!! It only flashes a rom.
Aroma Version Stock GPE
Mega Link
Important!! If you choose systemless root, please choose "Do not install SuperSU" when reboot in TWRP, because TWRP isn't updated to detect this new method. If you choose to install SuperSU within TWRP you'll get stuck in boot loop.
Root Info
In Marshmallow, Chainfire gave us with two rooting methods include:
The traditional root in system, which breaks OTA functionality.
(It's more stable now)
New "systemless" approach, which means the root stuffs are only in DATA and BOOT, the system will stay intact and it will accept OTAs.
(Note that this method is still in beta stage according to CF)
If you already downloaded the GPE Marshmallow stock rom and you want root, this is where you'd be interested with.
(Non-GSM device should now jump to next section)
Choose your preferred root method above, and follow the correspond instructions below.
Instructions:
Traditional:
Flash m8-mmgpe-su-boot.zip in attachment with TWRP
Flash SuperSU 2.52
Systemless:
Be sure you haven't used any other root method(like the traditional one above), if you've rooted with other methods, please re-flash your system back to pure stock
Flash m8-mmgpe-su-boot-systemless.zip in attachment with TWRP
Download SuperSU-v2.56-20151030013730.zip in this thread, and flash it through TWRP
Important!! Please choose "Do not install SuperSU" when reboot in TWRP, because TWRP isn't updated to detect this new method. If you choose to install SuperSU within TWRP you'll get stuck in bootloop.
GPE Marshmallow on All Models
Not an International/GSM device and still want some Marshmallow love? This is where you'd be interested with.
Simplest way is flash the pre-packed rom above, but if you already downloaded the stock rom and don't want to re-download, then look below.
GPE MM on all models is possible because it uses the Sense all-model dtb image, thanks to sun_dream for his work!!
Choose your preferred root method above, and follow the correspond instructions below.
Instructions:
Traditional:
Flash m8_AIO-mmgpe-su-boot.zip in attachment with TWRP
Flash SuperSU 2.52
Systemless:
Be sure you haven't used any other root method(like the traditional one above), if you've rooted with other methods, please re-flash your system back to pure stock
Flash m8_AIO-mmgpe-su-boot-systemless.zip in attachment with TWRP
Download SuperSU-v2.56-20151030013730.zip in this thread, and flash it through TWRP
Important!! Please choose "Do not install SuperSU" when reboot in TWRP, because TWRP isn't updated to detect this new method. If you choose to install SuperSU within TWRP you'll get stuck in bootloop.
Disable S-ON System Write Protection
After you rooted, you might find out that your system partition is locked up, this is because of HTC's system write protection on S-ON devices, and here is a handy mod for you to bypass it. Original mod by flar2, I modified it to work on MM GPE.
Instructions:
You have to use the traditional root method above to make this work!!
Flash m8-mmgpe-wp_mod.zip in attachment
Sweep to Sleep module
A handy mod to turn of the screen by swiping the bottom of the screen. Original mod by flar2, I modified it to work on MM GPE.
Instructions:
This will flash files to system, there is no point in using systemless method, it ot should be OK
Flash m8-mmgpe-s2s_mod.zip in attachment
FAQ
Q: After choosing full wipe, my contents in internal storage are all gone!!
A: No, it's not. It's a new behavior of Marshmallow. After each clean flash, it will move all previous files in /sdcard into /sdcard/0. You can just move them back to the proper locations.
Q: I cannot install Busybox in system / I cannot use adaway !!
A: Flash wp_mod.
Q: I used systemless root and wanted to keep my system partition intact, how do I install Busybox?
A: Download Busybox Pro, type /su/bin as the installation path for busybox. You cannot do it using the free version, unfortunately.
Q: **** app cannot access external SDcard!!
A: Look at this explanation:
Since Kitkat(2 years ago man), we don't have direct external storage write permission. Google consider it insecure, so they implemented this feature. The reason why you can access external SDcard easily before is because most roms on XDA already contains a hack in /system/etc/permissions/platform.xml. You should not rely on this hack forever, please take a look below.
In lollipop and after, Google provided a much secure and better way to grant external storage access to third party apps, first of all take a look at this article for details:
http://www.androidpolice.com/2014/1...s-automatic-mediastore-and-improves-security/
So instead of using the old platform.xml hack in the old Kitkat days, adopt yourself with this new behavior of Android!! If a certain app cannot access SDcard, ASK THE DEVELOPER to add support for this API!!
Many apps already have support for this API. I'll take Titanium Backup for example, as lots of you cannot find the way to use it on externals SD. In Menu>>Preferences>>Backup Location, you can choose Document Provider on top of the detect button.
In the provider, open the menu on the top right corner and select "Show SDcard", then you'll see External Storage in the left side. Select external SDcard in the document provider and press the button on the bottom, the app will then be granted access to the whole external storage. You can then create a new folder in TiBack and select it as your backup location.
Other apps also follows the instructions above, you just have to manually set up the folder where the app can access, in the case which most of us would love to give access to the whole SDcard, I set the location to the root of external storage. Each app has independent permission, so you have to manually grant each app you wish to access external storage.
Q: I want OTA, what should I do?
A: Look at the following info
To accept OTA updates, you need the following:
Your MID should be 0P6B17000
Your CID should be GOOGL001
You have to fully convert to GPE
You have to keep system partition untouched
You have to have GPE stock recovery
So before anything, if you want to accept OTA, you have to change MID, CID, and convert to GPE. The tricky part is the system partition and the recovery. The easiest way is when the OTA comes, flash the stock rom again without root, flash GPE stock recovery through fastboot, then apply OTA. But if you like to go the hardcore way, here comes a tutorial:
fastboot flash systemless_boot.img
fastboot boot TWRP.img(so that you can use TWRP but you didn't actually flash it)
Flash systemless SuperSU
By doing so you can accept OTA at anytime.
Q: Are there any mods around?
A: Because of the difficulty of file based flashing, modded GPE MM might take a while to appear.
You can use Xposed Framework, as it now officially support Marshmallow.
http://forum.xda-developers.com/showthread.php?t=3034811
Credits:
@Chainfire for the new root methods and SuperSU
@flar2 for wp_mod.ko and s2s_mod.ko
@enewman17 for original RUU
@sun_dream for the all models dtb image
@whaevr for porting to Verizon
@Captain_Throwback for porting to Sprint
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Does this mean it will boot with a warning message?
Edit: My post was in response to the very first version of pre systemless Root for M8 GPE 6.0 .. But the Dev was fast in updating
Noonski said:
Does this mean it will boot with a warning message?
Click to expand...
Click to collapse
no message - just root like normal.
Requires s-off?
Updated thread with systemless root.
Noonski said:
Does this mean it will boot with a warning message?
Click to expand...
Click to collapse
No warning message.
popoyaya said:
Requires s-off?
Click to expand...
Click to collapse
S-ON is OK
Have you encounter any issue with systemless root?
Thanks
Could anyone check if they have HTC's motion launch working with this?
isx said:
Could anyone check if they have HTC's motion launch working with this?
Click to expand...
Click to collapse
I have all of them working... Swipe to unlock is disabled by default though.
nhoc_maruko9x said:
I have all of them working... Swipe to unlock is disabled by default though.
Click to expand...
Click to collapse
EDIT after a TWRP restore and re-flash its all working well.
Anybody lost ex-sd card after using the traditional method?
Sent from my HTC One_M8 using Tapatalk
tominozh said:
Anybody lost ex-sd card after using the traditional method?
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Nope, mine still works. I think you've got to go to storage and configure your sd card as removable storage.
---------- Post added at 10:20 PM ---------- Previous post was at 10:18 PM ----------
tominozh said:
Anybody lost ex-sd card after using the traditional method?
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
@topjohnwu the mod doesnt seem to be working.. v4a still keeps asking for drivers..
n1234d said:
Nope, mine still works. I think you've got to go to storage and configure your sd card as removable storage.
---------- Post added at 10:20 PM ---------- Previous post was at 10:18 PM ----------
@topjohnwu the mod doesnt seem to be working.. v4a still keeps asking for drivers..
Click to expand...
Click to collapse
Try copy a random file to system (or remove an system app you don't like) using root explorer and reboot and see if it sticks. I haven't used v4a for years, and I'm not sure if it is something about selinux or other possible reasons.
Also I'm not sure if the su.d script is executing correctly(because stock rom lack init.d support I tried su.d), try this also:
First reboot the device, before doing any modifications to system open terminal on the phone and type:
su
insmod /system/lib/modules/wp_mod.ko
then do the system modification tests.
Thanks a lot!!
topjohnwu said:
Try copy a random file to system (or remove an system app you don't like) using root explorer and reboot and see if it sticks. I haven't used v4a for years, and I'm not sure if it is something about selinux or other possible reasons.
Also I'm not sure if the su.d script is executing correctly(because stock rom lack init.d support I tried su.d), try this also:
First reboot the device, before doing any modifications to system open terminal on the phone and type:
su
insmod /system/lib/modules/wp_mod.ko
then do the system modification tests.
Thanks a lot!!
Click to expand...
Click to collapse
My bad, it does indeed work!! Adaway works, and so does deleting system apps! Thanks a lot
n1234d said:
My bad, it does indeed work!! Adaway works, and so does deleting system apps! Thanks a lot
Click to expand...
Click to collapse
Thanks for the confirmation.
Doing thing blindly without testing is always a challenge
I am loosing htc gestures like double tap to wake after sometime
Have to disable and then re enable it to get it working
Just posting to say that the Systemless Root method worked great for me. Able to successfully modify /System files and folders (verified changes were still there after reboot), restored some apps, Messages, and Call Log using Titanium, and Android Pay is still working after rooting.
Thanks JW!
Is there any way to flash TWRP without PC if you don't have root...??
Well, whatever I try, V4A keeps asking for drivers. I have selinux permissive (selinux mode changer app) and flashed the wp_mod from here. Adaway and other changes to the system partition stick. Any ideas?
Updated post with pre-rooted with aroma installer rom.
gauravbhawsar said:
Is there any way to flash TWRP without PC if you don't have root...??
Click to expand...
Click to collapse
Flashify. Play store.
Or, I have one you can just put on SD card and rename 0p6bimg. It's 2.8.7.0
600,000 unique entries, browse the web without distractions by using this consolidated hosts file.
Features
- Combines tons of sources including AdAway.
- Systemless so you can block ads while using Android Pay
- Looks like a small zip but the hosts file is 18mb, a couple times the size of AdAway's.
- No app required.
- Update by typing hosts in terminal, no root required.
- 600,000 unique entries.
- 4 different hosts options
- Faster blockage time by changing the redirecting to 0.0.0.0 instead of localhost like AdAway
- Four hosts options, can also be combined
1. Master = Ad & Malware block
2. Gambling = Gambling block
3. Pornography = Pornography block
4. Social = Social Media block
How to use 'hosts' terminal program
1. Type 'su' then type 'hosts'.
2. When selecting an option, you can combine multiple options into one.
3. For example, 'gps' as option would block ads, malware, gambling, pornography and social.
4. Note: The 'master' option is in all of the options so no need to include it.
5. Note: Some devices may need a reboot after updating even if ran as root.
Instructions
- Make sure you have Magisk installed.
- Download latest: v8
- Flash the zip in recovery.
- Run update if you'd like.
Credits
- @topjohnwu for Magisk
Sources
- The Adaway hosts file, updated regularly. http://www.adaway.org/hosts.txt
- MVPs.org Hosts file at http://winhelp2002.mvps.org/hosts.htm, updated monthly, or thereabouts.
- Dan Pollock at http://someonewhocares.org/hosts/ updated regularly.
- Malware Domain List at http://www.malwaredomainlist.com/, updated regularly.
- Peter Lowe at http://pgl.yoyo.org/adservers/, updated regularly.
Source (GitHub)
- github.com/RatchetPanda/ratchetpanda.github.io
Submit an issue if you'd like a entry added, changed or deleted. Pm me if you'd like contributer access.
Very cool. I'm learning up on Magisk and it looks like a fundamental shift in the development stream. It seems like AdAway was a common culprit in AP failing ( along with Chainfire's SuperSU).
SilverZero said:
Very cool. I'm learning up on Magisk and it looks like a fundamental shift in the development stream. It seems like AdAway was a common culprit in AP failing ( along with Chainfire's SuperSU).
Click to expand...
Click to collapse
Yeah I never used AdAway though, kinda pointless having another app clutter the app drawer for something that can just be flashable.
Adaway updates the hosts file every day or so, while this appears to be a static hosts file. Is this intended to replace Adaway or provide a newer/bigger hosts file for Adaway to update? If it's intended to replace Adaway, how does it get updated?
Is it possible to include a uninstallation zip, in case we decide to revert the changes?
JimSmith94 said:
Adaway updates the hosts file every day or so, while this appears to be a static hosts file. Is this intended to replace Adaway or provide a newer/bigger hosts file for Adaway to update? If it's intended to replace Adaway, how does it get updated?
Click to expand...
Click to collapse
I would need to provide an updater app, I intended to replace AdAway as this provides much more than AdAway. I'll throw together an app or something to allow updates.
njunxuan said:
Is it possible to include a uninstallation zip, in case we decide to revert the changes?
Click to expand...
Click to collapse
Sure.
RatchetPanda said:
I would need to provide an updater app, I intended to replace AdAway as this provides much more than AdAway. I'll throw together an app or something to allow updates.
Sure.
Click to expand...
Click to collapse
That would be great!!!
Adaway's hosts file is 2.01MB so this isn't magnitudes bigger...
HypoTurtle said:
Adaway's hosts file is 2.01MB so this isn't magnitudes bigger...
Click to expand...
Click to collapse
The one at adaway.org/hosts.txt is not.
RatchetPanda said:
The one at adaway.org/hosts.txt is not.
Click to expand...
Click to collapse
Adaway combines 4 sources (last I checked) into one.
Added a remover zip to the OP. :good:
Update
- Hosts is now present here: ratchetpanda.github.io/hosts.txt
Anyone can contribute and add lines.
- Combined many more sources so we are up to 3mb with 90000 unique entries.
- Located at /sdcard/hosts so you don't have to have root to edit it.
- Hosts can be updated by running hosts in terminal
If rooted type su before hosts
If not rooted a reboot is needed after updating.
- Installs Magisk if not present.
Newest is attached and I've also added it to OP.
- A small tutorial on auto updating using Tasker or another automation app.
1. Set event to whatever you want.
2. Set task to Run Shell and set the code to run to 'hosts'.
3. If you have root make sure to check the 'use root' option.
Hope you guys like it! :good:
RatchetPanda said:
Update
- Hosts is now present here: ratchetpanda.github.io/hosts.txt
Anyone can contribute and add lines.
- Combined many more sources so we are up to 3mb with 90000 unique entries.
- Located at /sdcard/hosts so you don't have to have root to edit it.
- Hosts can be updated by running hosts in terminal
If rooted type su before hosts
:
Click to expand...
Click to collapse
just flashed this on Magisk V2 on my stock 6P. seems to work great.
edit:
Went to update the hosts file via Terminal. i don't think it worked though
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
steveo17 said:
just flashed this on Magisk V2 on my stock 6P. seems to work great.
edit:
Went to update the hosts file via Terminal. i don't think it worked though
Click to expand...
Click to collapse
Can you get screenshot or log of the terminal?
RatchetPanda said:
Can you get screenshot or log of the terminal?
Click to expand...
Click to collapse
just uploaded it. in the post above
steveo17 said:
just uploaded it. in the post above
Click to expand...
Click to collapse
Hmm this is what mine looks like. Can you go to /sdcard and check to see if you have either 'hosts' or 'hosts.txt' there?
@steveo17
This should fix your issues.
Just flash in recovery, small update to correct a couple of updater bugs.
RatchetPanda said:
@steveo17
This should fix your issues.
Just flash in recovery, small update to correct a couple of updater bugs.
Click to expand...
Click to collapse
I think that worked
Although it appears to have created another hosts file
Sent from my Nexus 6P using Tapatalk
---------- Post added at 06:04 PM ---------- Previous post was at 05:58 PM ----------
Update:
Unexpected side effect of flashing systemless adblock is that it seems to remove the magisk app.
Then when I flash phh supersu with the magisk app I can no longer toggle root
Sent from my Nexus 6P using Tapatalk
steveo17 said:
I think that worked
Although it appears to have created another hosts file
Sent from my Nexus 6P using Tapatalk
---------- Post added at 06:04 PM ---------- Previous post was at 05:58 PM ----------
Update:
Unexpected side effect of flashing systemless adblock is that it seems to remove the magisk app.
Then when I flash phh supersu with the magisk app I can no longer toggle root
Click to expand...
Click to collapse
If you updated to Magisk v2 you need to completely remove 1 before or the app will disappear.
RatchetPanda said:
If you updated to Magisk v2 you need to completely remove 1 before or the app will disappear.
Click to expand...
Click to collapse
remove v1 of magisk or this adblock?