Related
I rooted my phone on June 16, a couple weeks ago. I had to factory reset my phone. Everything on the phone and memory card was erased other than Superuser Permissions. Superuser Permissions still shows up on my home screen.
Because SU is still there, am I still rooted? If so what do I need to put back on my memory card for everything to work properly?
I can't get into ADB Shell anymore either, I've tried all day and nothing has helped. I guess I got really lucky.
If I'm still rooted, is there an easier way to get into ADB Shell? Also if I am still rooted, how exactly to I do a NAND? And by doing this, will it make it easier to get into ADB Shell?
I know these are probably basic questions for some, but I would really like a little help to get a step in the right direction. I really appreciate anyone's help and knowledge on this.
travazz said:
I rooted my phone on June 16, a couple weeks ago. I had to factory reset my phone. Everything on the phone and memory card was erased other than Superuser Permissions. Superuser Permissions still shows up on my home screen.
Because SU is still there, am I still rooted? If so what do I need to put back on my memory card for everything to work properly?
I can't get into ADB Shell anymore either, I've tried all day and nothing has helped. I guess I got really lucky.
If I'm still rooted, is there an easier way to get into ADB Shell? Also if I am still rooted, how exactly to I do a NAND? And by doing this, will it make it easier to get into ADB Shell?
I know these are probably basic questions for some, but I would really like a little help to get a step in the right direction. I really appreciate anyone's help and knowledge on this.
Click to expand...
Click to collapse
easiest way to know if you are still rooted is to download android terminal emulator from the market and type in su on the screen... if you get a # sign then you have root... if you get permission denied then you don't.
find that out first then we can answer the other questions.
Downloaded it, typed in su, Superuser Permissions came up on my phone, I allowed it. After I typed su, # showed up underneath it
travazz said:
Downloaded it, typed in su, Superuser Permissions came up on my phone, I allowed it. After I typed su, # showed up underneath it
Click to expand...
Click to collapse
You're in good shape. If you're looking to get into adb shell, you might as well go the whole nine yards and dl the recovery installer from unrevoked, it will install custom recovery and once you get that you can boot into the custom one and adb shell from there without having to do the SD card stuff over and over again.
viccyran said:
You're in good shape. If you're looking to get into adb shell, you might as well go the whole nine yards and dl the recovery installer from unrevoked, it will install custom recovery and once you get that you can boot into the custom one and adb shell from there without having to do the SD card stuff over and over again.
Click to expand...
Click to collapse
Where do I get the custom recovery file and how do I install it/use it?
Sorry that these are really dumb questions, but now that I know I still have root, this is getting exciting again.
See the stickied thread recovery reflash tool.
-------------------------------------
Sent via the XDA Tapatalk App
Now I'm trying to follow the recovery steps and I'm having the following errors. Can anyone please help?
When I try to install the modified USB drivers I receive the following errors:
Error 0x80004005: Unspecified error on these specific dll files.
WdfCoInstaller01007.dll
WUDFUpdate_01007.dll
WUDFUpdate_01007.dll
When I go to install the reflash-bundle, everything installs, but it fails installing the reflash.exe saying that the file is corrupt.
I'm using Windows 7 Ultimate x64, if that helps out
This is a development sub-forum. Please post your questions in the General section. Thanks.
I have no idea where to put the new ra-evo recovery file so that fastboot sees it. I have looked sorry for the stupid question
your fast boot should be installed in ur android sdk tools folders so if thats where ur fast boot is then put the file in the tools folder
Fastboot flashes files from your computer not on the sdcard or anything.
Ex. Fastboot flash recovery /User/downloads/recovery.img
Sent from my PC36100 using XDA App
i am so confused
so if I am rooted and unlocked and I already have the original amon recovery i just put the new amon recovery in the tools folder. then how do I get it on my phone
if you already rooted you should have android sdk installed
easyest way
go to start
my computer
c drive or your main drive
android sdk or sdk (wat ever you named it)
tools folder
put recovery in tools forder
open a command prompt and
cd \android-sdk
cd tools
now your in the tools folder
fastboot flash recovery /recovery.img
it is easyer and faster no searching for the files if you put the recovery in the tools folder its already there no going to filesfoldersdownloads you dont need them commands its faster and easy look through the adb and sdk guides it has all commands and most recover forums tell you all this
so i need to change the name of the amon recovery image to recovery.img
No he was just using recovery.img as a example.
Sent from my PC36100 using XDA App
Here's how i did it this morning, downloaded file to pc, connect phone as disk drive, opened disk drive, placed the amon file into the sdcard, changed phone back to charge only, went to astro to verify that the amon file was on the home list of files, then wen to market and downloaded terminal emulator free, and just follow Amon's instructions to apply using terminal or adb, it was reall easy that way, i kept trying to load the fastboot way and just couldn't figure it out, so i tried this was and perfect, new recovery, and hopefully i can wipe dalvik now.
You don't need fastboot to flash a new recovery image. Like tomh said in the post above this one, put the new recovery on the root of your sdcard, open a terminal emulator on your phone and type the following:
flash_image recovery /sdcard/name_of_recovery.img
I haven't used my computer to update a recovery image since I first got my Hero.
with a terminal app you'll want to use this exact cmd's
su(press enter)
flash_image recovery /sdcard/recovery-RA-evo-v1.8.0.img(press enter)
reboot recovery(press enter)
that's just as amon_ra has it, same as what i used as well.
thanks for the help
shawnten said:
thanks for the help
Click to expand...
Click to collapse
Somewhere on your PC. You just have to give the path to the fastboot command.
Sent from my HummerPhone using the XDA App
i just downloaded the terminal emulator onto my evo but when i type the first cmd "su" it says permission denied. please tell me how do i get passed that.
ro2themax said:
i just downloaded the terminal emulator onto my evo but when i type the first cmd "su" it says permission denied. please tell me how do i get passed that.
Click to expand...
Click to collapse
Root your phone..
i jsut use rom manager. I am to lazy to do everything else currently rom manager has the latest amon ra you can tell it to flash as an "alternative" recovery. takes 2 seconds and no typing out "long" commands in terminal.
i was under the impression i was rooted...i did the OTA update to 2.2 then used the method to root that came out a week ago using unrevoked3 and unrevoked forever. but instead of going back to a rooted 2.2 i stayed on a rooted 2.1.
ro2themax said:
i was under the impression i was rooted...i did the OTA update to 2.2 then used the method to root that came out a week ago using unrevoked3 and unrevoked forever. but instead of going back to a rooted 2.2 i stayed on a rooted 2.1.
Click to expand...
Click to collapse
Huh, that's weird. What rom are you using?
If you're using a rooted rom then you should be getting a # when you type "su" into the terminal..
Do you have the SU app installed? Did you get an SU Permission request when you opened the terminal for the first time? If so, did you grant the terminal emulator SU permission?
im using a stock 2.1 rom and i do have superuser permissions installed. i also have setcpu for root users installed and "su" grants "setcpu" permission.
i also forgot to mention that i also put a "netarchy kernal" on their also which appears to me, works as it said. right now if i want to go into recovery it goes through clockwork, but i want to get amon ra's recovery on there instead.
ro2themax said:
im using a stock 2.1 rom and i do have superuser permissions installed. i also have setcpu for root users installed and "su" grants "setcpu" permission.
Click to expand...
Click to collapse
hmm.. which 2.1 stock? Was it a rooted stock (with busybox and su already in there) or did you install the su app?
Although sounds like it already had busybox if setcpu is getting permission.
If you are near your computer see if you can get a # using the adb shell. I'm a little stumped here..
the 2.1 stock came with the "su" already. i just posted a quick update on the my previous post that i flashed a netarchy kernal on my evo also. i dont know if that helps but i just forgot to mention it...
please bare with me, im by my computer and to go into adb shell do i need to plug my evo in as charge only and open a cmd from android tools to see if i get # ???
[Update 12/23] For those of you unable to install the new system update, I've found a solution -- scroll down to the update! I AM NOT RESPONSIBLE FOR ANY DAMAGES THAT MAY OCCUR!
So I figured I'd at least get things started - Credit goes to whomever first tried z4root on their Droid Pro - and to mahst687 for the deodexing.
Lets Begin!
Resources:
Motorola ADB Driver
Android SDK
xUltimate V2.2.2
(Can't post links apparently, sorry -- googles your friend!)
#1 Root:
As seen on numerous android sites already, root is obtainable via z4root in the market. It may not work the first, second, or even third time -- just keep trying, it works I promise.
#2 Bootstrap and Clockwork Recovery
Download and install 'Rom Manager' from the Market. Once installed flash the Droid2 Clockwork Recovery. After flashing, obtain the Droid2 Bootstrapper and install it. Confirm Clockwork Recovery works by booting to recovery via Bootstrap.
#2 Deodex:
Download Android SDK for ADB, as well as the Motorola ADB Drivers posted above. Second, download xUltimate - also posted above. Once everything is downloaded and installed we're ready to begin.
1. Run Main in the xUltimate package - if the ADB drivers installed successfully you should be greeted with a menu containing several options - great!
2. Next run option 1.
3. Run option 2.
3. Run option 3 - sit back and relax for a bit
4. Once option 3 is done doing its thing, navigate to the xUltimate folder, more specifically the "origi_frame", and delete guava.odex
5. Run option 4 - it'll be a short wait
6. Exit the xUltimate
7. Enable USB Mass Storage on the phone and transfer both "done_app", and "done_frame" to the ROOT of the SD card.
8. Once both folders have transferred disable USB Storage, but keep the phone plugged in via USB.
9. Open up a command prompt and browse to the android SDK Tools folder (or where ever your ADB executable is located).
10. Enter the following commands:
Code:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
11. If all went well your phone should reboot - which may take a few minutes. Enjoy!
[Update]12/23/2010
For those of you unable to get the new Droid Pro OTA working I have found a solution! You will need:
1)Root
2)Clockwork Recovery
3)System.img from update
4)Current Nandroid backup of your phone
5)ADB drivers and ASDK
So lets begin.
1)Boot into Clockwork recovery and create a backup of your phone.
2)Once complete, mount the phone as USB storage and pull the system.img file from the nandroid backup folder, as well as the nandroid.md5 (KEEP THESE FILES SAFE!!!!!)
3)Obtain the system.img file from here (Compliments of whoopsiedaisy).
4)Replace the system.img file in the Nandroid backup folder on your PHONE.
5)ADB into your phone (preferably still in recovery) and do the following:
Code:
adb shell
# cd /sdcard/clockworkmod/backup/2010-xx-xx.xx.xx.xx
# rm nandroid.md5
# md5sum *img > nandroid.md5
6)If all goes will it should create a new MD5 checksum file utilizing the new system.img
7)Go to the 'backup and restore' menu in Clockwork, and select 'Advanced Restore'
8)Select the correct nandroid backup folder where the new system.img file is located, and then select 'Restore System'
9)Assuming all goes well, go to Settings, About and check your new system version!
Nice, can't wait to try this on my wifes phone after work.
Sent from my ADR6300 using XDA App
Is the second step necessary if you just want root access so you can install Wireless tether, etc?
jayhammy said:
Is the second step necessary if you just want root access so you can install Wireless tether, etc?
Click to expand...
Click to collapse
Not at all. Simply run z4 if all you require is root access (and a host of apps like Wireless Tether, DroCap, Titanium Backup ...)
Can you please post the quickoffice apk from the Dpro so I can put on an DX? Same would go for the software that allows me to Invite attendees to meetings using GAL. It be copasetic if you can.
Thanks a ton! Freaking worked flawlessly on my Droid X.
Nate
Cool. Cant wait to try this on my wife's phone.
I downloaded everything you said and i started my deodex but when i select option 3 in main it tells me "error no odex file" have i done something wrong please advise
Is it really that simple?
I feel like I must be missing something. I just download an app from the market and reboot and I'm rooted?
Also, what is the deodex for? I want to root my phone to install the apps I want and I want wifi tether. Do I need it?
Also, I really want to understand what is going on under the hood, but I don't know where to start. Is there a 'for dummies' tutorial somewhere that I can go to to start understanding what all of this stuff is, so I can make informed decisions for myself about what I want instead of begging for help on internet forums? Thanks in advance for any suggestions.
Is there a way to unroot? I am not rooted but just curious.
rllong1 said:
Is there a way to unroot? I am not rooted but just curious.
Click to expand...
Click to collapse
Yes, Z4Root app allows you to root, re-root, and UNroot.
I see no uproot button on the screen. Only a root button
Sent from my DROID PRO using XDA App
I had version 1.1 of z4. I now have the. 3 version and it has the unroot button
Sent from my DROID PRO using XDA App
rllong1 said:
I see no uproot button on the screen. Only a root button
Sent from my DROID PRO using XDA App
Click to expand...
Click to collapse
You'll only see the unroot button once you've rooted. Otherwise, it will first show only the "root" option.
jayhammy said:
You'll only see the unroot button once you've rooted. Otherwise, it will first show only the "root" option.
Click to expand...
Click to collapse
I was rooted. I had titanium installed and superuser. Z4 ran fine but I had an old version of it. I dont know if that matters but thats all I did. I downloaded the 1.3 version and I now have the unroot button. On the old version there was no option for temp root either. Just root. On the version I have now there is a temp root and perm root button.
Would just like to let people know that your method for "updating" via nandroid backup would not work for me. Followed all the instructions to the letter and during the advanced restore I continually received md5sum mismatch errors.
So I took the chance and updated through the OTA update, it installed fine but lost root. Ran z4root (twice) and gained root access again .
Looking forward to some real custom daily driver roms for this guy.
darkninja157 said:
Would just like to let people know that your method for "updating" via nandroid backup would not work for me. Followed all the instructions to the letter and during the advanced restore I continually received md5sum mismatch errors.
So I took the chance and updated through the OTA update, it installed fine but lost root. Ran z4root (twice) and gained root access again .
Looking forward to some real custom daily driver roms for this guy.
Click to expand...
Click to collapse
Is there a way to uninstall the CWM recovery?
darkninja157 said:
Would just like to let people know that your method for "updating" via nandroid backup would not work for me. Followed all the instructions to the letter and during the advanced restore I continually received md5sum mismatch errors.
So I took the chance and updated through the OTA update, it installed fine but lost root. Ran z4root (twice) and gained root access again .
Looking forward to some real custom daily driver roms for this guy.
Click to expand...
Click to collapse
Kinda new to the whole rooting thing, just got a new Pro and rooted successfully with z4root, got rid of bloatware and installed titanium backup, wifi tether, etc. Am I correct in reading your post that I can unroot, OTA update, and re-root again? If so, will I have to uninstall bloatware again, or reinstall root apps? Or any other repeats? Any danger in doing this?
mynameismolotov said:
Kinda new to the whole rooting thing, just got a new Pro and rooted successfully with z4root, got rid of bloatware and installed titanium backup, wifi tether, etc. Am I correct in reading your post that I can unroot, OTA update, and re-root again? If so, will I have to uninstall bloatware again, or reinstall root apps? Or any other repeats? Any danger in doing this?
Click to expand...
Click to collapse
No need to un-root. This update is for the system portion only and does not touch the userdata. I simply went ahead on the rooted phone, let the OTA update download and install. In doing so lost root, but had no trouble gaining root access again via z4root. Did not have to re-remove any of the bloatware, at least if I remember correctly. Root apps will not need to be reinstalled but you may need to re-give them permission for root access. No danger that I have noticed or can think of.
For anyone doing the update the android method....
For it to work
You must do the adb "new" md5 creation portion with your phone in clockwork recovery for it to work and to not receive the mismatch error...
To do this, reboot recovery... then plug in usb from your computer... during the phone boot into recovery you should hear the alert from your computer that something from usb was plugged in. Finally, use the mount option in recovery to mount sd card to be able to transfer the .img file over to the correct directory then unmount sd card and do the adb commands in terminal window...
I had the same mismatch errors using my windows 7 machine and creating the md5 with android booted
Hope this helps
Hi, I've got a Motorola Defy in Argentina (Carrier: Personal, means telecom). Well, I want to Root it, I've tryied z4mod, the ADB Method, 1 click, etc, and I still got the message "The application xxxx needs root user permissions", btw I have the Root (#) console in "adb shell", but I can't move files to /system/media (whit "AndExplorer" from mobile). Do I have to mount the FS there??
I've got the "Superuser" app working, and some applications whit "Root permissions" (because I've checked Remember my answer on the Popup when the app needs root privilegies)
Im a little bit confused because the version is not similar that you use here.
Version Number: JORLA_U3_6.14.7
Firmware version: 2.1-update1
So, I want to root it, and maybe upgrade to Froyo, but that questions make me scared (specially if i brick it).
What should I do?
PS: I've made a "Backup" with SystemRecovery app. This backup will work if I want to back my firmware to the stock one? (forgive the apps, I don't care).
Nobody can guarantee your backup will work, but it's a risk you'll have to take if you want to hack.
According to my search, your carrier uses UMTS 850 / 1900. This means you could have a different baseband firmware than the T-Mobile users here, and definitely different from the European users. The problem is, the only SBF files available are for European 900/2100.
So first things first, take a nandroid backup from the custom bootstrap recovery if you can get that working. Back up those files somewhere safe.
Read about the "3g fix". There is a folder containing the baseband firmware files, and you'll want to back those up in case you lose 3g on a custom ROM.
If your phone becomes unbootable, you'll have to flash an SBF to boot it, *then* root it again, install custom recovery again, and finally restore the nandroid backup.
Sent from my Nexus One using XDA App
Ok, thanks for the info. I've tryied to do a "nandroid backup" with the upgrade.zip stuff, but it just restarts and do nothing. I can't see any changes on my SDcard.
BTW, how I can run a .apk as root? (I want the AndExplorer to be root so I can copy some stuff to /system). I've got actually a root (#) terminal in adb shell and in Terminal emulator (via command su).
Thanks
cocus said:
Ok, thanks for the info. I've tryied to do a "nandroid backup" with the upgrade.zip stuff, but it just restarts and do nothing. I can't see any changes on my SDcard.
BTW, how I can run a .apk as root? (I want the AndExplorer to be root so I can copy some stuff to /system). I've got actually a root (#) terminal in adb shell and in Terminal emulator (via command su).
Thanks
Click to expand...
Click to collapse
How are you attempting to do this backup?
You need to download the bootstrap custom recovery, and use that to boot into the recovery menu. From there you go into backup/restore.
If you have successfully rooted your phone, then all apps have the opportunity to run as root. They should be able to make the request via Superuser Permissions, which would then prompt you.
Ok, but the bootstrap custom recovery is for 2.51 or similar firmware numbers, I've got 6.14. So, I really didn't test because I don't have experience with this things and I don't want to screw up all.
I tell you, for example, the Terminal Emulator runs on root when I run "su": Android requested Superuser permissions to me, and I ticked remember option, and now I can run "su" without the Superuser request.
BTW, I've got a root shell on adb (when I reboot the phone, I loose the root ). That means that is rooted??? (Got it using RATC)
Well, either it's compatible or it's not. If the bootstrap makes your phone unbootable... I guess you'll have to try for a warranty claim
Sent from my Nexus One using XDA App
Hahaha, I like to flash things and understand how it works, but in this case, I would prefer not screw nothing. Btw, I've buyed it on 15/jan.
So, for my other question the Terminal Emulator runs on root when I run "su": Android requested Superuser permissions to me, and I ticked remember option, and now I can run "su" without the Superuser request.
But when I restart the phone, I loose the # on "adb shell".
BTW, I've found the open source code of an earlier version of my defy on
opensource.motorola.com/sf/go/projects.moto_defy/frs.defy_latam
Anyone knowns how to compile this? I've got Debian lenny, Ubuntu 10.04, Ubuntu 10.10.
Thanks
Compiling a ROM yourself won't help if you can't sign it with Motorola's key. Yay locked bootloader...
Sent from my Nexus One using XDA App
Cocus,
I got the same phone as yours. Also from Personal.
And I am on the same situation, want to flash it, but not to brick it.
Let me know if you find out something ...
Hi, yes you can contact me via PM & I will send all the stuff that I've got. But I only get the rootshell via RageAgainstTheCage. When you reboot it you loose it, but you can use "su" or "rootshell" to get it again.
Now Im playing with C and C++ native code, with the ndk and sdk (no java ). Contact me
z4root worked in argentine (Latin American) defy.
Hi
I have a Motorola Defy like yours , (in Argentina - Carrier: Personal ).
I have rooted successfully using z4root 1.3.0 , that you can get from this post (look attached file at end ):
http://forum.xda-developers.com/showthread.php?t=833953
With z4root 1.3 you have the option of get root temporarily or permanent. The first one doesn't works for me ( no errors but no root ). The permanent root yes, works like a charm .
Hi, It seems that is not working for me... I've touched the permanent option, it restarted and the z4root says that is rooted, but I haven't the root console in adb shell, neither the apps run as root.
Edit: If I try to run "su" on the non-root console($) it says "Permission denied". But, running "rootshell" from RATC, it gives me a root shell.
Hey all, I'm using the Dirty Cow script to try and finally root my AT&T Note 4. I've got the terminal up and running in Linux and the script executes. I understand how the script works and know I'll essentially be able to give one execution root access. I'm attempting to give that to the TWRP Manager app so I can simply write a new recovery and then flash a different ROM, essentially rooting the device.
Where I run into trouble is finding the apk in the terminal window. Beyond the actual root directory the LS command doesn't work to list the file structure, so I have to go blind. Anyone have any advice on how I can find the apk file to point it to?
It's currently running 6.0 if that matters.
Thanks!