Database Info

No more of this :/

This is the last time any of you will see me post in the Captivate forum. I've now gone through 2 captivates due to bricks by Odin not working (gets stuck on DO NOT TURN OFF TARGET!!) and never getting past that thus having a bricked phone. And getting phones that have broken key combos. I'm going back to the Aria. I'll just buy a extended battery since those batteries are so bad.
No Android phone will compare to the speed of the Captivate. But at least I will never have to deal with Odin again.
Thanks to all the constant support and updates for the Captivate here at XDA. I really appreciate it. I love the support and updates that the Captivate got. But I can't stand how easy it is to brick for it to be "impossible" to brick.

Your acting like you had to mess with Odin, no one made you and the phone was usuable without it.

You do realize it was your fault right. And the 3 button combo has gotten fixed. Maybe reading more would have helped out some.
Sent from my SAMSUNG-SGH-I897 using XDA App

User error ruined your phone.

Happy Trails..

Wow ... I thought captivate was unbrickable. I've used Odin tons of times with no issues, most recently last night to installed froyo.
Aria isn't too bad, had one for a month. At least you still have support for the Aria.
Sent from my SAMSUNG-SGH-I897 using XDA App

I have to agree with the other posts here. Odin didn't brick your phone, you did.
Sent from my SAMSUNG-SGH-I897 using XDA App

How do you know it was fully bricked? - I've gotten stuck at DO NOT TURN OFF TARGET; I did these steps to fix it.
Try this, move quickly:
1.) Open ODIN One-Click on the computer.
2.) Take out the SIM and SD card.
3.) Put in the battery, quickly holding VOL UP and VOL DOWN and inserting the USB.
It should go into download mode.

dude....really?

I am the least knowledgeable and phone savvy person here IMO. I owned a Nokia N97 for the last year and a half and an N95 for two years bfore that (I recently trashed)
I was able to with two phones root them the first day, delete ATT SW Download the JH7 Update using Kies Mini, UNroot both and update one to 2.2 with ODIN3 with aero issues.
My wife is still deciding on the N97 vs the Captivate. In the mean time I will be using it as a guinea Pig for messing around with. Going to Master clear it and install Froyo today.
I think many times it is user error and the support here is amazing, patient and extremely well implemented.
I think the OP should step back and revisit all the steps.....This is a great device despite the "GPS failings" which are differing in degree based on individual expectations more than actual reality from what I read.
Small issues tend to become large ones and pileons occur quickly across the net. I would bet the GPS issue is not as bad as many phones , better than some worse thano others. I know it is far better than the GPS on the N97 as is the browser...on and on.

Colton5419 said:
How do you know it was fully bricked? - I've gotten stuck at DO NOT TURN OFF TARGET; I did these steps to fix it.
Try this, move quickly:
1.) Open ODIN One-Click on the computer.
2.) Take out the SIM and SD card.
3.) Put in the battery, quickly holding VOL UP and VOL DOWN and inserting the USB.
It should go into download mode.
Click to expand...
Click to collapse
That works for me everytime. No 3 button combo. Turn off, take out battery, start Odin, insert battery, hold only volume up and volume down, plug in usb. Goes straight to download mode. No counting black screens, no timing button release.
Sent from my SAMSUNG-SGH-I897 using XDA App

I "bricked" my phone. It would only boot to a black screen. Just holding down the volume keys, then adding the power key got me into download mode. Odin fixed everything. I actually fixed it so quickly that never got to the, "crap! I just bricked my phone. I hope I can fix this," stage. It was fixed before I even realized it was at the point that a lot of people around here call bricked. I was more just annoyed that now I had to re-odin before flashing.

Just today odin locked up on me and I had to remove the usb; I was getting the phone to pda disconnect screen when trying to do anything. So I quickly did the VOL UP and VOL DOWN while inserting the USB and thankfully all turned out well and I'm back on FROYO JI6 for now.

Well I have two of these things and they are both at the same thing. Phone+computer, None of the key combos will put them in Download mode. I've done every single possible method found to do it and none of them will work. It's not user error. I didn't brick it. I'm not the only person that had Odin freeze and NOT continue. I've had the worst luck with these phones.

Konner920 said:
Well I have two of these things and they are both at the same thing. Phone+computer, None of the key combos will put them in Download mode. I've done every single possible method found to do it and none of them will work. It's not user error. I didn't brick it. I'm not the only person that had Odin freeze and NOT continue. I've had the worst luck with these phones.
Click to expand...
Click to collapse
It is your fault though, because if you try to change kernels and use odin it is up to you. If the phone has the 3 button combo issue that is one thing, but you still need to know that anything you do to your phone is on you. It is not Samsung or ATT's fault for you trying to change kernel's. But there is no talking sense to someone that doesn't understand that fact. Sorry you had bad issues with this phone.

I have yet to brick my Captivate. The rule of thumb is, if you can get it into Download mode.. it's recoverable. If you decide to get rid of your Captivate, that's your business but the phone is a solid one. I had issues flashing Froyo and thought i bricked but it took a few tries with Odin and i got it working. If you want to use custom firmware, you have to put effort into reading up on things.

This is the funniest thing i have read in a long time. Especially since JH7 fixed the key combo issue.
I had never thought of that angle "I bricked my phone, so i better switch brands". Especially when 99% of us are uing Odin with ZERO issues. The only anology that comes to mind is "Every time I adjust the carb screws i more ford it won't start, so I am switching to Chevy"
Good luck OP!

alphadog00 said:
This is the funniest thing i have read in a long time. Especially since JH7 fixed the key combo issue.
Click to expand...
Click to collapse
JH7 didn't fix my 3-button

this is why i am being patient and just waiting for the official update

I dont understand why people feel the need to post a goodbye thread... we dont care....especially if its user error...if you would have taken the time to post a question with the issues you were having some one would have probably helped you..ehhh..you've wasted your breathe and now I've wasted mine...
Sent from my SAMSUNG-SGH-I897 using XDA App

[Q] Captivate... Isn't a Captivate Anymore?

After a month and a half of anticipation for FroYo, I was excited to find out a method of updating that wouldn't result in my warranty being voided. However, considering that I live in the US, the update wasn't available for me through Kies yet. So, with some digging around, I found a fairly straight-forward way of installing it anyway; I read it on several different news sites and I think I found it originating on this forum somewhere.
Then I realized that the method of doing this was for the i9000, and I have the Captivate i897. Still wanting to upgrade to FroYo, I quickly Google'd the method for use on other models. It seemed like it would work from what I read. So, I went through the steps; edited a few registry entries, clicked the 'update' button in Kies, and waited. Then, to my amazement, it worked: I saw my phone boot up with a newer splash screen. One minor problem so far: it said it was the i9000. I wasn't worried at this point, since I figured it wouldn't make a difference (and if I thought it would, there wasn't much I could do at this point anyway). But it did make a difference.
I was greeted with the familiar LauncherPro, as well as all of my apps. But, it was very laggy and was in landscape, even if my phone was in portrait. Playing around with rotations revealed problem one: the accelerometer was calibrated differently between the two models, showing a 90 degree difference. The lag was fixed with a Factory Reset in the Settings.
I then decided to browse around in the update. One, I had no more AT&T bloatware, and two, I got the free Samsung Apps, including Asphalt5. But, there were a few unwanted apps, too. For example, there was now an FM Radio app, even if the Captivate doesn't have one. That would be issue #2.
Anyway, considering that this was FroYo, I decided to see how well Flash actually worked by watching a Flash animation I found. It works fairly well, besides a few frame drops. Then, I decide to go back to the homescreen. Pressing 'Home' went back. Pressing 'Back' went back again. That is problem #3: the home button acts as a second back button, leaving me with a menu button, a search button, and two back buttons.
Between these issues, it is inconvenient to use the phone. Seeing this, I was wondering if I could 1.) Downgrade back to 2.1 Eclair (without rooting or anything) or 2.) Install the Captivate i897 variation of the Kies update once it's released in the US with even more Registry hacks. Thanks in advance!
[And sorry if this question has already been posted, but I didn't see it after a bit of searching]

Look for the odin one click in dev section(takes you to stock jf6). If you want to try froyo, cognition (for the captivate) its by designgears(he also did odin) it has a good faq(read it!) and great roms. I know it seems like a pain but go through the whole tread too.
Sent from my SAMSUNG-SGH-I897 using XDA App

This will take you back to a stock captivate if you want
http://forum.xda-developers.com/showthread.php?t=731989
Also there is allot of info on how to run an i9000 rom on the captivate as well as a beta reorient i9000 kernel for froyo in the development forum here
http://forum.xda-developers.com/forumdisplay.php?f=706
but take your time and make sure you know what you are doing with everything you try.

dayv said:
This will take you back to a stock captivate if you want
Also there is allot of info on how to run an i9000 rom on the captivate as well as a beta reorient i9000 kernel for froyo in the development forum here
but take your time and make sure you know what you are doing with everything you try.
Click to expand...
Click to collapse
After about two hours of frustration, ODIN finally gave in and fixed my phone! ^_^ Thanks for your help.

K25125 said:
After a month and a half of anticipation for FroYo, I was excited to find out a method of updating that wouldn't result in my warranty being voided. However, considering that I live in the US, the update wasn't available for me through Kies yet. So, with some digging around, I found a fairly straight-forward way of installing it anyway; I read it on several different news sites and I think I found it originating on this forum somewhere.
Then I realized that the method of doing this was for the i9000, and I have the Captivate i897. Still wanting to upgrade to FroYo, I quickly Google'd the method for use on other models. It seemed like it would work from what I read. So, I went through the steps; edited a few registry entries, clicked the 'update' button in Kies, and waited. Then, to my amazement, it worked: I saw my phone boot up with a newer splash screen. One minor problem so far: it said it was the i9000. I wasn't worried at this point, since I figured it wouldn't make a difference (and if I thought it would, there wasn't much I could do at this point anyway). But it did make a difference.
I was greeted with the familiar LauncherPro, as well as all of my apps. But, it was very laggy and was in landscape, even if my phone was in portrait. Playing around with rotations revealed problem one: the accelerometer was calibrated differently between the two models, showing a 90 degree difference. The lag was fixed with a Factory Reset in the Settings.
I then decided to browse around in the update. One, I had no more AT&T bloatware, and two, I got the free Samsung Apps, including Asphalt5. But, there were a few unwanted apps, too. For example, there was now an FM Radio app, even if the Captivate doesn't have one. That would be issue #2.
Anyway, considering that this was FroYo, I decided to see how well Flash actually worked by watching a Flash animation I found. It works fairly well, besides a few frame drops. Then, I decide to go back to the homescreen. Pressing 'Home' went back. Pressing 'Back' went back again. That is problem #3: the home button acts as a second back button, leaving me with a menu button, a search button, and two back buttons.
Between these issues, it is inconvenient to use the phone. Seeing this, I was wondering if I could 1.) Downgrade back to 2.1 Eclair (without rooting or anything) or 2.) Install the Captivate i897 variation of the Kies update once it's released in the US with even more Registry hacks. Thanks in advance!
[And sorry if this question has already been posted, but I didn't see it after a bit of searching]
Click to expand...
Click to collapse
Not sure why you didn't read the dozens of threads in regards to putting a i9000 rom on the captivate. You could have seen quickly that all the issues you have seen are well documented and most suggest hacks or different kernels to fix your issues.

K25125 said:
After a month and a half of anticipation for FroYo, I was excited to find out a method of updating that wouldn't result in my warranty being voided.
Click to expand...
Click to collapse
I am trying to find out where you heard this And what you are talking about.
Unless the update comes over the air; or Samsung makes an official announcement that says "update your captivate via Kies" or "update your captivate via odin"; then no method you read about will be official or save your warranty.
Any flashing of your phone - that is not directed by Samsung or AT&T will void your warranty. Unless you put it all back undetected.

i still love my cappy

alphadog00 said:
I am trying to find out where you heard this And what you are talking about.
Unless the update comes over the air; or Samsung makes an official announcement that says "update your captivate via Kies" or "update your captivate via odin"; then no method you read about will be official or save your warranty.
Any flashing of your phone - that is not directed by Samsung or AT&T will void your warranty. Unless you put it all back undetected.
Click to expand...
Click to collapse
Samsung had a press release about a Kies update, but only for certain parts of the world at this point. However, there was some Regedit trick that forced it to download the i9000 firmware regardless of location. The firmware didn't work very well, so I used ODIN One-Click, then flashed Cognition instead.
So, my warranty is now dead.

K25125 said:
Samsung had a press release about a Kies update, but only for certain parts of the world at this point. However, there was some Regedit trick that forced it to download the i9000 firmware regardless of location. The firmware didn't work very well, so I used ODIN One-Click, then flashed Cognition instead.
So, my warranty is now dead.
Click to expand...
Click to collapse
just flash back to jf6 or jf7 if you have issues. hopefully the official version will be out before you need to use the warranty. believe me as long as it looks legit at a glance the repair centers dont care if it is an odin flash or official update via ota or kies. they just replace parts, reflash and move on to the next one.

[HELP] What do I do now? Captivate dead.

Yessss another dead captivate thread.
I think I'm gonna go die now.
I followed the video guide to install a custom ROM, in the development thread to the letter, and now my phone wont even turn on... (now that im thinking about it, I think I may have left the debugging mode OFF before I went to flash back to stock, maybe thats why?)
I got into download mode, plugged the phone into odin3 JF6 one click, it started and at some point during the process it said "removed" even though I didnt touch anything, and then i got a weird msg saying my device is not recognized, keep in mind the drivers were installed properly, and I had everything double checked before i flashed....
wtf do I do now? Cant boot at all or go back into download mode. this is my third galaxy, got it two days ago ffs.

My only 2 suggestions. Go to the Dev section and in the guides there is a method to make a USB Jig without solder or anything. You're out like $1 if it doesn't work.
Also, what rev is your phone? There's been some threads started saying the newer Rev phones, maybe 1010 and up crap out using normal One-click. Do check your rev level under the battery and do a search of the forums. I know I have seen the threads.
good luck.

1 reboot pc
2 use different usb ports (direct to motherboard)
3 open odin first as administrator
Sent from my GT-I9000 using XDA App

bobbylx said:
My only 2 suggestions. Go to the Dev section and in the guides there is a method to make a USB Jig without solder or anything. You're out like $1 if it doesn't work.
Also, what rev is your phone? There's been some threads started saying the newer Rev phones, maybe 1010 and up crap out using normal One-click. Do check your rev level under the battery and do a search of the forums. I know I have seen the threads.
good luck.
Click to expand...
Click to collapse
I'm not sure if I was looking at the right place, but I think its 10.12. I'll do a search and see what comes up, thanks for your help.
JayPhill89 said:
1 reboot pc
2 use different usb ports (direct to motherboard)
3 open odin first as administrator
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I'll try that, thanks.

Open Odin first then,
1. Remove your battery for 30 seconds, remove external SD card and SIM card
2. Reinsert battery.
3. Hold down both volume buttons and while holding them down plug the phone in.
It should get into download mode then. I bricked my phone and it wouldn't boot up at all and this worked for me.
On a side note, I have not had much luck flashing or doing much of anything on Windows 7 64 bit. I would suggest trying it on an XP machine if you have access to one.

G.Hook said:
Open Odin first then,
1. Remove your battery for 30 seconds, remove external SD card and SIM card
2. Reinsert battery.
3. Hold down both volume buttons and while holding them down plug the phone in.
It should get into download mode then. I bricked my phone and it wouldn't boot up at all and this worked for me.
On a side note, I have not had much luck flashing or doing much of anything on Windows 7 64 bit. I would suggest trying it on an XP machine if you have access to one.
Click to expand...
Click to collapse
I've tried every possible key combination out there and nothing works. I think my best bet is a Jig, unfortunately the source didnt have any transistors in stock so im SOL for now.

Use JIG ... It will be your last help.

Use it as a paper weight.

If you look up samsung captivate jig on ebay you will find some pre built. I bought one not long ago just to have and it works just fine.
I hope this helps. Best of luck to you.
Sent from my GT-I9000 using XDA App

Sounds like you are a victim of the one size odin fits all debacle. You will indeed need a jig to recover and then you must use odin to flash jh2 or later firmware to your phone. Unfortunately, most guides still direct people to flash jf6 even though your situation comes up on a regular basis.

Check out this link for a jig. And there is a video to show you how to build one. Or mobiletechvideo guy sells them for 17 bucks.
http://forum.xda-developers.com/showthread.php?t=889128&highlight=usb+jig
Sent from my SGH-I897 using XDA App

newter55 said:
Sounds like you are a victim of the one size odin fits all debacle. You will indeed need a jig to recover and then you must use odin to flash jh2 or later firmware to your phone. Unfortunately, most guides still direct people to flash jf6 even though your situation comes up on a regular basis.
Click to expand...
Click to collapse
It seems to me like there's consistent irregularities with the entire process, its not uniform at all, which is very frustrating, every one faces different problems, and the solution is never the same.
Anyways, I went out and bought 3 resistors, turns out they were the wrong ones, I found out the colors werent the same of what I needed, but then that just goes to show you how difficult it is, its partly my fault i got the wrong ones, but someone like me who doesnt know much about hardware hacking, walks into an electronic store, faced with several options, is some times lost.
Oh well, I could've fixed it, had I got the right resistors, but then again, who was going to guarantee I wasn't going to kill it again, for the exact same reason I mentioned in the first post, because I need to consider a few things here, first and foremost, that I have a rogers branded device, and these are the ATT forums.
I called rogers and a replacement has been placed, I should be getting it by friday, or tomorrow if im lucky, with whatever comfort that brings, I still have several concerns, and now that I've basically rendered 3 devices to "almost" none-working condition (this one being an exception because I can "possibly" fix it) I'm not even sure how far I want to go.

rsnt said:
It seems to me like there's consistent irregularities with the entire process, its not uniform at all, which is very frustrating, every one faces different problems, and the solution is never the same.
Anyways, I went out and bought 3 resistors, turns out they were the wrong ones, I found out the colors werent the same of what I needed, but then that just goes to show you how difficult it is, its partly my fault i got the wrong ones, but someone like me who doesnt know much about hardware hacking, walks into an electronic store, faced with several options, is some times lost.
Oh well, I could've fixed it, had I got the right resistors, but then again, who was going to guarantee I wasn't going to kill it again, for the exact same reason I mentioned in the first post, because I need to consider a few things here, first and foremost, that I have a rogers branded device, and these are the ATT forums.
I called rogers and a replacement has been placed, I should be getting it by friday, or tomorrow if im lucky, with whatever comfort that brings, I still have several concerns, and now that I've basically rendered 3 devices to "almost" none-working condition (this one being an exception because I can "possibly" fix it) I'm not even sure how far I want to go.
Click to expand...
Click to collapse
My first captivate went fubar within my 30 days and I damaged the nv_data.bin on my second captivate and was stuck with the test IMEI. Samsung fixed my second one for free. Now I'm at the point where I'm totally sure about what precautions I need to take to keep me out of trouble but I'm not sure if I want to risk it again, heh.
The cheap jig does work. It helped me when I accidentally unplugged my phone during an odin flash.

Yes, you make a good point. You will find that most of the guides are written by people like myself who have an early revision or a phone from the initial release. For most of us, from what I've read and experienced, our phones are really hard to brick, ie, button recovery always works, odin one-click works, etc.
I honestly don't know all the differences now between revs. The first hiccup was the phones missing button recovery/download, and now it seems that people are having issues using the Odin One-click that we have been using for months.
I would recommend with your next phone check the rev or manufacture date, then search the forums for people with similar or same revs that have been successful at flashing and find out what they did.
good luck

@bobby
I wasnt trying to diminish the help that the guides provide. The work that went into creating them is certainly appreciated. The problem arises when so many people just tell newcomers to flash with x version of odin without considering the changes that have occured in the newer builds.
Sent from my Liquid Metal using XDA App

newter55 said:
@bobby
I wasnt trying to diminish the help that the guides provide. The work that went into creating them is certainly appreciated. The problem arises when so many people just tell newcomers to flash with x version of odin without considering the changes that have occured in the newer builds.
Sent from my Liquid Metal using XDA App
Click to expand...
Click to collapse
I agree with you completely. I tend to take it for granted that button recovery works for me and that good old odin one-click does too. It seems we need to start collecting data and making new guides.
Something like,
If you have rev, 1006, 1007,1008 go here,
If you have rev 1009 to 1012 go here,
etc.

latest update,
Two cables, and six resistors later, my phone won't go into download mode, lol, I'm not even sure I did things right, I'm gonna try stripping the same cable, used in one of those videos on how to make a jig, I still have three extra resistors.
I'm starting to think its because of it being with rogers. im gonna search the forums.

A micro usb breakout board is the simplest method for constructing a jig.

Wow, I guess I'm lucky that the used Captivate I picked up for my gf is an older one at 1007. Root procedure for her went without a hitch.
From stock rom, all set up and in daily use, WITHOUT ROOTING first.
Put clockwork update.zip on her sdcard.
Reboot into recovery.
Reinstall packages twice to get into clockwork recovery.
Wipe data/factory reset.
Flash Cognition.
Profit.
She's been using it this way for two weeks and loves it so much more than stock.
What was so complicated about the procedure you followed? Or was it the same as this but it just didn't work?

rsnt said:
...and now that I've basically rendered 3 devices to "almost" none-working condition (this one being an exception because I can "possibly" fix it) I'm not even sure how far I want to go.
Click to expand...
Click to collapse
I think you may have a good point. Eventually your carrier will stop replacing bricks for you. If you still have the inclination to play with flashing, investing in a jig would definately be a wise investment and if I were in your shoes, I wouldn't flash anything without one. I made a jig for myself before I ever flashed anything but luckily I have never had to use it, probably because I took the time (about a month and a half of trolling around here reading.) to research what all was involved with what I was about to jump into. Just something to consider in case you want to try again. Good luck!

[Q] com.Android.phone crashes after root Samsung Admire

Last week I rooted my primary phone, a Samsung Admire with Gingerbread 2.3.4. This was done only after successfully rooting my older LG Optimus T running Fryo. I had no trouble with either phone during the process. However, as of 2 days ago the Admire has had some troubles, namely that the phone function crashes when I press the send key. I get the error message stating “Sorry! The process com.android.phone has stopped unexpectedly. Please try again.” It will receive incoming calls but they cannot be answered and when I try, it crashes
I’ve spent much of the time since researching the problem to find the cause and it’s fix. In doing d\so I have read of multiple causes from screen resolution changes to attempted over clocking, which I have played with. I’ve read that there might be problems with the phones attempting to switch from 2g to 3g too rapidly, something this phone cannot do I believe.
I came to the conclusion, probably erroneously, that I needed to reset it back to factory and then reinstall apps and data out of the backup I made using Titanium Backup prior to the phones troubles. So I did so, doing the three button cocktail I’ve read about here on XDA Forums. After doing this, the problem persists. I’ve read some more becoming more baffled as I went along. So I tried to reroot the phone using one click root, and that was unsuccessful as well, no root. I then read that all I needed to do was to install Superuser from the Market. In attempting this I found my device was no longer recognized by Market and after going through their troubleshooting process it’s still unrecognized, Next I decided, also most likely erroneously to reset the phone again using the three button combo as before. This time I noticed at the bottom of the screen written in yellow, E: File is written: not updated
Also as a side note my phone currently says that there are 133MB available and after the reset(s) my bloat ware has not returned,
So that’s it. I seem to have deleted something that kills the phone app and prevents me from rooting. Other than those two things the phone is working well. However as it sits it’s merely a small Internet tablet with no phone capability. Can anyone help me out with this? And yes, I have read and read and read about it but clearly this is beyond my ability to fix on my own.
Thanks,
Zeke

Hey, my skill level ranges between beginner and intermediate, but honestly in a situation like that I would odin back to stock. I have an epic 4g, so I have no idea what your download mode is or if you have one or if you have to use quick boot or fast boot? Its one of those. If **** ever hits the fan on me (Thank god it hasn't yet) I would odin to an old stock rom and root it and install a recovery and wipe and flash a ROM. Good luck I hope I helped and didn't sound like too much of a scrub.

Reached said:
Hey, my skill level ranges between beginner and intermediate, but honestly in a situation like that I would odin back to stock. I have an epic 4g, so I have no idea what your download mode is or if you have one or if you have to use quick boot or fast boot? Its one of those. If **** ever hits the fan on me (Thank god it hasn't yet) I would odin to an old stock rom and root it and install a recovery and wipe and flash a ROM. Good luck I hope I helped and didn't sound like too much of a scrub.
Click to expand...
Click to collapse
I will research this Odin you mention as I have no clue as to what it is. Thanks, anyone else care to chime in?
Zeke

[Q] Can't Boot Into Bootloader

First, let me say I am a noob and not a developer, just more of a phone enthusiast. That said, my problem is that I cannot boot into the bootloader on my AT&T HOX. I have read through many threads on how this is done (Pwr+VolDown), but it simply doesn't work for me. After about 4 seconds, my nav button baklights flash a few times, then stop. From this point, I have tried two things...1) contine holdign pwr+voldown for well over a minute, nothign happens and 2) releasing the pwr+voldwn bottons and then pressing again and holding for what seems to be an eternity, but still nothing happens. Note that I'm having no issues with a normal boot.
The caviat: in order to sync my company's corporate email via exchange, I have to enable administrator rights by my company's IT policies (which totally blows, I know). This forces encryption on phone storage, even though I think it's really just the sector that houses files related to my exchange account. Regardless, I'm wondering if the administrative rights or encryption is what's preventing me from accessing my bootlader.
Thoughts? I know the thing I should so is just remove my exchange and disable the administrator rights, but to do so I am forced to factory reset the phone, which I'd like to prevent doing unless that's all there is left to do.
Any help is appreciated. If this is a dumb noob question and I missed a previous thread containing a solution, please link and I wont keep this thread going. thanks a lot.

Why are you trying to get into H-Boot? Are you trying to re-flash your phone with the stock ruu or something?
Anyways, to answer your question. No your admin stuff is in no way causing the phone not to get to h-boot, and it's there, I don't think I've ever heard of a phone that boots that can't h-boot.

HydroSkillet said:
Why are you trying to get into H-Boot? Are you trying to re-flash your phone with the stock ruu or something?
Anyways, to answer your question. No your admin stuff is in no way causing the phone not to get to h-boot, and it's there, I don't think I've ever heard of a phone that boots that can't h-boot.
Click to expand...
Click to collapse
To be honest, at this point I am only trying to access it out of curiosity. But ultimately I am checking it out because I have started to have a lot of connectivity problems with wi-fi and was looking into flashing the 1.82 update floating around. I was going to wait until the offical OTA update, but the wi-fi problem is getting worse, or at least it's effecting me more. Anyway, was just looking into accessing it. I initially noticed that I couldn't get in last week when reading a battery thread on calibration since my first couple days witht eh phone had very poor battery life. But it's improved since then and I never went back to check until the wi-fi issues proved annoying. Since I haven't rooted a device before, i figured I woudl familiarize myself with some of the basic steps before assuming I would just jump right in. Checking out how to h-boot seemed like a good place to start.

fitchpuckman said:
To be honest, at this point I am only trying to access it out of curiosity. But ultimately I am checking it out because I have started to have a lot of connectivity problems with wi-fi and was looking into flashing the 1.82 update floating around. I was going to wait until the offical OTA update, but the wi-fi problem is getting worse, or at least it's effecting me more. Anyway, was just looking into accessing it. I initially noticed that I couldn't get in last week when reading a battery thread on calibration since my first couple days witht eh phone had very poor battery life. But it's improved since then and I never went back to check until the wi-fi issues proved annoying. Since I haven't rooted a device before, i figured I woudl familiarize myself with some of the basic steps before assuming I would just jump right in. Checking out how to h-boot seemed like a good place to start.
Click to expand...
Click to collapse
disable fastboot in power options. turn the phone off. Hold down and power, you should see your h-boot
Also if you're looking to flash the unreleased it's just an exe that you run.... it's easy.

^This. Need to disable fast boot in your power options first.

HydroSkillet said:
disable fastboot in power options. turn the phone off. Hold down and power, you should see your h-boot
Also if you're looking to flash the unreleased it's just an exe that you run.... it's easy.
Click to expand...
Click to collapse
beaups said:
^This. Need to disable fast boot in your power options first.
Click to expand...
Click to collapse
Thanks guys, this is likely the case. I thought I disabled fast-boot mode the other day, but apparently I did not. I'll give it a shot in a little bit when I get back to my desk and let you know if I'm still stuck.
Also, re the unreleased RUU, yeah the thread made it sound pretty simple. there were various folks having issues after the update, so I'm just going to monitor for a few more days to see how my phone performs and if there comes official word of a carrier OTA update.
Thanks again.