Kindle Touch/PW1/PW2 5.0.x - 5.4.4.2 JailBreak. Plus FW 5.x USBNetwork.

[pghaworth]

Thank you. I thought about doing that, but didn't want to make things worse. I'll give it a try and report back later. It may be tomorrow or a couple of days, depending. I have a lot going on right now. I really appreciate your input.

[pghaworth]

Okay. Nothing like 'ENABLE_DIAGS' file(s) anywhere. There are some diagnostic logs from playing around yesterday trying to fix it and I noticed today that there is a file from today called 'NEW_BATTERY_FLAG'.

I've been charging it via direct power, not through computer, since I got the screen I posted the very first time. I charge it regularly anyway so it shouldn't have a battery issue and my other identical model is still going great. Lemon?

ETA - did the rest of what you recommended and it took me right back to the same screen. I had tried that yesterday, too.

[NiLuJe]

Shot in the dark: Did you ever install the Rescue Pack and the Coward's Rescue Pack?

If you did, do what @knc1 mentioned, but with the device completely unplugged.

[pghaworth]

I have the recue pack - fairly sure it's the coward's version. When I plug it in I can see the rp folder. I'll try those things as soon as I can (if) get a fully green light per my note below.

Interesting note - each time I would plug and unplug the yellow charge light would go out after a very few minutes. Now it's constantly on like it should be while charging. Also the time before knc1's post it had shown green when I tried various things (while doing them) but reverted to the off state when finished.

[GoSharks]

This is from dsmid's coward's rescue pack thread...(if it helps!)
https://www.mobileread.com/forums/sho...2&postcount=12

[pghaworth]

@knc1
@NiLuJe

I did what you suggested with no cables attached (I had before, too, but it wouldn't boot except to DIAGS) and got the same DIAGS EXIT screen as before, but this time it rebooted properly and went into the normal Kindle screen, as it should. Any idea what was going on there?

So glad I installed the coward's rescue pack and didn't delete it when I first encountered the issue. That's why I posted the screenshot. Wasn't sure which thing it was.

Thank you both once again! Do I need to update anything or am I good to go? You've done some updates and so forth since I did my last update of things.

[pghaworth]

@GoSharks - thanks for the link. Problem solved and I do have that link archived from our testing phase. I just wasn't sure if what I was seeing was the rescue pack or an Amazon thing. Got that answered too. All-in-all a good resolution with excellent assistance as always.

[NiLuJe]

Yup, the "go to diags if connected to power" is the CRP .

As for the charging, diags is probably designed to keep the battery in shipping range (something around 40 to 70%), so don't expect it to ever hit a green light . On some devices, it will even discharge the battery no matter what you do.

FWIW, I just inlined dsmid's post in the CRP README, because that's where this kind of info should have been from the start (I assumed it was and completely forgot about it... :x).

[pghaworth]

Thanks and thanks! Next time I know what it is and what to do if I start having the same issue.

[juan_carlos]

I just updated manually my PW2 from 5.6.5 to 5.7.2, and the jailbreak survived. Everything is working perfectly so far, KOReader, kpvbooklet etc.

[NiLuJe]

@juan_carlos: Thanks for jumping in the line of fire for us .

[dhdurgee]

Sounds like the next step will be for BranchDelay to update a unit and see if they have patched the security hole he found. If so, then he should be able to release his JB.

Dave

[knc1]

Originally Posted by NiLuJe

@juan_carlos: Thanks for jumping in the line of fire for us .

Not too big a risk -
The Kindle was jail broken - I.E: Had a serial port installed (or re-installable).

And we recently learned that evidently the "Recovery Menu" will run an Amazon Upgrade package without reference to it being actually a "Downgrade" package.

Plus we have worked out how to go from u-boot + otherwise erased eMMC to fully recovered.

But still a nice thing to do and report here as soon as possible -
Thanks A Lot.

[juan_carlos]

Originally Posted by knc1

Not too big a risk -
The Kindle was jail broken - I.E: Had a serial port installed (or re-installable).

And we recently learned that evidently the "Recovery Menu" will run an Amazon Upgrade package without reference to it being actually a "Downgrade" package.

Plus we have worked out how to go from u-boot + otherwise erased eMMC to fully recovered.

But still a nice thing to do and report here as soon as possible -
Thanks A Lot.

It was jailbroken 2 years ago, so I don't have a serial port installed But you are right, it can be done anytime if needed.

[knc1]

Originally Posted by juan_carlos

It was jailbroken 2 years ago, so I don't have a serial port installed
But you are right, it can be done anytime if needed.

I actually thought of that, after I pressed "post" button.

But I didn't edit the post because the rest of the point, about having recent recovery information for nearly any condition, was still good information.