I tried everything, but it is imposible to put the uefi into legacy mode, so the tablet never boot from USB... Has anybody an idea how I can install Android? Is it possible to flash something on the tablet from an other computer?
Sent from my C2105 using XDA Free mobile app
The Acer Iconia W3-810 is a Windows-based tablet that was released in 2013. While it may be possible to install Android on the device, doing so would require a significant amount of technical knowledge and may not be a straightforward process.
In general, the process of installing Android on a device that was not designed for it (such as a Windows tablet) is called "flashing" or "installing a custom ROM." Before attempting to install Android on your Acer Iconia W3-810, you should be aware that doing so can potentially damage your device, void your warranty, and could potentially render your device unusable.
If you are interested in trying to install Android on your Acer Iconia W3-810, I would recommend doing some research online to find resources and guides that can help you with the process. Keep in mind that this process is not officially supported by Acer, and any modifications made to your device are done at your own risk.
Related
Any ideas on how to update the Android OS from (Gingerbread) Android (2.2) to something higher like (android 4.0) Without Needing a Root?
Use kfu to install twrp and firefirefire. Then flash a rom from there.
If the reason you're scared of root is because you want/need your warranty, don't worry. Amazon cannot tell if you rooted when you unroot before claiming the warranty. If you're unable to unroot because your device is bricked etc., then they usually can't even know if its rooted anyway. (Unless of course you only thought it was bricked but it wasn't really.) Trust the devs here, and just go to http://goo.gl/DtVyY and enjoy a pure android tablet!
I've got a nexus 7 (2013) on android 6.0. Over the two years I've spent with it, I've ran into many features that require root. Now I've finally decided to do it. Right now, I'm doing it for the multi window thing.
Q.1: How long will Nexus 7 OTA updates continue to come?
Q.2: Will I get a notification that I got a system update if I'm rooted? And will I be able to keep my root while updating?
Q.3: I found a way for rooting the Nexus on Lollipop through one click( I think wugtoolkit). Will it work on Marshmallow? If not, whats the easiest way, preferably without connecting it to a computer?
Q.4: Any risks or cons? I've heard its impossible to brick a Nexus, is it true?
Thanks 
Tranquility. said:
I've got a nexus 7 (2013) on android 6.0. Over the two years I've spent with it, I've ran into many features that require root. Now I've finally decided to do it. Right now, I'm doing it for the multi window thing.
Q.1: How long will Nexus 7 OTA updates continue to come?
Q.2: Will I get a notification that I got a system update if I'm rooted? And will I be able to keep my root while updating?
Q.3: I found a way for rooting the Nexus on Lollipop through one click( I think wugtoolkit). Will it work on Marshmallow? If not, whats the easiest way, preferably without connecting it to a computer?
Q.4: Any risks or cons? I've heard its impossible to brick a Nexus, is it true?
Thanks 
Click to expand...
Click to collapse
I'm not a dev, but I have some experience rooting the N7 (2012 and 2013).
1) Well, it looks like 6.0 isn't coming to the N7 2012, so there is a good chance support for major versions will be dropped soon (within the next year?). They might continue to release patches and security fixes for 6.x a year or two after that, like they appear to be doing with the N7 2012, but this is all speculation. There are probably number crunchers looking at the sales figures and survey results to gauge interest, and there were some rumors recently of a new N7 possibly in the works. Those will both factor into whether support will continue.
2) You will get a notification, but everything I've seen has indicated that the install will fail (won't brick the tablet, but will just show an error and reboot to its previous state). What I think most people do, including me, is just flash the stock image in 'no wipe' mode and re-root after the update. You can also sideload the OTA update, depending on rooting method (I think, but haven't done this myself). Lastly, if you don't mind reconfiguring all your apps or if you have a good backup scheme, you can just do a fresh install then root. I have never had trouble flashing stock in no-wipe and re-rooting, but I've heard some people have had problems. (It's worth noting that if your bootloader hasn't been unlocked, you will have to wipe the device anyways. The unlocking survives flashing, so it's a 'one and done' thing. You only really need to lock it again if you're sending it in for warranty service.)
3) Wug's toolkit is currently borked for most people (version 2.0.6), so avoid it until the thread in the N7 development subforum has some success stories. Also, rooting in Marshmallow is possible, but seek out instructions specifically for M and use the latest versions of any linked utilities (like SuperSU and TWRP). I used Wug's toolkit 90% of the time for updating and rooting, and when it works, it's a breeze. It might be worth waiting for it to be updated to address the current issues. You can use the previous version to do some basic things and as a launchpad for manual tweaking, but the main, one click and done options will not work - I tried and was greeted with a bootloop due to an out of date SuperSU. But, in version 2.0.5 you can unlock the bootloader and flash the latest stock (haven't tried the U or V versions, but MRA58K worked fine). From there you have to root mostly manually, but there are shortcuts for some of the steps in the Advanced Utilities section.
4) It's always possible to brick a device, but it's very rare. There are 2 kinds of 'bricks'. 'Hard' brick is what most people worry about - something happens that prevents access to even the lowest level of the device. It's as if there was a hardware failure. 'Soft' bricking is what less tech literate people equate to hard bricking because to them the device is useless. In reality, it's a software issue that prevents some early stage of the boot up process. It is almost always recoverable with enough time and research. In basic computer terms, hard bricking is failing to post and soft bricking is failure of the OS to load (basically, though there are nuances). With root, you have access to everything and you're trusting whatever you install that takes advantage of that power to use it wisely. An ad blocker shouldn't need to adjust the CPU voltages. This is rare if you don't intend to overclock or mess with low level hardware tweaks. It is much more likely, but still pretty rare, to soft brick the device, which means you just have to reflash the system image. Worst case is you have to wipe the device and start over, or spend a few hours researching exactly what caused it.
Hope that helps. I'm not an obsessive ROM flasher and my experience has been only with Nexus devices, but these are my impressions.
Thanks a lot for your detailed reply.
1) I was under the impression that 6.0 would be the last updated for Nexus 7. Guess I'm wrong.
2) How long would "flashing the stock image in no wipe mode" take?
3) I'll wait then for an updated version ._.
4) Guess if I follow the steps correctly that won't happen. Prepared to take the risk.
Tranquility. said:
Thanks a lot for your detailed reply.
1) I was under the impression that 6.0 would be the last updated for Nexus 7. Guess I'm wrong.
2) How long would "flashing the stock image in no wipe mode" take?
3) I'll wait then for an updated version ._.
4) Guess if I follow the steps correctly that won't happen. Prepared to take the risk.
Click to expand...
Click to collapse
Android M is the last official update for N7 2013, the first gen N7 is done with updates. Once rooted you will not get any OTA updates anyway.
Flashing usually takes about 3-4 minutes. Booting up can take up to 10-15 min.
Just don't root on M until a stable method has been discovered.
Kay thanks.
Could you please update me when a stable way is found? Or at least provide a link where I can check myself.
You can check the marshmallow and the beta thread for updates. http://forum.xda-developers.com/apps/supersu
Tranquility. said:
Kay thanks.
Could you please update me when a stable way is found? Or at least provide a link where I can check myself.
Click to expand...
Click to collapse
You can root 6.0 pretty easy if you have fastboot installed. I've done it and can confirm it works. You just need to download the ElementalX-N7 kernel and SuperSU to your device then flash TWRP in fastboot then flash the kernel and SuperSU in TWRP. There are threads on here I believe with instructions to help you. If you need any help you can message me.
The beta SuperSU and elementalx method worked great for me and seems totally stable. I'd recommend learning fastboot/adb as mentioned. That has saved me a few times from the dumb things I've done messing around with root access.
Sent from my Nexus 7 using XDA Free mobile app
Rooting
As I mentioned in a previous post rooting using TWRP, SU I don't think fully roots
the device. When I loaded Multi-Rom, it installed in the usual fashion but only boots to the TWRP recovery utility.
In the past, one could globally root the device but the problem appears new.
Kurt
Hi all, i've got an old Galaxy Tab 3 8.0 that's been kicking around a few years.
Just went to update it, and it is saying that officially the latest update it has is 4.4.2, which is like getting towards 5 years old.
As far as i can tell, there isn't anything explictly preventing the tablet having a 'better' version of Android on it. Am i wrong?
If not, how can you trick/force the system into downloading it, and what is 'safe'?
EDIT: I mean.. it still uses the Menu button for chrissake.... and you can't disable apps you dislike (afaik)
Cheers,
Sam
kahlzun said:
Hi all, i've got an old Galaxy Tab 3 8.0 that's been kicking around a few years.
Just went to update it, and it is saying that officially the latest update it has is 4.4.2, which is like getting towards 5 years old.
As far as i can tell, there isn't anything explictly preventing the tablet having a 'better' version of Android on it. Am i wrong?
If not, how can you trick/force the system into downloading it, and what is 'safe'?
EDIT: I mean.. it still uses the Menu button for chrissake.... and you can't disable apps you dislike (afaik)
Cheers,
Sam
Click to expand...
Click to collapse
I'm not sure I even want to recommend this, but you might want to look HERE.
Also, you seem to completely new to this whole process of modifying your tablet, so I will give you a little general info. You can't trick your device into updating itself to a software version that doesn't exist for device. The software will only work if it has been customized for your specific device (T310). But, there are custom roms that are made for the T310 with newer version of Android (such as the one at the link above).
You can remove any app you wish to remove, simply by "rooting" your device. The T310 is easily rootable. Do a little reading about "rooting Android" and custom recoveries to understand what benefits it provides.
Read, read, read...then read some more. Then, you may want to install a custom rom.
gr8nole said:
I'm not sure I even want to recommend this, but you might want to look HERE.
Also, you seem to completely new to this whole process of modifying your tablet, so I will give you a little general info. You can't trick your device into updating itself to a software version that doesn't exist for device. The software will only work if it has been customized for your specific device (T310). But, there are custom roms that are made for the T310 with newer version of Android (such as the one at the link above).
You can remove any app you wish to remove, simply by "rooting" your device. The T310 is easily rootable. Do a little reading about "rooting Android" and custom recoveries to understand what benefits it provides.
Read, read, read...then read some more. Then, you may want to install a custom rom.
Click to expand...
Click to collapse
Excellent, that was the sort of thing i was looking for, thanks.
I am a little surprised to find the software is so restrictive, i guess i'm used to the idea of OS'es like Windows which don't care about the specific hardware they're in, as long as it can run it.
I will naturally do my research into the process and the risks before doing anything that would void the (albeit expired) warranty.
Thanks again,
Sam
gr8nole said:
I'm not sure I even want to recommend this, but you might want to look HERE.
Also, you seem to completely new to this whole process of modifying your tablet, so I will give you a little general info. You can't trick your device into updating itself to a software version that doesn't exist for device. The software will only work if it has been customized for your specific device (T310). But, there are custom roms that are made for the T310 with newer version of Android (such as the one at the link above).
You can remove any app you wish to remove, simply by "rooting" your device. The T310 is easily rootable. Do a little reading about "rooting Android" and custom recoveries to understand what benefits it provides.
Read, read, read...then read some more. Then, you may want to install a custom rom.
Click to expand...
Click to collapse
Thanks! Works for me
Hello, my name is WatchersGrim.
I have worked with coding for a little while back in the day and use to root and jailbreak devices for a long time. Going from my old Galaxy J3 from sprint to Galaxy S9, I was excited to finally do root on better hardware. Then came around to finding out that US models with Snapdragon processors don't allow OEM unlock and are not able to be rooted. This started a dilemma in my head. How are we able to fix this and work around it. So one, many of us know that something will probably change a few years down the line with samsung as TWRP recovery has been found to be working on snapdragon processors in different countries. Secondly, without TWRP, is it possible to trip a javascript object(knowing that most of android OS coding is done in javascript) to enable the OEM object to be able to have access.?Possibly could work but may need a different method to do so(I.E. triggering the effect with a custom file that loads on a SDCARD the moment the phone reads it, or creating a program along the line of ODIN to do the same effect.). Thirdly, is it possible to manipulate the hardware itself to allow third party hardware to manipulate the system? If doing so, will it cause a fault in the internal system? I know it would void warrenty but I do not know if it has a security fault that locks the system when dealing with hardware tampering.
I just want to see what you guys think and see if we can brainstorm idea's to help these great dev's!
can you do anything to trick android into running a modifyable file as root?
Hi,
Just bought a used M30. Model SM-305F. Android 9 (1 Nov 2019). I am still confused after reading through these posts:
[Rom][ANDROID 10 | Stock n Rooted Firmware | M305FDDU3CSL4
[Rom][ANDROID 10-Q | Stock & Rooted Firmware | M305FDDU5CTF2]
[Guide] Galaxy M30 Recovery, EDL Modes, Reset & Soft Reset
I am familiar with rooting Pixel devices and using ADB and FASTBOOT. With Samsung M30, it appears we need a software called ODIN which runs on Windows. Which unfortunately I don't have. Is it possible to root without using ODIN? And if so, I would appreciate some guidance.
2LoT said:
Hi,
Just bought a used M30. Model SM-305F. Android 9 (1 Nov 2019). I am still confused after reading through these posts:
[Rom][ANDROID 10 | Stock n Rooted Firmware | M305FDDU3CSL4
[Rom][ANDROID 10-Q | Stock & Rooted Firmware | M305FDDU5CTF2]
[Guide] Galaxy M30 Recovery, EDL Modes, Reset & Soft Reset
I am familiar with rooting Pixel devices and using ADB and FASTBOOT. With Samsung M30, it appears we need a software called ODIN which runs on Windows. Which unfortunately I don't have. Is it possible to root without using ODIN? And if so, I would appreciate some guidance.
Click to expand...
Click to collapse
You either need Odin on Windows, or Heimdall in Linux and the associated dependencies
You have what OS on your PC? If Windows the Odin is available in the above posts as well. It is very easy.
vdbhb59 said:
You either need Odin on Windows, or Heimdall in Linux and the associated dependencies
You have what OS on your PC? If Windows the Odin is available in the above posts as well. It is very easy.
Click to expand...
Click to collapse
I have Linux and macOS machines. I have looked at Heimdall, it seems the code is not updated since 2013. So I am not sure if it is OK. I can manage to get a Windows machine to run Odin. I was hoping there could be a way to to root the M30 without using specialized software.
Sorry for another silly question as I am not familiar with Samsung devices. It appears that when you root a Samsung device, this would trigger something that Samsung would know that you have rooted your device. What is this? And what can Samsung do to my device?
I used to root OnePlus, Nexus, Pixel devices. The manufactures nor the telecom providers doesn't care about what I do to the device. I even sent my rooted Pixel3 for warranty and it was accepted no problem.
2LoT said:
I have Linux and macOS machines. I have looked at Heimdall, it seems the code is not updated since 2013. So I am not sure if it is OK. I can manage to get a Windows machine to run Odin. I was hoping there could be a way to to root the M30 without using specialized software.
Sorry for another silly question as I am not familiar with Samsung devices. It appears that when you root a Samsung device, this would trigger something that Samsung would know that you have rooted your device. What is this? And what can Samsung do to my device?
I used to root OnePlus, Nexus, Pixel devices. The manufactures nor the telecom providers doesn't care about what I do to the device. I even sent my rooted Pixel3 for warranty and it was accepted no problem.
Click to expand...
Click to collapse
Actually the only way to do it with Samsung is via ODIN or Heimdall. Even Odin only works.
Moreover, rooted or non rooted the service centre blokes do not even understand. They just factory reset and change hardware parts. So..
Samsung has Knox which trips for various reasons and not just due to root.
2LoT said:
Hi,
Just bought a used M30. Model SM-305F. Android 9 (1 Nov 2019). I am still confused after reading through these posts:
[Rom][ANDROID 10 | Stock n Rooted Firmware | M305FDDU3CSL4
[Guide] Galaxy M30 Recovery, EDL Modes, Reset & Soft Reset
I am familiar with rooting Pixel devices and using ADB and FASTBOOT. With Samsung M30, it appears we need a software called ODIN which runs on Windows. Which unfortunately I don't have. Is it possible to root without using ODIN? And if so, I would appreciate some guidance.
Click to expand...
Click to collapse
I just realized. If you can patch just the boot.img it should work. But there are chances of bootloop and you may need to flash full rom again (may)..