Hi all.
Hope everyone is having a good day!
Lets start: in simple words, it appears I've got two CWM installed. Know it sounds crazy but this is how it looks.
I run Villain 2.4.2 with nynmphetamine 2.1.3 kernel and "some" CWMs
Previously I had also Villain but on CFRoot kernel that preloads a custom CWM
What I've done:
I tried to install CM7 "easy" way so installed ROM manager and when it asked me if I wanted to flash CWM with the newest one I pressed "yes" and stupidly overwrote it. Then downloaded CM7 and when ROM manager attempted to boot into CWM android logo with an expression mark appeared and the phone hung. I rebooted into recovery and it showed me I run CWM 4.0.0.2 (i think that's the custom from CFroot) but the ROM manager says I've got 4.0.1.5.
When I tried to install CM7 via 4.0.0.2 the installation itself went fine but the phone stucked on Samsung logo during post-instalation booting.
Could you give me an advice on how to sort this out? I mean to get properly set up kernel and CWM after some serious messing up
I'd be grateful for any help.
Cheers.
chalger
I dont know if its possible to have 2 CWMs (maybe app version is different), but this happens with CM7. You should wipe dalvik, factory reset, flash cm7 and boot. Phone will get stuck, shut down long pressing power, reboot in cwm and reflash (no wipe needed). CM7 should boot now.
Related
Hi,
Due to HTC's special touches, the recovery image doesnt stay flashed, and on normal boot its flashed over (meaning if i try to go to recovery after a normal boot, i get the red triangle stuff, and have to pull the battery). I was wondering if this would potentially cause troubles if i was trying to flash a custom ROM from recovery? in other notes, i do find sometimes i have to pull the battery 4 or 5 times to get it to normally boot (thats without holding the buttons >.>).
Thanks in advance.
HTC HERO recovery image flashing problems
I am having exactly the same problem!
I did a quite a bit of research on how to root, backup and flash my HERO and every guide I found describes the process using Universal AndRoot + Rom Manager and it seems there should be no problems. I already rooted my phone successfully, installed Rom Manager and flashed either ClockworkMod 2.5.0.1 or RA Recovery 1.7.0.1 which are able to boot but only once. The next time I reboot I get the red triangle warning and it loads into stock recovery (by pressing vol_up + powroff buttons), so the custom recovery lasts only one boot cycle. I was able to backup but I don't want to risk to wipe and flash since there is a chance it might stuck in the bootscreen loop afterwards and I won't be able to do anything.
There is a thing with s-off and SPrecovery which helps to resolve the problem but it doesn't look like there is anything for HERO.
Any help would be appreciated.
ps I tried to manually flash recovery from inside the phone and from windows command line with the same result.
forum.cyanogenmod.com/topic/8182-how-to-root-your-hero
posted some similar comments over there, and the only init script that i can find when in recovery.
Yeah I posted my question there too.
I was able to find some information about the issue (he is talking about Villain ROM but I think it doesn't really matter):
pulser_g2:
Repeat the process again, as I think stock ROMs try and overwrite the recovery each time they boot. When you finish the process, immediately nandroid and flash VR12. That will then flash a new recovery, AmonRA 1.6.2a, and you will be sorted
Click to expand...
Click to collapse
So it looks like we should just go ahead and flash a custom rom which, in theory, will eliminate the problem.
yeah was tempted to just flash, but sending duck my system img for him to dissect anyway.
yeah worked fine, running cm6.1 now
Yeah once you root you have to flash a custom rom before reboot or u loose the root
I learnt it after lots of reboots and re roots.
but now I wanted to know if I could save the original rom which i have as nand backup to make as an update.zip like custom rom for safe keepimg
I flashed CM6.1 -based TastyFroyo 1.2 and I can confirm custom recovery stays flashed now.
Alright so I just got a fascinate today. Already rooted it and looked on how to get in to recovery. Well I did the install with odin steps and all that jazz and everything appeared to go fine until I go to reboot into recovery in rom manager. It just takes me to the stock recovery and gives me the signature error or whatever it says. I tried doing a factory reset and rooting/odin all over again to no avail. Now what should I do in this situation?
QUOTE=iammclovin804;16065943]Alright so I just got a fascinate today. Already rooted it and looked on how to get in to recovery. Well I did the install with odin steps and all that jazz and everything appeared to go fine until I go to reboot into recovery in rom manager. It just takes me to the stock recovery and gives me the signature error or whatever it says. I tried doing a factory reset and rooting/odin all over again to no avail. Now what should I do in this situation?[/QUOTE]
Unless your on cm7, rom manager is useless to us as of right now....
Recovery gets over written on every boot from the stock kernel , if you wish to get recovery to stick, you must odin recovery and immediately hold up down and power (the three finger salute) until you see the recovery screen...at that point your must flash a non stock kernel at the least, otherwise recovery will be overwritten right then and there.
After recovery is on there permanently, holding up down power is how you will enter recovery....if however you go to cm7 you would choose reboot recovery from the power button menu
Sent from my SCH-I500 using XDA App
iammclovin804 said:
Alright so I just got a fascinate today. Already rooted it and looked on how to get in to recovery. Well I did the install with odin steps and all that jazz and everything appeared to go fine until I go to reboot into recovery in rom manager. It just takes me to the stock recovery and gives me the signature error or whatever it says. I tried doing a factory reset and rooting/odin all over again to no avail. Now what should I do in this situation?
Click to expand...
Click to collapse
Which recovery are you trying to flash? Better yet, which ROM are you trying to use?
If you'd like to try CM7, I posted steps I did that worked flashing CM7 on another thread.
Refer to: http://forum.xda-developers.com/showpost.php?p=16048409&postcount=10
This is installing CM7 after I Odined from Stock.
Hope you find it useful.
If you like the ROM, don't forget to say thanks to JT!
Hi all,
I rooted my SGS2 (KE7) with CF-Root ages ago and haven't done much since then, aside from take regular backups.
Looking at the Cyanogenmod stuff, I fancy giving it a go. All the guides talk about using the kernel at http://forum.xda-developers.com/showthread.php?t=1118693 .
Does anyone know if I can flash the cyanogenmod ROM using the recovery mode I have with CF-Root, or if I need to get use the kernel from the above patch first?
This morning I tried installing the kernel (from the CF-Root CWM), when my phone rebooted, the touchscreen worked on the unlock page but not once I unlocked (I use LauncherPro as my launcher). Rebooting into recovery mode didn't work (the phone just booted normally) so I reflashed CF-Root but still had the same problem however I could boot into recovery mode and restore this morning's backup.
Now, the phone boots (with the warning triangle, expected) but there is no response after I unlock for a minute or so. Setting the stock launcher back works but I'm confused about why this should happen and what I should do next.
Does anyone know why my non-stock launcher is now being non-responsive for the first minute after boot / what I can do to get it back?
Am I able to install cyanogen with CF-root, or do I need to use the kernel in the above link? and if so, do I need to do anything other than just flash and if not why didn't the phone boot into recovery when I tried it earlier?
Any suggestions gratefully received!
-Jeff
The cf-root kernel is all you need to install cm7.
peachpuff said:
The cf-root kernel is all you need to install cm7.
Click to expand...
Click to collapse
This is correct. However, after you install the cm7 .zip the first time, it will have only installed the kernel for cyanogen mod. So you will then need to boot back into recovery with 3 button mode and run the zip install again from there. You will then have CM7.
Electroz said:
This is correct. However, after you install the cm7 .zip the first time, it will have only installed the kernel for cyanogen mod. So you will then need to boot back into recovery with 3 button mode and run the zip install again from there. You will then have CM7.
Click to expand...
Click to collapse
Don't quite understand this. I've got the cm_galaxys2_full-39.zip (100MB), I was going to put this on the SD card, boot into recovery mode and install from there. Are you saying I need to do this same process twice? (and if so, why does it only install the kernel the first time when it is the complete zip file?)
Cheers,
-Jeff
CF-root => Cyanogen mod
Hello everybody,
There are a few threads that discuss this question, but they all draw a different conclusion.
This one for instance : http://forum.xda-developers.com/showthread.php?t=1367933 (or if the link is broken, search for : How can i use cf-root kernel for cm7?).
In the thread above they claim that CF-root is not compatible with CM7, however in this very thread there is said that when installing the .zip file twice, it should work just fine. As i'd like to install CM7 on my CF-rooted S2, i have to know for sure:
Is there a way to install CM7 on a CF-rooted device?
Many thanks
Rom manager doesnt work with cf root, so to flash cm7 download the zip, boot into recovery, and flash the zip twice, and it will work.
Make sure you wipe data and cache, and take backups before you do.
Sent from my GT-I9100 using Tapatalk
Ok, i'll give it a go .
Thanks for the quick response, it is much appreciated!
Hey everyone, my problem is genuinely mind blowing.
- I installed ROM Manager
- I flashed CWM Recovery
- Rebooted into CWM Recovery
- Downloaded CM7 and proceeded with the installation.(checked the cache wipe options too)
- It goes down to installing and...gets stuck. Nothing happens. It just says "installing update" or something similar.
My OS is ICS 4, is this the problem?
Also, is it absolutely necessary to have a micro SD inserted? I believed it could be done without one, but couldn't.
UPDATE: it somehow installed now, but it hangs at the boot screen. What is this about?
Thanx.
you have to atleast 2 or three times flash to get it worked
Thanx.
I eventually managed to brick it, so had to reinstall ICS
I believe this thread can be locked.
for your Notice :
In future Rom manager is not advisible for a smooth operations on the SGS2, it is highly recommended to use rooting kernels like CF-root for rooting the phone, it will provide CWM as well.
Ohai!
I have a Galaxy Player 5.0 USA (YP-G70), and a few days ago I installed Entropy512's kernel via the `dd` method. Everything worked nicely, until I decided to boot into ClockworkMod Recovery by holding the volume up key while booting. It booted into the recovery menu, and everything worked nice, but when I hit 'reboot' or 'shutdown', it booted right back into recovery (after seeing the SAMSUNG screen for about 5 seconds).
I've done pretty much everything I can think of. I've reflashed the kernel, flashed CM7 and CM9, and I tried flashing a stock ROM that I found. Flashing the kernel from the stock ROM causes my device to instead go into "Android System Recovery" rather than ClockworkMod Recovery, but I'm able to get back into CWM by flashing Entropy's kernel with heimdall.
I'm capable of getting root access with `adb shell`. I've wiped almost everything on the device (used the 'wipe data/factory reset' option and 'wipe cache partition' option) but still continues to boot into CWM recovery.
I'm not too interested in simply fixing the device so it's back to stock, as I *really* want CM9. I have a Droid X to keep me busy for now, so I found that my Galaxy Player has been just sitting there, collecting dust. If I can get it to run CM9, I'd have more use for it.
I apologize if I left out some important information. Any help would be appreciated!
Thanks in advance,
- Ben
Just an update, I tried an exitrecovery.zip, which did not help. I also extracted the exitrecovery.sh from the zip and executed the one command it had inside it manually in a root shell. Still stuck. Is my device bricked in some form? I'm pretty sure there is some bootflag that tells it to boot into recovery, even if everything is fine.
I would suggest to go ahead and flash CM9, because your problem may be caused by formatting/corrupting /system (the kernel has nothing to load, so it drops you into recovery).
Once you flash cm9, however, do not flash Entropy's kernel again.
Sent from my YP-G70
East gsstert
Mevordel said:
I would suggest to go ahead and flash CM9, because your problem may be caused by formatting/corrupting /system (the kernel has nothing to load, so it drops you into recovery).
Once you flash cm9, however, do not flash Entropy's kernel again.
Sent from my YP-G70
Click to expand...
Click to collapse
Thanks for the reply. I actually ended up trying so, and CM7 as well, to no avail. I also tried flashing stock, as I said in the post (I think, maybe I forgot to mention it) and it failed. (I used heimdall to flash stock)
I ended up giving up and replacing the device since it was under warranty, but I regret doing such as I *really* wanted to know why this happened in the first place. I'm anxious to get CM9 on it. Should I just put the device into download mode and use heimdall to flash CM9?
No. The safest way (and easiest, IMO) I think is to root it while on stock, install Entropy's kernel (extract the zip and dd it), and use CWM to wipe your device and install CM9, plus back up stock if you want to.
Sent from my 5.0 US with ICS
Mevordel said:
No. The safest way (and easiest, IMO) I think is to root it while on stock, install Entropy's kernel (extract the zip and dd it), and use CWM to wipe your device and install CM9, plus back up stock if you want to.
Sent from my 5.0 US with ICS
Click to expand...
Click to collapse
Apologies for the late reply.
That is what I did last time. I actually got stuck in CWM before even trying to flash CM9 or anything. I just booted into recovery, and then instantly clicked on 'reboot'.
Hmmm... that's really interesting. Although I still have no idea why it would have this problem (I've never had it on Entropy's kernel - which version are you using?), I think I know what the problem is. When you tell android to "reboot recovery", it puts a file in the boot partition that the kernel sees after the reboot and tells it to enter recovery mode. Logically, that file gets deleted so the system boots normally next time. It seems that in your case that failed to happen. But I still am wondering why...
Sent from my 5.0 US with ICS
Mevordel said:
Hmmm... that's really interesting. Although I still have no idea why it would have this problem (I've never had it on Entropy's kernel - which version are you using?), I think I know what the problem is. When you tell android to "reboot recovery", it puts a file in the boot partition that the kernel sees after the reboot and tells it to enter recovery mode. Logically, that file gets deleted so the system boots normally next time. It seems that in your case that failed to happen. But I still am wondering why...
Sent from my 5.0 US with ICS
Click to expand...
Click to collapse
Yeah, seems to be probably what happened. I actually ended up trying again on the new Galaxy Player, and things went swimmingly. I am now happily running CM9 on this device. However, I am scared to even think about booting into recovery again. (I only went into recovery to flash the kernel, and wipe the data partition)