PW4 keep battery at 50% in long-term usage

January 31, 2021, 6:05 am

≫ Next: getting started with my old PW1 (5.6.1.1)

≪ Previous: KV charging issue at long-term usage

Hello,
I set up a kindle PW4 as status display for my FHEM-Server. Known from my Voyage I searched in filesystem for files like "allow_charging"/"charging" to alternating de-/activate charging to keep at 50% for protection of the battery. But all files I have found on PW4 are read-only and only GIVE the state.
Have anyone figured out a way to do this?

↧

getting started with my old PW1 (5.6.1.1)

January 31, 2021, 3:54 pm

≫ Next: My new Kindle 8th gen it's weird!!

≪ Previous: PW4 keep battery at 50% in long-term usage

Hi!

I just joined up, because I switched my e-reading workflow with an iPad to start weaning myself of Amazon reliance more. Since I now have a PaperWhite 1 hanging around unused I thought I'd check into jailbreak options and trade-offs. Note that this device has never been jailbroken.

My Kindle's vitals:

S/N: B024 1501 2394 0QA8
Firmware: 5.6.1.1 (2689890035)

I've been reading a number of related forum articles, and thought I'd take a stab at checking what I think I've learned to see if I'm thinking about it correctly.

Here goes (just seeking confirmation or correction):

1) Need to downgrade first, e.g. to 5.3.9 (per PW1 downgrade thread), because PW1 5.6.1.1 firmware doesn't like jailbreaks?

2) Once downgraded, follow jailbreak instructions on the sticky post?

3) Once jailbroken, keep Wi-Fi off to avoid automatic upgrades?

4) Need to sideload and de-DRM ebooks in order to read things like Overdrive library books, etc.?

5) What else might I miss?

Do I have the general idea?

I'm a developer, know Calibre and Python, and don't fear running scripts, etc., but I don't want to get "cocky". ;)

Thanks!

↧

My new Kindle 8th gen it's weird!!

January 31, 2021, 4:32 pm

≫ Next: Kindle PW2 is write protected

≪ Previous: getting started with my old PW1 (5.6.1.1)

I already had other Kindles and this one I received from a friend of mine who said he found it in the trash, he had a demo mode sticker, so I came to the forum to solve this problem, but mine is different from the others, besides being in another one language (with the help of the google translator i found that it is in brazilian portuguese) it is on a strange screen, apparently it is explaining some kindle functions, i already tried restarting holding the power button for 40 seconds up to 5 minutes and it came to nothing, as the forum has already helped me to solve problems of my other kindles resolve to get together to share my problem that I don't find a solution.

Attached Thumbnails

Click image for larger version

Name: photo_2021-01-31_21-21-37.jpg
Views: N/A
Size: 72.1 KB
ID: 185129

Click image for larger version

Name: photo_2021-01-31_21-21-41.jpg
Views: N/A
Size: 66.9 KB
ID: 185130

↧

Kindle PW2 is write protected

February 1, 2021, 11:23 am

≫ Next: PW3 Jailbreak option for PW3 on FW 5.13.3--not yet?

≪ Previous: My new Kindle 8th gen it's weird!!

My PW2 worked fine until I trieded to copy some new books with Calibre. During the copy process the USB connection was interrupted because of a bad connector. The new books were visible on the Kindle but the reader was not able to open them. Also some other menue items brings some errors.
I decided to do a fatory reset by the kindle menue. After reboot every the file structure and the behavior was same as before. Including the Wifi setup.

I opened the Kindle and connected the serial port as seen in some tutorials. I Installed necessary driver and tools to get connected. I tried the following things:
I copied some images via fastboot to the Kindle. I saw that the data are transferd an written. After reboot nothing has changed.
I logged in as root and did some changes on the file system like mkdir. But after reboot is everthing gone.
The following show a part of the boot process:

Code:

U-Boot 2009.08-lab126 (Sep 25 2019 - 00:37:32)



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

Temperature:   31 C, calibration data 0x5514da5f

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: 02722011423615EW

S/N: 9017XXXXXXXXXXXX

I2C:   ready

DRAM:  256 MB

Using default environment



In:    serial

Out:   serial

Err:   serial

Quick Memory Test 0x80000000, 0xfff0000

POST done in 57 ms

Battery voltage: 4078 mV



Hit any key to stop autoboot:  0

uboot >

uboot > bootm 0xE41000

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

   Image Name:   Linux-3.0.35-lab126

   Image Type:   ARM Linux Kernel Image (uncompressed)

   Data Size:    2420504 Bytes =  2.3 MB

   Load Address: 80008000

   Entry Point:  80008000

   Verifying Checksum ... OK

   Loading Kernel Image ... OK

OK



Starting kernel ...



[    0.000000] Linux version 3.0.35-lab126 (jenkins-official@sjc10-jbuild10) (collect2: ld returned 1 exit status) #1 Wed Apr 23 16:52:30 PDT 2014

[    0.000000] CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c53c7d

[    0.000000] CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache

[    0.000000] Machine: Freescale i.MX 6SoloLite based Wario Board

[    0.000000] Ignoring unrecognised tag 0x54410011

[    0.000000] Will try to place printk log at 8fffc000

[    0.000000] Memory policy: ECC disabled, Data cache writeback

[    0.000000] CPU identified as i.MX6SoloLite, silicon rev 1.2

[    0.000000] On node 0 totalpages: 65536

[    0.000000] free_area_init_node: node 0, pgdat c04dcc94, node_mem_map c2000000

[    0.000000]   DMA zone: 64 pages used for memmap

[    0.000000]   DMA zone: 0 pages reserved

[    0.000000]   DMA zone: 8128 pages, LIFO batch:0

[    0.000000]   Normal zone: 448 pages used for memmap

[    0.000000]   Normal zone: 56896 pages, LIFO batch:15

[    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768

[    0.000000] pcpu-alloc: [0] 0

[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024

[    0.000000] Kernel command line: rootwait log_pos_goal=0x8fffc000 console=ttymxc0,115200 root=/dev/mmcblk0p2 ro ip=off debug video=mxcepdcfb:E60,bpp=8,x_mem=3M

[    0.000000] Prink buffer will be relocated to physical address: 8fff2000

[    0.000000] log_buf_len: 32768

[    0.000000] early log buf free: 31286(95%)

[    0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)

[    0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)

[    0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)

[    0.000000] Memory: 256MB = 256MB total

[    0.000000] Memory: 254652k/254652k available, 7492k reserved, 0K highmem

[    0.000000] Virtual kernel memory layout:

[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)

[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)

[    0.000000]     DMA     : 0xfde00000 - 0xffe00000   (  32 MB)

[    0.000000]     vmalloc : 0xd0800000 - 0xf2000000   ( 536 MB)

[    0.000000]     lowmem  : 0xc0000000 - 0xd0000000   ( 256 MB)

[    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)

[    0.000000]       .init : 0xc0008000 - 0xc010b000   (1036 kB)

[    0.000000]       .text : 0xc010b000 - 0xc04aa000   (3708 kB)

[    0.000000]       .data : 0xc04aa000 - 0xc04dd7c0   ( 206 kB)

[    0.000000]        .bss : 0xc04dd7e4 - 0xc0504540   ( 156 kB)

[    0.000000] SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1

[    0.000000] NR_IRQS:624

[    0.000000] MXC GPIO hardware

[    0.000000] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 178956ms

[    0.000000] arm_max_freq=1GHz

[    0.000000] MXC_Early serial console at MMIO 0x2020000 (options '115200')

[    0.000000] bootconsole [ttymxc0] enabled

[    0.000000] Console: colour dummy device 80x30

[    0.263660] Calibrating delay loop... 1987.37 BogoMIPS (lpj=9936896)

[    0.321984] pid_max: default: 32768 minimum: 301

[    0.326867] Mount-cache hash table entries: 512

[    0.331777] CPU: Testing write buffer coherency: ok

[    0.336805] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available

[    0.351754] print_constraints: dummy:

[    0.355705] NET: Registered protocol family 16

[    0.363949] print_constraints: vddpu: 725 <--> 1300 mV at 700 mV fast normal

[    0.371533] print_constraints: vddcore: 725 <--> 1300 mV at 1475 mV fast normal

[    0.379230] print_constraints: vddsoc: 725 <--> 1300 mV at 1475 mV fast normal

[    0.386893] print_constraints: vdd2p5: 2000 <--> 2775 mV at 2400 mV fast normal

[    0.394621] print_constraints: vdd1p1: 800 <--> 1400 mV at 1100 mV fast normal

[    0.402298] print_constraints: vdd3p0: 2625 <--> 3400 mV at 3000 mV fast normal

[    0.411186] LAB126 Board id - 02722011423615EW

[    0.419708] hw-breakpoint: found 6 breakpoint and 1 watchpoint registers.

[    0.426549] hw-breakpoint: 1 breakpoint(s) reserved for watchpoint single-step.

[    0.433883] hw-breakpoint: maximum watchpoint size is 4 bytes.

[    0.439755] L310 cache controller enabled

[    0.443780] l2x0: 16 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x02030000, Cache size: 262144 B

[    0.460050] bio: create slab <bio-0> at 0

[    0.467671] max77696> regulator init

[    0.472147] spi_imx imx6q-ecspi.0: probed

[    0.476729] usbcore: registered new interface driver usbfs

[    0.482339] usbcore: registered new interface driver hub

[    0.487845] usbcore: registered new device driver usb

[    0.494989] Reboot Reason - Standard Reporting

[    0.499464] kernel: I max77696-irq:evtrcrd: evt=RSTIN_PRSTRT: nRSTIN Partial Restart - likely watchdog

[    0.508794] Reboot Reason - Metric Framework Reporting

[    0.513952] kernel: kernel_metric_generic,counter,event_recorder,ercflags,RSTIN_PRSTRT,1,

[    0.522149] Reboot Reason - Legacy Metric Reporting

[    0.527041] boot: C def:rst:reset=watchdog

[    0.532742] MAX77696 TOPSYS 1.0.0 Installed

[    0.539599] max77696-gpio max77696-gpio.0: gpio#0 -- -- func-0 in

[    0.547097] max77696-gpio max77696-gpio.0: gpio#1 -- -- func--1 in

[    0.554840] max77696-gpio max77696-gpio.0: gpio#3 -- -- func-0 in

[    0.562891] MAX77696 GPIO Driver 1.0.0 Installed

[    0.568586] buck mode: 4

[    0.571898] buck mode: 4

[    0.575373] print_constraints: max77696_buck1: 900 <--> 1300 mV at 1250 mV fast normal idle standby

[    0.584983] buck mode: 4

[    0.588458] print_constraints: max77696_buck1dvs: 600 <--> 1300 mV at 900 mV fast normal idle standby

[    0.598258] buck mode: 4

[    0.601527] buck mode: 4

[    0.604998] print_constraints: max77696_buck2: 900 <--> 1300 mV at 1200 mV fast normal idle standby

[    0.614605] buck mode: 4

[    0.618081] print_constraints: max77696_buck2dvs: 600 <--> 1300 mV at 900 mV fast normal idle standby

[    0.627868] print_constraints: max77696_buck3: 600 <--> 3387 mV at 1300 mV fast normal idle standby

[    0.637654] buck mode: 4

[    0.640920] buck mode: 4

[    0.644185] print_constraints: max77696_buck4: 1200 mV fast normal idle standby

[    0.652043] buck mode: 4

[    0.655518] print_constraints: max77696_buck5: 600 <--> 3387 mV at 1800 mV fast normal idle standby

[    0.665136] buck mode: 4

[    0.668610] print_constraints: max77696_buck6: 600 <--> 3387 mV at 3200 mV fast normal idle standby

[    0.677720] MAX77696 Buck Regulators Driver 1.0.1 Installed

[    0.684087] print_constraints: max77696_ldo1: 800 <--> 3950 mV at 3300 mV normal idle standby

[    0.693216] print_constraints: max77696_ldo2: 800 <--> 3950 mV at 3000 mV normal idle standby

[    0.702306] print_constraints: max77696_ldo3: 800 <--> 3950 mV at 2500 mV normal idle standby

[    0.711426] print_constraints: max77696_ldo4: 800 <--> 2375 mV at 1800 mV normal idle standby

[    0.720493] print_constraints: max77696_ldo5: 800 <--> 2375 mV at 1800 mV normal idle standby

[    0.729610] print_constraints: max77696_ldo6: 800 <--> 3950 mV at 3200 mV normal idle standby

[    0.738691] print_constraints: max77696_ldo7: 800 <--> 3950 mV at 3200 mV normal idle standby

[    0.747801] print_constraints: max77696_ldo8: 800 <--> 2375 mV at 1100 mV normal idle standby

[    0.756867] print_constraints: max77696_ldo9: 800 <--> 2375 mV at 1100 mV normal idle standby

[    0.765998] print_constraints: max77696_ldo10: 2400 <--> 5550 mV at 5200 mV normal idle standby

[    0.775497] MAX77696 Linear Regulators Driver 1.0.2 Installed

[    0.781854] print_constraints: max77696_lsw1:

[    0.786673] print_constraints: max77696_lsw2:

[    0.791434] print_constraints: max77696_lsw3:

[    0.796174] print_constraints: max77696_lsw4:

[    0.800680] MAX77696 Load Switches Driver 1.0.0 Installed

[    0.807299] print_constraints: max77696-display:

[    0.812777] print_constraints: max77696-vcom:

[    0.817554] print_constraints: max77696-vee:

[    0.822278] print_constraints: max77696-vneg:

[    0.827060] print_constraints: max77696-vpos:

[    0.831816] print_constraints: max77696-vddh:

[    0.837302]

[    0.837305] EPD vreg probe complete!

[    0.842948] print_constraints: max77696_vddq: 240 <--> 984 mV at 600 mV

[    0.849727] MAX77696 LPDDR2 Termination Supply Driver 1.0.1 Installed

[    0.857453] MAX77696 I2C Driver 1.0.0 Installed

[    0.864536] i2c-core: driver [max17135] using legacy suspend method

[    0.870822] i2c-core: driver [max17135] using legacy resume method

[    0.877068] Switching to clocksource mxc_timer1

[    0.892144] NET: Registered protocol family 2

[    0.896603] IP route cache hash table entries: 2048 (order: 1, 8192 bytes)

[    0.903703] TCP established hash table entries: 8192 (order: 4, 65536 bytes)

[    0.910883] TCP bind hash table entries: 8192 (order: 3, 32768 bytes)

[    0.917416] TCP: Hash tables configured (established 8192 bind 8192)

[    0.923793] TCP reno registered

[    0.926946] UDP hash table entries: 256 (order: 0, 4096 bytes)

[    0.932808] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)

[    0.939431] NET: Registered protocol family 1

[    0.944161] RPC: Registered named UNIX socket transport module.

[    0.950099] RPC: Registered udp transport module.

[    0.954835] RPC: Registered tcp transport module.

[    0.959551] RPC: Registered tcp NFSv4.1 backchannel transport module.

[    0.970227] etb: probe of etb failed with error -2

[    0.975273] etm: probe of etm.0 failed with error -2

[    0.980511] Static Power Management for Freescale i.MX6

[    0.985774] wait mode is enabled for i.MX6

[    0.990057] cpaddr = d0820000 suspend_iram_base=d081c000

[    0.995446] PM driver module loaded

[    0.999202] IMX usb wakeup probe

[    1.002474] the wakeup pdata is 0xce1387c0

[    1.006919] IMX usb wakeup probe

[    1.010168] the wakeup pdata is 0xce1388c0

[    1.014485] cpu regulator mode:ldo_bypass

[    1.018706] _regulator_get: get() with no identifier

[    1.023699] mx6_cpu_regulator_init: failed to get pu regulator

[    1.029744] i.MXC CPU frequency driver

[    1.046710] squashfs: version 4.0 (2009/01/31) Phillip Lougher

[    1.053768] msgmni has been set to 497

[    1.057882] io scheduler noop registered

[    1.061922] io scheduler cfq registered (default)

[    1.067136] MAX77696 Backlight Driver 1.0.0 Installed

[    1.072987] imx-sdma imx-sdma: loaded firmware 1.1

[    1.082366] imx-sdma imx-sdma: initialized

[    1.256565] Serial: IMX driver

[    1.388713] console [ttymxc0] enabled, bootconsole disabled

[    1.388713] console [ttymxc0] enabled, bootconsole disabled

[    1.404208] loop: module loaded

[    1.407419] MAX77696 32kHz Oscillator Driver 1.0.0 Installed

[    1.413749] input: max77696-onkey as /devices/platform/imx-i2c.0/i2c-0/0-003c/max77696-onkey.0/input/input0

[    1.426936] MAX77696 ONKEY Driver 1.0.0 Installed

[    1.453014] max77696-rtc max77696-rtc.0: rtc core: registered max77696-rtc.0 as rtc0

[    1.472966] max77696-rtc max77696-rtc.0: rtc core: registered max77696-rtc.1 as rtc1

[    1.502283] MAX77696 RTC Driver 1.0.2 Installed

[    1.507691] snvs_rtc snvs_rtc.0: rtc core: registered snvs_rtc as rtc2

[    1.514421] i2c /dev entries driver

[    1.522281] max77696-battery max77696-battery.0: Voltage alert     3400mV ... 4260mV

[    1.530431] max77696-battery max77696-battery.0: SOC alert         (disabled)

[    1.538482] MAX77696 Fuel Gauge Driver 1.0.0 Installed

[    1.545358] MAX77696 USB Interface Circuit Driver 1.0.0 Installed

[    1.553170] max77696-adc max77696-adc.0: ADC average rate: 32 sample(s)

[    1.559792] max77696-adc max77696-adc.0: ADC delay: 0 nsec

[    1.565295] max77696-adc max77696-adc.0: ADC cur src: 50 uA

[    1.570872] MAX77696 ADC Driver 1.0.1 Installed

[    1.576079] imx2-wdt imx2-wdt.0: IMX2+ Watchdog Timer enabled. timeout=60s (nowayout=1)

[    1.584500] sdhci: Secure Digital Host Controller Interface driver

[    1.590684] sdhci: Copyright(c) Pierre Ossman

[    1.595171] mmc0: no vmmc regulator found

[    1.600486] mmc0: SDHCI controller on platform [sdhci-esdhc-imx.1] using DMA

[    1.608622] mmc1: no vmmc regulator found

[    1.615030] mmc1: SDHCI controller on platform [sdhci-esdhc-imx.2] using DMA

[    1.622792] Registered led device: max77696-leds.0

[    1.627593] MAX77696 LED Driver #0 1.0.0 Installed

[    1.636678] Registered led device: max77696-leds.1

[    1.641476] MAX77696 LED Driver #1 1.0.0 Installed

[    1.646801] nf_conntrack version 0.5.0 (3978 buckets, 15912 max)

[    1.655511] ip_tables: (C) 2000-2006 Netfilter Core Team

[    1.660884] TCP cubic registered

[    1.664140] NET: Registered protocol family 17

[    1.668601] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4

[    1.676408] LPDDR2 MfgId: 0x1 [Samsung]

[    1.680558] Bus freq driver module loaded

[    1.686607] Bus freq driver Enabled

[    1.691088] mxc_dvfs_core_probe

[    1.698682] DVFS driver module loaded

[    1.721762] regulator_init_complete: max77696_ldo10: incomplete constraints, leaving on

[    1.737076] regulator_init_complete: max77696_ldo7: incomplete constraints, leaving on

[    1.754443] regulator_init_complete: max77696_ldo6: incomplete constraints, leaving on

[    1.769646] regulator_init_complete: max77696_buck6: incomplete constraints, leaving on

[    1.777875] regulator_init_complete: max77696_buck5: incomplete constraints, leaving on

[    1.786586] regulator_init_complete: max77696_buck2dvs: incomplete constraints, leaving on

[    1.795288] regulator_init_complete: max77696_buck1dvs: incomplete constraints, leaving on

[    1.804514] emmc: I def:mmcpartinfo:vendor=sandisk, host=mmc0:

[    1.822299] max77696-rtc max77696-rtc.0: setting system clock to 2021-01-31 09:38:39 UTC (1612085919)

[    1.851829] mmc0: new high speed DDR MMC card at address 0001

[    1.857985] mmcblk0: mmc0:0001 SEM04G 3.68 GiB

[    1.862737] mmcblk0boot0: mmc0:0001 SEM04G partition 1 2.00 MiB

[    1.868782] mmcblk0boot1: mmc0:0001 SEM04G partition 2 2.00 MiB

[    1.875750]  mmcblk0: p1 p2 p3 p4

[    1.881989]  mmcblk0boot1: unknown partition table

[    1.889128]  mmcblk0boot0: unknown partition table

[    1.898394] KERNEL: I pmic:charger chgina::charger connected

[    1.909305] MAX77696 Main Charger Driver 1.0.0 Installed

[    1.921903] MAX77696 Energy Harvester Driver 1.0.0 Installed



[    1.928457] Freeing init memory: 1036K

3.0.35-lab126 #1 Wed Apr 23 16:52:30 PDT 2014 armv7l

[    1.958672] INFO:Loaded module /lib/modules/mxc_epdc_eink.ko  (10304 bytes)

[    2.391647] add wake up source irq 104

[    3.531663] KERNEL: I pmic:fg battery id check::wario_battery_valid=1

[    4.668415] INFO:Loaded module /lib/modules/mxc_epdc_fb.ko  (83340 bytes)

[    5.004591] INFO:eink initialized... (786432 bytes)

Press [ENTER] for recovery menu..[    5.010200] INFO:!!! Checking MBR /dev/mmcblk0 !!!!

.       0 /[    5.018892] INFO:partition 2, start sector is 782336

[    5.024001] INFO:partition 3, start sector is 913408

[    5.029049] INFO:partition 4, start sector is 1044480

[    5.034186] INFO:maximizing partition 6688768 sectors

[    5.039282] INFO:*** Partition table verified for /dev/mmcblk0 ***

[    5.047610] ARC USBOTG Device Controller driver (1 August 2005)

[    5.053908] add wake up source irq 75

[    5.066836] USB Cable is already plugged in. Simulating event

[    5.075783] INFO:Loaded module /lib/modules/arcotg_udc.ko  (33320 bytes)

[    5.088770] g_file_storage gadget: File-backed Storage Gadget, version: 1 September 2010

[    5.096936] g_file_storage gadget: Number of LUNs=1

[    5.101857] dr_controller_run: udc out low power mode

[    5.106936] fsl-usb2-udc: bind to driver g_file_storage

[    5.112380] INFO:Loaded module /lib/modules/g_file_storage.ko removable=1 vendor=0x1949 product=0x0004 release=0x0100 recovery_mode=1 (37756 bytes)

[    5.431822] g_file_storage gadget: high speed config #1

Charge: 89% [#####################################################:::::]





Menu

====

3. Load MMC0 over USB storage

4. Erase MMC0

I. Initialize Partition Table (fdisk) and format FAT

O. Format and overwrite FAT partition

E. Export FAT partition

U. Update using update*.bin file on FAT partition

M. Update using update*.bin file on FAT partition of second MMC port

D. dmesg / kernel printk ring buffer.

Q. quit

It looks like the partion table of the MMC is distroyed but the device is still booting :blink:

Code:

[    1.851829] mmc0: new high speed DDR MMC card at address 0001

[    1.857985] mmcblk0: mmc0:0001 SEM04G 3.68 GiB

[    1.862737] mmcblk0boot0: mmc0:0001 SEM04G partition 1 2.00 MiB

[    1.868782] mmcblk0boot1: mmc0:0001 SEM04G partition 2 2.00 MiB

[    1.875750]  mmcblk0: p1 p2 p3 p4

[    1.881989]  mmcblk0boot1: unknown partition table

[    1.889128]  mmcblk0boot0: unknown partition table

Also fdisk reported partition problems on /dev/mmcblk0boot0

Code:

[root@kindle root]# fdisk -l





Disk /dev/mmcblk0: 3959 MB, 3959422976 bytes

4 heads, 16 sectors/track, 120832 cylinders

Units = cylinders of 64 * 512 = 32768 bytes



        Device Boot      Start         End      Blocks  Id System

/dev/mmcblk0p1   *        1025       12224      358400  83 Linux

/dev/mmcblk0p2           12225       14272       65536  83 Linux

/dev/mmcblk0p3           14273       16320       65536  83 Linux

/dev/mmcblk0p4           16321      120832     3344384   b Win95 FAT32



Disk /dev/mmcblk0boot0: 2 MB, 2097152 bytes

4 heads, 16 sectors/track, 64 cylinders

Units = cylinders of 64 * 512 = 32768 bytes



Disk /dev/mmcblk0boot0 doesn't contain a valid partition table

Any Idea what was happend and how to fix it. I need some help :help:

Bernd

↧

PW3 Jailbreak option for PW3 on FW 5.13.3--not yet?

February 7, 2021, 10:31 am

≫ Next: help please

≪ Previous: Kindle PW2 is write protected

Hello, I'm new to the community and already pleasantly overwhelmed by all the helpful information. I have a PW3 on FW 5.13.3 that I'd like to jailbreak. I read the post about the PW4 version for this FW but can't find anything for PW3.

Can someone smarter than me please confirm that a JB for the PW3 is not yet available for FW 5.13? If that's the case I can just stop looking and try again in a few months. Many thanks.

↧

help please

February 8, 2021, 1:09 am

≫ Next: Jailbroken Paperwhite 3 not refreshing recently read list

≪ Previous: PW3 Jailbreak option for PW3 on FW 5.13.3--not yet?

Hey who know how to unbrick the kindle help please i wanted install the system in puTTY but in recovery mode when i put system on kindle then U and M doesn't work help please my kindle is paperwhite 2

Attached Thumbnails

Click image for larger version

Name: puTTY.png
Views: N/A
Size: 16.3 KB
ID: 185286

↧

Jailbroken Paperwhite 3 not refreshing recently read list

February 8, 2021, 5:10 am

≫ Next: Book Management through cloud and Voyage things

≪ Previous: help please

Hello

I have this issue where my jailbroken PW3 won't update the recently read books and has been stuck like that for months, which makes the book cover as lock screen feature useless (as it's always stuck on a book I read months ago)

The issue started sometime like 6 months ago and at first it would take long to refresh the latest read book until it stopped updating the recently read list completely

Should I update?
Would updating the firmware fix it?
Would I lose the jailbreak?
Would I brick the reader?

I have FW version 5.7.2, it's jailbroken and has been in flight mode for like two years, except for a few times I used wikipedia.

Thank you for reading.

↧

Book Management through cloud and Voyage things

February 10, 2021, 12:49 am

≫ Next: K4 Extending/refreshing screensaver timer?

≪ Previous: Jailbroken Paperwhite 3 not refreshing recently read list

Hello, a long time ago I jailbroke my Voyage via serial and everything worked out fine. Currently I have Firmware version 5.8.7.0.1. I have some issues with my buttons in KOReader, I have read the issue was closed on the thread but couldn't really understand what the fix is (anything with if you start koreader in KUAL , you should flip the page (which page?! :/) So the buttons work). Maybe an fix is now provided :) I would appreciate any help there

Now a management thing : I have seen many use Calibre to manage their collection. I use mostly my books on either Kindle or phone (I get all my books from my phone). I have an sync app on my android to upload my new books to my Dropbox, so I can sync it via cloud storage on my Kindle through koreader. Is it possible to manage/sort everything through calibre but with my Dropbox or do you guys use any other way ? Calibre would mean manage everything from my computer which would be fine but not ideal :)

Thanks for reading, have a great day and stay healthy

↧

K4 Extending/refreshing screensaver timer?

February 11, 2021, 8:50 am

≫ Next: Help with watermarke on ebook

≪ Previous: Book Management through cloud and Voyage things

I've recently set up and old Kindle 4 (4.1.4) to act as a weather station, which seems to be a fairly common project. I am using the Online Screensaver Extension script (https://www.mobileread.com/forums/sh...d.php?t=236104) with the modifications to allow it function on Kindle 4 found in this post: https://www.mobileread.com/forums/sh...2&postcount=36

This works great...except that it only updates 4 or 5 times before stopping. Using the log file for the script, I was able to track down the problem:

Code:

Thu Feb 11 03:05:09 UTC 2021: wait_for called with 900, now=1613012709, Powerd state: Screen Saver, defer_suspend:0, Remaining time in this state: 53.913745, Battery Level: 58% Battery logging: On

Thu Feb 11 03:20:22 UTC 2021: wait_for called with 900, now=1613013622, Powerd state: Screen Saver, defer_suspend:0, Remaining time in this state: 41.375632, Battery Level: 56% Battery logging: On

Thu Feb 11 03:35:35 UTC 2021: wait_for called with 900, now=1613014534, Powerd state: Screen Saver, defer_suspend:0, Remaining time in this state: 28.618913, Battery Level: 56% Battery logging: On

Thu Feb 11 03:50:47 UTC 2021: wait_for called with 900, now=1613015447, Powerd state: Screen Saver, defer_suspend:0, Remaining time in this state: 15.851457, Battery Level: 56% Battery logging: On

Thu Feb 11 04:06:00 UTC 2021: wait_for called with 900, now=1613016360, Powerd state: Screen Saver, defer_suspend:0, Remaining time in this state: 3.076768, Battery Level: 56% Battery logging: On

Thu Feb 11 04:21:12 UTC 2021: wait_for called with 900, now=1613017272, Powerd state: Ready to suspend, defer_suspend:1, Remaining time in this state: 33.024700, Battery Level: 56% Battery logging: On

From these log entries, you can see that the "remaining time in this state" continues to decrease every time the Kindle wakes up to update the screensaver. Once the power state reaches "ready to suspend" the wifi no longer functions (and I'm not sure the screen can be updated at that point either.)

So I'd like to know if there's a command I can add to the script that would extend the time remaining in the screensaver state, or to refresh it somehow, so the script can continue running indefinitely without needing to keep it plugged in (since I understand that when plugged in, the Kindle will stay in screensaver mode indefinitely.) I am aware that the length of the time the screensaver is active can be modified through the t2_timeout setting, though no matter what value is set it would always be a fixed amount of time (also not sure if there's a maximum value.)

Any suggestions would be appreciated.

↧

Help with watermarke on ebook

February 11, 2021, 4:00 pm

≫ Next: Retasking Paperwhite

≪ Previous: K4 Extending/refreshing screensaver timer?

Hi.

after I bought an ebook on amazon I passed out to a friend a pdf copy of the awz file I had previously de-drmd and converted to pdf with calibre. I am only now thinking that this was not a good idea. could there be a watermark in the pdf that would trace the file back to my amazon account? this was not done with commercial intent, but I am a bit afraid that this person could pass this pdf on to someone else and so on. I thank you in advance and hope I have not done something too stupid.

↧

Retasking Paperwhite

February 13, 2021, 4:50 pm

≫ Next: PW2 Kindle PaperWhite 2 6Gen DP75SDI emmc dump

≪ Previous: Help with watermarke on ebook

I have a 10th Gen Kindle Paperwhite reader, and I'd like to re task it to do things like show my calendar, or maybe display the weather or home automation status.

Has anyone reprogrammed (re flashed) the device so it is not a Amazon Kindle anymore but a general purpose display?

I've seen something called Jailbreak, but I think that is not the same thing.

Thanks, Mark.

↧

PW2 Kindle PaperWhite 2 6Gen DP75SDI emmc dump

February 14, 2021, 8:15 am

≫ Next: PW3 Problem with PW3 after serial port mod

≪ Previous: Retasking Paperwhite

Hi! look for dump emmc 2GB, for a programmer like z3x (or similar ones). Thank!

↧

PW3 Problem with PW3 after serial port mod

February 16, 2021, 2:02 pm

≫ Next: PW Is there any hope for my Kindle?

≪ Previous: PW2 Kindle PaperWhite 2 6Gen DP75SDI emmc dump

So, after having my old PW3 laying around unused for over a year now (bought the latest Oasis last year), I've decided to jailbreak it the hard way.

Soldering the pins went relatively straightforward - the hardest part was removing the front plate of the device without ruining the glue strips.

However since I've had the serial port wired up, for some reason the Kindle won't boot completely properly in regular mode. It starts up, but during the boot animation (the bar filling) the screensaver flickers in for a moment or two, before settling on it permanently. Through the serial port I can see it boots properly, and after doing the first step of the jailbreak (removing the root user password from the "regular" system partition), I can log in and play around. The device does not respond to the power button (apart from the 15 second long press to cut the battery), and after some time, sending data to the Kindle through the serial port also hangs. It is not frozen, since if I e.g. long press the power button until it reboots, or connect a power supply, I can see logs coming through - but entering any data is not possible.

At first I thought it's a hardware fault, however diag mode does not produce this effect. In diag mode, everything works as intended, the serial port does not freeze, and I do not get locked out at any point.

What could have gone wrong? I've literally didn't even touch the main OS partition at first, the only change that happened between it working and suddenly producing the above effect is the two pins being soldered to two freestanding (insulated) wires. They are not crossed - otherwise I wouldn't get any output through my adapter.

And what could be done? I was thinking about using the recovery mode that is prompted during boot, which offers to flash a *.bin file from internal storage. Since my PW3 is on a relatively old(ish) firmware - 5.12.1 if I recall correctly - I could flash a somewhat newer, but still not the latest firmware.

↧

PW Is there any hope for my Kindle?

February 22, 2021, 11:12 am

≫ Next: PW3 Serial jailbreak on 5.13.4?

≪ Previous: PW3 Problem with PW3 after serial port mod

I have a Kindle Paperwhite 1 that isn't turning on, the screen is just blank. I've tried long pressing the power button to force a restart, but nothing so far.

My next step is to leave it plugged into the wall charger for the next 24-48 hours and try again, but I've noticed that when I first plugged the charger into the Kindle the amber light came on for 3-4 seconds and then turned off and it doesn't come back on (no matter how many times I pull out and plug the charger back in).

I have a multimeter lying around, so I decided to open up the Kindle and see if I can get any useful information from the battery itself. It gave a reading of 2.52V on the multimeter (I don't know if this information helps). I plugged the battery back in and connected the charger again and the amber light once again came on for 3-4 seconds before turning off completely, and no more plugging out/in can make it come back on.

I've done some searching and any time the Kindle won't power on it's recommended to leave it on a charge for a few days, which I plan to do, but I was wondering if it sounds like I need a new battery, or if there may be something else more sinister going on possibly with the motherboard itself.

I've also tried plugging it into my computer, but nothing is recognised.

Has anybody came across any issues where the charging indicator would not turn on while connected to a power supply?

↧

PW3 Serial jailbreak on 5.13.4?

February 23, 2021, 11:03 am

≫ Next: PW Jailbreaking a PW (FW: 5.6.1.1)

≪ Previous: PW Is there any hope for my Kindle?

Hey all,

I've successfully run the jb.sh script on my PW3 after disabling the root password via serial. It said "*jailbreak*" at the bottom of the screen and everything. From here however, I have been unable to run any of the KUAL/mrpi/you name it installers in any form that I've found. The ";log mrpi" search trick does nothing, any updates I drop into /mnt/us get deleted on volume eject... Is there no way to move forward with the jailbreak on this firmware? It seems so strange that I have full write access to the filesystem but I don't actually have control.

Thanks,
Jeremy

↧

PW Jailbreaking a PW (FW: 5.6.1.1)

February 25, 2021, 5:27 am

≫ Next: Kindle keyboard screen gone weird after screen replacement

≪ Previous: PW3 Serial jailbreak on 5.13.4?

Hey guys!

I'm trying to jailbreak my old PW Kindle (the serial starts B024), it's got Wifi only and was bought in the UK. I want to jailbreak it so I can change the Collections Manager as Amazon's version totally sucks.

The Firmware is 5.6.1.1 but I can't find any reference to this early PW, I can only find stuff for the later versions.

Any ideas? Thanks in advance :)

↧

Kindle keyboard screen gone weird after screen replacement

March 2, 2021, 10:44 am

≫ Next: K4 Kindle 4 (Black) Constantly rebooting

≪ Previous: PW Jailbreaking a PW (FW: 5.6.1.1)

Hello,
Can anyone tell me what is wrong with my kindle screen?
I dropped my kindle, the screen cracked, so I ordered a replacement and installed it at the weekend.
Since turning it on after the screen replacement I can only see my kindle menus in the top right of the screen. The bottom right is just grey and never changes and there is a bar on the left which was the display when I unboxed the replacement screen.
Has anyone come across this before?
Is the replacement screen the problem.
I tried to attach a photo to this post however I am not sure if that worked.
Many thanks in advance.
Tom

Attached Thumbnails

Click image for larger version

Name: kindle screen jpg.jpg
Views: N/A
Size: 120.4 KB
ID: 185715

↧

K4 Kindle 4 (Black) Constantly rebooting

March 2, 2021, 3:04 pm

≫ Next: Help reading files (.mbs, .mbp1) from KOA3

≪ Previous: Kindle keyboard screen gone weird after screen replacement

Hi everyone,

I have a black Kindle 4 that is constantly rebooting after ~5 mins on standby. I have tried the following:

Unregistered.
Kubricked.
Purchased new battery from ebay and replaced (original battery).
Charged for 24 hours straight.
Kubricked again.

So far nothing helped. Issue is it just reboots, everything else works perfectly fine. What can be the issue here? Faulty power controller? And is there any hope of getting it back online?

↧

Help reading files (.mbs, .mbp1) from KOA3

March 3, 2021, 2:35 am

≫ Next: KOA Cover battery not charging 0% "!"

≪ Previous: K4 Kindle 4 (Black) Constantly rebooting

I'm wondering if there is a way to produce/collect reading times/stats from my KOA3. I see there are extra files with .mbs and .mbp1 extensions. When I view the .mbs file in a hexeditor I see a few mentions of 'timer' like timer.model, timer.average.calulator. And in the .mbp1 file I see like 'next.in.series' and 'annotation.cache'.

Does anyone have some code or specification of these files before I attempt to write my own?

Does anyone know if reading stats exist? Such that I could suck them out when the kindle is connected to PC?

↧

KOA Cover battery not charging 0% "!"

March 6, 2021, 12:32 pm

≫ Next: K3 execute script when (un)plugged

≪ Previous: Help reading files (.mbs, .mbp1) from KOA3

Hello, i have a kindle oasis 8th gen ant the case battery in not charging, when i connect it there is a "!" on cover battery with 0%. Is there a way to force the battery to charge from an external source? I thin the battery is discharged and the battery chip is in a lock state. Thanks.

↧