This thread is for noobs by noobs , a place to talk about the app so that we don't clutter the ROM threads .
I hope this works out and helps anyone including myself with using this app.
Here is another GUIDE by JJsax posted on The Root Of All EVO that is a lot more detailed then this one.
The Official forum for BootManager is Init2winit if you would like to learn even more about the app.
As I learn about this app ,as to how and what works with it I'll update this and maybe it will help everyone out that is trying to use BootManager.
This app also works with EVO 3D's with hboot 1.50 s-on
Thank XDA member mnomaanw for that information.
If you use this app and have the time to reply to this post , please share what ROMs you've got to work and a little info on how you installed it. This way I can add it to the op to make it easier and faster for everyone to find.
This is what I've learned so far.
How to install* ROMs via Boot Manager...
Thank seraph863 for filling me in and writing this up. I just changed a few details cause his was for a specific ROM.
MAKE SURE THE ROM IS ON THE ROOT OF YOUR SD CARD NOT IN ANY FOLDERS
1.)* PURCHASE Boot Manager. It does a License check upon boot, so your jacked version will just give you a headache. Seriously, I tried it. Doesn't work.
Here is a Market link to Boot Manager if you didn't already purchase it.
1.a) IF you didn't purchase it... WIPE ALL Boot Manager data and files, including the folder on your SD Card. Then buy it and let it setup again.
2.) Open SuperUser. Hit Menu -> Settings -> Disable Logging.
3. Open BootManager. If you're at work and on Wi-Fi, you may not pass the License check due to firewall issues. If you get a black screen, or license failures, switch to 3/4G and try again.
4.) If all is good, you're asked to Setup the Phone. Do so now. [ You will need to set up your Phone ROM any time you flash a new ROM or kernel to your phone ROM.]
5.) Once installed, hit Menu -> Settings -> Force Large Boot.img
6.) Swipe right to Slot 1. Hit Install .zip and browse to your downloaded ROM.zip file. Make sure to check the Wipe System, Data, and Cache boxes so that it will wipe before it flashes the ROM. Select EXT4 as the file structure.
[This is the important part. This build will take a LONG time. Do NOT use your phone while it is running.]
8.) Once the install has been successful if you need to flash a kernel , theme gapps etc..., go back to Slot 1 and select Install .zip (again). Choose the .zip file. Do NOT wipe system, data or cache. It will ask you to over write it just hit OK.
9.) You should now be ready to boot to your new ROM! Celebrate!
Since this is for the EVO 3D I recommend to always use ext4 as your file structure.
If you get any error messages start over.
Known working ROMs to my knowledge.
These are ROMs that I've set up.
Infected Eternity Phone ROM and sd ROM
KMyers CM7 beta 7.4* with gapps ext4 sd ROM
MeanROM ext4 sd ROM
TrevE Zone v2.3.12 ext4 phone and sd ROM
Mikrunny ext4 phone ROM and sd ROM
XDA members setups
JJsax setup
CDMA Evo3D
hboot 1.50 s-on
TWRP 2.0 touch recovery
Phone ROM SteeleROM 2.73
ROM1 CM9 (The latest version couple days old)
ROM2 Evervolve ICS
mnomaanw's set up
PhoneROM: ViperROM Redline v2.5 RC2
ROM1:CyanogenMOD9
ROM2:MIUI v2.1.6
I've found it to work better to flash and set up my ROM on the phone ROM and then back it up and restore it to a slot.
If your having problems restoring backups and your using TWRP recovery try using CWM. I was having issues with TWRP and since I went back to CWM (touch and 5.0.2.0 both work great but there is no usb mount on the touch version) and I haven't had a single issue restoring a backup to a ROM slot.
My setup will be changing all the time.
CDMA EVO 3D
Eng Hboot s-off
Radio 1.06.00.1216
Phone ROM Infected Eternity Sense 3.0
ROM1 Mikrunny
ROM2 EVOZone
ROM3 SteelROM
ROM4 MeanROM Aria51
Thank you for putting this here. I know I'm to blame for going off topic in some threads about Boot Manager.
I too am having issues getting a ROM to load into slot 1.
Here's my setup...
SteeleROM 2.73
Anthrax #2 kernel
Over 5GB of storage space available.
HBOOT 1.50
TWRP 2.0 recovery (the newest touch one)
I load steele just fine as the phone ROM then try to load CM9, or whatever other ROM into slot 1 it goes through everything then it get's killed at mounting img's. I have it setup for screen on, to load large files, and I even have SU logging turned off. This happens everytime I try to load a ROM into slot 1 it just kills it and never finishes 100%
JJsax said:
Thank you for putting this here. I know I'm to blame for going off topic in some threads about Boot Manager.
I too am having issues getting a ROM to load into slot 1.
Here's my setup...
SteeleROM 2.73
Anthrax #2 kernel
Over 5GB of storage space available.
HBOOT 1.50
TWRP 2.0 recovery (the newest touch one)
I load steele just fine as the phone ROM then try to load CM9, or whatever other ROM into slot 1 it goes through everything then it get's killed at mounting img's. I have it setup for screen on, to load large files, and I even have SU logging turned off. This happens everytime I try to load a ROM into slot 1 it just kills it and never finishes 100%
Click to expand...
Click to collapse
Mine say they install fine and they finish but when I hit boot to the slot it just gets stuck on the splash screen.
I had TrevE Zone on my phone ROM but just switched to eternity. I got MeanROM to install in slot 2 and it booted up fine and is running great but thats the only one I out of the 3 I tried. I set the boot.img to large or what ever the setting is cause thats what they said to do in the video on the site for the app. My real issue though is that restoring my backup to a slot it installs to my system memory. I would like to be able to install backups cause I've read they run better. Hopefully some that knows more about this will come in here and school us a little, I'll even add it to the op and make this a guide if we get enough info.
Here's my quick and dirty instructable I posted in the CM9 thread.
How to install this via Boot Manager...
1.) PURCHASE Boot Manager. It does a License check upon boot, so your cracked version will just give you a headache. Seriously, I tried it. Doesn't work.
1.a) IF you didn't purchase it... delete ALL Boot Manager files, including the folder on your SD Card. Then buy it and let it setup again.
2.) Open SuperUser. Hit Menu -> Settings -> Disable Logging
3. Open BM. If you're at work and on Wi-Fi, you may not pass the License check due to firewall issues. If you get a black screen, or license failures, uninstall BM and delete the folder. Switch to 3/4G and try again.
4.) If all is good, you're asked to Setup the Phone. Do so now.
5.) Once installed, hit Menu -> Settings -> Force Large Boot.img
6.) Swipe right to Slot 1. Hit Install .zip and browse to your downloaded CM9 .zip file. Wipe System, Data, and Cache. Select EXT4 as the file structure
7.) This is the important part. This build will take a LONG time. Do NOT use your phone while it is running.
8.) Once the install has been successful, go back to Slot 1 and select Install .zip (again). Choose the Google Apps .zip file. Do NOT wipe system, data or cache.
9.) You should now be ready to boot to your new ROM! Celebrate!
Warning: Several users report to NOT use any Backup app such as Titanium to restore your apps and data, since the apps on this ROM are very very different. Your mileage may vary.
FYI I'm doing this by memory, so the minor steps might not be accurate (i.e. disable Superuser logging).
If you get any error messages, start over. I assure you, this process worked for me step by step.
Go to their official forum
Applications-->boot manager
You will find my thread named [REF]working and not working rom list
There are many phones
And if you test a rom that is not listed please report if it is working or not
Thanks
Sent from my HTC Desire S using XDA Premium App
I saw your guide in the cm9 thread and tried it with no luck I did exactly what you said and everything seemed to go fine but when I hit boot to ROM on slot one where I installed the ROM I'm stuck on the splash screen. Any ideas why? Thanks for the help also.
kylon said:
Go to their official forum
Applications-->boot manager
You will find my thread named [REF]working and not working rom list
There are many phones
And if you test a rom that is not listed please report if it is working or not
Thanks
Sent from my HTC Desire S using XDA Premium App
Click to expand...
Click to collapse
I was on there I even posted my issue and my log but haven't gotten any help. I did see your list of ROMs but didn't know if its up to date.
I'll have another look at it cause I really want to get this to work and its driving me crazy cause I can usually figure problems out on my own or by searching but I just can't get this.
Thanks for the replies.
linsalata28 said:
I saw your guide in the cm9 thread and tried it with no luck I did exactly what you said and everything seemed to go fine but when I hit boot to ROM on slot one where I installed the ROM I'm stuck on the splash screen. Any ideas why? Thanks for the help also.
Click to expand...
Click to collapse
Which ROM are you using?
I would start over. Use a file manager to delete your ROM from the SD Card and take another image. Make sure you have plenty of storage on your SD card. You could also try clearing the Cache and Dalvik.
You can always get back to your phone ROM manually by booting to Recovery and flashing sdcard\bootmanager\phonerom\update.zip
Edit: Don't forget to check "Use Large boot.img" within Boot Manager
seraph863 said:
Which ROM are you using?
I would start over. Use a file manager to delete your ROM from the SD Card and take another image. Make sure you have plenty of storage on your SD card. You could also try clearing the Cache and Dalvik.
You can always get back to your phone ROM manually by booting to Recovery and flashing sdcard\bootmanager\phonerom\update.zip
Edit: Don't forget to check "Use Large boot.img" within Boot Manager
Click to expand...
Click to collapse
Should I just delete the whole bootmanager folder and clear the data for the app also?
another thing is why when I restore a backup to a slot its installing to my internal memory?
Yeah I just had another look at your list and there aren't many ROMs for this phone on there and they look old.
Thanks again for the help.
It up to date
Anyway gflame is busy
What do you do to install the rom
And wich rom?
Sent from my HTC Desire S using XDA Premium App
I wiped everything out and starting over. I'm going to just try and install viperom in one slot and see if that boots, then I'm going to try and restore a backup to another slot from within a ROM slot to see if that will fix my internal memory issue cause it wont have anywhere to install to . I'll post back with what happens.
kylon said:
It up to date
Anyway gflame is busy
What do you do to install the rom
And wich rom?
Sent from my HTC Desire S using XDA Premium App
Click to expand...
Click to collapse
I disabled logging in su checked off larg boot.img then whet to slot one hit install zip choose cm9 ext4 then checked all the wipe opinions, when that finished I flashed the gapps the same way but without wiping . Everything finished with that I didn't get any errors but when I went to boot to that slot it just hung at the splash screen.
I did that 2 times with cm9 , 1 time with the Eternity ROM sense 3.0 r130 , 1 time with Team Nocturnal's Blackened ROM and they all got stuck at the splash screen.
I did get MeanROM to work using those same steps last night.
Now with the restore of my backup I did basically the same thing but it doesn't give any wipe options when you install it but it would get an error saying boot.img something like that and then I would get a low memory popup saying I only had about 30mb left internal memory when I had over 800mb when I started.
Edit: I have about 6gb free on a 16gb class 10 sd card. I believe its a Samsung card I think.
Edit2: I finished flashing viperom and now that to is stuck on the splash screen. Is there a way to wipe caches for that slot and fix permissions like you would for a regular ROM in recovery if something like this happened.
I'm really starting to think I wasted $3 this is very frustrating sorry.
Thanks for your replies and trying to help.
I went into recovery to go to flash the update zip to restore my phone ROM but when I open the bootmanager folder I don't see anything in it. I'm using twrp 2.0 recovery. Could this have something to do with my problems?
linsalata28 said:
I went into recovery to go to flash the update zip to restore my phone ROM but when I open the bootmanager folder I don't see anything in it. I'm using twrp 2.0 recovery. Could this have something to do with my problems?
Click to expand...
Click to collapse
The steps in your previous post were all correct, except you said you turned OFF "Use large boot.img" ? Make sure that option is ENABLED (has an X on it)
I'm confused as to why the app is trying to install to your internal memory... Mine installs to my SD Card. Make sure the USB cable is not plugged into the phone, and try increasing your screen timeout so it doesn't sleep during the install.
The fact that you're getting the splash screen means you're getting somewhere. Maybe you're being too impatient on the install? Wait a few minutes even after it says Install Complete before continuing.
seraph863 said:
The steps in your previous post were all correct, except you said you turned OFF "Use large boot.img" ? Make sure that option is ENABLED (has an X on it)
I'm confused as to why the app is trying to install to your internal memory... Mine installs to my SD Card. Make sure the USB cable is not plugged into the phone, and try increasing your screen timeout so it doesn't sleep during the install.
The fact that you're getting the splash screen means you're getting somewhere. Maybe you're being too impatient on the install? Wait a few minutes even after it says Install Complete before continuing.
Click to expand...
Click to collapse
I said I checked the larger boot.img off meaning it was enabled sorry for that misunderstanding. I flashed 2 of the slots last night and didn't even test them till today so I don't think that its cause I'm not waiting long enough. Why would none of the folders inside of the bootmanager folder show up in twrp recovery? Could I copy and paste the phone update.zip to the root of my sd card so that I can recover without having to nand restore cause I've already wiped and restored about 10 times trying to get this to work.
Sent from my Eternity 3D using tapatalk
linsalata28 said:
I disabled logging in su checked off larg boot.img then whet to slot one hit install zip choose cm9 ext4 then checked all the wipe opinions, when that finished I flashed the gapps the same way but without wiping . Everything finished with that I didn't get any errors but when I went to boot to that slot it just hung at the splash screen.
I did that 2 times with cm9 , 1 time with the Eternity ROM sense 3.0 r130 , 1 time with Team Nocturnal's Blackened ROM and they all got stuck at the splash screen.
I did get MeanROM to work using those same steps last night.
Now with the restore of my backup I did basically the same thing but it doesn't give any wipe options when you install it but it would get an error saying boot.img something like that and then I would get a low memory popup saying I only had about 30mb left internal memory when I had over 800mb when I started.
Edit: I have about 6gb free on a 16gb class 10 sd card. I believe its a Samsung card I think.
Edit2: I finished flashing viperom and now that to is stuck on the splash screen. Is there a way to wipe caches for that slot and fix permissions like you would for a regular ROM in recovery if something like this happened.
I'm really starting to think I wasted $3 this is very frustrating sorry.
Thanks for your replies and trying to help.
Click to expand...
Click to collapse
My phone:
Phone ROM: SteelROM 2.72
Slot 1: AOSP ICS - wifi doesn't work
Slot 2: CM9 - (google talk and books FC)
Slot 3: MIUI
Slot 4: CM7 (kmeyers)
Boot Manager has a problem trying to restore from a NAND backup, it did the same thing to me where it was installing to the phone's internal memory. I was trying to figure out the problem, but I moved on without success.
I've had the best time installing tricking ROM's by this method. I installed CM7 to a slot, booted into CM7 and installed the ICS and CM9 from there. It's been pretty successful.
If you are getting it to freeze with mounting images, I came across this issue because my SD card did not have enough room. You can try to free up some more space to see if this is the same issue.
I had most problems installing due to not enough space on my SD card, I now have a 32gb card, and have had no issues
Also, I've never had to set it to large boot.img to get things to work, and make sure you disable logging in SU, and use EXT4
---------- Post added at 02:08 PM ---------- Previous post was at 02:04 PM ----------
linsalata28 said:
I said I checked the larger boot.img off meaning it was enabled sorry for that misunderstanding. I flashed 2 of the slots last night and didn't even test them till today so I don't think that its cause I'm not waiting long enough. Why would none of the folders inside of the bootmanager folder show up in twrp recovery? Could I copy and paste the phone update.zip to the root of my sd card so that I can recover without having to nand restore cause I've already wiped and restored about 10 times trying to get this to work.
Sent from my Eternity 3D using tapatalk
Click to expand...
Click to collapse
To quickly get back to your phone ROM (make sure you setup your phoneRom in boot manager first to create the update.zip file, you need to recreate this anytime you change the ROM or Kernel for your phoneROM)
Boot into Recovery
Install the update.zip inside the \boot manager\phonerom\update.zip (not sure if location is accurate, but you get the idea)
Reboot system
Phone should boot to phone ROM, or you can install any other update.zip from your slots, to boot to them etc
spookytay said:
My phone:
Phone ROM: SteelROM 2.72
Slot 1: AOSP ICS - wifi doesn't work
Slot 2: CM9 - (google talk and books FC)
Slot 3: MIUI
Slot 4: CM7 (kmeyers)
Boot Manager has a problem trying to restore from a NAND backup, it did the same thing to me where it was installing to the phone's internal memory. I was trying to figure out the problem, but I moved on without success.
I've had the best time installing tricking ROM's by this method. I installed CM7 to a slot, booted into CM7 and installed the ICS and CM9 from there. It's been pretty successful.
If you are getting it to freeze with mounting images, I came across this issue because my SD card did not have enough room. You can try to free up some more space to see if this is the same issue.
I had most problems installing due to not enough space on my SD card, I now have a 32gb card, and have had no issues
Also, I've never had to set it to large boot.img to get things to work, and make sure you disable logging in SU, and use EXT4
---------- Post added at 02:08 PM ---------- Previous post was at 02:04 PM ----------
To quickly get back to your phone ROM (make sure you setup your phoneRom in boot manager first to create the update.zip file, you need to recreate this anytime you change the ROM or Kernel for your phoneROM)
Boot into Recovery
Install the update.zip inside the \boot manager\phonerom\update.zip (not sure if location is accurate, but you get the idea)
Reboot system
Phone should boot to phone ROM, or you can install any other update.zip from your slots, to boot to them etc
Click to expand...
Click to collapse
What cm7 ROM would you recommend ? For some reason I couldn't see files inside of the BootManager folder but I checked and they are there. I have about 5gb free on a 16gb card ,I was looking into getting a 32gb if I get this app working.
Sent from my Eternity 3D using tapatalk
try
http://forum.xda-developers.com/showthread.php?t=1393613
I upgraded my card, I had about 3-4 gb free and was having problems, but once I upgraded I haven't had many since
I've purchased boot manager and when i run it, it says "application not licenced" Any fix?
spookytay said:
try
http://forum.xda-developers.com/showthread.php?t=1393613
I upgraded my card, I had about 3-4 gb free and was having problems, but once I upgraded I haven't had many since
Click to expand...
Click to collapse
cm7 worked thanks.
Sorry but I need some help. When upgrading roms a few times, no problems ever occurred. CWM always worked smoothly. Now, I have the Resurrection Remix 1.0 Pro installed and was attempting to upgrade to Resurrection Remix 1.2 AOKP. I see that when running CWM I only had to choice to access the "download" folder on the scard. When attempting to install the Remix 1.2 rom, I always end up with an e signature fail. I tried several times but had the same results. I had to reboot and stay with Remix 1.0 until someone can help me get the upgraded rom installed. I wiped all the data and reset, and don't know what else to do.
Please help!!
OK, not sure the procedure you made... but might also be that some files you got were corrupted. Check to see they all are fine before going ahead with this way to install:
Do a full wipe(factory reset+cache+dalvik cache)
Install the Main ROM
Install Siyah-v3.0.1-CWM.zip
Reboot
Do the initial setup of things
Go back to CWM and install navigation button fix
Reboot
Then go back to CWM and install app themes (there are some bugs, but if you want the black themes, then install classic first, then black)
Reboot
Some people have other issues after, but see how this goes.
I would change the DPI settings to 184 or 210 for everything to work fine from market apps.
*if have more problems, just reply here.
Is the file on an external SD?
It's wherever you put it, though some files will only flash properly from external SD.
I think it's the internal sd
felixg123 said:
Is the file on an external SD?
Click to expand...
Click to collapse
At first I thought I had the files on the external sd card, but when rebooting in recovery with CWM it looked like it was only allowing me to access the download folder on the internal sd card.
Thanks for any suggestions.
cyberboob said:
It's wherever you put it, though some files will only flash properly from external SD.
Click to expand...
Click to collapse
The CWM that came with the remix 1.0 pro rom is that weird one that seems to have to boot from the other little app. Do you recall this is the CWM zip file that was added to the files to download for the remix 1.0 pro rom. It doesn't appear to have the same flexibility that the CWM had that came with my previously used rom...remix 9.4
Any comments??
With 1.0 its 3e (stock recovery) so you have to put cwm.zip in your external SD or your cache then flash it through 3e. Now you have cwm. If its the one from westcrip its touch so don't use the volume buttons.. actually touch the screen.
Hopefully that helps.
Sent from my GT-I9100 using XDA
Does the same thing... but it's a touch version.
There is a newer 1.3 version out now for Resurrection Remix with far simpler installing procedure... and people have reported most bugs fixed now (maybe a couple remain to be found).
cyberboob said:
Does the same thing... but it's a touch version.
There is a newer 1.3 version out now for Resurrection Remix with far simpler installing procedure... and people have reported most bugs fixed now (maybe a couple remain to be found).
Click to expand...
Click to collapse
Now, I'm really scratching my head. When I try installing the 1.3 rom it begins ....but returns this message and then aborts.
E: failed to verify whole-life signature
E: signature verification failed
I re downloaded the rom 1.3 to make sure it wasn't corrupt, and it did the same thing. Then I downloaded remix 1.2 just to see if this would install properly. I got the same result with the failed signature coming up in red and then it aborts. So something is not allowing me to change roms?? At present I have remix 1.0 installed.
Please I need some assistance figuring this out. I don't know what to do now?
Thanks in advance
Check if your current rom is having any beta releases of siyah 3.0, if so then it would be the cause, download cf root, or any latest version of custom kernel in tar format and flash it via Odin, now enter cwm and flash the new rom, you would be good to go
#*posted on the move *#
Works fine ....but is there a GPS problem?
I got the darn thing installed. Thanks. I was able to install the CWM......one that worked properly and the remix 1.3 got installed without a hitch. One problem I'm noticing the the GPS taking a whole bunch of time trying to locate sats. Is there is gps fix ??
Thanks
go to the Emergency FAQ for 1.3 (in my sig)
Hello!
I am currently using The Collective's Seraphim Mesosphere Kang build from the thread in Development from a few weeks ago. The current build is called "Remix", I've downloaded it and installed it via CWM recovery just like I did for my old version, wiped all data and caches, but when I go to install the .zip from sdcard, it fails when opening and aborts installation.
I've tried this twice, once downloading the zip over WiFi and once over 3g in case the zip got corrupted and neither works. The moment it tries to open, it fails.
What am I missing here? Is there and issue with the ROM/zip? Should I try transferring the zip via cable instead of downloading it wirelessly?
Thanks!
Astriaal said:
Hello!
I am currently using The Collective's Seraphim Mesosphere Kang build from the thread in Development from a few weeks ago. The current build is called "Remix", I've downloaded it and installed it via CWM recovery just like I did for my old version, wiped all data and caches, but when I go to install the .zip from sdcard, it fails when opening and aborts installation.
I've tried this twice, once downloading the zip over WiFi and once over 3g in case the zip got corrupted and neither works. The moment it tries to open, it fails.
What am I missing here? Is there and issue with the ROM/zip? Should I try transferring the zip via cable instead of downloading it wirelessly?
Thanks!
Click to expand...
Click to collapse
That's what I would try...sound's like a corrupt file...I have flashed over and over and no problem...if you have the file on your PC...just for a test...unzip it to a folder with 7zip or whatever you use...usually this will tell you if a file or a folder in the zip is corrupt...if it test good, try using your cable to transfer...good luck!
Sent from my Note running Seraphim Remix Green Edition
Astriaal said:
Hello!
I am currently using The Collective's Seraphim Mesosphere Kang build from the thread in Development from a few weeks ago. The current build is called "Remix", I've downloaded it and installed it via CWM recovery just like I did for my old version, wiped all data and caches, but when I go to install the .zip from sdcard, it fails when opening and aborts installation.
I've tried this twice, once downloading the zip over WiFi and once over 3g in case the zip got corrupted and neither works. The moment it tries to open, it fails.
What am I missing here? Is there and issue with the ROM/zip? Should I try transferring the zip via cable instead of downloading it wirelessly?
Thanks!
Click to expand...
Click to collapse
as mentioned, sounds like possibly a corrupt file
i would download on wifi, then transfer by cable
actually, i would do the md5 hash check to make sure the file is unaltered before transferring
Looks like you guys were right! I downloaded it onto my computer first, then transferred via cable, and it installed totally fine.
The weird thing is that I downloaded the Remix .zip from the same wireless AP, for both the computer and directly onto the phone. Yet only the one on the computer actually worked.
I'm not sure if it was just unlucky and downloaded directly to the phone caused dropped packets/corrupted the data and the computer simply has a better connection or what.
In any case - glad I'm all sorted and up to do now!
Thanks!
*hello, could any one help me. im noob here
*i fail to install Resurrection Remix ics v2.5.3[4.0.4]
*im using CMW to install it but...this is the result "installations abort"
*i has flash several rom before all is success
*just now im using
SGS2
kernel = siyah-v3.3.2+
ROM = XWLPG.salmanRom_v4
*sorry for my bad english...ty for anyone are helping..,
may be a corrupt download
and from which rom ur coming from ??
Sent from my GT-I9300 using xda premium
When you have the Rom on internal_sd, then put it on your external_sd and when you have it on the external_sd, then try to put it in your internal_sd.
MFG Chabou
I was having the same problem, when I downloaded the .zip there was a space in the file's name. Remove that and you should be good.
I'm also having a problem, when I install the ROM I have a bunch of problems. I get messages saying com.process.gapps has stopped, Android Keyboard has stopped. On top of that when I choose System Settings it says the apk is not installed and the phone dialer and status bar are both missing.
I followed the extended instructions exactly as I came from Litening ROM and that didn't work. Tried re-downloading/re-flashing RR but still no joy. Any help?
I've been having an issue where it installs fine as first or second ROM (siyah) but won't boot. Doesn't even get to boot animation; just freezes either right after opting to boot into it as first or second ROM, or allowing it to boot straight from an of state.
Tried full wiping including manually formatting system partition, redownloading the ROM, using a different kernel and even changing the installation type from custom to full.
No luck.
Any suggestions?
Edit: Working now. Copied the ROM from my external memory to the internal; installed RR (secondary ROM) n then fixed permissions and wiped dalvik
Sent from my GT-I9100
***Solved***
****Corrupt download*****
Sent from my GT-I9100 using Tapatalk
Im trying to flash to the slick2vfinal rom and i keep getting "updating partition details" then it fails immediately...
im clearing everything I can think of without clearing my SD card
I originally had the rom in the wrong format for the phone to read so I change it to .zip file and now I can at least see the rom, but I still get "failed" when updating the partition details?
update: i tried to change the way I select the rom in the bootloader and TWRP , i got rid of the slick2vfinal folder and added just the .zip file and now its not even opening
am I supposed to "wipe system, this will wipe your rom"
any ideas?
Turn out I had a bad install. Downloaded a different Rom and it worked spot on,however I didn't like it so I flashed back to my nandroid backup
Sent from my LG-E970 using xda app-developers app