Develop Bugs

[Q] Unfortunately, Google Keyboard Has Stopped

A few months ago I decided to try and root my Nexus 7 (2013) tablet. At this time I simply cannot remember what process I used but all I know is that everytime I try to power it on the system start screen comes on where it asks what country you're in and so forth. But I also get the following Pop Up Error message "Unfortunately, Google Keyboard Has Stopped" and an "OK" button. When I click on OK the error message simply pops back up in a never ending loop. It stops at the SELECT WI-FI screen and won't let me input the access code because of the Pop Up Error message.
Does anyone have any idea how to completely wipe the system and bring it back to stock or just to the point I can do "anything"?
Thank you in advance for your assistance!

Boot into fastboot by holding volume down and power while the tablet is off. Scroll through the options with volume keys. When you see the option recovery mode at the top of the screen, press power. This will boot you into recovery. From there, there will be several option. One of which should be a hard reset. navigate using the volume keys. You should be OK from here.
sent from my nex7

Thank you for your reply but unfortunately this doesn't work. It puts me right back to where I always end up and still get the Error Message stated above.

I've been working on this for a few hours now and nothing! It basically says I don't have a Keyboard installed after I do anything. If I Factory reset it I get the same Error Message about no keyboard.
Any ideas? PLEASE HELP!

That is really weird. Do you have a custom recovery installed? Custom ROM? Does the computer find it? because flashing a stock image may be the way to go from here.
sent from my nex7

mugzylol said:
That is really weird. Do you have a custom recovery installed? Custom ROM? Does the computer find it? because flashing a stock image may be the way to go from here.
sent from my nex7
Click to expand...
Click to collapse
Thank you for your reply. I greatly appreciate you taking the time. I am at wits end at this point and simply need it to run again. Can you talk me through loading whatever to get it back to new? I'll take anything at this point. Everything is backed up so I have nothing to lose. How can I load the original image? (non rooted)
Thank you!

I AM NOT RESPONSIBLE FOR ANYTHING IF IT GOES WRONG (it should not go wrong though)
First you will need an image. Search for a stock 2013 nexus 7 image. Than you will need to download google USB drivers :
http://developer.android.com/sdk/win-usb.html
Than install them by opening the device manager program which is installed by default on any windows computer. Plug your tablet in, right click it in device manager and press update driver software and browse for the driver you downloaded. Than install it.
Now that that is done download the android SDK.
http://developer.android.com/sdk/index.html
Extract just the SDK folder (the other parts are not needed) and enter it once extracted. Click on the platform tools folder, hold shift and right click. Click on
"open new command window here"
Now put your tablet into fastboot mode. Type
"fastboot devices" in the command window. If there is something that shows up this means that your tablet is recognized.
Now type "fastboot OEM unlock" in the command window. Select yes on your tablet with volume keys and click power on your tablet. Than it will run through the unlock bootloader practice. This will erase all content on the tablet. It may take a bit.
Once that is done, put your image in the tablets internal storage.
Now download the latest twrp for your device.
http://teamw.in/project/twrp2/193
Press download latest .img
Now, put your twrp image in the platform tools folder and name it something easy to type. Now, in the command window type:
Fastboot boot (name of your twrp here).IMG
This will boot into twrp. It will not install it.
Now, in twrp press install and browse for your image (must be a .zip file) and flash it. If all goes well than reboot your system. If there is a problem try another image.
You do not need to unlock bootloader or install drivers again. Just boot back in to twrp and flash another image (if it goes wrong)

Stuck
mugzylol said:
I AM NOT RESPONSIBLE FOR ANYTHING IF IT GOES WRONG (it should not go wrong though)
First you will need an image. Search for a stock 2013 nexus 7 image. Than you will need to download google USB drivers :
http://developer.android.com/sdk/win-usb.html
Than install them by opening the device manager program which is installed by default on any windows computer. Plug your tablet in, right click it in device manager and press update driver software and browse for the driver you downloaded. Than install it.
Now that that is done download the android SDK.
http://developer.android.com/sdk/index.html
Extract just the SDK folder (the other parts are not needed) and enter it once extracted. Click on the platform tools folder, hold shift and right click. Click on
"open new command window here"
Now put your tablet into fastboot mode. Type
"fastboot devices" in the command window. If there is something that shows up this means that your tablet is recognized.
Now type "fastboot OEM unlock" in the command window. Select yes on your tablet with volume keys and click power on your tablet. Than it will run through the unlock bootloader practice. This will erase all content on the tablet. It may take a bit.
Once that is done, put your image in the tablets internal storage.
Now download the latest twrp for your device.
http://teamw.in/project/twrp2/193
Press download latest .img
Now, put your twrp image in the platform tools folder and name it something easy to type. Now, in the command window type:
Fastboot boot (name of your twrp here).IMG
This will boot into twrp. It will not install it.
Now, in twrp press install and browse for your image (must be a .zip file) and flash it. If all goes well than reboot your system. If there is a problem try another image.
You do not need to unlock bootloader or install drivers again. Just boot back in to twrp and flash another image (if it goes wrong)
Click to expand...
Click to collapse
OK, a couple of things;
1. I'm using a MacBook Pro. Does this make any difference? (It says I don't have to download any drivers using a Mac but other than that is there any differences?)
2. I'm stuck at ..... Extract just the SDK folder (the other parts are not needed) and enter it once extracted. Click on the platform tools folder, hold shift and right click. Click on "open new command window here". Now put your tablet into fastboot mode. Type "fastboot devices" in the command window. If there is something that shows up this means that your tablet is recognized.
Everything I do doesn't work. When I hold down Shift and Right-Click on the Platform Tools Folder I do not see "open new command window here". Is this the "platform-tools folder under the SDK folder?

Do you have any windows computers because this will not work without one
sent from my nex7
---------- Post added at 08:27 AM ---------- Previous post was at 08:25 AM ----------
This is because Mac computers do not execute batch scripts and the fastboot commands are made to execute through a command prompt rather than a Linux terminal
sent from my nex7

I honestly made this way too complicated. Just run through setup without using the keyboard. Find an unprotected network (like McDonald's) that works and find a way to get your hands on an apk of any keyboard and install it. I'm not quite sure how you can get a download link to a keyboard with no account (yet) and no keyboard but there must be a way. Its a simple issue that causes so many problems. So in a nutshell, if you can find a way to install an apk of any keyboard, your good
sent from my nex7

Help with fastboot!

Disregard, issue resolved.
I followed the procedure listed below from the 'Help how root new update 8.5.1' thread page 10 from andraw40 (which worked fine btw) but when I got to step 7, Fastboot doesn't seem to be doing what it is supposed to do which is reboot my device into Fastboot. I shut my tablet down, issue the command and then plugin my device but all it does is just boot up into the OS. What am I doing wrong? The SDK is installed and ADB appears to be working. With the device plugged into my PC, I can issue the command 'adb devices' and it shows a device plugged in. Any help would be greatly appreciated!
andraw40 said:
Guys, first of all THANK YOU for posting and helping other people.
For the last several days I have tried as hell to make my Kindle Fire HD to work like an usual android tablet. It was hell! with blocking the tablet, bricking it, reinstall it, coming back to Amazon version, and all of that for many times. Why? Because of too many version of procedures, because of missing important info from different procedures, because of me doing things wrong, and of course, because of me not reading carefully the procedures. Whatever... Finally I get it. And because it is normal to give back, here I am trying to make easy the path for a next "me".
(This procedure is for Windows Vista or above. On Windows XP there will be a lot of problems with ADB.)
So, what I had: Kindle fire HD, 8.9", version 8.5.1
What I have now: Kindle Fire HD, 8.9" (same ), runing CyanogenMod 11 and all the Google Services
How did I get there:
1. install from Amazon the ES File Explorer
2. make sure you enable ADB in Security, on Kindle
3. connect Kindle on computer and make sure you have installed ADB drivers. Check this in Device Manager. If you have the yellow warning, with the tablet connected, install "Kindle_Fire_HD_ADB_Drivers"
4. download, copy on Kindle (in Downloads) and then install "www apks.org-com zhiqupk root apk" to root the tablet. You need to root it in order to give permission to write in System folder. The aplication is the one mentioned by esema1o in the begining (keymasteroot) - Thank you esema1o! It is in Malaysian and you can use Google translate on computer if you are curious about the labels. It will not help you further but it will satisfy your need to know. So: press Mulai Root - it will do something, then will get a message. Press Root, not Batal. Another "doing something" then a new message. Choose Batal. (search on youtoube for "How to Root an Android Device with Key Root Master"). Done! You have rooted the Kindle. Reboot.
5. Open ES File Explorer and in Tools put all the switches on. Actually you will need only the Root Explorer. If you have problems keeping on the Root explorer reboot, open again ES File Explorer, try again. On the same tablet I had experienced different result after restoring the tablet to original Amazon version. Some time, I let the tablet open, come back after 15-30 minutes and try again to activate Root explorer. Surprise! it worked! Other times worked from first try or at seccond try. It is about your luck! Now, after is staying on, press on Root Explorer. A window will pop-up. Choose there to allow w/r on System folder.
6. Download "KindleFireHD89Root.zip" (you can fiind it by search on this forum by name. I'm not yet allawed to post links so remove the space before here: downloadandroidrom com/file/KindleFire/8.9root/KindleFireHD89Root.zip). Extract. Navigate into "stuff" folder. Shift +right click in window, then choose "Open command window here". (Or you just run cmd and navigate to "stuff" folder.)
7. Check fastboot avability:
Type the following command into the cmd window you had opened before at 6.
fastboot -i 0x1949 getvar product
it should return:
< waiting for device>
Then connect Kindle to computer with a regular usb cable. Power down Kindle. Press power buton to start Kindle. . It *SHOULD* show a Fastboot screen and your terminal window should show something like:
product: Jem-PVT-Prod-04
Type this to reboot out of fastboot mode:
fastboot -i 0x1949 reboot
8. follow this procedure: wiki cyanogenmod org/w/Install_CM_for_jem (again, remove spaces and add points to have working link)
Note: when you get to the point "Installing CyanogenMod from recovery" you may be confuse about the fact that adb commands are not working. If so, you check not to be in the recovery boot mode. Just shut down Kindle by long pressing power button, or reboot from meniu and if not passing the booting yellow logo, shut it down again by long pressing power button, then go in the fastboot mode again (see the first part of point 7; do not execute reboot! if you did reboot try again to enter in fastboot mode). Now, in fastboot mode, you can follow the instructions to copy zip files on tablet (I used the cyanogenmode 11 and Google apps zip files). After copy them on tablet, go back to the procedure at the point 4 where you start the kindle in recovery mode again by pressing volume up etc. If you do not succeed by pressing volume up during boot, simple enter again in fastboot (you should know how to do it by now ) and from terminal window on computer (cmd window where you are in "stuff" folder) type:
fastboot -i 0x1949 oem recovery
At this point you are back in the procedure at point 6. Do or not the backup and go next. I did not encountered any problems from this point on.
That is all. Sorry for my English, and I hope that my "procedure" will help someone. Again, thank to all the good people that bother to help us!
Click to expand...
Click to collapse

Nvidia shield tv - unroot instructions

Hello. Is there anyone out there that could provide me with basic instructions on how to unroot my device and put back the stock recovery image?
I haven't done too much after I rooted the device, but I will list whats been done.
1. Performed root with Minimal ADB Fastboot 1.3.1 with SuperSU and TWRP
2. Installed Xposed with a failed attempt to remap the Shield Remote for the OK button long press to kodi context menu. (then uninstalled exposed)
3. Since I couldn't get the exposed key remap to work, I performed a factory rest from within the Android TV settings. (SuperSU is still installed, and every now and then I will see the TWRP splash screen on startup.
4. I attempted to restore the Stock Nvidia Shield TV image with ADB by doing the following:
a. Downloaded the Stock Nvidia Shield TV image.
b. Extracted and copied the folder to ADB fastboot program file directory.
c. Connected Shield with USB to Windows computer.
d. Opened ADB and typed "adb devices" to verify and device showed up.
e. Tried Fastboot verification by typing "fastboot devices" in ADB. Device DID NOT show up.
f. Tried "adb reboot bootloader" and then "fastboot devices" Now the DEVICE SHOWS up.
g. typed, "flash-all.bat" in ADB and it says, "flash-all.bat" is not recognized as an internal or external command"
NOTE: I do have Developer mode, and USB Debugging enabled on the Shield.
The reason I want to unroot is because I have experienced some pretty annoying problems since root. Intermittently upon reboot, Netlix and the Nvidia Game apps do not show. They are just empty spaces. Also the recommendations do not show. I also frequently get "Unfortunately Google Play Services has stopped working" also "Unfortunately Tegra Services has stopped working" and apps crashing/freezing on a regular basis, which force quitting does not resolve. Have to restart Shield to get working again.
I have searched online, and looks like for the most part people who root this device end up not having these problems. Seems like everyone is pretty happy with the root and not experiencing these issues. There are a few I have talked to that have these or similar problems.
If someone could provide me with instructions on how to successfully Unroot my Shield, that would help me out a great deal. I just want it to operate like it was when I first got it. Thanks much for your time.

mikie00mike said:
Hello. Is there anyone out there that could provide me with basic instructions on how to unroot my device and put back the stock recovery image?
I haven't done too much after I rooted the device, but I will list whats been done.
1. Performed root with Minimal ADB Fastboot 1.3.1 with SuperSU and TWRP
2. Installed Xposed with a failed attempt to remap the Shield Remote for the OK button long press to kodi context menu. (then uninstalled exposed)
3. Since I couldn't get the exposed key remap to work, I performed a factory rest from within the Android TV settings. (SuperSU is still installed, and every now and then I will see the TWRP splash screen on startup.
4. I attempted to restore the Stock Nvidia Shield TV image with ADB by doing the following:
a. Downloaded the Stock Nvidia Shield TV image.
b. Extracted and copied the folder to ADB fastboot program file directory.
c. Connected Shield with USB to Windows computer.
d. Opened ADB and typed "adb devices" to verify and device showed up.
e. Tried Fastboot verification by typing "fastboot devices" in ADB. Device DID NOT show up.
f. Tried "adb reboot bootloader" and then "fastboot devices" Now the DEVICE SHOWS up.
g. typed, "flash-all.bat" in ADB and it says, "flash-all.bat" is not recognized as an internal or external command"
NOTE: I do have Developer mode, and USB Debugging enabled on the Shield.
The reason I want to unroot is because I have experienced some pretty annoying problems since root. Intermittently upon reboot, Netlix and the Nvidia Game apps do not show. They are just empty spaces. Also the recommendations do not show. I also frequently get "Unfortunately Google Play Services has stopped working" also "Unfortunately Tegra Services has stopped working" and apps crashing/freezing on a regular basis, which force quitting does not resolve. Have to restart Shield to get working again.
I have searched online, and looks like for the most part people who root this device end up not having these problems. Seems like everyone is pretty happy with the root and not experiencing these issues. There are a few I have talked to that have these or similar problems.
If someone could provide me with instructions on how to successfully Unroot my Shield, that would help me out a great deal. I just want it to operate like it was when I first got it. Thanks much for your time.
Click to expand...
Click to collapse
the firmware pack (the img files, and bat file in the zip file) need to be in the same directory as adb and fastboot
you also need to boot the shield in fastboot mode, you can't flash it otherwise.

Need Help With Unroot
xd4d3v said:
the firmware pack (the img files, and bat file in the zip file) need to be in the same directory as adb and fastboot
you also need to boot the shield in fastboot mode, you can't flash it otherwise.
Click to expand...
Click to collapse
Ok, so when I downloaded the file from: http://nvidiashieldzone.com/index.php/shield-android-tv/root-shield-android-tv/#comment-505
(towards bottom of page under "Restore Shield Android TV to Stock" prerequisites)
It was 1 zip file which I unzipped, and left me a folder with all the files in it (boot.img, recovery.img, blob .bat etc.) I transferred that folder into the minimal adb fastboot folder in C:\program files x86\minimal adb fastboot
Is this the correct process? Or should I have copied the contents of the folder into minimal adb fastboot directory, like a patch?
Thanks for your time, I really appreciate it.

mikie00mike said:
Ok, so when I downloaded the file from: http://nvidiashieldzone.com/index.php/shield-android-tv/root-shield-android-tv/#comment-505
(towards bottom of page under "Restore Shield Android TV to Stock" prerequisites)
It was 1 zip file which I unzipped, and left me a folder with all the files in it (boot.img, recovery.img, blob .bat etc.) I transferred that folder into the minimal adb fastboot folder in C:\program files x86\minimal adb fastboot
Is this the correct process? Or should I have copied the contents of the folder into minimal adb fastboot directory, like a patch?
Thanks for your time, I really appreciate it.
Click to expand...
Click to collapse
Direct link from nvidia http://developer.download.nvidia.co...1/nv-recovery-image-shield-atv-upgrade2_1.zip
And instructions http://developer.download.nvidia.co...TV/Upgrade-2.1/HowTo-Flash-Recovery-Image.txt

if your Shield is not showing up on devices list, you need to install nVidia's driver. It was pretty weird with my Shield. Even with generic drives installed, adb couldn't get authorization from shield. I saw it on a list, but couldn't talk to it. Only after installing official Windows drivers for Shield, I was able to get ADB authorization box to pop up and communicate with device through ADB/fastboot.

mikie00mike said:
e. Tried Fastboot verification by typing "fastboot devices" in ADB. Device DID NOT show up.
f. Tried "adb reboot bootloader" and then "fastboot devices" Now the DEVICE SHOWS up.
Click to expand...
Click to collapse
I'm trying to flash zulu's StockRestyle 3.0 for SATV v1.0 ROM and the "adb reboot bootloader" works fine for me when the shield box is booted up to android (fastboot devices comes up blank), but when I then enter "fastboot" mode, "fastboot devices" comes up with nothing as does "adb devices". It seems once the command to reboot bootloader sends me to what should be fastboot mode, I lose control from the PC.
Any ideas?

gffmac said:
Direct link from nvidia http://developer.download.nvidia.co...1/nv-recovery-image-shield-atv-upgrade2_1.zip
And instructions http://developer.download.nvidia.co...TV/Upgrade-2.1/HowTo-Flash-Recovery-Image.txt
Click to expand...
Click to collapse
I was trying to unroot 2017 Shield TV (16GB) using the instructions provided in this post and failed to notice the recovery image listed here is for 2015 ? version.
Now the shield doesn't boot, not even into fastboot. anyway I can recover?
I should have paid more attention and read more before blindly using the link provided

HELP! fastboot only sees shield for couple seconds
Trying to Restore my 2015 Shield tv.
First couple steps went ok, but in the middle of flashing the system image, I got an error. Now, the shield reboots and I get the laying down android with the "no Command". If I hold down the power button, I get a different boot-loader screen. Then it reboots after a minute. I plugged in my controller into the USB port closest to the HDMI port, hold down the A and B buttons, which gets me into the normal boot-loader.
Problem is that windows sees the shield for a couple seconds, then it disappears. When I type ADB devices, nothing shows up.
What am I missing?

Hello, So i have searched and have been unable to find any info on unroot NVidia Shield Tv (2017) without a computer. I cant seem to find my USB A to USB A cable. I think it may have been stolen last year when a bunch of my stuff was stolen.
Is it possible, if not, is it possible to use the terminal on my phone to unroot.
Any answers would help, and i would greatly appreciate it.

Mnstr3nrgy said:
Hello, So i have searched and have been unable to find any info on unroot NVidia Shield Tv (2017) without a computer. I cant seem to find my USB A to USB A cable. I think it may have been stolen last year when a bunch of my stuff was stolen.
Is it possible, if not, is it possible to use the terminal on my phone to unroot.
Any answers would help, and i would greatly appreciate it.
Click to expand...
Click to collapse
if u only want to unroot pretty sure theres amagisk uninstaller that can be used..
if u also mean relocking the bl then it might be possible if your mobile has adb and fastboot binaries.. theres a module in magisk to install adb and fastboot binaries.. then it would depend if it can connect or not

elliwigy said:
if u only want to unroot pretty sure theres amagisk uninstaller that can be used..
if u also mean relocking the bl then it might be possible if your mobile has adb and fastboot binaries.. theres a module in magisk to install adb and fastboot binaries.. then it would depend if it can connect or not
Click to expand...
Click to collapse
I know that I'm replying super late. My bad. But I just ended up buying a cable off Amazon. Then like 2 days after unrooting, I found the original cable I was looking for in the first place. LOL

ADB failure

i was trying to flash the 2.0 update to my watch. i was in command prompt and was typing in the codes then my watch rebooted into recovery i was able to get my watch back into fastboot mode but now adb isnt recognizing my device and the watch doesnt have any software on it what do i do ?!

Same for me what do I do ? Now when I turn on recovery appears for 2 sec then black screen and over and over again looks like I don't have software installed what do I do ?

I also got the same issue I clicked on recover in the bootloader as everytime I tried to run the following step: Execute the flash-all script by typing flash-all.sh or, in the case of Windows, flash-all.bat.
Set up the watch and begin testing it would just say adb does not recognise this command.
I am now stuck in a cycle of not being access the device in ADB to flash say TWRP or get it to even boot, the only thing I can do is get it back to the boot loader.

OK, so the good news is we didn't brick out watches
First thing is first you will need to get back into the watches boot-loader to do this follow the steps below:
1. Hold the power button down until the Huawei logo show's up
2.As soon as the watch vibrates let go of the power button and do one quick short press of the power button again
3. If you did this right the boot-loader should appear if not you will feel another vibration and will have to start over
Now that you are back in the Boot-loader put the watch back on the dock and plug it into your pc. Fire up ADB and fastboot minimal (Get it here: http://forum.xda-developers.com/showthread.php?t=2317790). Install this and drag the contents of the Sturgeon-nvd file you downloaded from the android site (this is the Android Wear 2.0 preview image) into the same folder that the minimal ADB is installed in like so:
http://i.imgur.com/Vw8sUo1.png
Now double click the Flash-all.bat file in the folder and you should see it processing on the ADB window.

Did you unzip the folder and placed it in the ad folder location?

Just an FYI: ADB is not what is used to flash .img files. Its fastboot. When you are in bootloader mode are you in fastboot mode and would use fastboot commands. Its normal for ADB not to see a device in fastboot mode.

Data recovery problem, no root, no USB debug, screen working, touch not working

Hi to everybody!
This is my first post. I really need help with my Asus Zenfone 2 ZE550ML.
I want to save my data, but the touch doen't work. I tried with Dr. Fone but obviously it need USB debugging on.
So I tried to recover my data via ADB and Fastboot, I've downloaded ADB on my pc, then the clockworkmod recovery mode non touch image(From XDA).
I've copied the image to "platform-tool" folder, then i've put my phone in fastboot mode(volume up + power) and i connected it to my pc.
I've opened cmd window(maiusc+rigth click) in the platform-tool folder, i do the command ect.. the my phone go to "recovery" but it disconnects and I cant' keep going.
At that point i must write in adb "adb pull (smartphone folder to save data) (pc folder where to save data)" or "adb shell" "cd sdcard" "is"
But it disconnects, I don't know what to do
P.s. the phone have sequence password; the wifi is on; the file are in the root, not sd; OTG doesn't work.
P.s.s. this is the second screen i've changed, i don't want to change screen again
Thanks to everybody!