Database Users

Won't boot into recovery

Got a replacement Vibrant today and it will not boot into recovery with vol up/dwn/power buttons, any ideas? I booted my first Vibrant daily into recovery, this one won't do it.

Have you tried Quick Boot in the market?

SugarMouth said:
Got a replacement Vibrant today and it will not boot into recovery with vol up/dwn/power buttons, any ideas? I booted my first Vibrant daily into recovery, this one won't do it.
Click to expand...
Click to collapse
The thing with these Vibrants is that some of them have that problem where the phone doesn't register that your pushing the volume buttons at boot up...only the power button, which is why it just turns on and nothing else. This is a known issue that was found out by another canadian phone company(Bell)
I just bought a Vibrant and I could not boot into recovery from day one...after a week I took it back 'today' and got a replacement and now it works. I guess me and you were the unlucky ones.
If you really want it to work I would take it back somehow because this isn't fixable, its a hardware issue on boot.
-By the way, you can still boot to recovery from adb or rom manager, anything like that, just not physically. The down side of this is that if your in a boot loop and your computer doesn't recognize your phone your screwed. It also doesn't recognize Download Mode either to restore.
Hope it works out for you.

Wow so I'm screwed? Hard to call up T-Mobile and say "hey my phone won't boot into recovery, I need to switch it."

s15274n said:
Have you tried Quick Boot in the market?
Click to expand...
Click to collapse
I need root for that and I can't boot into recovery to get root.

SugarMouth said:
Wow so I'm screwed? Hard to call up T-Mobile and say "hey my phone won't boot into recovery, I need to switch it."
Click to expand...
Click to collapse
Actually thats exactly what I did...I told them I like to have control over my phone and that I use the recovery to "clean up" my phone every month or so and I like to use the recovery to do it. I also told them in the past i've used the recovery to install OTA updates that simply did not want to install over the air, so I would download it myself and install manually. The T-mo rep didn't seem to care.

So why not root this way then, and use quick boot once you have root
http://forum.xda-developers.com/showthread.php?t=739300

s15274n said:
So why not root this way then, and use quick boot once you have root
http://forum.xda-developers.com/showthread.php?t=739300
Click to expand...
Click to collapse
Exactly...do that. Like I said in my first post, you can still do everything thru Quickboot, Rom Manager, etc and ADB. You just won't be able to get to recovery that way if your phone won't boot or is stuck in a boot loop..that would suck.

As I mentioned in your other thead on this subject, I have the same problem with a brand-new Vibrant, and I don't want to root it yet. Only way I was able to get into clockwork recovery was via 'adb reboot recovery' method. Once I'd done that, I was able to install and run wirelessap tethering without rooting, infrastructure mode and all. Still not rooted, but I never did get my intended 'factory-fresh' nandroid backup, I gave up and popped in my SIM and installed a few things before I got adb talking to the phone. (running adb on ubuntu box, hadda kill and restart server as root to fix permissions issue)
j

I got my replacement vibrant, after bricking the first one, and I can confirm that I am not able to boot into recovery by holding the volume buttons. I hope samsung hasn't changed something...
But thankfully I was able to finally get into recovery using ADB...

[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.

Can't boot nexus one or use recovery

Hello,
I come here and make a new thread after I spent the day inside various forums to solve my problem but wasn't able to.
Here is the thing I tried to install the cyanogenmod earlier today. I unlocked my N1 properly and think I rooted it properly as well. But I was unable to install the custom rom. Actually my N1 won't even boot, it's stuck on the cross image with the unlocked lock and I can't boot the recovery either. I tried to install a custom recovery, the amon ra thing, but it still freezes on the cross screen.
I assume my N1 isn't completely bricked since I can still power it up, start the fastboot mode and my computer recognize de USB connection (however ADB won't find the phone even after I re-installed the drivers).
So here I come for help to either bring back my N1 to its former stock rom or any functionning rom.
Thanks.

Try the unroot/restore guide with PASSIMG of FRG33. Look at my signature.

oh thank you !!! It worked perfectly !
EDIT : Well spoke too soon I rebooted the N1 after its apparent recover and it froze again, so I started the operation once more and while updating the files ravio_v2 was checked "fail-pu" instead of "ok"
EDIT 2 : Well I rebooted after the update and the N1 never powered up again ... I guess now it is really bricked... though I can't figure why

olicyr said:
EDIT 2 : Well I rebooted after the update and the N1 never powered up again ... I guess now it is really bricked... though I can't figure why
Click to expand...
Click to collapse
You can't even get into fastboot any more?
Also, you say you followed the right steps to unlock the device and the right steps to root the device... What steps did you take exactly?

Hi,
to unlock the phone I used the oem command in the fastboot mode. Then I tried to install the amon ra custom recovery and I think that is what brought all this trouble.

Can you still see your device through fastboot? If so you should be able to flash a recovery image and a ROM of your choosing.

It should boot up fastboot like Dirk said. You can not brick the phone by flashing a recovery.
Sent from my Nexus One using XDA App

I guess there is some HW fault - might be a recent bad sector in one of the system critical areas. It's not something you can cause with SW - unless you're flashing hboot or radio, which should have been covered in the first restore attempt, which worked.
Anyway, if it doesn't power up at all - and doesn't react to charging - try pulling out the battery for several hours, and then put it back and try again. If it doesn't work - then you're up for a warranty repair...

DirkGently1 said:
Can you still see your device through fastboot? If so you should be able to flash a recovery image and a ROM of your choosing.
Click to expand...
Click to collapse
No the phone doesn't boot anything. I'll try to remove the battery and wait a few hours like said above, if it doesn't work I'm still under warranty I think

[Q] My MT4G has bootloop, and adb says device offline. I will thank who can hlp

I have a MT4G with S-0ff. I dont know how it happened but I got it all messed up. I can get to the engineering menu then select recovery. But thats about it ( which I see a phone with warning sign in red) and when I run the command "adb devices" in adb/tools It says"error:device offline". I have tried everything even changing different usb ports. ( I have many roms and clockworkmod3.005 and 2.0 ,, version available)
Can someone help me please, I will thank you (will give thanks)
Good bless you.

ilkercatal said:
I have a MT4G with S-0ff. I dont know how it happened but I got it all messed up. I can get to the engineering menu then select recovery. But thats about it ( which I see a phone with warning sign in red) and when I run the command "adb devices" in adb/tools It says"error:device offline". I have tried everything even changing different usb ports. ( I have many roms and clockworkmod3.005 and 2.0 ,, version available)
Can someone help me please, I will thank you (will give thanks)
Good bless you.
Click to expand...
Click to collapse
What did you do before this, when phone was in working condition?

I dont know
Phone simply does not go into recovery. When I go into engineering menu then click recovery phone just freeze with my touch 4g logo on it.

ilkercatal said:
Phone simply does not go into recovery. When I go into engineering menu then click recovery phone just freeze with my touch 4g logo on it.
Click to expand...
Click to collapse
do you have the engineering hBoot or the stock hBoot? Can you boot into a fully working ROM?

it happened to mine as well...did you flash a new kernel on it....sometimes on a rom if you flash a new kernel to lets say overclock your phone or some sort it goes into a BootLoop where the Mytouch boot screen keeps rebooting but does not go into any rom...if you can get to recovery wipe cache and try to reboot..if you cant get to recovery try getting to it through the normal Hboot (volume down +power key)..hope it helps

ilkercatal said:
Phone simply does not go into recovery. When I go into engineering menu then click recovery phone just freeze with my touch 4g logo on it.
Click to expand...
Click to collapse
If you can boot completely, install ROM Manager and flash a recovery with it. If you can't boot, then you can flash a recovery using the fastboot tool from the Android SDK, but only if you have the engineering bootloader (0.85.2007)

neidlinger said:
do you have the engineering hBoot or the stock hBoot? Can you boot into a fully working ROM?
Click to expand...
Click to collapse
I see only stock bot. ( turning phone on while holding vol- down rocker button)

i only see stock menu

When adb said my device was offline I just typed in (While it was connected)
Code:
adb kill-server
adb start-server
any my device was online.

Are there anyone who knows what they are talking about? Or, most people just say things to be busy or something. Come on people if you dont know how, why waste your time

did you find anything that helped? My phone keeps restarting as well.. i even updated cmw and used cm7 rom.... still keeps restarting... it happened after i used the royal senseless rom..

myk0 said:
did you find anything that helped? My phone keeps restarting as well.. i even updated cmw and used cm7 rom.... still keeps restarting... it happened after i used the royal senseless rom..
Click to expand...
Click to collapse
did you do a complete wipe prior to flashing the your newest rom?

neidlinger said:
did you do a complete wipe prior to flashing the your newest rom?
Click to expand...
Click to collapse
yea.. wiped and formatted everything

i have a similar issue im trying to reboot my phone with adb. it is telling me that my adb is out of date the daemon starts but it tells me my device cant be found any ideas? and would an outdated adb be the reasson i cant find my device?

uroboch said:
i have a similar issue im trying to reboot my phone with adb. it is telling me that my adb is out of date the daemon starts but it tells me my device cant be found any ideas? and would an outdated adb be the reasson i cant find my device?
Click to expand...
Click to collapse
Install the usb driver for the glacier and reboot your computer
Sent from my GT-P3113 using xda app-developers app

Flashed a D802 on my VS980 Verizon G2

Alright like a idiot I downloaded a international rom and didn't pay attention...flashed in TWRP and went to reboot so it obviously doesn't work. Tried to use the Flashtool to revert back to the stock Verizon software and it throws the error of the Device Model is different. IMEI is right, BIN, DLL, SWV, SWOV all show the VS980 since I'm trying to flash that.
So have I killed it completely or is there a way to recover? Sure hope there is
I can get into the download mode still

Also appears that it boots into fastboot and can send fastboot commands via the command prompt

Wow this dropped quick...just putting this to the top so I can hopefully get it up and running quicker.

Please check the same thread about LG repair cost. It looks like you need to repair it. you have mismatch in model name in build.prop, so there is no solution as for now. http://forum.xda-developers.com/showthread.php?t=2506208

Ya I saw that after this morning...was hoping it wouldn't come to that. Mine says rooted on the download screen so hopefully that doesn't cause a issue when I send it in.

have you tried pushing a .img using fastboot, as you seem to be able to get to it?

aliaksei said:
have you tried pushing a .img using fastboot, as you seem to be able to get to it?
Click to expand...
Click to collapse
Nope as I'm not exactly sure which one I didn't want to attempt anything and break it further
If you could point me to the right one I would appreciate it

collins521 said:
Nope as I'm not exactly sure which one I didn't want to attempt anything and break it further
If you could point me to the right one I would appreciate it
Click to expand...
Click to collapse
Hey man are you able to access recovery at all by holding down Vol down+Power, releasing it when the LG splash screen appears for a sec, and then immediately pressing it again? I saw someone a day or two ago was able to put a ROM on a flash drive and install it from there in TWRP.

Mine actually seems to be booting into fastboot when I hold down the power button and it reboots. I can't get it to turn off completely, I can get into download mode if I hold down volume up and power if it's plugged into the computer. If I hold down the power button it will reboot and seems to be in some sort of fastboot when it tries to power on

collins521 said:
Nope as I'm not exactly sure which one I didn't want to attempt anything and break it further
If you could point me to the right one I would appreciate it
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1752270

aliaksei said:
http://forum.xda-developers.com/showthread.php?t=1752270
Click to expand...
Click to collapse
Makes sense and should be easy enough except that thread makes it out that the boot.img really wouldn't change the device model. Unless it contains it in the img file
Which .img file would I be pushing? The boot.img?

I guess it would be more like which one? Would I be able to just used the one from say CleanRom?

Wohoo! Finally got it up and going...thought for sure it was toast.
I flashed the boot.img through fastboot and then was getting "secure boot unsuccessful" on the screen when it tried to boot. Kept trying to get it into the recovery and it finally did so when it went to the splash screen about pressing the power it put me into TWRP.
I tried to restore the backup that I had stored and it started to but then turned off, I'm not sure if it was because the battery was so low or if it was just the jacked up file structure but it wouldn't get any father than the LG splash screen. The LED would flash green then blue and it would just sit there.
That was when I thought for sure it was toast, let it sit and charge for awhile and still couldn't get back into the recovery but was able to get into download mode. Flashed the stock software via LG Tools and it finally booted.
Not sure if anyone else will run into this issue but now it's documented lol

help a bro
collins521 said:
Wohoo! Finally got it up and going...thought for sure it was toast.
I flashed the boot.img through fastboot and then was getting "secure boot unsuccessful" on the screen when it tried to boot. Kept trying to get it into the recovery and it finally did so when it went to the splash screen about pressing the power it put me into TWRP.
I tried to restore the backup that I had stored and it started to but then turned off, I'm not sure if it was because the battery was so low or if it was just the jacked up file structure but it wouldn't get any father than the LG splash screen. The LED would flash green then blue and it would just sit there.
That was when I thought for sure it was toast, let it sit and charge for awhile and still couldn't get back into the recovery but was able to get into download mode. Flashed the stock software via LG Tools and it finally booted.
Not sure if anyone else will run into this issue but now it's documented lol
Click to expand...
Click to collapse
i did the same thing as you i loaded a d802 rom on my vs980 can you tell me how to load the boot .img so i can do what you did i didnt buy a warranty cause i figured i didnt need it so i have no alternative way of fixing it

Had to push the boot.img through adb

collins521 said:
Had to push the boot.img through adb
Click to expand...
Click to collapse
What's the command input for the push
All I know is its the along the line of push/c:/(boot.img location)

It's more like "fastboot flash boot boot.img" you can't push it via adb, unless you're already in TWRP.

NRGZ28 said:
It's more like "fastboot flash boot boot.img" you can't push it via adb, unless you're already in TWRP.
Click to expand...
Click to collapse
I have twrp installed but I can't boot to it I get stuck on the [800] fastboot mode started screen can I do it from download mode