Quote:
Originally Posted by NicolasR
|
I tried this already and it outputs that:
failed -
assert(getprop("ro.product.device") == "C67ML" ||
getprop("ro.build.product") == "C67ML");
I dunno perhaps the device says it is Artatech C67ML rather than just C67ML (it shows as Artatech C67ML on my computer when I connect it.
I did notice that if you look through the update.zip file from onyx-international and go to /META-INF/com/google/android/updater-script you can find those very lines. I imagine simply deleting them would allow me to install this firmware package. I'm just not sure if that's a good idea, hah. Maybe there are some minor differences in how Artatech's is configured vs the regular C67ML? Any ideas if that is a good or bad idea?
If they continue to ignore my emails and phone calls to their support department requesting assistance then maybe I will just have to try it and hope for the best.
The other thing that could maybe work is if anyone here could upload an rkimage (rk chip). Stealing from Nalor's advice you can create an image this way:
Quote:
Basically it's quite easy - here are the basic steps for the backup of the firmware:
download Tool from here (http://www.freaktab.com/showthread.p...ndroidTool-2-3) and umcompress it
connect a micro-usb cable to an USB2.0 (not an USB3.0 port to be on the safe side) on your computer
and switch your reader into loader mode:
# power off reader
# press and hold 'back' button below display
# plug in usb cable (while you hold the button)
# wait a couple of sec
# release button
>> device should be in loader mode!
(in case your device is booting now it didn't work - basically it should switch to 'loader' mode - so please repeat the procedure with another button until you succeed - eventually it's the button 'page back' button instead of the 'back' button )
windows should ask you for a driver - you find the correct driver in the folder of the tool package (in case you're using windows 8.1 it's a little bit more complicated - please take a look at this post) - and in case you're not asked please check your windows device manager, search for the unknown device and install the driver manually
download the rkdumper utility (http://forum.xda-developers.com/gene...mware-t2915363) and uncompress it
start a command prompt as administrator
change to the directory of the uncompressed rkdumper
create a dump with the command 'rkdumper /log dump'
In case you're using windows 8.1 (as I do) I want to share a few more details with that I've discovered today:
# as mentioned in the link above with the solution to the driver problem you need VID, PID and REV to create the correct key in the windows registry
# when you start the rkdumper tool with command 'rkdumper scan' it will show a list of all discovered usb devices - including your device and you can get at least VID and PID here.
# in my case windows automatically created the registry-folder in the registry - all I had to do was to find it and insert the DWORD 'SkipBOSDescriptorQuery ' with value 1 in the correct key. to check if windows also created the key for you can use the VID and PID
|
However, I think it will literally copy all the data exactly as is from your device and create an image you could flash back if you ever ran into problems (as I have had!). But you wouldn't want to do this if your device had any personal information in it, like if it were logged into your email or other services that required usernames and passwords.
So, if anyone has a stock version of the Afterglow 2, or would be willing to reset to stock in order to make a back up, I would super appreciate it if they wouldn't mind sharing the img file with me!
Edit - here's a tool for those on Linux:
http://www.cnx-software.com/2013/11/...ware-in-linux/