DroidForums.net | Android Forum & News
This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
[ROM] Rumm Rx v1.0 - First dose of awesomeness ;)
- Thread starter jrummy16
- Start date
CletusVanDam
Member
Rumm Rx messed up my DX 
So I was running Rubix 1.9.0 (on 2.3.320 update)on my girlfriend's Droidx. It worked fine, but I loved the Kangerade series so much from jrummy, that I had to try this ROM out. This is basically what happened:
ME: "Awesome Jrummy released a ROM for just for my Droid X!" LOL!!! :icon_ banana:
::Ti backup, Nandroid Backup, wipes data and cache, begins installing Rumm Rx::
DROID X: "mmm...hey boy, you gotta purdy face"
The phone booted up once and ran incredibly slow, every background service/app force closed constantly. I thought, "it must just be setting up caches and downloading crap." I waited about an hour (watched The Walking Dead on AMC, totally awesome series btw) and pulled the battery. At this point the phone went into an endless boot loop for about 15 minutes. So I pulled the battery again, held volume up and home key to go into recovery. Got into recovery after two tries and wiped data. Rebooted the phone and it finally came up. I proceeded to restore all the apps and settings.
This is when I started to notice a lot of problems. While testing the camera, it would either force close or just sit at the camera still-shot screen without ever saving the pictures. This is a major problem for my girlfriend, so I decided to just nandroid back to the backup I had made earlier. Wiped and restored to Rubix in about 10-minutes, everything looked fine. Then I tested the camera, it wouldn't save either, just like in Rumm Rx! At this point it's past midnight, so I located the latest SBF and just flashed it back to stock. All problems solved.
I'll still re-root the phone (since I lost root in the SBF) and load up a custom ROM, but I'm afraid to load up Rumm Rx again. Anyone have a similar problem?
So I was running Rubix 1.9.0 (on 2.3.320 update)on my girlfriend's Droidx. It worked fine, but I loved the Kangerade series so much from jrummy, that I had to try this ROM out. This is basically what happened:
ME: "Awesome Jrummy released a ROM for just for my Droid X!" LOL!!! :icon_ banana:
::Ti backup, Nandroid Backup, wipes data and cache, begins installing Rumm Rx::
DROID X: "mmm...hey boy, you gotta purdy face"
The phone booted up once and ran incredibly slow, every background service/app force closed constantly. I thought, "it must just be setting up caches and downloading crap." I waited about an hour (watched The Walking Dead on AMC, totally awesome series btw) and pulled the battery. At this point the phone went into an endless boot loop for about 15 minutes. So I pulled the battery again, held volume up and home key to go into recovery. Got into recovery after two tries and wiped data. Rebooted the phone and it finally came up. I proceeded to restore all the apps and settings.
This is when I started to notice a lot of problems. While testing the camera, it would either force close or just sit at the camera still-shot screen without ever saving the pictures. This is a major problem for my girlfriend, so I decided to just nandroid back to the backup I had made earlier. Wiped and restored to Rubix in about 10-minutes, everything looked fine. Then I tested the camera, it wouldn't save either, just like in Rumm Rx! At this point it's past midnight, so I located the latest SBF and just flashed it back to stock. All problems solved.
I'll still re-root the phone (since I lost root in the SBF) and load up a custom ROM, but I'm afraid to load up Rumm Rx again. Anyone have a similar problem?
CletusVanDam
Member
Yea, I actually installed it twice and tried restoring to my nandroid backup. Somehow the error carried over to that too, even after wiping between the restore. After the SBF, everything worked fine again. I'm running 2.3.320 leak right now, I'll probably root it tonight and re-install Rubix. I'm going to wait until the Facebook sync, Calendar FC's, and Camera issues get sorted out.
Themes from Apex work with this rom
Which one are you using?
Are there any other themes that work well with rumm rx?
Can someone tell me how to disable (if possible) the "google account re-download every app you had automatically to your phone after signing in option of doom"
Would like to start from scratch and add apps manually. I'm getting some freezing and random reboots. Did everything from ROM Manager (wipe n cache)
Thanks!
Would like to start from scratch and add apps manually. I'm getting some freezing and random reboots. Did everything from ROM Manager (wipe n cache)
Thanks!
Themes from Apex work with this rom
Which one are you using?
Are there any other themes that work well with rumm rx?
Currently using revolution and about other themes not that I know of yet
hoodboogie
New Member
So did medium use today. From 0500 to 2250 was off charger. Stock clocks too.
Maybe 150 txts, 5min of youtube, 10 min browsing, 10 min of pocket legends and at 70% battery. No reboots either.
Great job!
Sent from my DROIDX using DroidForums App
Maybe 150 txts, 5min of youtube, 10 min browsing, 10 min of pocket legends and at 70% battery. No reboots either.
Great job!
Sent from my DROIDX using DroidForums App
Thanks, did that. Then when I reloaded rumm, I skipped the google account setup and went back into privacy to uncheck them again.
When finally starting the google setup, I unchecked 'back up data' (i think that's what it said)
Anyway.. no automatic download of doom and after almost 24 hours, no problems with reboots/freezing.
Market still remembered what apps purchased and they were waiting for me to download again manually.
Probably shouldn't go here, but...
FYI... those concerned about the leak, IF the next OTA from VZW isn't the same thing as the 2.3.320 leak... then there are going to be lots of very unhappy people stuck on the leak.
Reasoning: The OTA is a patch. It doesn't replace files, it patches them... so if you go to the leak you will not be able to OTA even with a .sbf, because the OTA will be looking to patch 2.3.15 files, not 2.3.320 files. Until TBH releases a method to go back, those now on the leak will be stuck if the OTA isn't exactly the same.
NOTE: TBH has assured everyone repeatedly that the next OTA from VZW WILL CERTAINLY be 2.3.320
NOTE2: TBH has also stated that they have a work in progress, that MAY be able to revert people on 2.3.320 back to 2.3.15. (Assuming they get permission to release it (??))
Now, I'm sure I'll get flamed by the leaklovers for this, BUT, I still believe that information/knowledge is a GOOD thing, so I'm posting so that anyone on the fence knows that there are still risks, even with a full .sbf
I would NEVER take anything away from TBH/P3/CW/etc. Awesome work leaking the leak! And they DO put tons of time and effort into bringing everyone the latest and greatest stuff!
(I'm sorry if any hands were bitten by this post...
I believe you have misrepresented us, never have we said that this is the next official, as that information is unknown.
But no one will be stuck without the abiity to be on the official firmware, that is what has been said. That may or may not include a way back to take the official update zip. Having said that I reiterate that NOONE will be stuck at 2.3.320, unless they chose to, and everyone who has taken this update will be able to (through some method) upgrade or move to the offical firmware version released by Verizon.
Who is CW and etc? There is only one group responsible for all the X goodness and that is TBH, I am a part of TBH so no need to thank me twice, even though I do enjoy being thanked twice. HeHe.
The next OTA will be 2.3.340
Breaking: DROID X Update to 2.3.340 Coming, Madden 2011 to be Pre-installed (Updated) - Droid Life: A Droid Community Blog
Probably shouldn't go here, but...
FYI... those concerned about the leak, IF the next OTA from VZW isn't the same thing as the 2.3.320 leak... then there are going to be lots of very unhappy people stuck on the leak.
Reasoning: The OTA is a patch. It doesn't replace files, it patches them... so if you go to the leak you will not be able to OTA even with a .sbf, because the OTA will be looking to patch 2.3.15 files, not 2.3.320 files. Until TBH releases a method to go back, those now on the leak will be stuck if the OTA isn't exactly the same.
NOTE: TBH has assured everyone repeatedly that the next OTA from VZW WILL CERTAINLY be 2.3.320
NOTE2: TBH has also stated that they have a work in progress, that MAY be able to revert people on 2.3.320 back to 2.3.15. (Assuming they get permission to release it (??))
Now, I'm sure I'll get flamed by the leaklovers for this, BUT, I still believe that information/knowledge is a GOOD thing, so I'm posting so that anyone on the fence knows that there are still risks, even with a full .sbf
I would NEVER take anything away from TBH/P3/CW/etc. Awesome work leaking the leak! And they DO put tons of time and effort into bringing everyone the latest and greatest stuff!
(I'm sorry if any hands were bitten by this post...
I believe you have misrepresented us, never have we said that this is the next official, as that information is unknown.
But no one will be stuck without the abiity to be on the official firmware, that is what has been said. That may or may not include a way back to take the official update zip. Having said that I reiterate that NOONE will be stuck at 2.3.320, unless they chose to, and everyone who has taken this update will be able to (through some method) upgrade or move to the offical firmware version released by Verizon.
Who is CW and etc? There is only one group responsible for all the X goodness and that is TBH, I am a part of TBH so no need to thank me twice, even though I do enjoy being thanked twice. HeHe.
The next OTA will be 2.3.340
Breaking: DROID X Update to 2.3.340 Coming, Madden 2011 to be Pre-installed (Updated) - Droid Life: A Droid Community Blog
Yep, and if anyone is running TranQ 3.5.1 they already have the .340 build
This happens to me as well I have handcent too but I heard this was a froyo problem?