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

Root [ROM RELEASE] 2.2-based Byron Bare

darkxsun said:
The main zip file? strange. Can you give me a full list of the messages it prints?

For those with success, are any using amon-ra? I'm unable to use it, so I can't test for it.
Click to expand...

Here's part of the message that comes up:

Writing BOOT:...
E:No space left on device
E:Error writing BOOT:
E:Failure at line 93:
write_raw_image PACKAGE:boot.img BOOT:

I'll try clockworkmod recovery and see if it can install that way.

EDIT: No, it still gives me the same error mesage.
 
voyager84 said:
Here's part of the message that comes up:

Writing BOOT:...
E:No space left on device
E:Error writing BOOT:
E:Failure at line 93:
write_raw_image PACKAGE:boot.img BOOT:

I'll try clockworkmod recovery and see if it can install that way.
Click to expand...

Sounds like you have bad sectors in your boot partition and it's too much to have enough room for the boot image. It's ironically the same reason I can't use amon-ra (my recovery partition has bad sectors and it can't fit it).

If you are feeling adventurous, unzip the file, go into META-INF/com/google/android/update-script and remove this line:
write_raw_image PACKAGE:boot.img BOOT:
then re-zip everything and flash this new zip.

Do this only if you have faith in your /boot that came with 2.2.1 (i.e., 2.2.1 boots fine) and you are willing to take responsibility for it. You may have to restore a nandroid backup beforehand if /boot got partially written and corrupted.
 
voyager84 said:
Here's part of the message that comes up:

Writing BOOT:...
E:No space left on device
E:Error writing BOOT:
E:Failure at line 93:
write_raw_image PACKAGE:boot.img BOOT:

I'll try clockworkmod recovery and see if it can install that way.
Click to expand...

2 things I would try. 1st, try re-downloading and try flashing it again. Maybe there was a little glitch during your d/l process and something got corrupt. 2nd 'No space left on device'... If this is correct, then maybe do a factory restore on your phone before flashing, to clear up some space.
 
Matt's 175 said:
2 things I would try. 1st, try re-downloading and try flashing it again. Maybe there was a little glitch during your d/l process and something got corrupt. 2nd 'No space left on device'... If this is correct, then maybe do a factory restore on your phone before flashing, to clear up some space.
Click to expand...

It's possible but unlikely the download is corrupted.

Factory reset will simply clear /data and /cache, neither of which is related to the error of no room on /boot. This is almost definitely bad sectors. Normally they're nothing to worry about until you don't have enough good sectors left to hold what you want (as in my case, I don't have enough good recovery sectors to hold amon-ra).
 
@ darkxsun

Just curious. Which ROM is getting more 'action'. Regular or Bare? Do you have a way to track the number of downloads for each?
 
Matt's 175 said:
Which ROM is getting more 'action'. Regular or Bare?
Click to expand...

Download stats are on the mAndroid download pages. MediaFire downloads are a small percentage of the whole.

Byron (full) has had many more downloads but far fewer comments.
 
darkxsun said:
Sounds like you have bad sectors in your boot partition and it's too much to have enough room for the boot image. It's ironically the same reason I can't use amon-ra (my recovery partition has bad sectors and it can't fit it).

If you are feeling adventurous, unzip the file, go into META-INF/com/google/android/update-script and remove this line:
write_raw_image PACKAGE:boot.img BOOT:
then re-zip everything and flash this new zip.

Do this only if you have faith in your /boot that came with 2.2.1 (i.e., 2.2.1 boots fine) and you are willing to take responsibility for it. You may have to restore a nandroid backup beforehand if /boot got partially written and corrupted.
Click to expand...

That did it! Removing that line from the script got it installed and it works perfectly so far.
 
voyager84 said:
That did it!
Click to expand...

Great. Sorry to throw you in the deep end like that, but I'd rather not have a version of this ROM floating around that neglects to flash a working /boot. For you, it was perfect, but for anyone else, it's either equivalent to the main package, or confusingly harmful.

Glad you got it going.
 
darkxsun, you were asking for suggestions, and many are asking for this or that "stock" app be removed/installed, have you messed with some of the D1 roms? many of the devs there have scripts to remove or install "stock" apps as desired by the user. its a really nice convienent feature if you wanted to look into going that deep. then you could set just one version of Byron, and let the end user choose what to install/uninstall. I haven't tried this yet, but looks very interesting. I use a D1 myself, but two of my sons have Allys so, I might just check into this. Thanks for your time and work.
 
trav473 said:
many of the devs there have scripts to remove or install "stock" apps as desired by the user.
Click to expand...

I have not looked into the approach used by the D1 ROMs, but I have seen Velocity's approach, and I'm not a fan. It moves the apps to the sdcard when removing, and I feel this is too dangerous. In the event the user formats the card, the app can never be restored and the user may or may not know why.

Of course, this was a couple versions ago.

And I mean no offense to Trident. Velocity is a great product, I just don't like how it handles this one thing.
 
darkxsun said:
I have not looked into the approach used by the D1 ROMs, but I have seen Velocity's approach, and I'm not a fan. It moves the apps to the sdcard when removing, and I feel this is too dangerous. In the event the user formats the card, the app can never be restored and the user may or may not know why.

Of course, this was a couple versions ago.

And I mean no offense to Trident. Velocity is a great product, I just don't like how it handles this one thing.
Click to expand...

Thats a very good point. I'm not sure how they handle the uninstalled apps either, I'm not a dev and wouldn't know how to find that out. just thought I would throw that out there for ya.

If you wanted to look into it, I know CyanogenMod, Ultimate Droid, Sorcery, Saphire, Liquid, and a few others all have these scripts built in and its just a matter of going to their custom settings section and "clicking" the apps to install/uninstall.
 
trav473 said:
Thats a very good point. I'm not sure how they handle the uninstalled apps either, I'm not a dev and wouldn't know how to find that out. just thought I would throw that out there for ya.

If you wanted to look into it, I know CyanogenMod, Ultimate Droid, Sorcery, Saphire, Liquid, and a few others all have these scripts built in and its just a matter of going to their custom settings section and "clicking" the apps to install/uninstall.
Click to expand...

I'll look into a simple install and uninstall mechanism for a future version, if there's decent demand, but I'll probably build something myself.
 
Valkerie said:
Keeping the Themes app in both Bare and Byron may not be a bad idea. It is an easy way to switch between launchers.
Click to expand...

The standard way of doing this is going to Settings->Applications and clearing the default from the default launcher. It's the same way you change default browser, etc.

I was under the impression the Themes app was pointless for this reason. Does anyone else use this?
 
darkxsun said:
I'll look into a simple install and uninstall mechanism for a future version, if there's decent demand, but I'll probably build something myself.
Click to expand...

Thats cool, Don't feel like I am pushing, just adding to the conversation. Again, I want to express my thanks for your time and work. I am sure others appreciate what you do too.
 
darkxsun said:
The standard way of doing this is going to Settings->Applications and clearing the default from the default launcher. It's the same way you change default browser, etc.

I was under the impression the Themes app was pointless for this reason. Does anyone else use this?
Click to expand...

Yes, but why go that deep in a menu when I can just touch an icon on my screen and select a new launcher with one more touch?
 
Valkerie said:
Yes, but why go that deep in a menu when I can just touch an icon on my screen and select a new launcher with one more touch?
Click to expand...

Not to tell you your way is wrong, but I think the reasoning is this: if you're sticking with one launcher for a while, it's not a big deal to go to that menu. If you're changing frequently, you shouldn't set as default, you should pick each time.

I don't suspect this is one that is used often enough to be worth including by default but maybe as a add-on. That is, if I ever get any feedback on the Gmail addon I posted.
 
I'm using Byron Clothed anyway. :-p. I also have an apk of the LG home selector I install using the terminal so it's a non-issue really.

I'm still enjoying this odexed ROM.
 
This is so very nice! I installed the gmail addon right after flashing the rom and seem to have no problems, hough Im considering reflashing without it just to be more barebones lol
 
So I'm running the naked rom and truly loving it. I have 30 apps with 100MB free! Some are on the sd, most are not. Having run velocity all the way to froyo, I've always run a fast rom and this one is no exception. I like how nimbly this rom runs launcherpro (was having issues with stock rooted 2.2.1 running it). My phone feels snappier and crisp. This rom is one of many which will enhance our froyo experience. That being said...

I was wondering if you could point me in the direction of downloadable sound packages. I don't know about you but I do like the sound package included in Tridents' roms (thank you trident for your roms). Any help would be appreciated.

jmar
 
jmartino5920 said:
So I'm running the naked rom and truly loving it. I have 30 apps with 100MB free! Some are on the sd, most are not. Having run velocity all the way to froyo, I've always run a fast rom and this one is no exception. I like how nimbly this rom runs launcherpro (was having issues with stock rooted 2.2.1 running it). My phone feels snappier and crisp. This rom is one of many which will enhance our froyo experience. That being said...

I was wondering if you could point me in the direction of downloadable sound packages. I don't know about you but I do like the sound package included in Tridents' roms (thank you trident for your roms). Any help would be appreciated.

jmar
Click to expand...

You can extract velocitys sounds from the velocity_0.4_release.zip you already downloaded. Theyre located in velocity_0.4_release.zip/system/media/audio/ringtones

You can adb push them to your phones /system/media/audio folder, or just create a folder on your sd card called media and create a ringtones folder in there.

This is what I love about a barebones rom. It starts with the minimum and I only add what I want.
 
How about Maps, Nav, StreetView, and Places...the Update to Byron 4.0.2 adds gmail, google search, and youtube to this rom just fine for me. I use Navigation a lot though, so it would be much appreciated if we could get those.
 
Great rom. I really like the idea of adding what I want/need rather than removing a bunch of crap.

An optional zip with the live wallpapers would be nice.
 
You must log in or register to reply here.
Back
Top Bottom