I cannot get the ad blocking host files to stick with this device. I have tried both Adfree Android and Adaway. The host files won't survive a reboot. Sometimes, I apply them and they revert back after a few hours of use. I am just wondering if anyone else has experienced this issue on this device. SU is functioning properly.
Peace
Not exactly the same, but I noticed any app I remove via Titanium Backup gets restored on reboot as well.
Both of these actions require writing to /system, which cannot be done with android booted up, until we have s-off.
Every time I try to write to system (On accident by running some root app without thinking about it) my device reboots. I figured that was normal for a rooted S-on device. That doesn't happen to y'all?
trickster2369 said:
Both of these actions require writing to /system, which cannot be done with android booted up, until we have s-off.
Click to expand...
Click to collapse
I am pretty sure I was able to do this on the Rezound prior to S off. Also, how can one flash a ROM if your not able to write to the system?
I just want to understand this a little bit better. Thanks.
Irieone said:
I am pretty sure I was able to do this on the Rezound prior to S off. Also, how can one flash a ROM if your not able to write to the system?
I just want to understand this a little bit better. Thanks.
Click to expand...
Click to collapse
you can not write to /system with android booted up.
So you can flash a rom in recovery but you cant edit anything in /system while in android
Irieone said:
I am pretty sure I was able to do this on the Rezound prior to S off. Also, how can one flash a ROM if your not able to write to the system?
I just want to understand this a little bit better. Thanks.
Click to expand...
Click to collapse
On all the newer phones, HTC (or Verizon) write-locked \system while the phone is booted in android. :good: But you're right, on the Rezound, you could write to \system while still S-ON.
so I guess to debloat, someone will have to make one of those debloating tools that delete through adb.
nrfitchett4 said:
so I guess to debloat, someone will have to make one of those debloating tools that delete through adb.
Click to expand...
Click to collapse
This has already been done my friend look in the development section. Also I think I saw a script that you can run in recovery that ads ad blocking hosts! CHEERS:highfive:
Here you go:
ad block is on that other site => http://rootzwiki.com/topic/36775-mod-debloater-adblock-restore-v3/
and theres some debloat love here in development => http://forum.xda-developers.com/showthread.php?t=2012388
nrfitchett4 said:
so I guess to debloat, someone will have to make one of those debloating tools that delete through adb.
Click to expand...
Click to collapse
Freezing in TiBu appears to work.
Going to have a go with AdBlock Plus since its supposed to work without root.
https://play.google.com/store/apps/details?id=org.adblockplus.android&feature=nav_result#?t=W251bGwsMSwyLDNd
Irieone said:
Going to have a go with AdBlock Plus since its supposed to work without root.
https://play.google.com/store/apps/details?id=org.adblockplus.android&feature=nav_result#?t=W251bGwsMSwyLDNd
Click to expand...
Click to collapse
Screw that who wants that running in the background, run AdFree and update hosts, hook up USB with debugging on and use ADB:
"adb shell" then "su" and grant yourself root. Then "cp /system/etc/hosts /sdcard" then type "exit" and "exit" to get out of the shell.
Then run "adb reboot recovery" and mount /system partition in recovery. Then "adb shell" and "cp /sdcard/hosts /system/etc/hosts" -- exit shell and reboot
Done
Do this or just push the host file http://db.tt/LQAUEcZM to /system/etc/ with the built in TWRP file manager if you don't want to use ADB.
Nowak4G said:
Do this or just push the host file http://db.tt/LQAUEcZM to /system/etc/ with the built in TWRP file manager if you don't want to use ADB.
Click to expand...
Click to collapse
Is anybody having trouble creating this symlink as instructed in AdAway on their Droid DNA?
I type the command and all I get is "ln: /system/etc/hosts: File exists"
I exit, reboot and the app still tells me the symlink is missing.
I'll be the first to admit my adb-fu is weak, probably my fault.
Edit: so, I did it the other way. When the app tells you the symlink failed it still creates a hosts file in data/data. I used TWRP/Advanced/File Manager to move this into system/etc.
Still, it would be nice to get the symlink working and have AdAway update automatically rather than having to go through this process periodically.
disc0rdian said:
Screw that who wants that running in the background, run AdFree and update hosts, hook up USB with debugging on and use ADB:
"adb shell" then "su" and grant yourself root. Then "cp /system/etc/hosts /sdcard" then type "exit" and "exit" to get out of the shell.
Then run "adb reboot recovery" and mount /system partition in recovery. Then "adb shell" and "cp /sdcard/hosts /system/etc/hosts" -- exit shell and reboot
Done
Click to expand...
Click to collapse
This is exactly what I did. I used root explorer to copy the host file from /system/etc and pasted it on the sdcard
Rebooted into recovery, mounted /sdcard and /system and ran adb to push the file
viola! done
^^
I think that's basically doing the same thing I did, but still the symlink would be nice so it could be automatically updated.
---------- Post added at 09:02 PM ---------- Previous post was at 08:44 PM ----------
OK, got a little tech support off the DNA IRC. As I suspected, I'm just dumb
Make sure to delete any existing system/etc/hosts and data/data/hosts before you run the command.
Works fine now!
Now that we have s-off, what are you guys using to block ads?
andyroidna said:
Now that we have s-off, what are you guys using to block ads?
Click to expand...
Click to collapse
The same thing we've been doing for the past 3 months. Nothing had changed in that respect since kernels with system write enabled came out.
Sent from my HTC6435LVW using xda app-developers app
Related
Thanks goes to #TeamWin for Temp Root
This is For Windows only, if you wish to make it work for linux or mac help your self...
Remember, This is still a Temp Root & any Changes made will be Rest back to stock on a Reboot
It's stable & works 100%
I Personally have not lost Root with this new Method
Q. I thought RW was Fixed?
A. Caused by Deleting an apk / file that was already deleted. Journaling shows it still there!
Keep Track of what you delete, as trying to delete something off system that you alread di hangs the /system into RO state.
Before Using!!HTC Sync Must be Turned OFF
Put the Phone into Charge Mode only ( Not Disk Drive )
USB Debugging Must be Turned on
What's Fixed:
Revamped due to new Method:
~ Superuser Apps now Function
~ If you Lose Root, all you have to do is Open terminal & type SU then type fixit! > No More Rebooting & running the exploit again for R/W on system to get Root back in place
~ Fixed R/O Bug!!
~ R/W is now Forced
~ /system is fully editable now! until reboot that is.
~ Busybox is installed to /vendor/bin
~ hex Edited libext4
~ hex edited libfuse.so
~~ This is the Last Update due to it working & Stable ~~
Download for RW HTC Sensation 4G:
````````````````````````````````````````````````````````````````````````````````````````````
Download for RW HTC Evo 3D:
````````````````````````````````````````````````````````````````````````````````````````````
Download for RW HTC Flyer 16GB/32GB:
````````````````````````````````````````````````````````````````````````````````````````````
Download for RW HTC Evo View:
Q. Is this permanent?
A. no, it's a temp root method..
Q. Will I lose SU Access at some point while running the OS?
A. You might, but open terminal & type fixit to get root back!.
Q. What about apps that need a reboot to use superuser?
A. Use Fast Reboot form the market for app that need a reboot..
Q. Can I push & remove items to system & will it work?
A. Yes, but all changes are reset on a reboot.
Once Downloaded, Unzip & double click on the Run_ME_fre3vo_Root.bat File & Enjoy long lasting Root!
OLD NEWS:
Everyone knows that currently with any temp root, you still lose links to the SU Binary & Busybox links, it's just a matter of time before it happens!!
So after digging around somewhat I found an over sight that HTC might use later for system updates via /vendor/bin, who knows at this point though... Anyways, after amount of time the SU Binary along with busybox links if be in system/bin or /system/xbin gets deleted / removed..
Now, what I did was enable the $Path to /vendor/bin which is in the Sensation export PATH..
Any Calls made from this point either be SU or Busybox don't get deleted nor touched from any App requesting the SU Binary!! I've tested this with alot of apps & the Root sticks in place..
Other than Reboot, it might as well be a Perma-Temp-Root!!
Downloading now!!! Can't wait to test it!
***EDIT***
Rooted perfectly, opened and closed Titanium Backup several times with no force closes or loss of su, Barnacle is perfect, Wireless tether is granted su but the kernel doesn't support it, screenshot gained su also but the screenshots were smeared colors. Drocap2 takes perfect screenies though. Gonna try a few more root apps before bed and play some more when I wake up to verify it lasts.
going to try this now!
Ran the script and no root
script stays on
daemon started successfully :/
eugene373 said:
Thanks goes to #TeamWin for Temp Root!!!
Everyone knows that currently with any temp root, you still lose links to the SU Binary & Busybox links, it's just a matter of time before it happens!!
So after digging around somewhat I found an over sight that HTC might use later for system updates via /vendor/bin, who knows at this point though... Anyways, after amount of time the SU Binary along with busybox links if be in system/bin or /system/xbin gets deleted / removed..
Now, what I did was enable the $Path to /vendor/bin which is in the Sensation & Evo 3D export PATH..
Any Calls made from this point either be SU or Busybox don't get deleted nor touched from any App requesting the SU Binary!! I've tested this with alot of apps & the Root sticks in place..
Other than Reboot, it might as well be a Perma-Temp-Root!!
This is For Windows only, if you wish to make it work for linux or mac help your self...
If you have trouble with the Superuser.apk, uninstall first & reboot then run the .bat file again..
What is installed?
Busybox w/ symlinks
Superuser.apk
SU Binary
Fre3vo
sqlite3
What's Removed?
slackerradio.apk
TMOUS_Navigator.apk
Transfer-pyramid-8.30.0.26-S30.apk
Protips.apk
IdleScreen_Stock.apk
HtcTipWidget.apk
com.htc.TrendsWidget.apk
com.mobitv.client.tmobiletvhd.apk
FusionStockWidget.apk
Stock.apk
So without further ado, the link!
http://www.multiupload.com/LBEYIFVD58
Once Downloaded, Unzip & double click on the Run_ME_fre3vo_Root.bat File & Enjoy long lasting Root!
Last edited by Eugene373; Today at 05:51 AM.
Click to expand...
Click to collapse
Is there any chance u can edit the script or tell me how to edit it so it doesn't remove anything. Thanks.
perfect works great!!! Managed to restore TB! Will try out wifi tethering right now and other su required apps! Thank you! <3
I guess I don't understand.
How is removing anything from /system/app gonna stick?
This worked perfect for me. No problems with it. Wifi tether won't work for me, but barnacle tether works perfectly. Drocap2 is taking perfect screen shots for me as well, where as before the images would be all distorted and what not.
Made some changes to the .bat since I don't necessarily want to disable all of that yet, but it works, this is the longest superuser has worked for me so far on the EVO 3D.
k2buckley said:
This worked perfect for me. No problems with it. Wifi tether won't work for me, but barnacle tether works perfectly. Drocap2 is taking perfect screen shots for me as well, where as before the images would be all distorted and what not.
Click to expand...
Click to collapse
How'd you get Barnacle to work?
EDIT:
Sorry my tablet doesn't read Ad-Hoc >_>
Is anybody able to root the E3D with this method? I tried twice and it failed both times. I will do again by restart my pc and E3D.
urcboss07 said:
Is anybody able to root the E3D with this method? I tried twice and it failed both times. I will do again by restart my pc and E3D.
Click to expand...
Click to collapse
Yeah....First try.
nabbed said:
I guess I don't understand.
How is removing anything from /system/app gonna stick?
Click to expand...
Click to collapse
It won't stick, but after you reboot you run the batch program again and the apps are removed again until your next reboot.
hockeyfamily737 said:
It won't stick, but after you reboot you run the batch program again and the apps are removed again until your next reboot.
Click to expand...
Click to collapse
So, it will not stick as said, right?
Tiffany84 said:
Is there any chance u can edit the script or tell me how to edit it so it doesn't remove anything. Thanks.
Click to expand...
Click to collapse
a .bat file is just a text document that is executed in command prompt. If you are familiar with cmd just open the file in notepad, delete any commands you don't want executed, save.
urcboss07 said:
So, it will not stick as said, right?
Click to expand...
Click to collapse
Not through a full reboot....no you will have to run the batch file again (even says so in the OP). However, the other root methods would crash periodically even without a reboot or would last but not give you access to the majority of your root apps. This is the closest yet to a feasible root solution.
mine doesnt get past daemon started successfully i have usb debugging on
so if i downloaded and installed some apps that require root,
and i reboot, what happens to them ?
they will work after running the bat file again ?
or they will have to be installed again to work properly ?
thanks !
EDIT: i haven't done my due diligence (searching and reading)
but it's 5 am so i'll ask ...
what works for screen capture and for wireless tethering ?
lowetax said:
so if i downloaded and installed some apps that require root,
and i reboot, what happens to them ?
they will work after running the bat file again ?
or they will have to be installed again to work properly ?
thanks !
Click to expand...
Click to collapse
They will work after running the .bat file again. You shouldn't need to uninstall and reinstall them. Super User may need to be uninstalled before running the .bat file again, if it gives you any force closes.
Sent from my PG86100 using XDA App
hi everyone. i got my htc rezound on friday and have been fighting with it most of the weekend. i have the bootloader unlocked and (i assume) root achieved via amon ra. i cant get rid of the bloatware via multiple bloat removal tools, and its starting to make me hate life. can someone just tell me how i get to /system/apps so i can do it myself?
thanks.
Get a root explorer and it will allow you to remove the apks.
EmerikL said:
Get a root explorer and it will allow you to remove the apks.
Click to expand...
Click to collapse
thanks, that was excruciatingly simple. i grabbed an app and apparently perm root didnt take. going to need to try again after work.
im new to all this stuff with phones, i should have learned with my incredible 1 but it was satisfactory out of the box. seems like everything HTC with the newest version is full of bloat and runs like garbage. the last OTA to incredible nearly bricked the phone, i had to manually reprogram it to get back on the network; verizon tech support didnt do jack.
ill keep reading over these forums and learning as much as i can. any suggestions for this phone are greatly appreciated. currently im using the stock sense UI and stock kernel. i like the UI as it is, dont plan on modding it, just need to get rid of bloat.
Madnapali said:
hi everyone. i got my htc rezound on friday and have been fighting with it most of the weekend. i have the bootloader unlocked and (i assume) root achieved via amon ra. i cant get rid of the bloatware via multiple bloat removal tools, and its starting to make me hate life. can someone just tell me how i get to /system/apps so i can do it myself?
thanks.
Click to expand...
Click to collapse
Are you sure you're rooted and unlocked? You did the HTC unlock dance, right?
The reason I ask is that you say you achieved root via Amon Ra.....and Amon Ra doesn't get you root; it's a recovery vehicle/manager. Anyway, have you seen this thread?
HTH
rfarrah said:
Are you sure you're rooted and unlocked? You did the HTC unlock dance, right?
The reason I ask is that you say you achieved root via Amon Ra.....and Amon Ra doesn't get you root; it's a recovery vehicle/manager. Anyway, have you seen this thread?
HTH
Click to expand...
Click to collapse
i cant be sure im rooted, but i am unlocked. i watched the bootloader unlock myself, and it says 'unlocked' at the top of the hboot screen.
i have no idea how to see if i have root, though, and i know i dont right now.
as for that thread, yes, i have all that on my PC at home and tried it earlier today. unfortunately, i had previously used a different method, so i skipped straight up to the part after the unlock. the other method i used had me get into amon ra and use the su installer, which is why i mentioned that.
any other suggestions? im all ears heh.
rfarrah said:
Are you sure you're rooted and unlocked? You did the HTC unlock dance, right?
The reason I ask is that you say you achieved root via Amon Ra.....and Amon Ra doesn't get you root; it's a recovery vehicle/manager. Anyway, have you seen this thread?
HTH
Click to expand...
Click to collapse
No Amon Ra has the functionality to install su. It's been one of the only ways to obtain root after the OTA.
Sent from my ADR6425LVW using xda premium
Madnapali said:
i cant be sure im rooted, but i am unlocked. i watched the bootloader unlock myself, and it says 'unlocked' at the top of the hboot screen.
i have no idea how to see if i have root, though, and i know i dont right now.
as for that thread, yes, i have all that on my PC at home and tried it earlier today. unfortunately, i had previously used a different method, so i skipped straight up to the part after the unlock. the other method i used had me get into amon ra and use the su installer, which is why i mentioned that.
any other suggestions? im all ears heh.
Click to expand...
Click to collapse
Okay, then this: procedure.
if you haven't done this from beginning to end (incl step 7), you may not be perm-rooted. Good luck!
rfarrah said:
Okay, then this: procedure.
if you haven't done this from beginning to end (incl step 7), you may not be perm-rooted. Good luck!
Click to expand...
Click to collapse
actually... i think that is the first method i used LOL. either way, im going to factory reset my phone and go with hasoon2000's tool.
let me preface this by again stating i have the bootloader unlocked and can prove it with a picture if i have to.
ok, i factory reset my phone and used amon ra to install superuser. this did not work.
superuser says 'no apps in list.' ES file explorer tells me i cant delete Blockbuster.apk. terminal emulator says it is read only. after rebooting my phone, terminal emulator's keyboard is stuck in all caps mode (weird) and i cant even cd.
this is what i get when i use hasoon's method (cant post about this there cuz i dont have 10 posts ):
Code:
C:\Rezound_All-In-One_Kit_V1.0\data>adb shell mount /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
C:\Rezound_All-In-One_Kit_V1.0\data>adb push SU/Superuser.apk /system/app
failed to copy 'SU/Superuser.apk' to '/system/app/Superuser.apk': Read-only file
system
C:\Rezound_All-In-One_Kit_V1.0\data>adb push SU/androidterm.apk /system/app
failed to copy 'SU/androidterm.apk' to '/system/app/androidterm.apk': Read-only
file system
C:\Rezound_All-In-One_Kit_V1.0\data>adb push SU/Busybox /system/app
failed to copy 'SU/Busybox' to '/system/app/Busybox': Read-only file system
C:\Rezound_All-In-One_Kit_V1.0\data>adb push SU/Busybox /system/bin
failed to copy 'SU/Busybox' to '/system/bin/Busybox': Read-only file system
C:\Rezound_All-In-One_Kit_V1.0\data>adb push SU/su /system/app
failed to copy 'SU/su' to '/system/app/su': Read-only file system
C:\Rezound_All-In-One_Kit_V1.0\data>adb push SU/su /system/bin
failed to copy 'SU/su' to '/system/bin/su': Read-only file system
C:\Rezound_All-In-One_Kit_V1.0\data>pause
Press any key to continue . . .
Madnapali said:
let me preface this by again stating i have the bootloader unlocked and can prove it with a picture if i have to.
ok, i factory reset my phone and used amon ra to install superuser. this did not work.
superuser says 'no apps in list.' ES file explorer tells me i cant delete Blockbuster.apk. terminal emulator says it is read only. after rebooting my phone, terminal emulator's keyboard is stuck in all caps mode (weird) and i cant even cd.
this is what i get when i use hasoon's method (cant post about this there cuz i dont have 10 posts ):
Code:
C:\Rezound_All-In-One_Kit_V1.0\data>adb shell mount /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
C:\Rezound_All-In-One_Kit_V1.0\data>adb push SU/Superuser.apk /system/app
failed to copy 'SU/Superuser.apk' to '/system/app/Superuser.apk': Read-only file
system
C:\Rezound_All-In-One_Kit_V1.0\data>adb push SU/androidterm.apk /system/app
failed to copy 'SU/androidterm.apk' to '/system/app/androidterm.apk': Read-only
file system
C:\Rezound_All-In-One_Kit_V1.0\data>adb push SU/Busybox /system/app
failed to copy 'SU/Busybox' to '/system/app/Busybox': Read-only file system
C:\Rezound_All-In-One_Kit_V1.0\data>adb push SU/Busybox /system/bin
failed to copy 'SU/Busybox' to '/system/bin/Busybox': Read-only file system
C:\Rezound_All-In-One_Kit_V1.0\data>adb push SU/su /system/app
failed to copy 'SU/su' to '/system/app/su': Read-only file system
C:\Rezound_All-In-One_Kit_V1.0\data>adb push SU/su /system/bin
failed to copy 'SU/su' to '/system/bin/su': Read-only file system
C:\Rezound_All-In-One_Kit_V1.0\data>pause
Press any key to continue . . .
Click to expand...
Click to collapse
You don't have root. Install this by flashing it in Amon Ra, that should give you root. Then rerun the tool.
EmerikL said:
You don't have root. Install this by flashing it in Amon Ra, that should give you root. Then rerun the tool.
Click to expand...
Click to collapse
flashed the zip from amon ra and restarted so hasoon's permroot could run. still says read only file system.
im beginning to think no one has actually rooted the rezound, and this is an elaborate, worldwide prank on me lol.
if your in root explorer you need to press on the read only to change it to read write. Probably the same with any file manager. Default is read only.
Sent from my ADR6425LVW using xda premium
mjh68 said:
if your in root explorer you need to press on the read only to change it to read write. Probably the same with any file manager. Default is read only.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
!!!!!!!!!!!!!!!!!!!!!!!!!!!
you, sir, are the winner of the day. you have earned yourself a lifetime supply of HUGS! lol, thanks much.
ok, its not over yet. i removed a bunch of the .apk files for crapps i dont use, but the shortcuts still exist in the app menu and the processes still run. i verified that the .apk files are still gone.
also, the HTC people widgets are mysteriously gone .
what next?
Madnapali said:
ok, its not over yet. i removed a bunch of the .apk files for crapps i dont use, but the shortcuts still exist in the app menu and the processes still run. i verified that the .apk files are still gone.
also, the HTC people widgets are mysteriously gone .
what next?
Click to expand...
Click to collapse
Have you rebooted after your changes?
I would have used titanium backup first to freeze the apps that I am thinking about removing. And then moving them to a safe place rather than deleting them so that if I have to, I can put them back if there is a bad result.
krelvinaz said:
Have you rebooted after your changes?
I would have used titanium backup first to freeze the apps that I am thinking about removing. And then moving them to a safe place rather than deleting them so that if I have to, I can put them back if there is a bad result.
Click to expand...
Click to collapse
yeah, i rebooted. i dont understand... why would i have to freeze apps and move them? i own the stupid phone, cant i just delete this crap and forget about it?
i swear to god, this is more frustrating than buying a laptop from best buy...
Madnapali said:
yeah, i rebooted. i dont understand... why would i have to freeze apps and move them? i own the stupid phone, cant i just delete this crap and forget about it?
i swear to god, this is more frustrating than buying a laptop from best buy...
Click to expand...
Click to collapse
Simple. If you remove the wrong thing, you may have problems trying to put it back. Without having to reload the ROM again and start over.
Remove the wrong things... and you have a non-working phone.
By freezing them, you can see the affects before you perm remove them. If you move them instead of deleting them, you can put them back. If you delete them, sometimes even TB can't restore them.
It comes down to how much time you want to put into this...
krelvinaz said:
Simple. If you remove the wrong thing, you may have problems trying to put it back. Without having to reload the ROM again and start over.
Remove the wrong things... and you have a non-working phone.
By freezing them, you can see the affects before you perm remove them. If you move them instead of deleting them, you can put them back. If you delete them, sometimes even TB can't restore them.
It comes down to how much time you want to put into this...
Click to expand...
Click to collapse
edit: got it! thanks everyone for responding!
EmerikL said:
You don't have root. Install this by flashing it in Amon Ra, that should give you root. Then rerun the tool.
Click to expand...
Click to collapse
Seems that the AIO Tool's permaroot had problems and this did the trick. Thanks to you and the OP!
Here is a complete guide for anyone interested in rooting the HTC Droid DNA. The insecure boot image, TWRP recovery, CWM recovery and SuperSU files used in this guide are not my own developments, and their developers have been credited in the end of this post.
I am only writing this as a newbie-friendly guide for everyone, and am providing my own SuperSU, su and busybox installer zip file that includes everything you need for full root.
Unlock the bootloader of your device by visiting the HTC bootloader unlock page. Warning: This will wipe your data.
UPDATE: Thanks to Verizon, the official bootloader unlocking method mentioned above no longer works. Please refer to this method for unlocking the bootloader.
Download ClockworkMod or TWRP recovery for the device and rename it to recovery.img (or keep the existing name and change recovery.img in the command below to that name).
Download the SuperSU and busybox package and put it on your SD card.
Put your phone into bootloader mode and connect it to your PC via USB.
On your computer, make sure you are in the folder where you downloaded the recovery file and use this command to flash the recovery:
Code:
fastboot flash recovery recovery.img
Finally, reboot your device into recovery, flash the SuperSU and busybox package and reboot your device.
You should now have root access.
Credits:
jcase for unlocking the bootloader after Verizon decided to lock it.
dsb9938 for sharing the CWM port and correcting me regarding my previously posted and now removed second method involving his insecure boot image
Dees_Troy for TWRP recovery.
utkanos for CWM port.
Chainfire for developing SuperSU
I have tried to credit everyone involved but if I have missed out on anyone, please do let me know.
thanks for the guide!
just one question though. when you say "Download the SuperSU and busybox package and put it on your SD card.", what do you mean exactly by SD card? doesn't the DNA not have a SD card? sorry if this is a dumb question. i've never rooted a phone before :/
hotmonkas said:
thanks for the guide!
just one question though. when you say "Download the SuperSU and busybox package and put it on your SD card.", what do you mean exactly by SD card? doesn't the DNA not have a SD card? sorry if this is a dumb question. i've never rooted a phone before :/
Click to expand...
Click to collapse
Internal storage would be another name for the SD card.
touretts69 said:
Internal storage would be another name for the SD card.
Click to expand...
Click to collapse
ah okay, thank you
which device do u use on the htc page?
nyjw said:
which device do u use on the htc page?
Click to expand...
Click to collapse
"Other devices", or similar.
Sent from my ADR6425LVW using xda premium
Awesomeness.
The fact that this phone is rooted a week before its even out... simply awesome. I love XDA!
So excited for this phone.
HQRaja said:
Code:
adb shell mount -o remount,rw /system
[LIST=1]
[*] adb push su /system/bin/
adb push Superuser.apk /system/app/
adb push busybox /system/xbin/
adb shell
chmod 06755 /system/bin/su
chmod 0644 /system/app/Superuser.apk
chmod 04755 /system/xbin/busybox
cd /system/xbin
busybox --install /system/xbin/
exit
exit
[*]Reboot your device.
[/LIST]
Click to expand...
Click to collapse
This will not work. You cannot write to /system except in recovery.
This is why I did not publish my initial root method. Using a package and flashing in recovery is the only way to get files on /system without some really gnarly stuff.
D
.
dsb9938 said:
This will not work. You cannot write to /system except in recovery.
This is why I did not publish my initial root method. Using a package and flashing in recovery is the only way to get files on /system without some really gnarly stuff.
D
.
Click to expand...
Click to collapse
Thanks for your response. =)
Based on my understanding (and my experience with Nexus devices), once you boot using an insecure boot image, you have full root access in ADB since it is running adbd as root on the device. You can then successfully write to the /system partition and the changes persist after reboot. While I can confirm that the above will work on any Nexus device as well as any similar device with an unlocked bootloader and fastboot access, I am not 100% sure if that's how it works on HTC devices that have the S-ON flag. Are you referring to S-ON devices in particular here?
HQRaja said:
Thanks for your response. =)
Based on my understanding (and my experience with Nexus devices), once you boot using an insecure boot image, you have full root access in ADB since it is running adbd as root on the device. You can then successfully write to the /system partition and the changes persist after reboot. While I can confirm that the above will work on any Nexus device as well as any similar device with an unlocked bootloader and fastboot access, I am not 100% sure if that's how it works on HTC devices that have the S-ON flag. Are you referring to S-ON devices in particular here?
Click to expand...
Click to collapse
Normally it does work that way. And I was very disappointed that it did not on this phone, as I made the kernel just for that reason.
I think there was an error in the coding where it tells unlock which partitions to remove write protection from. That, or they just wanna make our lives hard for some reason.
Either way, you cannot write to /system while the phone is booted normally without S-Off. Even as root.
D
.
dsb9938 said:
Normally it does work that way. And I was very disappointed that it did not on this phone, as I made the kernel just for that reason.
I think there was an error in the coding where it tells unlock which partitions to remove write protection from. That, or they just wanna make our lives hard for some reason.
Either way, you cannot write to /system while the phone is booted normally without S-Off. Even as root.
D
.
Click to expand...
Click to collapse
Ah I see. Thanks for pointing that out. I'll remove the second method from my guide, since including that would be pointless if that's the case as you can now confirm.
So does this method work? Or not???Im confused with the last few posts. Thanks
suzook said:
So does this method work? Or not???Im confused with the last few posts. Thanks
Click to expand...
Click to collapse
Edited post is fine. He removed the part I was talking about.
D
.
What I want to know most if anyone knows..will the DNA through verizon be unlockable....I'm actually using the RAZR Maxx hd through verizon and Motorola has restricted unlocking the bootloader because of verizon
Sent from my DROID RAZR HD using xda app-developers app
Irish65 said:
What I want to know most if anyone knows..will the DNA through verizon be unlockable....I'm actually using the RAZR Maxx hd through verizon and Motorola has restricted unlocking the bootloader because of verizon
Sent from my DROID RAZR HD using xda app-developers app
Click to expand...
Click to collapse
You can't do any of this stuff without unlocking.
As of right now, it is working.
D
.
How do you do the command in the folder were u downloaded to like the instructions say?
idle0095 said:
How do you do the command in the folder were u downloaded to like the instructions say?
Click to expand...
Click to collapse
Please be more specific.
D
.
idle0095 said:
How do you do the command in the folder were u downloaded to like the instructions say?
Click to expand...
Click to collapse
In command prompt, use the "cd" command. The easiest way to do this is to make a folder at the root of your hard drive (C:\) and place all files you need to flash in here e.g. "C:\android\" Then in command prompt, type in "cd .." and press enter until it displays "C:\". Then type (if you use the same name as the example) "cd android" and it will enter the folder "C:\android\" where you placed the files. Now you can continue with the rest of the guide.
CastleBravo said:
In command prompt, use the "cd" command. The easiest way to do this is to make a folder at the root of your hard drive (C:\) and place all files you need to flash in here e.g. "C:\android\" Then in command prompt, type in "cd .." and press enter until it displays "C:\". Then type (if you use the same name as the example) "cd android" and it will enter the folder "C:\android\" where you placed the files. Now you can continue with the rest of the guide.
Click to expand...
Click to collapse
Or if on Windows, simply: Do the following in folder where files are located.
Shift+Right-Click > Open Command Window Here
I've never had an HTC device before but does using the HTC bootloader unlock is that making it s-off? Also I don't see the DROID dna on the list
Sent from my SCH-I535 using xda premium
I rooted my strange tablet using Kingo and apparently it was succesful:
http://i1312.photobucket.com/albums/t539/talos910/Screenshot_2015-09-11-17-08-20_zpsurdgzj8p.png
But I have been trying for days to erase a file in /system and I have not been able to do it, I think I have read every relevant thread about this problem but no luck, I tried using ES and changed /system to r/w in the root options but when trying to delete the file all I get is operation failed, the same happens with all the other root explorers and tools. I even tried the solution on this thread: http://forum.xda-developers.com/ascend-p7/help/edit-replace-write-files-set-immutable-t2884172
but still can't delete it.
Also the app root toolkit for android gives me this weird error too:
http://i1312.photobucket.com/albums/t539/talos910/Screenshot_2015-09-11-17-08-06_zps4nrxqiev.png
http://i1312.photobucket.com/albums/t539/talos910/Screenshot_2015-09-11-17-08-02_zpsa1ycwdwl.png
Do you have an app like root explorer that specifically asks for root permissions? It doesn't matter if you have root if the explorer can't use it
Sent from my Nexus 5 using Tapatalk
Yes all the file manager apps I used always ask for root permission, that is the problem they have root permission but still can't delete the file, which is weird because I can use apps that definitely need root like scr screen recorder and greenify just fine.
Try installing root explorer and then attempt to delete the file, then it should instantly open a window asking for root. The of course grant the permission. That should always work, but if it doesn't just restart the tablet, if it still doesn't work it must mean you are deleting a file that is in use by the system. Otherwise i have no idea whats wrong
Sent from my Nexus 5 using Tapatalk
Talos91 said:
Yes all the file manager apps I used always ask for root permission, that is the problem they have root permission but still can't delete the file, which is weird because I can use apps that definitely need root like scr screen recorder and greenify just fine.
Click to expand...
Click to collapse
What recovery did you install...twrp, cwm, philz?
Sent from my Nexus 6 using Tapatalk
JMink said:
What recovery did you install...twrp, cwm, philz?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Rooted my device using kingo root, I didn't intall other recovery.
Bad idea to try and remove system files without a custom recovery and a nandroid backup made and stored in a safe spot. What are you trying to remove?
I am trying to delete /system/sbin/su because I read in another thread this was the solution to fixing the issue of the app supersu not updating binaries when rooting your device using Kingo.
Talos91 said:
I am trying to delete /system/sbin/su because I read in another thread this was the solution to fixing the issue of the app supersu not updating binaries when rooting your device using Kingo.
Click to expand...
Click to collapse
That is the binary. If you remove it, you wouldn't be rooted. Can you link the thread you are looking at? There's an app made specifically for replacing that su binary with SuperSU and it's binary called Super-SUme, though I believe it is a paid app.
I know it is the binary but according to this guy:
http://forum.xda-developers.com/apps/supersu/support-update-failures-t2907365/page23
(post 223)
""It appears kango wrote to /system/sbin/su whereas supersu wrote /system/xbin/su and subsequently supersu would keep wanting to update 'su' then fail.
The long and the short of it is once I manually removed /system/sbin/su supersu stopped telling me 'su' was outdated. I don't know android but I do know linux.
$PATH on my tablet has /system/sbin/ prior to /system/xbin/ so it would appear supersu is issuing 'su -V' as opposed to '/system/xbin/su -V' when it checks the version. The kingo 'su' was older than the supersu 'su'.
Dunno what the solution is 'cos the older 'su' is going to get called first & I figure there's nothing but trouble to be gained from changing $PATH globally. Nevertheless it might be enough to check $PATH for unwanted 'su' and flag them, possibly offer to remove them? In my case I renamed it "/system/sbin/su.ORIGINAL" so that it's still runnable in an emergency"""
If you rename it, it won't be able to run, and won't require removal.
That's the thing I can't rename the file either for some reason. Using es and other root explorers doesn’t work.
Talos91 said:
That's the thing I can't rename the file either for some reason. Using es and other root explorers doesn’t work.
Click to expand...
Click to collapse
Seems like the SU binary that Kingroot included is pretty finicky and only works for some things. I've rooted 100s of devices and have never had issues like that. Have seen complaints about other various oddities with Kingroot too. It's nice that it's easy and works on a variety of devices, but if you have only limited control then that kind of defeats part of the purpose of rooting it...
Tried using SuperSUme but the app says I am not rooted with Kingo? wtf? Do you guys know of any other reason why i can't erase the system file sbin/su?
Talos91 said:
Tried using SuperSUme but the app says I am not rooted with Kingo? wtf? Do you guys know of any other reason why i can't erase the system file sbin/su?
Click to expand...
Click to collapse
With Root Explorer, does it let you set the system to R/W? There's a little button at the top of the app that will say R/O or R/W for Read Only or Read Write. If you don't have R/W to the system, then you are unable to make changes to it.
I just renamed file su and then it became able to be deleted.
Talos91 said:
Tried using SuperSUme but the app says I am not rooted with Kingo? wtf? Do you guys know of any other reason why i can't erase the system file sbin/su?
Click to expand...
Click to collapse
Connect your android tablet device to your windows computer. Then enable usb debugging on your android tablet. Then open the windows program called cmd. Then do these commands.
Code:
adb root
Code:
adb remount
Code:
adb shell rm /system/sbin/su
So with Android 7 there seems to be a change in the way the system partition works and I tried a ton of ways to make my /system partition as writable. I tried an app, I tried terminal commands, and I tried a root file explorer. Nothing working; adaway wouldn't work without systemless zip flash. Emoji Switcher was also not working.
Well I found a fast and simple solution!
Install busy box and a terminal app
- Install busy box on system
- Open terminal app
- Run "su" (no quotes)
- Give the terminal app root access
- Then run "busybox mount -o rw,remount system" (no quotes)
- You should get no errors; it will actual do nothing, it will just go to the next line.
Now test that bad boy out and your system partition should be writeable. No more host errors in adaway!
Going to try this out. Been looking for a solution to this as well. Thanks.
Sent from my Nexus 6P using Tapatalk
---------- Post added at 08:50 PM ---------- Previous post was at 08:43 PM ----------
phillymade said:
Going to try this out. Been looking for a solution to this as well. Thanks.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
So if Busy Box is installed to data, do I need to uninstall and install to system for this to work properly. As of now I'm getting a not found error.
Sent from my Nexus 6P using Tapatalk
phillymade said:
Going to try this out. Been looking for a solution to this as well. Thanks.
Sent from my Nexus 6P using Tapatalk
---------- Post added at 08:50 PM ---------- Previous post was at 08:43 PM ----------
So if Busy Box is installed to data, do I need to uninstall and install to system for this to work properly. As of now I'm getting a not found error.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Yeah you need your busybox installed on the system or it wont do anything
I have my busy box installed at /su/xbin
In terminal make sure you put su (then hit enter)
then type the command
If you put them together you get an error for some weird reason
Here is a picture of my busybox install https://www.dropbox.com/s/iwtutkots8bdd13/Screenshot_20160830-184451.png?dl=0
Will this thread make DPI change on rooted 7.0 possible ? :laugh:
ArminasAnarion said:
Yeah you need your busybox installed on the system or it wont do anything
I have my busy box installed at /su/xbin
In terminal make sure you put su (then hit enter)
then type the command
If you put them together you get an error for some weird reason
Here is a picture of my busybox install https://www.dropbox.com/s/iwtutkots8bdd13/Screenshot_20160830-184451.png?dl=0
Click to expand...
Click to collapse
I did su then enter and got the error. perhaps it's where I have busy box installed.
Sent from my Nexus 6P using Tapatalk
ps000000 said:
Will this thread make DPI change on rooted 7.0 possible ? :laugh:
Click to expand...
Click to collapse
Yeah dpi change it possible on Android 7! Currently running 420dpi!
phillymade said:
I did su then enter and got the error. perhaps it's where I have busy box installed.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Make sure you install busybox on /su
This doesn’t work. After running this and then touch /sbin/su /system/bin/su /system/xbin/su
It says Read-only file system. Tried on the pixel c.
backslashV said:
This doesn’t work. After running this and then touch /sbin/su /system/bin/su /system/xbin/su
It says Read-only file system. Tried on the pixel c.
Click to expand...
Click to collapse
Wondering if this might help—running `blockdev --getro /dev/block/dm-0´ (my /system) returned “1” when I checked on Nexus 6P, and returned “0” after --setrw.
I wasn't able to sucessfully remount with the second command, however, due to ‘/system is busy’ or some such thing.
Code:
blockdev --setrw /dev/block/dm-0
mount -o remount,rw /system
You are a saint! While my /system was "writable" after root using Magisk, I couldn't change file permissions. Stumbled upon your method and was able to correct this, although I used my laptop. I had already installed busybox with Magisk, so I opened an adb shell, typed "su," then issued: busybox mount -o rw,remount system
Adaway, and AFWall+ is working fine and I was finally able to chmod 644 bootanimation.zip in /system/media of my Moto X Pure.
Thank you! :good:
Ericarthurc said:
So with Android 7 there seems to be a change in the way the system partition works and I tried a ton of ways to make my /system partition as writable. I tried an app, I tried terminal commands, and I tried a root file explorer. Nothing working; adaway wouldn't work without systemless zip flash. Emoji Switcher was also not working.
Well I found a fast and simple solution!
Install busy box and a terminal app
- Install busy box on system
- Open terminal app
- Run "su" (no quotes)
- Give the terminal app root access
- Then run "busybox mount -o rw,remount system" (no quotes)
- You should get no errors; it will actual do nothing, it will just go to the next line.
Now test that bad boy out and your system partition should be writeable. No more host errors in adaway!
Click to expand...
Click to collapse
* I installed BusyBox to /system/xbin using the app's install.
* I opened my Terminal app and typed su.
* I granted it access.
* I ran the exact command.
It just gave me another prompt as you said it should. But the File Manager that I have used on many rooted devices still won't let me check the box in its settings for Root Explore, even though it prompted me and I granted SuperUser access.
I don't get what I'm missing here.
UPDATE: I am now able to Apply Hosts in AdAway.
However, my File Manager that I have used in Root mode on every device still won't allow me to turn on "Root Explorer" mode. It did prompt me for SuperUser access and I did grant it (and double checked), but when I go to choose that option in the apps' Preferences, it says my device is not Rooted.
Any ideas?
Thank You.
Hi,
Okay, got it! Cancel my distress call.
Thank You!
Hi,
Had to redo my phone and while I can apply Hosts in AdAway (not being able to is a sure sign /System isn't Writable), when I try to make a change to my Build.Prop file found in /System it won't stay changed. I am using Nougat 7.0 with Magisk and every other Root app works fine.
Just for kicks, I tried running the commands you posted to see if it would help, but this time it didn't take the command (I do have BusyBox installed). Instead, it responded with; "Invalid Argument" as follows;
"mounting /dev/block/bootdevice/by-name/system on /system failed: Invalid Argument"
Then the prompt changed to "255|elsa:/ #"
Any ideas? It appears to see that BusyBox is installed, but it isn't working. Also, how do I check where my BusyBox is installed?
Thanks,
Dave