Related
As I have less then 10 posts I can't write into the developer forum So I post here my results of updating to firmware 4.0.24 which isn't officialy released yet for the G9 archos devices (only for G10).
Update process:
- Downloaded file from URL
- Saved to disk
- Open File Browser
- Open the firmware file "firmware_archos_it4.aos" (should be inside the Download folder)
- Select yes for updating firmware
- PlugIn Power Coord as requested
- Update automaticaly starts
-- Relocate firmware
-- Restarts
-- Update Process Step one (Archos start logo and progress bar) ... Around 2 minutes on my device
-- Update Process Step two (Archos start logo only) ... Please Wait the device is updating! Took 2 min on my device.
-- Update Process Step three (Optimizing App X from Y applications) ... Around 3 minutes on my device with 100 apps installed.
-- Login Screen
- All done, firmeware file is removed
System: G9A101 ARMv7 rev 3 (v7l)
SDK: 4.0.4
Kernel: 3.0.21
Quadrant v2.1.1
===========
Total: 3307
CPU: 5735
Mem: 3235
I/O: 5138
2D: 1000
3D: 1427
PassMark Mobile v1.0.3000
====================
System: 1392
CPU: 4534
Disk: 1688
Memory: 1041
2D: 1736
3D: 483
Greetings Alex//
PS: Lost the benchmark data from firmware 4.0.7 couse I closed the file without saving But Quadrant total was around 2200 points. PassMark was IMHO around 4300 points in total, but the results of PassMark are very unstable.
I can't post either. Updated this over 4.0.7 deodexed and it is really fast:
80 G9 1 GHz 512 Mb RAM:
Quadrant 2735
CPU 4520
Mem 2547
I/O 4207
2D 990
3D 1411
Is your's the turbo version?
Only problem: i lost root...
rulerofkaos said:
I can't post either. Updated this over 4.0.7 deodexed and it is really fast:
80 G9 1 GHz 512 Mb RAM:
Quadrant 2735
CPU 4520
Mem 2547
I/O 4207
2D 990
3D 1411
Is your's the turbo version?
Only problem: i lost root...
Click to expand...
Click to collapse
How you install new firmware. I do a update firmware and now my tablet is broken
Sent from my GT-I9100 using xda app-developers app
rulerofkaos said:
Is your's the turbo version?
Click to expand...
Click to collapse
I have the "Archos 101 G9 Turbo 16GB, 1.2GHz" version.
BagbKa said:
How you install new firmware. I do a update firmware and now my tablet is broken
Click to expand...
Click to collapse
I updated as described in my first post.
My Archos is NOT rooted, deodexed or SEDed.
Can you enter the recovery? Then you could reformat the device and reinstall the system ans the sde. You'll need an Archos firmware aos file and all your data will bei deleted
Sent from my ARCHOS 80G9 using XDA Premium HD app
rulerofkaos said:
Can you enter the recovery? Then you could reformat the device and reinstall the system ans the sde. You'll need an Archos firmware aos file and all your data will bei deleted
Sent from my ARCHOS 80G9 using XDA Premium HD app
Click to expand...
Click to collapse
No. Recovery and SDE didn't work. How i can restore recovery
Sent from my GT-I9100 using xda app-developers app
I've lost Recovery and SDE on my device too. But managed how to bring it back. (I'm not a specialist, use this on your own risk)
1. I've lost my recovery, after updating firmware from recovery.
2. After that I return to my old firmware (thanks God it's alive) using "Power on + Vol+ + Vol-" on the powered off device.
3. Followed Surdu's instructions here.
4. Rebooted.
5. Connected my Archos to computer, and copied working official firmware_archos_it4.aos ver. 4.0.7 on it.
6. Archos authomatically detect this update and offered me to apply it.
7. I've agreed on that and device had rebooted.
8. After flashing it's bring's me back recovery and sde.
Good luck!
I'm personally, would recommend to wait the official release, I think it will be there in 2 weeks and will not make you bricks factory.
theadenter said:
I've lost Recovery and SDE on my device too. But managed how to bring it back. (I'm not a specialist, use this on your own risk)
1. I've lost my recovery, after updating firmware from recovery.
2. After that I return to my old firmware (thanks God it's alive) using "Power on + Vol+ + Vol-" on the powered off device.
3. Followed Surdu's instructions here.
4. Rebooted.
5. Connected my Archos to computer, and copied working official firmware_archos_it4.aos ver. 4.0.7 on it.
6. Archos authomatically detect this update and offered me to apply it.
7. I've agreed on that and device had rebooted.
8. After flashing it's bring's me back recovery and sde.
Good luck!
I'm personally, would recommend to wait the official release, I think it will be there in 2 weeks and will not make you bricks factory.
Click to expand...
Click to collapse
I've followed Surdus instructions, but not working how did you copy the files and apply the chown and chmod lines?
the1c3man said:
I've followed Surdus instructions, but not working how did you copy the files and apply the chown and chmod lines?
Click to expand...
Click to collapse
I copy files with es file manager. A do nothing with file attributes. Just reboot tablet and then install original 4.0.7 firmware. Thats all
Sent from my GT-I9100 using xda app-developers app
I recently bought another tablet off of eBay. This time, it's a very generic one. It does have branding and such, and calls itself "Hypertab", but it is no different from the other generic tablets with the same specs.
System Specifications
Android 4.2.2 Jellybean
Allwinner A23 - Cortex A7 Dualcore CPU 1.5GHz
Mali-400 GPU
512MB DDR3 RAM
2GB Inernal Flash Memory (Actual usable amount is less) + Expandable with MicroSD up to 32GB
Disclaimer (Please Read Before Continuing.)
I am in no way, shape or form, responsible for the outcome, positive or negative, of you following the provided instructions on this thread.
It worked for me, but that does not mean it will 100% work for you. You are responsible for any side effects and damage caused to your device, your property, anyone nearby, or yourself, which includes, but not limited to: software and/or hardware destruction of the device, robbery, riots, injury, death, acts of god, epidemics/pandemics, natural disasters, government shutdowns, mutations, getting a certain limb of your body stuck in a ceiling fan, etc. Rooting WILL void your warranty (if there is any).
Root Guide
Preparing to Root
Connect your tablet to your computer, and let the drivers install automagically or using PDAnet (http://forum.xda-developers.com/showthread.php?t=1983470) or Use this utility (http://forum.xda-developers.com/showthread.php?t=2091922), which seems to work better in my opinion. If you are on Windows 8, make sure to disable Driver Signature Verification.
Download Kingo Android Root: http://www.kingoapp.com/android-root/download.htm
Install the Program and any other dependencies.
Open the program. Click the "Agree" button on the top right corner of Kingo Root, and make sure there is a check mark.
Now, move over to your tablet. Hit the settings icon from your desktop or app drawer. Go to { } Developer Options.
One you're there, make sure that the options are on with the 'switch' on the top right corner of the screen. If not, tap it and turn it on.
Once the Developer Options are set to ON, check off USB debugging. Tap OK when the "Allow USB debugging?" window pops up.
Rooting the Device
Using a USB cable, connect your tablet to your computer.
Wait until Drivers are installed and Kingo Root Detects your tablet.
Hit "Root" or "Root Again" (as it said for my tablet).
Wait until Kingo Root finishes its magic.
Once Kingo finishes, and says that root was successful, reboot your device, and you can close Kingo Root.
Go to the play store (or Google the APK if you don't have Play Store) and download SuperSU or something similar.
Congratulations! Your Generic Allwinner A23 Tablet is now (or should be) rooted! To check that you have root permissions, download Root Checker from Google Play store or any other store.
Tweaks
Now that you have rooted the tablet, let's mess around with the system so it works as you want it to work!
Overclocking/Underclocking
Just use No-frills CPU Control (https://play.google.com/store/apps/details?id=it.sineo.android.noFrillsCPU&hl=en)
The tablet by default spins at 1.2 Ghz. It can be put up to it's maximum, 1.5. On mine, I also have the option of going to 2.0 GHz, but I've never tried it yet.
build.prop
Now this is an interesting one. I found some lines in the file that are interesting, and it seems editing some of them are quite helpful, especially with the battery life and performance. I've listed them below. In order to edit the file, I used JRummy's Build Prop Editor (https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor&hl=en).
chiphd.bright.max - The highest brightness for the display.
chiphd.bright.min - The lowest brightness for the display.
ro.hwa.force - Force GPU rendering. True/False
video.accelerate.hw - GPU rendering for videos. 0/1
The rest of the lines are quite common among all the devices I've seen so far, and frankly, googling "build prop battery saving tweaks" will do fine for them.
Have more tweaks? Just add them on to the thread, and I'll post them here with your name
FAQ
Is there a custom recovery for this tablet? Nope.
Is there a custom rom for this tablet? Nope.
Why? Nobody seems to know why but Allwinner is a bit hard-a'd about releasing the code so people can develop from it. They are also violating GPL in many ways so most threads about Custom Roms for these kind of tablets gets closed up on XDA.
Windows 8 Drivers
No drivers are being loaded on Windows 8. KingaRoot is not finding the tablet and in device manager I get a yellow ! and no drivers are loaded or can be found. Any suggestions?
shifattk said:
I recently bought another tablet off of eBay. This time, it's a very generic one. It does have branding and such, and calls itself "Hypertab", but it is no different from the other generic tablets with the same specs.
System Specifications
Android 4.2.2 Jellybean
Allwinner A23 - Cortex A7 Dualcore CPU 1.5GHz
Mali-400 GPU
512MB DDR3 RAM
2GB Inernal Flash Memory (Actual usable amount is less) + Expandable with MicroSD up to 32GB
Disclaimer (Please Read Before Continuing.)
I am in no way, shape or form, responsible for the outcome, positive or negative, of you following the provided instructions on this thread.
It worked for me, but that does not mean it will 100% work for you. You are responsible for any side effects and damage caused to your device, your property, anyone nearby, or yourself, which includes, but not limited to: software and/or hardware destruction of the device, robbery, riots, injury, death, acts of god, epidemics/pandemics, natural disasters, government shutdowns, mutations, getting a certain limb of your body stuck in a ceiling fan, etc. Rooting WILL void your warranty (if there is any).
Root Guide
Preparing to Root
Download Kingo Android Root: http://www.kingoapp.com/android-root/download.htm
Install the Program and any other dependencies.
Open the program. Click the "Agree" button on the top right corner of Kingo Root, and make sure there is a check mark.
Now, move over to your tablet. Hit the settings icon from your desktop or app drawer. Go to { } Developer Options.
One you're there, make sure that the options are on with the 'switch' on the top right corner of the screen. If not, tap it and turn it on.
Once the Developer Options are set to ON, check off USB debugging. Tap OK when the "Allow USB debugging?" window pops up.
Rooting the Device
Using a USB cable, connect your tablet to your computer.
Wait until Drivers are installed and Kingo Root Detects your tablet.
Hit "Root" or "Root Again" (as it said for my tablet).
Wait until Kingo Root finishes its magic.
Once Kingo finishes, and says that root was successful, reboot your device, and you can close Kingo Root.
Congratulations! Your Generic Allwinner A23 Tablet is now (or should be) rooted! To check that you have root permissions, download Root Checker from Google Play store or any other store.
Click to expand...
Click to collapse
The program is not finding my tablet... just shows "no device connected" any suggestions?
Try to install the ADB drivers using this tool here:
http://forum.xda-developers.com/showthread.php?t=2091922
shifattk said:
Try to install the ADB drivers using this tool here:
http://forum.xda-developers.com/showthread.php?t=2091922
Click to expand...
Click to collapse
its showing up as samsung galaxy sii is that okay?
Kobro said:
its showing up as samsung galaxy sii is that okay?
Click to expand...
Click to collapse
You could try, but I doubt that will work since it will install the drivers for SII
I've also found this which could help: http://forum.xda-developers.com/showthread.php?t=1983470
Sorry for being a bit vague. I remember installing the drivers for mine using some 'universal' tool but I can't remember which one and/or how I did it.
shifattk said:
You could try, but I doubt that will work since it will install the drivers for SII
I've also found this which could help: http://forum.xda-developers.com/showthread.php?t=1983470
Sorry for being a bit vague. I remember installing the drivers for mine using some 'universal' tool but I can't remember which one and/or how I did it.
Click to expand...
Click to collapse
I was able to obtain root using Kingo Android Root
http://www.kingoapp.com/android-root/download.htm
Windows 7 could not find the correct driver for "Android Device".
I installed PDAnet from this thread and it installed the requisite drivers:
http://forum.xda-developers.com/showthread.php?t=1983470
Kingo Android Root then detected my device after reboot and reconnecting tablet.
It went through it's gyrations without any issue.
A quick look at "Root Checker" application... It's rooted!
This is a "Q8 7" 8GB Allwinner A23 Dual Core Android 4.2 Tablet PC Wifi Camera IM" from Tmart.
Specs:
CPU Processor Allwinner A23 ARM Cortex A7 Dual Core, 1.5GHz
GPU Mali400MP2
Operating System Android 4.2
Display Size 7"
Resolution 800*480 Pixel
Touch Screen 5-points Capacitive Touch Screen
RAM 512MB
Storage Size 8GB
External Memory Support TF card up to 32GB (not included)
Hopefully others who bought this tablet from Tmart can find this thread with the additional keywords.
If anyone runs across a KitKat 4.4x rom for this tablet, PLEASE reply. Thanks.
P.S.
Tablet issues out of the box.
Battery - Labeled as 2800mAh. Not even close. I get about 10 minutes starting at 100%
I ordered a battery from eBay to replace it: http://www.ebay.com/itm/171375484987
Touchscreen - MOSTLY ok. Except in landscape mode... the "W" or "2" doesn't work. I get a "1" PLUS a "3"... the two adjacent characters.
Update to 4.4 when available should cure this, yes? Any other relatively simple fix?
Assuming I can rectify these two issues... For $39.99 it's a pretty good deal.
(Thanks for the original post shifattk)
Any possibilities of getting a custom recovery for this or locating the recovery.IMG?
:good::good::good::good::good:
Could you help how to solve this problem.
As you can see (picture 1), the second Internal Storage capacity is 3.50GB but the availabe space is weird (unknown number)
I've done the memory swapping (with 16GB) method by editing the vold.fstab file and the result (picture 2). As you can see now, the 2nd internal memory only detect 3.50GB (not 16GB) while the SDCARD is 720MB (is it suppose to be 3.5/4 GB).
I think I have been cheated for the 2nd internal memory suppose to be at least 4GB.
Could you help me how to get maximum memory (16GB) after swap...
[HELP] Firmware Tablet Allwinner A23 GA10H
Hi,
I need a stock firmware image to flash and unbrick a Tablet PC Allwinner A23 model GA10H. Description:
Model No: GA10H
Operation System: Android 4.2
Screen: 10.1 inch TFT 5 Point Touch Capacitive Screen
Resolution: 1024x600(16:9) Pixel
CPU: Allwinner A23 ARM Cortex-A7 Dual-Core 1.5GHz
GPU: Mali-400 MP2
RAM:1GB DDR3/ 512MB
Nand Flash: 8GB
The manufacturer´s website (AZhuo Digital) don´t offers the stock firmware to download.
Please help me.
Thanks a Lot
Luciano Scharf
it seems that getting the recovery.img for the tab is such a pain. Thus it is difficult to create a custom recovery using CWM or TWRP. The generic Rom is also a bit unstable and tends to freeze the device or autoreboots and some occasional auto sleeping of the LCD even when you set the sleep mode to any time.
Theory: possible that the freezing is caused by either bad ram management or high voltage per frequency. Already underclocked the device and it seemed to help it a little bit. Cannot try to test undervolting and even installing supercharger unless there is a way to create a NanDroid backup image.
izuall187 said:
it seems that getting the recovery.img for the tab is such a pain. Thus it is difficult to create a custom recovery using CWM or TWRP. The generic Rom is also a bit unstable and tends to freeze the device or autoreboots and some occasional auto sleeping of the LCD even when you set the sleep mode to any time.
Theory: possible that the freezing is caused by either bad ram management or high voltage per frequency. Already underclocked the device and it seemed to help it a little bit. Cannot try to test undervolting and even installing supercharger unless there is a way to create a NanDroid backup image.
Click to expand...
Click to collapse
Getting Recovery from these is not difficult at all.
With ADB properly set up on your PC and USB Debugging enabled on the Tab Browse to a location
on your PC where you have the ADB.exe (usually someplace like this D:\Android\sdk\platform-tools)
or have the folder with ADB.exe in your Path environment setting.
From that folder launch a command window (right click while holding shift) while in the folder in explorer
select open command window here.
In the command window type
adb remount
adb shell su -c "cat /dev/block/nandg > /mnt/sdcard/nandg-recovery.img"
adb pull /mnt/sdcard/nandg-recovery.img
adb shell rm /mnt/sdcard/nandg-recovery.img
The recovery image will be in the folder you executed the command window from.
Honestly though DragonFace can edit the Roms for allwinner soc's extremely well and it extracts the
seperate .img files from the Rom, My suggestion would be to First obtain your Tabs Factory Firmware
Back up all of the main Partitions on your Tab before doing Anything if you do not have your Original
Factory Firmware available. (nanda, nandc, nandd, nande, nandg - bootloader, boot, system, Data, Recovery)
Also I suggest you Pull a script.bin from the Tab as well as it contains the settings for your Hardware
initialization, and determine what Hardware is in it at least the main ones that differ on these Tabs
Touchscreen, Gsensor, Cameras and in some cases Bluetooth.
Once you have done this you can start editing your Rom in Dragonface with relative safety, or download
some other Firmwares for the A23 and attempt to mod them to work on your Hardware set.
To make a custom recovery the SDK is here : http://dl.linux-sunxi.org/SDK/A23-v1.0/
and there are a few Instructions on XDA you can follow once you have that, although you will likely
have to edit the output in some ways and/or the input.
You can feel pretty safe in Flashing Allwinner Devices as much as you like in your Testing, this SOC
family tends to be practically unbrickable, the basic fel is in the SOC and is not overwritten by a flash
so even flashing a completely wrong rom is recoverable by flashing one that more closely matches
the hardware.
There are currently many Roms available for this device Family the latest ones being android v 4.4
post ROOT Allwinner Polaris 1
High, I'm new to all of this. I have root and installed CPU tweak and am. Lost on the prop editing II am wanting to increase keyboard react loading and any tweaks.. I'm not sure what to do. Also I would like to get my allwinner upgraded hope to be able t
Thanks
A23 Manual Backup
Thanks fsebentley, that was extremely helpful!
fsebentley said:
My suggestion would be to First obtain your Tabs Factory Firmware
Back up all of the main Partitions on your Tab before doing Anything if you do not have your Original
Factory Firmware available. (nanda, nandc, nandd, nande, nandg - bootloader, boot, system, Data, Recovery)
Also I suggest you Pull a script.bin from the Tab as well as it contains the settings for your Hardware
initialization, and determine what Hardware is in it at least the main ones that differ on these Tabs
Touchscreen, Gsensor, Cameras and in some cases Bluetooth.
Click to expand...
Click to collapse
I do not have a factory firmware image. I see the block devices for the different nand partitions, and was able to back those up, great!
But I'm not sure how you go about backing up the other things you mentioned w/out having something like clockwork recovery installed. Could you elaborate on the backup steps for bootloader, boot, system, etc. Also on how to pull the hardware settings (script.bin) ? I've never done this manually outside of another program.
EDIT: after sleep I understood what you meant up there :
nanda == bootloader, etc.
EDIT2: Here's the full list from my Ubislate 7ci
Code:
[email protected]:/dev/block/by-name # ls -l
lrwxrwxrwx root root 2014-10-20 23:24 UDISK -> /dev/block/nandj
lrwxrwxrwx root root 2014-10-20 23:24 boot -> /dev/block/nandc
lrwxrwxrwx root root 2014-10-20 23:24 boot-resource -> /dev/block/nanda
lrwxrwxrwx root root 2014-10-20 23:24 cache -> /dev/block/nandh
lrwxrwxrwx root root 2014-10-20 23:24 data -> /dev/block/nande
lrwxrwxrwx root root 2014-10-20 23:24 databk -> /dev/block/nandi
lrwxrwxrwx root root 2014-10-20 23:24 env -> /dev/block/nandb
lrwxrwxrwx root root 2014-10-20 23:24 misc -> /dev/block/nandf
lrwxrwxrwx root root 2014-10-20 23:24 recovery -> /dev/block/nandg
lrwxrwxrwx root root 2014-10-20 23:24 system -> /dev/block/nandd
Can all of those be backed up "live" or do you need to get into recovery to do it so that the filesystems are closed?
-m
fsebentley said:
Getting Recovery from these is not difficult at all.
With ADB properly set up on your PC and USB Debugging enabled on the Tab Browse to a location
on your PC where you have the ADB.exe (usually someplace like this D:\Android\sdk\platform-tools)
or have the folder with ADB.exe in your Path environment setting.
From that folder launch a command window (right click while holding shift) while in the folder in explorer
select open command window here.
In the command window type
adb remount
adb shell su -c "cat /dev/block/nandg > /mnt/sdcard/nandg-recovery.img"
adb pull /mnt/sdcard/nandg-recovery.img
adb shell rm /mnt/sdcard/nandg-recovery.img
The recovery image will be in the folder you executed the command window from.
Honestly though DragonFace can edit the Roms for allwinner soc's extremely well and it extracts the
seperate .img files from the Rom, My suggestion would be to First obtain your Tabs Factory Firmware
Back up all of the main Partitions on your Tab before doing Anything if you do not have your Original
Factory Firmware available. (nanda, nandc, nandd, nande, nandg - bootloader, boot, system, Data, Recovery)
Also I suggest you Pull a script.bin from the Tab as well as it contains the settings for your Hardware
initialization, and determine what Hardware is in it at least the main ones that differ on these Tabs
Touchscreen, Gsensor, Cameras and in some cases Bluetooth.
Once you have done this you can start editing your Rom in Dragonface with relative safety, or download
some other Firmwares for the A23 and attempt to mod them to work on your Hardware set.
To make a custom recovery the SDK is here : http://dl.linux-sunxi.org/SDK/A23-v1.0/
and there are a few Instructions on XDA you can follow once you have that, although you will likely
have to edit the output in some ways and/or the input.
You can feel pretty safe in Flashing Allwinner Devices as much as you like in your Testing, this SOC
family tends to be practically unbrickable, the basic fel is in the SOC and is not overwritten by a flash
so even flashing a completely wrong rom is recoverable by flashing one that more closely matches
the hardware.
There are currently many Roms available for this device Family the latest ones being android v 4.4
Click to expand...
Click to collapse
Wait a minute.. aren't you the same "fsebentley" person from "Techknow"?
I have a tablet running 4.2.2 I want a good way to move apps to the external SD I have tried multiple tricks and none seem to work. i even use adb to force installing items to the SD. I have tried gl to sd, but it will just move items to portions of the internal memory labeled as ext sd but not the real external one. any other ideas?
asim.sidz said:
Wait a minute.. aren't you the same "fsebentley" person from "Techknow"?
Click to expand...
Click to collapse
Yes that is me
---------- Post added at 04:19 AM ---------- Previous post was at 04:14 AM ----------
ChiefWilNel said:
I have a tablet running 4.2.2 I want a good way to move apps to the external SD I have tried multiple tricks and none seem to work. i even use adb to force installing items to the SD. I have tried gl to sd, but it will just move items to portions of the internal memory labeled as ext sd but not the real external one. any other ideas?
Click to expand...
Click to collapse
In large part this will depend on the Tablet as well as the OS. I would suggest one of the many Apps2sd programs
available both from Play store as well as on this forum, most include pretty decent instructions on use.
Personally for installing apps onto my sd card I use Link2sd, it does however require extra partitioning of your external SD card and a working implementation of init.d that kicks off before full boot so if you are not
very android savvy it may not be for you.
---------- Post added at 04:28 AM ---------- Previous post was at 04:19 AM ----------
maxslug said:
Thanks fsebentley, that was extremely helpful!
I do not have a factory firmware image. I see the block devices for the different nand partitions, and was able to back those up, great!
But I'm not sure how you go about backing up the other things you mentioned w/out having something like clockwork recovery installed. Could you elaborate on the backup steps for bootloader, boot, system, etc. Also on how to pull the hardware settings (script.bin) ? I've never done this manually outside of another program.
EDIT: after sleep I understood what you meant up there :
nanda == bootloader, etc.
EDIT2: Here's the full list from my Ubislate 7ci
Code:
[email protected]:/dev/block/by-name # ls -l
lrwxrwxrwx root root 2014-10-20 23:24 UDISK -> /dev/block/nandj
lrwxrwxrwx root root 2014-10-20 23:24 boot -> /dev/block/nandc
lrwxrwxrwx root root 2014-10-20 23:24 boot-resource -> /dev/block/nanda
lrwxrwxrwx root root 2014-10-20 23:24 cache -> /dev/block/nandh
lrwxrwxrwx root root 2014-10-20 23:24 data -> /dev/block/nande
lrwxrwxrwx root root 2014-10-20 23:24 databk -> /dev/block/nandi
lrwxrwxrwx root root 2014-10-20 23:24 env -> /dev/block/nandb
lrwxrwxrwx root root 2014-10-20 23:24 misc -> /dev/block/nandf
lrwxrwxrwx root root 2014-10-20 23:24 recovery -> /dev/block/nandg
lrwxrwxrwx root root 2014-10-20 23:24 system -> /dev/block/nandd
Can all of those be backed up "live" or do you need to get into recovery to do it so that the filesystems are closed?
-m
Click to expand...
Click to collapse
Yes all can be backed up live, you will likely need to have the output of the command be placed on your
external sd due to size limitations unless you have around 4gig internal sd available. I did write a small
script to do it automatically, it is posted on Techknow in the open forum.
I am going to be actively looking into making a TWRP/CWM for these A23's now since I am beginning dev
work on the platform for making a custom Rom, I have not decided yet whether to pattern Hardware
support after my A13 CookedRom or not, im not sure I will have time for making patches for all the different
hardware sets as I am also planning Roms for the A20 and the A31. The similarities in the Allwinner SOC's
will make the work a bit easier on multi-SOC's but it is still more than I have time for to manage hardware
Patches for them as well as to keep up support on all of them.
fsebentley said:
Yes that is me
---------- Post added at 04:19 AM ---------- Previous post was at 04:14 AM ----------
In large part this will depend on the Tablet as well as the OS. I would suggest one of the many Apps2sd programs
available both from Play store as well as on this forum, most include pretty decent instructions on use.
Personally for installing apps onto my sd card I use Link2sd, it does however require extra partitioning of your external SD card and a working implementation of init.d that kicks off before full boot so if you are not
very android savvy it may not be for you.
---------- Post added at 04:28 AM ---------- Previous post was at 04:19 AM ----------
Yes all can be backed up live, you will likely need to have the output of the command be placed on your
external sd due to size limitations unless you have around 4gig internal sd available. I did write a small
script to do it automatically, it is posted on Techknow in the open forum.
I am going to be actively looking into making a TWRP/CWM for these A23's now since I am beginning dev
work on the platform for making a custom Rom, I have not decided yet whether to pattern Hardware
support after my A13 CookedRom or not, im not sure I will have time for making patches for all the different
hardware sets as I am also planning Roms for the A20 and the A31. The similarities in the Allwinner SOC's
will make the work a bit easier on multi-SOC's but it is still more than I have time for to manage hardware
Patches for them as well as to keep up support on all of them.
Click to expand...
Click to collapse
Good to see you here. Get ready because i'm going to bombard you with my intricate queries here as well!
fsebentley said:
There are currently many Roms available for this device Family the latest ones being android v 4.4
Click to expand...
Click to collapse
where are these 4.4 roms
ChiefWilNel said:
where are these 4.4 roms
Click to expand...
Click to collapse
They can generally be found by searching for A23 firmware via google.
Offhand the Irulu site and a few others have Roms available, whether they will work for your specific
model is another question entirely and in general you will simply have to check based on the internals
of your tab vs those supported by the Rom. Irulu Has several different 4.4 Roms for different models
using the A23 SOC, I also suggest that if you want more leads on Roms you might look on TechKnow
there are several source links there that will help get you started on a search.
Recently I received a request from a friend to help them with a tablet. The complaint was lots of adverts showing when using the tablet. Some info:
Manufacturer: Denver
Make: TAQ-10123 MK2
Model: PO-9839
Android: 5.1.1
Code Name: astar_m100 (astar-m100)
PCB is labelled 'Eferco M100_MB 3.0'. CPU-Z identifies it as follows: 'Cortex' + 'Allwinner A23 1.34GHz' + '4x ARM Cortex-A7 @ 1.34GHz', Model 'PO-9839 (astar_m100)', Manufacturer 'Denver', Board 'exdroid', Hardware 'sun8i', Screen Resolution '1024 x 600', Build ID 'astar_m100-eng 5.1.1 LMY47V 20160304 test-keys', Android Version '5.1.1', API Level '22'.
Manufacturer product webpage: denver-electronics.com/denver-taq-10123mk2/
(archive link): web.archive.org/web/20170317121038/denver-electronics.com/denver-taq-10123mk2/
I asked the manufacturer for the factory firmware and they sent me a 'wetransfer' link. I have re-compressed their ZIP archive into a 7Z archive, saving several hundred MB and re-hosted it on Mega.
Factory firmware: mega.nz/#!s4MAFTLa!TqrXXHShfxvqNg6wwQ10LsS2VuZQWgNGfmklouVLr-8
Just a warning, the default file manager installed on the tablet and also in the factory image is infected with a trojan. Specifically, /system/app/FileExplore/FileExplore.apk is detected as infected with 'Backdoor.AndroidOS.Coudw.a' by both Malwarebytes & Kaspersky. Virustotal scan results here: virustotal.com/en/file/e99b9b1d976cce2d4b34afc918950a6a71295e4694ec60a86c0494daf0f89872/analysis/1488895182/
Likely the source of all the adverts and crap. The tablet comes with an insecure ADB configuration by default, so once you install the necessary drivers and connect it to your computer, you can use ADB to have root access to the device. This makes it easy to disable or remove the infected file manager.
The device has an unlocked bootloader and you can easily flash your own firmware images.
The device is built using an Allwinner A33 SoC. CPU-Z will falsely identify this as the A23, but as the device is Quad-Core, you can clearly tell it is based on the A33 SoC. Further information can be found here: linux-sunxi.org/A23 & linux-sunxi.org/A33.
Information on partition layout here: linux-sunxi.org/Android/partitions
I have managed to hack together a working TWRP build for this device. As most A33 devices out there seem to be running 4.4, this may be of use to other tablet owners running Allwinner A33 based tablets that are running 5.1.1. I have compressed and uploaded to Mega.
TWRP: mega.nz/#!NkUCBJLQ!IL2Htl_0DifU-_wjuRD6ESwiCGw2-CxlumYmn9K9e7w
To flash, start the tablet normally and then connect to a computer, run 'adb reboot-bootloader'. Once that is complete, install the proper drivers if they don't auto-detect, and then run this command 'fastboot -i 0x1f3a flash recovery TWRP.img' - modifying the name of the IMG to whatever you have named it. Also, this device is a bit weird in that to boot to recovery, you have to hold down VOL+ and POWER and then quickly release VOL+ and then press and hold it again, releasing POWER shortly after the 'DENVER' logo shows on the screen. (otherwise it won't power up).
I used many different sources of information in getting this far, I will try and link them in later. For now - at least you have a TWRP image so you can easily root and begin hacking away. Also the default firmware means you can easily recover from any mistakes.
How to back up the firmware already on your device: forum.xda-developers.com/showpost.php?p=55973453&postcount=12
This gives you something to safely restore from in case you can't get a factory firmware image for your unit. For additional advice, see this thread: forum.xda-developers.com/showthread.php?t=2450045
Other Allwinner threads:
forum.xda-developers.com/showthread.php?t=3038123
<reserved>
Android 13 Developer Preview 1 horror story: If you can't unlock your bootloader, you shouldn't run especially so early in development versions of Android, because there's nothing you can do to fix it once you've "upgraded" to a newer version of Android, except wait for the next Developer Preview or Beta (or closer to release, Stable).
Deep Dive on Twitter:
Lughnasadh said:
Here's a little deeper dive into Tiramisu DP1...
https://twitter.com/i/web/status/1491838098161819679
Click to expand...
Click to collapse
Deep Dive in BLOG format:
Lughnasadh said:
Another deep dive by Mishaal Rahman in blog form...
Android 13 changelog: A deep dive by Mishaal Rahman
This is everything you need to know about new Android 13 features, its release date, and API changes for developers.
blog.esper.io
Click to expand...
Click to collapse
Here there be dragons. I am not responsible for anything at all.
Note the warning in the article:
Warning: The preview releases are intended for developers only, so don’t install them on your daily driver. You might encounter showstopper bugs or other system instabilities. It is highly recommended that you back up your data before proceeding. Users are advised to exercise caution.
Click to expand...
Click to collapse
TL;DR:
For supported Google Pixels: Sideload Android 13 via Recovery and ADB
For supported Google Pixels: Flashing full Factory Image via Fastboot
Any Project Treble-compatible Android device: Install Android 13 GSI
The recommended way to flash Android 13 to a Pixel device is to use the Android Flash Tool.If you'd rather flash your device manually, you can get an Android 13 system image for your device on the Pixel downloads page. See the general instructions on the downloads page for how to flash a system image to your device. This approach can be useful when you need more control over testing, such as for automated testing or regression testing.Be sure you're using the latest SDK Platform Tools and Google USB Driver.For eligible Google Pixel devices, you can download the first Developer Preview build of Android 13 from the links below:
DeviceOTAFactory ImageGoogle Pixel 4Download LinkDownload LinkGoogle Pixel 4 XLDownload LinkDownload LinkGoogle Pixel 4aDownload LinkDownload LinkGoogle Pixel 4a 5GDownload LinkDownload LinkGoogle Pixel 5Download LinkDownload LinkGoogle Pixel 5aDownload LinkDownload LinkGoogle Pixel 6Download LinkDownload LinkGoogle Pixel 6 ProDownload LinkDownload Link
How to install Android 13 on Google Pixel and other Android devices:
February 10, 2022 1:00pm Skanda Hazarika
How to install Android 13 on Google Pixel and other Android devicesAndroid 13 is making its first appearance today. The flashaholics will be delighted to know that Google has already made the system images available for download. You can give it a shot right now if you’ve got the right hardware, but there aren’t as many supported devices this time around. All you’ve got to choose from are the Google Pixel 4, Pixel 4 XL, Pixel 4a, Pixel 4a 5G, Pixel 5, Pixel 5a, Pixel 6, and the Pixel 6 Pro.
The first developer preview of Android 13 is, of course, rough around the edges, so Google doesn’t want to make it too easy to install it on your daily driver. You’ll need an eligible Pixel smartphone with an unlocked bootloader to flash the system image using your computer. There are also OTA files, which update your Pixel to the Developer Preview without an unlocked bootloader. However, you still need to manually sideload the OTA package.
Apart from device-specific firmware packages, Google has also published the first Developer Preview build of Android 13 as a Generic System Image (GSI) that can be flashed on a much wider range of devices. Google validated them on the aforementioned Pixel smartphones, but they should technically boot on any Project Treble-compatible device.
Warning: The preview releases are intended for developers only, so don’t install them on your daily driver. You might encounter showstopper bugs or other system instabilities. It is highly recommended that you back up your data before proceeding. Users are advised to exercise caution.
The three methods to install the update are:
For supported Google Pixels: Sideload Android 13 via Recovery and ADB
For supported Google Pixels: Flashing full Factory Image via Fastboot
Any Project Treble-compatible Android device: Install Android 13 GSI
Method 1: Sideload Android 13 via Recovery and ADBTo install the Developer Preview, you need to sideload the appropriate OTA package for your device from Recovery through ADB. This method will also work for Google Pixel devices with a locked bootloader.
Download the update .zip file on your computer from here. For convenience, you can rename this file to a simpler name and place the file in the directory where ADB is located on your computer.
Optional, but recommended: Verify the SHA-256 checksum of the file you have downloaded to ensure that the file has been downloaded completely and correctly.
Enable USB Debugging on your phone — Go to Settings > About Phone > Tap Build Number 7 times, (optionally) enter your pattern, PIN or password to enable Developer Options, and then navigate to Settings > Developer Options > Enable USB Debugging.
Connect your phone to your computer. Authorize your computer connection on your phone when the prompt comes up on your phone, if this is the first time you are connecting with the ADB instance of this computer.
On your computer, run the command:adb reboot recovery
Your phone should now be in Recovery mode.
On your phone, select the option Apply Update from ADB.
On your computer, run the command:adb devices
This should return a device serial with the “sideload” next to its name, indicating that your device is connected to the computer in sideload mode.
On your computer, run the command:adb sideload "filename".zip
The “filename” part is to be replaced with the name of the file downloaded in Step 1.
The update should install on your phone. Once the installation is complete, choose Reboot system now on your phone to reboot into Android 13.
Method 2: Flashing full Factory Image via FastbootIf you have an unlocked bootloader on a Google Pixel device, you need to flash the factory image of the Android 13 Developer Preview via Fastboot. Usually, this is done through a flash-all.sh or flash-all.bat script file that is included in the downloaded file, but its default configuration also wipes the device completely. You can, however, retain your data by deleting the “-w” wipe attribute from the command within the script.
Download the factory image .zip file on your computer from here.
Optional, but recommended: Verify the SHA-256 checksum of the file you have downloaded to ensure that the file has been downloaded completely and correctly.
Extract the .zip file, and copy and paste the resultant files onto your ADB and fastboot folder on your computer for convenience.
Optional: The resultant files would contain a flash-all.sh or flash-all.bat script file. Using a text editor, open the flash-all.sh if you’re on macOS/Linux or the flash-all.bat script file if you’re on Windows. Find and remove/delete the -w flag in the fastboot update command. This will skip the data wipe for your phone. To avoid compatibility issues, a data wipe is recommended though.
Enable USB Debugging on your phone — Go to Settings > About Phone > Tap Build Number 7 times, (optionally) enter your pattern, PIN or password to enable Developer Options, and then navigate to Settings > Developer Options > Enable USB Debugging.
Connect your phone to your computer. Authorize your computer connection on your phone when the prompt comes up on your phone, if this is the first time you are connecting with the ADB instance of this computer.
On your computer, run:adb reboot bootloader
This will reboot your phone into Fastboot mode.
On your Mac/Linux PC, run:flash-all
This command executes the flash-all.sh script file, which will then install the necessary bootloader, baseband firmware, and operating system. If you are on Windows, you can simply double click the flash-all.bat file.
Once the script finishes, your device will reboot into the new OS.
Method 3: Install Android 13 GSIEven if you don’t own a compatible Pixel smartphone, you can still install Google’s official GSI binaries to test Android 13, provided your device is compatible with Project Treble. You also need an unlocked bootloader. The last thing that we need to say is that flashing a GSI will require you to factory reset your device, so be sure you’re prepared to lose app data before you proceed with this! We recommend you make an off-device backup (such as on your PC or an SD Card) in case anything goes wrong.
Download links for the official Android 13 Developer Preview GSIs can be found here. You should download the appropriate version based on your device’s architecture. To see which architecture your device has, run the following command:adb shell getprop ro.product.cpu.abi
Optional but recommended: Verify the SHA-256 checksum of the file you have downloaded to ensure that the file has been downloaded completely and correctly.
Extract the .zip file, and copy and paste the resultant files (system.img and vbmeta.img) onto your ADB and fastboot folder on your computer for convenience.
Enable USB Debugging on your phone — Go to Settings > About Phone > Tap Build Number 7 times, (optionally) enter your pattern, PIN or password to enable Developer Options, and then navigate to Settings > Developer Options > Enable USB Debugging.
Connect your phone to your computer. Authorize your computer connection on your phone when the prompt comes up on your phone, if this is the first time you are connecting with the ADB instance of this computer.
On your computer, run:adb reboot bootloader
This will reboot your phone into Fastboot mode.
As mentioned earlier, the bootloader of the target device must be unlocked beforehand.
Next, we need to disable Android Verified Boot (AVB). To do that, run the following command:fastboot flash vbmeta vbmeta.img
Optional but recommended: Enter the following to wipe the system partition:fastboot erase system
Flash the Android 13 GSI:fastboot flash system system.img
Allow the image to flash, it could take a few minutes. Once that’s done, wipe the userdata partition:fastboot -w
Finally, reboot your device:fastboot reboot
Hopefully, your device should boot into the new build of Android.
Click to expand...
Click to collapse
How to download Android 13 for Google Pixel and other Android devices:
February 10, 2022 1:07pm Skanda Hazarika
How to download Android 13 for Google Pixel and other Android devicesGet ready to dig into Android 13! While we are still waiting for Android 12L to be officially released via stable channel, the next major release of Google’s OS is now available starting today in the form of the first Android 13 Developer Preview. For lucky owners of the Google Pixel 6, Pixel 6 Pro, Pixel 5a, Pixel 5, Pixel 4a 5G, Pixel 4a, Pixel 4, or Pixel 4 XL, you’ll be among the first users to see what Android 13 “Tiramisu” has to offer.
Notably, existing Android beta participants won’t automatically get the first Android 13 Developer Preview as an over-the-air update. The preview release must be manually sideloaded. You can learn how to install Android 13 on Google Pixel smartphones and other devices by visiting our dedicated guide here.
Keep in mind that the initial build won’t give you the full Android 13 experience as it’s very much a work-in-progress. This first preview is aimed solely at developers, since they need to test their apps against new Android platform APIs months before the next Android version becomes available for the general public. Installing the Developer Preview on your daily driver isn’t recommended, as you might face various system instabilities. Do back up your data before proceeding.
This page will serve as a one-stop download index for every Android 13 build released by Google. We will keep the page updated with the latest OTAs and factory images for the supported Pixel smartphones.
Navigate this page:
Download Android 13:
Developer Preview 1
Download Android 13 for Google Pixel devicesAndroid 13 Developer Preview 1For eligible Google Pixel devices, you can download the first Developer Preview build of Android 13 from the links below:
DeviceOTAFactory ImageGoogle Pixel 4Download LinkDownload LinkGoogle Pixel 4 XLDownload LinkDownload LinkGoogle Pixel 4aDownload LinkDownload LinkGoogle Pixel 4a 5GDownload LinkDownload LinkGoogle Pixel 5Download LinkDownload LinkGoogle Pixel 5aDownload LinkDownload LinkGoogle Pixel 6Download LinkDownload LinkGoogle Pixel 6 ProDownload LinkDownload Link
Additionally, Google offers ready-to-use Android 13 Developer Preview system images under the Android Emulator in Android Studio.
Click to expand...
Click to collapse
Three separate branches in a single week. Wow.
Time to check the modem again lol. Probably older than 12L and we flash on top.
LLStarks said:
Three separate branches in a single week. Wow.
Time to check the modem again lol.
Click to expand...
Click to collapse
Good luck! As always, please let us know your thoughts (goes for anyone who tries it). I'll likely be sticking to regular 12, at least until closer to when 13 releases, unless I hear about some stupendous new feature that I want to try.
Edit: Maybe I misremembered which release was going to be Android T (so great, both 12 and 12L are S). Old: Now, I thought I heard reference to 12L being Android T (as it should be since it's a new API level), so 13 should be U. My wife suggests Upside-down Cake. Any other better ideas? I'm sure someone's got to have a better idea.
Modem is newer than Feb but older than 12L. Bootloader is version 1.2 compared to 1.1 in 12L and 1.0 in Feb.
Mixed bag. Need to see what 13 modem is capable of (i.e. VoNR, C-Band, etc).
VoNR and C-Band are present. Rooting works as expected.
Edit: This update adds 3 carrier 5G aggregation?!?! n41-n71-n71 and n41-n41 looks to be present with the latter also appearing in 12L.
Here's a little deeper dive into Tiramisu DP1...
https://twitter.com/i/web/status/1491838098161819679
LLStarks said:
VoNR and C-Band are present. Rooting works as expected.
Edit: This update adds 3 carrier 5G aggregation?!?! n41-n71-n71 and n41-n41 looks to be present with the latter also appearing in 12L.
Click to expand...
Click to collapse
Are you using the latest stable Magisk?
As for root, just flashing a patched boot image?
I always use the latest alphas for Magisk and patch my own files.
Lughnasadh said:
Here's a little deeper dive into Tiramisu DP1...
Click to expand...
Click to collapse
Another deep dive by Mishaal Rahman in blog form...
Android 13 changelog: A deep dive by Mishaal Rahman
This is everything you need to know about new Android 13 features, its release date, and API changes for developers.
blog.esper.io
Lughnasadh said:
Another deep dive by Mishaal Rahman in blog form...
Android 13 changelog: A deep dive by Mishaal Rahman
This is everything you need to know about new Android 13 features, its release date, and API changes for developers.
blog.esper.io
Click to expand...
Click to collapse
Thanks! Adding to the OP.
So I guess their is no GSI version available as 2_12_20? Or did I get that wrong.
hooutoo said:
So I guess their is no GSI version available as 2_12_20? Or did I get that wrong.
Click to expand...
Click to collapse
Good question or observation. Indeed, it appears XDA's article references things that don't seem to be available, or at least their link to where it claims it is available doesn't lead to anything obvious. But I think it's just confusing, at least to this non-developer (me).
I think they're merely reflecting the official information Google gives, which also leads to a dead-end regarding GSI versions:
This search https://www.google.com/search?q=and...69i57j0i390.4224j0j7&sourceid=chrome&ie=UTF-8
led me to the 3rd or 4th search result "The first developer preview of Android 13" at https://android-developers.googleblog.com/2022/02/first-preview-android-13.html#:~:text=For even broader testing, GSI images are available, and their statement is the same:
If you don’t have a Pixel device, you can use the 64-bit system images with the Android Emulator in Android Studio. For even broader testing, GSI images are available.
When you’re set up, here are some of the things you should do:
Click to expand...
Click to collapse
The link at "set up" leads to Set up the Android 13 SDK, which includes the step of using Android Studio.
Since at the first search I give above, the 2nd or 3rd search result Generic System Image releases doesn't have anything for Android 13 (but it does mention 12L), in the end I believe that one or both of the following are true:
GSIs are only available for Android 13 through the Android Studio - i.e. to emulate a device running the Android 13 GSI.
and/or
They goofed up and included language that made it sound like GSIs are available to actually download and flash on physical devices, perhaps in preparation for when they do intend to have the GSIs available later in the development process - maybe once it progresses from Developer Preview 2 to Beta 1?
Ya, I was thinking the same thing. A lot what was mentioned in the OP is just copy/paste material for when the gsi rom drops.
https://twitter.com/i/web/status/1493335334125379586
Already got dp1 running on my lg v60.
Need some info. On my lg v60, after installing Pixel-Pixel4a-DP1-A13-AB-Tiramisu-20220211-NipponGSI.img, I checked settings>system>system update. I'm getting Android 12 on the dialog screen.
What does it show on an actual pixel phone?
hooutoo said:
Need some info. On my lg v60, after installing Pixel-Pixel4a-DP1-A13-AB-Tiramisu-20220211-NipponGSI.img, I checked settings>system>system update. I'm getting Android 12 on the dialog screen.
What does it show on an actual pixel phone?
Click to expand...
Click to collapse
I wish I knew what to tell you. Perhaps someone else can help. I know nothing about GSIs, much less GSIs on LG devices, and I'm not stepping into the Android 13 (or even 12L) pool just yet.
Have you asked about this aspect in the LG V60 section?
Little review and tablet issues:
This is a 2020 Tablet, that was launched with Android 11, and the last security patch was December 2021.
Hardware
It packs an UNISOC Tiger T310, basically 1 ARM A75 and 3 A55
4 GB RAM and 64 GB ROM
Build Number: BND_M7_EEA_2022101408 (comment if you have a different build number)
Pretty standard Chinese Tablet with Unisoc proc.
The battery is theoretically 8000mAh, but at least mine, through calibration, has reported less than 5000 mAh. Still, I have to do some extra tests to see if it goes better.
Priced around $100, it's simply a nice cheap tablet, very insecure with an old patch.
Still, I know there are a few owners of this piece of s**t so I would like to join forces and see if we can set Magisk and TWRP at least (100% unlikely to get a new Android 12 or 13 ROM but who knows?
Development: Rooting, Recovery, ROMSI would like to create a comprehensive list of Rooting, recovery, possible ROMS, that may appear for this recent tablet in the future. The tablet is an Unisoc underdog so we might have to wait a bit until other users start to find some value in this budget powerful tablet, despite of the caveats we have already found.
Progress so far
Unlocking Bootloader
TWRP
Root - Magisk
Unlocking Unisoc Bootloader
Remember: there is a risk of bricking the tablet!
This will do a full wipe to your Tablet, so remember to back up your data before doing so
1. First, you need to configure ADB and enable Developer Options. This is mostly the same as any other Android device. Also enable in developer options OEM Unlocking and USB Debugging
2. Check if "adb" command is working and do a "adb reboot bootloader"
3. In bootloader, run "fastboot oem get_identifier_token" and take note of the number (beware because it can be in two lines). Something like:
(bootloader) Identifier token:
(bootloader) 30216010214012394021
(bootloader) 3261
OKAY
Click to expand...
Click to collapse
4. Now you need Linux. Do a USB Live with Ubuntu for example. Boot into your Linux system
5. Download this file.
6. You will need to extract it and do writable both fastboot and signidentifier_unlockbootloader.sh (chmod +x name_of_file)
7. Then run: signidentifier_unlockbootloader.sh Your_Identifier_Token rsa4096_vbmeta.pem signature.bin
8. Then run: fastboot flashing unlock_bootloader signature.bin
If you did things right, it will take from 2 to 5 minutes, erase your data and end with a message: "Unlock bootloader success". Otherwise, you did something wrong.
Rooting the table with MagiskThis is my main target currently. I hope I will find something soon.
TWRP processAt this moment we don't have a TWRP or any other recovery compatible with this hardware, stay tunned.
Official ROMs* Nothing found so far
Changelog2022/12/17 - First draft