So I've tried searching but don't see anything relating to my question. If it's there I missed it and apologize.
My situation is this: I was running stock rooted 1.40 on my NT16 for the longest time but decided I wanted to try out the latest and greatest. I am not a noob when it comes to ROMs, but I am when it comes to Cyanoboot. I flashed CM10 and cyanoboot. then using Goomanager got the latest TWRP.
I'm not a big fan of TWRP personally, so i flashed CWM 6.0.13 and have been very happy. CM10 was nice and I liked the look and feel but it just wasn't stable enough to use as a daily so I decided to go to CM9 (0.05.3). I made a backup in CWM, wiped cache, factory reset and then flashed CM9. Rebooted and it loaded up just fine. Runs like a champ. the problem is that when I boot or reboot, I have the old cyanoboot installed. If I hold the n button to go to the menu and choose to boot EMMC recovery, it goes to the newer cyanoboot where I have to hold n again, to select boot EMMC recovery.
Now, like I said, everything seems to be working fine. I went in that way and made another backup in CWM and that finished successfully but how do I make it so there is only one cyanoboot now? I did not flash the recovery that is in the CM9 thread so is that my problem? If so, I will go ahead and flash it, but I wanted to ask before doing that. I would hate to have a third cyanoboot or worse, brick/really screw it up.
Again, I did try searching for this, but didn't find anything. If there is, please point me in the right direction and I will go from there.
Thanks!
Update... Decided to go back to CM10 and try out the latest from crmhoffmann (0.05.3). Restored my CM10 backup and flashed the new over top. Reboot and now the old version of Cyanoboot is gone leaving only the new one again.
I still don't know how to remove the first (older version) but I guess I can forget about it since the newer CM10 seems to be working much better.
Related
I lurked around the GlitchV13 forum for a good long time and didn't find an answer to this.. and because I've only been lurking for about a year I wasn't able to post anything, so it's about time I guess.
I'm having problems with the GlitchV13 kernel. Maybe I'm just being dumb and don't see something here. some help would be greatly appreciated.
I flashed GlitchV13 on my CM7.1 using CWM 5.0.2.7. No problems at all. Running great for two days. Suddenly, my phone won't connect to wifi. Cycled airplane mode and nothing popped up, so I did a reboot.. annnd got stuck in a bootloop between the CM splash and my lockscreen (wtf). Rebooted again, and now I'm stuck on the CM7 screen. Tried to Odin CWM4, still no bueno, and I get a "E:Can't mount recovery/log/"blahblahblah.
Admittedly, this happened one time before- I did a clean install from stock. Then I got gutsy and flashed GV13 again. Any idea why this is happening? After I flashed Glitch I didn't touch any other recoveries, nor did I try to push anything with Odin or Heimdall.
I really just don't wanna flash back to stock again, and a new solution to why this is happening would be super!
Thanks in advance.
EDIT: Got it. Glitch comes packaged with 4.x CWM, while CM7 comes packaged with 5.0.2.7. Any way to reconcile the two? Worth it to push 4.x over 5.x, flash Glitch then backup so I don't have to do a full restore to CM7?
I had the wifi problem on the stock kernel once, so I dont think that problem is with Glitch.
I also just flashed the latest kernel version and they have updated CWM to 5.0.2.7.
That being said are you sure the recovery is making this much trouble on the phone? Usually it doesn't make a difference (besides backups and whatnot).
The glitch recovery has a few extra features that the CM7 recovery does not.
one being able to wipe dalvik and cache at the same time. (very minor but its more convenient)
I personally think its worth it.
Hey all,
I'm very new to Cyanogen, so sorry if this is a very n00b question.
The ROM Manager doesn't appear to work. It keeps telling me I'm not running ClockWorkMod recovery, and cannot connect to the web to download. I purchased the premium version thinking it would solve this (as well as to support the dev), but no luck. Is it just an issue with the nightlies not capable of handling ROM manager yet, or is it a setting of some sort that I'm neglecting? It's not a huge deal, but it looks like such a nice, simple way to stay up-to-date with the nightly builds as opposed to updating through CWM, wiping, etc.
I saw a post mentioning to go into developer tools and enable root access. The closest I found was in settings and I allowed apps and ADB root access, but this didn't help.
Any suggestions would be greatly appreciated, thanks!
I'm a bit confused, Why do you require ROM manager? The CWM that is built in with the ICS Kang releases should be doing everything that is required, then again, your reply would matter.
I think I am having the same issue. When I try to Flash ClockworkMod Touch in Rom Manager it keeps telling me I need to first install ClockworkMod Recovery even though I have Recovery 5.5.0.4 currently installed. It did the same thing when I had Recovery 4.0.0.4 installed.
I even tried to "Flash ClockworkMod Recovery" (First option in ROM Manager) and it does nothing.
Any ideas?
BEcause the same menu is in the CWM recovery lol
I'm following one of the threads that updates the kang build every 3 days, and as opposed to having to boot through CWM, wipe, install, then re-install apps and replace widgets, I thought I could update through ROM Manager instead.
It sounds like Sn0warmy and I are having similar issues.
From what I've heard the ROM Manager doesn't really work for the tab yet. If you want to update without replacing all your apps you can just flash the zip file in CWM without doing a wipe. If it causes problems then you could do a wipe & reflash afterwards.
Dolfan058 said:
I'm following one of the threads that updates the kang build every 3 days, and as opposed to having to boot through CWM, wipe, install, then re-install apps and replace widgets, I thought I could update through ROM Manager instead.
It sounds like Sn0warmy and I are having similar issues.
Click to expand...
Click to collapse
ROM manager works but it's wonky on the ICS kangs. It doesn't do anything that you can't already do in recovery, so there's no real advantage anyways. Oh, and don't use ROM manager to install a new recovery, and CWR touch doesn't work for the GT10.
^You saved me the trouble of insisting Why thank you good sir.
Thanks for the replies. I'll keep updating through CWM.
Coffeebeans, obviously I'm following your thread (thanks for the good work!) and I tried flashing over once but I got a ton of process media FCs so I figured wiping was the best way to go and have done so ever since. Probably should invest in titanium backup at this point so I don't have to reinstall from market everytime I wipe.
Thanks again for the help y'all.
It worked once with 4/17 build of CM9. After that, it has never worked again. It boots into recovery and pretends its flashing, but stops half a second later and restarts.
Something odd happened today when I tried to update. It rebooted and phone locked up and screen went black. I took out the battery and put it back in then held up and power to go into CWM. All of a sudden Rom Manager took over and flashed the rom as well as the additional zips successfully and rebooted. Everything works.
CWM tries to flash from /emmc. Rom Manager tries to flash from /sdcard and fails. It may be due to the swapped mount points on CM9. in CWM they are still swapped, even if you check the use internal storage box and everything shows up properly in CM9.
Hi guys, so i decided to install the new CM10 so i already had root, i unlocked using the official tool, then installed CWM from Rom manager.
I then downloaded CM10 and GAAPS and kept them in a folder and also copied them to an sd card for safety.
I booted into CWM sucessfully, took a deep breath, then did a full wipe/factory restore, then wiped Cache, then wiped Dalvik Cache.
Then i proceeded to TRY to flash CM10.......... Firstly, CWM didn't list my external SD Card so i selected from the one i had saved on the internal storage.
It began to do the install then failed stating something about symlinks??? I retried the install and got the same thing.
I rebooted the Prime and now it's just stuck on the Eee Pad splash screen with "The Device Is Unlocked" written in the top left corner and it wont do anything else.............
I can reboot into CWM but how can i fix this and get CM10 installed??
PLEASE help!?!?!?!?!?
Thanks in advance.
Currently, no recovery can access external memory of any sort. Did you make a backup? Is it in the internal memory? Make sure you can flash back to your original settings BEFORE trying to flash something as experimental as CM10.
Please remember any Jelly Bean roms are highly experimental, and probably won't work correctly for everyone.
Read this thread for more help:
http://forum.xda-developers.com/showthread.php?t=1514088
I thought I replied to my own post shortly after the original post. I ended up rebooting into CWM and starting over again from the start and everything went smoothly. I endedup not liking the fact that flash and YouTube aren't supported yet so I flashed CM9 instead and I'm loving that.
Predtechhacker said:
I thought I replied to my own post shortly after the original post. I ended up rebooting into CWM and starting over again from the start and everything went smoothly. I endedup not liking the fact that flash and YouTube aren't supported yet so I flashed CM9 instead and I'm loving that.
Click to expand...
Click to collapse
Good to hear. One last advice is to use TWRP instead of CWM. CWM has issues with the prime while TWRP is more stable.
Predtechhacker said:
I thought I replied to my own post shortly after the original post. I ended up rebooting into CWM and starting over again from the start and everything went smoothly. I endedup not liking the fact that flash and YouTube aren't supported yet so I flashed CM9 instead and I'm loving that.
Click to expand...
Click to collapse
so how many time had u gone back then tried it.... i have the same problem i tried it like 10 times but it still stuck
what step did u do
I'm stuck in the same predicament! Did you just keep trying, and it finally worked????
I've got a Galaxy S III and it worked more than perfect before I decided to get the JB update in Kies. Now the physical buttons happen to freeze all the time (the phone itself works), if the screen is on, I can touch everything, apps work, but back/home/menu/screen off don't. It's terribly frustrating to have such an expensive phone and having such an experience with it.
Anyway, I flashed from Sammobile every possible stock ICS and all of them get me stuck in the splash screen as if it's soft bricked, and ALL the stock JBs have the same button problem. Now I thought to myself the only way to go is CM.
The question is: how to I install CM (9, 10 whichever!) over my JB? Or better still (although I gave up on it) how do I get back to the good old flawless stock ICS?
Thank you in advance!
It's basic. Install a recovery, then grab your desired Rom (cm10 or whatever) then backup your apps with Titanium, and reboot in recovery, wipe all partitions (data, cache, dalvick, system) then flash your room, bit and restore your apps.
I did just that, but I get error status 7 when flashing with every version of CM10 i downloaded. When I googled the error I saw it has to do with the kernel not matching the ROM or something...
Strange as kernel provided with Rom is designedto work with. What version of cwm are you using? Try with twrp recovery.
I noticed I didn't have the last version of CWM so I installed it but got the same error. Then I tried TWRP and it worked like a charm! I especially like the touch version. Thanks a lot for your advice, help and everything!
Before doing my flash, I did my research, and it seemed that in order to update from CM7 to CM10, I had to flash a different version of CWM. So I booted into recovery, flashed the version 6.xxx CWM, and then rebooted (I assumed that in order to flash CM10, I had to be in a CM10-compliant recovery). After getting back to my regular desktop, I rebooted into recovery as normal... only it didn't go into recovery. Instead, it paused for a moment like it would go into recovery, then booted to my normal desktop.
I've tried about a billion ways to boot into recovery, to include SD based recoveries, but it either goes to a larger sized N screen, then hangs up on a black screen, or it boots me to my normal CM7. I "can" continue to operate on CM7, but until I can boot into recovery, I can neither update to CM10 nor address any problems I come across in my current build.
Suggestions?
nashdude said:
Before doing my flash, I did my research, and it seemed that in order to update from CM7 to CM10, I had to flash a different version of CWM. So I booted into recovery, flashed the version 6.xxx CWM, and then rebooted (I assumed that in order to flash CM10, I had to be in a CM10-compliant recovery). After getting back to my regular desktop, I rebooted into recovery as normal... only it didn't go into recovery. Instead, it paused for a moment like it would go into recovery, then booted to my normal desktop.
I've tried about a billion ways to boot into recovery, to include SD based recoveries, but it either goes to a larger sized N screen, then hangs up on a black screen, or it boots me to my normal CM7. I "can" continue to operate on CM7, but until I can boot into recovery, I can neither update to CM10 nor address any problems I come across in my current build.
Suggestions?
Click to expand...
Click to collapse
Have you tried holding on the power button and the "n" button as you boot? I recall running into a similar issue as yours and that was the only way I could get to recovery. If you're able to get into recovery that way I would consider maybe getting a different version fo CWM. I had trouble with the 6.0.1.5 version. You might try the 6.0.1.2 version here: http://forum.xda-developers.com/showthread.php?t=1640958&page=5
I ran into something similar when I tried installing CWM 6.x.x. I chickened out and decided to run CM10 from SD instead, and I'm so happy on the performance now that I do!
I did the "unbrick" thing with "repart.img" to get the Tablet back to "out of the box" state and sighed of relief when it worked!
Yeah, I was afraid of that. I really didn't wanna go through the process of unbricking, but I guess there's no help for it.
troy9829 said:
Have you tried holding on the power button and the "n" button as you boot? I recall running into a similar issue as yours and that was the only way I could get to recovery. If you're able to get into recovery that way I would consider maybe getting a different version fo CWM. I had trouble with the 6.0.1.5 version. You might try the 6.0.1.2 version here: http://forum.xda-developers.com/showthread.php?t=1640958&page=5
Click to expand...
Click to collapse
Power + 'n' doesn't work on my NT either, I have to turn the device off, insert the SD with CWM, then plug in the (still turned-off) NT to a wall charger and allow it to boot up that way - then (and only then) do I boot into recovery, and without touching any buttons. Hopefully that helps
Dang, whoever thought this would be such a booger of a deal?!?
Okay, first off, let me apologize for coming off like a noob, but it seems there's so much information out there that everything's kinda bleeding together, so let me tell you where I'm at.
I've unbricked and restored the NT to stock 1.4.2
I tried rooting, but the only root I can find that is flashable from SD is the 5.5 CWM which is older than the CWM 6.xxx that every CM10 version calls for. So I went ahead and did the root, so now I have a stock NT with root access. This is where I'm getting stuck...
I'm at this point...
http://forum.xda-developers.com/showthread.php?t=1640958&highlight=cwm+1+4+2
...and it apparently requires you to reboot into CWM in order to install CWM?!?
I've found the CWM 6+ files I think I need, but when I try to follow the instructions, my NT won't kick over into recovery---it keeps booting straight to the rooted 1.4.2 stock rom. I've found guides that take you from stock 1.4.3 to CM10, some that take you from 1.4.2 to root, and I even found Indirect's CM7 (without the instructions on how to get CWM on there in the first place!). I even downloaded Rom Manager and tried to boot into recovery that way, but it said there was my device wasn't supported.
I've been staring at this dang screen for three hours, trying to find a step by step, and I'm coming up empty. Maybe I'm just too frustrated at this point and need a breather.
What I need to know is how to install CWM 6+ on a NT that's either rooted or stock 1.4.2 (I still have the unbrick SD card) so that I can boot into CWM. From there, I can make my way through installing CM10. Help. Please. Am about to chew the lining out of my cheek.
I don't know if this might be helpful? http://forum.xda-developers.com/showthread.php?t=2037368
Sent from my NookColor using Tapatalk 2
Not yet. I was expecting OTA to kick in, updating my current 1.4.2 to 1.4.3, but it hasn't. Honestly starting to think my NT doesn't want to be rehacked LOL
Okay, so here's what I'm doing at the moment...
I'm at rooted stock. I moved CWM 6.0.1.2, CM10, and gapps over to internal SD.
I booted into recovery with an older version CWM SD card (SD card image with Win32 > turned off NT > insert SD > plug in USB to autoboot)
While in recovery (from SD), I flashed CWM 6.0.1.2 , CM10 (meghd00t), and gapps-jb-20121011.
I reboot...
WE HAVE JOY!
Now to check to see if the thing's gonna run right (got a whole lotta "XYZ has stopped" error messages upon boot up)
Dangit, keep getting those error messages about Gapps stopping and Google Play, and other stuff. Not allowing me to do hardly anything I need to. I can't even boot into recovery from the home page---it still loads straight to the Rom. In order to get into recovery, I need to use the SD that I made to get into recovery in the first place. Going to wipe dalvik and the other caches to see if that helps...
After wiping the caches, I boot into CM10 with no error messages. I DL'd a game from my Gmail account, and it appears to be working properly. Thanks for the suggestions and for letting me vent
I just went thru this similar ordeal too. It took me over 3 weeks to finally find a recovery & cm10 combo. What I found is that I couldn't get ANY version of twrp to act right. Indirect's flashing tool was invaluable. I finally used it to flash a cwm 6.x from Laverne's thread. It seems that not all versions of cwm 6.x are compatible with certain cm10 roms too & by chance I hit a combo that finally worked! I'm staying with what I got for a while!
Sent from my Nexus 7 using Tapatalk 2