all right I have been running ICS roms since passion v6ish. Tried Miui, cm7 and eugenes gingermod with no problems. The other day I decided I wanted to try Slim-ICS. It looks nifty. I flash the base.zip then vibrant essentials and get a boot loop. ok no big deal I go back to clockworkrecovery and it is now wome sort of touch based recovery. I attempt to restore my nandroid of the most recently working CM9 build I was running. Hangs at boot animation.. I tried flashing other ICS roms that I had used previously to no avail. I have tried every which way I can read to wipe data/factory reset, wip dalvik, cache partition boot and data. I gots nothin can not get anything to work. Now I try using vibrant toolbox to odin back to stock. no problemo. Rooted using update.zip and installed cm7. No problemo. Tried to install an ICS rom again and still nothing. I have odines at least 12 times and tried different ways to root, install recovery and flash an ICS rom and am not having any luck. I tried flashing the GB bootloaders through odin a few times with no success. I have been glancing over at kangs pink unicorn for sometime now.
Was I wrong in believing that flashing CM7 means I now have GB bootloaders?
Now that I have flashed aokp again when I boot I still see the cyanogen mod splash screen before I see the team kang boot animation....this strikes me as odd.
No, flashing CM doesn't mean you have Gingerbread bootloaders. I don't understand were you able to install AOKP after all? Regarding CM kernel boot screen before aokp boot animation, it is because Aokp uses CM9 kernel.
I had tried passion, euphoria and CM9 before I decided to try slimics and everything got borked from there. Currently running CM7.
So odin the GB bootloaders like in this thread no more failing at life right?
Here goes...
Thanks for the emotional support. Currently running Slim ICS.
It sure was strange using GB for a day...
Double noob I guess posting a q here.
Related
I flashed the 6/09 build of jt1134's CM7 fascinatemtd ROM on my girlfriend's Fascinate, and the absolutely loved the improvement over stock. There were a few noticeably bugs, such as the sensor issue, so now I'm trying to flash the 7/07 update.
Booting into CWM Recovery, wiping, and installing the zip isn't working. It installes the bootloader (I get the Galaxy S/Cyanogen Mod boot image) but it keeps running an installer and boot looping. It looks like the assert error, but it's too fast to tell for sure.
I've had to keep restoring to EB01 Froyo stock with Odin, and starting the process over again (root, recovery, CWM, wipe, attempt flash.) Still no success. I've used both the orange and red CWM recoveries without success. Any help?
When you go back to eb01 are you also using the atlas 2.2 pit file
With re-partition checked?
Also you have to use the recovery in jt1134's original post...I believe there is only cwm one...possibly two your supposed to use and its in the same post... its yellowish orange color and I'm also pretty sure its a 4.x.x.x version not 3.x.x.x if that's what you've been trying to use that's probably the problem
rickatnight11 said:
I flashed the 6/09 build of jt1134's CM7 fascinatemtd ROM on my girlfriend's Fascinate, and the absolutely loved the improvement over stock. There were a few noticeably bugs, such as the sensor issue, so now I'm trying to flash the 7/07 update.
Booting into CWM Recovery, wiping, and installing the zip isn't working. It installes the bootloader (I get the Galaxy S/Cyanogen Mod boot image) but it keeps running an installer and boot looping. It looks like the assert error, but it's too fast to tell for sure.
I've had to keep restoring to EB01 Froyo stock with Odin, and starting the process over again (root, recovery, CWM, wipe, attempt flash.) Still no success. I've used both the orange and red CWM recoveries without success. Any help?
Click to expand...
Click to collapse
Sent from my SCH-I500 using XDA App
^ what he said, also here's a link on how to use the pit eith full instructions: http://forum.xda-developers.com/showthread.php?t=1124391
The 7/7 update seems to need the 7/4 release to work. It has an updater script that runs off of previous installations. Try flashing the 7/4 than the 7/7.
Beware that people are reporting that outgoing audio gets broken in the 7/7 release and you will have to flash the 7/4 otb kernel after the 7/7 release if you have any issues.
I did, indeed, use the PIT file with partitioning enabled, whenever I restored the phone. The directions I followed were pretty firm about that..
I didn't see anything about the 7/07 release being an update for 7/04, but that would make sense. I'll try that now and post results shortly. Thanks!
The 7/04 update flashsed successfully! I'm still nervous about 7/07, so I'll probably wait for the next update. Thanks for the help!
omg thank you so much..here i was trying to use the 7/07 update..i tried like 60 times literally..thanks man
I'm now running the nightly builds on my girlfriend's (now fiance's!) phone, her sister's phone, and her mom's phone all without a hitch. (I just had to update the radio to fix SM and MMS.) I'm thinking about switching on of them to MIUI to see if they like it better, but so far everything's good.
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.
I previously had stock Eclair 2.1update1 and flashed through CWM to Bionix-v 1.3.1 which I'm currently running. Now I want to know if I could flash CM 7.1.0.1 directly without Odining to stock. My current CWM is 2.5.1.3 and I don't want to mess with Odin or bootloaders. Is it Ok to flash CM7.1.0.1 with CWM from my current Bionix?
Yes. When you do it, make sure you flash CM7, IT WILL BOOTLOOP, this is normal. Pull the battery, boot back into recovery and then reflash CM7 again. Essentially flashing over itself. It does this bc of a CWR mismatch.
If you are going to go to CM7, why not go to Neo's ICS? Check it out. Very smooth, little bugs, RC came out today and plenty of support (CM team dropped Vibrant so no support from them. Us yes, them no).
Woodrube said:
Yes. When you do it, make sure you flash CM7, IT WILL BOOTLOOP, this is normal. Pull the battery, boot back into recovery and then reflash CM7 again. Essentially flashing over itself. It does this bc of a CWR mismatch.
If you are going to go to CM7, why not go to Neo's ICS? Check it out. Very smooth, little bugs, RC came out today and plenty of support (CM team dropped Vibrant so no support from them. Us yes, them no).
Click to expand...
Click to collapse
Great! I'll give it a try soon.
And yes, I've been following Neo's ICS thread actually. But I'm proceeding slowly as my internet bandwidth is very limited, I live in the third world, so... For now I've got the CM7 ROM and planing to give it a shot.
Another thing I read in Neo's OP instructions is that one can get to flash his ROM going through CM7, even without flashing GB bootleaders with this route. I still can't understand the difference CM7 does make for not needing them, and I wonder why. But well... I think is one step at a time.
Thank you very much Woodrube.
Just reporting that my cm7 flashing was successful and everything went as expected. Good.
I'm now a happy cm7 user.
I'll keep an eye on ics...
Hi I am new to the whole modding scene.
My girlfriend is tired of having her phone freeze and lock up, so I decided to load a nice Jelly Bean rom on it for her. She has a Verizon Samsung Fascinate.
I followed this tutorial here:
http://www.youtube.com/watch?v=mDH8NWyikJM
That I found on this roms site www.hellybean.com
I downloaded the 9/25 build.
I followed the tutorial, got it rooted, installed the teacmhacksung.... rom. rebooted and installed the hellybean rom. rebooted, reflashed hellybean again as it says to do. then installed the latest gapps 20120706 signed.zip
rebooted then it went all haywire. It shows the boot logo for hellybean for a split second then keeps booting to the devil recovery menu,:crying: no matter what i do.
I found a tutorial (http://forum.xda-developers.com/showthread.php?t=1238070) section 9.
I followed it until the second time I had to install the cm7 rom. after the second flash it keeps showing the boot menu for cm7 then 2 secs later it reboots constantly.
Good news is that I can get into CWM recovery with no problems (so glad I dont see devil recovery anymore lol )
I dont know what to do from here. I do have a backup but it is at the time of the infinate devil recovery situation, so that wont help me.
Any help at all would be greatly appricated, hell i would be ahppy with going back to stock if possible but I really want to see jelly bean on this thing
Thanks in advance!!
Chris
Not sure what could have happened there, you seem to be on the right track with following directions. I would Odin back to stock and try a different JB rom, such as AOKP or CM10, just follow droidstyle's guide on how to do that step by step.
Crawshayi said:
Not sure what could have happened there, you seem to be on the right track with following directions. I would Odin back to stock and try a different JB rom, such as AOKP or CM10, just follow droidstyle's guide on how to do that step by step.
Click to expand...
Click to collapse
I got it working no problems now. I used odin to go back to stock, re-rooted, and used AOKP 9/25 rom. It runs great, but the pink swagger unicorn has to go. What are some good sites to find boot animations? also are theme packs avaliable for this rom? I see the default 1/1 in the rom manager but nothing else is installed yet.
Thanks for the help
You can disable the boot animation in the rom settings...
As for themes, CM10 themes should work the same. Go here: http://forum.xda-developers.com/showthread.php?p=29455970#post29455970
Also, upgrade to 9/27 because it has the new partition layout with much more internal storage. It runs great with Devil Kernel 1.6.0. That's what I'm on now and it's fast as hell
I have a vibrant with Asgard Version 3.1.2 installed. How do I upgrade that to a jellybean rom? The problem is changing the partition from bml to mtd and I haven't done this for a long while and I only did it on a Galaxy S 4g, not a Vibrant. I remember I had to get version 3 or above of CWM for the 4g when I upgraded it to jb long ago. I never got the Vibrant past Asgard because the phone belongs to an ex-girlfriend and I haven't worked on her phone for over a year.
I tried flashing a kernel that had version 5 something of CWM on it (99 problems) but although I was able to flash it and the jb roms seemed to be loading, every time I rebooted it would only go to recovery and the new rom would never boot up. Reflashing Asgard with Odin didn't work, I kept getting the lady Sandra saying there was not enough space on the card to convert it to lagfix and it has been a long time since I ever had to deal with her at all. I was able to Odin a stock Froyo rom and it now boots up to the old grassy screen with the bloatware.
I suppose if a Vibrant works like a 4g I'll now be able to reflash Asgard but maybe that is not what I am supposed to do. You guys have so many roms and kernels compared to the 4g forum that I'm kind of lost trying to deal with this phone. I have not had to convert from bml to mtd for a long time. The phone I have came with an odin version of jb that got around all of that crazy stuff.
I remember using the Vibrant toolbox a long time ago as part of the upgrade, but the link now points to a page that isn't there any more.
Go here http://forum.xda-developers.com/showthread.php?t=849028 and use Odin to flash back to stock JFD, which is 2.1 not 2.2. After you flash to stock, use update.zip B from the link above to get CWM (clockwork mod recovery), you have you reinstall packages twice for it to work FYI. To flash to Jellybean from stock you must flash the ROM twice as well (important), the first flash just upgrades your CWM recovery. It will reboot to Jellybean CWM (blue), just flash the ROM again and you will be good to go. Remember to follow the devs install instructions, it's usually wipe data/factory reset, wipe cache and dalvik cache then flash the ROM and fix permissions. My favorite Jellybean ROM is Avatar in case you want a suggestion, tons of themes and very stable, I prefer Semaphore kernel as well, both can be found here http://forum.xda-developers.com/showthread.php?t=1982728.
Sent from my SGH-T959 using Tapatalk