Related
This is annoying as heck.
I have had the Droid 1, Droid X, and Charge and have always been able to root the phones and install roms and follow directions with now problem.
I have installed SDK, I have downloaded the adb platform tools. However, I have no idea how to get adb where it needs to be from there.
Does anyone know where I can find an in-depth guide?
try here:
http://developer.android.com/guide/developing/tools/adb.html
To use ADB commands, you open a CMD prompt (or terminal in linux) and navigate to your platform-tools folder. That's where "ADB" actually lives. Once you're in that folder, you can now use associated ADB commands.
Then you can use commands like /adb push <> <>, /adb pull <> <> etc.
This is what I found for ADB guide in XDA: http://forum.xda-developers.com/showthread.php?t=879701
Yeah, I have seen that.
I guess the wall I am hitting is how you actually start adb. I know where the folder is. I might be overlooking something though.
Didn't see your post Mart, ill try that now.
martonikaj said:
To use ADB commands, you open a CMD prompt (or terminal in linux) and navigate to your platform-tools folder. That's where "ADB" actually lives. Once you're in that folder, you can now use associated ADB commands.
Then you can use commands like /adb push <> <>, /adb pull <> <> etc.
This is what I found for ADB guide in XDA: http://forum.xda-developers.com/showthread.php?t=879701
Click to expand...
Click to collapse
An easy way to avoid the navigation through cmd is to right click in the folder that contains adb and open the command prompt.
Pacifik said:
An easy way to avoid the navigation through cmd is to right click in the folder that contains adb and open the command prompt.
Click to expand...
Click to collapse
Even easier is adding the folder to the system path variable.
That allows you to always run adb, no matter what folder you happen to be at.
Ok, I have effectively managed to get to adb and it is installed.
to root the nexus, do I now start at the 1st step in the "lets begin section" listed here:
http://rootzwiki.com/topic/12013-welcome-to-root-editionstep-by-step-oem-unlock-and-root/
http://wiki.cyanogenmod.com/wiki/ADB
Ohai droidstyle good to see you here
Has anyone seen John Connor?
skynet11 said:
Ohai droidstyle good to see you here
Has anyone seen John Connor?
Click to expand...
Click to collapse
Ya you too skynet! I have no gnex yet, but soon...very soon!!
I am now Bootlooped, the bootloader is unlocked, I flashed the recovery image without a problem, but now i am stuck at the constant flashing of the google logo
Did you flash a new ROM?
this is what I was flashing
fastboot flash recovery recovery-clockwork-5.5.0.4-toro.img
I was just trying to get root and CWM
I have CWM, but all it does bootloop and I can't get it to detect a sd card.
I have seen several of threads asking about how to recover data from a phone that has a broken display.
Backing up a phone with broken display
Prerequisites
Rooted phone with broken display/digitizer/etc. Display is nonfunctional for whatever reason.
ADB for your platform. Downloads for Windows, Mac, and Linux can be found at my dev-host.
Drivers installed (Windows), rules file set up (Linux + Mac). Drivers for windows can be found here. Rules file for Linux can be found here.
Recovery file attached to this post. (twrp.img)
External sdcard with at least 2 GB free space inserted in your broken phone.
openrecoveryscript.txt file attached to this post.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Backing up your broken device
Extract the ADB zip somewhere convenient.
Move the twrp.img recovery file into the ADB extracted directory.
Move the openrecoveryscript.txt file into the ADB directory.
Open a command prompt / terminal window in the ADB directory.
Windows: Windows Key + R => Type in "cmd" then click "RUN".
Linux: Open a terminal window by selecting it from your applications.
ALL:
Code:
cd /path/to/ADB/directory
Pull the battery from your phone, place it back in and boot into recovery (VolUp + Home + Power).
Connect your phone to your computer
Make sure that the following command returns "XXXXXX recovery" before proceeding to the next step.
Code:
./adb devices
Expected output:
Code:
List of devices attached
XXXXXXX recovery
Now to install TWRP recovery to your device. Type the following commands ( after each line). Linux users: Make sure you prepend each command with "./", as in "./adb ...". ALL Make sure you type the commands in CAREFULLY.
Code:
adb push twrp.img /tmp/twrp.img
adb shell dd if=/tmp/twrp.img of=/dev/block/mmcblk0p18
Wait until the last command above returns an output similar to below before proceeding to the next step:
Code:
12916+0 records in
12916+0 records out
6612992 bytes (6.3MB) copied, 1.094278 seconds, 5.8MB/s
Now pull your phones battery and reboot into recovery once again.
Run the following command to make sure your phone has booted into recovery completely.
Code:
adb devices
Expected output
Code:
List of devices attached
XXXXXXX recovery
Type the following to set up a script that will backup your phone to your external sdcard.
Code:
adb push openrecoveryscript.txt /cache/recovery/openrecoveryscript
Reboot your phone once more. This time, TWRP will begin backing up your ROM.
Wait for the backup to finish. You will know it is finished when you feel your phone reboot once more.
Optionally, you can check the state of your backup by running the following command and reading the last couple lines of it's output.
Code:
adb shell cat /tmp/recovery.log
Click to expand...
Click to collapse
Click to expand...
Click to collapse
That's it! Your entire system (/system, /data, /cache, and boot) will be backed up to your external sdcard. Just pop the sdcard in your replacement phone and you're good to go.
Enjoy and donate to the TWRP devs! This would not be possible if TWRP did not use the OpenRecoveryScript scripting engine!
Or you can use skip's unified toolkit.
I literally just used it. Moving the backup to my new device right now.
loserskater said:
Or you can use skip's unified toolkit.
I literally just used it. Moving the backup to my new device right now.
Click to expand...
Click to collapse
Whatever floats your boat :good:
Sorry, had to
Sent from my SGH-I747 using Tapatalk 2
Actually, this process might directly meet my needs.
You mentioned that the recovery image and script were attached to the initial post, though I must be missing something in that I don't see where they might be. Perhaps you could offer a pointer, please?
- ooofest
Ah sorry, you can find the files here
http://forum.xda-developers.com/showthread.php?t=2353828
Don't use the twrp.img from there though...go to the twrp website and download the latest .img file for your phone (d2att)
Sent from my S3 on Sense 5 (you jelly?)
CNexus said:
Ah sorry, you can find the files here
http://forum.xda-developers.com/showthread.php?t=2353828
Don't use the twrp.img from there though...go to the twrp website and download the latest .img file for your phone (d2att)
Click to expand...
Click to collapse
Thanks - I downloaded the appropriate files, but wonder if this can be used on a stock phone.
That is, I was able to push twrp.img to /tmp/twrp.img, but cannot write in the next step:
Code:
adb shell dd if=/tmp/twrp.img of=/dev/block/mmcblk0p18
/dev/block/mmcblk0p18: cannot open for write: Permission denied
This is a stock AT&T phone, in recovery mode, never been rooted.
- ooofest
You need to be rooted for this to work.
CNexus said:
You need to be rooted for this to work.
Click to expand...
Click to collapse
Ya know . . . I need to read things more carefully. Was so excited to see something that might possibly help. Sorry about that.
It's been awhile since I looked into rooting the Galaxy S III and will look around, but don't recall that this can be rooted from recovery, unfortunately. And, it seems that USB Debugging is not turned on when it boots to the lockscreen.
Hm.
- ooofest
[TOOL]ADB + Fastboot v1.0.31 for OS X/4.3 [NOW Includes ADB & Fastboot][08-17-2013]
ADB & FASTBOOT FOR OS X
There has been some confusion since I discuss using Fastboot in this post, but the zip only contained ADB. This is completely my fault and I apologize. Either way I've updated the .zip to include ADB & Fastboot.UPDATED: 08/17/2013 - Added Fastboot to adb-1.0.31-mac.zip
I've seen several people having issues on OS X trying to use ADB since the release of Android 4.3. In my case ADB recognized my device, but each time I ran adb devices my device would be reported as offline. I downloaded the SDK from Google several times and always ended up with ADB v1.0.29 (4.2.2).
This will should solve your OS X & ADB issues if you're running Android 4.3. This ONLY includes the ADB & Fastboot executable files and is for Mac OS X ONLY. I, like many others, do not need the full SDK. If you're not an app developer, like myself, this is all you need to have ADB working on your machine.
For any new OS X users I'll add a how to just so you don't have to go search for it else where:
How to setup ADB + Fastboot on OS X
Note: This is for not for developers. This only includes ADB & Fastboot and is not the full Android SDK
Step 1: Download the ZIP containing ADB & Fastboot
Step 2: Extract the ZIP to the directory of your choice
Step 3: Optional Create an environment variable
1. Open Terminal
2. Type cd to take you to your home directory.
Code:
cd
3. Type touch .profile to create a hidden file in your home directory named .profile
Code:
touch .profile
4. Type open -e .profile to open the file you just created in TextEdit
Code:
open -e .profile
5. In the file, add the following:
Code:
export PATH=${PATH}:/PathToDirectoryWhereYouExtractedTheZIP
6. Save the file and close TextEdit, quit Terminal, and relaunch the Terminal
Step 4: In Terminal type adb devices, you should see your phone's corresponding serial number Ex: HXM1005HNF012345 device
Code:
adb devices
Note: If you choose not to create an environment variable from Step 3 it effects two things:
1. You will need to cd to the directory containing ADB each time you want to run ADB.
2. When executing ADB commands you will need to add ./ in front of ADB. Ex: ./adb devices
Dropbox Download
Alternate Download
I've used a mac with with all three of me nexus devices so ime pretty familiar but..is anyone else having probs with fastboot trying to flash a system.img ...I kept getting a error everytime. Boot.img would go through but not system img...? Any help would be great. If not no worries...adb seems to work fine if u need to push something ... But this is the first device I couldn't use fastboot flash system with...??
Candy Painted
matthew0776 said:
I've used a mac with with all three of me nexus devices so ime pretty familiar but..is anyone else having probs with fastboot trying to flash a system.img ...I kept getting a error everytime. Boot.img would go through but not system img...? Any help would be great. If not no worries...adb seems to work fine if u need to push something ... But this is the first device I couldn't use fastboot flash system with...??
Candy Painted
Click to expand...
Click to collapse
Did you have ADB previously installed before download this .zip? This is not the full Android SDK, but the updated version of ADB and doesn't include fastboot.
wad3g said:
...and doesn't include fastboot.
Click to expand...
Click to collapse
Perhaps all references to fastboot should be deleted, right now this thread still says "adb + fastboot...". Thanks for providing it all the same. Save me the 400mb download
Chatperdu said:
Perhaps all references to fastboot should be deleted, right now this thread still says "adb + fastboot...". Thanks for providing it all the same. Save me the 400mb download
Click to expand...
Click to collapse
You're right. I can't believe that never crossed my mind, I guess I was assuming everyone previously had ADB on their machine.
Anyway, I've updated the download links and attachments so now everything includes ADB & Fastboot files. Hopefully this will clear up any confusing in the future and I apologize to all of you who had issues due to this.
wad3g said:
You're right. I can't believe that never crossed my mind, I guess I was assuming everyone previously had ADB on their machine.
Click to expand...
Click to collapse
I have a previous installation. I am assuming fastboot doesn't have to match the adb version. Will try it out soon. My previous solution is to boot into bootloader, than adb will find the device, an inefficient work around.
Chatperdu said:
I have a previous installation. I am assuming fastboot doesn't have to match the adb version. Will try it out soon. My previous solution is to boot into bootloader, than adb will find the device, an inefficient work around.
Click to expand...
Click to collapse
Yes a previous version of fastboot should work fine. I don't believe fastboot was updated. I still use the the fastboot version that came with 1.0.29.
i followed these instructions, including creating .profile, but still neither my nexus 4 or new nexus 7 running 4.3 are recognized. Nothing is listed when I do adb devices, just an emtpy list
Hi
I don't get paranoid to boot
I have installed
pa_find7-4.6-BETA5-20141021
+
pa_gapps-stock-4.4.4-20141025-signed
How i did it:
I boot from PC with[Recovery Installer for Oppo Find 7 by Find 7 O-Group]
uses openrecovery TWRP 2.7.1.0
Factory reset
Install BETA5 zip
Install gapps
reboot
When reboot screen only shows the OPPO logo, and stops, nothing more happens the next 15 minutes.
Anybody who can give me a hint?
Nobody has provided any logs to fix it so it's been sitting there untouched since release. The community apparently doesn't care enough to help the team fix it
#stayparanoid
Pirateghost said:
Nobody has provided any logs to fix it so it's been sitting there untouched since release. The community apparently doesn't care enough to help the team fix it
#stayparanoid
Click to expand...
Click to collapse
So, can i do anything to help PA?
torsoen said:
So, can i do anything to help PA?
Click to expand...
Click to collapse
Can you get a log or last_kmsg of the boot process?
#stayparanoid
Pirateghost said:
Can you get a log or last_kmsg of the boot process?
#stayparanoid
Click to expand...
Click to collapse
No problem :angel:
I can try a new flashing tomorrow morning (norwegian time) but then i need info for how to fetch the log(s) because after a probably fail, i need to restore it because i need it for work tomorrow.
You would get the logs with your computer
#stayparanoid
Pirateghost said:
You would get the logs with your computer
#stayparanoid
Click to expand...
Click to collapse
Thats fine, how do i access them from my computer?
I found this:
https://code.google.com/p/tegraowners-ics-rom/wiki/How_to_get_logs
So then i need to know how i get proper terminal app, i try this http://www.tomsguide.com/us/download/Android-Terminal-Emulator,0305-43764.html
All you need is adb and a command prompt. If the rom won't boot how do you expect to use an app in Android to get a log?
This is basic troubleshooting
#stayparanoid
Pirateghost said:
All you need is adb and a command prompt. If the rom won't boot how do you expect to use an app in Android to get a log?
This is basic troubleshooting
#stayparanoid
Click to expand...
Click to collapse
When running on stock ROM:
adb.exe logcat -v long > logcat.txt gives full log
After wipe+install rom+gapps:
When running cmd.exe (admin) type "adb devices": No devises is listed
Ween running
E:\Downloads\Android\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>adb.exe devices
List of devices attached (No list)
============================================================
adb.exe logcat -v long > logcat.txt gives empty log
========================
So how do i manage to connect?
By the way, the oppo boot logo uses to change colour (stronger white) when boot with PA it only displays logo, but logo dont change colour.
Please answer asap since i need to restore my phone
====
Further:
I manage to boot into TWPR and when i run terminal in directory 'supersu' and write 'su' responce is "su not found"
===
Further:
When in fastboot i can in cmd.exe write fastboot devices
Then i get answer "26de6ffc fastboot"
====
After a failed boot need to get into recovery and get a last_kmsg
#stayparanoid
Pirateghost said:
After a failed boot need to get into recovery and get a last_kmsg
#stayparanoid
Click to expand...
Click to collapse
And how?
torsoen said:
And how?
Click to expand...
Click to collapse
Huh?
#stayparanoid
Pirateghost said:
Huh?
#stayparanoid
Click to expand...
Click to collapse
Sorry, but i cant, i dont get my pc connected to my oppo. So until i know how to fix that there will be no log file.
T
torsoen said:
Sorry, but i cant, i dont get my pc connected to my oppo. So until i know how to fix that there will be no log file.
T
Click to expand...
Click to collapse
Until the boot is finished, adb won't show the device, try this.
adb wait-for-device && adb shell su; cat /proc/kmsg > kmsg.log
ⓐⓝⓓⓡⓞⓒⓛⓓⓔ ⓘⓢ ⓝⓞⓣ ⓐ ⓢⓘⓝ
plegdroid said:
Until the boot is finished, adb won't show the device, try this.
adb wait-for-device && adb shell su; cat /proc/kmsg > kmsg.log
Click to expand...
Click to collapse
Thanks!
I have tried
1) Booting stops with oppo logo
2) Connect usb
Then:
3) Admin cmd.exe from my PC
4) When doing all command on one line, northing happens. Have to stop with crtl+c
5) When doing adb shell su; cat/proc/kmsg > kmsg.log
Following happens:
E:\Downloads\Android\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>adb shell su; cat /proc/kmsg > kmsg.log
error: device not found
error: device not found
Any more help out there?
T
=======================
UPDATE
=============
Frwom TWRP i can browse files
I have tried to copy the cat proc/kmsg to external_sd
When copy command is executed the TWRP just writes that its 'copying' but nothing happens, only copying forever. And TWPR stop wortking and i have to boot
I also tried to chmod 7777 and move file to internal sd but TWPS hangs
I managed to copy recovery.log
======
Update
=============
After i wipe data+dalvik the cat proc + kmsg file is still on the device.
Should i wipe more?
In case of yes, what? I will not delete storage on internal and external sd,
What happens if i wipe system+cache+android secure ?
=====================
Magic, i found both logs on external sd when i put it physically in my pc
kmsg and recovery.log
They may be partially, because i did not get any Sucess feddback from TWPR when i did the copy job
You find them here for a day or two.
http://nesoddenseilforening.no/test/kmsg-pa_find7-4.6-BETA5-20141021.log
http://nesoddenseilforening.no/test/recovery_pa_find7-4.6-BETA5-20141021.log
So, no i have done my part. I wait for your answer
FYI I manage to run PA 4.45 stable -> pa_find7-4.45-20140729
This guide presupposes that you have Supersu installed as systemless, and that you have access to adb.
This will bypass provisioning checks for builtin tether app. The modded apk should work with future updates without touching /system at all.
Installation
Method 1 - Manual install
Download the attached CarrierEntitlement apk.
If you have su.img su:
Code:
adb push CarrierEntitlement.apk /sdcard/CarrierEntitlement.apk
adb shell
su
mkdir /su/CarrierEntitlement
cp /sdcard/CarrierEntitlement.apk /su/CarrierEntitlement/CarrierEntitlement.apk
chmod 644 /su/CarrierEntitlement/CarrierEntitlement.apk
echo "mount -o bind /su/CarrierEntitlement/CarrierEntitlement.apk /system/priv-app/CarrierEntitlement/CarrierEntitlement.apk" > /su/su.d/05TetherMod
chmod +x /su/su.d/05TetherMod
reboot
If you have sbin su (Android 8.0+)
Code:
adb push CarrierEntitlement.apk /sdcard/CarrierEntitlement.apk
adb shell
su
mkdir /sbin/supersu/CarrierEntitlement
cp /sdcard/CarrierEntitlement.apk /sbin/supersu/CarrierEntitlement/CarrierEntitlement.apk
chmod 644 /sbin/supersu/CarrierEntitlement/CarrierEntitlement.apk
echo "mount -o bind /sbin/supersu/CarrierEntitlement/CarrierEntitlement.apk /system/priv-app/CarrierEntitlement/CarrierEntitlement.apk" > /sbin/supersu/su.d/05TetherMod
chmod +x /sbin/supersu/su.d/05TetherMod
reboot
Method 2 - Flashable Zip (su.img only)
Code:
1. Download attached zip.
2. Flash in TWRP (Last tested in alpha 2)
Information
This mod is accomplished by replacing the following function:
Code:
.method public static getCarrierEntitlement(Landroid/content/Context;)Lcom/google/android/carrierentitlement/CarrierEntitlement;
.registers 2
.param p0, "context" # Landroid/content/Context;
.prologue
.line 56
const/4 v0, 0x0
return-object v0
.end method
NOTE: Post install
You may need to edit your APNs to get tethering working for your carrier.
On sprint, where editing APNs is disabled, the fix is here: Sprint Fix
Be sure to thank @Builtfordtough1 for all his help in diagnosing the issue at this post: The Solution!
Be sure to thank sb1893 for sbin su instructions.
Worked Perfectly
This worked perfectly. Fantastic job!
So I am on stock with unlocked bootloader, twrp installed, and rooted with SuperSU. Because this is an apk file, do i just download onto the phone and install as I would with any other .apk file?
coolhandz said:
So I am on stock with unlocked bootloader, twrp installed, and rooted with SuperSU. Because this is an apk file, do i just download onto the phone and install as I would with any other .apk file?
Click to expand...
Click to collapse
The directions clearly state in adb speak that you need to create a directory for the file. Move to said directory, change permissions, etc etc. Nothing about installing via the apk.
pcriz said:
The directions clearly state in adb speak that you need to create a directory for the file. Move to said directory, change permissions, etc etc. Nothing about installing via the apk.
Click to expand...
Click to collapse
well, i can follow basic commands in minimal adb & fastboot. I think this may be above me unless there is an idiots' guide.
coolhandz said:
well, i can follow basic commands in minimal adb & fastboot. I think this may be above me unless there is an idiots' guide.
Click to expand...
Click to collapse
Do you have access to adb? They are pretty straight forward. May need to view them on the website but if you are using an app it may throw the word wrap off and make the commands seem confusing. The directions are pretty word for word.
pcriz said:
Do you have access to adb? They are pretty straight forward. May need to view them actually on the website but if you are using an app it may throw the word wrap off and make the commands seem confusing. The directs are pretty word for word.
Click to expand...
Click to collapse
If by adb you mean minimal adb & fastboot, then yes I have access and I could probably brave it.
coolhandz said:
If by adb you mean minimal adb & fastboot, then yes I have access and I could probably brave it.
Click to expand...
Click to collapse
I wouldn't suggest doing it how I did it but I downloaded the file to my phone. I created the directory using a root enabled file browser (see mkdir command {make directory}). I even used the file properties option in solid explorer to change the permissions (see chmod 644). Every other command I did on the phone from a terminal emulator. Just had to ignore the adb shell command because I am actually doing them on the device and not through a shell on my computer.
pcriz said:
I wouldn't suggest doing it how I did it but I downloaded the file to my phone. I created the directory using a root enabled file browser (see mkdir command {make directory}). I even used the file properties option in solid explorer to change the permissions (see chmod 644). Every other command I did on the phone from a terminal emulator. Just had to ignore the adb shell command because I am actually doing them on the device and not through a shell on my computer.
Click to expand...
Click to collapse
yeah, all that is definitely outside of my comfort zone, but thank you for the info.
Can you normally update your device with OTA-updates like a un-rooted device, without flashfire or connect to your computer?
Is there an advantage to doing this over adding "net.tethering.noprovisioning=true" to the build.prop file?
airmaxx23 said:
Is there an advantage to doing this over adding "net.tethering.noprovisioning=true" to the build.prop file?
Click to expand...
Click to collapse
This mod is systemless, and should survive OTAs. That mod changes the build.prop on the system partition, which could prevent taking OTAs.
njeri123 said:
Can you normally update your device with OTA-updates like a un-rooted device, without flashfire or connect to your computer?
Click to expand...
Click to collapse
Any modification to the boot image *should* prevent OTAs from working at all. However, you can flash back to stock boot images, and take OTAs as long as you have not modified /system, which this mod does not do.
Furthermore, as long as you don't wipe /data/ this mod will live in su.img and survive when you flash newer system software.
Fenny said:
This mod is systemless, and should survive OTAs. That mod changes the build.prop on the system partition, which could prevent taking OTAs.
Any modification to the boot image *should* prevent OTAs from working at all. However, you can flash back to stock boot images, and take OTAs as long as you have not modified /system, which this mod does not do.
Furthermore, as long as you don't wipe /data/ this mod will live in su.img and survive when you flash newer system software.
Click to expand...
Click to collapse
Thanks for the explanation, I removed the build.prop line and used this method and it's working fine. Thank you.
@Fenny
Thank you so much for putting this into a .zip file. It is greatly appreciated!
is there a non root method to bypass the checks? i dont plan on unlocking or rooting since i use android pay...
ddarvish said:
is there a non root method to bypass the checks? i dont plan on unlocking or rooting since i use android pay...
Click to expand...
Click to collapse
I also use Android pay, so I have two boot images ready to fastboot or flash. I have a boot image with root, and a boot image without root running a kernel that hides the bootloader unlocked flag.
So, the way I handle this, I flash the unrooted (bootloader flag hidden) image as my daily driver kernel, this passes safetynet, and allows me to use Android pay.
I make a backup of that boot image. Then, I install TWRP, my custom kernel, and SuperSU. I make a backup of that image as well.
So I have two backed up boot images:
rooted.img
HideBLUnlock.img
I flash HideBLUnlock.img to boot a, and boot b, safetynet passes.
Whenever I need to tether I have my computer with me, so I "fastboot boot rooted.img" which leaves me rooted until my next reboot.
Depending on your usage you might want to reverse that.
All my mods get stored in su.img, so switching out the boot images is all I need to have the best of both worlds.
Is it possible to fastboot boot twrp and flash the zip without being rooted or having twrp actually installed? O unlocked my bootloader but that's been it
Ocelot13 said:
Is it possible to fastboot boot twrp and flash the zip without being rooted or having twrp actually installed? O unlocked my bootloader but that's been it
Click to expand...
Click to collapse
You can use the fastboot twrp image to install this mod but you MUST have SuperSu. I have basic validation to check that in my update.zip. If you don't have a su.img in /cache or /data, this mod cannot be installed.
Flashed via TWRP and now i finally have a fully functioning hotspot!!
Fenny said:
I also use Android pay, so I have two boot images ready to fastboot or flash. I have a boot image with root, and a boot image without root running a kernel that hides the bootloader unlocked flag.
So, the way I handle this, I flash the unrooted (bootloader flag hidden) image as my daily driver kernel, this passes safetynet, and allows me to use Android pay.
I make a backup of that boot image. Then, I install TWRP, my custom kernel, and SuperSU. I make a backup of that image as well.
So I have two backed up boot images:
rooted.img
HideBLUnlock.img
I flash HideBLUnlock.img to boot a, and boot b, safetynet passes.
Whenever I need to tether I have my computer with me, so I "fastboot boot rooted.img" which leaves me rooted until my next reboot.
Depending on your usage you might want to reverse that.
All my mods get stored in su.img, so switching out the boot images is all I need to have the best of both worlds.
Click to expand...
Click to collapse
This is facinating, do you ever think where we can use boot a and boot b in a multiboot like fashion so that when you turn on the device you can choose what to boot?