Related
Wanted to get a discussion going over a much debated and discussed topic....flashing ICS roms with ICS kernels. I want to know the forums specific attempts so we can better understand user errors versus software errors versus hardware errors.
I bring this up as I went from el29 to fc07 a while back and have been on ICS since. I am now on FC22 courtesy of agat63, which I flashed over calks fc18 v2 from. Before that I went from stock rooted fc15 to calks. This was all done using either rogue recovery fc07 or rogue recovery fc22 and using calks format all zip or modified format all zip.
Does it seem this was all "lucky"? I have a feeling many of these brick issues are due to people trying to flash between an AOSP type rom to another and/or using ROM Manager to do so. So lets hear it . . .
Sent from my SPH-D710 using XDA
wow, finally an official thread to discuss this rare issue......
Burn
10char
Wow a troll in xda. No way....
http://troll.me/images/futurama-fry/not-sure-if-trolling-or-just-retarded.jpg
Sent from my SPH-D710 using XDA
The bricking is related to (I think) data partitioning in the ics cwm recovery. If you wipe anything, something is most likely going to go wrong.
Sent from my SPH-D710 using Tapatalk
Overstew said:
The bricking is related to (I think) data partitioning in the ics cwm recovery. If you wipe anything, something is most likely going to go wrong.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
That's what I'm trying to boil down to....I have done bith wipes and zip formats, yet no issues....some methods or ROMS are leading into this so I'm hoping the brickers out there can give some feedback on exactly what was flashed and on what ROM, along with some success stories to try to figure out the issue.
Sent from my SPH-D710 using XDA
I dont mind firing up the Pc to run Odin, it justifies the 500+ I spent on it 4 months ago.
phatmanxxl said:
I dont mind firing up the Pc to run Odin, it justifies the 500+ I spent on it 4 months ago.
Click to expand...
Click to collapse
Agree, love Odin. Just wanna stop the brick posts and hope we can formulate a solid practice on how to prevent it.
Sent from my SPH-D710 using XDA
dante32278 said:
Agree, love Odin. Just wanna stop the brick posts and hope we can formulate a solid practice on how to prevent it.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Someone said once the source is released the risks should be minimal.
Also true....but with all the leaks going around and flashaholics it'd be good to have some guidelines til then, other than speculation. "I believe in science."
Sent from my SPH-D710 using XDA
Overstew said:
The bricking is related to (I think) data partitioning in the ics cwm recovery. If you wipe anything, something is most likely going to go wrong.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
In addition,
CM9/AOSP/AOKP seem to increase brick chances.
CMW Touch espicially with ROM Manager is espicially dangerous and should not be touched.
zonlicht said:
In addition,
CM9/AOSP/AOKP seem to increase brick chances.
CMW Touch espicially with ROM Manager is espicially dangerous and should not be touched.
Click to expand...
Click to collapse
This is what I hear the most. Has anyone else had success with flashing stock ROMs via clockwork on a stock(ish) ICS ROM? By this I mean based off fc07/15/18/22 (calk/agat63/goodness) and not CM9/AOKP/etc...
Sent from my SPH-D710 using XDA
Hey guys, I got a Nexus a few months ago and passed the Epic to the g/f (which I regret). Anyway, I have AOKP 35.1 on it and she is having issues. Maybe I forgot some Epic flashing routes.
The phone has EI22 baseband and I am looking to find the best g/f friendly rom (one where I can flash for her and have zero problems).
What do you think is the safest set up?
*Its been a while since I flashed on the Epic. I am on EI22 and I see EL30 is the newest build for GB. Do I need to use odin to get that, or can I just flash on top of EI22?
**I see FC09, is that the newest official?
Try cm7 or the peoples rom. The peoples is TW based it really is a matter of taste. I have my wife on CM7 which she loves she hates TW.
Sent from my Kindle Fire using Tapatalk 2
tazfanatic said:
Try cm7 or the peoples rom. The peoples is TW based it really is a matter of taste. I have my wife on CM7 which she loves she hates TW.
Sent from my Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
She prefers TW, and I was thinking the Peoples Rom. Where i get lost is all of the MTD, BML stuff. I dont remember having all of those options before.
What is the process to go to the Peoples from where I am? AOKP with EI22... I think EXT4 (is there a way to check?)
Neckberg said:
She prefers TW, and I was thinking the Peoples Rom. Where i get lost is all of the MTD, BML stuff. I dont remember having all of those options before.
What is the process to go to the Peoples from where I am? AOKP with EI22... I think EXT4 (is there a way to check?)
Click to expand...
Click to collapse
If you're on aokp you are on mtd... fc09 is the newest ota release... if she likes tw then clean gb el30 (she will be bugged by update message) or the peoples rom 2.2 (fc09) would be the best way to go...
Backup with Titanium Backup, download The People's ROM v2.2 MTD, wipe data, cache and Dalvik. Flash, choose to use or not use the Sprint Connections Optimizer, sign in to her Google account to sync contacts, restore her third party apps and only data she absolutely has to have...like Angry Birds high score or something...lol.
Sent from my SPH-D700 using xda premium
kennyglass123 said:
Backup with Titanium Backup, download The People's ROM v2.2 MTD, wipe data, cache and Dalvik. Flash, choose to use or not use the Sprint Connections Optimizer, sign in to her Google account to sync contacts, restore her third party apps and only data she absolutely has to have...like Angry Birds high score or something...lol.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
You guys are awesome. I think that is why I miss the Epic. Thanks for the help, I will follow your instructions and get it rockin.
Stock
Seriously you have no idea what responsibility your taking on Keeping the phone rooted.
Sent From My Sprint Galaxy Nexus via XDA Premium
I agree with UBER 100%. If you're okay with being lectured each time her phone freezes or needs updated... Go for it, but your better off having her be pissed at Sprint for her phone issues than you.
I've put my wife's Epic back to Stock and life has been better. Just looking out for my brothers on XDA.
Sent from my SPH-D700 using XDA
ÜBER™ said:
Stock
Seriously you have no idea what responsibility your taking on Keeping the phone rooted.
Sent From My Sprint Galaxy Nexus via XDA Premium
Click to expand...
Click to collapse
What?!?! Lol... I have my wifes evo rooted, and that phone is WAY harder to maintain than this one... just put on clean gb... completely stable and she will have no problems... after flashing clean gb head over to general and grab the flashable build.prop update and you're good to go....
The People never have to worry about updates.
TPR 2.2!
Sent from my SPH-D700 using xda premium
ÜBER™ said:
Stock
Seriously you have no idea what responsibility your taking on Keeping the phone rooted.
Sent From My Sprint Galaxy Nexus via XDA Premium
Click to expand...
Click to collapse
CM7 and call it a day no maintenance needed. And my wife loves it she hates stock.
kennyglass123 said:
The People never have to worry about updates.
TPR 2.2!
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Lol I would've suggested that, but it seems some phones just don't get along with tpr very well... if it was for him I would've suggested that... but to minimalize possible issue for a g/f or wife... clean gb takes the cake...
flastnoles11 said:
Lol I would've suggested that, but it seems some phones just don't get along with tpr very well... if it was for him I would've suggested that... but to minimalize possible issue for a g/f or wife... clean gb takes the cake...
Click to expand...
Click to collapse
So far all issues were resolved with clean installs, V 6 Supercharger or turning off the Optimizer because of bad 4G due to Sprint. 3000 downloads strong, seems pretty solid to me but I may be biased.
Sent from my SPH-D700 using xda premium
kennyglass123 said:
So far all issues were resolved with clean installs, V 6 Supercharger or turning off the Optimizer because of bad 4G due to Sprint. 3000 downloads strong, seems pretty solid to me but I may be biased.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Idk... I've never had not 1 problem... so not biased, truthful! I jusst didn't want him to put tpr on and then have to worry bout the supercharger and all that... but op, like I said, I have had not 1 problem with tpr, so if you'd rather her be on the latest, go with tpr cuz like kenny said,, all issues (if you even run into any) can be solved VERY easily....
Cm9 beta 3 with the touch wiz theme has been very good on my gfs phone
Sent from my SPH-D700 using XDA
ÜBER™ said:
Stock
Seriously you have no idea what responsibility your taking on Keeping the phone rooted.
Sent From My Sprint Galaxy Nexus via XDA Premium
Click to expand...
Click to collapse
I fully endorse this statement for the reasons mentioned in this thread. Seriously, my gf and I almost broke up over her rooted phone.
shane6374 said:
I fully endorse this statement for the reasons mentioned in this thread. Seriously, my gf and I almost broke up over her rooted phone.
Click to expand...
Click to collapse
Lol... no offense but if you almost broke up over a rooted phone the relationship musnt have been to great... my wifes phone is rooted and when something messes up she just asks me to fix it... if you don't mind fixing her phone all the time if she messes something up, you should be good to go (depending on if your girl blows things out of proportion or not)... no offense to anybody on any of this... if somebody loves you, they won't bite your head off for something going wrong with a phone!
flastnoles11 said:
Lol... no offense but if you almost broke up over a rooted phone the relationship musnt have been to great... my wifes phone is rooted and when something messes up she just asks me to fix it... if you don't mind fixing her phone all the time if she messes something up, you should be good to go (depending on if your girl blows things out of proportion or not)... no offense to anybody on any of this... if somebody loves you, they won't bite your head off for something going wrong with a phone!
Click to expand...
Click to collapse
She just gets nasty over some stupid crap sometimes. Plus, she travels a lot so I don't get much chance to work on the phone. Anyway, that was a year ago.
My lady likes to run whatever I am on. I find this useful for troubleshooting. If I can't recreate an issue on both, it's not a real issue. I made her sit on stock unrooted for a few days last month when she got a replacement phone from dropping it, and she couldn't wait to get back on an ICS rom. She made it through the random reboots on gb leaks, so anything out these days is easy for her to handle. It really depends on the individual. My techy ways have rubbed off on her over the years lol. She is smart enough to use her ipod (i know...) on wifi with a free messaging app to ask for help in the few situations that confuse her. She's a looker, does laundry, is a great mother, works, and cooks extremely well too! Needless to say we are getting married this July. I'm not sure exactly why I waited 14 years to ask her when I say it like that lol.
Sent from my SPH-D700 using xda premium
ÜBER™ said:
Stock
Seriously you have no idea what responsibility your taking on Keeping the phone rooted.
Sent From My Sprint Galaxy Nexus via XDA Premium
Click to expand...
Click to collapse
I cant agree with this strongly enough, though I may not have gone as far as saying no root.
Just remember, ANYTHING that goes wrong will be your fault, even if it has nothing to do with the phone itself (ie: tower down for upgrade, facebook update breaks the app, etc)
Am I the only one whom finds mostly all FF18 builds unresponsive at times? The touch keys don't work randomly... on the latest ota and the leak? Is this kernel related? I hope so.... I find myself constantly trying to find the right one buy no luck... this is perhaps a useless thread but I feel as if this ICS for phone is not even worth it at times
Sent from my SPH-D710 using Tapatalk 2
I get th. Touch key part as we.
Sent from my SPH-D710 using Tapatalk 2
Then use an aosp build
Sent from my SPH-D710 using xda app-developers app
cp320703 said:
Then use an aosp build
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Or this
http://forum.xda-developers.com/showthread.php?t=1748208
"PROJECT:PLACEBO" - now up to you
Sent from my SPH-D710 using xda premium
pyrostic said:
I get th. Touch key part as we.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Yeah that just makes using any ICS ROM a turn off at the moment... hope source can fix this.
Sent from my SPH-D710 using Tapatalk 2
cp320703 said:
Then use an aosp build
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
I love AOSP, I'm just not going that route at the moment till kernel is tweaked and modified now that they have source. Plus not all of us like to run aosp.
Sent from my SPH-D710 using Tapatalk 2
Why is it that all of these types of things are always categorized as ICS issues when the majority of us dont suffer from often if at all...?
Just make a checklist of consistent variables....
You
Your phone
Your settings
An operaring system succesfully applied to most of the world made by top-notch developers then supplemented by equally great devs that just always happens to brake for you =p
PhAkEer said:
Why is it that all of these types of things are always categorized as ICS issues when the majority of us dont suffer from often if at all...?
Just make a checklist of consistent variables....
You
Your phone
Your settings
An operaring system succesfully applied to most of the world made by top-notch developers then supplemented by equally great devs that just always happens to brake for you =p
Click to expand...
Click to collapse
I've had this on both stock and AOSP. I know my way around rooms and completely wipe before every flash even. its been happening to me since the early FF** kernel based builds. Frankly I think Samsung could have worked longer on this but something tells me it was rushed at the end.
Sent from my SPH-D710 using Tapatalk 2
Was mostly just flippin $#!t
Ive just been lucky I guess.. Ive got a big lib folder I carry around with me...
Any little problem Ive gotten has been easily remedied, and Ive never once had the weird problems that some get no matter what.
Maybe because mine was assembled in the states? Idk...
I do know that Placebo, placebo you want.. Worst case the flash doesnt take and you have to flash a backuo...
Most likely youll say, "this is a stock kernel?!"
Lol
Sent from my SPH-D710 using xda premium
PhAkEer said:
Why is it that all of these types of things are always categorized as ICS issues when the majority of us dont suffer from often if at all...?
Just make a checklist of consistent variables....
You
Your phone
Your settings
An operaring system succesfully applied to most of the world made by top-notch developers then supplemented by equally great devs that just always happens to break for you =p
Click to expand...
Click to collapse
Fixed for ya.
Agree 100% though.
Sorry to say this but I'm running my super nova rom and haven't had any problems what so ever. Nothing looked what you're describing at all. Any chance the phone is having a hardware factory issue since so many others have experienced the same thing?
No its definitely an ICS issue on certain devices. As it doesn't happen on Gingerbread roms based at all. Ive noticed certain users complain about the issue, maybe its different hardware models? Ill wait a bit to see what the developers cook up.... I'll give your super Nova ROM a try.. once all that fails I'll go get a device exchange LOL
Sent from my SPH-D710 using Tapatalk 2
Febby said:
No its definitely an ICS issue on certain devices. As it doesn't happen on Gingerbread roms based at all. Ive noticed certain users complain about the issue, maybe its different hardware models? Ill wait a bit to see what the developers cook up.... I'll give your super Nova ROM a try.. once all that fails I'll go get a device exchange LOL
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Lmfao.
When it fails, ill buy your broken phone for like 20 bucks, you say you flushed it so insurance covers it... Ill flash that same rom on your phone and have no issues =) everybody wins!
Sent from my SPH-D710 using xda premium
PhAkEer said:
Lmfao.
When it fails, ill buy your broken phone for like 20 bucks, you say you flushed it so insurance covers it... Ill flash that same rom on your phone and have no issues =) everybody wins!
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Who said anything about insurance? I'm very good friends with the store manager. He always performs a device exchange as long as it hasnt had water damage. And no, I'm pretty sure the issues I'm having are real as pressing the power button and having the unlock screen process done but captive buttons not work for 5 seconds or more, isn't a bad flash. Even on shubs one click to FF18.
Btw check list done.... settings are always left stock. Phone seems okay unless I can surgicly open it to check on internals lol... ! Yes I'm okay myself.other than my messed up fist from a drunk fist fight.
I've had the same issue with most ICS E4GT roms, and doubt it is anything user related. Don't pay attention to the trolls. I've fully wiped my phone and it made no difference. Hopefully someone can figure it out. It's pretty annoying having to turn the screen on a off twice to get the capacitive buttons working.
Febby said:
Who said anything about insurance? I'm very good friends with the store manager. He always performs a device exchange as long as it hasnt had water damage. And no, I'm pretty issue the issues I'm having are real as pressing the power button and having the unlock screen process done but captive buttons not work for 5 seconds or more, isn't a bad flash. Even on shubs one click to FF18.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
The only thing I notice is a bit of lag. I didn't have this issue before but it isn't so horrendous that I wanna destroy it. Ill be switching to a rom after I find one with absolutely no bugs. Oh an can I flash ICS to ICS now?
Sent from my SPH-D710 using Tapatalk 2
proxy0 said:
The only thing I notice is a bit of lag. I didn't have this issue before but it isn't so horrendous that I wanna destroy it. Ill be switching to a rom after I find one with absolutely no bugs. Oh an can I flash ICS to ICS now?
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
No you still can't flash ics to ics the emmc bug is still present
Sent from my Epic Blazer ICS 3G Touch
riggs170 said:
No you still can't flash ics to ics the emmc bug is still present
Sent from my Epic Blazer ICS 3G Touch
Click to expand...
Click to collapse
You think they'll push an update to the phone to fix the issue?
Sent from my SPH-D710 using Tapatalk 2
phelixian said:
I've had the same issue with most ICS E4GT roms, and doubt it is anything user related. Don't pay attention to the trolls. I've fully wiped my phone and it made no difference. Hopefully someone can figure it out. It's pretty annoying having to turn the screen on a off twice to get the capacitive buttons working.
Click to expand...
Click to collapse
Thank you, glad I'm not the only one who has this issue. The screen on and off is so far the only solution to this so far...
proxy0 said:
Oh an can I flash ICS to ICS now?
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
You can if you use the latest agat kernel built from source but remember not all developers have built in the new safe kernel! So you would always have to odin the kernel if it isnt baked with the ROM.
For reference, here is the link to source built kernel.
http://forum.xda-developers.com/showthread.php?t=1767421
riggs170 said:
No you still can't flash ics to ics the emmc bug is still present
Sent from my Epic Blazer ICS 3G Touch
Click to expand...
Click to collapse
That's been fixed now that we have source for ICS.
Sent from my SPH-D710 using Tapatalk 2
Ok heres my input. I believe that its a combination of software and hardware. Remember response time of soft buttons depends on how stable the rom is and also whats running at the time they where pressed. Ok say like you have a few apps it the background running and you turn off your screen. Once the screen come on the buttons may take a second to come on because the screen has more of a priorty than the soft button. Its all in how you look at it. And with apps running it slows that process down greatly because a combination of the proccesor and ram being used. Remember not notice but our soft buttons have a back light and they are press sensitive. So with them working together plus all the other stuff i explained timing would be off. But think about it. Lol is it really a depressing ordeal lol. I actually witness it and continue on without even thinking about it. Sorry for rambling lol
Im just wondering.... is there going to be another cm9 release or is the alpha 6 version the last one? I've noticed that cm10 is getting updated, so have they moved on? I also tried checking the cm website and can't find the E4GT section. Ive been holding out on rooting and setting up cm9 for something past alpha stage but im getting tempted too much to load alpha 6 version.
Sent from my SPH-D710 using xda app-developers app
whitelight said:
Im just wondering.... is there going to be another cm9 release or is the alpha 6 version the last one? I've noticed that cm10 is getting updated, so have they moved on? I also tried checking the cm website and can't find the E4GT section. Ive been holding out on rooting and setting up cm9 for something past alpha stage but im getting tempted too much to load alpha 6 version.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
There have been many nightlies that blow alpha 6 away. Go to the CM9 thread in the original development section for details...
Edit. It is very stable now and well worth a daily driver. Hope this helps!
Sent from my SPH-D710 using Tapatalk 2
I'd say its past alpha status. Pretty much an RC release, just haven't been officially merged into CM yet which chris41g has been working on. Like the guy above me said, very stable and a good DD.
Sent from my Nexus 7 using Tapatalk 2
Thats music to my ears. Im going to look for it. Is it still using the, i believe, modified gb kernel or is it using a ics kernel? Being in stock ics (ff18), would it be a problem?
Sent from my SPH-D710 using xda app-developers app
whitelight said:
Thats music to my ears. Im going to look for it. Is it still using the, i believe, modified gb kernel or is it using a ics kernel? Being in stock ics (ff18), would it be a problem?
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
CM9 never used a modified gingerbread kernel, we were flashing it with a gingerbread cwm repack to avoid the eMMC super brick bug.
Nightly 7-31 (which had no data due to a RIL change) was the last FF18 based kernel, initramfs was repacked with the startup scripts for AOSP etc. 7-17 Nightly was my favorite out of those.
Chris41G has had some source kernels out for awhile and starting with the 8/02 nightly they have been included. Early ones and the RC13 and older kernels had some problems with 4G and thanks to a ton of time Chris put into it the current ones shouldnt. Im runnin Chris's builds rather than the nightlies though.
So now there is no worries in the "super brick" thing?
Sent from my SPH-D710 using xda app-developers app
whitelight said:
So now there is no worries in the "super brick" thing?
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
The brick is triggered by a function being called with a particular switch but it only happens when the kernel or program has been compiled against a particular library. Thats a basic and slightly outdated view on the problem more info can be found here - http://forum.xda-developers.com/showthread.php?t=1644364
The Galaxy Note actually shipped with ICS and no work around and factory resetting was like playing russian roulette with the phone. The International is supposidly safe but based on the kernel source for FF18, our phone does not have a work around in place on FF18. The bug itself will never be fixed on our end. It requires flashing the eMMC firmware which can generally only be done by an eMMC partner.
Basically any time a partition is formatted without work arounds in place a bug in the eMMC controller could randomly corrupt storage at a very low level. These formats occur during Factory resets and when flashing a rom, etc.
Safe recoveries are worked around so that factory resetting and wiping partitions is safe. The danger still lies in scripts making the call, that as well has been worked around either blocking a certain call or replacing it. The final danger is zips, usually for roms with an unsafe Updater Binary. CM9 Alpha 5 for example does not have a safe updater binary, from what I know the stock roms don't either. There are recoveries setup to swap this element out to make flashing safe altogether. Can't tell you how common that is at this point I do not keep up.
Source kernels have more safeguards than just recovery repacked, but something is better than nothing as well.
RainMotorsports said:
The brick is triggered by a function being called with a particular switch but it only happens when the kernel or program has been compiled against a particular library. Thats a basic and slightly outdated view on the problem more info can be found here - http://forum.xda-developers.com/showthread.php?t=1644364
The Galaxy Note actually shipped with ICS and no work around and factory resetting was like playing russian roulette with the phone. The International is supposidly safe but based on the kernel source for FF18, our phone does not have a work around in place on FF18. The bug itself will never be fixed on our end. It requires flashing the eMMC firmware which can generally only be done by an eMMC partner.
Basically any time a partition is formatted without work arounds in place a bug in the eMMC controller could randomly corrupt storage at a very low level. These formats occur during Factory resets and when flashing a rom, etc.
Safe recoveries are worked around so that factory resetting and wiping partitions is safe. The danger still lies in scripts making the call, that as well has been worked around either blocking a certain call or replacing it. The final danger is zips, usually for roms with an unsafe Updater Binary. CM9 Alpha 5 for example does not have a safe updater binary, from what I know the stock roms don't either. There are recoveries setup to swap this element out to make flashing safe altogether. Can't tell you how common that is at this point I do not keep up.
Source kernels have more safeguards than just recovery repacked, but something is better than nothing as well.
Click to expand...
Click to collapse
Excellently said. Perfect!
Could you link my to Chris's latest/ most stable builds/kernels? Thanks
Sent from my SPH-D710 using Tapatalk 2
timmetal6669 said:
Excellently said. Perfect!
Click to expand...
Click to collapse
Thanks. I am sure anyone on my level with working memory and who has kept up can explain it a little better. Its been awhile for me. I know the mmc cap erase switch on the format call was the suspected culprit but in the end that didnt seem to matter it was then being looked at that the Android 4.0 kernel was compiled against a library for makeext4fs or something.
fabolousrmx said:
Could you link my to Chris's latest/ most stable builds/kernels? Thanks
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
I also tried searching for his rom builds but i get other things. I googled but the closes i got to was a kernel and not sure if it was for E4GT.
Sent from my SPH-D710 using xda app-developers app
whitelight said:
I also tried searching for his rom builds but i get other things. I googled but the closes i got to was a kernel and not sure if it was for E4GT.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
www.chris41g.devphone.org
Sent from my SPH-D710 using Tapatalk 2
I have a Samsung Galaxy SIII from AT&T (d2att ), and I have it rooted, running task650's AOKP, and TWRP 2.4.1.0 for recovery. It works fantastic, and I love it I have, however, been trying everything I can think of to try and get ktoonsez's kernel to work on it, for the features that his kernel offers. I am having a funky issue, which according to task, kt, and a few others on the boards, is device-related. It seems that my phone, individually, is the problem. This leads me to my question.
How feasible is it to get AT&T (or Samsung?) to replace my phone, based on the fact that there is something different hardware-wise between mine and the vast majority of other peoples?
It seems that nearly everyone who runs this combination of task and ktoonsez has nothing but good things to say, and I have yet to see anyone gripe about the same issues that I have had, and not be able to fix them, usually by a simple full wipe. I have tried to do full wipes with and without letting Google initialize/restore my account. I have tried going back to stock everything, and trying again. I have made sure to turn off Performance Control, so there should be no conflict there. I have tried setting up my phone in its entirety, restoring information, restoring apps with TiBu, and then installing the kernel. I have tried with and without deleting mpdecision. I am following all of the directions posted per OP for both threads, and with the gapps posted by task himself. Nothing works, and I end up in a glitchy boot loop almost immediately after flashing the kernel, even if my phone was running buttery stable before the flash.
I have come up with a couple things to try tonight, but if they don't work, I would like to pursue getting a new phone to replace this one. Is that an option?
You will need to do a warranty replacement through Samsung unless you have device insurance through att. But then you will be paying the deductable on it.
There are quite a few reports of people in ktoonsez's thread that stated they had to return their device and get a new one for his kernel to work. Not sure you searched good enough. But either way, you are not the first to have a device that cant run his kernel. I can assure you of that.
task650 said:
You will need to do a warranty replacement through Samsung unless you have device insurance through att. But then you will be paying the deductable on it.
There are quite a few reports of people in ktoonsez's thread that stated they had to return their device and get a new one for his kernel to work. Not sure you searched good enough. But either way, you are not the first to have a device that cant run his kernel. I can assure you of that.
Click to expand...
Click to collapse
Thank you. I may not have read it well enough Do you mean the deductible through Samsung or AT&T? And ho do I approach the warranty? I know, at least where I work, we wouldn't honor a warranty on something that was used for purposes outside of it's intended use (i.e. rooting). Granted, I don't work for a phone company
drinfernoo said:
Thank you. I may not have read it well enough Do you mean the deductible through Samsung or AT&T? And ho do I approach the warranty? I know, at least where I work, we wouldn't honor a warranty on something that was used for purposes outside of it's intended use (i.e. rooting). Granted, I don't work for a phone company
Click to expand...
Click to collapse
It would be the deductible through AT&T if you have device insurance. If going through Samsung, something would have to be a manufacturers defect in order for them to warrant a replacement device. I don't think either company will replace the device because you can't use a custom kernel. So you would need to get creative on your story before you go either route.
task650 said:
It would be the deductible through AT&T if you have device insurance. If going through Samsung, something would have to be a manufacturers defect in order for them to warrant a replacement device. I don't think either company will replace the device because you can't use a custom kernel. So you would need to get creative on your story before you go either route.
Click to expand...
Click to collapse
Time to get creative lol
Sent from my SGH-I747 using xda app-developers app
Settling In
I don't know if this could be a factor but, you will experience something commonly called a settling in period after installing a new kernel.
I have been through trying a couple other custom kernels for I747 plus all the progression of KT747 releases for TW ICS and TW JB since 9-23 release and have been through two phones due to warranty replacement. On both phones I have experienced significant settling in glitches for a while after flashing KT's or other kernels. These include crashing on boot, frequent screen freezes after boot, KTweaker settings not sticking, etc. These issues are far more extreme on first install of kernel than when flashing a new release to phone that already has kernel installed. First boot after first install can take about twenty problematic boot attempts to start behaving and it can take two or three days before kernel "settles in" and problems pretty much disappear.
In my feeble little mind, I envision the new kernel having to grow neurons into the guts of the phone hardware.
If you want to run this kernel and your phone will basically boot but, is all glitchy, I would say don't freak out. Have some patience, just keep rebooting, and give it time to settle in. For most the phone will straighten out in a few days.
Hope this helps.
bsam55 said:
I don't know if this could be a factor but, you will experience something commonly called a settling in period after installing a new kernel.
I have been through trying a couple other custom kernels for I747 plus all the progression of KT747 releases for TW ICS and TW JB since 9-23 release and have been through two phones due to warranty replacement. On both phones I have experienced significant settling in glitches for a while after flashing KT's or other kernels. These include crashing on boot, frequent screen freezes after boot, KTweaker settings not sticking, etc. These issues are far more extreme on first install of kernel than when flashing a new release to phone that already has kernel installed. First boot after first install can take about twenty problematic boot attempts to start behaving and it can take two or three days before kernel "settles in" and problems pretty much disappear.
In my feeble little mind, I envision the new kernel having to grow neurons into the guts of the phone hardware.
If you want to run this kernel and your phone will basically boot but, is all glitchy, I would say don't freak out. Have some patience, just keep rebooting, and give it time to settle in. For most the phone will straighten out in a few days.
Hope this helps.
Click to expand...
Click to collapse
I suppose that is possibly what's going on with mine, I'll give it a couple more tries
Sent from my SGH-I747 using xda app-developers app
Just an advice, make sure you restore everything to stock before you do
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
pcshano said:
Just an advice, make sure you restore everything to stock before you do
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I will be doing that In the meantime, any suggestions for how to explain my way into a warranty exchange? I thought about wiping everything, so it won't even boot, and saying that lol
Also, even if I flash back to stock, won't they be able to see that it had been flashed different before?
Sent from my SGH-I747 using xda app-developers app
drinfernoo said:
I will be doing that In the meantime, any suggestions for how to explain my way into a warranty exchange? I thought about wiping everything, so it won't even boot, and saying that lol
Also, even if I flash back to stock, won't they be able to see that it had been flashed different before?
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Just depends on how thorough the at&t rep is. You have to Odin back to stock, triangle away, unroot and factory reset for them not to know at all.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
drinfernoo said:
I will be doing that In the meantime, any suggestions for how to explain my way into a warranty exchange? I thought about wiping everything, so it won't even boot, and saying that lol
Also, even if I flash back to stock, won't they be able to see that it had been flashed different before?
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Do not intentionally brick your device. That could be just as bad as leaving your phone rooted when you take it in (depending if Samsung can see any part of the storage). As far as warranty exchange "excuse" that is on you to decide. Follow the post quoted below to help your chance at warranty exchange. This has been discussed quite a bit all over the place.
hednik said:
Just depends on how thorough the at&t rep is. You have to Odin back to stock, triangle away, unroot and factory reset for them not to know at all.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
You know, I've run tasks rom since it was still 4.1 and have always used the kernel provided in his rom. It runs great, and I wouldn't change it. My battery life and everything else is great. I can get 17 hrs with 3 hrs 34 mins screen time and have 20% battery left. I think trying to get a replacement device just to run a different kernel is absurd... just my .02 cents worth
Sent from my SGH-I747 using xda premium
G-Man. said:
You know, I've run tasks rom since it was still 4.1 and have always used the kernel provided in his rom. It runs great, and I wouldn't change it. My battery life and everything else is great. I can get 17 hrs with 3 hrs 34 mins screen time and have 20% battery left. I think trying to get a replacement device just to run a different kernel is absurd... just my .02 cents worth
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
I completely agree. I'm on tasks currently using his underwear kernel provided. I've also tried KT's kernel as well. Yes you can get more customization with KT's and his custom governor, but is it worth it to go through all the hassle to get a new device? I would say no. Like I said I've tried both kernels, I'm currently using tasks underwear kernel, I may try KT's again, may not. When I did before, I didn't notice a drastic difference between the two, esp not enough to warrant going through a device replacement.
Consider this. You are running tasks rom with absolutely no issues with the kernel he provides. Is that not good enough? I know it is for me. His rom is absolutely the most stable rom I've ever tried on any device. Remember it's just a phone. Just some food for thought.
Sent from my SGH-I747 using xda app-developers app
Probably right, but i don't always run task's ROM, either. My favorite ROM so far has actually been ParanoidKANGDroid, but I wanted 4.2.1, so I went to task. I'm actually running PACman right now, and for the time being, even his PC is broken
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
No matter which rom you are running, it's crazy to exchange a device (and having to lie to do it) just to run a different kernel... think about it...
Sent from my SGH-I747 using xda premium
G-Man. said:
No matter which rom you are running, it's crazy to exchange a device (and having to lie to do it) just to run a different kernel... think about it...
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Of course, but if it allows me more flexibilities and control over my phone and what it does, I'm all over that
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Bricking your phone would be the easiest way to get a new one and I've seen plenty of people accidentally bricking their i747 and getting a new one from Samsung. They won't even check if its rooted or not.
Check this thread: http://forum.xda-developers.com/showthread.php?p=34556189
Sent from my SGH-I747 using xda app-developers app
liltitiz said:
Bricking your phone would be the easiest way to get a new one and I've seen plenty of people accidentally bricking their i747 and getting a new one from Samsung. They won't even check if its rooted or not.
Check this thread: http://forum.xda-developers.com/showthread.php?p=34556189
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
That's a douche bag move.... pain and simple.
Sent from my SGH-I747 using xda premium
G-Man. said:
That's a douche bag move.... pain and simple.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
When the s3$ first come out, a lot of people were bricking them. Trying to root or installing an international ROM. I'm pretty sure Samsung staff was aware of that but they still gave free replacement. Some people even got a replacement from att or others carriers for free.
Sent from my SGH-I747 using xda app-developers app
If I do end up getting a replacement, can I take a nandroid, and restore it to the new phone?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app