How to flash a JDRead2 to Poke3

[f_coco]

I've got a brand new ereader JDRead2 which is a OEM model of Boox Poke3.
I first put a Poke3 latest 3.5 firmware in the root dir.

The reader recognized the update package, but after some processing step, the upgrade process stopped because the product name is not match.

After that, i want to try flash the update.zip with recovery. First, i have to open ADB.

After some research, I finally get the adb worked by input a secret code 0423.
Then i can reboot into recovery.

But after i reboot to recovery by using adb reboot recovery. The ereader only made a data wipe without showing the recovery page. So i can't try flash with the recovery. Seems this ereader do not have a full recovery.

Any other solutions?

Any comments is appriciated.

Regards!

[Renate]

You need to edit the update.zip so that the first line or two of updater-script does not put the checks for build in.
I've got a custom recovery for the Poke3 that can flash it.

[f_coco]

Originally Posted by Renate

You need to edit the update.zip so that the first line or two of updater-script does not put the checks for build in.
I've got a custom recovery for the Poke3 that can flash it.

Thanks for your comments.

Could you share the custome recovery?

And if i modified the update.zip i need to sign it with a test key, am i right?

[Renate]

Originally Posted by f_coco

Could you share the custome recovery?

And if i modified the update.zip i need to sign it with a test key, am i right?

No, you don't have to fix any signing.
I'm going to dust off the custom recovery and see if it's still ok.

Edit: I blew off some dust and it's ok.
You need either a USB Type C flash or an USB Type A flash and an OTG adapter.
You need to put update.zip (the decrypted file) on the flash that is formated with FATxxx and not NTFS or EXTxxx

You need to flash the image (I'll PM you a link) to recovery either with fastboot or dd if you are rooted.

fastboot flash recovery p9mod
fastboot reboot recovery
... zzzz ... white screen
adb shell start autoupdate
... follow directions ...

[f_coco]

Originally Posted by Renate

No, you don't have to fix any signing.
I'm going to dust off the custom recovery and see if it's still ok.

Edit: I blew off some dust and it's ok.
You need either a USB Type C flash or an USB Type A flash and an OTG adapter.
You need to put update.zip (the decrypted file) on the flash that is formated with FATxxx and not NTFS or EXTxxx

You need to flash the image (I'll PM you a link) to recovery either with fastboot or dd if you are rooted.

fastboot flash recovery p9mod
fastboot reboot recovery
... zzzz ... white screen
adb shell start autoupdate
... follow directions ...

Thanks for your help.
Let me put all this together.
01. I need to remove the devices check scripts in the original Poke3 update.zip and zip it again.
02. Put the new update.zip into a usb drive and attach it to the devices via a OTG adapter.
03. flash the p9mod to the recovery
04. reboot to recovery and start autoupdate and follow the instruction

Do i miss anything?

[Renate]

Originally Posted by f_coco

Do i miss anything?

Looks good to me.
Just the first line or two of updater-script

[f_coco]

Originally Posted by Renate

Looks good to me.
Just the first line or two of updater-script

Hi, Renate.
I followed your instrunction today. It's not working.

01. the "fastboot reboot recovery" shows "fastboot: usage: unknown reboot target recovery", So i can't reboot to recovery.

02. i realize the device only have one typc-c usb port. if i connect the usb adapter to it then i can't connect the devices to computer, so i can't input the adb shell start autoupdate command.

and there is a strange thing. after i flash the p9mod to recovery. i tried reboot to recovery after the devices boot to the system. But the device still make a data wipe like the recovery isn't been flashed.

Thanks for you help. Do you have any other solutions?

[Renate]

Originally Posted by f_coco

So i can't reboot to recovery.

If you have a working system you can just do:

adb reboot recovery

If you can get to EDL you can also flash a small file to misc and reboot.

Originally Posted by f_coco

if i connect the usb adapter to it then i can't connect the devices to computer, so i can't input the adb shell start autoupdate command.

More to the point, ADB requires peripheral mode and the flash drive requires host mode, so no hub or adapter does both.
Connect the PC, do the command, when it says "waiting for flash", unplug the PC and plug in the OTG/flash.

[f_coco]

[QUOTE=Renate;4420072]If you have a working system you can just do:

adb reboot recovery

Hi renate,
I tried adb reboot recovery from the working system after i successfully flash the p9mod from fastboot.
But the system wipe the data like the original recovery dose. No normal recovey page showed.
I also tried fastboot boot p9mod, the system started, but the light is out, and a navi bar shows.

[Renate]

If you previously wiped data and nothing overwrote that command it will try to overwrite again.
What do you see when you reboot recovery? Do you have rooted ADB?
Don't tell me what you didn't see. Tell me what you did see.

[f_coco]

Hi, Renate.
I attach a photo taken after i adb reboot recovery in the original system after i flash the p9mod.

[f_coco]

(bootloader) parallel-download-flash:yes
(bootloader) hw-revision:10000
(bootloader) unlocked:yes
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4296
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) erase-block-size: 0x200
(bootloader) logical-block-size: 0x200
(bootloader) variant:SDM EMMC
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x601BFBE00
(bootloader) partition-typenyxconfig:raw
(bootloader) partition-sizenyxconfig: 0x2000000
(bootloader) partition-type:vbmeta:raw
(bootloader) partition-size:vbmeta: 0x10000
(bootloader) partition-type:rawdump:raw
(bootloader) partition-size:rawdump: 0x8000000
(bootloader) partition-type:storsec:raw
(bootloader) partition-size:storsec: 0x20000
(bootloader) partition-type:sti:raw
(bootloader) partition-size:sti: 0x200000
(bootloader) partition-type:logdump:raw
(bootloader) partition-size:logdump: 0x4000000
(bootloader) partition-type:frp:raw
(bootloader) partition-size:frp: 0x80000
(bootloader) partition-type:devcfg:raw
(bootloader) partition-size:devcfg: 0x100000
(bootloader) partition-type:keystore:raw
(bootloader) partition-size:keystore: 0x80000
(bootloader) partition-type:misc:raw
(bootloader) partition-size:misc: 0x100000
(bootloader) partition-typeersist:raw
(bootloader) partition-sizeersist: 0x2000000
(bootloader) partition-type:modemst2:raw
(bootloader) partition-size:modemst2: 0x200000
(bootloader) partition-type:modemst1:raw
(bootloader) partition-size:modemst1: 0x200000
(bootloader) partition-type:ssd:raw
(bootloader) partition-size:ssd: 0x2000
(bootloader) partition-type:fsc:raw
(bootloader) partition-size:fsc: 0x400
(bootloader) partition-type:bluetooth:raw
(bootloader) partition-size:bluetooth: 0x100000
(bootloader) partition-type:sec:raw
(bootloader) partition-size:sec: 0x4000
(bootloader) partition-type:ddr:raw
(bootloader) partition-size:ddr: 0x100000
(bootloader) partition-type:logfs:raw
(bootloader) partition-size:logfs: 0x800000
(bootloader) partition-type:toolsfv:raw
(bootloader) partition-size:toolsfv: 0x100000
(bootloader) partition-type:limits:raw
(bootloader) partition-size:limits: 0x1000
(bootloader) partition-type:splash:raw
(bootloader) partition-size:splash: 0x20A4000
(bootloader) partition-type:dpo:raw
(bootloader) partition-size:dpo: 0x400
(bootloader) partition-type:msadp:raw
(bootloader) partition-size:msadp: 0x40000
(bootloader) partition-type:apdp:raw
(bootloader) partition-size:apdp: 0x40000
(bootloader) partition-type:devinfo:raw
(bootloader) partition-size:devinfo: 0x1000
(bootloader) partition-type:dip:raw
(bootloader) partition-size:dip: 0x100000
(bootloader) partition-type:abl:raw
(bootloader) partition-size:abl: 0x100000
(bootloader) partition-type:dsp:raw
(bootloader) partition-size:dsp: 0x1000000
(bootloader) partition-type:modem:raw
(bootloader) partition-size:modem: 0x6E00000
(bootloader) partition-type:mdtp:raw
(bootloader) partition-size:mdtp: 0x2000000
(bootloader) partition-type:mdtpsecapp:raw
(bootloader) partition-size:mdtpsecapp: 0x400000
(bootloader) partition-type:cmnlib64:raw
(bootloader) partition-size:cmnlib64: 0x100000
(bootloader) partition-type:cmnlib:raw
(bootloader) partition-size:cmnlib: 0x100000
(bootloader) partition-type:keymaster:raw
(bootloader) partition-size:keymaster: 0x100000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x10000000
(bootloader) partition-type:vendor:raw
(bootloader) partition-size:vendor: 0x32000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xC0000000
(bootloader) partition-type:recovery:raw
(bootloader) partition-size:recovery: 0x4000000
(bootloader) partition-type:boot:raw
(bootloader) partition-size:boot: 0x4000000
(bootloader) partition-type:fsg:raw
(bootloader) partition-size:fsg: 0x200000
(bootloader) partition-typemic:raw
(bootloader) partition-sizemic: 0x80000
(bootloader) partition-type:hyp:raw
(bootloader) partition-size:hyp: 0x80000
(bootloader) partition-type:rpm:raw
(bootloader) partition-size:rpm: 0x80000
(bootloader) partition-type:tz:raw
(bootloader) partition-size:tz: 0x400000
(bootloader) partition-type:xblbak:raw
(bootloader) partition-size:xblbak: 0x380000
(bootloader) partition-type:xbl:raw
(bootloader) partition-size:xbl: 0x380000
(bootloader) secure:no
(bootloader) serialno:559ed40c
(bootloader) product:sdm660
(bootloader) max-download-size:597590016
(bootloader) kernel:uefi
all:
finished. total time: 0.215s

Here is all the parameters i get in fastboot mod.

[Renate]

Originally Posted by f_coco

Hi, Renate.
I attach a photo taken after i adb reboot recovery in the original system after i flash the p9mod.

That's wacky Chinese stock recovery doing a factory reset of the device.
You may have flashed my recovery, but it's way gone now.

You need to learn about EDL.
You need to boot to something and

adb reboot edl

You need to go to my website, read about EDL and do everything there.

edl /lpoke3.bin
edl /g
edl /w /precovery p9mod
edl /w /pmisc misc-recovery
edl /z

Use your common sense with file names if I got them wrong.
When you get a white screen that's doing nothing, you have success.
Then do the "adb shell start autoupdate".

Finally, when things go clearly wrong, just stop.

[f_coco]

Hi, Renate.
Thanks for your help.
I can made it to the edl mode. i can see the partition tables.
Before i proceed to the next step, I just want to check with you is there a way i can backup all partitions? Just in case someting gose wrong.

[Renate]

If you've got 32 GB of space on your desktop just collecting dust, do this:

edl /r big_darn_file

(Choice of filename is yours.)