Related
Dear Users,
I am experiencing an issue which has been raised once before and no clear,
simple solution was found.
My current problem is that, after updating my G1 from 'cupcake' to 1.6, all
the calls I make and all the calls I receive are labelled as 'unknown',
despite the fact that these numbers are in my contacts. Here is the link to
the similar issue which was officially declined by Google:
http://code.google.com/p/android/issues/detail?id=2949
In the discussion thread amoung the users, there seem to be two possible
solutions (although this was not confirmed by Google, since the issue was
declined):
1. Complete factory reset.
2. STEPS:
1) Get to a shell prompt. If you're using ADB, it's "adb shell". If
you're using a
terminal/console app, just launch it.
2) Type "rm /data/misc/rild_ril.clip"
3) Reboot the phone.
My phone is currently not rooted and I have no intentions to root it in the
near future. Also, I do not favour the idea of a factory reset, since I
shall have to re-install all my applications, which will take time. The
second method to solve the problem seems the most probable in my case,
however the only problem is that, since I am not very good on the technical
stuff (i.e. 'shell prompt', 'console app', 'ADB'), I cannot figure out how
to perform what that method requests.
I would be very grateful to a person who would explain how to sort the
problem out in clear, step-by-step, user-friendly language.
The first method would be easiest for you but the second method makes the most sense. ADB is easy to set up & there are guides on here for it, also it doesn't require you to be rooted.
PS: This is in the wrong section so expect the mods to move it quickly.
You should start by trying option two.
1. Goto the market and search for Terminal. Downlaod and install the app.
2. Open your app drawer and open Terminal (The app you just installed)
3. Enter the line rm /data/misc/rild_ril.clip and hit enter.
If the command is accepted you'll get a blank prompt, type reboot and hit enter again to reboot the phone. If you get a mesage that says the command can't be completed, read only file system you'll probably need to setup ADB on your computer and enter the commands there. Search XDA for ADB for Dummies to find a thread on how to set up ADB, its really very straightforward.
Good Luck!
You could also go into Application manager and see if you can clear your Dialer or Dialer storage's cache or data (whatever they have there). I assumed that you've tried powering your phone off and on to see if that fixes it, right?
If you dont have root, you wont be able to remove stuff from the system.
It sounds like you have your contacts numbers saved without a 1 or 0 such as,
555-555-5555
1-555-555-5555
Try to edit the numbers and make them appear the same way they do when a contact calls you. I am sure this will solve the problem.
Hi Everyone
I updated to 2.1 and rooted my phone (htc hero, sprint) yesterday. While I was going through the setup process I was having problems with the syncing of my contacts (going to to people -> groups -> menu ONLY yields the options add group and delete group there is NO sync groups) My phone is syncing all 500 email contacts to my phone which is not what I want. A factory reset will remove my gmail account and allow me to add it again hopefully doing so will bring back the sync groups option (resetting over and over is usually the tactic I have done in the past when I have had problems with contact syncing)
My question is: being that I have rooted my phone what effect will a factory reset have on the now running rooted rom?
If doing a factory reset is not advised any suggestions on what I should do, should I restore the backup I made just after rooting prior to setting up the phone with all the accounts?
In your Backup recovery menu.
Go to wipe and then data should do what you want from the recovery menu without messing with root.
I beleive it is ok to factory reset your phone becouse i beleve it deletes deletes /data.
Or in your settings menu and go to accounts, and then select your gmail account. from here you can un check sync contacts with google. that will keep them from syncing
I currently have the sync contacts unchecked the problem is I actually want to sync my contacts just only certain groups that I have created in gmail.
Yes a factory reset does whipe data I just wasn't sure if it did anything else that is why I thought I would post here first before attempting anything.
Sorry if this is a newb question but how do I get to backup recover menu?
Are these steps correct:
1 plug the phone into the computer via usb port (making sure usb debugging is on & in charging only mode)
2 from the adroid sdk tools directory execute the following commands:
2a adb devices
2b adb shell
2c su
2d reboot recovery
now be in the recovery menu
3 wipe
4 data
I find it's easier (So long as your phone has an adequate charge) to Hold the end key until a menu pops up and hit power off. Then hold Home + Power until your recovery loads. Your method should work too but I don't think you have to issue su.
If I remember what I read a while back about syncing contact info on 2.1 was that they removed that feature in the 2.1 OS.
Edit: Here is a thread about this issue http://forum.xda-developers.com/showthread.php?t=689314
Hi everyone
I have an Asus laptop and I would like to reset it to factory settings (like wipe data in android) so all programs and settings I have made will be deleted. I dont want to reinstall windows I just want to delete all programs and reset settings so the computer will be like when I bought it Is there anyway to do this on windows7 and if its possible - how to do it?
Lol that doesn't exist really in Windows itself. Or you need to go back to state it was in when you bought it by using the recovery.
i agree with tomsteel1, the only way is to reinstall windows, i did this and backed up everything before i reinstalled windows.
Tap f9 during startup. That should load the recovery partition.
Sent from my ADR6400L using XDA
I've owned many laptops over the years, and have yet to come across a laptop that will not do what is called "Full Destructive Factory Reset."
All user added software and files are whipped clean, and the system reverts back to the way it was shipped from the factory.
For HP it's under all programs>system recovery>PC Recovery and then follow instructions.
For Lenovo there is a special "Think Vantage" blue button that you press during boot-up, AND you can also access the recovery program from "all programs." Every manufacture offers these Factory recovery programs, and sometimes they vary slightly as to how they're implemented, but they all do the same thing. (don't confuse Microsoft Windows Restore operations with Full Factory restore operations)
If you no longer have the owners manual for your laptop, which will tell you how to perform a Full Factory Restore Operation, just google your Asus model # and Full Factory Restore, or go to the Asus Support Website, and you shall prevail.
Edit: If this was not the type of restore operation you were looking for, the previous outlined steps will also list all available options.
TravisBean said:
I've owned many laptops over the years, and have yet to come accross a laptop that will not do what is called "Full Destructive Factory Reset."
All user added software and files are whiped clean, and the system reverts back to the way it was shipped from the factory.
For HP it's under all programs>system recovery>PC Recovery and then follow instructions.
For Lenovo there is a special "Think Vantage" blue button that you press during boot-up, AND you can also acess the recovery program from "all programs." Every manufactuar offers these Factory recovery programs, and sometimes they varry slightly as to how they're implimented, but they all do the same thing. (don't confuse Microsoft Windows Restore operations with Full Factory restore operations)
If you no longer have the owners manual for your laptop which will tell you how to perform a Full Factory Restore Operation, just google your Asus model # and Full Factory Restore, or go to the Asus Support Website, and you shall prevail.
Click to expand...
Click to collapse
Looks like you didn't own enough lol. I've seen many laptops without it.
As to how to do it, when the computer turns on, and you get the first screen and look at the bottom. It might say something along the lines of "Press F# for system recovery". If it doesn't boot into windows, and check if you have a recovery partition. Right click My Computer->Manage->Disk Management, and check if you have a partition called recovery.
jaszek said:
Looks like you didn't own enough lol. I've seen many laptops without it.
Click to expand...
Click to collapse
Must have been before my time. Unless his Asus is ancient, their support website and/or his owners manual will give explicit step by step instructions for performing all restore operations.
I dont have the recovery partition. I only have system reserved, C:, and two unnamed partitions (70 and 4 GB) I think they are for ubuntu since I also have ubuntu installed so I dont even have normal startup but only asus screen then OS select and then "starting windows" screen. The manual says that there should be a recovery partition but probably previous owner deleted it (I am 2nd owner). s there any hope for me to get computer back in original state? And if I reinstall windows will I still be able to get programs that were originally installed on it (turbo33, fingerprint unlock, power4gear hybrid...)?
yannn007 said:
I dont have the recovery partition. I only have system reserved, C:, and two unnamed partitions (70 and 4 GB) I think they are for ubuntu since I also have ubuntu installed so I dont even have normal startup but only asus screen then OS select and then "starting windows" screen. The manual says that there should be a recovery partition but probably previous owner deleted it (I am 2nd owner). s there any hope for me to get computer back in original state? And if I reinstall windows will I still be able to get programs that were originally installed on it (turbo33, fingerprint unlock, power4gear hybrid...)?
Click to expand...
Click to collapse
Ahhh, then they removed the recovery partition. You will need to use a windows CD (download it, it's legal) and use the key from the sticker on the bottom of the laptop. Than download all the drivers from Asus support website, and the might have all the programs (bloatware) there to download as well. If you don't have another computer, download the drivers before doing anything and keep them on a flash drive. Once you reinstall you might not have the LAN/WiFi drivers installed.
There may still be hope, try bashing "F11" on startup and see if you get to a recovery console, your 4gb partition could still be the recovery partition, if you want to explore it you can right click on my computer -> manage -> disk management -> click on the partition and click change drive letters and paths -> add a drive letter.
If this is completely useless then as the person above said (However the legality of obtaining an installation disk is questionable, also be careful with whether you are downloading an OEM version or RETAIL version, as your key is specific!) you can simply re-install windows and visit the asus site, punching in your model number from the bottom of the laptop !
The other 2 partitions are ext4 and are for linux so no recovery partition If I decide to format and install windows I download from somwhere will I be able to use original serial for activation? Because I see a lot of people have troubles activating (illegal) windows...
yannn007 said:
The other 2 partitions are ext4 and are for linux so no recovery partition If I decide to format and install windows I download from somwhere will I be able to use original serial for activation? Because I see a lot of people have troubles activating (illegal) windows...
Click to expand...
Click to collapse
as long as u haven't activated 3 times, u should be fine
Solved - Follow this - http://forums.webosnation.com/hp-touchpad/318426-how-install-android-without-setting-up-webos.html
Here is a series of steps that lead me to this problem.
1) I wanted to give my touchpad to a friend of mine. So I removed the dual boot. I also booted to WebOs and did a factory reset. The touch-pad is now in pristine state. So far so good. No problems.
2) My friend takes the touchpad from me but never goes thru the setup. He then looses it !!
3) Once I came to know about it, I went online and initiated a remote wipe. I don't know why I did that since it was already clean (from step 1 above). I think this action of mine created a problem.
4) My friend finds the Touchpad. It was in his home all along. So I charged it and then boot into WebOs.
5) This is where the problem starts. The initial webOs setup requires that I set up a new account with HP ( or use an existing one). First, I tried to use my existing account (the same that I used in step 3). It won't log in saying that there is a login error, try again or contact HP support. The password is correct, since I am using the same password on the HP website and I can see my device there.
6) I then tried to create a new account using a different email. To my surprise, that failed too. I tried a few other emails, all with same results. The new account creation was failing in all these cases.
7) Now I am stuck. I have emailed HP for support but I was hoping someone else had any other ideas. I am out of warranty. So email support is the only thing that I can get from HP.
8) Is there is a way I can install Android on it without launching webOs - Can I create a cmInstall folder from WebOs recovery ? ANy Novacom driver option to access the file system ? The only way to get the cminstall folder (that I know of) is to boot into webOs and I cannot do that.
I have tried a few other things that came to my mind.
1) I used WebOs Doctor to do a clean install. It still did not help. The log-in still fails.
2) I removed the device from my old account thinking that it might be the reason my new account creation is failing. But that did not help.
Any suggestion or links that might help me would be really appreciated.
[email protected] said:
Here is a series of steps that lead me to this problem.
1) I wanted to give my touchpad to a friend of mine. So I removed the dual boot. I also booted to WebOs and did a factory reset. The touch-pad is now in pristine state. So far so good. No problems.
2) My friend takes the touchpad from me but never goes thru the setup. He then looses it !!
3) Once I came to know about it, I went online and initiated a remote wipe. I don't know why I did that since it was already clean (from step 1 above). I think this action of mine created a problem.
4) My friend finds the Touchpad. It was in his home all along. So I charged it and then boot into WebOs.
5) This is where the problem starts. The initial webOs setup requires that I set up a new account with HP ( or use an existing one). First, I tried to use my existing account (the same that I used in step 3). It won't log in saying that there is a login error, try again or contact HP support. The password is correct, since I am using the same password on the HP website and I can see my device there.
6) I then tried to create a new account using a different email. To my surprise, that failed too. I tried a few other emails, all with same results. The new account creation was failing in all these cases.
7) Now I am stuck. I have emailed HP for support but I was hoping someone else had any other ideas. I am out of warranty. So email support is the only thing that I can get from HP.
8) Is there is a way I can install Android on it without launching webOs - Can I create a cmInstall folder from WebOs recovery ? ANy Novacom driver option to access the file system ? The only way to get the cminstall folder (that I know of) is to boot into webOs and I cannot do that.
I have tried a few other things that came to my mind.
1) I used WebOs Doctor to do a clean install. It still did not help. The log-in still fails.
2) I removed the device from my old account thinking that it might be the reason my new account creation is failing. But that did not help.
Any suggestion or links that might help me would be really appreciated.
Click to expand...
Click to collapse
When you tried to doctor, did you go back to 3.0.0? If you didn't, here's a good guide :
http://forum.xda-developers.com/showthread.php?t=1426244
You have to go back to 3.0.0 because it's the only one who can handle partitions. After you successfully do 3.0.0, you can update to 3.0.5 OTA. Then install android the usual way.
Read the whole thing. Around page 12 there's a good work around if you're having trouble with novaterm.
Good luck.
chicle_11 said:
When you tried to doctor, did you go back to 3.0.0? If you didn't, here's a good guide :
http://forum.xda-developers.com/showthread.php?t=1426244
You have to go back to 3.0.0 because it's the only one who can handle partitions. After you successfully do 3.0.0, you can update to 3.0.5 OTA. Then install android the usual way.
Read the whole thing. Around page 12 there's a good work around if you're having trouble with novaterm.
Good luck.
Click to expand...
Click to collapse
Yes I did doctor to 3.0.0. The problem is not that I am unable to install WebOs. The problem is that when the setup screen comes and I provide the user-id/password, it doesn't take it. It seems like my Serial Number is somehow blocked by HP since I did a remote erase. Or maybe the remote erase and the initial setup are getting deadlocked - neither the remote erase can complete since its waiting for login to happen - and the login cannot complete since it thinks erase is in progress.
[email protected] said:
Yes I did doctor to 3.0.0. The problem is not that I am unable to install WebOs. The problem is that when the setup screen comes and I provide the user-id/password, it doesn't take it. It seems like my Serial Number is somehow blocked by HP since I did a remote erase. Or maybe the remote erase and the initial setup are getting deadlocked - neither the remote erase can complete since its waiting for login to happen - and the login cannot complete since it thinks erase is in progress.
Click to expand...
Click to collapse
Then I think only HP support can help. They have to unblock your serial number / account so you can have access.
chicle_11 said:
Then I think only HP support can help. They have to unblock your serial number / account so you can have access.
Click to expand...
Click to collapse
But I was hoping that even though I cannot log in, I can at least install Android. But to do that, I need to be able to create a cminstall folder and I cannot do that unless I can see the touch-pad file system from my PC. I was hoping that there is a way to do that without logging into WebOs. Meanwhile I am still waiting for HP to respond back to my email !!
Possible solution to this problem - bypass activation
http://forums.webosnation.com/hp-to...ources/317164-activation-bypass-touchpad.html
I haven't tried it but this gives me hope. I might be able to bypass activation after all !!
How to Install Android without setting up webOS
Seems like someone had the exact same problem that I had. Thanks Google.
http://forums.webosnation.com/hp-touchpad/318426-how-install-android-without-setting-up-webos.html
Hello everyone! Just like others here, I've been somewhat spooked by our inability to enter Ouya's Recovery partition at the earliest stage of booting, meaning a bad flash of the Boot partition would leave the device inoperable. When I heard that Ouya's stock firmware updates were possibly bricking a few units out there, I decided to block updates on mine and see if I could transform the Boot partition such that it would become a logical extension of the bootloader. What I ended up with is something close to the "Ouya Safe Recovery" project, where a user should only need to flash Boot one additional time, along with chain-loading support as well.
Chain-loading in this case refers to the booting of ROM kernel images that reside as regular IMG files under the /sdcard and/or /system filesystems. With this capability it is possible to choose an image to run when the Ouya turns on. As an example, one may wish to set up a 2nd/test kernel+ramdisk image to use with your installed ROM, or he may wish to run Tuomas Kulve's Debian project from time-to-time without having to set up the USB cable for Fastboot mode. When dealing with distinctly different ROMs (not just alternate kernels), only one of them may install to the Ouya's built-in storage (e.g., /system); others must have been designed/created to use external storage.
An image for the Recovery partition is available along with the Boot. The former may be helpful if you wish to try out the boot menu before performing the flash of the Boot partition, or are generally okay with bouncing to Recovery before invoking a chain-load. Either of these may be tested from Fastboot mode, but do note that a successful chain-load requires that the image actually be flashed to the Ouya. (Otherwise it just reboots.) The ClockworkMod (CWM) recovery application is available on both images and is accessible from the boot menu.
Additional Information
There are a few things to consider when deciding if this approach makes sense for you:
- Users of the "Ouya Safe Recovery" project may want to stay put unless the dual-boot aspect is of interest. If so then it would be cleanest to choose my Boot image; the Recovery partition (your ROM image) could be left alone.
- The images here are not compatible with Ouya's stock firmware, due to the auto-update nature of Ouya's ROM. Either your flashed Boot image would get overwritten, or an installed non-Ouya Recovery might cause that update to hang. Therefore, you should be prepared to switch to one of the ROMs here at XDA. If you're currently on stock and don't want to switch right away, that's fine; we'll go over how to block updates for the time being.
- The Ouya CM10 ROM is nice in that it provides the IMG file separately, allowing us to handle it as we wish. However, the other ROMs end up placing their boot.img in the main ZIP. This is standard practice for other devices, but we need to be careful ensuring our Boot partition doesn't get reflashed as part of the ROM installation. Therefore, it would be necessary to investigate repackaging the ROM with an alternate updater-script prior to installation. See my StockPlus post on page 2 for more. (This shouldn't affect those who've opted for my Recovery image.)
This feature is based on CWM's initial ramdisk, and includes a new boot menu application that comes up prior to CWM itself. Basically, CWM shows up later if the menu application exits for any reason. The Ouya stock kernel (561) has also been compiled with HDMI's copy protection turned off, and includes two patch sets:
- KExec-HardBoot is the key to chain-loading on our platform. It overcomes standard KExec's lack of hardware reset (and thus failed execution) by triggering a reboot in the middle of the preparation of the new kernel. This ingenious system has been developed by Tasssadar and others over in the Nexus forums. (Be sure to enable CONFIG_TEGRA_HARDBOOT_RECOVERY if interested in compiling a Recovery kernel.)
- HDMI visual stability has been improved with a little hack of mine: a significant relaxing of a timer in the driver. (The latest Android source has corrected the instability with a significant design change, but my hack seems fine enough for this project.) Also picked up specific Android fixes in the area of Framebuffer double-buffering, as that needs to be working for CWM usability.
Installation
If you're on Ouya's stock firmware, then you should make sure that any future updates do not get applied. There is a project here ("Mod Collection For Ouya") that should help. I personally side-loaded the Baxy custom launcher to avoid Ouya's update environment. It is also likely necessary to stay out of the Ouya/Discover store if going the custom launcher route as I believe the store app can trigger an update.
At this point you can download your chosen image (Boot or Recovery) and unzip to get the IMG file. Boot your Ouya to a working Root/BusyBox environment (ROM or Recovery), and then transfer the IMG to the Ouya. (An example using ADB would be "adb push boot102513.img /sdcard/boot102513.img".)
Bring up the Ouya command prompt (e.g., "adb shell") and run these commands to get started:
su [command not present on CWM - that's okay]
cd /dev/block/platform/sdhci-tegra.3/by-name
ls
You should see the various 3-letter partition names from that last command. Your command prompt should also contain the "#" character to denote root-level access. This next step will save off your current ROM image, both because we may end up overwriting it, and because the saved file will end up as your main bootable kernel for the chain-loader. Run:
cat LNX > /sdcard/kernel.img
(If configured for "Ouya Safe Recovery," then replace the preceding "LNX" with "SOS".)
We are near the flashing stage. Check to make sure your Ouya has a reliable source of power, preferrably from an uninterruptable power supply. Recall that a bad flash of my boot image can leave the device inoperable, but I feel the risk is very low provided the following directions are heeded. Fortunately the flash process only takes a few seconds.
For the Boot image option, verify by running:
md5sum /sdcard/boot102513.img
Do not proceed unless you get "e4b1b1ad553e55ad0b2ce3fb8f5bf623".
Again for the Boot image option, flash to the Ouya by running:
dd if=/sdcard/boot102513.img of=LNX
For the Recovery image option, verify by running:
md5sum /sdcard/rcvy102513.img
Do not proceed unless you get "dda0811a7e8e82a7d4ad3fa4c3ae35e4".
Again for the Recovery image option, flash to the Ouya by running:
dd if=/sdcard/rcvy102513.img of=SOS
You may optionally verify (post-flash) by running "md5sum" on the partition name. Finish up with these commands:
sync
reboot
Usage / Configuration
The menu should come up, defaulting to "kernel.img" for the Boot image and "CWM" for Recovery. That default will then launch after ten seconds of inactivity. You may also briefly press the Ouya power button during the wait to advance through the options. The option list is 1) kernel.img, 2) kernelA1.img, 3) kernelA2.img, 4) CWM, and 5) Recovery Partition.
The defaults from above should be fine for most everyone, but it is possible to fine-tune them. An optional configuration file (/sdcard/bootmenu_b.cfg for Boot, /sdcard/bootmenu_r.cfg for Recovery) may be established to specify the default menu entry as well as the inactivity timeout. As an example, the following command would make Recovery start kernelA1.img after five seconds:
echo "2 5" > /sdcard/bootmenu_r.cfg
It is hoped that the menu would never hang. If it does, then waiting a full minute should allow CWM to start. Otherwise, it may be necessary to attach a wired/USB keyboard and type in the Alt-SysRq-X sequence, similar to Ctrl-Alt-Delete on a PC. The sequence might have to be done early on in the menu startup process, and should blink the Ouya light and place it in Fastboot mode.
The menu may unexpectedly place you in CWM, which would indicate an issue with a chain-load. The reason may be due to a missing or corrupt IMG file. Otherwise you should be able to determine why by checking /tmp/bootmenu.log against the attached source code.
---
I hope this project will be of help to others!
An additional support forum that everyone should be able to post at is available: http://forum.xda-developers.com/showthread.php?t=2450711.
Wow, really great. Thanks a lot for your effort
Gesendet von meinem One X+ mit Tapatalk
nchantmnt said:
Wow, really great. Thanks a lot for your effort
Click to expand...
Click to collapse
My pleasure, nchantmnt. Hope your new Ouya is helping you feel at home!
Yes im happy it already arrived, but after a second miscarriage and lots of stress because of a lawsuit with our neighbour i didn't have time nor nerves to play or code. Seriously this year sucks
Gesendet von meinem One X+ mit Tapatalk
nchantmnt said:
Yes im happy it already arrived, but after a second miscarriage and lots of stress because of a lawsuit with our neighbour i didn't have time nor nerves to play or code. Seriously this year sucks
Click to expand...
Click to collapse
Gosh, I'm very sorry to hear that. Do think ahead to the upcoming holiday season, and may it be a time to reflect and anticipate a fruitful 2014.
@Hal9k+1 - THANK YOU!
I was so nervous flashing CWM and StockPlus as there is no real way to fix things if something goes wrong. This should give people more confidence when flashing their Ouya.
I understand the process using ADB...my question is: can this be used from CWM somehow?
PS. I assume new kernel will always be flashable from CWM, the hack does not require 561 specifically.
Ipse_Tase said:
I understand the process using ADB...my question is: can this be used from CWM somehow?
Click to expand...
Click to collapse
Hi Ipse_Tase - I do hope the feature will be helpful to you and others.
As I think about your question, I suppose I could have have created a ZIP that would have been installed by CWM. Similarly I could have worked through some form of installation shell script. But for an important operation such as flashing, I prefer the one-at-a-time approach of the interactive shell.
Note that CWM does have an ADB service running with it. Your Ouya would show up as a different device while in CWM, so you'd need to enter Device Manager (Windows) and point the unknown device to the same ADB driver as used for the main ROM.
Alternatively you could skip ADB for this Ouya Boot Menu installation and set up an SSH server on your main ROM. I personally have installed "SSH Server" (Ice Cold Apps). I recall two screens to set up (does require the trackpad in cases), where I enabled automatic start on both, and also set the port number to 2222. After an Ouya reboot I had SSH/SCP capability and could use PuTTY/pscp from Windows.
Hal9k+1...fast reply, thank you.
Just to put my ever-so-senile brain at ease: so I run StockPlus 519r1, and WHILE in the ROM, I start ADB and follow your instructions .
OR...I enter CWM, make sure I get the right ADB drivers installed for THAT instance and go from there.
For a developer, I'm sure it's easier and more familiar to run ADB commands - for people like me (5%-over-the average-user) a CVM option to flash a zip and do all this would be more in-line with the abilities to hack.
I have rooted 4-5 devices so far and the only time I type any ADB commands is at root/unlock time - sometimes not even then (Nexus 4 and the Root Toolkit).
So if you ever consider creating a recovery flashable file, it would help many. Probably not me, as by then I would have done the ADB trick
Sounds like great work! I was hoping to implement something like this myself, but I haven't made any more time for OUYA-related development in a while (due to positive life events/busyness)
I will definitely take a look at your work when I have time!
~Troop
Ipse_Tase said:
Hal9k+1...fast reply, thank you.
Just to put my ever-so-senile brain at ease: so I run StockPlus 519r1, and WHILE in the ROM, I start ADB and follow your instructions .
OR...I enter CWM, make sure I get the right ADB drivers installed for THAT instance and go from there.
Click to expand...
Click to collapse
You got it! You don't need to worry about booting to the other partition prior to flashing. That is a given partition (LNX/SOS) is no longer being accessed once the image is booted. For CWM's ADB, you'd simply point Windows to the same INF file that you originally used. Hope this helps.
StockPlus Installation
Well, I finally retired this old stock 393 ROM I was on, and moved to StockPlus 519r2. I was not able to install it the normal way given my Boot image is in place here. So I ended up modifying "updater-script" under META-INF/com/google/android, and then repackaged prior to running the install procedure. I'm attaching my changed version in case it helps anyone, and please note that it makes StockPlus the main image (kernel.img).
(You'll need to right-click to save the attachment. Once done it will need to be renamed such that it does not include the ".txt" suffix.)
The Windows "7-Zip" utility is helpful for packaging. You may start by right-clicking the downloaded ZIP, then 7-Zip --> Extract to "OUYA_[...]". Enter the newly created directory, get to the updater-script, and replace it with mine. Now back up to the area with META-INF, system, and boot.img, still in the new directory. Select all three under Windows (Ctrl+Click), right click that area, and then 7-Zip --> Add to "OUYA_[...].zip". Be sure this new ZIP is the one that makes it to the Ouya.
Still haven't tried this out yet, but I hope to soon.
I missed out on news over the holidays though and just noticed this:
Announcing Ubuntu and Android dual boot developer preview
http://developer.ubuntu.com/2013/12/announcing-ubuntu-and-android-dual-boot-developer-preview/
I'm curious of their dual boot implementation and how it compares and if we can synergize with their approach, but haven't looked into the details of how theirs works yet (its sounds like it uses a custom recovery image, and they have the ability to trigger it to reboot into Ubuntu from an Android app and vice versa, which is cool)
It'd be awesome to be able to multi-boot an Ouya ROM, an Android ROM (CyanogenMod), and Ubuntu with that kind of ease.
EDIT: This may be more our speed though: (MultiROM)
http://forum.xda-developers.com/showthread.php?t=2011403
(did you pull anything from there? Sounds like they have a modified TWRP that can flash zips to the other ROM slots, which is something I was also hoping to implement)
~Troop
Thanks, Trooper. Good to see Ubuntu moving further along in the mobile world.
I briefly looked at MultiROM since it originated from the KExec-HardBoot work, but decided not to go in that direction. The main reason is that I decided not to pursue the setup/learning of an Android build environment, but also because it wasn't clear how I'd deal with our lack of a touchscreen and lack of volume up/down buttons. I ended up creating a small application that fits within Ouya's CWM framework and starts up before CWM itself; it monitors the power button for click events and writes to the framebuffer memory region using regular Linux calls.
I'm not too concerned about the dual-boot aspect of this new Ubuntu, but the lack of touchscreen could be a hindrance if mouse/keyboard were not a viable substitute. Whether this Ubuntu is designed to work from external storage is another question, since our /system and /data would be occupied by Android. But in general I think we could boot it from my framework, and if my Boot image were selected over the Recovery one, then the Ubuntu kernel could reside in Recovery and also be bootable from the Android side with the "reboot recovery" command.
Best of luck, and hope you'll have a chance to try it all!
accidental post please delete