yashsingh1/xdaforums huggingface dataset:
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] Solarenemy68:
If you bought it through a web store then clicking their user agreement is the same as your signature. If you bought it at a store and signed nothing then it is you against the corporation. Good luck.
[Galaxy Note II Q&A, Help & Troubleshooting] M.yaseen:
My Note II N7100 Stuck at the boot Screen

I tried to flash philz_touch and CWM by Odin3.09 but it didnt work

every time I try to get to recovery mode

I get this message

E:failed to mount /cache (Invalid argument ) can't mount '/cache' (Invalid argument )

E:failed to mount /system (Invalid argument ) can't mount '/system' (Invalid argument )

a pic of the message is attached

I dont know what to do

I almost tried every thing I know

Please help
[Galaxy Note II Q&A, Help & Troubleshooting] watsinaname:
There has to be something sinister with all Note 2 dying around the same time, I have run into same trouble, and only hope is a costly motherboard replacement, I see several others reporting the same
[Galaxy Note II Q&A, Help & Troubleshooting] edong23:
Do these at your own risk.

search for PIT file made by dr ketan and flash it together with the stock n7100 firmware in odin. that will solve tour problem.

somebody posted pit file here.. be sure that your n7100 is 16gb

http://xdaforums.com/showthread.php?t=1927983

extract it and use that together with the stock firmware in odin. select pit for pit files and pda for stock firmware

after finish flashing it will be stuck again in samsung logo. boot again to recovery mode and wipe data/reset to factory mode and then reboot
[LG Optimus L90] angelgaa:
Im running pacman rom 4.4.4, the problem is that if i call someone, and then hang up, it wont hang up till after a while, i will take 2 minutes or longer to hang up, anyone have the same issue?
[Verizon LG G2] techbeck:
For some reason, System (SDCARD) Usage is sucking up a lot of battery (when idle) on my LG G2 CM11 M12. I did the normal fixes I found with a Google search but cannot figure out what is going on. After about 1.5hrs, 20 percent battery is used.

Anyone have any ideas on what I can try to fix this? Seriously annoying.
[Nexus 6 Q&A, Help & Troubleshooting] Ironkidz:
So I was playing around with my settings and decided to give battery saving a whirl. The first thing I noticed was the completely backwards design of the UI color language in this mode. Considering the N6 has an amoled, it was perplexing to find that batter saving mode used a bright orange theme instead of a black one. I would have thought the screen technology would have made a black theme a natural fit. Is anyone else confused by this decision? Is there a setting I am missing?
[Nexus 6 Q&A, Help & Troubleshooting] biggiestuff:
Haha you definitely have a good point. Designer probably slapping himself in the forehead. I guess the thought behind it is that making it dark wouldn't apply to all phones since some use lcd panels plus the bright color is a warning to remind you to charge your phone
[Nexus 6 Q&A, Help & Troubleshooting] zephiK:
This feature on Android is for every phone, not just exclusive to the Nexus 6. Other phones that utilize a IPS screen doesn't need a dark background.

Although, you do have a point, it is odd that Motorola chose a AMOLED screen over a IPS when Lollipop is "white" and white uses more battery than blacks on AMOLED screens.
[Android Q&A, Help & Troubleshooting] whgarner:
Anyone have one or know anything about it or rooting the unit?

Android™

Intel Celeron J1850 Quad-core 2 GHz

21.5" Full HD (1920 x 1080) 16:9

Intel HD Graphics with Shared Memory

2 GB, DDR3 SDRAM

500 GB HDD

thanks

b.g.
[Android Q&A, Help & Troubleshooting] Soul0Reaper:
I saw this go on sale on eBay. I'd like to know as well.
[Android Q&A, Help & Troubleshooting] whgarner:
Info base

Got one works great, heavy. No info yet. Like the 500gb system memory. no usb debugging option, only via ethernet, have not yet accessed it. No root, super su , nor busybox will install. haven't looked into bootloader or recovery yet.

b.g.
[Android Q&A, Help & Troubleshooting] whgarner:
things I think I know

Had to use ethernet cable, setting address to 192.168.42.10 as the asus will put a hard address of 192.168.42.1 255.255.255.0. Able to adb by "adb connect 192.168.42.1" pinged it first to make sure network setting ok. Standard ethernet cable from asus directly to pc. Prob need binaries from intel system, either from a linux based machine or tablet/phone intel based. was able to adb reboot into either recovery (e3) or bootloader (droidboot), could not get fastboot to give commands to the asus, always "waiting for device", it would still ping however. Droid explorer crashes when attempting access, suspect it tries via usb.

Need someone smarter than me to jump in.

b.g.
[Android Q&A, Help & Troubleshooting] geminihc:
thanks for the small info, would like to know about full root as well.
[Android Q&A, Help & Troubleshooting] whgarner:
tablet

if I could find a screen protection and case for it, I could put those ipads to shame, when I go out.

b.g.
[Android Q&A, Help & Troubleshooting] geminihc:
hehe, you surely would get a workout as a benefit!
[Android Q&A, Help & Troubleshooting] whgarner:
more little things

Still no progress, except in bootloader, only open port is 1234, that being said. still cannot connect with fastboot; however, when I "adb connect" to this tcpip;port in the bootloader and adb devices comes back as "192.168.42.1:1234 offline".

I'm thinking I'm at the end or there maybe another bootloader type program on sdcard to access, as droidboot appears to looking for an update on drive "e".

b.g.
[Android Q&A, Help & Troubleshooting] geminihc:
a littl off topic, but does anyone know how to open and install more memory ram? what kinda ram does it take?

sodimm?
[Android Q&A, Help & Troubleshooting] whgarner:
Ram

No ram access panels at all. Do not even see in storage all HD. see screenshot
[Android Q&A, Help & Troubleshooting] whgarner:
unknown command 'CNXN'

In the bootloader, when i issue "adb connect 192.168.42.1:1234" i get the following response from the aa3 "unknown command 'CNXN'"

b.g.
[Android Q&A, Help & Troubleshooting] geminihc:
interesting, i ask because here: http://us.acer.com/ac/en/US/content/model/DQ.STPAA.001 (press full datasheet and search for 8gb) it seems to indicate there is one slot that you can install up to 8gb of ram. "SDRAM"
[Android Q&A, Help & Troubleshooting] geminihc:
i opened up the back to see what was inside. the 500gb hard-drive is definately easily replacable with SSD (the problem is seeing if it'll boot). most things were covered and the only thing exposed is some unknown PCB board. it does have some places where you can plug things in it seems like...

https://plus.google.com/photos/1132...s/6093720382613628977?authkey=CK3xwte3qpiv2QE
[Android Q&A, Help & Troubleshooting] whgarner:
Bootloader(droidboot)

The bootloader is definitely looking at the ext sd slot for its command when it boots up. It says "no valid installer found" on the "E" drive. If I put a file named "installer.cmd" in the root directory of the sdcard then I get a valid installer found. Tried placing "fastboot reboot" into installer.cmd with and without quotes, but no reboot. Need to find how to script installer.cmd to accept a command.

ps-nice pictures, good to see people interested

b.g.
[Android Q&A, Help & Troubleshooting] geminihc:
this might be a stupid question but is the bootloader phyiscally located in the 500gb hard-drive or else where? i was wondering what happens if we swap out the drive with say, a drive that is loaded with windows. what happens when you power on? i believe all of the components on this has drivers and everything already recognized by windows 8.
[Android Q&A, Help & Troubleshooting] whgarner:
Pulling hd

Might be a problem booting without proper bootloader in firmware, no bios or efi access, probably wouldn't hurt it. Wondering if pulling hd and accessing in linux or osx would allow you to place correct binaries for root? Thanks for idea.

b.g.
[Android Q&A, Help & Troubleshooting] whgarner:
Still trying to root

Thought I was close, but not close enough.

So far, removed hard drive from unit and was able to see and access files on drive via linux. I was able to install busybox and SU (x86 from Supersu zip, x64 was not a binary) into both bin and xbin, installed supersu into /system/app, fine so far. Upon reboot all works fine. Starting supersu says binaries need to be updated-fails, cannot update. In terminal attempted su command I get "permission denial broadcast asks to run as user" and about 10 other lines. Stuck now, tired of looking. Anybody with ideas are welcome.

ps was able to chmod 777 xbin and system on linux, but system reverted to 755 on reboot, locking me out, i suspect, from supersu updating binaries.

bill g.
[Android Q&A, Help & Troubleshooting] NTAB:
I don't have one of these but am seriously considering one. I hope you get this all figured out! :)
[Android Q&A, Help & Troubleshooting] whgarner:
willing to try almost anything

I'm going to try a few more times and things, but practically speaking I'm done. Love the unit though.

B.g.
[Android Q&A, Help & Troubleshooting] geminihc:
not sure if this is helpful, but there is another intel baytrail android device that someone seem to be able to install windows 8.1 on to successfully:

http://cngadget.info/2014/06/11/windows-8-1-firmware-for-teclast-x98-3g-instructions/

also, quite sure you did this already, but have you tried connecting a USB male to male from PC to the android ? what happens?
[Android Q&A, Help & Troubleshooting] whgarner:
usb connection

No response from usb pc to usb acer on any of three ports.

No usb debug option, only lan debug option.

b.g.
[Android Q&A, Help & Troubleshooting] laziod:
Off topic, have you been able to use this as a touchscreen while attached to a windows 8/1 machine?
[Android Q&A, Help & Troubleshooting] whgarner:
touchscreen

haven't tried
[Android Q&A, Help & Troubleshooting] ksimpsonel:
Has Acer sent out an upgrade for this device? It would Bebe nice to have 4.4.2 rooted...;)
[Android Q&A, Help & Troubleshooting] laziod:
I don't think Acer intends on supporting this device. It's a nice unit and would be much better if at least running 4.4. Hopefully someone figures out a root method.
[Android Q&A, Help & Troubleshooting] whgarner:
ROOTED aa3-600-ur10

Finally got around to working with the acer again and rooted it.

bootloader still locked as far as I know

no custom recovery, yet

I assume no responsibility if you screw it up.

How I did it

things needed:

linux machine, I'm running ubuntu 14.x

sata-usb drive interface

download "update-supersu-v2.46.zip" and extract

1. remove hard drive from acer, three screws on bottom of back and carefully pry back off.

2. drive is in a metal case in left side when looking from bottom of back, must remove two screws and slide case and drive to left. May need to remove drive from case to get sata connector to fit.

3 connect drive to linux machine, about 7-9 windows will open, you will need the window that is 2.1 gb in size that has app, bin and xbin folders.

4. you want to "cp" or copy the file "su" in the supersu folder "/UPDATE-SuperSU-v2.46/x86" into the bin and xbin folders of the 2.1 gb partition, i had to use sudo command

ex. sudo cp (source in my case /home/whgarner/Desktop/UPDATE-SuperSU-v2.46/x86/su no parenthesis) (destination /media/name of 2.1gb partition/bin/su no parenthesis) , repeat by placing a "su" copy in the xbin folder, one or other may not be necessary.

5 Place the "Superuser.apk" found in the "common" folder into the "app" folder using the above format.

6 sudo chmod 7655 the su in both the bin and xbin folders

7 sudo chmod 644 the Superuser.apk in the app folder

8 check to the permission in properties(right click the file) of each su and Superuser.apk to be sure owner and groups are "root", if not the use sudo chown root (filename) and sudo chgrp root (filename).

9 replace drive, boot, run superuser.apk, update binaries, reboot and I was rooted.

bill g.

good luck
[Android Q&A, Help & Troubleshooting] geminihc:
omg! that's so awesome! thakns for your hard works and testing. unfortunately i dont have a linux machine handy so i cant try it out for myself. now there is some hope for getting kitkat or even lollipop on this! and if bootloader unlocked, perhaps even windows.

i am reading that microsoft is actually going to make a flashable windows 10 ROM for some android devices that run x86 cpus like this one.
[Android Q&A, Help & Troubleshooting] stumms:
aa3

awesome news i love this tablet.. i feel like it could run windows i found this on another site but can't get pass the survey. http://newkitsroms.blogspot.com/2015/02/working-tutorial-how-to-updateupgrade_45.html
[Android Q&A, Help & Troubleshooting] stumms:
got into the boot mode anybody know what roms that might work?
[Android Q&A, Help & Troubleshooting] laziod:
Any update on rom development?
[Android Q&A, Help & Troubleshooting] rastographics:
[MENTION=2239034]whgarner[/MENTION] thanks for figuring out the root. is there a rom that you know of to use, at least version 4.4?
[Android Q&A, Help & Troubleshooting] whgarner:
roms

no rom development that i know of.

bg
[Android Q&A, Help & Troubleshooting] phishphish:
pulling this up from almost two years ago as i just grabbed this device and this is the only thread i could find on it, really here or anywhere else

user whgarner's method worked great. Mad props and thanks. Problem i am now having is when i adb into the bootloader via ethernet (only option) i lose my connection, fastboot finds no devices (previously connected through router), and i can't find a bootloader img anywhere on the system, not /dev/block/bootdevice not even just looking for an img file in general. Nothing.

Does anyone have any advice on how to proceed with unlocking the bootloader? Via retaining a connection through fastboot or really any other means?

Looks like the bootloader is droidboot 2.0 IFWI v00.36.R29 and recovery is Android System Recovery 3e if that helps anyone
[Android Q&A, Help & Troubleshooting] phishphish:
i found a pdf i cannot link to (too few posts) with some relevant adb/ethernet info, i'll copy paste the relevant task.

Seems relevant due to 1. the intel platform, 2. the required network settings are the same, and 3. droidboot. Looks like fastboot may not be an option? Or can only ping? I can ping the device using this process but cannot send any commands. I should also mention that the All in One bootloader is looking for the installer.cmd on the ext sd card according to the on screen prompt.

If anyone can provide any advice it would be appreciated
[Android Q&A, Help & Troubleshooting] whgarner:
Still have and use mine, but without being able to update android os, many updated apps don't work. I don't know enough about building updates to even try. Thanks for the interest.

whgarner
[Android Q&A, Help & Troubleshooting] sakhib:
i need your help.

i kill my acer aa6-600. no boot
[Android Q&A, Help & Troubleshooting] elisheva:
I have one of these, too. They're not bad for the price: nice big screen, quad-core 64-bit processor w/ virtualization, upgradable ram, sata drives, 1080p. I like. Great as an HTPC.

Unfortunately I think the only rom we're going to find with support for this architecture/hardware pair is the one that's on there, unless someone goes to work on intel's (abandoned?) opensource baytrail rom. For a more up-to-date OS, we'll have to look to Linux or Windows.

I think we have the same problem either way: UEFI. SecureBoot. I think it won't boot any OS without a bootloader signed by keys stored by UEFI, probably owned by Acer.

If you could get by that, you could install (flash) an OS to a hard drive, plug it in, and voila. Otherwise, you'll never boot anything but the factory-installed OS or one that Acer approves.

The solution then is to either disable SecureBoot or import a key into UEFI.

IIRC, these processors are subject to a vulnerability where on creates a UEFI race condition that allows the disabling of SecureBoot. This might be it: https://www.kb.cert.org/vuls/id/766164

If anyone is working on this, please contact me. I'll help if I can.
[Android Q&A, Help & Troubleshooting] bluegrassbandit:
Hello All,

I have downloaded a new ROM for my Acer AA3-600-UR10 because my hard drive failed.

What I am wondering is how do I put this ROM onto a new hard drive with the correct partitions/sizes.

Any help would be greatly appreciated!

Thanks,

bluegrassbandit
[Android Q&A, Help & Troubleshooting] abel408:
Hey elisheva,

Did you get any where with this. Currently have one of these and looking to tinker with it to get more out of it. I've upgraded the HD to a SSD. I also got it to boot with a 8gb ram stick, but android only recognizes 2gb for some reason. I've been looking into BlissOS, but I doubt that will work since that requires uefi. I know they made a Windows version of this same tablet. Wondering how we can unlock these android tablets so that we can boot into a bios or uefi similar to the Windows version.

Thanks
[Android Q&A, Help & Troubleshooting] elisheva:
I haven't worked on it, but I still have it and use it for Netflix and YouTube Music.

IIRC, the manufacturer stated it only supports 4GB. *my recollection was WRONG, *****!

It's exciting to hear that you got 8GB working(ish)! If any OS will fully utilize that, it really extends the utility of this computer.

I did the SSD upgrade, too. Huge improvement to boot time and app launch, eh?

First, the likely easiest fix: Take it to a computer repair shop and ask them to reflash the UEFI chip (disable SecureBoot). This is actually on my to-do list. You could do it yourself if you're a hardware guy or if you know somebody.

Remember that we're still at the speculation stage on why it won't boot another OS, but UEFI is VERY likely the cause. Working from that assumption, you should be able to install Bliss if it needs UEFI because the AA3 (probably) has it.

There is another problem, though. As far as I've been able to find, there is no way to access any boot options. Even after disabling SecureBoot, I don't know if there's going to be any straightforward way to select a boot device and enable installation of an OS from, say, a flash drive or SD card. We may be permanently stuck with imaging an OS directly onto a drive. That's not the end of the world, I just wanted to point that out.

I haven't worked on using the exploit because it's probably more economical to just have the chip re-flashed when you consider the time to develop, test, implement it (we also have to root the droid, which could be as easy as removing the drive and writing the binaries or as difficult as a privilege escalation exploit). I'm reasonably confident that just having a hardware guy re-flash the chip to disable SecureBoot will work and shouldn't be expensive. I'd offer him 20 bucks.

tl;dr:

Easiest fix is probably to take it to a repair shop and have them flash or replace the UEFI chip and eliminate the problem (disable SecureBoot). Including solder time, that's a 5-minute job.

Bliss should work if it supports the architecture and UEFI will still *exist*, but SecureBoot will be disabled.

*edit:

whgamer got it rooted:

https://xdaforums.com/showpost.php?p=60641474&postcount=26

Waitwhat?

Stumms, can you elaborate on this?

God damn, I talk too much.

Oh, and if anyone here thinks I'm talking out of my ass, corrections are welcome.

*edit:

........Has anyone tried contacting Acer?
[Android Q&A, Help & Troubleshooting] abel408:
This is great information! Thanks elisheva!

The bios chip is a winbound W25Q64FW which looks like it's flashable and common among windows tablets. Never flashed a bios chip before and wouldn't really now what I'm doing. I'll check some computer hardware stores around the area to see if anyone has the tools and experience.

I did not contact Acer, but that might be a good idea.

The SSD was a huge improvement. I'm trying to use this tablet as a display like the Lenovo Smart Display. Running Android 4.4 does not allow for Google Assistant though :/
[Android Q&A, Help & Troubleshooting] abel408:
So I'm about to give up but figured I would post about my experience to see if you have any ideas [MENTION=5704863]elisheva[/MENTION].

I purchased a ch341a flashing tool and downloaded the bios for the z3-600 from the Acer website. The bios file was a .CAP file so I needed to use uefitool to extract it and convert to a .BIN file. I then flashed the chips using that .BIN file. After flashing, the device does not boot up or display anything. I am able to reflash using the original bios file and boot into android again though.
[Android Q&A, Help & Troubleshooting] elisheva:
Wow, you're really going all out! Alright, let's see what we can do then.

Question for clarity:

After you flash the chip with the new bios from the Acer website, will it still boot the stock OS?

If the answer is no, then something is wrong with the downloaded file (corruption?) or (sorry) you're doing something wrong in your process.

If the answer is yes, then the download is fine, your process is fine, and Acer is providing you bad firmware. I just looked up the firmware. Read on.

We can do this! You have the tools. Now it's just a matter of troubleshooting/problem solving.

*edit: Why the az3-600? I must point out that Windows has also applied locked bootloaders to all-in-ones in the past, and it is possible that you may have created a new problem for yourself: trying to boot an android system on a system that will only boot an OS signed by Microsoft!

LOL same problem as trying to boot linux with the original uefi that would only boot an Acer-signed OS.

Here's what I can suggest for now:

If you can somehow get an EFI Windows 10 installation (that's what it's looking for) onto the hard drive for the tablet, do that. Try to boot the system using the new bios firmware that you flashed.

Ideally, you will then at least be able to press F2 or F10 or whatever and access the bios/uefi to disable secureboot! Though MS anti-piracy measures may stop you, it's worth a shot.

This may not work at all. So when you can, answer these questions for me:

With the new UEFI firmware, will the computer boot the original Android OS?

With the new UEFI firmware, will it boot an EFI Windows 10 installation?

We may have to hack the firmware file that you're flashing, and that would be an involved task but it's a much shorter road than root->exploit->overwrite-from-within. I'll help as much as I can, and that may be enough. Update me when you can. I admire you for taking the iniative on this!
[Android Q&A, Help & Troubleshooting] abel408:
Haha, at this point it's just a small project that has become a puzzle that I'd love to solve.

With the flashed chip, the device just displays a black screen. Does not boot up at all. I choose the z3-600 firmware because the it seems like the z3-600 and a3-600 are identical devices. Just one has android preinstalled and one has Windows. I'm interested in seeing if it would be possible to turn this a3-600 into a z3-600 and get Windows or BlissOS installed on it.

The device doesn't boot up with the android SSD or the Windows Installer media HD attached. Doesn't seem to even spin up the HD. I'm not exactly sure I have the correct firmware though. Like I said earlier, the z3-600 firmware is a CAP file. Online, I've read that the firmware image needs to be extracted from the CAP file using a tool like uefitool. Here is an example screenshot of an ASUS cap file in uefitool:

[IMG="Asus CAP File"]http://i.imgur.com/Q6jEs1C.jpg[/IMG]

Here is what the Acer z3-600 CAP file that I'm trying to use looks like:

[IMG="z3-600"]https://i.imgur.com/u6HFEv2.png[/IMG]

And here is what the original a3-600 firmware looks like:

[IMG="a3-600"]https://i.imgur.com/3N6h8OW.png[/IMG]