Phone suddenly stopped booting

This is a discussion on Phone suddenly stopped booting within the Nexus One Tech Issues / Bug Reports forums, part of the Nexus One category; Hi, I am hoping someone will know how to recover my phone. Here is what happened .. I installed clockwork recovery and it worked great ...

Results 1 to 8 of 8

Thread: Phone suddenly stopped booting

  1. #1
    Junior Member Draco's Avatar
    Join Date
    Aug 2012
    Posts
    5

    Phone suddenly stopped booting

    Hi,

    I am hoping someone will know how to recover my phone.

    Here is what happened ..

    I installed clockwork recovery and it worked great
    I then installed CM 7.2 and that also worked great..
    Then a week or so later it just stopped working ..
    When I turn it on it now stays at the booting X screen with the unlocked bootloader symbol at the bottom.

    Here is what I have tried so far ..

    Taking out the battery and rebooting .. no effect

    Booting into recovery .. same X boot screen

    Re-flashing recovery from fastboot .. successful flash but does not get past the X boot screen

    Renamed PASSIMG_Passion_Google_WWE_2.18.1700.1_FRG83_relea se_signed.zip
    to PASSIMG.zip and put it on the SD card via my computer and launched the bootloader .. all items flashed successfully.. but when rebooted it is still stuck at X boot screen

    Tried flashing Amen_Ra recovery from fastboot .. successful flash but does not get past the X boot screen when I try to launch recovery

    I'm not sure what else I could try .. I am hoping I am missing something

    Thanks in advance!

  2. Android.net is the premier Android Forum. Registered users do not see these ads. .

  3. #2
    Member n1newbie's Avatar
    Join Date
    Oct 2011
    Posts
    41
    try erasing all partitions from fastboot
    fastboot erase system
    fastboot erase userdata
    fastboot erase cache
    fastboot erase recovery

    now try to fastboot recovery.img or passimg...

    Sent from my Nexus One using Tapatalk

  4. #3
    Junior Member Draco's Avatar
    Join Date
    Aug 2012
    Posts
    5
    Thanks n1newbie ..

    I tried that and same results, however I have made some progress ...

    I managed to get blackrose_manual_120421 hboot installed ..
    this did not help the booting

    The strange thing is I finally did get something to boot ..
    but I had to use fastboot to do it

    >fastboot boot boot.img
    using either clockwork recovery or the image out of PASSIMG (after updating) works and boots

    It does not boot by itself however
    This is the result of normal booting (unsuccessful) via fastboot .. perhaps it will help

    >fastboot oem boot

    (bootloader) setup_tag addr=0xA0000100 cmdline add=0x8E08BCBC
    (bootloader) TAG:Ramdisk OK
    (bootloader) TAG:smi ok, size = 0
    (bootloader) TAG:hwid 0x0
    (bootloader) TAG:skuid 0x21F01
    (bootloader) TAG:hero panel = 0x0
    (bootloader) TAG:engineerid = 0x0
    (bootloader) MCP dual-die
    (bootloader) MCP dual-die
    (bootloader) TAG:mono-die = 0x0
    (bootloader) Device CID is not super CID
    (bootloader) CID is GOOGL001
    (bootloader) setting.cid::GOOGL001
    (bootloader) serial number: <removed>
    (bootloader) commandline from head: no_console_suspend=1 msmsdcc_sdioirq=
    (bootloader) 1 wire.search_count=5
    (bootloader) command line length =447
    (bootloader) active commandline: board_mahimahi.disable_uart3=0 board_mah
    (bootloader) imahi.usb_h2w_sw=0 board_mahimahi.disable_sdcard=0 diag.enab
    (bootloader) led=0 board_mahimahi.debug_uart=0 smisize=0 androidboot.bas
    (bootloader) eband=5.08.00.04 androidboot.cid=GOOGL001 androidboot.carrie
    (bootloader) r=GOOGLE androidboot.mid=PB9910000 androidboot.keycaps=qwert
    (bootloader) y androidboot.mode=normal androidboot.serialno=<removed>
    (bootloader) androidboot.bootloader=0.35.2017 blackrose=2000 no_console_s
    (bootloader) uspend=1 msmsdcc_sdioirq=1 wire.search_count=5
    (bootloader) aARM_Partion[0].name=misc
    (bootloader) aARM_Partion[1].name=recovery
    (bootloader) aARM_Partion[2].name=boot
    (bootloader) aARM_Partion[3].name=system
    (bootloader) aARM_Partion[4].name=cache
    (bootloader) aARM_Partion[5].name=userdata
    (bootloader) partition number=6
    (bootloader) Valid partition num=6
    (bootloader) 0
    (bootloader) 0
    (bootloader) 0
    (bootloader) 0
    (bootloader) 0
    (bootloader) 0
    (bootloader) 0
    (bootloader) 0
    (bootloader) 0
    (bootloader) 0
    (bootloader) 0
    (bootloader) 0
    (bootloader) 0
    (bootloader) 0
    (bootloader) 0
    (bootloader) 0
    (bootloader) 0
    (bootloader) 0
    (bootloader) 0
    (bootloader) 0
    (bootloader) 0
    (bootloader) 0
    (bootloader) 0
    (bootloader) 0
    (bootloader) 0
    (bootloader) 0
    (bootloader) 0
    (bootloader) 0
    (bootloader) 0
    (bootloader) 0
    (bootloader) 0
    (bootloader) 0
    (bootloader) jump_to_kernel: machine_id(2304), tags_addr(0x20000100), ker
    (bootloader) nel_addr(0x20008000)

  5. #4
    Junior Member Draco's Avatar
    Join Date
    Aug 2012
    Posts
    5

    Phone suddenly stopped booting [solved]

    Okay I got it working ..

    I booted using fastboot as above .. using the PASSIMG

    >fastboot boot boot.img

    Then I allowed it to update to gingerbread ..
    I let it shutdown and then took out the battery and usb cables
    rebooted into fastboot

    >fastboot boot recovery.img

    It updated and then started working ..

    I'm not sure what it was but I am glad it works now ..

    Thanks

  6. #5
    Android Master rugmankc's Avatar
    Join Date
    Apr 2010
    Posts
    1,955
    maybe a bad flash

    fyi or unless you just forgot to add flash--

    the correct commands to fastboot an img are:

    fastboot flash boot boot.img

    fastboot flash recovery nameofrecovery.img


    if you run, for example, fastboot boot recovery.img you are actually booting into recovery not flashing the new recovery thru fastboot


    either way it is working for you--
    Phones Owned: Nokia 6200; Nokia 6126 2ea; BB 8700g; BB 8900; MyTouch 4G; Nexus One: HTC One S; Carrier-TMobile

    [SIGPIC][/SIGPIC]


    San Francisco Giants

  7. #6
    Junior Member Draco's Avatar
    Join Date
    Aug 2012
    Posts
    5
    Hi rugmankc,

    I did flash both the boot and the recovery many times and it did not make any difference.

    I had to boot through the USB to get it to boot at all. I booted into the recovery.img because that is how it would update to Gingerbread. After that it started working again.

  8. #7
    Member n1newbie's Avatar
    Join Date
    Oct 2011
    Posts
    41
    glad you got it working buddy

    Sent from my Nexus One using Tapatalk

  9. #8
    Android Master rugmankc's Avatar
    Join Date
    Apr 2010
    Posts
    1,955
    Quote Originally Posted by Draco View Post
    Hi rugmankc,

    I did flash both the boot and the recovery many times and it did not make any difference.

    I had to boot through the USB to get it to boot at all. I booted into the recovery.img because that is how it would update to Gingerbread. After that it started working again.

    glad you got it also

    just wasn't sure if you mistyped or typed wrong command--sounds like you understand the difference. i have done that way also when needed

    enjoy--
    Phones Owned: Nokia 6200; Nokia 6126 2ea; BB 8700g; BB 8900; MyTouch 4G; Nexus One: HTC One S; Carrier-TMobile

    [SIGPIC][/SIGPIC]


    San Francisco Giants

Remove Ads

http://www.scramblerducati.org/

Sponsored Links

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Search tags for this page

cell phone stopped booting

,

htc nexus one google cid googl001 android rom download

,

passimg passion google wwe 2.18.1700.1 frg83 relea se signed.zip

,

passimg passion google wwe 2.18.1700.1 frg83 relea se signed.zip download

Click on a term to search our sites for related topics.
Android Forum