• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Liberation - Development Ceased

Medion

Medion

Android Expert
I'm maintaining three ROMs over at XDA. Rather than copy/paste and then maintain all three threads on multiple forums, my intent is to just post their links and a description in one thread to maintain here. However, this will be viewed as a master thread, and I will offer the same support here that I do over at XDA. So, feel free to post questions here, or to PM me on these forums.

Droid Incredible Stock ROMS

  • based on the November OTA
  • stock, rooted, patched against the recent Android Market malware attacks
  • two versions; one truly stock, and one deodexed to allow for user customization
  • edify script allows for flashing in ClockworkMod Recovery 2.x and 3.x.
Liberation

  • stock ROM with minor modifications and bloatware removal
Liberation Enhanced

  • deodexed version of Liberation
  • comes in a beta (Gingerbread version) as well
 
Some significant updates to the Peanut thread (first three posts) that allow you to make the ROM of your dreams. Post questions here or at XDA (wherever you're comfortable) and I'll be glad to help.
 
Can't believe the OP isn't riddled with thanks button hits. Thanks Medion, guess I haven't been spending as much time in the Rom forum lately...missed this until now.
 
Updated to version 1.4 (which is actually renamed Liberation 1.0). Still the same concept, stock minus carrier bloat/restrictions. Also has a beta version based on today's Gingerbread leak. Enjoy.
 
I've been wracking my brain trying to figure out why removing the stock "VZW_Droid.mp3" and replacing it with another mp3 causes such a problem after boot. First, there is no sound. The new file is not played before the animation. Second, when the phone boots, and finishes loading, pressing any of the buttons (power, volume, and face buttons) will force the phone to display the white HTC screen, and then come back. The touchpad buttons and widgets work fine, though. However, the only way to turn the phone off is to pop the battery.

I decided to look through the xml files in the 'customize' folder, and found the 'default.xml' in /system/customize/CID. The last entry is:
-<BootConfiguration> <BootAnimation audio="/system/customize/resource/VZW_Droid.mp3" animation="/system/customize/resource/VZW_bootanimation.zip"/> </BootConfiguration> </customization_form>

I'm wondering if this has anything to do with it. Does the system get confused because of contradictory information? It goes looking for one file, but finds another, and somehow doesn't load properly? If so, how can that one string change things so much?

Then there is also the 'default.xml' file in /system/customize/MNS. There are strings in there for every app in the /system/app folder. Does modifying the contents of that folder also confuse the system, because it can't find what it's looking for?

There is also this entry in the 'CCInfo.txt' file in /system/customize/Resource:
Build ID: 50411; SKU: VZW IncredibleC Froyo default; CID: default; MNS: default
This seems to be telling the system which xml files to use to load the necessary data for everything to work properly.

Unfortunately, there is one hole in my theory. If you simply remove the 'VZW_Droid.mp3' file and not replace it with anything, the system boots fine, and you have no problems.

Now, I'm not a coder, a modder, or anyone who can build a ROM. I'm just learning how to flash ROMs and radios, and haven't even gotten into kernels yet. I'm leaving all of that to the professionals. But could someone please explain this to me? When Medion made his original post over on the XDA-Developers forums, he said we could use Liberation Enhanced to create our own custom ROM by changing the boot sound, the wallpapers (if you could find compatible ones), and other little add-ons like changing the built-in apps, and the reboot menu. However, it seems there are some bugs in the system, either that or I just don't quite understand how to get this to work the way I want it to; both are possible, the latter more so.

One other thing I noticed is if the system doesn't load properly, you will definitely notice after the initial setup (logging in/creating your gmail account) that the time is about four hours ahead. The last boot I did was just now, but the phone was telling me it was 4:24 this morning.

~Farren (perpetually perplexed, often frustrated, but always Incredible-y Fascinate-d)
 
farren said:
I've been wracking my brain trying to figure out why removing the stock &quot;VZW_Droid.mp3&quot; and replacing it with another mp3 causes such a problem after boot. First, there is no sound. The new file is not played before the animation. Second, when the phone boots, and finishes loading, pressing any of the buttons (power, volume, and face buttons) will force the phone to display the white HTC screen, and then come back. The touchpad buttons and widgets work fine, though. However, the only way to turn the phone off is to pop the battery.

I decided to look through the xml files in the 'customize' folder, and found the 'default.xml' in /system/customize/CID. The last entry is:
-&lt;BootConfiguration&gt; &lt;BootAnimation audio=&quot;/system/customize/resource/VZW_Droid.mp3&quot; animation=&quot;/system/customize/resource/VZW_bootanimation.zip&quot;/&gt; &lt;/BootConfiguration&gt; &lt;/customization_form&gt;

I'm wondering if this has anything to do with it. Does the system get confused because of contradictory information? It goes looking for one file, but finds another, and somehow doesn't load properly? If so, how can that one string change things so much?

Then there is also the 'default.xml' file in /system/customize/MNS. There are strings in there for every app in the /system/app folder. Does modifying the contents of that folder also confuse the system, because it can't find what it's looking for?

There is also this entry in the 'CCInfo.txt' file in /system/customize/Resource:
Build ID: 50411; SKU: VZW IncredibleC Froyo default; CID: default; MNS: default
This seems to be telling the system which xml files to use to load the necessary data for everything to work properly.

Unfortunately, there is one hole in my theory. If you simply remove the 'VZW_Droid.mp3' file and not replace it with anything, the system boots fine, and you have no problems.

Now, I'm not a coder, a modder, or anyone who can build a ROM. I'm just learning how to flash ROMs and radios, and haven't even gotten into kernels yet. I'm leaving all of that to the professionals. But could someone please explain this to me? When Medion made his original post over on the XDA-Developers forums, he said we could use Liberation Enhanced to create our own custom ROM by changing the boot sound, the wallpapers (if you could find compatible ones), and other little add-ons like changing the built-in apps, and the reboot menu. However, it seems there are some bugs in the system, either that or I just don't quite understand how to get this to work the way I want it to; both are possible, the latter more so.

One other thing I noticed is if the system doesn't load properly, you will definitely notice after the initial setup (logging in/creating your gmail account) that the time is about four hours ahead. The last boot I did was just now, but the phone was telling me it was 4:24 this morning.

~Farren (perpetually perplexed, often frustrated, but always Incredible-y Fascinate-d)
Click to expand...


I'm sure medion will stop in and clarify, but I believe if you are changing the boot sound, you have to rename the new .mp3 correctly to VZW_Droid.mp3
 
sdrawkcab25 said:
I'm sure medion will stop in and clarify, but I believe if you are changing the boot sound, you have to rename the new .mp3 correctly to VZW_Droid.mp3
Click to expand...

Correct, and thank you for helping him.

Basically, as you saw from that string you posted, it's looking for a specific MP3 file. Placing any other MP3 file in that directory with a different name is completely irrelevant to the bootup process. It's not even going to look for it.

However, I have no idea why it's giving you bootup issues. It seems to me that the file, if not named properly, should be completely ignored. My recommendation would be to try it with a new MP3 file renamed to VZW_Droid.mp3. Also, there's always the chance that it has to be within a certain file size limit. I haven't played with it too much, just deleted it myself.
 
sdrawkcab25 said:
I'm sure medion will stop in and clarify, but I believe if you are changing the boot sound, you have to rename the new .mp3 correctly to VZW_Droid.mp3
Click to expand...
I actually thought the same thing at first, and did try it. Unfortunately, it still borked the install. I'm wondering if the file needs to be the exact same size and specs as the original. That part I did try, but didn't rename it.

I also have an update on the progress of this little test. I've systematically removed unwanted apps: Stocks, News, Facebook, Car Panel, Flickr, and wallpapers. After I removed each apk file, I'd create a new zip, just in case one didn't work for some reason. All of them had the new 3-in-1 reboot menu and no VZW_Droid.mp3.

Unfortunately, the first test which was just removing the Stock.apk and com.htc.StockWidget.apk files, resulted in a broken install. Curious and frustrating. At least the original Enhanced file with only the 3-in-1 boot menu works.
 
Three updates coming tomorrow evening;

Liberation v1.1
Liberation Enhanced v1.1
Liberation Enhanced v2.0 Beta 2
 
Nevermind, flashed the beta 2 and answered my own questions. Nice rom. :)
 
xfuchsiax said:
Any estimate of when we'll see new versions of your ROMs with the official Gingerbread update?
Click to expand...

A few issues:

-The official OTA was delayed due to bugs, of which many of us are assuming the same bugs that cropped up in the recent leak.

-The developer who was given the leak made a slightly customized ROM out of it. I prefer to work with an OTA or RUU (or source) rather than make my ROM based off of someone else's work. According to this developer, he agreed to only release the leak as a ROM and not as an RUU.

So, until we get a better leak, or the OTA comes out, I won't be releasing a final version. This doesn't rule out more beta releases though based on the May leak, nor does it preclude me from playing with the current ROM leak.
 
I am currently running Liberation Enhanced v2.0 Beta 3. If I want to go to Beta 4 should I do a complete wipe and reload everything or can I just load 4 over 3?
 
pharpe said:
I am currently running Liberation Enhanced v2.0 Beta 3. If I want to go to Beta 4 should I do a complete wipe and reload everything or can I just load 4 over 3?
Click to expand...

From 3 to 4 you can just do a flash over. Wipe cache and dalvik if you'd like to be safe, but no need to wipe data. I will STRONGLY encourage user to wipe data when RC 1 comes out.
 
I've downloaded V2 Beta 4 twice. Once on 3g and once on wifi. Both times when I go into ROM Manager to flash it I get an error stating that ROM Manager cannot read the package. Am I ******ed or something?

I just successfully flashed Nils Gingersense about 5 min ago after trying to flash liberation so I don't think it is my phone.
 
ctc said:
I've downloaded V2 Beta 4 twice. Once on 3g and once on wifi. Both times when I go into ROM Manager to flash it I get an error stating that ROM Manager cannot read the package. Am I ******ed or something?

I just successfully flashed Nils Gingersense about 5 min ago after trying to flash liberation so I don't think it is my phone.
Click to expand...

Are you doing the direct download or one of the mirrors? The direct download from MU sometimes has issues. I might disable it. I've gotten a lot of positive feedback on Beta v4, so I'm inclined to think that it works.
 
Beta 6 will be up in about 15-20 minutes. Had to halt the upload after a ******ed mistake. Key change in this one is the addition of Quick Settings to the notification pull-down.
 
Just installed Beta 6 this afternoon, really like it so far! :)

Only question -- is there a way to adjust how transparent the pull-down menu is? It's a bit too transparent for me.

I really like the battery meter with the percentage.
 
xfuchsiax said:
Just installed Beta 6 this afternoon, really like it so far! :)

Only question -- is there a way to adjust how transparent the pull-down menu is? It's a bit too transparent for me.

I really like the battery meter with the percentage.
Click to expand...

Next release won't be transparent. It will be stock (as is the intent of the ROM). However, you can always use UOT Kitchen to modify it to your liking. Same with the battery meter. I'll have a guide on that with the next release.

However, I've scrapped all beta plans with this build. Next release will be a release candidate based on the .3 OTA.
 
You must log in or register to reply here.
Back
Top Bottom