Related
So I installed several versions of Jelly Bean. I tried TeamBAMF Leaked ROM, Jelly Belly Leaked, and Vicious Toro (Source). All of them soft brick my phone after a day or two. It will just boot loop constantly. New ROM and Wipe make no difference. A Restore doesnt work because it gives an error when restoring Data. Always happens after a reboot or powering on the device. For me to fix this, I must use ADB to push the stock google image to the phone. This is tiring as it happened 3 times. I love JB and the features but I can't deal with this soft brick. Anyone else having an issue? I tried turning off SetCPU as well and using the Kernels that come with the ROMs. I would really like to install JB. I am and have been using AOKP M5 with absolutely no issues.
I am ready to get a new phone through Asurion. This is a launch Verizon Nexus.
EDIT: Missed the fact that this is a Verizon Nexus so removing this comment.
asawoszc said:
Have you tried a stock version of Jelly Bean from the files on XDA? Sorry but it just sounds like you've tried custom ROM's. My other suggestion would be to put on 4.0.4 takju from Google's site and see if you get the Jelly Bean OTA update and if it resolves the issues in the short term. If it does then it must be the process you're going thru to put on the ROM's..... might be missing something simple like Dalvik cache wipe, etc. Just speaking in very general terms.
Click to expand...
Click to collapse
no, he shouldnt do any of what you said. he is on a VERIZON nexus. not a GSM. if he flashed takju there could be serious problems.
Apologies... I missed the last line. Will edit out my comment.
lacesout said:
So I installed several versions of Jelly Bean. I tried TeamBAMF Leaked ROM, Jelly Belly Leaked, and Vicious Toro (Source). All of them soft brick my phone after a day or two. It will just boot loop constantly. New ROM and Wipe make no difference. A Restore doesnt work because it gives an error when restoring Data. Always happens after a reboot or powering on the device. For me to fix this, I must use ADB to push the stock google image to the phone. This is tiring as it happened 3 times. I love JB and the features but I can't deal with this soft brick. Anyone else having an issue? I tried turning off SetCPU as well and using the Kernels that come with the ROMs. I would really like to install JB. I am and have been using AOKP M5 with absolutely no issues.
I am ready to get a new phone through Asurion. This is a launch Verizon Nexus.
Click to expand...
Click to collapse
try do and this if you are comfortable doing it.. note you will lose all data including in your /sdcard/
fastboot erase system
fastboot erase userdata
fastboot erase cache
flash the factory mysid images, then install CWM (not the touch one) or TWRP and flash this rom: http://forum.xda-developers.com/showthread.php?t=1744389
Zepius said:
try do and this if you are comfortable doing it.. note you will lose all data including in your /sdcard/
fastboot erase system
fastboot erase userdata
fastboot erase cache
flash the factory mysid images, then install CWM (not the touch one) or TWRP and flash this rom: http://forum.xda-developers.com/showthread.php?t=1744389
Click to expand...
Click to collapse
Thanks Zepius but I already did this. It's the only way for me to recover. My phone is fine now on AOKP M5 but I want to use Jelly Bean. Is there any reason JB would cause boot loops after 24 hours? It's just a pain in the ass because I can't simply recover through CWM. I need a PC. The first time this happened I had to back up my SDCARD from ADB. This took forever!!
BTW, I know how to Root, ROM, etc. I always do everything twice. Wipe Data/Dalvik/Cache and install the ROM twice.
just curious... which version of CWM are you using?
Oh man I have the same issue I just get stuck at the Google screen or the jb splash screen on my cdma nexus I tried everything and wiped every last thing on my phone I just gave up and said ile wait for the official update I guess. Anyway I hope this thread shed some light on the situation we having
Sent from my Galaxy Nexus using xda app-developers app
Use the superwipe from the android HD thread, flash the rom, everytime it boots let it sit at the google logo IT IS NOT FROZEN. It just takes a while sometimes.
What are you doing that's causing a soft-brick after 24 hours? I mean, the phone is just sitting on a table and BOOM - it freezes and it's soft-bricked?? Maybe give us the scenario that happens when it's soft-bricked. We need more concrete details. It could be something you're doing wrong.
Zepius said:
just curious... which version of CWM are you using?
Click to expand...
Click to collapse
I was using the latest (forgot which version) and I also tried CWM touch between the first two bricks. Same issue.
XfrostX said:
Use the superwipe from the android HD thread, flash the rom, everytime it boots let it sit at the google logo IT IS NOT FROZEN. It just takes a while sometimes.
Click to expand...
Click to collapse
Nope, it keeps boot looping. I had it sitting for over 30 min. It starts with Google then JB splash. Then boot loops and continues. Even when I wipe and install AOKP it still boot loops. I need to use Fastboot to wipe and flash stock image.
akira02rex said:
What are you doing that's causing a soft-brick after 24 hours? I mean, the phone is just sitting on a table and BOOM - it freezes and it's soft-bricked?? Maybe give us the scenario that happens when it's soft-bricked. We need more concrete details. It could be something you're doing wrong.
Click to expand...
Click to collapse
It happens as soon as I reboot or power off the phone. For instance, Saturday I went shark fishing so I powered down the phone to save battery. Power it up several hours later and it boot looped for 20 min.
I am using a AOKP restore I recovered through ADB. Once I flashed stock image, rooted, installed CWM, the restore worked perfectly.
lacesout said:
I was using the latest (forgot which version) and I also tried CWM touch between the first two bricks. Same issue.
Nope, it keeps boot looping. I had it sitting for over 30 min. It starts with Google then JB splash. Then boot loops and continues. Even when I wipe and install AOKP it still boot loops. I need to use Fastboot to wipe and flash stock image.
It happens as soon as I reboot or power off the phone. For instance, Saturday I went shark fishing so I powered down the phone to save battery. Power it up several hours later and it boot looped for 20 min.
I am using a AOKP restore I recovered through ADB. Once I flashed stock image, rooted, installed CWM, the restore worked perfectly.
Click to expand...
Click to collapse
Is it getting wet??
akira02rex said:
Is it getting wet??
Click to expand...
Click to collapse
Lol nope. The shark fishing trip was the third boot loop for me.
Same boat here... I can flash any ics and restore any backup... but some how every time I flash jb rom it just stay in nexus logo or in any kernel logo.. the first time the vicious jb rom out I manage to flash and boot well ..then after a few days tried different jb rom then boom! Infinite boot loop.. then since then I can't flash jb rom. Tried all kind of kernel and rom combo and also used all kinds of cwm..
Sent from my Galaxy Nexus using XDA Premium App
landrian18 said:
Same boat here... I can flash any ics and restore any backup... but some how every time I flash jb rom it just stay in nexus logo or in any kernel logo.. the first time the vicious jb rom out I manage to flash and boot well ..then after a few days tried different jb rom then boom! Infinite boot loop.. then since then I can't flash jb rom. Tried all kind of kernel and rom combo and also used all kinds of cwm..
Sent from my Galaxy Nexus using XDA Premium App
Click to expand...
Click to collapse
Interesting that you got it to work once, because I have the same issue you do but have never gotten it to boot past the Google animation. Wonder if there was a Rom that we flashed that caused the issue to begin with. I have tried so many JB roms now that I don't know which one I started with, but I think it was Vicous JB since that was the first one I saw released at the time. Just wish someone out there that has had our symptoms and finally got past them could tell us what they did.
Well at least I'm not the only having this issue. Hopefully someone can shed some light.
@nothingshocking
Its the [email protected]_jelly jb rom that I flash when this things all starts.. the vicious rom works for me since v1 to v3.. I'm trying other rom because of grs issue in vicious at that time. I'm not afraid to flash or be in softbrick because I know I can always use my backup and restore or there's toolkit just in case ,but this thing I'm really puzzled this is so weird.. I can flash any ics rom but not the jb rom.. someone suggest me to use jb bootloader and I did and same results.. I'm really hoping that someone of our bright dev can look in to this and help us..
Sent from my Galaxy Nexus using XDA Premium App
Same exact problem here. I would boot loop anytime I rebooted or powered down my phone. Today, I flashed the new clockwork recovery (v.6.0.0.?). So of course I rebooted my phone to see what it looked like. Well it looked cool but when I went to reboot my phone it was just stuck on the google screen. Wouldn't boot at all. Tried wiping data/cache/dalvik cache/format system/format cache/fix permission. Got desperate cuz nothing worked. Backups wouldn't restore. Got "installation aborted error". Finally did like the op and flashed stock image. Works fine now. Just seems like my phone doesn't like the JB at all. Has done this on every JB I flashed.
Sent from my Galaxy Nexus using xda premium
had this happen on my cdma toroplus any ics rom will install and work fine but no jelly bean rom will boot past the bootanimation
Maybe it has to do with hardware version? For those of you with problems like me, are you on a launch Nexus? That is what I have.
My SKU is SCHI515MSV
I am not sure if they redesigned the hardware at some time.
Verizon Samsung Galaxy Nexus - Toro
Bootloader version: PRIMELA03
Baseband version: I515
Android version 4.1.1
Miui.US 2.9.14.0
Clockwork recovery v5.5.0.4
I was previously running Vicious Jelly bean and installed Miui.US. Since then my phone constantly reboots within a few seconds of booting up. I have tried flashing to a different ROM and flashing back to stock several times using different tools and also from command line. I have also tried going back to stock via ODIN. All have failed and the phone always restores itself to the previous state. I have searched for recovery-from-boot.p in /system and other locations but cannot find it.
My Droid is currently unusable. Any tips or tricks are greatly appreciated.
Does anyone know what would cause the phone to keep restoring its previous state ? As I mentioned I have looked for the recovery-from-boot script and cannot find it. Thanks!
Dr01d4l1f3 said:
Verizon Samsung Galaxy Nexus - Toro
Bootloader version: PRIMELA03
Baseband version: I515
Android version 4.1.1
Miui.US 2.9.14.0
Clockwork recovery v5.5.0.4
I was previously running Vicious Jelly bean and installed Miui.US. Since then my phone constantly reboots within a few seconds of booting up. I have tried flashing to a different ROM and flashing back to stock several times using different tools and also from command line. I have also tried going back to stock via ODIN. All have failed and the phone always restores itself to the previous state. I have searched for recovery-from-boot.p in /system and other locations but cannot find it.
My Droid is currently unusable. Any tips or tricks are greatly appreciated.
Click to expand...
Click to collapse
I have attached the output I get from logcat. Please help!
***Removed logcat file***
1) did you wipe data/cache when you switched roms?
2) dont use odin, its not really supported for this phone. learn fastboot: http://forum.xda-developers.com/showthread.php?t=1626895
3) recovery-from-boot.p has nothing to do with what you are talking about. all that does is restore the stock recovery. ODIN is failing for another reason.
Zepius,
Thanks for the response.
1) did you wipe data/cache when you switched roms?
I have wiped data and cache several times after I switched. Both from within recovery and running command 'fastboot erase cache'
2) dont use odin, its not really supported for this phone. learn fastboot: http://forum.xda-developers.com/show....php?t=1626895
I have followed this manual and others and have become familiar with the process. I complete all the steps and issue the 'fastboot reboot' command. The phone reboots back into the previous state
3) recovery-from-boot.p has nothing to do with what you are talking about. all that does is restore the stock recovery. ODIN is failing for another reason.
I'm grasping for straws here, not sure what else I need/can do
Dr01d4l1f3 said:
Verizon Samsung Galaxy Nexus - Toro
Bootloader version: PRIMELA03
Baseband version: I515
Android version 4.1.1
Miui.US 2.9.14.0
Clockwork recovery v5.5.0.4
I was previously running Vicious Jelly bean and installed Miui.US. Since then my phone constantly reboots within a few seconds of booting up. I have tried flashing to a different ROM and flashing back to stock several times using different tools and also from command line. I have also tried going back to stock via ODIN. All have failed and the phone always restores itself to the previous state. I have searched for recovery-from-boot.p in /system and other locations but cannot find it.
My Droid is currently unusable. Any tips or tricks are greatly appreciated.
Click to expand...
Click to collapse
This is what do every time for ANY rom and never have issues.
I also restore data with TB after successful flash and startup, then I login into Google.
Using clockworkmod touch recovery 6.0.1.5
Under mounts & storage:
Format....system
Format....cache
Format....data
Then install ROM of your choice.
If installing custom kernel waiting until the device has fully booted up to setup screen and then reboot to recovery and install your favorite kernel.
If flashing mods and such you need to reboot after each flash otherwise you could bootloop or get stuck at Google logo....
If using twrp it has a feature that allows flashing multiple zips.....with miui it has caused intermittent problems on some users devices.
Hope this helps.....
Sent from my Galaxy Nexus
cdexsw said:
This is what do every time for ANY rom and never have issues.
I also restore data with TB after successful flash and startup, then I login into Google.
Using clockworkmod touch recovery 6.0.1.5
Under mounts & storage:
Format....system
Format....cache
Format....data
Then install ROM of your choice.
If installing custom kernel waiting until the device has fully booted up to setup screen and then reboot to recovery and install your favorite kernel.
If flashing mods and such you need to reboot after each flash otherwise you could bootloop or get stuck at Google logo....
If using twrp it has a feature that allows flashing multiple zips.....with miui it has caused intermittent problems on some users devices.
Hope this helps.....
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Ill never understand why people dont learn stuff like this before they start flashing roms in the first place. These steps are common knowledge and easily attainable information. Maybe this post will help some poor android noob fight the urge to post an unnecessary topic in the future and stop panicking and restoring their phone to stock when they soft brick it.
Dr01d4l1f3 said:
Zepius,
Thanks for the response.
1) did you wipe data/cache when you switched roms?
I have wiped data and cache several times after I switched. Both from within recovery and running command 'fastboot erase cache'
2) dont use odin, its not really supported for this phone. learn fastboot: http://forum.xda-developers.com/show....php?t=1626895
I have followed this manual and others and have become familiar with the process. I complete all the steps and issue the 'fastboot reboot' command. The phone reboots back into the previous state
3) recovery-from-boot.p has nothing to do with what you are talking about. all that does is restore the stock recovery. ODIN is failing for another reason.
I'm grasping for straws here, not sure what else I need/can do
Click to expand...
Click to collapse
Odin fails because it is not fully compatible with CDMA radios....meaning that it cannot flash the baseband/radio for cdma devices....well at least it doesn't for Verizon gnex.
You need to manually flash your devices images using fast boot. This can take awhile.....if you don't know what you are doing then READ first before doing so. Make sure you have the proper images.
Or look for P3Droid All-n-One-JB-Installer zip, flash it from cwm recovery. It will get you pure stock running a rooted jelly bean ROM. That's the best you can hope for....
Also before flashing follow the steps I listed above.....
Goodluck
Sent from my Galaxy Nexus
eqjunkie829,
Is it lonely up there on your high horse ? This is not the first time or the first phone I have rooted.
eqjunkie829 said:
Ill never understand why people dont learn stuff like this before they start flashing roms in the first place. These steps are common knowledge and easily attainable information. Maybe this post will help some poor android noob fight the urge to post an unnecessary topic in the future and stop panicking and restoring their phone to stock when they soft brick it.
Click to expand...
Click to collapse
cdexsw,
Thanks for the tip, I will try that.
cdexsw said:
Odin fails because it is not fully compatible with CDMA radios....meaning that it cannot flash the baseband/radio for cdma devices....well at least it doesn't for Verizon gnex.
You need to manually flash your devices images using fast boot. This can take awhile.....if you don't know what you are doing then READ first before doing so. Make sure you have the proper images.
Or look for P3Droid All-n-One-JB-Installer zip, flash it from cwm recovery. It will get you pure stock running a rooted jelly bean ROM. That's the best you can hope for....
Also before flashing follow the steps I listed above.....
Goodluck
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Zepius said:
2) dont use odin, its not really supported for thisany phone. learn fastboot: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
Odin is a leaked tool from Sammy, it is not supported on any device.
OP, read efrant's guide on flashing stock (sticky, general section)
Sent from my i9250
Few hours before this post I flashed a rooted version of android 4.3 from the thread by "Carlos_Manuel". However, following that the supersu was not working I flashed the supersu binaries over the ROM from TWRP. Since then, it is stuck in boot loop at the Google Logo. Tried flashing PA, Sourcery, CM but nothing seems to work. What should I do?
Flash the official Google image: http://forum.xda-developers.com/showthread.php?t=2376687
check dreams rom thread and see my post there
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Fix it by flashing factory images! do a full wipe, you can get imprtant stuff from your Nexus by using adb pull commands!
Users was blaming me when they screwed their Nexus with the root files!
I can successfully even flash old root files and no bootloops but ofc. root wont work if using those old root files.
OP, did you factory reset between ROM flashes?
beekay201 said:
OP, did you factory reset between ROM flashes?
Click to expand...
Click to collapse
pulling files then flashing 4.2.2 stock image to start fresh
NyPlaya513 said:
Ok, I am paranoid and want to be sure about this. I am in the same boat as the OP. I have a 32gb toro on twrp 2.5. I am under the impression that flashing the stock images will flash my sdcard partition and I want to pull some files if that is the case. Is there anyway to pull the files or am I stuck and need to start fresh.
Click to expand...
Click to collapse
You cant use the stock images they are for gsm not toro/cdma, have to use a custom zip only one is that light speed one in development right now I am waiting for muzzys but, full wipe, flash rom, gapps, supersu.
NeoMagus said:
You cant use the stock images they are for gsm not toro/cdma, have to use a custom zip only one is that light speed one in development right now I am waiting for muzzys but, full wipe, flash rom, gapps, supersu.
Click to expand...
Click to collapse
nvm pulling files
If you tried wiping just cache/dalvik after the flash I dont know there may be another way to get it to boot or not but yeah the factory image will start it over fresh and get you out of it
NeoMagus said:
If you tried wiping just cache/dalvik after the flash I dont know there may be another way to get it to boot or not but yeah the factory image will start it over fresh and get you out of it
Click to expand...
Click to collapse
nvm got the toolkit to pull files via adb for me on my parallels
agent47er said:
Few hours before this post I flashed a rooted version of android 4.3 from the thread by "Carlos_Manuel". However, following that the supersu was not working I flashed the supersu binaries over the ROM from TWRP. Since then, it is stuck in boot loop at the Google Logo. Tried flashing PA, Sourcery, CM but nothing seems to work. What should I do?
Click to expand...
Click to collapse
"just wipe data" in recovery after flashing, solve bootloop issue
dexviajiboy said:
"just wipe data" in recovery after flashing, solve bootloop issue
Click to expand...
Click to collapse
thanks for your help.. but I ended up flashing factory image of 4.3 which fixed the problem. Also I wnted to ask if you know of any 4.3 kernels that have implemented high performance audio mod. So far I have tried Faux and Hybrid but both dont have it.
agent47er said:
thanks for your help.. but I ended up flashing factory image of 4.3 which fixed the problem. Also I wnted to ask if you know of any 4.3 kernels that have implemented high performance audio mod. So far I have tried Faux and Hybrid but both dont have it.
Click to expand...
Click to collapse
i dont think there's any kernel for now, give it some time and you'll get one
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
I've been searching for answers for a while now including blogs and videos on numerous websites, but I can't seem to find any answers. I am typically pretty good at flashing anything on my phone, researching for answers, but I am definitely running into a wall at this point. I will admit, compared to most posts on here, I do consider my self a n00b still, so I will apologize in advance for sounding ignorant.
I have an SGH-I747 stock 4.3 i747ucuemjb stock kernel rooted w/ TWRP 2.6 and busybox installed. SuperSU updated and binaries updated. SuperSU asked to block knox, and by the looks of it (meaning no more error messages of apps being blocked) everything is running great on the phone. My problem is that I can't flash any custom roms on the phone. I've tried just about anything I can think of (from 4.3 to 4.4.2) and TW based, aokp, cynmod, etc.. I'm getting a prop error with either it stating that the rom is intended for d2spr when my phone is obviously a d2att. But mostly all the roms I've tried have been just flat out failing. I can't even do a backup within TWRP, it also fails.
I've had to re-flash my stock 4.3 rom several times this past week b/c if I try to flash anything over the stock rom (keyboard, roms, etc.) the phone buggs out and touchwiz crashes to the point it gives me a black screen with the pop-up indicating that Touchwiz has stopped working and won't let me hit close or ignore. Even after rebooting the phone, that's all I see. At this point, the phone will vibrate in a peculiar pattern (buzz----------buzz-buzz-buzz) and it will repeat that pattern times infinity.
I am desperate for suggestions. I have a strong feeling it's kn*x causing all the problems. I have learned to accept my mistake by installing the OTA 4.3 aka sucker. But I need to be on a custom rom again.
Are there any success stories with specific roms? Are there knox based roms?
Any help will be greatly appreciated.
I had a similar issue this week....this is what I did after trying a number of things. Mine is finally up and working, and I don;t know for sure if this is what caused it to work or not....but its worth a shot. I formatted the internal data, wiped cache, wiped dalvik....I did all of this about three times each. I then flashed the mjb bootloader and modem, wiped cache, wiped dalvik, then I flashed the AOCP ROM.....finally I was able to use my phone. After I got that ROM up and running I then went back and tried flashing other ROMS I previously couldn't..they all work now. I am not sure why, but it worked, could just be coincidence. I used CWM for recovery BTW.
Flashing the boot loader may have done the trick. That's the only thing I haven't tried bc I keep reading warnings about potentially bricking the phone when flashing the boot loader. Are you on a sgh-i747 also? If so, what bootloader did you use?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Castillo2.0 said:
Flashing the boot loader may have done the trick. That's the only thing I haven't tried bc I keep reading warnings about potentially bricking the phone when flashing the boot loader. Are you on a sgh-i747 also? If so, what bootloader did you use?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Yes i have the sgh-i747...and I flashed the MJB bootloader...so I can't go back to any ROM before 4.3.
Yeah i had a very similar issue too. I was on TWRP as well but then i switched to cwm and everything works fine now. I too am on the updated bootloader but you can still flash 4.1.2 roms that don't contain a bootloader. I'm currently running hyperdrive which is 4.1.2 based, no problems at all.
Sent from my SGH-I747 using Tapatalk