Here is the deal. I was rooted before .621 when .621 hit I let it update me and used it for quite awhile. Now I'm getting the urge to go to a custom ROM. I followed the steps to get back to SBF .604, it's running great and my radio is AOK.
But for the life of me I can't get root back now. I've tried Pete's way on my Linux box and I get errors. I've checked my phone to see what's going on and when I adb I'm getting $ instead of #.
I've even tried z4 just to see if it would work, it can't do it either.
What is doing to be my best way of getting root back? I looked in my bin and sbin and I don't see su in there.
Here is what I'm running on DX
4.5.604.MB809.ACG-nTelos.en.US
Model Number Milestone X
Android Version 2.3.5
Any help is appreciated. I have access to Linux and Windows 7.
DanGarion said:
Here is the deal. I was rooted before .621 when .621 hit I let it update me and used it for quite awhile. Now I'm getting the urge to go to a custom ROM. I followed the steps to get back to SBF .604, it's running great and my radio is AOK.
But for the life of me I can't get root back now. I've tried Pete's way on my Linux box and I get errors. I've checked my phone to see what's going on and when I adb I'm getting $ instead of #.
I've even tried z4 just to see if it would work, it can't do it either.
What is doing to be my best way of getting root back? I looked in my bin and sbin and I don't see su in there.
Here is what I'm running on DX
4.5.604.MB809.ACG-nTelos.en.US
Model Number Milestone X
Android Version 2.3.5
Any help is appreciated. I have access to Linux and Windows 7.
Click to expand...
Click to collapse
Nevermind, 1KDS iso with zergrush fixed it.
DanGarion said:
Nevermind, 1KDS iso with zergrush fixed it.
Click to expand...
Click to collapse
can you explain the steps you did to gain root. I have the exact same problem you had but I can't get root whatsoever.
Sent from my Rooted OG Droid Incredible.
phillybizzle said:
can you explain the steps you did to gain root. I have the exact same problem you had but I can't get root whatsoever.
Sent from my Rooted OG Droid Incredible.
Click to expand...
Click to collapse
You are on .604 and have attempted to root via either zergrush v3 or zergrush v4?
Sent from my Galaxy Nexus using Tapatalk 2
Related
Hoping someone can point me in the right direction. Prior to OTA 2.2.1 had my DX rooted for tethering, but forgot to unroot this week before finally running the update that VZn pushed out. Now when i try to root with any method i can find info on, the rageagainstthecage process gets me to a point where rooting stops. Using ADB shows the DX is connected but offline and the whole process just stops there. Rebooting the DX is the only way to start all over again with the same results. Have seen some posts that maybe the later OTA was different than the earlier one and thats why some are having rooting issues. btw, was using pc mode and debug enabled.
I Sure do miss that tethering!
DasNas said:
Hoping someone can point me in the right direction. Prior to OTA 2.2.1 had my DX rooted for tethering, but forgot to unroot this week before finally running the update that VZn pushed out. Now when i try to root with any method i can find info on, the rageagainstthecage process gets me to a point where rooting stops. Using ADB shows the DX is connected but offline and the whole process just stops there. Rebooting the DX is the only way to start all over again with the same results. Have seen some posts that maybe the later OTA was different than the earlier one and thats why some are having rooting issues. btw, was using pc mode and debug enabled.
I Sure do miss that tethering!
Click to expand...
Click to collapse
Find the APK file for Z4 root and give it a go that way or Superoneclick has always worked for me. Just make sure you have the latest drivers from Motorolla for your phone and PC OS. It's far easier then rageagainstthecage.
Thanks, some of the things I've tried... Z4 all 3 editions, they dont hang and run through as if there sucessful, but when the X reboots and i try running an app like root explorer. It says phone not rooted. Super1click gets stuck in a loop and using adb devices, shows device connected but offline. Rebooting phone is the only way out. I Just can't see what im missing here, other than I should have unrooted b4 the OTA update.
DasNas said:
Hoping someone can point me in the right direction. Prior to OTA 2.2.1 had my DX rooted for tethering, but forgot to unroot this week before finally running the update that VZn pushed out. Now when i try to root with any method i can find info on, the rageagainstthecage process gets me to a point where rooting stops. Using ADB shows the DX is connected but offline and the whole process just stops there. Rebooting the DX is the only way to start all over again with the same results. Have seen some posts that maybe the later OTA was different than the earlier one and thats why some are having rooting issues. btw, was using pc mode and debug enabled.
I Sure do miss that tethering!
Click to expand...
Click to collapse
There's been a coupe threads already started with your issue..I think there's one on the 3rd page called can't reroot after the ota update...find it and follow the directions..
Sent from my DROIDX
Thanks for pointing me in the right direction to find the right post. I have to admit it was a very different approach to finally being able to get RW access to the file system & then using a terminal emulator to delete the old Superuser.apk at 1st try i couldn't get rm superuser.apk to work (no such file or dir) then it hit me its case sesitive. 2nd try & it went away.
Finally rooted again & Tethered!
Android Life is Good Again!
DasNas said:
Thanks for pointing me in the right direction to find the right post. I have to admit it was a very different approach to finally being able to get RW access to the file system & then using a terminal emulator to delete the old Superuser.apk at 1st try i couldn't get rm superuser.apk to work (no such file or dir) then it hit me its case sesitive. 2nd try & it went away.
Finally rooted again & Tethered!
Android Life is Good Again!
Click to expand...
Click to collapse
That's good..Enjoy
Sent from my DROIDX
I installed a non-rooted GB for my Droid X, I can't install either Droid X or Droid 2 Recovery Bootstape to get back to 2.2.1, I also tried to install A4Root, but it didn't work at all.
Much appreciated If someone could give me advice and help me out. I'm stuck now:$
leoxhj said:
I installed a non-rooted GB for my Droid X, I can't install either Droid X or Droid 2 Recovery Bootstape to get back to 2.2.1, I also tried to install A4Root, but it didn't work at all.
Much appreciated If someone could give me advice and help me out. I'm stuck now:$
Click to expand...
Click to collapse
You will need to Sbf to 2.3.340.
Sent from my DROIDX using XDA App
leoxhj said:
I installed a non-rooted GB for my Droid X, I can't install either Droid X or Droid 2 Recovery Bootstape to get back to 2.2.1, I also tried to install A4Root, but it didn't work at all.
Much appreciated If someone could give me advice and help me out. I'm stuck now:$
Click to expand...
Click to collapse
Yeah, you just have to SBF back to .340 or .320; .340 didn't work for me but .320 did. This link provides the files you need to download and explains how to do it.
http://www.mydroidworld.com/forums/...id-x-gingerbread-2-3-3-release-prerooted.html
When can we expect a root within this GB??
Delirious17 said:
When can we expect a root within this GB??
Click to expand...
Click to collapse
there is one out already comes pre rooted and another version that is pre rooted and deodexed
I mean when can we expect to be able to root within GB itself, without having to sbf if I already am in GB.
semi related;
if anyone needs to flash a SBF on a 64 bit Windows OS the .sbf file will need to be in the root directory of your main hard drive (C:/) and you will need to SHIFT+RIGHT CLICK your RSD Lite shortcut and run as admin
putting this up here because it took me a few google searches to figure it out...
Delirious17 said:
I mean when can we expect to be able to root within GB itself, without having to sbf if I already am in GB.
Click to expand...
Click to collapse
People are working on this, it has proven to be more difficult than anyone thought. So I wouldn't be surprised if it takes a while.
Rooted Droid X loving Gingerbread...
Twitter: Sierra8561
I SBFed and used the pre-rooted version from P3Droid. I can get root apps to work like Titanium Backup. But when I go to adb I am at the $ and adb remount won't work. When I type su I get access denied. Any thoughts?
Edit: Nevermind, tried su again and the screen asked me for permission. I'm good.
Just SBF, if you haven't done it yet then now is the time, if you can't handle an SBF then you shouldn't really be modding your phone :-/ dont mean to sound harsh but really its a basic procedure and you WILL eventually need to do one.
Either way I would just go back, update to the rooted build, and trust in TBH. They will not leave us hanging and they will probably be able to keep us rooted through any official updates.
donballz said:
I SBFed and used the pre-rooted version from P3Droid. I can get root apps to work like Titanium Backup. But when I go to adb I am at the $ and adb remount won't work. When I type su I get access denied. Any thoughts?
Edit: Nevermind, tried su again and the screen asked me for permission. I'm good.
Click to expand...
Click to collapse
Open up superuser app in the phone and hit allow.
mithikx said:
semi related;
if anyone needs to flash a SBF on a 64 bit Windows OS the .sbf file will need to be in the root directory of your main hard drive (C:/) and you will need to SHIFT+RIGHT CLICK your RSD Lite shortcut and run as admin
putting this up here because it took me a few google searches to figure it out...
Click to expand...
Click to collapse
Not entirely true, at least in my experience on Win7 x64. For me it has been hit and miss. I have never had the sbf on c:\ and have sbf'd successfully at least 50+ times. Typically the sbf file is on my desktop or lately in a folder on the desktop because the temp files annoy me while its in progress.
What I have found is running RSD Lite 4.8 in XP compatibility mode seems to be th best bet. Since I started this, I have 6 sbf's without a fail. Prior to that it was just hit and miss taking 1-4 attempts to get it to sbf completely.
So I've searched around the net, and am not 100% sure what to do. Here is my situation.
I "rooted" my phone awhile ago, or so I thought, but now despite having superuser and trying to do the fix and update for it, it doesn't work, and no app can gain root access, however when I try to run droid easy root, it says i'm already rooted.
I'm running GB with build # 4.5.1_57_DX5-35 (if that helps).
All I want to do is re-root or whatever and install a rom (miUi specifically) over the default gingerbread motoblur one. I'm on a Mac btw and don't know much about this stuff...Any help is appreciated.
mdemps9190 said:
So I've searched around the net, and am not 100% sure what to do. Here is my situation.
I "rooted" my phone awhile ago, or so I thought, but now despite having superuser and trying to do the fix and update for it, it doesn't work, and no app can gain root access, however when I try to run droid easy root, it says i'm already rooted.
I'm running GB with build # 4.5.1_57_DX5-35 (if that helps).
All I want to do is re-root or whatever and install a rom (miUi specifically) over the default gingerbread motoblur one. I'm on a Mac btw and don't know much about this stuff...Any help is appreciated.
Click to expand...
Click to collapse
use the zergrush (aka doomlord) method posted in my signature, should fix you right up
edit: eww just saw where you said you were on a mac, not sure if this will work for the mac, i know that superoneclick also now uses the zergrush method. perhaps there is a mac version of that.
I'll try it out using VMware fusion and my XP partition...Hopefully it works. Might have some questions on the process if there aren't detailed instructions. Thanks.
my buddy has a droid x n he wants custom firmware on it, am i able to just find a odin package and downgrade the phone or just flash a custom firmware that way, or do i absulutly have to use ubuntu to root the .621 first?
You have to use Ubuntu. I just did it today. Took me 2 hours because I didn't know I had to type "sudo su" first.
Sent from Galaxy Note with CM9
a) If your buddy wants a custom ROM I'd check and see if he's on .621 or not - a lot of people are having a LOT of trouble with it (I just got off the phone with Verizon, they said other people have reported the same issue as me and the fix is to buy a new phone or have Motorola fix it). If he's not already on .621 I'd skip the headache and just install the ROM without ever upgrading to .621.
b) If he's on .621 basically what you have to do is install a non-Verizon ROM and then root that, and you have to use Linux because otherwise you'll overwrite your radio software and won't be able to use it on Verizon. People have had good luck with the ISOs here which will do it automatically.
netraven5000 said:
a) If your buddy wants a custom ROM I'd check and see if he's on .621 or not - a lot of people are having a LOT of trouble with it (I just got off the phone with Verizon, they said other people have reported the same issue as me and the fix is to buy a new phone or have Motorola fix it). If he's not already on .621 I'd skip the headache and just install the ROM without ever upgrading to .621.
b) If he's on .621 basically what you have to do is install a non-Verizon ROM and then root that, and you have to use Linux because otherwise you'll overwrite your radio software and won't be able to use it on Verizon. People have had good luck with the ISOs here which will do it automatically.
Click to expand...
Click to collapse
He was originally rooted and it was basically a forced update it didn't prompt him for the update then we came across the ISO burned to CD successfully flashed the phone using the ISO then when that was completed it did the auto reboot and got stuck in recovery mode from there we went to boot loader mode flashed the .602 sbf file successfully booted and waiting to try again
Sent from my SAMSUNG-SGH-I727 using xda premium
Ok, so I ultimately want to root this phone and install a custom ROM on it. However, it is not activated, and I cannot bypass the prompt to activate, I can only get to a dialer.
So, after reading the forums, it appears that the latest official FW is .621 and there's a root method for it, but it only works on .621. Obviously, root methods are version dependent. I figure I have to know the software version before continuing then.
Is there a code I can enter into the dialer to pull up software info? Or perhaps an adb command that doesn't require root? Anything at all I can do?
Or, do I even need software info? Can I simply proceed with some alternative root method?
Regards
Smith
EDIT: I ended up solving this through trial and error. I flashed the 2nd most recent sbf file and it produced an error in the bootloader, indicating that the device must've been on .621 so I sbf back to .621 and I'll proceed with that method.
EDIT 2: Ok, so that's fine and dandy and I was able to flash the sbf specified in the thread, but now zerg exploit won't run because I have no way of enabling adb :/ any ideas?
smithisize said:
Ok, so I ultimately want to root this phone and install a custom ROM on it. However, it is not activated, and I cannot bypass the prompt to activate, I can only get to a dialer.
So, after reading the forums, it appears that the latest official FW is .621 and there's a root method for it, but it only works on .621. Obviously, root methods are version dependent. I figure I have to know the software version before continuing then.
Is there a code I can enter into the dialer to pull up software info? Or perhaps an adb command that doesn't require root? Anything at all I can do?
Or, do I even need software info? Can I simply proceed with some alternative root method?
Regards
Smith
EDIT: I ended up solving this through trial and error. I flashed the 2nd most recent sbf file and it produced an error in the bootloader, indicating that the device must've been on .621 so I sbf back to .621 and I'll proceed with that method.
EDIT 2: Ok, so that's fine and dandy and I was able to flash the sbf specified in the thread, but now zerg exploit won't run because I have no way of enabling adb :/ any ideas?
Click to expand...
Click to collapse
http://www.droid-life.com/2010/06/10/tip-how-to-bypass-android-activation-screen-on-motorola-droid/ this shows how to by-pass the "activation", I just did it so it does in fact work for the Droid X M8810
dasfaust said:
http://www.droid-life.com/2010/06/10/tip-how-to-bypass-android-activation-screen-on-motorola-droid/ this shows how to by-pass the "activation", I just did it so it does in fact work for the Droid X M8810
Click to expand...
Click to collapse
You sir are incredible, thank you, I will try this when I get back to work tomorrow !
Sent from my SGH-I747 using xda app-developers app
Also, if you want to root, check out this thread:
http://forum.xda-developers.com/showthread.php?t=1800047
Please post any questions you have in that thread
Sent from my Galaxy Nexus using Tapatalk 2
Going to check that thread now, got ADB working, just need to path it, and get all the other stuff going... Got this Droid X free and it has that pesky .621 on it.