Database Develop

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] Kindle HD, stuck on Kindle Fire log

Hi all,
Kindle fire HD ( rooted) got OTA update and after the update its stuck on the Kindlefire logo screen. Tired resetting it by pressing 20sec / also tried 30 sec but no joy. Also tried pressing the volume Up and power but its stuck on the kindlefire log.
Tried to run recovery (KFFA) but my laptop does not detect kindle fire at all. I guess factory cable is the last option but I dont have it and need to order one . But I was wondering if Amazon could replace it under warranty ?
Cheers

ipsearch said:
Hi all,
Kindle fire HD ( rooted) got OTA update and after the update its stuck on the Kindlefire logo screen. Tired resetting it by pressing 20sec / also tried 30 sec but no joy. Also tried pressing the volume Up and power but its stuck on the kindlefire log.
Tried to run recovery (KFFA) but my laptop does not detect kindle fire at all. I guess factory cable is the last option but I dont have it and need to order one . But I was wondering if Amazon could replace it under warranty ?
Cheers
Click to expand...
Click to collapse
Of course your computer won't detect it, ADB requires both devices to be fully-booted and can communicate. Use your regular cable to boot into fastboot and restore. Read my thread in my signature, #6 & #7.

seokhun said:
Of course your computer won't detect it, ADB requires both devices to be fully-booted and can communicate. Use your regular cable to boot into fastboot and restore. Read my thread in my signature, #6 & #7.
Click to expand...
Click to collapse
Thanks for the reply, I will try to follow your post #6 & #7.
I am still confused, I had only rooted Kindle and got google play installed and it was working fine. It seems that there was OTA firmware upgrade and after that upgrade when the device rebooted its stuck on the kindle fire screen.
Appreciate your reply.
Cheers

I dont know what is going on ? Android SDK is installed and even ADB is working but somehow my laptop does not detect the Kindle. It is just stuck on waiting for device.... ?
Getting error on step 2 Qemutool.bat ?
Step 2 - Exploiting...
/system/bin/sh: cannot create /data/local.prop: Permission denied
Rebooting...
Once your devices has finished restarting,
Press any key to continue . . .
Pls help.

ipsearch said:
I dont know what is going on ? Android SDK is installed and even ADB is working but somehow my laptop does not detect the Kindle. It is just stuck on waiting for device.... ?
Getting error on step 2 Qemutool.bat ?
Step 2 - Exploiting...
/system/bin/sh: cannot create /data/local.prop: Permission denied
Rebooting...
Once your devices has finished restarting,
Press any key to continue . . .
Pls help.
Click to expand...
Click to collapse
Try using root with restore by bin4ry.
Sent from my air conditioner unit running CyanogenMod

dugoy13 said:
Try using root with restore by bin4ry.
Sent from my air conditioner unit running CyanogenMod
Click to expand...
Click to collapse
Tried Binary too but does not work.

Possibly Solved
ipsearch said:
Tried Binary too but does not work.
Click to expand...
Click to collapse
Solutions
1. What root tool did you use? A: if it was bin4ry type in notepad 0x1949 and save it to .android under users/Your User/.android
Like for me it would be users/chris/.android and you would save it to .android dir. if you dont have an .android dir. make one. Then see if your device is reconized as android composite adb device or at least kindle. Also try installing drivers for the kindle and uninstall the drivers and reinstalling them
2. I had a similar problem i rooted my kfhd and it became so slow it wouldnt turn on eventully after 30min. it turned on but was so slow when i sided to unlock it took five minutes. I also i tried rerooting without unroot. it worked so i used binary's root like i was unrooted and my kindle was back again. it turned out when i rooted i only had 50% battery and you NEED to have at least 90%. this also fixed any audio issues.
3. your original kf cord that came when shipped maybe shot and you may need a new one if it wont charge like someone else said "android devices need at least 20% battery to turn on". i dont find this to be true i need at least 5% but find a new cord and charge it seee if it works then.
4. if it turns on the the kindle fire logo flashes quicker then you can boot into recovery. the recovery screen should be a red warning sign saying reboot or restore click restore.
5. with a home made factory cord try booting into recovery mode and follow solution (4).
6. what root apps did you have on the device fire flash? A: fire flash will not work with the new 7.4.1 ota update
Let me know from there if you get your kindle working if no i can supply more solutions based on your answers and the reactions from my solutions.
I can also supply drivers and root tools

CVanB said:
Solutions
1. What root tool did you use? A: if it was bin4ry type in notepad 0x1949 and save it to .android under users/Your User/.android
Like for me it would be users/chris/.android and you would save it to .android dir. if you dont have an .android dir. make one. Then see if your device is reconized as android composite adb device or at least kindle. Also try installing drivers for the kindle and uninstall the drivers and reinstalling them
2. I had a similar problem i rooted my kfhd and it became so slow it wouldnt turn on eventully after 30min. it turned on but was so slow when i sided to unlock it took five minutes. I also i tried rerooting without unroot. it worked so i used binary's root like i was unrooted and my kindle was back again. it turned out when i rooted i only had 50% battery and you NEED to have at least 90%. this also fixed any audio issues.
3. your original kf cord that came when shipped maybe shot and you may need a new one if it wont charge like someone else said "android devices need at least 20% battery to turn on". i dont find this to be true i need at least 5% but find a new cord and charge it seee if it works then.
4. if it turns on the the kindle fire logo flashes quicker then you can boot into recovery. the recovery screen should be a red warning sign saying reboot or restore click restore.
5. with a home made factory cord try booting into recovery mode and follow solution (4).
6. what root apps did you have on the device fire flash? A: fire flash will not work with the new 7.4.1 ota update
Let me know from there if you get your kindle working if no i can supply more solutions based on your answers and the reactions from my solutions.
I can also supply drivers and root tools
Click to expand...
Click to collapse
Dude, no offense meant really, but posting this big long thing everywhere isn't really helping anybody.....
If your kindle is stuck, you'll need a factory cable. You need to be able to get to fast boot so you can use the Kindle SRT tool, that allows you to flash a clean ROM to your device through fast boot.

Sorry...
DroidIt! said:
Dude, no offense meant really, but posting this big long thing everywhere isn't really helping anybody.....
If your kindle is stuck, you'll need a factory cable. You need to be able to get to fast boot so you can use the Kindle SRT tool, that allows you to flash a clean ROM to your device through fast boot.
Click to expand...
Click to collapse
They had similar problems giving similar answers. I was just trying to solve the problem.

CVanB said:
They had similar problems giving similar answers. I was just trying to solve the problem.
Click to expand...
Click to collapse
Sorry, didn't mean anything anything bad by that, I just found it's always easier to try the simple things first one by one and not overload with info because the problem usually is just something simple. I wasn't saying that you shouldn't try to help, that's what we should do as a community, just that we should take it one step at a time with simple items first. Again didn't mean anything bad, hope you weren't offended
from my Viped out one x

DroidIt! said:
Sorry, didn't mean anything anything bad by that, I just found it's always easier to try the simple things first one by one and not overload with info because the problem usually is just something simple. I wasn't saying that you shouldn't try to help, that's what we should do as a community, just that we should take it one step at a time with simple items first. Again didn't mean anything bad, hope you weren't offended
from my Viped out one x
Click to expand...
Click to collapse
It's okay, so the problem is solved? Also, ipsearch make sure you look on the forms for your problem because, other people may have the same problem and it might already be solved no offense.

CVanB said:
It's okay, so the problem is solved? Also, ipsearch make sure you look on the forms for your problem because, other people may have the same problem and it might already be solved no offense.
Click to expand...
Click to collapse
Manage to boot Kindle HD, had to use factory cable, then used SRT tool and use option 4 and that manage to fix it. THANKS EVERYONE for your help.

HELP
Hi there guys, I can see that some of you already solved the problem. In my case, I have an UNrooted kindle fire HD. It suddenly shut down when I was playing. ANd then now, it wont open anymore. Been trying to read some forums and stuff but it still wont get fixed. It opens, but only up to the KINDLE FIRE logo only. I dont really know that happened and I dont have a freakin' clue on how to fix it. Can somebody help me please? I miss my kindle so much.:crying:

letsyrkdelrosario said:
Hi there guys, I can see that some of you already solved the problem. In my case, I have an UNrooted kindle fire HD. It suddenly shut down when I was playing. ANd then now, it wont open anymore. Been trying to read some forums and stuff but it still wont get fixed. It opens, but only up to the KINDLE FIRE logo only. I dont really know that happened and I dont have a freakin' clue on how to fix it. Can somebody help me please? I miss my kindle so much.:crying:
Click to expand...
Click to collapse
I am not an expert but this is what helped me.
(1) Try charging the knidle
(2) also try getting Factory cable and use the recovery tool.
Cheers

ipsearch said:
I am not an expert but this is what helped me.
(1) Try charging the knidle
(2) also try getting Factory cable and use the recovery tool.
Cheers
Click to expand...
Click to collapse
HI, yes i've tried charging the kindle using my laptop. Well, the battery is drained. And it charges for quite sometime and then when it gets enough charge, it opens by itself. I cannot hold the power button for it will shut down and wont push thru charging. HEnce when I leave it charging, like I said it would open on its own then eventually shut down on its own again. At this part, I dont know if it still charges. Tried leaving it overnight too but still wont open. As for the factory cable, I dnt know where I could get it. I am from the Philippines. And how do I get that recovery tool? Thanks

[Q] Deleted fire OS

I attempted to install android 4.4 on my Kindle Fire HD 7 using C11 but when I tried to reboot the system after flashing and etc I was asked if I wanted my device to be rooted as it wasn't already, (Not knowing what to do I just hit yes.) in the video I watched the guy wasn't asked that. After I tried to reboot I've seen been stuck at the blue recovery screen. Please help! (Sorry in advance I'm a noob when it comes to this stuff.)

Hooyen said:
I attempted to install android 4.4 on my Kindle Fire HD 7 using C11 but when I tried to reboot the system after flashing and etc I was asked if I wanted my device to be rooted as it wasn't already, (Not knowing what to do I just hit yes.) in the video I watched the guy wasn't asked that. After I tried to reboot I've seen been stuck at the blue recovery screen. Please help! (Sorry in advance I'm a noob when it comes to this stuff.)
Click to expand...
Click to collapse
Since you can still access the recovery screen, try wiping and re-installing CM.
>>>Sent from my homebuilt TARDIS running Android 4.4... or maybe it's a Kindle Fire HD running Cyanogenmod 11<<<

Ph0enix_216 said:
Since you can still access the recovery screen, try wiping and re-installing CM.
>>>Sent from my homebuilt TARDIS running Android 4.4... or maybe it's a Kindle Fire HD running Cyanogenmod 11<<<
Click to expand...
Click to collapse
I actually don't have access to the menu, when I said screen I meant to say boot logo I just didn't know the term for it, sorry for not being specific enough. But yeah when I boot I get the normal red kindle boot logo then it switches to the blue one and stays that way.

Hooyen said:
I actually don't have access to the menu, when I said screen I meant to say boot logo I just didn't know the term for it, sorry for not being specific enough. But yeah when I boot I get the normal red kindle boot logo then it switches to the blue one and stays that way.
Click to expand...
Click to collapse
Right so when you power the Kindle on and you see the yellow kindle boot animation, hold the volume up rocker. Keep holding it and the blue TWRP boot animation will show. Continue holding the volume rocker up for three seconds and release. You should enter TWRP. Now flash whatever ROM is on your internal memory. Otherwise just adb sideboard a ROM while in TWRP.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app

LinearEquation said:
Right so when you power the Kindle on and you see the yellow kindle boot animation, hold the volume up rocker. Keep holding it and the blue TWRP boot animation will show. Continue holding the volume rocker up for three seconds and release. You should enter TWRP. Now flash whatever ROM is on your internal memory. Otherwise just adb sideboard a ROM while in TWRP.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That worked for getting back into the menu but unfortunately I still couldn't boot up cm11 it asked me again if I wanted supersu installed and I got the same thing, I was able to revert back to the normal os by factory resetting and restoring the backup and I'm not able to connect the kindle to my pc anymore to transfer data. : ( Oh and when I boot up I get the normal boot logo then the blue then it actually starts to boot up, it's really weird.

UPDATE
So I decided to do a full wipe while in the recovery menu because I kept getting messages about installing supersu and stuff while in the normal os, I ended up with no os and since I can't mount it onto my pc I think I bricked it to the point of no return. : /

Hooyen said:
So I decided to do a full wipe while in the recovery menu because I kept getting messages about installing supersu and stuff while in the normal os, I ended up with no os and since I can't mount it onto my pc I think I bricked it to the point of no return. : /
Click to expand...
Click to collapse
no u didnt lol. try plugging it into ur comp, in twrp recovery. I remember u need to have adb working, if not, uninstall it and install it again. it should show the kindle. then download rom of choice on computer in a folder and use adb push to move it to ur kindle. I cant find the thred someone made for fixing this but i beleive its like "adb push romexample.zip /sdcard/" without quotes, in command prompt. u also need to do that for the gapps.

miztah1999z said:
no u didnt lol. try plugging it into ur comp, in twrp recovery. I remember u need to have adb working, if not, uninstall it and install it again. it should show the kindle. then download rom of choice on computer in a folder and use adb push to move it to ur kindle. I cant find the thred someone made for fixing this but i beleive its like "adb push romexample.zip /sdcard/" without quotes, in command prompt. u also need to do that for the gapps.
Click to expand...
Click to collapse
My kindle isn't showing up when I type in adb devices so when I try to push it just tells me there are no devices connected. oh boyy

**second to last update**
Alright so thanks to miztah1999z, I now have a working kindle on 4.4, it's so beautiful. ;n; I don't know how to express my gratitude other than thanking your post. Oh and ONE LAST PROBLEM, my computer is recognizing the tablet but I can't transfer any files as it's not showing up in my computer, any last tips? (Oh also thanks to anyone else who posted even if you couldn't help much I appreciate it and I'm glad my first thread went well. <3)

Hooyen said:
Alright so thanks to miztah1999z, I now have a working kindle on 4.4, it's so beautiful. ;n; I don't know how to express my gratitude other than thanking your post. Oh and ONE LAST PROBLEM, my computer is recognizing the tablet but I can't transfer any files as it's not showing up in my computer, any last tips? (Oh also thanks to anyone else who posted even if you couldn't help much I appreciate it and I'm glad my first thread went well. <3)
Click to expand...
Click to collapse
Go into settings and select storage. Now tap the three dots in the upper right hand corner and tab USB CONNECTION. Now select which one you want.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app

LinearEquation said:
Go into settings and select storage. Now tap the three dots in the upper right hand corner and tab USB CONNECTION. Now select which one you want.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Those options pop up on the status screen when I plug my usb in, I've tried each and none work, both camera and media device.

Hooyen said:
Those options pop up on the status screen when I plug my usb in, I've tried each and none work, both camera and media device.
Click to expand...
Click to collapse
It could be a driver issue. Are you running Windows 8/8.1?
Sent from my iPod touch using Tapatalk, somewhere in the time vortex

Ph0enix_216 said:
It could be a driver issue. Are you running Windows 8/8.1?
Sent from my iPod touch using Tapatalk, somewhere in the time vortex
Click to expand...
Click to collapse
Nope win 7 also whenever I plug it in it shows up in my devices as MTP and has a driver issue, tried uninstalling and re installing but windows cant find drivers for it.

*conclusion*
I had my tablet plugged in for a few minutes and after a while it was recognized as a nexus 7 and automatically installed drivers, I'm good to go now. Thanks again to everyone that posted. : D

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!