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!

[HOW TO] Extract a stock image to restore to

Ok, there don't seem to be many, if any stock images to revert to if you need to restore and send back your phone. Especially if you have a custom rom like me.
I DO NOT ACCEPT ANY RESPONSIBILITY IF YOUR BREAK YOUR DEVICE, CAUSE WW3 ETC
Can someone just check over this. I think it will work but I can't guarantee it. Once we know it works, we can get people to extract various images so we all have something to restore to.
1) Download the CWM image: DOWNLOAD
We need to do it this way because ROM Manager requires root
2) Use fastboot to unlock the bootloader on the device. At the same time, this will wipe the phone to the clean stock image:
fastboot oem unlock
4) Use fastboot to boot CWM, NOT flash it. This will temporarily boot into CWM, however it will not flash it to your device:
fastboot boot recovery-clockwork-5.5.0.2-maguro.img
5) Once in CWM, go to backups and perform a full device backup
6) Reboot your device. If you want, lock the bootloader to return to how it was when you got it:
fastboot oem lock
7) Upload the backup for all to use
Click to expand...
Click to collapse
Now, technically that will have created a backup of every stock image on this system, correct?
If so, that should give us all something to restore to, should you need to send it back for any reason. To restore you would need to:
1) Download a backup and put it onto /sdcard/ of your rooted phone
2) Use fastboot to boot into CWM as above if you haven't flashed it. If not, just boot into CWM Recovery
3) Go to backups and restore the backup from above
4) *Not sure if recovery.img will have been restored. If not, use a stock recovery.img
5) Use fastboot to lock the bootloader:
fastboot oem lock
Click to expand...
Click to collapse
This should take us back to stock. The only thing I see it not flashing is the recovery.img. Not too sure how we can get that, however perhaps the Peter Alfonze recovery.img would work
Appreciated if someone could give this a second opinion and their thoughts

Evostance said:
Ok, there don't seem to be many, if any stock images to revert to if you need to restore and send back your phone. Especially if you have a custom rom like me.
DO NOT ATTEMPT THIS YET. NEED TO GET IT CHECKED OVER FIRST
Can someone just check over this. I think it will work but I can't guarantee it. Once we know it works, we can get people to extract various images so we all have something to restore to.
Now, technically that will have created a backup of every stock image on this system, correct?
If so, that should give us all something to restore to, should you need to send it back for any reason. To restore you would need to:
This should take us back to stock. The only thing I see it not flashing is the recovery.img. Not too sure how we can get that, however perhaps the Peter Alfonze recovery.img would work
Appreciated if someone could give this a second opinion and their thoughts
Click to expand...
Click to collapse
Hmm, that's a good idea, BUT we can also boot in the CWM image and from there dd all partitions. I only don't know if you boot with fastboot boot, that img file is mounted on the usual boot partition

Yes, that should save all partitions, including sytem, data, boot, radio, recovery etc. I'm just not sure if you will be able to backup data partition since it's auto-mounted in recovery (otherwise you wont be able to see the content of virtual SD card):
Code:
0 /tmp ramdisk (null) (null) 0
1 /system ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/system (null) 0
2 /cache ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/cache (null) 0
[B]3 /data auto /dev/block/platform/omap/omap_hsmmc.0/by-name/userdata (null) 0[/B]
4 /misc emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/misc (null) 0
5 /boot emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/boot (null) 0
6 /recovery emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/recovery (null) 0
7 /sbl emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/sbl (null) 0
8 /xloader emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/xloader (null) 0
9 /radio emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/radio (null) 0
To be honest this is very bad solution in Samsung Galaxy Nexus. Also I'm not sure why HSMMC devices are flagged as EMMC. I tried contacting with koush about it but no answer from him. OK, sorry, no more hijacking your thread

netchip said:
Hmm, that's a good idea, BUT we can also boot in the CWM image and from there dd all partitions. I only don't know if you boot with fastboot boot, that img file is mounted on the usual boot partition
Click to expand...
Click to collapse
That was my only concern
mike1986. said:
Yes, that should save all partitions, including sytem, data, boot, radio, recovery etc. I'm just not sure if you will be able to backup data partition since it's auto-mounted in recovery (otherwise you wont be able to see the content of virtual SD card):
Code:
0 /tmp ramdisk (null) (null) 0
1 /system ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/system (null) 0
2 /cache ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/cache (null) 0
[B]3 /data auto /dev/block/platform/omap/omap_hsmmc.0/by-name/userdata (null) 0[/B]
4 /misc emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/misc (null) 0
5 /boot emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/boot (null) 0
6 /recovery emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/recovery (null) 0
7 /sbl emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/sbl (null) 0
8 /xloader emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/xloader (null) 0
9 /radio emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/radio (null) 0
To be honest this is very bad solution in Samsung Galaxy Nexus. Also I'm not sure why HSMMC devices are flagged as EMMC. I tried contacting with koush about it but no answer from him. OK, sorry, no more hijacking your thread
Click to expand...
Click to collapse
I know its not an ideal solution, but if we can get this to work, at least it gives us an option in the short run

Nobody got any other views?

Why other views? It will simply work, even with mounted data partition.

mike1986. said:
Why other views? It will simply work, even with mounted data partition.
Click to expand...
Click to collapse
That'll do! Now, just need to get someone to do it before they flash a custom rom...

I haven't flashed anything yet. I can wipe and make a nandroid backup, if it is needed.

matt2053 said:
I haven't flashed anything yet. I can wipe and make a nandroid backup, if it is needed.
Click to expand...
Click to collapse
Please!
Sent from my Galaxy Nexus using Tapatalk

Ok, so if you want to go back to stock quick and dirty, this should do the trick.
1. Download this zip.
2. Extract to /sdcard/clockworkmod/backup
3. Boot into ClockworkMod recovery.
4. Restore backup "maguro_4.0.1"
http://www.mediafire.com/?7k9076axlyg7r7u

Thanks. I might need this as I have a few dead pixels and I'm looking to return and get a new one.

matt2053 said:
Ok, so if you want to go back to stock quick and dirty, this should do the trick.
1. Download this zip.
2. Extract to /sdcard/clockworkmod/backup
3. Boot into ClockworkMod recovery.
4. Restore backup "maguro_4.0.1"
http://www.mediafire.com/?7k9076axlyg7r7u
Click to expand...
Click to collapse
Downloading and saving just for the sake of saving it you never know.
Sent from my Galaxy Nexus using xda premium

Could someone please confirm it works? Thanks!
Sent from my Sensation using XDA App

matt2053 said:
Ok, so if you want to go back to stock quick and dirty, this should do the trick.
1. Download this zip.
2. Extract to /sdcard/clockworkmod/backup
3. Boot into ClockworkMod recovery.
4. Restore backup "maguro_4.0.1"
http://www.mediafire.com/?7k9076axlyg7r7u
Click to expand...
Click to collapse
Where did you get that zip from?
Sent from my Galaxy Nexus using Tapatalk

Evostance said:
Where did you get that zip from?
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I made it. I am still in factory stock, so I just did a factory reset and made the backup.
Sent from my Galaxy Nexus using XDA App

matt2053 said:
I made it. I am still in factory stock, so I just did a factory reset and made the backup.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Top guy! Thanks a lot

Let us know if you manage to flash back to stock successfully using this.

This will definitely work for rooted users and the stock recovery from PeterAlphonzo's images can be fastbooted back on if desired. A couple notes of caution though:
After restoring this backup, you will still be rooted and therefore not completely stock.
The radio is not backed up and restored by CWM and cannot be extracted using DD because it comes up all FF bytes in the image rendered. This shouldn't be of critical importance to most users because the radio is not typically altered by user modifications anyway, so this still gives you your best method of restoring a stock configuration until an official set of images is made available.

cellzealot said:
After restoring this backup, you will still be rooted and therefore not completely stock.
Click to expand...
Click to collapse
If you mean unlocked, that's what fastboot oem lock is for.

Ok, by using various images, zips etc posted on here. I've managed to get the phone back to the stock unrooted rom, stock kernels etc and the stock recovery.
I'll post a tutorial up later

Need Help Please WIND 889V Borked

Hi everyone. Yesterday I flashed a teshxx ROM and the 8K modem and when I booted there was "unknown baseband".
I flashed the Canadian modem and same thing. I tried a factory reset from recovery and got a bootloop where after the Samsung
boot animation it loops back to the logo. I lastly tried a stock factory image and the results are the same a never ending loop after the animation on
boot sequence. ANY help would be HUGELY appreciated here getting desperate.
Thanks.

Okay can boot now but still no baseband or IMEI.

I think you corrupted your imei
Sent from my Nexus 4 using XDA Premium HD app

Try the following: flash back to the 8K modem, and if the bootloops stop (you still probably won't have service) have a look at these threads:
Download this file: http://forum.xda-developers.com/attachment.php?attachmentid=1580200&d=1356058365
Which originally comes from this thread: http://forum.xda-developers.com/showthread.php?t=2056581
And use the tools in this thread to repair your IMEI and NV items: http://forum.xda-developers.com/showthread.php?t=1804117
The problem so far is that unlike with other Note II devices, modem cross-flashes on the T889V have been irreversible, so you might still be stuck with the T-Mobile modem.
Good luck,
Darkshado

odceop data
Darkshado said:
Try the following: flash back to the 8K modem, and if the bootloops stop (you still probably won't have service) have a look at these threads:
Download this file: http://forum.xda-developers.com/attachment.php?attachmentid=1580200&d=1356058365
Which originally comes from this thread: http://forum.xda-developers.com/showthread.php?t=2056581
And use the tools in this thread to repair your IMEI and NV items: http://forum.xda-developers.com/showthread.php?t=1804117
The problem so far is that unlike with other Note II devices, modem cross-flashes on the T889V have been irreversible, so you might still be stuck with the T-Mobile modem.
Good luck,
Darkshado
Click to expand...
Click to collapse
I cannot get the programs to connect to my phone. I can boot by using CWM to mount and then fixing permissions but no baseband, SIM card recognition or IMEI.

How did you made it boot ? Did you try nv writer to fix imei

Fixed permissions and mounts. With NV Writer I get phone did not answer errors.

MitchPT said:
Fixed permissions and mounts. With NV Writer I get phone did not answer errors.
Click to expand...
Click to collapse
Can you run df command in adb shell or in a terminal app and match with the below output. I have a doubt that /tombstones is missing due to bad rom flash.
Filesystem Size Used Free Blksize
/dev 895M 84K 895M 4096
/mnt/asec 895M 0K 895M 4096
/mnt/obb 895M 0K 895M 4096
/system 1G 1G 591M 4096
/efs 19M 4M 15M 4096
/cache 1G 21M 1G 4096
/data 11G 1G 9G 4096
/tombstones 251M 18M 233M 4096
/firmware 199M 90M 109M 4096
/storage/sdcard0 10G 1G 9G 4096
/mnt/asec/com.citiuat-1 3M 1M 1M 4096
/storage/extSdCard 3G 2G 1G 32768

Hello sjravi, having experienced issues similar to MitchPT I tried running the df command like you suggested, the /tombstones data seems present, but have a look at the /firmware partition, it's nowhere near as full as yours:
Code:
[email protected]:/ # df
Filesystem Size Used Free Blksize
/dev 895M 84K 895M 4096
/mnt/asec 895M 0K 895M 4096
/mnt/obb 895M 0K 895M 4096
/system 1G 1G 504M 4096
/efs 19M 4M 15M 4096
/cache 1G 22M 1G 4096
/data 11G 7G 3G 4096
/tombstones 251M 18M 233M 4096
/firmware 199M 45M 154M 4096
/storage/sdcard0 10G 7G 3G 4096
/mnt/asec/com.shazam.encore.android-1 10M 7M 2M 4096
/mnt/asec/com.fishstix.dosbox-1 11M 9M 1M 4096
/mnt/asec/app.fltplan-1 22M 21M 1M 4096
/mnt/asec/com.keramidas.TitaniumBackupPro-1 2M 108K 1M 4096
[email protected]:/ # ls /firmware
image
[email protected]:/ # ls -l /firmware/image
-rw-r--r-- root root 40 2012-10-02 09:15 acdb.mbn
-rw-r--r-- root root 2506592 2012-10-02 09:18 apps.mbn
-rw-r--r-- root root 2720440 2012-10-02 09:19 dsp1.mbn
-rw-r--r-- root root 30283208 2012-10-02 09:44 dsp2.mbn
-rw-r--r-- root root 6325056 2012-10-02 09:49 dsp3.mbn
-rw-r--r-- root root 40 2012-10-02 09:40 efs1.mbn
-rw-r--r-- root root 40 2012-10-02 09:40 efs2.mbn
-rw-r--r-- root root 40 2012-10-02 09:40 efs3.mbn
-rw-r--r-- root root 2097152 2012-10-02 09:11 mdm_acdb.img
-rw-r--r-- root root 2714796 2012-10-02 09:12 modem_ds.ima
-rw-r--r-- root root 6908 2012-10-02 09:49 q6.mdt
-rw-r--r-- root root 130124 2012-10-02 09:15 rpm.mbn
-rw-r--r-- root root 124916 2012-10-02 09:13 sbl1.mbn
-rw-r--r-- root root 249000 2012-10-02 09:14 sbl2.mbn
[email protected]:/ #

Darkshado your firmware partition data size is right, I have added additional files on my device dont bother about it.
Youe device is t889v right?
Sent from my Note 2

Ok thanks, and yes it's a T889V.

Darkshado said:
Ok thanks, and yes it's a T889V.
Click to expand...
Click to collapse
Hey your partitions are same as i317, did flash i317 rom by repartitioning? Looks like this could be the issue.
Sent from my Note 2

sjravi said:
Darkshado your firmware partition data size is right, I have added additional files on my device dont bother about it.
Youe device is t889v right?
Sent from my Note 2
Click to expand...
Click to collapse
I have the same issue, I think we need the .pit for the T889 to fix all partitions and the do the NV corrections. I have a thread in place for any kind soul willing to help us that have encountered the error.
http://forum.xda-developers.com/showthread.php?p=36010956#post36010956

sjravi said:
Hey your partitions are same as i317, did flash i317 rom by repartitioning? Looks like this could be the issue.
Sent from my Note 2
Click to expand...
Click to collapse
It's a long story. Here's an abridged version:
Got T889V, brand new from Mobilicity.
Flashed CF-AutoRoot the next day, kissed warranty goodbye, will remember it fondly.
Unlocked with ServiceMode menu.
Got an LTE microSIM, confirmed working in VMC demo GS3.
Backed up /efs (Mistake #1, this being insufficient with Qualcomm radios. Last time I had played with QPST was four phones ago.)
Flashed N7100 CWM
Nandroid backup
Decided working LTE would be nice...
Attempted flashing I317M modem through Odin. Failed before write operation, no harm done.
Made custom update zip with the I317M modem.bin (from Sammobile Odin tarball) based off the T889V modem zip posted here on XDA.
Flashed through CWM
LTE works! But IMEI shows 0.
Tried reverting mod by flashing T889V modem back through CWM.
Booooooootloooop! Too early for any logcat or dmesg messages to come through.
Tried flashing various modem/boot.img/ROM combinations, clearing data, cache, Dalvik and so on, many failed attempts.
Flashed stock T889V ROM, with I317M modem, no bootloops, but no service either.
Wrote NV items from a T-Mobile T889, in addition to my IMEI with NV_reader_writer. Rebooted.
Phone operational again.
Tried flashing T889V modem again through both Odin and CWM, bootloops again.
Reflashing the I317M modem works.
All that has left me stuck on the I317M modem, with LTE and DC-HSPA including on the AWS bands.

Sorry for the late reply, any particular reason for going back to t889v modem?
Dc hspa can be verified from the *#197328640# umts > debug screen > basic info
Here hspa connection will be displayed when data transfer is ongoing. If you see "dc hspa 1" then its dc

I wanted to be sure I could go back and forth for warranty purposes or in case things didn't work out with the I317M modem over time.
I've noticed hkfan's m9kefs1, 2 and 3 dumps in this thread, which could well be the solution I was looking for. But since I have a working phone, I'm not sure I feel like messing around with my modem again, with real life about to get much busier.
I made a quick test like you suggested, DC-HSPA works for me.

Darkshado said:
I wanted to be sure I could go back and forth for warranty purposes or in case things didn't work out with the I317M modem over time.
I've noticed hkfan's m9kefs1, 2 and 3 dumps in this thread, which could well be the solution I was looking for. But since I have a working phone, I'm not sure I feel like messing around with my modem again, with real life about to get much busier.
I made a quick test like you suggested, DC-HSPA works for me.
Click to expand...
Click to collapse
Thats exactly what I wanted to suggest, its kind of risky to try with a working phone.

Darkshado said:
It's a long story. Here's an abridged version:
Got T889V, brand new from Mobilicity.
Flashed CF-AutoRoot the next day, kissed warranty goodbye, will remember it fondly.
Unlocked with ServiceMode menu.
Got an LTE microSIM, confirmed working in VMC demo GS3.
Backed up /efs (Mistake #1, this being insufficient with Qualcomm radios. Last time I had played with QPST was four phones ago.)
Flashed N7100 CWM
Nandroid backup
Decided working LTE would be nice...
Attempted flashing I317M modem through Odin. Failed before write operation, no harm done.
Made custom update zip with the I317M modem.bin (from Sammobile Odin tarball) based off the T889V modem zip posted here on XDA.
Flashed through CWM
LTE works! But IMEI shows 0.
Tried reverting mod by flashing T889V modem back through CWM.
Booooooootloooop! Too early for any logcat or dmesg messages to come through.
Tried flashing various modem/boot.img/ROM combinations, clearing data, cache, Dalvik and so on, many failed attempts.
Flashed stock T889V ROM, with I317M modem, no bootloops, but no service either.
Wrote NV items from a T-Mobile T889, in addition to my IMEI with NV_reader_writer. Rebooted.
Phone operational again.
Tried flashing T889V modem again through both Odin and CWM, bootloops again.
Reflashing the I317M modem works.
All that has left me stuck on the I317M modem, with LTE and HSPA (possibly DC-HSPA, any definitive way to tell aside from a speed test?) including on the AWS bands.
Click to expand...
Click to collapse
First of all, thank you. I have used your steps to recover my phone! However, I cannot make phone calls. Can you provide more details on step 17, about how you wrote NV items? Thanks again!

Check out post #4 I made in this thread, it links the tools and backups you'll want to attempt restoring to your phone.
Good luck,
Darkshado
P.S. I also got your PM, but this sort of stuff is usually best discussed in public threads.

Can I ask you something. .?
Our Galaxy note 2 from wind or mobility. .... Do they support video calling and multiple screen ???
My friend had a N7100 .. n he gets to get video calling right from the contacts menu ..n multiple screen when back key is pressed for coupe of seconds ...
Sent from my SGH-T889V using xda app-developers app

[Q] After restart doesnt start

Hi,
About a month I used rom AR and I was aware of her faults (which yesterday revealed that it is not true), that when I restart, phone must be connected to the pc, and start bootloader via fastboot and the Command Promt flash boot.img dissected from ROM. Fortunately ROM, stable, so I followed all the time does not restart.
Yesterday I got a taste for change (and I wanted to get rid of the problem) and I downladed at first 4.4 ROM from xda taktik then 4.3JB and finally cyangen mod 7.2 Problem unfortunately stayed at all the same. When restarting HTC logo flashes and then turns off the display and starts "black" will flash this is over, unless we do the above procedure via the bootloader.
Does anyone an idea how to fix it?
Thnx

Have you format system + data + cache in mount and storage after wipe data cache and dalvik cache? Try this, if not success I think the only way is download the latest ruu and run it. You will be go back to stock. And we can use tools to root and flash custom recovery.
Sent from my Desire HD using Tapatalk

@Pilsner12 what the state of your phone bootloader..?, is that just unlocked with s-on..?, or already s-off..?, and what a custom recovery you used..?
if your phone is just unlocked with still s-on...did you already flashing a boot.img from the rom.zip that you already installed..?

to JJeamy:
bootloader is s-on, with touched clockworkmod 5.8.1.5, ROM cyanogen mod 7.2
if I standartly restart phone, didnt start. I must connect phone to pc, run bootloader, than fastboot and from pc via command prompt "send" boot.img (prepared from cm7.2) than phone restart and start correctly.
to pauleversham:
I will try it again (but I thing everythning expect SD card was formated, wiped, etc..) If I run RUU rom, I lost root permision, or is it possible get rooted RUU?

Pilsner12 said:
to JJeamy:
bootloader is s-on, with touched clockworkmod 5.8.1.5, ROM cyanogen mod 7.2
if I standartly restart phone, didnt start. I must connect phone to pc, run bootloader, than fastboot and from pc via command prompt "send" boot.img (prepared from cm7.2) than phone restart and start correctly.
to pauleversham:
I will try it again (but I thing everythning expect SD card was formated, wiped, etc..) If I run RUU rom, I lost root permision, or is it possible get rooted RUU?
Click to expand...
Click to collapse
so...you mean that you've already/ always flashing boot.img from the rom.zip itself after installing the rom from recovery...and that's mean your phone already can booting normally..right...?, so where's the problem exactly..?
anyway..if the problem you asked is...why you must always do a flashing boot.img manually after installing any new custom rom to boot normally is bacause you're still had s-on flag on your bootloader..that's why bootloader can't give permission to a custom recovery for flashing boot partition..
if you wanna running RUU...then you should be relocked your bootloader first..and that's mean your will return to the stock..so to rooting it again...you must unlocking your bootloader again..

Everytime, when I flash new rom, I have to flash boot.img. I know that. But problem is when I only restart phone, I need to flash boot.img otherwise phone doesnt start.
Today I find out:
- in clockworkmod I try to make a backup. Everything went great (back up boot image, recovery, system, data, android secure, cache) , but at the end I got a message: "No sd-ext found. Skipping backup of sd-ext."
Before AR rom I had many other roms and backing up and restarting without flashing wors fine.
The last hint which you give me is my last solution. I wouldnt lose my root privileges. I had a lot of trouble to get it..

Pilsner12 said:
Everytime, when I flash new rom, I have to flash boot.img. I know that. But problem is when I only restart phone, I need to flash boot.img otherwise phone doesnt start.
Today I find out:
- in clockworkmod I try to make a backup. Everything went great (back up boot image, recovery, system, data, android secure, cache) , but at the end I got a message: "No sd-ext found. Skipping backup of sd-ext."
Before AR rom I had many other roms and backing up and restarting without flashing wors fine.
The last hint which you give me is my last solution. I wouldnt lose my root privileges. I had a lot of trouble to get it..
Click to expand...
Click to collapse
maybe you can try it to installing and using a different custom recovery..like 4ext or twrp..

I would like to try use another custom recovery, but how I can Unistall cwm ? I didnt find any manual..

Pilsner12 said:
I would like to try use another custom recovery, but how I can Unistall cwm ? I didnt find any manual..
Click to expand...
Click to collapse
you don't need to uninstall it..just flashing a new one (like twrp or 4ext) through fastboot..then cwm will be replaced with that..

JJeamy said:
you don't need to uninstall it..just flashing a new one (like twrp or 4ext) through fastboot..then cwm will be replaced with that..
Click to expand...
Click to collapse
could you please post link, where is .zip file. I found only programs on market or .apk..

Are you booting the boot.img or flashing it? Also, recoveries are not zips, they are imgs.

Pilsner12 said:
could you please post link, where is .zip file. I found only programs on market or .apk..
Click to expand...
Click to collapse
This is a link for 4ext touch recovery here.., extract this zip file first to get recovery.img file
This is a link for TWRP touch recovery here..
just flash this recovery.img file through fastboot.. "fastboot flash recovery the_name_of_recovery.img"

JJeamy said:
This is a link for 4ext touch recovery here.., extract this zip file first to get recovery.img file
This is a link for TWRP touch recovery here..
just flash this recovery.img file through fastboot.. "fastboot flash recovery the_name_of_recovery.img"
Click to expand...
Click to collapse
Thank you for links, recovery is alerady fleshed, but problem is not fixed.
(btw: 4ext looks gorgeous )
here is log:
Starting recovery on Thu Feb 20 20:57:47 2014
framebuffer: fd 3 (480 x 800)
Welcome to 4EXT Recovery Touch
by madmaxx82
Preparing boot.. 0I:start load volumes..
Preparing boot.. 0 Preparing boot.. 0 Preparing boot.. 0I:st.f_bsize: 4096
Preparing boot.. 0 Preparing boot.. 1I:st.f_bsize: 4096
Preparing boot.. 1I:st.f_bsize: 4096
Preparing boot.. 1 Preparing boot.. 1 Preparing boot.. 1I:st.f_bsize: 4096
Preparing boot.. 2recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /recovery emmc /dev/block/mmcblk0p21 (null)
2 /boot emmc /dev/block/mmcblk0p22 (null)
3 /cache ext3 /dev/block/mmcblk0p27 (null)
4 /data ext3 /dev/block/mmcblk0p26 (null)
5 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
6 /system ext4 /dev/block/mmcblk0p25 (null)
7 /system_lib ext3 /dev/block/mmcblk0p28 (null)
I:end load volumes..
I:Completed outputting fstab.
Irocessing arguments.
Preparing boot.. 2I:Checking arguments.
Command: "/sbin/recovery"
ro.build.date=Sat Nov 10 16:53:16 CET 2012
ro.build.date.utc=0
ro.product.model=Desire HD
ro.product.brand=htc_wwe
ro.product.name=htc_ace
ro.product.device=ace
ro.product.board=spade
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=hdpi
ro.product.locale.region=
ro.board.platform=msm7x30
ro.build.product=ace
ro.com.android.dateformat=MM-dd-yyyy
net.bt.name=Android
ro.serialno=SH18KRX02893
ro.baseband=26.14.04.28_M
ro.carrier=HTC-GER
ro.bootloader=2.00.0029
init.svc.choice_fn=stopped
init.svc.offmode_charging=running
init.svc.detect_key=running
init.svc.adbd=running
init.svc.recovery=running
ext.version="1005.8.0"
ext.feature.version_check=yes
ext.build=0
ext.edition=ng
Ireparing..
Preparing boot.. 2Irep sys1: 0
Preparing boot.. 2Ireparing.. fin
Preparing boot.. 2 Configuring settings..
Your configuration settings:
Using button backlights level: 80
Restore: MD5Sum checks: enabled
Backups: generate MD5Sums: enabled
Backups: mode: tar
Backups: exclude /cache: disabled
Backups: exclude dalvik-cache: disabled
Backups: include lib: enabled
Preserve theme: enabled
Hide useless directories: disabled
Haptic feedback: enabled
Haptic feedback strength: 28
Timezone: configured
Using 24h-hour time format
I:theme propok
Recovery is ready..
I:have tz_data
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
Irocessing 4EXT Control file...
4EXT Recovery Updater v2.4.6b
Processing..
Mounting sdcard..
I:Backup path: /sdcard/clockworkmod/backup/2014-02-20-00.05.02_CyanogenMod7.2.0ace
I:Backup mode: custom
Calculating space needed..
Space needed to complete: 654 MiB
Free space on your sdcard: 8264 MiB
Backing up boot image...
Including /system/lib
Backing up system_lib...
backup mode: tar
Backing up system...
Writing 4EXT info for filesystem ext4
Backing up data...
Writing 4EXT info for filesystem ext3
Backing up .android_secure...
Backing up cache...
Writing 4EXT info for filesystem ext3
Generating md5 sums...
tar: removing leading '/' from member names
-- Installing: /sdcard/Download/4EXT_Recovery_Touch_v1.0.0.6_RC1.zip
Finding update package...
I:Update location: /sdcard/Download/4EXT_Recovery_Touch_v1.0.0.6_RC1.zip
Opening update package...
Installing update...
Installation aborted.
Critical error! Installation aborted!
Canceling pending actions and booting UI

Pilsner12 said:
Thank you for links, recovery is alerady fleshed, but problem is not fixed.
(btw: 4ext looks gorgeous )
here is log:
Click to expand...
Click to collapse
what do you mean problem is not fixed..?, is that you mean you can't installing 4ext recovery..?, or problem about installing custom rom..?

JJeamy said:
what do you mean problem is not fixed..?, is that you mean you can't installing 4ext recovery..?, or problem about installing custom rom..?
Click to expand...
Click to collapse
Problem is if I want restart, or Start phone, I have to connect phone to pc, go to fastboot, and via command prompt send to phone boot.img prepared from my custom rom.
Othervise phone didnt start.

Pilsner12 said:
Problem is if I want restart, or Start phone, I have to connect phone to pc, go to fastboot, and via command prompt send to phone boot.img prepared from my custom rom.
Othervise phone didnt start.
Click to expand...
Click to collapse
that's weird thing..i think there's something wrong with your phone partition..
maybe you wanna try it to return your phone to the stock first by running a RUU..to fix that problem...after that
you can tried to fully rooting again for gaining s-off using AAHK2 script by Phiber2000 from here..

JJeamy said:
that's weird thing..i think there's something wrong with your phone partition..
maybe you wanna try it to return your phone to the stock first by running a RUU..to fix that problem...after that
you can tried to fully rooting again for gaining s-off using AAHK2 script by Phiber2000 from here..
Click to expand...
Click to collapse
Thank you for help, and link with this rooting instruction. I will do that in next week, becouse of time and I will let you know how it ends.

Pilsner12 said:
Thank you for help, and link with this rooting instruction. I will do that in next week, becouse of time and I will let you know how it ends.
Click to expand...
Click to collapse
So yesterday I ran RUU and now restart bug is fixed. I am happy for it!
But I have respect from rooting process. Last time it takes me a lot of weeks..

Please help me!!! i'm italian and i don't speak very well english Language
My HTC Desire hd don't start!!!!!!!!
I have CWM TOUCH 5.8.0.0
In starting my HTC Desire HD is blocked in white screen with green logo HTC
When i start RUU....... .exe (much version) the installation fail: error 140
I hope in you!!!!!!!!!
I have too Asus Padfone 2: with FRAMAROOT :good::good::good::good::good:
Please help me for my HTC Desire HD
I append in this post 4 images of my HTC DHD

Bacchione said:
Please help me!!! i'm italian and i don't speak very well english Language
My HTC Desire hd don't start!!!!!!!!
I have CWM TOUCH 5.8.0.0
In starting my HTC Desire HD is blocked in white screen with green logo HTC
When i start RUU....... .exe (much version) the installation fail: error 140
I hope in you!!!!!!!!!
I have too Asus Padfone 2: with FRAMAROOT :good::good::good::good::good:
Please help me for my HTC Desire HD
I append in this post 4 images of my HTC DHD
Click to expand...
Click to collapse
Please help me

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.