(06-22-2021 09:45 AM)XY0797 Wrote: About how I came to this conjecture:
I saw a similar experience in a calculator forum in my country. It was 2016, and also HP Prime V1. His HP Prime V1 was unable to be opened after updating the new firmware at that time, and tried all the methods I mentioned earlier were invalid. There are other members of that forum who have HP Prime V1 unable to enter recovery mode, but his HP Prime V1 can work normally and can not enter recovery mode to update firmware. After discussion, they concluded that HP Prime V1 has bad blocks in its flash memory chip and that HP Prime V1, which cannot be opened after updating the new firmware, incorrectly writes data to the bad blocks while the new firmware is running, causing boot failures. HP Prime V1, which cannot enter recovery mode but can be used normally, has bad blocks in the flash memory area where the recovery mode is located.
I personally think this may just be an accident in a batch. However, my HP Prime V1 encountered almost the same problem, and I have reason to suspect that there was a quality control problem in the HP Prime V1 flash memory production line at that time. If it is a battery problem, using a regulated DC power supply should solve the problem, but it is not useful. If it is a screen problem, when connected to the computer, the software on the computer should respond, because the calculator can smoothly connect to the computer two days after the upgrade, and the malfunction occurs on the third day, but the software on the computer does not respond at all. If it's a keyboard problem, the reset button should be useful, but it's not. I can only make this guess because I tried what I know is that nothing can go into recovery mode or turn on the calculator.
My English is very bad and may mean something very strange. I apologize for this and hope you can forgive me. If there are any recovery methods that I have not mentioned, please reply to me. Thank you very much!
If your calculator was updated to the latest recovery version before the "failed" flashing procedure, as far as I know it will skip over bad blocks when writing the firmware, so your calculator should still work. The flash chip is made by Samsung, not exactly rookies in the flash business so your quality control assumption seems baseless.
All flash chips have and develop more bad blocks as they age. The firmware should be able to handle bad blocks without crashing.
As another theory, there could've been a software crash that randomly erased some blocks, preventing Recovery from loading, that's extremely rare but it could be possible.
Other hardware failure is much more likely (a blown capacitor, resistor, etc.), that could prevent the flash chip, the CPU or other unrelated hardware from working, hanging your calculator.
You said it was recognized via USB for 3 days after the flash, so flashing was unlikely to be the cause. I think you won't know until you connect it via JTAG. If it was indeed an erased block problem, you'll be able to write the new recovery and bring it back to life.
Search
Member List
Calendar
Help
