Hey all, been traveling around the world for a couple months and now that I'm back my poor DroidX needs some ROM lovin =)
I currently have RubiX 1.6, Android 2.2, System Version 2.3.15.
I've been reading and reading all the forums and I'm getting a little confused on what my upgrade path should be. Some have said I can just do the OTA update and it should work, others have said to do an SBF back to 2.2 Vanilla, then OTA, then root and ROM to rubiX 1.90 or whichever I would like.
I dont feel like the OTA would work with mine, but I would love to hear what xda thinks. Im on info overload right now, read too many posts by too many people that dont seem to know wtf they are talking about =)
I believe (someone correct me if I'm wrong...) But if you are running a custom rom, most devs recommend an sbf before updating just to reduce the chance of additional problems when trying to update.
I don't think you can pull the update with your current setup and have it install correctly as rubix has stripped out some bloatware I believe.
I would recommend using the full 2.3.15 sbf and a factory wipe. Be sure to create a nandroid backup before all this and backup any apps/data you would like to save as well
Sent from my DROIDX using XDA App
I'm runng rubix 1.9 on 2.3.15...
Best bet would be to look at the thread for the most recent version (or version you are looking top update to) as the dev well usually include a path for updates... could be wrong, but I feel like this is somewhat common
Sent from my DROIDX using XDA App
Perfect, thanks, just need to search more!
tahoe916 said:
Perfect, thanks, just need to search more!
Click to expand...
Click to collapse
No problem. Just make sure before performing an sbf for 2.3.15 version, that that is tryout actual version and your bootloader version is 30.03
Sent from my DROIDX using XDA App
Related
So currently I'm running on liberty x1.5 and when checking system phone updates, it says it is up to date. I'm sure it's not however since I see news of 2.2 laying around the net if I'm not mistaken. Do I have to revert back to factory to update my phone or how exactly does the process go about. Do I even benefit from the new version if I am running liberty or will liberty have it's own updates... sorry I am new to this whole rom scene and seeking guidance, thanks in advance.
If you put a rom on your phone you won't be able to pull any updates ota... the 2.3.3 update is a leak that tbh put on the net... in order to put it on your phone you need to sbf, and then install the 2.3.3... there are guides on doing this at mydroidworld.com
Sent from my DROIDX using XDA App
jinho11050 said:
So currently I'm running on liberty x1.5 and when checking system phone updates, it says it is up to date. I'm sure it's not however since I see news of 2.2 laying around the net if I'm not mistaken. Do I have to revert back to factory to update my phone or how exactly does the process go about. Do I even benefit from the new version if I am running liberty or will liberty have it's own updates... sorry I am new to this whole rom scene and seeking guidance, thanks in advance.
Click to expand...
Click to collapse
There is no new OTA yet. It's a leak also OTA's won't come to your phone on anything other than stock.
Thank you very Much guys. I don't want to trouble by making a new thread so ill ask here. I tried restoring to factory form from both reboot clockwork and on settings privacy but it just leads me back to liberty rom.
So to make things clear, there is no official 2.2 jslust a leak. Plus would I even benefit from any updates if I'm running a modded rom?
jinho11050 said:
Thank you very Much guys. I don't want to trouble by making a new thread so ill ask here. I tried restoring to factory form from both reboot clockwork and on settings privacy but it just leads me back to liberty rom.
So to make things clear, there is no official 2.2 jslust a leak. Plus would I even benefit from any updates if I'm running a modded rom?
Click to expand...
Click to collapse
Official 2.2 is the version that liberty is based off of. doing a factory reset from within the OS will not take you back to factory stock ROM. Did make a nandroid backup before flashing liberty? if so then you should be able to do a restore and you will have a rooted stock rom. If you didn't make a backup then you will need to SBF (I SBF between roms anyway).
Pretty sure he's just confused with version numbers.
Froyo = 2.2
Gingerbread = 2.3
The only available gingerbread rom at the moment is leaked stock and is version 2.3.3. 2.2 is Froyo and has been officially out now for months, it is what all the custom roms out (liberty, fission, rubix etc) are based off of.
so does this mean im automatically running on 2.2 because im using liberty? if so why does it say 2.1.2 on the about phone in settings? does it matter?
I'd be willing to bet it doesn't say 2.1.2 and it actually says 2.2.1. Am I right?
(To answer your question, yes you are running 2.2 Froyo. There are minor update builds to each major release, hence 2.2.1 and for Gingerbread, 2.3.3).
So I couldnt find a thread that quite answered my question. I have many ideas, but no sure answer, and I dont want a brick.
I have a rooted and Deodexed X on 2.2 that couldnt update to 340 for whatever reason. I want to update to OTA 340 and run the ApeX 141 ROM on that. Should I undo the root and reodex the phone before updating? Can I update it somehow as is and not have a brick? I saw something about doing an SBF, but Im not entirely sure if thats what I do...
Ive been away too long... ha
You could do an sbf, it is not too hard but if you don't know much about it you might as well try to stay away from it. What system version are you on exactly?
If you end up doing an sbf back to stock there are a few videos on youtube that walk you though the process. I watched xdroidroms and it worked perfect for me.
Sent from my DROIDX using XDA App
http://www.youtube.com/watch?v=N0jrXqqiepI&feature=youtube_gdata_player
Video walkthrough
Sent from my DROIDX using XDA App
If you decide to sbf it will automatically put you on 2.3.340. Just download the full version not the system only file. After that z4 to root. Install bootstrap make a backup and flash away. Good luck. Don't worry doing an sbf is not hard. Just read and read some more.
Sent from my DROIDX using XDA App
SoundZombie said:
So I couldnt find a thread that quite answered my question. I have many ideas, but no sure answer, and I dont want a brick.
I have a rooted and Deodexed X on 2.2 that couldnt update to 340 for whatever reason. I want to update to OTA 340 and run the ApeX 141 ROM on that. Should I undo the root and reodex the phone before updating? Can I update it somehow as is and not have a brick? I saw something about doing an SBF, but Im not entirely sure if thats what I do...
Ive been away too long... ha
Click to expand...
Click to collapse
I'm running that now, it's awesome.
2.2.1 rooted apex 1.4.1 honeybread v2
What I ended up doing was the Materstcok method. Seemed to be a lot easier then trying to learn sbf. Unfortunately I ended up having to do an sbf anyway because I tried deodexing for some reason. Haha. It all worked out in the end anyway. Loving the ApeX ROM as well!
Sent from my DROIDX running ApeX using XDA App.
Sbf wasn't as difficult as I thought, I used it to get back to stock in order to be able to flash gingerbread.
Droid X 2.3.3 Rooted
I flashed the 1.83 sbf using rsdlite and then flashed greyblur 2.1 over it, now in the "about phone" section it says I'm running 1.57 and always askes me to update.
Help?
This is happening to me too
Sent from my MB860 using XDA Premium App
Is it the same update pop up that was on stock? I had an update in my notification bar but it did not say what it was or let me cancel it.
It's the OTA 1.83 update for users that are on 1.57, but i already upgraded
Yeah this happened to me too. I was rooted on 1.57 and updated. Ran afterupdate and got root back. Than I installed GreyBlur and im back to 1.57 now.. :-/
Sent from my MB860 using XDA App
Its because greyblur isn't compatible with 83 yet. A lot of psuedo roms make changes to /system, and that include their own build.prop file. That makes it look to the phone that its on 57 and not on 83. Wait until greyblur gets updated or dive into the zip yourself and make your own changes.
Sent from my screaming Atrix *4G* using the XDA App
I'm really having a hard time here with this. This is my first custom rom I've installed. If I should wait for 83 compatibility. How do I uninstall the rom? If I accept the OTA update will it uninstall the rom for me?
Should I settle with GingerBlur instead? I really hate sounding like a newb here, but I've been digging deep into the forums and not really finding a clear answer about this issue.
ZombieChris said:
I'm really having a hard time here with this. This is my first custom rom I've installed. If I should wait for 83 compatibility. How do I uninstall the rom? If I accept the OTA update will it uninstall the rom for me?
Should I settle with GingerBlur instead? I really hate sounding like a newb here, but I've been digging deep into the forums and not really finding a clear answer about this issue.
Click to expand...
Click to collapse
Did you make a backup in Tenfar's recovery before you installed the rom? If so, its a simple process of restoreing the backup. If not, I personally would flash using the sbf available to whatever version. That basically will just reinstall your system, but keep your data (I.e. music not apps). I don't know what will happen if you update on greyblur... maybe try it? You could fall back on using the sbfs if needed. Gingerblur is great, although there are mixed repotlrts on bad batterylife with it. I'm personally on stock with LauncherPro until the next gladiatrix comes out.
Its good that you are asking questions before doing things.
Oh, P.S. you could use titanium backup to backup your apps.
Sent from my screaming Atrix *4G* using the XDA App
Actually I think this more to do with the fact that GreyBlurr came out when 1.57 was the current firmware version. It has that listed in the build.prop file. So the phone thinks it is 1.57 even though it is really 1.83. If you have root explorer you can safely edit that file to show the correct version (its the top line).
If you don't want to do that and you have Titanium Backup, you can freeze the Updater app.
Thanks for the advice Tyler.
I ended up flashing back to 1.26 and just rerooting again with GladRoot.
I now have GingerBlur installed and am very pleased with the results. =)
I've only had this phone for a weeks and it's my first droid, so I'm definitely learning a lot.
ZombieChris said:
Thanks for the advice Tyler.
I ended up flashing back to 1.26 and just rerooting again with GladRoot.
I now have GingerBlur installed and am very pleased with the results. =)
I've only had this phone for a weeks and it's my first droid, so I'm definitely learning a lot.
Click to expand...
Click to collapse
I'm glad you found something that works, and I'm glad to help anytime
Sent from my screaming Atrix *4G* using the XDA App
Ok, I know I have been really slacking with updating my phone. I'm still running the first rooted version that came out after the phone was released. I'm just getting back into tinkering with my phone and want to check out gingerbread 595.
With that said, I'm looking to find out if I need to sbf or flash (I can do either, I'm competent in both) any versions previous to 2.3.320 before I flash to 2.3.340 and then 595? I've been scouring all of the Android forums for the past week and I can't find out if I can flash directly to .320 from .9... can anyone help me out?
Sent from my DROIDX using XDA Premium App
a google search away from your answer
hxxp://androidforums.com/droid-x-all-things-root/289640-getting-rid-2-3-9-leak.html
I'll feed you baby bird...
edit:
Oh.. yeah I went with the leak and ended up having to sbf back to previous stock at the time. Then went and OTA'ed... from there you can start over and look into the GB. Although a word of caution, from what I read, going to GB now you might regret. Seems like you try GB and then end up wanting to go back to froyo and have all sorts of issues. You will be in the same position... I will wait... pretty satisfied with my Liberty 2.0.1!
Look for maderstock.340 update.zip
That will get you into froyo.340
Find and flash gingerbread.588
Then your good to go straight to .595
The only issue with GB is the free tethering is for the moment, dead.
Stock GB is as fast or faster than any custom froyo I have ever flashed. And I actually prefer the new blur to AOSP.
Go with gb, you wont be disappointed.
Sent from my DROIDX using XDA App
My question is why wouldn't you just install a ROM like Liberty and let them get you the most recent Android version?
twobadfish said:
My question is why wouldn't you just install a ROM like Liberty and let them get you the most recent Android version?
Click to expand...
Click to collapse
Because as they said they are on an older version and haven't been keeping it up to date. They may have just been satisfied with how things were on their system version
I am thinking about getting a Droid X this afternoon. With the OTA update is it rootable and if so with what? Thank!
floridatank said:
I am thinking about getting a Droid X this afternoon. With the OTA update is it rootable and if so with what? Thank!
Click to expand...
Click to collapse
Not the OTA. You will need to sbf back to froyo and then upgrade to the pre rooted GB
Sent from my DROIDX using XDA App
bigshotrob22 said:
Not the OTA. You will need to sbf back to froyo and then upgrade to the pre rooted GB
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
I went ahead and got it. It has 2.3.3 on it, Will Gingerbreak work on that? Thanks!
floridatank said:
I went ahead and got it. It has 2.3.3 on it, Will Gingerbreak work on that? Thanks!
Click to expand...
Click to collapse
Nope! Like I said its unrootable
Sent from my DROIDX using XDA App
Unrootable...
But that doesn't mean you can't root.
SBF to froyo.
Flash the 2-part gingerbread .zips.
Flash a custom rom (Liberty?)
Or stay on the froyo kernel...
and try MIUI or Cyanogen.
Be careful and read as much as you possibly can before starting. Myself and at least one other on here with the latest iteration of the X have ended up with boot looping or totally non-responsive devices.
I have started a thread with my findings. I am by no means an expert but I do have much experience with rooting devices going all the way back to the PPC6700.
Good luck.
getting stuck in a bootloop is part of the exploration process IMHO.
At least once per new ROM I'll flash something 'just to see what happens' and end up SBF'ing back. Just make backups between steps if you aren't sure about what will happen next.
it would be nice if one of the devs or people who work on rooting or someone in the know would at least comment if we are going to get a real root with the OTA
i mean im running froyo with CM7 but i sure would like the new firmwares for all the radios flashed and then be running CM7
so if someone could give us some kind of update at least saying no one is even remotely working on trying to gain root on 4.5.596 Official OTA or that yea we are working on it but it is a ***** and taken longer then we expected
that lil bit of info goes a long ways
thanks
I am not aware of any dev working on this ATM.
I don't think rooting 596 ota is critical 2nd unit has opened up alot of new doors and the attention has shifted. However I have flashed all of drew gardens latest and ran cm4dx until nightly 47. Now I'm daily MIUI and loving it, despite locked bootloader the cdma_shadow still has alot of options.
Sent from my DROIDX using XDA Premium App
to my understanding .596 has better battery life and signals are better for wifi and cellular (at least more stable and less drops)
i do not know if this is true but i have read/heard alot of ppl saying the battery life is better on .596
after all there is a .596 for some reason and its not a lil bump from 2.2.340 its pretty big
anyhow someone really needs to figure this out as the baseband has changed....i mean there is the pre-rooted rom .596 that works great so we know it can be done.
whats the big deal...let us have it
m16-maniac said:
anyhow someone really needs to figure this out as the baseband has changed....i mean there is the pre-rooted rom .596 that works great so we know it can be done.
whats the big deal...let us have it
Click to expand...
Click to collapse
the big deal is that there isn't a readily found exploit for the ota, the pre-rooted was done with a diff. method (brute force? recompiled?) but the versions are the same regardless
no ones holding back a secret root method, there just isn't a dev interested in spending huge amounts of time to recreate what already exists
i think it would be interesting to create a batch script that sbf's a phone and installs the pre-rooted .596 but all hidden behind a random animation so the user doesn't see what's happening. if i call it a 'one click' root method lots of people who don't seem to want to take the readily available pre-rooted gb for whatever reason would likely be happy. yeah i understand that if it includes a sbf then data may get lost, but if i said in the instructions of my 'app' that it would happen and they should have backups, people would still likely use it
sorry, but i just don't understand why so many people who want root are seemingly against using the pre-rooted option, as most of them don't have the knowledge to find an exploit or a root method from scratch themselves, so they are still using the work of someone else...
<Disclaimer>I'm going out on a limb here with limited knowledge of the X. <End disclaimer>
From what I read and I don't remember where, the rooting of an X involves a 2nd init method by which it takes control of the initial init. I believe I read the original init isn't able to be exploited and this is the basis of some of the more complicated methods of rooting the X.
If someone knows more about this please correct me or chime in.
I had an Incredible prior. The rooting was more comprehensive and simple. I believe that is because the bootstrap and recovery were not as difficult to get into. That being said, personally, I may be going back to another HTC device if the folks light years smarter than me aren't interested in developing a root method like the other devices out there.