[L5][E610/E612][ROM]Dual Boot CM10 and CM11 - Optimus L3, L5, L7 General

[L5][E610/E612][ROM]Dual Boot CM10 and CM11 - Optimus L3, L5, L7 General

thats very cool,but why only cm and why only between 10 and 11?

-CALIBAN666- said:
thats very cool,but why only cm and why only between 10 and 11?
Click to expand...
Click to collapse
In the private'm doing a test between the stock JB and cm11, just have to see a problem from cm11 that is giving bootloop, could have other ROM also like cm12.1 but I have no recent builds so it has no way, or also the stock ICS along with some cm, could have Trialboot there is also one thing that can prevent is creativity and your memory card hehe

Well done Jonas.

GreekDragon said:
Well done Jonas.
Click to expand...
Click to collapse
Thx man

It's a great tool for L5

Well, i was trying to figuring out own to port the dual boot function to any roms, did not succeed, if anyone know what i did missed in those step would be cool to share.
Using the CM11 dual boot file from the host, uncompress it and take the following 2 file and insert it in each zip.
-/system/bin/change_system
-/system/app/SystemChanger.apk
Finally take the boot.img from Rom 1 and insert it in /system/boot of Rom 2, does the same thing with for the other zip. Might work, i will edit if it does. This is according to the original zip file for the stock ICS roms.
Now you will need to modify your updater-script of your sd card roms, replace all the following correspondance by the other one aside.
"/dev/block/platform/msm_sdcc.3/by-num/p14" to "/dev/block/mmcblk1p2"
Also, because you will use 2 sd card partition and there's no way to format them, before it's the mount time, add the following line before mount :
format("ext4", "EMMC", "/dev/block/mmcblk1p3", "0", "/data");
format("ext4", "EMMC", "/dev/block/mmcblk1p2", "0", "/system");
Finaly, modify the package_extract_file at the end of the script with :
package_extract_file("boot.img", "/dev/block/mmcblk0p9");
Save, rezip, double check everything, transfert to sd card.
When done, do the same as the OP said with your personal zip file of Roms, flash and pray.

I need a tester wants to be?
Atari-San said:
Well, i was trying to figuring out own to port the dual boot function to any roms, did not succeed, if anyone know what i did missed in those step would be cool to share.
Using the CM11 dual boot file from the host, uncompress it and take the following 2 file and insert it in each zip.
-/system/bin/change_system
-/system/app/SystemChanger.apk
Finally take the boot.img from Rom 1 and insert it in /system/boot of Rom 2, does the same thing with for the other zip. Might work, i will edit if it does. This is according to the original zip file for the stock ICS roms.
Now you will need to modify your updater-script of your sd card roms, replace all the following correspondance by the other one aside.
"/dev/block/platform/msm_sdcc.3/by-num/p14" to "/dev/block/mmcblk1p2"
Also, because you will use 2 sd card partition and there's no way to format them, before it's the mount time, add the following line before mount :
format("ext4", "EMMC", "/dev/block/mmcblk1p3", "0", "/data");
format("ext4", "EMMC", "/dev/block/mmcblk1p2", "0", "/system");
Finaly, modify the package_extract_file at the end of the script with :
package_extract_file("boot.img", "/dev/block/mmcblk0p9");
Save, rezip, double check everything, transfert to sd card.
When done, do the same as the OP said with your personal zip file of Roms, flash and pray.
Click to expand...
Click to collapse

It seems that You files (change_system and SystemChanger.apk) are not device dependent of device or I'm mistaken?
Anyway that using this two filed I could try to make dualboot on my L7? If You say to try it I will try to add Your CM10 Room as second to my L7.
Any chance for brick? It doesn't look to dangerous, but... You are the dev

ch3mn3y said:
It seems that You files (change_system and SystemChanger.apk) are not device dependent of device or I'm mistaken?
Anyway that using this two filed I could try to make dualboot on my L7? If You say to try it I will try to add Your CM10 Room as second to my L7.
Any chance for brick? It doesn't look to dangerous, but... You are the dev
Click to expand...
Click to collapse
The logic as executed the process is the same, but in the CM10 kernel which is the secondary ROM has some modifications to recognize the location of the ROM is the card partitions, e.g., as you say to make dual boot between ROM Door mine and some other ROM L7 (Kitkat for example), you would have to edit the kernel of my rom door, as the basis of the ROM looks like it may be that using her kernel function, however necessarily have to install a kernel for top of it because it has some different things, and also the part of the baseband in each ROM there is a folder with her baseband another, CM10-> v20 and CM11-> v10, and also a boot folder that contains the boot the other, that when executed by the app are exchanged, the phone restarts with the ROM kernel and exchanged baseband, sure can give softbrick with but a backup solves only the baseband you have be attentive, I can even try to do but someone would that test because I'm not have a L7

Ahh, seemed s easy
I could test, as I my L7 just became my 4th device, so no big loss if bricked (but I'm not saying that I would like it).

ch3mn3y said:
Ahh, seemed s easy
I could test, as I my L7 just became my 4th device, so no big loss if bricked (but I'm not saying that I would like it).
Click to expand...
Click to collapse
Soon a dev here in xda will bring a better tool muiti boot

Good to know. However I had a chance before to use it on my 2 other devices, but never get need for it.

The DualBootPatcher - http://forum.xda-developers.com/opt...-custom-roms-l5-soon-l7-t3276182/post64459854
The tool for multiboot

Related

[THE FINAL TOOL][EASY TO USE]★★★ AIO Android Toolkit 7.5 ★★★ [= May/04/2013 =]

[THE FINAL TOOL][EASY TO USE]★★★ AIO Android Toolkit 7.5 ★★★ [= May/04/2013 =]
:victory: Welcome to the...
All In One Android Toolkit :victory:
===========================================================================================
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PLEASE USE THIS TOOL WITH CAREFULLY!
ME AND XDA ARE NOT RESPONSIBLE FOR ANY KIND OF DEVICE BREAKING!
ANY WAYS...THIS IT'S TOTALLY NOOB FRIENDLY :silly:
===========================================================================================
===========================================================================================
:silly: Want to Wipe your phone, Flash something, Resize system partitions, Install an app, Push a file to your phone, etc... without complications?
Then use this tool, Just Download, and install! Easy!
===========================================================================================
So...The screenshots are worth than a thousand words:
===========================================================================================
I hope this will help you to make your android life better and easy!
Press "Thanks" Button if you like this!
ChangeLog: http://forum.xda-developers.com/showpost.php?p=29502481&postcount=31===========================================================================================

===========================================================================================
Credits: Mur4ik (MBN files), Gigadroid (Backup Tool), roman10 (Screenshot jar)

good one but... Put proper credits!! E.g Mur4ik for the MBN files!!

-Grift- said:
good one but... Put proper credits!! E.g Mur4ik for the MBN files!!
Click to expand...
Click to collapse
Added, Sorry, was a quick thread

I use 210mb partition for every rom, does that effect anything or is it fine??
Sent from my GT540 using XDA

it is fine but you have smaller usage for data

mohnim said:
I use 210mb partition for every rom, does that effect anything or is it fine??
Sent from my GT540 using XDA
Click to expand...
Click to collapse
It's fine for an ICS ROM, but if you want more space to apps on GB ROM, reduce to 160 or 170.

i think for gb 150 is fine

-Grift- said:
i think for gb 150 is fine
Click to expand...
Click to collapse
If you delete some unuseful apps

my gb roms always fit 150 o.o

-Grift- said:
my gb roms always fit 150 o.o
Click to expand...
Click to collapse
I think, not the new ones, with GAPPS integrated and other heavy apps.

ah yes never got to try new ones so i guess its true.
Edit: maybe you can make a all in one .bat file so its like
Wipe Menu
1.Full wipe (cache and data)
2.Partial wipe (cache only)
3.Wipe boot
4.Wipe system
5.Wipe recovery
Flash Menu
6.Flash boot.img
7.Flash system.img
8.Flash data.img
9.Flash recovery.img
Partition Menu
10.Flash 150Mb system partition GingerBread
11.Flash 170Mb system partition GingerBread
12.Flash 200Mb system Partition ICS
13.Flash 220Mb system partition ICS
14.Flash 250Mb system partition ICS (stock)

-Grift- said:
ah yes never got to try new ones so i guess its true.
Edit: maybe you can make a all in one .bat file so its like
Wipe Menu
1.Full wipe (cache and data)
2.Partial wipe (cache only)
3.Wipe boot
4.Wipe system
5.Wipe recovery
Flash Menu
6.Flash boot.img
7.Flash system.img
8.Flash data.img
9.Flash recovery.img
Partition Menu
10.Flash 150Mb system partition GingerBread
11.Flash 170Mb system partition GingerBread
12.Flash 200Mb system Partition ICS
13.Flash 220Mb system partition ICS
14.Flash 250Mb system partition ICS (stock)
Click to expand...
Click to collapse
I'll try this on next week, thanks for the idea

I have a question, i just want to have a clean install of my next rom, because i installed quite a few in the past and saw that not all the files from other roms were deleted from the root folder. So can i just use your first part of your tutorial to totally clean the phone from old and unnecessary files and make a clean flash right after from cwm?
I would like to keep my partitions right as they are now, i just want to have all files and folders out of my root directory because i can see that a lot of files there have old creation dates and i think they arent needed anymore with my current rom.

FeuchtVonLipwig said:
I have a question, i just want to have a clean install of my next rom, because i installed quite a few in the past and saw that not all the files from other roms were deleted from the root folder. So can i just use your first part of your tutorial to totally clean the phone from old and unnecessary files and make a clean flash right after from cwm?
I would like to keep my partitions right as they are now, i just want to have all files and folders out of my root directory because i can see that a lot of files there have old creation dates and i think they arent needed anymore with my current rom.
Click to expand...
Click to collapse
Yes sure, but after run WipeAll.bat file, then you have to reboot your phone manually, how?:
Open cmd window and type:
Code:
fastboot.exe reboot
Then enter and enter to Recovery Mode manually.

okay sounds a bit dangerous but ill try, thank you
i can also just add
"fastboot.exe reboot" to your bat file at the end right?

FeuchtVonLipwig said:
okay sounds a bit dangerous but ill try, thank you
i can also just add
"fastboot.exe reboot" to your bat file at the end right?
Click to expand...
Click to collapse
Yes at the end.

I'm preparing a huge update for this tool, i think will be the most complete fastboot tool for out swift!
Stay tuned!

Updated OP! with my new tool!
Added more options and now you can flash your recovery ROM via Fastboot Mode!
Not testing everything, but if something are wrong, please tell me to fix it!
Happy Android Life!

leoposas said:
Updated OP! with my new tool!
Added more options and now you can flash your recovery ROM via Fastboot Mode!
Not testing everything, but if something are wrong, please tell me to fix it!
Happy Android Life!
Click to expand...
Click to collapse
Aww nice :3

Totally noob friendly!, good job :]

[RECOVERY] HighOnAndroid v1 Unofficial ClockworkMod Recovery Touch 6.0.1.1

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've put together an unofficial ClockworkMod Recovery 6.0.1.1 until Koush adds to ROM Manager, tested working for all features except SD card mount. Working on the latter at the moment.
UPDATE: This recovery does work for both GT-N8000 (3g version) and GT-N8013 (wifi version), just confirmed. (8/16/2012)
Notes:
v1 - Touchscreen is a bit if when you have to scroll, please use the volume buttons for scrolling otherwise you may get accidental presses.
Changelog:
v1 - Everything working except SD card mount. You can backup/restore/ROM to internal or external SD card and other CWM features functional.
Flash this in ODIN or Heimdall:
Download HighOnAndroid v1 ClockworkMod Recovery 6.0.1.1
Also, here's stock recovery you can flash in ODIN or Heimdall to revert (and get OTA updates):
http://downloadandroidrom.com/file/GalaxyNote10.1/recovery/N8000_StockRecovery.tar
Credits:
Of course to Koush! I used his builder then hacked graphics.c + other files to make it work.

reserved
reserved

Amazing! Can't wait to get my hands on my Note
Sent from my SCH-I535

Way to go buddy!

You built it off builder.ClockworkMod.com, didn't you?
Sent from my GT-P1000

cdesai said:
You built it off builder.ClockworkMod.com, didn't you?
Sent from my GT-P1000
Click to expand...
Click to collapse
I did initially but had to hack it to make it work.

zedomax said:
I did initially but had to hack it to make it work.
Click to expand...
Click to collapse
Hey Zedo! Check your PM !

I noticed it does not actually backup system.img on my device, nor did any of my attempts from the clockworkmod builder site either. It says it, but skips over in reality. This will be important to fix if indeed it is not backing it up...
EDIT: Nevermind... I guess the system.img was hiding from me

Where can I find the backup? From my Tab 10.1 I was used to find it in clockworkmod on the sdcard...

akxak said:
Where can I find the backup? From my Tab 10.1 I was used to find it in clockworkmod on the sdcard...
Click to expand...
Click to collapse
It's in your clockworkmod/backup directory. Now, with the new CWM, it stores backups as pieces of files under clockworkmod/blobs directory. This saves a ton of time when doing multiple backups as "blobs" store bits of your filesystem so when doing similar backups, it's not going to backup everything again.
Make sure you copy the whole clockworkmod folder to hard disk for moving though due to this new blobs feature. Your backup folder sizes might be much smaller because of this blobs thingee.

zedomax said:
I used his builder then hacked graphics.c
Click to expand...
Click to collapse
???
Please tutorial graphics.c ...Thanks by Notonlyeyes

I tried flashing with odin following the procedure on the video and with heimdall also, but when I boot in the recovery there is the stock one...both odin and heimdall say the flash is successful and the binary count increases...I also of course tried downloading the recovery again...any suggestions?

gol-D said:
I tried flashing with odin following the procedure on the video and with heimdall also, but when I boot in the recovery there is the stock one...both odin and heimdall say the flash is successful and the binary count increases...I also of course tried downloading the recovery again...any suggestions?
Click to expand...
Click to collapse
Did you do:
Code:
heimdall flash --recovery recovery.img

There is still no clean return-to-stock package available for the N8013: Could someone who has installed this recovery and NOT rooted their device or made any other modifications to /system please go into recovery, change the backup format to tar (it's in the backup/restore menu), and do a backup? Then please post system.ext4.tar
That will get us a stock unmodified system (including proper permissions and such), which can then be rooted and flashed in Odin to get stock unmodified kernel/recovery images. Unlike the N8000, the N8013 does not yet have a stock image available anywhere.

Zedomax......greatstuff...root access on the N8010 no problem at all
....................................................................................................
Entropy512
Will try to do this now... But it'll be N8010.
Ive got the file for the N8010 on my desktop, but XDA isnt letting me upload the file keeps failing - any thoughts?
Dc
Sent from my GT-N8010 using Tapatalk 2

Entropy512 said:
There is still no clean return-to-stock package available for the N8013: Could someone who has installed this recovery and NOT rooted their device or made any other modifications to /system please go into recovery, change the backup format to tar (it's in the backup/restore menu), and do a backup? Then please post system.ext4.tar
That will get us a stock unmodified system (including proper permissions and such), which can then be rooted and flashed in Odin to get stock unmodified kernel/recovery images. Unlike the N8000, the N8013 does not yet have a stock image available anywhere.
Click to expand...
Click to collapse
Just use this bud:
http://stockroms.net/file/GalaxyNote10.1/rooted/N8013/StockROMs.net-GT-N8013RootInjectedSystem.zip
And remove /system/xbin/su and /system/app/Superuser.apk
Other than those two files, it's completely stock I pulled off my stock N8013.
I could reupload it but it would be the exact same thing as removing the two files.

zedomax said:
Just use this bud:
http://stockroms.net/file/GalaxyNote10.1/rooted/N8013/StockROMs.net-GT-N8013RootInjectedSystem.zip
And remove /system/xbin/su and /system/app/Superuser.apk
Other than those two files, it's completely stock I pulled off my stock N8013.
I could reupload it but it would be the exact same thing as removing the two files.
Click to expand...
Click to collapse
That does the trick. So far I only saw your N8000 dump. .tar would be preferable due to permissions issues, but that issue is fixable with a little bit of time.
I did the same thing with I777... Right now the only RTS packages I have are rooted ones since it's so easy to remove. I really should reupload 100% clean packages (I used to have them, and then the MegaUpload fiasco killed ALL the damn mirrors and I haven't gotten around to reuploading...)
Edit: Oh, it's a zipped-up .tar - misleading, I usually name those either .tar.7z (using 7-zip to compress) or just .tar.gz or .tar.bz2 (standard compressed tarballs)

Entropy512 said:
That does the trick. So far I only saw your N8000 dump. .tar would be preferable due to permissions issues, but that issue is fixable with a little bit of time.
I did the same thing with I777... Right now the only RTS packages I have are rooted ones since it's so easy to remove. I really should reupload 100% clean packages (I used to have them, and then the MegaUpload fiasco killed ALL the damn mirrors and I haven't gotten around to reuploading...)
Edit: Oh, it's a zipped-up .tar - misleading, I usually name those either .tar.7z (using 7-zip to compress) or just .tar.gz or .tar.bz2 (standard compressed tarballs)
Click to expand...
Click to collapse
Well, I am just waiting for samfirmware to upload some official images, rather enjoy some of my note 10.1 first for awhile, it's pretty fascinating device, I've never used a tablet for a long time before getting this one, makes my life more productive. Yeah, what's up with Megaupload, that move by feds should have been illegal.

I have a few questions about root and I was hoping someone could help. I am fairly new to rooting. I have a galaxy nexus that i use CWM Recovery and have root. I need to root my Note but I am not familiar with the binary counter (all is a little different than the nexus was). If I Flash this CWM recovery and root after will the binary counter increase? is the only way to prevent binary counter to inject root? (all CWM will cause it to increase?)
I know i am a noob but any insight would be greatly appreciated!
Thanks guys!

greenzkool said:
I have a few questions about root and I was hoping someone could help. I am fairly new to rooting. I have a galaxy nexus that i use CWM Recovery and have root. I need to root my Note but I am not familiar with the binary counter (all is a little different than the nexus was). If I Flash this CWM recovery and root after will the binary counter increase? is the only way to prevent binary counter to inject root? (all CWM will cause it to increase?)
I know i am a noob but any insight would be greatly appreciated!
Thanks guys!
Click to expand...
Click to collapse
Flashing a recovery or kernel image in Odin will cause the binary counter to increase.
Flashing it using dd or Mobile Odin from a rooted system will not make it increase.
So the "safest" way to root is currently to flash that root-injected system image linked a few posts above, as it's fully unrootable and won't trigger the counter.
I have visitors most of this weekend so won't be able to do much work - once I get my kernel source tree properly set up I'm going to work on getting TriangleAway working on this device.

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

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

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

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

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

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

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

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

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

Yes.

i tried to make it but still the same problems

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

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

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

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

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

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

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

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

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

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

[MOD][UNOFFICIAL] MultiROM v33 for onyx

Reserved
Downloads
in OP for now

Reserved
Please read all about the no-kexec workaround from the author directly, (to avoid duplicity and get latest information), thanks to @nkk71
http://forum.xda-developers.com/showpost.php?p=64248526&postcount=4

Looking forward to this!
Verstuurd vanaf mijn ONE E1003 met Tapatalk

Looks very interesting.
Will this include the ability to install ROMs to SD card in the future since the phone only has 16 GB of internal storage?

Good to see great development on OPX thus far.
I'd like to point out that MultiROM v33 is out now!
Thanks for all the development
Regards.

very cool, i was just looking into that

Hey
So, I've waited long and now is it here *yeah*
Thank you a lot
But I have a (dumb?) question: Where do I have to download Sailfish OS? I know, in the "Sailfish wiki" but I didn't find it. Maybe it's WIP and it's not finished yet, but if it's somewhere in the world wiiiiideee web, please post a link, because I'm very interested to this ROM.
Sorry for my Bad english

IchBinNoob said:
Hey
So, I've waited long and now is it here *yeah*
Thank you a lot
But I have a (dumb?) question: Where do I have to download Sailfish OS? I know, in the "Sailfish wiki" but I didn't find it. Maybe it's WIP and it's not finished yet, but if it's somewhere in the world wiiiiideee web, please post a link, because I'm very interested to this ROM.
Sorry for my Bad english
Click to expand...
Click to collapse
Salfish OS is WIP and there isn't a download link. You can find the post in "OnePlus X General"

DavyA said:
Salfish OS is WIP and there isn't a download link. You can find the post in "OnePlus X General"
Click to expand...
Click to collapse
Yeah, thanks I already knew the post, but I want to test it now

Any bug list? or things that needs to improve?

Just curious whether or not you're using MM sources included in the new TWRP with eng.stk's commits. Great work

It is testing and will be some bug.
Yes, it's a old build and in the next days I'll build with new sources

finally.. waiting for multirom-enabled kernel for 1+x..

DavyA said:
It is testing and will be some bug.
Yes, it's a old build and in the next days I'll build with new sources
Click to expand...
Click to collapse
Does installing secondary and swapping primary-secondary works?

A video demo would be great...

Did anyone actually test this yet?

taaeem said:
Did anyone actually test this yet?
Click to expand...
Click to collapse
Just tried it. When adding a ROM it fails as it requires a MULTIROM binary but besides that it's great.

any news for the Kernel?

I try it. Look cool. For uninstall it I use the Moto G Multirom uninstaller zip. Works pretty good!

[MOD]MultiROM for Galaxy A5 (SM-A500)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
MultiROM is one-of-a-kind multi-boot mod for Galaxy A5. It can boot any Android ROM as well as other systems like Ubuntu Touch, Plasma Active, Bohdi Linux or WebOS port, once they are ported to our device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs, daily prebuilt image files to install Ubuntu Touch and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Use for example Ubuntu Touch or Desktop alongside with Android, without the need of device formatting, once they are ported to Galaxy A5
* Boot from USB drive attached via OTG cable
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is messing with boot sector and data partition. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
1) Flash Modified TWRP with odin or extract the tar file and install the img file with flashify or another recovery that has img install feature
2) Flash MultiROM zip in TWRP
3) enjoy
MultiROM has 3 parts you need to install:
Modified recovery Download the Modified TWRP for MultiROM
Patched kernel *OPTIONAL* : Not Needed
MultiROM download the ZIP file from second post and flash it in recovery.
Downloads:
Modified TWRP for MultiROM: https://www.androidfilehost.com/?w=files&flid=110082 Since the recovery image was too big for recovery partition, I used LZMA compression instead of LZO for the kernel, which saved about 3 MB
MultiROM: https://www.androidfilehost.com/?w=files&flid=110089
MultiROM Uninstaller: https://www.androidfilehost.com/?w=files&flid=110117
If you get force closes on secondary nougat ROMs:
Flash the rom, open /sdcard/multirom/roms/rom_name/system/build.prop on primary, or on TWRP with "vi" editor
and change:
Code:
ro.sys.sdcardfs=true
to
Code:
#ro.sys.sdcardfs=true
Then reboot.
DO NOT reboot the rom before changing build.prop line otherwise you will still get force closes!
You current rom will not be erased by the installation.
Important: Since the Kernel hasn't Kexec Hardboot patch, you have to check "use no kexec workaround" box in multirom settings
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Using USB drive (not tested yet)
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Explanation of recovery menus
Main menu
- Add ROM - add ROM to boot
- List ROMs - list installed ROMs and manage them
- Inject boot.img file - When you download for example kernel, which is distrubuted as whole boot.img (eg. franco kernel), you have to use this option on it, otherwise you would lose MultiROM.
- Inject boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
- Settings - well, settings.
Manage ROM
- Rename, delete - I believe these are obvious
- Flash ZIP (only Android ROMs) - flash ZIP to the ROM, for example gapps
- Add/replace boot.img - replaces boot.img used by this ROM, this is more like developer option.
- Re-patch init - this is available only for ubuntu. Use it when ubuntu cannot find root partition, ie. after apt-get upgrade which changed the init script.
How does Kexec workaround works
You need to a kexec-hardboot supporting kernel or the non-kexec workaround as described perfectly by @nkk71 here: http://forum.xda-developers.com/show...26&postcount=4 (Be sure to leave him a thanks!)
Source code
MultiROM - https://github.com/nkk71/multirom
Modified TWRP - https://github.com/nkk71/android_bootable_recovery
Device Tree: https://github.com/DeadSquirrel01/android_device_samsung_a5ultexx branch cm-13.0-mrom
Kernel w/ kexec-hardboot patch: NOT NEEDED
Credits
A big thanks for:
@nkk71 For kexec workaround and for helped me in IRC
@Tasssadar For MultiRom Source Code
That made this possible
Donations (Please donate to the Creator @Tasssadar )
I'd be glad if you could spare a few bucks. You can use either paypal or Bitcoins, my address is 172RccLB2ffSnJyYwjYbUD3Nx4QX3R8Ris
Click to expand...
Click to collapse

XDA:DevDB Information
MultiROM for Galaxy A5 (SM-A500), Tool/Utility for the Samsung Galaxy A Series
Contributors
DeadSquirrel01
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2016-09-10
Created 2016-09-10
Last Updated 2016-09-10

Reserved

AWESOME!!!!!!!!!!!!!!!FINALY!!!!!!!!!!!:good::good::good:

-CALIBAN666- said:
AWESOME!!!!!!!!!!!!!!!FINALY!!!!!!!!!!!:good::good::good:
Click to expand...
Click to collapse
He he thanks

one lil question from me.my current rom be untouched when i flash it,right?Because my current rom is working perfect and i dont need fail,thanx.

-CALIBAN666- said:
one lil question from me.my current rom be untouched when i flash it,right?Because my current rom is working perfect and i dont need fail,thanx.
Click to expand...
Click to collapse
No, it will br untouched, but a backup waste only 5 times, at massimum, so, if you have some free space make a backup, but as I said, it will be untouched

;DD will it work like this?
primary - stock touchwiz
secondary - cm 13
?
Thanks

supertiger1234 said:
;DD will it work like this?
primary - stock touchwiz
secondary - cm 13
?
Thanks
Click to expand...
Click to collapse
Sure

It's working perfectly! Thanks! hmm is cm 13 the best or rr? or anything else? xD
Edit: I'll choose your PacRom ;D

supertiger1234 said:
It's working perfectly! Thanks! hmm is cm 13 the best or rr? or anything else? xD
Click to expand...
Click to collapse
CM is pure android, rr has lots of feature regarding the personalization, so, if you want a rom wich is pure android, get the cyanogenmod, otherwise, if you like to personalize your android get the resurrection remix. Oh you installed multirom, so you can install both of them (you can install more than 2 roms) and decide which one is better for you
EDIT: if you use pac-rom you have to move this as primary, because it has a bug that won't boot if you set it as secondary

hmm is it normal to have "failed to mount /preload (invalid argument)"? happens when i flash rr
Edit: when i choose rr from the list, the device just reboots to multirom menu. hmm

supertiger1234 said:
hmm is it normal to have "failed to mount /preload (invalid argument)"? happens when i flash rr
Click to expand...
Click to collapse
Not, try to reboot to recovery and then reflash

DeadSquirrel01 said:
Not, try to reboot to recovery and then reflash
Click to expand...
Click to collapse
Okay I deleted and reflashed the rom, still the same error, hmm
Edit: when i go to mount and try to tick preload, it doesnt tick

Mmm, maybe i have to remove preload from the fstab. Now i'll do and notify once it's done

Works on my A500M with Stock 6.0.1 and CyanogenMod 13, thank you very much for port this mod to Galaxy A5

supertiger1234 said:
Okay I deleted and reflashed the rom, still the same error, hmm
Edit: when i go to mount and try to tick preload, it doesnt tick
Click to expand...
Click to collapse
Fixed, now download new twrp version (link in main post) and it should work
@codebseraph thanks for the support

DeadSquirrel01 said:
Fixed, now download new twrp version (link in main post) and it should work
@codebseraph thanks for the support
Click to expand...
Click to collapse
Hmm, The errors fixed buut now when I choose my second rom, it reboots to multirom menu xD
The non-kecex link doesn't work. Is there something important there?

Is the secondary rom pac-rom?
If yes, u have to move it as primary because it has a bug

DeadSquirrel01 said:
Is the secondary rom pac-rom?
If yes, u have to move it as primary because it has a bug
Click to expand...
Click to collapse
I'm trying rr and it's not working xD it's scary swapping
ResurrectionRemix-M-5.7.3-20160830-a5ultexx

supertiger1234 said:
I'm trying rr and it's not working xD it's scary swapping
ResurrectionRemix-M-5.7.3-20160830-a5ultexx
Click to expand...
Click to collapse
Well, it's a problem of the zip of the ROM. move it as primary or wait until I create a working installer
EDIT: maybe try with this installer https://www.androidfilehost.com/?w=file-thanks&fid=24591020540824243&mid=71&download_id=vlofv1jeu8k8ubpcpd375ql164&tid=1473585621&hc=c6de356c2e1c646fcb44f52216b36595df13152b92265bbb693814053fe5ca85

Database Develop

welcome