Database Users

Help with executing commands in adb; stuck at ".../bin/sh...No such file..." error

Help with executing commands in adb; stuck at ".../bin/sh...No such file..." error
I am out of all tricks now for reviving my Note which boots into download and recovery mode. I conclude that from what I have experienced, that factoryfs is the partition which fails to take any write commands when I odin a ROM, as it gets stuck at the factoryfs message. I have tried all the flashing of kernels and ROMs with no luck.
Working with adb seems to be the only option, to configure the partitions on my device manually. The big issue is that I am not able to execute "adb shell" command using Forest1971's guide.
So far, I have had no luck going beyond the "exec -/system/bin/sh...:No such file or directory...(2)" error message, when I type the "adb shell" command.
Can someone with the know-how of how to work through adb help with this? This is my last effort of trying to recover my Note, and if it fails, I will have no choice but to sent the device out of the US. I dread sending my phone out of the country for repairs, as I don't know just how long it will be before it gets fixed and is shipped back to me.
Please do not suggest any flash options, because as I said, I have tried all there is to do with flashing - nothing has helped.

First see if you have a /system filesystem. Looks to me that it doesn't exist. See if you can type
Code:
$ cd /system
or
Code:
$ cd /system/bin
If it complains then there's your problem - you don't have a functioning /system. Maybe type mount and show your filesystems.
I know you asked for no flash suggestions, but have you tried making the device do a hard reset - when powered off hold down home, volume up while holding down power on then release power button when screen shows life. May be worth a shot, but looking like another ICS firmware/emmc issue from here... good luck.
[edit]
should have read your post more closely. Looks like you have no /system/bin/sh at all so can't fire up a shell, so you can ignore my initial suggestion.

paulshields said:
First see if you have a /system filesystem. Looks to me that it doesn't exist. See if you can type
Code:
$ cd /system
or
Code:
$ cd /system/bin
If it complains then there's your problem - you don't have a functioning /system. Maybe type mount and show your filesystems.
I know you asked for no flash suggestions, but have you tried making the device do a hard reset - when powered off hold down home, volume up while holding down power on then release power button when screen shows life. May be worth a shot, but looking like another ICS firmware/emmc issue from here... good luck.
[edit]
should have read your post more closely. Looks like you have no /system/bin/sh at all so can't fire up a shell, so you can ignore my initial suggestion.
Click to expand...
Click to collapse
Suggestion ignored. Any more?

Get an iPhone?

Look at this thread
http://forum.xda-developers.com/showthread.php?p=26279833
Sent from my GT-N7000 using Tapatalk

paulshields said:
Get an iPhone?
Click to expand...
Click to collapse
I won't go the route of laughing and mocking you for saying that. I do think it's a very well put together device, but it just doesn't serve my needs of a big screen, the ability to be free...etc. By the way, you asked me to ignore your suggestion, so I did - FYI.
zviki said:
Look at this thread
http://forum.xda-developers.com/showthread.php?p=26279833
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
I was in that thread, and the suggestions didn't help as it is too complex a process. I was hoping to pick up from scratch, so I created this thread.

incisivekeith said:
I won't go the route of laughing and mocking you for saying that. I do think it's a very well put together device, but it just doesn't serve my needs of a big screen, the ability to be free...etc. By the way, you asked me to ignore your suggestion, so I did - FYI.
I was in that thread, and the suggestions didn't help as it is too complex a process. I was hoping to pick up from scratch, so I created this thread.
Click to expand...
Click to collapse
Hi, please take a look to my post. http://forum.xda-developers.com/showthread.php?p=26350317#post26350317
Just flash that kernel from cmw, and you should be able to run commands on adb shell.

matiasg85 said:
Hi, please take a look to my post. http://forum.xda-developers.com/showthread.php?p=26350317#post26350317
Just flash that kernel from cmw, and you should be able to run commands on adb shell.
Click to expand...
Click to collapse
Thanks for the kernel, but it seems you didn't have much luck solving the issue, even after doing everything in adb correctly. Is that the case?

incisivekeith said:
Thanks for the kernel, but it seems you didn't have much luck solving the issue, even after doing everything in adb correctly. Is that the case?
Click to expand...
Click to collapse
Yes, unfortunatelly i did everything as stated on adb, but had no luck. If ssc don't replace it, i will try using the memory blocks used by the "internal sd card".
You must try it anyway, there were some users that succesfully unbricked the phone.

Did anyone try this mk2efs command with -c option ON ??
Sorry Incesivekeith
I was out of connection for past 2 days.
We have to pull Mr Forest1971 for doing this.
Let me sum up :
parted is not able to solve your issue.
mk2efs is another formating tool that comes with CWM
You are stuck up in executing commands.
Now the idea of flashing the cwm kernel is fine. Did u try that ??
Mr Forest1971 :
Did you see Dr Sumralls comments for this bug.
''He says that we have to go for a full wipe. I have a tool but I dont know I couldnt share it.''

incisivekeith said:
I won't go the route of laughing and mocking you for saying that. I do think it's a very well put together device, but it just doesn't serve my needs of a big screen, the ability to be free...etc. By the way, you asked me to ignore your suggestion, so I did - FYI.
Click to expand...
Click to collapse
I asked you to ignore the initial suggestion as you've obviously not got any functioning recovery. You've not provided much info about how you got to this position, but in my similar situation I got out of it by successfully flashing a FULL WIPE factoryfs (LA4 in my case) and doing the factory reset as I mentioned in my first response. I lost a few GB of my eMMC storage but got a working device. May not help you, but may be useful info for others. Share and share alike. Good luck dude .

UK Nook Glowlight software 1.2.0 - Don't use glownooter

I got a uk glow worm on the 27th (2 days before release ) and one of the first things that I tried to do was to root with glownooter. Bad idea! I thought that I had bricked my device. I had to use a lot of trickery to recover from a loading screen lock-up and once I did the first thing that I did was backup my nook (Which i should have done before).
UPDATE!
Please try my new ROOT install pack HERE:
http://forum.xda-developers.com/showthread.php?p=34216660#post34216660
This can be used to root and install the most requested things of this thread in just one zip.
Here is a quick guide to most things you will need to do to get started. I will update this guide as I discover and build new modifications.
To Backup and Restore
Follow this guide. Please do this BEFORE any other tinkering!
http://blog.the-ebook-reader.com/20...-and-restore-nook-glow-and-nook-simple-touch/
Its important to check your backup before proceeding! Please listen to roustabout and dont skip this step... He knows what he's talking about
roustabout said:
I'd like to suggest an addition to the backup method that many folks are using - always test your restore, but dont test it (the first time) on your device.
Your backup file should be about 2 gig.
find a 2 gig or larger flash drive or sdcard and restore your backup image to that drive.
when you're done, there should be 8 partitions, as there were on your Nook to begin with.
If you can't get that working - you're not ready to root yet. Until you're sure you can restore, don't start making changes, please.
People turn up all the time having screwed themselves over by restoring a partial backup and not knowing it, or having restored only one partition from a complete backup and having blown out the partition table.
Click to expand...
Click to collapse
Thanks roustabout
To Root!
Make sure you use the CWM file suitable for your SD Card. I used "2gb_clockwork-rc2" because my card was 2gb+.
http://forum.xda-developers.com/showthread.php?t=1360994 (Thanks mali100)
Use WinImage with admin rights to restore CWM virtual hdd image to your SD.
Download tinynoot-1-of-2 and tinynoot-2-of-2
http://forum.xda-developers.com/showthread.php?t=1650593 (Thanks to eded333 and roustabout)
Put on CWM boot SD.
Install them in CWM back to back (I didn't bother with the restart in the middle as it should not make a difference considering the file content). After a restart you should have root access and an android launcher on your 1.2.0 Nook (among other files). If nook fails to boot one of the tinynoot files may have corrupted. Recover, Re-download and Retry!
To Add Apps
Using ADB to install apps is easy. Extract this to your C drive:
http://dl.dropbox.com/u/13673492/ADB + Fastboot + Drivers.zip
Navigate to the folder in a cmd prompt.
Drop your APK into the same folder and on your nook open the "adbwireless" app and enable ADB
That app will tell you what your nooks IP address is.
Then you can:
Code:
adb connect ip.address.of.nook:portnumber
adb install app_of_your_choice.apk
Setup ADB over USB
OK I have taken the liberty of building a quick driver mod to support your nook through USB. It works for me. First you need to have the android SDK if you don't already (sure you do but just in case ).
http://developer.android.com/sdk/index.html
Make sure you tick to install the android USB driver when the SDK is installed.
Browse to extras\google\usb_driver in your SDK folder (wherever you put it) and replace android_winusb.inf with my file:
http://dl.dropbox.com/u/13673492/android_winusb.inf
Next go to C:\Users\your_user_account\.android and replace adb_usb.ini with my file:
http://dl.dropbox.com/u/13673492/adb_usb.ini
In device manager, point google ADB driver to this and hopefully that should get you set up!
To test type
Code:
adb devices
Its working if you get something like this:
Code:
* daemon not running. starting it now on port ____ *
* daemon started successfully *
List of devices attached
[YOUR NOOK] device
And then try
Code:
adb install app_of_your_choice.apk
UPDATE
Install Multitouch Kernel With Overclocking
Install the CWM zip using your clockworkmod SD card
http://forum.xda-developers.com/showthread.php?t=1906507
:good: Thanks to johnjtaylor for discovering that this kernel works works.
Hopefully this more comprehensive guide will get others with this software to start playing around.
If this helps, be polite and say thankyou

Have you setup ADB yet? If you can connect with ADB and get a shell, you can execute a 'df' at the shell prompt to see how much free space is available in each partition. On my NST (no glowlight) apps seem to be installed in /data/app so see how much free space is there. On the NST, this appears to be the same partition that books purchased from B&N are placed in, so if you have a lot of books from B&N, you may have to archive some to install apps. Of course all this is going on the assumption that the NST Glow is similar to the NST in this regard.

David0226 said:
Have you setup ADB yet? If you can connect with ADB and get a shell, you can execute a 'df' at the shell prompt to see how much free space is available in each partition. On my NST (no glowlight) apps seem to be installed in /data/app so see how much free space is there. On the NST, this appears to be the same partition that books purchased from B&N are placed in, so if you have a lot of books from B&N, you may have to archive some to install apps. Of course all this is going on the assumption that the NST Glow is similar to the NST in this regard.
Click to expand...
Click to collapse
Thanks for replying. I'm actually working setting up ADB now. As for books I only just got my nook so all of my titles are epub format on an sd card so i wouldn't think it would be that. As soon as I get ADB set up I will post back my results incase it helps anyone else with this new software version.

Can you look in the documentation that comes with the reader for any reference to 'third party software' or 'GPL software'. They should list where to download / apply for the source code somewhere. Once we can see the source code we can compare it against the existing versions and identify any significant issues.

I set up ADB.
Plenty of space in all partitions including /data for the apps that I want. Managed to install through "adb install some_app_i_want.apk" so problem resides with the amazon app store. Not really an issue for me because I have a specific set of apps that I want and don't need to browse the app store.
I will try to work out what's wrong for others.

staylo said:
Can you look in the documentation that comes with the reader for any reference to 'third party software' or 'GPL software'. They should list where to download / apply for the source code somewhere. Once we can see the source code we can compare it against the existing versions and identify any significant issues.
Click to expand...
Click to collapse
Thanks. I'm looking for it now

No reference to GPL. Only references to third party software are to tell me that my warranty is no longer valid (no surprise there!)
Is there any other place I can find this info thats not the documentation?

loney01843 said:
No reference to GPL. Only references to third party software are to tell me that my warranty is no longer valid (no surprise there!)
Is there any other place I can find this info thats not the documentation?
Click to expand...
Click to collapse
Nothing obvious from the uk.nook.com website. On the US site the 'support' section links to terms of service which contain the links to the open source code (see http://www.barnesandnoble.com/container/nook_lnav.asp?pid=43307 and search for NOOK 1.1.5 OSS Release ), but I can't see an equivalent on the UK site. It's an oversight, but such things happen with a new product launch.
You can email them at [email protected] . The relevant paragraph from the US site is:
1. Notwithstanding anything to the contrary in this Agreement, certain components of the Software are licensed subject to the General Public License Version 2.0, a copy of which is attached as Exhibit A (the "GPL License"). You may not use these components except in compliance with the GPL License. In addition, you may have additional rights with respect to such components under the GPL License, including, without limitation, the right to obtain the source code for such components from us. You may obtain a copy of such source code by contacting us through the contact information provided on the Web Site. We will provide such source code in accordance with the GPL License.
I don't legally have the right to request the source code myself, because I don't own a UK NOOK yet. (Yeah, thinly veiled excuse for laziness!)

staylo said:
Nothing obvious from the uk.nook.com website. On the US site the 'support' section links to terms of service which contain the links to the open source code (see http://www.barnesandnoble.com/container/nook_lnav.asp?pid=43307 and search for NOOK 1.1.5 OSS Release ), but I can't see an equivalent on the UK site. It's an oversight, but such things happen with a new product launch.
You can email them at [email protected] . The relevant paragraph from the US site is:
1. Notwithstanding anything to the contrary in this Agreement, certain components of the Software are licensed subject to the General Public License Version 2.0, a copy of which is attached as Exhibit A (the "GPL License"). You may not use these components except in compliance with the GPL License. In addition, you may have additional rights with respect to such components under the GPL License, including, without limitation, the right to obtain the source code for such components from us. You may obtain a copy of such source code by contacting us through the contact information provided on the Web Site. We will provide such source code in accordance with the GPL License.
I don't legally have the right to request the source code myself, because I don't own a UK NOOK yet. (Yeah, thinly veiled excuse for laziness!)
Click to expand...
Click to collapse
You're obviously not that lazy. Thanks for looking and gathering all of the extra info I need. I'll send B&N an e-mail and see what they say. I wouldn't be surprised if they didn't want to hand it out considering you can use it for an easy root setup and install the amazon and kobo stores which could financially damage their advance into new territories! What are we to do! Can't even subscribe to a newspaper or magazine through the nook store yet!
I'll let you know when / if I get a response

There is a setting in nook touch tools that you need to "arm," to allow software from unknown sources to be installed before the Amazon appstore can install software on a tinynooted device.
The setting is a tickbox, "Allow non-Market apps"
Untick it if it is ticked by default, then re-tick it to get apps to install.

roustabout said:
There is a setting in nook touch tools that you need to "arm," to allow software from unknown sources to be installed before the Amazon appstore can install software on a tinynooted device.
The setting is a tickbox, "Allow non-Market apps"
Untick it if it is ticked by default, then re-tick it to get apps to install.
Click to expand...
Click to collapse
Thanks for the reply but I actually tried that. No joy. However perhaps it is this that is not working and not amazon app store. Im just installing through ADB instead. I wonder if I can enable unknown sources through ADB. Something to look at I guess!

UK tinynoot attempt failing
loney01843 said:
Thanks for the reply but I actually tried that. No joy. However perhaps it is this that is not working and not amazon app store. Im just installing through ADB instead. I wonder if I can enable unknown sources through ADB. Something to look at I guess!
Click to expand...
Click to collapse
I tried using the tinynoot process from roustabout's thread here http://forum.xda-developers.com/showthread.php?t=1650593 and am stuck on the final reboot with a "Your NOOK is starting up..." message. Could you let me know if you used a different tinynoot method/set of files?

smerrett said:
I tried using the tinynoot process from roustabout's thread here http://forum.xda-developers.com/showthread.php?t=1650593 and am stuck on the final reboot with a "Your NOOK is starting up..." message. Could you let me know if you used a different tinynoot method/set of files?
Click to expand...
Click to collapse
Yep thats what I used. You on 1.2.0 and did you back up?
I didn't backup first and to get out of the starting message I used this:
http://forum.xda-developers.com/showthread.php?t=1289233&highlight=restore
Then I made a backup using this:
http://blog.the-ebook-reader.com/20...-and-restore-nook-glow-and-nook-simple-touch/
I hope this helps!

loney01843 said:
Yep thats what I used. You on 1.2.0 and did you back up?
I didn't backup first and to get out of the starting message I used this:
http://forum.xda-developers.com/showthread.php?t=1289233&highlight=restore
Then I made a backup using this:
http://blog.the-ebook-reader.com/20...-and-restore-nook-glow-and-nook-simple-touch/
I hope this helps!
Click to expand...
Click to collapse
Thanks for the tip on screen freeze but the link to the images on that post don't work for me. I am on 1.2 and made a backup before attempting any rooting - have managed to reinstate my original nook so quite pleased with myself.
Is there any point in rooting until someone can find a way of getting apps onto the 1.2 NSTG?

smerrett said:
Thanks for the tip on screen freeze but the link to the images on that post don't work for me. I am on 1.2 and made a backup before attempting any rooting - have managed to reinstate my original nook so quite pleased with myself.
Is there any point in rooting until someone can find a way of getting apps onto the 1.2 NSTG?
Click to expand...
Click to collapse
Great that you got a backup. If you want custom apps you can either wait for a different root kit or push ahead (since you have a safety net).
As I said, it worked for me.
If you don't mind searching for the .apk files you want you can use this:
Code:
adb connect ip.address.of.nook:portnumber
adb install app_of_your_choice.apk
This has worked fine for me so far. Just don't try for custom kernels yet as they seem to give me troubles.
I will work more on this tomorrow including adjusting framework for gapps.

loney01843 said:
Great that you got a backup. If you want custom apps you can either wait for a different root kit or push ahead (since you have a safety net).
As I said, it worked for me.
If you don't mind searching for the .apk files you want you can use this:
Code:
adb connect ip.address.of.nook:portnumber
adb install app_of_your_choice.apk
This has worked fine for me so far. Just don't try for custom kernels yet as they seem to give me troubles.
I will work more on this tomorrow including adjusting framework for gapps.
Click to expand...
Click to collapse
Thanks also for the code but as this is my first foray into rooting I think I'll hang around and watch for a bit! Perhaps if I start learning some more I may feel confident enough to try it.
Do you have copies of the files needed for the factory reset - the links are still not working for me.
Thanks again and sorry for bothering you. Hope tomorrow is productive for you.

smerrett said:
Thanks also for the code but as this is my first foray into rooting I think I'll hang around and watch for a bit! Perhaps if I start learning some more I may feel confident enough to try it.
Do you have copies of the files needed for the factory reset - the links are still not working for me.
Thanks again and sorry for bothering you. Hope tomorrow is productive for you.
Click to expand...
Click to collapse
http://dl.dropbox.com/u/13673492/n2T-Recovery_0.2.img
This is the file needed to force factory reset. However a quality backup like you have is far more important.
For anyone who wants to give this a go, here is a quick guide for root access and app installs using windows tools until I can make something more complete:
Make sure you use the CWM file suitable for your SD Card. I used "2gb_clockwork-rc2" because my card was 2gb+.
http://forum.xda-developers.com/showthread.php?t=1360994
(Thanks mali100)
Use WinImage with admin rights to restore CWM virtual hdd image to your SD.
Download tinynoot-1-of-2 and tinynoot-2-of-2
http://forum.xda-developers.com/showthread.php?t=1650593
(Thanks to eded333 and roustabout)
Put on CWM boot SD.
Install them in CWM back to back (I didn't bother with the restart in the middle as it should not make a difference considering the file content). After a restart you should have root access and an android launcher on your 1.2.0 Nook (among other files). If nook fails to boot one of the tinynoot files may have corrupted. Recover, Re-download and Retry!
Using ADB to install apps is easy. Extract this to your C drive:
http://dl.dropbox.com/u/13673492/ADB + Fastboot + Drivers.zip
Navigate to the folder in a cmd prompt.
Drop your APK into the same folder and on your nook open the "adbwireless" app and enable ADB
That app will tell you what your nooks IP address is.
Then you can:
Code:
adb connect ip.address.of.nook:portnumber
adb install app_of_your_choice.apk
Hopefully this more comprehensive guide will get others with this software to start playing around.
Click thanks if this guides helpful.

loney01843 said:
If nook fails to boot one of the tinynoot files may have corrupted. Recover, Re-download and Retry!
Navigate to the folder in a cmd prompt.
Drop your APK into the same folder and on your nook open the "adbwireless" app and enable ADB
That app will tell you what your nooks IP address is.
Then you can:
Code:
adb connect ip.address.of.nook:portnumber
adb install app_of_your_choice.apk
Hopefully this more comprehensive guide will get others with this software to start playing around.
Click thanks if this guides helpful.
Click to expand...
Click to collapse
Great - thanks to your more detailed instructions, I have persevered and the second attempt at installing the tinynoot zips worked. Your post gave me the confidence to try installing apks for the first time and for anyone else who is unfamiliar with the processes used, I found these two pages useful for:
navigating within a command prompt (how naive): pcstats.com/articleview.cfm?articleid=1723&page=3
Pasting text into a command prompt (ditto): megaleecher.net/Copy_Paste_Text_Dos_Window
Sorry, as a newb I'm not trusted to post outside links yet. It took a couple of attempts of pasting and pressing enter to work out how to install using the adb code but it's not as hard as I expected.
I have tried installing the 1 Mobile Market which works but it is unable to install apps itself (not enough space).
Also, I have just installed NoRefreshToggle and can't seem to get it to work. Any thoughts - is 1.2 to blame? Really want this to work as Business Calendar Free is just a series of blinks at the moment!

Great! I'm glad you pushed onward and have root.
I am going through possibilities of other ways to install apps and mods.
No refresh is something that I would like as well but I think that the framework may need editing for 1.2.0. For fast mode a new kernel will need to be made or existing one modified.
Be aware that installing kernels not designed for this firmware can give you some serious problems.
Once I can setup app markets, I will work on these other modifications.
Stay tuned :good:

Take a look at the overclock kernel - it's got a lot of the norefresh features baked in, and gives you a nice ability to control both clock and kernel tuning (via the governor control.)
You're right, you can flash the two zips back to back with no ill effect, I was mistaken about what the second zip was doing.
I mistyped when I typed "nook touch tools," I meant nook color tools.
I'm very interested that the amazon store is not working in 1.2. I will see if the software's available for my device, so I can try to see what's happened.
As of now, the us bn site does not mention an os 1.2 for the glowlight.

[SUPPORT] Ouya Boot Menu Support Thread

Hello everyone,
This thread previously was a discussion area for the Ouya Boot Menu feature during its early development.
It's now being transitioned to a support area. The new project description/download page is at:
http://forum.xda-developers.com/showthread.php?t=2499673.
Thanks!

CWM Bootloop
Hal9k+1 said:
Hello everyone, attached is the ZIP of an updated CWM Recovery IMG file.
This image is based on the latest stock Ouya kernel in GitHub. The kernel contains some newer HDMI code, which will hopefully increase the chance of getting the CWM graphics showing up properly. I also turned off HDMI’s HDCP in the compile (not needed for a utility partition such as this), and grabbed a patch from Kulve’s Ouya kernel fork to really ensure HDCP bypass.
More importantly, the image contains Tasssadar’s excellent work involving KExec-HardBoot. This technology should allow for the implementation of a “fastboot boot”-related capability from a running ROM, enabling kernel chain loading. The recovery image in particular will be a place to practice with KExec-HardBoot, and come up with a booting method that could eventually be flashed to the boot/kernel partition.
It is fine (and recommended) to fastboot to this image as a quick verification of things. However, it will be necessary to flash to the Recovery (“SOS”) partition for proper testing of KExec-HardBoot, since there’s an embedded reboot (to Recovery in this case) in there. Do *NOT* flash this to the Boot.
A simple chain load test can be done by extracting “zImage” from this image, and “initramfs.cpio.gz” from your current ROM kernel. (Included is “unmkbootimg” that can help here - runs on Linux.) Push these to /tmp on the Ouya while it is running this image. Then enter the Ouya shell and do:
kexec --load-hardboot zImage --initrd initramfs.cpio.gz --mem-min=0xA0000000 --command-line=”$(cat /proc/cmdline)”
kexec -e
It should come up with this new kernel under your current ROM’s environment. As verification, you should see kexec files under /sys/kernel.
I’m looking to implement a basic chain loading application. It would come up before the Recovery and ADB services, and do the following:
% Pause for a bit, to allow any Alt-SysRq keyboard action (jump to Recovery or Bootloader) that may be needed.
% Check for any attached USB mass-storage devices (e.g., thumb drive), and look for the file “kernel.img”. Pull it in and boot it if present.
% If that failed, then look to “/system/kernel.img” on the Ouya itself, and boot it.
% And if that didn’t pan out, then exit and allow Recovery/ADB services to come up.
I hope all of this will be of help to others along the way!
Click to expand...
Click to collapse
Will this help with the problem I have?..
New update today it downloads automatically and then reboot to CWM and it fail verification...reboot system and it does all over again?...Any ideas Plz

View2Askew said:
Will this help with the problem I have?..
New update today it downloads automatically and then reboot to CWM and it fail verification...reboot system and it does all over again?...Any ideas Plz
Click to expand...
Click to collapse
Sorry, I'm not sure I understand. It sounds like the new stock firmware update is failing to go in, perhaps because of consistent download corruption. Whether you're actually being dropped in to the recovery partition is unclear. You might try the download again with the other networking type (Ethernet vs WiFi). You might also just disconnect from the network for the time being, and see if you remain in the firmware without interruption. From there you can consider setting up ADB to see if you can administer the Ouya from a PC.
My post is more for the developers at heart, just in case my investigation piqued anyone's interest. Ideally the post would go in the Development section, but I evidently need a few more posts here to unlock that area.
Best of luck!

Dual booting
Yes, please do enable dual/multi booting
Is there something I can do to help in that regard?

kulve said:
Yes, please do enable dual/multi booting
Is there something I can do to help in that regard?
Click to expand...
Click to collapse
Thanks kulve, and thank you for the kernel patch set. I need to get familiar with the offerings there.
I don't see any blockages in my plan so far; I just need to start in and see what comes up. At least it's a better feeling than the dead-ends encountered with the U-Boot and regular KExec investigations.
Someone more enterprising could possibly port in the MultiROM project, but I'll stick with this. Will let you know if I get stuck.

My findings so far...
- I've finally decided that shutting off HDCP in the build does nothing to help avoid the funky pink/purple squeezed screen that sometimes appears when CWM comes up. With my Asus monitor, I see the issue when the monitor was in sleep mode. Likewise, if I can switch the monitor to HDMI input at the same time as starting Recovery, then it's fine. It may be possible to hack in a fix by somehow starting and closing an HDMI session shortly before CWM itself starts. (I don't want to fight this too hard but would be nice to resolve.)
- I see how to pull the kernel and ramdisk out of an Android image (on the Ouya itself), so that they could be passed to KExec-HardBoot. I've done it with a script as a test but it may end up in an executable.
- I tried out a USB thumb drive. It's detected but no block device is made available under /dev -- I've finally decided that support is likely in a kernel module, which does not exist on the Recovery image. I'm probably not going to sweat this due to the next item.
- I notice that the CWM application can read the Ouya power button as something comparable to a keyboard key press. Borrowing this capability may allow us to count the button presses in a limited time range, and thus boot an appropriate image. (Would be easier than dealing with the pairing of the controller, but at least still wouldn't require a keyboard.) With this line of thought, I'm thinking the main image could sit in /system while any alternates could be in /sdcard or /data.
So in general, studying the code of the CWM application appears to be the next direction. Thanks - feel free to send any ideas.

Hal9k+1 said:
- I've finally decided that shutting off HDCP in the build does nothing to help avoid the funky pink/purple squeezed screen that sometimes appears when CWM comes up. With my Asus monitor, I see the issue when the monitor was in sleep mode. Likewise, if I can switch the monitor to HDMI input at the same time as starting Recovery, then it's fine. It may be possible to hack in a fix by somehow starting and closing an HDMI session shortly before CWM itself starts. (I don't want to fight this too hard but would be nice to resolve.)
Click to expand...
Click to collapse
What does the rendering in CWM? Is it Android or something lower level? I think my kernel has better HDMI support but for that the software needs to use that explicitly instead of the default one as there is not internal LCD panel (/dev/graphics/fb0 vs. fb1).

kulve said:
What does the rendering in CWM? Is it Android or something lower level? I think my kernel has better HDMI support but for that the software needs to use that explicitly instead of the default one as there is not internal LCD panel (/dev/graphics/fb0 vs. fb1).
Click to expand...
Click to collapse
It does look to be low-level, as CWM directly opens /dev/graphics/fb0 and uses ioctl() on it. I've decided to try my own compile of CWM as it does look to be a nice base for the booting effort. Will definitely look to your patches for the improved HDMI when I'm all ready -- thanks!

Hal9k+1 said:
It does look to be low-level, as CWM directly opens /dev/graphics/fb0 and uses ioctl() on it. I've decided to try my own compile of CWM as it does look to be a nice base for the booting effort. Will definitely look to your patches for the improved HDMI when I'm all ready -- thanks!
Click to expand...
Click to collapse
I noticed your comments related to this on the "Ouya CWM Recovery" thread but I'm not allowed to post there, so I'll post here.
Or actually repost as I'm mostly repeating myself. I had all kinds of issues in getting output using /dev/graphics/fb0 in Linux with the stock Ouya kernel but after some fixes the fb1 seems to work quite reliable. I get the output even if I don't have HDMI plugged in during the boot and it chooses the right resolution both for my TV (1080p) and for my monitor (1680x1050).

To all: I have updated the attachment that's present on the first post. I've synced to the latest Ouya kernel and pulled in the next HDMI patch set from Kulve. My HDMI issue now appears to be fully resolved.
Kulve: Thanks so much for refocusing me! I should have grabbed the patch from day 1, but that summary description had me a bit spooked. Note that I kept the HDMI/PRIMARY symbol enabled, so there's still only the fb0 device on this kernel.
With this handled and due to my thinking in general, I'm going to back away from trying to compile CWM itself -- I don't want to invest in CM10.1's environment at this time. Instead I will borrow CWM's UI and input technology to build an independent front-end with this Ubuntu/glibc environment I have working. My idea is to release another Recovery image when that's ready so we'll have a chance to practice/debug before moving to the Boot image.

Hal9k+1 said:
Kulve: Thanks so much for refocusing me! I should have grabbed the patch from day 1, but that summary description had me a bit spooked. Note that I kept the HDMI/PRIMARY symbol enabled, so there's still only the fb0 device on this kernel.
Click to expand...
Click to collapse
Hit the Thanks button
Anyway, do you have your kernel source code somewhere? Being able to use multiple resolutions on HDMI while keeping it as primary might be something that many Ouya Android gamers want as they might be able to play at 720p then.

ooo nice, ill try it out and see what happens

kulve said:
Hit the Thanks button
Anyway, do you have your kernel source code somewhere? Being able to use multiple resolutions on HDMI while keeping it as primary might be something that many Ouya Android gamers want as they might be able to play at 720p then.
Click to expand...
Click to collapse
Done! :laugh:
My modified files were tarred up and placed in the ZIP; let me know of any possible issue. I'm not planning on a GIT account, but anyone may feel free to pull anything back to their project. Also I understand that sticking with HDMI/PRIMARY may reduce some of the capability/flexibility you're seeing, but I wanted to stay honored to the Android/CM layout expectation if possible.

Hal9k+1 said:
Done! :laugh:
My modified files were tarred up and placed in the ZIP; let me know of any possible issue. I'm not planning on a GIT account, but anyone may feel free to pull anything back to their project. Also I understand that sticking with HDMI/PRIMARY may reduce some of the capability/flexibility you're seeing, but I wanted to stay honored to the Android/CM layout expectation if possible.
Click to expand...
Click to collapse
Any chance of getting some concise installation instructions?

zondajag said:
Any chance of getting some concise installation instructions?
Click to expand...
Click to collapse
Here's a quick executive summary until I can update the 1st post.
I'm reminded there's another XDA project (Ouya Safe Recovery) with a very similar goal as this, and works by reversing the Boot and Recovery concepts. However it's completely incompatible with us, and those users should not be doing any flashing -- at least not until we have a Boot image ready.
First step is to get rcvy092613.img to the Ouya in its /tmp directory. This may be done with an "adb push rcvy092613.img /tmp" command, or can by done through Secure Copy if an appropriate SSH server is set up.
Next step is to access the Ouya shell, either running from the main ROM or from a Recovery ROM. Be sure to become root (ensure "#" in the prompt) as needed.
Run the following to back up the old image:
cd /dev/block/platform/sdhci-tegra.3/by-name/
dd if=SOS of=/sdcard/old_rcvy.img
Make sure the new image is correct - should see "2a882d1ba8c2d543503cacb49ab0d397":
md5sum /tmp/rcvy092613.img
On to flashing Recovery:
dd if=/tmp/rcvy092613.img of=SOS
Now wait at least a full minute in case there is any internal flushing still taking place. And to finish up:
sync
reboot recovery

Aye....never enough time to tinker it seems, especially with getting over this flu.
At this point I have my own compiled code splitting the boot image file, as well as counting the power button clicks.
I want to see if I can make a welcome/instruction screen, probably by getting CWM's minui down to its core essence. From there it will hopefully just be normal integration work to achieve a new Recovery for testing.

Everyone, a new boot menu is ready for testing. Please read through the first post to see if you'd like to try it out. Apologies once again for the delay in getting this ready.

Hal9k+1 said:
Everyone, a new boot menu is ready for testing. Please read through the first post to see if you'd like to try it out. Apologies once again for the delay in getting this ready.
Click to expand...
Click to collapse
Did I read correctly that the image support multibooting?

kulve said:
Did I read correctly that the image support multibooting?
Click to expand...
Click to collapse
Hi again Kulve. It supports three Android boot images - the main + two alternates: kernel.img, kernelA1.img, & kernelA2.img. It prefers to see the selected image in /sdcard, but will shift to /system as needed.
So, it is multi-booting, but you should keep in mind that there is still only the single /system partition. So installing two normal ROMs together probably won't work out, due to that common storage area. However, one of the ROMs could be based out of /system, while any others could use some form of external/networked storage. Note that the Android image format contains both the kernel and the initial ramdisk, so I feel that a multi-boot arrangement could be done.

Hal9k+1 said:
Hi again Kulve. It supports three Android boot images - the main + two alternates: kernel.img, kernelA1.img, & kernelA2.img. It prefers to see the selected image in /sdcard, but will shift to /system as needed.
So, it is multi-booting, but you should keep in mind that there is still only the single /system partition. So installing two normal ROMs together probably won't work out, due to that common storage area. However, one of the ROMs could be based out of /system, while any others could use some form of external/networked storage. Note that the Android image format contains both the kernel and the initial ramdisk, so I feel that a multi-boot arrangement could be done.
Click to expand...
Click to collapse
My kernel is hard coded to mount the Debian (or whatever) rootfs from /dev/sdaX so Ouya's internal partitioning doesn't matter. It would be really cool to be able to put kernelA1.im to /sdcard, an USB flash drive to the USB port and boot to Debian without tinkering with adb/fastboot/etc. on a PC.
I'm not currently using any initrd-images but adding something simple should be straightforward.

[Q] U8800 bricked, update fails...

Hey guys,
I'm experiencing some serious case of bricking here. It is most probably caused of accidentally installing wrong .zip file that is actually not for u8800. When i try to go into recovery or regularly boot it up, i see the infamous green screen with blue and red blocks. My only possible interaction with phone could be done by pink screen cuz i think it's working.
Anyway, most of forums i've been on states getting the original image folder and putting the official Android 2.3.5 UPDATE.app to dload folder in my sd card, then booting up or going into download mode (which both do the same thing, starts the update process) without the battery attached and the phone connected to the pc via an USB cable. The only problem is whenever i try this, the update stucks on around 30% of the bar and when this happens, the red light switches on and off more frequently than before indicating there was something wrong with the process.
Am i doing something wrong here? What do you guys have else to offer? There is almost no forum left in xda, modaco and androidhelp that i didn't check out. I'm going to start throwing up threads here. Please help me!

If you can enter pink screen, you can try fullflash :http://forum.xda-developers.com/showthread.php?t=1971266

Ax1qwer said:
If you can enter pink screen, you can try fullflash :http://forum.xda-developers.com/showthread.php?t=1971266
Click to expand...
Click to collapse
I've already come across with these threads before, pointing out the only solution is via linux terminal but currently i have no access to any OS other than Windows. Is there any other way without installing Ubuntu?

dalpus said:
I've already come across with these threads before, pointing out the only solution is via linux terminal but currently i have no access to any OS other than Windows. Is there any other way without installing Ubuntu?
Click to expand...
Click to collapse
You can use linux live CD/DVD. No installation, only boot system from CD/DVD.

Ax1qwer said:
You can use linux live CD/DVD. No installation, only boot system from CD/DVD.
Click to expand...
Click to collapse
I decided to do it using Virtualbox but i had some problems specifying the directory of the .bin file (It's on desktop)
Here is the example command given:
[email protected] ~ $ sudo dd if=/media/Data/u8800/HUAWEI_U8800_FullFlash.bin of=/dev/sdc
My command:
[email protected] ~ $ sudo dd if=/home/myusername/Desktop/HUAWEI_U8800_FullFlash.bin
Am i coding wrong, incomplete or it cannot simply be done in Virtualbox?

dalpus said:
I decided to do it using Virtualbox but i had some problems specifying the directory of the .bin file (It's on desktop)
Here is the example command given:
[email protected] ~ $ sudo dd if=/media/Data/u8800/HUAWEI_U8800_FullFlash.bin of=/dev/sdc
My command:
[email protected] ~ $ sudo dd if=/home/myusername/Desktop/HUAWEI_U8800_FullFlash.bin
Am i coding wrong, incomplete or it cannot simply be done in Virtualbox?
Click to expand...
Click to collapse
Just follow the tutorial.
you must type "of=/dev/device_name" in command
with "device_name" is the device name alocated to the U8800. It can be "sdb", "sdc", "sdd", "sde", etc.

Ax1qwer said:
Just follow the tutorial.
you must type "of=/dev/device_name" in command
with "device_name" is the device name alocated to the U8800. It can be "sdb", "sdc", "sdd", "sde", etc.
Click to expand...
Click to collapse
Hey sorry for resurrecting this thread. It's just that i previously tried everything including linux terminal but it just didn't do it and i brought it to its maintenance service for repairs. You can close this thread now, nothing to discuss here. But before that, could you give me some ROM suggestions to install to my newly working phone. I'd appreciate if you specify the reasons to use them too. You can send it via personal message. Thank you in advance.

dalpus said:
Hey sorry for resurrecting this thread. It's just that i previously tried everything including linux terminal but it just didn't do it and i brought it to its maintenance service for repairs. You can close this thread now, nothing to discuss here. But before that, could you give me some ROM suggestions to install to my newly working phone. I'd appreciate if you specify the reasons to use them too. You can send it via personal message. Thank you in advance.
Click to expand...
Click to collapse
Hi, Now I am using AuroraSP + , very fast, stable and smooth, http://forum.xda-developers.com/showthread.php?t=2295318 very good for daily use.
MIUI V4 is good ROM too, I am going to test it this weekend and use it as my daily ROM http://forum.xda-developers.com/showthread.php?t=2029969
If you like JB, you can try coldblue_´s CM 10.1 http://forum.xda-developers.com/showthread.php?t=2337235 , but the ROM isn´t perfect.

Ax1qwer said:
Hi, Now I am using AuroraSP + , very fast, stable and smooth, http://forum.xda-developers.com/showthread.php?t=2295318 very good for daily use.
MIUI V4 is good ROM too, I am going to test it this weekend and use it as my daily ROM http://forum.xda-developers.com/showthread.php?t=2029969
If you like JB, you can try coldblue_´s CM 10.1 http://forum.xda-developers.com/showthread.php?t=2337235 , but the ROM isn´t perfect.
Click to expand...
Click to collapse
Hello again, did you have time to try out MIUI? What are your impressions?
I am finally in possession of my phone once again since the last time i received my phone back from its technical service, dumbass engineers nulled my IMEI after they fixed bricked ROM problem. After i got it back, i thought i could fix IMEI problem if i switch ROMs and installed AuroraSP+. It was decent but didn't really had time to fully explore it as i immidiately sent it back. And now they installed Android 2.3 firmware again, bah...

dalpus said:
Hello again, did you have time to try out MIUI? What are your impressions?
I am finally in possession of my phone once again since the last time i received my phone back from its technical service, dumbass engineers nulled my IMEI after they fixed bricked ROM problem. After i got it back, i thought i could fix IMEI problem if i switch ROMs and installed AuroraSP+. It was decent but didn't really had time to fully explore it as i immidiately sent it back. And now they installed Android 2.3 firmware again, bah...
Click to expand...
Click to collapse
Hi, my small review is on last page
http://forum.xda-developers.com/showthread.php?t=2029969&page=17

[Guide] Building AOSP & Adding Features

First off I'd like to apologize if this is in the wrong place or if it is perceived as advertising, I simply want to contribute to the dev community and this site, and in particular the Nexus 9 forum that has been the centre of my learning as I took up the hobby of AOSP.
I have been back and forth with AOSP, I've contributed a little bit here and there on the Android development forums but would like to properly document how to build AOSP and more importantly (because it is even less well documented) how to add features, change existing features and generally customize the operating system to your liking. I am by no means an expert but I feel I have enough knowledge that I can share it with others who may be in the position I was a number of months ago. I always found it very difficult to find a centralized location for the information I needed.
To this end I have started a site to do just that. I am using a Nexus 9 for my AOSP development but most (if not all) of the tutorials and information should be applicable to basically any AOSP/Nexus device. I have started things off by creating a tutorial on how to build AOSP from 'scratch' so to speak and a tutorial on how to add items to the power menu such as 'reboot', 'airplane mode' etc.
If anybody would like certain topics covered or just have any feedback or comments please reply here or leave them on the articles themselves. I'll do my best to accommodate / respond.
The link is: http://littlelostandroid.wordpress.com
From tomorrow the following (nicer) link should also work: www.alittlelostandroid.com
I should also add that the blog will be ongoing about all things android device but this initial series will be about also and implementing features.

wow this is a real good guide/blog u put together please do continue

Dreamlogix said:
wow this is a real good guide/blog u put together please do continue
Click to expand...
Click to collapse
Thanks! The next post should be up in a day or two, its been a busy week.

New post up about flashing the build to a device!
www.alittlelostandroid.com

This is a great website. Lol i'm gonna have to learn to use ubuntu(was gonna do it anyway on my old computer but motherboard died and i got lazy). Can you make this in chronological order? or better add each section to a sitemap? Just a suggestion:cyclops:

whowatchlist said:
This is a great website. Lol i'm gonna have to learn to use ubuntu(was gonna do it anyway on my old computer but motherboard died and i got lazy). Can you make this in chronological order? or better add each section to a sitemap? Just a suggestion:cyclops:
Click to expand...
Click to collapse
So I changed the theme so that you can see the most recent posts on the side and work from that. I'm still getting to grips with WordPress to be honest but hopefully that's better now.

Another post about setting up and storing your code on GIT repos:
https://littlelostandroid.wordpress...-open-source-project-part-4-git-repositories/

Thanks for this
Do you have any insight to share on your site about building the LTE variants at all?

THX for your work !
There are plans to continue this great guide?

scoobydu said:
Thanks for this
Do you have any insight to share on your site about building the LTE variants at all?
Click to expand...
Click to collapse
Sadly I won't be able to do any work around the LTE version as I don't have the hardware to test it on. I don't want to release advice I haven't tested and potentially end up inadvertently damaging someones tablet for example
Topse said:
THX for your work !
There are plans to continue this great guide?
Click to expand...
Click to collapse
Sorry for the late reply, I don't get any emails when someone posts on this thread, I need to subscribe to it. I do plan on doing more, in fact I think I may have some written already, just a matter of getting time to do it. I'll get to work on the next section of the tutorials and post here when it's up. Is there anything in particular you would like covered?

seanashmore said:
Sadly I won't be able to do any work around the LTE version as I don't have the hardware to test it on. I don't want to release advice I haven't tested and potentially end up inadvertently damaging someones tablet for example
Sorry for the late reply, I don't get any emails when someone posts on this thread, I need to subscribe to it. I do plan on doing more, in fact I think I may have some written already, just a matter of getting time to do it. I'll get to work on the next section of the tutorials and post here when it's up. Is there anything in particular you would like covered?
Click to expand...
Click to collapse
I m actually try to make my own little aosp rom.
I have some probs with gapps flashing.
Wrong api level error.
I tried different commits.
With pure nexus gapps it works .I need to flash it twice.
I do "make otapackage", this is different to your guide.
When I flash a custom kernel I don't have this gapps problems.?
Next thing I will integrate is that reboot option.
But with reboot recovery.
Once after flashing I was surprised with stock recovery..
How can I disable that?
At the moment I build only for my bullhead.
But if that recovery and gapps problem is solved.
I will try for my flounder and shamu too.
Actually I use n7 r 15 as source. But will will switch to 7.1*
When it is evaluable.

Topse said:
I m actually try to make my own little aosp rom.
I have some probs with gapps flashing.
Wrong api level error.
I tried different commits.
With pure nexus gapps it works .I need to flash it twice.
I do "make otapackage", this is different to your guide.
When I flash a custom kernel I don't have this gapps problems.?
Next thing I will integrate is that reboot option.
But with reboot recovery.
Once after flashing I was surprised with stock recovery..
How can I disable that?
At the moment I build only for my bullhead.
But if that recovery and gapps problem is solved.
I will try for my flounder and shamu too.
Actually I use n7 r 15 as source. But will will switch to 7.1*
When it is evaluable.
Click to expand...
Click to collapse
I'm not 100% sure about the GAPPS issue, maybe try http://opengapps.org/, it lets you choose your android version, architecture etc.
In terms of the recovery; You'll see in my tutorials that I am using the stock Google factory images as a base. In that image is a recovery.img file; You should be able to replace this file with TWRP or any other custom recovery and flash it as part of your ROM.
Hope this helps.

seanashmore said:
I'm not 100% sure about the GAPPS issue, maybe try http://opengapps.org/, it lets you choose your android version, architecture etc.
In terms of the recovery; You'll see in my tutorials that I am using the stock Google factory images as a base. In that image is a recovery.img file; You should be able to replace this file with TWRP or any other custom recovery and flash it as part of your ROM.
Hope this helps.
Click to expand...
Click to collapse
I tried opengapps. But i run in an error. Opengapps say my ROM has the wrong api level.
I tried this commit (and other like that)
https://github.com/Cardinal-AOSP/frameworks_base/commit/6c8322f3ad221ea2092e82b99ece537b85ec996f
And with pure nexus dynamic gapps . it works when I flash the gapps two times. First I get the error and the second try works.
Change recovery to twrp sounds good. But with more devices its a dangers thing. Cause ever device needs special twrp.
I think there is a way to disable this flashing recovery.
But till now I didn't find it.

Topse said:
I tried opengapps. But i run in an error. Opengapps say my ROM has the wrong api level.
I tried this commit (and other like that)
https://github.com/Cardinal-AOSP/frameworks_base/commit/6c8322f3ad221ea2092e82b99ece537b85ec996f
And with pure nexus dynamic gapps . it works when I flash the gapps two times. First I get the error and the second try works.
Change recovery to twrp sounds good. But with more devices its a dangers thing. Cause ever device needs special twrp.
I think there is a way to disable this flashing recovery.
But till now I didn't find it.
Click to expand...
Click to collapse
If it's just the case of not flashing the recovery img then just remove that line/command from the script. However you will have to assume that the device already has a recovery img (which to be honest is a fairly safe assumption).

[/STRIKE]
seanashmore said:
If it's just the case of not flashing the recovery img then just remove that line/command from the script. However you will have to assume that the device already has a recovery img (which to be honest is a fairly safe assumption).
Click to expand...
Click to collapse
I try this for recovery https://github.com/peteralfonso/platform_build/commit/9b3a020058b84fb1f9cfba600f4a958572a805c3
edit: i think this is to old...

seanashmore said:
I'm not 100% sure about the GAPPS issue, maybe try http://opengapps.org/, it lets you choose your android version, architecture etc.
In terms of the recovery; You'll see in my tutorials that I am using the stock Google factory images as a base. In that image is a recovery.img file; You should be able to replace this file with TWRP or any other custom recovery and flash it as part of your ROM.
Hope this helps.
Click to expand...
Click to collapse
I use this way to build:
cd ~/aosp/kernel/lge/bullhead
make clean
export ARCH=arm64
export CROSS_COMPILE=~/aosp/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-
export USE_CCACHE=1
make bullhead_defconfig
make -j6
cd ~/aosp
mkdir ~/aosp/device/lge/bullhead-kernel
rm ~/aosp/device/lge/bullhead-kernel/Image.gz-dtb
cp ~/aosp/kernel/lge/bullhead/arch/arm64/boot/Image.gz-dtb ~/aosp/device/lge/bullhead-kernel
source build/envsetup.sh
make clobber
lunch aosp_bullhead-userdebug
export USE_CCACHE=1
make -j6 otapackage

Topse said:
I use this way to build:
cd ~/aosp/kernel/lge/bullhead
make clean
export ARCH=arm64
export CROSS_COMPILE=~/aosp/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-
export USE_CCACHE=1
make bullhead_defconfig
make -j6
cd ~/aosp
mkdir ~/aosp/device/lge/bullhead-kernel
rm ~/aosp/device/lge/bullhead-kernel/Image.gz-dtb
cp ~/aosp/kernel/lge/bullhead/arch/arm64/boot/Image.gz-dtb ~/aosp/device/lge/bullhead-kernel
source build/envsetup.sh
make clobber
lunch aosp_bullhead-userdebug
export USE_CCACHE=1
make -j6 otapackage
Click to expand...
Click to collapse
Ah ok, see the way I build gives me separate .img files, and I write a script similar to the flash-all script you get with the factory images. This allows me to pretty easily change what i want to do and what i want to flash or not.

seanashmore said:
Ah ok, see the way I build gives me separate .img files, and I write a script similar to the flash-all script you get with the factory images. This allows me to pretty easily change what i want to do and what i want to flash or not.
Click to expand...
Click to collapse
Year , but zip is easier to use/share.

Topse said:
Year , but zip is easier to use/share.
Click to expand...
Click to collapse
Definitely, though you can always put your script and .img files inside a zip just like the factory images. so users would download your zip, unzip it and run your script. Its all down to personal taste i guess, there are many ways to skin a cat.

seanashmore said:
Definitely, though you can always put your script and .img files inside a zip just like the factory images. so users would download your zip, unzip it and run your script. Its all down to personal taste i guess, there are many ways to skin a cat.
Click to expand...
Click to collapse
:good:
I like it to try different ways.Good for learning and deeper understanding.
For my personal use is this way no problem.
But for sharing with other people is a flashable zip file the most used way.