Jump to content

Papa_I

Members
  • Content Count

    14
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Papa_I

  • Rank
    Newbie

Profile Information

  • Your Current Device(s)
    Nexus One
  1. I recently receive my Nexus One back from HTC to fix the power button. Since I received the phone back, I rooted using Super-One-Click , and installed Rom Manager to restore my phone to the rom I was using before I sent my phone away. Everything worked as expected, and my phone was fully restored. I tried to install Trackball wake and unlock from (http://forum.xda-developers.com/show...ight=trackball) and this is where my problems started. I used Root Manager to install the android.policy.jar and updated the permissions. I rebooted my phone and the phone will not get passed the “X” boot screen. I booted my phone into Bootloader mode (Power + Volume Down) and was going to push a new android.policy.jar file through ADB, but I could not connect to the phone through ADB. I do not believe I ever turned Debugging Mode on while the phone was working properly. I booted my phone into recovery and was going to restore my phone through clockwork recovery only to find out my phone did not have clockwork recovery flashed, but instead it had the stock recovery loaded. I than tried to restore my phone back to a stock image through loading a signed update.zip but that did not work. I than tried to downgrade using the PASSIMG.img method found here (http://forum.xda-developers.com/wiki...ore_your_Nexus), but my phone currently has hboot-0.35.0017 and will not accept the PASSIMG.img. When I try to load the PASSIMG.img I get an error stating “Main version is older!”. I for some reason cannot get adb to recognize my phone, so I don’t think I can downgrade my hboot. I have been able to get fastboot to recognize my phone, but for some reason the phone will not let my flash any files via fastboot. I would really like to find a way to restore my phone to a stock image so I can start the process over from scratch. I really would like to keep my bootloader locked if at all possible as the phone is still under warranty. Any assistance anyone could provide would be greatly appreciated. Please let me know if I left out any information that would usefully in fixing my problem. Thanks! HBoot-0.35.0017 Bootloader-Locked Current Rom Version-2.2.1 (this rom should be rooted) Recovery Image: Stock
  2. You should be able to update your system with out doing a full wipe. The only time that a wipe would be needed is if your system for some reason is not performing correctly after the update.
  3. Are you using A2SD? I am not using A2SD and haven't had any issues with Angry Birds.
  4. If you use the pre-baked releases trackball wake isn't included. You can easily add that feature by using the procedure laid out in this thread http://forum.xda-developers.com/showthread...=trackball+wake.
  5. I had no issues installing the MCR r24 through Rom Manager. You just need to download the rom and put it on the root of your sdcard as the rom can't be downloaded through Rom Manager.
  6. This method worked for me on the FRF91 build and the FRG83 and FRG83D builds too. http://forum.xda-developers.com/showthread.php?t=716967 UPDATE: Just an FYI, this mod was causing my dialer to be unstable with r24. Make sure you backup your services.jar prior to using this mod just in case it causes your system to become unstable too.
  7. Paul, First of all, thank you for your hard work on these roms. I installed the "r24 without default MoDaCo additions" this weekend and everything works well except for the phone dialer. I am not sure why but every time I hang up a call, my phone reboots. I did a full wipe along with wiping Dalvik-Cache prior to loading this rom. I had this issue previously when loading one of your roms (http://android.modaco.com/index.php?s=&showtopic=319064&view=findpost&p=1430019), and I can't seem to figure out what is going on or how to fix this. Any suggestions would be appretiated. I am using the 32.50.00.32U_5.12.00.08 radio currently. UPDATE: I have fixed my issue. Apparently using this battery percentage mod was causing my dialer to crash (http://forum.xda-developers.com/showthread.php?t=716967).
  8. Paul uses the stock Kernel in his roms, so this isn't going to happen. Same thing with 720p video.
  9. Paul, any chance you can work in 720p video recording?
  10. I installed "Rooted / deodexed / busybox / trackball alert with radio update zip download (recommended)" with no issues. I wiped cache and dalvik-cache prior to installation. The rom is running well, but when I use the dialer, the phone reboots. Is anyone else having this issue, or know how to fix it? Thanks.
  11. If you update through the OTA notification you are receiving, you will loose your root access.
  12. I had the same issue on T-Mobile with the stock radio. Service just recently came back up. I don't think it was the radio that was giving you issues, but rather it was a network issue.
  13. Is there any update on a Superboot file for FRF91? Thanks.
  14. For everyone that is having "waiting for device" issues, try this. -On your phone, click Settings > Applications > Development and make sure USB Debugging is on. -Plug your phone into your computer via USB cable (it needs to be on). It should say installing drivers if using Windows. After that, windows should install the correct drivers from the sdk and than you can turn your phone off and boot into fastboot and follow the instructions from the first post. This worked for me. Thanks.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.