I have an issue and it's killing me. I took the latest DX update to .621 and can't re-root my phone.
I've tried the Motofail, Droid 4 and Droid 3 methods and I encounter an error on each one. Apparently, if you were rooted before, these methods see remnants of BusyBox and SuperUser and don't know how to get past them to root. I wish I knew about RootKeeper prior, but it's too late now.
---------------------------------------------------------------------
Here's the suggested trouble-shooting that I can't get to work:
1. Open a Command Prompt in the folder where you extracted the one-click root package (see instructions for rooting). If you are using Windows 7, you can just use Shift+Right-Click on the folder you extracted the package and choose to "Open a command prompt here". For other operating systems or versions of Windows, you may require some DOS experience or need to Google how to change directories.
2. In the command prompt, type the following command:
adb shell
3. If you receive any kind of error, then you may not be in the folder where you extracted ADB.exe or you may need to reboot your computer, your phone, or check the connection. You should receive an ADB prompt ending with either a # or a $.
4. If the line ends with a $, then run the one-click exploit for Windows XP (even if you have Windows Vista or 7) and only complete step 1.
5. When you have adb shell ending with a #, type the following commands:
mount -o remount,rw /dev/block/system /system rm /system/bin/su rm /system/xbin/su
Ignore any messages that warn you about the file not being found/missing. We're removing old copies of su/superuser which are causing this one-click root method to fail.
Either I don't understand Step 4 above in red, or something isn't working properly. I never get the # to show to do Step 5. Oh, and at Step 5, am I supposed to hit enter after each of those commands??
Any ideas, tips, or suggestions here? I need my root!
Last edited by mahers; February 21st, 2012 at 11:35 AM.
Why don't you sbf back to .602 and do it correctly? It will probably be the simplest method in all honesty
Ha! I knew that was coming. I have never SBF'ed before and was hoping for an easier way. Since I have everything backed up with TU anyway, I guess it won't hurt.
I tried uninstalling BB and SU, but my phone is smarter than me...it obviously didn't work.
Last edited by mahers; February 21st, 2012 at 11:58 AM.
What can I say, I'm chicken! And just to be clear, I would SBF back to .602, root using one of the above methods, use RootKeeper to hide root, update to .621, then use RootKeeper to get back root?
I think when I type out all the steps, it seems more complicated than the "fix" suggested in my OP, but since that isn't working, I guess I gotta do what I gotta do.
Be very careful. I did try to SBF back to .602, and am getting the dreaded A5,70,70,00,1F MEM_MAP Blank error. If anyone is still on .621, has/hasn't rooted, and is handy with sbf_flash in Linux, I'd appreciate a PM to see if I can't fix this small problem. (and before you ask, tried the .602 and .340 SBFs. Both break, hard.)
can u please elaborate? did you miss a step, or mess up somehwere? i am thinking i'd just follow the sbf steps in the stickied root thread here, but if there's an issue, please advise!! thx
Not much to elaborate on, sadly. Tried using sbf_flash and RSDLite for the 340 and 602 SBFs, nothing can resurrect the DroidX. I've been able to do some tricks to get different bootloader errors, but no booting DroidX.
So, until a .621 SBF comes out, if ever, or someone figures out a way to fix the problem, I wouldn't recommend SBFing off of .621.
Device(s): LG Ally - Retired
Droid X- Retired
HTC Rezound with Beats!
Carrier: Not Provided
Thanks: 55
Thanked 36 Times in 24 Posts
I wouldn't SBF it this time... I've been flashing for ever, but I recieved the soak, didnt like it, sbf'd... and poof... bootloader error. Haven't been able to recover since. Tried .340 and .602 ... no go... theyve changed something.. Idk if its the bootloader... the keys... or what the crap it is.... but I've got a perma brick on my hands... and all I gots is a LG ally... yeah tell me abt it
Rat bastards! So it seems the only way to retain root is to use RootKeeper BEFORE the update to .621! I knew I shouldn't have jumped on this so quickly.
he is anything but a fine fellow, but that is how i perceive him, i dont care too much for him at all, he loves attention and will use this as a way to get more attention.
p3droid on twitter
mydroidworld is his forum
he will usually respond to twitter feeds, but sometimes will not.
his contacts inside of motorola should have the .621 update.
The Following 2 Users Say Thank You to VoidedSaint For This Useful Post:
he is anything but a fine fellow, but that is how i perceive him, i dont care too much for him at all, he loves attention and will use this as a way to get more attention.
p3droid on twitter
mydroidworld is his forum
he will usually respond to twitter feeds, but sometimes will not.
his contacts inside of motorola should have the .621 update.
I personally don't care what he is, as long as he can help with this. I don't have twitter (useless, IMHO) but I'm hoping someone else does reach out to him. I saw on another forum that someone was going to try...we shall see. At least I didn't try to SBF last night and brick the phone! A working non-rooted phone on .621 is better than nothing.
Just saw this on p3's site, so it's not looking good for a working solution:
Now that he has decided to no longer provide the hacked stock firmware or has lost access to the files,
Last edited by mahers; February 22nd, 2012 at 12:24 PM.
yeah, just another reason why moto is a failing ship (for the dev community that is) its hard to believe that the OG droid was the first and only truly unlocked device in the US
No proof that I can find atm, but it's been said the xoom2/xyboard root may work. Anyone willing to give it a shot and report back? I can't do anything at work (other than surf the net all day)
No proof that I can find atm, but it's been said the xoom2/xyboard root may work. Anyone willing to give it a shot and report back? I can't do anything at work (other than surf the net all day)
If this is the same as the Droid 4 method, I tried it and it didn't work. My phone is still at 621, not rooted, and running like cr*p.
No idea. I tried various ones as well (I think D3, D4, MotoFail), with no luck. I haven't tried this one yet, but may when I get home. If I can find where I saw the comment and any success, I will let you all know.
Honestly though, I haven't seen any difference in .621, good or bad.
Any ideas, tips, or suggestions here? I need my root!
I was in almost the same boat. I started with 605 rooted, and the OTA update wouldn't apply. So I did:
- SBF back to 602
- OTA to 605
- ran Pete's root tools to get root
- ran OTA Rootkeeper to save my root
- OTA to 621
I attempted to restore root with Rootkeeper, but it failed! Turns out my problem was that I had root previously, and that gums up the process. So I was on 621 with no root - just like you, except I did have a backup of my su program in /system/su-backup created by Rootkeeper. I was able to recover from this using Z4 1.3. I chose to "temporary root", which didn't seem to do anything, but when I "adb shell" into the phone I was able to execute /system/su-backup and it gave me a root (#) prompt. From there I just copied /system/su-backup to /system/xbin/su, and my problem was fixed.
What I suggest you try:
1. get a copy of the su binary, and the Superuser.apk
2. copy them to your sd card
3. run Z4 and choose temporary root
4. once z4 runs, do "adb shell"
5. in the shell ($ prompt) execute "/sdcard/su" to get a root prompt (#)
6. run the following command in the root prompt:
- cp /sdcard/su /system/xbin/su
- install /sdcard/Superuser.apk
- chmod 4755 /system/xbin/su
- chmod 755 /system/xbin/busybox
- /system/xbin/busybox --install -s /system/xbin/
- ln -s /system/xbin/su /system/bin/su
I am in the same non rooted 621 situation. If I ever get the droid x rooted again, I will shut off ota for good. I can not understand why verizon can not detect by ota if the phone is rooted and just leave it that way.
Even Microsoft being the stinkers that they are, gives us a choice to install updates or not and to pick which ones we want. Does this phone belong to us or not! What right does Verizon have to shut out the owners of the equipment from having root. The phone does not belong to them!
When you root-ed your Droid X you assumed total responsibility for it.
They gave you the choice of installing 4.5.621 or not. You chose to install it.
... Thom
No one expected Moto to prevent you from going back to Froyo or previous Gingerbread, no need to be so negative towards the unlucky ones stuck with 621
I will have to say this.. you "accepted full responsibility" for the phone the minute you walk out of the store with it....Mine is almost two years old, so I would not be receiving any "refurbished" nonsense anyway. I carry the insurance as well, which, knock on wood have never used.. I can olny imagine what kind of hassle that would be.. I was so frustrated after the ota's that destroyed the original phone I liked so much... made it very undesirable, border line un usable to the point I'm thinking they sell these things crappy so you buy buy and keep buying. I tried to see if they would put it back to the original version I bought it with and I get the deer in headlights look all techs at verizon must have to learn before being put onto the sales floor. They should not of screwed people that feel it's their right to perfect something or bring it halfway back up to par with the way it was when you bought it. I enjoyed having a few different roms to switch between... the stock stuff has nice features, but there is a lot of un neccessary bloat and junk. We should still be able to root the phone, bottom line. This phone still runs fine for what I need... I should not have to be forced to upgrade so quickly, although a front facing camera intrigues me...
Device(s): Bionic (98.72.22)
Droid X (4.5.621 root)
Carrier: vzw
Thanks: 874
Thanked 927 Times in 662 Posts
Quote:
Originally Posted by BridgeScore
I was not given the choice of not installing. The two choices were 1. install or 2. install later.
I kept getting this pop-up for three days and I got tired clicking on later. I wish they had a choice to not install.
I chose to install 4.5.621 and wait for a future root method. (The Droid X is my test machine.) I have not validated the following information.
To reiterate ... you made the choice to assume total responsibility for your Droid X. I fail to see the logic in your assertion that Motorola/Verizon should support you in that endeavor.
If you Google ".621 stop install" the second hit is a YouTube video ...
You android is bricked and the only solution is to find the current .621
and push it to the phone, no other OS version will work.
Verizon Tech support does not care, nor will they point you to the SBF
So Be sure the one you find is Stamped 02-26-12 and is .621
use RSD lite to push it on your phone....
Then wait a few weeks to see if anyone has found a way around this
anal behavior.
By the by, Verizon store tells me your phone can fail even with no root when
you update,,, their contention is, Gee buy a Android Nexus, its made for
folks like you and me that want to turn the phone inside out
im not sure i follow what you mean by all this politically, verizon stores are trying to push out the Droid Razr right now, and they could care less about the galaxy nexus, which if verizon doesnt sell enough, or outsell the droid line, they may stop carrying the nexus brand and that will surely leave alot many of us upset.
if the fails when there is no root, they have to fix it themselves, not you, as it is a verizon issue then with the software they push out.
Device(s): HP TouchPad,
Samsung Galaxy Nexus,
Google Nexus 7,
Surface RT
Carrier: Verizon
Thanks: 775
Thanked 1,620 Times in 1,262 Posts
Updating to .621 w/o installing rootkeeper results in no root.
No 100% guarantee that rootkeeper will work either, but better than nothing.
I saw in another forum where a CM9 user sbf'd due to an issue, grabbed the OTA thinking it was 605 and then lost root. Needless to say he's not happy.
IMO, the only resolution is to sell the X to someone who wants stock and buy one that has a custom rom on it OR use stock with the hope someone might fix it for another Moto phone and it happens to work with the X.
Damn, I have had my Droid X since launch weekend (back in July of 2010) and just decided to root my device today, but I already downloaded the OTA 621 update and just visited this rooting forum today. So I guess I am out of luck until a rooting method comes along for 621? Do you think that is likely at all with the phone being old now? I mainly want to root because I just pre-ordered the new wireless-only iPad and I want to wireless tether while away from Wifi. I heard you NEED to have root in order to wireless tether. I already have EasyTether from Amazon and it works wonderfully for my laptop. Is there a Wifi tether that I can get without root? Thanks!
Device(s): RAZR JellyBean rooted
Wife: LG intuition
Carrier: The Big Red Menace
Thanks: 122
Thanked 105 Times in 91 Posts
Sooooo, how bout that local sports franchise.........
Anybody got a line on rooting this monster we call .621-zilla? Been trying every method I can find. Might try another SBF and attempt root before activating the device, perhaps this will work, since my apps won't be available to mess things up? IDK, it is kinda fun messing with it to try to get root back...
__________________
Got ants?
Posts by this member may contain any of the following:
Sarcasm, Dumb jokes, Not-so-snappy comebacks, Off color comments, And rarely; Good information...You have been warned.
Device(s): PLASMA ROM @
http://androidforums.com/verizon-galaxy-s3-all-things-root/696581-plasmarom-iv.html#pos
Carrier: Verizon
Thanks: 27
Thanked 96 Times in 71 Posts
What if?
Instead of trying to root .621, someone made a .602 sbf that told the bootloader that it was version .622. Wouldn't that be easier than trying to find a new way to root. I'm not a programmer, but it seems like it would be easier than trying to break the code.
Yes I know I could pay an additional $20/month for only 2 GB on my now unlimited plan but I figure I should be able to use my unlimited data as I see fit. I think I will just have to try to root my sister's Fascinate instead before I get the new iPad. But yes, this $20/month plan is still cheaper than the stand-alone $30/month plan for 2 GB for iPad that Verizon currently charges. And I also saved $130 on the cost of the new iPad. Just in case rooting on the Samsung Fascinate doesn't work as intended, does anybody know if I can cancel the HotSpot whenever I feel like? Like can I do just one month of it then cancel without affecting anything else? No contract there right?
Device(s): RAZR JellyBean rooted
Wife: LG intuition
Carrier: The Big Red Menace
Thanks: 122
Thanked 105 Times in 91 Posts
Quote:
Originally Posted by WhoDoo Voodoo
Instead of trying to root .621, someone made a .602 sbf that told the bootloader that it was version .622. Wouldn't that be easier than trying to find a new way to root. I'm not a programmer, but it seems like it would be easier than trying to break the code.
That would be a good idea, but the problem as i understand it is there is a signature within the SBF file that would need to be generated for any changes made. If the signatures don't match, it won't load. Also, from reading on some other forums, I have found that the SBF file itself is encrypted this time and nobody has been able to keygen it.
Might be a long road for those of us with .621, but then again, it might not. I don't have that answer yet, but like I said before, it IS kinda fun messing with it to try to regain root access....lol
Device(s): Bionic (98.72.22)
Droid X (4.5.621 root)
Carrier: vzw
Thanks: 874
Thanked 927 Times in 662 Posts
Quote:
Originally Posted by IceMan5043
Yes I know I could pay an additional $20/month for only 2 GB on my now unlimited plan but I figure I should be able to use my unlimited data as I see fit. I think I will just have to try to root my sister's Fascinate instead before I get the new iPad. But yes, this $20/month plan is still cheaper than the stand-alone $30/month plan for 2 GB for iPad that Verizon currently charges. And I also saved $130 on the cost of the new iPad. Just in case rooting on the Samsung Fascinate doesn't work as intended, does anybody know if I can cancel the HotSpot whenever I feel like? Like can I do just one month of it then cancel without affecting anything else? No contract there right?
I don't know their current rules for new users. I had mobile hot spot with unlimited data on my Droid X and it was grandfathered when I got my Bionic.
For me it is just part of my long term contract. You would have to check with Verizon fr what they have on a short term basis.
Device(s): RAZR JellyBean rooted
Wife: LG intuition
Carrier: The Big Red Menace
Thanks: 122
Thanked 105 Times in 91 Posts
Quote:
Originally Posted by WhoDoo Voodoo
Could you just tell it it's .621 to match the old sig then?
editing an SBF file, like other computer files, changes the MD5 checksum.
Also, this version has been encrypted so it's pretty much impossible to edit without making a big mess of things.
There are some genius devs out there, I'm sure someone will come up with a solution sooner or later, this is getting to be a larger base of people that have this version, so it may be necessary to root it somehow and possibly do some development for ROMs
Ok so all root methods for 1 click is a fail, tried it all literally ALL 621.fml as I have come to call it has forced me to crawl out of my shell and start collaborating with others. I have a DROIDX never rooted fully updated ready to start from scratch post what ya know and Ill post what I find p3droid is as I can see out of the game so its on us.
- Files that need to be changed for root have been switched to read only after update. I am however having trouble accessing these files manually as I have never done this before any suggestions? if I can change the read write on the files manually then the old 1 click methods might work. I can only hope its that simple.
- for previously rooted phones the same problem exists with the old superuser, su binary and busy box all have been changed to read only causing the old 1 clicks to fail.
Last edited by rebel86; March 13th, 2012 at 12:23 PM.
Problems re-rooting after latest .621 update!
I have never SBF'ed before and was hoping for an easier way. Since I have everything backed up with TU anyway, I guess it won't hurt.
I don't have twitter (useless, IMHO) but I'm hoping someone else does reach out to him. I saw on another forum that someone was going to try...we shall see. At least I didn't try to SBF last night and brick the phone! A working non-rooted phone on .621 is better than nothing.
