Damage my accelerometer I think :( - G1 Q&A, Help & Troubleshooting

Dropped my phone to carpet, about 2 ft drop but now the accelerometer acts all funky, is there a way to calibrate it? or fix it?
Thanks

The suggested calibration for the accelerometer is to open an application that uses it, hold the phone in front of you and make kind of a figure 8 pattern with your wrist.
It has worked for me a few times but not because i've dropped it, it just gets "stuck" sometimes.
Hope that helps.

I had a similar issue where the accelerometer randomly stops working properly. I was about to call T-Mobile for a replacement phone but I tried doing a factory reset and it started working again.

A 2 ft drop to carpet probably didn't damage anything. How is it acting funky? If it's "stuck" you can smack it against the top of your hand.

It leans way to the right, I have tried bubble, labyrinth and pappijump, it's the same for all three apps
Thanks

shake shake baby
Hi, this has happened to me on occasion. I just shook the thing really hard vertically up and down.
job done

install and start the tricorder-app from the market and look whats going on.
will not realy help, but maybe shows you some funny stuff ^^

neiko69 said:
Hi, this has happened to me on occasion. I just shook the thing really hard vertically up and down.
job done
Click to expand...
Click to collapse
I know this is what Nintendo recommends when Wii controllers are acting weirdly. Just smack the phone against your hand a few times (of course, try at your own risk). Can't get any worse.

I got same problem ,..just with the dif that the keybord to haz problems now.. i don get light on the keys (( any1 there that knows if i can fix it?

I had the problem where the accelerometer did not work at all anymore. A wipe helped, but since I did not want to lose all my data, I figured out, how to do it without wiping:
1. Do a backup of your data (nandroid is best)
2. Reboot your phone to recovery console (home+power)
3. Enter recovery console
4. mount /data
5. Delete *.dex in /data/dalvik-cache
6. Reboot and wait (reboot takes longer this time)
If this doesn't fix it for you:
All steps above apply, but in step 5 delete/move/rename the file /data/misc/akmd_set.txt (also in recovery console). It will be recreated. Can't tell you if this fixed it or not, because I did both things at the same time. Sorry ;-)
DON'T try this while NOT in the recovery console! You will lose space on the /data partition because of a bug!! ONLY do this in the recovery console where no system is running.

Thanks! The second one worked for me.

dicer42 said:
I had the problem where the accelerometer did not work at all anymore. A wipe helped, but since I did not want to lose all my data, I figured out, how to do it without wiping:
1. Do a backup of your data (nandroid is best)
2. Reboot your phone to recovery console (home+power)
3. Enter recovery console
4. mount /data
5. Delete *.dex in /data/dalvik-cache
6. Reboot and wait (reboot takes longer this time)
If this doesn't fix it for you:
All steps above apply, but in step 5 delete/move/rename the file /data/misc/akmd_set.txt (also in recovery console). It will be recreated. Can't tell you if this fixed it or not, because I did both things at the same time. Sorry ;-)
DON'T try this while NOT in the recovery console! You will lose space on the /data partition because of a bug!! ONLY do this in the recovery console where no system is running.
Click to expand...
Click to collapse
Can you post more in depth instuctions on doing this? Please?

I only tried this with a JF image. You definitely need root to do this.
1. Turn your phone off
2. Hold Home/House button and press red power button. Release red then home button
3. G1 should boot with lots of text into a menu
4. Press Alt+b to backup everything (optional)
5. Then Alt+x to boot into a console (press enter when prompted)
6. type "mount data" + enter
7. type "rm data/misc/akmd_set.txt" + enter
8. type "reboot" plus enter to reboot
9. Have fun with accelerometer again
More detailed than this is not possible. Hope this helps

That is more info than I needed but I'm sure if will help others, Thank you Dicer

dicer42 said:
I only tried this with a JF image. You definitely need root to do this.
1. Turn your phone off
2. Hold Home/House button and press red power button. Release red then home button
3. G1 should boot with lots of text into a menu
4. Press Alt+b to backup everything (optional)
5. Then Alt+x to boot into a console (press enter when prompted)
6. type "mount data" + enter
7. type "rm data/misc/akmd_set.txt" + enter
8. type "reboot" plus enter to reboot
9. Have fun with accelerometer again
More detailed than this is not possible. Hope this helps
Click to expand...
Click to collapse
Thanks, worked a treat

appstosd
Hi,
What would be the command line for appstosd? I ve tried your instructions but I ve got nothing in data folder because of appstosd. Please help

For apps2sd you probably need to mount /system/sd and delete the file off there.
6. type "mount /system/sd" + enter
7. type "rm /system/sd/data/misc/akmd_set.txt" + enter
Haven't tried it though. Let us know if it works.

follow as above and yeah! working again...after trying for so long to recover....haha feel so good.....

mine stopped working and i wiped myphone and it worked again. =D

Is this a possiple way to fix the calibration issue on rosie? It aborts, so maybe it was looking is the wrong spot to rewrite the file

Related

G1 wont turn on HELP!!

Ok, I did an SPL update, it rebooted, I pulled battery, and then I was all set to put a new build on the phone. I put battery back in, and then nothing.. pressing power - nothing. Pressing pwr-home - nothing
when I plug it in, the charge light doesnt even come on..
please help guys...
...hhhh Probably in relative to the other problems people are having. You read to find that file, now read to see your not the only one. Sorry there isnt no fix yet.
joey3002 said:
Ok, I did an SPL update, it rebooted, I pulled battery, and then I was all set to put a new build on the phone. I put battery back in, and then nothing.. pressing power - nothing. Pressing pwr-home - nothing
when I plug it in, the charge light doesnt even come on..
please help guys...
Click to expand...
Click to collapse
why are people pulling the battery? there is no need to pull the battery.
here is how a flashing procedure should go:
1. Download spl-update.zip, place on phone as update.zip
2. Turn off device, go into recovery mode (HOME+POWER)
3. ALT+W to wipe, and ALT+S to update the SPL
4. WAIT until it completes. (It will ask you to press "HOME+BACK" to reboot).
5. press HOME+BACK
6. DO NOT TOUCH THE DEVICE ANYMORE
6. It will quickly spit out "Writing hboot.." then reboot and you will see a chip and an arrow facing up (image attached), it will reboot again, and boot you into recovery mode.
If you do NOT get taken into recovery mode, your phone is bricked..
If you are taken back into recovery mode, you are successful. Proceed.
7.
Code:
adb shell mount /sdcard
adb shell rm /sdcard/update.zip
adb push 6.0-signed.zip /sdcard/update.zip
8. Press ALT+W followed by ALT+S.
9. LET IT COMPLETE (you will be prompted to press "HOME+BACK")
10. press HOME+BACK
11. enjoy.

the quickest way to switch from jf 1.51 to the new CyanogenMod

Is their a really quick way to switch from the jf mod the CyanogenMod, because jesusfreke
Stopped updating the jf rom line permantely, I'm not sure if I have the recovery.img
Installed correctly, sorry if I don't make sense I'm a little new to this.
Make sure you are fully charged, and or have the G1 plugged in before starting.
1. Download and install MyBackup from the Market.
2. Backup all your call logs,contacts,sms,mms,applications,bookmarks, and ak notepad do not backup system settings, homescreen shortcuts.
3. Download and put this on the root of your sdcard: http://n0rp.chemlab.org/android/cm-recovery-1.4.img
4. Open up terminal, and type su.
5. cd /sdcard
6. flash_image recovery ./cm-recovery-1.4.img
7. type exit twice to exit out of the terminal application.
8. Download and put this on the root of your sdcard: http://n0rp.chemlab.org/android/update-cm-4.0.2-signed.zip
9. Download: ota-radio-2_22_19_26I.zip and put this on the root of your sdcard from: http://www.htc.com/www/support/android/adp.html#s3 or you can download it from: http://sapphire-port-dream.googlecode.com/files/ota-radio-2_22_19_26I.zip
10. Reboot the phone. When you get to a black screen (just before the G1 logo) hold down home + power. Keep pressed until you see the recovery screen.
11. Select wipe menu option (with trackball), then confirm it with home key (when it asks you to).
12. Select flash any update, select update-cm-4.0.2-signed.zip, then press home to confirm. Wait until the flash finishes.
13. Select reboot option (itll be highlighted once flashing is done).
14. Once it reboots, and you get to a black screen, hold down camera and power. When you get to the skating android or tri-colored boot screen (depending on which SPL (hard/engineering/stock) you have) take note of the radio version. If you don't have radio: 2.22.19.26I, hit call-menu-end, hold down power + home, keep it pressed until you get to the recovery. Select flash any update, and select ota-radio-2_22_19_26I.zip and confirm with home when it asks you to. When it finishes it will ask you to reboot. Click reboot option. It will then reboot and get to a screen where you see an arrow going in to a chip. Leave it be and let it finish (it might be a few seconds to 1-2 minutes). It will reboot on its own. After it reboots and gets to a black screen, hold down home+power until you get to the recovery screen. Your just doing this step to ensure that you can get to a recovery screen. If you have landed at the screem, then hit call-menu-end to reboot.
15. Wait until your g1 powers all the way up. it will take a few minutes on first boot. Please be patient.
16. Sign-in to google all over again, quickly go to data synchronisation (in settings) and untick contacts sync.
17. While in settings, go to applications, and tick unknown sources, click ok.
18. Go to the market application, agree to terms, download mybackup, install, restore call logs,contacts,sms,mms,applications,bookmarks and ak notepad. restore ak notepad data after restoring the application.
19. Go back to settings,synchronisation and tick back contacts sync.
20. re-set back up your home screens, and system settings.
21. your done. enjoy
quite interesting as I also think of moving to cyanogenmod. one question still: does it support the multitouch on the browser as the jf1.51 does?
DJ_Spray said:
quite interesting as I also think of moving to cyanogenmod. one question still: does it support the multitouch on the browser as the jf1.51 does?
Click to expand...
Click to collapse
yes 10char
really nice!!!!
thanks!!
I did the switch this morning, ran one day and it is really nice!
I still had to modify the azerty.kl and azerty.kcm.bin files as usual to get the azerty physical keyboard, else nothing to do!
really love the 5 home screens.
just trying to get the 110% satisfaction: any way to get flash on cyanogen builds?
DJ_Spray said:
really nice!!!!
thanks!!
I did the switch this morning, ran one day and it is really nice!
I still had to modify the azerty.kl and azerty.kcm.bin files as usual to get the azerty physical keyboard, else nothing to do!
really love the 5 home screens.
just trying to get the 110% satisfaction: any way to get flash on cyanogen builds?
Click to expand...
Click to collapse
It's in the release thread ffs >.>
22. Will you include the Flash Player from Hero?
No, because it's tightly coupled to the Hero Browser, which is tightly coupled to the Hero Framework. It's not easily portable at this point. Run Hero if you want it. Otherwise, we will have to wait for something more compatible.
Click to expand...
Click to collapse
Flash 9 sucks anyway...
pershoot said:
Make sure you are fully charged, and or have the G1 plugged in before starting.
1. Download and install MyBackup from the Market.
2. Backup all your call logs,contacts,sms,mms,applications,bookmarks, and ak notepad do not backup system settings, homescreen shortcuts.
3. Download and put this on the root of your sdcard: http://n0rp.chemlab.org/android/cm-recovery-1.4.img
4. Open up terminal, and type su.
5. cd /sdcard
6. flash_image recovery ./cm-recovery-1.4.img
7. type exit twice to exit out of the terminal application.
8. Download and put this on the root of your sdcard: http://n0rp.chemlab.org/android/update-cm-4.0.2-signed.zip
9. Download: ota-radio-2_22_19_26I.zip and put this on the root of your sdcard from: http://www.htc.com/www/support/android/adp.html#s3 or you can download it from: http://sapphire-port-dream.googlecode.com/files/ota-radio-2_22_19_26I.zip
10. Reboot the phone. When you get to a black screen (just before the G1 logo) hold down home + power. Keep pressed until you see the recovery screen.
11. Select wipe menu option (with trackball), then confirm it with home key (when it asks you to).
12. Select flash any update, select update-cm-4.0.2-signed.zip, then press home to confirm. Wait until the flash finishes.
13. Select reboot option (itll be highlighted once flashing is done).
14. Once it reboots, and you get to a black screen, hold down camera and power. When you get to the skating android or tri-colored boot screen (depending on which SPL (hard/engineering/stock) you have) take note of the radio version. If you don't have radio: 2.22.19.26I, hit call-menu-end, hold down power + home, keep it pressed until you get to the recovery. Select flash any update, and select ota-radio-2_22_19_26I.zip and confirm with home when it asks you to. When it finishes it will ask you to reboot. Click reboot option. It will then reboot and get to a screen where you see an arrow going in to a chip. Leave it be and let it finish (it might be a few seconds to 1-2 minutes). It will reboot on its own. After it reboots and gets to a black screen, hold down home+power until you get to the recovery screen. Your just doing this step to ensure that you can get to a recovery screen. If you have landed at the screem, then hit call-menu-end to reboot.
15. Wait until your g1 powers all the way up. it will take a few minutes on first boot. Please be patient.
16. Sign-in to google all over again, quickly go to data synchronisation (in settings) and untick contacts sync.
17. While in settings, go to applications, and tick unknown sources, click ok.
18. Go to the market application, agree to terms, download mybackup, install, restore call logs,contacts,sms,mms,applications,bookmarks and ak notepad. restore ak notepad data after restoring the application.
19. Go back to settings,synchronisation and tick back contacts sync.
20. re-set back up your home screens, and system settings.
21. your done. enjoy
Click to expand...
Click to collapse
Boy that was not needed. Download the latest relase of cyans stable rom. But at root of sd. There is no need to rename update.zip if u have cyanogen 1.4 recovery and flash. If u were on jf apd 1.51 there is no need to wipe.
pistol4413 said:
Boy that was not needed. Download the latest relase of cyans stable rom. But at root of sd. There is no need to rename update.zip if u have cyanogen 1.4 recovery and flash. If u were on jf apd 1.51 there is no need to wipe.
Click to expand...
Click to collapse
I agree. All the instructions look like they would be for a phone that has just been rooted on RC29.

How can I fix the Hero ROM's bootloop without wiping and fresh install?

I am frustrated that everytime an new release is out gotta reprogram my phone.
rm -rf /system/sd/*
search
sillyshyme said:
I am frustrated that everytime an new release is out gotta reprogram my phone.
Click to expand...
Click to collapse
Wiping your ext should not be an issue unless you're using Drizzy's "builds". If you're switching ROMs then you will have to wipe - get over it, but there should be "no wipe" updates when updating the a new version of the same ROM.
sillyshyme said:
I am frustrated that everytime an new release is out gotta reprogram my phone.
Click to expand...
Click to collapse
so i just noticed you had 27 posts, and im pretty sure all 27 have been about not wanting to wipe when switching roms, or complaining that you keep getting a boot loop. its just the dirty truth, if you wanna avoid a bootloop follow the info in the thread in my signature. if you dont wanna wipe, then dont switch, plain and simple.
SEARCH!!!!
palosjr said:
so i just noticed you had 27 posts, and im pretty sure all 27 have been about not wanting to wipe when switching roms, or complaining that you keep getting a boot loop. its just the dirty truth, if you wanna avoid a bootloop follow the info in the thread in my signature. if you dont wanna wipe, then dont switch, plain and simple.
SEARCH!!!!
Click to expand...
Click to collapse
Oh snap tellin it like it is..
I feel nice today, you're in luck, but this is the only post I'm writing to explain this procedure to you:
1. Reboot into recovery (Home + Power)
2. Backup NANDROID (or switchrom if you know how)
3. Enter into the console (alt+x)
4.
Code:
mount /system/sd
rm -rf /system/sd/app_s
rm -rf /system/sd/dalvik-cache
5.
Code:
ums_enable
6. Go into sdcard thru windows or whatever and then grab the data.img from the nandroid folder or switchrom folder depending on which one you used and place it in the same folder as fastboot (Go search if you don't know how)
7.
Code:
ums_disable
8.
Code:
recovery
9. Repair Filesystems (alt+f) (I think...)
10. Wipe data (alt+w)
11. Flash ROM of choice. (I've done this with practically every Hero flavor out there, should be no problem unless you cut corners in my directions some where... shame on you...)
12. Reboot phone when it finishes.
13. Wait for phone to get to setup page. Then, once there, reboot your phone again, but this time into bootloader (Camera + Power). You must wait for it to load the setup or this won't work.
14. Once fastboot is connected to the phone and can detect it (From connected PC):
Code:
fastboot flash userdata data.img
fastboot reboot
15. Wait for phone to boot up.... and bam, all wallpapers, lockscreen, program settings, mms, sms, contacts, etc. are already set up and your old settings + new ROM is ready to rock.

Cyanogen slow downs?

I'm using cyanogen-4.1.999 and for some reason, I'm seeing a massive speed decrease. I got 4.1.99 to run before it, but it also got slow-downs as well. None of cyanogen's roms did this before.
Example. It takes more than a few seconds for the screen to go from off, to maximum illumination (according to system setting that is).
What should I do?
I don't know what rom you were running before cm-4.1.99 but before you flash 4.1.99 make sure you wipe/clear your ext2/3/4 if you are using a second partition. After you have flashed 4.1.99 you should no longer need to wipe/clear your ext partitions when installing new cyanogen versions
ninjavampire said:
I don't know what rom you were running before cm-4.1.99 but before you flash 4.1.99 make sure you wipe/clear your ext2/3/4 if you are using a second partition. After you have flashed 4.1.99 you should no longer need to wipe/clear your ext partitions when installing new cyanogen versions
Click to expand...
Click to collapse
Crap... I only wiped ALT+W style. Oh well. Should I wipe ALT+W again after reformating?
edit: and when you say second partition, you mean the SDcard right?
Instructions to install cm-4.1.99 and 4.1.999 using cm-recovery1.4
Download tmo1.6, cyanogen 4.1.99 and cyanogen 4.1.999 from cyanogen fourm to root of your sd card (not in any folder)
Boot into recovery mode (home+power)
Wipe
If you are not using a second partition ignore next steps
Enter recovery console any type the following:
#mount -o /system/sd
#rm -rf /system/sd/*
#reboot recovery
Wipe again
Fix filesystems
Continue here if you are not using a second partition
Select option flash any .zip from sdcard and flash the tmo1.6 rom
When it is finished select option flash any .zip from sdcard and flash cm-4.1.99. You can do this with out rebooting your phone after the tmo1.6 flash
When 4.1.99 is finished select reboot option (home+back)
After boot and phone setup turn off your phone and boot into recovery again (home+power)
Select option flash any .zip from sdcard and select cm-4.1.999
When finished reboot phone (home+back) and enjoy the awesomness of Cyanogen!
Tactical Fart said:
Crap... I only wiped ALT+W style. Oh well. Should I wipe ALT+W again after reformating?
edit: and when you say second partition, you mean the SDcard right?
Click to expand...
Click to collapse
Yes I mean the sdcard when talking about second partition
ninjavampire said:
Instructions to install cm-4.1.99 and 4.1.999 using cm-recovery1.4
Download tmo1.6, cyanogen 4.1.99 and cyanogen 4.1.999 from cyanogen fourm to root of your sd card (not in any folder)
Boot into recovery mode (home+power)
Wipe
If you are not using a second partition ignore next steps
Enter recovery console any type the following:
#mount -o /system/sd
#rm -rf /system/sd/*
#reboot recovery
Wipe again
Fix filesystems
Continue here if you are not using a second partition
Select option flash any .zip from sdcard and flash the tmo1.6 rom
When it is finished select option flash any .zip from sdcard and flash cm-4.1.99. You can do this with out rebooting your phone after the tmo1.6 flash
When 4.1.99 is finished select reboot option (home+back)
After boot and phone setup turn off your phone and boot into recovery again (home+power)
Select option flash any .zip from sdcard and select cm-4.1.999
When finished reboot phone (home+back) and enjoy the awesomness of Cyanogen!
Click to expand...
Click to collapse
Ohh i had the same problem too. So Do we need to do the 'alt w' in recovery still?
NOback said:
Ohh i had the same problem too. So Do we need to do the 'alt w' in recovery still?
Click to expand...
Click to collapse
Yes in the instructions I posted above "wipe" is the same as "alt+w"
Doing all those instructions seems to be a lil extreme. Clear your data and cache in the browser, google maps, and street view (thats where it's held the most). And then go to terminal and type:
Code:
su
cd /system/sd/dalvik-cache
rm *
exit
exit
Then reboot your phone. It will take awhile for it to boot up like the very first time flashing.
supremeteam256 said:
Doing all those instructions seems to be a lil extreme. Clear your data and cache in the browser, google maps, and street view (thats where it's held the most). And then go to terminal and type:
Code:
su
cd /system/sd/[B]dalvik[/B]-cache
rm *
exit
exit
Then reboot your phone. It will take awhile for it to boot up like the very first time flashing.
Click to expand...
Click to collapse
fixed typo (dalvik instead of dalvick)
B-man007 said:
fixed typo (dalvik instead of dalvick)
Click to expand...
Click to collapse
Thank you. Way to keep your eye on the ball son.
This only worked until today. When I checked the directory some (all?) of the files there were restored and I had to "rm *" the directory again. Earlier, it took me about 5 minutes to get the phone to cooperate long enough to order a reboot. Ideas?
Tactical Fart said:
This only worked until today. When I checked the directory some (all?) of the files there were restored and I had to "rm *" the directory again. Earlier, it took me about 5 minutes to get the phone to cooperate long enough to order a reboot. Ideas?
Click to expand...
Click to collapse
Well when you reboot the phone...android remakes those files. thats why it takes so long to boot after you do that. the phone should run smoother then.
Have you tried wiping your ext partition?
B-man007 said:
Have you tried wiping your ext partition?
Click to expand...
Click to collapse
Yes. I used sdparted to nuke the whole thing. Now I have a main, swap, and ext2 partitioned card.
Tactical Fart said:
Yes. I used sdparted to nuke the whole thing. Now I have a main, swap, and ext2 partitioned card.
Click to expand...
Click to collapse
is it in that order? because its in the wrong order then. it needs to be FAT32, EXT, Linux-Swap
you should upgrade to EXT3 as it uses journaling (its safer)
did you try booting without the sd card? (wipe and flash the update, remove the sdcard, and reboot)
is there still a problem with the speed w/o it?
No, my partitions are the order you said they should. It was just a basic reformat without any special paramaters.
Also, the slow downs don't occcur until the phone has been on for a while. A reboot fixes the problem quickly, but while the problem is in place, I can't use "su" in the terminal (the phone is so slow that the su permissions manager can't respond in time to give permission and it refuses) and I can't receive calls. Plus it takes about 5 minutes of fighting to reboot, and thats if I don't pull the battery.
Tactical Fart said:
No, my partitions are the order you said they should. It was just a basic reformat without any special paramaters.
Also, the slow downs don't occcur until the phone has been on for a while. A reboot fixes the problem quickly, but while the problem is in place, I can't use "su" in the terminal (the phone is so slow that the su permissions manager can't respond in time to give permission and it refuses) and I can't receive calls. Plus it takes about 5 minutes of fighting to reboot, and thats if I don't pull the battery.
Click to expand...
Click to collapse
im starting to get these problems too. Cyan is going to release anotherr rom (probably today) that aims to fix some of the major errors with the rom according to his twitter. I guess we should just wait and see if it makes it better
cyanogen 4.1.99 and 4.1.999 slow down cure
I upgraded two g1’s to 4.1.99 and then to 4.1.999. First they were slow. I had to upgrade my ext2 partition to ext3. I did this from cyanogen recovery console, 4.1 If you already have 4.1 console installed, Go to console, enter/return, on the keyboard and typed the command, upgrade_fs next to the # and then pressed enter.
If you do not have recovery console 4.1 installed. Use this link below, in the instructions for installing it from the terminal emulator make sure you type, su then press the return/enter then type in the flash command per the instruction.
http://www.cyanogenmod.com/downloads/recovery-image
Then you must be in the 4.1 recovery console, you access by holding down the power and home buttons while rebooting, got to alt-x, Go to console)
in console press enter/return
type the command upgrade_fs then press enter/return then type reboot and press enter/return.
I then downlaoded everything I needed and put them on my sd card and installed following these instructions.
http://www.simplehelp.net/2009/10/04/how-to-install-cyanogenmod-4-1-99-on-your-g1-android-phone/
Worked like a charm and runs fast and stable. Hope this helps.

Newbie on a mac, please check my rooting steps...

I'm using some guys guide for mac users:
1. Take a deep breath. It is just software and you are going to master it!
2. Download and install the Mac OSX Android SDK. I am going to assume for the purposes of this list that you have put it in /Applications/android-sdk-mac_86/tools/ but it doesn't matter.
3. Get fastboot-mac from here. Rename it 'fastboot' and put it in /Applications/android-sdk-mac_86/tools/.
4. Get Radio_20100203_2_Signed_PASSION.img,
update-cm-5.0.4.1-N1-signed.zip AND gapps-passion-ERE36B-2-signed.zip
from here and put them in /Applications/android-sdk-mac_86/tools/.
5. Get recovery-RA-nexus-v1.6.2.img from here and put it in /Applications/android-sdk-mac_86/tools/
6. Put Get Radio_20100203_2_Signed_PASSION.img,
update-cm-5.0.4.1-N1-signed.zip and gapps-passion-ERE36B-2-signed.zip
on the root of the SD card. You can do this by mounting the phone via a USB cable (this works just like any USB stick except you have to click a button on the phone's UI).
7. In your phone settings > applications > development, set usb
debugging to enabled.
8. Turn off your phone and put the SD card with the 3 files on it
into your phone.
9. Hook up the USB connection to your phone and your mac.
10. Reboot phone into fastboot: Hold down trackball, push the power
button and hold both until you see the fastboot screen. (The fastboot
screen is the one with the Androids on skateboards)
11. In Terminal on your mac, cd to /Applications/android-sdk_mac_86/tools
12. Type ‘./fastboot devices‘ to make sure your phone is recognized
(it should list a device number rather than simply returning to
command prompt with no feedback).
13. Type ‘./fastboot oem unlock‘ to unlock the bootloader (wohoo, your phone is now rooted!)
14. Use volume keys on the phone to navigate to yes and press the
power button to confirm.
15. When the phone finishes booting, in your phone settings >
applications > development, set usb debugging to enabled, then power
it down.
16. Reboot phone into fastboot: Hold down trackball, push the power
button and hold both until you see the fastboot screen. (The fastboot
screen is the one with the Androids on skateboards)
17. (you're still in terminal in /Applications/android-sdk_mac_86/tools)
Type ‘./fastboot flash recovery ./recovery-RA-nexus-v1.6.2.img‘. (Note
filename will change as recovery image is updated)
18. Type './fastboot flash radio ./Radio_20100203_2_Signed_PASSION.img'
to also update your radio at this point
19. Once the Recovery flash is complete (should be almost instant),
press the Power Button. The highlighted blue text should now say
HBOOT. Use the volume down button to highlight "Recovery" and hit the
power button to reboot into recovery.
20. if this step fails, power down the phone, and try this: hold down
the VOLUME DOWN button and then hold the POWER button until you get to
the skateboard screen; use volume down to highlight RECOVERY and hit
the POWER button
21. You should now be in the Recovery screen after a reboot -- this
screen has 9 green text options at the top and an android x in the
center of the screen
22. Once in Recovery Mode, use the trackball to scroll down to
"Backup/Restore" and press the trackball three times, and wait until
the backup is complete.
23. Once backup is complete, wipe, since you're coming from stock
(even fastboot oem unlock may not fully wipe, do it just in case) many
users report the phone not booting properly without a wipe at this
point.
24. Scroll down to "Flash zip from sdcard", and press the trackball.
25. Select the CyanogenMod update (update-cm-5.0.4.1-N1-signed.zip),
and press the trackball again to confirm. Wait until the flash is
complete. (Note: this will take a little while).
26. Once again, Scroll down to "Flash zip from sdcard", and press the trackball.
27. This time, select the Google Apps File
(gapps-passion-ERE36B-2-signed.zip), and press the trackball again to
confirm. Wait until the flash is complete.
28. Once you are back in the main menu, press the trackball select the
first option (Reboot system now) and reboot the phone.
29. If everything was done correctly, the phone should boot into CyanogenMod!
Click to expand...
Click to collapse
My few questions...
Do I really need SDK? I've been reading a lot, and some say use it, some don't mention it.
I've already found that some of his files are updated, so I'd be using the more recent ones.
Also, I'm thinking that I'm NOT going to mess with the radio. I don't have to, right?
ETA: And then I see that his post says nothing about superboot. Am I supposed to do both? Fastboot and then superboot?
And then another question... I plan on getting a 16gb class 6 sd card. Should I wait to do this until I get that? Will I have to do it all over again?
Thanks!!
I am by no means a pro at this, but to answer a a question or 2 of yours...
I never bothered using the SDK. I did download it, but like you, I followed other instructions that did not tell you to use the SDK.
The important part is to put all the downloaded files into your renamed "fastboot" folder, where fastboot will know where to look for it.
Concerning the radio, some ROMS may or may not require different radios, but for the simple process of rooting your phone, I'm pretty sure you're cool.
I used fastboot, but superboot (if I understand it correctly) is a total tool for your use. Someone correct me if I'm wrong, but I believe it takes the place of all the steps you listed above, and does it all in one command.
Good luck! Its easy, and it sounds like you have all the tools you need!
1) I didn't flash a new radio when I rooted mine (didn't for a couple of weeks until I was comfortable with flashing and abd and stuff). The radio is evidently the greatest risk of bricking the phone.
2) I've typically seen "superboot" to refer to a rom image that modaco hosts that includes the superuser perms and apk and not as a tool (as fastboot is referred to). ymmv.

Categories

Resources