Hey guys.
Using Samsung Galaxy S Froyo 2.2.1 I9000
Was installing CM7 today through CWM in Recovery Mode, at first it wouldn't work, threw me an error about signature verification, found it was because of 3e verification on zip files, so flashed the kernel with Odin to 2e.
After installing the kernel, ran the CM7 again and it ran fine, followed the instructions, wiped before installing CM7. The install looked like it ran fine, phone rebooted no problem, but it came back to a wiped Froyo still, didn't load CyanogenMod at all.
Anyway, there's no GMail app, and only Market, and Market wont let me add a Google account even if I say yes to the prompt. Looked round the SGS forums, didn't see anything like this.
I'm guessing I did something wrong, help someone?
Belahzur said:
it came back to a wiped Froyo still, didn't load CyanogenMod at all.
Click to expand...
Click to collapse
What do you mean by this?
Theonew said:
What do you mean by this?
Click to expand...
Click to collapse
I can only describe it as once I got to the step of rebooting the phone, it didn't load CyanogenMod, I was expecting the CM animation but I got my normal Froyo screen, does that make sense?
Probably a bad download. Delete the download and do it again. But just a word of advice...ROM's come with kernels, so if you flash a kernel first and then a ROM, you are going to lose the first one you flashed.
Thanks lowandbehold, one problem though.
I wiped the phone following the instructions, so I don't have ROM Manager anymore and can't open the Market, it asks me if I want to sign in with a Google account, I hit yes and nothing happens.
Ideas?
Sorry for double post, looks like I made some progress possibly.
Got the CM7 animation on boot, but doesn't go any further.
Got Clockworkmod recovery up though, flashed speedmod kernel, and CM7 initial kernel through ODIN.
Now in recovery mode when I go to install "update-cm-7.1.0-GalaxyS-signed.zip" I get an error about assert failed, error in the zip, status 7 and aborts.
Did you make a nandroid backup of the stock ROM before you flashed? If so, try to revert back to that. If you didnt make a backup, do a full wipe...wipe data/factory reset, wipe cache, and go into advanced and wipe the davlik cache. Then go to install zip from SD Card and select the CM7 zip. You should also check the md5 sum of the zip file to see if it matches up to make sure the download was good. You will be able to figure something out, as long as you can get into recovery and not getting crazy cache errors your phone should be 100% recoverable. Maybe even try something that is not CM7...just keep at it.
---------- Post added at 12:13 PM ---------- Previous post was at 12:11 PM ----------
Also, standby on the kernel for now. Get CM7 up and running on the kernel it provides you with and then make a backup in CWM. Then you can try to change the kernel...if you have issues then you can just go to your CM7 backup.
Would the backup be a recovery-update.zip file in the \clockwordmod folder?
Belahzur said:
Would the backup be a recovery-update.zip file in the \clockwordmod folder?
Click to expand...
Click to collapse
No, it's in recovery/backup on the clockword recovery screen.. personally, I like Amon Recovery a lot better than CM. Clockwork doesn't wipe the cache as well good luck! Hope you get it working
Sent from my Evo 4G using Tapatalk.
kendallc123 said:
Clockwork doesn't wipe the cache as well
Click to expand...
Click to collapse
Fixed your spelling (bold). Anyways, do you have proof of this?
Theonew said:
Fixed your spelling (bold). Anyways, do you have proof of this?
Click to expand...
Click to collapse
Thanks haha, went back and fixed it too. I don't have solid facts about it, but I have read in multiple threads that
1) People love Clockwork
2) People say Clockwork doesn't wipe the Dalvik cache thoroughly and sometimes causes boot loops (I've never had one)
I have had some problems with Clockwork personally. But, this is just my opinion. Also, Clockwork doesn't recognize some zips that I try to flash while Amon does. Anyway, it's all your opinion, whatever feels better to you.
Related
So the current iterations of cwm seem to have trouble working reliably with the newer froyo ROMs, and koush's recovery (although seeming to work correctly) is quite broken. So......
please find below a new recovery package that should work for any ROM for the fascinate, mesmerize, or showcase.
This is a "red" cwm recovery, and it will work with both voodoo and non-voodoo installations.
cwm-recovery-ALL.zip can be flashed via any cwm recovery.
if you are using odin, then use the cwm-recovery-ALL odin (.tar) package.
updated 3/29 - thanks to GizmoDroid for help with fixing fix_permissions script and root permissions typo that screwed up nandroid restores
updated 3/30 - fixed 'umount' typo - actually *fixed* fix_permissions this time - fixed odin/heimdall recovery attachment
Thanks, I just installed it. I'd rather not have a broken clockwork mod.
thanks, will give this a try!
ok, so I flashed this in the old cwm and it does come up red, but also says CwM Voodoo Lagfix Recovery, is that right?
In what ways is the old cm broken with froyo? I haven't noticed any problems.
Thanks! Good to have a fully working recovery again.
renf said:
In what ways is the old cm broken with froyo? I haven't noticed any problems.
Click to expand...
Click to collapse
Yeah, I'd like to 2nd this question. I have DL30 and CW worked for me in setting that up. Granted, I haven't tried anything else after that, but I'd like to know too.
Well I've had weird things happen when flashing stuff (I was using the "new-cwm.zip") , seemed like data being written where it shouldn't be? Just flashing theme files or own stuff I want to add, and I've had the following stuff happen:
Nuked my radio, had an unknown baseband and calls would never work, fortunately Radio Odin fixed it.
Had some /data apps disappear. Had some /data/data disappear. On reboot had Setup Wizard pop-up, even though I still had my Google account registered.
Hoping this new clockwork is completely safe. I suspected that clockwork was responsible for my weird happenings, so data-wiped and haven't flashed anything, so far fine functioning.
Using this is it easy to flash back to a prior set up, for me it would be back to dj05 w superdark and voodoo5?
Ive been holding off on froyo bc I need wireless tether, preferably unreported tether. But I really want to play around and see what the fuss is about. Ive downloaded every dl30 rom, havent installed one fearing I cant go back easily
Sent from my SCH-I500 using XDA App
/data on the fascinate is on /dev/block/mmcblk0p1
koush's recovery mounts /data as mmcblk0p2 (THIS IS OUR /DATA/FOTA. THAT'S BAAADDD)
under most circumstances this does not matter , because recovery.rc mounts data CORRECTLY before cwm gets to it, but there are circumstances where /data can be unmounted and then remounted, in which case cwm is gonna mount mmcblk0p2. If things get written there, at best you've got a **** load of FC's to deal with. At worst, a dead radio.
I've pointed this out to koush before, but was met with a "half-response", and to date it not been addressed (except for the recoveries that I've posted)
installed. When I go to do a backup, it gives the messages below. Backup seems to run fine though
E: missing bitmap progress_empty (code -1)
E: missing bitmap progress_fill (code -1)
Click to expand...
Click to collapse
Thanks, jt.
Copied to sdcard, booted into recovery, ran the program, keep coming back to green, no red.
ETA: Interesting. If I go to recovery from ROM mgr and try to load from sdcard, it does nothing, but if (while in ROM Mgr) I load from SDcard, it works. Got the blue screen, ran update, red appeared.
I likewise get the error message mentioned previously, but got it at install. Backup seemed to ahve run fine.
Installed like a charm, thanks jt!
sent from my fascinating XDA App
jackmei2 said:
thanks, will give this a try!
ok, so I flashed this in the old cwm and it does come up red, but also says CwM Voodoo Lagfix Recovery, is that right?
Click to expand...
Click to collapse
Yes, that is correct. It says in the OP. But it may have been edited since the time you posted and my response, so I'll let it slide
thank you JT!!!!! I thought it was just me, Ive had to start over again with my data about 6 times now becuase of Clockwork either not restoring my backups or my phone freaking out once I restored the backup. Thanks again!!!
beenz said:
Yes, that is correct. It says in the OP. But it may have been edited since the time you posted and my response, so I'll let it slide
Click to expand...
Click to collapse
haha thanks... but he said it will be red and that it is not for voodoo, so that's what I wanted to double check since it does have the voodoo menus and all.
superchunkwii said:
Yeah, I'd like to 2nd this question. I have DL30 and CW worked for me in setting that up. Granted, I haven't tried anything else after that, but I'd like to know too.
Click to expand...
Click to collapse
Lets see:
Broken mass storage function.
Broken data mounting function.
Couldn't wipe properly because of the above.
adrynalyne said:
Lets see:
Broken mass storage function.
Broken data mounting function.
Couldn't wipe properly because of the above.
Click to expand...
Click to collapse
The couldn't wipe properly bit me once already. Glad to have a proper recovery.
Sent from my SCH-I500 using XDA App
Thanks very much for addressing this issue.
For a while, I felt like a fresh n00blet, wondering what I was doing wrong. I tried flashing versions of supposedly compatible cwm's in different ways, always coming to the mounting errors.
Other than the errors from the missing graphics, this one works error free.
Scared to mess with this since i haven't experienced any problems with my current cwm stuff from pre dl09... Might just go ahead and do this tomorrow. For some reason I feel more comfortable using the odin method, so I can do all this over my Super Clean 1.0 with Neon GT theme and not have to do any data wiping or anything first?
So this makes no sense and I think its a weird coincident but as soon as I flashed this my beta version of swype started the force close loop..
EDIT: so weird, I had to uninstall the installer and swype itself using titanium backup and then download the installer and install again (had to do it all twice). Seems to be working again now tho..
Superclean 0.7.. aka Froyo.. Thanks devs!
Flashed .3 of Cherry Pi, and get stuck in a bootloop.
According to the first post on the thread, I have everything required.
Went back to my Nandroid backup of CherryBlur 1.4d.
I read one person had the problem and updated his CWM, but I'm already on the latest one from Tenfars thread, from 6/30. Is there another one I didnt see?
Thanks
ydgmms said:
Flashed .3 of Cherry Pi, and get stuck in a bootloop.
According to the first post on the thread, I have everything required.
Went back to my Nandroid backup of CherryBlur 1.4d.
I read one person had the problem and updated his CWM, but I'm already on the latest one from Tenfars thread, from 6/30. Is there another one I didnt see?
Thanks
Click to expand...
Click to collapse
Did you wipe the cache & data?
im having the same problem. just flashed cherryPi and now my phone is stuck in a bootloop. tried factory reset and still doesnt work.
Try to do a full wipe FIRST, then reflash the rom. Also, make sure you're not flashing from Rom Manager. If all else fails, PM the developer and he'll respond (or if he's not signed on try asking some other dev--they really are all eager to offer help, as long as you're patient).
~ Sent from My Unlocked, Rooted, Pie-Crusted Atrix 4g ~
Vangelis13 said:
Did you wipe the cache & data?
Click to expand...
Click to collapse
It was my understanding during the ROM flashing process, it would do all that. I'll try that again though.
Try to do a full wipe FIRST, then reflash the rom. Also, make sure you're not flashing from Rom Manager. If all else fails, PM the developer and he'll respond (or if he's not signed on try asking some other dev--they really are all eager to offer help, as long as you're patient).
~ Sent from My Unlocked, Rooted, Pie-Crusted Atrix 4g ~
Click to expand...
Click to collapse
Flashing from Tenfars CWM. I had wanted to post in the dev thread, but not enough posts yet . Especially since one other person was having this issue...he fixed it by 'updating to latest CWM' .. which I believe I am on.
Thanks. I'll do a full wipe then flash. See if htat helps any.
So I asked the other day about which rom would be best for a noob like me, in this thread to be exact: http://forum.xda-developers.com/showthread.php?t=1483712 and although most said Eclipse, I had a few people saying CM7 since it is based off of 2.3.4 and I would not have to SBF to try it and so on... So that sounded good to me and I made up my mind to try out CM7 and start out the easiest way possible, heh. So I got started and was following the instructions here: http://forum.xda-developers.com/showthread.php?p=21342515 downloaded all the files and what not and sat on them for a day before trying anything... cause I was sure I would screw something up... and I feel like I have...
So heres what I did. I read number 1 was NANDROID BACKUP! So I go to this link: http://forum.xda-developers.com/showthread.php?t=1318083 which says to perform a backup I must be rooted. Now this conflicted with the original thread I had read, but I went ahead and rooted it anyways. Followed the instructions here: http://forum.xda-developers.com/showthread.php?t=1315711 and everything went fine. I rooted my phone. But I was already worried because I am not sure if I was supposed to do some kind of back up before rooting... but its a little late for that now.
So now that I am rooted I go back to the original CM7 thread and go ahead and perform the backup which goes fine. Now, at this point I assume I move on to number 5 on that list, because I shouldnt have to root again, correct?
So number 5 states: 5. Put both the Google Apps zip, the CM7 zip, and dragonzkiller's patched BSR apk on your EXTERNAL sd card. I go and get my files and put them on the External SD card (or so I thought). I then move to number 6 that says go into Bootstrap recovery, which I do fine, then move on to the next one that says Install CM7.zip but I cant find it. I see google apps and tethering but nothing about just CM7.zip. Go back to later in the post under downloads and make sure I have everything that is there. I made sure all of this is on my EXTERNAL SD card:
Patched BSR APK for ALL versions of CM7DX2
Google Apps (market, maps, YouTube, etc.) MD5 Sum: e4313eb28b65758bff0cf63bc1a404f5
Tethering Patch for CM7DX2-beta1
REFLASH THE GAPPS AFTER UPGRADING IN CASE OF FACTORY RESTORE
Cyanogenmod 7 for the Motorola Droid X2 - BETA MD5 Sum: 789f25244e475901048e0d0e5908b5a4
I try to click the Patched BSR file, but it doesnt install anything, so I go to install the google apps and tethering assuming CM7 is in there some where... reboot and get stuck in a boot loop. Yeah, I am surprised too I am learning what all these terms mean, lol.
So I didn't know what to do, so I ripped off my Otterbox case and pulled the battery and went back and found this thread: http://forum.xda-developers.com/showthread.php?t=1318083 and I performed a restore and got my phone to boot back up.
So this is where I am now. I really don't know where to go from here. Am I still rooted? Did I screw up by rooting first? The instructions were really confusing for a noob and I tried to make sure I knew what I was doing before I started and I still managed to screw it up. I am not really worried that I screwed up the phone... seems to be working fine as is, and if I am stuck I guess I can just leave it like this till November when I upgrade... But I would really like to get some help and see if anyone out there could hold my hand and get me thru this and let me know where I went wrong. I am up for continuing... but I need to be clear before I do anything else. I know this is a lot to ask, but if anyone can help I would greatly appreciate it... Thanks so much for your time if you made it this my rambling...
Well first of all do you have Superuser in your app tray?
Sent from my DROID X2 using xda premium
You did a data wipe in android recovery! If so you need to reroot
Then install our bootstrap recovery,
You already have the files on your card so find them in file manager, boot into bsr, flash cm7, while still in bsr flash gapps. Data/cache/dalvi= wipe
Reboot will take you into cm7, install the patched bsr. Apk inside some file managet program.... Enjoy
from my X2 roaming the north
I wasnt clear on if you got the CM7.zip file cleared up and got it to show up in recovery. That needs to be flashed first. The bootstrap.apk isnt installed in recovery. You install that after you get CM7 up and running. Just go to any file manager and click it. It should ask if you want to install it. The process should be, from stock android:
1. Root your phone
2. Install regular bootstrap (not CM7 bootstrap) EDIT: Actually I think this installs when you root. I dont remember, its been so long. lol. If not, find it and install it.
3. put zip files on your sd card
4. In Booststrap recovery, wipe data, clear cache and under "advanced", clear dalvik cache.
5. Flash CM7 zip FIRST, THEN google apps zip (Probably the tether patch here too, but I never did it so dont take my word on that.)
6. Reboot (CM7 SHOULD boot up)
7. Install the CM7 Bootstrap for future flashing.
You should be good after that.
Just to make things clear, the name of the CM7.zip is this:
update-cm-7.2.0-RC0-daytona-KANG-public-beta1.zip
So, when they say to install the CM7.zip file, that is the file you want to look for.
Here are the files you should have for CM7 and the order they need to be flashed in:
update-cm-7.2.0-RC0-daytona-KANG-public-beta1.zip (Again, this is the mentioned "CM7.zip" file)
gapps-cm7dx2-signed.zip (This is the Google Apps zip)
CM7DX2-beta-tether-patch-signed2.zip (This is the tether patch)
Once you are in CM7, that is when you want to install the MOTODX2_Bootstrap-CM7_signed.apk BSR.
iBolski said:
Once you've flashed those files, clear the cache/data reset and clear the dalvik cache (located in the Advanced menu under BSR) and then reboot.
Click to expand...
Click to collapse
I thought you were supposed to wipe data and cache and all that before flashing. Doesnt wiping it after flashing wipe the stuff you just flashed? Or does it not really matter? I always clear data/cache BEFORE flashing anything.
jsgraphicart said:
I thought you were supposed to wipe data and cache and all that before flashing. Doesnt wiping it after flashing wipe the stuff you just flashed? Or does it not really matter? I always clear data/cache BEFORE flashing anything.
Click to expand...
Click to collapse
You're right. Most of the time, you clear that out BEFORE you flash. I went ahead and removed that instruction so as to not confuse him.
Jubomime said:
Well first of all do you have Superuser in your app tray?
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Yes. I updated it as well.
Thanks everyone, I passed out this morning with the computer sitting on my lap, and just woke up... so I am gonna try to go thru your answers. Appreciate all the help!
Your restore has root. Since you used root to install the recovery, your backup includes the necessary files. Sometimes instructions can be confusing or worded oddly. Once you get the hang of it, it will be easier. First thing you should do is enter our recovery and format data, cache, and dalvic (in the advanced section), then flash your cm7 zip. After, flash gapps and tether patch. I like to put my zips in their own folder so I can find them easily.
Sent from my DROID X2 using xda premium
jsgraphicart said:
I thought you were supposed to wipe data and cache and all that before flashing. Doesnt wiping it after flashing wipe the stuff you just flashed? Or does it not really matter? I always clear data/cache BEFORE flashing anything.
Click to expand...
Click to collapse
Wiping only removes user apps. You can flash cm7 then wipe all day and you will still have cm7 that's why sbf's are necessary.
Sent from my DROID X2 using xda premium
Sounds like you used the patched bsr to try and flash cm7. That should be installed after cm7 is running on your phone. Should have used the unpatched bsr first.
Sent from my MB870 using XDA App
Yeah, I think I will be able to figure it out with all of your help. I have been busy and not had a chance to get to it yet... but I was wondering if I should start from scratch, un-root and re-root? I was not sure if that is necessary, but I am gonna try again this weekend and wasn't sure. I did want to ask, is it hard to un-root your phone?
kalojado said:
Yeah, I think I will be able to figure it out with all of your help. I have been busy and not had a chance to get to it yet... but I was wondering if I should start from scratch, un-root and re-root? I was not sure if that is necessary, but I am gonna try again this weekend and wasn't sure. I did want to ask, is it hard to un-root your phone?
Click to expand...
Click to collapse
SBFing will remove the root because it returns your phone back to stock. It's a complete wipe of ANY changes you've made to the phone.
If you want to ensure that you remove any traces of rooting, flashing, modifications, SBFing will do that.
Hey folks,
So the end of Q3 came with no ICS so I decided it was time to learn about modding these phones. I have modded Xboxes etc so I figured I would try to take this on.
My Phone:
AT&T MB860 bone stock with 4591 on it when I started.
I was able to unlock the phone following a tutorial on youtube. Then I tried to reflash CWM and CM7 using AUTOMATIC_UNLOCK_V4.2. Thats where things went wrong. The phone got stuck at the Dual core screen (to be honest I might not have waited 10 minutes after flashing).
So now here I am the battery is drained so I am using a cut off USB cable for power. When the phone is booting it says "unlocked" in the top left corner I can access all of the menus. When I choose recovery the phone boots into ClockWork Mod recovery. I am hoping I am half way there and the kind folks here can guide me to the finish. If not I'm open to starting from scratch whichever is going to be fastest. I'll attach a few pics for reference
Mycotopian said:
Hey folks,
So the end of Q3 came with no ICS so I decided it was time to learn about modding these phones. I have modded Xboxes etc so I figured I would try to take this on.
My Phone:
AT&T MB860 bone stock with 4591 on it when I started.
I was able to unlock the phone following a tutorial on youtube. Then I tried to reflash CWM and CM7 using AUTOMATIC_UNLOCK_V4.2. Thats where things went wrong. The phone got stuck at the Dual core screen (to be honest I might not have waited 10 minutes after flashing).
So now here I am the battery is drained so I am using a cut off USB cable for power. When the phone is booting it says "unlocked" in the top left corner I can access all of the menus. When I choose recovery the phone boots into ClockWork Mod recovery. I am hoping I am half way there and the kind folks here can guide me to the finish. If not I'm open to starting from scratch whichever is going to be fastest. I'll attach a few pics for reference
Click to expand...
Click to collapse
(I went through this today, I needed to use option 6 in automatic unlock 4.2 before I could get a Rom on my phone.) this was wrong, tried so many things I got confused, go to this thread:
[Unlocked Only][RECOVERY][2011-11-14] Custom CWM-based Recovery 5.0.2.7-atrix5 in ATRIX android development
and download one of the zipped recoveries, flash through recovery to get a modified CWM that left me install a Rom. I was stuck at the same screen as you before I did this now I'm up and running with MROM.
Your recovery is too old. Get a newer version of CWM. Try flashing this. If you can't you will have to fastboot flash a newer recovery.
Flash ROMs with CWM, not automated tools. CWM is the safest way. As soon as you get a new recovery installed create a backup. Good luck!
okay guys I'm jammed up I download the file CWM_Atrix4G_5.0.2.0 and copied it to a clean microsd. Then I went through the recovery menu
Install zip from sdcard>choose zip from sdcard>
In the next folder list I am unable to find the CWM file. Any tips on how to get the file straight onto the phones internal flash? Maybe through RSD?
Dude, you're trying to install recovery from the recovery... Doesn't really make sense, does it?
Use fastboot instead.
Avoid RSD at all costs.
ravilov said:
Dude, you're trying to install recovery from the recovery... Doesn't really make sense, does it?
Use fastboot instead.
Avoid RSD at all costs.
Click to expand...
Click to collapse
You can't do a first install of recovery from recovery. But you can update (assuming recovery is functioning - even partially).
upndwn4par said:
You can't do a first install of recovery from recovery. But you can update (assuming recovery is functioning - even partially).
Click to expand...
Click to collapse
Yeah, I know. You posted a flashable ZIP, the only one I am aware of.
I'd still recommend a standard fastboot flash though.
ravilov said:
Yeah, I know. You posted a flashable ZIP, the only one I am aware of.
I'd still recommend a standard fastboot flash though.
Click to expand...
Click to collapse
Huh? The only one? Did you search?
upndwn4par said:
Huh? The only one? Did you search?
Click to expand...
Click to collapse
No... Not really.
Hey, I said "that I'm aware of".
ravilov said:
No... Not really.
Hey, I said "that I'm aware of".
Click to expand...
Click to collapse
I have flashed recovery with fastboot exactly once - when I unlocked by bootloader. Ever since it has been flashable zips.
Okay I successfully flashed the new recovery to v5.0.2. Then I chose "apply /sdcard/update.zip" I received the "Install from sdcard complete message" I then chose "+Go Back+" then "reboot". The phone rebooted and sat at the logo with "unlocked" in the corner for a few minutes. I thought maybe I needed to clear it by pulling the battery for a few seconds, which I did. then I let it sit on my desk for 20 minutes at the logo screen.
do need to go in and clear cache? is there another file I should try to flash?
Any input would be appreciated.
Mycotopian said:
Okay I successfully flashed the new recovery to v5.0.2. Then I chose "apply /sdcard/update.zip" I received the "Install from sdcard complete message" I then chose "+Go Back+" then "reboot". The phone rebooted and sat at the logo with "unlocked" in the corner for a few minutes. I thought maybe I needed to clear it by pulling the battery for a few seconds, which I did. then I let it sit on my desk for 20 minutes at the logo screen.
do need to go in and clear cache? is there another file I should try to flash?
Any input would be appreciated.
Click to expand...
Click to collapse
You probably need to re-flash your ROM.
Wipe data, cache, Dalvik, then flash ROM.
upndwn4par said:
You probably need to re-flash your ROM.
Wipe data, cache, Dalvik, then flash ROM.
Click to expand...
Click to collapse
I ran the wipe, cache, davlik then reran the update.zip.
I am still stuck at dual core screen with unlocked the corner.
Mycotopian said:
I ran the wipe, cache, davlik then reran the update.zip.
I am still stuck at dual core screen with unlocked the corner.
Click to expand...
Click to collapse
Umm... That would just install the recovery again. You need to flash a ROM. Seems like your boot partition (aka. the kernel) is borked.
ravilov said:
Umm... That would just install the recovery again. You need to flash a ROM. Seems like your boot partition (aka. the kernel) is borked.
Click to expand...
Click to collapse
Success!
Thank you to everyone that helped.
Now that its done is there a link to outline what all my new perks and features are now that I am rooted and running?
Mycotopian said:
Success!
Thank you to everyone that helped.
Now that its done is there a link to outline what all my new perks and features are now that I am rooted and running?
Click to expand...
Click to collapse
I just installed CM7 on my Atrix last week. Don't forget to install gapps like I did. I had to install them as a zip from the recovery, but I think it's also possible to use the ROM Manager app.
Look for the Google Apps section on this thread: forum.xda-developers.com/showthread.php?t=1257574 This will have the Market (now Google Play) so you can download more apps.
After that, play with all the features! I started with Menu > Settings > CyanogenMod Settings and started playing around. Don't play with the performance settings without knowing what they do.
Also, Make a backup! Make a backup! Make a backup! It may save you when little else will.
Sent from my MB860 using xda app-developers app
Mycotopian said:
Success!
Thank you to everyone that helped.
Now that its done is there a link to outline what all my new perks and features are now that I am rooted and running?
Click to expand...
Click to collapse
Awesome! Enjoy!
Hello all, I want to install Clockworkmod on my Samsung Vibrant T959 so I can install a custom ICS ROM. I ran into some problems along the way. I can not seem to install CWM correctly. I had the phone under Froyo 2.2, kernel version 2.6.32.9, and build number froyo.uvkb5. After flashing the recovery by ROM Manager, I would still be stuck at the stock recovery. I have the correct files to download:update.zip. After clicking on "reinstall packages", the recovery said "replacing stock recovery with Clockworkmod recovery". The problem is that after that message, the phone restarts into the stock recovery. I tried it 4 times in a row, but I'm still stuck at the stock recovery. The system keeps saying that it will replace the stock recovery with the CWM recovery, but that did not happen with me. I would keep getting the same message when I click on "re install package". What am I missing that does not allow me to do this? Thanks all.
Are you on 2.1 eclair or 2.2 froyo?
I'm pretty sure you need to be on 2.1 but don't quote me.
Also, I believe there is an issue with the newer versions of ROM manager, recovery mismatch. (Again don't quote)
I haven't had to mess with that stuff in a long time. Either way I'm posting a link that will help you along. If you have any more questions just shoot.
http://forum.xda-developers.com/showthread.php?p=9375927
Paranoid, sitting in a deep sweat...
Thanks for the reply. Like I said in my last post, I am running at Froyo 2.2. I already bricked my phone for failing to downgrade to 2.1. I already rooted my phone, my problem is that I could not install CWM correctly by the stock rom. After the message states that it is replacing the stock rom, my phone goes back to stock with no changes.
woodrube has some great guides, I use the update.zip method, rom manager didnt like my phone, post if you still have problems and Ill give you more accurate directions on guides.This is probably heresy, but i never could get rom manager, even pro to do what I wanted,and Im sure it was me.
Your positive you dont have a 4g?
Sugartibbs said:
woodrube has some great guides, I use the update.zip method, rom manager didnt like my phone, post if you still have problems and Ill give you more accurate directions on guides.This is probably heresy, but i never could get rom manager, even pro to do what I wanted,and Im sure it was me.
Click to expand...
Click to collapse
You do not understand, I am having the problem that CWM could not install properly. When I chose "install packages" the steps went by and ended with "Replacing stock recovery with CWM recovery". Usually, that would jump straight into CWM recovery after it's installed. That did not happen to me, After installation, my phone restarted and booted back into stock recovery. I tried installing again but I always go back to stock recovery and not Clockworkmod recovery as I planned.
Ive never seen that error message, I know its frustrating, but the t959v 4g comes loaded with Froyo 2.2,the a 2.1 eclair odin will brick it.Just trying to help.
Go back to 2.1, uninstall ROM manager, use the update zip in the guide link I posted.
Paranoid, sitting in a deep sweat...
---------- Post added at 11:06 PM ---------- Previous post was at 10:44 PM ----------
In the link I sent is the AIO toolbox download. There is a guide how to use it in this link. The DL links are dead in this one so get from previous.
Paranoid, sitting in a deep sweat...
IIRC the update.zip method does not work in Stock 2.2 because of the 2e and 3e recovery mismatch. If you to go to 2.1 Eclair, then you can use the update.zip method and then flash your ROM of choice after that. If you decide to stay on 2.2, you'll have to get the 3e method. It is in the Development section, so you'll just have to search 3e and it should come right up.
All this is provided you have a T959 (3g) and not a T959v (4g). Sorry but lately there have been many 4g users flashing our ROMs and then freaking out.
You can also find a bunch of files in my Repo thread stickied in the Dev section.
samsgun357 said:
Go back to 2.1, uninstall ROM manager, use the update zip in the guide link I posted.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Maybe you'll get it now.
Good luck.
@Woody, thanks buddy.
I linked your repo thread in my previous post.
Edit: well the link isn't in my posts, must not have sent??? But here it is
http://forum.xda-developers.com/showthread.php?p=31279153
Paranoid, sitting in a deep sweat...
Click to expand...
Click to collapse
The first thing you need to do after obtaining root is flash a kernel. You can't install a rom from re-install packages. That has to be done in a custom recovery, which is built into the kernel. Easiest way to do that is download a kernel and flash it with sgs kernel flasher. I would suggest immortality kernel. After that you can go into the custom recovery and flash your rom of choice.
nfkod said:
The first thing you need to do after obtaining root is flash a kernel. You can't install a rom from re-install packages. That has to be done in a custom recovery, which is built into the kernel. Easiest way to do that is download a kernel and flash it with sgs kernel flasher. I would suggest immortality kernel. After that you can go into the custom recovery and flash your rom of choice.
Click to expand...
Click to collapse
^^ this is not true.
I had a issues with my apps doing the same thing. I had to get busy box and install a older ver 19.2. It corrected the issue. Updating superuser caused my headache
Sent from my SGH-T959 using xda premium
naturallight said:
I had a issues with my apps doing the same thing. I had to get busy box and install a older ver 19.2. It corrected the issue. Updating superuser caused my headache
Sent from my SGH-T959 using xda premium
Click to expand...
Click to collapse
I have no idea what you are talking about?????
Paranoid, sitting in a deep sweat...
If you have the proper xda version of update zip on your sd...,, theres no need for a kernel flash.
I have the same exact issue as the original poster. 2.2 froyo and all. I even replaced my stock 3e recovery with the modded one, but I get the same issue. Says its flashing CW recovery but it always reboots and comes back with the stock recovery. What exactly are we doing wrong?
Follow steps in this guide, update.zip b is probably best but you need to Odin back to stock first.
http://forum.xda-developers.com/showthread.php?p=9375927
Alright so I managed to get CWM on my 2.2 Stock Vibrant and even got it permanently. What I did was download SGS Kernel Flasher and install it. Then I went the Samsung Vibrant Kernel Bible and found the stock kernel with Voodoo lagfix included that matched my phone (because the kernel has CWM built in) downloaded it, and placed it on the root of my card. Launched the app, backed up my current kernel and then flashed the new one. Everything went smooth and then my phone rebooted and was stuck on the Vibrant screen for 20 minutes. I was pretty sure I messed my phone up. Also it was talking to me which I didn't realize at first, because I was expecting my phone to be talking to me! Finally made out what it said and it said something along the lines of not enough space on the partition, closing... It was hard to understand because it was in a robotic voice. It eventually rebooted and loaded up like normal. Checked the about phone but saw nothing different. So I decided to reboot to recovery just to check and sure enough, CWM 2.5.1.3 comes up, and comes up every time Finally, now to figure out what to do to get on a jellybean ROM
When I say Odin to stock that's 2.1 eclair. Voodoo lagfix will cause issues going to a JB ROM.
You don't need to try and re-invent the wheel.
Odin to stock 2.1 eclair JFD.
Put ROM on sdcard
Go to recovery, install update.zip from guide I linked.
Wipe and flash ROM.
It can't get much easier. I am not trying to come off as a ****, only to help you, and avoid future issues.
BTW, I saw your pm, I can't reply because it keeps crashing the app. If you go in and disable voodoo lagfix you should be able to flash PA without issue. It will take 3 flashes. You only need to wipe before the first flash. Wipe cache, dalvik cache, factory/data and format system in mounts and storage. If you get in a boot loop, pull battery then use button combo back to recovery. GB boots are not required.
samsgun357 said:
When I say Odin to stock that's 2.1 eclair. Voodoo lagfix will cause issues going to a JB ROM.
You don't need to try and re-invent the wheel.
Odin to stock 2.1 eclair JFD.
Put ROM on sdcard
Go to recovery, install update.zip from guide I linked.
Wipe and flash ROM.
It can't get much easier. I am not trying to come off as a ****, only to help you, and avoid future issues.
BTW, I saw your pm, I can't reply because it keeps crashing the app. If you go in and disable voodoo lagfix you should be able to flash PA without issue. It will take 3 flashes. You only need to wipe before the first flash. Wipe cache, dalvik cache, factory/data and format system in mounts and storage. If you get in a boot loop, pull battery then use button combo back to recovery. GB boots are not required.
Click to expand...
Click to collapse
QFT. Just yesterday I ran into the same problem as reported by the OP and a few others. I HAD to downgrade to 2.1 via JFD Odin. Then flash the update.zip. I then just downloaded ROM Manager to get CWM working. However, I did see in some instructions that sometimes even though you know you have CWM installed, it will still default to stock recover. I simply applied the update.zip again and it eventually fixed itself. Not sure what that was about, but I did see it in some instructions, and I experienced it as well.
nfkod said:
the first thing you need to do after obtaining root is flash a kernel. You can't install a rom from re-install packages. That has to be done in a custom recovery, which is built into the kernel. Easiest way to do that is download a kernel and flash it with sgs kernel flasher. I would suggest immortality kernel. After that you can go into the custom recovery and flash your rom of choice.
Click to expand...
Click to collapse
great help dude.i fixed finaly."""""thanks"""""