Develop Bugs

skyrocket roms and our phone

so i tried flashing the skyrocket UCLA3 2.3.6 stock rom, and it came with their modem too. after installing the rom, i flashed the latest faux kernel.
using odin, i tried flashing the latest modem for our phones twice. for some reason the modem won't change and remains as the at&t one, leaving me with just the edge network.
i thought skyrocket roms worked fine on our phones? is this a bug with the new 2.3.6 base or something?

darkness122 said:
so i tried flashing the skyrocket UCLA3 2.3.6 stock rom, and it came with their modem too. after installing the rom, i flashed the latest faux kernel.
using odin, i tried flashing the latest modem for our phones twice. for some reason the modem won't change and remains as the at&t one, leaving me with just the edge network.
i thought skyrocket roms worked fine on our phones? is this a bug with the new 2.3.6 base or something?
Click to expand...
Click to collapse
try flashing our modem.

b0ricuaguerrero said:
try flashing our modem.
Click to expand...
Click to collapse
lol i mentioned that i did that 2 times in the 2nd line of my post bro :x

Not sure as I've never tried flashing that rom before, but I do know firsthand that skyrocket roms work on our phones, AOSP roms work as well (regardless of what you have read).
My suggestion would be to wipe everything clean from recovery and try again. I wipe everything except sd card under mounts and storage every time I flash, and then run the darkside superwipe tool, then follow the roms instructions. It may be a bit of overkill but it works great for me. I've also found that booting and setting up with the SR kernel installed first saves a lot of hassle.
Good Luck

Jester6 said:
Not sure as I've never tried flashing that rom before, but I do know firsthand that skyrocket roms work on our phones, AOSP roms work as well (regardless of what you have read).
My suggestion would be to wipe everything clean from recovery and try again. I wipe everything except sd card under mounts and storage every time I flash, and then run the darkside superwipe tool, then follow the roms instructions. It may be a bit of overkill but it works great for me. I've also found that booting and setting up with the SR kernel installed first saves a lot of hassle.
Good Luck
Click to expand...
Click to collapse
thats how i flash any sort of rom bro, do all the wipes/formats (minus sd card) twice, then install the darkside superwipe thing, then the rom itself. no luck.

darkness122 said:
thats how i flash any sort of rom bro, do all the wipes/formats (minus sd card) twice, then install the darkside superwipe thing, then the rom itself. no luck.
Click to expand...
Click to collapse
one bump, if there's no solution then i guess i'll stick with my hercules roms lol

[Q]droid gtr rom v1.0 not booting

Ok so I flashed it the first time and it was successful but noticed market was not opening so I flash the latest gapps for cyonogen mod and then everthing fc so wiped and flash and now it won't even boot it gets stuck on splash screen. Is it cause of SD card is on ext 4 or is it smellkus recovery or what?? Any help is much appreciative

Try wiping cache and dalvik then fix permissions in recovery.

Did you flash the correct ROM for your specific phone model and carrier? I had the the problem of flashing a T-Mobile ROM for my GS2 a while back, due to my excitement about using an ICS rom.

Ryan_28 said:
Did you flash the correct ROM for your specific phone model and carrier? I had the the problem of flashing a T-Mobile ROM for my GS2 a while back, due to my excitement about using an ICS rom.
Click to expand...
Click to collapse
Exactly...I've never heard of this rom for the evo. So I question it.

teh roxxorz said:
Exactly...I've never heard of this rom for the evo. So I question it.
Click to expand...
Click to collapse
no its for the evo its under evo general development it was just released

Can you boot into recovery? If so, I think your best bet is to restore a backup, delete the faulty ROM, and try reinstalling it if you want that specific ROM badly enough. That has worked for me a few times.

Ryan_28 said:
Can you boot into recovery? If so, I think your best bet is to restore a backup, delete the faulty ROM, and try reinstalling it if you want that specific ROM badly enough. That has worked for me a few times.[/Q
Yes I could go into recovery and I actually fixed the issue. I'm guessing it was the recovery itself that I was using because now I flashed Among RA recovery and now is booted and working fine. A great Tom overall. Thanks guys for your help
Click to expand...
Click to collapse

Not to bother anyone, but I was trying to run the droid GTRv2.0 ROM on my EVO 4G and it wont get past the first screen.

How can I get CM10 while on UVALH3?

Still a major noob here. I want to get cyanogenmod 10 onto my s3 but I've had issues ever since putting on UVALH3. If I want to get CM10 can someone walk me through all the steps to get there, or is it just impossible?

ambitionlessness said:
Still a major noob here. I want to get cyanogenmod 10 onto my s3 but I've had issues ever since putting on UVALH3. If I want to get CM10 can someone walk me through all the steps to get there, or is it just impossible?
Click to expand...
Click to collapse
Do you have a recovery installed like CWM or TWRP? Lets start with that.

sipple31 said:
Do you have a recovery installed like CWM or TWRP? Lets start with that.
Click to expand...
Click to collapse
Could it be I was supposed to do this before flashing CM10? Because 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

isikh said:
Could it be I was supposed to do this before flashing CM10? Because 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
Click to expand...
Click to collapse
pretty sure having a custom recovery isn't your issue if you are to the point of wiping caches and flashing kernels. The OP is asking how to wipe a stock ROM off and get CM on his/her phone i'm pretty sure.

sipple31 said:
pretty sure having a custom recovery isn't your issue if you are to the point of wiping caches and flashing kernels. The OP is asking how to wipe a stock ROM off and get CM on his/her phone i'm pretty sure.
Click to expand...
Click to collapse
I was asking about myself because I thought I had a similar problem

sipple31 said:
Do you have a recovery installed like CWM or TWRP? Lets start with that.
Click to expand...
Click to collapse
No i do not. I tried rooting my phone and it didn't take, and you need to root before CWM right? I had CWM when I was on Uvalh2 but when I went through the process of Uvalh3 I guess I lost it. Should I go ahead and do it? I have the zip file in my phone, still.
I should also mention that when I go into recovery the android dude is fallen over, dead. I'm guessing that's a bad sign.

That just means you're on stock recovery. Odin a rooted rom which you can find in the dev forums (root without tripping flash), then install twrp or cwm, then flash cm10, then flash desired radio.
Sent from my SGH-T999 using xda app-developers app

AOSP roms will NOT run! Driving me crazy...

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

Some ROMs not booting

Hey guys, I'm on vs985 and was wondering if anyone else is having the same problems I'm having. Some ROMs won't boot properly, ex. After flashing a ROM the LG logo screen appear and then goes away then the screen turns completely black. This also happens with some kernels only certain ROMs or kernel will allow my phone to boot normally. Does anyone know a solution to this? Would really like to use stock kernels on some of these ROMs. Thanks in advance

Which version of TWRP are you using, and what procedure are you using to flash ROMs and kernels? Are you flashing a different kernel immediately after flashing a ROM? Which specific ROM and kernel combinations are you flashing?

redduc900 said:
Which version of TWRP are you using, and what procedure are you using to flash ROMs and kernels? Are you flashing a different kernel immediately after flashing a ROM? Which specific ROM and kernel combinations are you flashing?
Click to expand...
Click to collapse
I'm using TWRP 2.8.3.0. And I always clean flash. Usually never dirty flash even when I'm just updating a ROM. If the stock kernel doesn't boot with the ROM I reflash the ROM along with kernel as a clean flash. The mains ones I have problems with are Exodus, BrokenOS, and XenonHD just recently. Usually the only kernel that works with any of those ROMs and allows it to boot is JediKernel 3.0. Others such as nebula, any kernel and fechda don't seem to work.

I think the first thing I would try is updating TWRP to version 2.8.7.0

redduc900 said:
I think the first thing I would try is updating TWRP to version 2.8.7.0
Click to expand...
Click to collapse
Updated to TWRP version 2.8.7.0 and still not working. Any other suggestions?
Sent from my SCH-I535 using XDA Free mobile app

Are you verifying the MD5 of the ROMs and kernels beforehand? And are you installing them from internal storage or external SD?

I don't know if this helps, but I had a lot of trouble with something that almost nobody post in ROM installation instructions: you should always format data, not just wipe it. My device is D855 International, hope it helps.

redduc900 said:
Are you verifying the MD5 of the ROMs and kernels beforehand? And are you installing them from internal storage or external SD?
Click to expand...
Click to collapse
Yeah they always match, and I install from external SD.

Try installing from internal instead.

redduc900 said:
Try installing from internal instead.
Click to expand...
Click to collapse
antony.ps said:
I don't know if this helps, but I had a lot of trouble with something that almost nobody post in ROM installation instructions: you should always format data, not just wipe it. My device is D855 International, hope it helps.
Click to expand...
Click to collapse
Tried both of these methods, still doesn't work for exodus or broken which are the only ones I really tried because I know they don't normally boot up