-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Guidance on sp9832e_1h10_gofu (Connected but receive 7e ver expected error) #6
Comments
This is the command sent to the phone:
|
Try running Please note that |
I am suspecting an issue with FDL1, which well, I don't know, but how did you get the firmware? I cannot find it online anywhere. Either way, my FDL1 address is 0x5500 (notice the 2 fives not one), so if you are pulling a random FDL1, then I can try to build the FDL1 myself and send it to you with the modification. I do have the leaked BSP source code though I cannot re-share it online, to prevent me from getting DMCAs. However, if FDL1 source code is highly demanded I can try to send it out, but then again, DMCA. |
Thanks for the quick response. I've updated the description to provide additional details. @ilyakurdyukov yes I was running spd_dump about 5-10 seconds before entering boot mode (which requires the battery to be removed and reinserted whilst holding the volume down key). Perhaps I'll try some various combinations and timeouts. Do you have any suggestions? @CE1CECL Original firmware was a Original:
I have attached my original fdl1 and fdl2 from above and some of the interesting configuration files (flash.cfg, PAX_Android_scatter.txt) if you are interested. Regarding the FDL1 address I pulled this from the |
Update: On further experimentation it appears I now have device connectivity by running I then used Running a similar command as before I get a lot more output but still receive an error as mentioned in the documentation already: verbose 0:
verbose 2:
|
0x2d means BSL_CMD_READ_PARTITION (this command lists partitions)
Try other commands, your device may be too old and support fewer commands. |
Thanks @ilyakurdyukov that appeared to be the problem! My device had issues with a number of commands (In this case it was I can now read:
Writing back the same
However, taking another smaller signed image
My only challenge now is the vbmeta and signing bypass. Write appears to also fail when I write a magisk patched image. |
You can try |
Do note that when you do the vbmeta bypass, you have to flash vbmeta first, before boot, else it will fail at the last sector |
Thanks @ilyakurdyukov my appears to not support the raw
I do however have access to the I guess it sounds like I need to work on getting this working for my device: TomKing062/CVE-2022-38694_unlock_bootloader#39 |
can you send your stock vbmeta an your attempted modified version? |
Sure, I followed the guide from: https://www.hovatek.com/forum/thread-32664.html with a basic script and some minor padding modifications. I've attempted both with and without flags (
There are two stock files (One from using Using I have attached stock, modified and the scripts I used in a vbmeta.zip file. |
Ill try to do it when i can but im having myself trying to reproduce it on my device, trying to flash back a full emmc backup with nothing but problems:
Cannot figure out what 0xa2 exactly is, anyone know? |
@BenEdridge I think I found your issue was with the python vb pad file that you had: https://github.com/CE1CECL/VBHelp/ |
Sorry late reply. Thanks for looking @CE1CECL I feel like perhaps I'm doing things the wrong way From above I can see you have It seems the key combination to enter "SPRD3" is incorrect or somehow this functionality is disabled. What keys do you use? |
I held down the volume down key, but it if i delete splloader & splloader_bak, it auto enters the same mode (it works better with battery removed but it didnt matter.) |
@BenEdridge I tested you VBMeta images in that zip (all this time later, I know) with this repo to see if it would have the private key changed, and sure enough, that hovatek guide won't work, the key was changed (unlike my C00070WW), meaning you probably won't be making strong integrity like I did (see: herzhenr/spic-android#12), unlock, or even boot Magisk or other images.
On my C0070WW (Stock) (It seems like the _key.bin files are changing on every OTA, and therefore, some of the keys are different on each OTA):
On my C0070WW (Rooted + super partition modded):
(I use this command to repack my rom when I need to change it):
Public Keys from vbmeta images (with this tool):
My Private & Public keys:
What should be YOUR private & public key (but is not, only here for reference):
|
Hi there, great project.
I've attempted running
spd_dump
on Ubuntu 22.04 with configuration for asp9832e_1h10_gofu
device and using signed fdl1 and fdl2 obtained from a firmware dump but having issues.I did the following:
spd_dump
before boot modeWhen using
spd_dump
I get the following error:This is similar to an issue raised earlier in: #2 but the differences is that
7e
appears to be related to the HDLC_HEADER. So my assumptions are that I'd need to modify the communications to the device or perhaps build a custom fdl that suits the device?Any suggestions or help would be much appreciated. Thanks.
I've also attached the BMA Configuration file obtained during a a flash.
sp9832e_1h10_xml.txt
The text was updated successfully, but these errors were encountered: