Just Bootloader/Fastboot - HTC Wildfire S

Hello
First I am sorry for my bad english.
To my problem:
I have a WFS that absolutely does not want to boot. The only thing that still works is the bootloader and fastboot. No matter what I do, it always ends in a Bootloop. Be it a normal start, recovery or factory reset. 've Re-flashed via PG76IMG.zip/RUU up and play new recovery via fastboot. Neither the original nor CWM recovery can be started. The flash was always confirmed with OK but then I end up back in just a Bootloop. The Bootloop seems no matter what I always do the same, it takes about 3 seconds for the HTC logo and then it restarts. Maybe someone here has an idea what I could try?
Here's the info from the phone:
*** RELOCKED ***
MARVEL PVT SHIP S-ON RH
HBOOT-1.09.0099
MICROP-0451
RADIO-7.57.39.10M
Feb 8 2012, 18:29:31
Edit:
I have tried the following:
fastboot oem boot
...
(bootloader) setup_tag addr=0x60000100 cmdline add=0x9D0746B8
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x28806
(bootloader) TAG:hero panel = 0x5
(bootloader) TAG:engineerid = 0x0
(bootloader) MCP dual-die
(bootloader) MCP dual-die
(bootloader) TAG:mono-die = 0x0
(bootloader) TAG:TP = 1
(bootloader) Device CID is not super CID
(bootloader) CID is HTC__102
(bootloader) setting->cid::HTC__102
(bootloader) serial number: SH2*********
(bootloader) commandline from head: no_console_suspend=1 console=null
(bootloader) command line length =535
(bootloader) active commandline: board_marvel.disable_uart3=0 board_marve
(bootloader) l.usb_h2w_sw=0 board_marvel.disable_sdcard=0 diag.enabled=0
(bootloader) board_marvel.debug_uart=0 smisize=0 userdata_sel=0 androidbo
(bootloader) ot.emmc=false androidboot.pagesize=2048 androidboot.baseban
(bootloader) d=7.57.39.10M androidboot.cid=HTC__102 androidboot.batt_powe
(bootloader) ron=good_battery androidboot.carrier=HTC-GER androidboot.mid
(bootloader) =PG7610000 androidboot.keycaps=qwerty androidboot.mode=norma
(bootloader) l androidboot.serialno=SH2********* androidboot.bootloader=1
(bootloader) .09.0099 zygote_oneshot=off kmemleak=off no_console_suspend=
(bootloader) 1 console=null
(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) partition number=7
(bootloader) Valid partition num=7
(bootloader) Delay 99993(us) for dpram command before goto AMSS...
FAILED (status read failed (Too many links))
finished. total time: 1.199s
And then...:
IMAGE CRC
osbl: 0x0
amss: 0x0
hboot: 0xF685DEFF
boot: 0xAC0E9C41
recovery: 0xC2B13A0A
system: 0x23F3082D
Is OSBL/AMSS broken and it comes from?

Can be closed...

Related

inding out InfoCID for G2?

I am trying to get root on a T-Mobile G2 that has obtained the 1.72 OTA update and I have followed the commands from the G2 Downgrading Thread on using ADB and Fastboot but this is the output I get:
C:\Users\ZeroXR\Downloads\android-sdk-windows\platform-tools>fastboot oem boot
...
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8D0876E8
(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 not super CID
(bootloader) CID is T-MOB010
(bootloader) setting->cid::T-MOB010
(bootloader) serial number: HT09MR211333
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =462
(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.03.02.26_M androidboot
(bootloader) .cid=T-MOB010 androidboot.batt_poweron=good_battery androidb
(bootloader) oot.carrier=TMUS androidboot.mid=PC1010000 androidboot.keyca
(bootloader) ps=qwerty androidboot.mode=normal androidboot.serialno=HT09M
(bootloader) R211333 androidboot.bootloader=0.82.0000 no_console_suspend=
(bootloader) 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) partition number=7
(bootloader) Valid partition num=7
(bootloader) jump_to_kernel: machine_id(2245), tags_addr(0x4000100), kern
(bootloader) el_addr(0x4008000)
(bootloader) -------------------hboot boot time:93835 msec
FAILED (status read failed (Too many links))
finished. total time: 8.418s
Some post I have seen say the CID is the InfoCID and some say that it isn't... Is anyone able to give a definitive answer? I would like to know whether or not I have to make a goldcard to get root.
Yeah, it means your CID (T-MOB010). The downgrade guide you are trying to follow isn't for the G2 though, only the Desire Z. You also don't have the 1.72 OTA. The G2's have only received a 1.22 OTA (with the newer G2's having the update pre-installed), which doesn't needed to be downgraded in order to root.
You can just follow the guide in the Wiki.
Thanks for the verification because I was so leery of rooting from all the stuff I was reading about the downgrading then rooting. I just rooted my phone and I am extremely happy to have it rooted!

[Q] Desire boot problems

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

Can't boot into recovery/OS, only hboot/fastboot works

So..
The patient:
A completely stock HTC Desire Z.
Code:
VISION PVT SHIP S-ON
HBOOT-0.85.0013
MICROP-0425
RADIO-26.10.04.03_M
eMMC-boot
Apr 11 2011,23:36:27
What happened?
Got home, and connected the phone to my computer via USB cable to charge, as I do every time.
However this time I have also launched and forgot to exit Blizzard Authenticator app (I'm a Diablo 3 fan )), which, as I have previously noticed, causes a garbage collection extremely often (only by displaying a progress bar which is constantly moving).
There were two times previously where I left this app open and after an hour or so the phone automatically rebooted itself.
So.. it happened again: I noticed a brief vibration from the phone, as it does when it starts to boot and shows the HTC logo. So I took it in the hand to see what's happening and it was extremely hot, and after a few seconds of showing the HTC logo it rebooted, then showed HTC logo again, rebooted, and looped until I pulled the battery out.
I thought it must have some thermal protection which tries to save the phone from overheating and is constantly shutting it off. So I pulled the battery out and left it to cool-down.
After that - same thing, when you put in the battery and push the power button (or connect a USB cable), it displays the HTC logo for a few seconds and then reboots, starting a boot loop.
So, the summary:
The phone will only boot to hboot while holding down the VOLUME DOWN button.
It won't boot into recovery if I select it from the hboot/fastboot menu. It does exactly the same (boot-looping).
hboot/fasboot works perfectly fine, I am able to interact with the phone while in fastboot USB mode.
I was able to use stock RUU, it flashed everything fine, not a single error, but the result was the same - still boot-looping.
I was able to upgrade hboot and unlock the bootloader via htcdev.com and successfully flash the ClockWorkMod recovery, but still I am not able to boot to it because of boot-loop.
I tried flashing official ROM from RUU by using fastboot oem rebootRUU so that I could see what's actually happening, expecting that I ran into the same issue as a few other people on this forum (the "re-flush image immediately" issue, where the zip must have been flashed multiple times before succeeding), but no, the ROM flashed perfectly fine. And still the same result: boot loop.
So, after two days of browsing, reading, searching and trying I finally ran out of ideas.
Here goes some additional info, if it could prove useful while diagnosing the problem:
Code:
FROST:~ frost$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.85.0013
(bootloader) version-baseband: 26.10.04.03_M
(bootloader) version-cpld: None
(bootloader) version-microp: 0425
(bootloader) version-main: 2.42.405.2
(bootloader) serialno: SH0*********
(bootloader) imei: ***************
(bootloader) product: vision
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PC1011000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: low
(bootloader) battery-voltage: 3570mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 81c588a7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.003s
Code:
FROST:Downloads frost$ fastboot oem boot
...
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8D0878FC
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x25209
(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 not super CID
(bootloader) CID is HTC__Y13
(bootloader) setting->cid::HTC__Y13
(bootloader) serial number: SH0*********
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =497
(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.10.04.03_M androidboot
(bootloader) .cid=HTC__Y13 androidboot.batt_poweron=good_battery androidb
(bootloader) oot.carrier=HTC-Nor androidboot.mid=PC1011000 androidboot.ke
(bootloader) ycaps=qwerty androidboot.mode=normal androidboot.serialno=SH
(bootloader) 0********* androidboot.bootloader=0.85.0013 zygote_oneshot=o
(bootloader) ff 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(2245), tags_addr(0x4000100), kern
(bootloader) el_addr(0x4008000)
(bootloader) -------------------hboot boot time:15618 msec
* the phone reboots at this point, so naturally, USB connection is lost, causing the output below: *
Code:
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 8.358s
Any ideas of what's causing this? And/or how to fix this?
Thanks in advance.
I think you're knocking on a wrong door, this is Desire (only without Z) section...
Yes, I must have accidentally posted here, sorry. This thread may now be deleted.

[Q] Need Backup of Stock Rom For HTC Desire Z A7272 (CID: HTC__038)

Hi All,
It look, I have a semi bricked phone (HTC Desire Z A7272), But I can boot the phone into recovery.
It hangs on HTC Logo, USB Debugging is not enabled.
I Need the Stock Backup for my phone, If any one have it please post it on this thread.
Here is the Boot Loader status and log.
*****UNLOCKED********
VISION PVT S-ON
HBOOT-0.85.0015
MICROP-0425
RADIO-26.10.04.03_M
eMMC-boot
Dec 20 2011, 16:21:13
****************************
C:\adtx86SDK\sdk\platform-tools>fastboot oem boot
< waiting for device >
...
(bootloader) setup_tag addr=0xC0000100 cmdline add=0x8D0935B4
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x25209
(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 not super CID
(bootloader) CID is HTC__038
(bootloader) setting->cid::HTC__038
(bootloader) serial number: SH0CDRT03500
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =499
(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.10.04.03_M androidboot
(bootloader) .cid=HTC__038 androidboot.batt_poweron=good_battery androidb
(bootloader) oot.carrier=HTC-India androidboot.mid=PC1011000 androidboot.
(bootloader) keycaps=qwerty androidboot.mode=normal androidboot.serialno=
(bootloader) SH0CDRT03500 androidboot.bootloader=0.85.0015 zygote_oneshot
(bootloader) =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(2245), tags_addr(0x4000100), kern
(bootloader) el_addr(0x4008000)
(bootloader) -------------------hboot boot time:87690 msec
FAILED (status read failed (Too many links))
finished. total time: 8.365s
Also I need suggestion weather I can recover my phone in this way or not.
Please help me out.....
Delete...
I'm not sure you could flash someone else back-up...
What is your recovery?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Official RUU_Vision_hTC_Asia_India CID: HTC_038
demkantor said:
What is your recovery?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi,
Thanks for the response, I need the Backup Or
Please give me the link from where I can Download official RUU for my phone, so that I can flash my rom.
C:\adtx86SDK\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.85.0015
(bootloader) version-baseband: 26.10.04.03_M
(bootloader) version-cpld: None
(bootloader) version-microp: 0425
(bootloader) version-main: 2.42.0.0
(bootloader) serialno: SH0CDRT03500
(bootloader) imei: 352212047348870
(bootloader) product: vision
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PC1011000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 3748mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3cd54d84
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.003s
http://forum.xda-developers.com/showthread.php?t=2094420
Official RUU_Vision_hTC_Asia_India CID: HTC_038
Kéno40 said:
http://forum.xda-developers.com/showthread.php?t=2094420
Click to expand...
Click to collapse
Hi,
Thanks for the quick reply.
I tried the below given RUU's but it gives me Unknown Error while running the RUU's and sending the update to the phone.
RUU_Vision_Gingerbread_S_hTC_Asia_TW_2.42.709.10_Radio_12.56.60.25_26.10.04.03_M_release_201045_signed.exe
RUU_Vision_Gingerbread_S_HTC_WWE_2.42.405.3_Radio_12.56.60.25_26.10.04.03_M_release_224299_signed.exe
I need the RUU for below given Information since my phone is not S-OFF.
RADIO-26.10.04.03_M
cid::HTC__038
version-main: 2.42.0.0 (Currently it's showing this)
OR
version-main: 2.42.709.2 (It used to be this one)

[Q] New boat anchor?

Took a flyer on a $15 evo 4g looks like I overpaid, anyone have bootloop recovery not available brick?
I've tried recovery/roms pushed from fastboot and from zip updates and the same thing boot screen for a sec black bootscreen again reboot. Pwr vol+ works but recovery is will not come up, wipe avail but not factory reset choice. I've pushed various recommended recovery and boot images, and they all say success but have zero effect. I'm guessing it's that s-on is on but with out recovery I'm not having any luck, any ideas?
***Unlocked****
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-2.18.0001
MICROP-041f
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.0.15
Dec 21 2011,12:50:32
partial list of recs/roms I've tried...
htc_supersonic-deck-pb25-a2sd
PC36IMG_ra-supersonic-4.3-smelkus-reloaded2
PC36IMG_SuperSonic_GB_Sprint_WWE_4.54.651.1_Radio_ 2.15.00.0808_NV_2.15_release_220182_signed
PC36IMG_RA_2.3
PC36IMG_Clockwork_2.5.0.1
PC36IMG_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2 .15.00.11.19_NV_1.90_release_161482_signed
C:\adb>fastboot oem boot
...
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8E07BD2C
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x23301
(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 not super CID
(bootloader) CID is SPCS_001
(bootloader) setting->cid::SPCS_001
(bootloader) serial number: HT136HL00237
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =512
(bootloader) active commandline: board_supersonic.disable_uart3=0 board_s
(bootloader) upersonic.usb_h2w_sw=0 board_supersonic.disable_sdcard=0 dia
(bootloader) g.enabled=0 board_supersonic.debug_uart=0 smisize=0 userdata
(bootloader) _sel=0 androidboot.emmc=false androidboot.baseband=2.15.00.
(bootloader) 01.15 androidboot.cid=SPCS_001 androidboot.batt_poweron=die_
(bootloader) battery androidboot.carrier=COMMON androidboot.mid=PC3610000
(bootloader) androidboot.keycaps=qwerty androidboot.mode=normal androidb
(bootloader) oot.serialno=HT136HL00237 androidboot.bootloader=2.18.0001 z
(bootloader) ygote_oneshot=off kmemleak=off no_console_suspend=1
(bootloader) aARM_Partion[0].name=wimax
(bootloader) aARM_Partion[1].name=misc
(bootloader) aARM_Partion[2].name=recovery
(bootloader) aARM_Partion[3].name=boot
(bootloader) aARM_Partion[4].name=system
(bootloader) aARM_Partion[5].name=cache
(bootloader) aARM_Partion[6].name=userdata
(bootloader) partition number=7
(bootloader) Valid partition num=7
(bootloader) Delay 99998(us) for dpram command before goto AMSS...
(bootloader) jump_to_kernel: machine_id(2433), tags_addr(0x20000100), ker
(bootloader) nel_addr(0x20008000)
(bootloader) -------------------hboot boot time:133908 msec
FAILED (status read failed (Too many links))
finished. total time: 5.845s
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.18.0001
(bootloader) version-baseband: 2.15.00.01.15
(bootloader) version-cpld: None
(bootloader) version-microp: 041f
(bootloader) version-main: 5.07.651.1
(bootloader) serialno: HT136HL00237
(bootloader) imei: 355195000000017
(bootloader) product: supersonic
(bootloader) platform: HBOOT-8x50
(bootloader) modelid: PC3610000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3438mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 4b46e889
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.029s
So when you use the PC36IMG to flash a recovery what happens? Any error messages or failures? From what you have here looks like only a stock recovery is installed.
The bootloader should boot scan the file and ask you if you want to upgrade. Does this happen for you?
Sent from my GT-N7105 using XDA Premium 4 mobile app
Everything acts like it works, blue bar installing from a zip or pushing from fastboot gives "success" but they are not actually being installed as far as I can tell. I'm not sure if it's because it s-on? I got root with the htcdev method but getting s-off for this version is pretty murky the guide from this just mentions downgrading and a link but doesn't give clear what/how to downgrade and if a cust rec won't flash I doubt downgrading will either.. "Fastboot device" sees the phone but "adb device" doesn't, is adb supposed to use the "bootoader driver", even though I tried switching the driver still did not allow adb to see it I've never found a clear explanation of the diff drivers offered?..
What recovery version are you using? I highly recommend the Smelkus recovery for this particular device.
Sent from my HTC M8
Thanks, but I've passed this on to the next over confident ebayer, hope he has more skillz, btw I tried smelkus with no effect, other than getting root I don't think anything else actually did anything I fb flashed at least 6 diff. recovery img's flashed the boot, unzipped the stock image and did "flash all", Zip updated with various recovery imgs of full stock, cyanogen and some 4.0 based installs and while most all them said "success" as far as I can tell nothing actually changed., hopefully they next guy needs it for parts..

Categories

Resources