Cannot flash M96

fAX · 05-16-2015, 10:20 AM

Hi allmighty All,

Yesterday I connected a bad cable to a charger which made my M96 very hot. I don't really understand what happened and thought the reader is dead.

As it was completely discharged, I charged the reader from my notebook today; and it started to show signs of life. It didn't boot but at some point I could enter the recovery.

Now I cannot reflash from recovery, since I get signature failures during package verification.
I cannot flash from fastboot, as I get

Code:

sending 'system' (378880 KB)...
FAILED (remote: data too large)

I cannot flash from MFG_tool, as the mass storage does not have a drive mounted...

Is there a way to reflash from a PC, or an update image which flashes without failing signature validation?

I understand, the reader could be still dead and causing this, but I have no idea what to do at the point...

Thanks...

rkomar · 05-16-2015, 04:02 PM

It sounds like your bad cable shorted out the battery, which would make it very hot. If so, you're lucky it didn't burst or even catch fire. Maybe all you need is a new battery, but I can imagine that the charging circuitry also got damaged.

fAX · 05-17-2015, 05:43 PM

rkomar, you were absolutely right, all the weird behavior seemed to be the result of short circuit and battery that didn't give enough current or so. After a couple of charge-discharge cycles I was able to flash ROM and boot the device.

So it seems that the device is alive (huh!), will watch the battery. BTW, can you advice where do I find replacement one if I need?

japinder · 05-19-2015, 10:54 AM

Quote:

Originally Posted by fAX

rkomar, you were absolutely right, all the weird behavior seemed to be the result of short circuit and battery that didn't give enough current or so. After a couple of charge-discharge cycles I was able to flash ROM and boot the device.

So it seems that the device is alive (huh!), will watch the battery. BTW, can you advice where do I find replacement one if I need?

The official replacement battery from Booxstor:

http://ereader-store.de/en/8-accessoires

Some discussion about the battery, which could help you find alternate suppliers:

https://www.mobileread.com/forums/sho...d.php?t=175472

Jp

05-16-2015, 10:20 AM	#1
fAX Junior Member Posts: 9 Karma: 10 Join Date: Apr 2010 Device: Boox Max2, Kindle Voyage	Cannot flash M96 Hi allmighty All, Yesterday I connected a bad cable to a charger which made my M96 very hot. I don't really understand what happened and thought the reader is dead. As it was completely discharged, I charged the reader from my notebook today; and it started to show signs of life. It didn't boot but at some point I could enter the recovery. Now I cannot reflash from recovery, since I get signature failures during package verification. I cannot flash from fastboot, as I get Code: sending 'system' (378880 KB)... FAILED (remote: data too large) I cannot flash from MFG_tool, as the mass storage does not have a drive mounted... Is there a way to reflash from a PC, or an update image which flashes without failing signature validation? I understand, the reader could be still dead and causing this, but I have no idea what to do at the point... Thanks...

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
M96 Questions	Spydah	Onyx Boox	5	03-23-2015 06:59 PM
[M96] Perfect cover case for M96	kuskro	Onyx Boox	3	01-30-2015 01:28 PM
M96 Out of Stock everywhere	EldRick	Onyx Boox	5	09-29-2014 02:25 PM
To Flash or Not to Flash? For the Eee Transformer	Ken Maltby	Android Devices	4	06-28-2011 05:58 PM
Can't get new f/w - flash site broken again and non-flash not updated	jusmee	Astak EZReader	8	03-13-2010 12:26 PM

05-16-2015, 04:02 PM	#2
rkomar Wizard Posts: 3,016 Karma: 18765431 Join Date: Oct 2010 Location: Sudbury, ON, Canada Device: PRS-505, PB 902, PRS-T1, PB 623, PB 840, PB 633	It sounds like your bad cable shorted out the battery, which would make it very hot. If so, you're lucky it didn't burst or even catch fire. Maybe all you need is a new battery, but I can imagine that the charging circuitry also got damaged.

05-17-2015, 05:43 PM	#3
fAX Junior Member Posts: 9 Karma: 10 Join Date: Apr 2010 Device: Boox Max2, Kindle Voyage	rkomar, you were absolutely right, all the weird behavior seemed to be the result of short circuit and battery that didn't give enough current or so. After a couple of charge-discharge cycles I was able to flash ROM and boot the device. So it seems that the device is alive (huh!), will watch the battery. BTW, can you advice where do I find replacement one if I need?

Advert