Replacing stock 6.0 system.img with rooted system.img? (like 13b root method) - Verizon LG G4

Are we able to take our firmware to 6.0 (2BA) and swap out the system.img with a rooted system.img like we did on 13b?
I am currently unable to UsE because I only have a mini laptop that's 32 bit and I cannot get ANYTHING to work, I cannot even boot FWUL in Virtual Box, live, nothing.... ..
I am currently in 13b root and there are NO custom roms I can use. Nothing. And no way to upgrade and keep root I believe?.

robles4242 said:
Are we able to take our firmware to 6.0 (2BA) and swap out the system.img with a rooted system.img like we did on 13b?
I am currently unable to UsE because I only have a mini laptop that's 32 bit and I cannot get ANYTHING to work, I cannot even boot FWUL in Virtual Box, live, nothing.... ..
I am currently in 13b root and there are NO custom roms I can use. Nothing. And no way to upgrade and keep root I believe?.
Click to expand...
Click to collapse
not posable...
google made a verification system for Android 6.0+ (locked bootloader only) that will check if anything in the system partition has changed...
I believe SALT can run on any architecture( x86 32 or 64bit, arm, arm64, etc ). you can use a different distro and install salt from there. you can use Linux Mint or MX Linux since They still have 32bit versions and are easier to use. you can use VirtualBox (have to install the distro) or USB(you can run directly off of it). to start the installation of SALT you need an internet connection. open terminal by Ctrl + Alt + t or by searching it in the app menu.
type these commands in the terminal:
Code:
sudo apt update
sudo apt install policykit-1 yad git xterm python3 python3-usb python3-crypto python3-pip
sudo pip3 install zstandard
git clone [url]https://github.com/steadfasterX/SALT.git[/url]
cd SALT
sudo ~/SALT/salt
after that just follow the USU thread...

Related

[Q] Help On Root

I managed to get S-Off even though it never said complete at the end. I used the alpharevx. Somehow I kept trying it and even though it never said completed, I now have the Alpharevx bootloader.
I tried to install clockworkmod since I don't have it, and I did this in linux(ubuntu). I downloaded the fastboot files and the image. Ran terminal and ran
fastboot devices while my phone is in fastboot usb mode. I get "command not found." I try to flash the image too and I get the same error.
Is there a step i skipped?
How are you running your command?
Well i run sudo /home/selayan/android-linux-tools/fastboot flash recovery <recoveryimagename.img>
I also went as far as installing the android sdk and adb in linux and it still will not work.
selayan said:
Well i run sudo /home/selayan/android-linux-tools/fastboot flash recovery <recoveryimagename.img>
I also went as far as installing the android sdk and adb in linux and it still will not work.
Click to expand...
Click to collapse
All of the procedures I have seen show that you should run sudo in the same directory as fastboot and the recovery image are in:
sudo ./fastboot flash recovery recoveryimagename.img
The problem is alpharevx did not install ClockworkMod for me so I need to do it manually. In this case I have to install JDK, and anddroid SDK plus ADB too I think in order to get everything working. I saw a post on how to flash CWM manually but it was for windows not linux.
selayan said:
The problem is alpharevx did not install ClockworkMod for me so I need to do it manually. In this case I have to install JDK, and anddroid SDK plus ADB too I think in order to get everything working. I saw a post on how to flash CWM manually but it was for windows not linux.
Click to expand...
Click to collapse
If you can do it via Windows, you only need four files: adb.exe, AdbWinApi.dll, cwm-recovery-vivow.img, fastboot.exe.
That was all I used when I did it last night. Yeah, I went through the hassle of installing the JDK and SDK for Android, but it probably wasn't necessary. You can pull the first two files from the temp root download, and they'll probably work fine.
Well I'm on a macbook pro so I need to do it on Linux, I could try running windows 7 in vmware and just doing it that way, but I think since I have linux set up, it would be easier to do it that way. I hope it works, I will reinstall ubuntu, and then go through the android sdk install instructions.

[Q] Flashtool for mac

I want to flash the at&t stock rom before it changed my build number, but all I have is a mac and flashtool is only for windows. I tried changing the linux version since it is java, but it didnt work. Can someone help?
You can run flashtool on ubuntu using VirtualBox
Legoman2 said:
I want to flash the at&t stock rom before it changed my build number, but all I have is a mac and flashtool is only for windows. I tried changing the linux version since it is java, but it didnt work. Can someone help?
Click to expand...
Click to collapse
I may be able to assist you as I am successfully running the linux version on SL 10.6.8. OK, first things first so start a terminal window and do the following ...
1. You need to setup the session variable for JAVA_HOME so type "export JAVA_HOME=$(/usr/libexec/java_home)" and then return
2. I like to add the default location of the binaries to the PATH so type "export PATH=${JAVA_HOME}/bin:$PATH" and return
Next we need to grab the libraries that enable the java vm to work with USB devices. You can do this a couple of ways, either by installing macports and then the usb libs or compiling from source (you will need xcode installed). macports is useful and you may have it installed already so I'll go with this method.
3. Install macports http://www.macports.org/ following their instructions.
4. update macports so type "sudo port -v selfupdate"
5. install the usb libs so type "sudo port install usb"
6. need to configure the library path so type "export LD_LIBRARY_PATH=/opt/local/lib"
Now, you can either execute the FlashTool binary through finder or manually from a terminal window. The exports could be made permanent by adding to your shell profile (like ~/.bashrc or system (/etc/profile) etc...
N.B. Forgot to mention I'm using FlashTool 0.8.6.0 and Java 1.6.0_35 (@ terminal type 'java -version'). I haven't tested the more recent versions of FlashTool but it is possible they may be built on more recent JRE so make sure the version of Java you have is the same as the FlashTool dependency.
I posted some instructions for mac Flashtool here:
http://forum.xda-developers.com/showpost.php?p=32221825&postcount=7
Hope it helps out
Legoman2 said:
I want to flash the at&t stock rom before it changed my build number, but all I have is a mac and flashtool is only for windows. I tried changing the linux version since it is java, but it didnt work. Can someone help?
Click to expand...
Click to collapse
Hey Legoman2, there is a FlashTool Mac Edition released two days ago think so. Check it out at: http://androxyde.github.com/ good luck.
Updated on my instructions to install and use Flashtool on the mac, http://forum.xda-developers.com/showpost.php?p=32221825&postcount=7 should work now

[GUIDE] ADB & Fastboot not working under Windows? UBUNTU WILL DO!

The keystone of this guide: make ADB & fastboot working in Ubuntu, when nothing else helps with with Windows. Resent Windows OS versions are getting less flashing-friendly and some brands (like Samsung) release new devices on the market without compatible USB drivers. Before losing countless hours trying to solve the problems, try this, possibly very easy solution.
Compatible devices: ADB will work on nearly all devices, fastboot should be also usable for very most of the devices with bootloader mode: Nexus, HTC, Sony etc.
The guide is posted here in Nexus 7 (2013) thread for high amount of reported bootloops right after unlocking the bootloader- or problems with executing fastboot commands in Windows, which must work to unbrick the device.
DISCLAIMER:
Code:
* [I]I am not responsible for bricked devices or PCs, personal crisis, depressions[/I]
* [I]sleeples nights, termonuclear wars, electricity blackouts, short circuits,[/I]
* [I]or for bad weather in your region that will brick your Android device or your PC.[/I]
* [I]I try to help here, but it may not work for you. You do all on your own risk.[/I]
Click to expand...
Click to collapse
INSTALL ONLY FASTBOOT :
Windows can cause so many problems, that sometimes ADB & Fastboot simply won't work.
Run therefore ADB or fastboot in Ubuntu if Windows fails.
Installing ONLY fastboot in Ubuntu (should work with 10.x, 11.x and 12.x)
(internet connection required)
Run in the Terminal:
Code:
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
Reboot isn't required.
Save all the flashing files on home folder, or navigate with "cd" to your files.
Happy flashing!
For the case it doesn't work after this, try THIS method which is little bit more complicated, but should work in actually all Linux OS variants.
Click to expand...
Click to collapse
INSTALL ADB AND FASTBOOT :
To fix a bootloop, for unbricking, to root, to unlock/relock the bootloader, for flashing of a stock firmware, kernel, or recovery: for all those things fastboot must work reliably. And in Windows, it sometimes simply won't work at all, whatever you try.
Windows OS is complicated. And needs drivers at all times. Successful use of ADB or Fastboot with Windows is totally dependent on perfectly installed drivers. And there we have the source of many problems. As way around all those in fact Windows related promblems, we will use here Linux instead of Windows. Linux needs no drivers. Linux is free. Linux needs no antivirus software. Linux gets optimized day by day. Your Android device is Linux based.
After reading how many users encounter day by day countless issues by attempt to run fastboot and ADB commands (especially here in Nexus threads), I've decided to make this guide. There are some longer and complicated guides here around. I like fast, easy and secure way- so I hope this will help.
STEP 1: how to run Linux on Windows PC
There are many variants of Linux OS, but to keep the things really simple I will refer here entirely to the most popular variant of Linux: Ubuntu.
Windows users have three common ways to run Ubuntu on their Windows PC:
OPTION 1: installing Ubuntu permanently (my personal preference)
Pros: you will gain Ubuntu OS besides Windows and possibility for dual-boot. Reboot between Windows and Ubuntu takes about 1 minute. Full functionality of both operating systems.
Cons: in very seldom cases the installation of Ubuntu doesn't work flawless and if Ubuntu gets installed on the same HDD, Windows OS can get partly damaged or unusable, or has to be re-installed. Part of HDD memory space has to be permanently reserved for Ubuntu (min. 10GB recommended) and won't be accessible from Windows anymore.
OPTION 2: running Ubuntu from bootable live-CD
Pros: Ubuntu won't get physically installed, it runs 100% virtually from bootable live-CD and uses only RAM of the PC. People who don't desire to install Ubuntu permanently will have no changes on their PSs. No potential risks due to unsuccessful installation. In general, works with most of the computers.
Cons: No data or settings can get permanently saved in Ubuntu, especially Linux novices will have to learn quickly about setting the permissions: each time again after restarting Ubuntu session from the live-CD. Ubuntu is considerably slower this way.
OPTION 3: running Ubuntu from VirtualBox (in your Windows OS)
Pros: easy way to run Ubuntu directly from Windows in kind of "sandbox"
Cons: doesn't work well with some PCs
STEP 2: INSTALLING FASTBOOT & ADB IN UBUNTU
Now when your Linux OS is working, we can finally go for it!
Make sure to have internet connection
open the Software Center in Ubuntu
install openjdk-7-jdk
install Eclipse
download adt-bundle for your respective OS (32-bit or 64-bit version) from http://developer.android.com/sdk/index.html
extract the folder and paste the extracted folder to prefered folder and rename it to your prefered folder name
run the Terminal and navigate (cd) to the unzipped folder into "platform-tools"
Example for novices: I have pasted my extracted adt-bundle folder under "Home" and renamed it to "SDK", so I have to navigate to my platform-tools this way:
Code:
cd /home/tetakpatak/SDK/sdk/platform-tools
After this, you should be able to execute all the ADB and fastboot commands
Now just mind to paste all the files you desire to flash or push or sideload into your "platform-tools" folder!
Happy flashing!
Click to expand...
Click to collapse
DOWNLOAD LINKS
Ubuntu OS: DOWNLOAD HERE
Virtual Box: DOWNLOAD HERE
Warning: VirtualBox supports only the 32-bit version of Ubuntu, so also owners of 64-bit PC-systems should make sure to download the 32-bit version of Ubuntu, and not the 64-bit version!
ADDITIONAL INFORMATION AND USEFUL LINKS
Checklist for ADB:
for using in Android OS make sure to enable USB debugging under "developer options"
ADB works in Android OS and in the recovery mode, but not in the bootloader mode
make always sure at the very beginning that your ADB connection works by typing "adb devices" (the response must include a serial number on the left and "device" right after it!)
Basics about ADB: check for example this excellent ADB guide
Checklist for fastboot:
fastboot commands can be executed only in bootloader mode
fastboot commands will work also if USB debugging was disabled
make always sure at the very beginning that your fastboot connection works by typing "fastboot devices" (the response must include a serial number on the left and "fastboot" right after it!)
by using fastboot for the first time on a PC or Android device, never start with bootloader flashing! Missmatched bootloader flashing can hard-brick the device. Rather first execute "fastboot reboot-bootloader" and try to flash a kernel or recovery to make sure flashing commands are working and the connection is established.
Flashing with fastboot (example Nexus 7 v2012): check this excellent guide by @comminus
My self made video of flashing a full factory image with manually done fastboot commands in real time (example Nexus 7 v2012):
Click to expand...
Click to collapse
Please use "thanks" button beyond my posts if you find this guide useful. I've spent my time to help you, who read this.
TROUBLESHOOTING:
Occasionally, the device's storage doesn't get recognized in Ubuntu (something like MTP Camera error, can't mount camera, or so). The source of this problem is, that Ubuntu 12.04 doesn't support MTP natively yet, hopefully 13.04 will do.
This is the solution that should work with Ubuntu 12.04, enter in Ubuntu Terminal following:
Code:
sudo add-apt-repository ppa:langdalepl/gvfs-mtp
sudo apt-get update
sudo apt-get install gvfs
restart your PC, now everything should work (enable USB debugging if it doesn't)
If this method wasn't successful, you can try alternatively to do the same thing with these two repos:
Code:
sudo add-apt-repository ppa:webupd8team/unstable
sudo apt-get update
sudo apt-get install go-mtpfs
After the last command just reboot the PC
Also this repo could work:
Code:
sudo add-apt-repository ppa:langdalepl/gvfs-mtp
sudo apt-get update
sudo apt-get dist-upgrade
If none of both repos works and you want to uninstall both of them, just enter:
Code:
sudo ppa-purge ppa:webupd8team/unstable
sudo ppa-purge ppa:langdalepl/gvfs-mtp
great tutorial!
tetakpatak said:
reserved
Click to expand...
Click to collapse
Hey brother, great tutorial...
I know this will help so many people in the future and i love to see anything linux based! I have been using linux/bsd based operating systems for years and i love the way linux and android work together!
Take care my friend and thanks again for all of the hard work.
-droidshadow
You can also put your computer in test mode which bypasses msm kernel mode code signing policy. This will enable the ability to install the drivers needed. From the administration profile on your PC open a command prompt and type
Bcdedit.exe -set TESTSIGNING ON
Then restart your computer.
Edit: This is for Windows 7 X64 and Windows 8 users alike.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
I keep getting a keyserver error when entering first command.
Got it to install the problem I see now is with java
Steve One said:
I keep getting a keyserver error when entering first command.
Click to expand...
Click to collapse
Which Linux version do you use?
tetakpatalked from Nexus 7 flo
tetakpatak said:
Which Linux version do you use?
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
Mint15
Here's another shot
Steve One said:
Here's another shot
Click to expand...
Click to collapse
Please google a bit, I think you need another repo for Mint 15, I think I saw it somewhere in www last week. Sorry, I can't research right now until end of week.
tetakpatalked from P5110
tetakpatak said:
Please google a bit, I think you need another repo for Mint 15, I think I saw it somewhere in www last week. Sorry, I can't research right now until end of week.
tetakpatalked from P5110
Click to expand...
Click to collapse
I'm truly stumped went from Windows Vista to all Linux to be able to use adb and still can't get it to recognize my device.
I installed the java 7 sdk but it still doesn't recognize my device..........guess I will try to get a Petra CD don't know what else to do ha ha and I thought this was the easy way to get adb to work. Thank you for your help kind Sir.
Steve One said:
I'm truly stumped went from Windows Vista to all Linux to be able to use adb and still can't get it to recognize my device.
I installed the java 7 sdk but it still doesn't recognize my device..........guess I will try to get a Petra CD don't know what else to do ha ha and I thought this was the easy way to get adb to work. Thank you for your help kind Sir.
Click to expand...
Click to collapse
It should definitely work with Ubuntu versions 10. 11. and 12.04 even without extra installing Java. I didn't try it with other Linux versions.
Which Linux did you install? Did you enable USB debugging?
Check in www as there are different repos available for ADB and fastboot.
Opening post updated: added procedure for enabling all ADB and fastboot functions in Ubuntu, for the short way with enabling fastboot only doesn't work with every Ubuntu version.
tetakpatalked from the legendary i9000

Rooting Zenfone 2 WW under Linux?

Is there a tutorial or explanation, how to root a Zenfone 2 WW under Linux, especially with Ubuntu?
lg-optimus said:
Is there a tutorial or explanation, how to root a Zenfone 2 WW under Linux, especially with Ubuntu?
Click to expand...
Click to collapse
Same as windows but easier, do sudo apt-get install android-tools then just follow the other guides on here but don't do the parts where it says to install adb and setup drivers
If android-tools doesn't work (can't remember the exact package name as I don't use Debian distros) then try phablet-tools
Niropa said:
Same as windows but easier, do sudo apt-get install android-tools then just follow the other guides on here but don't do the parts where it says to install adb and setup drivers
If android-tools doesn't work (can't remember the exact package name as I don't use Debian distros) then try phablet-tools
Click to expand...
Click to collapse
I think he's talking about the fact that the scripts to root are windows scripts.
Maybe I can look at the windows-script and transfer the commands to Linux. But I would be glad, if someone can name the needed commands. The last Asus device, I have rooted under Linux, was a Nexus 7 and this was very easy, same with a LG P880. It is always an adventure, when you have to fear you brick the phone.
This is already installed:
ii android-tools-adb 4.2.2+git20130218-3ubuntu23 amd64 Android Debug Bridge CLI tool
ii android-tools-fastboot 4.2.2+git20130218-3ubuntu23 amd64 Android Fastboot protocol CLI tool
Click to expand...
Click to collapse
But I don't know, if it is necessary to define udev-rules.

Androxyde FlashTool 09.23.1 linux 32 bit(For use of FSC script)also adb and fastboot

Having struggled myself to find a working reasonably up to date FlashTool for linux 32 bit i would like to share FlashTool v09.23.1 which for me is up to date enough to do everything I've asked of it.
I believe this is (i may be wrong) the newest available version for 32bit linux it also run's on 64bit system's.
Obviously all the credit to @Androxyde :good:I hope this help's out the 32 bit linux user's in the XDA community.
Instruction's for those new to linux.
Open the fully unzipped and untared Flashtool folder.
In an empty space inside the opened folder right click mouse then select open terminal here.
On the command line write ./FlashTool .......or bash FlashTool (one or the other)
The terminal is case sensitive so be sure the command is correct eg ./FlashTool
It's probably worth mentioning that FlashTool is said to work better when given root access through terminal ,I have always given it root access without any problem's.
Wait for FlashTool to update it's devices list,then enjoy
If you are using a 32bit system remember not to upgrade to a newer version if FlashTool prompt's you.
The new version is only available in 64bit there for downloading it would be a waste of your bandwidth and more importantly waste of your time.
Code:
I have not given a tutorial as there are lot's out there .
Also if you are needing adb and fastboot for linux open terminal and input this command
sudo add-apt-repository ppa:phablet-team/tools && sudo apt-get update
That will add the repository needed and update your system,
If your system doesn't automatically update after the command "&& sudo apt-get update" part then do it manually by imputing the command
sudo apt-get update
Then finally add this command.
sudo apt-get install android-tools-adb android-tools-fastboot
Then chose "install"
Your adb and fastboot command's will now be recognised via your terminal.
Click here to download FlashTool v09.23.1 for 32bit LInux

Categories

Resources