Cannot mount SD card
I wanted to get the trackball wake feature enabled following this post: [APP] Trackball Wake/Unlock/Skip [FRF91] - xda-developers following these steps:
1) open root explorer and find the file, make sure it is named android.policy.jar
2) copy android.policy.jar
3) go up to the root and then drill down to system>framework
4) at the top of the window, click on "Mount R/W"
5) paste the file (replace)
6) reboot... IMMEDIATELY
But when I replaced the policy.jar file something must have gone wrong. I rebooted the phone but now it never goes beyond the four colored X. It's just stuck there. I can't even mount the phone anymore. The SD card does not appear in Finder on my mac.
I've tried booting into Recovery mode but don't have a backup. Even if I did I'm not able to access the SD card.
Any suggestions how to save my N1? I'm getting quite desperate.
10-28-2010 03:48 PM
Well if you were going to go through all that trouble, you should of just rooted and added a custom ROM to it. Most custom ROMs enable the trackball wake feature.
Before messing with ANYTHING in that regards, you need to have a backup.
Can you access recovery and reset factory defaults?
All I can suggest boot into recovery and mount your SD card through recovery. Jump over to XDA and find a STOCK FroYo ROM / .img and flash it. If you're not rooted and don't have a custom recovery, I'm not sure that will work. I never really messed around with stock recovery, I've always used ClockWork.
Open up a thread over on XDA, they will definitely be able to help.
I can get into recovery mode but I can't reset factory defaults. At least doing that doesn't help anything. It still gets stuck at the X upon startup. I will try the XDA forum.
What happens when you fire up into hboot, does your phone try and read your card? (do you see the green text flash quickly, as it scans the card? does it report an error?)
Sent from my Nexus One using Tapatalk
Friend of mine fixed it. He basically installed the latest and greatest custom rom. The phone was so 'damaged' that it hardly responded to anything. He had to unlock the bootloader first. This probably voids the warranty but I'll take the chance.
Anyway, thanks for your replies :-)