Related
I TAKE NO CREDIT FOR THAT. I FOUND IT OVER THE DROID 4 FORUM AND BRING IT HERE FOR THE ONES WHO MAY NEED IT.
IT IS SAID TO BE WORKING GREAT BUT DON'T HOLD ME RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE. WELL IF YOU ALREADY BRICKED IT, WHAT WHAT'S WORST CAN YOU DO TO IT???
THANKS TO SGMD1 FOR THE PROCEDURES AND TO ALL OTHERS WHO CONTRIBUTED TO THE RESURRECTION OF DROID 4. AMEN
Thumbs up [HOW TO] Restore your Motorola Droid 4 (XT894) to stock [Windows Only]
***If you notice a broken link, please let me know in this thread or send me a PM and I will fix it ASAP***
These fastboot files allow you to recover a bricked device/return to stock on your Motorola Droid 4.
Android 2.3.6 System Version 6.13.215 (VRZ_XT894_6.5.1-167_DR4-1_M1-215_1FF_01) (1.17GB)
DOWNLOAD
Android 2.3.6 System Version 6.13.219 (VRZ_XT894_6.5.1-167_DR4-1_M1-219_1FF_01) (1.18GB)
DOWNLOAD
INSTRUCTIONS:
Download one of the fastboot image files above
Download and install RSDLite 5.7
Download and install the latest Motorola USB Drivers
Connect your phone to your PC via USB
Power off your phone
Hold the volume up, volume down, and power buttons at the same time until you see the bootloader menu
Use the volume down button to navigate to "AP Fastboot" then use the volume up button to select it
Open RSD Lite, press the "..." button to the top, and select the fastboot image .zip file
Select "Decompress And Start Flashing" and wait for the process to finish (it will take around 20 minutes)
Credits: kholk @ EternityProject/XDA for the 6.13.215 file, daywalker04 @ XDA for the 6.13.219 file, Skrilax_CZ @ XDA and djb.617 @ DroidForums for the mirrors
I made that thread But actually I pretty much just copied it over from info I found here on XDA in this thread: http://forum.xda-developers.com/showthread.php?t=1622256
All the credit belongs to kholk, daywalker04, and Skrilax_CZ for releasing/hosting the files
True that but you made easier to find and broke it down Barney style for slow noob like myself. The whole developer team fulfilled my prayer but man you made my day
So, is there any way now that I can brick my phone into an unsalvageable mess short of physical damage? That's the situation I had with my OG droid with sbf files. I'm still not completely sure this the case with a locked bootloader. If it is, I'm looking so forward to tinkering with my phone again, as I have shown restraint since there was no way to unbrick my phone.
That should solve for all the bricking issues with the Droid 4
The restoring to stock just won't work for me at all... I'm about ready to give up.
First off thanks for the post.
I have a quick question. My system version is 6.93.215 instead of 6.13.215. Does anyone know why? Does it really matter?
Grizzy3 said:
My system version is 6.93.215 instead of 6.13.215. Does anyone know why? Does it really matter?
Click to expand...
Click to collapse
That's really strange. I've never seen 6.93.215 anywhere...and Googling it only brings up your post. I would imagine you shouldn't have a problem flashing 6.13.219 but I'd try and determine how you got that system version first, just to be safe.
SGMD1 said:
That's really strange. I've never seen 6.93.215 anywhere...and Googling it only brings up your post. I would imagine you shouldn't have a problem flashing 6.13.219 but I'd try and determine how you got that system version first, just to be safe.
Click to expand...
Click to collapse
Ya I tried googling it too and got nothing. I got the OTA update this morning and now it says 6.13.219 so I guess I'm good. It was just weird cuz I didn't see it anywhere.
lorddunlow said:
So, is there any way now that I can brick my phone into an unsalvageable mess short of physical damage? That's the situation I had with my OG droid with sbf files. I'm still not completely sure this the case with a locked bootloader. If it is, I'm looking so forward to tinkering with my phone again, as I have shown restraint since there was no way to unbrick my phone.
Click to expand...
Click to collapse
I think the only way to really screw it up (someone correct me if I'm wrong), is the same way you could really screw the OG Droid up, by interrupting the flash procedure during RSDLite.
With the locked bootloader, we should be even safer (I think) than with the OG Droid. Although I never tried this on the OG Droid, on the Kindle Fire you can replace the bootloader. If you hose that, pretty sure it is game over... Don't think this is possible on the D4, since it needs to be signed...
podspi said:
I think the only way to really screw it up (someone correct me if I'm wrong), is the same way you could really screw the OG Droid up, by interrupting the flash procedure during RSDLite.
With the locked bootloader, we should be even safer (I think) than with the OG Droid. Although I never tried this on the OG Droid, on the Kindle Fire you can replace the bootloader. If you hose that, pretty sure it is game over... Don't think this is possible on the D4, since it needs to be signed...
Click to expand...
Click to collapse
Just read something about some Razr owners bricking their phone trying to go back to stock using RSDLite after flashing a leaked ICS build. Not sure what the leak could have done to mess that up but just FYI.
kwyrt said:
Just read something about some Razr owners bricking their phone trying to go back to stock using RSDLite after flashing a leaked ICS build. Not sure what the leak could have done to mess that up but just FYI.
Click to expand...
Click to collapse
Ya a few people were having problems with the razr leak. I think its more because of the leak than anything else.
Coriolis3ffect said:
The restoring to stock just won't work for me at all... I'm about ready to give up.
Click to expand...
Click to collapse
It's not like the D3 you could restore back to stock without rsdlite. When I flashed mine I didn't get the msg saying "process completed".
If your phone keeps bootlooping after flashing it to stock with the 6.13.219 via rsdlite v 5.7
You can try tne following. Works like a charm for me
1-unplug the phone from the pc
2-Hold down the power button + volume down to reboot onto recovery,
Select Recovery from the list.
3-when the screen with the android and the exclamation mark comes up press both volume buttons to get onto the recovery options.
4-Wipe data and cache and then select "reboot system".
Then you should be good to go.
mrbidjey said:
I TAKE NO CREDIT FOR THAT. I FOUND IT OVER THE DROID 4 FORUM AND BRING IT HERE FOR THE ONES WHO MAY NEED IT.
IT IS SAID TO BE WORKING GREAT BUT DON'T HOLD ME RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE. WELL IF YOU ALREADY BRICKED IT, WHAT WHAT'S WORST CAN YOU DO TO IT???
THANKS TO SGMD1 FOR THE PROCEDURES AND TO ALL OTHERS WHO CONTRIBUTED TO THE RESURRECTION OF DROID 4. AMEN
Thumbs up [HOW TO] Restore your Motorola Droid 4 (XT894) to stock [Windows Only]
***If you notice a broken link, please let me know in this thread or send me a PM and I will fix it ASAP***
These fastboot files allow you to recover a bricked device/return to stock on your Motorola Droid 4.
Android 2.3.6 System Version 6.13.215 (VRZ_XT894_6.5.1-167_DR4-1_M1-215_1FF_01) (1.17GB)
DOWNLOAD (MIRRORS: 1, 2, 3, 4, 5, 6)
Android 2.3.6 System Version 6.13.219 (VRZ_XT894_6.5.1-167_DR4-1_M1-219_1FF_01) (1.18GB)
DOWNLOAD
INSTRUCTIONS:
Download one of the fastboot image files above
Download and install RSDLite 5.7
Download and install the latest Motorola USB Drivers
Connect your phone to your PC via USB
Power off your phone
Hold the volume up, volume down, and power buttons at the same time until you see the bootloader menu
Use the volume down button to navigate to "AP Fastboot" then use the volume up button to select it
Open RSD Lite, press the "..." button to the top, and select the fastboot image .zip file
Select "Decompress And Start Flashing" and wait for the process to finish (it will take around 20 minutes)
Credits: kholk @ EternityProject/XDA for the 6.13.215 file, daywalker04 @ XDA for the 6.13.219 file, Skrilax_CZ @ XDA and djb.617 @ DroidForums for the mirrors
Click to expand...
Click to collapse
Can you please fix the links.
mrbidjey said:
I TAKE NO CREDIT FOR THAT. I FOUND IT OVER THE DROID 4 FORUM AND BRING IT HERE FOR THE ONES WHO MAY NEED IT.
IT IS SAID TO BE WORKING GREAT BUT DON'T HOLD ME RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE. WELL IF YOU ALREADY BRICKED IT, WHAT WHAT'S WORST CAN YOU DO TO IT???
THANKS TO SGMD1 FOR THE PROCEDURES AND TO ALL OTHERS WHO CONTRIBUTED TO THE RESURRECTION OF DROID 4. AMEN
Thumbs up [HOW TO] Restore your Motorola Droid 4 (XT894) to stock [Windows Only]
***If you notice a broken link, please let me know in this thread or send me a PM and I will fix it ASAP***
These fastboot files allow you to recover a bricked device/return to stock on your Motorola Droid 4.
Android 2.3.6 System Version 6.13.215 (VRZ_XT894_6.5.1-167_DR4-1_M1-215_1FF_01) (1.17GB)
DOWNLOAD (MIRRORS: 1, 2, 3, 4, 5, 6)
Android 2.3.6 System Version 6.13.219 (VRZ_XT894_6.5.1-167_DR4-1_M1-219_1FF_01) (1.18GB)
DOWNLOAD
INSTRUCTIONS:
Download one of the fastboot image files above
Download and install RSDLite 5.7
Download and install the latest Motorola USB Drivers
Connect your phone to your PC via USB
Power off your phone
Hold the volume up, volume down, and power buttons at the same time until you see the bootloader menu
Use the volume down button to navigate to "AP Fastboot" then use the volume up button to select it
Open RSD Lite, press the "..." button to the top, and select the fastboot image .zip file
Select "Decompress And Start Flashing" and wait for the process to finish (it will take around 20 minutes)
Credits: kholk @ EternityProject/XDA for the 6.13.215 file, daywalker04 @ XDA for the 6.13.219 file, Skrilax_CZ @ XDA and djb.617 @ DroidForums for the mirrors
Click to expand...
Click to collapse
where's the donwload link?
magikstar said:
where's the donwload link?
Click to expand...
Click to collapse
I will try to fix them for you when I get home. It's been a while since I wrote that
Firmware:http://sbf.droid-developers.org/phone.php?device=11
Sent from my Amazon OtterX using Tapatalk
---------- Post added at 08:21 PM ---------- Previous post was at 08:17 PM ----------
Rsd lite links http://forum.xda-developers.com/showthread.php?t=1348587
Sent from my Amazon OtterX using Tapatalk
magikstar said:
where's the donwload link?
Click to expand...
Click to collapse
You should be good now
i have found another way to recover
thank you anyway
magikstar said:
i have found another way to recover
thank you anyway
Click to expand...
Click to collapse
Good to know buddy
Hey guys, i really need some help here, i would really like to just hard reset my phone back to stock, and then i can start from scratch on rooting and what not. My problem is , the phone just wont reset ahha.
like i go into TWRP, and using this post " http://www.droidforums.net/forum/droid-bionic-hacks/234845-factory-bionic-stock-rom-ics-4-0-4-a.html " try and restore my device. Ive so far encountered probably every problem possible...following that post i DL the file and go to past it onto the device storage but i couldn't find the 3. Copy or Move Folder to your Backups....(Ex). Sdcard-Ext/TWRP/Backup.... so i just paste it into the TWRP file directory.from there i go to boot the device, it automatically boots in to adb usb mode stating that ( flash failed) i then have to hold the volume buttons and power to bring it back to the main recovery menu to boot normally!? thats only one problem, next i have Safestrap installed, it shows the start up screen i can continue or boot into recovery. Now in recovery following the instruction in the link provided i go and i 5. Select Stock ROM slot (Activate) and go select 6. Select Restore but theres noting in it, so i just go to install and find my file that i put there. i then do step 7. Select Factory Bionic Folder and 8. Flash it ( Swipe ). TWRP says it was complete but it only shows it going into the flashing process of installing update... so i reboot the phone and same thing, i get automatically pushed to the ABD USB screen saying flash failed. ... last problem , i go to boot past and theres no OS installed ... just a black screen ... im totally lost i dont know what to do hahah , any help here people??
anyone have any ideas on how to just restore this baby straight to stock ICS? thanks
P.S sorry for the bad quality photos, that what u get for taking pics with a razr haha
Dose anyone have any ideas at all, please??
I'd suggest hooking up your Bionic to a computer and FXZ through RSDlite.
Else if phone is bricked use fastboot and use the FXZ version of the stock image.
If you need the official FXZ for 246 ICS, one place to get it from is here:
http://sbf.droid-developers.org/cdma_targa/list.php
Sent from my DROID BIONIC using Tapatalk 2
---------- Post added at 01:17 PM ---------- Previous post was at 01:13 PM ----------
Need further help?
Google this: fxz fastboot bionic
There should be a YouTube video called 'unbrick factory reset droid bionic with fast boot and fxz', near the top of the search results. Watch it
Sent from my DROID BIONIC using Tapatalk 2
collije said:
I'd suggest hooking up your Bionic to a computer and FXZ through RSDlite.
Else if phone is bricked use fastboot and use the FXZ version of the stock image.
If you need the official FXZ for 246 ICS, one place to get it from is here:
http://sbf.droid-developers.org/cdma_targa/list.php
Sent from my DROID BIONIC using Tapatalk 2
---------- Post added at 01:17 PM ---------- Previous post was at 01:13 PM ----------
Need further help?
Google this: fxz fastboot bionic
There should be a YouTube video called 'unbrick factory reset droid bionic with fast boot and fxz', near the top of the search results. Watch it
Sent from my DROID BIONIC using Tapatalk 2
Click to expand...
Click to collapse
errr, bump? Do you still need help?
Hello Bueller?
This is the first issue with an android phone I've had in a while where I have absolutely no idea what I should do next.
The music player was beginning to stutter a LOT on my install of CM11, and I was having issues where if I selected a song to play on my music player, the volume would suddenly spike to THE HIGHEST LEVEL, and I had to adjust the volume down to get it to reset back to normal. So I figured I'd wipe everything clean and re-install CM11. I didn't just wipe /data and /cache, but I also wiped /system because I believe the issues mentioned above came from a Sony Walkman Mod ZIP I flashed. So after formatting all of the partitions, I went to the "Install" button of TWRP (by the way, I am using TWRP 2.8.1.0) to re-install the CM11 ROM. When I tried to open the CM11 ZIP, TWRP gave me an error saying it couldn't open the file to flash it. I tried using adb sideload as well but adb sideload gave me a similar error.
So I figured it was just an issue with TWRP and that I'd have to boot into fastboot and flash a different recovery image that I know works, like shinobisoft's CWM. I power off the phone, hold the volume up button while plugging the phone back in to the USB port and I am greeted with the Download Mode screen as usual. Here's where things start to get unusual: instead of the phone taking about 1-2 seconds and presenting me with a "Fastboot Ready" line of text or something similar to that, the Download Mode screen hangs on [270] udc_start().
What should I do from here? I tried flashing back to the stock KDZ, but Download Mode needs to be working to do that. Also, I can still get into TWRP recovery just fine, and TWRP can still see all of my partitions.
jasonmerc said:
This is the first issue with an android phone I've had in a while where I have absolutely no idea what I should do next.
The music player was beginning to stutter a LOT on my install of CM11, and I was having issues where if I selected a song to play on my music player, the volume would suddenly spike to THE HIGHEST LEVEL, and I had to adjust the volume down to get it to reset back to normal. So I figured I'd wipe everything clean and re-install CM11. I didn't just wipe /data and /cache, but I also wiped /system because I believe the issues mentioned above came from a Sony Walkman Mod ZIP I flashed. So after formatting all of the partitions, I went to the "Install" button of TWRP (by the way, I am using TWRP 2.8.1.0) to re-install the CM11 ROM. When I tried to open the CM11 ZIP, TWRP gave me an error saying it couldn't open the file to flash it. I tried using adb sideload as well but adb sideload gave me a similar error.
So I figured it was just an issue with TWRP and that I'd have to boot into fastboot and flash a different recovery image that I know works, like shinobisoft's CWM. I power off the phone, hold the volume up button while plugging the phone back in to the USB port and I am greeted with the Download Mode screen as usual. Here's where things start to get unusual: instead of the phone taking about 1-2 seconds and presenting me with a "Fastboot Ready" line of text or something similar to that, the Download Mode screen hangs on [270] udc_start().
What should I do from here? I tried flashing back to the stock KDZ, but Download Mode needs to be working to do that. Also, I can still get into TWRP recovery just fine, and TWRP can still see all of my partitions.
Click to expand...
Click to collapse
Check your PM's
shinobisoft said:
Check your PM's
Click to expand...
Click to collapse
I tried your suggestion of holding the power button but that didn't work. And this is the ONE TIME where I did not make any backups. I couldn't because TWRP couldn't read my /data partition since my phone was encrypted, but before this whole thing happened I formatted /data as EXT4 (which I did before without issue), so I don't think it should be encrypted anymore.
jasonmerc said:
I tried your suggestion of holding the power button but that didn't work. And this is the ONE TIME where I did not make any backups. I couldn't because TWRP couldn't read my /data partition since my phone was encrypted, but before this whole thing happened I formatted /data as EXT4 (which I did before without issue), so I don't think it should be encrypted anymore.
Click to expand...
Click to collapse
What I said about the power button was only to help you get out of fastboot mode so you could try to get to fastboot mode again. LOL.
BTW, I always have a least 2 backups on my sdcard.
You're in a bit of a pickle... I need to think about this for a few...
**BUMP***
I went back to TWRP and tried flashing a PurePerformances .zip and it was able to flash just fine. But even with a fresh download of the CM11 ZIP It still doesn't work. Maybe I'll try flashing a different ROM.
jasonmerc said:
**BUMP***
I went back to TWRP and tried flashing a PurePerformances .zip and it was able to flash just fine. But even with a fresh download of the CM11 ZIP It still doesn't work. Maybe I'll try flashing a different ROM.
Click to expand...
Click to collapse
That's really strange. As I stated in my ROM thread, I haven't changed anything with the last build...
Whoa, just noticed the 12/2 build! I was trying to flash the 10/22 this whole time. I'll try flashing 12/2.
I tried the new build with ADB Side load. It was able to load the zip!
But the device could not be found...
Sent from my MB520 using XDA Free mobile app
jasonmerc said:
I tried the new build with ADB Side load. It was able to load the zip!
But the device could not be found...
Sent from my MB520 using XDA Free mobile app
Click to expand...
Click to collapse
So ADB debugging isn't enabled in TWRP 2.8.1.0? Have you tried another recovery? And why sideload? Why not straight flash?
shinobisoft said:
So ADB debugging isn't enabled in TWRP 2.8.1.0? Have you tried another recovery? And why sideload? Why not straight flash?
Click to expand...
Click to collapse
I can't load another recovery on here without going into fastboot. And I am currently in the process of attempting a straight flash. I am going to save the rom on an SD card on another phone then inset it in the L90.
Sent from my MB520 using XDA Free mobile app
...And the moral of this story is: change your USB cables
I'm feeling a little stupid right now...
Sent from my MB520 using XDA Free mobile app
jasonmerc said:
...And the moral of this story is: change your USB cables
I'm feeling a little stupid right now...
Sent from my MB520 using XDA Free mobile app
Click to expand...
Click to collapse
LMFAO. Lesson learned I hope. LOL
shinobisoft said:
LMFAO. Lesson learned I hope. LOL
Click to expand...
Click to collapse
I've never had this happen to me before. What's weird is the cable was able to transmit power to the device, but not data.
Sent from my LG-D415 using XDA Free mobile app
jasonmerc said:
I've never had this happen to me before. What's weird is the cable was able to transmit power to the device, but not data.
Sent from my LG-D415 using XDA Free mobile app
Click to expand...
Click to collapse
Ya got me. I use the same cable for PC communication. My main charger is a hardwire charger so I basically just leave my data cable attached to my PC. In fact, it's the same cable I started modding my P506 with about 2 years ago .
jasonmerc said:
...And the moral of this story is: change your USB cables
I'm feeling a little stupid right now...
Sent from my MB520 using XDA Free mobile app
Click to expand...
Click to collapse
Speaking of feeling stupid, is that the fastboot screen? Like, if I have that screen and it says "hold up till download mode" does that mean I can do fastboot commands like that????? Maybe I DID enable fastboot mode????
whodisname said:
Speaking of feeling stupid, is that the fastboot screen? Like, if I have that screen and it says "hold up till download mode" does that mean I can do fastboot commands like that????? Maybe I DID enable fastboot mode????
Click to expand...
Click to collapse
Yes, that is the fastboot screen in the picture and it passed the UDC START. What you have to do is power off the phone, hold volume up while inserting USB cable to phone, and KEEP HOLDING VOLUME UP until you see something like "fastboot: processing commands". Then you will be in fastboot.
Sent from my LG-D415 using XDA Free mobile app
How long you got to hold it? I been holding it for about 3 min and counting'
---------- Post added at 11:42 PM ---------- Previous post was at 11:27 PM ----------
http://forum.xda-developers.com/showthread.php?t=2559363
---------- Post added at 11:42 PM ---------- Previous post was at 11:42 PM ----------
For your problem
whodisname said:
How long you got to hold it? I been holding it for about 3 min and counting'
---------- Post added at 11:42 PM ---------- Previous post was at 11:27 PM ----------
http://forum.xda-developers.com/showthread.php?t=2559363
---------- Post added at 11:42 PM ---------- Previous post was at 11:42 PM ----------
For your problem
Click to expand...
Click to collapse
Its only for a few seconds.
Sent from my LG-D415 using Tapatalk
I don't think I got it. It goes into the screen but if I hold down the button it stays the same. I unplugged the coed and plugged it back in (saw something about that here but I can't find it again) fastball devices comes back with nothing. Fastboot OEM unlock gets "waiting for device" as does fastboot reboot and fastboot flash recovery recovery.IMG (I have twrp in my fastboot folder called recovery.IMG) does download mode look like all the rest of the LG phones I have seen with the S/W UPGRADE IN PROGRESS DO NOT TURN OFF TARGET. Just asking because these things are subject to change!
whodisname said:
I don't think I got it. It goes into the screen but if I hold down the button it stays the same. I unplugged the coed and plugged it back in (saw something about that here but I can't find it again) fastball devices comes back with nothing. Fastboot OEM unlock gets "waiting for device" as does fastboot reboot and fastboot flash recovery recovery.IMG (I have twrp in my fastboot folder called recovery.IMG) does download mode look like all the rest of the LG phones I have seen with the S/W UPGRADE IN PROGRESS DO NOT TURN OFF TARGET. Just asking because these things are subject to change!
Click to expand...
Click to collapse
Download mode and fastboot mode are the same. S/W Upgrade mode is totally different. S/W Upgrade mode is what you should have if you DIDN'T zero out your laf partition. If you did zero out your laf partition, then you should have access to fastboot/download mode.
If the fastboot executable isn't recognizing your device, then you must be in S/W Upgrade mode, or fastboot mode on the device had become corrupted somehow.
I remember reading in the Android Original Development section that you used the script to increase your internal data storage. Does that script mess with the laf partition? If so, there's your issue.
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!
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!