|
@clydecoutinho
Thank you for your reply. I will continue working on this with the help of a forum member and planning to post whatever developments I have. Hope we will get trough this.
@geek1011
You're almost completely right on my post. As I am not a genuine engineer but a thinkerer turned designer I needed help from LLMs and believe me I am no fan of them or the slop. So I am really sorry if my efforts added to the slop. I will try to add details you mentioned as far as my abilities allow.
- I specifically pointed the part that was generated by the LLM but you're right that that's the bulk of it.
- By bricked what I meant was, my beloved KA1 (after not using it for a short while) was stuck on the cover of the last book I was reading, and a “power off” overlay on a small portion of the cover. When I tried to turn on, the RGB LED slowly blinked with blue color and nothing happened, the device didn’t turn on. As I was at the beach at that moment, I tried a reasonable amount times (like 50) before I gave up. When I got back to the place I was staying I tried first the same thing and then tried long pressing while connected to the power. There were a couple of red blinks too but nothing more. I thought it was a failure originated from the battery so I left it plugged for 8 hours or so. After that the long press without power produced nothing new but the colors produced by the RGB LED changed when plugged. After the blue slow blink there came rapid red and green blinks. The backlight of the screen turned on but nothing else. U tried the same with different chargers,/cables, connecting to macs and pc’s instead of wall plugs etc. before turning on to google, reddit, kobo faq’s, this forum and the LLMs as a last resort. This is what I mean by bricked.
* Both of you tried to make a kernel+initramfs boot image out of the 4.38.23697 kernel and various /init payloads which perform different actions (USBMS, LED, ethernet, reboot, watchdog).
- Yes I tried to get any type reaction from the device to understand if I was encountering with a hw failure or a corrupted logic. As I am a mac user of 30 years the old HFS+ seasoned my to logic failures especially in the early days.
* All attempts were inconclusive after fastboot success (and you didn't provide any indication in the post nor to your LLMs to concretely distinguish failures).
- Exactly
* Your LLMs have been guessing at the boot image format mostly blindly, which may have resulted in the inconclusive results.
- I can concur this guess exactly and sadly about the LLMs I tried but I had nothing more to work with at the time and I don’t like giving up.
* The kernel cmdline may or may not be correct.
- Exactly
Neither of you have provided:
* What actually happens to the device when attempting to turn it on, nor what you consider "bricked" to be.
- That is a big mistake on my side, I had lost the perspective for a good reporting after long hours of blind trying without much knowledge
* UART logs.
- I was not at my place so my abilities were even more limited they already are. So I didn’t pry open the device and try locate the UART pins.
* What state the "idle" device was in (was it plugged in? lights?).
* What the screen is showing now, and what the screen was showing before and after it was "idle".
- The device when I don’t meddle with it is without any indication from the LED and the backlight is off. The screen still has the cover on it. The screen didn’t show anything different at all since AK1 is “bricked”
* Actual concrete information about booti.
- This question is beyond my ability to give a good answer without an LLM interfering but since that was the reason of your complaint to begin with I will not try to get an information from those.
* Whether you have your own flash dumps we can look at.
* Your test boot images, and how you created them.
- I can share those if you like, I didn’t know the kind of reply I would get so tried to keep the initial post as short as I could.
* Your host tooling, versions, platform, etc.
- Not sharing those may be the stupidest thing I did. I should know at least that much about debugging. I created the custom images on an M1 / sonoma Mac and did the fastboot&sending of images on a windows10 Lenovo laptop (that a family member owns). The reason to use two different machines were the USBC ports on the mac, the need to use a converter and Apple’s strict management on the data transferred trough those ports in their infinite wisdom🤦🏻*♂️🤦🏻*♂️🤦🏻*♂️
* I also recommend looking at ntx_hwconfig (both the partition and the tool).
- I will check that as soon as I can return to this adventure.
* Also, malodayi, your (or the LLM's) original notes and logs would be much more useful than whatever that summary is supposed to be
- Believe it would be 80 pages of back and forth of four idiots (the LLMs and me). I let the LLMs generate the report and tried to edit myself, albeit miserabl, as I understand. But I should have done a much better job.
Thank you so very much for your detailed reply. I will try to do much better both on this adventure and my further posts in the forum.
Sadly I had to stop looking at this for (hopefully) a short while as I am dealing with a health emergency of a family member. But I hope to return to this as soon as I can. I am a firm believer of right to repair and enjoy trying to revive/revitalise devices as I can’t do that for people.
This post is completely hand written and I am truly grateful for your replies.
|