Develop Bugs

USB bricked, what to do?

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

[Q] Desire stuck at boot screen

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

[Q] SD Card not recognized

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

Last desperate attempt to save My desire HD

I'm a total n00b, just wanted to get that out of the way first
I have acquired an HTC Desire HD which booted very slowly when I got it, and ran ok except that sms did not work. I was told it was unlocked and rooted.
I have been trying for days to un-root or revert back to a stock rom with no success. I only half understand what I'm doing and everything I try fails at some point and I seem to have totally fuc%&d the poor thing.
Now when I switch it on, it goes to the T-Mobile splash screen and sits there forever. I can boot into H-boot and run recovery (CWM Recovery installed). I can then mount usb storage and acces it from my PC via usb.
In HBOOT or FASTBOOT I can not connect to my PC via usb (I have installed the correct drivers and it used to connect before I "fixed it"):crying:
These are the phone stats
Code:
getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0029
(bootloader) version-baseband: 26.14.04.28_M
(bootloader) version-cpld: None
(bootloader) version-microp: 0438
(bootloader) version-main: 3.13.110.4
(bootloader) serialno: HT0CVRX10795
(bootloader) imei: 356299043105830
(bootloader) product: ace
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PD9810000
(bootloader) cidnum: T-MOB005
(bootloader) battery-status: good
(bootloader) battery-voltage: 4189mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: fcef1579
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) region-id: 0
all: Done!
finished. total time: 0.003s
...
(bootloader) setup_tag addr=0xC0000100 cmdline add=0x8D0985F8
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x26503
(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 T-MOB005
(bootloader) setting->cid::T-MOB005
(bootloader) serial number: HT0CVRX10795
(bootloader) commandline from head: no_console_suspend=1 wire.search_coun
(bootloader) t=5
(bootloader) command line length =510
(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.14.04.28_M androidboot.cid
(bootloader) =T-MOB005 androidboot.batt_poweron=good_battery androidboot.
(bootloader) carrier=TMUK androidboot.mid=PD9810000 androidboot.keycaps=q
(bootloader) werty androidboot.mode=normal androidboot.serialno=HT0CVRX10
(bootloader) 795 androidboot.bootloader=2.00.0029 zygote_oneshot=off kmem
(bootloader) leak=off no_console_suspend=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=local
(bootloader) aARM_Partion[5].name=cache
(bootloader) aARM_Partion[6].name=userdata
(bootloader) aARM_Partion[7].name=devlog
(bootloader) aARM_Partion[8].name=pdata
(bootloader) aARM_Partion[9].name=lib
(bootloader) partition number=10
(bootloader) Valid partition num=10
(bootloader) jump_to_kernel: machine_id(2844), tags_addr(0x4000100), kern
(bootloader) el_addr(0x4008000)
(bootloader) -------------------hboot boot time:73765 msec
FAILED (status read failed (Too many links))
finished. total time: 7.544s
Any help would be greatly appreciated.
Please be gentle with me.

sup3rbird said:
I'm a total n00b, just wanted to get that out of the way first
I have acquired an HTC Desire HD which booted very slowly when I got it, and ran ok except that sms did not work. I was told it was unlocked and rooted.
I have been trying for days to un-root or revert back to a stock rom with no success. I only half understand what I'm doing and everything I try fails at some point and I seem to have totally fuc%&d the poor thing.
Now when I switch it on, it goes to the T-Mobile splash screen and sits there forever. I can boot into H-boot and run recovery (CWM Recovery installed). I can then mount usb storage and acces it from my PC via usb.
In HBOOT or FASTBOOT I can not connect to my PC via usb (I have installed the correct drivers and it used to connect before I "fixed it"):crying:
These are the phone stats
Code:
getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0029
(bootloader) version-baseband: 26.14.04.28_M
(bootloader) version-cpld: None
(bootloader) version-microp: 0438
(bootloader) version-main: 3.13.110.4
(bootloader) serialno: HT0CVRX10795
(bootloader) imei: 356299043105830
(bootloader) product: ace
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PD9810000
(bootloader) cidnum: T-MOB005
(bootloader) battery-status: good
(bootloader) battery-voltage: 4189mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: fcef1579
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) region-id: 0
all: Done!
finished. total time: 0.003s
...
(bootloader) setup_tag addr=0xC0000100 cmdline add=0x8D0985F8
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x26503
(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 T-MOB005
(bootloader) setting->cid::T-MOB005
(bootloader) serial number: HT0CVRX10795
(bootloader) commandline from head: no_console_suspend=1 wire.search_coun
(bootloader) t=5
(bootloader) command line length =510
(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.14.04.28_M androidboot.cid
(bootloader) =T-MOB005 androidboot.batt_poweron=good_battery androidboot.
(bootloader) carrier=TMUK androidboot.mid=PD9810000 androidboot.keycaps=q
(bootloader) werty androidboot.mode=normal androidboot.serialno=HT0CVRX10
(bootloader) 795 androidboot.bootloader=2.00.0029 zygote_oneshot=off kmem
(bootloader) leak=off no_console_suspend=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=local
(bootloader) aARM_Partion[5].name=cache
(bootloader) aARM_Partion[6].name=userdata
(bootloader) aARM_Partion[7].name=devlog
(bootloader) aARM_Partion[8].name=pdata
(bootloader) aARM_Partion[9].name=lib
(bootloader) partition number=10
(bootloader) Valid partition num=10
(bootloader) jump_to_kernel: machine_id(2844), tags_addr(0x4000100), kern
(bootloader) el_addr(0x4008000)
(bootloader) -------------------hboot boot time:73765 msec
FAILED (status read failed (Too many links))
finished. total time: 7.544s
Any help would be greatly appreciated.
Please be gentle with me.
Click to expand...
Click to collapse
You could try returning to stock if that may help by extracting the PD98IMG.zip from a RUU and putting it in the root of your SD Card then booting into HBOOT

What does it say in hboot? Is your phone in fastboot (not hboot, not recovery, not system) when you try to use fastboot from the computer? What have you done so far?

thekool said:
You could try returning to stock if that may help by extracting the PD98IMG.zip from a RUU and putting it in the root of your SD Card then booting into HBOOT
Click to expand...
Click to collapse
I have tried that, but it didn't work. I'm not sure if I used a suitable RUU.
I also tried with a couple of downloaded stock PD98IMG.zip files which were recommended in various how-to posts.
When I boot into HBOOT the phone shows the following error
SD Checking........
Loading...[PD98DIAG.zip]
No image!
Loading...[PD98DIAG.nbh]
No image or wrong image!
Loading...[PD98IMG.zip]
No image!
Loading...[PD98IMG.nbh}
No image or wrong image!
and returns to the HBOOT screen

OK, first, you want a file named PD98IMG.zip, not PD98DIAG.zip. Second, what RUUs? Find one compatible with your phone's region. And I'm reiterating my questions from my earlier post.

bananagranola said:
What does it say in hboot? Is your phone in fastboot (not hboot, not recovery, not system) when you try to use fastboot from the computer? What have you done so far?
Click to expand...
Click to collapse
The phone is in fastboot when I try to connect via fastboot on my PC.
When I boot into hboot with a PD98IMG.zip file on a goldcard I get this error message
SD Checking........
Loading...[PD98DIAG.zip]
No image!
Loading...[PD98DIAG.nbh]
No image or wrong image!
Loading...[PD98IMG.zip]
No image!
Loading...[PD98IMG.nbh}
No image or wrong image!
If I try to install PD98IMG.zip file using recovery I get the following response
Finding update package...
Opening update package...
Installing update...
Installation aborted.
NB I've been continuing to fiddle with it and I am once again able to connect to the phone via usb when in fastboot mode!
I am running windows 7 x64 if that makes a difference

You can't install PD98IMGs from recovery. If you want to flash one, put it on the root of your sdcard, boot into hboot, and choose to update. Make sure it's a compatible one for DHD. However, since you have recovery apparently, why don't you just full wipe and flash a ROM from recovery? Android Revolution HD is very stable and stock-ish.
And again. What does it say in hboot? What have you done so far?

bananagranola said:
You can't install PD98IMGs from recovery. If you want to flash one, put it on the root of your sdcard, boot into hboot, and choose to update. Make sure it's a compatible one for DHD. However, since you have recovery apparently, why don't you just full wipe and flash a ROM from recovery? Android Revolution HD is very stable and stock-ish.
And again. What does it say in hboot? What have you done so far?
Click to expand...
Click to collapse
I have attached an image of the hboot screen and the image which I was trying to use. The inf says its suitable for my phone cid T-MOB005
I'v just downloaded the rom you recommended and copied it to my sd card. Wiping now.
HOLY CRAP!!!!! it's working this time and I'm not doing anything I didn't try before. I just needed someone to hold my hand for a bit:laugh:
Many Many Thanks guys, specially bananagranola for persevering with my ineptitude.
EDIT Ok, I got over-excited and spoke too soon, it went through the full install routine but on reboot it's just sitting on the t-mobile splash screen:crying:

sup3rbird said:
I have attached an image of the hboot screen and the image which I was trying to use. The inf says its suitable for my phone cid T-MOB005
I'v just downloaded the rom you recommended and copied it to my sd card. Wiping now.
HOLY CRAP!!!!! it's working this time and I'm not doing anything I didn't try before. I just needed someone to hold my hand for a bit:laugh:
Many Many Thanks guys, specially bananagranola for persevering with my ineptitude.
EDIT Ok, I got over-excited and spoke too soon, it went through the full install routine but on reboot it's just sitting on the t-mobile splash screen:crying:
Click to expand...
Click to collapse
Check that the name of the file is incorrect. It should be PD98IMG and not PB98
Sent from my ASUS Transformer Pad TF700T using xda app-developers app

Wait, so did you do the recovery thing or the hboot thing? If the recovery thing, since you're S-On unlocked, you need to flash the ROM zip's boot.img from fastboot each time you flash a ROM. "fastboot flash boot boot.img"

bananagranola said:
Wait, so did you do the recovery thing or the hboot thing? If the recovery thing, since you're S-On unlocked, you need to flash the ROM zip's boot.img from fastboot each time you flash a ROM. "fastboot flash boot boot.img"
Click to expand...
Click to collapse
Thanks for sticking with me
I tried the recovery thing.
Ok I have flashed the boot.img from the Revolution rom via fastboot. It says it was successful.
Please tell me exactly what I should do next (as if you were talking to a moron).
It's 3:30 am here and I'm getting more stupid by the minute.

Did you flash the ROM from recovery before flashing the boot? You need to do that first. Then the boot.img. Then reboot.

bananagranola said:
Did you flash the ROM from recovery before flashing the boot? You need to do that first. Then the boot.img. Then reboot.
Click to expand...
Click to collapse
I did it in the wrong order...................I'm wiping everything and starting again.
Right, I have flashed the rom from my sdcard using cwm recovery; how do I get from here to fastboot to flash the boot.img which I copied from the rom?
FYI . If I "reboot system now" from recovery I cannot go directly to fastboot. The phone will only reboot into the regular boot mode or recovery mode.
My only other available method for restarting the phone is to pull the battery as the power switch no longer works.
FINAL EDIT Got it sorted working 100%
Thanks for your help

[Q] Can I revive my G2 or is it bound to eternal sleep?

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