LeapFrog Epic: Difference between revisions
Line 102: | Line 102: | ||
VTech more or less nerfed the device by disabling features such as ADB and development settings, though USB debugging can be restored by temporarily rooting the device by patching boot.img with Magisk and editing the ADB setting using a settings database editor such as [https://play.google.com/store/apps/details?id=by4a.setedit22&hl=en&gl=US SetEdit]. Bizarrely enough they also dropped Bluetooth, replacing the wireless module with an obscure AltoBeam ATBM6011 wireless LAN controller. | VTech more or less nerfed the device by disabling features such as ADB and development settings, though USB debugging can be restored by temporarily rooting the device by patching boot.img with Magisk and editing the ADB setting using a settings database editor such as [https://play.google.com/store/apps/details?id=by4a.setedit22&hl=en&gl=US SetEdit]. Bizarrely enough they also dropped Bluetooth, replacing the wireless module with an obscure AltoBeam ATBM6011 wireless LAN controller. | ||
Ripping the firmware also used to be a challenge due to the uboot binary | Ripping the firmware also used to be a challenge due to the uboot binary coded with a deterrent which corrupts the dumped images past a certain point. To be fair this is hardly even unique to LeapFrog as the implementation by Rockchip themselves [https://gitlab.com/pgwipeout/u-boot-rockchip/-/blob/1b01cf5590f8d0b2270ffff5a656e38c5e3930ee/cmd/rockusb.c#L28 has this] until the [https://gitlab.com/pgwipeout/u-boot-rockchip/-/blob/6336d2324985831ed766031f91d410d0e587dbc8/cmd/rockusb.c latest commit]. However, an update to RedScorpio's [https://xdaforums.com/t/tool-imgrepackerrk-rockchips-firmware-images-unpacker-packer.2257331/post-89464941 imgRePackerRK] tool now made it possible to patch the stock uboot and enable firmware dumping. | ||
In case of a brick, it is possible to unbrick the LeapPad by forcing it to run in MASKROM mode through shorting two conveniently-located test points on the logic board just beside the eMMC chip, though it may also be rather fiddly to pull off. | In case of a brick, it is possible to unbrick the LeapPad by forcing it to run in MASKROM mode through shorting two conveniently-located test points on the logic board just beside the eMMC chip, though it may also be rather fiddly to pull off. |