USB brick/rickrolled/b0rked -> FIXED!

[Guest potter97]

Where did you get your phone, and have you done anything special with it? Yes, that's your CID, and that could be very interesting...

He may have found the "DEV" CID????

[Guest IEFtm]

He may have found the "DEV" CID????

We already know that 1111111 is a super CID from earlier hacks on f.e. the Hero.

But we have no way of getting that on our desires :(

[Guest potter97]

We already know that 1111111 is a super CID from earlier hacks on f.e. the Hero.

But we have no way of getting that on our desires :o

Ah ok..

Cool so he may of accidently found out how! :(

nice find @ maddoxus

And now a few devs are on the case atm anyway, i think we could be seeing a more stable rooting methord soon, With added FULL access to EVERYTHING :()

Edited May 30, 2010 by potter97

[Guest Jagdish]

NO!!

And if your asking that you need to do your homework boy! lol.

READ FULLY the flashing thread.

No need to shout mate, lol, i obviously did not fully understand the tut hence this question, no need to get all worked out :(

[Guest Kaare]

Norwegian Desire:

CID: HTC__Y13

ROM: 1.15.405.3

I'm running a 1.21 ROM (MoDoCo r3) right now though, so it looks like the ROM string in misc is whatever was on the device when it was new(?)

misc.img

[Guest nerdo]

Even though my Desire was never affected by this issue, but I am so pleased to have a solution to end the suffering of all the other Desire owners :(

Thanks guys so much for this, well done!!

[Guest IEFtm]

hmm @maddoxus:

Could you get on IRC? irc.freenode.net #modaco . Then we can talk a bit further perhaps.

[Guest potter97]

No need to shout mate, lol, i obviously did not fully understand the tut hence this question, no need to get all worked out :(

I Shouted as i thought how stupid can someone be!, im not worked up, just did not want you to brick yours too!

Not that i am bricked.. And like i said do your homework first, soooo many people just rush in...

[Guest maddoxus]

Sorry, could not reply earlier had to get some food with the missus, she was already complaining me sitting in front of the computer all afternoon hitting the refresh button every second.

So here the story how I got to the phone:

I wanted this phone for a time, could not order it online so I went to a THREE store. But the only desire they had was the one which was their demo unit, after some discussions with a few people and offerings of many other phones, which all are "much better" and "newer" with "bigger displays" with "better OS's". I still insisted on buying this phone and I said to them if they don't sell me one today I will find someone who will sell it. So finally they offered me their demo unit, and I took it. I then was looking at getting a custom rom on it, I tried first a early MCR, can not remember which one. Went then to XDA tried Evil Desire rom, and finally ended up with Pays rom version 1.5, and then I read about the usb bricks and stopped flashing new roms.

I update the radio to 32.36.00.28U_4.06.00.02_2.

And that's it.

Oh of course I rooted with the goldcard method. Using a Windows 7 x64 machine HxD.

But I think I might just have had luck to get this phone. As I think many of you guys went through all these steps as well and they should not change the CID as far as I understand the whole thing. But bricking/recovery changes it. Ahh I don't understand it at all.

If I can be of any help with my phone let me know, and try to explain it in some kind of a newbiesh way. I have some experience using Linux and Windows, programmed in C but don't know anything about kernels and android development.

maddoxus

[Guest Andrsp]

That's mine, never bricked

maybe it can be useful..

macbook:tools Andr$ ./fastboot-mac oem boot

... INFOsetup_tag addr=0xA0000100 cmdline add=0x8E07D98C

INFOTAG:Ramdisk OK

INFOTAG:smi ok, size = 0

INFOTAG:hwid 0x0

INFOTAG:skuid 0x21F04

INFOTAG:hero panel = 0x0

INFOTAG:engineerid = 0x0

INFOMCP dual-die

INFOMCP dual-die

INFOTAG:mono-die = 0x0

INFODevice CID is not super CID

INFOCID is HTC__001

INFOsetting->cid::HTC__001

INFOserial number: HT03LPL00187

INFOcommandline from head: no_console_suspend=1 console=null

INFOcommand line length =434

INFOactive commandline: board_bravo.disable_uart3=0 board_bravo.

INFOusb_h2w_sw=0 board_bravo.disable_sdcard=0 diag.enabled=0 boa

INFOrd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e

INFOmmc=false  androidboot.baseband=4.05.00.11 androidboot.cid=H

INFOTC__001 androidboot.carrier=HTC-WWE androidboot.mid=PB992000

INFO0 androidboot.keycaps=qwerty androidboot.mode=normal android

INFOboot.serialno=HT03LPL00187 androidboot.bootloader=0.75.0000 

INFOno_console_suspend=1 console=null

INFOaARM_Partion[0].name=misc

INFOaARM_Partion[1].name=recovery

INFOaARM_Partion[2].name=boot

INFOaARM_Partion[3].name=system

INFOaARM_Partion[4].name=cache

INFOaARM_Partion[5].name=userdata

INFOpartition number=6

INFOValid partition num=6

INFOmpu_nand_acpu_rw A1E 1000

INFOjump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker

INFOnel_addr(0x20008000)

INFO-------------------hboot boot time:49677 msec

ERROR: usb_read failed with status e00002ed

FAILED (status read failed (No such file or directory))

[/codebox]

misc.img

[Guest kubino]

Hi,

thanks for the good work, being free to flash new roms makes it so much easier. My device was never bricked, but I tried to get my misc.img. I did it with the phone running via adb, I attached it. However, I could not find my CID in there, so I tried it with the fastboot command with following result:

... INFOsetup_tag addr=0xA0000100 cmdline add=0x8E07D98C

INFOTAG:Ramdisk OK

INFOTAG:smi ok, size = 0

INFOTAG:hwid 0x0

INFOTAG:skuid 0x21F04

INFOTAG:hero panel = 0x0

INFOTAG:engineerid = 0x0

INFOMCP dual-die

INFOMCP dual-die

INFOTAG:mono-die = 0x0

INFODevice CID is super CID

INFOCID is super CID

INFOBackup CID is empty

INFOsetting->cid::11111111

INFOserial number: HT03VPL07398

INFOcommandline from head: no_console_suspend=1 msmsdcc_sdioirq=

INFO1 wire.search_count=5

INFOcommand line length =457

INFOactive commandline: board_bravo.disable_uart3=0 board_bravo.

INFOusb_h2w_sw=0 board_bravo.disable_sdcard=0 diag.enabled=0 boa

INFOrd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e

INFOmmc=false androidboot.baseband=4.06.00.02_2 androidboot.cid

INFO=11111111 androidboot.carrier=ALL androidboot.mid=PB9920000

INFOandroidboot.keycaps=qwerty androidboot.mode=normal androidbo

INFOot.serialno=HT03VPL07398 androidboot.bootloader=0.75.0000 no

INFO_console_suspend=1 msmsdcc_sdioirq=1 wire.search_count=5

INFOaARM_Partion[0].name=misc

INFOaARM_Partion[1].name=recovery

INFOaARM_Partion[2].name=boot

INFOaARM_Partion[3].name=system

INFOaARM_Partion[4].name=cache

INFOaARM_Partion[5].name=userdata

INFOpartition number=6

INFOValid partition num=6

INFOjump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker

INFOnel_addr(0x20008000)

INFO-------------------hboot boot time:142877 msec

FAILED (status read failed (Too many links))

I have not seen this here until now, is my CID now 11111111 ? And what means super CID?

Or did I do something wrong?

this is great finding... does anybody noticed that he has propably full write access to all partitions ? can you please do for me a small test ? can you try the following in normal boot :

adb shell

mount -o remount,rw /system

mkdir /system/test

ls -l /system

rmdir /system/test

and paste here the output ?

[Guest i6bazar]

Good job guys and thanks a lot to all the contributors :(

[Guest pina]

just feels like i have a new phone again, after 2 weeks of a bricked desire :(

[Guest jdouce]

someone could just flash his misc img and try

Edited May 30, 2010 by jdouce

[Guest Elbereth]

Thanks guys! Not bricked but this is a relief. Just did a backup of this partition in case of. :(

[Guest jdouce]

tried flashing the mtd0.img that was super CID ... no sucess... still normal CID

[Guest djtosh]

Thanks guys! Not bricked but this is a relief. Just did a backup of this partition in case of. :(

how do u back up the partition?

thnx

[Guest Snarkasm]

su

cat /dev/mtd/mtd0 > /sdcard/mtd0.img

From a terminal app inside a booted phone. mtd0.img will be your backup, stored on your SD card.

It's only been stated 10 times or so.

[Guest stevebrush]

Usb-bricked misc.img generator is online here : http://ks33673.kimsufi.com/misc/

you have to provide your cid and your rom version.

it's a quick and dirty generator written in php, but it should work :( I did some diffs with a good misc.img and files generated and it's ok...

it's lite, so you can access it thru your device.

have nice unbricking...

edit : change script, so the downloaded filename is now mtd0.img

edit2 : source code here

mtd0.zip

Edited May 30, 2010 by stevebrush

[Guest djtosh]

su

cat /dev/mtd/mtd0 > /sdcard/mtd0.img

From a terminal app inside a booted phone. mtd0.img will be your backup, stored on your SD card.

It's only been stated 10 times or so.

u can state that 100 times and it will still make no sense to me, im a new user and dont know what a terminal app is. im guessing su and cat are the commands?

[Guest maddoxus]

this is great finding... does anybody noticed that he has propably full write access to all partitions ? can you please do for me a small test ? can you try the following in normal boot :

adb shell

mount -o remount,rw /system

mkdir /system/test

ls -l /system

rmdir /system/test

and paste here the output ?

Here is my output:

ls -l /system

drwxr-xr-x 1 0 0 2048 May 13 22:05 ←[1;34mapp←[0m

drwxr-xr-x 1 0 2000 2048 May 13 22:06 ←[1;34mbin←[0m

-rw-r--r-- 1 0 0 4757 Aug 1 2008 ←[0;0mbuild.prop←[0m

drwxr-xr-x 1 0 0 2048 May 13 22:05 ←[1;34mcustomize←[0m

drwxr-xr-x 1 0 0 2048 May 13 22:05 ←[1;34metc←[0m

drwxr-xr-x 1 0 0 2048 May 13 22:05 ←[1;34mfonts←[0m

drwxr-xr-x 1 0 0 2048 May 13 22:05 ←[1;34mframework←[0m

drwxr-xr-x 1 0 0 2048 May 13 22:05 ←[1;34mlib←[0m

drwxr-xr-x 1 0 0 2048 May 13 22:04 ←[1;34mlost+found←[0m

drwxr-xr-x 1 0 0 2048 May 13 22:05 ←[1;34mmedia←[0m

drwxrwx--x 6 1000 1000 1024 May 13 21:32 ←[1;34msd←[0m

drwxrwxrwx 1 0 0 2048 May 30 22:25 ←[1;34mtest←[0m

drwxr-xr-x 1 0 0 2048 May 13 22:05 ←[1;34musr←[0m

drwxr-xr-x 1 0 0 2048 May 13 22:06 ←[1;34mxbin←[0m

seems like I have rw rights for system.

[Guest AsayWat]

try and make the test directory!

edit: yes I'm blind :( he did it

Edited May 30, 2010 by AsayWat

[Guest Snarkasm]

u can state that 100 times and it will still make no sense to me, im a new user and dont know what a terminal app is. im guessing su and cat are the commands?

Might have been better to phrase the question differently to express that you wanted a little more explanation. :(

Download Better Terminal from the Market and launch it

Enter su and hit enter to get superuser access for that session - you may get a prompt asking if you want to give it superuser access if you haven't used it before.

Then enter the second line - cat will read a file and output it, since we specified the > operator, to the file path we specify at the end.

su <- superuser mode

cat /dev/mtd/mtd0 > /sdcard/mtd0.img <- read mtd0 out to mtd0.img on the SD card.

Make sense?

Good news for you, maddoxus. :( You got nice and lucky.

[Guest Snarkasm]

try and make the test directory!

He did make his test directory:

drwxrwxrwx 1 0 0 2048 May 30 22:25 ←[1;34mtest←[0mb

[Guest ctkhaled]

is there any particular reason why you are using 'cat source > destination' instead of 'cp source destination' ?

no, i use cat because in the first post the command is cat, and as i know there is ni difference between cp and cat without parametres

but the copy of these two files to the data folder is ok

the probleme is when i try the misc command i just get the error message "[1] illegal instruction

no way to unbreak for me, or i missing something

give me help please