Hello everyone, today I tried to install bliss os and when the boot remains on the x86-64 writing: and I can not do anything.
And long ago I tried to install Android x86 and gave me the same problem some time ago.
How can I solve this problem?
A good start would be to move this questions to the official support thread found here https://forum.xda-developers.com/bliss-roms/bliss-roms-development/x86-bliss-x86-pc-s-t3534657
Second would be to provide relevant information about the device you are installing to. Device, make, model #, cpu chipset, your instalation method(there are several listen in the "install instructions" portion of the OP)
Right now you are simply stating "i tried this, it did not work, why not?"
Nobody can possibly assist you if you are not willing to provide useful information about your process. Also, please read through the above linked thread. there is much useful information already available for troubleshooting.
Related
I am very new to Android development. My need is to
1. Modify an Android service in the Android OS source code
2. Then to build the Android OS with that modification
3. Then install it on a device for example Google Nexus S
At this time I am just trying to build the Android OS as it is following the guidelines given on the page source[dot]android[dot]com[/]source[/]download[dot]html
I am using Ubuntu 64 bit and I have achieved all the rest of steps successfully but the last step that is make command is not working.
I would like to know if anyone has followed this guideline as it is and come up with success.
Otherwise I will like to know if anyone can tell me whether the instructions on this page are exclusively enough to build the Android OS source code. If yes then why I am getting errors.
Regards,
Asif
Can anyone reply to this message or even point to me where should I put this question to get any answer? Thanks.
what kind of answer are you expecting if you didn't even tell anything about the error message?
My advice: Make sure you're on Precise. Then POST THE BUILD LOG, SCREENSHOT, ERRORS, WHATEVER THE BUILD PROCESS IS TELLING YOU WHEN IT STOPS.
Otherwise, go google it and leave these good people alone.
Sorry for posting this in the general section, but I was told I can't post in the development section until I have 10 posts. I hope someone here can help me! I just finished downgrading my OS from the .29 build to .17 and everything went okay except for one big problem I am having. When I try to launch file manager I get "Unfortunately, File Manager has stopped". Everything else on my device works. Has anyone had any experience with this?
usually that occurs when you didn't clear cache etc...
For future reference, this type of thread shouldn't be posted in the development section anyway. Development is for people releasing ROMs, recoveries, kernels, and other related items for download.
Hello all,
Updating android-x86 variant could be accomplished via OTA updates, and/or
another bootable installer, however wouldn't having the ability to 'flash'
customizations via a GRUB like interface be beneficial as well?
I feel for testing purposes that this could be beneficial. Having the
ability to rework the source without having to do a clean install every
time could provide a more accurate method for testing. This would also be
good for devs, who want to modify their actual system rather than a virtual
one.
I have little knowledge of android building, however I am vaguely familiar
with C and java. I have the source downloaded and I am reviewing it, in the
case that people will find this worthwhile, I will (hopefully) be able to
contribute to the cause.
Again, if I am completely off base here, please inform me. I am just trying
to help the cause!
Thanks all for future inputs. :good:
korg bootable recovery ( may be useful) : http://sourceforge.net/p/android-x86/korg_bootable_recovery/ci/master/tree/
Source thread : http://grokbase.com/t/gg/android-x86/143w3yx749/grub-based-recovery-similar-to-cwm
bump
no idea?
Hi so i am new in the Android world i just recently obtained a new Asus Memo Pad 10 (ME103K) and i would like to root it to use some functions a friend showed on their Android device, but i sadly got scared that i might brick my device if i do not root correctly, so i searched up my device but i couldn't find anything that looked like a guide for this particular one ( i even read in a forum that it supposedly doesn't have a root yet because its new ) , so my question is : Is there any way to root this device yet? and if yes, can i ask for a guide or a link that has the guide? Thanks in advance .
*Bump*
I haven't been able to find a root working for Asus MemoPad 10 (ME103K) Could anyone provide any information if there is a root available? (I saw many fake sites and some claiming to work but didn't)
Thank you in advance
Framaroot?
Yoohei said:
Hi so i am new in the Android world i just recently obtained a new Asus Memo Pad 10 (ME103K) and i would like to root it to use some functions a friend showed on their Android device, but i sadly got scared that i might brick my device if i do not root correctly, so i searched up my device but i couldn't find anything that looked like a guide for this particular one ( i even read in a forum that it supposedly doesn't have a root yet because its new ) , so my question is : Is there any way to root this device yet? and if yes, can i ask for a guide or a link that has the guide? Thanks in advance .
Click to expand...
Click to collapse
have you tried framaroot?
http://forum.xda-developers.com/apps/framaroot/root-framaroot-one-click-apk-to-root-t2130276
Downlaod version 1.9.3
I rooted ME103K on my own, compiling a custom kernel
Executive summary: Go to youtube and watch video with ID "gqubgQjqfHw" (I can't post links yet, sorry! ) - or search Youtube for "Rooting MemoPAD10 (ME103K) with my custom compiled kernel"
Analysis:
I hated the fact that my recently purchased MemoPAD10 (ME103K) tablet had no open process to allow me to become root. I don't trust the closed-source one-click root apps that use various exploits, and require communicating with servers in.... China. Why would they need to do that? I wonder...
I therefore decided this was a good opportunity for me to study the relevant documentation and follow the steps necessary to build an Android kernel for my tablet. I then packaged my custom-compiled kernel into my custom boot image, and the video shows how I boot from it and become root in the process.
Note that I didn't burn anything in my tablet - it's a 'tethered' root, it has no side-effects.
If you are a developer, you can read in detail about the steps I had to take to modify the kernel (and su.c) and become root - by reading the questions (and answers!) that I posted in the Android StackExchange forum ( can't post links yet, see the video description in Youtube ).
If you are not a developer, you can download my custom boot image from the link below - but note that this means you are trusting me to not do evil things to your tablet as my kernel boots and my /sbin/su is run
Honestly, I haven't done anything - I just wanted to run a deboot-strapped Debian in my tablet. But I am also worried about the cavalier attitude I see on the web about rooting your devices - if you want to be truly safe, you must either do what I did (and recompile the kernel yourself) or absolutely trust the person that gives it to you. I do wish Google had forced a UI-accessible "become root" option in Android, just as Cyanogen does (sigh).
The image I created and used in the video to boot in rooted mode, is available from the link show in the Youtube video details.
Enjoy!
Aloha,
I tried following the following guide but a good number of the links are broken, and mostly for windows users when trying to update their Linux based phone. The Irony.
http://forum.xda-developers.com/showpost.php?p=16211361&postcount=117
I did find a useful guide for following the first step for most universal rotting phones: install adb drivers for ... Ubuntu easily translated to my working system, Fedora.
http://esausilva.com/2010/05/13/setting-up-adbusb-drivers-for-android-devices-in-linux-ubuntu/
The lexikon image which is the basis is of the pushed system image is missing or no longer available, five years old, from shipped-roms and the gold card method, a UK website, for my non Verizon version not to surprising also no longer working either, only 4 years old. So I guess if I can find the images needed, I didn't try all the links after the first three were found to be broken, especially since they don't seem to apply to my non verizon phone.
XDA Visitor said:
Aloha,
I tried following the following guide but a good number of the links are broken, and mostly for windows users when trying to update their Linux based phone. The Irony.
http://forum.xda-developers.com/showpost.php?p=16211361&postcount=117
I did find a useful guide for following the first step for most universal rotting phones: install adb drivers for ... Ubuntu easily translated to my working system, Fedora.
http://esausilva.com/2010/05/13/setting-up-adbusb-drivers-for-android-devices-in-linux-ubuntu/
The lexikon image which is the basis is of the pushed system image is missing or no longer available, five years old, from shipped-roms and the gold card method, a UK website, for my non Verizon version not to surprising also no longer working either, only 4 years old. So I guess if I can find the images needed, I didn't try all the links after the first three were found to be broken, especially since they don't seem to apply to my non verizon phone.
Click to expand...
Click to collapse
Welcome to XDA Developers.
First, please register as a user, here > http://forum.xda-developers.com/register.php
I'm sorry, but there is not a specific forum for your device yet.
After you have registered, If you go to the following forum and post your request for the lexicon image, hopefully one of our experts can help you > http://forum.xda-developers.com/showthread.php?t=2259645
Good luck.