Attention! Before installing this kernel, read carefully (don't forget reading post 2!)!
1.) Make a Nandroid!
2.) If you are installing this kernel the first time, it wipes your data and system! (this is caused by creating the secondary system partition) - you can restore your nandroid afterwards
3.) Make sure to have 700 mb free space at your internal sdcard (this is needed for secondary data)
4.) You can't install a rom as secondary rom, without doing some work yourself! This is caused by the way, rom installing is mounting the system partition. I can't do anything against it (What you need to do is written in the guide of post 2)
5.) You only can install 4.2.1 roms, with the "default"/cm partition layout!
6.) You have to install the kernel again, after you have installed a new rom. If you forget to install it, you just boot up to primary rom.
Many thanks to:
- cm team, especially pawitp
- stratosk
- mialwe
- zachariasmaladroid
- kasper_h
- krarvind
- kufikugel
- gokhanmoral (great idea to build a dualboot kernel, always helpful)
- Bejda
- sUsH667 ( i have taken his design for aroma filemanager, it's looking great)
- amarullz ( who coded the filemanager)
- ...
About this kernel (and installing it):
installing a dualboot kernel the first time:
1.) the kernel needs to create a secondary system partiton. this is taking place at the current /data partition.
b) the new version (04-Feb.) is creating an addional "devil" partition of 20 mb. it currently isn't used, but i am preparing already for later (boot.img is limited to 7.5 mb in size because of the boot partition size), because the dualboot kernel needs to include more files as the stock one, and for 4.1.2 support, i even need to include more...
2.) by installing the kernel the first time, data and system get deleted due to the partition change.
3.) as a security feature, the install fails the first time, before your data gets formated. if your install fails, you still can make a nandroid, if you didn't before. then just install again. this time the install does not fail. the kernel reboots to recovery automatically now
4.) install the kernel a third time
5.) before installing a new rom, go to advancend, reboot recovery
6.) after installing a rom (primary or secondary), flash the kernel again, follow the steps below for this!
updating the dual boot kernel to a newer version/installing the kernel after a rom flash:
1.) flash the kernel
2.) reboot to recovery (just in case...)
how to revert the partition changes:
there also is a "revert" kernel now, which is available here:
http://rootaxbox.no-ip.org/derteufel/jellybean4.2.x/
if one isn't using the dualboot kernel, the "revert" kernel doesn't revert anything, but is a normal single boot kernel, with the same features as the dualboot one.
if one is flashing reset kernel after dualboot, you need to flash it three times. the first install just fails. the second one succeds and reboots to recovery. the third one finishes the restore.
The reset kernel wipes data and system, (only) if coming from dualboot kernel!
in the recovery:
1.) by default, there is no entry for system and data in the fstab. i have done this, to ensure you don't install apps/packages to the wrong rom. this means, if you just go to install zip, install fails, because there is no system partition which can be mounted.
2.) the dualboot menu. what do these options do?
a) the first two options are mounting primary/secondary filesystem right after clicking.
b) these two options are preparing for mounting primary/secondary filesystem after you reboot to recovery. without using this, you don't have the options in recovery, to mount/format data or system, etc
3.) reboot primary/secondary system should be clear
how to install a rom as primary/secondary rom:
1a ) remove spaces from filename!
1b )install zip from sdcard
2.) choose from where to install
3.) choose what and where to install
note: the kernel installs itself after the rom. no need to reflash. this does not work with elite rom (because of the zip design)
How to create/restore a nandroid:
1.) go to dual boot menu
2.) select "enable mounting of pri. fs" or select "enable mounting of sec. fs"
3.) reboot to recovery
4.) backup or restore your nandroid, depending on your previous choise, you'll backup/restore the primary or secondary system
5.) consider to rename your backup, to something like primary_date or secondary_date
here you get the kernel. nothing else needed:
http://rootaxbox.no-ip.org/derteufel/dualboot/
Going to try it out
Enviado desde mi GT-I9000 usando Tapatalk 2
Where is the link
Sent from my GT-I9000 using xda premium
WOW great work derteufel
thanks a lot
WOW... Just wow!
almost all files uploaded/added now
a dualboot version of hellybean is currently uploading
thanks dev :good:
will give it a try ! ...
will you compile a kernel without dualboot for JB4.2.1???
Gesendet von meinem GT-I9000 mit Tapatalk 2
Awesome. Cant wait to try this. I remember a long time ago i mentioned it in your kernel thread.
Still following your work actually, but got stuck on CM all this time. Now can be on both! Nice.
So how does one boot into 1st or 2nd rom? By button combo? Dont see it mentioned.
Considering second donation :thumbup:
WOW WOW WOW WOW !!! DUAL BOOT ON OUR GALAXY S!!! FANTASTIC!!!! someone tested it???
sorry for my bad english
jelle2503 said:
Awesome. Cant wait to try this. I remember a long time ago i mentioned it in your kernel thread.
Still following your work actually, but got stuck on CM all this time. Now can be on both! Nice.
So how does one boot into 1st or 2nd rom? By button combo? Dont see it mentioned.
Considering second donation :thumbup:
Click to expand...
Click to collapse
Also, when do we need to flash the kernel again? When we install the main rom, or every time when we install a rom, even if its primary or secondary.
I am scared
Sent from my GT-I9000 using XDA Premium HD app
Perfect timing and choices DerTeufel,that guy:
DerTeufel1980 said:
- sUsH667 ( i have taken his design for aroma filemanager, it's looking great)
Click to expand...
Click to collapse
Keeps telling me i have to test Slim beta 2
Trak-X said:
Also, when do we need to flash the kernel again? When we install the main rom, or every time when we install a rom, even if its primary or secondary.
Click to expand...
Click to collapse
you have to flash the kernel everytime you install a rom, because every rom flashes a kernel. as this is implemented in the rom update script, i can't avoid it.
Terrible.... I am without voice!
There is no need to edit the primary ROM, is it?
Sent from my GT-I9000 using Tapatalk 2
So i flashed Dual Kernel (2 times as expected,error 7 first).
Advanced>reboot recovery> dual boot menu and all is here.
I mount secondary filesystem and flash the edited Slim beta2.
Reflash the dual kernel but it only boot in recovery.
If i don't flash dual kernel after Slim install it is stuck at semaphore boot image.
I have 1g free on sd,don't know what i'm missing,i think i'll download again edited slim beta2..don't know but its install seems too fast in cwm (i know it's Slim but hey,it's fast lol).
I love you DerTeufel.
Good Job.
Amazing<3
Gesendet von meinem GT-I9000 mit Tapatalk 2
Bejda said:
So i flashed Dual Kernel (2 times as expected,error 7 first).
Advanced>reboot recovery> dual boot menu and all is here.
I mount secondary filesystem and flash the edited Slim beta2.
Reflash the dual kernel but it only boot in recovery.
If i don't flash dual kernel after Slim install it is stuck at semaphore boot image.
I have 1g free on sd,don't know what i'm missing,i think i'll download again edited slim beta2..don't know but its install seems too fast in cwm (i know it's Slim but hey,it's fast lol).
Click to expand...
Click to collapse
This should not happen. Could you please flash the kernel a third time.
If the install fails like it does the first time, secondary system did not get created
Gesendet von meinem GT-I9000 mit Tapatalk 2
Related
THERE WERE AT LEAST TWO REPORTS OF SYSTEM FAILURE AFTER THIS UPDATE, BOTH HAD LAGFIX ENABLED.
!!!BACKUP BEFORE PROCEED!!!
This guide is to help those who would like to test tegrak's kernel but have dowbts about losing ability to flash zip files from CWM. This will also help those who would like to have simple root solution, and 2e recovery on froyo.
a) If you want to have simple root solution, one click lagfix and 2e recovery. Tested with Doc's v9.1.4 but should work on any rom including stock
1. flash tegrak's kernel found here http://forum.xda-developers.com/showthread.php?t=920711 using Odin (all instructions in tegrak's thread)
2. install Tegrak lagfix app from the market and install root from the app's menu
3. download attached file
4. extract this file saving directory structure and copy it's system folder into /sdcard/tegrak/update/00/ (If this path doesnt exist, create those folders) so your path should look like /sdcard/tegrak/update/00/system/...
5. reboot your phone into tegrak's recovery (simply reboot your phone and press home button when you see tegrak's kernel introduction)
6. (before proceed with this step backup your system partition from the same tegraks recovery) choose update from sdcard and select 00 folder
7. Install Rom Manager from the market and flash CWM from it. Now you have tegrak's kernel and CWM to flash all types of zip files.
a) If you already rooted your phone
1. flash tegrak's kernel found here http://forum.xda-developers.com/showthread.php?t=920711 using Odin (all instructions in tegrak's thread)
2. install Tegrak lagfix app from the market
3. download attached file
4. extract this file saving directory structure and copy it's system folder into /sdcard/tegrak/update/00/ (If this path doesnt exist, create those folders) so your path should look like /sdcard/tegrak/update/00/system/...
5. reboot your phone into tegrak's recovery (simply reboot your phone and press home button when you see tegrak's kernel introduction)
6. (before proceed with this step backup your system partition from the same tegraks recovery) choose update from sdcard and select 00 folder
7. Install Rom Manager from the market and flash CWM from it. Now you have tegrak's kernel and CWM to flash all types of zip files.
All this process replaces your 3e recovery with 2e recovery image and as tegrak's kernel does not overrides original recovery image your CWM will be untouched by tegrak's kernel, and you will successfully have combination of two recoveries (CWM and Tegrak's) To access CWM you can chose "reboot in recovery" from the Rom Manager menu or from Tegrak lagfix menu, and to access tegrak's recovery, press home button when you see tegrak's kernel introductory window while booting up your phone.
Brack11, thanks for the guide, but you should be posting this over to the general subforum.
Sent from my GT-I9000 using XDA App
g00ndu said:
Brack11, thanks for the guide, but you should be posting this over to the general subforum.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I think it's too advanced and dangerous for novices that mostly visit general. Also both described things 2e recovery and tegrak's kernel are from the area of development, this is all about customizing rom. I dont agree that it should be in general.
Thanks a lot!!
I also fail with barebone rom with incorporated tegrak kernel in 3e recovery,**** m8 spend all day to fix it & get back to insanity rom
10ks m8 for your efort
hensk said:
I also fail with barebone rom with incorporated tegrak kernel in 3e recovery,**** m8 spend all day to fix it & get back to insanity rom
10ks m8 for your efort
Click to expand...
Click to collapse
As I understand this fix didn't work for you, could you share to others what and how has failed?
Sent from my GT-I9000
no, no mate, just did not know that there is
thread like this,with fix solution
hensk said:
no, no mate, just did not know that there is
thread like this,with fix solution
Click to expand...
Click to collapse
Glad to hear that this works for you, thanks are accepted
Sent from my GT-I9000
brack11 said:
Glad to hear that this works for you, thanks are accepted
Sent from my GT-I9000
Click to expand...
Click to collapse
Point to note, this may even be only me.
The CWM does not reside in the kernel. Rebooting through recovery will only bring back to 2e. I need to apply update.zip again, reboot through recovery to get CWM. This happens everytime when going to recovery.
Sent from my GT-I9000 using XDA App
g00ndu said:
Point to note, this may even be only me.
The CWM does not reside in the kernel. Rebooting through recovery will only bring back to 2e. I need to apply update.zip again, reboot through recovery to get CWM. This happens everytime when going to recovery.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
You are right, this has nothing to do with tegraks kernel or with recovery, I has this issue when I has rooted phone without custom kernel. It would always go to standard recovery and then I would have to apply update. I believe thoa is some special feature of the device.
Sent from my GT-I9000
brack11 said:
You are right, this has nothing to do with tegraks kernel or with recovery, I has this issue when I has rooted phone without custom kernel. It would always go to standard recovery and then I would have to apply update. I believe thoa is some special feature of the device.
Sent from my GT-I9000
Click to expand...
Click to collapse
Iirc, when I use Rom Manager the last time, it wasn't like that at all. Reboot let me goes directly to CWM. I only need to download it and apply it once.
Sent from my GT-I9000 using XDA App
g00ndu said:
Iirc, when I use Rom Manager the last time, it wasn't like that at all. Reboot let me goes directly to CWM. I only need to download it and apply it once.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Well, the tegraks kernel doesn't really replaces kernel, and if the kernel is stock you get thesame behaviour as you should have with the stock kernel, as I say, I never had rommanager be as default recovery, always either through update.zip or custom kernel (which is not custom in tegraks case)
Sent from my GT-I9000
brack11 said:
Well, the tegraks kernel doesn't really replaces kernel, and if the kernel is stock you get thesame behaviour as you should have with the stock kernel, as I say, I never had rommanager be as default recovery, always either through update.zip or custom kernel (which is not custom in tegraks case)
Sent from my GT-I9000
Click to expand...
Click to collapse
I understand, back in the days before the speedmod, voodoo or even the oc kernels, i installed the ROM manager and had made CWM as the default recovery. Anyway, it is still okay, I guess. Btw, using tegrak's kernel, have you tried using update zips via cwm?
I have not tried it yet, since I find that updating via tegrak method works very well for me.
g00ndu said:
I understand, back in the days before the speedmod, voodoo or even the oc kernels, i installed the ROM manager and had made CWM as the default recovery. Anyway, it is still okay, I guess. Btw, using tegrak's kernel, have you tried using update zips via cwm?
I have not tried it yet, since I find that updating via tegrak method works very well for me.
Click to expand...
Click to collapse
Yes, I used a few times to flash different modems and r64 theme.
Unfortunately this did not work for me (XWJS5), got stuck on initial splash screen, luckily Dean-O's post http://forum.xda-developers.com/showpost.php?p=10562493&postcount=80 saved my ass.
I've been unable to get 2e recovery working on a bear-bones kernel since XXJPY.
fomofo said:
Unfortunately this did not work for me (XWJS5), got stuck on initial splash screen, luckily Dean-O's post http://forum.xda-developers.com/showpost.php?p=10562493&postcount=80 saved my ass.
I've been unable to get 2e recovery working on a bear-bones kernel since XXJPY.
Click to expand...
Click to collapse
Did you have lagfix enabled? As I can say from my own experience.now - this hack is DANGEROS if you have lagfix enabled. To say more any manipulations with recovery while on onenand fix - DANGEROUS AND LEAD TO LOOSING ALL PARTITIONS
Sent from my GT-I9000
brack11 said:
Did you have lagfix enabled?
Click to expand...
Click to collapse
No, I have used the "hack" recovery 2e method with success right up until JPY, but JS3, and now JS5 does not work.
It seems to me (just learning Android), that it doesn't have write permissions to the /sbin directory, which is what the recovery script needs.
Recovery 2e works with CF-root, but I already have root, and rather not overwrite the stock kernel.
Ok, yesterday I have thoroughly tested my workarounnd for installing rom. I hade Doc's 9.6 downloaded 9.8 reboot into recovery using rommanager option, wiped cach partition, wiped dalvik, wiped data, flashed 9.8, wiped data again, and flashed again, rebooted, restored titanium backups, flashed tegrak's kernel, flashed update for recovery 2e from within tegrak's kernel, then rebooted into 2e recovery, flashed new modem (JVE) and flashed theme r64, rebooted, everything works as it should no errors no hangs no loops.
Does this still work?
Here's a simple guide for CM7 users, to install CM9 as a test rom AND keep their CM7 ROM as a main ROM
EDIT (01/04/2012):Guide updated according to new versions of multiboot. Also works for CM10!
DUE TO KERNEL INCOMPATIBILITIES, MY GUIDE IS FOR PEOPLE WHO INSTALL CM9 +CM7 WITH THE SAME KERNEL. (EX: CM7 FROYO KERN + QUARX CM9 FOR FROYO KERN)
This guide is tested and approved on froyo kernels.
First: I suggest you backup your rom before doing anything, but there's no danger don't worry
first download and simply place on your SD-Card these files:
m11kkaa's multiboot:
http://forum.xda-developers.com/showthread.php?t=1364659
This will allow us to lauch our main ROM normaly, and when we want to, launch our 2nd rom (which will be CM9 =D)
Epsylon3's or Quark's latest version of CM9:
http://defy.wdscript.fr/
Or
http://quarx2k.ru/
Google Apps (optional):
http://goo-inside.me/gapps
Place all 2/3 zips on SD-card.
Download 3filesystem images that will be your virtual partitions for CM9 on Sdcard:
www.mediafire.com/?vvkmy2tx4yeg32m
extract them, and place all 3 of them under /multiboot/CM9 in SDcard
You can also use the app called multibootmanager to do this
Warning: these partitions have size limits (300mb each). Don't run out of space!
People who know how to can create their own partitions, any size they want, threads exist for that
Here are the instructions:
DO NEVER WIPE DATA DURING PROCESS, IT IS NOT NEEDED
1) Go into Bootmenu
2) Choose "recovery ->" to go to the recovery choice menu
3) MAKE SURE you have:
"Custom Recovery" OR "Latest Recovery"
"Stable Recovery"
"Stock Recovery"
4) Choose "Stable Recovery"
6) Install Zip from SD-Card: multiboot_vXXXX.zip
7) REBOOT SYSTEM NOW
8) When you get the blue led, press Vol. Down, you will be in the Bootmenu.
-Choose boot->Set Default->2nd-init
-Go back once
-choose [2nd-system] to boot into the 2nd system menu.
- Here is where you will be able to select 2nd roms to boot. If you put the files on the SDcard in the right place (see above), you should see them in the menu. Other choices are "boot from nand","recovery" or "reboot".
- Choose Recovery(CWM), and then select which rom you want to apply the modifications (CM9). You will now reboot into a recovery for your virtual system.
9) a) Install zip from sdcard: CM9!!! =D
9)b) (OPTIONNAL): install google apps
10) Wipe cache and dalvik cache and then reboot system.
11) Done! reboot. If you want to launch CM9 just press Vol. Down on blue led, boot into 2nd system like above and select CM8 to boot it.
Booting any virtual ROM will take a few minutes, sd cards are slower, and this will be first boot.
Enjoy Epsilon's, Quark's, m11kkaa's and walter79's great work!
Originally Posted by m11kkaa
Some info:
- After installation, The recoveries under the 2nd system multiboot menu is for your virtual system and "Stable Recovery" for your real system
- you can restore any backup or install any zip in "Lastest Recovery" and it will go into your virtual system
- boot the virtual system with the 2ndsystem-option in bootmenu
Click to expand...
Click to collapse
Tutorial video made by Yamandude:
http://youtu.be/aqdQSusw2zw
If one day you don't want CM9 again, simply remove the folder /fsimages/ from your SDcard.
I suggest you keep them in case, you may change your mind one day
You now have double boot, and CM7, and CM9 on your same phone!!!!
Troubleshooting:
My main ROM works, but i get a bootloop with CM9
In latest recovery: wipe cache + Dalvik cache. If you still get a bootloop then wipe data too.
Are u shore u flash multiboot from custo/latest recov?
I always do it from stable recov!
Sent from my MB525 using xda premium
It IS from custom and NOT latest recovery (step 4). Your "guide" is incorrect and if you ask me, makes things even more complicated than they are...sorry.
In what way is this needed amyway?; there's already a multi-boot thread.
No warning about NOT wiping data in latest recovery...Nothing about the size and limits of the 3 image files...
[] AL [] said:
It IS from custom and NOT latest recovery (step 4). Your "guide" is incorrect and if you ask me, makes things even more complicated than they are...sorry.
In what way is this needed amyway?; there's already a multi-boot thread.
No warning about NOT wiping data in latest recovery...Nothing about the size and limits of the 3 image files...
Click to expand...
Click to collapse
"Custom recovery" as we know today used to be called "latest recovery" a few months ago. The name changed so i mentionned both names in case people get confused if i say only one and they see the other. What is important is checking if you have three recoveries, not the way you call them.
Seen as CM9 is for test purposes, i doubt that warning not to install to much apps on the Second ROM is very relevant. Even though i will take into account your comment
Sent from my 1Ghz CM7 Defy
nogoodusername said:
Are u shore u flash multiboot from custo/latest recov?
I always do it from stable recov!
Click to expand...
Click to collapse
If you flash multiboot.zip in the stable mod, you'll change mount settings for your 2nd init partition, and then it will be your main rom that will load from sdcard. I tried this and unfortunately my main com became CM9, and it is not what we want ^^.
Sent from my MB525 using xda premium
Sent from my 1Ghz CM7 Defy
In fact, my bad: I meant "stable" not custom. m11kkaa multiboot is to be installed in stable recovery and never in latest.
Never wipe data in latest recovery or android secure will be erased and your main boot apps will stop working.
There are incompatibilities between some roms: MSGinger will not work with ics..
...OP need some work to say the least...
Here:
[] AL [] said:
QUOTE=twa_priv;19863273]I think that's exactly what most people here are doing. Look at AL's post (http://forum.xda-developers.com/showpost.php?p=19814199&postcount=280) which is the one that got me started using multiboot.
Click to expand...
Click to collapse
Yes thanks. He might also be interested in reading this one and this one as well on this.
Edit:
And i don't know about wajkiui, but there's is a problem with MSGinger though; so be warned!
Just give it a shot anyway... but if there was ever a reason to make a nandroid backup of your current build before jumping into something, I think multiboot calls for it...
L.E.: and while I think about it: one drawback I've noticed from multiboot is that once you boot back into your main rom, the battery stats are screwed up (or to the state they were when you left for the 2nd-boot). So give your phone a nice long charge to fix this or don't complain about eventual steep battery drop...[/QUOTE]
crakeron said:
If you flash multiboot.zip in the stable mod, you'll change mount settings for your 2nd init partition, and then it will be your main rom that will load from sdcard. I tried this and unfortunately my main com became CM9, and it is not what we want ^^.
Sent from my MB525 using xda premium
Sent from my 1Ghz CM7 Defy
Click to expand...
Click to collapse
That is incorrect...that's how I did (and others and how m11kkaa's instructions were at first _ I believe) and CM7 IS my main boot and ics my 2nd boot. And multiboot zip most probably can be install with both when you think about it. It's ICS that you absolutely need to install in latest/custom recovery... that was my last comment here good luck with this thread.
[] AL [] said:
That is incorrect...that's how I did (and others and how m11kkaa's instructions were at first _ I believe) and CM7 IS my main boot and ics my 2nd boot. And multiboot zip most probably can be install with both when you think about it. It's ICS that you absolutely need to install in latest/custom recovery... that was my last comment here good luck with this thread.
Click to expand...
Click to collapse
Yeah i've just re-done it all by flashing the multiboot in stable recovery, both work you're right ^^
Sent from my 1Ghz CM7 Defy
Great guide. Thanks.
Sent from my MB525 using XDA App
and how to uninstall 2nd boot now?
Screwed my Cyanogen 7.1: cannot run any external keyboard, language is always English after reboot.
tvg said:
and how to uninstall 2nd boot now?
Screwed my Cyanogen 7.1: cannot run any external keyboard, language is always English after reboot.
Click to expand...
Click to collapse
I wouldn't bother with uninstalling the multiboot function. But if you don't want to use your 2nd rom anymore simply take the /fsimages/ folder of your sdcard.
If one day you change your mind, copy them back . Multiboot may go away if you change anything to do with bootmenu in your main ROM (CM7).
Remember: if you don't want the 2nd Boot anymore, simply take the partitions under /fsimages/ off your card
P.S. You should have a chat with epsylon and m11kkaa about the issues you mentionned
royale1223 said:
Great guide. Thanks.
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
Your welcome =)
I tested CM9 and deleted /fsimages.
I reflashed many times using SBF, fixed SBF, omg, at least ten times.
And my CM7 (a new instance) does not save the language I choose after a reboot.
And any keyboard except the built-in one also hangs (The application has stopped etc).
Help, I need to fix it back =( I just cannot understand why I reflashed all the things thoroughly and still I can't get just the normal CM7 back =(
---------- Post added at 12:59 AM ---------- Previous post was at 12:58 AM ----------
crakeron said:
P.S. You should have a chat with epsylon and m11kkaa about the issues you mentionned
Click to expand...
Click to collapse
Thank you, I will try...
10x for detail Explanation; Can I translate this and post into Korean forum?
CM9现在还不成熟，系统也有bug吧
Motivateme said:
10x for detail Explanation; Can I translate this and post into Korean forum?
Click to expand...
Click to collapse
Sure feel free . Put a little link to this thread somewhere as a source and you can
Sent from my 1Ghz CM7 Defy
tvg said:
I tested CM9 and deleted /fsimages.
I reflashed many times using SBF, fixed SBF, omg, at least ten times.
And my CM7 (a new instance) does not save the language I choose after a reboot.
And any keyboard except the built-in one also hangs (The application has stopped etc).
Help, I need to fix it back =( I just cannot understand why I reflashed all the things thoroughly and still I can't get just the normal CM7 back =(
---------- Post added at 12:59 AM ---------- Previous post was at 12:58 AM ----------
Thank you, I will try...
Click to expand...
Click to collapse
Did you backup before starting any of the instructions as i suggested? It's a wierd issue you have there =/ ....are you sure it has nothing to do with settings you may have changed? What do the dev's say about it?
Sent from my 1Ghz CM7 Defy
jejeje thanks for your tutorial, now maybe if I can install it without problems
lenidas said:
jejeje thanks for your tutorial, now maybe if I can install it without problems
Click to expand...
Click to collapse
How did it go?
I tried to install it, but no luck. After reboot I am stuck on Cyanogoogle logo forever... Wonder what could be wrong?
http://forum.xda-developers.com/showthread.php?t=1719746
Original Thread.
For those that want information I've a GSM model and I flashed this upon
.58 Enhanced v2
-Firstly Flash DooMLoRDs ICS Beta Kernel via fastboot OK!
-Boot the phone into recovery OK!
-Perform a Factory Reset OK!
-Wipe cache and dalvik-cache OK!
-Flash the Zip from SD Card in recovery OK
-REBOOT and Enjoy! - Stuck On Kernel Screen / DoomLord Kernel ICS Beta
I'm unsure what to do, all the other roms seem to work well for me.
This rom is built based on KA14 Test Play which does not work for me either, and Cyanogen 9 RC2 is sluggish at games at least for me.
Cyanogen 7 is slow on the menu and all apps always stay in memory.
I just want to add this rom to my collection I.E I make a backup of each Rom and Kernel so I can switch without using a laptop.
sewer56lol said:
http://forum.xda-developers.com/showthread.php?t=1719746
Original Thread.
For those that want information I've a GSM model and I flashed this upon
.58 Enhanced v2
-Firstly Flash DooMLoRDs ICS Beta Kernel via fastboot OK!
-Boot the phone into recovery OK!
-Perform a Factory Reset OK!
-Wipe cache and dalvik-cache OK!
-Flash the Zip from SD Card in recovery OK
-REBOOT and Enjoy! - Stuck On Kernel Screen / DoomLord Kernel ICS Beta
I'm unsure what to do, all the other roms seem to work well for me.
This rom is built based on KA14 Test Play which does not work for me either, and Cyanogen 9 RC2 is sluggish at games at least for me.
Cyanogen 7 is slow on the menu and all apps always stay in memory.
I just want to add this rom to my collection I.E I make a backup of each Rom and Kernel so I can switch without using a laptop.
Click to expand...
Click to collapse
Hi , what was your rom before trying to install miui?
It seems so I had two recoveries at that point of which one being the leftover and which is terminated upon forst boot and one in the IcsBeta Kernel. What have I done is used the leftover CWM and that was the error. Anyway I found out this by accident when trying to enter flashmode and I didn't realise the kernel booted. I've flashed this rom using the kernel's touchscreen recovery and that worked for me. Anyway to answer your question it was 2.3.4 stock (.58) Enhanced version v2 anyway considering this is as an ICS ROM I should be able to get to it with any Gingerbread version.
Sent from my R800i using xda app-developers app and Miui v4 - Which IS installed.
Hi everyone,
I have tried searching but was not able to find what I was looking for.
I would like to install Cyanogen 9 RC2 on my phone. http://forum.xda-developers.com/showthread.php?t=1757323
I currently have an early version of CM10 GSM Jelly Bean on there, which is missing some of the core features (they will come with time!). According to the instructions though, the zip file is supposed to contain a boot.img file to flash it.
Guessing its my newbieness, but, where do I get this file? How do I extract it from the archive to flash with?
Code:
Rom Installation:
Flash boot.img in fastboot
FACTORY Reset
[B]Flash the ROM[/B]
reboot
boot rom
reboot back into recovery
Flash GApps
Reboot into the system (first boot will take several minutes)
Thanks muchly! As well, if someone can point me to a handy user guide for this kind of thing, that would be awesome. As of now I'm only barely able to finger this stuff out. Took me over an hour to unlock my phone haha
:/
U READ THE INSTRUCTIONS WRONG :/
""DONT FLASH THE BOOT.IMG INSIDE THE ZIP""
U can simply use KISS kernel open :
http://www.mediafire.com/?7hq6ikra7w0kt
open the 1 wid cm9 written in it ..rename it to boot.img ...
this kernel has several advantages lik sweep2unlock and usb host <3
Aninomus said:
U can simply use KISS kernel open :
open the 1 wid cm9 written in it ..rename it to boot.img ...
this kernel has several advantages lik sweep2unlock and usb host <3
Click to expand...
Click to collapse
Interesting. So, I take this new boot.img and toss it in my /FastLoader folder, patch it, then fire up my CWM Recovery, load zip from SD and voila?
(I can't check it out now, MediaFire is blocked at work)
:/
read the instructions 1000 times :/
As of now i am out of tim wen free i'll giv u the whole instructions
Aninomus said:
U READ THE INSTRUCTIONS WRONG :/
""DONT FLASH THE BOOT.IMG INSIDE THE ZIP""
Click to expand...
Click to collapse
Sorry, new to this stuff. Please don't hate!
I had just installed CM 10 which did require a boot.img flash, so I was a bit confused with the "Flash the ROM" portion of the install.
So with CM 9, I just plop the zip on my phone's SD, fire up recovery, load, bob's my uncle?
You need to flash a kernel for cm9 go to the KISS kernel thread http://www.mediafire.com/?7hq6ikra7w0kt pick a kernel and flash it via fastboot, just like you did the CM10 kernel, boot into recovery ,wipe data, cache and format system, flash the CM9 ROM and the Gapps, reboot!
rockstar_26 said:
You need to flash a kernel for cm9 go to the KISS kernel thread http://www.mediafire.com/?7hq6ikra7w0kt pick a kernel and flash it via fastboot, just like you did the CM10 kernel, boot into recovery ,wipe data, cache and format system, flash the CM9 ROM and the Gapps, reboot!
Click to expand...
Click to collapse
Yey! Thanks man. Exactly what I needed. I'm installed and up/running.
Having a bit of an issue with the SD card, it won't detect it. Card works fine in my computer; tried another one as well. Tried mounting/unmounting, rebooting, violently protesting in the streets, nothings working.
I'm not even sure where to begin fixing that. Any suggestions? Thanks!
Whats MultiROM
Multirom is a ROM manager created by Tasssadar with the ability to load multiple ROMs without the need to remove your older one, giving you the ability to test/run multiple ROMs at once, you can also restore TWRP backup as Secondary ROMs allowing you to look at your backup to choose the right one, or maybe just have 2,3,4,5,6 working OS on your phone... just because it's cool.
Warning!
It _is_ dangerous. This whole thing is basically one giant hack.
I Nuked my SDCard twice in porting this tool over, I'm not entirely sure what caused it, but I reverted few changes which might have been the reason, so I hope it wont happen again.
Still, I'll highly recommend you make backups and keep them on your computer. Always.
I've been using this for 2 weeks now with no serious problems, but just as well, don't be blaming me if anything goes wrong.
keep the "i cant get this to work" messages out of my PM i wont bother replying to them,
as almost anyone on this thread can help you.
you have a problem, read the main OP and if you still cant get it to work... post your problem here...
and be specific... "this is not working" will get you nowhere and no answers.
Special Thanks: @Tasssadar: For The MultiROM Source.
Sources:MultiROM
Modified TWRP
Download is one post below.
Requirements:
S-off/Unlocked Bootloader
Understand How KL Zeus Work*
By Flashing That Kernel, you'd need to flash a 2nd kernel to go along with it..
if you don't follow those instruction, the main ROM wont boot.
To Install MultiROM:
Flash Zeus Boot.img
Flash Multirom-20141228-v30-UNOFFICIAL-endeavoru.zip normally trough recovery.
Flash Multirom-20150430-v32-UNOFFICIAL-endeavoru.zip normally trough recovery (New Layout ONLY).
Reboot
To Fix Write To SDCard issue(flash on secondary ROM only):Not Needed with New Layout
Flash UPDATE-SuperSU-v2.40.zip(possible only needed on Lollipop, if no, no harm in switching to SuperSU)
Flash SDFix.zip
To Remove ROMs:
Reboot Into MultiROM
Boot Into TWRP --> Advanced -- > MultiROM --> List ROM --> Select the ROM To Remove --> Delete
To Add ROMs:
Reboot Into MultiROM
Boot Into TWRP --> Advanced -- > MultiROM --> Add ROM
To Remove ROMs:
Reboot Into MultiROM
Boot Into TWRP --> Advanced -- > MultiROM --> List ROM --> Select the ROM To Remove --> Delete
To Change Kernels:
Boot TWRP --> Advance --> MultiROM --> List ROMs --> Flash Modules Zip*
List ROMs --> Remove boot.img
List ROMs --> Add boot.img
* The Modules must be flashed 1st, as the boot.img is replaced with each flash.
Failed Install & losing memory
MultiROM -> TWRP
adb shell dosfsck -a /dev/block/mmcblk0p14
ToDo:
-- Nothing as it stands
and another one...
Amazing you did it..well done mate glad you are still with us on our dated hox.
Sent from my One X using XDA Premium 4 mobile app
Great!!! Eager to try but its very late night here
Also waiting for your Kernel
Sent from my One X using XDA Premium 4 mobile app
Wow your are just great ...... Will Test it if i have enough time.
Maybe you get tomorrow a pm
Gesendet von meinem HTC One X mit Tapatalk
Thant said:
OK one question maybe stupid but When I install MultiROM.zip from my recovery and then I will restart the phone it will directly start in TWRP and ask me which ROM I want ot boot or how I will go in TWRP recovery when it is not on the recovery partition and it will be posible to flash custom kernel on the others roms 2,3,4 and etc.?
Click to expand...
Click to collapse
It'll be better if i answer this here,
during boot, after flashing MultiROM, MultiROM starts and prompts you to choose what to boot,
Internal (Main ROM), TWRP or other ROMs you installed.
if you want to change kernel of a secondary ROM,
You boot TWRP -->Advance --> MultiROM --> Select ROM --> Remove boot.img
Select ROM --> Add boot.img, then you get to select the kernel you want.
To Flash the Zips/Modules
TWRP -->Advance --> MultiROM --> Select ROM --> Flash Zip
Ill update the OP with these now.
I have a silly question do I have to reflash my current Rom or it will be updated in Boot List Automatically after following above instructions.
Sent from my One X using XDA Premium 4 mobile app
lalit387 said:
I have a silly question do I have to reflash my current Rom or it will be updated in Boot List Automatically after following above instructions.
Sent from my One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The main ROM will remain untouched..
but you'll need to know how KL Zeus works to boot it.
Great! I do not have important data in the internal storage, so I can test it.
@Thunder07 I want to test it too
The Current structure of a secondary rom is...
/system 1.25GB
/data 1GB
/cache 436MB
It's a waste having this big of /system partition and small of /data partition...
So i need to know the size of the biggest bloatware ROM so i can shrink the /system partition to it.
Thunder07 said:
The Current structure of a secondary rom is...
/system 1.25GB
/data 1GB
/cache 436MB
It's a waste having this big of /system partition and small of /data partition...
So i need to know the size of the biggest bloatware ROM so i can shrink the /system partition to it.
Click to expand...
Click to collapse
It seems that the Sense based Roms do have a massive system partition. Skydragon 2.0, for example, has system at 922MB in zipped format.
ljjehl said:
It seems that the Sense based Roms do have a massive system partition. Skydragon 2.0, for example, has system at 922MB in zipped format.
Click to expand...
Click to collapse
jeez... 1GB it is then :/
Thunder07 said:
jeez... 1GB it is then :/
Click to expand...
Click to collapse
Though people should keep the really big ROMs like Sense as the 1st OS. It only seems logical enough. By the way, does running a ROM on the internal sdcard slow down the OS at all? I know external sdcards have this issue for sure on other devices.
Sent from my One X using Tapatalk
humzaahmed155 said:
Though people should keep the really big ROMs like Sense as the 1st OS. It only seems logical enough. By the way, does running a ROM on the internal sdcard slow down the OS at all? I know external sdcards have this issue for sure on other devices.
Sent from my One X using Tapatalk
Click to expand...
Click to collapse
I am not complaining for me work perfect I have for main ROM SENSE5 LonelyX and for second SlimKat5.2a and for third CM11 nightly from 25.05.2014 and I don't see lags or something else now my phone work on CM11 for few days after this I think to start SlimKat for few days Main Rom is ok
Thant said:
I am not complaining for me work perfect I have for main ROM SENSE5 LonelyX and for second SlimKat5.2a and for third CM11 nightly from 25.05.2014 and I don't see lags or something else now my phone work on CM11 for few days after this I think to start SlimKat for few days Main Rom is ok
Click to expand...
Click to collapse
You've made me think of trying sense again.
I've only tried aosp for a long time now.
But with multirom I might flash a sense rom again. Would be great to be able to use sense camera for example while running carbon as main rom.
I'm on carbon (main rom) and slimkat (second rom) and they both work fine and smooth.
Maybe only the start up needs a little longer than usual but once it's booted it works fine.
sent from my carbonated Kitty Kat
cappuccina said:
You've made me think of trying sense again.
I've only tried aosp for a long time now.
But with multirom I might flash a sense rom again. Would be great to be able to use sense camera for example while running carbon as main rom.
I'm on carbon (main rom) and slimkat (second rom) and they both work fine and smooth.
Maybe only the start up needs a little longer than usual but once it's booted it works fine.
sent from my carbonated Kitty Kat
Click to expand...
Click to collapse
just now deleted CM11 to many bug for me I missed important notification. The phone beep but I don't see nothing on the screen. Now for this week I think to test SlimKat to see how it works I hope to be stable and don't miss any inportant notification. Whole day I thik on the question why today I have too many free hours and in the end of the day when start main rom I understand why
So I flashed the MultiROM zip through the Aroma installer, when I boot into MultiROM and try to add a secondary ROM, it installs but i can't do much with it after, it doesn't boot either, as for my primary ROM, this goes missing until I actually boot into recovery and reinstall the ROM, any ideas? Or am I supposed to use the Aroma KL Flasher for every boot image? Though it doesn't work because it only asks for a standalone image, not a modules folder.
I flashed the kernel modules through the MultiROM section but everything fails aswell, I know I'm doing something wrong though.
humzaahmed155 said:
So I flashed the MultiROM zip through the Aroma installer, when I boot into MultiROM and try to add a secondary ROM, it installs but i can't do much with it after, it doesn't boot either, as for my primary ROM, this goes missing until I actually boot into recovery and reinstall the ROM, any ideas? Or am I supposed to use the Aroma KL Flasher for every boot image? Though it doesn't work because it only asks for a standalone image, not a modules folder.
I flashed the kernel modules through the MultiROM section but everything fails aswell, I know I'm doing something wrong though.
Click to expand...
Click to collapse
When I add a secondary Rom I also go into the advanced/Multirom/ list and select the Rom I installed. I then remove boot.img, then go back and install boot.img (the boot.img I extracted from Rom), go to the directory I saved that to and it's done. Should boot after that.
@Thunder07,
My current issue seems to be a cache issue. I seem to have to fastboot cache a lot more than I like, otherwise I can't always get to TWRP. Reboot (or from poweroff) more often than not seems to get me only the internal Rom and not the MultiRom startup. I was hoping a wipe cache from device would be sufficient, but no luck.