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.
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.
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!!!
I am having a problem. I was trying to upgrade to Jelly bean 4.1 on this Atrix 4g. I tried to go through the steps that it gave online with the CM10 n Cyro and all. Long story short it couldn't find the rom within the zip or something of that nature. In other words, it screwed me over. I can't get back into recovery. It's been giving me this error:
SVF 108:1:2
Failed to boot 3
Starting RSD mode
Before it was giving me just:
Failed to boot 4
Starting RSD mode
I had tried reseting to factory through the moto-fastboot but of course it failed. I have been tryin like crazy to flash various SBF from 2.3.5 to 2.3.6. I was originally at 2.3.6 but for what ever reason when I try the RSD lite it gives me the error after it executes "Phone did no re-enumerate after RAM downloader was sent". (0x703e). I have been reading forums literally all day. Perhaps I am not understanding something therefore I am missing it but maybe one of you guys could help me out with this? Maybe there is a real simple fix or maybe I completely ruined it? Either way it would be nice to get some help on this. Basically when I was trying to upgrade to 4.1 I followed "How to upgrade the Atrix 4G to Android 4.1.1 Jelly Bean via CyanogenMod 10" off of the androidauthority website. I got to step 9 but it couldn't find the ROM, by then it was too late.
UPDATE: So I got just that and RSD was flashing it until it reached yet another error:
failed flashing process. Failed flashing process. Phone[0000]: error switching phone BP pass through mode (0x70BE); phone disconnected.
Help?
majorrazer said:
Help?
Click to expand...
Click to collapse
I'm no expert, you can wait for an expert response but what i couldnt understand is why you try to flash a SBF. The manual you refer to is a CWM based installation, with a zip file, not a SBF.
So do you have CWM recovery flashed? Do you have the related zip file downloaded to sdcard?
saldirai said:
I'm no expert, you can wait for an expert response but what i couldnt understand is why you try to flash a SBF. The manual you refer to is a CWM based installation, with a zip file, not a SBF.
So do you have CWM recovery flashed? Do you have the related zip file downloaded to sdcard?
Click to expand...
Click to collapse
I don't have anything flashed at the moment. I can't boot into anything at the moment. I am confused perhaps with what will solve my problem.
majorrazer said:
I don't have anything flashed at the moment. I can't boot into anything at the moment. I am confused perhaps with what will solve my problem.
Click to expand...
Click to collapse
Do you have an unlocked bootloader? Does the word "Unlocked" appear when you power the phone on? You must have an unlocked bootloader for sure. IF not, you must unlock it.
his is the guide you were following;
http://www.androidauthority.com/atrix-4g-mb860-android-4-1-1-jelly-bean-cyanogenmod-10-cm10-106639/
As said there, it requires unlocked, rooted Atrix with with ClockworkMod Recovery installed
I guess you can still unlock the bootloader and install cwm recovery. Just search and find instructions.
HEY
i have the same problem also.... and the same error...
is your phone fix already?
could you tell me how?
SVF: 108:failed to boot 3 starting RSD mode
Hi,
I have Atrix 4G AT&T, last night rooted it and from recovery mode install custom rom cm-7.2.0-olympus after reboot its not booted and showing "SVF: 108:failed to boot 3 starting RSD mode". Removing battery also not solve this problem, Andriod recovery mode also not working by pressing down volume key on restarting. RSD Lite procedure also not working for my phone. RSD Lite 5.6 or other versions (i tried most of all) also not deducted my phone when i connected to PC in Fastboot mode. I m new and have not to much information about software version of this Motorola Atrix 4G but before its bricking mode it was on Gingerbread 2.3.6.
I have also tried "cmd prompt" stock frame version and other procedures but all failed to start my Phone to normal.
salimdawar said:
Hi,
I have Atrix 4G AT&T, last night rooted it and from recovery mode install custom rom cm-7.2.0-olympus after reboot its not booted and showing "SVF: 108:failed to boot 3 starting RSD mode". Removing battery also not solve this problem, Andriod recovery mode also not working by pressing down volume key on restarting. RSD Lite procedure also not working for my phone. RSD Lite 5.6 or other versions (i tried most of all) also not deducted my phone when i connected to PC in Fastboot mode. I m new and have not to much information about software version of this Motorola Atrix 4G but before its bricking mode it was on Gingerbread 2.3.6.
I have also tried "cmd prompt" stock frame version and other procedures but all failed to start my Phone to normal.
Click to expand...
Click to collapse
Did you unlock the bootloader the right way?
Sent from my MB860 using xda app-developers app
palmbeach05 said:
Did you unlock the bootloader the right way?
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
Not fully under stand "unlock bootloader" the right way? As mention earlier i m not an expert or more knowledge about Rooting and hacking of Andriod Phones, Please tell me in Details, thanks
salimdawar said:
Not fully under stand "unlock bootloader" the right way? As mention earlier i m not an expert or more knowledge about Rooting and hacking of Andriod Phones, Please tell me in Details, thanks
Click to expand...
Click to collapse
did you flash pudding sbf via rsd and use fastboot to oem unlock?
Sent from my MB860 using xda app-developers app
palmbeach05 said:
did you flash pudding sbf via rsd and use fastboot to oem unlock?
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
No i didnt use RSD methode because RSD Lite not deducting my Phone, tried different versions of RSD for flash pudding, I have Windows 8-64bit.
Also Flash the Mobile throw following procedure
Boot the Atrix into “Fastboot Mode” (hold power + vol down)
plug your Atrix into your PC via USB
Navigate to your fastboot folder via command prompt
type “moto-fastboot flash boot boot.img” press enter
type “moto-fastboot flash system system.img” press enter
type “moto-fastboot -w” press enter
type “moto-fastboot reboot” press enter.
But it also not Boot my phone in normal, Its stuck in Start menu,
SVF 108:1:2
Failed to boot 3
Starting RSD mode
salimdawar said:
No i didnt use RSD methode because RSD Lite not deducting my Phone, tried different versions of RSD for flash pudding, I have Windows 8-64bit.
Also Flash the Mobile throw following procedure
Boot the Atrix into “Fastboot Mode” (hold power + vol down)
plug your Atrix into your PC via USB
Navigate to your fastboot folder via command prompt
type “moto-fastboot flash boot boot.img” press enter
type “moto-fastboot flash system system.img” press enter
type “moto-fastboot -w” press enter
type “moto-fastboot reboot” press enter.
But it also not Boot my phone in normal, Its stuck in Start menu,
SVF 108:1:2
Failed to boot 3
Starting RSD mode
Click to expand...
Click to collapse
ok so its telling you what to do. Since you haven't flashed a sbf, chances are you are not unlocked, so how do you expect to flash anything on a locked device?
Did you install motorola device manager for the drives?
Sent from my MB860 using xda app-developers app
palmbeach05 said:
ok so its telling you what to do. Since you haven't flashed a sbf, chances are you are not unlocked, so how do you expect to flash anything on a locked device?
Did you install motorola device manager for the drives?
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
Yes already install this file from Net
"Motorola_End_User_Driver_Installation_5.1.0_64bit "
and not expect any thing else about flashing of my device.
Before Motorola Atrix 4G, i were used in passed Samsung S1, S2, S3, & T989 (T-Mobile S2 version). All these andriod sets were very easily hack or Root and can install Roms easily .
But Moto Atrix 4G can me upset and sad.
kindly help me to re-connect my self to the andriod world by this Motorola Atrix 4G, thanks
Hey guys I'm having trouble getting to RSS mode my phone comes on then it says entering nv flash recovery mode then the phone dies so I need help trying to get into my phone to flash the sbf file
Sent from my GT-N7105 using XDA Premium 4 mobile app
Need Help regarding Motorola Atrix Mb 861.
salimdawar said:
No i didnt use RSD methode because RSD Lite not deducting my Phone, tried different versions of RSD for flash pudding, I have Windows 8-64bit.
Also Flash the Mobile throw following procedure
Boot the Atrix into “Fastboot Mode” (hold power + vol down)
plug your Atrix into your PC via USB
Navigate to your fastboot folder via command prompt
type “moto-fastboot flash boot boot.img” press enter
type “moto-fastboot flash system system.img” press enter
type “moto-fastboot -w” press enter
type “moto-fastboot reboot” press enter.
But it also not Boot my phone in normal, Its stuck in Start menu,
SVF 108:1:2
Failed to boot 3
Starting RSD mode
Click to expand...
Click to collapse
I need your help regarding Motorola Atrix Mb 861. My phone is not boot and show..
SVF: 108:1:2, Failed to boot 3
Starting RSD mode.
also not able to hard reset. My phone detail are.
My model is KT Atrix MB861
Not sure which is the build number
s/w version: 4.5.2A-KT-75
Android version: 2.3.4
Kernel version: 2.6.32.9-00001...
Please Help regarding that matter.....
kamal.navigator said:
I need your help regarding Motorola Atrix Mb 861. My phone is not boot and show..
SVF: 108:1:2, Failed to boot 3
Starting RSD mode.
also not able to hard reset. My phone detail are.
My model is KT Atrix MB861
Not sure which is the build number
s/w version: 4.5.2A-KT-75
Android version: 2.3.4
Kernel version: 2.6.32.9-00001...
Please Help regarding that matter.....
Click to expand...
Click to collapse
Were you bootloader unlocked before getting this message?
OK, I will start off by saying I have (nearly) completely screwed myself.
I have a P769 (TMO; does this mean BK?).
I followed this (http://forum.xda-developers.com/showthread.php?p=38677123http://forum.xda-developers.com/showthread.php?p=38677123) to root the device and successfully made it through (using V20D KDZ).
Then then tried to flash this ROM (http://forum.xda-developers.com/showthread.php?t=2335984). Unforunately, I did not have an unlocked bootloader and now I am receiving a Security Error at boot. Even more unfortunate is that I did NOT do a backup so I am truly in a bad place now.
I tried to run through the first step of rooting but the software will not detect the phone as being connected and tells me to connect the USB cable. I have installed the drivers that are in that post but admittedly I may have updated them after rooting.
At this point I only have access to fastboot so I am trying that method but I cannot find any system.img files to be able to flash the system partition.
What do I do now? Can anyone help me? I have exhausted every Google search and XDA search. I may be missing something but I feel I am in a very bad place now and need to get this phone back up and running.
thchipmunk said:
OK, I will start off by saying I have (nearly) completely screwed myself.
I have a P769 (TMO; does this mean BK?).
I followed this (http://forum.xda-developers.com/showthread.php?p=38677123http://forum.xda-developers.com/showthread.php?p=38677123) to root the device and successfully made it through (using V20D KDZ).
Then then tried to flash this ROM (http://forum.xda-developers.com/showthread.php?t=2335984). Unforunately, I did not have an unlocked bootloader and now I am receiving a Security Error at boot. Even more unfortunate is that I did NOT do a backup so I am truly in a bad place now.
I tried to run through the first step of rooting but the software will not detect the phone as being connected and tells me to connect the USB cable. I have installed the drivers that are in that post but admittedly I may have updated them after rooting.
At this point I only have access to fastboot so I am trying that method but I cannot find any system.img files to be able to flash the system partition.
What do I do now? Can anyone help me? I have exhausted every Google search and XDA search. I may be missing something but I feel I am in a very bad place now and need to get this phone back up and running.
Click to expand...
Click to collapse
A system.img is to big to flash in fastboot. Follow Lelus directions http://forum.xda-developers.com/showpost.php?p=43021469&postcount=5
Sent from my LGMS769 using xda app-developers app
kuma82 said:
A system.img is to big to flash in fastboot. Follow Lelus directions http://forum.xda-developers.com/showpost.php?p=43021469&postcount=5
Sent from my LGMS769 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the suggestion. I just tried it and I get an error"
Updating is not possible any longer due to a fatal error while the LG Mobile Phone Software Update.
Click to expand...
Click to collapse
I am still getting the security error even though other threads said I should be able to get rid of it.
Is it possible to create a custom update.zip to flash with?
When I do the recovery it returns my phone as a P769BKGO if that helps with anything.
thchipmunk said:
Thanks for the suggestion. I just tried it and I get an error"
I am still getting the security error even though other threads said I should be able to get rid of it.
Is it possible to create a custom update.zip to flash with?
Click to expand...
Click to collapse
What os are you running also what kdz are you trying to flash ?
Lelus said:
What os are you running also what kdz are you trying to flash ?
Click to expand...
Click to collapse
I am running 32-bit Windows 7 Professional Service Pack 1. I tried flashing V20D_00.kdz (using the offline flash) as well as the V10G_00.kdz and V10E_00.kdz.
Using the offline flash method I constantly get the error of cannot connect to phone no matter how many times I restart the PC or phone and unplug USB.
thchipmunk said:
I am running 32-bit Windows 7 Professional Service Pack 1. I tried flashing V20D_00.kdz (using the offline flash) as well as the V10G_00.kdz and V10E_00.kdz.
Using the offline flash method I constantly get the error of cannot connect to phone no matter how many times I restart the PC or phone and unplug USB.
Click to expand...
Click to collapse
you already flashed ics xloader and uboot with fastboot and kdz files names are all CAPS right ?
Lelus said:
you already flashed ics xloader and uboot with fastboot and kdz files names are all CAPS right ?
Click to expand...
Click to collapse
All caps, correct.
Should I do fastboot and then run the offline method?
I did do the fastboot then tried the recovery phone option from the support tool.
I did find a recovery I made that included (for some reason) only the recovery and boot.
thchipmunk said:
All caps, correct.
Should I do fastboot and then run the offline method?
I did do the fastboot then tried the recovery phone option from the support tool.
I did find a recovery I made that included (for some reason) only the recovery and boot.
Click to expand...
Click to collapse
Don't worry about stock recovery it's useless, just flash ics xloader and uboot http://forum.xda-developers.com/showthread.php?t=2292828 option #5
, put your phone into s/w upgrade mode and try offline method
Lelus said:
Don't worry about stock recovery it's useless, just flash ics xloader and uboot http://forum.xda-developers.com/showthread.php?t=2292828 option #5
, put your phone into s/w upgrade mode and try offline method
Click to expand...
Click to collapse
I'll reboot and then try that again. I'll check back afterwards.
Should I do anything extra like start the offline flash from scratch as far as drivers? I'm not even sure where to begin in regards to what drivers/files to remove.
Thank you! Thank you! Thank you!
Now I just need to figure out the screen calibration.
Also, what can I do with this now? Do I need to unlock the bootloader to load custom ROMs without getting a security error?
Sorry for my lack of knowledge. My last phone was a Bionic and that was the easiest phone to root and add a ROM to.
unfortunately i find myself in this situation
gettin security error after what i assume was me trying to flash on a locked bootloader
anyway, i can't figure this out, the whole flashing fastboot and what not
i read through the readme and installed the drivers for the "other/unknown" device that pops up
this is what i try to do next
open up start.bat
enter 5 and hit enter
remove battery from phone (as instructed) and hit any key
boot phone into sw upgrade (holding vol up and plugging in usb cable)
device seems to be picked up and i see the "wait 5 seconds" (german?) and the image is revered horizontally on my phone
now after 4/5 seconds it says "waiting for device", which then i put the battery in
but NOTHING happens after this, it hangs at "waiting for device"
can someone please tell me what i'm doing wrong?
otherwise i think i'm left with a totally effed lg optimus l9
rotatorkuf said:
unfortunately i find myself in this situation
gettin security error after what i assume was me trying to flash on a locked bootloader
anyway, i can't figure this out, the whole flashing fastboot and what not
i read through the readme and installed the drivers for the "other/unknown" device that pops up
this is what i try to do next
open up start.bat
enter 5 and hit enter
remove battery from phone (as instructed) and hit any key
boot phone into sw upgrade (holding vol up and plugging in usb cable)
device seems to be picked up and i see the "wait 5 seconds" (german?) and the image is revered horizontally on my phone
now after 4/5 seconds it says "waiting for device", which then i put the battery in
but NOTHING happens after this, it hangs at "waiting for device"
can someone please tell me what i'm doing wrong?
otherwise i think i'm left with a totally effed lg optimus l9
Click to expand...
Click to collapse
Odds are, you are doing nothing wrong. Check your android version, if you are on 4.2+ (JellyBean) you can't unlock your bootloader quite yet. Here is the thread you should keep track of at the moment http://forum.xda-developers.com/showthread.php?t=2277639&page=152
Insert battery more quickly
rotatorkuf said:
unfortunately i find myself in this situation
gettin security error after what i assume was me trying to flash on a locked bootloader
anyway, i can't figure this out, the whole flashing fastboot and what not
i read through the readme and installed the drivers for the "other/unknown" device that pops up
this is what i try to do next
open up start.bat
enter 5 and hit enter
remove battery from phone (as instructed) and hit any key
boot phone into sw upgrade (holding vol up and plugging in usb cable)
device seems to be picked up and i see the "wait 5 seconds" (german?) and the image is revered horizontally on my phone
now after 4/5 seconds it says "waiting for device", which then i put the battery in
but NOTHING happens after this, it hangs at "waiting for device"
can someone please tell me what i'm doing wrong?
otherwise i think i'm left with a totally effed lg optimus l9
Click to expand...
Click to collapse
I've found that the process completes if you put the battery back in , right after you reconnect the USB.
mven45 said:
I've found that the process completes if you put the battery back in , right after you reconnect the USB.
Click to expand...
Click to collapse
hi iam in the same boat have you figured any thing out please help i also may have found away if you by chance had your lg pc suit installed and setup prior to this mishap
maso321 said:
hi iam in the same boat have you figured any thing out please help i also may have found away if you by chance had your lg pc suit installed and setup prior to this mishap
Click to expand...
Click to collapse
If you're running a Windows 8 OS, that's the reason it's not working.
Sent from my LGMS769 using XDA Premium 4 mobile app
rotatorkuf said:
unfortunately i find myself in this situation
gettin security error after what i assume was me trying to flash on a locked bootloader
anyway, i can't figure this out, the whole flashing fastboot and what not
i read through the readme and installed the drivers for the "other/unknown" device that pops up
this is what i try to do next
open up start.bat
enter 5 and hit enter
remove battery from phone (as instructed) and hit any key
boot phone into sw upgrade (holding vol up and plugging in usb cable)
device seems to be picked up and i see the "wait 5 seconds" (german?) and the image is revered horizontally on my phone
now after 4/5 seconds it says "waiting for device", which then i put the battery in
but NOTHING happens after this, it hangs at "waiting for device"
can someone please tell me what i'm doing wrong?
otherwise i think i'm left with a totally effed lg optimus l9
Click to expand...
Click to collapse
Take out battery and USB cable from phone
Enter #5
Plug in USB when it tells you
Wait 5 seconds or less then place battery in
once in fastboot mode remove battery for a couple of seconds then replace
take out the usb press the vol + then reconnect
S/W upgrade mode achieved.
Flash accordingly. . .
Nathan.7118391 said:
Take out battery and USB cable from phone
Enter #5
Plug in USB when it tells you
Wait 5 seconds or less then place battery in
once in fastboot mode remove battery for a couple of seconds then replace
take out the usb press the vol + then reconnect
S/W upgrade mode achieved.
Flash accordingly. . .
Click to expand...
Click to collapse
Hey Nathan did you ever get your device operating again?
Sent from my LGMS769 using XDA Premium 4 mobile app
kuma82 said:
Hey Nathan did you ever get your device operating again?
Sent from my LGMS769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nope! I had to do a warranty exchange. I was copying the system image then I thought it finished so I unplugged the phone. May I tried my best to get the phone back but I could only get into fastboot mode, but hey lesson learned. Though I did see this tool that someone here was trying to use to flash bin and fls files in 3 minutes! But it only works for p790 Optimus black. Which sucks because I could get my phone into an inverted S/W upgrade mode (yeah I know it's on the real one) but it only lasted for about 3 minutes then shut down so doing the offline fix just took too long. I would get to about 23% install and the phone would just turn off. . so close! LOL
EDIT: YEAH got the phone to finally work! No exchange now, take that LG! Just kept trying there offline fix
Nathan.7118391 said:
Nope! I had to do a warranty exchange. I was copying the system image then I thought it finished so I unplugged the phone. May I tried my best to get the phone back but I could only get into fastboot mode, but hey lesson learned. Though I did see this tool that someone here was trying to use to flash bin and fls files in 3 minutes! But it only works for p790 Optimus black. Which sucks because I could get my phone into an inverted S/W upgrade mode (yeah I know it's on the real one) but it only lasted for about 3 minutes then shut down so doing the offline fix just took too long. I would get to about 23% install and the phone would just turn off. . so close! LOL
EDIT: YEAH got the phone to finally work! No exchange now, take that LG! Just kept trying there offline fix
Click to expand...
Click to collapse
I'm trying to restore my P769 to stock (Stuck LG logo), and getting nowhere.
How did you get the flash to work? What error did you get when the phone would turn off? How did you get the inverted S/W mode?
My phone only got to 17-20% before getting an connection error using the offline booth method, this was with both JB and ICS u-boot/boot/recovery .imgs from the P769 ROMs--should I try the steps in unlocking the bootloader to at least get to a bootable state?
Nathan.7118391 said:
Nope! I had to do a warranty exchange. I was copying the system image then I thought it finished so I unplugged the phone. May I tried my best to get the phone back but I could only get into fastboot mode, but hey lesson learned. Though I did see this tool that someone here was trying to use to flash bin and fls files in 3 minutes! But it only works for p790 Optimus black. Which sucks because I could get my phone into an inverted S/W upgrade mode (yeah I know it's on the real one) but it only lasted for about 3 minutes then shut down so doing the offline fix just took too long. I would get to about 23% install and the phone would just turn off. . so close! LOL
EDIT: YEAH got the phone to finally work! No exchange now, take that LG! Just kept trying there offline fix
Click to expand...
Click to collapse
How did you solve this? I am at the same steps, I get into mirrored software mode and then I attempt the offline fix. I have even started the offline fix early to save time. And yet it will only stay on for 2 and a half minutes or so and then shuts off. The farthest i have been able to get it to go is 41%. I have tried fastboot mode to try and send boot.img and it just says that it cannot find the boot partition. So it looks like my only option is the offline fix but it doesn't have enough time to complete. I have tried about 20 or so times how many tries did it take for you? Did you do anything special to get it to finish? any advice on how to get it to finish? Spent about 6 hrs last night trying to get this phone back up and running and this is where i am stuck. Its lame cuz i woke up to the phone like this it was fine when i went to bed. And was for months.