[ROM][Stock][ICS]LG P990 v28g Stock ICS flashable zip by harsh & tonyp [DISCONTINUED]
LG P990 Stock ICS flashable zip [DISCONTINUED]
This ROM is discontinued.
If you're looking for a stable ROM I recommend this ROM as an alternative: ParanoidAndroid CM10
It's more up-to-date and smoother than Stock ROMs - but at the same time still rock stable and qualifies as a daily driver.
If you want to continue using a Stock ROM on the GB bootloader I'd recommend to use the updated and actively maintained v30a/b Stock ROM by rugglez.
Some of the work of this ROM went into it - especially the heavily reworked ramdisk.
Using this ROM with the kowalski oldbl kernel does work as well (and fixes the callbug).
I've never intended to support a Stock ROM in the long term - I prefer CM based ROMs by far.
The initial intention of the first version of this ROM was to provide an easy way for people to test the SU660 leaks - back when we didn't even have P990 ICS leaks.
Nowadays that's easy, thanks to tools like the AIO toolbox by spyrosk, but back then it was more complicated for the users - especially with a SU660 ROM as base.
Then harsh & I decided to work on it together and update the initial SU660 base to a P990 v28 one.
A big thanks to harsh with whom I've been working closely together.
What is this?
This is a flashable zip version of the official LG v28g ROM by LG.
It's a Stock LG Android 4.0.4 ROM which uses the default ("old") bootloader and stock ("old") partition layout.
I prefer to stick with the GB layout and old bootloader as pretty much all ROMs, including CM10, are build for that.
If you have used the NVFlash ICS ROM you need to go back to the GB partition layout.
There are two versions. The standard version will fit into the stock GB partition layout.
To make it fit in there we had to remove some apps, including LGEmail, LG Calendar, LGMemo (QuickMemo is still there, don't worry) etc.
If you want to have the full ROM you can use the extended version, but need to increase the /system partition size to 512mb+ beforehand (see here for instructions).
Note that by only changing the partition size the partition layout won't change - so you still can flash other ROMs like CM10.
What's working?
This ROM is considered stable. harsh and I are using it as a daily driver currently!
Full hardware accelleration including:
Working Videocamera
Google Chrome
Videodecoding
etc.
In-call audio
Playstore
LG UI 3.0 & LG 4x lockscreen (THE MOST demanded feature in every dev thread )
Bluetooth
2G/3G
FM Radio
Everything else you can expect from a stable ROM (data, wifi, sms etc.)
What's not working?
slow charging on usb computer connection. Wall charger does work.
Workaround: Power off phone, attach usb cable, boot.
Screenshots (Power + Vol down) are empty. Just use Quickmemo (Vol up + down).
LG Application Manager not fully working and thus not included
The call issue of CM10 ROMs is present for some people.
If you reboot the phone once a day (e.g. at the morning) it usually won't occur during the whole day.
Credits:
Besides harsh thanks (especially for the old versions) to the following people:
(alphabetical order)
Someone missing? PM me asap!
aremcee
bihariel
ergoen
Kostja_V
wkpark
Due to the continuous misunderstanding: This ROM requires you to run the GB (aka the "old") bootloader and partition layout.
If you flashed a ICS ROM (kdz etc.) with NVFlash you need to go back to the old layout and bootloader, for example with this tool:
[TOOL] Full Brick Repair (Clean & Easy)http://forum.xda-developers.com/showthread.php?t=1975274
If you're coming from CM7, CM10, PA, GB (Android 2.3) Stock ROMs etc. this warning does not affect you.
Note:
I fixed the error which required you to use CWM 5.0.2.x for this ROM so you can now use any recovery you want now.
I'd recommend the official CWM 6.0.1.5 Touch or the newest TWRP.
How to install the new CWM:
You can use the ROM Manager to install CWM. But you need ROM Manager premium (or an in-app purchase for ~2$) to be able to flash CWM Touch with it.
You can use this flashable zip to install CWM 6.0.1.5 Touch easily: http://forum.xda-developers.com/showpost.php?p=34263577&postcount=1083
You can use my freshly zipped NVFlash CWM6 touch Recovery flasher (based on Rusty!'s method):
http://goo.im/devs/tonyp/P990-stuff/various/CWM6.0.1.5 touch NVFlash-tonyp.zip
Remove battery, hold both Vol - & Vol +, connect the phone to your notebook and use the "install_cwm6.bat" file (or the matching linux sh install script). APX driver is included.
This will flash CWM without touching any other partition.
Installation (follow carefully!):
Read post 1 and post 2 completely before you're doing anything with your phone!
If it doesn't exist, yet: Create the folder "external_sd" on your internal sdcard.
Reboot once.
Reboot into your recovery.
If you are coming from another ROM than my Stock ICS:
wipe data/factory reset(!)
Install zip from sdcard (flash the ROM)
Reboot (can take a couple minutes)
After fully booting up and going through the setup wizard: Restart your phone once again
Don't touch the RIL! And don't mind the "Unknown baseband" if everything works. This just means you got one of the older basebands which aren't displayed properly anymore. Nothing to worry about.
If automatic time if off you can either flash the v28g baseband (see my stickyied thread) or disable automatic time and use ClockSync.
Download:
standard version (fits into GB's /system partition):
http://goo.im/devs/tonyp/P990-stuff/ICS
extended version ("full" version requires /system of 512+ mb):
http://d-h.st/CVb
Changelog:
Code:
[u]version 3.01[/u]
[LIST]
[*]build.prop lines added to identify it as P990 device in the ROM Manager
[/LIST]
[u]version 3.0[/u]
[LIST]
[*]updated to v28g
[*]CWM Encryption error fixed (you can use any recovery now)
[*]kernel updated. fixes the bluescreen issue and some bugs & memory leaks
[/LIST]
[u]version 2.0[/u]
[LIST]
[*]complete new version based on the v28e leak
[*]no more korean SU660 files, pretty much all bugs are fixed
[*]thanks to harsh who build this version!
[/LIST]
[u]version 0.98[/u]
[LIST]
[*]bsod on screen off fixed (thx arcee!)
[*]huge update to the updater-script
[*]now pre-rooted
[*]Playstore updated
[*]Stock Messaging app replaces LG's one
[*]added Stock LG Browser
[*]added LGAlarm
[*]removed Google TTS
[/LIST]
[u]version 0.81[/u]
[LIST]
[*]typo fix in the updater-script
[/LIST]
[U]version 0.8[/U]
[LIST]
[*]initial release
[*]A mix between the final SU660 v30c ROM and the P990 ICS leak
[*]custom kernel to let it boot with the old bootloader
[/LIST]
Old installation instructions for versions prior to 3.0 (which was way more complex):
Installation (follow carefully!):
Read post 1 and post 2 completely before you're doing anything with your phone!
Create the folder "external_sd" on your internal sdcard.
You need to use ClockWorkMod 5.0.2.x
TWRP & CWM 6.x will result in encryption errors (something to investigate later)
use e.g. RomManager, scroll to the bottom, choose "older recoveries" and install 5.0.2.0
Backup your current ROM
wipe data/factory reset
mounts and storage - format /system
Install zip from sdcard (flash the ROM)
remove the usb cable from the mobile phone!
(if you boot with the phone connected to your PC the PC will either freeze or show you a bluescreen!)
Reboot (can take a couple minutes)
After the setup wizard go to Settings - Connectivity and change the USB connection type to MTP
(now you can attach the phone back to your PC).
Restart your phone
Don't touch the RIL! And don't mind the "Unknown baseband" if everything works. This just means you got an older baseband which aren't displayed properly.
If automatic time if off you can either flash the v28e baseband or disable automatic time and use ClockSync.
Thanks man.
i'll try this and feedback later
thx i'm test:good:
Thanks man. I'll try whether the USSD code is usable or not. This is important for a prepaid user like me.
Sent from my LG-P990 using xda app-developers app
yeah baby
tonyp said:
It's possible that in-call audio is not working! It's too late to call someone to test it.
Click to expand...
Click to collapse
downloading now, will flash and call myself (landline) and report back
I get almost 40kb/s so I think it's gonna be a while
Thank u. Will try
Sent from my LG-P990 using xda app-developers app
flashing...
Damnit, I had it at the USB cable the whole time. I just realized the ROM will bsod when going into deep sleep.
This is a kernel issue due to the GB bootloader.
So this is mainly a "let's check out how ICS works" ROM at the moment
Doesn't deserve an own thread. I can't yet close my own thread, will have to ask a mod about it.
no go then
will check tomorrow for any news
dont worry, you did a amazing job by make it flashable
go get some sleep you deserve it and thanks you again for your hard work :good: :fingers-crossed:
unkown function "uassert"
I wanted to try this anyways(despite the BSOD issue). Installation aborted with (Status 6). Logs show
Code:
line 1 col 89: unknown function "uassert"
1 parse errors
I wiped data and was on CM9 PA rom before. Tried toggling script asserts in recovery but same results.
Let me know if I am missing something? [busybox maybe?]
Edit: Maybe this is a recovery issue, I am on 5.0.2.7, but never had this issue before with any other roms.
Fix: Just use the 0.81 build or modify the update-script as described in the post below.
Aj264 said:
I wanted to try this anyways(despite the BSOD issue). Installation aborted with (Status 6). Logs show
Code:
line 1 col 89: unknown function "uassert"
1 parse errors
I wiped data and was on CM9 PA rom before. Tried toggling script asserts in recovery but same results.
Let me know if I am missing something? [busybox maybe?]
Click to expand...
Click to collapse
This is a simple mistake I made resulting of me being tired.
I did some last minute modifications of the update-script file (to ensure no P999 or SU660 users try and install it) and unfortunately wrote uassert instead of assert.
You can either fix it yourself: Goto META-INF/com/google/android/updater-script and remove the first character (the "u").
Or download v0.81.
goo.im is a great hosting service and offers me remote ssh access via a linux terminal - so I just unzipped the ROM, fixed the line and rezipped it as v0.81. No need to re-upload
Please reply if it works.
v0.81 of this rom is release i didn't even finish to download the first build and another build is uploaded thanks tonyp download speed is 40kbps so it take a while to test it
Tonyp is one of my favourite guy, there is a reason behind and thats he is simply amazing!
Thank u man. Now ppl can flash it w/o worries and fear
Sent from my LG-P990 using Tapatalk 2
grimmyrippy said:
v0.81 of this rom is release i didn't even finish to download the first build and another build is uploaded thanks tonyp download speed is 40kbps so it take a while to test it
Click to expand...
Click to collapse
Oh, goo.im slow again. A couple hours ago I had full speed.
If someone wants to provide a mirror feel free to do so, I'm out now really.
The v0.81 zip is untested, I hope it works the way I did the change remotely. If it doesn't use 0.80 and apply the manual fix I posted in my last post.
Open the updater-script with a texteditor like Notepad++.
Use build 0.81
tonyp said:
This is a simple mistake I made resulting of me being tired.
I did some last minute modifications of the update-script file (to ensure no P999 or SU660 users try and install it) and unfortunately wrote uassert instead of assert.
You can either fix it yourself: Goto META-INF/com/google/android/updater-script and remove the first character (the "u").
Or download v0.81.
goo.im is a great hosting service and offers me remote ssh access via a linux terminal - so I just unzipped the ROM, fixed the line and rezipped it as v0.81. No need to re-upload
Please reply if it works.
Click to expand...
Click to collapse
thanx, i'll modify the update script and try. I also thought it should be assert but refrained on commenting lest you had defined your own macro.
Thank you for your hard work. :good:
Edit: Can confirm that modifying updater-script manually works. Using stock ICS now. Cheers.
Somebody who has installed it, could try running playing song through music player before screen lock?
Does music/song keep playing continuesly after screen locks and after 2-3 mins does the phone wakeup by pressing unlock key or still BSOD?
Definately unplug usb cable before doing this
Sent from my LG-P990 using Tapatalk 2
Related
1st off I'm not a Dev, I'm using Ken's rom and added some mods and i thought i'd share it so some people can flash it and not have to apply patch/mods.
R-9 2.3.4 ROM
*NEW v5* This includes all the previous features of v4/v3
*V5 DOWNLOAD*
Code:
*v5*
- Base updated to πCRUST Official 91 build (thanks to navalynt)
- Droid 3 camera (stock camera restore zip below)
- 1080p video option
- AppWidgetPicker
- Skip blur setup option
- Updated SuperUser
- Updated Battery fix
*V4*includes
- Wifi Tethering
- APN menu opened
- Google Talk video
- AGPS option
- Dock Settings
- HDMI Settings
--------------------------
- Battery fix
- International APN (all network support incl ATT)
- 8 Point touch
- HDMI hack for webtop
- Battery percentage by Nottach
- GPS config set for international (backup included .bak file if you have issues)
- Stock boot animation minus ATT logo.
- Updated Google Maps
- Spare Parts (untick compatible mode for full screen apps)
- Stock blur messaging app removed and replaced with stock android (no conversaion limit)
- Different Font
πCRUST base features.
Code:
General Optimizations:
Fully deodexed
Fully zipaligned
Fully PNG optimized
build.prop optimizations
touchpad.cfg optimization
SU binary with latest SuperUser.apk
Busybox Installed
SQLite3 Installed
Select Network (menu option enabled, select manually 2G/3G, or auto)
Gootle Talk Video over 3G
FuguTweaks
Juwe11 optimizations
Einherjar Dev Team Permissions Script
DarkyROM Zipalign Script
SDcard Speed Fix (2048 by default)
Sqlite script to enable Gtalk Video
Defaults set to allow:
Unknown Sources (sideloading)
Data Roaming
All Animations
Tethering (no entitlement)
It has stock kernel. I recommend new GB radio Thanks to Samcripp for cwm zip
BACKUP NOW!
To install:
Download the rom
Put on SD card.
Boot into CWM
Wipe Data/reset factory
Install From SD
Click to expand...
Click to collapse
For international users (non ATT) , use the correct kernel from this thread
If you want working Webtop
then Flash Joe's webtop v1
New Market zip below
STOCK SMS APP Restore zip below
STABLE! V4 Base: V4a DOWNLOAD
v4a includes finger scanner fix
Base is Ken's 4.5 (BIG THANKS TO KENNETH!)
*v4a* Using Ken's Alien installer script so does not touch Webtop!
New features have been taken from Alien Rom (thank you Kenneth again)
original features
Code:
- Root
- Deodexed
- Compressed
- Zipaligned
- Memory hack
- SD card speed hack
- Rooted
- SQLite3 added
- Update script upgraded
DISCLAIMER|WARNING
USE AT YOUR OWN RISK!! I take no responsibility if you brick!
Click to expand...
Click to collapse
I TAKE NO CREDIT FOR THEIR WORK, I SIMPLY PUT STUFF TOGETHER FOR ME AND NOW SHARING IT.
Thanks to michael0619, kamma, Nottach, Kennethpenn, navalynt, Jug6, Unknown, Joe and who ever else, if i have used your work please tell me and i will credit or remove it.
For full screen apps, untick compatible mode in spare parts and the reboot.
V4 does not touch webtop..this means if you have a working webtop on 2.3.4 it will work after upgrade to v4.
V4 include Gtalk Video.
big thanks to you and kenneth
i screw up my atrix by pulling the battery when installing an app
i was stuck at gingerblur screen without further movement for good ten minutes. i think is time to move on to a new rom
liger-zero said:
big thanks to you and kenneth
i screw up my atrix by pulling the battery when installing an app
i was stuck at gingerblur screen without further movement for good ten minutes. i think is time to move on to a new rom
Click to expand...
Click to collapse
Try it and let me know
Back up 1st
well, my phone is unbootable(right?)
might as well wipe the database and install it fresh. does it compatible on ATT atrix?
I keep getting an error just says unable to open (bad) anyone have any idea?
it says cant open /sdcard/gingerbread.... .zip(bad) installation aborted
is it because i hasnt unlock the bootloader?
Yes u need unlocked bootloader.
Error on zip?
My bootloader is already unlocked and yes an error on the .zip file
Ok give me 10 mins to upload a new zip
EDIT: new zip uploaded
can you confirm if the messaging app works when you open the settings in the app. I tried to install it my self and it worked but every time I tried to access settings it would force close on me.
on21st said:
can you confirm if the messaging app works when you open the settings in the app. I tried to install it my self and it worked but every time I tried to access settings it would force close on me.
Click to expand...
Click to collapse
yes it works, because i have it. I installed it in /system/app and not data/app
Downloading now... is this a new zip upload?
I installed the new zip to my ext. SD Card and rebooted into CWM but get an error where the installation aborts.
crea78 said:
I installed the new zip to my ext. SD Card and rebooted into CWM but get an error where the installation aborts.
Click to expand...
Click to collapse
I have updated v3 and tested on my phone and it is working.
i really didnt want to flash over my nice setup but for the sake of testing my own i had to.
i'm uploading v3
Thanks.. just finish flashing
Ronaldo_9 said:
Yes u need unlocked bootloader.
Error on zip?
Click to expand...
Click to collapse
im not sure, i tried download the zip couple times. still gives me the same error
i probably try your new zip and work on the bootloader tomorrow.
thanks for your effort!
I thought I was in the development board... Oh wait, you just posted in the wrong section.
Thanks for the effort bud.
question, does it support japanese files?
i have a lot of mp3 files that is in japanese, it would have been sucks if the 2.3 doesnt support them
it supports japanese. no problem at all.
SAFESTRAP v3.73 (2nd-System Bootstrap / Recovery)
ATTENTION: I will be stopping official Safestrap support on 9/1/2014. For more information please see:
https://plus.google.com/111109372727398356624/posts/AtoJ3xLj35b
** INSERT STANDARD DISCLAIMER: I'm not responsible for any damage you do to your phone using my tools. Always have a fastboot available for disaster recovery. **
Download the APK Installer:
Mirror 1: Goo.im
Mirror 2: Crackflasher
FOLLOW THESE INSTRUCTIONS: How to Safestrap
[ DOUBLE-CHECK you have the "Maserati" version ]
NOTABLE TWRP-BASE CHANGES:
Key/button vibration in recovery and MANY more 2.7 updates
Screen saving in recovery. Can set the timeout under Advanced->Settings->Screen *Don't freak out of the screen is dark, try the power button.*
SElinux support in recovery
and much much more.. check the TWRP changelog here: http://www.teamw.in/project/twrp2
DEVICE SPECIFIC SAFESTRAP CHANGES:
[05/15] (3.73) Bugfix for dual SD card UMS mounting and pull in TWRP changes
[04/14] (3.72) Mostly other device updates
[01/15] (3.71) Code cleanup
[01/15] (3.71) Minor hijack updates
[12/18] (3.70) Mount cleanup during hijack / debugging output
[12/18] (3.70) Splashscreen: Instant stock boot key (needs to be set for Moto OMAP4's still)
[11/13] (3.65) recovery init.rc cleanup
[11/13] (3.65) fix updater build for cm 10.1 and 10.2
[09/20] (3.60) Better handling for virtual images > 2gb
[09/20] (3.60) Much improved block device handling
[09/20] (3.60) Bugfix in script translation
[09/20] (3.60) hijack / init.rc tweaks
[09/06] (3.53) Fixed mass_storage in recovery (via Mount menu)
[09/06] (3.53) Added Webtop to partition backup list (optional)
[09/06] (3.53) New virtual systems created will be 640mb (got reset 600mb)
[09/06] (3.53) Fixed file selector when changing from internal to external storage (previously location wouldn't update)
[09/05] (3.52) added "Reboot to Recovery" in APK
[09/04] (3.51) Disabled screen blank while creating a rom-slot
[09/04] (3.51) Fixed openrecovery script processing for stock slot to re-inject hijack after .zip install (cmupdater on stock now works)
[08/30] (3.50) If running a new CM10.1/CM10.2 ROM (08/30 or later) you *should* be able to install Safestrap and update the recovery w/o having to go back to stock. If Safestrap shows "recovery not installed" while you're on a ROM-slot, then that ROM hasn't been updated and it won't work. Swap back to stock ROM and update Safestrap from there.
[08/30] (3.50) Worked on stock ROM flashing and *should* work with CM10.1/CM10.2 builds on or after 08/30 *WILL NOT WORK WITH OLDER ROMs.*
[08/30] (3.50) Battery meter is back
[08/30] (3.50) Updated TWRP theme
[08/30] (3.50) Added partition sizes to ROM-slot screen when it's ACTIVE
[08/30] (3.50) Added "Check FS" function to ROM-slot screen when it's ACTIVE
[08/30] (3.50) Complete re-write against TWRP 2.6 base (up from version 2.2.2.1): TWRP changelog for reference
[12/29] (3.11) Allow use of custom updater-binary in .zip files for flashing on stock ROM (virtual slots still use prebuilt updater-binary in recovery).
[12/29] (3.11) BUGFIX: Fixed fake flash error at the end of a .zip install. (No real error, .zip installs fine)
[12/29] (3.10) Early support for booting custom ROMs on stock partitions.
[12/29] (3.10) Enable flashing to stock ROM *BE CAREFUL -- NEW FEATURE -- STILL TESTING*
After .zip installations, nandroid restore or system wipe on the stock ROM: the current Safestrap files are restored to the system partition (Doesn't include the APK in /data -- so if you're restoring an old backup, be sure to update the Safestrap APK)
During the Safestrap files restore a check is done to be sure there are minimal files on /system to re-enter Safestrap
[12/29] (3.10) New virtual system partitions will be 640mb (closer match to stock RAZR/D4)
[12/27] (3.07) Bugfix: missed some changes in Safestrap 3.06
[12/26] (3.06) Bugfix/Update for JB4.1 OTA for DroidRAZR (Non-JB devices can also use)
[10/17] (3.05) Fixed SD card / emmc sharing in recovery (UMS)
[10/17] (3.05) Fixed recovery installation/removal from ROM-slots
[10/14] Updated to v3.04 BETA.
[10/14] Recovery is now based off TWRP 2.2.2.1 (fully featured touch-based recovery)
[10/14] Can create up to 4 Virtual ROM-slots to flash ROMs to and when "Active" ALL TWRP functions affect that ROM-slot (For example: Flashing .zips, Backup and Restore)
[10/14] Nearly instant swapping from ROM to ROM
[10/14] User selectable data partition sizes during ROM slot creation: 1GB, 2GB or 3GB
[10/14] ROM slots are saved on the internal emmc space so that preinstall and webtop partitions are no longer used and shouldn't break OTAs.
[10/14] Charging in recovery
[10/14] Supports "Reboot Recovery" from Android OS
Entry to recovery via Splashscreen on boot-up. The screen stays up for around 8-10 seconds and if you hit the menu button, it takes you to Safestrap Recovery.
SPECIAL THANKS TO:
The entire TWRP team who has built an AMAZING recovery system.
The testers which have helped in past and present versions of Safestrap, knowing that it could mean they brick their devices.
As always, let me know what you think!
SCREENSHOTS (showing slightly older TWRP base)
do i need to be rooted?
Sweet. Let the ics based roms begin.
Sent from my DROID4 using Tapatalk
pimpsalot69 said:
do i need to be rooted?
Click to expand...
Click to collapse
Yes. There is no way to get Safestrap installed w/o being rooted.
Tol flash the leak or to not flash the leak
Hashcode,
There seem to be too differing opinions on whether or not it is safe to flash the ICS leak or not. Being the android guru that you are, would you mind weighing in or whether or not this is safe to do? It seems, based on the fact the people are able to go from .200 to .206 that, theoretically, you should be able to use the same method to flash the OTA when it comes out and get back on the upgrade path. What are your thoughts? Thanks!
Just used safestrap 2.0 to do a full system backup. I think the confusing thing about pressing the keys to enter or skip the safestrap menu is the lack of haptic feedback when pressing the menu or search softkeys.
Thanks for your work hashcode. Without you the D4 would be lost.
Sent from my DROID4 using Tapatalk
kwyrt said:
Hashcode,
There seem to be too differing opinions on whether or not it is safe to flash the ICS leak or not. Being the android guru that you are, would you mind weighing in or whether or not this is safe to do? It seems, based on the fact the people are able to go from .200 to .206 that, theoretically, you should be able to use the same method to flash the OTA when it comes out and get back on the upgrade path. What are your thoughts? Thanks!
Click to expand...
Click to collapse
I don't recommend people jump on the ICS leaks just yet. But, if you do and are looking to make backups etc, then Safestrap is probably what you need. Just make sure to do the initial backup of your non-safe system (don't need webtop) so that you can put everything back the way you found it.
bdsullivan said:
Just used safestrap 2.0 to do a full system backup. I think the confusing thing about pressing the keys to enter or skip the safestrap menu is the lack of haptic feedback when pressing the menu or search softkeys.
Thanks for your work hashcode. Without you the D4 would be lost.
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
Ah the haptic feedback. Yes, I probably should add that back in. As it is, I'm not super thrilled w/ the touch response in the new Safestrap. I probably need to work on it as well. There are times when touches are "lost" and then double up (for 2 touches at once). But hey, it's better than nothing.
I could not agree with you more. I am ecstatic that i was able to make a backup. Now i can work on getting rid of some of this bloat without sacrificing the ability to update again.
Sent from my DROID4 using Tapatalk
I'm behind, say I'm running stock, with safestrap with aokp.
What's the best way to install the leak then install safetrap 2.0?
1. Go to non safe
2. Flash leak
3. Root the leak
4. Install safestrap
That about right?
Any gotchas we should know about?
Sent from my XT894 using Tapatalk 2
Here is the link for detailed instructions. If you have to the fastboot route than it is about an hour long process so my advice is start with a fully charged battery.
http://forum.xda-developers.com/showthread.php?p=26311439
Sent from my DROID4
bonesjones said:
I'm behind, say I'm running stock, with safestrap with aokp.
What's the best way to install the leak then install safetrap 2.0?
1. Go to non safe
2. Flash leak
3. Root the leak
4. Install safestrap
That about right?
Any gotchas we should know about?
Sent from my XT894 using Tapatalk 2
Click to expand...
Click to collapse
Follow the instructions posted but the basic rundown will be..
1. Fastboot .219 images
2. Re root phone with motofail.
3. UPDATE SUPERUSER BINARY!!!
4. Use Voodoo rootkeeper to backup root, temp unroot, and restore root.
5. Install .206 ICS leak with stock recovery
6. Use Voodoo Rootkeeper to restore root.
7. Install Safestrap 2.0
Done, and pretty sweet.
No more data issues!
No more not being able to do video!
No more not being able to use flash!
No more weird youtube glitch!
Now to wait to wait for an AOKP port and I'll be perfectly happy!
...Until the next android comes along...
Have you successfully removed any of this awful mototrash? It almost makes me want to go back to CM9's dailys. It's that awful.
strakajagr said:
Have you successfully removed any of this awful mototrash? It almost makes me want to go back to CM9's dailys. It's that awful.
Click to expand...
Click to collapse
I know your questions was not directed towards me but I used Titanium Backup to freeze all of the bloatware, then realized you can do this within the OS under the APPS list. There is a disable button in each app details screen. I froze almost EVERYTHING, except for the My Gallery/music apps. I pretty much did the same thing when I was running GB...was worried that something would cause a bootloop but was very careful I guess. Battery is MUCH better now!!!
Yeah I've done that for the most part. I just really can't stand the motoblur. It's so frustratingly cartoony and awful and I'm really conflicted about what is worse, the intermittent data or this crappy interface.
strakajagr said:
Yeah I've done that for the most part. I just really can't stand the motoblur. It's so frustratingly cartoony and awful and I'm really conflicted about what is worse, the intermittent data or this crappy interface.
Click to expand...
Click to collapse
Lol tell us how you REALLY feel. I have to agree with you though. Motoblur is dog ugly but then again so are most of the custom interfaces. I prefer vanilla android.
Sent from my DROID4 using XDA
flamefangahs said:
Lol tell us how you REALLY feel. I have to agree with you though. Motoblur is dog ugly but then again so are most of the custom interfaces. I prefer vanilla android.
Sent from my DROID4 using XDA
Click to expand...
Click to collapse
+1 on that... I just really didn't want to purchase the galaxy nexus just to get a vanilla android experience.
Sent from my DROID4 using XDA
Any word on when it will be available to 208 users?
Not working for Newest ICS Leak 6.16.208
gdeeble said:
Any word on when it will be available to 208 users?
Click to expand...
Click to collapse
Good question, I can confirm this new Safestrap does not work for 208. When you push install recovery, it loads and obtains root rights, but it never changes from not installed/not active.
Actually I fixed mine. Make sure you install busybox when you root your phone. I just used the free busybox installer and it fixed it where Safe Strap installed on 208. Woo Hoo! My data from 206 also restored. Thank you god for Hashcode and this wonderful tool. :-D
Dual Boot for P990 & SU660 on Both Bootloaders
Now with more and more new ROMs being released every day and only one phone (at least for most of us) to try them all, I think this was needed.
It is based on the method Bihariel found on a Chinese forum and his latest v2 version for the old bootloader and my previous version 3 for the new one.
It is now modified to work on both bootloaders and Partition layouts. Read change log for details.
Thanks to:
SuperSkill personally, for digging it up from the grave and giving me the vote of confidence to port dual boot into the new bootloader. He is also the 1st after me, who tested it. (thank you again my friend)
KingMGT personally, for helping me make the necessary modifications for SU660 and of course for testing it since I don’t own a SU660. (thank you again my friend)
Bihariel of course, for his great work on which I based the new version (and for copying a lot of text from his thread)
ChinaGB, the creator of the System changer app and the original idea.
What is this useful for?
Devs: you can have one ROM configured and ready for use in one partition and a second partition to test your ROMs without touching your daily ROM, so you won/t need to wipe or backup anything.
Users: you can have a stable ROM, let’s say a stock ROM with everything working and configured and you can have a second partition to test ROMs (for example a custom stock based one or a CM10 beta) so you won't need to do backups and wipes.
How Dual Boot works?
Dual-Enabler.zip: this file enables Dual boot by splitting system partition into two.
Dual-ROM-1-to-XX.zip: this file have to be flashed after flashing ROM 1, after flashing it and boot the phone, you will find an app called system changer, by launching this app and selecting Switch ROM, the phone will reboot and start the ROM 2.
Dual-ROM-2-to-XX.zip: this file have to be flashed after flashing ROM 2, after flashing it and boot the phone, you will find an app called system changer, by launching this app and selecting Switch ROM, the phone will reboot and start the ROM 1.
What ROMs can I use?
P990 Devices:
You can use theoretically, any combination of ROMs for dual booting, working on the same Bootloader of course.
SU660 Devices:
On OLD layout you can use theoretically, any combination of ROMs for dual booting, working on this Bootloader of course.
On ICS layout, due to lack of any custom ROMs for SU660, the p990 layout and bootloader is used so only custom CM, PA & MIUI ROMs are compatible, working on this Bootloader of course.
Attention !! The only ROMs you should not use are Auto-wipe ROMs because they will delete your data partition and with it ROM1 and ROM2 save files. Of course if you are an advanced user, you can open the wipe rom and modify the updater-script to remove the auto wipe lines.
Download from here the package for your device and follow the instructions in post #2.
For older versions follow the instructions included in package.
Change Log:
v5.0 Date 05 Feb 2013
DualBoot-Control.zip. All five zips used till now for enabling/maintaining Dual-Boot have been replaced by this aroma-style flash-able zip.
SU660 package now supports also the su660 ics bootloader & layout.
V4.6 Date 30 Jan 2013
512MB-512MB system partitions for both bootloaders,
Reduced data (to 2000MB) for old-bootloader (because a 2048MB one cannot be formatted on old bootloader)
Bug-fix for dual-boot remover (SystemChanger app wasn't removed).
V4.5 Date 22 Jan 2013
Now it auto enters recovery after repartitioning. No need to keep pressing Vol- & Pwr.
Linux nvflash binary added. (I had forgotten to include it in package, sorry.)
Minor changes in flash.sh (for linux).
V4 Date 20 Jan 2013
It now works on both bootloaders. During repartition with nvflash you have the option to select which one
In old bootloader the system partition is splitted in 370MB for ROM1 and 512MB for ROM2 (in case someone wants to install tonyp's & harsh's full ICS version for old bootloader).
Same simple procedure to enable and maintain dual-boot.
Common flash-able zips because they detect current bootloader and partition layout and act accordingly.
Re-compiled SystemChanger app to display more correct messages and also in which ROM you are switching to.
V3 Date 12 Jan 2013
System partition size is 512 MB for each ROM.
Data partition is still shared but with the max size of 2GB.
Included latest cwm recovery 6.0.2.5 by pengus77. It works for all available ROMs for new BL (DM X, FLEX-ICER & unofficial CM10 CM10.1 ones)
NewBL-Dual-Enabler’s scripts are modified not only for the new layout but now also check and format (if needed) the internal SD (the first time after NVFlash is always needed). It also returns to recovery automatically to let you install or restore the 1st ROM.
NewBL-Dual-ROM-1-to-XX.zip & NewBL-Dual-ROM-2-to-XX.zip no longer need to be updated with the boot images of the ROMs.
SystemChanger app’s scripts, before switching to the other ROM, check if current ROM is changed (by md5 checksum of its build.prop as before) and saves the boot.img for next switch.
noshare file, containing the data folders list, is now also saved under /data/dual-boot. This way it will be always accessible and updatable if needed, no matter which ROM is running.
Boot images and md5 checksums are also saved under /data/dual-boot.
Two more flash-able zips added:
Wipe-ROM-data.zip This will wipe the data of the current ROM. Useful for changing ROM or if required by ROM’s chef
Remove-DualBoot.zip This will wipe the data of the other ROM and will also remove the SystemChanger app and scripts from the current ROM. Useful if you want to make a clean nandroid backup, to restore after a repartition to normal layout.
For V2 change log see bihariel's thread
Here is the guide to get Real Dual boot on both BLs.
Please read carefully because this may mess up your phone if you don't know what you are doing.
Oh!! I forgot, this phone is unbrickable, so give it a try.
Installation Instructions
Extract the downloaded package with WinRAR or similar to any folder.
Copy ROM1, ROM2 and the DualBoot-Control.zip to external SD.
Go to the folder DualBoot-Partition-resizer and run flash.bat (or flash.sh for linux) follow on-screen instructions select BootLoader and wait until NVFlash process finishes and the screen goes black.
Disconnect the USB cable, put the battery back and just power on the phone it will enter into recovery automatically. (It takes about 40 secs to enter recovery 1st time after NVFlash)
Install DualBoot-Control.zip and select Enable Dual Boot option. The phone will reboot (if supported by recovery) and enter in recovery again (if not select reboot recovery from recovery).
Make a full wipe just in case to avoid boot-loops and format /system because it may not be formatted by ROM’s updater-script (mounts and storage --> format /system)
Now flash ROM1 (or restore a nandroid backup of ROM1) and without rebooting install DualBoot-Control.zip, select ROM1 update and reboot when it finishes.
When the phone completely boots, you will find an app called SystemChanger, launch it and click Switch ROM, it will ask you for root rights, click yes, the phone will reboot quickly, press and hold Pwr button + vol down when the screen goes black to enter recovery, if the phone doesn't go to recovery, remove the battery, plug it again and enter recovery.
Format /system (the 2nd system now), because it may not be formatted by ROM’s updater-script.
Now flash ROM2 and without rebooting install DualBoot-Control.zip, select ROM2 update and reboot when it finishes. (Attention: do not restore a backup of ROM2 because it will wipe data files of ROM1)
And that is all, if you want to switch to ROM1, as before, run SystemChanger and click Switch ROM.
Note for those having experienced the older version 2: No need to add boot images in Dual-ROM zips any more.
How to change/update a ROM or Kernel
You have to be on the ROM you want to change/update.
Enter Recovery
If you are changing the ROM or kernel and/or a wipe is needed, install the DualBoot-Control.zip and select Wipe current ROM data.
Flash the ROM or kernel and before reboot install the DualBoot-Control.zip and select ROM1 update if you flashed ROM1 or ROM2 update if you flashed ROM2.
Info: There is also the wipe-rom-x-data.sh in /data/dual-boot/ which can be used to delete the non-running Rom’s data. You can also run this from terminal or adb shell to clean the data of the non-running Rom quickly. For example if you are on ROM1 and you want to change the ROM2 run the script, switch to ROM2 but when screen goes black press pwr & vol- to enter recovery.
How to disable Dual Boot
You have to be on the ROM you want to keep.
Enter Recovery
Install the DualBoot-Control.zip and select Remove Dual Boot. This will wipe the data of the other ROM and will also remove the SystemChanger app and scripts. Useful if you want to make a clean nandroid backup, to restore after a repartitioning to normal layout with AIO-Toolkit.
Enjoy it !!
Wow......one thing i ws missing on NEW BL......thank you so much....now can hold onto this phone for 1more year....
This is just Aweosme <3 will give a try for sure ! LG O2X still the Crazy phone will try today eveng and comment back again ! can i try CM10.1 & V30B (Roms available) ???
Kudooos 4 ur post
This is what i need, i often flash rom 1 to another and restore my app and setting manualy... with this i would keep my daily rom and other for testing
thanks good job
Spyrosk, again, CONGRATULATIONS, this is another great product useful for all of us. To drop the bomb; i think you should add this in AIO, it would be natural if possible. Ive tested this during the weekend, its more easy than the previous gb version. Huge thanks for doing this spyrosk and also huge thanks to Bihariel who did the gb version, you have my deepest respect
Let me give you another challenge lol
It should be possible to.......no no, I must shut up now.
Thanks mate
Nice ! Trying soon... :fingers-crossed:
SuperSkill said:
Spyrosk, again, CONGRATULATIONS, this is another great product useful for all of us. To drop the bomb; i think you should add this in AIO, it would be natural if possible. Ive tested this during the weekend, its more easy than the previous gb version. Huge thanks for doing this spyrosk and also huge thanks to Bihariel who did the gb version, you have my deepest respect
Let me give you another challenge lol
It should be possible to.......no no, I must shut up now.
Thanks mate
Click to expand...
Click to collapse
Thank you too again.
No, don't give me another challenge now. :laugh:
I am thinking on making a v3 version for old bootloader too, or even better a v4 hybrid one for both bootloaders. So I do have work for now.
Yes I could integrate that into AIO-toolkit eventually in an "Addvanced Options" menu , but let's see how it is working, when more users will try it and "cure" any "baby sicknesses" that may come up first.
I can't thank you enough for your testing it so thoroughly.
I really appreciate it.
i don't really understand how this dual boot work
but, can i use my internal sd card for booting stock-based custom rom and using my external one for booting CM10 based rom?
what about ics and gingerbread on dual boot!?
jhonjames09 said:
what about ics and gingerbread on dual boot!?
Click to expand...
Click to collapse
you couldn't do that unless someone release GB rom for ics bootloader (is that even possible?)
Nice man" I ll try it soon!
jhonjames09 said:
what about ics and gingerbread on dual boot!?
Click to expand...
Click to collapse
babi_perang said:
you couldn't do that unless someone release GB rom for ics bootloader (is that even possible?)
Click to expand...
Click to collapse
I don't know if this will be ever possible or if it's worth trying it.
The only thing that can be done at the moment, is having one 370MB & one 512MB system partitions on the upcoming gb dual-boot version for installing the tonyp's and harsh's full ics 28g version as 2nd ROM on old bootloader.
I installed yesterday dual boot on my 2X and worked fine without any problems!
Great tool Spyrosk!!
You have done our life easier!!!
Thank you for dual boot
is indeed something very special!!!
It works beautifully for me,
the P990 is significantly upgraded:laugh:
And what about dual boot with linux?
tomsi91 said:
And what about dual boot with linux?
Click to expand...
Click to collapse
What do you mean? Read step 3 carefully.
3.Go to the folder NewBL-DualBoot-Partition-resizer and run flash.bat (or flash.sh for linux) follow on-screen instructions and wait until NVFlash process finishes and the screen goes black.
sorry, i didnt see it with linux
EDIT: no sorry. i mean, i want to dualboot android/linux (debian, ubuntu, etc.).
tomsi91 said:
sorry, i didnt see it with linux
EDIT: no sorry. i mean, i want to dualboot android/linux (debian, ubuntu, etc.).
Click to expand...
Click to collapse
And iOS & Windows Mobil 8...
How about flashing the second rom that have aroma installer??
By example of this thread, I thought it would be convenient to also create a separate thread for our L5. I will update this first post with relevant information and links when needed.
Info
CyanogenMod's site: http://www.cyanogenmod.org/
Announcement on Google+ by CM: link
Screenshots by luKi13223: link
Screenshots by Sirrocco with dpi lowered to 130 and theme applied: link
Requirements
Properly unlocked boot loader (here, a guide on top of first post)
Root/working CWM
Ability to read and common sense
Downloads
Nightlies started building. You can get the latest build from http://get.cm/?device=e610 OR http://10.cmxlog.com/?device=e610
CWM Recovery by Ricardo Cerqueira (CyanogenMod): Direct download. Alternatively you can download the flashable zip provided in the attachment, it's the same, but easier to install if you already had a recovery installed.
Google Apps (GAPPS) for Jelly Bean/CM10: http://goo.im/gapps/gapps-jb-20121011-signed.zip
Short Installations guide
Make sure you meet the requirements
Download needed files (see above) and place them on your internal sd card
Update your ClockWorkMod Recovery to v6.0.2.8 (you can do this by using terminal, adb (guide) or use the flashable zip I've attached
This will avoid status(7) error messages and prevent issues with ROM Manager.
Flash "cm-10-build date-NIGHTLY-e610.zip" from your internal sd card with CWM (or if you prefer with ROM Manager)
[*]Optional: Flash custom kernel by PinkFlozd: link to thread WARNING: Don't install this kernel with builds created on 21 april 2013 or later (at least not untill someone updates the kernel)
Optional: Flash "gapps-jb-20121011-signed.zip"
After first boot see if your receiving any signal (provided your normally have any signal on that spot). If not, don't worry, a simple reboot might fix it.
Enjoy
Bugs:
Considering these are the very first nightly builds of CM10 for our device, the dev did a pretty great job. Almost everything is working. Thanks to him :highfive:
Network / data is not working after 1st boot. A simple reboot after a few minutes might fix this
Multi-touch not fully working (dual touch works)?
SD card is full error, while there is still room left (up to at least 300 MB). I haven't experienced this bug in a while, it may be fixed, but I'm not sure.
Accelerometer
Small mods/Fixes
Wake with Home key
Pinkflozd's custom kernel[/COLOR]. Supports multi-touch and allows for overclocking. His kernel doesn't work with builds after April 14th
Overclocked kernel for builds made after April 14th
Workaround to make accelerometer work
:
i tried to flash this on my E612..
But i got an error.
Error in sdcard/cm blah blah.zip
(status 7)
Installation aborted.
Ianuz1320 said:
i tried to flash this on my E612..
But i got an error.
Error in sdcard/cm blah blah.zip
(status 7)
Installation aborted.
Click to expand...
Click to collapse
same here...
Will the developer look here for bugs? Or is there some other way to report CM10 bugs?
Anyway, I noticed that it drains battery much faster than the stock rom too.
Tonight it drained 20% of battery just by standby.
Ianuz1320 said:
i tried to flash this on my E612..
But i got an error.
Error in sdcard/cm blah blah.zip
(status 7)
Installation aborted.
Click to expand...
Click to collapse
First install the recovery provide by CM. This will fix this problem. You will need to copy your flashables zips and back ups to the internal SD-card, because this version only mounts internal SD (instead of only the external)
E.jr said:
Will the developer look here for bugs? Or is there some other way to report CM10 bugs?
Anyway, I noticed that it drains battery much faster than the stock rom too.
Tonight it drained 20% of battery just by standby.
Click to expand...
Click to collapse
I don't know if he will look here. We could inform him about it, when we have more clarity about the bugs.
My main purpose was to concentrate talk about CM10 in one place, because in the other thread also other subjects were discussed and it got messy. And we might help each other here with CM10 related problems.
ldeleeuw said:
First install the recovery provide by CM. This will fix this problem. You will need to copy your flashables zips and back ups to the internal SD-card, because this version only mounts internal SD (instead of only the external)
Click to expand...
Click to collapse
thank you buddy..but where can we get recovery provide by CM?
For Instalation aborted :
Open downloaded zip by winrar or 7zip.
Open Meta-inf>google>android>updater-script
Open updater-script by notepad++
Delete first lane in updater-script
Save and rebuild archive (automaticly)
Copy your package to sd card and instal via cwm
Kisloo said:
For Instalation aborted :
Open downloaded zip by winrar or 7zip.
Open Meta-inf>google>android>updater-script
Open updater-script by notepad++
Delete first lane in updater-script
Save and rebuild archive (automaticly)
Copy your package to sd card and instal via cwm
Click to expand...
Click to collapse
it's not working buddy.
delete this lane :
assert(getprop("ro.product.device") == "e610" || getprop("ro.build.product") == "e610");
Click to expand...
Click to collapse
and it will work
Thanks buddy.. it worked on my phone!! but first boot took so long..i was stuck on CyanogenMod boot logo!! untill now!
Ianuz1320 said:
thank you buddy..but where can we get recovery provide by CM?
Click to expand...
Click to collapse
check first post
The new nightly does seem to lag a little as opposed to the original one.
The first one was smoother I've noticed.
E617
Has anyone tried CM10 for the E617 version of the L5? I'm to much of a newb to try it myself, I wouldn't be able to find my way back if I screwed-up my phone.
Bootlop
Im on cm bootloop about 20 minutes WHEN THIS WILL BOOT UP
I noticed that this cm10 for e610 has a kind of problem with multitouch,I have played shadow gun,modern combat 3 and modern combat 4 and six guns and in all these 4 games, I noticed that I can't move at the same time that I shoot,I wait that they solve this problem in next updates ;p
Sent from my LG-E610 using xda premium
Kisloo said:
delete this lane :
and it will work
Click to expand...
Click to collapse
thanks a lot mate!
---------- Post added at 08:57 PM ---------- Previous post was at 08:53 PM ----------
DodoKoce said:
Im on cm bootloop about 20 minutes WHEN THIS WILL BOOT UP
Click to expand...
Click to collapse
E: I found out why there is a bootloop, we didn't took the right bootloader, see here my tutorial: http://forum.xda-developers.com/showthread.php?t=2186161 - if you do everything like i did, everything will work properly
Use older build, idk - new is more bugged :/ Old working smarter than new.
OK, I've got it installed (nightly 20130310), first I installed the provided CWM (6.0.2.8), had to do that manually though, because for some reason Rom Manager destroyed the 6.0.2.5 version I had when I tried to install CWM through Rom Manager.
It's running smoothly, although I also see a little graining in the screen. I had no data issues.
Also, booting didn't take that long.
One strange phenomenon:
I had FreeL5 running before CM10. Before flashing CM10 I did a factory reset from CWM, cleaned cache and Dalvik cache. After booting CM10 for the first time, my WiFi settings were still there... hadn't expected that, but since I'm on a corporate WiFi connection which needs a username and password to connect, it was nice not to have to retype it :victory:
---
Previous devices:
HTC Desire - MIUI
HTC Desire HD - MIUI
Sony XPeria S - FreeXPeria JB
Current devices:
Samsung Galaxy Tab 2 7.0 - Stock JB (because my girlfriend doesn't want me 'messing' with it)
LG Optimus L5 (E610) - CM10 nightly
Bootloop too, any way to solve?
Okay i only started looking at multirom around 4hours before releasing this, so i am aware we already have a multiROM thread, however i do believe it's outdated, and perhaps unsupported now, so i am merging a supported multirom with my TWRP thread where i will be keeping both updated, thanks to @Tasssadar for bringing multiROM to the android community. I failed hard with outdated sources from adam so i have written my own stuff, but i think iodak is using his .diff
Taken and modified from official thread at Flo
Introduction
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, once they are ported to that 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 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
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. 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
Manual installation
Find all needed files here: MOD Edit: Links removed
I think Iodak has the kexec patch so use his Rom, i'm not too sure on how to add a kexec so i'll look into it, this does support KK roms as i tried it, and so has dan.
MultiROM has 3 parts you need to install:
MultiROM multirom.zip - download the ZIP file from second post and flash it in recovery.
Modified recovery (TWRP_Mrom.zip) - download and flash in recovery.
Patched kernel - Iodaks kernel i believe is kexec patched, worked for me, have a play, i use share kernel for KK roms of the same type. I suggest this.
You current rom will not be erased by the installation.
Download links are somewhere below
Adding ROMs
Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Updating/changing ROMs
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.
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.
Source code
MultiROM - https://github.com/Tasssadar/multirom/tree/master (branch master)
Modified TWRP - https://github.com/Tasssadar/Team-Win-Recovery-Project (branch master)
Device Tree for building Mrom and TWRPhttps://github.com/Fluoxetine/android_device_lge_p880 (branch TWRP)
Thanks and Links
Official thread with screenshots, donate link, and changelogs
Original Thread for 4xHD by @Adam77Root
FAQ and other notes
About security
In order to make multi-booting possible, MultiROM has to sacrifice some security measures. Firstly, on secondary Android ROMs, /system is not mounted read-only. While there are other things preventing malicious software from messing with /system, this might potentialy make it easier for such software to attack that system.
Next, MultiROM doesn't work with /data encryption. Not many people who use custom ROMs also use encryption anyway, so that isn't much of a concern.
What do the ROMs share?
All ROMs are separate, except /sdcard, which is shared between all Android ROMs.
How many ROMs can I have?/Where are the ROMs stored?
You can have as many ROMs as you can fit in your /sdcard. All the ROMs are stored in /sdcard/multirom/roms or on an USB drive. This folder is unaccessible in Android, to prevent mediascanner from scanning it. You can either in recovery, or obtain root and go to /data/media/0/multirom/roms.
Can I have different versions of Android working alongside
Yes. As long as you select "Don't shere kernel" when installing the secondary ROM, the systems are separated.
MultiROM recovery says it's 2.6.3.0. Why isn't it updated to 2.6.3.*highernumber*?
It is, it just shows wrong version.
The menu with all the ROMs won't show up during boot, how to fix it?
Either re-flash the MultiROM zip or go to recovery, Advanced -> MultiROM -> Inject curr. boot sector.
The reason for this is that something rewrote your boot.img, which happens for example when you flash a kernel. MultiROM's boot menu is part of the boot image, so it has to be added into it again.
Will you port MultiROM to device X?
No, probably. I won't port MultiROM to any device I don't own, because it is very difficult to provide the level of support I want to provide if I can't test things myself, as proven by the Nexus 4 port. I'll probably keep buying Nexus devices and keep porting MultiROM to those myself, but I can't buy every single device - I'm still a student, all my existing devices were bought using some kind of money grant or donations from users.
But, you can port it yourself, the wiki should give you at least some idea how to do that: https://github.com/Tasssadar/multirom/wiki/Porting-MultiROM
Message from Fluoxetine
I spend a lot of time trying to bring new roms/mods to this and many other devices, this doesn't really cost me anything so i will not ask for money, however i am open to other donations, if you can supply me with a donated spot on a build server that would be great! Otherwise, you can supply me with Drink and Food to snack on whilst i work away, just PM me with an amount and i'll choose a product from amazon and send you my address and info for it to be shipped directly to me Thanks for your time guys.
Click to expand...
Click to collapse
-
-
-
-
-
-
Changelog from my end and not multiROM (Ascending Order)
Code:
- [I] Release within 4 hours of solid working on it [/I]
- Fix Recovery
- Fix touch input
- Build Multirom.zip
- Remove weird vibration
- Fix MultiRom button
- Fix Layout
- Build Modified TWRP
- Create TWRP.fstab
- Build MultiRom.zip
- Fix Sizing
- Build Initial MultiRom.zip
- Create mr_init_devices.c
- Create a modified BoardConfig.mk
- Sync Modified TWRP
- Sync MultiRom
- Sync Omni
Reserved
Great work
Sent from my LG-P880 using Tapatalk
Ha, it's working... Somtimes it's a bit tricky to install secondary ROMs. To get Zaiben RC8 booting I installed it from a backup.
Pure CM11 (20140220 nightly) without gapps is booting, after flashing gapps in MultiROM it dosn't boot. Only using a backup to create it as secondary works for me...
But no way to install AnyKernels like Iodak9.95 om secondary. For CM/ASOP you can try sharing option, for stock-based the only way is using backup with installed custom kernel...
Since AnyKernel there are no boot images for different roms, so there is nothing to inject...
One downer for me is missing ADB in recovery. I've tried mounting USB-Device first, no way. Device manager in Windows shows nothing.
In bootmenue ADB is working, but it's useless without mounted system, data etc. When I use "adb shell mount -o remount,rw system" I got "mount: can't find system in /proc/mounts"
And I noticed after booting any secondary ROM, primary needs wiping cach/dalvikcache to prevent a bootloop...
EDIT: Got system access from ADB...
Code:
adb shell mount /dev/block/platform/sdhci-tegra.3/by-name/APP /system
Nice work man! Does ADB work in MultiROM? Did you check new hardboot patches? It doesn't need target kernel to be patched anymore.
Sent from my OmniROM-powered LG Optimus 4X HD
Adam77Root said:
Nice work man! Does ADB work in MultiROM? Did you check new hardboot patches? It doesn't need target kernel to be patched anymore.
Sent from my OmniROM-powered LG Optimus 4X HD
Click to expand...
Click to collapse
I've got ADB only working from boot menu. With correct mounts from ADB shell I'm able to modfy anthing I need...
But ADB working in TWRP would be nice
Adam77Root said:
Nice work man! Does ADB work in MultiROM? Did you check new hardboot patches? It doesn't need target kernel to be patched anymore.
Sent from my OmniROM-powered LG Optimus 4X HD
Click to expand...
Click to collapse
I don't think ADB works in multiROM, i saw in your patch a few ADB related stuff but in all honesty i think i left them and am still using all the same ones as grouper :') But i will be looking into this.
Also i haven't checked out any of the new hardboot patches, because in all honesty i have no clue what they are :highfive: but i can learn, i'll look into it now I just threw myself at multirom and looked at whatever the other devices had, and then just made it for p880 :3 Touch was an asshole Till i realized all i had to do was change b to an a.
Edit 1: This was the device specific mrom stuff i needed to add https://github.com/Fluoxetine/android_device_lge_p880/blob/TWRP/mr_init_devices.c
Edit 2: Added https://github.com/Tasssadar/androi...mmit/005cf387c1404eac862cc35153d7641d18faef4c this commit manualy, well for the files we had i added, we didn't have lge_devices or reboot.c and reset.c was different :s
Compiling stock CM11 kernel with this patch and see if i can dual boot stock with stock kernel that isnt patched, or cm10.1 with stock cm10.1 selecting "don't share"
Edit 3: Getting Errors with the changes i made, so gonna need some more time to amend them for the p880, i think i might have to call on some other devs to help out with this, i have no idea what i'm doing..
Nice work, could I ask you to prepare multirom uninstaller also?
It is working very well, thanks for this. All I do was I installed a CM-based Kitkat rom (Mokee) in the internal, and for the secondary, I installed stock rom (Zaiben) with kernel sharing enabled. Both roms are working flawlessly.
Thanks man I love your work!!
We can install FirefoxOS and Ubuntu too? MultiRom Manager working?
Sent from my LG-P880 using XDA Premium 4 mobile app
Can't seem to get anything to boot as secondary, I've tried zaiben and nameless. From backup and from zip, with and without kernel sharing.
Most times device just shuts down, once I got to boot animation and then it froze.
All backups normally boot as primary.
Primary uses latest iodak.
Probably I'm doing something wrong since others report it working.
Sent from my LG-P880 using Tapatalk
dcos said:
Can't seem to get anything to boot as secondary, I've tried zaiben and nameless. From backup and from zip, with and without kernel sharing.
Most times device just shuts down, once I got to boot animation and then it froze.
All backups normally boot as primary.
Primary uses latest iodak.
Probably I'm doing something wrong since others report it working.
Sent from my LG-P880 using Tapatalk
Click to expand...
Click to collapse
Try having your device connected to ac power while rebooting to secondary. If that works, then its the same problem as with adams multiboot, but it has two workarounds
Will you keep the non-dualboot twrp ?
I'm really not into this dual boot gimmicks and really like, and am still using your "clean" twrp version that works flawless BTW
Tapatalked from my CM11-LG4XHD-P880
remorema said:
Will you keep the non-dualboot twrp ?
I'm really not into this dual boot gimmicks and really like, and am still using your "clean" twrp version that works flawless BTW
Tapatalked from my CM11-LG4XHD-P880
Click to expand...
Click to collapse
You can use this recovery witout flashing the multiboot binarys... And the N7 multirom uninstaller works after editing the updater-script.
dcos said:
Can't seem to get anything to boot as secondary, I've tried zaiben and nameless. From backup and from zip, with and without kernel sharing.
Most times device just shuts down, once I got to boot animation and then it froze.
All backups normally boot as primary.
Primary uses latest iodak.
Probably I'm doing something wrong since others report it working.
Sent from my LG-P880 using Tapatalk
Click to expand...
Click to collapse
When you see in listeted roms with shared boot "remove boot.img" ,you can do this.
When I klicked "share boot" on ROM installation and after flashing it have its own boot.img. Don't know why, those ROMs will not boot on my device...
I lose signal on Miui 4.2.2 and CM10.1.3 dosen't boot.
I use Omnirom 4.4 and Iodak 9.95 as default.
Dual boot would be intresting if Android/data/ of secondary rom was on the external sdcard. I'm not very confident of using a secondary rom sharing that same folder as the primary rom. IMO that could cause some issues. Example: if I uninstall a game I'm secondary ROM the obb file of that ROM will be deleted on primary ROM and vice versa.
Tapatalked from my CM11-LG4XHD-P880
love you guy! i like the idea of having multiple roms, but I never got this stuff running not on my Lg 4X either on my nexus 7 - hope to get it working now with this release
Kexec for stock Cm11 kernel?
Can someone patch stock Cm11 kernel with kexec-hardboot ?
Okay so, i have uploaded CM11 stock kernel with a kexec patch, although this is not the same patch as used in iodak or stock patched kernel, i have taken the commits from groupers kernel with kexec and have implemented them into our stock cm11 kernel (took ages, had to do it manually).
This should mean that the target kernels do not need to be patched, only the host kernel needs the patch, i tried this with carbon-kk with my kernel flashed and added Carbon-KK WITHOUT SHARING kernel, then when i selected it to boot, as soon as the screen goes black HOLD THE POWER BUTTON, and then it will boot into the secondary Rom with the stock kernel that comes with it!
Well i think so anyway, Danny is testing for me now, maybe some of you could test it too? I'm not sure what will happen, i only tried it with carbon and my kexec as host, and stock carbon as target.
Link is here for the kernel http://d-h.st/j9Z or just check my folder in OP for the MultiROM stuff
For those who are having signal problems or no mobile internet connection from secondary ROM(s) with kernel sharing, you have to copy the kernel modules (baseband_usb_chr.ko, raw_ip_net.ko, scsi_wait_scan.ko) from internal ROM module folder (/system/lib/modules) to your secondary ROM. Make sure to change the permissions as well.
Just my 20 cents .
not able to flash kernel in secondary roms
hi, i have Enox rom as default rom and i installed omni 4.4.2 kk rom as secondary, and no kernel sharing.
now it boots my Enox rom but doesn't boot omni with error to have kernel with patch
so i go in advance > multirom > select omni > flash zip > and flash iodak kernel 9.95, but it fails every time, i tried iodak 9.5 too, but same,
am i doing something wrong or its not possible to flash kernels in secondary roms?
then what am i supposed to do now?
i really don't wanna change kernel of my default rom, it's working perfect with amazing battery life that i want, but i want secondary roms with different kernels ?