Results 1 to 6 of 6

Thread: semi-bricked panache/mytouch 4g, please help?

  1. #1
    Join Date
    Apr 2009
    Posts
    44
    Phone
    Nokia N95
    Carrier
    Rogers Wireless
    Feedback Score
    0

    Question semi-bricked panache/mytouch 4g, please help?

    I've already did this on xda-developers, but I didn't get the answers I was looking for. Anyway, I'll just copy/paste the important bits:

    1) recovery doesn't work. the partition seems to have been corrupted somehow. going into recovery through hboot results in the screen turning off and the phone vibrating 7 times.

    2) Phone hangs on htc logo unless the volume down + power/back + power combos are used to boot the phone into hboot/fastboot.

    3) The phone seemingly stopped working overnight while I was sleeping. I put it to charge and when I woke up it wasn't working anymore.

    4) the crc for the recovery partition has a string of 7 hexadecimal numbers. I'm no expert in this, but aren't hexadecimal strings supposed to be even-numbered?

    5) Despite the recovery/everything else having been corrupted, I can still send data to the phone through fastboot, although trying to flash anything fails because my phone has its security on.

    6) Using Fastboot oem boot and watching the output ends with the phone hanging at the htc logo while fastboot returns a "status read failed (too many links)" error.

    7) Using Fastboot oem task 28 (or 29) fails with a too many links error

    8) trying to erase the cache (the only thing that can be erased with s=on) fails with: you guessed it, too many links!

    9) Letting the phone drain its battery while doing 6, 7 or 8 still fail with too many links.

    10) using the update file from the stock videotron ruu (my phone's carrier) and onto the sd card has the phone hanging on trying to flash the bootloader through hboot.

    11) Trying to flash the phone using the update through fastboot fails saying something like signature verification fail. I kinda assume that's what makes the update hang on hboot.

    Here's all the technical stuff I could gather:

    -REBOOT BOOTLOADER (from FASTBOOT menu) (hangs)
    -FACTORY RESET (hangs)
    -RECOVERY (shows an image of two curved arrows with a regular arrow within, over a tilted cellphone, then the image is reversed, and the screen goes black and the phone vibrates exactly 7 times.)

    C:\sdk-tools>adb devices
    * daemon not running. starting it now on port 5037 *
    * daemon started successfully *
    List of devices attached


    C:\sdk-tools>

    C:\sdk-tools>fastboot getvar all
    INFOversion: 0.5
    INFOversion-bootloader: 0.89.0005
    INFOversion-baseband: 26.09.04.26_M
    INFOversion-cpld: None
    INFOversion-microp: 0429
    INFOversion-main: 2.10.1530.1
    INFOserialno: SH16KRM01484
    INFOimei: 357935045141682
    INFOproduct: glacier
    INFOplatform: HBOOT-7230
    INFOmodelid: PD1510000
    INFOcidnum: VIDEO001
    INFObattery-status: good
    INFObattery-voltage: 4183mV
    INFOpartition-layout: Generic
    INFOsecurity: on
    INFObuild-mode: SHIP
    INFOboot-mode: FASTBOOT
    INFOcommitno-bootloader: 6a4abc53
    INFOhbootpreupdate: 11
    INFOgencheckpt: 0
    all: Done!
    finished. total time: 0.047s

    Parsing... [SD ZIP]
    [1] BOOTLOADER -Updating
    [2] BOOT
    [3] RECOVERY
    [4] SYSTEM
    [5] SPLASH1
    [6] USERDATA
    [7] TP
    [8] TP
    [9] RADIO_VZ
    [10] RADIO_CUST
    Do you want to start update?
    <VOL UP> Yes
    <VOL DOWN> No
    Update is in progress...
    Do not power off the device!

    "Calculating... please wait
    osbl: 0xe6bacf7d
    amss: 0x38c9d05f
    hboot: 0x7eb3eb4c
    boot: 0xcf5ec298
    recovery: 0x339bbe8 (7 numbers/letters instead of 8?)
    system: 0xfe5c8f34

    Press power key to go back."

    C:\Program Files\Android\android-sdk\platform-tools>fastboot flash recovery reco
    very.img
    sending 'recovery' (3624 KB)...
    OKAY [ 1.188s]
    writing 'recovery'...
    (bootloader) signature checking...
    FAILED (remote: signature verify fail)
    finished. total time: 2.203s

    C:\Program Files\Android\android-sdk\platform-tools>fastboot oem powerdown
    ...
    OKAY [ 0.031s]
    finished. total time: 0.063s (it shut down the phone normally.)

    C:\Program Files\Android\android-sdk\platform-tools>fastboot oem check_emmc
    ...
    (bootloader) This eMMC is not made from Micron.MID=21.
    (bootloader) eMMC should not be Micron's
    OKAY [ 0.031s]
    finished. total time: 0.031s

    C:\Program Files\Android\android-sdk\platform-tools>fastboot oem check_emmc_mid
    ...
    (bootloader) Manufacturer ID, MID=15
    (bootloader) eMMC should be samsung
    OKAY [ 0.016s]
    finished. total time: 0.016s

    C:\Program Files\Android\android-sdk\platform-tools>fastboot oem list_partition_
    emmc
    ...
    (bootloader) index, type, start, num
    (bootloader) 0, 0x4D, 0x1, 0x3E8
    (bootloader) 1, 0x45, 0x3E9, 0x80
    (bootloader) 2, 0x46, 0x469, 0x2328
    (bootloader) 3, 0x5, 0x2791, 0x43186E
    OKAY [ 0.031s]
    finished. total time: 0.031s

    C:\Program Files\Android\android-sdk\platform-tools>fastboot oem heap
    ...
    (bootloader) Total free heap size: 710942216 Bytes (0x2A601E08)
    (bootloader) Max. free heap segment size: 373293056 Bytes (0x16400000)
    (bootloader) Max. free NPC heap segment size: 373293056 Bytes (0x16400000
    (bootloader) )
    OKAY [ 0.031s]
    finished. total time: 0.031s

    C:\Program Files\Android\android-sdk\platform-tools>fastboot oem keytest
    ...
    (bootloader) start keypad testing ...
    (bootloader) <HOME>
    (bootloader) <MENU ON QWERTY>
    (bootloader) <SEND>
    (bootloader) <POWER>
    (bootloader) <VOL UP>
    (bootloader) <VOL DOWN>
    (bootloader) <ACTION>
    (bootloader) <ACTION>
    (bootloader) <BACK>
    (bootloader) keypad testing is finished.
    OKAY [ 28.125s]
    finished. total time: 28.125s

    C:\Program Files\Android\android-sdk\platform-tools>fastboot oem boot
    ...
    (bootloader) setup_tag addr=0xA0000100 cmdline add=0x8D0879EC
    (bootloader) TAG:Ramdisk OK
    (bootloader) TAG:smi ok, size = 0
    (bootloader) TAG:hwid 0x0
    (bootloader) TAG:skuid 0x24801
    (bootloader) TAG:hero panel = 0x1
    (bootloader) TAG:engineerid = 0x6
    (bootloader) MCP dual-die
    (bootloader) MCP dual-die
    (bootloader) TAG:mono-die = 0x0
    (bootloader) Device CID is not super CID
    (bootloader) CID is VIDEO001
    (bootloader) setting->cid::VIDEO001
    (bootloader) serial number: SH16KRM01484
    (bootloader) commandline from head: no_console_suspend=1
    (bootloader) command line length =506
    (bootloader) active commandline: board_glacier.disable_uart2=0 board_glac
    (bootloader) ier.usb_h2w_sw=0 board_glacier.disable_sdcard=0 diag.enabled
    (bootloader) =0 board_glacier.debug_uart=0 smisize=0 userdata_sel=0 andro
    (bootloader) idboot.emmc=true androidboot.baseband=26.09.04.26_M android
    (bootloader) boot.cid=VIDEO001 androidboot.batt_poweron=good_battery andr
    (bootloader) oidboot.carrier=CA_Videotron androidboot.mid=PD1510000 andro
    (bootloader) idboot.keycaps=qwerty androidboot.mode=normal androidboot.se
    (bootloader) rialno=SH16KRM01484 androidboot.bootloader=0.89.0005 zygote_
    (bootloader) oneshot=off kmemleak=off no_console_suspend=1
    (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) aARM_Partion[6].name=devlog
    (bootloader) aARM_Partion[7].name=pdata
    (bootloader) partition number=8
    (bootloader) Valid partition num=8
    (bootloader) jump_to_kernel: machine_id(2592), tags_addr(0x4000100), kern
    (bootloader) el_addr(0x4008000)
    (bootloader) -------------------hboot boot time:295842 msec
    FAILED (status read failed (Too many links))
    finished. total time: 8.266s

    C:\Program Files\Android\android-sdk\platform-tools>fastboot oem heap_test
    ...
    (bootloader) ======heap_test (Ver: 1.0)======
    (bootloader) heap_test <test_mode> <cyles> <break> <cache/non-cache> <ob
    (bootloader) verse/reverse> <seed/pattern>
    (bootloader) <test_mode> (0): Mix pattern mode -> heap_test 0 <cy
    (bootloader) les> <break>
    (bootloader) <test_mode> (1): Fix pattern mode -> heap_test 1 <cy
    (bootloader) les> <break>
    (bootloader) <test_mode> (2): Random pattern mode -> heap_test 2 <cy
    (bootloader) les> <break>
    (bootloader) <test_mode> (3): Assign seed mode -> heap_test 3 <cyles
    (bootloader) > <break> <cache/non-cache> <obverse/reverse> <seed>
    (bootloader) <test_mode> (4): Assign fix pattern mode -> heap_test 4 <cy
    (bootloader) les> <break> <cache/non-cache> <obverse/reverse> <pattern>
    (bootloader) <cyles> The number of testing cycle
    (bootloader) <break> Command break off when RAM issue occurs 0:Not break
    (bootloader) off 1:Break off when RAM issue occurs
    (bootloader) <cache/non-cache> use cache or non-cache memory space 0:cac
    (bootloader) he 1:non-cache
    (bootloader) <obverse/reverse> assign the direction of scanning 0obvers
    (bootloader) e 1:reverse
    (bootloader) <seed/pattern> seed to create random pattern for each byte
    (bootloader) / pattern for every byte
    OKAY [ 0.109s]
    finished. total time: 0.109s

    C:\Program Files\Android\android-sdk\platform-tools>fastboot oem get_wp_info_emm
    c
    ...
    (bootloader) eMMC write protection group size = 8192
    OKAY [ 0.016s]
    finished. total time: 0.016s

    C:\Program Files\Android\android-sdk\platform-tools>fastboot oem get_sector_info
    _emmc
    ...
    (bootloader) Available eMMC Sector = 4407295
    OKAY [ 0.031s]
    finished. total time: 0.031s

    C:\Program Files\Android\android-sdk\platform-tools>fastboot oem task 28
    ...
    (bootloader) Format start
    (bootloader) erase sector 1343488 ~ 3749886 (2406399) -- phone hanged, nothing actually happened

    C:\Program Files\Android\android-sdk\platform-tools>fastboot erase cache
    erasing 'cache'...
    FAILED (status read failed (Too many links))
    finished. total time: 3869.188s (battery ran out of power)

  2. #2
    Join Date
    Apr 2009
    Posts
    44
    Phone
    Nokia N95
    Carrier
    Rogers Wireless
    Feedback Score
    0
    Here's what I'd like to know:

    1) How can I put my phone into download mode? That seems to be the only way right now to enable adb and flash the phone (or at least get the info to make a gold card)
    2) What does status read failed (too many links) mean?
    3) Is it normal that the crc for recovery has 7 numbers?
    4) Is there a way to boot into download mode with fastboot.exe?
    Last edited by everett1911; 05-15-2012 at 12:21 AM.

  3. #3
    Join Date
    Apr 2009
    Posts
    44
    Phone
    Nokia N95
    Carrier
    Rogers Wireless
    Feedback Score
    0
    anyone, please?

  4. #4
    Join Date
    Oct 2007
    Posts
    2
    Feedback Score
    0


    Yeah I have exactly the same problem i mean everything you have i do and its the exact same but its weird when i try to do PD15IMG.zip it goes through it and when i say yes to it, it freezes on first one, the bootloader. No where does it tell me my emmc chip is bad so screw it I am going to try the unbrickable mod even though glacier is not supported what is the worst that can happen? My phone doesnt work anyways, but if you have found anything out let me know and I will let you know what happens with the mod, thanks.

  5. #5
    Join Date
    Apr 2009
    Posts
    44
    Phone
    Nokia N95
    Carrier
    Rogers Wireless
    Feedback Score
    0
    the only thing I found out about it is that its screen really didn't like being hit with a hammer.

    needless to say, it's in the garbage now.

  6. #6
    Join Date
    Apr 2008
    Posts
    233
    Feedback Score
    0
    The garbage is the best for it. It is not worth all the frustration. I bought a mytouch 4g for my wife a few weeks ago on eBay and had to return it for that very reason. It was working fine and then one day it was stuck at the logo and would not go pass it no matter what.

    Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
    I need some judges at my website for a contest, PM me for more info.

Similar Threads

  1. bricked my slvr l7 phone !_! please help!!!!!!!
    By starscalling in forum Motorola Modding
    Replies: 3
    Last Post: 04-20-2007, 10:23 AM
  2. Possibly bricked W550, please help!
    By Lunatikbunnie in forum Sony Ericsson Modding
    Replies: 8
    Last Post: 01-26-2007, 09:56 AM
  3. v400 - BLACK screen = Brick? Please help...
    By PRELUDiCON in forum Motorola Phone Problems
    Replies: 8
    Last Post: 12-16-2006, 12:12 AM
  4. v400 - BLACK screen = Brick? Please help...
    By PRELUDiCON in forum Motorola
    Replies: 5
    Last Post: 12-15-2006, 08:34 PM
  5. Please help. I bricked my MDA.
    By SeaniePants in forum Windows Mobile Devices
    Replies: 8
    Last Post: 08-18-2006, 12:47 PM

Tags for this Thread

Bookmarks