Database Users

[SOLVED] Stuck in APX mode, can't boot into CWM

Hi all, I've been having problems with my transformer... again. This time I have my transformer successfully rooted with an updated CWM, and flashed PRIME 1.6 and Netformer 1.5. The problem started when I held down power and selected the recovery option in the shutdown menu. the tablet went into a bootloop until I put it into APX mode to run the unbricking tool stickied in the dev section. For some reason, the tool didn't work and it did NOT say "phone update success on the tablet screen."
I then turned it off and my computer makes the USB disconnect sound, but then makes the connect sound right after, and Nvidia USB recovery shows up in device manager again, which means that it is stuck in APX mode. I cannot boot into CWM and I cannot boot up normally because it just dumps me back into APX.
I found a thread of someone who was also stuck in APX mode, but it doesn't help because he just returned the tablet whereas I cannot. http://forum.xda-developers.com/showthread.php?t=1169097
So to recap, I am stuck in APX mode, I can't boot normally or into CWM, and the unbricking tool does not work. Help please? I am starting to seriously regret flashing anything
EDIT: I did it! Thanks to all for the responses, I finally followed this guide to nv_flash prime 1.6r2 to my tablet and now it boots! The problem turned out to be that when I used the unbricking tool, it formatted all my data so the tablet was not able to boot into anything. By nv_flashing a rom onto it, it had something to boot into... again, thanks!

Anyone have any ideas? If I can't fix this then $400 went down the drain

Have you tried nvflash? I had that problem but nvflashing prime worked for me.
Sent from my PC36100 using Tapatalk

Vertiginouz said:
Hi all, I've been having problems with my transformer... again. This time I have my transformer successfully rooted with an updated CWM, and flashed PRIME 1.6 and Netformer 1.5. The problem started when I held down power and selected the recovery option in the shutdown menu. the tablet went into a bootloop until I put it into APX mode to run the unbricking tool stickied in the dev section. For some reason, the tool didn't work and it did NOT say "phone update success on the tablet screen."
I then turned it off and my computer makes the USB disconnect sound, but then makes the connect sound right after, and Nvidia USB recovery shows up in device manager again, which means that it is stuck in APX mode. I cannot boot into CWM and I cannot boot up normally because it just dumps me back into APX.
I found a thread of someone who was also stuck in APX mode, but it doesn't help because he just returned the tablet whereas I cannot. http://forum.xda-developers.com/showthread.php?t=1169097
So to recap, I am stuck in APX mode, I can't boot normally or into CWM, and the unbricking tool does not work. Help please? I am starting to seriously regret flashing anything
Click to expand...
Click to collapse
Did you actually flash a rom? That can happen when you dont have the appropriate files in the directory. Refer to the video that demonstrating an NVflash.
Sent from my Transformer TF101 using XDA Premium App

Yes, I flashed prime 1.6 and booted it successfully. I used the "recovery" option in the shutdown menu and that caused the bootloop, i never got into cwm

Did you compare md5's?
Sent from my Transformer TF101 using XDA Premium App

Backwardsblade said:
Did you compare md5's?
Sent from my Transformer TF101 using XDA Premium App
Click to expand...
Click to collapse
I didn't, but it did boot up fine, which means it was a legitimate download right?
I think I'll just try to send it to asus and see what they can do since NVflash doesn't work

I would probably download again, check the MD5 and reinstall.
Skickat från min ASUS Eee Pad TF101

I can't reinstall if I can't boot into cwm

Vertiginouz I can't reinstall if I can't boot into cwm
Click to expand...
Click to collapse
Are you sure you know what nv_flash is? This is only run in apx mode.

Did you try the one click batch method: http://forum.xda-developers.com/showthread.php?t=1185104
See whether that works for you...

keep this thread open, I would really like to know what the OP did to get out of this mess.
I would also like to know if other peeps running Prime 1.6 can press the recovery button instead of shutdown for some testing.

What kind of testing? I just did root a TF, backed it up, installed Prime, clicked the Recovery button and did a back up. Zero trouble.
I think this is my 7th or 8th root. People at work just keep bringing them to my office

It sounds like you didn't have a Rom when you nvflashed. If you just downloaded nvflash file in the stickied unbricking post then you will format everything without putting anything back on. You need to Rom that was built nvflash and put it in the root directory of the nvflash folder. There are some stock Roms available somewhere & also a prime 1.4 nvflash. They will install a recovery and then you can flash whatever you want from there.
Sent from my Transformer TF101 using XDA Premium App

boglwe said:
keep this thread open, I would really like to know what the OP did to get out of this mess.
I would also like to know if other peeps running Prime 1.6 can press the recovery button instead of shutdown for some testing.
Click to expand...
Click to collapse
I am currently running Prime 1.6 and i did a recovery method the other day to update a rom and it worked just fine.
I did it since i updated from 1.5 to prime 1.6 and had to re install the Clemsyn-blades cause the overclocking rom got disabled after update...

Thanks for the suggestions guys, I'll try the link that Q.Entity posted first.
housry23 said:
It sounds like you didn't have a Rom when you nvflashed. If you just downloaded nvflash file in the stickied unbricking post then you will format everything without putting anything back on. You need to Rom that was built nvflash and put it in the root directory of the nvflash folder. There are some stock Roms available somewhere & also a prime 1.4 nvflash. They will install a recovery and then you can flash whatever you want from there.
Sent from my Transformer TF101 using XDA Premium App
Click to expand...
Click to collapse
Okay so the unbricking nvflash formats everything, meaning I can't boot normally because I have no ROM? Shouldn't I still be able to boot into CWM though?
Also, the prime 1.4 nvflash thread you're talking about is this right? If I follow that guide will it install prime 1.4 during the nvflash process? If so, that will probably solve my problem

should work, but why stop there, I went ahead and popped on Prime 1.6 and then flashed a different kernel as well. I mean, I nvflashed from temp brick, perhaps like yours, and instead of flashing 1.4 prime I went ahead and did 1.6 since I already had the zip. I also at some point did the unbricking nvflash to stock rom, then used the pure root for tranformer method that includes CWM and then flashed Prime. regardless, both ways I was temp bricked. The key for me was knowing that I was in APX mode even though Device Manager in wndows 7 64bit did not show I was. Hope I could help, I am only speaking from my OWN experience with this device and prior mistakes.
EDiT: I also noted as some point that I could not get into recovery becuase I was not paying attention to my recovery screen. If all is correct, then when you hold down Vol- and power button, you are only given 5 seconds to press vol+ button to enter CWM.
Sent from my Transformer TF101 using XDA Premium App

The batch pure root script didn't work for me, even though I tried nvflashing the stock boot.img and recovery. No matter what, I couldn't get out of APX mode. The transformer immediately turns back on and puts me back into APX mode after I turn it off. Device manager and the USB connect/disconnect sounds confirm this. I'm afraid there's no way to get out

Why are you doing a pure root, after nv_flash. Why not just nv_flash prime 1.6 and be done? That will have everything working.

Yep.. your doing things kinda backwords.
Sent from my PG86100 using XDA Premium App

[Q] 3.2 wifi only root

hi all i cant seem to root my xoom.
to start i have a uk wifi only model and have flashed the 3.2 usa wifi.
works perfectly, i have unlocked the bootloader flashed root boot and then when i give the command fastboot reboot to then try and enter the recovery it just gets jammed on motorola logo does anyone know what im doing wrong i have followed several guides to the letter know and i cant seem to get root,

You didn't explain exactly what you are doing (have done) when you get stuck at the dual core screen.
One problem that can occur when rooting is overwriting your new Clockworkmod Recovery with stock recovery. In case this is the problem, here is
some important information to help get the new CWM recovery to stick.
From a thread called "an Idiot's Guide to flashing the Xoom" with info originally by public animal:
To install recovery image (CWM)
Download the recovery image file and save it to your computer
1 Boot into flash mode with 'adb reboot bootloader'
2 Install your downloaded recovery image
C:\Documents and Settings\Anders> fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
3 Restart the device with 'fastboot reboot'. Timing is essential here, so be alert when the device restarts, or you will have to redo this process
4 Enter CWM with the following procedure: Once the Motorola logotype is shown, start counting to 3. At 3, press the Volume Down button. This should result in the text 'Android Recovery' in the top left corner. If it does not work, experiment with the timing ... 5 When 'Android Recovery' is shown press the Volume Up button. This should invoke the CWM recovery menu. If that works, then congratulations for reaching this far .
Here is a potential pitfall. If you are unable to enter CWM *before* the device boots into Honeycomb, then the newly installed recovery image will be overwritten by the system default recovery.

When it gets jammed after the bootloader unlock process it stays on the Motorola dualcore logo' if I press power and up to restart it won't boot normally at all it just stays on moto logo and then I have to reflash for it to boot up normal' I don't understand where I'm going wrong' I have followed the threads to the letter a DB and fastboot fully working but something is stopping me from getting root.
Sent from my Xoom using XDA Premium App

bearusa said:
When it gets jammed after the bootloader unlock process it stays on the Motorola dualcore logo' if I press power and up to restart it won't boot normally at all it just stays on moto logo and then I have to reflash for it to boot up normal' I don't understand where I'm going wrong' I have followed the threads to the letter a DB and fastboot fully working but something is stopping me from getting root.
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
I would like to add I had no probs rooting my Sony experia play using adb and fastboot its weird I just can't put my finger on it'
Sent from my Xoom using XDA Premium App

bearusa said:
I would like to add I had no probs rooting my Sony experia play using adb and fastboot its weird I just can't put my finger on it'
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
It would help if we knew which guide you were using.

Guide for usa 3.2 wifi and 3g posted by jase33 in xoom android dev' than for your help guys
Sent from my Xoom using XDA Premium App

okantomi said:
It would help if we knew which guide you were using.
Click to expand...
Click to collapse
Than mate your guide sorted me out I'm now rooted and have recovery' I'm thinking I may have been entering a cmd incorectly'
or something or my recovery.img was corrupted I redownloaded files followed the guide you posted for me and it worked a treat.
Thanks for your help mate much gratitude and appreciation to you.
Sent from my Xoom using XDA Premium App

bearusa said:
Than mate your guide sorted me out I'm now rooted and have recovery' I'm thinking I may have been entering a cmd incorectly'
or something or my recovery.img was corrupted I redownloaded files followed the guide you posted for me and it worked a treat.
Thanks for your help mate much gratitude and appreciation to you.
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
I'm so glad it worked out. Now enjoy your rooted Xoom!

okantomi said:
I'm so glad it worked out. Now enjoy your rooted Xoom!
Click to expand...
Click to collapse
This thing is flying now' got rid of bloat once again thanks for your help
Sent from my Xoom using XDA Premium App

TF300TG: problem updating to new firmware (.40)

My Pad just told me that there is a firmware update. It loaded the file and restarted. But after a minute or so the android-icon changed into a lying figure with a warning label on the open stomach.
I was able to restart and the pad told me that the update was broken and the old version restored.
I tried to get the update again but now the pad says there is no new version.
Now I got the new firmware (.40) from the asus website but I'm not sure if I should try to to flash it by myself. Will I still get OTA-updates after I flashed a firmware by myself?

Doing a manual update wont prevent you from installing future ota updates. Go ahead and install it.
Sent from my HTC One X using Tapatalk 2

Ever since I updated OTA to .40, I have had lots of WiFi disconnects. Recovery from prob is manually connecting and waiting.
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app

MiGri said:
My Pad just told me that there is a firmware update. It loaded the file and restarted. But after a minute or so the android-icon changed into a lying figure with a warning label on the open stomach.
I was able to restart and the pad told me that the update was broken and the old version restored.
Click to expand...
Click to collapse
I had the same thing when I made the OTA Update the first time. But in difference I could start it again, it downloaded again and the update seemed to run through.
But after that the TF300TG always stops at the boot screen (mentioned in an other thread).
I think ASUS has some serious troubles with the .40 update.

I haven't seen an update notification at all on my Prime.. I have done the system update manually every day and still have yet to get the update.. im not root and every thing still stock.
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app

I tried the manual update but unfortunately I got again the lying figure with the warning sign.
My device is rooted using the one-click-method.
Is it possible that this causes the problem? Do I have to unroot and maybe doing a hard reset to get the update?
I was told the problem with the flickering screen in Tegra-games should be solved, so I really would try to get it...

Do you still have the stock system recovery image installed?
I'm having the same problem but I have clockwork recovery installed, which probably works great on the TF300T but can't install the 3G modem software on the TF300TG.
That's why my update is failing anyhow.

JezzAU said:
Do you still have the stock system recovery image installed?
I'm having the same problem but I have clockwork recovery installed, which probably works great on the TF300T but can't install the 3G modem software on the TF300TG.
That's why my update is failing anyhow.
Click to expand...
Click to collapse
I have still the stock recovery. I don't trust any of the instructions for the TF300T, as they may cause the lost of the 3G-ability of the TF300TG. :silly:

MiGri said:
I have still the stock recovery. I don't trust any of the instructions for the TF300T, as they may cause the lost of the 3G-ability of the TF300TG. :silly:
Click to expand...
Click to collapse
Yeah I did that a few weeks ago, I'm really wishing I hadn't now though!
Have you booted into recovery and checked that its still working?
I read that somebody corrupted their recovery image using the one-click root method.

JezzAU said:
Yeah I did that a few weeks ago, I'm really wishing I hadn't now though!
Have you booted into recovery and checked that its still working?
I read that somebody corrupted their recovery image using the one-click root method.
Click to expand...
Click to collapse
Stock recovery is just the menu you get when you press <vol down> during boot, where you can choose to get a factory reset or a cold boot, isn't it?
I tried that, seems to work. I read about the other guy with the broken recovery, too (http://forum.xda-developers.com/showthread.php?t=1795902). But as far as I understood he tried to unroot with the 1-click-method after the update to .40.

Update: I managed to install the new firmware. After I used the rootkeeper to temporarily unrooting the device the update ran without problems.
After the update the device was complete unrooted but I got back root using the tool here: http://forum.xda-developers.com/showthread.php?t=1706588
Unfortunately my issues with Tegra-games are not fixed with the new fírmware.

Is this only for tG? since I'm not having any notifications on my 300T

jusatin said:
Is this only for tG? since I'm not having any notifications on my 300T
Click to expand...
Click to collapse
The firmware 9.4.4.40 is only for the TG.

[Q] Custom Recovery or Stock Recovery?

I just used an automated program to root my phone. I was sick of running into websites on a daily basis that used flash, and hated every other browser out there so I rooted my Nexus 4 to get the stock browser from the Gnex. I am new at this though, and didn't realize rooting my phone could potentially interfere with OTA updates. How can I check to see if the automatic rooting tool I used kept the stock recovery, or changed it to a custom one?

This is exactly why I hate these toolkits...
Boot into recovery, check what it says. If it only shows you an android with a triangle, it's probably stock. If it's anything else (eg TWRP or Clockwork Recovery) then it's a custom.

You can be on Stock Rom with No Mods Unlocked Rooted with a Custom Recovery and you will get the ota update and it will install fine.
The ota update link will be posted here before you get on your device so it's good to have a custom recovery so you can just flash it. It will also protect you from losing root and your custom recovery
To check if you have a custom recovery with the phone off press and hold power and volume down then when in bootloader press volume down till you see recovery press power button if you get a android laying down that's stock recovery
Sent from my Nexus 4

ryfly65 said:
I just used an automated program to root my phone. I was sick of running into websites on a daily basis that used flash, and hated every other browser out there so I rooted my Nexus 4 to get the stock browser from the Gnex. I am new at this though, and didn't realize rooting my phone could potentially interfere with OTA updates. How can I check to see if the automatic rooting tool I used kept the stock recovery, or changed it to a custom one?
Click to expand...
Click to collapse
Rooting doesn't interfere with OTA updates. You are still able to update even with a custom recovery, and it actually makes things easier because you don't have to flash a custom recovery and then root after each update if you have a custom recovery. Custom recoveries offer many more options than regular as well.
For your original question, just power down your phone and turn it back on by holding both volume up and down while holding the power button. This will bring you to the bootloader. From there, navigate to recovery using the arrow keys and push power. If it's a custom recovery you'll know, and if it's stock, you'll just see an android.
It's recommended not to use automated programs to root because you don't learn anything, by the way, although it makes things much easier.
Sent from my Nexus 4 using xda app-developers app

^^^^^ that's what I said
Sent from my Nexus 4

spaceman860 said:
^^^^^ that's what I said
Sent from my Nexus 4
Click to expand...
Click to collapse
Haha, I thought I was the first reply
You need to hold volume up and down along with the power button to boot into the bootloader with this phone though
Sent from my Nexus 4 using xda app-developers app

hoponpop said:
Haha, I thought I was the first reply
You need to hold volume up and down along with the power button to boot into the bootloader with this phone though
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
No you don't that's for galaxy nexus for the n4 its just the down button
Sent from my Nexus 4

spaceman860 said:
No you don't that's for galaxy nexus for the n4 its just the down button
Sent from my Nexus 4
Click to expand...
Click to collapse
You're right. My bad, lol
Sent from my Nexus 4 using xda app-developers app

I went into Recovery Mode and it is showing a dead Android with a red triangle. I'm not quite sure what that means.

ryfly65 said:
I went into Recovery Mode and it is showing a dead Android with a red triangle. I'm not quite sure what that means.
Click to expand...
Click to collapse
That's the stock recovery. You have to press volume up and power to see the menu.

El Daddy said:
That's the stock recovery. You have to press volume up and power to see the menu.
Click to expand...
Click to collapse
Do you mean when it shows the dead Android with the triangle? Or before that?

ryfly65 said:
Do you mean when it shows the dead Android with the triangle? Or before that?
Click to expand...
Click to collapse
When it is showing. You can't do much with stock recovery though. Wipe data, clear cache, adb sideload. That's about it.

El Daddy said:
When it is showing. You can't do much with stock recovery though. Wipe data, clear cache, adb sideload. That's about it.
Click to expand...
Click to collapse
Ah, okay gotcha. The reason I asked if I have stock is because I read an article that not having the stock recovery, or altering files in the /system folder may interfere with OTA updates if the checksum fails. I did change the browser in the /system folder though. I renamed two files to get the stock browser in there and working. I just hope that won't affect the OTAs.

ryfly65 said:
Ah, okay gotcha. The reason I asked if I have stock is because I read an article that not having the stock recovery, or altering files in the /system folder may interfere with OTA updates if the checksum fails. I did change the browser in the /system folder though. I renamed two files to get the stock browser in there and working. I just hope that won't affect the OTAs.
Click to expand...
Click to collapse
That will definitely affect OTA's. Anything modified in /system will abort the OTA. You can read more info in my OTA help-desk thread in my signature.

El Daddy said:
That will definitely affect OTA's. Anything modified in /system will abort the OTA. You can read more info in my OTA help-desk thread in my signature.
Click to expand...
Click to collapse
I am completely stock with stock recovery; unlocked, and rooted. The only two things I did was put browser.apk, and ChromeBookmarksSyncAdapter.apk into the /systems folder, and then I renamed BrowserProviderProxy.apk, and BrowserProviderProxy.odex. I just just put a "1" in front of both names. It was part of the instructions to install the stock browser from the Galaxy Nexus phone onto my Nexus 4.
In order to receive the update, would I just have to name those two apps back to their original name? Or would I also have to remove the apps I put in there as well?

ryfly65 said:
So I am completely stock with stock recovery, unlocked, and rooted. The only two things I did was put browser.apk, and ChromeBookmarksSyncAdapter.apk into the /systems folder, and then I renamed BrowserProviderProxy.apk, and BrowserProviderProxy.odex. I just just put a "1" in front of both names. It was part of the instructions to install the stock browser from the Galaxy Nexus phone onto my Nexus 4.
In order to receive the update, would I just have to name those two apps back to their original name? Or would I also have to remove the apps I put in there as well?
Click to expand...
Click to collapse
You should be OK just changing them back. Additions to /system are fine too. If it does end up falling you can just flash the system image with fastboot
Sent from my Nexus 10 using Tapatalk 4 Beta

[Q] Factory Reset from Fastboot

Hi everyone,
My phone cannot get into recovery and I need to factory reset. Is it possible to do this using fastboot from the console?
My phone keeps going back to the fastboot screen and this is what it says:
Invalid Flash Mode (S)
10.9B(*) (sha-le9f557, 2013-05-24 14:49:34)
eMMC Info: Size 8GB
Device is LOCKED. Status Code: 0
Battery OK
Connect USB
Data Cable
Failed to hab check for boot: 0x56
Fastboot Reason: Boot Failure
This comes up after I hold down the both volume buttons and the power button and try to load Recovery. I get the dead android with the red traingle.
If I start up normally I get the dead android with the red triangle again, and then it eventually goes back to fastboot, saying the reason is Flash Failure
Any help is gratefully appreciated
Thanks

mgoldenberg said:
Hi everyone,
My phone cannot get into recovery and I need to factory reset. Is it possible to do this using fastboot from the console?
My phone keeps going back to the fastboot screen and this is what it says:
Invalid Flash Mode (S)
10.9B(*) (sha-le9f557, 2013-05-24 14:49:34)
eMMC Info: Size 8GB
Device is LOCKED. Status Code: 0
Battery OK
Connect USB
Data Cable
Failed to hab check for boot: 0x56
Fastboot Reason: Boot Failure
This comes up after I hold down the both volume buttons and the power button and try to load Recovery. I get the dead android with the red traingle.
If I start up normally I get the dead android with the red triangle again, and then it eventually goes back to fastboot, saying the reason is Flash Failure
Any help is gratefully appreciated
Thanks
Click to expand...
Click to collapse
I am in the same predicament. I hope there is a way out

mgoldenberg said:
Hi everyone,
My phone cannot get into recovery and I need to factory reset. Is it possible to do this using fastboot from the console?
My phone keeps going back to the fastboot screen and this is what it says:
Invalid Flash Mode (S)
10.9B(*) (sha-le9f557, 2013-05-24 14:49:34)
eMMC Info: Size 8GB
Device is LOCKED. Status Code: 0
Battery OK
Connect USB
Data Cable
Failed to hab check for boot: 0x56
Fastboot Reason: Boot Failure
This comes up after I hold down the both volume buttons and the power button and try to load Recovery. I get the dead android with the red traingle.
If I start up normally I get the dead android with the red triangle again, and then it eventually goes back to fastboot, saying the reason is Flash Failure
Any help is gratefully appreciated
Thanks
Click to expand...
Click to collapse
when you get to Android Andy what happens when you hold volume down and tap volume up?
If you get in there I would wipe the cache partition as well... tho either of these may not help the issue... what were you doing prior to this happening? were you updating and get this upon its restart? Did it die and power up to this?... did it just randomly shut off and power up to this?
Sent from my XT907 using xda app-developers app

ezknives said:
when you get to Android Andy what happens when you hold volume down and tap volume up?
If you get in there I would wipe the cache partition as well... tho either of these may not help the issue... what were you doing prior to this happening? were you updating and get this upon its restart? Did it die and power up to this?... did it just randomly shut off and power up to this?
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
When I got to android andy the android system recovery 3e menu popped up. I wiped the cache partition and did a factory reset, then rebooted but I'm still going in circles between the dead android and fastboot. Prior to this I had tried using safestrap to set up a recovery, but when I rebooted, I got stuck at fastboot. There was one point when I got to what I think was the fastboot menu and from there I tried flashing cyanogenmod, which I'm pretty sure was a mistake. Now I cant figure out how to get back to that menu.

mgoldenberg said:
When I got to android andy the android system recovery 3e menu popped up. I wiped the cache partition and did a factory reset, then rebooted but I'm still going in circles between the dead android and fastboot. Prior to this I had tried using safestrap to set up a recovery, but when I rebooted, I got stuck at fastboot. There was one point when I got to what I think was the fastboot menu and from there I tried flashing cyanogenmod, which I'm pretty sure was a mistake. Now I cant figure out how to get back to that menu.
Click to expand...
Click to collapse
OK...
First, what do you mean by "set up a recovery"?
I noticed your bootloader is locked. That means no custom recoveries can be flashed, so that's probably your problem.
If you tried to fastboot the Cyanogenmod zip (!?) that definitely didn't help.
What exactly are you trying to accomplish? Are you trying to reset to sell or return or something? Also, what system version did you have (or, if you don't know that, when did you get the phone and have you taken any OTA updates)? And were you previously rooted?
It sounds like you had a bad flash. Give me that info and I'll try to help you unbrick it...
Sent from my Nexus 7 using Tapatalk 4

From the fastboot details it looks like the most recent ota
mgoldenberg said:
10.9B(*) (sha-le9f557, 2013-05-24 14:49:34)
eMMC Info: Size 8GB
Click to expand...
Click to collapse
I say rsd the recent firmware....
Sent from my XT907 using xda app-developers app

sloosecannon said:
OK...
First, what do you mean by "set up a recovery"?
I noticed your bootloader is locked. That means no custom recoveries can be flashed, so that's probably your problem.
If you tried to fastboot the Cyanogenmod zip (!?) that definitely didn't help.
What exactly are you trying to accomplish? Are you trying to reset to sell or return or something? Also, what system version did you have (or, if you don't know that, when did you get the phone and have you taken any OTA updates)? And were you previously rooted?
It sounds like you had a bad flash. Give me that info and I'll try to help you unbrick it...
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Yeah I'm still a noob at this, sorry. By set up a recovery I mean manually installing safestrap because clockworkmod doesn't support xt907, and I couldn't flash it manually from my computer, probably because of what you said about my bootloader being locked. Really all I want to do is get my old OS back, just the stock android that I got when I bought it. I had version 4.1.2 which I got from an OTA update, and I have not been previously rooted. Thanks for being patient with me by the way, I understand people like me probably make you want to rip your hair out...

mgoldenberg said:
Yeah I'm still a noob at this, sorry. By set up a recovery I mean manually installing safestrap because clockworkmod doesn't support xt907, and I couldn't flash it manually from my computer, probably because of what you said about my bootloader being locked. Really all I want to do is get my old OS back, just the stock android that I got when I bought it. I had version 4.1.2 which I got from an OTA update, and I have not been previously rooted. Thanks for being patient with me by the way, I understand people like me probably make you want to rip your hair out...
Click to expand...
Click to collapse
Try this
I was stuck on the same screen all day
http://www.droidrzr.com/index.php/topic/28162-house-of-moto/

mgoldenberg said:
Yeah I'm still a noob at this, sorry. By set up a recovery I mean manually installing safestrap because clockworkmod doesn't support xt907, and I couldn't flash it manually from my computer, probably because of what you said about my bootloader being locked. Really all I want to do is get my old OS back, just the stock android that I got when I bought it. I had version 4.1.2 which I got from an OTA update, and I have not been previously rooted. Thanks for being patient with me by the way, I understand people like me probably make you want to rip your hair out...
Click to expand...
Click to collapse
Ah OK. That clarifies a lot.
So, I'll explain a few things here since you seem a little lost
1: safestrap is not the same as clockworkmod. It's based off of TWRP, but it's not technically even a custom recovery, just a bootstrap hijack.
2. Yeah, you can't flash safestrap. It's actually installed via an app, and you do need root to use it.
3. When did you update? If you did the latest OTA, you unfortunately can't downgrade... If you didn't, we can help you unlock the bootloader, then you can downgrade at will.
4. If you do unlock, you can install clockworkmod or any other recovery. If you can unlock, I strongly advise you do it.
Sent from my Nexus 7 using Tapatalk 4

sloosecannon said:
Ah OK. That clarifies a lot.
So, I'll explain a few things here since you seem a little lost
1: safestrap is not the same as clockworkmod. It's based off of TWRP, but it's not technically even a custom recovery, just a bootstrap hijack.
2. Yeah, you can't flash safestrap. It's actually installed via an app, and you do need root to use it.
3. When did you update? If you did the latest OTA, you unfortunately can't downgrade... If you didn't, we can help you unlock the bootloader, then you can downgrade at will.
4. If you do unlock, you can install clockworkmod or any other recovery. If you can unlock, I strongly advise you do it.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Oh ok, thanks for explaining. I'm not sure when I updated, but I know for sure it was OTA, so I can't downgrade. And do I need to unlock to fix this whole thing? Because for now I just want my phone back... I'm not exactly worried about flashing or rooting or anything.

mgoldenberg said:
Oh ok, thanks for explaining. I'm not sure when I updated, but I know for sure it was OTA, so I can't downgrade. And do I need to unlock to fix this whole thing? Because for now I just want my phone back... I'm not exactly worried about flashing or rooting or anything.
Click to expand...
Click to collapse
Did you try the link I provided? I was stuck on the same screen, took me all day to figure it out.
Sent from my XT907 using xda app-developers app

zombolt said:
Did you try the link I provided? I was stuck on the same screen, took me all day to figure it out.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
So this might be a stupid question... but which option do I choose after typing in my phone model? RSD, Fastboot [snapdragon] or moto-fastboot [omap]?

sloosecannon said:
Ah OK. That clarifies a lot.
So, I'll explain a few things here since you seem a little lost
1: safestrap is not the same as clockworkmod. It's based off of TWRP, but it's not technically even a custom recovery, just a bootstrap hijack.
2. Yeah, you can't flash safestrap. It's actually installed via an app, and you do need root to use it.
3. When did you update? If you did the latest OTA, you unfortunately can't downgrade... If you didn't, we can help you unlock the bootloader, then you can downgrade at will.
4. If you do unlock, you can install clockworkmod or any other recovery. If you can unlock, I strongly advise you do it.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Also, I tried unlocking my bootloader. I used this thing called motopocalype and it should have worked, but apparently it didn't Im sort of hesitant about running it again.
Here's the link: http://www.droidrzr.com/index.php/t...k-your-bootloader-atrix-hdrazr-hdrazr-m-only/

Did you get your phone back up?... if your on system version .3 or .78 you cannot unlock your boot loader build date 5/2013..
Sent from my XT907 using xda app-developers app

mgoldenberg said:
Also, I tried unlocking my bootloader. I used this thing called motopocalype and it should have worked, but apparently it didn't Im sort of hesitant about running it again.
Here's the link: http://www.droidrzr.com/index.php/t...k-your-bootloader-atrix-hdrazr-hdrazr-m-only/
Click to expand...
Click to collapse
If it didn't work, you're probably already updated. Looks like you can't unlock unfortunately
Sent from my XT907 using Tapatalk 4

mgoldenberg said:
So this might be a stupid question... but which option do I choose after typing in my phone model? RSD, Fastboot [snapdragon] or moto-fastboot [omap]?
Click to expand...
Click to collapse
Rsd. From that point you should be able to choose whether you want to erase everything or save it. Worked like a charm for me, took about 10min
Sent from my XT907 using xda app-developers app