Related
I have a moto droid, rooted mine the normal way with update.zip and adb but my mom has a eris and wants wifi tether and a faster rom with working youtube app
Can i just download the rooting file update her phone then download rom manager to install recovery image? i dont feel like setting up adb on her computer. i want to flash it to the newest ota rooted rom that is on this site.
bL33d said:
I have a moto droid, rooted mine the normal way with update.zip and adb but my mom has a eris and wants wifi tether and a faster rom with working youtube app
Can i just download the rooting file update her phone then download rom manager to install recovery image? i dont feel like setting up adb on her computer. i want to flash it to the newest ota rooted rom that is on this site.
Click to expand...
Click to collapse
Sure, put your sdcard in your computer, or connect it to your computer with the USB cable and mount the sdcard. Download the PB00IMG.zip with root, flash_image, and recovery.img. Shut the phone down, and then do the VOL DOWN+Power ON to flash PB00IMG to the phone. Once done flashing, go in to the android market and download a terminal emulator. Type these commands:
su
after su, phone should change from sh-3.2$ to sh 3.2#
mount -o rw,remount /dev/block/mtdblock3 /system
cp /sdcard/flash_image /system/bin
chmod 755 /system/bin/flash_image
flash_image recovery /sdcard/recovery.img
If you do that, it should allow you to do it without adb on the computer. Just remember to type the 5 commands in the terminal emulator.
I just talked to devs and they told me that It can be done, Just download the rom Manager and install the recovery from there without using adb at all.
You just have to install the root rom first, then you should be able to use the rom manager to install the recovery img, which in my opinion the clockworkmod recovery is a lot better than the RA recovery which is listed in the rom.
thanks guys seemed like it was doable but wanted to double check here first.
I'm in a pretty bad situation.. (I think..) In short: I rooted my HTC EVO 4G LTE, unlocked bootloader, installed viper rom, by mistake deleated a root file, (so now i have the su brainy app, and cant uninstall it.) But i have no root. Then i re-locked my bootloader (while trying to fix my root...)
*UPDATE* users are suggesting i fix it useing recovery: I DONT HAVE RECOVERY
This is what Root checker said:
Root Access is not properly configured or was not granted.
Superuser Application Status:
Superuser application - version 3.1.3 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: -rwxr-xr-x root shell 91980 2008-08-01 08:00 su
Analysis: Setuid attribute NOT present BUT root user ownership is present. Root access is NOT correctly configured for this file!
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwsr-sr-x root root 91980 2008-08-01 08:00 su
Analysis: Setuid attribute present and root user ownership present. Root access is correctly configured for this file! Executing this file can grant root access!
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your EVO device by Root Checker Pro version 1.2.7 from joeykrim in the Android Market
I dont understand this jibberish.. Im still a noob.
Please help me ether:
1) return it to stock
or
2)Re-root it.
Thanks in advance,
Messed up EVO owner.
do you still have TWRP installed as your recovery?
Just reflash the ROM.
Problem solved.
Rxpert said:
Just reflash the ROM.
Problem solved.
Click to expand...
Click to collapse
I wish i can but i no longer have root or recovery
bog3nator said:
do you still have TWRP installed as your recovery?
Click to expand...
Click to collapse
No. But i cant get it because im not rooted. (and cant root b/c i have viper rom and my pc wont recognize it as evo 4g lte)
does you phone turn on? if it does then run regaw mod and unlock bootloader and it will reflash everything for you...
bog3nator said:
does you phone turn on? if it does then run regaw mod and unlock bootloader and it will reflash everything for you...
Click to expand...
Click to collapse
Because i have viper lte rom regaw mod wont recognise me and says "this is not a htc evo 4g lte"
did you do the gameloft tweak? if you did thats why, that tweak edits the build prop. you can always ruu back to stock and re-run the rooter
bog3nator said:
did you do the gameloft tweak? if you did thats why, that tweak edits the build prop. you can always ruu back to stock and re-run the rooter
Click to expand...
Click to collapse
I did. Thank for your tip (and i will hit the like botton.) but if the build prop. is changed, will ruu recognize me?
i would think it would. but i havent tried to ruu before so i am not sure what the exact process is
edit: i will hit the thanks button for you so i can pop you thanks cherry
Stop. You don't need to ruu. First install twrp recovery. Then wipe and reflash your favorite Rom. Are you s-off?
he said he is not currently rooted and the bootloader is locked again. so goo manager wont be able to get root permissions and he cant fast boot if the bootloader is locked.
---------- Post added at 09:48 PM ---------- Previous post was at 09:29 PM ----------
Did you try installing supersu from the market and see if that works. I don't know if it would but couldnt hurt also.
Sent from my EVO using xda app-developers app
That doesn't mean he is s-on if he was s-off at some point. Boot into bootloader. Does the phone say s-on or s-off?
{ParanoiA} said:
That doesn't mean he is s-on if he was s-off at some point. Boot into bootloader. Does the phone say s-on or s-off?
Click to expand...
Click to collapse
Its S-ON
I have ruu ready to run.. Should i go ahead with it now, or is there something else to do?
Running ruu can't hurt.. u will just have to start over that's all ..and with one click root that's easy
firmbiz94 said:
Running ruu can't hurt.. u will just have to start over that's all ..and with one click root that's easy
Click to expand...
Click to collapse
ok thats good to know, thanks!
thats why i recommended it, if you dont mind starting over...how did it all go?
bog3nator said:
thats why i recommended it, if you dont mind starting over...how did it all go?
Click to expand...
Click to collapse
:laugh: Its like a new phone! Thank you!!!! Now im just gonna re-root it and im good to go!
Hi guys, need some help here.
I followed all the steps to unlock the bootloader and root the rezound last night but the root didnt work. The bootloadrer is unlocked, i have been able to confirm that at the very least by going back into the fastboot screen.
I was using the guide at the unlocker as it really went over step by step in great detail.
No idea what i did and am really hoping someone can provide me some guidance here.
See below for the errors i am getting from root checker app.
Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - is NOT installed.
System File Properties for Root Access:
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: lrwxrwxrwx root root 2012-09-18 06:41 su -> /system/bin/su
Analysis: File: su is a symbolic link pointing to another file: /system/bin/su
Standard Location
Check Command: ls -l /system/bin/su:
Result: -rwsr-sr-x root root 22228 2012-09-18 06:41 su
Analysis: Setuid attribute present and root user ownership present. Root access is correctly configured for this file! Executing this file can grant root access!
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your ADR6425LVW device by Root Checker Pro version 1.3.0 from joeykrim in the Android Market -
Thanks so much, i have always done a ton of reading on this site and love it...figured it was about time to reach out for some help.
Thanks again and please let me know if i can provide any other info that would help you all figure out where i went wrong.
Amon Ra 3.15?
swilbert80 said:
Amon Ra 3.15?
Click to expand...
Click to collapse
Not 100% sure......i will have to double check tonight but i used the Amon Ra linked to the unlocker site in the walkthrough.
I did do some reading on this a bit last night after unsucessfully attempting to root the rezound and read a few things about Amon Ra not working with ICS....but the walkthrough on unlocker was updated just a few weeks ago so i would have assumed they would use the newest one.
Thanks Swilbert80.......apprecaite the response here.
Thoughts?
jesternsb said:
Not 100% sure......i will have to double check tonight but i used the Amon Ra linked to the unlocker site in the walkthrough.
I did do some reading on this a bit last night after unsucessfully attempting to root the rezound and read a few things about Amon Ra not working with ICS....but the walkthrough on unlocker was updated just a few weeks ago so i would have assumed they would use the newest one.
Thanks Swilbert80.......apprecaite the response here.
Thoughts?
Click to expand...
Click to collapse
When you pull battery and then power + volume down start into hboot (make sure no PH98IMG.zip on root of ext sd card), you should be able to get into recovery. You will see very quickly if Amon Ra is there. It is a dark screen with blue text. If you don't have it, you can get it at:
http://forum.xda-developers.com/showpost.php?p=23781936&postcount=428
I assume you are using adb fast boot for this. If I am telling you stuff you already know, let me know.
jesternsb said:
Not 100% sure......i will have to double check tonight but i used the Amon Ra linked to the unlocker site in the walkthrough.
I did do some reading on this a bit last night after unsucessfully attempting to root the rezound and read a few things about Amon Ra not working with ICS....but the walkthrough on unlocker was updated just a few weeks ago so i would have assumed they would use the newest one.
Thanks Swilbert80.......apprecaite the response here.
Thoughts?
Click to expand...
Click to collapse
If you are not sure on Amon Ra, I think you missed a step. The unlocker only puts the SuperSU program on your phone. You then need to go into recovery (Amon Ra) and flash the file. When I did this to my friends phone a few days ago, the file was on the internal SD card.
If you are still having issues, please refer to this thread - http://forum.xda-developers.com/showthread.php?t=1872651
Download the latest version of SuperSU zip file and install it with Amon RA recovery.
http://download.chainfire.eu/204/SuperSU/
swilbert80 said:
When you pull battery and then power + volume down start into hboot (make sure no PH98IMG.zip on root of ext sd card), you should be able to get into recovery. You will see very quickly if Amon Ra is there. It is a dark screen with blue text. If you don't have it, you can get it at:
http://forum.xda-developers.com/showpost.php?p=23781936&postcount=428
I assume you are using adb fast boot for this. If I am telling you stuff you already know, let me know.
Click to expand...
Click to collapse
Thanks for the info.....I went back into the hboot menu and did see a zip file titled PH98IMG.zip when it flashed the check on that hboot screen....i also was able to go into recovery and see a black backround with options to install the su.......and yes i am using adb for this.
Hey thanks for the reply here HowardZ......i am assuming i place that file in the same location as i do the recovery image? Trying to figure this out tonight....never a dull moment. lol
Thanks again
Correction.....no ph98im.zip was located....was just searching for it.
UPDATE i tried to go back through ADB and re work the steps and now the superuser is not on the phone anymore....argh.
UPDATE...i dl'ed the superuser through google play.....but still no root access.
I think if i can get some guidance on flashing Amon Ra and getting the supersu on the phone i might be ok, not 100% on that though.
Updated root checker report below.
Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - is NOT installed.
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: -rwsr-sr-x root root 22228 2012-09-18 19:22 su
Analysis: Setuid attribute present and root user ownership present. Root access is correctly configured for this file! Executing this file can grant root access!
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: lrwxrwxrwx root root 2012-09-18 19:22 su -> /system/bin/su
Analysis: File: su is a symbolic link pointing to another file: /system/bin/su
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your ADR6425LVW device by Root Checker Pro version 1.3.0 from joeykrim in the Android Market
Flash amon ra in boot loader and then download the super user.zip, the link is a few posts above mine
Sent from my cm_tenderloin
You can try updating the binary for SU from:
http://androidsu.com/superuser/
First, reinstall SU in recovery, and then flash the new binary followed by reboot. Should fix so SU remains (in app drawer) and root success.
MD5 checksum provided below DL link to check.
chaos254 said:
Flash amon ra in boot loader and then download the super user.zip, the link is a few posts above mine
Sent from my cm_tenderloin
Click to expand...
Click to collapse
Hey Chaos thanks for the reply here.....and please excuse my Noob-ness, god i hate the sound of that. I just want to make sure i fully understand and follow your instructions here.
Once i flash the amon ra recovery in the bootloader where do i save the super user zip file to and how do i flash that? That is where i seem to be getting hung up on.....not exactly sure where to save that file to and where to access/flash it from.......
I just want to make sure i follow you so that i dont scew it up.
thanks again
jesternsb said:
Hey Chaos thanks for the reply here.....and please excuse my Noob-ness, god i hate the sound of that. I just want to make sure i fully understand and follow your instructions here.
Once i flash the amon ra recovery in the bootloader where do i save the super user zip file to and how do i flash that? That is where i seem to be getting hung up on.....not exactly sure where to save that file to and where to access/flash it from.......
I just want to make sure i follow you so that i dont scew it up.
thanks again
Click to expand...
Click to collapse
Superuser.zip should be on your SD card. Once in amon ra>flash zip menu>sdcard>superuser.zip
Sent from my ADR6425LVW using Tapatalk 2
Awesome....victory is mine....thanks again......XDA is the shiznit!!!!!
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
Does anyone know how I can implement a custom ROM but have it urooted
I need an unrooted for work. I have tried rootcloak type applications but they don't do the trick. Plus, this is for work so, in order to comply with requirements I want to make sure phone is not rooted rather than just hiding root
Reason I want to use custom ROM is to get additional features such as dropdown menu on main page, remove unwanted app (malware) and have smallest footprint possible
wrong thread. post in q&a
Flash custom ROM.
Download Root explorer or any other root explorer app
Navigate to system.
delete
Code:
/system/app/Superuser.apk
Code:
/system/xbin/su
or
Code:
/system/bin/su
reboot the phone
That should do it.
karandpr said:
Flash custom ROM.
Download Root explorer or any other root explorer app
Navigate to system.
delete
Code:
/system/app/Superuser.apk
Code:
/system/xbin/su
or
Code:
/system/bin/su
reboot the phone
That should do it.
Click to expand...
Click to collapse
Thank you - will try and see how it goes
jean001luc said:
Thank you - will try and see how it goes
Click to expand...
Click to collapse
No good. Deleted system/bin/su and xbin/su but could not find system/apps/superuser
Rebooted device and still rooted
what ROM are you using ?
it could be
/system/app/superuser.apk
/system/app/Superuser.apk
/system/app/SuperSU.apk
/system/app/eu.chainfire.supersu.apk
/system/app/com.koushikdutta.superuser.apk
/system/app/com.noshufou.android.su.apk
in anycase ,you will need to reflash ROM or reflash superuser.
Technically the "Superuser" app is a front end for /system/bin/su...So you are unrooted, Just you need to remove that app..