Q&A for [MOD][14 GEN 2015] [LS990] Multirom
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [MOD][14 GEN 2015] [LS990] Multirom. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Say device unsupport but i have a ls990
I was really looking forward to using multirom, but once i downloaded and opened it, it said device not supported... but the thread is for LS990 which is the device i have. so i dont not understand why i cannot use it.
Sneakygasm said:
I was really looking forward to using multirom, but once i downloaded and opened it, it said device not supported... but the thread is for LS990 which is the device i have. so i dont not understand why i cannot use it.
Click to expand...
Click to collapse
Did you flash all three files, in this order, before trying to use it?
1- reboot in recovery and flash the new TWRP with Multirom support; --> HERE
2- reboot the recovery;
3- flash the kernel with the kexec hardboot patch HERE
4- flash the multirom zip; ---> HERE
5- install every Rom you want ( advanced--> multirom --> add rom )
6- reboot and choose the rom you want to boot.
[Sorry, first time I pasted the wrong information]
help with multirom
Team, i am interested in multirom please help me understand and use it. 1st i am rooted stock zv6. I have installed the multirom twrp also the supported kernel. My understanding of multirom is being able to switch between roms without having to wipe and losing data. Is this correct? Id like to test more but i hate losing data. Id like to keep zv6 as primary and try customs to see what else i like. Like i said i have multirom installed and zv6 as primary i tried illusion as secondary. When i tried to flash illusion it said boot error and i had to recover zv6. I read that illusion kernel dont work with multirom.
1st can you use different roms without wiping?
2nd what are 2 usable roms to try to test this?
3rd. Help with gapps? Im not sure what to ask about this. What is best gapps i downloaded "pa gapps" does it flash after aosp based rom?
Thanks in advance for pointing me in right direction.
1moneymark said:
Team, i am interested in multirom please help me understand and use it. 1st i am rooted stock zv6. I have installed the multirom twrp also the supported kernel. My understanding of multirom is being able to switch between roms without having to wipe and losing data. Is this correct? Id like to test more but i hate losing data. Id like to keep zv6 as primary and try customs to see what else i like. Like i said i have multirom installed and zv6 as primary i tried illusion as secondary. When i tried to flash illusion it said boot error and i had to recover zv6. I read that illusion kernel dont work with multirom.
1st can you use different roms without wiping?
2nd what are 2 usable roms to try to test this?
3rd. Help with gapps? Im not sure what to ask about this. What is best gapps i downloaded "pa gapps" does it flash after aosp based rom?
Thanks in advance for pointing me in right direction.
Click to expand...
Click to collapse
To flash new secondary ROMs you need to do it from with the MultiROM menu in the modified TWRP. If you just flash normally you're replacing the primary ROM.
Illusion works fine. I have it as my secondary ROM. Once you have a good installation of the modified TWRP, Kernal and the multiROM app, boot into recovery, tap Advanced, then MultiROM. Tap Add ROM, navigate to Illusion, and install. To flash GApps, reboot into recovery again, tap List ROMs, choose Illusion, then Flash Zip, and choose your Gapps file.
A for what Gapps, I used the one recommended in the Illusion thread.
meyerweb said:
To flash new secondary ROMs you need to do it from with the MultiROM menu in the modified TWRP. If you just flash normally you're replacing the primary ROM.
Illusion works fine. I have it as my secondary ROM. Once you have a good installation of the modified TWRP, Kernal and the multiROM app, boot into recovery, tap Advanced, then MultiROM. Tap Add ROM, navigate to Illusion, and install. To flash GApps, reboot into recovery again, tap List ROMs, choose Illusion, then Flash Zip, and choose your Gapps file.
A for what Gapps, I used the one recommended in the Illusion thread.
Click to expand...
Click to collapse
Ok. I am doing something wrong. I go into twrp, advanced, multirom, illusion and install but when i reboot it goes to stock rom. When i go to swap roms and load illusion. It boots into a boot error. Then i have to boot into recovery and flash backup.
1moneymark said:
Ok. I am doing something wrong. I go into twrp, advanced, multirom, illusion and install but when i reboot it goes to stock rom. When i go to swap roms and load illusion. It boots into a boot error. Then i have to boot into recovery and flash backup.
Click to expand...
Click to collapse
Did you install all three files in the multirom thread (TWRP, Kernel and the MultiROM program) http://forum.xda-developers.com/sprint-lg-g3/development/mod-multirom-t3002649?
Installed in the right order (see post #2 in that thread)?
If so, when the phone boots, you should briefly see a menu of sorts that includes a "boot now" button. Tapping that will take you to a boot menu where you can select which ROM to boot. Alternately, while on the boot screen, you can press a volume key to get to the selection screen. If you don't do anything the phone will boot into your primary ROM by default.
If you don't see that "boot now" screen, then I think you didn't install something right.
And I don't think you can make the stock ROM a secondary. It's too big for MultiROM to handle.
meyerweb said:
To flash new secondary ROMs you need to do it from with the MultiROM menu in the modified TWRP. If you just flash normally you're replacing the primary ROM.
Illusion works fine. I have it as my secondary ROM. Once you have a good installation of the modified TWRP, Kernal and the multiROM app, boot into recovery, tap Advanced, then MultiROM. Tap Add ROM, navigate to Illusion, and install. To flash GApps, reboot into recovery again, tap List ROMs, choose Illusion, then Flash Zip, and choose your Gapps file.
A for what Gapps, I used the one recommended in the Illusion thread.
Click to expand...
Click to collapse
meyerweb said:
Did you install all three files in the multirom thread (TWRP, Kernel and the MultiROM program) http://forum.xda-developers.com/sprint-lg-g3/development/mod-multirom-t3002649?
Installed in the right order (see post #2 in that thread)?
If so, when the phone boots, you should briefly see a menu of sorts that includes a "boot now" button. Tapping that will take you to a boot menu where you can select which ROM to boot. Alternately, while on the boot screen, you can press a volume key to get to the selection screen. If you don't do anything the phone will boot into your primary ROM by default.
If you don't see that "boot now" screen, then I think you didn't install something right.
And I don't think you can make the stock ROM a secondary. It's too big for MultiROM to handle.
Click to expand...
Click to collapse
Ok. Im getting closer. So i add rom in twrp then during boot i can pick whichto boot to. When i tried to boot to illusion said kernel crash. Yes i flashed all 3 in order listed. Is there a better kernel to use? I was thinking the swap rom in twrp would switch roms and boot into it for me.
1moneymark said:
Ok. Im getting closer. So i add rom in twrp then during boot i can pick whichto boot to. When i tried to boot to illusion said kernel crash. Yes i flashed all 3 in order listed. Is there a better kernel to use? I was thinking the swap rom in twrp would switch roms and boot into it for me.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=58643700
hey guys, hows ubuntu running on the lg? I have ubuntu installed in my usb for my PC and it works great, just on the USB lol, hows the overall performance on LG?? internet speed??
Sent from my LGLS990 using Tapatalk
Related
I have an S4 with CM10.2 which was done through the CM installer.
Unlike traditional rooting, cyanogen installer roots and installs the cm Rom in a few clicks automatically.
This new method leads me to believe that I must unroot to stock and root manually in order to use a different ROM.?
Or can I go ahead and download a rom, put it in the sd card, boot into the thing, and flash the ROM?
I'm trying to flash foxhound ROM.
Need an answer guys, it's not on Google.
Bumping this.
I don't have an s4 nor have I ever used a oneclickrootmeapp but to my understanding on how the cyanogen installer works is that it flashes clockwork recovery and cyanogenmod + kernel to your device
So I would say 99% sure that no you don't need to do anything special here, steps I would take
Download ROM of choice + gapps or any extras needed
Check md4sums for match
Put on SD
Boot to recovery
Do a nandroid backup
Wipe everything but SD
Flash ROM and whatever else needed
Reboot
And all should be just fine
Sent from my Nexus 4 using XDA Premium 4 mobile app
I salute you.
Been on the Samsung side of the street for the past four years so if it wasn't named after a accient Viking God then I'm lost However just a couple questions if I may: I am unlocked, rooted, recovery installed, & TA backed up however not real sure how the whole boot image flash works, does this need to be done everytime I go to flash a ROM? Also do I have to reflash recovery everytime I flash a ROM? just remember reading that somewhere, been trying to read all I can
nickfar2000 said:
Been on the Samsung side of the street for the past four years so if it wasn't named after a accient Viking God then I'm lost However just a couple questions if I may: I am unlocked, rooted, recovery installed, & TA backed up however not real sure how the whole boot image flash works, does this need to be done everytime I go to flash a ROM? Also do I have to reflash recovery everytime I flash a ROM? just remember reading that somewhere, been trying to read all I can
Click to expand...
Click to collapse
You only need to flash a boot image once to get the recovery going if you have a locked bootloader then this will have to be done, if it is unlocked as you have said then you do not need to do this again. The recovery should stay how it is. Some kernels that you can flash have twrp and usually cwm included, when you flash it you'll have access to both.
Cool, welcome!
The recovery is included in the kernel (boot.img), so it's automatically updated/flashed every time you install a ROM zip through recovery. The very first time you install a CM/AOSP/etc ROM, you may have to first flash the boot image through fastboot, like you said, to get a recovery compatible with the ROM. I think you only have to do this when going from stock based recovery to AOSP based recovery.
Oops, got beaten.
theinspector said:
You only need to flash a boot image once to get the recovery going if you have a locked bootloader then this will have to be done, if it is unlocked as you have said then you do not need to do this again. The recovery should stay how it is. Some kernels that you can flash have twrp and usually cwm included, when you flash it you'll have access to both.
Click to expand...
Click to collapse
Not quite correct but close
You have installed recovery (dual by [NUT]?). most ROMs are completable with both twrp and cwm. Just flash the zip for the rom (after making a backup. choose the recovery that is in the ROM*). if this fails then you can flash the boot.img from the zip with adb/fastboot (fastboot flash boot <boot_img_name>). most ROMs only contain one recovery
* CM based normally have cwm. Slim, omni, candy all use twrp from memory
Okay thanks guys very much appreciated, so if I'm understanding you correctly then I don't need to flash any "boot images" becuase I am already unlocked and on a non stock recovery(dual recovery by NUT) becuase the "boot image" is just the recovery? So since I already have nuts dual recovery then I should be good to
Enter TWRP
Nandroid, Wipe
Flash CM 11+Gapps
Reboot
???
If not correct please let me know, sorry just trying to make sure I'm understanding this correctly, and if not then my ass needs to go read some more ;+)
nickfar2000 said:
Okay thanks guys very much appreciated, so if I'm understanding you correctly then I don't need to flash any "boot images" becuase I am already unlocked and on a non stock recovery(dual recovery by NUT) becuase the "boot image" is just the recovery? So since I already have nuts dual recovery then I should be good to
Enter TWRP
Nandroid, Wipe
Flash CM 11+Gapps
Reboot
???
If not correct please let me know, sorry just trying to make sure I'm understanding this correctly, and if not then my ass needs to go read some more ;+)
Click to expand...
Click to collapse
boot.img is the kernel (and ramdisk etc) + recovery
If you are going to flash CM the do it from cwm as then the nandroid backup can be flashed from the recovery that cm uses. other than that you are about right (wipe both caches and /data, dont wipe /system. the ROM will take care of this)
Q&A for [RECOVERY] TWRP Recovery 2.8.1.0 - Thor
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY] TWRP Recovery 2.8.1.0 - Thor. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Tried it on 13.3.2.4 with know dice. You have to hard reset a couple of times and then safestrap comes back up. Tried a few times with zero luck so I just flashed twrp2.7.1 and all is good again. Also made me post here because I have less than 10 posts.
Kudos!
Firstly - thanks very much to all people involved in this - especially vortox - excellent work!
Secondly, I've just flashed TWRP successfully on 13.3.0.5.
The only thing which seems a bit strange is that when starting TWRP, I have to wait until the HDX's display goes into power-saving mode (i. e. goes deeply black) and switch the display on again before the starting screen of TWRP can be seen & TWRP be used (before that point, the display black for a while, but not in power-saving mode).
Is this normal?
I have made a grave error and have no recovery.
Well watching this special day unfold I mistakenly lost my original backup recovery.img and after dd now have no recovery. What can I do to get a working stock recovery.img back onto /dev/block/mmcblk0p18. When I dd twrp I apparently wasn't ready and now I have no recovery. I am running the rollback 13.3.0.9 and still have root/safestrap.
Nevermind I followed this and fixed my stock recovery.
http://forum.xda-developers.com/showthread.php?t=2782159&page=20
Certainly no expert here, but can't you just flash the TWRP recovery via Rashr or Flashify while the OS is running...? Or do you just want to have the stock recovery image? If I'm misunderstanding your question - sorry.
nocmonkee said:
Well watching this special day unfold I mistakenly lost my original backup recovery.img and after dd now have no recovery. What can I do to get a working stock recovery.img back onto /dev/block/mmcblk0p18. When I dd twrp I apparently wasn't ready and now I have no recovery. I am running the rollback 13.3.0.9 and still have root/safestrap.
Click to expand...
Click to collapse
RiseT said:
Certainly no expert here, but can't you just flash the TWRP recovery via Rashr or Flashify while the OS is running...? Or do you just want to have the stock recovery image? If I'm misunderstanding your question - sorry.
Click to expand...
Click to collapse
Sure but it never would boot into recovery or it was booting into an unexploitable recovery. I hadn't fully downgraded it yet or something went wrong so I had no usable recovery. I couldn't use amazon's tools to fix it and I could properly install twrp, so after "Amazon Recovery" worked again I was able to boot into the rollback image and use amazon's own upgrade bin. "update-kindle-13.3.1.0_user_310079820.bin". Once it went through the Amazon upgrade process. I used the KFHDX Toolkit to root it, then I adb'd into it and then su'd to root and immediately dd'd the TWRP recovery and then did reboot recovery in adb and "TADA" I had working twrp recovery and was able to install the CM 11 and gapps.
I see. Great to hear that it's working now. As you've successfully installed TWRP & CM 11 now - could you confirm the above stated behaviour regarding the black screen? Additionally to TWRP, I've just installed CM as well; interestingly, the display is showing the same behaviour with CM as with TWRP (I can only see something after the display returned from power-saving mode). With Amazon stock recovery & ROM, this isn't the case, so it shouldn't be a hardware problem.
nocmonkee said:
Sure but it never would boot recovery. I hadn't fully downgraded it yet or something went wrong so I had no recovery. After "Amazon Recovery" worked again I was about to boot into the rollback image and use amazon's own upgrade bin. "update-kindle-13.3.1.0_user_310079820.bin". Once it rebooted I used the KFHDX Toolkit to root it, then I adb'd into it and then su'd to root and immediately dd'd the TWRP recovery and then did reboot recovery in adb and "TADA" I had working twrp recovery and was able to install the CM 11 and gapps.
Click to expand...
Click to collapse
RiseT said:
I see. Great to hear that it's working now. As you've successfully installed TWRP & CM 11 now - could you confirm the above stated behaviour regarding the black screen? Additionally to TWRP, I've just installed CM as well; interestingly, the display is showing the same behaviour with CM as with TWRP (I can only see something after the display returned from power-saving mode). With Amazon stock recovery & ROM, this isn't the case, so it shouldn't be a hardware problem.
Click to expand...
Click to collapse
I am not experiencing this black screen issue. I did though start from 3.2.4 and worked my way down to 3.1.0. CM boots quickly and is super responsive. When booting it flashes the all gray "kindle fire" for about 10-20 seconds before it boots into recovery or cm. Possibly you just aren't see that screen and are seeing black instead?
Thanks for the feedback!
I think I don't see the gray "Kindle Fire" for that long - so that's a possibility. Btw, I also don't see the Cyanogenmod boot logo I'm used to on mobile phones. I guess I have to investigate this further. Wondering if the fact that I started with a rather "antique" stock firmware could have something to do with it, but I would guess that this is not possible as all that old stuff is wiped away when installing TWRP & the CM rom.
Edit: The gray "Kindle Fire" logo shows up for circa 4 seconds.
nocmonkee said:
I am not experiencing this black screen issue. I did though start from 3.2.4 and worked my way down to 3.1.0. CM boots quickly and is super responsive. When booting it flashes the all gray "kindle fire" for about 20 seconds before it boots into recovery or cm. Possibly you just aren't see that screen and are seeing black instead?
Click to expand...
Click to collapse
Thanks to everyone for their hard work bringing us TWRP for the Kindle HDX models.
vortox said:
It's not working on 3.2.4, but works atleast at 3.1.0. I didn't test other versions.
Click to expand...
Click to collapse
What's the best way to downgrade a rooted/safestrapped 13.3.2.4 stock-rom to a lower version?
well
Deathcrow said:
Thanks to everyone for their hard work bringing us TWRP for the Kindle HDX models.
What's the best way to downgrade a rooted/safestrapped 13.3.2.4 stock-rom to a lower version?
Click to expand...
Click to collapse
go back to development and start reading. To have somebody here we explain everything would just be ridiculous there is a thread or several threads on rolling back..from different versions to different versions I believe in development there is even a thread started now for exactly your question. And it was started yesterday or the day before.
jimyv said:
go back to development and start reading. To have somebody here we explain everything would just be ridiculous there is a thread or several threads on rolling back..from different versions to different versions I believe in development there is even a thread started now for exactly your question. And it was started yesterday or the day before.
Click to expand...
Click to collapse
Oh yeah, I completely missed that. Thanks for pointing it out.
if i install this twrp, what would happen to my safetrap recovery and can i even access it after and use the backups i saved using safetrap on twrp?
well
latedays101 said:
if i install this twrp, what would happen to my safetrap recovery and can i even access it after and use the backups i saved using safetrap on twrp?
Click to expand...
Click to collapse
yes you will still be able to access your safestrap. And yes your safestrap backups will be compatible with your new recovery. But keep in mind that your backups from safestrap will not contain a kernel and you will have to match one up with it..
jimyv said:
yes you will still be able to access your safestrap. And yes your safestrap backups will be compatible with your new recovery. But keep in mind that your backups from safestrap will not contain a kernel and you will have to match one up with it..
Click to expand...
Click to collapse
thanks, i just installed the twrp recovery successfully, how do i boot into safetrap again if i want to use it?
lol
latedays101 said:
thanks, i just installed the twrp recovery successfully, how do i boot into safetrap again if i want to use it?
Click to expand...
Click to collapse
it probably took you longer to ask me that question then it did for you to figure it out.
if not just simply reboot it and tap recovery on the splash screen as it boots just like always if you want access to it from your system just install the APK..personally I wouldn't mess with itother than to get into the backups from my new recovery to restore data....
jimyv said:
it probably took you longer to ask me that question then it did for you to figure it out.
if not just simply reboot it and tap recovery on the splash screen as it boots just like always if you want access to it from your system just install the APK..personally I wouldn't mess with itother than to get into the backups from my new recovery to restore data....
Click to expand...
Click to collapse
yeah i tried that but seems like its just boots into twrp not safetrap and thought something weird is happening and even if i tried installing the apk and press into recovery, it just boots into the cm rom.
well
latedays101 said:
yeah i tried that but seems like its just boots into twrp not safetrap and thought something weird is happening and even if i tried installing the apk and press into recovery, it just boots into the cm rom.
Click to expand...
Click to collapse
did you open up the app and see if the recovery is installed?. Like I said I would not mess with it personally. safestrap is a version of TRWP.. but is installed in the system and may have compatibility issues with your cm 11 etc other ROM that you may install with your new true recovery.
besides if you flash cm through your new recovery nothing you can install through safestrap at this moment would be compatible with the kernel ..besides a backup of that same rom. you would have left there. Unless you flash a renamed bin file to get compatible kernel for whatever stock backup you were trying to restore from safestrap
jimyv said:
did you open up the app and see if the recovery is installed?. Like I said I would not mess with it personally. safestrap is a version of TRWP.. but is installed in the system and may have compatibility issues with your cm 11 etc other ROM that you may install with your new true recovery.
besides if you flash cm through your new recovery nothing you can install through safestrap at this moment would be compatible with the kernel ..besides a backup of that same rom. you would have left there. Unless you flash a renamed bin file to get compatible kernel for whatever stock backup you were trying to restore from safestrap
Click to expand...
Click to collapse
Hm damn i just wanted to go back into safestrap so i can delete all my rom slots that i created that are wasted space seems like i kind of screwed right now for not backing the previous safetrap recovery i guess, unless someone share a back image of safetrap that i can flash?
well .
latedays101 said:
Hm damn i just wanted to go back into safestrap so i can delete all my rom slots that i created that are wasted space seems like i kind of screwed right now for not backing the previous safetrap recovery i guess, unless someone share a back image of safetrap that i can flash?
Click to expand...
Click to collapse
you were supposed to do that somewhere in the rolling back effort just before you do your new recovery. You were supposed to do it through a stock system and stock recovery to completely wipe the device.
you can still do it in your new recovery after you back your stuff up to your PC just go into wipe options and choose the option on the right wipe complete data.but that location of that folder is someplace I'm trying to find it for you
---------- Post added at 09:31 PM ---------- Previous post was at 09:23 PM ----------
jimyv said:
you were supposed to do that somewhere in the rolling back effort just before you do your new recovery. You were supposed to do it through a stock system and stock recovery to completely wipe the device.
you can still do it in your new recovery after you back your stuff up to your PC just go into wipe options and choose the option on the right wipe complete data.but that location of that folder is someplace I'm trying to find it for you
Click to expand...
Click to collapse
Try \mnt\shell\emulated\ then delete that folder named safestrap. That is where it is on my Apollo anyway
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
MultiROM is one-of-a-kind multi-boot mod for Lg G3. 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
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. There is also an awesome article on Linux Journal.
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is not encrypted).
MultiROM has 3 parts you need to install:
MultiROM (multirom-YYYYMMDD-vXX-d851.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (TWRP_multirom_d851_YYYYMMDD.img) - download the IMG file from second post and use fastboot or Flashify app to flash it.
Patched kernel - 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.
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.
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.
Source code
kernel https://github.com/Skin1980/android_..._lge_msm8974ac
Device Tree https://github.com/Skin1980/device-ls990-multirom
TWRP https://github.com/Skin1980/Team-Win-Recovery-Project
Credits: @tassadar for the awesome work; @invisiblek and @savoca @patrik.KT for them help
@Tectas cause i used his ( awesome) source code for building the kernel
And sure... tnx to @HPTesla and the other guy ( sorry i deleted for error the messages) for testing this!
...and all the people that now i forget
reservedPLEASE READ THE MULTIROM WIKI TO UNDERSTAND BETTER WHAT YOU ARE DOING
IMPORTANT: Need to be with a Kitkat stock Rom ( if you use my kernel ) or with a rom that have a kernel with the kexec hardboot patch.
HOW TO INSTALL:
1- reboot in recovery and flash the new TWRP with Multirom support; --> HERE
2- reboot the recovery;
3- flash the kernel with the kexec hardboot patch HERE
4- flash the multirom zip; ---> HERE
5- install every Rom you want ( advanced--> multirom --> add rom )
6- reboot and choose the rom you want to boot.
You can also use a Cyanogenmod or similar with the wonderful Rin Kernel by @Tectas --> DOWNLOAD FOLDER
If you want show me your love for this you can consider a small DONATION
Issues:
1- On boot the touch need some seconds to work in multirom menu, you can use the volume keys to move and the power button to select.
You are awesome man. Flashed and installed with no issues. Currently running BarRin and a backup of Dirty Unicorns. I was kinda stressing on setting this up but it was way easier then I imagined it would be.
You will have a donation coming your way as soon as I get paid.
Thank you! Thank you! Thank you!
It's so exciting to see how far the G3 is coming along and I love it! Thank you! I will definitely be testing this in the future (just not right now) :good::good::good::good:
I remember this. Also safestrap. These are sweet. Thanks.
Sent from my LGLS990 using XDA Free mobile app
this sounds incredible....so is it possible to run barrin and a lolipop rom?
If I flash the modified twrp in the op so I can use this ROM, would I need to re flash a different twrp if I didn't want to use multirom anymore? Or is the twrp in the op good for any rom?
mrkrabs said:
this sounds incredible....so is it possible to run barrin and a lolipop rom?
Click to expand...
Click to collapse
I've been testing this since a few days ago. Once properly installed and set up, when my phone boots I have the choice of stock and 6 other roms to choose from. It's the best, really. Since BarRin is modified stock, you can use it as your primary as long as you use the included kernel from this post. Also, rin kernel which is included with BarRin will be getting a kexec-hardboot patch shortly. I'm sure engine will start using it once I build it.
---------- Post added at 07:52 AM ---------- Previous post was at 07:50 AM ----------
Will32 said:
If I flash the modified twrp in the op so I can use this ROM, would I need to re flash a different twrp if I didn't want to use multirom anymore? Or is the twrp in the op good for any rom?
Click to expand...
Click to collapse
I was able to restore my nandroid made with the original bump twrp just fine. If you do it the classic way thru twrp you will lose multirom boot bc it restored my old kernel but yes. You can restore old backups in this twrp just fine from my tests.
I cant for the life of me get my BarRin backups to restore, either as primary or secondary roms, I took two for safe measure, one to my internal and one to a USB OTG, both say when being Restored: "Unable to find file system (first period)." when it first moves to restore then finally fails completely with the same error followed by "Unknown restore method for '/rpm'
Now I have two questions:
I created this backup using the original non-multirom twrp and am trying to restore it with the multirom twrp, could this be the issue?
Is it as simple as with the N7 multirom to just flash the original twrp, restore, and restart the process?
I can confirm I can flash both CM12 and BarRin fresh to the Primary partition and both boot without error.
EDIT: Color me even more confused.. Flashed back to 2.8.40 twrp, got the same errors when restoring but phone booted just fine, Truly stumped
JaceAlvejetti said:
I cant for the life of me get my BarRin backups to restore, either as primary or secondary roms, I took two for safe measure, one to my internal and one to a USB OTG, both say when being Restored: "Unable to find file system (first period)." when it first moves to restore then finally fails completely with the same error followed by "Unknown restore method for '/rpm'
Now I have two questions:
I created this backup using the original non-multirom twrp and am trying to restore it with the multirom twrp, could this be the issue?
Is it as simple as with the N7 multirom to just flash the original twrp, restore, and restart the process?
I can confirm I can flash both CM12 and BarRin fresh to the Primary partition and both boot without error.
EDIT: Color me even more confused.. Flashed back to 2.8.40 twrp, got the same errors when restoring but phone booted just fine, Truly stumped
Click to expand...
Click to collapse
Yeah i have no idea. I made a nandroid of zv4 stock, installed everything then made another nandroid after. I never wiped anything, until I went to test nandroids. But ultimately I just kept stock as primary and multiple aosp as secondaries. I restored both nandroids thru twrp fine, but didn't try to add backups via multirom advanced option in twrp.....
Like I said I have no clue, Works currently though and thats what matters BarRin Primary and CM12 Secondary, Now to try the other lovelies!, Thanks for this!
I'm using barin now and I have a backup of it. I don't have the full barin zip downloaded. Can I restore my barin backup as my primary rom as long as I use the kernel in the op? I don't want to download barin unless I have to. Slow speeds where I'm at today.
Will32 said:
I'm using barin now and I have a backup of it. I don't have the full barin zip downloaded. Can I restore my barin backup as my primary rom as long as I use the kernel in the op? I don't want to download barin unless I have to. Slow speeds where I'm at today.
Click to expand...
Click to collapse
I believe so. Restore your backup and reflash the kernel. If that doesn't bring back up the multirom boot, go back into twrp and reflash the third zip, the multirom scripts. But hopefully you only need the kernel.
HPTesla said:
I believe so. Restore your backup and reflash the kernel. If that doesn't bring back up the multirom boot, go back into twrp and reflash the third zip, the multirom scripts. But hopefully you only need the kernel.
Click to expand...
Click to collapse
Man I appreciate the help. Hopefully this last question will clarify all of it for me.
As I said, I'm on barin now. If I flash all 3 items in the op in order, will my current rom then be known as my "primary rom"? Then I can flash secondary roms, right?
Will32 said:
Man I appreciate the help. Hopefully this last question will clarify all of it for me.
As I said, I'm on barin now. If I flash all 3 items in the op in order, will my current rom then be known as my "primary rom"? Then I can flash secondary roms, right?
Click to expand...
Click to collapse
Yeah, that's what I did. I restored my stock zv4 nandroid(since BarRin is stock based you're good) then flashed the kernel, twrp and multirom. I rebooted after each(kernel I rebooted system to make sure kernel was OK, twrp, I rebooted back into recovery to make sure twrp was updated then flashed multirom and rebooted system again). Then under advanced->multirom in twrp I added roms from flashable zips and under list roms I flashed gapps for each.
As for the help, anytime, it's what this community should be all about. Just pay it forward man.
I keep getting kernel crash and unable to load my 2nd rom...my default rom...cm12 runs fine...I installed the rin kernel for that...and I.tried using the kernel in post 2 for the 2nd rom which is barin...I tried with and without the kernel...
edit: ok...got 2 cm roms working as multi boot...but still can't get cm 12 and barrin working..kernel crash right after the lg screen when trying to load barrin as secondary rom
Sent from my LG-ls990 using XDA Free mobile app
Fantastic thanks a lot guys
Using the AOSP kernel provided in 2nd post, I'm not getting any MultiROM features in TWRP. Do I need to flash the stock-based kernel on install and then overwrite with AOSP? Thx!
otroguero said:
Using the AOSP kernel provided in 2nd post, I'm not getting any MultiROM features in TWRP. Do I need to flash the stock-based kernel on install and then overwrite with AOSP? Thx!
Click to expand...
Click to collapse
So after you tap advance, you don't have see a button for multirom? Are you using a theme in twrp?
Pump Ac7i0n said:
So after you tap advance, you don't have see a button for multirom? Are you using a theme in twrp?
Click to expand...
Click to collapse
I have a theme in my current TWRP 2.8.3 and that's what reboots. Same 2.8.3 as before. No MULTIROM options in Advanced. I've been per the OP. I guess my question is, can this be initiated from an AOSP system? All flashes and reboots are successful, but nothing changes... Thanks for the help @Pump Ac7i0n. Your builds make my g3 rock like it oughta.
VERIZON SAMSUNG GALAXY NOTE 2 (T0LTE)
PLEASE READ READ READENTIRE OP
"ALL MAJOR WORK DONE BY HASHCODE SO GO GIVE HIM SOM THANKS.DO NOT POST ANY BUG OR ISSUE COUSED BY THIS RECOVERY IN ORIGINAL THREAD BY HASHCODE, POST HERE AND I WILL HELP YOU."
CURRENT PROJECT STATUS:
BETA v4.00-B01 (ND7/KK)
WHAT IS SAFESTRAP?
Safestrap is a Bootstrap / Recovery for locked bootloader phones. The goal is to avoid touching your primary system (I'll call this "stock" system) and only flash or make large changes to another place on your phone that Safestrap treats as a "2nd system" (in this case, it's a series of virtual ROM slots located on the internal emmc area: "/sdcard"). Once installed, you will see a "Splashscreen" giving you the option to hit "menu" to enter recovery. The recovery portion of Safestrap is now based on TWRP 2.6.1.0 (a touch based recovery) and you can perform .zip installs, backups and restores here. The additional features I've added to TWRP are mostly located under the "Boot Options" menu:
Here you can create virtual ROM-slots (3-4 on the S3 due to partition size and internal space) for flashing ROMs. NOTE: The bigger you make the /data partition the less room you will have to make other ROM-slots.
You can activate a new ROM-slot by choosing the slot you wish to make active and then selecting the "Activate" button. Once active, you will see the "rom-slot#" up in the top of the screen shown in green. If you make the "stock" ROM active, then you can see it in the top shown in red.
Once a ROM-slot is active, all actions you would normally perform using TWRP are directed to that ROM-slot. For example, "Install" to flash a .zip, backup and restore.
HOW DO I INSTALL SAFESTRAP?
Requirement: Root
[NEW FOR v4.00+ KK Safestrap] Requirement: Uninstall old Safestrap application.
[NEW FOR v3.75+ KK Safestrap] Requirement: busybox. Grab "Busybox" from the Play Store and run the installer.
Once installed, open up the Safestrap application, Agree to the disclaimer that you won't try to sue me and hunt me down with a rifle if you manage to break your phone..
Then use the "Install Recovery" button. You should see the current version down in the lower left corner of the window. And the "Status:" should say "Installed" when you're done.
From there you can reboot and you *should* see a new splash screen during the boot up. While this is showing you can enter Safestrap Recovery using the [ menu ] button.
INSTALL VIDEO by DMX: https://www.youtube.com/watch?v=_RZI...e_gdata_player
HOW DO I ENTER RECOVERY?
During each reboot a splashscreen will be displayed showing whether the device is running a rom-slot or on the "Stock ROM".
Press the button shown on the screen to either enter "RECOVERY" or "CONTINUE" booting (or the hard button underneath each option).
HOW DO I UPGRADE SAFESTRAP?
Push the APK up to your sdcard.
Boot back into the "stock" rom-slot.
Open your old Safestrap app and use the "Uninstall Recovery" button
Browse to where you pushed the APK
Click on it and install like normal
Once installed, open the APK, Grant SU access, Use the "Install Recovery" button.
KNOWN ISSUES:
- Sometimes the installation doesn't work correctly. If you don't see the splashscreen after a rebooting. Install Safestrap again. (DEBUGGING THIS AS I GET TIME)
- Busybox is now required for the Safestrap APK to work correctly
DOWNLOADS:
CONFIRM THAT YOU ARE USING A VERIZON WIRELESS SAMSUNG GALAXY NOTE 2 (T0LTE) [KITKAT:ND7]
LATEST FILE: Safestrap-T0LTE-4.00-B01.apk
androidfilehost
WARNING: Safestrap is heavily modified to be "Safe" for your device. Do not download TWRP from their website and expect it to work the same way. Also TWRP does not support Safestrap, tho some issues that may come up will be TWRP dependant, please try and contact myself or look on the forums for your device for answers before hunting down TWRP people. They won't be able to help w/ Safestrap specific questions.
Special Thanks To
@Hashcode , DeesTroy & TeamWin for all their hard work making TWRP such a fantastic recovery. If you are considering a donation, then please have a look at the Team WIN website: http://teamw.in/project/twrp2
@urphonesux for testing
CHANGES:
4.00-B01
[2015-11-22] Synced with latest TWRP commits.
[2015-11-22] Remove read-only system.
[2015-08-13] Update TWRP recovery to 2.8.7.0 .
[2015-08-13] Materialize Safestrap apk.
Safestrap Recovery theme (Stock TWRP)
How to...
The theme zips are not flashable. First installation has to be done manually:
- Download the theme and rename it to "ui.zip".
- On SD card (if device has internal and external storage, use the internal) open TWRP folder and create a folder called "theme", without capital letters.
- Copy ui.zip to theme folder.
- Restart to recovery.
Safestrap Stock TWRP theme v4.00 B01.zip
1st!! Everything works fine. Multiple rom slots, backup/restore etc.
Thanks for this Mo!
on ND7 OTA. rooted via ghettoroot. Installed a previous version of safestrap: Safestrap-T0LTE-3.72-B02
it worked but didnt work with rom slots. I uninstalled the previous recovery and then uninstalled safestrap. Then installed this new one. Keeps not installing the safestrap recovery. Any ideas?
Tried doing a system wipe then installed clean 4.00 safestrap. no work..
Tried then system wipe and doing kingroot instead of ghettoroot. same result
albert001 said:
on ND7 OTA. rooted via ghettoroot. Installed a previous version of safestrap: Safestrap-T0LTE-3.72-B02
it worked but didnt work with rom slots. I uninstalled the previous recovery and then uninstalled safestrap. Then installed this new one. Keeps not installing the safestrap recovery. Any ideas?
Tried doing a system wipe then installed clean 4.00 safestrap. no work..
Tried then system wipe and doing kingroot instead of ghettoroot. same result
Click to expand...
Click to collapse
Does busybox installed! From the app too.
What's updated over the previous versions?
Upgrade from 3.72 on Verizon Note 2
I am using 3.72 and wonder if I should upgrade to the latest version. It must be completely removed and not updated as per OP instructions under content?
Thanks
adobrakic said:
What's updated over the previous versions?
Click to expand...
Click to collapse
TWRP is now 2.8.7.0 and its support kitkat..
NB2A said:
I am using 3.72 and wonder if I should upgrade to the latest version. It must be completely removed and not updated as per OP instructions under content?
Thanks
Click to expand...
Click to collapse
yes comlplete remove the old apk as mine has different package name
Hi,in this version works the option restore?
Piombo71 said:
Hi,in this version works the option restore?
Click to expand...
Click to collapse
As reprted by urphonesux its working as it should.
hello sir i try ur recovery mood Everything works fine and install new 5.01 rom in my i605 4.4.2 but samsung logo restart prob. in my phone rom and google apps successfully install in my phone then reboot but my phone not on. :crying::crying:
plzz help me..
djrajiv said:
hello sir i try ur recovery mood Everything works fine and install new 5.01 rom in my i605 4.4.2 but samsung logo restart prob. in my phone rom and google apps successfully install in my phone then reboot but my phone not on. :crying::crying:
plzz help me..
Click to expand...
Click to collapse
Hi,then if it is as in the previous version,this recovery can flash only TW Rom and not CM Rom,because black screen upon reboot.
djrajiv said:
hello sir i try ur recovery mood Everything works fine and install new 5.01 rom in my i605 4.4.2 but samsung logo restart prob. in my phone rom and google apps successfully install in my phone then reboot but my phone not on. :crying::crying:
plzz help me..
Click to expand...
Click to collapse
If you are locked bootloader then AOSP ROMs not for you.
The recovery wont flash any kernel and lack of kernel wont boot the ROM.
mohammad.afaneh said:
If you are locked bootloader then AOSP ROMs not for you.
The recovery wont flash any kernel and lack of kernel wont boot the ROM.
Click to expand...
Click to collapse
i try this 3 roms in my note 2 i605. 4.4.2nd7.
[ROM] [5.1.1_r18] [OFFICIAL] [Layers] XenonHD i605 - Note 2
[ROM] [6.0.1r10] [MULTI-WINDOW][VRToxin][i605] [01/08/2016]
[ROM][5.1/6.0][CM12.1/13][SABER][20160201] Unofficial Build - i605
rom and google apps successfully install but my phone black screen upon reboot..
djrajiv said:
i try this 3 roms in my note 2 i605. 4.4.2nd7.
[ROM] [5.1.1_r18] [OFFICIAL] [Layers] XenonHD i605 - Note 2
[ROM] [6.0.1r10] [MULTI-WINDOW][VRToxin][i605] [01/08/2016]
[ROM][5.1/6.0][CM12.1/13][SABER][20160201] Unofficial Build - i605
rom and google apps successfully install but my phone black screen upon reboot..
Click to expand...
Click to collapse
those ROMs are AOSP and you cant flash over locked bootloader device.
mohammad.afaneh said:
those ROMs are AOSP and you cant flash over locked bootloader device.
Click to expand...
Click to collapse
how to unlock my note 2 bootloader 4.4.2 ND7 Sir ???
djrajiv said:
how to unlock my note 2 bootloader 4.4.2 ND7 Sir ???
Click to expand...
Click to collapse
http://www.mobiletechvideos.com/samsung-galaxy-note-2-bootloader-sboot-downgrade-service/
The only way to unlock the bootloader at this point is to have this done. They will downgrade your Note 2 to 4.1.2 which can be unlocked. Sorry it is what it is.
i follow everything but when i install ss from the app, it doesnt give me an option to reboot recovery , im on 4.4.2
cubajean10 said:
i follow everything but when i install ss from the app, it doesnt give me an option to reboot recovery , im on 4.4.2
Click to expand...
Click to collapse
You installed Busybox?