Root Packager
Hey everyone! So for some reason, I hate batch files... They are ugly and I think it makes some users turn away from rooting their phones. So I went ahead and made a graphical UI that can be used for any root methods (non-Odin). The idea is that anyone who comes up with a method to root phones will have an easy way to throw together a GUI for rooting the phone instead of using a batch file.
This will work on Windows, Mac, and Linux. I haven't done the build on the Linux version or Mac yet but it is written in Qt so it will compile for all of the machines. So here is the deal:
There is a main structure to the program:
RootPackager
|
| -> root/ -- files used for the root method
| -> root.script
| -> tools/ -- location of adb (android debugger bridge)
| -> device/
| -> phone.txt -- name of the device you are rooting in the text file
| -> credits.txt -- HTML of credits for whoever made the root method
| -> drivers.txt -- links and names of carriers with the url to the driver for the phone
| -> html/
phone.txt
Simply put the name of the phone in this text file
credits.txt
You may put any HTML in this document crediting the people who made the root method.
Please keep the HTML relatively short, I recommend a <ul> list
drivers.txt
This file contains the carrier name and url to download the USB driver of the phone
On each line, you put the carrier name (no spaces) separated by whitespace and then the URL to the download.
Example:
Verizon url_goes_here
TMobile url_goes_here
root/ folder inside of the main folder
You may put all the files required to perform the root method here so they can be accessed by the script.
root/root.script
The 'root.script' file inside the root folder is where all the magic happens. This is essentially your batch script, but in a much simpler syntax. There is an example root.script in the folder provided, but here are the methods I have implemented so far:
# Commands Available For Root Packager:
# sleep - example: sleep 2 (sleeps for 2 seconds) - sleeps for a determined amount of time in seconds
# move - example: move /data/local/file /data/local/file2 - moves files on Android device
# shell - example: shell /data/local/debugfs - executes commands on the adb shell
# delete - example: delete /data/local/tmp.bak - deletes a file on Android device
# waitfordevice - example: waitfordevice - wait for the device to connect
# push - example: push su /data/local/ - pushes a file from the root/ folder to the Android device
# reboot - example: reboot - restarts the device
# adb - example: adb shell /data/local/su - execute any adb command you want
Please look at the example I have provided to make sense of it all.
Notice that if you are pushing a file, there is no need to add the directory, as the directory is the root/ folder. This is why it is important to put all root method files in here.
After all methods are executed, the program will verify that the device has been rooted.
The example I have provided will root the Samsung Galaxy S3 USA Variants on Android 4.0.4.
I hope you find this useful and I hope that this leads to less batch scripts floating around!!!
Here is the download:
mediafire.com/?l559tse4ztzc47d
Here are some screenshots:
imgur.com/a/7Eq48
Hi guys!
As I'm not a developer, but did not find a proper section to post this, feel free to edit / move / remove this topic if you feel it necessary / that does not comply.
Short story: updated my HTC One M8 Verizon phone with Viper OneM8 ROM, had some issues during various setups, and at final install I disalowed Google to restore my infos (contacts, apps, wifi settings etc) automatically at initial setup. Did almost all of the restore manually at a later time. But without my saved wifi profiles (arround 200 saved).
As I did not find a proper way to get them from Google, I had to do it old way. Had an older HTC One S, sync'd with Google backup, having full list of all my wifi profiles.
Disclaimer: I cannot take credits for this, as I just double checked and adapted the code found here for my needs (I am a lazy guy, and - as the original code was written to be used "as is" on a linux machine - I did not wanted to reboot to Mint, do the job and revert to Windows afterthat ).
So please make backups and don't do it if you don't understand what you are doing! As I take no credit, I also take no responsibility!
The goal: copy relevant info from wpa_supplicant.conf on old phone and put it in wpa_supplicant.conf in the new phone and make it load the new info correctly.
What you need:
- rooted device (rw access to /data/misc/wifi/),
- a backup of wpa_supplicant.conf from the above folder (a previous version) - might be from another device (like in my case).
- working adb tools on a windows computer (for linux see the above disclaimer).
- some basic skills in adb
The job:
1. Get the wpa_supplicant.conf from BOTH devices on your desktop.
This can be done in various ways, I will not get too deep into it. The easiest way is to just copy the wpa_supplicant.conf from /data/misc/wifi/ somewhere on sdcard on devices (using root explorer or similar app - remember, you need root on your device!), and after that just get it with windows explorer or whatever tool you are using to copy files from device to computer.
the adb should look like (I assumed you did copy the file(s) from /data/misc/wifi to the root of your sdcard(s) ):
(from old device)
Code:
adb pull /mnt/sdcard/wpa_supplicant.conf wpa_supplicant.FULL
(from new device)
Code:
adb pull /mnt/sdcard/wpa_supplicant.conf wpa_supplicant.EMPTY
2. Make a backup of BOTH files you just got! Especially of the EMPTY file, in case you run troubles.
3. Open the wpa_supplicant.FULL with a text editor on your computer and clear the headers. Save afterthat:
Don't use notepad, it's not handling well *nix new lines. You can use notepadd++, wordpad etc.
You need to delete everything in the begining of the .FULL file down to first
Code:
network={
ssid="hro-M"
(DON'T delete the network={ part or anything bellow it!)
Save the file. Open it again to check headers are gone.
4. Get the content from just saved wpa_supplicant.FULL into wpa_supplicant.EMPTY
Can be done in various ways. Easiest:
Code:
more wpa_supplicant.FULL >> wpa_supplicant.EMPTY
Check that now wpa_supplicant.EMPTY is full (filled with original new file headers and your networks info from the FULL file).
5. Put the new file back to new device sdcard and rename it with correct filename:
Again multiple options here (explorer, cloud etc).
Adb should look like:
Code:
adb push wpa_supplicant.EMPTY /mnt/sdcard/wpa_supplicant.conf
Check on your device that file is indeed there (also check it's contents with a text editor).
6. Turn off device WiFi
7. Make a backup of /data/misc/wifi/wpa_supplicant.conf:
Adb stuff:
Code:
adb shell
su
cd /data/misc/wifi
cp wpa_supplicant.conf wpa_supplicant.conf.backup
Check on device that both wpa_supplicant.conf AND wpa_supplicant.conf.backup are in place, and they have the same size.
8. Overwrite wpa_supplicant.conf in /data/misc/wifi/ with wpa_supplicant.conf from sdcard:
I prefered to delete the file and copy my version instead of overwriting it:
Code:
rm wpa_supplicant.conf
cp /mnt/sdcard/wpa_supplicant.conf .
9. Change permissions for wpa_supplicant.conf:
Code:
chown system.wifi wpa_supplicant.conf
10. Turn on wifi on device (restart device recommended):
In my case it worked after device reboot, but I did it with wifi turned-on.
Check your saved wifi networks in Settings - WiFi!
Most probably this will not apply to all devices (I remember I saw a wpa_supplicant.conf with encrypted passwords at some point on my device (different ROM, probably original Verizon One M8 ROM), but in some cases might help, as there are few references of how to recover previously saved network details (except Google backup and some apps, that sometimes do not work).
Hope this helps someone!
Thanks!
Warning: Even an expert runs the risk of “bricking,” or locking up their Android device when modifying it. Often this is a ‘soft brick’ from which they can recover, but sometimes the device is “hard bricked” from which no recovery is possible, and the device becomes a source of spare parts. Proceed at your own risk. Neither the author, nor XDA is liable if you do “brick” your device.
Note: I have insufficient posts to include outside links. I'll add them when I do. Until then you'll need to search the 'net.
Keeping that in mind, you may wish to acquire an older model device to practice with before attempting to modify leading edge devices. Kijiji and Craig’s List are good sources for low cost, used devices that can be used for practice. I acquired the Samsung Galaxy S5 neo (SM-G903W) with Android 7.0.0 (Nougat) installed, I’m using in this guide for about $20 USD. Although any device will do, try to get one from the same manufacturer as the device you want to modify. If your device is a phone, you do not need a SIM card to follow this guide.
The Android OS is a derivative of Linux, and many, but not all commands are the same. You should refer to Linux or Unix manuals for an explanation of the commands. Search the ‘net for “Linux Commands” to find the latest manuals.
As the boot animation and sound are the most common modifications, changes to those are the goals of this guide. It seems as though there is an app for everything now. Yes, they are handy, but this guide will use the command line for many of the modifications. I use Terminal Emulator on the device for command line access. I also use BusyBox to expand the command set available. Both are available from the Play Store. You need root access to install and use BusyBox.
The first step is to read the manual for your device. Pay particular attention to the method used to enter the download and recovery modes. The Samsung Galaxy S5 neo uses volume up + home + power to enter the recovery mode, and volume down + home + power To enter the download mode from the power off condition. Press the volume and home buttons first, and then press the power button while holding them down. The device will boot into the desired mode. You may also require special USB drivers on your PC for your device.
Next you need to take as complete a backup of your device as possible using the stock options. See your manual for help with this. It’s also a very good idea to download the full firmware, as well as the boot and recovery partitions and any tools needed to re-flash this software. The best way to find these is to consult the manufacturer’s website, then this forum, followed by a ‘net search if nothing else provides results. For my device I need Odin on my PC. I found the full firmware at sammobile.com and firmware.mobi. The boot and recovery images can be extracted from the Samsung file, and then re-compressed using 7-zip on your PC. The firmware.mobi website offers all three files for several versions of Android, as well as a configured Odin package to root my device.
Now that we’re ready, the next few posts in this thread will cover the following sequence:
1. Root Device
2. Install Recovery
3. Install Applications
4. NANDroid backup
5. Make your modifications
Root Device with Chainfire
Warning: If you have a KNOX enabled device, rooting it will trip the KNOX warranty flag, voiding your warranty. This flag cannot be reset, and will prevent some applications from working.
Warning: Rooting improperly can “Hard Brick” your device, turning it into a source of spare parts.
There are numerous rooting tools out there. I use Chainfire whenever possible. The current website firmware.mobi will generate an easy to use package including Odin for supported devices. Download and extract the package to a new folder on your PC. Start Odin using the root.bat file. Read the warnings. Next:
Ensure Developer Options are enabled on your device. On the SM-G903W, go to Settings/About Phone/Software information/Build number seven times. Other devices may use a different method. Consult your manual.
In Settings / Developer Options ensure OEM Unlock is on and turn on USB Debugging
Note: I also turn “Auto update system” off
Turn the device off, then re-boot into the download mode (Volume Down + Home + Power, and then press Volume Up on my device)
Plug the device into a USB port of your PC
Select AP in Odin, then select the image.tar.md5 file downloaded with your package.
Ensure one of the COM ports is highlighted.
This is your last chance to abort. DO NOT CONTINE if you have any doubts.
Click Start
When your device is rooted successfully you’ll see a green pass in Odin. Congratulations! Your device will re-boot into recovery mode to root the device, and then re-boot normally. Well, that’s how it was supposed to work. When I used the CF Autoroot file for the SM-G903W, I got the error message “Recovery is NOT seandroid enforcing”, and was unable to boot into the recovery mode. I used Odin to re-flash the recovery partition which allowed me to enter the recovery mode again. A little searching on this forum, led me to this post by Neoony. I used the link for the SM-G903F and succeeded in rooting the device.
Now you need a root manager. My preference is Super SU. Install it from Google Play. Run Super SU. It will let you know if you were not successful by reporting that your device is not rooted.
Install Backup/Recovery (TWRP)
As we intend to modify the Android system itself, we need the ability to back it up and restore it. There are several options including Clockwork Mod (CWM), Team Win Recovery Project (TWRP) and Titanium Backup. My personal preference is TWRP.
Installation is as follows:
Install the “Official TWRP App” from Google Play
Run the App, agree to the Terms and Conditions, and enable “Run with root permissions,” then tap OK.
Tap “TWRP FLASH” on the next screen
Select your device from the drop down menu, you will need a network connection for this. You’ll be presented with a series of choices. Choose the latest and greatest. The image will be downloaded to your device.
Select “FLASH TO RECOVERY”, and confirm the image is correct. You will see the message “Flash Completed Successfully!” when installation is complete.
Exit the “Official TWRP App” and re-boot your device into the Download, followed by Recovery, and finally normally to confirm all is well.
Install Applications
The applications to install are those you will use to customize your device. I suggest BusyBox, and Terminal Emulator from the Play Store. BusyBox requires root access for the expanded command set. Terminal Emulator will allow command line access on your device so you won’t need ADB on your computer. You will be able to gain root access through it to modify anything on your device anytime, anywhere.
Other Apps you may find useful are the Jota Text Editor, and Hex Editor. These are also available through the Play Store.
NANDroid backup
Once the device is rooted, and your choice of applications are installed it’s a good idea to fully back up the device. This includes ALL partitions, so you have a baseline that you can re-flash. If your device has minimal memory, you may need an SD card or USB OTG drive to hold your backup. These backups will often be larger than 4GB.
Re-boot your device into the Recovery Mode. In TWRP, select ALL the partitions. Select the desired Storage location, and tap OK. Swipe to backup your device. Note the warning that “Backups of data do not include any files in internal storage such as pictures or downloads.” That is not the purpose of TWRP, and is best accomplished with the native backup utility. This backup will require several minutes.
Make your modifications
With root access, a recovery program and needed applications installed; and a complete backup we are finally ready to modify the Android installation of your device. We’ll start with the boot animation.
Modifying the boot animation:
Most devices use a ZIP file for boot animations. Samsung uses a proprietary QMG file. I tried to convert a boot animation that I put together a few years ago into the QMG format using Samsung’s Theme Designer Version 2.0.4 (Build 3918), as the links I found to newer versions on the XDA forum were broken. Searching through this forum, I found this post by Jertlok. I used the Marshmallow version with Nougat successfully.
Enough of this talking, let the games begin! Find the boot animation you want to use and download it to your device.
I’m using the Terminal Emulator for this installation. Our first step is to find the source and destination folders for this file. The relevant folders for the SM-G903W are:
boot animation: /system/media
downloads: /data/media/0/Download
If you have another device and the boot animation is located elsewhere, do a search of this forum first to find them. Look for your device first, and the other models by the same manufacturer.
Type the following commands using the Terminal Emulator:
Code:
su get super user privileges
mount -o rw,remount /system remount /system with read & write permissions
cd /system/media go to directory with boot media files, may differ
ls verify this is the correct folder
mv /data/media/0/Download/bootanimation.zip . move the file to our current location
ls verify the file was moved
exit leave super user mode
Reboot your device and verify the boot animation works.
Note: Don’t forget the period at the end of the mv command. This is a shortcut meaning the current directory, saving you from typing the full location.
Modifying the boot sound:
Finding the location for the boot sound can be more involved that finding that for the boot animation. If you know the name of the file, you can do a search through Terminal Emulator with the following commands:
Code:
su get super user privileges
cd /system/media choose a starting point for your search
find –name PowerOn.ogg name of the boot sound on the SM-G903W
This shows the file to be located in /system/media/audio/ui. Put the sound you want in the Download folder. I’ve named mine bootsound.ogg to show another use of the mv command. Use the following commands in Terminal Emulator:
Code:
su get super user privileges
mount -o rw,remount /system remount system with read /write permissions
cd /system/media/audio/ui go to the folder containing PowerOn.ogg
ls confirm we’re in the right folder
mv PowerOn.ogg PowerOn.ogg.bak rename PowerOn.ogg
mv /data/media/0/Download/bootsound.ogg . move bootsound.ogg
mv bootsound.ogg PowerOn.ogg rename bootsound.ogg
ls confirm the change has been made
exit leave super user mode
Reboot your device and verify the boot sound works. The shutdown sound is not used in the stock ROM. You can add a shutdown sound in the same manner by placing PowerOff.ogg in /system/media/audio/ui. Note: If PowerOn.ogg or PowerOff.ogg do not play, check your file permissions. Set them to the same values as the remainder of the files in the directory, usually 644.
Wrap up
Everyone needs to start somewhere. My goal in starting this thread was to provide that starting point, and a path forward for those new to modifying an Android device. That is why I started with a stock not-too-old device, and showed how to take it to manually changing the boot animation and sound. Why manually, when there are apps for that? An App can only accomplish a single task, such as changing the boot animation. At the command line you can do almost anything. You won’t be stopped by the lack of an App.
Much of the material covered by this guide is specific for a device. Those with Samsung devices came out far ahead, and those with a Galaxy S5 neo may just have hit the jackpot. The general sequence for all devices is the same. You’ll just need to dig for those devilish details.
There are two things that should stick out:
1. Use a not too old device by the same manufacturer as your target when starting. It’s far cheaper than bricking a bleeding edge device.
2. Backup, backup, backup! This can’t be stressed enough. Losing hours or days of work is very depressing, and often leads to dropping a project.
Good luck modding your device. This forum is one of the best, if not THE best place for resolving those devilish details that you will encounter.
The Next Step: Changing the Boot Logo
First, thanks to Near_07 for his post Galaxy S9 and S9+ Boot logo. I modified his package to make one for the Samsung Galaxy S5 neo. Note that his script is for the same exynos platform. This is critical for packages containing binaries.
I unpacked the pile to a new directory on my PC.
The first thing I did was to verify paths and filenames in the script "update-binary". I opened the file using WordPad on my PC for ease of reading. The file contains references to "/dev/block/platform/11120000.ufs/by-name/UP_PARAM", which does not exist on the S5 neo. I used Terminal Emulator to check for something close and found "/dev/block/platform/13540000.dwmmc0/by-name/PARAM ". I copied the file to the Download directory, and from there to my PC. Opening the archive, I found that it contained the file "logo.jpg". Bingo! I was in the right place. I copied the "update-binary" back to the Download directory on the S5 neo, and used Jota Text Editor to change ALL the references from 11120000.ufs to 13540000.dwmmc0; and UP_PARAM to PARAM. I then copied the modified "update-binary" back to replace the original on my PC. Why did I use Jota Text Editor on the S5 neo, instead of notepad on my PC? Unix, Linux, and Android use different end of line sequences than the PC. There are programs for the PC capable of generating Android compatible files, but I'm sticking with software already mentioned in this tutorial.
Choosing or Creating a New Boot Logo:
Choose or create a new .jpg image, the same size as your screen for your new boot logo. I've attached the original logo.jpg from my S5 neo to this post. I used that as a starting point, moving and adding elements to mate with my boot animation. I've included a demo copy in the zipped package. I've also attached a copy of the first image in my boot animation sequence. The powered by Android Nougat element fades in as the animation runs.
How to Change the Boot Logo:
You are rooted and have TWRP installed if you've been following along. These are pre-requisites. STOP NOW if they are not installed.
Download the file S5neo_Boot_Logo_Changer
Unzip the file to an empty directory
Replace logo.jpg with your desired logo. Note the name MUST be exactly the same.
Use 7-Zip to compress the contents of your working folder, with 'Store' as the compression method
Copy the resulting archive to the Download folder on your S5 neo
Re-boot your S5 neo into the Recovery mode
Install the package, re-boot, and enjoy!
Removing Bloatware (or fun with scripts)
Bloatware consists of the unwanted apps generously added to your phone by Google, the manufacturer, and your carrier. There can literally be a hundred or more of these apps on your phone. So how do you get rid of them? You can use a package found on this site, but that can be problematical. You may have a different view of bloatware than the package’s author. You may not know what each APK deleted by the package does, and delete one you actually want on your phone. If this happens you’ll need to restore from backup, factory reset the phone, or even re-flash the firmware. My preference is to archive the APK on my desktop so that hopefully I can restore the APks with the package manager.
To start, grab one of the packages to delete bloatware for your version of Android, for as close to your phone as possible. I used this one by Windforce. The contents of updater-script may include a section that looks like this:
Code:
run_program("/sbin/rm", "-rf", "system/app/AASAservice");
run_program("/sbin/rm", "-rf", "system/app/BluetoothMidiService");
run_program("/sbin/rm", "-rf", "system/app/CloudGateway2017");
run_program("/sbin/rm", "-rf", "system/app/GooglePrintRecommendationService");
There are many tools such as word processors, and text editors that you can use to strip out the unwanted bits so that you end up with something like this:
Code:
AASAservice
BluetoothMidiService
CloudGateway2017
GooglePrintRecommendationService
Save it as a file, ensuring that you have an Android (Unix) end of line character. We end up with a list of folders containing the unwanted APKs. Next we need a script to archive the APKs.
The following script has been designed to run in the ‘Download’ folder, from the Terminal Emulator, or ADB (Android Debugging Bridge). It was written on my desktop using Notepad++, to ensure the proper end-of-line character was used. The script, and APK lists must be copied to the Download folder from the desktop. To access the Download folder from the Terminal Emulator or ADB, Super User or root permissions are required. File permissions allowing root to execute the script must be set. Finally the script must be run from within a shell.
Code:
mount -o rw,remount /system # mount /system for read/write
tempdir=/system/app/app # temporary folder for APKs to be archived
mkdir $tempdir
while read apkname # loop parses file for APK names to archive
do
mv /system/app/$apkname $tempdir/$apkname
done < sysapp.txt # supplied list of APKs to be archived
tar -czvf sysapp.tar.gz $tempdir # archive APKs
rm -rf $tempdir # remove temporary folder recursively
rm -rf /cache/* # clear cache contents
rm -rf /data/dalvik-cache/* # clear dalvik-cache contents
reboot
exit 0
After the script has executed, you’ll note the icons for the archived APKs remain on the apps screen, and are still listed under Apps. The must be manually removed. You’ll find that ‘Uninstall’ is now available in both places for the archived apps.
Attached is a .zip file containing the script, and data files I used on a Samsung Galaxy S5 neo (SM-G903W).
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS
Code:
# knox_bit_warranty:0x1
#
# Your warranty is now void
#
# You have been warned.
#
# I will laught at you if you point the finger at me.
Hello everyone, in this guide I will be showing you how to edit android HOST file. There will be more methods in this guide, make sure you have allready unlocked the OEM and have installed root_privlages
Unlocking the bootloader and rooting
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS # knox_bit_warranty:0x1 # # Your warranty is now void # # You have been warned. # # I will laught at you if you...
forum.xda-developers.com
I will be updateing this guide regulary so make sure to chek it.
FIRST METHOD
First method is by useing Android Debugging Bridge (ADB). Make sure you SDK platform tools ready on your pc.
1. Open a terminal window in the install folder of platform tools.
2. Pull the hosts file out of the phone to your PC
Code:
adb pull /system/etc/hosts C:\platform-tools
Ofcourse you can change the location of where you want the fille to be pulled to.
3. Once you have pulled the hosts file to the desired location you can edit it. I will share my hosts file I use on my PC, you can take stuff frome there and integrated it in to yours. But don't put #, " and usles text, It will not like it.
4. After you have edited the host file to your needs, you need to send it back to your phone.
Code:
adb shell
su
mount -o rw,remount /system
adb push C:\platform-tools\hosts /system/etc/
After you type SU a prompt for root_privlages will apear on your phone, allow the shell to have root_privlages. mount -o rw,remount /system will disable SYSTEM on READ_ONLY
5. After pushing the HOSTS file to your phone put SYSTEM back to READ_ONLY
Code:
mount -o ro,remount /system
6. Enoy.
SECONED METHOD
Doesn't require root but requires TWRP to be installed.
1. You will need SDK platform tools
2. Open a terminal windows in the install folder of platform tools.
3. Pull the HOST file from the phone
Code:
adb pull /system/etc/hosts C:\platform-tools
Ofcourse you can change the location of where you want the fille to be pulled to.
4. Once you have pulled the hosts file to the desired location you can edit it. I will share my hosts file I use on my PC, you can take stuff frome there and integrated it in to yours. But don't put #, " and usles text, It will not like it.
5. Transfer your version of the HOSTS file to your sd_card, either by file explorer or ADB
Code:
adb push C:\platform-tools\hosts /sdcard
6. Boot in to TWRP and tap on mount, uncheck the option SYSTEM PARTITIONS ON READ_ONLY
7. Once READ_ONLY is disabled on SYSTEM partition go in to advanced then in to file manager. Copy your hosts file from external_sd card to system\etc\
8. Reboot and enoy.
THIRD METHOD
Requires SDK platform tools and root_privlages
1. Open terminal window in install folder
2. Run shell with super user
Code:
adb shell
su
You will get a pop up on your phone for shell asking root_premisions you want to click allow.
3. Remount system and get in to folder of host file
Code:
remount system
cd system
cd etc
4. Display the host file in terminal window
Code:
cat hosts
5. Manualy edit host file, this is with a example ip
Code:
echo "127.0.0.1 google.com" >> hosts
6. You should see this now after running cat hosts
Code:
127.0.0.1 localhost
::1 ip6-localhost
127.0.0.1 google.com
7. Exit shell by typing exit
FOURTH METHOD
Useing a app on your phone which is the easiest way. Requires root_privlages.
Wount be writeing that, I will link a video that will show you how to do it.
Credits goes to him for that video.
FIFTH METHOD
You can use a terminal emulator app on your phone and manualy do everything, same as THIRD METHOD.
Requires root_privlages
LINKS:
Unlocking the bootloader and rooting
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS # knox_bit_warranty:0x1 # # Your warranty is now void # # You have been warned. # # I will laught at you if you...
forum.xda-developers.com
Installing TWRP and LInageOS
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS # knox_bit_warranty:0x1 # # Your warranty is now void # # You have been warned. # # I will laught at you if you...
forum.xda-developers.com
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
what are bloat ips and how do i add?
also how much of the host file is necessary
Seems the solution is not working for me,
I'm on Android 11 and it seems I cannot remount because I need to disable dm-verity first.
But when I run adb disable-verity, I got following error:
Code:
verity cannot be disabled/enabled - USER build
Any idea how to make it work?
LAST_krypton said:
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS
Code:
# knox_bit_warranty:0x1
#
# Your warranty is now void
#
# You have been warned.
#
# I will laught at you if you point the finger at me.
Hello everyone, in this guide I will be showing you how to edit android HOST file. There will be more methods in this guide, make sure you have allready unlocked the OEM and have installed root_privlages
Unlocking the bootloader and rooting
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS # knox_bit_warranty:0x1 # # Your warranty is now void # # You have been warned. # # I will laught at you if you...
forum.xda-developers.com
I will be updateing this guide regulary so make sure to chek it.
FIRST METHOD
First method is by useing Android Debugging Bridge (ADB). Make sure you SDK platform tools ready on your pc.
1. Open a terminal window in the install folder of platform tools.
2. Pull the hosts file out of the phone to your PC
Code:
adb pull /system/etc/hosts C:\platform-tools
Ofcourse you can change the location of where you want the fille to be pulled to.
3. Once you have pulled the hosts file to the desired location you can edit it. I will share my hosts file I use on my PC, you can take stuff frome there and integrated it in to yours. But don't put #, " and usles text, It will not like it.
4. After you have edited the host file to your needs, you need to send it back to your phone.
Code:
adb shell
su
mount -o rw,remount /system
adb push C:\platform-tools\hosts /system/etc/
After you type SU a prompt for root_privlages will apear on your phone, allow the shell to have root_privlages. mount -o rw,remount /system will disable SYSTEM on READ_ONLY
5. After pushing the HOSTS file to your phone put SYSTEM back to READ_ONLY
Code:
mount -o ro,remount /system
6. Enoy.
SECONED METHOD
Doesn't require root but requires TWRP to be installed.
1. You will need SDK platform tools
2. Open a terminal windows in the install folder of platform tools.
3. Pull the HOST file from the phone
Code:
adb pull /system/etc/hosts C:\platform-tools
Ofcourse you can change the location of where you want the fille to be pulled to.
4. Once you have pulled the hosts file to the desired location you can edit it. I will share my hosts file I use on my PC, you can take stuff frome there and integrated it in to yours. But don't put #, " and usles text, It will not like it.
5. Transfer your version of the HOSTS file to your sd_card, either by file explorer or ADB
Code:
adb push C:\platform-tools\hosts /sdcard
6. Boot in to TWRP and tap on mount, uncheck the option SYSTEM PARTITIONS ON READ_ONLY
7. Once READ_ONLY is disabled on SYSTEM partition go in to advanced then in to file manager. Copy your hosts file from external_sd card to system\etc\
8. Reboot and enoy.
THIRD METHOD
Requires SDK platform tools and root_privlages
1. Open terminal window in install folder
2. Run shell with super user
Code:
adb shell
su
You will get a pop up on your phone for shell asking root_premisions you want to click allow.
3. Remount system and get in to folder of host file
Code:
remount system
cd system
cd etc
4. Display the host file in terminal window
Code:
cat hosts
5. Manualy edit host file, this is with a example ip
Code:
echo "127.0.0.1 google.com" >> hosts
6. You should see this now after running cat hosts
Code:
127.0.0.1 localhost
::1 ip6-localhost
127.0.0.1 google.com
7. Exit shell by typing exit
FOURTH METHOD
Useing a app on your phone which is the easiest way. Requires root_privlages.
Wount be writeing that, I will link a video that will show you how to do it.
Credits goes to him for that video.
FIFTH METHOD
You can use a terminal emulator app on your phone and manualy do everything, same as THIRD METHOD.
Requires root_privlages
LINKS:
Unlocking the bootloader and rooting
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS # knox_bit_warranty:0x1 # # Your warranty is now void # # You have been warned. # # I will laught at you if you...
forum.xda-developers.com
Installing TWRP and LInageOS
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS # knox_bit_warranty:0x1 # # Your warranty is now void # # You have been warned. # # I will laught at you if you...
forum.xda-developers.com
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Click to expand...
Click to collapse
Thanks, I will be thankfully glad that I seccseed, Fir 1st Method via twrp recovery>file terminal,mount system>file maneger>cd /system/host/etc, but Ihave lost the host of the host refer to gms [email protected]#$# auto update, someone has made that in past and now a days the battery work by the rulz of android 9 eco system
great write up, third method worked for me on Android 12 with root.
tealtadpole said:
Seems the solution is not working for me,
I'm on Android 11 and it seems I cannot remount because I need to disable dm-verity first.
But when I run adb disable-verity, I got following error:
Code:
verity cannot be disabled/enabled - USER build
Any idea how to make it work?
Click to expand...
Click to collapse
the easiest way is to get and use a vndklite image.
you can google: "vndklite vs vndk" to learn more about it.
here it is from Google for a head start: https://source.android.com/docs/core/architecture/vndk
I cannot solve my one issue and very dipressed, I highly for you to see the given link and plz replay me for my Issue.
Hello and welcome, today Ill teach you, how to enable naitive call recording on any rooted samsung A53
so requirements for this
.java needs to be installed on the pc
. rooted samsung A53 (obviously)
. a root file explorer of your choice, I personally recommend Solid explorer
. the the latest jar from https://github.com/fei-ke/OmcTextDecoder/releases
Preparing
on your phone, go to about phone>software information and look at what the Software provider software version says (i e in my case it would be EU)
after that go ahead and go to A)optics/configs/carriers/your csc code/conf/system/ OR B) optics/configs/carriers/single/your csc code/
and copy that csc file over to your phone.
after that download that jar file and put it in a folder somewhere, then drag that csc file from the phone into that folder.
now right klick in that folder and choose open in terminal.
in terminal paste this
java -jar omc-decoder.jar -i cscfeature.xml -o cscfeature_decoded.xml
now delete the orignal cscfeatures file, and then open the decoded one with notepad, and go to where it says feature set at the werey end of that line, hit enter then paste this
<CscFeature_VoiceCall_ConfigRecording>RecordingAllowed</CscFeature_VoiceCall_ConfigRecording>
(note if you have diffirent country codes within your, cscfeatures.xml u must scroll down till u see your country code i e mine is under SE!!)
now klick save. and close notepad
now open the terminal again, if you closed it, just right klick and choose open in terminal.
then paste this
java -jar omc-decoder.jar -e -i cscfeature_decoded.xml -o cscfeature.xml
now u have an encrypted cscfeatures.xml, with call recording enabled, move it back to the phone, once back at the phone goahead and delete the stock cscfeatures.xml, then copy and paste the new freshly modified one, where the stock file used to be.
now reboot the phone, then go to the phone app, settings, and confirm that the call recording tab is under bixby calls.