rubiX Focused 1.9.5

[Johnnysyeah]

I think I might purchase the extended battery too.
The only issues I have are:
Would I need to buy a different back cover?
And would I not be able to use my current casing anymore?

 

[rkrasny]

I think I might purchase the extended battery too.
The only issues I have are:
Would I need to buy a different back cover?
And would I not be able to use my current casing anymore?

The extended battery comes with a new battery door that is 1-2 mm thicker (or protrudes that amount). It fits into most cases and visually is similar but not identical. Some people have put the original battery door back with the extended battery in (snug fit) but I don't recommend it (personal experience with overheating and screen blotches). If you post what case you have I'm guessing someone else with an extended battery can tell you if it works. I'm using the Seidio case and its fine.

 

[Johnnysyeah]

I have a pretty cheap casing; when I bought the phone, the guy gave me the case for free.
So I just kept using it.
I don't even know what it's called.

 

[E Mad]

ROM Manager OTA Support

Hi,

I've been using RubiX since 1.6 and have loved it ever since. One of my only issues is the fact that there is no support for OTA updates, so I never know when the updates are ready until I check the forums here. Can you enable OTA updates in ROM manager for us?

Also, a word of advice for people who want the new RubiX 1.95, but are stuck on system version 2.3.15: flash .20, but don't flash .40. I've seen a few people (including myself) who have bricked their phones by doing this. It turns your phone from dancedroid into :motdroidvert: ... But if you play dumb with Verizon, you'll get a refurbished DX overnighted to you. But then again, with the new phone, you can flash the new version of RubiX without a problem. And then you can go back to being this :icon_ banana:

 

[rkrasny]

I have a recurrence of a fairly awful problem that I must be alone in experiencing. I posted a while back about my DX having a bootloader error after 1.95 and trying to nandroid backup. I went to VZW and they had no clue and didn't have the capability or intelligence to reflash the software so I received a refurb unit by mail yesterday.

The new unit was already on .340/2.2.1 so I rooted with z4root, loaded clockwork, loaded Rubix 1.95 and then restored most of my stuff via google and mybackup pro (just apks and data, no system).

Everything was fine until this morning when I went back to clockwork and re-bootstrapped recovery (I always do this before I go into clockwork recovery or ROM manager), and had clockworkmod reboot into recovery. I am now back stuck at the M logo. However, this time I can get into the normal recovery mood (Home/Power/Search etc.) In the normal recovery I tried a cache clear with a reboot - nothing; then I tried a wipe data/factory reset with a reboot - still stuck at the M logo.

I am guessing I have to SBF but I am now unsure what files to use for the SBF - I think there are .340 system only files somewhere and I am praying that will work. Does anyone know where those SBF files are and whether they might work or have any other suggestions??

Clearly there is some reproducible corruption of the bootloader (?) with the Clockworkmod recovery bootstrap that I have now unfortunately duplicated on two different DXs but I am guessing I am the only one experiencing this since nobody could even flash a theme after the ROM without going into recovery...

First time I've heard of someone having such problems, let alone repeated... :S And I have to say, I track probably 6 different DroidX Forum sites pretty regularly...

Well I have some more info (they really have no options at the VZW store except a replcement - neither of the two stores I went to had a clue how to reload software). I was able to SBF from a different computer with the moto drivers already installed. I used the .340 system only SBF and the phone seems fine.

Because I'm curious about the problem I then re-rooted with z4root, reinstalled bootstrap and reloaded the same Rubix 1.95 non-themed version. I then went back to the market, re-downloaded clockwork and rebooted into clockwork recovery and it was fine. I installed one of the themes to be sure.

At this point I am left with some difficult options for troubleshooting. I've been using Mybackup pro for restoring apps and data (no system info) although I have complete TiBUps as well. I don't know if something in my restoring is causing a problem or if I have a very bizarre app conflict (I have maybe 200 apps but pretty benign stuff). I'm also wondering if a Mybackup restore of the bootstrapper is causing some conflict???

If anyone has some troubleshooting thoughts I'd be happy to try; otherwise I seem to be alone with this bizarre problem and since it has occurred on two phones I'm sure it is somehow software related.

Thanks for everyone's help, especially Seph (it took you almost two hours to respond - I almost called 911 for you - lol).

 

[drod2169]

Hi,

I've been using RubiX since 1.6 and have loved it ever since. One of my only issues is the fact that there is no support for OTA updates, so I never know when the updates are ready until I check the forums here. Can you enable OTA updates in ROM manager for us?

Also, a word of advice for people who want the new RubiX 1.95, but are stuck on system version 2.3.15: flash .20, but don't flash .40. I've seen a few people (including myself) who have bricked their phones by doing this. It turns your phone from dancedroid into :motdroidvert: ... But if you play dumb with Verizon, you'll get a refurbished DX overnighted to you. But then again, with the new phone, you can flash the new version of RubiX without a problem. And then you can go back to being this :icon_ banana:

That's called fraud... and another reason our phones are continuously being locked down.

OTA Updates will be done in the future. I'm trying to enable a way to let you guys know directly, not through rom manager.

 

[sephtin]

Hi,

I've been using RubiX since 1.6 and have loved it ever since. One of my only issues is the fact that there is no support for OTA updates, so I never know when the updates are ready until I check the forums here. Can you enable OTA updates in ROM manager for us?

No. NO custom ROM will ever enable OTA's. The OTA is a PATCH, it requires that all files be unaltered (which is exactly what you're doing when you load a custom ROM.

So, this is NEVER going to happen, for ANY ROM.

Also, a word of advice for people who want the new RubiX 1.95, but are stuck on system version 2.3.15: flash .20, but don't flash .40. I've seen a few people (including myself) who have bricked their phones by doing this. It turns your phone from dancedroid into :motdroidvert: ... But if you play dumb with Verizon, you'll get a refurbished DX overnighted to you. But then again, with the new phone, you can flash the new version of RubiX without a problem. And

The best way to upgrade, is to .sbf back to 2.3.15 cleanly using the 2.2 .sbf file (the_gift2)... works 100% of the time if you do it correctly, and the OTA will install should never fail from clean install of 2.3.15. (Since the OTA is a patch, if the correct versions of every file it patches aren't the right version, the OTA fails.. since the .sbf puts back all of the correct versions... it will work.

With the DroidX, there is pretty much NEVER a situation where a software problem should require sending a phone back to VZW...

 

[Sweettreat]

I had to sbf today for the first time, now I'm on system version 2.3.320, and phone keeps saying no updates available ( trying to get back on .340). Wtf, over? Can I install Rubix1.9.5 over.320 or no? Help.

 

[Droid74]

Hi,

I've been using RubiX since 1.6 and have loved it ever since. One of my only issues is the fact that there is no support for OTA updates, so I never know when the updates are ready until I check the forums here. Can you enable OTA updates in ROM manager for us?

Also, a word of advice for people who want the new RubiX 1.95, but are stuck on system version 2.3.15: flash .20, but don't flash .40. I've seen a few people (including myself) who have bricked their phones by doing this. It turns your phone from dancedroid into :motdroidvert: ... But if you play dumb with Verizon, you'll get a refurbished DX overnighted to you. But then again, with the new phone, you can flash the new version of RubiX without a problem. And then you can go back to being this :icon_ banana:

This is the dumbest thing i have read in awhile.....

 

[drod2169]

Also, a word of advice for people who want the new RubiX 1.95, but are stuck on system version 2.3.15: flash .20, but don't flash .40. I've seen a few people (including myself) who have bricked their phones by doing this. It turns your phone from dancedroid into :motdroidvert: ... But if you play dumb with Verizon, you'll get a refurbished DX overnighted to you. But then again, with the new phone, you can flash the new version of RubiX without a problem. And

The best way to upgrade, is to .sbf back to 2.3.15 cleanly using the 2.2 .sbf file (the_gift2)... works 100% of the time if you do it correctly, and the OTA will install should never fail from clean install of 2.3.15. (Since the OTA is a patch, if the correct versions of every file it patches aren't the right version, the OTA fails.. since the .sbf puts back all of the correct versions... it will work.

With the DroidX, there is pretty much NEVER a situation where a software problem should require sending a phone back to VZW...

THIS! +1,000,000,000
If there is any chance of no more locked bootloaders.. its by not stealing from the companies.

As rude as it may sound, please please please research before rooting and modding your phone.

 

[teh_g]

I had to sbf today for the first time, now I'm on system version 2.3.320, and phone keeps saying no updates available ( trying to get back on .340). Wtf, over? Can I install Rubix1.9.5 over.320 or no? Help.

There are no OTA updates from .320 to .340. You need to go to TBH and find the info for how to upgrade from them.

THIS! +1,000,000,000
If there is any chance of no more locked bootloaders.. its by not stealing from the companies.

As rude as it may sound, please please please research before rooting and modding your phone.

It isn't rude at all. People shouldn't be playing with this kind of stuff on their phones without understanding more. I also dream of a day where I can get a quality phone like the DX and not have a locked bootloader.

 

[ashah87]

So one thing that I have noticed is that when I choose an image from a gallery to set as a wallpaper, it is not sharp at all. This is comparison to the exact same wallpaper I used in 1.9.0. Is anyone else seeing this problem/know of a fix?

Thanks in advance...I don't know where I would be without people out there like you.

 

[sephtin]

I had to sbf today for the first time, now I'm on system version 2.3.320, and phone keeps saying no updates available ( trying to get back on .340). Wtf, over? Can I install Rubix1.9.5 over.320 or no? Help.

You can. To udpate to 2.3.340, there are patches here:
TBH Patches: 2.3.340-System, Baseband, 2.3.340-Kernel, Bootloader

Just install the kernel/baseband/bootloader scripts, you do NOT need the SYSTEM patch, as you'll be replacing system with a ROM!

HTH!

 

[ashah87]

So one thing that I have noticed is that when I choose an image from a gallery to set as a wallpaper, it is not sharp at all. This is comparison to the exact same wallpaper I used in 1.9.0. Is anyone else seeing this problem/know of a fix?

Thanks in advance...I don't know where I would be without people out there like you.

So I continued to play around with my phone and noticed that an image that you download from the web browser on the phone will be grainy but if you download that same picture from your computer and put it on your phone it will look perfectly fine.

 

[teh_g]

So I continued to play around with my phone and noticed that an image that you download from the web browser on the phone will be grainy but if you download that same picture from your computer and put it on your phone it will look perfectly fine.

I bet that depending on which browser you use, you may be saving the lower quality version that the browser makes for you. To be clearer, if a picture is 1280*1024, it won't display great at full resolution on the phone's screen. Perhaps the browser decides to resize it down to 640*512. When you save it, maybe it is saving the smaller resized version, but the file itself is still under the impression that it should be displayed at 1280*1024. This will then cause the file to look grainy and ugly, since the image is being blown up.