Hello, im coming from Defy to Atrix, mine is Brazilian 2.3.6 Retail, and just unlocked the bootloader using Bell SBF. After installing RomRacer CWM (recovery-atrix5.img) using the fastboot method, my phone went in a continuous bootloop. Fastboot mode shows me an error something like FAILED TO EXECUTE COMMAND %e (a0cccx) that repeats and scrolls down the screen in red lines. I have to pull battery to stop this. RSD mode reboots the phone. Android Recovery shows me "Entering Android Recovery Mode" and after that phone hangs. To have the things worse, battery drained down.
After charging the battery using an universal charger, phone started, but when Android loaded, it hanged everything. I had to pull the battery. After that, phone went in bootloop again. I got into fastboot, wiped everything. After that i was able to get into Android Recovery, wiped everything again and tried to start the system, no luck. It went in bootloop again and the message in fastboot mode came on again.
One more point is, when the battery in on the phone, the phone is getting really hot.
I was using the phone for about 5 hours before messing the whole thing up, if i have it working again, i will stick with original firmware. No more customizing on this Atrix as long as its really easy to hardbrick. Im afraid that i did this to mine.
Defy is almost impossible to hardbrick. And its bootloader is locked. I see no goodness on having a phone that is that easy to kill... Please help me................
look into flashing an sbf on your atrix. puts it back to stock firmware.
if youre only soft bricked this will fix it. or try going to android recovery ( if it still has the original) and do a factory data wipe.
hope i helped!
I recommend you to download again RomRacer CWM
enter fastboot mode and flash again CWM (in case your download is corrupt)
type "fastboot devices" Press Enter.
type "fastboot erase recovery" Press Enter.
type "fastboot flash recovery recovery-atrix5.img"
if this didnt fix it
perform a full fastboot wipe
http://forum.xda-developers.com/showthread.php?t=1421261
and then try to reflash the recovery. if u cant fix it this way flash a sfb!
Related
So I have a rooted, unlocked atrix 4g running nottachtrix 1.3.1 (which is based off of 2.3.6 and the 4.5.141 OTA). anyway, the phone worked fine for a couple of weeks after i bought it. SOOOO I bought a lapdock just to use for long car rides and stuff (big screen movies). after about three days with the lapdock the phone started acting up so I wiped dalvik/factory restore/wipe data and reflashed Nottachtrix. Then it would boot up to Motoblur registration and after 2 seconds, shut off. So I did the restore process again and now the phone will only boot to the M logo.
I can pull up the "fastboot" menu but it won't actually open those options. For example, if i choose android recovery, the phone will stay on the M logo and say "starting android recovery" but it won't ever get to the recovery. This applies for all the fastboot options and also for just booting up normally (just stays on the M logo forever).
I read somewhere ( i think it was here) that some people are having a similiar problem and it can be fixed by using RSD and flashing an sbf (would that be alright with my unlocked 4.5.141?) and the problem originates from a problem in the webtop partition (which makes sense considering my recent use of webtop). However, as I can't get into rsd can someone help me? has anyone else had this problem?
Sorry didn't mean to thank you. My hyper kitten did that.
one of the thread i read earlier about a problem similiar to mine, someone did the same thing (accidentally thank someone)
Needs to be a way to unthank. Lol. Hope you get your problem fixed.
bumpo
I would try flashing the 2.3.6 sbf using rsd lite. That would at least get you back to stock, and you could start over.
I also use nottachtrix and I have no troubles, so I do not think it is your problem.
After flashing, if that doesn't fix it for you, you are ready for warranty, and they are being very generous with replacement at the moment. But go straight to Motorola, not where you bought it. If you bought it used, don't offer that info, they don't even ask that question.
Good luck.
Have you tried going to fastboot mode directly while booting up. (Volume up)
I faced similar issue while flashing a rom (no dock though).
Deleted the data (fastboot -w), wiped the caches, and luckily it worked. Then I could go into recovery and flash another rom.
Sent from my Moto Atrix using Tapatalk
except i can't get into fastboot or rsd. it will show that option and say "starting Rsd protocol" but it won't actually start the rsd protocol (atleast my computer doesn't recognize it)
i can get into CWM recovery, though i have to turn it on, selecet android recovery, and then plug it into the lapdock.
DO NOT USE RSD UNLESS UR LIFE DEPENDS ON IT.
if u can get to recovery and fastboot then do this via fastboot.
All CRAP REMOVING
fastboot erase boot
fastboot erase system
fastboot erase webtop
fastboot erase userdata
fastboot erase cache
fastboot erase preinstall (not required)
fastboot -w (redundant, wipes userdata and cache)
and if possible reflash ur recovery too (might be the problem maker.
and then re-download ur favorite ROM and flash again.
I had such problems in gobstoper (bell stock) and this trick helped me a lot.
now i do this all the times.
There's a TL;DR at the end !
Hi - I hope you will be able to help me !
I have a XT910 Motorola Razr from Rogers in Canada.
I've had a Nexus S for a long time and I guess I wasn't prepared for a phone that wasn't as friendly to modding and flashing.
Before trying to flash a version of CM10 found here in the forums, I installed CWM Touch and made a nandroid backup - standard stuff.
What I didn't realize until it was too late is that booting into recovery DOES NOT boot CWM Touch - but rather the regular android one - the one that does not allow you to do much other than to factory reset.
I found out about RSD Lite but not until my battery wasn't charged enough and couldn't do anything about the phone.
I searched for the longest time on a LOT on different forums about how I could fix this and resorted to getting a factory cable - which works.
So, now, I can flash stuff using fastboot. Great, right ? Well, I still can't get things working.
RSD Lite doesn't detect my phone, and I believe that's because ADB doesn't detect it as well - so I tried that alternative way to flash fastboot files provided by the eternity project.
I've tried various fastboot packages but to no avail.
The best I can do is to get past the motorola logo - then black screen. Otherwise, I get boot or flash failures and get sent back to fastboot.
When the phone is on the black screen and that I plug a USB cable to my phone, Windows sees the device but it doesn't recognize it - I assure you I've tried all the different drivers to try and get it to work. Nothing.
Worth mentioning - I often get errors "Preflash validation failure" when trying to flash stuff.
I really feel I could fix this issue by flashing an IMG version of CWM touch or some other sort of recovery so that I can recover using a nandroid but they are no where to be found ! I can't believe that all recovery options are installed by APKs.
Any ideas ?
TL;DR, XT910 went boot looping after trying to flash CM10 - resorted to getting a factory cable and even then, can't get the phone back into working condition. Phone is detected by fastboot but not ADB.
Thanks !
first... the battery is the problem
this article can help...
How to Boot your Phone on Low Battery with Fastboot Flash Failure
To boot your phone on low battery where you get stuck on fastboot flash failure, hold down Volume Up and Volume Down then plug in “AC” USB charger to your Droid Razr. This will give you the bootloader menu upon where you can choose “Normal Recovery” to boot. If your phone doesn’t boot here, it will at least re-charge the battery normally instead of being stuck on fastboot flash failure which will re-charge your phone “very very slowly”.
I had JB 4.1.2 on my Razr (Verizon/Motorola stock build).
The phone was rooted but bootloader was untouched.
I used FontChanger to change a secondary font, and upon rebooting it would not get beyond a point in the bootup animation.
A factory reset did not yield success.
There is no 'safe mode' option...
Is there a way to download a zip file to the external SD card and use recovery mode to flash the original ROM?
Thanks!
You don't have safe strap or bootmenu installed?
Sent from my XT910 using xda premium
Go into fastboot mode and use this: http://www.droidrzr.com/index.php/t...xt912-jellybean-windows-mac-linux-all-in-one/
dpcole72 said:
I had JB 4.1.2 on my Razr (Verizon/Motorola stock build).
The phone was rooted but bootloader was untouched.
I used FontChanger to change a secondary font, and upon rebooting it would not get beyond a point in the bootup animation.
A factory reset did not yield success.
There is no 'safe mode' option...
Is there a way to download a zip file to the external SD card and use recovery mode to flash the original ROM?
Thanks!
Click to expand...
Click to collapse
Might wanna Try RSDLITE
here's tutorial:
I've tried all that and more.
RSD Lite and finding a ROM (SPYDER) ultimately fails because AP Fastboot states "Phone is LOCKED" and status code 0. To my knowledge, the bootloader can't be broken for the original Razr Maxx, so I have to find a way to get around that...
"AP fastboot flash mode (0) Recipe Failure)"
I did see the qe code go from 1/1 to 0/1 while flashing ROMs with RSD Lite, though...
I did re-flash the original Motorola 98.72.8 JB upgrade via Recovery Mode and using the phone's "install upg from external drive", which I could not do in an earlier attempt, but when rebooting that AP fastboot lock screen appeared right away. Erasing the cache partition then doing a factory reset.
AP fastboot flash mode is v0.77.
RSD Lite is v6.1.5.
what else can I try, if anything?
Thanks!
UPDATE
Oh, I held down all 3 buttons and did another power-up, to get around the AP Fastboot lock screen that keeps showing up - this time I selected "boot normally" -- it is booting into the OS and I am moving forward.
If I reboot again, but if I don't do the three-button salute at the time of powerup, I get the "LOCKED" fastboot screen again. Doing the 3-finger salute and going into 'boot normal' gets around the LOCKED error and all becomes well. Should I count my blessings, as I'll be ditching this phone in a couple months, or should I go for the gold and try to fix this remaining hiccup?
And is it possible to get the qe code back to 0/0?
Thanks!
dpcole72 said:
Oh, I held down all 3 buttons and did another power-up, to get around the AP Fastboot lock screen that keeps showing up - this time I selected "boot normally" -- it is booting into the OS and I am moving forward.
If I reboot again, but if I don't do the three-button salute at the time of powerup, I get the "LOCKED" fastboot screen again. Doing the 3-finger salute and going into 'boot normal' gets around the LOCKED error and all becomes well. Should I count my blessings, as I'll be ditching this phone in a couple months, or should I go for the gold and try to fix this remaining hiccup?
And is it possible to get the qe code back to 0/0?
Thanks!
Click to expand...
Click to collapse
I'd honestly try fixing it, as that'd be a pain in the ass every boot. Did you have plenty of battery when you tried AP Fastboot mode? Being under 15% will cause any effort to flash to fail.
I kept getting the "set metadata error" on the latest Android Revolution HD rom so installed the latest version of CWM recovery but I kept getting the same error upon installing the rom. However, this time my phone is really screwed up. I cannot get back into CWM to restore my last backup, when I get the little "entering recovery" text on the top of my phone the screen goes black and then flashes something on the screen and that's it. I plugged the phone into my pc and followed the instructions for flashing TWRP recovery but again...when I try to enter recovery this time the TWRP log flashes and then it disappears. For some reason it also appears I am S-ON now as well! I can connect the phone and go to FASTBOOT USB and type "fastboot devices" and my phone shows up but no matter what I do I cannot get into TWRP to restore. What the heck do I do?!
type fastboot clear cache and try again
So my friend was trying to get some stupid game to work on my phone that my phone didn't support, so he tried replacing the build.prop for my Pantech Flex with one for the Galaxy s3. Which needless to say bricked it.
I can start up the phone, and I assume it starts up normally and goes to the lock screen. But everything after the pantech logo is black screen.
Here is what I've tried:
1. Pulling my current build.prop and editing it, then pushing it back with ADB. Pulling it works, but when I push it, nothing seems to happen. It says "Success" but when rebooting the device, my phone is still ****ed up. And when I pull the build.prop back again, it's the one for the Galaxy s3 and not the one I just pushed.
I read that the reason this is happening is because ADB doesn't have root permissions. Not sure if thats true though, as I obviously have rooted my phone.
2. Booting the device into recovery. For a while now, trying to boot into recovery leaves me stuck on the Pantech logo. I think this may be due to me flashing a recovery that wasn't for my device a while back. So I can't get into my recovery to factory reset it.
3. Booting into fastboot mode. The Flex is a strange creature, so there is no standard bootloader apparently so when using "adb reboot bootloader" it reboots into fastboot instead of a bootloader. Meaning on the screen is just white text saying "FAST BOOT mode" and adb disconnects, and fastboot devices sees the device now.
Trouble here is, I have the stock recovery for the Flex. But when I use Fastboot boot recovery.img or Fastboot flash recovery recovery.img or fastboot wipe data or anything in fastboot really, I get a "Not support!!" error. Which I assume means my phone is a piece of **** and can't be used with fastboot.
So now I'm at my wits end and don't know what else to do. I am dead broke and need my phone for work.
Is there anyway I can fix the build.prop or factory reset my phone?
Fukesh said:
So my friend was trying to get some stupid game to work on my phone that my phone didn't support, so he tried replacing the build.prop for my Pantech Flex with one for the Galaxy s3. Which needless to say bricked it.
I can start up the phone, and I assume it starts up normally and goes to the lock screen. But everything after the pantech logo is black screen.
Here is what I've tried:
1. Pulling my current build.prop and editing it, then pushing it back with ADB. Pulling it works, but when I push it, nothing seems to happen. It says "Success" but when rebooting the device, my phone is still ****ed up. And when I pull the build.prop back again, it's the one for the Galaxy s3 and not the one I just pushed.
I read that the reason this is happening is because ADB doesn't have root permissions. Not sure if thats true though, as I obviously have rooted my phone.
2. Booting the device into recovery. For a while now, trying to boot into recovery leaves me stuck on the Pantech logo. I think this may be due to me flashing a recovery that wasn't for my device a while back. So I can't get into my recovery to factory reset it.
3. Booting into fastboot mode. The Flex is a strange creature, so there is no standard bootloader apparently so when using "adb reboot bootloader" it reboots into fastboot instead of a bootloader. Meaning on the screen is just white text saying "FAST BOOT mode" and adb disconnects, and fastboot devices sees the device now.
Trouble here is, I have the stock recovery for the Flex. But when I use Fastboot boot recovery.img or Fastboot flash recovery recovery.img or fastboot wipe data or anything in fastboot really, I get a "Not support!!" error. Which I assume means my phone is a piece of **** and can't be used with fastboot.
So now I'm at my wits end and don't know what else to do. I am dead broke and need my phone for work.
Is there anyway I can fix the build.prop or factory reset my phone?
Click to expand...
Click to collapse
Also, maybe there is a way to set up a VNC server of some sort to use the phone from the computer??