Database Info

[Rom][ODIN] Stock Gingerbread 2.3.3 Deodexed + Root KF2

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.

[Q] Rewinding sound while speaking.

Hi, I recently started messing around with my sgs4g and installed a custom rom using the GB Stater Pack and flash the KJ6 AOSP, everything is working flawlessly except that everytime I'm talking to someone I suddenly hear a rewinding-kind of sound and the other person can hear it too, it happened to me using octane rom, stock GB update and AudiophileFTW edition, can someone please help me get rid of that sound it's getting really annoying, I would really appreciate any help given. Thanks in advance

dude, you hurt your hardware.
Go back to stock KD1, and see if you still have the issue, If you do, go to the tmobile store.

airfluip1 said:
dude, you hurt your hardware.
Go back to stock KD1, and see if you still have the issue, If you do, go to the tmobile store.
Click to expand...
Click to collapse
If I Odin the stock one the rewinding sound goes away, I already did that, but I really want to try a few custom roms because the battery consumption of the stock one is awful.
I have 2 galaxy s 4g both of them are having the same problem one is running the kj6 aosp and the other one is running stock gingerbread leak rooted

ajtorres14 said:
If I Odin the stock one the rewinding sound goes away, I already did that, but I really want to try a few custom roms because the battery consumption of the stock one is awful.
I have 2 galaxy s 4g both of them are having the same problem one is running the kj6 aosp and the other one is running stock gingerbread leak rooted
Click to expand...
Click to collapse
When you flash the GB ROMs, are you doing a factory data reset, clearing caches, etc?

stephen_w said:
When you flash the GB ROMs, are you doing a factory data reset, clearing caches, etc?
Click to expand...
Click to collapse
Factory reset, wipe cache & wipe davlik and my mount settings are u,m,m,u..

ajtorres14 said:
Factory reset, wipe cache & wipe davlik and my mount settings are u,m,m,u..
Click to expand...
Click to collapse
Weird issue. I know you didn't mention it in the OP, but are you over or under-clocking at all?
I'm somewhat with airflup on this - it seems to be a hardware issue. I am saying that based on the fact that I've not heard of anyone else having this issue on GB ROMs. It could be something funky with one of the chips in the phone but only manifests in the GB ROMs. It's weird but not unheard of.
I've not attempted this so someone tell me I'm an idiot for thinking about this, but what if you flash a stock GB ROM followed by the modem from KD1 or whatever Froyo ROM you're using to see if the problem is still there?

If you have the same issues on 2 different devices, you should redownload the roms(cwm and odin), maybe its a download issue i.e. mds5 error
Tell me if that works
Sent from my SGH-T959V using XDA App

As of today I have rooted my phone with different methods, re-downloaded everything, used different versions of Odin, went back to stock, install official GB, it's still doing it, also with the stock Gingerbread leak I noticed that besides the rewinding nose every 4-5 minutes, also the call log doesn't work and while I was watching a movie at work the phone light stayed lit during the whole film... I don't know what to do, is either go back to stock and recharge my phone every 4 hours or go back to kj6 aosp and deal with that annoying sound ..

stephen_w said:
Weird issue. I know you didn't mention it in the OP, but are you over or under-clocking at all?
I'm somewhat with airflup on this - it seems to be a hardware issue. I am saying that based on the fact that I've not heard of anyone else having this issue on GB ROMs. It could be something funky with one of the chips in the phone but only manifests in the GB ROMs. It's weird but not unheard of.
I've not attempted this so someone tell me I'm an idiot for thinking about this, but what if you flash a stock GB ROM followed by the modem from KD1 or whatever Froyo ROM you're using to see if the problem is still there?
Click to expand...
Click to collapse
Kernel is stock no under nor overclocked, btw what's the modem's role on the galaxy s 4g can this be the issue, I have never changed it but what if I do, can it help in any way, thank for all the help...

The modem is the radio for your phone to communicate with the cellular service. People change the modem file to see if they get better speeds in their area. Check the dev section, there's a whole thread containing just the modem files to flash.
I don't know if it will makea difference but it certainly couldn't hurt to try.
Sent from my SGH-T959V using XDA App

[Warning] Ice Cream Sandwich OS Bricks

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.

Serious issues trying to flash new rom!

Ok, I have an AT&T HTC One X. I have already rooted the phone and I have been running Venom Rom successfully for quite some time now. I decided I wanted to give some other roms a try today and I am running into some weird issues that I can't seem to figure out. To clarify my set up, I am not trying to run any custom kernels or anything that would potentially cause the issues I am experiencing. The roms I have tried and had these issues on are King Kang, Paranoid Android, and CM 10 official. With each the issues are always the same. First of all, I can't even type anything because Android Keyboard keeps force closing. Secondly, none of my hardware keys work at all except the back key, volume rocker, and power (home and recent apps do not function at all except to vibrate). Basically it leaves the phone completely unusable. I have gone back to Venom Rom for now because I have NEVER had any issues out of it. If anyone has any ideas why I am being plagued with these issues I would appreciate some feedback because I can't seem to find anyone else experiencing these kinds of issues honestly. Also I might add that I used a method to downgrade my HBOOT to, I believe, 1.09 instead of 1.14 because of the need to flash kernels separately with 1.14. My phone has worked flawlessly installing any ICS roms. This seems to only happen with JB roms. Thanks for your help in advance guys!

Factory reset in TWRP, and wipe Dalvik and cache before flashing any new ROM?
And to confirm, you are flashing the respective boot.img extracted from each ROM file, every time you've flashed a new ROM?

redpoint73 said:
Factory reset in TWRP, and wipe Dalvik and cache before flashing any new ROM?
And to confirm, you are flashing the respective boot.img extracted from each ROM file, every time you've flashed a new ROM?
Click to expand...
Click to collapse
Yeah, I of course did a factory reset and wiped cache and dalvik.
As far as the boot.img, I was under the impression that was only necessary for those with HBOOT 1.14 which is why I reverted my HBOOT. That was the only reason I have read anywhere to have the extract the boot.img. I am not new to Android or rooting.

guitarjuggalo said:
Yeah, I of course did a factory reset and wiped cache and dalvik.
Click to expand...
Click to collapse
If you don't tell us, we don't know. Its a common mistake, and better to ask, rather than the possibility of your issue just being something simple like not wiping.
guitarjuggalo said:
As far as the boot.img, I was under the impression that was only necessary for those with HBOOT 1.14 which is why I reverted my HBOOT. That was the only reason I have read anywhere to have the extract the boot.img. I am not new to Android or rooting.
Click to expand...
Click to collapse
Ah, I see I read that part too quickly. Confirm on the hboot screen that you are in fact on hboot 1.09, since you seem unsure.
And you are on TWRP, not CWM right?

Yea he wouldn't even boot up if he was on 1.14...
OP, are you doing a titanium backup?
Sent from my One X using Tapatalk 2

redpoint73 said:
If you don't tell us, we don't know. Its a common mistake, and better to ask, rather than the possibility of your issue just being something simple like not wiping.
Ah, I see I read that part too quickly. Confirm on the hboot screen that you are in fact on hboot 1.09, since you seem unsure.
And you are on TWRP, not CWM right?
Click to expand...
Click to collapse
Yes, I am on 1.09 for sure and using TWRP.

InflatedTitan said:
Yea he wouldn't even boot up if he was on 1.14...
OP, are you doing a titanium backup?
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
No, I haven't done a titanium backup. When things didn't work for whatever reason in any of those roms I just went back to the nandroid backup I had for Venom Rom that I did before jumping to any of those roms.

That's odd... usually a 100% fresh install comes out with good results lol.
Sent from my One X using Tapatalk 2

InflatedTitan said:
That's odd... usually a 100% fresh install comes out with good results lol.
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Yeah, it is very weird. I have never encountered these kind of issues. I have been using android since the original G1 on T-Mobile and haven't encountered issues with roms this horrible. Installing any of those roms makes my phone pretty much unusable. All 3 of them (haven't tried others) exhibit the same issues. Android keyboard force closes over and over again and won't ever pull up, and the home and recent apps buttons don't work at all. Also just about any Google app or service I tried to use was crashing out.

What are you using to download?
Sent from my One X using Tapatalk 2

InflatedTitan said:
What are you using to download?
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Downloading through wi-fi on my computer and sending it to the phone via USB. Also dried downloading directly to the phone over wi-fi. Results are all the same.

So, it appears that nobody has an answer?

Did you check the md5 of the zip before flashing?
I had a problem where the Rom would install fine but issues loading. Md5 of the zip on my pc was good but was bad on my sdcard. Got messed up while transferring I guess.
Also try updating to latest twrp
Sent from my HTC One XL using xda app-developers app

Make sure you aren't flashing 4.2 gapps on a 4.1 ROM. That could cause a lot of Google app FCs.
Sent from my One X using xda app-developers app

lauterm said:
Make sure you aren't flashing 4.2 gapps on a 4.1 ROM. That could cause a lot of Google app FCs.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I officially feel retarded. Thank you so much! That was indeed the issue. FML lol :good: :victory:

Its amazing that gapps controls so much that it even screwed my hardware keys with the wrong version. I really appreciate all the suggestions guys.

vzw s3 random reboots when downloading a file or moving files.

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