-
Notifications
You must be signed in to change notification settings - Fork 130
The Upgrade Guide
Upgrade via official approach may affect your rooted device. Therefore, here is the guide with modified PKG.
If you have never rooted, go to the basic hack. If you already rooted your device, it is not necessary to redo the hack unless told so.
This guide assumes you are already familiar with python dpt-tools.py. Also we assume you already rooted your device. It does not matter what version you are on currently.
Note: always make a backup of all your documents before you update. Also, if you have installed apps, it will be better to backup (upgrade will likely remove your apps).
And remember that just syncing the DPT with your PC does not automatically backup your documents!
You can do the official update if you are updating to 1.6.03.09261 or lower version (11/23/2019). Notice you can only do this exactly ONCE, and after doing it, your version number will stick to whichever version you updated to.
If you try to do this the 2nd time, it will not flash and will fail.
Step 1: do the official update (you can only do it exactly ONCE). It will say successful. But this will remove ADB. Also AppLauncher will likely crash if you did the launcher mod before.
Now don't panic. Use python dpt-tools.py to do the following:
Step 2: get back ADB by redoing the 3rd step from this guide. It will pop up error saying error: unable to update but is normal. It will still show AppLauncher crashed.
Step 3: re-apply the AppLauncher mod. After reboot, you will have no problem with AppLauncher any more!
Enjoy.
Procedure is the same as above, except for Step 1. Use python dpt-tools.py to do the following:
Step 1: Download the official PKGs I made. If you have never updated to the latest firmware before, it will say "update successful". Otherwise, it will say "error: unable to update" but it is actually updated. Also, ADB is gone, and AppLauncher crashes. But don't panic.
Step 2: get back ADB by redoing the 3rd step from this guide. It will pop up error saying error: unable to update but is normal. It will still show AppLauncher crashed.
Step 3: re-apply the AppLauncher mod. After reboot, you will have no problem with AppLauncher any more!
Enjoy.
This is more like a recovery method.
Run python dpt-tools.py --diagnosis, and follow the instruction to get into diagnosis mode.
Enter install-pkg and your PC will see the mass storage drive.
Put the downloaded FwUpdater.pkg from official PKGs I made, and follow the instruction on screen.
After flashed, you can follow steps 2 & 3 in above Method 2 to recover AppLauncher crash.
Enjoy.
To independently restore boot.img or system.img, use restore-boot-img or restore-system-img and follow the instruction.
Note: after 05/17/2019, it is required to use name boot.img or system.img in the drive to make it work.
For system.img, when it asks you about sparse image, try to say yes first. If errors occur, try again and say no.
Download this FwUpdater.pkg and use fw to update.
If it halts at waiting.. with a cancel button, it means it misses a system folder named Note. To solve this, you need to press cancel (wait for a minute or two) and then reset the device.
After reset, when it asks you about default launcher, use DigitalPaperApp.
Re-do the launcher mod. It happened because even though system partition is changed, data partition remained untouched (so do ExtMgr.db and ExtMgr.db-journal). Since I added the launcher mod to the system, to solve the crash, you need to overwrite ExtMgr.db and ExtMgr.db-journal as suggested in the launcher mod.
If AppLauncher crashes but your DPT isn't connected to Wifi (so dpt-tools.py regular fw method can't work), you can directly enter diagnosis mode using a cable via python dpt-tools.py --diagnosis. Then use install-pkg to install related PKGs.
Or equivalently the setting of pen color is empty. To solve this, you have to reset the device by going to "System Settings" and then "Initialize DPT". Before doing so, back up your documents.
Well, reset. If you can't get into the original system and use system settings to reset, then go to diagnosis mode and reset from there. Ways to reset is written in another wiki page.