Database Develop

[FIX] Enable download mode by force adb push update.zip without permission

MY Phone Condition:
My phone was previously install with voodoo rom and use clockwork recovery to restore to my stock rom that i backup and it crash half way.
My phone was hardware lock this mean no matter how i press the volume and power button , i will never get into download mode. non of the method posted work !
My phone cannot use "adb reboot download" because there is no OS and it was stuck in the recovery loop.
It does not have clockwork recovery because i formatted my internal sdcard
If i do have clockwork recovery and i use restore image or install new from zip , i still stuck in the recovery mode after reboot several times.
My phone does not mount to internal sdcard because i don't even know what i did on this part.
I believe i screw up my partition of the phone.
DO IT AT YOUR OWN RISK.
You need the Samsung USB driver and you can get it from Here
http://forum.xda-developers.com/showthread.php?t=728929
First Part
1. Download update.zip from the link below. This was post by another member.
The post is here http://forum.xda-developers.com/showthread.php?t=804305
2. Place the update.zip in tools folder so you can push it into your phone by using adb command
3. Plug usb into the phone and your phone should be on the Android system recovery <2e>
4. Use your volume button to select reinstall package, don't press power button yet.
5. constant "adb push update.zip /sdcard" from computer , you will get permission denied.
6. While you are constantly pushing the adb command from computer. press the power button on the phone so it install update.zip from sdcard.
7. This is the part where it force adb push into sdcard without permission
8. once the update.zip install completed. unplug the usb cable from the phone and take the battery out.
9. put the battery back to the phone then press on both volume button.
10. While holding both volume button , plug in your usb cable and it will boot to download screen.
If you need use Odin to flash your phone to original stock rom. Go to the Second Part

Second Part:
If you get black screen with only 4 light on the bottom after flashing from Odin.
Follow http://forum.xda-developers.com/showthread.php?t=728698
There should be T959-PDA.tar,T959-CSC.tar and T959-Phone.tar within the package.
Check "Re-Partition" , "Auto Reboot" and "F.Reset Time" check box. Use the PIT 0512 version. Use "PDA", "PHONE" and "CSC" from the link above.
After flashing with Odin, you will loose the download mode. repeat the first part and you are good to go.
Here is the link on rooting the phone
http://wiki.cyanogenmod.com/index.php?title=Full_Update_Guide_-_Samsung_Galaxy_S_(Vibrant)

If your phone is hardware locked, how are you able to get into recovery? Hardware locked phone means no recovery and download mode.
Sent from my SGH-T959 using XDA App

mr2t32 said:
If your phone is hardware locked, how are you able to get into recovery? Hardware locked phone means no recovery and download mode.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
my hardware lock mean cannot use the button method to get into download mode and using adb reboot download does not help too.

Im pretty sure hardware lock does not mean no recovery. Just no button download mode
Sent from my SGH-T959 using XDA App

you saved my life man. thank you so much. this was the only thing that worked, after days of frustration

No, it means both.
Sent from my SGH-T959 using XDA App

muncknr said:
you saved my life man. thank you so much. this was the only thing that worked, after days of frustration
Click to expand...
Click to collapse
i was about to give up. i was trying to push update.zip and do adb reboot download left and right and no luck untill i found this method. It took me a week to figure it out

wildklymr said:
No, it means both.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
my recovery was working because i was stuck in the a loop. ya , this update.zip pretty much do both download mode and recovery mode.

What the point of this? Does the other thread not cover this??

Master™ said:
What the point of this? Does the other thread not cover this??
Click to expand...
Click to collapse
Are you asking or you are insulting ?

jaex said:
Are you asking or you are insulting ?
Click to expand...
Click to collapse
probably asking. Considering there is another thread on the same topic that has been on the front page for over a week now, with several pages of replies.
http://forum.xda-developers.com/showthread.php?t=804305
EDIT: So you were bricked and hardware locked and got yourself out of it? If thats the case then yets its different than that thread and why didn't you just come out and say it?

nermie said:
probably asking. Considering there is another thread on the same topic that has been on the front page for over a week now, with several pages of replies.
http://forum.xda-developers.com/showthread.php?t=804305
EDIT: So you were bricked and hardware locked and got yourself out of it? If thats the case then yets its different than that thread and why didn't you just come out and say it?
Click to expand...
Click to collapse
You figure it out after all. I already stated the condition of my phone ! My phone was pretty bricked at that point. There is way for me to push any files into the phone because i don't have permission and my phone will not go to download mode by using the volume button. It just stuck at recovery mode.
There are guide out there teach you to use "adb push download". This method only work if you are in your phone and you turn on debug mode. My phone crash at the clockwork recovery bootloader. Then i formated my internal sdcard that hold the clockwork. next i push a stock update.zip that does not have su and busybox so i lost the capability to push anything into the phone.
no download mode , no permission, no sdcard --> You tell me how can i use the method that post few week ago ?

muncknr said:
you saved my life man. thank you so much. this was the only thing that worked, after days of frustration
Click to expand...
Click to collapse
Thank You

Thank ! You save my phone !

unfortunately, i was one of those careless people to brick my phone via Voodoo.
Firstly, i tried to "FLASH" the disable_voodoo zip file via Clockwork, i put it in root, and never created any folders. i knew i had to disable voodoo before flashing but my steps were wrong.
sadly enough, my phone was also HW locked, so i got it exchanged. now im not using voodoo YET and i my new vibrant can handle OC and has the recovery/download mode via buttons.

atlaswingpasaway said:
unfortunately, i was one of those careless people to brick my phone via Voodoo.
Firstly, i tried to "FLASH" the disable_voodoo zip file via Clockwork, i put it in root, and never created any folders. i knew i had to disable voodoo before flashing but my steps were wrong.
sadly enough, my phone was also HW locked, so i got it exchanged. now im not using voodoo YET and i my new vibrant can handle OC and has the recovery/download mode via buttons.
Click to expand...
Click to collapse
i use shell to create the file that disable voodoo. after disable voodoo , i was able to do restore and install new rom unfortunately after restore or install new rom , it still reboot into recovery.

I also forgot to disable voodoo, and this was before there were fix instructions posted. So i basically effed up my phone to the point of being stuck in the samsung recovery loop, no hardware download mode, no clockwork recovery, no update.zp, no adb download.
I really thought I had completely bricked my phone, I tried this just out of desperation and what do you know, push update.zip over and over and click and it goes through, which allowed me to get into download mode.

muncknr said:
I also forgot to disable voodoo, and this was before there were fix instructions posted. So i basically effed up my phone to the point of being stuck in the samsung recovery loop, no hardware download mode, no clockwork recovery, no update.zp, no adb download.
I really thought I had completely bricked my phone, I tried this just out of desperation and what do you know, push update.zip over and over and click and it goes through, which allowed me to get into download mode.
Click to expand...
Click to collapse
nice , you just have to re-root and install the new rom again , if it brick again , just use this method and you are good again.many of us forgot to disable the voodoo before we restore or install new rom and this crashes the phone.

Need some help really bad
Ok so I have a similar situation as you did (OP), only mine is a bit worse... In my irrational "in the moment" fear of the situation, I used adb reboot recovery to get into recovery mode (HW locked phone) and I did the option that deletes all the **** on the phone and restores the phone to its original format (I think it reinstalled the OS or something, because it looks brand new). So now, whenever I boot up, it does the annoying black screen with the 4 glowing buttons thing for a while, and then eventually the OS actually shows up on the screen. Then it does "scanning media" thing over and over again, but thats not the main problem. I figured, hey this isnt so bad atleast I found your thread and would be able to use your method to help restore my phone... the problem is that somehow my "settings" button is totally gone from the app menu, and I cant get it into debug mode, so I cant use either adb or your method or ANYTHING!! My phone is practically bricked as I cant do anything because its constantly laggy and turns back to the black screen thing, and then when it is showing the homescreen I cant do **** because even swiping to another screen takes like 5 minutes to do cause its so laggy. So basically I ****ed up, and I really need some help.. Im kinda a noob at this whole thing and im really outa options as far as I can tell.. does anyone know what I can do to repair my phone? Thanks!

I have rebooted the tablet 10+ times with vol + and vol - and it is still stuck on th

I have rebooted the tablet 10+ times with vol + and vol - and it is still stuck on the Google screen when it starts up. In fact I can't make it turn off, only reboot and go right back to the Google text screen. Any ideas?

morell2 said:
I have rebooted the tablet 10+ times with vol + and vol - and it is still stuck on the Google screen when it starts up. In fact I can't make it turn off, only reboot and go right back to the Google text screen. Any ideas?
Click to expand...
Click to collapse
Are you running stock, or did you root and customize?

Try plugging it in to a computer. A lot of us are finding better results when you do. You may end up having to do more. But just being connected to a computer has helped in the past. Quick fix before you start trying adb
Sent from my Nexus 7 using Xparent SkyBlue Tapatalk 2

Turn fastboot off in the power settings. I'm not sure if it has the fastboot setting, but that would be your problem.

kiewee3 said:
Turn fastboot off in the power settings. I'm not sure if it has the fastboot setting, but that would be your problem.
Click to expand...
Click to collapse
Err ..... it won't boot.
Does ADB work at this stage? Assuming you are rooted with CWM recovery, try
Code:
adb reboot recovery
Then from recovery, power it off completely. If fastboot is the problem, this should workaround it for you.

morell2 said:
I have rebooted the tablet 10+ times with vol + and vol - and it is still stuck on the Google screen when it starts up. In fact I can't make it turn off, only reboot and go right back to the Google text screen. Any ideas?
Click to expand...
Click to collapse
It's karma because of your ridiculous signature.
Anywho. What did you do to the device? Attempt to root it? What happened between it working and not working?

khaytsus said:
It's karma because of your ridiculous signature.
Click to expand...
Click to collapse
Page-long signatures seem to be getting more prevalent, sadly. Not great reading on a 1280x800 laptop.

it now work but all data delete!
i do unroot and back to stock with rootkit 1.5.2 and after it is work!

wmoore said:
Page-long signatures seem to be getting more prevalent, sadly. Not great reading on a 1280x800 laptop.
Click to expand...
Click to collapse
Right. I can't figure out why people think others want to see large pictures of their crap.

just lou said:
Right. I can't figure out why people think others want to see large pictures of their crap.
Click to expand...
Click to collapse
Don't be mean. It's a visual aid to go with his query. Just in case we don't know what a Nexus 7 is (here in the Nexus 7 forum).

Rock-&-Roll-Hedgehog said:
Don't be mean. It's a visual aid to go with his query. Just in case we don't know what a Nexus 7 is (here in the Nexus 7 forum).
Click to expand...
Click to collapse
Oh. Now I see.

The nice thing is that Signatures can be disabled if you so choose, it'd just be nice if everyone kept a modestly sized signature.

wmoore said:
Page-long signatures seem to be getting more prevalent, sadly. Not great reading on a 1280x800 laptop.
Click to expand...
Click to collapse
XDA Signatures: The new Geociities
morell2 said:
it now work but all data delete!
i do unroot and back to stock with rootkit 1.5.2 and after it is work!
Click to expand...
Click to collapse
wat?
When you oem unlock, data is deleted, it tells you that. Otherwise, no idea what you're talking about.

Known issue about the bootloader. Have to be connected to a computer via USB to be able to boot into recovery. if you have a working system partition you can use a script or other apps that will boot you into recovery.
Also the bootloader will freeze if you try to boot into it via the buttons if you are connected to a power outlet via USB
Sent from my Nexus 7

evonc said:
Known issue about the bootloader. Have to be connected to a computer via USB to be able to boot into recovery. if you have a working system partition you can use a script or other apps that will boot you into recovery.
Also the bootloader will freeze if you try to boot into it via the buttons if you are connected to a power outlet via USB
Sent from my Nexus 7
Click to expand...
Click to collapse
That's interesting. I pretty much always make sure I'm plugged in before going into recovery / bootloader anyway (I'm paranoid about running out of battery mid-operation). I also pretty much always use adb reboot recovery, etc rather than hardware buttons.

evonc said:
Known issue about the bootloader. Have to be connected to a computer via USB to be able to boot into recovery. if you have a working system partition you can use a script or other apps that will boot you into recovery.
Also the bootloader will freeze if you try to boot into it via the buttons if you are connected to a power outlet via USB
Sent from my Nexus 7
Click to expand...
Click to collapse
wmoore said:
That's interesting. I pretty much always make sure I'm plugged in before going into recovery / bootloader anyway (I'm paranoid about running out of battery mid-operation). I also pretty much always use adb reboot recovery, etc rather than hardware buttons.
Click to expand...
Click to collapse
Not neccessarily true. I use an app called Quick boot. I can boot into recovery from it with Ease. Lets me set up Widgets/icon for recovery and I have one for reboot. No need for me to hook up to pc. Anywhere at anytime I can boot into recovery on my Nexus 7. I can also set one up for bootloader. If someone gets stuck on bootloader screen, the hardware button press for reboot works to get out of there.
They have a free version of the app and it works perfectly. Check it out. No need to run to a pc everytime you want to flash a rom or something. Battery is nothing to worry about. As long as you have 50%(really even less than that), you good to flash, wipe, or what ever.

demandarin said:
Not neccessarily true. I use an app called Quick boot.
Click to expand...
Click to collapse
Me too. Though I'm old school and still like to type commands rather than point and click. I'll be looking at Quick Boot but still go to PowerShell (which I always have open) and type adb reboot.:silly:

All the various apps that offer rebooting options will work as they are still executing the same terminal commands that you would've had to type in in order to reboot it.
The issue is that you would still require a working system partition in order to boot into recovery (stock/twrp/cwm) without any USB connection. Incase of a soft brick, you will need to connect to a computer in order to get into recovery so i would suggest people make sure they have one nearby when they're flashing stuff.

I just went through this. I boinked my setup and it was bootlooping. I couldn't get into CWM.
Just press and hold Power+VolDwn+VolUp until you get into the stock bootloader. Now plug in your USB to to a PC.
Stay in the bootloader. Mine actually kinda froze but it will unfreeze after a while. Don't select anything. Just stay there.
Now you can use Fastboot commands to reboot into CWM. ADB only works when the phone is on.
I think the command is "fastboot reboot recovery".
This will put you in CWM. You can also take this opportunity to reflash your recovery here too. I reflashed mine just to be on the safe side before rebooting it.
Sent from my Nexus 7 using xda premium

[Q] So, I bricked my phone.

Everyone should do it at least once, really. Teaches humility and caution.
I was messing around between ROMs with SafeStrap, testing battery life. Had gone ahead and tested SlimKat while I had it booted, found it acceptable, so I decided to do stock JB next.
It seemed only right and proper to install myfishbear's deodexed ROM over stock, so if it turned out that I was going to use it, I wouldn't need to shuffle it anywhere. And, I imagine, it would have been fine if I had simply installed it over stock.
However, in a moment of brilliance, I wiped the stock slot, installed the deodexed ROM, ignored the "NO O/S MORON" warning, and rebooted. In my defense, I had read somewhere that new versions of SS made a safety check to make sure necessary boot files were intact, and I knew that there were recovery options in case of bricking, so I wasn't especially worried if I screwed something up.
Well, I screwed something up, obviously. If I had to guess, I would say that I wiped the bootloader out?
So now:
Trying to let it boot results in a black screen
Trying to get into AP FastBoot results in a black screen
Recovery is accessible. However...
Trying to flash firmware from an SD card zip aborts itself when verifying the package. Have tried a few Android 4.x packages so far, for variety. To be honest, I didn't really expect this to work in the first place.
Trying to use Fastboot from recovery results in Windows detecting the phone as "Droid4", improperly installed (good ol' yellow triangle), and refuses to let me install it as the Motorola Flash Interface as it should be (won't even give me the option when I try to forcefully install the driver).
What shall I try next?

Septfox said:
Everyone should do it at least once, really. Teaches humility and caution.
I was messing around between ROMs with SafeStrap, testing battery life. Had gone ahead and tested SlimKat while I had it booted, found it acceptable, so I decided to do stock JB next.
It seemed only right and proper to install myfishbear's deodexed ROM over stock, so if it turned out that I was going to use it, I wouldn't need to shuffle it anywhere. And, I imagine, it would have been fine if I had simply installed it over stock.
However, in a moment of brilliance, I wiped the stock slot, installed the deodexed ROM, ignored the "NO O/S MORON" warning, and rebooted. In my defense, I had read somewhere that new versions of SS made a safety check to make sure necessary boot files were intact, and I knew that there were recovery options in case of bricking, so I wasn't especially worried if I screwed something up.
Well, I screwed something up, obviously. If I had to guess, I would say that I wiped the bootloader out?
So now:
Trying to let it boot results in a black screen
Trying to get into AP FastBoot results in a black screen
Recovery is accessible. However...
Trying to flash firmware from an SD card zip aborts itself when verifying the package. Have tried a few Android 4.x packages so far, for variety. To be honest, I didn't really expect this to work in the first place.
Trying to use Fastboot from recovery results in Windows detecting the phone as "Droid4", improperly installed (good ol' yellow triangle), and refuses to let me install it as the Motorola Flash Interface as it should be (won't even give me the option when I try to forcefully install the driver).
What shall I try next?
Click to expand...
Click to collapse
What recovery is accessible?
Sent from my DROIDX using XDA Free mobile app

sd_shadow said:
What recovery is accessible?
Sent from my DROIDX using XDA Free mobile app
Click to expand...
Click to collapse
The second one, Android's recovery.

Septfox said:
The second one, Android's recovery.
Click to expand...
Click to collapse
Stock recovery is worthless for flashing.
Need to use ap fastboot with rsd lite to flash stock firmware
Sent from my DROIDX using XDA Free mobile app
---------- Post added at 01:53 AM ---------- Previous post was at 01:52 AM ----------
http://forum.xda-developers.com/showthread.php?t=2817531
Sent from my DROIDX using XDA Free mobile app
---------- Post added at 01:55 AM ---------- Previous post was at 01:53 AM ----------
Or could just try
Power off, Hold M key, Power on, release buttons at
Boot Mode Selection Menu> Scroll down with volume down button, to BP Tools, Select with Volume UP button, should boot directly to SafeStrap
Sent from my DROIDX using XDA Free mobile app

sd_shadow said:
Stock recovery is worthless for flashing.
Need to use ap fastboot with rsd lite to flash stock firmware
Click to expand...
Click to collapse
I've realized this, yes. If the stock recovery weren't useless, there wouldn't be the need for using fastboot. I was just playing with it, since I couldn't get anything else to work properly.
sd_shadow said:
Or could just try
Power off, Hold M key, Power on, release buttons at
Boot Mode Selection Menu> Scroll down with volume down button, to BP Tools, Select with Volume UP button, should boot directly to SafeStrap
Click to expand...
Click to collapse
The key word being "should"...but I've actually already tried this, after seeing it in a couple of other posts. Booting this way results in the same black screen as booting without holding M.

Right, well. I made a factory-style cable, to avoid killing my battery while I screw around.
I would very much appreciate any further suggestions on how to proceed. Is there any way to get the phone running from stock recovery, or am I completely SOL without AP Fastboot working from the first recovery menu?
Picking up another mainboard is always an option, but I'd really prefer not to if at all possible.

Septfox said:
Right, well. I made a factory-style cable, to avoid killing my battery while I screw around.
I would very much appreciate any further suggestions on how to proceed. Is there any way to get the phone running from stock recovery, or am I completely SOL without AP Fastboot working from the first recovery menu?
Picking up another mainboard is always an option, but I'd really prefer not to if at all possible.
Click to expand...
Click to collapse
power off, press both volume buttons

sd_shadow said:
power off, press both volume buttons
Click to expand...
Click to collapse
That gets me the first menu.
Everything in this menu, aside from Recovery, results in a black screen; even the M-to-BP Tools Safestrap shortcut.
Recovery, of course, gets me to android recovery, which apparently borders on useless. I mean, there's a fastboot option there, but it doesn't seem to work properly.

Septfox said:
That gets me the first menu.
Everything in this menu, aside from Recovery, results in a black screen; even the M-to-BP Tools Safestrap shortcut.
Recovery, of course, gets me to android recovery, which apparently borders on useless. I mean, there's a fastboot option there, but it doesn't seem to work properly.
Click to expand...
Click to collapse
Power off your phone, hold volume down button and press power button, until you see AP Fastboot Flash Mode

sd_shadow said:
Power off your phone, hold volume down button and press power button, until you see AP Fastboot Flash Mode
Click to expand...
Click to collapse
Ok, just so we're on the same page here.
First menu:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have no problem getting to this menu. Everything but Recovery in this menu fails to do anything but go to a black screen; including AP Fastboot. Holding M while opening this menu, then selecting BP Tools to try and skip to Safestrap, doesn't work.
Recovery:
Useless, because it can't seem to actually flash packages (I would guess because how borked everything is), and the fastboot option doesn't seem to work properly.

Septfox said:
Ok, just so we're on the same page here.
Click to expand...
Click to collapse
When from power off, hold just volume down, power on, should go straight to ap fastboot
Useless, because it can't seem to actually flash packages (I would guess because how borked everything is), and the fastboot option doesn't seem to work properly.
Click to expand...
Click to collapse
No only update.zip(s) can be installed in stock recovery and only if Stock rom is installed, and only if it is the correct update, can not install updates on same system version, can not downgrade, so if newest system version is installed, there is no update.zip that will work. It's the same for every Motorola Droid for last 4 years.
---------- Post added at 06:10 PM ---------- Previous post was at 06:05 PM ----------
updates.zips are named like Blur_Version.6.16.217.XT894.Verizon.en.US.zip
rsd lite fles are like cdma_maserati_9.8.2O-72_VZW-18-2_1ff.xml.zip
---------- Post added at 06:15 PM ---------- Previous post was at 06:10 PM ----------
could try
Code:
adb reboot-bootloader

sd_shadow said:
When from power off, hold just volume down, power on, should go straight to ap fastboot
No only update.zip(s) can be installed in stock recovery and only if Stock rom is installed, and only if it is the correct update, can not install updates on same system version, can not downgrade, so if newest system version is installed, there is no update.zip that will work. It's the same for every Motorola Droid for last 4 years.
---------- Post added at 06:10 PM ---------- Previous post was at 06:05 PM ----------
updates.zips are named like Blur_Version.6.16.217.XT894.Verizon.en.US.zip
rsd lite fles are like cdma_maserati_9.8.2O-72_VZW-18-2_1ff.xml.zip
Click to expand...
Click to collapse
Ah, I see. That seems...rather short-sighted of Motorola. They knew very well that many of their users would be doing monumentally stupid things - like wiping the phone, for example - being able to debrick it from recovery would be extraordinarily helpful...
Then again, I'm sure that stock recovery on my Ally was just as unhelpful, so eh.
This is my first Droid, my first Motorola ever in fact, so I didn't know.
I'm aware of the naming conventions, I actually did download the RSD lite file for debricking...just couldn't get anywhere to use it. Several updates too, to spam at the package installer; that of course got me absolutely nowhere.
Anyway, I finally got into Fastboot.
What I was trying to do originally was disconnect the battery to power the phone off, then reconnect it and follow your instruction for going straight into Fastboot. This wasn't working; the phone refused to power on until I let go of all buttons. Is there some other way of shutting the phone off? Simply pressing the power button does nothing for me.
I thought we were having a breakdown in communication, since Vol Down+Power is supposed to be for reset. I apologize.
What finally got me in was disconnecting the battery, then holding the button down while "manually" powering on by using the factory-style cable. I now have the AP Fastboot menu; I just have to get Windows to install it properly (currently up, improperly as I understand, as "Mot Single ADB Interface"). I have your Google Docs guide up, so hopefully I can proceed from here without screwing anything else up.

Septfox said:
Ah, I see. That seems...rather short-sighted of Motorola. They knew very well that many of their users would be doing monumentally stupid things - like wiping the phone, for example - being able to debrick it from recovery would be extraordinarily helpful...
Then again, I'm sure that stock recovery on my Ally was just as unhelpful, so eh.
This is my first Droid, my first Motorola ever in fact, so I didn't know.
Click to expand...
Click to collapse
all "Droid"(s) are designed for Verizon, and Verizon does not want their devices rooted, so this would not happen.
I'm aware of the naming conventions, I actually did download the RSD lite file for debricking...just couldn't get anywhere to use it. Several updates too, to spam at the package installer; that of course got me absolutely nowhere.
Anyway, I finally got into Fastboot.
What I was trying to do originally was disconnect the battery to power the phone off, then reconnect it and follow your instruction for going straight into Fastboot. This wasn't working; the phone refused to power on until I let go of all buttons. Is there some other way of shutting the phone off? Simply pressing the power button does nothing for me.
I thought we were having a breakdown in communication, since Vol Down+Power is supposed to be for reset. I apologize.
What finally got me in was disconnecting the battery, then holding the button down while "manually" powering on by using the factory-style cable. I now have the AP Fastboot menu; I just have to get Windows to install it properly (currently up, improperly as I understand, as "Mot Single ADB Interface"). I have your Google Docs guide up, so hopefully I can proceed from here without screwing anything else up.
Click to expand...
Click to collapse
Windows does not like Motorola devices/Drivers, may need to reboot pc and droid 4 a few times

Let me start this post off by saying THANK YOU for sticking around and putting up with me. It has been a trying day, both because of this and offline stuff going on. I'm sorry if any of it bled over into my responses.
Flash was successful, phone is currently doing its thing, and I now know several new things about not only my phone, but Motorola devices in general. As well as what to avoid doing at all cost in the future unless I want more headaches.
sd_shadow said:
all "Droid"(s) are designed for Verizon, and Verizon does not want their devices rooted, so this would not happen.
Click to expand...
Click to collapse
Yes, god forbid people try and get the most out of devices that they paid several hundred dollars and/or are roped into multi-year contracts for.
sd_shadow said:
Windows does not like Motorola devices/Drivers, may need to reboot pc and droid 4 a few times
Click to expand...
Click to collapse
Funny thing about that.
I couldn't get Windows to install the phone "properly". Manually installing it as the Motorola Flash Interface simply made it unusable. After repeatedly rebooting the phone and computer, trying different cables and installation orders and methods, I finally gave up and left it as "Mot Single ADB Interface". RSD lite picked it up, but wouldn't display any information about it; didn't care, told it to flash anyway. The way I figured, it's not like it could hurt the phone much more than it already was.
Lo and behold, it worked. I'm not saying that this is a typical case and leaving it alone will work for everyone, but for anyone looking for an answer in the future: if you can't install it "properly", try flashing it anyway, provided it displays in Device Manager as functioning with no issues.
Final question, before I go off and do something stupid again: how does one flash ROMs into the stock "slot"? Is it a simple matter of installing without wiping the existing partitions?
Though frankly, at this point, I'm almost happy to just leave well enough alone and write that 3gb off as unusable.

Can't remember if all the ROMs can be installed on stock slot.
Cm11 and slimkat can just in safestrap/twrp, select stock slot, factory reset, and install.
Sent from my DROIDX using XDA Free mobile app

Indeed, Slimkat installed with absolutely no issue, and is at this point well on its way to being acceptably tweaked for daily usage. Aside from the rare random hot reboot, anyway.
Thanks again for your help, I can say with certainty that the phone wouldn't be working without it.

UnBrick Memo PAd me176cx

Hello, i have bricked my Memo pad 7 then me176cx model and need help fixing it. i installed the adb driver and cant get into recovery for some reason, but i can get into the bootloader. but i cant figure out how to flash the update from the asus website threw the bootloader. is there anyway to unbrick it? :good:

clapper66 said:
Hello, i have bricked my Memo pad 7 then me176cx model and need help fixing it. i installed the adb driver and cant get into recovery for some reason, but i can get into the bootloader. but i cant figure out how to flash the update from the asus website threw the bootloader. is there anyway to unbrick it? :good:
Click to expand...
Click to collapse
Dont bother, I have tried for a week straight trying to unbrick mine. I did a factory reset and it destroyed my whole filesystem. :/

i just got mine so i just got a replacement from amazon

Mine was a present and I have no idea where they got it and they tossed the receipt. I'm sol. I'm broke so RMA may take a while as well! xD
Sent from my Galaxy Nexus
---------- Post added at 02:41 AM ---------- Previous post was at 02:36 AM ----------
Also for getting into recovery follow these steps. Turn off. Hold volume down and also power. When Asus pops up release power and keep hold of volume until the bootloader appears. On bootloader go down to boot recovery. When it reboots to an android guy hold volume up and down at the same time. Let go of volume up and do this r over and over until it goes to recovery. The steps are ridiculous but I know it for sure because my last week of trying to fix mine has been hell.
Sent from my Galaxy Nexus

the there is a way
applerulez1 said:
Mine was a present and I have no idea where they got it and they tossed the receipt. I'm sol. I'm broke so RMA may take a while as well! xD
Sent from my Galaxy Nexus
---------- Post added at 02:41 AM ---------- Previous post was at 02:36 AM ----------
Also for getting into recovery follow these steps. Turn off. Hold volume down and also power. When Asus pops up release power and keep hold of volume until the bootloader appears. On bootloader go down to boot recovery. When it reboots to an android guy hold volume up and down at the same time. Let go of volume up and do this r over and over until it goes to recovery. The steps are ridiculous but I know it for sure because my last week of trying to fix mine has been hell.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
http://forum.xda-developers.com/android/help/asus-memo-7-me176cx-t2814046/post57408037#post57408037

clapper66 said:
Hello, i have bricked my Memo pad 7 then me176cx model and need help fixing it. i installed the adb driver and cant get into recovery for some reason, but i can get into the bootloader. but i cant figure out how to flash the update from the asus website threw the bootloader. is there anyway to unbrick it? :good:
Click to expand...
Click to collapse
what update are you trying to flash?

Steps to unbrick (if you can get into fastboot)
clapper66 said:
Hello, i have bricked my Memo pad 7 then me176cx model and need help fixing it. i installed the adb driver and cant get into recovery for some reason, but i can get into the bootloader. but i cant figure out how to flash the update from the asus website threw the bootloader. is there anyway to unbrick it? :good:
Click to expand...
Click to collapse
I bricked mine, but I am adventurous so found a method to recover to factory.
I'm not providing links as they are searchable here on XDA.
The steps are:
1) Get the factory image from Asus
2) Get FB Tethered Recovery Launcher
3) boot into fastboot mode
4) Hook up to computer
5) ensure the device is listed with correct drivers
6) Run ADB (from your platform tools, there is a copy in FBRL folder)
8) copy the zip file from Asus to the device (adb push /path/to/local/file /mnt/sdcard/path/to/file)
9) Run launcher from FB recovery
10) Choose T2 option, follow prompts to let it do it's thing
11) You should boot into CWM on the device
12) install from zip and point to the zip file you pushed earlier
13) Follow the prompts, and presto, restored to factory and can root/update etc.

I'd like to say thanks to the good info posted here and in other threads. I got stuck in a boot loop tonight and had no idea if I'd be able to fix it. Here's what I did (combination of this thread and others)
My method requires an micro SD card and an Internet connection
1. Confirm you can boot into fastboot:
---->Reboot into fastboot (droid boot) by powering device off (hold power button down), then holding down volume up while powering on. I released the up button once the screen went blank. It should eventually present options to reboot into droidboot, reboot, update from SD, etc.
2. Download the newest firmware from ASUS
YOU NEED THE WW version most likely (worldwide?)
3. Save this to the root of your SD card
4. rename file to MOFD_SDUPDATE.zip
5. Insert card into tablet.
6. While in droidboot/fastboot Choose the option to update from SD. It reboots and uploads the firmware. I was pleasantly surprised that I got my tablet back so easily.
Hope this helps some other poor soul.

There are other methods, but in simplicity, yours seems to win the match. Thank you very much.

How did you get cwm?
Sent from my K013 using XDA Free mobile app

JarrelStudios said:
How did you get cwm?
Sent from my K013 using XDA Free mobile app
Click to expand...
Click to collapse
I do not get the option to Update from SD while in DroidBoot...why is that? I get the other options...REBOOT, REBOOT DROIDBOOT, RECOVERY, POWER OFF.
Please help! I've already sent this back to Asus, and they just sent it right back to me.

Shaundiesel said:
I do not get the option to Update from SD while in DroidBoot...why is that? I get the other options...REBOOT, REBOOT DROIDBOOT, RECOVERY, POWER OFF.
Please help! I've already sent this back to Asus, and they just sent it right back to me.
Click to expand...
Click to collapse
Click on recovery. Inside recovery you'll get a "no command" screen. Hit the center of the volume rocker (it'll take a few tries) and you'll see the update command.

jerbear294 said:
Click on recovery. Inside recovery you'll get a "no command" screen. Hit the center of the volume rocker (it'll take a few tries) and you'll see the update command.
Click to expand...
Click to collapse
thanks Jerbear (Love the name, Deadhead!), I did this which brings up regular Android recovery, but no option to update except through ADB.

Shaundiesel said:
thanks Jerbear (Love the name, Deadhead!), I did this which brings up regular Android recovery, but no option to update except through ADB.
Click to expand...
Click to collapse
Try this, then.
In the main thread somebody linked a temporary cwm session. Try booting into it and installing the update from there (Nandroid while you're at it )

Why would I not even have the option though??

Shaundiesel said:
Why would I not even have the option though??
Click to expand...
Click to collapse
I'm not exactly sure.

I need some help. I have average experience with ADB and cannot get ADB to recognize my device. Debugging on of course, and I dowloaded the zip for the drivers. I don't really know where to go from here. Any help will be greatly appreciated! I need to get this thing back up and running!!

gcballard said:
I'd like to say thanks to the good info posted here and in other threads. I got stuck in a boot loop tonight and had no idea if I'd be able to fix it. Here's what I did (combination of this thread and others)
My method requires an micro SD card and an Internet connection
1. Confirm you can boot into fastboot:
---->Reboot into fastboot (droid boot) by powering device off (hold power button down), then holding down volume up while powering on. I released the up button once the screen went blank. It should eventually present options to reboot into droidboot, reboot, update from SD, etc.
2. Download the newest firmware from ASUS
YOU NEED THE WW version most likely (worldwide?)
3. Save this to the root of your SD card
4. rename file to MOFD_SDUPDATE.zip
5. Insert card into tablet.
6. While in droidboot/fastboot Choose the option to update from SD. It reboots and uploads the firmware. I was pleasantly surprised that I got my tablet back so easily.
Hope this helps some other poor soul.
Click to expand...
Click to collapse
I'm at the Android System Recovery, however, there's no option to apply update from SD...only apply update from ADB...

jhenehj said:
I'm at the Android System Recovery, however, there's no option to apply update from SD...only apply update from ADB...
Click to expand...
Click to collapse
In this case use the Intel Atom temporary ClockWorkMod to flash it.

jerbear294 said:
In this case use the Intel Atom temporary ClockWorkMod to flash it.
Click to expand...
Click to collapse
Thanks for your reply...I'm not really sure what you're referring to, but is this about ADB sideloading? I already tried but this comes up...
Now I don't know what to do...so I badly need anyone's help here...thanks in advance!

DroidTurbo XT1254 fails to load fully (Solved)

Stock n locked DT 1254 6.0.1 latest ota rom. When turning on phone boots until stock rom supposed to work. Then toast pops up Unfortunately system UI has stopped. When you tap ok it goes away for a few seconds then comes back no matter how many times you try it. You can push power to shut down and after vibrate tap ok and tap shutdown and will shut down. You can boot into fastboot but when you go to recovery it seems to be gone. Followed root junky's restore with rsdlight several times with latest software but didn't work. Using windows 10 pc to do this. Any help appreciated...
Found this will study up...
https://forum.xda-developers.com/ge...torola-usb-drivers-rsd-lite-firmware-t3042687
Had to use an updated win7 PC for it to function correctly and restore the turbo. Must be a bug with win10 and rsd or moto drivers even tho it said it worked...

newbe1droidx said:
Stock n locked DT 1254 6.0.1 latest ota rom. When turning on phone boots until stock rom supposed to work. Then toast pops up Unfortunately system UI has stopped. When you tap ok it goes away for a few seconds then comes back no matter how many times you try it. You can push power to shut down and after vibrate tap ok and tap shutdown and will shut down. You can boot into fastboot but when you go to recovery it seems to be gone. Followed root junky's restore with rsdlight several times with latest software but didn't work. Using windows 10 pc to do this. Any help appreciated...
Found this will study up...
https://forum.xda-developers.com/ge...torola-usb-drivers-rsd-lite-firmware-t3042687
Click to expand...
Click to collapse
You get this fixed?
Which bootloader?
using QUARK_VERIZON_6.0.1_MCG24.251-5-5_cid2_subsidy-DEFAULT_CFC.xml.zip

sd_shadow said:
You get this fixed?
Which bootloader?
using QUARK_VERIZON_6.0.1_MCG24.251-5-5_cid2_subsidy-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
No caing for very senior father and don't have all the time I want, do have 5-5 from root junky but didn't work. Possibly from using win 10. Am restoring a HP win 7 machine now doing updates and etc to try it. Thanks for checking up on me I appreciate all you've done since droid x days. Will keep updating as I can...

newbe1droidx said:
No caing for very senior father and don't have all the time I want, do have 5-5 from root junky but didn't work. Possibly from using win 10. Am restoring a HP win 7 machine now doing updates and etc to try it. Thanks for checking up on me I appreciate all you've done since droid x days. Will keep updating as I can...
Click to expand...
Click to collapse
Windows 10 can be a problem.
Sent from my Moto E (4) using Tapatalk

@sd_shadow Windows 7 machine did the trick, but getting it updated was tricky, had to make sure security essentials was installed and activated. then updates would happen. Used Motorola device mgr and rsdlite 6.2.4 then flashed QUARK_VERIZON_6.0.1_MCG24.251-5-5_cid2_subsidy-DEFAULT_CFC.xml.zip. So far signing in ok and restoring apps and data from google, see what gets restored. But still no recovery available. Did I miss something?

newbe1droidx said:
@sd_shadow Windows 7 machine did the trick, but getting it updated was tricky, had to make sure security essentials was installed and activated. then updates would happen. Used Motorola device mgr and rsdlite 6.2.4 then flashed QUARK_VERIZON_6.0.1_MCG24.251-5-5_cid2_subsidy-DEFAULT_CFC.xml.zip. So far signing in ok and restoring apps and data from google, see what gets restored. But still no recovery available. Did I miss something?
Click to expand...
Click to collapse
Why are you trying to get to recovery, it's mostly useless, on a Motorola

just trying to get it back to factory, not my phone for a friend. Thats all
OK found this for stock recovery when you see a dead andy with no command: In the dead andy screen press vol up + power for 4 seconds. if nothing happens try again, is a little tricky. Seems an update changed how you access recovery. Thanks for the help

newbe1droidx said:
just trying to get it back to factory, not my phone for a friend. Thats all
Click to expand...
Click to collapse
Rsd lite didn't wipe the device?
that's default.
Sent from my Moto E (4) using Tapatalk
---------- Post added at 06:52 PM ---------- Previous post was at 06:49 PM ----------
Motorola Firmware with CFC in the name will wipe data as part of the flashing process.
---------- Post added at 06:53 PM ---------- Previous post was at 06:52 PM ----------
Did you verify md5 of firmware file?

Yes all confirmed good, on another site they said after an ota the change took place on accessing recovery, this friend always took ota's. Maybe part of 5-5? I don't know

newbe1droidx said:
Yes all confirmed good, on another site they said after an ota the change took place on accessing recovery, this friend always took ota's. Maybe part of 5-5? I don't know
Click to expand...
Click to collapse
What step are you using to get to recovery?
Sent from my Moto E (4) using Tapatalk

Vol down and power, then vol down to recovery, then power and see the dead Andy with no command, then supposed to push down button hold and push power then let up and will be at recovery. Still waiting for apps and data to finish restoring before I try it.

newbe1droidx said:
Vol down and power, then vol down to recovery, then power and see the dead Andy with no command, then supposed to push down button hold and push power then let up and will be at recovery. Still waiting for apps and data to finish restoring before I try it.
Click to expand...
Click to collapse
sounds right, I've sometimes found the button combination at the no command screen a little tricky.
You may need to adjust how long you press the buttons, to get into recovery.
Sent from my XT1254 using Tapatalk

OK thanks very much, I guess using a win7 machine is what made it work for me. All set to use again. Thanks so much!