I just tried unlocking the BL from my official AT&T gingerbread using this guide, I tried flashing the sbf file with RSD and it got stuck and now my phone stays at this with the difference that mine gives me the option to try fastboot, RSD mode, Android Recover and another pletora of options I'm not sure i want to name.
So being able to try RSD again, i tried flashing this and it was appearently working but when it tried to set the device on BP Pass through mode, the device would go back to the Infamous screen and it wouldn't move from there.
Am I screwed? Do i have option?
I'm going to try to flash the stock FW to see what happens
Kenchinito said:
I just tried unlocking the BL from my official AT&T gingerbread using this guide, I tried flashing the sbf file with RSD and it got stuck and now my phone stays at this with the difference that mine gives me the option to try fastboot, RSD mode, Android Recover and another pletora of options I'm not sure i want to name.
So being able to try RSD again, i tried flashing this and it was appearently working but when it tried to set the device on BP Pass through mode, the device would go back to the Infamous screen and it wouldn't move from there.
Am I screwed? Do i have option?
I'm going to try to flash the stock FW to see what happens
Click to expand...
Click to collapse
use the automatic unlock tool found here:http://forum.xda-developers.com/showthread.php?t=1182871&highlight=automatic
do option 1 then option 3 (only use option 3 if on gingerbread) and you're good to go
Fastboot then use fastboot oem unlock command on PC. Reboot and it should work.
Sent from my MB860 using XDA Premium App
Thanks, I'll try it out and post back
I forgot to mention that my phone seems to be low on battery. Does it charge if it's not on the OS?
Noob Killed his phone
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. Everything started well, then it failed while writing to the device. Now, when I attempt to boot, I get the similar message of
SVF:405;1:2
Failed to boot 0x1000
With a 14 available options. 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.
Did I just kill my phone?
I haven't still fixed mine because of the battery, I still have to find an external charger. Though, you can try the link from above.
Ok, I did the steps and now my phone is at a screen with the motorola logo with the dual core name on it and it has the word Unlocked on top of it.
What should i do?
the boot screen with motorola logo and unlock in corner will take awhile to load usually like 10 minutes but if it doesnt load for example i let mine sit for an hour and never loaded i just took the batter o and restart it and it rebooted and worked but use that as a last resort give it some time!
Omg i just fixed it!! Thx for the help!!
Mrniceguy0921 said:
the boot screen with motorola logo and unlock in corner will take awhile to load usually like 10 minutes but if it doesnt load for example i let mine sit for an hour and never loaded i just took the batter o and restart it and it rebooted and worked but use that as a last resort give it some time!
Click to expand...
Click to collapse
i think if the phone can be detected by PC, it should be a soft brick.. it is unfortunate my phone is booting loop and can not be read by PC, you're better than me..
I hope this is posted in the correct location, apologies if it is not.
As stated in the title my droid razr maxx is stuck in a boot loop:
it will go to the "M" "dual core technology" screen and reboot itself after about 20s.
I tried going into the boot menu [I can turn off the phone from the AP fastboot, so it doesn't lose charge].
In the boot menu, I tried to do a factory reset (I've never done anything to this phone and have no idea how)...the recover screen never comes up, the phone just goes back into the loop, same thing for BP tools.
Note: FYI: I had my phone plugged into my computer when I went into AP fastboot and I got an error on my computer saying that it can't find the device.
As of right now I have no idea what to do (I've only ever used phones as they came in the box)
Any help would be greatly appreciated
Thanks
Update: After charging for the night, the phone turned on with no problem...
then later the screen wouldn't turn on [side buttons and touch didn't work].
Now it looks like the phone is completely off and wont turn on at all (I tried all the combination of buttons and I tried plugging it in)
Please help
I have a gsm razr on ics. i installed bootmenu and all worked fine. i then went and tried to install a rom on the second system did a factory wipe (guessing this might have been my error) and installed. then tried to boot.
the motorola logo shows up but then nothing happens. the screen stays blank. when i connect the phone to my computer it detects it (makes a noise) so it seems to be on. however i can't acess it via rsd or adb.
ofcourse i tried to boot it into fastboot to use rsd but i can't. i hold down volume+&- and then press power but nothing happens...really desperate. please help!
ok looks like the crisis is solved. jesus that gave me a fright.
i managed to boot into bootloader via adb and then was able to flash the ics system via rsd...holy smokes i thought my phone was done...
hey having a pretty major issue and really hoping someone can help. i have a rooted razr with jellybean leak. installed and rooted with mattlgroff droid razr utility. was working fine for a while. started having some issues so i just did a safestrap system restore and now the phone wont boot. it gets to the moto splash screen and then just goes blank, does not even get to the option to boot to safestrap or regular boot. i have tried to restore jb again with the razr utility and it seemed to install but then safe result on reboot, moto splash then nothing. i would try factory reset, but cant seem to get to that either. i boot to the built in recovery mode and choose recovery and then it gets to the screen with the android lying on its back with the triangle and exclamation mark and i hit the volume button and nothing happens, just stays there. would really appreciate any help or ideas here. thanks.
nevermind. was finally able to get into recovery mode and did factory reset and its working now
I just recently joined the rooting community a few days ago. I started by rooting my phone with petes rooting tool, and then sbf'd the phone back to android 2.3.4 before installing boot strap recovery on the phone. I was able to successfully flash the cyanogen 10 mod, with many exceptions. The first of these exceptions is that the phones keyboard did not work at all (unable to active phone, unable to do anything really), so I decided to look this up. I tried almost everything except installing a new gapps which I was in the process of doing when I hit a major roadblock. The problem I ran into was that when I re-installed the bootstrap recovery on the cyanogen 10 rom to get to the recovery mode in order to flash the gapps file, the phone became stuck on the M (dual core) boot screen. I was however able to access the boot menu (power+volume down), and tried to sbf the phone back to android 2.3.4 so that it would hopefully fix all of my stupidity. Little did I know that this would just increase my unluckiness with the rooting process, and the phone now will not boot into the boot screen. When I hold down (volume down+power) the phone simply flahes a screen and then will do nothing until I pop the battery out. After that, i tried simply turing the hone on by holding down just the power button, and it boot to a screen which displays "failed to boot 2" and then below that "starting RSD mode". From this screen I have tried to sbf to android 2.3.4, and also to android 2.3.5 multiple times, and every time it pops up with either an error on the computer, or "sec_exception: febe, 4e, 4e" and then an error on the computer. ANY HELP WOULD BE GREATLY APPRECIATED!!!! I AM OUT OF OPTIONS AT THIS POINT, AND AM STARTING TO PANIC! HELP ME!
Failed to boot, sounds like hardware failure
but you can try ezSBF, link in my list, might work.
sd_shadow's [Collection] of Links for Droid X2
Sent from my Clear using xda premium
vernon428 said:
I just recently joined the rooting community a few days ago. I started by rooting my phone with petes rooting tool, and then sbf'd the phone back to android 2.3.4 before installing boot strap recovery on the phone. I was able to successfully flash the cyanogen 10 mod, with many exceptions. The first of these exceptions is that the phones keyboard did not work at all (unable to active phone, unable to do anything really), so I decided to look this up. I tried almost everything except installing a new gapps which I was in the process of doing when I hit a major roadblock. The problem I ran into was that when I re-installed the bootstrap recovery on the cyanogen 10 rom to get to the recovery mode in order to flash the gapps file, the phone became stuck on the M (dual core) boot screen. I was however able to access the boot menu (power+volume down), and tried to sbf the phone back to android 2.3.4 so that it would hopefully fix all of my stupidity. Little did I know that this would just increase my unluckiness with the rooting process, and the phone now will not boot into the boot screen. When I hold down (volume down+power) the phone simply flahes a screen and then will do nothing until I pop the battery out. After that, i tried simply turing the hone on by holding down just the power button, and it boot to a screen which displays "failed to boot 2" and then below that "starting RSD mode". From this screen I have tried to sbf to android 2.3.4, and also to android 2.3.5 multiple times, and every time it pops up with either an error on the computer, or "sec_exception: febe, 4e, 4e" and then an error on the computer. ANY HELP WOULD BE GREATLY APPRECIATED!!!! I AM OUT OF OPTIONS AT THIS POINT, AND AM STARTING TO PANIC! HELP ME!
Click to expand...
Click to collapse
im not completely sure why you sbf'd after rooting the first time? no need for that. i would read up a bit more if you do get it working, watch tomsgt123 's videos on youtube so you know what youre doing. and you used the Gapps for cm10.1 not our version. that is why keyboard didnt work. read read read.
after reading abain, i guess you were on 2.3.5. and thats why you sbf'd. but rooting was not needed before sbf. hope you have better luck next time .
flash will fail if battery is too low, should be a low battery error though, but maybe not every time.
if it is low battery, you will need a charged battery or a tbh programing adapter
link to TBH adapter and dx2 external charger in my list
Sent from my XT862 using xda premium
Lorenzo VonMatterhorn said:
im not completely sure why you sbf'd after rooting the first time? no need for that. i would read up a bit more if you do get it working, watch tomsgt123 's videos on youtube so you know what youre doing. and you used the Gapps for cm10.1 not our version. that is why keyboard didnt work. read read read.
after reading abain, i guess you were on 2.3.5. and thats why you sbf'd. but rooting was not needed before sbf. hope you have better luck next time .
Click to expand...
Click to collapse
Do you have any advice on where I should go from here then? My phone is basically a useless hunk of technology until i can get it to boot back into cyanogen 10, or sbf it back to an android operating system. The RSD mode always fails when I try to normally sfd, but i have not tried EZ sbf yet..... any other suggestions?
vernon428 said:
I just recently joined the rooting community a few days ago. I started by rooting my phone with petes rooting tool, and then sbf'd the phone back to android 2.3.4 before installing boot strap recovery on the phone. I was able to successfully flash the cyanogen 10 mod, with many exceptions. The first of these exceptions is that the phones keyboard did not work at all (unable to active phone, unable to do anything really), so I decided to look this up. I tried almost everything except installing a new gapps which I was in the process of doing when I hit a major roadblock. The problem I ran into was that when I re-installed the bootstrap recovery on the cyanogen 10 rom to get to the recovery mode in order to flash the gapps file, the phone became stuck on the M (dual core) boot screen. I was however able to access the boot menu (power+volume down), and tried to sbf the phone back to android 2.3.4 so that it would hopefully fix all of my stupidity. Little did I know that this would just increase my unluckiness with the rooting process, and the phone now will not boot into the boot screen. When I hold down (volume down+power) the phone simply flahes a screen and then will do nothing until I pop the battery out. After that, i tried simply turing the hone on by holding down just the power button, and it boot to a screen which displays "failed to boot 2" and then below that "starting RSD mode". From this screen I have tried to sbf to android 2.3.4, and also to android 2.3.5 multiple times, and every time it pops up with either an error on the computer, or "sec_exception: febe, 4e, 4e" and then an error on the computer. ANY HELP WOULD BE GREATLY APPRECIATED!!!! I AM OUT OF OPTIONS AT THIS POINT, AND AM STARTING TO PANIC! HELP ME!
Click to expand...
Click to collapse
mine did the fail to boot thing back in september, i have to get a new x2. Try using a different computer, good luck
vernon428 said:
Do you have any advice on where I should go from here then? My phone is basically a useless hunk of technology until i can get it to boot back into cyanogen 10, or sbf it back to an android operating system. The RSD mode always fails when I try to normally sfd, but i have not tried EZ sbf yet..... any other suggestions?
Click to expand...
Click to collapse
With it powered off, hold power and volume up . See if you can get it into rsd mode . If so, sbf from there . Hope it works .
Lorenzo VonMatterhorn said:
With it powered off, hold power and volume up . See if you can get it into rsd mode . If so, sbf from there . Hope it works .
Click to expand...
Click to collapse
I can get into RSD mode, and the phone seems to SBF okay, until the SBF on the computer displays "failed", and the phone displays an error message. I am also using a fully charged battery during the whole process (my friend has the same phone so i swap batteries out with him to charge).
vernon428 said:
I can get into RSD mode, and the phone seems to SBF okay, until the SBF on the computer displays "failed", and the phone displays an error message. I am also using a fully charged battery during the whole process (my friend has the same phone so i swap batteries out with him to charge).
Click to expand...
Click to collapse
and you tried EZsbf?
try ezSBF
if you can't get it to work, you can go back, try using rsd lite, and look for Driver issues