yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] rauliordache:
Lol......... why 2 versions of ,,7.0" on their website? (excuse me, probably 5.1 ahaha)
[Android Q&A, Help & Troubleshooting] Palm Trees:
There is a small difference in filesize.

Android Version 7.0(1) [552.95 MB]

Android Version 7.0(2) [557.84 MB]
[Android Q&A, Help & Troubleshooting] rauliordache:
After studying ,,hard", I can confirm that there are 2 versions of Android because there are two types of display:

1. From Samsung

2. From Huawei

Unfortunately, I don't know (atm) how cand we find our display model. But, there is a high probability that the problems with flickering (and all related problems) are due to the display models.

Obviously, we should ask Voyo's team.
[Android Q&A, Help & Troubleshooting] Goldi6:
Anyone tried it yet?
[Android Q&A, Help & Troubleshooting] RedMi92:
After flashing 7.0 rom (number 1, number 2 gives artifacts on the screen), i still have android 6.0 in system info. This is crazy
[Android Q&A, Help & Troubleshooting] kenryandub:
After flashing 7.0 rom ,

How to flash the Rom, please
[Android Q&A, Help & Troubleshooting] RedMi92:
You have to use spflashtool. Download the rom, extract it and use the scatter file oj spflashtool. This guide can help you https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
[Android Q&A, Help & Troubleshooting] rauliordache:
=== Instructions ===

Steps:

1. Rooting - file: https://dropapk.com/us2mra4pga2z

- necessary in order to perform a FULL BACKUP + a lot of other stuff

- for rooting, just install the NewKingRoot.apk. Allow installing unknown resources from Android settings (before this procedure)

- The first time, it will fail. The second time ("Retry rooting"), it will succeed.

- Restart the tablet. You will have King Root installed.

= It is not a must to try SUPER SU. It just depends on everyone's preferences.

2. TWRP - file https://drive.google.com/file/d/0B4TxwXoR2Nq3eXJxTFpFRkxlN28/view

- trying the custom Recovery.

a. Using fastboot (recommended):

- you will NOT flash this recovery into your device

- insted, you will boot into TWRP, in order to execute a FULL STOCK BACKUP (including stock recovery)

- Use adb to reboot into the bootloader

- Use fastboot to do an oem unlock

- Boot TWRP WITHOUT flashing (so it is safe!): "fastboot boot Voyo_Q101_TWRP_..img"

Then execute a FULL STOCK BACKUP (all files: original unmodifed bootloader, RECOVERY, etc.). Better on an SDCARD.

b. Flashing TWRP on the Device (recommended just after following a.):

- this will erase the original Recovery (backed up at a.)

- Use Flashify (or other tools)

- Turn off, Volume Down + Power for about 10 seconds:

i) if you have a Chinesse recovery, it is the stock recovery (something happened). Navigate at the end of the Chinese list, and select it (with power button).

ii) if you have TWRP ... bingo.

3. VOYO has sometimes GPS problems. Even if you have not, you can execute the following (after rooting):

- install MobileUncle/MT EPO from Google Play

- from Engineer Mode - AGPS - Hot - Full - AGPS restart

- Download EPO (with an Internet connection)

- You will have a better GPS signal (I hope :D, I've just followed these steps, not tested).

4. Now, waiting for a real Android 7.0 (those from VOYO's website are NOT 7.0 ...).

Do not try every custom ROM, even if you have a FULL STOCK BACKUP (from 2.a.), just wait for a good one.

I have made step 1 and step 3, today. Probably, backing up when a new ROM is available (the real Android 7.0).

By the way, is there is a difference (in terms of performance) between King Root and Super SU ?
[Android Q&A, Help & Troubleshooting] rockrider81:
Good instructions

Thank you

Maybe I say something wrong ...

How to load TWRP and ROOT?

1) Use SP FLashtools to load TWRP recovery (use original ROM scatter)

2) With TWRP do a FULL STOCK BACKUP and set it aside securely.

3) With the TWRP then upload SuperSU.zip

END
[Android Q&A, Help & Troubleshooting] rauliordache:
So, rooting is safe and mandatory in order to take other actions. Use KingNewRoot, run the apk from an Explorer (with "Allow unknown apps" in Settings)

Flashing the custom TWRP from the first time is a bad idea. Try just to boot into it (without flashing) - use a SDCARD or a connection with a PC. (adb)

After taking a backup of the stock recovery (chinese recovery, atm) you can (relatively) safely flash TWRP custom recovery. You can make a backup of the stock recovery with Flashify.

In general, take a backup of everything that will "change". Even if someone else has tried "something", be sure that you have a backup.

Any news about "Android 7.0" which is 5.1? :lol:
[Android Q&A, Help & Troubleshooting] murerlars:
Ordered it yesterday from Gearbest so let's see what I get. They still announce it with android 7.0:rolleyes:

They even answered a question from a customer that it's really android 7.0:silly:
[Android Q&A, Help & Troubleshooting] quack75:
The problem is not a number written 6,7,8 or everything else but API LEVEL 24 or 25 for Nougat. Someone reports API 22 and it is Lollipop Api[emoji20]

Inviato dal mio ASUS_Z00AD utilizzando Tapatalk
[Android Q&A, Help & Troubleshooting] rauliordache:
:( Any news about last firmware?

I have the july version (Android 5.1, API 22, advertised on that time as: ,,Android 6.0"). Any difference between this, and the new "Android 7.0"?
[Android Q&A, Help & Troubleshooting] mw210461:
All the Q101 4G that touted 'Android 6.0' in the boot screen were fakes: they all run on API_22 (Lollipop_MR1).

I have not seen the new 'Android 7.0' devices, but would NOT be surprised if these Voyo/TecLast creeps would continue their customer betrayal.

My last message here was apparently censored and disappeared, so I am asking again:

HOW CAN I CHANGE THE GENERIC SERIAL NUMBER ("01234567890ABCDEF") INTO A UNIQUE ONE?

None of the known tools like "DonkeyGuard", "XPrivacy" and "Serial Number Changer" work, all fail for different reasons.

I need a UNIQUE serial number as some apps require it or will not work. All Q101 4G seem to use the same fake number (surprise again).

There is a SN change script I found elsewhere, but it is written in a cryptic way. Can someone explain the exact process on how to apply it and what exactly to modify for a personal serial number?

Thanks!

"

adb shell

su

mount -o remount,rw /system

vi /system/etc/install-recovery.sh

# edit, save and exit

mount -o reount, ro /system

And here comes the line to add to /system/etc/install-recovery.sh to make the magic happen:

echo -n NEWSERIAL123 > /sys/class/android_usb/android0/iSerial

"

Any other ideas how to generate a new serial number that sticks or is injected during each boot?
[Android Q&A, Help & Troubleshooting] mc_seem:
The one I got from GearBest runs Nougat 7.0 NRD90M test-keys, kernel 3.18.35+ ll@server Tue Aug 29 12:39:15 CST 2017 , alps-mp-n0.mp1-V1.19_joyasz6753.65.5.n, baseband MOLY.LR9.W1444.MD.LWTG.MP.V117, 2017/06/29 ... I can post the full backup of stock ROM and partition layout to those in need.

Is there a custom LineageOS ROM for that?
[Android Q&A, Help & Troubleshooting] quack75:
Api level?

Inviato dal mio ASUS_Z00AD utilizzando Tapatalk
[Android Q&A, Help & Troubleshooting] rauliordache:
Wow? Are you sure sure sure sure, it is 7.0 ?
[Android Q&A, Help & Troubleshooting] mc_seem:
Yup. Clicking in the menu on Android version shows Nougat stock Easter egg app, not Marshmallow. And all of the UI is definitely nougat... Although the kernel build version is older, it seems... I messed up badly --- being unable to root it with KingRoot at all, I ended up doing "fastboot oem unlock" on it, bricking it in the process with a custom recovery after that. So the only way to recover it back was via MTK flash tool + the MTK USB COM driver. The firmware that is avail at Voyo site is Android 6.x :( ... for both i8 / q101 tablets, in fact some firmware file are even 5.0.1, not even 6.x ... the build keys on mine (which was clearly 7.x) - were also quite unique (not the same as Voyo's). Plus the build machine is different than that of a stock Voyo firmware.. So I ended up with Android 6.x, which is rootable... cool.. But since I kinda feel dumb now not backing up the scatter file and partitions with MTK flash_tool from 7.x, I ordered another device like this to properly back it up this time. One key difference between that one (that I had and lost) - it had Blue Voyo logo at boot. And if you do "fastboot oem unlock" it, it unlocks easily with Volume Down button. Then for each boot it is saying something like "Orange State... waiting 5 seconds before boot". Then after I reflashed it with Android "7" (so called 7 from web-site), I got back to 6.. And this time the bootrom is no longer unlocking - Vol Down button does not work :( ... and this time the bootrom stays locked - doesn't let me boot a custom recovery - saying "fastboot boot recovery.img" FAILED :( ... So I had it and I lost it all.... Without KingRoot working on this device w/ Nougat, it seems like someone with MTK flast_tool should go straight to fastboot oem unlock. Then read back the raw contents of it with flash_tool ... that's what I do in a week when replacement device arrives. I am not sure if fastboot oem unlock erases DRM keys on this device. If someone has one of these blue boot screen devices, can you publish the scatter.txt file and a backup of all partition.. I really feel dumb bricking it and having to roll back to 6. Spent all day searching for alternate scatter files on baidu and none of them are nougat.. :(
[Android Q&A, Help & Troubleshooting] PIxelPaws:
Hold the phone!

I meant to respond to this post yesterday, but was pulled away by something else, promising myself to return asap. While searching for this particular post, I overshot by one page so I've seen that it's already catching. I hope the answer to this that I'm about to post isn't redundant.

I just got mine last week, and only got to really start playing with it yesterday. When I opened the box, it has a card inside which reads:

"USEFUL REMINDER -- Dear customers, thank you very much for purchasing our products. Before you use it, please read the tips below:

A. When receiving the tablet but can not boot (word for word, folks) please use the standard parameters of the charger to charge the tablet PC about 2-3 hours.

B. If there is no charger included in product package, please purchase a charger that matches the product's charging parameters.

C. If the product shut down automatically because of power exhausted completely, please connect the standard charger and press the power key about 30 seconds, then you would charge it normally.

D. It takes long time for updating Windows, so you need to keep the power all the time and don't force to shut down. If the power is off during the update process, it will lead to system breakdown or other issues.

E. If WIFI, BT, touching function and other functions in windows can not be used, please contact our customer service to ask for driver software for installation.

F. The stated ROM which is in the listing shows the maximum available ROM with nothing installed. However, the OS and pre-installed software from the manufacturer will occupy some of this ROM. The available ROM on the device will therefore be slightly less than the ROM listed. (seems like it was news to them as well. Can you imagine THAT discussion?)

G. When the Windows system restarts after shutdown abnormally and you need to restore the latest correct configuration, please follow the instructions in the manual for recovery.*

*A quick look through the manual only suggests the settings>backup and reset>reset way, but they do mention (in several places) to 'format device' and do a reset as a solution to some problems, so I would take that to mean they have the ROM with the current running version stored on their site somewhere. I have mine configured with Android OS 7.0, which was a no-charge option installed on my device.
[Android Q&A, Help & Troubleshooting] PIxelPaws:
THIS.

I agree.

I feel that his time is NOT waisted by reporting this, I applaud his efforts and feel that not enough people mind being took 'if it's only a few bucks'.

Instead of thanking this guy for his efforts, you slam him for not having anything else to do? That attitude just plain sucks. It's an open invitation to sellers that we're ready to bend over and grab ankles any time, we've got something else to do.

If you knew how far this attitude has seeped into our society, you would indeed find yourself something better to do.
[Android Q&A, Help & Troubleshooting] Stoerner:
Hello,

maybe little bit OT:

Is there a way to build in a bigger battery and better speakers in this tablet ? As this Voyo tablet seems to be identical to my Teclast 98 I'm interested to improve battery and speakers.

In Internet I can not find any mods / instructions on this. What battery and speakers will fit ? Maybe you have links or hints how to do this.

Thank you very much for your help & best regards.

Edit: can I use Q101 Android 7 firmware also for Teclast 98 because they seem to have identical hardware ?
[Android Q&A, Help & Troubleshooting] mc_seem:
Do not try the one posted on official Voyo web-site! It is not 7. It is 6... although I attest that there is 7 available for that device already... wait for 7 to show up here.

According to 4pda.ru the two tablets (Voyo Q101 4G / Voyo i8) and (Teclast TPad 98 4G) are indeed the same identical generic MediaTek hardware - alps kt109. But there are two different Android 6.0 firmwares for Voyo for two different display types: one causes LCD flicker and GPU issues. And another one is fine. So it is hard to tell what firmware would work for you. You might want to wait for the dump of real Android 7.0 to show up. I'll post it here in a week when I get hold of a replacement tablet. You might want to try flashing Android 7.x using MTK Tools, previously backing up your current ROM, so that you can get back to stock if it won't work for you with Voyo Android 7.x firmware. I used official signed MTK tools (SP_Flash_Tool_v5.1628) with MediaTek DA USB VCOM + Preloader Driver 1/22/2016 (3.0.1504.0) to reflash it after I bricked mine, so I am no so afraid bricking mine anymore :) ... looks like it is recoverable in most cases using scatter file + ROM files + MTK_AllInOne_DA.bin ... the process is well described on YouTube. Be careful with MTK tools as it seems that some require turning digital signatures off.. it wasn't needed in my case. I run latest Win 10 with driver signature enabled and all the drivers are digitally signed (authentic MediaTek stuff with no trojans in the installer pkg).
[Android Q&A, Help & Troubleshooting] rauliordache:
I have some news (thanks to the Italian and Russian forums)

1. If anybody has 6924266911259 as the bar code for this VOYO Box, it is 99% sure that the tab has a Samsung display (not Huawei) - so use the second (2) offical ROM (which is still 5.1 Android), if needed.

2. Some russians have reported a big problem at the battery. It discharges smoothly from 100 to 50%, and then sharply (20 minutes) from 50 to 0%. And it seems is not a calibration problem ... I'll test tomorrow (use 3C Battery Monitor Widget + a FullHD 10hours Youtube video). 3C BMW will show us when each percent drops.

3. There is no Android 7.0 ROM yet (this is interesting as long as a colleague has reported an Android 7.0 version on this forum).
[Android Q&A, Help & Troubleshooting] Stoerner:
Oh, that´s bad. I was thinking bout bying a Q101 for the children. Thought that Voyo would be the better one instead of Teclast. But it seems that the T98 is not worst, except battery life. Maybe I can find other battery for T98 to mod it. Then it would be a good choice. It seems that those cheap tablets never get any firmware update and not at all Android 7.
[Android Q&A, Help & Troubleshooting] Palm Trees:
Why don't you buy Teclast P10? Great build quality, Android 7. And perhaps the best budget choice right now on the market.

Review (among many): https://www.youtube.com/watch?v=RYFu71_D5y4
[Android Q&A, Help & Troubleshooting] marek-x:
I'm waiting for Teclast 98 Octa Core Dual 4G Phablet - OLD VERSION SILVER WHITE 208107001 Android 6.0 MTK6753 2GB RAM 32GB ROM so it's very likely that I will find same problems with fake data sheet... not happy :(

---------- Post added at 12:51 AM ---------- Previous post was at 12:46 AM ----------

A budget choice? It's a joke? The price is at least x2 or x2.5 more.
[Android Q&A, Help & Troubleshooting] Palm Trees:
Notice I wrote the P10 not the T10. It's on sale for 115.99 USD (87.97 GBP).

And notice how the user asked for a budget-friendly, Android 7 tablet option.

Jokes on you, if you don't know where to buy it and/or use coupon codes ;)
[Android Q&A, Help & Troubleshooting] csagan5:
This is arm64 right? I wouldn't be surprised if it can run AOSP
[Android Q&A, Help & Troubleshooting] mc_seem:
Android 7.0 24 N

I got another Voyo Q101-4G tablet ... that is in addition to the other one I ended up soft-bricking and having to roll back to Android 6.0. The build on it is Android 7.0 (NRD90M) Nougat, API version 24.

joyasz6753_65_5_n:/ $ getprop | grep build
[ro.bootimage.build.date]: [2017σ╣┤ 08µ£ê 29µùÑ µÿƒµ£ƒΣ║î 11:02:40 CST]
[ro.bootimage.build.date.utc]: [1503975760]
[ro.bootimage.build.fingerprint]: [alps/full_joyasz6753_65_5_n/joyasz6753_65_5_n:7.0/NRD90M/1503975761:user/test-keys]
[ro.build.characteristics]: [tablet]
[ro.build.date]: [2017σ╣┤ 08µ£ê 29µùÑ µÿƒµ£ƒΣ║î 11:02:40 CST]
[ro.build.date.utc]: [1503975760]
[ro.build.description]: [full_joyasz6753_65_5_n-user 7.0 NRD90M 1503975761 test-keys]
[ro.build.display.id]: [NRD90M test-keys]
[ro.build.fingerprint]: [alps/full_joyasz6753_65_5_n/joyasz6753_65_5_n:7.0/NRD90M/1503975761:user/test-keys]
[ro.build.flavor]: [full_joyasz6753_65_5_n-user]
[ro.build.host]: [server]
[ro.build.id]: [NRD90M]
[ro.build.product]: [joyasz6753_65_5_n]
[ro.build.tags]: [test-keys]
[ro.build.type]: [user]
[ro.build.user]: [ll]
[ro.build.version.all_codenames]: [REL]
[ro.build.version.base_os]: []
[ro.build.version.codename]: [REL]
[ro.build.version.incremental]: [1503975761]
[ro.build.version.preview_sdk]: [0]
[ro.build.version.release]: [7.0]
[ro.build.version.sdk]: [24]
[ro.build.version.security_patch]: [2016-11-05]

I'll create the full SP Flash tool -flashable dump of all partitions today. Last time I tried - I didn't manage to easily root it on 7.0, but it is easily rootable on 6.0

Re. battery life --- my experience with this tablet on 6.0 was largely positive. I don't like the touch screen, it feels weird, but the display is alright otherwise. Battery life is good too (that is on 6.0 without SIM card). I'm using it as Remote Desktop with external bluetooth keyboard and mouse... Trying to measure now how long 7.0 would last with LTE SIM for casual use. 4pda doesn't seem to quote any 7.0 firmware for it , but mine runs 7.0 :)
[Android Q&A, Help & Troubleshooting] _PrEzi_:
I'll receive my Voyo soon too. Also marketed as "7.0" so I hope for the best. But it would be helpful to have a stock-ROM backup just for the sake of having it (then I wouldn't have any issues to just "play" a little bit and try to root it ;) )

So... eagerly waiting for your reply my friend :D
[Android Q&A, Help & Troubleshooting] mc_seem:
Here we go.. Android 7 Nougat - dump from my tablet, with re-created scatter file and all partitions backed up to proper format:

goo.gl/u6DJzh

goo.gl / u6DJzh

Sorry, I didn't bother packing system.img from raw, but it works great that way. It took a bit of time to figure this one out since the scatter file in this build has changed from stock f/w (bummer!).. So I ended up doing complete ROM backup in a single file. Then using gdisk to reconstruct the proper partition layout. Then splitting it into separate files, repacking ... and patching up the scatter file. In SP Flash tool - Choose [Firmware Upgrade] mode because the partition layout from Voyo Android 6.x to this Android 7.x build has changed. System partition has grew a tiny bit. So cache and userdata would have to be shifted. You'd lose all apps installed. Use at own risk. No warranties whatsoever.. Basically I managed to reclaim my 1st tablet back from Android 6 to Android 7 using this SP Flashable-dump, so it worked for me. I'll post pre-rooted system.img later when I have time for that... Basically --- do not try if you care about losing $99 . I didn't care much, whatever happens - happens.

In order for this upgrade to work, my tablet was running the official Voyo firmware (7.0-which-is-actually-6.0, the one that does not flicker on my display and the one with July-ish timestamp) --- must be installed first. Then power-down, Volume down, go into SP Flash mode, make sure you have MediaTek Drivers installed... of course launching the SP Flash tool in download (Firmware Upgrade) mode as usual... wait couple minutes and it's all upgraded to Nougat. First boot takes about 4-5 minutes, optimizing the apps (but it doesn't show anything on screen for that). Cheers,
[Android Q&A, Help & Troubleshooting] mc_seem:
Random facts about rooting on Android 7 image:

- although stock 6.0 firmware is easily rootable with KingRoot, 7.0 is not (I'd be happy to be wrong on that one, but I didn't manage to root it with KingRoot)

- preloader + boot image for 7.0 uses Verified Boot (dm-verity), so tinkering with system image renders device unbootable

- when device is unbootable, long press of reset button does not work - you'd have to wait for the battery to drain

- the battery connectors are soldered to motherboard, so you'd have to put extra load on VBAT to drain faster (that damn thing holds the charge for several hours, so if it locks-up - you have to wait a long time before you can get back to SP Flash mode again)

- Android 6.x image contains preloader where up-down volume buttons do not work for "fastboot oem unlock" command

- however, Android 7.x image preloader posted above - allows to perform "fastboot oem unlock".. after that the tablet remembers that it's unlocked and displays a warning on each boot

- reverting back to old preloader "resets" the unlock status, so you can relock it by reflashing stock preloader then back joya_sz preloader

- system.img contains a patch of recovery-from-boot , so it'd replace the custom recovery on boot

I am not sure if there is a command to disable verity on this device. So far it looks like the best route towards rooted N or LineageOS on it would be to start with prerooted 6.0 without dm-verity, maybe keep the more recent prebuilt kernel from 6.0 (not sure if MTK released the source for this platform?), then patch system image with 7.0 binaries and framework, thus keeping it without dm-verity... alternatively tinkering with preloader and oem keys should allow to reflash a custom set of testkeys, and re-signing the patched boot and system.

Just letting you guys know, if you try tinker with system.img - be ready for epic fail and waiting for the battery to drain slowly .. so that you can recover it back to bootable state via SP Flash tool. I find it unusual that the long press on reset button doesn't forcedly power-down this device.. also not sure why would someone enable dm-verity on a sub-$100 tablet, it's not like it's a BlackBerry Priv or something... sigh.
[Android Q&A, Help & Troubleshooting] Bib_x:
Can someone provide a picture of the place, where the usb cable is connected?

I want to buy this tablet and use it as smarthome-controller, directly fixed to the wall. So i need a white micro-usb-cable with an angled plug. I need to know, if this must be a right or left angled plug.

mc_seem wrote, the touchscreen is weird. Can you explain this further?

Will it react immediately? I only want to use this tablet with a web-based smarthome-control page and voip video telephony.