I am running the latest cm9 nightly. If I boot into recovery by using the power button reboot option, I get cwm 5.5.0.4 (from Entropy's DD kernel when I was on UnNamed). If I boot into recovery from rom manager, I get version 5.8.1.8. So apparently I have two different versions of cwm installed on my i777. Is this normal? I cannot seem to update the older version by flashing a newer version over it.
Sent from my SGH-I777 using XDA
HellBunny said:
I am running the latest cm9 nightly. If I boot into recovery by using the power button reboot option, I get cwm 5.5.0.4 (from Entropy's DD kernel when I was on UnNamed). If I boot into recovery from rom manager, I get version 5.8.1.8. So apparently I have two different versions of cwm installed on my i777. Is this normal? I cannot seem to update the older version by flashing a newer version over it.
Sent from my SGH-I777 using XDA
Click to expand...
Click to collapse
<removed because apparently "it works flawlessly in CM9"> - still makes me wonder about the question then
alacrify said:
I'll say it for everybody else - DON'T USE ROM MANAGER. I'm yelling on purpose because it's made clear across the i777 forums that ROM Manager is worthless on the i777 unless you want to rename a backup - and ES File Explorer will do that just fine. You can't update with it, you can't back up safely with it, you can't restore with it, and if you boot into recovery with it you WILL screw up the phone at some point.
Even if someone pipes up that "it works fine on CM9" I still won't believe it - it's just not built for this phone.
Click to expand...
Click to collapse
Ummmmm....it does work totally with cm9. Check out the cm9 thread. It's very nice to be able to use it again.
Sent from my SGH-I777 using Tapatalk
alacrify said:
I'll say it for everybody else - DON'T USE ROM MANAGER. I'm yelling on purpose because it's made clear across the i777 forums that ROM Manager is worthless on the i777 unless you want to rename a backup - and ES File Explorer will do that just fine. You can't update with it, you can't back up safely with it, you can't restore with it, and if you boot into recovery with it you WILL screw up the phone at some point.
Even if someone pipes up that "it works fine on CM9" I still won't believe it - it's just not built for this phone.
Click to expand...
Click to collapse
As TOA stated, Rom Manager works with CM9 flawlessly. Now everything else for the i777 is a different story.
And TOA your Avatar makes me laugh every time I see it, so ridiculous looking lolz
yoderk said:
As TOA stated, Rom Manager works with CM9 flawlessly. Now everything else for the i777 is a different story.
And TOA your Avatar makes me laugh every time I see it, so ridiculous looking lolz
Click to expand...
Click to collapse
Apologies then, but if it's flawless, then I'd be curious how it's dual-booting recovery. Maybe the question should go in the CM9 thread? Or just put it somewhere Entropy will notice - I'll bet he knows.
alacrify said:
Apologies then, but if it's flawless, then I'd be curious how it's dual-booting recovery. Maybe the question should go in the CM9 thread? Or just put it somewhere Entropy will notice - I'll bet he knows.
Click to expand...
Click to collapse
Yeah I'd ask Entropy for sure, he is the kernel master. The only thing I can think of why it is dual booting like that is, it is injecting it's own recovery that is associated with the app. SO when he boots through rom manager it gives him one recovery whereas booting using the button method gives him the cwm associated with the kernel. But as for working flawless, for CM9 you can download the newest nightly's, boot into recovery and flash all through the app.
Yes, I am sure Entropy knows why. I hope he or anyone who knows the topic notices this thread and shed some light on it.
Sent from my SGH-I777 using XDA
Somehow, and I'm not sure why, RM is able to inject its own recovery.
This would be the first time in my entire history that it didn't inject a broken one.
Related
Birgertime has done a great job getting EDT ROMs available via Rom Manager (I may have bugged him a couple of times). I was a bit shocked when I was reading the thread and saw people were having issues when they updated using Rom Manager. I think the consensus was that Rom Manager was not properly wiping.
This is what I did:
I was on Trigger 2.9.3 *I try every ROM and I just felt like being old school.
I opened Rom Manager and downloaded the latest Trigger 3.2,
I used the KB1 Modem, KB5 kernel, I selected a few of the apps I wanted (bloater, titanium, maybe a couple others)
I told Rom Manger to wipe and do a backup by clicking the two boxes.
Once the download was completed I proceeded.
It went into CWR and it did a backup... immediately it did a wipe (it showed the steps in CWR like normal)... and then it flashed the ROM and it rebooted perfectly. I have had NO issues with the ROM. It's perfect in my opinion.
What I want to know, for those who had issues... what was different?
Did you get rebooted into the red voodoo recovery (I was at the normal CWR)? I don't understand how it can work perfectly for me, and not others. I would like to know exactly what went wrong so we can go to @koush and try and get both Rom Manager and Clockwork Recovery working better for us.
Between this, Fix Permissions, Partitions F'ing people, stats not working (for the dev's) I think our phone needs this amazing app to be better, and I know koush can do it.
** If there are other things wrong with Rom Manager/CWR, please post... it would be nice to have a list of things to work on.
I can put up a test version on rom manager. The current Trigger 3.2 up there will wipe regardless of what you tell ROM manager.
PS: who rated it 1 star?
birgertime said:
PS: who rated it 1 star?
Click to expand...
Click to collapse
Team Whiskey
EDIT, were you going to fix the prop so it showed 3.2, not 3.1? =)
Im confused. You said you used CWR to wipe and flash the ROM. What exactly did you use ROM Manager for?
s15274n said:
Team Whiskey
EDIT, were you going to fix the prop so it showed 3.2, not 3.1? =)
Click to expand...
Click to collapse
I think I did when I uploaded the vvm fixed version
androidmonkey said:
Im confused. You said you used CWR to wipe and flash the ROM. What exactly did you use ROM Manager for?
Click to expand...
Click to collapse
To download it
Sent from my SGH-T959 using XDA App
duboi97 said:
To download it
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Ah, ok. I dont see why downloading it with RomManager would make a difference, unless its not completely downloading. The safest is like birgertime says in the Trigger thread, download on PC and check Hash.
androidmonkey said:
Ah, ok. I dont see why downloading it with RomManager would make a difference, unless its not completely downloading. The safest is like birgertime says in the Trigger thread, download on PC and check Hash.
Click to expand...
Click to collapse
Rom Manager is the most convenient way to do this. it also checks the MD5 before it flashes the ROM. Trust me when I say I know the process...
I just want to know from those who had issues with using Rom Manager to download/wipe/flash, what went wrong?
I flashed it using Rom manager.
I chose KB5 modem and KB5 Kernel.
along with things like Bloater and swype.
it rebooted into red recovery and seemed to go fine from there.
when it first booted up it seemed ok at first, I let it sit for a while like usual.
and then rom manager force closed.
from there it was just force close after force close.
So I rebooted back into recovery and wiped data and dalvik.
then I rebooted.
and everything works just fine, with the exception of it never installed any of the extras I chose (swype,Bloater, etc...)
but I had those in titanium backup just in case anyways so it wasn't a big deal.
Its been running beautifully ever since.
Pretty much same thing happened to me, it went to red recovery and seemed to flash just fine. then when it rebooted i kept getting force closes everywhere. rebooted to clear cahce, dalvik, and fix permissions and has been fine ever since. it didnt wipe my apps which i found a bit odd
Alright, so as I expected... it sounds like it was
THE RED VOODOO RECOVERY AS THE PROBLEM.
Anyone able to prove that wrong?
I mean, it makes sense, it's not the recovery Rom Manager expects to see.
So, how do we fix it? This would not be koush now, I do not think.
Where did the red voodoo recovery initiate? I remember it just showed up one day. was it supercurio?
Does anyone know or has anyone heard if this will be included in the next update for the Glitch kernel? I havent seen or heard any word on this and am more or less just curious.
Sent from my SCH-I500 using xda premium
hesh.monster said:
Does anyone know or has anyone heard if this will be included in the next update for the Glitch kernel? I havent seen or heard any word on this and am more or less just curious.
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
yes it will. it was just recently talked about in the glitch v12 thread.
A word about the 3 finger recover thing. Jt's zip file flashes both a recovery image and a supporting kernel.
The recovery image is flashed to the recovery partition that is booted when you do the 3 finger method. The image, however, does not actually contain an mtd-compatible recovery (for some reason, it can't). Instead, it contains a "decoy kernel" that sets a flag in /data and then boots the main kernel.
The main kernel (the one we're always flashing and modding) then looks for that flag, and if it is there, runs recovery instead of the ROM.
A consequence of this is that if your main kernel is somehow hosed, you no longer have the option of going back to 3-finger-land and fixing it. You must Odin/heidmall a new, working kernel or the old recovery.bin.
This is why, when v13 comes out, there will be a separate zip that flashes the "decoy kernel" only. I figured some people might not want to give up that extra later of safety, so it will be optional whether you want the 3 button fix. The new glitch kernel should work fine either way.
Click to expand...
Click to collapse
and there it is
Gracias, havent been in the thread for a while it's kind of messy in there
Sent from my SCH-I500 using xda premium
Just like the title says why should we not use rom-manager on this phone?
from what i can remember it installs a ****ty version of CWM that doesn't cooperate well with our phones.
Boobie Watcher said:
from what i can remember it installs a ****ty version of CWM that doesn't cooperate well with our phones.
Click to expand...
Click to collapse
gotcha. i wish koush would do something about rom manager because the atrix also had a wipping issues on roms and he never fixed it
From my recent experience with the SGSII, the recovery is integrated into the kernel (unlike HTC devices which have a dedicated partition for it). My guess is ROM Manager can't flash it, since it doesn't have the kernel image.
Phoenix84118 said:
From my recent experience with the SGSII, the recovery is integrated into the kernel (unlike HTC devices which have a dedicated partition for it). My guess is ROM Manager can't flash it, since it doesn't have the kernel image.
Click to expand...
Click to collapse
gotcha thats intresting
You shouldn't use it on any phone anyway, your best bet is going into recovery
Sent from my Inspire 4G using XDA App
Haha too funny I was literally wondering this last night. Glad you asked kuz I couldn't find an answer when I did a quick search.
Edit: so I've been running miui this week and see the app rom manager. I'm fine as long as i don't actually do anything through it correct?
Sent from my SGH-I777 using Tapatalk
It breaks and does weird crap - I've heard it works OK if (and only if) you are currently on CM7.
But since you're most likely using it to move to/from another ROM... Just three-finger into recovery or if the ROM has an extended power menu use that for recovery.
Its best to just use three-finger or the extend menu power menu like Entropy said. I've seen Rom manager mess up leading to a semi-brick phone.
Hey all,
First time poster and new to rooting.
I ended up attempting to use rom manager to load CWM right after root, but I think that borked my wifi.
What can I do if I've already used it? I did it because I hadn't yet seen all the xda threads on NOT using it, and the place I was was not as well informed as you folks.
Also, how do I get CWM if not via ROM Manager?
My brothers EVO was royally effed up from using ROM Manager. Became a paperweight until Sprint authorized a replacement.
karankshah said:
Hey all,
First time poster and new to rooting.
I ended up attempting to use rom manager to load CWM right after root, but I think that borked my wifi.
What can I do if I've already used it? I did it because I hadn't yet seen all the xda threads on NOT using it, and the place I was was not as well informed as you folks.
Also, how do I get CWM if not via ROM Manager?
Click to expand...
Click to collapse
Read through the FAQs and this thread - CWM is included in kernels that support it.
karankshah said:
Hey all,
First time poster and new to rooting.
I ended up attempting to use rom manager to load CWM right after root, but I think that borked my wifi.
What can I do if I've already used it? I did it because I hadn't yet seen all the xda threads on NOT using it, and the place I was was not as well informed as you folks.
Also, how do I get CWM if not via ROM Manager?
Click to expand...
Click to collapse
I ended up figuring most of this out so I wanted to close this out (for anyone that stumbles past my original post).
Here's what I did:
I uninstalled ROM Manager - but this didn't get the wifi going.
I reflashed with the stock ROM and unrooted kernel - this still didn't help.
I did a factory reset - this did manage to get it going.
I was able to track down a CWM standalone that I flashed it with (using Odin).
I followed that up with a root, a wipe, and then a fresh flash of UnNamed.
Phone seems to be working fine.
Andrew149 said:
Just like the title says why should we not use rom-manager on this phone?
Click to expand...
Click to collapse
When I first rooted my phone I installed rom manager because it looked easier to just pick the file that u wanted flashed and it would do it for u, so u wouldn't have to play with the volume keys. But every time I tried to do anything with it, it just said certificate not found. Aborting. So u shouldn't use rom manager. I think it works with the roms that u download of the app but not ones from XDA.
Sent from my SGH-I777 using XDA App
I loaded a kernal with cwm. I use rom manager to install Google apps. After new rom loads up.
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Flash entropys kernel. Daily driver
Sent from my Samsung Galaxy S II
If you're on CM7, ROM Manager can be used to install gapps - that's about the only thing it doesn't seem to choke on.
karankshah said:
Hey all,
First time poster and new to rooting.
I ended up attempting to use rom manager to load CWM right after root, but I think that borked my wifi.
What can I do if I've already used it? I did it because I hadn't yet seen all the xda threads on NOT using it, and the place I was was not as well informed as you folks.
Also, how do I get CWM if not via ROM Manager?
Click to expand...
Click to collapse
You cannot get CWM via ROM Manager - that is the point. It comes with certain custom kernels such as Entropy's DD kernel. If you do not have a CWM kernel - you will more than likly need to use Odin to get a kernel with CWM.
If you have totally screwed things up - look in the dev thread for "the return to stock" section and start over doing it the right way
karankshah said:
I ended up figuring most of this out so I wanted to close this out (for anyone that stumbles past my original post).
Here's what I did:
I uninstalled ROM Manager - but this didn't get the wifi going.
I reflashed with the stock ROM and unrooted kernel - this still didn't help.
I did a factory reset - this did manage to get it going.
I was able to track down a CWM standalone that I flashed it with (using Odin).
I followed that up with a root, a wipe, and then a fresh flash of UnNamed.
Phone seems to be working fine.
Click to expand...
Click to collapse
Hi first post as well XDA forums so in depth and helpful decided I wanted to be apart of it. Still a noob though ill work my way up.
I am trying acheive the same goal he is, that is to say Instal the UnNamed (it is exactly what I want) Rom on my Samsung Galaxy S2 Skyrocket.
Keep it brief: Rooted my phone using root exploit:
it will not let me post link. the zergrush one
and bellow flashed clockwork mode using stand alone not ROM because of this forum. Model 5.0.2.6
I wipe catch, battery, then format everything. Then I start to flash the ROM. The installation begins. It cleans and formats everything again, then sais that there was an error in the file and it fails. After this if I dont restore my phone will not start. Ive tried it several times being even more thorough on procedure and its the exact same error every time.
Im just wondering if its the way I rooted it is incorrect, The CWM Im using is not the correct one, or if Im doing something wrong entirely. I think it might be CWM but I have not been able to locate one like he did that worked.
Any help, suggestions, criticism or advice would be very helpful. I just thought Id ask. thanks in advance ^^
Elemblue said:
Hi first post as well XDA forums so in depth and helpful decided I wanted to be apart of it. Still a noob though ill work my way up.
I am trying acheive the same goal he is, that is to say Instal the UnNamed (it is exactly what I want) Rom on my Samsung Galaxy S2 Skyrocket.
Keep it brief: Rooted my phone using root exploit:
it will not let me post link. the zergrush one
and bellow flashed clockwork mode using stand alone not ROM because of this forum. Model 5.0.2.6
I wipe catch, battery, then format everything. Then I start to flash the ROM. The installation begins. It cleans and formats everything again, then sais that there was an error in the file and it fails. After this if I dont restore my phone will not start. Ive tried it several times being even more thorough on procedure and its the exact same error every time.
Im just wondering if its the way I rooted it is incorrect, The CWM Im using is not the correct one, or if Im doing something wrong entirely. I think it might be CWM but I have not been able to locate one like he did that worked.
Any help, suggestions, criticism or advice would be very helpful. I just thought Id ask. thanks in advance ^^
Click to expand...
Click to collapse
UnNamed is not a Skyrocket ROM nor are any other ROMs in this subforum. You want to go here: http://forum.xda-developers.com/forumdisplay.php?f=1399
My SGS2 has been running AOKP for a few months now, all of a sudden today the phone keeps rebooting itself every few minutes. I have tried wiping cache, full wipe etc.... I tried installing a different kernel and also a different rom, now it's on ShoStock, but it continues to loop. Also I have flashed the newest version of CWM but everytime I reboot the phone it reverts back to the old version. Any ideas help?
Still Mostly Harmless said:
My SGS2 has been running AOKP for a few months now, all of a sudden today the phone keeps rebooting itself every few minutes. I have tried wiping cache, full wipe etc.... I tried installing a different kernel and also a different rom, now it's on ShoStock, but it continues to loop. Also I have flashed the newest version of CWM but everytime I reboot the phone it reverts back to the old version. Any ideas help?
Click to expand...
Click to collapse
How do you flash CWM?
I got no clue on the issue at hand other than to go back to stock and see if it persists, if it does its hardware.
Is your name a throwback to the movies/books or something else? In hoping something else...
Good luck bro!
Clay
Team Pirate
Sent from my PINK GS2 using xda app
Thanks guys, another issue I noticed is that the power button was acting really strangely. When you pressed it it wouldnt turn off the phone it would just bring up the restart menu or it wouldn't register at all, so I thought I had a hardware issue. Any finally I ran this kernel cleaner:
http://forum.xda-developers.com/showthread.php?t=1363738
did a full wipe etc...installed rom and then kernel and that has seem to do the trick. Going to hope that it continues to work and I don't have to go out and buy a new phone!
Looks like I have some donating to do.
Don't use ROM manager to flash cwm. As that is what it sounds like u did when u said u "flashed" cwm. Our kernels have recovery built in.
Sent from my SGH-I777 using Tapatalk 2
Phalanx7621 said:
Don't use ROM manager to flash cwm. As that is what it sounds like u did when u said u "flashed" cwm. Our kernels have recovery built in.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Thats what I was thinking :highfive:
I download the latest CWM (6.0.1.0), put the zip on my SD then boot into recovery and installed it as a zip, is that incorrect?
Still Mostly Harmless said:
I download the latest CWM (6.0.1.0), put the zip on my SD then boot into recovery and installed it as a zip, is that incorrect?
Click to expand...
Click to collapse
Yeah, that's probably incorrect.
For our phones, CWM is included in all custom kernels and isn't separate from the kernel at all. The only way to update CWM is to flash an updated custom kernel, like if Siyah or NEAK were to update for instance.
Don't bother trying to update CWM all the time, there's honestly little to no benefit from even trying and you'll likely end up with problems instead like you did this time. The version of CWM included with the custom kernels available is more than sufficient, just stick with those instead of trying to update it separately.
So I thought I fixed it but at last I haven't. After running the kernel cleaner, installing different roms/kernels the phone still boots for no reason after a while, not as often but at least 2-5 times a day. I am have no idea what's going on.
Still Mostly Harmless said:
So I thought I fixed it but at last I haven't. After running the kernel cleaner, installing different roms/kernels the phone still boots for no reason after a while, not as often but at least 2-5 times a day. I am have no idea what's going on.
Click to expand...
Click to collapse
You tried going to stock and seeing if the problem persists? For my brother it was an app so keep that in mind as well
clay101eve said:
Is your name a throwback to the movies/books or something else? In hoping something else...
Good luck bro!
Clay
Team Pirate
Sent from my PINK GS2 using xda app
Click to expand...
Click to collapse
still awaiting an answer!
Have you noticed if the phone is getting really hot around the time it's rebooting?
Clay
Team Pirate
Sent from my PINK SGH-I777
clay101eve said:
still awaiting an answer!
Have you noticed if the phone is getting really hot around the time it's rebooting?
Clay
Team Pirate
Sent from my PINK SGH-I777
Click to expand...
Click to collapse
Yes it is definitely from my favorite series of books. This is one of the only forums I visit that I couldn't get just Mostly Harmless.
Doesn't really get hot, but after a while the power button stops responding and only time fixes this or a fresh install of a kernel. I formatted my SD card and the internal memory (without grabbing my pictures ) and any app I install is new from the market.
I currently have CWM Recovery 5.0.2.6 and I'm on CM9 RC1. I want to update to RC2 but I want to backup first. Backup in recovery keeps failing ("Error while making a backup image of /data!"). I thought I'd try updating to the latest version (6.0.1.0), but I can't find a clear answer on this (I read multiple posts on these forums): can I just flash it using the update from zip option in recovery? (I think you have to do it twice in a row?) Thanks.
Slusho said:
I currently have CWM Recovery 5.0.2.6 and I'm on CM9 RC1. I want to update to RC2 but I want to backup first. Backup in recovery keeps failing ("Error while making a backup image of /data!"). I thought I'd try updating to the latest version (6.0.1.0), but I can't find a clear answer on this (I read multiple posts on these forums): can I just flash it using the update from zip option in recovery? (I think you have to do it twice in a row?) Thanks.
Click to expand...
Click to collapse
From what I've heard you should never update CWM. Also are you backing up in recovery? or Using (God forbid) Rom Manager
CWM is easy to install.
There are two methods that I know of.
The first being using ROM manager though it could (ironically) break it and your device end up in a soft brick.
The second is to manually push it using adb, but first you must download the CWM for our phone (i777) from the clockwork mod website.
Sent from my SGH-I777 using Tapatalk 2
Biporch said:
CWM is easy to install.
There are two methods that I know of.
The first being using ROM manager though it could (ironically) break it and your device end up in a soft brick.
The second is to manually push it using adb, but first you must download the CWM for our phone (i777) from the clockwork mod website.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Don't tell him to use rom manager.
CWM is part of the kernel on our phones, so you would have to find a kernel with the version of CWM you want to install and flash that to update it.
Are you sure you have enough free space on your SD card to do a backup?
I am using recovery, not rom manager. If I shouldn't update it, how should I backup without getting that error?
Slusho said:
I am using recovery, not rom manager. If I shouldn't update it, how should I backup without getting that error?
Click to expand...
Click to collapse
You sure you have space in SD card?
Sent from my SGH-I777
mvi57 said:
CWM is part of the kernel on our phones, so you would have to find a kernel with the version of CWM you want to install and flash that to update it.
Click to expand...
Click to collapse
I can't stress this enough to people.
For the ATT Samsung Galaxy S2, model SGH-I77, ClockworkMod is a custom recovery built into a custom kernel. It is not separate and you do not flash or update it separately. Please do not attempt to update ClockworkMod at all, this will only result in a soft brick.
As mvi57 said, if you want a newer version of CWM, you'll have to find a custom I777 kernel which has the newer version built in.
I wish we could place this warning somewhere where newbies can see it while trying to flash stuff. I'm glad we caught OP before he soft bricked. OP, I don't mean to make you sound stupid or anything by such a highlighted post, I just want to warn as many newbies as possible, and I'm hoping they see your thread and thus this post.
122ninjas said:
You sure you have space in SD card?
Click to expand...
Click to collapse
That was it. I had past backups taking up space. Thanks.
Also, when I backup my phone to my computer (manually), some files don't copy over (I'm pretty sure it's because the file names are horrendously long). Is there a way I can get around this?
And karate, I take no offense to that. I prefer clear posts like yours, and I actually remember that it's part of a kernel now. I knew back when I first rooted, but forgot, as I'm sure many do. Maybe it should be added to a sticky about updating?
Slusho said:
That was it. I had past backups taking up space. Thanks.
Also, when I backup my phone to my computer (manually), some files don't copy over (I'm pretty sure it's because the file names are horrendously long). Is there a way I can get around this?
And karate, I take no offense to that. I prefer clear posts like yours, and I actually remember that it's part of a kernel now. I knew back when I first rooted, but forgot, as I'm sure many do. Maybe it should be added to a sticky about updating?
Click to expand...
Click to collapse
From past experience it seems like people don't read the stickies
Sent from my SGH-I777
Slusho said:
I currently have CWM Recovery 5.0.2.6 and I'm on CM9 RC1. I want to update to RC2 but I want to backup first. Backup in recovery keeps failing ("Error while making a backup image of /data!"). I thought I'd try updating to the latest version (6.0.1.0), but I can't find a clear answer on this (I read multiple posts on these forums): can I just flash it using the update from zip option in recovery? (I think you have to do it twice in a row?) Thanks.
Click to expand...
Click to collapse
Just install the latest cm9 nightly for the i777. It will install cwm 6.0.1.1... our device is different than others, cwm must be built into the kernal.