Trouble backing up ROM on MT8163 with SPFT - BROM ERROR: S_DL_GET_DRAM_SETTING_FAIL
Trouble backing up ROM on MT8163 with SPFT - BROM ERROR: S_DL_GET_DRAM_SETTING_FAIL
(17-12-2020, 04:50 PM)legalpet I have an android managed device created by a company, for that company specifically. It's got a slimmed down version of android, and I cannot enable debugging, can't get online in any way, and pretty much can't do anything with it. It was meant to be used only with company kiosks. Anyways, it's pretty decent hardware and I'd like to use it. It's a tablet.
The tablet has a mediatek MT8163V chip. I generated a scatter file and followed all the steps found at this link:
https://www.hovatek.com/forum/thread-21970-page-15.html
However, I keep getting this error when I try Read Back with the SP Fash tool:
BROM ERROR: S_DL_GET_DRAM_SETTING_FAIL
It's as if the scatter file is incorrect. However, I generated the scatter file per the instructions in the link above, using WwR MTK version 2.51
Please help me out with some guidance as to what I can do. Thanks!
(18-12-2020, 05:52 AM)hovatek(17-12-2020, 04:50 PM)legalpet I have an android managed device created by a company, for that company specifically. It's got a slimmed down version of android, and I cannot enable debugging, can't get online in any way, and pretty much can't do anything with it. It was meant to be used only with company kiosks. Anyways, it's pretty decent hardware and I'd like to use it. It's a tablet.
The tablet has a mediatek MT8163V chip. I generated a scatter file and followed all the steps found at this link:
https://www.hovatek.com/forum/thread-21970-page-15.html
However, I keep getting this error when I try Read Back with the SP Fash tool:
BROM ERROR: S_DL_GET_DRAM_SETTING_FAIL
It's as if the scatter file is incorrect. However, I generated the scatter file per the instructions in the link above, using WwR MTK version 2.51
Please help me out with some guidance as to what I can do. Thanks!
Download MT8163 scatter file @ https://www.hovatek.com/forum/thread-12724.html and try using it to readback recovery partition. Do Not attempt to flash with this scatter file, its generic
(18-12-2020, 03:07 PM)legalpet ..
The one offered at the link you supplied has: partition_size: 0x40000
The one created by WwR has: partition_size: 0x80000
Is it possible that the partition size is off?? Could I try any other sizes that might work?
(19-12-2020, 03:26 PM)hovatek(18-12-2020, 03:07 PM)legalpet ..
The one offered at the link you supplied has: partition_size: 0x40000
The one created by WwR has: partition_size: 0x80000
Is it possible that the partition size is off?? Could I try any other sizes that might work?
I recommended that (generic) scatter file because the starting scatter wwr creates is just enough to dump preloader and PGPT.
This is why I asked you to attempt to readback ONLY recovery using the generic scatter file. Most (if not all) partitions will have different addresses but targeting recovery can help you discover the device's build number and search for a firmware online.
Share a full screenshot of SP flash tool when you get that error message. Use the wwr scatter file (for preloader dump) and generic scatter file for recovery dump)
(21-12-2020, 04:14 PM)legalpet First of all, thank you very much for your help.
I have taken screen-shots of what I’m doing. I broke the images down into Method #1 and Method #2.
Method #1 uses the method as you described, attempting to read-back only the recovery partition. I tried this method in two ways. One as is shown, with no recovery.img file. However, I also tried it with a TWRP recovery image file in the same directory as the scatter file, which gave the same error…
Method #2 uses the method described in your post explaining to read-back on the preloader partition, using the WwR scatter file.
As you can see, both methods give the same result.
Thanks again, any help/ideas are greatly appreciated.
(22-12-2020, 06:04 AM)hovatek(21-12-2020, 04:14 PM)legalpet First of all, thank you very much for your help.
I have taken screen-shots of what I’m doing. I broke the images down into Method #1 and Method #2.
Method #1 uses the method as you described, attempting to read-back only the recovery partition. I tried this method in two ways. One as is shown, with no recovery.img file. However, I also tried it with a TWRP recovery image file in the same directory as the scatter file, which gave the same error…
Method #2 uses the method described in your post explaining to read-back on the preloader partition, using the WwR scatter file.
As you can see, both methods give the same result.
Thanks again, any help/ideas are greatly appreciated.
Use Miracle Thunder v2.82 to dump your firmware in scatter format as explained @ https://www.hovatek.com/forum/thread-13347.html
Let me know how that goes
(22-12-2020, 03:24 PM)legalpet ..
EDIT: If I can pay you to troubleshoot this device and potentially come up with a solution, I'd be highly interested. If setting up something like this is possible, please notify me as to how we may arrange this. Thanks.
(22-12-2020, 03:24 PM)legalpet(22-12-2020, 06:04 AM)hovatek(21-12-2020, 04:14 PM)legalpet First of all, thank you very much for your help.
I have taken screen-shots of what I’m doing. I broke the images down into Method #1 and Method #2.
Method #1 uses the method as you described, attempting to read-back only the recovery partition. I tried this method in two ways. One as is shown, with no recovery.img file. However, I also tried it with a TWRP recovery image file in the same directory as the scatter file, which gave the same error…
Method #2 uses the method described in your post explaining to read-back on the preloader partition, using the WwR scatter file.
As you can see, both methods give the same result.
Thanks again, any help/ideas are greatly appreciated.
Use Miracle Thunder v2.82 to dump your firmware in scatter format as explained @ https://www.hovatek.com/forum/thread-13347.html
Let me know how that goes
Tried it with miracle box... It quickly said "Not Supported". I included a screen shot.
Could it be a driver issue?? I see a lot of posts saying to uninstall/reinstall drivers... But I already tried that, including disabling driver signature validation. Maybe I should try it on a different computer?? Or is that unlikely to help?
The android version is 8.1 oreo. Is it possible that the manufacturer built a secure boot chain that won't work with sp flash tool??
Thanks again.
EDIT: If I can pay you to troubleshoot this device and potentially come up with a solution, I'd be highly interested. If setting up something like this is possible, please notify me as to how we may arrange this. Thanks.
