Related
I've got an issue where all four capacitive buttons will not work in portrait mode but will work in landscape mode with the keyboard out. I've found some people had issues when they first got their phones but I've had mine for about 14 months and this just started happening. I'm on RandomRom right now with a fresh flash but I had this same Rom before I re-flashed and didn't have the issue. Also, the capacitive buttons used to work in CWM but they don't anymore. I'm going to try the new RandomRom later this weekend but I was curious if anyone else had this issue? I'm leaning towards a hardware problem even though it does work with the keyboard out but also the software has essentially remained unchanged so I'm lost.
Try a different kernel
sent from my touchwiz 4.5-ed epic
That was a kernel problem when the ei22 kernels first started being develpoed and has since been fixed. Flashing a newer kernel will take care of the problem
Sent from my SPH-D700 using Tapatalk
I flashed the 3.3 ThunderHawk ROM and re-flashed the Shadow Kernel (My device says 2.6.35.7-Shadow-EI22_v1.0.2+OC) but it persists. However it's reassuring that you both came up with the same solution; do you have a different kernel in mind that might work better? Thanks for your help.
I'm currently on iap's samurai.mtd.tw.warrior, you could try that if your on mtd. If not he has a bml version too
sent from my touchwiz 4.5-ed epic
Go into cwm, wipe data 3x, cache 3x, and dalvik cache 3x. then try installing cleangb rom and shadowkernel. See what results u get.
Sent from my SPH-D700 using xda premium
FaithOmitted said:
I flashed the 3.3 ThunderHawk ROM and re-flashed the Shadow Kernel (My device says 2.6.35.7-Shadow-EI22_v1.0.2+OC) but it persists. However it's reassuring that you both came up with the same solution; do you have a different kernel in mind that might work better? Thanks for your help.
Click to expand...
Click to collapse
I recommmend doing a clean install of whatever rom you want to use. An updated kernel should be included with the rom. Wiping 3 times is not neccessary as that was a bug with old cwm (3.x.x.x) 1 time is enough now. If the problem persits after a clean install download the newest samurai kernel. If that doesn't work try the newest shadow kernel (you can try shadow first if you would rather that kernel). Shadow is now on 1.0.4....
Sent from my SPH-D700 using Tapatalk
androidmaster1 said:
Go into cwm, wipe data 3x, cache 3x, and dalvik cache 3x. then try installing cleangb rom and shadowkernel. See what results u get.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
3 times is no longer neccessary as long as your on cwm 5.0.2.7... just throwing that out there...
Sent from my SPH-D700 using Tapatalk
Ugh...I flashed Samurai Kernel I believe. One of the ninja-esque titled kernles; no luck. I tried changing CWM to ACSRecovery 5; no luck. I tried flashing xBTx's "MostlyStock" ROM; no luck. I'll try the CleanGB ROM with both kernels now Also, I flash cache, Dalvik, and data 3x from habbit. Thanks again for your help
FaithOmitted said:
Ugh...I flashed Samurai Kernel I believe. One of the ninja-esque titled kernles; no luck. I tried changing CWM to ACSRecovery 5; no luck. I tried flashing xBTx's "MostlyStock" ROM; no luck. I'll try the CleanGB ROM with both kernels now Also, I flash cache, Dalvik, and data 3x from habbit. Thanks again for your help
Click to expand...
Click to collapse
if that doen't work... try this...it may work.. and i got this advice from kennyglass, it helped me alot. if you can reflash from odin, try repartitioning...that may fix it. "trial and error". that's what i would do. "but thats just me".
Okay I tried the CleanGB, with the stock kernel and Shadow kernel, and neither of those worked either! Does anyone know of a decent ROM to Odin? I don't want to download the stock from the Samsung website and have to re-root. Or, does anyone know of a gesture application that has "back" and "home" that can be mapped?
Besides "odin", u really got me there. If. U repartition...as much as u don't want to..it will completely reset everything. I would have to say, its better than continuining the guesing game...u know? That's my advice though.
Sent from my SPH-D700 using xda premium
androidmaster1 said:
if that doen't work... try this...it may work.. and i got this advice from kennyglass, it helped me alot. if you can reflash from odin, try repartitioning...that may fix it. "trial and error". that's what i would do. "but thats just me".
Click to expand...
Click to collapse
^^^^^^+1... if all else fails you probably have bad data converting over everywhere you go... odin the ec05.tar with the victory pit and make sure reboot and repartition is checked... then reroot and flash rom/kernel of your choosing and that should take care of your problem!
Sent from my SPH-D700 using Tapatalk
Would you recommend I just use this?
Flast, thanks for adding about pit file...forgot to add that in my reply.
Sent from my SPH-D700 using xda premium
FaithOmitted said:
Would you recommend I just use this?
Click to expand...
Click to collapse
Yep that's the one... if you have odin the victory pit should've been included with odin... put the ec05.tar in the pda slot and the pit in the pit... reboot and repartition checked and flash... then either root from there with the one click or accept update and root ei22... if you need help with the rerooting in anyway you can pm me... I'm always up till bout 5 or 6 in the morning cuz imma bit of an insomniac so anytime is fine and I will walk you through it as best as I can
Sent from my SPH-D700 using Tapatalk
I re-flashed through Odin 3 times but after each time my problem persisted. I followed the instructions exactly yet the reformat didn't change anything. I'm going to rip it apart tonight and re-seat everything and if that doesn't work I guess I have to live with it.
I've tried enabling the bluetooth both thru the pull down button and through the settings menu. It acts like it's starting to turn on, and then after a few seconds, just goes dark again.
Tried reboot. No luck.
Used ACS Recovery to do a pre-ROM wipe before flashing the new ROM.
Can't post in developers forum yet, so hopefully someone here can help. I read every page and every entry in the applicable forum for the ROM I flashed, but no one reported this problem or solutions.
Any ideas? I'd rather not have to flashback to stock or whatever. I've seen plenty of helpful posts for other bugs in the ROM. Just nothing for this. HELP!
Thanks,
Epic 4g
Gingerbread 2.3.5
ROM Revival MTD v2
JrWicked said:
I've tried enabling the bluetooth both thru the pull down button and through the settings menu. It acts like it's starting to turn on, and then after a few seconds, just goes dark again.
Tried reboot. No luck.
Used ACS Recovery to do a pre-ROM wipe before flashing the new ROM.
Can't post in developers forum yet, so hopefully someone here can help. I read every page and every entry in the applicable forum for the ROM I flashed, but no one reported this problem or solutions.
Any ideas? I'd rather not have to flashback to stock or whatever. I've seen plenty of helpful posts for other bugs in the ROM. Just nothing for this. HELP!
Thanks,
Epic 4g
Gingerbread 2.3.5
ROM Revival MTD v2
Click to expand...
Click to collapse
Backup that rom... flash a different rom... if bluetooth works then its that rom... btw I would strongly suggest not using acs recovery... use cwm 5.0.2.7... it is the officially supported recovery for our epics! Also acs does not play well with mtd roms so that may be your problem!
Sent from my SPH-D700 using Tapatalk
Get rid of ACS Recovery. It is not supposed to be used for MTD ROMs.
kennyglass123 said:
Get rid of ACS Recovery. It is not supposed to be used for MTD ROMs.
Click to expand...
Click to collapse
Bah humbug acs not play well with mtd blah!
I used it to convert to mtd when cyanogen first came and it worked just fine...... acs not the problem because even if he was on bml cwm5 before flashing he would have the same results.
Please stop blaming that recovery ^^
http://i1202.photobucket.com/albums/bb374/TexasEpic/Biggoron3.png
Sent From My Cyan Samurai
However once on mtd he shouldn't be using it
http://i1202.photobucket.com/albums/bb374/TexasEpic/Biggoron3.png
Sent From My Cyan Samurai
Biggoron said:
Bah humbug acs not play well with mtd blah!
I used it to convert to mtd when cyanogen first came and it worked just fine...... acs not the problem because even if he was on bml cwm5 before flashing he would have the same results.
Please stop blaming that recovery ^^
http://i1202.photobucket.com/albums/bb374/TexasEpic/Biggoron3.png
Sent From My Cyan Samurai
Click to expand...
Click to collapse
Maybe it worked for YOU but it is highly recommended to use CWM 5.027 to convert and note that if you want to convert and restore nandroid data it must come from 5.027.
Sent from my SPH-D700 using XDA App
kennyglass123 said:
Maybe it worked for YOU but it is highly recommended to use CWM 5.027 to convert and note that if you want to convert and restore nandroid data it must come from 5.027.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I'm pretty sire recoveries don't differ from phones... software is software its not a hardware difference just saying. How is your day going kenny?
http://i1202.photobucket.com/albums/bb374/TexasEpic/Biggoron3.png
Sent From My Cyan Samurai
Biggoron said:
I'm pretty sire recoveries don't differ from phones... software is software its not a hardware difference just saying. How is your day going kenny?
http://i1202.photobucket.com/albums/bb374/TexasEpic/Biggoron3.png
Sent From My Cyan Samurai
Click to expand...
Click to collapse
Ah always better after you brighten my day Biggie...lol.
BTW you know software is what drives the hardware. So any flash can go wrong at some point whether Odin, CWM, ACS, or Bonsai Recovery. Just sayin'...LOL. How you been?
Sent from my SPH-D700 using XDA App
kennyglass123 said:
Ah always better after you brighten my day Biggie...lol.
BTW you know software is what drives the hardware. So any flash can go wrong at some point whether Odin, CWM, ACS, or Bonsai Recovery. Just sayin'...LOL. How you been?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
GRRRR.... oh me I'm good I see what your saying but how would be able to flat out blame that software for all you know it was the rom .... okay end of argument no reason to keep up this fiasco anyways I'm not saying to not use the official cwm I'm just saying you can't blame the issue on the recovery... I've had tons of bluetooth issues concerning kernels never the recovery
http://i1202.photobucket.com/albums/bb374/TexasEpic/Biggoron3.png
Sent From My Cyan Samurai
I agree...just trying to narrow down the possibilities. Probably just needed to delete some bluetooth data files. I forget which ones force the bluetooth database to rebuild.
Sent from my SPH-D700 using XDA App
BRICKED
Thank u all for the replies. I DID use ACS to do the pre-rom wipe, but I thought CWM got changed afterwards, somewhere in the process of flashing the new ROM, etc. Funny that several of you mentioned the possibility of that being the issue. I went to boot into recovery to check, and my phone bricked. #*(#@$%&. So, I had to odin back to stock and then root again, then use Titaniun just to get to my pre-ROM settings. I'm just gonna go without the custom ROM for now.
JrWicked said:
Thank u all for the replies. I DID use ACS to do the pre-rom wipe, but I thought CWM got changed afterwards, somewhere in the process of flashing the new ROM, etc. Funny that several of you mentioned the possibility of that being the issue. I went to boot into recovery to check, and my phone bricked. #*(#@$%&. So, I had to odin back to stock and then root again, then use Titaniun just to get to my pre-ROM settings. I'm just gonna go without the custom ROM for now.
Click to expand...
Click to collapse
You mean sponged, not bricked. As long as there is life you are not bricked. Just grab the official CWM 5.027 and flash that. When doing conversions like that don't use ROM Manager and all should be well. When in doubt, wipe wipe wipe.
So heres a question:
Wgy do we have rogue recovery with the kernels when we cant flash ROMs from it.
Well we arent supposed to.
Why not repack the kernel with pure CWM and eliminate everyone form having to take the extra step of flshing back to CWM before flashing a new ROM
tramane said:
So heres a question:
Wgy do we have rogue recovery with the kernels when we cant flash ROMs from it.
Well we arent supposed to.
Why not repack the kernel with pure CWM and eliminate everyone form having to take the extra step of flshing back to CWM before flashing a new ROM
Click to expand...
Click to collapse
It won't matter as its the ics kernel that is the problem not rouge not Acs not cwm.....
Sent from my SPH-D710 using xda premium
I've been flashing with it. So have plenty of others. Some people bricked and they may have been using rogue but I wrecked a Honda once.... Its usually user error.
Sent from my SPH-D710 using XDA
You have a point.Im coming from original Epic 4g and im deffinetly confused about the kernels on Epic Touch.
This is what I mean:On original Epic they had kernels that you could flash on top of just about any rom in cwm or odin.But for Epic Touch im yet to find any kernels for it.Yes there are some stock EL29EG31,etc.. in wiki pages but thats it?
There are only two kernels on wiki that are non stock and they are Hitman's kernel and Rogue kernel,is that all we got?Og Epic had about 30 different nonstock kernels.
So my question is this:
1 Are Rogue and Hitman kernels come with their own cwm?
2 Are Rogue and Hitman are only two nonstock kernels?
3 Are all the other lernels on wiki EL29,EL26,EG30,etc.. are just stock or modified stock?
4 Can any of those kernels(besides ics Rogue of course) be flashed to any GB rom?
5 Are there any difference between different versions of Rogue and Hitman?Or latest is the best?
6 And if Rogue and Hitman also come bundled with their own version of cwm,what is the difference between those two cwm's?
I been on original epic xda forums for years and this **** is confusing,they should make a thread for new people.
Pretty sure its not user error, given that at least 3 of our most prominent bleeding edge devs bricked doing it. I made the mistake of believing it was user error, but all evidence points to the contrary.
The reason we have recovery on ICS kernels is there are things at this point that you can safely flash (basically, anything that doesn't wipe data). You can safely flash the visual voicemail .zips from rogue ICS recovery on AOSP roms, for example. But you can't flash a whole rom. You can make a nandroid for later restore from EL26 cwm. You can do a lot of things actually. Just don't flash an actual rom, and you should be fine.
lviv the reason there aren't many options on the ET for recovery is there aren't many devs that work with it. SteadyHawkin repacks rogue for us, and that's about it. We used to have a few others that did so, but now it's just SH. Personally I don't really care as rogue recovery works perfectly fine, and the reason we use stock CWM from EL26 is because it's all we need (no point in repacking another kernel since we all have access to that one, why waste the effort to put CWM on EL29 when chris41g did a fine job on EL26 and we are all using it for ICS flashing right now?). No point putting any more work into packing a diff recovery on ICS kernels when there's no source and there's a ton of fear of bricking going on.
I'm certainly no dev, but those are my observations.
I've said this before in the threads discussing the bricks. I am not a dev, so they can correct me.
I don't think the bricks had anything to do with the rogue repacks. I think it has to do with the way ICS handles the data partition. It seemed like the bulk of the bricks happened when we tried a factory reset, or wipe data and at that point we burned up our emmc chips.
Sounds crazy that that is possible just wiping a data partition, but it was pretty consistent.
At first I thought it was the temp touch recovery because that was what people were using when ICS was first leaked. I think most of us were also flashing it through the stock recover rather than odin or mobile odin. But, it began happening with rogue repacks as well.
Once the source drops these problems will probably clear up.
To the ops question, someone already answered. We can flash just about everything else with the repacks. I prefer the rogue repacks because he has streamlined them making them handier to use.
Sent from my SPH-D710 using Tapatalk
I understand that some have had luck and others haven't. It just seems to me that if it doesn't brick every phone then it can't be the recovery itself. There has to be another common denominator. I guess the issue is that until that common denominator is figured out it could be dangerous to use.
Sent from my SPH-D710 using XDA
Devi0124 said:
I understand that some have had luck and others haven't. It just seems to me that if it doesn't brick every phone then it can't be the recovery itself. There has to be another common denominator. I guess the issue is that until that common denominator is figured out it could be dangerous to use.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Exactly, I have been flashing things with the Rouge recoveries with no issues at all. I always use the Format all zip though and not the wipe in recovery, and that does wipe data so not really sure what is causing people to brick there phones.
I've never bricked using the ICS repacked recoveries, and I've used em to flash to different roms without format.zips before we knew it was even an issue, but now that I know this could potentially brick your phone, I won't be doing anything in recovery anymore except flashing themes or something that does not involve wiping. I'm not longer on ICS anymore though, as I see it completely pointless until official is out. Too much flashing, and not enough functionality ATM to see usable, runs kinda slow too, not complaining at all just stating why I'm not on it, when it's official it will be great, and the devs will be able to tweak the final build for some massive speed.
It is the data partition I believe, I'm not 100% sure on this but I think the wipe in recovery doesnt actually just wipe but reformats and resets the partition sizes whereas the wipeall zips just erase the data leaving the partitions alone
To simplify compare it to reformatting your harddrive in your PC.vs just factory resetting it or deleteing the data off of the drive leaving the OS intact but removing added on data
Sent from my SPH-D710 using xda premium
i flashed roms with rouge
FYI there's evidence of problems in the kernel source.
I9100 update4 seems fine - but apparently Koreans are having lots of problems with the SHW-M250S/K/L source drop, and also gokhanmoral of SiyahKernel encountered a bunch of bricks when he attempted to rebase on the SHW-M250* source code base.
I'm another original epic owner that just switched to the touch....I've rooted and flashed ics.....now over there on the epic 4g we don't have ics source either...but we have cwm that flashes roms ,backups, restores, we can even flash a ROM to boot from the sdcard to calibrate the sensors and update your prl....so why do we need source on the touch to acquire those luxuries?
XDA Premium
rujelus22 said:
Exactly, I have been flashing things with the Rouge recoveries with no issues at all. I always use the Format all zip though and not the wipe in recovery, and that does wipe data so not really sure what is causing people to brick there phones.
Click to expand...
Click to collapse
Same here as far as flashing things via rogue recovery. I even nandroided back to a gb rom from the fc24 repack, after wiping manually. I am not a fan of wipe all, i just like to verify my actions, so I do it manually. I am definitely not sure what is causing issues, but different phones have different actions on kernels in general, and our phones arent even near ready to handle them. That is why it is taking so long in order to push out official ICS, cause they need it to function on every phone, not just one. I am running mijjah XPLOD mini, and it works fantastic on my phone, but during charging it overheated until I flashed over the FD19 kernel.... Then problem solved. Maybe just a lot of these phones were first gen epic touches, and they couldnt handle the newest kernel..... I just bought my phone in december, so maybe my phone can handle it.... Just a something to ponder over.
Sent from my SPH-D710 using xda premium
Entropy512 said:
FYI there's evidence of problems in the kernel source.
I9100 update4 seems fine - but apparently Koreans are having lots of problems with the SHW-M250S/K/L source drop, and also gokhanmoral of SiyahKernel encountered a bunch of bricks when he attempted to rebase on the SHW-M250* source code base.
Click to expand...
Click to collapse
Thanks Entropy512 for the great response and insight! I hope more of the newbies (and some of the other hold outs) read your post. If guys like you, SiyahKernel, SteadyHawkin and some of other unbelievably fantastic devs can major issues and/or brick their device, and have found it to be the kernal (the other 'real' devs' have said that too!); than I for one and going with that! Thanks for all your work. Hopefully we'll get the final real source soon and than can pick through that.
-EViL-KoNCEPTz- said:
It is the data partition I believe, I'm not 100% sure on this but I think the wipe in recovery doesnt actually just wipe but reformats and resets the partition sizes whereas the wipeall zips just erase the data leaving the partitions alone
To simplify compare it to reformatting your harddrive in your PC.vs just factory resetting it or deleteing the data off of the drive leaving the OS intact but removing added on data
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I think you nailed it EK. If you watch what's going on in recovery when you flash the format all zip, it formats system which is not the same as a factory reset. After system it formats cache and dalvik. I haven't heard of any bricks flashing Calkulin's format all zip with an ICS recovery and then flashing an ICS rom. I've done it myself a few times but to be safe I now flash the EL26 kernel first.
i just picked up an e4gt today, i had one back in december that i rooted then sold. so im back and now there's a ton of stuff out there for this phone.
i just came over from the evo design where there is pretty much nothing happening, and before that i had an evo shift. i had cm7 installed on that and loved it.
so what rom do you guys suggest i use? i see there is cm9 available in alpha form, which has me very tempted.
im looking for a stable rom with no bloatware. and id love some advice.
BiffTirkle said:
i just picked up an e4gt today, i had one back in december that i rooted then sold. so im back and now there's a ton of stuff out there for this phone.
i just came over from the evo design where there is pretty much nothing happening, and before that i had an evo shift. i had cm7 installed on that and loved it.
so what rom do you guys suggest i use? i see there is cm9 available in alpha form, which has me very tempted.
im looking for a stable rom with no bloatware. and id love some advice.
Click to expand...
Click to collapse
Go with cm9 that darchstar has posted. It works great and I use it as my daily. After you do the base install I recommend nightly 7/24 and using the chris41g kernel b3 version with it. Great battery life and full functionality.
Sent from my SPH-D710 using xda app-developers app
Does cm9 wipe out cwm?
I'm paranoid to do anything without an option for recovery.
Sent from my SPH-D710 using Tapatalk 2
Here is your safest bet (as in super safe):
1. Download the el26 safe cwm kernel from the kernel repository in the sticky for this phone
2. Download cm9 6 and gapps
3. Follow cm9 6 download instructions
4. Let it boot
5. Use mobile Odin if you have it (highly recommend as it makes flashing so easy) and flash the el26 kernel that you downloaded in the kernel section from external sd...always check md5 sum first!
6. Once u see the blue light on ur phone in the LED, hold power+volume up to boot into recovery, once the sgs2 logo shows you can lay off the buttons
7. If you didn't do it in time or held too long, just pull the battery and go to recovery via power+volume up
8. You should be in cwm, flash the nightly of cm9, clear dalvik and cache, then flash the chris 41g b3 kernel and reboot
9. Enjoy
10. From this point forward you have a bomb rom and working recovery that will allow backup/nand/flashing safely.
Sent from my SPH-D710 using xda app-developers app
Look into Blu Kuban(team venum). No bloat, excellent help from dev. Plenty of options/mods/hacks/updates/themed apps/speed/great battery.
Ditto on Alex. Excellent support... Great battery life. It's themed so you should look at the screenshots and the video on the dev site.
Sent from my SPH-D710 using XDA
ok, i think im going to try the cm9 route, but i cannot find the correct kernel, or im doing something wrong. i got odin for android, and downloaded a couple of kernels i thought were the right ones and they didnt show up when i tried to select them with odin.
BiffTirkle said:
ok, i think im going to try the cm9 route, but i cannot find the correct kernel, or im doing something wrong. i got odin for android, and downloaded a couple of kernels i thought were the right ones and they didnt show up when i tried to select them with odin.
Click to expand...
Click to collapse
Here is the link for el26, first download.
http://forum.xda-developers.com/showthread.php?p=26295021
The chris41g kernel has its own thread in development, grab the zip format of the cwm b3 version.
Sent from my SPH-D710 using xda app-developers app
im not finding a b3 version. but i did download the first kernel from chris41g
StockCWM-EL26.zip
i hope thats correct. im going to do a nandroid backup and give it a shot later today. thanks for the help and advice!
its been several months since ive been flashing roms, and i find that it takes me a few days to get back in the swing of things before im flashing again.
The b3 kernel is at chris's goo which is linked to in this xda thread.
http://forum.xda-developers.com/showthread.php?p=28981308
Sent from my SPH-D710 using xda app-developers app
So I need to flash el26 kernel first, then I flash 41g-CWM-RC1-b3-0723.zip. then I can flash cm9 and gapps from recovery?
Sent from my SPH-D710 using Tapatalk 2
BiffTirkle said:
So I need to flash el26 kernel first, then I flash 41g-CWM-RC1-b3-0723.zip. then I can flash cm9 and gapps from recovery?
El26, boot to recovery, install cm9 per their install guide...after successful install, flash el26 again, wipe cache/dalvik, and install the chris41g kernel from there.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Sent from my SPH-D710 using xda app-developers app
dante32278 said:
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
ok, so i got cm9 on the phone. very excited, except for the launcher wont allow me to add widgets. wierd, same thing with my touchpad.
anyway i tried to flash el26 and it stalled at the splash screen, so i opened up recovery and wiped cache and dalvik, then installed the chris41g kernel. and no dice. aaaanyway. whats the benefit to the other kernels versus what i get with cm9? and is there a solution to my problem?
I read 4g is unreliable on Chris' new kernels
Sent from my SPH-D710 using Tapatalk 2
BiffTirkle said:
ok, so i got cm9 on the phone. very excited, except for the launcher wont allow me to add widgets. wierd, same thing with my touchpad.
anyway i tried to flash el26 and it stalled at the boot screen, so i opened up recovery and wiped cache and dalvik, then installed the chris41g kernel. and no dice. aaaanyway. whats the benefit to the other kernels versus what i get with cm9? and is there a solution to my problem?
Click to expand...
Click to collapse
I get that problem whatever I wipe the dalvik cache
Sent from my SPH-D710 using Tapatalk 2
well, im not sure what to do now. i love cyanogenmod, and id put up with a few hiccups if i could. but it looks like i wont be able to use this as a daily rom. very disappointing...
so, i might try the blu kuban rom.
at this point i want a debloated stable rom. im back to a rooted stock rom with el29.
i just dont want to brick my phone, i have insurance and can take it in to swap it out. its just a waste of time if i can avoid it.
any other suggestions?
BiffTirkle said:
well, im not sure what to do now. i love cyanogenmod, and id put up with a few hiccups if i could. but it looks like i wont be able to use this as a daily rom. very disappointing...
so, i might try the blu kuban rom.
at this point i want a debloated stable rom. im back to a rooted stock rom with el29.
i just dont want to brick my phone, i have insurance and can take it in to swap it out. its just a waste of time if i can avoid it.
any other suggestions?
Click to expand...
Click to collapse
Start with thread #1 on the attached link.
http://forum.xda-developers.com/showthread.php?t=1625535
To Install
Boot to recovery
Make an NAND Backup
Wipe the phone (with the Format All X2 script)
Flash Part 1
Boot the phone
Go to the updater (Under put things back to stock) and install Part 2 (Two part install is to finish theming Talk)
Reboot and Enjoy
When I did this I went to CWM to flash this through odin. Rom works very smooth. There is a ton of information in the thread but that should get you started.
First a little background. I am not new to the android world whatsoever. I don't post much but have been lurking for years. I had a Verizon GS3 and just recently switched to T-Mobile a few days ago and obviously bought a T-Mobile GS3. My vzw phone had no problems. But for some reason my T-Mobile phone will not boot any kernel I try to flash. Roms flash fine but when I flash a kernel everything goes fine in recovery but my phone won't boot past the splash and I end up having to restore a backup. I know I'm flashing the right kernels. I am on touchwiz based ROMs and haven't tried any aosp Rom because for the first time ever I actually prefer an OEM skin to aosp. So basically am I missing something obvious. Anyone else having thus problem. On Verizon I had to root and unlock the bootlosder. From what I understand tmobiles bootliader was not locked down and all I had to do was root. Like I said. I've tried every touch wiz Rom and every touch wiz kernel with each Rom and none will boot past the splash screen. I always wipe dalvik and cache but even tried wiping data every time too and keep getting the same result. Any input would be appreciated. . Thanks in advance.
Sent from my SGH-T999 using xda premium
Shouldn't need to do any wiping of any kind. I only use AOSP/AOKP, though. May I ask why you even bother with custom kernels? They honestly seem like a waste of time to me.
Im just flash happy. Like to try them out. I've been on Verizon for many Years and am used to the developers over there. I'm still getting used to the devs over here. Don't know any of there work. I'm sure its all good though. Been using imoseyons lean kernel since the thunderbolt back in the day and have stuck with them. Just my personal preference. I'd like to try some of tmobolrs kernel devs work but like I said I can't get a single one to boot.
Sent from my SGH-T999 using xda premium
What kernels have you tried to flash? There are a couple that have ICS builds. Also, what version of CWM are you using?
I've tried all the tw kernels. Every single one with 2 different ICS tw ROMs. I'm not using the leaked jb tw. I'm stickung with the more stable ICS ROMs for now. I just don't understand. I've tried every one. I've been flashing a long time and don't get it. Im kinda new to Samsung though. First Samsung was the galaxy nexus. Didn't ever use Odin with it. Does anyone flash kernels with Odin. Maybe I should try that. And to answer your question I've tried twrp and the latest version of cwm from rom manager. And of course I'm using the ICS TW version of the kernels im trying.
Sent from my SGH-T999 using xda premium
It could just be your phone doesn't like them. There is another guy on CM10 and AOKP that can't get custom kernels to boot either.
Sent from my Nexus 7 using Tapatalk 2
The kernel source code was never released for any build from UVALH2 and beyond. So most of our kernels will only work with UVALEM and UVALG1 builds.
We got kind of lucky I think and ktoonsez att kernel was brought over and works. I think there's one or two others that work now too.
As far as described here go I think we've got some of the best! For an outstanding rom you should try FreeGS3. It works with most of the kernels and is an awesome stable rom. If you want a later build try wildcards XquiziT v70 based on UVALH2. Use ktoonsez kernel with it.
And just to note, the stock kernel is surprisingly good. So give it a fair shot as well. Though I can definitely see some potential advantages of custom ones as well.
Sent from my SGH-T999 using xda app-developers app
Thanks for all the info. But now I can't even get any other ROMs to boot. I don't get it. I keep having to restore my Xquizit v20 back up. Its driving me nuts
Sent from my SGH-T999 using xda premium
jasonpantuliano said:
Thanks for all the info. But now I can't even get any other ROMs to boot. I don't get it. I keep having to restore my Xquizit v20 back up. Its driving me nuts
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Have you done full Wiping?
Wipe Data/Factory Settings
Wipe cache and dalvik
Flash Rom
Fix Permission
Reboot and don't touch it for 10 minutes
Reboot.
Wipe cache and dalvik
Flash Kernel (Must be compatible with ROM)
Fix Permission
Reboot and don't touch it for 10 minutes
Reboot.
See if this will work. Sometimes you have to let it breathe so it can adjust itself.
Have you tried uding odin to flash MrRobinsons root66 UVALH2? This will take you to fresh full stock plus root. Then try roms again.
Sent from my SGH-T999 using xda app-developers app
Whatever you do................
Be sure to double check before you flash that kernel. Had my first SGS3 for 12 days before hard brick set in. Terrible disease it is.......! I had to adopt a replacement shortly after to cope with the pain of the loss. Back on my feet again now though and soarin' higher than giraffe vagina on the things I learned in my days off for mourning. I can tell ya I've personally flashed the lean kernel and kt-747 with no issues. My problems were with siya mainly.
Guys, I have a serious problem.
It's similar to the one of the thread-opener.
The diference is that I cant get ANY ROM to boot, WITH the stock kernel.
And i do like the guide says: wipe/factory reset, wipe chache, wipe dalvik cache and then flash the ROM.
Everything works fine til the ROM finished flasing and runs a reboot.
My S3 shuts down screen, then turns screen on with the "Samsung Galaxy SIII-GT-I9300" and then thats it!
All i can do is to go in download mode or recovery mode. I can also flash CWM and so on, but after flashing ROMs it won't boot!
Is it possible that i broke the device by formating internal sd-card with the stock recovery tool?
Did it, after I tried to install Wickedv6 ROM and after both times when it rebooted it just reinstalled stock ROM. So i thought, ok delete the internal sd-card, so no stock ROM on it any more.
Also tried this ROM: http://forum.xda-developers.com/showthread.php?t=1875923
Same problem.
Also tried to fix the problem by rooting and then flashing ROM. No help.
Please help guys!
Best regards
ke-ironman said:
Guys, I have a serious problem.
It's similar to the one of the thread-opener.
The diference is that I cant get ANY ROM to boot, WITH the stock kernel.
And i do like the guide says: wipe/factory reset, wipe chache, wipe dalvik cache and then flash the ROM.
Everything works fine til the ROM finished flasing and runs a reboot.
My S3 shuts down screen, then turns screen on with the "Samsung Galaxy SIII-GT-I9300" and then thats it!
All i can do is to go in download mode or recovery mode. I can also flash CWM and so on, but after flashing ROMs it won't boot!
Is it possible that i broke the device by formating internal sd-card with the stock recovery tool?
Did it, after I tried to install Wickedv6 ROM and after both times when it rebooted it just reinstalled stock ROM. So i thought, ok delete the internal sd-card, so no stock ROM on it any more.
Also tried this ROM: http://forum.xda-developers.com/showthread.php?t=1875923
Same problem.
Also tried to fix the problem by rooting and then flashing ROM. No help.
Please help guys!
Best regards
Click to expand...
Click to collapse
This isn't the I9300 forum, but if you flashed a T999 rom, you bricked your phone.
Aerowinder said:
This isn't the I9300 forum, but if you flashed a T999 rom, you bricked your phone.
Click to expand...
Click to collapse
Wow, you scared the **** out of me
But i just tried to flash stock ROM: http://forum.xda-developers.com/showthread.php?t=1646610
It worked out!
What is the right forum for my GT-I9300 to post then?
And why isn't any other ROM working?
The forum you got that stock rom from is the international one. This is the US Tmobile T999 forum. The two phones are NOT compatible.
Only flash, well...anything, from that forum. Our roms will brick yours and vice versa.
Sent from my SGH-T999 using xda app-developers app