Jump to content

Recommended Posts

Guest MestariEetu
Posted

Kyllä tarvii mut ei se oo vaikeet ja kyl täält saa apuu

Juu täytyy kysellä sit kun vihdoin puhelimen sais :(

Guest Phoenix Silver
Posted (edited)

wait and see ;) it's my devise

i have just installed alpha 4 from paul after 2 days of looking for the details :(

but worth it system is running perfectly ;)

so guys take a breath wait for the experts ;) (i'm not one of them just a network administrator)

and merry Christmas (yes it's today hehe)

p.s. : thank you to use search function in forum and google

thank you not to ask for stupids questions like is this need root ; is this need a yellow box for the phone to work ;)

this don't help experts for the development

Edited by Phoenix Silver
Guest rogerpe
Posted

Thank you so much Wellbeing! Looking forward for a fixed version!

Posted (edited)

Is there any kind soul who could turn his this system.tar.gz into a system.img to use as recovery, or tell me how to do it? it may sound stupid, but i have an idea to test on the portuguese "blade" Sapo a5, which is giving tons of problems with all the custom froyos available here, more than the usual problems on orange/other Blades, like having no touch etc.

That problem seemed to have disappeared with the FroyoBlade_0.3.zip (not the testPort one) made from this dump.

Edited by fufax
Guest WellBeing
Posted
Could you confirm that this is from a production (retail) unit? or is it another leaked version?

Thanks for your work!

It is a production unit, economics at 12/24

Guest WellBeing
Posted
好样的哥们 加油 1个小时就从失败走向了成功

是因为有国外大神的帮助,不然也不可能的,呵呵~~

Posted

Well done, waiting for the Modaco custom Froyo, BTW, I find that you are using the "softbank" network service, are you living in Japan now? you buy your blade from softbank?

Guest Master One
Posted (edited)

This is exciting news! Can't wait to see custom 2.2 final ROMs pop up. :(

Edited by Master One
Guest turoscsusxa64
Posted

Could you please check if the wifi sleep issue has been fixed. Thanks.

Guest JBSCARFACE
Posted

Hi m8 can u install clockwork and reset user data, then backup all via clockwork backup option, then zip all files and upload them please?

Guest Sebastian404
Posted
Hi m8 can u install clockwork and reset user data, then backup all via clockwork backup option, then zip all files and upload them please?

Why do you need that?

Guest Sebastian404
Posted

I think I saw it before, but I cant find it now...

anyone got the results of /proc/mtd ? Im interested in how big the OEM partition is..

Guest WellBeing
Posted
Well done, waiting for the Modaco custom Froyo, BTW, I find that you are using the "softbank" network service, are you living in Japan now? you buy your blade from softbank?

Yes, I'm living in japan now, for working。

Buy it from softbank~~

Guest WellBeing
Posted
I think I saw it before, but I cant find it now...

anyone got the results of /proc/mtd ? Im interested in how big the OEM partition is..

I try to get mtd, but faild

# dd if=/dev/block/mtdblock1 of=/sdcard/boot.img

dd if=/dev/block/mtdblock1 of=/sdcard/boot.img

/dev/block/mtdblock1: read error: I/O error

0+0 records in

0+0 records out

0 bytes transferred in 0.001 secs (0 bytes/sec)

# dd if=/dev/block/mtdblock2 of=/sdcard/system.img

dd if=/dev/block/mtdblock2 of=/sdcard/system.img

/dev/block/mtdblock2: read error: I/O error

0+0 records in

0+0 records out

0 bytes transferred in 0.002 secs (0 bytes/sec)

#

Guest Sebastian404
Posted
I try to get mtd, but faild

# dd if=/dev/block/mtdblock1 of=/sdcard/boot.img

dd if=/dev/block/mtdblock1 of=/sdcard/boot.img

/dev/block/mtdblock1: read error: I/O error

0+0 records in

0+0 records out

0 bytes transferred in 0.001 secs (0 bytes/sec)

# dd if=/dev/block/mtdblock2 of=/sdcard/system.img

dd if=/dev/block/mtdblock2 of=/sdcard/system.img

/dev/block/mtdblock2: read error: I/O error

0+0 records in

0+0 records out

0 bytes transferred in 0.002 secs (0 bytes/sec)

#

Ah, sorry, no I ment:

'cat /proc/mtd/'

it will show you what partitions there is on the device

Guest WellBeing
Posted
Ah, sorry, no I ment:

'cat /proc/mtd/'

it will show you what partitions there is on the device

# cat /proc/mtd

cat /proc/mtd

dev: size erasesize name

mtd0: 00500000 00020000 "recovery"

mtd1: 00500000 00020000 "boot"

mtd2: 00180000 00020000 "splash"

mtd3: 00080000 00020000 "misc"

mtd4: 02580000 00020000 "cache"

mtd5: 0dc00000 00020000 "system"

mtd6: 0a280000 00020000 "userdata"

mtd7: 01500000 00020000 "oem"

mtd8: 00180000 00020000 "persist"

Guest WellBeing
Posted
# cat /proc/mtd

cat /proc/mtd

dev: size erasesize name

mtd0: 00500000 00020000 "recovery"

mtd1: 00500000 00020000 "boot"

mtd2: 00180000 00020000 "splash"

mtd3: 00080000 00020000 "misc"

mtd4: 02580000 00020000 "cache"

mtd5: 0dc00000 00020000 "system"

mtd6: 0a280000 00020000 "userdata"

mtd7: 01500000 00020000 "oem"

mtd8: 00180000 00020000 "persist"

I try it yestoday~~

Posted (edited)

sorry

the command is

su

cat /proc/partitions > /sdcard/info.txt

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

cat /dev/mtd/mtd1 > /sdcard/boot.img

cat /dev/mtd/mtd2 > /sdcard/splash.img

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

cat /dev/mtd/mtd4 > /sdcard/cache.img

cat /dev/mtd/mtd5 > /sdcard/system.img

cat /dev/mtd/mtd6 > /sdcard/userdata.img

cat /dev/mtd/mtd7 > /sdcard/oem.img

cat /dev/mtd/mtd8 > /sdcard/persist.img

Edited by godmd5
Posted

Maybe this will be more general:

cat /proc/partitions > /sdcard/info.txt

cat /dev/mtd > /sdcard/mtd.txt

cat /dev/mtd | grep '^mtd' |

while read dev size erasesize label

do

  label=${label#\"*}

  label=${label%\"}

  cat /dev/mtd/${dev%%:} > /sdcard/$label.img

done

I've not tried it on the phone but it seems to work-ish* on busybox on my linux box

* tries to do the right thing

Guest Sebastian404
Posted
sorry

the command is

su

cat /proc/partitions > /sdcard/info.txt

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

cat /dev/mtd/mtd1 > /sdcard/boot.img

cat /dev/mtd/mtd2 > /sdcard/splash.img

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

cat /dev/mtd/mtd4 > /sdcard/cache.img

cat /dev/mtd/mtd5 > /sdcard/system.img

cat /dev/mtd/mtd6 > /sdcard/userdata.img

cat /dev/mtd/mtd7 > /sdcard/oem.img

cat /dev/mtd/mtd8 > /sdcard/persist.img

Erm, you do know this device has already been dumped?

Guest Sebastian404
Posted

Thanks for that, it helped me a little....

can I ask another question?

can you do a 'uname -a' and see what you get back?

you might need to do 'busybox uname -a' if the first one will not work.

Thanks

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.