For the last 2 months or so my s3 has been having random reboots when acceding the internal or external storage. It happens when downloading files from web or transferring files over wifi. Happens when connected to home network or cell network. Also happens when moving or unzipping files that are already on my device. Generally files about 100mb or larger, but has happened with smaller files. May reboot once and I can finish downloading or transferring, or it may reboot repeatedly when I try to redownload or move files. I have Googled this and can only find older threads about freeze ups that occur when accessing storage but were for the GSM models of s3, and aging the threads were over a year old. Device info is 16gig with 16gig external card. Running aokp (8/20 build currently). BMS kernel (7/30 build). Happens on last few releases of aokp with stock (aokp) kernel or others (BMS). (Lean). Any one experience this or have any input on this issue?
Try going back to stock with stock kernel. If it still happens you have a faulty device or hardware is failing.
Sent from my SCH-I535 using Tapatalk 4
Sandman-007 said:
Try going back to stock with stock kernel. If it still happens you have a faulty device or hardware is failing.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Would it be ok to restore my stock nandroid? Or should I just use odin?
No use odin
Sent from my SCH-I535 using Tapatalk 4
Sandman-007 said:
No use odin
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
thank you, i will give it a go when i have a chance. just flashed beanstalk 4.3 to see if that helps. ill restock if i have any issues.
tdawgg777 said:
thank you, i will give it a go when i have a chance. just flashed beanstalk 4.3 to see if that helps. ill restock if i have any issues.
Click to expand...
Click to collapse
Going back to stock would only be necessary if you have a soft brick. You're already rooted, and there is no other reason to go through the entire process again until you've tried everything else.
Lots of things can go wrong with Odin that could put you in a predicament, such as accidentally putting the file in the wrong slot, a faulty connection, a bad flash, all of which would put you in a much worse situation.
Random reboots occur from many factors, but a lot of it can be boiled down to the phone not playing nice with the current rom you are on, these are the steps I would take.
1. Try a different rom, 4.2 aosp roms or touchwiz roms might fix it. Restoring your stock android would be a great step, just make sure you don't ota because you'll lose root.
2. If it's similar on all roms, then try a different kernel.
3. If it's still occurring, try to use a kernel that allows you to apply voltages such as ktoonsez, and raise the minimum voltage for each cpu step a tiny bit for each step.
4. If it's still rebooting, try formatting your internal SD card and reflashing a stock based rom through a custom recovery, such as cleanrom or a stock rooted rom.
5. Odin back to stock at a last resort.
If all of those steps don't work, then you have a hardware problem.
Sent from my SCH-I535 using Tapatalk 2
If he just went back to official Firmware ie Stock he wouldn't have to screw around with different ROMs and kernels and voltages. No offense but you need to learn better troubleshooting skills. If he went to stock it would pretty much eliminate all things u suggested (ie low voltage). Odining back to stock would format his internal for him thus eliminating that step u suggested as well. I this this will save him time and frustration.
Sent from my SCH-I535 using Tapatalk 4
Sandman-007 said:
If he just went back to official Firmware ie Stock he wouldn't have to screw around with different ROMs and kernels and voltages. No offense but you need to learn better troubleshooting skills. If he went to stock it would pretty much eliminate all things u suggested (ie low voltage). Odining back to stock would format his internal for him thus eliminating that step u suggested as well. I this this will save him time and frustration.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
What you're suggesting is basically a cure all for everything, but don't you think it would be better to troubleshoot the problem systematically than simply go back to stock everytime you have an issue you can't figure out? If that was the case, then I would have used Odin to go back to stock at least a dozen times by now.
It's a better learning experience to understand what a specific phone can run and can't run. It's a pita to have to flash back to stock and reroot when you don't troubleshoot the actual problem. Especially when it's a rom or kernel related issue that can be easily remedied.
Sent from my SCH-I535 using Tapatalk 2
OK I can see where you r coming from.
Sent from my SCH-I535 using Tapatalk 4
Ok so its been 10 or so hours now that I've been running beanstalk 4.3 (8/27 build) with bms kernel (8/15 build). I've transfered files around, made app back ups and downloaded latest update for beanstalk (200+ MB) and no reboots.
What advice is there when I have random reboots across roms. no matter which I try oi always get random reboots. is it tthe battery?
Sent from my SCH-I535 using Tapatalk 4
0331 said:
What advice is there when I have random reboots across roms. no matter which I try oi always get random reboots. is it tthe battery?
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Odin back to stock and run it completely stock and see if you can repeat the problem.
If you're completely stock and your phone keeps rebooting, it's likely a hardware problem.
Sent from my SCH-I535 using Tapatalk 2
will do thank you!
Sent from my SCH-I535 using Tapatalk 4
Related
This thread is now irrelevant as Jellybean is available for the device.
The old post can be found below:
As of right now be sure that you all are extemely cautious when trying to flash any type of ICS package (be it firmware, a ROM, or any type of system running it). Our tablet may have an issue with ICS as many other galaxy devices have. A bug currently exists that corrupts the mounting of the data partition on the device which *MAY* lead to a permanent hard bricking of your device.
This is currently a very RARE issue, however, those who are not well educated in Android development and that do not know how to 100% reset their tablet should refrain from flashing any type of ICS ROM or ODIN package.
If you have already flashed an ICS ODIN package or are running CM9 safely and have been for a good amount of time, then my guess is that this issue will not effect you, BUT it may strike you at any given time!
For those of you who insist on upgrading to ICS, *PLEASE* backup your entire ROM and make sure that you have the stock HC ODIN package. Although it probably won't help having them if you are hard bricked.
A quote from an effected user:
ringnutz said:
I also had the can't mount data problem, I tried for 3 days to get it to work. I ended up sending it back to Samsung after reverting everything to stock. I was on cm9 though and one night it just started bootlooping while i was asleep. I.e. it would fully boot then restart after 5 seconds or so. So I tried reverting to stock and trying again, which is when I got the can't mount data issue. I literally tried every combination of wiping, recovery, Odin/heimdall, and the only thing that would get past the Samsung logo was cm9, which would just stick at the boot animation forever. I got tired of messing with it and thought it could have been a hardware problem, so I sent it back under warranty
Sent from my myTouch 4g via Tapatalk
Click to expand...
Click to collapse
A quote from an effected user:
daviddavid123 said:
i installed cm9 and ics 4 then my tab hard bricked and internal memory damaged
Click to expand...
Click to collapse
A quote from an effected user:
krbabb said:
I dont have posting privleges in the developer forums but i thought i would let you know whats up with my tab.
Rooted it, got cwm on it and flashed cm9. Worked for about a week without issue then started the bootlooping issues. I couldnt even wipe the data in recovery.
Used odin to go back to stock HC according to your instructions. Then i thought it bricked cause it just got stuck on the default screen showing galaxy tab. Tried installing HC a few more times but it never booted.
Tried one more time but now with the stock ics. Still nothing so i gave up.
Only thing is i couldnt power off. I planned to let the battery die. So it just sat on the default gakaxy tab screen and about 30 minutes later it showed the samsung boot animation.
I let it sit for another half hour with samsung pulsing. Nothing. So i reboot into recovery (stock) which i couldnt even get to before now, wipe everything like 5 times then reboot the device.
Booted up and works like a charm. I thought this thing wad gone.
Not sure if the stock ics tar file did the trick but let everyone know that mine came back to life. It possible other devices could be bricked but maybe there is a chance for some people.
Sent from my GT-P6210 using xda app-developers app
Click to expand...
Click to collapse
If you have flashed ICS and you have bricked your device I am sorry. I know there are a few people out there who have....
To conclude, everybody please be careful about tinkering with your device. I know ICS has great speed enhancements and all, but as of right now your box of ice cream sandwiches may or may not be poisoned.
For the daredevils:
CM9 [View thread]
Guide to flashing ICS [View thread]
EDIT: Our case is not the same as the other galaxies.... Ours effects the data partition while theirs effects their emmc... I'm assuming ours may be a bug with the firmware installation / recovery as it was with theirs however I'm not sure why it is effecting users on CM9....
EDIT 2: We should all be cautious and NOT wipe at all using Samsung's ICS Recovery. I was chatting with aorth and he suggested that that may be the cause of the issue. His recovery (or the one I posted in my guide) are safe to wipe on.
EDIT 3: I guess we also have reports of the emmc being corrupted as well...
Just don't wipe data/factory reset using recovery ICS (RECOVERY 3e). Use recovery 5.5.0.4 or 6.0.x.x......only you wipe for up new rom, everything will be OK.
Sent from my GT-P6200 using Tapatalk 2
Yeah, i experienced this type of total brick. I flashed p6200 ics firmware with mobile odin and than did factory reset in ics recovery mode. I think this was the reason of hard brick. After some time tablet did shut down and didn't turn on. Service fixed the problem, they said that main board died.
Ignore this post.
StrumerJohn said:
That's not the case I afraid...
Click to expand...
Click to collapse
I really don't think it was a problem with upgrading. I had been on cm9 for over a month, then I woke up one morning and it was bootlooping. I got all the can't mount data errors afterwards, so it's either a hardware problem or cm9 is somehow magically corrupting the /data partition. I hadn't even installed anything recently
EDIT: Samsung just sent me the email that the repair is finished, they replaced the main board, so it definitely was a hardware problem.
Sent from my myTouch 4g via Tapatalk
This issue was brought up a couple months ago by aorth, I think its in his CM9 thread or in one of the rooting or CWM threads. I don't think it is an issue that will be going away any time soon as Samsung isn't in any hurry to fix it, that is if they even can or want to.
Using stock ICS for almost 3 weeks now.
I was backing up and restoring all of the partitions via CWM 6.0.1.0 two times.
Nothing weird happening for the moment.
I use the ics wipe/factory reset and I don't have any problem, I have 6210 .
Well, aorth entioned sth like this before, here his post:
aorth said:
Maybe you guys have heard, but some early ICS ROMs for Galaxy Note and other similar Galaxy S II variants have triggered hard bricks due to faulty MMC firmware handling erase commands improperly. I never bothered to read up about the issue until now, but it looks like we should also be careful.
Chainfire just released a tool to print out whether your device has a known-bad firmware revision, Got BrickBug?. As you can see, my device has firmware revision 0x19. This revision has been known to cause hard bricks on other devices using Samsung ICS ROMs.
CM9 is safe (Entropy512 haxx0red the kernel), but we should be careful.
Click to expand...
Click to collapse
I got this bad firmware revision too, but iam still safe after 2 months
Sent from my GT-P6200 using xda app-developers app
Bad2hold said:
Well, aorth entioned sth like this before, here his post:
I got this bad firmware revision too, but iam still safe after 2 months
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
I'm not sure if I had the bad one, but mine worked fine for months too. Then out of the blue it bootlooped and when I tried to fix it by reverting to stock, I got the error. Hopefully when it comes back it will have a different firmware revision (if that's what the problem was)
Sent from my myTouch 4g via Tapatalk
I flashed my tab with 'P6200OXALQ1_P6200XXLQ1_P6200XXLQ1' on 19th July - so far nothing has happened.... and it is working much faster than the 3.2 Honeycomb it came with.:fingers-crossed: Using Stock kernel/recovery... only rooted using temporary touch recovery.
02xda2 said:
I flashed my tab with 'P6200OXALQ1_P6200XXLQ1_P6200XXLQ1' on 19th July - so far nothing has happened.... and it is working much faster than the 3.2 Honeycomb it came with.:fingers-crossed: Using Stock kernel/recovery... only rooted using temporary touch recovery.
Click to expand...
Click to collapse
If you flashed it using Mobile Odin that's normal because it uses its own recovery.
Ok, so what's the verdict? This bug sounds very scary.
Given that I'm running a stock ICS flashed via ODIN, should I be running:
-Stock recovery
-CWM
-Something else
to avoid bricking while factory reset?
I also use mobile Odin to flash ics and no problem. So, could you say that with Mobile Odin are safe from this problem?
Just read this http://www.reddit.com/r/Android/comments/xj2hd/i777_superbrick/, seems some of the things said could be relevant for us.
I have a galaxy note and Entropy who is dealing directly with samsung on this issue has a thread over on the galaxy note page. Lots of information over there.
I use the free emmc bug check app by vinagre https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check&hl=en to check my samsung devices on ics. Not entirely sure that the same case applies for the note and the tab plus though but it does give me peace of mind.
Just to err on the side of caution, I always odin flash back to gingerbread to wipe cache and other stuff before upgrading. This seems to have worked for me so far. *fingers crossed*
Check out that app above, its free and have a read of entropy's thread http://forum.xda-developers.com/showthread.php?t=1698977 but beware they don't take kindly to noob questions. I just mainly read entropy's updates and replies and ignore most of the rest of the stuff there.
Is there any chance to bring my tab to life has the repair center hasen't repaired mine
hi,
i have flashed the stock ICS, the Austrian version using ODIN3. i have been running it since july 18th.
so far i dont see any problem with my tab..
just to say, i have flashed the firmware atleast 3 times, just as an exercise. and have factory reset it after ICS flash atleast like 5 times now.
everything so far works fine. i use the stock recovery for factory reset.
after the 1st flash, i had root.. then thought of unrooting, so flashed the firmware 2 more times.
and in between the flashes, i have factory reset a lot of times.
so far, the bootloop problem which i used to have when on HC, is not there. hopefully, it wont occur in ICS.
hope, this helps developers.
Zarvox said:
Is there any chance to bring my tab to life has the repair center hasen't repaired mine
Click to expand...
Click to collapse
Use pit file (tab 7.7) in topic of hg42 - galaxy note this forum.
http://forum.xda-developers.com/showthread.php?t=1667886
Or use this method:
http://forum.xda-developers.com/showthread.php?t=1661590
Sent from my GT-P6200 using Tapatalk 2
giangp1 said:
Use pit file (tab 7.7) in topic of hg42 - galaxy note this forum.
http://forum.xda-developers.com/showthread.php?t=1667886
Click to expand...
Click to collapse
Thanks with manual method described in this thread I've confirmation that my data partition became corrupted.
Yes it is alive !!!
I've deleted mmcblk0p9 (DATAFS on my P6210) and recreate one with smaller size (3 GB) than normal (15.2 GB).
When the tablet boot I realise I've 1.68 GB of storage
Now I may increase the size of data but previous tries told me if data reach 5 GB in size the creation of partition fail.
I having big issues with my SR lately. I was on chimera 2.2 and things were great. Popped cm10 alpha 3 on there with investgator Xs kernel on there and started getting SODs, one time it was locked for a while before I got to it. Was pretty warm. After that I've wiped the SD cards clean, odin'd back to stock, tried SEVERAL ROMs, cm 9 official, skyics, cm 10 super lite, and others... no matter what ROM (all with the kernel they come with) I get a SOD every 15 to 45 minutes. Even weirder is no last_kmsg is being produced!
With or without any CPU apps. No under volting. Tried 3 different batteries. Tried all I/O Schedulers.
I have exhausted everything I know about this to fix it and I don't know what to do.
I've tried wiping and flashing ROMs with all existing recovery options (twrp, cwm, cwm touch, custom cwm touch) and with or without dark side scripts. I've wiped 3 times or more....restored very old nandroids that never had that problem too, and they get it.
Is it possible there is ANYTHING left in my files that normally won't get wiped that could cause this? Is there anyway to figure this out or does it sound like my SR is going bad? I'm up for any solution. Today using one of the nandroids it didn't get a SOD all day, but it was stuck from going into deep sleep due to a wake lock from chrome which I have since fixed... its getting SODs again now...
I realize you may benefit helping me with a log cat which I'm trying to get with lumberjack. Oh and a dmesg right?
Thanks in advance to anyone who can help. I'll answer any questions I can I may have forgotten.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Forgot to mention I know a repatriation in Odin should help but there is no pit file for this phone... any other ways around that?
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Try a fresh new revert back to stock on odin. If you still get sod, you are sol. Your phone hardware has gone bad. I'm guessing your internal sdcard developed corruption and is ireparably damaged.
Try to get it repaired or replaced under warranty.
Sent from my SGH-I727 using xda premium
jamesc760 said:
Try a fresh new revert back to stock on odin. If you still get sod, you are sol. Your phone hardware has gone bad. I'm guessing your internal sdcard developed corruption and is ireparably damaged.
Try to get it repaired or replaced under warranty.
Sent from my SGH-I727 using xda premium
Click to expand...
Click to collapse
Thank you for the reply.
Wanted to give an update... I sent the phone to Samsung for warranty repairs last week. It is labeled as fixed and on its way home today. The repair tracker they let me see said it was a "Side Button Failure" and the repair was a "S/W Updated"... Now I know there has been talk of a power button issue with this phone.. but I was leaning more towards what the above poster stated.. a corrupt internal SD or something along those lines...
I guess my confusion is, did they really duplicate my problem before throwing a fix at it and then VERIFY it was indeed, fixed? I don't know how shotty Samsung warranty repairs have been for others but I hope they did indeed fix my problem. I guess we'll see.
Since the New TouchWiz JellyBean leak dropped, we quickly found out that the Rootdebug method no longer works for rooting...Not a big deal as developers rolled back to our grass roots and used the original Odin method to achieve root. My only issue is with the suggestion to flash a modified No Wipe image of the stock K1 leak...Im not sure if I agree with this. I have dirty flashed with Odin in the past and things appeared to work fine on ICS, but stepping up to JellyBean seems to be different!
Point is since the leak has dropped many folks complain of media server causing battery drain, I was one of them. So I decided to odin back to stock using the rooted FULL WIPE VRBLK1 version by Mr. Robinson...and I have had substantially less battery drain!!! Battery life is currently at 15hrs with 65% left...2 hrs screen on.
I would suggest to anybody that flashed a no wipe image in odin and is having issues with media server draining the battery, and/or any other issues appear, try flashing the FULL WIPE version! As others have said, I believe the problem is a corrupted file on the internal sd causing the issue. Also a few other small issues I was having appears to be fixed, such as touch screen being unresponsive at times...also gps seems to lock faster. Anybody else noticing the same??
This is interesting. I did the no wipe to the newest leak and I felt it was horrible. Battery for me was not as good and the phone was always hotter. So I went back to J1 leak. If I get time I might try the full wipe version of the newest leak. Try the theory out.
As an addition, my CPU was always acting crazy. Random low frequency locks (would not ramp up). Sometimes it would stay high, probably the cause of the warm phone. And weird battery drain from the system I just could not explain.
Thanks for this and as I said I'll try fresh after the weekend. Holiday weekend is my family time.
Sent from my SCH-I535 using Tapatalk 2
I know this is somewhat off topic so I apologize for derailing....are you guys having any issues with NFC on AOSP ROMs after flashing the leak via Odin?
Sent from my SCH-I535 using Tapatalk 2
Marcismo55 said:
I know this is somewhat off topic so I apologize for derailing....are you guys having any issues with NFC on AOSP ROMs after flashing the leak via Odin?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I've only flashed an AOSP once. That was the last time. Too choppy, and i like my TW features. So, to answer your question, I don't know.
Sent from my SCH-I535 using Tapatalk 2
I did full wipe and everything is great except gps.
I did a no wipe version moving from J1 to K1, what I saw was the RAM footprint increase by 50%...
I did the full and footprint went back to what I recognized on J1...Barry seems as good or better than J1 too
Sent from my SCH-I535 using xda app-developers app
I did Robinson's no error via Odin and don't have any apparent issues. what should I be looking for?
lexluthor said:
I did Robinson's no error via Odin and don't have any apparent issues. what should I be looking for?
Click to expand...
Click to collapse
Did you use the full wipe or no wipe version in odin? Thats the point of this thread...no wipe seems to be causing a foul odor with media drain and random issues for folks. The full wipe leaves you so fresh and so clean!!
Sorry for sounding like a noob, but what exactly is media drain? Battery use by "media server?"
Sent from my Galaxy S III using Tapatalk 2
US Marine said:
Sorry for sounding like a noob, but what exactly is media drain? Battery use by "media server?"
Sent from my Galaxy S III using Tapatalk 2
Click to expand...
Click to collapse
yes
Hmm...I did the no-wipe flash, and I haven't had any issues whatsoever.
Sent from my Galaxy S III using Tapatalk 2
US Marine said:
Hmm...I did the no-wipe flash, and I haven't had any issues whatsoever.
Sent from my Galaxy S III using Tapatalk 2
Click to expand...
Click to collapse
Thats good! Im not saying everybody is going to have issues with the no wipe version...most likely its going to be folks that have flashed a bunch of roms and accumulated alot of folders/files on the internal SD. The point is if you are one of the unfortunate folks thats having issues, try the FULL WIPE version.
droidstyle said:
Thats good! Im not saying everybody is going to have issues with the no wipe version...most likely its going to be folks that have flashed a bunch of roms and accumulated alot of folders/files on the internal SD. The point is if you are one of the unfortunate folks thats having issues, try the FULL WIPE version.
Click to expand...
Click to collapse
Yeah, I flashed from bone stock the day I got the phone.
Sent from my Galaxy S III using Tapatalk 2
My phone seems a little laggy which I did not experience on the first leak. I don't not have the typical problems people have with flashing the no wipe version... That's what I flashed. Thinking of trying a factory reset but this thread makes me wonder if flashing the wipe version might be better? What's the difference though? Both wipe and no wipe are from the same file, right?
Sent from my SCH-I535 using xda premium
Question, I did the no wipe version on odin from the stock samsung s3, and now my RAM usage is almost always close to 1 gb. Before on ICS it was like 600 or 700 mb. Is this normal for jelly bean?
Ryno77 said:
My phone seems a little laggy which I did not experience on the first leak. I don't not have the typical problems people have with flashing the no wipe version... That's what I flashed. Thinking of trying a factory reset but this thread makes me wonder if flashing the wipe version might be better? What's the difference though? Both wipe and no wipe are from the same file, right?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Full Wipe will repartition the Internal SD and wipe rom data...this will get rid of any corrupted files that reside on the internal. Its the same principal as reformatting and installing windows. Dirty Flashing writes your data over the top of data and nothing else in the internal sd is touched...not saying dirty flashing is bad, I do it alot, but when wierd issues arise, 90% of the time a Full Wipe with Odin fixes things.
VigilanteM2 said:
Question, I did the no wipe version on odin from the stock samsung s3, and now my RAM usage is almost always close to 1 gb. Before on ICS it was like 600 or 700 mb. Is this normal for jelly bean?
Click to expand...
Click to collapse
I believe touchwiz jellybean uses more ram.
Is the full wipe version included everything like the original Verizon release version? (radio, rom, kernel, bootloader etc...)Thanks.
buhohitr said:
Is the full wipe version included everything like the original Verizon release version? (radio, rom, kernel, bootloader etc...)Thanks.
Click to expand...
Click to collapse
Yep
I have just realized that the hotspot is broken. Every time I try to turn it on, it force closes Settings. Anyone else having this problem?
EDIT: So I downloaded a hotspot toggle widget, and it works fine. I only have a problem if I try to enable hotspot via Settings. Interesting.
Sent from my Galaxy S III using Tapatalk 2
I been running into some weird problems, and I'm not sure what's causing it so just wondering if anyone can help me out a little here.
I been keeping up with the cm10.1 updates and mortez kernels, but only since couple days ago. It started acting really weird.
1) I notice the files that are created on external are often corrupted. Like back ups or copies of the ROM I dl.
2) sometimes the reception bars shows that I have no reception bar at all,but if I changed it to text then change it back, it turns back to normal.
I fully wiped/reinstall the the phone at least 5 times already, but situation isn't getting any better, tried different radios and kernels and is still the same.
Any helps will be great,thanks in advance
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Odin back to stock and see if the issue persists...
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Yeah tried that also
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Format both external SD and internal SD, flash my efs fix then Odin to GB 2.3.4
can i just flash it in cwm?
Okay I flashed the esffix. I am running on embryo right now and everything's okay for now, but if I flash the cm10.1 then the problem is back, can anyone five me some suggestions on what to do?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
spiderman905 said:
Okay I flashed the esffix. I am running on embryo right now and everything's okay for now, but if I flash the cm10.1 then the problem is back, can anyone five me some suggestions on what to do?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
which recovery are you, use the latest from sk8's cwm or twrp
im using sk8's cwm, i just odin back to gb and now its bootlooping.... really need some help thanks
spiderman905 said:
im using sk8's cwm, i just odin back to gb and now its bootlooping.... really need some help thanks
Click to expand...
Click to collapse
Do a factory reset and it won't boot loop
God promised men that he'd put beautiful women in all corners of the world. Then he laughed and laughed and made the world round
oh that solves the problem, i thought i did, but i guess i didnt. thanks. its already my 3rd odin back to gb. because it didnt solve the problems the last 2 times i did it, any suggestions on how to proceed from here?
You probably have a bad external sd card. They do go bad sometimes
Edit: cm10.1 has had some problems with the phone. Mostly not being able to make calls, maybe that's your other problem. Idk, I'm not sure I under stand what problem you're having
What was the best before sliced bread?
i guess thats part of my problem and the other one is whenever its creating files on external sd, the files ended up being corrupted.
The external works fine if I use the adaptor on the computer, I guess it's fine? Is there way to check it?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
spiderman905 said:
The external works fine if I use the adaptor on the computer, I guess it's fine? Is there way to check it?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I would try a different rom and see if you still have the problems. The nightly cm10.1 is going thru some bugs fixes. Although issues with external sd card is not one of the bugs that I'm aware of.
What was the best before sliced bread?
I have a really bad problem, my gf and I recently both got the Verizon galaxy s3 from Amazon wireless. I happen to like mine. In a day I rooted, flashed Synergy and won't go back.
Now..my gf's galaxy is a different story. From day one,.Hers likes to shut off by itself or become unresponsive (with the blue light blinking in sleep mode. The only fix is to pull the battery and restart.
Here is what I've tried..
Browse the hell out of forums (mainly yours)
Changing stock settings.
Flashed a custom ROM to see possibly it's the stock rom was broken. Same issue
Used my battery to see if it was a bad battery.still didn't fix it
Flashed a different kernel to see if the kernel is to blame. No dice.
Wiped to stock using Odin. Nuh uh.
I'm pretty much out of options.
I'm thinking about sending it back.
Hers has Synergy on it atm. If no one has any options left, can I just Odin back to stock, lock the bootloader, and use triangle away?
Thanks
Sent from another Galaxy far, far away using xda premium
stanleyopar2000 said:
I have a really bad problem, my gf and I recently both got the Verizon galaxy s3 from Amazon wireless. I happen to like mine. In a day I rooted, flashed Synergy and won't go back.
Now..my gf's galaxy is a different story. From day one,.Hers likes to shut off by itself or become unresponsive (with the blue light blinking in sleep mode. The only fix is to pull the battery and restart.
Here is what I've tried..
Browse the hell out of forums (mainly yours)
Changing stock settings.
Flashed a custom ROM to see possibly it's the stock rom was broken. Same issue
Used my battery to see if it was a bad battery.still didn't fix it
Flashed a different kernel to see if the kernel is to blame. No dice.
Wiped to stock using Odin. Nuh uh.
I'm pretty much out of options.
I'm thinking about sending it back.
Hers has Synergy on it atm. If no one has any options left, can I just Odin back to stock, lock the bootloader, and use triangle away?
Thanks
Sent from another Galaxy far, far away using xda premium
Click to expand...
Click to collapse
What build was your Synergy ROM? I've had difficulties with any ROM after about 3/23 due to some problems with the whole 3.4 thing. I'm not familiar with the Synergy ROM (obviously I've heard of it, but I don't like the stock "feel") and the problems that I've encountered have been on AOKP and CM based ROMS. But you may want to try flashing an earlier build. I went back to a build of the ROM I use from 3/13 and the problems I had that were similar to the ones you described stopped.
I've been running synergy for months now, and with almost all of their different releases. I have never had random reboots like that though. If you are using r420, or pretty much any of the newer releases, make sure you are doing a full wipe and not restoring any app data. That's the only way to make sure it isn't the ROM causing it. If it's still a problem, use that manufacturer warranty
Sent from my SCH-I535 using xda app-developers app
SynergyROM is awesome agreed. I had similar problems at one point due to my voltage settings. Not all phones are created equal. Increased voltage and changed governor to 'on demand' because 'interactive x' had problems at the moment.
Some have just flashed a different kernel but imo ziggy is a genius and I will rock his kernel as long as he makes one.
The issue is one one of the builds ziggy and I think phones with rev4 couldn't handle the low volt
The blue light blinks or stays on for a bit like when booting.?
Clearly..... It your phone does it on a stock kernel,
I highly doubt the software is causing it.
It sounds like somewhere across the line you have a hardware issue.
Oh damn...hardware..that's what I suspected. Should I do the three steps (odin, re-lock , triangle away) and send it back to Amazon?..or sammy?
And will they know if I messed with it?
Sent from my SCH-I535 using xda premium
I'm having the exact same problem with the latest AOKP and CM10.1. I reverted back to an older version to see if this fixes the problem.
stanleyopar2000 said:
Oh damn...hardware..that's what I suspected. Should I do the three steps (odin, re-lock , triangle away) and send it back to Amazon?..or sammy?
And will they know if I messed with it?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
triangle away first then odin, since you need root to use triangle away. re-lock not necessary if you flash a stock image.
reslor1 said:
triangle away first then odin, since you need root to use triangle away. re-lock not necessary if you flash a stock image.
Click to expand...
Click to collapse
+1. Also, Odin will not up your flash counter unless your flashing something that isn't stock......Odin as the last step will leave you at out of box stock.
Sent back the phone. Hope for the best
Sent from my SCH-I535 using xda premium
Amazon apologized and she got overnight a 32gb s3 for the same price as the 16. This new one has no sleep issues
Sent from my SCH-I535 using xda app-developers app