Posts: 7
Threads: 1
Joined: Mar 2020
Reputation:
0
Hello, hovatek's stuff,
I tried to do the backup of my smart phone based on your guide from: https://www.hovatek.com/forum/thread-21970.html.
But, from some reason the SPFT (SP_Flash_Tool_v5.1924_Win) wasn't able to provide me a lenght of my EMMC memory, so I used the one from WwR's (WwR_2.51_Eng) ADB tab:
Brand: NUBIA; Model: NX575J;
Hardware: MT6755
Platform: mt6750
File system: EXT4
Android version: 6.0
Firmware version: 1538623647
Baseband version: NX575J_Z69_EN_4SQPN1MF10L110, 2018/10/04 11:25
Build number: alps-mp-m0.mp7-V3.54.1_nubia6750.66.m
Description: NX575J-user 6.0 MRA58K 1538623647 release-keys
Serial number: NR6TWW8SOF4SUSPV
Root: No
Full memory RAM: 0x76F26000 (1903 MB)
Full memory of ROM (EMMC_USER): 0xE8F800000 (59640 MB)
Full memory of ROM (EMMC_BOOT_1): 0x400000 (4 MB)
Full memory of ROM (EMMC_BOOT_2): 0x400000 (4 MB)
Full memory of ROM (EMMC_RPMB): 0x400000 (4 MB)
Full memory of the disk 1 (SD Card): 0x3A9000000 (14992 MB)
It was canceled by error message 0xC0010002.
I am not sure, if is it because of wrong length (0xE8F800000) of EMMC memory?
screenshot.564.png (Size: 42 KB / Downloads: 4)
Posts: 8,336
Threads: 189
Joined: Jun 2015
Reputation:
95
24-03-2020, 03:00 PM
(This post was last modified: 24-03-2020, 03:02 PM by xerxes.)
(24-03-2020, 11:38 AM)Yco Wrote: Hello, hovatek's stuff,
I tried to do the backup of my smart phone based on your guide from: https://www.hovatek.com/forum/thread-21970.html.
But, from some reason the SPFT (SP_Flash_Tool_v5.1924_Win) wasn't able to provide me a lenght of my EMMC memory, so I used the one from WwR's (WwR_2.51_Eng) ADB tab:
Brand: NUBIA; Model: NX575J;
Hardware: MT6755
Platform: mt6750
File system: EXT4
Android version: 6.0
Firmware version: 1538623647
Baseband version: NX575J_Z69_EN_4SQPN1MF10L110, 2018/10/04 11:25
Build number: alps-mp-m0.mp7-V3.54.1_nubia6750.66.m
Description: NX575J-user 6.0 MRA58K 1538623647 release-keys
Serial number: NR6TWW8SOF4SUSPV
Root: No
Full memory RAM: 0x76F26000 (1903 MB)
Full memory of ROM (EMMC_USER): 0xE8F800000 (59640 MB)
Full memory of ROM (EMMC_BOOT_1): 0x400000 (4 MB)
Full memory of ROM (EMMC_BOOT_2): 0x400000 (4 MB)
Full memory of ROM (EMMC_RPMB): 0x400000 (4 MB)
Full memory of the disk 1 (SD Card): 0x3A9000000 (14992 MB)
It was canceled by error message 0xC0010002.
I am not sure, if is it because of wrong length (0xE8F800000) of EMMC memory?
If you’re not sure of the length you use for full readback simply use the method https://www.hovatek.com/forum/thread-22701.html @ to get full length.
Or use miracle thunder @ https://www.hovatek.com/forum/thread-13347.html to perform backup.
Posts: 7
Threads: 1
Joined: Mar 2020
Reputation:
0
Miracle Thunder has been marked as potential threat with Trojan horse by NOD32. So, I won't use it.
However, I didn't say, the length is inaccurate. I had got a suspicious, only. But, I also told you, I used it from WwR's ADB tab. It is 59640 MB what is near to 64GB, Nubia N2 should have got it.
So, what might by another reason of described crash of EMMC validation? Thank you.
Posts: 7
Threads: 1
Joined: Mar 2020
Reputation:
0
This is Nubia N2's HW info:
Screenshot_2020-03-24-16-28-04.png (Size: 75.44 KB / Downloads: 6)
Posts: 7
Threads: 1
Joined: Mar 2020
Reputation:
0
I downloaded also "MTK Droid Root & Tools v2.5.3" and it writes me this:
--->>> Connect to device <<<---
--- ERROR : --- TotalBytesPerChunk Not Found. Set default Page/Spare=2048/64 !!!
--- Unknown ROM structure, backup NOT possible!
ATTENTION! File /system/recovery-from-boot.p which restore factory recovery in case of phone switching on in a normal mode Is Found!
--- task is complete ---
Maybe, it helps you to help me.
Posts: 22,066
Threads: 570
Joined: Jul 2014
Reputation:
332
(24-03-2020, 11:38 AM)Yco Wrote: ...But, from some reason the SPFT (SP_Flash_Tool_v5.1924_Win) wasn't able to provide me a lenght of my EMMC memory, so I used the one from WwR's (WwR_2.51_Eng) ADB tab:...
That's an alternative means to finding the full length of the emmc, i mean the info provided by wwr's adb tab. So nothing to worry about.
(24-03-2020, 11:38 AM)Yco Wrote: It was canceled by error message 0xC0010002
I am not sure, if is it because of wrong length of EMMC memory?
definitely not because of wrong length, i'd say it's either the USB connection got interrupted either by you or a mistake OR the size you're attempting to readback is too large (a full 58GB in length)
1. if all you need is the firmware of your device, ie you don't mind leaving out userdata (the partition containing files you stored on the device) then you can readback and skip both cache and userdata ; see the title on How to skip userdata and cache when dumping ROM using Wwr_MTK @ https://www.hovatek.com/forum/thread-22701.html
2. if you must readback including userdata, consider reading back in parts (from your failed screenshot, it passed 50% so you can attempt to readback half the length in size twice).
ie first readback
start address : 0x0
end address : 0x747C00000
second readback
start address : 0x747C00000
end address : 0xE8F800000
if successful on both counts, you should have two readbacks of about 29GB in size then concatenate (join) both files together (hxd hex editor can concatenate file, i'm not certain if it can work with extremely large file size, if it can't then you'll have to look for a software that can achieve this)
Posts: 22,066
Threads: 570
Joined: Jul 2014
Reputation:
332
(24-03-2020, 05:06 PM)Yco Wrote: I downloaded also "MTK Droid Root & Tools v2.5.3" and it writes me this:
...
mtk droid tools doesn't work on devices with new chipset type. it's basically useless for your device
Posts: 7
Threads: 1
Joined: Mar 2020
Reputation:
0
25-03-2020, 07:14 AM
(This post was last modified: 25-03-2020, 07:15 AM by Yco.)
[quote pid='188958' dateline='1585068048']
Hello, X3non,
Thank you for your confirmation regarding to EMMC size in WwR.
I don't think, the interruption was caused by USB connection, because of I tried it twice and it ended on the exact same place.
So, I could consider to divide it to two read backs, but it will be useless, if there will be no way, how to restore it then?
Can you send me a link with description, how to restore "large" image?
Thank you.
[/quote]
Posts: 7
Threads: 1
Joined: Mar 2020
Reputation:
0
25-03-2020, 07:31 AM
(This post was last modified: 25-03-2020, 07:32 AM by Yco.)
One more thing is there: Couldn't it be in a wrong preloader.bin file?
The issue is, that when I grabbed the scatter file I wasn't sure, if am I supposed to use MT6750 or MT6755 chipset because of this record in WwR ADB tab:
Hardware: MT6755
Platform: mt6750
So, I used MT6755, but it failed. Then I used MT6750, what worked and generated this scatter file:
#########################################__WwR_MTK_2.50__###################################################
#
# General Setting
#
#########################################__WwR_MTK_2.50__###################################################
- general: MTK_PLATFORM_CFG
info:
- config_version: V1.1.2
platform: MT6750
project: WwR_Testing
storage: EMMC
boot_channel: MSDC_0
block_size: 0x20000
############################################################################################################
#
# Layout Setting
#
############################################################################################################
- partition_index: SYS0
partition_name: PRELOADER
file_name: preloader.bin
is_download: true
type: SV5_BL_BIN
linear_start_addr: 0x0
physical_start_addr: 0x0
partition_size: 0x80000
region: EMMC_BOOT_1
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: BOOTLOADERS
reserve: 0x00
Related preloader has been generated for EMMC_BOOT_1 as well and I used it for read back.
But, its end address is 0x2daab, but it should be 0x400000 according to WwR ADB tab or 0x80000 (ROM_0) according to generated scatter file.
How is preloader.bin file connected to read back process? Thank you.
Posts: 7
Threads: 1
Joined: Mar 2020
Reputation:
0
25-03-2020, 08:23 AM
(This post was last modified: 25-03-2020, 09:03 AM by Yco.)
I tried to divide read back to two ones, as you suggested. 1st one went fine. 2nd one failed with error "STATUS_EXCEED_AVALIABLE_RANGE = 0xC004000B":
screenshot.566.png (Size: 43.32 KB / Downloads: 3)
|