Bagaimana memulihkan hh yg brick

by jonitan17 » Sun, 01 Nov 2009 11:46:07 GMT


Sponsored Links
 bradre semua, cuma mau share aja, tapi ketemu link yg bagus dari
xda ,bagaimana mengatasi hh yg brick (belum nyoba dan moga2 jangan
deh  ,hehe) .

ini link nya
 http://forum.xda-developers.com/showthread.php?t=571457 

langkah2 nya (kalo ada salah mohon di revisi yah)
1.di pc jalanin dulu command "fastboot boot recovery image"
2.pada saat ini command akan muncul pesan "waiting for device"
3. setelah itu , cabut baterai hh nya
4. connect hh ke pc via usb
5. masukkan lagi baterainya ke hh
6  setelah itu nyalakan hh dengan cara menekan dan menahan tombol
home
7. setelah beberapa saat , hh akan masuk ke recovery lagi.

mohon maaf kalo ada kata2 yg gak jelas (poor english)

TIA


--~--~---------~--~----~------------~-------~--~----~
Google Groups "
-~----------~----~----~----~------~----~------~--~---



Bagaimana memulihkan hh yg brick

by Bayu Wicaksono » Sun, 01 Nov 2009 11:49:08 GMT


 Hm... I might try this.. see if this helps the bricked G1 on my possession..
:)

2009/11/1 jonitan17 <jonita...@gmail.com>


--~--~---------~--~----~------------~-------~--~----~
Google Groups "
-~----------~----~----~----~------~----~------~--~---


Sponsored Links


Other Threads

1. TMobile myFaves (com.tmobile.myfaves) is tied heavily into Android Framework?

For technical reasons (that I don't remember) we had to use myFaves as
the contacts provider and make it run in acore. This is specific
**only** to T-Mobile phones with myFaves.






-- 
Romain Guy
Android framework engineer
romain...@android.com

Note: please don't send private questions to me, as I don't have time
to provide private support.  All such questions should be posted on
public forums, where I and others can see and answer them

--~--~---------~--~----~------------~-------~--~----~

2. TMobile myFaves (com.tmobile.myfaves) is tied heavily into Android Framework?

When I kill any Google app, even the built in ones,
android.process.acore doesn't crash causing a cascade effect of
wonderfulness that is a black Launcher screen sometimes. So it can't
be related to being integrated into Google Authentications or
something. So, why the heck does myFaves do this? According to it's
package info it's process should be com.tmobile.myfaves.

A question for the TMobile guys, as well as pertinent to the Framework
engineers I think. And sure, I shouldn't be killing built in apps, but
I'm wondering why it has to behave like this.

10-02 19:46:06.716: DEBUG/ActivityManager(56): Uninstalling process
com.tmobile.myfaves
10-02 19:46:06.726: DEBUG/ActivityManager(56): Force removing process
ProcessRecord{433f8780 511:android.process.acore/10001}
(android.process.acore/10001)
10-02 19:46:06.726: INFO/ActivityManager(56): Killing app
com.google.process.gapps (pid 494) because provider
com.android.providers.im.ImProvider is in dying process
android.process.acore
10-02 19:46:06.726: INFO/Process(56): Sending signal. PID: 494 SIG: 9
10-02 19:46:06.746: INFO/Process(56): Sending signal. PID: 511 SIG: 9
10-02 19:46:06.766: DEBUG/ActivityManager(56): Force removing process
ProcessRecord{433c3b28 492:com.android.inputmethod.latin/10001}
(com.android.inputmethod.latin/10001)
10-02 19:46:06.766: WARN/ActivityManager(56): Scheduling restart of
crashed service com.android.inputmethod.latin/.LatinIME in 5000ms
10-02 19:46:06.776: INFO/Process(56): Sending signal. PID: 492 SIG: 9
10-02 19:46:06.816: INFO/ActivityManager(56): Process
com.google.process.gapps (pid 494) has died.
10-02 19:46:06.816: WARN/ActivityManager(56): Scheduling restart of
crashed service com.google.android.apps.gtalkservice/
com.google.android.gtalkservice.service.GTalkService in 5000ms
10-02 19:46:06.816: WARN/ActivityManager(56): Scheduling restart of
crashed service com.google.android.googleapps/.GoogleLoginService in
5000ms
10-02 19:46:06.826: DEBUG/ActivityManager(56): Received spurious death
notification for thread android.os.binderpr...@43381ff0
10-02 19:46:06.856: WARN/InputManagerService(56): Window already
focused, ignoring focus gain of:
com.android.internal.view.iinputmethodclient$stub$pr...@433095a8
10-02 19:46:06.896: DEBUG/ActivityManager(56): Received spurious death
notification for thread android.os.binderpr...@4327d3c8
10-02 19:46:06.896: INFO/WindowManager(56): WIN DEATH: Window{4311c660
com.android.launcher/com.android.launcher.Launcher paused=false}
10-02 19:46:07.076: WARN/ResourceType(56): No package identifier when
getting value for resource number 0x7f060001
10-02 19:46:10.136: INFO/ActivityManager(56): Starting activity:
Intent { action=android.intent.action.MAIN categories=
{android.intent.category.HOME} flags=0x10200000 comp=
{com.android.launcher/com.android.launcher.Launcher} }
10-02 19:46:10.177: INFO/ActivityManager(56): Start proc
android.process.acore for activity com.android.launcher/.Launcher:
pid=642 uid=10001 gids={3003}

--~--~---------~--~----~------------~-------~--~----~

3. Applicatoin Context Vs Activity Context

4. Using ContentProvider.query to access multiple tables efficiently.

5. Is it possible to check if an activity is enabled or not?

6. Emulator -dpi-device option is not work.

7. downloading latest SDK