[Q] Please help! Stuck and can't use phone. - T-Mobile Samsung Galaxy S II SGH-T989

This morning I was using font installer to change my system font . I guess somewhere along the way something got messed up because when I went to reboot it gets to the boot animation and turns off. Not exactly a boot loop but useless anyway. I could just go into recovery and reflash. The problem is I can't get the phone into recovery. I use TWRP. I hold volume up and down and power, the TEAM Win blue screen and logo comes up but then what do I do? If I keep holding it down then it just goes into that mode where it vibrates every second and nothing happens.if I let go then the blue logo screen goes away and it tries to boot up normally again. What am I missing here? Why can't I get into recovery so I can reflash... Thanks for all Your help guys!

have you tried using adb commands? Also if you have not gotten into recovery as of now you just have to keep trying with the vol and power key buttons you will get it.
ADB choices
Plug phone into pc and type adb reboot recovery and hope for the best

I think you might be able to reflash/reinstall the recovery using adb commands and that might work too. Worst comes to worst, you could try using ODIN to restore your recovery or whole phone, but you'll probably lose anything not on SD.
And I haven't used font installer in ages, but I had issues with it on my SGSII because I think it flashes system files; I know it doesn't help now, but I'd stick to using font apks, since our phones support that.
Russian smashed across the interwebz from my Galaxy S2.

Sometimes this happens with fonts that are not designed for whichever version of android you are running. Its not all of them believe me, as well as this is honestly an easy fix. This is why I believe in knowing everything about your phone prior to doing stuff to it and knowing how to escape 90% of the issues that may come your way.

Thanks alot. the annoying part is that TWRP blue screen comes up but nothing happens. It just kinda flashes like a crt tv off and then goes into the vibrate every second thing. I typically do alot of reading and research prior to doing anything and I used to use the font app before on the HD2 so I was suprised this happened. I guess you live and learn. I just thought that was one of the benefits of having a recovery so you Could fix stuff like this. it doesn't help if you Can't even get into recovery. I never had this problem with Cwm Recovery.

I got it to work! I guess it's all about the timing for when to release the buttons to get into recovery. I flashed the rom back and all is well. Or at least getting there. Thanks everyone for the help. Hopefully this thread will help someone else in the future. Lesson Learned: Don't give up on trying to boot into recovery. It will work. You just have to release the power and volume button at just the right time to get everything going. Lesson 2: Don't use the font installer app....

Related

[Q] Help! Unlocked bootloader, installed CWM, now phone won't boot

I used the GN Toolkit V2.2 to unlock the bootloader, after installing the adb drivers via PDANet. I flashed Clockwork Mod on as well, and was going to install the Android Revolution ROM. I thought I had already copied the zip file to the internal storage, but when I tried to flash it from inside CWM, it said no files were found. (May have copied it before wiping device, I can't remember). So I restarted so I could copy the zip file again and then flash it. However when starting, it seemed to be stuck on the startup screen, with all the flashing blocks of color fading in and out. After a while stuck on there I couldn't do anything so I did a battery pull to restart. At this point, I can start normally or into recovery mode. If I try to start normally, (or go into recovery mode and choose restart from the submenu), it shows the black screen with the white Google logo, and the unlocked icon, stalls for a few seconds, then does a short vibrate and reloads the logo again. It will keep doing this and not go any further. I tried doing an additional data wipe from recovery mode but that didn't help, and I tried to do USB mount from recovery mode, hoping to copy the Revolution zip file and flash it over, but it couldn't mount. I'm starting to panic a little bit, did I brick or otherwise mess my phone up? What can I do? Any help is REALLY appreciated.
Thanks so much and I hope this is the right forum.
I dont have the answer but I wanted to post to calm you. This happens a lot.....multiple times to me on my android devices. You live and learn next time, do a backup in cwm before wiping data and flashing new stuff
Im sure someone will post shortly to solve your problem
Well ok that is reassuring thanks. I downloaded the Google factory ROM from the code.google.com and was able to flash that on my phone with GN Toolkit. It is trying to boot right now, still on the colorful screen. I think maybe I didn't give it enough time last time around? At least I'm past the black and white logo screen. So I'll let it sit for a few minutes and see what happens.
Edit: I let it run for a couple minutes, and it blacked the screen for a sec, showed the white Google logo again, and then went into the colorful startup screen again. I think it's working now so that's a relief.
If someone finds this thread in the future with a similar issue: Don't battery pull during start up and be patient if you don't want to freak yourself out haha. But as spitefulcheerio said, it will be okay so just don't panic. Thanks again.
Make sure you do a Factory Reset in STOCK recovery after unlocking the bootloader. THEN install CWM. learned that one the hard way. skipped a step after doing the oem unlock.
Yes, first time will take awhile on the boot animation.
And, as long as you see the google logo, you are ok, even if it freezes on that. They designed this phone to be easy
Sent from my Galaxy Nexus Bugless Beast 4.0.3 lte +franco#6
Guess all I needed was a psychological confidence boost, thanks for everyone for being supportive I thought I just threw a few hundred bucks away. But I got Revolution installed, phone and rooted and runs like a dream. Thanks all around!
mynameismolotov said:
I used the GN Toolkit V2.2 to unlock the bootloader, after installing the adb drivers via PDANet. I flashed Clockwork Mod on as well, and was going to install the Android Revolution ROM. I thought I had already copied the zip file to the internal storage, but when I tried to flash it from inside CWM, it said no files were found. (May have copied it before wiping device, I can't remember). So I restarted so I could copy the zip file again and then flash it. However when starting, it seemed to be stuck on the startup screen, with all the flashing blocks of color fading in and out. After a while stuck on there I couldn't do anything so I did a battery pull to restart. At this point, I can start normally or into recovery mode. If I try to start normally, (or go into recovery mode and choose restart from the submenu), it shows the black screen with the white Google logo, and the unlocked icon, stalls for a few seconds, then does a short vibrate and reloads the logo again. It will keep doing this and not go any further. I tried doing an additional data wipe from recovery mode but that didn't help, and I tried to do USB mount from recovery mode, hoping to copy the Revolution zip file and flash it over, but it couldn't mount. I'm starting to panic a little bit, did I brick or otherwise mess my phone up? What can I do? Any help is REALLY appreciated.
Thanks so much and I hope this is the right forum.
Click to expand...
Click to collapse
cancerouspete said:
Yes, first time will take awhile on the boot animation.
And, as long as you see the google logo, you are ok, even if it freezes on that. They designed this phone to be easy
Sent from my Galaxy Nexus Bugless Beast 4.0.3 lte +franco#6
Click to expand...
Click to collapse
mynameismolotov said:
Guess all I needed was a psychological confidence boost, thanks for everyone for being supportive I thought I just threw a few hundred bucks away. But I got Revolution installed, phone and rooted and runs like a dream. Thanks all around!
Click to expand...
Click to collapse
To provide some technical details on why it takes longer the first boot and appears to "hang" at boot animation ...
During the boot animation, the /data/dalvik-cache directory is built up for each application loaded on the device. This occurs during the very first boot. If the /data partition is wiped, the dalvik-cache directory is also wiped and will have to be rebuilt on the first boot. All subsequent boots will be quicker as this directory has already been populated.
Whenever loading a new ROM or performing the fastboot oem unlock command, the /data partition is generally wiped which takes with it dalvik-cache and results in the delayed initial boot time while the dalvik-cache directory is re-populated.
Hope that makes sense and fills in a few blanks on the why Android appears to "hang" at the boot animation during first boot after the /data partition is erased or the /data/dalvik-cache directory is erased.

[Q] HELP!! New stock nexus ui crashed, stuck at boot animation

Stock galaxy nexus, ui force closed. Powered off. Can get into recovery mode to attempt to reinstall stock rom. It shows a droid with an opened chest, with a red triangle above it when I try to go to recovery mode from the odin screen.
Anyone else have this issue? Is there a way to flash using a mac? I have limited access to a pc.
Thanks all.
This is the hspa version.
svntsvn said:
Stock galaxy nexus, ui force closed. Powered off. Can get into recovery mode to attempt to reinstall stock rom. It shows a droid with an opened chest, with a red triangle above it when I try to go to recovery mode from the odin screen.
Anyone else have this issue? Is there a way to flash using a mac? I have limited access to a pc.
Thanks all.
Click to expand...
Click to collapse
The android icon you're referring to sounds like the stock recovery. In order to flash a ROM (even stock) from recovery mode, you'll need to load a custom recovery. This requires the device to be unlocked.
Not very often a stock setup needs to be restored. Generally, with the stock setup, only the /data partition is wiped (revert to factory default) and the issues are cleared. Not sure why a stock setup would need to be restore.
If you're still going to pursue reloading the system, without access to the normal android mode, the best route will be using fastboot. This can be done on a mac and the fastboot commands should be the same.
Hope that helps get a start!
This happened me earlier. I was able to factory reset it, which, unfortunately really annoyed me because I hadn't saved a backup..
Before the "Google" logo shows up, press and hold the power button and the volume up and down buttons.
Then go into recovery mode using the volume buttons.
When it reboots, you get that Droid with the hazard sign (which I know you're at, but just for the sake of others who need help) all you have to do is hold down the power button and WHILE it's held, press the volume up or down button and move to "Factory Reset". When you hold down the power button and press the volume rocker, a little menu will appear. It should only take a few minutes then.
Hope this helps. Apparently this is a WiFi issue. I'll definitely be keeping backups as of now..
I left it off, plugged it back in for a couple of hours and it booted right up. Strange.
I'm wondering if it had anything to do with juice defender and its settings that take effect at a lower battery level? Its the only thing I can come up with. Never had a stock phone's ui force quit and not reboot. The battery was definitely up to 25% given the time it was initially charging, but maybe it was still interfering.
Well, now that she's running, time to get root, recovery, rom and rejoice.
Thanks for the replies, very much appreciated.
svntsvn said:
I left it off, plugged it back in for a couple of hours and it booted right up. Strange.
I'm wondering if it had anything to do with juice defender and its settings that take effect at a lower battery level? Its the only thing I can come up with. Never had a stock phone's ui force quit and not reboot. The battery was definitely up to 25% given the time it was initially charging, but maybe it was still interfering.
Well, now that she's running, time to get root, recovery, rom and rejoice.
Thanks for the replies, very much appreciated.
Click to expand...
Click to collapse
I had the exact same problem happen last night with UI crashing and then the getting stuck at the boot animation. I was desperately searching online, looking to find a solution that didn't involve rebooting to factory setting and came across this post and did exactly what you did and it WORKED, very strange, I really wanna know what caused that!!!!
I've had the same problem with my Galaxy Nexus. I received it on December 21st, with stock 4.0.1 build. No root or unlock attempt at any time. On January 2nd I experienced this problems (UI process crash, screen not responding, reboot and stuck in boot animation).
The only solution was to do a factory reset and start over.
On January 10th same problem, same solution. Second factory reset.
I got the 4.0.2 OTA just two days after that. I thought that would resolve the problem. The phone seemed more stable, with less FC's and no trace of the UI crash. Indeed it lasted long...
Exactly until January 24th when I picked up the phone and seemed in the sleep of dead. Removed the battery, restarted the phone... and stuck in the boot animation.
Do you have any advice? Should I return the phone? Aside from those specific problems I am quite happy with the SGN and Android 4 in general. And I use it quite a lot (I have a very long train commute) without other problems.
Again...
It happened again!!
I don't know what to do anymore, this is not a usable phone when I have to reinstall and reconfigure every 3 weeks.
I may have found the problem
Well, not me exactly, but this bug report seems to fit the problem and the charging workaround. Seems to be a problem the file used to store the battery stats and draw the charge graph.
It also fits my usage (I try not to charge it up until 100%).
I can't post links to the forum, the issue is id number 24518 which you can find in code.google.com/p/android/

[Q] Can't access bootloader at all. Please help!

Hi guys
I've searched the forum for something like this but I'm coming up empty handed. But then again, I'm freaking out a bit.
I just tried flashing ARHD 9.7.0 and I've hit a big snag... For a bit of background, I was previously running ARHD 9.4.2 with the Endeavoru-Faux123-010b3 kernal. The battery was at 35% when I started the process...
I downloaded the zip, put it onto my SD card and rebooted into CWM. No worries there.
Did a wipe/factory reset and wiped the cache aswell. No worries there.
I did NOT flash the boot.img in the zip as I believed it would work okay with the current kernel (possibly the issue)
Went to install zip from SD card and chose the zip to install. AROMA starts up and I go through the familiar install process. No problem there.
I checked the reboot now option in AROMA and let it reboot. This is where the fun begins...
I get the beepy boopy start up sound and let it sit there because, as we all know, first boot can take a while. 10 minutes later, it's stuck at the HTC One splash screen. So I thought I'd reboot into CWM and start over like I've done with other ROM/kernal incompatibilities.
So I hold down the power button, let the three lights blink and the screen go blank and hold down the volume down button. And it goes back to attempting to boot up. I've tried different combinations of holding the buttons down and letting them go and hell, I've even sat there hammering the volume down button while it starts up! Still, I can't get into the bootloader.
Obviously, no bootloader, no ADB connection so I can't go through CMD and can't re-flash the kernel.
I'm currently sitting here looking at it. The USB cable is plugged in and the orange light is lit up so I hope it's charging. I'm at a loss here guys. Please, if anyone can give me some help, I will be most appreciative.
I'm really sorry to have wasted your time. It worked eventually after about 50 tries! :laugh:
Looks like it ws a kernel incompatibility.
But out of curiosity and for anybody else who gets this problem and really can't boot into the bootloader, what would be the steps involved in recovering a device in that state? I'd rather look like a knob in public as long as something constructive comes from it. :silly:
It's a bit tricky to get into hboot after a forced reboot, I think we've all been there
Just avoid the problem altogether by flashing the boot.img inside the zip first to make sure that it boots. Once up and running, flash your custom kernel and modules.
Try this http://forum.xda-developers.com/showthread.php?t=1734365
And don't let go when reboots keep hold of buttons and it should go to bootloader
Sent from my HTC One X using xda premium

Phone is stuck on teamwin screen flashing on and off.

I cannot use the hardware buttons any longer to even get into fastboot mode. I tried to insert a new TWRP theme, named it ui.zip, place it in the theme folder, then rebooted the phone and now it will not even go into recovery, fastboot mode, nor turn on. Anybody have any suggestions on how to get through to the recovery. I guess I locked up the recovery, and can no longer boot my phone to even be able to delete that ui.zip file from the theme folder under TWRP.
OK, now I managed to get it into fastboot mode. But that is it.
Can I extract a file from the phone in fastboot mode?
Thanks,
chevy383surfing
Well, I finally figured it out. I'll add an explanation on this whole deal after I get off work. Just in case anybody else runs into the same problem, maybe my little routine will help someone else.
chevy383surfing said:
I cannot use the hardware buttons any longer to even get into fastboot mode. I tried to insert a new TWRP theme, named it ui.zip, place it in the theme folder, then rebooted the phone and now it will not even go into recovery, fastboot mode, nor turn on. Anybody have any suggestions on how to get through to the recovery. I guess I locked up the recovery, and can no longer boot my phone to even be able to delete that ui.zip file from the theme folder under TWRP.
OK, now I managed to get it into fastboot mode. But that is it.
Can I extract a file from the phone in fastboot mode?
Thanks,
chevy383surfing
Well, I finally figured it out. I'll add an explanation on this whole deal after I get off work. Just in case anybody else runs into the same problem, maybe my little routine will help someone else.
Click to expand...
Click to collapse
Next time you loop, vol up and power for 10 seconds with phone Unplugged, then vol down and power to go to boot loader
If for some reason it doesn't restart put the phone close to a bright light
Similar problem
Hi. I am on a Kindle Fire HD 7 and just got cynogeanmod 12. I was going through settings when device got laggy. And somehow the device thought I wanted factory reset so thats what it did. My Kindle Rebooted and now I get a screen that says "teamwin" and every 2 secs. the screen flashes. None of the tips using buttons worked. It can only turn on and off. I need assistance in finding a way to get this back to stock(from there I can re-root and do the process again to get back cynogeanmod).
Thanks,
aputtapa000
aputtapa000 said:
Hi. I am on a Kindle Fire HD 7 and just got cynogeanmod 12. I was going through settings when device got laggy. And somehow the device thought I wanted factory reset so thats what it did. My Kindle Rebooted and now I get a screen that says "teamwin" and every 2 secs. the screen flashes. None of the tips using buttons worked. It can only turn on and off. I need assistance in finding a way to get this back to stock(from there I can re-root and do the process again to get back cynogeanmod).
Thanks,
aputtapa000
Click to expand...
Click to collapse
First, this is the M8 forum, not the Kindle forum. However, I actually can help you with that.
Most stock recoveries seem to have a problem with doing factory resets. Flash the stock recovery for your device, let it perform the factory reset, boot back into the OS (to make sure it worked), then reflash your custom recovery.
jshamlet said:
First, this is the M8 forum, not the Kindle forum. However, I actually can help you with that.
Most stock recoveries seem to have a problem with doing factory resets. Flash the stock recovery for your device, let it perform the factory reset, boot back into the OS (to make sure it worked), then reflash your custom recovery.
Click to expand...
Click to collapse
Tank you for this quick reply :good: . I will try to get back into my stock recovery but if it is on my device, how will I access this on my computer and force flash it on my tablet. I only need help making the tablet responsive/workable. Once this is done I should be able to figure out the rest.
Thanks

[Q] hard brick s2

If any one can help with any idea I would really appreciate it.
So I let my little brother play my s2 and he completely ran the battery out.
now I have left it on the charger over night, when i go to boot into recovery. You feel the phone vibrate then see the samsung for a split second, and if you keep holding the power you just feel the phone keep vibrating. The screen never turns back on. Now I know it works because i was able to boot recovery once, when i did that i just tried a full wipe and reboot. phone kept boot looping, so i pulled battery, but now i cant get into download mode or recovery.
Please help, or atleast let me know that its not fixable
thanks
You are supposed to let go of power after the first vibration. ?
Try downloading a stock ROM (.tar format, I believe) and flashing it, using ODIN. That worked for me when I bricked my SGH-T989.
I later had to install a new recovery, but you can play around and see what needs doing.

Categories

Resources