Database Users

So... I think I just bricked a G1. You tell me.

Reading the "How to root" thread here. I've rooted a few G1's and a MT3G in the past.
Anyways. I downgraded to RC29, downloaded Amon's recovery and Hard SPL.
Did the whole Telnetd, downloaded telnet from market and mount remount, flash yadda yadda as per stated.
Rebooted and applied the Hard SPL.
After that finished I rebooted and it just hangs on the G1 screen, Home/Power does nothing. Camera/Power does nothing. Trackball/Power just lights the LED up blue.
Will it live the rest of it's life as a door stop?

not being able to boot into anything is a brick but there have been many threads about people who have somehow reversed their brick so just search this forum and see if anything happends who knows it could happen. otherwise its a really shiny paper weight

Bummer. I'll search around a bit more and see if there might be a thread I missed. I don't want to dig into it and do the whole jtag crap since there is still a warranty on the phone.
This is the "How-to" thread I followed and has worked on every G1 I have rooted til this phone which is a brand new one from Tmo.
http://forum.xda-developers.com/showthread.php?t=442480
Searching more I have read about people not flashing a radio before the SPL and caused a brick. If that is true why doesn't it state this as a necessary step?

Flashing the Radio before the SPL is needed for DangerSPL (although I seem to recall a thread debating that - http://forum.xda-developers.com/showthread.php?t=655097 ), I didnt think it was needed for HardSPL, it sounds like a brick unfortunatly, but I am no expert.
It is thought that its safer to flash the SPL and radio ect via fastboot (see link above) , not that it helps to much now, but that is an old guide, it should be updated though

Yep. From what I have gathered is if you can't get into recovery (home+power) or fastboot (camera+power) and it hangs on the G1 boot screen. It's a brick.

-RotorDemon- said:
Yep. From what I have gathered is if you can't get into recovery (home+power) or fastboot (camera+power) and it hangs on the G1 boot screen. It's a brick.
Click to expand...
Click to collapse
its not a brick unless it doesn't turn on at all (depending on how you define the word "brick")
exact same thing happened to one of the G1 replacements my friend got sent to him...we sent it back and they sent him a new one

Nah it's not bricked, the HSpl isn't compatible with your ROM, try flashing he ROM again, or faulty ROM this happens a lot.
Howto fix:
1. Backup any files on your SD card that are valuable to you (you can copy them to your PC's hard drive)
2. Format your SD card to FAT32 ( put your SD in your PC)
Windows: Right-click on SD icon and select format
3. Download the RC29 / RC7 dreaimg.nbh file (don't rename it or your phone won't recognize it):
RC29 (US): http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod
RC7(Europe):http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod
4. Put the file you just downloaded onto your freshly formatted SD card (make sure it is named DREAIMG.nbh, the rc7 file downloads with .NBH which is wrong)
5. Turn your phone off.
6. Hold down the Camera button, and press the Power button until the bootloader starts.
Note: On some G1s it may require pressing the action button (trackball), while on others it may require pressing the power button.
7. Follow the on-screen instructions to flash the image.
8. When it's done, press the trackball.
9. Press the Call, Menu, and Power buttons at the same time to reboot. You may need to unplug your phone for this to work.
10. And you're done, your phone is in Manufacture default-settings.
If you want to flash a ROM follow a guide (start from the beginning)
Tell me if it worked or didn't worked!
Source: http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod

what tally said....
but on the one i described, just to let you know, i flashed the rc29 dreaimg.nbh like 15 times, it would never get off the G1 boot screen

tnpapadakos said:
what tally said....
but on the one i described, just to let you know, i flashed the rc29 dreaimg.nbh like 15 times, it would never get off the G1 boot screen
Click to expand...
Click to collapse
Try flashing the ROM again if you can go to the bootloader(Rainbow) screen try this:
1. take out the SD card
2. download this file ,open the folder and paste the dreaming.NBH file to the root of your SD card(use your pc or another phone to past this on your SD card).
2. you should get a gray screen once the card in placed back into the phone
3. then press power to start update
4. once the update is complete press the track ball then the rainbow(bootloader) screen should come back up,
5. pull out the battery and there you go your phone should work again
Note: If it didn't updated turn of your phone and turn it on by pressing (& holding) Power+Camera button.
Tell me if it worked

Lol, for some reason it double posted my previous post sorry.

He says in the first post Camera / Power dosent load the bootloader

vixsandlee said:
he says in the first post camera / power dosent load the bootloader
Click to expand...
Click to collapse
send it back

vixsandlee said:
He says in the first post Camera / Power dosent load the bootloader
Click to expand...
Click to collapse
Yes I know but if he connects it to he's PC and turns it off and on and then go to bootloader it will work.

tally114 said:
Yes I know but if he connects it to he's PC and turns it off and on and then go to bootloader it will work.
Click to expand...
Click to collapse
Interesting, I didnt know that.
Thanks for the info.

tally114 said:
Yes I know but if he connects it to he's PC and turns it off and on and then go to bootloader it will work.
Click to expand...
Click to collapse
Doesn't work either. Connected, disconnected, SD card in or out, SIM card in or out and any combination of that.
Logcat just sits and says "Waiting for device" while the phone just hangs on the G1 screen. So unless there is a different way to get into the bootloader besides using Camera+Power I'd like to know.
Camera+Power and Home+Power are unresponsive.

Well... it sounds like you've got yourself a fancy plastic brick, just remember for next time
1. Downgrade
2. Radio
3. Spl
-------------------------------------
Sent via the XDA Tapatalk App

Froyo Software

Here is a link to download the Froyo software so you can do it via the sdcard instead of thru motorolas update program.
http://www.motorola.com/staticfiles...dcards/US-EN/flipside/index.html?pubid=987654

I am having difficulties updating my son's phone...it goes through the process of updating and ends up with the !

pamaguin said:
I am having difficulties updating my son's phone...it goes through the process of updating and ends up with the !
Click to expand...
Click to collapse
What was the setup on his phone before the update? Rooted, how much memory avail, etc. Also, did you try both methods, or just this one?

I've tried both methods and phone was not rooted. And I also did a factory reset, which cleared all data.

pamaguin said:
I've tried both methods and phone was not rooted. And I also did a factory reset, which cleared all data.
Click to expand...
Click to collapse
I wish I had the answer to this. It baffles me as so many have had luck. Hopefully someone will come along that knows more than I.

You should try reflashing 2.1 using SBF to get it completely back to how the phone was when you first got it (more of a full wipe then just a factory reset). Use RSD Lite to do this, do you know how to do that?
Another alternative is to rename the 2.2 update to "update.zip" and then put it on your sd card. And once you got the "!" screen you can do the hardware reset by either pressing fn and T and the same time, up and down arrow keys at the smae time, or press up and down on the volume keys (one of these works depending on version device is running). From there 3 options will popup and you should select the wipe option first and then after thats finished select apply update zip and it will automatically apply the 2.2 update you renamed to "update.zip" on your sd card. And that should install the update. Hope this helps
*Note that flashing back to 2.1 AFTER you've already made it to 2.2 will brick your phone...so know what you're doing*
*Also some computers will automatically have the ".zip" at the end of the file name so after you rename right-click and go to properties and check to see if it just says update.zip. If it says "update.zip.zip" then you only need to rename it "update"*

Where can I find on how to use RSD lite? And I've tried renaming the file to update with no luck; "installation abort".
JBallin4life27 said:
You should try reflashing 2.1 using SBF to get it completely back to how the phone was when you first got it (more of a full wipe then just a factory reset). Use RSD Lite to do this, do you know how to do that?
Another alternative is to rename the 2.2 update to "update.zip" and then put it on your sd card. And once you got the "!" screen you can do the hardware reset by either pressing fn and T and the same time, up and down arrow keys at the smae time, or press up and down on the volume keys (one of these works depending on version device is running). From there 3 options will popup and you should select the wipe option first and then after thats finished select apply update zip and it will automatically apply the 2.2 update you renamed to "update.zip" on your sd card. And that should install the update. Hope this helps
*Note that flashing back to 2.1 AFTER you've already made it to 2.2 will brick your phone...so know what you're doing*
*Also some computers will automatically have the ".zip" at the end of the file name so after you rename right-click and go to properties and check to see if it just says update.zip. If it says "update.zip.zip" then you only need to rename it "update"*
Click to expand...
Click to collapse
Sent from my Xoom using XDA App

Flipside Bootloader Mode - Restore with SBF File
To put the Flipside into bootloader mode:
Open the keyboard
Press and hold the up arrow key (to the left of the OK key)
Hold the power button down
Release both buttons after about 4 seconds
You should see a display that says:
Bootloader
91.2B
Battery Ok
OK to Program
Connect to USB
Data Cable
This mode is for flashing an sbf file (ROM) to your phone using RSDLite.
RSD Lite version 4.9 works with the Flipside
You can get a stock AT&T ROM here (2nd post) or here (2nd post). I believe that they both point at the same file.
I can state that when I DLed that file it did work for my Flipside.
The hashes for the file I tested were:
CRC32: 92E73801
MD5: 7B529FE7D732EC4E71F5955C887E33A5
SHA-1: 7B49401A107F6DD779DBA0F55DECF473501E554A
Filesize: 196 MB (206,426,725 bytes)
This hashes/filesize are for the extracted sbf file.
I have received info from a reliable source that downgrading the Flipside from the not-yet-released Froyo upgrade using the available SBF files will brick your AT&T phone.
*you can find RSD Lite by just googling and downloading it*
Will post instructions for using RSD Lite in a second

This guide is for anyone who:
Has ever used RSD Lite, given up at the "Please Reboot this Phone Manually" status, and closed RSD Lite despite being warned: "Application is currently busy. Closing application may DAMAGE the attached device. Do you wish to continue?".
Has never used RSD Lite, but are going to, and want to do it right when you do.
The action described in the first bullet is quite common, so if you've done it, you're not an idiot. I think pretty much every RSD Lite YouTube video shows it being done that way, and it doesn't seem to cause any trouble, so who cares, right? Maybe it's just me, but I'd rather see a result of "PASS" when doing something this critical if at all possible. Here's how to do just that.
Proper RSD Lite flashing procedure:
1. Be sure you have your SBF file somewhere that you can find it. Also, be sure your SBF file is good. If your file was originally zipped, then unzipping it would have given an error if it was corrupted so you're OK. Otherwise, hopefully the source of your file lists its MD5sum. If so, you should verify the MD5sum of your file to make sure it is not corrupt. You can permanently brick your phone with a corrupted SBF (if it's corrupted in just the right place).
2. Plug your phone into a USB cable attached to your computer. Depending on whether or not you have USB debugging turned on, have had your phone attached to the computer recently, etc., you will at least probably hear the "device insertion tone" in Windows, and you may see the New Hardware Wizard install the drivers for your phone. Wait until your computer settles and looks bored before continuing.
3. Power down your phone. Once your phone is all the way "off", slide your keyboard open (on the phone).
4. Summon your best contortionist skills, and press on the "up" direction of the directional keypad rocker (the direction toward the screen -- which could really be to the right depending on how you're holding the phone) [pic]. While holding the dpad in the up direction, simultaneously press and hold the power button of the phone. When you see the backlight of the screen come on you can release the power button and the bootloader screen should appear (it will say "Bootloader" in the upper left corner). You can release the dpad. At the bottom of the text on the screen it should say "Transfer Mode: USB" if your cable is properly connected. If it says "Connect USB Data Cable", then you need to do so.
5. Run RSD Lite. If you're on a version of Windows newer than XP, remember to run RSD Lite as administrator by right clicking its menu choice and choosing "Run as Administrator".
6. At this point the phone should show up in the grid in the bottom half of the RSD Lite window. Give it a minute or two if it doesn't show up right away. Sometimes it takes Windows a minute (or 2 or 3) to let go of the phone and pick it back up again after rebooting into the bootloader. If after a couple minutes your phone still isn't listed in the "Model" column of the bottom section, in RSD Lite, click Config, Device Id Options, and choose "First-Come-First-ServeDeviceId Mode" and press "OK". RSD Lite may say you need to restart RSD -- if so, do so.
7. Assuming that you now can see your phone listed, click the "..." button to the right of the "Filename:" box. Find the SBF file you intend to flash on your hard drive. After choosing the file the right hand File details pane will fill in.
8. OK, this step is where you are going to press "Start" in RSD Lite, but don't do that yet. Before you press Start, read step 9. Step 9 has some timing sensitive tasks. If you do step 9 wrong it's not going to break anything, but you'll waste some time going through an un-needed boot and shutdown of the OS. Once you've read Step 9 and know what you'll be doing next, go ahead and press Start.
9. So far this has all been routine and you're thinking "so what?". This next part is what will get you a result of PASS instead of a warning about destroying your phone. After clicking Start the flashing process goes through several distinct steps. At some point there will be a bit of a delay with RSD Lite showing a status of "Phone[0000]: Waiting for re-enumeration". After that is when the actual flashing happens. When the flashing has completed, RSD Lite is going to issue a "reboot-bootloader" command to your phone. Unfortunately the Droid does not appear to implement the reboot-bootloader command correctly and does a normal reboot instead. If you don't "catch the boot" by holding up on the dpad key the OS will boot. Just before sending the reboot instruction to your phone the status in RSD Lite will change to "Phone[0000]: Phone is being rebooted". On your phone the screen will change to "SW Update Complete" (unless the message has been changed by the person who built the SBF) and your phone will reboot shortly thereafter. You want to be already holding the dpad key up when this happens. If you followed the instructions for Step 8 you have pre-read this step and knew to be ready for this. If not, your phone is probably already rebooted into the OS. If you miss it and the phone boots the OS it's no big deal (unless the instructions for the particular SBF you're flashing say otherwise). If that happens, let the phone finish its boot, and then just do a shutdown like normal. Then press/hold up on the dpad key and power back on. RSD Lite is patient and will wait.
10. You should now be looking at the bootloader on the phone, and RSD Lite should still be saying "Phone[0000]: Phone is being rebooted". If too much time has passed RSD Lite may be saying "Please manually boot the phone". The "Progress" value on the screen will keep incrementing, and at some point before, or at, 100% the result should change to "PASS". You can now click Close to exit RSD Lite without getting any disturbing warnings.
Congratulations. You've just done a proper SBF flash! The result is not simply cosmetic. RSD Lite is doing a final integrity check after rebooting clean into the bootloader. If you do it the old way (just unplug after the reboot and ignore the warning about destroying the device) you may be just fine, but you may also miss the chance to know your flash didn't go quite right and needs to be redone.
Installing RSD Lite:
First you're going to need a Windows workstation. There is a utility called sbf_flash for Linux that will let you do it with Linux, but that is not the subject of this guide.
Next, grab RSD Lite 4.6 and the appropriate Motorola drivers (32-bit or 64-bit) for your machine. In addition to the preceding links you can get them by going to this link, then double clicking on "rsd_lite" in the right side panel (or single click in the left side panel). [Older versions of the drivers here in case they be useful to anybody: 32 bit or 64 bit.]
Install RSD Lite and the drivers on your computer. If you're running Windows XP, life is good. If you're running Vista or Windows 7 you need to be sure to run RSD Lite as Administrator (by right clicking on the choice in your Start menu and choosing "Run as Administrator"). Hopefully your computer isn't too old. Some machines with older BIOS (like 2002 era) have been known to have USB issues that cause trouble with flashing using RSD Lite.
That's all there really is to installation.

I just posted the 2.2.2 Froyo SBF file in the Flipside Development section. Check that out and use RSD Lite to flash the file...you shouldn't have any problems if you do it correctly. Let me kno if it works or you need more specific instructions

Thanks Jballin, I followed your tutorial to restore my flipside before updating to froyo. It was the only way I could install 2.2. I kept getting stuck on the exclamation point. Thanks so much for your tutorial.

thehotrod11 said:
Thanks Jballin, I followed your tutorial to restore my flipside before updating to froyo. It was the only way I could install 2.2. I kept getting stuck on the exclamation point. Thanks so much for your tutorial.
Click to expand...
Click to collapse
Anytime man!

any one get the white notification led working after upgrade?

data2318 said:
any one get the white notification led working after upgrade?
Click to expand...
Click to collapse
YES OMG its so damn annoying. I thought I had turned it off, but it still shows when getting an incoming call. Turning it off in settings did stop it from flashing if I have a missed call or voicemail tho.

[Q] Unbricking Help?

Attempting to update a US-Tmobile Defy (green lens) with CM7 to CM10
1. As a 1st step wanted to do a full Nandroid - but the backup repeatedly failed.
2. Next, installed RSD lite to unroot, revert to stock, 1st tried with "JORDN_U3_6.36.0_SIGNED_USAJRDNTMOB1B4B5DE1028.0R_JORDANTMO_P022_HWp3_Service1FF.sbf.gz"
After completion, the Defy was stuck in a boot loop
3. Finally, used RSD lite attempting to unroot & revert to stock using, "T-Mobile_MB525_6.19.0_1FF.zip"
After completion, the phone would not boot nor go into bootloader.
The battery was very low and I suspect that it may be the reason I cannot start the bootloader. The phone, in its current state does not seem to charge the battery.
Please help!
Doug

All you had to do was wipe data after 1 St flash via stock recovery
But now search around for the mcgyer trick to charge your phone and then flash the first sbf and wipe data afterwards
Never flash with a low battery
Sent from my MB525 using xda premium

thekguy said:
All you had to do was wipe data after 1 St flash via stock recovery
But now search around for the mcgyer trick to charge your phone and then flash the first sbf and wipe data afterwards
Never flash with a low battery
Sent from my MB525 using xda premium
Click to expand...
Click to collapse
Thanks,
found the thread and am gave it a try. Still no love insofar as getting into the boot loader. Perhaps the battery is not dead. Reads 3.9v
Anything else I can do to try n summon the bootloader?

techhome said:
Thanks,
found the thread and am gave it a try. Still no love insofar as getting into the boot loader. Perhaps the battery is not dead. Reads 3.9v
Anything else I can do to try n summon the bootloader?
Click to expand...
Click to collapse
Do you get something like :
'battery ok in bootloader' ?
EDIT:
I see you are not able to see boorloader at all.
one thing you can do is :
connect the phone to your system
start rsd lite
take out the battery
insert it again
and immediately press power and volume up.
you may not see the bootloader on the screen but your device may show up on rsd lite.then you can flash your sbf.

kanpurite said:
Do you get something like :
'battery ok in bootloader' ?
EDIT:
I see you are not able to see boorloader at all.
one thing you can do is :
connect the phone to your system
start rsd lite
take out the battery
insert it again
and immediately press power and volume up.
you may not see the bootloader on the screen but your device may show up on rsd lite.then you can flash your sbf.
Click to expand...
Click to collapse
You nailed it, looks like I am out of the woods... Thanks!

Happy flashing
Sent from my MB525 using xda premium

what do i do if it says "Battery Low..Cannot Program"??

prateekranka said:
what do i do if it says "Battery Low..Cannot Program"??
Click to expand...
Click to collapse
You must charge your battery. The possible ways are:
1. with friend's defy or external charger
2. McGyver way - find in threads, but use with caution

Stuck in Boot-loop

I'm not sure what's going on with my device or how to fix it so I'm hoping someone here may be able to assist.
I just got my Moto X from AT&T. It came with Android 4.2.2 and immediately upon starting it up asked me if I wanted to software update to which I responded no. I then used this guide (http://forum.xda-developers.com/showthread.php?p=45598679) to root the device with the PwnMyMoto. I installed the APK and the device was then rooted. I restarted the phone and upon reboot I was asked again to update the software.
This time I did update the software and the device proceeded to turn off, restart, and do this over and over. It would continue to turn itself back on for somewhat of 20 seconds before saying "Powering Off..." and then restart again. I tried using the RSD Lite method to flash the stock firmware back on the device but RSD Lite wouldn't recognize it, even with USB debugging on and the phone in bootload mode.
I could really use all the help I can get. It's completely stuck and I have no idea how to recover it from this state.

Konvett said:
I'm not sure what's going on with my device or how to fix it so I'm hoping someone here may be able to assist.
I just got my Moto X from AT&T. It came with Android 4.2.2 and immediately upon starting it up asked me if I wanted to software update to which I responded no. I then used this guide (http://forum.xda-developers.com/showthread.php?p=45598679) to root the device with the PwnMyMoto. I installed the APK and the device was then rooted. I restarted the phone and upon reboot I was asked again to update the software.
This time I did update the software and the device proceeded to turn off, restart, and do this over and over. It would continue to turn itself back on for somewhat of 20 seconds before saying "Powering Off..." and then restart again. I tried using the RSD Lite method to flash the stock firmware back on the device but RSD Lite wouldn't recognize it, even with USB debugging on and the phone in bootload mode.
I could really use all the help I can get. It's completely stuck and I have no idea how to recover it from this state.
Click to expand...
Click to collapse
Try fastboot erase cache first, you can not flash the ota while having any form of a custom recovery
Sent on my Moto X

flashallthetime said:
Try fastboot erase cache first, you can not flash the ota while having any form of a custom recovery
Sent on my Moto X
Click to expand...
Click to collapse
Anything I try to do in fastboot menu results in the phone restarting. If I select any of the options, it just starts the phone up and goes through this process all over again.

flashallthetime said:
Try fastboot erase cache first, you can not flash the ota while having any form of a custom recovery
Ops might be to late, now that I see it did flash it.
Make sure your phone is recognized first through fastboot, then open redlite and you should see its connected. If still no connection make sure you have all the current Motorola drivers
Sent on my Moto X
Click to expand...
Click to collapse
Really, do you have all the current Motorola drivers
Sent on my Moto X

I'm not really sure on what you're saying to do now.

Konvett said:
I'm not really sure on what you're saying to do now.
Click to expand...
Click to collapse
Make sure all Motorola drivers are up to date , I believe its Motorola device manager, otherwise rsdlite will not recognize your phone
Also your phone needs to be in fastboot mode, hopefully it won't reboot during the process
Sent on my Moto X

I've made sure the drivers are correct. RSDLite still won't recognize the device.

Konvett said:
I've made sure the drivers are correct. RSDLite still won't recognize the device.
Click to expand...
Click to collapse
What version of windows are you running
Sent on my Moto X

flashallthetime said:
What version of windows are you running
Sent on my Moto X
Click to expand...
Click to collapse
Windows 8

Konvett said:
Windows 8
Click to expand...
Click to collapse
That's probably the issue, try to run rsdlite under windows 7 comp. Its either that or a driver issue, leave it to windows 8, did you find the thread with the instructions to use rsdlite?
Sent on my Moto X

What keys are you hitting by chance when you get into fastboot? I had the same problem with mine while trying to root it and get software updated on it, but mine is a developer edition so I had some options.
I would try this first.
1. Turn phone completely off (you will have to have the phone unplugged from the wall outlet and/or computer when you do this) by beating the bootloop and powering it off manually.
2. Hold both the volume up and volume down and power button at the same time for 4 seconds and let go of all of them.
3. This should bring you to fastboot
4. Plug the phone up to your computer and open a command prompt
5. In the command prompt type in fastboot erase cache
6. Hit enter and it should show on the phone that your deleting the cache partition.
7. After its complete use the volume down key to go to Normal Power Up or Normal Boot (I can't remember what exactly the option is)
8. Hit the volume up key to select it and it will start booting back in Android.
Let the phone sit for a few seconds and see if it restarts anymore. If it does then your only option to stop it is to either erase user data or RSDLite it back to factory. You can erase the userdata by doing this.
1. Power off the phone
2. Hit the volume down and volume up and power button for 4 seconds and then let go
3. While the phone is in fastboot open up a command prompt on your computer and hook up the phone by USB to your computer
4. In the command prompt type in fastboot erase userdata
5. Hit enter
6. After it completes type in fastboot erase cache
7. Hit enter
8. Use the volume down key to select Normal Powerup or Normal Boot and hit the volume up key
9. That should get you back to android and let you set it back up. After that I would no longer take an OTA update unless you removed root.

flashallthetime said:
that's probably the issue, try to run rsdlite under windows 7 comp. Its either that or a driver issue, leave it to windows 8, did you find the thread with the instructions to use rsdlite?
Sent on my moto x
Click to expand...
Click to collapse
thank you flashallthetime!!!!! **** you windows 8!!!!!!!

Konvett said:
thank you flashallthetime!!!!! **** you windows 8!!!!!!!
Click to expand...
Click to collapse
So did it work?
Sent on my Moto X

supr2nr said:
What keys are you hitting by chance when you get into fastboot? I had the same problem with mine while trying to root it and get software updated on it, but mine is a developer edition so I had some options.
I would try this first.
1. Turn phone completely off (you will have to have the phone unplugged from the wall outlet and/or computer when you do this) by beating the bootloop and powering it off manually.
2. Hold both the volume up and volume down and power button at the same time for 4 seconds and let go of all of them.
3. This should bring you to fastboot
4. Plug the phone up to your computer and open a command prompt
5. In the command prompt type in fastboot erase cache
6. Hit enter and it should show on the phone that your deleting the cache partition.
7. After its complete use the volume down key to go to Normal Power Up or Normal Boot (I can't remember what exactly the option is)
8. Hit the volume up key to select it and it will start booting back in Android.
Let the phone sit for a few seconds and see if it restarts anymore. If it does then your only option to stop it is to either erase user data or RSDLite it back to factory. You can erase the userdata by doing this.
1. Power off the phone
2. Hit the volume down and volume up and power button for 4 seconds and then let go
3. While the phone is in fastboot open up a command prompt on your computer and hook up the phone by USB to your computer
4. In the command prompt type in fastboot erase userdata
5. Hit enter
6. After it completes type in fastboot erase cache
7. Hit enter
8. Use the volume down key to select Normal Powerup or Normal Boot and hit the volume up key
9. That should get you back to android and let you set it back up. After that I would no longer take an OTA update unless you removed root.
Click to expand...
Click to collapse
Thank you for the help, I was able to get RSD Lite to recognize the device. I'm restarting it now in the hopes that it will successfully have flashed the stock ROM. I now don't really know what to do about rooting/unlocking the bootloader. Any ideas? Not sure if it's possible for the AT&T version due to all their stupid restrictions.

Konvett said:
Thank you for the help, I was able to get RSD Lite to recognize the device. I'm restarting it now in the hopes that it will successfully have flashed the stock ROM. I now don't really know what to do about rooting/unlocking the bootloader. Any ideas? Not sure if it's possible for the AT&T version due to all their stupid restrictions.
Click to expand...
Click to collapse
You can't unlock with AT& idiot
If its a retail version, you have to go back to 4.2 I believe and use rockmymoto do the upgrade and use slapmymoto, not sure as my boot loader is unlocked. I used the easy way to root
Sent on my Moto X

flashallthetime said:
You can't unlock with AT& idiot
If its a retail version, you have to go back to 4.2 I believe and use rockmymoto do the upgrade and use slapmymoto, not sure as my boot loader is unlocked. I used the easy way to root
Sent on my Moto X
Click to expand...
Click to collapse
This one is currently on 4.2.2. I should be able to go right from there right?

Konvett said:
This one is currently on 4.2.2. I should be able to go right from there right?
Click to expand...
Click to collapse
I believe so but read the slapmymoto thread, so I guess it booted
Sent on my Moto X

I think I'm asking the wrong questions.
With my Moto X (AT&T - NOT developer edition) on 4.2.2, I'd like to install CyanogenMod. Of course the bootloader is locked, but I'm not presently aware if it has been cracked. I don't want to install TWRP and risk bricking it if it's not going to work.
Has the bootloader been cracked yet?

Konvett said:
I think I'm asking the wrong questions.
With my Moto X (AT&T - NOT developer edition) on 4.2.2, I'd like to install CyanogenMod. Of course the bootloader is locked, but I'm not presently aware if it has been cracked. I don't want to install TWRP and risk bricking it if it's not going to work.
Has the bootloader been cracked yet?
Click to expand...
Click to collapse
No, your boot loader will likely never be unlocked, as for cm Roms , again not at this point in time. The only way for locked boot loaders to flash Roms is with safestrap and that requires a safestrap compatible kernel. To make you feel better, you can get all the customizations that cm has with xposed frameworks and a few modules on our stock ROM. So there's really no reason for cm roms
Sent on my Moto X

flashallthetime said:
No, your boot loader will likely never be unlocked, as for cm Roms , again not at this point in time. The only way for locked boot loaders to flash Roms is with safestrap and that requires a safestrap compatible kernel. To make you feel better, you can get all the customizations that cm has with xposed frameworks and a few modules on our stock ROM. So there's really no reason for cm roms
Sent on my Moto X
Click to expand...
Click to collapse
I'll check into xposed, thank you!

[Q] Dead Droid on factory reset

Im trying to update from 4.1.2 , it gets to %30 and gives me dead droid.
So i thought a factory reset might help, it didn't but i saw update from external as an option so i downloaded the latest update to my sd but i cant get back to that screen (bootloader?)...when i hold the vol buttons and power then select reset i get a black screen for a few seconds then dead droid...nothing else from that menu boots anything but os.
I tried draining the battery; played video till it died then left it for 4hrs.
Is the bootloader corrupted or do i just need to pull the battery(/drain it more)?

When you get to android Andy laying on his back hold volume up and tap the power button that should take you into the recovery menu options...you should consider upgrading via rsd lite to 182/183.46.10 then unlock your bootloader as if you go straight to .15 there will be no root or unlocked boot loader for you... Everything you need is here and do not attempt to update on a low battery there is a big chance at a brick if you do that... Best of luck
We cannot teach people anything; we can only help them discover it within themselves.

The first time I tried RSD lite (6.1.5) it put it into fastboot immediately after I pressed start, then timed out and said failed to put phone in fastboot.
I tried putting it in fastboot manually, which is recognized and gave me the following
Code:
Failed flashing process. Unknown fastboot command. (getvar)
and now this is all i get when i try...rebooted pc and phone a few times, i have moto device manager (latest) installed and im trying to flash "VZW_XT907_4.4.2-KDA20.62-10.1_CFC_1FF.xml".
i found a youtube video on this that told me to extract the zip and delete
Code:
<step operation="getvar" var="max-download-size" />
from the xml file and now it just says
Code:
Failed flashing process. Unknown fastboot command. ()
Edit:
I uninstalled 6.1.5 and installed 6.1.4, i still had to try a few times but it worked.
Thanks for your help.