Database Develop

[Q] Confused w/ busybox

This is the account of my foolishness and I advice everyone not to follow it.:::
1.installed Linux installer std and complete Linux installer from play store.
2.when the 2nd app failed to unmount and GUI crashed showing some errors with busybox, followed 3rd step.
3. found the embedded busybox from 1st app n directly placed it in /system /xbin
4. the original busybox is gone n everything is fine but got too many errors in reading root directory of phone. None of the file manager is showing me root.
5. I'm suspecting that it has done something wrong with my cwm recovery as well for which I can't take a chance of bricking my phone.
6. NOW I need kind advice of u ppl on how to confirm the presence of recovery.img or whatever it should be to recover my cwm backed up data.

boot into recovery, if recovery do not boot then pull battery and start the mobile it will start normally, download busybox installer from play store (the one from stephen)
install busybox through the app(busybox problem will be solved)
download tass recovery cwm.tar file and flash with odin you will get cwm recovery back

did it
I've already tried busybox installers. non of them worked cause the whole root directory is unreadable to any of my apps except diskusage n similar things those show memory occupied.

then you should flash firmware and root again

Superuser
maybe update superuser binary?

solved
chmod 777 path name n got busybox 1.12

You lost root access because there is no busybox. Reflash the ROM. Easy way out.

nothing lost at all just replaced.
as I've stated the command above u, it was just a busybox w/0 permissions. I was getting permission denied.
thanks to Gael péron for his Help.

Help - Rooted, failed installing Busybox, now stuck while booting

Hello guys, I really need your help here.
I will try to explain the situation as detailed as possible, if you still need any info, just ask.
I own a HTC One, carrier locked (Base) and not the sprint version, whatever that is.
Yesterday I unlocked the bootloader and rooted the device, following a tutorial by a german tech site. It all went well, everything worked and I was happy. I did a complete backup of the Internal Storage, as accessible by PC. I did also install TWRP and used it to flash SuperSU. I did not do any backup using TWRP.
After downloading a few root apps, a few demanded missing Busybox, so I went to research a bit. I found some installers, downloaded the first one, and clicked install. It said something along the lines of "Install failed, try another location", so I did that. It failed again. I uninstalled the installer and tried another, same result. After a bit of research, I found out I had to unlock read/write permissions for the system partition.
I then found this Thread, telling to flash a .zip file which contains
- Everything necessary to install the latest SuperSU and supporting files (su binary included)
- Install latest busybox in recovery
- A ported wp_mod.ko module for this kernel
- A script to start wp_mod.ko
- A modified boot.img - insecured (allows for remounting of /system to rw when in Android), enabled USB debugging by default, and added busybox run-parts (alows scripts to run during boot).
Without noticing that the title said "Sprint HTC One" and without knowing the difference, I went on and flashed this .zip using TWRP.
The first time, it turned off/rebooted before it was finished (before TWRP showed the reboot option). Turning it on again, it was stuck on the "HTC - quietly brilliant" screen. I held the power button until it turned off, booted into recovery (TWRP) again and tried flashing the .zip again, this time seemingly successful. I clicked reboot, and it again got stuck on the "HTC - quietly brilliant" screen, now I don't know what to do.
After trying rebooting a few times, I did a factory reset, now before rebooting again, TWRP gave me the warning "No OS - Are you sure to reboot?" or something similar, which I find very strange.
Is my backup of Internal Storage of any use? (BTW: I can not access it right now, sadly)
Does anyone know what I could do?
Thanks in advance for all answers.

Oneiiros said:
Hello guys, I really need your help here.
After trying rebooting a few times, I did a factory reset, now before rebooting again, TWRP gave me the warning "No OS - Are you sure to reboot?" or something similar, which I find very strange.
Is my backup of Internal Storage of any use? (BTW: I can not access it right now, sadly)
Does anyone know what I could do?
Thanks in advance for all answers.
Click to expand...
Click to collapse
Long description, but you didnt say what you want to accomplish.
Anyway, probably easiest to flash a custom ROM using one of the following methods:
1- OTG Cable
2- adb push <name of rom>.zip /sdcard/
3- adb sideload <name of rom>.zip

[Q] Questions about CWM/TWRP, Nandroid and SuperSu

Hi..
I have a couple of questions about recovery mode and Nandroid backups. Easiest one first.. Does Nandroid back up everything, right done to home screen layout, personal folders, widgets etc.. an EXACT copy of the phone?
Secondly, I installed CWM/TWRP, and was able to boot into it to install my ROM, however, once the ROM is on the phone, I seem to lose the ability to boot into recovery mode. The CWM app shows that the recovery is installed, however the usual volume- and power key just starts the phone normally. I've put on an Xposed mod, which puts recovery on the power menu, with reboot, screenshot etc, however, that does the same.. Just reboots the phone.
Is this normal, and is it safe to keep pushing recovery to the phone via PC every time I need to use it?
Lastly, my phone is nicely rooted, however SuperSu only seems to grant access when set to "allow". On 4.1.2 I used to have it set to "prompt", however selecting this seems to block root access. I've tested it with an SU checker and a root checker, and with "prompt" selected, it tells me the phone isn't rooted. It's ok having it set to "allow", but not ideal, as I prefer total control over what is, and isn't allowed root access.
Any help and suggestions gratefully recieved. I'm on Android 4.3, .201 on an Xperia SP.
Thanks!

1. Recovery backup usually backs up these things..
-Boot (kernel)
-System partition (ROM with system apps. But not app data)
-Data (apps and app data- with all apks you installed, user settings, accounts etc. Including UI layout. But not sdcard data)
-Cache
*Philz recovery has a nice option to backup internal sdcard (data/media)-very useful!
# So, if you choose the option "custom backup", you can select which component to backup in TWRP/Philz. (CWM has custom restore only).
2. Installing a ROM will erase any recovery installed in the system partition (which is the case if locked bootloader. If BL unlocked, can install a custom kernel with recovery, which won't get erased by ROM installing because it's with the kernel, not in system partition).
#So, you might have to install the recovery every time after flashing a ROM (of course, unless the ROM has pre-installed recovery).
3. SuperSU on "prompt" mode works well for me. Try to clear the data of SuperSu app and see.. or see whether there's a new update..
Hope this is of some help to you

mrhnet said:
1. Recovery backup usually backs up these things..
-Boot (kernel)
-System partition (ROM with system apps. But not app data)
-Data (apps and app data- with all apks you installed, user settings, accounts etc. Including UI layout. But not sdcard data)
-Cache
*Philz recovery has a nice option to backup internal sdcard (data/media)-very useful!
# So, if you choose the option "custom backup", you can select which component to backup in TWRP/Philz. (CWM has custom restore only).
2. Installing a ROM will erase any recovery installed in the system partition (which is the case if locked bootloader. If BL unlocked, can install a custom kernel with recovery, which won't get erased by ROM installing because it's with the kernel, not in system partition).
#So, you might have to install the recovery every time after flashing a ROM (of course, unless the ROM has pre-installed recovery).
3. SuperSU on "prompt" mode works well for me. Try to clear the data of SuperSu app and see.. or see whether there's a new update..
Hope this is of some help to you
Click to expand...
Click to collapse
Thanks.. I've done a Nandroid backup with TWRP.. Can I move the folder from the SD Card to my laptop without any problems, or does it put files anywhere else? I gather doing it with CWM makes transferring to PC quite difficult, which is why I opted to go with TWRP.
Also, if I clear the data on SuperSu, will I lose any of the permissions it has already granted? I don't fancy setting up Greenify all over again!
Cheers!

MetalOllie said:
Thanks.. I've done a Nandroid backup with TWRP.. Can I move the folder from the SD Card to my laptop without any problems, or does it put files anywhere else? I gather doing it with CWM makes transferring to PC quite difficult, which is why I opted to go with TWRP.
Also, if I clear the data on SuperSu, will I lose any of the permissions it has already granted? I don't fancy setting up Greenify all over again!
Cheers!
Click to expand...
Click to collapse
You mean, you want to copy the backup files to your laptop for safe keeping? Yes, you can copy those files to laptop/pc and then copy back to proper backup folder whenever you want to make a restore. TWRP makes backup files under TWRP folder (below many subfolders of course) in internal sdcard ("sdcard" ) or external SD ("sdcard1" ), depending on where you choose to backup. You can easily copy back and forth from there, especially external SD because you can even remove it and read/write with a pc if the phone is screwed up. (Check whether files are copied properly and make sure 'safely remove usb drive' etc in pc. If a small corruption in files when copying, md5 checksum tests will fail and recovery would refuse to use those backup files for restore).
CWM, stores them under clockworkmod folder in external SD (easy access), but in data/media/clockworkmod if you chose internal sdcard. If you're familiar with ADB, you can use pull/push commands to copy back and forth from there to a pc. Philz recovery stores things under same clockworkmod, but under proper "sdcard" though.. so easy access. (Or at least it has an option to look for "sdcard" under /data/media/0, which is a proper place where internal "sdcard" is mounted..). Feel free to ask if any of above is not clear to you..
About SuperSU, yes.. clearing data (Apps>All>SuperSU>Clear data) of the app will erase all yes/no su permission granted settings.. like going back to where you began. But it won't do anything to greenify settings. I have a feeling that you didn't flash SuperSU update after you flashed a new ROM.. is it? You also have to flash SuperSU update zip after ROM flashing, so proper su binaries get installed to the new ROM (I think ). Otherwise you won't get proper root. So, you did/not flash SuperSU update after ROM flashing?

Hi..
I did flash SuperSu 1.93 update after flashing the ROM, and then after a reboot, flashed it to 1.94. I've cleared the data, but it still doesn't offer a prompt. When set to "prompt", Root Checker tells me the device isn't rooted.. As soon as I set it back to "Grant access", it's fine.

MetalOllie said:
Hi..
I did flash SuperSu 1.93 update after flashing the ROM, and then after a reboot, flashed it to 1.94. I've cleared the data, but it still doesn't offer a prompt. When set to "prompt", Root Checker tells me the device isn't rooted.. As soon as I set it back to "Grant access", it's fine.
Click to expand...
Click to collapse
Strange..! No idea what's causing your issue.. but try this:
-Open SuperSu app. "Apps" column should be empty because you cleared its data, no?
-Set to "prompt" mode.
-Open Terminal Emulator (get from Google play if not present)
-type "su -v" (without quotes) and press enter (checking su version). Should show something like "1.93:SUPERSU"
-then type "su" and press enter. See whether any su prompt.
-then type "id" and press enter. What's the output?

mrhnet said:
Strange..! No idea what's causing your issue.. but try this:
-Open SuperSu app. "Apps" column should be empty because you cleared its data, no?
-Set to "prompt" mode.
-Open Terminal Emulator (get from Google play if not present)
-type "su -v" (without quotes) and press enter (checking su version). Should show something like "1.93:SUPERSU"
-then type "su" and press enter. See whether any su prompt.
-then type "id" and press enter. What's the output?
Click to expand...
Click to collapse
With prompt mode set:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nothing happens when trying SU if set to prompt.
I noticed in terminal it reports as being 1.93, so tried reflashing in recovery to 1.94, however it still reports as 1.93. The app is 1.94 though?

mrhnet said:
Strange..! No idea what's causing your issue.. but try this:
-Open SuperSu app. "Apps" column should be empty because you cleared its data, no?
-Set to "prompt" mode.
-Open Terminal Emulator (get from Google play if not present)
-type "su -v" (without quotes) and press enter (checking su version). Should show something like "1.93:SUPERSU"
-then type "su" and press enter. See whether any su prompt.
-then type "id" and press enter. What's the output?
Click to expand...
Click to collapse
When set to grant, this is the output..

MetalOllie said:
With prompt mode set:
Nothing happens when trying SU if set to prompt.
I noticed in terminal it reports as being 1.93, so tried reflashing in recovery to 1.94, however it still reports as 1.93. The app is 1.94 though?
Click to expand...
Click to collapse
I too get 1.93 even though I also flashed latest version. It's the version of su binary. No issues for me. So it shouldn't be the problem.
Wanted to see "id" output after "su" (if "uid=0" like output means root access). Anyway, when "prompt", your su command seems to get stuck.. is it? Doesn't any message saying "su denied" appear after keeping it for a while?
Other thing you can try is to reinstall SuperSU app to see whether it makes any difference. Under SuperSU app settings, there's an option cleanup>reinstall (from google play). Can't be sure that it works, but an option to try. Keep a CWM/TWRP back up before trying it, just in case..

mrhnet said:
I too get 1.93 even though I also flashed latest version. It's the version of su binary. No issues for me. So it shouldn't be the problem.
Wanted to see "id" output after "su" (if "uid=0" like output means root access). Anyway, when "prompt", your su command seems to get stuck.. is it? Doesn't any message saying "su denied" appear after keeping it for a while?
Other thing you can try is to reinstall SuperSU app to see whether it makes any difference. Under SuperSU app settings, there's an option cleanup>reinstall (from google play). Can't be sure that it works, but an option to try. Keep a CWM/TWRP back up before trying it, just in case..
Click to expand...
Click to collapse
Done a reinstall, which went ok.. It updated the binaries, though still says 1.93 in Terminal. I don't get any message in Terminal on prompt mode.. Here's a screenshot of the "id" after "SU" while on "grant".
The other thing I've noticed is that the configured apps list is always empty, although apps do show in the log if I call them up.. For example, terminal shows, with a green hash next to it. Red if I set it to prompt.

Yup, it doesn't come in app list if set to grant/deny for me too. Could be normal.
I've run out of ideas.. One last checking...
Can you check with Root Validator app here https://play.google.com/store/apps/details?id=eu.thedarken.rootvalidator
My one is like this
See what's the difference in prompt/grant modes for you.
#And, do this command in terminal to see su permissions
Code:
ls -l /system/xbin/su
#What I would do as a last resort is to reflash the rom and root again (AFTER taking a full cwm backup). Btw, is the ROM you flashed pre-rooted? Is there another su binary in another (conflict?) location like /system/bin..? (Root Validator app would indicate about it anyway). For this you can do..
Code:
find /system -name "su"
#also, check whether daemonsu is running..
Code:
ps |grep -w daemonsu
Could you think of anything else that might cause this?
Edit: Chainfire's SuperSU xda thread is here: http://forum.xda-developers.com/showthread.php?t=1538053
You could post a query there if you wish..

mrhnet said:
Yup, it doesn't come in app list if set to grant/deny for me too. Could be normal.
I've run out of ideas.. One last checking...
Can you check with Root Validator app here https://play.google.com/store/apps/details?id=eu.thedarken.rootvalidator
My one is like this
See what's the difference in prompt/grant modes for you.
#And, do this command in terminal to see su permissions
Code:
ls -l /system/xbin/su
#What I would do as a last resort is to reflash the rom and root again (AFTER taking a full cwm backup). Btw, is the ROM you flashed pre-rooted? Is there another su binary in another (conflict?) location like /system/bin..? (Root Validator app would indicate about it anyway). For this you can do..
Code:
find /system -name "su"
#also, check whether daemonsu is running..
Code:
ps |grep -w daemonsu
Could you think of anything else that might cause this?
Edit: Chainfire's SuperSU xda thread is here: http://forum.xda-developers.com/showthread.php?t=1538053
You could post a query there if you wish..
Click to expand...
Click to collapse
Here's my Root Validator (in grant mode)

And here is the terminal output.. Sorry for individual posts.. I can't seem to attach more than one pic at a time (possibly because I'm on an iPad)

Those outputs are similar to mine. Sorry mate.. no idea what to do next. Suggest making a query in Chainfire's SuperSU thread. Don't forget to attach the logcat in your post (after attempting in "prompt" mode).
Catlog app is an easier way to get logcats (need root for that, so run that app in grant mode when collecting logcat).

Lollipop OTA Update via ADB - Keep Data - Restore Root

Just thought I'd share, might help someone. This is for Nexus 7 previously bootloader unlocked and rooted (and whatever else, like xposed) going from 4.4.4 to 5. If you're not on 4.4.4 and bootloader unlocked get there first. Obviously you need usb debugging on.
You also need some form of adb and fastboot. I used Minimal ADB from here:
http://forum.xda-developers.com/showthread.php?t=2317790
What I Did:
- Got the Lollipop OTA from the links posted everywhere by now, including the second sticky here in General.
Put a copy in the adb/fasboot folder in Windows, and renamed the file to updatelollipop.zip to make it easier to handle.
Tried old style of updating: Uninstall Xposed, flash Xposed Disabler, flash OTA zip from custom recovery. Failed. Tried again, failed again.
But this was expected, as I'd read that the way lollipop updates is different from all previous updates and will fail at the slightest discrepancy in system partition.
So, need clean system.
- Got the Stock 4.4.4 firmware from Google: https://developers.google.com/android/nexus/images
Inside the firmware file found the system.img and recovery.img images.
Put these two files in the same folder as minimal adb and fastboot.
- Got into bootloader.
if powered off hold power and volume down keys. if booted up in Minimal ADB command prompt window type:
adb reboot bootloader
- flashed stock system and recovery
fastboot flash system system.img
fastboot flash recovery recovery.img
- Got into stock recovery
In bootloader, scrolled to select recovery, then with "No Command" showing held power and clicked volume up.
Select apply update from adb. Screen says to type adb sideload update from computer.
Ran into a hiccup. ADB would not recognize my N7. typing "adb devices" returned empty result. Booted up into Android, computer and adb recognized device fine. typed adb reboot bootloader, and in bootloader adb no go.
So while connected to computer in bootloader mode, went into Device Manager in Windows. Sure enough there was unknown device called grouper. Promptly update the driver. I used driver files from the Wugfresh toolkit I had installed. The device was recognized as Google Galaxy Nexus ADB device. Didn't matter to me as long as it was recognized as ADB. If you want official drivers you can get them from Asus here: http://support.asus.com/Download.aspx?SLanguage=en&m=Nexus+7&p=28&s=2
- Back into ADB sideload screen in N7 stock recovery.
typed adb sideload updatelollipop.zip
Let the ADB push the file, then stock recovery did the update. no issues. back in recovery might as well erase cache partition.
Root then. Could use Wugfresh NRT but decided to go manual.
UPDATE: As of SuperSU 2.27 Beta, flashing SuperSU from custom recovery is enough to gain root on Lollipop 5.0. Root kernel is no longer needed!
Old fashioned root failed works now: get the latest twrp recovery (copied it into adb folder, renamed it to twrprecovery.img), get the latest superSU (put it anywhere in N7 internal storage), flash the latter with the former:
In command prompt, typed fastboot boot twrprecovery.img
this temp booted twrp. promptly went to install, found superSU zip, flashed it.
Booted into Android, Lollipop looks nice, but No Root.
Again, not surprised, had already read lollipop needs modified kernel for root. Looked in the Wugfresh NRT files, had two candidates, modified boot img and root kernel img. not sure the difference, but the two files had different file sizes, and I had read somewhere that modified kernel would keep most of the security features of stock kernel, only modifying permissions needed for root, so decided to go with the kernel img file. Copied it over to adb fastboot folder, renamed it rootboot.img
- got back into bootloader. in command prompt typed
fastboot flash boot rootboot.img
Rebooted into Android, had root! Great. Notice didn't need to flash superSU a second time.
To check if root works fine, just open superSU app. If it opens fine then you're good. Root apps will ask for root, and granting will work fine, but that doesn't mean the apps will be able to use root for the simple reason that they might need to be updated. for example, es file manager asked for root, was granted, but root directories showed empty. clearly needs an update. Tried Total Commander, gave root, worked fine. So apps ability to use root in lollipop will vary based on their need to be updated to work.
thanks as always to Wugfresh and Chainfire.

"Unknown Device" when USB Debugging On
Speaking of root apps needing update, one app that needed updating if you use it, is Adbd Insecure. Why am I singling it out? Because it had me running around in circles trying to figure out why Windows was claiming my N7 was an Unknown Device.
Thing is, I installed adbd insecure long ago set on auto start, and it's useful for when it's needed, but I had completely forgotten about it now when trying to figure out the driver issue. Turning off USB debugging Windows happily recognized MTP, but who wants debugging off, it's a bad idea.
After twirling in circles finally decided to check if Windows would recognize bootloader and recovery mode. Sure enough, everything was good there. Rebooted into Android and noticed ADB was recognized briefly upon startup before it went away. That got me suspicious which led me to the culprit. So, yeah, save yourself some trouble and update that app, if you have it running.

Question Easiest way to just modify etc/hosts.

For digital wellbeing reasons* I'd like to lock myself out a handful of websites by redirecting them to local.
I've tried to follow the guideline using Magisk, only to nearly brick my phone (a friend had to flash the original image). What is the easiest way to simply modify the hosts file without changing too much?
lg lngo

I've been using this Magisk module for a long to block Ads. Just edit etc/hosts and install!

That means you recommend to simply follow this guideline and install Magisk including this plugin?

It may be that the websites you are concerned about are blocked in the hostlist that AdAway would install. If your phone is rooted, consider installing AdAway. I think it can only be installed using F-Droid.

@Rafiul Bari Chowdhury: I edited the hosts file in your zipped module, run it in Magisk: worked fine, after restart I saw the changes (shell cat /etc/hosts). However, after locking it again the device is bricked. I'm looking how to flash the factory image again.
Any ideas what went wrong? Is it not possible to edit root files and relock the phone again so it seems "normal"?
Edit: re-unlocked the phone and it works again. Reset OS (and hosts file), but works. When locked again: "Can't find valid operating system". Any ideas?

Fnokrer said:
@Rafiul Bari Chowdhury: I edited the hosts file in your zipped module, run it in Magisk: worked fine, after restart I saw the changes (shell cat /etc/hosts). However, after locking it again the device is bricked. I'm looking how to flash the factory image again.
Any ideas what went wrong? Is it not possible to edit root files and relock the phone again so it seems "normal"?
Edit: re-unlocked the phone and it works again. Reset OS, but works. When locked again: "Can't find valid operating system". Any ideas?
Click to expand...
Click to collapse
i doubt the phone is bricked. it is either locked up that you can force off by holding down power + vol up + vol down all 3 at the same time for 15 to 30 seconds to force off. you can get into boot loader by power + vol down. then flash the stock image from https://developers.google.com/android/images#barbet
make sure you have the google usb drivers and use chrome installed or nothing work when trying to flash back to stock.
it pretty hard to mess up the bootloader section of the phone. it can be done but you would have to flash a corrupt image to the boot partition.
i use to use adaway https://github.com/AdAway/AdAway/releases/tag/v5.12.0 if i remember right you can modify the host file using that apk

I did id all over again: Flashed latest firmware (barbet-sp2a.220305.012), installed Magisk acc. to Guideline here in the forum. Same result.
Phone wasn't bricked, Boot loader worked fine all the time, sorry for unprecise description. Editing the hosts file simply doesn't last (maybe I have to change the file on partition A and b??!) and 2nd, if locked again the phone won't find the OS.
Gives me two questions:
1.) how actually does the script from Rafiul Bari Chowdhury work, how can it replace the hosts file while I can't do it manually due to read-only partition.
2.) If I change both partitions, A and B, would the change last after I lock the phone again? Then how do I do it and how do I make sure the OS is found.
Is it even possible to change system files and go back into "locked" mode again without any other impacts?

Fnokrer said:
I did id all over again: Flashed latest firmware (barbet-sp2a.220305.012), installed Magisk acc. to Guideline here in the forum. Same result.
Phone wasn't bricked, Boot loader worked fine all the time, sorry for unprecise description. Editing the hosts file simply doesn't last (maybe I have to change the file on partition A and b??!) and 2nd, if locked again the phone won't find the OS.
Gives me two questions:
1.) how actually does the script from Rafiul Bari Chowdhury work, how can it replace the hosts file while I can't do it manually due to read-only partition.
2.) If I change both partitions, A and B, would the change last after I lock the phone again? Then how do I do it and how do I make sure the OS is found.
Is it even possible to change system files and go back into "locked" mode again without any other impacts?
Click to expand...
Click to collapse
did you try adb shell then su ? you can try chmod -R 775 or 777 a file to give full permisions. you probably could get away with just 660 for read and write without execute command. so chmod -R 660 (filename) should allow you to change the file permisions and allow you to write to the file.
as for relocking. i usually leave mine unlocked. i think if you relock it does a verification process of the rom. not sure on that one. maybe a developer can answer that question.

Hey I am trying to figure this out. did OP ever find an answer?
For me, I am on a pixel 5 with android 13, a phone I got from Backmarket. It is an "Unlocked" pixel 5. I thought this would make things easier. According to an article, pixel 5 is "one of the easiest phones to root"
:/
The phone is not A/B, only A
I pulled the magisk image using adb to the file with platform tools
I tried sideloading a hosts file through ADB but I got Error 21.
I have tried rooting the phone with Magisk boot.img but it fails because in Fastboot "Remote: failed to write to partition not found" and in FastbootD there is also an error.
SU is not found when I attempt to use the adb shell. It is Greyed out in the Magisk App
I have mounted the /system with Recovery but then I receive "Remote: no such file or directory"
I am using the most current Platform tools.
Any advice? Really I just want to edit the hosts file

Gnome_chomsky said:
Hey I am trying to figure this out. did OP ever find an answer?
For me, I am on a pixel 5 with android 13, a phone I got from Backmarket. It is an "Unlocked" pixel 5. I thought this would make things easier. According to an article, pixel 5 is "one of the easiest phones to root"
:/
The phone is not A/B, only A
I pulled the magisk image using adb to the file with platform tools
I tried sideloading a hosts file through ADB but I got Error 21.
I have tried rooting the phone with Magisk boot.img but it fails because in Fastboot "Remote: failed to write to partition not found" and in FastbootD there is also an error.
SU is not found when I attempt to use the adb shell. It is Greyed out in the Magisk App
I have mounted the /system with Recovery but then I receive "Remote: no such file or directory"
I am using the most current Platform tools.
Any advice? Really I just want to edit the hosts file
Click to expand...
Click to collapse
Don't do this method...
Once you're rooted with Magisk, open Magisk and go to settings and tap Systemless hosts. This installs the Systemless Hosts module. Then you can just use an app like AdAway (https://f-droid.org/en/packages/org.adaway/) and block the domains you want there.