View Single Post
Old 11-17-2017, 09:44 PM   #7
mr9v9
Nameless Being
 
Post

Quote:
Originally Posted by filippo80x View Post
The original post is quite old (2015), but actually the solution worked on my Max with 1.8.1 and it is still working with 1.8.2 (may 2017) that is the last available firmware.
Confirmed!
The method works although I had to modify the original instructions for new users in case somebody comes here from a google search. I use Arch but instructions can be adapted for other Distros, and I already have adb and fastboot tools installed.

First install abootimg. Now grab the latest update.zip for your device here. *Make sure you use the correct file and Android version, and that you are also running the same build!
Open update.zip and extract the boot.img.
Open a terminal in this location and run these commands:
Code:
abootimg -x boot.img

mkdir fs

cd fs; zcat ../initrd.img | cpio -i

nano init.freescale.rc
Comment out this line and save the file:
Code:
setprop ro.ONYX_DISABLE_KEYGUARD 1
Repack the files:
Code:
find . | cpio -o -H newc | gzip > ../newinitrd.img

cd ..

abootimg --create newboot.img -f bootimg.cfg -k zImage -r newinitrd.img
On your device go to Applications>Settings>Developer Options and enable USB Debugging. Now would also be a good time to double check or set your pin code lock under Security>Screen lock.
Power off your device, and then hold next page and power for 7 seconds until you see the Boox logo stop.
With your computer if you have fastboot tools installed, type fastboot devices to confirm you are in fastboot mode. Then on your terminal type
Code:
fastboot flash boot newimage.boot
and you should receive this message:
Code:
target didn't report max-download-size
sending 'boot' (3674 KB)...
OKAY [  3.507s]
writing 'boot'...
OKAY [  0.297s]
finished. total time: 3.804s
*If you get a FAILED (remote: : Write partition) Power off, and try one more time until it completes.
Type fastboot reboot and test your pin code lock screen. If all is well then you can use your device! If not then you need to repeat the process with the correct file, or revert using the original boot.img from the zip.

Last edited by mr9v9; 11-19-2017 at 04:49 AM. Reason: Update
  Reply With Quote