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
Related
Hey,
I'm having difficulty mounting the /system/ directory as read/write on my Legend.
I've tried both "adb remount" and "mount -o remount,rw /dev/block/mtdblock3 /system".
The mount appears to succeed but when I try to do anything I get errors (eg; "touch: /system/test: Out of memory" and "mkdir failed for /system/test, Out of memory")
ro.secure=0 is set in my /default.prop
Code:
# cat /default.prop
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
HBOOT: 1.01 S-ON
Does it need to be S-OFF to do so? If so, is it possible to S-OFF my Legend?
Thanks.
You are s-on, so you can't write on /system
You need to have s-off, but you are on hboot 1.0+ where s-off isn't possible yet
Thanks ThauExodus ,
So am I right in thinking that when I flash a rom (let's say "update-cm-7.0.0-RC4-Legend-signed.zip"), I am re-flashing the /system partition?
If that's the case, can I somehow modify the rom before flashing to add custom things? If I extract it and insert a directory called "/system/test", when I flash it will /system/test exist?
A practical example being, if I populate the hosts file (/system/etc/hosts) with AdFree entries then somehow repackage and flash the rom will it work?
Just use Blay0's overlay filesystem (flash the zip with CWM) and you will be able to do what you want
I am S-on and found no reason for s-off..for modifying anything in /system..i use adb in recovery mode..this serves the purpose..
that sounds appealing
abhishek92 said:
I am S-on and found no reason for s-off..for modifying anything in /system..i use adb in recovery mode..this serves the purpose..
Click to expand...
Click to collapse
does that stick? (e.g. remove system apps like stocks)
what are you doing that on? (legend-hboot-os ect)
yes it does stick..when u enter recovery mode..u r allowed to write to /system..ul have to boot into ur custom recovery mode(clockwork/amon)..and then use adb shell from the command line on ur comp...jus search on how to use adb shell in recovery mode..
thank you sir
abhishek92 said:
yes it does stick..when u enter recovery mode..u r allowed to write to /system..ul have to boot into ur custom recovery mode(clockwork/amon)..and then use adb shell from the command line on ur comp...jus search on how to use adb shell in recovery mode..
Click to expand...
Click to collapse
Thank you for the information, from what i have been reading i was convinced that could be a viable way to go about things. I have been reading about adb shell and recovery, unfortunately i find sites like adb for beginners a little rough for an actual beginner-well, not as informative as typing help into the cmd prompt.
As of right now i am trying to compile a list of commands specific to the legend structure.
That is why i would ask what build, hboot or any phone specific info about your phone so i can get a better grasp on how things change from one system\setup to the next.
Following instructions is one thing, i want to understand what i am doing.
Before I flash a new ROM I just open the downloaded ROM zip on the PC and delete apps I don't want from the system directory. Delete stocks, quick office etc. Simplest method for Windows users who don't want to use adb.
Sent from my HTC Legend using XDA App
billyJAM said:
Before I flash a new ROM I just open the downloaded ROM zip on the PC and delete apps I don't want from the system directory. Delete stocks, quick office etc. Simplest method for Windows users who don't want to use adb.
Sent from my HTC Legend using XDA App
Click to expand...
Click to collapse
wouldnt it be nice if we could do that with our ota updates and just skip the whole rooting process
billyJAM said:
Before I flash a new ROM I just open the downloaded ROM zip on the PC and delete apps I don't want from the system directory. Delete stocks, quick office etc. Simplest method for Windows users who don't want to use adb.
Sent from my HTC Legend using XDA App
Click to expand...
Click to collapse
It doesn't work that way .
It's just not so symple
http://forum.xda-developers.com/showthread.php?t=760376
But u may give it a try
Just start your phone with clockwork recovery, select mount system and restart adb in advanced menu from recovery. Then start adb on PC and push your file to system,
Adb push ...apk /system/app/...apk
Apk should be in same folder like advanced itself
Sent from my Legend using XDA App
Hi everyone,
I tried using a script which automated the install for the the custom recovery, but I started to get messages that it ran out of disk space (I can't link to the file due to my noob status). I probably should have come here first before using that script, but such as life..
I have no important data on the phone, if I lose it all that's ok.
It rebooted and my p500 waits with the following
"Fastboot mode started"
"udc_start()"
It also gives some info when USB is connected ie.
"- suspend -"
"- reset -"
Do I have a paperweight?
thanks and sorry for the newb post ..
edit: so I found this : http://forum.xda-developers.com/showthread.php?t=1003790 and
http://forum.xda-developers.com/showthread.php?t=875881
and have gotten it to the yellow emergency mode, not sure how to flash it from here though.
edit2: dling the stock firmware from http://forum.xda-developers.com/showthread.php?t=1073827
edit3: there's this as well.. http://forum.xda-developers.com/showthread.php?t=1088046 If I try this method, will it screw up again from too little free disk space?
I'm to drunk to guide our give you the link to fix it but I will tell you, you can fix it just hold on we will help you ; ) and we don't by the time I wake up I will help you its ok ))
Sent from my LG-P500 using XDA Premium App
dislplin01 said:
I'm to drunk to guide our give you the link to fix it but I will tell you, you can fix it just hold on we will help you ; ) and we don't by the time I wake up I will help you its ok ))
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
thank you very much, I appreciate it haha
Your phone has booted in fastboot mode. Go to development section and read a tutorial how to recover from fastboot.
Sent from my LG-P500 using XDA Premium App
setTopbox said:
thank you very much, I appreciate it haha
Click to expand...
Click to collapse
Then did u unbricked now
Mahesh
go here....
http://forum.xda-developers.com/showthread.php?t=1088046
or here
http://forum.xda-developers.com/showthread.php?p=13813493
How to install Android SDK /ADB
http://lgoptimusonep500.blogspot.com/2011/01/how-to-install-android-sdk-adb.html
dislplin01 said:
I'm to drunk to guide our give you the link to fix it but I will tell you, you can fix it just hold on we will help you ; ) and we don't by the time I wake up I will help you its ok ))
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
Most honest post I've seen on the entire forum.
Sent from my Kyocera Echo.
mvgadagi said:
Then did u unbricked now
Mahesh
Click to expand...
Click to collapse
I got the phone working again - thanks! I guess it's not a great idea to install the custom recovery
with low disk space?
setTopbox said:
I got the phone working again - thanks! I guess it's not a great idea to install the custom recovery
with low disk space?
Click to expand...
Click to collapse
Hmmm. Well, should not matter? /recovery uses a separate partition. Perhaps you flashed a corrupt (incomplete) image?
well if u ever wish to install recovery just download rom manger from market (latest) and install recovery from rom manger option make sure u hav eusb debugging enabled. it works easy
shhbz said:
well if u ever wish to install recovery just download rom manger from market (latest) and install recovery from rom manger option make sure u hav eusb debugging enabled. it works easy
Click to expand...
Click to collapse
Erm... reading all the posts about fastboot after using ROM Manager for this, I guess I would rather stick with the custom script using flash_image.
doktornotor said:
Hmmm. Well, should not matter? /recovery uses a separate partition. Perhaps you flashed a corrupt (incomplete) image?
Click to expand...
Click to collapse
hmm, I'm not sure (when I dl'd the file I did compare the hash as per instructions). I used the following instructions:
manast.com/2011/05/07/how-to-install-custom-recovery-on-lg-optimus-one-p500
I then went into a terminal emulator, and ran "sh /sdcard/rf.sh". At that point the output of the script started to say "disk full" (and then it reboot into the fastboot prompt).
setTopbox said:
I then went into a terminal emulator, and ran "sh /sdcard/rf.sh". At that point the output of the script started to say "disk full" (and then it reboot into the fastboot prompt).
Click to expand...
Click to collapse
No idea about that script. Using flash_image and never had any issue with "disk full", frankly the message does not make sense. All you need is to copy the recovery image to SD and run as root:
Code:
# flash_image recovery /sdcard/recovery.img
Done.
doktornotor said:
No idea about that script. Using flash_image and never had any issue with "disk full", frankly the message does not make sense. All you need is to copy the recovery image to SD and run as root:
Code:
# flash_image recovery /sdcard/recovery.img
Done.
Click to expand...
Click to collapse
I'm getting permission denied when trying to use flash_image. Gingerbreak says the device is rooted, and the terminal does ask for superuser permission when i open it (su works in the terminal). I also tried chmod 755 flash_image but that didn't work either.
the permissions for flash_image are r-xr-x any thoughts ?
edit: apparently the sdcard is mounted with -noexecute ? So I tried copying flash_image to / but it's read only. Is there somewhere where I can execute this?
This rf.sh script seems most notorious, I too went into fastboot after that. Doktornotor's method worked (in fact I think he/she was the one who bailed me out back then as well).
If you got into fastboot, most probably you have a rooted phone.
To use flash_image you need to get the flash_image.sh on the root of your sd card. Search the forum for Amon-Ra custom recovery, and you shall find this file in that thread (it is required for Amon ra setup). Log in to your adb console, and use fastboot to push the new image in the recovery partition.
Unless your recovery.img or flash_image.sh is corrupted, it will work for sure.
Keep in mind, fastboot is a very powerfull tool, if you can access it, you're safe.
Cheers,
Alex
did you get out??
just flash stock firmware with kdz worked for me bro
Buddy,
You do not need to flash anything with KDZ. The ROM is fine nothing happened to it. All your issue is with the recovery being flashed wrongly for some reason.
I had the same issue just yesterday and I managed to flash the recovery through fastboot.
What you need to do is:
1. Install android SDK from Google.
2. Connect the phone while it is on fastboot.
3. If your windows does not find the fastboot drivers online, use the drivers in this link:
http://www.megaupload.com/?d=39ZR16W1
4. extract the .zip file that you copied to your SD. The one that contains the recovery.
5. Copy the recover.img (or whatever the name of the .img file in the .zip file) to the folder inside the android sdk where fastboot.exe is located (I think its the tools folder)
6. Copy the adbwinapi.dll file from the android SDK\platform-tools\ to the folder containing fastboot.
7. issue the command (and replace recovery.img with the .img file name you have):
fastboot flash recovery recovery.img
fastboot reboot
Dr.Alani said:
Buddy,
You do not need to flash anything with KDZ. The ROM is fine nothing happened to it. All your issue is with the recovery being flashed wrongly for some reason.
I had the same issue just yesterday and I managed to flash the recovery through fastboot.
What you need to do is:
1. Install android SDK from Google.
2. Connect the phone while it is on fastboot.
3. If your windows does not find the fastboot drivers online, use the drivers in this link:
http://www.megaupload.com/?d=39ZR16W1
4. extract the .zip file that you copied to your SD. The one that contains the recovery.
5. Copy the recover.img (or whatever the name of the .img file in the .zip file) to the folder inside the android sdk where fastboot.exe is located (I think its the tools folder)
6. Copy the adbwinapi.dll file from the android SDK\platform-tools\ to the folder containing fastboot.
7. issue the command (and replace recovery.img with the .img file name you have):
fastboot flash recovery recovery.img
fastboot reboot
Click to expand...
Click to collapse
I appreciate the information. When I'm in adb, su won't allow me to gain root access on the phone. The phone itself is rooted using gingerbreak though.
setTopbox said:
I appreciate the information. When I'm in adb, su won't allow me to gain root access on the phone. The phone itself is rooted using gingerbreak though.
Click to expand...
Click to collapse
I do not see how you need to use adb.
Sent from my LG-P500 using XDA App
i triad to download it from x various stock Theard,
but both odex & Deodex give me error,
can u guys get me one that works properly?
slidert said:
i triad to download it from x various stock Theard,
but both odex & Deodex give me error,
can u guys get me one that works properly?
Click to expand...
Click to collapse
Try the RUU and simply re-root.
from where can i download it?
Sent from my HTC_Amaze_4G using XDA App
slidert said:
from where can i download it?
Sent from my HTC_Amaze_4G using XDA App
Click to expand...
Click to collapse
Rom||RUU|| Shipped Ruby ROM Collection
Binary100100 said:
Rom||RUU|| Shipped Ruby ROM Collection
Click to expand...
Click to collapse
i put the file in my root folder on the Memory Card,
then i reboot into the Bootloader/HBOOT screen. but i dont get the "Do you want to start the update" question.
what should i do now?
slidert said:
i put the file in my root folder on the Memory Card,
then i reboot into the Bootloader/HBOOT screen. but i dont get the "Do you want to start the update" question.
what should i do now?
Click to expand...
Click to collapse
you got to relock
xboarder56 said:
you got to relock
Click to expand...
Click to collapse
i relock my phone and boot into the bootloder but nothing happen...
after i reboot again i go to the root folder with root explorer, but the file is vanished.
also i can't boot into the bootloder when i torn the phone off, the only way is by pooling the battery.
slidert said:
i relock my phone and boot into the bootloder but nothing happen...
after i reboot again i go to the root folder with root explorer, but the file is vanished.
also i can't boot into the bootloder when i torn the phone off, the only way is by pooling the battery.
Click to expand...
Click to collapse
Clearify this for me.
Can you get into hboot at all? If you have adb and fastboot already installed and configured on your computer you should be able to do: adb shell reboot bootloader.
What does it say at top? Unlocked or Relocked? If relocked then proceed.
Do you have a PH85IMG.zip file on the root of the external sdcard?
Binary100100 said:
Clearify this for me.
Can you get into hboot at all? If you have adb and fastboot already installed and configured on your computer you should be able to do: adb shell reboot bootloader.
What does it say at top? Unlocked or Relocked? If relocked then proceed.
Do you have a PH85IMG.zip file on the root of the external sdcard?
Click to expand...
Click to collapse
1: yes i can get into hboot
2: both adb and fastboot installed in my computer ( i shore hope so, otherwise how did i mange to unlock my phone and install x roms and rtl patch...)
but when i tried to do adb shell i got this line: c:\android>adb shell reboot bootloader
adb server is out of date. killing...
* daemon started successfully *
error: device not found
3: in the hboot its saying ***relocked*** ***security warning***
4: i did put the PH85IMG.zip file on the root of the external sdcard with the root explorer, but when i got into the hboot nothing happen.
4: if i return to the root folder after i reboot my phone, i dont see that file any more...
slidert said:
1: yes i can get into hboot
2: both adb and fastboot installed in my computer ( i shore hope so, otherwise how did i mange to unlock my phone and install x roms and rtl patch...)
but when i tried to do adb shell i got this line: c:\android>adb shell reboot bootloader
adb server is out of date. killing...
* daemon started successfully *
error: device not found
3: in the hboot its saying ***relocked*** ***security warning***
4: i did put the PH85IMG.zip file on the root of the external sdcard with the root explorer, but when i got into the hboot nothing happen.
4: if i return to the root folder after i reboot my phone, i dont see that file any more...
Click to expand...
Click to collapse
I don't understand what is deleting the file from your sdcard. That doesn't make any sense at all.
Binary100100 said:
I don't understand what is deleting the file from your sdcard. That doesn't make any sense at all.
Click to expand...
Click to collapse
is there a way to push this file from the computer when I'm in the hboot?
if not, do you have the latest Various Stock 1.36.351.6 that i can install from the ClockWorkMod Recovery?
b.t.w what is the difference between Deodex and Odex version?
slidert said:
is there a way to push this file from the computer when I'm in the hboot?
if not, do you have the latest Various Stock 1.36.351.6 that i can install from the ClockWorkMod Recovery?
b.t.w what is the difference between Deodex and Odex version?
Click to expand...
Click to collapse
You cannot push a file to the sdcard via fastboot. It must be there already when the hboot is activated so that it can be detected and prompt you to update.
There is a version however I could never get it to install. It always gives me an error.
Difference between deodex and odex is simply the way that the files are compiled. For example the odex version you will see files such as Browser.apk, Browser.odex, Calculator.apk, Calculator.odex, Calendar.apk, Calendar.odex, etc. The de-odexed is simply the *.odex files already compiled with the .apk files. So there will not be a Browser.odex, Calculator.odex, etc. Is there a difference performance wise? None that I've noticed personally. However it does make it easier to theme when there isn't a .odex file involved and it's also a lot easier to manage.
Back on topic... do you have another sdcard to try? Perhaps the one that you are using is corrupted somehow? Remember to properly unmount the device before you unplug it.
i do have another sd card (in my hd2) with ext 2 pert'. i will give it a try later on.
but the strange thing is that on this phone i didnt put any sd card, i only use the internal card.
another thing, i cant boot into the hboot if i turn of my phone, only after i pull the battery out.
Sent from my HTC Amaze 4G using XDA App
slidert said:
...this phone i didnt put any sd card, i only use the internal card.
Click to expand...
Click to collapse
WAIT...
It MUST be on the MicroSD (external) card. Internal will not work.
now its trying to load the file but its writing no image and do nothing
slidert said:
jesussss!!!!!! one small thing can drive u crazyyyyy!!!!
thnx man, i really appreciate all your help
Sent from my HTC Amaze 4G using XDA App
Click to expand...
Click to collapse
I'm going to crawl into a fetal position and cry now.
Binary100100 said:
I'm going to crawl into a fetal position and cry now.
Click to expand...
Click to collapse
it seems that my phone hate me! LoL
now its trying to load the file but its writing no image and do nothing
I am rooted but i have been reading on installing a recovery. I don't have a sd card at the moment so not sure if i can use ADB to install a recovery. Why cant i just install recovery through Rom Manager?
eastwood1 said:
I am rooted but i have been reading on installing a recovery. I don't have a sd card at the moment so not sure if i can use ADB to install a recovery. Why cant i just install recovery through Rom Manager?
Click to expand...
Click to collapse
Someone with more knowledge will need to chime in, but I I'd bet the build we are using isn't official, and probably can't be installed through Rom Manager. Give it some time, eventually things will work as normal
And you can use the internal storage to copy over the recovery. I used terminal emulator and the internal memory when I did mine.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
And you can use the internal storage to copy over the recovery. I used terminal emulator and the internal memory when I did mine.
Click to expand...
Click to collapse
Can you explain to me how you went about installing the recovery with only internal storage? I would like to give that a try but not sure the best way to go about it. What commands to use and such, thanks.
eastwood1 said:
Can you explain to me how you went about installing the recovery with only internal storage? I would like to give that a try but not sure the best way to go about it. What commands to use and such, thanks.
Click to expand...
Click to collapse
To all,
I couldn't be bothered with learning ADB, but wanted a custom recovery on my SIII ... maybe you can relate?
Here's the easiest way to do it -- and you don't even need a computer!!! You do, however, already need to be rooted before you can use this method ...
Download your recovery of choice (.. as of this writing, I think there are two: CWM and TWRP ..) and make sure you place a copy in the root drive of your sdcard. Rename it recovery.img, if you want to follow the terminal directions listed below ...
Then, download a terminal emulator onto your device (I use Better Terminal Emulator Pro, which is a paid app) and fire it up.
Once in the terminal emulator, type the following commands one line at a time, waiting after each line for the appropriate prompt:
$ su
# dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
# reboot recovery
Your device should then boot into the custom recovery, which serves as immediate confirmation that you did things correctly.
I just used this method to install birdman's twrp8.img to my SIII and it worked like a charm.
http://forum.xda-developers.com/showthread.php?t=1764398
I dont think that will work. Notice the command says sdcard.
The internal memory on the sgsiii is labeled sdcard for whatever reason. The external sdcard slot is under mnt/extsdcard in root explorer if that helps.
Sent from my SGH-T999 using xda premium
Ok i open Better terminal emulator Pro and it has
/ $ .. when i add in the SU it says
bash: -c: command not found
what am i doing wrong?
I have downloaded and renamed the TWRP.IMG to recovery.img
eastwood1 said:
Ok i open Better terminal emulator Pro and it has
/ $ .. when i add in the SU it says
bash: -c: command not found
what am i doing wrong?
I have downloaded and renamed the TWRP.IMG to recovery.img
Click to expand...
Click to collapse
You need to be rooted and have a "su" command. Typical "rooted" roms include supersu , or equivalent, and busybox (which provides the basic Linux commands). I would install super super and busybox from Google play and try again.
You need the SU command to switch to root user in the shell to have the rights to use dd to overwrite the recovery partition.
I can confirm that the dd command works as that is how I loaded cwm on my s3.
Sent from my SGH-I747M using xda app-developers app
eastwood1 said:
Ok i open Better terminal emulator Pro and it has
/ $ .. when i add in the SU it says
bash: -c: command not found
what am i doing wrong?
I have downloaded and renamed the TWRP.IMG to recovery.img
Click to expand...
Click to collapse
See if this helps.
http://forum.xda-developers.com/showthread.php?t=1739426
For what its worth the reason ROM manager doesn't work is because there is not an official CWM Recovery out for the Verizon S3. We are using the Sprint Recovery
Pompsy said:
For what its worth the reason ROM manager doesn't work is because there is not an official CWM Recovery out for the Verizon S3. We are using the Sprint Recovery
Click to expand...
Click to collapse
There's no official CWM Recovery for any US versions of the GS3, Sprint included. The only official GS3 recovery available is for the international version. The one we're all using right now (I believe) was built by Team Epic. They're historically Sprint devs and so they built it for the Sprint version; however, as you know it works on more than just the Sprint version. Eventually, I'm sure there will be official recoveries direct from Koush.
Personally, I prefer TWRP (bettery touch control layout and options such as compression to save space), but that too is a work in progress.
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