Related
Alright folks, my phone appears to have gone off the deep end.
A few weeks back, I was changing over to the new Eclipse ROM, and at first everything was going fine and dandy. However, I soon began experiencing a few force closes. I restarted the phone, and then everything went to hell. So many force closes I couldn't operate the phone, inability to make calls, unable to open apps, unable to install apps, basically all I can do is text, receive calls, and browse the web (although after enough time the phone crashes anyway). I have tried everything I know of to fix it: new ROMs via recovery, new ROMs via Odin, deleting caches, deleting personal data, using the .pit file and factory stock in Odin, the works. I even found the Samsung PST and used that, but for naught. The weird thing is that even after using the .pit file (which is supposed to delete EVERYTHING), my phone "remembers" old applications that were installed on it. In fact, it seems like there is some sort of ghost image on my phone, and whenever I restart it the phone returns to that state (any applications I tried to uninstall are back, all contact data is deleted, etc.). This ghost image hangs around no matter what I do.
Any suggestions?
Sounds to me that you obviously are not getting a true "PASS" with pit file. If you had you would have no files saved on phone. But if you followed the instructions to a "t" like you allude to...
Sent from my SCH-I510 using xda premium
I have followed the instructions fully (and multiple times to boot), and I have always gotten a PASS.
This is sounding regrettably similar to the issues reported in this thread - try looking at post numbers in the mid 300s - I think they are centered around late September/early October (there are more than this, but I'm pretty sure that timeframe has the highest density of discussion on this). If it's what it sounds like, the /data partition is no longer in a state that can be written over (the "ghost image" you were referring to) - and truth be told I don't know if anyone has come up with a "free" solution to the problem.
dwitherell said:
This is sounding regrettably similar to the issues reported in this thread - try looking at post numbers in the mid 300s - I think they are centered around late September/early October (there are more than this, but I'm pretty sure that timeframe has the highest density of discussion on this). If it's what it sounds like, the /data partition is no longer in a state that can be written over (the "ghost image" you were referring to) - and truth be told I don't know if anyone has come up with a "free" solution to the problem.
Click to expand...
Click to collapse
I had read through those posts before, and was not very happy to see the conclusion. As those posts were from a few months ago, I was hoping that perhaps someone had some new ideas. Oh well, I guess I'll be trying my luck with Verizon. Thanks for trying, folks!
jderig said:
I had read through those posts before, and was not very happy to see the conclusion. As those posts were from a few months ago, I was hoping that perhaps someone had some new ideas. Oh well, I guess I'll be trying my luck with Verizon. Thanks for trying, folks!
Click to expand...
Click to collapse
Thinking... What recovery does your phone have on it now- stock or clockwork? Are you on rfs file system- did you revert back or can you flash a diff kernel using cwr?
These are just some thoughts that came to mind. If dwith can't help you I can't do much more. Good luck with Verizon offering any help
Sent from my SCH-I510 using xda premium
Corrupted NAND, but still returns a pass.
I had this once, I spammed with the PIT and it somehow worked
Sent from my SCH-I510 using xda premium
Hindle1225 said:
Thinking... What recovery does your phone have on it now- stock or clockwork? Are you on rfs file system- did you revert back or can you flash a diff kernel using cwr?
These are just some thoughts that came to mind. If dwith can't help you I can't do much more. Good luck with Verizon offering any help
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
I currently have Clockwork. I am unable to tell at this moment what my file system is, as I can't install Voodoo, and the method of adding/deleting folders on my SD card doesn't work. However, I do recall during one of my many attempts at using different kernels/radios/roms I did get the creepy female Voodoo bootup voice, but even though that said it was a success I was never able to tell whether it actually worked.
As of right now I am capable of ODIN and Clockworking any Rom/kernel/etc., but they all bring along the Ghost Image.
kvswim said:
Corrupted NAND, but still returns a pass.
I had this once, I spammed with the PIT and it somehow worked
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
What is NAND, if you don't mind me asking? Also, I suspect by now I've run ODIN with the PIT 10+ times with no success
jderig said:
What is NAND, if you don't mind me asking? Also, I suspect by now I've run ODIN with the PIT 10+ times with no success
Click to expand...
Click to collapse
NAND is just a type of flash memory. If you recognize the word nand then you should have an idea. If not, it's not really important.
jderig said:
Alright folks, my phone appears to have gone off the deep end.
A few weeks back, I was changing over to the new Eclipse ROM, and at first everything was going fine and dandy. However, I soon began experiencing a few force closes. I restarted the phone, and then everything went to hell. So many force closes I couldn't operate the phone, inability to make calls, unable to open apps, unable to install apps, basically all I can do is text, receive calls, and browse the web (although after enough time the phone crashes anyway). I have tried everything I know of to fix it: new ROMs via recovery, new ROMs via Odin, deleting caches, deleting personal data, using the .pit file and factory stock in Odin, the works. I even found the Samsung PST and used that, but for naught. The weird thing is that even after using the .pit file (which is supposed to delete EVERYTHING), my phone "remembers" old applications that were installed on it. In fact, it seems like there is some sort of ghost image on my phone, and whenever I restart it the phone returns to that state (any applications I tried to uninstall are back, all contact data is deleted, etc.). This ghost image hangs around no matter what I do.
Any suggestions?
Click to expand...
Click to collapse
just covering bases by asking, did you go ALL the way back to ed1 with that pit file or a more recent version (gb or something along those lines)
From what I understand, the phone is still working, but is very unstable. The PBJ kernel does NOT support Voodoo Lagfix (but still supports EXT4). Can you try flashing imoseyon's kernel (which supports it) and enabling/disabling Voodoo? It can be found at RootzWiki. Also, when you get into CWM, it says the version at the top.
Sent from my SCH-I510 using xda premium
Here you go....i have been here.
Get into clockwork(CWM) - mount everything via usb and backup what you need to backup.
Perform a quick format of your sdcard so that when you see your phone on the pc, its blank.
Go back to stock odin and boot up, report any issues.
Sent from my SCH-I510 using XDA
What happened next
I tried what you said because I'm in the same boat. I still get the FCs and it tries to walk me through the setup. It gets stuck at the Checking Account step in the setup wizard. I let it sit there for about an hour while I went to lunch to no avail.
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 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
To start, I have never had problems flashing Skyrocket ROMs before. I flashed the ICS leak with Odin when I first got the phone, then CWM, then Cyanogeonmod when that came out, and some other things. But recently I decided to flash SlimBean which suggested TWRP so I flashed that and I had it working well for awhile.
After Google I/O I decided to f;ash the weekly build, SlimBean 5.5. The flash went OK but the ROM was glitchy and crashed a lot. So I decided yesterday to go back to the release channel of SlimBean. So I downloaded SlimBean 5.0 and AIO Addons 5.x and I moved them to my SD card. However before I did that I noticed I already had a 5.x from my last flash that would turn out to be the Aroma installer that i didn't want. But anyways, after wiping the cache, Dalvik cache, system, and data, I flashed the 5.0 ROM then the 5.x aroma aio addons, and then it sent me into the Aroma installer which I figured out that I used the wrong addons aio package. So then I hit next all the way through the installer without changing anything and didn't hit reboot device. Then, still in the TWRP menu, I wiped the same sections I did last time, mounted the SD card through TWRP, moved the AIO Addons 5.x on, and deleted the AIO Aroma 5.x. Then I flashed SlimBean 5.0 from before with the AIO Addons 5.x.
When I hit reboot, my phones screen was off and it never went on again. I took out the battery, had it hooked to the charger, and tried everything and it wouldn't even vibrate. So I knew pretty fast that I had hard bricked it. I Google'd a little bit and read about the jig, but I have a feeling that wouldn't work with this low level of a brick. So I guess what I want to know is what actually happened, and I just want to get this story out there because I have no idea how I got such a low level brick from just flashing ROMs like usual.
Also, I'm planning on making a trip to the AT&T store with hopes of getting a replacement. I don't know if I will because it is refurbished and I bought it online over a year ago. (the warranty being 90 days) Does anyone have experience getting replacements out of warranty?
First off if it's bricked it's bricked it's not about low level or whatever.
Second a jig does nothing for this phone that can't be done manually, don't waste your time or money on it.
Third you can have it jtag'd for $50 by some dudes if you search tons of people have done it.
You left out an astounding amount of detail for an extremely long post so no one can tell you exactly where you went wrong.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Yea, way too many words. But to your last paragraph, good f'n luck. You're way out of warranty.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
You will get no warranty. Send it away for jtag if you want it fixed, you can't fix it if it's hard bricked.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
I sent the phone to be jtag'd and they sent it back saying they couldn't fix it. What could have gone so wrong in the flashing process that it is bricked so badly?
TankTan38 said:
I sent the phone to be jtag'd and they sent it back saying they couldn't fix it. What could have gone so wrong in the flashing process that it is bricked so badly?
Click to expand...
Click to collapse
probably wasnt the flash but bad hardware, most likely mobo/memory, jtag can only write to the mem chip if its corrupted or a incompatible rom was trying to write to it but it wont/cant fix a hw failure of chip
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