Database Info

[Q] superpad III original firmware

Hi all,
I recently purchase a Flytouch3 from efox-shop with the following specification:
flytouch 3 X210 Jpad 10,2 " Zoll Tablet PC Infotm flytouch3 Android2.2 WIFI GPS und Kamera HDMI 512M 1 GHz 4GB Superpad
This is the actual site I procured it from is efox-shop and search for the above item.
It arrived in a box, stating superpad III on the side and only a frontal picture on the top.
However, when I installed Launcher Pro, and reverted it back afterwards to the INFOTM launcher, I remained with the black screen, only the taskbar was visible. I tried to update the firmware to that one of Tim, but it would not take any update directly from the SD card, I tried almost all versions around this forum.
The boot screen states INFOTMIC 0.6.1.5 (578), I'm able to flash it to this of to 0.6.1.2 (578). Before that I had: 0.6.1.5()
I can have it to communicate with my PC and burntool recognises it.
Now I'm looking to the correct files to flash back to the original format. The following details were in the original firmware:
model number: SAWEE10
Android version: 2.2 v2.1:#3925
Kernal version: 2.6.32.9 infotmic_infotmic-desktop #14
Build number: FRF85B
Is there somebody that can help me restoring my device???
Currently the device hangs at the INFOTMIC screen, and does not continue. Pressing bak+home+power brings me to the restore menu, but then it hangs at 1 second. Pressing within the 5 seonds back+home, it give a message that no recovery is found, try from SD.
With a bootable SD card I can have it start to update with a folder "android" on the SD card with the image files on it. However, the pad hangs during the "updating image linux-2.6.32.9" step. It can be there for very long time without any progress.
Anybody any ideas, suggestions, help.
Thanks already!!!

I encounter the same things :
"Currently the device hangs at the INFOTMIC screen, and does not continue. Pressing bak+home+power brings me to the restore menu, but then it hangs at 1 second. Pressing within the 5 seonds back+home, it give a message that no recovery is found, try from SD."
Nothing knows how to update this freakin f***ing superpad III ?
Mine is blocked cause i try to update with a micro sd bootable card, now it block on strat at "android" text and do nothing more...
Help plz !

I have this model too (SAWEE10) and I search every android forum on how to activate recovery process (something about zsys.img), no found.
Yes, this model can't boot from usual SDCARD, and thus we need bootable sdcard, googling around and we end up with creating a 704 MB sdcard and a folder name android.
I successfully boot from this bootable SDCARD, but I can't find a correct combination of uImage, ramdisk.img, and system.img (and optionally userdata.img). Flashing with SDCARD or burntool or IUW result the same, flashing system.img and userdata.img failed.
Currently my superpad III stops at ANDROID _, and I still find the correct *.img or a single *.ius file to burn.
Click to expand...
Click to collapse
I have found someone who have exactly the same problem, can someone help us plz ?

SuperPad III update failed restored to Firmware Update deb-r2.1.1623‎
hi
i have the same tablette model and same problems also, i try to update firmeware using sdcard bottable ........
now i restore it to flytouch 2 Firmware Update deb-r2.1.1623‎ and work fine i ll try to update it later to froyo ...
Good news , Chinese guys accept to send Firmware :
Firmware (ius files ) :
( Initial InfoTM screen shows this digit : infotmic 0.6.1.5 (672) ) h* .megaupload ?d=746FN3U0
( Initial InfoTM screen shows this digit : infotmic : 676 ) h**** .megaupload ?d=2WN6QW9Z

Run Froyo From SDCARD
issamux said:
hi
i have the same tablette model and same problems also, i try to update firmeware using sdcard bottable ........
now i restore it to flytouch 2 Firmware Update deb-r2.1.1623‎ and work fine i ll try to update it later to froyo ...
Click to expand...
Click to collapse
I've got the firmware in the form of update.zip, so it must be flashed using recovery mode, and this just don't work, as my previous post, it said something missing/invalid about zsys.img, so I've converted it to the *.img form using ubuntu mtd-utils (basically it needs gzip, cpio, mkimage and mkyaffs2image), but as usual, updating/flashing system.img and userdata.img resultin FAILED....
Finally after a full of a week researching here and there, I've manage to hack the ramdisk.img to produce the exact problem, and here they are:
- dump the dmesg and /proc/mtd, resulting the actual RAM that's 256MB (ads says it's 512, however, after successfully running on SDCARD --more on this later, the system reporting it's actually 512MB of RAM), and the processor is X210.
- no NAND found! (cat /proc/mtd), so that's why we can't write the system.img/userdata.img, where to write? I've managed to get the original dump of kernel (mtdblock1), and via dmesg I could finally see the NAND partition. So, the most important here is the ORIGINAL kernel to identify the NAND partition (still dunno if it's actually sdcard or it's nand flash). Check the output of /proc/mtd, resulting the correct information of mtd0 - mtd7, but again, manual flashing to the mtd3 (system), still a no go...
- hacking the init.rc, I've managed to run Froyo via SDCARD! Somewhere in this forum someone has done it also...., by this method, we can update the system partition with any firmware release (tim, sol, official, whatever), just extract the firmware-discovery, and then extract the system.tar(.gz) into the system partition on SDCARD.
- I've tried to manually (from working froyo on SDCARD) mounting /dev/block/mtdblock3 and extract/copy the system.img/system.tar.gz into it, and change the init.rc to mount it as /system, but still the tablet hang on ANDROID _ (or whatever screen animation logo), although when I checked via SDCARD, I actually see the partition is there with the complete structure of /system partition (no lost, and it actually written in the NAND system block).
- Tried different partition from NAND to handle the /cache, /data and /local and it's running, so confusing.... only the /system from NAND has the problem. So my last scheme is /system from mmcblk0p2 (SDCARD), and the others are from NAND (/data, /cache and /local). Maybe I need to flash_erase the NAND, but still didn't find a pre-compiled working file (flash_erase, flashcp, etc) to try. I've tried to cross compile the mtd-tools and copying to the sdcard, but when I run them, resulting segmentation fault(!), maybe need some libs or what...
- Although I can run froyo from SDCARD, I've got a random freeze/hang and had to (hard) reset, or an instant quit in the middle of running when I play some games or programs, maybe need to tweak some memory options, or it's something about SDCARD speed and quality. However, this is the best result I can get this time, at least it works, buddy

solmich said:
I've got the firmware in the form of update.zip, so it must be flashed using recovery mode, and this just don't work, as my previous post, it said something missing/invalid about zsys.img, so I've converted it to the *.img form using ubuntu mtd-utils (basically it needs gzip, cpio, mkimage and mkyaffs2image), but as usual, updating/flashing system.img and userdata.img resultin FAILED....
Click to expand...
Click to collapse
The sequence of my problem was. There was the original firmware on the device: Firmware Froyo 2.2 v2.1 # 3925 downloader 0.6.1.5 (). Connect 3G modem failed. Reading the forums decided to flash the deb-r2.1.1623_update_zip, but in the recovery menu, exit failed. Device to respond only to the home center, and home at the top and press power. Found information that the modem is connected and the firmware 3245. Flashed through the cable. Hanging on android_. That is until this point I have repeatedly easily rolled away for 3925. Then put all the firmware on the queue, even managed to get recovery menu substitution ramdisk.img. But the firmware deb-r2.1.1623_update_zip well established with an error. I immediately thought of one feature. When the tablet was still alive, when you install Navitel, tested on multiple devices, this would not work. As it turned out the system at boot mounted sdcard, sdcard1 and sdcard2. At the same time on sdcart not create folders NavitelContent. I copied it from sdcart1 (top slot) and Navitel run. After rebooting, sdcard folder NavitelContent reinstall. I think maybe because of this feature when writing firmware sdcard.img it is not completely installed, and because of that all the problems?

Superpad 3 firmware
I hope this will anyone having trouble with Superpad 3.
I have had to haggle with the shipper to send so I could get my Superpad up and going.
I have the sawee10 model that you all have been talking about. I have uploaded an attachment zip folder.
extract zip. on TF card create file folder called Android, place all files in it on your TF card. insert into superpad slot and turn it on. it should start loading files . hope it helps.

dont know how to load
I dont know how to upload them to ya'll one file is 67meg.
help me to get them to ya'll. I think it will work.

Anyone have the same thing but model tablet 10?
Id just use a file upload site search for one through google.
The person I bought mine from also gave me updated firmware it contains system.img zSYS.img and others but I've had no success.I can't seem to get it to load.Anyone know a link for the tab 10 model?If anyone needs the files I have or think they will have better luck I'll post the link.

try
http://www.slatedroid.com/forum/114-unlisted-infotm-x220-tablets/

[ROOT][TWRP][Unlock] Chuwi HI10 Pro by yener90

I tried lots of ways to root this tablet.
Finally succeed.
This package contains a modified kernel. It is required to let the tablet boot with modificated system drive.
After root, you shouldn't update your firmware. You could end in a bootloop.
Thanks @kostyamat. I used his way to root this tablet. But needed to edit most of the files, to get this done with our tablet
http://forum.xda-developers.com/android/general/root-chuwi-hibook-kostyamat-t3368642
DOWNLOAD
http://www43.zippyshare.com/v/lSaWBKVt/file.html
PREPERATION
Unzip the archive to PC, but try not to use special characters or folder names with space in the paths to files. Better way is unzip to a folder in the root of drive C: or D:
Turn on ADB-debugging: "Settings"-"About Tablet" >-> Taps under the item "build number" until the caption appears "you became a developer"-> Return one step back-> enter the item for developers "-> Enable" USB debugging ". A popup may appear on tablet. Set remember and press ok. Also enable OEM unlock.
Connect the device to the PC.
Install the Intel driver IntelAndroidDrvSetup1.10.0.exe
ROOT
1. Unlock_Bootloader.bat - Run first. It will unlock the bootloader. Carefully follow the description of the script and on the screen of the tablet. ATTENTION! All settings, programs, as well as all data on internal SDCard will be destroyed! Data on external MicroSD and Windows will not suffer. After unlocking the device will reboot in factory recovery, which does not display anything (stupidly black screen with backlight), the process may take up to 10 minutes, then the device will reboot into Android.
Tablet is now reseted, enable ADB Debugging and OEM-Unlocking again
2. Outside_boot-TWRP-recovery.bat - The device will be rebooted into the temporary session of TWRP-recovery, to Internal sdcard will be placed UPDATE-SuperSU.zip - install it using TWRP. Previously, you can make TWRP backup (recommended!)
3. Flash-TWRP-recovery.bat - (It is optional) TWRP-recovery will be permanently flashed into the Tablet. (Not recommended! Some time firmware will update, TWRP cannot install OTA-update)
4. Flash-ORIGINAL-recovery.bat - (It is optional) Flash back to the original Recovery.
ENABLE EXFAT & NTFS
SuperSU is required for this!
Download attachment, copy hi10pro-android-fs-1.0.4-install.zip to your tablet and flash it in recovery using TWRP.
WARNING!
Xposed doesn't work. Don't try it.

yener90 said:
I tried lots of ways to root this tablet.
Finally succeed.
This package contains a modified kernel. It is required to let the tablet boot with modificated system drive.
After root, you shouldn't update your firmware. You could end in a bootloop.
Thanks @kostyamat. I used his way to root this tablet. But needed to edit most of the files, to get this done with our tablet
http://forum.xda-developers.com/android/general/root-chuwi-hibook-kostyamat-t3368642
DOWNLOAD
http://www43.zippyshare.com/v/lSaWBKVt/file.html
PREPERATION
Unzip the archive to PC, but try not to use special characters or folder names with space in the paths to files. Better way is unzip to a folder in the root of drive C: or D:
Turn on ADB-debugging: "Settings"-"About Tablet" >-> Taps under the item "build number" until the caption appears "you became a developer"-> Return one step back-> enter the item for developers "-> Enable" USB debugging ". A popup may appear on tablet. Set remember and press ok. Also enable OEM unlock.
Connect the device to the PC.
Install the Intel driver IntelAndroidDrvSetup1.10.0.exe
ROOT
1. Unlock_Bootloader.bat - Run first. It will unlock the bootloader. Carefully follow the description of the script and on the screen of the tablet. ATTENTION! All settings, programs, as well as all data on internal SDCard will be destroyed! Data on external MicroSD and Windows will not suffer. After unlocking the device will reboot in factory recovery, which does not display anything (stupidly black screen with backlight), the process may take up to 10 minutes, then the device will reboot into Android.
Tablet is now reseted, enable ADB Debugging and OEM-Unlocking again
2. Outside_boot-TWRP-recovery.bat - The device will be rebooted into the temporary session of TWRP-recovery, to Internal sdcard will be placed UPDATE-SuperSU.zip - install it using TWRP. Previously, you can make TWRP backup (recommended!)
3. Flash-TWRP-recovery.bat - (It is optional) TWRP-recovery will be permanently flashed into the Tablet. (Not recommended! Some time firmware will update, TWRP cannot install OTA-update)
4. Flash-ORIGINAL-recovery.bat - (It is optional) Flash back to the original Recovery.
ENABLE EXFAT & NTFS
SuperSU is required for this!
Download attachment, copy hi10pro-android-fs-1.0.4-install.zip to your tablet and flash it in recovery using TWRP.
WARNING!
Xposed doesn't work. Don't try it.
Click to expand...
Click to collapse
Does this work for CHUWI HI10 not pro with dual os? and if it does can you make a video tutorial how to root the tablet?

hi10pro-android-fs-1.0.4-install.zip
I tried this and from now on the tablet Hibook 10 pro does NOT accept the external SD-card dany more
How to remove this "feature"?? any ideas welcome ...

WIFI, bluetooth and camera do not work
HI, Thanks for the tutorial
My problem is that, after follow your instructions, I have lost WIFI and BT connectivity. The camera icon and functionality has also dissapear.
How can I recover the initial sotware. I have downloade the image from the Chuwi Website but I do not know how to flash it.

Is there any thread for the Chuwi Hi10 Pro on XDA?

Head over here: http://www.modaco.com/forums/topic/...us-hi10-plus-hi10-pro-hibook-pro-hi12/?page=1

After I unlocked the bootloader, when reboot into android the touch does not work even if I reboot to recovery TWRP.. any ideas??

Use a PC and reflash the recovery again? It is for a Chuwi hi10 Pro right?

RichTJ99 said:
Use a PC and reflash the recovery again? It is for a Chuwi hi10 Pro right?
Click to expand...
Click to collapse
yes is a hi10 pro.. I already tried to reflash recovery and system, but the touch does not work.. it seems that the screen rotation is not right

I would ask over here:
http://www.modaco.com/forums/topic/...10-plus-hi10-plus-hi10-pro-hibook-pro/?page=3
You should be able to get a response/advice.

TWRP backup file
Hi!
Maybe someone could do on the running the tablet backup in TWRP. Android on my tablet died - would need to backup the whole android - system + bootloader.
I have a Chuwi Hi10 Model: CWI515 S / N: Q64G421161XXXXXX
Thank you very much !

przem0 said:
Hi!
Maybe someone could do on the running the tablet backup in TWRP. Android on my tablet died - would need to backup the whole android - system + bootloader.
I have a Chuwi Hi10 Model: CWI515 S / N: Q64G421161XXXXXX
Thank you very much !
Click to expand...
Click to collapse
you should find stock images at the chuwi.com website

Can't read SD card after flashing hi10pro-android-fs-1.0.4-install.zip
Hi there. Thanks for your information. I purchased a Hi10pro recently with the newer chipset. The bootloader was already UNLOCKED. I managed to load TWRP and rooted my tablet. I then flashed hi10pro-android-fs-1.0.4-install.zip and now it wont read the SD card.
If I put the card in another device I can see the data.
I ran a TWRP backup before I flashed hi10pro-android-fs-1.0.4-install.zip but it is on the SD card.
Any ideas on how to fix the problem?
Which partitions would need to be reflashed to be able to read SD card without losing my tablet data?
Looking forward to your response. Thanks

My chuwi hi10 pro doesn't get detected in adb or fastboot mode. I can't even connect it in MTP mode. Charging works fine but. Any help appreciated.

alby_92 said:
yes is a hi10 pro.. I already tried to reflash recovery and system, but the touch does not work.. it seems that the screen rotation is not right
Click to expand...
Click to collapse
Do you have mouse for PC? It works well with mouse. You don't use mouse Bluetooth because mouse bluethooth doesn't work.

https://www.youtube.com/watch?v=V33fbnoaPkE
Chuwi Hi10 PRO UNBOXING, REVIEW, BENCHMARK + GEARBEST COUPONS - YouTube

Hi there, I do not try to hijack this thread, but would someone please be so kind tohelp me find a bios dump from th PQ64 version of this tablet. My bios seemed to be fried by the previous owner. I Ihave the necessary tools to write to the chip over spi, but without the right bits/bytes the tools are useless.
Thx in advance
tron1

SAME
alby_92 said:
After I unlocked the bootloader, when reboot into android the touch does not work even if I reboot to recovery TWRP.. any ideas??
Click to expand...
Click to collapse
so i see that i wasnt the only one with this problem so only the android wont work with touch screen but its fine with a mouse, what i used to finish the set up seeing ass i couldnt touch the screen and i dont know how to fix this problem does anyone know how to fix it? if so reply
---------- Post added at 07:22 PM ---------- Previous post was at 06:56 PM ----------
THANKS SO MUCH YENER90 MY CHUWI HI10 IS ROOTED AND NOW I CANT CONNECT TO WIFI OR USE BLUETOOH NOT TO FORGET I CANT EVEN CLICK THE FREAKING SCREEN :good::good::good::silly::silly::silly::silly::silly:
---------- Post added at 07:32 PM ---------- Previous post was at 07:22 PM ----------
THANKS SO MUCH YENER90 MY CHUWI HI10 IS ROOTED AND NOW I CANT CONNECT TO WIFI OR USE BLUETOOH NOT TO FORGET I CANT EVEN CLICK THE FREAKING SCREEN :good: :good: :good: :silly: :silly: :silly: :silly: :silly:

I have a similar problem.
Horizontal and vertical appear to be reversed. Any Ideas?
I can't go back either. The problem still remains.

Hi guys, no idea?

Root tutorial for intel atom Cherry Trail dual os tablet

root tutorial using onda v820w ch v1 for example :
--root tools (root.zip) , unzip to c:\
https://drive.google.com/file/d/0BySA4DPrnBM-eXpsdlFzN21jQm8/view?usp=sharing
or
link：http://pan.baidu.com/s/1pLjJhHp
pwd：h79i
--use cmd and BOOTIMG.EXE to unpack boot.img
bootimg.exe --unpack-bootimg
-- use notepad++ open file \initrd\init*.rc , maybe called init.aosp.rc
--search string "class_start core" , add one line on this line's top
start sysinit
-- and then add these lines to bottom and save
service sysinit /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
disabled
oneshot
-- find another file called default.prop
modify ro.secure=1 to ro.secure=0
--use cmd and bootimg.exe to repack boot.img
bootimg.exe --repack-bootimg
rename boot-new.img to boot.img
after successfully boot into android , go to developer enable OEM Bootloader Lock and usb debug mode
download lastest supersu TWRP / FlashFire installable ZIP , copy to emmc flash or microsd card
http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
unzip root.zip to c:\
-- install driver follow this order and new driver overwrite old driver
iSocUSB-Driver-Setup-1.2.0.exe
IntelAndroidDrvSetup1.5.0.exe
PhoneFlashTool_5.3.2.0_win32.exe
connect otg usb line and hold "volume-" restart tablet or you can find reboot app to enter fastboot mode
cmd run
fastboot flash boot boot.img
fastboot oem unlock
fastboot reboot
hold "volume-" and enter fastboot mode again
-- if twrp file is not working on your tablet , you can find others twrp version , you need try more by yourself
v820w ch twrp file : I use v919 ch twrp on xda forum , rename to twrp.img
--cmd run to enter twrp recovery mode , if tablet don't automatically to restart to enter recovery , you can use volume key to select recovery mode and power key to ensure
fastboot boot twrp.img
connect mouse because touch fuction maybe not work , twrp install supersu recovery zip , root finish
you can use app like foldermount now
if play store has new version supersu , you can update app
but you can't install "binary" from app , it will damage system , if you do , you will find microsd size always 1GB max
so , how to install supersu "binary" , you only need use above step about flash twrp and install lastest recovery zip , after install lastest supersu zip file , on table you run supersu , it will not show any update "binary" request .
p.s. Onda Table Full Gapps Firmware
http://forum.xda-developers.com/android/development/onda-table-gapps-firmware-root-tutorial-t3462774
dual os tablet can use 64gb/128gb microsd card , you need use GUIformat to format to FAT32
dual os all can read/write it
if you have highspeed microsd compatible issue
I suggest you can buy speed < 50 mbps/s sandisk microsd
it work fine on onda tablet
on windows , you can use micorsoft official download win10 version to install
for example onda tablet , you need to do two things
1. backup driverstroe \ FileRepository , after reinstall new win10 , you can use device manager to find lose drivers .
2. backup \system32\drivers\sileadtouch.fw , you need to copy this touch location driver to new win10 .
win10 touch gamepad
china version is free , you don't need to pay to buy 8-axis , function is useless :
https://www.microsoft.com/zh-tw/store/p/微派平板助手/9nblgggzlx51
guide translation here , look attachments pictures : http://forum.xda-developers.com/windows-8-rt/general/tutorial-onsceen-gamepad-touchpad-t3104501
english version is free to try :
https://www.microsoft.com/zh-tw/store/p/touch-anyway/9nblggh31d54

Thank you so much for this detailed guide!
I am having some troubles at the line "fastboot flash boot boot.img": I get "FAILED (remote: Flash failure: Not Found)" on the computer, and "Failed to get partition [the_name]: Not Found" on the tablet screen.
Does anyone know something about this error?
Thanks!

Thanks you for the post! Any idea if I can use this same process to root RemixOS 2.0 on an Onda Obook 11 Plus? I downloaded the RemixOS .zip for the Obook 11 Plus from the Onda site and it seems like the contents are very similar to the process that you describe here...
Or - do you know if I can somehow "convert" the RemixOS partition to run stock Android 5.1? I know that they sell this same device with stock Android as well, but I didn't see an Android .zip file on the Onda site for this device - just the RemixOS .zip file...
Thank you!
Sent from my OBOOK 11 PLUS DUALOS using Tapatalk

Well, not so worried about root now. i already broke my new toy... Was messing with the BIOS brightness level settings (get get lower brightness in RemixOS) and accidentally set GOP Driver to "Disabled" in the BIOS - not I can't get ANY output on the screen or via the HDMI out.. Tried *everything* to try and reset it "blindly", but no luck.. If anyone has any ideas (like how to flash a new BIOS or reset it to defaults), please chime in! Frustrated...
Onda Obook 11 Plus.
Thanks.
Sent from my HP SlateBook 10 x2 PC using Tapatalk

Dificulty
Man, i'm having too much problems to understand exactly what i have to do. I have panic to do something wrong. If you can add some screenshots to post will save my life and my dumbness hahahahah
Thanks a lot

hey i no a way to fix this problem it will cost a little about £10 maybe you need to buy a ch341a flash tool off ebay and the 8 pin clip you will need a computer to plug it into and also your bios .bin file.open up your tablet find the bios chip put the clip on run software load your bios.bin and write it to the chip with software all done good luck

[email protected] said:
hey i no a way to fix this problem it will cost a little about £10 maybe you need to buy a ch341a flash tool off ebay and the 8 pin clip you will need a computer to plug it into and also your bios .bin file.open up your tablet find the bios chip put the clip on run software load your bios.bin and write it to the chip with software all done good luck
Click to expand...
Click to collapse
Thanks - Yeah, I'm aware of that method to re-flash the BIOS, but I have 2 issues with that:
1. Trying to get the damn tablet apart without breaking anything (there isn't a single screw involved here). Considering the cheap materials used on these tablets to begin with, I'd be lucky to get it apart without breaking anything - and honestly, don't really feel like fighting it.
2. More importantly, the BIOS for this device is not available anywhere. The manufacturer has never released it. So if even if I did manage to get the device apart without breaking it, I'd have no BIOS file to flash anyway.
For what I paid for it, I'll write it off as a learning experience and move on. Truth is that I've found a much better device anyway (Chuwi HI10 Pro/Plus). The Onda was OK, but the Chuwi's are MUCH better devices.
But again, thanks for the info - I do appreciate it.
Sent from my Vi10 Plus using Tapatalk

i rooted my onda v80 plus successfully, but now there is no way to access windows again. can anybody tell me how i access windows?
There is no "OS Change" In the android system, the tablet recognices no volume + at the starting process, so i have no chance...

kudi120 said:
i rooted my onda v80 plus successfully, but now there is no way to access windows again. can anybody tell me how i access windows?
There is no "OS Change" In the android system, the tablet recognices no volume + at the starting process, so i have no chance...
Click to expand...
Click to collapse
You can try going in to your bios and check boot mode to see if it says android or windows

I don't know where to start.
I have Cube iwork 8 air. Trying to root but where can i find bootimg which i have to unpack.
Unpacked twrp.img and found init.rc but cannot find line with class_start core, all i have is class_start default#. Is it place where i have to add start sysinit? Where exactly?
Can someone add those lines to file and ad here?
Please explain this as for total noob. Cause for me it looks too complicated like i should do something before which is not include in this tutorial.
Tried iroot, kingroot and this https://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096 method as well, no luck so far.
Thank You in advance.

You can boot Linux or Windows and make a dump of boot partition.

Repacking boot.img error
wgarnett said:
root tutorial using onda v820w ch v1 for example :
]
Click to expand...
Click to collapse
Hi,
I have the onda obook 10 boot.img. Unpacking goes on well including adding the lines instructed using the notepad ++. Repacking however produces the error "set_cmdline <>takes exactly 1 argument <6 given>".
What could I be doing wrong?

First - there is no need to quote the OP fully.
Please upload or attach the 2 original and your 2 changed files (and original boot.img), I will take a look.

Troubles repacking the onda obook 10 boot.img
wgarnett said:
root tutorial using onda v820w ch v1 for example :
]
Click to expand...
Click to collapse
Hi there,
Tried the above rooting method but have a problem repacking the boot image. I get the error "cmdline too many arguments (6 given)". I unpacked stock android boot.img tweaked it and flashed but the tab never booted.
Kindly help

Ivansu said:
Hi there,
Tried the above rooting method but have a problem repacking the boot image. I get the error "cmdline too many arguments (6 given)". I unpacked stock android boot.img tweaked it and flashed but the tab never booted.
Kindly help
Click to expand...
Click to collapse
I already answered you just above your post.
And again, please don't quote the WHOLE message, it is unneeded.

The excessive note on quoting is appreciated. I will take a look on the newbies guide. Attached are the original and modified files. The boot.img size is more than the limit allowed.
Here is the link on Google drive.
https://drive.google.com/file/d/0B7mm7XsgjszUZEY3VEM4ZEVObGc/view?usp=sharing
Thanks

Ivansu said:
The excessive note on quoting is appreciated. I will take a look on the newbies guide. Attached are the original and modified files.
Click to expand...
Click to collapse
modified_files.rar contains no files.

My bad for that. I have it right now

Your changes to default.prop are OK. To init.aosp.rc not:
class_start core
+
+ start sysinit
+ service sysinit /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
+ disabled
+ oneshot
While I did it like this:
+ start sysinit
class_start core
+ service sysinit /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
+ disabled
+ oneshot
+ means added lines.
Does it work if you move "start sysinit" before "class_start core"?

Thank you for pointing that error. I modified but still have the same repack error. See the attachment

TWRP modded to work now with Unihertz Atom

Below you will find a download for my modification of a ported Team Hovatek TWRP file as their TWRP did not support OTG. Thanks to Team Hovatek for making a nice porting tool. Unfortunately it took some days and late nights of work to get the ported TWRP to actually be useful as this phone needs OTG support to use TWRP.
When I recently got the Unihertz Atom I didn't realize that it had no micro SD card slot for an external SD card like the Unihertz Jelly Pro had. However it does have OTG support unlike the Jelly Pro but I could not find any TWRP versions for the Atom. So I found a TWRP porting tool from Hovatek and I was able to create a TWRP version but USELESS unfortunately as that version of TWRP did not have OTG support for the Atom.
To make matters worse that TWRP can't deal with the encrypted internal storage of the Atom so there was no way to do a backup of your system. It was possible to format data in TWRP and do a backup to it but upon reboot all that data was gone and reset by the Atom as an essentially new phone being setup for the first time.
I needed a way to modify the ported TWRP so it would recognize an OTG flash drive or USB flash with an OTG cable. I used Image Kitchen to disassemble the original Atom Recovery image and also the modded TWRP recovery image so I could find what was missing from TWRP that was there in the original setup. After a whole lot of reassembling and reflashing various attempts to fix the OTG problem I finally got it. Had to add different lines of code to 3 different files within the unpacked TWRP recovery for it to finally recognize an OTG attached flash drive.
A couple notes on using your external flash drive with TWRP. First you want to insert the flash drive with an appropriate USB type C OTG adapter or cable. Or I see Sandisk (and possibly other brands) are now making a flash drive with USB and Type C dual setup for OTG use.
Bootup your regular phones Android system and look in the pull down notifications - it will ask if you want to use the flash drive as storage. Answer yes and it will then Format it to FAT32 0x0C type which is different than what it was fresh out of the package as most will be FAT32 0x0B type. Once formatted the way the Atom wants it you can use it. However if you put the drive back in your Windows computer it may not see the drive at all. The solution is to open Windows Disk Management and Assign it a drive letter. Once that is done you can read and write to it from both Android and Windows or Linux.
Once that is done you can turn off your phone (IMPORTANT). Do not use any apps that reboot into recovery after installing this TWRP or you will likely just get a black screen and it won't boot up until you reflash the preloader, boot and recovery.
To get into recovery hold down the Volume UP button and the Power button at the same time until you see Unihertz then release both. This is of course after you have flashed TWRP. More on that below. Once your are in TWRP you may have to remove your Flash drive if you had it plugged in during recovery boot up - then reinsert it for TWRP to see it. You can then see it when you mount storage or select storage and it should show the size of your flash drive.
You can then backup your Boot, Recovery, EMMC, System and cache. However the data on the Atom seems to be encrypted in a way that this TWRP does not see it so it will be best to use something like Titanium backup for your Apps and their data. The TWRP though will ensure a complete backup of your system and it's settings as well as the other items mentioned above. I am still looking into why it can't see the encrypted data part of the phone but for now it's nice to have an image of all the rest of the phone. If anyone can help with that I would appreciate it. So far I've tried several 'no encrypt scripts' and ones to turn off DM verity I found on XDA but none of them worked on this phone.
Here is the download of my modded TWRP and also a link for the SHA-256 of it:
TWRP mod: TWRP mod by droidzer1
SHA-256 for file above: SHA-256 for TWRP mod Love the Atom - fast Octacore 4GB Ram - 64GB Internal storage, rugged and tiny as an underfed mouse. :silly: Enjoy !

Notes on Installing this TWRP on your Atom
There are two ways I have used to install this TWRP onto the Atom. One way (and the best way IMO) is to use the SP Flash tool version 5.1828. The other is to use Fastboot. I believe for both methods you need to enable developer options on your phone and turn on OEM unlocking. But if you use Fastboot you also have run the line: "fastboot oem unlock" to install TWRP and that will wipe your phone to a new reset condition plus you will see the 5 second "Orange State" pause screen every time you turn on the phone. To eliminate the "Orange State you can run : "fastboot oem lock" but that will once again totally reset your phone wiping everything including apps and settings. So I prefer using SP Flash tool to avoid all that.
When installing with SP Flash tool I always flash the preloader, boot and recovery (the TWRP modded one) and of course the scatter file. It seems if you don't flash all of those it sometimes doesn't want to boot up.
Also this mod is for the official Unihertz 11-30-2018 ROM version which is the latest update I've seen as of a week ago. I don't know if it will work for other versions. You will want to download that ROM to get the scatter file that is needed by SP Flash tool and it's always good to have an original ROM just in case. Link for the new 11-30-2018 Atom ROM here: 11-30-2018 Atom ROM If you are not on that version you could backup your apps and data with Titanium backup and then install the new ROM while flashing my modded TWRP all at the same time. Just make sure the TWRP you download is named "recovery-verified.img" when you replace the stock one in the SP Flash tool list on the Download page. Also make sure on the tools 'Connections' setting that you check 'Battery installed'.
IMPORTANT!!! - Every version of SP Flash tool I've used shows up as having a virus or trojan and although it may probably be a False positive to be safe I always run Shadow Defender before starting the SP Flash tool. There may be other similar programs but I found this to be one of the best as it totally freezes your computer and hard drive(s) so nothing can be changed or written permanently to them while in Shadow mode. Once you reboot everything is back to a normal state and any changes that may have been made are gone. SP Flash tool available here: SP Flash tool v5.1828 I strongly suggest you use this latest version as previous ones had some issues in completing this project.
A couple quick notes on using the SP Flash tool: It is best to start the tool, have all your items in the check boxes loaded (select scatter file location first) check and locate preloader, boot and recovery - the preloader and boot are from the original ROM you downloaded from the above link. Unzip it and you'll see the needed files inside along with the scatter file.
Once that is ready turn OFF your phone and hook it up with the original USB-C cable to your computer. Wait for it to show the battery charging screen and wait till all that disappears and you have nothing but the black screen. (Or per user SepticFuddy you can hold the Volume Up key while inserting the USB cable and it will connect quickly - I have not tested it this way). Then click on the Flash tool download button. After that you need to push the Atom Power button once briefly - not long enough to turn it on - just a brief click. After that you should see the Flash process going on - it only takes a few seconds to load the preloader, boot and recovery and then you will see a "done" with a big check mark. Remove your phone then and boot into your regular Android OS or use Volume Up and the Power key to boot into your TWRP. :highfive:

Why TWRP doesn't work with Encryption - from TeamWin
I guess this may explain why it is unlikely to get TWRP to work with the encrypted data partition - straight from Teamwin's TWRP website:
"Why doesn't TWRP support encryption on my device?
TWRP encryption is supported in 2 phases. The first item is keeping up with the newest support from AOSP, which can require lot of changes and integration with the new AOSP release. This can take time especially if we have to wait for reference devices to test with. The second item is custom blob support and integration with device OEM firmware.
Even if your device supports AOSP encryption and decryption, it usually requires custom blob support. The process of figuring this out may take time and may never be done. Some vendors such as Samsung use their own encryption techniques. Without heavy deconstruction/decompiling of custom library blobs, and successful ports by an active maintainer, this may never be done. Encryption support is a nice thing to have in TWRP, and not a must have support option. We feel that the ability to backup system and install custom firmware can outweigh having no TWRP support at all."
From: TWRP Website FAQ on Encryption

How I fixed TWRP
For anyone who wants to try the mods their self if you don't trust using the recovery I uploaded I believe these are the changes I made to the ported TWRP. You need of course the porting tool from Hovatek and after you have ported your original recovery you will want to use Image Kitchen to make these mods to the ported image:
Use Image Kitchen to unpack the ported TWRP recovery. In the Ramdisk folder this line "ro.agui.otg_usbdisk=yes" orginally found in the prop.default of the original recovery needs to be put into the file "default.prop" which is a different file name than the original but I am sure is the same purpose and was referenced in the original by a small file with that name.
Then this line "/dev/mt_otg_test(/.*)? ubject_r:mt_otg_test_device0" from the original recovery image in the file "nonplat_file_contexts" I believe I copied into the file "file_contexts" in the TWRP image in the Ramdisk folder.
Note - the above code line that has a smiley in it is because there is the letter "o" followed by a colon. Replace the smiley with "o" and : no spaces between it and the letter 'u' before it or between 'o' and :
I think the third file I modified was found in the unpacked folder /ramdisk/etc in the file 'recovery.fstab' and I took this line "/devices/platform/mt_usb* auto vfat defaults voldmanaged=usbotg:auto " from it to add to the same file in the ported TWRP. Then just repack everything in Image Kitchen and you should have a TWRP recovery that works with OTG.
If you aren't familiar with how to use Image Kitchen it would be best to google how to use it. I have left out some of the basics such as needing to Copy the “recovery.img-kernel” and “recovery.img-kernel_offset” from the unpacked stock recovery and overwrite those two files in ported TWRP folder. Best to look for an instruction article on techora.net about porting TWRP on mediatek devices.

Thank you, it's awesome! But how did you manage to flash Magisk? I can't flash it as /data and /storage can't be mounted.

You should be able to flash it with Fastboot by using command:
fastboot flash boot /path/to/patched_boot.img OR simply put it in the fastboot folder and type:
fastboot flash boot boot.img (the patched boot image)
You may want to review info on the Magisk thread here:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
This method of course is done with you computer and USB cable attached to the Atom. Make sure you have correct drivers for it to fully recognize your phone.
A bit more info from topjohnwu's Magisk thread mentioned above:
Via Magisk Manager:
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot/download mode or ODIN
Install the latest Magisk Manager
If you're planning to flash the patched boot image through ODIN, go to Settings > Update Settings > Patched Boot Output Format, and select .img.tar. For normal users leave it as the default .img
Press Install > Install > Patch Boot Image File, and select your stock boot image file
Magisk Manager will now patch your boot image, and store it in [Internal Storage]/Download/patched_boot.img[.tar]
Copy the patched boot image to your PC. If you can't find it via MTP, you can pull the file with ADB:
adb pull /sdcard/Download/patched_boot.img[.tar]
Flash the patched boot image to your device and reboot. Here is the command if using fastboot:
fastboot flash boot /path/to/patched_boot.img

If the above method fails for some reason you should also be able to flash to patched boot image with SP flash tools as long as you have the scatter file for the ROM you have installed on your phone. As I mentioned if you flash the patched boot image that way I found it best to also flash the preloader and recovery at the same time.

Cannot mount /data
What you did here was remarkable. I love the Atom so I never tried to tinker with recovery since I might end up with a bootloop. I hope we find a solution soon on how to mount /data.

post-root network failure
First off thank you for doing the research and posting in the thread to help us root this awesome little device.
I followed your steps to the "T" and I was able to successfully patch magisk and re-download it back onto my atom and it was rooted BUT, there seems to be some sort of network issue that I'm stuck on, I'm unable to turn on the wi-fi and bluetooth and every few seconds I keep getting an error message that says "bluetooth keeps stopping" consistently whenever I have the phone on.
I was wondering If you had any idea on what might be causing this, or if you had this problem.
thank you, and I look forward to hearing back from you

droidzer1, Finally got to post now and wanted to thank you for your work on the Atom. I got it rooted and got TWRP working too with only some frustrations because I got in a hurry and missed a detail the first try. I haven't found any problems and have had it running about 2 weeks now with root and TWRP. Nice to have root and of course great to be able to do a whole system backup now!
---------- Post added at 03:08 AM ---------- Previous post was at 03:02 AM ----------
hayestak said:
First off thank you for doing the research and posting in the thread to help us root this awesome little device.
I followed your steps to the "T" and I was able to successfully patch magisk and re-download it back onto my atom and it was rooted BUT, there seems to be some sort of network issue that I'm stuck on, I'm unable to turn on the wi-fi and bluetooth and every few seconds I keep getting an error message that says "bluetooth keeps stopping" consistently whenever I have the phone on.
I was wondering If you had any idea on what might be causing this, or if you had this problem.
thank you, and I look forward to hearing back from you
Click to expand...
Click to collapse
Were you able to get this fixed? Doesn't look like droizer1 has been on here recently. Mine didn't have either of those issues. Have you tried doing a factory reset and doing the whole process over? I think sometimes just a computer PC might glitch something on your phone so doing it over might skip the hiccup.
---------- Post added at 03:48 AM ---------- Previous post was at 03:08 AM ----------
Since droidzer1 first posted this in early January you might try using the version of Magisk that was available at that time as I think by later March when you posted there was a newer version out and I've found some versions of Magisk to not work a hundred percent and had to use an older version on some phones.

The latest Magisk (19100) + Xposed (v90 beta 3) work fine for me using the TWRP posted above, in case people were wondering about it.
R

Lost in reboot ...
Hi
I urgently need some help. I seem to be lost...
I have successfully installed TWRP on my Unihertz atom. And I can manage to go into either TWRP mode or into fastboot mode.
I can also successfully unlock the Unihertz atom with:
fastboot oem unlock-go
But what is next?
If I reboot, my phone constantly reboots. It cycles into reboot without Android coming up.
(perhaps I made something wrong).
What I actually want is: The phone should boot including Magisk.
Can anyone please help me what commands I have to issue (with the phone connected to my linux computer via USB) in order
to recover to a normal reboot? Which image-file should I use (please provide URL)?
Can anyone please help me what commands I have to issue to flash Magisk?
Which image-files I should use (please provide URL)?
If somebody has a custom rom or lineageOS rom I would be even happier ...
Thanks a lot.

Thank you

Confirmed working with the Android 9 Pie 2019082617 ROM, latest Magisk 19.3 (19300), latest Riru core v19.5, latest Riru- EdXposed v0.4.5.1b (4463) (SandHook). EdXposed seems hit or miss after a reboot though, getting it to stick may take a few installations.
To get SP Flashtool to work, I had to hold the Volume Up key while inserting the USB cable and it would instantly connect, rather than following the OP's instructions of just inserting the cable and waiting for a black screen.
I'd love to see a custom ROM like LineageOS or something, but this is will have to do for now.

SepticFuddy said:
Confirmed working with the Android 9 Pie 2019082617 ROM, latest Magisk 19.3 (19300), latest Riru core v19.5, latest Riru- EdXposed v0.4.5.1b (4463) (SandHook). EdXposed seems hit or miss after a reboot though, getting it to stick may take a few installations.
To get SP Flashtool to work, I had to hold the Volume Up key while inserting the USB cable and it would instantly connect, rather than following the OP's instructions of just inserting the cable and waiting for a black screen.
I'd love to see a custom ROM like LineageOS or something, but this is will have to do for now.
Click to expand...
Click to collapse
Thanks for the mention of a quicker method. I've updated my post to include your info.

LineageOS for Uniherz Atom?
SepticFuddy said:
I'd love to see a custom ROM like LineageOS or something, but this is will have to do for now.
Click to expand...
Click to collapse
Me too!! LineageOS for the Unihertz Atom would be great!
The hadrware of the Uniherz Atom is just great, is is small and it is dual-sim. This is unique in the market.
I would be even willing to contribute with 100,- EUR if somebody delivers a working LineageOS ROM.
Any body interested? :highfive:

SepticFuddy said:
I'd love to see a custom ROM like LineageOS or something, but this is will have to do for now.
Click to expand...
Click to collapse
The main problem is that unihertz never released their source code (despite being obliged to do so according to the android licensing contract).
There are some bits in the official mediatek kernel source tree (https://android.googlesource.com/kernel/mediatek/) but I doubt that this would be enough to build something stable out of it.

@droidzer1 Hey there, what is the difference between your modded TWRP and this test release by the TWRP Builder Project asside from the TWRP version?

J-Kos said:
@droidzer1 Hey there, what is the difference between your modded TWRP and this test release by the TWRP Builder Project asside from the TWRP version?
Click to expand...
Click to collapse
I'm not sure what the difference is except I came out with mine in January and theirs came out in March. Theirs is about 4 Megabytes bigger - maybe a newer version (mine is 3.2.1-0). I contacted 'bigbiff' at TWRP about mine when I had it working but they were not interested unless I had a device tree which I didn't so they didn't want to post it on their site.

Great, thanks for your reply. I am satisfied with you version, so I will just keep using it.

upgrade method to another android version for Rockchip unit (px6 px5 Px30 and other )

following the official Rockchip upgrade tool https://forum.xda-developers.com/an...ment/mtcd-e-android-10-upgrade-using-t4123933
if you are upgrading from the same version ex android 9 to android 9 you don't need this
if you are upgrading from android 9 to android 10 or later version you will need this
tools link
https://github.com/rockchip-linux/tools
here is the simplified method ( for 1&2 you need update.img for 3 you need UPDATE.ZIP )
first method __________________________________________________________________________________________________________________________________________________________________
using usb A to A ( https://www.amazon.com/Monoprice-Male-24AWG-Cable-Plated/dp/B002KKXP3M/ref=sr_1_2?dchild=1&keywords=usb%2Batoa&qid=1594497313&sr=8-2&th=1 )
and laptop
download RockChip Batch Tool
connect the pc to the unit using the usb
in fw path chose the IMG file
the click upgrade
wait until you process is done will see the new version booting up
don't unplug until the app tel you to do so
second method _______________________________________________________________________________________________________________________________________________________________________________________
using the Real GPS SD port
download SDDiskTool
plug the SD to PC
select the SD from drop menu
Only upgrade option is checked
then select the IMG file
click create
when it is done
go to your unit
the put in to recovery
then plug the sd into the REAL GPS port
then from recovery select restart system
the upgrade process will start
then it will ask you to remove the sd
then it will boot up
third method ______________________________________________________________________________________________________________________________________________________________________________________
using the app modinstaller 2 on your unit ( http://hal9k.ru/?page_id=207)
click on the version you want
then NEW recovery will boot
put a OTA update.zip on sd or usb drive
select upgrade
then the upgrade will start don't remove the USB until update is done

and for anyone that his unit only have 1 SD card reader only ( media sd )
actually the second one is hiding inside (GPS SD)
if you want to try
i have moded my unit to be able to access the GPS port
you need to remove the one side the cut a hole to access the SD card
from top cover
https://i.imgur.com/fzusSZ5.jpg
close up to the SD card ( it comes empty)
https://i.imgur.com/uGgUdxn.jpg
after i remove the side case
https://i.imgur.com/gGxj61y.jpg
the side case after cutting ( i am very bad i know )
https://i.imgur.com/0qTW7Mw.jpg
after installing the side back and you can see the SD card
https://i.imgur.com/yQqeVIJ.jpg
this is after the android 10 install
https://i.imgur.com/yQqeVIJ.jpg

The Latest version in here https://yadi.sk/d/umCvHqCDzHccr
in the name if it is IMG for method 1& 2 as you need img
if the name is OTA is for method 3
after you upgrade you can upgrade to the latest ota like normal just put it on the usb
just so you know
HA3_HCT_CHS2 and other
are built for the same unit the only different is the launcher included in it
use the one you like

Thank you for this.
I have hal9k rooted ROM, Android 9, Dasaita max6.
If I do procedure method 1 (easy way) will it works without problem?
I know I will loose hal9k ROM, just I want be sure that HU will be like original but with Android 10.

Thank you for the explanation.
How to create a. Img from the ota update.zip?
Envoyé de mon Mi 9T en utilisant Tapatalk

spinose said:
Thank you for the explanation.
How to create a. Img from the ota update.zip?
Envoyé de mon foofoo en utilisant mrbungle
Click to expand...
Click to collapse
You dont. In theory, not impossible, just difficult unless OTA contains full files including bootloader and recovery - which they never do.
Instead, install appropriate full .IMG then OTA from recovery.
If next question is where do I find .IMG files, a search through the mtcd section is the best place to start

marchnz said:
You dont. In theory, not impossible, just difficult unless OTA contains full files including bootloader and recovery - which they never do.
Instead, install appropriate full .IMG then OTA from recovery.
If next question is where do I find .IMG files, a search through the mtcd section is the best place to start
Click to expand...
Click to collapse
Hi just to have the complete picture as this is were i get doubts , so to upgrade to a higher version of android you require a "third file " , if using SD card method ?
As for a normal upgrade you have
- DMCU file to upgrade MCU (DMCU.IMG)
- OTA file to upgrade manufacturer firmware ( update)
if i understand you correctly for android upgrade to a higher version you would require the OTA file(update) to be an image file(.img) as well ?
Or are the required files just the two you would normally use only you have to apply them dfferently as described above ?

spinose said:
Thank you for the explanation.
How to create a. Img from the ota update.zip?
Envoyé de mon Mi 9T en utilisant Tapatalk
Click to expand...
Click to collapse
don't create anything if you need IMG donwnload an img if you need a update zip download that
you can find them all in my 3rd post
if you want to use method 1 or 2 you need IMG like this
hct7_rk3399_10.0_IMG(20200415).zip
if you want to use method 3 you need ota like this
hct7_rk3399_10.0_ota(20200415).zip

Tempest67 said:
Hi just to have the complete picture as this is were i get doubts , so to upgrade to a higher version of android you require a "third file " , if using SD card method ?
As for a normal upgrade you have
- DMCU file to upgrade MCU (DMCU.IMG)
- OTA file to upgrade manufacturer firmware ( update)
if i understand you correctly for android upgrade to a higher version you would require the OTA file(update) to be an image file(.img) as well ?
Or are the required files just the two you would normally use only you have to apply them dfferently as described above ?
Click to expand...
Click to collapse
if you want to use method 1 or 2 you need IMG like this
hct7_rk3399_10.0_IMG(20200415).zip
if you want to use method 3 you need ota like this
hct7_rk3399_10.0_ota(20200415).zip

This video in GERMAN ( you can put subtitle in English )from Alex's Android Radio explain the method 3
https://www.youtube.com/watch?v=UIJFJYh2y4A

And here's the English video ?

How to update from 8.1 to 10 ?
I tried an update from 8 to 9 before using stock img but got aborted. Something to do with incompatibility with Hals rom.

Ati_gangster said:
And here's the English video
Click to expand...
Click to collapse
Thanks for showing the link but what a Waste of time. Instructions ineligible and video so fast, it was hard to know what was going on.
The only bit that is understandable was the section on how to pay.
Nothing on the merits of upgrading or function.
Just a big useless advert.

cleverdicky said:
Thanks for showing the link but what a Waste of time. Instructions ineligible and video so fast, it was hard to know what was going on.
The only bit that is understandable was the section on how to pay.
Nothing on the merits of upgrading or function.
Just a big useless advert.
Click to expand...
Click to collapse
You can adjust the playback speed to 0.75 or maybe better to 0.5.

abogrhen said:
don't create anything if you need IMG donwnload an img if you need a update zip download that
you can find them all in my 3rd post
if you want to use method 1 or 2 you need IMG like this
hct7_rk3399_10.0_IMG(20200415).zip
if you want to use method 3 you need ota like this
hct7_rk3399_10.0_ota(20200415).zip
Click to expand...
Click to collapse
where to find image for dasaita px6?

m1john said:
where to find image for dasaita px6?
Click to expand...
Click to collapse
The first thing if you want to update to 10 with this mode, you have to install the .img that is here. After you have android 10 you can install dasaita's if you want.
Enviado desde mi ONEPLUS A5010 mediante Tapatalk

It seems that I cannot upgrade to Android 10. My unit is Dasaita PX6 and whichever method I choose it always boots into...black screen.
1. USB A to A - does not recognise the unit in Windows, I have tried invoking booting into bootloader with command reboot bootloader....black screen
2. SDCard - boot into recovery, insert card, reboot ... black screen
3. Purchased MODInstallerPro, copied ZIP onto SD card, install the apk, reboots and black screen again

mariof said:
It seems that I cannot upgrade to Android 10. My unit is Dasaita PX6 and whichever method I choose it always boots into...black screen.
1. USB A to A - does not recognise the unit in Windows, I have tried invoking booting into bootloader with command reboot bootloader....black screen
2. SDCard - boot into recovery, insert card, reboot ... black screen
3. Purchased MODInstallerPro, copied ZIP onto SD card, install the apk, reboots and black screen again
Click to expand...
Click to collapse
I have a Dasaita PX6 unit and what did not work for me, was the bootable SD card method. The mod installer worked, the connection to the PC through the single USB cable worked, but make sure you have the drivers installed so that the pc recognizes the radio unit, when you use the USB cable method use the reset button to go into recovery mode and the PC will sound that something was connected, from there try to install the correct drivers. Show us the exact head unit that you have, mine doesn't have any buttons on the front, and sometimes there was a black screen because I needed to touch the power button and the screen would turn on showing the boot logo.

Al Ferro said:
I have a Dasaita PX6 unit and what did not work for me, was the bootable SD card method. The mod installer worked, the connection to the PC through the single USB cable worked, but make sure you have the drivers installed so that the pc recognizes the radio unit, when you use the USB cable method use the reset button to go into recovery mode and the PC will sound that something was connected, from there try to install the correct drivers. Show us the exact head unit that you have, mine doesn't have any buttons on the front, and sometimes there was a black screen because I needed to touch the power button and the screen would turn on showing the boot logo.
Click to expand...
Click to collapse
This is the Unit I have
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ok, The Mod Installer finally worked for me. I mean it installed Android 10 but I did not see any progress at all. I have left the unit with blank screen for several minutes, then rebooted and the Android 10 logo showed up.
The USB method still does not work at all. I have tried different combinations
Tried all 3 USB ports
Booted into recovery with cable inserted - black screen, no Windows drivers beep sound
Boot into bootloader - black screen, no Windows drivers beep sound
Device off, cable inserted, powered on - black screen, no Windows sound.
Windows device manager did not recognise any unknown devices in all the above methods.

mariof said:
This is the Unit I have
Ok, The Mod Installer finally worked for me. I mean it installed Android 10 but I did not see any progress at all. I have left the unit with blank screen for several minutes, then rebooted and the Android 10 logo showed up.
The USB method still does not work at all. I have tried different combinations
Tried all 3 USB ports
Booted into recovery with cable inserted - black screen, no Windows drivers beep sound
Boot into bootloader - black screen, no Windows drivers beep sound
Device off, cable inserted, powered on - black screen, no Windows sound.
Windows device manager did not recognise any unknown devices in all the above methods.
Click to expand...
Click to collapse
when you have the device turned off, USB cable connected to pc, turn on the device and right away use the reset button to go into recovery, the drivers in your pc should be already installed before you do any of these steps, and have the android tool installed as well. Open the android app tool on your pc, open device manager if you want too, and scan for new devices, the head unit screen stays black when connected to the pc, but it will sound that it has connected, the single USB cable should be used from the back of the head unit.