Hi everyone!
I hope I came to the right forum with this...
I (once upon a time) was a proud owner of a Milestone (A853). Then I was the content owner of a Milestone running Android 2.1. This turned into a disillusioned and never-to-buy-Motorola-again-ever Milestone owner when it took them ages to release an update to 2.2. Now that they did, I'm just plain angry. Their release is so ridiculously bad, it's a beta version at best. Therefore I have finally decided to finally get a custom ROM.
Now I did a bit of googling and found this forum and another site hosting ROMs (theunlockr.com/category/roms-2/android-roms-2/motorola-milestone-roms/ - can't post real links yet, sorry)
Seems like there are quite a few ROMs to choose from. Unfortunately I have no idea which one would be the best for my needs, nor do I know how I'd get them onto my stone...
Things that are important for my are (in that order):
- long battery life
- stable operation
- email via IMAP and Exchange
- camera, gps for My Tracks & Navigation
- sync with google calendar & contacts
- pdf & doc-viewer
- bluetooth and wifi-tethering (the later with WPA2)
- good performance
So I need help with two things: choosing the ROM best meeting these demands, and getting said ROM onto my phone. The tutorials I found so far were not very helpfull to me unfortunately, since they seemed to asume I already knew quite a few things and had a bunch of tools already installed. Is there something like a "dummies guide to flash your Milestone"?
And can someone recommend a certain ROM to me? Preferably one that isn't to hard to find and is easy to flash?
Also, do I loose the stuff stored on my SD-Card when I flash the phone? There are quite a lot of pictures and My Tracks, well, tracks, that I'd hate to loose.
tl,dr: Motorola sucks, I need help in choosing a ROM and getting it on my Milestone.
Thx,
Alex
You should try APAC.. long battery time
mikicishte said:
You should try APAC.. long battery time
Click to expand...
Click to collapse
I think you need to use TheFroYoMod, it's a very stable and battery friendly ROM. I don't want to brag, but I think my guide is very n00b friendly: CLICK
There is also a list of all ROM's available for the Milestone.
I'm using CM7 at the moment and i really love it, you also need to try this one out.
Installing a ROM doesn't touch your SD card outside of reading the install package.
Your choice of ROM is really a personal thing but a pretty safe bet to start with CyanogenMOD 6; it's one of the most common ROM's and it's very stable. While the Milestone is not "Officially" supported by CM, there are a ton of folks around here that have run it, and are quite familiar with it. Check out the link in the Milestone Dev section of this forum. As a first time flasher I'd stay away from CM7 at this time, it's still in development.
A couple of reminders:
-Your Milestone is not a DROID and is not compatible with DROID ROMS or guides.
-Always insure your battery is fully charged before flashing anything. Having a dead battery with a FUBAR ROM is bad.
-Back-up your stuff! Once you have the custom recovery loaded you can create a "Nandroid" back-up of your stock ROM (basically a disk image) through the custom recovery. This will give you something to fall back on if the ROM softbricks your device.
The guide posted above is a great guide. Way clearer then the one I followed originally. I highly recommend it.
thx 4 all your posts!
Actually I already flashed cm7rc3 at about 1:30am on sunday, after I worked my way through a lot of tutorials.
It works quite fine, only the galery-app is giving me trouble, but I guess that could be connected to me havin 1.4k photos on my sd-card. Guess it's time for some cleanup!
Thank you drae52 for pointing out the link (and thank you eXtink for putting it in your sig)! Especially the OR part is really helpfull, as I didn't know until now what all the options do and was afraid to touch any. Now I'm definitly looking forward to installing that adblocker!
Now that OR is set up good and propper and I figured out the procedure I think I'll try some other ROMs too in time. Thank you again for your help!
Alex
Hi everybody!
so can anyone explain me how to deodex my entire rom? and it's VERY IMPORTANT.
i need a good and serious guide.
my firmware version is xwjvb, csc: neejv3 AND i have cf root
i have no idea how it's done and ive clearly never done it but it dont mean i cant,
Also, ive found this post "http://forum.xda-developers.com/showthread.php?t=765270" but it's a lil bit confusing, i have xultimate 2.2.3, and for example after step 4 on that guide, i dont find any guava.odex to remove, and it doesnt even work when i start the 4th choice.....
im also not sure if it will work on my phone/os versions.
so will anybody help me please, i really need to deodex to especially try the touchwiz 4 port!
"http://forum.xda-developers.com/showthread.php?t=1050666"
DOn't waste your time in trying to do it yourself; it's already available on this forum. Check this one out!
http://forum.xda-developers.com/showthread.php?t=948790
wow, this is GREAT!!! exactly what i was looking for, thanks ALOT
***eventhough i no longer really need to manually deodex thanks to ramad, and to widget21 for letting me know about it, i'd still like to learn how to manually do it...... so can anybody please help?
once you are rooted the easiest and quickest way to get deodexed is installing a custom ROM -- there are several now that are fairly minimalist and you can cook a bare bones custom rom over at Doc's kitchen. Custom ROMs have the advantage of not only being deodexed but zipaligned and consistent with the file system. Why re-invent the wheel?
lgsshedden said:
once you are rooted the easiest and quickest way to get deodexed is installing a custom ROM -- there are several now that are fairly minimalist and you can cook a bare bones custom rom over at Doc's kitchen. Custom ROMs have the advantage of not only being deodexed but zipaligned and consistent with the file system. Why re-invent the wheel?
Click to expand...
Click to collapse
im so NOT going to reinvent anything, im not even sure if i can anyways LOL, i was just curious cuz when they talk about it it's like something than can simply be done after flashing a stock rom like rooting..... i already goofed up and lost everything i had on the phone so flashing a new rom is not that big of deal anymore lol
know how you feel: my understanding comes from doing it the hard way and having to rescue the phone several times, so now I know better I try to help people not make the same mistakes I did while I was trying to sort it out myself.
Hope you flashed the kernel and rom you like that gets the most out of your phone and all is excellent today!
Hi guys!
Since two days I'm trying to create a ROM based on HTC Sense, porting from HTC Desire to our Nexus One using, as a base, the RCADSmixHD ROM.
I've been able to complete the entire package .zip and installing succesfully, BUT at reboot I'm stuck at the Nexus logo...
Do you think it's a kernel-related issue?
I really don't have any other ideas...
EDIT: I'd also like to know how to develop/modify a kernel for our Nexus One, but based on HTC roms... Someone has guides/links?
Try to Flash this Kernel: 2.6.35.6-eViL--10-7--1-wmcfg by eViL D:
You can find dl link here : http://forum.xda-developers.com/showpost.php?p=16995049&postcount=2
I had problems with the kernel include in RCADS on my N1
Thanks but no changes here... BTW the kernel included in RCADS rom works with my Nexus.. But here in this new ROM that I'm trying to develop I don't know what's wrong...
My guess there's something wrong with the ROM itself you probably have a few lines of code somewhere that are not working right. Were you able to compile the code on your computer?
Well, actually I'm trying to port a Sense ROM from HTC Desire with 250mb fit into /system/... I think that's the problem because my Nexus One could have bad blocks and/or less space into /system/, so this ROM wouldn't fit. I think so.
Regarding the code, I haven't written any kind of code, apart from looking at updater-script to be ok... Other suggestions? Thanks anyway, much appreciated
Now I'm trying to port a different ROM, the Desire S Gingerbread 2.3.5 with Sense 3.0!
But after replacing many folders and files from a Sense Rom of the Nexus One and the target Sense Rom that I'm developing, I have replaced boot.img and edited the updater-script properly (I think).
After installation, it's stuck at the Nexus logo... always!
What's wrong????????
Look at your logcat.
And at your /proc/kmsg.
If you don't know what these 2 mean - read up on those, use some googling.
If you can't - I believe you won't be able to develop anything worthy, or anything at all.
Moreover, Nexus has 145MB on /system partition. You need to utilize SD-EXT partition and symlink parts of the ROM to make it fit.
If I'm speaking Chinese and you can't figure it out - read the previous paragraph
From your posts I can't detrmine if you are developing or just trying to flash the rom to your phone, since you haven't done any coding. Am I misunderstanding?
rugmankc said:
From your posts I can't detrmine if you are developing or just trying to flash the rom to your phone, since you haven't done any coding. Am I misunderstanding?
Click to expand...
Click to collapse
You're right, because I'm not coding for a completely new ROM..
I'm just trying to "assemble" different pieces of ROMs together, a porting!
The only thing to "code" is the updater-script (or update-script)...
I have some errors there and I can't really determine why certain things goes wrong.. for now I don't have full knowledge of system partitions of Android.
And now I don't have enough time to fully explore this complex world
I have just tried for a couple of days...
Iperzampem0 said:
You're right, because I'm not coding for a completely new ROM..
I'm just trying to "assemble" different pieces of ROMs together, a porting!
The only thing to "code" is the updater-script (or update-script)...
I have some errors there and I can't really determine why certain things goes wrong.. for now I don't have full knowledge of system partitions of Android.
And now I don't have enough time to fully explore this complex world
I have just tried for a couple of days...
Click to expand...
Click to collapse
What did you add to the updater-script? And which folders specifically did you replace and change? And did you use a rooted ROM or the OTA one for the desire?
@Ace42:
Hi, I had used a rooted ROM from the Desire thread and I have followed this pretty useful guide which illustrates how to port Sense Roms:
http://forum.xda-developers.com/showthread.php?t=1222746
I have also had a look at almost all the files into each folders to see if there was differences in the code between the 2 roms..!
BTW the problem is in the updater-script...
For example I'm not able to mount "sd-ext", which is one of the most important steps to do for the Rom to being able to run into the device.
Look at that link properly, porting sense to OTHER SENSE DEVICES.
N1 isn't a sense device.
First, porting is more than replacing your boot.img and changing your update-script.
Like the other user said, you need to symlink files to your SD card cause N1 just isn't big enough.
Second, you're taking roms from other devices, most probably you'd have to re-write or mod the drivers.
Third, Porting just isn't that easy.
@illuminarias:
-> I know that, and in fact N1 becomes a Sense device when it has a Sense rom already installed... so it can be compared with other Sense devices.
-> I also know that we must symlink files, and you do that by adding lines of code into the updater-script (or update-script)!
-> If no one starts from something, how do you think that development for N1 can continue??
Iperzampem0 said:
@illuminarias:
-> I know that, and in fact N1 becomes a Sense device when it has a Sense rom already installed... so it can be compared with other Sense devices.
-> I also know that we must symlink files, and you do that by adding lines of code into the updater-script (or update-script)!
-> If no one starts from something, how do you think that development for N1 can continue??
Click to expand...
Click to collapse
The n1 also runs miui, is comparable to the m1? No.
Sent from my HTC Sensation Z710e using xda premium
illuminarias said:
The n1 also runs miui, is comparable to the m1? No.
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
I'm sorry but personally I love HTC Sense, not a-bad-copy-of-iPhone such as MIUI.
And since now I don't have money to change the device, I'll stick with this for other time.
Cheers
Iperzampem0 said:
I'm sorry but personally I love HTC Sense, not a-bad-copy-of-iPhone such as MIUI.
And since now I don't have money to change the device, I'll stick with this for other time.
Cheers
Click to expand...
Click to collapse
Yes, the same for me. I Love my nexus one with sense. Currently i also working on a gb sense rom for my nexus. Update Script is done and system should fit now with 151mb into the nexus rom. I ll will try to install & boot it at the weekend. Base was the currrent 2.3.3 Desire Release... Hopefully it fits into the small system and boots , to get logcats to work with...
If someone want to help & try, please contact me. I can upload the rom then to test. Currently i don´t have a lot of time , maybe together we get a working release...
@Deep-Knight:
Yep, I was working yesterday evening with the official Desire gingerbread update from HTC, but, as always, I'm stuck at the Nexus logo, after the installation is done... :/
I think I'm doing something wrong with system partition.. I know that our N1 can handle only 150mb for /system...
But I must admit that I'm using almost the same updater-script and boot.img as the N1Sensation v0.5 rom or RCADSmixHD rom..
Deep-Knight said:
Yes, the same for me. I Love my nexus one with sense. Currently i also working on a gb sense rom for my nexus. Update Script is done and system should fit now with 151mb into the nexus rom. I ll will try to install & boot it at the weekend. Base was the currrent 2.3.3 Desire Release... Hopefully it fits into the small system and boots , to get logcats to work with...
If someone want to help & try, please contact me. I can upload the rom then to test. Currently i don´t have a lot of time , maybe together we get a working release...
Click to expand...
Click to collapse
Just make a thread and upload your beta version, theres a plenty of people here able to test and help.
Thank you Menelkir for your interest!
But first I'll have to create something useful.. Maybe later on I'll create a new thread..
Till now I'm using some HTC Desire's ROM from the dedicated section here at XDA.
Stay tuned guys
As always graphical glithces will not be solved, until HTC releases Desire's Source Code..
The code is released already.
Unfortunately, the real trouble with porting ROMs is fixing the things that don't work - which will include trackball, hotspot etc - and this is the part where most of ROMs fail, because very few developers are skilled enough for that.
Hi Guys!
I'm what you guys call "the new kid who want's to play". I have various experience in Android flashing and updating, but I still have none kind of experience in building a Custom ROM.
But I said: What the hell! Let's try it! So I took a quick lesson at Nokia7Vista's tutorial on Youtube. I don't know if I can post links, but you can find it if you want to.
Anyway, My first ROM booted, and was based on the contents of Deodexed JW1. It has only some apps included, so no big deal here. But I wanted some experience before I get to the real thing.
OK, so I finished that, and I got to the real business:
I've started searching some of the best Custom ROM's out there. I found OserX's One, GalaxyDroid and S.U.R.F.A.C.E to meet my likes. I inspired myself from there (downloaded the 3) and took some apps, system tweaks, etc from them. OserX is JVZ, the other 2 are JW1. My ROM Was based on JW1 and was Odexed (like OserX and Surface). From what I know, JVZ and JW1 are pretty much the same ROM. Still, I didn't took anything from there but apps.
I've changed my drivers to the Nexus S drivers, and the framework-res.apk to get a CRT-on/off effect (Downloaded from this site, it's for JW1).
Basically, I did some mod's that everyone has did before. Still, when I flash the ROM, it get's stuck at the Galaxy S LOGO, (not bootanimation).
What should I do? What can be the cause of this?
Thanks...
Still no answer...
Now I understand the n00bs that post in the Development Section. Here no one f(^&&^5ing listen...
And I am no N00b, I'm just new to Custom ROM's ...I've posted to the right section, and still...no answer after a couple of days! That sucks!
Try sending a pm to one of those developers.
I've never created a Android ROM (although I used to on WM6.5).
The biggest advice that I can give to you is to go slow: Try to create a ROM in small steps - one change at a time. Very ften you'll find out that two apps supposedly working ok are incompatible with each other. The same applies to drivers and changes alike. So, if version 0.01 works and 0.02 don't, it's just a matter of see what's changed and try to figure why that change caused the new ROM to stop working.
I also agree with Valinorian - try PM experienced developers - we all walked that path already. But please: one change at a time.
Hello,
I am having trouble flashing the newest Zero Hero current release. RC 2.5
I would like to make a few statements before i go on to the issue just to air out a few things.
First i am a noob in all things considered with phones. Long story short i got a Heroc from sprint about 4 months ago. And as a computer aficionado since age 11 ( i am 35 now) i am pretty well verse in PC's, some small coding, and a little bit of linux. I build, repair and breathe PC.
Sooo.. modding phones came relatively came easy to me... I did the research... experimented etc..
Now that i have been modding my phone and experimenting for all this time i have come across my first actual problem that i have not been able to resolve with a quick google search/ XDA search. I flash roms all the time.. use scripts and mods to tweak thing on the constant. I am very well versed in these things and have succeeded 100%
Thank you for reading the above post as i just wanted to relay my knowledge to include that yes im a noob, but i have skills.
Problem:
Upon flashing the latest ZERO HERO RC 2.5 release i have came across a problem
I cannot get this rom to install... i am not talking boot... im talking install.
Heres is my install notes:
(reminder i install roms all the time.. testing/trying... its like a hobby for the last few months, i have hadf no issues EVER)
OK so i come from an CM 7.02 (sorry if i got the numbers wrong.. the latest.. ALTHOUGH i switch roms almost weekly. CM an ZERO seem to be the major roms i use)
TO THE ERROR:
Upon wiping all necessary things (may be noob but i get the things i need to do)
I get this:
"Zero-Hero- Sense- 3.5-RC 2.5-Tweak-03022012.zip (bad)
"open rom manager to report"
i have wipe.. removed.. etc etc.. multiple times.. what am i doing wrong.
This is the first time i have had a prob in the 50 times i have installed DIF roms..
Thanks you guys.. all of you. i especially appreciate Matt and Dast, Jay, AND EVERYONE ELSE involved in the DEV section for this HERO of ours.
And if i wasnt living off disability i would fully donate to these people. And when and if i do have a few dollars left over.. Matt and Dastin and Jay will most def be getting my support
Thanks you all.. I love you guys... and even everyone else..
Thank you.. thank you all
Nick
How are you flashing the rom?? What recovery do you have ??? Are you s-off ??? Did you flash anything before or after you flashed the Rom ??? What all did you wipe/format???
#Root-Hack_Mod*Always\
You just have a bad download. Redownload the file and verify the md5sum once you have the file on your SD card.
私のEVO 3Dから送信される。