http://www.mediafire.com/?j0anq7kfe...ajlhunt3jras6,c92jlnxd3vdngn8,i6hqic38gc4h68d
system is ext4 image, can be mounted with mount -o loop in linux or by utilizing latest version of ext3 driver ( 0.51 ) for windows.
Can me give someone the WLAN widget with the GPS think in?
Gesendet von meinem R800i
is it the system dump from xperia s...?????
is it dump? real one?
Sent from my X10i using XDA App
works on xperia arc s ?
download, extract, sin2img, mount, get files
Sent from my X10i using XDA App
how you get this ...??????
can someone help me with this Im stuck on mounting the annoying img file
tatit1011 said:
can someone help me with this Im stuck on mounting the annoying img file
Click to expand...
Click to collapse
you can unpack it without mounting, by using unyaffs : http://code.google.com/p/unyaffs/
It says broken image file, can someone upload the xperia S system folder? Thanks
can you provide the binaries you are using to unpack this ?
1- extrating with 7zip : Ok, there are 3 .sin files
2- sin2img I already had : Crash
3- I tried an other version : Ok ... but the .img file size is exactly the same as the .sin ...
4- unyaffs : Crash !
So I think I don't have the good binaries ...
Thanks
sambastrakan said:
can you provide the binaries you are using to unpack this ?
1- extrating with 7zip : Ok, there are 3 .sin files
2- sin2img I already had : Crash
3- I tried an other version : Ok ... but the .img file size is exactly the same as the .sin ...
4- unyaffs : Crash !
So I think I don't have the good binaries ...
Thanks
Click to expand...
Click to collapse
THIS IS NOT YAFFS THIS IS EXT4
JUST MOUNT THE IMG IN LINUX AS EXT 4
(i hav not.done myself, I'm jus saying)
Sent from my X10i using XDA App
I also tried to mount the .img in DiskInternals Linux Reader without success. Until today it was working for any image available in xda-dev... so I think there is something special with these images ...
I will try directly in Linux to see ...
thx.
I can confirm it's not working.
Latest sin2img version gives a FileStream.Seek ArgumentException "Attempted seeking before the beginning of the stream.".
An older version creates an img file the same size as the sin, but unyaffs crashes with a segmentation fault / core dump and:
[email protected]:~$ dmesg | tail
[44637.019046] unyaffs[18031]: segfault at 1adb2b2c0 ip 0000000000400a08 sp 00007fffba023ca0 error 4 in unyaffs[400000+1000]
Click to expand...
Click to collapse
No mounting either, 'cause:
[email protected]:~$ sudo mount -t ext4 -o loop system.img /mnt/mountpoint/
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
[email protected]:~$ dmesg | tail
[44678.194165] EXT4-fs (loop0): VFS: Can't find ext4 filesystem
Click to expand...
Click to collapse
So, wasted time, I guess...
zdzihu has some tool to extract the package try that one. I think it's called auip.exe
ShyamSasi said:
zdzihu has some tool to extract the package try that one. I think it's called auip.exe
Click to expand...
Click to collapse
Thanks, but no luck with that one either. It keeps telling me the page size is wrong (tried with all three options)
Code:
[email protected]:~$ ./aIUP
aZuZu - Direct SIN / YAFFS Image Unpacker, v1.03.5. (c) aZuZu. 2011.
usage adiup [System.Img OR System.Sin] [Page Size] [Directory]
page size is one of 2048, 4096, 8192. - Sorry to lazy to encode auto detect. ;)
Tip: Directory - directory will be created if doesn't exist.
Supported: SE System.SIN files & Android System.IMG files.
[email protected]:~$ ./aIUP system.sin 4096 test/
UnPacking system.sin to test/ ...
Error: Page size parameter is wrong.
done.
[email protected]:~$ ./aIUP system.sin 2048 test/
UnPacking system.sin to test/ ...
Error: Page size parameter is wrong.
done.
[email protected]:~$ ./aIUP system.sin 8192 test/
UnPacking system.sin to test/ ...
Error: Page size parameter is wrong.
done.
Same for the .img file.
crimilde said:
Thanks, but no luck with that one either. It keeps telling me the page size is wrong (tried with all three options)
Code:
[email protected]:~$ ./aIUP
aZuZu - Direct SIN / YAFFS Image Unpacker, v1.03.5. (c) aZuZu. 2011.
usage adiup [System.Img OR System.Sin] [Page Size] [Directory]
page size is one of 2048, 4096, 8192. - Sorry to lazy to encode auto detect. ;)
Tip: Directory - directory will be created if doesn't exist.
Supported: SE System.SIN files & Android System.IMG files.
[email protected]:~$ ./aIUP system.sin 4096 test/
UnPacking system.sin to test/ ...
Error: Page size parameter is wrong.
done.
[email protected]:~$ ./aIUP system.sin 2048 test/
UnPacking system.sin to test/ ...
Error: Page size parameter is wrong.
done.
[email protected]:~$ ./aIUP system.sin 8192 test/
UnPacking system.sin to test/ ...
Error: Page size parameter is wrong.
done.
Same for the .img file.
Click to expand...
Click to collapse
What is your page files size? Those 3 are just examples. You need to find the page file of your PC.
ShyamSasi said:
What is your page files size? Those 3 are just examples. You need to find the page file of your PC.
Click to expand...
Click to collapse
Ah ok, sorry.
It's :
[email protected]:~$ getconf PAGESIZE
4096
Click to expand...
Click to collapse
Which I had already tried.
crimilde said:
Ah ok, sorry.
It's :
Which I had already tried.
Click to expand...
Click to collapse
I'll download it and try it today.
ShyamSasi said:
I'll download it and try it today.
Click to expand...
Click to collapse
yap please sone one fine a way to unpack it .......... ????
i am waiting too for it
How to Make a full backup ROM for MT6592,MT6589, MT6582, MT6577, MT6575, MT6572, MT6516 phones. This is basically for all MTK phones from MediaTek.
This is also a great way to share your firmware with someone who may need the stock ROM for their bricked phone. Or if you're the bricked one, you can direct someone with the same phone as you to this tutorial so they can prepare their ROM for you.
Important: Make sure to accept any SuperSU or SuperUser permission requests your phone may ask for while you're doing these steps. Any firewall requests your PC may have installed, also allow.
The tutorial will show you how to:
- make a full backup of your ROM (firmware)
- make the ROM firmware ready for SP Flash Tools
Click to expand...
Click to collapse
What you need:
- A rooted MTK phone
- BusyBox (can be downloaded from Google Play)
- MTK Droid Tools v2.5.0 Download Here
- ADB drivers Download Here or Here(so your computer can communicate with your rooted phone)
Click to expand...
Click to collapse
A) Prepare your phone and get the utilities we'll need
1. Enable debugging mode on your phone. From your homescreen, tap the Menu button > Settings > Development. Tap 'Debug Mode' and make sure it's checked.
2. Install BusyBox. Go to Google Play and search 'BusyBox' and install.
3. Install PDANet ADB Drivers. Download from here. Run the download and follow the instructions. A USB cable is required to connect your phone to your PC. After installing the drivers, keep your phone connected.
4. Download MTK Droid Tools 2.5.0 and extract to a known location on your PC.
Click to expand...
Click to collapse
B) Open ADB prompt to begin communication with the phone
1. Go into the extracted MTK Droid Tools folder from step 4 and right-click on 'MTKdroidTools.exe'. Select 'Run as administrator'.
2. Wait several seconds while MTK Droid Tools communicates with your phone. You'll eventually see the main screen come up with all of your phone's information. Look in the bottom left hand corner of the main window, you should see a green square. If it's yellow, you can try to click the 'root' button in MTK Droid Tools to get temporary root shell. If this doesn't work, and you've already got CWM, alternatively you can boot into CWM and then the little square should be green.
Click to expand...
Click to collapse
C) Read back the ROM with MTK Droid Tools
1. Go back to the main menu of MTK Droid Tools and select the 'Root, Backup, Recovery' tab.
2. Click the 'Backup' button. You will see MTK Droid Tools start to read all the data from your phone Smile. This can take awhile. So let it do it's thing. Have a coffee, whatever.
3. After it's finished reading back the ROM, another window will pop up asking you if you'd like to compress the image. Better to select 'Yes'. This will save space and make it into one tight package. MTK Droid Tools will then pack it up into a zip and then let you know it's finished.
İmage
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
D) Prepare the data from MTK Droid Tools for SP Flash Tools
1. In the MTK Droid Tools 'root, backup, recovery', you will a button that says 'To prepare blocks for Flash Tool'. Click it.
2. A new explorer window will open directly to the backups folder that MTK Droid Tools made. Select your phone's backup folder. It will look something like *your phone*-backup-YYMMDD. Open this folder.
3. Inside your phone's backup folder, you will see a file called 'files.md5'. Select this and the process will start Smile
4. This will take a while. Go have another coffee or shot of whiskey, smoke a joint. Whatever your like.
5. After it's finished, open the folder where you extracted MTK Droid Tools. There you will see a folder called 'backup'. Open this folder, then open the folder for your phone (*your phone*-backup-YYMMDD). There will be a folder called '!Files_to_FlashTool'. That's the folder to use for flashing with SP Flash Tools! Smile
Click to expand...
Click to collapse
This Guide can be Found on Chianaforums, but i poste specialy becuse of many Q700/Q700i users still unkown from this
Credit:-
@yuweng , @rua1 still don't know who is the developer of this app, if anything missing PM me :highfive:
Click to expand...
Click to collapse
Please rate the thread 5stars For support And Press thanks Too
Rather not thank you for a guide that's been done a hundred times already.
Sent from my A1-810 using XDA Premium HD app
KieranFoot said:
Rather not thank you for a guide that's been done a hundred times already.
Sent from my A1-810 using XDA Premium HD app
Click to expand...
Click to collapse
i know here and there lots of,,
but i think you woun't read the the last few lines
Ok, I'm going to avoid flaming, but shouldn't you have just posted a link to the original with a statement saying you had found it helpfull...
I'm all for information dispersal, but just copying annoys me.
Also, on a rooted device, I wouldnt use MTKDroidTools/SPFlashTool, I'd just use dumchar, dd and gzip to do it on the command line.
Also, it's bad advice to use the root function of MTKDroidTools as it will soft brick S-On devices.
Sent from my A1-810 using XDA Premium HD app
KieranFoot said:
Ok, I'm going to avoid flaming, but shouldn't you have just posted a link to the original with a statement saying you had found it helpfull...
I'm all for information dispersal, but just copying annoys me.
Also, on a rooted device, I wouldnt use MTKDroidTools/SPFlashTool, I'd just use dumchar, dd and gzip to do it on the command line.
Also, it's bad advice to use the root function of MTKDroidTools as it will soft brick S-On devices.
Sent from my A1-810 using XDA Premium HD app
Click to expand...
Click to collapse
i don't have any regret that what i am doing ,, if you don't think its helpful or coped then use the Report button and END this conversion
Here is how to backup your device for those more interested in how it works.
Now, let me say before we begin that this won't be as simple as using MTKDroidTools to create the backup, but as we will read and compress as we go using a gzip stream, it should be faster.
Before the backup can be made you need to find out a bit of information about your device, you will need to find the partition table layout from either dumchar_info or the scatter file distributed inside android update/rom packages.
Here is my dumchar_info (/proc/dumchar_info) from my Acer Iconia A1-810 (MTK6589i) device.
Code:
preloader 0x0000000000c00000 0x0000000000000000 2 /dev/misc-sd
mbr 0x0000000000080000 0x0000000000000000 2 /dev/block/mmcblk0
ebr1 0x0000000000080000 0x0000000000080000 2 /dev/block/mmcblk0p1
pmt 0x0000000000400000 0x0000000000100000 2 /dev/block/mmcblk0
pro_info 0x0000000000300000 0x0000000000500000 2 /dev/block/mmcblk0
nvram 0x0000000000500000 0x0000000000800000 2 /dev/block/mmcblk0
protect_f 0x0000000000a00000 0x0000000000d00000 2 /dev/block/mmcblk0p2
protect_s 0x0000000000a00000 0x0000000001700000 2 /dev/block/mmcblk0p3
seccfg 0x0000000000020000 0x0000000002100000 2 /dev/block/mmcblk0
uboot 0x0000000000060000 0x0000000002120000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x0000000002180000 2 /dev/block/mmcblk0
recovery 0x0000000000a00000 0x0000000002780000 2 /dev/block/mmcblk0
sec_ro 0x0000000000600000 0x0000000003180000 2 /dev/block/mmcblk0p4
misc 0x0000000000080000 0x0000000003780000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000003800000 2 /dev/block/mmcblk0
expdb 0x0000000000a00000 0x0000000003b00000 2 /dev/block/mmcblk0
android 0x0000000040000000 0x0000000004500000 2 /dev/block/mmcblk0p5
cache 0x000000002bc00000 0x0000000044500000 2 /dev/block/mmcblk0p6
usrdata 0x000000033a220000 0x0000000070100000 2 /dev/block/mmcblk0p7
bmtpool 0x0000000001500000 0x00000000ff3f00a8 2 /dev/block/mmcblk0
As you can see it gives you the block device used for the partition and the size and start of the position on that device.
Sent from my A1-810 using XDA Premium HD app
KieranFoot said:
Here is how to backup your device for those more interested in how it works.
Now, let me say before we begin that this won't be as simple as using MTKDroidTools to create the backup, but as we will read and compress as we go using a gzip stream, it should be faster.
Before the backup can be made you need to find out a bit of information about your device, you will need to find the partition table layout from either dumchar_info or the scatter file distributed inside android update/rom packages.
Here is my dumchar_info (/proc/dumchar_info) from my Acer Iconia A1-810 (MTK6589i) device.
Code:
preloader 0x0000000000c00000 0x0000000000000000 2 /dev/misc-sd
mbr 0x0000000000080000 0x0000000000000000 2 /dev/block/mmcblk0
ebr1 0x0000000000080000 0x0000000000080000 2 /dev/block/mmcblk0p1
pmt 0x0000000000400000 0x0000000000100000 2 /dev/block/mmcblk0
pro_info 0x0000000000300000 0x0000000000500000 2 /dev/block/mmcblk0
nvram 0x0000000000500000 0x0000000000800000 2 /dev/block/mmcblk0
protect_f 0x0000000000a00000 0x0000000000d00000 2 /dev/block/mmcblk0p2
protect_s 0x0000000000a00000 0x0000000001700000 2 /dev/block/mmcblk0p3
seccfg 0x0000000000020000 0x0000000002100000 2 /dev/block/mmcblk0
uboot 0x0000000000060000 0x0000000002120000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x0000000002180000 2 /dev/block/mmcblk0
recovery 0x0000000000a00000 0x0000000002780000 2 /dev/block/mmcblk0
sec_ro 0x0000000000600000 0x0000000003180000 2 /dev/block/mmcblk0p4
misc 0x0000000000080000 0x0000000003780000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000003800000 2 /dev/block/mmcblk0
expdb 0x0000000000a00000 0x0000000003b00000 2 /dev/block/mmcblk0
android 0x0000000040000000 0x0000000004500000 2 /dev/block/mmcblk0p5
cache 0x000000002bc00000 0x0000000044500000 2 /dev/block/mmcblk0p6
usrdata 0x000000033a220000 0x0000000070100000 2 /dev/block/mmcblk0p7
bmtpool 0x0000000001500000 0x00000000ff3f00a8 2 /dev/block/mmcblk0
As you can see it gives you the block device used for the partition and the size and start of the position on that device.
Sent from my A1-810 using XDA Premium HD app
Click to expand...
Click to collapse
dude.. Why to follow an odd and complicated backup method like yours when an easy tool like mtkdroidtool is available which can easily backup whole firmware and it is tested by several users which means it is reliable tool.
KieranFoot said:
Here is how to backup your device for those more interested in how it works.
Now, let me say before we begin that this won't be as simple as using MTKDroidTools to create the backup, but as we will read and compress as we go using a gzip stream, it should be faster.
Before the backup can be made you need to find out a bit of information about your device, you will need to find the partition table layout from either dumchar_info or the scatter file distributed inside android update/rom packages.
Here is my dumchar_info (/proc/dumchar_info) from my Acer Iconia A1-810 (MTK6589i) device.
Code:
preloader 0x0000000000c00000 0x0000000000000000 2 /dev/misc-sd
mbr 0x0000000000080000 0x0000000000000000 2 /dev/block/mmcblk0
ebr1 0x0000000000080000 0x0000000000080000 2 /dev/block/mmcblk0p1
pmt 0x0000000000400000 0x0000000000100000 2 /dev/block/mmcblk0
pro_info 0x0000000000300000 0x0000000000500000 2 /dev/block/mmcblk0
nvram 0x0000000000500000 0x0000000000800000 2 /dev/block/mmcblk0
protect_f 0x0000000000a00000 0x0000000000d00000 2 /dev/block/mmcblk0p2
protect_s 0x0000000000a00000 0x0000000001700000 2 /dev/block/mmcblk0p3
seccfg 0x0000000000020000 0x0000000002100000 2 /dev/block/mmcblk0
uboot 0x0000000000060000 0x0000000002120000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x0000000002180000 2 /dev/block/mmcblk0
recovery 0x0000000000a00000 0x0000000002780000 2 /dev/block/mmcblk0
sec_ro 0x0000000000600000 0x0000000003180000 2 /dev/block/mmcblk0p4
misc 0x0000000000080000 0x0000000003780000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000003800000 2 /dev/block/mmcblk0
expdb 0x0000000000a00000 0x0000000003b00000 2 /dev/block/mmcblk0
android 0x0000000040000000 0x0000000004500000 2 /dev/block/mmcblk0p5
cache 0x000000002bc00000 0x0000000044500000 2 /dev/block/mmcblk0p6
usrdata 0x000000033a220000 0x0000000070100000 2 /dev/block/mmcblk0p7
bmtpool 0x0000000001500000 0x00000000ff3f00a8 2 /dev/block/mmcblk0
As you can see it gives you the block device used for the partition and the size and start of the position on that device.
Sent from my A1-810 using XDA Premium HD app
Click to expand...
Click to collapse
Do you have a complete tutorial on how to do this? plus commands to restore? This would be great for us Linux users, I have two of these phones coming in from china and have zero desire to use windows to back up and restore a android device.
I think I got it figured out, wont know for sure until I get my phones to test.
Anyway basically I just
cat /proc/dumchar_info
this gives me partition info, from there I dd partition contents to sdcard, example below is to pull your recovery.img from the info you posted.
to pull eg backup
dd if=/dev/block/mmcblk0 of=/sdcard/recovery.img bs=4096 count=2560 skip=10112
to restore
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0 bs=4096 seek=10112
vampirefo said:
Do you have a complete tutorial on how to do this? plus commands to restore? This would be great for us Linux users, I have two of these phones coming in from china and have zero desire to use windows to back up and restore a android device.
I think I got it figured out, wont know for sure until I get my phones to test.
Anyway basically I just
cat /proc/dumchar_info
this gives me partition info, from there I dd partition contents to sdcard, example below is to pull your recovery.img from the info you posted.
to pull eg backup
dd if=/dev/block/mmcblk0 of=/sdcard/recovery.img bs=4096 count=2560 skip=10112
to restore
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0 bs=4096 seek=10112
Click to expand...
Click to collapse
Yup, that's right
hello, i tried this with my MT6572 Device [Firefly S120 - Rebranded Cubot C11] i followed exactly as said, well not the coffee ones
and here is my log, notice the bolded and underlined letters, i need help thanks in advance
Code:
In system already available: Android Debug Bridge version 1.0.31
--->>> Connect to device <<<---
--- The preservation folder on the computer: C:\Users\Kristian Acel Cua\Desktop\MTK Droid Tool\backups\FIREFLY_S120_140117_backup_140520-075724\
--- In phone files will remain in the folder: /storage/sdcard0/clockworkmod/backup/140520-075724/
--- scatter is write to the file:
C:\Users\Kristian Acel Cua\Desktop\MTK Droid Tool\backups\FIREFLY_S120_140117_backup_140520-075724\MT6572_Android_scatter.txt
--- We keep blocks:
- preloader_and_dsp
- MBR
- EBR1
- nodl_pro_info
- nvram.bin
- userdata_nvram_only.tar
- nodl_protect_f.ext4.img
- nodl_protect_f.ext4.tar
- nodl_protect_s.ext4.img
- nodl_protect_s.ext4.tar
- nodl_seccfg
- lk.bin
- boot.img
- recovery.img
- secro.img
- nodl_misc
- logo.bin
- nodl_expdb
- system.ext4.img
[U][B] - system.ext4.tar - ERROR - tar: write error: No space left on device[/B][/U]
--- We keep folders contents copying on PC
- /data/nvram
- /system
--- We pack everything kept in archive: C:\Users\Kristian Acel Cua\Desktop\MTK Droid Tool\backups\FIREFLY_S120_140117_backup_140520-075724.zip
[U][B] --- task end with ERROR ---[/B][/U]
--- Check and copying of files in the folder: C:\Users\Kristian Acel Cua\Desktop\MTK Droid Tool\backups\FIREFLY_S120_140117_backup_140520-075724\!Files_to_FlashTool\
-- preloader_and_dsp: md5 OK; ... it is copied ... cut OK
-- MBR: md5 OK; ... it is copied
-- EBR1: md5 OK; ... it is copied
-- nodl_pro_info: md5 OK;
-- nvram.bin: md5 OK;
-- userdata_nvram_only.tar: md5 OK;
-- nodl_protect_f.ext4.img: md5 OK;
-- nodl_protect_f.ext4.tar: md5 OK;
-- nodl_protect_s.ext4.img: md5 OK;
-- nodl_protect_s.ext4.tar: md5 OK;
-- nodl_seccfg: md5 OK;
-- lk.bin: md5 OK; ... it is copied
-- boot.img: md5 OK; ... it is copied
-- recovery.img: md5 OK; ... it is copied
-- secro.img: md5 OK; ... it is copied
-- nodl_misc: md5 OK;
-- logo.bin: md5 OK; ... it is copied
-- nodl_expdb: md5 OK;
-- system.ext4.img: md5 OK; ... it is copied
--- copying is complete ---
--->>> Connect to device <<<---
xlSKYFiRElx said:
hello, i tried this with my MT6572 Device [Firefly S120 - Rebranded Cubot C11] i followed exactly as said, well not the coffee ones
and here is my log, notice the bolded and underlined letters, i need help thanks in advance
Code:
In system already available: Android Debug Bridge version 1.0.31
--->>> Connect to device <<<---
--- The preservation folder on the computer: C:\Users\Kristian Acel Cua\Desktop\MTK Droid Tool\backups\FIREFLY_S120_140117_backup_140520-075724\
--- In phone files will remain in the folder: /storage/sdcard0/clockworkmod/backup/140520-075724/
--- scatter is write to the file:
C:\Users\Kristian Acel Cua\Desktop\MTK Droid Tool\backups\FIREFLY_S120_140117_backup_140520-075724\MT6572_Android_scatter.txt
--- We keep blocks:
- preloader_and_dsp
- MBR
- EBR1
- nodl_pro_info
- nvram.bin
- userdata_nvram_only.tar
- nodl_protect_f.ext4.img
- nodl_protect_f.ext4.tar
- nodl_protect_s.ext4.img
- nodl_protect_s.ext4.tar
- nodl_seccfg
- lk.bin
- boot.img
- recovery.img
- secro.img
- nodl_misc
- logo.bin
- nodl_expdb
- system.ext4.img
[U][B] - system.ext4.tar - ERROR - tar: write error: No space left on device[/B][/U]
--- We keep folders contents copying on PC
- /data/nvram
- /system
--- We pack everything kept in archive: C:\Users\Kristian Acel Cua\Desktop\MTK Droid Tool\backups\FIREFLY_S120_140117_backup_140520-075724.zip
[U][B] --- task end with ERROR ---[/B][/U]
--- Check and copying of files in the folder: C:\Users\Kristian Acel Cua\Desktop\MTK Droid Tool\backups\FIREFLY_S120_140117_backup_140520-075724\!Files_to_FlashTool\
-- preloader_and_dsp: md5 OK; ... it is copied ... cut OK
-- MBR: md5 OK; ... it is copied
-- EBR1: md5 OK; ... it is copied
-- nodl_pro_info: md5 OK;
-- nvram.bin: md5 OK;
-- userdata_nvram_only.tar: md5 OK;
-- nodl_protect_f.ext4.img: md5 OK;
-- nodl_protect_f.ext4.tar: md5 OK;
-- nodl_protect_s.ext4.img: md5 OK;
-- nodl_protect_s.ext4.tar: md5 OK;
-- nodl_seccfg: md5 OK;
-- lk.bin: md5 OK; ... it is copied
-- boot.img: md5 OK; ... it is copied
-- recovery.img: md5 OK; ... it is copied
-- secro.img: md5 OK; ... it is copied
-- nodl_misc: md5 OK;
-- logo.bin: md5 OK; ... it is copied
-- nodl_expdb: md5 OK;
-- system.ext4.img: md5 OK; ... it is copied
--- copying is complete ---
--->>> Connect to device <<<---
Click to expand...
Click to collapse
i think in your case you should use latest mtk tools as mtk6572 is new
rajit said:
i think in your case you should use latest mtk tools as mtk6572 is new
Click to expand...
Click to collapse
thanks sir, but i already fixed that. my problem now is, mtk droid tools did not generate a backup image of ANDROID, USRDATA, and CACHE .. which is all needed in SPFT .. how can i fix it ? please ? thanks
xlSKYFiRElx said:
thanks sir, but i already fixed that. my problem now is, mtk droid tools did not generate a backup image of ANDROID, USRDATA, and CACHE .. which is all needed in SPFT .. how can i fix it ? please ? thanks
Click to expand...
Click to collapse
I hink you did not read ... mtk6572 has different base.. so the old mtkdroid tools cant generate backup as i am told that the path are diff. so if you are not using latest one no one could help you out
rajit said:
I hink you did not read ... mtk6572 has different base.. so the old mtkdroid tools cant generate backup as i am told that the path are diff. so if you are not using latest one no one could help you out
Click to expand...
Click to collapse
well, i tried the latest version sir. and even dared to test with the old versions too just to be sure lol .. still, no usrdata, android, and cache backups generated
xlSKYFiRElx said:
hello, i tried this with my MT6572 Device [Firefly S120 - Rebranded Cubot C11] i followed exactly as said, well not the coffee ones
and here is my log, notice the bolded and underlined letters, i need help thanks in advance
Code:
In system already available: Android Debug Bridge version 1.0.31
--->>> Connect to device <<<---
--- The preservation folder on the computer: C:\Users\Kristian Acel Cua\Desktop\MTK Droid Tool\backups\FIREFLY_S120_140117_backup_140520-075724\
--- In phone files will remain in the folder: /storage/sdcard0/clockworkmod/backup/140520-075724/
--- scatter is write to the file:
C:\Users\Kristian Acel Cua\Desktop\MTK Droid Tool\backups\FIREFLY_S120_140117_backup_140520-075724\MT6572_Android_scatter.txt
.........
- nodl_expdb
- system.ext4.img
[U][B] - system.ext4.tar - ERROR - tar: write error: No space left on device[/B][/U]
--- We keep folders contents copying on PC
- /data/nvram
- /system
--- We pack everything kept in archive: C:\Users\Kristian Acel Cua\Desktop\MTK Droid Tool\backups\FIREFLY_S120_140117_backup_140520-075724.zip
[U][B] --- task end with ERROR ---[/B][/U]
--- Check and copying of files in the folder: C:\Users\Kristian Acel Cua\Desktop\MTK Droid Tool\backups\FIREFLY_S120_140117_backup_140520-075724\!Files_to_FlashTool\
.................
--->>> Connect to device <<<---
Click to expand...
Click to collapse
I am not an expert but did you check the available free space on C: partition of your PC? It seems to me that "system.ext4.tar - ERROR - tar: write error: No space left on device" it referring to such an issue. This backup operations can require quite a space sometimes.
How Much time Does it Usually takes !
Hey Guyz i have starting backing up my Mtk Device And it took for abt 10 mins and yet its not finished ?
futurebreeze2014 said:
I am not an expert but did you check the available free space on C: partition of your PC? It seems to me that "system.ext4.tar - ERROR - tar: write error: No space left on device" it referring to such an issue. This backup operations can require quite a space sometimes.
Click to expand...
Click to collapse
... Also check your internal SD for free space as some of the backups can end up in cwm folder.
Sent from my NOA H42 using Tapatalk
---------- Post added at 07:13 PM ---------- Previous post was at 07:12 PM ----------
Vicky khan said:
Hey Guyz i have starting backing up my Mtk Device And it took for abt 10 mins and yet its not finished ?
Click to expand...
Click to collapse
It can last up to an hour depending of PC, used data and system space, etc.
xlSKYFiRElx said:
well, i tried the latest version sir. and even dared to test with the old versions too just to be sure lol .. still, no usrdata, android, and cache backups generated
Click to expand...
Click to collapse
I backup apps, userdata and cache with Titanium Backup. After a nandroid restore (e.g., CWM) Titanium Backup does the rest. Hope this helps.
Btw, Looking forward to your Firefly S120 (aka Cubot C11) custom ROMs
Hello,
This way doesn't work.
It needs to backup every data on the phone from root !
This way backup only the system folder... Then, every apps data are not saved.
i used FF to find a ota to download the lasted fullota to get oreo and i saw someone and check if was compatible and it said that i was, so i star download the ota from the system update option and after tried to install the ota it didn´t boot just stood on the eRecovery and i couldn´t do anything y tried to resest to factory and nothing, i couldn´t used the 3 bottons option with the firmware of my build number and nothing
i tried everything before i used the dc phoenix, my bootloader was locked as frp too so i couldn´t do much, i tried download the exact firmware that i was before install the OTA but nothing and i can´t either download the package from eRecovery, so my only option was dc phoenix tool
i bought 15 credits to use the dc phoenix tool to flash the firmware of my phone, everything went ok except for the verlist partion
the phone reboot in emui logo and after 5% it says installation failed,
I read about if i get an error from verlist i need to use the HCU client but like i said before i just bought the exact 15 credits to use the dc phoenix tool, i don´t know if i have to buy the 72 Hours license for unlimited all functions + DC Phoenix or i just need to charge some amount of credits to use the program to repair the vendor/country info or i have to do another thing o flash something else (sorry for my english)
Code:
Looking for a device in upgrade mode
No devices detected in upgrade mode
Looking for a device in fastboot mode
Device found: 6XTDU17601000028
17/8/2018 17:07:13 Starting to write device in FASTBOOT mode...
Device found: 6XTDU17601000028
IMEI: 864065030441586
Build number: :WAS-LX3C25B105
Product model: WAS-LX3
Extracting partition XLOADER...
Preparing file to write...
Writing XLOADER partition with file XLOADER
XLOADER partition UPDATE ...FAILED
Cannot get FBlock info from device
Activating backdoor: DONE
Extracting partition XLOADER...
Preparing file to write...
Writing XLOADER partition with file XLOADER
XLOADER partition UPDATE ...OK
Extracting partition FW_LPM3...
Preparing file to write...
Writing FW_LPM3 partition with file FW_LPM3
FW_LPM3 partition UPDATE ...OK
Extracting partition FASTBOOT...
Preparing file to write...
Writing FASTBOOT partition with file FASTBOOT
FASTBOOT partition UPDATE ...OK
Extracting partition MODEMNVM_UPDATE...
Preparing file to write...
Writing MODEMNVM_UPDATE partition with file MODEMNVM_UPDATE
MODEMNVM_UPDATE partition UPDATE ...OK
Extracting partition TEEOS...
Preparing file to write...
Writing TEEOS partition with file TEEOS
TEEOS partition UPDATE ...OK
Extracting partition TRUSTFIRMWARE...
Preparing file to write...
Writing TRUSTFIRMWARE partition with file TRUSTFIRMWARE
TRUSTFIRMWARE partition UPDATE ...OK
Extracting partition SENSORHUB...
Preparing file to write...
Writing SENSORHUB partition with file SENSORHUB
SENSORHUB partition UPDATE ...OK
Extracting partition FW_HIFI...
Preparing file to write...
Writing FW_HIFI partition with file FW_HIFI
FW_HIFI partition UPDATE ...OK
Extracting partition BOOT...
Preparing file to write...
Writing BOOT partition with file BOOT
BOOT partition UPDATE ...OK
Extracting partition RECOVERY...
Preparing file to write...
Writing RECOVERY partition with file RECOVERY
RECOVERY partition UPDATE ...OK
Extracting partition RECOVERY2...
Preparing file to write...
Writing RECOVERY2 partition with file RECOVERY2
RECOVERY2 partition UPDATE ...OK
Extracting partition DTS...
Preparing file to write...
Writing DTS partition with file DTS
DTS partition UPDATE ...OK
Extracting partition MODEM_FW...
Preparing file to write...
Writing MODEM_FW partition with file MODEM_FW
MODEM_FW partition UPDATE ...OK
Extracting partition CACHE...
Preparing file to write...
Erasing CACHE partition
Partition CACHE erased
Writing CACHE partition with file CACHE
CACHE partition UPDATE ...OK
Extracting partition SYSTEM...
Preparing file to write...
Writing SYSTEM partition with file SYSTEM
SYSTEM partition UPDATE ...OK
Extracting partition USERDATA...
Preparing file to write...
Erasing USERDATA partition
Partition USERDATA erased
Writing USERDATA partition with file USERDATA
USERDATA partition UPDATE ...OK
Software written
17/8/2018 17:17:31 Writing device finished OK
Waiting for fastboot device...
Device found: 6XTDU17601000028
Writing rescue_recovery partition with file recovery
rescue_recovery partition UPDATE ...OK
Looking for device in upgrade mode...
COM3: Android Adapter PCUI (COM3)
COM8: DBAdapter Reserved Interface (COM8)
17/8/2018 17:18:03 Starting to write device in UPGRADE mode...
File to update: Warsaw-L03_C25B101_Firmware_Colombia_CLARO_S.A._Android7. 0_EMUI5.1.APP
Validating file...
Looking for attached port...
Preparing to write...
Writing partition: SHA256RSA...OK
Writing partition: CRC...OK
Writing partition: CURVER...OK
Writing partition: VERLIST...
Error downloading file Warsaw-L03_C25B101_Firmware_Colombia_CLARO_S.A._Android7. 0_EMUI5.1_3.dtwork, partition: VERLIST
Error writing software
17/8/2018 17:18:40 Starting to write device in UPGRADE mode...
File to update: update_WAS-L03_C25B101_claro_la.APP
Validating file...
Looking for attached port...
Preparing to write...
Device does not support this update file
Error writing software
17/8/2018 17:19:16 Writing device finished with ERROR
Make sure you're flashing firmware approved for your phone, I recommend B206
davidhozic said:
Make sure you're flashing firmware approved for your phone, I recommend B206
Click to expand...
Click to collapse
This is my first huawei so i just download the exact firmware that appears on my information device, i´m from latin america and idk is the firmware that yo recommend me it will work for me
pcme_ said:
This is my first huawei so i just download the exact firmware that appears on my information device, i´m from latin america and idk is the firmware that yo recommend me it will work for me
Click to expand...
Click to collapse
You can also try to findthe right firmware on dc phoenix's formware site, there's a button in the program that takes you there