yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] kubino99:
I've managed to access mtd6 partition. it looks like it's full NAND image(the size is 512Mb)

# cat /proc/mtd
dev: size erasesize name
mtd0: 000a0000 00020000 "misc"
mtd1: 00500000 00020000 "recovery"
mtd2: 00280000 00020000 "boot"
mtd3: 0fa00000 00020000 "system"
mtd4: 02800000 00020000 "cache"
mtd5: 093a0000 00020000 "userdata"
mtd6: 20000000 00020000 "msm_nand"

# ls -l /system/sd/mtd6.img
-rw-rw-rw- 1 0 0 536870912 May 29 14:32 /system/sd/mtd6.img

seems like normaly we have acces only to 445.75 Mb (mtd0 + mtd1 +.. + mtd5) of NAND, seems like 66.25 Mb is in hidden part of NAND.

it will be usefull to have also complete dump also from USB-bricked device.
[Desire Android Development] The Professor:
How do you find it? My brick only shows mtd0 through 5.
[Desire Android Development] kubino99:
you need patched kernel to see MTD6.
[Desire Android Development] aszeman:
Hi! Did someone check the misc partition content if it's easy to interpret? Isn't it so that recovery and bootloder use that to communicate so it might worth checking?

-------------------------------------

Sent via the XDA Tapatalk App
[Desire Android Development] Normola:
Is it possible to mount and write to mtd6? Would it be possible to just overwrite it with the data from a non-bricked device?
[Desire Android Development] kubino99:
I've dumped the mtd6 partition and analazing it right now so far I've found this :

0	unknown_part_start (propably radio + splash + spl ..)
4240000 recovery_start
4740000 boot_start
49C0000 system_start
143C0000 cache_start
16BC0000 userdata_start
1FF60000 misc_start

not sure if it's possible to rewrite part of mtd6 by dd command, I won't risk the complete brick ;o)
[Desire Android Development] Normola:
Is mtdblock6 listed in /dev/block ? Any chance you could upload your image? I haven't got a patch kernel installed.
[Desire Android Development] kubino99:
yes it's there :

# ls /dev/block
mmcblk0 mmcblk0p2 mtdblock1 mtdblock3 mtdblock5 vold
mmcblk0p1 mtdblock0 mtdblock2 mtdblock4 mtdblock6

check the boot.img with patched kernel in attachement.
[Desire Android Development] kubino99:
hi

Here is what I've found when dumped NAND :

0 - radio + unknown (62.125 Mb)
3E20000 spl (512Kb)
3EA0000 blank (FF) (256Kb)
3EE0000 misc	(64Kb)
3F80000 blank (FF) (256Kb)
3FC0000 some parameters (macddr...) (2048b)
3FC0800 unknown (126Kb)
3FE0000 blank (FF) (64Kb)
4080000 splash.nb0 (768Kb)
4140000 blank (FF) (384Kb)
41A0000 unknown (propably wifi FW) (64Kb)
4240000 recovery_start (5Mb)
4740000 boot_start (2.5Mb)
49C0000 system_start (250Mb)
143C0000 cache_start (40Mb)
16BC0000 userdata_start (147.625Mb)
1FF60000 misc_start (64Kb)
[Desire Android Development] shawe_ewahs:
If you can dump from NAND to PC, can be possible dump from PC to NAND?
[Desire Android Development] Normola:
If it's an overflowing nand write casuing the brick, I'd think it would be 1FF60000 misc_start (64Kb) that was damaged (I think userdata is mtdblock5 which is written to here during rom pauls rom flashing.)
[Desire Android Development] kubino99:
There are just few strings in MISC partition. Can someone with bricked device dump misc partition ?

cat /dev/mtd/mtd0ro > /sdcard/misc.img
[Desire Android Development] xtcislove:
Can you explain step by step? I am bricked and i wish to help!
[Desire Android Development] kubino99:
1. run any terminal on your phone (better terminal)

2. type

su
cat /dev/mtd/mtd0ro > /sdcard/misc.img

3. somehow get misc.img from sdcard and upload it.
[Desire Android Development] Jpcurrie:
This is good work.

Where is the recovery written too as part of the adb push?

Edit is that the user data as mentioned?

-------------------------------------

Sent via the XDA Tapatalk App
[Desire Android Development] stevebrush:
misc.img

Hi, my usb-bricked desire is back to customer for repair but I dump the boot, misc and recovery partition before sending it, so here they are... :)
[Desire Android Development] :
Hmm, I have quite a few more strings in mine - Ranging from my CID to things like

"DeviceWarmBoot..................................CE Serial InUse.Debug Cable Ena.CE USB InUse.................ClearAutoImage"

Forgot to mention: I am not bricked, but rooted.
[Desire Android Development] kubino99:
indeed first 159 bytes are overwritten. I'm wondering if it can be flashed back.

if there is anyone brave enought with bricked USB you can try this :

cat /dev/zero >/dev/mtd/mtd0
flash_image misc misc.img

note if you don't have flash_image binary you need to put it somewhere in data partition

DO AT YOUR OWN RISK :-)
[Desire Android Development] JDouce:
if coem brave soul does this and we have a fix that would be AWSOME...can you do this from fastbstboot
[Desire Android Development] JDouce:
can more bricked desires post there misc.img would be interesting to see if is truly random or if its the same part thats overwritten everytime
[Desire Android Development] kubino99:
if it will be fix depends on writable partition mtd0. If it's writable from normal boot mode it coud be fix ;-)
[Desire Android Development] kubino99:
can more bricked users do this simple test ? :

# cat /dev/mtd/mtd0 | grep DeviceWarmBoot
DeviceWarmBoot
#

It looks like SPL reads some string from misc partition (DeviceWarmBoot).
[Desire Android Development] emontes:
I sent mine to HTC last week otherwise I would give it a go.

Come on guys :)
[Desire Android Development] The Professor:
I will give this a shot in 10 minutes.
[Desire Android Development] JDouce:
awsome cant wait to see the result
[Desire Android Development] pina_:
I would like to try this, but don't know how how to do it, if someone could give me some more detailed instructions...?
[Desire Android Development] m2te:
Starting at position 161 in the misc.img files appears to be a ROM version, I would be concerned to flash this misc.img file to a phone running a different rom version.

Maybe we need to get a working misc.img from a 1.21.405.1 as well as 1.15.405.3
[Desire Android Development] The Professor:
My misc.img:

misc.img

I don't, however, have DeviceWarmBoot anywhere:

Can anybody take a quick look at my misc.img and make sure this overwrite is safe-ish for my situation?
[Desire Android Development] Liquid-Silver:
Your misc.img is definately corrupted.

The new one only contains strings and none of these seem to be device specific except for the ROM version string. Your rom version string is currently corrupted (all ff's) so I don't see any harm coming from flashing the new misc.img.

Being sure though, that's another question.
[Desire Android Development] The Professor:
I tried looking at it myself, and it's completely blank. :( Not even a hint of the strings in the replacement one.

I have several old nandroids - is there any way to pull an old misc.img out of those to compare and possibly flash back? I know I haven't changed ROMs since my last nandroid.

I'm fairly terrified to SUPER-brick the phone, but I see no harm replacing what used to be there, right...?

Please let me know what I can try. :)
[Desire Android Development] ephumuris:
I was going to suggest that. No harm if you have an old misc.img that you can just flash back. You could be the first un-usb-bricked-desire owner.
[Desire Android Development] The Professor:
How do I pull it from the given nandroid dumps? I have system.img, boot.img, and data.img - where does misc live, can I/do I need to extract it, etc?

PS sorry for nubbiness, but I'll follow directions like a champ. :)
[Desire Android Development] kubino99:
I have 1.15.405.3 installed. you can hexedit the img file and replace the string with your version.
[Desire Android Development] kubino99:
you should have misc.img aswell. appearently looks like it's not dumped by default. when checked nandroid-mobile.sh found the following:

# Reference data:

# dev: size erasesize name
#mtd0: 00040000 00020000 "misc"
#mtd1: 00500000 00020000 "recovery"
#mtd2: 00280000 00020000 "boot"
#mtd3: 04380000 00020000 "system"
#mtd4: 04380000 00020000 "cache"
#mtd5: 04ac0000 00020000 "userdata"
#mtd6 is everything, dump splash1 with: dd if=/dev/mtd/mtd6ro of=/sdcard/splash1.img sk ip=19072 bs=2048 count=150

[B]# We don't dump misc or cache because they do not contain any useful data that we are a ware of at this time.
[/B]
[Desire Android Development] cedeel:
Well, whoever made that assumption might have been very wrong :eek:
[Desire Android Development] geek78:
So if the misc.img is the solution we need an htc signed update with the misc.img ?
[Desire Android Development] shawe_ewahs:
Can be not useful for nandroid backup/restore, but here can be possible that are saved values that changes on usb-bricked devices.
[Desire Android Development] The Professor:
So there's nothing I can pull from to verify.

In MoDaCo, people have tried flashing their own misc.imgs with fastboot, and they get sig failures; still looking at flashing from elsewhere using flash_image.
[Desire Android Development] kubino99:
not in case the misc partition is not write protected (it's the last one in NAND so I assume it's not but nobody knows)

if the partition is writable you can simply flash it with flash_image binary.
[Desire Android Development] geek78:
Ok. So a bricked user will be able to test it quickly from the terminal...
[Desire Android Development] The Professor:
Two questions, then I'll give it a shot:

Where can I get flash_image?

Where do I find the ROM version I'm using to change that string to one that will match what I'm running? I assume I'll just switch the CID at the beginning.
[Desire Android Development] xtcislove:
Tell me what to do! I do! Just want my phone back =(
[Desire Android Development] kubino99:
flash_image you can find for example in Paul's recovery (files/sbin). Seems like the rom version is still in corrupted partiton just dump misc and check via hexeditor.
[Desire Android Development] The Professor:
Mine is not in misc - my misc is entirely blank, as attached above.
[Desire Android Development] :
Fingers Crossed;)))

I feel this could be the answer, Lets **** HTC and show them we can bite back;)

JD;)
[Desire Android Development] kubino99:
if it's blank I wouldn't bother seems like it's not used at all. I've performed grep in /system partiton and nothing found
[Desire Android Development] shawe_ewahs:
Please, anyone with:

ROM: 1.21.40.5.2

Radio: 32.36.00.28U_4.06.00.02_2 release 126984

Rooted and non-rooted devices, can try this for share with others:

Power off the devices

Press "Vol.Down + Power"

Select Recovery and press Power

And using AMDesireRecovery do:

chmod +x adb-linux
chmod -R -w * files/
chmod -R +x * files/
sudo ./adb-linux kill-server
sudo ./adb-linux root
sudo ./adb-linux push files
sudo ./adb-linux shell busybox --install /sbin
sudo ./adb-linux shell
cat /dev/mtd/mtd0ro > /sdcard/misc.img
cat /dev/mtd/mtd1ro > /sdcard/recovery.img
cat /dev/mtd/mtd2ro > /sdcard/boot.img
cat /dev/mtd/mtd3ro > /sdcard/system.img
cat /dev/mtd/mtd4ro > /sdcard/cache.img
cat /dev/mtd/mtd5ro > /sdcard/userdata.img

And when finished, share here your .img files, think that contains private data.
[Desire Android Development] abc27:
Would a rooted 1.15.405.4 ROM misc be of any use to any of you?

Not bricked but I definitley want to see a fix for bricked phones!
[Desire Android Development] JDouce:
would be nice abc
[Desire Android Development] abc27:
How would I dump the misc.img?
[Desire Android Development] JDouce:
from adb in recovery

chmod +x adb-linux

chmod -R -w * files/

chmod -R +x * files/

sudo ./adb-linux kill-server

sudo ./adb-linux root

sudo ./adb-linux push files

sudo ./adb-linux shell busybox --install /sbin

sudo ./adb-linux shell

cat /dev/mtd/mtd0ro > /sdcard/misc.img

or you may beable to do it from better terminal in andorid

same

cat /dev/mtd/mtd0ro > /sdcard/misc.img

and the .img will be in the root of ur sd card
[Desire Android Development] shawe_ewahs:
Posted 5 posts up from this:

http://xdaforums.com/showpost.php?p=6640871&postcount=142
[Desire Android Development] JDouce:
you can dump the misc image from better terminal emulator

su

# cat /dev/mtd/mtd0ro > /sdcard/misc.img
[Desire Android Development] abc27:
Ok done that using Terminal emulator on the phone, before I upload this, what exactly is located inside it? Any private details e.t.c.?
[Desire Android Development] JDouce:
misc.img

non-bricked

MRC r2
[Desire Android Development] JDouce:
theres nothing personal in it ... its jsut os stuff
[Desire Android Development] abc27:
Stock Rooted Rom

Non-Bricked

1.15.405.4
[Desire Android Development] abc27:
Has someone with a bricked phone posted up their misc.img up yet?

I want to take a look at both in a hex editor
[Desire Android Development] JDouce:
back a few pages

theres a load of lines missing from the bricked dump
[Desire Android Development] xtcislove:
I am bricked!

Should i upload other .img files than the misc img?

Hboot 0.80

Testimage v. 1.21.405.2
[Desire Android Development] JDouce:
xtcislove get the file abc just uploaded

im not sure how to flash the misc partition so ull have to get info

u should be able to do it from the better terminal emulator
[Desire Android Development] abc27:
Ah yes you can see there is exactly 56 bytes of data missing between the misc.img of a bricked and an unbricked phone.

I think we may be getting closer to finding a solution :)
[Desire Android Development] shawe_ewahs:
Edit your post and put what version are you using, please.
[Desire Android Development] abc27:
What rom are you running?
[Desire Android Development] xtcislove:
The Testimage from Modaco ! For Hboot 0.80 i took the testimage from R5 Rooting Method!
[Desire Android Development] JDouce:
could someone post info on how you'd go about flashing the misc.img from terminal emulator in andorid
[Desire Android Development] abc27:
I've just taken a look at both in a hex editor.

The regular misc.img is almost entirely empty barr the first 11 lines, the rest of it is made up almost exclusively of 00. The bricked has very little in it barr the version number.
[Desire Android Development] totzkotz:
Non-Bricked-USB

Bootloader 0.75

Pays 1.6 BraveSoul - Rom

Kernel: 2.6.29-bravo-r13 (V13 UVOC by richardtrip)

Baseband-Version: 32.37.00.32U_4.06.00.16_2

my misc.img (zipped)

hope it will help u all ^^

i did the first rooting method by paul... ^^
[Desire Android Development] xtcislove:
Should i try to flash the misc.img from the non bricked user?

How do i do it?
[Desire Android Development] shawe_ewahs:
Can be more useful for all non-dev users have a little explanation with commands step by step for do that. Anyone can explain it? I don't know how to do it.
[Desire Android Development] abc27:
Here is a line by line of the regular misc.img

HTC__001

.............

DeviceWarmBoot

ÿÿÿÿÿÿÿÿÿÿÿÿ

ÿÿÿÿÿÿÿÿÿÿÿÿ

CE Serial InUse

Debug Cable Ena

CE USB InUse

.....................

ClearAutoImage

1.15.405.3

However in the bricked it is made up entirely of "." and "ÿ" barr the 11th line

ÿÿÿÿÿÿÿÿÿÿÿÿ

..................

ÿÿÿÿÿÿÿÿÿÿÿÿ

ÿÿÿÿÿÿÿÿÿÿÿÿ

ÿÿÿÿÿÿÿÿÿÿÿÿ

ÿÿÿÿÿÿÿÿÿÿÿÿ

ÿÿÿÿÿÿÿÿÿÿÿÿ

ÿÿÿÿÿÿÿÿÿÿÿÿ

ÿÿÿÿÿÿÿÿÿÿÿÿ

ÿÿÿÿÿÿÿÿÿÿÿÿ

1.21.405.1

So personally I think if it is possible to just change the version number to the one suited to the phone and then to just flash that misc.img it would restore it to how it was pre-bricked.
[Desire Android Development] xtcislove:
U mean it wouldn´t change anything?
[Desire Android Development] The Professor:
Guys, I am now unbricked. More details to follow, hold on to your butts.
[Desire Android Development] abc27:
I've edited my non-bricked misc.img and changed it to version number 1.21.405.1
[Desire Android Development] abc27:
Brilliant :D
[Desire Android Development] kubino99:
wtf ? are you kidding ? ok guys hope that we did it ;o)) the misc is not more misc :D
[Desire Android Development] Upquark:
This is legend. XDA @ its best!
[Desire Android Development] xtcislove:
I COULD SCREAM IF ITS TRUE ! PLEASE INSTRUCTIONS ! I have water in my eyes :D
[Desire Android Development] myth1001:
There's a solution to this?!?!

That will be a great news!

Sent from my HTC Desire
[Desire Android Development] shawe_ewahs:
:eek: Very good news, explain how to solve the problem :D
[Desire Android Development] andycted:
Are you kidding ? Or are you already jumping on the roof naked to celebrate ?

Totally unbricked ?! I'm holding to my butt !
[Desire Android Development] potter1984:
Omfg....... well done :)

I'm not bricked personally but am so glad you guys have an answer for everyone else.

+ 1,000,000
[Desire Android Development] sruon:
wow... +1000000000 to XDA if this is true.
[Desire Android Development] kingchris:
its online on MoDaCo

http://android.modaco.com/content/h...com/309939/usb-brick-rickrolled-b0rked-fixed/
[Desire Android Development] The Professor:
Thread'd.
[Desire General] poldie:
I'm still confused about syncing contacts. I have a Desire on Orange. I have a gmail account, and I use the htc mail app and connect to my gmail account using exchange. I sync my contacts to my gmail account using `google/sync contacts` from the sync page, and I sync my mail using `exchange activesync`. I do this because I can see/edit my contacts via the web gmail page (which is easier/faster than doing it on the phone), and because the mail app is better than the gmail app. But it seems that I have some contact information on my phone which is not visible via the gmail website. To pick one example, it's showing as a `linked contact` between 'exchange' and 'google'. Can I see my exchange contacts online? Where are they? I want them in one place, so I can back them up occasionally (I've already lost my contacts once as I set my phone up). It would seem to make sense, given that some contact info appears to be on exchange somewhere, to have them all there - then I can stop syncing with 'google' on my phone altogether, but I have to be able to see/edit/back them up first.

I've tried googling for this, but all I see is Googles own pages for other platforms, non-free apps to do exchange etc etc.
[Desire General] jauhari:
I have the same issues too
[Desire General] Necroman_AI:
Well i don't use exchange, but i can say how i use my gmail sync:

I use Sync/google account on the definitions menu to sync my google calendar, contacts and mail.

This allows me to use mail on gmail app (not htc mail app), calendar on android calendar (i can use htc calendar widgets) and manage online contacts.

Since i previously added my "phone" contacts to phone memory and to a group on google contacts, they have linked to each other and i can mantain an online and local copy of them (this is great to add a hi res picture to contact, since i add the picture to online and local and then choose local picture to be displayed).

I do know that some fields from online google contacts and local contacts are different, and i think this is as stupid as the picture not having quality on google contacts online, but i hope they would solve it in a near future.

I hope that from now on, since google is saying that the BIG changes on Android are done, they will spend some time dealing with the little details that can be very annoying...
[Desire General] Hexxer:
Same issue here.

Sync of Contacts

Google-Contacts -> Desire: works

Desire -> Google-Contacts: dosent work

If i try to add or change a birthday on the phone it does not arrive theo google-contacts account. The other way works. Biggest issue on this fine phone.
[Desire General] Necroman_AI:
Hi, that issues are from Android and Gmail and not from the Desire.

You should add birthday dates to Google contacts or else the synchronization wont work well, but i do agree these are major stuffs that really annoy me!
[Desire General] Hexxer:
There could be an interesseting thing.

I have Software-Version 1.15.XXXX (T-Mobile, rooted Phone) and i found an O2 User with 1.20.XXX - he said it works at his phone.
[Desire General] Necroman_AI:
Uau! How can he have an 1.20.xxx? I have unlocked Desire also with 1.15.XXX and no updates for me!
[Desire General] Necroman_AI:
Well I now have 1.21.405.2 updated from ota.
[HD2 Windows Mobile 6.5 ROM Development] Omega Kaos:
¦ WM6.5.5 ¦ WWE ¦ Kaos ROM Series ¦ Build 23569 ¦ Sense 2.5.2016 ¦ 576MB Enabled ¦ 07 August 2010 ¦​

ROM Name - Kaos

ROM Version - V3.8

ROM Language - WWE

Manila Version - 2.5.2016

OS Version - WM6.5.5

Radio Version - 2.11.50.26

PagePool Size - 20M

Build - 23569

576MB Enabled

Based On 3.01.405.T1

Kaos ROM Versions (Post 2)

Original Packages (Post 3)

Kaos ROM Change Log(Post 4)

Other Information(Post 5)

​

Please let me know if there's any issues. If you feel there should / could be apps added then please leave you suggestions on this from and they will be cooked after some consideration. Also i am looking for someone to create a full theme for my ROM, don't hesitate to ask, full credit and link to original thread will be given!

To keep up-to-date on the status of my ROM development please follow me on twitter. Feel free to send tweets if you find any issues, help and feedback is always helpful.

Notes

On the Max Sense UI versions of my ROMs i have left every thing as default (as is when originally cooked without re-arranging the Home Screen). If you prefer me to cook it as the screen shot below in post 2 please leave a comment. I have left it like this so you can have it how you want rather than having to remove my customizations and add yours.

Please do not install SRS WOWHD it makes the sound choppier on my ROMs

For CDMA enabled phones using MaxSense UI please install this cab. Max Sense UI - Enable CDMA

To follow me on twitter click here.

Credits

Chainfire - Chainfire's HD2 3D Driver Patch

Co0kieMoster - Co0kie's Home Tab

johncmolyneux - CHTEditor

Arktronic - Arkswitch

makeveral - BsB Tweaks

Sector - SRS WOW HD

meltwater - Facebook Tab

goatrance - Dial-Up Enabler Disabler

g.lewarne - Performance Tweaks

tboy2000 - System Registry Tweaks

NuShrike - libGLES_CL.dll

lesscro - Chainfire's HD2 3D Driver Patch program icon

Maxycy - MaxSense UI and Max Manila

Lechux - FiRESTORM iCONSET

::indie:: - His help and feedback for this rom

djcedric - DJC Taksbar Leo 6.5.x v0.2, BlackBlue Dialer + Fix for WM6.5.x

DINIK - Slider

Team GTX - GTX Theme

Dark Ninja - Android Taskbar V6 + Dark Ninja White Theme

And anybody else i forgot to mention.
[HD2 Windows Mobile 6.5 ROM Development] Omega Kaos:
Kaos ROM Versions

Standard Sense 2.5.2016

Free Program - 257.61MB

Free Storage - 165.33MB

Co0kie's Home Tab v1.8.5

Free Program - 227.40MB

Free Storage - 162.52MB

Max Manila 2.5 v3.0 beta

Free Program - 252.43MB

Free Storage - 164.64MB

MaxSense UI v1.05

Free Program - 271.69MB

Free Storage - 139.87MB

Titanium

Free Program - 305.93MB

Free Storage - 213.38MB

GTX Themed v1.8.5

Free Program - 271.58MB

Free Storage - 185.45MB

Radio Version 2.11.50.26 is included in my ROMs so you don't need to download one.

Please use Task29 before flashing this ROM to avoid any errors.

All of Kaos ROMs are uploaded to hotfile please leave a post if you require another site.

ROM Downloads:

[07 August 2010] Kaos ROM v3.8 - Standard Sense 2.5

[07 August 2010] Kaos ROM v3.8 - Co0kie's Home Tab v1.8.5

[07 August 2010] Kaos ROM v3.8 - Co0kie's Home Tab v1.8.5 without HTC Messaging (Requested by theory_87)

[07 August 2010] Kaos ROM v3.8 - Max Manila v2.5 v3.0 Beta

[07 August 2010] Kaos ROM v3.8 - Max Sense UI v1.05

[07 August 2010] Kaos ROM v3.8 - Titanium

[07 August 2010] Kaos ROM v3.8 - GTX Themed v1.8.5