Problem Booting - T-Mobile Samsung Galaxy S II SGH-T989

so heres my problem. i had slimbean 4.1 on my device and it worked great. but i got a new phone and left it in a drawer
decided to give my phone to my sister and the update message showed up in my notifications
i downloaded it and flashed as i have a million times before
then i was stuck in a bootloop.
i did the usual, full while, cache and dalvik, and no success, the same has occured with every rom except the miui rom for some reason that one works
i have noticed that i can not factory reset the normal way, i have to use the alternate under settings in twrp
i have also used the super scripts and i noticed that it gets stuck on clearing the cache, any ideas?

supercharge1 said:
so heres my problem. i had slimbean 4.1 on my device and it worked great. but i got a new phone and left it in a drawer
decided to give my phone to my sister and the update message showed up in my notifications
i downloaded it and flashed as i have a million times before
then i was stuck in a bootloop.
i did the usual, full while, cache and dalvik, and no success, the same has occured with every rom except the miui rom for some reason that one works
i have noticed that i can not factory reset the normal way, i have to use the alternate under settings in twrp
i have also used the super scripts and i noticed that it gets stuck on clearing the cache, any ideas?
Click to expand...
Click to collapse
Are you still using the same version of TWRP you used to flash slimbean 4.1? If you are trying to flash newer ROMS with an older version of TWRP, that could be causing the problem.

supercharge1 said:
so heres my problem. i had slimbean 4.1 on my device and it worked great. but i got a new phone and left it in a drawer
decided to give my phone to my sister and the update message showed up in my notifications
i downloaded it and flashed as i have a million times before
then i was stuck in a bootloop.
i did the usual, full while, cache and dalvik, and no success, the same has occured with every rom except the miui rom for some reason that one works
i have noticed that i can not factory reset the normal way, i have to use the alternate under settings in twrp
i have also used the super scripts and i noticed that it gets stuck on clearing the cache, any ideas?
Click to expand...
Click to collapse
Try TWRP 2.6.1.0

Related

[Q] LeeDroid HD V3.0.3 GB crash after install

Having trouble with the latest LeeDroid HD ROM have flashed many LeeDroid roms before without issue but for some reason aftering clearing all caches and running the latest rom it will install ok but on reboot it just hangs on the White HTC screen and won't boot in.
Any Ideas what could be causing it?
Currently Running LeeDroid HD v3.0.1, LeeDroid Kernel v3.1.1 radio 12.54.60.25_26.09.04.11_M2
Make sure you're deleting all data do a full factory reset (deletes all data does not actually restore to factory condition) then clear the dalvik cache, re apply the ROM make sure its CLEAN and you haven't modified it, don't apply any themes or anything, then let it boot and be patient.
Try downloading it again also it could be a corrupt download.
m3t4lh34d said:
Having trouble with the latest LeeDroid HD ROM have flashed many LeeDroid roms before without issue but for some reason aftering clearing all caches and running the latest rom it will install ok but on reboot it just hangs on the White HTC screen and won't boot in.
Any Ideas what could be causing it?
Currently Running LeeDroid HD v3.0.1, LeeDroid Kernel v3.1.1 radio 12.54.60.25_26.09.04.11_M2
Click to expand...
Click to collapse
I had similar issue few days back. But i had the Leedroid rom (same rom,kernel as urs) already runing flawlessly for a few days. It decided just to hangs at the same HTC Screen... tried to clear caches(all), hard reset, reflash same rom... still stuck same place. I finally had to flash stock 1.32 image, root all over again, etc. ... and flash Leedroid (same) again... works fine now
I got the feeling that I made my friends with their stock DHD and Iphone users drooling and jealous of my phone(csutomised with sense 3.0 stuffs), and they collectively jinxed my phone, and had this crash! lolz
btw. i flashed SAME rom i had on my sdcard, so I think the rom fine(mine at least). just something triggered that crash!
all the best...
Yea i tried reflashing from stock rom the other day loaded up one of the RUU exe's and rerooted etc and tried to reflash with no luck so i'm all out of ideas
raidenxl said:
Make sure you're deleting all data do a full factory reset (deletes all data does not actually restore to factory condition) then clear the dalvik cache, re apply the ROM make sure its CLEAN and you haven't modified it, don't apply any themes or anything, then let it boot and be patient.
Try downloading it again also it could be a corrupt download.
Click to expand...
Click to collapse
Have also done factory reset and cleared dalvik cache etc. no joy
Just managed to find a copy of LeeDroid HD V3.0.2 have installed and found it also crashes but.... it gets to the LeeDroid Android screen, little further but unfortunately still crashes
Managed to get 3.0.3 working on my DHD turns out it was just down the cwm version i had, updated to 3.0.2.5 and boom worked first time =D only problem i have had with both 3.0.1 and 3.0.3 is the camera keeps dropping out, app doesn't force close but the screen keeps going black and all buttons dissapear then all comes back... =( Atleast i'm up to date though
Any Idea's on the Cam issue?
have run logcat and noticed the following in the log
W/mm-camera( 1400): config_proc_CAMERA_STOP_SNAPSHOT: state is not correct ctrl->state = 25 W/mm-camera( 1400): VFE_RESET_ACK illegal ctrl->state 24
dunno if that makes any sense to anyone
tinkered with it a little last night didn't seem to make a difference so left it over night and for some odd reason works fine this morning i think the issue was down the camera app itself but it looks to be working fine now thankfully
UPDATE:
Ok looks like the issue is still there found out what is causing it thought, the camera works fine but...only when wifi is off, if you turn wifi back on you get the same issue as before,
Please anyone got an idea on wtf?
UPDATE2: have worked out it must be the camera app due to the fact i download a different app which appeared to work fine. Not sure why there's a glitch though

CM10.1.3 crashed and softbrick

I have been running CM 10.1.3 for quite a while, and 10.1.2 for a while before that, and out of nowhere last night I was on the browser and it closed, and wouldn't open again. Then every other app I tried wouldn't open, just forced closed right away. Next thing I know, trebuchet starts force closing over and over. So I reboot my phone, and no bootscreen. I used TWRP to recover back to stock and it works fine. But everytime I try to re-install CM it just bootloops. I didn't change anything on my phone for it to crash, i haven't even changed any apps for a few weeks. Anyone know why it would do this?
jamesclay89 said:
I have been running CM 10.1.3 for quite a while, and 10.1.2 for a while before that, and out of nowhere last night I was on the browser and it closed, and wouldn't open again. Then every other app I tried wouldn't open, just forced closed right away. Next thing I know, trebuchet starts force closing over and over. So I reboot my phone, and no bootscreen. I used TWRP to recover back to stock and it works fine. But everytime I try to re-install CM it just bootloops. I didn't change anything on my phone for it to crash, i haven't even changed any apps for a few weeks. Anyone know why it would do this?
Click to expand...
Click to collapse
Do you have TWRP version 2.6.3 by any chance? Most of the bootloop bugs have been attributed to that specific version.
If you do have 2.6.3, downgrade to, I believe, 2.6.1. Otherwise, did you forget to do a cache, dalvik cache, data, and system partition wipe before upgrading your ROM?
sagirfahmid3 said:
Do you have TWRP version 2.6.3 by any chance? Most of the bootloop bugs have been attributed to that specific version.
If you do have 2.6.3, downgrade to, I believe, 2.6.1. Otherwise, did you forget to do a cache, dalvik cache, data, and system partition wipe before upgrading your ROM?
Click to expand...
Click to collapse
Actually, I am running 2.4.4. Whats still odd about it though is that it ran fine for at least a month and had been on all day. The problem didn't start with a reboot, I had been on it for a while and everything forced closed on me. I am about to try to update TWRP to 2.6.1 and try that. I haven't tried any other roms yet either, I would really like to stay on CM though if I can get it to flash back.

[Q] Phone suddenly stopped working with 4.4

Hi,
I was running AICP android 4.4 fine for weeks.
Then it kept hanging at boot screen , well just after when screen went black
Only way I could get to boot was clearing cache and re-boot. Worked OK then same thing any re-boot. This got worse and worse until nothing would boot.
I have found this isnt an ACIP issue all kitkat roms do this now on my phone (has now become they never boot). If I put 4.2.2 back on works perfectly
Im flashing the boot.img and reseting factory, dalvik and cache before flashing
Any ideas - really dont understand why 4.4 worked for a fortnight before becoming problematic and then being impossible to work
m60kaf said:
Hi,
I was running AICP android 4.4 fine for weeks.
Then it kept hanging at boot screen , well just after when screen went black
Only way I could get to boot was clearing cache and re-boot. Worked OK then same thing any re-boot. This got worse and worse until nothing would boot.
I have found this isnt an ACIP issue all kitkat roms do this now on my phone (has now become they never boot). If I put 4.2.2 back on works perfectly
Im flashing the boot.img and reseting factory, dalvik and cache before flashing
Any ideas - really dont understand why 4.4 worked for a fortnight before becoming problematic and then being impossible to work
Click to expand...
Click to collapse
You don't need to reset to factory you need to format data,system, cache and dalvik cache this is full wipe. Don't format your SD

OK, I'm stuck [T700]

I've been trying to update my firmware all day, I'm running TWRP2.8.7.2, updated to the newest bootloader, and tried 6 different ROMs, nothing will boot, except the alpha AOSP Marshmallow, but with that play services keeps crashing as soon as I try to set up my google account, and I can't get past the first run wizard. I've wiped my cache and data and internal storage a couple times now, and nothing is working. could someone give me an idea? I've never had so much trouble flashing a device before.
try going back to 100% stock by flashing stock firmware on ODIN. Next root and twrp.
sarreq said:
I've been trying to update my firmware all day, I'm running TWRP2.8.7.2, updated to the newest bootloader, and tried 6 different ROMs, nothing will boot, except the alpha AOSP Marshmallow, but with that play services keeps crashing as soon as I try to set up my google account, and I can't get past the first run wizard. I've wiped my cache and data and internal storage a couple times now, and nothing is working. could someone give me an idea? I've never had so much trouble flashing a device before.
Click to expand...
Click to collapse
I have a t700 and had the same problems you have installing marshmallow. What worked for me was advanced wipe in twrp, everything except internal storage and sd card. From there hit the home key, and flash the marshmallow rom, then reboot into recovery, next flash su 2.5x, then reboot into recovery. Lastly, flash the benzo gapps, and reboot system. My play store started working after i installed in that sequence on t700. Ive heard a few others have had to do that process 2 or 3x before it works, and some, it doesnt work at all. Worth a try though. Good luck.

bootloop or something like it after updating CM

First, for shortening and simplicity let's use cm versions only last numbers (cm-12.1-20151230-NIGHTLY-nicki will be 30 etc.).
I will arrange my short story in points for better understanding, let's begin here:
- I installed CM 23 (it's 12.1 but the number is for nightly like shown higher) and updated to 26, everything was fine
- quick install of Open Gapps, my apps and doing settings stuff, everything fine
- wild update to 30 appeared, i updated it and it was not very effective
- device rebooted, flashed update automatically, optimized apps aaaaand it got stuck on finishing boot. it was fully ok and responding cause a sound played when i plugged it to charging, it was showing touches ( i set it to show em before update), but it was stuck. So i took battery out and it started to boot, after couple of seconds screen brightness turned down as in every normal booting, boot animation slowed and lagged a few times but then continued to bootloop. Here is a list of things i tried:
- rebooting of course
- clearing cache and dalvik in twrp, then it just optimized apps again and got stuck on starting apps
- wiping data, still bootloop
- wiping everything and installing fresh CM 30
Only the last worked but i lost everything i installed etc. I made a backup of data partition but it restored only some apps ( not even gapps) and settings for some reason.
so after installing everything again i lived it for a while, but because it is a nightly a new update was posted! CM 104
- i downloaded it in cm updater as every other update (btw flashing cm 26 and then 30 from .zip gave the same result), installed it, and it worked soo...
- two days later another update appeared(cm 106), i check every update changelog and this one was big.
- happy of last successful update i just updated it but this time it didn't worked so well
everything is the same as updating 26 to 30, and here we are it got stuck on finishing boot, i took battery out, bootloop, clearing cache and dalvik, optimizing apps, got stuck on starting apps, system fully responding to the same things. i turned the phone down and started this thread.
I have a full backup of everything on another sd with cm 30 and installed apps, but because system is responding i think you guys can help me. i don't want to do a clean install every time a not working update appears. I could stay on last working version, but i'm a type of a person who wants everything updated even if won't give me anything new so staying on last working version from backup is only accepted if you guys won't have any solution or at least idea.
Big thanks for everyone that will bring anything here and probably save some time another happy cm user
EDIT: also, i can restore that backup i have and install version 104, and then figure out how to install it properly
my own idea
so, now i have restored my backup and when i have some free time i'll try to install fresh cm without gapps and update it a few versions, if it'll work problem solved. i will have to just clear cache and dalvik after every update and flash gapps. I only want to ask, if it will work, will flashing gapps with the old ones installed make any issues?
Try to re install rom after full wipe
rohitnegi44 said:
Try to re install rom after full wipe
Click to expand...
Click to collapse
i specially wrote this thread with extra simplicity, but you didn't read that it's working after full wipe, i'm trying to install update AND save my data. read before you post and try to get some easy thank points or whatever this forum has somewhere else.
FIXED IT!!
So for everyone who's looking for answer to this problem here's the fix: after cm flashes and turns off, hold VOL+ button to go to recovery instantly then wipe cache and dalvik, flash gapps, again wipe cache and dalvik reboot. For me it worked.

Categories

Resources