Uboot needed for pw2

[Merlin09]

Status update :

I flashed both kernels and the diags partition, then rebooted in diags, with no luck, BUT, and it's a big but (easy one, but I couldn't skip it...), I was able while booting in diags mode to access recovery.

The battery error is gone.

I was able, with the recovery method, to flash the 4.3.2 initial firmware, but it doesn't to boot. I have another "your kindle needs repair" message, but no error indication.

I wanted to try and install the last 5.8 firmware from Amazon, but the Kindle doesn't accept it from recovery.

I have no clue as to why the firmware doesn't flash, but for the 4.3.2, maybe it has to do with the idme variables still cleared (mainly both mac addresses are unset, along with the postboot variable, which I have no idea how to fill).

Do you know of a way to find out both Mac addresses of the device, and what I should have in the postboot variable?

[knc1]

Is firmware version 4.3.2 a typo?
That is for the K4 (K4 'non-touch') model.

Did you mean 5.4.3.2 factory use only version?
All de-brick and recovery directions on this site are written only for the consumer use firmware images. Nothing was ever tested or intended to be used with the factory use only firmware images.

Best that you post a link to what you actually used.

[Merlin09]

Yes, it was a typo, I forgot the 5. I used this firmware from the jailbreak post :

https://www.adrive.com/public/EDj8zF...in/?ai=2g2g4bb

The second I tried but that was rejected by the recovery update mechanism was this one :

https://www.amazon.com/gp/help/custo...deId=201307450

[knc1]

After you put the first one (the factory image) on the device -
You should have been able to reset the bootmode to 'main';
Booted to 'main';
And use the regular Amazon install process, rather than the 'recovery' process.

I don't know why the recovery mode would reject the usual customer update.

Neither of those would have touched the 'diags' system, that should still be a copy of what you got off of your wife's PW-2.

= = = = =

A basic summary (mostly speculation, but supported by actual usages):

*) The eMMC chip is partitioned and has the initial (model independent) firmware loaded (u-boot and 'diags' system) while still on the tape.
(This is so the devices on the tape reel are not dedicated to a particular model device and the devices that do chip-on-tape writes are very fast.)

*) The eMMC chip is assembled to the board.

*) The board has the diagnostics pre-installed on the eMMC chip run (you can find the result files of all the tests as erased files in user storage).

*) For devices that pass all tests, the factory 'production use' main firmware image is installed.
This means that the 'factory initial' firmware image is not dependent on device specific information on the device (because it isn't there yet).
It also means those images can be used by the people/firms that re-furbish used Kindles, in any operational state.

Note: this is also the reason those firmware images can be used to 'jail break' a Kindle running consumer firmware - they can be written and run on a bare board.

*) The motherboard is then combined with a display/frame.

*) Now a final programming (and maybe tests) are done, which sets the device specific information outside of the partitioned area.

*) Then the 'release' consumer firmware is installed.

From the above -
I would have to say once you install the 'factory initial (as we call it)' firmware image, you need to boot that and 'idme ....' all of the device specific information.
Once that is done, the device will install a normal Amazon update in a normal manner.

(of course, you might just want to jailbreak your device before loading the consumer firmware image)

All of the above is mostly speculation but is based on knowledge of modern, high-speed, production of electronic devices. Without that production engineering background (mine), the current jail break procedure would never have been found.
It is also why it took us nearly a year and a half to come up with the procedure.

[Merlin09]

That's indeed what I expected to see. I don't know why it doesn't work. I can boot to main... But it doesn't boot at all.

At least I can have access to the user partition over USB

Do you think my idme problem could be part of the problem? My understanding was that some firmware versions were bringing them back, do you know about it?

It's bothering since I didn't wrote the mac addresses down before everything went mad (didn't expected it to go mad at all...)

OK, so basically I will have to guess the mac addresses and hope for the best, since I have no way to find the real ones, won't I?

[knc1]

Originally Posted by Merlin09

That's indeed what I expected to see. I don't know why it doesn't work. I can boot to main... But it doesn't boot at all.

At least I can have access to the user partition over USB

Do you think my idme problem could be part of the problem? My understanding was that some firmware versions were bringing them back, do you know about it?

It's bothering since I didn't wrote the mac addresses down before everything went mad (didn't expected it to go mad at all...)

OK, so basically I will have to guess the mac addresses and hope for the best, since I have no way to find the real ones, won't I?

I was still writing my post when you posted this, re-read the above post, I think I answered your questions.

The mac adress is not all that important - use your wife's with a different device id field (the vendor field will be the same).
Say: Wife + 7 or something like that.

[Merlin09]

Oh yes, thank you. Do you know what the postboot variable should be set to in idme?

I'd say main but I'm a little reluctant, seeing how I nearly messed up my pw2

---Edit - -

Don't worry, I'll read it on my wife's, I just read the post about idme mechanisms, it will be easy over telnet

[knc1]

Originally Posted by Merlin09

Oh yes, thank you. Do you know what the postboot variable should be set to in idme?

I'd say main but I'm a little reluctant, seeing how I nearly messed up my pw2

No, I don't - check what you wife's is set to.

I think that controls the 'run once after update' processing (which is where are 'bridge code' is hooked into - the processing, not the variable).

[Merlin09]

When, after flashing the firmware, I go back to main bootmode (FYI, postmode is set to normal), it doesn't boot. Here is the log:

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2017.03.05 17:28:37 =~=~=~=~=~=~=~=~=~=~=~=
/-\|/-\|/-/-\|/-[  122.065769] bcut: C def:pcut:wario pending 15 second battery cut:
\|/-


U-Boot 2009.08-lab126 (Apr 23 2014 - 01:01:24)


CPU: Freescale i.MX6 family TO0.0 at 996 MHz

Temperature:   28 C, calibration data 0x5524e15f

mx6sl pll1: 996MHz

mx6sl pll2: 528MHz

mx6sl pll3: 480MHz

mx6sl pll8: 50MHz

ipg clock     : 66000000Hz

ipg per clock : 66000000Hz

uart clock    : 80000000Hz

cspi clock    : 60000000Hz

ahb clock     : 132000000Hz

axi clock   : 198000000Hz

emi_slow clock: 22000000Hz

ddr clock     : 396000000Hz

usdhc1 clock  : 198000000Hz

usdhc2 clock  : 198000000Hz

usdhc3 clock  : 198000000Hz

usdhc4 clock  : 198000000Hz

MMC:  FSL_ESDHC: 0,FSL_ESDHC: 1,FSL_ESDHC: 2

Board: Pinot WFO

Boot Reason: [ POR ]

Boot Device: NAND

Board Id: xxxxxxxxxxxxxxxx

S/N: xxxxxxxxxxxxxx

I2C:   ready

DRAM:  256 MB

Using default environment


In:    serial

Out:   serial

Err:   serial

Quick Memory Test 0x80000000, 0xfff0000

POST done in 60 ms

Battery voltage: 3895 mV


Hit any key to stop autoboot:  1  0 

## Booting kernel from Legacy Image at 80800000 ...

   Image Name:   Linux-3.0.35-lab126

   Image Type:   ARM Linux Kernel Image (uncompressed)

   Data Size:    2426044 Bytes =  2.3 MB

   Load Address: 80008000

   Entry Point:  80008000

   Verifying Checksum ... OK

   Loading Kernel Image ... OK

OK


Starting kernel ...


[    0.095347] boot: C def:bcut:batterycut=1
[    0.268135] LPDDR2 MfgId: 0x1 [Samsung]
[    0.272029] 
[    0.272032] just text: vaddr 0xc011e9bc, va 0xc011e200 pa 0x801000c3 attr 0x6
[    0.280499] 
[    0.280502] nmx6sl_wfi_iram: vaddr 0xd081a000, va 0xd081a200 pa 0x902043 attr 0x2
[    0.289474] 
[    0.289476] mx6sl_ddr: vaddr 0xd0852000, va 0xd0852200 pa 0x903043 attr 0x2
[    0.297936] 
[    0.297939] mx6sl_iomux: vaddr 0xf40e0000, va 0xf40e0200 pa 0x20110c3 attr 0x149
[    0.306832] 
[    0.306834] ANATOP: vaddr 0xf40c8000, va 0xf40c8200 pa 0x20110c3 attr 0x149
[    0.315292] 
[    0.315294] CCM: vaddr 0xf40c4000, va 0xf40c4200 pa 0x20110c3 attr 0x149
[    0.323491] 
[    0.323494] MMDC_P0: vaddr 0xf41b0000, va 0xf41b0200 pa 0x21110c3 attr 0x149
[    0.332038] 
[    0.332041] L2: vaddr 0xf2a02000, va 0xf2a02200 pa 0xa02043 attr 0x149
[    0.340064] 
[    0.340067] arm perif: vaddr 0xf2a00000, va 0xf2a00200 pa 0xa00043 attr 0x149
3.0.35-lab126 #1 Wed Apr 23 01:26:01 PDT 2014 armv7l
[    0.546318] FAT-fs (loop1): bogus logical sector size 65535
[    1.580233] imx_epdc_fb imx_epdc_fb: Failed to load fw! (err -2) Trying fallback fw
[    3.105553] panel_get_upd_modes: Unknown waveform mode. Using MODE_07!INFO:Loaded module /lib/modules/mxc_epdc_fb.ko  (85104 bytes)
Press [ENTER] for recovery menu...       0 //-\|/-\|/-/-\|/-

and it stays stuck there.
any idea on what could cause this?

[knc1]

loop1 is part of the fs stack that will become user (USB) storage.

Have you ever done anything that might have tried to re-format it?
(Because it takes non-standard format options - ns on windows)

= = = = =

It should "just sit there" while it re-formats user storage.
Which, depending on the number of bad erase blocks, might take a few days.
Leave it on a wall charger during that time, none of the Kindles have enough battery capacity to re-format user storage if bad erase blocks are present.

= = = = =

Are you using the write-readback-verify tools when you transfer things to the Kindle?
As you recall, the original suspect was eMMC hardware errors.

[Merlin09]

No, I initialized it with the recovery menu. On the last try I pressed O to format it, then e to use it via USB.
When the copy is finished, I press done in the menu, should I rather eject it from the computer side, and I keep the USB cable plugged, I guess it's alright?

[knc1]

Yes, always 'eject' (or 'safely remove' OS dependent terms).
Then always remove the USB cable, with an OTG port (which it is) be sure that no cable is plugged into the Kindle (you don't want the host/device sensing of the cable's 5th lead to screw things up).

= = = = =

The recovery menu formatter **should** have gotten things correct (and not produced that funky numeric value).

= = = = =

You may have to struggle along without me, I have two of my three RAID arrays on this computer that will not come on-line.
And there is no telling what else may fail once I turn this box off to fix the problem(s).

[Merlin09]

OK. I will try again, and I will remove the cable and eject it properly.

Good luck with your computer.

[Merlin09]

Hello, sorry for the long silence, but I had a lot to deal with in my "real" life.

I tried to flash again with the recovery menu (first I, then O, and E, copy update file via usb)

I made two tries: first, I then pressed U to update, it stays stuck at nearly 90%

data.stgz 43380562   [#########:::::::::::::::::::::::::::::]
data.stgz 43511594   [#########:::::::::::::::::::::::::::::]
data.stgz 43642626   [#########:::::::::::::::::::::::::::::]
data.stgz 43773658   [#########:::::::::::::::::::::::::::::]
data.stgz 43904690   [#########:::::::::::::::::::::::::::::]
data.stgz 44035722   [#########:::::::::::::::::::::::::::::]
data.stgz 44166754   [#########:::::::::::::::::::::::::::::]
data.stgz 44297786   [#########:::::::::::::::::::::::::::::]
data.stgz 44428818   [#########:::::::::::::::::::::::::::::]
data.stgz 44559850   [#########:::::::::::::::::::::::::::::]
data.stgz 44690882   [#########:::::::::::::::::::::::::::::]
data.stgz 44821914   [#########:::::::::::::::::::::::::::::]
data.stgz 44952946   [#########:::::::::::::::::::::::::::::]
data.stgz 45083978   [#########:::::::::::::::::::::::::::::]
data.stgz 45215010   [#########:::::::::::::::::::::::::::::]
data.stgz 45346042   [#########:::::::::::::::::::::::::::::]
data.stgz 45477074   [#########:::::::::::::::::::::::::::::]
data.stgz 45608106   [#########:::::::::::::::::::::::::::::]
data.stgz 45739138   [#########:::::::::::::::::::::::::::::]
data.stgz 45870170   [#########:::::::::::::::::::::::::::::]
data.stgz 46001202   [#########:::::::::::::::::::::::::::::]
data.stgz 46132234   [#########:::::::::::::::::::::::::::::]
data.stgz 46263266   [#########:::::::::::::::::::::::::::::]
data.stgz 46394298   [#########:::::::::::::::::::::::::::::]
data.stgz 46525330   [#########:::::::::::::::::::::::::::::]
data.stgz 46656362   [#########:::::::::::::::::::::::::::::]
data.stgz 46787394   [#########:::::::::::::::::::::::::::::]
data.stgz 46918426   [#########:::::::::::::::::::::::::::::]
data.stgz 47049458   [#########:::::::::::::::::::::::::::::]
data.stgz 47180490   [##########::::::::::::::::::::::::::::]
data.stgz 47311522   [##########::::::::::::::::::::::::::::]
data.stgz 47442554   [##########::::::::::::::::::::::::::::]
data.stgz 47573586   [##########::::::::::::::::::::::::::::]
data.stgz 47704618   [##########::::::::::::::::::::::::::::][  302.677698] 
[  302.677707] ADC value out of thermistor range! setting display temp to 3 deg C

data.stgz 47835650   [##########::::::::::::::::::::::::::::]
data.stgz 47966682   [##########::::::::::::::::::::::::::::][  362.836124] 
[  362.836146] ADC value out of thermistor range! setting display temp to 3 deg C
[  422.996033] 
[  422.996041] ADC value out of thermistor range! setting display temp to 3 deg C
[  449.349825] KERNEL: I pmic:charger chgina::charger connected
[  449.372419] otg udc vbus rising wakeup
[  449.377965] try_wake_up_udc: udc out low power mode
[  449.831409] g_file_storage gadget: high speed config #1
[  483.155303] 
[  483.155310] ADC value out of thermistor range! setting display temp to 3 deg C
[  543.315279] 
[  543.315287] ADC value out of thermistor range! setting display temp to 3 deg C
[  603.475267] 
[  603.475275] ADC value out of thermistor range! setting display temp to 3 deg C
[  663.635284] 
[  663.635292] ADC value out of thermistor range! setting display temp to 3 deg C
[  723.795085] 
[  723.795093] ADC value out of thermistor range! setting display temp to 3 deg C

and that's it. I made a second try after an hard reboot, but instead of pressed u, I exit the diags menu, when I reboot, the system detects the update file and installs it, with success, but I'm back to previous error (partitionning it seems).

I'm running out of ideas... do you have any insight to help me?

And by the way, did you manage to save your data with your raid mostly out ?

[knc1]

I am pretty certain now that it is spare parts.

- - - - -

All data is safe, but neither of the arrays are up.
Something serious has died here.
To much Mobileread most likely did it.