yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] santamanga:
Check out this post:

https://xdaforums.com/showpost.php?p=74286764&postcount=176

The right twrp you find in my post above as attachment.

Basically:

0. thoroughly read through this whole thread.

1. enable developer settings and in developer settings enable oem unlock. And enable usb debug mode.

2. install minimal adb and fastboot on your pc and the right drivers for mediatek 65XX/67XX.

3. connect to pc, go to fastboot in a terminal and use fastboot devices - it will not find the tab.

3. boot into fastboot: when device is turned off, hold vol - and power down. Try fastboot devices again, it will find your tab.

4. do the oem unlock as mentioned in the other post.

5. power off the device and let it erase whatever it wants to erase. And let it start up again.

6. enable the developer settings again and the debug mode.

7. copy the right su zipfile (and the recovery) to your sd card.

8. follow the linked post to flash the custom twrp recovery from fastboot. Or just boot into the recovery without flashing it, just for testing (instructions a few posts back!).

9. In recovery wipe data partition to be able to make a backup of your rom to sdcard. Flash su zip!

* don´t remember if dalvik needed to be deleted along the way
[Android Q&A, Help & Troubleshooting] starbright_:
Finally I ordered one too. It is described to have Android 7 and a battery of 6500mAh ?!? Curious what I will get finally.

Some devices stated 5000 has just 4000 if I look into earlierer posts of this thread.

Maybe they really have different kinds of hardware? Can remember that ony guy mentioned support of LTE band 20. Very strange altogether. And we have different kinds of displays.

Summary so far:

different batteries 5000 (real 4000), 5500, 6500 (in selling description)

different displays (Samsung, Huawei)

different basebands (check the available bands with the engineering code * # * # 3646633 # * # *)

different OS versions (Fake Android 6, Android 7)

Is this all mixed or do they have just two versions?
[Android Q&A, Help & Troubleshooting] santamanga:
[MENTION=2492996]starbright_[/MENTION]

My tab has only 2GB RAM, although it was advertised wrongly with 4. But I was very surprised to discover that LTE (Vodafone Germany) works.

Can't tell you about the batteries mAh.
[Android Q&A, Help & Troubleshooting] starbright_:
Woudn't it be best to cut the tempered glass to the size of the screen? Not sure how hard it is to do.

#########################################

New users probably get a tablet with Android 7. As a summery :

Reading a lot here the way to go is described here:

https://xdaforums.com/showpost.php?p=74286764&postcount=176

fastboot oem unlock

fastboot flash recovery recovery.img

adb sideload SR1-SuperSU-v2.82-SR1-20170608224931.zip

I think the step that is missed is to create an backup (just incase). But howto do this before flashing the recovery?

Did I have overseen this?

Is someone working on a custom rom or even lineage? I think on of the guys mentioned that he wants to start this.
[Android Q&A, Help & Troubleshooting] macrex:
Santamanga

Thank you very much for information finally I have root on the tablet.
[Android Q&A, Help & Troubleshooting] fabrik1964:
News on Android 7 for huawey screen?
[Android Q&A, Help & Troubleshooting] Serg-83:
Hello! People, does anyone have a modified file lk.bin from the post number 184? It looks like the file was deleted, if anyone has this file, then post it please.

P.S. Sorry for my English.
[Android Q&A, Help & Troubleshooting] santamanga:
[MENTION=1528995]mc_seem[/MENTION]

Could you please re-share the lk.bin and also explain if one can flash it from recovery? Thanks.
[Android Q&A, Help & Troubleshooting] xonnox:
I also would be very happy to get the lk.bin file.
[Android Q&A, Help & Troubleshooting] haseka:
Hello everybody,

in my search for informations how to update my "Android 6 - API22"-Q101 tablet i stumbled across this forum.

I today downloaded the actual Android 7-Update from Voyo's website.

Now after reading here that the update will only work for tablets with Samsung screens I am not sure what to do.

I opened build.prop file in my system folder and this is what I found:

ro.jty.version.release=KT109_MID-2016

So does anybody know if the screen is from Samsung or Huawei? Or maybe even another manufacturer?

Will the update work for my tablet?

Many thanks in advance :)
[Android Q&A, Help & Troubleshooting] m1steron:
I've managed to install Magisk Manager with root access on my q101 Android 7.0 with locked bootloader. All seems to be working fine. Does anyone want me to post a guide?
[Android Q&A, Help & Troubleshooting] santamanga:
I've installed xposed framework on mine with unlocked bootloader. But I'm sure people would appreciate your guide.

[MENTION=8871622]haseka[/MENTION]

I could not find any hint how to find out about your screen manufacturer.
[Android Q&A, Help & Troubleshooting] starbright_:
Got mine today. There is a strip: "Please peal of this mask".

Should I really do this or do I remove the protection foil with this?

For those who want to have a leightweight one: It is 530g, not 460g as advertised.
[Android Q&A, Help & Troubleshooting] starbright_:
Anyone knows how to get rid of the Screen-Shot Button at lower right corner? Can't find how to configure it .. ?!?

My one Android7 doesn't have this kind: The only shown ins:

ro.jty.def_launcher_pname=

ro.jty.def_launcher_cname=

ro.jty.camera_dummy_focus=enable

ro.jty.camera_preview_ratio=

Beside that it is stated as ro.product.model=Q101-4G

I found no indiciation what kind of screen is used.
[Android Q&A, Help & Troubleshooting] dondiasco:
wi fi problem with nougat

hi all.

I've a probelm with the Q101, with the nougat rom form voyo website when i connect to my wifi network it starts to go in bootloop, when the wifi is off i can use it without problem, could you pleae suggest me a solution?

I've seen that was post a nougat rom by mc_seem but unfortunally the link expired so i 'can't download his rom, someone could reupload it so i can try it out?

Thanks.
[Android Q&A, Help & Troubleshooting] newkid2k:
Yes. I'm waiting for your guide.

Thanks.
[Android Q&A, Help & Troubleshooting] starbright_:
Maybe this can help:

http://blog.andrsec.com/android/2016/03/26/android-verified-boot.html

For me the output is not the problem, but waiting another 5s is annoying.
[Android Q&A, Help & Troubleshooting] santamanga:
Maybe examining your logcat can help you find where it gets stuck.

https://logmatic.io/blog/a-how-to-guide-to-debugging-with-android-logcat/

Quick Google search:

https://amp.reddit.com/r/GalaxyS7/comments/6jzz4w/boot_loop_when_galaxy_s7_edge_has_wifi_turned_on/
[Android Q&A, Help & Troubleshooting] dondiasco:
Thanks, i've partially solved the problem and now I can use the q101. The problem, I don't know why, was the modem router I was using ( tp-link Archer vr600 with firmware updated). I tried to connect to the hotspot of my phone and it works, no more bootloop, so I tried with the home modem router which gave me my internet provider and it loos to work normally. The mistery unsolved is why it goes in bootlop only when connected to the tp-link router.
[Android Q&A, Help & Troubleshooting] starbright_:
So, as I received mine:

a) 6500mAh

b) til now : 6,5days : 35% battery usage - so around 0.2%/h

That is a good value (if the device is not suffered from a drop down in power as reported)

Are the newer Android 7.0 devices have this problem? - We will see.

c) no experience till now (will be updated)
[Android Q&A, Help & Troubleshooting] santamanga:
Does anyone have the bigger model with 3GB RAM?
[Android Q&A, Help & Troubleshooting] starbright_:
Could you (or someone else) find a solution? Cutting the screen to the real LCD size may be?

And finally does this glass improved the touch feeling?

[MENTION=4205274]santamanga[/MENTION]:

Til now I haven't seen any special offer for the 3GB Voyo - so it is not very attractive for the regular price (except it solves a real problem).
[Android Q&A, Help & Troubleshooting] fredlamour:
Yes please provide a guide. I would like to root my Q101 android 7.

Thanks.
[Android Q&A, Help & Troubleshooting] m1steron:
Install TWRP Recovery and Magisk Manager on Voyo Q101 4G Tablet

Hardware required:

USB cable

Micro SD Card

Software required:

TWRP Recovery (voyo_twrp_3_1_1-0_recovery_from_jemmini.zip): https://xdaforums.com/showpost.php?p=75116955&postcount=282

Latest firmware: http://en.myvoyo.com/xiazai/Win Pad/VOYO_Q101/down/

Latest Magisk Zip File: http://tiny.cc/latestmagisk

SP Flash Tool: https://spflashtool.com/

This guide is for advanced users who are comfortable using ADB/Flashtool commands, TWRP and SP Flashtool.

Before proceeding make sure you have Android ADB & relevant device drivers installed on your system. Use XDA to find out more.

I take no responsibility if you brick your device!

If you are already on Android 7.0 (2017-12-27) please skip to step 6.

My Problem:

Followed a guide in this thread and entered a bootloop as I forgot to flash Supersu so I did the following:

Warning: This process will wipe all of your data!

1. Downloaded & unzipped the latest firmware from Voyo site (Android 7.0 2017-12-27)

2. Start SP Flash Tool and selected "Format All + Download" from the drop-down menu.

3. Selected the Scatter-loading file "MT6753_Android_scatter.txt" from the unzipped firmware folder.

4. Clicked the "Download" button then connected the tablet via USB in a powered off state. The tablet will startup and begin the flash.

5. Wait for the flash to finish, disconnect the USB cable and press the power button to reboot.

6. Once booted enable the "Developer options" by tapping on the "Build number" several times in the "About Phone" section of the settings menu.

Enter Developer options and enable the "OEM Unlocking & USB Debugging"

7. Back in settings click on security and enable "Unknown sources"

7. Reboot in to Fastboot using ABD. Alternatively, shutdown the tablet then hold the "Volume Up" button whilst re-connecting the USB cable. This will bring up the Boot menu. From here select 'Fastboot mode".

8. Copy the extracted TWRP image to your ABD folder and rename it "recovery.img". Open a CMD prompt and input the following commands:

fastboot oem unlock

On the tablet select to option to unlock the bootloader

Then this:

fastboot flash recovery recovery.img

Next step is optional:

fastboot oem lock

This will allow you to lock the bootloader and prevent the annoying warning that pops up during boot.

Then press and hold the volume up button whilst issuing this command:

fastboot reboot

Select Recovery mode

TWRP Recovery

1. This will load TWRP, change language to English and tap Cancel if it asks you to enter a password.

2. Swipe to allow Modifications

3. Tap Wipe >> Advanced Wipe >> Data >> Swipe to Wipe

4. Insert your Micro SD card with the Magisk zip copied to it, mount it and install the zip file >> Wipe cache/dalvik >> reboot system.

Tap "Do Not Install" and wait for the tablet to restart.

Viola, you now have root access through Magisk Manager.

Compiled from various sources in this and other forums.

Thanks to Santamanga, Vertycall for the fastboot commands and the Magisk team for their awesome work.
[Android Q&A, Help & Troubleshooting] fredlamour:
Thanks [MENTION=8052006]m1steron[/MENTION] for this guide.

Must we use Magisk or can we replace by SuperSu ?
[Android Q&A, Help & Troubleshooting] m1steron:
Yes it should work but can't remember if I tested it or not.

Substitute the Magisk.zip for SuperSu.
[Android Q&A, Help & Troubleshooting] newkid2k:
[MENTION=8052006]m1steron[/MENTION]

Thanks for your guide. It's work.
[Android Q&A, Help & Troubleshooting] fredlamour:
Hi,

Using the guide, I have unlocked, flashed TWRP, flashed SuperSU but then I was in a bootloop into TWRP. Tried to flash MAgisk over the top but not better.

So I used the guide again to flash ROM using SP Flash Tool. That worked but then it stop with the Android text after 2 min and reboot again.

Retried to flash full ROM without getting a better result.

Any idea to help solving ?
[Android Q&A, Help & Troubleshooting] santamanga:
Which software and recovery are you at now?
[Android Q&A, Help & Troubleshooting] fredlamour:
I was with a release 7 of Android (the true Android 7) and use the full ROM available on the voyo website.

I used those links from the previous guide :

Software required:

TWRP Recovery (voyo_twrp_3_1_1-0_recovery_from_jemmini.zip): https://xdaforums.com/sho...&postcount=282

Latest firmware: http://en.myvoyo.com/xiazai/Win Pad/VOYO_Q101/down/

Latest Magisk Zip File: http://tiny.cc/latestmagisk

SP Flash Tool: https://spflashtool.com/
[Android Q&A, Help & Troubleshooting] starbright_:
Does someone of you have experience with anti-reflexive / matte screen protection for this device? Source for it?

It doesn't have to fit perfect for the Voyo, as the front cam is not of importance for me, but the reflections are annoying (at least if you have once used it with anti-reflective surface.)
[Android Q&A, Help & Troubleshooting] lakeconstance78:
Good morning,

I would like to say thank you for the instructions to root this cheap, but good device, especially [MENTION=8052006]m1steron[/MENTION].

Before the device was very slow and I there was a bug with display of the battery level.

After re-flashing of Android 7 and rooting almost everything is perfect.

But there is still one issue: The Speaker Sound

The sound is not very loud and clear. Sometimes it is crackeling.

Anybody solved this?

Thank you so much.

Ben.
[Android Q&A, Help & Troubleshooting] rauliordache:
Are you sure? Everyone has the bug with battery level, even after root .... It is a firmware bug...
[Android Q&A, Help & Troubleshooting] lakeconstance78:
Mh... I think yes. After I rooted the Q101 I charged it from around 50% to 100% uns used it to 60%.

Before I root the charging level goes

sometimes

only to 86% and after a couple of hours it shows 1%.

I will try it again today and will measure my capacity of the battery.
[Android Q&A, Help & Troubleshooting] starbright_:
As I received it (Android7 preinstalled) I charged it completly and let it run dry in flight mode. It takes around 18 days to be at 20% (BBS shows 0.2%/h) - without any bigger drop downs. So my assumption was, battery and calculation of its state is ok.

Yesterday I go to sleep with around 40..50% battery and get this low power alarm at night. Not amused about this wake up call!

Charging it, it seems very rapidly go from around 20% to 50%. But I didn't watched at it whole time.

Beside that: The Launcher is rather low featured or I am to blind. I can't set a homescreen, get rid of this screenshot buttom and place widgets ?!? Can't believe!
[Android Q&A, Help & Troubleshooting] lakeconstance78:
Good morning everyone,

yesterday I drained the battery to 0% until the device is not starting anymore.

I plugged in my "measuring-device" and started to charge it. After a couple of seconds it shows 53% and after 4 hours it shows 98%...and not charging to 100% over night....

The capacity of the battery is only arround 3400 mAh. I will test it again another time.

Have a nice day.

Ben.
[Android Q&A, Help & Troubleshooting] starbright_:
When did you get your device and what Android version was originally installed?
[Android Q&A, Help & Troubleshooting] santamanga:
Yes. That screenshot button is annoying.
[Android Q&A, Help & Troubleshooting] lakeconstance78:
I got my device in September 2017 from Gearbest with Android 7.0
[Android Q&A, Help & Troubleshooting] rauliordache:
The problem is not the capacity, for me. It could be 3000 mAh but a good quality of battery + Android firmware. What happened today (and yesterday)?

I wanted to test the battery. I have used Waze (which is a good battery drainer :lol: ), + 50% brightness, in a 12 hours train-trip (AC charge, 220V). Conclusions:

1. With the stock charger (5V, 2A), from 4300mV, the voltage dropped until 3900mV in 4 hours but the % from Android showed around 98-99-100%. After another 2 hours of normal usage - around "70%" it(Android) said, 3.7V. The consequences?

2. Today, after powering on: 17%. The "real" capacity. Really? Not so. It was around 2% because the tablet powered off in 10 minutes.

So?....

3. Yesterday, at "70%" it was almost 0%. Futhermore, when using a high-power-consumpting(HPC) application (like Waze) combined with charging (AC 220V) we can end up with a "99%" battery after 3-4 hours, which in reality is 5%. And a sudden power off in the middle of Wien, Paris or Rome (in case of the ,,in car-charging,,).

4. I hope that a good quality charger (2.1A/5V) will maintain a constant voltage and will cover the dirty, f*cking battery and firmware. I don't want to "fill it" (when using Waze). Just to keep the load ...

This is my story....

And I don't think that rooting is a solution. Maybe changing the battery or the firmware? Don't know.

You can try:

1. Install 3C Battery Monitor, Waze. Plug in the charger (you should already have 100%).

2. Open both, + location (GPS), without Internet (you don't need to waste it). Just open Waze at 50% brigthness, and keep it in front (for 2-3-4 hours). Then, look at the 3C Battery history....

It's not a problem if the charger cannot supply enough energy. But show itttt to us, f*cking Android Chinesse firmware!!! Do not modify the firmware in order to show 99%, while the battery is continuing discharging!! (highlighted by the voltage in 3C Battery Mon)
[Android Q&A, Help & Troubleshooting] fredlamour:
Here is a video of the bootloop : https://youtu.be/851i2OmU4tI

[YOUTUBE]https://youtu.be/851i2OmU4tI[/YOUTUBE]
[Android Q&A, Help & Troubleshooting] santamanga:
In your video, there is no unlocked bootloader warning at the beginning.

So I guess you also don't have twrp installed. You can boot into recovery?

And there delete cache or whatever to see if it helps with the loop?

Also, since your tablet only reboots after your screen glitch, I guess the rom you installed doesn't work with your display, which might be from Huawei.

See for example posts from 2. Januar 2018
[Android Q&A, Help & Troubleshooting] lakeconstance78:
Hello :)

after a few loops I am very desperate about one big problem and one smaller problem.

The bigger problem is, that I have lost my IMEIs, after my first flash. I tried a lot of tools, MTK enginieer mode and to set the IMEI via ADB.

Any ideas?

My smaller problem is, that the speaker is crackeling and not very loud.

Thanks for your support.

Ben.
[Android Q&A, Help & Troubleshooting] fredlamour:
Hi Santamanga,

I can enter the recovery menu with chinese words. I did a clear memory and emmc and it rebooted but still same issue.

Where can I get a huawei screen rom I can upload with SPFlash tool ?

Thanks
[Android Q&A, Help & Troubleshooting] starbright_:
That is really annoying. I have mixed results here. After fully charged it I let it untouched in flightmode and get a contionous low drain of 0,2%h til 20% in more than 2 weeks. So I thought it is ok and working. But once I get a wake up call from "low battery" while it has few hours before 60% and has'nt been used.

I'll not use it as often, but have to repeat some test.

BTW: can this battery warning or shut down notification sound disabled ?

Does someone here as good russian language knowledge and can inform us about whats going one in that forum. I think it is more active that this here :(
[Android Q&A, Help & Troubleshooting] chan200606:
The usual methods including those using engineer mode work only when the tablet is running "Android 6" (really lollipop) but don't with the latest 7.0 firmware.

If you can still find a copy of mc_seem's rom dump you could "use" his IMEI by flashing the other files in the dump that are not normally included in the flash (you have to manually change the scatter.txt file). Not sure if this causes any conflict though if you happen to be on the same network as he is.

Or you can try the new tools posted on voyo's Chinese site (see my post at https://xdaforums.com/showthread.php?t=3634517&p=74943571) which apparently can be used to write IMEI and other things to the tablet. Let us know if they work for you!
[Android Q&A, Help & Troubleshooting] santamanga:
Hi. Maybe try the image from this thread from 25th of August posts, but maybe also read via google translate through the Russian pda website how it should be flashed.
[Android Q&A, Help & Troubleshooting] lakeconstance78:
Thanks for that helpful hint! Will try it tonight....

Ben.
[Android Q&A, Help & Troubleshooting] rauliordache:
I also try to talk on the 4pda forum about these problems.

All in all, I don't know if the wrong % display is:

- a battery problem (despite the fact that it has a good capacity, around 5-6 hours with 3G, around 7-8 hours without)

- a firmware problem (the chinesse people excel at tricks/modifications and why not at lies)

The real problem is that we don't know when the battery is full, half-full, etc. and voltage monitoring is just an emergency index...

1. The general behavior is: Linear discharge from 100-40% (around 5:50 hours), and a huge drop from 40%-15%-1 (in 10 minutes). We can just estimate the real capacity by voltage: 4.2-4.3V means 100%, 3.7V means around 5%. BUT:

2. I also encountered another strange behavior: This time, while charging in car, with Waze +3G+GPS+ 100% brightness. Besides the fact that ,,charging" or at least maintaining the initial load is not achieved, after 1 hour of using, the OS reported 99% with a 3.8V. Which is unbelievable. It was around 25-30%.

So, after 2 hours of using (in car), I can expect a full shutdown, in the middle of the road, with a ,,99%" status...
[Android Q&A, Help & Troubleshooting] GMPX21:
My Q101 was shipped with Android 7 but a version prior to the 2017-12-27 build, is it possible just to update to that Dec 2017 version without wiping everything?

And what does that 2017-12-27 build bring to the table? Later security patches etc?

Cheers.
[Android Q&A, Help & Troubleshooting] santamanga:
I think, If you already have the real android 7.0, then it's the same as the later officially released image.
[Android Q&A, Help & Troubleshooting] cermi:
Hi all...

i have flashed my Q101 with the firmware from the Yovo Website ..

but now i have a bootloop... Yovo Screen - Android Screen... stuck - fragments - new start - everything again..

do you have any idea?

thx
[Android Q&A, Help & Troubleshooting] santamanga:
Hi. Maybe try the image from this thread from 25th of August posts, but maybe also read via google translate through the Russian pda website how it should be flashed.

Read a bit higher, s.o. has the same problem as you. Some tablets not sold with 7.0 are in fact incompatible to the image from the website, because they have a screen from Huawei and not Samsung. That might be the case with yours. It's all in this thread mentioned.
[Android Q&A, Help & Troubleshooting] cermi:
thx...

i have bought the tablet 2 weeks ago...

today is my first day with the yovo... and now... :D
[Android Q&A, Help & Troubleshooting] fredlamour:
I am in the same case.

I have downloaded another rom from the post of 25th august but it fails when opening the scatter file with SP flash tool.

Please, let me know if you find a solution.
[Android Q&A, Help & Troubleshooting] cermi:
i've tried 3 different roms... same problem...
[Android Q&A, Help & Troubleshooting] cptwhite:
Ignore video title, this also fixed the boot loop issue I had with my Voyo i8 plus...

My video guide here, I'm no expert so apologise it's very amateur

youtube . com /watch?v=Dcdv_PmmRgY

You will need to Q101 ROM from here

http://en.myvoyo.com/xiazai/Win Pad/VOYO_Q101/down/

Not sure if the same MediaTek drivers will work - might be just getting confirmation from others here before attempting, but this is the general process at least, hope it's of use.

Edit: Tablet specs seem very similar - Arm Cortex A-53 CPU, so I expect probably the same hardware / drivers. Check Voyo website and you will see.