Database Users

Lenovo K1 CM10 V2 -Clockwork Mod /Recovery Question

In Clockwork Mod, in build [ROM][JB] CM10 for Ideapad K1 (Big thanks to krook1, it runs great) (I'm running version 2). Whenever I attempt to use any of the features it asks me to install the recovery (which I know I have, and can boot to it) and asks me to choose my device.. Which it then only gives me the ASUS TRANSFORMER as an option.
So, on Version 1 of this build, some time back. I said, what the heck, why not. Let it do its thing,rebooted.. and the system would not ever boot. Just hung at the CM10 boot animation.
Whatever. I used the NVFlash version, got it back up and running. Rebooted in to CWR, and flashed the [ROM]CM10 for Ideapad K1 version 2 CWM version on it. No real loss.
However, Id really rather not have to wipe my device again to go to version 3, or 4.. and I don't want to get stuck at a boot animation again.
Is it normal for the CWM to identify this build as a ASUS TRANSFORMER?
Thanks

Basically ROM manager doesn't support our device directly. Someone ported cwm recovery for our device.
Again if you try using cwm meant for other device it won't work.
I have same issue with my phone.
Sent from my GT-I9003 using xda premium

Thank you for the reply.
I figured it was something along those lines. What doesn't make sense to me is, if Krook1 took the time to make a CWM enabled ROM, then one would assume that in the build process the proper porting/modifications will have taken place. Otherwise why bother?
That said, I have no doubts about XDA's fine developers, the author of this one included in that. Thus it must be something specific to either that build revision (V1 at the time) or something specific to my tablet (possibly the remnant of an earlier flash [is that even possible with NVFlash and the format it does prior to flashing?]). If it is the latter, then what actions might I take to correct it?
I guess, what I am trying to mine out of this thread is has anyone else running this build have the same issue (Does it prompt for the ASUS?) and if so, did it work as intended. I'm just a little gun shy of trying it again now that the tablet is setup. However as aforementioned I would like the ability to use later revisions of this ROM, while reaping the benefits of the paid CWM.
-Cheers.

I see the same time to thing on my k1.
ROM manager will not show us tablet unless the ROM manager creator adds our device to his app.
Again ROM manager is not a required app and can be safely removed. I don't use it at all.
Sent from my GT-I9003 using xda premium

[VIDEO] Idiot's Guide - How to Install CM10 on the HP Touchpad

This is my FINAL VERSION of my Idiots Guide for the HP Touchpad. Now that a stable enough version of CM10 is available, I finally created a guide for you.
Here are links to the files you will need:
CM10 03/04/2012 Build
GAPPS 10/11/2012
ACMEInstaller3
Moboot 3.8
Anything else that you might need, you'll find on http://www.reverendkyle.com

Thanks for the video. It came just in time as I just purchased a used TP that had an older version of android ICS already on it and I wanted to upgrade but seeing as how this is the first device I have sort of inherited already rooted, it is hard to just jump in and know everything that I would have learned from the beginning like i did with my previous phones.
Anyways, I did everything you said except I used the newest AOKP rom. But my tp is still booting to the older version of android that I had on it. Any ideas? Feel free to pm me if you prefer that.

aujbman said:
Thanks for the video. It came just in time as I just purchased a used TP that had an older version of android ICS already on it and I wanted to upgrade but seeing as how this is the first device I have sort of inherited already rooted, it is hard to just jump in and know everything that I would have learned from the beginning like i did with my previous phones.
Anyways, I did everything you said except I used the newest AOKP rom. But my tp is still booting to the older version of android that I had on it. Any ideas? Feel free to pm me if you prefer that.
Click to expand...
Click to collapse
If the AOKP ROM is using a unique uImage file, then you may see two different entries on your moboot screen for two different Android builds.
What does your moboot menu have in it?

Maybe your install failed. Try downloading and flashing it again. If you're trying AOKP JB, you should wipe both /data and dalvik cache to avoid a boot loop!
If using AcmeInstaller3 remember to rename the ROM with ”update-” at the beginning so that it looks like update-AOKPJB_UnOfficial.zip
Sent from my SAMSUNG-SGH-T989 using xda premium

-SGA- said:
Maybe your install failed. Try downloading and flashing it again. If you're trying AOKP JB, you should wipe both /data and dalvik cache to avoid a boot loop!
If using AcmeInstaller3 remember to rename the ROM with ”update-” at the beginning so that it looks like update-AOKPJB_UnOfficial.zip
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
I believe it was the "update-" thing that was keeping it from updating. I followed another video tutorial which provided files that had the "update" in front of them and it worked.
I haven't tried yet but now that it worked will the regular method of wiping and flashing through recovery work? (Like, if I want to try out different JB Roms) Are there any files that need to be in a particular place for the recovery method to work? I tried that method first and it would never take, would always revert back to the original version. Don't know if, because I just jumped in and haven't been here from the beginning, I am just missing a necessary step that is hardly even talked about anymore.

Love your work Rev! Thank you again for everything that you do!
Update went like clockwork, unfortunately I can't seem to get the camera to work (not a terrible loss, but I was sorta excited to see it actually working with this release).

Jubmasterflex said:
Love your work Rev! Thank you again for everything that you do!
Update went like clockwork, unfortunately I can't seem to get the camera to work (not a terrible loss, but I was sorta excited to see it actually working with this release).
Click to expand...
Click to collapse
I can attest to the improved battery life on this cm10 build. Amazingly, it holds battery life when it's sleeping now.

Thank you so much for taking the time in making the video for us. Your instructions are easy to follow, hard for anyone to mess up.
(The hosting site for the files is not working, not sure if you were aware)

Hi, I have CM9 running on my TP. With the latest release, the camera works great. But before updating it to CM10, I'd like to know about the issues currently in this build.
Thanks.

Where does one go when the goo.im site appears down, to get the needed files? Mirror somewhere?

ljderm said:
Where does one go when the goo.im site appears down, to get the needed files? Mirror somewhere?
Click to expand...
Click to collapse
Don't go for external mirrors unless some recognized developer suggests them. Best will be to wait for goo.im to come up again, being a prime site, it won't be down for long.

The goo servers do appear to go down on occasion. They always come back up a bit later.

Problem with installing GAPPS using ACMEInstaller3
Excellent tutorial for an idiot like me. Thanks for again for the guide! Question:
I followed the instructions step by step and was able to get CM10 installed successfully. However, I wasn't able to get GAPPS installed using this method. From researching I understand sometimes there is a problem installing GAPPS through ACMEInstaller3 and one can simply get GAPPS installed through CWM Recovery. However, I would like to use/have TWRP instead so is there a way to get GAPPS installed properly through ACMEInstaller3 and then I can install TWRP through GooManager?
Alternatively, is there a way to install GAPPS without using CWM Recovery?
Or, I guess I can install CWM Recovery first, then install TWRP Recovery, then remove CWM Recovery while keeping TWRP and not go back to the stock Recovery? I tried to search the forums and wasn't able to find instructions on removing CWM Recovery WHILE still keeping CM10 and not go back to the Stock recovery.
Any help would be much appreciated. Thanks in advance for your help.

@reverendkjr - appreciate your videos. they're awesome. definitely helped me (and several other friends) many times and saved a ton of time. super easy to follow.

Yes you can install TWRP normally, flash gapps in CWM then install goomanager app, open and click the 3 dot menu and install custom recovery script then it will install it
Now using a root file manager go to the directory called boot and delete uimage.cwm.img (this is from memory but still should be correct
Sent from my cm_tenderloin using XDA Premium HD app

waynekirby said:
Yes you can install TWRP normally, flash gapps in CWM then install goomanager app, open and click the 3 dot menu and install custom recovery script then it will install it
Now using a root file manager go to the directory called boot and delete uimage.cwm.img (this is from memory but still should be correct
Sent from my cm_tenderloin using XDA Premium HD app
Click to expand...
Click to collapse
Dumb question. I had dual boot installed with moboot and one day my dumbarse clicked erase SD card.well it did...EVERYTHING accept twrp. I successfully reinstalled webos and installed preware. Its actually pretty cool.its like a fledgling play store for webos. Now....where should i go from here.i no longer think twrp is on it. All i have is webos with preware.sorry if this is newbie
Sent from my Galaxy Nexus using xda premium

Crwolv said:
Dumb question. I had dual boot installed with moboot and one day my dumbarse clicked erase SD card.well it did...EVERYTHING accept twrp. I successfully reinstalled webos and installed preware. Its actually pretty cool.its like a fledgling play store for webos. Now....where should i go from here.i no longer think twrp is on it. All i have is webos with preware.sorry if this is newbie
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
My goodness you have forgotten everything, you will need to install acmeuninstaller 3, moboot, CMW and the rom you want along with the relevant gapps. Sounds complicated this thread will make it easy
http://forum.xda-developers.com/showthread.php?t=2147284 and has all the necessary links. Have fun.
Sent from my Transformer Prime TF201 using Tapatalk 2

Heck ya i did lol. That refreshed my memory instead of a long video. Thank yo very much

Awesome!
Sent from my cm_tenderloin using xda app-developers app

Great vid!! Finally got CM10 on my Touchpad.

[CWM][6.0.3.1] ClockworkMod Recovery

Hey there,
Please find CWM for Oppo FInd 5 attached to this thread
CWM (ClockWork Mod) is a custom recovery designed to flash unofficial updates, backup and restore your device, and repair it in case of bad-flashed files, as well as a few extras.
INSTRUCTIONS
- Download the Android SDK in order to get the "fastboot" command-line tool
- Download the recovery.img and put it in the directory of fastboot (......\android-sdk\tools\)
- Hold power key and choose to restart your phone. Unplug any USB cord, and press the Volume Up key when the screen goes black. It takes some practice to get in fastboot mode, you might need to not press the Vol Up key immediately, etc. It's a bit jiggly, but after some time you get used to it and manage to do it in the first try
- If you succeed so far, you should be on a black screen with white text saying "fastboot mode..."
- Plug your USB cord, open your command-line, go to the fastboot directory, and type fastboot flash recovery recovery.img
- After a few seconds, the recovery will be flashed. Then type fastboot boot recovery.img to boot the recovery immediately
- Use the recovery option "Reboot system now" and say "Yes" to "Prevent system from writing recovery". Oppo official ROM will reflash a stock recovery on boot if you don't do that.
It shouldn't be too hard. Also, you're free to use CWM or TWRP (available in another thread), whatever you prefer. I'm just making that thread to separate our CyanogenMod build from the recovery itself and provide an alternative.

Thanks,
Its actually 6.0.3.1

Aerys said:
Thanks,
Its actually 6.0.3.1
Click to expand...
Click to collapse
Oops

Source code links can be found in the second post of the CM10.1 thread at http://forum.xda-developers.com/showthread.php?t=2238512

Nice, any reason to choose CWMR over TWRP?

CWM is known to work, and it's what we were using for development. It's less beautiful than TWRP, but it does its job, so if you don't plan to spend hours in recovery, CWM is a bit more painful to use (vol keys + power to validate), but safer.

XpLoDWilD said:
CWM is known to work, and it's what we were using for development. It's less beautiful than TWRP, but it does its job, so if you don't plan to spend hours in recovery, CWM is a bit more painful to use (vol keys + power to validate), but safer.
Click to expand...
Click to collapse
https://plus.google.com/106631699076927387965/posts/PzR46FpXiWP is a pretty good summary of it.
The TWRP guys do great work, but - recovery is recovery, you shouldn't be spending that much time there. CWM's simplicity makes it a bit easier to maintain.

Will you be updating it to clockworkmod touch?That would be great
Also,does it support ROM Manager app? I find this a better method since it removes need for a PC,and is simpler.

Allanitomwesh said:
Will you be updating it to clockworkmod touch?That would be great
Also,does it support ROM Manager app? I find this a better method since it removes need for a PC,and is simpler.
Click to expand...
Click to collapse
CWM touch is not open source, so no.
As to ROM Manager - I personally don't use it, it has failed on every device I've ever tried it on. It softbricked Infuses easily, and caused no end of problems on the I777.

It worked well on my phone,and saved a lot of time,it all has to do with the quality of the CWM submitted. At least consider it,if only for the PC-less.

Allanitomwesh said:
It worked well on my phone,and saved a lot of time,it all has to do with the quality of the CWM submitted. At least consider it,if only for the PC-less.
Click to expand...
Click to collapse
Um, you can do things PC-less now - it's just not recommended. CMUpdater is PC-less, so is downloading a ZIP and flashing it in recovery. (Although I don't recommend this, mobile browsers seem to be far more likely to corrupt zips than desktop ones do.)
You should never be flashing stuff without a PC around in case things go wrong anyway.

I agree with you,but if it works well there's nothing wrong with it. The option is a good thing. It works well with Goomanager and TWRP atleast.And it's easier to download an app from playstore than setup ADB,for the "make my phone kewl" user.

“- Download the Android SDK in order to get the "fastboot" command-line tool”
Where to find this "Android SDK" ? sorry for noob question.
---------- Post added at 08:09 AM ---------- Previous post was at 08:06 AM ----------
biou said:
“- Download the Android SDK in order to get the "fastboot" command-line tool”
Where to find this "Android SDK" ? sorry for noob question.
Click to expand...
Click to collapse
I found sth like "http://developer.android.com/sdk/index.html#download" is taht right?

CWM 6.0.3.1 Touch - Find 5
http://jenkins.cyanogenmod.com/job/recovery/25986/artifact/archive/recovery.img

Aerys said:
CWM 6.0.3.1 Touch - Find 5
http://jenkins.cyanogenmod.com/job/recovery/25986/artifact/archive/recovery.img
Click to expand...
Click to collapse
Can anyone confirms this works
Sent from my X909 using Tapatalk 2

It does work..
Here is the updated CWM touch 6.0.3.2 for Find 5 tested by me:
http://jenkins.cyanogenmod.com/job/recovery/26760/artifact/archive/recovery.img

Aerys said:
It does work..
Here is the updated CWM touch 6.0.3.2 for Find 5 tested by me:
http://jenkins.cyanogenmod.com/job/recovery/26760/artifact/archive/recovery.img
Click to expand...
Click to collapse
And it works! who's maintaining this for Oppo Find 5?

richie390 said:
And it works! who's maintaining this for Oppo Find 5?
Click to expand...
Click to collapse
None of us. Recovery Builder builds have a nasty habit of breaking - they've been nothing but a nightmare over on N80xx (lots of Status 7 errors that shouldn't be happening.)
Seriously, CWM Touch only makes sense on the Kindle Fire (no volup/voldn keys). On top of that, it's closed source.

Entropy512 said:
None of us. Recovery Builder builds have a nasty habit of breaking - they've been nothing but a nightmare over on N80xx (lots of Status 7 errors that shouldn't be happening.)
Seriously, CWM Touch only makes sense on the Kindle Fire (no volup/voldn keys). On top of that, it's closed source.
Click to expand...
Click to collapse
Yeah that may be true but I came from 4Ext on HTC Sensation. I missed the touch, and I don't like TWRP so much. But I'm glad there is a CWM Touch that works for the Find 5.

Where is the CWM touch which works for Find 5?

[ROM] [WIP] [DEV] Ubuntu Touch 13.10

Warning:
This is very alpha version of Ubuntu Touch. IT'S NOT READY FOR DAILY DRIVER. This is mainly for those curious souls like me that simply can't wait to try it on the find 5. There are and will be bugs. When that is said, lets get started.
Requirements before doing anything:
You will need to read the full guide before starting to do it. Just so you know what to do.
Downloads:
1. ubuntu image
2. saucy-preinstalled-touch-armhf.zip
3. extra zip
How to flash:
1. Reboot to recovery, i tested with twrp but any should do.
2. Make a full backup so you can restore after playing with ubuntu touch
3. Wipe System, Data, Dalvik-cache and Cache
4. Flash Ubuntu image....
5. Flash saucy-preinstalled.zip
6. Flash extra zip.
7. Reboot to System.
-------------------------------------
A few notes:
If you starts camera, you can shoot images but sometimes images files are corrupted, but back and front camera are working, also does flash.
If you enter video recording and starts that, camera app will freeze, you can then just exit it by swyping to the side and then long press camera under Recent apps and hit the X.
then camera can be tested again.
if you want to test music player, it can be done this way :
Code:
adb push testsong.mp3 /home/phablet/Music
adb chown phablet:phablet /home/phablet/Music/testsong.mp3
adb chmod 777 /home/phablet/Music/testsong.mp3
Then if you enter music player it should show a song that can be played. It failed for me the first time so I needed to reboot to recovery, with adb reboot recovery , then did "how to flash" again and after that when trying to boot it failed, and i needed to go back to recovery and do it all over with "how to flash but no wipe". When phone booted i started up the music app and can now play the song with or without wired headset
If you dont start music player before you push the song to the phone and all that, its possible that it can see the song without all the reflashing thing.
The reason for the reflash thing is that if you just reboots ubuntu, it will fail to bootup.
starting apps and switching between those is also working, sometimes phone gets a bit slow and not all apps is working, like soduku will not startup, but alot others is workiing fine.
Working:
Speaker
Camera
Sim card signal with 3g | sim card pin code needs to be disabled on phone before flashing ubuntu.
WiFi
Sms
Bootup.
A few important notes:
1. You cant reboot ubuntu in curret state, it will end up in bootloop.
2. To reboot to recovery use :
Code:
adb reboot recovery
This is a wip (work in progress) and need alot of work and i will do whatever i can to get it good.
Some images can be found here and a review here
Im hoping we can work together on this one so we can get it usefully as a dayli driver. So if you want to help, just pm me.
Sources:
Device tree
Vendors
Kernel
XDA:DevDB Information
[ROM] [WIP] [DEV] Ubuntu Touch 13.10, a ROM for the Oppo Find 5
Contributors
anders3408
ROM OS Version: 4.2.x Jelly Bean
ROM Kernel: Linux 3.4.x
Version Information
Status: Beta
Created 2013-09-19
Last Updated 2013-09-20

Reserved

Cool. Alpha indeed but awesome work nonetheless. Can't wait to see this progress. With roughly the same internals as mako and n4 hopefully the port goes smoothly. Cheers!
Sent from my Find 5 using Tapatalk 4

killerskincanoe said:
Cool. Alpha indeed but awesome work nonetheless. Can't wait to see this progress. With roughly the same internals as mako and n4 hopefully the port goes smoothly. Cheers!
Sent from my Find 5 using Tapatalk 4
Click to expand...
Click to collapse
Just as you think a device is about to "die" and be replaced by a newer version, a developer comes up with this stunning ROM to breath fresh life into it.
I don't want to get rid of my device now!

robifis said:
Just as you think a device is about to "die" and be replaced by a newer version, a developer comes up with this stunning ROM to breath fresh life into it.
I don't want to get rid of my device now!
Click to expand...
Click to collapse
I don't really see the Oppo find5 on it's way to the pasture just yet.

killerskincanoe said:
I don't really see the Oppo find5 on it's way to the pasture just yet.
Click to expand...
Click to collapse
Me neither. I'm sure this device will be running great for a long time.
Sent from my Find 5 using XDA Premium HD app

Thanks for this! Going to try this in the weekend
Sent from my Find 5 using xda app-developers app

‎

MultiROM

Hi there!
So I tried to add SailfishOS as second ROM with MultiROM, but getting stuck on boot.
First thought: kernel not kexec-hardboot patched
Anyone having a hint how to get this done? :/
Thanks in advance!
Ali
EDIT: Didn't flashed the Stock Images first. So maybe wrong bootloader there...? hm... don't know if this will run this way...? :/

aliander said:
Hi there!
So I tried to add SailfishOS as second ROM with MultiROM, but getting stuck on boot.
First thought: kernel not kexec-hardboot patched
Anyone having a hint how to get this done? :/
Thanks in advance!
Ali
EDIT: Didn't flashed the Stock Images first. So maybe wrong bootloader there...? hm... don't know if this will run this way...? :/
Click to expand...
Click to collapse
quote frome email:
* Multiboot / multirom is not supported currently
Click to expand...
Click to collapse

Yeah, so what?
One could still look for a solution...?

aliander said:
Yeah, so what?
One could still look for a solution...?
Click to expand...
Click to collapse
i looked.
looks like Sailfish OS is unpacked to /data/.stowaways/sailfishos and another boot.img is flashed
you can not flash boot.img just boot it via fastboot
i.e. flash sailfish os from zip file, next flash only boot.img from CM
next boot it using
Code:
fastboot boot hybris-boot.img
cons is only that you have to be connected to PC while booting

EnErGy[CSDX] said:
i looked.
looks like Sailfish OS is unpacked to /data/.stowaways/sailfishos and another boot.img is flashed
you can not flash boot.img just boot it via fastboot
i.e. flash sailfish os from zip file, next flash only boot.img from CM
next boot it using
Code:
fastboot boot hybris-boot.img
cons is only that you have to be connected to PC while booting
Click to expand...
Click to collapse
Thanks!
That's actually great information!
I've started to read a little bit about the MultiROM and will try to get a working configuration for SailfishOS today night or tomorrow.
If there isn't anything wrong with their kernel config or something, I should be able to get it to boot.
EDIT: To my current knowledge at least - which isn't much regarding the internals of MultiROM and SailfishOS boot sequence

EnErGy[CSDX] said:
i looked.
looks like Sailfish OS is unpacked to /data/.stowaways/sailfishos and another boot.img is flashed
you can not flash boot.img just boot it via fastboot
i.e. flash sailfish os from zip file, next flash only boot.img from CM
next boot it using
Code:
fastboot boot hybris-boot.img
cons is only that you have to be connected to PC while booting
Click to expand...
Click to collapse
I tried booting with the hybris-boot. Still hangs at Google logo. It even showed me a pong game when I rebooted it. Will continue to test.
EDIT: It's probably not that easy. Otherwise Jolla would have posted this as a method. There are probably more modifications done within the kernel/ramdisk.
While booting with hybris-boot my PC thinks it's a RNDIS xD
Don't we need a cyanogenmod 10.1.3 kernel that is kexec hardboot patched?
Mako kernel: https://github.com/CyanogenMod/lge-kernel-mako/releases

Zenety said:
I tried booting with the hybris-boot. Still hangs at Google logo. It even showed me a pong game when I rebooted it. Will continue to test.
EDIT: It's probably not that easy. Otherwise Jolla would have posted this as a method. There are probably more modifications done within the kernel/ramdisk.
Click to expand...
Click to collapse
Maybe something went wrong, but there is nothing more in jolla zip file.
Zenety said:
While booting with hybris-boot my PC thinks it's a RNDIS xD
Click to expand...
Click to collapse
RNDIS is usb network card, you can telnet to phone and see what went wrong.

EnErGy[CSDX] said:
Maybe something went wrong, but there is nothing more in jolla zip file.
RNDIS is usb network card, you can telnet to phone and see what went wrong.
Click to expand...
Click to collapse
Can only get a connection refused from putty. Have you been able to boot? And how is your MultiRom set-up? Like how many roms etc.

Zenety said:
Can only get a connection refused from putty. Have you been able to boot? And how is your MultiRom set-up? Like how many roms etc.
Click to expand...
Click to collapse
no, i do not use MutiRom, I do my experiments on Xperia L and have different setup.
about using fastboot
https://github.com/mer-hybris/hybris-boot#initial-ram-fs-debug-console

Zenety said:
Can only get a connection refused from putty. Have you been able to boot? And how is your MultiRom set-up? Like how many roms etc.
Click to expand...
Click to collapse
for me a simple telnet worked, got access to the device..
one issue is that the android /data was mounted, i solved this with a mount --bind /realdata/media/0/multirom/roms/sailfishos/

LuHe said:
for me a simple telnet worked, got access to the device..
one issue is that the android /data was mounted, i solved this with a mount --bind /realdata/media/0/multirom/roms/sailfishos/
Click to expand...
Click to collapse
Okay I got into telnet. Where are you mounting the sailfishos directory to? just to /data?

aliander said:
Hi there!
So I tried to add SailfishOS as second ROM with MultiROM, but getting stuck on boot.
First thought: kernel not kexec-hardboot patched
Anyone having a hint how to get this done? :/
Thanks in advance!
Ali
EDIT: Didn't flashed the Stock Images first. So maybe wrong bootloader there...? hm... don't know if this will run this way...? :/
Click to expand...
Click to collapse
A crude solution is to install both sailfish and your primary rom through MultiROM, and use the 'Swap ROMS' feature everytime you want to switch. It takes some time to swap roms but it does the job.

Is that MultiRom actually supports Sailfish OS?
I plan to install Sailfish OS using MultiRom. I've currently three Roms ( Android KitKat 4.4.2, FirefoxOS,Ubuntu Saucy). Is that possible to add Sailfish as Fourth or else I've to wipe all existing Roms from Memory?

aliander said:
Hi there!
So I tried to add SailfishOS as second ROM with MultiROM, but getting stuck on boot.
First thought: kernel not kexec-hardboot patched
Anyone having a hint how to get this done? :/
Thanks in advance!
Ali
EDIT: Didn't flashed the Stock Images first. So maybe wrong bootloader there...? hm... don't know if this will run this way...? :/
Click to expand...
Click to collapse
Still have no news for MultiRom? Wait for this.

kesavan2000in said:
I plan to install Sailfish OS using MultiRom. I've currently three Roms ( Android KitKat 4.4.2, FirefoxOS,Ubuntu Saucy). Is that possible to add Sailfish as Fourth or else I've to wipe all existing Roms from Memory?
Click to expand...
Click to collapse
Hi I'm planning to do the same did it work for you?
Sent from my Nexus 4 using Tapatalk

eSKaPe said:
Hi I'm planning to do the same did it work for you?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I don't think multirom is supported yet. It's the only thing keeping from testing this.
Sent from my HTC One using Tapatalk

multirom support is near. nexus 5 is the first one. take a look at:
http://forum.xda-developers.com/goo...h-os-alpha-t2841266/post54682704#post54682704

carepack said:
multirom support is near. nexus 5 is the first one. take a look at:
http://forum.xda-developers.com/goo...h-os-alpha-t2841266/post54682704#post54682704
Click to expand...
Click to collapse
N4 will also have support with the next release
vgrade

Multirom supports SailfishOS now.. Just download the sailfish zip n cm zip. Then install as secondary rom via recovery

Shiestie said:
Multirom supports SailfishOS now.. Just download the sailfish zip n cm zip. Then install as secondary rom via recovery
Click to expand...
Click to collapse
WTF! is it functional or is it really not stable and the most functions doesnt work??????
does it also work with the oneplus one?