I having been trying to run the latest carbon (4.3) nightly
but every time i would reboot, it would get stuck at the static boot screen.
I'd have to do a full wipe of everything (data partition as well) and re-install just to get it to work again.
i tried several time with a few nightlies. I had an 8/27 cm 10.2 on my card and decided to give that a go. to my surprise
i had the same problem. so now i'm thinking WTF?
I decided to pull my sd card and boot. again it went to the boot screen. i pulled the battery and powered up again. this time it booted. (no sd card)
woohoo.
rebooted several times.. seems to be good to go.
so i did a full wipe loaded up carbon 0903 and same problem.
so i tried my fix. pulled sd card.. powered on. at boot screen. pulled battery and powered back up.
took a little bit of time. but it booted up.. success!
powered off, put the sd card back in and powered back up and it's working fine now.
rebooted several times with no issues.
i'm not sure what the problem is, but i googled and found many people across different phones & roms with the same issue. so it's a google issue.
but with our phone that's a possible fix.
give it a go and see what you get.
I had that problem once but flashing 09/03 seemed to fix it. Are you running a kernel with that or just stock carbon?
stock kernel. I didn't try any 3rd party kernels. I should have though. good idea
when you say "SDCARD" do you mean an extsdcard? I'm coming from a DROID-X, and sometimes get confused. This was happening on Mastamoon's 10.2 when people would boot from the extsdcard, so am wondering if that is the answer
goldsmitht said:
when you say "SDCARD" do you mean an extsdcard? I'm coming from a DROID-X, and sometimes get confused. This was happening on Mastamoon's 10.2 when people would boot from the extsdcard, so am wondering if that is the answer
Click to expand...
Click to collapse
I also came from the DX
yes i mean the external SD card that is by the sim card that you can take out.
I realize not all phones have sd cards that can be pulled. but i do know the problem happens on more than just the sgs3
oddly my father in law has the droid razr maxx and i loaded carbon 4.3 on his and had no problems with it (using multi-boot slot system)
however, what's interesting is i can reproduce both the problem and the fix for 4.3 roms (carbon & cm 10.2 at least)
1) full wipe (including data partitions) & install 4.3 rom (carbon or cm 10.2)
2) rom boots and works, configure it as usual
3) reboot
stuck at static boot screen? read on. if not then you probably won't be reading this post anyways
4) pull battery AND external sd card
5) battery goes back in WITHOUT sd card. power up.
if it is still stuck at boot screen, pull battery 1 more time.
6) battery back in and power back up. wait (could take a minute or two just wait, if your at like 10 minutes, then somethings wrong, try again)
If it boots into rom, then your golden. power off, put sd card back in and boot back up.
good to go..
again, i was able to re-produce both the problem and the fix on 0902/0903 carbon 4.3 and 0827 cm 10.2
I did download the 0904 carbon today and flashed and have had no problems, i have rebooted several times without problems
so i don't know if the "fix" from the day before resolved my issue or if i did a full wipe if the problem would come back.
i have not determined that yet and am happy with my set up (everything is working) so i'm probably not going to try unless someone needs me to verify.
hope it is helpful to someone stuck like i was.
All 4.3 ROMs do this to me.. As soon as I reboot I get stuck at the splash... Can't load anything. Have to do a full wipe and reboot.
Sent from my SCH-I535 using Tapatalk 4
Hmm, I run TW as my daily and every couple weeks I've run Slim 4.3. I haven't noticed any issues on reboots. Didn't notice this on the AOKP 4.3 alpha this weekend either. Is this reproducible on every 4.3 rom we have with your phone: whether its (un)official PA, Slim, CM, and whatever else there is?
Yup all 4.3
Sent from my SCH-I535 using Tapatalk 4
faehsemc said:
Yup all 4.3
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Is it a specific brand of sdcard that does this to you both? Have you tried another brand maybe or even reformatting that card? Its unusual that the sdcard would cause a freeze up like that every time.
I've done it with no SD card inserted at all. Complete clean install. Literally the only thing j had the sdcard in for was installing the ROM after a complete phone wipe. As soon as it was completed, I pull the SD card and do the initial ROM boot. It loads up just fine. I can do whatever with the ROM... If I reboot at all, I get stuck. This is all with stock kernel. I have not tried to use KT or any other 4.3 out there at all. My phone just does not like 4.3 as of right now.
Sent from my SCH-I535 using Tapatalk 4
---------- Post added at 10:57 PM ---------- Previous post was at 10:56 PM ----------
By complete. I mean COMPLETE. Full factory reset. If I would've flashed a 4.1 I would no longer have the /0 folder
Sent from my SCH-I535 using Tapatalk 4
faehsemc said:
I've done it with no SD card inserted at all. Complete clean install. Literally the only thing j had the sdcard in for was installing the ROM after a complete phone wipe. As soon as it was completed, I pull the SD card and do the initial ROM boot. It loads up just fine. I can do whatever with the ROM... If I reboot at all, I get stuck. This is all with stock kernel. I have not tried to use KT or any other 4.3 out there at all. My phone just does not like 4.3 as of right now.
Sent from my SCH-I535 using Tapatalk 4
---------- Post added at 10:57 PM ---------- Previous post was at 10:56 PM ----------
By complete. I mean COMPLETE. Full factory reset. If I would've flashed a 4.1 I would no longer have the /0 folder
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Yea, I would hold off from prolonged JB 4.3 use if I had those same issues too. I've only used custom kernels with 4.2 and 4.3 but idk how much a difference that would make. I have an inherent bias against using the stock kernel regardless of the rom.
faehsemc said:
All 4.3 ROMs do this to me.. As soon as I reboot I get stuck at the splash... Can't load anything. Have to do a full wipe and reboot.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
did you try doing it exactly as i listed above?
I loaded carbon 0905 and kt747 - 0831 and working fine (dirty flash)
but everything works great after i do what i listed above.
SlimSnoopOS said:
Is it a specific brand of sdcard that does this to you both? Have you tried another brand maybe or even reformatting that card? Its unusual that the sdcard would cause a freeze up like that every time.
Click to expand...
Click to collapse
i'm using a sandisk 32gb card.
as i mentioned if i follow the steps listed above, everything works great for me.
custom kernels and all.
Just tried with build 5.. No luck. Did the method in the op as well.. I have a 32 GB sandisk as well
Sent from my SCH-I535 using Tapatalk 4
No Problems Here
I've flashed a number of the nightlies (both clean and dirty update) and have not encountered this issue with a 32GB Sandisk external card. Odd that it doesn't affect all sg3's.
BTW, my device is d2vzw.
Its similar with the issue of Miui. There were some that just couldn't run MIUI... wouldn't boot at all
Sent from my SCH-I535 using Tapatalk 4
faehsemc said:
Its similar with the issue of Miui. There were some that just couldn't run MIUI... wouldn't boot at all
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
I never tried it with MIUI.
but the problem and fix/workaround worked for me on carbon, CM so at least for me it's a reproduce-able experience.
I don't think it's a bad SD card by any means. I think that something is trying to be written or read from the card and fails, so by removing the card and rebooting, the OS stops trying to do whatever it was trying to do and goes on with the boot.
edit: tonight i tried pa_d2vzw-3.99-L13N-20130906 and it did not do this this freezing at the boot screen stuff.
Slim 4.3 works for me.. Apparently the CM kernel doesn't like my phone. I flashed BMS.. I rebooted. The first initial reboot took 10 min and then all of the sudden it was up and working.
Sent from my SCH-I535 using Tapatalk 4
Related
I was going to post a quick reply in the actual thread, but since I'm a new member you know.... But I flashed Scott's cleanROM 4.1 earlier BEFORE he recommended using twrp recovery instead of cwm. Although I have no problems, would it be wise to download the zip file, and flash it using cwm? Would it just replace itself with the new recovery file? Would I need to delete anything after? I'm still new to root/flashing, so just want to be cautious. Thanks to any replies in advance.
Are you wanting to switch from cwm to TWRP? I just flashed the zip for twrp using cwm and it worked fine. Go for it.
Sent from my HTC One X using xda app-developers app
Same here just flashed it from cwm worked fine.
Sent from my Nocturnalized Beast
Worked just fine! Flashed twrp, wiped everything, and installed a fresh cleanROM 4.1 and goodies... Everything works flawlessly! And I gotta day, cleanrom Dev edition along with over clock and forced dual core mod turns my one X into a damn monster lol. Thanks for the help guys, I'm impressed with such quick answers.
E.Cadro said:
Same here just flashed it from cwm worked fine.
Sent from my Nocturnalized Beast
Click to expand...
Click to collapse
I did this as well and was up an running for a few hours. I plugged my phone in to transfer some files and now my SD card is wiped clean. I don't keep anything too important there but this is the second time this has happened. Once with CWM and now with TWRP.
kirbo20 said:
I did this as well and was up an running for a few hours. I plugged my phone in to transfer some files and now my SD card is wiped clean. I don't keep anything too important there but this is the second time this has happened. Once with CWM and now with TWRP.
Click to expand...
Click to collapse
There's a few threads about this and it had happened to me as well both with cwm and twrp but luckily not my entire sd card just random stuff. At this time no one seems to have a definitive answer to what causes it. I personally think it has something to do with the way the mount and un-mount of the sd card is being handled but its just a guess I have no proof that this is the case
Sent from my Nocturnalized Beast
I keep losing map data and nothing else, its very frustrating downloading a 500mb file multiple times a week. Oddly it never happened on stock rom rooted or not.
I think it has more to do with roms than anything else. I change tunes and movies out daily and never lost files on stock rom. I might return to stock for a week to test.
I know there is a thread similar to this already up, but my issue is a little different. I'm currently on Sasba Prime 3.0. Before that I was running a beta Jelly Time.
I've tried six different roms. Each freezes either in first boot or soon after. I know it is not the roms. I always do a full wipe. I have completely reformatted my sd. I've tried fixing permissions in 4ext and ROM manager.
Any suggestions? Because I am completely at a loss. Mainly because when I restore my backup of Sasba Prime, everything is perfectly fine with no issues.
Sent from my Inspire 4g using xda app-developers app
Try a different SD card...
ai6908 said:
Try a different SD card...
Click to expand...
Click to collapse
Tried it also.
Well, I finally got IceColdSandwich to flash okay. No force closes or anything. I'm never using Sabsa Prime again(No offense to the dev. It works great). It seemed like it was causing my issues. Someone had mentioned to me that some ROMs can take over a phone. I have no idea if this is true, but better safe then sorry I guess.
Here's what's going on. I flashed an aosp rom(all I ever use). Didn't like it and restored a previous rom I had backed up(I do this all the time). After the restore was done or so i thought the phone just rebooted and wouldn't load anything past the Samsung screen just black and then reboot followed by the same thing. I pulled the battery loaded up recovery manually and tried another backup I had and same thing. I finally ended up going back into recovery manually again and loaded up a rom. It worked but now the phone won't wipe I forget what it says when I try to wipe. Iv since loaded up several roms with the same wipe errors and all seems good. Just weird. I'm using twrp btw. Any ideas on what happened?
Sent from my Galaxy Nexus using Tapatalk 2
djj624 said:
Here's what's going on. I flashed an aosp rom(all I ever use). Didn't like it and restored a previous rom I had backed up(I do this all the time). After the restore was done or so i thought the phone just rebooted and wouldn't load anything past the Samsung screen just black and then reboot followed by the same thing. I pulled the battery loaded up recovery manually and tried another backup I had and same thing. I finally ended up going back into recovery manually again and loaded up a rom. It worked but now the phone won't wipe I forget what it says when I try to wipe. Iv since loaded up several roms with the same wipe errors and all seems good. Just weird. I'm using twrp btw. Any ideas on what happened?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Well, if you're GS3 is running then I wouldn't worry too much. However it couldn't hurt to make a nandroid, restore back to stock, and redo the STOCK>root>unlock>flash recovery>flash rom process. You may have messed something up along the way. Either way, happy flashing. PS: you should try out paranoidkangdroid if you love the AOSP experience. CM base with a ton of tweakability.
Anybody else ever experience anything like this?
Sent from my SCH-I535 using Tapatalk 2
A thought.... I flashed a wrong kernel once, I would see the boot animation, then black screen. Maybe you have a wrong kernel?
Sent from my PACmaned SCH-I535
My tablet (Samsung Galaxy Tab 2 10.1 Wifi) keeps rebooting randomly. I'm running CM 10.1.0-RC5, and I've had the same problem with RC2, RC3, and RC4. I'll just be using my tablet, happy as a clam, when *BAM* I'm looking at the Cyanogen startup animation. This seems to happen randomly; sometimes every few minutes, sometimes every few hours. Always several times a day. Memory doesn't seem to be an issue; it looked like I had roughly 50% free during one reboot (I was looking at the "Running Applications" screen in "Settings" when it rebooted).
Anybody else having this problem? Any possible solution? I love CM and don't want to start from scratch with the stock ROM again, but these reboots are driving me NUTS!
jqcaffeine said:
My tablet (Samsung Galaxy Tab 2 10.1 Wifi) keeps rebooting randomly. I'm running CM 10.1.0-RC5, and I've had the same problem with RC2, RC3, and RC4. I'll just be using my tablet, happy as a clam, when *BAM* I'm looking at the Cyanogen startup animation. This seems to happen randomly; sometimes every few minutes, sometimes every few hours. Always several times a day. Memory doesn't seem to be an issue; it looked like I had roughly 50% free during one reboot (I was looking at the "Running Applications" screen in "Settings" when it rebooted).
Anybody else having this problem? Any possible solution? I love CM and don't want to start from scratch with the stock ROM again, but these reboots are driving me NUTS!
Click to expand...
Click to collapse
try reinstalling this rom!
before installing zip from sd
do
clear data/factory reset
clear cache
go to advanced>wipr dalvic
flash the rom
again wipe dalvic cache.
after the rom starts, let it be as it is for 5 minutes. the rom needs som time to get stable, this avoides many FC's.
hit thANKS,
jqcaffeine said:
My tablet (Samsung Galaxy Tab 2 10.1 Wifi) keeps rebooting randomly. I'm running CM 10.1.0-RC5, and I've had the same problem with RC2, RC3, and RC4. I'll just be using my tablet, happy as a clam, when *BAM* I'm looking at the Cyanogen startup animation. This seems to happen randomly; sometimes every few minutes, sometimes every few hours. Always several times a day. Memory doesn't seem to be an issue; it looked like I had roughly 50% free during one reboot (I was looking at the "Running Applications" screen in "Settings" when it rebooted).
Anybody else having this problem? Any possible solution? I love CM and don't want to start from scratch with the stock ROM again, but these reboots are driving me NUTS!
Click to expand...
Click to collapse
Have you done any undervolting or anything? That can cause this.
If not you may try doing a full wipe and reinstall of the ROM. Clearly you've got something borked up that an update flash isn't fixing. A full wipe may solve your problem. It's a pain in the rump, but sometimes you have to do that.
Siddharth121 said:
try reinstalling this rom!
before installing zip from sd
do
clear data/factory reset
clear cache
go to advanced>wipr dalvic
flash the rom
again wipe dalvic cache.
after the rom starts, let it be as it is for 5 minutes. the rom needs som time to get stable, this avoides many FC's.
hit thANKS,
Click to expand...
Click to collapse
Ive been having this same problem for the past few days now also.
I tried reinstalling rom with these exact instructions and after installing some of the basic apps i use, the tablet restarted itself again.
Try a new kernel. The problem wil fly away. :screwy:
Sent from my HTC One X+ using xda premium
Siddharth121 said:
Try a new kernel. The problem wil fly away. :screwy:
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
any suggestion on which kernal to try?
Domino_13 said:
any suggestion on which kernal to try?
Click to expand...
Click to collapse
Never mind my post. I got my devices mixed up.
Sent from your phone. You should be careful where you leave that thing.
Plz mention which rom you are using?
Press thanks ppz, it makes me solve your issue as it was mine :thumbup::thumbup:
Sent from my HTC One X+ using xda premium
Siddharth121 said:
Plz mention which rom you are using?
Press thanks ppz, it makes me solve your issue as it was mine :thumbup::thumbup:
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
It started for me when I upgraded from CM10.1 M3 to CM10.1RC3 i think it was. I have tried upgrading to Rc4 and RC5 also but same problem with the rebooting.
I also tried to go back to M3 but it was also just rebooting randomly.
Before I upgraded to RC3, I never had a problem with the tablet.
Problem Fixed...Hopefully
Siddharth121 said:
try reinstalling this rom!
before installing zip from sd
do
clear data/factory reset
clear cache
go to advanced>wipr dalvic
flash the rom
again wipe dalvic cache.
after the rom starts, let it be as it is for 5 minutes. the rom needs som time to get stable, this avoides many FC's.
hit thANKS,
Click to expand...
Click to collapse
I tried this last night, and thus far, I haven't had any more problems. I've been running it hard, too; prior to the factory reset and reflash, it would have rebooted several times by now. Here's hoping.
I have a theory as to what caused my problems. Looking at the original CM zip that I used, I realized that it was a nightly build rather than a stable Release Candidate. Perhaps my problem was building on a non-stable foundation? At any rate, I flashed CM 10.1.0-RC5 last night, and it's working great.
To anyone else having this problem, remember to do a FULL CLEAR DATA/FACTORY RESET. Simply clearing the cache and flashing a new ROM wasn't enough. I recommend backing up your apps and settings with Titanium, then just going for the clean start.
Normal practice for rom flashing
It is in my, and many others experiences that a failsafe way to flash a ROM is as described below..
Note: this is assuming that you have already downloaded the rom you want and placed it on your sdcard/external-sdcard and that you have a custom recovery like clockworkmod or twrp...
Reboot into recovery
Make a backup of your current system
Tip: its always better to have a removable external_sdcard when doing any kind of root tasks but not needed
Now for the ROM..
1. go to mounts & storage and select it
2. Scroll down to the "format" section
3. Now select format system (and then yes)
4. Select format cache (and then yes)
5. Select format preload (and the yes)
6. Select format data (you get it)
If you don't have an external_sdcard don't format anything else and proceed to step 8
Now if you have a (removable) external_sdcard and you have placed the ROM and gapps on it, then you should;
7. Select format sdcard (the NOT REMOVABLE, internal sdcard space)
8. ***go back***
9. Install zip from sdcard/external_sdcard and proceed with your normal install procedure...
By doing the format methods before installing a new ROM, you're insuring that the ROM is writing to all freshly wiped partitions on your device and this will always be the most redundant way of making sure something did not get left over from your previous setup.
Most install.zips that the ROM is packed up in do perform the format of system, data, and cache during the install and usually it works fine but however, it is not always reliable.. By doing the few extra steps above, you will always know that the installation is a clean one and will greatly reduce problems like described above in this thread.. Why not just be sure?
---------- Post added at 07:24 PM ---------- Previous post was at 07:00 PM ----------
If you have done a "FULL WIPE" like I described in the post above and your device is still randomly rebooting..
Then it is most likely due to something having to do with the kernel.
There are many reasons why it could be triggering the "panic" feature in android but the most common ones are;
Over clocking.. Either your devices processor CPU OR GPU, cannot handle being scaled up to the frequency that the ROM sets it at, or
Unstable... The kernel that came with the ROM you are installing is not yet stable enough for daily use and is in need of more debugging/development.
jqcaffeine said:
I tried this last night, and thus far, I haven't had any more problems. I've been running it hard, too; prior to the factory reset and reflash, it would have rebooted several times by now. Here's hoping.
I have a theory as to what caused my problems. Looking at the original CM zip that I used, I realized that it was a nightly build rather than a stable Release Candidate. Perhaps my problem was building on a non-stable foundation? At any rate, I flashed CM 10.1.0-RC5 last night, and it's working great.
To anyone else having this problem, remember to do a FULL CLEAR DATA/FACTORY RESET. Simply clearing the cache and flashing a new ROM wasn't enough. I recommend backing up your apps and settings with Titanium, then just going for the clean start.
Click to expand...
Click to collapse
You had either an app or a setting that wasn't doing what it was supposed to. That is the only way a factory reset would fix it.
That also means the problem could have been fixed without the reset. You would have just had to isolate the error, which obviously is tough. Just keep that in mind if it happens again, immediately try to remember the last thing you changed, the last app that was updated, the last setting you altered, etc. Then maybe you can fix it faster without the hassle of the reset.
Glad its fixed!
Sent from my HTC Sensation using xda app-developers app
After flashing and reflashing the CM 10.1 rom, and it still giving me random reboots, I flashed a custom kernal today and it seems to have fixed the reboot problem I had.
Domino_13 said:
After flashing and reflashing the CM 10.1 rom, and it still giving me random reboots, I flashed a custom kernal today and it seems to have fixed the reboot problem I had.
Click to expand...
Click to collapse
Which kernel?
I'm very new to this kernel stuff, I got the hang of roms (I think) and I'm now using Cyanogenmod. I read somewhere it already includes it's own kernel, correct?
All roms come with a kernel as part of the install package. You can change to different kernels as well.
Right now for the t mobile phone i think there is just the stock cm kernel and albinoman887's kernel. The aokp roms probably have some other kernel tweaks in their stock kernels
Sent from my SGH-M919 using xda app-developers app
Don't forget DhollmenCM Kernel.
Posted from my Galaxy Tab 2 with CM10.1
I am Having the same prob with galaxy tab2 7.0(gt-p3100)
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