Related
Hi everyone. I have a samsung galaxy s vibrant on android 2.2. I am a total noob with any modifications but am going overseas next month and wanted to unlock my phone. After looking into rooting etc. I downloaded odin and darky's ROM resurrection edition. I followed the prompts to go into recovery and wipe etc. and remove battery and turn back on. After using odin and restarting my phone now just flashes the start screen showing galaxy s GT-I9000. I can't enter recovery mode just download mode. I'm unsure what to do and even tried mounting another recovery file on odin which lead me to the same point. Any help would be greatly appreciated.
Try re-flashing it and see if that works, sometimes that's all it takes. It's possible you just had a bad flash.
I've tried about 5 times now and it seems to keep failing to boot after flash and sticking on the initial boot screen and flashing on and off. Is there a way to download and flash an original ROM and mount on odin to start over?
Try getting into download mode. Hold and continue to hold up & down volume controls while holding in the power button. When the Vibrant logo comes up release only the power button. If you do get into recovery that way scroll down to install zip from sd card and install whatever rom you've got on there that you want to use. Let me know if that works or not.
I can still only get into download mode. I've tried flashing again with both ROMs I have and they both are doing the same thing. Holy frustrating lol
Spike84 said:
I can still only get into download mode. I've tried flashing again with both ROMs I have and they both are doing the same thing. Holy frustrating lol
Click to expand...
Click to collapse
Look for a hard surface... concrete for example.. now take your phone and throw it as hard as you can... Just kidding don't do that, that's a permanent reboot. I know the frustration, I've been there many times. You may want to go back and read through the noob guide, I'm not sure what else to suggest. Hopefully someone else will read this and have a better suggestion. Good luck.
haha yeah the thought crossed my mind. I appreciate your help. I'm still reading through the forum. Most instructions seem to require me to reach recovery mode or usb debugging. My phone is no longer being recognized on the computer but odin is obviously still recognizing so I'm going to try a fresh 2.2 on odin and see if that works.
Good luck, I'm rooting for ya. If that does not work and your close to a T-mobile store I'd just run it in and have them check it out, they may have to replace it.
Thanks again. I'm actually in Canada and using a sub provider from bell "virgin mobile".
Well last night I tried to unlock my brothers Atrix 4G on 2.3.4 using zomgunlock-lite.sbf using RDS Lite.
It failed and the phone was unable to boot with the error code 0x1000.
So basically I thought it was for sure bricked, but I kept looking around. I found nothing.
However I did find this file:
filesonic.com/file/1507329091/1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf.gz
Which is apparently like a restored bootloader(or something, i'm new to android), so i plugged the phone into the computer, arrowed down to RSD support or whatever on the phone, and using RSD lite 5.3.1 I managed to flash that file onto the device and get it working again.
Maybe I was never hard bricked in the first place but everyone I found on the internet thought so.
Hope this helped some people, it was a great relief when it worked for me.
After flashing the "zomgunlock-lite.sbf" you could have pulled the battery (then put it back in) and without turning it on just plug back into the computer and it would have turned on by itself and given you a menu in which you would have selected fastboot and then entered the commands for unlocking the bootloader.
I'm glad you got yours working and appreciate the info but there is a way out of it. Actually, someone has created an automatic script for just that occasion here:
http://forum.xda-developers.com/showthread.php?t=1182871
Just follow the directions for the error.
ravicus said:
Well last night I tried to unlock my brothers Atrix 4G on 2.3.4 using zomgunlock-lite.sbf using RDS Lite.
It failed and the phone was unable to boot with the error code 0x1000.
So basically I thought it was for sure bricked, but I kept looking around. I found nothing.
However I did find this file:
filesonic.com/file/1507329091/1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf.gz
Which is apparently like a restored bootloader(or something, i'm new to android), so i plugged the phone into the computer, arrowed down to RSD support or whatever on the phone, and using RSD lite 5.3.1 I managed to flash that file onto the device and get it working again.
Maybe I was never hard bricked in the first place but everyone I found on the internet thought so.
Hope this helped some people, it was a great relief when it worked for me.
Click to expand...
Click to collapse
glad you're phone is ok, but yea you were not hard bricked. You just had to redo the OEM unlock command in fastboot one more time. The hard brick is when trying to downgrade, not from flashing pudding and it takes away the ability to RSD or fastboot. If those options are there then there's a way out.
I think a mod should change title so people aren't getting false hope.
You were soft bricked. Unlocking a stock 2.3.4 phone always results in a 0x1000 No OS error, at which point you are supposed to choose fastboot before the 5 seconds are up (or reboot into fastboot mode if you miss the 5 second window) and run fastboot oem unlock once to get the unique key and then again with the key followed by a fastboot reboot.
I repeat, all unlock attempts on stock 2.3.4 OTA Atrices will result in this temporary soft brick.
This thread really did me a massive favor in telling me exactly what I was searching for when google was being useless. Thank you guys. Particularly the post above mine about soft bricks.
ravicus said:
Well last night I tried to unlock my brothers Atrix 4G on 2.3.4 using zomgunlock-lite.sbf using RDS Lite.
It failed and the phone was unable to boot with the error code 0x1000.
So basically I thought it was for sure bricked, but I kept looking around. I found nothing.
However I did find this file:
filesonic.com/file/1507329091/1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf.gz
Which is apparently like a restored bootloader(or something, i'm new to android), so i plugged the phone into the computer, arrowed down to RSD support or whatever on the phone, and using RSD lite 5.3.1 I managed to flash that file onto the device and get it working again.
Maybe I was never hard bricked in the first place but everyone I found on the internet thought so.
Hope this helped some people, it was a great relief when it worked for me.
Click to expand...
Click to collapse
Massive n00b post, nothing but misinformation.
Sweet.....
soft brick could be fixed.. my phone is hard one, can not be read by PC.. it is always booting loop.
and blemeIf
I have also hard bricked my Atrix. I have read many post on this forum and on google that phone can not be recovered after hard brick. Is it confirmed that there is no way to recover after a hard bricked? Please help.
mysticdrew said:
glad you're phone is ok, but yea you were not hard bricked. You just had to redo the OEM unlock command in fastboot one more time. The hard brick is when trying to downgrade, not from flashing pudding and it takes away the ability to RSD or fastboot. If those options are there then there's a way out.
I think a mod should change title so people aren't getting false hope.
Click to expand...
Click to collapse
So, i did try to downgrade using RSD lite since nothing seemed to work when i was stuck at the unlocked M screen despite flashing 3 different roms via CWM. Now i get the error message failed to boot 0x1000, but there are no options at all and my phone just goes to black after 1sec. this is considered hard bricked correct? and there is nothing i can do other than send it into motorola
patsprobst said:
So, i did try to downgrade using RSD lite since nothing seemed to work when i was stuck at the unlocked M screen despite flashing 3 different roms via CWM. Now i get the error message failed to boot 0x1000, but there are no options at all and my phone just goes to black after 1sec. this is considered hard bricked correct? and there is nothing i can do other than send it into motorola
Click to expand...
Click to collapse
Try http://forum.xda-developers.com/showthread.php?t=1648947
dcarpenter85 said:
You were soft bricked. Unlocking a stock 2.3.4 phone always results in a 0x1000 No OS error, at which point you are supposed to choose fastboot before the 5 seconds are up (or reboot into fastboot mode if you miss the 5 second window) and run fastboot oem unlock once to get the unique key and then again with the key followed by a fastboot reboot.
I repeat, all unlock attempts on stock 2.3.4 OTA Atrices will result in this temporary soft brick.
Click to expand...
Click to collapse
I can't believe it was so hard to find these particular instructions and that it is not listed anywhere on the sbf file. Thank you so much for your answer and the last sentence should be added to the sbf file. Actually your whole statement should be there. Thanks a lot. Saved me a lot of anguish.
Alright here goes
So my question is, what options do i have? I can't access any recovery options (Fastboot, android recovery, etc) and my RSD lite wont connect.
Short Story
Every time i try to boot my Atrix (after trying to update CherryPi), I get the Failed to boot 2, Starting RSD mode. Unfortunately, when I plug my phone into a computer RSD doesn't see it. It's like its not even phased.
Long Story
Okay, so I got my atrix not too long ago. Got my phone rooted at proceeded to use gingerblur. Then shortly there after, I attempted to upgrade to the Gingerbread OTA update, which got me stuck in a boot loop. (Now I'm a little confused, I don't think that I have unlocked my phone at all. I don't ever recall "unlocked" being on the boot screen at all). From this point I don't think RSD was working. I spent about a week trying to get it to work. Then I was able to fastboot flash the stock img files for gingerbread to my phone. So now I had a working gingerbread atrix. I sat stock for a little while, figgured out how to root via fastboot (again, no rsd support at this point). After I was rooted I installed CherryPi 0.3 via CWM. It worked great, a couple of days later I went to do the CherryPi 0.X > 0.5 and it flashed with CWM "successfully" got to the AT&T logo on bootup and then crashed and has been giving me the failed to boot 2.
I hope i've given you guys enough info. If any of you super hackers live in San Diego, I'd be more then willing to bring my phone over for you to figure out. So I just really need to know what my options are. If I take it back to AT&T will they likely give me a new one? (I'm good at playing dumb). I traded my phone originally so I don't know what kind of warranty is in place. Can I contact Motorola and get a new handset? Just looking for suggestions.
Thanks guys
Have you tried to reinstall the motorola driver?
Yes, when I first "lost" RSD support and since the current "Failed to boot 2" message.
It has the flash interface when I plug it in, but the motorola software dosent see it, same with RSD. just like nothing is plugged in.
Why not put it into fastboot mode when it reboots and then flash a different file?
phobos512 said:
Why not put it into fastboot mode when it reboots and then flash a different file?
Click to expand...
Click to collapse
It won't boot into any other mode, upon putting the battery in, it shows the dual core logo for about 1.5-2 seconds that pops up the "Failed to boot 2" message and starting RSD mode.
Judging by your first post u mentioned that u never unlocked your boot loader, unless I'm reading this wrong. These ROMS weren't meant to be flashed with the Bootstrapped version of CWM (The one that requires u to be plugged in to AC power) so not sure if that sheds any light on the subject or not. Again, if I read your post wrong, I apologize.
Sent from my MB860 using XDA Premium App
Phalanx7621 said:
Judging by your first post u mentioned that u never unlocked your boot loader, unless I'm reading this wrong. These ROMS weren't meant to be flashed with the Bootstrapped version of CWM (The one that requires u to be plugged in to AC power) so not sure if that sheds any light on the subject or not. Again, if I read your post wrong, I apologize.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Ya, from what I can tell its Motorola locking me out for using an modified rom. But I think that I should be able to return to a stock firmware using RSD lite or the Motorola software restore from thier site, but neither see my phone connected. This leads me to belive that somewhere in the process the RSD protocol got messed up. Now I really don't know much, just enough to be dangerous. So if theres anyone that can tell me if I'm even looking the right direction.
And if I am right is there anything I could possibly do?
gjRabbit said:
Alright here goes
So my question is, what options do i have? I can't access any recovery options (Fastboot, android recovery, etc) and my RSD lite wont connect.
Short Story
Every time i try to boot my Atrix (after trying to update CherryPi), I get the Failed to boot 2, Starting RSD mode. Unfortunately, when I plug my phone into a computer RSD doesn't see it. It's like its not even phased.
Long Story
Okay, so I got my atrix not too long ago. Got my phone rooted at proceeded to use gingerblur. Then shortly there after, I attempted to upgrade to the Gingerbread OTA update, which got me stuck in a boot loop. (Now I'm a little confused, I don't think that I have unlocked my phone at all. I don't ever recall "unlocked" being on the boot screen at all). From this point I don't think RSD was working. I spent about a week trying to get it to work. Then I was able to fastboot flash the stock img files for gingerbread to my phone. So now I had a working gingerbread atrix. I sat stock for a little while, figgured out how to root via fastboot (again, no rsd support at this point). After I was rooted I installed CherryPi 0.3 via CWM. It worked great, a couple of days later I went to do the CherryPi 0.X > 0.5 and it flashed with CWM "successfully" got to the AT&T logo on bootup and then crashed and has been giving me the failed to boot 2.
I hope i've given you guys enough info. If any of you super hackers live in San Diego, I'd be more then willing to bring my phone over for you to figure out. So I just really need to know what my options are. If I take it back to AT&T will they likely give me a new one? (I'm good at playing dumb). I traded my phone originally so I don't know what kind of warranty is in place. Can I contact Motorola and get a new handset? Just looking for suggestions.
Thanks guys
Click to expand...
Click to collapse
Hey man, I have the same problem with you.. have you some progress for that..
I find some infor from forum that this kind of hard brick can be solved by using the developping cable to reflash the sbk file, this method is pending at the SBK file is unavailable which is not released out by MOtorola.. I find a one of my friend who is working in MOTO (Tianjing, CHINA) to see my device, I hope he can help me to unbrick my phone.. when i have good news, I'll update it.
If someone has found the solution for the hard brick in motorola atrix please share this post
Nope. And very unlikely it will unless motorola leaks what is needed.
I voided my warranty.
No.. so many hard brick happened, no solution now.
not to sure if this helps but just about an hour ago i found myself bricked with "0x1000 failed to boot os" this happened will i was trying to enable pudding. the phone was ota updated to gingerbread.. so i started to panic and i decided to go ahead and try to unlock the bootloader anyways.. so i pulled the battery and rebooted the phone then started fastboot mode.. the phone was showing the 0x1000 error still. then i ran the command for the oem unlock and then wiped the phone in fastboot then i rebooted. to my surprise the phone booted to the motorola boot logo screen with the unlocked sign at the top.. but the phone did not start up all the way. so decided to flash tenfars recovery and did so.. booted into recovery and flashed alien build 4 and then rebooted and now i have to phone back up and running! so like i said im not too sure if i did hard brick ..but thought i share what happend! hope that helps!
Yeah that what you had was a soft brick,but what were talking about is a hard brick,where nothing happens when you push the power button,only if you put the battery in it shows the error message.
i apoligize. just wondering why the thread in the dev section is labeled hard brick 0x1000?
Here's the story - purchased a soft-bricked Vibrant for $50. It booted up to the phone - ! - computer screen. Took it home, used One-Click Unboot. Took a few tries, drivers, and USB ports, but eventually it worked. After that, it was just turning on and hanging at the Vibrant screen. Going along with other threads, I tried flashing to stock from ODIN. I followed this guide: http://androidspin.com/2010/08/09/how-to-restore-or-recover-your-samsung-vibrant/
ODIN was finicky but eventually recognized my phone on COM Port 4. With the appropriate PIT and PDA loaded, I clicked Start and all the files uploaded. The phone restarts and.. stuck at Vibrant again. ODIN even lights up with a green PASS but I've let the phone sit and sit and it never gets anywhere.
Is this thing a total dud? Granted I'm trying to boot without a SIM card in it but I didn't think that would make a difference. Please, someone help. I'm stumped and annoyed.
Tried following this guide as well. Same problem. I'm definitely frustrated.
http://forum.cyanogenmod.com/topic/6998-howto-recover-from-a-soft-brick-on-your-vibrant/
I'm having this same problem, any info would be nice. I've actually tried several different guides online and none have worked for me, I can never get past the bootloader screen.
Also, I have been unable to find the file to install CWR, so I have no backup. I know my phone isn't bricked because I can install different modems and such but nothing is working to get it back up and working.
Make sure you've got the right files. Grab the ones out of the noob guide just to be sure
Sent from my SGH-T959 using XDA App
Yep, same problem. I can't seem to get into recovery either. Or connect to ADB to reboot into recovery. I'm tearing my damn hair out over this.
I tried ODIN flashing the Froyo No-Brick ROM for the hell of it cuz I read it fixed this issue as a last ditch for some people. No dice. Boots to the Vibrant screen for a second, then Vibrant switches to Galaxy S and it just sits there.
If no one has any ideas soon, I'm just going to say screw it. Pretty bummed - I've been on a G1 forever and was excited to use an Android phone that doesn't totally suck.
Wrrryyy said:
I tried ODIN flashing the Froyo No-Brick ROM for the hell of it cuz I read it fixed this issue as a last ditch for some people. No dice. Boots to the Vibrant screen for a second, then Vibrant switches to Galaxy S and it just sits there.
If no one has any ideas soon, I'm just going to say screw it. Pretty bummed - I've been on a G1 forever and was excited to use an Android phone that doesn't totally suck.
Click to expand...
Click to collapse
Go into the Developers section and look at the 2nd or 3rd post "Bay_wolf's AIO Vibrant Toolbox 2.5" . Download that into your computer and run 'Flash to Stock'.
That should help you get to where you need to go. Try the one click method first.
PM sent to Wrrryyy
Thanks for the advice guys, but still no go. Installed the drivers from the toolkit but all I can still do is use ODIN to try and flash stock. Results are exactly the same. Reboot into recovery still isn't working - I have a feeling USB debugging was not enabled on this phone before any of this happened so I'm screwed in that respect.
Keep trying, it's not bricked, one combination of files has to work for you.
Well there's only so many files I can apparently try. I've tried JFD, JI6, Eugene No-Brick.. Is there anything else I should trying flashing with ODIN?
Take out your sim card and microSD card. Download the appropriate stock JFD files, make sure you check repartition; you should be fine. USB debugging box not being checked before has nothing to do with your problem now. I believe either your partition or your bootloasder is screwy. Follow my steps above and you should be ok.
In fact, look at this and follow it to the T.
http://forum.xda-developers.com/showthread.php?t=848737
That's what I've tried probably 30 times by now. Repartition checked and unchecked. And yeah I know USB debugging doesn't have to do with ODIN, it's why I'm assuming I can't get ADB to recognize the phone so I could at least try "adb reboot recovery".
Outside of flashing JFD, JI6, or Eugene's No-Brick, is there anything else I could try?
Wrrryyy said:
That's what I've tried probably 30 times by now. Repartition checked and unchecked. And yeah I know USB debugging doesn't have to do with ODIN, it's why I'm assuming I can't get ADB to recognize the phone so I could at least try "adb reboot recovery".
Outside of flashing JFD, JI6, or Eugene's No-Brick, is there anything else I could try?
Click to expand...
Click to collapse
Try eBay
Sent from my T959 using XDA App
I'm in the same boat, same scenario with constant boot loop. This is my girlfriends phone too
IA-32e said:
I'm in the same boat, same scenario with constant boot loop. This is my girlfriends phone too
Click to expand...
Click to collapse
Look for a new girlfriend on ebay
djquick said:
Look for a new girlfriend on ebay
Click to expand...
Click to collapse
Haha no Craigslist I ended up having her file a claim and send it back. I must have borked the bootloader somehow cause now it wont turn on at all. Thank God for insurance. She's SUPER pissed though.
Compared to my Galaxy SII this phone is very finicky and ODIN is even more unreliable than normal. Never hard bricked a device before.
Picked up a G2 practically new for $100. Loving it so far - rooting process was a snap.
F this Vibrant. Back to Craigslist it goes. Still open to ideas before it's gone so I can attempt to get my money back, lol.
Wrrryyy said:
Picked up a G2 practically new for $100. Loving it so far - rooting process was a snap.
F this Vibrant. Back to Craigslist it goes. Still open to ideas before it's gone so I can attempt to get my money back, lol.
Click to expand...
Click to collapse
The only thing I see that will fix the Vibrant when it's in this state is JTAG brick repair for $50. This is after spending 12 hours searching and attempting to ODIN different stock firmwares till I finally hard bricked it.
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-4g-vibrant-4g-jtag-brick-repair/
Yeah I was considering this. I e-mailed the guy asking if it was an appropriate fix. I figure, if the service takes care of a hard brick, it can certainly take care of a soft brick. Maybe I'll do that to keep it around as a back-up phone. Thanks for the replies, everyone.