after flashing 1FF-sunfire-user-2.3.5-4.5.1A_SUN_USC_19.0-19-release-keys-signed-USC-US i get failed to boot 4
tried http://androidforums.com/4545287-post3.html with no rezult
tried to flash SBF: 1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-154_5-CM-release-keys-signed-Sprint-US , rds lite 5.6 writes - waiting for re-enumeration,
phone writes - svf : 106:1:2 sec_exeption: b655, eddc, eb
plus nothing hepens when i try to power on phone with vol-, vol+ and both keys
i have already delete rsd and drivers and reinstall them
please help me
you cant flash 2.3.4 on a phone with 2.3.5. it does not work. not sure where to start but can you get to fastboot or rsd mode?
---------- Post added at 07:59 PM ---------- Previous post was at 07:49 PM ----------
also was your bootloader unlocked? any customizations at al re.....recovery or rom etc....can you give a lttle more info.
If I understand correctly you are no longer able to get to rsd mode (power and vol +) when booting correct? If so you are pretty much S.O.L. When you flashed the 2.3.4 sbf it tried to revert your locked bootloader back to 2.3.4 which is a no-no on a locked 2.3.5. Your best bet is to start coming up with a good excuse and take it back to sprint.
Truely need more info. I just a week ago did the same thing to an electrify. I at this time cant tell you the exact steps i took took fix it but it can be fixed. You are not completly screw as of yet and if you look around you will find all you need to fix this but it comes from different sources and some of the info was for different phones but worked on the photon which made it work on the electrify.
Like i said the given info is not enough to give you what you need to do and although the mopho and electrify are similar in almost every way there are a few things that differ.
I dont believe that your "S.O.L." because i just did the same thing and brought it back.
Open a command prompt as administrator and plug your phone into you computer and see if its recognized by fastboot or adb or rsd lite.
hoslayer13 was helping me with this issue and had a lot of info that helped. maybe he will chime in who knows.
More info!!!!!
After the phone says failed to boot 4 if you leave it at that screen for about a minute does it say "starting rsd mode" under failed to boot 4? If so your best bet would be to follow the steps here: (http://forum.xda-developers.com/showthread.php?t=1798145) as long as you originally started with a Photon running 2.3.5. I you can flash via rsd, make sure you remove your sd and sim card. For some reason it seams to work better. Also plug the USB cable directly to the computer (no hubs, no usb extension cables) they can cause issues with rsd. I hope you've already resolved the issue and I'm giving you advice you don't need.
@ rhewins2268. That is exactly the reason I asked "If I understand correctly you are no longer able to get to rsd mode (power and vol +) when booting correct?" If he can boot to rsd then the link I provided is a fix. Which by the looks of it may be what he was trying to do in the first place considering the electrify sbf he mentions is the first step in bringing a Photon back to stock, or back from a soft brick. You are correct more info would be helpful, but by reading what he did it sounds like more than likely he was on 2.3.5 which is an unlock-able bootloader (for the time being) and trying to downgrade (SBF: 1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-154_5-CM-release-keys-signed-Sprint-US) on a locked 2.3.5 bootloader can and more than likely will perma brick the photon. If when booting he can not see the boot options, i.e. fastboot, android recovery, rsd mode etc. he's bricked. There is no way to flash anything if the device has no, or a corrupted bootloader to start those processes.
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.
PC will not identify phone in RSD or fastboot. I have tried all drivers I can find, have uninstalled and reinstalled all software, the drivers install in each mode but RSDlite or the official moto software updater will not ID the phone when connected...
I have tried 64 and 32 windows and 3 different cables just to be sure....
Anyone have an idea what to do? I have locked an unlocked this thing once before the 4.5.91 update and again after. I used the official Motorola Software Updater to "update" back to locked stock and have had this issue ever since then....
Fixed: Belkin USB print and storage drivers had to be removed.
* delete * 10 chars
anyone??????????????
Simple question, do you have debugging turned on? I was having a similar problem, when i realized it was off I totally face palmed myself
Yesy I have tried everything I can think of... the issue is before booting into android not after... something is blocking my phone from getting picked up by RSDlite and the moto update tool... everything in android functions fine, i have turned USB debug on and off both.
I was able to root through fastboot with no issues so it is ok, but I will be d*&$^d if I can get rsd running so I can unlock... it's not like this is new to me I have unlocked this thing twice before...
halfevildruid said:
I was able to root through fastboot with no issues so it is ok, but I will be d*&$^d if I can get rsd running so I can unlock... it's not like this is new to me I have unlocked this thing twice before...
Click to expand...
Click to collapse
You are trying to unlock the same atrix?
Once it's unlock, it remains!
Even if it doesn't show it at booting(maybe disapeared after installing a rom..)
Sent from my MB860 using XDA App
Nope. I am definately locked again. I flashed the official motorola GB software update over my existing GB software to attempt to revert to locked and stock again. It worked but now I am unable to unlock. RSDlite AND the same Moto update do not see my phone in RSD mode.
halfevildruid said:
Nope. I am definately locked again. I flashed the official motorola GB software update over my existing GB software to attempt to revert to locked and stock again. It worked but now I am unable to unlock. RSDlite AND the same Moto update do not see my phone in RSD mode.
Click to expand...
Click to collapse
Actually, once a bootloader is unlocked, its unlocked for good. By reflashing to stock, all that you did was copy over pudding (the SBF file that you flashed when you unlocked the bootloader). This hides the "Unlocked" text in the top corner. To reshow this text and regain access to locked fastboot features, you must reflash pudding via the "Unlock SBF file" available here:
briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
Im not sure why you can't get into RSD mode. Try the following:
- Insure that your volume buttons work
- Unplug phone, take out battery
- wait 10 seconds
- reinsert battery
- hold down UP (not down, I made that mistake once) volume button firmly
- press and hold power button
- phone should say "Starting RSD Mode"
To enter Fastboot mode do the same steps as above, only press the down volume button instead. When the word "FastBoot" appears, press the up volume button.
I can get into rsd and fastboot on the phone. The driver in rsd installs as se flash where it used to install as nf flash. Fastboot is working fine, I was able to reroot.
The problem is rsd does not identify my device and allow me to flash. I am thinking it is in the se flash driver instead of the previous nf flash driver.
Anyone have an opinion?
Sent from my MB860 using Tapatalk
SOLVED!!!
So I figured it out! As it happens I picked up a new Belkin 750 router with networked USB support a few days back for my ext drive and printer. Apperently the Belkin drivers were the culprit! After uninstalling them everything picked up and ran like it should. Some of you devs and folks creating guides should note this in the posts so we can give folks a heads up in case it happens to them. I am sure this will happen to someone else.
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!!!