View Single Post
Old 10-04-2022, 12:12 PM   #4
trimen
Junior Member
trimen knows the difference between 'who' and 'whom'trimen knows the difference between 'who' and 'whom'trimen knows the difference between 'who' and 'whom'trimen knows the difference between 'who' and 'whom'trimen knows the difference between 'who' and 'whom'trimen knows the difference between 'who' and 'whom'trimen knows the difference between 'who' and 'whom'trimen knows the difference between 'who' and 'whom'trimen knows the difference between 'who' and 'whom'trimen knows the difference between 'who' and 'whom'trimen knows the difference between 'who' and 'whom'
 
Posts: 7
Karma: 10052
Join Date: Jul 2022
Location: Prague
Device: PW4,5
By default, everything is disabled. You have no bootloader access, nor Linux shell.

In the u-boot source, I found that the u-boot determines the type of device by reading state of some GPIOs, but I didn't look into it properly yet.

I don't know, what will happen if some partitions become broken. I'll try it, but first I need to acquire HW for reading eMMC so I can do a full backup, before modifying the content of it.

My next plans are to reverse the u-boot binary to get some knowledge about functions, that were removed from the released source but are in present the production u-boot binary.

Also, the datasheet for the used CPU is unobtainable. Currently, I don't know about any process to load empty eMMC, as I'm still waiting for HW.

The whole point of my efforts is to be able to unlock the bootloader, which should enable low-level access to internal storage.
trimen is offline   Reply With Quote