hi everybody I am new here and using atrix 4g and I need help I was update my att atrix 2.3.4 official gingerbread and today my phone is always restarting not opening . red motorola logo passing and att logo came then restart itself always doing this not giving any error . I can enter the fastboot menu and try to make android revovery but not working what is the problem do you know ? the phone heating
my advice:
try wiping data/cache first... if it doesn't help -> pull battery off... wait 2 minutes... put it back, power on in RSD mode (volume up + power)... flash official AT&T 2.3.4 SBF (if you don't care about unlocking or modding).... wipe data/cache...
Click to expand...
Click to collapse
I solved with wipe data option thank you so much
My gf's phone finally got the ICS OTA this morning and i managed to root it with no problems.
I was going to try out a new rom so i went through the safestrap process. Upon switching to safe mode, and trying a reboot, i get the menu to continue like normal, but then just a black screen.
I ended up having to force reset with the power and volume down button to get back to recovery. I was able to switch back to unsafe and successfully boot (thank god she woulda killed me if i bricked it or had to SBF lol).
Im curious why it did that tho, because obviously it needs to be in safe mode to rom.
Only thing i managed to find while searching was to update busybox but that didnt help.
vaeevictiss said:
My gf's phone finally got the ICS OTA this morning and i managed to root it with no problems.
I was going to try out a new rom so i went through the safestrap process. Upon switching to safe mode, and trying a reboot, i get the menu to continue like normal, but then just a black screen.
I ended up having to force reset with the power and volume down button to get back to recovery. I was able to switch back to unsafe and successfully boot (thank god she woulda killed me if i bricked it or had to SBF lol).
Im curious why it did that tho, because obviously it needs to be in safe mode to rom.
Only thing i managed to find while searching was to update busybox but that didnt help.
Click to expand...
Click to collapse
It was probably plugged into the charger, Safestrap has known issues with not going into recovery while on charge.
Is their any other ideas I have run into the same thing with my XT910 with the CM10 build
I am rooted but running stock ICS via the last OTA update. For the last few days, my RAZR has rebooted randomly when I would tap on an app notification from my status bar. It did not make a difference what the app was that I tapped the notification for. Sometimes it would reboot, sometimes not. This morning I woke up around 3 AM and tapped a notification. Of course my phone rebooted and now is stuck in the reboot animation. I tried booting into recovery, wiping cache, and rebooting. It did not work. After a couple of hours I gave up and decided to reset the phone to factory settings. Ah success or so I thought. I started to set the phone back up again but the phone rebooted and is once again stuck in bootloop. I am stuck now on what to do. Any suggestions?
I'd be using RSD software to flash a different stock Rom. Here is how and all you need:
http://forum.xda-developers.com/showthread.php?t=1539192&highlight=rsd
Just confirming that I've got an Australian RAZR, bought from Optus and I've flashed the European UK version without any problem. After RSD does the job, you may have to boot into Recovery and wipe the cache and data, just in case you get stuck in a bootloop.
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
Okay, so i rooted my phone and something went wrong and to fix it i thought i would wipe my phone but instead wiped the os on twrp so now my phone is basically ruined. I tried to flash the s and it worked but the installing took too long so i unpligged and now it is so now it is stuck on a page saying an error occurred while updating the device software. plug into smart switch emergency etc... so i did but it wouldnt come up on the emergency thing so im screwed?
cosmohamwee said:
Okay, so i rooted my phone and something went wrong and to fix it i thought i would wipe my phone but instead wiped the os on twrp so now my phone is basically ruined. I tried to flash the s and it worked but the installing took too long so i unpligged and now it is so now it is stuck on a page saying an error occurred while updating the device software. plug into smart switch emergency etc... so i did but it wouldnt come up on the emergency thing so im screwed?
Click to expand...
Click to collapse
What model is it?
Never unplug something when it says not too. Thats how you corrupt and ruin stuff.
Your phone is not broke.
Hold vol down + home + power until you get into download mode.
Flash stock firmware for your model.
Phone will be back on. While its installing apps and software do not turn off.
It can freeze at samsung logo for a while but this is normal on first boot.
If you give me the model number and what version you was on i can find you the firmware.