yashsingh1/xdaforums huggingface dataset:
[Teclast X98 Air 3G] guvno:
ROOT DONE

Selected option 5 from the launcher "CMW" then used trigger T4.

This indeed booted the unit into custom recovery and I managed to select my su.zip file. I also decided to do a "backup to external sd card" while in custom recovery so I am doing that too, not sure if its any good but though its an idea.

BTW, choosing TWRP also works with trigger T4 but for some reason the touchscreen is not working so TWRP is a no go, use CMW.

So, the next step is to use hordarians instructions to do the dump, I will try this next, or will that backup in CMW that I am just now doing to the external sd card do the job? Tell me and I will start the upload.

BACKUP DONE... using Hordarians instructions

Allthogh, running the first command in the windows terminal resulted in "Permission Denied"

I had to start with:

adb root

and then I used Hordarians first command:

adb shell "dd if=/dev/block/mmcblk0 | gzip > /sdcard/mmcblk0.img.gz"

This is now generating a big mmcblk0.img.gz file on my sd card

I guess when it is finished that will be all that is needed right?

I can upload it to my google drive and share, will some expert be able to make this flashable?

Just to summarize, this will be the upload of the clean stock Teclast X98 air iii ROM V1.00_20151204

It is factory erased, as it came from Teclast, only rooted and SU installed

DUMP COMPLETED

Ehm, yeah, I guess Hordarian was right in saying that a complete dump using:

adb shell "dd if=/dev/block/mmcblk0 | gzip > /sdcard/mmcblk0.img.gz"

is not needed... As it resulted in a 32GB file...

I will try the other commands and hopefully generate 3 smaller files, I don't think I can upload that 32GB file, unless it becomes substantially smaller when compressed?
[Teclast X98 Air 3G] SkubiDoo:
Nice information guvno! Good try!

Does anyone have idea if CWM backup would work? Or it can brick the tablet?
[Teclast X98 Air 3G] SkubiDoo:
question is if now we can restore this backup ;) on other tablet without any problem

From Xiaomi Mi4c Prime sent by Tapatalk
[Teclast X98 Air 3G] :
someone link a recovery.img from your model stock rom and i will make a twrp for it
[Teclast X98 Air 3G] hordarian:
Surprising it's generated such a big file, the gzip should have squeezed it down substantially.
[Teclast X98 Air 3G] :
encrypted data?

also, imo you ppl should only dump the partitions that are 'really' needed for a 'home-made' rom: ESP, boot, recovery, fastboot, system
[Teclast X98 Air 3G] guvno:
Right folks, so here goes:

The below is a link to my Google Drive which should have 2 compressed files

One is the dump using Hordarians ADB commands

One is the CWM backup which I did

Both are of the clean stock Teclast ROM

Now if someone can just make something useful of this, like make it flashable using Intel MFT or similar? Surely it cant be as easy as just replacing the image and system file from one of the other ROMs, like mireks and flash?

Or, as Scobi already asked, can I just put the SD card that has the CWM backup into my other Air III unit and get to CWM and use restore instead of backup or will that brick the unit?

Here is the link:

https://drive.google.com/folderview?id=0ByduPU9AsJInd2lsUEUxSk5tNnM&usp=sharing
[Teclast X98 Air 3G] :
you should remove 'data' from backup if you have sensitive stuff already configured on your tab (accounts etc)
[Teclast X98 Air 3G] SkubiDoo:
He wrote before that's backup is made after reset to factory settings..

From Xiaomi Mi4c Prime sent by Tapatalk
[Teclast X98 Air 3G] :
first, a factory settings (you meant reset?) is not guarantee to wipe (zero out) the partition (so the data can still be there)

second, the 'data' backup is either way irrelevant for the purpose declared, the partitions needed are: ESP, boot, recovery, fastboot, system
[Teclast X98 Air 3G] hordarian:
Grabbing. I'll give a reflash a go later when I'm home.

CWM restore may/may not work, it depends if the partitions are configured the same on both units.

Reflashing the MMC has a chance of messing up the operating system, but we are not touching the BIOS at all so the unit would only ever be soft-bricked, since we can enter DNX mode to recover it.
[Teclast X98 Air 3G] SkubiDoo:
I keep my fingers crossed for you guys to make it successfully!

From Xiaomi Mi4c Prime sent by Tapatalk
[Teclast X98 Air 3G] guvno:
Sounds good Hordarian. I am also tempted to do a CWM restore on my other unit and see how that goes. If the partitions are different. Do you think that entering DNX mode will still work? As then I can still flash using MFT so no risks involved?

Just to clarify some questions in some other posts.

This is a clean dump of a Teclast X98 Air III 32GB version, android only, no dual boot BIOS.

No user data is there, it is completely factory reset, only rooted. And the ROM build is that latest Teclast V1.00 20151204 build which AnTuTus higher than mireks v7 ROM. It seems to be what Teclast ship their units with today, at least to EU...
[Teclast X98 Air 3G] guvno:
Well. I could not upload this huge file... I assume it is a "block by block" dump or similar, so even empty space is copied... Not sure... But anyway... I also did a dump using Hordarians adb commands... I think the partitions copied were system, image and recovery. Are there more needed? The original unit is still completely unused and factory reset so if anyone can tell me which adb commands to run I'd be happy to do it and upload what I get.

I have still not dared to run the CWM recovery on my other unit using the backup data from my first unit... Does anyone know if it will work and if not if DNX mode will still work? Hordarian seems to think that it will so if I dont hear otherwise I will give it a try later this eve
[Teclast X98 Air 3G] :
haven't checked what has been dumped, just passing-by this thread, however since i already did stuff like this:

to make a flashable rom you need the dd image files of ESP, boot, recovery, fastboot, system partitions

ESP, boot, recovery, fastboot can be used as they were dumped (changing their names of course, ESP -> esp.img, fastboot -> droidboot.img etc)

system cannot be flashed in the dumped format- ext4 (will error when flashing) you need to make a flashable image out of it (also make sure you apply the selinux context on the files in it or the device wont boot or have unexpected behavior) this will result in the system.img

at the end extract the attached files (they are from the m5c5 stock rom) in the folder where the new img files are, this will also ensure the rrequired partitioning formatting (since is the same device model they should be the same) or just make a simple batch file copying the fastboot commands in the xml script in the order they appear, fastboot flash, format, etc, (in the end Intel Phone Flash Tool or the Manufacturing one are nothing but a crap load of MBytes for an interface to fastboot)
[Teclast X98 Air 3G] guvno:
Thanks for the info ionioni.

This seems a little complicated... Any chance you can help? Just tell me which adb commands to run to dump the correctly needed partitions and I can do this and upload them. After that, I suppose anyone can continue from that point and rename the files to their correct format, make the system partition flashable and fix the .xml file?

You would'nt happen to be able to answer my question regarding whether a CWM backup from one unit can be restored on another? And if not, whether it will brick the attempted unit?
[Teclast X98 Air 3G] :
ok, two more partition dumps are needed for ESP and fastboot (dunno if they are visible from cwm so go for the dd approach)

just so i won't mess what you have used already as syntax, i will use the same

adb shell "dd if=/dev/block/by-name/ESP | gzip > sdcard/ESP.img.gz"

adb shell "dd if=/dev/block/by-name/fastboot | gzip > sdcard/fastboot.img.gz"

adb pull /sdcard/ESP.img.gz

adb pull /sdcard/fastboot.img.gz

then upload them

cwm could be fine but i don't know whether it has all these partitions detected, i think the better approach is to have a (virtually) stock rom that one can flash as known, also the flashing will start anew with the partitions table and reinitialize them (format) cwm would also need some extra steps when installing that one might or might not be familiar with
[Teclast X98 Air 3G] guvno:
Many thanks ionioni.

I will dump these 2 partitions as well and upload a new compressed file with all 5 partitions rather than just the 3 currently done.

Will let u know once done! Thanks again.... Also I think I will give the CWM recovery a go on the other unit... I am hoping thay if I brick it it will still be DNX mode accessible
[Teclast X98 Air 3G] :
hah, i just fastboot flashed the costructed system.img (from the dump) and made a boot image from the one you dumped using my kernel (i have a Lenovo Yoga Tab 2 Pro) and guess what? this is hilarious (adb, mtp working, but no projector as in my stock rom??? :)
[Teclast X98 Air 3G] SkubiDoo:
Lol ;D so it looks good ;) I hope in other Air III M5C5 it will work without any problem. Just please share with me files and the way how to do it on tablet with mirek v7 rom

From Xiaomi Mi4c Prime sent by Tapatalk
[Teclast X98 Air 3G] hordarian:
Thanks for the advice ionioni. I've had fun (compiling the damn tools is a pain on Arch Linux) making a flashable system.img (uploading it now), but it works! My partitioning may be mireks, if that's different to the original, but I'm happy enough to just be back to AOSP!

Mega thanks guvno :) I'll pop the link to the repacked system.img up once it's finished uploading.

For whatever reason, when I was making the dd instructions I could not mount the dump of mireks system.img here - but your stock one mounted perfectly first time :)
[Teclast X98 Air 3G] hordarian:
Flashable system.img here https://drive.google.com/file/d/0BxaCVgxhLwHFdUdBSlJfZ05tTTQ/view?usp=sharing

GUnzip first of course.
[Teclast X98 Air 3G] SkubiDoo:
Please could you share also boot.img because it looks better than mireks one?

How should I proceed with instalation from mirek v7 ROM ?
[Teclast X98 Air 3G] :
system.img already made and tested (seeing that i fastboot flashed it) didn't upped as i was waiting for the other two dumps in order to complete the full rom

well then...
[Teclast X98 Air 3G] SkubiDoo:
Ok so I will wait for full rom and hopefully instruction how to install it from mirek v7 :)
[Teclast X98 Air 3G] :
nope, i mean i will step back from this now :) but once the other two partitions are added to the existing ones (together with the xml script and the efi loader) that's it
[Teclast X98 Air 3G] SkubiDoo:
So who could prepare full rom from the dumps which guvno made? And instructions how to flash it?
[Teclast X98 Air 3G] hordarian:
You know better than me how to pack everything together :) Anyone wanting to come for a completely clean ROM should wait for the whole thing - I just skipped a few bits as I knew mireks ROM hadn't altered those partitions.
[Teclast X98 Air 3G] :
not me :)

with the instructions given putting it together is trivial

have fun
[Teclast X98 Air 3G] guvno:
All good then, I'll try to flash this on my other Air III.

Am I correct in assuming that I just replace the system.img file in Mireks v7 and flash normally?

BTW, I am still uploading a new "X98 Air III V1.00_20151204 Clean Stock Dump using ADB terminal.7z" file containing all 5 partitions as asked for by ionioni but it is taking some time... That is how it is being in UK and being on TalkTalk Fiber Broadband (1.5Mbps up speed) :(
[Teclast X98 Air 3G] SkubiDoo:
Could someone reply how to install it on Mirek V7?
[Teclast X98 Air 3G] SkubiDoo:
Ok I've got it on my hard disk.

How to flash it by DNX mode? Any commands or tools I need? Or just replace with files Mirek v7 ROM and reflash by his tool and instruction?

EDIT:

I'm trying with instruction from here: http://xdaforums.com/showpost.php?p=61852850

ERROR:

http://i.imgur.com/dE3TXYa.png
[Teclast X98 Air 3G] :
rom link

if manuf tool not working for you try using flash.bat (needs fastboot in path) will do the exact same thing as the xml (start in dnx mode then run the flash.bat file)
[Teclast X98 Air 3G] SkubiDoo:
I've downloaded once again. Reinstalled the drivers you sent me, but still the same :(

When I try with flash.bat it goes like this:

< waiting for device >

error: cannot load 'efilinux.efi'

cannot load 'droidboot.img': No such file or directory
[Teclast X98 Air 3G] :
really now? you need to place the bat file where the efilinux, droidboot.img etc files are
[Teclast X98 Air 3G] SkubiDoo:
I unzip everything into one folder and starting flash.bat from there as administrator..

EDIT:

Ok without admin rights it started.. lets see in a while. Flashing.

EDIT2:

Thank you so much! Works :D Just I don't understand why around 200MB (one the one I've flashed from mirek v7 ) is missing in storage compering both tablets.
[Teclast X98 Air 3G] :
missing from where? from the rom that are flashed? from the device?

what rom are you talking about? link
[Teclast X98 Air 3G] SkubiDoo:
I have 2 x Air III.

One arrived with ROM full of chineese **** so I've installed on it Mirek V7 ROM from: http://xdaforums.com/x98-air/development/mirek190romv5-0-android-lollipop-t3206772

Second arrive with clean ASOP - this we try to dump and install.

Finally I've installed this ASOP on the first where was Mirek V7.

Difference is in Storage.

Internal storage is 25,02GB and in the clean ASOP is around 25,2xGB - I've checked it yesterday. I don't have both of them now to show you screenshots - I will do it later.
[Teclast X98 Air 3G] :
means that they have different partition tables and in the AOSP one they gave more to data and ripped from some place else, probably cache as it has some 1.5GB (i have used the table present in the stock M5C5 rom i found somewhere). enable usb debugging on the AOSP one (make sure is the clean AOSP one as that one is the one we need to dump the partition sizes from) so you can connect with the adb shell and from a command prompt input:

adb shell cat /sys/block/mmcblk0/mmcblk0p1/size

adb shell cat /sys/block/mmcblk0/mmcblk0p2/size

adb shell cat /sys/block/mmcblk0/mmcblk0p3/size

adb shell cat /sys/block/mmcblk0/mmcblk0p4/size

adb shell cat /sys/block/mmcblk0/mmcblk0p5/size

adb shell cat /sys/block/mmcblk0/mmcblk0p6/size

adb shell cat /sys/block/mmcblk0/mmcblk0p7/size

adb shell cat /sys/block/mmcblk0/mmcblk0p8/size

adb shell cat /sys/block/mmcblk0/mmcblk0p9/size

adb shell cat /sys/block/mmcblk0/mmcblk0p10/size

adb shell cat /sys/block/mmcblk0/mmcblk0p11/size

adb shell cat /sys/block/mmcblk0/mmcblk0p12/size

adb shell cat /sys/block/mmcblk0/mmcblk0p13/size

adb shell cat /sys/block/mmcblk0/mmcblk0p14/size

adb shell cat /sys/block/mmcblk0/mmcblk0p15/size

and paste the results
[Teclast X98 Air 3G] guvno:
Just thougt I'd add that I've now done my other Air III unit and they way I did was through CWM.

So the compressed dump file in my drive, extract it to a SD card and put it in the unit you want to update.

Use the link in this thread to root.

Launch the .bat

Type "ACCEPT"

Choose option 5 (CWM)

Choose option T4

After the unit reboots into 'CWM choose restore backup from SD card'

Takes about 10min

Then choose "reboot"

CWM asks you if you want to "fix root" select "yes"

Your tablet will now reboot and all is done

This works on a M5C5 unit 32GB running Mireks v7 ROM and the end result is of course this AOSP ROM v1.00 20151204
[Teclast X98 Air 3G] SkubiDoo:
What about storage on both devices? Are they the same?

From Xiaomi Mi4c Prime sent by Tapatalk
[Teclast X98 Air 3G] guvno:
Yes. Both my units were 32GB (single OS, Android) but one came with an old Teclast ROM full of bloatware, the other came with this new clean ROM that scores even higher in AnTuTu than Mireks v7 ROM. So both units are now running this new clean ROM (v1.00 20151204)
[Teclast X98 Air 3G] SkubiDoo:
So loook ;)

Can you see the difference?

Also on boot first I have old logo and then this orange Teclast

I will write here soon also the answers of adb commands

From Xiaomi Mi4c Prime sent by Tapatalk
[Teclast X98 Air 3G] :
well i believed when you told me first time... as i said i need the sizes of the partitions from the AOSP one in order to sync them in the rom
[Teclast X98 Air 3G] SkubiDoo:
I'm just doing this right now. I will edit this post soon

From Xiaomi Mi4c Prime sent by Tapatalk
[Teclast X98 Air 3G] guvno:
Ah. I see what you mean. Yes. The storages are slightly different it would seem. I will double check once I get home...

The other unit boots just like yours. First a chineese logo then it changes to the "orange" Teclast logo. Which is different from the first unit. I assume that could be due to a different BIOS
[Teclast X98 Air 3G] SkubiDoo:
Here you have it:

And how do you think are we able to dump this boot logo to be as in the first device or not? I will check BIOS versions and compare ;)
[Teclast X98 Air 3G] :
the first bootlogo has to do with the bios

ok, now do the same adb commands on the other device
[Teclast X98 Air 3G] guvno:
Compare the 2 BIOS versions. I beleive there is a way to backup a BIOS and then this can be flashed
[Teclast X98 Air 3G] :
ok, also this command on both devices

adb shell cat /sys/block/mmcblk0/size
[Teclast X98 Air 3G] SkubiDoo:
DONE! :)

It's true the first boot logo is about BIOS. I made backup and flash it by mirek tool ;)

Here you can find it: https://mega.nz/#!dYxVTQrL!J9h-bk-hWzE80UK2MSzRd2CBiAoYY8TF6XXr-JwpgdU

Just replace this file in \X98_Air_2_android_5.0_mirek190_v7.0\data\BIOS and run flash version 2.05

[MENTION=997923]ionioni[/MENTION]

Mirek v7 - 60620800

Org ASOP - 61079552
[Teclast X98 Air 3G] guvno:
Mireks flash tool has a way to backup and flash BIOS I beleive... But if anything goes wrong when flashing BIOS then it gets complicates... So beware
[Teclast X98 Air 3G] SkubiDoo:
As I wrote you before I've done it and it works :) just follow my instructions and than Mirek flashing tool ;)

Download boot file from my link and replace in mireks folder ;)
[Teclast X98 Air 3G] guvno:
Good stuff. Im ok my mobile so my posts are a bit late it would seem :)
[Teclast X98 Air 3G] :
well then, that's it, all the fixed sized partitions are having the exact same size

the difference in size of the 'data' is identical with the difference on the mmc0 devices, meaning that the mmc0 devices have different (available) space sizes. nothing to be done on increasing the mmc0 available size, that one is reported by the controlled in the mmc, and since 'data' is created at the end of partitioning operation whatever difference there is between the mmc's will propagate to it. could be useful to check with other (not AOSP) devices as if they are ok this means your is slowly going rogue

====================================================

X98 Air III(M5C5) - guvno.zip rom, updated batch with error checking and progress messages
[Teclast X98 Air 3G] SkubiDoo:
Well that's all I can do. Please guvno and the others check how it looks like in your devices.

Mirek flashing tool also have a tool to repartition device. There are many of partition.tbl files:

I can share those files with you.
[Teclast X98 Air 3G] guvno:
Also check for differences in emmc drive (HW) I heard that Teclast use different makes Hitachi, Samsung... etc. If they are different makes they are bound to be slightly different in size
[Teclast X98 Air 3G] SkubiDoo:
Hah true that's possible.. question is how to check it? Any ideas?
[Teclast X98 Air 3G] :
you don't understand... i don't need that (i can make you hundreds like that) if one wants to keep the fixed sized partitions identical with the ones in the AOSP device then that is the remaining space that 'data' has... however, if you want to rip off some space from another partition and give that to 'data' feel free to open the partition.tbl file and modify as you want, it really is trivial to do it, just read it a minute and you will understand (-b is the partition start sector and -s is the size in sectors, each sector holds 512 bytes)

===============

so that's it on this thread, someone should take the rom as i will probably delete it in a week or so

have fun soldering :)
[Teclast X98 Air 3G] guvno:
Easy in Windows... Not sure how to in Android... Must be an app for it or something... CPU-Z?
[Teclast X98 Air 3G] SkubiDoo:
Well for now I don't mind. It is as it is. Check on your device and let us know than we will investigate more maybe ;) It's not a huge difference and it's friday evening ! :D
[Teclast X98 Air 3G] Durete:
This app show you the emmc brand, and some other info.

https://play.google.com/store/apps/details?id=com.humanlogic.sdi

This is my emmc from my 4 weeks old MC5C. Probably one of the slowest emmc in the market actually [emoji20]

Enviado desde mi X98 Air III(M5C5) mediante Tapatalk
[Teclast X98 Air 3G] guvno:
Just thought I'd give my storage values as well:

The unit that came with the old ROM (now updated) is showing "Total space 26.62GB"

The unit that came with the new ROM (V1.00_20151204) is showing "Total space 25.24GB"

---------- Post added at 01:39 AM ---------- Previous post was at 01:05 AM ----------

Many thanks for all your help ionioni!

I never did try to flash your ROM from DNX mode, but I simply restored using CWM (hope that is ok) I also flashed the BIOS and the 2 units do seem to perform identically now...

Only thing I noticed is that the flashed unit still displays a Chinese logo initially which the other does not... Is there a flag or option in the BIOS that needs to be changed to disable this? I haven't got a USB keyboard so I can't get into the BIOS right now...
[Teclast X98 Air 3G] :
& [MENTION=5426693]SkubiDoo[/MENTION]

actually when saying 'to compare' i was meaning between exactly the same model and the whole mmc0 (because the 'data' size is computed dynamically at partitioning time and if for eg the same fixed sized partitions are having different sizes then of course it will result in different 'data' sizes even on a identical mmc0). also even on the same mmc model one can have different sizes due to different configuration of mmc at manuf time (over provision etc) so you must make sure your compare is made with models having the same hw revision.

but this is somehow the complicated way (and i already see that it does get that way by the posts already coming).

the best compare (from a practical point of view, since one cannot change the mmc0 available space, all he can do is to determine whether your mmc is healthy or not) is made when one checks the value of the mmc0 size of his tab at different times (after he flashes a rom that includes re creation of the gpt table) and only if he sees significant (increasing) difference on the mmc0 sizes can he say that the mmc started to fail (i doubt failing, even if an emmc is not even close to an ssd still it needs large amounts of data to be written/erased in order to start wearing out).

not to say that this is a 'it is what it is' situation and if i were you i would start 'using' the tab instead of seeking these kind of answers (seems to me like a waste of time)

as i already said, the rom flashing procedure seemed to me like the most 'usable'(familiar) one to the common user. sure, many other ways of deploying exist (for eg for my tab i have a restore script together with the compressed mmc and whenever i brick i just tap Install on the restore script and in 5 minutes i have whole mmc back to his good/known state) still a 'normal' user should be presented with the simplest way (one can of course 'customize' the flashing as he desires)

normally the initial logo is stored as a raw file (bmp in my YogaTab2) in the uefi firmware, you could try and extract your bios (it is compressed now) and check/search for the logos (but this one also means a 'complicated way') if you have the exact same bios you should also have the same logos, not so many storage places for that on a tab (tho some models used to store the logo on a dedicated partition on the emmc)