Ok so I got this AT&T USA Atrix lastnight from craigslist, it was working fine and I tried to unlock it for T-Mobile. It's a model MB860
I looked for tutorials and see alot of outdated and confusing information, so I found one that instructed me to download RSD Lite and flash the phone with Pudding 4547-fix-try2.sbf. Well now the phone says
SVF:105:1:2
Failed to boot 0x0001
No OS Detected, going to RSD Mode in 5 seconds
Press a Key to stop count down
Available modes are:
1 RSD
2 Fastboot
3NvFlash
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
10 Boot Android (No BP)
11 Device UID
12 Console=tty50,115200n8
13 Early USB Enumeration
14 BP Tools
and when I tried to Boot Android No BP it says (Magic Value Mismatch) Reading ODM Fuse 1
So what do I do now? I hope I didnt brick this thing, I just spent $160 on it and now I have no phone. Can someone tell me how to restore this please? Thank You very much.
Phonebricker said:
Ok so I got this AT&T USA Atrix lastnight from craigslist, it was working fine and I tried to unlock it for T-Mobile. It's a model MB860
I looked for tutorials and see alot of outdated and confusing information, so I found one that instructed me to download RSD Lite and flash the phone with Pudding 4547-fix-try2.sbf. Well now the phone says
SVF:105:1:2
Failed to boot 0x0001
No OS Detected, going to RSD Mode in 5 seconds
Press a Key to stop count down
Available modes are:
1 RSD
2 Fastboot
3NvFlash
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
10 Boot Android (No BP)
11 Device UID
12 Console=tty50,115200n8
13 Early USB Enumeration
14 BP Tools
and when I tried to Boot Android No BP it says (Magic Value Mismatch) Reading ODM Fuse 1
So what do I do now? I hope I didnt brick this thing, I just spent $160 on it and now I have no phone. Can someone tell me how to restore this please? Thank You very much.
Click to expand...
Click to collapse
The unlock process you started is for the bootloader. Sounds like you wanted a carrier unlock.
Right now you just need to finish unlocking the bootloader. If you don't have drivers, fastboot, etc already set up then I would recommend just using the Automatic Unlock tool. There is an option (#3) that deals with your exact situation. Also, there are dozens of posts dealing with this issue. Searching for 'unlock bootloader', 'SVF:105:1:2', or 'No OS Detected, going to RSD Mode in 5 seconds' should get you plenty of good info.
Here is a quick rundown of what to do manually:
1. Boot into fastboot
2a. Issue command: fastboot oem unlock
2b. Take note of the OEM number it displays for your phone.
3. Issue same command, but this time add the # from step 2b: fastboot oem unlock #######
This should finish the unlock process. See the pudding thread for pictures of what to expect.
Thank You very much Ghost_OG, that worked! Now my problem is that the phone booted up, I inserted my tmobile sim and it asked for a code, so I booted into recovery mode to attempt to flash a rom and the recovery mode showed a Chinese symbol instead of the CM symbol, but I accidentally erased the data partition and now when I try to flash the gingerbread rom from a .zip file on my sd card, it says its unable to mount external sd. So now Im stuck. It mounts internal memory fine, but I cant access the internal memory with my pc to put the image on it to flash. Damn. This is all new to me, the last phone I flashed regularly was the Google G1, so that show you how long ago that was. What can I do?
Phonebricker said:
Thank You very much Ghost_OG, that worked! Now my problem is that the phone booted up, I inserted my tmobile sim and it asked for a code, so I booted into recovery mode to attempt to flash a rom and the recovery mode showed a Chinese symbol instead of the CM symbol, but I accidentally erased the data partition and now when I try to flash the gingerbread rom from a .zip file on my sd card, it says its unable to mount external sd. So now Im stuck. It mounts internal memory fine, but I cant access the internal memory with my pc to put the image on it to flash. Damn. This is all new to me, the last phone I flashed regularly was the Google G1, so that show you how long ago that was. What can I do?
Click to expand...
Click to collapse
Easy fix (now that you're unlocked).
First thing first, your recovery. I'm assuming you installed the recovery that came with the Auto Unlock tool? That is a very outdated recovery. I recommend using romracer's. You want to d/l the .img file, not the zip. Put the recovery-atrix5.img file in your Auto Unlock folder and open a command prompt from that same directory. Follow the instructions from that thread to install.
At this point you can see if both internal/external are available while in recovery. You may need to mount them from within the recovery program. If you're able to access either, put the your zip back on the card and try to re-flash the ROM. Make sure to follow all install instructions from the ROM thread as well.
DAMN DUDE! That worked! I wasnt sure what you meant about putting that romracer img file in the folder an opening a command prompt from within there and updating it that way, so instead I renamed romracer's img file to that old one that was already in there and the batch file flashed it for me. From there, I mounted internal usb storage, dropped my rom in there, and viola! Good lookin Out Brother! I'll drink a beer for you! Sending some good karma your way. I really appreciate it.
Would this fix my Boot Loop
So I'm guessing this would fix my Boot Loop Thanks Guys.... (I'm unlocked and have an old recovery image file....) but the $#!T I'm in now is that I can't flash the romRacer recovery img for the simple reason that My battery is to low so I can't go into fastboot lolol...... I'm going to order and external charger to charge this damn Battery...
Or is there another way for me to charge my battery... because from what I'm seeing my battery does not charge during this bootloop...... in a way I don't mind buying it... but I just don't want to wait....
Phonebricker said:
Thank You very much Ghost_OG, that worked!
Click to expand...
Click to collapse
I have the same problem..... but I cannot read Ghost_OG's answer .... how could I read it?
Related
I was following this video on instruction on unlocking my atrix on youtube titled "Motorola Atrix: Unlock and Upgrade to GB - Unlock P1"
My atrix was already updated to 2.3.4
Now Using RSD Lite.. idk what happened, the process failed.. and everytime I turn on my phone, it tells me "OS not found" or something like that.
It says:
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
Available 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
10. Boot Android (No BP)
11. Device UID
12 console=ttyS0, 115200n8
13. Early USB Enumeration
14. BP Tools
Can someone please help my get my phone working again.. I can't even live like a day without my phone. Is my phone hardbricked or is there any way to revive it?
Any help would be appreciated.
Thanks
try the next step
Just continue the fastboot commands and you should be fine, same thing happen to me
Sent from my MB860 using XDA App
Javi97100 said:
Just continue the fastboot commands and you should be fine, same thing happen to me
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Which fastboot commands, because I tried to use the ones such
fastboot flash preinstall preinstall.img
fastboot reboot
but nothing worked.
Try this
fastboot oem unlock
(Then it will give you a code, and type it again with code at the end)
Then when phones says unlocked
Type
fastboot reboot
Sent from my MB860 using XDA App
cpatel90 said:
Now Using RSD Lite.. idk what happened, the process failed.. and everytime I turn on my phone, it tells me "OS not found" or something like that.
It says:
SVF:105:1:2
Failed to boot 0x1000
Click to expand...
Click to collapse
Guys, where do you get the courage to do the unlock process that bricked so many phones without reading instructions?
When flashing pudding over OTA 2.3.4, Failed to boot is a common error.
You need to redo the fastboot unlock commands and all will be fine.
This is explained in the pudding thread, and gets explained every day again and again with each new thread that newbies create.
xploited said:
Guys, where do you get the courage to do the unlock process that bricked so many phones without reading instructions?
When flashing pudding over OTA 2.3.4, Failed to boot is a common error.
You need to redo the fastboot unlock commands and all will be fine.
This is explained in the pudding thread, and gets explained every day again and again with each new thread that newbies create.
Click to expand...
Click to collapse
Also if you do some looking around you'll find this http://forum.xda-developers.com/showthread.php?t=1182871 which I think was a SUPER easy way to unlock my bootloader and I didn't run into any of the issues that so many have ran into.
From unlocked/rooted GB Atrix
thanks for the help guys.. but i think its over for my phone.
it doesn't even turn on anymore. the green light comes on for one second and turns back off. i think i'll just have to get a new phone.
cpatel90 said:
thanks for the help guys.. but i think its over for my phone.
it doesn't even turn on anymore. the green light comes on for one second and turns back off. i think i'll just have to get a new phone.
Click to expand...
Click to collapse
You weren't a hard brick. You just didn't complete the steps. Did you do something else to it since your initial post? Sounds like your battery is drained, which means you need to charge it externally.
cpatel90 said:
thanks for the help guys.. but i think its over for my phone.
it doesn't even turn on anymore. the green light comes on for one second and turns back off. i think i'll just have to get a new phone.
Click to expand...
Click to collapse
uhh... sounds like your battery is drained. find someone who can charger your battery (another Atrix owner, or a Droid X owner) and try again PROPERLY.
you were trying to flash PREINSTALL to your phone? that is NOT the OS. that roots your phone once it's already installed. you need to install the SYSTEM.img and related files. you really need to read the entire guide as it so far looks like you didn't read anything.
you need to use moto-fastboot to flash System images, not regular fastboot.
http://forum.xda-developers.com/showthread.php?t=1138092
use these images and this guide, which coincidentally warns you NOT to RSD from the stock 2.3.4 and is stickied at the top of the dev forum.
http://forum.xda-developers.com/showthread.php?t=1160408
i seem to have hard bricked my atrix, doing the same thing.. well, my brother did anyway. but i somehow forced it to download mode. and re-flashed it. Works perfectly.
caleb4992 said:
i seem to have hard bricked my atrix, doing the same thing.. well, my brother did anyway. but i somehow forced it to download mode. and re-flashed it. Works perfectly.
Click to expand...
Click to collapse
that's a soft brick.
svf :105.1:2
failed to boot 0x1000
show this..........
i cant to move it to android recovery cause there no option to move
after showing this error automatically switch off my phone.....
any solution
bivrat said:
svf :105.1:2
failed to boot 0x1000
show this..........
i cant to move it to android recovery cause there no option to move
after showing this error automatically switch off my phone.....
any solution
Click to expand...
Click to collapse
Yea, thats a hard brick
Sent from my MB860 using XDA App
bivrat said:
svf :105.1:2
failed to boot 0x1000
show this..........
i cant to move it to android recovery cause there no option to move
after showing this error automatically switch off my phone.....
any solution
Click to expand...
Click to collapse
bivrat,
You've asked this same thing maybe like 5 times already and each time we've told you that there is no fix and you have to get a new phone.
Need urgent reply
Guys.. i have a favour to ask!
m in a search for a second hand moobile and found this ATRIX 4G unlocked edition which has run into this problem!
"A recent Over The Air upgrade 2.3.6 to the phone (which should have been avoided on a rooted phone) has made the phone non working.
The phone does not boot, and displays the message:
Failed to Boot 1...
Entering RSD Mode."
Guys please let me know if this coud be fixed or not, as i am in a real mood to buy this one!
bivrat said:
svf :105.1:2
failed to boot 0x1000
show this..........
i cant to move it to android recovery cause there no option to move
after showing this error automatically switch off my phone.....
any solution
Click to expand...
Click to collapse
Did you try the Unlock v4.2 app from this site? Option 3 of the menu very well might fix it for you. Well worth a shot if you haven't tried it yet.
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!
Hello every one,
I upadated my Bell Atrix to 2.3.4 gingerbread and I rooted but when i try to copy some files to frameworks file but i can't because the file is read only
how i can solve this issue ?
Messi 10 said:
Hello every one,
I upadated my Bell Atrix to 2.3.4 gingerbread and I rooted but when i try to copy some files to frameworks file but i can't because the file is read only
how i can solve this issue ?
Click to expand...
Click to collapse
You need to remount the filesystem to be writable. Use "adb shell" to do the following:
Code:
$ su // Be sure to allow superuser if prompted on the handset
# /bin/mount -o rw,remount /system
At this point, you should be able to copy files to /system.
Hope this helps.
Thank you kwick60073
Now after I do your solution it is work but i tried to copy some files to lib folder but my atrix shutdown and i opened the battery when i return it my cellphone show just motorloa logo !
how i can solve this issue
regards
Messi 10 said:
Thank you kwick60073
Now after I do your solution it is work but i tried to copy some files to lib folder but my atrix shutdown and i opened the battery when i return it my cellphone show just motorloa logo !
how i can solve this issue
regards
Click to expand...
Click to collapse
Are you doing this on PC or terminal?
by using root explorer app
I think I soft bricked my phone
Hello Evryone, I was in the process of trying to root my phone and I think I soft bricked it. I had done this once before with another atrix that had to get replaced. This was before the Gingerbread update. I went to the same site and tried the same method and somewhere it messed up. I've scoured the internet for the past 2 days trying to find something similar but I haven't found something that matches my case to the point that I'm comfortable taking a risk trying to follow their steps to fix it. The reason I'm posting this is because most of the recovery fixes I've found on the internet are from March, before the gingerbread update.
So here is exactly what I'm looking at. I now have the following text on the screen:
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
Available 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
10 Boot Android (No BP)
11 Device UID
12 console-ttyS0,115200n8
13 Early USB Enumeration
14 BP Tools
---------------------------------------
Vol Up to select, Vol Down for next choice
Current choice is mode:
RSD
Starting Fastboot protocol support
I have downloaded RSDLite5.4.4 and SuperOneClick. I'm just not sure how to use them. I recognize I'm a noob and I am sorry if this is a redundant post, but if I could get any help at all, I would greatly appreciate it. Thank you so much in advance.
CantoErgoSum said:
Hello Evryone, I was in the process of trying to root my phone and I think I soft bricked it. I had done this once before with another atrix that had to get replaced. This was before the Gingerbread update. I went to the same site and tried the same method and somewhere it messed up. I've scoured the internet for the past 2 days trying to find something similar but I haven't found something that matches my case to the point that I'm comfortable taking a risk trying to follow their steps to fix it. The reason I'm posting this is because most of the recovery fixes I've found on the internet are from March, before the gingerbread update.
So here is exactly what I'm looking at. I now have the following text on the screen:
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
Available 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
10 Boot Android (No BP)
11 Device UID
12 console-ttyS0,115200n8
13 Early USB Enumeration
14 BP Tools
---------------------------------------
Vol Up to select, Vol Down for next choice
Current choice is mode:
RSD
Starting Fastboot protocol support
I have downloaded RSDLite5.4.4 and SuperOneClick. I'm just not sure how to use them. I recognize I'm a noob and I am sorry if this is a redundant post, but if I could get any help at all, I would greatly appreciate it. Thank you so much in advance.
Click to expand...
Click to collapse
Go into the dev forum and download the pudding file that corresponds with your phone. Flash it, then boot into fastboot and use the command fastboot OEM unlock
Sent from my MB860 using xda premium
Ok so apparently I flashed a the kitchen sink rom and when phone booted up it stop and said fail to boot 2 but I flashed the and files in the video from qbking77 and now it says fail to boot 4 can anybody help me please. It the only phone I got and I'm not available for an upgrade till february
Robert5686 said:
Ok so apparently I flashed a the kitchen sink rom and when phone booted up it stop and said fail to boot 2 but I flashed the and files in the video from qbking77 and now it says fail to boot 4 can anybody help me please. It the only phone I got and I'm not available for an upgrade till february
Click to expand...
Click to collapse
What version soft ware did you start with.
the android version ? i was running on 2.3.5 it first said fail to boot 2 and thn after i flashed the sbf file it went to boot 4 do u know how i can fix this
Robert5686 said:
the android version ? i was running on 2.3.5 it first said fail to boot 2 and thn after i flashed the sbf file it went to boot 4 do u know how i can fix this
Click to expand...
Click to collapse
You can't flash custom ROMs with a locked bootloader
Sent from my MB855 using xda app-developers app
Yeah i didnt know that but idk y does the bootloader have to be unlocked cuz i flashed the beats audio one and didnt do this
What sbf did you flash?
Sent from my MB855 using xda app-developers app
mof9336 said:
What sbf did you flash?
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
Also having the same issue, I just got root, and I tried to install Jellybean from Jokersax with my battery at 5% which was dumb, but anyways now I get failed to boot 4, I can get it into fastboot protocol support, or rsd mode, and that's it, I've tried to flash some stock files, but no good, I also have a locked bootloader & am on 2.3.5
i flashed the one from qbking77 video i only flashed the one and my batery was drained cuz it wasnt full but the proccess said succes but it went to fail to boot 4 and now it says battery to low to flash but i can get a new battery real quick i jux need to know wat sbf file to flash do u know any that i can flash and would work like i said its the only phone i have and im not available for an upgrade till later and i need my phone
Failed to boot 4 Starting RSD Mode
The Story:
I started having issues with the phone becoming slower and slower and crash prone so i figured this would be a good time to flash an alternate rom. I have had root for some time and i unlocked the boot loader probably about two weeks ago. I had tried a few roms by Th3Bill and i kept having issues so i thought id try to re-lock the boot loader as i couldn't flash any of his roms even with is recovery in place to see if unlocking it again would solve my issue. Also i was running 2.3.4 NOT 2.3.5 so it wasn't due to that.
I just followed the steps outlined here from Link:
Relocking without Full SBF flash
Factory reset phone Menu/Settings/Privacy/Factory Data Reset DO NOT SKIP THIS STEP
Reboot phone into fastboot mode: VOL down/Power. Use VOL down to scroll though options til you see "fastboot" then VOL up to enable. and connect phone to computer
Open command prompt in the moto-fastboot folder and type the following using the <enter> key after each command:
moto-fastboot devices
moto-fastboot erase recovery
moto-fastboot flash recovery stock_recovery.smg
moto-fastboot reboot
Disconnect phone from computer
Start RSD Lite on your computer
Reboot phone into RSD mode: VOL down/Power. Use VOL down to scroll though options til you see "RSD" then VOL up to enable.
Connect phone to computer.
Flash nopudding4u.sbf.
Close RSD Lite and disconnect phone.
Reboot phone
Once i completed the Flash nopuding4u.sbf step it failed giving the status: "Failed flashing process. Failed Flashing process. Phone[0000]: THe "Secure_Motorola_Flash" Interface could not be found. The super-file is secure and for re-flash; the phone needs a super-file that is not secureand not for reflash. (0x7066);Phone connec"
It is not just booting to the first Motorola Dual Core Technology splash screen and showing:
Failed to boot 4
Starting RSD Mode
I've been looking for a solution to the issue for about 30 minutes and have found nothing helpful.
Nopudding4u.sbf relocks your phone, however I would recommend using the 198_7.sbf file instead. U can still unlock with pudding.sbf but you will be able to get back running.. after u flash the stock sbf u will probably need to go into recovery and do a factory reset.
Sent from my MB855 using xda app-developers app
Did you fix,
Tempest_Inc said:
The Story:
I started having issues with the phone becoming slower and slower and crash prone so i figured this would be a good time to flash an alternate rom. I have had root for some time and i unlocked the boot loader probably about two weeks ago. I had tried a few roms by Th3Bill and i kept having issues so i thought id try to re-lock the boot loader as i couldn't flash any of his roms even with is recovery in place to see if unlocking it again would solve my issue. Also i was running 2.3.4 NOT 2.3.5 so it wasn't due to that.
I just followed the steps outlined here from Link:
Relocking without Full SBF flash
Factory reset phone Menu/Settings/Privacy/Factory Data Reset DO NOT SKIP THIS STEP
Reboot phone into fastboot mode: VOL down/Power. Use VOL down to scroll though options til you see "fastboot" then VOL up to enable. and connect phone to computer
Open command prompt in the moto-fastboot folder and type the following using the <enter> key after each command:
moto-fastboot devices
moto-fastboot erase recovery
moto-fastboot flash recovery stock_recovery.smg
moto-fastboot reboot
Disconnect phone from computer
Start RSD Lite on your computer
Reboot phone into RSD mode: VOL down/Power. Use VOL down to scroll though options til you see "RSD" then VOL up to enable.
Connect phone to computer.
Flash nopudding4u.sbf.
Close RSD Lite and disconnect phone.
Reboot phone
Once i completed the Flash nopuding4u.sbf step it failed giving the status: "Failed flashing process. Failed Flashing process. Phone[0000]: THe "Secure_Motorola_Flash" Interface could not be found. The super-file is secure and for re-flash; the phone needs a super-file that is not secureand not for reflash. (0x7066);Phone connec"
It is not just booting to the first Motorola Dual Core Technology splash screen and showing:
Failed to boot 4
Starting RSD Mode
I've been looking for a solution to the issue for about 30 minutes and have found nothing helpful.
Click to expand...
Click to collapse
Hello, did you fix your phone. i am in the same issue now.. please guide me or help me to fix the phone.I have been trying for 3 days,, thanks.
Tried to flash MIUI without unlocking the bootloader
keljoe2804 said:
Also having the same issue, I just got root, and I tried to install Jellybean from Jokersax with my battery at 5% which was dumb, but anyways now I get failed to boot 4, I can get it into fastboot protocol support, or rsd mode, and that's it, I've tried to flash some stock files, but no good, I also have a locked bootloader & am on 2.3.5
Click to expand...
Click to collapse
It is was initially stuck on failed to boot 2 and Starting RSD mode. Then I used RSD lite to flash the stock sbf, and my computer went to sleep in the middle of the flash and failed. Now it is stuck on Failed to boot 4, Starting RSD mode, Battery is too low to flash.
I am not in the US right now, so cannot take it to the Sprint store. PLEASE HELP!!!
Hello ..
I was following the method given on the cyanogenmod website to unlock the bootloader and then install cm7 ... After i downloaded the files suggested i opened the RSD lite and selected the sbf file and pressed start when my phone rebooted it gave the following error ..
No OS detected, going to RSD mode
in 5 seconds
Press a key to stop countdown
Available modes are:
1. RSD
2. Fastboot
3. NVFlash
4. BP HW Bypass RSD
5. BP HW Bypass QC Dload
6. BP Diag & 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=ttyS0,115200n8
13. Early USB Enumeration
14..BP tools
i followed all the instructions clearly but dont know why it happened ... what should i do now .. ?
i am really scared i think i might have bricked my phone :crying: .. please help me out .. Please .. ...
Also i am a big noob .. this was my first time for unlocking a bootloader .. Also i rooted the phone successfully first ..
I found a thread on xda http://forum.xda-developers.com/showthread.php?p=25708728
It says that its a soft brick trying to follow the instructions but it isnt opening this file
Download atrix oem unlock and unzip to moto-fastboot folder
DL here:http://gititbit.ch/pub/unlock.zip
And i cant find the atrix oem unlock anywhere on the internet ....
Kindly please help me out ...
I don't see a problem here. This is perfectly normal. Select fastboot and install custom recovery, then proceed to install ROM of choice. Also next time use search and read existing threads as this has been covered already.
ravilov said:
I don't see a problem here. This is perfectly normal. Select fastboot and install custom recovery, then proceed to install ROM of choice. Also next time use search and read existing threads as this has been covered already.
Click to expand...
Click to collapse
Really sorry for asking but how do i install the custom recovery .. ? .. will go into fast boot while pressing the power on button and the up volume key .. thanks for the reply
zealot92 said:
Really sorry for asking but how do i install the custom recovery .. ? .. will go into fast boot while pressing the power on button and the up volume key .. thanks for the reply
Click to expand...
Click to collapse
You could have found the sticky thread in Atrix General forum:
http://forum.xda-developers.com/showthread.php?t=1302423
And, "oem unlock" is not a file, it's a command of fastboot application.
Thank you
i was able to solve the problem by completing the fast boot procedure ... thanks