Related
Failed to boot 2
Starting RSD mode.
I tried to flash the new Ninja Rom from the Gingerblur rom. I am now stuck on the dual core screen with the message above stuck there. Someone please help, I looked through the forms but it seems like I should be able to get into recovery still, which I cannot... If you need any other info please let me know....
rp2gardner said:
Failed to boot 2
Starting RSD mode.
I tried to flash the new Ninja Rom from the Gingerblur rom. I am now stuck on the dual core screen with the message above stuck there. Someone please help, I looked through the forms but it seems like I should be able to get into recovery still, which I cannot... If you need any other info please let me know....
Click to expand...
Click to collapse
Were you unlocked before trying to flash Ninja rom?
unlocked... no at least I dont think? Obviously I was rooted but unlocked i dunno...
That is why, your bootloader has to be unlocked.
Sent from my MB860 using XDA Premium App
rp2gardner said:
unlocked... no at least I dont think? Obviously I was rooted but unlocked i dunno...
Click to expand...
Click to collapse
Ah ok... gingerblur was a pseudo-rom... made before we were able to install custom roms because we couldn't unlock our bootloader. That changed last month when devs figured it out and thus the newer custom roms. To install them you need to unlocked your bootloader.
Please read this thread for information on how to unlock
http://forum.xda-developers.com/showthread.php?t=1136261
Now, since you're already softbricks, running that may not work right now. BUT it's start.
My suggestion- read the thread, follow the instructions and see if that gets you to boot up properly after running the oem unlock.
If not, then download a fresh stock 1.8.3 SBF form the development thread and RSD flash that.
Ok thank you for your help, will post a question if I come to one. How would I download the stock 1.8.3 SBF if I am stuck on the boot screen? Im feeling like Im in over my head, Paypal donation to anyone who can walk me through this....
rp2gardner said:
Ok thank you for your help, will post a question if I come to one. How would I download the stock 1.8.3 SBF if I am stuck on the boot screen? Im feeling like Im in over my head, Paypal donation to anyone who can walk me through this....
Click to expand...
Click to collapse
Stock SBFs are in the development forum as well.
I guess first things first, do you have the tools needed
Do you have or know how to use RSD?
How about Fastboot?
Just downloaded RSD lite and flashed the SBF..
"Open and extract the Fastboot package from above" is the step I am on.. Not sure where to go from here.
The phone rebooted to the same screen that it was at before with the error message but says PASS in RSDLite for the sbf flash
rp2gardner said:
Just downloaded RSD lite and flashed the SBF..
"Open and extract the Fastboot package from above" is the step I am on.. Not sure where to go from here.
The phone rebooted to the same screen that it was at before with the error message but says PASS in RSDLite for the sbf flash
Click to expand...
Click to collapse
Which SBF? The pudding/unlock?
If you flashed the pudding SBF, then you need to do the fastboot steps next.
Did you download and unzip the fastboot package to your computer?
I did, I just dont know what to do with fastboot. Do I run it or what?.. THANKS A TON BY THE WAY...
Ok, I still have the failed to boot 2, but I am now getting the Starting Fastboot protocol support. I dont understand this step..
Type the following command:
fastboot oem unlock
rp2gardner said:
I did, I just dont know what to do with fastboot. Do I run it or what?.. THANKS A TON BY THE WAY...
Click to expand...
Click to collapse
let's say you saved and extracted the fastboot files to c:\fastboot
then you have to open up CMD (start - run - cmd )
then cd to the directory it's saved (in this example c:\fastboot )
Now you have to get your phone into fastboot mode (directions are in the link), but in short, as you turn on your phone, hold the down button. THen it should say fastboot, then hit volume up, should say entering fastboot
Then back on computer in the command window
while your in the fastboot directory
type the oem unlock command (specific command in the instruction).
after it's all done, type fastboot reboot.
I have to go now for a while, but if all that doesn't work. I suggest flashing via RSD the 1.83 SBF with Pudding built in.
The download is in the pudding thread near the top "1. All phones If you have unlocked then try to use 2.3.4 update zip from Motorola servers, then revert back to a "pre-unlock" version(1.8.3 or earlier on ATT) you will get bricked! Do not use the OTA via experimental servers and revert to older versions WITHOUT pudding preinstalled in your sbf.
ATT ONLY Get your 1.8.3 with pudding from gitbrew or multiupload."
I cant figure out where to type the command in (fastboot oem unlock) i have the screen that came up when i located the fastboot. It has a list of commands, but nothing about oem unlock...
rp2gardner said:
I cant figure out where to type the command in (fastboot oem unlock) i have the screen that came up when i located the fastboot. It has a list of commands, but nothing about oem unlock...
Click to expand...
Click to collapse
Is your phone in fastboot mode and connected?
All you gotta do is just type the command in the command window
C:\fastboo\ fastboot oem unlock
I have an ota updated atrix 4g running 4.5.91 (2.3.4) and I've tried the ever popular pudding / everyone else 4547-fix-try2.sbf and the 1.4gig monster sbf from pudding
I put my phone into RSD mode, Fire up RSD lite, plug my phone in, flash the sbf
Failed to boot
fastboot error 0x1000
And then i flash back to the default OS.
Wash Rinse Repeat.
Every time, Every SBF guide, without fail.
I can't unlock, I can't root, I can't back up, I can't do anything but use the stock rom from the roms mega thread with a nice tada I wasted another 30-40 minutes of my life.
ertDeath said:
I have an ota updated atrix 4g running 4.5.91 (2.3.4) and I've tried the ever popular pudding / everyone else 4547-fix-try2.sbf and the 1.4gig monster sbf from pudding
I put my phone into RSD mode, Fire up RSD lite, plug my phone in, flash the sbf
Failed to boot
fastboot error 0x1000
And then i flash back to the default OS.
Wash Rinse Repeat.
Every time, Every SBF guide, without fail.
I can't unlock, I can't root, I can't back up, I can't do anything but use the stock rom from the roms mega thread with a nice tada I wasted another 30-40 minutes of my life.
Click to expand...
Click to collapse
Need to enter fastboot command "fastboot oem unlock" after flashing the pudding unlock sbf file. This requires fastboot files on pc.
So long story shot, flash unlock .sbf file from pudding OP (only like 10 mb) w/ RSD Lite. Then upon reboot enter fastboot & issue unlock command, reboot. If you get bootloop or softbrick after unlocking try flashing a fruitcake. Also, need to install RomRacers CWM recovery. For detailed instructions see the pudding thread OP or the unlock bootloader instructions on briefmobile's website (link in my N00B guide).
*Edit*
Oh yeah, there's a automatic process that you can use to unlock now... its in the general section... link also in my N00B Guide.
Sent from my MB860 using xda premium
Worked like a charm
Hi ,
i have a small problem actually i tried to unlock my bootloader recently , i used the automatic bootloader unlock file but it didn't work, don't know why ,so i tried the fastboot unlock thing..where we have to put unique id code, n put commands fastboot oem unlock code my phone when doing it says ur phone is unlocked but when i on my phone the boot screen doesn't show unlock symbol ....i heart that unlock symbol should be showed...i think i am missing some steps or like that...can u guys help me out to solve it....my phone is working fine now but i am confused is my bootloader unlock or not?????
tris_333 said:
Hi ,
i have a small problem actually i tried to unlock my bootloader recently , i used the automatic bootloader unlock file but it didn't work, don't know why ,so i tried the fastboot unlock thing..where we have to put unique id code, n put commands fastboot oem unlock code my phone when doing it says ur phone is unlocked but when i on my phone the boot screen doesn't show unlock symbol ....i heart that unlock symbol should be showed...i think i am missing some steps or like that...can u guys help me out to solve it....my phone is working fine now but i am confused is my bootloader unlock or not?????
Click to expand...
Click to collapse
Did you flash the pudding unlock sbf first, before entering fastboot? If not, see Pudding OP in dev section.
Sent from my CM7 Atrix 4G
Swiftks said:
Did you flash the pudding unlock sbf first, before entering fastboot? If not, see Pudding OP in dev section.
Sent from my CM7 Atrix 4G
Click to expand...
Click to collapse
but in this site http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloaderit says if u r using gingerbread u dont have to flash just can do the fastboot
but i tried to flash the sbf file but RSD AFTER 100%...... my phone just open to normal state n rsd says reboot it manually n results says in process i damn confused
i am using android version 2.3.4 and system version 4.5.74.mbb860.att.en.us
plz help me out
tris_333 said:
but in this site http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloaderit says if u r using gingerbread u dont have to flash just can do the fastboot
but i tried to flash the sbf file but RSD AFTER 100%...... my phone just open to normal state n rsd says reboot it manually n results says in process i damn confused
i am using android version 2.3.4 and system version 4.5.74.mbb860.att.en.us
plz help me out
Click to expand...
Click to collapse
I would grab the "Unlocker for 1.8.3 and 4.5.91 ATT firmwares" from the main Pudding thread: http://forum.xda-developers.com/showthread.php?t=1136261
It's under the Unlock part of the OP (ATT ONLY).
Flash that small sbf file with RSD Lite.
Once finished flashing the unlock sbf file, Reboot, enter fastboot mode then enter the unlock commands.
See if that works.
I've read this tutorial here:
[PUDDING] International House of Pudding! BL Unlock/root thread (Updated 07/23/2011)
I can't download the unlocked sbf, the site is suspended... Does anyone know another link? What's the size of this sbf file?
When I do this flash, the phone will restart automatically, it's normal if appear an error "flash failed"?
I saw another tutorials that don't need the step of installing SDK tools. Neither have to install this, they go to the cmd and go to fasboot folder. Do I really need to instal SDK tools to do the unlock or just go to the command line and get the fastboot?
Thanks
Murilo.
As long as you have the fasboot files you shouldn't need to install it. And you only need the few mb sbf unlock file, should be able to find it in dev section under the everything photon sticky thread
Edit: yes it is normal for the flash to "fail" you just have to pull battery and continue
Sent from my MB855 using XDA
one more question
Thanks for the answer.
There is any way to know if this flash with the unlock sbf was made correctly and it's ready for fastboot?
In wich moment can I do something that brick my phone?
Thanks
You'll know its done and ready for moving on when it says failed to flash or something along those lines, you can watch the percentage meter move through as it progresses until its done and "fails" but actually works and just displays a fail message. And as long as you follow the instructions you'll be fine
last doubt
Ok, I'll do now just the fastboot command.
Last weekend I did the flash with the unlock sbf and it was too fast, and the reboot was fast too. Different from the video I saw... Right?
Do I have to start again or can I just do the prompt command with the fastboot and unlock?
Thanks again.
The flashing shouldnt take long at all if your using the file "photonpudding" that is only a few mb in size, if you use the whole unlock sbf thats ~400 something mb then yeah it will take a long time but its unnecessary and wipes all data so stick to the small file and it will only take a few min if that to flash. And if you flashed the unlock sbf before and havent reset the phone you should be able to jump right to the fastboot unlock phase
Getting the Failed to boot 3 error.
I've been working at this for days now trying to reflash an sbf image to the phone to no avail. Every single time RSDLite (5.6) gives me the error saying it failed to re-enumerate the device no matter which sbf file I use. I am running as admin, and have all the drivers installed. Any help on this would be VERY much appreciated. Any info you need, just ask.
Hows the charge on the battery.
Sent from my MB855 using xda app-developers app
Well, I keep trying to get it to flash so it runs out a lot but I have a battery charger and I periodically charge it for a few hours. There's no way for me to tell how much of a charge it has but I assume it's somewhere around 75%.
"SVF: 108: 1: 2
Failed to boot 3
Starting RSD mode"
is what is says on the phone.
Always gets stuck on "Waiting for re-enumeration" in RSD Lite.
I get this error:
Phone did re-enumerate after RAM downloader was sent. (0x703e). Phone connected.
This is not much info, we need to know, if you were unlocked, locked, what sbf did you flashed last before this, if you flashed some OTA update, or radio, which sbf are you flashing now, if you can boot into fastboot after this error, and anything, that you think might be important to know.
But if you didn't do anything special, first try redownloaing the sbf.
I never successfully unlocked my bootloader, and I think this is where the brick occured so as far as I know it is locked still. I never flashed any sbf prior to this, I was trying to install a different ROM (I don't like blur very much). As far as I know I am able to boot into fastboot (power + volume up button) and it says fastboot on my phone and when it is plugged into my computer RSD lite displays it as fastboot mode but I can't flash anything to it, it'll give me an error in fastboot. When I hold power + volume down, it says something about NVFlash which I believe is an NVidia tool except the phone just shuts off almost immediately after this. The SBF I am flashing is the Sprint 2.3.5 version, and I've tried downloading and redownloading it from about 4 different locations to no avail. I purchased an external battery charger so I can keep trying different things, so the battery is almost always at a 100% charge. As of now I believe the phone to be unrecoverably bricked, and it's pretty sad because I had the photon for all of maybe 10 hours. Safe to say I've learned my lesson about flashing non HTC devices. My EVO 4G was so easy to do, I guess Motorola really doesn't like people messing with their devices.
Edit: If there is anymore information you think would be helpful let me know.
So you can get into rsd lite or not? There is no flashable 2.3.5 sbf, except the electrify one. All these sprint test sbfs, who knows, what it is for, but there is no signature and no full partition smgs. I think it won't even start flashing. Or? If it started to flash in your case, then your phone is bricked. But if you never flashed anything like 2.3.5 ota or 2.3.5 electrify or 2.3.5 pudding, and you can get into rsd lite or fastboot, I don't think it's unrecoverablly bricked.
peetr_ said:
So you can get into rsd lite or not? There is no flashable 2.3.5 sbf, except the electrify one. All these sprint test sbfs, who knows, what it is for, but there is no signature and no full partition smgs. I think it won't even start flashing. Or? If it started to flash in your case, then your phone is bricked. But if you never flashed anything like 2.3.5 ota or 2.3.5 electrify or 2.3.5 pudding, and you can get into rsd lite or fastboot, I don't think it's unrecoverablly bricked.
Click to expand...
Click to collapse
Yes I am able to get into RSD lite, and it recognizes my phone just fine everytime with no trouble. I believe it starts flashing, or it at least creates the image but everytime it gets stuck on "waiting for re-enumeration" and it fails there with an error like "phone did not re-enumerate" or something along those lines. I've tried flashing a 2.3.4 sbf as well but it gives me the same error as if I were to flash one of the 2.3.5 files.
Ok. If it was 2.3.4 - 198_7 or 198_6 sbf and did not even re-enumerated, you need to get unlocked. Try flashing pudding unlock and recovery from fastboot or try flashing this - http://d-h.st/WKD or use this method - http://forum.xda-developers.com/showthread.php?p=25826491
peetr_ said:
Ok. If it was 2.3.4 - 198_7 or 198_6 sbf and did not even re-enumerated, you need to get unlocked. Try flashing pudding unlock and recovery from fastboot or try flashing this - http://d-h.st/WKD or use this method - http://forum.xda-developers.com/showthread.php?p=25826491
Click to expand...
Click to collapse
Pudding unlock in fastboot gives me the error "Failed flashing process. Unable to retrieve interface handle(0x7027) phone connected."
Deblur gives me the same error as before, "failed to re-enumerate".
The link to the third method is really hard for me to understand. I understand the basics in which he speed hacks it, but I don't understand which files I will need to put in and where to get those files and which ones are correct etc.
I've found the directory with all the .smg files that I'm assuming is the image. Which files would I need to speed hack to have a chance at saving this thing?
Also, my phone fails to flash anything. I'm pretty sure it doesn't actually get anything done except to create the image.
In the command line when I type in "moto-fastboot oem unlock" it says INFOOEM unlock not implemented so I take it that means I'm still locked for sure.
When I try to manually write stuff via command line with the command "moto-fastboot flash recovery derpunlock" and any of the .smg files, it sends it fine but it fails on writing it.
bdotr said:
When I try to manually write stuff via command line with the command "moto-fastboot flash recovery derpunlock" and any of the .smg files, it sends it fine but it fails on writing it.
Click to expand...
Click to collapse
thats because deprunlock is a bootloader not a recovery.
step by step what have to done to get this error. sounds like your have a error in recovery.
mof9336 said:
thats because deprunlock is a bootloader not a recovery.
step by step what have to done to get this error. sounds like your have a error in recovery.
Click to expand...
Click to collapse
Well it would never get far enough to let me flash a recovery. I'm not able to flash any .sbf's through RSD lite either. The error it gives me every time is "device failed to re-enumerate".
I'm trying it through the ramloader now. I'm pretty sure I'm stuck on an bum electrify install. When I use the electrify ramloader it reboots to a blank screen with the motorola logo on it and when I try to flash derpunlock over through command line it doesn't say anything past "writing 'boot'".
Pudding must be flashed in rsd lite too.
Fastboot oem unlock is useless right now. You need to get there unlockable bootloader there first.
You need to speedhack CG42 it's bootloader, and it's preventing from re-enumeration, because it is not booting to rsd after re-enumeration. Try that one CG42 from pudding first. You need to split that with moto android depacker. But I have suspicion, that your bootloader or ramdownloader was switched to another signature version.
Last chance, but really the last, is flashing Electrify sbf.
****, now I noticed that, you should never ever flash electrify ramdownloader there. You changed rdl signature version. Now you have only the last chance. Download and flash full electrify sbf. But you will have no 4g, no more ota, and I am not sure if it flashes electrify radio or not, so maybe you will have no service.
If you really want, you can try some combination with creating custom sbf for recovering, but you need to read the whole thread in dev section and get much more familiar with that situation.
peetr_ said:
Pudding must be flashed in rsd lite too.
Fastboot oem unlock is useless right now. You need to get there unlockable bootloader there first.
You need to speedhack CG42 it's bootloader, and it's preventing from re-enumeration, because it is not booting to rsd after re-enumeration. Try that one CG42 from pudding first. You need to split that with moto android depacker. But I have suspicion, that your bootloader or ramdownloader was switched to another signature version.
Last chance, but really the last, is flashing Electrify sbf.
Click to expand...
Click to collapse
It now says fail to boot 2. I'm going to try the speedhack when I get home from work today and I'll let you know how it goes. No 4G I can do without, no ota as well I'm fine with. The radio thing might bug me though. So do I drop pudding's CG42 file into the 2.3.5 image while it's being created? Or do I flash just the CG42?
You cannot get unlocked anymore with cg42 from pudding, even with speed hack. You must read whole how to make custom sbf thread if you want to try custom combinations. If nothing will help, your only solution is flashing Electrify 2.3.5 sbf or wait, if some similar photon sbf comes out (I doubt).