Related
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/
SPECIAL KNO'DIS: This Guide has been changed to refelct proper installation for both types of Maven Pro tablets, be Sure to follow the appropriate guide.
For the purpose of this guide, I'll assume you already have working ADB and Fastboot on your PC, if not, you'll need to set that up first. This guide doesn't cover installation of ether of those. If you're looking for the guide to the Viking Pro (RCT6303W87DK), go here.
KNO'DIS: I, OR ANYONE ELSE AT XDA, WILL NOT BE HELD RESPONSIBLE FOR "BRICKING" YOUR TABLET!! IF YOU MANAGE TO MAKE A BRICK, DUE TO YOUR "FUN-DA-MENTAL" INABILITY TO READ, GO BUILD A BBQ PIT WITH IT!! (Or ask for help, there's a lot of friendly people around here)
So, without further ado, lets get started. First, you'll need to know which version of firmware your device is running, this can be found in 2 different ways. From a running device go to: Settings/About tablet and look at the Build number. Or you can boot into stock recovery and the firmware version will be at the top left of the screen.
You should see something like the following, and note the 2nd number after the 2nd "V":
Code:
RCT6213W87DK-ANDROID5.0-V37-V1.9.30 <-- This is x.9.x version of firmware
or
RCT6213W87DK-ANDROID5.0-V68-V1.12.30-B <-- This is x.12.x version of firmware
Now that you know which firmware you have, follow the approriate guide below. I've broken this post into 2 different sections, as each tablet is just a little bit different.
About the Bootloader
This applies to both versions of firmware and tablet users. Turns out, the booloader doesn't have to be unlocked in order to install a custom recovery or root the device. So there's really no reason to unlock it, and I have removed that portion of this guide.
Installing MTK Preloader Signed Drivers
Drivers located Here
x.9.x Versions
Steps (Windows 8/8.1/10): For step 2 you will have less than five seconds. Preloader mode is only active for a few seconds. So read first!
1- Extract the drivers to the Desktop and open the Device Manager ("right click" on the Start button, select "Device Manager")
2- Plug your tablet in as such: turn off the tablet. Plug in the micro USB on the tablet, the other to the USB port on the PC, now very quickly in the device manager locate the new device and right click on it. For me, it showed up under "Other devices" and read MT65XX.
3- Select "update driver software" then select "browse my computer for driver software" (make sure "Include subfolders" is selected.
4- Click "Browse..." and navigate to where you extracted the driver zip. You "should" be at the following path: Desktop/MTK Preloader Signed Drivers
5- Click on "OK" then "Next". The driver should install at this point. Once that is done, unplug the usb cable from the pc (I find it easier to just keep the micro in the tablet).
x.12.x Versions (Requires Full size Male-to-Male USB Cable)
Steps (Windows 8/8.1/10): For step 2 you will have less than five seconds. Preloader mode is only active for a few seconds. So read first!
1- Extract the drivers to the Desktop and open the Device Manager ("right click" on the Start button, select "Device Manager")
2- Plug your tablet in as such: turn off the tablet. Plug in the full size USB cable to both the tablet and the PC.
3- Plug the micro USB into the tablet, the other to another USB port on the PC, now very quickly in the device manager locate the new device and right click on it. For me, it showed up under "Other devices" and read MT65XX.
4- Select "update driver software" then select "browse my computer for driver software" (make sure "Include subfolders" is selected.
5- Click "Browse..." and navigate to where you extracted the driver zip. You "should" be at the following path: Desktop/MTK Preloader Signed Drivers
6- Click on "OK" then "Next". The driver should install at this point. Once that is done, unplug both USB cables from the PC (I find it easier to just keep them in the tablet).
Installing TWRP
Firmware/TWRP Downloads
Maven x.9.x (Currently Contains: V37-1.9.30 and TWRP)
Maven x.12.x (Currently Contains: V63-V1.12.0-20150802 and V66-1.12.20-B-20150831 Firmware and TWRP)
Special Thanks to: @ShadowCX11 for testing for me.
Be sure you are using the appropriate TWRP for your version of firmware, and do the following:
1- Extract the firmware and the SP Flash Tool to your desktop.
2- Start the SP Flash Tool, and where it says "scatter file loading" click and navigate to the folder where you have the firmware and load the scatter file (depending on device, it could be in the "Images" folder).
3- Once that is done, uncheck everything, and select "recovery" only, from the list, navigate to the TWRP image file and click "Open", then click on the download button.
4- Plug the USB cable(s)* back into your PC. At this point the flash tool will load the recovery to the tablet. DO NOT UNPLUG ANYTHING UNTIL THE FLASH TOOL SHOWS YOU A GREEN CHECK MARK TO INDICATE THAT IT IS DONE, OR YOUR TABLET COULD BE HARD BRICKED AND IRREPARABLE.
5- After you get your check mark, unplug and boot into recovery, hold the Volume + and Power button. When splash screen comes up (the 2 dogs) release the power button.
6- Welcome to TWRP
*Remember, x.12.x requires 2 USB cables to work
ROOT
You can get root by flashing the latest SuperSu zip file located here, be sure to download the flashable zip.
Otherwise, for root, you can use the KingRoot app located here, (get the apk, or "Download for Android") and if you don't want a Chinesse Super User app, you can replace it with the ChainFire SuperSu by going here.
NOTE: This method of replacing KingRoot with SuperSu no longer works properly, and results in a bricked device.
Device Tree
GitHub
CREDITS
@vampirefo (for the CWM Recovery and teaching me about TWRP, there would be no recoveries if it wasn't for him!)
@Bogram (for the lk.bin patch trick)
@smartmanvartan (for the flashing guide)
Reserved
Reserved #2
Hello! I've had my Maven Pro for a couple months now and I still haven't rooted it like I have with the rest of my devices. I'd love to do it too, but reviewing your instructions, I found that my version number is way different. V66-V1.12.20-B. will that version patch tool still work for it? is there an update that it's refusing to download? Thanks!
Edit: on top of this, i can't get it to even connect (step 2) with any of my microUSB cables. (they work with my other devices)
equinox13 said:
Hello! I've had my Maven Pro for a couple months now and I still haven't rooted it like I have with the rest of my devices. I'd love to do it too, but reviewing your instructions, I found that my version number is way different. V66-V1.12.20-B. will that version patch tool still work for it? is there an update that it's refusing to download? Thanks!
Edit: on top of this, i can't get it to even connect (step 2) with any of my microUSB cables. (they work with my other devices)
Click to expand...
Click to collapse
Ooh, a v12, sorry friend, lol. Make sure the tablet is off, and be ready with "Device Manager" open, the preloader only shows up for a bit, then it disappears. The patch tool should still work for you, but the TWRP recovery may not. If it doesn't, the CWM recovery will after I modify it, because it's non-touch.
If neither recovery works for you, you can give me a copy of your "boot.img" file, and I can convert TWRP or CWM to work on your tablet. Also, I've changed the guide up top to include other root methods.
If you have any trouble, by all mean, post, and I'll try to help you through it
Regards,
Nepo
EDIT:
A friend found some V12 firmware, and I'll be uploading it soon. I can get a boot.img file from it to make a recovery.
My maven pro is stuck in a bootloop after I rooted now I don't know what to do. I can't even shut it down
GartimusPrime said:
My maven pro is stuck in a bootloop after I rooted now I don't know what to do. I can't even shut it down
Click to expand...
Click to collapse
You can reflash firmware while it is in a bootloop, I've done this many times. If you have everything set up, drivers, SP Flash Tool, firmware, etc..
Do the following:
1) Startup the Flash Tool and Load your firmware, as described in the OP (be sure to "uncheck" the Preloader)
2) Plug in your micro USB cable to both the PC and the tablet
3) Press and hold the "Reset" button located on the back
4) Click the Download button, then let go of the reset button, it should start flashing the firmware.
If it doesn't the first time, retry steps 3 and 4. I've had it fail the first time before, but work on the second.
Good Luck and let me know how it goes. Also, if the battery is completely drained by the time you read this, just flash firmware normally (again, uncheck the preloader). The tablet has to be powered off to flash it anyway.
Regards
Nepo
So after reflashing my tablet (a Canadian V12 that had V68, and flashed to V66 trying to unlock the boot loader and install CWM), USB doesn't work. The port doesn't output any voltage, and neither does the keyboard connector. The tablet acts like nothing is there, as does the PS3 controller I tried. Also, before, Firmware Update would say there's no updated firmware. Now, it doesn't seem to do anything. I flashed every partition except preloader, MBR and ebr, and the sec partitions. Do I have to reflash again, or is there something else I can do?
On a completely different note, I tried flashing a patched lk.bin, and it failed with an error I don't remember (I had temporary access to a PC).
One more thing that was quite interesting to me. It seems if you reboot into recovery or bootloader from Android (APM+ or root), you're then able to access the recovery with Power + Vol. Up. Is this known, or was it a fluke?
ShadowCX11 said:
So after reflashing my tablet (a Canadian V12 that had V68, and flashed to V66 trying to unlock the boot loader and install CWM), USB doesn't work. The port doesn't output any voltage, and neither does the keyboard connector. The tablet acts like nothing is there, as does the PS3 controller I tried. Also, before, Firmware Update would say there's no updated firmware. Now, it doesn't seem to do anything. I flashed every partition except preloader, MBR and ebr, and the sec partitions. Do I have to reflash again, or is there something else I can do?
On a completely different note, I tried flashing a patched lk.bin, and it failed with an error I don't remember (I had temporary access to a PC).
One more thing that was quite interesting to me. It seems if you reboot into recovery or bootloader from Android (APM+ or root), you're then able to access the recovery with Power + Vol. Up. Is this known, or was it a fluke?
Click to expand...
Click to collapse
No USB is a new one on me, I wish I had a x.12 version of this tablet to test on (mine's x.9) I'd try a re-flash, this time, do everything but the preloader, the reason for not flashing a preloader is because it sometimes semi-bricks one of these tablets.
Interesting note, there was a guy on the Viking thread (RCT6303W87DK) that flashed CWM without unlocking his bootloader, and everything is working fine for him...
Regards,
Nepo
PS, Power + Vol Up is the standard way to enter recovery on this device (I have the Xposed APM+ apk installed too)
NepoRood said:
No USB is a new one on me, I wish I had a x.12 version of this tablet to test on (mine's x.9) I'd try a re-flash, this time, do everything but the preloader, the reason for not flashing a preloader is because it sometimes semi-bricks one of these tablets.
Interesting note, there was a guy on the Viking thread (RCT6303W87DK) that flashed CWM without unlocking his bootloader, and everything is working fine for him...
Regards,
Nepo
PS, Power + Vol Up is the standard way to enter recovery on this device (I have the Xposed APM+ apk installed too)
Click to expand...
Click to collapse
So just a quick question: Is the device /dev/recovery for sure recovery? I want to see if I can just use dd to flash recovery.
ShadowCX11 said:
So just a quick question: Is the device /dev/recovery for sure recovery? I want to see if I can just use dd to flash recovery.
Click to expand...
Click to collapse
Yes, to pull a copy from a running tablet you use dd, and the path is: /dev/recovery
So, I'd do it this way, using adb:
Code:
adb push NAME_OF_RECOVERY.img /data/local/tmp
# Wait for it, then type:
adb shell
#Followed by:
dd if=/data/local/tmp/NAME_OF_RECOVERY.img of=/dev/recovery
#After it finishes:
reboot recovery
Okay, I got CWM installed! Now to see if I can find a way to build TWRP...
ShadowCX11 said:
Okay, I got CWM installed! Now to see if I can find a way to build TWRP...
Click to expand...
Click to collapse
Great! Is the CWM in portrait or landscape? You can always try to port the one I built for the x.9's, just unpack stock recovery, unpack TWRP, swap out the prebuilt kernel and repack.
NepoRood said:
Great! Is the CWM in portrait or landscape? You can always try to port the one I built for the x.9's, just unpack stock recovery, unpack TWRP, swap out the prebuilt kernel and repack.
Click to expand...
Click to collapse
It's in landscape, and works quite well! I just like the touch interface a bit more. I'll try the kernel replacement.
ShadowCX11 said:
It's in landscape, and works quite well! I just like the touch interface a bit more. I'll try the kernel replacement.
Click to expand...
Click to collapse
I prefer TWRP as well, that's why I built it
The only reason I don't have one posted for x.12 users is I can't test it. If you get it to work properly, let me know and I'll add it to the OP so others can benefit. :good:
If not, I can do some builds for you to test, if you don't mind. I have the x.12 kernel in my repo
NepoRood said:
I prefer TWRP as well, that's why I built it
The only reason I don't have one posted for x.12 users is I can't test it. If you get it to work properly, let me know and I'll add it to the OP so others can benefit. :good:
If not, I can do some builds for you to test, if you don't mind. I have the x.12 kernel in my repo
Click to expand...
Click to collapse
Yeah, I can't figure out how to extract the kernel, because I don't usually have access to a PC. However, I'll take some testing builds if you can make them.
Also, back to the USB issue, a reflash of everything except preloader didn't fix it. However, checking the firmware update now tells me that this is the latest version (which is definitely wrong, since I had v68). It must be an incompatibility between the USA and Canadian variants. If you find a Canadian firm dump, can you send me a link?
---
Hmm, okay.
So I just took a look at the model number on my box, and it's RCT5213W87DKF. That extra letter is what changes this a bit. I'll try seeing what I can dig up in terms of OTA updates, and I'll keep posting about what I find.
---
Okay, so after a few packet captures, I found the tablet makes a GET request to http://tablet12.gyrodock.com:2300/OtaUpdater/android?device=RCT6213W87DK with the User-Agent rk29sdk/4.0, but the server returns a 404 page. When I do this in the browser, however, I get something quite peculiar happen, which interests me. Most of the other places on the site return a Tomcat 404 that has the path in the parenthesis. However, for the OTA URL, it just has empty parenthesis. POST requests to that URL return a 200 OK with no return data, which is also interesting. I'll keep hunting around.
Some people might not have a PC to run flash_tool on, so here's how you can flash recovery/uboot/mbr/ebr2/logo/sec_ro from within Android
I'll use recovery as an example. I'm using a V12 tablet, so steps might be different if you have a V9. I tried to make this guide as revision-agnostic as possible, so correct me if I mess something up.
Root your device. The method I use is KingRoot, because it doesn't require any weird things. You can uninstall KingRoot and flash SuperSU later.
Download a recovery image. Make sure if you have a V12 tablet, you download a recovery image for V12, and a V9 recovery for a V9 tablet, or you'll brick your recovery. I personally prefer TWRP, because it has more features and a nicer UI, but CWM works too.
Get shell access. You can use a terminal emulator.
Type in su, and give the terminal superuser access on your device.
Type in dd if=/sdcard/Download/mavenVY_XXX.img of=/dev/recovery, where Y is 9 or 12, and XXX is CWM or twrp3.0.2. This will flash the recovery image.
Finally, type in reboot recovery. This should reboot into your custom recovery! It might also enable Power + Vol Up access to recovery, however, this hasn't been confirmed.
All the other partitions are similar, just replace the references to recovery images with the respective file names for the raw partition, and /dev/recovery with /dev/[PARTITION]. You can NOT flash the android or usrdata partition while in Android or you'll most likely soft-brick your tablet, however, you can boot into TWRP and go to the terminal and do the flash. You must copy your disk images to /tmp when doing so however, or you'll probably lose the disk image during the flash, effectively causing a brick.
Hope this helps people out!
ShadowCX11 said:
I've found out that it seems the v12 tablets strictly enforce the checksums of partition images, so flashing a custom recovery or uboot does not work with flashtool.
Click to expand...
Click to collapse
Nice addition, but all you have to do is disable it in the Checksum.ini file (change the 1 to 0):
Code:
[IsEnableChecksum]
CHECKSUM_SWITCH=0
I did that for the v9 versions, but only uploaded the v12 firmware...
NepoRood said:
Nice addition, but all you have to do is disable it in the Checksum.ini file (change the 1 to 0):
Code:
[IsEnableChecksum]
CHECKSUM_SWITCH=0
I did that for the v9 versions, but only uploaded the v12 firmware...
Click to expand...
Click to collapse
Oh... makes sense...
ShadowCX11 said:
Oh... makes sense...
Click to expand...
Click to collapse
I'm glad you posted that info, it'll be super handy for folks that may not have access to a PC, or would rather use their device instead of a PC :good:
We are trying to get hold a custom recovery for Lenovo Tab3-710F. We are using hundreds of Lenovo tablets in our projects and have up until now used Tab2 A7-10 which has a custom recovery build for it (found here att XDA).
The reason we need the custom recovery is for cloning the unit which works good in CWM or TWRP.
The problem now is that Lenovo have stopped selling Tab2 so we are now stuck with a unit we cant clone.
Have somebody successfully created a custom recovery for the unit? If not or if you have we are offering payments/devices to get this working asap. Are you interested please PM us? When we have it we can share it to the world here no problems for us.
If you need to root the device KingoRoot latest APK works.
So hope somebody can help us.
Perhaps useful for you: I've managed to extract the stock rom of a brand new TB3-710F
http://forum.xda-developers.com/android/help/lenovo-tab-3-7-essential-tb3-710f-mt8127-t3416397
This also includes the "recovery.img" so you could try to change this image and simply flashing it. If it does not work you'll have a stock rom to restore it.
gogetrd said:
We are trying to get hold a custom recovery for Lenovo Tab3-710F. We are using hundreds of Lenovo tablets in our projects and have up until now used Tab2 A7-10 which has a custom recovery build for it (found here att XDA).
The reason we need the custom recovery is for cloning the unit which works good in CWM or TWRP.
The problem now is that Lenovo have stopped selling Tab2 so we are now stuck with a unit we cant clone.
Have somebody successfully created a custom recovery for the unit? If not or if you have we are offering payments/devices to get this working asap. Are you interested please PM us? When we have it we can share it to the world here no problems for us.
If you need to root the device KingoRoot latest APK works.
So hope somebody can help us.
Click to expand...
Click to collapse
Did u manage to get TWRP or CWM for TB3-710F ?
zwirc said:
Did u manage to get TWRP or CWM for TB3-710F ?
Click to expand...
Click to collapse
Yes, I built it for them. Download here
@Tzul @gogetrd We are trying to achieve something similar, configure about 700 tablets of this model. I have played with custom ROMs in the past, but mostly as a consumer (e.g. Cyanogen on personal devices).
It is my understanding that installation using the files provided by @Tzul would require to;
0. create a custom ROM.
Then for each device
1. root device (e.g. Developper mode, allow "Unknown source"s, adb install one rooting apk, run it, etc).
2. install custom recovery on device
3. flash custom ROM
Am I right?
If so do we agree that the time spent doing these operations might be about similar than the time spent e.g. manually installing / configuring the device? Or is there a way to automate the steps above?
You can configure 1 tablet, then extract the ROM and flash it with the "download mode". You don't even need to boot the tablet!
If you want more info let me know, back from holiday in a few days
@lacostej You can certainly automate some steps, and you do not always need root. (And the best way to root is to install the latest SuperSU via TWRP; no need for questionable apps that are doing who knows what...)
There are three ways to install another firmware:
The MediaTek SmartPhone Flash Tool (SPFT). This is a PC program (Windows and Linux) that allows reading and writing of the entire internal storage (on a partition granularity). Via USB, while the device is powered down. Only for devices based on MediaTek chips, of course (this tablet is MediaTek-based).
Fastboot. This is a little USB protocol implemented by the bootloader. A Fastboot client on PC can communicate with the bootloader via USB and execute certain commands, e.g. "fastboot flash" for flashing partitions. However, there are a few drawbacks with this:
First, you need to boot the device into fastboot mode. Some devices have a boot menu that allows you to do this, but this device doesn't. Starting the tablet via power+volumeUP takes you directly to the recovery instead of a boot menu. But in the recovery, whether stock or TWRP, there's a reboot to bootloader option. Using ADB (adb reboot bootloader) should also take you there.
Second, the "fastboot flash" command is restricted on this tablet. If you were to use "fastboot flash recovery <recoveryfilename_here>", for example, it would abort with an error message. I have patched the bootloader to allow the flash command, but you'd first need to install this patched version on your tablet(s), of course, via SPFT or other means.
Third, the "fastboot flash" command has a size limit - the bootloader needs to buffer the USB data in RAM before it can be written, and since the tablet has only 1 GB of RAM, you obviously can't flash a 1 GB system image this way. The buffer is actually a lot smaller: just 128 MiB. Meaning whatever file you send to the tablet via "fastboot flash", it cannot be larger than 128 MiB. So, how do you flash the system or userdata partition then, which are much, much larger? By splitting their image file into many smaller "sparse" image files, each of which is below the size limit. There's probably a tool for doing this, but I don't know any details.
TWRP, or another custom recovery. They allow you to create and restore backups. TWRP has some automation support via OpenRecoveryScript.
So, if you have 700 tablets to configure, you can configure just one, then save its state via SPFT or TWRP, then restore that on each other tablet.
What is its "state"? Well, the system, cache, and data partitions. The system partition is normally read-only and won't change, therefore you do not need to clone it. Unless you install root and modify stuff on the system partition, of course. The cache partition is quite irrelevant. It is the data partition that has all the app settings.
However, if you clone the data partition from one tablet to others, then you're causing each tablet to use the same Android ID (a long number identifying an Android device, usually randomly generated when Android is first booted after a factory reset), the same Bluetooth and WiFi MAC addresses, and some other IDs that should be unique on each device (the tablet's Lenovo serial number might be in some cloned files as well, e.g. the WiFi settings).
You can at least avoid cloning the MAC addresses by deleting the entire directory /data/nvram/ before you create your backup. MediaTek devices have a dedicated NVRAM partition that contains the MAC addresses and some other stuff, and this data gets unpacked to /data/nvram/ when Android boots. Unless the files there already exist. So, by deleting /data/nvram/ before you clone, you force each tablet to extract its unique MAC addresses again at the next boot...
Thanks a lot for the feedback. Really appreciated.
Tzul said:
@lacostej And the best way to root is to install the latest SuperSU via TWRP; no need for questionable apps that are doing who knows what...
Click to expand...
Click to collapse
Doesn't SuperSU already requires root? (http://forum.xda-developers.com/showthread.php?t=1538053)
How did you get root on your Lenovo device? (I assume you had one to dump the image)
However, if you clone the data partition from one tablet to others, then you're causing each tablet to use the same Android ID (a long number identifying an Android device, usually randomly generated when Android is first booted after a factory reset), the same Bluetooth and WiFi MAC addresses, and some other IDs that should be unique on each device (the tablet's Lenovo serial number might be in some cloned files as well, e.g. the WiFi settings).
.
Click to expand...
Click to collapse
That's exactly the thing I was worried about when it comes to cloning. Those problems might arise later during QA, and I probably don't have the time required to do it properly this time.
lacostej said:
Doesn't SuperSU already requires root? (http://forum.xda-developers.com/showthread.php?t=1538053)
How did you get root on your Lenovo device? (I assume you had one to dump the image)
Click to expand...
Click to collapse
SuperSU is just like any other root manager. It provides the actual "su" (superuser) binary that other programs rely on to obtain root privileges, plus an Android app for managing permissions and settings. The su binary needs to be installed on the system partition (at least traditionally), but in order to get write access there, you need root privileges. Therefore, this is a chicken and egg problem: SuperSU provides root, but it also needs root in order to be installed. Other root manager are no different - except that some try to exploit security flaws in Android in order to temporarily obtain root and install their su binary.
Anyway, the classic solution to this conundrum is the (custom) recovery: it basically has root built-in. It can write to the system partition by default, after all one of its jobs is to install firmware updates.
TWRP includes a SuperSU stub. If you leave TWRP via the Reboot menu, it checks whether or not the su binary is installed (at least in Android 4 and 5), and if it isn't, it asks if you'd like to install the SuperSU stub. Which you can then use in Android to update to the latest SuperSU via Play Store. But you can also install SuperSU's latest "update zip" in TWRP to immediately install the full version.
lacostej said:
That's exactly the thing I was worried about when it comes to cloning. Those problems might arise later during QA, and I probably don't have the time required to do it properly this time.
Click to expand...
Click to collapse
Yeah, it is annoying. MediaTek apparently wisened up a bit. Newer platforms they produce do not unpack the NVRAM partition to the data partition anymore. Instead, they use a dedicated "nvdata" partition for that purpose. That way, if you clone the data partition, you at least won't include the unpacked NVRAM data (MAC addresses and IMEI). But still, some other IDs such as the Android ID, references to the serial number, etc. will very likely be referenced by some other files on the data partition.
I created a little "update zip" that can be "installed" via TWRP, which is just a shell script that tries to delete all the files on the data partition that contain unique or sensitive info. I use it to "clean" a data partition before publishing it. But it's not perfect yet...
@Tzul Your modified rom is great. But I have one problem with it.
When you connect your turned off device to the power supply there is a clock and charging animation. The clock is several hours ahead of the system clock. System clock and clock during the charging are connected (when I change the system time the 2nd clock also changes the hour).
I was trying to use hwclock but without success.
Is there some kind of file where I can set the correct time zone for the 2nd clock?
Sorry for my English.
@Yozen I didn't modify the ROM. I extracted and packaged it.
When the tablet is turned off and then connected to a power supply, it will usually start "off-mode charging" (can be disabled, so that Android will boot up instead). This is handled by the bootloader (LK, lk.bin), which also displays the battery animation and the clock that you see. Apparently the bootloader on this device doesn't handle time zones, because the clock shown uses China Standard Time (CST, UTC+08:00). This is the first MediaTek-based device I've seen which shows a clock in the off-mode charging screen at all. I guess they normally don't because they have no simple way to figure out the user's correct time zone at that stage.
Will this method and these files work for TB3-730F?
Sir, is there a custom ROM available for Lenovo tab3-710f ?
lacostej said:
@Tzul @gogetrd We are trying to achieve something similar, configure about 700 tablets of this model. I have played with custom ROMs in the past, but mostly as a consumer (e.g. Cyanogen on personal devices).
It is my understanding that installation using the files provided by @Tzul would require to;
0. create a custom ROM.
Then for each device
1. root device (e.g. Developper mode, allow "Unknown source"s, adb install one rooting apk, run it, etc).
2. install custom recovery on device
3. flash custom ROM
Am I right?
If so do we agree that the time spent doing these operations might be about similar than the time spent e.g. manually installing / configuring the device? Or is there a way to automate the steps above?
Click to expand...
Click to collapse
How did you do it in the end? I'm trying to do something similar here and am very curious!
.acy said:
How did you do it in the end? I'm trying to do something similar here and am very curious!
Click to expand...
Click to collapse
For us it is this "simple".
1. Manually configure a single device
2. Readback the ROM (get the ROM from the device and store it on your PC) using SP Flash Tool
3. Parse the ROM from a single file to multiple files using Mtk Droid Tool
4. (clear cache partition & remove stuff like serial number)
5. Load your ROM in SP Flash Tool
6. Click start
7. DO NOT START your new tablet
8. Connect it to USB
9. Wait (assuming you already have the preloader drivers installed)
10. Done, new ROM is flashed to your tab!
edit:
Oh and with 700 tablets it might be nice to look into compressing the file as the full 8gb dump we flash (and we don't do a lot these days) will take ~30-40 minutes
mattiemvs said:
3. Parse the ROM from a single file to multiple files using Mtk Droid Tool
Click to expand...
Click to collapse
That's unnecessary, because the SP Flash Tool can already read back partitions into separate files.
Also, you don't need to clone some partitions like cache, and you really should not clone nvram and parts of data, otherwise you'll end up with tablets sharing unique IDs such as MAC addresses, which will cause problems.
Tzul, you are absolutely right! I typed the items from my mind as it has been quite some time since I've created the ROM
tb3-710f s000028
Tzul said:
Yes, I built it for them.
Click to expand...
Click to collapse
Hello tzul,
Thanks for your jobs.
I want to install Lenovo_TB3-710F_S000027_TO_S000028_Patched_Tzul.zip
But i don't know how i do this when i try with SPFT i choose teh scatter-file and i have an error :
sp flash toll error : 5417
The load scatter file is invalid !
hint :
please check the scatter file and select again
Can you help me ? please
@siegheart73 That is a patched OTA update. It needs to be installed by the recovery (stock or TWRP). If a zip file contains a "META-INF" folder, then it's most likely intended for the recovery, and not for the SPFT.
Tzul said:
@siegheart73 That is a patched OTA update. It needs to be installed by the recovery (stock or TWRP). If a zip file contains a "META-INF" folder, then it's most likely intended for the recovery, and not for the SPFT.
Click to expand...
Click to collapse
Thanks for your answer.
I go to test it.
I want to root this kernel 000028 and i have difficult to do it ?
Do you have a easy solution ?
Thanks a lot for your help.
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
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.