Database Develop

[ROM]Fission Vanilla 1.2 - DroidX - 1.2.1 - Back Up...

Vanilla FroYo FRF91
For your Droid2 & DroidX
Developed for You by Team DeFuse
Splitting Blur from your Moto Droid.​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
HotFix:
D2 1.2.1 - Download HERE - This will update your build to 1.2.1
DX 1.2.1 - Download full ROM, if coming from Fission 1.1+ you can install right over.
If you are coming from the 1.2.1 test file from IRC then still install this update file since it will remove items that did not make it to final build (Nexus One Livewallpapers that were not working)
Full 1.2.1 ROMs are listed bleow.
Changelog is listed below.
No need to wipe for update file. No need to wipe if AND ONLY IF you are coming from 1.1, 1.2 and upgrading to 1.2.1. You MUST wipe if coming from any other ROM.
D2/DX - HotFix for data still functioning when custom battery manager is used to turn off data during certain times. Download HERE. Install from recovery as any other update. Just mount system, do not wipe and select the zip file for update.
Twitter:
@AngDroid
@Drod2169
Web:
http://www.teamdefuse.com
IRC:
http://www.freenode.net
#teamdefuse
Changelog:
1.2 -> 1.2.1
Cleaned up Add_On folder. Removed items that would not work with this ROM, added Live Wallpaper packages.
Added Network location (AGPS) pop ups. Will pop up when permission is needed. It is working in ROM but the option is not in settings.
Data Manager fix now included. Fixed issue when setting custom battery manager profile but data was still on during off hours.
Few changes to build.prop.
Added transparent status bar pull down curtain.
1.1 -> 1.2
Addressed Superuser issue - Not sure if it is fixed for some users.
DX Build now has FroYo Android Keyboard stock - Install DX Multi-Touch in add_on folder if you prefer.
Addressed USB issue - Not sure if it is fixed for some users.
Added ability to overclock from shell. Open terminal (download from market) and type in proper commands.
Improved boot animation. Now with hi-res graphics.
Updated install script for ROM.
DX Build - Fixed displayed version info in about phone.
Add Ons have been fixed so all zip files should install fine.
More cleaning of code...
Not part of the release but I updated darkonion's one click root method. It is now an EXE file. Will fix all broken root issues, update you to latest version of Superuser and install the APK properly in data/app so any future update from market should not cause problems.
About ROM:
First Vanilla ROM for Droid2, DroidX & Droid2 WE!
First ROM for Droid2, DroidX & Droid2 WE that can be overlocked!
This is not an AOSP ROM but all stock packages are built from source. It is a complete set of vanilla Android applications. All Blur has been removed so it is the closest you will get to a true AOSP clean ROM for the Droid2/X/WE/Pro right now. This is not a themed ROM to make it look like AOSP ROM.
The purpose of this ROM was to remove all Blur and have a real Android experience. Please do not ask to add anything to ROM. Everything that is missing can be found in the Add On folder that was created when you installed ROM or can be downloaded from market.
The installed applications are all of your basic Android apps. Gmail, Voice Search, Car Home, YouTube and some other apps are missing since there are more updated versions on the market.
ROM has root, deodexed, busybox and zip alligned.
How To Report Bugs:
Before you report a bug please search through thread and see if someone has your problem and if a fix was found. If you do not find a fix please report bugs using this format.
In subject of post place "[Bug Report]" Bug here so it will read [Bug Report]Force Close with X APP.
In Body:
Device Name:
Explain in detail about bug and list anything that will cause it so we have more info when we correct it.
Install Insctructions:
Installing ROM:
This Method works for al supported devices.
It is suggested you follow all the steps even if you are coming from previous Fission ROM. If you do not want to perform all wipe steps then at least wipe system.
Pre-Installation Tasks:
You must have root. You can use our One Click Root in this THREAD.
You must have Koush's Bootstrap program for your device. Download from Market or check HERE.
Select the ROM for your device (Droid2, Droid2 WE, DroidX or Droid Pro)
Download and place ROM on SD Card
Open Bootstrap
Tap "Bootstrap Recovery"
Tap "Allow" if asked to grant SU Persmission
Tap "OK' on "Success" screen
Tap "Reboot Recovery"
You will be booted into Recovery
Use Volume up/down keys to navigate through menu. Press Camera button to Confirm selection. Power button to back up to last menu.
Create Backup - "backup and restore" then select what you want to do
Back out to main menu
Wipe Cache
Wipe Data
Mount System - Screen will read "UNMOUNT /SYSTEM" when mounted
Mount Data - Screen will read "UNMOUNT /DATA" when mounted
Back out to Manin Menu
Install Zip From SD Card
Choose Zip From SD Card
Select your ROM
Yes - Install
Wipe Cache
Wipe Data
Reboot
Back into Android
Perform a Factory Reset
Open App Draw
Tap Settings
Tap Privacy
Tap Factory Reset
Tap Reset Phone
Tap Erase Everything
Your phone will now be rebooted, perform factory reset and then reboot itself when completed.
Activate phone when prompted.
Enjoy!
You may install ROM by not wiping anything and not peform a Factory Reset. You will run into a few problems though. One will be battery manager may force close and Market Facebook App will not sync correctly with contacts.
Please do not ask if doing it another way is good. These are the instructions for a proper clean install and we will only accept bug reports if you followed the above instructions.
Installing Updates and Add Ons:
Open Bootstrap
Tap "Bootstrap Recovery" - if you have not installed yet on new ROM
Tap "Allow" if asked to grant SU Persmission - If you have not granted it SU permission
Tap "OK' on "Success" screen - if you have not installed yet on new ROM
Tap "Reboot Recovery"
You will be booted into Recovery
Use Volume up/down keys to navigate through menu. Press Camera button to Confirm selection. Power button to back up to last menu.
Mount System - Screen will read "UNMOUNT /SYSTEM" when mounted
Back out to Manin Menu
Install Zip From SD Card
Choose Zip From SD Card
Select your Zip File
Yes - Install
Reboot
If you are installing more than one update zip then please remember to mount system before installing new file.
Donations:
We do not have a DX to fully test ourselves yet so donating to project will help us obtain one. We would also like to obtain future devices such as the Droid Pro, Droid2 World Edition and whatever else may come down the pipe that we can port this ROM too. Your help will allow us to do that. If you would like to contribute to our project you may do so by clicking HERE
Downloads:
Fission 1.2.1 for Droid2 HERE
Fission 1.2.1 for DroidX HERE

Place Holder
Holding spot in line...
Hopefully lost stalker...

Please lets keep focus on thread topic if you have issues please PM me directly.
-McMex

Eagerly awaiting the release!
Sent from my DROIDX using Tapatalk

Breezer23 said:
Eagerly awaiting the release!
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
Your wait is over...ROMs are now up

is it 1.2 or 2.0?

jrherras said:
is it 1.2 or 2.0?
Click to expand...
Click to collapse
Haha...news spread quick...1.2. First 2.0 based on Android 2.2.1 will be for D2 some time next week. Would love to develop both side by side but do not have a DX to work with.

haha coz you said in other thread it's going to be on 2.0. Is there a HDMI settings on 1.2?

I want to install this but can someone confirm whether or not apps can be added to the car home app? I'm running ApeX right now and it has the Google Car Home, but apps can't be added to the blank slots. I know there is a version that lets you customize it, so is that what's included in this ROM?
I would just install it and see for myself, but uninstalling requires flashing the SBF and while I have the SBF, I don't have instructions on how exactly to do it and have never done it - so I'd like to avoid it if possible.

ok this is weird everything is as if i have Vanilla FroYo FRF91 installed, but I still have a few apps that were from blur like NFS Shift, Files, and a few others...can anyone confirm if they do or dont have these apps...also cardock is not opening, I'm gonna reflash ROM and report back!

DX 1.2 Users...Please apply this update http://tinyurl.com/2fejpew it removes the easter egg...aka...my D2 ROM...accidenta file placement
Hahah Sorry
When I was moving the new boot animation I must have dropped the wrong file

that link is broken for me

paul89 said:
that link is broken for me
Click to expand...
Click to collapse
http://tinyurl.com/25rjngt

paul89 said:
ok this is weird everything is as if i have Vanilla FroYo FRF91 installed, but I still have a few apps that were from blur like NFS Shift, Files, and a few others...can anyone confirm if they do or dont have these apps...also cardock is not opening, I'm gonna reflash ROM and report back!
Click to expand...
Click to collapse
NFS and Flash are there because you need to delete the apk files in the preinstall folder which can be found in the root folder of phone. This is after every SBF or fresh phone, not ROMs fault. Use Root Explorer or something like it.

indypacer said:
I want to install this but can someone confirm whether or not apps can be added to the car home app? I'm running ApeX right now and it has the Google Car Home, but apps can't be added to the blank slots. I know there is a version that lets you customize it, so is that what's included in this ROM?
I would just install it and see for myself, but uninstalling requires flashing the SBF and while I have the SBF, I don't have instructions on how exactly to do it and have never done it - so I'd like to avoid it if possible.
Click to expand...
Click to collapse
If you are talking about the market version then you can install on this ROM. I left the car launcher in but left car home out so there was no issue with market downloads. The launcher needs to be there so you can download it and launch it.

MotoBoy said:
Haha...news spread quick...1.2. First 2.0 based on Android 2.2.1 will be for D2 some time next week. Would love to develop both side by side but do not have a DX to work with.
Click to expand...
Click to collapse
Wow... I am really looking forward to getting a 2.2.1 based rom If you need someone to test on the DX I am available

kejar31 said:
Wow... I am really looking forward to getting a 2.2.1 based rom If you need someone to test on the DX I am available
Click to expand...
Click to collapse
+1 also...
I sent you a PM via DroidLife regarding another issue...
Thank You

Thank you for another awesome release . Now!! you keep asking for donation, but you just refunded mine. I guess my money is not good enough..... (just kidding. I got the email). Donation resent with a little more.
I said this before. I'm in South Fl. and you are more then welcome to use my DX.
Thanks again for your guys hard work.

Anybody care to put up a video of this on YouTube ?

New hot fix is now posted. Cures data still being active when a custom profile is used in battery mananger.
The link is in the first post under the hot fix section.

[TUTORIAL] Replace Windows Mobile with Android NAND ROMs

About
This thread contains all the Android NAND development that is going on in different websites like Github.com
The developers are not responsible for any damages happened to your phone in any way so be aware of what you are doing
Note that the development is still in "Beta" state and it has few issues which are still under development, the Android NAND ROMs are almost ready for day to day use
you can always switch back to any windows mobile ROM by flashing the official or a custom windows mobile ROM just like when you had windows mobile using any Sony Ericsson Xperia X1 ROM Update utility or the SD Card (KOVSIMG.nbh) method, as the SPL or windows mobile's bootloader will not be effected
there will be few random screen flashes when the device start even when you shift back to windows mobile but this does not effect the performance of the device in anyway
Your SD Card Android ROMs are not going to be effected but you wont be able to run them unless you re-install Windows Mobile again
below is the list of whats working and not working so far
Working
Phone
SMS
Speaker
LEDs
Bluetooth (beta)
Headphone
Media Playback
Touch Pad
Data connection (GPRS/3G)
Main Camera (Beta)
Hardware acceleration (3D/OpenGL ES) (beta)
USB (beta)
Screen (beta)
Keyboard/Keypad
WiFi (Beta)
Battery Meter (beta)
Battery Charging
Battery Life (beta)
Camera Flash LED
GPS (beta)
Not working
Light Sensor (Under development)
FM Radio
Hardware Acceleration bugs
Flash Player support, YouTube HQ Mode support
Front Camera
Main Camera bugs (under development)
focus function
WiFi bugs (under development)
WEP connection support
GPS bugs (under development)
Bluetooth bugs (under development)
once turned on, causes rapid battery drain and cant be turned off unless user restart the device
USB bugs
Battery Life (beta)
still not same as Windows mobile
Screen auto rotation bug
rotates to landscape every time user turns the screen off and on
Battery Meter (beta)
inaccurate after certain percentage of battery
Downloads
below is the list of Files which are required
HSPL 0.78 (optional)
Download it from here if you haven't install a Custom ROM before or you are on initial HSPL 0.72
A ROM update utility (optional)
Kovsky Advance ROM update utility is recommended as Its easier to work with, but the official RUU and SD Card method will do the same
Latest Android bootloader
Download the latest bootloader available here
Android Driver and Fastboot
Xperoid installer is recommended as it contains the necessary files of Android SDK only and can do the job automatically,
Latest Android Recovery
Download the latest recovery available here
Latest Android Kernel
Download the latest Kernel available here
An Android ROM
choose and download your favorite Android ROM from here or here
Video
Here is the video of how to install any NAND ROM, lots of steps have changed but the main procedure is the same
PART 1
PART 2
1.HSPL
If you have already installed a custom Windows Mobile ROM and have the 0.78 version skip this part, to know about your SPL version turn off your phone, hold Volume down button and while holding hold the power button till you see the Tri colour screen which is the SPL; If you have Olinex name on any line, you have HSPL,
SPL is like your devices BIOS, and Hard SPL will unlock your devices bootloader to allow you to install any custom made Read only memory (ROM)
to do a HSPL refer to THIS thread
(if you had a problem in performing a HSPL, read the replies at the end of the above thread as there were some users not being able to HSPL the normal way and had to do few other steps)
2.Android BootLoader
Put the .zip ROM you have downloaded in the root of your SD Card before you do anything further; which means put the .Zip file in E:\ROM.zip if your SD Card drive letter is E
HTC Linux LK bootloader allows the device to run the kernel directly after it got turned on
Install it just like the way you install any other Windows Mobile ROM, which is using a RUU or the SD Card method
It is always recommended to do a Task29 before you flash an Android Bootloader if you know how to.
(Kovsky Advance RUU)
3.Kernel
Kernels are like drivers in PC, it connects and manage the hardware of the device
they have to be installed using Fastboot. Fastboot is a command line tool used to directly flash the filesystem in Android devices from a host via USB.
>For Windows users
Extract Xperoid Installer
Rename the Kernel you have downloaded to boot.img, then place it in the Xperoid fastboot folder
Rename the recovery you have downloaded to recovery.img, then place it in the Xperoid fastboot folder
connect your phone and install the drivers from Android USB driver folder
then simply run Xperoid Fastboot installer.bat from the Xperoid fastboot folder
>For Linux based OS users
follow the instruction on This page
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5.Recovery
ClockWorkMod Recovery is like the BIOS in PCs, which is the software that can install and manage the device's software
To go into recovery turn on your device and as soon as the phone starts (Sony Ericsson logo stage) hold the Camera Focus button which is holding the Camera button half pressed till recovery starts, (it might take few seconds to load)
once you are in recovery use the touch pad to go up and down, power button to go back and middle button to select trough the menu,
Go to mounts and storage> Format Data
Go to mounts and storage> Format Cache
Go to mounts and storage> Format dalvik cache
go back to main menu
Go to install zip from SDcard
select the file and install it
after installation select restart system now
Remove the SD Card and the battery, put the battery in, turn on the phone and wait till it completely start up
Re enter recovery with SD Card inserted and install the GAPPS
Load the system without SD Card and sync it with your accounts and open all the apps once and then restart again and once you are in android again insert your SD Card
If you are updating your ROM from an earlier version of NAND Android ROM
Download the full wipe script and put it in the root of SD Card
Go to backup and restore
select Backup
go back to main menu
Go to install zip from SDcard
select the full wipe script.zip and install it
go to main menu
Go to install zip from SDcard
select your new ROM and install it
go back to main menu
go to backup and restore
go to Advanced restore
select Restore data
go back to main menu
select restart system now
Recommendations:
Booting with SD Card inserted:
As you might have notice in the guide, the Kernels have a major bug of not being able to boot the ROM with a normally formatted SD Card inside the device. so we have to format the SD card in a special way to bypass this problem
To do so follow this guide
You have to perform these recommended actions for better performance
Back to Windows Mobile:
In order to switch back to any windows mobile ROM, enter the Windows mobile bootloader (SPL) by turning the device on while holding Power and Volume down buttons together, and once you entered SPL simply flash the ROM as you did earlier
It is always recommended again to do a Task29 before and a Hard reset after you installed a Windows Mobile ROM
report back your issues and problems for faster and better ROMs in future.
Special thanks goes to:
SP3DEV
Sun Dream
XDAndroid team
Neopeek
Ady
zargloub
Jerrytan
BrickPSP
Elibl
Im not asking for donation but press the thanks button , Please Vote for this thread too

Hi, very good guide... but
What features are working/not working on the NAND build?

lordblacksuca said:
Hi, very good guide... but
What features are working/not working on the NAND build?
Click to expand...
Click to collapse
updated

kerfooly said:
updated
Click to expand...
Click to collapse
could you add a link to gapps, too?
The guide is very good But I have allready done it
Edit: Just want to let you know, CWM is upside down.

Greetings, guys!
It is necessary to simplify setting!

Task 29
Hey guys,
Just tried to flash the NAND version, but after doing the task 29 I cant reconnect to the PC to flash the other stuff like LK Bootloader etc. All i get is the Sony Ericsson logo at the start of the boot.
How can to get around this?
Thanks in advanced

you must go in bootloader (hold Volume down+power button until you get in the tri-color screen) in order to connect to pc via usb

stefanpowell said:
Hey guys,
Just tried to flash the NAND version, but after doing the task 29 I cant reconnect to the PC to flash the other stuff like LK Bootloader etc. All i get is the Sony Ericsson logo at the start of the boot.
How can to get around this?
Thanks in advanced
Click to expand...
Click to collapse
Go in Bootloader to flash LK Boot

Hi Guys !
When wallpaper are changed the Android will restart. And sometimes reset when I try to unlock phone.
EDIT:
And when I try to unlock the phone screen will be whole black until the keyboard is opened.

Yes, these problems are kernel related...
Like bad wifi width, no mobile data (can't understand why it isn't included, because it says it is easy to add).

Finally, This sounds great ... finally a NAND build ... following with great excitement ... I'll flash it as soon as I get a chance ... college is keeping me busy ... but I'll try to find time to read and figure it out ...
THANKS SO MUCH

Great
Thanks for the update, very nice build, I hope we can have a fully working android in NAND soon.
Thank you all.

Waiting For Final NAND Android?
Are you developing this Nand Rom?

tamakura said:
Waiting For Final NAND Android?
Are you developing this Nand Rom?
Click to expand...
Click to collapse
if you want final nand soon just flash this and report errors and issues, it will help alot

neoofoox said:
could you add a link to gapps, too?
The guide is very good But I have allready done it
Edit: Just want to let you know, CWM is upside down.
Click to expand...
Click to collapse
updated again please do report more

tamakura said:
Waiting For Final NAND Android?
Are you developing this Nand Rom?
Click to expand...
Click to collapse
No this is mostly done by SP3DEV (alex)

does this ROM support Flash and AVI?

Hammerhead89 said:
does this ROM support Flash and AVI?
Click to expand...
Click to collapse
non of the ROMs support Flash player, but AVI, if you install an app and your file be small maybe

Could someone send me the driver for x1 while it is connected in fastboot mode, because it can't find a driver (win xp) have tried the contained driver in the sdk pack, and some others.

I am new here. I flash LK Bootloader successfully. But I don't how to do next step. I downloaded and installed Android SDK, I installed Google usb, I start the phone and it's start into boot loader screen with "reverting to fastboot..." so I don't know ho to do fast boot via PC
=============================
I did it but recovery is up - down :-( any solutions?

[APP] Flash Image GUI - Flash Kernels and Recoveries from normal Android mode!

Credits:
birbeck for the usual random java guidance, slushpupie for his previous java guidance, dodgejcr for extreme amounts of testing, and one_love_420 and shift for some great graphics!
testers: JT-, couga6442, happytweak and many others I might have forgot in the furry of three days I built the initial app from scratch.!
Thanks to SDX
Works with HTC Unlock Method:
Tested after using htcdev.com's bootloader unlock method.
Please see the guides at the bottom of this post!
Background:
flash_image (bmlwrite) is an extremely useful utility for flashing custom kernels, boot logos (so far ONLY Samsung devices) and recoveries. This binary has made it possible to easily flash all these items and is used almost everywhere behind the scenes (i.e. in custom recoveries, packaged into a kernel /sbin directoy, included in custom ROMs, etc).
Description:
This android application, FlashImageGUI, is basically a GUI interface for the linux binary, flash_image provided by google in AOSP for loading custom kernels and recovery images onto the phone.
This app allows the flashing of kernels and custom recovery images in normal android mode!
Current Device Support:
Full Kernel, Logo and Recovery flashing: Samsung Moment, Transform, Intercept and Acclaim - the s3c6410 series of devices
Full Kernel (Anykernel and boot.img) Flashing and Recovery (zip file or image) flashing: Sprint HTC One, T-Mobile HTC One, HTC EVO 4G LTE, One S, EVO 3D CDMA and GSM, One XL, Droid DNA, Amaze, Vivid/Holiday, EVO 4G, EVO Shift, Google Nexus 4, Google Nexus 10, Google Nexus 7, Samsung Google Galaxy Nexus, Nexus S/Nexus S 4G & LG Optimus
Full Kernel (zImage) Flashing: Samsung Epic
Check application version for updates
Future Support:
Will continue to test kernels as they are released to ensure compatibility!
YouTube Install Video:
http://www.youtube.com/watch?v=9aqnhFxb__k
Thanks @wwjoshdew !
Install Directions:
Install process is the same as any other .apk. Download to computer and adb push or mount sdcard on computer and copy over or download directly to the phone. Use any file manager, adb, connectbot/terminal emulator to install.
My preferred method, maybe a bit technical: ./adb install c:\downloads\FlashImageGUI.apk
Download Locations
Market (99 cents!): Flash Image GUI
Release version (free): Flash Image GUI
Contact:
Any questions, comments, concerns, or issues, please post in this thread or send me an email! Thanks for all the help and support!
FAQ:
Q: Will this app support a marketplace to pick and chose kernels from?
A: No. Use Kernel Manager!
Q: Can I flash nandroid kernel backups?
A: Yes. Rename the specific image to boot.img and select from inside of Flash Image GUI. **Make sure to also load the associated modules or WiFi might stop working!
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Feedback:
Please post any helpful feedback. I'm always looking to improve the application!
HTC Unlock - User Guides for Flash Image GUI!!
HTC Unlock - Users Guide for ROMs with a Kernel (boot.img file):
1) Unlock using the HTC method and gain root access.
2) Load this application, Flash Image GUI, onto the device, either through the Market or the link provided in this OP.
3) Download ROM .zip file to the sdcard on the device.
4) Open up Flash Image GUI, select Browse and select the ROM .zip file, downloaded to /sdcard in the previous step.
5) Flash Image GUI will provide a warning, reminding that the ROM .zip file will *need* to be flashed in the custom recovery afterward.
6) Flash Image GUI will index the full ROM .zip file searching for the kernel and kernel modules. Once located, the Flash Image button should be enabled.
7) Select the Flash Image button and Flash Image GUI will load the kernel modules and kernel from inside the ROM zip file.
8) Select reboot recovery.
9) Inside the custom recovery, wipe data as ROM requires and load/flash the ROM zip file.
10) Reboot to normal Android mode and all should work including WiFi!
HTC Unlock - Users Guide for flashing ONLY a Kernel (zip file):
1) Unlock using the HTC method and gain root access.
2) Make sure the selected Kernel is compatible with the currently loaded ROM. If not, this will result in a lot of frustration!!! See troubleshooting steps below.
3) Download kernel zip file to /sdcard.
4) Open Flash Image GUI, browse and select kernel zip file, downloaded/loaded to sdcard in previous step.
5) Flash Image GUI will validate the kernel zip file is contains the minimum required files
6) Select the Flash Image button and Flash Image GUI will load the kernel and the kernel modules from the source kernel zip file.
7) Reboot
Troubleshooting after Rebooting:
First step, when experiencing issues flashing is to RE FLASH the files again. Many times, re flashing again will clear up any issues. If not, see the issues/solutions below.
Issue #1: If the device hangs or reboots while on the splash screen, the kernel itself or the ramdisk packaged in the kernel is NOT compatible with your device!!!
Solution for #1: Have to boot into fastboot (or directly into the custom recovery) and load the custom recovery to flash a known good kernel or restore a previously known good nandroid backup. Command: fastboot boot c:\downloads\cwm-recovery.img
Issue #2: If the device hangs or reboots while on the boot animation, the ROM is likely NOT compatible with the kernel!!!
Solution for #2: Have to boot into fastboot and load the custom recovery to flash a known good ROM/kernel combination either from a zip file or restore from a nandroid backup.

I actually used this app the other day I used on my evo lte a lot before s-off. Also makes flashing kernels and recoveries a breeze
Sent from my HTCONE using xda premium

This is a great app. Been using it for a while....thanks.
via phONE.

For the guys who never used it,it works great. Forgot how much it was but it was worth every dime.
Just an amazing app.
Sent from my HTCONE using Tapatalk 2

I made a video showing how to update/install custom recovery using your app! Thanks @joeykrim!
http://www.youtube.com/watch?v=9aqnhFxb__k

wwjoshdew said:
I made a video showing how to update/install custom recovery using your app! Thanks @joeykrim!
http://www.youtube.com/watch?v=9aqnhFxb__k
Click to expand...
Click to collapse
Excellent! I've added a link in the OP. Thanks!

App didn't seem to like philz_touch_5.08.5-m7spr.img wouldn't work for me, verified md5 downloaded it twice wouldn't work, then I renamed it to TWRP.img and finally it work and would allow me to hit the Flash Image button.

im0rtalz said:
App didn't seem to like philz_touch_5.08.5-m7spr.img wouldn't work for me, verified md5 downloaded it twice wouldn't work, then I renamed it to TWRP.img and finally it work and would allow me to hit the Flash Image button.
Click to expand...
Click to collapse
The error message that occurs each time you select a file that doesn't fit the naming criteria says, for a boot.img file, it needs to have the phrase "boot" in the name. Just need to add "boot" to the filename, for example: philz_touch_5.08.5-m7spr-boot.img.
Unfortunately, this limitation came about from beginners flashing incorrect files and overwriting their kernels so the device wouldn't boot. No real way around that issue other than silly filename limitations in an effort to education the users.
I test out the function real quick and the error message does come and go fairly quickly. I'll look at adjusting that so it the error message sticks around a bit longer to make it easier to read it.
Thanks for the feedback and hope that helps!

Thanks for the quick reply. This was definately worth the 99 cents. Since I can never get fastboot drivers to work on windows 8.

Myself, I prefer to adb .img's. But for a person who isnt as familiar with adb or someone who just doesnt want to, this is a great app, well worth the .99cnts. Thanks joey.
***Sent from my Super Groovy Hand Held Porno Machine***

Will this let us flash a firmware update instead of using adb? Thanks
Sent from my HTCONE using Xparent Blue Tapatalk 2

treIII said:
Will this let us flash a firmware update instead of using adb? Thanks
Sent from my HTCONE using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
Unfortunately, as far as I've seen HTC doesn't allow direct access to the firmware components from the standard booted Android mode. If you see any new information on how to access the firmware components directly, feel free to provide the links here and I'll research.
Thanks for the support!

[Q] how to root and installing CM 10.1.2 on i9000

I searched for more than 3 hours to root and install CM 10.1.2 on my Samsung Galaxy S i9000
but i dont find anything good i lost my mobile :crying: then it works again :silly:
my mobile information:
GT-I9000
Firmware Ver: 2.3.3
Baseband Ver: I9000JHJV9
Build number: GINGERBREAD.JHJVG
Thank you.

i found it to use these files and kernels
https://app.box.com/shared/z2jmmzres0
a video but in Arabic
http://www.youtube.com/watch?feature=player_embedded&v=6WiuaSlKYC8#t=244
is it right????

sycolon said:
GT-I9000
Firmware Ver: 2.3.3
Baseband Ver: I9000JHJV9
Click to expand...
Click to collapse
Follow this and root only after your firmware is 2.3.6
Check this out!You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, please click on the Thanks button
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.​

Use Samsung Kies and update your phone to a newer build.
Download a root package from here (search for your build after the update) : http://forum.xda-developers.com/showthread.php?t=788108
Download odin3 1.85 and flash the rom (in odin only put the tar file in the pda box - the phone has to be in download mode {volume down+power+home pressed}) .
Go online (google play) on the phone and download the clockwork mod and install it.
Download the latest stable CM10.1.2 from here: http://download.cyanogenmod.org/?type=stable&device=galaxysmtd
Put the cm10 archive on the sd card and power off the phone.
Enter in the recovery mode (volume up + power + home) and using the volume select Wipe Data/Factory Reset and in advanced Wipe Dalvik Cache. Go back and select install zip from sd card. If it's done quick do the install from zip again.
The full tutorial here: http://forum.xda-developers.com/showthread.php?t=1494493
Do the root like i said because it's easy and then follow the guide from point 4 "• Using the volume buttons to navigate up and down select..."
After search for a google play app pack (gapps) and put it in the sd card and install it using recovery mode.
I did this yesterday and it works great.

i made the same as i told you in the last post
"i found it to use these files and kernels
https://app.box.com/shared/z2jmmzres0
a video but in Arabic
http://www.youtube.com/watch?feature...uaSlKYC8#t=244
is it right????"
and i installed CM 10.1.2
and all i s ok for now, i have 2 problems no service and the mobile reboot from its own when i dont use it....crazy

is it possible that i have the problem cuz i didänt make Lag Fix for it????

do you have the clockwork mode installed?
go back in recovery mode and wipe data/dalvik again and install cm10 again.
sycolon said:
is it possible that i have the problem cuz i didänt make Lag Fix for it????
Click to expand...
Click to collapse

yes i have it... i will try .... do i install CM 10.1.2 ?

Yes.

i tried to make it but still the same problems

i made the CM 10.1.3 and still the same problem, automatic rebooting wjen i dont use the mobile and no service .....

yes finally i fix it, thanks guys for all, but i did it in my way yeaaaaaaaaaaaah

Does it work? Are you happy with CM?:good:
sycolon said:
yes finally i fix it, thanks guys for all, but i did it in my way yeaaaaaaaaaaaah
Click to expand...
Click to collapse

yes i'm using the CM 10.1.3 Rc2 and its fantastic........... i love it

the only thing i found weird in the CM that he mentioned that the memory is 368MB just of 512MB !!!!

sycolon said:
the only thing i found weird in the CM that he mentioned that the memory is 368MB just of 512MB !!!!
Click to expand...
Click to collapse
Don't worry about that. Part of memory has been reserved by the CM. You may like the CM10.2, it is in nightly stage but even faster than 10.1.3 and you will have about double battery life. But read very carefully whole first post before installing it. It is bit odd way comming from cm10.1.3
Or quote my text (reply this e-mail) and I will send you the workflow, it isn't absolutely clear written in the opening post ofnthe thread.

tetakpatak said:
Don't worry about that. Part of memory has been reserved by the CM. You may like the CM10.2, it is in nightly stage but even faster than 10.1.3 and you will have about double battery life. But read very carefully whole first post before installing it. It is bit odd way comming from cm10.1.3
Or quote my text (reply this e-mail) and I will send you the workflow, it isn't absolutely clear written in the opening post ofnthe thread.
Click to expand...
Click to collapse
thanks you so much then i wish to have the instructions about upgrading to 10.2

Update-Desc http://forum.xda-developers.com/showthread.php?t=2385178
The rest of RAM is reserved for audio/video coding ,example camera for HD-mode and kernel for the linux system
Some Kernel support RAM up to 408MB but with no HD-support then...
sycolon said:
the only thing i found weird in the CM that he mentioned that the memory is 368MB just of 512MB !!!!
Click to expand...
Click to collapse

More information about RAM (in example the semaphore kernel ...http://www.semaphore.gr/how-to/use-semaphore-jb
"Bigmem
When the kernel boots, it reserves some RAM to be used by some drivers (video, capture, JPG) for DMA (Direct Memory Access). In Linux kernel this reservation have to be done only during boot. It was found that using less reserved memory for video capture, the kernel can operate normally without issue with the only regretion that 720p video recording is not possible. Enabling this option will leave ~13MB more available RAM.
Phone must be rebooted to enable this feature. After the device powers down the information about this option is lost and you have to reboot the phone again.
Default: Disabled"
freakymod2120 said:
Update-Desc http://forum.xda-developers.com/showthread.php?t=2385178
The rest of RAM is reserved for audio/video coding ,example camera for HD-mode and kernel for the linux system
Some Kernel support RAM up to 408MB but with no HD-support then...
Click to expand...
Click to collapse

Upgrade workflow to the CM 10.2
sycolon said:
thanks you so much then i wish to have the instructions about upgrading to 10.2
Click to expand...
Click to collapse
Ok, from CM10.1x it should work like this:
This is the thread of CM10.2 development for the i9000:
http://forum.xda-developers.com/showthread.php?t=2385178
Read whole the first post there.
Preparation:
Before upgrading, first prepare all this for the case anything goes off the plan (it shouldn't, but who knows...):
make nandroid backup
download zip files of your presently used ROM (cm10.1.3) and gapps for Android 4.2.2 and save them in your phone
download zip files of the new ROM you want to install (cm10.2) and gapps for Android 4.3 and save them in your phone
boot your phone into the recovery mode (CWM) and check if all zip files are visible
Now if all the files are visible you can upgrade (some CWM recovery versions can read zip files only from the external SD, some other versions only from the internal SD card, some both). If they are not visible, don't even try upgrade (and don't wipe any data) but reboot phone and move the zip files to another place (for example if they were not visible on internal SD, move them to the external SD card) and after you moved the files, do again the check like I wrote you above.
Upgrade:
make factory reset/wipe data
wipe cache
wipe dalvik cache under "advanced"
install zip of the CM10.2 nightly build (possibly you need to install twice, as it uses different re-partition and only warns the first time)
install the Gapps for 4.3 right after, while still in recovery
while still in recovery go to "advanced restore" and restore only /data from your last nandroid backup of the cm10.1.3
go back to first menu, reboot
enjoy, all your data from presently used cm10.1x build should be there, including Google account
If anything should go wrong, make the same procedure like you did for the installing CM10.2, wipe all and make factory reset, after that just instead of the CM10.2 zip flash your CM.10.1.3 zip and gapps for Android 4.2.2, reboot, boot again to recovery, restore your whole nandroid backup of the CM10.1.3 build.
Let me know if it worked well

[BOOTLOADER][SAFEBOOT] Ouya Bootmenu (mlq)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ouya Bootmenu development/release thread​
This is based on the awesome work by Hal9k.
Because of the fact that the Ouya doesn't have recovery accessibility via hardware buttons we need to play safe and utilise chainbooting.
This bootmenu resides in the kernel partition and is loaded on every normal bootup.
In-depth info in Hal9k's thread here: http://forum.xda-developers.com/showthread.php?t=2499673.
It presents various choices on every boot:
Normal boot - (default) loads bootimage from system partition (/system/boot.img)
Alternate boot - loads bootimage from sdcard (/sdcard/altboot.img)
Recovery - reboots into recovery (recovery partition)
Failsafe - loads built-in failsafe mode
Bootloader - Reboots into stock bootloader (for fastboot access - USE WITH CARE)
Notes about the failsafe
the failsafe mode (which has the bootmenu built-in) will pop up in the following cases:
the bootmenu could not find a valid bootimage (read: /system/boot.img for "normal boot"; /sdcard/altboot.img for "alternate boot")
the user selects "failsafe" from the menu
the failsafe mode resides in the bootmenu image itself and should ONLY be used (as its name suggests) as failsafe.
for regular flashing you need to use a newer cwm version which resides in the recovery partition and is accessible via the "recovery" entry in the bootmenu (see below).
And remember: After flashing this you DON'T NEED TO EVER touch your boot/LNX partition again
Reminder: Failsafe mode is ONLY to be used in case you can't boot into your recovery partition. For regular rom flashing the respective CWM recovery (see below) is required.
Installation
You need to have a newer CWM recovery installed in order to flash the bootmenu.
READ AND UNDERSTAND what you are doing!
This bootmenu is flashed over your current bootimage - newer cyanogenmod builds will place their bootimage to /system/boot.img automatically. if you are not using a custom rom you will need to relocate your bootimage (read: kernel) to /system/boot.img manually.
You need to have a newer CWM recovery installed in order to flash the bootmenu (otherwise you'll get a build.product mismatch while installing).
1a) If you already have an older custom recovery installed:
Boot into recovery and flash https://download.milaq.net/public/android/ouya/misc/recovery-clockwork-6.0.4.8-ouya.zip. This will update your recovery to a newer version allowing you to flash the bootmenu regularly.
1b) If you don't have a custom recovery installed:
You can either use the one-click installer from http://forum.xda-developers.com/showthread.php?t=2295645 and continue with step 1a).
Or you can flash a newer recovery via fastboot (if you know what you are doing): https://download.milaq.net/public/android/ouya/misc/recovery-clockwork-6.0.4.8-ouya.img
2.) Flash the bootmenu via (the new) recovery by installing the latest updatezip (download below). Make sure that the installation procedure was successful.
If you get a "MD5 mismatch" your download is probably broken. Just redownload and try again. The installscript checks the md5's mutliple times while installing and reflashes your old bootimage in case something goes wrong.
So if you are not doing something REALLY stupid this is safe to go.
Download
Download latest version (v2.0.4)
Changelog
Code:
2.0.4
* reduce menu timeout for faster regular boot
* ui improvements in failsafe mode
2.0.3
* bootmenu: increase maximum number of input devices to 5 - e.g. the gpio
keys (the ouya power button - 1 node), a mutlimedia keyboard (2 nodes), a mouse (1 nodes)
and a controller (1 node).
2.0.2
* add in additional alternate boot image folder handling to fix compatibility with kitkat
* update failsafe recovery to differ more from regular recovery
* minor ui and ux tweaks in both bootmenu and failsafe
2.0.1
* initial reworked version
And as always: we take no responsibility whatsoever for raging, screaming, crying, frustration, failing, confusion, dead kittens, etc.
Source
https://github.com/milaq/ouya_bootmenu

Thanks/Credits
Click to expand...
Click to collapse
Hal9k - for the inital ouya bootmenu and many great ideas
Dan Pasanen (invisiblek) - for great work on the recovery and initial porting efforts
Let me know if i omitted you and i will add you here asap
IRC channel
Click to expand...
Click to collapse
Visit us in #cyanogenmod (general) or #cyanogenmod-dev (only dev related talk) on freenode

alright so i installed it, and normal boot boots back into recovery

YoshiFan501 said:
alright so i installed it, and normal boot boots back into recovery
Click to expand...
Click to collapse
This bootmenu is flashed over your current bootimage (you will need to relocate your kernel (to /system/boot.img) if you not using a custom rom)
Click to expand...
Click to collapse
most probably because /system/boot.img is not found. you need to install cyanogenmod afterwards or relocate your bootimage if still on stock.

Is it possible to easily revert the Ouya to a fully stock state after this? Any unninstall method?

Fyi everyone, if you scroll down through the options in cmw a couple times you'll activate rainbow mode! I'm not sure if this is an ouya specific cmw mod or not cuz all my other devices have twrp but anywho ENJOY!
Sent from my Galaxy Nexus using XDA Premium 4 mobile app

Is it possible to use this bootloader with the EternityProject Kernel 3.4.37 for OUYA and the OUYA-Enhanced Rom. I can flash the ROM from within Recovery, but how do I install their kernel for it to boot in ouya bootmenu? I just don't want to brick, thanks for your help!

Just wanted to be the first to tell you that it's working fine and I'm glad to finally give the ouya what it deserves: a custom ROM! Thanks dude!

Can someone post a step by step to move from ep bootlegger to this one?

So can this be dualbooted? If stock ouya boot image is put on /sdcard and named altboot.bin? Right now if I select Alternate Boot, it boots cwm 6.0.3.2. Same as Failsafe.

new version
new version is available in the first post

firmtech said:
So can this be dualbooted? If stock ouya boot image is put on /sdcard and named altboot.bin? Right now if I select Alternate Boot, it boots cwm 6.0.3.2. Same as Failsafe.
Click to expand...
Click to collapse
update the bootmenu to v2.0.2 and rename your alternate bootimage on /sdcard to "altboot.img" and you should be ready to go

milaq thanks for excellent work....
Can you add reboot recovery options in Ouya Failsafe menu to get the full recovery menu?
The power button(for choices) works only if ouya connected-hdmi to hdmi
If Ouya connected hdmi to dvi(Pc monitor) the power button does not respond!
So to go into recovery mode, you can use alt + printScn (SysRq) + i (if keyboard connected)
But now the Ouya goes into a Failsafe menu.

version bump again
krest said:
the power button does not respond!
Click to expand...
Click to collapse
i suspect that you have too many input devices connected during boot.
in version <=2.0.2 the maximum number of input devices that are recognised in the bootmenu was 3.
in case you have a keyboard (usually takes up 2 input nodes) and a mouse connected, the ouya power button (also an input device) was at the end of the list thus not taken into account.
i raised the number of recognised input devices to 5 in version 2.0.3 (see first post for download). that should allow most setups to work fine.
in case you still can't use the power button to select just briefly disconnect your usb devices at boot and reconnect them after making your choice in the bootmenu.

milaq said:
i suspect that you have too many input devices connected during boot.
in version <=2.0.2 the maximum number of input devices that are recognised in the bootmenu was 3.
in case you have a keyboard (usually takes up 2 input nodes) and a mouse connected, the ouya power button (also an input device) was at the end of the list thus not taken into account.
i raised the number of recognised input devices to 5 in version 2.0.3 (see first post for download). that should allow most setups to work fine.
in case you still can't use the power button to select just briefly disconnect your usb devices at boot and reconnect them after making your choice in the bootmenu.
Click to expand...
Click to collapse
Yes, you're right....
Now it's working perfectly
In any case, it would be great if you added the reboot recovery options in Ouya Failsafe menu.
Thanks

Dual Boot
Now that I have CWM with the newest boot menu and CM11 running super smooth how do I go about flashing the stock Ouya ROM to the SD card without wiping the whole thing again? Must restore balance in the household. The natives are demanding to have Amazing Frog back!

bootmenu v2.0.4
new version up.
see first post for details.
KJRob said:
Now that I have CWM with the newest boot menu and CM11 running super smooth how do I go about flashing the stock Ouya ROM to the SD card without wiping the whole thing again?
Click to expand...
Click to collapse
dual booting the stock rom is not as easy as it may seem.
with the boot menu you _have_ the ability to dual boot another boot image (read: kernel/ramdisk) but you still need to have a partition where all stock roms system files reside. the internal "sdcard" is out of the game here as it is just a fused filesystem. but i could imagine external usb storage or such. one needs to partition it and make the respective changes to the stock ramdisk for it to work.
nevertheless, i will not spend time working on stock rom dualboot compatibility. but anyone willing to invest time into it is very welcomed to do so.

milaq said:
new version up.
see first post for details.
dual booting the stock rom is not as easy as it may seem.
with the boot menu you _have_ the ability to dual boot another boot image (read: kernel/ramdisk) but you still need to have a partition where all stock roms system files reside. the internal "sdcard" is out of the game here as it is just a fused filesystem. but i could imagine external usb storage or such. one needs to partition it and make the respective changes to the stock ramdisk for it to work.
nevertheless, i will not spend time working on stock rom dualboot compatibility. but anyone willing to invest time into it is very welcomed to do so.
Click to expand...
Click to collapse
I appreciate the reply. I would love to have the know how to do the work but that is out of my knowledge base. Maybe one day I will. I can wait for the official Ouya store to hit android. The kids will have to wait as well. I love my KK device just the way it is.

milaq said:
dual booting the stock rom is not as easy as it may seem.
with the boot menu you _have_ the ability to dual boot another boot image (read: kernel/ramdisk) but you still need to have a partition where all stock roms system files reside. the internal "sdcard" is out of the game here as it is just a fused filesystem. but i could imagine external usb storage or such. one needs to partition it and make the respective changes to the stock ramdisk for it to work.
nevertheless, i will not spend time working on stock rom dualboot compatibility. but anyone willing to invest time into it is very welcomed to do so.
Click to expand...
Click to collapse
It's doable but once its done both sides of the roms would have significant storage reduction... on another note the method would be completely ( and easily ) reversible to the actual installed rom.
The other route is like you said with usb storage which would probably be the better of the 2 options.
Although with all this said we know that the ouya storefront is coming in the form of an app and I guess the other option would be to "portablize" the current framework ( I did it with 519... could try with the latest one... but I never tried it on anything higher than 4.3 )

How do you revert back to factory settings? Every time I flash stock, it boots to this. Thanks and sorry in advance