Just getting the logo and a black screen after an update - AT&T Samsung Galaxy S II Skyrocket SGH-I727

Samsung Galaxy S2 i727 Skyrocket.
I recently updated to a 4.3 rom.
It booted up and I just got a message "Unfortuanately, Nfc Service has stopped. Blame Tyler."
I couldn't get the message to go away and the only thing I could do was a hard reboot.
Still same issue.
Rebooted into Recovery mode.
Factory Reset, wipe cache partition, format /system, wipe dalvich cache
Restored an older rom.
It booted up with no issues. But when I rebooted, I just get the Samsung logo and then the screen goes black.
I even tried Factory Reset, wipe cache partition, format /system, wipe dalvich cache and installed a new rom from scratch.
Same problem.
I have no idea what to try next or why this is happening.
Any help or comments are welcome.
Thanks

benraines said:
Samsung Galaxy S2 i727 Skyrocket.
I recently updated to a 4.3 rom.
It booted up and I just got a message "Unfortuanately, Nfc Service has stopped. Blame Tyler."
I couldn't get the message to go away and the only thing I could do was a hard reboot.
Still same issue.
Rebooted into Recovery mode.
Factory Reset, wipe cache partition, format /system, wipe dalvich cache
Restored an older rom.
It booted up with no issues. But when I rebooted, I just get the Samsung logo and then the screen goes black.
I even tried Factory Reset, wipe cache partition, format /system, wipe dalvich cache and installed a new rom from scratch.
Same problem.
I have no idea what to try next or why this is happening.
Any help or comments are welcome.
Thanks
Click to expand...
Click to collapse
What recovery are you using?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

Clock Work Method CWM...
I've done several ROM updates in the past with no problems...

benraines said:
Clock Work Method CWM...
I've done several ROM updates in the past with no problems...
Click to expand...
Click to collapse
What version of cwm? Most likely you need to update it. And what 4.3 rom?

Thanks.
I had a an older version of CWM and just upgraded to 6043..
Its now working with reboots...
I didn't realize CWM had that type of effect..
jd1639 said:
What version of cwm? Most likely you need to update it. And what 4.3 rom?
Click to expand...
Click to collapse

Related

samsung infuse: com.android.phone has stopped

I am new to android and yesterday I accidentally clicked the red download button when I held the power button down. Then a black screen with yellow text came up and said "don't power off the target!!" I left the phone on for about 30 minutes, but the battery died. Now when I power up the device I get the message com.android.phone has stopped working. I also tried a factory reset but it didn't fix anything. The device is rooted, I checked using the root checker app (i bought the phone from someone). How can I fix this? Any help is appreciated, Thanks.
Try pulling the battery for 10 minutes or so. Do you know what ROM you are running? Only other thing I can think to try is trying to boot into CWM and wiping cache and dalvik. The usually fixes a lot of my issues.
Sent from my SGH-I997 using xda app-developers app
After wiping Dalvik/cache, go into Advanced, and select Fix Permissions, just to cover all of the simple bases. If none of that works, you may have to Heimdall/Odin back to stock and start all over again.
I got into CWM, but there is no option for advanced. There are 4 options: reboot system now, apply update from SD card, wipe data/factory reset, wipe cache partition. There are no other options. Maybe I have an older version of CWM, on the top it says Android system recovery <3e>
Is the wipe cache partition what i have to click to wipe cache. Thanks for the help.
neogamma said:
I got into CWM, but there is no option for advanced. There are 4 options: reboot system now, apply update from SD card, wipe data/factory reset, wipe cache partition. There are no other options. Maybe I have an older version of CWM, on the top it says Android system recovery <3e>
Is the wipe cache partition what i have to click to wipe cache. Thanks for the help.
Click to expand...
Click to collapse
Yes...wipe cache partition to wipe cache.
And it does appear like you have the old 3e Modded Recovery. I forget the version numbers but the CWM recoveries: commonly referred to as green, red and blue, will give you other options including Advanced as mentioned above
Sent from a de-FUNKt Infuse
If you plan on doing any serious flashing, I'd think you'd want to upgrade to Red CWM. Here's a thread that tells you how.
I'd recommend Method 1:
http://forum.xda-developers.com/showthread.php?t=1107881

[Q] [P6210]Boot Looping and Corrupt Data Partition

Been running CM10 and CWM 6.0.1.9 for ages with no issues and loving it. Yesterday morning (while on vacation) picked up the tab from charging and it was boot looping. Tried formatting cache and Dalvik cache as 1st attempt to fix and it reboots when trying to format Dalvik cache, regular Cache deletes just fine. Next reflashed CM10, but still boot loops. Started manually formatting partitions and when I get to Data it reboots.
So this sounds like Brick Bug, but shouldn't be since I'm on CM10/CWM6.0.1.9 and wasn't wiping when it occurred.
So questions for the braintrust...
1) Is there anything I can do to fix this while on vacation when the only PC I can access is Windows RT? Basically it needs to be something I can flash with CMW.
2) Assuming #1 isn't possible, my next step was to try flashing a stock rom when I get back home. Make sense or other thoughts?
Thanks,
Todd
try removing your ext sd card and boot it up. See if that helps. If not, I'd Odin the stock ROM
I have experienced this too. My fix was to delete data after reflashing CM10. I tried just clearing cache and dalvik like you did but it continued to boot loop. So I flashed CM10 because I was at school and it was all I have but it was still stuck and so I cleared data at CWM(Didn't flash CM10 again anymore). And yeah, it pretty much deleted everything, but I had a backup at home. It was fixed.
Graffiti Exploit said:
I have experienced this too. My fix was to delete data after reflashing CM10. I tried just clearing cache and dalvik like you did but it continued to boot loop. So I flashed CM10 because I was at school and it was all I have but it was still stuck and so I cleared data at CWM(Didn't flash CM10 again anymore). And yeah, it pretty much deleted everything, but I had a backup at home. It was fixed.
Click to expand...
Click to collapse
Thanks. Formatting data causes a reboot, so I think I'm stuck until I get back home and can use Odin.
Sent from my SCH-I535 using Tapatalk 2
[SOLVED] [Q] [P6210]Boot Looping and Corrupt Data Partition
For the sake of the archives...reflashing stock Honeycome fixed the partition problem and allowed me to re-install CM10.

[Q] How to wipe cache Partition

I try to wipe the cache partition on my Galaxy Tab 7.0 P3100 by booting up by pressing volume button up and power button and chose wipe cache partition and when it start erasing after 5 second it's sowing error and boot to system without wiping the cache.
I'm using JB 4.2.2 with no root.
Any way to wipe the cache?
godsmack_dmx said:
I try to wipe the cache partition on my Galaxy Tab 7.0 P3100 by booting up by pressing volume button up and power button and chose wipe cache partition and when it start erasing after 5 second it's sowing error and boot to system without wiping the cache.
I'm using JB 4.2.2 with no root.
Any way to wipe the cache?
Click to expand...
Click to collapse
The may be a write problem with the cache. Does the tab works fine in normal usage?
Alternatively, you could root it and flash CM Recovery, and then try wiping cache. If it works good, otherwise its a failing hardware.
用odin3重新刷一遍recovery,一切难题迎刃而解。和楼上解法差不多。先root再用固件管家刷第三方clockworkmod。
(英语不好没法输英文抱歉。(
I had the same issue after the 4.2.2 update. I was going to wipe it because the Tab was real laggy. I got the same error. Mine is a gt-p3113.
Sent from my GT-P3113 using XDA Premium 4 mobile app
I don't think it's a hardware problem. Try installing a custom recovery and then wiping cache. A good process should be like this:
1. Root device
2. Install Custom Recovery (CWM or PHILZZ)
3. try to wipe cache
Once you have rooted and have installed custom recovery, you may also like to try out new roms.
I would suggest not rooting if you have warranty left. If you have, best option is to send it in warranty and ask them to try wiping cache.
obmahmood said:
I don't think it's a hardware problem. Try installing a custom recovery and then wiping cache. A good process should be like this:
1. Root device
2. Install Custom Recovery (CWM or PHILZZ)
3. try to wipe cache
Once you have rooted and have installed custom recovery, you may also like to try out new roms.
I would suggest not rooting if you have warranty left. If you have, best option is to send it in warranty and ask them to try wiping cache.
Click to expand...
Click to collapse
My tab still in warranty but I'm willing to trying every solution cause warranty will simply will reset factory sittings and they will say it's fixed and come to get it. But in the same time I don't want to lose the warranty.
godsmack_dmx said:
My tab still in warranty but I'm willing to trying every solution cause warranty will simply will reset factory sittings and they will say it's fixed and come to get it. But in the same time I don't want to lose the warranty.[/COLOR][/SIZE]
Click to expand...
Click to collapse
Yeah, that's basically what I am thinking. I only have until February when my warranty runs out, then I may do the root and mod deal.
Sent from my GT-P3113 using Tapatalk
I did a downgrade to JB 4.1.2 but the tab stuck at samsung animation boot screen but I did manged to enter recovery mode and do a wipe cache partition and restart to know if it gone boot but it did stuck at samsung animation screen than I used odin to but it back to 4.2.2 and it worked fine with no restart for the first 24 hour but it did restart once while I'm using it in the half of the second day and two while I'm recharging it at the end of second day.
And here we are at the third day with no restart for about 15 hour since the last restart.
I hope it's the end for this problem.

[Q] Phone stuck "Optimizing apps" after upgrading rom

Long time visitor, first time poster.
Upgraded rom today when I found of there was an official 4.3 upgrade for the Verizon GS3. Looked around and found this one: http://forum.xda-developers.com/showthread.php?t=2600305 Before that, I was on the last official stock, flashed deodexed rom.
Installed rom zip via CWM, rebooted. After loading screen, it starts upgrading apps. It got stuck on 82 of 601. After 15 minutes, I booted into recovery and wiped cache (failed to do this during initial install, it never was a problem before). Reboot, gets stuck on 93 of 465. Hard reboot, total number keeps going down, but keeps sticking.
After several hard reboots (pulling the battery), I got it down to 1 of 1, but it won't go any further. It's been about an hour.
What do I do next?
While waiting for ideas, I'll hard reset, boot into recovery, wipe cache again, and see what happens.
Edit: Wiped cache partition from CWM, rebooted, still stuck at 1 of 1.
CaffeinatedGuy said:
Long time visitor, first time poster.
Upgraded rom today when I found of there was an official 4.3 upgrade for the Verizon GS3. Looked around and found this one: http://forum.xda-developers.com/showthread.php?t=2600305 Before that, I was on the last official stock, flashed deodexed rom.
Installed rom zip via CWM, rebooted. After loading screen, it starts upgrading apps. It got stuck on 82 of 601. After 15 minutes, I booted into recovery and wiped cache (failed to do this during initial install, it never was a problem before). Reboot, gets stuck on 93 of 465. Hard reboot, total number keeps going down, but keeps sticking.
After several hard reboots (pulling the battery), I got it down to 1 of 1, but it won't go any further. It's been about an hour.
What do I do next?
While waiting for ideas, I'll hard reset, boot into recovery, wipe cache again, and see what happens.
Edit: Wiped cache partition from CWM, rebooted, still stuck at 1 of 1.
Click to expand...
Click to collapse
I believe you may need to use ODIN to manualy re-flash the 4.3 update. NOTE: This will lock your bootloader, but seeing as how you have already upgraded it already is.
Mtsprite said:
I believe you may need to use ODIN to manualy re-flash the 4.3 update. NOTE: This will lock your bootloader, but seeing as how you have already upgraded it already is.
Click to expand...
Click to collapse
Do I specifically need to find a rom that is Odin flashable, or should I try another zipped package flashed through recovery?
CaffeinatedGuy said:
Do I specifically need to find a rom that is Odin flashable, or should I try another zipped package flashed through recovery?
Click to expand...
Click to collapse
Don't use Odin to flash the official tar file, you'll lock your bootloader and you'll be stuck.
Wiping dalvik cache should work, but if it doesn't then do this.
In recovery factory reset, wipe cache, wipe dalvik cache, format system, then format internal sd card (this will erase everything on your phone). Then reflash the rom again.
Sent from my SCH-I535 using Tapatalk 2
---------- Post added at 01:55 PM ---------- Previous post was at 01:53 PM ----------
Mtsprite said:
I believe you may need to use ODIN to manualy re-flash the 4.3 update. NOTE: This will lock your bootloader, but seeing as how you have already upgraded it already is.
Click to expand...
Click to collapse
His bootloader is not locked, he never upgraded to the official 4.3 ota.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Don't use Odin to flash the official tar file, you'll lock your bootloader and you'll be stuck.
Wiping dalvik cache should work, but if it doesn't then do this.
In recovery factory reset, wipe cache, wipe dalvik cache, format system, then format internal sd card (this will erase everything on your phone). Then reflash the rom again.
Click to expand...
Click to collapse
I wanted to try something else before formatting the card and having to deal with that, so I downloaded the zipped rom here http://forum.xda-developers.com/showthread.php?t=2591895
From CWM I wiped cache (again), wiped dalvik (again), and installed rom. On reboot, went through app optimization without any problems.
I'm not sure what the problem was, but I fixed it by using a different rom.
Thank you for the help.

Problems after updating firmware for my samsung galaxy note 8 gt-n5110

I installed cm12.1 rom for my samsung galaxy note 8 gt-n5110 and after i turned it on this was what happened. It constantly showed text boxes like "unfortunately, google app has stopped" and after i closed it another one showed up and now i cant control it anymore! I cant even finish the setup! What can i do?
Im new to these firmware stuff btw.
sunglassesman said:
I installed cm12.1 rom for my samsung galaxy note 8 gt-n5110 and after i turned it on this was what happened. It constantly showed text boxes like "unfortunately, google app has stopped" and after i closed it another one showed up and now i cant control it anymore! I cant even finish the setup! What can i do?
Im new to these firmware stuff btw.
Click to expand...
Click to collapse
Try a smaller Gapps package than the one that you flashed with the ROM. The package you used is probably too large to fit in the system partition along with the ROM.
Or, you didn't factory reset, wipe cache and wipe dalvik cache when you flashed the ROM. Failing to do those wipes will cause bugs due to the new system conflicting with the saved system data/settings from the previous system. In other words, data left over from the old ROM is causing problems with the new ROM.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Try a smaller Gapps package than the one that you flashed with the ROM. The package you used is probably too large to fit in the system partition along with the ROM.
Or, you didn't factory reset, wipe cache and wipe dalvik cache when you flashed the ROM. Failing to do those wipes will cause bugs due to the new system conflicting with the saved system data/settings from the previous system. In other words, data left over from the old ROM is causing problems with the new ROM.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Hey thanks for replying but it seems like i cant even finish the setup. Therefore i cant load any files into my device. Any suggestions?
sunglassesman said:
Hey thanks for replying but it seems like i cant even finish the setup. Therefore i cant load any files into my device. Any suggestions?
Click to expand...
Click to collapse
Boot back into recovery, then factory reset, wipe cache and wipe dalvik cache, then reboot.
If that doesn't work, try booting back into recovery then flash the ROM then the Gapps then factory reset, wipe cache and wipe dalvik cache then reboot.
If that doesn't work, try booting back into recovery, then select the "Wipe" option, then choose the "advanced wipes" option, then choose the system partition, then swipe the slider at the bottom to run the wipe, then try flashing just the ROM but don't flash the Gapps, factory reset, wipe cache and wipe dalvik cache then reboot. After you get the device booted, you can delete the Gapps file then download a smaller package and put it in your phone's internal storage then boot back into recovery and select the "Install" option, at this point, you already have the ROM installed so no need to flash it again, but you do need to flash the new Gapps file, then factory reset, wipe cache and wipe dalvik cache.
Do you see how important it is to factory reset, wipe cache and wipe dalvik cache every time you flash? It is a vital step.
Sent from my SM-S767VL using Tapatalk
Hey thanks for all these but my device is using cwm right now so can you pls rewrite the instructions for me?
Also i cant finish the setup with all these popups so theres no way i can load files into it.
And yeah i guess i didnt wipe data or caches away after i finished flashing the files.
Thank you so much.

Categories

Resources