I'm trying to get boot manager to load a 2nd rom. ANY rom. I'm running CM7.2 RC1 and the program opens. Works just fine I can make my phone rom a rom and install zip or nandroid to slot 1 but when I boot to slot 1 it just sits on the M logo every single time.
My guess is that the kernel in CM7.2 RC1 is not fully compatable with boot manager? It seems like it is considering other roms didn't even allow me to setup the phone rom. If anyone has any experience with boot manager I would greatly appreciate it.
Some roms just are not compatible. I have never used CyanogenMod 7.2 with Boot Manager, but you will probably have more luck asking in the CyanogenMod 7.2 RC1 thread over on Rootzwiki.
Sent from my Transformer TF101 using Tapatalk
Related
Hi, I have a rooted HTC Wildfire and was trying to install the CyanogenMod 7 ROM based on instructions here (http://forum.xda-developers.com/showthread.php?t=918072).
After wipe+format, I have installed the ROM in recovery mode and rebooted the phone.
Although the phone shows the CyanogenMod 7 startup blue android image, the phone keeps rebooting thereafter without starting up fully.
Can someone tell me what's wrong??? Thanks in advance.
bah. still trying and not working.
Which nightly have you tried ?
Sent from my HTC Wildfire using XDA App
Did you wipe /system under Partitions Menu also?
Yup did the wipe + format as per instruction. but had difficulty booting up CM7 build #34.
decided to install CM6 instead and it's ok.
Just don't understand why CM7 not booting up.
whoorderlaksa85 said:
Yup did the wipe + format as per instruction. but had difficulty booting up CM7 build #34.
decided to install CM6 instead and it's ok.
Just don't understand why CM7 not booting up.
Click to expand...
Click to collapse
It is probably because of the new kernel. Many users are reporting the same issue. To circumvent this, you have two options:
* Use an older Nightly. #0 and #19 are recommended.
* Flash #34, then, Flash HCDR.Kernel v4.1 from the HCDR.Kernel thread under Wildfire Android Development Thread, then reboot.
Is there an cm7 which also on the internet can and you can make calls.
Ihad it before but I can't call
guus_1995 said:
Is there an cm7 which also on the internet can and you can make calls.
Ihad it before but I can't call
Click to expand...
Click to collapse
Tried #19??
Good day all. I recently bought a Nook Color. I'm running CM7.0.2 along with gapps 20110613 from a 16gb SanDisk class 4 SD. When set up the apps (after enabling wifi) I got an error, due to the fact that my sucky router dropped the signal. As a result of this I was not able to download gmail, google maps, etc. My android market runs perfectly but I wanted to flash gapps so as to download gmail and the others. I went into ROM manager and updated to the latest CWM. However, no matter what I do I can't but into recovery. I tried n+power button, reboot into recovery from the power button menu, and from within ROM manager. All no go...it just booted into CM7, so I removed the SD card to boot into stock Nook 1.2 software. When I did this it brought me to the CWM recovery menu (SD card not in). Of course I could not select anything on the menu. Put back in the SD while still in the menu to try select an option but nothing. Shut it down by holding the power button and booted it back up and it went str8 into CM7. Shut down took out SD and it booted into stock Nook 1.2 software. What am I doing wrong guys? I'm trying to flash the overclock kernel and reflash gapps. THANKS
Could the reason gmail, youtube, googlemaps didn't install on setup be due to the fact that I'm not in the USA? If so I'd still like to know what the problem is so I can flash the overclock kernel.
No one has any idea? I know one option is to backup and redo everything, but I'd really like some troubleshooting ideas before.
Did you use the 1.3 image from verygreens thread? If so the old 7.0.* stables are not supported. You will need to back up and redo it either with the old image or a new CM7 version.
---
- Sent from my LG Optimus V using Tapatalk
Yea I used the 1.3 in the thread with 7.0.2. What version cm7 would I need to use with the 1.3? 7.0.3 or a nightly,? Where would I be able to find an older image to work with 7.0.2 and what version of the image should it be?
The 1.3 image won't work with any 7.0.* versions. You should upgrade to either a recent nightly or the 7.1.0 RC. You could find an older image somewhere but there isn't much of a point as you would have to redo it all anyway so why not upgrade? Plus your battery life will improve by a lot as 7.1 RC and the nightlys have deep sleep.
---
- Sent from my LG Optimus V using Tapatalk
As I said many times to newbie who runs CM7 off uSD that do not or should not mess up with ROM Manager. In fact, there are members also confirm that if booting off uSD, ROM Manager has no effect.
Based on what you, OP, described, you had flashed the CwM into the internal memory.
Keep your fingers crossed as I do hope you didn't screw up anything else.
Anyway, using verygreen's 1.3 image along with the latest nightly-built CM7 and the latest 06132001 gapps and boot it off uSD again. You should be fine.
Before that, fix your home wireless network first.
I decided to just go with 7.1RC1 since I wanted the better battery life. Is there a way to check about the CWM on the internal and how would I go about removing it if I did? I ask for warranty purposes ofcourse since I opted for the 2 year extended one. Also to flash upgrades and such, since you don't recomend using ROM manager then how should I go about doing it (i.e. overclocking kernel)?
dna59 said:
I decided to just go with 7.1RC1 since I wanted the better battery life. Is there a way to check about the CWM on the internal and how would I go about removing it if I did? I ask for warranty purposes ofcourse since I opted for the 2 year extended one. Also to flash upgrades and such, since you don't recomend using ROM manager then how should I go about doing it (i.e. overclocking kernel)?
Click to expand...
Click to collapse
1. I never have any issue related to battery with any nightly build that I've ever used. I am currently having the nb153 and it is fantastic.
2. Check CwM and how to remove off the internal memory? I don't know any quick way except restoring the original ROM.
Again, for warranty purposes, strongly suggest running off uSD
3. Updating by loading/copying/dragging the updated files onto the root folder (aka "boot" partition), then TRY loading into Recovery by:
a. combination of power/N buttons if you have skill or
b. let it boot normally into CM7, wait until completely loaded, then reboot and select "recovery" option. Keep yr fingers crossed. This is an easy method but if it doesn't work then option a is the only choice.
Sorry the battery issue was as compared to the current CM7 stable not the nightly. I got everything installed so far besides the overclock kernel. So I will try your recommendation for booting into recovery not using ROM manager.
You don't flash anything when running off an sd card you just boot into recovery and then reboot. Easiest way to get the overclock kernel would be to just upgrade to the latest nightly.
---
- Sent from my LG Optimus V using Tapatalk
Hello all, I've successfully rooted my phone, I get the yellow triangle when I boot, and I can run root apps. My kernel is cyanogenmod #4, and running 2.3.3 standard rom. I have rom manger installed and have clockwork mod 4.0.1.4 installed. My question is however that I can only sometimes boot into recovery, I occasionally get a white triangle with an ! in the middle with a little green droid. When I do get the phone to boot into recovery, and say try to back up my rom, it freezes at backing up system, progress bar never moves. Also tried custom roms, same thing, no joy, progress bar is the same, doesn't even start to move. I have had a number of android phones and have always ran custom roms, so do have a little idea about installing them, but I'm totally stuck. Any help would be greatly appreciated, dying to try the new cyanogenmod rom.
Sent from my GT-I9100 using XDA App
Rom Manager isnt compatible with the SII, use the standard CMW via the 3keys/Jig/app and not
Rom Managers recovery.
Sent from my GT-I9100
ROMManager most certainly does work with SGS2, it is even the recommended way for installing CM7 on the SGS2.
I've also never seen the problem OP says, even though I use rommanager a fair bit.
I've been running CyanogenMod 7.0.3 on my Desire Z for the last couple of weeks but have been unhappy with the battery life, so thought I'd try installing the Pershoot kernel as it had been recommended elsewhere here.
I downloaded and installed Pershoot using ROM manager but the phone got stuck trying to reboot - I got the blue Android with the spinning arrow going perpetually I waited 10-15 minutes for it to complete, took out the battery, retried, waited another 10-15 minutes but it still wouldn't complete the boot process. In the end I had to restore to my previous backup.
Has anyone successfully deployed Pershoot on an existing CM7 setup?
itm,
I've been running Pershoot on both CM7 and MIUI on my Desire Z without issues. Might just have been a hickup with your handset.
I'd try it again. Just to see.
Cheers mate,
Hopefully you won't run into the problem again.
Thanks for your reply. As a matter of interest, what method did you use to flash the kernel? Did you use ROM Manager?
Hopefully your flashing straight through recovery and not RM. If your not, that might be the problem.
I downloaded Pershoot from Rom Manager and then used the Install feature from Rom Manager which then rebooted into CLOCKWORK RECOVERY and then installed the Kernel.
I didn't run into any problems.
Thanks for the replies. I tried installing a different ROM from a .zip on the SD card (Wildmonk's 2.6.38.8) and this time it worked.
The main reason for checking out alternatives is to compare battery life. How have you guys found battery life compared to the CM7 default kernel?
Also, which version of Pershoot are you running?
I just updated to the latest MIUI release earlier 1.8.19.
My battery life depends on how much I use it... I'm quite a heavy user and I'm getting a little over 24hrs. On the weekend I may get more as I don't use it often up to 30hrs.
I'm currently running on the following:
Hello XDA,
First time posting so I have to ask in Q&A rather than the thread for MultiROM itself. I've been to these forums quite a few times for rooting and unlocking other's devices, but now that I have a Nexus 7 myself, it's time to start messing around with it.
So the situation for my problem is that I have successfully installed MultiROM and was able to boot up my stock image fine, but when I installed Cyanogenmod 10.0.0, the screen automatically goes to the boot screen for Cyanogenmod rather than asking which ROM to boot and then just hangs on that boot screen forever.
I have not used the kexec hardboot patches for anything yet so it can be that I should be using those somewhere along in the process.
Also, how do I go about uninstalling MultiROM so that I can start all over again? Do I just go into TWRP and hit "install" and choose the stock image for 4.2.1?
destructo322 said:
Hello XDA,
First time posting so I have to ask in Q&A rather than the thread for MultiROM itself. I've been to these forums quite a few times for rooting and unlocking other's devices, but now that I have a Nexus 7 myself, it's time to start messing around with it.
So the situation for my problem is that I have successfully installed MultiROM and was able to boot up my stock image fine, but when I installed Cyanogenmod 10.0.0, the screen automatically goes to the boot screen for Cyanogenmod rather than asking which ROM to boot and then just hangs on that boot screen forever.
I have not used the kexec hardboot patches for anything yet so it can be that I should be using those somewhere along in the process.
Also, how do I go about uninstalling MultiROM so that I can start all over again? Do I just go into TWRP and hit "install" and choose the stock image for 4.2.1?
Click to expand...
Click to collapse
It's overwriting the kernel with one of its own... that's the only thing I can think of. Flash a kernel that has MultiROM support like m or motley.
Mac of York said:
It's overwriting the kernel with one of its own... that's the only thing I can think of. Flash a kernel that has MultiROM support like m or motley.
Click to expand...
Click to collapse
Does this mean that I should find a version of CM that has one of those kernels? Or do i simply flash the kernel by itself and that would overwrite the CM kernel so that the problem would be resolved?
Also I tried installing Kaos Droid and chose the option to install the M kernel before CM actually and I remember that it also would just boot to a completely black screen and nothing past that. So i'm not sure if it's the kernel. But i did just successfully go back to stock and rooted again so that I will try out your suggestions tomorrow. Thanks.
destructo322 said:
Does this mean that I should find a version of CM that has one of those kernels? Or do i simply flash the kernel by itself and that would overwrite the CM kernel so that the problem would be resolved?
Also I tried installing Kaos Droid and chose the option to install the M kernel before CM actually and I remember that it also would just boot to a completely black screen and nothing past that. So i'm not sure if it's the kernel. But i did just successfully go back to stock and rooted again so that I will try out your suggestions tomorrow. Thanks.
Click to expand...
Click to collapse
You can flash the kernel separately and it'll be fine.
Sent from my Nexus 7 using Tapatalk HD