So last night something strange happened while wiping data/system. I guess someone unplugged my charger, or I had lower battery than I knew - because the power on the phone went out mid-wipe - or something.
The state of things: Currently when you put in the battery or try to boot it immediately loads a black screen with numbers and stuff instead of the usual Motorola symbol and battery charging and whatnot. This screen says things like:
PwrReason = POWER_OUT (if you just put in the batter)
PwrReason = Power_Key_Press (if I turn it on manually)
1 RSD
2 Fastboot
3 NVFlash
etc
And it gives the option to boot into RSD, fastboot, Android Recovery, etc.
RSD recognizes it as an 'engineering' model, and claims that I have bootloader version 0.00000007v or somesuch. Android recovery doesn't seem to work (or exist anymore, not even the stock version.
Plugging it in while powered off triggers the LEDs for charging/charged correctly, but not the motorola symbol or battery indicator.
If left at the current boot screen, it says:
Powering on BP
Reading_ODM_Fuse = 1
Cold_Booting_Linux
And boots into Cyanogen Mod correctly, data, phone, everything working.
I'd like to have recovery back - given that RSD recognizes it, should I try to return to stock by flashing an SBF? Should I leave well enough alone? What's the correct thing to do here - I do want to remain unlocked and on CM7, and I want my recovery mode back. All my music, files, etc are still on the device - nothing's missing.
Can you help?
Funny, the same thing happened to me yesterday. I didn't lose power or anything, I just flashed the newest CM9 alpha and when I rebooted it went to the same screen you are talking about. Everything still works fine like you said and I can still get into CWM and everything, just want to know why its going to this strange menu all of a sudden...
Sent from my MB855 using Tapatalk
Just reinstall cwm. Use adb method, or install bootstrap recovery and flash the zip version of cwm.
Sent from my Motorola Photon using Tapatalk
Related
Listen i'm somewhat new so forgive me if i posted in the wrong place.
Just hear me out please.
Ok heres a little s/a. I have a samsung vibrant, last night i flashed my vibrant which was on a rooted vibrant9 rom. To bionix 1.9.1 w/ jacs oc kernal and the voodoo lagfix. Before flashing to the bionix i switched the boot logo and .wav file to one i perfered, i also did the same for the shutdown logo. Now, per the instructions for installing bionix 1.9.1 i took a nandroid backup of my phone on vibrant9 before performing the flash. After i did i flashed using clockwork. Everything went fine, the phone flashed, rebooted and was working great. However i rebooted the phone and relized that the shutdown screen wasnt working as it should because i forgot to include the shutdown.cfg thats required. What i did was took the bionix.zip off my sd card went into it and added the .cfg file i needed. I added it back to the sd card and figured i'd just reflash and all would be fine. Not so lucky however, i tried to reflash using clockwork (which took me to the regular recovery menu you would get to holding down the volume buttons and power) and it failed giving me an error which said "error on line 80". Relizing that the instruction said that if you had the voodoo lagfix you should disable it, i decided to do a factory wipe of all data (thinking that would definitly disable voodoo) after the factory wipe i attempted to flash bionix 1.9.1 again with no luck. After the last attempt i decided to just restore using the nandroid backup of vibrant9 i had taken earlier, the phone went through the restore process with waht appeared to be no problems. After it finished i rebooted from the recovery menu then bammmm. The phone is stuck in a boot loop. Its not a normal boot loop though the initial samsung logo will pop up for a sec then the phone screen will show what looks like tv static for a sec, it just keeps repeating this. To get it to stop i have to pull the battery. Ive tried booting into recovery by holding the volume buttons and the power button, but all that happens is the phone starts into the above mentioned bootloop. As a note whenever i plug the phone up via usb to my computer a grey battery screen pops up but it dosent charge it just sits there, and if i unplug the usb it goes right back into the bootloop. Also my computer will not recognize the phone so using odin seems like a lost cause. I read in a forum for this phone just a bit earlier that its nearly impossible to brick this phone. Have i done the impossible?
Well it sounds like you have hardware locked phone. Also you cannot do a nand restore w/ voodoo enable. That's your problem. There are threads on xda about recovering hardware lock phones. You need to search. If you can get into download mode, you need to flash eugene373's "Froyo that does not brick". Also, once you get phone working, isuggest you keep a disable-lagfix zip on your internal sd.
Sent from my SGH-T959 using Tapatalk
Great Success
Ok, ok after what seems like a million tries i finally got my vibrant working. After finally getting my vibrant into download mode (by removing the battery, putting the battery back into the phone, holding down both volume buttons and plugging in the phone via usb) i used odin to try and flash back to the factory rom. The flash worked except for an error i noticed when the phone was kicked into factory recovery mode to format itself. There i noticed that at the point when all user data was supposed to be wiped it would have a failure to wipe data. After the flash completed with this error i was able to get past the boot loop. At this point my phone would finish the boot sequence but after the samsung s disappeared the screen would just stay black. However, when ever i pushed any of the soft keys on the front they would light up. So what i did was followed the instructions in the above post and used odin to flash eugenes froyo rom that wont brick. Again the flash would complete but when the phone was kciked into factory recovery mode i got an error and it wouldnt complete it would just hang. So what i did next was use odin to again flash the factory rom and to my surprise it worked. So my vibrant is now restored to its full glory. I owe everything to the patrons of this community. Thanks all.
Hey folks,
I'm having some issues with my ATT Atrix. The phone keeps rebooting at the "Rethink Possible" screen. I bought this phone off of somebody on CL. I actually had the phone make it past the att screen a couple times. It made it to the setup up Motoblur screen but when I clicked start it just skipped it and takes me to the "Emergency Calls Only" screen. However the phone would just restart eventually at this screen as well. When the screen timed out I could not get the screen to turn back on at this point unless I unplugged the USB cord and plugged it back in. When the phone was on the Emergency Calls screen, my computer did recognize the phone and it did launch the motorola website. While I had the phone at this screen it did say that it had to force close android.process.com. I am coming from a captivate with rooting and flashing roms so I am familiar with Android. I am just trying to figure out where the problem could be with my Atrix. I am hoping somebody can point me in the right direction. Thanks for your time!
Your best bet will be to SBF that back to stock. Have you tried that yet? If not search for RSD Lite and SBF in the forums. There are several links and guides.
Is it unlocked?
I am not sure if it is unlocked as I cannot get past the emergency call screen. However, I will search SBF and research that option of setting it back to stock. I know when I flashed roms on the Captivate I would enter into recovery mode. I see in the Atrix that I would have to use Fastboot? The only reason I am worried about flashing a rom is that the phone reboots on its own so I would not want to hard brick it if it rebooted during a flash.
If it's unlocked you should see the word "unlocked" in the upper left corner of the boot logo screen, unless it was unlocked then flashed back or fruitcake in which case it will not say unlocked.
You should not have issues flashing from recovery if you have enough juice in your battery, which you maybe don't if you have been letting it sit rebooting. The rebooting is more than likely caused by an issue with a kernel, ROM, etc. Think of recovery as being similar to the BIOS on a PC. You enter into BIOS before the OS boots, etc., and this is before all the hardware has initialized and drivers have loaded, so the problem causing the reboots should not exist at that time. I would definitely try flashing a different ROM, and also a stock kernel.
It never said unlocked when I got the phone to turn on. I am having trouble getting the phone to turn on this time. I have downloaded RSD Lite and the 4.5.91 .sbf file to flash. I am just having trouble getting the phone started. Are there any ways to force the phone on. When I press the power button the green LED stays lit but nothing comes on the screen. When I plug into the charger it shows the moto symbol then goes to the Battery charging screen. Im not sure if the battery is correct because it says BHX5 1500mAh on the battery. Thanks for your help guys!
Update: I can get the phone into Fastboot and then Android Recovery Mode when the phone is plugged into the wall charger. However when I connect the phone to the computer via USB it just shows the green led when the phone is powered on. Anyway I can get the phone to boot into Fastboot while connected to the computer via USB?
Bump. Any way to get the phone to turn on when plugged into the computer or anyone know why there would be an issue of the phone turning on when plugged into the wall charger but only showing the green led when plugged into the computer? The battery shows 100% charged. Thanks
Update: I got the phone into RSD mode and flashed the 4.5.91 sbf but the phone only goes to the Emergency Call Screen. Is there anything else that can be done?
nishith611 said:
Update: I got the phone into RSD mode and flashed the 4.5.91 sbf but the phone only goes to the Emergency Call Screen. Is there anything else that can be done?
Click to expand...
Click to collapse
Did you fastboot -w before flashing the sbf? (Guess you don't really need to when flashing a sbf)
What may also help is flashing the boot.img file from whatever ROM you are using via fastboot.
Don't know if this will help, but it solves an issue when flashing to a different ROM from CM7, so maybe will help for you.
I know this might sound dumb, but do you have a sim card installed? Also, try to boot into recovery and just do a factory reset. @CaelanT already pointed out that this should be unnecessary since you flashed an sbf but it wouldn't hurt to try.
nishith611 said:
Update: I got the phone into RSD mode and flashed the 4.5.91 sbf but the phone only goes to the Emergency Call Screen. Is there anything else that can be done?
Click to expand...
Click to collapse
EDIT: I reread the OP and realized he had already tried to bypass the start screen.
That is not the correct battery. That is actually a battery used for the Droid X/X2. It seems they have pulled a switch-a-roo on you. (Probably because the Atrix battery could be used as an "Extended" battery in the DX/DX2) Anyways, it should still work but you can find the correct battery online, it should be a BH6X and should have a capacity of 1880/1930mAH.
nishith611 said:
...Im not sure if the battery is correct because it says BHX5 1500mAh on the battery. Thanks for your help guys!
Click to expand...
Click to collapse
Thanks for the reply. I tried to get the phone into recovery mode. I get to the Exclamation Point screen but it gives me no options for a factory reset. I saw that you have to touch the lower right hand side of the screen, but this doesn't do anything for me.
As far as flashing the boot.img file for the rom that I used. I flashed the stock 4.5.91 motorola rom. How can I find boot.img and would I flash it using RSD?
Also would it help if I flashed a custom rom instead of the stock Motorola 2.3.4 rom?
Could the battery not being the BH6X rom be the issue for it not getting enough power to stay on by itself?
Thanks for the help guys, I really appreciate it!
No, the sim card was not installed during the flash. However, I did install the sim card afterwards but the phone boots up and goes to the big green battery charging screen and does not go any further. However when the sim card is not plugged in I can get the phone to go to the Emergency Call screen.
nishith611 said:
As far as flashing the boot.img file for the rom that I used. I flashed the stock 4.5.91 motorola rom. How can I find boot.img and would I flash it using RSD?
Click to expand...
Click to collapse
The following are the instructions for flashing the boot.img. this was the solution to bootloops when trying to restore to a different ROM after CM7, but as I said previously, you never know if it will help or not:
1.Open up the Zip file of your current Blur ROM (Ninja, CherryBlur, Alien, etc.)
2.extract the boot.img file and copy to the directory where your fastboot is.
3.Pull phone battery & reinsert
4.Power on phone and go straight to Fastboot mode (Power + Vol Down)
5.Type "fastboot flash boot boot.img" (exclude quotation marks)
6.Once flashed, reboot phone using "fastboot reboot"
Sorry, don't know how to extract the boot.img from a sbf. Did a quick search and couldn't find instructions. Not something I have done before. Maybe someone else can help with this. I don't even know if this will work, but anything is worth a shot when you are stuck.
<edit> Which CWM are you using?
You can flash Romracers via fastboot if you are not using it. This may help you get into recovery.
Update: I got the phone to recognize the sim card and make phone calls and get wifi active. But the phone still reboots by itself. I can use all the functions of the phone except it just reboots by itself. I got into the About phone section and it says
Android: 2.3.4
Kernel: [email protected] # 2
I can get into the Android Market as well as everything else. Could this be a hardware issue that causes the phone to reboot by itself within a minute or so?
Edit: I can get the vol up and down buttons to work while the phone is working but the power button is not responsive to let me power the phone off. Could a hardware issue with the power button be causing the constant reboot loop?
Update: I got the phone to function with the OS working just fine (phone calls, texts, emails, etc..) but it keeps restarting on its own. The power button still does not work however, could this be a hardware issue? Thanks
I attempted to flash MIUI.us V4 2.6.8 Atrix ByTeamMotoTegra today, and was almost successful, but I found out that I shouldn't have wiped the phone before flashing. I lost the touch functionality, and couldn't select my language. I flashed my old ROM (Neutrino) to try to flash back to MIUI, but still could not seem to get the touch funcationality.
After a few times of taking out the battery and trying to get the MIUI ROM working, I ran into a boot loop. The screen will not go past the screen with the red logo, no matter what I do. If I hold the volume up/down buttons, "starting RSD protocol support" appears, but nothing else happens. The phone just keeps turning off, then returning to the screen with the red logo. Any ideas on how to get past this screen?
i have a similar problem, i rooted and unlocked a friend atrix today on 2.3.6 version 4.5.141
it went fine and booted normally. i then went into cwm and made a mistake by not making a backup, cleared data cache and dalvik then proceeded to flash aokp. it booted but didnt go past the motorola dual core screen while still displaying unlocked. i can still go to fastboot and even into cwm as i have attempted to flash other roms after clearing all things out again but nothing is going past the boot screen.
any suggestions?
I can scroll through the other CWM menu options, but I can't boot up or anything else. Anytime I select one of the options, it will either just restart and go back to the red logo screen, or say I don't have enough battery life to flash. My battery is now completely dead and doesn't seem to be charging at all, even though it's been plugged in all night.
Hi guys,
My XT910 ran Cyanogenmod 11, Kitkat Nightly. Tonight an OTA update appeared (something called snapshot or something). Thought it might fix some thing that were not quite right in my version so decided to update. At some point during this process the screen went black then the M logo appeared than the android recovery menu (i can load it). And nothing else. I tried rebooting, wiping cache, reset to factory, nothing works. Copied several ROM on the sd card because i have the option to update from sd. Nada. I gotta tell you i'm on a Mac and i cant change that this week, no Windows till next week. And probably the battery is draining...
What to do?
This is how it goes:
I can not power down the device
It restarts periodically if no action taken
at first the M logo appears
instead of CM logo there is a robot with an exclamation mark inside a red triangle
i can get into recovery menu by pressing the volume keys
i can choose one of the options but nothing else
when applying updates from sd card (stock 4.1.2, nightly rom or snapshot rom) it goes up to "verifying update" then it abandons
Later edit:if i reboot from recovery menu and when it powers off i press pwr and vol- it goes to boot menu. No windows means no adb hence power off from that menu. when i plug in the charger, the M logo appears andstays there. Question: if it does actually charge the battery and i dont fix it before getting a windows, what kind of rom should i flash? Stock?
OK, I tried updating the M10 snapshot today over my current M9 snapshot that I had installed.
As it was updating, the screen went off and then I couldn't get anywhere past the M Logo, pressing the volume keys I'm also able to navigate to recovery etc.. but that's it.
I was not able to boot the phone off and even though the screen was off, I don't believe the phone was off. When I got home, the only thing I knew to do was to flash a stock JB rom using RSD Lite. But when I tried flashing it a few moments ago, it failed - the battery is low apparently. Putting it on charge I can now see a charging logo on the screen that is not centered, but I believe it is charging. Once I've got some juice I will try flashing it again, and then I think it's a whole process of rooting it, installing SafeStrap again, and then starting over with CM11.
I don't know if you can even get RSD Lite for MAC, but it's the only way I know that should work to get the phone back up and running.
Thanks for sharing.
There is no RSD for Mac, nor something similar. But i've managed to set up a virtual xp machine (modern.ie), installed everything, captured the usb port with the phone stating "usb connected". Unfortunately i just couldnt connect the phone to rsd, no matter what i did.
Oh gosh.
I managed to get my phone back by flashing the stock JB rom and then working from there.
Try going to the boot menu thing (hold down all keys) and then navigate to AP fastboot. RSD lite should see the phone in this mode.
But make sure the battery is OK first. I did manage to charge it to 40% and it then flashed after it had some charge. Seemed to flash it a little differently than other times. Also the phone said "Device is LOCKED", but thankfully it all worked out fine. Now I'm on CM11 09/15 Nightly.
Have you installed the Motorola drivers?
Maybe you can't do it through a VM.
Generated on a RAZR Maxx (XT910) using XDA's free mobile app.
d.casper.b said:
Oh gosh.
I managed to get my phone back by flashing the stock JB rom and then working from there.
Try going to the boot menu thing (hold down all keys) and then navigate to AP fastboot. RSD lite should see the phone in this mode.
But make sure the battery is OK first. I did manage to charge it to 40% and it then flashed after it had some charge. Seemed to flash it a little differently than other times. Also the phone said "Device is LOCKED", but thankfully it all worked out fine. Now I'm on CM11 09/15 Nightly.
Have you installed the Motorola drivers?
Maybe you can't do it through a VM.
Generated on a RAZR Maxx (XT910) using XDA's free mobile app.
Click to expand...
Click to collapse
"Device is locked" means that bootloader is locked in our phones,except those few developer edition models.
Sent from my Razr XT910
I'm glad you could do it. Mine seems to charge as well, it's now close to 24h since it bricked and i assume it would just die if it wouldnt charge in that particular state. Fortunately the keys on the Mac keyboard started working again after drinking beer two nights ago so i dont need to trick the virtual machine anymore, but unfortunately i just cannot get the rsd to see the phone on this VM. Probably should try a VM with windows 7 - i guess ill just do that. I have installed the drivers, the VM recognizes the phone (moto spyder adb...) but rsd wont see it, nor the adb driver installer (it needs to identify the device in order to install the proper drivers). I know that rsd is picky when it comes to usb cables, it might just not work with the original cable, but after trying 4 different cables i tend to think this is not the problem
P.S. I'm very upset on Google about killing Motorola and being disrespectful with its own customers (i mean i would have been expecting to be the first to get Android updates, not to wait one year to be able to update from 2.3 and i couldnt imagine they will not roll out RAZR updates after 4.1.2) so my next phone will be a Nokia Lumia. The coolest one, like my StarTac, my V70, my V3, my RAZR...
You maybe successful with a Windows machine
Indeed i was. It was fast and sound, no problems at all flashing stock rom. Though the phone didn't actually charged when plugged in and displaying the M logo. I had to actually sacrifice a usb cable and charge the battery directly.
I have the same problem - I updated to the last snapshot, and did a wipe in safestrap - and got bricked.
Only difference is I can't flash nothing! and in AP Fastboot mode the computer doesn't recognize anything.
Hi:
I've read through several "bricked" threads and none of them had the symptom I have so I'm not sure.....
I was on IMNUT's Tweaked Remix (VRAMC3 0906 release) and it's been acting up so I thought I'd move up to a newer ROM (I had planned to go to lacoursiere18's 4.4.2 to start).
I first updated recovery from an old version of CWM to the last version of Philz.
I flashed IMNUT's unlocked VRAMC3 stock via Odin and it booted fine although I hadn't realized I needed to wipe it first so all my apps were there.
I then booted to recovery to see if Philz was still there and found it replaced by the stock recovery (I didn't realize that would happen but I suspected it might).
So, since I used the unlocked version I used stock recovery to flash Philz. The output went by very fast and all I really caught was something about a file check failed (3 lines in red about it) and then a bunch of lines and then the screen went blank.
Now the phone will not do anything - won't turn on, won't go to recovery, won't go to download mode.
I pulled the battery and no change. I was at 60% battery when I started so I connected the USB cable to charge it. The little battery symbol that comes up while charging when you tap the power button did not come up. I tried power on/recovery/download and still nothing.
Am I SOL?
it is sure sounding like it to me... I don't think i've ever had a phone not at least go into bootloader mode.. ( vol down, home and power)