Hi, Guest! Login / Register




Thread Rating:
  • 1 Vote(s) - 4 Average
  • 1
  • 2
  • 3
  • 4
  • 5

[Please help] Issues making Stock ROM Backup using MTKdroid and SP flash tools

#11

(05-28-2016, 02:50 PM)Rajneesh Wrote: Oh!

Any ways, going back to the backup created using SP flash tools readback, and mtk droid:

5,718,01 ----- 3G-7271-HD70_141105__boot_patched_160518-201438.img


6,416,384 ----- 3G-7271-HD70_141105__recovery_160518-201438.img

16,777,216 ------ factory_NONmodified_recovery.img

The last file is the default recovery of device whose size is 16Mb and the 2nd file is CWM recovery but the size is 6Mb 

Can I downdoad the small file with CWM recovery through SP Flash and that wont brick the device?

If not, then I can then create the backup of my Stock ROM, with CWM recovery, correct?

From all results, it seems Mtk droidtools isn't fully compatible with your phone...unless some programs on your PC are interfering with MTK droidtools. A common example is an ADB clash (https://forum.hovatek.com/thread-10111.html).
I would advise you try MTK Droid tools on a different PC....just to be sure.

Down to your recovery images. its normal to have one recovery image being 6MB and another being 16MB; yet, both working fine. 16MB is the maximum size your device's recovery partition can take and will thus likely be the size of recovery.img when you do a readback using SP flash tool.
You should be able to flash the CWM recovery image using SP flash tool without a problem so far its for your phone model.
You can also backup your phone in recovery mode once its on CWM recovery (not stock recovery)


Reply
#12
(05-29-2016, 06:33 AM)hovatek Wrote:
(05-28-2016, 02:50 PM)Rajneesh Wrote: Oh!

Any ways, going back to the backup created using SP flash tools readback, and mtk droid:

5,718,01 ----- 3G-7271-HD70_141105__boot_patched_160518-201438.img


6,416,384 ----- 3G-7271-HD70_141105__recovery_160518-201438.img

16,777,216 ------ factory_NONmodified_recovery.img

The last file is the default recovery of device whose size is 16Mb and the 2nd file is CWM recovery but the size is 6Mb 

Can I downdoad the small file with CWM recovery through SP Flash and that wont brick the device?

If not, then I can then create the backup of my Stock ROM, with CWM recovery, correct?

From all results, it seems Mtk droidtools isn't fully compatible with your phone...unless some programs on your PC are interfering with MTK droidtools. A common example is an ADB clash (https://forum.hovatek.com/thread-10111.html).
I would advise you try MTK Droid tools on a different PC....just to be sure.

Down to your recovery images. its normal to have one recovery image being 6MB and another being 16MB; yet, both working fine. 16MB is the maximum size your device's recovery partition can take and will thus likely be the size of recovery.img when you do a readback using SP flash tool.
You should be able to flash the CWM recovery image using SP flash tool without a problem so far its for your phone model.
You can also backup your phone in recovery mode once its on CWM recovery (not stock recovery)

Thanks a ton for replying in Admin.

You know what, YOU NAILED IT!!

The moment you said adb clash, I remember seeing two adb tasks running in my Task Manager, (whenever I killed mtkdroid).

I uninstalled pdanet, rebooted the PC and the moment I connect my device and start Mtkdroid tools, the Adb brothers come up in the Task manager, one remains other keeps on playing hide & seek i.e. coming and going. I have only one folder with adb in it which is Mtk_Droid_Tool_v2.5.3d\adb and they both are running from the same folder. I started my backup and killed one of the brothers, and whoa the mtkdroid started creating all the files on my device in within 10 seconds, it copied 110 Mbs of those.

But that was a temporary solution. I would get rid of the another adb, reinstall using your link, come back and report to you Sir.

Regards,

Rajneesh
Reply
#13
(This post was last modified: 05-29-2016, 02:40 PM by mensa. )
(05-28-2016, 02:50 PM)Rajneesh Wrote:
(05-28-2016, 01:56 PM)X3non Wrote:
(05-28-2016, 01:24 PM)Rajneesh Wrote: ...
When I connect the device via USB mass storage, the copying speed is around 4.5mb/s.  My PC RAM is 4Gb, 2.9 Ghz CPU

seems like your device isnt fully compactible with mtk droid tools
you'd have to use the rom dump you made using the readback method

Oh!

Any ways, going back to the backup created using SP flash tools readback, and mtk droid:

5,718,01 ----- 3G-7271-HD70_141105__boot_patched_160518-201438.img


6,416,384 ----- 3G-7271-HD70_141105__recovery_160518-201438.img

16,777,216 ------ factory_NONmodified_recovery.img

The last file is the default recovery of device whose size is 16Mb and the 2nd file is CWM recovery but the size is 6Mb 

Can I downdoad the small file with CWM recovery through SP Flash and that wont brick the device?

If not, then I can then create the backup of my Stock ROM, with CWM recovery, correct?
I don't see anything wrong with it. It won't brick your phone if the CMW recovery is designed specially for your phone. you can go ahead.
Reply
#14
(05-29-2016, 11:23 AM)Rajneesh Wrote:
(05-29-2016, 06:33 AM)hovatek Wrote:
From all results, it seems Mtk droidtools isn't fully compatible with your phone...unless some programs on your PC are interfering with MTK droidtools. A common example is an ADB clash (https://forum.hovatek.com/thread-10111.html).
I would advise you try MTK Droid tools on a different PC....just to be sure.

Hi Admin,

Now I am in a fix. I was able to remove the clash by installing adb drivers from scratch. So after going in the folder and typing adb devices, it shows me my device name i.e.

C:\adb>adb devices
List of devices attached
0123456789ABCDEF device

I can confirm the device ID on usbdeview as well. However, what happens is that with the device connected, when I run mtk droid tools, adb.exe comes up in the Task Manager. After going in root.backup.recovery, when I press the Backup button, another adb.exe comes up in the task manager. After viewing it in the Resource monitor I can see the second adb.exe is in a wait chain and continues to sit there. (screen shot attached)

Now on the device the same thing happens with the preloader_dsp file i.e. it is being copied down very slowly (starting from 2.00 Mb) (as mentioned in my first post). If I kill one adb.exe from the task manager, it manages to get past the preloader_dsp and continues the process further and the mtkdroid completes the task.

Now, what is happening is if I immediately kill the adb.exe soon after starting the backup, the file size of preloader_dsp comes to around 2030 Mbs. However, if I wait for lets say 30 minutes and then kill the adb.exe file, the file size increases accordingly.

Hence the files that are ultimately prepared for SP flash tools are:

Files created directly via MTK Droid tools and prepared for SP Flash tools.(!Files_to_FlashTool)

16,777,216 boot.img
512 EBR1
512 EBR2
393,216 lk.bin
3,145,728 logo.bin
512 MBR
7,631 MT6582_Android_scatter.txt
119,176 preloader.bin
16,777,216 recovery.img
6,291,456 secro.img
1,073,741,824 system.img

Files created via SP flash tools ROM_0, converted by MTK droid tools for SP flash tools -> Download

16,777,216 boot.img
512 EBR1
512 EBR2
3,145,728 logo.bin
512 MBR
524,288 misc
7,631 MT6582_Android_scatter.txt
119,176 preloader.bin
16,777,216 factory_NONmodified_recovery.img
6,291,456 secro.img
1,073,741,824 system.img

As one can see, the file sizes are exactly the same except that the MTK droid tools did not create the below files.

10,485,760 protect_f
10,485,760 protect_s
3,145,728 pro_info
131,072 seccfg
22,020,096 bmtpool
5,242,880 nvram.bin
393,216 uboot.bin
132,120,576 cache.img
4,294,967,296 data.img
10,485,760 expdb

And therefore, after going in the SP flash tools, loading the scatter file, I can see all the options Checked except Cache, userdata (because they were not backed up)

MY OBSERVATIONS
===============

As mentioned above:

Observation 1
-------------
Scenario 1 - After killing the adb.exe file immediately after running backup, the file size of preloader_dsp was 2030 Mbs.
Scenaria 2 - After killing the adb.exe file after 30 minutes of running backup, the file size of preloader_dsp was 3088 Mbs.

However it did not matter in the end because the preloader.bin created by Mtk droid tool, for (!Files_to_FlashTool) was of same size in both the scenarios i.e. 119,176 bytes.

Observation 2
-------------
I used 3 fresh PCs to get rid of the another adb.exe file from task manager, but was not able to, and in the end, killing one, did not adversely have any effect.

Observation 3
-------------
Both the backups of Stock ROM using Readback in SP Flash tools AND Mtk droid tools MATCHED.

QUESTION 1
----------
After the task was successfully created by MTK droid and all the files copied to my PCs HDD, there are still 4 files that are left by the Mtk droid tools, in path sdcard0/clockworkmod/backup/xxxxxxxxxx/

nandroid.md5
system.ext4.tar
recovery.img (obvious)
boot.img (obvious)

but, What are the first two files, the Nandroid and system.ext4.tar and whats their use?

QUESTION 2
----------
As you mentioned in your post, "You should be able to flash the CWM recovery image using SP flash tool without a problem so far its for your phone model."
How do I know whether the CWM recovery image is for my phone model, because MTK droid created it?

QUESTION 3
----------

In the SP flash tools, before downloading the Stock ROM to my device, what all are the options I should not Check apart from the preloader?

Thank you so much in advance, as well reading this lengthy post.

Kind Regards,

Rajneesh

Attachments:
1. Resource Monitor showing status of 2nd adb.exe
2. USBDeview: Showing my Device status, drivers installed etc.
3. Log of Beginning to End of Stock ROM creation of MTK Droid tools.
4. Status of SP Flash Tools after creation of (!Files_to_FlashTool) by MTK Droid tools.

Attached Files
.jpg   resource.JPG (Size: 76.14 KB / Downloads: 4)
.txt   selected items.txt (Size: 3.48 KB / Downloads: 2)
.txt   log of final process of mtk.txt (Size: 7.26 KB / Downloads: 2)
.jpg   sp flash.JPG (Size: 95.45 KB / Downloads: 4)
Reply
#15
(05-30-2016, 04:29 PM)Rajneesh Wrote: ...
Attachments:
1. Resource Monitor showing status of 2nd adb.exe
2. USBDeview: Showing my Device status, drivers installed etc.
3. Log of Beginning to End of Stock ROM creation of MTK Droid tools.
4. Status of SP Flash Tools after creation of (!Files_to_FlashTool) by MTK Droid tools.

question1: system.ext4.tar is the same as system.img containing the system partition files
nandroid.md5  checksum file used by CWM recovery
in summary the entire folder is a CWM backup (its not entirely useful since you have the MTK backup)

question2: since mtk droid tools created the image then it should work fine. you can flash using rashr apk or with sp flash tools +  the scatter file

question3: when downloading/flashing the rom, if the phone is totally bricked ie dead you would have to flash all files including preloader. 
Reply
#16
(This post was last modified: 05-31-2016, 01:00 PM by Rajneesh. Edit Reason: Update )
(05-31-2016, 12:24 AM)X3non Wrote:
(05-30-2016, 04:29 PM)Rajneesh Wrote: ...
Attachments:
1. Resource Monitor showing status of 2nd adb.exe
2. USBDeview: Showing my Device status, drivers installed etc.
3. Log of Beginning to End of Stock ROM creation of MTK Droid tools.
4. Status of SP Flash Tools after creation of (!Files_to_FlashTool) by MTK Droid tools.

question1: system.ext4.tar is the same as system.img containing the system partition files
nandroid.md5  checksum file used by CWM recovery
in summary the entire folder is a CWM backup (its not entirely useful since you have the MTK backup)

question2: since mtk droid tools created the image then it should work fine. you can flash using rashr apk or with sp flash tools +  the scatter file

question3: when downloading/flashing the rom, if the phone is totally bricked ie dead you would have to flash all files including preloader. 


Thanks X3non,

So you agree and approve that:

1. The process as explained, went fine and the file preloader especially thus created  despite adb.exe chaos is Ok?

2. I can go ahead flashing the cwm recovery created earlIer with SP flash tools, is for my device and I can use it?

3. Refering my 1st post, out of the 2 files below,

5,718,016 3G-7271-HD70_141105__boot_patched_160518-201438.img

6,416,384 3G-7271-HD70_141105__recovery_160518-201438.img

which file has the cwm recovery?

4. In case of any issues, I can flash my 

16,777,216 factory_NONmodified_recovery.img

file to restore back my stock recovery?

I will be waiting for a green signal from your side, after which I will go through with flashing the CWM recovery, please

Edit: An update, I have tried installing CWM through ROM Manager app, but it says your device is currently not supported, have you tried installing CWM manually?
Reply
#17
(05-31-2016, 05:09 AM)Rajneesh Wrote: Thanks X3non,

So you agree and approve that:

1. The process as explained, went fine and the file preloader especially thus created  despite adb.exe chaos is Ok?

2. I can go ahead flashing the cwm recovery created earlIer with SP flash tools, is for my device and I can use it?

3. Refering my 1st post, out of the 2 files below,

5,718,016 3G-7271-HD70_141105__boot_patched_160518-201438.img

6,416,384 3G-7271-HD70_141105__recovery_160518-201438.img

which file has the cwm recovery?

4. In case of any issues, I can flash my 

16,777,216 factory_NONmodified_recovery.img

file to restore back my stock recovery?

I will be waiting for a green signal from your side, after which I will go through with flashing the CWM recovery, please

Edit: An update, I have tried installing CWM through ROM Manager app, but it says your device is currently not supported, have you tried installing CWM manually?

1. The process went fine
2. Since the recovery.img was backed up from your phone and you could boot into recovery mode then the recovery image should work fine. Mind you, dont make the mistake of thinking it is a CWM (custom) recovery. If you hadn't ported a custom recovery to the phone then it will still be stock recovery
3. 3G-7271-HD70_141105__boot_patched_160518-201438.img is a patched boot.img while 3G-7271-HD70_141105__recovery_160518-201438.img is your recovery.img. If you had ported CWM using MTK Droid tools then it should have flashed CWM recovery to your phone. try booting into recovery and list what you see; this will tell us if your phone is still running on stock recovery or CWM has been successfully ported
4. Exactly. just rename it to recovery.img
5. ROM manager might not support your phone. try the proceure @ https://forum.hovatek.com/thread-455.html
Reply
#18
(06-03-2016, 12:50 PM)hovatek Wrote: 1. The process went fine
2. Since the recovery.img was backed up from your phone and you could boot into recovery mode then the recovery image should work fine. Mind you, dont make the mistake of thinking it is a CWM (custom) recovery. If you hadn't ported a custom recovery to the phone then it will still be stock recovery
3. 3G-7271-HD70_141105__boot_patched_160518-201438.img is a patched boot.img while 3G-7271-HD70_141105__recovery_160518-201438.img is your recovery.img. If you had ported CWM using MTK Droid tools then it should have flashed CWM recovery to your phone. try booting into recovery and list what you see; this will tell us if your phone is still running on stock recovery or CWM has been successfully ported
4. Exactly. just rename it to recovery.img
5. ROM manager might not support your phone. try the proceure @ https://forum.hovatek.com/thread-455.html

Thanks Hovatek

3. I couldn't port this CWM recovery into the phone and still have my Stock ROM recovery in my phone.

In the SP Flash tools:
While trying to flash my recovery through SP flash tools, it says "PMT changed for the ROM, it must be downloaded" and aborts the process.

I found some youtube videos explaining me to format + Do a firmware upgrade on my device with all the Check boxes on the SP Flash tools selected and it will solve the issue.

https://youtu.be/B0D43U-ppx8 and https://youtu.be/XfIK-LHW6Zk

But did not use the solutions as shown in the videos.

In MTK Droid Tools:
While flashing CWM recovery through MTK Droid Tools -> root.backup.recovery -> To choose the boot.img file or To use boot from phone -> Recovery and Boot it gave me a dialog box:

"Attention! There is a probability to damage the boot block!..... If phone isn't loaded, it is necessary to flash this file through FlashTool! Install Patched boot to phone?" Yes or No?

To which I clicked No and the operation aborted.

But the video link you gave me proved really helpful.

Although you did not cover this error in your video, but you said just click YES on every prompt thereafter.

Therefore using Boot.img from file (created with MTK droid tool), I clicked Yes Yes & Yes and BINGO!

The phone was flashed with CWM recovery rua1 autoCWM v5.5.0.4 for 3G 7271-HD70. I booted into CWM recovery and have taken the backup of my ROM and copied them to my PC. The files created are:

239,813,120 .android_secure.vfat.tar
16,777,216 boot.img
19,456 cache.ext4.tar
521,130,496 data.ext4.tar
346 nandroid.md5
16,777,216 recovery.img
2,560 sd-ext.ext4.tar
862,431,744 system.ext4.tar

which are certainly my Stock ROM Backup, which I can use in future to restore my Stock ROM using CWM right?

Thanks a lot Hovatek, X3non for your kind help in solving my issues. The videos posted by you Hovatek on Youtube are excellent and were really helpful in making me learn the concept.

Thanks a lot once again.

With Warm Regards,

Rajneesh

Attachment : Final log of patching CWM recovery with MTK Droid tools using boot.img from file

Attached Files
.txt   final log.txt (Size: 9.32 KB / Downloads: 1)
Reply










Users browsing this thread:
1 Guest(s)