Now that I'm satisfied with the results from the original testing thread, I'd like to announce the general public release of my modified version of the FIREFIREFIRE 1.2 bootloader. The main feature? You can dualboot two different ROMs! All of the downloads I'm providing are listed in the second post.
Standard disclaimer: I am not responsible for anything that happens to your Kindle Fire as a result of using this software. I designed this in my spare time, voluntarily, and choose to release it for others to hopefully enjoy. Although it has been safe throughout testing there is always a risk involved in modifying your device, including unpredictable and uncontrollable circumstances that I cannot prepare for. You have been given a fair warning.
Installation
You can install FFF Extended like you would any other bootloader:
Download the latest zipped binary from GitHub (links below).
Extract the u-boot.bin file from the zip. This is the bootloader.
If you already have a custom bootloader you can install from fastboot by rebooting into fastboot and executing fastboot flash bootloader u-boot.bin from a PC shell. You can also run this on your PC first and then reboot with your device plugged in; it should run when your device starts up fastboot.
If you do NOT have a custom bootloader, you can follow pokey9000's instructions for the original FFF:
Code:
Howto flash by hand
- Get into fastboot mode somehow. Having and older FFF from the TWRP
installer is a good start. Currently KFU or fbmode is the easiest
- flash with "fastboot -i 0x1949 flash bootloader u-boot.bin"
(take out "-i 0x1949" if FFF is already installed)
- disable fastboot: "fastboot -i 0x1949 oem idme bootmode 4000"
- reboot: "fastboot -i 0x1949 reboot"
Done! The bootloader is installed.
Prepping for dualboot
Once the bootloader is installed, you can use it right away to boot into recovery or your normal ROM. In order to use your device to dualboot, though, you're going to need to do a little bit of up-front configuration.
NOTE: Backup the data on your sdcard partition. It will be formatted during the setup procedure.
Get into fastboot somehow and execute fastboot oem dualformat
Reboot your device into recovery mode.
Use your recovery to format/wipe your sdcard partition. This varies between CWM and TWRP, but it will be in the "wipe" or "advanced" menus.
Download altrom-format-all.zip and flash it from recovery to properly format your secondary partition set.
Your device should be ready to flash an alternate ROM now.
To return to a stock partition layout, connect your device to a PC, reboot into fastboot, and execute fastboot oem format from a PC shell. You will probably want to format your sdcard partition afterwards.
Installing alternate ROMs
If you want to install an alternate ROM, the ROM must be properly packaged to use the secondary partition set instead of the default ones. Normal ROMs will install ONLY to your regular partition slots.
I am currently providing one ROM, which is a CM7 KANG build and a GAPPs package for it. You do not need to do anything special to install the ROM, just flash it from recovery as you normally would (see downloads below).
If you want to install a new alternate ROM, you can flash the altrom-factory-reset.zip to perform a "factory reset" of your alternate partitions (it will wipe data2 and cache2).
You cannot currently make a nandroid backup of an alternate ROM install (unless you want to manually use 'dd' or something). This would require recovery changes which I may or may not try to implement at some point, or someone else is welcome to do it if they feel so compelled.
Each ROM will have its own boot, data, system, and cache partitions and they will share your sdcard (media) partition. They run completely separately, and modifications to the kernel, apps, system, etc of one will not in any way affect the other.
Using the boot menu
FIREFIREFIRE Extended listens for 5 seconds and starts up fastboot like FFF1.2 does, but when you press the power button it starts a new 2.5 second countdown and effectively changes the selected boot state. This provides more flexibility because it allows you to "cycle" between boot options instead of just being a one-shot thing. Note that there is a slight delay before the power button will accept input, but you can tell when it's ready when the LED fades from bright green to darker green. You can see a demo of the boot menu on YouTube here: http://www.youtube.com/watch?v=xV2Jtu3fDSM
Packaging alternate ROMs
If you're a ROM author and would like to package your ROM for alternate booting, please see the "how-to" page on my GitHub. Note that some ROMs seem to play more nicely than others, so you may experience some bugs when running your ROM from the alternate partition set. I'd be happy to try to help you out if I can, but I can't guarantee that I'll know the solution to your specific issues.
Downloads and Source
Downloads are provided in the second post. The source for FFF Extended is available on my GitHub and is licensed under the GNU GPLv2. I've also set up a few wiki pages on my GitHub with some additional information about the bootloader.
Credits
Thanks and appreciation to:
pokey9000 for all of his development, tutorials, etc for FIREFIREFIRE and omap4boot.
All of the people that helped me test this.
Everyone who's worked on the CM7 repos that my altrom version is built on, both for the KF specifically (whistlestop, IngCr3at1on) and the CM project as a whole.
Downloads
These are various downloads provided by me. If you get a ROM from somewhere other than this post, I didn't package it. So if you have bugs, talk to the ROM author first
Bootloader
Latest version: GitHub, Mediafire (md5 of the u-boot.bin: 89df8d45262a92061c461e8ff134286a)
All versions: GitHub
Setup/Maintenance Files
altrom-format-all.zip (reformats all secondary partitions, flash from recovery)
altrom-factory-reset.zip (factory reset for your secondary partitions, flash from recovery)
My altboot ROMs
CyanogenMod7 KANG
Gingerbread GAPPS for altboot partitions
Bugs in this ROM: Unpredictably hangs on boot very occasionally (once every 5 or 6 boots, maybe?). Rebooting fixes it.
Kernels
IntersectRaven's 2.6.35.14 CM7 kernel, repackaged for altboot partitions (Thanks IR!): http://www.mediafire.com/?6b5545b55tx5jwd
Wooo hoooo, can't wait!!!!
Sent from my classic stock
Nice nice nice! Could you make a guide to change the updater-script for random ROM ?
Trojan38 said:
Nice nice nice! Could you make a guide to change the updater-script for random ROM ?
Click to expand...
Click to collapse
Check out the wiki page on GitHub. If you think it could use expansion feel free to let me know
Thanks and appreciation to:
pokey9000 for all of his development, tutorials, etc for FIREFIREFIRE and omap4boot.
All of the people that helped me test this.
Everyone who's worked on the CM7 repos that my altrom version is built on, both for the KF specifically (whistlestop, IngCr3at1on) and the CM project as a whole.
I think this is not so easy, you'll need to compile a source code of random rom.
Oh okay, I thought it was more simple, something like renaming partition names in the updater-script . Will take a look at it, thanks .
animefun135 said:
Thanks and appreciation to:
pokey9000 for all of his development, tutorials, etc for FIREFIREFIRE and omap4boot.
All of the people that helped me test this.
Everyone who's worked on the CM7 repos that my altrom version is built on, both for the KF specifically (whistlestop, IngCr3at1on) and the CM project as a whole.
I think this is not so easy, you'll need to compile a source code of random rom.
Click to expand...
Click to collapse
What?
eldarerathis said:
What?
Click to expand...
Click to collapse
Nevermind
I've installed your bootloader and running altcm7 rom, but if I want flash cm7 or cm9 kernels - how to determine to whom it is intended?
animefun135 said:
Nevermind
I've installed your bootloader and running altcm7 rom, but if I want flash cm7 or cm9 kernels - how to determine to whom it is intended?
Click to expand...
Click to collapse
If you mean "how do I know where it will install?" then it's all based on how it's packaged. Unless the ROM/kernel author packages the zip for the alternate partitions and specifically says that's what it's for, it will install for your regular ones. So everything is for your primary ROM unless otherwise noted by the author.
Dualboot Support for CM9
When will there be dualboot support for CM9??
thedeveloper1 said:
When will there be dualboot support for CM9??
Click to expand...
Click to collapse
When it's done.
Fixed
stephenm00 said:
What about a stock kindle image for the 2nd rom?
Click to expand...
Click to collapse
This would be quite a feat.
Sent from my Amazon Kindle Fire using XDA
I am kinda new to all of this so this is maybe a noob question!
I have Flashed FFF extended, but before Formatting my SD Card, I am just having some simple question: Would running 2 ROMs on my Kindle Fire be really heavy, we have a 8Gb of storage in your Kindle Fire and how much would it take out of the 8Gb? Is it acceptable for a "user" such as myself, I mean I will still have space to storage my personal data
Thanks!
pmdisawesome said:
I am kinda new to all of this so this is maybe a noob question!
I have Flashed FFF extended, but before Formatting my SD Card, I am just having some simple question: Would running 2 ROMs on my Kindle Fire be really heavy, we have a 8Gb of storage in your Kindle Fire and how much would it take out of the 8Gb? Is it acceptable for a "user" such as myself, I mean I will still have space to storage my personal data
Thanks!
Click to expand...
Click to collapse
Of the 8 GB, about 6 is usable by you normally, and 1 GB of that is reserved for apps leaving ~5 GB of general storage space (the "sdcard" partition). You'll end up with about 1 GB of data space (e.g. apps and the like) per ROM and 3.6 GB of general storage space using FFFE.
eldarerathis said:
Check out the wiki page on GitHub. If you think it could use expansion feel free to let me know
Click to expand...
Click to collapse
Thanks for taking the time to type this up, it helps alot. And thanks for your work on this project
Wow! Thanks for making this for us! It's amazing!
stephenm00 said:
What about a stock kindle image for the 2nd rom?
Click to expand...
Click to collapse
I have stock rooted 6.3 insecure, originally from here modded to install to the alternate partition.
If you want it, let me know and I can find a place to put it.
three-p-o said:
I have stock rooted 6.3 insecure, originally from here modded to install to the alternate partition.
If you want it, let me know and I can find a place to put it.
Click to expand...
Click to collapse
I know I want it........Please.
Related
This guide is for you that have a new Xoom (WiFi only, US model) with Android 3.1 and want to
- get root access
- enable the external SD card unit
Please note that Android 3.2, which now is available for the US Wifi models, make this guide more or less obsolete. If your aim is to have root access, then there are probably simpler methods.
What you need to do can be encompassed in these following short steps (will be detailed later on) in the following order. Each step is required before you can proceed to the next one. However, make sure that you are very very careful and dont try to take any shortcuts. That may soft-brick your device, and you may have a difficult time to explain that to your wife ... You have been warned!
I strongly recommend you to read the entire guide before trying this. In fact, read it twice to ensure that you have understood everything. If there is wierd stuff that you dont understand, dont hesitate to ask. The reason for me writing this down is that I like to document what I have learned. This is to me an excellent way to ensure that I will remember what I just did. Another reason was that I could not find a single thread that encompassed all steps required. There are many different threads, but noone (that I could find) that really guides you from start to goal. So enjoy and good luck!
I would like to thank LandMaster and cam30era for helping out with advice during my initial trail-and-error session. I soft-bricked my device once and had big problems to get by point 4.3 (avoid overwriting of CWM), but with their encouragement I finally succeeded.
If someone else adapts this guide for the EU model or the 3G model, feel free to drop me an IM and I will update the guide for these devices too. Until then, this has only been tested on a WiFi only, 32 GB device bought in the US. If you brick your 3G or EU bought model, dont call me ...
0. Overview of the 6 required steps
1. Install Motorola USB drivers for your computers (for USB connectivity)
2. Install Java SDK and Android SDK tools (for adb and fastboot commands)
3. Unlock the device for flashing (allowing replacement of recovery and boot images)
4. Install a modified recovery image (ClockWorkMod recovery for Android)
5. Root the device (Allow r/w access to the device filesystem)
6. Flash a kernel that supports the SD card (SD card access, overclocking etc.)
Steps 1, 2, 4, 5 and 6 require that you download install, image and zip files needed for the flashing.
All this was performed on a Windows XP x86 SP3. Windows 7, Mac and Linux users will probably have to do some steps differently.
Update July 7: I have tested the procedure on Windows 7 x86 now and the procedure is identical to Windows XP.
1. Install the latest Motorola USB drivers
The installation file can be found here
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
1.1 Install the drivers and ensure that your Xoom is recognized by the computer
2. Installation of development software
Java SDK 6 and Android SDK (for Honeycomb at least) need to be installed. You can find the installation kits here.
http://www.oracle.com/technetwork/java/javase/downloads/jdk-6u26-download-400750.html
http://developer.android.com/sdk/index.html
2.1 Install them as any other software.
2.2 What I had to do was to manually modify the PATH environment variable. I use Windows XP so I did that by right clicking on My Computer, choose Properties and select Advanced. Here I added the path to platform-tools and Tools
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\QuickTime\QTSystem\;D:\Java\Android-sdk\platform-tools;D:\Java\Android-sdk\tools
Note: If the Android SDK complains that the Java Dev Kit cant be found, just press Back and then Next again. Wierd, but that seems to do the trick ... go figure.
2.3 Test that ADB and FASTBOOT works. You should open a command window and go to your Android installation directory. Plug in your Xoom to your computer and write 'adb devices'. Your Xoom should now be listed like this
C:\Documents and Settings\Anders>adb devices
List of devices attached
0288414343813157 device
Did your device not show up? Make sure that you have USB debugging enabled in Settings / Applications / Development
3. Unlocking the device for flashing
This step will effectively erase the internal storage, including all your apps and settings. Use whatever backup you want to rescure important data before you start.
3.1 Power up and start the Xoom
3.2 Ensure that your device is fully recognized by the computer. A good sign is that the 'Portable device' dialog is activated on Windows when your Xoom has booted. The Xoom should also be seen in 'My Computer'. If not, go back to step 2 and double check your USB drivers.
3.3 Use the command 'adb reboot bootloader' to go into Flash mode
3.4 Use the command 'fastboot oem unlock'. This will trigger a dialog on your Xoom. Follow the instructions on the screen to complete the unlocking. I repeat, this *will* do a factory reset and all data will be lost!
3.5 Once unlocked, the Xoom will restart and work as normal, but now ready for step 4
4. Install recovery image (CWM)
Download the recovery image file and save it to your computer
4.1 Boot into flash mode with 'adb reboot bootloader'
4.2 Install your downloaded recovery image
C:\Documents and Settings\Anders> fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
4.3 Restart the device with 'fastboot reboot'. Timing is essential here, so be alert when the device restarts, or you will have to redo section 4.
4.4 Enter CWM with the following procedure
4.5 Once the Motorola logotype is shown, start counting to 3. At 3, press the Volume Down button. This should result in the text 'Android Recovery' in the top left corner. If it does not work, experiment with the timing ...
4.6 When 'Android Recovery' is shown press the Volume Up button. This should invoke the CWM recovery menu. If that works, then congratulations for reaching this far .
Here is a potential pitfall. If you are unable to enter CWM *before* the device boots into Honeycomb, then the newly installed recovery image will be overwritten by the system default recovery. There are ways to prevent this (see posts below), but I recommend you to redo step 4 instead of messing with removal of system files. But both methods would probably work. Experiment!
5. Rooting the Xoom
The root zip file is located here
5.1 You need to transfer the ROOT zip file to a working micro SD card. You can do this on a computer or cell phone, but the ROOT zip must be located in the root directory of the SD card.
5.2 Insert the now prepared SD card in the Xoom
5.3 Boot into recovery (as described in 4.3). Navigate using the volume buttons and press the power button to select the active option
5.4 Select 'Install ZIP from sd card'
5.5 Select 'Choose ZIP'
5.6 Navigate to the ROOT zip file with the Volume buttons and select it with the Power button. Confirm that you want to install it.
5.7 Everything should indicate success, so back out to the main CWM menu and reboot the device.
5.8 From Android Market, install the ROM Manager app and start it. If the rooting was successful, then ROM Manager should start without any complaints.
6. Flashing a new kernel that supports SD cards (and maybe more ...)
The kernel that I used is described here http://forum.xda-developers.com/showthread.php?t=978013
The kernel zip file is located here
6.1 This step is identical to 5, but swap the ROOT zip towards the KERNEL zip. For simplicity, you may want to prepare the SD card with both zip files at the same time in step 5.1 ...
Looks great. You just might want to give credit to LandMaster and cam30era, too.
Also is this for just USA or all, cos many people brick there xoom if its just for USA only
okantomi said:
Looks great. You just might want to give credit to LandMaster and cam30era, too.
Click to expand...
Click to collapse
Of course, done
juDGEY2k10 said:
Also is this for just USA or all, cos many people brick there xoom if its just for USA only
Click to expand...
Click to collapse
This is only tested on a US device. OP updated.
Will this wipe all USER data?
Also, is the location of the zipped root file fine? the title says "[BOOT] Wifi-Only Charge Light Off".
I only see one problem, you have recovery before boot.img. If you flash the recovery, without a rooted boot.img and happen to boot into honeycomb, it will erase your recovery and load stock. So you can remove /system/etc/install-recovery.sh and /system/recovery-from-boot.p or flash the boot.img BEFORE rebooting out of recovery.
BrokenPixel said:
Will this wipe all USER data?
Also, is the location of the zipped root file fine? the title says "[BOOT] Wifi-Only Charge Light Off".
Click to expand...
Click to collapse
When you unlock your Xoom, it will wipe all user data.
bwcorvus said:
I only see one problem, you have recovery before boot.img. If you flash the recovery, without a rooted boot.img and happen to boot into honeycomb, it will erase your recovery and load stock. So you can remove /system/etc/install-recovery.sh and /system/recovery-from-boot.p or flash the boot.img BEFORE rebooting out of recovery.
Click to expand...
Click to collapse
You're right. I rooted 1st and flashed CWR later. I then used brd's method to update to 3.1, re-root and flash the new bootloader and kernel. So there is a step missing after Step 3. I'm sorry, I don't remember exactly how to do this from HC 3.1. (meaning what files to use) as I was on HC 3.0 at the time.
BrokenPixel said:
Will this wipe all USER data?
Also, is the location of the zipped root file fine? the title says "[BOOT] Wifi-Only Charge Light Off".
Click to expand...
Click to collapse
Yes it will. Read 3.4 again, it will do factory reset.
The root file may vary from case to case, but the procedure is the same AFAIK. I used the one that "charge light off"... There are probably others too.
bwcorvus said:
I only see one problem, you have recovery before boot.img. If you flash the recovery, without a rooted boot.img and happen to boot into honeycomb, it will erase your recovery and load stock. So you can remove /system/etc/install-recovery.sh and /system/recovery-from-boot.p or flash the boot.img BEFORE rebooting out of recovery.
Click to expand...
Click to collapse
This is true, and I will update the OP to reflect that.
So has anyone followed this guide successfully yet? I don't really want to be the first...
yordikins said:
So has anyone followed this guide successfully yet? I don't really want to be the first...
Click to expand...
Click to collapse
Hi
I did!. And you know that someone gotta be first (actually second). Why not take the credit?
pingvinen said:
This is true, and I will update the OP to reflect that.
Click to expand...
Click to collapse
So I'm guessing the OP has been updated? I think I'm ready to dive in
Sent from my Xoom using XDA Premium App
Abracastabya said:
So I'm guessing the OP has been updated? I think I'm ready to dive in
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
Instructions are good to go. Just make sure that you don't reboot after flashing recovery, and before flashing boot image. If you do, by mistake, no harm done. You will just have to flash recovery again.
cam30era said:
Instructions are good to go. Just make sure that you don't reboot after flashing recovery, and before flashing boot image. If you do, by mistake, no harm done. You will just have to flash recovery again.
Click to expand...
Click to collapse
Sounds good and thanks B-)
Sent from my Xoom using XDA Premium App
Tnx . Very help full .
I don't know but ROM Manager just isn't budging showing any signs of root... or Superuser (+Elite)... or MarketEnabler...
I don't know, I'm kinda lost here. Let me retry (for the tenth time).
rmcsc said:
I don't know but ROM Manager just isn't budging showing any signs of root... or Superuser (+Elite)... or MarketEnabler...
I don't know, I'm kinda lost here. Let me retry (for the tenth time).
Click to expand...
Click to collapse
Try again, and remember that timing (3 seconds) are key to success ...
I'll retry being more precise. I do get into Recovery and I flash the file mentioned. It seems it flashes correctly but when I boot into the OS, there's no signs of root anywhere.
I'll update in a few. Thanks!
Sent from my T-Mobile G2 using Tapatalk
Easiest guide to flash a custom ROM and custom kernel
Lets accept it,we all have been here,confused what should do after i root/boot unlock
we think i know enough so lets get this going but then, we get stuck in the splash/welcome screen and we think **** this was such a bad idea
SO i created this thread for anyone who ever is confused,lost,seeking help.
IF YOU FIND THIS THREAD HELPFUL, BE SURE TO RECOMMEND IT TO OTHERS AND PRESS THE THANKS BUTTON :d
Thread Contents
1.Common terms/Android Slangs
2.Basic Requirements
3.Download links for Recovery Images for PRIMO U/ PRIMO C]
4.How To flash recovery
5.FAST BOOT FILES(download links) : HTC ONE V DRIVER (DOWLOAD LINKS)
6.How To Back Up Your Current Rom
7.Installing Your ROM
8.Choose Your Kernel(download links)
9.Flashing The Kernel[windows]
*Flashing The Kernel[MAC]
10.people who have already flashed a ROM and are confused how to upgrade it
11.Upgrading KERNEL
12.Stuck in Bootloops, Cant Pass the HTC welcome Screen
13.Some tips from me
Click to expand...
Click to collapse
Hope u have successfully rooted and boot unlocked
Common Terms/Android Slangs
a small guide on some of the android terms my Diablo67
Bootloader:This small program's only job is to load other data and programs which are then executed from RAM.Often, multiple-stage boot loaders are used, during which several programs of increasing complexity load one after the other in a process of chain loading.
Fastboot:A diagnostic protocol used primarily to modify the flash filesystem in Android smartphones from another computer over a USB connection. It is part of the Android Debug Bridge library.
Utilizing the Fastboot protocol requires that the device be started in a boot loader or Second Program Loader mode in which only the most basic hardware initialization is performed. After enabling the protocol on the device itself it will accept any command sent to it over USB via a command line. Some of most commonly used fastboot commands include:
•flash - Overwrites a partition in flash with a binary image stored on the host computer.
•erase - Erases a partition in flash.
•reboot - Reboots the device into the either the main operating system or the system recovery partition.
•devices - Displays a list of all devices (with Serial #) connected to the host computer.
Flashing:The ROM memory used in smartphones and tablets etc. is often same as flash memory found in SD cards and USB flash drives, simply optimized for better speed and performance while running the operating system.
Kernel:A kernel is a layer of code that allows the OS and applications to interface with your phone's hardware. The degree in which you can access your phone's hardware features depends on the quality of code in the kernel. The homebrew (rooting) community for HTC has made several kernel code improvements that give us additional features from our hardware that the stock kernel does not. When you flash a custom ROM, you automatically get a kernel. But you can also flash a standalone kernel ROM on top of the existing one, effectively overwriting it. These days, the difference in custom kernels is less about new features and more about alternate configurations. Choosing a custom kernel is basically choosing one that works best with your ROM.
Nandroid:To backup the current running rom.
Recovery Mode:A small separate operating mode you can boot your device into, used for device administration. Two popular custom recovery modes are Amon Ra and Clockwork.
Basic Requirements
1.A Boot-unlocked and Rooted HTC One V
2.Charge it till above 75% battery
2.A PC(this guide is for now only for windows)
3.usb cable
4.HTC driver download here or HTC SYNC
5.FastBoot Files[ click here>>> download them and put in a folder in c drive ]
> example c:\fastboot or c:\android
6.A recovery image(for image scroll down)
7.A Rom(thats ur choice)
8.boot image(scroll down)
9.put the rom(.zip file) in sd card
Here Are The Recovery Images
Recovery Images[PRIMO U/GSM]
1. CWM 6 by Lloir
2. TWRP 2.6.0 <<Ill Recommend [very user friendly]
3. CWM v5 Touch Recovery
Recovery Images[PRIMO C/CDMA
1. [VM/PRIMOC][RECOVERY] CWM Recovery
2. [VM/PRIMOC][RECOVERY] TWRP2 Recovery
3. [RECOVERY] [PRIMOC/CDMA] CWM 6.0.1.5
How To flash recovery
HOPE U HAVE THE FAST BOOT FILES
[IF NOT]
click here download them and put in a folder in c drive
example c:\fastboot)
>>Now enter Fast boot(power button +volume DOWN(for 15 + sec))<<<
u might have arrived at Hboot boot mode>>> now move up down by pressing the volume buttons and select fastbootwith the power button
Flash it via cmd(command prompt)
Enter these commands
Code:
[B][COLOR="Red"]fastboot flash recovery recovery.img
[/COLOR][/B]
How To Back Up Your Current Rom
(must for first time flashers)(nand=backup of current ROM)
1. Once the CWM/TWRP recovery installed:
Now enter Fast boot(power button +volume DOWN(for 15 + sec))
now move up down by pressing the volume buttons and select fastbootwith the power button
2. Once you are in the RECOVERY menu:
click backup and restore
click backup
the backup process is running. It will be a max 20 minutes to complete.
(optional step just to be sure)
3. once complete, check whether the backup is successful
click backup and restore
click restore
you will see your backup files, for example 2012-11-27 11-7
it should complete with in a span of time
4.Now if that is over go back to the previous menu
use the back button
click reboot system now to boot your device
Installing Your ROM
5.just do a factory reset and wipe cache, then click on install from sd card
6.flash it(the ROM in ur sd card shud be in a .zip format)
7.NOW.DON'T REBOOT UR PHONE GO TO FAST BOOT MODE (VOLUME DOWN+ POWER BUTTON)(or there will be a option to reboot into bootloader)
Choose Your Kernel
9.download whichever kernel u want
[CDMA/PRIMO C]
SuperSick kernel Click ME
SICK kernel PRIMO C/CDMA click here
[GSM/PRIMO U]
SuperSick kernel Click ME
SICK kernel CLICK here
TITANIUM KISS kernel SENSE users CLICK here
HELLBOY kernel FOR AOSP based ROMS(cm9/cm10/AOKP/PA)USE THE LATEST ONE FOR 4.2.2 >click<
Flashing The Kernel[windows]
8.HOPE U HAVE THE FAST BOOT FILES (if not click here download them and put in a folder in c drive)
rename it boot.img and put it in the folder as the fastboot files
GO TO FAST BOOT MODE (VOLUME DOWN+ POWER BUTTON)(or there will be a option to reboot in recovery)
10.flash it via CMD
Enter these commands
Code:
11.[B][COLOR="Red"]Fastboot flash boot boot.img [/COLOR][/B]
12.[B][COLOR="Red"]fastboot reboot[/COLOR][/B]
Flashing The Kernel[MAC] by kalaker
kalaker said:
Go developer.android.com and download the SDK & move it to your home directory ("~" or /Users/<username>)
Go to <sdk-location>/tools and launch "Android"
Download the platform tools
Open terminal
Open Finder to <sdk-location>/platform-tools
In terminal, type "sudo cp"; drag adb from the Finder window into the Terminal window; type "/usr/bin/"; hit enter
Enter your password
Repeat the above three steps, but drag "fastboot" instead of "adb"
Close terminal
Open terminal (it sounds weird, but just do it)
Now, and forever, do this to install a kernel:
Download kernel
Connect phone to computer
Make sure USB Debugging is enabled (Settings>Development>USB Debugging)
In terminal, type "adb reboot bootloader"
In terminal, type "fastboot flash boot"; drag in the kernel from finder; hit enter
Examples:
Code:
sudo cp /Users/Username/android-sdk-mac/platform-tools/adb /usr/bin/
sudo cp /Users/Username/android-sdk-mac/platform-tools/adb /usr/bin/
adb reboot recovery
fastboot flash boot /Users/Username/Downloads/boot.img
Click to expand...
Click to collapse
13.enjoy
First boot takes some time have patience......be sure to ask questions or doubts
Ok For people who have already flashed a ROM and are confused how to upgrade it
Upgrading ROM
1.download your needed ROM
2.put in SD card
3.boot into recovery
4.no need to wipe everything,wipe caches(and if the dev says to full wipe do it)
5. (Unless u come from a different ROM eg.From Amazing Sense To CM10, in this case a factory reset i needed
6.flash the ROM
7.reboot
8.flash GAPPS
9. enjoy
Upgrading KERNEL
1.boot in bootloader
2.do the required steps(as mentioned above)
3.wipe caches
5.enjoy
Stuck in Bootloops, Cant Pass the HTC welcome Screen
ok, calm down, everyone has this problem while flashing, i get it so many times, they can cause by the following reasons
bad flash
wrong rom
you forgot to flash the kernel
wrong kernel
messed up the order in flashing
ok,
1.Bad flash-this occurs if the .zip file is corrupted
solution:= re flash the ROM, if still no, download the file again and try
2.wrong ROM- u may have downloaded a ROM that is not for ur device or a ROM which is of not ur description
for example u might me a PRIMO C device/CDMA and u downloaded a PRIMO U/GSM ROM
3.Wrong Kernel-Kernel is the link between ur software and hardware, if u flash the wrong one like the case mentioned above , download the correct one and re flash
4.[ FLASHING YOUR KERNEL SHOULD BE THE LAST STEP][UNLESS U HAVE A S-OFF DEVICE]
Ok Some Tips Which May Help You
1.Battery Draining fast?
-----get an app called BetterBatteryStats,run it over night.then next morning open it and check whats waking your device
Click to expand...
Click to collapse
2.Can i use scripts?
-----Your wish, the rom works perfect,running a script can ruin it in some cases(chill,even i run some)
Click to expand...
Click to collapse
3.Good/best/recommended ROMS?
-----all roms are good in their own way, but i can give u a list of recently updated roms
-----1.sphongle(4.2.2) 2.Slimbean 3.Cm10
Click to expand...
Click to collapse
will add more cheers
Hope this helps u
another get thanks quick scheme thread?
Sent from my One V
paarthdesai said:
another get thanks quick scheme thread?
Sent from my One V
Click to expand...
Click to collapse
LOL :silly:
no i plan to help!
My works
You call that work ??
Those are just tips
Y do u have a problem with that
Sent from my One V
No but that work word is pissing me off ..... For using it in a inappropriate place
donhashem.dh said:
No but that work word is pissing me off ..... For using it in a inappropriate place
Click to expand...
Click to collapse
Don't read it
Sent from my One V
to clarify, step 6: "flash" should be edited to say " install ROM from zip" to avoid the "flash" misconception associate with flashing kernels:good:
more detailed work should be there.. like you said install cwm or twrp.... give a link to where they are embedded in the words will be good...
and the above goes for the flashing rom part also...embed the link to the dev section
make it easy and tidy instead of all those ugly looking clutters you did
Sent from my One V
will work into that!
did it!
cybervibin said:
flash it via cmd
Enter these commands
Fastboot flash recovery recovery.img
Click to expand...
Click to collapse
You forgot to mention to boot into fastboot. No offence, but it has to be much better written. Its not noob friendly at all.
m sorry abt that! guess missed it! wrote the thread throygh my phone!
any other problems i corrected the one u said!
cybervibin said:
m sorry abt that! guess missed it! wrote the thread throygh my phone!
any other problems i corrected the one u said!
Click to expand...
Click to collapse
Yeah, you could try creatign sub sections, like thinigs to have before swap, then steps after that. Eg in step 1 you say
>>Now enter Fast boot(power button +volume DOWN(for 15 + sec))<<<
and
1.Flash CWM 6 by lloir
or TWRP 2.3.1.0 ill recommend TWRP
>>PRIMO C /CDMA click here<<
To flash recovery HOPE U HAVE THE FAST BOOT FILES(IF NOT click here download them and put in a folder in c drive
example c:\fastboot
Click to expand...
Click to collapse
First you mention the ROM, then out of the blue you mention recovery. ROM should be introduced after a nand backup. You should also explain in short what a nand backup is. A sentence with an analogy is sufficient. I am a software developer and I would like to share a rule that I follow: If you need to add a comment in your code, that means the code is not readable. In the same way, when you mention something in bracket, it itself means that the sentence is no clear, and need rephrasing and rewording.
Dont get me wrong, I am not trying to insult or berate or anything, but I got it read by a friend who wants to flash his One V, and he got back to me with more questions than the guide answered. There a some step holes in the guide, and you have to write is as if you are a noob
Lastly, thanks a lot, this particular guide and your answers have been really helpful to me and the community.
Cheers!
now ill consider that! hard being a noob!
thetuxracer said:
If you need to add a comment in your code, that means the code is not readable. In the same way, when you mention something in bracket, it itself means that the sentence is no clear, and need rephrasing and rewording.
Click to expand...
Click to collapse
Nice, I liked this!
Sent from my One V using xda app-developers app
soham_sss said:
Nice, I liked this!
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
thetuxracer said:
Yeah, you could try creatign sub sections, like thinigs to have before swap, then steps after that. Eg in step 1 you say
First you mention the ROM, then out of the blue you mention recovery. ROM should be introduced after a nand backup. You should also explain in short what a nand backup is. A sentence with an analogy is sufficient. I am a software developer and I would like to share a rule that I follow: If you need to add a comment in your code, that means the code is not readable. In the same way, when you mention something in bracket, it itself means that the sentence is no clear, and need rephrasing and rewording.
Dont get me wrong, I am not trying to insult or berate or anything, but I got it read by a friend who wants to flash his One V, and he got back to me with more questions than the guide answered. There a some step holes in the guide, and you have to write is as if you are a noob
Lastly, thanks a lot, this particular guide and your answers have been really helpful to me and the community.
Cheers!
Click to expand...
Click to collapse
how about now, noob friendly enough?
Yup, pretty cool! If there was a way to thank again..
ty!! please keep the recomendations coming!
Ok firstly this may seem a bit confusing, I am copying this from a PM i sent to @wedgess
Hi, I am wondering if you would be able to make a bootable recovery image with TWRP as i have no idea how to do it and i can only find CWM ones which requires signature for "--update_package="
I don't want a kernel and i don't want a cwm image but i want just simple a TWRP recovery.img which is bootable like http://forum.xda-developers.com/showthread.php?t=1493996 but TWRP instead
Your kernel's work fine but i need it to boot a recovery.img then flash the new rom via "--update_package=" and then reboot device.
For more information check http://forum.xda-developers.com/showthread.php?t=2391169
I hope you can help, Thanks.
-------------------------------
TWRP works great with both the last 2 options so i need to some how create a bootable recovery img based on TWRP but i don't have a clue about kernel development... Could i maybe replace ramdisk with existing bootable recovery or something?
-------------------------------
So to put it simply, I need to switch out CWM on this recovery.img and put TWRP on it (The reasons for this are complicated to explain but i would be extremely thankful if any one could help and credit will be giviven)
So please can any one help me Thanks.
Sorry I didn't reply to your final PM as I said due to real life and limited time I cannot do it for you, But happy to help assisting you if needed. Championswimmer has a tutuorial on what to change in the device tree for TWRP. Search function is down ATM so I can't link you to the thread.
wedgess said:
Sorry I didn't reply to your final PM as I said due to real life and limited time I cannot do it for you, But happy to help assisting you if needed. Championswimmer has a tutuorial on what to change in the device tree for TWRP. Search function is down ATM so I can't link you to the thread.
Click to expand...
Click to collapse
Yeah no worries, Decided to ask any one else, As i really don't have the time to do this aswell as all the other stuff im doing. And it will take some one with experience a lot less time.
I tried switching out the /sbin folder but it didn't work and i didn't expect it to
I am hoping to find some 1 with a linux enviroment all sorted as i don't have a clue when it comes to kernels. surely there is a simple way to switch out a prebuiilt CWM Recovery with a TWRP recovery? Do you know what files TWRP and CWM use?
Thanks.
Altenatively any ideas on what needs to be changed to boot it to recovery always? if so i could modify a existing TWRP kernel (yours for example) and then force it to recovery.
EDIT
I assume you meant this guide?
PORT TO STOCK/ICS/YOU-FAVOURITE-KERNEL
A boot.img consists of the kernel image and the ramdisk (additionally and optionally RPM.bin and commandline). If you want to use TWRP for some other kernel, you have to do this
1. decompile this boot.img (for 2011 models it's a true boot.img, for 2012 models, it's actually a kernel.elf file renamed to boot.img, so you have to decompile accourdingly. you can use my kernel kitchen to do the same)
2. replace the kernel zImage with the one from the kernel you want to port to
3. replace /sbin/ramdisk.cpio with the "UNCOMPRESSED" ramdisk of the kernel you want to port this to. (usually ramdisk is compressed with gzip i.e. ramdisk.cpio.gz. you need to uncompressed ramdisk image i.e. ramdisk.cpio)
4. do not touch anyother thing
5. pack it up into a boot.img (for 2011) or kernel.elf (for 2012) and fastboot it
@wedgess ok so i got it working it now auto boots to TWRP but ADB isn't working, Any ideas?
Thanks so much i got it all working that guide helped
I am curious of what you are trying to do...
As i understand you want:
-flash (only) twrp recovery in fastboot mode
-reboot to recovery and flash rom from pc (adb sideload maybe?)
-reboot to fastboot again to flash kernel
-reboot
If i understand correctly you want to flash ROM (and kernel) from PC side, not dong it from phone?
Bakisha said:
I am curious of what you are trying to do...
As i understand you want:
-flash (only) twrp recovery in fastboot mode
-reboot to recovery and flash rom from pc (adb sideload maybe?)
-reboot to fastboot again to flash kernel
-reboot
If i understand correctly you want to flash ROM (and kernel) from PC side, not dong it from phone?
Click to expand...
Click to collapse
ok this is what happens
1. Download rom and kernel from my kitchen via helper application on windows
2. verifiy md5's
3. fastboot fllash new kernel
4. fastboot boot "recovery.img"
5. once in the new bootable recovery i created/edited, send adb command "adb shell" > recovery --update_package=ROM
6. wait for rom to install, reboot
7. DONE! new rom and kernel flashed
All done automagically and without any user interaction other than picking the rom.
Check post 1 and 2 for more info - http://forum.xda-developers.com/showthread.php?p=46111684
fma965 said:
ok this is what happens
1. Download rom and kernel from my kitchen via helper application on windows
2. verifiy md5's
3. fastboot fllash new kernel
4. fastboot boot "recovery.img"
5. once in the new bootable recovery i created/edited, send adb command "adb shell" > recovery --update_package=ROM
6. wait for rom to install, reboot
7. DONE! new rom and kernel flashed
All done automagically and without any user interaction other than picking the rom.
Check post 1 and 2 for more info - http://forum.xda-developers.com/showthread.php?p=46111684
Click to expand...
Click to collapse
One word: WOW :good:
Not just you have ideas what you can do, but knowledge to do it. You have my respect man :highfive:
i'll check that app ASAP
Bakisha said:
One word: WOW :good:
Not just you have ideas what you can do, but knowledge to do it. You have my respect man :highfive:
i'll check that app ASAP
Click to expand...
Click to collapse
Thanks current released version is quite buggy but new version coming soon
Any way since this problem is now solved, I will close the thread. if you want to discuss this then post on my kitchen thread or pm me
Disclaimer
I (alvinhochun) am NOT responsible for events including but not limited to bricking any electronic or non-electronic devices, losing data, fever, heart attack, thermonuclear war, or the cooling down of the Sun, either caused by or not caused by downloading or installing this mod.
You are expected to back up all your data by your own means before installing this mod.
You should always only follow tested instructions and install only tested ROMs with a tested setup, or else you should have extended knowledge in the inner workings of Android, Linux and MultiROM Xperia.
Notice
This is an unofficial port of MultiROM.
Before anything else, I would like to say thanks to @Tasssadar who developed the original MultiROM (thread for Nexus 7). Without him, this mod wouldn't be here.
Unless otherwise specified, anything that is designed for just "MultiROM" (without "Xperia" after it) will not work for this because there are some operational differences between "MultiROM" (original) and "MultiROM Xperia" (this mod).
Introduction
Perhaps you want to try the new CyanogenMod 11 ROM, but don't want to erase your phone to flash it because you need to keep your stock ROM and all your data, and don't want to bother backing up and restoring every single time? Don't worry! MultiROM Xperia can help you.
MultiROM Xperia is a mod which lets you install alternative Android ROMs to your internal memory, microSD cards or USB storage connected via OTG and boot them. Together with a kernel with kexec-hardboot patch, you can even boot ROMs with kernels different from the one you've installed!
The idea is that you can install ROMs to external storage spaces via a modified TWRP recovery, but it is not ready yet.
This mod is mostly ready for testing, but since the installer is not ready yet, I've uploaded the boot image (to be flashed with `fastboot flash boot`) and the files of unofficial CM11 Beta 1 (Thanks to @PecanCM) to be placed on the microSD card or USB device in the form of a zip archive. At the time being, they can only be used when you have stock 15.1.C.2.8 firmware (Android 4.1.2) installed.
Warning
This mod is basically one giant hack. Neither the ROMs nor the device itself is designed with multiboot in mind so there is no absolute guarantee that it will work properly. Technically, installing it only modifies the boot partition (sometimes casually called the kernel) which is the same thing that custom kernel is installed to, and in the worse case you only need to (re-)flash a stock or custom kernel or flash an ftf to remove MultiROM Xperia, but the MultiROM booting mechanism is hacky and is not guaranteed to always work.
Always make backup, frequently, like you should do even if not using MultiROM Xperia.
Features
Boot any number of alternative Android ROMs installed onto microSD cards and USB storage
Support alternative "internal storages": For every ROMs (including internal ROM), you can have multiple separated "profiles", which is represented by an entire "emulated" /data partition. Technically, the profiles can also support encryption.
Installation
This instruction is reviewed on 2014-01-09.
Prerequisite: You need to unlock your bootloader and be on stock 15.1.C.2.8 firmware (Android 4.1.2),
Download multirom-boot-********-c1905-test.img and multirom-cm11beta1-********-c1905-test.zip.
Use fastboot to flash the boot image:
Code:
fastboot flash boot multirom-boot-********-c1905-test.img
Extract multirom-cm11beta1-********-c1905-test.zip directly to the root of a microSD Card or USB flash drive.
Currently, these filesystem formats are supported: vfat (FAT16/FAT32), ext2, ext3, ext4.
******** represents the date of the release.
Usage
To boot a ROM (including internal stock ROM), insert the microSD card or connect the USB flash drive and switch on the phone, then select the corresponding ROM and press "boot". (Note, the first boot of an external ROM may take very long depending on the speed of the storage device.)
To enter CWM recovery, switch on the phone, select "Misc" tab and press "Recovery". Alternatively, you can execute `adb reboot recovery`. The included CWM recovery is the same as the one in unofficial CM11 Alpha 2 (Thanks to @PecanCM).
Note: Do NOT attempt to use any existing recovery to flash any ROMs unless you don't want to keep MultiROM Xperia and your existing data!
[/LIST]
Downloads
2013-01-08 / 2013-01-19
multirom-boot-20140107-c1905-test.img (10 MiB)
multirom-boot-20140108-c1905-test.img (10 MiB)
multirom-cm11alpha2-20140107-c1905-test.zip (173 MiB, 1 GiB extracted)
multirom-cm11beta1-20140119-c1905-test.zip (202 MiB, 1.2 GiB extracted)
Screenshots
See Screenshots
Source code
MultiROM Xperia:
https://github.com/alvinhochun/multirom-nicki
Device tree (used to build MultiROM Xperia):
https://github.com/alvinhochun/cyanogenmod_device_sony_nicki/tree/multirom
Kexec-hardboot patch:
See http://forum.xda-developers.com/showthread.php?t=2568151
Stock kernel with kexec-hardboot patch:
https://github.com/alvinhochun/sony-xperia-m-kernel
CM11 kernel:
See original unofficial CM11 Beta 1 thread
XDA:DevDB Information
MultiROM Xperia M, Tool/Utility for the Sony Xperia M
Contributors
alvinhochun, Tasssadar
Version Information
Status: Testing
Created 2014-01-06
Last Updated 2014-11-04
Changelog and technical information
Changelog
2014-01-08
Added option to update/rescan for ROMs
2014-01-07
First public test release
Technical information
It works by extracting the boot ramdisk to root and patching init.rc files after boot selection.
More to be added
Changes from the original MultiROM
This port is based on the original MultiROM by @Tasssadar, which is available for multiple devices including the Nexus 4, 5 and 7. However, since his original port did not account for supporting external SD cards, and also didn't handle most Xperia devices without a recovery partition, I've rewritten some part of his original MultiROM to handle these things.
Differences include:
All binaries are placed in the ramdisk altogether instead of the internal storage.
MultiROM Xperia does not mount the partitions before starting the real Android init. Instead, it generates a script and patches some files (including init.rc) to trick the target system to mount filesystem images (loop mounting loop devices).
One ROM can contain multiple user profiles (i.e. data, cache and persist).
The code to boot generic (non-Android) Linux ROMs is removed due to heavy rewrite of parts from the original MultiROM.
It currently only support using partition filesystem images, neither symlink nor bind mount is supported.
Reserved
Working perfectly.
Booting time(from sdcard) is okay I would say.
Now we just need the modified TWRP. Hope you could get it for us too.
Thanks
aweosomeabhijeet said:
Working perfectly.
Booting time(from sdcard) is okay I would say.
Now we just need the modified TWRP. Hope you could get it for us too.
Thanks
Click to expand...
Click to collapse
how did u get it work?
which model c1904 or c1905?
which sdcard?
Till now I've discovered a few bugs in this test release:
Sometimes, microSD card is not detected because the initialization is too long.
This varies between cards. A theory is that SDHC might take a longer time to initialize, which happens after MultiROM has scanned for partitions.
You can try rebooting a few times and if, by any chance, the card initialized right in time, you will be able to boot the external ROM.
I have a few possible solutions for this, and I will update to you when I've implemented a working solution.
USB OTG storage devices may not be detected properly. Needs investigation...
Thanks to @ansebovi for testing and informing about these.
i followed all the instructions, flashing the boot.img (i renamed the boot file to multirom.img) and move the files to my sdcard, why when i reboot, its just rebooting normally (no rom select screen) ?
EDIT: Rebooted again and it worked.
EDIT AGAIN: Is there any way to flash gapps? or just flash normally with cwm?
ansebovi said:
how did u get it work?
which model c1904 or c1905?
which sdcard?
Click to expand...
Click to collapse
Flashed boot.img using fastboot.
Extracted ROM in the root of sdcard.
Rebooted. Selected sdcard>cm11>boot. And it booted
Model C1904
SanDisk micro sd 8GiB class4
Sent from my C1904 using xda app-developers app
I've added an option in the "Misc" tab to rescan for ROMs as a temporary measure. Flash the new boot image to get it. Please refer to the first post for download.
Sent from my Sony Xperia M (C1905)
GedeWK said:
i followed all the instructions, flashing the boot.img (i renamed the boot file to multirom.img) and move the files to my sdcard, why when i reboot, its just rebooting normally (no rom select screen) ?
EDIT: Rebooted again and it worked.
EDIT AGAIN: Is there any way to flash gapps? or just flash normally with cwm?
Click to expand...
Click to collapse
Well, how to install gapps to the ROM? I need the play store
to do the tutorial I have to have the bootloader unlock?
alvinhochun said:
Disclaimer
I (alvinhochun) am NOT responsible for events including but not limited to bricking any electronic or non-electronic devices, losing data, fever, heart attack, thermonuclear war, or the cooling down of the Sun, either caused by or not caused by downloading or installing this mod.
You are expected to back up all your data by your own means before installing this mod.
You should always only follow tested instructions and install only tested ROMs with a tested setup, or else you should have extended knowledge in the inner workings of Android, Linux and MultiROM Xperia.
Notice
This is an unofficial port of MultiROM.
Before anything else, I would like to say thanks to @Tasssadar who developed the original MultiROM (thread for Nexus 7). Without him, this mod wouldn't be here.
Unless otherwise specified, anything that is designed for just "MultiROM" (without "Xperia" after it) will not work for this because there are some operational differences between "MultiROM" (original) and "MultiROM Xperia" (this mod).
Introduction
Perhaps you want to try the new CyanogenMod 11 ROM, but don't want to erase your phone to flash it because you need to keep your stock ROM and all your data, and don't want to bother backing up and restoring every single time? Don't worry! MultiROM Xperia can help you.
MultiROM Xperia is a mod which lets you install alternative Android ROMs to your internal memory, microSD cards or USB storage connected via OTG and boot them. Together with a kernel with kexec-hardboot patch, you can even boot ROMs with kernels different from the one you've installed!
The idea is that you can install ROMs to external storage spaces via a modified TWRP recovery, but it is not ready yet.
This mod is mostly ready for testing, but since the installer is not ready yet, I've uploaded the boot image (to be flashed with `fastboot flash boot`) and the files of unofficial CM11 Alpha 2 (Thanks to @PecanCM) to be placed on the microSD card or USB device in the form of a zip archive. At the time being, they can only be used when you have stock 15.1.C.2.8 firmware (Android 4.1.2) installed.
Warning
This mod is basically one giant hack. Neither the ROMs nor the device itself is designed with multiboot in mind so there is no absolute guarantee that it will work properly. Technically, installing it only modifies the boot partition (sometimes casually called the kernel) which is the same thing that custom kernel is installed to, and in the worse case you only need to (re-)flash a stock or custom kernel or flash an ftf to remove MultiROM Xperia, but the MultiROM booting mechanism is hacky and is not guaranteed to always work.
Always make backup, frequently, like you should do even if not using MultiROM Xperia.
Features
Boot any number of alternative Android ROMs installed onto microSD cards and USB storage
Support alternative "internal storages": For every ROMs (including internal ROM), you can have multiple separated "profiles", which is represented by an entire "emulated" /data partition. Technically, the profiles can also support encryption.
Installation
This instruction is reviewed on 2014-01-09.
Prerequisite: You need to unlock your bootloader and be on stock 15.1.C.2.8 firmware (Android 4.1.2),
Download multirom-boot-********-c1905-test.img and multirom-cm11alpha2-********-c1905-test.zip.
Use fastboot to flash the boot image:
Code:
fastboot flash boot multirom-boot-********-c1905-test.img
Extract multirom-cm11alpha2-********-c1905-test.zip directly to the root of a microSD Card or USB flash drive.
Currently, these filesystem formats are supported: vfat (FAT16/FAT32), ext2, ext3, ext4.
******** represents the date of the release.
Usage
To boot a ROM (including internal stock ROM), insert the microSD card or connect the USB flash drive and switch on the phone, then select the corresponding ROM and press "boot". (Note, the first boot of an external ROM may take very long depending on the speed of the storage device.)
To enter CWM recovery, switch on the phone, select "Misc" tab and press "Recovery". Alternatively, you can execute `adb reboot recovery`. The included CWM recovery is the same as the one in unofficial CM11 Alpha 2 (Thanks to @PecanCM).
Note: Do NOT attempt to use any existing recovery to flash any ROMs unless you don't want to keep MultiROM Xperia and your existing data!
[/LIST]
Downloads
2013-01-07
multirom-boot-20140107-c1905-test.img (10 MiB)
multirom-boot-20140108-c1905-test.img (10 MiB)
multirom-cm11alpha2-20140107-c1905-test.zip (173 MiB, 1 GiB extracted)
Screenshots
See Screenshots
Source code
MultiROM Xperia:
https://github.com/alvinhochun/multirom-nicki
Device tree:
https://github.com/alvinhochun/cyanogenmod_device_sony_nicki/tree/multirom
Kexec-hardboot patch:
See http://forum.xda-developers.com/showthread.php?t=2568151
Stock kernel with kexec-hardboot patch:
https://github.com/alvinhochun/sony-xperia-m-kernel
CM11 kernel:
See original unofficial CM11 Alpha 2 thread
XDA:DevDB Information
MultiROM Xperia M, a Tool/Utility for the Sony Xperia M
Contributors
alvinhochun, Tasssadar
Version Information
Status: Testing
Created 2014-01-06
Last Updated 2014-01-09
Click to expand...
Click to collapse
to do the tutorial I have to have the bootloader unlock?...because i have the bootloader locked and i like to introduce in cwm.
daruto80 said:
to do the tutorial I have to have the bootloader unlock?...because i have the bootloader locked and i like to introduce in cwm.
Click to expand...
Click to collapse
u should not quote op on any thread...edit ur post..remove quote
and yes u need an unlocked bootloader
since it is called multirom xperia , can't it be ported to xperia z ? and other xperias , or it is made exclusively for xperia m ?
elias234 said:
since it is called multirom xperia , can't it be ported to xperia z ? and other xperias , or it is made exclusively for xperia m ?
Click to expand...
Click to collapse
It's only for Xperia M at the moment since it is not completed yet.
If anyone feels like porting it to other devices I will surely appreciate, but for me I will wait till most of it is ready before porting to other devices.
Uploaded test package with unofficial CM11 Beta 1. Just extract it to SD card, just like the previous test release.
Although I don't expect daily usage on a pre-alpha test release, if you want to keep your data in CM11 Alpha 1, copy the `default` directory from cm11-alpha2 and replace the one in cm11-beta1.
Just a little update, I am coding as I type this, but you cannot expect the alpha release of MultiROM Xperia to be here in a short time 'cause there is a lot to do. You can still try the test packages at the moment.
Is the testing still in process? Because I can't wait to try this out. I hope it would be done sooner...
Booting all the 4 ROM(s)!
Thanks Alvin :highfive:
elias234 said:
since it is called multirom xperia , can't it be ported to xperia z ? and other xperias , or it is made exclusively for xperia m ?
Click to expand...
Click to collapse
XZ already have multi rom elias it has been done by mithun46
rebelos said:
XZ already have multi rom elias it has been done by mithun46
Click to expand...
Click to collapse
it is out dated , and it needs an app , says always unsupported rom , mithun stopped the developing for it ( he never replies on his thread nor on any question about the multirom )
aweosomeabhijeet said:
Thanks Alvin :highfive:
Click to expand...
Click to collapse
How were you able to get it to read ROMs? I'm currently having trouble and have tried almost everything. I compared the test zip and the FXP311 zip and found out that they are completely different.
Disclaimer:
Code:
Your warranty is now void.
Flashing this recovery assumes you have a sufficient technical understanding
of your device. Before continuing, you should be aware of the risks involved
and have an idea of what to do if something goes wrong. I am not responsible
for any bricked or otherwise malfunctioning devices.
A while back, bekriebel posted a working CWM image for Glass. Since then, there have been significant firmware changes for Glass that rendered the old recovery image unusable. A lot of people have been asking for an update, so I decided to compile an updated version.
This image is based on the latest stable CM11 sources, and uses the XE18.1 (XRV70D) kernel source found at http://github.com/justindriggers/android_kernel_Google_glass_1 and the device tree at http://github.com/justindriggers/android_device_Google_glass_1
Installation Instructions:
Download the recovery image here (md5sum: 1c0299145ec08efc5a7ec0f87ab7ef24)
Boot into fastboot mode:
Code:
adb reboot bootloader
Flash the image:
Code:
fastboot flash recovery recovery-clockworkmod-20140613-UNOFFICIAL-glass_1.img
Reboot your device:
Code:
fastboot reboot
Finally, you can boot into recovery:
Code:
adb reboot recovery
Usage:
Change the selection with the camera button. Select the current item with the power button.
Let me know if you have any issues, and enjoy.
What are the changes made? Does it add anything new that Glass couldn't do before, does it re-add non-glass input (OTG USB - Bluetooth input)?
Basically, what are the advantages of using this?
ResleyZ said:
What are the changes made? Does it add anything new that Glass couldn't do before, does it re-add non-glass input (OTG USB - Bluetooth input)?
Basically, what are the advantages of using this?
Click to expand...
Click to collapse
This is just the recovery, completely separate from everything inside the Glass operating system. I've personally used it to install Superuser and Xposed onto my device, but it opens the door to many other opportunities. If Google ever decides to make Glass open-source, then we may see some custom roms, which would be flashed using this recovery.
A publicly available recovery image is the first step toward further customization. If you have no need for it at the moment (you aren't a developer), then I wouldn't recommend flashing it.
I know this is old but it does work and even on XE24. I just did a full backup. Took awhile to find where it was stored but found it and pulled it to the computer with adb pull command. Found at:
/mnt/shell/emulated/clockworkmod/backup/ where there were a total of 10 files from the backup.
Just wish I would have had this before losing my working XE23 which at least could still send texts, make calls and a few other things.
ADB seems to have quit working. I had AOSP 5.1.1 on it but things got too slow and decided to put XE24 back on so got that done with fastboot but have not been able to get ADB to work at all. Any ideas?
I flashed to rooted bootloader after adb quit working but no change. Tried flashing the clockworkmod recovery again but still no adb.