.15 to .340 back to .15,why?

mich1248

Active member
Nov 22, 2009
35
0
0
i was running rubix 1.9 off of system version 2.3.15..i wanted to try fabulous new rom but i needed a new system version to do so..so the easiest way i knew how was to flash back to stock using a sbf file with rsd lite,install the new ota update of .340,reroot my phone then install apex...so all that worked..liked the rom but not running to stable on my phone,so i installed the zip for rubix 1.9 back on my phone and it downgraded the system version back to .15..any ideas why this happened?thanks
 
It didn't change your system. I can edit the file to say 5.0 if I wanted to. Don't worry.
 
Thats because rubix is a .15 rom I think. It was unstable because something got jacked the way u did it. Following the directions bellow will take u directlly to .320. Then install apex 1.3 from rom manager. Easy 2 steps. Takes like 15 minutes or so.

DROID X 2.2.1 Leaks, Updates System to 2.3.20 - Droid Life: A Droid Community Blog

If you did a nandroid backup of 2.3.340 try restoring from backup and then reinstall the OTA version to be sure all is restored from http://forum.androidcentral.com/mot...wnload-official-droid-x-2-3-340-ota-here.html and then install DarkSlide v4 Blur ROM from [ROM] DarkSlide v4
 
He just wanted to know why it went back to .15. The other roms build props state .15 as the build so that's why it went back but it really didn't go back it just looks that way. Install apex 1.3 and it will go back to .340. Restore the stock .340 that you should have made and it will show back at 340 again.

Sent from my DROIDX using Tapatalk
 
ok so i'm running the apex 1.0.2.2 or whatever it was (phone rebooting, don't wanna wait to look) for those of us who still were on the .15. i tried to do the ota update from verizon to get to .340 but everytime it d'l and reboots, my phone just says update failed. i've also tried d'l onto my laptop then moving to the root, blah, blah, blah and with this method it didn't work. i've also tried formatting the cache and data and it ends in failure as well. is my only solution to go back to stock 2.1 the update to 2.2 to get the .340? i'm really wanting to give the new apex 1.3 a go but i'm at a crossroads and don't know what to do =(
 

Trending Posts

Forum statistics

Threads
956,740
Messages
6,969,711
Members
3,163,603
Latest member
blåhaj