Can't boot into recovery - Vibrant Q&A, Help & Troubleshooting

Just received a replacement Vibrant and can not boot into recovery through the power/volume up/down method, has something changed?

To get into recovery mode you need to hold Volume Down and Power Button.

I have booted into recovery many times with my original Vibrant, my replacement will not boot.

Um, the OP explicitly said that they can't get into recovery with volup+voldn+power, on a replacement phone. Replacement=more likely they know how to do it that I do, but I just received a new Vibrant from T-Mo-USA today and I cannot get it into recovery either.
VolUp+VolDn held, power until 'vibrant samsung' then release power is supposed to be recovery, but not working for me. Just VolDn or just VolUp and power only boots the phone as well. Waiting with power held until screen goes black again then 'vibrant samsung' returns is also ineffective. I can get to download mode with vol buts while plugging USB, and I've double-checked that both vol buts are working. It /is/ possible that a change took place and recovery is no longer accessible through that key combo...
Shiny new handset, never yet had a SIM inserted. (Trying to get clockwork recovery running to do nandroid backup before setting up first time) (adb gives me a permission error, going to research that now)
j

Quick Boot in the market.
I am NOT a fan of the new q&a section. I liked going to one place.

s15274n said:
I am NOT a fan of the new q&a section. I liked going to one place.
Click to expand...
Click to collapse
Agreed. Wait, is this s15274n. I love Q&A.

haha guess you saw you were in the sticky now

newkirk said:
Um, the OP explicitly said that they can't get into recovery with volup+voldn+power, on a replacement phone. Replacement=more likely they know how to do it that I do, but I just received a new Vibrant from T-Mo-USA today and I cannot get it into recovery either.
VolUp+VolDn held, power until 'vibrant samsung' then release power is supposed to be recovery, but not working for me. Just VolDn or just VolUp and power only boots the phone as well. Waiting with power held until screen goes black again then 'vibrant samsung' returns is also ineffective. I can get to download mode with vol buts while plugging USB, and I've double-checked that both vol buts are working. It /is/ possible that a change took place and recovery is no longer accessible through that key combo...
Shiny new handset, never yet had a SIM inserted. (Trying to get clockwork recovery running to do nandroid backup before setting up first time) (adb gives me a permission error, going to research that now)
j
Click to expand...
Click to collapse
Let us know if you find a resolution, thanks!

s15274n said:
Quick Boot in the market.
I am NOT a fan of the new q&a section. I liked going to one place.
Click to expand...
Click to collapse
Quick Boot specifically states that you must ALREADY have root status for it to work.
So we need Root for Quick Boot to get into Recovery Mode, but we need to first get into Recovery Mode to get Root...
Ring around the rosy...
Anybody else have any ideas?

^ he didn't say he didn't have root already. I also posted an alternate method to root above without stock recovery.

Have either of you found a way to recovery with key combos yet. I too can not get recovery with vol buttons. Only thru terminal, adb, rom manager, etc. i'd really like to know if anyones found a solution to this??? I'd like to be able to boot recovery manually in case I cant boot into home screen for some reason.

Someone mentioned getting it to work while having it plugged into the charger.
Frankly, the only way I was able to get into Recovery Mode was through the ADB method.
Sent from my SGH-T959 using XDA App

I called T-Mobile regarding this and they agree it should work with hardware buttons and are sending me a replacement.

Same issue. Got the phone on Aug 23 and the only way I can go to recovery is via ADB and ClockWorkMod

Hmmm, I have the same issue. The funny thing is that I can get into recovery on my girl's phone just fine. And I can't on mine. They only way I could get into recovery was by using the 1-click root. Now, I can use ROM Manager to get into recovery while "on-the-go". At first, I was honestly afraid that maybe my phone came without the recovery installed!
I know it gets frustrating listening to the stupid T-Mobile jingle taunting you every time it fails.
I guess it's not a big enough deal to me to send it back now that I have a couple of options, but it seems like it's a more common issue than I thought. Only way to get Samsung to do something is to keep sending them back . . .

Its important to be able to get recovery with the buttons tho. What if your flashing roms or anythimg for that matter and the phone wont boot regularly. Then you cant get into recovery to restore. Called tmobile and Im sending mine back tomorrow for replacement, unless somebody knows another way to get into recovery if you end up in a boot loop???

My friend just got his Vibrant, I went to root it for him and wont go into recovery. Mine works fine,I can get into recovery fine on mine everytime. I told him to return it and swap it out. Getting into recovery is very important if you flash a rom and you run into booting issues.

roguespy0 said:
My friend just got his Vibrant, I went to root it for him and wont go into recovery. Mine works fine,I can get into recovery fine on mine everytime. I told him to return it and swap it out. Getting into recovery is very important if you flash a rom and you run into booting issues.
Click to expand...
Click to collapse
I really suspect what we're seeing isn't a defect per se, but the result of a suit at t-mo being told that people are using recovery mode for rooting their phones and restoring things like wifi tethering, who responded "then disable recovery mode dammit"...
If you return a Vibrant that won't go into recovery from buttons and actually get a new-in-the-box vibrant in its place, I suspect there's a very high probability that the replacement is the same, and if you get a replacement that WILL enter recovery from buttons I suspect it's likely to be an open box or what-have-you. For the latter, as more Vibrants are returned for not entering recovery, you're more and more likely to end up with a 'like-new' replacement that won't enter recovery either.
Long-term I suspect the solution is going to have to come from us, not t-mobile.
j

I can not boot into recovery this is also a replacement phone. I installed vibrant7 didn't care for it so did a rom manager recovery back to stock and my phone is stuck on the vibrant start screen. Can anyone help me fix my brick?

it doesn't work on my Vibrant,tried Volume Up/Power,Volume Down/Power, no luck....

Related

Vibrant won't boot into recovery?

I have tried everything. Holding volume up and power, down and power, both and power
Holding the whole time, letting go at the vibrant screen
I even did i factory reset and it wont work
Does anyone else have this issue?
It is going to ultimately force me to get a replacment device
I was wondering if there was somehing i missed
Sent from my SGH-T959 using XDA App
hold both volumes and power until you see the contact screen for the second time.
Sent from my SGH-T959 using XDA App
Same problem here. Spent a day trying to get it to work. Finally gave up and used the one click root method to get into recovery. This is my second Vibrant, so it's not that I haven't done this correctly before. Very strange, but one click worked for me.
Sent from my SGH-T959 using XDA App
The one click doesn't do anything
It puts the update.zip on my internal storage then doesn't reboot or anything
Would it still work through adb?
Sent from my SGH-T959 using XDA App
I've spent several hours trying to get into recovery and download mode via the buttons. I've tried everything I've found on the forums, and pretty much concluded that the US Vibrant is seeing the same issue that Bell Canada and Aus Optus is with some phones not having the power button reboot functional for whatever reason. I'm going to return mine tomorrow for one that works. Hopefully I don't get any static about trying them out till I find one that works properly.
ADB works fine for me to reboot to recovery and download. I personally would use TGA_Gunman's root.
Hey guys. I just bought a Vibrant today and am having this same issue. No matter how many times I hold either volume button independently (or even together), I can't get into Fastboot, or I guess Download mode as it's called here. I'm coming from a Nexus One where it works everytime, so this is kind of weird. Launching RomManager and selecting to boot into recovery does work, but I don't want to rely on that.
Is the smart thing to go swap the physical phone?
I am having the same problem with my Vibrant. Anyone figure out how to get it into recovery?
kas21 said:
I am having the same problem with my Vibrant. Anyone figure out how to get it into recovery?
Click to expand...
Click to collapse
As unpleasant as it may seem to do so, it really behooves you who are having those issues, (as am I with my 3rd replacement!!!) Vibrant, it is absolutely worth your while to set up ADB, for numerous reasons. It solves both of those issues and allows so many other options. Once you do the installation of the SDK on your PC and install the right drivers, it is not at all difficult to use it to do many important things much easier.
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
just download quick boot from the app store and u can reboot, recovery, or bootloader ur phone with this app
rdunn20 said:
just download quick boot from the app store and u can reboot, recovery, or bootloader ur phone with this app
Click to expand...
Click to collapse
he means boot rom and hes right just download it from app store and click install clockrecovery and after that click reboot in recovery and your done.
The problem with relying on adb, Quick Boot, and Rom Manager is what are you going to do when you flash and your phone won't boot? You won't be able to get into download or recovery mode and you'll be hosed. Take the phone back while you can and get one that works.
Exactly. I'm curious if there's a way around this though. What is it
that actually causes the phone to boot into recovery with the hardware keys and is it something that can be fixed/flashed?
I already exchanged once within the thirty days and I don't think the 30 days gets reset. Think I'm past the return period now.
Sent from my SGH-T959 using XDA App
shootr said:
The problem with relying on adb, Quick Boot, and Rom Manager is what are you going to do when you flash and your phone won't boot? You won't be able to get into download or recovery mode and you'll be hosed. Take the phone back while you can and get one that works.
Click to expand...
Click to collapse
I'm so glad you wrote that. This is exactly my feeling. In ideal solutions, ADB or even installing a terminal emulator onto the phone is great. But for any dev who dabbles with modifying their phone in any way, having access to recovery directly from the phone is an absolute must.
Im having the same problem but let me ask could it be because Avatar is in the sd card?...I keep reading (NOW) that the Root zip files should be copy to a SD without Avatar....
Gusgom said:
Im having the same problem but let me ask could it be because Avatar is in the sd card?...I keep reading (NOW) that the Root zip files should be copy to a SD without Avatar....
Click to expand...
Click to collapse
There are two "SD" cards, an internal and external. The external one is the on that the user can swap. It also contains the Avatar movie (if it is the one that came with the phone).
The update.zip file should be copied to the internal SD card. The one WITHOUT the Avatar movie.
I also cannot get my phone to boot into recovery using the buttons. I rooted using one-click.
It seems to be an issue with new/replacement Vibrants. I have a thread about it here: http://forum.xda-developers.com/showthread.php?t=764360
If anyone has a device like this and can pull a dump file from it and upload it, that would be fantastic! I'm not sure if this is a physical limiter or a software based one, but I'm pretty sure it's software based on experience and manufacture dates. Once we get a dump, I'm sure someone will be able to figure it out.
And to back what the others said, I was able to adb download no problem, but when the Odin flash hung, there was no way to get back in to download mode and I ended up having to exchange the phone. As soon as my next one gets here, I'll test and post a dump if someone else hasn't already.
johnny12times said:
And to back what the others said, I was able to adb download no problem, but when the Odin flash hung, there was no way to get back in to download mode and I ended up having to exchange the phone.
Click to expand...
Click to collapse
I had the same issue on a replacement Vibrant and this works for me to get into download mode (even after Odin hung and it looked 100% dead):
1. Removed SD and SIM card
2. Removed battery
3. plugged the phone into USB
4. held down vol-up and vol-down
5. popped the battery back in while holding vol buttons
dex1701 said:
I had the same issue on a replacement Vibrant and this works for me to get into download mode (even after Odin hung and it looked 100% dead):
1. Removed SD and SIM card
2. Removed battery
3. plugged the phone into USB
4. held down vol-up and vol-down
5. popped the battery back in while holding vol buttons
Click to expand...
Click to collapse
Excellent directions. Worked like a charm.
OMG! I seriously thought my Vibrant was trashed! Excellent directions for getting your Vibrant out of Boot loop and into Download mode:
1. pull everything out of phone (battery, SIM, SD card)
2. Plug in USB cable
3. Hold down both volume buttons
4. Insert battery while holding down volume buttons.
My phone went into Download mode easily at this point.
In my case, my phone got stuck in Boot loop while trying to use ROM Manager for a new ROM. Guess I used it wrong, I'll just stick with installing ROM's by way of Recovery mode. Anyway, my phone stayed in Download mode until I flashed it with ODIN. I just flashed it back to stock and started over. Here's the link:
http://forum.xda-developers.com/showthread.php?t=734475
I'm so glad I didn't have to exchange my phone, I feel bad for those that had to exchange thier phones, this is a nice workaround.
i try it went into downloading screen. Odin did not see my phone. What can i do now? Can anyone help.

[Q] Worthless Vibrant

Well, after spending almost 11 hours trying to boot into recovery or download, I know for sure that there is something going on with my phone re: hardware locked. The date on my box is 7-16. It is an early Vibrant. But no matter what I do, I cannot get into download or recovery which means my ****ing phone is literally worthless.
I have tried all possible thousands of combination's of buttons, batteries, and cords while booting and nothing happens.
The Vibrant logo shows, then it shows the pink, annoying as hell T-mobile logo, than goes to the Galaxy S logo which loads for a little bit and then just leads me to a black screen. Eventually the 4 buttons on the front of the phone turn on and then nothing else happens. It will just sit like this forever.
I know all I need to do is get a working ROM loaded but it is literally impossible to do so.
Can anyone offer any suggestions? Or are anyone else having the same problem?
I guess the only way I can get a working phone is to get in touch with T-mobile and do a Warranty exchange. That's a damn shame too, because I will be without a working phone for a week.
What about using adb?
adb reboot recovery -or- adb reboot download ?
I had a hw locked vibrant, never tried the adb reboot download, recovery did work.. I added another line on my account last night for somone, who got a vibrant, theirs wasn't hw locked, so I traded 'em ;P
Agree with the above poster I have been stuck on the vibrant screen or dark screen and adb still worked to save me
when i try to use adb, it just tells me that it cant find the device. i'm not able to boot into android OS at all.... screen just hangs. so my computer is never getting a chance to see my phone hence why i cant use adb to reboot it into recovery or download.
I believe your device has to go into recovery mode then check with and devices and if you see a device I THINK it is and reboot download, I am 90% certain
Sent from my SGH-T959 using Tapatalk
have you installed the drivers? phone DOES NOT have to boot into android for adb to read it.
98classic said:
have you installed the drivers? phone DOES NOT have to boot into android for adb to read it.
Click to expand...
Click to collapse
i do believe i have the correct drivers installed. i was able to use adb to run lagfixes before i was having this problem. when i boot my phone, i get a sound from my computer saying that it recognizes a usb device. the two drives in the vibrant show up in My Computer but i cannot access them as windows says they are not accessable at the moment.
at what point will adb be able to recognize my phone when booting? no matter what i do when i try adb shell i get error: device not found
It could be the phone not bring in debugging mode, either because it's been turned off or the os isn't getting far enough to turn it on. I think I've been able to get adb to recognize my phone even while it was booting up (at the white vibrant screen). Maybe you can try adb then?
Same problem here. I probably just have to sell it fast on ebay or something. Hopefully some kind of fix starts by the end of the week. First phone in my smartphone life to brick from a simple Voodoo lag fix. Please XDA gods find a solution.
crazycaveman said:
It could be the phone not bring in debugging mode, either because it's been turned off or the os isn't getting far enough to turn it on. I think I've been able to get adb to recognize my phone even while it was booting up (at the white vibrant screen). Maybe you can try adb then?
Click to expand...
Click to collapse
nope, no go. adb will not recognize my device no matter what. and the device isnt loading the OS so i cannot turn debugging on. i guess this is a real "brick" then.
This sounds like a rant rather than a question. Just sayin'.
DKYang said:
This sounds like a rant rather than a question. Just sayin'.
Click to expand...
Click to collapse
fixed that. my bad.
Check my thread in the dev section... I can get ADB working when you are stuck at the vibrant screen... MIGHT... just might work in your situation...
My thread is probably fallen back a few pages now... its a [Guide] [Think Tank]
renocivik said:
Check my thread in the dev section... I can get ADB working when you are stuck at the vibrant screen... MIGHT... just might work in your situation...
My thread is probably fallen back a few pages now... its a [Guide] [Think Tank]
Click to expand...
Click to collapse
thanks for the suggestion. i found your thread and went through the steps in the OP... still no luck. no matter what i do, i cannot get passed the black screen the loads after the galaxy s logo. i also cannot get into download mode or recovery no matter what combination of button presses i use.
just do the following , i used to have the problem of going into the download mode and this is what realy worked to me :
1- turn off the phone.
2- plug in the USB cable.
3- wait until the battery green charging start.
4- press the vol + , vol - , the power botton together.
5- when the screen gose black release the power botton only.
you should now be in the downloading mode
core99 said:
just do the following , i used to have the problem of going into the download mode and this is what realy worked to me :
1- turn off the phone.
2- plug in the USB cable.
3- wait until the battery green charging start.
4- press the vol + , vol - , the power botton together.
5- when the screen gose black release the power botton only.
you should now be in the downloading mode
Click to expand...
Click to collapse
this isnt working either. :-(
I just fixed this on my phone. Your phone will go into download mode. Plug the phone in and wait for the battery symbol to fully load. Hold Vol + and _ and PWR until it goes black, then release the PWR button only. It will go into DL mode. Fire up Odin, and flash the "Froyo that does not brick" ROM. It will boot into the i9000 recovery mode and give you an error. Hold the Vol + and - and PWR again and release PWR when the phone goes black. It will go into DL mode again. Now with Odin, flash the factory firmware, making sure to click re-partition this time. After the phone reboots, it will fire right up into the factory ROM.
atoz350 said:
I just fixed this on my phone. Your phone will go into download mode. Plug the phone in and wait for the battery symbol to fully load. Hold Vol + and _ and PWR until it goes black, then release the PWR button only. It will go into DL mode. Fire up Odin, and flash the "Froyo that does not brick" ROM. It will boot into the i9000 recovery mode and give you an error. Hold the Vol + and - and PWR again and release PWR when the phone goes black. It will go into DL mode again. Now with Odin, flash the factory firmware, making sure to click re-partition this time. After the phone reboots, it will fire right up into the factory ROM.
Click to expand...
Click to collapse
this is exactly the method i want to try. but unfortunately i cannot get the phone into recovery or download mode. i have tried at least 100 times now with many different combination's of plugging the usb cord in and pressing the volume and power buttons.
two ideas: one, is it possible that i wiped recovery and download mode from my phone on accident? the reason why i ask is that i was super tired and flashing roms and kernels to my phone. i flashed back to my original stock rom and then i flashed the kernel. for some reason, i selected wipe date/cache in Rom Manager before flashing the kernel. i have no idea why i did this. seriously. totally noob move. so im assuming i have a kernel flashed but now there is no ROM installed for the phone to boot into.
two, if above is not the issue, than im going to assume that the phone is not recognizing any button presses while its off, so when i turn it on it just recognizes that the power was pressed and ignores the volume presses, thus not booting the phone into recovery or download.
edit: i should mention again that at no time does adb recognize my device. so i cannot use adb to reboot the phone into the mode i need.
just a comment for the OP - the vibrant isnt worthless, it is something that YOU did to get the phone into its current state. So dont blame the phone for something that it didnt do on its own.
/end rant
byt3b0mb said:
just a comment for the OP - the vibrant isnt worthless, it is something that YOU did to get the phone into its current state. So dont blame the phone for something that it didnt do on its own.
/end rant
Click to expand...
Click to collapse
I understand what you mean. I appreciate your criticism of my original post. Let me say that I wrote it while frustrated. But I know that isn't an excuse.
The device is fantastic. I know that I did this to it myself. It's unfortunate.
Anyways, I received a replacement phone. I will be more careful this time.

[Q] Can I reset the phone if stuck in loop?

Hello. My HTC Hero locked up, once again, and when I pulled the battery and tried to reboot, it got stuck in the white, HTC screen. I took it to a repair shop and was told that it has "water damage" and that can probably be fixed. They said as long as it powered up, they could reload the software, if needed. They would charge $25 to reload the software. Is that something I can do myself? I am not sure how to get it into recovery mode from that main white screen. Can anyone help me? I do not have the money to buy a new phone, and really need to get this one up and running again. I don't know if it matters, but my phone is rooted.
Thanks in advance!!!
More info plz
Try pressing the home button before turning and keep pressing 'til you get to the recovery screen then use the usb to move the rom to the sd-card and flash it.
Danger Rom 2.1, it is rooted. Clockwork mod is the recovery. Does that sound right to you? They guy at the repair store just called to say he has it working but he had to wipe it and install the software again. I specifically asked him not to do that knowing it is something I can do at home instead of paying $25. As long as it is powering up I can fix it, is that correct? I just have to get it booted into recovery?
Sorry i edited my first reply when i first read it was rooted .. my mistake are you sure the ROM was running ok? if not you may find loads of other ROMs and just flash them once you're in recovery .. gd luck
I just want to make sure I am in correct in saying, if I can get it booted into recovery, then I can get it up and running again? I shouldn't have to pay someone $25 when I can do it for free. What is the easiest way to boot into recovery?
Yes you can re-flash the ROM once you're in the recovery and that should fix your issue, the easiest way to get into recovery is
1. turn phone off (by removing the battery then putting it back)
2. press the home button and keep holding it
3. press the power button (while holding the home key)
4. that should have got u in recovery screen
Thank you for the info!!

[Q] Atrix Unrecoverable Soft Brick

I'm just going to get straight to the problem here: my Atrix won't boot because something went wrong with a ROM I was trying to install. I was using the package from here Project kitchen sink, and selected aokp. I have Clockwork Recovery 5.8.1.8, so it boots into recovery.
The problem is that my volume rocker is broken, I *think* because of pds, so I cannot navigate the menu. I have tried using RSDLite and Fastboot, hoping that I could work through the recovery boot menu, but it's useless. And since my volume keys refuse to work, I can't set the phone to boot into RSD mode. I'm stuck in an endless loop of not-able-to-do-jack-****, and I don't think I'll be able to send it in to Moto for a replacement.
I don't know if the failure is due to a hardware issue (my Atrix was shipped to me from my family, since I live in Puerto Rico), the CM7 ROM I had before, or a recent crash (the battery was also giving me problems, and lately crashed the phone several times, not turning on unless I pulled it.)
Sparr159 said:
I'm just going to get straight to the problem here: my Atrix won't boot because something went wrong with a ROM I was trying to install. I was using the package from here Project kitchen sink, and selected aokp. I have Clockwork Recovery 5.8.1.8, so it boots into recovery.
The problem is that my volume rocker is broken, I *think* because of pds, so I cannot navigate the menu. I have tried using RSDLite and Fastboot, hoping that I could work through the recovery boot menu, but it's useless. And since my volume keys refuse to work, I can't set the phone to boot into RSD mode. I'm stuck in an endless loop of not-able-to-do-jack-****, and I don't think I'll be able to send it in to Moto for a replacement.
I don't know if the failure is due to a hardware issue (my Atrix was shipped to me from my family, since I live in Puerto Rico), the CM7 ROM I had before, or a recent crash (the battery was also giving me problems, and lately crashed the phone several times, not turning on unless I pulled it.)
Click to expand...
Click to collapse
PDS does not affect volume buttons.
And what happens when you boot? Boot loop is not very specific...
I read a post on here that said it did...
And what happens is that it boots once, stays on the Moto logo, then blacks out, boots again and goes into recovery. Since I have no way to do anything, I press the power button and it goes again.
What I need is either
1) A way to work with RSD through the recovery, or
2) A way to work with ADB through recovery, or
3) Someone to just tell it to me straight: I'm f*cked and I need to send it in to Moto (Which I doubt they would take it.)
Sparr159 said:
I read a post on here that said it did...
And what happens is that it boots once, stays on the Moto logo, then blacks out, boots again and goes into recovery. Since I have no way to do anything, I press the power button and it goes again.
What I need is either
1) A way to work with RSD through the recovery, or
2) A way to work with ADB through recovery, or
3) Someone to just tell it to me straight: I'm f*cked and I need to send it in to Moto (Which I doubt they would take it.)
Click to expand...
Click to collapse
I would tell you to flash touch recovery however I don't think you can and how it would help you recover from this situation.
Sent from my MB860 running Jokersax's CM9
The weird thing is that I had flashed touch recovery before I started with kitchen sink, and it fixed the touch problems I was having there, but now the touch doesn't work. I downloaded it from the clockwork website, because I don't want to pay for something that is available for free, and I flashed it in fastboot.
Now I have Clockwork Recovery 1.8, which should be touch, no?
Sparr159 said:
The weird thing is that I had flashed touch recovery before I started with kitchen sink, and it fixed the touch problems I was having there, but now the touch doesn't work. I downloaded it from the clockwork website, because I don't want to pay for something that is available for free, and I flashed it in fastboot.
Now I have Clockwork Recovery 1.8, which should be touch, no?
Click to expand...
Click to collapse
You mean 5.8.1.8? If so then yes. And if touch is not working in touch recovery then it does sorta confirm you need the PDS fix...
We are finally getting somewhere: yes, it is 5.8.1.8, touch doesn't work. I know I need the PDS fix, and I applied it. Twice. I patched in fastboot before I started with kitchen sink, and I thought it had worked, since the Aroma installer was touch-enabled after I patched. But now the recovery menu is not working. I tried pressing the search key, like with the Aroma installer, but I knew it wouldn't have any effect.
Sparr159 said:
We are finally getting somewhere: yes, it is 5.8.1.8, touch doesn't work. I know I need the PDS fix, and I applied it. Twice. I patched in fastboot before I started with kitchen sink, and I thought it had worked, since the Aroma installer was touch-enabled after I patched. But now the recovery menu is not working. I tried pressing the search key, like with the Aroma installer, but I knew it wouldn't have any effect.
Click to expand...
Click to collapse
Can you point me to the thread where it says volumer rocker is linked to pds because i searched and cant find it.
How are you booting...i mean with what key combination? Im assuming your booting normally(only power button) and end up going into recovery. Try booting with power button and volume down.
Sorry I'm not quoting anybody, first off.
Second, I can't find the link. I spent around an hour searching and found it through duckduckgo, but now I can't remember the search term I used. If I find it, I'll post it.
And yes, I'm booting only with power button, because the volume down key isn't working. That is where the pds problem comes in: I can't use the volume down or up key because the keys don't work.
My friend told me that I could use adb to manually boot it into fastboot mode. That works fine, but I don't know how to flash anything other than the recovery/pds partitions. I know fastboot has a "flashall" command, but I don't know how to use that or if it is even going to help. **Essentially** I can boot into fastboot mode, but I want to know if it is even possible to just flash a rom through that. Messy, of course, but if I can just get even a basic ROM working, I can go on from there.
I think you have 2 options:
1. if you can get to fastboot you can reflash everything using uncle cemka's method: http://forum.xda-developers.com/showthread.php?t=1501532
you basically take an .sbf unpack it and flash each part separately.
2. buy a atrix audio jack/camera flex cable from ebay and install it yourself, be especially careful when installing because the very small flex/ribbon that goes to your volume buttons stress fractures very easily if bent very much when installing, hence your volume buttons stop working.
I'm using cemka's method now. I'm waiting for the stock ROM to download, the one from his post. When I finish the whole process, I'll let you guys know how it worked out.
UPDATE: Thank you to whoever referred me to uncle cemka's method, I was able to use it to flash stock ROM. I have functionality back, can boot, and won't waste around $90 on a paperweight.
However, the first problem is still there: The volume keys still don't work. I still need to fix those before everything is %100 percent, so this issue is still open... Sorry guys

Bootlooping, Odin mode stuck, need a bit of advice

OK, here the story. My SGS2 started acting up a few days ago, it thinks it's charging all the time now. I searched and found that this seems to be a common problem with the port, so I cleaned the contacts on the microUSB connector, but it's not helping. I decided today that I'll just take it in since it's still under warranty, and I'd like to do it after work today since I live almost an hour away from the AT&T Store near the hospital. Problem was, I'm running AOKP on it and I don't have access to a computer with Odin on it where I can restore it to stock. Then I find the thread that details how I can download the .tar file and flash on the phone with Mobile Odin. Seems to work great, but it goes into a bootloop afterwards. One member posted that he had the same problem, but it was solved by booting into recovery and doing a full wipe. Here's where I have a problem now.
I can only boot into Odin mode, and it gives me the choice where it's asking me if I'm sure I want to load a custom binary or cancel and reboot. When I click that I want to load the binary, I get to the Odin mode screen; it reads
Custom Binary Download: No
Current Binary: Samsung Official
Downloading...
Do not turn off target!!
That's it. If I reboot normal, it goes into bootloop. Otherwise, it sits there with the battery logo showing, whether it's plugged in or not.
I'm pretty sure when I get home tonight, I can plug it in and get something going on my desktop, but I'd like to hit up the store before I head home. Anyone got any ideas or suggestions?
If you can't boot into recovery using the three button method, I'm not aware of any way to put it into recovery mode without a computer. You didn't say, but I assume you used vol+, vol-, & pwr?
creepyncrawly said:
If you can't boot into recovery using the three button method, I'm not aware of any way to put it into recovery mode without a computer. You didn't say, but I assume you used vol+, vol-, & pwr?
Click to expand...
Click to collapse
Yup, and that's what comes up. I'm thinking it has something to do with the fact that the phone thinks it's plugged in. I guess I'll just have to plug it in my desktop when I get home and work on it from there. Worst case scenario is that I just take it to AT&T tomorrow as it is, tell them about the false charging problem, and when I tried to do factory reset to see if it would fix things, this is where it's stuck.
I can't believe I spent the first 30 years of my life without a cell phone and now I don't feel right if it won't work for a day or two.
creepyncrawly said:
If you can't boot into recovery using the three button method, I'm not aware of any way to put it into recovery mode without a computer. You didn't say, but I assume you used vol+, vol-, & pwr?
Click to expand...
Click to collapse
I'm having the same problem after trying to install S-Voice. You indicate that there is a way to get into recover using a computer. Can you explain?
Thanks.
drjim said:
I'm having the same problem after trying to install S-Voice. You indicate that there is a way to get into recover using a computer. Can you explain?
Thanks.
Click to expand...
Click to collapse
need adb.
adb reboot recovery
Google
Update:
I actually managed to catch it when it didn't think it was plugged in and do full wipe. It worked after that, sorta. It didn't think it was plugged in all the time, but it was still real funky; like the power usage curve started high, had a sudden big drop, then went up from there. Plus, when it was off, it would flash between a grey battery with a circle and a green on, back and forth. And I couldn't power it on unless it was plugged in. Once I showed them that, AT&T gave me a new SGS2. It's rocking Shostock2 now, so problem solved.

Categories

Resources