Posts: 30
Threads: 2
Joined: Mar 2021
Reputation:
1
I am trying to root my tablet Duoduogo G20, which have a broad Beneve M1035SE_EEA. I try to search the firmware on web but no luck.
Now I am thinking of flash the tablet with the firmware of Teclast P10SE, which firmware can be download from Teclast official website.
These two tablet have the same CPU platform SC7731e, will that works?
Posts: 22,063
Threads: 570
Joined: Jul 2014
Reputation:
332
(07-04-2021, 04:59 AM)nheaven Wrote: I am trying to root my tablet Duoduogo G20, which have a broad Beneve M1035SE_EEA. I try to search the firmware on web but no luck.
Now I am thinking of flash the tablet with the firmware of Teclast P10SE, which firmware can be download from Teclast official website.
These two tablet have the same CPU platform SC7731e, will that works?
you'll only end up bricking your device, you'll be better off contacting the oem or vendor of the device for the firmware. maybe they can provide you with a link
Posts: 30
Threads: 2
Joined: Mar 2021
Reputation:
1
(07-04-2021, 10:09 AM)X3non Wrote: (07-04-2021, 04:59 AM)nheaven Wrote: I am trying to root my tablet Duoduogo G20, which have a broad Beneve M1035SE_EEA. I try to search the firmware on web but no luck.
Now I am thinking of flash the tablet with the firmware of Teclast P10SE, which firmware can be download from Teclast official website.
These two tablet have the same CPU platform SC7731e, will that works?
you'll only end up bricking your device, you'll be better off contacting the oem or vendor of the device for the firmware. maybe they can provide you with a link
I already flash my tablet with the Teclast P10SE firmware, but it is stoping at the 100% procedure of flashing FDL2, I think unsign the FDL1.bin and FDL2.bin or remove the secure flag may solve the problem, can you help me?
Posts: 30
Threads: 2
Joined: Mar 2021
Reputation:
1
I am trying to flash my tablet with a firmware from another brand. This firmware have a same CPU platform SC7731e that of my tablet.
However, when I flash the firmware using SPD researchdownload, it stop at the 100% flashing bar of FDL2, and finally give me a message of wait input time out.
I think the reason is that the FDL1-sign.bin and FDL2-sign.bin have sign flag which stop the PC pointer jumping to the other address for flashing. Do anyone know how to unsign the FDL? or any method of removing the sign flag of the FDL using the HEX editor?
Posts: 22,063
Threads: 570
Joined: Jul 2014
Reputation:
332
12-04-2021, 09:33 AM
(This post was last modified: 12-04-2021, 09:33 AM by X3non.)
(10-04-2021, 08:41 PM)nheaven Wrote: I already flash my tablet with the Teclast P10SE firmware, but it is stoping at the 100% procedure of flashing FDL2, I think unsign the FDL1.bin and FDL2.bin or remove the secure flag may solve the problem, can you help me?
honestly doubt that unsigning will help you
but you can post a link to your boot.img / fdl1 and 2 files
Posts: 30
Threads: 2
Joined: Mar 2021
Reputation:
1
13-04-2021, 05:21 AM
(This post was last modified: 14-04-2021, 05:01 AM by nheaven.)
(12-04-2021, 09:33 AM)X3non Wrote: (10-04-2021, 08:41 PM)nheaven Wrote: I already flash my tablet with the Teclast P10SE firmware, but it is stoping at the 100% procedure of flashing FDL2, I think unsign the FDL1.bin and FDL2.bin or remove the secure flag may solve the problem, can you help me?
honestly doubt that unsigning will help you
but you can post a link to your boot.img / fdl1 and 2 files
OK, I post the fdl1, fdl2, and boot.img to the attachment.
https://drive.google.com/file/d/1dC6XiUd...sp=sharing
https://drive.google.com/file/d/1IPtP7oy...sp=sharing
https://drive.google.com/file/d/1pXnZeZN...sp=sharing
Posts: 22,063
Threads: 570
Joined: Jul 2014
Reputation:
332
(13-04-2021, 05:21 AM)nheaven Wrote: OK, I post the fdl1, fdl2, and boot.img to the attachment.
...
all your links require access, ensure to post shareable link, on the other hand, here's what you can try
open boot.img (it should be signed as well) using hxd hex editor
search for "ANDROID"
note the start addr for ANDROID
open fdl files using hxd
select and delete everything from the start addr you got earlier to the first position
save the file as your unsigned file
Posts: 30
Threads: 2
Joined: Mar 2021
Reputation:
1
(13-04-2021, 12:45 PM)X3non Wrote: (13-04-2021, 05:21 AM)nheaven Wrote: OK, I post the fdl1, fdl2, and boot.img to the attachment.
...
all your links require access, ensure to post shareable link, on the other hand, here's what you can try
open boot.img (it should be signed as well) using hxd hex editor
search for "ANDROID"
note the start addr for ANDROID
open fdl files using hxd
select and delete everything from the start addr you got earlier to the first position
save the file as your unsigned file
I have change the share permission of the google drive, please try to download the files again.
The start addr for "ANDROID" in boot.img is far beyond the size of FDL files. The boot.img in the PAC file of the firmware is not a signed image.
I think we should find the secure flag in the uboot-sign.img, I have upload the uboot-sign.img in the google drive, please take a look at it.
Posts: 22,063
Threads: 570
Joined: Jul 2014
Reputation:
332
(14-04-2021, 05:36 AM)nheaven Wrote: I have change the share permission of the google drive, please try to download the files again.
The start addr for "ANDROID" in boot.img is far beyond the size of FDL files. The boot.img in the PAC file of the firmware is not a signed image.
I think we should find the secure flag in the uboot-sign.img, I have upload the uboot-sign.img in the google drive, please take a look at it.
uboot is the same as fdl2, anyways removing offset 0 - 200 from your files should result to unsigning the file
Posts: 30
Threads: 2
Joined: Mar 2021
Reputation:
1
(14-04-2021, 12:52 PM)X3non Wrote: (14-04-2021, 05:36 AM)nheaven Wrote: I have change the share permission of the google drive, please try to download the files again.
The start addr for "ANDROID" in boot.img is far beyond the size of FDL files. The boot.img in the PAC file of the firmware is not a signed image.
I think we should find the secure flag in the uboot-sign.img, I have upload the uboot-sign.img in the google drive, please take a look at it.
uboot is the same as fdl2, anyways removing offset 0 - 200 from your files should result to unsigning the file
don't understand what is offset 0-200.
do you mean from address 00000000 to address 00000200?
|
