Warning about app2sd ! and gathering data about the cause :-D

[Guest WolfspiritM]

for fastboot it is ok, but with adb no, so we can't change nothing as we can mount /system in RW only with adb

So did you try the following?

1. Connect the Phone with USB

2. Boot in Bootloader (Back key while turning on)

3. do step1 of the rooting process again.

AFAIK this step will overwrite the recovery partition on the phone and maybe bring you USB back?

If you still have USB in fastboot mode, I won't say, that the phone is bricked...

Greetings

Spirit

[Guest geek78]

So did you try the following?

1. Connect the Phone with USB

2. Boot in Bootloader (Back key while turning on)

3. do step1 of the rooting process again.

AFAIK this step will overwrite the recovery partition on the phone and maybe bring you USB back?

If you still have USB in fastboot mode, I won't say, that the phone is bricked...

Greetings

Spirit

Yes off course, many times, with different microsd cards, PCs, USB cable .... If we have a signed NBH could try something else ... Never mind (for me) I will receive a new one from Orange next week :P

[Guest WolfspiritM]

Hm yeah...that's weird.

The next step I'd try, would be to unroot with the official HTC RUU:

http://android.modaco.com/content/htc-desi...our-htc-desire/

and then try if the phone works as before. After that I'd try to reroot again.

[Guest geek78]

Hm yeah...that's weird.

The next step I'd try, would be to unroot with the official HTC RUU:

http://android.modaco.com/content/htc-desi...our-htc-desire/

and then try if the phone works as before. After that I'd try to reroot again.

Allready done...

[Guest nilezon]

Important question:

Did anyone brick their phone without having a goldcard in the phone?

We have a theory that the goldcard is a contributing factor.

[Guest ZiCoN]

Important question:

Did anyone brick their phone without having a goldcard in the phone?

We have a theory that the goldcard is a contributing factor.

Could this mean, trying step1.sh without the goldcard could fix this? I have a non-branded desire, so in theory I shouldn't need goldcard

[Guest slamslugeren]

I didn't have my goldcard in the phone when it happened.

[Guest ZiCoN]

Well... no goldcard-step1-try is the same... Ran the "unroot.exe" and I'm considering going to the store next week with "I don't know what happend look, saying I just wanted to restore defaults and have NO idea what happend... please sir, may I have another?

[Guest stevebrush]

mine is unbranded too... I made a goldcard as first step but realize I don't need one.

is the recovery partition at mtdblock2 ? I would try to mount it to see inside...

if the step1 flash the recovery partition, may be paul can 'incorporate' the step2 (pushed files) inside, so at least, we can get the green recovery mod everytime we enter recovery and we cant flash everything without adb...

[Guest zanshin]

I guess this is why the calls get hung up:

I can repeat that bug again and again.

If you want I can post the complete stack trace

I/DEBUG ( 53): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

1859 I/DEBUG ( 53): Build fingerprint: 'htc_europe/htc_bravo/bravo/bravo:2.1-update1/ERE27/150129:userdebug/test-keys'

1860 I/DEBUG ( 53): pid: 54, tid: 63 >>> /system/bin/rild <<<

1861 I/DEBUG ( 53): signal 11 (SIGSEGV), fault addr 00000004

1862 I/DEBUG ( 53): r0 100ffb0c r1 00000001 r2 000000ff r3 000000ff

1863 I/DEBUG ( 53): r4 00000000 r5 afe3ae08 r6 0000c988 r7 000000ff

1864 I/DEBUG ( 53): r8 00100000 r9 ae4069fd 10 10000000 fp 00000000

1865 I/DEBUG ( 53): ip afe13aa8 sp 100ffa70 lr 8004cbfb pc afe13ab6 cpsr 00000030

this is the radio I use: radio-4.05.00.11

Edited May 10, 2010 by zanshin

[Guest dimor]

where's that stacktrace from?

[Guest zanshin]

Just some things in noticed in dmesg

Pasted from xda:

cat /sys/devices/platform/msm_hsusb/usb_function_switch

usb_mass_storage:enable

adb:enable

diag:disable

serial:disable

ether:disable

modem:disable

nmea:disable

dmesg says:

<6>[ 5.284698] usb_function_register() 'adb'

185 <6>[ 5.284881] SMD: ch 40 0 -> 1

186 <6>[ 5.284942] SMD: ch 40 1 -> 2

187 <6>[ 5.285125] usb_function_register() 'diag'

188 <6>[ 5.285186] usb0 (): not using net_device_ops yet

189 <6>[ 5.285552] usb_function_register() 'ether'

190 <6>[ 5.285949] usb_function_register() 'modem'

191 <6>[ 5.285980] usb_function_register() 'nmea'

192 <6>[ 5.285980] usb_function_register() 'serial'

Why is usb_mass not created?

A few lines further:

<3>[ 5.435089] msm_i2c msm_i2c.0: error, status 43c8 (40)

<3>[ 5.435119] msm_i2c msm_i2c.0: Error during data xfer (-5) (40)

and further:

52 <3>[ 6.230957] msm_i2c msm_i2c.0: error, status 43c8 (18)

253 <3>[ 6.230957] msm_i2c msm_i2c.0: Error during data xfer (-5) (18)

254 <4>[ 6.231018] ds2482 0-0018: i2c write c3 87 failed, -5, retries left 5

255 <3>[ 6.231323] msm_i2c msm_i2c.0: error, status 43c8 (18)

256 <3>[ 6.231353] msm_i2c msm_i2c.0: Error during data xfer (-5) (18)

257 <4>[ 6.231384] ds2482 0-0018: i2c write c3 87 failed, -5, retries left 4

258 <3>[ 6.231719] msm_i2c msm_i2c.0: error, status 43c8 (18)

259 <3>[ 6.231750] msm_i2c msm_i2c.0: Error during data xfer (-5) (18)

260 <4>[ 6.231781] ds2482 0-0018: i2c write c3 87 failed, -5, retries left 3

261 <3>[ 6.232116] msm_i2c msm_i2c.0: error, status 43c8 (18)

262 <3>[ 6.232116] msm_i2c msm_i2c.0: Error during data xfer (-5) (18)

263 <4>[ 6.232177] ds2482 0-0018: i2c write c3 87 failed, -5, retries left 2

264 <3>[ 6.232482] msm_i2c msm_i2c.0: error, status 43c8 (18)

265 <3>[ 6.232513] msm_i2c msm_i2c.0: Error during data xfer (-5) (18)

266 <4>[ 6.232543] ds2482 0-0018: i2c write c3 87 failed, -5, retries left 1

267 <3>[ 6.232879] msm_i2c msm_i2c.0: error, status 43c8 (18)

268 <3>[ 6.232910] msm_i2c msm_i2c.0: Error during data xfer (-5) (18)

269 <4>[ 6.232940] ds2482 0-0018: i2c write c3 87 failed, -5, retries left 0

a lot of these:

363 <3>[ 22.430023] msm_nand_write_oob 101c0000 800 1c failed -5

364 <3>[ 22.430419] msm_nand_write_oob 101c0800 800 1c failed -5

365 <3>[ 22.430725] msm_nand_write_oob 101c1000 800 1c failed -5

366 <3>[ 22.431121] msm_nand_write_oob 101c1800 800 1c failed -5

367 <3>[ 22.431427] msm_nand_write_oob 101c2000 800 1c failed -5

368 <3>[ 22.431823] msm_nand_write_oob 101c2800 800 1c failed -5

and in a other log another crash:

839 <6>[ 1074.828948] msm_hs_check_clock_off_locked, Set bt_chip_wakeup HIGH

840 <3>[ 1074.829772] BUG: scheduling while atomic: btld/823/0x00000002

841 <4>[ 1074.830139] Modules linked in: bcm4329

842 <4>[ 1074.831481] [<c0328dbc>] (dump_stack+0x0/0x14) from [<c005c484>] (__schedule_bug+0x54/0x60)

843 <4>[ 1074.832977] [<c005c430>] (__schedule_bug+0x0/0x60) from [<c03290c4>] (schedule+0x7c/0x45c)

844 <4>[ 1074.834716] r5:c048cf00 r4:c9e9eae0

845 <4>[ 1074.835784] [<c0329048>] (schedule+0x0/0x45c) from [<c01b1e60>] (msm_hs_shutdown+0x120/0x188)

846 <4>[ 1074.837219] [<c01b1d40>] (msm_hs_shutdown+0x0/0x188) from [<c01ac364>] (uart_shutdown+0xe4/0x10c)

847 <4>[ 1074.838958] [<c01ac280>] (uart_shutdown+0x0/0x10c) from [<c01ad768>] (uart_close+0x158/0x1dc)

848 <4>[ 1074.840667] r7:c04c4a78 r6:c9e6a400 r5:db1cc200 r4:db1cc288

849 <4>[ 1074.842407] [<c01ad610>] (uart_close+0x0/0x1dc) from [<c01a345c>] (tty_release_dev+0x180/0x46c)

850 <4>[ 1074.844177] r9:c9e08000 r8:da88f820 r7:db00a2a0 r6:00000000 r5:00000000

851 <4>[ 1074.846221] r4:c9e6a400

852 <4>[ 1074.847259] [<c01a32dc>] (tty_release_dev+0x0/0x46c) from [<c01a3764>] (tty_release+0x1c/0x28)

853 <4>[ 1074.848999] [<c01a3748>] (tty_release+0x0/0x28) from [<c00c67e8>] (__fput+0xf8/0x1e4)

854 <4>[ 1074.850433] r5:00000008 r4:da88f820

855 <4>[ 1074.851806] [<c00c66f0>] (__fput+0x0/0x1e4) from [<c00c6904>] (fput+0x30/0x34)

856 <4>[ 1074.853179] [<c00c68d4>] (fput+0x0/0x34) from [<c00c3504>] (filp_close+0x68/0x74)

857 <4>[ 1074.854888] [<c00c349c>] (filp_close+0x0/0x74) from [<c00c35d4>] (sys_close+0xc4/0x120)

858 <4>[ 1074.856323] r7:00000006 r6:da88f820 r5:cbeb0240 r4:00000006

hence msm_hs_shutdown

[Guest zanshin]

where's that stacktrace from?

this I gues:

1860 I/DEBUG ( 53): pid: 54, tid: 63 >>> /system/bin/rild <<<

in saw it in a logcat on the phone

[Guest ZiCoN]

Are we getting any closer to a verdict? Is it time to find the reciept and head on down to the store, hoping to get a new one?

[Guest Jamsi]

I've got an un-branded Desire which I succesfully rooted with the TinyCore-method.

And now I'll be gettin' a 16gb SD card in a few days, and I'd be interested to know whether there is a safe way to install the A2SD update??

[Guest ascot17]

I've got an un-branded Desire which I succesfully rooted with the TinyCore-method.

And now I'll be gettin' a 16gb SD card in a few days, and I'd be interested to know whether there is a safe way to install the A2SD update??

My T-Mobile Desire still has it's stock ROM. I have been following the threads on this forum for the last month. My main interest in rooting the Desire would be to install A2SD and free up some space on the phone. There are a LOT of threads currently referring to A2SD and most of them deal with problems people are having.

I have a Gold card and a brand-new 16GB card. At present though, A2SD seems to be too big a risk to take....

[Guest jdouce]

Issue: USB tethering, disk drive, not available, USB via ADB works, USB via Fastboot Works

16gb SanDisk C2

Recovery Partioning of SD

[Guest xTc is loVe]

Issue :- No SD card + No Mount

SD card :- Standerd

Formatted :- Recovery

Hboot: 0.80

[Guest IdleVoid]

Issues:

No ADB connection (saying the phone is a Qualcomm CDMA Technologies SMS device) (results in no recovery mode only fastboot)

No USB connection

No SD Card at all

The SIM card I use for the phone doesn't work anymore (it isn't recognised, SIM cards from two other suppliers worked but no 3G connection

HBOOT: 0.75

ROM Version: generic 1.15.405.4

No use of goldcard. read it wasn't needed and after the initial rooting using the r4 version everything worked.

Then I upgraded to the r3 version from the kitchen (with A2SD or A2SD+, not sure) support. And then all the problems started.

The SD card was partioned using the recovery imnage and converted to EXT3. I veryfied the partion using the Windows disk mamanger and could see the EXT3 partion was last.

The vendor ID and product ID changed (to the Qualcomm.... stuff). I tried hacking the driver INF file but to no avail.

I've now sent it back to the shop where I bought it... hoping they just replace it without anything, else I guess I have to pay for the repair... but I was warned.

Edited May 16, 2010 by IdleVoid

[Guest afiorillo]

[...]

Then I upgraded to the r3 version from the kitchen (with A2SD or A2SD+, not sure) support. And then all the problems started.

[...]

Have you ever flashed any radio update? What baseband version do you have at this time?

[Guest xTc is loVe]

Issue :- No SD card + No mount + NO ADB SINCE THIS DAY

SD card :- Standerd

Formatted :- Recovery

[Guest Chromed]

Issue: USB tethering, disk drive, not available, USB via ADB works, USB via Fastboot Works

16GB Kingston Class 10

Partitioned with gparted on pc..

[Guest IdleVoid]

Have you ever flashed any radio update? What baseband version do you have at this time?

No I never updated the radio and I don't recall including it in the rom from the r3 kitchen.

And I wasn't able to update the rom afterwards. I was thinking it could be that but no success at getting into recovery mode