Database Info

Reflashing the EEPROM

Hello all...
as in these threads for the Hermes:
http://forum.xda-developers.com/showthread.php?t=322225
and
http://forum.xda-developers.com/showthread.php?t=296936
and
http://forum.xda-developers.com/showthread.php?t=299451
I seemed to have screwed up my EEPROM while flashing to WM6 via HardSPL, the problem is that there was a power outage halfway through the process and now ANY ROM that I flash it to there is NO WIFI... It is there, it just won't work.
I have read that this is due to my EEPROM being screwed up due to bad flashing. Before I say that the MoBo is fried, I would like to try to reflash the EEPROM part
I have tried to mmty and putty and plink while no commands are able to be registered on the s200.
Could anyone with some expertise assist me in rewriting my EEPROM (I have the SPL from a 2.20 official ROM) - I assume that I need to write it back via putty, but I cannot seem to send commands to the device!
PLEASE HELP!
Thanks in advance for any assistance in this matter.

same here...i tried but cant get the commands to work like you...pls let me know if you find a solution.

Off course it will not work, different doc and different addresses
It is your cid block at n1, not the SPL, please use pdocread.exe like this
Pdocread.exe -n 0 0 0xaf0000 spl.nb
pdocread -n 1 0 0x40000 cidblock.bin
pdocread -n 1 0x40000 0x4000 -b 0x4000 gsmdata.bin
compress the files using 7-zip ultra compression and send them to my mail
I'll try to help
or the MAC adress can be found @ offset 3e5c in gsmdata.bin
long live Palestine

Jeff said:
I seemed to have screwed up my EEPROM while flashing to WM6 via HardSPL,
Click to expand...
Click to collapse
I think it is not hard SPL
Code:
hard spl G3
99DCC: 00 0D
99DCE: A0 00
99DCF: E1 1A
99DEC: 00 13
99DEE: A0 00
99DEF: E1 0A
99DFC: 00 0F
99DFE: A0 00
99DFF: E1 1A
99FCC: 00 0D
99FCE: A0 00
99FCF: E1 1A
99FEC: 00 13
99FEE: A0 00
99FEF: E1 0A
99FFC: 00 0F
99FFE: A0 00
99FFF: E1 1A
paradis_pal

Chopin,
Mail sent as requested... Thank you IMMENSELY for your attention and assistance.
Pdocread.exe -n 0 0 0xaf0000 spl.nb returns this error:
"ERROR: ITReadDisk : read 00008000 bytes - A device attached to the system is not functioning."
However the other two were successful...
Is this because the SPL is bugged?

I sent you mail back
Again it is not the SPL, sorry the command I wrote was wrong
Pdocread.exe -n 0 0 0x1f0000 spl.nb
Waiting your test, and there is no risk as you have a backup

pdocread -n 1 0x40000 0x4000 -b 0x4000 gsmdata.bin
and send the file again
and tell me what is the size of the pdocread and pdocwrite
use the new itsutils tools
and what do u have g3 or g4?

Just to add my $0.02... this thread has helped me somewhat with my Kaiser and @chopin: http://youtube.com/watch?v=MZTGYxVGzQg

seattleweb said:
Just to add my $0.02... this thread has helped me somewhat with my Kaiser and @chopin: http://youtube.com/watch?v=MZTGYxVGzQg
Click to expand...
Click to collapse
youtube is forbbiden in Syria, what is this?
@Jeff
I checked your cidblock.bin and it is correct
but gsmdata.bin is corrupted, try to flash it again

YouTube Link
It is
Arvo Pärt: Silouans Song / Vienna Philharmonic Women

A NEW message now!
"pdocwrite -n 1 -b 0x4000 gsmdata.bin 0x40000 0x4000
CopyFileToTFFS(gsmdata.bin:0, 40000, 00004000)
ERROR: ITWriteDisk - The drive cannot locate a specific area or track on the disk."
This is with the newer versions of Pdocwrite with the GOOD GSMData...
I am lost at this point...

pdocwrite -n 1 gsmdata.bin 0x40000 0x4000

The Mystery thickens...
With the 104K Pdocwrite I get:
CopyFileToTFFS(gsmdata.bin:0, 40000, 00004000)
ERROR: could not read 0x0 bytes of preceeding sector data at 0x40000
With the 140K Pdocwrite I get:
CopyFileToTFFS(gsmdata.bin:0, 40000, 00004000)
ERROR: ITReadDisk : read 00004000 bytes - Data error (cyclic redundancy check).

wrong information for me, no one rea this please

You have mail!

Chopin said:
Off course it will not work, different doc and different addresses
It is your cid block at n1, not the SPL, please use pdocread.exe like this
Pdocread.exe -n 0 0 0xaf0000 spl.nb
pdocread -n 1 0 0x40000 cidblock.bin
pdocread -n 1 0x40000 0x4000 -b 0x4000 gsmdata.bin
compress the files using 7-zip ultra compression and send them to my mail
I'll try to help
or the MAC adress can be found @ offset 3e5c in gsmdata.bin
long live Palestine
Click to expand...
Click to collapse
Glad u back from silence...
Nice to see u here

Jeff said:
You have mail!
Click to expand...
Click to collapse
Now I need help
Why in the new itsutils tools the gsm data @ offset 0x10000 with block size 0x4000
In the old one @offset 0x40000 with the same block size?
Is it a joke?
@jeff
But first back up GSM data and send it to my mail
Use the updated change MAC address tool it works now, to restore and write GSM data

kram3r said:
Glad u back from silence...
Nice to see u here
Click to expand...
Click to collapse
thanks my other man
nice to have some people like me, becasue a lot hate me

IT WORKED!
I WORKED!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
I now have Wifi Back on my Prophet!!!!
All hail Chopin for his concern for the welfare of others, many should make him an example!
Dude, I owe you some virtual beer or something...
I am indebted to you, thank you from the bottom of my heart.
"You shouldn't worry about what some think of you, what you think of yourself is more important." - Jeff

you are welcome
just say please if you like me, Long live Palestine

[UTIL][ALL][MT65XX] Partitions Resizer

Hi every one.
Only for rooted MT65XX phones, tested with MT6592, MT6589 and MT6582.
In Mediatek phones, the total storage space is shared between the ANDROID (/system), CACHE, DATA (on witch apps will be installed) and FAT (Phone Storage, like an internal SDCARD)
With this tool you can decide witch space to give to eatch part, by resizing any of those 4 partitions.
It is useful if you have already an external SDCARD and you do not need the Phone Storage, so with this program, you can give the DATA the max of space.
0- Do a full backup of your rom in the recovery (important!)
1- Do a backup with MtkDroidTools and create, always with MtkDroidTools, the files for SPFlashTool.
2- With this program, open the scatter freshly created in step 1, resize as you want, and apply changes. (to avoid resizing the partitions you do not want to resize, disable their resize using the small colored buttons)
The new scatter will be created in the same folder than the original as 'MT65XX_Android_Scatter_MOD.txt'
3- Do a "firmware upgrade" with SPFlashTool and the new modded scatter
4- Enter the recovery and do a full restore.
It is a Java program (jar file) so you can execute it under any OS, with java installed : www.java.com
the sources are in the jar file, or here : https://code.google.com/p/jmtkdataresizer
ChangeLog:
=========
- V1.0 : first version, only data/fat resizer
- V2.0 : can resize the 4 partitions ANDROID/CACHE/DATA/FAT, and add the possibilty to disable resize for some partitions (the small colored buttons)
- V2.1 : some cosmetic and minor changes
- V2.2 : can now accept scatters without FAT size information (in this case, only other partitions can be resized)
- V2.3 : add the ability to use firmware.info if present, if not it will ask for the FAT partition size, if the scatter does not contains this info : thank you iZLeeP
- V2.31: can handle now scatter without FAT partition.
- V2.32: correct a bug with some firmware.info files
Tips:
1- the file firmware.info is created by MtkDroidTools while backuping, copy it in the same directory than the scatter or its parent, it will be detected and used if needed.
2- if you want to be sur that the new modded scatter is correct, open it with this program and try to resize : if the apply button is enabled --> OK (do not apply, just a test)
Enjoy

dreambo said:
Hi every one.
Only for rooted MT65XX phones, tested with MT6592, MT6589 and MT6582.
In Mediatek phones, the total storage space is shared with the DATA (on witch apps will be installed) and FAT (Phone Storage, like an internal SDCARD)
With this is a tool you can decide witch space to give to eatch part, by resizing the DATA/FAT partitions.
It is useful if you have already an external SDCARD and you do not need the Phone Storage, so with this program, you can give the DATA the max of space.
1- First do a backup with MtkDroidTools and create, always with MtkDroidTools, the files for SPFlashTool.
2- With this program, open the scatter freshly created in step 1, resize as you want, and apply changes.
The new scatter will be created in the same folder than the original as 'MT65XX_Android_Scatter_MOD.txt'
3- Flash it with SPFlashTools (firmware update) and enjoy.
It is a Java program (jar file) so you can execute it under any OS, with java installed : www.java.com
Click to expand...
Click to collapse
Hi awesome tool!
Thanks but can you share/make a system partitioner tool, I can resize my "SYSTEM" partition. It's 890 Mb I want it around 1.4 Gb

Tech N You said:
Hi awesome tool!
Thanks but can you share/make a system partitioner tool, I can resize my "SYSTEM" partition. It's 890 Mb I want it around 1.4 Gb
Click to expand...
Click to collapse
A good idea
Il will add that in the future version.
The cache partition must be touched too!
It will be so ANDROID/CACHE/DATA/FAT resizer (ANDROID= /system) it will be complicated.
It will be my next goal.
Thank you for your interest

dreambo said:
A good idea
Il will add that in the future version.
The cache partition must be touched too!
It will be so ANDROID/CACHE/DATA/FAT resizer (ANDROID= /system) it will be complicated.
It will be my next goal.
Thank you for your interest
Click to expand...
Click to collapse
Awesome will be waiting :laugh::good:

dreambo said:
Hi every one.
Only for rooted MT65XX phones, tested with MT6592, MT6589 and MT6582.
In Mediatek phones, the total storage space is shared between the DATA (on witch apps will be installed) and FAT (Phone Storage, like an internal SDCARD)
With this tool you can decide witch space to give to eatch part, by resizing the DATA/FAT partitions.
It is useful if you have already an external SDCARD and you do not need the Phone Storage, so with this program, you can give the DATA the max of space.
1- First do a backup with MtkDroidTools and create, always with MtkDroidTools, the files for SPFlashTool.
2- With this program, open the scatter freshly created in step 1, resize as you want, and apply changes.
The new scatter will be created in the same folder than the original as 'MT65XX_Android_Scatter_MOD.txt'
3- Flash it with SPFlashTools (firmware update) and enjoy.
It is a Java program (jar file) so you can execute it under any OS, with java installed : www.java.com
Click to expand...
Click to collapse
@dreambo any update on system partitioner increaser?

For this WE max, sure.
Sent from my 709v92_jbla828 using XDA Free mobile app

dreambo said:
For this WE max, sure.
Sent from my 709v92_jbla828 using XDA Free mobile app
Click to expand...
Click to collapse
Sorry didn't catch your phrase
Sent from my bobobibi

Excuse me, I want to say maximum this week-end, my English is very French
Sent from my 709v92_jbla828 using XDA Free mobile app

dreambo said:
Excuse me, I want to say maximum this week-end, my English is very French
Sent from my 709v92_jbla828 using XDA Free mobile app
Click to expand...
Click to collapse
Oh no problem please take your time
Sent from my bobobibi

Tech N You said:
Oh no problem please take your time
Click to expand...
Click to collapse
It is here, please test it and tell me if it works for you.
thank you

Awesome :good:
Sent from 8x-1000 Using XXX ROM (Xceptional XPERIA Xperiance)

dreambo said:
It is here, please test it and tell me if it works for you.
thank you
Click to expand...
Click to collapse
Hey the apply button isn't working! :crying:
LOG here
The DATA and FAT partitions must be found!
Please check your scatter, MBR, EBR1 and EBR2 files
Partitions: {}
totalSize=15528361984 byte (100%)
Before:
sysSize=947912704 byte (6%)
cacheSize=134217728 byte (1%)
dataSize=4294967296 byte (28%)
fatSize=10151264256 byte (65%)

Tech N You said:
Hey the apply button isn't working! :crying:
LOG here
The DATA and FAT partitions must be found!
Please check your scatter, MBR, EBR1 and EBR2 files
Partitions: {}
totalSize=15528361984 byte (100%)
Before:
sysSize=947912704 byte (6%)
cacheSize=134217728 byte (1%)
dataSize=4294967296 byte (28%)
fatSize=10151264256 byte (65%)
Click to expand...
Click to collapse
The apply button is disabled when the program can not find the partitions, given in the scatter, in the boot sectors MBR, EBR1 and EBR2.
Can you give me those 4 files : scatter, MBR, EBR1 and EBR2 (if exists) ?

dreambo said:
The apply button is disabled when the program can not find the partitions, given in the scatter, in the boot sectors MBR, EBR1 and EBR2.
Can you give me those 4 files : scatter, MBR, EBR1 and EBR2 (if exists) ?
Click to expand...
Click to collapse
Sure attaching them here

dreambo said:
The apply button is disabled when the program can not find the partitions, given in the scatter, in the boot sectors MBR, EBR1 and EBR2.
Can you give me those 4 files : scatter, MBR, EBR1 and EBR2 (if exists) ?
Click to expand...
Click to collapse
@dreambo Here are the files. See the attached files and remove ".txt" from MBR EBR1 and EBR2 had to rename them as XDA won't let them upload

Tech N You said:
@dreambo Here are the files. See the attached files and remove ".txt" from MBR EBR1 and EBR2 had to rename them as XDA won't let them upload
Click to expand...
Click to collapse
He is the log I have with those files:
Code:
FAT and DATA sizes must be present in the scatter file!
Please check your scatter (it is made by MtkDroiTools ?)
You can manualy add DATA and FAT sizes in the scatter using MtkDroiTools
Partitions: {ANDROID={0=EBR1}, USRDATA={2=EBR1}, CACHE={1=EBR1}, FAT={0=EBR2}}
totalSize=5377097728 byte (100%)
Before:
sysSize=947912704 byte (18%)
cacheSize=134217728 byte (2%)
dataSize=4294967296 byte (80%)
fatSize=0 byte (0%)
I am not sure that those files are the same you have test in you previous post, the log was different, the probleme was the boot records (perhaps not in the same folder than the scatter) and not the scatter (patition sizes was found) but Now, the boot records are OK (partitions was found) but not the scatter : the FAT size is 0!
If I merge the 2 logs, I can add the fat size from the previous log, to the scatter you give me, and the result is OK :
Code:
Partitions: {ANDROID={0=EBR1}, USRDATA={2=EBR1}, CACHE={1=EBR1}, FAT={0=EBR2}}
totalSize=15528361984 byte (100%)
Before:
sysSize=947912704 byte (6%)
cacheSize=134217728 byte (1%)
dataSize=4294967296 byte (28%)
fatSize=10151264256 byte (65%)
So, just open you scatter you give me in text editor, and replace the line "partition_size: 0x0" with this "partition_size: 0x25D100000" in the FAT section (partition_index: SYS19) and you will be able to resize your partitions.
do not forgot, the scatter and boot records (MBR, EBR1 and EBR2) must be in the same folder!
I am waiting your feedback.

dreambo said:
He is the log I have with those files:
Code:
FAT and DATA sizes must be present in the scatter file!
Please check your scatter (it is made by MtkDroiTools ?)
You can manualy add DATA and FAT sizes in the scatter using MtkDroiTools
Partitions: {ANDROID={0=EBR1}, USRDATA={2=EBR1}, CACHE={1=EBR1}, FAT={0=EBR2}}
totalSize=5377097728 byte (100%)
Before:
sysSize=947912704 byte (18%)
cacheSize=134217728 byte (2%)
dataSize=4294967296 byte (80%)
fatSize=0 byte (0%)
I am not sure that those files are the same you have test in you previous post, the log was different, the probleme was the boot records (perhaps not in the same folder than the scatter) and not the scatter (patition sizes was found) but Now, the boot records are OK (partitions was found) but not the scatter : the FAT size is 0!
If I merge the 2 logs, I can add the fat size from the previous log, to the scatter you give me, and the result is OK :
Code:
Partitions: {ANDROID={0=EBR1}, USRDATA={2=EBR1}, CACHE={1=EBR1}, FAT={0=EBR2}}
totalSize=15528361984 byte (100%)
Before:
sysSize=947912704 byte (6%)
cacheSize=134217728 byte (1%)
dataSize=4294967296 byte (28%)
fatSize=10151264256 byte (65%)
So, just open you scatter you give me in text editor, and replace the line "partition_size: 0x0" with this "partition_size: 0x25D100000" in the FAT section (partition_index: SYS19) and you will be able to resize your partitions.
do not forgot, the scatter and boot records (MBR, EBR1 and EBR2) must be in the same folder!
I am waiting your feedback.
Click to expand...
Click to collapse
I am so sorry but please can you do it for me I am a total noob in this please can u help

Tech N You said:
I am so sorry but please can you do it for me I am a total noob in this please can u help
Click to expand...
Click to collapse
here the correct scatter.
copy it in the same folder as MBR, EBR1 and EBR2, open it with JMTKResizer and you can resize your partitions
Code:
############################################################################################################
#
# General Setting
#
############################################################################################################
- general: MTK_PLATFORM_CFG
info:
- config_version: V1.1.2
platform: MT6592
project: j608_xolo
storage: EMMC
boot_channel: MSDC_0
block_size: 0x20000
############################################################################################################
#
# Layout Setting
#
############################################################################################################
- partition_index: SYS0
partition_name: PRELOADER
file_name: preloader_j608_xolo.bin
is_download: true
type: SV5_BL_BIN
linear_start_addr: 0x0
physical_start_addr: 0x0
partition_size: 0x40000
region: EMMC_BOOT_1
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: BOOTLOADERS
reserve: 0x00
- partition_index: SYS1
partition_name: MBR
file_name: MBR
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x0
physical_start_addr: 0x0
partition_size: 0x80000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS2
partition_name: EBR1
file_name: EBR1
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x80000
physical_start_addr: 0x80000
partition_size: 0x80000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS3
partition_name: PRO_INFO
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0x100000
physical_start_addr: 0x100000
partition_size: 0x300000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: PROTECTED
reserve: 0x00
- partition_index: SYS4
partition_name: NVRAM
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0x400000
physical_start_addr: 0x400000
partition_size: 0x500000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: BINREGION
reserve: 0x00
- partition_index: SYS5
partition_name: PROTECT_F
file_name: NONE
is_download: false
type: EXT4_IMG
linear_start_addr: 0x900000
physical_start_addr: 0x900000
partition_size: 0xa00000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: PROTECTED
reserve: 0x00
- partition_index: SYS6
partition_name: PROTECT_S
file_name: NONE
is_download: false
type: EXT4_IMG
linear_start_addr: 0x1300000
physical_start_addr: 0x1300000
partition_size: 0xa00000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: PROTECTED
reserve: 0x00
- partition_index: SYS7
partition_name: SECCFG
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0x1d00000
physical_start_addr: 0x1d00000
partition_size: 0x40000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: INVISIBLE
reserve: 0x00
- partition_index: SYS8
partition_name: UBOOT
file_name: lk.bin
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x1d40000
physical_start_addr: 0x1d40000
partition_size: 0x60000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS9
partition_name: BOOTIMG
file_name: boot.img
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x1da0000
physical_start_addr: 0x1da0000
partition_size: 0xa00000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS10
partition_name: RECOVERY
file_name: recovery.img
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x27a0000
physical_start_addr: 0x27a0000
partition_size: 0xa00000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS11
partition_name: SEC_RO
file_name: secro.img
is_download: true
type: EXT4_IMG
linear_start_addr: 0x31a0000
physical_start_addr: 0x31a0000
partition_size: 0x600000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS12
partition_name: MISC
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0x37a0000
physical_start_addr: 0x37a0000
partition_size: 0x80000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: INVISIBLE
reserve: 0x00
- partition_index: SYS13
partition_name: LOGO
file_name: logo.bin
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x3820000
physical_start_addr: 0x3820000
partition_size: 0x800000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS14
partition_name: EBR2
file_name: EBR2
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x4020000
physical_start_addr: 0x4020000
partition_size: 0x80000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS15
partition_name: EXPDB
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0x40a0000
physical_start_addr: 0x40a0000
partition_size: 0xf60000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: INVISIBLE
reserve: 0x00
- partition_index: SYS16
partition_name: ANDROID
file_name: system.img
is_download: true
type: EXT4_IMG
linear_start_addr: 0x5000000
physical_start_addr: 0x5000000
partition_size: 0x38800000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS17
partition_name: CACHE
file_name: cache.img
is_download: true
type: EXT4_IMG
linear_start_addr: 0x3d800000
physical_start_addr: 0x3d800000
partition_size: 0x8000000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS18
partition_name: USRDATA
file_name: userdata.img
is_download: true
type: EXT4_IMG
linear_start_addr: 0x45800000
physical_start_addr: 0x45800000
partition_size: 0x100000000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS19
partition_name: FAT
file_name: NONE
is_download: false
type: EXT4_IMG
linear_start_addr: 0x145800000
physical_start_addr: 0x145800000
partition_size: 0x25D100000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: INVISIBLE
reserve: 0x00
- partition_index: SYS20
partition_name: BMTPOOL
file_name: NONE
is_download: false
type: NORMAL_ROM
linear_start_addr: 0xFFFF00a8
physical_start_addr: 0xFFFF00a8
partition_size: 0x1500000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: false
is_reserved: true
operation_type: RESERVED
reserve: 0x00

@dreambo See this error! Device not turning on now! :crying:

Tech N You said:
@dreambo See this error! Device not turning on now! :crying:
Click to expand...
Click to collapse
Sorry for that
First, you have always the original scatter (never touched by the program) you can reflash it and revive the phone.
Second, some rules that we must know before using this program :
1- We must know what we are doing, if we resize a partition we must be sure that the image file designed for this partition can fit in the new partition
2- With SPFlashTool, we have to do (as mentinned in the help) a "firmware upgrade" or "format and download all", because we have touched the scatter structure
3- All files must to be provided to SPFlashTool, not only the modded ones.
I have used this program to resize the DATA/FAT partitions for my phone, and it is working as I expect now, it is a STAR N9800, an MT6592 like yours

[ROM] Fake Lenovo S900 5.5'' Unbrick [4.2.2]

I have a fake Lenovo S900 with a lot of apps that fake the real specs of this phone, so I made this rom base in the oficial ROM for Cubot GT88 since it is idential in the real hardware specs.
If you want a clean rom for your fake phone, then install this ROM check the real specs and dont have any other problems, so enjoy it.
1. Make a backup of your nvram with the MTKdroid Tools (IMEI backup)
2. Do a factory restore (dont do this part without previously backup your nvram o imei backup)
3. Use the Flash Tool to install this ROM.
4. Restore the nvram or imei.
Link:
Mega Folder

thanks! i have one but, i have a problem too
thanks! i have one but, i have a problem too
my fake s900 is not entering the menu apps anymore, im not able to navigate in apps or menus. i downloaded your rom, but how i can enter in recover mode in this phone? can you help me?
getting error to get root mode in mtkdroidtools to make a backup
---------- Post added at 08:21 PM ---------- Previous post was at 07:23 PM ----------
miottoss said:
thanks! i have one but, i have a problem too
my fake s900 is not entering the menu apps anymore, im not able to navigate in apps or menus. i downloaded your rom, but how i can enter in recover mode in this phone? can you help me?
getting error to get root mode in mtkdroidtools to make a backup
Click to expand...
Click to collapse
--->>> Connect to device <<<---
ATTENTION! Fake Hardware in kernel or firmware doesn't correspond to phone!
--- scatter is write to the file:
G:\New folder\MtkDroidTools\MT6572_Android_scatter.txt
--->>> Connect to device <<<---
ATTENTION! Fake Hardware in kernel or firmware doesn't correspond to phone!
--- ERROR ttycmd1 device NOT found!
--- Reboot in recovery ...
--->>> Connect to device <<<---
--- ERROR : --- TotalBytesPerChunk Not Found. Set default Page/Spare=2048/64 !!!
--- Unknown ROM structure, backup NOT possible!
--- ATTENTION! Recovery doesn't suit this phone!
--- Unknown ROM structure, backup NOT possible!
--- The preservation folder on the computer: G:\New folder\MtkDroidTools\backups\_700101_ForFlashtoolFromReadBack_150414-161914\

thank you very much!
still appears as lenovo?
model is really known? to seek alternative ROMS ...
I think it is a V5 Jiake, but not sure ... The V6 ROMs work fine, but do not work the cameras
in this ROM I keep getting 4GB of RAM .. some way to modify it to come out the real thing?
and no work the home button

i made this detailed post to try get some help.
hi a i have a fake lenovo s900, and after remove some bloatware, i have a loop in the start screen from android. im not able to enter system, he already back to lockscreen when i pass finger in the screen.
i tried a lot of tutorials, but im not able to make sp_tools recognize the phone.
but droid tools is working. here some photos when i conect in droid tools.
the button to root in droid tools, not work. droid tools freeze
the images are attached
i have a rom to test, but not able to make the sp_tools use the phone.
the rom in this thread: http://forum.xda-developers.com/gen...-5-unbrick-t3080479/post60112257#post60112257
folder with vid e images for details.
https://www.dropbox.com/sh/9g6sdft0pqh96lv/AADFCD-o9kk1XC6OvJZU3Gtia?dl=0
any idea how i can fix this? thanks!

miottoss said:
i made this detailed post to try get some help.
hi a i have a fake lenovo s900, and after remove some bloatware, i have a loop in the start screen from android. im not able to enter system, he already back to lockscreen when i pass finger in the screen.
i tried a lot of tutorials, but im not able to make sp_tools recognize the phone.
but droid tools is working. here some photos when i conect in droid tools.
the button to root in droid tools, not work. droid tools freeze
the images are attached
i have a rom to test, but not able to make the sp_tools use the phone.
the rom in this thread: http://forum.xda-developers.com/gen...-5-unbrick-t3080479/post60112257#post60112257
folder with vid e images for details.
https://www.dropbox.com/sh/9g6sdft0pqh96lv/AADFCD-o9kk1XC6OvJZU3Gtia?dl=0
any idea how i can fix this? thanks!
Click to expand...
Click to collapse
I was the same
the problem is the launcher, which is corrupt
I solved it like this:
down the notification bar and enter settings
click on settings (sometimes not work the first time, try more times)
once in settings, go to Applications
locate the store play
install any launcher to your liking
once installed, should have finished your problem, try and comment

im a noob here so i cant post links or files :/
I'm back to say that my fake S900 is ok again. i useD the romfrom heldigard friend. with this rom several software problems have been resolved, as the HDR CAM which no longer turns off the camera after taking a photo HDR. im testing more apps.
I do not know if it was that, but I did several extra steps.
installed the android SDK following these steps.
used drivers: ADB_usb_driver_120827_v3 and A25_USB_VCOM_Drivers
1- GOOGLE SEARCH: [TUTORIAL] Como instalar o SDK TOOLS e habilitar o ADB
2- YOUTUBE SEARCH: How To Flash ROM for Every China Phone with the SP Flash Tool ! [HD]
i just flashed "system.img" in ANDROID section of sp_tools.
after all installed mtkdroid_tools use to extract and save your android_scatter.txt-it
sp_tools open, choose your android_scatter, select ANDROID in the list below, and choose system.img.
click download
OFF with the device connect it to the USB
wait a few seconds and the sp_tools begin the the update
then just restart your phone
NOW YOU HAVE A CUBOT START SCREEN. NO MORE LENOVO.
wohooooooooooooooooooo!

miottoss said:
i made this detailed post to try get some help.
hi a i have a fake lenovo s900, and after remove some bloatware, i have a loop in the start screen from android. im not able to enter system, he already back to lockscreen when i pass finger in the screen.
i tried a lot of tutorials, but im not able to make sp_tools recognize the phone.
but droid tools is working. here some photos when i conect in droid tools.
the button to root in droid tools, not work. droid tools freeze
the images are attached
i have a rom to test, but not able to make the sp_tools use the phone.
the rom in this thread: http://forum.xda-developers.com/gen...-5-unbrick-t3080479/post60112257#post60112257
folder with vid e images for details.
https://www.dropbox.com/sh/9g6sdft0pqh96lv/AADFCD-o9kk1XC6OvJZU3Gtia?dl=0
any idea how i can fix this? thanks!
Click to expand...
Click to collapse
miottoss said:
im a noob here so i cant post links or files :/
I'm back to say that my fake S900 is ok again. i useD the romfrom heldigard friend. with this rom several software problems have been resolved, as the HDR CAM which no longer turns off the camera after taking a photo HDR. im testing more apps.
I do not know if it was that, but I did several extra steps.
installed the android SDK following these steps.
used drivers: ADB_usb_driver_120827_v3 and A25_USB_VCOM_Drivers
1- GOOGLE SEARCH: [TUTORIAL] Como instalar o SDK TOOLS e habilitar o ADB
2- YOUTUBE SEARCH: How To Flash ROM for Every China Phone with the SP Flash Tool ! [HD]
i just flashed "system.img" in ANDROID section of sp_tools.
after all installed mtkdroid_tools use to extract and save your android_scatter.txt-it
sp_tools open, choose your android_scatter, select ANDROID in the list below, and choose system.img.
click download
OFF with the device connect it to the USB
wait a few seconds and the sp_tools begin the the update
then just restart your phone
NOW YOU HAVE A CUBOT START SCREEN. NO MORE LENOVO.
wohooooooooooooooooooo!
Click to expand...
Click to collapse
tou're spanish?

vicent76 said:
tou're spanish?
Click to expand...
Click to collapse
br

miottoss said:
br
Click to expand...
Click to collapse
nah, curiosity...
in your previous post put a google search in Spanish, caught my attention.
a greeting

Hola! llevo con el telefono brickeado mas de un mes, he probado lo imposible y con todo tipo de FW y no hay manera de conseguir hacerlo volver a la vida.
Llevaba bastante esperando que alguien subiera una ROM cualquiera para probar si por fin conseguia la barra verde en el flashtool pero me sigue dando el error de siempre:
http: // i57.tinypic.com / 16a9rhe.png (quitar los espacios del link)
El telefono esta totalmente brickeado y ni enciende, ya lo habia dejado por imposible.
Muchas gracias!
--------------------------------------------------------------------
Hi! I have the phone briked since one month or more. I tried all and nothing makes alive the phone again
I've been waiting for somebody could upload the original rom, so i would can try if I get a green bar on flashtool app, but I still having the same error:
http: // i57.tinypic.com / 16a9rhe.png (put out the spaces on the link)
The phone are completly bricked, it no powers on, I left it for imposible
Sorry for my english and lots of thanks

s900 lenovo
i found this rom and tested in my lenovo s900 fake. is a lenovo 5.5 fake mtk 6592
Hardware : MT6572 (MTK6592 is Fake!)
Model : S900
Build number : S5_JB3_3G_EMMC_32_4_XLD_QHD_Z7_LZ_S900_20141211.10 4037
Build date UTC : 20141209-024037
Android v : 4.4.3
Baseband v: MOLY.WR8.W1315.MD.WG.MP.V15, 2014/08/04 16:18
download:
yadi.sk/d/8TSef8IZewx3y
try this video to see how flash.
youtube.com/watch?v=ztI8sc8MUNo
good luck.

anbs said:
i found this rom and tested in my lenovo s900 fake. is a lenovo 5.5 fake mtk 6592
Hardware : MT6572 (MTK6592 is Fake!)
Model : S900
Build number : S5_JB3_3G_EMMC_32_4_XLD_QHD_Z7_LZ_S900_20141211.10 4037
Build date UTC : 20141209-024037
Android v : 4.4.3
Baseband v: MOLY.WR8.W1315.MD.WG.MP.V15, 2014/08/04 16:18
download:
yadi.sk/d/8TSef8IZewx3y
try this video to see how flash.
youtube.com/watch?v=ztI8sc8MUNo
good luck.
Click to expand...
Click to collapse
Hello
Do You can send my scatter file for S900 fake ?

bartsoft said:
Hello
Do You can send my scatter file for S900 fake ?
Click to expand...
Click to collapse
save all below as a "MT6592_Android_scatter.txt"
############################################################################################################
#
# General Setting
#
############################################################################################################
- general: MTK_PLATFORM_CFG
info:
- config_version: V1.1.1
platform: MT6572
project: yuanda72_wet_a_jb3
storage: EMMC
boot_channel: MSDC_0
block_size: 0x20000
############################################################################################################
#
# Layout Setting
#
############################################################################################################
- partition_index: SYS0
partition_name: PRELOADER
file_name: preloader_yuanda72_wet_a_jb3.bin
is_download: true
type: SV5_BL_BIN
linear_start_addr: 0x0
physical_start_addr: 0x0
partition_size: 0xc00000
region: EMMC_BOOT_1
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: BOOTLOADERS
reserve: 0x00
- partition_index: SYS1
partition_name: MBR
file_name: MBR
is_download: true
type: NORMAL_ROM
linear_start_addr: 0xc00000
physical_start_addr: 0x0
partition_size: 0x80000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS2
partition_name: EBR1
file_name: EBR1
is_download: true
type: NORMAL_ROM
linear_start_addr: 0xc80000
physical_start_addr: 0x0
partition_size: 0x80000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS3
partition_name: PRO_INFO
file_name: NONE
is_download: false
type: NONE
linear_start_addr: 0xd00000
physical_start_addr: 0x0
partition_size: 0x300000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: PROTECTED
reserve: 0x00
- partition_index: SYS4
partition_name: NVRAM
file_name: NONE
is_download: false
type: NONE
linear_start_addr: 0x1000000
physical_start_addr: 0x0
partition_size: 0x500000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: BINREGION
reserve: 0x00
- partition_index: SYS5
partition_name: PROTECT_F
file_name: NONE
is_download: false
type: NONE
linear_start_addr: 0x1500000
physical_start_addr: 0x0
partition_size: 0xa00000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: PROTECTED
reserve: 0x00
- partition_index: SYS6
partition_name: PROTECT_S
file_name: NONE
is_download: false
type: NONE
linear_start_addr: 0x1f00000
physical_start_addr: 0x0
partition_size: 0xa00000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: PROTECTED
reserve: 0x00
- partition_index: SYS7
partition_name: SECCFG
file_name: NONE
is_download: false
type: NONE
linear_start_addr: 0x2900000
physical_start_addr: 0x0
partition_size: 0x20000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: INVISIBLE
reserve: 0x00
- partition_index: SYS8
partition_name: UBOOT
file_name: lk.bin
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x2920000
physical_start_addr: 0x0
partition_size: 0x60000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS9
partition_name: BOOTIMG
file_name: boot.img
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x2980000
physical_start_addr: 0x0
partition_size: 0x600000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS10
partition_name: RECOVERY
file_name: recovery.img
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x2f80000
physical_start_addr: 0x0
partition_size: 0x600000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS11
partition_name: SEC_RO
file_name: secro.img
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x3580000
physical_start_addr: 0x0
partition_size: 0x40000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS12
partition_name: MISC
file_name: NONE
is_download: false
type: NONE
linear_start_addr: 0x35c0000
physical_start_addr: 0x0
partition_size: 0x80000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: INVISIBLE
reserve: 0x00
- partition_index: SYS13
partition_name: LOGO
file_name: logo.bin
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x3640000
physical_start_addr: 0x0
partition_size: 0x300000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS14
partition_name: EXPDB
file_name: NONE
is_download: false
type: NONE
linear_start_addr: 0x3940000
physical_start_addr: 0x0
partition_size: 0xa00000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: INVISIBLE
reserve: 0x00
- partition_index: SYS15
partition_name: ANDROID
file_name: system.img
is_download: true
type: YAFFS_IMG
linear_start_addr: 0x4340000
physical_start_addr: 0x0
partition_size: 0x28a00000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS16
partition_name: CACHE
file_name: cache.img
is_download: true
type: YAFFS_IMG
linear_start_addr: 0x2cd40000
physical_start_addr: 0x0
partition_size: 0x17800000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS17
partition_name: USRDATA
file_name: userdata.img
is_download: true
type: YAFFS_IMG
linear_start_addr: 0x44540000
physical_start_addr: 0x0
partition_size: 0x52c00000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
- partition_index: SYS18
partition_name: FAT
file_name: NONE
is_download: false
type: NONE
linear_start_addr: 0x97140000
physical_start_addr: 0x0
partition_size: 0x0
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: INVISIBLE
reserve: 0x00
- partition_index: SYS19
partition_name: BMTPOOL
file_name: NONE
is_download: false
type: NONE
linear_start_addr: 0xFFFF00a8
physical_start_addr: 0x0
partition_size: 0x1500000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: false
is_reserved: true
operation_type: RESERVED
reserve: 0x00

Need S900 mtk6580 firmware
I have also a fake lenove s900. i need mtk6580 firmware

yadi.sk/d/8TSef8IZewx3y - your link is dead. please upload it again. Thanks in advance.

[Completed] MTK6572 M8 SP Flash Tools Scatter file question

Hi there,
I have an MTK6572 M8 4.2.2 HTC clone that I picked up 2nd hand. The previous owner had somehow installed KingRoot as an embedded system app and all attempts to remove it completely have failed. My only option appears to be to apply a new system.img file.
I created an SP Flash Tool scatter file and have found a ROM whose scatter file indicates that the contents of this ROM are identical (almost) to that of the phone I am trying to fix. When I compare the 2 scatter files one line differs, see following text. I've tried Root Browser (with root) to get rid of the KingRoot.apk from the system/apps dir but it refuses to 'go away'.
SCATTER FILES
MINE DOWNLOADED ROM
partition_index: SYS18 partition_index: SYS18
partition_name: FAT partition_name: FAT
file_name: NONE file_name: NONE
is_download: false is_download: false
type: NONE type: NONE
linear_start_addr: 0x36740000 linear_start_addr: 0x36740000
physical_start_addr: 0x35B40000 physical_start_addr: 0x35B40000
partition_size: 0x387E0000 XXXXX partition_size: 0xB49C0000
region: EMMC_USER region: EMMC_USER
storage: HW_STORAGE_EMMC storage: HW_STORAGE_EMMC
boundary_check: true boundary_check: true
is_reserved: false is_reserved: false
operation_type: INVISIBLE operation_type: INVISIBLE
reserve: 0x00 reserve: 0x00
The contents of each scatter file is identical apart from the line marked XXXXX partition_size: 0xB49C0000
My questions are.
1. Do I need to make modifications during the SP Flash Tool flashing process to make sure that I don't damage anything?
2. Is it enough to just flash the system.img file on it's own? Which would mean that I don't have to worry about the variation in partition sizes, just select the system.img file and download to phone, which I believe will replace my system dir with the original.
Sorry if I have asked any dumb questions, but when you are on the brink of doing something that might trash your phone you should at least seek a 2nd opinion from someone more who has more experience (less fear).
Thanks in advance for your advice.
Barney

barniclebill said:
Hi there,
I have an MTK6572 M8 4.2.2 HTC clone that I picked up 2nd hand. The previous owner had somehow installed KingRoot as an embedded system app and all attempts to remove it completely have failed. My only option appears to be to apply a new system.img file.
I created an SP Flash Tool scatter file and have found a ROM whose scatter file indicates that the contents of this ROM are identical (almost) to that of the phone I am trying to fix. When I compare the 2 scatter files one line differs, see following text. I've tried Root Browser (with root) to get rid of the KingRoot.apk from the system/apps dir but it refuses to 'go away'.
SCATTER FILES
MINE DOWNLOADED ROM
partition_index: SYS18 partition_index: SYS18
partition_name: FAT partition_name: FAT
file_name: NONE file_name: NONE
is_download: false is_download: false
type: NONE type: NONE
linear_start_addr: 0x36740000 linear_start_addr: 0x36740000
physical_start_addr: 0x35B40000 physical_start_addr: 0x35B40000
partition_size: 0x387E0000 XXXXX partition_size: 0xB49C0000
region: EMMC_USER region: EMMC_USER
storage: HW_STORAGE_EMMC storage: HW_STORAGE_EMMC
boundary_check: true boundary_check: true
is_reserved: false is_reserved: false
operation_type: INVISIBLE operation_type: INVISIBLE
reserve: 0x00 reserve: 0x00
The contents of each scatter file is identical apart from the line marked XXXXX partition_size: 0xB49C0000
My questions are.
1. Do I need to make modifications during the SP Flash Tool flashing process to make sure that I don't damage anything?
2. Is it enough to just flash the system.img file on it's own? Which would mean that I don't have to worry about the variation in partition sizes, just select the system.img file and download to phone, which I believe will replace my system dir with the original.
Sorry if I have asked any dumb questions, but when you are on the brink of doing something that might trash your phone you should at least seek a 2nd opinion from someone more who has more experience (less fear).
Thanks in advance for your advice.
Barney
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist.
Please consider asking your questions here:
Android Q&A
The experts there may be able to help you.
Good luck!

[Completed] Mtk6572 recovery size !

hello everyone :laugh:
i want to extend my recovery size to 7mb
i read an article that convert 1mb from bootimg patition to the recovery partition :
http://forum.xda-developers.com/showpost.php?p=55160827&postcount=100
but i had a problem with applying it
i have a problem with editing the values ( numbers)
i changed the partion size but linear_start_addr its not like the same in the article :silly:
i dont have numbers i have numbers and letters
this is how its look like in my scartter file
partition_index: SYS10
partition_name: RECOVERY
file_name: recovery.img
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x2f80000
physical_start_addr: 0x0
partition_size: 0x700000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
so please any one if you know the answer tell me :good::good:
good by :highfive:

OP reposted in the correct section:
http://forum.xda-developers.com/and...overy-size-t3435185/post68093408#post68093408
Thread closed.