Database Users

[TRICK] restore after testing CM7 ( switching ROMs )

Hey guys I noticed people having problems restoring a back-up after testing CM 7
So here it is; switching ROMs with NO data loss
The deal is CM7 has is own kernel and there fore his own recovery.
Back ups made in another kernel ( and this means other CWM ) can not get restored with CM7 kernel.
And of course the other way around.
what you can do to easy test CM 7 and get back
- make nandroid backup with your own CWM, probarbly Doom kernel
- flash and test CM 7
- take the ''boot.img'' from the download of your kernel you had before testing CM7
- place it in your fastboot folder
- connect phone in fastboot
- in fastboot issue the command ''fastboot boot boot.img''
- the phone wil reboot, now dont let it boot but enter recovery
- you are now in the same recovery where you made your back up, so just restore it.
all done
---------- Post added at 05:14 PM ---------- Previous post was at 05:12 PM ----------
you can also do this the other way around :
[ UNTESTED ]
- make nandroid backup with CWM in CM7 kernel
- restore stock as stated above
- take the ''boot.img'' from the download CM7
- place it in your fastboot folder
- connect phone in fastboot
- in fastboot issue the command ''fastboot boot boot.img''
- the phone wil reboot, now dont let it boot, but enter recovery
- you are now in the CM7 recovery so you can restore CM7 back up and go back to testing

hi can u tell me exactly wht are the issues restoring backups when using latest CWM 4.0.1.5?

thatt is not the back up used in CM7 and as far as I know you cant take a back up made with CWM 4.0.1.5 and restore it with CWM included in CM7 right ?
or is it already possible at the moment ( been away for a while )

depulle87 said:
thatt is not the back up used in CM7 and as far as I know you cant take a back up made with CWM 4.0.1.5 and restore it with CWM included in CM7 right ?
or is it already possible at the moment ( been away for a while )
Click to expand...
Click to collapse
currently i dont have my Xperia Arc with me, so i cant test..
can u tell me which is the CWM version in CM7 kernel? (version number is written in title of recovery menu)
for my kernels i use the older CWM v4.0.1.4...

I have to get back to you later Iḿ on my tablet now not my pc so cant look

DooMLoRD said:
currently i dont have my Xperia Arc with me, so i cant test..
can u tell me which is the CWM version in CM7 kernel? (version number is written in title of recovery menu)
for my kernels i use the older CWM v4.0.1.4...
Click to expand...
Click to collapse
Hey buddy,
It's 4.0.1.5 in FXP 24 latest release. Waiting for you to update Doomkernel...

vaibhavknockout said:
Hey buddy,
It's 4.0.1.5 in FXP 24 latest release. Waiting for you to update Doomkernel...
Click to expand...
Click to collapse
thanks man if doom can ( no we know he can, if he wants to ) that will be great

Hmm, but where's the advantage? I don't get it, sorry
It saves about ~3 minutes of time because your just booting the image and not flashing?
Or do i miss something?

bmwbasti said:
Hmm, but where's the advantage? I don't get it, sorry
It saves about ~3 minutes of time because your just booting the image and not flashing?
Or do i miss something?
Click to expand...
Click to collapse
Well just means ya could restore data from your current rom on top of cm7 and have all your current setup wit no setting up
Sent from my LT15i using XDA Premium App

I dont think that that is going to work but it is worth a shot.
The advantage is : when it is done you can switch roms without the need of a PC ( and a bit faster and easier )

depulle87 said:
I dont think that that is going to work but it is worth a shot.
The advantage is : when it is done you can switch roms without the need of a PC ( and a bit faster and easier )
Click to expand...
Click to collapse
I think i read some where that the arc is missing some partition ,which allows u to flash kernels on the phone
So im not sure it will ever be possibe without fastboot
Edit:
DooMLoRD said:
we cant write to boot partition from recovery... so only way to flash custom kernels is via fastboot...
Click to expand...
Click to collapse
Sent from my LT15i using XDA Premium App

yes but if doomlord and CM7 use the same recovery than we wont have to change the boot.img right?
because you can restore your system from CM7 to stock without flashing boot.img
you just boot it and than restore after that the phone will reboot in boot.img that was already on the phone
not the one you booted this one time to get in CWM

As far as I no cm7 kernel will not work on stock rom and doomkernel will not work wit cm7 rom
So even if we get same cwm on both neither will boot others rom and you will still have to use fastboot to change kernels because kernels are not compatible with both
This is how I understand it to be ,im no expert tho
Can someone confirm this
Sent from my LT15i using XDA Premium App

I have to agree with you but than : howecome my method works ?

depulle87 said:
yes but if doomlord and CM7 use the same recovery than we wont have to change the boot.img right?
because you can restore your system from CM7 to stock without flashing boot.img
you just boot it and than restore after that the phone will reboot in boot.img that was already on the phone
not the one you booted this one time to get in CWM
Click to expand...
Click to collapse
CM7 will require different kernel (ramdisk)...
pushtostop said:
As far as I no cm7 kernel will not work on stock rom and doomkernel will not work wit cm7 rom
So even if we get same cwm on both neither will boot others rom and you will still have to use fastboot to change kernels because kernels are not compatible with both
This is how I understand it to be ,im no expert tho
Can someone confirm this
Sent from my LT15i using XDA Premium App
Click to expand...
Click to collapse
yes u are partly correct...
CM7 kernel should also work on stock THOUGH some functions may/may not work...
my kernel MIGHT NOT work on CM7 as it requires a diff ramdisk... it will boot but some CM7 features/functions might be broken...

Thanx for clarifying
Is it a case that we will never flash kernels without fastboot or is it something that can be solved in later dev
Thanx again
Ps v10 is running v well for me
Sent from my LT15i using XDA Premium App

pushtostop said:
Thanx for clarifying
Is it a case that we will never flash kernels without fastboot or is it something that can be solved in later dev
Thanx again
Ps v10 is running v well for me
Sent from my LT15i using XDA Premium App
Click to expand...
Click to collapse
there is always a possibility... but currently we cant...

No limits I like it
Thanx again
Sent from my LT15i using XDA Premium App

so better not use this method ?
better to delete it ?

No ur first is correct and is at the mo the only way to switch between the two roms while maintaining data
Sent from my LT15i using XDA Premium App

[mod][PATCH][AROMA] ROM_PATCH v1.2 for ics- full freedom

thanks a lot to amarullz for providing aroma installer, and thanks to nightshack0 I have taken his installer and modded to work according to my need but dont think that I have just copied and pasted the installer
had you ever feel that another galaxy s variant's forum have a ics rom which suits all your need but you cannot flash it because it is not yet ported to your device but now all this will not happen again with this patch you can install which ROM you want to flash there will be no boundation for you.
if you are getting status 7 or getprop error then a little work from your side is needed
extract the rom to a folder then go to /extracted folder/META - INF/com/Google/Android
from there open updater-script and remove all getprop lines
come back to META - INF folder and delete all three files
zip the file and flash it in recovery
NOTE:- to edit updater script use jota text editor(android), notepad++(windows)
Click to expand...
Click to collapse
this patch will let you flash other I9000 or t959 roms I have not tried it on other variant but you can try and let me know if it works, I have tried to flash a nexus s rom and it was not flashing so just flash and let me know there is no harm no soft brick no hard brick just physical button will not work until you flash this patch or another rom
Click to expand...
Click to collapse
how to use this patch:- first flash the rom you wanted then this patch and if rom is not flashing read the FAQ
Click to expand...
Click to collapse
download link
*AROMA compatible v1.2:- http://bit.ly/rompat12 (39mb)
* AROMA compatible v1.1:- http://bit.ly/JpHy83 (41mb)
* CAPRIVATE patch v1.0:- http://db.tt/35H5A9mH
Click to expand...
Click to collapse
PROS:- 1.flash which ics rom you want
2. new world with more rom have been revealed
3. rom chefs work have been reduced because now they do not need to port their rom.
4. small size just 12mb
5. TWRP kernel is pre bundled thanks to KRARVIND
Click to expand...
Click to collapse
CONS:- 1. you cannot get the build properties(build.prop) of the rom you are flashing instead you will get the build property which will not be related to any ics rom
Click to expand...
Click to collapse
the patch do not contains any file which can cause a bug and patch will only work on ics roms not gb
For further clarification read FAQ on second post
update:- keep the thanks coming guys and I will add the support of aroma installer and new things just keep me encouraged by pressing thanks
Click to expand...
Click to collapse
update 2:- hi all if you like my work please rate this thread with 5 stars and also submit it as news tip
Click to expand...
Click to collapse
update:- flashed fascinate rom by editing updater script and without resigning got it booted up but it cleared my efs folder so was not getting any network coverage, I got very depressed tried cleared data restore nandroid but nothing works then I thought about efs and with the backup I copy imei files to efs folder and after reboot I got coverage now I will not flash any fascinate rom just for testing but I can say that fascinate rom are working
Click to expand...
Click to collapse

PATCH FAQ
FAQ
Q.:- how to use this installer
Ans:- don't worry about this all the instruction have been given in the installer you just need to flash the package in recovery it is just like installation wizard of windows
Click to expand...
Click to collapse
Q.:- will this also work on gb rom
Ans:- no the patch contains a kernel which cannot work with gb rom
Click to expand...
Click to collapse
Q:- while flashing a galaxy s ics rom I got an error of assert failed what to do.
Ans:- first flash this patch then go to advance and select reboot recovery with new TWRP recovery flash the rom then again flash patch
Click to expand...
Click to collapse
Q.:- why you provided custom build.prop.
Ans:- if build.prop will not be provided then rom's build.prop will change you device's build properties which will not letyou flash files specially created for captivate
Click to expand...
Click to collapse
Q.:- can I flash another captivate ics kernel
Ans:- yes you can flash
Click to expand...
Click to collapse
Q.:- can I flash a kernel I9000 or T959
Ans:- no you cannot flash
Click to expand...
Click to collapse
Q.:- can you give some info about TWRP kernel
Ans:- a bigmem kernel with 720p recording patch originally can be found in Slim Ice rom thanks KRARVIND for this
Click to expand...
Click to collapse
Q.:- what can happen if I forgot to flash this patch
Ans:- nothing serious just the physical keys (menu, back etc.) will not work except this everything will be normal just boot to recovery and flash the patch and keys will work again
Click to expand...
Click to collapse
Q.:- I like your work where can I donate you
Ans:- my work is not that much to be donated and I got pocket money from my father I am just a teenager of seventeen just press thanks button and rate this thread with 5 stars, I will be happy
Click to expand...
Click to collapse
Q.:- Is there any modem provided Ans:- no, there is no modem in the package and will be provided in next update following in 3-5 days
Click to expand...
Click to collapse

WHAT'S NEW
v1.2
1. added bootanimation support
2. removed 30 data fix script
3. added vold.fstab
4. added shutdown charging animation files
5. only single modem is there to decrease size of the patch
6. added a new splash screen
v1.1
1. Added support of AROMA INSTALLER (thanks AMARULLZ)
2. Updated Semaphore kernel
3. Removed some unwanted files
4. Added some Init Scripts
5. Removed Lib files
6. Added Modem.bin

tested roms
a list of tested roms is here
1. infinitum (currently ported)
2. myics ultimate fusion
3. galaxy s cm9 kang build
4. team icssgs

Interesting. Will check it out
Sent from my SGH-I897 using xda premium

Interested to try this out... waiting for link. I'm feeling daring today.
edit: thread updated while I was posting- I'll report back when I try it out.

cool... So where is the link?
Sent from my SGH-I897 using XDA

guys I have just created the thread it will take time to complete link have been added

oooh whats this lol
sorta like Hellraiser from the infuse forum

Cool it's there yeah let's see )))))
Sent from my SGH-I897 using XDA

Really? Wow! that sounds awesome!! Gonna try it for sure.

Any feedback? Lol
Just to clarify
I flash this after ANY ICS rom on Any(galaxy s) Phone?(Such as Galaxy s II) Or Just for vibrant?
Also I flash the patch first then the rom Of My choice? Or what o.o

[email protected]$$ GONNA TRY THIS OUT NOW!
Sent from my SGH-I897 using xda premium

Can somebody explain how the hell I use this o.o Im confused

patrick8996 said:
Can somebody explain how the hell I use this o.o Im confused
Click to expand...
Click to collapse
Hi confused! I'm perplexed. Would like to this as well.
Sent from my SGH-I897 using xda premium

shaker2k said:
Hi confused! I'm perplexed. Would like to this as well.
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
Lol Guess Im gonna try it o.o
Gonna flash this patch and find advanced(wherever that may be) and then flash an SGSII Rom

patrick8996 said:
Lol Guess Im gonna try it o.o
Gonna flash this patch and find advanced(wherever that may be) and then flash an SGSII Rom
Click to expand...
Click to collapse
I think it's just i9000 and i9020 (google nexus). Not sure though.

swayjd said:
I think it's just i9000 and i9020 (google nexus). Not sure though.
Click to expand...
Click to collapse
damn it o.o

so i can flash a nexus one ics rom on my cappy? i dont get it

@OP, can you explain us what this does?

[4.0.4 Rom] CyanogenMod 9 [Built From Source] - Alpha Stage - Flash with Caution

Hello! This is a CM9 I built from source some days ago using CM9 device & vendor tree made by Ivan/qiwu (big thanks to him for this)
This ROM is in really early stage.
IT CAN BRICK YOUR DEVICE !!! FLASH CAREFULLY !!! YOU HAVE BEEN WARNED !!!
What works:
I think everything works apart from camera !
I have tested this rom on my phone before uploading. When I rebooted in recovery through the reboot menu of the ROM my device was hard-bricked. That means I sent it to service in order to repair it!
In this rom I intergrated a fix for camera and also for recovery I think.
Still you are NOT encouraged to reboot into recovery from within the ROM unless you want to test how lucky you are.
You can flash this rom and tell me what other things may not work correctly and also try to make your own fixes for the problems mentioned above.
Flash via CWM 5.0.2.7
1) Wipe data/factory reset
2) Advanced-> Wipe Dalvik Cache
3) Instal from .zip in sdcard
Notes:
1)Installation will get a lot of time. No other rom took me so much ever. Just wait patiently and it will eventually end
2)If you have no baseband/imei=null try using the amss.mbn from gingerbread pinkscreen image folder -> aka the gingerbread baseband file
Download link: https://sourceforge.net/projects/moidroid/files/CM9_U8800Pro_Alpha.zip/download
AGAIN I'M NOT RESPONSIBLE FOR ANY DAMANGE TO YOUR DEVICE !!! NO ONE FORCED YOU TO FLASH THIS ROM !

Thank you Moihack! I can't believe how much Qiwu Huang has helped us... Good luck with this project

Moihack said:
In this rom I intergrated a fix for camera and also for recovery I think.
Click to expand...
Click to collapse
Camera don't work:crying:

macros95 said:
Camera don't work:crying:
Click to expand...
Click to collapse
error is still : "cannot connect to camera" ?
well even so, thank you very much for trying though. I can't properly test till I get my phone back from service.

error is still : "cannot connect to camera" ?
Click to expand...
Click to collapse
Yes

Awesome! Moihack thanks a lot i cant try it. But still I know i can somehow feel you did a hell of an amazing job
Sent from my U8800Pro using Tapatalk 4 Beta

Wow,wait. You compiled a 4.0 ROM with 4.2 source?

forumber2 said:
Wow,wait. You compiled a 4.0 ROM with 4.2 source?
Click to expand...
Click to collapse
You are a fool?

Is the problem only with the stock camera app or generally with all of them?

forumber2 said:
Wow,wait. You compiled a 4.0 ROM with 4.2 source?
Click to expand...
Click to collapse
of course not. ivan also made device & vendor tree for cm9 for u8800pro
it isn't available at his github anymore , but the lewa os team (ioz9 at github) had made a fork
@ svteam : I didn't try any other cameras but I think you 'll get the same errors. Some libraries and maybe some bin files may need to be changed in order for camera to work.
@ rittik : thanks! hope you can fix the non-working camera or/& the recovery issue
be careful with the recovery fix though! it may brick your device.

Moihack said:
of course not. ivan also made device & vendor tree for cm9 for u8800pro
it isn't available at his github anymore , but the lewa os team (ioz9 at github) had made a fork
@ svteam : I didn't try any other cameras but I think you 'll get the same errors. Some libraries and maybe some bin files may need to be changed in order for camera to work.
@ rittik : thanks! hope you can fix the non-working camera or/& the recovery issue
be careful with the recovery fix though! it may brick your device.
Click to expand...
Click to collapse
I cant do anything on U+ now. Got imei 0 cant restore it..i am not sending it back to centre. May be looking at some new phones now. But will try to fix for sure.
Sent from my U8800Pro using Tapatalk 4 Beta

Tried pika's step by step imei flashing. worked for me for '0' imei problem
Sent from my U8800pro using xda app-developers app

Rittik said:
I cant do anything on U+ now. Got imei 0 cant restore it..i am not sending it back to centre. May be looking at some new phones now. But will try to fix for sure.
Sent from my U8800Pro using Tapatalk 4 Beta
Click to expand...
Click to collapse
You can find some local mobile repair store,they will create imei. Ask some one near by you
Sent from my U8800pro

@Moihack is any update in your plans for this incredible ROM?

NickVXD said:
@Moihack is any update in your plans for this incredible ROM?
Click to expand...
Click to collapse
I'm not gonna try my luck again with CM9. Whenever I try, my phone hard bricks
The only thing not working though is camera. If you are interested PM. I have some ideas which may result in a fix

binoj.6066 said:
You can find some local mobile repair store,they will create imei. Ask some one near by you
Sent from my U8800pro
Click to expand...
Click to collapse
You sure? They rewrite the imei rite? Then I will try and go
Sent from my GT-I9152 using Tapatalk 4 Beta

Rittik said:
You sure? They rewrite the imei rite? Then I will try and go
Sent from my GT-I9152 using Tapatalk 4 Beta
Click to expand...
Click to collapse
But if u find another motherboard on THE NET?
Inviato dal mio U8800Pro con Tapatalk 2

I aint gonna spend a single penny on upro now.
Sent from my GT-I9152 using Tapatalk 4 Beta

Cm7 compitable baseband?

I am on Hyperion final and tried to flash aosp 2.3.7 , y-escape , cm7 by biel.tv , kitkat experience v1.1 and they doesn't boot, stuck on bootanimation, and sometimes it pass it and vibrates for long time, in kitkat experience it booted fine then the screen turned green with strong vibrations, in aosp it doesn't even pass the boot logo
I performed a full wipe and formatted partitions many times, mounting every thing, redownloaded roms, So I think it is a baseband problem, anyone please tell me the cm7 comptiable baseband.
Note : I am on DXLL1.
Sent from my GT-S5360 using Tapatalk 2

Use DDLK2 as baseband and then flash the roms.When you have flashed your desired rom,flash the CSC of your region.

mohamedrashad said:
I am on Hyperion final and tried to flash aosp 2.3.7 , y-escape , cm7 by biel.tv , kitkat experience v1.1 and they doesn't boot, stuck on bootanimation, and sometimes it pass it and vibrates for long time, in kitkat experience it booted fine then the screen turned green with strong vibrations, in aosp it doesn't even pass the boot logo
I performed a full wipe and formatted partitions many times, mounting every thing, redownloaded roms, So I think it is a baseband problem, anyone please tell me the cm7 comptiable baseband.
Note : I am on DXLL1.
Sent from my GT-S5360 using Tapatalk 2
Click to expand...
Click to collapse
What kernel do you use? This problem of bootloop mostly occurs on stock kernel. Try to change kernel and try to flash again. There are so many kernels you can choose from. Don't ask me the link. Search it yourself.
You can use Percy's Cyanogenmod kernels for flashing the ROM based on CM.
Here's the link to the kernel thread: Click here to view
If it doesn't solve your problem, feel free to PM me.
Press thanks if I have helped you.

the_pirate_predator said:
What kernel do you use? This problem of bootloop mostly occurs on stock kernel. Try to change kernel and try to flash again. There are so many kernels you can choose from. Don't ask me the link. Search it yourself.
You can use Percy's Cyanogenmod kernels for flashing the ROM based on CM.
Here's the link to the kernel thread: Click here to view
If it doesn't solve your problem, feel free to PM me.
Press thanks if I have helped you.
Click to expand...
Click to collapse
I am on hells fusion 50
I flash percy cm2 and format every thing then install, still doesn't boot
Sent from my GT-S5360 using Tapatalk 2

aniket.lamba said:
Use DDLK2 as baseband and then flash the roms.When you have flashed your desired rom,flash the CSC of your region.
Click to expand...
Click to collapse
Will try this
Sent from my GT-S5360 using Tapatalk 2

mohamedrashad said:
I am on hells fusion 50
I flash percy cm2 and format every thing then install, still doesn't boot
Sent from my GT-S5360 using Tapatalk 2
Click to expand...
Click to collapse
theres your problem right there - you are not on an ext4 system partition which is required to boot cm7
flash percys kernel in cwm with system mounted
now for the important part
REBOOT TO RECOVERY!
you must reboot to recovery after flash the kernel - do not just flash the rom without rebooting to recovery
once you have rebooted to recovery you may have mount errors - ignore them
format system
format data
format cache
mount system
mount data
mount cache
install from zip and select cm7
format data again
optional steps
mount system
flash gapps
restart

I do everything you said but I dont do format data after flash, ok, I will try this and tell you in some time, Thanks
Sent from my GT-S5360 using Tapatalk 2

mohamedrashad said:
I do everything you said but I dont do format data after flash, ok, I will try this and tell you in some time, Thanks
Sent from my GT-S5360 using Tapatalk 2
Click to expand...
Click to collapse
remove your sim card - if it boots then you know its baseband

mohamedrashad said:
I am on Hyperion final and tried to flash aosp 2.3.7 , y-escape , cm7 by biel.tv , kitkat experience v1.1 and they doesn't boot, stuck on bootanimation, and sometimes it pass it and vibrates for long time, in kitkat experience it booted fine then the screen turned green with strong vibrations, in aosp it doesn't even pass the boot logo
I performed a full wipe and formatted partitions many times, mounting every thing, redownloaded roms, So I think it is a baseband problem, anyone please tell me the cm7 comptiable baseband.
Note : I am on DXLL1.
Sent from my GT-S5360 using Tapatalk 2
Click to expand...
Click to collapse
DDMD1 is the best baseband for CM7!
Press Thanks if it helped!

lionelsuyog said:
DDMD1 is the best baseband for CM7!
Press Thanks if it helped!
Click to expand...
Click to collapse
there is no 'best' baseband - just those that will work and those that wont
theres no point using ddmd1 if you are from europe for example - much better using a firmware starting xx and not dd in that case - not everyone is from india

marcussmith2626 said:
there is no 'best' baseband - just those that will work and those that wont
theres no point using ddmd1 if you are from europe for example - much better using a firmware starting xx and not dd in that case - not everyone is from india
Click to expand...
Click to collapse
I'm not from India! Im a Nepali! (No Offence) And yeah I 2 experienced problem while using DXLL1, but when I updated it to DDMD1, CM7 worked fine! :good:

lionelsuyog said:
I'm not from India! Im a Nepali! (No Offence) And yeah I 2 experienced problem while using DXLL1, but when I updated it to DDMD1, CM7 worked fine! :good:
Click to expand...
Click to collapse
DD is indian firmware which is why I said india
DX is Indonesia, Malaysia, Philippines, Singapore, Vietnam
They may inlude other countries which can also use these firmwares fine - it is region based not specific countries
its best to flash a firmware from your region which is why I said people from europe shoud flash a firmware starting with XX
If it works for you great

[Q&A] [PATCHER][APP] Dual boot any ROM on all Galaxy S4 variants!

Q&A for [PATCHER][APP] Dual boot any ROM on all Galaxy S4 variants!
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

Support for Galaxy S4 Mini GT-I9195
Hi, I tried this on a GT-I9195 using the "Galaxy S4" preset... Both ROMs seem to be installed, but once I install the second ROM, there doesn't seem to be any way to boot back into the first ROM.
I'd love for this to work on my device (serranoltexx). Could I help add support for this device in some way?
Thanks

utjunkie said:
Hi, I tried this on a GT-I9195 using the "Galaxy S4" preset... Both ROMs seem to be installed, but once I install the second ROM, there doesn't seem to be any way to boot back into the first ROM.
I'd love for this to work on my device (serranoltexx). Could I help add support for this device in some way?
Thanks
Click to expand...
Click to collapse
I started to wonder how did you install them in the first place???

qtwrk said:
I started to wonder how did you install them in the first place???
Click to expand...
Click to collapse
There were no errors and both ROMs are physically taking up the space; just it boots into the second ROM no matter what I do. It sounds like it's pretty close, can I help make this work?

Dual Boot with MIUI 4.9.26
Hello,
i tried to install the MIUI v5 4.9.26 Multilang but I got the error in the picture attached to this post.
Could you help me to install It? I have Omega ROM for first space and for the second I would install MIUI. I've already patched the ROM with the app for Android on the Omega and the tool create a dual.zip of the original MIUI ROM. I tried to flash it from recovery (TWRP 2.8.0.1 with Aroma MOD)
Thanks,
Whity

utjunkie said:
There were no errors and both ROMs are physically taking up the space; just it boots into the second ROM no matter what I do. It sounds like it's pretty close, can I help make this work?
Click to expand...
Click to collapse
i assume you followed instruction precisely ?
tried both app switcher and zip file switcher ?

Cam someone send me the link to the snapshots?
Sent from my GT-I9505 using Tapatalk 2

Alucard 1.4oc kernel issues
Hey, i am trying to flash Alucard 1.4oc over SlimKat on my Dual partition.. The patched script seems to install fine, but my boot just stops at the Samsung logo, vibrates twice and restarts... I can see that they made some changes to their updater_script, but I have not figured out if this is the source of my problems,or if it is not related to my multi-boot at all..
So, i just wanted to know if anyone has patched 1.4oc on anything other than Primary with success.

App Sharing
twcobra said:
+1
Click to expand...
Click to collapse
sronweb said:
As I understood from previous posts there is some work in progress but nothing yet released. Currently you can share only apps (which is a lot for me...)
Click to expand...
Click to collapse
Well, I was trying to reply to the question on app sharing. I have used both the full share and the individual. I stopped the full share because of the differences between Gapps with the different ROMS. However, the full share seems like a better bet because it is a straight swap of partitions. The individual app sharing has been working, but as it has been noted, data is not part of that... Also, i find the use of hard links challenging when i am trying to look at my filesystem and figure out what is where. Not to mention that it doesn't really let you manage all the apps you care about for all the ROMS in one place. I have needed to go to every ROM if i want to uninstall a shared app and really have it go away.
that said, i don't really want to go down the path of partitioning my external sd card and using something like Link2SD. I am going to wait and see what our patch master produces for his latest updates that try to handle sharing of data, as well.

Response to Primary Rom update question
1) From recovery, flash the DualBootUtilities
2) Select Primary
3) Do a full wipe
4) Exit to recovery
5) From recovery, install your new primary ROM as usual
The big point noted by the OP is to avoid using recovery wipe utilities because they may wipe parts/all of secondary ROMS (those in Dual and MultiSlots)
---------- Post added at 09:58 PM ---------- Previous post was at 09:40 PM ----------
So, I can get these kernels to boot up fine from the primary ROM which is current some recent nightly of CM11
However, when i flash over my dual (SlimKat 8.10) or multi-slot-1 (DirtyUnicorns v8.2) i can't get past the initial Samsung logo. The phone vibrates once .... twice .... then reboots.
EDIT: I should note that i have 2 other kernels that are booting fine for my secondary ROM
Can someone confirm if they are using either of these Alucard kernels succesfully on something other than the PRimary ROM.
thanks

FuzzyPete said:
1) From recovery, flash the DualBootUtilities
2) Select Primary
3) Do a full wipe
4) Exit to recovery
5) From recovery, install your new primary ROM as usual
The big point noted by the OP is to avoid using recovery wipe utilities because they may wipe parts/all of secondary ROMS (those in Dual and MultiSlots)
---------- Post added at 09:58 PM ---------- Previous post was at 09:40 PM ----------
So, I can get these kernels to boot up fine from the primary ROM which is current some recent nightly of CM11
However, when i flash over my dual (SlimKat 8.10) or multi-slot-1 (DirtyUnicorns v8.2) i can't get past the initial Samsung logo. The phone vibrates once .... twice .... then reboots.
EDIT: I should note that i have 2 other kernels that are booting fine for my secondary ROM
Can someone confirm if they are using either of these Alucard kernels succesfully on something other than the PRimary ROM.
thanks
Click to expand...
Click to collapse
Ok, got my kernel patched and working. As it stands right now, it looks like the current releases of the Alucard AOSP kernel (1.4oc) do not patch correctly. I confirmed this for 1.4h and 1.4oc. It took a lot of painful sleuthing, but i finally determined that the Alucard kernel for AOSP gets a patch for the init binary. I could not tell from the commits why this was needed originally, but it appears that Alucard changed something on his end, or the ROMS have changed something else on their end or whatever.. Regardless, the init_kk binary is now incompatible with 1.4 AOSP kernel.. I didn't have a dev environment handy to just change the config and rebuild the DualPatcher app, so i did the following to confirm:
1) Ran the DualPatcher app for the 1.4oc kernel
2) Started recovery, and flashed the patched kernel
3) went to the shell, unpacked the ramdisk and replaced the patched init with the original from the Alucard kernel ramdisk
4) repacked the boot.img, copied it to MultiKernels
5) rebooted
At this point, my ROM booted fine.

9.0 Apk crashing
I also have the same problem. Tried to patch several different ROM for S5 but the app crashes at 0%. Using the 9.0 app

App crashes 9.0
I have the same problem. 9.0 app crashes at 0% when trying patch S5 dual boot ROM. Changed to standard patcher option and tried various ASOP ROMs.

Tried to patch 5.0 PA GAPPs with latest dbug apps failed. Patched CM12 is running ok.

I have a problem updating my ramdisk on the secondary rom(slimkat 4.4.4), can you help me?

I have a problem failed to patch kennel..
Both on v9 debug and v8
I am on ozcan rom v6.2
I have also tried on CM12 but does not work please help

ouwesh said:
I have a problem failed to patch kennel..
Both on v9 debug and v8
I am on ozcan rom v6.2
I have also tried on CM12 but does not work please help
Click to expand...
Click to collapse
Use the 17mb version on alpha 9.0

Dualboot TW Update
Hi guys,
I'm using the Dualbootoption developed inhere. As primary I'm using TW, as secondary DirtyUnicorns. Now the thing: I could make a Update of Touchwiz by Kies. I now, Root Rights will be removed and the Bootloader will be closed. So after the update I have to unlock the Boodloader and to root the Phone again to use the Dualboot Option or only to unlock the bootloader.
Just a few Information please
Best Regards,
Aeneas

AeneasG said:
Hi guys,
I'm using the Dualbootoption developed inhere. As primary I'm using TW, as secondary DirtyUnicorns. Now the thing: I could make a Update of Touchwiz by Kies. I now, Root Rights will be removed and the Bootloader will be closed. So after the update I have to unlock the Boodloader and to root the Phone again to use the Dualboot Option or only to unlock the bootloader.
Just a few Information please
Best Regards,
Aeneas
Click to expand...
Click to collapse
I think you must be rooted to set the kernel for your primary rom, and also have an unlocked bootloader to have custom recovery so you can flash dualboot patched roms

jigsawcrank said:
I think you must be rooted to set the kernel for your primary rom, and also have an unlocked bootloader to have custom recovery so you can flash dualboot patched roms
Click to expand...
Click to collapse
Yeah that's clear. But I have the dualboot option yet. To change after the update its enough only to root the smartphone or also to unlock the Bootloader?
Regards,
Aeneas