Related
[INTRODUCTION]
This ROM is based of the joined effort of a couple of devs (Ejtable, Scanno and Brucelee666) who are working on getting JellyBean working for our device. As soon as JellyBean is getting stable, my goal is also to put everything on github, just like i did with VegaCream. This way other devs can also work on this.
Please remember that I, ejtagle and brucelee666 are *NOT* professionals and do this in our spare time. We all have full time jobs and a family. So be happy that there is an Android ROM based on Android 4.1.1 / JellyBean for a device that was sold with Android 2.2 and never had an update.
We do our best to make this ROM as good as possible. With VegaCream we gave you a ROM that gave a new life to your tablet and unleashed its full potential. But we are not wizzards and there might be problems that we cannot solve or do not have time for.
[SPECIFICATIONS]
This ROM is based on AOSP 4.1.1 and the device config made by Ejtagle, brucelee666 and myself.
- INT2EXT+ (Needs a correctly partitioned SDCard)
- zRAM
- DPI is set at 120dpi
- Default JellyBean Launcher installed
- Apex Launcher installed
- Filemanager installed
- Terminal installed
- Google Apps is installed. This means that the Google base is installed and all the apps that are available in the Play Store are not installed (i.e. GMail, Maps)
- All languages that are available in AOSP are included
- Partition layout is the same as VegaCream / VegaICS beta1 / Modded stock
- /system/app, /system/lib, /system/fonts, /system/framework and /system/usr are Squashfs filesystems.
[INSTALLATION]
There are 2 methods of installation. There is a CWM recovery flashable ZIP and a NVFlash file.
I realy recommend flashing VegaBean the first time with the NVFlash version.
Before installing any version, you have to make sure that you have a SDCard that has the correct partition layout:
- First partition is a primary partition formatted as FAT32
- Second partition is a primary partition formatted as EXT4
EXT4 is a linux filesystem so you will need a program that can handle Linux filesystems when you are using Windows.
Before installing the ZIP file make sure that:
- You have the correct partition layout (if you have VegaCream installed, you have the correct layout, if not then use the NVFlash installer. This will repartition your internal memory))
- Copy the ZIP file to your SD-Card
- Boot into Recovery
- Do a FULL WIPE / FACTORY RESET
- Install the ZIP file from your SDCard
- After installing reboot the tablet.
[WORKING]
- WiFi
- Bluetooth (Tested with a A2DP headset)
- Camera
- HDMI including audio
- 3G (only fro the Huawei internal modem, usb modems may work)
- GPS not tested by me, but some say it kind of works.
[CREDITS]
- Ejtagle
- Brucelee666
- Scanno
- LeoP for his zRAM implementation
- Legionaire (for the VegaBean bootanimation)
[DOWNLOADS]
Please do *NOT* use Link2SD anymore. You do not need it. With the INT2EXT script, your apps will install on SDCard by default. Just make sure you have 2 primary partition. First partition *MUST* be a FAT32 partition. The second partition *SHOULD* be EXT4. When upgrading from a previous version, make sure your EXT partition is empty / reformatted. Also when using the NVflash version !!!
Downloads:
https://www.androidfilehost.com/?w=files&flid=118264
[Changelist]
[Beta 6]
- RIL updated to the latest version (3 october i think)
- updated to AOSP 4.1.2
- Added check to see if there is a second partition on the SDCard. If not INT2EXT is not excecuted (PLEASE TEST !!!)
- Updated GApps
[Beta 5]
Changes compared to Beta 3-1:
- New kernel with the following changes:
- Suspend problem solved. Tablet does not enter LP0 anymore
- Compiled with zRAM support
- zRAM modules added
- zRAM implementation from LeoP included
- RIL from ejtagle updated
[Beta 3-1]
- Included int2ext+
- Included bootanimation for legionnaire
[Beta 3]
- Latest RIL from EJTagle
- CM10 keyboard
- Stock browser with the option to set User Agent
- You can now just wipe cache and dalvik-cache when updating from a previous VegaBean version. Please remember that from other version you will have to do a full wipe / factory reset !!!
[Beta 2.2]
What has changed compared to Beta 2
- AOSP updated to JRO03L
- Latest update to the huaweigeneric RIL (from aug 27) by EJTagle
The stripped version has the following apps removed from /system/app compared to the original version:
- ApexLauncher.apk
- PlayMusic.apk
- Talk.apk
- YouTube.apk
The stripped version should give you around 10 MiB extra on /system. So if you have bad NAND problems and have problems booting (not able to) you can try this.
[Beta 2]
- HDMI audio working
- VegaBean bootanimation added by indigolemon
[Beta 1]
- Rotation really fixed and HW acceleration working
- Disable / Enable GPS would crash, fixed (thanks Eduardo)
Alpha 3:
- Rotation Fixed. Portrait mode is working correctly
- 3G files included... Sadly no 3G because of too old version of Huawei RIL. Need at least version 6 and we have version 4. So if anybody can get his / her hands on a newer version, please let us know.
Hey , very nice to see JellyBean here
I have ViewSonic 10s
I am using at this moment VegaICS , so i am thinking to upgrate it to JB. So my questions :
- kernel with hostdriver ?
- is system rewritable?? its Squashfs so i think its not (like VegaICS, no deletable apps...)
- can I update BusyBOX and Superuser ??? (always after i did it , WIFI was brocken and I lost root (VegaICS))
- is it possible to change DPI to normal 160 ??
............................
One more question about CWM
always after installing any Roms via CWM , it booted , but after first reboot/turnoff my device died... only what help is reflashing via NVflash....
So what should i flash first to use a stable-CWM (without killing device)
any suggestions
If you are still using VegaICS, I suggest you switch to VegaCream RC2. It has an NVFlash installer, so you don't have to use CWM at all. It is by far the most stable and fast ROM ever built for our devices, and is 100% feature complete.
This ROM is a beta, and if you have not experienced VegaCream RC2 yet, you should try that first and wait on this for a later release.
rpmccormick said:
If you are still using VegaICS, I suggest you switch to VegaCream RC2. It has an NVFlash installer, so you don't have to use CWM at all. It is by far the most stable and fast ROM ever built for our devices, and is 100% feature complete.
This ROM is a beta, and if you have not experienced VegaCream RC2 yet, you should try that first and wait on this for a later release.
Click to expand...
Click to collapse
ye but its 120 dpi... its horrible and all is toooo small .. can see pixels
What a great ROM, but I've got a problem where my Viewpad don't boot. Ok, it boots the first time after installing it, but not on 2nd boot. I've tried to install it over both VegaICS and VegaCream RC2. Does anybody have a solution? I really want this ROM. I had the same problem on VegaCream in the past, but it I think it works now, but not in VegaBean. I hope I get any help...
Sent from my HTC Sensation, Venom-infected with the ViperS ROM!
2minuutes said:
What a great ROM, but I've got a problem where my Viewpad don't boot. Ok, it boots the first time after installing it, but not on 2nd boot. I've tried to install it over both VegaICS and VegaCream RC2. Does anybody have a solution? I really want this ROM. I had the same problem on VegaCream in the past, but it I think it works now, but not in VegaBean. I hope I get any help...
Sent from my HTC Sensation, Venom-infected with the ViperS ROM!
Click to expand...
Click to collapse
ye its the same problem , flashing with CWM kill your Pad at second boot
thats why i am flashing only via NVflash
Vlad87do said:
ye its the same problem , flashing with CWM kill your Pad at second boot
thats why i am flashing only via NVflash
Click to expand...
Click to collapse
VegaCream works now after flashing it through NVFlash. Could the boot problem have something with an uncomplete CWM or something? Like it "destroys" the important partitions?Since both VegaCream and VegaICS use an unofficial build of CWM with Touch-interface? Mabye I'll try to flash an official version and install VegaBean through there! Will report back if it works!
Nice, will test this out!
2minuutes said:
VegaCream works now after flashing it through NVFlash. Could the boot problem have something with an uncomplete CWM or something? Like it "destroys" the important partitions?Since both VegaCream and VegaICS use an unofficial build of CWM with Touch-interface? Mabye I'll try to flash an official version and install VegaBean through there! Will report back if it works!
Click to expand...
Click to collapse
I can now confirm that flashing VegaBean through official CWM works, and it boots and 2nd boot too... Just download the .zip file at the bottom and follow this guide by me: http://forum.xda-developers.com/showthread.php?t=1597556 or this guide by add.thebad: http://forum.xda-developers.com/showthread.php?t=1041036
Don't forget to hit the "Thanks" button if I helped you out
Link: https://dl.dropbox.com/u/85837377/recovery.zip
Thank you , i will do it then today !
Should i do it better via PC-adb and flash 3.0.2.8 with guide from add.thebad or better your method and recovery OR its just the same recovery 3.0.2.8 just deffirend flash method ???
...........................
Permission request to scanno: can I use his rom as base for Remics-Vega??
Vlad87do said:
Thank you , i will do it then today !
Should i do it better via PC-adb and flash 3.0.2.8 with guide from add.thebad or better your method and recovery OR its just the same recovery 3.0.2.8 just deffirend flash method ???
...........................
Permission request to scanno: can I use his rom as base for Remics-Vega??
Click to expand...
Click to collapse
If you want to use this for a new rom go ahead. Just give the credits for the work done (also ejtagle and brucelee666)
Modifications to the standard AOSP source code can be found on my github. Also the kernel sources are there too.
They are not up-to-date yet.
If you find solutions to problems in the ROM, give them back to the community so they can also be used in other ROMS.
scanno said:
If you want to use this for a new rom go ahead. Just give the credits for the work done (also ejtagle and brucelee666)
Modifications to the standard AOSP source code can be found on my github. Also the kernel sources are there too.
They are not up-to-date yet.
If you find solutions to problems in the ROM, give them back to the community so they can also be used in other ROMS.
Click to expand...
Click to collapse
yes ofc i will.
Is there Host-Driver in the kernel included ?
I am searching developers for Advent Vega device : http://remics.bennz.eu
If you have interests to join Remics-Team pm me!
Vlad87do said:
yes ofc i will.
Is there Host-Driver in the kernel included ?
I am searching developers for Advent Vega device : http://remics.bennz.eu
If you have interests to join Remics-Team pm me!
Click to expand...
Click to collapse
If you mean USB host... Yes it is... On my github there are the sources of the 3.1.10 kernel (based on the rel-15r7 version of nvidia) with the patches ejtagle made. But they are not up to date yet.
As soon as i have time i have to clean up the lunch target of beta1 and do a commit on github. Then you can fork from there and build a version for yourself. If you use the manifest file for vegabean you also get the modifications made to the framework, wpa_supplicant etc to make it all work.
See https://github.com/scanno
Again do not use it yet because they are not up to beta 1.
Thanks for the offer, but i do not have time to do a lot of work and join a development team. For the development of roms for the advent vega i would prefer and suggest that you and the Remics team go to the modaco forum and join the kernel development thread and join the efforts.
This way we have more changes of getting a very good base and from there make ROMS. The more roms to choose from, the better for the people using an advent vega.
Thx for answere, but i dont will compile it , i will use the ready zip file and edit it.
I am not a kernel-developer
thats why i asked you about team
Vlad87do said:
Thx for answere, but i dont will compile it , i will use the ready zip file and edit it.
I am not a kernel-developer
thats why i asked you about team
Click to expand...
Click to collapse
Ok... but again all help is welcome, but you know that. Besides kernel development is done by EJtagle and not by me. He reversed engineerd most of the device specific vega stuff.
Also... /system/lib, /system/framework, /system/usr, /system/app are squashfs filesystems. To access the files in there you have to unsquash them.
do you can tell me programm on windows how to unsquash and again to squash after editing ?
Vlad87do said:
do you can tell me programm on windows how to unsquash and again to squash after editing ?
Click to expand...
Click to collapse
Sorry... I am using Linux and it is available in the repository there. On windows I really do not know. You could Google to see if there are any hits on mksquashfs and unsquashfs. That are the tools used on Linux.
You will need to find a version that supports XZ ( LZMA2) compression. That is the compression algorithm used in vegabean.
This is needed because otherwise the ROM does not fit in the /system partition.
very nice!
7zip can do it under windows - unpack
This is my patch that replaces your current Adreno EGL Graphics libraries with the new ones.
It will boost your 3D performance remarkably.
It is based on original update that appeared on several sites dealing with android tuning but
the exact original source is still unknown to me. Anyway, libraries seem to work properly.
This patch will automatically append all the necessary settings into your existing /system/build.prop file
even if they are probably not necessary for libraries to work. But anyway, just to be sure.
It will not modify your existing settings in your build.prop in any way. It will just add a new section that can be easily
removed if desired.
THIS PATCH IS FOR GINGERBREAD ROMS ONLY THAT DON'T HAVE IT APPLIED YET (ASK YOUR ROM MAINTAINER TO FIND OUT). APPLYING THIS PATCH ON ANY OTHER ANDROID VERSION (ICS, JELLYBEAN) WILL PUT YOUR DEVICE IN A BOOTLOOP
I strongly encourage you to make a backup of your current ROM in recovery before aplying this patch!!!
It may happen that new libs will not work with your ROM at all (CM7 and CM9 are questionable) and you may
easily end up with your phone not booting after aplying this patch!!! I will not provide support to anyone ignoring the step
of making the backup! Backup is essential because in case of any problems you can easily revert back to your previous state.
Download: http://tinyw.in/IB0D ( MIRROR )
MD5 Checksum: 509402fb4bbbe0c2292abdca02f3846a
Screenshots: http://ceco.sk.eu.or...creenshots/gpu/
Installation instructions:
1) Download the ZIP file to your SD card
2) Reboot to recovery
3) Make a backup of your current ROM using menu Backup and Restore / Backup
4) Choose from menu: install zip from sd card / choose zip from sd card Find ZIP in filesystem structure
5) Confirm to flash
6) Reboot
{
"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
I was able to get multirom working on Motorola Moto G and would like to share with you guys. Moto G (falcon) is my first android phone (ya, you heard me correct. It took a longtime for me to switch to android ) and I am new to android development and XDA community.
I have converted my XT1033 to single sim variant after flashing XT1032_RETAIL-GB_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF.xml.zip firmware. I did this to install Parandroid (currently it only supports single sim). It might work on the default firmware.
MultiROM is one-of-a-kind multi-boot mod for Nexus 7. It can boot any Android ROM as well as other systems like Ubuntu Touch, Plasma Active, Bohdi Linux or WebOS port.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
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.
There are stil many issues, and I am still testing and learning :angel:.
- Only for falcon stock firmwares. Doesn't work on falcon GPE.
- Sometimes Wifi not able to get IP address (static config works) on secondary rom. (same issue is observed on primary rom - fixed after flashing latest kernel)
- Sometimes secondary rom boot failure. Need reboot.
- Touch doesn't seem to work on multirom, so need to use volume down key for navigation and power button got selection. (Fixed)
- On GPE sometimes when booting I see "exec '/system/bin/sh' failed: Permission denied" errors. reinstalling the rom in multirom fixes this issue. Need to check.
You can get the relavent files at following location
http://d-h.st/users/montamer
Multirom Files
TWRP with Mutirom changes
multirom-20140902-v28-UNOFFICIAL-falcon.zip
multirom_uninstaller.zip
Patched Kernels
Stock Kernel (only for Stock firmware not GPE)
Modiefied 3.4.103-XPerience-STK-14-gpemod for GPE stock firmware (original kernel from TeamMEX)
PA Kernel
I have tested booting following roms
- CynogenMod
- ParanoidAndroid
- Boot2Gecko
I will share any code modifications as soon as possible.
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. Via MultiROM Manager app
Not supported at the moment.
2. Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them.
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is not encrypted).
Note 2: There have been reports that (not only) MultiROM does not work properly with older bootloaders.
MultiROM has 3 parts you need to install:
Modified recovery (TWRP with Mutirom changes) - download the IMG file from Multirom Files section and use fastboot or Flashify app to flash it.
- Fastboot command "fastboot flash recovery recovery.img"
Patched kernel - You can use either one of the stock ones in Kernel section or third-party kernels which include the patch. Download the ZIP file and flash it in recovery. or flash the img from fastboot.
- Flash the "Stock Kernel (only for Stock firmware not GPE)" if your using STOCK 4.4.4 firmware images using below fastboot command
fastboot flash boot stock_boot_patched.img
- Flash the 3.4.103-XPerience-STK-14-gpemod from recovery if you are using GPE 4.4.4 firmware.
MultiROM (multirom-XXXXXXXX-v28-UNOFFICIAL-falcon.zip) - download the ZIP file from Multirom Files section and flash it in recovery.
Note: make sure to disable screen timeout in recovery (multirom_patched_recovery.img) (not required in latest recovery build)
You current rom will not be erased by the installation.
Download links are in the second post.
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 4.2 after first boot (with dalvik cache generated and connected to google account) takes 676mb of space.
2. Ubuntu Touch
Use the MultiROM Manager app to install Ubuntu Touch.
Ubuntu Touch is in development - MultiROM will have to be updated to keep up with future changes in Ubuntu, so there's a good chance this method stops working after a while and I'll have to fix it.
Using USB drive
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 curr. 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.
In some cases, you might need to flash patched kernel - get coresponding patched kernel version from second post and flash it to the secondary ROM sama way you flashed 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 curr. 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.
Source code
Original MultiROM - https://github.com/Tasssadar/multirom (branch master)
Falcon modified MultiROM - https://github.com/montamer/multirom
Falcon modified kexec-tools - https://github.com/montamer/kexec-tools.git
Falcon CM kernel with kexec-hardboot-patch - https://github.com/montamer/android_kernel_motorola_msm8226.git
kexec-hardboot-falcon.patch
Modified TWRP - https://github.com/montamer/Team-Win-Recovery-Project
XDA:DevDB Information
MultiROM, a Tool/Utility for the Moto G
Contributors
Tasssadar
Montamer
Thanks
h2o64 for the post template
willing to test I've got an xt1034. all I need is a link.
montamer said:
I was able to get multirom working on Moto-G and would like to share with you guys :highfive:. Moto-G is my first android phone (ya, you heard me correct. It took a longtime for me to switch to android ) and I am new to android development and XDA community.
I have converted my XT1033 to single sim variant after flashing XT1032_RETAIL-GB_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF.xml.zip firmware. I did this to install paranoidandroid (currently it only supports single sim). It might work on the default firmware.
There are stil many issues, and I am still testing and learning :angel:.
- Only for falcon stock firmwares. Doesn't work on falcon GPE.
- sometimes Wifi not able to get IP address (static config works) on secondary rom.
- sometimes secondary rom boot failure. Need reboot
- touch doesn't seem to work on multirom, so need to use volume down key for navigation and power button got selection
You can get the relavent files at following location
http : // d-h.st / users / montamer
mutirom files - falcon/multirom
patched kernels - falcon/hardboot_patched_kernel
I have tested booting following roms
- CynogenMod
- ParanoidAndroid
- Boot2Gecko
I will share any code modifications as soon as possible.
INSTALLATION:
- Flash multirom_patched_recovery.img from fastboot.
- Flash stock_boot_patched.img from fastboot if you are on stock rom
or flash PA-falcon-kernel-signed.zip (build kernel from aospal, should work on other roms????) from recovery.
- reboot to recovery
- Flash multirom-20140819-v27-UNOFFICIAL-falcon.zip from recovery
WARNING
Port is not tested completely and might damage your device. Not for the faint hearted
I will not be responsible for any damage. Try at your own risk and make sure to backup
Credits:
Tasssadar (multirom aurthor).
paranoid android team.
Click to expand...
Click to collapse
I'll try it out.
Does this replace the kernel on stock ROMs?
Also, does this modify the eMMC partitioning to store the second ROM system files or can you use external storage such as a USB stick via USB OTG
DustArma said:
Does this replace the kernel on stock ROMs?
Also, does this modify the eMMC partitioning to store the second ROM system files or can you use external storage such as a USB stick via USB OTG
Click to expand...
Click to collapse
same question... multirom needs kexec support in the base rom. so this is just mutirom system or does it flashes a kernel with kexec support?
Amazing! I'll try as soon as possible. Could you share with us your device tree and your kernel sources? [emoji4]
@TeamMex perhaps something interesting for u man!
OP any instructions on how to use it?
Has you patched memory allocator's and kexec the kernel? Port Multirom is easy xD I have the sourse moded on my github but kexec isn't easy so tell me about your kernel patch
Sent from my XT1032 using XDA Premium 4 mobile app
abhifx said:
same question... multirom needs kexec support in the base rom. so this is just mutirom system or does it flashes a kernel with kexec support?
Click to expand...
Click to collapse
DustArma said:
Does this replace the kernel on stock ROMs?
Also, does this modify the eMMC partitioning to store the second ROM system files or can you use external storage such as a USB stick via USB OTG
Click to expand...
Click to collapse
The stock_boot_patched.img and PA-falcon-kernel-signed.zip are patched to support kexec. You need to flash one of the kernels based on your primary rom, before flashing multirom.zip.
I think new version of multirom doesn't mess with the eMMC partitioning and I have not tried flashing secondary rom on USB OTG.
TeamMex said:
Has you patched memory allocator's and kexec the kernel? Port Multirom is easy xD I have the sourse moded on my github but kexec isn't easy so tell me about your kernel patch
Sent from my XT1032 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes the kernels shared are patched with modified kexec_hardboot.patch from Tasssadar . I will share the changes soon.
yeshwanthvshenoy said:
@TeamMex perhaps something interesting for u man!
OP any instructions on how to use it?
Click to expand...
Click to collapse
Instruction should be similar to any other multirom flashing. check the original post from Tasssadar for more clear instructions.
http://forum.xda-developers.com/showthread.php?t=2011403
montamer said:
Yes the kernels shared are patched with modified kexec_hardboot.patch from Tasssadar . I will share the changes soon.
Click to expand...
Click to collapse
Interesting, I will be tuned to implement patch in my kernel.
cheers.
TeamMex said:
Interesting, I will be tuned to implement patch in my kernel.
cheers.
Click to expand...
Click to collapse
Awesome.
I'm just curious : how many time do you take to do this @montamer ?
That incredible
Are you a C // C++ developper ?
PS : Please make a clear and readable topic If you don't want I can propose you a design x')
?
Bugs? Dual sim XT1033?
montamer said:
The stock_boot_patched.img and PA-falcon-kernel-signed.zip are patched to support kexec. You need to flash one of the kernels based on your primary rom, before flashing multirom.zip.
I think new version of multirom doesn't mess with the eMMC partitioning and I have not tried flashing secondary rom on USB OTG.
Click to expand...
Click to collapse
fantastic... need to try this. after glorious mutiboot on nexus 4, i now have mutiboot on moto.
now where is the ubuntu build i want to test
montamer said:
Instruction should be similar to any other multirom flashing. check the original post from Tasssadar for more clear instructions.
http://forum.xda-developers.com/showthread.php?t=2011403
Click to expand...
Click to collapse
i do understand the instructions but adding them to ur OP would help first timers. we got people who dont have much experience with advanced stuffs like this man so was just suggesting!
Thank you very much! I'll wait for you to release the changes before implementing it on other kernels.
BTW the PA kernel does not work on LiquidSmooth - it boots but have no wifi/networking, just to say
It made you a little prettier topic :
Code:
[CENTER][IMG]http://i.imgur.com/vh3puLb.png[/IMG][/CENTER]
[b][U][size=5]Introduction[/size][/U][/b]
I was able to get multirom working on [B]Motorola Moto G[/B] and would like to share with you guys. Moto G (falcon) is my first android phone (ya, you heard me correct. It took a longtime for me to switch to android :p) and I am new to android development and XDA community.
I have converted my XT1033 to single sim variant after flashing XT1032_RETAIL-GB_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF.xml.zip firmware. I did this to install Parandroid (currently it only supports single sim). It might work on the default firmware.
[INDENT]MultiROM is one-of-a-kind multi-boot mod for Nexus 7. It can boot any Android ROM as well as other systems like Ubuntu Touch, Plasma Active, Bohdi Linux or WebOS port.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
* Boot from USB drive attached via OTG cable
[url=https://www.youtube.com/watch?v=JDnDNxqfSaw]You can also watch a video which shows it in action.[/url][/INDENT]
[INDENT] There are stil many issues, and I am still testing and learning :angel:.
- Only for falcon stock firmwares. Doesn't work on falcon GPE.
- Sometimes Wifi not able to get IP address (static config works) on secondary rom.
- Sometimes secondary rom boot failure. Need reboot.
- Touch doesn't seem to work on multirom, so need to use volume down key for navigation and power button got selection.
You can get the relavent files at following location
[URL="http://d-h.st/users/montamer"]http://d-h.st/users/montamer[/URL]
mutirom files - [B]falcon/multirom[/B]
patched kernels - [B]falcon/hardboot_patched_kernel[/B]
I have tested booting following roms
- CynogenMod
- ParanoidAndroid
- Boot2Gecko
I will share any code modifications as soon as possible. [/INDENT]
[b][U][size=5][color=Red]Warning![/color][/size][/U][/b]
[INDENT]It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. [strike]It is messing with boot sector and data partition.[/strike] 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.[/INDENT]
[b][U][size=5]Installation[/size][/U][/b]
[INDENT][B]1. Via MultiROM Manager app[/b]
This is the easiest way to install everything MultiROM needs. [url=https://play.google.com/store/apps/details?id=com.tassadar.multirommgr]Install the app[/url] and select MultiROM and recovery on the [i]Install/Update[/i] card. If the [i]Status[/i] card says [i][b]Kernel:[/b] [color=red]doesn't have kexec-hardboot patch![/color][/i] in red letters, you have to install also patched kernel - either select one on the [i]Install/Update[/i] card or get some 3rd-party kernel here on XDA. You are chosing kernel for your primary ROM, [b]not[/b] any of your (future) secondary ROMs, so select the version accordingly.
Press "Install" on the [i]Install/Update[/i] card to start the installation.
[/INDENT]
[INDENT][b]2. Manual installation[/b]
Note: [COLOR="Red"]make sure to disable screen timeout in recovery[/COLOR]
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them.
[b]Note 1:[/b] Your device must [b]not[/b] be encrypted (hint: if you don't know what it is, then it is not encrypted).
[b]Note 2:[/b] There have been reports that (not only) MultiROM does not work properly with older bootloaders.
MultiROM has 3 parts you need to install:
[LIST]
[*][b]MultiROM[/b] (multirom-XXXXXXXX-v27-UNOFFICIAL-falcon.zip) - download the ZIP file from second post and flash it in recovery.
[*][b]Modified recovery[/b] (multirom_patched_recovery.img) - download the IMG file from second post and use fastboot or [url=https://play.google.com/store/apps/details?id=com.cgollner.flashify]Flashify app[/url] to flash it.
[*][b]Patched kernel[/b] - You can use either one of the stock ones in second post or third-party kernels which include the patch, you can see list in the second post. Download the ZIP file and flash it in recovery.
[/LIST]
[b]You current rom will not be erased by the installation.
Download links are in the second post.[/b][/INDENT]
[b][u][size=5]Adding ROMs[/size][/u][/b]
[INDENT][b]1. Android[/b]
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 4.2 after first boot (with dalvik cache generated and connected to google account) takes 676mb of space.[/INDENT]
[INDENT][b]2. Ubuntu Touch[/b]
Use the [url=https://play.google.com/store/apps/details?id=com.tassadar.multirommgr]MultiROM Manager app[/url] to install Ubuntu Touch.
[b]Ubuntu Touch is in development - MultiROM will have to be updated to keep up with future changes in Ubuntu, so there's a good chance this method stops working after a while and I'll have to fix it.[/b][/INDENT]
[U][size=5][b]Using USB drive[/b][/size][/U]
[INDENT]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.[/INDENT]
[U][size=5][b]Updating/changing ROMs[/b][/size][/U]
[INDENT][B]1. Primary ROM (Internal)[/B]
[LIST]
[*] 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 [I]Inject curr. boot sector.[/I]
[/LIST][/INDENT]
[INDENT][B]2. Secondary Android ROMs[/B]
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
[LIST]
[*] Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
[*] Select "Flash ZIP" and flash ROM's ZIP file.
[*] In some cases, you might need to flash patched kernel - get coresponding patched kernel version from second post and flash it to the secondary ROM sama way you flashed ROM's ZIP file.
[/LIST][/INDENT]
[u][size=5][b]Explanation of recovery menus[/b][/size][/u]
[INDENT][b][color=Blue]Main menu[/color][/b]
[b]- Add ROM[/b] - add ROM to boot
[b]- List ROMs[/b] - list installed ROMs and manage them
[b]- Inject boot.img file[/b] - 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.
[b]- Inject curr. boot sector[/b] - Use this option if MultiROM does not show up on boot, for example after kernel installation.
[b]- Settings[/b] - well, settings.
[b][color=Blue]Manage ROM[/color][/b]
[b]- Rename, delete[/b] - I believe these are obvious
[b]- Flash ZIP[/b] (only Android ROMs) - flash ZIP to the ROM, for example gapps
[b]- Add/replace boot.img[/b] - replaces boot.img used by this ROM, this is more like developer option.
[b]- Re-patch init[/b] - this is available only for ubuntu. Use it when ubuntu cannot find root partition, ie. after apt-get upgrade which changed the init script.[/INDENT]
[u][size=5][b]Source code[/b][/size][/u]
[INDENT]MultiROM - [URL]https://github.com/Tasssadar/multirom[/URL] [b](branch master)[/b]
Modified TWRP - not available yet[/b]
Stock kernel w/ kexec-hardboot patch - not available yet
CM kernel w/ kexec-hardboot patch - not available yet
[B][U][SIZE="4"][PLAIN]XDA:DevDB Information[/PLAIN][/SIZE][/U][/B]
[SIZE=3][B]MultiROM, a Tool/Utility for the Moto G[/B][/SIZE]
[B][U]Contributors[/U][/B]
[URL="http://forum.xda-developers.com/member.php?u=1248420"]Montamer[/URL]
thanks man!
tried with GPE(partially) converted 1033XT
unable to install multirom-20140819-v27-unofficial-falcon.zip
base rom PA 4.5-Beta1
any one facing the same issue
Only for falcon stock firmwares. Doesn't work on falcon GPE.
Device - Micromax a62
Clones - Micromax a26, a34, Karbonn a1+
OS - Gingerbread 2.3 5 SDK -10
Kernel version - 2.6.x
Chipset - Spreadtrum SC6820
Processor - Armv7 single core
Ram - 204 mb
System rom - 200 mb odexed
Internal memory- 202 mb
known software versions - 1.1.2, 1.1.6, 1.1.7 ,1.2.2, 1.2.3
No fastbooot mod
Before we proceed check about deodex & odex roms
http://forum.xda-developers.com/showthread.php?t=1443957
This device don't have fastboot mod so I request users only try tested things & follow each step of guide or flashing method correctly
If you bricked your device I am not responsible for it
So guys i guess you have faced many issues in stock rom like low ram ugly UI etc
There is only one way to make it better is custom roms for it you need to root your device & flash custom cwm recovery
Rooting guide by my dear friend @anabhi
http://forum.xda-developers.com/showthread.php?t=2459020
And cwm as well
http://forum.xda-developers.com/showthread.php?t=2514759
Cudtom Roms List-
1.FusionBlastX (s/w version 1.1.x)by me- http://forum.xda-developers.com/showthread.php?t=2775427
2. Invincible S5 (s/w version 1.1.x) by me- http://forum.xda-developers.com/android/general/custom-rom-invincible-pure-s5-themed-t2840733
3.Cyanokat Inverse (for deodexed roms only) (s/w version 1.1.x) by me- http://forum.xda-developers.com/and...om-rom-cyanokat-inverse-t2861825/post55122846
4.Ginger cream rom (s/w version 1.2.x)by @vikrantgmail - http://forum.xda-developers.com/and...micromax-a62-karbonn-a1-t2863440/post55196030
5.L-Kat (s/w version 1.1.x) by me- http://forum.xda-developers.com/android/development/custom-rom-t2899079/post55900520#post55900520
Things to be noted -
1. Always make a clean flash that is
Wipe data factory reset
Wipe cache
Wipe delvic cache (in advance menu)
Before flashing
Don't format system in cwm you will get no touch after flashing rom
2. First check your device software version & flash rom accordingly
3.-Software version 1.2.x has bug with restoring backup so please don't take a risk on it
4.if your device is bricked give full info what rom you flashed & s/w version
5. As its a bug of SC6820 no touch after formattimg system while flashing rom some roms are provided as cwm backup & some as Mods/ updates
Here we have one more problem in cwm backup you can face problem with ril( network) if you face please prefer flash mods
6.Flashing mod require System memory(not internal memory) free up to 40 mb
7.If you have any doubt post before flashing
8 if your device is bricked move to the last section
SystemUI mods
1.Kitkat Statusbar - http://forum.xda-developers.com/showthread.php?p=53392578
2.- S5 statusbar - http://forum.xda-developers.com/showthread.php?p=53516017#post53516017
3. Z2 Statusbar- http://forum.xda-developers.com/android/general/z2-statusbar-micromax-a62-a26-a34-t2879683
Want to recover to stock rom ?
Here is flashing guide by @navi_5886 - http://navi-singh.blogspot.com.es/2013/10/micromax-a62-flashing-process.html?m=1
Well there are tools like research download available to flash stock rom( .pac ) you can try by this guide
http://forum.xda-developers.com/showthread.php?t=2624918
I haven't tried flash tools so I can't guarantee it will work or not for this device
All system apps thanks to Vikrant Sharma for it
https://www.dropbox.com/s/02dblh23fyubpsg/All System Apps_MMX A62 Bolt_By Vikrant.rar
Awesome Works Bro
Really all Roms are awesome... I tried all roms in mobile. Thanks to Dayal Bro for making all roms & #VK also
dayal4742 said:
Device - Micromax a62
Clones - Micromax a26, a34, Karbonn a1+
OS - Gingerbread 2.3 5 SDK -10
Kernel version - 2.6.x
Chipset - Spreadtrum SC6820
Processor - Armv7 single core
Ram - 204 mb
System rom - 200 mb odexed
Internal memory- 202 mb
known software versions - 1.1.2, 1.1.6, 1.1.7 ,1.2.2, 1.2.3
No fastbooot mod
Before we proceed check about deodex & odex roms
http://forum.xda-developers.com/showthread.php?t=1443957
This device don't have fastboot mod so I request users only try tested things & follow each step of guide or flashing method correctly
If you bricked your device I am not responsible for it
So guys i guess you have faced many issues in stock rom like low ram ugly UI etc
There is only one way to make it better is custom roms for it you need to root your device & flash custom cwm recovery
Rooting guide by my dear friend @anabhi
http://forum.xda-developers.com/showthread.php?t=2459020
And cwm as well
http://forum.xda-developers.com/showthread.php?t=2514759
Cudtom Roms List-
1.FusionBlastX (s/w version 1.1.x)by me- http://forum.xda-developers.com/showthread.php?t=2775427
2. Invincible S5 (s/w version 1.1.x) by me- http://forum.xda-developers.com/android/general/custom-rom-invincible-pure-s5-themed-t2840733
3.Cyanokat Inverse (for deodexed roms only) (s/w version 1.1.x) by me- http://forum.xda-developers.com/and...om-rom-cyanokat-inverse-t2861825/post55122846
4.Ginger cream rom (s/w version 1.2.x)by @vikrantgmail - http://forum.xda-developers.com/and...micromax-a62-karbonn-a1-t2863440/post55196030
5.L-Kat (s/w version 1.1.x) by me- http://forum.xda-developers.com/android/development/custom-rom-t2899079/post55900520#post55900520
Things to be noted -
1. Always make a clean flash that is
Wipe data factory reset
Wipe cache
Wipe delvic cache (in advance menu)
Before flashing
Don't format system in cwm you will get no touch after flashing rom
2. First check your device software version & flash rom accordingly
3.-Software version 1.2.x has bug with restoring backup so please don't take a risk on it
4.if your device is bricked give full info what rom you flashed & s/w version
5. As its a bug of SC6820 no touch after formattimg system while flashing rom some roms are provided as cwm backup & some as Mods/ updates
Here we have one more problem in cwm backup you can face problem with ril( network) if you face please prefer flash mods
6.Flashing mod require System memory(not internal memory) free up to 40 mb
7.If you have any doubt post before flashing
8 if your device is bricked move to the last section
SystemUI mods
1.Kitkat Statusbar - http://forum.xda-developers.com/showthread.php?p=53392578
2.- S5 statusbar - http://forum.xda-developers.com/showthread.php?p=53516017#post53516017
3. Z2 Statusbar- http://forum.xda-developers.com/android/general/z2-statusbar-micromax-a62-a26-a34-t2879683
Want to recover to stock rom ?
Here is flashing guide by @navi_5886 - http://navi-singh.blogspot.com.es/2013/10/micromax-a62-flashing-process.html?m=1
Well there are tools like research download available to flash stock rom( .pac ) you can try by this guide
http://forum.xda-developers.com/showthread.php?t=2624918
I haven't tried flash tools so I can't guarantee it will work or not for this device
All system apps thanks to Vikrant Sharma for it
https://www.dropbox.com/s/02dblh23fyubpsg/All System Apps_MMX A62 Bolt_By Vikrant.rar
Click to expand...
Click to collapse
AWESOME !!
SOft Bricked up my a62
My rooted Micromax a62 was working properly. It was running on Stock ROM. But then I repartitioned my memory card. When I power up my phone, the bootloader comes up followed by a white screen and the phone shuts off. I've tried reset factory settings and formatting the system using CWM. It's not working. The problem still persists.Don't know what to do Please help me out... Any help'd be appreciated..
LG Stylo 2 Plus K550 Stock Rom Unrooted/Tweak-less
I AM NOT RESPONSIBLE FOR ANY BRICKED DEVICES, BOOTLOOPS, NUCLEAR ANNIHILATION, OR SPONTANEOUS
COMBUSTION! YOU ARE CHOOSING TO FLASH!!!
What you need -
1) TWRP
2)A brain
What is this ROM?
This is the Stock ROM for the K550 Variant of the Stylo 2 Plus. This ROM is completely Stock for the exception of having Adoptable Storage available Out of the box, and Kernel Fixes To be used on K550 ONLY (I mean, you can try on the MS550 but I'm not sure if It will SimLock to Tmobile
How is this different from [K55010r Stock Rooted Odex for T-Mobile LG Stylo 2 Plus by pvsgh]?
1) This is a purely stock ROM extracted directly from KDZ, no mods at all
2) Kernel and Security fixes that ROM by pvsgh doesnt have, fixing ADB (which doesn't work on his ROM, which was the main reason I had to make my own since ADB is crucially needed for speedy builds in my line of work)
Also, @pvsgh, DM me if you want the boot.img to use for your ROM so you can fix these issues
Will you make this for Andrioid N, when it comes out as well? Will there be a De-odexed version? What about for the MS550?
Yes, I am planning on also having a completely stock ROM built from KDZ as soon as Android N comes out. I will only make a De-odexed version if there is demand for one. In order to make one for the MS550, I need testers first as I only have K550.
Did you give up on LineageOS?
No, I'm just waiting for Android N
How Do I install this ROM?
First of All, Download the ROM and Place it in a Directory where you can find it. Then Boot into Recovery, and Go to Install, and select the Downloaded Zip File in your Selected Directory. When prompted to, Flash. IMPORTANT! - IT IS RECOMMENDED TO FORMAT DATA (USING THE BUTTON THAT LITERALLY SAYS "Format Data" IN TWRP) IF ATTEMPTING A COMPLETELY CLEAN BUILD OR YOU MAY BE LOCKED OUT OF YOUR DEVICE AND CONTENT LOCK WILL NOT WORK ANYMORE
FEATURES
- Literally Stock
- No Mods
- No Root, No Busybox, and No Xposed Out of the Box (User Install-able)
-Custom Stock Kernel with ADB and Security fixesTo be Included
-Nothing
DOWNLOADS
Download Here
Changelog
Version - 1
Code:
[LIST]
[*]Initial Release
[/LIST]
Known Bugs
None, all Stock
If you like you can Donate (On my Profile) or Hit that thanks Button!
didn't realize adb issue is still present in my rom's kernel, i might have forget to include the fixed boot.img. thanks for the headsup.
No problem. You can just extract the boot.img from this rom and put it into yours.
Link is dead