Oasis on 5.8.2 stuck in Diag Mode - Page 2

picree · 08-26-2016, 09:04 AM

OK, I will do all/most of that when I get back tonight. But if that doesn't work is that to say that the device is "bricked"?

When you say export USB area you just mean run the diags command called USB EXPORT right? There is another command called USB DOWNLOAD. from the description ("USB Bundle Install") I wondered if that was the command that would trigger a factory reinstall if the .bin was in the root folder.

knc1 · 08-26-2016, 09:07 AM

Quote:

Originally Posted by picree

OK, I will do all/most of that when I get back tonight. But if that doesn't work is that to say that the device is "bricked"?

When you say export USB area you just mean run the diags command called USB EXPORT right? There is another command called USB DOWNLOAD. from the description ("USB Bundle Install") I wondered if that was the command that would trigger a factory reinstall if the .bin was in the root folder.

No more experimenting just yet, please.

I mean on the diags menu, there should be a menu entry to export the USB storage area to the USB cable.
The one that makes the USB storage area visible over the USB cable when hooked to a PC.

You mentioned it in passing in one of your posts here.

It may not include the word "export" in its menu entry, that is what it does, not how it may be labeled.

NiLuJe · 08-26-2016, 11:19 AM

Just to double-check, because the idme thing should definitely have done the trick:

Make sure you do not reboot with the device plugged to *anything* (that may include the cover and/or any OTG stuff on the Oasis).

Was that the *first* time you rebooted since installing the CRP?

(I don't think the false positives are *that* severe, but you might want to check the system logs to check that it's not actually the CRP that's re-throwing you back in diags mode for some reason...).

From the look I had at an Oasis rescue binary, it *should* be exiting diags properly, IIRC, but, again, that's from the outside, and @knc1 has seen a few misbehaving diags build over the years, so that's not an entirely uncommon sight (but on those builds, running idme manually over SSH does the trick).

picree · 08-26-2016, 11:30 AM

Quote:

Originally Posted by NiLuJe

Just to double-check, because the idme thing should definitely have done the trick:

Make sure you do not reboot with the device plugged to *anything* (that may include the cover and/or any OTG stuff on the Oasis).

The device was plugged in. In fact I issued the reboot from the command line...and the cover was attached. So if I reboot from the diagnostic menu after disconnecting do I issue EXIT REBOOT or EXIT DISABLE? I assume Reboot but have to ask. What is OTG?

Quote:

Originally Posted by NiLuJe

Was that the *first* time you rebooted since installing the CRP?

It was the first time I rebooted with power connected for sure. And I think it was the actual first reboot as I had just installed CRP the night before (but doesn't it reboot right after running the .bin?)

NiLuJe · 08-26-2016, 11:37 AM

@picree: Rebooting while plugged in will *definitely* throw you back in to diags, that's just CRP doing its job

.

As for the reboot after an install, that doesn't happen if you installed it through MRPI, which you probably did.

(That's relevant here because there may be an issue with the CRP checks on the Oasis, which are currently a little greedy, they probably match on more conditions than they should, hence my comments about the cover and OTG [i.e., the Voice thingy dongle]).
They definitely shouldn't match with a "naked" Oasis, but since all of this was mostly blind-coded, I might have screwed things up.

knc1 · 08-26-2016, 11:52 AM

Remove the cover -
That external battery might be triggering the CRP to throw you back into diags.

But the message so far about having to use the serial port to exit has been true.

Even some builds of the K3 diags where that way.
(I know, I have one of them - I was locked out for months.)

picree · 08-26-2016, 12:02 PM

Quote:

Originally Posted by NiLuJe

@picree: Rebooting while plugged in will *definitely* throw you back in to diags, that's just CRP doing its job

.

As for the reboot after an install, that doesn't happen if you installed it through MRPI, which you probably did.

I did use MRPI...

picree · 08-26-2016, 12:20 PM

Quote:

Originally Posted by knc1

Remove the cover -
That external battery might be triggering the CRP to throw you back into diags

I know, along the way, last night, I tried exiting the diagnostic page with a naked kindle (no cover no power but MAYBE with the USB cable hanging off). However, it went back to the diagnostics. I just tried EXIT DIAGS with a naked kindle and it worked! Sadly I think I left the trigger file, DO_FACTORY_RESTORE on the device, so I was greeted with a brand new Kindle.

I can't get on WiFi so I will have to wait until later to re-register and see where I am exactly.

It looks like I just did an unnecessary factory reset.

But, it's nice to be out of the diagnostic page. @NiLuJe, are you still convinced that CRP should work fine on an Oasis...AS LONG AS, it is disconnected from everything when restarting? I want to make sure RP and CRP are fine for the Oasis. For now, until there is better confirmation I will drop back off 5.8.2

Curt

knc1 · 08-26-2016, 12:26 PM

This is the first time in years that we have had the freedom to "start over" on nearly any model of Kindle by using the factory firmware package.

You might just have to re-install the hotfix package.

I have a KT3W from the most recent production run arriving Monday.
Of course the first thing I will do is check if the factory image package is different.

picree · 08-26-2016, 12:46 PM

@knc1 and @NiLuJe:

Thanks so much for your help. If I have any other issues related to CRP I will post. I may wait to reinstall it until there is more confirmation the issues here were not related to the builds but simply that most of the restarting was with the cover or usb cable attached.

Side thought: Does this mean if a user has installed CRP and then restarts the Oasis with the cover on the Kindle will flip into Diagnostic mode? That might not be the intended behavior.

knc1 · 08-26-2016, 04:09 PM

You are the only one who can tell us what is happening.

Neither I nor NiLuJe have an Oasis to play with.

No, that is not the intended operation of the CRP -
But keep in mind, the Oasis is the first Kindle since the K3 that had a cover wired to the electronics.

picree · 08-26-2016, 05:52 PM

It turns out the DO_FACTORY_RESTORE didn't set the firmware back to 5.7.4 but it simply wiped the user space leaving the Oasis is still on 5.8.2. To make sure things were well I Restarted it (oopps...with the cover on) and it went back into the diagnostic screen (of course). Removing the cover and running EXIT DISABLE takes me back to user space like it should. So that seems to be working.

I guess that means it is still jailbroken because CRP is working? What would you recommend as a path forward? Drop back to 5.7.4, re-jailbreak, re-hotfix? start over and bring it up to 5.8.1.0.1? Or move forward from here?

In the end I think the issue with being stuck in Diagnostics was because I didn't make sure to remove both the cover and any dangling USB cables. Now it seems to work. All the extensions I had seemed to work. Thoughts?

knc1 · 08-26-2016, 06:19 PM

As I posted above, all you should have to do is re-install the hotfix.

DO NOT run or allow OTA to run an update package until you do re-install the hotfix.

- - - -

Factory restore re-initializes both of the user spaces.

It does not return to original - this system does not have an original image stored to return to - not enough storage.

picree · 08-26-2016, 06:24 PM

Quote:

Originally Posted by knc1

As I posted above, all you should have to do is re-install the hotfix.

DO NOT run or allow OTA to run an update package until you do re-install the hotfix.

Well, the system tells me the hotfix .bin is an invalid update so I guess I'll have to drop back to 5.7.4 and start from the beginning. Unless you say no I plan to do that later this evening.

knc1 · 08-26-2016, 06:46 PM

Quote:

Originally Posted by picree

Well, the system tells me the hotfix .bin is an invalid update so I guess I'll have to drop back to 5.7.4 and start from the beginning. Unless you say no I plan to do that later this evening.

How are you trying to install it?

Follow step #6 spoiler.

08-26-2016, 11:19 AM	#18
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	Just to double-check, because the idme thing should definitely have done the trick: Make sure you do not reboot with the device plugged to anything (that may include the cover and/or any OTG stuff on the Oasis). Was that the first time you rebooted since installing the CRP? (I don't think the false positives are that severe, but you might want to check the system logs to check that it's not actually the CRP that's re-throwing you back in diags mode for some reason...). From the look I had at an Oasis rescue binary, it should be exiting diags properly, IIRC, but, again, that's from the outside, and @knc1 has seen a few misbehaving diags build over the years, so that's not an entirely uncommon sight (but on those builds, running idme manually over SSH does the trick). Last edited by NiLuJe; 08-26-2016 at 11:24 AM.

08-26-2016, 12:46 PM	#25
picree Connoisseur Posts: 93 Karma: 10000 Join Date: Apr 2016 Device: Kindle Oasis KOA FW 5.13.3 JB	@knc1 and @NiLuJe: Thanks so much for your help. If I have any other issues related to CRP I will post. I may wait to reinstall it until there is more confirmation the issues here were not related to the builds but simply that most of the restarting was with the cover or usb cable attached. Side thought: Does this mean if a user has installed CRP and then restarts the Oasis with the cover on the Kindle will flip into Diagnostic mode? That might not be the intended behavior. Last edited by picree; 08-26-2016 at 02:44 PM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Kindle can't start after entering DIAG mode	Mr.Samuel	Kindle Developer's Corner	15	05-21-2016 06:17 AM
Does pw2 have a diag mode like kinde4?	cxy560	Kindle Developer's Corner	1	02-04-2014 03:58 AM
Kindle Touch bricked in diag mode	tommytomtom	Kindle Developer's Corner	3	09-05-2012 12:17 PM
PRS-T1 Stuck in Landscape mode	Jcee	Sony Reader	2	01-07-2012 10:49 PM
Need help! Stuck in udating mode	SuzInKS	enTourage Archive	9	04-21-2010 06:10 PM

08-26-2016, 09:04 AM	#16
picree Connoisseur Posts: 93 Karma: 10000 Join Date: Apr 2016 Device: Kindle Oasis KOA FW 5.13.3 JB	OK, I will do all/most of that when I get back tonight. But if that doesn't work is that to say that the device is "bricked"? When you say export USB area you just mean run the diags command called USB EXPORT right? There is another command called USB DOWNLOAD. from the description ("USB Bundle Install") I wondered if that was the command that would trigger a factory reinstall if the .bin was in the root folder.

08-26-2016, 11:37 AM	#20
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@picree: Rebooting while plugged in will definitely throw you back in to diags, that's just CRP doing its job . As for the reboot after an install, that doesn't happen if you installed it through MRPI, which you probably did. (That's relevant here because there may be an issue with the CRP checks on the Oasis, which are currently a little greedy, they probably match on more conditions than they should, hence my comments about the cover and OTG [i.e., the Voice thingy dongle]). They definitely shouldn't match with a "naked" Oasis, but since all of this was mostly blind-coded, I might have screwed things up.

08-26-2016, 11:52 AM	#21
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	Remove the cover - That external battery might be triggering the CRP to throw you back into diags. But the message so far about having to use the serial port to exit has been true. Even some builds of the K3 diags where that way. (I know, I have one of them - I was locked out for months.)

08-26-2016, 12:26 PM	#24
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	This is the first time in years that we have had the freedom to "start over" on nearly any model of Kindle by using the factory firmware package. You might just have to re-install the hotfix package. I have a KT3W from the most recent production run arriving Monday. Of course the first thing I will do is check if the factory image package is different.

08-26-2016, 04:09 PM	#26
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	You are the only one who can tell us what is happening. Neither I nor NiLuJe have an Oasis to play with. No, that is not the intended operation of the CRP - But keep in mind, the Oasis is the first Kindle since the K3 that had a cover wired to the electronics.

08-26-2016, 05:52 PM	#27
picree Connoisseur Posts: 93 Karma: 10000 Join Date: Apr 2016 Device: Kindle Oasis KOA FW 5.13.3 JB	It turns out the DO_FACTORY_RESTORE didn't set the firmware back to 5.7.4 but it simply wiped the user space leaving the Oasis is still on 5.8.2. To make sure things were well I Restarted it (oopps...with the cover on) and it went back into the diagnostic screen (of course). Removing the cover and running EXIT DISABLE takes me back to user space like it should. So that seems to be working. I guess that means it is still jailbroken because CRP is working? What would you recommend as a path forward? Drop back to 5.7.4, re-jailbreak, re-hotfix? start over and bring it up to 5.8.1.0.1? Or move forward from here? In the end I think the issue with being stuck in Diagnostics was because I didn't make sure to remove both the cover and any dangling USB cables. Now it seems to work. All the extensions I had seemed to work. Thoughts?

08-26-2016, 06:19 PM	#28
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	As I posted above, all you should have to do is re-install the hotfix. DO NOT run or allow OTA to run an update package until you do re-install the hotfix. - - - - Factory restore re-initializes both of the user spaces. It does not return to original - this system does not have an original image stored to return to - not enough storage.

Advert

Advert