can't flash pkg - even official 1.4 firmware -- error 90001 #19

Closed
opened 2018-12-05 21:27:47 -08:00 by ziegfeld · 5 comments
ziegfeld commented 2018-12-05 21:27:47 -08:00 (Migrated from github.com)

Dear HappyZ,

I have followed the README and some hi-pda e-ink bbs posts and successfully patched my boot.img and rooted my DPT-RP1.
Great job! Really appreciate your work!

Problem now is that I am trying to use "dpt-tools.py" fw mode

  1. to flash the official SONY firmware. but after the script in terminal finished normall,y the device reboots, then a "verfiying package" message is there. but afterwards it goes to a "cannot upgrade. error code 900001".

  2. if I use my own modified pkg, it would be similar to the above, but even without the "veryfiying package part", straght to 90001 after a few screen blinks. (I would also mention that, when I use your unofficial repacker to generate this .pkg file. on one step the sdtout/stderr showed "Verification Failure", I guess from openssl")

Would you kindly provide some insights? Thank you!

Regards,
Ziegfeld

Dear HappyZ, I have followed the README and some hi-pda e-ink bbs posts and successfully patched my boot.img and rooted my DPT-RP1. Great job! Really appreciate your work! Problem now is that I am trying to use "dpt-tools.py" `fw` mode 1. to flash the official SONY firmware. but after the script in terminal finished normall,y the device reboots, then a "verfiying package" message is there. but afterwards it goes to a "cannot upgrade. error code 900001". 2. if I use my own modified pkg, it would be similar to the above, but even without the "veryfiying package part", straght to 90001 after a few screen blinks. (I would also mention that, when I use your unofficial repacker to generate this .pkg file. on one step the sdtout/stderr showed "Verification Failure", I guess from openssl") Would you kindly provide some insights? Thank you! Regards, Ziegfeld
ziegfeld commented 2018-12-05 21:30:38 -08:00 (Migrated from github.com)

I would add that -- previously when I did "dpt-tools.py" "root", I saw 90001 and update failure errors too, just as many pals in hi-pad e-ink bbs. But still the root worked, I even successfully added busybox.

I would add that -- previously when I did "dpt-tools.py" "root", I saw 90001 and update failure errors too, just as many pals in hi-pad e-ink bbs. But still the root worked, I even successfully added busybox.
HappyZ commented 2018-12-06 09:28:50 -08:00 (Migrated from github.com)

The update failure 90001 error is expected. It is the error comes from the missing signals that acknowledge the success of fw updates. For example, if your system is already updated to 1.4.abcd, when you flash that 1.4.abcd pkg again, it will show this failure msg. Similarly, since rooting pkg isn't a real pkg, it didn't alert the system the success of fw update.

And yes, the verification failure message is only a warning. If you modified the updater.sh in your system, the system will flash the pkg, bypassing verifications, even though 90001 message shows.

The update failure 90001 error is expected. It is the error comes from the missing signals that acknowledge the success of fw updates. For example, if your system is already updated to 1.4.abcd, when you flash that 1.4.abcd pkg again, it will show this failure msg. Similarly, since rooting pkg isn't a real pkg, it didn't alert the system the success of fw update. And yes, the verification failure message is only a warning. If you modified the updater.sh in your system, the system will flash the pkg, bypassing verifications, even though 90001 message shows.
HappyZ commented 2018-12-07 17:59:12 -08:00 (Migrated from github.com)

Actually, it'll depend on the script in pkg. If there is a version check bash like the official pkg does, then when you run it, it will stop upgrading.

Actually, it'll depend on the script in pkg. If there is a version check bash like the official pkg does, then when you run it, it will stop upgrading.
ziegfeld commented 2018-12-11 07:36:38 -08:00 (Migrated from github.com)

Got it. I will modify the updater.sh.

Thank you so much for replying, yanzi!

I did not modify the updater.sh because I cannot see it; then someone told me I need to mount system partition first.. I missed that part.
So it would also be great, if you can add that line to mount the system so that /usr/shared/bin/ can be viewed. In your README at https://github.com/HappyZ/dpt-tools/blob/master/fw_updater_packer_unpacker/README.md

mkdir /mnt/system
mount -t ext4 /dev/mmcblk0p9 /mnt/system
Got it. I will modify the updater.sh. Thank you so much for replying, yanzi! I did not modify the updater.sh because I cannot see it; then someone told me I need to mount system partition first.. I missed that part. So it would also be great, if you can add that line to mount the system so that /usr/shared/bin/ can be viewed. In your README at https://github.com/HappyZ/dpt-tools/blob/master/fw_updater_packer_unpacker/README.md ``` mkdir /mnt/system mount -t ext4 /dev/mmcblk0p9 /mnt/system ```
HappyZ commented 2018-12-11 13:03:19 -08:00 (Migrated from github.com)

I have added the method in diagnosis mode. It's patch-updater-bash command.

I have added the method in diagnosis mode. It's `patch-updater-bash` command.
Sign in to join this conversation.
No description provided.