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
Related
Some people have requested this, this is Gingerbread KF2 Deodexed + Root and odin flashable.
This contains all bloat.
Instructions:
1. Perform Factory Data Reset/Wipe Data (If you skip this step it may still work but may leave existing apps and may cause FC's)
2. Flash Via Odin
3. Wait 5min to boot
4. Hit Thanks
The messed up Rainbow at boot is normal if using Froyo BootLoaders just wait it will boot.
Below File contains no BOOTLOADERS
T959VUVKF2 NO BOOTLOADERS
Thanks
Dr.Honk for answering all my stupid questions.
Krylon360 for original KF2 leak
nice dude!!!
Been looking for this. Might be enough to make me give KF2 a try finally.
Thanks.
Nice up man
Sent from my SGH-T959V using XDA Premium App
If I apply this (without manually doing a factory reset along the way), will I retain all of my apps and app data through this process?
I know I've used ODIN to update to the current stock release and used ODIN on my Vibrant and didn't lose my apps and app data.
Yes, there was some people in another thread that said you ALWAYS lose data when you update. I know they are wrong, but not sure what the case is with this particular update.
Does that fact that it's deodexed make it less likely that the data will be retained?
just flashed and waited 15 minutes on the rainbow screen, flashed again,same thing. how long does it take to boot the first time?
lexluthor said:
If I apply this (without manually doing a factory reset along the way), will I retain all of my apps and app data through this process?
I know I've used ODIN to update to the current stock release and used ODIN on my Vibrant and didn't lose my apps and app data.
Yes, there was some people in another thread that said you ALWAYS lose data when you update. I know they are wrong, but not sure what the case is with this particular update.
Does that fact that it's deodexed make it less likely that the data will be retained?
Click to expand...
Click to collapse
This will erase all apps, you need to use titanium backup first if you want to save that stuff.
Do I place in pda or phone in odin
My Fon is the shizz'nic!
Tommyboy2k said:
Do I place in pda or phone in odin
My Fon is the shizz'nic!
Click to expand...
Click to collapse
place in pda
punkkloser said:
just flashed and waited 15 minutes on the rainbow screen, flashed again,same thing. how long does it take to boot the first time?
Click to expand...
Click to collapse
try hitting the power button quickly it should loop once then work.
which bootloaders are you on?
froyo bootloaders. will try it again.....
K. running smooth now,will test more tommorrow.
I see the wifi signal is weak,as with the previous rom
Strangely enough I have the froyo bootloaders, flashed this, got an upgrade failure to which got me to that annoying ass screen rom upgrade failed, so I tried it again, it was successful, but oddly not only did I not get the rainbow screen but I booted with all my apps and everything intact but confirm that I am now at 2.3.3 by su binary had gotten downgraded to 2 from the ,3 beta I had had and I was coming from the KD1 rom.... Anyway strange I know....
Sent from my SGH-T959V using Tapatalk
aestivalisakito said:
Strangely enough I have the froyo bootloaders, flashed this, got an upgrade failure to which got me to that annoying ass screen rom upgrade failed, so I tried it again, it was successful, but oddly not only did I not get the rainbow screen but I booted with all my apps and everything intact but confirm that I am now at 2.3.3 by su binary had gotten downgraded to 2 from the ,3 beta I had had and I was coming from the KD1 rom.... Anyway strange I know....
Sent from my SGH-T959V using Tapatalk
Click to expand...
Click to collapse
That's strange I wonder if its not clearing everything before flashing. I will look into this.
Sent from my SGH-T959V using XDA Premium App
Flashed last night no problem, but now my phone wont register to my tmobile network.
Sent from my SGH-T959V using XDA App
Thanks my friend!
My Fon is the shizz'nic!
Like I said, weird as hell but no issues and its running beautifully..... Shrugs....im not going to argue lol
Sent from my SGH-T959V using Tapatalk
anyone else having issues registering to there network? ive flashed 3 times now and still cant register to my tmobile network.
dj02 said:
anyone else having issues registering to there network? ive flashed 3 times now and still cant register to my tmobile network.
Click to expand...
Click to collapse
What were you running prior to this flash?
If you are having troubles with this flash please give more info, what rom did you have before, what bootloaders are you using? Any info helps so that I can narrow down any issues and fix them.
Thanks.
Sent from my SGH-T959V using XDA Premium App
corradokng said:
What were you running prior to this flash?
If you are having troubles with this flash please give more info, what rom did you have before, what bootloaders are you using? Any info helps so that I can narrow down any issues and fix them.
Thanks.
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
had the fully stock gb rom that shipped with the phone. i was able to flash with no problems, just cant get it to connect to the network just keeps saying searching, wifi calling and txting work just fine.
-edit
oh right after i did the flash, i did do sgs unlock pro app. not sure if that would of caused any problems but it looks like my IMEI is showing up as .[]x[]~ ".[]x[]~
I was having issues with this version and getting stuck on samsung screen a whole lot; and i'm talking about i started clean with KC1 full with .pit>whitehawkxKD1+root>then this rom.
tried the other route and odined back to KD1>boot into cwm>checked mount and flashed the cwm version. worked flawlessly; except the rainbow, ofcourse.
my recommendations are quiet obvious
dj02 said:
Flashed last night no problem, but now my phone wont register to my tmobile network.
Click to expand...
Click to collapse
try toggling airplane mode on & off.
I'm currently using the newest Weapon G2X ROM on my phone...
Like many of you, this ROM is working just fine, but I get the itch to try something new.
I've tried to flash the new EaglesBlood release (1.9), and I've also tried the latest CM7 and MIUI.
I'm DEFINITELY NOT a pro at flashing ROMs, but I've done enough successful flashes to know how to do it correctly. In all of the above mentioned ROMS, my phone will freeze up on the boot screen, or I will get booted, but not even be able to sync a google account or reload apps... My phone will lock up and I'll have to battery pull.
In another thread this morning, I saw a user mention that the REFURBISHED handsets sometimes have problems with some ROMs and OC'd kernals...
Is anyone else having this problem? This kind of makes sense for me.
TeldenW said:
I'm currently using the newest Weapon G2X ROM on my phone...
Like many of you, this ROM is working just fine, but I get the itch to try something new.
I've tried to flash the new EaglesBlood release (1.9), and I've also tried the latest CM7 and MIUI.
I'm DEFINITELY NOT a pro at flashing ROMs, but I've done enough successful flashes to know how to do it correctly. In all of the above mentioned ROMS, my phone will freeze up on the boot screen, or I will get booted, but not even be able to sync a google account or reload apps... My phone will lock up and I'll have to battery pull.
In another thread this morning, I saw a user mention that the REFURBISHED handsets sometimes have problems with some ROMs and OC'd kernals...
Is anyone else having this problem? This kind of makes sense for me.
Click to expand...
Click to collapse
That should not be the case. The only difference in a refurbished handset is the model number. Other than that, and the fact is is previously used but everything reflashed to stock by LG or TMO, the ROMs should work the same as a DW model phone.
jboxer said:
That should not be the case. The only difference in a refurbished handset is the model number. Other than that, and the fact is is previously used but everything reflashed to stock by LG or TMO, the ROMs should work the same as a DW model phone.
Click to expand...
Click to collapse
I'm all out of ideas then... Do you have any idea why I'd have so much trouble loading other ROMs?
Like I mentioned, I'm no pro, but I've Flashed enough ROMs to think that I'm "good" at it.
I'm completely stumped.
TeldenW said:
I'm all out of ideas then... Do you have any idea why I'd have so much trouble loading other ROMs?
Like I mentioned, I'm no pro, but I've Flashed enough ROMs to think that I'm "good" at it.
I'm completely stumped.
Click to expand...
Click to collapse
Before flashing a new ROM did you do a factory data reset, format the system partition and clear the Dalvik cache? If not you will have problems as you described. You need to wipe the phone clean between flashing different roms. If upgrading to a new version of the same rom you might get away without a wipe. But if you are changing roms the steps I mentioned above are essential or you will often get bootloops or the phone will lock up during boot.
jboxer said:
Before flashing a new ROM did you do a factory data reset, format the system partition and clear the Dalvik cache? If not you will have problems as you described. You need to wipe the phone clean between flashing different roms. If upgrading to a new version of the same rom you might get away without a wipe. But if you are changing roms the steps I mentioned above are essential or you will often get bootloops or the phone will lock up during boot.
Click to expand...
Click to collapse
JBoxer, I make SURE to Reset/Wipe/Format/Clean everything EVERYTIME.
That's what I can't get figured out. I've been meticulous about it!
And I still get the frozen bootscreens and the lock ups.
Any other ideas?
Are you using rom manager because mine does that unless I use the cwm I installed from my computer
Sent from my LG-P999 using xda premium
monte666 said:
Are you using rom manager because mine does that unless I use the cwm I installed from my computer
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I'm using the NVFlash method.
Best ROM I found with the least problems
TeldenW said:
I'm currently using the newest Weapon G2X ROM on my phone...
Like many of you, this ROM is working just fine, but I get the itch to try something new.
I've tried to flash the new EaglesBlood release (1.9), and I've also tried the latest CM7 and MIUI.
I'm DEFINITELY NOT a pro at flashing ROMs, but I've done enough successful flashes to know how to do it correctly. In all of the above mentioned ROMS, my phone will freeze up on the boot screen, or I will get booted, but not even be able to sync a google account or reload apps... My phone will lock up and I'll have to battery pull.
In another thread this morning, I saw a user mention that the REFURBISHED handsets sometimes have problems with some ROMs and OC'd kernels...
Is anyone else having this problem? This kind of makes sense for me.
Click to expand...
Click to collapse
the Best I've found if you want gingerbread style is Hellfire phoenix
or if you want ICS style is Hellfire sandwich v1.6 (which is what I am using for a while now)
the only problem that I found is the video camera but other than that everything else works fine on my G2X. they update couple times a month for the last 4 months so they are always trying to make things better for their users. if you have problems they are more than willing to try to help you with it. if you are using with a simple mobile setting it has a funny setup but it work very good (better wifi & phone signals)
adeptustech said:
the Best I've found if you want gingerbread style is Hellfire phoenix
or if you want ICS style is Hellfire sandwich v1.6 (which is what I am using for a while now)
the only problem that I found is the video camera but other than that everything else works fine on my G2X. they update couple times a month for the last 4 months so they are always trying to make things better for their users. if you have problems they are more than willing to try to help you with it. if you are using with a simple mobile setting it has a funny setup but it work very good (better wifi & phone signals)
Click to expand...
Click to collapse
Second that but i'm on the GB til video can work good
Sent from my LG-P999 using xda premium
My original g2x could handle oc and UV big time, anything the devs put out . My replacement can only handle kernels with stock voltage and oc is unstable anything past 1.1ghz. So to answer your question, may be a coincidence or may just be bad luck on our part. Remember, not every processor is created equal despite being the same phone. I get tempted to get an additional replacement every once in a while but laziness tells me otherwise.
Sent from my LG-P999 using xda premium
TeldenW said:
JBoxer, I make SURE to Reset/Wipe/Format/Clean everything EVERYTIME.
That's what I can't get figured out. I've been meticulous about it!
And I still get the frozen bootscreens and the lock ups.
Any other ideas?
Click to expand...
Click to collapse
Possibly cleaning and wiping everything soo good that you clean the new rom right off your sd card?? lol. just a thought. ive done that when i 1st started flashing roms. or possibly flashing gapps on roms that dont require you to?
edit: i just realized how old this post is. lol
the reason refurbs night have worse luck is because of all the people who send their phones back because of that, they make up a reason to tell Tmobile and get a nice shiny new one. The old one is reset and passes all the "official" stability tests and gets sent out again.
Sent from my LG-P999 using Tapatalk 2
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.
I'm pretty new to the S3, so still trying to understand the nuances of locked bootloaders and flash counters. Right now I'm running stock rooted on the latest update (MF1) stock recovery. The only things I've changed from stock are used Multi Window Manager to add a couple apps to multi Window and used Wallet installer for Google wallet. Had to unlock the bootloader for wallet, but did lock it back. I've had no issues... Until this morning. When I started the phone I got the "Custom" screen with the unlocked lock. Phone finished loading with no problems. Decided to reboot into download to check the flash counter, missed it the first time and it loaded the OS... no custom screen. Rebooted again into download and everything looked fine. Rebooted into recovery... Still stock. I probably used 20% of my battery rebooting over and over to see if I got it again and never did. Anyone else ever have this happen, or did I just catch a random fluke and need to move on with my life? Any ideas as to what would have thrown the custom screen?
Sent from my SCH-I535 using xda app-developers app
Move on it just means that you have a custom bootchain.
jmxc23 said:
Move on it just means that you have a custom bootchain.
Click to expand...
Click to collapse
Yeah, not getting to worked up about it. Just thought it was odd because I don't think I have a custom bootchain, but I'm new at this phone. If you do have a custom bootchain doesn't it have the custom screen every time it boots?
Sent from my SCH-I535 using xda app-developers app
roaddog665 said:
Yeah, not getting to worked up about it. Just thought it was odd because I don't think I have a custom bootchain, but I'm new at this phone. If you do have a custom bootchain doesn't it have the custom screen every time it boots?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
It will be there until you flash a custom ROM.
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