hey guys I currently have a captivate and my upgrade is due on the 24th. As some of you may know the captivate is almost unbrickable (usb jig) and I am looking to try all different kinds of ROMs.
My Question is how brickable is the Atrix? I read that you can recover from a soft brick, but how about a hard brick (is it possible)?
Thanks and sorry for re-post if this has already been asked but I couldn't find an answer.
The Atrix is similar in that we have Motorola SBF files if you bork your phone (soft brick).
Related
Unfortunately, my Canadian Bell Vibrant bricked when i was listening to music (seriously dont know how that happened). After doing some searching on this forum, i found it was just a soft brick which can be fixed either with recovery mode or Odin. For some reason, since the brick, my recovery mode has been disable, however, the download mode still works (yay). After reading about all the warnings of using Odin, i decided to make sure everything was ok before taking the plunge.
Will the Odin files posted for the Tmobile T959 work on my Canadian Bell Vibrant (i dont want my soft brick to turn into permanent)?
Is Odinv1.000 or Odin1.3 more reliable? ive heard of it bricking phones and without my recovery mode... im kinda hesitant to do it.
Lastly, does anyone know a safer way to get my phone fixed? My phone was unlocked and rooted prior to bricking so im guessing theres no way to get the company to completely fix it. Well, i guess i could act stupid and get them to look at it?
What do people normally do with phone bricked due to tampering with firmware?
Ive seen the video tutorial for Odin and it looks fool proof so i really want to try it.
Any help with this would be great
bump
It would be great if someone could help me out
Hey there,
I read on many threads here and on other sites that if your vibrant doesnt access recovery when pressing the volume buttons(both of them) and the power one together then your device is hardware locked, so apparently mine is since I've been trying to do just that for hours and miserably failed despite even viewing vids about the exact way in doing so.
Now back to my question, Im updating my vibrant to froyo (or intended to anyway) then came across many topics suggesting that updating the vibrant through kies (what I was about to use) would brick my phone. Is that true? Or is it just idiocy rumors and Im good to go. Please answer me ASAP I freaked out when I read that and immediately unplugged my vibrant but don't worry kies was only in download mode as in downloading the update from the internet not into my precious vibrant
Wow, I certainly didn't expect ut to be that impossible of a question.
Some people have had issues, a lot with your story (hardware locked, never rooted or flash a custom rom). There is a way to enable the three button recovery and I believe that you can get into download mode without it, so there's always an option if it does brick your phone.
Actually, from what I read, the only way to un-brick a bricked phone is by rooting it and going to recovery which would involve the three buttons procedure. So if Im to rely on that option I have to find a way to unlock my hardware first before installing the update not after it as there's no way to do so after that.
In any case, it would be really helpful if you provide me with the way (or link) to how hardware unlock a vibrant. As you seem to agree with the say that a hardware locked phone will be bricked.
Well it looks like my Vibrant is actually rooted since I have the Rom Manager running safe and sound and the icon android superuser permission icon in the apps. I just backed up my data on the SD via Rom manager.
Now the new question is; does this mean that I have nothing to fear when/if I update my device? Please guys, help me with this as Im a noob really and can't make up my mind as I need the update to help me browse arabic sites but yet Im afraid this would end up bricking my phone.
Remove battery, plug in usb to pc, then put in battery while holding volume buttons. If you can get to download mode then you're pretty much unbrickable. If not there's the option of a jig you can make or buy if you want that can get you into dl mode. The way to enable the three button combo should be easy to find, Ill search for it when I get home.
http://forum.xda-developers.com/showthread.php?t=804305
Ok so i had an atrix. And it had gingerbread. But my screen cracked so i got a galaxy s 2. I kept my atrix and saw the cm9 rom. Tried ut. Awesome great dev work. My friend tried to get ittoo
I had put gingerbread kn his atrix. But he messed up. Yried to update recovery or something but errored out. And now its bricked. He wants me to fix it since i know more. So all i can do thus far is get the rsd protocol thing. But i cant scroll to recovery or anything. Im at work now so i cant do anything for another 5 hours. I just haven't been in this thread in a while so i was wondering what the community thought. Thanks for all the help.
If you can't enter on fastboot, you have a hard brick. But if you can enter in fastboot, it's only a soft brick, in this case you can reflash a recovery from you pc. Try romracer recovery. I hope that be only a soft brick.
yeah i figured it out, thanks a lot for the help
Hi guys,
I've started joining the android tinkering world and have recently acquired a bricked atrix as a hobby. I have poured over the sticky posted in the Atrix Devs part of the forums (and many other threads) for sometime now. I can't find an answer and I'm now stuck in my tinkering. And there seems to be no complete consensus if there is any way to fix a bricked atrix. My atrix does have the same error message of
SVF:105:1:2
Failed to boot 0x1000
Entering NVFlash Recovery Mode
Battery is too low to flash
My own currents attempts have been to create a factory cable, which allowed me to successfully connect to my computer. The drivers recognize that the phone is connected, but when I run NVFlash and do a test command --sync, I get the error:
USB failed to write
So from what I have gathered, Motorola has not released the SBK for the atrix so I cannot flash through this method correct? Is there anything I can do from here, or possibly a different method? Or is this phone simply hard bricked?
Simply hardbricked... Read around the forum. Its posted in many places. You cannot recover a hard brick.
yep. Sorry dude. It doesn't help that the term "brick" is used for so many different failed-to-boot states, but the Unrecoverable Hard Brick is when NVFlash is your only boot option for exactly the reason you stated -- we don't have the SBK from motorola.
(If you have access to any other options, like fastboot or RSD, that's a "soft brick" and it's possible to recover.)
Alright thanks for the help and clarification guys.
But yeah I did look around the forums quite a bit. Its just the information is never quite clear with all the people posting and whatnot.
If bootloader is unlocked you shouldn't have a problem. Try unlocking bootloader again.
Sent from my MB860 using xda premium
Can I still access the bootloader while my phone is bricked? I can't access RSD to start unlocking the bootloader or any other options when I turn on my phone.
yeah it's borked forever. sorry
Alright that's what I thought. I don't mind so much since my main phone is an HTC Sensation. I just started getting interested in tinkering around with phones and learning more. So I'll probably just resell this on ebay or something and take a slight loss in cash.
Did learn a lot from this venture though
as title,i had tried to flash using speedmod,hydra but still no hope
N7000 rm on an AT&T Note will brick your phone.
And it likely already has. ..
OP. ...you will need a JTAG repair for the device.
Very sorry, but insufficient research has caused you to kill your device.
Im surprised that you did this after being a member here for nearly 2 years, but I suppose that bad sh** happens to everyone at some point.
Flashing of that rom has deleted your partitions, and removed your boot partition and download mode. USB function is gone as well.
Ranger got it. ...your phone is hard bricked.
Search for "JTAG" repair in the search box.....g