Related
Hey Guys,
I've been some flashing lately and I'm not sure what caused the problem. I've been using SprintLovers Rom with no issues since Feb. But when it stopped being supported, so I switched over to [ ROM / 5-3 ] Calkulin's EViO 3 v1.0 Beta 2 [ 4.12 l Gingerbread l Tweaked ] (which IO loved by the way)but I kept getting constant reboots. I would be using Navigation or watching a video with Rock Player and within one min , my phone would go into a boot loop and stay rebooting until and I flashed the rom again. It drove me nuts and I couldnt take it anymore.
So I reformatted everything (even deleted my card by accident) and installed [MikRoms] - [6/7/2011] - MikG v1.03 - Re-Engineered GB Sense 2.1 + 3.0 (which I also love) and the reboots are not as frequent but they are still happening. The difference is that with this rom, its getting stuck in a boot loop at the HTC EVO 4G screen that you see when it boots up. If it does boot up, the phone gets to the Sense screen and reboots again. So the only way I can get it to boot back up is to flash the rom again from recovery.
I have a 32GB Duracell Microsd Card I got off Amazon: http://www.amazon.com/gp/product/B004AM6SOG
It worked perfectly with Sprintlovers rom, But as soon as I reformatted and flashed Calkuns rom, the reboots started,. I even tried using Nandroind and going back to a Sprintlovers backup and the reboots were happening on that rom and I never had issues with that rom.
So basically I'm trying to narrow down what is causing the rebooting. I thought maybe the memory card was going bad, but how can I tell? So what I started thinking was maybe my bootloader needs to be refomattted or cleaned? But I dont know how. Then after talking to Nick1313, who helped me reformat and get my phone running again, we started thinking maybe the internal memory of the phone has gotten corrupted. I assume that Android looks to boot the OS from the internal memory and then looks to the SD card for apps and etc....
Is there a way to test my SD card to see if its ok? is there a way to see tell if my internal memory is corrupted and if so can it be reformatted and fixed?
I saw some people having a similar issue in the Galaxy S forums,but no one seemed to have a solution.
My last resort is unrooting and returning my phone to the store tomorrow. The only problem with that is , I know they are gonna have to order me one and it wont be in until Monday or whatever and the is annoying.
Any ideas would be greatly appreciated.
Snarky Answer: Well, I now know which memory card NOT to get.
Serious: I really doubt your SD card has much to do with this. Internal memory does have the potential of getting corrupted. That said, it's not likely.
It's obvious that you had good specific reasons for flashing the rom you've flashed. My advice is to flash one that you've not flashed and see if your phone's behaviour is any different.
jesuspgt said:
Snarky Answer: Well, I now know which memory card NOT to get.
Serious: I really doubt your SD card has much to do with this. Internal memory does have the potential of getting corrupted. That said, it's not likely.
It's obvious that you had good specific reasons for flashing the rom you've flashed. My advice is to flash one that you've not flashed and see if your phone's behaviour is any different.
Click to expand...
Click to collapse
Thanks for the reply. I actually Flashed back to Sprint Lovers Rom last night to after deleting everything again and reboots were still happening. I flashed back to MikG rom this morning. No reboots as of yet. But it rebooted on me 5 times last night before I flashed Sprintlovers.
GPS has been the main app I've busing when the rebooting starts. So I'm testing my phone right now with having it map to a far location and keeping my screen on to see how long it takes to make my phone reboot. Right now I'm 3mins into the test.
Turns out the processor in my phone is bad and Sprint has to order me a new one
For the past 5 months I have been using cm7 with no problems. But in the last month or so problems have been slowly coming up. It started with phone freezes then it slowed down greatly, then I got fc on EVERY APP! So then I switched to synergy hoping to fix the problems but there still there. I need help quick because I can't even make calls with out it freezing.
Sent from my Synergy Rom using XDA Premium App
monkey10120 said:
For the past 5 months I have been using cm7 with no problems. But in the last month or so problems have been slowly coming up. It started with phone freezes then it slowed down greatly, then I got fc on EVERY APP! So then I switched to synergy hoping to fix the problems but there still there. I need help quick because I can't even make calls with out it freezing.
Sent from my Synergy Rom using XDA Premium App
Click to expand...
Click to collapse
have you wiped everything (data, cache, dalvik) in recovery BEFORE flashing?
I just went through the same thing with the stock rom (rooted without the verizon crapware).. Had it since Day 1 of availability.. then a few days ago.. force closing all the time..
Even when switching roms. Even when NOT restoring with titanium.. Did everything fresh (ugh.. you have no idea how many hours).... and photos were disappearing from it
My first thoughts were "frak... I really screwed up something" (my niece dropped in on the floor a few days earlier.)
Then the IT in me decided to fall back on my experience. K.I.S.S. (keep it simple stupid).....
If even changing roms didn't fix it.. what did everything have in common? The SD Card.
So I formatted the card making sure to take everything off I needed. Put it back in.. and put a fresh rom on.
No problems since. I'm guessing the file system of the SD card went a little wonky after a year of putting files on.. taking off.. putting on.. etc
Yep I cleared everything, data, cache
D cache and batt stats. Im going to try the SD card thing right now
Sent from my Synergy Rom using XDA Premium App
Just gonna throw this out there. Try also formatting /system in the "mounts and storage" menu.
So far so good. The SD trick worked. But I want to put my titanium backup folder back on my SD card to get my apps back but I am not sure if that was the problem.
Also about the format /system l, I was thinking about that too. But if I can't get things working in the end I will format the system, data and cache.
Sent from my ADR6300 using XDA Premium App
monkey10120 said:
So far so good. The SD trick worked. But I want to put my titanium backup folder back on my SD card to get my apps back but I am not sure if that was the problem.
Also about the format /system l, I was thinking about that too. But if I can't get things working in the end I will format the system, data and cache.
Sent from my ADR6300 using XDA Premium App
Click to expand...
Click to collapse
Glad it worked.. after 3 very frustrating days for me and trying multiple roms and losing a few pics... glad I was able to at least past the info on to someone else
I am having this problem now with apps that are not installed on my SD card (which I just upgraded to larger size). All the Google apps are fc and some other ones here and there.
Were the fc apps all installed on SD?
I was thinking about a fresh gapps flash but may try the SD card first.
sent from my Dinc running CM7
Glad I found this thread! I've been having same problem and couldn't figure out if it was a rogue app or not. It seemed like right after I flashed a new rom it would run great but after a few days I would start having trouble and eventually I'd have to flash another new one or try same one again.
I have a question though....I know most things on sd card are ok to delete since any app will put new folder on there if it needs to (obviously keeps pics, titanium backups, rom backups etc.)
But I don't have a way of formatting the sdcard OUTside of the phone. I don't have a card reader on my computer. Would it be ok to do this while the phone is plugged in? (something tells me no but...)
My only other option would be to put the sdcard in my old HTC ozone and try it that way...
You can just plug your phone into your PC, mount your SD card and reformat it that way. It works for me.
jackbtha1 said:
You can just plug your phone into your PC, mount your SD card and reformat it that way. It works for me.
Click to expand...
Click to collapse
This ^^
OR
Random thought
You can try to repair the SD card before you format( if the repair doesn't work). Mount SD card to the computer via usb. Right click, properties, tools tab. Run error check. Just like a computer files get corrupted.
Sent from my ADR6300 using XDA Premium App
Ok so here's the story. I have been using HO!NO!'s cm9 roms since the first one came out. But today i flashed the newest one (v6) and also decided I would format my SD card. Then everything started to go wrong. The phone has horrible lag, like i can do a few actions for 4 seconds and then it freezes again for 30 seconds. CWM won't show any files when I try to reflash the ROM via CWM. I have tried 2 other SD cards in the phone and the same thing happens. The lag doesn't go away either when I remove the SD card. I have CWM 5.8.2.0. I am not really sure what to do at this point. If you need any more information to help me, please ask.
Update: I factory restored the phone and I'm still having the same problems.
Can someone please help i have the same problem
Try reformatting the SD card on your pc
Sent from my LG-P930
Hi!
For te past couple of days i have massive problems with my desire. SOme quirkiness had begun to show up before, but nothing on this scale. It all started on thursday when my battery died and when i came home and plugged the phone in, it came into a constant bootloop. At first i tried everything i did in a simmilar case of a bootloop - took the SD Card out, run check for errors on both partitions (i have an ext partition, yeah), run fix permissions from clockworkmod, make a nandroid backup and restore the ext image, everything that used to help. It didn't now.
So i gave up and made a fresh install of the Nikez JB ROM. I have a weird quirk with Nikez JB ROMs that freezes the phone, if i open Chrome from it's shortcut in the dock/launcher (opening links from GMail for example works okay). So it froze, and reboots (it reboots after ~10 seconds). And there came another bootloop. When i came home again, i did another fresh install. All was well for the friday evening, until i came home lat at night and opened Chrome again. What a mistake. I woke up to the lovely Evervolv boot animation.
Yesterday i installed Sandvold ICS 0.18.2.1, configured everything and went out. When i called a freind, the phone froze again (it was dialing until it dialed out, but the call UI was frozen). After pulling the battery, yep, you guesed it, bootloop. Multiple reboots, with or without SD and SIM card didn't help. I did a fresh install while being out, since i needed to be connectable. And i did another one just 10 minutes ago, only to boot into 'sorry, that and that app closed' errors. Right now it's sitting here with the first use since i reinstalled it AGAIN.
It's worth noting, that i had an 8 GB Class 10 SD card. Which apparently died. I put in the original 4 GB c2 card in yesterday, hoping it would be okay. It clearly wasn't. The 4 gig one worked okay up until now, but 2 months ago i killed a 8 GB c10 after about a year. This one held up for only a month or two. GParted dies when trying to create a partition in the last 1024 MB, so the ext has been affected.
Since the 4 GB is supposed to work, what's left, dead NAND? How can i check that? Do you guys have any suggestions as to what to do, appart from 'get a new phone' (trying to wait till 29th to see, what the Nexus 4 will be like)?
I prolly missed a ton of info, so ask away (i'm in kind of a bad mood since i have a dead phone and i might have a tiny hangover, but it's not bad).
Anyone?
I reinstalled Sandovld's ICS ROM again yesterday, downloaded all the apps, made a nandroid backup and only after that made all the settings. Later, i got two calls, the first went fine, but before ringing at the second one, the phone froze (i heard buzzing in my radio speaker and a friend came over, confirming, it was him). It didn't boot. So i restored the backup, made all the settings again (it worked), went back to CWM recovery, made another backup and that's where the story ends, it doesn't boot anymore. Another format and reinstall probably would help, but it's not actually a solution...
Ideas?
Try a GB rom that doesn't need an ext partition, like CM7. See what happens.
Technically a GB rom, like CM7, also needs an ext partition (CM7 was one of my first custom, non-Sense ROMs, tested exactly because of the ext support) or the ICS doesn't, it's not ROM dependant.
But a GB ROM, maybe even an official version, is definetly on my to-do list, i just don't know when i'll get around to it.
So here's the deal,
My ATT Galaxy S3 is half dead, and by that I mean soft bricked and I still believe there is hope in fixing this thing. Here's the entire story, everything was fine before I updated to CM 10.1 via ClockworkMod Recovery. At the time I was running the stable CM10. So I grabbed a copy of GAPPS, The CM10.1 nigthly, and a lean kernel to help improve battery life. I did the factory reset setting in CWM, then flashed CM10.1, Gapps, then the kernel. Then I did the usual after you flash a kernel, clean the cache, dalvik cache, and fix permissions. When I rebooted, the Galaxy S III boot logo was purple and glitchy, and my thought was, "Oh nooooo I bricked my phone." I had a backup saved, but after that glitch, everything was gone, so I had no backup and now I was panicking. I put my ext sd card in my reader on my PC and put the stable CM10 zip file on it, so i flashed it in CWM. My phone booted up normally. But here's the catch, no keyboard. Everything worked fine except my keyboard which kept saying, "Android Keyboard(AOSP) has encountered and error" or something like that every few seconds and would disappear just as fast. But here's the even funnier catch, everything that was my phone was still there except in a folder called 0, and in that folder another folder called 0, and in that contained a 'snapshot' of my phone as it was. CWM would not read the backup folder, or any of the files. So then I put my phone in download mode and flashed the stock ICS Samsung/ATT Rom called I747UCALG1_I747ATTALG1_I747UCALG1_HOME.tar.md5 to try to revive my phone fresh. It passed in ODIN, and now it boots up like normal except it gets stuck on the last Samsung label of the boot animation with the notification light a solid blue. Any help would be so much appreciated, I know of nothing else to do but I believe this can be fixed.
Re: [Q] Any possible ways to unbrick a softbricked SHGI747
MeatwadGetTheHunniesG said:
So here's the deal,
My ATT Galaxy S3 is half dead, and by that I mean soft bricked and I still believe there is hope in fixing this thing. Here's the entire story, everything was fine before I updated to CM 10.1 via ClockworkMod Recovery. At the time I was running the stable CM10. So I grabbed a copy of GAPPS, The CM10.1 nigthly, and a lean kernel to help improve battery life. I did the factory reset setting in CWM, then flashed CM10.1, Gapps, then the kernel. Then I did the usual after you flash a kernel, clean the cache, dalvik cache, and fix permissions. When I rebooted, the Galaxy S III boot logo was purple and glitchy, and my thought was, "Oh nooooo I bricked my phone." I had a backup saved, but after that glitch, everything was gone, so I had no backup and now I was panicking. I put my ext sd card in my reader on my PC and put the stable CM10 zip file on it, so i flashed it in CWM. My phone booted up normally. But here's the catch, no keyboard. Everything worked fine except my keyboard which kept saying, "Android Keyboard(AOSP) has encountered and error" or something like that every few seconds and would disappear just as fast. But here's the even funnier catch, everything that was my phone was still there except in a folder called 0, and in that folder another folder called 0, and in that contained a 'snapshot' of my phone as it was. CWM would not read the backup folder, or any of the files. So then I put my phone in download mode and flashed the stock ICS Samsung/ATT Rom called I747UCALG1_I747ATTALG1_I747UCALG1_HOME.tar.md5 to try to revive my phone fresh. It passed in ODIN, and now it boots up like normal except it gets stuck on the last Samsung label of the boot animation with the notification light a solid blue. Any help would be so much appreciated, I know of nothing else to do but I believe this can be fixed.
Click to expand...
Click to collapse
This one should be easy, if you got a pass in ODIN, the hard part is over.
Go into stock recovery, wipe cache and perform factory reset. Reboot and report back. This generally fixes that bug. Its very common after an ODIN flash.
Sent from my SGH-I747 using xda app-developers app
RPelham said:
This one should be easy, if you got a pass in ODIN, the hard part is over.
Go into stock recovery, wipe cache and perform factory reset. Reboot and report back. This generally fixes that bug. Its very common after an ODIN flash.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Oh wow, thank you so much. That worked and everything is as it should be, just like when I got it out of the box. I thought I was screwed for a moment, I even had an upgrade and got a HTC One VX a couple days ago haha. Wow. Again, thank you. :highfive:
MeatwadGetTheHunniesG said:
Oh wow, thank you so much. That worked and everything is as it should be, just like when I got it out of the box. I thought I was screwed for a moment, I even had an upgrade and got a HTC One VX a couple days ago haha. Wow. Again, thank you. :highfive:
Click to expand...
Click to collapse
No problem at all =) Its pretty hard to completely brick your device unless you flash something made for a different phone lol. As long as your phone can see any signs of life (even a faint vibration), let us know and we are more than happy to help!
Sent from my SGH-I747 using xda app-developers app
I once spent four hours trying to hard brick a Galaxy S2 phone (science experiment).
I'd flash ROM's for other phones.
Kernel's.
Recoveries.
Took forever to finally hard brick it.
S.O.S. Phone is completely wiped only dowload mode and recovery work.
Okay so I think I kind of put myself in a sticky situation. I tried to flash a custom rom onto my phone but in the process deleted my modem file everything worked fine except for the fact that I couldnt make calls or text messages. Basically a $400 dollar multimedia device. At this point I just want to put my phone back to the way it was when I got it at the AT&T store. My phone model is SGH-i747 Galaxy S3 that came with JB 4.1.1 pre installed.
I once spent four hours trying to hard brick a Galaxy S2 phone (science experiment).
I'd flash ROM's for other phones.
Kernel's.
Recoveries.
Took forever to finally hard brick it.
Click to expand...
Click to collapse
Out of curiosity, how did you finally manage to brick it?
Sent from my Nexus 7 using xda app-developers app
solution
MeatwadGetTheHunniesG said:
So here's the deal,
My ATT Galaxy S3 is half dead, and by that I mean soft bricked and I still believe there is hope in fixing this thing. Here's the entire story, everything was fine before I updated to CM 10.1 via ClockworkMod Recovery. At the time I was running the stable CM10. So I grabbed a copy of GAPPS, The CM10.1 nigthly, and a lean kernel to help improve battery life. I did the factory reset setting in CWM, then flashed CM10.1, Gapps, then the kernel. Then I did the usual after you flash a kernel, clean the cache, dalvik cache, and fix permissions. When I rebooted, the Galaxy S III boot logo was purple and glitchy, and my thought was, "Oh nooooo I bricked my phone." I had a backup saved, but after that glitch, everything was gone, so I had no backup and now I was panicking. I put my ext sd card in my reader on my PC and put the stable CM10 zip file on it, so i flashed it in CWM. My phone booted up normally. But here's the catch, no keyboard. Everything worked fine except my keyboard which kept saying, "Android Keyboard(AOSP) has encountered and error" or something like that every few seconds and would disappear just as fast. But here's the even funnier catch, everything that was my phone was still there except in a folder called 0, and in that folder another folder called 0, and in that contained a 'snapshot' of my phone as it was. CWM would not read the backup folder, or any of the files. So then I put my phone in download mode and flashed the stock ICS Samsung/ATT Rom called I747UCALG1_I747ATTALG1_I747UCALG1_HOME.tar.md5 to try to revive my phone fresh. It passed in ODIN, and now it boots up like normal except it gets stuck on the last Samsung label of the boot animation with the notification light a solid blue. Any help would be so much appreciated, I know of nothing else to do but I believe this can be fixed.
Click to expand...
Click to collapse
There's another thread called stuck on boot screen with same issue. Had same issue with simular Rom had to boot in recovery and clear cache and user settings. And no longer an issue
Soft bricked...
I'm currently dealing with a soft brick that I can't unbrick either. Got a replacement Sgh-i747 thru insurance. Rooted and decided to try twrp instead of cwm. Went to flash the ROM and didn't realize twrp didn't read ext SD cards until after i wiped my phone and OS. Tried reverting back to stock but Odin fails on the stock firmware every time. Tried flashing cwm and flashing a ROM but keep getting error 7 and no Roms flash. Any ideas as to where to start over with?
kinjo1023 said:
I'm currently dealing with a soft brick that I can't unbrick either. Got a replacement Sgh-i747 thru insurance. Rooted and decided to try twrp instead of cwm. Went to flash the ROM and didn't realize twrp didn't read ext SD cards until after i wiped my phone and OS. Tried reverting back to stock but Odin fails on the stock firmware every time. Tried flashing cwm and flashing a ROM but keep getting error 7 and no Roms flash. Any ideas as to where to start over with?
Click to expand...
Click to collapse
I think I did someting like that too nd now I cant install any ROM and TWRP complains that I have no OS inside the phone.I tried modifying the assert-script file but it then eventually ends up at STATUS 6 and not status 7 again.Pls and Pls help us
You have to be on twrp 2.7.x to install any kk ROMs.
Sent from my SGH-I747 using Tapatalk