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
Related
Rooted...no issue there.
Installed ROM Manger.
Installed Clockwork Recovery from Rom Manager as I wanted to install a new rom.
Now when I boot, no matter what combination I hold down, it goes to the Android System Recovery screen and in the background is the white triangle, yellow exclamation point and little android guy.
I can move between the three ofered choices but pressing the power button (I assume this is the OK button) does nothing.
Thoughts / help?
Does your computer recognize it? If it does you should try adb download and see if you can get into download mode
Sent from my SPH-D710 using xda premium
Have you even tried pressing any of the soft keys, home button?
Sent from my SPH-D710 using xda premium
Just realized I posted the question in the wrong forum as well.
Computer makes a noise as though it knows it's connected, yet it doesn't show up and odin and kies don't find it either.
I think home button is select and power button is back, but I haven't used stock in a long time, so might be remembering incorrectly.
I suggest you don't use Rom Manager to install recovery. It doesn't work properly for this phone and could lead to non-recoverable problems.
Read this thread and you'll have references to everything you need to undo and start from scratch:
http://forum.xda-developers.com/showthread.php?t=1342728
THANKS!
What a doof........hit the home button and all is fixed!!!!!!!!!!!!!!!!!!!!
jfenton57 said:
What a doof........hit the home button and all is fixed!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
And leave stupid ROM manager alone it's crap on Samsung
Sent from my SPH-D710 using xda premium
I don't know for the life of me why people still use Rom manager to install roms.
I think they are probably HTC converts because nothing here is asking them to use ROM manager.
jordan2333 said:
I don't know for the life of me why people still use Rom manager to install roms.
Click to expand...
Click to collapse
Lazy lazy and most don't know how to do it correctly....
Sent from my SPH-D710 using xda premium
sfhub said:
I think they are probably HTC converts because nothing here is asking them to use ROM manager.
Click to expand...
Click to collapse
I came over from an Evo and believe me everything pointed to not use Rom Manager when I had my phone as well. I agree that if people took the time to read properly they would see that Rom Manager and a few other crazy things they do are not suggested. But they make sure to have time to post and read their threads when they screw up. Honestly with all the brick laying and blue light specials up in herrre. Do you really need to post your problem and how do you fix it...
His problem is one of 100 exactly the same in here and instead of searching and helping himself he did the same lazy thing that got him stuck in the first place. Then too lazy to find out how to work CWM. Quite sure he will be back again if he keeps up this route... @OP not trying to be an ass but just hate to see people who don't want to help themselves.
Sorry to hear that you've bricked OP. Hope you can get a replacement and get back into owning your phone.
Here's what I've done to avoid bricking since I am also somewhat new to the E4GT...
Read the forums on XDA.
Observed what others are doing that worked.
Didn't flash anything you are unsure of.
Became familiar with ODIN.
Stayed away from ROM manager.
Flashed using el29 rogue recovery only. (I've been successful with this so far, others say to use el26.)
Wipd cache/dalvik-cache/data/system.
Purchased mobile ODIN, $5 is better than the deductible to get a replacement.
Sent from my SPH-D710 using xda premium
I bricked but it was a bad recovery well not bad just messy team trolls recovery bricked me 2 weeks ago wiping Cache . But as always when u post questions like this here ur gonna hear it lol but searching helps.
Now if its hard bricked ud not even get to recovery at all just a blue light and a black screen that if is ur case unplug it cause it runs the battery super hot .
If not in that position than try power and volume down if it does not bring u to download mode to Odin another recovery if that don't work idk
Sent from my SPH-D710 using xda premium
sfhub said:
I think they are probably HTC converts because nothing here is asking them to use ROM manager.
Click to expand...
Click to collapse
The OG Epic uses ROM Manager just fine.
Sent from my SPH-D710 using Tapatalk 2 Beta-2
azyouthinkeyeiz said:
The OG Epic uses ROM Manager just fine.
Sent from my SPH-D710 using Tapatalk 2 Beta-2
Click to expand...
Click to collapse
That took a long time and a ton of porting. Pretty recent. Went through Eclair and Froyo without support.
The Root said:
That took a long time and a ton of porting. Pretty recent. Went through Eclair and Froyo without support.
Click to expand...
Click to collapse
Porting was needed for CWM recovery. Not ROM Manager. Support for ROM Manager comes from device devs, not koush. In the form of uploading vetted software, that doesn't corrupt. It is a universal starting point, not a fully functional product.
But regardless, I wasn't even talking about it's support. I was saying people other than ones with HTC devices can get into the habit of using ROM Manager.
Sent from my SPH-D710 using Tapatalk 2 Beta-2
azyouthinkeyeiz said:
Porting was needed for CWM recovery. Not ROM Manager. Support for ROM Manager comes from device devs, not koush. In the form of uploading vetted software, that doesn't corrupt. It is a universal starting point, not a fully functional product.
But regardless, I wasn't even talking about it's support. I was saying people other than ones with HTC devices can get into the habit of using ROM Manager.
Sent from my SPH-D710 using Tapatalk 2 Beta-2
Click to expand...
Click to collapse
I never used it even when there was support. Lol
Sent from my SPH-D710 using XDA App
Doesn't matter the recovery is in the kernel and rom manager will not work on this phone ....there is no separate recovery partition and ROM manager won't flash the recovery right on here since it's part of the kernel partition.koush doesn't really care he made it to temporarily flash a recovery like touch that might work if not for ics kernels... The thing is it doesn't work people should not rely on it like a crutch
Sent from my SPH-D710 using xda premium
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)
Im getting my ET4G on the 14th, So I decide to do some research on it (which is what everyone should do anyways) and I stumble upon the ICS kernel, data wipe hard brick, and I wonder to myself, Why hasn't the option to wipe data been removed from ICS kernels(cwm)? it would save alot of ppl (albeit ppl who don't know how to research first) alot of time and potentially money, hell i mean no one can even wipe in ICS anyways right? so why even allow the option until a workaround is found?
holy monky! so simple, yet brilliant. im sure somebody is gonna come along and say....nevermind..... good call though!
Sent from my SPH-D710 using xda premium
probably right, but hey, my phones (most likely) not gonna get bricked.
its a sad day when someone destroys a phone they just got, especially doing something simple like wiping the data partition.
maybe even just a warning when you wipe that it could brick your phone on ICS, shouldn't be that hard, its already got a confirmation dialogue
zeruth said:
Im getting my ET4G on the 14th, So I decide to do some research on it (which is what everyone should do anyways) and I stumble upon the ICS kernel, data wipe hard brick, and I wonder to myself, Why hasn't the option to wipe data been removed from ICS kernels(cwm)? it would save alot of ppl (albeit ppl who don't know how to research first) alot of time and potentially money, hell i mean no one can even wipe in ICS anyways right? so why even allow the option until a workaround is found?
Click to expand...
Click to collapse
ICS kernel source hasn't been released for the epic touch yet. So there's no way to remove the command that's causing the bricks.
Sent from my Galaxy Nexus using XDA
It's been done already on some kernels and other work arounds have already been found, until source drops.
This thread goes into exceptional detail. The devs and some users have gone to tremendous lengths researching the specific cause. I believe samsung actually threw in a little help as well. http://forum.xda-developers.com/showthread.php?t=1644364
Sent from my SPH-D710 using Tapatalk 2
times_infinity said:
ICS kernel source hasn't been released for the epic touch yet. So there's no way to remove the command that's causing the bricks.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
May be true but you can work around it. Chris41g and Dees_Troy did so with TWRP recovery by working around the command so it isn't called when you wipe data and by having a safe GB update-binary used when flashing zips. Also isn't sbrissens kernel safe?
Sent from my SPH-D710 using Tapatalk
slick_rick said:
May be true but you can work around it. Chris41g and Dees_Troy did so with TWRP recovery by working around the command so it isn't called when you wipe data and by having a safe GB update-binary used when flashing zips. Also isn't sbrissens kernel safe?
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
This is very true. The suppress_emmc_wipe feature implemented into ext4_utils along side the gb update-binary is a good alternative for now. Also, sbrissens kernel is safe, just not ready for prime time yet
Sent from my Galaxy Nexus using XDA
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 2 Wind Mobile GS3's and when I put any custom rom on my fiancees S3 when I am on the phone with her in between the conversation all of a sudden I will hear a loud noise that I can only describe as a transformer transforming in the speaker..It seems to be fine when it is running the stock Touchwiz with Root injected into it but as soon as I rom it the sound comes back. I was just wondering if anyone else has had this issue and was able to find a fix for it. Thanks for the help
What rom, kernel, and mods do you have on it?
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
What rom, kernel, and mods do you have on it?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Stockorama V2 with T-Mobile (Canada): Stock Kernel and no mods. I was using this as well and I never get the issues that my girlfriend is having. I am currently running Hyperdrive RLS14 with its stock T-Mobile Kernal and no mods and have no issues what so ever.
That's strange. Have you searched the rom thread to see if anyone else reported the same thing?
If they haven't, and you want to still use it, I'd backup and then wipe all data, including internal sd. Then flash the rom from a new download. Then test before adding anything back on.
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
That's strange. Have you searched the rom thread to see if anyone else reported the same thing?
If they haven't, and you want to still use it, I'd backup and then wipe all data, including internal sd. Then flash the rom from a new download. Then test before adding anything back on.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I looked for anyone reporting issues like mine and I didnt find any. I wiped the phone entirely and was unable to get it to work without the voice being all messed up. I think I may have to just keep regular Stock Root on the device for now but the thing that confuses me is the fact that my device is fine and hers isnt..
It could be a minor defect in a certain part, or just due to "no two chips are truely equal".
It is quite odf. Hopefully someone else may have an idea, but you may want to look into warranty options.
Actually, you could try flashing a custom kernel such as ktoonsez. See if that helps.
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
It could be a minor defect in a certain part, or just due to "no two chips are truely equal".
It is quite odf. Hopefully someone else may have an idea, but you may want to look into warranty options.
Actually, you could try flashing a custom kernel such as ktoonsez. See if that helps.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I tried the ktoonsez kernal and it still did it..I also put it to just pure touchwiz with root and it was worse then before..I am looking into warrenty options now because this is beyond weird now. Thank you for all the help with this!!
That may be your best option, especially if its doing it all stock now too.
If you wanted to try one more thing, you could see if flashing an audio mod would help. (beats ir something like that)
Can't remember what's available for our phone, but check the sticky in Themes and Apps section and you should find a link in there.
Sent from my SGH-T999 using xda premium