I'm having issues with the ROM I've been cooking and can use some help / advice. I've been working on a ROM based on jeepers007 Evervolv JellyBean effort. I've done the testing and modding on my device, and it seems to work well. However something is happening from when it leaves my handset as a backup and the finished result from the kitchen that introduces tremendous instability that I can't seem to overcome. Every attempt I've made experiences random crashes, lockups, and reboots that are nonexistent with the original configuration on my handset. I can't for the life of me figure out what I'm doing wrong. It's really getting frustrating and I'm almost ready to throw in the towel. Any ideas suggestions would be greatly appreciated.
Edit: Let me elaborate further. I can wipe clean all of my partitions, do a custom restore of just my /system partition, and my base system will recreate itself with no issues. From that point I can completely restore with Titanium, no crashes, no lockups, and no reboots. Every attempt I've made at cooking my backup into a working installable ROM in the kitchen results in crashes and reboots before it ever gets to the initial login and setup screen. It gets worse from there. I get a mysterious cascade of toasts announcing various processes crashing, before it reboots back to the sign-in screen. When I finally am able to login and begin using it I get sporadic crashes from out of nowhere.
I've experimented with the kitchen before, using it to add or remove features or mods to ROMs I was using or wanted to use, but never had these kinds of problems before. This is getting frustrating.
When you extract the nandroid from original rom folder to working rom folder, do you get any errors during that process?
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
Are you talking about Dsixda's kitchen?
I think the main reason is because you're doing it by a nandroid.
Did you try pulling the system folder via ADB?
The main issue might be because of the way you're getting a system dump.
It's better to just compile from source for AOSP, IMO.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
I'm using the last version kitchen. Working off my backup as base. No errors at all extracting to working directory. Rom builds, I zipalign and sign with no errors. Must be something in the installation scripts. I need to examine further. Must be a permission issue or links aren't being properly created.
Your using Windows or Ubuntu? I've noticed that dxdia kitchen is a bit buggy when it comes to extracting the updater script from nandroids or from a stock ruu using Windows..
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
ravike14 said:
Your using Windows or Ubuntu? I've noticed that dxdia kitchen is a bit buggy when it comes to extracting the updater script from nandroids or from a stock ruu using Windows..
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I haven't used Windows for years except for rooting tools for which there is no Linux counterpart. I run Gentoo Linux from the unstable (testing) branch, more specifically ~amd64. Every application, library, and compiler on my machine was compiled from scratch and optimized for my setup.
Odysseus1962 said:
I haven't used Windows for years except for rooting tools for which there is no Linux counterpart. I run Gentoo Linux from the unstable (testing) branch, more specifically ~amd64. Every application, library, and compiler on my machine was compiled from scratch and optimized for my setup.
Click to expand...
Click to collapse
i'm not sure if it has anything to do with it tho, however dxdia kitchen works perfectly for me in Ubuntu 12.04 LTS
Related
So... II am having a issue I can NOT find anyone else having. After upgrading from UBUNTU to LinuxMint GNOME 64Bit (Clean Install)... I CAN NOT get Android Kitchen to extract my ROMs. Never had a problem prior. When I choose to Setup my working folder and choose my ROM (which was built in Kitchen) i get "Error No system folder found".
Anybody have some insight?
Could it possibly have anything to do with switching from GNOME 3 to GNOME 2 or vice versa? Not sure what versions you're running. I've only dabbled around with Linux a little bit but I know it can be a real pain in ass getting some programs to work. I recently switched back to Ubuntu from windows 7 and then to bodhi Linux sense its a little easier on resources.
Sent from my DROID BIONIC using xda premium
Your AXIOM can't find? Like AXIOM very much!
:good::good::good::good::good:
DroidTh3ory said:
So... II am having a issue I can NOT find anyone else having. After upgrading from UBUNTU to LinuxMint GNOME 64Bit (Clean Install)... I CAN NOT get Android Kitchen to extract my ROMs. Never had a problem prior. When I choose to Setup my working folder and choose my ROM (which was built in Kitchen) i get "Error No system folder found".
Anybody have some insight?
Click to expand...
Click to collapse
The 2 main programs that the kitchen depends on is jdk and sdk,make sure that the paths are correct and linked to kitchen and that you have installed all the tools used for sdk and kitchen.
what steps do i take to know that the rom i made is going to work other than flashing it?
I am compiling ICS for my Galaxy Nexus using Ubuntu and a tutorial I found. I didn't give my VM enough disk space, so it ran out during the compile process. I'm growing the VM's hdd and am going to re-try the build, however, I'd like to clean up the mess that I made already on the VM. What do I need to delete in order to get to where I started before running "make"? I guess what I need to do is deleted whatever has been compiled, but I'm not sure exactly where those files are within my development directory. Thanks!
i would just delete the "out" directory in the root of the source directory.
Thanks. Apparently "make clean" does it too.
Sent from my Galaxy Nexus using Tapatalk
As of you guys have found out there has been a few threads that have been started that throw around theories about getting CWMR to work and such and I'm here to finally give you guys the progress from the dev that's working on it.
I have been working on getting CWMR working off and on for a few months now to some avail. I have been slowly testing it and sending out alphas to people on the IRC and now I'm here to tell you where I'm at and what has been accomplished.
Part 1: Getting into CWMR
I started working with our current bootstrap recovery as a base for CWMR. It was of course in charge mode, but it was a step that had to be done first. I got a hold on a CWMR binary and after a bunch of shell commands managed to get the mangled version of CWMR that we've seen before. From there I had the idea to inject the ATRIX binary into the recovery and try it from there. It was a big success and I could use some (very few) of the functions that if offered. But I was finally in CWMR on the X2. (I posted the picture on my twitter).
Part 2: Making the Functions Work
From here the first thing I decided to do was to get the "Fix Permissions" script working. By getting this to work I know I could place my own code in there that will log to the file that I could open up and see whatever I wanted as ADB didn't work YET (more on that later). I fiddled with it a bit and got it working.
This also allowed me to access the log and find out why the unmounting and formatting wasn't working either. This was due to an issue with the mke2fs and other complementary binaries not being appropriately compiled for our phone. As I was working on CM7 at the time, i had access to the sources of these and to the recovery binary as well. I decided to build a recovery binary that was tailored to our phone and not the ATRIX and the binaries that handle formatting partitions, etc. These worked on some partitions I could wipe data and cache properly by reformatting, I could easily erase a partition at will except for one: /system.
Part 3: Getting /system Formatted (WIP)
At this point I decided to find out why /system could never be formatted. When a partition needs formatting it must be unmounted first. But I could never unmount /system. By using the logs I found out that the partition was still in use. By using the "Fix Permissions" script, I managed to find that a lot of daemons (aka services) were being ran from the /system sub directories. This meant that in order to format, I had to have them not running. Easy enough as there's a script in CWMR that allows us to kill certain processes before the new recovery starts. I decided to kill all of the services with this script but found that the display would go blank. From there I found that two services are REQUIRED to be running on the phone for drawing (making things show on the screen) to take place: servicemanager and nvrm_daemon.
The servicemanager does exactly what it's title says: it manages the currently running services. This has to be running to keep nvrm_daemon running or else things get kinda freaky.
nvrm_daemon is what is used to manage drawing commands to the screen (the nv stands for nVidia which is who made the Tegra 2). With this service running I was able to (while in charge mode still) draw to the screen and show all of the menus for CWMR.
This created a problem. As these HAD to be running /system could never unmount because they were in there. Unless we used 2nd-init. From here I created my own hijack script that allowed me to copy over the necessary daemons into /sbin (which is just a sub directory of the rootfs). Then by using a new init.rc I could start these daemons from /sbin and see if they worked for CWMR.
After a lot of coding I managed to get the daemons running from /sbin and I thought I was free from there. And while I was at it, I might as well tried to get it out of charge mode.
Part 4: Untethering the Recovery (WIP)
I figured that since I was using 2nd-init anyway that I might as well have been working on trying to get it untethered also. After a bunch of looking into why charge mode was the only way to get it working, I found that before charge mode was started the init.rc started the "pre-zygote" services. These include usbd (the usb daemon), battd (the battery daemon), etc. What was also started was nvrm_daemon (another proof that we needed this running) to draw on the screen (charge mode draws the battery indicator to show charging progress).
I decided to move to mot_boot_mode to do the hijacking. I eventually managed to get things running but it still wouldn't draw to the screen. A look at the logs showed that for whatever reason we still didn't have access to the framebuffer (the memory space aka buffer that is drawn to the screen). I was tired of rebooting over and over again to get results and by now I had SBF'd I don't know how many times, only to not be able to access the logs due to a wipe. So next thing I decided was to get ADB working at boot.
Part 5: Starting ADB at Boot (The Short Version)
I took a look through the init.rc and found that Motorola had disabled the default way to get ADB working at boot. Through a bunch of digging I found that I could re-enable the method but it started usbd also (yet another daemon I'd have to move and thus more time, etc.). But eventually I found another property (aka system variable) that i could set that would start ADB without having usbd started: persist.adb.enable_NV_DISABLED. Setting that to 1 started ADB whenever I wanted it to. This allowed me access to the system (as root actually) without having to reboot and try to get into logs and whatnot. I could see everything that was running, mount/unmount and do everything I normally could and see better why they were failing.
Part 6: Recent Discoveries (as of 1/3/12) On the /system Unmount
I decided that I was going to go back to charge mode for now. After causing too much pain with framebuffer access I decided to look into why /system STILL wouldn't unmount after moving everything out of there. With the help of mastafunk and DrPenguin I was able to get a hold of a program named strace. This allows you to debug what binaries are doing down to pretty much every comparison, file opening, memory mapping, etc. I had found that nvrm_daemon (although started from /sbin) was looking for and loading drivers found in /system/lib. This was a problem and I thought that we may never get /system unmounted. Until I found out one other thing.
The nvrm_daemon doesn't look for the drivers inside of /system/lib first. It looks for them in /vendor/lib first and then if it can't find them, goes to /system/lib. So simple enough. I thought I could just make a /vendor/lib directory, copy the libs over and have them load from there. Well it's not that simple as there is already a file in the rootfs named vendor. But the file is a symlink to /system/vendor so if it looks at /vendor/lib it really looks at /system/vendor/lib. I thought I was stuck again until I took a closer look at the /system directory. There is no ./vendor sub directory in /system. That being said, I was able to delete the symlink in the rootfs and then create a /vendor/lib directory copy over the libs to it and nvrm_daemon successfully loaded the libs from there and not from system.
Conclusion
You are now caught up on when we've basically done to try to get CWMR working on the X2. Being that we're the only Tegra 2 phone from Motorola that is locked, we're kinda stuck trying to get things working. For now I consider this progress. Albeit slow progress, but progress none the less. If you took the time to read this, I hope you now understand the frustrations I've had to deal with this. All the while trying to help masta get 2nd-init fully working for our phones.
Thank you.
Thank you very much for the detailed explanation - well written so that even a novice like myself could understand your progress and frustrations. Thank you to you and your peers also for your hard work and determination to see this through. I think I can speak for all X2 users and say this is most appreciated!
Great writeup. Very informative. Thank you for your dedication.
I thought 2nd init was done and masta was working on aosp? I mean we can log from our new init.rc so it is using it. In the meantime i've been working on my barebones so we can get new blood using 2nd init and because I want a decent daily driver in the event we cant get stuff going.
To echo what others have said, thank you very much for the information. This kind of transparency is always very much appreciated when there's some spare time to put that out there. It not only is really helpful to make it understandable, but it's nice to know that these projects are still active.
Perhaps most importantly though in the context of potential progress: having specific information is a great way for knowledgeable people reading to recognize if they might be able to help out in certain areas. You might get some fresh ideas from people who hadn't considered themselves familiar enough with the situation to be useful. Who knows.
Anyways, thank you very much again. It's very encouraging to hear progress reports in general, not to mention ones like this that involve so many successes.
Wow thanks so much for your hard work and dedication can't wait until you conquer this sounds like you are closer then ever
Sent from my DROID X2 using XDA App
I am so glad to hear the "behind the scene" drama. Thank You DK sharing. I AM sorry for what bad drama I may have started. Will you forgive me?
skwoodwiva said:
I am so glad to hear the "behind the scene" drama. Thank You DK sharing. I AM sorry for what bad drama I may have started. Will you forgive me?
Click to expand...
Click to collapse
No need to appologize man... Stuff like this should have been posted or known. To be honest, I thought Masta was finishing 2nd INIT and starting to work on getting AOSP running and CWM was out the window, thats why I jumped in to try and get progress on CWM. Thanks DK and now I know the IRC is more active, I will be on there more to try and help out.
Thank you!
Thanks a ton for all the effort you're putting in. When I got my DX2 I thought that despite the crazily over-bloated Motoblur, I would be OK due to the Tegra 2 power and wonderfully innovative developer community. I didn't count on their being such a small number of us out there for this device or the complexity that Moto would unnecessarily bake in. So, after many months of gut wrenching disappointment, I finally have hope again.
You are a true nerd hero, sir!
Its nice to have an explanation of things and why they work or dont work. A lot of us are just trying to learn so we can be useful.
Sent from my Eclipsed and ICS themed X2.
Dragonz...after reading the info about 1/3/12 I am curious...
Does this mean that you might be able to get it working and unmount system as u need it to?
Or were there still other processes using system that you will need to mess with and change around as you did with the vendor ?
Do you still need to move the servicemanager also?
O btw imma start Hopn on the irc. I have a cm7 nightly booting thanks to second init but am having some crashes, not to mention other horrific bugs.. I need some help
Sent from my DROID X2 using xda premium
PM me with a copy of your nightly so I can help as well please
kaliblazin707 said:
O btw imma start Hopn on the irc. I have a cm7 nightly booting thanks to second init but am having some crashes, not to mention other horrific bugs.. I need some help
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Kali send me a pm, I have the week off and work as a mobile developer... would like to help get rid of some of those crashes. Send me a link to that irc and ill get cracking on it 2moro
Sent from my DROID X2 using xda premium
drapp said:
Kali send me a pm, I have the week off and work as a mobile developer... would like to help get rid of some of those crashes. Send me a link to that irc and ill get cracking on it 2moro
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Webchat.freenode.net
Channel #X2-AOSP
AND #DX2 for "off topic"
kaliblazin707 said:
O btw imma start Hopn on the irc. I have a cm7 nightly booting thanks to second init but am having some crashes, not to mention other horrific bugs.. I need some help
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
I know why you have a cm7 nightly "booting" and I'm sorry to say that it's not for good cause. What is happening is that the system isn't being formatted properly (hence a point in my post) and you're just flashing a bunch of new APKs from CyanogenMod on top of BLUR. I'm sorry to say, but it's not CyanogenMod.
dragonzkiller said:
I know why you have a cm7 nightly "booting" and I'm sorry to say that it's not for good cause. What is happening is that the system isn't being formatted properly (hence a point in my post) and you're just flashing a bunch of new APKs from CyanogenMod on top of BLUR. I'm sorry to say, but it's not CyanogenMod.
Click to expand...
Click to collapse
I honestly think the way to go is to get back to that step with proper 2nd init and then replace everything blur with as much CM as possible
aceoyame said:
I honestly think the way to go is to get back to that step with proper 2nd init and then replace everything blur with as much CM as possible
Click to expand...
Click to collapse
But that's not the right way to go. All that is is basically taking the BLUR base ROM and replacing the things with CM7's stuff. That's basically taking the stock rom and turning it into another blur-based ROM with CM7 apks. That's basically like Eclipse.
dragonzkiller said:
But that's not the right way to go. All that is is basically taking the BLUR base ROM and replacing the things with CM7's stuff. That's basically taking the stock rom and turning it into another blur-based ROM with CM7 apks. That's basically like Eclipse.
Click to expand...
Click to collapse
Let me rephrase that, add CM stuff and then remove Moto stuff. So get back to that, delete moto apk's and then edit init.rc for the framework. All those FC's we are getting if when were in that state are vital clues as to whats isn't playing nice with CM's apk's and framework. The fact it can even somewhat boot in a state like that means it's fairly close to how it wants. If it didn't wipe /system/ then it sounds like you just need to properly 2nd init that ***** and then in moto's init.rc remove moto jar's and apks's. Remember if it didn't wipe then you replaced the framework with CM and it's blur running ontop of it.
ashclepdia said:
Webchat.freenode.net
Channel #X2-AOSP
AND #DX2 for "off topic"
Click to expand...
Click to collapse
Thanks ashclepdia.... helpful as always...
Sent from my DROID X2 using xda premium
I have noticed that many people have had issues rooting their phone, especially recently. And i have also gotten tired of typing or copying the root method over and over after flashng in RSD and loosing root.
In response to that i have taken it upon myself to write a script for automating a majority of the process for all of us, making the process swifter than before. However this is not a one click root there are many steps nessecary to root our device. All i have done is wiritten a script to automate a majority of the process.
I will only test one version of the script, the ubuntu 12.10 version, because thats the only operating system i run and its easiest to test this one. i will leave the other versions to other people and to post issues with them as they arise so i may fix them
there are several versions of the script
*Ubuntu - 12.10 and up
*Ubuntu generic - 10.04-12.04
*Linux generic - any version of linux
*Windows bat file - Must download Motorola drivers
*Android - NEW ALPHA!! can actually be run from another rooted phone or tablet!! Scripts for general use coming soon! Testers are welcome! Check out the second post for details.
each version has the nessecary files to root your phone and including the script
These are not flash able scripts these must be uncompressed and run on a computer
Oh and feed back is more than welcome im not an expert at writing scripts or any sort of write up but i will do my best to fix any flaws or add suggestions.
Post 2: Change Log & Unstable Versions
Post 3: Instructions
Motorola USB drivers
Motorola website
MyGoogle Drive
Change log and unstables
Change log:
Version 4 - for windoze only:
Cleaned up script and readme
tested script runs into an issue because of the way windoze command prompt works
will update the instructions to inclued a sepereate method meant for windoze
Version 3:
Changed initial reboot command to adb reboot
broke script into to parts to fix adb shell /preinstall/su issue
Version 2:
Not published
would not get past adb shell /preinstall/su
Version 1:
First version made
BETAS:not for the faint of heart
To use you agree to contact me via pm upon downloading to obtain the password. This is because I REQUIRE all who use unstable versions to provide details and information on what does and does not work and what I can do to improve the experience.
MX2-arm-root:
Version alpha 0.1
Initial creation
No scripts
Root must be applied manually
Will need USB otg cable or micro USB to micro USB cable for fastboot command use (required cannot be fixed to run any other way)
Otg cable can be purchased for a few dollars from Amazon or other electronic retailer
MX2_arm_root_alpha0.1.zip
broken beyond android 4.1.2
Instructions:
*Download the zip file for your computers operating system from post one
*decompress with your favorite arcive manager i prefer 7zip
*READ THE README!!!!
*run initial script aka MX2-2.3.6-something-root
*follow instructions in the script
*CONTINUE TO FOLLOW THE README!!!!
*while your still in the adb shell as root run the following
*cd /sdcard
*sh android-script.sh
*your phone will reboot it should now have root update the su binary in the superuser apk
Windoze Instructions:
*decompress the zip and place somewhere easilly accessable by both windows explorer and command prompt
*READ THE README!!!!
*make sure drivers are installed- if at any point while the first script is running that drivers need to be installed(aka first time windoze has seen fastboot ect) wait for the drivers to finish installing before continuing.
*double click the initial script MX2-2.3.6-windows-root.bat
*follow the instructions in the script
*CONTINUE TO FOLLOW THE README!!!!
*close the script command prompt when finished
*open a new command prompt and do the following
*cd(to the directory where you uncompressed the zip
*adb shell
*/preinstall/su
*cd /sdcard
*sh android-script.sh
*your phone will reboot it should now have root update the su binary in the superuser apk
Ah, wow. Thank you so much for this. I didn't root my Milestone X2 2.3.6 on ACS Wireless for 6 months because I was afraid of breaking it (again.) I wish this was around a few months ago
Hopefully this helps everyone root their phone in a much easier and safer way.
By the way.. Does anyone have any suggestions on a working MX2 2.3.6 ROM? I'm still using stock, and I hate it.
there aren't any roms based on 2.3.6, doubt we will see any soon
Sent from my Milestone X2 using xda app-developers app
PotentChili said:
Ah, wow. Thank you so much for this. I didn't root my Milestone X2 2.3.6 on ACS Wireless for 6 months because I was afraid of breaking it (again.) I wish this was around a few months ago
Hopefully this helps everyone root their phone in a much easier and safer way.
By the way.. Does anyone have any suggestions on a working MX2 2.3.6 ROM? I'm still using stock, and I hate it.
Click to expand...
Click to collapse
Try eclipse its not 2.3.6 based but it runs wonderfully on the mx2. As for the script its mostly an untested product. I've runt the Ubuntu 12.10 one once with little issue but the rest I haven't tried. Just remember its a two part script that requires the running of both pieces to work.
As to having a rom 2.3.6 based there really is no point we have fully functional roms that run beautiful with what we have not to mention that there's no real point in going back if we get a kexec or second boot working as further versions are going to be based off of a newer kernel and version of android.
Sent from my Nexus 7 using XDA Premium HD app
I'm now rooted thanks to this script by Lrs121! I strongly recommend those new to the process of root to use this script because it works!
Sent from my Milestone X2 using xda premium
Got my phone rooted after a couple hiccups due to not reading carefully. A great tutorial; just make sure you follow the steps to the letter.
DonInKansas said:
Got my phone rooted after a couple hiccups due to not reading carefully. A great tutorial; just make sure you follow the steps to the letter.
Click to expand...
Click to collapse
I'm glad it was able to help. I tried to make certain things more autonomous but unfortunately it does have to be specific, and handled as such. So there's not a lot of flexability in how the process is done by the user and by the script itself.
Sent from my Nexus 7
I've tested some superuser managing apps and so far the only one that works for our device is chainsdd's app. Clockworkmod's and chainfires supersu do not work well or at all. Please use the chainsdds app from the market or keep the one that the script installs as they work best.
Sent from my Milestone X2 using xda premium
A new script is coming soon. It will be an android to android script where you can root your phone using another phone or an android tablet. Thanks will go to the guys who have developed the p2p-abd tools. If the fast boot binarys are included
Sent from my Nexus 7 using XDA Premium HD app
Alpha for the arm aka android script is up. Testers are welcome to play with it. This is a very very basic build. Nothing is automatic, will be worked on as I go. The download, requirements and minor change log of what's included can be found on the second post. that post is now change log and unstable versions. Read what's included on the the log before trying. If you want to try but don't have and otg cable flash the preinstall img using a computer and play around with the arm adb binaries. Credit for the arm versions of the adb and fastboot binaries go to the original developers, they will be listed as I find the correct threads and sites I pulled them from are found.
Sent from my Nexus 7 using XDA Premium HD app
not working :|
hey guys. I know this is an old thread but I cannot get this script to work. I get to the last command and I get sh: can't open android-script.sh
This is the only problem I am having. Any thoughts?
zaq_37 said:
hey guys. I know this is an old thread but I cannot get this script to work. I get to the last command and I get sh: can't open android-script.sh
This is the only problem I am having. Any thoughts?
Click to expand...
Click to collapse
which pack did you use, each script is a little different
Lrs121 said:
which pack did you use, each script is a little different
Click to expand...
Click to collapse
Sorry I should have specified. It's the windows Pack.
Are you using it on windows 8?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Lrs121 said:
Are you using it on windows 8?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sorry. I meant to get back to you earlier, I've been busy. No. I'm running Windows 7. Used the Windows Pack and ran through the instructions/README and got hung on that last step when the script wouldn't run.
I have a bootable CD of a few Linux OS's should I try one of those instead of through Windows? Is there a specific OS that the Linux script doesn't work on. I am a fan of LinuxMint and CentOS but I also have an Ubuntu CD as well.
zaq_37 said:
Sorry. I meant to get back to you earlier, I've been busy. No. I'm running Windows 7. Used the Windows Pack and ran through the instructions/README and got hung on that last step when the script wouldn't run.
I have a bootable CD of a few Linux OS's should I try one of those instead of through Windows? Is there a specific OS that the Linux script doesn't work on. I am a fan of LinuxMint and CentOS but I also have an Ubuntu CD as well.
Click to expand...
Click to collapse
Hum I wonder what broke the windows script. Um really its up to you I can try to tear it apart and see if what's wrong but I'd need specific information from you in what's happening. But I'm a better Linux script writer so the Linux scripts are a bit more stable. Ubuntu 12.04 and up is best because the repositories have adb and fastboot included and can be installed. Both of which the script requires to run but any of the linux ones should work.
Sent from my SCH-I535 using XDA Premium 4 mobile app
On a side note I think I I figured out what's wrong. If I'm right correct me if I'm wrong, you tried to run the android-script.sh script from windows. If I'm wrong then I think the issue may be due to permissions
Sent from my SCH-I535 using XDA Premium 4 mobile app
Please help.
I recently received my Motorola Milestone X2 running 2.3.6. I have followed your method to a T. After the adb shell cmd, I receive no Superuser prompt. Then, after typing in the /preinstall/su cmd, it says: file not found, or file does not exist. I cannot remember. Can you help?
Thanks,
Jeremy
hi im looking at maybe buying a ubuntu phone on the next flash sale or intsalling it on my nexus 5 and 7
but not sure if its good enough on the nexus 5 and just worth trying to buy one
two questions how does it run now on nexus 5 is it ready for day to day use and will the operating system be current like the one on the ubuntu phone
and were do i find a list of scopes and apps available
like i want to run nvpy can i just install as i do native like on a ubuntu
many thanks
wayne
Here's an unofficial store frontend: https://appstore.bhdouglass.com/apps
And yes, you can install debian packages, but that breaks OTA updates.
update
And yes, you can install debian packages, but that breaks OTA updates.[/QUOTE]
i change to and remounted RW
and did update and upgrade all worked fine but killed my dual boot
so if i did RW and then update
and installed say lifeograph would it install that package and be useable from the repository?
wayneward said:
And yes, you can install debian packages, but that breaks OTA updates.
Click to expand...
Click to collapse
i change to and remounted RW
and did update and upgrade all worked fine but killed my dual boot
so if i did RW and then update
and installed say lifeograph would it install that package and be useable from the repository?[/QUOTE]
Did you upgrade using the system settings update mechanism? That won't be blocked and the update will seem to work, but things will break after some time, just like your dual boot, especially when you start installing custom packages.
Theoretically, the application should work, but you're going to have to set up XMir properly to run X applications. If you are interested in doing that, the guy who made this video is the one who can tell you: https://www.youtube.com/watch?v=c3PUYoa1c9M
This video may be helpful, too: https://www.youtube.com/watch?v=XfMLzlki9XE
AND you'll have to install the devel-proposed channel as stable/rtm doesn't contain the necessary software yet.
I got root write - updated and upgraded and it killed my nexus 5 install basicaly wrote over the boot sector I think !
Can I not get a chroot for ubuntu apps I have on ubuntu and would they run? For example lithograph?
Ill take a look I've installed the sdk to test as well I'm certain these apps will get added soon scopes are great but being able to install ubuntu apps like lifeograph and other apps would be amazing.. Is this on the cards or do the developers have to release the touch apps version ?
Sent from my awesome Ubuntu Touch device using the Forum Browser app
wayneward said:
I got root write - updated and upgraded and it killed my nexus 5 install basicaly wrote over the boot sector I think !
Can I not get a chroot for ubuntu apps I have on ubuntu and would they run? For example lithograph?
Ill take a look I've installed the sdk to test as well I'm certain these apps will get added soon scopes are great but being able to install ubuntu apps like lifeograph and other apps would be amazing.. Is this on the cards or do the developers have to release the touch apps version ?
Sent from my awesome Ubuntu Touch device using the Forum Browser app
Click to expand...
Click to collapse
I'm sorry for you killing your boot sector. Were you able to set up everything again?
I tried the chroot method some time ago but you still need to install the necessary packages for that using apt-get. So you need a writable system again...
You could, however, try to package the apps as a click package yourself. I've never tried that and I don't know of anyone who did, but if you ship xmir and the application in a click package, it should work.
I just had to reinstall and re-root was good really because got it set up right now.
I'm did a emulated rw and compiled lifeograph from source that it might work but it wont connect to mir using cmake there must be a use flag or ill look are cross compiling maybe.. Does it create a click package or a deb ? Ill take a poke around in apt cache to look at packages already cached from install
Sent from my awesome Ubuntu Touch device using the Forum Browser app
wayneward said:
I just had to reinstall and re-root was good really because got it set up right now.
I'm did a emulated rw and compiled lifeograph from source that it might work but it wont connect to mir using cmake there must be a use flag or ill look are cross compiling maybe.. Does it create a click package or a deb ? Ill take a poke around in apt cache to look at packages already cached from install
Sent from my awesome Ubuntu Touch device using the Forum Browser app
Click to expand...
Click to collapse
Great that you got it sorted out.
There's a trick to get the app working on Mir: Lifeograph is an app for the X window system. To make it run with Mir, there's a software called Xmir. Check out whether it's in the repos. If not, the source code should be online somewhere.
The app is probably going to compile as a debian package though. Either you stay with your phone in rw mode or you look into packaging it as a click package. The latter might be a little bit more difficult.