yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] syserr:
^ An example of why we need a MediaTek sub-forum. No one knows where to post. (including me, and I'm pretty much sole-ly supporting a MTK device)
[Android Software/Hacking General [Developers Only]] Alex1948:
For Flash , another , identical phone

Someone has my same phone.A5 DUO , MT6572 chipset

It did not backup the firmware

He installed the firmware on a phone Walton.

Now he wants to quit, to return to firmware

What files to give the backup(!Files_to_FlashTool) , for flash ?

Boot.img , recovery.img and system.img ? Now it has another logo.Se change and it?

Are enough to flash these files??

See image my backup((!Files_to_FlashTool)
[Android Software/Hacking General [Developers Only]] rua1:
@Alex1948 , Probably everything, except for the userdata.img file. This file can contain your personal data and passwors!
[Android Software/Hacking General [Developers Only]] Alex1948:
IMEI change or no

Thanks, I understand , and cache ???But IMEI, change it(phone is dual-sim)

Not change his IMEI with my IMEI , or remain without IMEI.
[Android Software/Hacking General [Developers Only]] jaiswalnilesh:
Plese Help me Getting this error when extracting partitions for recovery

Tablet is

Swipe MTV Slash

JB 4.1.2

--- root shel it is received temporarily before reboot !

--- The preservation folder on the computer: C:\MKT Tools\MtkDroidTools\backups\MTV-SLASH_130629_ForFlashtoolFromReadBack_131119-215930\

--- scatter is write to the file:

C:\MKT Tools\MtkDroidTools\backups\MTV-SLASH_130629_ForFlashtoolFromReadBack_131119-215930\MT6577_Android_scatter_emmc.txt

-- preloader.bin ...it is copied ... cut OK

-- DSP_BL ...it is copied ... cut OK

-- MBR ...it is copied

-- EBR1 ...it is copied

-- uboot.bin - The signature isn't found!

--- ERROR of a signature, ôàéë ROM ïðî÷èòàí èç òåëåôîíà íåâåðíî!

--- task end with ERROR ---
[Android Software/Hacking General [Developers Only]] oscarblue48:
Try later/different version of Spflashtool, latest version here.... SP_Flash_Tool_v3.1328.0.183.7z
[Android Software/Hacking General [Developers Only]] jaiswalnilesh:
I did

Thanks for ure response. I tried with latest only.

The error i am getting is from MKT droid tools and not SP_Flash tools
[Android Software/Hacking General [Developers Only]] oscarblue48:
Sorry, I assumed you were following the tutorial on page one of this thread, and were up to step 7 which involves processing your Rom file created by SP flashtool, and was suggesting you might try creating your rom file with a different version of Sp flashtool, as this is quite buggy software whatever the version, and often causes errors
[Android Software/Hacking General [Developers Only]] jaiswalnilesh:
Error in Step -- Process file ROM_ from Flash tools

Hello friend

I am having Swipe MTV Slash Tablet with JB 4.1.2 with following specifications

Hardware : MT6577

Model : MTV SLASH

Build number : MD700HB.1G.V1.60.2013.07.01

Build date UTC : 20130629-075032

Android v : 4.1.2

Baseband v: MAUI.11AMD.W12.22.SP.V27, 2013/03/23 22:24

Kernel v : 3.4.0 (root@elinktek) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP Mon Jul 1 16:20:55 CST 2013

I dont have factory ROM or Stock ROM for my tablet as company is not providing it

so i decided to back up ROM and install recovery via droid tools and flash tool

i was successful in extracting and creating ROM file via Scatter file and Flash tools

but after that

WHEN TRIED TO THE STEP OF --- PROCESS FILE ROM_ FROM FLASH TOOL---

I GET FOLLOWING ERROR

--- root shel it is received temporarily before reboot !

--- The preservation folder on the computer: C:\MKT Tools\MtkDroidTools\backups\MTV-SLASH_130629_ForFlashtoolFromReadBack_131119-215930\

--- scatter is write to the file:

C:\MKT Tools\MtkDroidTools\backups\MTV-SLASH_130629_ForFlashtoolFromReadBack_131119-215930\MT6577_Android_scatter_emmc.txt

-- preloader.bin ...it is copied ... cut OK

-- DSP_BL ...it is copied ... cut OK

-- MBR ...it is copied

-- EBR1 ...it is copied

-- uboot.bin - The signature isn't found!

--- ERROR of a signature, ôàéë ROM ïðî÷èòàí èç òåëåôîíà íåâåðíî!

--- task end with ERROR ---

Please help me
[Android Software/Hacking General [Developers Only]] rua1:
@Alex1948

I never saw in cache of important information... and I do not know, why this block in general is necessary ;)

@jaiswalnilesh

What you use the program version? If 2.4.8, give me ROM_ and scatter.
[Android Software/Hacking General [Developers Only]] watusi:
yes thanks...working on my DaxianE668 chinese phone...root,backup,etc

my only problem now is google play error 403

anyway thanks for the tool!!!bravo!!!
[Android Software/Hacking General [Developers Only]] spiderman1961:
Restoring stock "chinese" recovery on IdeaTab s6000h

Hi,

i used wonderful tool to make custom recovery for lenovo ideatab s6000h; unfortunately i forgot backup original stock recovery :(

Now i received an update fron Lenovo and i can't install it!

Error message is "can't mount sd card"

I copied Lenovo update.zip on external microsd, but no success in upgrade.

I think it's because changed recovery.

So anybody can help me to restore stock recovery or explain me how solve upgrading issue?

Thanks on advance
[Android Software/Hacking General [Developers Only]] fragargon:
hi [MENTION=4927589]spiderman1961[/MENTION],

I've got the same situation as yours on same tablet. ideatab s6000-h

look to this thread, u can grab a full stock image from lenovo forum thanks goes to bgcngm http://xdaforums.com/showthread.php?t=2368913&page=5

the probleme is that the update given by lenovo used diff file to patch boot, recovery and other system stuff (some interesting driver that i would like to patch).

so the update script uses assert apply_patch_check and made a haschfile sha1 of boot and recovery.

I already restore recovery from stock with mtktool (look page 69 [MENTION=5119815]rua1[/MENTION] gives some advices) however it still fails coz patched boot.img.

I m still looking forward to get out of this update process. if you find some good advice share them pls.
[Android Software/Hacking General [Developers Only]] syserr:
[GUIDE][UTIL][MT65xx] Create Scatter File and Dump Full ROM

For any MT65xx device, no matter how obscure.

http://xdaforums.com/showthread.php?t=2540400

A few reasons to look at the guide/mini-util above:

* If you feel like understanding more of how MediaTek works

* you want a ROM dump without rooting

* you want a ROM dump without your OS booted (clone cold system is safe)

* you want a guaranteed way to restore exactly current state (safety and return to store)

* you are just plain worried something will go wrong

rua1's tool here is great and I recommend it. This is a different way to skin the cat. The way I describe is definitely not as easy, but does have some merits. Just letting the information flow...

-syserr
[Android Software/Hacking General [Developers Only]] Alex1948:
Only original recovery

Yes , and I think it is because changed recovery.Update can not be done without the original recovery.

With SP Flash tool , flash only original recovery - see image
[Android Software/Hacking General [Developers Only]] farazafs:
Hello, I have QMobile Noir Quatro Z4 which is rebrand of Gionee Elife E6! I want to change partition layout, to install Gionee Elife E6 Firmware, If I can install Gionee system only... while applying OTA Update it's give me error of incorrect partition in Recovery! can anyone help me in this issue???

Partition Layout of QMobile Quatro Z4:

PRELOADER 0x0

MBR 0x600000

EBR1 0x680000

__NODL_PMT 0x700000

__NODL_PRO_INFO 0xb00000

__NODL_NVRAM 0xe00000

__NODL_PROTECT_F 0x1300000

__NODL_PROTECT_S 0x1d00000

__NODL_SECCFG 0x2700000

UBOOT 0x2720000

BOOTIMG 0x2780000

RECOVERY 0x2d80000

SEC_RO 0x3380000

__NODL_MISC 0x3980000

LOGO 0x3a00000

EBR2 0x3d00000

__NODL_EXPDB 0x3d80000

ANDROID 0x4f80000

CACHE 0x4b380000

USRDATA 0x63380000

FAT 0x123380000

__NODL_BMTPOOL 0xffff00a8

Partition Layout of Gionee Elife E6:

PRELOADER 0x0

MBR 0x600000

EBR1 0x680000

__NODL_PMT 0x700000

__NODL_PRO_INFO 0xb00000

__NODL_NVRAM 0xe00000

__NODL_PROTECT_F 0x1300000

__NODL_PROTECT_S 0x1d00000

__NODL_SECCFG 0x2700000

UBOOT 0x2720000

BOOTIMG 0x2780000

RECOVERY 0x2d80000

SEC_RO 0x3380000

__NODL_MISC 0x3980000

LOGO 0x3a00000

EBR2 0x3d00000

__NODL_EXPDB 0x3d80000

ANDROID 0x4780000

CACHE 0x44780000

USRDATA 0x5c780000

FAT 0xdc780000

__NODL_BMTPOOL 0xFFFF00a8
[Android Software/Hacking General [Developers Only]] Alex1948:
Update

You can not update OTA or update.zip(file for site) without original recovery on phone.It is my opinion.....?!

As shown , recovery.img is : RECOVERY 0x2d80000-(block adress) but it's not working.?

Other opinions ?
[Android Software/Hacking General [Developers Only]] farazafs:
Any other way? I want to change block address in which place it can be change? Preloader, MBR, EBR1, EBR2?
[Android Software/Hacking General [Developers Only]] syserr:
I think he was saying he could boot into recovery, but during the update process... the update detects incorrect partitions and will not install.

One way is to go all the way with your target layout. If you have a full SPFT-style ROM. It would have your PRELOADER, MBR, EBR1, EBR2 etc... everything. You would use SPFT to Format and then Download the whole thing. I'm assuming either you don't have a full SPFT-style ROM or you don't want to wipeout your flash to install it.

If you want to change the layout but don't have the target layout's MBR, EBR1, EBR2... then I have a tool for that. I'd like to release it on github after a little cleaning. I can create an MBR, EBR1, EBR2 to your specifications in your target layout specified by the scatter file. But you need to understand just changing the contents of MBR, EBR1, EBR2 will break things... the partitions also have to match the scatter file locations. You have 4 indicators on locations of partitions: scatter file, PMT partition, MBR/EBR1/2, then reality of where the partition was written. They all need to match ;)

Update: As long as you don't change the number of partitions or re-arrange them... you only need to tweak MBR, EBR1, EBR2... and during SPFT Format the PMT partition is written according to the scatter file.

Let me know,

syserr
[Android Software/Hacking General [Developers Only]] syserr:
The GScript shell scripts that gather the info, I know grabbed dumchar_info and saved it as firmware.info. rua1 may have been responsible for those scripts too. I used it to learn. :good:

Yes, you can see my little python that processes /dev/dumchar_info does that addition. I've only experimented with EMMC type flash, I don't know about the other. I don't feel as comfortable relying on dumchar and offsets as I do the SPFT log. I like to see both dumchar_info and SPFT log match, then I feel good. ;)

if block != 'misc':
start = start + 0x600000

Alex1948, I'm not sure what you mean? (sorry)

UPDATE:

Sorry I re-read your comment again. Yes... you get a file called scatter.txt that matches the firmware. The script's input is the dumchar_info file and the output is a well formatted scatter file.

UPDATE2:

Alex1948, It may have been confusing, this is not the python script I'm using to adjust MBR, EBR1, EBR2.
[Android Software/Hacking General [Developers Only]] farazafs:
I have full SP Flash Tool ROM of both QMobile Quatro Z4 and Gionee Elife E6! including (Preload, LK, MBR, EBR1, EBR2, Boot, Recovery, System) I think these are main files! I want to flash and layout partition according to Gionee Elife E6. I want to change these layout only...

Partition Layout of QMobile Quatro Z4:

ANDROID 0x4f80000

CACHE 0x4b380000

USRDATA 0x63380000

FAT 0x123380000

TO.

Partition Layout of Gionee Elife E6:

ANDROID 0x4780000

CACHE 0x44780000

USRDATA 0x5c780000

FAT 0xdc780000

Tell me easy way how it's possible, If it'll be able via ur software then share me i can do it, or other option is I can Provide you both Preload, MBR, EBR1, EBR2 u can do it for me.

Main thing is I want to port 100% Gionee Elife E6 Firmware, I m sure it is possible but need little help from u people.
[Android Software/Hacking General [Developers Only]] syserr:
If you have all you need of the Gionee SPFT-style ROM, I would only use it. It should work. If you have Gionee preload, MBR, EBR1, EBR2, system, etc.. and a scatter file that matches them all it should be easy. In SPFT, choose Gionee's scatter file. Make sure all the blocks that you want are loaded.. Format / Download. I hope it is that simple, or I don't understand what is hard.
[Android Software/Hacking General [Developers Only]] farazafs:
Only problem I m predicting that Invalid IMEI issue and GPS issue after flashing this coz, I was done before on Qmobile A900 which is similar to Gionee Elife E3!

---------- Post added at 09:09 PM ---------- Previous post was at 08:57 PM ----------

Bro is this is possible to do this process without format all? just select scatter file of Gionee Elife E6 and flash all including (Preloader, MBR, EBR1, EBR2, SecRo, UBOOT, LOGO, Boot, Recovery, System, Cache, Userdata, Fat). it'll work?
[Android Software/Hacking General [Developers Only]] syserr:
The first thing I would do is a full backup, it will grab the NVRAM partition and everything else. You could also do a partial backup of the NVRAM. I think backing up the NVRAM partition is much more sure than backup of /data/nvram.

I've outlined a complete backup here: http://xdaforums.com/showpost.php?p=46544293&postcount=3

To backup just the NVRAM partition, it would be the same except your begin address would be 0xe00000 and length 0x500000. You have other partitions that I'm not familiar with, so I would read those individually too.

??? __NODL_PRO_INFO 0xb00000

__NODL_NVRAM 0xe00000

??? __NODL_PROTECT_F 0x1300000

??? __NODL_PROTECT_S 0x1d00000

For insurance, even if you backup all 4 of those individually with SPFT... I'd still "read back" the whole dang thing for safety. You don't need cache, userdata, fat... those can be recreated. so I'd go begin address: 0x0 length: 0x4b380000. That's about 1.2GB... will take probably 2-3 hours.
[Android Software/Hacking General [Developers Only]] Alex1948:
Excuse me, after you get this scatter file , as that obtained with MTKDroid , see image 1 ?

or , scatter file with start adress and lenght , firmware , see image 2.(and dumchar_info , look the same.)
[Android Software/Hacking General [Developers Only]] Alex1948:
Scatter file

I send dumchar_info, I've renamed it dumchar.txt and MT6572_Android_scatter_emmc , I've renamed it scatter.txt.

Wed crashes when I run your script
[Android Software/Hacking General [Developers Only]] fragargon:
delete the file scatter.txt, the script creates it and looks like the MTK scatter file except some " _NODL_" do not know what thatNODL_mean.
[Android Software/Hacking General [Developers Only]] syserr:
The _NODL_ is a flag that SPFT uses to not include the block in it's normal Download process. So, for instance, you normally don't clobber the NVRAM block partition... it is marked _NODL_. This information is not only in the scatter file, but also in the PMT partition, which is dynamically written during SPFT Format.

---------- Post added at 06:09 PM ---------- Previous post was at 06:02 PM ----------

I use both methods in my post to get a good feel for the scatter file. The input is the dumchar.txt and the output is scatter.txt. You will have to rename the scatter.txt file accordingly -- and for you it probably is MT6572_Android_scatter_emmc.txt.

But yes, this method doesn't know what partitions to designate with _NODL_ prefix on the block names. That is why the SPFT Log method is useful.
[Android Software/Hacking General [Developers Only]] aykut..:
nvram how is it done?
[Android Software/Hacking General [Developers Only]] Alex1948:
Benefits or...

Either I do not understand or does not explain well.

With these two methods that scatter file get?Same as with MTKDroid tool ?Which makes me in seconds and without many complications.

And , READ BACK , makes in 15 minutes, not hours.

Can you be more explicit, to understand the benefits.

From what I see and you collect, the script you , preloader , making and MTKDroid

if block != 'misc':

start = start + 0x600000

Eventually, you get scatter file, in my case , the one you have and with MTKDroid , this , see block info and image.:
[Android Software/Hacking General [Developers Only]] syserr:
I do recommend using MTKDroid... rua1 did a great job. In my post/thread I steer the general audience to MTK DRT, and from what I understand you got the same answer with MTKDroid, that is great. But if you want to know how to do it yourself, I describe 2 ways. I realize for most people, they don't care. I'm trying to spread knowledge, and gain knowledge.

A full "Read back", for me, has always been much slower than "Download." And for that matter "Write memory" has been much slower for me than "Download." Not sure which you are asking about the benefit of, but the full "Read back" on a cold OS is a very safe and complete backup. You don't have to construct a scatter file my way to follow the "Read back" backup method and dice up the whole ROM with a similar method. When you dice it up you are making an SPFT-style ROM you can give to others.

I'll respond to any more questions about this on the guide thread. I don't want to derail what this topic is about.
[Android Software/Hacking General [Developers Only]] Alex1948:
OK

OK, thanks will go on guide thread
[Android Software/Hacking General [Developers Only]] farazafs:
I tried but mobile run in background start and charging, getting info but not display.... Then after revert back everything working fine... but tell me how to permanent fixed NVRAM (invalid IMEI) issue?
[Android Software/Hacking General [Developers Only]] syserr:
This problem usually comes from a SP Flash Tool "Format". That is why it's important to backup the NVRAM portion before doing an SPFT Format, because the Format will write over with zeros the "NVRAM" block of flash.

MediaTek synchronizes the data in the NVRAM partition with the normal filesystem /data/nvram. So when people patch their IMEI it's usually just fixing /data/nvram. So when they flash a new ROM or do a Data Wipe, the /data/nvram doesn't exist and consequently the IMEI fix is gone too.

I think different ROMs behave differently. I have one 4.0.4 ROM for my device that seems to be able to write /data/nvram values up into the (previous blank) NVRAM partition. But I have a 4.0.3 ROM that refuses to push any changes in /data/nvram up.

The painful way to fix this permanently would be able to create your own NVRAM image block or hack an existing one directly, then write it with SPFT. This would be painful. We need a bounty collected for someone do this. :) It might not be too bad, if I had a week I bet I could do it unless the IMEI is encoded in a real weird way.

I spent hours watching the behavior of NVRAM and /data/nvram. Watching the kernel's first boot populate all the files in /data/nvram even when there is a blank NVRAM block. Calibration data is stored here other than the MEI... GPS config, brightness, volume. I speculate... Often people have trouble with these things after a SPFT Format because the kernel's first boot is not populating /data/nvram with the same initial values as the NVRAM partition would have had.

I understand this isn't the answer you wanted, but I suspect others on this thread can benefit from this general view of what is going on.

So you can try IMEI tools:

MTK Droid Root & Tools

MobileUncle

AT Command method -> http://xdaforums.com/showpost.php?p=46840514&postcount=619
[Android Software/Hacking General [Developers Only]] farazafs:
I have backup of everything, Already tried all methods u told, but still unlucky, I have bachup of SP Flash Tool NVRAM.bin and MTK Droid Tool Backup. One more interesting thing when I was tried to restore MTK Droid Tool It's gave me error /dev/pttycmd1 not found then I flash secro.bin image from Sp Flash Tool, files was shown but again I tried MTK Droid Tool with out error operation done but still no IMEI. I think there is no permanent solution still for that.... so my bad luck I was give on warranty claim.
[Android Software/Hacking General [Developers Only]] biobio76:
issue with backup of my clone S4 mini GT-9190 6572

Hi Dear Rua & all,

posting today because I am having an issue trying to generate the dump backup , folder " !Files_to_FlashTool"

well, trying to backup the rom of my y9190 mtk6572, the backup goes (supposably) just fine with mtkdroid tools 2.4.8 B:

see what I got step by step:

ATTENTION! Requests for confirmation on the device screen are possible!

--- root shel it is received temporarily before reboot !

--- scatter is write to the file:

C:\Users\biobio\Desktop\cloni smartphone\MINI\test\MT6572_Android_scatter.txt

--- The preservation folder on the computer: C:\Users\biobio\Desktop\cloni smartphone\MINI\test\MTKdroidTools_v248b\backups\GT-I9190_131111_backup_131128-095412\

--- In phone files will remain in the folder: /mnt/sdcard/clockworkmod/backup/131128-095412/

--- scatter is write to the file:

C:\Users\biobio\Desktop\cloni smartphone\MINI\test\MTKdroidTools_v248b\backups\GT-I9190_131111_backup_131128-095412\MT6572_Android_scatter.txt

--- We keep blocks:

- preloader.bin

- nodl_pro_info

- nvram.bin

- userdata_nvram_only..img

- userdata_nvram_only..tar

- nodl_protect_f.yaffs2.img

- nodl_protect_s.yaffs2.img

- nodl_seccnfg

- uboot.bin

- boot.img

- recovery.img

- nodl_secro.bin

- nodl_misc

- logo.bin

- nodl_expdb

- system.img

- cache.img

- data.img

--- task is complete ---

THEN, I press on TO PREPARE BLOCKS FOR FLASH TOOL and here what I got:

--- Check and copying of files in the folder: C:\Users\biobio\Desktop\cloni smartphone\MINI\test\MTKdroidTools_v248b\backups\GT-I9190_131111_backup_131128-095412\!Files_to_FlashTool\

-- preloader.bin: md5 OK; ... it is copied ... cut OK

-- nodl_pro_info: md5 OK;

-- nvram.bin: md5 OK;

-- userdata_nvram_only..img: md5 OK; unyaffs ...ERROR , The yaffs2 format isn't defined

-- userdata_nvram_only..tar: md5 OK;

-- nodl_protect_f.yaffs2.img: md5 OK;

-- nodl_protect_s.yaffs2.img: md5 OK;

-- nodl_seccnfg: md5 OK;

-- uboot.bin: md5 OK; ... it is copied

-- boot.img: md5 OK; ... it is copied

-- recovery.img: md5 OK; ... it is copied

-- nodl_secro.bin: md5 OK;

-- nodl_misc: md5 OK;

-- logo.bin: md5 OK; ... it is copied

-- nodl_expdb: md5 OK;

-- system.img: md5 OK; unyaffs ...ERROR , The yaffs2 format isn't defined

-- cache.img: md5 OK; unyaffs ...ERROR , The yaffs2 format isn't defined

-- data.img: md5 OK; unyaffs ...ERROR , The yaffs2 format isn't defined

--- copying is complete ---

Can someone help me of this??

I have to say that the structure of the blocks and the scatter itself it's strange, maybe because it's running 6572 CPU and the device is quite different from others with cpu 6589 etc...

see below pictures of the BLOCKMAP I got with MTK Droid tool as well as a screenshot shwoing what there is inside the backup_folder on my pc supposed to be generated correctly....

never seen blocks like that....

appreciate if someone and especially RUA can provide some suggestions how to solve it...
[Android Software/Hacking General [Developers Only]] alifuk:
Hi, I have a similar problem - Kernerl block map pmt mismatch. I have uploaded the MTKdroid tools information here

http://xdaforums.com/showthread.php?p=47931280#post47931280

Can you help Please?
[Android Software/Hacking General [Developers Only]] PrimeMax:
Well i didnt get the above prblm but faced the unmatching of scatter file frmat.so i have to use latest version of both mtk tools as well of sp flash tool,means mainly depends upon the version used of mtk tools fr backing up and have to use sp flash tool of same time.

Hope dis wud wrk.

:D