yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] Alex1948:
UBIFS

Right, [MENTION=5119815]rua1[/MENTION] is able to respond, but read what it says:

"On phones with ubifs file system (while meets on some MT6572)

Select Blocks Map in the program and look at the Type field opposite to block "system". If there is "ubifs", you got .

That it is possible to do with such phone in the program:

make scatter file

get root, install SU, delete unnecessary software

make a backup, but blocks except ubifs will be suitable

That it is impossible:

make CWM, it needs to be done with ubifs support

write boot through the program, it kills phone (while it is unclear why)

Download ubifs blocks from a program backup through FlashTool, it will kill a phone"

Sorry , that I mixed
[Android Software/Hacking General [Developers Only]] biobio76:
Hi Alex

i am not sure to have understood your message 100%...

anyway, I understood the difference is in phones ( most likely with 6572 ) that have ubif

well, if you look the pictures I posted above, you see my blockmap how looks like...

opposite to SYSTEM there is NOTHING on "type".....quite strange...

there is type: yaffs2 opposite to protect_f and protect_s instead....

there is no blocks with ext4

so basically don't know what to do here....

I have also tried to create my "own" custom CWM...but mtk droid tool failed generating it...and I am not able to find out a custom CWM who can be used on this clone mini S4

before using mtk droid tool for the backup, i have tried to make a DUMP using READBACK function of SPFT.....well, I got the scatter with MTK Droid tool, I open the scatter and MODIFIED it REMOVING all (__NODL_ ) becasue I know otherwise SPFT READBACK is not starting...

with the new scatter I created I run READBACK putting as started 0x00000000 and as "lenght" of whole ROM the field 17 ( USERDATA ) basically: 0x126C0000

as suggested for 6572 cpu, I have used SP_Flash_Tool_v3.1320.0.174 and readback started correctly and without errors.....I got the ROM_0 file in more or less 3 minutes, total size 294MB...a little bit un-usual comparing with other readback where you get usually 2GB file and takes 45 minutes...

I tried to exctract the ROM_0 I got with MTK Droid tool 2.4.8B still using my "modified" scatter, and the exctraction was successfully, but honestly I am afraid to try flash it back on phone since I don't know where to find a stock rom for this strange version of mini s4 and I have actually no way to create CWM and I am not sure the backup I have is working in the end.....
[Android Software/Hacking General [Developers Only]] syserr:
The first thing I'd be cautious about is not reading all the flash on a new device that we/you don't know much about. If you read only length 0x126C0000, then you will only get PRELOADER through CACHE, you won't get USERDATA.

If you want to get a full dump, begin at 0x0 and length 0x1f5c0000. This is start of USERDATA plus it's length. So in the end you will get PRELOADER through USERDATA.

You asked me how you know your backup is good. Well, I'd make sure ROM_ is large, if you read size of 0x1f5c0000... that is 501MB. That seems small for a super modern phone, but numbers don't lie. Another way is to look at things with a hex editor. I use an old one called Tiny Hexer. If you look at the start address of BOOT or RECOVERY, those should have a signature that is consistent -- both start with "ANDROID!" in the block. A hex editor may not like to open a file 501MB, so you could dice it up like this with dd:

dd if=ROM_ of=RECOVERY bs=$(( 0x10000 )) skip=$(( 0x11c )) count=$(( 0x60 ))

Sorry ^ that command line relies on bash to expand out the hex to decimal which dd needs.

Normally, I would chop out SYSTEM (with dd) and try extracting it with simg2img or loopback mount it with Linux as type ext4... but you have UBIFS? I have no experience with it.. looks challenging... google how to mount UBIFS images.

But, I'd feel pretty confident you have a good read if you see the right size file and you find good things with a hex editor.

---------- Post added at 05:10 PM ---------- Previous post was at 05:04 PM ----------

I think you wrote "NVRAM.bin" with "Write memory" tab in SPFT to the right location? But you must Wipe Data directly after with Recovery so it rebuilds /data/nvram from your NVRAM partition. I'm not sure, you did that part.

Where did your NVRAM.bin come from? If it came from a running system (maybe with MTK DRT) it might not be a clean grab. If you read some MediaTek docs, they are "versioning" items etc.. it could mark things as dirty and then /data/nvram information looks better than what is in NVRAM to the algorithm.
[Android Software/Hacking General [Developers Only]] rua1:
@biobio76: I have not seen the file log.txt (and in my signature is written about it). But probably in the phone file system ubifs type. Now it is impossible to do a full backup. Be careful, only the factory firmware can be restored brick! I corrected the guide:

@All: Please do not trash in a thread: don't overquoting; hide screenshots and more text; follow the subject of this thread.
[Android Software/Hacking General [Developers Only]] Alex1948:
Sorry, I observed now – Type is : yaffs2 to [MENTION=5132793]biobio76[/MENTION] Block Info. - This is image Block Info posted by him - see

And on this account [MENTION=5119815]rua1[/MENTION] in post 630

“ATTENTION! It is possible to make a brick of phones with MTD (nand) type flash with yaffs2 or ubifs file systems.” – post 630

[MENTION=5132793]biobio76[/MENTION] read what it says [MENTION=5119815]rua1[/MENTION]

PS. In the second picture you see that two folders : ! Files_to_FlashTool(for flash with SPFT) and !Unpacked_Yaffs
[Android Software/Hacking General [Developers Only]] johnnyx83:
after i rooted my samsung mega clone "mtk6572" successfully , i pressed "blocks map" button

and it displays every thing but with the "create scatter file" button is UNAVAILABLE !!

what can i do ??!!
[Android Software/Hacking General [Developers Only]] rua1:
@johnnyx83: use v2.4.8b
[Android Software/Hacking General [Developers Only]] Alex1948:
For [MENTION=4796707]syserr[/MENTION]

I do not know what all you write here, Python, etc.start adress + lenght , I think we know how to add two numbers in base 16 , no other ....MTKdroid is a software that solves everything,In Python a script of yours, gives me error.

I posted a picture of treadh and you did not answer why(Or you can not quite explain , and we do not understand) - see image

Tks [MENTION=5119815]rua1[/MENTION] for MTKDroid.It is particularly and very good for MT65xx
[Android Software/Hacking General [Developers Only]] biobio76:
Hi Dear Rua1

thanks for your comment.

yes you right, forgot to post the log file on previous post..., please find it here attached now together with scatter file generated out of BlockMap, also both attached.

In this phone I am almost sure the file system is ubifs type so I understood that it's not possible to create "own" CWM using MTK Droid tool, I am wondering if there is some other way to create a working CWM to allow me to flash this phone in future or at leat to have / try to create from CWM a nandroidbackup ready to be installed back in case of mess with the phone....

MTK Droid Tool is not able to correctly prepare file_to_Flashtool....but I did a backup with it and I have it on PC as well as on MicroSD in the device.....are both backup something VALID that I can keep and use in the future in case of issue with this phone?? Or simply are backup that looks nice but that are not really valid?

The "readback" I did with SP Flash Tool was successfully, at least the ROM_ has been then extracted with 2.4.8 B and I also have this....

Just would like to understand if I can do something with the backup/readback I have...or simply need to ask seller to let me have the factory rom?? I asked him already 10 times but you know...this is quite hard to get .....

in case RUA you want me to send you my ROM_ file or my backup please let me know I can easily upload for you in case of testing or you want to try something new....

Thanks
[Android Software/Hacking General [Developers Only]] Alex1948:
MT6272

Sorry , [MENTION=5119815]rua1[/MENTION] -

2.4.8 , does not have this chipset MT6572

2,4.8b = MTKsocs = ^(MT65(16|72|73|75|77|82|89)|8135)

And SP Flash Tool , be careful which version you use

---------- Post added at 03:58 PM ---------- Previous post was at 03:50 PM ----------

I corrected myself and I wrote above ,

where you see ubi , he writes clearly - The yaffs2 format isn't defined

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

If you !Files_to_FlashTool You can make flash on the phone(with SPFT) - the picture looks like you

Can we explain to @ rua1 !

---------- Post added at 04:10 PM ---------- Previous post was at 03:58 PM ----------

That's what the write [MENTION=5119815]rua1[/MENTION]

in 630 post : see post

in case of non-standard splitting a flash on page/spare

The program does images of yaffs2 blocks with a standard ratio 2048/64. Other ratios of page/spare are non-standard and the program yet doesn't do the correct backup of such blocks!

How to learn page/spare ratio:

most reliable of a log BROM_DLL_V5.log from FlashTool. We look for there the line "nand_pagesize (". In it there will be a page value, in the following spare

page value can be learned having collected in a terminal window

Code:

adb shell cat /proc/yaffs

in the lines totalBytesPerChunk there will be a page value. Spare isn't known

indirectly from log.txt program or from the firmware.info file made during a backup. There will be lines approximately such

Code:

mtd11: 0c800000 00020000 "system"

value 00020000 in the 3rd column (erasesize) as a rule corresponds to 2048 page value. If there 00040000, page most likely 4096. And spare isn't known

If page = 4096 that as a rule spare =128, but meets and 224. From a backup made by the program, under Linux it is possible to rebuild yaffs2 files for non-standard a flash by means of yaffs2utils.

How to do:

Example on ubuntu. How to make of standard system.yaffs2.img the system.img file with the relation of 4096/128 system.img. If spare = 224, in line it is necessary to replace - s 128 on - s 224. Not to forget to copy before unyaffs2 the file from a backup in the yaffs2util/latest folder or to specify in the command a full path to it.

Code:

mkdir yaffs2util

cd yaffs2util

wget https://yaffs2utils.googlecode.com/files/latest.tar.gz

tar -xvf latest.tar.gz

cd latest

make

sudo mkdir system

sudo ./unyaffs2 --yaffs-ecclayout system.yaffs2.img system

sudo ./mkyaffs2 --yaffs-ecclayout -p 4096 -s 128 system system.img
[Android Software/Hacking General [Developers Only]] biobio76:
@ Alex

go here and read please when we discussed about my phone.....

http://xdaforums.com/showthread.php?p=47936392#post47936392

you will see that thanks to the help of another user He decompiled my "ORIGINAL RECOVERY" and posted the results......

ALSO, I run the ADB SHELL and the command He told me and here attached as picture you see what I got....

my phone has definitely a UBIFS file system
[Android Software/Hacking General [Developers Only]] Alex1948:
Right. At the same command in ADB me show not see ubifs - see image . I have a phone with chipset MT6572

I think this rule should teachers - [MENTION=5119815]rua1[/MENTION] and [MENTION=4796707]syserr[/MENTION] , me frankly beyond me.And I still learn from others

PS :Look what anyone says on the link that you posted and more and....

""Its a bit of luck, many do get a MT6572 with ext4 partition so i guess either you get another one with ext4 or just use it without CWM & NO custom ROMs for you.""

In other words, I think you got the phone that gives you headaches.
[Android Software/Hacking General [Developers Only]] Alex1948:
Great excuses for [MENTION=5119815]rua1[/MENTION].

It's thread and should talk about MTKDroid.Why do , not do and can help.

Tks
[Android Software/Hacking General [Developers Only]] rua1:
I wrote:

from your log:

29/11/13 13:50:57 /dev/ubi0_0 /system ubifs ro,relatime 0 0
29/11/13 13:50:57 /dev/ubi1_0 /data ubifs rw,nosuid,nodev,relatime 0 0
29/11/13 13:50:57 /dev/ubi2_0 /.cache ubifs rw,nosuid,nodev,relatime 0 0
29/11/13 13:50:57 /dev/ubi3_0 /fat ubifs rw,nosuid,nodev,relatime 0 0

yes ... yet you can still make a tar archive folder /system (the next version of the program will do it myself) and make yourself under linux as described here http://http://www.linux-mtd.infradead.org/faq/ubifs.html

But everything is difficult, it is not clear what the number should be entered in some places.

Thank you, not yet required. In Russian forum was a man with UBI phone and he is already working with me.

... cat /proc/filesystem only says what modules are included in the kernel. Use mount to determine the types of file systems.
[Android Software/Hacking General [Developers Only]] biobio76:
Thank dear Rua, it clear to me now....

I thank you again for the time spent in the creation of your great

Program that everybody use as one of the main tool for our phones with

MTK CPU

Keep going in developing my friend, you are the best!

In case any further test you want to do please consider myself at your

Complete disposal

Ciao from Italy
[Android Software/Hacking General [Developers Only]] imayoda81:
Another one from Italy, here to thank and just report that latest b version works flawlessly on new wave of fake star n9589 spreading here, with mt6572 soc.

Thanks a lot again mate, long live!!! :D
[Android Software/Hacking General [Developers Only]] syserr:
rua1, thank you for teaching us.

Is it just the ubifs grab from a running phone that is unusable?

Can you confirm a SP Flash Tool "Read back" of a ubifs partition/block would not break the phone? I assume it's not possible to break a phone with Read back.

If an SPFT read back gives a valid image, could SPFT "Write memory" or "Download" be used successfully?
[Android Software/Hacking General [Developers Only]] rexes13:
Hello rua! Thank you for your great tool!

I just downloaded but i can't seem to be able to read anything because of the encoding in the GUI texts!

Is there any way that i can change the default language?
[Android Software/Hacking General [Developers Only]] biobio76:
Hi syserr,

regarding you message I am also waiting RUA1 to reply, but in the meantime I can post my experience up to now.

I followed your suggestions:

QUOTE

..If you read only length 0x126C0000, then you will only get PRELOADER through CACHE, you won't get USERDATA.

If you want to get a full dump, begin at 0x0 and length 0x1f5c0000. This is start of USERDATA plus it's length. So in the end you will get PRELOADER through USERDATA.

UNQUOTE

I readback again using length 0x1f5c0000 and I got ROM_ around 501MB as you said

I have exctracted it and MTD Droid did it successfully without errors...the only error was when the program asked me if I want to create a CWM,

I press yes...but as RUA1 said then the recovery was not generated because doesn't suite the phone...

I have flashed back on the phone the BOOT.img and the RECOVERY.img I got from the exctraction and then the phone boot normally......

Of course I will not flash anything else, especially blocks with UBIFS that I know by RUA1 will "kil the phone"

BTW, please find the exctraction in full, I upload it for you and for all friend that want to have a look and maybe "play" with linux, script and all stuff I am too far from....

GT-I9190_131111_ForFlashtoolFromReadBack_131129-223530.rar ( TOT 207 MB )

https://mega.co.nz/#!c9gA1ZRQ!Y6FlNS3mlO-P_eJV1upC8XykdJ0lvyBKzzENvJQu4Fc

Appreciate syserr id you want to dice it up with your "dd" for me, and make some testing...I am at disposal of everybody who has script or linux knowhow and wanty to "play" a bit with it...I will be happy to make some test for you

I hope seller will fidn out my original firmware and finally let me have it....even if then I honestly did not understand yet if I can flash the original firmware "normally" by SP FLASH TOOL and /or should I do something different to restore my phone in case of future needs

Thanks
[Android Software/Hacking General [Developers Only]] rua1:
@syserr , @biobio76 :

ubifs too will be not valid on this step

@rexes13 http://forum.china-iphone.ru/post561435.html#p561435
[Android Software/Hacking General [Developers Only]] syserr:
I think maybe if you do a SPFT "Read back" this would give a valid ubifs image?
[Android Software/Hacking General [Developers Only]] johnnyx83:
my back up process seems to be endless ..

after making some files on my pc & phone it stops at system.ext4.img ..

see attachment below pls..
[Android Software/Hacking General [Developers Only]] bovirus:
[MENTION=5119815]rua1[/MENTION]

Many thanks for info (like changelog) about MTKdroidTools.

I checked some problems in italian translation (some lines missings/some terms not clear/right translated).

This is my proposal for italian language file and MTKdroidTools 2.4.7/2.4.8.
[Android Software/Hacking General [Developers Only]] Alex1948:
Read Back
[Android Software/Hacking General [Developers Only]] oscarblue48:
[MENTION=5266985]johnnyx83[/MENTION] make sure you have enough storage space on your device where backups are stored, looks to me as if you might be running out of space.
[Android Software/Hacking General [Developers Only]] swooby:
I recently purchased a Lenovo Yoga 10" Tablet (B8000).

It's specs say that it runs a MediaTek MT8125 CPU.

MTK Droid Root & Tools (v2.4.8) says the device runs a MT8389.

MediaTek seems to imply that the two chips are nearly identical: http://www.mediatek.com/_en/01_products/04_pro.php?sn=1085

I searched this thread for MT8125 and got no hits.

I searched this thread for MT8389 and got tons of hits.

I'm going to start skimming all of the posts in this thread, but has anyone successfully ported CyanogenMod (10.x or 11) to an MT8125/MT8389 device?

I have started to look in to this and am following the CM porting wikis.

I will be updating my github as I make progress:

https://github.com/paulpv/android_device_lenovo_b8000

There must be lots of MT8125/MT8389 devices out there, and theoretically if any of them can be made to run CM then they all can.

Lets get CM on these devices folks?

Who is the furthest along so far, and what help can we provide them?

Pv

---------- Post added at 09:17 PM ---------- Previous post was at 08:53 PM ----------

Can you please explain.

I have a Lenovo Yoga 10" Tablet (B8000) that the specs say has a MT8125 CPU.

MediaTek says the MT8125 and MT8389 are [nearly?] identical CPUs: http://www.mediatek.com/_en/01_products/04_pro.php?sn=1085

Are you saying that the SPFT tool calls the MT8125 and the MT8389 a "MT6589"?

Are they identical or just similar?

If a tool or technique works on an MT6589, does that also mean it will/should work on an MT8125 and/or MT8389?

To take this even further, does this mean that if a ROM is created to work on an MT6589, it will/should also work on an MT8125/MT8389?

Thanks!

Pv
[Android Software/Hacking General [Developers Only]] rua1:
can not share backup, containing userdata, there's your personal data!

if a very long time, it is necessary to interrupt and repeat. Often hangs thread process

Make a link to this post from OP? Then when you do the translation of new version adds to this post.

yes

I do not know, not much interested in

probably yes ... In any case, I have not reported the opposite

not much interested in
[Android Software/Hacking General [Developers Only]] biobio76:
RUA1,

thanks for this warning, I know it, and there is no personal data since I receive the phone and I never use it....

I am still in the phase trying to backu it up and create DUMP of it....

no account setup on phone, nothing.....

OK, in NVRAM you can pick up IMEI, but I can easily change it...i've got plenty of imei to use......

so appreciate your message anyway, but I am really afraid to start using the phone and have some mess later, and NOT BE able to restore anything since no CWM installed, and no DUMP due to this UBIFS partition...much more serious thing that and IMEI shared....

Hope RUA you can invent something in your next MTK Droid Tool relese....UBIFS is a serious issue for people like me who buy a phone suppose to get an EXT4 partition and be able to back up regularely the phone etc etc and then discover you are basically out of games ....

and I am afraid chinese wil put and use UBIFS partition in also next generation phones...so guys this can be the beginning of a serious problems

everybody can face in maybe two months....

Thanks
[Android Software/Hacking General [Developers Only]] Alex1948:
And of course , storage space.
[Android Software/Hacking General [Developers Only]] rua1:
v2.5.2

v2.5.2

Please do not place the file on other sites!
​

v2.5.2 is a bug fix for v2.5.1.

------------------------------------------------------------------------------------------------------

v2.5.1 is a bug fix for v2.5.0. Older added fix for backup flash emmc

---------------------------------------------------------------------------------------------------------

Сhanges v.2.5.0:

Running on Win 8.1

Support MT6572 and MT6582 (already in v2.4.8b)

Support phones MTD flash and different from the 2048/64 ratio Page/Spare. In the log window displays at a connection is an ratio. Because Spare determined intuitively, there is the probability of error definitions. Then the images will have to recompile under Linux.

if the file system ubifs, then a warning is displayed with reference to the index page with a description of the problem.

Cleaned checkboxes "Backup userdata and cache" and Leave "FlashTool files on SD card" (wrote about this plan recently).

Fixed bugs found

Previous bugfixes v2.5.0:

v2.5.0b -->

Bugfix for device with nonstandart MTD Page/Spare ratio

v2.5.0c -->

Bugfix for some device with nonstandart MTD Page/Spare ratio ​

Known unresolved problems v2.5.2:

doesn't make backup ubifs blocks

block secro incorrectly saves on some phones with MTD type flash if it is not mounted in the system

doesn't make scatter in a new format for 6582 and 6572 devices ( in development process)
[Android Software/Hacking General [Developers Only]] johnnyx83:
i'm using a 4GB class 4 toshiba sd card, that is also revealed in attachment #1 (sd : 2GB) free space ...

i will try to do it again a couple of times.

actually i made a backup using cwm recovery image (after installing it using same tool "MTKDroid") and successfully restored it .. ~754MB

but i want a robust backup to be restored on a pc even if the the phone not booting or has a corrupted ROM or bricked cwm ..

how can i use MTKDroid tool to do such a full backup or at least to flash only the cwm recovery image on a turned off phone just in case ..

because i want to try many custom ROM's and i afraid to loose my current system ..
[Android Software/Hacking General [Developers Only]] Alex1948:
Tks

Many thanks , [MENTION=5119815]rua1[/MENTION]
[Android Software/Hacking General [Developers Only]] oscarblue48:
[MENTION=5266985]johnnyx83[/MENTION] on my device the Mtkdroid backups are stored in the internal storage, (although its still called an sd card) not on the external card.
[Android Software/Hacking General [Developers Only]] Alex1948:
2.5.0

Very important and welcome these changes.

Tks.
[Android Software/Hacking General [Developers Only]] bovirus:
[MENTION=617394]rua[/MENTION]

Could you distribute the program archive as .ZIP (or .RAR) instead as .exe?

Could please include for the future in the program archive also other languages available (like italian)?

Thanks.
[Android Software/Hacking General [Developers Only]] anandmarar:
Link Doesn't work

Dear Sir,

Would like to bring to your notice that the download link doesn't work. Please recheck.

:)
[Android Software/Hacking General [Developers Only]] bovirus:
@ anandmarar

The link works perfectly!

Please don't post the entire previous post.

Just use the link to identify the link that didn't work. Like

v2.5.0 --> http://dfiles.ru/files/vdz2lejbs