Did I brick my phone :'( ?

[ben at benwen.info]

Thank you so much, Michael!  This was just the kind of tip I needed.  I 
was completely ignorant of the fact that on a Galaxy S, pressing FOUR 
keys (Vol+, Vol-, Select, Power) simultaneously boots you into recovery 
mode.  I was thus able to reinstall a CM10 zip that was on the SD card 
and go back to my comfort zone.  I guess I'll need a better 
understanding of some fundamental concepts before reattempting to flash 
Replicant.

Thanks again.


Le 2012-11-26 06:09, Michael von Glasow a écrit :
> Hi,
>
>  Just a guess... but you should be able to get into recovery without
> ADB. All you need to do is press some key combination while switching
> on your phone (depends on model, Volume Up is a frequently used one).
> This will take you to the recovery menu. From there you can flash a
> boot image using fastboot (described on CyanogenMod wiki) or heimdall
> (see Replicant wiki).
>
>  Hope it helps
>  --
>  Sent from my Android phone with K-9 Mail. Please excuse my brevity.
>
> Benjamin Rochefort <ben at benwen.info> wrote:
>
>> Hello freedom lovers!
>>
>> I was a happy user of CyanogenMod 10 and decided to try out 
>> Replicant.
>> Unfortunately, the install procedure failed at some point and I am 
>> now
>> stuck in an endless boot loop which goes like this:
>>
>> 10 Galaxy S GT-I9000M splash screen
>> 20 Galaxy S cyanogen(mod) splash screen
>> 30 A screen with text scrolling so fast that I can't make anything 
>> out
>> of it, the android robot icon in the background which seems to 
>> change to
>> a 'dead' robot lying on its back with a red error icon just before 
>> rebooting
>> 40 GOTO 10
>>
>> I had the following chat with paulk yesterday:
>>
>> (16:51:20) paulk-desktop: oysterboy, so CyanogenMod bootsplash 
>> appears
>> at some point?
>> (16:51:33) paulk-desktop: if so, then do "adb reboot recovery" at 
>> this
>> moment
>> (16:51:38) paulk-desktop: and press the key combination
>> (16:51:47) paulk-desktop: then when you're in download mode, reflash
>> replicant boot.img
>> (16:52:10) paulk-desktop: and it'll boot in replicant recovery, and
>> there you'll be able to flash replicant following the next 
>> instructions
>> (or reflash cyanogenmod)
>> (16:52:51) paulk-desktop: oysterboy, I'll need to leave very soon 
>> though
>> (16:52:57) paulk-desktop: so i hope this will work
>> (16:53:13) oysterboy: will try...
>> (16:53:21) oysterboy: hope I can get it back to a normal state...
>> (16:53:40) paulk-desktop: you always can
>> (16:53:50) paulk-desktop: unless you reflash the bootloader, but 
>> that
>> doesn't happen a lot
>>
>> Unfortunately, I am unable to run any adb commands on my phone in 
>> its
>> current state.
>>
>> adb reboot recovery -> error: device not found
>> adb devices -> List of devices attached
>>
>> [I do a have a udev rule that enabled my phone to be recognized, but 
>> it
>> doesn't seem to be taken into account anymore]
>>
>> Any help much appreciated. I've searched so much on the internet 
>> today
>> and I am really stuck :(. If the #replicant irc channel is a better
>> place for discussing this problem, please let me know.
>>
>> Thanks!
>>
>> -------------------------
>>
>> Replicant mailing list
>> Replicant at lists.osuosl.org
>> http://lists.osuosl.org/mailman/listinfo/replicant [1]
>
>
> Links:
> ------
> [1] http://lists.osuosl.org/mailman/listinfo/replicant