Database Users

Most suitable ROM for Magic

So I've caved in to temptation and rooted my Magic. Now I'm looking for a suitable ROM - I've been into the Sapphire wiki and looked at the ones listed in there but they don't really explain what is on the ROMs.
What I am looking for is a ROM that contains Exchange sync, multitouch and browser with Flash, and most importantly - stability!
Also a few more questions - can I use the Android market if I have a custom ROM? I ask because in the ROM discussions I've noticed a lot talking about adding and removing software using the adb tool. Are there any other pitfalls I should be aware of, seeing as this my first time applying a new ROM.
TIA

Firstly what version of the magic do you have, 32A or 32B.
It's best to check out the rom development section and read what each rom is about there.
And yes you can still use the android market, the icon is still in all the custom roms.

Mine is the 32B - UK Vodefone.
The problem is the threads for those ROMs are sometimes more than 100 pages long with little or no descriptions about what is contained on them ... unless I am missing something

Well the ROMs will always be updated on the very first page, there's usually some kind of description as well of what is and whats not included.
As with all these things it's best to try each one out for yourself and see what you do and don't like.
As long as you use nandroid to backup your phone then you can always go back to the rom you were using before you falashed a new one.

I've tried installing Fatal1ty's 32B ROM from this thread:
http://forum.xda-developers.com/showthread.php?t=531617
(Fatal1ty-Hero-Full-v1-4-zip)
Rename it in update.zip
copy to sd
reboot (pressing home+power)
wipe
apply update
Click to expand...
Click to collapse
It said the update.zip was bad ...? Thank god for the nandroid backup (cheers for the advice on that one), I was restored and working again straight away on my old config ... but what went wrong? From doing a bit more reading, is it because the ROM isn't signed? Or should I just download the file again and try again - perhaps it corrupted somewhere along the way?

Can you provide the exact error you got?

st0kes said:
I've tried installing Fatal1ty's 32B ROM from this thread:
http://forum.xda-developers.com/showthread.php?t=531617
(Fatal1ty-Hero-Full-v1-4-zip)
It said the update.zip was bad ...? Thank god for the nandroid backup (cheers for the advice on that one), I was restored and working again straight away on my old config ... but what went wrong? From doing a bit more reading, is it because the ROM isn't signed? Or should I just download the file again and try again - perhaps it corrupted somewhere along the way?
Click to expand...
Click to collapse
I've been caught out with something like this before - make sure the zip you are downloading is the actuall update zip! Open it and check it only has the 3 folders and boot.img in it.
The update.zip maybe in the zip you have downloaded

But on a side note - the Hero Roms aren't suitable (yet) for the 32B's as the RAM is too small - wait until they cut it down a bit.
I would recommened either Nk2 or CyanogenMod [v3.6.8] && Palm Pre theme [1.5] ported
The second being the fastest i've used (rapid infact)

Cheers - I tried downloading the rom again and this time used adb push to copy and rename it to the sd card, tried again and it worked.
I agree with what you're saying about the hero rom needing some work though. I can't use touchflo or the weather app as they are too slow. Browser is also quite a lot slower than on the stock Voda UK firmware.
I really like HTC Peep and the facebook integration into my contacts, and the HTC keyboard is a lot better.
On your advice I'll give the CyanogenMod rom a try. I would like to find one good one and stick to it rather than become addicted to flashing the latest roms every week!

Is it possible to run Cyanogen 4.2.6 on the SDK Emulator?

Is there a good way to get the current version of Cyanogen up and running on the SDK emulator? I have several people that complain about my application widget closing when they open or close the keyboard. The logs show nothing pertaining to my application and the only thing they all have in common is a stock G1 with Cyanogen 4.2.6 and no home screen manager. Many others with non-modded G1's do not have this problem.
I'd like to test it out in the emulator since I now only have a Droid
I found some instructions with an image file to use for this, but it was for a very old version of Cyanogen.

do a nandroid backup and then copy the files from it in to the directory of a virtual device you have already created
then all shall be good

Is there a good source to snag a existing nandroid backup of 4.2.6? I don't have a G1 or any other device to run a nandroid backup on. Too bad too cause I just shipped out my old HTC Magic a few days ago. Now all I have is my Droid.
I'll search around for one and report back if I locate one.

just did a dump for you
http://code.google.com/p/cyanogen-updater/downloads/list
itl be up in a few minutes

You just need to make a yaffs2 image of the /system folder from cyan's update.zip. The boot.img is already in the zip.
Search for mkfs.yaffs2.

That nandroid backup works perfectly in my AVD 1.6 emulator. Thanks so much for building that for me. I can test all my apps against Cyan now
Thanks goldenarmz too, I'll save this away for future versions. Does this work with Hero roms as well?

pcm2a said:
Thanks goldenarmz too, I'll save this away for future versions. Does this work with Hero roms as well?
Click to expand...
Click to collapse
Yes, you can run anything on the emulator like that

I also found out that trick a few days ago. The only problem I have is that I do not get an Internet connection.
Does the SDK simulate wifi, 3G or is there just another fictive network device? I've got DroidWall and Y5 installed. Furthermore I've got sometimes problems to start my wifi after rebooting (problem by manual copied wpa_...cfg, I guess).
I am not really sure where to search. I will investigate the stuff in the paragraph above but perhaps you've got another few hints for me?
btw: I've got 4.2.13, but that shouldnt make a big difference, should it?

Anybody has found a fix for internet Issue for Cyanogen system.img file and Android SDK emulator?
Regards,
Oscar.

Replacement Friendstream from Froyo

Im running Modaco 3.1 and im very happy with it. i do however have one small issue
Im running danish version and i cannot for the life of me get the line that says when it's last updated to show 24h format
I have tested Jons Foryo 2.2 rom and the friendstream widget in that is so much better, but how do i remove the old one from modaco rom and install the new one ?
Preferably without having to recook the entire rom
an adb shell and use the command rm *FriendStream* gives the error 'Directory not empty' and then fails the removal
Any bright ideas ?
/Smirge
p.s. i do not know how to cook and resign a rom - yet, but i suppose it can be learned if i have to.

Well - past hour or 2 i have learned how to sign the zip file - easy piece of cake
But if i take the friendstram widgets from the froyo rom i had and replace those in the 2.1 Modaco rom, i don't get a widget, and if i run the FriendStream app i get a force close....so i guess it's not compatible
dang - really had hopes for this....
But on the positive side - i learned stuff from this
/Smirge

Eris Dual Boot ROM

I'm posting this in General as I don't have the knowledge to port this or develop a similar version for the Slide and I don't want to clutter up the Development forum.
Team ADX over in the Droid Eris forum came up with this gem; a dual boot Eclair Sense/2.2 AOSP ROM. http://forum.xda-developers.com/showthread.php?t=824072
I don't know if this can be done on our phones, but I thought it possible as you don't need to flash a custom recovery.

man this would awesome... the best of both worlds, run and "stock" ROM so we can still receive updates and still have CM.

i was actually thinking about dual boot just the other day! i dont feel like id be switching back and forth from 2 roms but itd be a great feature for those who do. unfortunately i dont think we have that much developers :/

I was reading the instructions for it and it looks like we'll have to wait for S-OFF before we can try it.
Part of the scripting is telling the phone how to partition the phone, sizes of those partitions, and so on. The slide is, generally speaking, un-brickable and it's the measures used to give us that luxury that also prevent us from doing so much like R/W on the system while in a non-recovery boot and changes we do make while booted are just wiped on reboot *sigh* man I love that ramdisk image.
Once we get S-OFF let's get this project started

KCRic said:
I was reading the instructions for it and it looks like we'll have to wait for S-OFF before we can try it.
Part of the scripting is telling the phone how to partition the phone, sizes of those partitions, and so on. The slide is, generally speaking, un-brickable and it's the measures used to give us that luxury that also prevent us from doing so much like R/W on the system while in a non-recovery boot and changes we do make while booted are just wiped on reboot *sigh* man I love that ramdisk image.
Once we get S-OFF let's get this project started
Click to expand...
Click to collapse
I don't think S-OFF is the issue. The partitioning instructions only refer to sdcard. This command:
Code:
mkpartfs primary fat32 0 3500 (can be adjusted to your needs. This partition will be used by the 2.1 rom and by recovery)
I think is only for the phone ROM storage and the for the recovery to find the boot scripts. According to the instructions, they're only partitioning the sdcard to run the AOSP ROM in it. They install the 2.1 Sense ROM to the phone, get it set up, run the boottosd script to boot into the 2.2 AOSP ROM on the sdcard, then set that up and run the boottophone script to go back to 2.1 Sense. They're running a ROM on the sdcard!
As I said before, I think something like this can work for our phones because it doesn't require flashing a recovery. The problem is we don't have the devs to do it.

heybobitsme said:
I don't think S-OFF is the issue. The partitioning instructions only refer to sdcard. This command:
Code:
mkpartfs primary fat32 0 3500 (can be adjusted to your needs. This partition will be used by the 2.1 rom and by recovery)
I think is only for the phone ROM storage and the for the recovery to find the boot scripts. According to the instructions, they're only partitioning the sdcard to run the AOSP ROM in it. They install the 2.1 Sense ROM to the phone, get it set up, run the boottosd script to boot into the 2.2 AOSP ROM on the sdcard, then set that up and run the boottophone script to go back to 2.1 Sense. They're running a ROM on the sdcard!
As I said before, I think something like this can work for our phones because it doesn't require flashing a recovery. The problem is we don't have the devs to do it.
Click to expand...
Click to collapse
I'll take a look. No promises as I'm an übernoob but I would love to have this.
Sent from my T-Mobile myTouch 3G Slide using XDA App

migueltherocker said:
I'll take a look. No promises as I'm an übernoob but I would love to have this.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
You won't be able to do a simple port. I posted about it more of as a proof of concept. Take the same idea, but obviously using our espresso sense and CM6.

heybobitsme said:
I don't think S-OFF is the issue. The partitioning instructions only refer to sdcard. This command:
Code:
mkpartfs primary fat32 0 3500 (can be adjusted to your needs. This partition will be used by the 2.1 rom and by recovery)
I think is only for the phone ROM storage and the for the recovery to find the boot scripts. According to the instructions, they're only partitioning the sdcard to run the AOSP ROM in it. They install the 2.1 Sense ROM to the phone, get it set up, run the boottosd script to boot into the 2.2 AOSP ROM on the sdcard, then set that up and run the boottophone script to go back to 2.1 Sense. They're running a ROM on the sdcard!
As I said before, I think something like this can work for our phones because it doesn't require flashing a recovery. The problem is we don't have the devs to do it.
Click to expand...
Click to collapse
Ok that makes sense. I thought it was pointing to the partitions on the phone telling it to format to a different size for some reason. Then what's preventing us from doing this? Just a lack of a proper script?

I have not poked around with how they are going about doing everything, but I was the one who got the ball rolling with my dual boot linux script. Conap took the basic setup and made some changes to just install them both on the phone and sdcard. Here is the basic of what it is doing....
The init.rc file found in boot.img has been modified for the froyo rom on the sdcard. The lines where it mounts [email protected] , [email protected], and [email protected] have been changed to the partitions on the sdcard (/dev/block/mcblk0px) The updater-script for froyo has been modified to flash the rom to the partitions on the sdcard. There are some gscripts which are ran from the phone that either modify or replace the boot.img for the rom you want to boot into.
The froyo ROM is running completely off the sdcard and the recovery is left untouched. The script that is required if you are using clockworks is because clockworks sbin and folder locations are setup a little different. I was running into some problems with froyo not recognizing the sdcard after making more than 4 partitions. Several had reported to me that their phones also did not recognize the sdcard, but the Eris phones somehow still did. I am working on something that should run from all android phones and allow you the option of installing whatever ROM you want.
One Last Thing..
Anyone is capable of learning how to do some development work. It just takes some patience and "Google". I had no knowledge of linux or any other scripting languages, except windows batch scripts, until 3 months ago.
There is not much activity on my thread, but once I get a working version finished it will be posted there-----Dual Boot Android

When you get it done and own working, post it in development. I only posted the thread in general because I knew I wasn't going to be the one to develop it. I'm a welder by trade and java and linux are a little beyond me. Although I am trying as I'm using Ubuntu as my main OS and starting reading java tutorials.
Sent from my CM6 Slide

heybobitsme said:
You won't be able to do a simple port. I posted about it more of as a proof of concept. Take the same idea, but obviously using our espresso sense and CM6.
Click to expand...
Click to collapse
If there was ever a reason to get a dev started on a project, this would be it. I would reconsider upgrading from the Slide if we had something this awesome.

unCoRrUpTeD said:
I was running into some problems with froyo not recognizing the sdcard after making more than 4 partitions. Several had reported to me that their phones also did not recognize the sdcard, but the Eris phones somehow still did. [/URL]
Click to expand...
Click to collapse
From what I understand, android can not *see* more than 4 partitions so they had to do something a bit different. Somewhere in the thread that's linked it states what they did to get it to work.

s off is tmobs response to....
KCRic said:
I was reading the instructions for it and it looks like we'll have to wait for S-OFF before we can try it.
Part of the scripting is telling the phone how to partition the phone, sizes of those partitions, and so on. The slide is, generally speaking, un-brickable and it's the measures used to give us that luxury that also prevent us from doing so much like R/W on the system while in a non-recovery boot and changes we do make while booted are just wiped on reboot *sigh* man I love that ramdisk image.
Once we get S-OFF let's get this project started
Click to expand...
Click to collapse
The "companies" wanted s-off due to the large number of brix getting returned for handest exchange and assurion claims, just to figure out somebody pooched sumthin up trying to be a HAXOR, if you haven't done anything like this before. Id suggest peeps get a g1 or some other root & rom-o-matic type for and play with it till you take on your brand new handset trying to install some bleenin edge hack...
You gotta learn to wank off before you can try it with somebody else in the room.
I remember my early days at xda, hacking my mda, xcaliber, and esato hacking SonyEricsson fones before they jumped the shark. People who had the ability to read and follow directions (emphasis on the read part) would study till they were sure they would still have a working fone at the end. Hung out and did great stuff with there handsets. And the noobs were wary enough to investigate before they just started mucking about.
So the handset manu. Had to do sumthin and now we have s-off.
the moral of my high and mighty rant an rave, if you don't know how to do sumthing or if you understand what to do but not the why, then keep reading, read more do less

KCRic said:
From what I understand, android can not *see* more than 4 partitions so they had to do something a bit different. Somewhere in the thread that's linked it states what they did to get it to work.
Click to expand...
Click to collapse
In the newest builds they have 2.1 system on the phones system partition and froyo system on the phones data partition. The data is moved to the SD. 2.1 and previous Rome had no problem with extra partitions on the sdcard.froyo changed the way it mounts the sdcard and could only see 4.
I am actually releasing a dual boot method very shortly that should work on any android phone with very little setup required on your part. I am in the process of finalizing it. Anyone interested in testing please let me know as I want to test on as many devices ad possible
Sent from my HERO200 using XDA App

HTC Hero GSM - Cyanogen 7.2

Cyanogen has released the 7.2 version OS for HTC Hero GSM. I've seen a lot of people talk over the CDMA version, but none on the GSM one. Has anyone tried it out? I wanna hear the bad and good remarks that you have to say about it , by "you" I mean those who have tried it.
To be sure, this is the tipe of HTC Hero I'm referring to: spinei.hotnews.ro/wp-uploads/2009/10/htc_hero.jpg

I runned it for a week or two. As for stability it's the same as CM7, CM7.2 just has some ICS backports, nothing bad

What do you mean by ruining it?
People who own the CDMA version claim that on their phone it's a performance improvement from 7.0 to 7.2.
I have 2.1 official version on it. It's stable and somewhat ok in terms of flow in the menus. Will 7.2 be an improvement over the the official 2.1 version on my phone?
P.S. I didn't test any other version of Android, it never used anything except the stock version.

cata3092 said:
What do you mean by ruining it?
People who own the CDMA version claim that on their phone it's a performance improvement from 7.0 to 7.2.
I have 2.1 official version on it. It's stable and somewhat ok in terms of flow in the menus. Will 7.2 be an improvement over the the official 2.1 version on my phone?
P.S. I didn't test any other version of Android, it never used anything except the stock version.
Click to expand...
Click to collapse
It;'s not ruined, I had it on my device for a week or two. I thing it will beat your 2.1 official. It will not have HTC Sense. You get 2.3 version of android some ICS goodies. I didnt run official 2.1 on hero so i dont know how it is

What does HTC Sense has and cyanogen 7.2 doesn't have as equivallent?
From what I saw in youtube videos, cyanogen pretty much has something almost equal to HTC Sense as GUI. Are you referring to the HTC specific apps and widgets?
P.S. I misread "runned" for "ruined" )

Yup that fancy weather widget and all that stuff, but you wont miss it trust me, that raw android look is way better

One more question.
How functional are these:
- WIFI
- Bluetooth
- Camera
- basic phone functions(calling, messages)
- sound
? Did you have any problems with these in terms of errors or functionality(loss or low of signal, automuted, etc.)? And did you had any random restarts issues?

Nope they all work awsome, it's a stable release, those releases dont have problems with that. And you shouldnt be too scared to flash your device. So far I had 4-5 android devices that are rooted and flashed a million times without any losses, you may encounter a soft brick sometimes but you can fix that easily. You cant know how good is a ROM until you test it. So stop being a girl and flash it . No offence If you dont like it, there is a lot more ROM's on this forum, you dont have to choose CM7.2....

First time to install Cyanogenmod was not entirely easy
Hey all,
I just created an account to be able to post my experience with CGM 7.2 on the HTC Hero GSM. Everything I checked so far works fine, however there's a slight jaggedness in scrolling.
For me as a complete newbie it took about 6 hours to get it to run, mainly because I had to get straight what I actually have to do. There is no paucity of TO-DOs, just no individual one worked for me - I got it sorted out only by combining all kinds of posts from everywhere. That's why I want to share my viewpoint on this - without all kinds of different people airing their piece of the puzzle I would surely have given up!
The specs were as follows; starting with the "fastboot-info":
HERO CVT SHIP S-ON
HBOOT-1.76.0007 (HERO10000)
MICROP-010f
TOUCH PANEL-SYN0104
RADIO-6.35.15.11
Aug 4 2009,19:43:30
And software-information:
Firmware-Version 2.1-update1
Baseband-Version 63.18.55.06PU_6.35.15.11
Kernel-Version 2.6.29-7527f009 [email protected] #1
Build-Nummer 3.36.405.1 CL199109 release-keys
Software-Nummer 3.36.405.1
Browser-Version WebKit 3.1
So here's what I did:
0) I wrongly assumed that I need to unlock my bootloader directly, i.e. using the software from HTCDev. As I am using Ubuntu Linux, this meant quite a hassle in itself, and I did not manage it after all. The reason was due to an error when trying to get the Identifier Token needed by HTC to send you some clearance-file to unlock the bootloader:
Code:
fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.007s
I found no solution to this problem, but tried to up- or downgrade my HBOOT-version. Luckily that wasn't necessary after all. A side-effect of it was that I installed adb and fastboot, which I happened to use later on (but are not necessary either).
Let me assure you: Unlocking the bootloader directly (in the HTC-way) is NOT necessary!
1) Getting root access:
I used UniversalAndroot-1.6.2-beta5.apk to do that, and conveniently installed it using
Code:
adb push, adb install
though if you don't want to install this nice utility, you can just install a File Browser and then install the package.
Now here's a quirk that cost me about an hour: Using the default settings, UniversalAndroot only claimed to successfully get root-access, but left everything unchanged! Only after finding a comment on some website did I try to check both check-boxes (log and temporary install) - this time it worked (it installs yet another app called SuperUser)! (I then ran it again without the temporary setting enabled, which at least did not revoke the SuperUser-Account). Anyways, adb is handy in this case again because you can just log in with
Code:
adb shell
and check if
Code:
su
gives you root access or says "Permission denied".
2) Deleting /system/etc/install-recovery.sh I got that idea from androidforums.com, and will probably never know whether it was really necessary. That just shows how desperate I became after 3 hours of poking around in the dark.
3) Installing ROM Manager from Google Market There's probably a quicker way to install recovery images, which does not involve a damn Google account! Or maybe it is not even neccesary.
4) Downloading and installing ClockWorkMod Recovery I did this using the ROM Manager. Again, there might be a more direct way. In any case, I was paranoid enough to install it twice, as it was recommended that way somewhere.
5) Downloading cm-7.2.0-hero.zip and putting it on /sdcard/ Again, I just used
Code:
adb push cm-7.2.0-hero.zip /sdcard/
to accomplish this, but my guess is you can just as well do it via USB.
6) Format cache, /data/factory, /boot and /system By that, I mean do this in ClockWorkMod (you get there by booting up with HOME+POWER). The last two locations to reformat are "hidden" in the menu partitions. This step is very important because without it, Cyanogenmod did only loop infinitely (for more than 10min) in its loading screen! I got this idea from the more detailed description at droidforums.
7) Install Cyanogenmod using ClockWorkMod That's straight forward; just select the image from sdcard and you're done!
Hope I didn't forget a vital step, and maybe it is helpful to somebody; at the very least my future ME will maybe find it useful again .