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
Related
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
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.
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?
hello XDA forums, I'm not really too good at computers, and would need some help in unbricking my TF201
yes, im silly. I Should of known more about rooting and unlocking, blah blah blah
The device is unlocked and running the latest stock firmware, unlocked.
I tried flashing the recovery with ClockWorkMod, but i open recovery and it just freezes
then i installed goomanager, and think i accidentally hit flash/ boot to recovery or something like that
> next thing, it booted
frozen on the screen saying that 'the device is unlocked' and has the asus logo, is just stick on that.
nothing changes in device manager when its plugged in.
tried holding VOLDOWN + Power
= no luck, still doing the same thing
You say you're not too good with computers yet you're attempting very advanced operations on one. Can't help ya with the brick but may I suggest a much higher dose of caution in the future.
Sent from my Transformer Prime TF201 using XDA Premium App
I hope that when you say you're unlocked you mean that you have nvflash access. If so, this guide should help you out:
http://forum.xda-developers.com/showthread.php?t=1927818
Oh,, and there's only one way to "get good with computers", and that's getting your hands dirty. So don't not do stuff because you're scared, just be careful while you do.
If you didn't use Nvflash, you're hard bricked like hundreds of others, including me. Nothing you can do. RMA.
Hello all!
First of all, I am no developer.
Long story short.. I purchased an HTC 10 because I was sick and tired of my at&t galaxy s5 being bootlocked. I received the 10 and set out the next day to root it. I followed a video on youtube (not saying that the info was not correct...I may have done something wrong...not trying to discredit anybody) to the letter and lo and behold I ended up in a bootloop. My heart probably came close to a complete blockage at this point. This bootloop lasted maybe a minute before it would reboot. So... In my infinite wisdom I chose to relock the bootloader. Oh Boy!!! Fun times were ahead for me!! As soon as I relocked said bootloader, the bootloop increased its timing to about 1 point 5 seconds. I remember waking up on the floor in the fetal position. Now I am stuck with a phone that adb will not recognize. It does however recognize the device at the fastboot devices prompt. So my question is this.... Is this a salvageable phone? If so, How would one go about fixing this problem?
*** Relocked ***
htc_pmew1 pvt S-ON
os-2.28.617.8
I would prefer that the money I spent on this thing would amount to something more than a small ant bed.
Any help at all would be greatly appreciated. Also I have been doing a lot of digging around and (I may be wrong) but. I could not find this scenario in the forums here. I apologize if this has already been covered.
...So..after looking around for a bit more, I discovered out that there is a way to flash a ruu/zip from an sd card. I have tried multiple times with what I thought were the right ones. As I am unable to boot into recovery, I feel I am limited as to what I should do. I have read about that I should wipe dalvik but I am very limited in my knowledge on an android system and would prefer to not mess this phone up anymore than it already is. I was trying to root and I used TWRP as the recovery but I never made it to the end before it started the loop. The Phone is an htc 10 unlocked version. and it just constantly reboots about 3 seconds apart. ADB says no device connected, so I cannot execute commands that way... really at a loss here. all the tutorials I have read refer to using and and being able to boot into rrecovery. when i boot into recovery, I get an immediate reboot and the 3 second bootloop forever. Is there a way to use twrp to somehow resolve this?Is there a tool that will help me at least get into recovery mode?
SOLVED... Ran across Batchtool by sneakyghost. Quite the bunch of tools there! Ended up solving my problem by placing the stock RUU in the root folder as the batch tool. Before I could not install from a factory RUU (would not recognize the phone through ADB or install the RUU. After the install of the batch tool I was able to get a clean install back to my factory settings.. Now I am free to mess it up again!!
BIG THANKS TO SNEAKYGHOST!!!!!
I'm unsure why the batch tool has worked for you and the sdcard method didn't - getting fastboot to work and all the bits and pieces together (drivers, Windows VCRedist, correct fastboot, correct adb) is usually more error prone than just identifying the correct zip and placing that in your sdcard root.
At this time, I'm a bit in a "scratch my head" mood, thinking this is weird. Same zip? Really the same zip didn't work from sdcard but would work in fastboot? I think I haven't come across that myself yet (non booting phones are a daily thing, almost).
I wish I had the time to analyze your steps with you, so I could gain understanding as to why that happened, so I can use that in the future, but alas! I have no time for XDA and deep digging around in issues of other people. Lately I can't even solve my own phone's problems anymore due to too many other things going on.
Well, glad it worked for your phone, anyhow. I'll keep this in mind for the next one messing up his/her phone.