Develop Bugs

*REQUEST* Firerat's Custom MTD Partitions (resize Data,System and Cache)

can any dev. make this happen for our EVO 4G please? I included a link to the thread were the mod is. This mod enables a person to decide how big the partitions in their phone should be. (ei system, data, cache, etc). Its awesome but I just have it on my hero which i gave to my brother and it wouldn't hurt that everyone could have more space for apps on their phone.
Thanks everyone!!!
http://forum.xda-developers.com/showthread.php?t=754805

I found a dmesg for your evo
# dmesg|awk '/0x.+: "/{ print }'
Code:
<5>[ 4.290466] 0x00003f360000-0x00003ff60000 : "wimax"
<5>[ 4.305419] 0x00003ff60000-0x000040000000 : "misc"
<5>[ 4.306518] 0x000004240000-0x000004740000 : "recovery"
<5>[ 4.312377] 0x000004740000-0x0000049c0000 : "boot"
<5>[ 4.315979] 0x0000049c0000-0x00001a7c0000 : "system"
<5>[ 4.730438] 0x00001a7c0000-0x0000247c0000 : "cache"
<5>[ 4.916748] 0x0000247c0000-0x00003f360000 : "userdata"
it has an extra partition to the g1 ( wimax )
see below for working version v1.5.7

Sounds really great! Thank you, Firerat.
But FR-CustomMTD-v1.5.6-Evo4G.zip is not downloadable to me. The site says its set to private.
Firerat said:
FR-CustomMTD-v1.5.6-Evo4G.zip
that zip contains
73d5ba178ffd702c9b963e9de9b4d5bc FR-recovery-v1.5.6-Evo4G-CustomMTD_S.zip
f468aefb7ad1f86b24c0156fb81a36c2 FR-boot-v1.5.6-Evo4G-CustomMTD_S.zip
89b4e67b87f5337e19c2d7dc95e87055 FR-remove-v1.5.6-Evo4G-CustomMTD_S.zip
Click to expand...
Click to collapse

ywjkid said:
Sounds really great! Thank you, Firerat.
But FR-CustomMTD-v1.5.6-Evo4G.zip is not downloadable to me. The site says its set to private.
Click to expand...
Click to collapse
oops,
http://www.mediafire.com/?0ae7y9sekpb3s
b74d178e7ed698879b555123ea494377 FR-recovery-v1.5.7rc1-CustomMTD_S.zip
331c1b31bbc007fa7c3a9ff01c9301dd FR-boot-v1.5.7rc1-CustomMTD_S.zip
ab946b6b9aa83554c452d3d5face18d4 FR-remove-v1.5.7rc1-CustomMTD_S.zip
its a generic version, which _should_ suit all devices with msm_nand
it collects every partition from dmesg
few little bits I want to do, then I'll bump it up to v2

RC1 is not working for me. After flashing FR-recovery-v1.5.7rc1-CustomMTD_S.zip, my RA-recovery 1.8 is broken and generates errors like
E: Can't find MISC:
E: Can't mount CACHE:recovery/command
E: Can't mount CACHE:recovery/log
E: Can't open CACHE:recovery/log
Firerat said:
oops,
http://www.mediafire.com/?0ae7y9sekpb3s
b74d178e7ed698879b555123ea494377 FR-recovery-v1.5.7rc1-CustomMTD_S.zip
331c1b31bbc007fa7c3a9ff01c9301dd FR-boot-v1.5.7rc1-CustomMTD_S.zip
ab946b6b9aa83554c452d3d5face18d4 FR-remove-v1.5.7rc1-CustomMTD_S.zip
Click to expand...
Click to collapse

ywjkid said:
RC1 is not working for me. After flashing FR-recovery-v1.5.7rc1-CustomMTD_S.zip, my RA-recovery 1.8 is broken and generates errors like
E: Can't find MISC:
E: Can't mount CACHE:recovery/command
E: Can't mount CACHE:recovery/log
E: Can't open CACHE:recovery/log
Click to expand...
Click to collapse
Ok, I think I see the problem
Not at home right now,
But in the mean time you should be able to flash the remove zip and return to stock
Looks like a copy paste fail and I'm excluding userdata what I shouldn't be
May also be escaping when I shouldn't be
If you have problems flashing the remove zip you can mount cache manually via adb shell
( you can also flash_image a standard recovery.img via adb shell )

Thanks. Just reflashed recovery and restore the nandroid and everything is fine. I am glad there is no permanent damage done. Cannot wait for the working version!
Firerat said:
Ok, I think I see the problem
Not at home right now,
But in the mean time you should be able to flash the remove zip and return to stock
Looks like a copy paste fail and I'm excluding userdata what I shouldn't be
May also be escaping when I shouldn't be
If you have problems flashing the remove zip you can mount cache manually via adb shell
( you can also flash_image a standard recovery.img via adb shell )
Click to expand...
Click to collapse

ywjkid said:
Thanks. Just reflashed recovery and restore the nandroid and everything is fine. I am glad there is no permanent damage done. Cannot wait for the working version!
Click to expand...
Click to collapse
new version here
http://www.mediafire.com/?7w9sh54lm3mwi
9074fde94c8e534585da4adaa5e59e14 FR-AutoMTD_partitionPatcher_v1.5.7.tar.bz2
919db3e671d0688af9824f37b16ccc87 FR-boot-v1.5.7-CustomMTD_S.zip
05828d98920540c711e06abe5028388f FR-recovery-v1.5.7-CustomMTD_S.zip
changed the 'remove' option
to revert to the stock MTD layout set system size to 0 in mtdpartmap.txt and flash the recovery patcher
e.g.
echo "mtd 0" > /sdcard/mtdpartmap.txt

Great! now the recovery error is gone and the mod is working on my EVO, beautifully. More than 600M for /data. Thank you so much, Firerat. You're the best!
Code:
df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 207.4M 0 207.4M 0% /dev
tmpfs 207.4M 0 207.4M 0% /mnt/asec
/dev/block/mtdblock4 240.0M 195.1M 44.9M 81% /system
/dev/block/mtdblock6 637.6M 374.7M 262.9M 59% /data
tmpfs 8.0M 4.0K 8.0M 0% /app-cache
/dev/block/mtdblock6 637.6M 374.7M 262.9M 59% /cache
PS. It seems /cache and /data now share the same space. It is new to me. Does that mean there is only one size need to specify in mtdpartmap.txt?
Firerat said:
new version here
http://www.mediafire.com/?7w9sh54lm3mwi
9074fde94c8e534585da4adaa5e59e14 FR-AutoMTD_partitionPatcher_v1.5.7.tar.bz2
919db3e671d0688af9824f37b16ccc87 FR-boot-v1.5.7-CustomMTD_S.zip
05828d98920540c711e06abe5028388f FR-recovery-v1.5.7-CustomMTD_S.zip
changed the 'remove' option
to revert to the stock MTD layout set system size to 0 in mtdpartmap.txt and flash the recovery patcher
e.g.
echo "mtd 0" > /sdcard/mtdpartmap.txt
Click to expand...
Click to collapse

ywjkid said:
Great! now the recovery error is gone and the mod is working on my EVO, beautifully. More than 600M for /data. Thank you so much, Firerat. You're the best!
Code:
df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 207.4M 0 207.4M 0% /dev
tmpfs 207.4M 0 207.4M 0% /mnt/asec
/dev/block/mtdblock4 240.0M 195.1M 44.9M 81% /system
/dev/block/mtdblock6 637.6M 374.7M 262.9M 59% /data
tmpfs 8.0M 4.0K 8.0M 0% /app-cache
/dev/block/mtdblock6 637.6M 374.7M 262.9M 59% /cache
PS. It seems /cache and /data now share the same space. It is new to me. Does that mean there is only one size need to specify in mtdpartmap.txt?
Click to expand...
Click to collapse
you still need to specify size of cache , the minimum is 2mb
on your phone /cache is actually a bind mount of /data/cache
its there if anything needs to use it, for instance your rom may want to put dalvik-cache in /cache/dalvik-cache
it will actually be on /data, the advantage is that you can make better use of what was free space on /cache

That's indeed a nice advantage. A million thanks. Now I can throw everything in the phone storage without worrying about the space.
Firerat said:
you still need to specify size of cache , the minimum is 2mb
on your phone /cache is actually a bind mount of /data/cache
its there if anything needs to use it, for instance your rom may want to put dalvik-cache in /cache/dalvik-cache
it will actually be on /data, the advantage is that you can make better use of what was free space on /cache
Click to expand...
Click to collapse

Noob tutorial
THIS IS SO COOL. THANK YOU SO MUCH FIRERAT.
Hope this mod helps everyone. Just like it is helping me
Thanks anyone.
TUTORIAL FOR NOOBS
In TERMINAL:
1. for Fresh Evo 3.4.0.1: echo "mtd 210 3" > /sdcard/mtdpartmap.txt *****(you can do less than 210 for cm6 if you desire)*****
2. adb shell reboot recovery
In RECOVERY MENU
1. nandroid backup
2. wipe data/factory reset
3. wipe cache
4. wipe Dalvik-cache
5. flash fr-recovery.zip
6. wipe data/factory reset
7. wipe cache
8. wipe Dalvik-cache
In TERMINAL
1. adb shell reboot recovery
In RECOVERY MENU
1.2*. IF YOU GET A CACHE ERROR DO NOT ALARM IT MEANS SOMETHING WENT WRONG. ALL YOU NEED TO DO IS WIPE DATA, CACHE, AND DALVIK-CACHE AND FLASH fr-recovery.zip and then when it finish flashing - adb reboot recovery - from terminal
1.3** IF YOU DID NOT GET THE ABOVE ERROR GO TO STEP 2
2. flash ROM (or nandroid backup)
3. flash app (I.E. cm6 google apps)
4. flash kernal (if one)
5. flash fr-boot.zip
6. reboot
7. DONE!!! AND ENJOY THANKS TO FIRERAT (DONT FORGET TO THANKS HIM)
If you want to update/install a kernal
In TERMINAL
1. adb shell reboot recovery
In RECOVERY MENU
2. wipe cache
3. wipe Dalvik-cache
4. flash KERNAL
5. flash fr-boot.zip
6. reboot
7. Sit and let EVO turn on
*****for reset partitions--- echo "mtd 0" > /sdcard/mtdpartmap.txt**** (IF YOU WANT TO GO BACK TO STOCK) and flash the FR-AutoMTD_partitionPatcher then flash any ROM you want or NANDROID BACKUP
+++IF I DID ANYTHING WRONG UP THERE FEEL FREE IN CORRECTING ME +++

mrcamposd said:
THIS IS SO COOL. THANK YOU SO MUCH FIRERAT.
Can anyone post a tutorial for noobs?
Or is this the same as for the HERO?
Hope this mod helps everyone. Just like it is helping me
Thanks anyone.
Click to expand...
Click to collapse
I can confirm the process is the same as for the HERO.

mrcamposd said:
THIS IS SO COOL. THANK YOU SO MUCH FIRERAT.
*****for reset partitions--- echo "mtd 0" > /sdcard/mtdpartmap.txt**** (IF YOU WANT TO GO BACK TO STOCK) and flash the FR-AutoMTD_partitionPatcher then flash any ROM you want or NANDROID BACKUP
Click to expand...
Click to collapse
How do I flash this? It doesn't show up in the list of zip files in recovery. I tried renaming it and extracting it but it doesn't look like it's in a flashable format.

antiphon said:
How do I flash this? It doesn't show up in the list of zip files in recovery. I tried renaming it and extracting it but it doesn't look like it's in a flashable format.
Click to expand...
Click to collapse
i think you just need to rename the file's extension to xxxxx.zip (because .zip's are the one you flash in recovery), but then again I have not used that file. So not responsible for damages or anything. Try it at your own risk buddy.

mrcamposd said:
*****for reset partitions--- echo "mtd 0" > /sdcard/mtdpartmap.txt**** (IF YOU WANT TO GO BACK TO STOCK) and flash the FR-AutoMTD_partitionPatcher then flash any ROM you want or NANDROID BACKUP
+++IF I DID ANYTHING WRONG UP THERE FEEL FREE IN CORRECTING ME +++
Click to expand...
Click to collapse
FR-AutoMTD_partitionPatcher , is linux shell script to shoehorn the boot patcher into a rom zip ( so the end user dosn't need to flash the boot patcher , its automagic ) ,, you don't really need it
to get back to stock layout,
do the mtd 0 thing
nand backup
flash the recovery patcher
format system cache and data ( I recommend clockwork recovery )
reboot
nand restore ( providing the backup will fit stock ! )
flash boot patcher
your done
Note, v1.5.7b is newer

Had this working well on my Hero, so I'm looking forward to putting this on my new Evo as well!

Doesn't Calkulin have an evo version posted?
Sent From My HTC Evo 4G Using Tapa Talk Pro!

113MB of bad blocks on /data...can i be helped???

Edit: summary of what ive tried and failed with.
Wipe all userdata from cwm and amon recovery ... no effect.
erase_image from cwm ... no effect.
fastboot erase ... no effect.
fastboot erase -w ... no effect.
RUU ... no effect.
cat zero to mtd ... no effect.
dd zero to mtd ... no effect.
flash_image (image edited with hex editor to contain only zero's) ... no effect.
fastboot oem task 28 ... no effect.
fastboot oem task 29 ... no effect.
fastboot flash hboot (different partition tables) ... no effect.
I'm out of ideas.
Original post:
Even after clearing all userdata from recovery and erasing userdata from fastboot i am missing over 100mb from /data, but there are no files there taking up the space.
How can i reclaim this space, is it corrupted??? How do i check for (and fix) a corrupt filesystem on android?
I'm thinking of flashing a new HBOOT, oxygen table, but if it's corrupt will it screw it up or fix it?
Below was done from recovery and fastboot and shows the problem, look at how much space is in use on data after wipe.
Code:
[email protected]:~$ sudo su
[email protected]:/home/mercianary# adb shell
/ # mount -a
mount: mounting /dev/block/mmcblk0p2 on /sd-ext failed: No such file or directory
/ # df -hm
Filesystem Size Used Available Use% Mounted on
tmpfs 203.2M 0 203.2M 0% /dev
/dev/block/mtdblock4 95.0M 1.1M 93.9M 1% /cache
/dev/block/mtdblock3 145.0M 132.6M 12.4M 91% /system
/dev/block/mtdblock5 197.6M 187.5M 10.2M 95% /data
/dev/block/mmcblk0p1 3.7G 3.4G 302.9M 92% /sdcard
[B]/ # #wipe all userdata from recovery (amonra 2.0.0)[/B]
/ # mount -a
mount: mounting /dev/block/mmcblk0p2 on /sd-ext failed: No such file or directory
/ # df -hm
Filesystem Size Used Available Use% Mounted on
tmpfs 203.2M 0 203.2M 0% /dev
/dev/block/mtdblock3 145.0M 132.6M 12.4M 91% /system
/dev/block/mtdblock4 95.0M 1.2M 93.8M 1% /cache
[B]/dev/block/mtdblock5 197.6M 113.3M 84.4M 57% /data[/B]
/dev/block/mmcblk0p1 3.7G 3.3G 378.5M 90% /sdcard
/ # reboot bootloader
[B][email protected]:/home/mercianary# fastboot erase userdata
erasing 'userdata'... OKAY[/B]
[email protected]:/home/mercianary# #into recovery again
[email protected]:/home/mercianary# adb shell
/ # mount -a
mount: mounting /dev/block/mmcblk0p2 on /sd-ext failed: No such file or directory
/ # df -hm
Filesystem Size Used Available Use% Mounted on
tmpfs 203.2M 0 203.2M 0% /dev
/dev/block/mtdblock4 95.0M 1.2M 93.8M 1% /cache
/dev/block/mtdblock3 145.0M 132.6M 12.4M 91% /system
[B]/dev/block/mtdblock5 197.6M 113.3M 84.4M 57% /data[/B]
/dev/block/mmcblk0p1 3.7G 3.3G 378.5M 90% /sdcard
/ # ls /data
lost+found
/ # du /data
2 /data/lost+found
4 /data
I'm using
CM7
amonra recovery 2.0.0
N1 Boot table
Any help troubleshooting this would be great, thanks.

did you wipe the /data/ partition in mounts & storage in recovery? try that if not, also try flashing a stock ruu, it will revert and changes made to the MTD Partitions

that was the first thing i tried, no luck. it erased fine but space was still missing
I dont particularly want to flash a RUU or another HBOOT untill i know what's wrong because if there's 100mb of bad nand on my phone i can imagine flashing a RUU or HBOOT going very wrong and leaving me with a very pretty paperweight.

I tried flashing some different hboots, problem still there, it just moves round a bit....
on the original boot table the space is missing on system and data..about 10mb or 20mb on system, the rest on data.
on oxygen and n1 boot table its just missing on data.
I cant seem to reclaim this space
anyone know how to check the disk for errors?

thats bad news, sounds like you may have some corrupt blocks

AndroHero said:
thats bad news, sounds like you may have some corrupt blocks
Click to expand...
Click to collapse
just a few, only 897 of them the phone is still working, so i suppose i'm kinda lucky.
I think i may have screwed it up a few weeks ago when i was messing around with cat, dd, fastboot and flash_image. I remember when i finished messing around i tried to restore my nand backup back on it but it failed, looking back it must have been because it didnt fit anymore due to the bad blocks. This must have been when the corruption occured.
Is it normal to have this many bad blocks? i've never seen more than a few, i'm hoping they aren't actually bad and it just thinks they are because of something stupid i did, is there anything i can do to remove the bad block flag (if there is one???) and then try again?
Code:
/sdcard/badblock # flash_image userdata mtd5.img
mtd: MEMGETBADBLOCK returned 1 at 0x00000000 (errno=0)
mtd: MEMGETBADBLOCK returned 1 at 0x00020000 (errno=0)
mtd: MEMGETBADBLOCK returned 1 at 0x00040000 (errno=0)
mtd: MEMGETBADBLOCK returned 1 at 0x00060000 (errno=0)
mtd: MEMGETBADBLOCK returned 1 at 0x00080000 (errno=0)
mtd: not writing bad block at 0x00000000
mtd: not writing bad block at 0x00020000
mtd: not writing bad block at 0x00040000
...
edited because it put the post over the 30,000 character limit!
...
mtd: not writing bad block at 0x0c520000
mtd: not writing bad block at 0x0c540000
mtd: not writing bad block at 0x0c560000
mtd: not writing bad block at 0x0c580000
error writing userdata: No space left on device
/sdcard/badblock #

That's way too high. NAND blocks usually fail at once and in the same area but not that many at once unless it be software error or a major stressor placed on them. It may be faulty bad block management defuncting those cells. If you could somehow find a way to Secure Erase the NAND, it could help. NAND cells sometimes work fine after this and cell state becomes reset so all those marked bad will be recycled back in use to test. The reason why they can sometimes spring back to perfect retention after a SE is academically quite known.
------------------------------
- Sent via HTC Desire -

I guess that you should use an RUU as it should format nand. If it does not the update wikl fail which mesns that your bad block could never be recoverd. Keep in mind to use RUU and not a PB.img i believe it is safer as long as it comed to bricking the phone. I know that some pvt 1 boards had some bad blocks on nands but never so muny( if it is a pvt1) . Regards
Sent from my LeeDroided Desire HD

I decided to flash a ruu, that was scary, it failed the first time writing /system but successfully recovered itself and worked on the second attempt.
Available space on /data after RUU, 58.44MB not good
looks loke it didnt work, time to re root and get apps2sd, data2sd and the n1 boot table, lets see how i get on with 110MB missing from data, at least it will be fun

mate now that you used the RUU, why don't you return it to HTC for repairs? tell them that it happened whileattempting to update.
mercianary said:
I decided to flash a ruu, that was scary, it failed the first time writing /system but successfully recovered itself and worked on the second attempt.
Available space on /data after RUU, 58.44MB not good
looks loke it didnt work, time to re root and get apps2sd, data2sd and the n1 boot table, lets see how i get on with 110MB missing from data, at least it will be fun
Click to expand...
Click to collapse

mariosraptor said:
mate now that you used the RUU, why don't you return it to HTC for repairs? tell them that it happened whileattempting to update.
Click to expand...
Click to collapse
That's what I was planning to do but I decided against it for several reasons.
I'm not feeling lucky, I dont think I will get away with it this time.
With the nature of the problem I can imagine whoever gets their hands on it at HTC will look into what's happened and discover my warranty's void...paranoid I know.
It doesn't help that there is no RUU for orange UK branded desires, I have to use a dodgy method to unroot (restoring an old backup, removing superuser and su then updating OTA.)
I'm happy with the way it is at the moment, who knows, I might drop it under my car at some point in the near future

anyone know anything about performing a low level format or clearing the bad block map so i can start a fresh???
PS...turns out the stock orange rom doesn't even fit on /system because its missing 10MB of space...damn you orange bloatware...damn you to hell!!!
PPS...Bump.

Get in contact with a dev. I am sure they will help you out to access and do a secure wipe on your memory. Way beyond me for sure

Bricked and confused

I've been searching for a couple of days now - hence this post.
My Desire boots to HTC green on white - nothing more.
I can get to Bootloader / fastboot / recovery, here's some details :
Code:
Revolutionairy
Bravo PVE3 SHIP S-OFF
HBOOT-6.93.1002
MI CROP-051d
TOUCH PANEL-SYNW0101
RADIO-4.05.00.11
Aug 10 2010 12.75.10
Can flash RUU (RUU_Bravo_HTC_WWE_1.15.405.4_Radio_32.30.00.28U_4.05.00.11_release_122704) and it completes with no errors but all I gain (?) is the loss of recovery which I can restore using AndroidFlasher.
I have no access to multiple sdcards (formatted using gparted to fat32) which work in both my Win7 and Linux machines without issue - I don't think the sdcards are at fault.
Have done a full wipe and tried a couple of recoveries and am now on recovery-RA-desire-v2.0.1.img. They all give the same errors, ie :
Code:
E: Can't mount /dev/block/mmclk0p1 (or /dev/block/mmclk0) (No such file or directory)
E:Can't mount /sdcard
Searching for these has suggested that it's a USB brick but all fixes include loading something to the sdcard - which I have no access to.
Other things I've tried with no success :
Code:
fastboot oem enableqxdm 0
...
OKAY [ 0.096s]
finished. total time: 0.096s
fastboot oem eraseconfig
...
(bootloader) Erase config: complete
OKAY [ 0.097s]
finished. total time: 0.097s
Code:
fastboot flash misc mtd0.img
sending 'misc' (640 KB)...
OKAY [ 0.106s]
writing 'misc'...
OKAY [ 0.183s]
finished. total time: 0.289s
Code:
parted /dev/block/mmcblk0
Error: Could not stat device /dev/block/mmcblk0 - No such file or directory.
/dev/block # ls
ls
loop0 loop2 loop4 loop6 mtdblock0 mtdblock2 mtdblock4
loop1 loop3 loop5 loop7 mtdblock1 mtdblock3 mtdblock5
Code:
fastboot getvar cid
cid: HTC__001
finished. total time: -0.000s
Code:
/ # sdparted -es 512M -ss 256M -efs ext4
sdparted -es 512M -ss 256M -efs ext4
checking script requirements...
err: /dev/block/mmcblk0 does not exist!
Code:
/ # /sbin/e2fsck -p /dev/block/mmcblk0p2
/sbin/e2fsck -p /dev/block/mmcblk0p2
/sbin/e2fsck: No such file or directory while trying to open /dev/block/mmcblk0p
2
/dev/block/mmcblk0p2:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
It's like it's a "sdcard brick" but I've failed to find anything on that and that still doesn't explain why it doesn't boot. It used to boot with no sdcard.
This is now driving me mad, please can somebody provide some sanity ?

Have looked at bortak's troubleshooting guide? Ul get more info there. Look in Desire Q&A/ Stickies
Sent from my HTC Desire

Yes.
It seems I have two of the problems.
[1]BOOT PROBLEMS
[IF YOU DO NOT HAVE A BACKUP]
[STEP10b]- go back to the main menu, select "install zip from sdcard"
But I don't have a sdcard so ...
[13]RECOVERY CAN'T MOUNT SD-CARD
In fastboot :
Code:
fastboot oem enableqxdm 0
...
OKAY [ 0.097s]
finished. total time: 0.097s
fastboot oem eraseconfig
...
(bootloader) Erase config: complete
OKAY [ 0.135s]
finished. total time: 0.135s
Which in theory has mounted the sdcard but when I go into recovery for step [1]BOOT PROBLEMS it's no longer mounted.
The commands from [13]RECOVERY CAN'T MOUNT SD-CARD don't work in recovery - I get
Code:
< waiting for device >
Catch 22 and hence my confusion.
How do I mount the sdcard when in recovery - which is what it seems needs doing ?

It cant mount sdcard if u dont have 1. Ul have to buy 1
Sent from my HTC Desire

dik23 said:
I have no access to multiple sdcards (formatted using gparted to fat32) which work in both my Win7 and Linux machines without issue - I don't think the sdcards are at fault.
Click to expand...
Click to collapse
..

"But I don't have a sdcard so ..."
......
Sent from my HTC Desire

Ok ?

Lol what??? U don't have a SD card?
Sent from my SAMSUNG-SGH-I717 using xda premium

dik23 said:
I have no access to multiple sdcards (formatted using gparted to fat32) which work in both my Win7 and Linux machines without issue - I don't think the sdcards are at fault.
Click to expand...
Click to collapse
The "no" there is most likely a typo. The guy is saying that he DOES have multiple SD cards which work properly under W7 and Linux but not with the Desire.
dik23 said:
[1]BOOT PROBLEMS
[IF YOU DO NOT HAVE A BACKUP]
[STEP10b]- go back to the main menu, select "install zip from sdcard"
But I don't have a sdcard so ...
Click to expand...
Click to collapse
Again, he's not saying that he does not have an SD card, he's just saying that the procedure described in the guide requires that the phone "sees" the SD card but his phones does not.
Conclusion: he DOES have MULTIPLE WORKING SD cards, but the phone does NOT recognize them.
What the hell is wrong with you guys?

Theres fk all wrong with us. Ok if "no" was a typo then why does he say " but i dont have a sdcard so.." dont take it the wrong but was just a bit confusing. If they dont work, buy a new 1, like i already said because u need a sdcard
Sent from my HTC Desire

...
Again: he's saying that Bortak's guide requires him, at one point, to run a zip from the SD card, BUT HIS PHONE CANNOT MOUNT ANY SD CARD, thus he "does not have an SD card".

TVTV said:
...
Again: he's saying that Bortak's guide requires him, at one point, to run a zip from the SD card, BUT HIS PHONE CANNOT MOUNT ANY SD CARD, thus he "does not have an SD card".
Click to expand...
Click to collapse
Yes, that is exactly my problem. Sorry, I'd not spotted my typo

http://www.google.ie/url?sa=t&sourc...35n2CA&usg=AFQjCNEPzzSqlgqVMhPWLsFoY_dqWn0Xag
Have a read at that, mite help.
Sent from my HTC Desire

jmcclue said:
http://www.google.ie/url?sa=t&sourc...35n2CA&usg=AFQjCNEPzzSqlgqVMhPWLsFoY_dqWn0Xag
Have a read at that, mite help.
Click to expand...
Click to collapse
That thread ends :
the phone is now with the repair guys for next 2 weeks
Click to expand...
Click to collapse
So I flashed RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe and now it works - sort of
It now boots but still has no access to the sdcard.
Menu > Settings > SD & phone storage
shows SD card total/available space as "Unavailable" and the options to mount / format greyed out.

Lol sry, there is a link at the end too, i had a quick read at it and theres something saying about unlocking the sdcard so i thought maybe u have the same problem. Have look again and click the other link at the bottom, it explains more.
Sent from my HTC Desire

jmcclue said:
Lol sry, there is a link at the end too, i had a quick read at it and theres something saying about unlocking the sdcard so i thought maybe u have the same problem. Have look again and click the other link at the bottom, it explains more.
Click to expand...
Click to collapse
Sorry - I fail to find anything new there. All I find is the same instructions
Code:
fastboot oem enableqxdm 0
...
OKAY [ 0.096s]
finished. total time: 0.096s
fastboot oem eraseconfig
...
(bootloader) Erase config: complete
OKAY [ 0.097s]
finished. total time: 0.097s
And then your sdcard will be mounted.
It might be mounted right at that second but when I go into recovery / reboot it defiantly isn't.
Anyone got any ideas ?

Have now made a mtd0.img with this site. I am using RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed so used 2.29.405.5 for the ROM version. Uploaded both it and the file flash_image from this post :
Code:
adb push flash_image /data
adb push mtd0.img /data
adb shell
chmod u+x /data/flash_image
/data/flash_image misc /data/mtd0.img
That all went as planned but I am still left without a mountable sd card.
Is my Desire borked ?

dik23 said:
Is my Desire borked ?
Click to expand...
Click to collapse
Ok guys, thanks for all your help but I think I may have just answered my own question.
I've just noticed that it's not just the sd card it won't recognise. It's the SIM card too. This says to me that I've got a hardware rather than software issue here.
Sorry for wasting anyone's time. I need my phone for work calls and have not thought about inserting the SIM into a phone that doesn't work properly.
Again - thanks for your help here. Anyone know how much I can get for a spares / repairs Desire on the open market ?

Help with /dev/block/mmcblkxxx (HTC Desire 816)

The problem started when I flashed the philz touch recovery, and used the "Clear for new rom" in the wipe menu. I then proceeded to try to install two different roms unsuccessfully, as well as trying two different recoveries, and they always return the same error:
Code:
Mount:failed to mount /dev/block/mmcblk0p6
This is a strange error, since using the df command returns the following results:
Code:
tmpfs 683452 160 683292 0% /dev
tmpfs 683452 652 682800 0% /tmp
/dev/block/mmcblk0p42
273948 4408 269540 2% /cache
/dev/block/mmcblk0p44
4506568 707644 3798924 16% /data
/dev/block/mmcblk0p44
4506568 707644 3798924 16% /sdcard
/dev/block/mmcblk1p1 15540224 4846896 10693328 31% /external_sd
If I am understanding this correctly, the ROM should be installed on mmcblk0p44 since it is the internal drive and always has been, not mmcblk0p6, and I don't see why it needs access to mmcblk0p6.
I tried a method of repairing the filesystem using a mkfs.ext4 file, found in a blog.
I then used the following commands after putting the mkfs file in /tmp:
Code:
chmod 777 /tmp/mkfs.ext4
/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/mmcblk0p37
After this, I managed to get a ROM to report installing successfully, but when I booted the phone, it got stuck in a boot loop which was better than the immediate booting to recovery, and am now getting the same error again, and I can't boot the phone at all, it just goes into recovery.
I have tried to restore from previous backups, with no luck.
Can anyone help?

jacobjake683 said:
The problem started when I flashed the philz touch recovery, and used the "Clear for new rom" in the wipe menu. I then proceeded to try to install two different roms unsuccessfully, as well as trying two different recoveries, and they always return the same error:
Code:
Mount:failed to mount /dev/block/mmcblk0p6
This is a strange error, since using the df command returns the following results:
Code:
tmpfs 683452 160 683292 0% /dev
tmpfs 683452 652 682800 0% /tmp
/dev/block/mmcblk0p42
273948 4408 269540 2% /cache
/dev/block/mmcblk0p44
4506568 707644 3798924 16% /data
/dev/block/mmcblk0p44
4506568 707644 3798924 16% /sdcard
/dev/block/mmcblk1p1 15540224 4846896 10693328 31% /external_sd
If I am understanding this correctly, the ROM should be installed on mmcblk0p44 since it is the internal drive and always has been, not mmcblk0p6, and I don't see why it needs access to mmcblk0p6.
I tried a method of repairing the filesystem using a mkfs.ext4 file, found in a blog.
I then used the following commands after putting the mkfs file in /tmp:
Code:
chmod 777 /tmp/mkfs.ext4
/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/mmcblk0p37
After this, I managed to get a ROM to report installing successfully, but when I booted the phone, it got stuck in a boot loop which was better than the immediate booting to recovery, and am now getting the same error again, and I can't boot the phone at all, it just goes into recovery.
I have tried to restore from previous backups, with no luck.
Can anyone help?
Click to expand...
Click to collapse
Could you please provide me with the mkfs.ext4 binary? The link in that blog has expired.
I'm also having problems with my partitions and can't flash anything. I can't relock the bootloader either.
If you have stock recovery installed on your phone, you should relock the bootloader. Then run the ruu. That should fix the problem.
Thanks in advance.

uhm said:
Could you please provide me with the mkfs.ext4 binary? The link in that blog has expired.
I'm also having problems with my partitions and can't flash anything. I can't relock the bootloader either.
If you have stock recovery installed on your phone, you should relock the bootloader. Then run the ruu. That should fix the problem.
Thanks in advance.
Click to expand...
Click to collapse
Sorry, but I do not have the file anymore due to the fact that I have gone through various hard drive formats and I don't seem to have it on the HTC anymore.

No problem. Thanks for your reply.

Unable to mount EFI Operation not supported on transport endpoint

I have a family member's phone (N7100) that was stuck on a bootloop. This phone was never rooted or had any custom recoveries or roms installed on it. When I go into recovery I see that I'm getting the common "e:failed to mount /efs(invalid argument)". When trying to google the problem I found that common fix for it:
Code:
adb shell
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3 /efs
So I go ahead and do this but I notice that even though the phone is out of a bootloop and goes into factory mode (I already know how to get out of it), it doesn't connect to the phone network. Going back to recovery I see that EFI is still not able to be mounted but the error is different "failed to mount /efs Operation not supported on transport endpoint".
I can tell that if I ADB into the phone and do "mount -w -t ext4 /dev/block/mmcblk0p3 /efs" it will mount just fine. Anybody knows what is happening? To make everything worse he doesn't have a EFI backup so at this point I'm thinking the phone is dead no matter what. Suggestions?
Thanks

Try flashing stock ROM.

Skull97 said:
Try flashing stock ROM.
Click to expand...
Click to collapse
I already did and it didn't help. Googling the problem doesn't seem to give me any results for that particular error line.

Bump! I hate to do this but I think this is my last chance to fix it. Google is not giving me any good leads for me to latch on.