| 
 | |||||||
|  | 
|  | Thread Tools | Search this Thread | 
|  07-15-2014, 11:06 AM | #1 | 
| Booxtor            Posts: 1,126 Karma: 2305664 Join Date: Jun 2011 Location: Germany Device: a lot of.. |  How to recover a "bricked" T68 device or change from Lynx to Booxtor edition 
			
			If your T68 experiencing some troubles and you want to recover it do following: Warnings. Be aware - after recovery your device will be like a new born baby. All your installations will be gone! If you apply this tool to a Lynx, it will be changed to a T68 UHDML (without Polish bookshop, Polish dictionaries, Ivona TTS etc... ). Also warranty of Artatech (Lynx devices only) could be affected. However, it is possible to recover back to Lynx edition using that tool (you need to get update.zip from Artatech first and replace it in this package). * download program package from here * decompress zip package * connect device with pc * shutdown device * run mfgtool2 * press both pageup/pagedown and power button to boot device Your device boots in "download" mode. The screen will not change but your PC will signal a new USB device and in mfgtool2 window appears "HID device. * click start to program the device If you see a windows message like this: (you need to format drive X ...) - just ignore it and wait for the tool finishes flashing. * once finished, click stop and exit * long press power button to shutdown device * press power button again to boot device that's it Last edited by Booxtor; 10-17-2014 at 01:00 PM. | 
|   |   | 
|  07-15-2014, 12:01 PM | #2 | 
| Starving artist     Posts: 17 Karma: 378 Join Date: Sep 2013 Location: Ljubljana, Slovenia Device: Boox T68, Kobo Aura HD, Galaxy Note 10.1 2014 | 
			
			edit: okay, after 30 minutes of rebooting it finally recognized the device. edit2: recovery worked, it now successfully boots into android. Last edited by Domen Lo; 07-15-2014 at 12:22 PM. | 
|   |   | 
|  07-16-2014, 03:32 AM | #3 | 
| Groupie            Posts: 164 Karma: 10020 Join Date: Mar 2012 Device: Onyx Boox M92, Onyx Boox T68 | 
			
			Thank you very much for the tool. It occurs to me as we have a recovery, if we could make a backup of our T68 perfectly configured, then restore. A greeting -. | 
|   |   | 
|  07-20-2014, 03:36 PM | #4 | 
| Enthusiast            Posts: 39 Karma: 13126 Join Date: Jul 2011 Device: Kobo Aura One | 
			
			where do I find "mfgtool2" to download ?
		 | 
|   |   | 
|  07-20-2014, 04:03 PM | #5 | 
| Enthusiast     Posts: 35 Karma: 382 Join Date: Mar 2012 Location: UK Device: Onyx BOOX T68, M92 | |
|   |   | 
|  07-20-2014, 08:04 PM | #6 | 
| Addict            Posts: 291 Karma: 3762916 Join Date: Nov 2011 Device: none | 
			
			Thanks a lot.
		 | 
|   |   | 
|  07-26-2014, 11:53 AM | #7 | 
| Member            Posts: 10 Karma: 208986 Join Date: Jul 2014 Device: Onyx T68 |   
			
			Hi, I'm trying to revert the firmware to original Lynx version, your support is great and your version of sw is infinitely better than Artatech one, but i decided to return the t68 to Amazon because of the touch screen issues. In your package I replaced the update.zip file with the one found on onyx website, which is the exact version (2014-06-26_16-16_1.5.0_c3193d0) i had before flashing yours. The flashing process completes successfully (including "partitioning", "writing system.img" steps, etc.), however after reboot the version is still yours (2014-07-15_20-23_1.6.0_252635f), just as it was simply factory resetted. What I'm doing wrong? Maybe there is a version check (1.5.0 vs 1.6.0) somewhere? EDIT: Ok solved, in the zip package released on the OP, the files written to the device are NOT those inside update.zip. Instead MfgTool2 looks for so called "profiles" inside the Profiles dir (configured via the cfg.ini file). In our case the configured profile directory is named "MX6SL Linux Update", and inside it you can find a sort of xml script file (ucl2.xml). This references the real files written during the flashing process, which can be found inside the files directory. So, in case somebody else needs to revert to another firmware version, extract the T68_2014-07-15_20-23_1.6.0_252635f_user.zip package (for example in C:\T68), extract the update.zip you want to flash and then move the following files: 
 then move logo.bmp to C:\T68\Profiles\MX6SL Linux Update\OS Firmware\files\logo and rename it uboot_logo.bmp (delete the existing file). then follow the OP flashing procedure. Bye Roberto Last edited by bitblaster; 07-27-2014 at 06:28 PM. | 
|   |   | 
|  07-28-2014, 04:58 PM | #8 | 
| Wizard            Posts: 3,472 Karma: 48036360 Join Date: Aug 2009 Location: where the sun lives, or so they say Device: Pocketbook Era, Pocketbook Inkpad 4, Kobo Libra 2, Kindle Scribe | 
			
			Does this method work on a win 8.1 system? My win 8.1 laptop cannot connect per USB with my T68 if the USB debugging option is on. If I switch it off, it connects without problem but I always get a driver not recognized message. I went to have a look in my device manager and what the laptop does on connection is to very shortly recognize it as T68, but then as an Android phone and downloads the ADB drivers. The mfgtool never recognizes a device.... Where can I find the right drivers to have the T68 communicate without problems with my PC, or is this hopeless on windows 8.1 anyway ? Last edited by aceflor; 07-28-2014 at 05:07 PM. | 
|   |   | 
|  07-29-2014, 09:35 AM | #9 | 
| Member            Posts: 10 Karma: 208986 Join Date: Jul 2014 Device: Onyx T68 | 
			
			It's very strange, since in download mode the debug mode is off anyway (entire Android is off actually). Are you sure you put the device in download mode?
		 | 
|   |   | 
|  07-29-2014, 09:47 AM | #10 | |
| Wizard            Posts: 3,472 Karma: 48036360 Join Date: Aug 2009 Location: where the sun lives, or so they say Device: Pocketbook Era, Pocketbook Inkpad 4, Kobo Libra 2, Kindle Scribe | Quote: 
  The download mode would have just the logo and the light on ? EDIT: Success at last. I had to unsinstall all drivers related to the device. I had been getting in download mode without problem after all, it was indeed a driver problem. Last edited by aceflor; 07-29-2014 at 10:52 AM. | |
|   |   | 
|  07-29-2014, 10:37 AM | #11 | 
| Member            Posts: 10 Karma: 208986 Join Date: Jul 2014 Device: Onyx T68 | 
			
			yes, you have to: 
 | 
|   |   | 
|  07-29-2014, 11:15 AM | #12 | 
| Wizard            Posts: 3,472 Karma: 48036360 Join Date: Aug 2009 Location: where the sun lives, or so they say Device: Pocketbook Era, Pocketbook Inkpad 4, Kobo Libra 2, Kindle Scribe | 
			
			Thanks bitblaster, K for you. It was a driver problem after all, but it is nice to have a newbie helping an oldie   . Did you end up sending yours back ? | 
|   |   | 
|  07-30-2014, 05:56 PM | #13 | 
| Member            Posts: 10 Karma: 208986 Join Date: Jul 2014 Device: Onyx T68 | |
|   |   | 
|  09-07-2014, 08:47 AM | #14 | 
| Addict      Posts: 257 Karma: 432 Join Date: May 2014 Location: New York, NY Device: NG,NSTG,NST,AuraHD,OnyxT68,Lynx, BoyueT62,NGP,Aura1,Oasis,Mars | 
			
			Is there an equivalent of the mfgtool in the Linux world ?  I only have linux ... | 
|   |   | 
|  09-07-2014, 05:24 PM | #15 | 
| Ex-Helpdesk Junkie            Posts: 19,421 Karma: 85400180 Join Date: Nov 2012 Location: The Beaten Path, USA, Roundworld, This Side of Infinity Device: Kindle Touch fw5.3.7 (Wifi only) | 
			
			search for "kobs-ng"
		 | 
|   |   | 
|  | 
| 
 | 
|  Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post | 
| PRS-T3 bricked device (blocked on "loading book"), any recovery SD ? | darkape | Sony Reader Dev Corner | 1 | 01-08-2014 03:16 PM | 
| SONY pocket edition: "Device locked" + "charge battery" obstacles? | hermes | Devices | 3 | 06-02-2011 03:32 AM | 
| How to change "Send to device" without folders? | Skydog | Calibre | 12 | 05-23-2010 12:13 PM | 
| K1 how do I Change "Settings & Device info" | KINDLEMEx | Amazon Kindle | 1 | 11-24-2009 01:21 PM |