MobileRead Forums - View Single Post - Move your M96 to Booxtor's firmwares and/or Unbrick and rooting

nknouf · 03-01-2015, 04:15 PM

Okay, it looks like I've really screwed up my Arta Tech M96. I've flashed ROMs before on other Android devices, so I'm not sure what's going on here.

Here are the two problems I'm having, the second being fatal:

* Many of my Windows systems have not been detecting my M96, even when following the information posted above. This has happened even on Windows systems that have not had any other ADB drivers installed. (That is, when I try and use ADB to show the devices attached, or use MfgTool2, it doesn't recognize the device. And yes, USB debugging is enabled.) The only system that was able to recognize my M96 was a Windows 7 instance in my virtual machine on an OS X host. Which leads me to my main problem:
* I was able to get MfgTool2 to recognize my M96 when running it from the previously mentioned virtual machine. I hit Start, but unfortunately the process never completed successfully, even after 5 or so attempts. This caused my M96 to be stuck in a continual reboot loop where it never boots properly, but always dumps me into recovery. So I thought I'd try to apply the update.zip provided above. Unfortunately that fails as well with an assertion error: assert failed: file_getprop("/tmp/android-info.txt", "oard") == getprop("ro.product.board"); E: Error in /tmp/sideload/package.zip; (Status 7)

So now I have a completely non-functional M96. Any suggestions of how to recover it?

03-01-2015, 04:15 PM	#12
nknouf Enthusiast Posts: 34 Karma: 10 Join Date: Dec 2014 Device: Onyx Boox M96 Universe	Okay, it looks like I've really screwed up my Arta Tech M96. I've flashed ROMs before on other Android devices, so I'm not sure what's going on here. Here are the two problems I'm having, the second being fatal: * Many of my Windows systems have not been detecting my M96, even when following the information posted above. This has happened even on Windows systems that have not had any other ADB drivers installed. (That is, when I try and use ADB to show the devices attached, or use MfgTool2, it doesn't recognize the device. And yes, USB debugging is enabled.) The only system that was able to recognize my M96 was a Windows 7 instance in my virtual machine on an OS X host. Which leads me to my main problem: * I was able to get MfgTool2 to recognize my M96 when running it from the previously mentioned virtual machine. I hit Start, but unfortunately the process never completed successfully, even after 5 or so attempts. This caused my M96 to be stuck in a continual reboot loop where it never boots properly, but always dumps me into recovery. So I thought I'd try to apply the update.zip provided above. Unfortunately that fails as well with an assertion error: assert failed: file_getprop("/tmp/android-info.txt", "oard") == getprop("ro.product.board"); E: Error in /tmp/sideload/package.zip; (Status 7) So now I have a completely non-functional M96. Any suggestions of how to recover it?