Related
Hi,
I had a few questions about kernels...hope someone can help me in answering these...
I am thinking of trying out the Netarchy kernel on my Nexus S, but i was just wondering is there anywhere I can download the stock kernel (so that if anything does go wrong i dont have to do a full nandroid restore?)
Also, when installing a new kernel does that wipe data (of course I will make a backup etc before installing it, but should all my settings and apps etc remain intact normally?)
what impact does an OTA update have if i am running a non stock kernel? so say i am using Netarchy's kernel, and google releases a new OTA update...will i still be able to install the update? If i do, will it revert to stock kernel?
Thanks in advance,
brownmonkey said:
Hi,
I had a few questions about kernels...hope someone can help me in answering these...
I am thinking of trying out the Netarchy kernel on my Nexus S, but i was just wondering is there anywhere I can download the stock kernel (so that if anything does go wrong i dont have to do a full nandroid restore?)
Also, when installing a new kernel does that wipe data (of course I will make a backup etc before installing it, but should all my settings and apps etc remain intact normally?)
what impact does an OTA update have if i am running a non stock kernel? so say i am using Netarchy's kernel, and google releases a new OTA update...will i still be able to install the update? If i do, will it revert to stock kernel?
Thanks in advance,
Click to expand...
Click to collapse
I'm not aware of anywhere that the stock kernel is available for download so doing a NANDroid backup is really your best option. If you have anything that deviates from stock (kernel, rom, theme, even just deleted stock apps) it will prevent you from being able to successfully update from an OTA.
You can find a lot of information about all the available kernels here just scroll down to the third post and you'll find the info.
Finally, just as a note of personal opinion, getting OTA updates is a little overrated. If you run a custom ROM, the OTAs will be included in those ROMs eventually so you won't have to worry about restoring a stock ROM just to get the updates.
kenvan19 said:
I'm not aware of anywhere that the stock kernel is available for download so doing a NANDroid backup is really your best option. If you have anything that deviates from stock (kernel, rom, theme, even just deleted stock apps) it will prevent you from being able to successfully update from an OTA.
You can find a lot of information about all the available kernels here just scroll down to the third post and you'll find the info.
Finally, just as a note of personal opinion, getting OTA updates is a little overrated. If you run a custom ROM, the OTAs will be included in those ROMs eventually so you won't have to worry about restoring a stock ROM just to get the updates.
Click to expand...
Click to collapse
Thanks for the quick answer. I had read that post before (it was actually how i came to discover kernels ). The reason why I was asking about the OTA is because I actually use the stock ROM but was just thinking about trying out the Netarchy kernel just to see what its all about. Hence if there is an OTA update, and i am running a different kernel to the stock, is the only way for me to incorporate the update by flashing the new stock rom and then reinstall the netarchy kernel?
Also, if i install it, do you know if it wipes data/apps?
Thanks
brownmonkey said:
Thanks for the quick answer. I had read that post before (it was actually how i came to discover kernels ). The reason why I was asking about the OTA is because I actually use the stock ROM but was just thinking about trying out the Netarchy kernel just to see what its all about. Hence if there is an OTA update, and i am running a different kernel to the stock, is the only way for me to incorporate the update by flashing the new stock rom and then reinstall the netarchy kernel?
Also, if i install it, do you know if it wipes data/apps?
Thanks
Click to expand...
Click to collapse
I apologize as I forgot to mention that part of your question, I'm sick with the flu and a little out of it on some cold medications lol. You only lose data and apps when flashing if you wipe the /data partition in mounts and storage and this is not required nor is it recommended when flashing a kernel. Sorry for answering out of order, but I thought I should clear that up first. As to the other question, you have it correct; you would need to flash the new update ROM and then flashing a new kernel.
I should also note that whenever you install a new ROM, you will need to reflash a custom kernel. This is because the vast majority of ROMs released include a kernel and when you flash them it will overwrite whatever kernel you currently have.
Finally, if you have any other questions you can always feel free to post them on that thread. I'm the one who wrote it and I check it often to try and answer questions as best and as quickly as I can. Happy flashing!
Are you using a custom ROM? Flashing CM7 has the stock kernel. There are probably other ones out there that includes stock kernel with them such as OTA.
Following up on my ported Bali kernel, here's a "ROM" to use it with, even though this really isn't much of a ROM, but more of a base for other themers to work with. It's a deodexed version of our update, and includes Root, as well as my ported Bali kernel. Other than that, nothing should be different from the Stock ODIN update.
My test had a broken browser app, so I pulled the stock browser for KG1 and deodexed it.
-BaliKG1 port from Dr. Honk's original Bali kernel
-Deodexed and rooted
-Flash script from ayoteddy's roms
-Updated Market, and Voodoo Control app by Supercurio to make use of the Bali kernel.
This does include Bali, but the name isn't changed in settings, this will be an update to the Bali kernel when I get motivated to do it, as that is just an asthetic change, it doesn't make a difference to the actual functionality of the kernel.
Download: http://www.multiupload.com/7DH5QLGGGW
It work's great i pulled the stock browser from KG1 ROM & put it on this KG2 & it work's perfect .
sduvick said:
Following up on my ported Bali kernel, here's a "ROM" to use it with, even though this really isn't much of a ROM, but more of a base for other themers to work with. It's a deodexed version of our update, and includes Root, as well as my ported Bali kernel. Other than that, nothing should be different from the Stock ODIN update.
My test had a broken browser app, so I pulled the stock browser for KG1 and deodexed it.
-BaliKG1 port from Dr. Honk's original Bali kernel
-Deodexed and rooted
-Flash script from ayoteddy's roms
-Updated Market, and Voodoo Control app by Supercurio to make use of the Bali kernel.
This does include Bali, but the name isn't changed in settings, this will be an update to the Bali kernel when I get motivated to do it, as that is just an asthetic change, it doesn't make a difference to the actual functionality of the kernel.
Uploading now, and I will post the link when it gets uploaded.
Click to expand...
Click to collapse
Can this be flashed over a rooted KG1? I tried doing so and I softbricked. I'm in the process of ODINing to stock KG2.
Also, is it safe to restore the data from a KG1 nandroid?
This should work to flash from KG1, you may have softbricked because you didn't check your mounts before and after flashing? restoring data should be fine, make sure you wipe your dalvik-cache from the advanced menu in CWM after restoring your data so that it rebuilds.
Yea, I don't think I checked my mounts. I'm ODIN'ing to KG2, then I'll be rooting, CWM'ing, and then flashing this ROM. Thanks!
Let me know if you're still having problems, I'll do my best to help you out!
I got it to work. Thanks for giving me the heads up on the mounts. I'm sure that's what softbricked me. Thanks again!
Sent from my SGH-T839 using XDA App
So is this rom up to speed compared to Smooth Maximus GingerClone? I'm reading form T-Mobile support that it actually lags a lot more than stock rom. Can this be flashed from GingerClone? Or must I odin first?
This can be flashed from GingerClone, as it contains both the updated firmware and the updated kernel. This is not really intended to be a rom persay, but rather to be a base for other themers and devs to make roms with. There's no speed changes, other than the lagfix that comes from Bali.
I'm using it now. It is pretty good already with bali implemented. Other than Media Room becoming an active process periodically, the stock experience is going well. The disability of the track pad will be very helpful outdoors.
Also got a soft brick trying this. Goes to the boot screen, and the motor buzzes once, then twice in a row, pauses then does the buzzing again.
Double checked the mounts before doing it.
Can still get into recovery, but trying to reinstall packages gives an invalid signature error.
Ugh...
Then it didn't flash correctly. You would have red CWM if this flashed correctly. Odin back to stock and try again, as if you can't get into recovery correctly, you can't do anything from there. You may want to redownload to make sure that you get a good copy.
That's what I did. Odin to stoc kg2, rooted, added cwm recovery (orange) then used same copy i downloaded earlier to flash. Worked properly.
Might be worth a test, that this might not be cwm flashable over stock kd1. Thats 2 reports of it happening so far, and i am not a beginner in flashing or following directions. Just an annoyance really, odin was painless to use. (Now, having to reinstall windows on a old pc laptop, so much fun /sarcasm) ;P
I've done it before just fine, flashing on the SK4G is different from most phones, if you don't check your mounts before and after, then it will not work.
All ROMs here include a KD1 or KG2 specific kernel in addition to their specific systems, so as long as mounts are checked, everything is overwritten. /system is entirely wiped in the flashing process, and a new kernel is flashed. There is no possible way, given a correct flashing procedure and a ROM that includes a kernel (which as far as I know are all the ones here) that this would not work to flash KD1 over KG2 or vice versa.
So far, this is the fastest rom I've tried, thank you for creating it! Even if its stock.
This had serve me fantastically. Wish the same was available for kj2
You mean like this?
http://forum.xda-developers.com/showthread.php?t=1328698
sduvick said:
You mean like this?
http://forum.xda-developers.com/showthread.php?t=1328698
Click to expand...
Click to collapse
Sadly, it is Bali/Voodoo-less.
Download link for this doesn't work. States the file has been deleted.
Does anyone have this file still?
Okay ... So I am about to update to the latest pushed version. Am rolling back to EE4 now and have the update.zip on my card. What about CWM? Does my current version I've been using with my Gummy Charged 2.1 work with it? I have the Imosyn (sp) kernel on my card that I will apply after the update to 2.3.6 for root, as I understand it.
Are there any Gummy's or anything that are going to work after the 'official' update?
You don't use CWM with the update. You use stock recovery.
Gummy is EP1W. If you install it over the OTA, you'll bring yourself right back down to EP1, and the update will be pointless. You can get lagfix by running imoseyon kernel. It's EP4. It's slightly older EP4, but I haven't had any issues.
shrike1978 said:
You don't use CWM with the update. You use stock recovery.
Gummy is EP1W. If you install it over the OTA, you'll bring yourself right back down to EP1, and the update will be pointless. You can get lagfix by running imoseyon kernel. It's EP4. It's slightly older EP4, but I haven't had any issues.
Click to expand...
Click to collapse
Thank you sir! Phone is updating now. I will apply the imoseyon kernel after it's done. Lagfix is the main thing anyhow, I can nuke the bloatness with my Titanium.
now I'm confused .... I no longer have CWM recovery. How am I to apply the imoseyon kernel via stock recovery? Can I just rename it as update.zip?
By taking it back to stock EE4 and installing the update, one of the things it did was restore the default recovery environment.
Go back into ODIN and install CWM, don't use Auto-Reboot. When it's done flashing, turn the phone off and hold the button combinations to start the phone into CWM. Flash iMoseyOn's kernel and you're done at that point.
trparky said:
By taking it back to stock EE4 and installing the update, one of the things it did was restore the default recovery environment.
Go back into ODIN and install CWM, don't use Auto-Reboot. When it's done flashing, turn the phone off and hold the button combinations to start the phone into CWM. Flash iMoseyOn's kernel and you're done at that point.
Click to expand...
Click to collapse
Ahhhh.... it's @ the Sammy screen and she's talking to me! Looks like all is good while it re-writes the allocation tables. Thanx again, appreciate the heck out of the help.
hmmm .... I guess all is not well ... I installed the kernel but I don't have root. I installed superuser from the market and then Titanium and when opening Titanium I have no root .... what next?
Chopstix9 said:
hmmm .... I guess all is not well ... I installed the kernel but I don't have root. I installed superuser from the market and then Titanium and when opening Titanium I have no root .... what next?
Click to expand...
Click to collapse
You SHOULD have root since the kernel is your root method. Have you tried restarting?
Sent from my SCH-I510 using xda premium
Yeah I sure have. The kernel I used is imoseyon_kernel_charge_gb_4.0.0 ... not rooted .... guess I need to drop five yards and punt (do it all over)
Edit: The one thing I did not do prior to rolling back to EE4 was to do the big 3 wipe of data/cache/etc ..... maybe that's the problem?
Chopstix9 said:
Yeah I sure have. The kernel I used is imoseyon_kernel_charge_gb_4.0.0 ... not rooted .... guess I need to drop five yards and punt (do it all over)
Edit: The one thing I did not do prior to rolling back to EE4 was to do the big 3 wipe of data/cache/etc ..... maybe that's the problem?
Click to expand...
Click to collapse
Try installing Superuser from the Market? imosyeon kernel should have installed binary and apk, but maybe it missed part of it. If all else fails, flash the superuser zip from CWM.
http://www.toms-world.org/android/download/http/Superuser-3.0.7-efgh-signed.zip
Yes, I had installed SU from the market and didn't have root. I had an SU zip saved on my desktop .... su-2.3.6.3-efgh-signed .... I put that on the sd and installed it and I am rooted !!
Thanx Again
I love Lagfix and Voodoo Sound, but I'm currently running the stock kernel. I read in other forum discussion that Samsung designs their kernels to work with their OS revisions. People have said they're getting the best performance with the stock kernel.
Until IMoseyOn releases a new kernel based on the EP4D source that was released, I'm going to stick with stock.
Just some food for thought.
KarateExplosion6 said:
I love Lagfix and Voodoo Sound, but I'm currently running the stock kernel. I read in other forum discussion that Samsung designs their kernels to work with their OS revisions. People have said they're getting the best performance with the stock kernel.
Until IMoseyOn releases a new kernel based on the EP4D source that was released, I'm going to stick with stock.
Just some food for thought.
Click to expand...
Click to collapse
My concern was updating to 2.3.6 and having root. (on the road all day and need wireless tethering so outlook is open on laptop) Using the tad older imoseyon kernel gave me that, plus lagfix, which I have liked since this phone hit the market. I'm good for now, I can always update when the latest and greatest comes out.
Chopstix9 said:
My concern was updating to 2.3.6 and having root. (on the road all day and need wireless tethering so outlook is open on laptop) Using the tad older imoseyon kernel gave me that, plus lagfix, which I have liked since this phone hit the market. I'm good for now, I can always update when the latest and greatest comes out.
Click to expand...
Click to collapse
I have root on the stock kernel bro. Did a clean EE4 install, skipped as much set up as possible, ran update.zip in stock recovery, ODIN flashed imnuts' latest CWM recovery with auto-reboot disabled, booted directly into CWM recovery, flashed the latest SU zip, then ran setup as normal. Boom! Root.
Completely clean install, latest OS and kernel, root, plus tether works and everything.
Right now I'm just waiting on imnuts' TW4 theme to launch (he's estimating Sunday). Hopefully I can install that theme over a debloated and deodexed version of the latest OTA. It won't be long before IMoseyOn releases a kernel built from source that enables Lagfix. That's really all I'm missing, since Voodoo Control lets me load most of Voodoo Sound on top of the stock kernel.
What I'm REALLY looking forward to is an release of Liberty for the Charge or something AOSP if we ever get the 4G RIL sorted out... This things will take considerable time though.
It just doesn't matter ... In all honesty I liked the feel of the Gummy GBE 2.1 better than this stock ginger ... but again, it just doesn't matter to me. Functionality is all I care about, it's only a damn phone !!!
I loaded up the debloated/deodexed/rooted all-in one package danalo posted in development, flashed perfectly and after a wipe in CWM on first boot seems to be running fine except for the poop
sent from my Acer Iconia A500 beast of a tablet via XDA app
KarateExplosion6 said:
I have root on the stock kernel bro. Did a clean EE4 install, skipped as much set up as possible, ran update.zip in stock recovery, ODIN flashed imnuts' latest CWM recovery with auto-reboot disabled, booted directly into CWM recovery, flashed the latest SU zip, then ran setup as normal. Boom! Root.
Completely clean install, latest OS and kernel, root, plus tether works and everything.
Right now I'm just waiting on imnuts' TW4 theme to launch (he's estimating Sunday). Hopefully I can install that theme over a debloated and deodexed version of the latest OTA. It won't be long before IMoseyOn releases a kernel built from source that enables Lagfix. That's really all I'm missing, since Voodoo Control lets me load most of Voodoo Sound on top of the stock kernel.
What I'm REALLY looking forward to is an release of Liberty for the Charge or something AOSP if we ever get the 4G RIL sorted out... This things will take considerable time though.
Click to expand...
Click to collapse
Care to make a thread of what you done? Files used? I want to re-root my Charge, but want to keep the latest ota update and radios. Main question is the "update.zip" file?
iMoseyOn has stated that he's not going to be developing kernels anymore due to him having to turn in all of his phones to his old employer. He's taken up a new job and because of that he has to return his phones, including the Droid Charge.
trparky said:
iMoseyOn has stated that he's not going to be developing kernels anymore due to him having to turn in all of his phones to his old employer. He's taken up a new job and because of that he has to return his phones, including the Droid Charge.
Click to expand...
Click to collapse
Yeah, I read last night. Awful news. I hope someone can just get us full Voodoo and EXT4 support. I don't absolutely need OC/UV, but it'd be nice...
In other bad news, imnuts is getting a Galaxy Nexus and only pledging support for the Charge for "a few more months."
Let's hope JT and the gang can get this RIL figured out, so we can at least have Team Douche to continue development with CM 7.2 and CM 9...
Sent from my SCH-I510 using xda premium
Damn. And I thought it couldn't get any worse with iMoseyOn leaving. And now we have imnuts leaving too? It just went from bad to worse in a matter of 48 hours!
Guess I better get used to just using the stock kernel.
Hello, all.
I have a T-Mobile Blaze 4G with rooted stock ROM (Gingerbread), flashed radio version T989UVMC6, manually debloated and dewizzed. I'm running Halo launcher and Busybox Free version 9.6.
Since almost the first day I've had this phone, it would occasionally force close the phone process, usually when hanging up the phone with the Bluetooth radio on and paired with an earpiece. It happened bone stock, rooted, after I changed the modem, whenever. It seemed to happen less often after I changed the modem. The process always starts back up, but the Bluetooth device connection and system sound controls are wonky (unusable) until the phone is rebooted.
The only thing that seems to stop it is running Zepplinrox's V6 Supercharger script. That, however, occasionally freezes the entire system when trying to open certain apps, requiring a reboot. I've run earch after search on this subject, and nobody else seems to have this problem. The only thing I haven't tried is wiping the whole thing and flashing a custom ICS or JB ROM. I tried Dark Knight ver. 8 and hated it pretty much instantly.
I have two questions. Number one; Will flashing a custom ROM fix this situation? I figure that this must be a problem with the crappy stock Samsung ROM. Number two; Which ROM is fully functional and stable? I'd really like to keep this phone dependable. I don't care about the latest and greatest funky cool features that are hit-or-miss at best. I just need dependable, fast and functional.
Since you have been having issues for a while, I would suggest starting fresh. With a few runs of black hole wipe from cwm. Add a run of the gremlin remover for extra cleanliness. Then a flash of the latest ICS rooted stock rom and kernel, for reliability.
Black hole wipe. http://forum.xda-developers.com/showthread.php?t=1721057
Gremlin remover, FSC http://forum.xda-developers.com/showthread.php?t=2218713
Uvmb1 ics ROM http://forum.xda-developers.com/showthread.php?t=2329081
Romman0 said:
Since you have been having issues for a while, I would suggest starting fresh. With a few runs of black hole wipe from cwm. Add a run of the gremlin remover for extra cleanliness. Then a flash of the latest ICS rooted stock rom and kernel, for reliability.
Black hole wipe. http://forum.xda-developers.com/showthread.php?t=1721057
Gremlin remover, FSC http://forum.xda-developers.com/showthread.php?t=2218713
Uvmb1 ics ROM http://forum.xda-developers.com/showthread.php?t=2329081
Click to expand...
Click to collapse
I'll definitely go for the rooted version! Does it matter what order in which the ROM and the kernel are flashed? Also, I take it from the name of the download link that I'll have to go through the process of de-bloating this thing again. S'okay, I actually enjoy that part, but I don't want to screw it up since I've not messed with anything newer than GB. Is there a good guide somewhere on the forum for apps that can be dumped safely? I know there was one for GB stock root.
Thanks for the response.
ionizd said:
I'll definitely go for the rooted version! Does it matter what order in which the ROM and the kernel are flashed? Also, I take it from the name of the download link that I'll have to go through the process of de-bloating this thing again. S'okay, I actually enjoy that part, but I don't want to screw it up since I've not messed with anything newer than GB. Is there a good guide somewhere on the forum for apps that can be dumped safely? I know there was one for GB stock root.
Thanks for the response.
Click to expand...
Click to collapse
Flash the ROM then the kernel, rewipe cache and davlik, then profit.
The most recent ICS debloating thread. http://forum.xda-developers.com/showthread.php?t=2183726&highlight=debloat
Romman0 said:
Flash the ROM then the kernel, rewipe cache and davlik, then profit.
The most recent ICS debloating thread. http://forum.xda-developers.com/showthread.php?t=2183726&highlight=debloat
Click to expand...
Click to collapse
A few more silly questions; Do I need GAPPS or is that just for CM? Aren't the CM 10 ICS nightlies fairly stable and relatively bug-free? I use CM7 on my Nook color and it's...okay... Just a few little annoying things pop up with that. To be honest, I like the idea of starting with a clean slate and adding stuff I like rather than pulling stuff out of the Samsung stock ROM, but the issues I've had with the Nook and CM7 have sort of scared me off. Your opinions?
ionizd said:
A few more silly questions; Do I need GAPPS or is that just for CM? Aren't the CM 10 ICS nightlies fairly stable and relatively bug-free? I use CM7 on my Nook color and it's...okay... Just a few little annoying things pop up with that. To be honest, I like the idea of starting with a clean slate and adding stuff I like rather than pulling stuff out of the Samsung stock ROM, but the issues I've had with the Nook and CM7 have sort of scared me off. Your opinions?
Click to expand...
Click to collapse
All the AOSP ROMs for the Blaze needs GAPPs. And yes. The latest CM10 nightly is stable. And you said CM10 ICS? CM9 is ICS and CM10 is Jellybean.
ionizd said:
A few more silly questions; Do I need GAPPS or is that just for CM? Aren't the CM 10 ICS nightlies fairly stable and relatively bug-free? I use CM7 on my Nook color and it's...okay... Just a few little annoying things pop up with that. To be honest, I like the idea of starting with a clean slate and adding stuff I like rather than pulling stuff out of the Samsung stock ROM, but the issues I've had with the Nook and CM7 have sort of scared me off. Your opinions?
Click to expand...
Click to collapse
The stock roms don't require gapps, but like Wolf said the cm10 jb variants do.
If your willing to use cm10 it is very stable. Just use the latest CM10 nightly and not the old stable version.
Here http://forum.xda-developers.com/showthread.php?t=1922935
The jb gapps 20121011 http://goo.im/gapps/gapps-jb-20121011-signed.zip
xWolf13 said:
All the AOSP ROMs for the Blaze needs GAPPs. And yes. The latest CM10 nightly is stable. And you said CM10 ICS? CM9 is ICS and CM10 is Jellybean.
Click to expand...
Click to collapse
Of course. I get a bit confused ever since people started talking about 10.1.
Okay, I went ahead and installed the stock rooted ROM with the stock kernel. Went through the debloating process (mostly, there are some apps that I'm not sure I can do without so they stay for now), and did some customizing. I'm seeing a bit more battery drain. Is this an issue with ICS or do I need to try another kernel or supercharge the phone? I also have this crazy issue with ROM Manager ver. 5.5.3.0. It tells me that there is an updated version of Clockworkmod Recovery, but it freezes when I try to flash from ROM Manager. Also, ROM Manager freezes when I try to reboot into Clockworkmod Recovery. Maybe I need to test a bit more before I mess with it any more.
**EDIT** Well, it looks as if my CWM recovery installation is corrupted. Can I reflash it without messing up my current ROM?
ionizd said:
Okay, I went ahead and installed the stock rooted ROM with the stock kernel. Went through the debloating process (mostly, there are some apps that I'm not sure I can do without so they stay for now), and did some customizing. I'm seeing a bit more battery drain. Is this an issue with ICS or do I need to try another kernel or supercharge the phone? I also have this crazy issue with ROM Manager ver. 5.5.3.0. It tells me that there is an updated version of Clockworkmod Recovery, but it freezes when I try to flash from ROM Manager. Also, ROM Manager freezes when I try to reboot into Clockworkmod Recovery. Maybe I need to test a bit more before I mess with it any more.
**EDIT** Well, it looks as if my CWM recovery installation is corrupted. Can I reflash it without messing up my current ROM?
Click to expand...
Click to collapse
Yes, with Odin, in the Dev forum
BTW, stay away from ROM Manager with our device. I've softbricked so many times because of it, it's ridiculous
jparnell8839 said:
Yes, with Odin, in the Dev forum
BTW, stay away from ROM Manager with our device. I've softbricked so many times because of it, it's ridiculous
Click to expand...
Click to collapse
Used this method http://forum.xda-developers.com/showthread.php?t=2011585, it worked well. Still have the battery drain issue, though. : /
ionizd said:
Used this method http://forum.xda-developers.com/showthread.php?t=2011585, it worked well. Still have the battery drain issue, though. : /
Click to expand...
Click to collapse
Since you have it setup, except for battery life. I would make a backup, then try a mod one at a time and see if any help. Also check the battery stats to see if anything of is seen. ICS will use more juice than GB, generally.
I would suggest Nos/direct injection, supercharger, or cross breeder. I would use one and see, then restore and try another.
http://forum.xda-developers.com/forumdisplay.php?f=565
Some time later...
I've been using the stock rooted ICS ROM since my last post, debloated and dewizzed of course, with Holo Launcher and T989UVMC6 baseband version flashed. Just over a month has passed, and I have good news!
I FREAKING LOVE THIS PHONE!!!
All of the force close and freezing issues have vanished, the phone's battery lasts almost as long as it did on GB, it's WAY more user friendly, and the phone is as fast as it ever was.
The bad news is that my wife got a GS4 and I lust after it now. : /
Thanks to everyone for their help!
My S7's firmware kicked the bucket yesterday and had the black screen of death. Currently out the house so I had no way to recover anything and ended up factory resetting via the recovery menu.
I was planning to root before all this happened but I was waiting for Samsung Pay in UK since I wanted to try it out, but I don't really want my device locking up again and having to reset it again.
I'm thinking of installing a custom ROM since it would prevent the issue from occuring again but I'm wondering if theres anything I should know before I do, since I've seen people say that the stock Samsung camera app is the best and that any stock custom ROM camera makes the quality bad. Is there anything else I should know?
Just install a different stock based ROM, BSODs are caused by a myriad of reasons ranging from Kernel instability to a system modification gone wrong.
Just make sure to stick with a stock-friendly kernel or the stock based kernel to avoid BSODs
Revontheus said:
Just install a different stock based ROM, BSODs are caused by a myriad of reasons ranging from Kernel instability to a system modification gone wrong.
Just make sure to stick with a stock-friendly kernel or the stock based kernel to avoid BSODs
Click to expand...
Click to collapse
Alright, thanks!
I'll probably install superstock ROM or some other de-bloated stock ROM then.
Superstock ROM + Superstock Kernel make for a killer combo, go for it
Revontheus said:
Superstock ROM + Superstock Kernel make for a killer combo, go for it
Click to expand...
Click to collapse
Sounds good! I'll install it tomorrow when I get back home
Would rather not lose my data than have access to Samsung Pay, so it's all good.