I know that there are lots of posts about this issue, but i think i ran down of options, so had to open up another one...
I had the touch on my desire broken maybe a year ago. I was using it like that for a year, until few weeks ago when i decided i should finally replace it. Have to notice here that the phone was working without any issue for all that time, even with broken touch. When I got the phone back with new touch from the repair shop, some issues came up...the wireless was not turning on (it was showing Error message), also the sd card was not recognized. So i returned it for another check, they fixed the wireless but the sd card problem is still there. The folks from the repair shop told me that they checked and from hardware point there was nothing wrong, so I should check for any software issue.
My device:
BRAVO PVT3 SHIP S-OFF
HBOOT-0.93.0001
TOUCH PANEL-SYNT0101
RADIO-5.17.05.23
Running on CM7.2.0.1-bravo
1. I tried another card, not working also.
2. Did factory reset, nothing changed.
3. Re-formatted the card as fat32 primary on my pc (where is readable without any problem), again nothing.
4. Tried the commands fastboot oem enableqxdm 0 and fastboot oem eraseconfig, the output tells everything ok but sd still not working.
Code:
C:\android-sdk-windows\platform-tools>fastboot oem enableqxdm 0
...
OKAY [ 0.092s]
finished. total time: 0.094s
C:\android-sdk-windows\platform-tools>fastboot oem eraseconfig
...
(bootloader) Erase config: complete
OKAY [ 0.092s]
finished. total time: 0.097s
5.Tried fastboot oem reboot, it says something like FAILED and then reboots...the output is as followed:
Code:
C:\android-sdk-windows\platform-tools>fastboot oem boot
...
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8E07F9F0
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x26A0D
(bootloader) TAG:hero panel = 0x3
(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 HTC__032
(bootloader) setting->cid::HTC__032
(bootloader) serial number: HT09HPL04877
(bootloader) commandline from head: no_console_suspend=1 msmsdcc_sdioirq=
(bootloader) 1 wire.search_count=5
(bootloader) command line length =466
(bootloader) active commandline: board_bravo.disable_uart3=0 board_bravo.
(bootloader) usb_h2w_sw=0 board_bravo.disable_sdcard=0 diag.enabled=0 boa
(bootloader) rd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
(bootloader) mmc=false androidboot.baseband=5.17.05.23 androidboot.cid=H
(bootloader) TC__032 androidboot.carrier=HTC-EastEurope androidboot.mid=P
(bootloader) B9920000 androidboot.keycaps=qwerty androidboot.mode=normal
(bootloader) androidboot.serialno=HT09HPL04877 androidboot.bootloader=0.9
(bootloader) 3.0001 no_console_suspend=1 msmsdcc_sdioirq=1 wire.search_co
(bootloader) unt=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) jump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker
(bootloader) nel_addr(0x20008000)
(bootloader) -------------------hboot boot time:629851 msec
FAILED (status read failed (Too many links))
finished. total time: 11.766s
6. I switched from CWM to AmonRa recovery, samo result.
7.I even tried by switching between unrevoked drivers and the official desire drivers, tried everything stated above, same result.
So did I miss anything? Which drivers should i use? After the two fastboot commands, should I reboot regular or reboot bootloader? Any advice is welcomed. Tx
Maybe you are usb bricked.
If you have 4ext recovery try usb brick fix from menu , if not install 4ext from fastboot and try then
Seems a strange coincidence that Wi-Fi and storage worked perfectly before the shop had it, afterwards they fixed the Wi-Fi (which they must have broken) but were unable to fix the storage which they're blaming on anything but themselves. Either take it back and fire some f'ks into them, or strip it down and reconnect everything yourself
Sent from my HTC Desire using Tapatalk 2
Related
I have an unrooted Desire, which doesn't work like it should anymore. When I try to boot it, it stucks on the first white screen with HTC logo.
When I take out the battery for a while, it will sometimes boot. But after an hour it will reboot itself, and get stuck in boot again.
Also, sometimes, the phone will try to boot, stays on for 5 seconds, turns itself off, and boots again, stays on 5 seconds, etc.
I can get into recovery, using volume down and power, and executed the 'fastboot oem boot' commando, with results:
C:\Users\Niek>fastboot oem boot
...
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8E07F9F0
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x21F04
(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 HTC__E11
(bootloader) setting->cid::HTC__E11
(bootloader) serial number: HT06RPL00507
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =423
(bootloader) active commandline: board_bravo.disable_uart3=0 board_bravo.
(bootloader) usb_h2w_sw=0 board_bravo.disable_sdcard=0 diag.enabled=0 boa
(bootloader) rd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
(bootloader) mmc=false androidboot.baseband=5.11.05.27 androidboot.cid=H
(bootloader) TC__E11 androidboot.carrier=HTC-Dutch androidboot.mid=PB9920
(bootloader) 000 androidboot.keycaps=qwerty androidboot.mode=normal andro
(bootloader) idboot.serialno=HT06RPL00507 androidboot.bootloader=0.93.000
(bootloader) 1 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) partition number=6
(bootloader) Valid partition num=6
(bootloader) mpu_nand_acpu_rw A1E 1000
(bootloader) jump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker
(bootloader) nel_addr(0x20008000)
(bootloader) -------------------hboot boot time:30551 msec
FAILED (status read failed (Too many links))
finished. total time: 4.830s
Click to expand...
Click to collapse
I'm not sure what this means.
try another usb cable or another usb port
remove battery from phone, then restart phone vol down + power, click fastboot before conecting USB cable (" waiting for phone"), conect cable .....
retry your command
I removed the battery, put it back in (else it won't boot ofc), vol down + power, clicked fastboot, on pc executed 'fastboot oem boot', plugged usb cable in:
C:\Users\Niek>fastboot oem boot
< waiting for device >
...
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8E07F9F0
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x21F04
(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 HTC__E11
(bootloader) setting->cid::HTC__E11
(bootloader) serial number: HT06RPL00507
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =423
(bootloader) active commandline: board_bravo.disable_uart3=0 board_bravo.
(bootloader) usb_h2w_sw=0 board_bravo.disable_sdcard=0 diag.enabled=0 boa
(bootloader) rd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
(bootloader) mmc=false androidboot.baseband=5.11.05.27 androidboot.cid=H
(bootloader) TC__E11 androidboot.carrier=HTC-Dutch androidboot.mid=PB9920
(bootloader) 000 androidboot.keycaps=qwerty androidboot.mode=normal andro
(bootloader) idboot.serialno=HT06RPL00507 androidboot.bootloader=0.93.000
(bootloader) 1 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) partition number=6
(bootloader) Valid partition num=6
(bootloader) mpu_nand_acpu_rw A1E 1000
(bootloader) jump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker
(bootloader) nel_addr(0x20008000)
(bootloader) -------------------hboot boot time:40362 msec
FAILED (status read failed (Too many links))
finished. total time: 7.080s
Click to expand...
Click to collapse
It did boot all the way though. There is no SD or SIM card in the phone.
Usb brick???
http://forum.xda-developers.com/showthread.php?t=691639
I says I need root, which I don't have.
When I try to root the phone, it fails, because in the process it needs to reboot several times, and every time in the last reboot, the boot fails..
http://forum.xda-developers.com/showthread.php?t=833953&highlight=desire&page=1
never used it but its the last chance you have, or its off to HTC your phone will have to go...
Unless anyone else can see a solution? Because i've never had this problem so I am far from an expert
Were you s-off and changed your hboot to one from alpharev?
MatDrOiD said:
Were you s-off and changed your hboot to one from alpharev?
Click to expand...
Click to collapse
It isn't my phone, and the owner said he didn't do anything special with it. So it is still as it was when he bought it.
---------- Post added at 01:36 AM ---------- Previous post was at 01:19 AM ----------
BigMrB said:
http://forum.xda-developers.com/showthread.php?t=833953&highlight=desire&page=1
never used it but its the last chance you have, or its off to HTC your phone will have to go...
Unless anyone else can see a solution? Because i've never had this problem so I am far from an expert
Click to expand...
Click to collapse
I did the root via the app, that worked (the temporary one), and also the usb brick fix worked.
This is what I did in a shell:
C:\Users\Niek>adb shell
$ su
su
# cat /sdcard/flash_image > /data/flash_image
cat /sdcard/flash_image > /data/flash_image
# cat /sdcard/mtd0.img > /data/mtd0.img
cat /sdcard/mtd0.img > /data/mtd0.img
# chmod 755 /data/flash_image
chmod 755 /data/flash_image
# /data/flash_image misc /data/mtd0.img
/data/flash_image misc /data/mtd0.img
Click to expand...
Click to collapse
When I rebooted the phone, it went into the boot - off - boot - off cycle again.
I ran the 'fastboot oem boot' command again:
C:\Users\Niek>fastboot oem boot
...
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8E07F9F0
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x21F04
(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 HTC__E11
(bootloader) setting->cid::HTC__E11
(bootloader) serial number: HT06RPL00507
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =423
(bootloader) active commandline: board_bravo.disable_uart3=0 board_bravo.
(bootloader) usb_h2w_sw=0 board_bravo.disable_sdcard=0 diag.enabled=0 boa
(bootloader) rd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
(bootloader) mmc=false androidboot.baseband=5.11.05.27 androidboot.cid=H
(bootloader) TC__E11 androidboot.carrier=HTC-Dutch androidboot.mid=PB9920
(bootloader) 000 androidboot.keycaps=qwerty androidboot.mode=normal andro
(bootloader) idboot.serialno=HT06RPL00507 androidboot.bootloader=0.93.000
(bootloader) 1 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) partition number=6
(bootloader) Valid partition num=6
(bootloader) mpu_nand_acpu_rw A1E 1000
(bootloader) jump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker
(bootloader) nel_addr(0x20008000)
(bootloader) -------------------hboot boot time:21557 msec
FAILED (status read failed (Too many links))
finished. total time: 4.770s
Click to expand...
Click to collapse
By the way, now it did the cycle again for 4-5 times, and gave 7 vibrates. Then nothing.
Sounds like motherboad brick to me.
Vibrate 7 times.... Oh dear
Motherboard failure i would guess.... send to HTC for repair i'm afraid
That's a very bad sign?
Well, then I'll give up.. There's a crack in the screen anyway, and repairing that and this problem is not worth it.
Thanks anyway
Resolved: It was an issue with the Leedroid beta rom I was using, installing the kernel update that is listed on his post on here fixed it up.
Hey all, I'm hoping I can get some help with this.
I just rooted my desire hd (telus version, if that matters) using this method: driphter.com/index.php?topic=3867.0. Now there are some posts on doing it differently with a telus version, but I belive this should have worked, and it did, perfectly, except can not access my phone via USB now. I have searched for solutions, the simpler one, using the fastboot oem eraseconfig which gives me this:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Dman>cd C:\AndroidFlasher\Data\
C:\AndroidFlasher\Data>fastboot oem eraseconfig
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.000s]
finished. total time: 0.000s
C:\AndroidFlasher\Data>
And after looking through the other guide (forum.xda-developers.com/showthread.php?t=691639) when I search for the cid, the output i get is :
C:\AndroidFlasher\Data>fastboot oem boot
...
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8D088398
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x27E03
(bootloader) TAG:hero panel = 0x1
(bootloader) TAG:engineerid = 0x0
(bootloader) MCP dual-die
(bootloader) MCP dual-die
(bootloader) TAG:mono-die = 0x0
(bootloader) Device CID is super CID
(bootloader) CID is super CID
(bootloader) Backup CID is TELUS001
(bootloader) setting->cid::TELUS001
(bootloader) serial number: SH15KTZ02927
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =459
(bootloader) active commandline: board_spade.disable_uart2=0 board_spade.
(bootloader) usb_h2w_sw=0 board_spade.disable_sdcard=0 diag.enabled=0 boa
(bootloader) rd_spade.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
(bootloader) mmc=true androidboot.baseband=26.03.02.26_M androidboot.cid
(bootloader) =TELUS001 androidboot.batt_poweron=good_battery androidboot.
(bootloader) carrier=TELUS androidboot.mid=PD9814000 androidboot.keycaps=
(bootloader) qwerty androidboot.mode=normal androidboot.serialno=SH15KTZ0
(bootloader) 2927 androidboot.bootloader=0.85.0007 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(2844), tags_addr(0x4000100), kern
(bootloader) el_addr(0x4008000)
(bootloader) -------------------hboot boot time:304537 msec
FAILED (status read failed (Too many links))
finished. total time: 10.419s
I have no mtd0.img file on my phone,
and, I have :
(bootloader) Device CID is super CID
(bootloader) CID is super CID
(bootloader) Backup CID is TELUS001
(bootloader) setting->cid::TELUS001
Does this mean I need to restore something, or do I use TELUS001..
Hope to get some input on this before I go ahead and mess something up.
Sorry by the way, this is my first time messing with rooting and android though Im decent with linux..
Other question, in the mtd0.iso provided, do I need to change the number at the end to anything?
Thanks a lot to anyone who can help.
Edit: after reading a little more, I think I don't completely understand flashing, and I shouldn't be expecting to find that file on my phone, though my output still seems a bit odd and I'm wondering if i should be restoring something rather that creating the image from the file provided. Also whether the mod I'm using etc has to be entered into the mtd0.img i download at all? or just the CID? Lastly, probably a stupid question, what is the flash_image file for....
Live and learn
A little bit more info, it shows up in devive monitor as android device on two computers but still dows not give me any options on the phone
My Desire ran out of power this night and now it wont boot. It's just stuck at the boot screen. I cant boot into recovery mode either. I tried the "clear storage" thingy, but no luck. I've tried with and without sim and sd cards, with different batteries etc. - I can only boot to hboot and fastboot menus.
I'm running Oxygen 2.3.2, got clockworkmod recovery and S-OFF.
From the Troubleshooting guide, I've tried flashing a new recovery with Android Flasher, but I just get the error "Error, your phone is not plugged in or drivers aren't installed"
If I tick the "i'm already in fastboot", nothing happens. No respons or whatever for 20 minutes.
I tried installing the latest RUU, but it won't detect the phone.
Fastboot is able to detect the phone when booted, I've placed the Oxygen rom as an update.zip on the SD-card and tried to re-flash it, but my skills seems to end here.
Any suggestions?
try using my guide and use cmd instead of android flasher
Tried, no luck.
Just flashed the recovery via fastboot, but it still can't boot. Below is output.
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recovery c:\recovery.img
sending 'recovery' (4216 KB)...
OKAY [ 0.608s]
writing 'recovery'...
OKAY [ 1.310s]
finished. total time: 1.919s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot oem gencheckpt
...
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8E07F9F0
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x21F04
(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 super CID
(bootloader) CID is super CID
(bootloader) Backup CID is HTC__Y13
(bootloader) setting->cid::HTC__Y13
(bootloader) serial number: HT03SPL08362
(bootloader) commandline from head: no_console_suspend=1 msmsdcc_sdioirq=
(bootloader) 1 wire.search_count=5
(bootloader) command line length =461
(bootloader) active commandline: board_bravo.disable_uart3=0 board_bravo.
(bootloader) usb_h2w_sw=0 board_bravo.disable_sdcard=0 diag.enabled=0 boa
(bootloader) rd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
(bootloader) mmc=false androidboot.baseband=5.11.05.27 androidboot.cid=H
(bootloader) TC__Y13 androidboot.carrier=HTC-Nor androidboot.mid=PB992000
(bootloader) 0 androidboot.keycaps=qwerty androidboot.mode=recovery andro
(bootloader) idboot.serialno=HT03SPL08362 androidboot.bootloader=6.93.100
(bootloader) 2 no_console_suspend=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) jump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker
(bootloader) nel_addr(0x20008000)
(bootloader) -------------------hboot boot time:875594 msec
When getting sick of the boot screen, I removed the usb cable and got this error.
Code:
FAILED (status read failed (Too many links))
Not much else todo. After some retries, i finally got to reflash the hboot to stock using the PB99IMG method and afterwards the RUU rom, after extracting it from the .exe.
It sucks and all data is lost, but it's better than buying a new phone.
May be caused by Recovery
I bought HTC Rhyme (Bliss) last week and I'm regretful !!! It worked perfectly till the night, when I put it on the dockstation to charge, but 15 mins later I saw it rebooting over and over and stuck on the green HTC logo !!! what people call soft brick or bootloop problem !!!
I tried factory reset, erase data and cache in recovery which didn't work.
I downloaded and installed RUU_Bliss_ICS_35_S_HTC_EU_2.14.401.2 from htcdev.com site, which didn't change anything. Also I flashed different boot.img , but no result.
I unlocked the bootloader using htcdev and flashed CWM 6 touch. Erased cache and dalvik, reinstalled RUU, didn't work!
I downloaded some custom roms for HTC Rhyme, but when I try to flash them in CWM, it says Can't open ... (bad) Installation aborted. !!! I changed the CWM to version 5, downloaded the roms again, but still the same error !!!
Flashed Dark side wipe cache and super wipe via CWM and installed RUU again, no luck !!!
Found the stock RUU (1.31.707.6) on a Russian forum, but I faced some difficulties downgrading !!! I got main version error at first, changed the main version using misc_version and then it said hboot version is older. I generated the mtd0.img , setup adb in CWM recovery and followed the instructions to flash it to the misc partition using flash_image, but it says failed with error: -1 !!! tried "dd if=/sdcard/mtd0.img of=/dev/block/mmcblk0p17" but still I get "hboot version is older" or "hboot version check failed" when I try to revert it back to stock rom.
I spent hours of time testing different methods (even the phone twisting method I found on youtube!!!) and I don't know what else to do !!! Maybe If I could flash a different rom or revert it back to stock i get rid of the damn bootloop !!!
"fastboot oem boot" output
>fastboot oem boot
...
(bootloader) setup_tag addr=0xC0000100 cmdline add=0x8D0D26EC
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x2C701
(bootloader) TAG:hero panel = 0x890037
(bootloader) TAG:engineerid = 0x0
(bootloader) MCP dual-die
(bootloader) MCP dual-die
(bootloader) TAG:mono-die = 0x0
(bootloader) TAG: PS ID = 0x0
(bootloader) Device CID is not super CID
(bootloader) CID is HTC__044
(bootloader) setting->cid::HTC__044
(bootloader) serial number: SH33EVV00786
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =599
(bootloader) active commandline: board_bliss.disable_uart2=0 board_bliss.
(bootloader) usb_h2w_sw=0 board_bliss.disable_sdcard=0 diag.enabled=0 boa
(bootloader) rd_bliss.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
(bootloader) mmc=true androidboot.pagesize=4096 skuid=0 ddt=20 ats=0 and
(bootloader) roidboot.lb=1 androidboot.baseband=3831.17.00.17_M androidbo
(bootloader) ot.cid=HTC__044 androidboot.devicerev=2 androidboot.batt_pow
(bootloader) eron=good_battery androidboot.carrier=HTC-Asia-SEA-WWE andro
(bootloader) idboot.mid=PI4610000 androidboot.keycaps=qwerty androidboot.
(bootloader) dq=PASS androidboot.mode=normal androidboot.serialno=SH33EVV
(bootloader) 00786 androidboot.bootloader=1.33.0000 zygote_oneshot=off no
(bootloader) _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) aARM_Partion[8].name=extra
(bootloader) partition number=9
(bootloader) Valid partition num=9
(bootloader) Delay 81565(us) for dpram command before goto AMSS...
(bootloader) jump_to_kernel: machine_id(3490), tags_addr(0x4400100), kern
(bootloader) el_addr(0x4408000)
(bootloader) -------------------hboot boot time:677838 msec
FAILED (status read failed (Too many links))
finished. total time: 8.450s
A while back I had posted about my problems with my G2.
"For a while now I've been running a MIUI ROM without problems.
Today, the phone didn't want to wake up from sleep (tried using trackpad and power button).
I pulled the battery and started the phone back up but after the boot animation it went to black screen and wouldn't do anything from there.
I wiped cache and rebooted, went through the app checking but somewhere in the process crashed and went to black screen.
After several failed tries of pulling the battery and trying to reboot but only getting black screen, I did a full wipe and tried installing a new ROM but have not been able to boot into it.
According to the ROM installation everything went fine, but when I boot the phone up it starts trying to boot the MIUI boot animation then goes to black screen even though I did a full wipe and flashed a new ROM.
After doing various full wipes and sdcard formats, the phone doesn't seem to want to boot into anything even if I flash a rom, and recovery keeps loading up in Safe Mode due to a problem with /cache."
After trying many different ways, I gave up and fired up my trusty G1.
I decided after almost a year to give the G2 another try and for some reason now it was working fine and let me flash a rom and boot into it.
Unfortunately soon after, errors kept popping it to the point that I rebooted into recovery to try to flash a different rom and see if it fixed the problem.
Apparently, all it did was make things worse.
Phone got stuck on bootscreen and since then won't boot into rom or recovery.
The only thing I can get it to do, aside from getting stuck on the white screen with "htc" then going black, is booting into the bootloader.
From there I can use fastboot and look at the system info but if I try to boot into recovery from there it flashes the white htc screen then screen goes black and nothing happens.
From bootloader:
VISION PVT ENG S-OFF
HBOOT-0.84.2000 (PC1010000)
MICROP-0425
RADIO-26.02.01.15_M2
eMMC-boot
Sep 9 2010, 15:56:38
From SYSTEM INFO:
SN-SH0C2R200230
LCD-SO
TOUCH PANEL-ATMELC12_20aaT
Commit-adbd7a75
OS Ver.-1.19.531.1
CID-11111111
eMMC-Sandisk 2151MB 4407295sectors
Is there anything I can do that will possibly save my phone?
Thanks in advance for any help.
Bootloader info looks good, you have the better of the two emmcs that were put in these phones
What I would do is flash all new firmware through fastboot
http://forum.xda-developers.com/showthread.php?t=2348266
At the bottom of the first thread in this link there is some info on "debricking" these phones. There will be a link in one of those threads for a PC10IMG.zip I made that may help you out, but if it doesn't work you may have dead nand... Hopefully not
Best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app
Thanks for the reply!
I started to go through some of the steps to recover with no luck yet.
I did run the "fastboot oem jump" and got this:
(bootloader) Error status=0x400008
(bootloader) [SD_HW_ERR] SD: read fail ..
(bootloader) DATA_TIMEOUT
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(453): error 13
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(453): error 2
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8D087B50
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x25200
(bootloader) TAG:hero panel = 0xF
(bootloader) TAG:engineerid = 0x4
(bootloader) MCP dual-die
(bootloader) MCP dual-die
(bootloader) TAG:mono-die = 0x0
(bootloader) Device CID is super CID
(bootloader) CID is super CID
(bootloader) Backup CID is T-MOB010
(bootloader) setting->cid::T-MOB010
(bootloader) serial number: SH0C2R200230
(bootloader) commandline from head: no_console_suspend=1 androidboot.seli
(bootloader) nux=permissive
(bootloader) command line length =494
(bootloader) active commandline: board_vision.disable_uart2=0 board_visio
(bootloader) n.usb_h2w_sw=0 board_vision.disable_sdcard=0 diag.enabled=0
(bootloader) board_vision.debug_uart=0 smisize=0 userdata_sel=0 androidbo
(bootloader) ot.emmc=true androidboot.baseband=26.02.01.15_M2 androidboo
(bootloader) t.cid=T-MOB010 androidboot.batt_poweron=good_battery android
(bootloader) boot.carrier=TMUS androidboot.mid=PC1010000 androidboot.keyc
(bootloader) aps=qwerty androidboot.mode=normal androidboot.serialno=SH0C
(bootloader) 2R200230 androidboot.bootloader=0.84.2000 no_console_suspend
(bootloader) =1 androidboot.selinux=permissive
(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(2245), tags_addr(0x4000100), kern
(bootloader) el_addr(0x4008000)
(bootloader) -------------------hboot boot time:94512 msec
There's a few errors right at the beginning but not sure what those mean.
It also just sits at the white htc screen and never does anything.
Went through the next step of erasing recovery and flashing the one included in the post but still no luck.
I then entered the "fastboot erase system -w" command and it seemed to be fine erasing everything but i saw some errors with formatting.
If you need any other information that could possibly help understand my problem more just let me know.
Thanks!
http://forum.xda-developers.com/showthread.php?t=1728208
See post 30
If it doesn't work for you I'm afraid your phone is toast
Sent from my Nexus 4 using XDA Premium 4 mobile app