Database Users

[Q] Need help with semi/soft brick!

So my Vibrant has been turning off randomly. I think its because of the loose battery or maybe it's just over-heating. But a few days ago, after turning it on there is only a black screen and lit capacitive buttons at the bottom.
It boots up normal, with the vibrant name, t-mobile animation, and the Galaxy S boot animation, then black screen! This started to happen after a few reboots, and now it won't rebbot properly, just black screen. It seems like I have to restore my phone, but the problem is I cannot get the phone into recovery or download mode! Please advise.
Samsung Vibrant, Eugene Eclair v6 custom rom with lag fix

First of all, there's no such thing as semi brick, there's brick or not. Try installing your Rom again..

Dan0zone don't be rude man,.backup your apps, enter recovery more delete all user data, if after that you have the same problem restore, or keep trying to enter download mode, try different methods
Sent from my SGH-T959 using XDA App

iwillkillyou said:
Dan0zone don't be rude man,.backup your apps, enter recovery more delete all user data, if after that you have the same problem restore, or keep trying to enter download mode, try different methods
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
dude, he cant back up if he cant access the homescreen. neither can he use rom manager..
cant use the hardware buttons to get into dl or recovery either... read op guys...
2010ngojo said:
[Q] Need help with semi/soft brick!
So my Vibrant has been turning off randomly. I think its because of the loose battery or maybe it's just over-heating. But a few days ago, after turning it on there is only a black screen and lit capacitive buttons at the bottom.
It boots up normal, with the vibrant name, t-mobile animation, and the Galaxy S boot animation, then black screen! This started to happen after a few reboots, and now it won't rebbot properly, just black screen. It seems like I have to restore my phone, but the problem is I cannot get the phone into recovery or download mode! Please advise.
Samsung Vibrant, Eugene Eclair v6 custom rom with lag fix
Click to expand...
Click to collapse
Do this bro... just tested it myself, works fine...
get adb installed on your computer, should already have it if your rooting but if not get it, youll find it in the stickied thread for informative links in the development section.
get a cmd prompt open on your computer and type in
>adb devices
let it start up deamon and it will tell you device not found, its ok.
now type and have ready...
>adb reboot recovery (do NOT press enter yet)
start your phone like normal. before its even finished with the boot up tmobile animation and the galaxy s (but after the plain vibrant text/picture) logo press enter. if it says error: device not found then wait all the way till galaxy s only you did it too early...
screen will go black and reboot into standard recovery... hope to goodness you had a working clockwork recovery installed and nandroid ready for this next part...
go down using your volume keys and select reinstall packages using the power key
now in clockwork recovery go down to nandroid
now go to restore
go to your earliest back up and restore it.
there you go.
I would start fresh get odin set up and reinstall the original rom at this point as something may still be corrupted, reroot, install latest clockworkmod, latest vibrant 9 rom (im using and see no bugs and runs better then the vibrant 6 rom i had) and DONT install the lag fix until the newest "TRUE" lag fix comes out with the new file system and kernel that JAC is working on and has almost ready.
good luck and pm me if any of these steps need further explanation.

Pypanys thanks for that post, I learn something new but he said its bootsup normally, but it goes to a black screen after the boot logo he can enter recovery mode, same thing happen to me. I was opening maps and it crashed, it frooze the phone, to I restarted the phone and enter recovery amd deleted user apps, and it did the fix,
Sent from my SGH-T959 using XDA App

iwillkillyou said:
Dan0zone don't be rude man,.backup your apps, enter recovery more delete all user data, if after that you have the same problem restore, or keep trying to enter download mode, try different methods
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
iwillkillyou said:
Pypanys thanks for that post, I learn something new but he said its bootsup normally, but it goes to a black screen after the boot logo he can enter recovery mode, same thing happen to me. I was opening maps and it crashed, it frooze the phone, to I restarted the phone and enter recovery amd deleted user apps, and it did the fix,
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
hes just stated man that he cant even get into recovery, my guess is hes locked out using the volume up/down keys like many new phones are (which btw is a known defect, spend 10min on the phone with tmobile doing thier trouble shooting to show them it doesnt work and they send you a replacement..) sooooo I gave him a way to get into recovery without the buttons and not having to wait till he gets to a black screen where possibly its frozen and he cant use adb commands.
I was just making mention to you also that he cant even back stuff up NOW (hopefully he already archived all his apps and data) and hes better off starting fresh since hes getting problems using his current rom/lagfix....

Thanks for the quick reply p()()pypants, but i will have to try your method later. It's late and I have class (college) tomorrow, but i will post my results soon. Thank you again.
Edit 1:
Btw, is there a way to back up my current rom? Like the way rom manager back up roms? I know my current rom works before so that's why I want to back it up.
Edit 2:
Actually i did not use adb to root my phone, just used the one click method. So can you please give me more detailed instructions on how to install/use adb?

Okay, I typed in "adb reboot recovery" and press enter as my phone booted up during the t-mobile animation and at the Galaxy S boot animation. Neither time work. Then I reentered it again after the black screen. That did not work either. CMD keeps on returning "error: device not found" and the phone stays on with the black screen.

2010ngojo said:
Okay, I typed in "adb reboot recovery" and press enter as my phone booted up during the t-mobile animation and at the Galaxy S boot animation. Neither time work. Then I reentered it again after the black screen. That did not work either. CMD keeps on returning "error: device not found" and the phone stays on with the black screen.
Click to expand...
Click to collapse
Do you have the right drivers installed? You can check here: http://forum.xda-developers.com/showthread.php?t=728929
Another very stupid question, just to cover all bases - your phone is plugged into the computer, correct? When you install the new drivers, try plugging the phone into a different USB port on the computer than you've been using, so it will hopefully pick up the new drivers without much extra effort.
If that doesn't help, just keep trying the command while the phone boots up. Maybe you'll get lucky and it will work. Sorry I don't have any real solution for you :\

I'm fairly sure I have the right drivers, otherwise I wouldn't be able to root in the first place. Yes, the phone is plugged in also. I'll try a different USB port and see what happens...
Update: Trying different USB ports does not help.

[Q] Nexus 7 Boot Loop and no Recovery

Hello,
i need some help.
my nexus 7 is in a boot loop.
please look at youtube
youtube . com/watch?v=z-JbPdhr_1Q&feature=plcp
thanks from germany

verysalty said:
Hello,
i need some help.
my nexus 7 is in a boot loop.
please look at youtube
youtube . com/watch?v=z-JbPdhr_1Q&feature=plcp
thanks from germany
Click to expand...
Click to collapse
Unplug your device. Hold the power button until it turns off. Then hold volume up, volume down, and the power button. It should boot you into recovery.
Sent from my SAMSUNG-SGH-I747 using xda premium

I'm sure there are more ways to deal with this, but I personally would just flash a custom recovery from bootloader and re flash the rom. Probably the easiest way to go about it. Others may have a better idea.
Sent from my Nexus 7 using xda app-developers app

NuttyLemonz said:
I'm sure there are more ways to deal with this, but I personally would just flash a custom recovery from bootloader and re flash the rom. Probably the easiest way to go about it. Others may have a better idea.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
+1 to that

verysalty said:
Hello,
i need some help.
my nexus 7 is in a boot loop.
please look at youtube
youtube . com/watch?v=z-JbPdhr_1Q&feature=plcp
thanks from germany
Click to expand...
Click to collapse
What did you do before? If you flashed a new ROM / Kernel, most likely they are not compatible.

AndDiSa said:
What did you do before? If you flashed a new ROM / Kernel, most likely they are not compatible.
Click to expand...
Click to collapse
nothing.
i was exporting some data from my dropbox to my nexus. after that i lost my icons and had a empty desktop without icons.
after reboot, i was in the loop
my nexus is a stock nexus with 4.1.2 no root.
i will not loose my data

You may have no choice but to flash my friend. Sounds like you had an unlucky gremlin.
+2 to Lemonz post.
Sent from my GT-I9100 using xda app-developers app

NuttyLemonz said:
I'm sure there are more ways to deal with this, but I personally would just flash a custom recovery from bootloader and re flash the rom. Probably the easiest way to go about it. Others may have a better idea.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
... but if it's still locked, you need to unlock and then you will loose all your data
@verysalty: Did you try already to access the system with adb? Do you have debugging option switched on? Then you could try to do a backup of all your data before.

AndDiSa said:
... but if it's still locked, you need to unlock and then you will loose all your data
@verysalty: Did you try already to access the system with adb? Do you have debugging option switched on? Then you could try to do a backup of all your data before.
Click to expand...
Click to collapse
Sorry, no debungging mod on...
How can i flash my nexus to stock. easy way please.

The easiest way in my opinion:
- unlock boot loader (you will loose all your data!)
- download factory image from Google
- flash the factory image (fastboot or adb)
I am wondering why synchronizing some files with dropbox is causing a boot loop ???
Sent from my Nexus 7 using xda app-developers app

AndDiSa said:
The easiest way in my opinion:
- unlock boot loader (you will loose all your data!)
- download factory image from Google
- flash the factory image (fastboot or adb)
I am wondering why synchronizing some files with dropbox is causing a boot loop ???
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
My Nexus 7 is alife
i have use the nexus 7 toolkit and unlock the boot loader > flash the factory image > lock the boot loader...
1000x thanks for all you help
verysalty from Hamburg, Germany

Had a very similar issue today
Nexus started rebooting in the middle of different apps 2-3 times last night.
charged it overnight, unplugged it and went to class.
Then progressed to rebooting after only 40 seconds after the lock screen loaded from the reboot
40 secs wasn't enough time to do anything in android so after much research this is how I fixed it:
- in the 40 secs that android worked I pressed and held the power button and powered it down to stop the boot loop.
- when it was finally shut down I pressed and held the power and vol dwn buttons til the recovery menu appeared.
- used the vol buttons to select recovery, then pressed power
- When the android with the red exclamation point (!) showed up I pressed power then vol up and released for the menu to appear.
- Selected and execute Factory Reset. Then wipe Cache. then reboot, fixed the problem so far, now I'm re-installing apps.
I talked with a google rep about the problem, said it could me anything from a poorly written app, to a corrupted boot sequence.
Anyone know what may have caused this, so I don't inadvertently cause it to happen again??
-----------------------------------------------
Nook Tablet --> Nexus 7
HTC HD2 --> Razr Maxx

eodelf said:
Had a very similar issue today
Nexus started rebooting in the middle of different apps 2-3 times last night.
charged it overnight, unplugged it and went to class.
Then progressed to rebooting after only 40 seconds after the lock screen loaded from the reboot
40 secs wasn't enough time to do anything in android so after much research this is how I fixed it:
- in the 40 secs that android worked I pressed and held the power button and powered it down to stop the boot loop.
- when it was finally shut down I pressed and held the power and vol dwn buttons til the recovery menu appeared.
- used the vol buttons to select recovery, then pressed power
- When the android with the red exclamation point (!) showed up I pressed power then vol up and released for the menu to appear.
- Selected and execute Factory Reset. Then wipe Cache. then reboot, fixed the problem so far, now I'm re-installing apps.
I talked with a google rep about the problem, said it could me anything from a poorly written app, to a corrupted boot sequence.
Anyone know what may have caused this, so I don't inadvertently cause it to happen again??
-----------------------------------------------
Nook Tablet --> Nexus 7
HTC HD2 --> Razr Maxx
Click to expand...
Click to collapse
I had the exact same issue from your description, I solved it after I read someone else disconnected the battery. Its a pretty quick fix to what looks like an unrecoverable problem loop of switching on, then powering down.
Here's what I did:
Open the back using just my nail on one corner , it snaps off easy pesy, trust me
Use ifixit nexus 7 battery replacement guide , steps 1-6 only, note where they use a tool I used a pair of nail scissors to prise the connector out and back in
http://www.ifixit.com/Guide/Installing+Nexus+7+Battery/9895/1
Pulling the battery out, as with any android device can work.
Total time 2 mins
It was working again before I put the back cover on.

[Q] Phone boots, works, but has no recovery

I have a bit of a situation, I have the AT&T Galaxy s4, and I able to boot into it properly, it's running the Goldeneye ROM, all my apps are working, and I don't have the triangle, or the padlock custom logo. In other words my phone is working great, except for one thing. I ran triangle away, which I am beginning to think was a mistake, and ever since then, while the phone itself works great, I am absolutely unable to get into recovery mode at all. The phone acts like it's going to go into recovery, then boots normally. This would not be particularly bothersome, except I would like to be able to back up my phone in the event of something happening with it, which has happened once before. I've searched the forums, and everything I have come up with has solutions for a phone that is bricked, or otherwise won't boot, which does not apply to me. My phone works, and works well, I just want to be able to back the darn thing up, and have a recovery in case of emergency, or worse, I get bored and want to change roms.

dsly4425 said:
I have a bit of a situation, I have the AT&T Galaxy s4, and I able to boot into it properly, it's running the Goldeneye ROM, all my apps are working, and I don't have the triangle, or the padlock custom logo. In other words my phone is working great, except for one thing. I ran triangle away, which I am beginning to think was a mistake, and ever since then, while the phone itself works great, I am absolutely unable to get into recovery mode at all. The phone acts like it's going to go into recovery, then boots normally. This would not be particularly bothersome, except I would like to be able to back up my phone in the event of something happening with it, which has happened once before. I've searched the forums, and everything I have come up with has solutions for a phone that is bricked, or otherwise won't boot, which does not apply to me. My phone works, and works well, I just want to be able to back the darn thing up, and have a recovery in case of emergency, or worse, I get bored and want to change roms.
Click to expand...
Click to collapse
Why don't you just download goomanager and install TWRP open script, or ROM manager and install clock work recovery?
When going into recovery (volume up+home+power) continue to hold the volume up+home once you feel the phone vibrate. If you hold the power to long it'll just cause it to boot normally. Make sure you're not holding power too long lol.
Sent from my SGH-I337 using XDA Premium 4 mobile app

I tried ROM manager (I actually have to pro version, I purchased it a couple phones back) and it was showing that TWRP AND Clockwork were installed on the phone, but the phone will not boot into either. It shows the galaxy s4 logo, blue print that says recovery booting, then boots normally, Goldeneye rom has a boot to recovery option, the same thing happens, I even downloaded a boot to recovery app and ran that, same thing. It's like the recovery is there, but just will not open.
Br4nd3n said:
Why don't you just download goomanager and install TWRP open script, or ROM manager and install clock work recovery?
When going into recovery (volume up+home+power) continue to hold the volume up+home once you feel the phone vibrate. If you hold the power to long it'll just cause it to boot normally. Make sure you're not holding power too long lol.
Sent from my SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse

dsly4425 said:
I tried ROM manager (I actually have to pro version, I purchased it a couple phones back) and it was showing that TWRP AND Clockwork were installed on the phone, but the phone will not boot into either. It shows the galaxy s4 logo, blue print that says recovery booting, then boots normally, Goldeneye rom has a boot to recovery option, the same thing happens, I even downloaded a boot to recovery app and ran that, same thing. It's like the recovery is there, but just will not open.
Click to expand...
Click to collapse
How about "dd"method using terminal emulator. I do understand it uses the same partition but give it a shot.
sent from a I337 MF3 S4

If ADB Terminal emulator doesn't work than I'm assuming somehow your recovery partition is broke. You may need to flash back to the stock amdl firmware through Odin.
Sent from my SGH-I337 using XDA Premium 4 mobile app

jball said:
How about "dd"method using terminal emulator. I do understand it uses the same partition but give it a shot.
sent from a I337 MF3 S4
Click to expand...
Click to collapse
I am going to be honest, as i've never had an issue remotely like this before, I am completely unfamiliar with what the "dd" method in terminal emulator is. I am more than willing to look it up, but honestly I am not even sure what parameters I would use to search that.

dsly4425 said:
I am going to be honest, as i've never had an issue remotely like this before, I am completely unfamiliar with what the "dd" method in terminal emulator is. I am more than willing to look it up, but honestly I am not even sure what parameters I would use to search that.
Click to expand...
Click to collapse
It's hidden in here http://forum.xda-developers.com/showthread.php?p=46798778

[Q] HELP!! 4.4 update

i tried to update to 4.4 through factory image files and i wounded up getting stuck on the nexus symbol and it wont boot up!!
i tried then going to recover mode but its not even doing that! the furthest i can get is into fastboot mode and when i go to recovery mode theres just the red triangle with no menu at all.. just the picture with the red triangle.. all i can do from there is hard reboot
so the situation is..boot stuck and no recovery
thanks for the help!

Well you should be fine. The little red triangle is normal, it is the screen you get before it goes to stock recovery. If you were to google that, you'd see you need to depress the power button and the volume up buttons at the same time. You keep them pressed together for about 4-5 seconds before it goes into recovery. Once you do that do a factory reset and see if that works.
BTW when you post like this make sure you include a little more detail how you got to where you are. Like what operating system you are using, Windows _, Ubuntu __._, or IOS. Also if you were using a tool kit. If you have ADB and Fastboot installed, etc., helps w/ the diagnosis if you know what I mean.

jawmail said:
Well you should be fine. The little red triangle is normal, it is the screen you get before it goes to stock recovery. If you were to google that, you'd see you need to depress the power button and the volume up buttons at the same time. You keep them pressed together for about 4-5 seconds before it goes into recovery. Once you do that do a factory reset and see if that works.
BTW when you post like this make sure you include a little more detail how you got to where you are. Like what operating system you are using, Windows _, Ubuntu __._, or IOS. Also if you were using a tool kit. If you have ADB and Fastboot installed, etc., helps w/ the diagnosis if you know what I mean.
Click to expand...
Click to collapse
i know what stock recovery mode is and how to get to it.. its just that it doesnt show up .. just the picture with no options
anyways.. i figured out how to flash stock recovery from fastboot mode but every stock i try to flash i keep getting a bootloop!

namnam123 said:
i know what stock recovery mode is and how to get to it.. its just that it doesnt show up .. just the picture with no options
anyways.. i figured out how to flash stock recovery from fastboot mode but every stock i try to flash i keep getting a bootloop!
Click to expand...
Click to collapse
Maybe your factory image is corrupted. I downloaded the factory image from Google, checked the MD5 to make sure it was right, and then flashed it with no problem.

wipe data / factory reset on STOCK recovery.

https://www.youtube.com/watch?v=kFqZ7z4ZeLY&feature=youtube_gdata_player
Sent from my Nexus 4 using xda app-developers app

i had the same problem.. n then i found the solution by flashing it through toolkit follow here i made a video
http://forum.xda-developers.com/showthread.php?t=2531374
Sent from my Nexus 4 using xda app-developers app

Locking and then unlocking the boot loader has worked for several including myself
Sent from my Nexus 4 using XDA Premium 4 mobile app

[Q] tried to install xposed on 4.3 and now stuck on bootloop

so this morning I tried to install xposed on PacMan 4.3. I installed it and it said to do a soft reboot.
after the soft reboot i am now stuck on the PacMan boot graphic.
I can't get into recovery any which way.
I have tried the power down to get into recovery and it just reboots.
I am now in download mode connected to my computer but want to know what to do get back into the ROM and if its possible to do a nandroid so I don't lose my texts/phone logs/app data.

You may be forced to go back to stock and start from scratch. If recovery isn't working then you can't really do much to fix the issue. What's the model?

ceredics said:
You may be forced to go back to stock and start from scratch. If recovery isn't working then you can't really do much to fix the issue. What's the model?
Click to expand...
Click to collapse
vs980
anyway to get into recovery via abd to backup info?
also why would xposed mess with recovery?

Getting into recovery will leave you with what options since your bootlooping? Wiping for a fresh install or trying to reboot for a another vicious cycle? Either way your going to lose texts app data and phone logs. Unless you have a backup your hiding from me? Lol

To get into recover
Try holding volume down + power*
Immediately when LG appears let go of both and ONLY hold onto power, should boot into option to factory reset*
Hit power button 3 times to continue, then itll load into recovery
Sent from my LG-VS980 using xda app-developers app

I got stuck in a bootloop last week as well and had to do a factory reset (on my Moto X). Good reminder to move my backups to my computer...
There was just an update (2.4.1) to the Xposed installer that says it "Fixed a bootloop which mainly occured on some x86 ROMs," so hopefully that fixes it.