Related
I really wanna use this kernel/custom kernels, but I give up! Constant force closing and crashes for me Now I'm wondering, did I do something wrong during the root process? I rooted my device a couple weeks ago using this link: http://forum.xda-developers.com/show....php?t=1771687 (Root without tripping flash counter), followed by flashing Team Sonic's TouchWiz Rom, and then now, recently as of a little over a week ago I started using Cyanogen Mod 10. Did I miss a step in between which is causing so many problems with installing a custom kernel on my phone? Lean kernel worked earlier around the 8/20-25 nightlies, but now everything's pretty much a bust
It's a T-Mobile GSIII
No you didn't do anything wrong. A lot of the kernels aren't updated as fast as kernel changes in CM. Have you tried the latest nightly with the latest LK?
Sent from my SGH-T999
joshnichols189 said:
No you didn't do anything wrong. A lot of the kernels aren't updated as fast as kernel changes in CM. Have you tried the latest nightly with the latest LK?
Sent from my SGH-T999
Click to expand...
Click to collapse
I've tried all the latest kernels. Every kernel I've tried is compatible with the ROM I've tried it on.
isikh said:
I really wanna use this kernel/custom kernels, but I give up! Constant force closing and crashes for me Now I'm wondering, did I do something wrong during the root process? I rooted my device a couple weeks ago using this link: http://forum.xda-developers.com/show....php?t=1771687 (Root without tripping flash counter), followed by flashing Team Sonic's TouchWiz Rom, and then now, recently as of a little over a week ago I started using Cyanogen Mod 10. Did I miss a step in between which is causing so many problems with installing a custom kernel on my phone? Lean kernel worked earlier around the 8/20-25 nightlies, but now everything's pretty much a bust
It's a T-Mobile GSIII
Click to expand...
Click to collapse
if it was me, which btw am running CM10/LeanKernel, I would use odin to flash back to a rooted stock app, then install NEWEST CWM, and try again, I have had no issues EVER using the combo's that you are using. Also, I NEVER flash a kernel on a new rom until the rom has booted correctly, then reboot and flash whatever compatible kernel.
Good Luck.
TheAxman said:
if it was me, which btw am running CM10/LeanKernel, I would use odin to flash back to a rooted stock app, then install NEWEST CWM, and try again, I have had no issues EVER using the combo's that you are using. Also, I NEVER flash a kernel on a new rom until the rom has booted correctly, then reboot and flash whatever compatible kernel.
Good Luck.
Click to expand...
Click to collapse
Okay I'll do that, but tell me this. How did you come to CM10 exactly? What steps did you do? I want to see if you did something different from me and I may have sent wrong somewhere.
I simply rooted installed freegs3, wiped data and caches and all, then I flashed cm10. Was that the wrong way? Should I go back to stock and restart the process? Because right now for one, custom kernels are giving me strange issues. Also, a ktoonz kernel dev told me my log cat pointed towards corrupt partition or Rom, but I'm using cm10
How do I go back to stock basically? Can you link me to some guides and/or videos? I'm on the T-Mobile galaxy s3. The reason I ask is because I'm mobile and can't search for some reason but I'd like to read up on it before I do it
isikh said:
Okay I'll do that, but tell me this. How did you come to CM10 exactly? What steps did you do? I want to see if you did something different from me and I may have sent wrong somewhere.
I simply rooted installed freegs3, wiped data and caches and all, then I flashed cm10. Was that the wrong way? Should I go back to stock and restart the process? Because right now for one, custom kernels are giving me strange issues. Also, a ktoonz kernel dev told me my log cat pointed towards corrupt partition or Rom, but I'm using cm10
How do I go back to stock basically? Can you link me to some guides and/or videos? I'm on the T-Mobile galaxy s3. The reason I ask is because I'm mobile and can't search for some reason but I'd like to read up on it before I do it
Click to expand...
Click to collapse
I started here, READ EVERY LINE in a separate window, so you can reference back in forth between the windows. And do it STEP BY STEP. Once you are rooted and using the stock rom, back that up, so you can revert back to if you crash, once you have those 2 done, get the newest copy of Clockwork, install it. (by the way, the flash counter will tick you using Odin) so make sure you wipe the tick counter before installing any custom roms. Now get CM10 from the thread, install, do not flash the kernel until you have booted the first time, then reboot to recovery and flash kernel of choice. then your set. Now these are MY DIRECTIONS ONLY! and worked for me. So anyone want to add, feel free, or if I missed something, but do NOT slam me for trying to help, again this worked for me, may not for others, but it has been flawless for me. Hope this helps good luck.
Start here>>>http://forum.xda-developers.com/showthread.php?t=1746682
TheAxman said:
I started here, READ EVERY LINE in a separate window, so you can reference back in forth between the windows. And do it STEP BY STEP. Once you are rooted and using the stock rom, back that up, so you can revert back to if you crash, once you have those 2 done, get the newest copy of Clockwork, install it. (by the way, the flash counter will tick you using Odin) so make sure you wipe the tick counter before installing any custom roms. Now get CM10 from the thread, install, do not flash the kernel until you have booted the first time, then reboot to recovery and flash kernel of choice. then your set. Now these are MY DIRECTIONS ONLY! and worked for me. So anyone want to add, feel free, or if I missed something, but do NOT slam me for trying to help, again this worked for me, may not for others, but it has been flawless for me. Hope this helps good luck.
Start here>>>http://forum.xda-developers.com/showthread.php?t=1746682
Click to expand...
Click to collapse
Thanks for the input! I just wiped everything properly, other than odining back to stock again because that wasn't really necessary I thought since I did everything right, maybe? Well, I don't know lol. I don't have time to go back to stock atm, so I wiped all things including external/internal sd, used superwipe and just flashed a touchwiz rom, by xquizit: http://forum.xda-developers.com/showthread.php?t=1843409 UVALH2 and flashed the kernel for touchwiz by ktoonz and it is running smooth and solid. So, now, I'm going to go back and flash CM from scratch superwiping and all because I have now confirmed ktoonz's kernels work, and for some odd reason it wasn't working with my CM setup, so I'm going try it again from start and see if it works on CM, and go from there. I'll report back either ways in case anyone is having this problem. If I still have the same issue back on CM, I'll live with it or come back to touchwiz. I kinda like it Weird. Haha, but either ways, I'll keep yall updated! I'm wondering if I need to/should flash the UVALH2 radio/baseband since I"m on a UVALH2 ROM though.
Use this kernel it works perfectly on CM10
http://forum.xda-developers.com/showthread.php?t=1845836
EDIT: nvm use this one http://forum.xda-developers.com/showpost.php?p=31025930&postcount=1152
isikh said:
Thanks for the input! I just wiped everything properly, other than odining back to stock again because that wasn't really necessary I thought since I did everything right, maybe? Well, I don't know lol. I don't have time to go back to stock atm, so I wiped all things including external/internal sd, used superwipe and just flashed a touchwiz rom, by xquizit: http://forum.xda-developers.com/showthread.php?t=1843409 UVALH2 and flashed the kernel for touchwiz by ktoonz and it is running smooth and solid. So, now, I'm going to go back and flash CM from scratch superwiping and all because I have now confirmed ktoonz's kernels work, and for some odd reason it wasn't working with my CM setup, so I'm going try it again from start and see if it works on CM, and go from there. I'll report back either ways in case anyone is having this problem. If I still have the same issue back on CM, I'll live with it or come back to touchwiz. I kinda like it Weird. Haha, but either ways, I'll keep yall updated! I'm wondering if I need to/should flash the UVALH2 radio/baseband since I"m on a UVALH2 ROM though.
Click to expand...
Click to collapse
Now I am a tad confused, you have UVALH2 on the phone already, and you want to flash UVALH2? or did you typo? I am no dev, but from what I have been seeing, the radio should not matter at the moment, if I am wrong, someone please set me straight, also, I will be on the web all night and tomorrow, so I will help where ever I can, I will check here for your progress. Good luck my friend.
BTW, I do not like stock roms, so to me CM10 is for sure better. Faster also.
There is no wrong way to root. I bought my phone, didn't even set it up. Downloaded the toolkit, rooted and flashed a custom recovery, then flashed CM10. You didn't miss any steps, and you didn't do anything in the wrong order.
Your radio and ROM do NOT have to match.
joshnichols189 said:
There is no wrong way to root. I bought my phone, didn't even set it up. Downloaded the toolkit, rooted and flashed a custom recovery, then flashed CM10. You didn't miss any steps, and you didn't do anything in the wrong order.
Your radio and ROM do NOT have to match.
Click to expand...
Click to collapse
Yeah, I know all this, but I wanted to ask in case I may have missed something. Even when you're pretty Android savvy when it comes to rooting and whatnot, you do miss things on occasion. In this instant I didn't, but I was hoping I did because a bunch of custom kernels won't work on my phone with CM10! Trinity worked well, so I'm waiting for those. It must be some specific chip related issue because I'm not the only one. Anyways, thanks everyone!
hello all, have a small question, right after i rooted, using odin. ( im on a boost Galaxy SII) i flashed this kernel "41g-VolDbg4-1109" and then the "vanilla rootbox rom" followed its directions. well it was actin a little buggy, so i decided to try a few other roms. flashed the amazing unicorn rom, went just fine., same bugs so i tryed "jelly bam" i think i was flashin the EL26 kernel betweeen all of em. expet for the rootbox rom. well wen i tryed EL26 and then jellybam, it gave me about a paragraph of errors and said "install aborted at the end", tryed to flash the rootbox rom again, same thing. so I flashed the "41g-VolDbg4-1109" zip kernel, rebooted recovery, and flashed rootbox just fine. What was a i doing wrong? it seems like most roms say to use EL26? it was the stock with CW5 in it. Should i just use the 41g kernel i stated above from now on? unless im downgrading or goin back to stock? any help greatly appreciated.
BAleR said:
hello all, have a small question, right after i rooted, using odin. ( im on a boost Galaxy SII) i flashed this kernel "41g-VolDbg4-1109" and then the "vanilla rootbox rom" followed its directions. well it was actin a little buggy, so i decided to try a few other roms. flashed the amazing unicorn rom, went just fine., same bugs so i tryed "jelly bam" i think i was flashin the EL26 kernel betweeen all of em. expet for the rootbox rom. well wen i tryed EL26 and then jellybam, it gave me about a paragraph of errors and said "install aborted at the end", tryed to flash the rootbox rom again, same thing. so I flashed the "41g-VolDbg4-1109" zip kernel, rebooted recovery, and flashed rootbox just fine. What was a i doing wrong? it seems like most roms say to use EL26? it was the stock with CW5 in it. Should i just use the 41g kernel i stated above from now on? unless im downgrading or goin back to stock? any help greatly appreciated.
Click to expand...
Click to collapse
I have flashed vanilla rootbox using EL26 repacked w/ CWM with no issues. Maybe the kernel download is bad. Also don't use wipe all scripts especially the one that wipe the system partition.
BluesRulez said:
I have flashed vanilla rootbox using EL26 repacked w/ CWM with no issues. Maybe the kernel download is bad. Also don't use wipe all scripts especially the one that wipe the system partition.
Click to expand...
Click to collapse
ok, it was jellybelly that gave me the error. everything ells flashes fine. Should i only use the repacked kernels? i was usin just the stock with cwm. i think. and i have always manually wiped system, should i leave it alone from now on? should i just do a factory reset when switching roms?
Use the Stock EL26 w/CWM http://www.rwilco12.com/downloads.p...ernels/Recovery Kernels/GB/Chris41g/Stock CWM
And yes just a factory reset. Blues is right about not using the wipe scripts unless specifically called for by the developer.
leaderbuilder said:
Use the Stock EL26 w/CWM http://www.rwilco12.com/downloads.p...ernels/Recovery Kernels/GB/Chris41g/Stock CWM
And yes just a factory reset. Blues is right about not using the wipe scripts unless specifically called for by the developer.
Click to expand...
Click to collapse
ok, got it. thanks for the info, clears some things up. I always follow directions exactly, sometimes their just not very spacific. this all will help me alot, i have been reading for the past 2 days straight. thanks for helpin me. one last thing, i notice, if i flash EL26, then after flashing rootbox, it replaces the recovery with CWM6, is it ok to just stay in that if flashing another cm10.1 based rom or another rom that has the exact same directions as the last? or do i have to flash EL26 every time i flash a new rom that requires it?
BAleR said:
ok, got it. thanks for the info, clears some things up. I always follow directions exactly, sometimes their just not very spacific. this all will help me alot, i have been reading for the past 2 days straight. thanks for helpin me. one last thing, i notice, if i flash EL26, then after flashing rootbox, it replaces the recovery with CWM6, is it ok to just stay in that if flashing another cm10.1 based rom or another rom that has the exact same directions as the last? or do i have to flash EL26 every time i flash a new rom that requires it?
Click to expand...
Click to collapse
To be fully safe, flash EL26 every time.
BluesRulez said:
To be fully safe, flash EL26 every time.
Click to expand...
Click to collapse
^ that ^
leaderbuilder said:
^ that ^
Click to expand...
Click to collapse
i read somewhere that 4.2 roms have different partition settings and you have to use the one click kernel, not the zip or tar, for it to partition correctly, is this true?
BAleR said:
i read somewhere that 4.2 roms have different partition settings and you have to use the one click kernel, not the zip or tar, for it to partition correctly, is this true?
Click to expand...
Click to collapse
No. Flashing a kernel doesn't repartition anything. It flashes kernel to kernel partition and that's about it.
BluesRulez said:
No. Flashing a kernel doesn't repartition anything. It flashes kernel to kernel partition and that's about it.
Click to expand...
Click to collapse
hmmmm, alright, I wonder why this person claimed this, maybe it was rom spacific, dunno, ill try to find where i read that, and maybe see if i miss read something. thanks for the help. again. thank you.
Edit: i just noticed in the OP i put "jelly bam"... lol i ment jelly belly...
I've flashed 3-4 ROMs on my Dinc2. (Magnolia, IC Tazz, Skyraider, ViperINC). I've done the wipe cache/davlik/format before each flash. After testing each ROM, I decided on Magnolia, and did a full superduperwipe via Chillybean's AntiVenom. With each ROM flash I've noticed things being different and outright missing. For example, YouTube may or may not be there after flash.
Is this normal? I've tried formatting with ext3 and ext4, noticing no speed or function different... but could this have something to do with it?
I'm still sorta new at this flashing thing. If there's something I'm missing or doing wrong, I'm open to ALL suggestions.
My phone is a Verizon Dinc2, radio is 320, and my recovery is 4EXT.
Rumblur said:
I've flashed 3-4 ROMs on my Dinc2. (Magnolia, IC Tazz, Skyraider, ViperINC). I've done the wipe cache/davlik/format before each flash. After testing each ROM, I decided on Magnolia, and did a full superduperwipe via Chillybean's AntiVenom. With each ROM flash I've noticed things being different and outright missing. For example, YouTube may or may not be there after flash.
Is this normal? I've tried formatting with ext3 and ext4, noticing no speed or function different... but could this have something to do with it?
I'm still sorta new at this flashing thing. If there's something I'm missing or doing wrong, I'm open to ALL suggestions.
My phone is a Verizon Dinc2, radio is 320, and my recovery is 4EXT.
Click to expand...
Click to collapse
Some Deva just won't put it in their Roms. Most the apps just need to be redowbliaded from the market.
Sent from a phone HTC forgot. Right now its running Chilly powered PAC n a lil NOS jus for fun.
Thanks but that's not what I'm saying. I'm saying I can load the same ROM from the same file and there be different apps or features each time I flash it.
Rumblur said:
Thanks but that's not what I'm saying. I'm saying I can load the same ROM from the same file and there be different apps or features each time I flash it.
Click to expand...
Click to collapse
Then you probably aren't doing a full wipe, assuming the rom isn't an aroma installed rom and you choose different features.
yes, they are Aroma installed, using EXT4 as my recovery. I'm talking about (specifically) Magnolia and ViperINC. I've noticed different apps being loaded with each flash. I use Chilly's AntiVenom wiper, then let the ROM do another wipe of it's own choosing. It's just weird, I thought I'd ask if anyone else ever had the same experience.
...
*facepalm
Rumblur said:
I've flashed 3-4 ROMs on my Dinc2. (Magnolia, IC Tazz, Skyraider, ViperINC). I've done the wipe cache/davlik/format before each flash. After testing each ROM, I decided on Magnolia, and did a full superduperwipe via Chillybean's AntiVenom. With each ROM flash I've noticed things being different and outright missing. For example, YouTube may or may not be there after flash.
Is this normal? I've tried formatting with ext3 and ext4, noticing no speed or function different... but could this have something to do with it?
I'm still sorta new at this flashing thing. If there's something I'm missing or doing wrong, I'm open to ALL suggestions.
My phone is a Verizon Dinc2, radio is 320, and my recovery is 4EXT.
Click to expand...
Click to collapse
Hi Friend,
Best way to overcome this is to install Titanium Backup from play store and take a full backup of your apps+data and you can restore the same after flashing new rom.
Regarding youtube you can flash GAPPS from this link goo.im/gapps (install according to your android version)
denny007 said:
Hi Friend,
Best way to overcome this is to install Titanium Backup from play store and take a full backup of your apps+data and you can restore the same after flashing new rom.
Regarding youtube you can flash GAPPS from this link goo.im/gapps (install according to your android version)
Click to expand...
Click to collapse
Um, if you're flashing sense roms, don't flash gapps... Those are specifically for aosp, cm base and aokp roms.
Sent from my Nexus 7 using xda premium
I don't know if someone already posted this, but searched and couldn't find the answer. I get stuck at boot screen all on AOSP 4.2.2 roms that I tried, but with any TW roms are fine (no problem at all). Can anyone help? I want to run AOSP rom. Thanks.
I think you may be using a touch wiz kernel
You can find some aosp kernels in the original development thread
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4 Beta
jinxzn said:
I don't know if someone already posted this, but searched and couldn't find the answer. I get stuck at boot screen all on AOSP 4.2.2 roms that I tried, but with any TW roms are fine (no problem at all). Can anyone help? I want to run AOSP rom. Thanks.
Click to expand...
Click to collapse
which rom did you flash, and what did you flash?
the rom only?
the rom and GAAPS?
The rom and kernel?
you need to provide more details if you want to be helped..
Zachinater said:
I think you may be using a touch wiz kernel
You can find some aosp kernels in the original development thread
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I did flashed SOAPKernel along with aosp roms.
wase4711 said:
which rom did you flash, and what did you flash?
the rom only?
the rom and GAAPS?
The rom and kernel?
you need to provide more details if you want to be helped..
Click to expand...
Click to collapse
I flashed BeanStalk, SlimBean, CyanogenMod 10.1 official nightlies, FSC rom, and IllusionRom.
I have CWM Philz_Touch 5.07.1. Every time install a new rom, I wiped Caches + Data / Factory Reset 2x.
I flashed rom only, then flashed rom and GAPPS, those 2 didn't work, I even tried rom w/ SOAPKernel and still didn't work.
ok, you should try switching to TWRP, since most of the time people have zero issues flashing AOSP roms with TWRP.
Also, after all your wipes, flash the rom and GAAPS in the same session, and reboot..
I've done this exact procedure for years, and it works for me 99.98% of the time..
wase4711 said:
ok, you should try switching to TWRP, since most of the time people have zero issues flashing AOSP roms with TWRP.
Also, after all your wipes, flash the rom and GAAPS in the same session, and reboot..
I've done this exact procedure for years, and it works for me 99.98% of the time..
Click to expand...
Click to collapse
Switched to TWRP, and did all the wipes, install rom and GAAPS. Same thing.
Planning to flash stock rom, and redo all the root/recovery procedures all over again. Do you think I should do that?
it couldnt hurt...
some phones are just tempremental; do you have an SD card in your phone?
are you installing from the sd card or internal memory?
try installing from one or the other to see if that helps; sometimes it does...
wase4711 said:
it couldnt hurt...
some phones are just tempremental; do you have an SD card in your phone?
are you installing from the sd card or internal memory?
try installing from one or the other to see if that helps; sometimes it does...
Click to expand...
Click to collapse
I did try both, none work for me.
Thank you so much for your help thou. I'll now just install stock rom and re-root it, see how it goes.
jinxzn said:
I did try both, none work for me.
Thank you so much for your help thou. I'll now just install stock rom and re-root it, see how it goes.
Click to expand...
Click to collapse
good luck, and post back if you get it working properly
flashed stock rom and rooted and installed boot recovery, after all that, it's still not let me install any AOSP roms. Really don't why I can only flash TW roms but not AOSP roms.
So, first off, just wanna say that I have a RIDICULOUS amount of experience with flashing roms. Literally over 100 different devices and 1000s of different flashes of my own devices on top of it. Quite familiar with this S2 as well and have customized them to all sorts of extents, but this one has me baffled. This phone refuses to run 4.2.2/4.3/4.4.x roms. Using the most up to date radio and the suggested TWRP (2.6.1.0) as well as CWM 6.0.44 and the newer TWRP: 2.6.3.0. Every time the phone will get to the set up screen, refreeze and boot. No issues running stock or stock based 4.1.2 roms. I've tried changing recoveries, wiping everything (/system, /data, /caches) repeatedly, Odin back to stock and redoing everything, switching kernels, wiping caches before rebooting and leaving it be, changing batteries, etc but nothing has worked. So far I've tried BlackLiquid 2.92 (4.2.2 stable), Awesome Audio rom (4.3), official CM11 (whatever the last build up was last night), and BeanStalk 4.4.2 (12/16) and all behave exactly the same - freeze on start up and reboot. This doesn't seem to be much of a widespread issue obviously, so just baffled and getting a bit frustrated as this should have been a 20 minute process that has turned into a few hours already. Since USB Debugging isn't on by default on newer roms, how would I even do a logcat to see if there is anything meaningful there? Any ideas?
Update: I have another S2. Performed same steps, same TWRP, same radio and rom, on same external SD card and that one booted right up like normal confirming that it is the phone itself, but what causes that?? Corrupted partitions?
I have the same problem, just format your internal and external sd card with just ROM file on your storage then try to install, than please inform me
Sent from my SGH-T989 using XDA Premium 4 mobile app
iamdofus said:
I have the same problem, just format your internal and external sd card with just ROM file on your storage then try to install, than please inform me
Sent from my SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nope. No luck there (only tried Beanstalk so far, but exact same issue). Thanks for the suggestion though! Only using internal storage, no SD card, though thinking I might try that next...
Edit: Just to be thorough, I formatted internal storage via TWRP and my computer then readded the files and just tried to boot rom only and freezes before I can do anything.
Do you by chance have a refurbished s2?
The screen has been replaced by a friend of mine and he managed to mess up the soft keys with it, but everything else functions. That's actually why he sent it to me, so I could hook him up with Pie and all that kind of thing so the soft keys aren't an issue. What's your thoughts on the refurb side of it?
es0tericcha0s said:
The screen has been replaced by a friend of mine and he managed to mess up the soft keys with it, but everything else functions. That's actually why he sent it to me, so I could hook him up with Pie and all that kind of thing so the soft keys aren't an issue. What's your thoughts on the refurb side of it?
Click to expand...
Click to collapse
OK thanks for reply, I have one more solution give me. Some time I will give try that it worked for me.
Sent from my SGH-T989 using XDA Premium 4 mobile app
es0tericcha0s said:
Nope. No luck there (only tried Beanstalk so far, but exact same issue). Thanks for the suggestion though! Only using internal storage, no SD card, though thinking I might try that next...
Edit: Just to be thorough, I formatted internal storage via TWRP and my computer then readded the files and just tried to boot rom only and freezes before I can do anything.
Click to expand...
Click to collapse
ok lets stat it with this
1) download both the scripts of infamous wipe cache and infamous super wipe.
2) format your both SD card with PC (FAT32)
2) put both these wipe files and and your rom file ( i prefer try slimbean rom first)
3) Now in twrp 2.6.0.0- follow the steps
i) format your phone with twrp options
ii) again format your phone with infamous super file. (by going in to INSTALL ZIP file option in TWRP)
iii) than format with infamouse cache file (by going in to INSTALL ZIP file option in TWRP)
iv) install your rom and compatiable GAPPS zip file.
v) after installing or somewhere between procedure if twrp says something about supersu birnaries are not correct than click on DO . NOT FIX
vi) again format infamouse cache wipe.
vii) now FINALLY reboot the rom.
it should work, and it worked for me. if u sucessfully run the rom than you can eailsy run all the AOSP roms in this forum. Again If you try this please do tell me what happend.
Followed to a "T" and still in the same boat - freezes after bootup. I used those same steps before with another darkside wipe script (maybe older?) but yea, have already been down that road. I did downgrade to 2.6.0.0 and used Slim 4.3 because 4.4 is supposed to use the newer TWRP, just to be certain, but GRRR. I guess we're just gonna have to settle for a 4.1.2 rom and call it a day. :/
So here are the log output from the wipes:
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.SUPER.WIPE_recovery.log
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.CACHE.WIPE_recovery.log
I see some stuff at the bottom of those that might indicate something weird, but I am not adept at interpreting these, so just wondering if someone could point me to the right direction about the repair checks and what not listed on these. Thanks!
Edit 2: I did get a AOSP based 4.1.2 rom to boot with no problems! wtf... LoL
Last Edit:
Problem solved! I used basically the same steps I had been doing but once the AOSP 4.1.2 rom booted then now everything works like it should again. Have loaded a 4.3 and 4.4 rom successfully. Thanks for the help!
es0tericcha0s said:
So, first off, just wanna say that I have a RIDICULOUS amount of experience with flashing roms. Literally over 100 different devices and 1000s of different flashes of my own devices on top of it. Quite familiar with this S2 as well and have customized them to all sorts of extents, but this one has me baffled. This phone refuses to run 4.2.2/4.3/4.4.x roms. Using the most up to date radio and the suggested TWRP (2.6.1.0) as well as CWM 6.0.44 and the newer TWRP: 2.6.3.0. Every time the phone will get to the set up screen, refreeze and boot. No issues running stock or stock based 4.1.2 roms. I've tried changing recoveries, wiping everything (/system, /data, /caches) repeatedly, Odin back to stock and redoing everything, switching kernels, wiping caches before rebooting and leaving it be, changing batteries, etc but nothing has worked. So far I've tried BlackLiquid 2.92 (4.2.2 stable), Awesome Audio rom (4.3), official CM11 (whatever the last build up was last night), and BeanStalk 4.4.2 (12/16) and all behave exactly the same - freeze on start up and reboot. This doesn't seem to be much of a widespread issue obviously, so just baffled and getting a bit frustrated as this should have been a 20 minute process that has turned into a few hours already. Since USB Debugging isn't on by default on newer roms, how would I even do a logcat to see if there is anything meaningful there? Any ideas?
Update: I have another S2. Performed same steps, same TWRP, same radio and rom, on same external SD card and that one booted right up like normal confirming that it is the phone itself, but what causes that?? Corrupted partitions?
Click to expand...
Click to collapse
Interesting, so you're saying it's phone specific?
That begs to ask other questions now:
1. Where did this phone come from? is it a Tmobile version (SGH-T989) or AT&T (i-1900)?
2. You mentioned you got it from a friend; did it come rooted? unlocked? Or did you have to do that process yourself?
UltimaniumX said:
Interesting, so you're saying it's phone specific?
That begs to ask other questions now:
1. Where did this phone come from? is it a Tmobile version (SGH-T989) or AT&T (i-1900)?
2. You mentioned you got it from a friend; did it come rooted? unlocked? Or did you have to do that process yourself?
Click to expand...
Click to collapse
Yep, very much phone specific. Used same recovery, same rom zip and gapps off the same external SD card, to be certain. That one updated just like every other S2 I've done. And it's the Tmo version. The At&t models are i777 S2 or i727 S2 Skyrocket. The i9100 is international and has a physical home button. But the phone was not modified at all. No root, custom recovery, etc. I was only able to resolve it by first starting with an AOSP 4.1.2 rom and working my way up to 4.4. One of the weirder issues I've come across.
es0tericcha0s said:
Followed to a "T" and still in the same boat - freezes after bootup. I used those same steps before with another darkside wipe script (maybe older?) but yea, have already been down that road. I did downgrade to 2.6.0.0 and used Slim 4.3 because 4.4 is supposed to use the newer TWRP, just to be certain, but GRRR. I guess we're just gonna have to settle for a 4.1.2 rom and call it a day. :/
So here are the log output from the wipes:
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.SUPER.WIPE_recovery.log
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.CACHE.WIPE_recovery.log
I see some stuff at the bottom of those that might indicate something weird, but I am not adept at interpreting these, so just wondering if someone could point me to the right direction about the repair checks and what not listed on these. Thanks!
Edit 2: I did get a AOSP based 4.1.2 rom to boot with no problems! wtf... LoL
Last Edit:
Problem solved! I used basically the same steps I had been doing but once the AOSP 4.1.2 rom booted then now everything works like it should again. Have loaded a 4.3 and 4.4 rom successfully. Thanks for the help!
Click to expand...
Click to collapse
What did you exactly do? I flashed a 4.1.2 and then flashed a 4.3 based ROM and it didn't work. What recovery version did you use to flash the 4.3 ROM?
tpag02 said:
What did you exactly do? I flashed a 4.1.2 and then flashed a 4.3 based ROM and it didn't work. What recovery version did you use to flash the 4.3 ROM?
Click to expand...
Click to collapse
Sorry, I don't pay attention to the notifications on XDA very often. I don't usually browse the S2 forums unless needed because I have an N5, but anyway... The 4.1.2 rom you used, was it TW or AOSP type? I used 2.6.0 to wipe everything, then used cache and superwipe zips then 4.1.2 AOSP type rom then cache wipe zip again then after that booted, I was able to go back to 2.6.1 and flash a 4.3 via wiping, wipe zips, installing rom then cache wipe again. After that, repeated with a KK rom and now it loads roms just like it should. If you want more precise help, feel free to hit me up on Hangouts with my username: es0tericcha0s. Good luck! I know how frustrating it can be when it gets a little out of whack like this...
I'm in the same boat
Same here. I just bought a galaxy s2 from my friend (tmobile version) and I too get stuck in a bootloop no matter what rom I use. It boots up freezes then reboots 7 keeps doing that endelessly. I've even wiped using twrp & darkside then reflashed the stock rom in odin, but no luck. strangely it only happens on the cellular network, otherwise it works fine on wifi. But when I turn off the wifi and go to the cellular network I can't even turn on the wifi anymore and still stuck in this boot loop It's wierd and frustrating.
DennyTek said:
Same here. I just bought a galaxy s2 from my friend (tmobile version) and I too get stuck in a bootloop no matter what rom I use. It boots up freezes then reboots 7 keeps doing that endelessly. I've even wiped using twrp & darkside then reflashed the stock rom in odin, but no luck. strangely it only happens on the cellular network, otherwise it works fine on wifi. But when I turn off the wifi and go to the cellular network I can't even turn on the wifi anymore and still stuck in this boot loop It's wierd and frustrating.
Click to expand...
Click to collapse
Hmm. That's interesting... This is happening on the stock rom - where you turn on cellular data and it reboots? Definitely a different issue than the one I was having. Which stock rom were you flashing via Odin? Have you tried other versions of the stock rom and had the same problem?
TMO 4.1.2
es0tericcha0s said:
Hmm. That's interesting... This is happening on the stock rom - where you turn on cellular data and it reboots? Definitely a different issue than the one I was having. Which stock rom were you flashing via Odin? Have you tried other versions of the stock rom and had the same problem?
Click to expand...
Click to collapse
This was happening on any rom I used (Cm 10.2 stable, Cm 11 nightly, AOKP & Super Nexus 3.0 which is Android 4.3) I can't really speak for the stock rom (tmo 4.1.2) since I've never used it for more that 5 minutes, sigh but I'll try it and see if it gives me the same problem :/
Are you guys flashing gapps if the ROM you're installing doesn't have it?
Sent from my SGH-T989 using Tapatalk
yep
wikitiki said:
Are you guys flashing gapps if the ROM you're installing doesn't have it?
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
ya, well at least I am anyways
wikitiki said:
Are you guys flashing gapps if the ROM you're installing doesn't have it?
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
I had tried with and without and did not make any difference.
DennyTek said:
This was happening on any rom I used (Cm 10.2 stable, Cm 11 nightly, AOKP & Super Nexus 3.0 which is Android 4.3) I can't really speak for the stock rom (tmo 4.1.2) since I've never used it for more that 5 minutes, sigh but I'll try it and see if it gives me the same problem :/
Click to expand...
Click to collapse
I just started working on a VZW S3 on T-Mobile service that has this issue. Happens on stock VZW 4.1.2, stock T-Mobile 4.1.2 rom, custom 4.1.2 T-Mobile rom, and stable CM 10.2. Weirdest thing... full wipes including /system inbetween each flash. Changed the modem too. Nothing helps. Pretty sure it's a bad board at this stage.
Cool beans, 0! Having this exact problem, will try your method for my s2, btw which aosp 4.1.2 did u use? Can I get a link? Thanks been having the problem for a few months now and just gave up haha, been super thirsty for that beanstalk kk build
One last thing can u also provide a link to the 4.3 that u used? I really want it to work and want to follow what u did to the , megabyte