Likebook Alita bricked after accidentally flashing Mars firmware..
Quote rvcjew
unfortunately the firmware for the touch matrix ect may be stored in the actual panels it self and therefor for the 8.1 upgrade the mars did a firmware update to it's panels to be more compatible with 8.1 and that update was flashed to your panel. Until they push the 8.1 update for the alita with its own update for the panel it might be stuck that way. Could you try getting an explorer on there that has root level access like solid explorer ect. and go to system/then open build.prop (should open as text) I'm wondering if the data in that thinks it's a mars digitizer.
Edit: you have a link to the exact mars firmware you flashed? I want to see what it had in the img.
That would explain why none of these flashes are working, think I've tried just about everything at this stage bar sending the thing back to the manufacturer.. I'm going to try and get a root explorer going tomorrow, hopefully I can dig something up.
Here's the first image I flashed;
https://mega.nz/file/yRRR2CzB#WVI-wMGj_oi1_tGzIVjojH5OnV2LOCesuLIQk6klFVgQuote ottischwenk
Did you try the
image in the pdf?
Yes, I've tried that one 3-4 times at this stage, formatting data/ and cache/ beforehand too.
Sending it to Boyue may not be the best idea. Communication is an issue because my emails although answered were a bit unclear. You have the language problem plus the highly specialised vocab required on their part. I sent a number of short questions phrased as simply as I could and they did reply to each one.
The fact that you screwed this up for yourself means that you are on dodgy ground. They may hold on to it for a long while or charge you a lot of money. Carriage alone isn't going to be cheap either. If they get their act together with the Android update and it includes a flash for the Alita touch screen that would be ideal for you.
It's worth sounding them out though. Helping you would give them some Kudos on the forum. Nobody wants to buy an expensive device that cannot be easily recovered when it goes wrong.
Quote FixMyAlita
That would explain why none of these flashes are working, think I've tried just about everything at this stage bar sending the thing back to the manufacturer.. I'm going to try and get a root explorer going tomorrow, hopefully I can dig something up.
Here's the first image I flashed;
https://mega.nz/file/yRRR2CzB#WVI-wMGj_oi1_tGzIVjojH5OnV2LOCesuLIQk6klFVgYes, I've tried that one 3-4 times at this stage, formatting data/ and cache/ beforehand too.
When I get some time I will look at these (main desktop is in peices atm waiting on some parts), I agree you should not send it to boyue as they might charge you a lot, what they should do is put a big ass warning on the Facebook ect for the firmware posts to not flash these on non mars devices, I figgured I would see a thread like this eventually when they decided to not do a service ota (one that is a stop gap on things like the TP firmware) that would have then let them push a second ota for the main upgrade. I believe this is because they only have one file for the device to find on their servers at a given time and if it had to find a small ota then after a larger one it would just find the small one as they only put one up. If that wasn't the case I feel the Mars could just update this way. But perhaps it's also hardware issue with being in the middle idk but an old phone would do it this way.
@FixMyAlita any progress now that boyue has released the official update to 8.1 for the Alita?
Quote rvcjew
I have attached the modded flasher that I also have on hand that must have been with that full thing (I have like 6 versions of RKtool from a long time ago lol)
RK_Android_Tool_2.3.9_bernado_mod.rar
How can I update my device with the above mentioned Android tool and the backup files shown below?
Code
Content of Output:
<DIR> Image
11.009 config_16.cfg
5.640 config_8.cfg
957 parameter
Content of Image:
117.440.512 backup.img
4.194.304 baseparamer.img
21.479.424 boot.img
134.217.728 cache.img
19.601.204 kernel.img
4.194.304 kpanic.img
16.777.216 metadata.img
4.194.304 misc.img
67.108.864 radical_update.img
24.805.376 recovery.img
425.176 resource.img
1.717.567.488 system.img
4.194.304 trust.img
4.194.304 uboot.img
4.194.304 wbf.img
I'm following all this geek speak but don't understand much of what's going on. However, there appear to be few advantages to upgrading to 8.1 so maybe FixMyAlita would be better advised to look at restoring the device to its original state - Android 6. Note taking apps for these devices clearly have a long development path ahead. The Alita is a decent enough e-reader in its own write. (Joke)
Quote bazz2004
I'm following all this geek speak but don't understand much of what's going on. However, there appear to be few advantages to upgrading to 8.1 so maybe FixMyAlita would be better advised to look at restoring the device to its original state - Android 6. Note taking apps for these devices clearly have a long development path ahead. The Alita is a decent enough e-reader in its own write. (Joke)
Android 8.1 has many advantages, e.g. OS3 in which you can also take notes in files other than pdf.
But it also has disadvantages - e.g. a bug in the handling of internally formatted SD cards, the A2 mode also looks horrible compared to that of Android 6 or Boox devices.
Perhaps these bugs / weaknesses will be fixed - I've already reported them.
Mine is set permanently to A2. It's rubbish otherwise. I've got used to the slight page bleed through. Sorry, don't know if there's a technical term for that.
