1

I have this tablet that runs on RK3168 (Rockchip) SoC. The problem is that fastboot doesn't recognize the device, but after so much toil, I managed to find Finless' flashing tool and flashed CM Recovery image unto the device. The flashing worked because when I rebooted to recovery mode, it showed CM recovery screen instead of the stock recovery screen.

The flashing tool is a windows GUI. It doesn't have an unlock bootloader function. But since I was able to flash the recovery image successfully, my question is, does this mean that my device bootloader is already unlocked?


Edit: (more details) Using Finless' flashing tool, I backed up all the NAND partitions and named them accordingly, e.g. backup.img, kernel.img, etc. Then I reflashed them all back into the device but reflashed a different recovery.img. I reflashed a generic CM that I got from this site instead: http://androtab.info/clockworkmod/rockchip/

I did all this with the assumption that the flashing tool actually works. After all, I used it to make the backup as it was the only tool that detected the device in fastboot mode because fastboot just doesn't detect it. (It could be that the bootloader interface driver doesn't work properly for fastboot on Win x64, but I don't have the luxury of setting up a 32-bit OS.)

When I rebooted the device, everything was fine. Rebooted into recovery mode and CM recovery screen showed up.

I'm still new to all this android flashing stuff, I don't really know what an unlocked bootloader means, and I just read from other guides that in order to flash a custom recovery, I need an unlocked bootloader first. So I'm presuming that if I was able to flash images, that my bootloader is already unlocked? But I'm not sure, so that's why I'm asking (albeit a very naive question...)

  • Unfortunately no, the bootloader is a separate entity that will need to be unlocked on it's own. Flashing a custom recovery doesn't automatically unlock it. What is the model of the tablet? – IAmTheSquidward Jul 29 '14 at 13:06
  • It's a Starmobile Engage7+ tablet. It's one of those cheap >$100 tablets. The problem with these devices is that there's hardly any "official" technical support. Took me days to get adb to detect the device, and I just gave up on fastboot. – Poly Bug Jul 29 '14 at 13:39
  • I gotcha. I can't find any information in the modding community for that tablet. I think you're out of luck with unlocking the bootloader. Towelroot should work for rooting, and other than that, I think you're stuck on the stock ROM. – IAmTheSquidward Jul 29 '14 at 13:42
  • But I'm wondering, if I was able to flash NAND partitions while the device was in fastboot mode, not just the recovery partition, doesn't that mean the bootloader's already unlocked? Edited question to add details. – Poly Bug Jul 29 '14 at 13:43
  • Close. The bootloader runs before the OS is loaded and makes sure that the installed system is "approved." So, for example, on Samsung devices, the bootloader checks to make sure the system is written by Samsung. (Almost) every Android device has access to fastboot to help recover the device in case of damage to the OS. By flashing the stock backups, the bootloader still sees the OS as the original factory OS (which, well, it is). Does that make sense? My apologies if I'm talking confusingly! – IAmTheSquidward Jul 29 '14 at 14:08

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.