Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by Bokai

  1. What I did was that I ran the RUU .exe. And while the app is at its first screen, you do a search for rom.zip in your temporary folders in C:\. Copy the rom.zip to somewhere and close the RUU .exe after that. Hope this helps! /Jakob
  2. Solved! For anyone having issues with Error 155(CID-checks fail, perhaps?) or 171(USB fail) while trying to restore a rooted HTC Hero to stock with an official RUU-exe, this is what worked for me where nothing else did: - Create Goldcard - Extract ROM.ZIP from the Official RUU exe you want to use. I downloaded it from their main site - Rename to HEROIMG.zip - Boot to flashboot mode (Volume down + Power on) - Flash. - Reboot and enjoy your new stock HTC Hero.
  3. Hi! So.. My HTC Hero GSM has some issues that need to be repaired. Touchscreen not working in the lower part of the screen, constant headset-icon, trackball not working good. So I've contacted my repair center and they told me to send it in. So I want to restore my phone to as close to original as possible to be on the safe side. The problem is I can't use the official RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver.exe(or any other version), without getting an error 155(apparently it has something to do with the rom not having correct filesize). It doesn't matter what rom I'm currently using; Modaco, Villain, different kind of generics(from Pauls sticky post), but nothing affects the outcome. I got a feeling it has to do with the recovery image I use(RA 1.6.2) or Hboot version(.0007), but I can't seem to flash a new one. Recovery flasher gives me "Backup FAILED: could not run command.", and since my HBOOT is .0007 I can't use remote command from fastboot to restore original. 1. Is it possible to downgrade HBoot from recovery mode? If so, does anyone have a update.zip I can use? 2. Could error 155 has something to do with the computer/OS im using? 3. Anyone has any other suggestions what I can try to restore? Currently using: HTC Hero GSM Generic 2.73.405.38 (1.5) Baseband HBoot 1.76.0007 Any help is greatly appreciated! /Jakob
  4. Bokai


    I love it after 10 mins! :D Will try it out for a couple of days. Its a little bit different to input special symbols though.. Had to add smileys as shortcut.
  5. If it doesn't work to make an exception to HTC Checkin service, try uninstalling. I did it as recommended above, and I haven't encountered the FC loop yet. *crosses fingers* To fix uid you use recovery mode. If you have Amon Ra's recovery image, then it is under the menu "Other". I'm sure you can do it trough ADP shell, but I'm no expert there...
  6. I use it! I absolutely love it but will uninstall to see if it is causing this. Anyone have any suggestions for replacements?
  7. This doesn't occur when I Mount USB. In fact, I can even mount USB while the FC is looping. It seems my loop has something to do with a scheduled event that should take place sometime around 4pm and perhaps some other time of the day(It was FC-looping when I woke up this morning). Slightly after 4pm I wake up my phone and get ready to go home from work. 2 days in a row now, it has been in the force close loop when I turn it on... This might just be chance ofcourse. Can someone please help my understand the following from logcat? This is just a snippet of the log, there is more in the attached .txt. Too me it seems like several apps need "provider settings" that come from com.android.provider.settings.settingsprovider, but it can't provide anything and therefor lots of stuff dies. As I'm a total noob at custom roms, modding and Linux it feels like I am fumbling in the dark here... Please help! W/ActivityManager( 108): Process com.android.providers.settings has crashed too many times: killing! D/ActivityManager( 108): Force removing process ProcessRecord{43824660 3947:system/1000} (system/1000) W/ActivityManager( 108): Unable to launch app android/1000 for provider sync: launching app became null I/ActivityManager( 108): Killing app com.htc.launcher (pid 3924) because provider android.content.SyncProvider is in dying process system I/Process ( 108): Sending signal. PID: 3924 SIG: 9 W/ActivityManager( 108): Unable to launch app com.android.providers.settings/1000 for provider settings: launching app became null W/ActivityManager( 108): Unable to launch app com.android.providers.settings/1000 for provider settings: launching app became null E/ActivityThread( 3934): Failed to find provider info for settings D/AndroidRuntime( 3934): Shutting down VM W/dalvikvm( 3934): threadid=3: thread exiting with uncaught exception (group=0x40013140) E/AndroidRuntime( 3934): Uncaught handler: thread main exiting due to uncaught exception I/ActivityManager( 108): Killing app com.google.process.gapps (pid 3934) because provider com.android.providers.settings.SettingsProvider is in dying process system I/Process ( 108): Sending signal. PID: 3934 SIG: 9 I/Process ( 108): Sending signal. PID: 3947 SIG: 9 I/ActivityManager( 108): Process com.google.process.gapps (pid 3934) has died. D/ActivityManager( 108): Received spurious death notification for thread [email protected] I/ActivityManager( 108): Process com.htc.launcher (pid 3924) has died. D/dalvikvm( 3960): Rosie launcher will have a 32MB heap[/codebox] FC_loop_log.txt
  8. Is there some way to remove just a few words? On more than one occasion I have accidentally added silly words that later one screws with my typing... :)
  9. Is the second cpu never used by anything other than the radio functions? Is that why the hero i blazing fast when you are in plane mode? Because the 2nd cpu is then used for all the goodies?
  10. This is my current homescreen. I try to keep things as clean as possible, and I prefer darker themes as you can see. :) Nothing too special here though... Black Eclair theme, lockbot pro, smooth calendar, better widgets... Thats about it I think.
  11. Hi guys, I've been having some FC-loop issues since I upgraded to Modaco custom rom. It appears at least a couple of times a day and the only thing I can do to get my Hero to work again is to reboot. I'm kinda new to custom roms, so please bear with me... :) The processes that seem to stop working are htc launcher and htc sense + alot of others(I just recently learned about logcat so I haven't run it to get more precise info, but will do that later today when the looping begins). The problems began after I first rooted my Hero and flashed MoDaCo 2.9. Right now I'm sitting on 3.1, which is totally awesome except that I still get these damn FCs. Before I upgraded to 3.1 I did a wipe/factory reset via recovery mode, but the FC-loop is still there. After searching some here on the forums and elsewhere on the web I thought I'd try to wipe dalvik cache + fix mismatched UIDs. UIDs are now fixed but apparently I can't use the wipe dalvik cache from recovery mode, I only get "Error : Run 'wipe dalvik' via adb!"). Anyone have any ideas on how I can get wipe dalvik cache to work? Or perhaps any other advice that could point me in the right direction to solve this and make my phone even more awesome? :) Some info: Build: MoDaCo 3.1 Kernel: 2.6.17-mck-teknologist-1,91 Baseband:
  • Create New...

Important Information

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