I've been trying to get boot manager up and running,but for some reason when I go to setup phone rom it keeps looping boot manager has been given superuser permissions. I've tried deleting the folder from the SD card, uninstalling the program,resetting the permissions in su, but no luck. Can someone help me out
If I remember correctly only a few ROMs will boot on BM. You could talk directly to them here
Its not a rom program, but the actual app itself
Have 4 ROMs running on BM here. Havent got ICS a5 running yet or it would be 5. May be of some help but direct link to their forums that fenixjn posted might be a better place as the devs GFlam and Conap check their forums numerous times a day and are fantastic.
Which ROM are you trying to boot? I have four running but have had some issues with some of the newer ones.
I think that you need to talk directly to the Devs.
And as stated, some Roms do not let boot manager open.
Sent from my PC36100 using Tapatalk
I got ics alpha to run in a slot with BM, but once in ics I couldn't use BM.
I'm not even at the step of getting a rom ready to setup,I press the setup phone rom button and it starts a continuous loop of granting superuser permissions,and it doesn't stop until I either restart the phone or force close it
I bought it and never got it to work. I am happy to support devs and it is an awesome Idea but, I couldnt find a single rom that would boot from it. MIUI, OMGB, CM none worked
I got the problem fixed,it was something wrong with my backup,a clean install fixed it
Swyzzlestickz said:
I bought it and never got it to work. I am happy to support devs and it is an awesome Idea but, I couldnt find a single rom that would boot from it. MIUI, OMGB, CM none worked
Click to expand...
Click to collapse
I had the same problem before,make sure the rom your using has the same kernel as the phone rom, or download a kernel for sense
Sent from my PC36100 using xda premium
xcpefrmreality said:
I got ics alpha to run in a slot with BM, but once in ics I couldn't use BM.
Click to expand...
Click to collapse
Once you are in the ICS, then let it settle, then reboot it. Check to make sure you have an internet connection of anykind so it can check permissions, then try to reload it. Also, NEVER delete the Bootmanager directory while in a Slot ROM. Can you say problem? It is, that is the only way you can get back to the stock Boot.img.
---------- Post added at 09:46 PM ---------- Previous post was at 09:36 PM ----------
Swyzzlestickz said:
I bought it and never got it to work. I am happy to support devs and it is an awesome Idea but, I couldnt find a single rom that would boot from it. MIUI, OMGB, CM none worked
Click to expand...
Click to collapse
I also had the same problem, after I had it installed and running flawlessly.
A solution is to do a clean wipe of your phone, and reflash the ROM you want as your primary. SD cards can corrupt data just like anything else, so sometimes a file gets screwed. So I wiped, reflashed primary, then restored the apps, then set up boot manager, and installed 4 ROMs without any problems.
Related
So my roms i download will install and boot up but once i get to that specific roms boot screen it just does an infinite loop. i then take the battery out, boot it into recovery and go back to my back up. I am not sure why it is doing this and would just love to be able to use cm7 (which did the infinite boot as well). its rooted using unrevoked and i have used a few other roms on it as well this has just been what has been happening lately. any help would be much appreciated!!
Had the same prob with cm7 #22, but 23 is working just fine, try that one. Remember the Dec said some may be broken, just fish around, but be very careful.
Sent from my ADR6300 using XDA App
Sorry, meant to say the "dev" said some cm7 nightlys are experimental and may be broken. Flash to the last rom that functioned for you, then use rom manager to download the latest cm7 nightly. Which is what I'm using now and am very satisfied with.
Sent from my ADR6300 using XDA App
30 is running great for me
6stringandy said:
Sorry, meant to say the "dev" said some cm7 nightlys are experimental and may be broken. Flash to the last rom that functioned for you, then use rom manager to download the latest cm7 nightly. Which is what I'm using now and am very satisfied with.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
see i tried the latest one and a few others. im not sure what it could be, that makes them go to the infinite boot screen. Should i try factory reset, root it again, restore my old version, then try to boot more roms?
crazyturtle777 said:
see i tried the latest one and a few others. im not sure what it could be, that makes them go to the infinite boot screen. Should i try factory reset, root it again, restore my old version, then try to boot more roms?
Click to expand...
Click to collapse
Flash CM7 in recovery. Then BEFORE you reboot, install a different kernel
This is your best choice for CM7 - http://forum.xda-developers.com/showthread.php?t=905873
Then reboot your Inc and see if it boots up, I have heard of a couple people who couldn't get their Inc to boot up with the stock CM& kernel, no clue why though.
hahaha so i got it to work. it was rom manager not letting me go through with it all. just did it manually through recovery. but i got sm7 to install and no notification bar. hence why im laughing. just gonn install miui and give her a shot.
I've been trying to get boot manager to work and so far no luck. Eerytime I install a rom it gets stuck at the ssplash screen. Sometimes it will freeze myy phone up when it's installing. The roms I been trying to install in the additional slots are Miui and pool party. It does ask something before install about either installing ext2 or ext4. Can someone explain what that is and how I can find out what my current rom ext is? I'm running SkyRaider1.1
Does it not say in the roms description? It usually does, a lot of the new roms are going to ext4, its basically just a different format for your SD card, ext4 is supposedly faster, I would try visiting skyraiders website to see, o, and I read that if the other roms you were trying to install to boot with this are ext4 roms, they will not work, this was only like 2 days ago I read that so unless they have fixed it since then that may be your problem also...
Sent from my ADR6350 using XDA App
bluedegeon said:
I've been trying to get boot manager to work and so far no luck. Eerytime I install a rom it gets stuck at the ssplash screen. Sometimes it will freeze myy phone up when it's installing. The roms I been trying to install in the additional slots are Miui and pool party. It does ask something before install about either installing ext2 or ext4. Can someone explain what that is and how I can find out what my current rom ext is? I'm running SkyRaider1.1
Click to expand...
Click to collapse
it doesnt matter the rom runs off the sdcard. the .img files it creates are each partition for the rom, it asks you what filesystem you want to use for those img files.
Sent from my Incredible 2 using XDA App
No I looked like 10x. Does not say what file extension it is on SkyRaider website. I talked to a dev. and he said the app isn't connecting to the servers and if I tried connecting using data not wifi which I have been and no luck. I'm just going to get a refund
I would listen to guy above me, he's pretty knowledge, but like I said, regardless of that issue, I red under comments on market, if the roms you are trying to use run ext4 they won't work for some reason, I don't know why, just what a lot of people said, it kept me from buying it cause I wanted to try it.
Sent from my ADR6350 using XDA App
I love my boot manager. I always install as ext2 and don't have problem. I'm running CM7 beta as my main phone rom, with Magnolia, MIUI, Carbonite and GingerBangVanilla in the other slots. So much win.
Anyway you can always copy past the bootmanagers log.txt into an email and send it to [email protected] and they'll be more than happy to help.
chattguy said:
I love my boot manager. I always install as ext2 and don't have problem. I'm running CM7 beta as my main phone rom, with Magnolia, MIUI, Carbonite and GingerBangVanilla in the other slots. So much win.
Anyway you can always copy past the bootmanagers log.txt into an email and send it to [email protected] and they'll be more than happy to help.
Click to expand...
Click to collapse
Yeah I've already done that. They told me my app was connecting to servers to install necessary files in order for it to work properly. They told me to open the app using data while wifi disconnected which I always do anyways. I don't use wifi unless im downloading huge files. I told them i tried it and nothing seem to work, Haven't heard from them ever since. If i install as ext 2 it will install but when i want to select rom 1 it will get stuck at splash screen. If i install ext 4, it freezes my phone
bluedegeon said:
Yeah I've already done that. They told me my app was connecting to servers to install necessary files in order for it to work properly. They told me to open the app using data while wifi disconnected which I always do anyways. I don't use wifi unless im downloading huge files. I told them i tried it and nothing seem to work, Haven't heard from them ever since. If i install as ext 2 it will install but when i want to select rom 1 it will get stuck at splash screen. If i install ext 4, it freezes my phone
Click to expand...
Click to collapse
flash skyraider, open terminal emulator or use adb shell, type mount, look for ext4 in the output.
Sent from my Incredible 2 using XDA App
times_infinity said:
flash skyraider, open terminal emulator or use adb shell, type mount, look for ext4 in the output.
Sent from my Incredible 2 using XDA App
Click to expand...
Click to collapse
Didn't find ext4. I see ext3 in some parts though. Weird.. If my rom is ext3 and it only gives me the option to install as ext 2 or 4. Look at my screen shot in OP to see what ik talking about.
I've been playing with boot manager and have found it a bit buggy as well. I was able to install Miui and stock GingerSense, but both Pool Party and OMFGB boot loop.
I'm not complaining though, I'm amazed it works at all considering what it's doing. I'll happily wait for it to be further refined, and I'm happy to support an app like this.
I think I may have found the problem. Correct me if i'm wrong. I'm running skyraider and the file system is ext3. I need ext4 installed on the main rom for boot manager to work? I tried converting it to ext4 but wouldn't boot so i converted it back to ext3 via EXT4 recovery
Initially CWM was installed fine via Rom Manager but now I can't do *anything* in rom manager. None of the options work, not even the override setting (I have CWM installed already) This wouldn't be a huge issue but I wanted to download some roms away from the computer and experiment a bit.. I was wondering why this would be occouring as it doesnt seem like normal behavior.
I click flash CWM and it gives me the little loading symbol for a few seconds..
I do the same for Override.. same thing happens
None of the other features will work because it doesn't detect CWM
>.< help!
Silentplanet said:
Initially CWM was installed fine via Rom Manager but now I can't do *anything* in rom manager. None of the options work, not even the override setting (I have CWM installed already) This wouldn't be a huge issue but I wanted to download some roms away from the computer and experiment a bit.. I was wondering why this would be occouring as it doesnt seem like normal behavior.
I click flash CWM and it gives me the little loading symbol for a few seconds..
I do the same for Override.. same thing happens
None of the other features will work because it doesn't detect CWM
>.< help!
Click to expand...
Click to collapse
I would suggest reflashing CMW through Rom Manager. Make sure you select the right version for your device GSM or CDMA as this will cause huge issues!!!
I can't flash it.. it just gives me the loading circle for a second and does absolutely nothing at all. CWM works fine outside of rom manager.. rom manager isn't working correctly. I am a little worried that this a symptom of a larger problem though.
do u have root permissions?
do u give rom manager root permission when supersuser ask u?
did u treid uninstall and install again rom manager?
Don't want to sound like an ass, but you did both unlock and root your phone, right? When you enter ROM Manager, does it ask you for superuser permission?
absolutely, I even double checked =) I am not entirely fresh to rooting phones. I have rooted, unlocked (and even flashed custom roms) I have gone back to stock.. and done the whole process again (JUST to make sure) it doesn't matter what I've done so far though.. the problem still persists.
Rom manager doesn't even ask for superuser permissions, unless rebooting into recovery (surprisingly it does this fine)
Silentplanet said:
Initially CWM was installed fine via Rom Manager but now I can't do *anything* in rom manager. None of the options work, not even the override setting (I have CWM installed already) This wouldn't be a huge issue but I wanted to download some roms away from the computer and experiment a bit.. I was wondering why this would be occouring as it doesnt seem like normal behavior.
I click flash CWM and it gives me the little loading symbol for a few seconds..
I do the same for Override.. same thing happens
None of the other features will work because it doesn't detect CWM
>.< help!
Click to expand...
Click to collapse
Wow, I thought it was just me. Rom Manager just did this to me last night also. I've been rooted and flashing rooms on my gnex since Feb and had no problems. This just happened to me last night out of nowhere. Wasn't even flashing anything. It doesn't even shows that I don't have recovery flashed anymore.
Weird.
Sent from my Galaxy Nexus using xda premium
Alright, I figured out my problem. Don't know if it will help you.
I forgot I downloaded the CWM touch .img but decided I wasn't going to do it. I forgot to delete the .img file from the root of my SD. I deleted it and and than rom Manager went back to normal and let me reflash recovery.
Hope this helps.
Sent from my Galaxy Nexus using xda premium
Cheers but! The root of my SD is empty >.>
Edit: so I went back into root and deleted some folders... and voila! Its all working again! Cheers for the tip mate!
Sent from my Galaxy Nexus using Tapatalk
You probably had an .img in one of those folders. Happy to be of some assistance :thumbup:
Sent from my Galaxy Nexus using xda premium
I had this problem too, the fix permissions button helped for me, then finaly Rom Manager asked for permissions, i hop this helps u guys too :laugh:
I recommend twrp
Sent from my Galaxy Nexus using xda app-developers app
I strongly recommend fastboot.
Sent from my Nexus
If TWRP is asking for a password and not booting do this: Re odin recovery twrp 2.4.4.0, wipe ALL data, odin twrp 2.6.1.0 back on to the device, reboot recovery, re-wipe data, flash desired COMPATIBLE rom.
To sum up what I found, new encryption added to 4.0+ of android encrypts user and important file partitions, updating recovery basically screws that all up. Your device has no way of accessing those files without the encryption key which was never explicitly made, its just a background feature to help protect your data.
I know this isnt much but atleast some people wont have to search around as much.
Now I cant take any credit for this, I also couldnt really find any user that took credit for it either.
Update: Something about gapps is the catalyst for this issue. After I flash gapps i get 15 mins of solid system performance, after that I start to get app download errors. The device will continue to function normally with snag and hiccups but after rebooting it goes right back to bootlock and asking for a P/W in TWRP. And of course I find a couple thread talking about this fix after, sorry for the redundancy I guess.
Can any confirm that Gapps may be causing this? Or better yet, what is actually causing this?
Jataadroid said:
If TWRP is asking for a password and not booting do this: Re odin recovery twrp 2.4.4.0, wipe ALL data, odin twrp 2.6.1.0 back on to the device, reboot recovery, re-wipe data, flash desired COMPATIBLE rom.
To sum up what I found, new encryption added to 4.0+ of android encrypts user and important file partitions, updating recovery basically screws that all up. Your device has no way of accessing those files without the encryption key which was never explicitly made, its just a background feature to help protect your data.
I know this isnt much but atleast some people wont have to search around as much.
Now I cant take any credit for this, I also couldnt really find any user that took credit for it either.
Update: Something about gapps is the catalyst for this issue. After I flash gapps i get 15 mins of solid system performance, after that I start to get app download errors. The device will continue to function normally with snag and hiccups but after rebooting it goes right back to bootlock and asking for a P/W in TWRP. And of course I find a couple thread talking about this fix after, sorry for the redundancy I guess.
Can any confirm that Gapps may be causing this? Or better yet, what is actually causing this?
Click to expand...
Click to collapse
im seeing people popping on on my phones forums (note 2) getting this message....and def not gapps...i have latest 4.3 gapps for weeks now and never seen this message
What rom you using?
PA 3.99 I have been running solid for 12 hrs now but I haven't rebooted since the last time I had to redo this process. It does fix it though.
All my apps have been installing and functioning fine. One thing I did different is I didn't flash BMS kernel. I havent checked the other threads reporting this issue but does any one know if they were using BMS?
Sent from my SPH-L710 using xda app-developers app
Jataadroid said:
PA 3.99 I have been running solid for 12 hrs now but I haven't rebooted since the last time I had to redo this process. It does fix it though.
All my apps have been installing and functioning fine. One thing I did different is I didn't flash BMS kernel. I havent checked the other threads reporting this issue but does any one know if they were using BMS?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Now I dont have TWRP asking for a password but PA_3.99 is stuck at the splash screen with the yellow sub. No longer an encryption issue it seems but now a new one entirely. At this point it exceeds my nooby knowledge of android and im stuck waiting for a kind soul to assist.
So please anybody have any idea? Or any idea how to define the issue better so i can get some help, it seems kernel or recovery related.
Is there a bootloader Im supposed to flash for 4.3? Im at a loss entirely.
Pls&thx
Just flash clockwork. Done
Sent from my SPH-L710 using xda app-developers app
I had the same problem, just once though. I booted into my ROM and all I needed to do was reinstall TWRP through Goomanager, then everything worked out fine. I updated from 2.6.0 to 2.6.1 at that point, so maybe that fixed my TWRP password problem. I did it about two weeks ago, so far no recovery issues. I used TWRP pretty intensely about a week ago to update to 4.3 and all went according to plan.
Shoot...I odin'd twrp 2.6.1.0 so many times I thought my phone would literally die. I didn't come from 2.6.0.1 ( not sure if that's the right) but instead several versions back.
Sent from my SPH-L710 using xda app-developers app
It wouldn't be a bad idea to implement a recovery password
Sent from my Nexus 5 using Tapatalk
alvintimothyjr said:
It wouldn't be a bad idea to implement a recovery password
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It's kind of already been done.
Really...info?
Sent from my Nexus 5 using Tapatalk
Well, I don't know if this is how I'm supposed to go about doing this, but I've been having issues recently with Quantum rom, and was planning on posting them in the actual Quantum thread, but I need 10 posts to do that because 10 posts mean something important.
Anyways, Ive been fine previously just doing
1. Wipe Dalvik, cache, and system,
2. flashing rom and gapps
3. the wipe option you get after you flash (TWRP)
Ive been doing that since i started basically, until 1.9. Anything after 1.9, it either constantly crashes, has processes constantly stopping, or on one of the versions (2.1 i think) the screen would constantly flicker (which someone else mentioned happening in the thread). So i figured I should try a clean flash, so I try wiping everything and flashing, and doing the default factory reset option and flashing, neither of which helped. In fact, after doing the clean flash it made 1.9 stop working too, so I had to restore my 1.9 backup to get it working again.
Anywho, if anyone has any advice that could help me get the newer versions working that would be great, Thanks!
EDIT: I might try flashing a different rom, to see if the issues persist elsewhere, but firstly Id like to stay on Quantum, and secondly, iirc I tried one a different rom when 4.3 first started showing up in roms, and I kept having problems, to which I just went back to Quantum.
It sounds to me you have a bad download. Have you tried re-downloading the ROM? I run the Quantum ROM and I have had no issues whatsoever.
I'm also looking forward to your reply about flashing another ROM.
Sent from my SAMSUNG-SGH-I497 using Tapatalk
codemonkey98 said:
It sounds to me you have a bad download. Have you tried re-downloading the ROM? I run the Quantum ROM and I have had no issues whatsoever.
I'm also looking forward to your reply about flashing another ROM.
Sent from my SAMSUNG-SGH-I497 using Tapatalk
Click to expand...
Click to collapse
Well, I've tried flashing every version including and after 2.0, up to the current version, and have the same problems for each one. So i somewhat doubt that that's the problem. Ill probably try to flash somethign else some time tomorrow
DanCardin said:
Well, I've tried flashing every version including and after 2.0, up to the current version, and have the same problems for each one. So i somewhat doubt that that's the problem. Ill probably try to flash somethign else some time tomorrow
Click to expand...
Click to collapse
Could be your recovery too. I believe the Quantum ROM developer recommends CWM than TWRP.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
If you do decide to change to CWM, make sure you revert to your TouchWiz backup first since TWRP and CWM backups aren't compatible. My best recommendation is to re-download the newest version (2.35 as of 11/7/13), and wipe data/factory reset, wipe /cache, wipe system, wipe dalvik cache, then install ROM and Gapps, wipe cache and dalvik again, and reboot.
iirc, i noticed a fair enough number of people on TWRP that I would prefer to stay on it (since it *should* work). I did, however just update it, tried again. For 2.31, i just get constant for closes on phone and SystemUI, and others iirc. Im trying carbonRom right now, and its working perfectly fine.
EDIT: I did get one SystemUI force close, on it, but its literally constant on quantum sadly.
also tried a couple random other roms, all work, but no Quantum rom will work after 1.9. I also tried just flashing it and not gapps, and i end up with the same thing. Now its just constant force closes though. I don't think i remember seeing any flickery screens like i was getting around 2.1X i think it was.
What bootloader and firmware are you using with the later quantum ROMs.... I believe that the more recent ones need the dmg2 or emj2 boot and firmware to run properly.... Also what were your settings in trickster did you disable mp-dec and UV... Were you OC using stock quantum kernel etc.
Sent from my SGH-I747 using XDA Premium 4 mobile app
android_geek_0507 said:
What bootloader and firmware are you using with the later quantum ROMs.... I believe that the more recent ones need the dmg2 or emj2 boot and firmware to run properly.... Also what were your settings in trickster did you disable mp-dec and UV... Were you OC using stock quantum kernel etc.
Sent from my SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I think that the leaked 4.3 bootloader (whatever end code they gave it) isn't necessary yet, since it hasn't been officially released by AT&T. I'm personally holding off on flashing any 4.4 rom until they're a bit more mature and don't have as many hiccups (although pwncake's work is superb). The UV depends on your device and how it handles it, usually, mine needs +25 than stock but it doesn't seem to shorten battery life. All throughout 4.3, it was best to keep MP-Decision off since he built one into the rom. In the case of 4.4, IIRC from Quantum v3 beta3 and forward, he removed his own MP- Decision, so you could keep it switched on.
android_geek_0507 said:
What bootloader and firmware are you using with the later quantum ROMs.... I believe that the more recent ones need the dmg2 or emj2 boot and firmware to run properly.... Also what were your settings in trickster did you disable mp-dec and UV... Were you OC using stock quantum kernel etc.
Sent from my SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just flash the ROM and boot. If I should be flashing a seperate firmware slash bootloader, I'm not (and never have to my knowledge). I couldnt have gotten to the trickster settings if i wanted to due to the constant force closes.
Would anyone know why when I enable ART mode on Quantum 4.4 Beta3 Rom, my phone continually has pop up messages with unexpected errors? -Such as calendar storage issues or the google keyboard(This should probably be in the ROM section but I can't write there.)
DanCardin said:
I just flash the ROM and boot. If I should be flashing a seperate firmware slash bootloader, I'm not (and never have to my knowledge). I couldnt have gotten to the trickster settings if i wanted to due to the constant force closes.
Click to expand...
Click to collapse
Can't run Quantum either. Same boat. I think it's an issue with the Core kernel and Rev0 processors.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I tried flashing the new beta 8 of v3, and it worked with the odd restart and FC on the side. But the restarts were starting to get a bit annoying so I tried reflashing, and now I just get infinite boot animations no matter what I do. And if I try to restore my nandroid backup, there's this flash every 2 or 3 seconds around the boot animation. Sigh
EDIT: actually, completely reflashing works, but still ends up with the random reboots when doing random things
DanCardin said:
I tried flashing the new beta 8 of v3, and it worked with the odd restart and FC on the side. But the restarts were starting to get a bit annoying so I tried reflashing, and now I just get infinite boot animations no matter what I do. And if I try to restore my nandroid backup, there's this flash every 2 or 3 seconds around the boot animation. Sigh
EDIT: actually, completely reflashing works, but still ends up with the random reboots when doing random things
Click to expand...
Click to collapse
I get the same thing...
supahdaniel said:
I get the same thing...
Click to expand...
Click to collapse
sorry to hear of your problems. it is not the rom. enough folks are running it and I have had flawless installs. Read the OP and follow the directions, it works.
there is a new TWRP (from their site) that I downloaded as a .tar file and flashed with odin. flashes 4.4 roms now so you might try that rout.
my suggestion, in its limited knowledge is this:
put the rom, superuser, and the gapps on your SD card.
Reboot into the new TWRP and format the system- your phone is now blank.
install rom zip
install superuser zip
reboot.
first boot may take a bit, but not forever. Set up CM stuff and go from there
---------- Post added at 12:29 PM ---------- Previous post was at 12:17 PM ----------
Demminex said:
Would anyone know why when I enable ART mode on Quantum 4.4 Beta3 Rom, my phone continually has pop up messages with unexpected errors? -Such as calendar storage issues or the google keyboard(This should probably be in the ROM section but I can't write there.)
Click to expand...
Click to collapse
search the quantum thread about google settings. you have to turn on google now and disable notifications. also, I've been using the swift keyboard and don't have to deal with the google or android keyboard. that seems to have helped.
enable art after loading apps and be prepared for a wait for android to upgrade.