Difference between 2.3.20 & 2.3.320?


Last Updated:

  1. budmonster

    budmonster Guest This Topic's Starter

    My DX came with Android 2.2 v2.3.15. I flashed my first ROM, the rubiX Blurry 1.5.2 and when I checked my settings it said I was on Android 2.2 v2.3.15. Yesterday I flashed this rubiX Blurry 1.6.3 ANDROID DOES EXCLUSIVE and now it says I'm on Android 2.2.1 v2.3.20. How is that possible, I never flashed the new SBF leak file?

    Is there a difference between 2.3.20 & 2.3.320? Or did he just edit the build.prop and rename the os and build #?

    This is getting confusing for myself and a bunch of other users that I know, any help would be appreciated!

    Thanks -BUD
     

    Advertisement
  2. RoOoLeR

    RoOoLeR Active Member

    Joined:
    Nov 26, 2010
    Messages:
    31
    Likes Received:
    99
    I also am in sort of a Bind here hopefully someone can help us out??

    I was on 2.1 and updated Via the LEAKED 2.2 from there i now have Rubix Focused 1.8.6 on my phone.. says i am on Android 2.2.1 Version = 2.3.20

    i want to run Fabolous Apex New Rom but it says it should be ran on either the New LEAKED 2.3.320 or else 2.3.15 Well what am i on??
     
  3. bladebarrier

    bladebarrier Well-Known Member

    Joined:
    Jul 1, 2010
    Messages:
    75
    Likes Received:
    20
    Please correct me if I'm wrong here.

    Some of the ROMs went over to leaked software, some went a step further and require the new boot/kernel.

    The first type replaces the system data, and is based on a develepor release. I believe Fission initially went this route, which would explain why Rubix is similar. The ROM only updated your software, and did not update the boot/kernel (which is ok).

    Some of the ROMs are now going to require the updated boot/kernel, which means they expect you to upgrade fully, before loading the ROM.

    This also happened in Fission/RubiX, because they used parts of the D2 release to create the ROM.

    You can determine what bootloader/kernel you're on in the system info, but the build number is really just whatever the dev typed in.

    The same confusion happened when Froyo was released. Some people upgraded OTA, and in doing so upgraded their boot/kernel, and some people just used the leaks to upgrade the system data. At that point in time, you generally could run any Froyo ROM without upgrading the boot/kernel, or run the same ROM if you did. If you used a full SBF, however, you had to make sure you didn't try to downgrade the boot/kernel, or you would brick it.

    It seems that a split may be happening, where some ROMs will require a complete update, and some will not.

    Basically, you need to read the full instructions of the Dev that made the ROM to be sure, and if you aren't sure about what to do, wait until a full SBF for the new leak is available.

    /Better to be safe, than brick.

    //If you're happy enough with what you have running, just hang in there, until a proper SBF is released. Until then, enjoy your smartphone. It's not as if the screen will get any larger by updating to something you aren't sure about. Fission is running great for me. RubiX blurry is a great ROM, and there are versions that don't require updating the boot/kernel. ApeX has great reviews, and ran very well for me. Tranquility 3.0 runs just fine. SSX ran great for me. There are tons to pick from, without the need to update without needing the new kernel/bootloader.

    ///I really want to try Jrummy's ROM, and Darkslide, but I'm going to hold off for a proper SBF to be released.
     
    GrandMasterB likes this.
  4. cashX3r0

    cashX3r0 Well-Known Member

    Joined:
    Apr 24, 2010
    Messages:
    137
    Likes Received:
    10
    same here. im going to make an educated guess: i didnt flash teh 2.3.320 leak, and my sys info says 2.3.20. and i remember flashing 2.3.15. went from apex to fission to rubix. i figure i'm still on 2.3.15. now heading back to updated apex v1.02.2(fab's 2.3.15 release). cheers.
     
  5. javroch

    javroch Well-Known Member

    Joined:
    Aug 7, 2010
    Messages:
    85
    Likes Received:
    46
    DEVs can put whatever they want in build.prop and that'll show up on your "About Phone" screen. If you applied the sbf, you have 320. If you didn't, you have 15. 20 was never even a release for the DX, that's a version for the D2. I'm assuming drod did this to make the phone work with one or more applications that didn't work nicely before. I wouldn't be alarmed.
     
  6. digdug1

    digdug1 Well-Known Member

    Joined:
    Apr 27, 2010
    Messages:
    1,965
    Likes Received:
    309

    holy crap! i am not new to rooting but this is VERY confusing to me! i got my x yesterday rooted it today and have no idea wether i should upgrade to the newest build or not. since my x came with 2.2 should i sbf before hand?
     
  7. javroch

    javroch Well-Known Member

    Joined:
    Aug 7, 2010
    Messages:
    85
    Likes Received:
    46
    As well, for the most part at least, a ROM won't push the leak for you. You'd have to push it yourself and the install the ROM over it. So, if you never installed the leak yourself, that's a good indication that you're not actually on the leak. Like I said though, .20 was never a build for the DX in the first place, that's a D2 build number simply edited into build.prop probably to make the phone play nicely with one or more apk's. I've seen ROM dev's do this to get the Market working properly for example.
     
  8. colchiro

    colchiro Well-Known Member

    Joined:
    Jun 4, 2010
    Messages:
    8,886
    Likes Received:
    1,784
    Rubix blurry updated to the newer system files (but not the bootloader) so it reports back a higher version number (2.3.20 vs 2.3.15) and Android 2.2.1 (vs 2.2).

    As was said tho, roms can report any version so may not be accurate.
     

Share This Page

Loading...