Greetings,
I've read something about Android 4.0.3 on x86 based computers and saw, that it would be running on EeePCs.
So I decided to install it on my EeePC and I like it. But that's the bright side of the story.
Here comes the problem. It's rooted of course and superuser is installed.
Worked very well at the beginning (though that was without having it installed but just running it via CD)
Now it's not working, superuser is, but obviously I don't have root...
I tried several things
1. Cleared data of superuser
2. Set superuser to always allow requests
3. took superuser.apk out of some old android revolution hd to install it over the existing superuser (what of course didn't work)
Now I'm out of ideas. And still without success...
I'm not really sure if root has ever worked since installing it, but while running it via cd it worked like a charme.
Maybe some of you decided to check on Android for x86-based computers and experienced the same.
Furthermore I hope that this one might have found a solution to this.
Thanks in advance, hopefully there's a solution without having to reinstall it
(If it's important or needed - Windows 7 Starter is installed as well)
Gesendet von meinem eeepc mit Tapatalk
Check the superuser binary inside the superuser app.
nejc121 said:
Check the superuser binary inside the superuser app.
Click to expand...
Click to collapse
I did and it tells me that I need root to install it :-/
at least it fails at the point where it wants root to continue
Not the best photo but I think it's readable enough to see, that updating the binary fails :-/
{
"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"
}
nuovo
New D & H PAGINA CON LINK A WIKI Promemoria (LEGGERE PRIMA DI DISTACCO)
rama197525 said:
New D & H PAGINA CON LINK A WIKI Promemoria (LEGGERE PRIMA DI DISTACCO)
Click to expand...
Click to collapse
Pardon me?
did you choose a write-only system folder on install?
that could restrict some su stuff
cougarten said:
did you choose a write-only system folder on install?
that could restrict some su stuff
Click to expand...
Click to collapse
I'm not quite sure about it, but that could be.
However. What if I decide to reinstall it? Could I save some files and restore them afterwards?
There are some .img files that I can save with Windows. But I guess all apps and data will be removed.
thanks for the hint, I'll try that this afternoon
Gesendet von meinem eeepc mit Tapatalk
I have removed the Android I had on my eeepc and installed it.
Looked out for the prompt if write-only system, chose write-read - no root.
Before doing that I just booted Android via CD and had root access. Weird - guess I have to ask the developers of Android x86
Just got an idea.
I've read that root wouldn't work if the partition was fat32 - my chosen partition wasn't fat32 but ntfs. So I created a partition which I then formatted to ext3. Let's see if it works now
Perfect. It works
So for everybody that's interested:
you need to make a partition and format it while installing Androidx86 to ext3 or others, at least NOT fat32 - and it'll work
There's another thing I can't achieve myself.
I wanted to configure the battery so it shows my actual battery.
There's a guide to it ( http://www.android-x86.org/documents/howtoconfigurebatteryservice) -
the problem is in this
" In Linux, applications collect the battery status through sysfs, where the battery status is located in /sys/class/power_supply/. Different platforms, however, may give you a different directory layout under /sys/class/power_supply/, but Android hardcodes the directory layout to /sys/class/power_supply/. To resolve this issue, I have added new entries in vendor/asus/eeepc/system.prop, where the user can change the value of these entries to correctly configure the sysfs directory layout for different platforms. These entries are:"
I can't find such directory as vendor/asus/eeepc/system.prop - there is no system.prop on my device, I've searched for it
Mainly I don't know, where to put all these values written in the how-to
Gesendet von meinem eeepc mit Tapatalk
Not only FAT32 has those issues. NTFS too... Eee PC 1008HA
Crimento said:
Not only FAT32 has those issues. NTFS too... Eee PC 1008HA
Click to expand...
Click to collapse
You have to create a ext3 partition and then install Android x86 on it - will work perfectly
Related
Hey xda,
I have found a very cool application for windows users: Android Commander.
Its a File Manager for Windows that lets you browse the root directories of your phone within a nice gui. No more typing lines of adb shell commands!
Download: Visit Website http://androidcommander.com/
Functions:
File Actions
Copy Files
Delete Files
Push Files from PC
Pull Files to PC
Create Directories
Edit File Properties (Permissions, etc)
Select Multiple Files
Sign Files
Read Device Info
Open a ADB Shell console
Read logcat
Virtual Input (havent tried it)
Screenshots (Tested and found buggy on CM9)
Screenshots from the Website:
{
"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 been around for quite a while. Very useful.
Ah, ok. I didn't kne it and found it useful to have it written down somewhere.
Sent from my GT-I9003 using XDA
I do know Why its always keeps on loading
NO Root Acces
Does anyone can help me, I have no root access over my phone?
When I run Android Commander, the bottom status bar says "Root Access : NO"
I don't understand what went wrong.
I tried to click the status bar, it just keep on loading.
Doesn't even find my HTC Sensation (adb drivers installed+rooted), while both QTADB and Droid Manager are able to access the phone.
So it's a no go for me, too bad, looks promising.
Thank you
@Taraen;
br im a new bie can you send some tutorials on how to use this?
thanks bro, this is realy good app. :highfive: i searched for app like this very long time :good:
link broken? giving up..
downloaded doesent seem to work for me or find my device.
does not show my phone as root ?
viditshah36 said:
does not show my phone as root ?
Click to expand...
Click to collapse
Maybe because you are runing jb mr1 4.2.2
For all those that get "Root Access : NO" on rooted phone, it's because adbd is running in "secure" mode.
Try adbd Insecure v1.30. It worked for me:
http://forum.xda-developers.com/showthread.php?t=1687590
It won't show my device
it says my Galaxy nexus(4.3 +rooted) is offline and that I should reboot it.
done the reboot, nothing changed, tried insecure adb, the same message.
can someone help me.
I need to to modify swap file as im using androidcommander with rooted note 2 4.3
thank u people
works just fine with Chainfires Insecure Mode app and KitKat on my Nexus 5.
You need to overwrite the files that are in $ROOT/Android Commander DIR/bin/ with the ones that are from an up-to-date sdk.
There are 4 files.
Here; I'll make it easier for you all.
Android Commander Update Files for 4.3+ Support
doesn't work with my gt p3110 with 4.2.2 works fine with droid 4.1 and below
Awesome
krylon360 said:
works just fine with Chainfires Insecure Mode app and KitKat on my Nexus 5.
You need to overwrite the files that are in $ROOT/Android Commander DIR/bin/ with the ones that are from an up-to-date sdk.
There are 4 files.
Here; I'll make it easier for you all.
Android Commander Update Files for 4.3+ Support
Click to expand...
Click to collapse
Brother. Yes it does the magic. Its working when the files are replaced by the fresh files.:good::fingers-crossed:
---------- Post added at 10:47 AM ---------- Previous post was at 10:42 AM ----------
lohtse said:
doesn't work with my gt p3110 with 4.2.2 works fine with droid 4.1 and below
Click to expand...
Click to collapse
Above files as mentioned are for 4.3+ but you are on 4.2.2.
First search, first result..just what I needed when I needed it..worked perfectly for me! Big Thanks. :good:
Cannot access data/data
imakulate said:
First search, first result..just what I needed when I needed it..worked perfectly for me! Big Thanks. :good:
Click to expand...
Click to collapse
I am successful in connecting the device , but I can't access the path data/data . When I click on data/ it doesn't displays anything.I require it for development purpose, so has to access the database file of the apps
And one more, can I backup apps along with data like Titanium backup
Please help... I have flashed this: http://forum.xda-developers.com/goog...eview-t2796003 with the recovery method and now I can´t see my files because the mobile sais that I don´t have SD Card. I tried this to solve it using this:
Got "No SDCard" error?
This is because 4.4.x seems to point to: storage/emulated/0 & L points to: data/media/0
Solution:
- Mount system in TWRP/CWM
- Wipe system, dalvik, data, cache
- Unmount system
- Install ROM
- Factory reset
- Reboot
- Go back to recovery & flash SuperSU (link above).
- Reboot
But doing that I only can see the folders, but when I enter in them it doesnt show any file
When I try to restore the nandroid backup that i make before install Android L I cant see the file on TWRP so I can´t restore it... How can I come back to KitKat?
It was mentioned on another thread but I don't remember by whom so can't give proper credit but from a terminal emulator on your phone run
su
storecon -r /data/media/0/*
See if that works
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
It was mentioned on another thread but I don't remember by whom so can't give proper credit but from a terminal emulator on your phone run
su
storecon -r /data/media/0/*
See if that works
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I tried that too, but its doesnt work... :S
kapucho19 said:
I tried that too, but its doesnt work... :S
Click to expand...
Click to collapse
The first time I flashed L I had the same problem. Are you trying to get back to 4.4.4? You're going to lose all data on your device flashing back
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
The first time I flashed L I had the same problem. Are you trying to get back to 4.4.4? You're going to lose all data on your device flashing back
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Ok, I get back to 4.4.4 by flashing again my ROM and once I did that, I could be able to see files on the KitKat storage, I moved the nandroid to the L storage and I restored it. But now I have the problem that now I have two different storages (The L´s one it´s the preset) How could I change the storage now? restorecon -r... What else?
kapucho19 said:
Ok, I get back to 4.4.4 by flashing again my ROM and once I did that, I could be able to see files on the KitKat storage, I moved the nandroid to the L storage and I restored it. But now I have the problem that now I have two different storages (The L´s one it´s the preset) How could I change the storage now? restorecon -r... What else?
Click to expand...
Click to collapse
{
"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"
}
(0 it's the one of KitKat)
Nexus 5 || Android 4.4.4 || Paranoid Android
Guys, as already mentioned a couple of times, please keep all Android L related discussions inside the according Android L Q&A thread
---> Thread closed
{
"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"
}
Description
GlassROM Young N is a ROM (the first one, if I am not in error) for the Samsung Galaxy Young GT-S6310N (not S6310!, but the N variant). I was horrified by this low-end device, because there were no custom ROMs for it, and S6310 ROMs didn't work, I just ended up re-flashing the original firmware after a boot loop. So, here it is, the first ROM for this device, based on the Samsung 4.1.2 official AMJ1 firmware. It is de-bloated (which means no software besides what you want), has Trebuchet Launcher instead of TouchWiz Home, and I also remved most Google Apps (except for Play Store), because you can install them if you want, from Google Play.
This new thread for GlassROM Young N was made as a pre-release. The files here released, are an installer of the ROM Patch. This means you need to flash the stock ROM (4.1.2 AMJ1) via ODIN or Heimdall. Also, you must flash CWM (get it here: https://www.mediafire.com/?nwcnwu1yu92ym9w) via ODIN/Heimdall too. Then, you must boot up the stock firmware and enable USB Debugging. FInally, reboot to recovery, go to Mounts and Mount /system . Finally, connect the phone to the computer and run the script.
The original script was made for Unix-like OSes which use Bash Shell (like Linux and Mac). But I have made a Windows version too, available on the project page.
Screenshot
Download
Version 0.1.1 [Notes - some people report problems with the Windows installer]
[MIRROR]Try this link if our website is down!
Download v0.1 for GT-S6310N
If you like my work here on XDA, please consider donating!
Added files to our project page!
http://glassrom.5gbfree.com/young/n/gt-s6310n/stable/
I am developing an OTA Installer and OTA Updater for this ROM!
Stay tuned!
OTA Updater going to tests!
I've done everything, recovery, clean install, usb debugging enable, I get a usb device not install in device manager for SAMSUNG_android when a get in recovery and put usb in phone. The solution?
I tried on all sorts samsung drivers, and even KIES and nothing.
Thanks in advance.
Windows script is useless, several errors, bricked the phone. Needed to flash again. Do not upload until you test it.
Could you provide a screenshot of the error? Does ADB say anything?At the moment, I can only test the Linux/Mac OS/*nix version. You could try using it btw.
Sent from my GT-I9100 using XDA Free mobile app
gunar74 said:
Windows script is useless, several errors, bricked the phone. Needed to flash again. Do not upload until you test it.
Click to expand...
Click to collapse
I see. Look, this isn't a Google Play app review. This is a development thread. You seem like you don't understand it, but doing this takes time. Here, useful feedback is the only one I would like to receive. Useless feedback like yours wont help development at all.
Sent from my GT-I9100 using XDA Free mobile app
Since I do not know linux, I can not use it. I have tried Ubuntu live dvd, but it does not run the script without adb.
gunar74 said:
Since I do not know linux, I can not use it. I have tried Ubuntu live dvd, but it does not run the script without adb.
Click to expand...
Click to collapse
Use the live dvd or usb, then install adb from the terminal (write adb, it should tell you what to do to install it), and use the installer. Note th\g yoj must be on recovery when running the script.
Update: 0.1.1 bugfixing update was released. 0.2 is expected to use OTA updating via our app.
Working on the OTA Updater
As you can see in the screenshot, the OTA Updater app will be available in the next updater. It is almost finished, now I have to start working on actual flashable updates.
gnmmarechal said:
Use the live dvd or usb, then install adb from the terminal (write adb, it should tell you what to do to install it), and use the installer. Note th\g yoj must be on recovery when running the script.
Click to expand...
Click to collapse
What to do next, after adb is installed?
Dokotrs said:
What to do next, after adb is installed?
Click to expand...
Click to collapse
You just run the installer.
gnmmarechal said:
You just run the installer.
Click to expand...
Click to collapse
install.sh opens in text editor.
You have to change it's permissions to executable.
Open the Terminal, and do:
chmod u=rwx install.sh
Then type
./install.sh
And that's it.
error
Link to get instruction for GlassROM Young N dos not working
Hello.Thank you for your job,but i can not to try GlassROM Young N - link to get instruction for install from Windows not working,also not working link for install from SD.How i can get that?Thank
Just got my Sony Xperia Z3. Still messing around to get a feel of the UI.
Was not able to uninstall File Commander as I find the UI badly design. So installed ASTRO File Manager, tried deleting a file from ext SD card. pops up a notice saying that due to KitKat design, 'write' to ext SD card is prohibited.
I uninstalled ASTRO File Manager and installed SOLID Explorer, deletion from ext SD card was not allowed as well.
Tried deleting same file using File Commander and it worked
{
"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"
}
!
Probably will try File Expert but expecting the same rejection.
It is a well known issue with KitKat and is brought in on purpose by google.
Basically in an effort to increase security protection to the user only system apps can write to the SDcard. There is a way around it but you need root. Just google "Write to SD card KitKat" for further information and how to revert it.
gregbradley said:
It is a well known issue with KitKat and is brought in on purpose by google. Basically in an effort to increase security protection to the user only system apps can write to the SDcard.
Click to expand...
Click to collapse
You believe in Santa Claus, too ?
Google tries to force you into using their cloud services, that's all magic.
But it's correct: You need root to edit the file platform.xml. After doing that, everything is ok again.
But DO NOT ROOT, yet ! You'll lose all DRM keys (making the horribly bad Z3 camera even worse) and X-Reality. And believe me: You really do not want to lose that.
Chefproll said:
You believe in Santa Claus, too ?
Click to expand...
Click to collapse
What does this mean?
Google tries to force you into using their cloud services, that's all magic.
Click to expand...
Click to collapse
If you say so
But it's correct: You need root to edit the file platform.xml. After doing that, everything is ok again.
But DO NOT ROOT, yet ! You'll lose all DRM keys (making the horribly bad Z3 camera even worse) and X-Reality. And believe me: You really do not want to lose that.
Click to expand...
Click to collapse
Yes I know, its an old issue and well known how to get around it. And trust me, if I want to unlock my bootloader I will.
The only way around it is to save files in your File Explorer's App folder. With FX Explorer, for example, save your files into Android/data/nextapp.fx/files/
You'll be able to write and delete all you want.
File Commander works across all folders because it's a system apk.
Presumably with root you could just convert your file manager app of choice to a system app with the likes of Titanium and it would then work ok? Or just use one that uses root anyway (like Root Explorer).
Work root you just add one line to platform.xml and then it works just like it did before
Sent from my D6603 using XDA Free mobile app
3Shirts said:
Presumably with root you could just convert your file manager app of choice to a system app with the likes of Titanium and it would then work ok? Or just use one that uses root anyway (like Root Explorer).
Click to expand...
Click to collapse
Of course, with root you can get around any software restriction. However, in 2 - 3 years it'll be moot (hopefully sooner). It's like when Android dropped the menu key and everyone was pissed. After 2 years no one cares about the lack of a menu key anymore.
I had the problem, I couldn't root my phone after the update from B521 to the latest B820 version.
I tried out SuperSu versions 2.65 till 2.74.
After rooting through TWRP, I always got bootloops and after unrooting the system starts normally.
As a last try, I looked into the install script and set the "SYSTEMLESS" var to "true".
Now I've got a rooted and starting phone.
So I think there must be a problem, at least for me, with automatically detecting a systemless installable Android version in SuperSu from chainfire at Honor 6, as I understand.
Did anyone else have that problem?
I added SYSTEMLESS=true in /META-INF/com/google/android/update-binary within SuperSu-v2.65.zip, just as described there, but it should defaults to true after proper detecting without this.
At my B521 system, I used SuperSu version 2.52, which worked there and wasn't booting at Marshmallow, too.
Install 2.62
{
"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"
}
Sent from my H60-L04 using Tapatalk
What Tools did you use? The multi tool doesn't have emui 4 on L04 yet
gammaanimal said:
What Tools did you use? The multi tool doesn't have emui 4 on L04 yet
Click to expand...
Click to collapse
Flash it using TWRP recovery...
Sent from my H60-L04 using Tapatalk
The Multi Tool says for TWRP L02 and L12, can I also install it on L04?
I've installed SuperSu 2.74 via fastboot/TWRP, but as I wrote, only with an modified updater-script, the system boots up. (for me, not sure why and maybe this can help others)
Machredsch said:
I've installed SuperSu 2.74 via fastboot/TWRP, but as I wrote, only with an modified updater-script, the system boots up. (for me, not sure why and maybe this can help others)
Click to expand...
Click to collapse
I think I have exactly the same issue, could you upload your modified supersu.zip for me or walk me through the modifications?
That'd be swell.
hagehagen said:
I think I have exactly the same issue, could you upload your modified supersu.zip for me or walk me through the modifications?
That'd be swell.
Click to expand...
Click to collapse
Have tested it today with latest stable SuperSu, which is v2.76-20160630161323.
-> open the archive with an archive-manager
-> go to /META-INF/com/google/android/ directory
-> edit update-binary with a text editor (your text editor should respect linux line breaks (LF), so if you're on windows, you have to make sure this, I think)
-> after the commented section(all lines with a # beginning), where you can read about possible system vars and beyond,
you have to set the SYSTEMLESS variable to true like in the following example of code:
Code:
...
# if needed. It must replace the input file and return a 0 exit code.
[COLOR="Red"]SYSTEMLESS=true[/COLOR]
OUTFD=$2
...
Line 2, you have to insert to achieve an systemless installation, which seems to be the only way for you and me to make it work.
Please make sure to pay attention to upper/lower case, because otherwise it will fail.
-> save the updated zip and install it via TWRP, e.g. via sideload
Hope, this was usefully.
Note: This is only usefull for Marshmallow as described in the file, because it will not work below.
If you leave TWRP afterwards, e.g. for reboot and it asks you for installing root, click on "Do not install".