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.
Related
Got my brand new nexus today, rooted it using toolkit, then i wanted to install a rom. Everything went fine, flashed eagle blood, everything went fine. Then i downloaded an app and it took for ever to download so i rebooted my phone, then i was stuck with the dreaded animation lock. Now no matter what i do, i cant get past the animation. Still have access to CWM, tried a factory reset/cache wipe...but no success...
Any idead?
P.S. It's not me, it's my friends nexus! I got skyrocket!
Flash the stock ROM on the phone. You have access to recovery so use it then after you verify you can boot with the stock ROM then try flashing another ROM on again.
Personally as it is your friends phone if (s)he doesn't know how to flash ROMs then I would leave the phone stock.
No idea what caused you from being able to boot to this issue but this is my advice.
by that you mean to what??? because on the skyrocket flashing to stock rom is quite simple, via ODIN + Stock TAR...but how to do it on nexus?
Personally as it is your friends phone if (s)he doesn't know how to flash ROMs then I would leave the phone stock.
Click to expand...
Click to collapse
everybody has to start somewhere...you werent the android dev youself the first time you flashed. I brocked my skyrocket the first hour i got it because of a flailed flash...but today, 2 months later i can do anything with it
polish_pat said:
by that you mean to what??? because on the skyrocket flashing to stock rom is quite simple, via ODIN + Stock TAR...but how to do it on nexus?
everybody has to start somewhere...you werent the android dev youself the first time you flashed. I brocked my skyrocket the first hour i got it because of a flailed flash...but today, 2 months later i can do anything with it
Click to expand...
Click to collapse
Go into cwm, do a wipe and also go into advanced and wipe dalvik. You should then be able to reflash your custom rom to fix your boot loop. If thats successful then go back to cwm and make a NANDROID backup so they have a restore point if anything goes wrong in the future.
If you want to flash back to stock its quite simple and can all be done from my ToolKit. Its basically going to http://code.google.com/android/nexus/images.html and downloading the latest factory rom for your model, moving it to the correct folder in the ToolKit and then selecting option 8 from the ToolKit to extract the images and flash it.
Mark.
polish_pat said:
Got my brand new nexus today, rooted it using toolkit, then i wanted to install a rom. Everything went fine, flashed eagle blood, everything went fine. Then i downloaded an app and it took for ever to download so i rebooted my phone, then i was stuck with the dreaded animation lock. Now no matter what i do, i cant get past the animation. Still have access to CWM, tried a factory reset/cache wipe...but no success...
Any idead?
P.S. It's not me, it's my friends nexus! I got skyrocket!
Click to expand...
Click to collapse
I've run into the same issue tonight going back to Apex 1.0.2 from the 4.0.4 leak. I'm trying the suggestion below to wipe and re-flash the ROM. I'll report back when I'm finished.
Edit: Yep, it worked!
I've tried to flash the two different ROMs out for JB and for some reason it is not getting past the Nexus Logo Boot screen. I can flash any ICS ROM but JB never gets past the boot screen. I've been flashing ROMs since the OG Droid and have never experienced this before.
Steps already taken:
1) Full wipe
2) Format of system and data
3) executed Super Wipe Script
4) Battery Pulls
5) Backed out of CWM and unmounted system and data
6) Flashed Various AOKP and AOSP ROMs and tried to JB ROM from those ICS ROMs
7) Performed a factory restore of the phone using WugFresh's ToolKit (un-rooted and locked phone) and then Rooted, unlocked, and flashed CWM again
8) Flashed Team Win Recovery and re-flashed JB ROMs
I have tried everything I can think of and yet nothing has worked. Has anyone Else experienced this or does anyone have any suggestions on what I can possibly do to get past the Nexus Boot screen? Thanks in advance.
how long are you waiting after the install?
Zepius said:
how long are you waiting after the install?
Click to expand...
Click to collapse
Average wait time is 20 minutes but I've waited up to 4 hours.
which rom are you flashing?
try this one: http://www.teambamf.net/topic/4064-romtoro-jellybamf-13/
it works for me perfectly (thanks adrynalyne)
Zepius said:
which rom are you flashing?
it works for me perfectly (thanks adrynalyne)
Click to expand...
Click to collapse
I've tried Liquid Vicious Versions 1-3 and BAMF Versions 1.0 and 1.2. Thanks for the updated BAMF...I'll try that one now.
I am having the same problem as you, I flashed multiple JB roms and it is stuck at the X screen. I can flash ics roms easily tho.
I had the freeze at logo issue a few times while I was trying to get my JB up and running.
1. I got superwipe from http://forum.xda-developers.com/showthread.php?p=20473980
2. I dl JellyBelly and GApps from http://rootzwiki.com/topic/28677-rom-jelly-belly-v17-07012012-jellybean-41-its-all-about-speed/
3. Cleared cache/factory reset
4. Flashed and used superwipe
5. Flashed JellyBelly then GApps
I had to wait about 5 minutes while it booted. Hope this helps, yall.
I'll definitely try those steps...Thanks!
Sent from my HTC One X using Tapatalk 2
keno23 said:
I'll definitely try those steps...Thanks!
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Glad to pass along the help I got earlier :highfive:
consultant.ben said:
I had the freeze at logo issue a few times while I was trying to get my JB up and running.
1. I got superwipe from http://forum.xda-developers.com/showthread.php?p=20473980
2. I dl JellyBelly and GApps from http://rootzwiki.com/topic/28677-rom-jelly-belly-v17-07012012-jellybean-41-its-all-about-speed/
3. Cleared cache/factory reset
4. Flashed and used superwipe
5. Flashed JellyBelly then GApps
I had to wait about 5 minutes while it booted. Hope this helps, yall.
Click to expand...
Click to collapse
Unfortunately it did not work...same Nexus Bootscreen forever. Thanks though.
i have the same the problem with my phone , i flash the jb rom it works fine the first time booting i setup my account download my apps every thing works fine BUT when i re-start the phone the phone got stock on the google logo and don't re-start again, so guess what i have to try another rom so i try a regular ICS rom guess what on the first boot the phone got stock on the boot logo so i try another ICS rom and the same thing happing stock again on the boot logo, so i have to do flash the google factory rom to my phone got back to work
Same her.. infinite boot loop.. I'm tired of unbricking back to stock
Flash all kinds of from and kernel combo and still got boot loop.. I hope someone can help us with this..
Try mROM http://forum.xda-developers.com/showthread.php?t=1763823
Make sure wipe/factory reset and also wipe caches while you're at it. Also make sure that CWM is updated.
keno23 said:
Unfortunately it did not work...same Nexus Bootscreen forever. Thanks though.
Click to expand...
Click to collapse
Same here, I've tried just about every rom out there now and have cleaned the phone out several times. Wonder if there is anyone who had a boot longer than 20 minutes and finally was able to get it to boot, wonder what they did to get it to boot. I've waited hours with some of these roms and still no luck.
nothingshocking said:
Same here, I've tried just about every rom out there now and have cleaned the phone out several times. Wonder if there is anyone who had a boot longer than 20 minutes and finally was able to get it to boot, wonder what they did to get it to boot. I've waited hours with some of these roms and still no luck.
Click to expand...
Click to collapse
Are you wiping dalvik and system cache along with doing data wipe?
mb9023 said:
Are you wiping dalvik and system cache along with doing data wipe?
Click to expand...
Click to collapse
wipe data/factory reset -> wipe cache partition -> wipe dalvik -> format /system -> format /data -> format/cache. I've tried super wipe. All Roms never get passed the boot animation. I get past the "Google" unlock symbol, but it just sits at the boot animation. It doesn't reboot or anything, just sits there for hours or when I get bored looking at it after about 30 minutes or so.
@nothingshocking
We have the same problem.. I been flashing all kinds of jb rom since last week..I'm not new in flashing rom and kernel so I know what doing.. it so weird that it only stay in Google logo (x) when I flash jb rom..but if I flash ics it will boot up.. hayzzz I hope someone can help us with this issue.. calling all great dev. I hope u can help us..
Sent from my Galaxy Nexus using XDA Premium App
landrian18 said:
@nothingshocking
We have the same problem.. I been flashing all kinds of jb rom since last week..I'm not new in flashing rom and kernel so I know what doing.. it so weird that it only stay in Google logo (x) when I flash jb rom..but if I flash ics it will boot up.. hayzzz I hope someone can help us with this issue.. calling all great dev. I hope u can help us..
Sent from my Galaxy Nexus using XDA Premium App
Click to expand...
Click to collapse
Not going to happen man...I've tried EVERYTHING and have gotten feedback from various devs to no avail. All I get is Nexus boot logo FOREVER.
Solution is to flash it back to stock (plus unroot and re-lock) and then take it in to a store and get another one shipped to you since it's still under the annual warranty. As for the issue for bringing it in, just say it boot loops at random times (that's not technically a lie).
Sent from my Galaxy Nexus using Tapatalk 2
Have you tried flashing the JB Boot loader and then flashing the JB ROM??
It is from jakeday and his Jelly Belly ROM
adclem said:
Have you tried flashing the JB Boot loader and then flashing the JB ROM??
It is from jakeday and his Jelly Belly ROM
Click to expand...
Click to collapse
That doesn't work either. Thanks though.
Sent from my HTC One X using Tapatalk 2
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Did you wipe data and cache when you flashed the new rom?
nyyankees1237 said:
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Click to expand...
Click to collapse
a few questions:
and i can verify the issue is something on your end, because the ROM you tried was mine, and nobody has had that issue (not booting it)
do this...
1. make sure you have the latest version of clockwordmod, don't use twrp
2. re-download my ROM (just for sake of not adding any other variables to your issue, because mine should boot)
3. put ROM on external SD card
before continuing... take a quick look at my thread here in QA titled "flashing ROMs correctly every time" .... so you can get some instruction on verifying MD5 of the download... don't worry, the thread will explain that you...
now proceed
4. boot to recovery
5. do a factory reset - 3 times do this, just to be thorough. people will say you don't need to, but like i said, just for the sake of removing variables
6. go to mounts and storage, format system 3 times - (yes, through recovery as well)
7. flash ROM, and reboot
EDIT*** i will say this, ALWAYS format system when flashing a new ROM
cobraboy85 said:
a few questions:
and i can verify the issue is something on your end, because the ROM you tried was mine, and nobody has had that issue (not booting it)
do this...
1. make sure you have the latest version of clockwordmod, don't use twrp
2. re-download my ROM (just for sake of not adding any other variables to your issue, because mine should boot)
3. put ROM on external SD card
before continuing... take a quick look at my thread here in QA titled "flashing ROMs correctly every time" .... so you can get some instruction on verifying MD5 of the download... don't worry, the thread will explain that you...
now proceed
4. boot to recovery
5. do a factory reset - 3 times do this, just to be thorough. people will say you don't need to, but like i said, just for the sake of removing variables
6. go to mounts and storage, format system 3 times - (yes, through recovery as well)
7. flash ROM, and reboot
EDIT*** i will say this, ALWAYS format system when flashing a new ROM
Click to expand...
Click to collapse
thanks for the info, will try this all out soon. I've been flashing roms for years now and have never run into anything like this, and as previously stated, this didn't occur solely with your rom which has me thinking something has happened to the phone itself. will get back to you soon and once again thank you
chucktdriscoll said:
Did you wipe data and cache when you flashed the new rom?
Click to expand...
Click to collapse
of course, wiped data, cache, & delvik
nyyankees1237 said:
of course, wiped data, cache, & delvik
Click to expand...
Click to collapse
my point is...
coming from a cm based ROM, or aokp, whatever you said... you would want to format system as well.
nyyankees1237 said:
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Click to expand...
Click to collapse
I was having some of the same issues. I downloaded XquiziT's Superwipe and ran it by installing from external sd card. I ran it three times to clear everything out, then I wiped data, cache and the rest three times.
No probs for me after that.
Will definitely give that a try as well! Thank you! Will post my results when the holiday is over.
Happy thanksgiving
Sent from my SGH-T999 using xda app-developers app
I have tried everything over and over. But I am unable to get my phone to boot anything but 4.2.1. I am rooted and using TWRP 2.6.0.0 (the latest). I have tried a few different ROMs: Carbon, EAS, AOSPA, PA 4.2.2 and 4.3 versions and can't get it to boot past the boot animation. It will just hang there. I tried flashing stock 4.2.2 but Odin won't recognize the phone and couldn't find an update zip for 4.2.2. I have literally been trying all day and haven't gotten any custom ROM to boot. All clean flashes. Any help would be great. If you want more info just ask
Device: Toroplus (sprint galaxy nexus)
Version: 4.2.1
Also some background info: I was previously using carbon Rom on their latest nightly before 1.8 and was wiping my phone and for some reason I wiped data with twrp which deleted everything off my device. I had to then push slim Rom beta 1 (their 4.3 build which is what I was doing this whole thing for in the first place) using adb. I flashed that tried booting and it worked once. Reboot and it got stuck at the Google logo. Tried reflashing and clearing cache but nothing worked. Tried all the ROMs I listed but nothing no one got past the boot animation. Then I unrooted my phone with the stock 4.2.1 and tried all that again after rooting and again fail. Idk what else to do honestly
Are you sure you're flashing the ROMs from the sprint gnex section?? Always rule out the easiest things first, is why I ask
Sent from my Galaxy Nexus using Tapatalk 2
Or try to flash stock via fastboot.
Sent from my Galaxy Nexus using XDA Premium HD app
Yep positive I'm flashing the right ones. Tried using fastboot to flash fc12 or whatever the latest was and that hung on the boot animation also.
I've definitely covered my bases. Things I do remember setting in the dmesg were could not find firmware for mms something and hdcp: failed to load keys. maybe that helps? This does not occur when booting stock 4.2.1 rooted
Any suggestions anyone?
herousr said:
I've definitely covered my bases. Things I do remember setting in the dmesg were could not find firmware for mms something and hdcp: failed to load keys. maybe that helps? This does not occur when booting stock 4.2.1 rooted
Click to expand...
Click to collapse
HDCP has to do with DRM decryption of video files over HDMI. Normal. That doesn't single handedly causes the device to fail boot up. You have a copy of those logs?
a manta sent this.
beekay201 said:
HDCP has to do with DRM decryption of video files over HDMI. Normal. That doesn't single handedly causes the device to fail boot up. You have a copy of those logs?
a manta sent this.
Click to expand...
Click to collapse
Not right now I'll try and pull them tonight or tomorrow and post
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