Related
Can someone please help?
I'm trying to edit the system\etc\bluez\main.conf file using root explorer.
I can edit the line I want, save and exit but it then reboots the phone automatically and the original unedited file is back.
What am I doing wrong?
BTW the phone is rooted and this is why I want to edit the file...
http://forum.xda-developers.com/showthread.php?t=676175
neomagik said:
Can someone please help?
I'm trying to edit the system\etc\bluez\main.conf file using root explorer.
I can edit the line I want, save and exit but it then reboots the phone automatically and the original unedited file is back.
What am I doing wrong?
BTW the phone is rooted and this is why I want to edit the file...
http://forum.xda-developers.com/showthread.php?t=676175
Click to expand...
Click to collapse
As we don't have write access to /system on a normal booted desire, you have to do all your work in recovery-mode.
I can get into recovery mode ok but how do I edit the file I want from there?
The options I have are:
- Reboot system now
- USB-MS toggle
- Backup/Restore
- Flash zip from sdcard
- Wipe
- Partition sdcard
- Other
- Power off
Extract the file out of the rom, change it, than push it back to the rom.
You can do that from ADB shell while your phone is in recovery.
You can find commands how to backup files and push/delete them back to ROM on this forums, or you can search it on internet.
dont forget to mount /system
adb shell in a new terminal screen
then mount /system
I can't figure out what I'm doing wrong.
I've tried the method suggested by allla and ivicask ie, using adb commands in recovery mode and I get the same result as using root explorer, the file appears to have copied successfully it reboots but the original file is back again
I've also tried vastlopers method and after lots of reading found that the device needs to be booted normally to 'remount' however when I try to push the file now it says "Directory not empty"
It seems to me that this adb method is just a long winded alternative to root explorer, none of which get the desired result.
Please help?
Bump. Bump.
I've now tried adb file explorer but can't figure out how to install Busybox on my device.
I'm out of ideas. Someone must know how to edit/overwrite the main.conf file.
I'm being told elsewhere on this Forum that the Desire cannot yet be fully rooted for r/w access to the /system/ folder. Is this correct?
neomagik said:
I'm being told elsewhere on this Forum that the Desire cannot yet be fully rooted for r/w access to the /system/ folder. Is this correct?
Click to expand...
Click to collapse
Yes it is. It's also written in the root tutorial!
Hi, I've got a noob question here: How do I properly remove Super User from my GSM Galaxy Nexus?
I used Wugs Root Toolkit and it applied some "permanent" superuser method. My question is, how can I go about deleting the files so that the APK is no longer on my phone? I don't mind rooting again if that's what is required to remove it.
I searched around and didn't find an answer--that said if this has already been answered somewhere before I apologize--maybe I just all around fail! I saw some posts that related to the Hero but yeah... pretty sure it doesn't apply to the GNex.
Thanks! Oh, and don't ask me why I want to do this, yeah yeah, I know I must be out of my mind. A follow-up question though, would be that if I decide to root again after this, is there a method of pushing superuser where it will be removed whenever the stock ROM is updated?
Thanks again!
Just use root explorer to delete it from system/ app
Sent from my Galaxy Nexus using Tapatalk 2
I was under the impression that, that would not completely work? Isn't there another file somewhere that has to be removed as well? Thanks for the response!
shadrage said:
Hi, I've got a noob question here: How do I properly remove Super User from my GSM Galaxy Nexus?
I used Wugs Root Toolkit and it applied some "permanent" superuser method. My question is, how can I go about deleting the files so that the APK is no longer on my phone? I don't mind rooting again if that's what is required to remove it.
I searched around and didn't find an answer--that said if this has already been answered somewhere before I apologize--maybe I just all around fail! I saw some posts that related to the Hero but yeah... pretty sure it doesn't apply to the GNex.
Thanks! Oh, and don't ask me why I want to do this, yeah yeah, I know I must be out of my mind. A follow-up question though, would be that if I decide to root again after this, is there a method of pushing superuser where it will be removed whenever the stock ROM is updated?
Thanks again!
Click to expand...
Click to collapse
This is another example of the pitfalls of trying to take shortcuts by using toolkits. Toolkits are fine to save time for those that understand what the toolkit is doing, but if you don't have that knowledege base, yo really should do things manually first, in order to learn. (In school, they don't let you use a calculator until you can add/sub/mult/div for a reason).
Take a look at this post, specifially method 2. See if you can figure out what those commands are actually doing.
I will help you out: you are essentially mounting the system partition as read-write, copying two files to the system, changing permission on the system, and then mounting the system as read-only.
So, in order to remove root, you need to mount the system as read-write, remove those two files (command is rm) and mount the system as read-only. [EDIT: depending on where the toolkit you used place su, it could be somewhere else than /system/bin, like /system/xbin or /system/sbin -- yet another reason not to use toolkits...]
Toolkits don't teach you that.
And for you follow-up question, the answer is no (if you are talking about updates). If you update using an OTA update, the update does not delete those two files, but it does change the permissions on them to disable root access.
Thanks Efrant! I'll try this out. Yeah, being lazy definitely didn't help me here
I used to flash my Vibrant all the time, but I got the Nexus so that hopefully I wouldn't need anything besides stock (for which I love the experience), so I'm just trying to stay as pure as possible
Thanks again, appreciate it!
shadrage said:
Thanks Efrant! I'll try this out. Yeah, being lazy definitely didn't help me here
I used to flash my Vibrant all the time, but I got the Nexus so that hopefully I wouldn't need anything besides stock (for which I love the experience), so I'm just trying to stay as pure as possible
Thanks again, appreciate it!
Click to expand...
Click to collapse
Give it a shot, and if you are having issues, post here and I'll guide you through it.
Appreciate it! I'll be fiddling around with it either tomorrow or the next day--pretty slammed this week.
Thanks again.
Let me know
shadrage, let me know what you figure out, and how you went about it, I'm stuck trying to figure out the same thing. If I figure it out, I'll give you instructions here.
nodnerb said:
shadrage, let me know what you figure out, and how you went about it, I'm stuck trying to figure out the same thing. If I figure it out, I'll give you instructions here.
Click to expand...
Click to collapse
It's very simple. If you still have root, just use root explorer and delete two files:
1) /system/app/Superuser.apk
2) the second file is su, and it could be in one of three places, depending on how you rooted:
/system/bin/su OR
/system/sbin/su OR
/system/xbin/su
That's it.
If you do not have root, go to the dev section and find an insecure boot image for the version of Android that you are running, download it, rename it to boot.img (if it isn't already), and place it in the same directory on your PC as you fastboot.exe and adb.exe files. Then boot into fastboot mode, plug your phone into your PC and type the following:
fastboot boot boot.img (wait for the device to boot)
adb remount
adb shell
rm /system/app/Superuser.apk
rm /system/bin/su
rm /system/sbin/su
rm /system/xbin/su
Done.
Now if you do not have root, and your bootloader is locked (and you are running 4.0.4), then you are out of luck. You will need to unlock your bootloader (which will wipe your data), and do the second method above/
Thanks
Thanks Efrant.
I'm trying to learn the ins and outs of adb, and it confuses me to no end. I'm slowing remembering playing with my dad's DOS computer when I was a kid, so command prompt and shell type work is coming back, but not easily.
efrant said:
This is another example of the pitfalls of trying to take shortcuts by using toolkits. Toolkits are fine to save time for those that understand what the toolkit is doing, but if you don't have that knowledege base, yo really should do things manually first, in order to learn. (In school, they don't let you use a calculator until you can add/sub/mult/div for a reason).
. . .
Click to expand...
Click to collapse
Exactly!
And how to only remove Superuser data?
I mean, I want Superuser to ask me again if I grant or not superuser-permision.
I need this because I have in Superuser 5 times Titanium Backup.
All has the same id but only one has the Titanium Backup icon and the other doesn't.
And if I try deleting the app from the list... the app just go to "Denied" but still there.
So, I want to delete the whole data so I get a clean list of apps.
Thanks!
settings >> apps >> all apps >> super user
clear cache, clear data
3rdstring said:
settings >> apps >> all apps >> super user
clear cache, clear data
Click to expand...
Click to collapse
Thanks man! I cannot believe I did not try that before.
Thanks!
efrant said:
If you do not have root, go to the dev section and find an insecure boot image for the version of Android that you are running, download it, rename it to boot.img (if it isn't already), and place it in the same directory on your PC as you fastboot.exe and adb.exe files. Then boot into fastboot mode, plug your phone into your PC and type the following:
fastboot boot boot.img (wait for the device to boot)
adb remount
adb shell
rm /system/app/Superuser.apk
rm /system/bin/su
rm /system/sbin/su
rm /system/xbin/su
Done.
Now if you do not have root, and your bootloader is locked (and you are running 4.0.4), then you are out of luck. You will need to unlock your bootloader (which will wipe your data), and do the second method above/
Click to expand...
Click to collapse
Having the same issue (I'm about to return the phone for a replacement so I want Superuser gone).
Can you maybe possibly kindly point me toward a good boot version of the file you're talking about? I'm running a Verizon Galaxy Nexus and I'm on version 4.0.4 Build IMM76K.
I found this link: http://forum.xda-developers.com/showthread.php?t=1631796 ...but I'm unsure what I should be downloading, renaming and throwing into my fastboot folder.
I understand I'll have to unlock the bootloader, but I'm going to wipe anyway since I'm sending it back. Any help with that part would be appreciated too.
Sorry if this is an unauthorized thread resurrection.
USA Prime Credit Peggy said:
Having the same issue (I'm about to return the phone for a replacement so I want Superuser gone).
Can you maybe possibly kindly point me toward a good boot version of the file you're talking about? I'm running a Verizon Galaxy Nexus and I'm on version 4.0.4 Build IMM76K.
I found this link: http://forum.xda-developers.com/showthread.php?t=1631796 ...but I'm unsure what I should be downloading, renaming and throwing into my fastboot folder.
I understand I'll have to unlock the bootloader, but I'm going to wipe anyway since I'm sending it back. Any help with that part would be appreciated too.
Sorry if this is an unauthorized thread resurrection.
Click to expand...
Click to collapse
Follow the instructions in this thread. It will take you back to stock, and there are instructions on re-locking the bootloader as well.
Had to restock my Nexus as well. but my USB didnt work so I decided to take my losses and just return it, rooted with Superuser.
I had spend 2 days trying to restock it. and then this Tech Guy from my Carrier Tells me...
O you have rooted your Phone. Well that might be a problem with the insurance... unless you got a Nexus Device.
I was like what do you mean.
wel with all nexus devices you are allowed to root your phone.
So I think this is the best Solution there is . just take it back and save yourself some time.
this really works!!!!
shadrage said:
Hi, I've got a noob question here: How do I properly remove Super User from my GSM Galaxy Nexus?
I used Wugs Root Toolkit and it applied some "permanent" superuser method. My question is, how can I go about deleting the files so that the APK is no longer on my phone? I don't mind rooting again if that's what is required to remove it.
I searched around and didn't find an answer--that said if this has already been answered somewhere before I apologize--maybe I just all around fail! I saw some posts that related to the Hero but yeah... pretty sure it doesn't apply to the GNex.
Thanks! Oh, and don't ask me why I want to do this, yeah yeah, I know I must be out of my mind. A follow-up question though, would be that if I decide to root again after this, is there a method of pushing superuser where it will be removed whenever the stock ROM is updated?
Thanks again!
Click to expand...
Click to collapse
1. after you have or have not unrooted, search up superuser on playstore
2. click uninstall, if it says uninstalling........, ignore that and go to home page
3. go to folder and delete cwm-root thingy(the zip file you copied to your folder when you rooted) and delete that(seriously, thats important)
4. make sure you have the root remover file in your external sd card
5. turn off device, reboot by holding power and down/left
6. select install zip from sd card and install the root remover file
7. reboot and superuser should be gone lol
keep in mind that i did this on my galaxy tab 2 10.1 so it will definitely work on that
should work with any device
hope this helped
lol
wow, old thread...
I have use root explorer to delete the Superuser.apk and system/bin/su
but once i restart my device, those two thing happen again and again.
Help!!!
About the only reason I root my phone is to install AdAway. I'd prefer to not modify the system partition to help make OTA's easier to get and to allow Android Pay to work. AdAway has a flashable .zip file that preps the hosts file to use the systemless root structure that comes along with SuperSU. Unfortunately, that script depends on being able to access the /data partition inside of TWRP which isn't going to happen any time soon on the HTC 10. Fortunately, it is easy for us to manually replicate what the flashable .zip is trying to do.
This isn't a detailed how-to, but more of a set of guidelines. Don't blame me if your phone explodes.
Root the phone with the latest SuperSU.
Download the AdAway_systemless_hosts_v2.zip file from the Unofficial AdAway thread.
Extract the files from inside the zip. We are only interested in two files in the support folder.
Connect the phone to your PC and turn on file transfer mode.
Copy "hosts" and "0000adaway.script" that you just extracted to the internal storage of your phone.
Use a program file Root Explorer to move "hosts" into /su/etc and move "0000adaway.script" into /su/su.d (this probably could have been done with ADB push, but I got permission errors when I tried it that way and I'm impatient and lazy).
Chmod 0755 /su/su.d/0000adaway.script (I used a root shell on the phone via ADB)
Install AdAway (I used the link in the Unofficial AdAway thread.)
Reboot the phone.
Run AdAway like normal. By default it should use /system/etc/hosts which is what you want.
If something doesn't work, figure out why and fix it. I'm happy to answer questions to the best of my ability.
AdAway works without problems here, with simple press activate button.
starbase64 said:
AdAway works without problems here, with simple press activate button.
Click to expand...
Click to collapse
Yup
Sent from my HTC 10 using Tapatalk
starbase64 said:
AdAway works without problems here, with simple press activate button.
Click to expand...
Click to collapse
Yes, but it modifies the /system partition unless you do the trick in OP. If I'm correct, you will have problems with OTA updates and Google Pay if you let AdAway directly modify the hosts file on /system.
Now that TWRP can access /data, can we just flash the zip?
goodtimes50 said:
Now that TWRP can access /data, can we just flash the zip?
Click to expand...
Click to collapse
Yes, you can. I downloaded that zip and apk from the Unofficial AdAway thread linked above. Booted into TWRP, flashed the newest betaSuperSU2.74-2-forceencrypt (not related to this, just so I'd be on the latest version), then the AdAway_systemless_hosts_v2.zip, rebooted and installed the apk and let it run. Rebooted. Showing hosts location as /system32/etc/hosts as the OP says is a good thing, and both files mentioned are in their correct places per Root Browser. [emoji106]
Sent from my HTC 10 using XDA-Developers mobile app
Sorry that it doesn't completely match the thread here but I think my question could fit in here anyway.
Do I suggest correctly that with systemless root, systemless AdAway and the stock recovery OTAs should be fully usable? Since there's no other modification to /system then.
bmwbasti said:
Sorry that it doesn't completely match the thread here but I think my question could fit in here anyway.
Do I suggest correctly that with systemless root, systemless AdAway and the stock recovery OTAs should be fully usable? Since there's no other modification to /system then.
Click to expand...
Click to collapse
I believe that is correct. There hasn't been a new OTA for my phone yet so I can't verify. However, when I do the check for new software it tells me no new updates (as opposed to the message about the files system being corrupt). I believe Android Pay should also work. I have it installed and added a new card, but I haven't tested making a purchase yet.
Thanks for the guide.
My device is rooted, but I didn't found su folder in anywhere when I use Root Explorer with root access, does anyone tell me how to get su folder and make AdAway work?
Fix for AdAway.
matif525 said:
Thanks for the guide.
My device is rooted, but I didn't found su folder in anywhere when I use Root Explorer with root access, does anyone tell me how to get su folder and make AdAway work?
Click to expand...
Click to collapse
Your device may use su, & still not have an su folder (at all) that is used for hosts file (ie systemless root). Just do this..
Download... Terminal emulator.
https://play.google.com/store/apps/details?id=jackpal.androidterm
Open terminal
Then enter these commands.. "Quote"
su
mount -orw,remount /system
rm /system/etc/hosts
ln -s /data/data/hosts /system/etc/hosts
mount -orw,remount /system
Now open AdAway go to preferences and select option to " Target hosts file"
Select /data/data/hosts
Enjoy..
If you still have ads in apps do this!!!
githyanki said:
Open the 3 dot menu in adaway, chose log DNS request. Enable TCP dump.
Open the app with ads, when ad loads, go back to adaway, and open log.
Long press any entries and chose black list.
Profit
Click to expand...
Click to collapse
All credit where credit is due. I just shared what I read else where.
Read here for more details..
https://github.com/AdAway/AdAway/issues/770
&
http://forum.xda-developers.com/showthread.php?t=2190753&page=143#post68988079
There is a known issue in HTC devices involves S-off. If the above doesn't solve this for you message here I'll follow. Or pm me. I work wierd hours be patient.
Rom Maximus 3.0.0 ( Android 7 ).Any instruction don't works,adaway no blocked ads.
regarding su folder to move files to
FreydNot said:
About the only reason I root my phone is to install AdAway. I'd prefer to not modify the system partition to help make OTA's easier to get and to allow Android Pay to work. AdAway has a flashable .zip file that preps the hosts file to use the systemless root structure that comes along with SuperSU. Unfortunately, that script depends on being able to access the /data partition inside of TWRP which isn't going to happen any time soon on the HTC 10. Fortunately, it is easy for us to manually replicate what the flashable .zip is trying to do.
This isn't a detailed how-to, but more of a set of guidelines. Don't blame me if your phone explodes.
Root the phone with the latest SuperSU.
Download the AdAway_systemless_hosts_v2.zip file from the Unofficial AdAway thread.
Extract the files from inside the zip. We are only interested in two files in the support folder.
Connect the phone to your PC and turn on file transfer mode.
Copy "hosts" and "0000adaway.script" that you just extracted to the internal storage of your phone.
Use a program file Root Explorer to move "hosts" into /su/etc and move "0000adaway.script" into /su/su.d (this probably could have been done with ADB push, but I got permission errors when I tried it that way and I'm impatient and lazy).
Chmod 0755 /su/su.d/0000adaway.script (I used a root shell on the phone via ADB)
Install AdAway (I used the link in the Unofficial AdAway thread.)
Reboot the phone.
Run AdAway like normal. By default it should use /system/etc/hosts which is what you want.
If something doesn't work, figure out why and fix it. I'm happy to answer questions to the best of my ability.
Click to expand...
Click to collapse
Hi there, ive got a mate 8, not sure if this adblocker will work on it but i want to try it out anyway. Ive unzipped the file but which folder in su do i move the files to? screenshot of the folders i have in su
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?
I think I already know the answer but you'll never know.....
I am looking into options to use LOS17 in combination with LOS recovery because then it is possible to have OTA updates even when storage is encrypted.
Though, I would like to have the option to use a script so I can remove some system apps, add some stuff to build.prop and remove some temporary files after every OTA.
As far as I know the only way this is possible is to add an a script to /system/addon.d.
Therefor I have tried using adb to push a file, though when phone is not rooted, it is not possible to use adb root and then adb remount rw and adb push.
So here the questons;
- Is is possible to add a script to /system/addon.d, though without root and without TWRP?
- When not; is there another way to run a script after every OTA without root and without TWRP?
Setup:
LOS 17.1 without root, encrypted and locked bootloader
I will answer myself as it seems OR a stupid question OR something else....
But, as already expected, without root en with a locked bootloader, the recovery is the only place where you can do something root-related when the recovery is giving this option ofcourse. LOS recovery, automatic OTA updates and additional scripts is therefor not possible because you can not place or modify stuff in /system (as it should be out of security concerns on non-rooted devices).
Though, @nvertigo67 posted a nice post about this topic. After reading I realised that, as I want to be in control of my phone AND I want to pay something back to our great dev's, I will definitely stick with TWRP and flashing and running scripts myself.
How to install LOS with TWRP, encrypt en relock bootloader can be found here.
Topic closed for me.
I messed it up myself with my modified build.prop settings:
By design adb root command works in development builds only (i.e. eng and userdebug which have ro.debuggable=1 by default). So to enable the adb root command the ro.debuggable=1 line must be in build.prop, which I have set to 0 for CTS reasons.
Unfortunately it seems my banking app is looking for this parm because when set to 1 the app is giving an error message on startup.
So no adb root for me as long as I want to use the banking app.