I have been a happy 32A user for awhile now, trying virtually every ROM that came out, and never had a problem. Get a 32B rom, drop a 32A kernel pack on it (thanks to the fine people who do the Cyanogen port typically) and everything works awesome.
There are a couple eclair roms that this doesn't work for. Its been about 50-50. I'm trying to get King's and Hervers ROM's on my 32A, but they both error out immediately with:
I//system/xbin/busybox( 48): run-parts: /system/etc/init.d: No such file or directory
I/logwrapper( 48): /system/xbin/busybox terminated by exit(0)
Obviously they are using Busybox to do the init, busybox is calling run-parts, and its looking for init.d which doesn't exist. I get all that. I've looked thru the original roms, and I don't see an init.d in the originals either, so i'm frustrated at this point.
Can someone give me a clue or point me in the right direction on what I need to do to get these ported? Any help would really be appreciated. I'm currently running manup's 2.0.1, but I'd love to be able to try these others out.
-- Solution if anyone cares: --
It wasn't exactly rocket science; I found a couple eclair ROMs that worked on 32A. They had the /system/etc/init.d directory in them. They were basically identical. Took that directory from the working ROMs and put it in the unworking ROMs, and now they work.
What I don't understand is how anyones getting them to work as distributed (they obviously do). The kernel (as far as I know) shouldn't make a difference in how the ROM boots.
If anyone can clear that up for me, i'd appreciate it.
Related
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!
Ok, I'm sorry if this has been asked already (or is too obvious to have been asked), but I'm having problems with my phone after rooting it and I'd like to get it fixed if possible.
Basically, I rooted my phone and flashed Cyanogen. Everything works perfectly by the accelerometer and compass, which are both completely kaput it seems.
I've tried the method in Cyanogen's FAQ (the one involving restore and deleting two files), but one of the two sets of files that he asks to delete doesn't exist.
I've already tried performing multiple wipes and reinstalls of different roms (Including Cyanogen, JF's, even the original T-mobile mytouch rom) to no avail. I even flashed back to JF's 1.5 since some people said their problems started with the 1.51 update.
Now I'm back on Cyanogen since it's my favorite so far and it seems that the problem follows me no matter what.
Now it seems that my only choice as determined by this thread is to port in some files from JF's 1.42 and delete the Cyanogen version. I have no idea if this will work since these guys are obviously on G1's and I'm using a mytouch, but I figure it shouldn't hurt too much as long as I can still get to the recovery console if something goes crazy.
This is the method given:
reboot recovery
mount /system
rm /system/bin/akmd
mount /sdcard
cp /sdcard/jf1.43_akmd /system/bin/akmd
Click to expand...
Click to collapse
And I understand every single bit of it but the part where he copies the jf1.43 akmd to bin because I can't seem to get my hands on that single file.
Here's the actual question in case you want to skip all of that crap.
How do I extract the particular file that i need (akmd from JF's 1.42) from the .img file that I downloaded. Is there a particular method, or am I just downloading the incorrect package?
Furthermore, if you have any other possible solutions to my problem, I'd be glad to hear them. I'm pretty much shooting in the dark here since the first time I even looked into the system was yesterday when it was rooted.
Ok I found the perl script that I needed and ran it to extract the image. Now I'm looking for the file.
Oh my god. I'm an idiot. Opened the file in Linux and everything showed up. I think I might've had hidden files not showing.
Sorry for the stupid question, hah.
Edit: No luck. Am I really the only one who got a broken accelerometer from rooting?
Edit2: For someone who usually picks up on stuff like this quickly, I'm an idiot. For some reason every problem crossed my mind but the fact that I was using a rom that was not specifically made for the MyTouch. I flashed with the modded Cyanogen rom and the accelerometer works again.
You can delete this thread if you'd like mods.
Would like to try out a full Hero ROM for a mytouch 32b that does not utilize apps2sd... Its something I would like to try, as other ROM's that I"ve used on the mytouch that give you a choice to not use apps2sd are significantly faster from my experience
I am doing this right now with the JACxHero 1.4 that just got posted. I used the instructions given in this post - http://forum.xda-developers.com/showpost.php?p=4353332&postcount=68
thanks for the link... i'll give it a go and post my opinions in a day or two of testing... from your experience does it help lag issues at all?
how did you go about editing the a2sd file when you run the "vi a2sd" command... i'm using a plain old windows command prompt to use adb shell, and it only gives me a partial amount of the file and does not let me edit... i tried pulling the file from the phone and replacing it after editing it through wordpad, but that just crashes the phone on the splash screen... i've tried on 3 different ROMs, including jacxhero 1.4 for 32b and all the same results...
Hello,
so, hello to everybody, im new in this board and the whole android thing. i bought a htc wildfire last week and i spent almost the whole evening, rooting it, putting a new kernel on it and a new software...
so here we go, i have:
- Rooted with unrevoked3
- installed OC-Kernel-2.6.32_v2
- installed OpenFire_V_2_2_1
So now im stuck at Metamorph... I successfully installed Busybox with the App out of the Market. It says 8500kb in my /system directory are free, i think thats enough for the metamorph app... dont know how to delete any files, i dont have anything loaded manually onto the device...
But everytime i start metamorph, it keeps telling me, that my /system doesnt have enough space...
im out of luck, so now i need your help, please remember, im a newbie
with kind regards
drippin-water
Its probably that you need system read / write. I haven't had any joy with it either. Waiting for s-off full root.
Yeah thats most likely it. There should be support for AUFS overlay in CM6 but i have yet to manage getting it working.
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 .