Hi I would like someone to help me, I bought a Motorola Atrix 1 week ago from ebay, and this atrix was updated by the seller to 4.5.91 with Android 2.3.4.
I unlocked the bootloader all went fine after that I installed CWM everything was great until I wanted to install Cherry Blur.... I flashed it and when I rebooted everything it just stucks on a Infinite Boot Loop...
What should I do I cant flash anything else and dont know how to mount the phone internal storage to flash a new zip.
Please Help
Pull Battery if you havnt already hold Volume down and power button
when you go to boot your phone back up. hold until it says fastboot
Use volume down to cycle thur menu then up to select android recovery
Once in recovery go to wipe / factory reset ( WIPE )
Then Wipe Cache
Then Scroll down to Mount
Scroll all the way down to Mount as USB plug your cable in
and it should show you your ext sd card must have one .
Copy a Fruit cake file or Kenneth build of gingerbread or w/e.
Then go back to install it.
awca22 said:
Hi I would like someone to help me, I bought a Motorola Atrix 1 week ago from ebay, and this atrix was updated by the seller to 4.5.91 with Android 2.3.4.
I unlocked the bootloader all went fine after that I installed CWM everything was great until I wanted to install Cherry Blur.... I flashed it and when I rebooted everything it just stucks on a Infinite Boot Loop...
What should I do I cant flash anything else and dont know how to mount the phone internal storage to flash a new zip.
Please Help
Click to expand...
Click to collapse
sounds like a bad flash...reflash again...if same problem occurs...download the file again and restart the procedure....
awca22 said:
I unlocked the bootloader all went fine after that I installed CWM everything was great until I wanted to install Cherry Blur.... I flashed it and when I rebooted everything it just stucks on a Infinite Boot Loop...
Click to expand...
Click to collapse
This happened to me yesterday. For me it was a case of grabbing the wrong CMW file. In my zombie state I somehow grabbed the 2nd newest. Worked fine after that.
Sent from my MB860 using XDA App
Help please...
I tried to flash CM7 onto my unlocked motorola Atrix 4g. Before doing so, I made a restore with Clockwork recovery and proceeded to flash the CM7 beta found on XDA. Before flashing, I made sure to wipe data/cache.
After doing this, my phone is stuck on the boot screen. I tried using the backup that I made to restore, but it says "can not find system.info" and finished. Then when rebooting it is still stuck at the boot screen.
Worst of all, my battery is now dead and wont charge! I searched and did some things in fastboot to try to fix it, but whenever I try to use fastboot, it gets stuck on "waiting for device".
Is there any way that I can save my phone or am I done for?
asdad123 said:
Help please...
I tried to flash CM7 onto my unlocked motorola Atrix 4g. Before doing so, I made a restore with Clockwork recovery and proceeded to flash the CM7 beta found on XDA. Before flashing, I made sure to wipe data/cache.
After doing this, my phone is stuck on the boot screen. I tried using the backup that I made to restore, but it says "can not find system.info" and finished. Then when rebooting it is still stuck at the boot screen.
Worst of all, my battery is now dead and wont charge! I searched and did some things in fastboot to try to fix it, but whenever I try to use fastboot, it gets stuck on "waiting for device".
Is there any way that I can save my phone or am I done for?
Click to expand...
Click to collapse
take your battery out and plug your phone into a wall charger. Then place the battery back in and let your phone charge.
After that fastboot flash romracer's recovery from the dev section. Reinstall cm7 and enjoy!
Sent from my MB860 using xda premium
Doing that to charge the battery didnt work
Also, I tried using romracer's recovery last night before the battery died, but it kept getting stuck on "waiting for device"
Did I use a wrong version of fastboot or something?
asdad123 said:
Doing that to charge the battery didnt work
Also, I tried using romracer's recovery last night before the battery died, but it kept getting stuck on "waiting for device"
Did I use a wrong version of fastboot or something?
Click to expand...
Click to collapse
http://www.youtube.com/watch?v=9pYcgmLhUcQ
follow the instructions in that video to charge your phone, use a SPARE USB CABLE. do NOT hack apart your Motorola charger, you can pick up a USB cable for 2-3 bucks off the internet.
download the fastboot files from here: http://forum.xda-developers.com/showthread.php?t=1138092
after you get your phone charged (let it charge for about half an hour with that method) try to boot into fastboot and do a fastboot -w (this will wipe EVERYTHING)
download the latest recovery from here: http://forum.xda-developers.com/showthread.php?t=1204500
after you fastboot -w, you should flash Romracer's latest recovery by doing the command 'fastboot flash recovery <recovery.img name goes here>'
then boot into recovery mode and wipe Dalvik Cache, wipe Data, and wipe Cache.
after that, install CM7 beta. or any other ROM you want. you should proceed to make a backup immediately after your first boot into the device.
please don't ever try to flash anything if your phone is not at 100% charge.
Woo Thank you guys!
I went to a best buy and they switched out the battery for me and I was able to fix it with the directions you guys provided! Thank you so much!
Happened to me too. Minus the dead battery part. It was fine till I tried flashing fauxs 1.3ghz kernel. Then all hell broke loose
Sent from my MB860 using XDA App
I follow your instructions and i revived my atrix
thaks you so much!!!!
10 character
I cant get it to boot in recovery(CWM) It comes up a big list of RSD BP Tools all that in a single page in white text when i try to enter recovery or any mode. And i cant get the RSD Lite drivers to install!! I already have used RSD lite 2 days ago with my phone. I managed to get phone into RSD mode once but it still wouldnt show up under the actual RSD Lite program, and it came up saying it failed to install drivers. It fails to install the driver "NS Flash Sunfire" and ive looked around and cant seem to find it anywhere.. I can get the phone into RSD mode fine, but it wont boot to CWM recovery, apparently something went AWOL. Tell me how i can get my photon back please?!
try removing all your motorola drivers and reinstalling them from yay 4 juggs link. you should be able to flash the sbf from his thread (in rsd mode) and be back in business.
Didnt even think of that.. i already had the 5.21 drivers installed, but sure enough did what you said and im flashing back to stock sbf right now. THANK YOU!
OK, so i just flashed 1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-198_6-CM-release-keys-signed-Sprint-US and now im stuck in a bootloop of the dual core screen.. Any ideas..? I know its not latest SBF, but the link for latest was dead.. So i just used this one i had on my desktop already. Anything im missing here?
EDIT: Oh yeah, the flash went through fine and said completed, and when i boot into recovery its back to stock recovery of android triangle and my bootloader menu system is how it should be again. Im just stuck in a boot loop.. Can i go ahead and like unlock bootloader and install CWM and get back on CM7 or will i most likely still be in a bootloop even after that..? Any insight would be great
w0lf215 said:
OK, so i just flashed 1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-198_6-CM-release-keys-signed-Sprint-US and now im stuck in a bootloop of the dual core screen.. Any ideas..? I know its not latest SBF, but the link for latest was dead.. So i just used this one i had on my desktop already. Anything im missing here?
EDIT: Oh yeah, the flash went through fine and said completed, and when i boot into recovery its back to stock recovery of android triangle and my bootloader menu system is how it should be again. Im just stuck in a boot loop.. Can i go ahead and like unlock bootloader and install CWM and get back on CM7 or will i most likely still be in a bootloop even after that..? Any insight would be great
Click to expand...
Click to collapse
you may need to factory wipe to get it to boot up... are you stuck on the dual core or the sprint now screen? it may be a bad flash as well - did it reboot by itself and such?
Im at the Dual core screen, i reflashed same sbf and its still doing same thing. ONE time it boot through the sprint now boot logo stuff, then just fell back into same old loop of just the dual core boot animation/screen. How can i factory reset it..? It rebooted right after it installed(never successfully into OS though) then RSDLite told me to manually power up phone, so i battery pulled and powered up to just have it go into moto dual core boot screen loop
Ok sweet i just unlocked bootloader and installed CWM and was able to restore to my CM7 backup fine! Im not activated atm, going to have to call sprint i guess.. But everything else looks to be working!!
Sorry if this is in the wrong thread, not sure where to put it,
I own a NATPC M009s x2.
I rooted it today and was hoping to install the cwm.
I had to install the driver manually so i tried to install it through the recovery mode
However after I did this the device wouldnt boot up past the boot logo and im not too sure what to do.
Unfortunately this is a soft bricked device now. You can either try to use ADB to attempt rebooting into recovery.
EDIT: If you do not have cwm successfully flashed, (this is based off of previous experience) there is no way to fix this. Please correct me if I am wrong, I rooted my first phone and factory reset it through the stock rom without a recovery. Sent the phone into a boot loop. I did write a program (Mango Tools) to help fix this however, it can be found on mellowdev.net It is being updated atm but wouldnt mind emailing it to you if you PM me.
Sent from my Nexus 4 using xda premium
I rolled back from MMROM to NOTTACHTRIX Today and now my phone is stuck in CWM. (Cold Boot Android by selecting Boot Anroid NO BP option doesnt work either).
I have flashed MROM, Neutrino, NOTTACHTRIX, CM10.120120720 and all ended up into clockwork mod recovery. Kindly tell me an alternative -.- I am stuck with this from past 12 hours and no luck.
Update
I have managed to boot into android using Cold Boot without BP (i-e GSM radio will be disabled). I am recharging my phone battery and experimenting.
Before flashing NOTTACHTRIX, my phone had SKT version of 2.3.5 v167. I directly went for unlocking bootloader blabla recovery to get the NOTTACHTRIX working (thats like 4 months ago when I bought this phone)
So I tried going back to a version near 2.3.5 or higher. So going for 141 AT&T version didnt seem a problem for me except the .91 version bricks the device if u downgrade from 2.3.5 or above.
RSD Lite gave me 0x703e error and I couldn't flash the stop sbf.
Second resort I did was flashing 2.3.5 and 2.3.6 fruitcakes and still ended up in recovery.
I can only coldboot into android with Neutrino ROM other roms give me rebootloop when I choose coldboot.
I am suspecting a corrupted system or some kind of corrupt script in boot which keeps me in a loop into recovery. I did try adb script for ASUS TF101 to exit recovery bootloop but to no luck.
Also, I tried exitrecovery.zip flashable and still couldnt get into regular android OS.
This device is a headache for me now -.- and seemingly no one bothers to reply or to help me solve this issue >_>
Thanks for reading atleast
Update 3
Fixed it myself.
I downloaded fastboot, 2.3.6 fruitcake (system and boot), the older clockwork mod recovery, the one comes with Bootloader unlocking not some 5.0 version.
All I did was erased RECOVERY from fastboot, then boot and system. Frasled boot and system. Rooted with the bootloader unlocker package. Installed the old recovery and flashed NOTTACHTRIX.
Did all rom u flash succesfull..or fail mount?
Can u mount/unmount system..data etc..
If no..then yr cwm was not fr yr models..try another version
Yr detail on process but without the error msg..if flash ok then should be boot if not it must giv aome error while falshing even its completed
Sent from my e2001v21_v89_jbl1a698_2g using xda app-developers app
mynonama said:
Did all rom u flash succesfull..or fail mount?
Can u mount/unmount system..data etc..
If no..then yr cwm was not fr yr models..try another version
Yr detail on process but without the error msg..if flash ok then should be boot if not it must giv aome error while falshing even its completed
Sent from my e2001v21_v89_jbl1a698_2g using xda app-developers app
Click to expand...
Click to collapse
It was the bug of rebooting into CWM recovery and yes I was using right recovery for my Atrix i-e Rom Racers. Right now I am 4.x recovery and that works 100% to my needs on NOTTACHTRIX
And I flashed the fruitcake using fastboot. No flashing of stock sbf
Please help...recovery bootloop
dark_prince said:
It was the bug of rebooting into CWM recovery and yes I was using right recovery for my Atrix i-e Rom Racers. Right now I am 4.x recovery and that works 100% to my needs on NOTTACHTRIX
And I flashed the fruitcake using fastboot. No flashing of stock sbf
Click to expand...
Click to collapse
I have the same problem and tried several CWMs, and TWRP.
I can only boot to recovery, unless I try to boot with the BP HW Diag & Boot AP. Then I can cold-boot into Android, but with no USB support (so no ADB or charging capabilities).
I should have left my phone alone...I was running Nottachtrix just fine. Tried to flash CM 7 and then encountered this problem.
I have tried to restore, flashed new Roms, flashed new recoveries, flashed new boot.img, etc. No luck yet.
Tried the exitrecovery.zip, scripts to reset boot flags, full wipe and reload nottachtrix, flash radio, etc.
Still no luck.
Tried CWM version 4.xxx following instruction above, flashed fruitcake, rooted...still no luck.
Anyone have any advice?
Thanks in advance.
noobButStudying said:
I have the same problem and tried several CWMs, and TWRP.
I can only boot to recovery, unless I try to boot with the BP HW Diag & Boot AP. Then I can cold-boot into Android, but with no USB support (so no ADB or charging capabilities).
I should have left my phone alone...I was running Nottachtrix just fine. Tried to flash CM 7 and then encountered this problem.
I have tried to restore, flashed new Roms, flashed new recoveries, flashed new boot.img, etc. No luck yet.
Tried the exitrecovery.zip, scripts to reset boot flags, full wipe and reload nottachtrix, flash radio, etc.
Still no luck.
Tried CWM version 4.xxx following instruction above, flashed fruitcake, rooted...still no luck.
Anyone have any advice?
Thanks in advance.
Click to expand...
Click to collapse
did you try the updated and usually standardly used CWM, 5.0.2.6?
palmbeach05 said:
did you try the updated and usually standardly used CWM, 5.0.2.6?
Click to expand...
Click to collapse
Yes, thanks for the reply. I tried this one, and the CWM touch version advertised as designed for this phone model. No luck.
Aaaand.....I got impatient and tried to flash an sbf. Stupid, I know. Now, I have a shiny new brick.
Oh well, I ordered a new one from ebay, and I will spend my free time learning about possible ways to unbrick a phone.
noobButStudying said:
Yes, thanks for the reply. I tried this one, and the CWM touch version advertised as designed for this phone model. No luck.
Aaaand.....I got impatient and tried to flash an sbf. Stupid, I know. Now, I have a shiny new brick.
Oh well, I ordered a new one from ebay, and I will spend my free time learning about possible ways to unbrick a phone.
Click to expand...
Click to collapse
What's the msg that your brick is giving you? did you try flashing the pudding sbf and then trying to flash a custom ROM?
Resolved!
palmbeach05 said:
What's the msg that your brick is giving you? did you try flashing the pudding sbf and then trying to flash a custom ROM?
Click to expand...
Click to collapse
So here's the full story:
It would boot up and say "failed to boot 1"
It would not boot into fastboot(power on while pressing vol down). When I tried to boot into RSD(power on while pressing vol up), it would give the same error and say "PWR REASON PWR KEY PRESS" and then say Fastboot Protocol Support.
Using RSD, it would recognize the phone as being in fastboot mode, and any flashes would fail...including pudding.
Using fastboot, it would connect but give errors if I tried to flash or erase anything, like it was locked. When I tried to unlock again, it would say " OEM unlock not implemented."
This is why I figured it was bricked...the bootloader seemed hosed. Couldn't use RSD, and fastboot was useless.
But...after screwing around with it (battery pulled and re-inserted while holding various buttons) while connected to RSD, I noticed that the same error was there but somehow RSD recognized it! (I think the magic combo was to hold power and vol up while actually inserting the battery.)
So I flashed pudding, and it worked! Re-rooted, loaded CWM (using auto unlock 4.2), and the phone booted to stock config. It was still acting flaky (I don't think the sbf had loaded right), and it was unable to boot back into recovery, but I flashed CWM again using rom manager and was able to do a full recovery!
Yay!! I am ridiculously happy right now!
Anyway, when my ordered phone comes in, I will have a spare to play with. This one is staying as is from now on. (until I get bored again)
noobButStudying said:
So here's the full story:
It would boot up and say "failed to boot 1"
It would not boot into fastboot(power on while pressing vol down). When I tried to boot into RSD(power on while pressing vol up), it would give the same error and say "PWR REASON PWR KEY PRESS" and then say Fastboot Protocol Support.
Using RSD, it would recognize the phone as being in fastboot mode, and any flashes would fail...including pudding.
Using fastboot, it would connect but give errors if I tried to flash or erase anything, like it was locked. When I tried to unlock again, it would say " OEM unlock not implemented."
This is why I figured it was bricked...the bootloader seemed hosed. Couldn't use RSD, and fastboot was useless.
But...after screwing around with it (battery pulled and re-inserted while holding various buttons) while connected to RSD, I noticed that the same error was there but somehow RSD recognized it! (I think the magic combo was to hold power and vol up while actually inserting the battery.)
So I flashed pudding, and it worked! Re-rooted, loaded CWM (using auto unlock 4.2), and the phone booted to stock config. It was still acting flaky (I don't think the sbf had loaded right), and it was unable to boot back into recovery, but I flashed CWM again using rom manager and was able to do a full recovery!
Yay!! I am ridiculously happy right now!
Anyway, when my ordered phone comes in, I will have a spare to play with. This one is staying as is from now on. (until I get bored again)
Click to expand...
Click to collapse
The RSD issue and not being able to do anything. you are the 4rd person that i've dealt with to have that issue. we had a guy on here a few wks ago that me and andresrivas were trying to help. he wasn't getting the bootloop you were getting, but he had a very similar issue and had the RSD issue. like a wk later, i ended up having the RSD issue as well. Andresrivas also has experienced this issue. All i know is flashing that pudding is what saved us as well.
Idk what ROM you're going to put on there, but i would definitely keep that spare around. if your digitizer dies, you have a backup digitizer