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.
For:
USA MyTouch 3g 32B (Possibly Others, would need help specifying)
SAPPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.0006 (SAPP30000)
CPLD-10
RADIO-2.22.19.26I
(This is just my experience and the way I've interpreted things I've read.)
Lessons Learned:
I assumed Swappyness, Swap, 10MB Hack, compcahe etc all came up and running on most roms. I would flash them and still, things were SLLLOOWWW.
I found out about user.conf etc. These need to be pushed to the OS to work. (I know compcache is included in builds, but I never really felt it was doing anything, possibly not starting correctly)
10MB hack gets over-written sometimes when I am hacking and flashin' all these different roms.
Cyanogen Recovery "Wipe" wasn't really clearing out things like I thought it would.
Recreating Partitions in ADB Shell were most likely unsuccessful because of user error, unix newb.
Getting Amon Ra's Recovery on was a pain to read about. Nothing seemed catered to my situation. I couldn't get clarification on Radio/SPL etc.
Notes:
I'm a 'new guy' like many other readers here. I'm just trying to help out someone that may have been in the same position as me. Steps in this guide may not make sense to the "Pro's" but I'm not a pro and am learning that decernment myself.
I'm sure I've configured something in such a way that isn't "Best Practice" but I will boldly state that after performing the steps listed below, my phone became fun and snappy again.
I take no credit for anything listed here other then the time I spent writing this compilation. Props to the developers noted in the referenced links.
This Guide is Applicable to:
USA MyTouch 3g 32B (Possibly Others, would need help specifying)
SAPPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.0006 (SAPP30000)
CPLD-10
RADIO-2.22.19.26I
Tested on ROM:
Super D Rom 1.5.1 [STABLE]
http://forum.xda-developers.com/showthread.php?t=613809
CyanogenMod 4.2.13
http://forum.xda-developers.com/showthread.php?t=567610
Files Needed:
recovery-RA-sapphire-v1.5.2H.img
http://www.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=recovery-RA-sapphire-v1.5.2G.img
From: http://forum.xda-developers.com/showpost.php?p=4029315&postcount=1
COC10 build of Cupcake from
http://www.megaupload.com/?d=BLM4EDGE (sappimg.nbh)
md5sum: 33d958062cc02bb2cec157f68621d2ff
FlashRec from
http://g1files.webs.com/Zinx/flashrec-20090815.apk
md5sum: 7e3f43760783348c02130f26e25df486
After Downloading, rename to .apk so the app installer can see it.
Configuration Steps:
From CyanogenMod's Wiki And PSGuardian "[How-To] Flash Your MT3G/Magic/Sapphire {32A/32B} w/ CM 4.2.13 + Amon RA Rec v1.5.2" http://forum.xda-developers.com/showthread.php?t=579328 -- I Just found this guide and it does cover some of the things I am but It does differ in some areas.
1. Format your SD card to FAT32
* Windows: Right-click on SD icon and select format
* Mac users: Start Disk Utility, Partition the card
* Linux: Use gparted (it's in the repositories of your favorite distro)
2. Copy the COC10 build (sappimg.nbh) file (and no others!!) to your SD card.
3. Shut down your phone.
4. Reboot into fastboot by holding Volume Down + Power (you should see three Androids on skateboards)
5. Follow the on-screen instructions to flash the image. On some handsets it may require pressing the action button (trackball), while on others it may require pressing the power button.
* If you get an error saying "Main version is older" or "Incorrect Model ID" you'll need to create a goldcard. Follow goldcard instructions and the continue with the next step.
6. Reboot when phone is done updating. You now have the one-click vulnerable version of the firmware.
7. Connect phone to pc via USB
On the phone: pull down the notification bar & press ->USB Connected->Mount
8. On the pc:
Erase sappimg.nbh from your SD card.
Copy the FlashRec.apk & the Amon RA recovery.img onto your SD card.
If you don’t have a ‘file manager’ or ‘app manager’ go to the market & download one such as: ASTRO, LINDA, AppManager or the like. Then browse to your SD card & open/run the flashrec.apk to install it. (if asked what to open with choose Package Installer)
9. Open RecoveryFlash (flashrec) & make a backup of your current recovery.img. Flashrec just made "recovery-backup.img" on the root of your SDcard, so now rename Amon Ra's recovery to "recovery-backup.img" (choose replace when the dulpicate file name message appears) then open flashrec again & choose restore recovery. (Credit for this step goes to deb82swearingen Much easier then the orig method I was shone for using flashrec)
Once the flash is complete turn the phone off.
Boot into 'Recovery' like this: Press-&-Hold END/Power AND Pres-&-Hold Home. (this will be a black background with green text options)
Scroll down to ‘partition’ (press trackball to select)->partition SD->follow onscreen steps (HOME=confirm, VOL +/- changes partition size, any other key=cancel).
10. Go BACK until top says "Android system recovery" ->Connect phone to pc & scroll to 'USB-MS toggle'->HOME to confirm.
11. Copy the Super D Rom 1.5.1 [STABLE] ROM .ZIP or CyanogenMod Rom, or whatever rom your wanting to use, onto your SD card then close the SD card folder on your PC & toggle USB-MS again, then disconnect from the pc.
Scroll to & select ‘wipe'
Wipe data partition
Wipe Data/factory reset
Wipe Devlik-cache
Wipe SD:ext partition
Scroll to & select ‘Flash zip from sdcard.
choose rom image filename and posh "Home" to confirm.
Be patient. DO NOT REBOOT!
When completed select "Reboot System Now"
You now have AmonRA Image recovery and your rom loaded.
**************************************
Time to speed up your rom.
10MB hack
Taken from: http://forum.xda-developers.com/showthread.php?t=566410
[MOD] 10MB RAM Increase kernels/boot.img for Dream and Magic 32B[01/13]
Boot.Img file: http://www.sendspace.com/file/9dvmvi
Put on SD card root
Unmount sd card from phone
C:\android-sdk_r04-windows\android-sdk-windows\tools>adb devices
*Confirm device is listed
C:\android-sdk_r04-windows\android-sdk-windows\tools>adb shell
# mount -o remount,rw /dev/block/mtdblock3 /system
mount -o remount,rw /dev/block/mtdblock3 /system
# flash_image boot /sdcard/boot.img
flash_image boot /sdcard/boot.img
# flash_image boot /sdcard/boot.img
flash_image boot /sdcard/boot.img
# reboot
reboot
reboot returned
#
C:\android-sdk_r04-windows\android-sdk-windows\tools>
After reboot: (Confirm new Mem total: ~107324)
C:\android-sdk_r04-windows\android-sdk-windows\tools>adb shell
# free
free
total used free shared buffers
Mem: 107324 104376 2948 0 8
Swap: 32760 11148 21612
Total: 140084 115524 24560
#
*****************************************
Setup Swap manually.
From:
http://forum.xda-developers.com/showthread.php?t=542899
[MOD]user configurable userinit.sh V0.1.5.3 for CM. [UPDATED 9/05]
Copy attached userinit.zip files,user.conf and userinit.sh to SD card root.
Install using ADB:
*Turn Off USB Storage
C:\android-sdk_r04-windows\android-sdk-windows\tools>adb devices
*Confirm device is listed
C:\android-sdk_r04-windows\android-sdk-windows\tools>adb shell
# mount -o remount,rw /dev/block/mtdblock3 /system
mount -o remount,rw /dev/block/mtdblock3 /system
# cp /sdcard/userinit.sh /system/sd
cp /sdcard/userinit.sh /system/sd
# cp /sdcard/user.conf /system/sd
cp /sdcard/user.conf /system/sd
# chmod 755 /system/sd/user.conf
chmod 755 /system/sd/user.conf
# chmod 755 /system/sd/userinit.sh
chmod 755 /system/sd/userinit.sh
# reboot
reboot
reboot returned
#
C:\android-sdk_r04-windows\android-sdk-windows\tools>
*****************************************
After reboot, execute userinit.sh shell script.
C:\android-sdk_r04-windows\android-sdk-windows\tools>adb shell
# sh /system/sd/userinit.sh -s
sh /system/sd/userinit.sh -s
=== user.conf ===
*** CompCache ***
compcache_en=0
cc_memlimit=18
cc_disksize=96
cc_backingswap_en=0
cc_backingswap=/dev/block/mmcblk0p3
cc_swappiness=60
*** Swap File ***
swap_file_en=0
linux_swap_file_size=0
linux_swap_file=/system/sd/swap.file
*** Linux Swap ***
linux_swap_en=1
linux_swap_partition=/dev/block/mmcblk0p3
swappiness=30
*** VM ***
sys_vm_en=0
page_cluster=0
laptop_mode=0
dirty_expire_centisecs=3000
dirty_writeback_centisecs=500
dirty_background_ratio=5
dirty_ratio=10
*** CPU ***
proc_cpu_en=1
scaling_min_freq=384000
scaling_max_freq=528000
sampling_rate=2000000
powersave_bias=0
up_threshold=25
=== Linux Swap status ===
Linux SWAP enabled on /dev/block/mmcblk0p3
Linux Swap: swappiness - 30(system) 30(user)
=== CPU status ===
Set CPU: scaling_min_freq - 384000(system) 384000(user)
Set CPU: scaling_max_freq - 528000(system) 528000(user)
Set CPU: sampling_rate - 2000000(system) 2000000(user)
Set CPU: powersave_bias - 0(system) 0(user)
Set CPU: up_threshold - 25(system) 25(user)
# reboot
reboot
reboot returned
#
C:\android-sdk_r04-windows\android-sdk-windows\tools>
*****************************
I'm sure there are plenty of things that can be tweaked, done differently but this worked for me.
Will add pretty formatting etc if the post becomes beneficial or used by anyone.
Hope it's helpful to atleast somebody.
Works for me
Hi, I hace follow the steps, basically the 10mb hack and the setup of Swap manually is the really increase of speed. Thanks for this guide.
Great guide, thanks for this. A couple of things,
If you had already done all of this (10MB hack, swappiness, compache etc) and you said it still didn't increase the speed of your phone, are you saying that you had to wipe your phone and the dalvik cache, start from scratch and then reapply the 10MB hack + swap partitions? Is the wipe and starting over from scratch the thing that fixed everything for you? How long has your phone been "snappy/speedy"? I've followed all of these steps but not from a full wipe/restart and I have mixed results. Sometimes its snappy (usually after killing all running apps) and minutes later it goes back to very sluggish. It seems as if I don't use the phone for a while and then unlock the screen, it needs to "wake up" to pick up some speed and even then when the screen responds (when trying to swipe home screen) it sometimes is still laggy.
Btw, CM 4.2.13 absolutely murdered my phone with bugs, the kind that make the phone unusable although I did notice a slight speed increase. I didn't use it long enough to notice if it slowed down over time. Had to roll back to sluggish 4.2.11.1 as its the one that was most stable for me.
Let me know your thoughts.
Quiketaz said:
Hi, I hace follow the steps, basically the 10mb hack and the setup of Swap manually is the really increase of speed. Thanks for this guide.
Click to expand...
Click to collapse
Glad it helped!
Gusjdt said:
Great guide, thanks for this. A couple of things,
If you had already done all of this (10MB hack, swappiness, compache etc) and you said it still didn't increase the speed of your phone, are you saying that you had to wipe your phone and the dalvik cache, start from scratch and then reapply the 10MB hack + swap partitions? Is the wipe and starting over from scratch the thing that fixed everything for you? How long has your phone been "snappy/speedy"? I've followed all of these steps but not from a full wipe/restart
Btw, CM 4.2.13 absolutely murdered my phone with bugs, the kind that make the phone unusable although I did notice a slight speed increase. I didn't use it long enough to notice if it slowed down over time. Had to roll back to sluggish 4.2.11.1 as its the one that was most stable for me.
Let me know your thoughts.
Click to expand...
Click to collapse
Yeah, I had heard so issues with 4.2.13 so it was a version I wanted to test this process on specifically. It ran okay for me.
As for your other questions;
I can't say 100% which step fixed my problem. I simply didn't have enough time to reproduce specific scenarios and test accordingly. I took a blanket approach and just started from scratch.
I suspect I may have had something not correct on my SD card partitions and the Amon RA recovery was what I know I wanted as it automated the creation of it.
I have tried just redoing the 10mb hack on sluggish roms, but that did not help.
I completely know what you mean about after the phone hasn't had use, or waking up. This is part of the same bad behavior I was seeing. My process fixed that.
It has been snappy for 3 days now and I intentionally haven't killed any tasks as I'm testing that out. I'm quite amazed still.
I would say if things still aren't happy for you, backup that SD card and start from scratch.
GL!
Hmm, I'll wipe and start from scratch then. I'll report back soon to see if its made any difference. The fact that your phone has run "snappy" for 3 days straight without task killing gives me hope. One thing, did 4.2.13 run fine for you as soon you finished installing the ROM or did you have to update the Contacts.apk or do any other tweaks aparts from the ones you mentioned in the guide?
Thanks again
Gusjdt said:
..did 4.2.13 run fine for you as soon you finished installing the ROM or did you have to update the Contacts.apk or do any other tweaks aparts from the ones you mentioned in the guide?
Thanks again
Click to expand...
Click to collapse
Yes, it ran fine and I didn't update contacts.apk or tweak anything additional.
I hope to hear back from you with good news.
Just wiped everything except battery, repartitioned and upgraded to ext4, repaired ext, rebooted and as soon as it gets to the page where it asks for the google mail sign in (at the very beginning, touch the android to begin etc) I get this error:
SORRY! The process com.google.process.gapps hast stopped unexpectedly. Please try again.
I ignored it since clicking force close didnt seem to do anything, but now its popping up every 15 seconds or so over and over again. Cant download any apps from market (they just hang there on "starting to download).
Will re-wipe and try again...
Btw, this is with CM 4.2.13 and I can confirm long-press and call button dont cause any errors/crash so thats good... I think.
err, now that you mention It I think I may have seen that error aswell, but it didn't keep popping up on me.
Was it performing any faster? Sounds like possibly reverting to a previous CM build might be a good idea.
Also, and I'm not trying to twist your arm, nor do I understand all your needs around running CM but I might recommend:
Super D Rom 1.5.1 [STABLE]
http://forum.xda-developers.com/showthread.php?t=613809
I am absolutely in love with this rom over anything I've seen out of CM.
It was performing faster, but thats to be expected after a wipe.
I wiped again except rotate settings and I did not repartition after installing 4.2.13 again. Booted and got the same damn error. Will wipe one more time for 4.2.13 and if it happens again I'm staying on 4.2.11.1
If it happens again on 4.2.11.1 I might just blend the phone.
Could the CM ROM .zip file be bad and thats what may cause this error? Maybe I should redownload the ROM. How do I check the md5sum on a zip file?
Bingo, I found the problem. Apparently I was using an older version of the 1.6 base rom. I used the defanged base rom and the error stopped. I can now download apps fine too.
http://wiki.cyanogenmod.com/index.php/Upgrading_From_Older_CyanogenMod_or_other_rooted_ROMs
No problems with contacts app, long-touch or the call button causing force close issues. I can make calls fine as well. During application backups using MyBackup Pro (excellent app), the installs were going fast as ****, which never happened to me before. It would really slow down the phone.
Restored Data, rebooted (which is actually quite fast now) and although the home screen took a little longer to load my icons/widgets, everything is running smooth. Even the power manager widget reacts super fast when I press on the buttons. Brightness changing is instantaneous. Home screen responds quickly, no lags in touch responsiveness... and I don't even have swap OR compcache enabled OR the 10MB memhack.
FINALLY.
So it looks like the base rom was the issue, at least for me.
Excellent to hear, I love that feeling of, "YES!"
Sigh... same problems came back again. Tried messing around with swap settings but that didn't help. Looks like I'm done with this, I'll just suck it up wait for the 2.1 OTA...
For the love of God someone please make this a sticky!
Great thread.
Wow Stokes, Thanks! Glad to have a senior users opinion!
*sigh* good guide to a limit... there's been quite a few of these i've read, but it all comes down to one thing... every mytouch is different. you might use 96mb swap on 60 swappiness and it works amazing, however it might slow mine down horribly. you have to try and try and try to find your sweet spot. also, compcache is overrated. horribly. its a good concept, but with tests ive read and done on my own; compcache just doesn't match up to your good ol fashioned swap. 2:51 am im tired would write more and provide links but its almost bed time, plus i have to get another thread talking about ext3s on mytouch.... why people, why? YOU DON'T NEED APPS2SD ON MYTOUCH. it has plenty, and i mean plenty of internal space for your apps. you're just wasting your sdcard.
blah edit: unless the rom you use specifically calls for ext partition. running cyanogen and most others, hell no. hero roms and random others, yea. but in my experience, the best ones i've ever came across are cyanogen and dwang. dwang if you want pure speed and don't need all the extra stuff you'll probably use once if at all, and cyanogen if you want a pimp phone that does damn near everything.
r3s-rt said:
every mytouch is different. you might use 96mb swap on 60 swappiness and it works amazing, however it might slow mine down horribly. you have to try and try and try to find your sweet spot.
Click to expand...
Click to collapse
Of coarse different hardware requires different settings. Hence why this guide specifically says what hardware it is for.
Specifically:
For:
USA MyTouch 3g 32B (Possibly Others, would need help specifying)
SAPPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.0006 (SAPP30000)
CPLD-10
RADIO-2.22.19.26I
It was not meant to be a blanket approach to fixing every phone.
no. EVERY mytouch requires different settings. i may have the EXACT same phone as you in every way possible, and you can run a different swap, swappiness, and swap size. every "speed" guide is just more of a guideline... im not saying you're wrong in any way, or you're not helping. i know it took time to put it together, and people like you are the reason i enjoy having a mytouch or any android for that matter. im just saying this before someone comes along and complains how they used it and their phones slow and calls you a n33b.
and im saying this because i've herd it alot. from alot of different speed guides. also, on top of that, i've herd it universally. with torrent programs and the such. i don't know why this is, but i've herd it multiple multiple times. i mean, i may be wrong. but i did my research because i was and still am quite dissatisfied with the speed of things and i've read speed guides all over comparing swaps, roms, and just about everything that can boost the speed of your phone, and that statement always comes up.
but like i said, i'm not downing your guide. its well thought out and nicely organized (something i'll never be able to do, lol.)
oh yea, one more thing... the *sigh* was for the ext3 partition, not your guide. i hate hearing about them on mytouches. :|
edit again: i don't even know if there's anything about ext partitions on this thread, it was like 3:00am on that first post and i was trying to read like 5 threads at once. :s
So far so good...
Wow! So far so good! I'm exactly the person who needed this, so a big thanks. I've meen using winmo for years, and am encountering the steep learning curve to mod android devices.
FYI I already had installed the latest Cyanogen ROM 4.2.13 and did not have my SD card partitioned. I did not go through all the steps of a fresh ROM install, but just started by partitioning my SD card then going through the steps from there. I can say that having only been running it now for about 10 minutes, it's impressive. The main reason I was doing this was because I was getting a RIDICULOUS delay in my dialer. Any time I hit the green button it would take up to 10 seconds for the dialer to open. Now it's much much faster. Looking forward to seeing if it will bog down or stay quick. Will report back.
Thanks for the guide. A++
Tim
I've been searching both google, and the xda forums all day trying to find a solution for this problem. I want to test certain functionalities of ROMS in the emulator. The problem is that I'm unable to get past the bootscreen animation on any ROM.
All the guides I've found are for Roms based on 1.5 and earlier.
My method thus far has been to nandroid backup my system, paste the system.img into a copy of the 2.1 API folder located in "platforms".
It's obviously trying to load the system, because it's showing the custom boot sequence, but fails at some point and goes into a loop.
Thus far, I've tried upping the RAM, Cache, and heap limit of the emulator, but to no avail.
So, I'm fairly new to Android myself and am still learning things daily. My first two thoughts are:
1) Aren't there some drivers in the system.img that are going to be device specific? So, you'll have to swap out the Eris stuff and insert some 'goldfish' drivers or whatever they call the emulated arch?
2) Logcat is your friend. Logcat it while it's booting up. That should give you some clues.
3) If you figure this out, please post the steps so that anyone else who wants to do the same will not have to start from scratch.
4) Isn't this fun?
gnarlyc
Indeed, will logcat it tonight and see what I can find through that.
I was looking for a way to make custom rom running in the emulator.anyone got a working 2.1 rom for emulator?
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 .