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 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
I am not necessarily a noob at this because I did a lot of this stuff on my old HTC Aria. But I was trying to unlock my BL doing 2.3.4 steps on 2.3.6 and I managed to get this error:
Code:
SVF: 105:1:2
Failed to boot 0x1000
No OS detected, going to RSD mode in 5 seconds
Press a key to stop count down
Availible modes are:
1 RSD
2 Fastboot
3 NvFlash
4 BP HW Bypass RSD
5 BP HW Bypass QC DLOAD
6 BP HW Diag & Boot AP
7 BP HW Bypass BP Only
8 BP SW Bypass RSD
9 Android Recovery (NO BP)
Vol up to select, vol down for next choice.
Now I think what happened was that I didn't have my phone USB plug plugged into the back port instead I had it in the front one and caused it to fail.
Does anyone know if it's possible to save my phone, and if so what I could do to unlock boot loader for 2.3.6 or 4.5.141.
[EDIT] I forgot to do the fastboot oem unlock which resolved this issue. Phone says unlocked and everything!
[EDIT] I forgot to do the fastboot oem unlock which resolved this issue. Phone says unlocked and everything!
i got the same problem u used the automatic unlock program.......my phone wont get detected my computer am using a laptop ////
I have a question. My friend has a Atrix 4G and I think He soft Bricked it. I took a look at it and I turns on then shows :
SVF: 105:1:2
Failed to boot 0x1000
then says something about svflash or etc and turns off right then and there. is there any way to fix this?
AZNSNSAZN said:
I have a question. My friend has a Atrix 4G and I think He soft Bricked it. I took a look at it and I turns on then shows :
SVF: 105:1:2
Failed to boot 0x1000
then says something about svflash or etc and turns off right then and there. is there any way to fix this?
Click to expand...
Click to collapse
Looks like a hard brick. What did your friend do exactly? What firmware version he had and if he had tried to flash a SBF, what is the version of the SBF?
Share some more details so that we can narrow down on the problem.
To begin with, I was trying to unlock Lg sp200 tribute dynasty phone , I was told that flashing lg k8 plus x210mula firmware will do it. Everything went well during flashing process using chip erase command on lg up software until it didn't.
The phone stuck in lg k8 plus logo, at first I went to download mode but then I tride hard reset way by using recovery method but everything went bad after that. I had been stuck at black screen since then with a message saying [LGE] [Image Recovery] op_image : 0 API Support : 3 and no ability to go back to download mode .
When plugged in, the phone was recognized by the computer for a few seconds beep and then disconnected after the message appears.
I tried lg up, lg flash tool and even plugging without battery using volume up method to get into download mode but no luck.
Now I need a powerful tool to get back to download mode to flash new firmware that I got recently.
hi
i too have a bricked lg phone mine is a fortune 2 lmx210ma. i was trying to flash a tecknight rom and when it erased the partitions it went dead and never came back. is there a way to fix this?
WaleedHAA said:
To begin with, I was trying to unlock Lg sp200 tribute dynasty phone , I was told that flashing lg k8 plus x210mula firmware will do it. Everything went well during flashing process using chip erase command on lg up software until it didn't.
The phone stuck in lg k8 plus logo, at first I went to download mode but then I tride hard reset way by using recovery method but everything went bad after that. I had been stuck at black screen since then with a message saying [LGE] [Image Recovery] op_image : 0 API Support : 3 and no ability to go back to download mode .
When plugged in, the phone was recognized by the computer for a few seconds beep and then disconnected after the message appears.
I tried lg up, lg flash tool and even plugging without battery using volume up method to get into download mode but no luck.
Now I need a powerful tool to get back to download mode to flash new firmware that I got recently.
Click to expand...
Click to collapse
Got a queation. Have you plugged your phone into a pc mac or linux machine to see if it registers. It being a qcom device it might show up as hsusb 9008 or qdl mode. If so you might be in the same boat as me. If it is check out QPST or QDL on linux and do some research. Im going to try to use qdl to revive my fortune2.
Worthy to note before attempting any kind of drastic procedure like exchange of firmware do extra research and make sure device hardware is compatible with the firmware you are trying to flash.
Some phones like the LG LMX210 variants called CV1 are pretty much interchangeable running the same hardwares. But there are a couple like my ulma that run mtk. Flashing mtk with qcom or vice-versa cause really bad. Thats not what i did i was just tired and wasnt paying attention to my procedure list and well you know it happens.
I am currently trying to install LineageOS on my phone. I personally have never unlocked or reinstalled a new operating system on my phone. I looked on some XDA forums for some guides and i found one and followed the steps. I unlocked my phone and I installed a custom TWRP because I was trying to downgrade the phone back to android 11. Once i was done flashing the file to the phone and rebooted it doesn't boot anymore and only gives me a booting screen for a few seconds after I hold down the power and volume up button for a few seconds nothing else works. I have use the MSM tool and put my phone into EDL mode and it detected the phone with a black screen. Every time I use the tool it works till about 18% then it gives me a Sahara communication failed error and then my phone gets out of EDL mode.. I installed all the drivers needed on my PC and used multiple USB 2.0 slots but it still fails. Any help would be appreciated.
There are warnings in the TWRP thread for the N200 that it is broken and should not be flashed.
I have written an easy to follow guide here to downgrade to A11 with Fastboot Enhance.
Unfortunately, now that you have used MSMTool on the phone, it is now bootloader LOCKED. This tool should be the last resort only if you are already hard bricked. You could have gotten the phone into fastboot if either boot.img was still intact and re-flashed the rom with a still unlocked bootloader. The phone will change slots after so many failed boots.
Now that your boot loader is locked, the only tool that can modify the phone is MSMTool. If you can get into Recovery, do delete user data and try again.
Otherwise, you will need to get an RMA and send phone back to OP.
scanman0 said:
There are warnings in the TWRP thread for the N200 that it is broken and should not be flashed.
I have written an easy to follow guide here to downgrade to A11 with Fastboot Enhance.
Unfortunately, now that you have used MSMTool on the phone, it is now bootloader LOCKED. This tool should be the last resort only if you are already hard bricked. You could have gotten the phone into fastboot if either boot.img was still intact and re-flashed the rom with a still unlocked bootloader. The phone will change slots after so many failed boots.
Now that your boot loader is locked, the only tool that can modify the phone is MSMTool. If you can get into Recovery, do delete user data and try again.
Otherwise, you will need to get an RMA and send phone back to OP.
Click to expand...
Click to collapse
Sorry I should have written more details but I currently have a hard bricked device. It will not boot and It failed to boot like 20 times. It will not enter fastboot or even get past the logo when you first turn it on. I did use MSM tool after it wasn't letting me into fastboot. Thanks for the help and I will send it back.
z67gp said:
Sorry I should have written more details but I currently have a hard bricked device. It will not boot and It failed to boot like 20 times. It will not enter fastboot or even get past the logo when you first turn it on. I did use MSM tool after it wasn't letting me into fastboot. Thanks for the help and I will send it back.
Click to expand...
Click to collapse
Fix Sahara communication failed error in MSM Download Tool
In this tutorial, we will show you how to fix the Sahara communication failed and other related MSM Download Tool errors.
www.droidwin.com