Update 4.5.5.621 is live and breaks the ability to SBF back to an earlier version.
Only take the update if your willing to lose the ability to SBF. A fix is in the works but there is no ETA.
If you decide to update, there is no way to root, but OTA Root Keeper can be used to retain root.
Sent from my DROIDX using Tapatalk
I am rooted on. 605 and im gonna update will this hurt my phone
Sent from my DROIDX using XDA App
htcdroidincredible23 said:
I am rooted on. 605 and im gonna update will this hurt my phone
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
No, but be aware that you will not be able to return to .605 or earlier, and you will lose root unless you use OTA Root Keeper.
Sent from my DROIDX using Tapatalk
infazzdar said:
Update 4.5.5.621 is live and breaks the ability to SBF back to an earlier version.
Only take the update if your willing to lose the ability to SBF. A fix is in the works but there is no ETA.
If you decide to update, there is no way to root, but OTA Root Keeper can be used to retain root.
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
I was on stock .605 with 1 click root then updated with the .621 OTA and after it was done I still had root. Verified by running Root Explorer and Titanium Backup.
Update: After reading a response to this post I decided to try and see if I could get root access with any new apps that were not installed prior to the .621 update and I have discovered that I cannot. So user trebuchet76 (the one that had questioned my results) had the right suspicion that I didn't really have root anymore but rather the apps I had installed prior to the .621 update that had root kept it after the update but new apps will not get root access.
I can't install the update
Sent from my DROIDX using XDA App
I'm running Liberty 3 ROM, and am quite happy with it. However, I've seen this SBF issue posted here and other places.
A few questions:
- can I update without flashing back to stock .605 (understanding I need to use OTA root keeper to keep root access)?
- once I do that, will I need to flash Liberty back on the phone again?
Basically, my DX was a total piece of crap until I switched off the Verizon stock .605 update. I would rather not lose the freedom I have now and be forced to stay with Blur and whatever other bloatware is installed by Verizon. In all likelihood I'll be upgrading in a few months anyway, and Liberty has made my phone not only tolerable, but fun again. I'd rather skip the update entirely than go back to the stock ROMs from Verizon.
Actually, my next phone choice will probably be based on how easy it is to root... ;-)
mikecico said:
I'm running Liberty 3 ROM, and am quite happy with it. However, I've seen this SBF issue posted here and other places.
A few questions:
- can I update without flashing back to stock .605 (understanding I need to use OTA root keeper to keep root access)?
- once I do that, will I need to flash Liberty back on the phone again?
Basically, my DX was a total piece of crap until I switched off the Verizon stock .605 update. I would rather not lose the freedom I have now and be forced to stay with Blur and whatever other bloatware is installed by Verizon. In all likelihood I'll be upgrading in a few months anyway, and Liberty has made my phone not only tolerable, but fun again. I'd rather skip the update entirely than go back to the stock ROMs from Verizon.
Actually, my next phone choice will probably be based on how easy it is to root... ;-)
Click to expand...
Click to collapse
Don't update! You won't be able to flash Liberty, and you won't be able to flash back to .605 to install Liberty.
If you update there is no going back. Ever.
Sent from my DROIDX using Tapatalk
What about a hard reset. Then root shut off ota then sfb 605 re_root shut ff ota again ? Could this work?
BridgeScore said:
What about a hard reset. Then root shut off ota then sfb 605 re_root shut ff ota again ? Could this work?
Click to expand...
Click to collapse
If you are on .605 or below disabling the OTA Updater will keep you from updating, but once you update there is no going back.
Sent from my Transformer TF101 using Tapatalk
i hadn't seen this thread when I took the ota. tried to sbf using rsd lite 4.8 and the following sbf files, 2.3.34, 4.5.596, and the latest 2.3.4-4.5.1. found the last one through a Google search, it said it would work but it doesn't. so my old dx is currently out of commission. i wanted to use it as media player but i guess that's not going to happen right now.
Droid Razr
marculous said:
i hadn't seen this thread when I took the ota. tried to sbf using rsd lite 4.8 and the following sbf files, 2.3.34, 4.5.596, and the latest 2.3.4-4.5.1. found the last one through a Google search, it said it would work but it doesn't. so my old dx is currently out of commission. i wanted to use it as media player but i guess that's not going to happen right now.
Droid Razr
Click to expand...
Click to collapse
The .621 SBF should work. Make sure your battery is charged and try SBFing again. If RSD Lite doesn't work try using Linux.
Sent from my DROIDX using Tapatalk
infazzdar said:
The .621 SBF should work. Make sure your battery is charged and try SBFing again. If RSD Lite doesn't work try using Linux.
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
it still failed and now battery is too low to program and dx won't leave bootloader with battery in.
Droid Razr
You have to use RSD 5.4 or higher with the .621 sbf.
OTA Update
Appears that keeping my .605 is a good thing, how do I disable the updater??
harveyhungwell said:
You have to use RSD 5.4 or higher with the .621 sbf.
Click to expand...
Click to collapse
is there a way to charge the battery? only bootloader screen comes up with battery in, says code corrupt, battery too low to program.
Droid Razr
marculous said:
is there a way to charge the battery? only bootloader screen comes up with battery in, says code corrupt, battery too low to program.
Droid Razr
Click to expand...
Click to collapse
You can strip the red and black wires in a USB cable and place the exposed copper to their respective battery terminals while the battery is in the phone.
This will allow you to SBF the device.
Sent from my Transformer TF101 using Tapatalk
Just thought I'd share this.............
So yesterday I figured I try to get root back and if anything it would brick the phone and there was an sbf to get it back. At least to .621 stock. Well I did the one click root ( droid3 i believe it was, with of course with droid 2 bootstrap ). So it put my phone back into clockworkmod and I was able to wipe everything including the dalvic cache and restored my phone to a backup I had from stock .605 that was rooted but no rom installed. It actually worked no brick, no nothing. So I ran the D2 bootstrap and went back into cwm and restored to another backup I had with liberty 2.0 running.....and that also worked. Now, I was surprised it actually worked so I went into about phone and confirmed! It did say .605. So I was ecstatic!
I was prepared to brick my phone (which wouldn't be the first or second time anyway) but glad it all worked out. Now im back to being rooted and running 4.5.605.
infazzdar said:
You can strip the red and black wires in a USB cable and place the exposed copper to their respective battery terminals while the battery is in the phone.
This will allow you to SBF the device.
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
going to try that this morning, and thanks for the tip.
holy **** it worked with rsd lite 4.8 after wiring split USB to battery. you are awesome.
Droid Razr
marculous said:
going to try that this morning, and thanks for the tip.
holy **** it worked with rsd lite 4.8 after wiring split USB to battery. you are awesome.
Droid Razr
Click to expand...
Click to collapse
I'm glad you got it worked out =D
Sent from my Transformer TF101 using Tapatalk
I'm on CM4DXGB, the only update's I will EVER take again for my DX is the ones the ROM devs put out, screw Moto's crap!
Related
Morning all,
Is anyone running the Gbread 595 leak yet? I am thinking about trying it out this morning, as everything I read indicates it will be the launching point for what could be the official 596 release on the 13th.
Let me know if you have any observations on this.
Thanks,
Steve
I downloaded it yesterday, and am running liberty v.5 on top of it and I love it. It is really fast, and other than a few bugs with my contacts syncing up with facebook, I am having no problems.
Im gonna wait it out, till we get the official release... Apex2.0.0 is pretty sweet for now
Sent from my DROIDX using XDA App
owenbeals said:
Im gonna wait it out, till we get the official release... Apex2.0.0 is pretty sweet for now
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
I agree. Apex is amazing. I will wait for it to update
Weird issue I am running into....
I upgraded to 588 with no problems from 340 Froyo. I used DroidX recovery to accomplish this. When I rebooted 588 I tried to go to 595. I tried using DroidX recovery but this did not allow me to boot into recovery...it only gave me a blank screen. When I got back to 588 I uninstalled DroidX recovery and then installed Droid2 recovery. I was then able to reboot into recovery and try to install 595. The install aborted saying it was looking for 3 arguments and got 4.
Any ideas? Which recovery should I be using thoughtout this?
Thanks,
Steve
Both recoveries (AFAIK) are the same clockwork recovery, it's just a different method of "bootstrapping" so that you can get into the recovery. Droid2 bootstrap works on gbread unless USB debugging is disabled, then droidx bootstrap works.
Sounds like you got a bad file.
Just redownload the file and it should work
Yes the one I downloaded yesterday was bad, and a new one was uploaded. I just downloaded the new one and am going to try again to move back up to 595. Once that happens I am hanging on til the 13th.
I would assume once this official update comes out then VZW will no longer support the DX with official updates. We really need to get Moto to unlock the bootloader for us, so we can continue to develop for the DX.
Steve
I have made it successfully to 595. I am having a problem with Gingerbreak 1.2, so I am betting there is something in 595 that doesnt allow it to root.
stevefxp said:
I have made it successfully to 595. I am having a problem with Gingerbreak 1.2, so I am betting there is something in 595 that doesnt allow it to root.
Click to expand...
Click to collapse
P3Droid released three different versions of .595: full stock, rooted and odexed, and rooted and deodexed.
You can try flashing one of the rooted .595 releases.
Sent from my DROIDX using XDA App
Yes it looks like the rooted ones will accept Gingerbreak. I may go back to .591 and hold there until the official OTA version comes out.
You shouldn't need Gingerbreak on the rooted ones, as they are already rooted.
stevefxp said:
Yes it looks like the rooted ones will accept Gingerbreak. I may go back to .591 and hold there until the official OTA version comes out.
Click to expand...
Click to collapse
If you are going to flash a rooted version what do you need gingerbreak for?
smiteme said:
I downloaded it yesterday, and am running liberty v.5 on top of it and I love it. It is really fast, and other than a few bugs with my contacts syncing up with facebook, I am having no problems.
Click to expand...
Click to collapse
So you're not running it at all then... lol. You downgraded it back to .591 when you installed Liberty.
Sent from my DROIDX using Tapatalk
Curious, I'm running .573 now, if I flashed the latest rooted & deoxed, do I really have to sbf back to Froyo before hand like I've read in other places? OR can I just flash over it and roll on?
You only need to flash back if you don't have root, I believe.
Sent from my DROIDX using XDA App
Not having luck.
I tried to install, initially from my rooted deoxed stock .340 to rooted deoxed .595, first got a corrupted file report....would not upgrade.
Next got boot loop (repeating M), so SBF back to stock 340...Rooted and tried again with the same file and got a very unstable phone, reboots etc.
The only thing I can think of is that the phone was stock rooted but not deoxed, so when I tried loading the deoxed version it didn't like it? no idea.
I did a wipe before each load but can't seem to get it to work on my phone. My phone is very new.
SBF'd back to stock unrooted and I'll leave it like that to see if I can get the update from VZW.
I believe you have to start at .588 (or .573) then flash .591 over it, then flash .595 over it.
Sent from my DROIDX using XDA App
I'm on 2.2 and waiting. Just not convinced about 595 and getting the update. How do we know its going to be 596.
Sent from my DROIDX using XDA App
infazzdar said:
I believe you have to start at .588 (or .573) then flash .591 over it, then flash .595 over it.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Not completely accurate.. I went from .588, to .595 without any adverse effects. Phone is a bit snappier than before too, app drawer scrolls more fluidly, etc.
So I got the official GingerBread OTA (Build 596) last night but I can't root it using gingerbreak and I use my phone to tether wirelessly on my tablet all day.
So my question is Has anyone rooted these build of GB and how?
Thanks
Does it cost mony to tether with the dx?
Sent from my DROIDX using XDA App
synplex said:
So I got the official GingerBread OTA (Build 596) last night but I can't root it using gingerbreak and I use my phone to tether wirelessly on my tablet all day.
So my question is Has anyone rooted these build of GB and how?
Thanks
Click to expand...
Click to collapse
I'm in the same boat as you. (got a replacement phone today and the wife updated it before I got home) I assumed there would be a simple way to root after the OTA but it looks like for now that isn't the case. I'm just going to wait a few days and see what happens.
Luckily .596 uses the same boot loader as froyo .340 so you can simply sbf the phone back to .340 then reroot and update to the prerooted .596 that p3droid posted on mdw.
SBF and root. Then you can flash the rooted version. Pm me if you need instructions on how to SBF.
Tethering using the official app costs money but there are other tethering apps
Oh ok, so like where can i find the other apps, n are they free? Also my phone was rooted n i was runnin the stock rom but i just sbf'd the fone and updated to 2.3 ota, can i still root my fone with the z4root? Or do i have to wait for something else?
Sent from my DROIDX using XDA App
Sbf the phone then follow instructions here (video tutorial included)
http://droidmodderx.wordpress.com/l...4-5-596-upgrade-from-froyo-or-gb-588-591-595/
Sent from my DROIDX using XDA App
Is the pre-rooted .596 exactly the same as the OTA .596?
Rocko yes except its not signed
Sent from my DROIDX using XDA App
No one ever reads the first sticky?
I wonder if people are put of by the word "Noob" in the sticky, maybe it should be renamed Everything you need to know about the DROID X.
Everything is explained in there up to Froyo and SBF
firefly2004 said:
I wonder if people are put of by the word "Noob" in the sticky, maybe it should be renamed Everything you need to know about the DROID X.
Everything is explained in there up to Froyo and SBF
Click to expand...
Click to collapse
I sir was not put off by the word NOOB in the thread
That thread has saved my arse dozens of times so far and Im not to proud to say ive it bookmarked and reference it a lot. Thanks a million for that thread
The GB OTA is not rootable.......yet. If you want 596 and root SBF back to 340 and install the pre-rooted 596,or wait for the devs to get it.
Sent from my DROIDX using XDA Premium App
well u finally decided to upgrade to gb using p3s rooted gb i think. i had to sbf back to froyo cause it caused my charging port ti go awol any suggestions? yes i wiped like 4 times including cache and dalvik. but ither than that it looked really nice. and root explorer wouldnt work either...
Sent from my DROIDX using the XDA mobile application powered by Tapatalk
and also my stock recovery blitzd when on gb... did the rec fix. still blitzd. n e suggestions would be grewtly apreciated. would love to go back to gb
Sent from my DROIDX using the XDA mobile application powered by Tapatalk
wow cool no replies ok thx ne way folks. I tried gb again still same issue with root explorer and charging both are still blitzing. at least the stock rec worked this time but whatever... guess no one cares to help me out. well cool n e way. gonna sbf again and just stay on froyo till gb root comes out...
Sent from my DROIDX using the XDA mobile application powered by Tapatalk
Yeah, you have to sbf back to froyo before installing rooted gb.
There is an actual guide somewhere I know, google it - I just saw it like a week ago. In a nutshell:
Make sure you have the right files.
You need leaked rooted gb, all the sbf stuff, droid x bootstrap and droid 2 bootstrap, and I think that is about it.
Root current device build.
Install droid x bootstrap.
Make a back up.
Sbf.
Install droid 2 bootstrap.
Install rooted gb leak .596, I prefer deodexed myself but idk...
Use droid 2 bootstrap to restore.
Remove droid x bootstrap from phone, or at least uninstall. Not compatible with gb.
I don't remember if I had to wipe data or cache or dalvik anywhere, last weekend I tried that new apex but didn't care for it and had to sbf and reinstall to get back to .596 myself, so I feel your pain on that. Had to do it so many times I thought I was going to brick for sure, I just kept trying. Eventually I got it right, on like tuesday.
Good luck.
Ps, idk about the not charging thing, sorry.
DX 2.3.3
yea i got everything set up. multiple times. the only priblems i had were root explorer and charging. other than that everything worked great. i will just wait for the gbbreak. thx though
Sent from my DROIDX using the XDA mobile application powered by Tapatalk
akaruna said:
yea i got everything set up. multiple times. the only priblems i had were root explorer and charging. other than that everything worked great. i will just wait for the gbbreak. thx though
Sent from my DROIDX using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
Might re install busybox, or try a newer root explorer, if you haven't tried those things. Also might wanna try reseting battery stats, but there is a recommended way to do it, saw a post on gizmodo a while back.
Good luck
DX 2.3.3
When the Droid X first came out I rooted and haven't changed a thing since... I am running System Version.2.3.15.MB810.Verizon.en.US with Android Version 2.2 rubiX Focused 0.5
I was thinking that if I did an update, things would run quicker and smoother. Because I am rooted, I am not able to install the OTA to .340... Is starting from scratch the best thing to do in this case? Can I SPB to 2.3.340 if I'm currently running 2.3.15? If I unroot and try the OTA will I brick the phone? I'm not 100% sure where I should begin... Any advice will be greatly appreciated.
If I should have been in a different thread I apologize in advance...
First you should find out your bootloader version, then SBF to 2.3.15, and take the OTA.
Sent from my DROIDX using XDA App
Thanks infazzdar,
The bootloader is 30.01
Finding the right download is tough... any ideas?
It still might be in the TBH app if you bought it.
Wish there was a place that had all SBF files
I didnt...
I have gone cross-eyed looking through all the forums in regards to SBF-ing back to 2.3.15
If anyone could point me the the direction to the file I'm looking for you may be a lifesaver...
joebob296 said:
It still might be in the TBH app if you bought it.
Click to expand...
Click to collapse
Not in the Team Black Hat app.
Sent from my DROIDX using XDA App
I have the 2.3.15 sbf file, but I believe that it is for bootloader version 30.03.
Sent from my DROIDX using XDA App
Found It, but thank you for getting back...
I found the file and sbf to 2.3.15, the did OTA to .340, then did another OTA to 4.5.605... I tried installing the DarkSlide Rom and it turns out I went to far... I prolly should have stuck with .340
My brother's X seemed to be stock on an older VZW firmware so I manually flashed him to the one just before .621, rooted with Pete's tools, used Voodoo to backup root, then flashed the .621 SBF.
Voodoo is reporting that su is backed up but when I hit restore it doesn't work. The app actually says it is restoring but I don't get root -- or an error message.
Thoughts?
Flashing the phone lost your root, Voodoo OTA only works if you take the OTA
****. Well I hope someone figures out how to root the .621, or a way to SBF back to an older version.
We all do buddy!
Actually, if I obtain the temporary root and nuke all the Verizon bloatware, will it stay gone once the phone reboots?
dparm said:
Actually, if I obtain the temporary root and nuke all the Verizon bloatware, will it stay gone once the phone reboots?
Click to expand...
Click to collapse
It should remain deleted.
Sent from my DROIDX using Tapatalk
Has neone gotten close to a root exploit yet?
harveyhungwell said:
Has neone gotten close to a root exploit yet?
Click to expand...
Click to collapse
I haven't heard news of anyone working on an exploit.
Sent from my Transformer TF101 using Tapatalk
Same issue. Hoping for answer here also. Following thread thx
I am actually surprised it has not been rooted yet....thought a week or so would have passed and then we would be good to go....Hope it happens soon.....
KMDonlon said:
I am actually surprised it has not been rooted yet....thought a week or so would have passed and then we would be good to go....Hope it happens soon.....
Click to expand...
Click to collapse
Is there any news of someone working on an exploit?
Sent from my Transformer TF101 using Tapatalk
This is the end in the life of DX. Maybe.......
rren said:
This is the end in the life of DX. Maybe.......
Click to expand...
Click to collapse
Maybe just for those on .621. The Droid X still has plenty of life.
Hopefully an exploit will be released soon.
Sent from my Transformer TF101 using Tapatalk
Got lucky
Sure you've heard all the nightmare stories. Stupid me (twice actually - read on) accepted the OTA a few weeks ago and yes, lost root, didn't have or even know about OTA Rootkeeper. Ended up bricking then SBF'ing to 621 - blah blah blah...
Lost my phone. Had insurance, got phone replaced, installed firmware on replacement .605 - YES! got root, OTA Rootkeeper and backup, restored my full back up of everything via Titanium Backup and am now back to where I was right before the OTA. Have no reason or desire to take 621 again.
One day last week, passed out on sofa, phone starts with non-stop notifications, half asleep, I pick it up and click something to get it to stop making so much noise, pass out again. Wake up a while later, pick up my phone, unlock it to see something like "Update 621 applied successfully" FFFUUUUU!!!!!!!
OTA Rootkeeper definitely saved the day.
New every two coming up in May - WANT Galaxy Journal (note) - will wait for it.
It really is a crushing feeling when the root got lost and there (still) is no method to regain it so I feel for ya. The scariest part about this is that there is no known exploit now, it's been a long while and if this cannot be rooted (out of the box with 621) - it may very well be a sign of the times for MotoRizon which is why I'm bailing.
good luck.
-Sin
I suggest anyone who has SBF'd to 621 or done the OTA and lost root, to check out this thread on RootzWiki. It isn't root for 621, but its a viable workaround. What was found was that an SBF for the milestone X (sbf 604) could be flashed over 621, and then zergrushv4 could be used to root that. Now to do this you MUST use SBF_flash on Linux, otherwise you will flash your baseband and your data will not work (this can be corrected by a call to VZW asking them to reprovision your data). Once on this 604 your phone will report as a Milestone, but you can install BSR/CWM and flash over to a *GB* rom (froyo roms will not work, IIRC) and after that it'll report as DX (this can also be achieved using a build.prop edit, but who really wants stock? If you do just want stock and you do this build.prop edit, you will need to freeze/remove the updater or else it'll freak and try to update and bug you incessantly.) Hope this helps! I've got a dx2 personally but I've been following this thread hoping to glean some information for when our next update drops (which was supposed to happen like a week ago... -__-)