help me i need poke5 3.3.2 firmware

[Renate]

The link I posted was Poke5P 3.5.1

[Quyen607]

So the issue is not incremental update, cause i did not use the incremental update file.
Now i can still have adb and edl but can not boot to the system.
I am wondering that Could the cause be:
original version 3.5.3 with some changes
flash file version 3.5.1 will not work
??

[Renate]

Maybe incompatible changes to something in /data?

Did you make a full backup before?

When you say that you have ADB, do you mean in the regular system or recovery?

[Quyen607]

I did not make a backup yet, i only have a adb on recovey mode

[Quyen607]

Is there any others way to fix it, can we use a backup of another poke5 device?

[Renate]

If there is nothing that you want on the device you can try wiping all the userdata.
Go to recovery, "reboot bootloader", "fastboot -w".

[Quyen607]

C:\>fastboot devices
6C1E2FDB        fastboot

C:\>fastboot -w
Erasing 'userdata'                                 FAILED (remote: 'unknown command')
fastboot: error: Command failed

[Renate]

Ok, so they screwed up abl/bootloader/fastboot

Use the new recovery that I just PM'ed you.
I've figured out the bugs in recovery (the init service).
So my recovery now does autoupdate and stock recovery.

adb reboot edl
edl /lqcm2290.bin
edl /w /precovery_a recmod
edl /w /precovery_b recmod
edl /z
adb reboot recovery

So, you get a white screen (as before).
You could "start autoupdate" but you don't want to right now.
Type "start recovery".
You get the stock recovery.

Normally on a device without buttons you can pull/insert the USB cable to increment selection.
Unfortunately, since I own the USB that is not going to work.
You have to open/close the cover.
If you don't have a cover, use a magnet on the bottom edge of the screen.
The power button is select.

[Quyen607]

AFTER start recovery, the screen showed as below picture:
https://drive.google.com/file/d/11Un...ew?usp=sharing

Then i re did the autoupdate
then the device is not reboot to system, it stops on this screen:
https://drive.google.com/file/d/1HyI...ew?usp=sharing

https://drive.google.com/file/d/1m4m...ew?usp=sharing

autolog:
https://drive.google.com/file/d/1FCd...ew?usp=sharing

Is the white display because of some different things bettween Eink carta 1200 your device - poke5 2023, and my device Poke5 2024 Eink carta 1300?

Can you guide me step by step to select wipe userdata on your screen, i will do it on my device without looking on my screen.

[Renate]

Just to be clear, with autoupdate or the recovery part of recovery you never see any normal text on the screen?

From the log I can see that autoupdate itself is 100% correct.
I can see that update-engine-sideload ran 100% happily.

I don't think that you can just flash the Poke5P software on this and have it work.
At the very least it would need different build.prop

I'm surprised that ttyscreen could not make any text.
It's supposed to work on anything.
If it screwed up it might make a blizzard of black dots, but I don't even see that.

[Quyen607]

Originally Posted by Renate

Just to be clear, with autoupdate or the recovery part of recovery you never see any normal text on the screen?

Right, never seen any normal text on the screen

C:\Users\>adb shell
# reboot recovery
Was: boot-recovery
Rebooting
#
C:\Users\>adb shell
# start recovery
# start recovery
# ttyscreen
Created fifo /dev/ttyscreen

https://drive.google.com/file/d/1s5W...ew?usp=sharing

[Renate]

Oh. I've seen the Onyx not getting erased before.
I don't erase it. The system usually does that on startup.
I've never had a device like that so I can't say where the problem is.

A minor point: ttyscreen is an init service.
Don't run it by "ttyscreen", you could get multiple instances fighting over resources.
Just say "start ttyscreen".

[Quyen607]

Can i do this ?
Make a raw backup by edl on another poke5
Restore the backup file to this broken poke5

[Renate]

If you did a Poke5P full update on this device (despite the screen not showing) and it didn't work, then you have some big compatibility problems.

I don't even know which device EXACTLY that you're talking about. I've never seen it. I don't know what's inside it.

[Quyen607]

I will take some pictures of its mainboard.