AMON HAS MADE US A NEW RECOVERY THAT FIXES THE BAD PARTITIONS IN RECOVERY - &postcount=27
THANKS AMON (everyone buy that guy a redbull)
Zikronix has updated his step by step tutorial on how to use this. - ?t=829045
Info below just for historical purposes
-----------------------------------------
My old evo died so zikronix and i have been messing around all day trying to get a new 003 evo with 2.02 hboot on it rooted.
What we have determined is that once you flash recovery partition and partitions get mounted in recovery half of the space disappears. It does not matter what recovery partition you are using (tried amons, clockwork, even the eng recovery part). We have tried a variety of different combos of boot.img and such.
This is what we are seeing:
before recovery flashed with 2.02 003 hardware
Code:
# busybox df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 212408 0 212408 0% /dev
tmpfs 212408 0 212408 0% /mnt/asec
/dev/block/mtdblock4 358400 272388 86012 76% /system
/dev/block/mtdblock6 436224 46208 390016 11% /data
/dev/block/mtdblock5 163840 2312 161528 1% /cache
tmpfs 8192 8192 0 100% /app-cache
after flashed eng recovery, pushed recovery files manually and did a mount -a (this is the same using any recovery)
Code:
# df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 202060 0 202060 0% /dev
/dev/block/mtdblock5 81920 1296 80624 2% /cache
/dev/block/mtdblock6 218112 12812 205300 6% /data
/dev/block/mtdblock4 179200 100608 78592 56% /system
/dev/block/mmcblk0p1 7753728 674112 7079616 9% /sdcard
============================================
Even /proc/partitions sees them as wrong. - on a working 003 2.02 hboot this shows:
Code:
cat /proc/partitions
major minor #blocks name
31 0 12288 mtdblock0
31 1 1024 mtdblock1
31 2 4608 mtdblock2
31 3 3328 mtdblock3
31 4 358400 mtdblock4
31 5 163840 mtdblock5
31 6 436224 mtdblock6
In recovery:
Code:
cat /proc/partitions
major minor #blocks name
31 0 6144 mtdblock0
31 1 512 mtdblock1
31 2 2304 mtdblock2
31 3 1664 mtdblock3
31 4 179200 mtdblock4
31 5 81920 mtdblock5
31 6 218112 mtdblock6
==============================================
/proc/mtd from 003 hboot 2.02 not in recovery:
Code:
dev: size erasesize name
mtd0: 00c00000 00040000 "wimax"
mtd1: 00100000 00040000 "misc"
mtd2: 00480000 00040000 "recovery"
mtd3: 00340000 00040000 "boot"
mtd4: 15e00000 00040000 "system"
mtd5: 0a000000 00040000 "cache"
mtd6: 1aa00000 00040000 "userdata"
==========================================
MTD layout on 2.02 hboot with 003 hardware from my post - &postcount=10
Code:
<5>[ 5.696319] Creating 7 MTD partitions on "msm_nand":
<5>[ 5.696411] 0x00003f300000-0x00003ff00000 : "wimax"
<5>[ 5.705780] 0x00003ff00000-0x000040000000 : "misc"
<5>[ 5.707000] 0x000004340000-0x0000047c0000 : "recovery"
<5>[ 5.710510] 0x0000047c0000-0x000004b00000 : "boot"
<5>[ 5.713043] 0x000004b00000-0x00001a900000 : "system"
<5>[ 5.951934] 0x00001a900000-0x000024900000 : "cache"
MTD layout on 0.76 hboot with older 003 hardware from zikronix post - &postcount=12
Code:
<5>[ 3.319244] Creating 7 MTD partitions on "msm_nand":
<5>[ 3.319366] 0x00003f360000-0x00003ff60000 : "wimax"
<5>[ 3.333801] 0x00003ff60000-0x000040000000 : "misc"
<5>[ 3.334991] 0x000004240000-0x000004740000 : "recovery"
<5>[ 3.341033] 0x000004740000-0x0000049c0000 : "boot"
<5>[ 3.344421] 0x0000049c0000-0x00001a7c0000 : "system"
<5>[ 3.852111] 0x00001a7c0000-0x0000247c0000 : "cache"
<5>[ 4.036437] 0x0000247c0000-0x00003f360000 : "userdata"
My best guess is offsets changed which is why we are seeing the missing space and failed flashes in recovery. Any recovery image gurus out there?
reserved....
reserved....
bump for the night krew
When I flash via recovery everything completes but when it boots it hangs on the HTC logo screen.
Is this why when I flash it hangs?
Sent from my PC36100 using XDA App
what does 'cat /proc/mtd' show?
I never cat will do in a little while. Should I flash and when it hangs on the HTC logo do I run the cat to get the info?
Sent from my PC36100 using XDA App
you can try there or while in the recover
Sent from my PC36100 using XDA App
Ok I'll let you guys know.
Sent from my PC36100 using XDA App
Devs - Could it be possible that somehow the partitions need to be changed in recovery.img? I found the following:
http://forum.xda-developers.com/showthread.php?t=704560
Looks like boot.img and recovery.img both can have offsets/partition sizes set by specifying addition kernel parms when its made with mkbootimg. Is it possible whatever the "default" recovery.img structure is borked somehow with this hardware?
If this helps, this seems to be the MTD layout from a working boot on 2.02 on 003:
<5>[ 5.696319] Creating 7 MTD partitions on "msm_nand":
<5>[ 5.696411] 0x00003f300000-0x00003ff00000 : "wimax"
<5>[ 5.705780] 0x00003ff00000-0x000040000000 : "misc"
<5>[ 5.707000] 0x000004340000-0x0000047c0000 : "recovery"
<5>[ 5.710510] 0x0000047c0000-0x000004b00000 : "boot"
<5>[ 5.713043] 0x000004b00000-0x00001a900000 : "system"
<5>[ 5.951934] 0x00001a900000-0x000024900000 : "cache"
xHausx said:
you can try there or while in the recover
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
This is what I got while in recovery before I flashed
dev: size erasesize name
mtd0: 00600000 00020000 "wimax"
mtd1: 00080000 00020000 "misc"
mtd2: 00240000 00020000 "recovery"
mtd3: 001a0000 00020000 "boot"
mtd4: 0af00000 00020000 "system"
mtd5: 05000000 00020000 "cache"
mtd6: 0d500000 00020000 "userdata"
working values on an older 003 evo with 076.2000
<5>[ 3.319244] Creating 7 MTD partitions on "msm_nand":
<5>[ 3.319366] 0x00003f360000-0x00003ff60000 : "wimax"
<5>[ 3.333801] 0x00003ff60000-0x000040000000 : "misc"
<5>[ 3.334991] 0x000004240000-0x000004740000 : "recovery"
<5>[ 3.341033] 0x000004740000-0x0000049c0000 : "boot"
<5>[ 3.344421] 0x0000049c0000-0x00001a7c0000 : "system"
<5>[ 3.852111] 0x00001a7c0000-0x0000247c0000 : "cache"
<5>[ 4.036437] 0x0000247c0000-0x00003f360000 : "userdata"
sorry took so long dmesg was all over the place lol
device said i was offline and online at the same time....****ing nexus of the universe.
TrevE are you sure those mtd values are correct? I was expecting something along the lines of:
dev: size erasesize name
mtd0: 00c00000 00020000 "wimax"
mtd1: 000a0000 00020000 "misc"
mtd2: 00500000 00020000 "recovery"
mtd3: 00280000 00020000 "boot"
mtd4: 15e00000 00020000 "system"
mtd5: 0a000000 00020000 "cache"
mtd6: 1aba0000 00020000 "userdata"
I believe most evo roms have a boot.img offset of 20000, I could ber mistaken though
Sent from my PC36100 using XDA App
xHausx said:
TrevE are you sure those mtd values are correct? I was expecting something along the lines of:
dev: size erasesize name
mtd0: 00c00000 00020000 "wimax"
mtd1: 000a0000 00020000 "misc"
mtd2: 00500000 00020000 "recovery"
mtd3: 00280000 00020000 "boot"
mtd4: 15e00000 00020000 "system"
mtd5: 0a000000 00020000 "cache"
mtd6: 1aba0000 00020000 "userdata"
I believe most evo roms have a boot.img offset of 20000, I could ber mistaken though
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
yes i just ran it again. This is on my new 003 phone with 2.02 hboot and s-off.
Code:
$ cat /proc/mtd
cat /proc/mtd
dev: size erasesize name
mtd0: 00c00000 00040000 "wimax"
mtd1: 00100000 00040000 "misc"
mtd2: 00480000 00040000 "recovery"
mtd3: 00340000 00040000 "boot"
mtd4: 15e00000 00040000 "system"
mtd5: 0a000000 00040000 "cache"
mtd6: 1aa00000 00040000 "userdata"
im guessing this and the MTD offsets being different is part of the reason we only see half of the space in recovery leading to nothing flashing properly
chubbzlou said:
When I flash via recovery everything completes but when it boots it hangs on the HTC logo screen.
Is this why when I flash it hangs?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
What does your bootloader look like? Can you tell us what the top 3 or 4 lines say
Sent from my PC36100 using XDA App
I have a white evo with hardware 0003 and hboot 2.02.
I initially rooted with http://forum.xda-developers.com/showthread.php?t=838448
The part where it flashes the recovery image never succeeds it and I come up with the stock recovery screen. What's interesting is that if I run the recovery-windows.bat from http://link.geekfor.me/evorecovery while in the stock recovery, it actually loads a working recovery image, allowing me to flash roms and everything else. It doesn't keep though, and upon reboot I lose that recovery. Whatever I flash to sticks, though.
cat /proc/partitionsajor minor #blocks name
7 0 16664 loop0
31 0 12288 mtdblock0
31 1 640 mtdblock1
31 2 4608 mtdblock2
31 3 3072 mtdblock3
31 4 358400 mtdblock4
31 5 163840 mtdblock5
31 6 437888 mtdblock6
179 0 7761920 mmcblk0
179 1 6261718 mmcblk0p1
179 2 1000000 mmcblk0p2
179 3 500201 mmcblk0p3
254 0 16663 dm-0
cat /proc/mtdev: size erasesize name
mtd0: 00c00000 00020000 "wimax"
mtd1: 000a0000 00020000 "misc"
mtd2: 00480000 00020000 "recovery"
mtd3: 00300000 00020000 "boot"
mtd4: 15e00000 00020000 "system"
mtd5: 0a000000 00020000 "cache"
mtd6: 1aba0000 00020000 "userdata"
Here is what I show, for what it's worth. Hardware version 003, Rooted, s-off, 2.02 hboot. This is while os is up. I can run it from recovery in the am if you like. I have had no problems flashing roms, though.
Sent from my HTC SuperSonic 4G using the XDA app.
xHausx said:
What does your bootloader look like? Can you tell us what the top 3 or 4 lines say
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
supersonic evt2-3 ship s-off
hboot-2.02.0000
microp-041f
touch panel-atmelc03_16ac
radio-2.15.00.09.01
Oct 14 2010,19:14:47
TrevE
I was curious and I ran cat /proc/mtd in recovery and not in recovery
cat /proc/mtd not in recovery
dev: size erasesize name
mtd0: 00c00000 00040000 "wimax"
mtd1: 00100000 00040000 "misc"
mtd2: 00480000 00040000 "recovery"
mtd3: 00340000 00040000 "boot"
mtd4: 15e00000 00040000 "system"
mtd5: 0a000000 00040000 "cache"
mtd6: 1aa00000 00040000 "userdata"
cat /proc/mtd in recovery
mtd0: 00600000 00020000 "wimax"
mtd1: 00080000 00020000 "misc"
mtd2: 00240000 00020000 "recovery"
mtd3: 001a0000 00020000 "boot"
mtd4: 0af00000 00020000 "system"
mtd5: 05000000 00020000 "cache"
mtd6: 0d500000 00020000 "userdata"
Don't know why it would be different.
chubbzlou said:
TrevE
I was curious and I ran cat /proc/mtd in recovery and not in recovery
cat /proc/mtd not in recovery
dev: size erasesize name
mtd0: 00c00000 00040000 "wimax"
mtd1: 00100000 00040000 "misc"
mtd2: 00480000 00040000 "recovery"
mtd3: 00340000 00040000 "boot"
mtd4: 15e00000 00040000 "system"
mtd5: 0a000000 00040000 "cache"
mtd6: 1aa00000 00040000 "userdata"
cat /proc/mtd in recovery
mtd0: 00600000 00020000 "wimax"
mtd1: 00080000 00020000 "misc"
mtd2: 00240000 00020000 "recovery"
mtd3: 001a0000 00020000 "boot"
mtd4: 0af00000 00020000 "system"
mtd5: 05000000 00020000 "cache"
mtd6: 0d500000 00020000 "userdata"
Don't know why it would be different.
Click to expand...
Click to collapse
Ok. Starting to make sense now. It looks like they are using different partition tables
Sent from my PC36100 using XDA App
edit: meant block sizes not partition tables
Related
Hi,
I'm working on modding a cheap Android-based MediaPlayer.
I already got root-access and dumped the partitions with "cat /dev/mtd/mtdx".
Here is the partition table("cat /proc/mtd"):
dev: size erasesize name
mtd0: 00020000 00020000 "block0"
mtd1: 00100000 00020000 "bootloader"
mtd2: 01900000 00020000 "bootimgs"
mtd3: 01900000 00020000 "bootimgs-B"
mtd4: 00080000 00020000 "u-boot.env"
mtd5: 0c000000 00020000 "system"
mtd6: 08000000 00020000 "userdata"
mtd7: 06800000 00020000 "cache"
mtd8: 00400000 00020000 "factory_setting"
mtd9: 00400000 00020000 "factory_data"
mtd10: 01000000 00020000 "sysconf"
mtd11: 20000000 00020000 "mv_nand"
Click to expand...
Click to collapse
As you can see this system has a very different partition-organisation.
I dumped bootloader but I can't find a way to open/extract it.
I tried unyaffs but it doesn't work.
I already tried to do the same with the partitions cache, data and system.
Because they are mounted as yaffs2 in the system I thought it should work. But it does not. unyaffs say "broken image file" or "Memory Access Error".
I don't know if this will help but I uploaded the bootloader-Backup:
http://www.multiupload.com/QY9RV46GQZ
My purpose is to get access to the bootloader so I could install CWM (as you can see there is no recovery-partition).
I really hope that anyone of you experts can help me.
m11kkaa
Hi, I found out, that MTD-partitions are no block-devices and that they need transition-layer. /dev/block/mtdblockx is an emulated block-device.
Can I do the same under Ubuntu with an image-file instead of a real block device?
Hello to all...
I try to flash custom recovery in my LG P500 but every time I get error message and my phone becomes a brick!
I follow every single instruction here but when I type
Code:
flash_image recovery /sdcard/recovery.img
I get the error
Code:
mtd: not writing bad block at 0x00440000
error writing recovery : No space left on device
I get the same error with every method about flashing custom recovery and after reboot I get in fastboot mode.
I don't know if this helps but with the next command I get the results
Code:
>adb shell cat /proc/mtd
dev: size erasesize name
mtd0: 00440000 00020000 "boot"
mtd1: 0be00000 00020000 "system"
mtd2: 00500000 00020000 "recovery"
mtd3: 002c0000 00020000 "lgdrm"
mtd4: 00100000 00020000 "splash"
mtd5: 00180000 00020000 "FOTABIN"
mtd6: 005c0000 00020000 "FOTA"
mtd7: 00040000 00020000 "misc"
mtd8: 04000000 00020000 "cache"
mtd9: 0c780000 00020000 "userdata"
Thank you in advance for every help!
Hi...guys.......I m in serious problem to root my device.....that is local branded as Symphony W5.and it is clone device of Micromax A52 and Gionee gn100..but without 3g..I tried a52 root method but didn't work...it gives eboot error 16008...that means the problem is in scatter.I made a scatter file via MT65xx rom dump..but it also didn't work.....I tried all the known rooting software but no success!!! What should I do now????? This is what I got after "cat proc/mtd" on terminal emulator--------------------------------------------------------------------- $ export PATH=/data/local/bin:$PATH
$ cat proc/mtd
dev: size erasesize name
mtd0: 00080000 00040000 "preloader"
mtd1: 00180000 00040000 "dsp_bl"
mtd2: 00300000 00040000 "nvram"
mtd3: 00040000 00040000 "seccnfg"
mtd4: 00080000 00040000 "uboot"
mtd5: 00a00000 00040000 "boot"
mtd6: 00600000 00040000 "recovery"
mtd7: 00140000 00040000 "secstatic"
mtd8: 00080000 00040000 "misc"
mtd9: 00300000 00040000 "logo"
mtd10: 000c0000 00040000 "expdb"
mtd11: 00400000 00040000 "gionee"
mtd12: 10400000 00040000 "system"
mtd13: 03c00000 00040000 "cache"
mtd14: 08c40000 00040000 "userdata"
$.........
Did you rooted your phone....
Sent from my A52 using xda app-developers app
My wifes phone has been rooted through the poot method. However it is now time to install CWM. And none have been created yet for this version. Can someone point me in the right direction. Here are my mounts. I can dump the mounts as needed.
$ su # cat /proc/mtd dev: size erasesize name mtd0: 00500000 00020000 "boot" mtd1: 00500000 00020000 "recovery" mtd2: 00140000 00020000 "misc" mtd3: 00240000 00020000 "MTD-Crash" mtd4: 0ba00000 00020000 "system" mtd5: 03a00000 00020000 "cache" mtd6: 0a500000 00020000 "userdata" mtd7: 01400000 00020000 "userdata2" mtd8: 01400000 00020000 "cust" mtd9: 00140000 00020000 "MIBIB" mtd10: 00060000 00020000 "QCSBL" mtd11: 00800000 00020000 "OEMINFO" mtd12: 001a0000 00020000 "OEMSBL1" mtd13: 001a0000 00020000 "OEMSBL2" mtd14: 01e00000 00020000 "AMSS" mtd15: 00600000 00020000 "EFS2" mtd16: 00060000 00020000 "APPSBL" mtd17: 00040000 00020000 "FOTA" # cat /dev/mtd/mtd1 > sdcard/recovery.img
Sent from my LGL55C using Tapatalk 2
I second that motion. I would like to CWM Recovery on this phone.
I will third that.
Will this somehow work with the P500?
https://github.com/Firerat/CustomMTD/
I've used it on an HTC Legend before. Since most Android devices are mtd based...
However, the mtd layout on the P500 have the system partition sandwiched between boot and recovery:
(is this correct? Not from my device but found it on the forum, I've converted the hex "size" value to decimal)
Code:
dev: size erasesize name
mtd0: 4456448 00020000 "boot" = 4.25MB
mtd1: 199229440 00020000 "system" = 190 MB
mtd2: 5242880 00020000 "recovery" = 5MB
mtd3: 2883584 00020000 "lgdrm" = 2.75MB
mtd4: 1048576 00020000 "splash" = 1MB
mtd5: 1572864 00020000 "FOTABIN" = 1.5MB
mtd6: 6029312 00020000 "FOTA" = 5.75MB
mtd7: 262144 00020000 "misc" = 0.25MB
mtd8: 67108864 00020000 "cache" = 64MB
mtd9: 209190912 00020000 "userdata" = 199.5MB
In the latest CM11 from androidarmv6, system and userdata was swapped to gain 9.5MB along with the updated recovery.
Will AutoMTD be able to patch androidarmv6.org CWM? Resizing system/mtdblock2 would be impossible, but swapping and/or merging cache/mtdblock8 with mtdblock9 will be possible for a mere 60MB or so max
And then /cache can by symlinked to /data or to the sdcard?
Worth the trouble?