I have started to follow the process to Unlock/root my atrix phone found here
http://forum.xda-developers.com/showpost.php?p=15989846&postcount=1
But after the first step I used RSD and flashed my rom and Now I get Bootloader error and I am able to select a new way of booting my phone (ie RSD, Fastboot, NvFlash, BP HW Bypass RSD...... BP Tools)
If I try android recovery I get the error Magic Value Mismatch.
What Should I do?
Is my Phone Hard Bricked?
Here is a little more information about what I did:
I tried to use this website:
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
to unlock my bootloader and I ran into an error when I typed "fastboot oem unlock"
and it seemed that people didn't understand how to fix that error. So I then surffed forums to find information.
I ran into this post by Clear-Fire:
http://forum.xda-developers.com/archive/index.php/t-1221042.html
where he says "well you should try and flash Download ATT 2.3.4 pudding+root here (http://www.multiupload.com/C0I82IXH7V) through RSDLite 5.3.1 link (http://forum.xda-developers.com/attachment.php?attachmentid=634879&d=1308872277)"
Then That leads me to today.
Answer.
If you are seeing the different
ways to start the phone your phone is not bricked it is only "soft Bricked" meaning we can fix it.
Go to the following forum and download the application and run it on your computer: it has a way to fix the soft brick and then unlock your phone.
http://forum.xda-developers.com/showthread.php?t=1182871
Related
Hello, First time Poster here, please bare with me...
I really shouldn't of touched this.....
I have an Atrix w/ the newest updates to it, and attempted to unlock the phone. Using the guide from atrix4ghacks.com Everything started well, then it failed while writing to the device. Now, when I attempt to boot, I get the message
SVF:405;1:2
Failed to boot 0x1000
1- RSD
2-Fastboot
3-NVflash
4- BP HW Bypass RSD
5-BP HW Bypass QC DLOAD
6-BP HW Bypass & Boot AP
7-BP HW Bypass BP only
8- BP SW Bypass RSD
9- Andriod recovery
10- Boot Andriod (no BP)
11- Device UID
12- Console
13- Early USB
14- BP tools
I can get into fastboot, though I honestly am not sure what to do from there. I have the fastboot s/w downloaded, along with the gingerbread OS. When I tried to execute the command via Command prompt. I keep getting unknown command errors (yes, directories within the command are good).
Did I just kill my phone?
I have found a few posts here related to this, though I havent found what seems to be a solid answer to a "fix" for this. I would highly appreciate if someone could try to help me with this.
Sorry, I have broken a noob rule (was pretty late when I watched the video), I thank you all in advanced for any help
STOP!!! YOU HAVEN"T KILLED YOUR PHONE JUST YET!
BUT IF YOU SBF YOU WILL!!!
Go into fastboot and repeat all of the unlock commands, reboot and your phone should boot fine after that.
Ok, I will give that a shot!
Hopefully this will work. THANK YOU!
Ok, is there a way to force charge this?
I had it hooked up and when I was going to execute the flash, it gave the message of battery too low to flash.... Will just leaving it plugged in be ok? or is there a button function I can do that will ensure it charges the unit?
Thanks again
Grumbles said:
Ok, is there a way to force charge this?
I had it hooked up and when I was going to execute the flash, it gave the message of battery too low to flash.... Will just leaving it plugged in be ok? or is there a button function I can do that will ensure it charges the unit?
Thanks again
Click to expand...
Click to collapse
Ugh... from what I heard the battery won't charge while in fastboot mode. You need a standalone charger or a different battery.
So, it doesn't let you get into fastboot at all, huh?
I was afraid of that- I think ive found the solution to that on this link:
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html
That is def. something I can do, and will try. Otherwise, to answer your question. The PC sees the device- It is then the device that says battery is too low to flash (on any mode you choose). Once that message is shown, it wont allow me to access it at all.
Worse to worse, I will take a trip to the att store, or somewhere close to see if they have a wall or base charger. If the doc has a separate power connector, I may try that...
Grumbles said:
I was afraid of that- I think ive found the solution to that on this link:
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html
That is def. something I can do, and will try. Otherwise, to answer your question. The PC sees the device- It is then the device that says battery is too low to flash (on any mode you choose). Once that message is shown, it wont allow me to access it at all.
Worse to worse, I will take a trip to the att store, or somewhere close to see if they have a wall or base charger. If the doc has a separate power connector, I may try that...
Click to expand...
Click to collapse
The factory cable would allow you to use the phone without the battery, but it might take more money and time to make then you think.
From what I understand, RSD threw you an error when you were flashing bootloader unlock.
Anyway, you need to find a way to charge your battery and they do the fastboot unlock commands.
If that doesn't work you need to reflash the pudding SBF, (make sure you install the drivers Windows x64 version here prior to flashing and that your phone is recognized in RSDlited)
Get the correct pudding file from here: http://forum.xda-developers.com/showthread.php?t=1136261
Use instructions here (start at step 1) : http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
Note that after pudding is flashed successfully and you do the unlock commands, you will get a failed to boot error (seems like what you have now). You need to redo the unlock commands in fastboot and it will fix the problem.
Good luck.!
Alright!
Got the cable completed and works!
So, battery situation is handled, now to follow your steps
THANK YOU! I will report back and let you know.
Ok,
Clearly I am doing something wrong here.....
I followed the instructions using the newest Pudding_preroot.sbf file, and the RSD software sees the device (as a SE flash not a NS if that matters) and will start the flashing process.
Everything works to plan until the phone does its reboot(99$ executed), gives the fail to boot message again. Then wants to start back up in RSD mode.... The RSD application on the otherhand, it seems like its trying to switch the phone to"BP passthrough mode" I do not see that exact option, and after it failed while rebooting to RSD. I tried to move it to fastboot, BP HW Bypass RSD, and finally BP SW bypass RSD... All with the same failure on the RSD screen:
"Failed Flashing Process. Phone (0000): Error switching to BP Pass through mode (0x70BE); phone connected"
I have a funny feeling that this part is obvious, for that I am sorry for my ignorance.
I am pretty sure this thing is toast...
After getting nowhere after step 12, and multiple attempts to install the pudding_preroot file. I did some searching around and found multiple atrix users that would get the same issues. From the flash showing up as SE rather than NE, to the constant failing during the flash via RSD lite, with the same failure errors.
I noticed a "NV flash" option, and found this link that could establish a recovery USB driver to the phone. Do you think this maybe my next best route?
http://forum.xda-developers.com/showthread.php?t=1123429
My factory cable is good, so that option IS open..... Though I am starting to think this is toast.
We cannot use NVFlash unless we get the SBK (signature file). Currently, we do not have it. Motorola does, so plead to them
OK, well now it decided to only mount itself as a unknown APX device... Not sure the whats or whys there. Nothing has changed since the last failures?
Hey man, I think RSD shows the flashing process as failed since it can't fully reboot the phone.
Go into fastboot mode and try doing the unlock commands. (try this twice if ita fails after the first time).
In the worst case scenario if unlocking fails no matter what, you can flash a complete 2.3.4 rom via SBF and that should get you back up and running.
Let us know how it goes.
Remember, if you can get into RSD or fastboot - the phone isn't bricked yet!
I was trying to unlock the BL in my Atrix via Fastboot OEM Unlock, and when that failed I moved on to other, more complicated methods including RSD Lite 5.5 and sbf flashing.
Now when I power up my Atrix I get no logo, just "failed to boot 0x1000
No OS detected, going to RSD mode in 5 seconds."
And literally everything I do will not work. Fastboot does nothing. RSD fails everything, says "Unable to retrieve interface handle (0x7027); phone connected"
When I connect in RSD Mode now, my Atrix shows up as SE Flash Olympus under the Model column, as it did before, rather than the typical NS Flash Olympus.
I'm trying to flash the full 4.5.91 sbf from the IHOP thread that includes an unlocked BL, but it keeps failing.
Edit: It gets to 99% And then says "Switching phone to BP Passthrough mode," but my phone still fails to boot (0x1000) and I have to pick what mode to put it in. I see now it's not BP HW Bypass RSD. Does anyone know?
Did you try to pull the battery and then boot into fastboot (Hold Vol down & Power) and then issue the unlock commands?
Mecharuva said:
I was trying to unlock the BL in my Atrix via Fastboot OEM Unlock, and when that failed I moved on to other, more complicated methods including RSD Lite 5.5 and sbf flashing.
Now when I power up my Atrix I get no logo, just "failed to boot 0x1000
No OS detected, going to RSD mode in 5 seconds."
And literally everything I do will not work. Fastboot does nothing. RSD fails everything, says "Unable to retrieve interface handle (0x7027); phone connected"
When I connect in RSD Mode now, my Atrix shows up as SE Flash Olympus under the Model column, as it did before, rather than the typical NS Flash Olympus.
I'm trying to flash the full 4.5.91 sbf from the IHOP thread that includes an unlocked BL, but it keeps failing.
Click to expand...
Click to collapse
Of course, that's the first thing I did. If it had worked, I wouldn't have a bricked Atrix now. I read somewhere else here on XDA that if your Atrix shows up as "SE" in RSDLite, rather than "NS," you have an Atrix that ATT used to use for testing and support. Not sure how correct that is, but it's possible, considering this is a refurb I bought as a part of the ATT 3rd Party Reseller concession line program. (sub-$50 bill with Unlimited web ftw)
Edit: And now.. for whatever reason, fastboot oem unlock worked. But will my phone boot? It just pops up the M logo, with "Unlocked" in the upper corner. Doesn't appear to be doing anything though.
Edit 2: Now my Atrix shows up as NS in RSDLite. Perhaps there is hope. Flashing the full 4.5.91 sbf from the IHOP thread.
Edit 3: Worked. Now my Atrix is unbricked. Pardon my naivete.
That's quite alright. The only reason I asked is because for people who flash pudding on an Atrix that's already been updated to GB will encounter a "soft brick" in which they need to go through a separate procedure. That's all. Didn't mean to imply you didn't know what you were doing. Glad you got it working.
Mecharuva said:
Of course, that's the first thing I did. If it had worked, I wouldn't have a bricked Atrix now. I read somewhere else here on XDA that if your Atrix shows up as "SE" in RSDLite, rather than "NS," you have an Atrix that ATT used to use for testing and support. Not sure how correct that is, but it's possible, considering this is a refurb I bought as a part of the ATT 3rd Party Reseller concession line program. (sub-$50 bill with Unlimited web ftw)
Edit: And now.. for whatever reason, fastboot oem unlock worked. But will my phone boot? It just pops up the M logo, with "Unlocked" in the upper corner. Doesn't appear to be doing anything though.
Edit 2: Now my Atrix shows up as NS in RSDLite. Perhaps there is hope. Flashing the full 4.5.91 sbf from the IHOP thread.
Edit 3: Worked. Now my Atrix is unbricked. Pardon my naivete.
Click to expand...
Click to collapse
Of course, thanks live.
I was tried to unlock bootloader but after my phone showe there is no os detected i scared and luged my phone out then i got soft brick. I tried to recover it by this guide http://forum.xda-developers.com/showthread.php?t=991072 but after first step of rsd lite flashing i got hard brick/ RSD lite showed that it is turning my phone to BP by pass mode but then it showed error turning phone to BP by pass mode and stoped flashing after that my phone is hard brick. What can i do? please help
Can i send it to AT&T service to repair or change it i bought it from ebay two days ago.
Is your phone an international (non-US) model?
When your phone boots up, and you see the "Failed to boot" message at the top: Does it say "Entering NVFlash mode" quickly before shutting back down, or do you have a list of other options below?
brick?
RSD Lite seem connected? see if you still have a chance to heal: (
it is us model
It is not connect to rsd. When it turns on it shows nvflash mode. I asm searching a way to write a true script to install rom via nvflash by using nvidia apx drivers from lg tegra devices.
Could anyone help me with this. I am sure it is able to recover via nvflash and this wat is not published by motorola or nvidia. Because on another tegra device i use nvflash recover easily. It is verybig problem. Who will use motorola devices after that .....
I just bought a motorola atrix 4g manufacturer refurbrished from US and i want to use custom ice cream rom on it, i've managed to root the phone following the commands in the previous threads. But i'm unable to unlcock the bootloader, i've tried all methods founds here. The phone is running on 2.3.6 Gingerbread 4.5.141.MB860.ATT.en.US. I'm unable to use android recovery as well as Customrom recovery either, the error i get is 'fail to boot 2'......I flashed back to stock with SBF 2.3.6, 4.5.141 and had no fix with wifi/bluetooth bugs.
I'm unable to use wifi/bluetooth, i get wifi error and bluetooth fails to switch on and whenever i try to switch on wifi the phone restarts.
mulfty said:
I just bought a motorola atrix 4g manufacturer refurbrished from US and i want to use custom ice cream rom on it, i've managed to root the phone following the commands in the previous threads. But i'm unable to unlcock the bootloader, i've tried all methods founds here. The phone is running on 2.3.6 Gingerbread 4.5.141.MB860.ATT.en.US. I'm unable to use android recovery as well as Customrom recovery either, the error i get is 'fail to boot 2'......I flashed back to stock with SBF 2.3.6, 4.5.141 and had no fix with wifi/bluetooth bugs.
I'm unable to use wifi/bluetooth, i get wifi error and bluetooth fails to switch on and whenever i try to switch on wifi the phone restarts.
Click to expand...
Click to collapse
You may have an unlockable bootloader.
Your wifi / BT are on the same chip. If the chip gets damaged, neither works.
I sell phones on Ebay and have worked on a few atrix phones.
1. The wifi/bt chip is burned out, it cannot be fixed only by replacing the whole motherboard. Has it been this way since you bought it? If so then the seller screwed you.
2. This is the way I personally BL unlock atrix phones:
A. Boot into RSD
B. Flash "4547-fix-try2.sbf" using RSD lite 5.7
Note this will soft brick your phone. You will get an error like 0x000 don't freak out, it will ask you what to boot into, RSD or what, choose fastboot.
C. Open a command prompt and navigate to your adb and fastboot files. Make sure your device is listed under "fastboot devices" then "fastboot oem unlock" This will return a string of characters. Next retype that character code "fastboot oem unlock XXXXXXXXXXXXXXXXXXXXXXXXX"
D. If you did it right it will say your bootloader is now unlocked.
E. Next "fastboot flash recovery recovery.img"
Where recovery.img is a flashable recovery CWM or TWRP (I prefer TWRP because it's touch based)
These instructions assume you understand how to use RSD lite and fastboot. You can find other similar methods on the forums.
after flashing 1FF-sunfire-user-2.3.5-4.5.1A_SUN_USC_19.0-19-release-keys-signed-USC-US i get failed to boot 4
tried http://androidforums.com/4545287-post3.html with no rezult
tried to flash SBF: 1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-154_5-CM-release-keys-signed-Sprint-US , rds lite 5.6 writes - waiting for re-enumeration,
phone writes - svf : 106:1:2 sec_exeption: b655, eddc, eb
plus nothing hepens when i try to power on phone with vol-, vol+ and both keys
i have already delete rsd and drivers and reinstall them
please help me
you cant flash 2.3.4 on a phone with 2.3.5. it does not work. not sure where to start but can you get to fastboot or rsd mode?
---------- Post added at 07:59 PM ---------- Previous post was at 07:49 PM ----------
also was your bootloader unlocked? any customizations at al re.....recovery or rom etc....can you give a lttle more info.
If I understand correctly you are no longer able to get to rsd mode (power and vol +) when booting correct? If so you are pretty much S.O.L. When you flashed the 2.3.4 sbf it tried to revert your locked bootloader back to 2.3.4 which is a no-no on a locked 2.3.5. Your best bet is to start coming up with a good excuse and take it back to sprint.
Truely need more info. I just a week ago did the same thing to an electrify. I at this time cant tell you the exact steps i took took fix it but it can be fixed. You are not completly screw as of yet and if you look around you will find all you need to fix this but it comes from different sources and some of the info was for different phones but worked on the photon which made it work on the electrify.
Like i said the given info is not enough to give you what you need to do and although the mopho and electrify are similar in almost every way there are a few things that differ.
I dont believe that your "S.O.L." because i just did the same thing and brought it back.
Open a command prompt as administrator and plug your phone into you computer and see if its recognized by fastboot or adb or rsd lite.
hoslayer13 was helping me with this issue and had a lot of info that helped. maybe he will chime in who knows.
More info!!!!!
After the phone says failed to boot 4 if you leave it at that screen for about a minute does it say "starting rsd mode" under failed to boot 4? If so your best bet would be to follow the steps here: (http://forum.xda-developers.com/showthread.php?t=1798145) as long as you originally started with a Photon running 2.3.5. I you can flash via rsd, make sure you remove your sd and sim card. For some reason it seams to work better. Also plug the USB cable directly to the computer (no hubs, no usb extension cables) they can cause issues with rsd. I hope you've already resolved the issue and I'm giving you advice you don't need.
@ rhewins2268. That is exactly the reason I asked "If I understand correctly you are no longer able to get to rsd mode (power and vol +) when booting correct?" If he can boot to rsd then the link I provided is a fix. Which by the looks of it may be what he was trying to do in the first place considering the electrify sbf he mentions is the first step in bringing a Photon back to stock, or back from a soft brick. You are correct more info would be helpful, but by reading what he did it sounds like more than likely he was on 2.3.5 which is an unlock-able bootloader (for the time being) and trying to downgrade (SBF: 1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-154_5-CM-release-keys-signed-Sprint-US) on a locked 2.3.5 bootloader can and more than likely will perma brick the photon. If when booting he can not see the boot options, i.e. fastboot, android recovery, rsd mode etc. he's bricked. There is no way to flash anything if the device has no, or a corrupted bootloader to start those processes.