Related
I am running 2.2.2 Froyo with 1.77 build.
I unlocked and rooted via Gingerbreak.
I went into CWM Recovery, erased all cache and flashed Alien Rom v3 and immediately flashed the Alien theme over it (I think that is where I made my booboo). The Rom appeared to load perfectly yet when the phone restarted the Moto logo animation appeared to run then the screen would go dark. This process repeats every few seconds non stop.
I can get into Android Recovery, RSD, everything. I tried flashing the 1.8.3 sbf through RS Lite 5.3.1 and while it said "PASS" it still hangs at the Moto animation.
I have no idea what to do. I think I can get out of it as I have done A LOT of searching through the forums and google but I am terrible with CMD.
Any helpful and/or useful advice?
Try restoring a backup, if not try to flash a fruitcake
http://forum.xda-developers.com/showthread.php?t=1163009
Sent from my MB860 using XDA App
Thanks for the thread. However it looks like I need CWM Recovery in order to flash a fruitcake? I cant get the phone to boot past animation so this wont work...
Also I didnt create backups
noxlo said:
Thanks for the thread. However it looks like I need CWM Recovery in order to flash a fruitcake? I cant get the phone to boot past animation so this wont work...
Also I didnt create backups
Click to expand...
Click to collapse
Are you unlocked and flashed cwm through fastboot, or did you use the system recovery app?
Sent from my MB860 using XDA App
System recovery app. I can access Androids recovery (obviously) but not many options...
Did you unlock your bootloader?
I ran into the same issue the first time I tried to flash Alien. Since you're flashing Alien, I assume your bootloader is unlocked (As it's required for Alien).
If you have an unlocked bootloader, do this:
EDITED: Apparently, I'm a new user and can't post links. Go to the address bar and replace the number with 1163342
Use Fastboot to flash the boot.img and the system.img files. This will give you Gingerbread/Motoblur like it comes out of the box. (It's a start!)
Thanks for the link. Will try when I get home. If I can just get past cmd...
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!!
Things went from bad to worst, I fixed my market update and had the utlities on the device i needed to i tryed flashing the Neutrino Rom.
After it was done it rebooted and said "failed to boot 2 starting rsd".
So I downloaded RSD Lite and found the unlock SBF which I applied. Now I can get into the FastBoot menu's and go to Android Recovery and try to do the back to stock option, it says it completes then reboots...
Then it just sits and sits and sits on the motorola Dual core logo.
Can someone please help me here. I cant seem to find any of my backups i made with system recovery or rom manager. I also didnt load RomRacers Recovery (which i just now noticed)
Any help is greatly appreciated.
So, did you unlock the bootloader before trying to flash the ROM?
Does it say "Unlocked" at the boot logo now?
Get back into fastboot and flash romracer's recovery and then try to mount the storage and get another rom on there.
SDRAKE101085 said:
Things went from bad to worst, I fixed my market update and had the utlities on the device i needed to i tryed flashing the Neutrino Rom.
After it was done it rebooted and said "failed to boot 2 starting rsd".
So I downloaded RSD Lite and found the unlock SBF which I applied. Now I can get into the FastBoot menu's and go to Android Recovery and try to do the back to stock option, it says it completes then reboots...
Then it just sits and sits and sits on the motorola Dual core logo.
Can someone please help me here. I cant seem to find any of my backups i made with system recovery or rom manager. I also didnt load RomRacers Recovery (which i just now noticed)
Any help is greatly appreciated.
Click to expand...
Click to collapse
i unlocked the bootloader after the update failed (i panicked) and yes it does say unlocked at the top now
Well, you mentioned you can get into fastboot so that's a start. You can try to flash a proper recovery and try to boot into recovery and see if you can mount the storage, or if you have a card reader you can just put a ROM on your sd card and then flash. If you can't get into recovery but you can get into fastboot you can flash a rom that way. You'll have to search for the procedure but I'm almost certain it can be done. If all else fails, you can install the unlocked "Full" SBF through RSD Lite, but it is not really recommended but should work.
SDRAKE101085 said:
i unlocked the bootloader after the update failed (i panicked) and yes it does say unlocked at the top now
Click to expand...
Click to collapse
Thanks so much. I got radracers on there and reflashed the neutrino rom again. Everything appears to be working. Now to just figure out the rest.
Thanks again.
Look tke the sd card and load the rom and google apps. Then go and fastboot wipe and re install the rom and try to boot honestly it just sounds like you got a corrupted rom
Rooted a atrix 4g AT&T US.
I had the stock rom running after root, then when I tried to setup a custom rom it wont get past the M logo. I can get into fastboot but when I try to flash any system.img it says the file is too large. I tried erasing system, boot and data, then got into CWM and tried to install from zip. It runs and says it finished. but still no boot. I dont know what else to try. any ideas?
did you format system, data, cache in advanced menu in recovery?
Sent from my MB860 using xda app-developers app
I noticed only one important thing missing from your post, did you unlock the bootloader first? Rooting is totally separate from being able to install custom roms.
jpaytoncfd said:
Rooted a atrix 4g AT&T US.
I had the stock rom running after root, then when I tried to setup a custom rom it wont get past the M logo. I can get into fastboot but when I try to flash any system.img it says the file is too large. I tried erasing system, boot and data, then got into CWM and tried to install from zip. It runs and says it finished. but still no boot. I dont know what else to try. any ideas?
Click to expand...
Click to collapse
So I used fastboot to flash a new recovery (http://forum.xda-developers.com/showthread.php?t=1204500) Worked like charm, Roms load correctly and are loading great. (Although the one I am trying right now is stuck on the boot animation) I did have one loaded and working in only a few seconds after updating the recovery.
Hope this helps someone else.
jpaytoncfd said:
Rooted a atrix 4g AT&T US.
I had the stock rom running after root, then when I tried to setup a custom rom it wont get past the M logo. I can get into fastboot but when I try to flash any system.img it says the file is too large. I tried erasing system, boot and data, then got into CWM and tried to install from zip. It runs and says it finished. but still no boot. I dont know what else to try. any ideas?
Click to expand...
Click to collapse
Try to restore to the stock rom with the RSDlite method, it's the most simple.
Then check the automatic unlock and root for the atrix, it's a command line program that makes everything by itself, it must be somewhere here in the top guides of this forum
joelorona said:
Try to restore to the stock rom with the RSDlite method, it's the most simple.
Click to expand...
Click to collapse
Do NOT use RSD or SBF files. Use fruitcakes.
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