Hovatek Forum MOBILE Android STATUS_PRELOADER_INVALID
Can't login? Please, reset your password.
Hovatek is recruiting! Apply Now


STATUS_PRELOADER_INVALID

STATUS_PRELOADER_INVALID

Aizawa Hikaru
Aizawa Hikaru
Aizawa Hikaru
Newbie
4
26-08-2021, 03:06 AM
#1



Hello, I am trying to use the temporary scatter file created by the WwR MTK tool to read back the preloader partition and got an error: STATUS_PRELOADER_INVALID

I uploaded my scatter file and error message,my device uses MT6761 CPU and 16GB EMMC storage
Attached Files
.txt
MT6761_Android_scatter.txt
Size: 1.01 KB / Downloads: 3
.png
ScreenShort-202108261005.png
Size: 22.92 KB / Downloads: 7
X3non
X3non
X3non
Recognized Contributor
22,062
26-08-2021, 10:38 AM
#2
(26-08-2021, 03:06 AM)Aizawa Hikaru Hello, I am trying to use the temporary scatter file created by the WwR MTK tool to read back the preloader partition and got an error: STATUS_PRELOADER_INVALID

I uploaded my scatter file and error message,my device uses MT6761 CPU and 16GB EMMC storage

for all new devices, you need to include preloader in the download tab before you'll be allowed to readback
you can use any preloader from the same phone model
Aizawa Hikaru
Aizawa Hikaru
Aizawa Hikaru
Newbie
4
26-08-2021, 02:08 PM
#3
(26-08-2021, 10:38 AM)X3non
(26-08-2021, 03:06 AM)Aizawa Hikaru Hello, I am trying to use the temporary scatter file created by the WwR MTK tool to read back the preloader partition and got an error: STATUS_PRELOADER_INVALID

I uploaded my scatter file and error message,my device uses MT6761 CPU and 16GB EMMC storage

for all new devices, you need to include preloader in the download tab before you'll be allowed to readback
you can use any preloader from the same phone model

Unfortunately, I cannot find any information about this device.

But when I tried to enable the advanced options in SPFlash, I successfully read a copy of EMMC_BOOT1 by switching to the SRAM option and extracted preloader.bin using WwR. I know that its EMMC_USER size is 0x3a3e00000. When I try to read back from 0x0 to 0x3a3e00000, SPFlash seems to stop working, and finally a 6MB file is output. The same is true for other partitions. It seems that only a part of the incomplete content can be extracted .
X3non
X3non
X3non
Recognized Contributor
22,062
27-08-2021, 11:11 AM
#4
(26-08-2021, 02:08 PM)Aizawa Hikaru Unfortunately, I cannot find any information about this device.

But when I tried to enable the advanced options in SPFlash, I successfully read a copy of EMMC_BOOT1 by switching to the SRAM option and extracted preloader.bin using WwR. I know that its EMMC_USER size is 0x3a3e00000. When I try to read back from 0x0 to 0x3a3e00000, SPFlash seems to stop working, and finally a 6MB file is output. The same is true for other partitions. It seems that only a part of the incomplete content can be extracted .

you can try skipping userdata and cache, see if it completes the readback ; see https://www.hovatek.com/forum/thread-22701.html
Aizawa Hikaru
Aizawa Hikaru
Aizawa Hikaru
Newbie
4
27-08-2021, 03:00 PM
#5



(27-08-2021, 11:11 AM)X3non
(26-08-2021, 02:08 PM)Aizawa Hikaru Unfortunately, I cannot find any information about this device.

But when I tried to enable the advanced options in SPFlash, I successfully read a copy of EMMC_BOOT1 by switching to the SRAM option and extracted preloader.bin using WwR. I know that its EMMC_USER size is 0x3a3e00000. When I try to read back from 0x0 to 0x3a3e00000, SPFlash seems to stop working, and finally a 6MB file is output. The same is true for other partitions. It seems that only a part of the incomplete content can be extracted .

you can try skipping userdata and cache, see if it completes the readback ; see https://www.hovatek.com/forum/thread-22701.html

I tried to follow what you said, skipping Userdata and Cache. At first, things seemed good, but when it came to about 450MB, SPFlash crashed again. I can see the timer keep increasing and hear the sound made by the hard disk writing, but the progress bar does not seem to move.

I can't stop it. After a while, it prompts an error as shown in the second picture.

I tried to use 7-Zip to decompress it, and I found that it seemed to be normal until 23.lk2. After 24.boot, all files showed errors like picture three...

This is really a headache!
Attached Files
.png
Picture.png
Size: 238.71 KB / Downloads: 4
.png
Picture-2.png
Size: 134.92 KB / Downloads: 3
.png
Picture-3.png
Size: 198.89 KB / Downloads: 3
Aizawa Hikaru
Aizawa Hikaru
Aizawa Hikaru
Newbie
4
27-08-2021, 04:11 PM
#6
(27-08-2021, 11:11 AM)X3non
(26-08-2021, 02:08 PM)Aizawa Hikaru Unfortunately, I cannot find any information about this device.

But when I tried to enable the advanced options in SPFlash, I successfully read a copy of EMMC_BOOT1 by switching to the SRAM option and extracted preloader.bin using WwR. I know that its EMMC_USER size is 0x3a3e00000. When I try to read back from 0x0 to 0x3a3e00000, SPFlash seems to stop working, and finally a 6MB file is output. The same is true for other partitions. It seems that only a part of the incomplete content can be extracted .

you can try skipping userdata and cache, see if it completes the readback ; see https://www.hovatek.com/forum/thread-22701.html

But when I try to read back Boot alone, there is no problem, which is very strange...
This post was last modified: 27-08-2021, 04:12 PM by Aizawa Hikaru.
X3non
X3non
X3non
Recognized Contributor
22,062
28-08-2021, 10:15 AM
#7
(27-08-2021, 03:00 PM)Aizawa Hikaru I tried to follow what you said, skipping Userdata and Cache. At first, things seemed good, but when it came to about 450MB, SPFlash crashed again. I can see the timer keep increasing and hear the sound made by the hard disk writing, but the progress bar does not seem to move.

I can't stop it. After a while, it prompts an error as shown in the second picture.

I tried to use 7-Zip to decompress it, and I found that it seemed to be normal until 23.lk2. After 24.boot, all files showed errors like picture three...

This is really a headache!

you could try the other fix for read_data_exception @ https://www.hovatek.com/forum/thread-439.html
if it still fails then try using a different pc


(27-08-2021, 04:11 PM)Aizawa Hikaru But when I try to read back Boot alone, there is no problem, which is very strange...

you'll be able to readback all smaller partitions if you do them alone but the large like system could be a problem
if all else fails, there's still another tactics you could use though, lets say you've readback all smaller partitions and you're left with system
take the partition size of system from the scatter file and divide it by say 300mb or 400mb, so lets say system begin addr is 0x0 and the length is say 2gb (the values within the scatter are in hex)
first readback item, start addr 0x0 , length (convert 300mb to hex)
second readback item, start addr of first readback which is 0x0 + 300mb in hex, length will still be 300mb in hex
...
last readback item, start addr of the previous item + 300mb in hex, length will be any leftover (it could be less than 300mb)

in essence you're reading back system all split up into a smaller size, and once successful, you only need to concatenate all the files together as system.img and you can use the same method to readback userdata but that'll be way more stressful considering userdata is usually 6x or more larger than system
Users browsing this thread:
 1 Guest(s)
Users browsing this thread:
 1 Guest(s)
YtWhTl
live chat
whatsapp telegram instagram