107 replies to this topic

[rjm2k]

Has anyone dumped the config for this device?

If not please post /proc/config.gz somewhere .

thanks

[flibblesan]

Ok I've been looking at this dump over the last few days and honestly I don't see it being as useful as the current Chinese ROM. The very fact that the kernel is incompatible with our phones means that any advantage of the newer rom is lost to us. Also the Phone.apk needs patching to remove the annoying "Call to Japan" alert and tethering has been disabled from Settings.apk. Oh and apparently no support for phone unlocking?

Since the current roms based on this are using the kernel, apks and fixes from the Chinese ROM... why not use the Chinese ROM? Really there isn't any benefit using the Japanese ROM unless the kernel can be made to work on our phones.

[kallt_kaffe]

rjm2k, on Dec 28 2010, 12:00, said:

Has anyone dumped the config for this device?

If not please post /proc/config.gz somewhere .

thanks

oldkernel_config.txt is the config from the beta kernel from the 2nd of September.
newkernel_config.txt is from the non-booting kernel in this dump.

Attached Files

•  newkernel_config.txt   51.65K   52 downloads
•  oldkernel_config.txt   51.53K   33 downloads

[hecatae]

could I use what wellbeing uploaded with the hungarian total phone transfer update method?

StevenHarperUK, on Dec 28 2010, 15:01, said:

I wounder if we can remove the bits of the update we don't wan't to happen and just apply the Memory Fixing part - and not flash the Recovery etc...

-rw-r--r--  1 steven steven		40 2010-12-08 00:05 amsshd.mbn
-rw-r--r--  1 steven steven  19484672 2010-12-08 00:05 amss.mbn
-rw-r--r--  1 steven steven		40 2010-12-14 17:59 appsboothd.mbn
-rw-r--r--  1 steven steven	 44220 2010-12-14 17:59 appsboot.mbn
-rw-r--r--  1 steven steven   2516992 2009-01-01 00:00 boot.img
-rw-r--r--  1 steven steven	577536 2010-05-05 15:12 cefs.mbn
-rw-r--r--  1 steven steven		40 2010-12-08 00:05 oemsblhd.mbn
-rw-r--r--  1 steven steven	435444 2010-12-08 00:05 oemsbl.mbn
-rw-r--r--  1 steven steven	   464 2010-12-08 00:05 partition.mbn
-rw-r--r--  1 steven steven	   252 2010-12-14 17:59 partition_zte.mbn
-rw-r--r--  1 steven steven	 11412 2010-12-08 00:05 qcsblhd_cfgdata.mbn
-rw-r--r--  1 steven steven	 57328 2010-12-08 00:05 qcsbl.mbn
-rw-r--r--  1 steven steven   2891776 2009-01-01 00:00 recovery.img
-rw-r--r--  1 steven steven	770048 2010-12-08 00:41 splash.img
-rw-r--r--  1 steven steven 139780608 2009-01-01 00:00 system.img

I wounder if we reduce the ZIP to JUST the files needed to fix the memory problem - is there any way of finding out which ones we need

and if it will work with some missing.

so if I replace boot.img recovery.img and system.img, could it boot?

Edited by hecatae, 03 January 2011 - 02:59 PM.

[hecatae]

using TPT fails at writing boot.img 90%

off to find a hex editor

softbank

# 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"

Edited by hecatae, 03 January 2011 - 06:43 PM.

[hecatae]

kallt_kaffe, on Dec 29 2010, 10:50, said:

oldkernel_config.txt is the config from the beta kernel from the 2nd of September.
newkernel_config.txt is from the non-booting kernel in this dump.

Quote

diff oldkernel_config.txt newkernel_config.txt
4c4
< # Thu Sep  2 15:51:21 2010
---
> # Fri Dec 10 17:34:12 2010
221c221
< CONFIG_PHYS_OFFSET=0x02A00000
---
> CONFIG_PHYS_OFFSET=0x02600000
734a735
> # CONFIG_BT_MSM_BCM is not set
874c875
< # CONFIG_UID_STAT is not set
---
> CONFIG_UID_STAT=y
979a981
> # CONFIG_DHD is not set
1251,1252c1253,1254
< # CONFIG_MT9T11X_QTECH_MCNEX_SOCKET is not set
< # CONFIG_OV5642 is not set
---
> CONFIG_OV5642=y
> CONFIG_OV5642_GLOBALOPTICS=y
1253a1256
> # CONFIG_MT9D113 is not set
1257c1260
< # CONFIG_SENSOR_ADAPTER is not set
---
> CONFIG_SENSOR_ADAPTER=y
1500a1504
> # CONFIG_WIFI_AR6003 is not set
1532c1536,1537
< # CONFIG_LEDS_GPIO is not set
---
> CONFIG_LEDS_GPIO=y
> CONFIG_LEDS_GPIO_PLATFORM=y
1550a1556
> # CONFIG_ZTE_FIX_ALARM_SYNC is not set

not much difference then

[fineking]

Hello, WellBeing

I'm glad you get the SoftBank 003Z's ROM.

I am also chinese and also live in Japan.

I had the softbank 003Z. I want to install Clockwork Recovery, but failed.
http://android.modac...p...t&p=1575418


Can you tell me How to Install Clockwork Recovery on SoftBank 003Z ?

By the way, How to use Fastboot method on SoftBank 003Z ?
(I tested by holding volume up + power, but it seems SoftBank 0003Z can not use this Fastboot method)

Thank you very much.

[oh!dougal]

fineking, on Jan 25 2011, 03:44, said:

...

I am also chinese and also live in Japan.

I had the softbank 003Z. I want to install Clockwork Recovery, but failed.
http://android.modac...p...t&p=1575418
Can you tell me How to Install Clockwork Recovery on SoftBank 003Z ?

By the way, How to use Fastboot method on SoftBank 003Z ?
(I tested by holding volume up + power, but it seems SoftBank 0003Z can not use this Fastboot method)

STOP FOR A MOMENT !

Be very careful !
The 003Z (and V880) is very similar to, but not the same as, the Blade (or each other).

A kernel for a standard Blade (as in Blade versions of Clockwork) would not run on a standard 003Z.


I would suggest that your best route forward would be to look at the Chinese forums on the V880.
It would be difficult for the Developers here to do anything much for the Japanese and Chinese phones without having the phone to work with.