I am trying to backup my phone using MTK, but it ends with some errors... Can i still use use this, or what should i do?
This is what it says:
--- The preservation folder on the computer: C:\Users\...\MtkDroidTools v2.5.3\backups\V1_Viper_150122_backup_160110-121624\
--- In phone files will remain in the folder: /mnt/media_rw/sdcard0/clockworkmod/backup/160110-121624/
--- scatter is write to the file:
C:\Users\...\MtkDroidTools v2.5.3\backups\V1_Viper_150122_backup_160110-121624\MT6589_Android_scatter_emmc.txt
--- We keep blocks:
- preloader_and_dsp
- MBR
- EBR1
- nodl_pmt - ERROR : /dev/pmt: read error: Invalid argument
--- ERROR : no open file: C:\Users\....\MtkDroidTools v2.5.3\backups\V1_Viper_150122_backup_160110-121624\nodl_pmt
--- ERROR :Block PMT error
- nodl_pro_info
- nvram.bin
- userdata_nvram_only.tar - ERROR - : :Zero file, no space left on device!
--- We keep folders contents copying on PC
- /data/nvram
- /system
--- We pack everything kept in archive: C:\Users\....\MtkDroidTools v2.5.3\backups\V1_Viper_150122_backup_160110-121624.zip
--- task end with ERROR ---
Thanks
I am facing sAme error can somebody help to solve this error
Related
Hello community!
I tried to unlock bootloader on my mini pro, unsuccessfully, of course
Now I have some questions, just to make things clearer.
Followed instructions from guide on this forum.
USB debugging mode is enabled. Here is log:
process requires standard 2.x android firmware.
Press any key to continue . . .
Getting ROOT rights.
* daemon not running. starting it now *
* daemon started successfully *
670 KB/s (585731 bytes in 0.852s)
error: protocol fault (no status)
Waiting ...
Removing NAND MPU restrictions via SEMC backdoor. Permanent. Require ROOT rights
.
110 KB/s (3087 bytes in 0.027s)
- exec '/system/bin/sh' failed: No such file or directory (2) -
- exec '/system/bin/sh' failed: No such file or directory (2) -
- exec '/system/bin/sh' failed: No such file or directory (2) -
Waiting ...
Getting ROOT rights.
- exec '/system/bin/sh' failed: No such file or directory (2) -
Waiting ...
Writing patched semcboot. Two step process
First, we need get access to semcboot area
474 KB/s (8064 bytes in 0.016s)
- exec '/system/bin/sh' failed: No such file or directory (2) -
- exec '/system/bin/sh' failed: No such file or directory (2) -
Second, we need to write semcboot
546 KB/s (596916 bytes in 1.066s)
- exec '/system/bin/sh' failed: No such file or directory (2) -
- exec '/system/bin/sh' failed: No such file or directory (2) -
Press any key to continue . . .
I suppose my mistake was trying to unlock on non-srandard ROM (MiniCM7pro v10).
I do not understand role of PC Companion in whole process. Is it used just to check connection between phone and PC? Do I have to really connect to PC Companion enabling USB Storage?
Thanx!
a kind of answer here
of course do not reflash miniCM7 2.0.7 since it is not for pro
but the other steps should work
(-Reflash Eclair with SEUS
-Root with SuperOne Click
-Unlock bootloader)
BACKUP before anything else !!!
Thank you Mat, can you also clarify PC Companion question?
cheers!
gstipe said:
Thank you Mat, can you also clarify PC Companion question?
cheers!
Click to expand...
Click to collapse
PC compagnon is needed for one thing : a driver needed for flashtool
if you don't want to install PCcompagnon, you need to install the driver :
in flashtool folder, go to drivers and install "ggsetup-2.2.0.10.exe"
I have it installed already, so no problem. Now I know why is needed!
Thanks mate!
Hi!
My main aim is to root a china phone (symphony w67).
I made the scatter file, rom and stuffs. Now the problem I end up with is when I want to make the cwm recovery image using the Mtk Droid Tools. Here is the log:
--------------------------------------------------------------------------------------------------------------------------------------
--->>> Connect to device <<<--- --- The preservation folder on the computer: C:\Users\Adib\Desktop\MtkDroidTools v2.5.3\backups\W67_140811_ForFlashtoolFromReadBack _141029-124724\ --- scatter is write to the file:
C:\Users\Adib\Desktop\MtkDroidTools v2.5.3\backups\W67_140811_ForFlashtoolFromReadBack _141029-124724\MT6572_Android_scatter.txtcopying is complete
-- preloader.bin ...it is copied ... cut OK
-- MBR ...it is copied
-- EBR1 ...it is copied
-- pro_info ...it is copied
-- nvram.bin ...it is copied
-- protect_f ...it is copied
-- protect_s ...it is copied
-- seccfg ...it is copied
-- uboot.bin ...it is copied
-- boot.img ...it is copied
--- ERROR :No find KernelGZ
--- ERROR :No Split Boot Image
-- recovery.img ...it is copied
-- secro.img ...it is copied
-- misc ...it is copied
-- logo.bin ...it is copied
-- expdb ...it is copied
-- system.img ...it is copied
--- task is complete ---
------------------------------------------------------------------------------------------------------------------------------------------------
As u can see there are 2 errors:
--- ERROR :No find KernelGZ
--- ERROR :No Split Boot Image
and also no modified cwm recovery image is created in the backup folder. So may I please have some solution for this error? I became very desperate, been trying to root this device for 4 days.
Below are more details about the mobile if it helps in anyway:
Model number: W67
Android version: 4.4.2
Baseband version: MOLY.WR8.W1315.MD,WG.MP.V43, 2014/05/22 18:56
Kernel version: 3.4.67
Build number: W67_1_XXX_V01.0_V2.0_20140809
brother,,,
How to Root Symphony W67
i got the same error, maybe locked bootloader
Same error with a Mediatek D101_MB_V4
Android 4.4.2
Rocky oo7 said:
How to Root Symphony W67
Click to expand...
Click to collapse
Message me rocky, I can root w67
Adib254 said:
Hi!
My main aim is to root a china phone (symphony w67).
I made the scatter file, rom and stuffs. Now the problem I end up with is when I want to make the cwm recovery image using the Mtk Droid Tools. Here is the log:
--------------------------------------------------------------------------------------------------------------------------------------
--->>> Connect to device <<<--- --- The preservation folder on the computer: C:\Users\Adib\Desktop\MtkDroidTools v2.5.3\backups\W67_140811_ForFlashtoolFromReadBack _141029-124724\ --- scatter is write to the file:
C:\Users\Adib\Desktop\MtkDroidTools v2.5.3\backups\W67_140811_ForFlashtoolFromReadBack _141029-124724\MT6572_Android_scatter.txtcopying is complete
-- preloader.bin ...it is copied ... cut OK
-- MBR ...it is copied
-- EBR1 ...it is copied
-- pro_info ...it is copied
-- nvram.bin ...it is copied
-- protect_f ...it is copied
-- protect_s ...it is copied
-- seccfg ...it is copied
-- uboot.bin ...it is copied
-- boot.img ...it is copied
--- ERROR :No find KernelGZ
--- ERROR :No Split Boot Image
-- recovery.img ...it is copied
-- secro.img ...it is copied
-- misc ...it is copied
-- logo.bin ...it is copied
-- expdb ...it is copied
-- system.img ...it is copied
--- task is complete ---
------------------------------------------------------------------------------------------------------------------------------------------------
As u can see there are 2 errors:
--- ERROR :No find KernelGZ
--- ERROR :No Split Boot Image
and also no modified cwm recovery image is created in the backup folder. So may I please have some solution for this error? I became very desperate, been trying to root this device for 4 days.
Below are more details about the mobile if it helps in anyway:
Model number: W67
Android version: 4.4.2
Baseband version: MOLY.WR8.W1315.MD,WG.MP.V43, 2014/05/22 18:56
Kernel version: 3.4.67
Build number: W67_1_XXX_V01.0_V2.0_20140809
Click to expand...
Click to collapse
I have same problem
help with rooting and making cwm mtk6572
my phone is o+8.93 mtk6572 and was following this thread http://forum.xda-developers.com/showthread.php?t=2519432&page=2
but see this image here when using 1st step of droid root tool : i cant make scatter file why is this?
any help is much appreciated. i've been searching for rooting methods for a week a now
Getting This Error
--->>> Connect to device <<<---
--- task is complete ---
- Boot kernel version =3.4.67
It is created: D:\Android\MtkDroidTools v2.5.3\recovery\NOA-H41_140705__boot_patched_140907-000408.img
--- test recovery OK !
It is created: D:\Android\MtkDroidTools v2.5.3\recovery\NOA-H41_140705__recovery_140907-000408.img
--- ERROR :Recovery doesn't match by the size
--- task is complete ---
What do you use ?
It seems that Windows solution provided on XDA is not more updated from a lot of time ...
H930g - lgv30 - kdz extract - linux
wolfgart said:
What do you use ?
It seems that Windows solution provided on XDA is not more updated from a lot of time ...
Click to expand...
Click to collapse
Hello Dear Sir Wolfgart
If you are still looking for a tool , I can propose to you a Linux one : https://github.com/ehem/kdztools
(sorry it's not Windows , but with the help of a VirtualBox or even an Live CD, you should be able to perform this extraction)
Here are my command line output :
[email protected]:~/Android/kdztools-master$ ./unkdz -f H93011m_00_OPEN_EU_OP_1229.kdz -l
[!] Warning: Data between headers and payload! (offsets 826 to 83768)
[+] KDZ Partition List (format v2)
=========================================
0 : H93011m_00.dz (3563995785 bytes)
1 : LGUP_c.dll (3079120 bytes)
2 : LGUP_c.dylib (1229456 bytes)
[email protected]:~/Android/kdztools-master$ ./unkdz -f H93011m_00_OPEN_EU_OP_1229.kdz -x
[!] Warning: Data between headers and payload! (offsets 826 to 83768)
[+] Extracting all partitions from v2 file!
[+] Extracting H93011m_00.dz to kdzextracted/H93011m_00.dz
[+] Extracting LGUP_c.dll to kdzextracted/LGUP_c.dll
[+] Extracting LGUP_c.dylib to kdzextracted/LGUP_c.dylib
[+] Extracting extra data to kdzextracted/kdz_extras.bin
Unfortunately there is an error when I want to list the DZ file
[email protected]:~/Android/kdztools-master$ ./undz -f H93011m_00.dz -l
[!] Error: Value supposed to be zero in field "reserved5" is non-zero (0x5900)
Maybe you have an idea about this error or a tool that can extract the DZ ?
Just let me know
Regards
For windows I successfully used this one: https://forum.xda-developers.com/showthread.php?t=2600575
Could unpack the kdz, then the dz, and also create working (mountable) system images from all these system_xxxx.bin's.
Havent found a working one (atleast non that could create a system.img) for linux though :/
So apparently, I rooted my phone and have been using Xposed on my Stcok MIUI since a long time. But now recently, I installed the AEX Rom(Oreo) . The ROM is just great but now I just simply root my phone. Any suggestions/ ideas? The error has been given below:
Code:
**************
SuperSU installer
**************
- Mounting /system, /data and rootfs
- Extracting files
- Detecting system compatibility
- System-less mode, boot image support required
- Creating image
- Mounting image
- Creating paths
- Removing old files
- Placing files
**************
Boot image patcher
**************
- Finding boot image
--- Boot image: /dev/block/mmcblk0p21
- Extracting ramdisk
- Checking patch status
- Creating backup
- Patching sepolicy
--- Failure, aborting
Thread closed at OP request