Hi all,
I recently got hold of one of these OTT M8S boxes and have been banging my head against a wall ever since then. My ultimate objective is to load Openelec onto this and be done. The Android Firmware it comes with is flaky - especially on MPEG2 content (which is amazing considering how well the Pi Zero does with that content).
Trouble is the Firmware that mine came with has no functional recovery partition. Eventually I loaded a new firmware with a recovery using USB_Burning_tool using a stock .img . This image didn't have my WIFI support so I upgraded it using another zip file and the stock recovery method. This went fine, but really I was no nearer my goal since the new recovery firmware has built in signature checking and will only allow firmwares in the same series to be loaded. It seems that this has become a standard feature of all the firmware for these boxes now coming out. So there is no pathway to loading TWRP or Openelec using the standard Firmware - but it won't allow you to break out of the standard firmware signature checking. Deadend !!!
I attempted to dd a functioning TWRP onto the box using shell emulator, but this simply broke the recovery. This suggests that this issue is deeper than just the way the recovery is setup, it suggests that the issue is with the second bootloader (u-boot.ini) which seems to have signature checking built in as well. So no longer can you pick any functioning u-boot.ini file and make a bootable SD-card with Amlogics SDcardMaker.
Fairly locked down altogether, and it would seem that this feature is going to proliferate to all of these boxes since they are all using variants of the same basic Android ROM, which I suspect is issued by AMlogic themselves.
It seems to me that the only way forward is to create alternative ROMS such as Openelec as pure .img files which can be loaded at the raw NAND level using USB_Burning_Tool. None of the developers seem to be addressing this, simply repeating the old approaches which no longer work on these new generation boxes.
A lot of people are thrashing around and bricking their boxes and without a functioning recovery partition these become defacto hard bricks.
So I make a call out for the developers of the unofficial Openelec firmwares to package them as raw .img files rather than OTA zip files which can no longer be sideloaded.
Maybe someone reading this with a functioning Openelec M8S S812 box can do a dd dump and post up a .img file for me to burn into my box. Please.
Stephen
I attempted to use USB_Burning_Tool to burn an Openelec Wetek Core .img file and the program wouldn't pass it. So it seems that not even this is a suitable method of bypassing the bootloaders.
Stephen
However here is a heads up for anyone out there struggling to get a decent performance from their Kodi. I have just loaded up my box with the Wetek Core Kodi 15.2 and I can report that out of the box it solves almost all of the Amlogic codec issues people have been facing and runs all three hardware acceleration tabs. On Tvheadend PVR playback it occassionally does a black screen on channel switches and can be very slow to switch channels, but if you switch channels again and then back to the black screen channel it usually comes back. no stuttering or audio lag what so ever. Can be found here:
http://wetekforums.com/v/index.php?...-2-to-fix-23-976fps-video-sync-issues?p=23662
Here is an interesting quote from the users of this Kodi version, which suggests that the Kodi developers know what the issue are but refuse to address them, I suppose they hate these "pirate boxes" that much :
Blame Kodi for this. By default mpeg4 / divx is not Hardware accelerated. I'm not sure what WeTek did with this version, they may or may not have patched it to re-enable Hardware accelerated mpeg 4 / divx for the Core.
Try playing with the Video > Playback > Hardware acceleration options.
The Android Kodi devs know about this problem and refuse to change what is distributed by default.
Note other Kodi issues on AML.
mpeg2 in .vob files will not play in Kodi on ANY AMLogic platform, they stutter.
Click to expand...
Click to collapse
If I had to factor in my time to the cost of this box, the WETEK core starts to look a very cheap deal.
Stephen
I went back to this on a hunch and downgraded my Firmware to cyx_m8s_ap6330_8g2g_150728_SD.rar
this ROM has fully functioning recovery and it Flashes Openelec upgrade ROM by default with the toothpick method. So I tried as many different versions of Openelec for M8S as I could find and the sad news is that they all soft brick my box with the M8 v8_8 board. They all reproduce the same behaviour of preventing the box from booting and no Blue light on power up. Fortunately USB_Burning tool version 2.0.5.13 recovers the box without difficulty (though it usually takes two tries to get it past 3%).
It is my conclusion at this point in time that there is no functional Openelec available for this version of the board.
Stephen
Working TWRP?
Shoog03 said:
I went back to this on a hunch and downgraded my Firmware to cyx_m8s_ap6330_8g2g_150728_SD.rar
this ROM has fully functioning recovery and it Flashes Openelec upgrade ROM by default with the toothpick method. So I tried as many different versions of Openelec for M8S as I could find and the sad news is that they all soft brick my box with the M8 v8_8 board. They all reproduce the same behaviour of preventing the box from booting and no Blue light on power up. Fortunately USB_Burning tool version 2.0.5.13 recovers the box without difficulty (though it usually takes two tries to get it past 3%).
It is my conclusion at this point in time that there is no functional Openelec available for this version of the board.
Stephen
Click to expand...
Click to collapse
I worked with Abdul over on this forum and he was able to port a OTT S812 2G/8G M8 4335 TWRP which might work for your box. It was for my M8 v8_6 box. I tried all other TWRPs and they didn't work. I was his guinea pig and this result works great
If you go to the Freaktab dot com forum and look into the "TWRP for Amlogic devices" folder (which is under the "AMLogic based TV Players" folder, go to message 900 and you'll see a link to a TWRP recovery which may work on your machine.
I cannot post the URL due to rules in this website to prevent spam.
Hope it helps you.
Thanks a lot, that TWRP works very well off of a SD-Card.
It also successful boot into TWRP recovery on my box.
Finally some progress and the possibility of loading Openelec open's up.
Cheers.
Stephen
I attempted to use my new power of TWRP to flash a WETEK-Core Openelec development OTA. The result was a soft brick again.
However TWRP opens up new possibilities since I can now flash my Openelec image and then flash the bootloader from a stock rom - since I believe it is the bootloader packaged with Openelec which causes it to soft brick.
Will report back if I am successful.
Update: this strategy still produces a soft brick so the problem must run deeper than the Bootloader.
Maybe you could persuade Abdul to express an opinion on why Openelec soft bricks these boxes as I am sure he would have a good understanding of what was going wrong at the boot sequence.
Stephen
So good news folks. I have manged to get openelec loaded onto my box and its working fine.
My method was to use BootCardMaker and to load onto it the u boot.ini file from my second stock ROM.
I then placed the same u boot.ini file into the root of the same SD-card and then unzipped the image "OpenELEC-Amlogic.arm-M8S-6.0.0.2.zip" into the SD-card root (which I believe I got from the WETEK site). All seem to work fine out of the box and HD works fine. It still has lip sink issues when handling streamed MPEG4 content - but it is definitely using the built in amcodec hardware decoding. Last thing to do is to replace the recovery with the working TWRP and make a full backup of the configured system.
So the issue with all the other builds of Openelec was an incompatible u boot.bin
Openelec is a lot more snappy in the interface than Kodi as an Android app, which is really noticeable when using the crappy remote it came bundled with.
Last thing to check is if the Amcodec has the same zoomed screen issue when outputting composite that exists in the Android version. Hope not.
I can now reload either the working Android or the Openelec using TWRP which is great.
Update: It appears at first glance that this build has no AV support at all.
Stephen
Hi firstly thank you i managed to get twrp on my OTT M8s following your instructions with the link to post 900~
Now i have made a complete backup of my rom but when i try to update a different rom it always reloads my original rom - It goes through the updating apps process but is always my stock rom
Now when i say stock rom that is a bit of a lie, i bricked this box within 20 mins of getting it and had to find a compatible rom, i ended up having to use the usb flashing tool and shorting out pins 28 and 29
there is a problem in the recovery/bootloader/u.boot bin somewhere that will not let me update the firmware
I am currently on a ap6330 but have had it on bcm4335 previously (go figure)
Also when i tried to update it to the latest acemax firmware last night it said 'this rom is for n200c and this box is k200 etc' but CPUZ clearly states my box is a n200c (again go figure)
I am by no means an expert on the file system of Android as a whole but am pretty experienced in flashing roms/cyanogenmod/xposed/twrp etc
Getting twrp running is a small achievement in itself....
It seems that the stock recovery process for installing OTA's checks signatures and will not allow "incompatible" ROM's to be flashed. The only way to get a ROM on there would be to find a full TWRP backup of that ROM and sidestep the standard recovery process.
I am still having issues with mine in that now that I have a working version of Openelec 6.0.0.2 it will not allow me to use the standard method of installing Openelec to downgrade to the 5.95.5 version. I am very happy with the way that Openelec performs, but without AV output it is a dead duck for me.
Looks like it was a wise move to do a full TWRP backup of the Android system as it seems that is the way I am going.
Stephen
Hi Stephen
Yes been trying to update and continually getting the E:error executing updater binary in zip
Could i take the meta-inf file from my working rom and swap it out?
I am not familiar with the more complicated stuff :/
See this comment by abdul in another forum:
On newer versions i have changed device id to k200. What device do you have ? I don't recall having made a TWRP for the MXQ.
That check is made by the update-script inside the flashable zip, I DID NOT MAKE IT CHECK. And "toggle signature verification" is there but it's not related to this.
Just delete the assert in update-script or use a newer version
I have been messing about with some roms and now i cannot restore my backup:/
E: unable to mount storage
Got a feeling i am going to have to start from scratch with usb burning tool
USB Burn tool will generally solve most issues. Only once or twice did it fail to find my Box and then the NAND shorting trick sorted that out.
Stephen
Shoog03 said:
So good news folks. I have manged to get openelec loaded onto my box and its working fine.
My method was to use BootCardMaker and to load onto it the u boot.ini file from my second stock ROM.
I then placed the same u boot.ini file into the root of the same SD-card and then unzipped the image "OpenELEC-Amlogic.arm-M8S-6.0.0.2.zip" into the SD-card root (which I believe I got from the WETEK site). All seem to work fine out of the box and HD works fine. It still has lip sink issues when handling streamed MPEG4 content - but it is definitely using the built in amcodec hardware decoding. Last thing to do is to replace the recovery with the working TWRP and make a full backup of the configured system.
So the issue with all the other builds of Openelec was an incompatible u boot.bin
Openelec is a lot more snappy in the interface than Kodi as an Android app, which is really noticeable when using the crappy remote it came bundled with.
Last thing to check is if the Amcodec has the same zoomed screen issue when outputting composite that exists in the Android version. Hope not.
I can now reload either the working Android or the Openelec using TWRP which is great.
Update: It appears at first glance that this build has no AV support at all.
Stephen
Click to expand...
Click to collapse
I have the exact same PCB board M8 V8_8 and am also trying without success to get openelec running on it. Can you please explain the steps and firmwares you were using please and thank you - you are a god to me right now lol
I got the openelec file from the the VectorDroid website where i grabbed the file "OpenELEC-Amlogic.arm-M8S-6.0.0.2.zip" from their download section.
I grabbed Amlogics Bootcard maker from Chinesegadget Reviews. This runs in Windows, but I had no problem using it in VirtualBox running Win7.
I extracted the file "u boot.bin" from the stock ROM "cyx_m8s_v8.6_bcm4335_8g2g_kodi_addons_151013_SD##.rar" (hash represent chinese letters). This is the most critical part since this is the layer which points Openelec to all of the available hardware. Use Bootcard maker to burn this file into a SD_card, and then for good measure add it into the root by a simple file transfer.
Copy the Openelec file into the SD cards root, and then extract it into the root.
The SD card should now be setup and ready to roll. However it will depend on the recovery setup that you have on your box. I cannot remember at this stage whether I used the stock ROM's "cyx_m8s_ap6330_8g2g_150728_SD升级.rar" or "cyx_m8s_v8.6_bcm4335_8g2g_kodi_addons_151013_SD升级.rar" to boot into recovery. My gut feeling at this stage is that the ap6330 has a less secure recovery partition and will recognise the Openelec card better than the bcm4335.
If you have the correct recovery img from the correct ROM it will boot into Openelec via Android stock Recovery and flash the files to you box. Give it at least 15mins as the screen is likely to go blank. Take out the SD card and reboot.
I used TWRP to back up my stock ROM and Kodi setup before I did all this, but if you decide to do this (a good idea) you will need to reload the STOCK ROMs recovery img using TWRP before you can get Openelec to boot since it uses a functional unlocked down version of Android recovery to do the flash.
If this fails to create a working box it will most likely brick your device, but its a simple matter to reflash the "cyx_m8s_ap6330_8g2g_150728_SD升级.rar" ROM using USB_Flash_Tool and start all over again !!
Hope that works for you.
Stephen
Good to know that a change to openelec can brick it because i tried to install
it. I like more the wetek stuff but my box is cheap chinese trash where the
ota-update have a failure.
Well, it's working but the pvr will not work (said no connection but 127.0.0.1
is already set and ports open in my modem...), and a settop box without the
ability to look tv or streams is useless.
any suggestions how to bring the pvr to work? Os is Kodi 15.2 bc jarvis
refused to run on this box.
Most of the versions of Kodi you get bundled with these packages have got no installed PVR support and no release candidates. They are sold purely as streaming candidates.
The only way to get round this is to completely remove the Kodi version and reinstall it from scratch. This will lose all the preconfigured Addons but most of them are useless anyway. Get a release candidate from the Google Play store or from Kodi Foundation and this should either have PVR support built in or should have a release candidate. Its important to get the right PVR support otherwise it will fail to load the dll of the addon and will report as broken. I had the self same problem with my Kodi version on my Opensuse Linux box and solved it by making sure that both the Kodi build and the PVR build came from the same source. Its not really a Kodi problem and you will get no help from their forums.
Stephen
"Most are useless anyway", so right. I tried to install the wetek firmware
(device is rooted) but it seems this chinese counterfeits miss a lot of
system settings ....change thru twrp and uboot-button also failed.
I'm clueless what to do.
Mine settled down quite nicely in the end. I could be running Openelec if it had AV plug support. As it is I settled for nothing fancy - but a version of KITKAT firmware with a fresh install of Kodi from the Google Playstore, has been working OK for months. Any of the WETEK ROMs are likely to be unsatisfactory. Go back to the post where I point out the specific two ROM's which worked for me and use the ROM burning tool from Amlogic. There is very little to be gained by trying to get anything more complex working.
Stephen
lost finding right firmware
please dont be mad if i did something wrong in this forum i have never post before or subscribe on any forum but here i am very confused with my box (sorry no picture) but here are the spec as a friend opened it once for me :
m8s box from ott (M8S on the top and the sticker on the bottom of the box)
inside amlogic s802b and wifi 6330
connect succes with usb burning tool
didnt find the right firmware, the only one that worked had no wifi no bluetooth and remote issue (with color button) i tried several firmware but invain, your are my last hope,
not looking for openlec, just an android rom sorry again and thanks in advance
Related
Welcome to my tutorial !
You can find others tutorials related to the Cube i6 :
Install windows 10
Install Android 4.4.4 (Stock & RemixOS)
I received the magnificent AllDoCube i6 Air 3G last week, and i've been struggling since to get updates,
firmware flashing and all of that working, I searched the whole web and the drivers/Firmwares are nowhere to find,
but on some chinese proxy-needed sites sometimes, or baidu which is a pain in the a** to download from.
So I decided to share the ways to update this tablet at all costs (heh, no worries, -NORMALLY- it wont brick)
Disclamer: This process might contain ROM hacking, this is for advanced users.
THIS TUTORIAL HAS BEEN TESTED ON i632GB1537XXXXXXX MODEL, AND WORKS ON IT,
WHEREAS IT HAS BEEN REPORTED THAT i632GB1522XXXXXXX MODEL BRICKED UPON DOING IT,
SO PLASE DO IT CAREFULLY, IF THE INSTALL VERSION IS 202 YOU SHOULD THINK ABOUT IT BEFORE TRIYING AS IT COULD BRICK!
Software included may be subject to copyright.
Flash your device at your own risk. Developer is not responsible for what you do on your device.
What you need:
Cube i6 Air (3G or Wifi)
Flash Drive (256Mo +)
OTG cable
USB Hub (3 Ports recommended)
EFI BIOS Firmware
DOWNLOAD THE FIRMWARE BEFORE STARTING SO EVERYTHING IS AVAILABLE WHEN YOU DO IT
https://drive.google.com/folderview?id=0B8YPw4HjmqNCZktOZy1OTEN2ZVE&usp=sharing
Get on the drive, go to your device folder, select the wanted version inside BIOS folder
What to do :
1.) Start by plugging the usb drive into your computer, and format it to FAT32 using any formatting tool
2.) Now you need to uncompress the downloaded firmware :
you will find a "Firmware_X.X.X" folder inside, take all of its content, and extract it to your freshly formatted drive.
here's what looks like the root of your usb:
3.) Your USB Drive is ready, now just plug the OTG cable to your tablet, plug your HUB onto that OTG
and fill it with your keyboard and the USB Drive just created.
4.) Press power button until you see the screen backlight, when you see it repeatidely smash "Esc" key on the connected keyboard.
You will see the bios 6 square configuration screen.
Hit "Boot Manager" and select your USB in the list.
5.) The tablet should now boot from your USB, booting to a UEFI Shell. Depending on your device, it might be either 64 or IA32.
Now you just let startup.nsh script do the firmware flashing init, it should drive you to a flashing BIOS screen.
6.) Follow instructions on screen and let the tool flash your BIOS automatically.
Once done, the tablet will shut down.
Congrats! You successfully updated your BIOS !
It is my first tutorial, i will post some photos of steps in the future so come back, the guide will be better soon !
Regards,
Max.
Hi,
I have bought the Cube i6 Air 3G a week ago and i'm still waiting for it to arrive.
Have you update the win 8.1 to win 10?
Does everything works correctly?
Regards
re
Hi, I successfully updated the BIOS as of now,
I changed the bootloader animation to nexus one on Cube ROM.
I also manager to boot on Android x86 but it had too many drivers issues.
Still, 4.4.4 stock cube is working and i reflashed to a new partition scheme of 9Go
and i'm currently testing some win10 pen drives for install, will keep you updated.
Édit: oh you were asking about thé tablet? Weil jack has default, charging takes hours, glass is plastic, firmware is pain but hell this is a goodamn good tablet for its price !
regards,
Max
stalker2106 said:
i'm currently testing some win10 pen drives for install, will keep you updated.
Click to expand...
Click to collapse
I achieved installing Win10 x32 Pro on Cube i6 Through hacking WinPE installation environnement, but now i'm struggling finding the drivers. touchscreen, battery and vital things like hd graphics are not working as of now. Will post a tutorial on how to install Win10 in given time when i'll get out of this mess!
My tablet has arrived yesterday.
From what the little i've used it, it has good performance especially in android.
A lot faster compared to my last android tablet (Cube U39GT).
Something i didn't like was the size of the icons and text in android, my next step is to root and change the dpi.
Regarding windows 10, i found in a chinese tablets blog with win 8 and 10 drivers.
I haven't tested it, but as soon as i find it again, i will let you know where to download them from.
You haven't tried the normal win 10 upgrade? From the microsoft icon?
gtbr said:
My tablet has arrived yesterday.
From what the little i've used it, it has good performance especially in android.
A lot faster compared to my last android tablet (Cube U39GT).
Something i didn't like was the size of the icons and text in android, my next step is to root and change the dpi.
Regarding windows 10, i found in a chinese tablets blog with win 8 and 10 drivers.
I haven't tested it, but as soon as i find it again, i will let you know where to download them from.
You haven't tried the normal win 10 upgrade? From the microsoft icon?
Click to expand...
Click to collapse
I did not try anything as i like "stock" versions of my windows, but tonight i got it working all the way !
My cube i6 is running perfectly windows 10 and oh my god what a paradise it is ! The tablet experience got way better onto that version.
Can you try to update from the icon you are talking about ? i'd be curious if it works. anyway, i'm currently writing+uploading for the win10
tutorial for this tablet, so you'll be able to flash it late tonight, or tomorrow.
EDIT: The dpi is correct in android, only the status bar icons and some other are not in correct dpi but that is KitKat issue I guess. still interested in resolving that though. I'm currently hacking android lollipop ROM also, i'll keep you tuned on that. For rooting, i used KingRoot, it worked, but after a reboot, it tells me "root" is wrecked, so i guess there is some investigation to do there, but I was mainly focused on getting windows 10 ENGLISH STOCK version running to share it with you guys.
EDIT2: Still uploading, but tutorial is here: http://forum.xda-developers.com/android/help/guide-how-to-install-windows-10-t3252042 and it should work on any Z37xx powered device. Enjoy !
Hello,
I'm using this tablet from 2 days now. great !
But, i got wifi problem after sleep : wifi chip cut and never found network anymore.
has to reboot, and all goes right.
same in win and android.
Did you hear about this ? many poeple complain about this.
Any trick or advice ? Is this bios correct this ? Is your bios work on i6 3g dual-boot ? (there is 2 bios for dual boot ?...)
Thanks !
Hi,
I've also have the same problem with the wifi.
I usualy disconnect the wifi and reconnect it, but sometimes it doesnt work and have to reboot the tablet.
I've not noticed it in windows but maybe it's because i'm using the tablet a lot more in android.
I've tryed to update to win 10 using the microsoft icon, but i got an error and was unable to complete the upgrade.
gtbr said:
Hi,
I've also have the same problem with the wifi.
I usualy disconnect the wifi and reconnect it, but sometimes it doesnt work and have to reboot the tablet.
I've not noticed it in windows but maybe it's because i'm using the tablet a lot more in android.
I've tryed to update to win 10 using the microsoft icon, but i got an error and was unable to complete the upgrade.
Click to expand...
Click to collapse
Hello, i have such a tablet for now about 6 Months and it is awesome so far (i often use win8.1).
My Tablet has also DUAL Boot with Android 4 and win 8.1 Bing.
I tried to upgrade to win10 but i also got a message that the partition can not be resized by windows. So i cant upgrade to win 10 with the normal tool from microsoft.
Is there any Solution yet to get this to work?
Anyway, i tried to boot from usb (win8.1 / ubuntu / gparted) but it is not working at all. When i try to boot true windows Advanced Boot Options, the BIOS says that there is no USB device.
When i use the EFI Shell to mount the USB Stick i can see that the BIOS has recognized the USB Stick.
I think that is all very strange, but i will try to update the BIOS soon. The serialnumber is not the same as from @stalker2106 but i will try it.
I hope there is a way to get win 10 working, but Ubuntu would be even better for performance.
Greetings from Germany.
tysonpower said:
Hello, i have such a tablet for now about 6 Months and it is awesome so far (i often use win8.1).
My Tablet has also DUAL Boot with Android 4 and win 8.1 Bing.
I tried to upgrade to win10 but i also got a message that the partition can not be resized by windows. So i cant upgrade to win 10 with the normal tool from microsoft.
Is there any Solution yet to get this to work?
Anyway, i tried to boot from usb (win8.1 / ubuntu / gparted) but it is not working at all. When i try to boot true windows Advanced Boot Options, the BIOS says that there is no USB device.
When i use the EFI Shell to mount the USB Stick i can see that the BIOS has recognized the USB Stick.
I think that is all very strange, but i will try to update the BIOS soon. The serialnumber is not the same as from @stalker2106 but i will try it.
I hope there is a way to get win 10 working, but Ubuntu would be even better for performance.
Greetings from Germany.
Click to expand...
Click to collapse
Check windows 10 Post, there is no need to update BIOS to fix this error, your USB has to be in GPT partition style, check answer on the other thread
But usually the bios update should work, as it did on my tablet. But why bother taking risk if you can get it working without it
Hi,
I have sucessfully updated to win10
I have bios 203 in my cube and serial i632gb1510xxxxxxxxxxx, does anybody have tried to update to 206 on such setup ?
What are the chances that I will brick my device ?
I have downloaded latest Cube i6 roms from cube site (may 2015) . There are two bios-es which have to be installed in chronological order.
Shall I do it first, and then try to update to 206 ?
Edit: I was not patient and tried it on my own.I have successfully updated bios and tablet has started to both android and windows
I will perform some functional tests afterwards.
Actual steps :
I have first downgraded bios to 201(provided here )
Flashed bios1 from link provided
Flashed bios2 from link provided
Flashed bios 206 from guide in first post
Edit2:
I have tested basic functionalities like : Gyro-sensors, WIFI, GPS, 3G network and yet everything works like charm.
Maybe a placebo, however I have the feel that android runs like two times faster
I do suggest to update the windows, however I take no responsibility if you will brick your device. Even if the setup is like mine, neither if it differs
Regards
Why do you first downgrade to 201?
What do you mean with bios1 and bios2?
Many thanks and question
Hello Stalker,
I am new here and i want to
thank you for the instructions!
I bought a cube i6 from china.
It is the 'i6 air remix',
So it should have only Android on it.
When it arrived. it didn't function.
The only think that happens is booting to theEFI-shell.
I could switch between Android and Windows in the boot settings.
But Android did not boot.
I have updated the bios with your instructions
now firmware 2.0.6 is installed.
But still i can not boot Android.
I found a few flash tools and android for the cube i6 .
But i don’t know what is the right version flash tool I have to use.
Maybe you have advise or the right android and flash tool in your google drive download area?
Kind regards and many thanks in advance.
jan-netherlands said:
Hello Stalker,
I am new here and i want to
thank you for the instructions!
I bought a cube i6 from china.
It is the 'i6 air remix',
So it should have only Android on it.
When it arrived. it didn't function.
The only think that happens is booting to theEFI-shell.
I could switch between Android and Windows in the boot settings.
But Android did not boot.
I have updated the bios with your instructions
now firmware 2.0.6 is installed.
But still i can not boot Android.
I found a few flash tools and android for the cube i6 .
But i don’t know what is the right version flash tool I have to use.
Maybe you have advise or the right android and flash tool in your google drive download area?
Kind regards and many thanks in advance.
Click to expand...
Click to collapse
The truth is, the 206 BIOS provided is hacked off i6 remix repository from cube, so i guess there is no big deal flashing it on your device as it works on regular i6.
Moreover, you can use any version of the flash tool as long as you flash a correct rom for your device, which i would suggest to download from official cube repository or geekbuying or so.
Android Geecbuying
Hello Stalker,
Ok. Thank you!
I will try Geecbuying.
Hopefully the windows drivers will function.
There isn't a way to flash from USB I suppose?
Greetings
Hi, well, actually, you should flash over USB with à windows computer. MFT by Intel is recommended. I shall make some tutorial about Android installation and partition resizing.
flash and resize partitions
That is super. When you want to do so.
I was indeed wondering or there would be one android partition on the tablet or two partitions (one for android, one for windows).
I also questioned myself how to see that there are partitions.
In earlier times when I was working with a pc, i use F-disk or partition-magic for this kind of work.
But on the tablet I do not have a clue...
So if you could make me wiser on this, I would be very thankful.
Maybe you could boot on some gparted liveusb? Or inside efi shell some commands could help
bluefish007 said:
Why do you first downgrade to 201?
What do you mean with bios1 and bios2?
Click to expand...
Click to collapse
no particular reason, I just wanted to know, which version of bios is in the latest firmware provided by geekbuying
Additional condition in my decision mechanism was that my serial did not match mentioned ones in w10 thread from stalker, so somehow I have used sleepy sloopy logic and tried to minimalize the risk (I know it have no rational reason and logic behind it at all)
Therefore, I tried the ones from geekbuying repository, to be sure to have latest provided from "official source".
greetings
thermoska said:
no particular reason, I just wanted to know, which version of bios is in the latest firmware provided by geekbuying
Additional condition in my decision mechanism was that my serial did not match mentioned ones in w10 thread from stalker, so somehow I have used sleepy sloopy logic and tried to minimalize the risk (I know it have no rational reason and logic behind it at all)
Therefore, I tried the ones from geekbuying repository, to be sure to have latest provided from "official source".
greetings
Click to expand...
Click to collapse
Ok thanks for the answer! So i can upgrade from 203 at 206 at one part or what do you think?
This is Directly related to the Mseries boxes.
The M8s+ device inperticular but its widely cloned and comes under many names.
MXIII, M8, M8s, M8s Plus etc. The chipset and storage are the important factors here.
Amlogic S8xx series devices, like the S802, S812 etc.
This will be used for Q/A
Troubbleshooting
and helping direct traffic to the right devices.
Freaktab.com has the Android Tv box section laid out well compared to Xda.
The Android phone section on XDA is perfect and im hoping we can get the Tv boxes organized and supported more!
To enter the recovery stock or not, there are multiple methods.
Using a toothpick and pushing the reset button inside the AV port ( Harder/nonrooted )
1.) At the bottom of the AV jack hole is the reset button.
Using a tooth pick hold this button in. You know you have pressed it if you feel the click.
2.) Now plug in the power cord.
3.) While holding the reset button down, wait until you see the logo and you can then release the reset button.
done: The recovery menu should now be shown and the device should update.
ALT For rooted devices:
1.) Install romtoolbox lite and Give romtoolbox superuser permissions
2.) Use the rebooter function inside the app to enter recovery mode. (easier)
Rooted how to Install Custom Recovery or Return to Stock Recovery:
To install the custom recovery I used [Root] Rashr - Flashingtool app to install the custom TWRP recovery, this also can be used to install the image files like boot.img or return to stock recovery.img
Notes:
The boot img needs to match the rom version you are running.
IE: 4.0 needs the 4.0 boot.img. 5.0 needs the matching 5.0
in most cases the device will not boot or bootloop when using mismatched images. in some cases you can use the LATEST image and run older software behind it. Furthermore, if you choose to not listen your support will be to listen and try it this way first.
The recovery images should be used the same way, ive attatched the links on my main page for convienece.
The manufactures and sources post the rom and the img together in a combined zip, ive broken them apart to reduce size and to avoid loosing your custom recovery evey time you flash a rom! This makes updates etc sooo much easier!
Would you know if you're able to flash the m8s+ rom on an ACEMAX M8S Amlogic S812 Quad Core box? From what I can see they have the same hardware specs however the + is a lollipop rom?!
Thanks in advance. I realise this says to only post 'answers' but your first post says this will be the Q&A section...
I have a M8s Android box (Amlogic s812 Quad Core 2gb Octa Core Gpu).
I am running a 5.1 ROM (Originally came with 4.4). It runs great but it has 3 problems.
1. Remote doesn't work (I have a zip file I flash to get the main functions working but not all the buttons are mapped correctly).
2. Ethernet doesn't work, only WiFi.
3. When power button is pressed on remote the box goes to sleep and never wakes up. (I tried an apk from FreakTab called wakemescottie which solves this problem for maybe half a day, then it goes back to never waking up again unless unplugged.)
I am trying to downgrade to what should be a proper ROM for the box (5.1 ROM is listed as being for the M8s+) but when I try to it tells me it cannot install the zip package because the date is older than the ROM on the box.
Has anyone figured out a workaround that does not involve TWRP? Reason I am asking is I cannot seem to get TWRP working on my box from links provided. I am not sure if it is because my box is a cheap clone or if I need to do something before trying to run TWRP like rooting the box or something.
Any help on this would be great I have tried so many different ROM downloads I'm out of ideas.
Though if anyone is capable of helping me with the three issues that would be great as I do find the 5.1 ROM to be much more stable than the original ROM.
M8s mini is with SoC S905?
Sent from my GRACE using Tapatalk
TopperBG said:
M8s mini is with SoC S905?
Click to expand...
Click to collapse
From what I know I don't think it's the mini. It's this box Click to view URL I have pictures of the board but it's on FreakTab which is currently down.
Can some one point me in the right direction for the firmware for a t95z plus firmware it's a amlogic s912 chipset with 2gb ram
h t t p s://mega.nz/#F!Ix9zmZqC!LIVPa5zPR6XmcwODW42r7Q
Use this method to flash the box:
h t t p://androidpcreview.com/how-to-use-the-amlogic-usb-burning-tool-to-manually-update-firmware/3749/
You will need an usb to usb male cable. Connect to usb1 on the box. No power cable needed.
Worked for me.
are there newer images.. I bought one of these
https://www.aliexpress.com/item/2GB...73409096.html?spm=2114.search0104.8.57.YrpUy2
[Genuine] T95Z Plus 2GB 16GB 3GB 32GB Amlogic S912 Octa Core Android 7.1 OS Smart TV BOX 2.4G/5GHz WiFi BT4.0 4K pk X92 h96 pro+
I got the 3g/32g rom was fast and seemed ok android 7.1
until I upgraded or installed the superuser from chain DD said installed ok and asked to reboot which
I did for it only to hang on the boot animation... so very sad
I suspect its altered or written to the wrong partition?
now need to reflash
recovery works with toothpick
is there a image for this new update? and can it be flash from recovery from sd card so dont need a pc
as pc cable method is more a pain
Firmware for t95p ?
(3GB)
T95ZPLUS-7.1-912-3GB-17.3-v1072
https://goo.gl/RG92GR
by the way, who also want a 2GB or directly dl from their link are also welcome,
Below are the links from sunvell,
(2GB)
T95ZPLUS-7.1-912-2GB-17.3-v1013
http://pan.baidu.com/s/1jl7jLOU
Pw: 81uc
(3GB)
T95ZPLUS-7.1-912-3GB-17.3-v1072
http://pan.baidu.com/s/1hrPU5rY
Pw: gbrg
I add the info for others with bricked boxes or bad ram.. reformat reflash can bring them back
also try a new power pack.. often the voltage degrades over years and drops too low
I used the 3gb with the flashing tool usb to right sid port... leave power plug out.. and insert toothpick and
connect usb from pc.. should beep if pc detects device on USB and the tool should show finally
http://androidpcreview.com/how-to-use-the-amlogic-usb-burning-tool-to-manually-update-firmware/3749/
http://androidpcreview.com/wp-content/uploads/2015/12/USB_Burning_Tool_v2.0.6.2_build2.rar
---------- Post added at 12:49 AM ---------- Previous post was at 12:43 AM ----------
endera said:
Firmware for t95p ?
Click to expand...
Click to collapse
you could try asking these guys
http://freaktab.com/forum/tv-player...s/s905x/607678-sunvell-t95p-tv-box-2-8gb-wifi
I thought i read some 95z plus roms will work but not sure.
---------- Post added at 01:02 AM ---------- Previous post was at 12:49 AM ----------
endera said:
Firmware for t95p ?
Click to expand...
Click to collapse
similar cpu
http://chinagadgetsreviews.com/firmware-t95x-tv-box.html
(2GB)
T95ZPLUS-7.1-912-2GB-17.3-v1013
http://pan.baidu.com/s/1jl7jLOU
Pw: 81uc
The above link for 2GB is not working, also can you please clarify for which WiFi chip is the above firmware? There are three versions of T95Z Plus: WiFi 8830, WiFi 6330 and WiFi 6335. If one flashes the wrong version, then WiFi will not be working on his box...
Thanks for this thread. I am fighting with a T95z PLUS 3/32GB stuck on boot. I am going to try the above ROM (the one in gdrive is still available) as soon as I can get a USB cable, and report the results.
EDIT: Is there a way to flash from SD? I have no usb-to-usb cable to try right now, I am going to have to buy one and wait for it...
EDIT 2: Flashed through SD directly. Extracted the contents to a FAT32 formatted SD card and inserted it in the T95Z Plus. Booted normally and proceeded to "upgrade". The box is working right now. Sound are wifi are working - cannot say more than that so far. I don't know if the version is older than the original that came with the box, but I guess it should be possible to update if necessary (not sure how, though).
Thanks @kiwiman2000!
I can see from the boot screen that the firmware posted for the 3/32GB model by Kiwiman2000 with which I recovered my box is the 20170623 version. I know that the one my box had before rescuing it was 20170807, so it is possible that somewhere a newer version is available. The OTA updater is not finding anything online, though. In the meantime I will stick with this working version, and if I happen to find an update, I will post it here.
After playing around with the T95z Plus after installing the above firmware, I started noticing some bugs. First, the Play Store resets itself constantly. It seems every time it updates from the factory version to the current one, whenever you open it, it goes back to factory, asks for permissions again, and resets all settings.
I have tried to replace the system apk with an updated version. This works but only when starting it for the first time. It then fails to open, and will only open again after clearing the app data.
Does anyne know how to correctly fix a broken gapps?
Latest T95Z Plus Firmware. Android v7.1.1 For 2GB RAM/16GB S912 Chipset
Here is the latest firmware for the T95Z Plus Android tv box. Works on Sunvell, and also on Weily branded T95Z plus and probably all models with same chipset. Says android 7.1.2 but it’s actually 7.1.1. Latest firmware for this box tho. Runs great.
Google search “latest t95z plus firmware” and it’ll be the first site you see called entertainmentbox. I can’t post links here as I’m a new user.
You don’t need to use the male to male USB cable method to flash firmware. You can use Burn Card maker and update box using micro sd card. USB burn card maker can flash new firmware and also revive bricked Amlogic based android tv boxes.
search on YouTube for “t95z plus burn card maker” and there are many videos on how to use this method.
Hope this helps, it will get your box updated to Android v7.1.1 build T5ZP1013 kernel v3.14.29 android security patch level February 1, 2017 Model T95ZPLUS despite the build saying T5ZP1013. I assure you it’s the T95Z Plus firmware.
As for google play updating, then returning back to previous version and default settings every time I believe this is to keep the box running without breaking any apps or software for the current firmware. You really only need the version the firmware comes with. If you wish to update keep a lookout for future firmware releases. My box has the same issue as do others I have asked. I also like to have the latest version of everything too so this is what prompted me to check into the google play thing myself.
Happy Flashing!!! -~
T95z Plus will not flash
I have tried over 7 different roms, different usb, ect all the same result
UBOOT/Partition _aml_dtb/Verify patition/Error result can't pass 9%
What does that mean??
Hi friends, which application is responsible for display (LED) on the device?
victorsyt said:
Hi friends, which application is responsible for display (LED) on the device?
Click to expand...
Click to collapse
It's the WinS8Launcher system app. This also five the CEC options in the settings.
mr sharpey said:
It's the WinS8Launcher system app. This also five the CEC options in the settings.
Click to expand...
Click to collapse
Thanks. It's important.
I ran into this problem, since Kodi wasn't playing right. I used a script program universal init.d and supersu, and after supersu rebooted the device it hung on reboot. I have an easytone t95zplus but don't see any of their firmware posted online.
startreksuite said:
I ran into this problem, since Kodi wasn't playing right. I used a script program universal init.d and supersu, and after supersu rebooted the device it hung on reboot. I have an easytone t95zplus but don't see any of their firmware posted online.
Click to expand...
Click to collapse
You first need to determine the precise model to get the firmware:
1) Is it a 16 or 32 GB model?
2) Is it model q200 or q201?
You can check these by booting into recovery.
Need files for recovery
Hello guys, i need some dire help.
i have a 3G 32GB variant with AP6255.
my wifi was broken hence i browsed thru and was flashing the firmwares using tooth pick method.
1st attempt. - my recovery didnt boot at all. no HDMI signal was going to the TV
2nd attempt - managed to boot to recovery and flashed the firmware. wifi was not fixed.
3rd attempt onwards i could never get into recovery.
looks like my sd card marker is missing some boot files.
appreciate someone could guide me the extact steps and files i need for recovery to work.
archrival9 said:
looks like my sd card marker is missing some boot files.
appreciate someone could guide me the extact steps and files i need for recovery to work.
Click to expand...
Click to collapse
I am not sure of how to help you- but I will tell you this: I did not use a SD card maker. I just pasted the img file into the root of the SD card AND also included the extra files (which I believe are needed for proper boot and installing) from a different img file package I found somewhere else. So, tell me if this can make sense somehow:
Get the img file you tried to use in step 3 and put it in a SD along the extra files included in the package you used in the second attempt.
This is sort of the way I had to go to fix mine (although, for the sake of truth, my box is pretty unstable now - freeezes and hangs often). I hope an update would come out, but nothing so far.
Hi everybody, I'm just posting to let you know that I have very much upgraded my T95Z Plus 3/32 through the instructions in this thread, which includes firmware and recovery files.
Hopefully someone else can give it a try.
hello,
what / where is the last upgrade / custom rom for T95z plus 2/16gb S912 ?
These tablets were sold with certain Vizio TVs in mid-2016 into 2017, primarily used for Smartcast to the TV.
They are now obsolete since Vizio released firmware for their TVs turning them into normal Smart TVs, requiring the owners of these TVs to get new remotes and the tablets stopped being useful for this function.
Here in 2019, one can buy these tablets, at the low price end, in working condition, for $25 (for the M series) to $40 (for the P series) shipped.
The specs are as follows:
XR6M10:
Snapdragon 410 1.2GHz quadcore APQ8016
2GB RAM
8GB Storage
1280x720 IPS display
802.11n, Bluetooth 4.0
2740mAh battery
MicroUSB for charging, Qi Charging built-in for bundled charge pad or any compatible charging solution
XR6P10:
Snapdragon 615 1.45GHz octocore APQ8039
2GB RAM
16GB Storage
1920x1080 IPS display
802.11n, Bluetooth 4.0
2740mAh battery
MicroUSB for charging, Qi Charging built-in for bundled charge pad or any compatible charging solution
Both tablets feature side-firing stereo speakers, a headphone jack, and NO cameras. The size of the tablet is comparable to the size of a Galaxy Note 9, give or take.
Both tablets came with Android 5.1.1, and OTA updates upgraded them to 6.0.1. There are ZERO available stock ROM files available for the tablets. I've tried sniffing the updater and they seem to go to a dead website.
The stock ROM is fairly clean, and only has the Vizio Smartcast app which needs disabling upon setting up. Aside from this, there is no other bloatware on the tablet to speak of after running a fine-tooth comb through the system apps. You get a clean and snappy tablet.
The problem:
There's no stock ROM file available, neither for Android 5.1.1 or for 6.0.1. Vizio does not have any sort of download for either on their site, nor did in the past. The updater checked a third-party website affiliated with Vizio to manage the tablet's updates, as it does with their TVs. Since the website is inert, it can be safely said that Vizio is no longer interested in their existence at all, especially since the warranty on every single one of these tablets is now up.
The tablet seems it can have the bootloader unlocked, the developer options has the toggle for that, but there's no way to get into fastboot. Holding VOL UP+DOWN+POWER at boot or sending the "adb reboot bootloader" command sends it into a "Qualcomm HS-USB QDLoader 9008" mode under USB. This, from what I understand, is behavior persistent with the locked bootloader, but I have no idea of how to get it out of this and just into fastboot. Stock recovery does not have a fastboot option either.
The desires list:
Have someone that knows the intricacies of the MSM8916 platform and the APQ8016/APQ8039 get their hands on these tablets
Get a ROM dump of both tablets in stock form so people with bricked tablets can flash them with it
Get Root (Patch level on the 6.0.1 stock ROM is from October 2016, shouldn't be hard)
Get the bootloader unlocked, somehow, and if not, figure a way to get something like Safestrap running on it if the out-of-the-box kernel allows for it
Custom ROMs? LineageOS would be sweet, especially with some of the tablet-specific fixes that have dropped in the past couple months overall.
so I ask: is there any interest in the freeing of these super cheap tablets? The price to spec ratio is not bad (once again, I got my 6M10 for $25 shipped, and the seller has like 7 more as of the time of this writing), and it doesn't seem like it would be all too hard to unlock the bootloader and get it rooted (at least, from my perspective, that of a novice in this specific hardware field). There are plenty of these in the wild in the hands of people that bought the TVs and plenty in the hands that bought them from ebay when the tablets became obsolete.
This link contains screenshots of CPU-Z and the About Tablet settings section from the tablet, uploaded to imgur. If anyone needs more information on this tablet that needs an app or adb command, I can make this happen.
Board Pic of the XR6M10, XR6P10 should be the same inside:
(click for larger image)
Update: I have temp root.
I have temp root!-the latest kingroot (NOT Kingoroot) APK seemed to have done the trick. I was able to fire up adaway and get the hosts file set up with adblocks to keep the thing safer.
The root is still temporary so it goes away after a reboot. The rooting process involves it doing the root process once, then rebooting, then failing, then you reboot once more, and then retry rooting from the app. From here, 80% of the time, it works and you're able to get temporary root for that boot session.
Once you're done with anything you need root for, you should reboot and then uninstall Kingroot, which you then need to deactivate the device administrator priveleges for, before it will allow you to cleanly uninstall it.
I also made a huge discovery that may turn out better for anyone that can help getting this thing properly rooted and the bootloader unlocked... it seems the file manager included in the stock ROM is v3.0.0 from Cyanogenmod 12.1.
This makes me think that the ROM creator either used that since it was opensource and readily available than come up with their own solution, or that this ROM has some cyanogenmod roots.
I also found this post from another Q&A thread in this section:
TheDrive said:
This device have made by Chinese/Indian company Borqs. The code name Bennu-M. Platform is Qualcomm APQ8016 (MSM8916 w/o modem). There should work standard method to bring EDL mode. Hold Vol+ and Vol- at power on (press power). Then connect to the PC. Thus device will stay look dead, however should be detected as Qualcomm QDLoader 9008 on the PC side. This is the factory described method.
You can flash factory firmware from this mode using external bootloader (programmer) for MSM8916 firehose protocol. This procedure is described in the thousands of manuals around the net. Qualcomm tools like QPST or QFIL can be used as good as many 3rd party utils to flash and manage any another available way. Many professional 'box' tools should support this device too but only as 'generic' msm8916 (if applicable).
However I can't find the firmware package for this device anywhere. You should ask and require the manufacturer/distributor to publish firmware, the source code and all the corresponding matherials to be able to flash and rebuild firmware from sources in any manner you want without any limitations as required by GNU/GPL free open source software licenses this firmware is obligated to.
Everyone who have the device working or software dead, can try to dump the current firmware and data, stored on the internal eMMC memory module in part(s) or in whole image using free QTools project utilities and suitable external bootloader with ability to dump eMMC, not only to flash as many factory supplied programmers do. There are programmer(s) for MSM8916 available in the project repo. Read and understand manuals carefully before trying anything!
There is definitely another ways to root, dump, flash, manage the device in any manner YOU WANT, not only the way you are "allowed" to use your own device by manufacturer/distributor. FTA!
You can root the device then dump all the multiple partition images manually (dd if=/dev/block/mmbblk0...... of=/sdcard/......) or using built custom recovery like CWM/TWRP for your device. Please note, kernel sources are important but not mandatory to build e.g. CWM. You can build one using CWM image from the similar device and the kernel (boot/recovery) image binaries from your device. There are good manuals and image repacking utils available around like e.g. AndImgTool.
There are the way to produce factory image from the eMMC/partitions dump(s). Use utils like R-Studio to dump particular partition images from the eMMC dump (it's like whole HDD or UFD image with all the sectors raw, one by one, w/o any modifications/compression/etc) Manuals / utils are avavailable to make e.g. sparse and xml scripts set which is flashable by the programmer in the EDL mode (i.e. from any damaged state, because EDL is built in to the PBL and masked to the internal CPU ROM, thus can not be damaged in any manner, except firing the CPU up).
You can also flash partition images from the more common Fastboot mode, unless eMMC GPT and bootloaders (SBL/RPM/TZ/ABoot) stay intact (logo showed). You can't dump from fastboot, which is common due to the (foolish) 'safety' requirements. It's security by obscurity and is definitely not for your favor, but for the corps control over you and force to send valuable private data to foreign clouds.
Please share eMMC full and/or partitions dumps using reliable 'neverending' file cloud/hosting since there is no factory firmware available yet (ever). I do not own this device and never seen being overseas, so I can't share.
Click to expand...
Click to collapse
This gives a little bit more information but seems to be more waffle than helpful. Still need someone, or some individuals, that can get one of these devices into their hands and work on a way to get the bootloader unlocked, the eMMC dumped, and ROMs going.
Update file?
I THINK I have the update file for 6.0.1. I did a packet sniff on a 5.1.1 tablet using a mitm packet sniffer and I ran the system updater, and was able to get this URL:
http://updatev.vo.llnwd.net/v1/idownload/64821.bin
The filesize is 570MB or so, and it looks like it might be the real deal. since it's a .bin file and 7zip can't read it, I won't be able to see what it really is without going over to the box that has a copy of universal extractor installed.
I'll be doing this momentarily and editing this post once I figure out what the contents are or if it's even readable to that extent. Knowing vizio, it could very well be encrypted and need decrypting by the updater application.
Update: it seems to be encrypted. oh joy.
Update 2: I got together with a friend on discord and we successfully decompiled the updater app to a point.
This MEGA link contains all the files thus far and a copy of the tablet's /system/framework folder for decompiling purposes.
However, it doesn't seem we're getting anywhere. the file is still encrypted and I still can't figure out what's needed to decrypt it. Hopefully someone with more knowledge on this can lend a hand.
Sudosftw said:
I THINK I have the update file for 6.0.1. I did a packet sniff on a 5.1.1 tablet using a mitm packet sniffer and I ran the system updater, and was able to get this URL:
http://updatev.vo.llnwd.net/v1/idownload/64821.bin
The filesize is 570MB or so, and it looks like it might be the real deal. since it's a .bin file and 7zip can't read it, I won't be able to see what it really is without going over to the box that has a copy of universal extractor installed.
I'll be doing this momentarily and editing this post once I figure out what the contents are or if it's even readable to that extent. Knowing vizio, it could very well be encrypted and need decrypting by the updater application.
Update: it seems to be encrypted. oh joy.
Update 2: I got together with a friend on discord and we successfully decompiled the updater app to a point.
This MEGA link contains all the files thus far and a copy of the tablet's /system/framework folder for decompiling purposes.
However, it doesn't seem we're getting anywhere. the file is still encrypted and I still can't figure out what's needed to decrypt it. Hopefully someone with more knowledge on this can lend a hand.
Click to expand...
Click to collapse
Just out of curiosity, with the temp root, have you tried using dd to get the recovery image off? If we can do that, we might be able to work on getting a custom recovery built.
Qiangong2 said:
Just out of curiosity, with the temp root, have you tried using dd to get the recovery image off? If we can do that, we might be able to work on getting a custom recovery built.
Click to expand...
Click to collapse
It's not possible to get a proper recovery image from within the system files so far as I know, but my take so far has been that there is no proper way to get that at this time without decrypting that file grabbed from the update server. I'd do it on a 5.x ROM since that will get me permaroot, but the issue is getting and keeping root on a 6.x ROM.
Although encrypted (so far as I can tell) the image linked above is the real deal, and I've given all I can to get it decrypted. A proper exploit to take care of this tablet's vulnerabilities and get temp root (on 6.x) that isn't kingo is what is really needed at this point so to not hinder going around the system with crudware and shady background apps, shouldn't be hard since the security patch level for the 6.x ROM is 2016-10-01.
Even if the ROM is extracted or a recovery image found, custom recovery won't be possible until the bootloader is unlocked, and this isn't doable until someone figures out how the qualcomm qdloader9008 stuff works with this specific tablet. Fastboot is unreachable and I'm almost sure I'm doing something wrong.
I'll get temp root and see about dd'ing stuff later on. What exactly would be needed for me to dd off? Whole disk and then go through it elsewhere? I could definitely see if rsync exists and dd over rsync to another box.
Sudosftw said:
It's not possible to get a proper recovery image from within the system files so far as I know, but my take so far has been that there is no proper way to get that at this time without decrypting that file grabbed from the update server. I'd do it on a 5.x ROM since that will get me permaroot, but the issue is getting and keeping root on a 6.x ROM.
Although encrypted (so far as I can tell) the image linked above is the real deal, and I've given all I can to get it decrypted. A proper exploit to take care of this tablet's vulnerabilities and get temp root (on 6.x) that isn't kingo is what is really needed at this point so to not hinder going around the system with crudware and shady background apps, shouldn't be hard since the security patch level for the 6.x ROM is 2016-10-01.
Even if the ROM is extracted or a recovery image found, custom recovery won't be possible until the bootloader is unlocked, and this isn't doable until someone figures out how the qualcomm qdloader9008 stuff works with this specific tablet. Fastboot is unreachable and I'm almost sure I'm doing something wrong.
I'll get temp root and see about dd'ing stuff later on. What exactly would be needed for me to dd off? Whole disk and then go through it elsewhere? I could definitely see if rsync exists and dd over rsync to another box.
Click to expand...
Click to collapse
I found this today: https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
The miflash tool seems promising (it works with nearly any device)
For the dd stuff, you can usually figure out the partitions easily with the fstab file in /. However, getting a raw dump is always useful.
Really, the big 3 would be the recovery.img, the boot.img, and the system.img. We can work from there
Qiangong2 said:
I found this today: https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
The miflash tool seems promising (it works with nearly any device)
For the dd stuff, you can usually figure out the partitions easily with the fstab file in /. However, getting a raw dump is always useful.
Really, the big 3 would be the recovery.img, the boot.img, and the system.img. We can work from there
Click to expand...
Click to collapse
I've had that installed whilst trying to figure the image out and the qdloader stuff, it doesn't do anything for this tablet sadly :/
Sudosftw said:
I've had that installed whilst trying to figure the image out and the qdloader stuff, it doesn't do anything for this tablet sadly :/
Click to expand...
Click to collapse
Hmmm. Which tablet do you have? The M or the P?
Qiangong2 said:
Hmmm. Which tablet do you have? The M or the P?
Click to expand...
Click to collapse
this is the M. the P was out of my price range ($40 shipped over $25 shipped) when I was looking at them, but now the Ms are going for around 25 bucks but 15 shipping from another seller, bringing the price up to 40 bucks where the P was. ended up buying the other Ms from the one seller and gave them out to family members because I was so impressed... but I really should have set some money aside for one of the Ps as well and didn't.
Sudosftw said:
this is the M. the P was out of my price range ($40 shipped over $25 shipped) when I was looking at them, but now the Ms are going for around 25 bucks but 15 shipping from another seller, bringing the price up to 40 bucks where the P was. ended up buying the other Ms from the one seller and gave them out to family members because I was so impressed... but I really should have set some money aside for one of the Ps as well and didn't.
Click to expand...
Click to collapse
Okay. You said miflash doesn't do anything, does the device show up in the application and not function? Or does it not show up at all?
Qiangong2 said:
Okay. You said miflash doesn't do anything, does the device show up in the application and not function? Or does it not show up at all?
Click to expand...
Click to collapse
just doesn't show up at all. and yet installing the qualcomm qdloader drivers says it's connected in device manager, so something's up. tried on two different boxes, different cables, no dice.
Sudosftw said:
just doesn't show up at all. and yet installing the qualcomm qdloader drivers says it's connected in device manager, so something's up. tried on two different boxes, different cables, no dice.
Click to expand...
Click to collapse
Hmmm. That's unusual. Are you running it in win 7 compatibility mode?
It would be nice to see community roms for these devices. I have the XR6P. If you need any info from this device, just tell me what to do.
I'm very interested in this as I have one of these tablets that I would like to use in my vehicle as a display for my piggyback ECU tuner. It doesn't currently support USB OTG, but I read that if I can gain root access I can add the file to give it USB Host functionality. Can anyone confirm this? I have tried several apps to get it rooted including Kingroot as you were able to get a temp root with that. Unfortunately Kingroot, as all the others I have tried, won't even install on the tablet. Again, I'm only looking to get this thing to be OTG capable. If anyone here has any suggestions, I would be very grateful! Thanks all!
I just bought an M remote to replace my broken P remote. My P remote had Android 6. My M remote has Android 5, and the OTA updater says there's no update. Any way to get Android 6 on this?
I have factory firmware for Bennu P and Bennu M , but take some time to upload the file.
ALANCHONG said:
I have factory firmware for Bennu P and Bennu M , but take some time to upload the file.
Click to expand...
Click to collapse
Hey. You can lay out the firmware for XR6M10
XR6M10 and XR6P10 firmware
konog said:
Hey. You can lay out the firmware for XR6M10
Click to expand...
Click to collapse
Mega Link: mega.nz/#F!n65kVYIT!PKH8A1WoD_Nc4DU_-9dbiQ
ALANCHONG said:
Mega Link: mega.nz/#F!n65kVYIT!PKH8A1WoD_Nc4DU_-9dbiQ
Click to expand...
Click to collapse
All the time, an error pops up at 12 seconds
Flash fail (-4002)
Log:
21:59:03.576 Arrival: \\?\USB#VID_05C6&PID_9008#5&13a74b18&0&11#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
21:59:03.591 Thread '_PortDownloadThread' started
21:59:04.610 Get Port ...
21:59:04.610 _GetDevicePortName (0): COM5
21:59:04.630 _ComPort: COM5
21:59:04.640 Get Port (0)
21:59:04.650 Flash ...
21:59:09.668 _Connect (0)
21:59:09.668 Downloading flash programmer: C:\_qcMUP\v8016-SIGNED-VIZIO-user-IMAGES\v8016-SIGNED-VIZIO-user-IMAGES\prog_emmc_firehose_8916.mbn
21:59:14.669 Failed to read the command from the opened port
21:59:14.669 _FlashProgrammer (-4002)
21:59:15.700 Flash (-4002)
21:59:15.700 Flash fail (-4002)
21:59:15.731 Download ended: -4002
21:59:15.763 Thread '_PortDownloadThread' ended
konog said:
All the time, an error pops up at 12 seconds
Flash fail (-4002)
Log:
21:59:03.576 Arrival: \\?\USB#VID_05C6&PID_9008#5&13a74b18&0&11#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
21:59:03.591 Thread '_PortDownloadThread' started
21:59:04.610 Get Port ...
21:59:04.610 _GetDevicePortName (0): COM5
21:59:04.630 _ComPort: COM5
21:59:04.640 Get Port (0)
21:59:04.650 Flash ...
21:59:09.668 _Connect (0)
21:59:09.668 Downloading flash programmer: C:\_qcMUP\v8016-SIGNED-VIZIO-user-IMAGES\v8016-SIGNED-VIZIO-user-IMAGES\prog_emmc_firehose_8916.mbn
21:59:14.669 Failed to read the command from the opened port
21:59:14.669 _FlashProgrammer (-4002)
21:59:15.700 Flash (-4002)
21:59:15.700 Flash fail (-4002)
21:59:15.731 Download ended: -4002
21:59:15.763 Thread '_PortDownloadThread' ended
Click to expand...
Click to collapse
Please check if the driver is installed