Can't restart or shut down the phone - AT&T Samsung Galaxy S II Skyrocket SGH-I727

Hi,
I have flashed new ROM ( [ROM]SKY-ICS 4.2F6-2.6.1 (8/4)(UCLF6 Base) AT&T-OFFICIAL ICS.PROJ MARGARINE, W/ G-NOW).
Phone works fine, exept that I can't shut down or restart the phone - it just freeze.
thanks

I had same problem before... was from backup cwm when I do restaro backup... I just flashed same rom again never I get this problem
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

i had similar problem on previous version of sky ics. i went through the normal process of format system, clear cache, wipe davilic, but regardless of the version of sky ics, it would never shutdown/reboot. (got tired of holding down volume up/down and power to hard boot).
I ended doing ODIN back to att stock and verifying it shutdown/reboots fine.
Then i went through and installed skyics again. BAMMM it works fine afterwards...

Sounds like you had a bad install. Do a factory wipe and clean reinstall of SkyICS. If that doesn't fix it, take yourself back to stock, re-download (and check MD5s on) all files you need to install Sky, then reinstall it.
A good rule of thumb I use if a clean wipe fails, or something just doesn't feel right afterwards, is, "When in doubt, return to stock."

Thanks! problem was solved, I reflashed the stock rom then the custom one
Thanks! problem was solved, I reflashed the stock rom then the custom one

It happens usually due to an old CWM, so if it happens again update it.

Related

Help needed ... custom ROM issues!

I have a Nexus S 4G w/ Sprint, rooted w/ Clockwork recovery. I'm running into problems using custom ROMs. Flashing any ROM goes fine; however the next time I reboot, my lockscreen PIN won't work, and it looks like I've been signed out of my Google account (based on an alert in the notification bar). I've tried CM7, BugglessPete's GRJ90 stock ROM, and ROM v1.1.1 ... tried a couple different kernels too. Each time I flash I do a full wipe, and everything seems peachy until I reboot the phone... so then I have to reboot into recovery and restore my stock backup nandroid. The new radio I flashed seems to work though.
So basically I've always resorted back to just using stock, which really doesn't bother me since Gingerbread + ADW is more than fine IMO. However now I wouldn't mind updating to 2.3.5, without losing root. And I would like to use CM7 when the next stable release comes out...
Thoughts? Thanks!
When you run cm7 or any other rom are you installing gapps and setting everything up again?
When u install a new rom you start with a fresh phone no saved info till you sign into Google.
Sent from my Nexus S 4G using Tapatalk
cc82 said:
I have a Nexus S 4G w/ Sprint, rooted w/ Clockwork recovery. I'm running into problems using custom ROMs. Flashing any ROM goes fine; however the next time I reboot, my lockscreen PIN won't work, and it looks like I've been signed out of my Google account (based on an alert in the notification bar). I've tried CM7, BugglessPete's GRJ90 stock ROM, and ROM v1.1.1 ... tried a couple different kernels too. Each time I flash I do a full wipe, and everything seems peachy until I reboot the phone... so then I have to reboot into recovery and restore my stock backup nandroid. The new radio I flashed seems to work though.
So basically I've always resorted back to just using stock, which really doesn't bother me since Gingerbread + ADW is more than fine IMO. However now I wouldn't mind updating to 2.3.5, without losing root. And I would like to use CM7 when the next stable release comes out...
Thoughts? Thanks!
Click to expand...
Click to collapse
when you do a full wipe, your settings get restored to factory settings. thats what a full wipe is, a factory reset. if you are just updating a rom, do not wipe. like if youre just updating to a newer cm, dont wipe. just update on top and your setting will stay. if youre updating from one rom to another completely different rom, then you have to wipe.
simms22 said:
when you do a full wipe, your settings get restored to factory settings. thats what a full wipe is, a factory reset. if you are just updating a rom, do not wipe. like if youre just updating to a newer cm, dont wipe. just update on top and your setting will stay. if youre updating from one rom to another completely different rom, then you have to wipe.
Click to expand...
Click to collapse
No I'm talking about flashing a new ROM, not just an update. And it works at first - I sign into google, restore my apps, etc. The problem arises the next time the phone reboots (no flashing or anything); after the reboot, my lockscreen code no longer works, as in I can't get past the lockscreen and into my phone, and it looks like I've been signed out of my Google account.

I think I broke it.

I just got this phone yesterday and immediately installed CM7. Thinks were going well, except for the random restarts at the lock screen and some apps not working. I read that Faux's CM stock kernel improves stability, and I hoped it would fix the restarts.
I read the directions thoroughly, wiped out the cache, wiped out the Dalvik cache, installed the kernel, and rebooted. It got stuck at a black screen, but I read that it does take a while, so I left it for about 10-15 minutes before removing the battery.
I wiped all caches, including user data, and reinstalled CM7 hoping it would fix whatever kernel problem just happened. Now it freezes at the blue LG screen.
I've tried several different caches that are all supposed to be comparable with my phone, and after installing them (after wiping all caches and /system each time) I'm stuck at the blue LG screen. I also tried flashing the entire phone to stuck, but to no avail. Installing the GB Kernel stock got me back to the black screen, this time flashing a brighter shade of black periodically, but still after 20 minutes, nothing happened.
I'm going insane after spending all day searching these forums and Google. If there's anything I can try besides installing kernels and reinstalling CM7, please let me know. I'm an idiot and didn't backup before I installed CM7 the first time, and every backup I've downloaded gives me an MD5 checksum error. At least I still have access to recovery. Most results I pulled up with searches brought me to people who lost their recovery menu as well, I'm not sure why I can't fix this even with the recovery menu still intact.
Keep in mind that you have to clear cache/dalvik right AFTER you have flashed the kernel, before reboot.
At this point, i would suggest to do a full wipe (clear data/factory reset, caches and also format system under storage and mounts). Then flash your flavor of CM7 and while still in CWM, flash the kernel of your choice, DON'T REBOOT, but clear cache/dalvik. Reboot, let it sit for a while and you should be good.
Sent from my LG-P999 using xda premium
Luriden said:
I just got this phone yesterday and immediately installed CM7. Thinks were going well, except for the random restarts at the lock screen and some apps not working. I read that Faux's CM stock kernel improves stability, and I hoped it would fix the restarts.
I read the directions thoroughly, wiped out the cache, wiped out the Dalvik cache, installed the kernel, and rebooted. It got stuck at a black screen, but I read that it does take a while, so I left it for about 10-15 minutes before removing the battery.
I wiped all caches, including user data, and reinstalled CM7 hoping it would fix whatever kernel problem just happened. Now it freezes at the blue LG screen.
I've tried several different caches that are all supposed to be comparable with my phone, and after installing them (after wiping all caches and /system each time) I'm stuck at the blue LG screen. I also tried flashing the entire phone to stuck, but to no avail. Installing the GB Kernel stock got me back to the black screen, this time flashing a brighter shade of black periodically, but still after 20 minutes, nothing happened.
I'm going insane after spending all day searching these forums and Google. If there's anything I can try besides installing kernels and reinstalling CM7, please let me know. I'm an idiot and didn't backup before I installed CM7 the first time, and every backup I've downloaded gives me an MD5 checksum error. At least I still have access to recovery. Most results I pulled up with searches brought me to people who lost their recovery menu as well, I'm not sure why I can't fix this even with the recovery menu still intact.
Click to expand...
Click to collapse
This is what you need to recover your phone
http://forum.xda-developers.com/showthread.php?t=1248644 , after that you need to root again and reinstall NVflash. Check youtube for instractions to flash CM7 on your phone. Good luck
Instaling custom kernel instructions:
Wipe Cache
Wipe Dalvik
Wipe Batt Stats
Install Kernel
Fix Permissions
Reboot
ratza66 said:
This is what you need to recover your phone
http://forum.xda-developers.com/showthread.php?t=1248644 , after you need to root again and reinstall NVflash. Check youtube for instractions to flash CM7 on your phone. Good luck
Click to expand...
Click to collapse
That worked! I came across that earlier, but I downloaded a similar package with a flash.bat that didn't fix it. Sure enough, I'm back. Thanks!
Make sure you downloaded his CM7 version and not Stock kernel.
Luriden said:
That worked! I came across that earlier, but I downloaded a similar package with a flash.bat that didn't fix it. Sure enough, I'm back. Thanks!
Click to expand...
Click to collapse
You welcome, I've added info on how to install custom kernel too
What are the usual behaviors while waiting for the phone to boot up for the first time with the new custom kernel? I downloaded the latest March nightly of CM7 (the latest April build gave me a bad file error while trying to install for whatever reason) and Faux's LGE Pre-OC/UV Kernel Version 013, did the proper order of installation, and it's been sitting for about 15 minutes now at a black screen that keeps flashing on and off. With USB plugged into my PC, I'm hearing a rapid "plugged/unplugged" sound loop with each flashing screen. Will I have to do the whole ROM Recovery tool process to try again?
Luriden said:
What are the usual behaviors while waiting for the phone to boot up for the first time with the new custom kernel? I downloaded the latest March nightly of CM7 (the latest April build gave me a bad file error while trying to install for whatever reason) and Faux's LGE Pre-OC/UV Kernel Version 013, did the proper order of installation, and it's been sitting for about 15 minutes now at a black screen that keeps flashing on and off. With USB plugged into my PC, I'm hearing a rapid "plugged/unplugged" sound loop with each flashing screen. Will I have to do the whole ROM Recovery tool process to try again?
Click to expand...
Click to collapse
You can't install custom kernel on nightly release. Use RC 7.2 and yes do the rom recovery and back it up so the next time you can just restore to any rom that works on your phone.
This may sound crazy, but I feel like I CM7-proofed my phone. Ever since I messed up that first time with the kernel and used the recovery tool, I can't get CM7 loaded anymore. I got 7.2 RC and installed it with the kernel the proper way, and got stuck at the LG screen.
So I used the recovery tool again, then NVFlash, wiped data/cache, installed the root file, then tried installing just 7.2 RC by itself. No luck.
I used recovery tool again, then NVFlash, then wiped data/cache, then used restore to bring it back to the stock + root that I made this morning before trying 7.2 RC and I'm back... so I went to CWM again and did wipe data/cache, and installed the SAME CM7 file I installed with yesterday morning which worked fine at the time, the latest stable release (7.1), and I'm still stuck at the LG screen.
This makes absolutely no sense. EaglesBlood installs fine, so it's not a problem with custom roms, I just don't like EaglesBlood (and EaglesBlood also froze when installing a custom rom the correct way as well). I'm tempted to just stick with the stock GB 2.3.3 + root since it works, I'm just missing the features I had yesterday of CM7 before I installed that god forsaken kernel.
Luriden said:
This may sound crazy, but I feel like I CM7-proofed my phone. Ever since I messed up that first time with the kernel and used the recovery tool, I can't get CM7 loaded anymore. I got 7.2 RC and installed it with the kernel the proper way, and got stuck at the LG screen.
So I used the recovery tool again, then NVFlash, wiped data/cache, installed the root file, then tried installing just 7.2 RC by itself. No luck.
I used recovery tool again, then NVFlash, then wiped data/cache, then used restore to bring it back to the stock + root that I made this morning before trying 7.2 RC and I'm back... so I went to CWM again and did wipe data/cache, and installed the SAME CM7 file I installed with yesterday morning which worked fine at the time, the latest stable release (7.1), and I'm still stuck at the LG screen.
This makes absolutely no sense. EaglesBlood installs fine, so it's not a problem with custom roms, I just don't like EaglesBlood (and EaglesBlood also froze when installing a custom rom the correct way as well). I'm tempted to just stick with the stock GB 2.3.3 + root since it works, I'm just missing the features I had yesterday of CM7 before I installed that god forsaken kernel.
Click to expand...
Click to collapse
I Think you are missing a one step, Wipe Dalvik. Ok let start from the begining,
First restore your phone to stock, let it boot. Root your phone and install CWM. Install CM7.2 RC rom and let it boot. Go back to the CWM and follow this instructions:
Wipe Cache
Wipe Dalvik
Wipe Batt Stats
Install Kernel
Fix Permissions
Reboot
all these steps are important. I was using CM 7.2 RC with Faux's kernel without any problem and it worked flawlessly
I just tried again with those instructions, and I still can't even get CM7 to boot up for the first time.
- Recovered my phone to stock using rom recovery tool
- Let boot, got to android's home screen, shut down
- Used One-Click-Recovery's "Flash CWM 5.0.2.0 Internal and External SD ROM" feature to install CWM (I'm assuming this is the proper way. I learned this from a YouTube video and it helped me to root my phone and get CM7 working the first time)
- Booted into CWM, wiped user data and cache, installed root-g2x-su-2.3.6.3.zip
- Restarted just to be sure (though I have tried just flashing CM7 after the root without restarting) and got into the android home screen just fine after I had to go through initial setup again. Though oddly enough my Google Apps were still present. They weren't present the very first time I rooted my phone, I had to install gapps.
- Shut down phone, went into CWM again
- Wiped user data, wiped cache, installed CM7 7.2 RC1
- Rebooted
- Stuck at blue LG screen for eternity.
I'm using the same root file as I did when I rooted my phone for the first time, and I've tried using this same method with the very first CM7 file I successfully installed and ran, and I'm still stuck at the blue LG logo unless I stock recover again and stick with stock. Rooting works fine, I've been able to run rooted apps on the stock rom, I just can't install any version of CM7 again for the life of me.
Luriden said:
I just tried again with those instructions, and I still can't even get CM7 to boot up for the first time.
- Recovered my phone to stock using rom recovery tool
- Let boot, got to android's home screen, shut down
- Used One-Click-Recovery's "Flash CWM 5.0.2.0 Internal and External SD ROM" feature to install CWM (I'm assuming this is the proper way. I learned this from a YouTube video and it helped me to root my phone and get CM7 working the first time)
- Booted into CWM, wiped user data and cache, installed root-g2x-su-2.3.6.3.zip
- Restarted just to be sure (though I have tried just flashing CM7 after the root without restarting) and got into the android home screen just fine after I had to go through initial setup again. Though oddly enough my Google Apps were still present. They weren't present the very first time I rooted my phone, I had to install gapps.
- Shut down phone, went into CWM again
- Wiped user data, wiped cache, installed CM7 7.2 RC1
- Rebooted
- Stuck at blue LG screen for eternity.
I'm using the same root file as I did when I rooted my phone for the first time, and I've tried using this same method with the very first CM7 file I successfully installed and ran, and I'm still stuck at the blue LG logo unless I stock recover again and stick with stock. Rooting works fine, I've been able to run rooted apps on the stock rom, I just can't install any version of CM7 again for the life of me.
Click to expand...
Click to collapse
Follow this guy on YT, you will find everything there
http://www.youtube.com/watch?v=fxMnnarHaOU
Installing CM7 tutorial
http://www.youtube.com/watch?src_vi...id=annotation_334516&feature=iv&v=Cy9on64jAZs
This one is even better
http://www.youtube.com/watch?v=vUaWXM8GwUI
I've done what all three of those videos have shown. These methods work for other custom roms just fine, just not CM7 which is what I want, regardless of what build I use. Which rom is the closest to CM7? I tried EaglesBlood and I noticed a lot of changes I didn't agree with, I didn't toy around with it long enough to see if I could get it working like CM7.
EDIT: Even tried Nullifier Dual Wipe, still stuck. Just... wow.
EDIT #2: Now EaglesBlood doesn't even want to run, also getting stuck at the LG logo after recovering, wiping data/cache, and flashing the rom. It worked fine last night, I just erased it so I could give CM7 another shot and didn't have enough space on my SD to have a backup of that AND my rooted stock.
EDIT #3: Did the recovery/root/flash method again, going from fresh stock to flashed CM7, and this time it sits at the blue LG logo for a few seconds, before restarting and going back to the white LG logo. I wiped the cache though to prevent a bootloop, and I think most bootloops occur with the CM7 logo anyway.
There's no chance of any files being on the micro sd that could be causing the problems, could there? And is there anything else I should be wiping/formatting these tries? Like maybe rom recovery doesn't wipe EVERYTHING out, and I still have remnants of other attempts still?
Luriden said:
I've done what all three of those videos have shown. These methods work for other custom roms just fine, just not CM7 which is what I want, regardless of what build I use. Which rom is the closest to CM7? I tried EaglesBlood and I noticed a lot of changes I didn't agree with, I didn't toy around with it long enough to see if I could get it working like CM7.
EDIT: Even tried Nullifier Dual Wipe, still stuck. Just... wow.
EDIT #2: Now EaglesBlood doesn't even want to run, also getting stuck at the LG logo after recovering, wiping data/cache, and flashing the rom. It worked fine last night, I just erased it so I could give CM7 another shot and didn't have enough space on my SD to have a backup of that AND my rooted stock.
EDIT #3: Did the recovery/root/flash method again, going from fresh stock to flashed CM7, and this time it sits at the blue LG logo for a few seconds, before restarting and going back to the white LG logo. I wiped the cache though to prevent a bootloop, and I think most bootloops occur with the CM7 logo anyway.
There's no chance of any files being on the micro sd that could be causing the problems, could there? And is there anything else I should be wiping/formatting these tries? Like maybe rom recovery doesn't wipe EVERYTHING out, and I still have remnants of other attempts still?
Click to expand...
Click to collapse
No chance. Nothing will be left over when you wipe your phone. Your SD card is only accessed when you tell CWM to do so. Take your phone back to stock. Do it again this time try either a froyo rom or ICS rom. Then go back wipe everything and install CM7. Sometimes you have to take the long way. after flashing my phone a bazzilion time I learned this the hard way when I couldnt load EB ICS anymore. Had to run GB to get to ICS. Try it in reverse or from a step below and it should go through fine. IF it doesn't, you might have to use ICS instead, which may be stuttery, but works damn well.
DupleX01 said:
Keep in mind that you have to clear cache/dalvik right AFTER you have flashed the kernel, before reboot.
Click to expand...
Click to collapse
I'm wondering why he still has the issue. YOU CLEAN CACHE BEFORE FLASHING KERNEL/ROM UPDATES!!!
Sent from my LG-P999 using xda premium
For God sake, just flash a random ROM to get access to inside your phone.
1. DIAG your phone OFFLINE with v21e baseband (phone will automatically restart)
2. Let it stay for 5mins after that
3. Use your phone for 15mins
4. Root using 1Click
5. Install CWM
6. Install your ideal ROM + GAPPS (if needed) via CWM
7. Reboot
8. Go outside your living room and watch TV for at least 15mins
9. Reboot your phone into CWM and flash your ideal kernel
10. Enjoy!!!
You better know which ROM/kernel to choose from. Period.
How to upgrade/downgrade your baseband? Do some search, please!
Sent from my LG-P999 using xda premium
I'll do a flash of Froyo or ICS and possibly some baseband research tomorrow. Considering my luck getting a simple rom flash to work, I don't feel too comfortable dealing with the baseband.
A friend was brave enough (somehow) to let me root and install CM7 on his phone, he has the same phone as mine. I got CM7 7.2 RC and Faux's DM UV working like a dream on my first try. Tried it on my phone after recovering it, same problem. So it's a problem that exists deeper on my phone, not with my methods.
The NAND restores for GB and Froyo give me MD5 checksum errors, and the stock zipped rom of GB gives me an installation failed error, so I'm thinking a zipped Froyo rom won't work either, but it might be worth a shot.
Tried Weapon and MIUI too. No go. If I don't get stuck at the blue LG logo, then I'm stuck in a loop between the two LG logos or stuck at a flashing black screen. 8/10 times though it's the blue LG, I think the other errors may have actually been me forgetting to wipe my cache when I was flustered.
I'll try ICS, and hopefully won't get to a point where I have problems installing things I used to be able to, since that seems to be the pattern. After that I finally give up.
I FIGURED IT OUT! Well, sort of. For the hell of it, I downloaded CM7 7.1.0.1 through Rom Manager and it installed fine. It downloaded it to my internal SD, so I hooked it up to my PC to copy the 7.2.0 RC1 to my internal SD and tried installing. No go.
So I went on my phone's web browser and redownloaded 7.2.0 RC1 that way directly to the phone. It works. So somehow, roms I copy from my PC to the phone appear to not work, yet apps and kernels still do. I'm running CM7 7.2.0 RC1, downloaded through my phone's web browser, with Faux's DS UV kernel, copied from my computer. After four days, I finally found a workaround, so I'll stick to it. Whatever works, I guess. I can try reinstalling my USB drivers, but I can probably get by with a combination of the phone's web browser and ES File Manager w/ LAN if need be.

Phone freezing and unresponsive

My girlfriend's Skyrocket starting tonight has been freezing while the screen is locked. It won't wake by pressing the button immediately, but opens briefly after maybe 30 seconds. I pull the battery and restart and it worked fine for about two hours and did it again.
Any ideas? I have her fix permissions but it keeps coming back.
I feel bad because she was fine with stock but I convinced her to let me root it!
Unlocked, rooted, stock rom.
wipe cache and dalvik cache? Any new apps or changes that have been done recently?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
this happens to mine maybe once every two weeks, so it is so few and far between that i dont mind. using nexusmod gb.
whenever it freezes, i hold down the home button to see which apps are running and attempt to close them, but it takes too long and i just yank the battery. the only common app that is always running during every freeze is 'phone'.
jphilippon said:
My girlfriend's Skyrocket starting tonight has been freezing while the screen is locked. It won't wake by pressing the button immediately, but opens briefly after maybe 30 seconds. I pull the battery and restart and it worked fine for about two hours and did it again.
Any ideas? I have her fix permissions but it keeps coming back.
I feel bad because she was fine with stock but I convinced her to let me root it!
Unlocked, rooted, stock rom.
Click to expand...
Click to collapse
Rooting wont freeze your phone, that's something to do with the ROM. Did you make a CMW backup before rooting? If yes, then you can boot into recovery, perform a factory reset 3 times, then wipe cache 3 times, then wipe davlik cache 3 times, then restore from the backup, reboot back to recovery and flash the radio (the ICS radio's ) work with GB so you can chose one from them.
If you haven't made a backup, you can download the stock 2.3.5 rom from sammobile, install it, and then do the update to 2.3.6.
Also dont restore apps, using Titanium backup, it causes issues. You can use superbackup to restore, call logs, sms and contacts, that's what I use.
If you would like to try a ICS rom, you can install Sky ICS 4.2E, there is an update 4.2F but it kept crashing so I am on 4.2E runs butter smooth as the stock GB.
All custom ROMS you can find in the Android Development Section
Unless she is going to run themes on AOSP, she probably won't get much other benefit from root. Sounds like she just wants stable, stock. I learned that lesson the hard way with my wife...every time she ran into a glitch! Otherwise, SkyICS is going to be your best bet for the least problems. My wife has been using it with no complaints... yet.
Sent from my SGH-I727 using xda app-developers app
aviseqdas said:
Rooting wont freeze your phone, that's something to do with the ROM. Did you make a CMW backup before rooting? If yes, then you can boot into recovery, perform a factory reset 3 times, then wipe cache 3 times, then wipe davlik cache 3 times, then restore from the backup, reboot back to recovery and flash the radio (the ICS radio's ) work with GB so you can chose one from them.
If you haven't made a backup, you can download the stock 2.3.5 rom from sammobile, install it, and then do the update to 2.3.6.
Also dont restore apps, using Titanium backup, it causes issues. You can use superbackup to restore, call logs, sms and contacts, that's what I use.
If you would like to try a ICS rom, you can install Sky ICS 4.2E, there is an update 4.2F but it kept crashing so I am on 4.2E runs butter smooth as the stock GB.
All custom ROMS you can find in the Android Development Section
Click to expand...
Click to collapse
SkyICS 4.2F is running far more flawlessly than all other sky roms. The vast majority of users have no issues. It's based on an official release, not a leaked release. Those users with issues are normally at fault, not the rom; and these issues are usually easily fixed.
Don't be afraid of 4.2F.
Using SeanZ's SkyICS 4.2F r2 v6B ROM / XDA Premium

My phone is soft bricked I think.

Ok, I flashed something that wasn't for my sgs2 skyrocket and when I did it nothing happened, then when I rebooted it it seemed ok untill it kept freezing, no sound even on full val. I cant call because I cant here the other person and that it freezes on every app I open it takes like 2mins to open or a force close comes up. Well I have flashed back to stock using odin but still the same problem. I dont know what to do? Any thoughts about fixing this?
Sent from my samsung galaxy s2 skyrocket i727.
If you have flashed back to stock, and are still having the same issues it sounds like there may be a hardware problem. Did you do a full clean flash back to stock? (system wipe, clear the dalvik)
Sent from my SAMSUNG-SGH-I727 using xda premium
Why would you flash something not for the Skyrocket?
Wipe the phone completely, as in all data, the system, caches, and repeat that wipe three times in recovery, then power down. Go into download mode and restore to GB stock (yes, all the way back), then use Kies to do the ICS update and stay stock for a few days to make sure everything works after that.
If it's still not working after that, your hardware is jacked. Restore the thing back to GB, pull the cord out during the ICS update on Kies and finish the job. Hope you're still in warranty; if not, I hear you can get a used Captivate for $60 or so while you learn not to flash stuff for the wrong phone.
in stock recovery wipe caches and do a reset, if still a no go, install cwm, wipe caches and reset x3, reflash stock firmware with odin again, perform a reset, if still a no go then hw malfunction
Well someone's lazy...
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
No I just flashed it back. But ima try that right now. Hope it this will work.
CaLLm3LAzY- said:
No I just flashed it back. But ima try that right now. Hope it this will work.
Click to expand...
Click to collapse
You just flashed it back? You're not making any sense. Post a link to the ROM you flashed or we can't help you.
I flashed the stock rom.

Boot Loop but why??? And do I HAVE to Odin??

Quick background - unlocked, and rooted months ago. Clean Flashed CR5.6 ten days ago (first and only ROM flashed). Flashed WaWasabi theme few days later. Yesterday morning I flashed a mod that broke Wasabi theme. I reflashed Wasabi, still broken. Each time clearing cache and Dalvik. Dirty flashed CR5.6, clearing cache and Dalvik again. Worked fine. Flashed Wasabi theme, worked fine. Did a full charge. Played on my phone to 1am without a problem.
Went to bed with the phone next to me, it was on and not hooked to a charger. Heard a slight buzzing sound on and off. Looked at phone and it was boot looping. It gets to Verizon and 3 bars, then boot loops.
So does this mean I have to Odin? Never had to Odin so I'll be researching that now. Thanks!!!
I would restore my nandroid, that should fix you right up.
If you don't have one, Odin time.....
Either that or try a clean flash of your ROM. If you think that ROM is bad, you can also always download a different ROM to your SD card using a computer and clean flash that.
rpz3.14 said:
Either that or try a clean flash of your ROM. If you think that ROM is bad, you can also always download a different ROM to your SD card using a computer and clean flash that.
Click to expand...
Click to collapse
Thanks guys. I couldn't get into recovery VolUp+Power+Home for some reason, not matter how many times I tried. Finally worked and tried the lazy way of clearing caches, but that didn't work. So I did a clean install and it seems to be fine again. Now for the rebuilding everything part that I really don't like....
But I'm concerned about why it just started boot looping out of the blue.
If you have a nandroid, you can go to backup/restore and do advanced restore of data and it will out everything back the way you had it on your clean install.

Categories

Resources