Database Develop

[Q] Easy Rom Installer

Anyone know of some sort of one click or easy rom installer that a beginner could do? I've rooted, but updating the g1 to froyo is just so intimidating. Anyone know of some sort of one click installer?

No. Several parts of the system need to be updated, so that isn't possible.
Just tell us what you need help with.

the "easiest" way to install a rom is through the ROM manager app that requires ClockwordMod recovery, but I've heard that it is pretty unreliable for the G1. I personally use AmonRa 1.7

same here. AmonRa is in fact the best way as it frees up the needed files to be changed or removed when installing a rom.
its quite simple to install a froyo rom. im a novice myself and found it easy to do. takes about 10 mins if you include collecting and transfering the files you need

Can anyone explain the steps to upgrade to froyo from 1.6 with AmonRa 1.7? Did a search, couldn't find anything on the topic. Thanks in advance!

most devs actually put this in their threads with the rom they have created. if not check out cyanogens wiki on his website. he has some information on how to do it on there.
I think all you really need to do is install the rom through amonra then if you want google apps, find one that will work with it and install that.

I'm sort of confused as to what AmonRa actually is. What does it do?

michael2041 said:
Can anyone explain the steps to upgrade to froyo from 1.6 with AmonRa 1.7? Did a search, couldn't find anything on the topic. Thanks in advance!
Click to expand...
Click to collapse
Mind giving your current setup is first?
ROM (which 1.6, CM4?) ? Recovery (RA-1.7.0 I guess)? SPL (Danger perhaps?)?

pl4sMa said:
Mind giving your current setup is first?
ROM (which 1.6, CM4?) ? Recovery (RA-1.7.0 I guess)? SPL (Danger perhaps?)?
Click to expand...
Click to collapse
I'm not rooted and have no custom roms installed...just stock ota 1.6 donut...I know how to root. But the froyo part just confuses me. What's amonra and how is it used to install froyo? All the guides confuse me...can someone break down everything to a beginner level so I can understand it a little more? I'm naturally good at most tech stuff so I catch on quick...I need help though!

Let's Give it a Shot
michael2041 said:
I'm not rooted and have no custom roms installed...just stock ota 1.6 donut...I know how to root. But the froyo part just confuses me. What's amonra and how is it used to install froyo? All the guides confuse me...can someone break down everything to a beginner level so I can understand it a little more? I'm naturally good at most tech stuff so I catch on quick...I need help though!
Click to expand...
Click to collapse
Hmm, lemme try. At least you're sure until the root part.
AmonRA is a recovery... the phone has system/boot, recovery, and fastboot.
Try reading ... hxxp://wiki.cyanogenmod.com/index.php?title=HTC_Dream:_Rooting
then shoot a question on which part u actually aren't sure and I'll try to help. CyanogenMod 6 is based on Froyo, so I guess that's the one you want.
No URL posting capability yet, so edit what you have to edit

Why Complexities

First off, Thank you to all the dev's who've put out all the great roms (too many to mention)....
But, as I was reading through some of the most recent releases of roms, I found myself more and more frustrated with confusion. It wasn't the screenshots (thanks, it helps), it wasn't the list of changes/additions/subtractions (that really helps), it was more the complex install info.
I'm not trying to hurt anyone's feelings, but why would you go off on a tangent to left field while your writing down how to install something? Can we get a universal install procedure?
Most roms are released within hours and in some cases days of one another. Lets assume that rom a has what newest rom b needs and create something from that. Then if you need to express random thought for the new guy, that could be post #2. I guarentee that most of the people here have flashed and re-flashed and soft bricked and flashed again.
Guess what I'm trying to say is, rom dev's are releasing things that probably no one will use cause they aren't clear and concise on the install procedure.

FroztIkon said:
First off, Thank you to all the dev's who've put out all the great roms (too many to mention)....
But, as I was reading through some of the most recent releases of roms, I found myself more and more frustrated with confusion. It wasn't the screenshots (thanks, it helps), it wasn't the list of changes/additions/subtractions (that really helps), it was more the complex install info.
I'm not trying to hurt anyone's feelings, but why would you go off on a tangent to left field while your writing down how to install something? Can we get a universal install procedure?
Most roms are released within hours and in some cases days of one another. Lets assume that rom a has what newest rom b needs and create something from that. Then if you need to express random thought for the new guy, that could be post #2. I guarentee that most of the people here have flashed and re-flashed and soft bricked and flashed again.
Guess what I'm trying to say is, rom dev's are releasing things that probably no one will use cause they aren't clear and concise on the install procedure.
Click to expand...
Click to collapse
I see your on super nova. Have you looked at Mosaic. I tried to make the directions as simple as i could

right now with the recent port of the i9000 2.3.3 things have changed.
and changed very recently.
soon enough there will be an easier, more standard way to upgrade.
but keep this in mind....
what we are doing here is programming a phone. the devs AND YOU!
programming an electronic device is not a simple thing, and is not childs play.
the devs have YEARS of experience in programming to bring us the software,
we need to understand what we are doing in order to do it.
so we need to understand programming.
this cannot be done in 10 minutes by just reading instructions.
and this SHOULD NOT be able to be done in 10 minutes by reading instructions.
there are real risks in doing this, that is why it voids your warranty.
you need to understand what you are doing to be able to do it.
thats why you must LEARN in order to do this.
nobody ever learns with brain-dead instructions.
the more you LEARN first, before flashing, the better your chances at success.
the easier the instructions the easier noobs run into problems! Brick their device or get scared and confused about very simple things that they should have understood first!
so the complexity has a dual purpose, it forces you to go out and LEARN before you do anything AND also provides you with alot of information to start learning
<<Captivate Post of the Week>>

TRusselo said:
right now with the recent port of the i9000 2.3.3 things have changed.
and changed very recently.
soon enough there will be an easier, more standard way to upgrade.
but keep this in mind....
what we are doing here is programming a phone. the devs AND YOU!
programming an electronic device is not a simple thing, and is not childs play.
the devs have YEARS of experience in programming to bring us the software,
we need to understand what we are doing in order to do it.
so we need to understand programming.
this cannot be done in 10 minutes by just reading instructions.
and this SHOULD NOT be able to be done in 10 minutes by reading instructions.
there are real risks in doing this, that is why it voids your warranty.
you need to understand what you are doing to be able to do it.
thats why you must LEARN in order to do this.
nobody ever learns with brain-dead instructions.
the more you LEARN first, before flashing, the better your chances at success.
the easier the instructions the easier noobs run into problems! Brick their device or get scared and confused about very simple things that they should have understood first!
so the complexity has a dual purpose, it forces you to go out and LEARN before you do anything AND also provides you with alot of information to start learning
<<Captivate Post of the Week>>
Click to expand...
Click to collapse
Nice long post. Although alot of rambling Tru but I like your last line

As for a standard set of installation instructions, I dont think we will ever see it. Each rom is as unique as the person that developed it, and with that individuality comes an individual requirement for implementation.

ATM some ginger roms are wipes, some arent, this used to be true for all froyo/eclair roms.
that is why we USED TO have to flash to stock each time. same now. (for non wipe roms)
that changed! it can again!
as for getting the bootloaders, if you are installing a WIPE rom you dont need to flash the whole i9000 package. Just the bootloaders alone and ONLY ONCE. some roms currently use this method.
other roms that arent wipe roms depend on apps and framework to be there, or might not like other stuff left over that may still be there. so it is necessary to flash back to i9000 stock, this can be done with or without bootloaders if you already have them. but most of the non bootloaders packages have been taken down. once again you only need to get the bootloaders once.
once again all this can change and standardize again. with the following intructions:
from eclair or froyo
1. odin flash GB bootloader and CMW3 kernel in a single package. (small 4 MB package!)
2. boot into CWM3 and flash a WIPE ROM.
done and upgraded.
my fastest upgrade was one extra step. the bootloader package had re-orient kernel with no cwm3 so i had to reboot and odin flash talon between step 1 and 2.
still pretty easy with a wipe rom.
we grow up so quickly...

About custom Roms

So, I installed Juwe's ROM and now that I have it installed... well... to me it just seems like a compilation for the lazy. Dont get me wrong, i really appreciate the work done by all chefs but, theres no real reason to use them. Or at least I think.
I believe if I flash a stock firmware and apply a custom kernel the results will be much better. Many of the "features" of these roms are thanks to the kernels flashed in them, and can be done manually. Also, I think many of the cosmetic improvements are not my cup of tea, and I much prefer the stock samsung animations, etc.
Please correct me if i'm wrong, or well help me out choose what to do. I'm not eager to reflash my firmware all over again. I would just like to flash something on my phone and never have to reflash again.
-Nestor

exactly....if you have the time and knowledge do it yourself....if not flash any of the custom roms prepared by the rom "chefs" out there....and be grateful for the opportunity (I suspect you underestimate the amount of work and intellect that these guys have invested in their custom roms...far more than just different kernels and basic cosmetics as you suggest)
Unless i am mistaken you have stated the obvious...if not, what is your point?

Oh, yes. I wasnt really obvious on what i wanted to do. Well, I see all of the things my rom has installed, and see that im still having some bugs, etc, and, well I cant diagnose where are they coming from. Is it my apps fault, etc, since all these modifications are done and all of these apps installed and now I really dont know what caused what.
So I think, what if some of the stuff that was done was unnecessary? What if just flashing to stock, and then adding stuff one by one until im satisfied will rid me of most of my problems?
I must admit I relate the rom chefs with the people from the pirate bay who give you modified versions of windows, with all the necessary stuff done, but you can get a fresh copy of windows and get much better results on most cases.
I mean no disrespect to anyone's intelect, or ego. Im a really new guy myself, but the more I learn the more I realize, maybe the best way to go is just flash stock, root, get a new kernel and all will be peachy. That sounds too easy though. So i raised this discussion to see what do people think.
Edit: Well, after reflashing and doing some stuff, like repartitioning tried some custom kernels and ended up bootlooping my phone, and after much frustration, I reflashed Juwe's. Now I can appreciate how well this works. The couple of erros may have been caused by not repartitioning the first time. Now Im very happy with how my phone is working. Hopefully, this is the last firmware i ever flash.

[Q] A few questions about mods, from a total n00b

I have a Sprint HTC hero with original everything.
I've been wanting to do a mod but that brings up a few questions.
1) A lot of places say the CM7 mod from here is great for this phone but I clicked around and can't find a list of things it changes/improves. Why would I install a mod and will most things continue to work (market places, email, phone utilities, purchased apps).
2) All roms have those warnings that they void warranty. How often do they brick the device? Is this something I should worry about?
Sorry for the noobish questions but I am looking towards modding the hero but I want to make sure I don't make it worse.

1.) well basically MOD's are roms that people cook themselves from the scratch android or from a base like for example the DesireHD android base. They can do things varying from the look and feel of android to adding elements like being able to browse Privately on your browsers. i know that CM7 allows you to do that. Being able to flash different roms opens up a even bigger Android World.
2.) I have been flashing back and forth for a long time and not once have i bricked the device. Besides not like a little system restore wont fix anything. Also if you happen to send you device into maintenance or repair just restore you phone back to factory settings. All of it is reversible. When i first started out it helped me to really read NOOB forums so i didn't do something i would regret, but you should have nothing to really worry about.

reply from a still nearly noob, although i read alot about roms already and flashed my sgs2. ill just attemt to help you a little here.
1) i now flashed lite'ning rom on my phone as there is no cm7 for it yet. once realeased i will also flash it as i also read that it is the most widely used rom with best support. within a thread of the specific rom there should be a list of improvements/major changes or what will be added if you flash the rom. these and mostly more battery life and/or more speed are the reasons people flash roms. after flashing the phone you will have all the things still working, sometimes even better. for apps it depends on the rom. mine for example didnt require a wipe that delets all you data on the phone. others (as i think cm7 also) require a wipe of all you on-phone personal data apps and so on (not sd card if im not mistaken, please correct me!)
2)yes, you void warranty if you flash a custom rom, root or do sth else on the firmware not published by the manufacturer. when i flashed and overflashed my phones rom for several time already i haven't had any problems. and as i read all over the net/xda there is just a very little chance to brick your phone and even there you might have possibilities to revive it, i think. but im not sure on this, cosider others informations first!
hope i could help you a little from noob to noob and enjoy flashing roms. oh and of course have a look in the htc hero android development section for roms!
cheers!
IQHU

Damn - too late, and didnt recognize until now...
Sent from my GT-I9100 using XDA App

Go to this thread and start reading some of the linked threads. All your answers can be found there.

[Q] Advice for Flashing custom ROMs

I have a friend that want's to flash a custom ROM to his captivate. He has it rooted but hasn't done anything else.
I said I would install CM7 or something on it for him. I had a Droid and Droid2 and am now on a Thunderbolt. So rooting and flashing ROMs aren't new to me. But, as with all three of my phones, things are a little different on the Captivate.
I see there's this Odin thing and I think no permanent clockwork recovery? How do you install ROMs on the Captivate? I see there's a new CW that doesn't need what ever Odin is. He's on the stock kernel and everything. So do I just boot into recovery and flash the clockwork update.zip and then flash normally through CW?
Also, being as he doesn't know how to do any of this, which is the most stable and bugless ROM that everyone uses. He won't know how to flash something else, so I need something that is as close to 100% as possible, speedy, and close to, if not ASOP.
Thanks

Hello,
Please post in Q/A as this is not a development topic. Suggest mod move the post.

I suggest that your buddy do some reading. Are you going to be there to hold his hand every day if something goes wrong with his flash? Tell him to educate himself. And if flashing is not new to you and your 3 phones, you should know what section a question like this goes in, is it "android development" related?
Sent from the frozen tundra known as Canada.

Most stable rom I have ever used is firefly 3.0. But your friend should see u do it and at least know how u did it to his phone. And yes from stock just do the clockwork mod update.zip and then flash through clockwork mod, there is a little more involved in flashing cm7 and it is not the most stable rom anyways. Good luck and I hope u take my advice on firefly you won't be dissapionted

The flashing procedure will vary depending on what ROM you want to run.
CM7/MIUI have their own set of procedures.
Flashing a Froyo based ROM you'll have to flash CWM 2.X then the ROM
Flashing a Gingerbread based ROM you'll have to flash the updated Gingerbread bootloaders first via Odin then flash the Kernel or CWM 3.X or higher, then the ROM.

Post in question section plz
I advice you to start flashing a not complicated rom (2.2) , once you get the hang of it then you go advance.

Moved to proper forum.

Odin is a program that is ran in the computer to flash a rom, bootloaders, and kernel at once. For it to work your phone has to be in download mode. Clockwork works with rom manager in the app store, some roms have it in the kernal.

Sorry, the forums I used before all root related things, including questions, went in the Root section. I thought Q&A was for non-root/development questions.
Thanks a lot Dustin, Kyuta, and bassplayer for the information.
I am going to show him how to do it. But I'm not going to hold his hand every time. That's why I wanted something stable where he wouldn't have to flash something else to get functionality that was missing.