topjohnwu / Magisk

The Magic Mask for Android
GNU General Public License v3.0
48.39k stars 12.36k forks source link

Tesco Hudl stuck in recovery mode with patched boot.img #4484

Closed RayyanAnsari closed 3 years ago

RayyanAnsari commented 3 years ago

Device: Tesco Hudl (the original) Android version: 4.2.2 Magisk version name: v22.1

Since the Hudl runs Android Jellybean, I don't think I can use the Canary Builds. Instead this was done with Magisk version 22.1. When I patched the boot image with the Magisk 22.1 app and flashed it, the device displays "Powered by Android", then goes to a blank screen for a while, then enters recovery. Rebooting from recovery went back to recovery and pressing the reset button with a pin went back to recovery. Essentially, all the tablet could do was go to recovery. What the tablet is supposed to do it show "Powered by Android", then show the Hudl boot animation.

Steps to reproduce the issue:

  1. Have ADB and rkflashtool installed.
  2. adb reboot bootloader
  3. sudo rkflashtool r boot > boot.img <- This gets the boot image from the device. Make sure to keep this as you will need this to fix the boot partition later!
  4. sudo rkflashtool b <- Reboot to system.
  5. Copy the boot image to the device.
  6. Use the Magisk v22.1 app to patch the image.
  7. Copy the patched image back onto your computer.
  8. adb reboot bootloader
  9. sudo rkflashtool w boot < magisk_flashed.img <- Writes the patched boot image.
  10. sudo rkflashtool b

Steps to restore the boot partition

Whilst I was stuck in recovery, adb didn't seem to work. So I couldn't just run adb reboot bootloader. I stumbled upon the correct key combination on the Internet to get to flash mode. Hold Volume Up, and use a pin to click the reset button on the back of the tablet.

  1. sudo rkflashtool w boot < boot.img <- Use the image you should have backed up.
  2. sudo rkflashtool b

After this the tablet functions normally.

github-actions[bot] commented 3 years ago

This issue is being automatically closed because it does not follow the issue template.