Can't get Root access on W500 with Brazos 4 0101 build

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install Brazos 4 0101 build on a W500
2. Specified "Allow System R/W Access" during the initial install. 
3. Market apps indicate that they don't have root access.  

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?

Please provide any additional information below.

I've installed superuser and a couple different busybox apps.  Titanium  backup 
still reports no root access, even when I check the box to "use system 
busybox".  

I'm dual booting with Windows, so I intially installed android to a Fat32 SD 
card, but have also copied the android folder to the NTFS Formatted SSD drive 
and created a Windows Bootloader entry for Android.   It works great, but I 
can't get root access.   

Is there a way to run rooted market apps in this build?           

Original issue reported on code.google.com by rsha...@gmail.com on 24 Jan 2012 at 9:37

[GoogleCodeExporter]

Hi there,

I think this isn't really an issue, cause the documentation stated, that you 
can't have the android system as r/w installed on fat32  partition.

See here : http://code.google.com/p/android-x86/wiki/InstallHowTo

Original comment by TKlightf...@googlemail.com on 25 Jan 2012 at 11:45

[GoogleCodeExporter]

I have Android ICS RC1 installed on my eeePC and superuser came pre-installed.  
But every app i've tried to run that requests root access is being denied.  I 
don't know what would be going wrong.  I know I selected a r/w system during 
the install.  Any suggestions would be appreciated.

Original comment by motronma...@gmail.com on 8 Mar 2012 at 4:32

[GoogleCodeExporter]

I also still have the same problem on my W500, even after a complete refresh to 
RC1 WITHOUT using FAT32.    Still no root access being reported by apps that 
require root.   

Original comment by rsha...@gmail.com on 8 Mar 2012 at 2:38

[GoogleCodeExporter]

I also have the problem: 

I installed  Android x86 4 RC 1 with read only: I have root access.
If I install Android x86 4 RC 1 read/write : I don't have root access. 

Both times installed using NTFS. Any idea? "Superuser" always denies su access, 
no matter if I use Terminal Emulation / su or an app that requires root 
priviledges.

Original comment by marcel.u...@gmail.com on 19 Mar 2012 at 7:51

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I can confirm this issue on my lenovo s10-3t.

Superuser does not work.

Setup: Read and write. NTFS. 4.0RC2.

Funny story: Go to superuser. Click on the "i" sign on the top. Click on top to 
update. It will request permission. Give it permission. Yet it will be denied 
and fail. xD

Original comment by sn...@darkbattlers.com on 28 Jul 2012 at 9:06

[GoogleCodeExporter]

i got same problem

installed rc2 
superuser denies root access for all apps without prompt
installed marek vasut's release
superuser denies root access for all apps without prompt

anybody figured out why it was happening?

Original comment by yildirim...@gmail.com on 29 Jul 2012 at 6:29

[GoogleCodeExporter]

Yes, it seems like a fix to a lot of problems is using ext3 file system.
It fixed this and the sdcard and numerous other bugs for me. With arm libs 
installed, it is just so awesome.

Original comment by sn...@darkbattlers.com on 29 Jul 2012 at 6:33

[GoogleCodeExporter]

If i were to install on ext3, will i be able to dualboot with my windows? I 
tried to dualboot android on ext3. During bootup, bios just bootup into windows.

Original comment by mohd.han...@gmail.com on 29 Aug 2012 at 8:46

[GoogleCodeExporter]

Check out this link for dual boot with ext3

http://code.google.com/p/android-x86/issues/detail?id=993&q=w500

Original comment by rsha...@gmail.com on 6 Oct 2012 at 8:41

[GoogleCodeExporter]

I am new to this...
got the Iconia W500 (AMD Brazos)
used RC2 marek vasut's release on ext3 sdcard (with r/w system at install time)
superuser comes pre-installed
works well everywhere
*but*
stops working if I allow superuser to update/upgrade itself
after that impossible to get root access without doing a full re-installation 
of RC2...

now I remember this happening on a 'normal' Android device (Toshiba Thrive) 
where solving it required flashing a zip file from the superuser dev that 
contained the signed su (for x86 the file is Superuser-3.1.3-x86-signed.zip)...

I would like to try that on the x86, but it does not have CWM (Clockworkmod) as 
boot menu, so is there another way to flash Superuser-3.1.3-x86-signed.zip?

or am I stuck with having to prevent superuser from upgrading itself...

otherwise, if I reformat and re-install again, how can I uninstall superuser 
and install Chainfire's Supersu  - I read it was better behaved, but when I try 
to install it on top of superuser - which I guess is not advisable, it 
complains it cannot find su as a problem, but su is in /system/xbin in this 
case...

any advice greatly appreciated...

for now I will yet again re-install the whole lot, and will not touch supersu 
or allow it to upgrade (which forces me to not enable auto-update, and do all 
updates manually instead)...

Original comment by nabilh2...@gmail.com on 20 Mar 2013 at 2:02

[GoogleCodeExporter]

Replying to myself of #11
Maybe I solved it...

this is what I did:

re-install everything as before
installed root explorer which I own
allow r/w on file system
copy /system/xbin/su to /system/bin/

install Chainfire's superSU pro which I own
and now superuser has been taken over by superSU

I checked in /system/app and superuser.apk has gone, so superSU removes it...
but I needed superuser to allow root permission to superSU so a new su for 
superSU 
gets downloaded and copied...

well so far it works...
but fiddly

the problem with the superuser dev is that he has not upgraded his app for a 
very long time... and I want this to work now...

another thing... I still have not figured out how to use adb from windows for 
the acer w500... I guess it is not possible as with a usb A to A lead windows 
does not recognise the tablet...

Original comment by nabilh2...@gmail.com on 20 Mar 2013 at 5:30

[GoogleCodeExporter]

Iput no r/w acess and had full root acess......I put rewrite no root acess, 
NTFS file system as well.

Original comment by DonHyp...@gmail.com on 19 Nov 2013 at 5:56