[ROM] Rumm Rx v1.0 - First dose of awesomeness ;)

[Aixelsyd]

So, changing the bootloader...does that mean when Gingerbread comes out it won't be possible to get it?

Well, you can't go back (yet (TBH is "working on it")).
And considering the OTA patches.. are just that, patches.. (they verify you have the correct files, and if you do, then they modify them, not replace them)..

IF the OTA isn't the same as the LEAK, then you can't go forward either (TBH has assured everyone repeatedly that the OTA coming for the DroidX IS indeed the same as 2.3.320 leak).

Only time will tell.. great question though!

Bootloader should have nothing to do with updates moving forward. Team Black Hat has already figured out the bootloader is not what the issue seems to be currently. It is more in depth of an issue then that from what they are seeing as this point and time. And trust me it is being worked on as to what is causing some of these bricks.

What I mean by this is someone who had a brick from last week sent it to one of the TBH guys. He was able to get the 2.3.320 build up and running on it. Once he did he went to an extreme and started messing with the bootloader and was able to still have 2.3.320 running with any of the 3 different bootloaders ( ie 30.01,30.03, and 30.04).

Just give them time and I'm sure they will get it figured out. What I find interesting tho is what is going on. It seems to me like Moto STILL has NOT fixed or figured out the issue as to what bricks a device when being updated. We saw these same type of reports from folks who had a stock X and tried to get the 2.2 OTA update when VZW pushed it out. And low and behold what was reported people stuck on the M or bootlooping after pulling the OTA update and having it install going from 2.1 to 2.2.

 

[TVC430]

I am curious, if TBH can run 2.3.320 on any bootloader, why did they include the 30.04 bootloader in the 2.3.320 update? I don't think they ever included a bootloader in an update before this? I KNOW THEY WARNED US.

Some of us made a choice to wait. I don't think the people who decided to wait expected the Rumm ROM 2.3.15 version to update their bootloader. IMHO

 

[geronimogman]

Im coming from ssx can some please help me with what i need to do? im confused by installing the leak, then apparently i have to root again? then bootstrap..but then do i boot the phone up normally or do i just install jrummy rom while im still in clockwork..but then it says to root again and bootstrap again..plz someone just enlighten me.

 

[Aixelsyd]

I am curious, if TBH can run 2.3.320 on any bootloader, why did they include the 30.04 bootloader in the 2.3.320 update? I don't think they ever included a bootloader in an update before this? I KNOW THEY WARNED US.

Some of us made a choice to wait. I don't think the people who decided to wait expected the Rumm ROM 2.3.15 version to update their bootloader. IMHO

From my understanding it was said by whoever they get there info from the bootloader had to be updated for 2.3.320 to work. Don't quote me on all the specific tho. Anywhoo obviously from there current findings that is not the case tho. They kinda just went out on a limb to see what would happen seeing as the device was bricked already anyways. And with that all said they didn't knwo this until after 2.3.320 was pushed out with the bootloader and a bad device was sent to them to mess with.

 

[MrDizzle]

IM SO STUPID PLEASE HELP! Installed the 2.2.1 updat AFTER I installed the rom. Now I have the 30.04 bootloader but my system is telling me im running 2.3.15. My dialer isn't working and other things are screwy. Im afraid to reflash the rom since there's no sbf for the 30.04 bootloader yet. Please someone smarter than I give me some advise. Thanks in advance

 

[Steady Hawkin]

Im coming from ssx can some please help me with what i need to do? im confused by installing the leak, then apparently i have to root again? then bootstrap..but then do i boot the phone up normally or do i just install jrummy rom while im still in clockwork..but then it says to root again and bootstrap again..plz someone just enlighten me.

I was rooted running APEX V1.0. I downloaded both the leak, and JRummy's Rom first. Then booted into recovery, wiped data and cache first (three times because im paranoid). Installed the leak first from SD, then WITHOUT rebooting after the leak was finished installing I flashed Rummies rom. ZERO issues other than the known glitches with the ROM.

 

[Steady Hawkin]

IM SO STUPID PLEASE HELP! Installed the 2.2.1 updat AFTER I installed the rom. Now I have the 30.04 bootloader but my system is telling me im running 2.3.15. My dialer isn't working and other things are screwy. Im afraid to reflash the rom since there's no sbf for the 30.04 bootloader yet. Please someone smarter than I give me some advise. Thanks in advance

Did you wipe data/cache?

 

[tx3kgtman]

This rom so far has been top notch. Im really impressed with how good this rom is running for the first release. Very fast, 3g hotspot works, battery life is excellent, blur alarm works, transitions look great and smooth, not near as many fc as I used to get. Thanks rummy

Sent from my DROIDX using DroidForums App

 

[thefamousmoe]

JRummy, If I could make a suggestion.

I like your backup/restore options, but here is no progress bar to tell when it is finished. Is there anyway you can incorporate something like that? Thanks a lot! Been using your Rom for a day so far and it is running great.

 

[geronimogman]

but the ssx isnt based off the 2.3 leak its off of the 2.2.1

 

[jrummy16]

couple of questions
i just installed this with no problems what so ever, didn't need a computer or anything

question 1: is there a way to "remap" or change the buttons on the bottom? the browser and dialer (not on adw) ? i miss the contact button from stock blur..it was nicer than going to dialer then contacts and you could also pick between fb, google, and etc.

question 2: is there a way to get back the blur contact widgets? those were really useful.

thanks!

I like both of those.. Think I'll do it for next time

 

[MrDizzle]

Yes wiped, should I try the update leak again?

 

[macdaddybuff]

Quadrant scores on this rom was 1415 stock no oc. That is nice.....
Rom is running excellent. I was having random reboots with tranq and bootup was taking forever. This rom has been running smooth. Bootup is quick again and no reboots. Loving this rom and thanks. Big reason I tried this rom was because I like the OC app Jrummy put out. He really throws in the extras for all who have not tried it I would def flash this.

I do have one question. I went through all the custom bootloaders and when I tried super mario it never worked went to droid eye bootloader after reboot. Dancing droids came up as blank when rebooted. The rest worked great. Anyone else notice this.

 

[sephtin]

Bootloader should have nothing to do with updates moving forward. Team Black Hat has already figured out the bootloader is not what the issue seems to be currently. It is more in depth of an issue then that from what they are seeing as this point and time. And trust me it is being worked on as to what is causing some of these bricks.

What I mean by this is someone who had a brick from last week sent it to one of the TBH guys. He was able to get the 2.3.320 build up and running on it. Once he did he went to an extreme and started messing with the bootloader and was able to still have 2.3.320 running with any of the 3 different bootloaders ( ie 30.01,30.03, and 30.04).

Just give them time and I'm sure they will get it figured out. What I find interesting tho is what is going on. It seems to me like Moto STILL has NOT fixed or figured out the issue as to what bricks a device when being updated. We saw these same type of reports from folks who had a stock X and tried to get the 2.2 OTA update when VZW pushed it out. And low and behold what was reported people stuck on the M or bootlooping after pulling the OTA update and having it install going from 2.1 to 2.2.

From my understanding it was said by whoever they get there info from the bootloader had to be updated for 2.3.320 to work. Don't quote me on all the specific tho. Anywhoo obviously from there current findings that is not the case tho. They kinda just went out on a limb to see what would happen seeing as the device was bricked already anyways. And with that all said they didn't knwo this until after 2.3.320 was pushed out with the bootloader and a bad device was sent to them to mess with.

Links please?

CURRENTLY, the bootloader has EVERYTHING to do with updates. IF/WHEN they have a fix, that's great, then I'll COMPLETELY change my recommendation to people who ask me if they should install the leak!

"And trust me it is being worked on as to what is causing some of these bricks."
Uhmm, ok, I'll trust you. I trust everything I read on the internets. But again, links? Have you seen this working? Is the fix posted and I don't know about it? Or is it once again masses of people, taking the word of someone that "everything will be fine.. see everyone else jumping off the cliff? You can too!"

Sorry if I'm skeptical, and/or paranoid. I see tons of people installing this, and saying "Don't be paranoid!, just do it, these aren't the bricks you're looking for, move along..." But I can't help but to think, that IF VZW comes out with a non 2.3.320 patch, and people are stuck... I might be one of only a few paranoid people who are not returning phones to VZW..

In any case, I'm with everyone else. I hope for the sakes of hundreds if not thousands of people that TBH make good on their assurances...

Love to see links, or better yet, working patches, whatever. When they're available, sign me up for the leak!

EDIT: Bleh, sorry for (again) derailing... not meaning to be off topic.
On Topic: JRummy- Keep up the good work. Regardless of leak or not leak, I'm extremely glad to see another option for ROMs running on the X.

 

[andylulzyou]

Question about the leak, let's say that the next OTA for the DX is this 2.3.320 build or whatever... would I have to .sbf to stock 2.2 and then install the OTA and then reroot or would downloading the leak essentially be the same thing without all that hassle