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...
Hello everyone.
I own Motorola Atrix 4g AT&T with 2.3.4 / 4.5.91 Build.
I have read every single thread about Unlocking the bootloader yet I still cannot do it.
First I tried directly the fastboot unlock command for unlocking it but I had an error saying that OEM Unlock is not implemented. Thats OK since the stock bootloader isnt unlockable. So I downloaded RSD Lite as well as the two SBF files (the small pudding and the huge pudding (full version) of AT&T unlockable/pre root) Here is where I got stuck! I have the drivers properly installed and I tried both Windows7 and WindowsXP still i cant get past the boot logo. Here is the situation.
I connect the Phone in RSD Mode. In RSD Lite it shows as NS Flash Olympus and stays connected. When I load the SBF file and press start it gets to 100%. Then phone reboots and RSD Lites says that its waiting for phone to re-enumeration and after a while it gets the error message: Phone[0000]: Phone did not re-enumerate after RAM-downloader was sent.. Phone is still stuck on the Moto Logo untill I remove the battery. If I remove the battery Phone starts.
Am I missing something?
As far as I remember, once you flash pudding the phone will indeed seem unusable. Immediately after flashing pudding you need to go into fastboot and run the oem unlock commands, then you need to flash a custom recovery, then boot into recovery and flash a custom ROM. You miss any of these steps and the phone will very likely not boot.
ravilov said:
As far as I remember, once you flash pudding the phone will indeed seem unusable. Immediately after flashing pudding you need to go into fastboot and run the oem unlock commands, then you need to flash a custom recovery, then boot into recovery and flash a custom ROM. You miss any of these steps and the phone will very likely not boot.
Click to expand...
Click to collapse
The problem is that i cannot flash pudding since I get an error message after the extracting process when the phone is suppose to reboot and flash itself. It just reboots and stays with Motorola logo (RSD Lites gives me the error) and phone freezes untill I remove battery. After that when I power on the phone it just loads normally.
So the problem is that I cannot flash pudding.... simply because phone dosnt reenumerate after reboot....
Bump ...
I want to add that the phone dosnt have backlight in boot menus (ak. background light is turned off but i can still see the options in boot menus)
Also I am not able to install OTA Updates I get a triangle on the screen and phone boots into os with failed to update message.
Else phone is fully functional. I havnet done anything except rooting the phone and doing the tethering and webtop over hdmi hack.
m140n1 said:
Bump ...
I want to add that the phone dosnt have backlight in boot menus (ak. background light is turned off but i can still see the options in boot menus)
Also I am not able to install OTA Updates I get a triangle on the screen and phone boots into os with failed to update message.
Else phone is fully functional. I havnet done anything except rooting the phone and doing the tethering and webtop over hdmi hack.
Click to expand...
Click to collapse
Try this automated tool. There are several options to choose from.
Download tool here.
Sorry i did not have the kernel or most information about the phone but ill explain the problem if anyone can help out it'd be a blessing
i have a U.S cellular Motorola electrify running 2.3.5 ( which recently found out was unrom-able)
i got it rooted using one touch method--
Then not thinking -- ( ive rooted and installed roms on other phones never a Motorola) didn't know it needed a unlocked bootloader to function and get roms installed.
i knew i needed a clockworkmod on the phone and i read about the app that boots into clockworkmod bootstrap--apk
did that and it worked--
here is the problem..
didn't install the bootloader.. and tried installing Cyanogenmod10 unofficial rom from photon development forum
rebooted-- got Failed to Start2- starting rsd mode -- if i dont press anything
if i press down it says NV recovery but does nothing
if i press UP it goes into Starting usd recovery ( sorry not exact words not with my phone at the moment)
ive been reading guides.. downing the lock unlock from the bricked guide.. RSD lite would read the phone in the usd recovery
try flashing the offical us cellular back but get an error
wont show up in command prompt
not sure what to do.. please help its hard to function without a phone i hope its not fully bricked
Can you get into fast boot by pressing power and volume-down? If so, you just need to wipe everything using "fastboot -w" and rebooting into RSD mode to flash the uscc sbf.
When you flashed cm10, the kernel is not compatible with the bootloader you're on.
If anyone has the 2.3.5 electrify boot.img, you could probably flash it through fastboot if it'll let you
Sent from my sunfire using xda premium
hoslayer13 said:
Can you get into fast boot by pressing power and volume-down? If so, you just need to wipe everything using "fastboot -w" and rebooting into RSD mode to flash the uscc sbf.
When you flashed cm10, the kernel is not compatible with the bootloader you're on.
If anyone has the 2.3.5 electrify boot.img, you could probably flash it through fastboot if it'll let you
Sent from my sunfire using xda premium
Click to expand...
Click to collapse
Thank you for the reply.. when I press volume down and boot on it says " nv flash mode" then turns off unless hooked in a computer then just stays on that screen
If I press volume up and turn on it says fast boot protocol support and Is half recognized in rsd ITE
If I just power no volume press on it says failed to boot 2 starting RSS mode..
I'm sort of new to everything and need more details.. tryed wiping using fast boot u downloaded but gives error.. same with flashing yes cellular sbf in RSd lite trying all 3 button combos that work
Please I need this phone working.. I messed up someone's phone saying I could put cm10 it for Christmas! Any help would be awesome
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
I think I bricked my device big time in an effort to return to stock. I flashed 4.5.141 and later got a system update while bootloader was unlocked. I got Failed to boot 4.
Later, I tried to relfash the same 4.5.141 sbf and it failed to flash and I got "Failed to boot 1".
Now, I thought I will try to flash again using RSD lite and tried to get into RSD Mode using Vol Down+Power. I am supposed to see options to navigate to RSD and press Vol Up. The first option appears for half a second and the screen turns off.
I am not sure what this behavior is. However, it stays on if battery is low. It stays in NV Flash mode with a message "Battery too low... blah"
I tried to put into fastboot mode and did "fastboot reboot-bootloader". It rebooted but it does not get into RSD Lite mode. It just shows Failed to boot 1. I know how to fix Failed to Boot 1 issue. But this failure to enter RSD mode is killing..
Any one encountered this? Any help here please?
I got out of this problem by using sbf_flash and unlocked the bootloader (with pudding one). That unlocked my bootloader and my Vol Down+Power menu was accessible. And, I went to recovery, performed a wipe and rebooted.
Voila.. It booted very well. I am now in the latest stock. I went all the way from 2.3.6->4.1->4.4.4->Mokee 5.0 and then back to sweet old stock 2.3.6.
My experience with Atrix had been awesome from 2013 where i installed CM 10. It is a great phone and now it works as a music player for me.