Linux - MobileThis forum is for the discussion of all topics relating to Mobile Linux. This includes Android, Tizen, Sailfish OS, Replicant, Ubuntu Touch, webOS, and other similar projects and products.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
@tailinlinux: Thanks for the links. I am trying the first method.
Quote:
Originally Posted by anoce132
Hello everyone i need your help i want to boot ubundu on my sony ericcson xperia neo v but it always says error 20 or 44 the same is hapenning with backtrack. Does anyone knows how to help me? ( 2.3.4 , kernel 2.6.32.9-perfSEMCUser@SEMCHost#1)
Why don't you mention the exact steps you have taken more clearly.
A device is only an 'Android Device' because it runs the Android OS. Beyond that, it is simply a device. The method of loading and booting to any other OS depends entirely on the device itself. This is exactly the same state of affairs that existed with microcomputers before IBM came along and started building PCs, which quickly became an industry standard architecture. I'm not really a tablet geek, but I doubt very much whether there is any kind of standardization in tablet/handheld/mobile devices that allows you to install anything new by following generic instructions. About the only thing that seems to be a common convention is that mobile devices tend to use some form of ARM architecture. Unfortunately, even that describes a very broad spectrum of CPUs and other architecture. Most ARM based devices use some form of on-chip flash memory from which to boot. Modifying that memory may be anywhere from impossible to merely difficult. It is very much a possibility that getting the modification wrong will brick the device. There are probably a host of components that have custom drivers or require special configuration. Heck, even getting Linux to run on something pretty standard like a laptop can be difficult.
Hello everyone i need your help i want to boot ubundu on my sony ericcson xperia neo v but it always says error 20 or 44 the same is hapenning with backtrack. Does anyone knows how to help me? ( 2.3.4 , kernel 2.6.32.9-perfSEMCUser@SEMCHost#1)
Hi, please do not hijack other people thread, it would be better and to get the proper attention if you start a thread for your specific problem.
Did you check your device if having root permission. Try to download root checker on google play and check if you have permission as root.
Now when I run z4root, it informs me that the device is already rooted and gives me options to unroot or re-root. Also on some occassions, there was a message box asking me whether to permit some program asking for superuser priviledges. The tablet appears to be rooted.
Now when I run z4root, it informs me that the device is already rooted and gives me options to unroot or re-root. Also on some occassions, there was a message box asking me whether to permit some program asking for superuser priviledges. The tablet appears to be rooted.
Did you try to check it using root checker?
If root checker tells you have root permission you can go on the next step.
A device is only an 'Android Device' because it runs the Android OS. Beyond that, it is simply a device. The method of loading and booting to any other OS depends entirely on the device itself. This is exactly the same state of affairs that existed with microcomputers before IBM came along and started building PCs, which quickly became an industry standard architecture. I'm not really a tablet pc geek, but I doubt very much whether there is any kind of standardization in tablet/handheld/mobile devices that allows you to install anything new by following generic instructions. About the only thing that seems to be a common convention is that mobile devices tend to use some form of ARM architecture. Unfortunately, even that describes a very broad spectrum of CPUs and other architecture. Most ARM based devices use some form of on-chip flash memory from which to boot. Modifying that memory may be anywhere from impossible to merely difficult. It is very much a possibility that getting the modification wrong will brick the device. There are probably a host of components that have custom drivers or require special configuration. Heck, even getting Linux to run on something pretty standard like a laptop can be difficult.
--- rod.
Hello theNbomr thanks for sharing your views. I completely agree with you. Before making any modification we need to check compatibility of device
Last edited by SheldonWatkins; 04-11-2013 at 11:11 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.