This thread is about dual booting Dell venue 8 (3830) and is only for Dell venue 8 (3830)
You need to have already unlocked bootloader, have cwm recovery installed, no help will be given in this thread for rooting, unlocking bootloader or installing cwm recovery.
You need a micro sdcard , I use class 10 sandisk micro sdcard, you need to format micro sdcard into 3 partitions, 1st partition fat32, 2nd and 3rd partitions ext4.
1st partition is external sdcard, you need this large enough to store files.
2nd partition is system at least 1GB
3rd partition is going to be for data so you might want it to be 4GB or larger
depending on the size of your micro sdcard, will determine how large partitions you can make, you can make them small first time, just so you can understand how this works, you can always reformat the micro sdcard later and redo this entire process.
I use gparted, as I use Linux, you can use whatever partition tool you want to partition your micro sdcard.
Insert your micro sdcard into a reader, insert your reader into your pc and partition micro sdcard, below is a sample pic.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Once done place micro sdcard into your tablet.
Now download dell_venue_8_dual_boot.zip
http://www.mediafire.com/download/f1wk0331eirlzde/dell_venue_8_dual_boot.zip
extract to desktop, all three zip files goes onto your sdcard, or micro sdcard up to you, create a folder name it dual_boot on either internal sdcard, or external one, place all three zips into that folder.
Boot into recovery navigate to 4.3.zip then install, once installed click back then navigate to sdcard_boot.zip then install reboot to system, tablet should now boot into 4.3,
To switch back to 4.4, boot into recovery navigate to phone_boot.zip and install then reboot to system, you should then boot into 4.4.
Added another 4.3 rom, this rom doesn't try to update to 4.4.2, I pulled this rom from http://opensource.dell.com/releases/Venue_8_3830_CloverTrail_plus/developer-edition/
Download
http://www.mediafire.com/download/7s5vpbvmj44jr9q/Sdcard_MDK_4.3.zip
use same sdcard_boot.zip from other 4.3 rom.
can you also discribe what kind of changes were made to the boot image and system so I can try to boot 4.2 or just have two kitkats
Really thanks for this, you are awesome and android 4.4 sucks in dell venue 8830.
I only have a question, with this the tablet will have two versions of android? And if yes, this will affect the performance?
Also the 4.3 version is going to be installed in micro sd or in the intertal storage (i have 32gb version)?
quevon24 said:
Really thanks for this, you are awesome and android 4.4 sucks in dell venue 8830.
I only have a question, with this the tablet will have two versions of android? And if yes, this will affect the performance?
Also the 4.3 version is going to be installed in micro sd or in the intertal storage (i have 32gb version)?
Click to expand...
Click to collapse
4.3 installs to micro sdcard, that's why you partition micro sdcard. There is no performance decrease if you use class 10 micro sdcard, the lower the class the lower the performance.
Yes you have two OS they are ran independently of each other.
They have their own apps and settings, they aren't ran in VM mode.
sent from my kingSing T1 via taptalk
joanthanmajh said:
can you also discribe what kind of changes were made to the boot image and system so I can try to boot 4.2 or just have two kitkats
Click to expand...
Click to collapse
Changes to system isn't needed, boot.img needs mount points modified,
sent from my kingSing T1 via taptalk
Dual Boot Questions...
This isn't exactly the same thing, but I'm looking to take my Venue 8 Pro (64gb + 2gb ram) and Dual Boot it with Android. To my knowledge, they might share the same hardware, sans the Qi charging. Anyone have a complete factory ROM for it? Would be nice to have Win8.1x86 and KitKat on the same tablet without needing an emulator....
thals1992 said:
This isn't exactly the same thing, but I'm looking to take my Venue 8 Pro (64gb + 2gb ram) and Dual Boot it with Android. To my knowledge, they might share the same hardware, sans the Qi charging. Anyone have a complete factory ROM for it? Would be nice to have Win8.1x86 and KitKat on the same tablet without needing an emulator....
Click to expand...
Click to collapse
Well seeing you have the windows version, then you would be the one who has windows rom, or could make one.
Sent from my Venue 8 3830 using Tapatalk
vampirefo said:
Well seeing you have the windows version, then you would be the one who has windows rom, or could make one.
Sent from my Venue 8 3830 using Tapatalk
Click to expand...
Click to collapse
I meant, that I need a complete image from your model, the 3830. The Pro model (5830) runs like a normal x86 computer(x86 UEFI, so no Android-IA). Only things in place is Secure Boot (which can be disabled) and the EVIL Bitlocker Encryption (which also can be disabled.) Wanted to see if there try some things, rather than wasting my time with the slow VMs from BlueStacks or Genymotion.
Also, didn't know if anyone was interested in the viceversa, run 8.1 on your model.
There's any chance to downgrade the tablet from 4.4 to 4.3 without having the 2 versions of android?
quevon24 said:
There's any chance to downgrade the tablet from 4.4 to 4.3 without having the 2 versions of android?
Click to expand...
Click to collapse
Yes just flash 4.3 stock rom and stock 4.3 boot.img through my recovery.
I will need to make them and upload them, at some point.
Sent from my Venue 8 3830 using Tapatalk
thals1992 said:
I meant, that I need a complete image from your model, the 3830. The Pro model (5830) runs like a normal x86 computer(x86 UEFI, so no Android-IA). Only things in place is Secure Boot (which can be disabled) and the EVIL Bitlocker Encryption (which also can be disabled.) Wanted to see if there try some things, rather than wasting my time with the slow VMs from BlueStacks or Genymotion.
Also, didn't know if anyone was interested in the viceversa, run 8.1 on your model.
Click to expand...
Click to collapse
I have no interest in windows tablet, you could make your own thread and those that are interested in windows OS, could work with you.
Sent from my Venue 8 3830 using Tapatalk
vampirefo said:
Yes just flash 4.3 stock rom and stock 4.3 boot.img through my recovery.
Sent from my Venue 8 3830 using Tapatalk
Click to expand...
Click to collapse
Thanks i did it a few minutes ago, but i have a question, for what are this files:
partition.tbl
image.list
ifwi/ (folder)
And it's neccesary to disable ota updates to avoid update to android 4.4? because tablet downloaded it.
quevon24 said:
Thanks i did it a few minutes ago, but i have a question, for what are this files:
partition.tbl
image.list
ifwi/ (folder)
And it's neccesary to disable ota updates to avoid update to android 4.4? because tablet downloaded it.
Click to expand...
Click to collapse
They aren't needed just delete them.
Sent from my Venue 8 3830 using Tapatalk
Also, like i mentioned before, the tablet downloaded the android 4.4 update (like 340Mb), if i reboot the tablet, the update will get installed? or how can i avoid to update to android 4.4?
quevon24 said:
Also, like i mentioned before, the tablet downloaded the android 4.4 update (like 340Mb), if i reboot the tablet, the update will get installed? or how can i avoid to update to android 4.4?
Click to expand...
Click to collapse
The easiest way is to go to cache you will see the update there make an empty zip file using same now as zip in your cache, then delete the real update and replace with empty zip.
Sent from my Venue 8 3830 using Tapatalk
do you mean the directory: /cache? because is empty.
quevon24 said:
do you mean the directory: /cache? because is empty.
Click to expand...
Click to collapse
Yes cache partition, it's not empty you need to be root to see in cache.
The name of the zip is 0d7bfbe5968f01664ed5f9aec8bb0bbd0e2704f1.P801_KK4.4_wifi_user_signed_US_update_gota_package_25-33.zip
I just checked my cache.
Sent from my Venue 8 3830 using Tapatalk
thanks i forgot to activate the root explore on es file explorer. The notifications of update will keep showing?
vampirefo said:
I have no interest in windows tablet, you could make your own thread and those that are interested in windows OS, could work with you.
Sent from my Venue 8 3830 using Tapatalk
Click to expand...
Click to collapse
I already have. There's another thread in the Venue Pro forum, but no one has replied.
http://forum.xda-developers.com/showthread.php?t=2602070
thals1992 said:
I already have. There's another thread in the Venue Pro forum, but no one has replied.
http://forum.xda-developers.com/showthread.php?t=2602070
Click to expand...
Click to collapse
if you just want the images they are here in the second post
http://forum.xda-developers.com/showthread.php?t=2681783
Related
This post can unbrick any Nook Tablet as long as there is no hardware damage.
Introduction
Some of you might know that I've been working on getting Ubuntu 11.10 running on the Nook Tablet. Why Ubuntu 11.10? It's optimized for touchscreen. My work with Ubuntu is not totally ready yet. The touchscreen is totally wonkey and unusable for touch input.
...Well, without a 3.0 kernel tailored to our device, Ubuntu is quite unusable as a Graphical User Interface. I've tried to compile a few times without any real results to report. The best results I've come across use a 2.6 kernel based on the kernel used for our device by Android. Anyway, if anyone can help get us a operational 3.0, 3.2+ kernel with full support for our device, I can get Ubuntu running.
However, all is not lost. Ubuntu DOES boot on a 2.6 kernel and it WILL perform most tasks that do not require special device control, like wiping the disk and reflashing. I've come up with a total wipe and restore program for SDCard based on ubuntu.
So, as a result of my work, I would like to present the first ever Ubuntu Recovery. This will totally wipe your device. With the exception of the ROM Partition which contains serial information, every single partition will have zeros written to it then flashed with just enough to perform an initial factory reflash. Normally when you perform an update or flash of a device, it is simply formatted. A formatted device can be unformatted. A zeroed device cannot be unformatted. All information is overwritten with zeros.
This will also work if you've damaged the bootloaders or recovery partition.
how to create your own bootable Ubuntu Recovery SDCard
You will need:
A Class 4 SDCard with at least 4Gigs of space
6 gigs of free space (for downloading sdcard image and uncompressing)
The SDCard Image: http://ge.tt/9rVFXxC?c
Linux/Mac Instructions
Open a terminal in Ubuntu by typing "terminal" in the search bar then hit enter
uncompress the Downloaded SDCard Image
Code:
cd ~/Downloads
tar -xvwzf ./AdamOutlerUbuntuTotalReFlash.tar.gz
With the SDCard or reader removed from the computer, get a list of all disks
Code:
ls /dev/sd?
Insert your sdcard or usb sdcard reader, then press the up key and enter to repeat the last command. The new device will show up as sdb, sdc, sdd or sde. each new device gets a higher letter. Note this newly plugged in device.(ie. /dev/sdc)
Use the following command to make your new SDCard, where "sdc" is the name of your SDCard device.
Code:
sudo dd if=./AdamOutlerUbuntuTotalReFlash of=/dev/sdc bs=4096; sync
Wait 5-20 minutes (depending on SDCard speed) until the image burning completes.
Shove it in your nook and turn it on by inserting the USB cable(do touch the power button, just insert the usb cable). Your nook will boot Ubuntu and perform a total factory restore. The process will take 15 minutes to complete with a Class4 micro SDcard.
Pro-tip: to copy and paste easily in Ubuntu, highlight text in the browser, then press the middle mouse button on the terminal.
Pro-tip: The tab key will auto-complete filenames.
Windows Instructions
Thanks to cyberma007 for Windows instructions.
Extract AdamOutlerUbuntuRecoveryImage with Winrar
Rename the resulting file to Add the .img extension to the filename
Download and open Win32 Disk Imager. note: The open source project can be found here: https://launchpad.net/win32-image-writer
Choose the drive letter of your SD Card from Win32 Disk Imager
Click the Write button
Turn of your nook and put in the SD Card and turn it back on.
Your Microsoft®™ Windows©®℠ computer sucks at reading anything except Microsoft formats. It cannot read the Open Source Linux EXT4 format. You will only see one partition after creating the SDCard but it will work fine. If you want to inspect the contents, install a Linux distribution on your computer.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Theory of operation
how it works
When you insert the SDCard and turn on the device this is what happens.
The device boots from SDCard.
The Ubuntu GUI will load. Personally, I recommend that you do not touch anything
You will be presented with a 100 Second countdown
If you wish to stop, press and hold power for 10 seconds before flashing has started
You will be presented with a progress bar status update only. Closing this will not affect the process. the only way to stop is to turn the device off.
At this point, the flashing process will begin
Flashing Process
After Ubuntu has booted here is the procedure which takes place
MLO partition will be written with all zeros, then flashed
U-BOOT partition will be written with all zeros, then flashed
RECOVERY partition will be written with all zeros, then flashed
BOOT partition will be written with all zeros, then flashed
BOOTDATA partition will be written with all zeros, then flashed
BOOTDATA is mounted and a command is sent to factory reset the device upon next boot.
FACTORY partition will be written with all zeros, then flashed in two parts to work around a 120 second filesystem operation bug.
A sync operation takes place to ensure all data is written to the device
SYSTEM partition is wiped with all zeros
SYSTEM partition is recreated as a blank EXT4 filesystem
CACHE partition is wiped with all zeros
CACHE partition is recreated as a blank EXT4 filesystem
SDCARD partition is wiped with all zeros
SDCARD partition is recreated as a blank FAT32 filesystem
A sync operation takes place to ensure that all data is written
You are notified to press and hold power. When the screen goes black remove your SDCard
note: Using a Class4 SDCard, the screen timeout will be aproximately 30 seconds after the entire operation has completed. Do not confuse screen-timeout (blank screen) with turning off the device (black, unilluminated screen). Turn the device off and then remove the sdcard or risk corrupting the data on the sdcard.
It's my intention that this may help someone. This will at least be one more method for people to try before giving up on restoration to 1.4.0. I generally receive 5-10 PMs per week requesting support on the acclaim_update.zip. Hopefully this will reduce those and give people another option to try.
Ubuntu isn't ready for daily use yet, but this recovery tool is more thorough than any other recovery method out there. I need some help porting the 3.0 kernel to the Nook Tablet.
Note: to neuter recovery and just use ubuntu, remove the file called /root/recovery from the sdcard before loading into your Nook.
Which kernel branch did you try to build?
Kuzma30 said:
Which kernel branch did you try to build?
Click to expand...
Click to collapse
I've tried several. The problem is in configuration. I eventually settled for the stock 2.6 android_4430BN_defconfig. It seems to function best for this until we have a proper 3.0 kernel.
Thanks Adam very nice work. Question what if we want to revert to 1.4.0 or 1.4.0 is it possible or we will be stick it lol. Can this be supported for dual/multi boot?
~ Veronica
Sent from XDA premium using my Nook Tablet
Very good work Adam.
I have one trivial question... Why on all your projects do you use Ubuntu and not any other distro?
lavero.burgos said:
Thanks Adam very nice work. Question what if we want to revert to 1.4.0 or 1.4.0 is it possible or we will be stick it lol. Can this be supported for dual/multi boot?
~ Veronica
Sent from XDA premium using my Nook Tablet
Click to expand...
Click to collapse
Thats what this does. It reverts you to 1.4.0. It uses Ubuntu as a dedicated recovery. If you would like to dual boot, just remove the /root/recovery file. You can boot Ubuntu or normal by inserting and removing the sdcard. But like i said, the touchscreen is wonkey and there's no way to fix most of the problems without a 3.0 kernel.
ShadowReaperGR said:
Very good work Adam.
I have one trivial question... Why on all your projects do you use Ubuntu and not any other distro?
Click to expand...
Click to collapse
I use Ubuntu on my desktop. I like Ubuntu because it has a large user base and if i come across a problem, it is easier to correct or has generally at least been discussed. For a mobile device, it makes more sense than other Linux distributions because newer versions have been optimized for touchscreens. In general, i find Ubuntu supports more things than other Linux distributions.
Hoster: http://ge.tt/ or 4shared.com both max. upload 2Gb/file.
AdamOutler said:
Thats what this does. It reverts you to 1.4.0. It uses Ubuntu as a dedicated recovery. If you would like to dual boot, just remove the /root/recovery file. You can boot Ubuntu or normal by inserting and removing the sdcard. But like i said, the touchscreen is wonkey and there's no way to fix most of the problems without a 3.0 kernel.
Click to expand...
Click to collapse
Gotcha! thanks Adams, i'll wait until it gets a better kernel, i love the Ubuntu idea .
My 2 cents for host: http://minus.com/
Great work, will monitor this. Would be nice to have Ubuntu fully working on the Nook Tablet (or Nook Color, for that matter -- seems like development on that has died, shame as they are now $129 refurbished direct from B&N)
Hi Adam,
When you say the screen is wonky what do you mean? Is it sort of 90degrees out like our original CM7 build was?
CelticWebSolutions said:
Hi Adam,
When you say the screen is wonky what do you mean? Is it sort of 90degrees out like our original CM7 build was?
Click to expand...
Click to collapse
Yes. Also, none of the native tools to correct this work because of lack of proc and sys support.
Such a shame, I quite fancied a dual boot with android/ ubuntu
It was a simple fix in the build.prop on CM7
Oh well hopefully somebody will come up with a suitable 3.0 for you soon
AdamOutler said:
Note: If someone has web hosting for a 1.5Gig file and nearly unlimited bandwidth, the instructions above can be reduced to only a few simple steps... download, uncompress, run command in terminal to make a disk image, boot from SDCard. Team Komin's server bandwidth does not allow this.
Click to expand...
Click to collapse
If you're still interested in doing this let me know. I can find a place to host it. Who knows how many people "bricked" their NTs from the CM7 beta - this seems to be the only logical fix if ADB doesn't work in CWM (which I'm experiencing (even from the SD version of CWM)). I haven't gotten a chance to confirm if this works or not yet for that issue (I'm waiting on a new microSD -> SD adapter), but if it works this would make it a lot easier.
Bit of problem in the end of setting up the sd
Everything goes quite fine but in the end when it is supposed to automount and than to copy the files from the recovery it behaves strange. Im a windows user so i have been using linux for 10hr now. Ill post later what it says .
@scsione889 . If you have web hostin i think you should send a PM to AdamOutler because he is quite busy. Because that would help a lot a lot. In the future also if we brick it again would be easier to do it in shorter steps. Because this one takes long and is a bit complicated to.
Here is the rehosted file and new instructions. Let me know if there are any problems so I can redo the first post.
You will need:
A Class 4 SDCard with at least 4Gigs of space
Ubuntu installed on Disk, USB drive, Wubi, or CD: http://ubuntu.com/download
6 gigs of free space (for downloading sdcard image and uncompressing)
The SDCard Image: http://ge.tt/9rVFXxC?c
Instructions:
Open a terminal in Ubuntu by typing "terminal" in the search bar then hit enter
uncompress the Downloaded SDCard Image
Code:
cd ~/Downloads
tar -xvwzf ./AdamOutlerUbuntuTotalReFlash.tar.gz
type "ls" to get a file listing and locate the name of the new file. (ie AdamOutlerUbuntuTotalReFlash).
With the SDCard or reader removed from the computer, get a list of all disks
Code:
ls /dev/sd?
Insert your sdcard or usb sdcard reader, then press the up key and enter to repeat the last command. The new device will show up as sdb, sdc, sdd or sde. each new device gets a higher letter. Note this newly plugged in device.(ie. /dev/sdc)
Use the following command to make your new SDCard, where "AdamOutlerUbuntuTotalReFlash" is the name of the uncompressed file and "sdc" is the name of your SDCard device.
Code:
sudo dd if=./AdamOutlerUbuntuTotalReFlash of=/dev/sdc
Wait 5-45 minutes (depending on SDCard speed) until the image burning completes.
Shove it in your nook and turn it on. The process will take 15 minutes to complete with a Class4 micro SDcard
Pro-tip: to copy and paste easily in Ubuntu, highlight text in the browser, then press the middle mouse button on the terminal.
Pro-tip: The tab key will auto-complete filenames.
Fixed Nook
AdamOutler said:
Here is the rehosted file and new instructions. Let me know if there are any problems so I can redo the first post.
Click to expand...
Click to collapse
Works hurrey.
My nook was not just bricked but more than that heeheh. I have tried with adb, CWM, with the flashable zip but none of them dident work. I did lose my hope to fix it actually.
But this method worked just fine. And with the last post it was way easier to make it to .
Thanks a lot Adam i have been hiting your thanks booton and ill hit it for some more days too.
I can tell that now if you want you can replace the first post with this one. Of that's what you want.
Thanks once more.
Fatos said:
Works hurrey.
My nook was not just bricked but more than that heeheh. I have tried with adb, CWM, with the flashable zip but none of them dident work. I did lose my hope to fix it actually.
But this method worked just fine. And with the last post it was way easier to make it to .
Thanks a lot Adam i have been hiting your thanks booton and ill hit it for some more days too.
I can tell that now if you want you can replace the first post with this one. Of that's what you want.
Thanks once more.
Click to expand...
Click to collapse
Glad you accepted my suggestion and tried it, well worth it in the end then
You'd gone a little bit further than the others that had just formatted the xloader, you'd got carried away and done the lot lol
Enjoy you're CM7 NT and DON'T format anything on there ever again!!!!
CelticWebSolutions said:
Glad you accepted my suggestion and tried it, well worth it in the end then
You'd gone a little bit further than the others that had just formatted the xloader, you'd got carried away and done the lot lol
Enjoy you're CM7 NT and DON'T format anything on there ever again!!!!
Click to expand...
Click to collapse
Haha as they say learnig by doing. Heheh now i know.
Thanks for sharing your time.
Adam, will it ever be possible to get this on streak 7 ?
I recently acquired an Asus EeePC (900 model) for practically nothing, and was frustrated by how slow WinXP ran on it (even after a fresh install). Being that it only has a 16GB SSD hard drive and I don't fully plan on dumping money into upgrading it, I figured it was ripe for some Android goodness. So, I've tried 3 different versions available at android-x86.org (2.2 R2, 3.2 RC2, 4.0 RC1). Each has their own pros and cons, but I've decided to stick with Froyo, as it seems to be the thoroughly most stable of the bunch.
Overall, I'm pretty happy with the whole thing. Boot-up times are lightning quick, and most things seem to work fast enough, but there is the issue of APK compatibility. I understand that the architecture between x86 and ARM processors lends to a lot of apps simply not working. I was hoping to use Google Voice and Groove IP to be able to make phone calls using my home's WiFi network. I have no problem establishing a strong connection (both through WiFi and Ethernet), and Google Voice installs and syncs to my account with no problem, but I can not get Groove IP to install. My grasp of it is that until Groove's makers build the program to work on x86 architecture, I'm out of luck.
That's all well and good, but are there any other options I can look into? Search terms I come up with are vague at best and generally lead to dead ends. It isn't a deal-breaker for me either way, it just seems like a decent use for this little netbook.
Could you tell me how did you boot android from usb\/ cause i think that u did it using usb not sd card. Cause i have eeepc 1202nl and i cant boot android 4.0 rc1. Did you change sth in cd image files?
I pretty much just followed the install instructions HERE.
I used UNetbootin to make a bootable USB stick. Since I posted this thread, I have since switched to the 4.0.1 version for the EeePC. As long as you have a decent WiFi connections, it runs amazingly. The nice thing about going the UNetbootin method, is that you can boot from the USB and run it like a "LiveCD" version without altering anything on your hard drive, or go through the business of formatting and doing a clean install.
Basically, just download the version of Android x86 you need from the website, download UNetbootin, and when they are done, put the USB drive in the computer you downloaded the ISO and program to.
On UNetbootin, here's how you do it.
1. Click on the bubble about 3/4 of the way down where it says "Disk Image"
2. If it doesn't say so already, select "ISO" from the drop-down menu.
3. Select the Android ISO you want.
4. On the very bottom, make VERY SURE it says "USB Drive" for Type and that you select the correct Drive Letter for your USB drive.
5. Press OK, let it do its thing. When it is finished, Click the button to Exit, then properly unmount and remove your USB drive.
With your netbook turned off, plug in the USB stick. When the BIOS screen comes up, press the ESC key on the keyboard to bring up the boot menu. From there, choose a "Live" installation to test it out and run it from the USB stick, or choose to install it on a partition of the hard drive.
One last bit of advice, if you do elect to do a full installation, it isn't a bad idea to partition your hard drive. The maximum amount of memory Android-x86 will recognize is 2GB (1GB as "onboard memory" and 1GB as a dummy SD card). If you did a 3GB partition on your hard drive, it will be plenty of space for the full install of Android-x86 with the maximum amount of memory, and you'll still have the bulk of the hard drive left for a Windows, Linux, etc installation.
So today I have enough time to try run android on my asus and i cant do it. As i know u are the only one person with android x86 on asus I have one ask:
1. unebootin is booting and i can choose option to run/install android
2. than i got "detecting android-x86....", "found at /dev/sdb1"
3. than change resolution and "A N D R O I D [email protected]:/ # _"
4. after that i got sth like this (sry cause i did it in paint, but i cant make screenshot/good photo):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(it's black screen with 5-6 white dots in right up corner) - it is staying until i dont turn off netbook
I think its cause that my asus has Nvidia ION graphic and i cant run android on it
But i thought that maybe u have similar problem and can help me...
Or some1 other has any idea?
Try a different VoIP client?
I tried Froyo again and it is working! But i dont know why other dont work (
IAmAN00bie said:
Try a different VoIP client?
Click to expand...
Click to collapse
What its mean? Maybe any tutorial - if exist?
I'm noob in linux (i know sth about android but only about phone versions).
EDIT: is there any possibility to root it? I dont want recovery, but SU and RootExplorer is what i want
Glad you got it working. The installs seem to be a little weird. I had to wipe and install 3 times before I got a fully functional ICS install on my roommate's EeePC.
As for root, you should have it. My ICS install came bundled with Superuser. The only issue I'm having is adding apps to the accepted list.
Card83 said:
Glad you got it working. The installs seem to be a little weird. I had to wipe and install 3 times before I got a fully functional ICS install on my roommate's EeePC.
Click to expand...
Click to collapse
After installing i got the same - Froyo is running perfectly, other not boot (even after 10 installs). I still have the same problem with black screen and dots. I ask on android-x86 site about this, maybe they know sth.
Card83 said:
As for root, you should have it. My ICS install came bundled with Superuser. The only issue I'm having is adding apps to the accepted list.
Click to expand...
Click to collapse
On Froyo i dont see any superuser.apk. Maybe its only on ICS (and GB or Honeycomb).
Hi its me again. I want to ask about one thing: have/had u problems with wifi connecting? Cause i cant connect to my router - i get remember but i cant connect.
Sent using r800i with DoomKernel v11 (1.21ghz)
ch3mn3y said:
Hi its me again. I want to ask about one thing: have/had u problems with wifi connecting? Cause i cant connect to my router - i get remember but i cant connect.
Click to expand...
Click to collapse
As far as getting an internet connection...
On Froyo, I am able to establish a connection with both WiFi and a wired ethernet connection.
On ICS, I can get a good WiFi connection, but no wired ethernet connection.
However, I put ICS on my roommate's EeePC with the standard HDD instead of the SSD that mine has and he was unable to connect to the WiFi. I'm not 100% sure why that was the case. I think his is a 700-series EeePC while mine is a 900-series.
Hi
I'm new to running android on my netbook but not new to android, and I was wondering whether there's an easy way to change the resolution?
Idk what the default resolution it uses but my HP Mini runs on the standard 1024x600.. this was the only fault I could find with running android x86
I changed the ppi using root explorer but no matter what change I make, on rebooting, the launcher FC's and I pretty much can't do anything else, so I have to reinstall the whole thing
Does anyone know how to change the res? Right now, it's probably something like 800 x 480 or something
Is there no official x86 port of Android? I thought I read about it somewhere... but can't find anything, so I'm probably mistaken. On the other hand though Intel has already released Android devices which run on their x86 processors. Are they not bound by the GPL (of Linux) to release the sourcecode? I am quite confused...
Unrelashade said:
Is there no official x86 port of Android? I thought I read about it somewhere... but can't find anything, so I'm probably mistaken. On the other hand though Intel has already released Android devices which run on their x86 processors. Are they not bound by the GPL (of Linux) to release the sourcecode? I am quite confused...
Click to expand...
Click to collapse
Currently, there is not an official x86 port.
Will there ever be? Probably.
When? I have no idea.
Hi guys,
Just want you to know, that I've for first, successfully
started USB MASS STORAGE mode on Sony Tablet S!!!
Without any additional software!
That USB MODE is not even available in system settings,
system notification on the device says:
"Connected as an installer" lol.
Gonna figure everything out, to be an easy to use
...and most probably I will add this feature in next AiO
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Its a good day
br
condi
thanks for all the effort you put in condi! i've tried 3 mass storage apps to no avail, i'm so glad that one of our favourite devs is working on this!
wow condi you make this better and better, hats off to you
Condi .. are you running ICS or HC in those screen shots? Just wondering why it says a system update is available?
Sent from my Sony Tablet S using XDA Premium HD app
He's running ics with Kernel 9. Newest is kernel 10 which is unrootable(?) at this point. That's why he's got the update notification
Sent from my GT-I9100 using Tapatalk 2 Beta-6
PurpleFries said:
He's running ics with Kernel 9. Newest is kernel 10 which is unrootable(?) at this point. That's why he's got the update notification
Sent from my GT-I9100 using Tapatalk 2 Beta-6
Click to expand...
Click to collapse
Sorry, but you completely missed the point. With Condi's AIO Tools you may spoof the device for system update to see it as an older firmware, it's also a part of a rescue-backdoor (but not the necessary part).
condi said:
Hi guys,
Just want you to know, that I've for first, successfully
started USB MASS STORAGE mode on Sony Tablet S!!!
Without any additional software!
That USB MODE is not even available in system settings,
system notification on the device says:
"Connected as an installer" lol.
Gonna figure everything out, to be an easy to use
...and most probably I will add this feature in next AiO
Its a good day
br
condi
Click to expand...
Click to collapse
Doesn't UMS normally leads to new drives appearing on the PC's file explorer, like while inserting an USB key?
In the case of the tablet, one drive for the internal SD card, another for the external one if there's one inserted...
The "gadget" link shown by your screenshots is neither what we expect for a MTP link. It reminds me what I see when connecting a device in fastboot mode.
But well... We will know all the story in next AiO!
Nesquick95 said:
Doesn't UMS normally leads to new drives appearing on the PC's file explorer, like while inserting an USB key?
In the case of the tablet, one drive for the internal SD card, another for the external one if there's one inserted...
The "gadget" link shown by your screenshots is neither what we expect for a MTP link. It reminds me what I see when connecting a device in fastboot mode.
But well... We will know all the story in next AiO!
Click to expand...
Click to collapse
OK then, for example - show me how you are working with your external SD on MTP mode, of course without taking it out and putting in card reader?
It will be also helpful for Linux and Mac OS users.
The 'gadget' is just as I expected to be.
Also 'gadget' reminds me a nice cartoon from my childhood - inspector gadget
Below is a quick video, sorry for quality and shaking hand lol:
sebarkh said:
Sorry, but you completely missed the point. With Condi's AIO Tools you may spoof the device for system update to see it as an older firmware, it's also a part of a rescue-backdoor (but not the necessary part).
Click to expand...
Click to collapse
Thank you. I thought it was something to do with that. I am unrooted ICS so I was just curious.
Sent from my Sony Tablet S using XDA Premium HD app
actually thats an ics feature available on storage menu
arturodelac said:
actually thats an ics feature available on storage menu
Click to expand...
Click to collapse
So, tell me the steps to turn it on.
There is no such option on this device.
On ICS it is. Like on my Galaxy S 2, but not here.
arturodelac said:
actually thats an ics feature available on storage menu
Click to expand...
Click to collapse
Nope, you're wrong. Do you think that I would spend some hours on trying to do something which is already done?
Nesquick95 said:
Doesn't UMS normally leads to new drives appearing on the PC's file explorer, like while inserting an USB key?
Click to expand...
Click to collapse
Oh Nesquick - one more example Try to open some file directly from 'mtp drive' - some .doc etc, modify it, and try to save it. You will not.
Its been copied to tmp dir, no 'direct access'.
Thats why I hate MTP mode.
Current state of my USB Mass Storage mode is which needs one reboot after running. Im trying to find the solution for direct change.
If we would have kernel access, then it would work already..
But we dont. To be continued
br
condi
Condi, I've no trouble with MTP... Or should I say, I've the same troubles as anybody else. Horrible on my Linux platforms, slow, uneasy to use and even worst whith my Nexus which has no SD card slot.
What I tried to say when looking at your screenshots was they aren't looking like something known : no drive on Windows explorer, no Sony tablet device, just the "gadget" link. Your video later shows an E:\CONDISD showing that you've win the race.
As I was saying, the "gadget" link appears when I connect something in fastboot mode to my PC (in the USB menu of my VirtualBox Windows XP VM to be precise) and I was thinking that you may have put your finger on some low level USB thing (showed by the tablet as an installer!) which could open some perspectives.
Of course, I know that you're the first here to see exploitable perspectives and one of the only people here able to do something with them but who knows...
By the way, I'm thinking of an adb based file explorer. No time to do it myself but many people have already done it. Just google "adb file explorer" and choose the one that best match your needs.
Nesquick95 said:
Condi, I've no trouble with MTP... Or should I say, I've the same troubles as anybody else. Horrible on my Linux platforms, slow, uneasy to use and even worst whith my Nexus which has no SD card slot.
What I tried to say when looking at your screenshots was they aren't looking like something known : no drive on Windows explorer, no Sony tablet device, just the "gadget" link. Your video later shows an E:\CONDISD showing that you've win the race.
As I was saying, the "gadget" link appears when I connect something in fastboot mode to my PC (in the USB menu of my VirtualBox Windows XP VM to be precise) and I was thinking that you may have put your finger on some low level USB thing (showed by the tablet as an installer!) which could open some perspectives.
Of course, I know that you're the first here to see exploitable perspectives and one of the only people here able to do something with them but who knows...
By the way, I'm thinking of an adb based file explorer. No time to do it myself but many people have already done it. Just google "adb file explorer" and choose the one that best match your needs.
Click to expand...
Click to collapse
I like Android Commander as an explorer using ADB (btw from aanother Polish dev)
Good morning folks,
fist want to say ... Condi well done .. I thing is a work in the right direction ..
Currently I use a workaround with apps like AirDroid as a WLAN file explorer.
Additional advantage, you need no USB cable (but WLAN connection).
So much hype... The topic died in 2 days...
[email protected] said:
So much hype... The topic died in 2 days...
Click to expand...
Click to collapse
?? lol
its in AiO as function, since v2.9, 06.05.12
:cyclops:
thanks man!!!! your works best for ever!!!! really thanks
PurpleFries said:
He's running ics with Kernel 9. Newest is kernel 10 which is unrootable(?) at this point. That's why he's got the update notification
Sent from my GT-I9100 using Tapatalk 2 Beta-6
Click to expand...
Click to collapse
That's not quite correct. I had kernel 10 for a while, then updated to r5. Not sure what kernel it was after update, but I was able to root with backup/restore method and now have build 5 kernel.
Sent from my HTC VLE_U using xda app-developers app
OCedHrt said:
That's not quite correct. I had kernel 10 for a while, then updated to r5. Not sure what kernel it was after update, but I was able to root with backup/restore method and now have build 5 kernel.
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Wow... Why even reply to that??? It is months old! He was referring to hc 3.2.1r2 where k10 was unrootable..
Hi,
I contacted gearbest to root my TV box and they sent me a link from Baidu. I tried to download it but I can't because it want a Chinese number to register. Somebody can download and upload on mega or something else the Rom? Thanks
Link: http://pan.baidu.com/s/1bpDQFhX Password: nd93
https://docs.google.com/uc?id=0B5VjVTtm8AqmX3gxa0pOcU5kNjg&export=download
However, this version is not pre-rooted, it is the latest release as of now (rel. date 2016-07-19).
To update:
Extract the 3 files (update.zip, factory_update_param.aml & recovery.img) to the SD Card
start the "update / backup" app on your box
select the update.zip and confirm
box will restart and install the new firmware
other version pre-rooted?
I try to find to root this tv box but i loose my time.
DIDIMR said:
other version pre-rooted?
Click to expand...
Click to collapse
All releases so far are not rooted. You can gain root access via ADB though.
I used adbLink to open the shell & "mount -o remount,rw /system".
Deleted the bootanimation and other things to test if it actually works... it does.
Editing the build.prop is also possible (ro.adb.secure=0, ro.secure=0, for example).
I tried to install my own version of TWRP 3.x, the command was successful ("dd if=/sdcard/recovery.img of=/dev/block/mmcblk1p6") but it didn't stick and the stock recovery was still active.
Since it's Marshmallow, I wasn't able to manually recreate the systemless root method.
I'm not going to try further for now, waiting if they will release an update, etc.
Bingo,
Can you make a root installer for this device or do we need chainfire to make a new SuperSU? I have 50 units that I need to root but can't find an installer. I need it for Titanium Backup to restore my custom setup.
atvbc said:
Can you make a root installer for this device? I need it for Titanium Backup to restore my custom setup.
Click to expand...
Click to collapse
I'm looking into it, but with my limited knowledge, most approaches seem to be a dead end due to Marshmallow. (It's also my first box ever bought in general...)
I already have my custom TWRP img ready, but it doesn't stick when I flash it.
ADB says it was "dd" successfully but rebooting straight to recovery brings up the stock recovery.
I hope someone beats me to it. ^^
I also wrote an inquiry, asking for an IMG file, so I can use with the customization tool... I don't think they have one ready yet...
And those twats sitting on the source files and can't poop out an alternative variant of the firmware with root? Beetch please.
AFAIK, all boxes with Android 6 are in this state (looked at some other firmwares).
The old tricks from Lollipop don't work here anymore, like booting a custom recovery.img from SD, etc.
edit: can't mount "sbin" as RW (ofc. knowing where it's coming from)
edit: tried an old signed ZIP (root update for Android 4.x) via stock recovery: it went through, verified... I'm afraid this won't work with a custom ZIP trying to recreate latest SuperSU install method...
atvbc said:
I have 50 units that I need to root but can't find an installer.
Click to expand...
Click to collapse
Ok Heisenberg, slow down... :laugh:
atvbc said:
...or do we need chainfire to make a new SuperSU?
Click to expand...
Click to collapse
SuperSU would work "ootb" but the stock firmware has no 'unzip' in 'sbin', so the original script will fail.
And since we don't have a custom recovery that can support 'unzip'. that's another dead end.
I tried flashing 3 different versions of my custom recovery zip (with diff. timestamp, etc).
They all went through without error but the device isn't even bothered, still brings up the stock recovery.
I also modified the original update.zip that contains the whole firmware with all partitions and just replaced the recovery.
Signed it, flashed it, no error, reboot... yup, stock recovery is still there. ^^
edit: small progress, I can now update the recovery... as proof I changed the "error pic" with the little droid and wrote something nice on it ^^
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Awesome Bingo Bronson! At least it's a start. Now if only we could get TWRP working on these... I've tried all the S905 TWRP img files available but no joy yet, at least not booting from microSD card. Android 6.0 Marshmallow has been rooted on several smart phones; can we learn something from those methods and maybe hack together a working root?
atvbc said:
I've tried all the S905 TWRP img files available but no joy yet
Click to expand...
Click to collapse
SDK 23 devices do things slightly different, yes, but the main reason for the old images not working is (ofc. ^^) the ramdisk cpio and the small but important differences in the hardware (boards) and the according references in the files.
I'm going through the ramdisk cpio piece by piece as we speak, takes "a while" for users like me...
Let's hope it will at least boot with an error and not just flicker and remain on the "Google TV" bootloader screen.
I'm editing the stock recovery from 2016-07-28 (language fix update).
If I fail numerous times, I will get on my knees and send Abdul the files and some monayyy. ?
edit: calling it a day... will continue tomorrow afternoon (GMT+1 ^^)
So basically if someone can get TWRP to boot on these then root should be fairly easy? I guess the only road block after that would be getting sbin mounted rw so we can install the SuperSU binary.
atvbc said:
So basically if someone can get TWRP to boot on these then root should be fairly easy? I guess the only road block after that would be getting sbin mounted rw so we can install the SuperSU binary.
Click to expand...
Click to collapse
I've used systemless root on a number of 6.0.1 devices... Qualcomm, MTK... based one the arch. this one should work just as well.
'sbin' is part of the ramdisk, so it's always 'ro' (hence: "knowing where it's coming from" ^^) so no need to try to force anything here.
Btw. that was the default 'sbin' from the stock system, the 'sbin' from a custom recovery has all the goodies on board.
Ramdisk: applying the changes necessary for TWRP is not that difficult, just need to finish the matching ramdisk cpio...
That being said, I haven't gotten anything done since my last post which is annoying... had to work on "non Android" related things.
Currently rechecking the blocks & partition table, so everything can be mounted properly (given it boots up ^^).
Any updates?
Eager to get this.
robinkooli said:
Any updates? Eager to get this.
Click to expand...
Click to collapse
I gave up with slapping it together manually, I may try again on the weekend when I'm able to use my Linux PC again and build it from source like it should be done...
If you want to try, your updater-script can look like this:
Code:
set_bootloader_env("upgrade_step", "3");
write_raw_image(package_extract_file("recovery.img"), "recovery");
show_progress(0.200000, 10);
set_bootloader_env("upgrade_step", "1");
set_bootloader_env("force_auto_update", "false");
I had the fstab files edited with the info from the block & partitions report but no success so far.
( I avoided porting / using old files from TV boxes running Android L based firmwares...)
Aldideos said:
Hi,
I contacted gearbest to root my TV box and they sent me a link from Baidu. I tried to download it but I can't because it want a Chinese number to register. Somebody can download and upload on mega or something else the Rom? Thanks
Link: http://pan.baidu.com/s/1bpDQFhX Password: nd93
Click to expand...
Click to collapse
Just download Kingroot or Kingoroot . One of the two will root it . And if successful try get supersume so you can get rid of the bloat they install and install SuperSU
Autolounge said:
Just download Kingroot or Kingoroot . One of the two will root it . And if successful try get supersume so you can get rid of the bloat they install and install SuperSU
Click to expand...
Click to collapse
I had already tried this, but no root
Aldideos said:
I had already tried this, but no root
Click to expand...
Click to collapse
Can you run CPUZ and post your specifications so I can find a method or possibly test certain methods if I have it .
My Mini M8S II doesn't go past logo screen after using Kongo Root (Windows edition) over ADB internet.
Autolounge said:
Can you run CPUZ and post your specifications so I can find a method or possibly test certain methods if I have it .
Click to expand...
Click to collapse
valid.x86.fr/a/zc7944
its a cpuz validation url. not allowed to post links due to this being a new account.
If anyone here has the skills to root this box and can prove it, I will donate one and pay for shipping if you're within Canada/USA. I'm looking for a zip file based root that can be applied from a flash drive or SD card (ezroot style).
Root
atvbc said:
If anyone here has the skills to root this box and can prove it, I will donate one and pay for shipping if you're within Canada/USA. I'm looking for a zip file based root that can be applied from a flash drive or SD card (ezroot style).
Click to expand...
Click to collapse
I am fairly certain I can put together something for you. I have a pretty good history with android, custom ROMS, blahblahblah. I have a Android box from Tops with the S905 in it and rooted mine manually from my laptop. I don't have this particular model but they can't be that different. What version of Android is this running?
Android 6.0,
ARM64
Kingo Root, KingROOT (APK's) don't work.
Kingo Root (Windows) bricked my M8S II ): .
Hi,
Recently i purchased Cube iWork10 Ultimate 64GB Intel Atom x5 Z8300 Quad Core 10.1 Inch Dual OS Tablet and something wrong went with android side, I am not able to use it so i search for official firmware and did not find. I found firmware for tablet SN number start as i15TC,i15TD and i15T.
http://www.cube-tablet.com/download
http://www.51cube.com/ch/DownList.asp?SortID=7
I installed following img on my device
https://forum.xda-developers.com/android/development/rom-stock-cube-iwork-10-flagship-i15-t-t3372281
Camera did not work at all. Second problem i can not change Auto rotate when i want (with game work like it should).
I resize partition by using Phone Flash Tool and X98 serie GPT file
https://4pda.ru/forum/index.php?showtopic=725568
https://techtablets.com/forum/topic/resize-android-partition-the-easy-way-for-x98-serie/
I contact resller (banggood) to provide me official firmware and unfortunately they ignore my email. Then I create new topic in thier site to ask about firmware and got link for firmware but i think i need password in order to download firmware. Here is my topic
http://forum.banggood.com/forum-topic-307419.html
Then i went to http://www.51cube.com/ to check if there is any email to contact them about firmware and i sent couple emails to most of them and unfortunately they ignore my email. I resent the same email and got answer from Eddy with official firmware ( i told Eddy that reseller ignore my email then he provided me link for official firmware).
https://pan.baidu.com/share/link?shareid=467329010&uk=3474489303#list/path=/
to download from pan.baidu.com i follow these step:
https://www.gizdev.com/download-files-pan-baidu-com/
Details about my device:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Anyone have idea how to root firmware for i15-TFL?
I think the correct place for my thread is to put it in xda-developers iwork-10
https://forum.xda-developers.com/t/iwork-10
but i am not able to do that because rules of this forum (to prevent spam, you must have a higher post count in order to make a new thread in this development section.�But feel free to make new thread in the non-development sections like General, Q&A, etc. Thanks for your understanding! )
Thanks in advance
Hello, I`ve met the same problem with same device with unknown revision serial "i15TFL": I`d flashed TWRP and Android stop starting proper.
Have you managed to restore the original Android on your device? Please give me instruction how to do this, and, if you could, post firmware files to Google Drive (Baidoo cloud speed really low).
nm101 said:
Hello, I`ve met the same problem with same device with unknown revision serial "i15TFL": I`d flashed TWRP and Android stop starting proper.
Have you managed to restore the original Android on your device? Please give me instruction how to do this, and, if you could, post firmware files to Google Drive (Baidoo cloud speed really low).
Click to expand...
Click to collapse
I resize partitions and restore the original firmware on my device by using Phone Flash Tool 5.3.4.1 and X98 serie GPT file ( i have chosen gpt_20g_org)& TWRP Boot.
In the android firmware, replace the file gpt.bin
On the computer, install and run the Intel Phone Flash Tool . Click Browse ... , select the flash.json file, in the Configuration: field , set the recover option .
We translate the tablet into DNX FASTBOOT MODE , for this, on the off tablet simultaneously press and hold the On and both volume buttons . USB-cable connect it to the computer, make sure that the program saw it and click Start to flash
The first launch will take a lot of time, be patient
Then i installed window.
Everything worked like it should but without root
I can upload firmware to Google Drive but can not post link coz (To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!)
All data will be deleted. Everything you do, you do at your own risk.
Mathias31 said:
I resize partitions and restore the original firmware on my device by using Phone Flash Tool 5.3.4.1 and X98 serie GPT file ( i have chosen gpt_20g_org)& TWRP Boot.
In the android firmware, replace the file gpt.bin
On the computer, install and run the Intel Phone Flash Tool . Click Browse ... , select the flash.json file, in the Configuration: field , set the recover option .
We translate the tablet into DNX FASTBOOT MODE , for this, on the off tablet simultaneously press and hold the On and both volume buttons . USB-cable connect it to the computer, make sure that the program saw it and click Start to flash
The first launch will take a lot of time, be patient
Then i installed window.
Everything worked like it should but without root
I can upload firmware to Google Drive but can not post link coz (To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!)
All data will be deleted. Everything you do, you do at your own risk.
Click to expand...
Click to collapse
Thanks.
Please send me link to firmware and utilities using PM or email: "m e l n i k o v s m 2 @ g m a i l . c o m" without spaces. I have no time to wait until it will be downloaded with Baidoo speed (~10kbps). Thanks in advance, you'll seriously help me.
Mathias31 said:
All data will be deleted. Everything you do, you do at your own risk.
Click to expand...
Click to collapse
Even Windows 10 installation will be wiped?
P.S. Send me firmwares GDrive links pleeeaasee.
nm101 said:
Thanks.
Please send me link to firmware and utilities using PM or email: "m e l n i k o v s m 2 @ g m a i l . c o m" without spaces. I have no time to wait until it will be downloaded with Baidoo speed (~10kbps). Thanks in advance, you'll seriously help me.
Click to expand...
Click to collapse
I have sent pm to you with sharing link (android firmware for i15-TFL). Sorry for delayed response
nm101 said:
Even Windows 10 installation will be wiped?
P.S. Send me firmwares GDrive links pleeeaasee.
Click to expand...
Click to collapse
Yea even win 10 will be wiped, you have to re install it. I have sent pm with android firmware link for i15-TFL. I had uploaded to google drive
Thank you wery much. I am even managed to get working Remix OS and Rooted stock Android (I don`t test it, but it should work) images.
How to install:
1. Download this firmware and flash via Intel Platform Flash Tool.
2. Put Rooted stock Android or Remix OS zip into internal memory or sd card.
3. Make sure you had activated "Enable OEM Unlock" in Android Developer`s menu.
4. Boot into recovery (choose android boot then hold Volume Down, in appeared menu choose recovery, device will reboot, then again choose android.. welcome to TWRP).
5. Install zip via TWRP.
Notice: Never never ever upgrade SuperSU APK. After upgrade it`s unable to update binary and stop functioning at all.
Notice: At RemixOS cameras does not work at all.
nm101 said:
Thank you wery much. I am even managed to get working Remix OS and Rooted stock Android (I don`t test it, but it should work) images.
How to install:
1. Download this firmware and flash via Intel Platform Flash Tool.
2. Put Rooted stock Android or Remix OS zip into internal memory or sd card.
3. Make sure you had activated "Enable OEM Unlock" in Android Developer`s menu.
4. Boot into recovery (choose android boot then hold Volume Down, in appeared menu choose recovery, device will reboot, then again choose android.. welcome to TWRP).
5. Install zip via TWRP.
Notice: Never never ever upgrade SuperSU APK. After upgrade it`s unable to update binary and stop functioning at all.
Notice: At RemixOS cameras does not work at all.
Click to expand...
Click to collapse
Np. Thank you for sharing your experience. I knew this method and its for re install android firmware but still have 2 problems I have mentioned it(check out first post) Camera did not work at all. Second problem you can not change Auto rotate when you want (with game work like it should). Also there is video showing how to install RemixOS in our devices, search in youtube ([SL] 043 Cube Iwork 10 Ultimate: How to flash ROM + root + MIUI + play.google + 512mb videocard - YouTube). You can follow the same step to install different img. I tried 6 different img and all of them have the same problem with auto rotate and camera. I resized partions coz android side have just 8 GB and its not enough for my games.
all imgs which i found and img which you provided not for i15-TFL . Its for iWork10_V1 and i15-T
But at rooted android image everything ok with camera and autorotation, after 1 day of RemixOS usage I decided it's better for me to return to stock os, but I also need root permissions. So, my experience is successful, everything still unresolved is sd card unmount during device sleep. But I detected it even on stock image.
nm101 said:
But at rooted android image everything ok with camera and autorotation, after 1 day of RemixOS usage I decided it's better for me to return to stock os, but I also need root permissions. So, my experience is successful, everything still unresolved is sd card unmount during device sleep. But I detected it even on stock image.
Click to expand...
Click to collapse
For me with rooted android img camera & auto rotation. I had problem with sd card mount and unmount and i fixed it by uninstall supersu and install just busybox. Then i decided to resized partions ( 20 GB for android and rest for win) and i used sd in win side to install program&game. To do that search in youtube (Install any Windows programs or applications on microsd card Tech Guy Charlie).
Hello thank you for your Help.
The Root is there and the auto rototion is working.
But i have one problem there, the canera is not working after installing the rom via TWRP.
Is it a bug?
Mathias31 said:
For me with rooted android img camera & auto rotation. I had problem with sd card mount and unmount and i fixed it by uninstall supersu and install just busybox. Then i decided to resized partions ( 20 GB for android and rest for win) and i used sd in win side to install program&game. To do that search in youtube (Install any Windows programs or applications on microsd card Tech Guy Charlie).
Click to expand...
Click to collapse
Do either @Mathias31 or @nm101 have links to the firmware and ROMs which you used to resolve the rotation and camera issues you experienced? I tried the previous links and it looks like they have expired....
denndsd said:
Hello thank you for your Help.
The Root is there and the auto rototion is working.
But i have one problem there, the canera is not working after installing the rom via TWRP.
Is it a bug?
Click to expand...
Click to collapse
Did you get your camera to work? My rotation and camera are not working...
OEM Win10 and Android both (GDrive)
I'd uploaded this one year ago at 4pda (russian forum), but totally forget about this thread.
Also, as I noticed, camera and rotation sensor works right on original firmware only.