I've been trying to load a new rom onto my fascinate sch-i500v for a few hours now. I previously had a 4.1 build (milestone I think) and cwm 4.0.1.0 installed. I've tried every rom from cw10 to hellybean to avatar and they all do the same thing. I wipe the cache, factory reset. Then installed from the zip file. At this point, the install starts to initiate, but the phone suddenly reboots and after a few seconds tries to load up the old rom (unsuccesfully, hence why I said I'm seeing the "initiating swagger" load screen forever)
Yesterday, I did this exact upgrade successfully to my other fascinate sch-500 (no v on the end for that one, not sure if that makes any difference).
That one rebooted suddenly as well, but it went back into the clockwork recovery and completed the install without a hitch.
Anybody have any suggestions? I'm sort of a noob, but I have flashed over ten phones...
Go back to stock and start over
Sent from my SCH-I500 using Tapatalk 2
bbrad said:
Go back to stock and start over
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
Thank you. i fugured that was what I needed to do, but I was afraid of how complicated it would be. LMFAO, it was pretty simple!
Related
Hey guys. I've been an Android & XDA user for a while now, so this question shouldn't be about a nooby-sitiuation.
My friend bought an AT&T Samsung Galaxy SII (SGH-i777) this week. I've been trying to flash CM7 ever since. I got the rooting done, the properly recovery (with no signature / "abort" problems)
The rom seems to keep bricking the phone. Its simply unflashable. I seen tons of people on XDA who got it to work, with barely any serious problems. I troubleshooted the problem myself, and its simply just the CM7 roms. I would do a full wipe, and then install the rom like I would on my other Android phones, and the installation is successful. When it boots, it gets stuck on the Galaxy SII boot screen (not the splash/boot animation screen) and it would stay on it with a yellow warning triangle on the bottom.
I tried flashing other roms, like Cognition X2, and they worked. Its just CM7 on this phone... which is odd because CM7 is usually stable (nightlies aside.) Especially since the 7.1 stable version was recently released. Anyone can help me get the rom up and going? Would be highly appreciated.
did you try to wipe dalvick cashe as well when you wiped data?
I just flashed it tonight myself and all I did was reboot into CWM and did a Wipe data/factory reset and then Wipe cache partition. After doing that, I simply flashed the cm7 zip file that was loaded on my internal sd. Rebooted and no problems.
I didn't have ANH ISSUES installing it but I know I read that some.people bad to flash it twice initially. So flash it, then when it goes back to the recovery screen flash it a second time. I also remember users on the international SGS2 bad to do the same thing. Most have no issues but I think they found that it depends on what you used to root your phone (on the SGS2 internationals) and I THINK some had to do the same here. Try it and if it works just hit the thanks button.
Sent from My KickAss CM7 Galaxy S2
if you flash it and get stuck in a bootloop, just pull the battery, and 3-finger back into recovery to flash the rom again.
keep doing this until you get it up and running - took me a few times, including a couple of battery pulls.
How do you boot into recovery? I know On the SGH-i777 you have to hold the Vol down+back+power to get to the Download mode, but I tried everything to get to the recovery itself.
Boobie Watcher said:
did you try to wipe dalvick cashe as well when you wiped data?
Click to expand...
Click to collapse
Yes. I've flashed many roms before, this seems to be the only one I had ever seen a problem with.
mfpearson said:
if you flash it and get stuck in a bootloop, just pull the battery, and 3-finger back into recovery to flash the rom again.
keep doing this until you get it up and running - took me a few times, including a couple of battery pulls.
Click to expand...
Click to collapse
Word.
Edit: To boot into recovery vol up+vol down+power
Had the same problem. Read somewhere to install the ROM twice in a row in CWM without rebooting inbetween. Worked like a charm.
Thanks for the feedback guys. I'll try this in the morning once I get my hands on the phone again.
Saw this type of behaviour on occasion with cm7 on my aria. Sometimes caused by a bad download of the rom. Did you verify md5s ?
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Don't forget to do a master data clear /reset before trying to boot the new CM7 rom for the first time - clear out the old stuff. Works perfectly here.
Sent from my SGH-I777 using xda premium
I'm having the same issue. I'm getting signature errors when trying to flashCM7.1 stable. I've downloaded it two times now with the same problem. My question is, I'm trying to flash from on the phone itself, storing the zip in the download dir on the phone as I don't have an sd card. Will this even work? I've tried looking around and all I can find is flashing from an sd card. I can get one, I just haven't yet.
squigge said:
I'm having the same issue. I'm getting signature errors when trying to flashCM7.1 stable. I've downloaded it two times now with the same problem. My question is, I'm trying to flash from on the phone itself, storing the zip in the download dir on the phone as I don't have an sd card. Will this even work? I've tried looking around and all I can find is flashing from an sd card. I can get one, I just haven't yet.
Click to expand...
Click to collapse
That's the way I did it. Put the update in the same folder on the internal SD card. I can't even access my external SD card from CWM.
Sent from my SGH-I777 using xda premium
Hmm, I'm not sure what I'm doing wrong then. I did a factory reset, and wiped the cache and get the same thing. I know it wiped because now I have nothing setup on the phone when I boot normally. Suggestions?
Quit downloading the CM7 builds for the International Galaxy S II. They will NOT work. That is why it fails. Look for the Galaxys2ATT build.
Sent from my SGH-I777 using xda premium
I got the build by going to the cm7 website, looking by device, finding the galaxy s 2 and grabbing the stable one. So perhaps that is the incorrect one and I'll look closer for one that has att in it, whenever the site isn't going up and down. They seem to be having issues today.
Make sure you're installing the version located in this thread...
http://forum.xda-developers.com/showthread.php?t=1297568
Specifically this link
Double flash made it work. Thanks guys. + thanks for telling me how to boot into recovery lol. Great rom.
Sorry for the newb issues, it was the wrong version. I got the att version from the thread previously mentioned and that worked perfectly. Thanks!
Hi all
I'm not new to flashing but I'm new to flashing cm7.
I odin back to stock jfd eclair. Root and Install CWM 2.xxx. I downloaded the stable cm7 and I started flashing. (after I wipe data/cache of course)
IN recovery, it said finding package, opening package, then my phone processed a series of lines and reboot automatically. On the startup, it says VIBRANT SAMSUNG, then GALAXY S CYANOGEN(mod) then the same recovery screen with many lines. It moved too fast into another reboot I couldn't read what was on the screen. And it kept doing this for quite 10 mins now.
Is it normal? if not, what did I do wrong? I can get into download mode and odin back to stock but I did it last night and I couldn't think what i did wrong.
Please help!
Hmmmm..... seems a bit wierd, try going into recovery and wiping and reinstalling with a new download.
Sent from my Nexus S 4G using XDA App
stumpyz9 said:
Hmmmm..... seems a bit wierd, try going into recovery and wiping and reinstalling with a new download.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
No i don't think its a bad dl. I checked md5. I'm odin back to stock again now.
wavestar92 said:
No i don't think its a bad dl. I checked md5. I'm odin back to stock again now.
Click to expand...
Click to collapse
Try reflashing cwm when your rooted, may have not flashed right
Sent from my Gewgle Phone via XDA App
This happened to me also, I went directly back to recovery, 3 button, and reflashed. Worked the second flash for some reason.
Thanks. I turn it off, get into recovery again, and re flash it successfully
Same exact thing happened. I have no idea how many time I odened back to stock trying to figure it out.
I did as you guys said, as soon as that loop began, pulled the battery and got back into recovery. flashed again and worked just fine!
same thing happened to me...i got back into recovery...i noticed cwm updated to 5.0.2.8 then i reflashed and all good...when i tried to flash at first. cwm was 2.5 ..maybe thats the issued it wont flash on that...has to be cwm 5.0
anyway getting ready enjoy some cm7 on my vibrant...
so i succesfully put aokp on my friends fascinate, it booted fine, worked for like 3 months. today, i booted into recovery, nandroided, then rebooted into system and it worked fine. but later, i rebooted back into recovery, did nothing, then tried to boot back into system, but it just booted back into recovery. i tried restoring from the nandroid i made earlier, still no luck, tried flashing another rom, kept booting right back into recovery... i have no idea what the problem is. has anyone else had this and is there any way to fix it without odin as i dont have a windows handy?
Did you three-finger into recovery the second time? If you did, this is a known issue. You can't three-finger into CWM on MTD filesystems (CM7 or ICS) or you will bootloop. See Droidstyle's guide in the General section for instructions on how to escape.
I would seriously update your friends phone as a lot has changed with all the roms in 3 months. Heck, a lot happens in 3 weeks.
Sent from my SCH-I500 using Tapatalk
shelby04861 said:
I would seriously update your friends phone as a lot has changed with all the roms in 3 months. Heck, a lot happens in 3 weeks.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
bingo.....
Has anyone else had a boot loop problem with the new V of TWRP?? I'm running SOAv3 ROM and had ZERO problems, upgraded my twrp and had about a dozen restarts and freezes and then when I tried to boot into recovery, it boot looped. Fixed it with ODIN, then tried installing it fresh, and got the same thing. Went back to my older version and things are fine once again just wondered if this is isolated or just a known bug??
Yes its a know issue right now go back to the previous working version of twrp and wait for it to get fixed.Also be sure to check big Biff's twrp page before trying to update again to make sure everything is good.
Sent from my SGH-I717 using xda premium
Just update from Padawan V8 to SOA build 3. Was skeptical for a day or so but finally did it last night. Was just about to update to the New TWRP, thank fully I read through all those pages before I did, I usually don't. Saved me a head ache except I forgot to wipe cache's before installing the GAPPS, going to have to re-do that I believe to get the new camera functions from what I've read.
Demmonnixx said:
Just update from Padawan V8 to SOA build 3. Was skeptical for a day or so but finally did it last night. Was just about to update to the New TWRP, thank fully I read through all those pages before I did, I usually don't. Saved me a head ache except I forgot to wipe cache's before installing the GAPPS, going to have to re-do that I believe to get the new camera functions from what I've read.
Click to expand...
Click to collapse
you are correct Sir.....wipe caches and re-flash gapps.....g
psycoartwork said:
Has anyone else had a boot loop problem with the new V of TWRP?? I'm running SOAv3 ROM and had ZERO problems, upgraded my twrp and had about a dozen restarts and freezes and then when I tried to boot into recovery, it boot looped. Fixed it with ODIN, then tried installing it fresh, and got the same thing. Went back to my older version and things are fine once again just wondered if this is isolated or just a known bug??
Click to expand...
Click to collapse
How did you fix with odin? I can't get mine into the download mode to connect to odin. it just keeps boot looping?
whitebrw said:
How did you fix with odin? I can't get mine into the download mode to connect to odin. it just keeps boot looping?
Click to expand...
Click to collapse
Hold volume down and power ...it will go into download mode
Sent from my SGH-I717 using xda app-developers app
thanks but no thanks, when i do that it does the same thing as any other way of starting, just loops.
check out my post if you want.
http://forum.xda-developers.com/showthread.php?t=2202663
Ok guys I'm on stock rooted right now. Was on rls 7 hyper and the blue kubatan* rom and when rebooting trying mods it froze on custom splash. So I boot into twrp and wipe dalvik and cache. Reboot from twrp and no issues. Restore to stock no problem. Swap batteries on stock and boom custom splash. Went through wipe in recovery and fine but any reboot from stock tw goes straight to custom splash. Did the kernel get messed up or recovery what? Any ideas?
Sent from my SCH-I545 using Tapatalk 2
Fixed it by odin
Sent from my SCH-I545 using Tapatalk 2
oneandroidnut said:
Ok guys I'm on stock rooted right now. Was on rls 7 hyper and the blue kubatan* rom and when rebooting trying mods it froze on custom splash. So I boot into twrp and wipe dalvik and cache. Reboot from twrp and no issues. Restore to stock no problem. Swap batteries on stock and boom custom splash. Went through wipe in recovery and fine but any reboot from stock tw goes straight to custom splash. Did the kernel get messed up or recovery what? Any ideas?
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
I'm having a similar issue. I did a full wipe and installed Hyper Rls 7 and it was working great. I made no changes or flashed anything new, but when trying to reboot it gets stuck at the Samsung Custom screen. I've waited 30 minutes with no change. I wiped with CWM and reflashed the rom with the same results multiple times. Any ideas short of going back to stock would be appreciated.
rickt1152 said:
I'm having a similar issue. I did a full wipe and installed Hyper Rls 7 and it was working great. I made no changes or flashed anything new, but when trying to reboot it gets stuck at the Samsung Custom screen. I've waited 30 minutes with no change. I wiped with CWM and reflashed the rom with the same results multiple times. Any ideas short of going back to stock would be appreciated.
Click to expand...
Click to collapse
I don't think there is another way. I flashed numerous roms in hope of something that would work and no. Phone also ran hot like over 100°+ at idle or screen off and lagged bad when I did get it to boot. After flashing back to stock rerooting and restoring my backup it runs like brand new. Wonder is rls 7 is screwing with something?
Play it safe and go back to stock man
Sent from my SCH-I545 using Tapatalk 2
You must flash your Verizon loki kernel after you flash any rom, not all of the roms are loki'ed, so it will hang at the boot screen.
Thanks you...
TheAxman said:
You must flash your Verizon loki kernel after you flash any rom, not all of the roms are loki'ed, so it will hang at the boot screen.
Thanks you...
Click to expand...
Click to collapse
Doesn't apply to us or rom wouldn't have booted first time after install. And a quick wipe of cache boots it so can't be that issue thanks though
Sent from my SCH-I545 using Tapatalk 2
Wrong, it is a kernel issue, try another. I have seen it boot once, then hang the next. Whatever.
TheAxman said:
Wrong, it is a kernel issue, try another. I have seen it boot once, then hang the next. Whatever.
Click to expand...
Click to collapse
Then why would wipe cache make it work? & no issues before with it. Had to be a mod we tried to install
Sent from my SCH-I545 using Tapatalk 2