Could I have bricked my tablet? Or could there be a way to recover?
As for what it's current state is; (I am sure is is stuck in the reboot loop) When powering on the tablet, it displays "Android", goes dark, and repeats. Though this is a change from when I was trying to fix it on my own. Before it looping, it would show the "Android" screen and just sit there.
No comes what I think the REAL issue is... Running 'ClockworkMod v2.5.1.1-bekit-0.8', I am unable to mount an external SDcard or mount the USB Storage(text in menu implies to me it is the USB cable to computer).
So other than the images already on the tablet, I seem to be unable to get a new image into it. And of course the images on it don't do any good.
Tech1381 said:
Could I have bricked my tablet? Or could there be a way to recover?
As for what it's current state is; (I am sure is is stuck in the reboot loop) When powering on the tablet, it displays "Android", goes dark, and repeats. Though this is a change from when I was trying to fix it on my own. Before it looping, it would show the "Android" screen and just sit there.
No comes what I think the REAL issue is... Running 'ClockworkMod v2.5.1.1-bekit-0.8', I am unable to mount an external SDcard or mount the USB Storage(text in menu implies to me it is the USB cable to computer).
So other than the images already on the tablet, I seem to be unable to get a new image into it. And of course the images on it don't do any good.
Click to expand...
Click to collapse
Most definitely not bricked. I've recovered from a much worse situation (bootloader wouldn't even budge - couldn't boot into recovery or regular at all).
Since you are able to boot into recovery, there's probably a way to get things working without resorting to nvflash (we'll get to that in a second - nvflash is the failsafe mechanism, and you should be able to re-nvflash your tablet back to its original state if all else fails).
Here's roughly what I'd try in order:
Option 1) Figure out why you are unable to mount as USB in recovery. I've actually never heard of this problem. Are you using the right cable - i.e. a working USB-to-mini-USB cable (I don't think this works at all with the full sized USB port under the latch cover). Have you tried it with another computer - perhaps there's a driver issue on your PC?
Option 2) If for some reason you really aren't able to get USB mounting working in recovery (I'm skeptical - again, I've never heard of that problem - unless you really did flash a bum recovery image or something - but seems unlikely), then I'd see if you can get ADB working properly when you are in recovery mode. Search around and read about setting up ADB if you haven't already - just a matter of getting the right driver installed on your PC and installing the binary stuff (either from the full Android SDK or one of the packages that just has the ADB stuff floating around). Search the forums, you'll find some references to help you get this working and download the right stuff.
If ADB works, you can always use "adb push filetoflash.zip /sdcard/filetoflash.zip" to put a new file on your internal SD card area and flash it.
Option 3) You can always use nvflash. I'm not going to write up a tutorial on it here - search the forums for nvflash, there are several HOWTOs. Look for the stuff Roebeet posted. You'll need to install the APX driver on your PC first before this will work, and Roebeet's posts don't explain how to install it on Windows, so you'll need to search separately for that. I have gotten this to work before, but it's a pain and I only recommend it if your recovery image is truly trashed or your bootloader is malfunctioning as mine was. In other words, don't bother until you've exhausted the first two options.
So in short - you are in a pain-in-the-ass situation, but you have by no means bricked your tablet - it is very, very far from bricked. Give us more info on *exactly* what happens when you try to "mount as USB" while you have your mini USB cable plugged into the G Tablet - do you see a drive appear on your PC? Are you running a Windows box? Mac? Linux? Have you verified that a USB keychain drive works fine with your PC but the G Tablet won't mount? Basically we need some more info to guide you in your search.
Ok finally had some free time from cleaning/packing and house hunting to try fixing the tablet.
Good news is that I was able to mount the USB. I didn't notice the cat nibble on my cable... So once I dug a spare out, I was able to copy a TnT-Lite image (still had on computer) onto it right quick. Restarted and it installed the image.
So now it has TnT-Lite, though it is weirdly stuck on the setup wizard. It tells me to touch the android to continue and shows an animation of a hand touching the android. But when I touch the android, it turns white and thats it. Also I can change the language to UK or American English. Plus when I press the menu button, I can go to wireless settings, as in cell phone wireless settings. Lastly, I can make an emergency call. So new worthless image. YEY!
I next tried to reboot back into ClockworkMod to see what I could possibly do to get by the lack of continuation in the TnT. But the image install did something interesting. When trying to enter Clockwork Mod, here is what it does from powerup: Displays "Detect a recovery key pressed" then on the next line "Booting recovery kernel image", blanks the screen and then displays "Android" for a few seconds, lastly switching to an exclamation mark in a triangle and rebooting.
So how do I go about screwing it up more?
Tech1381 said:
I next tried to reboot back into ClockworkMod to see what I could possibly do to get by the lack of continuation in the TnT. But the image install did something interesting. When trying to enter Clockwork Mod, here is what it does from powerup: Displays "Detect a recovery key pressed" then on the next line "Booting recovery kernel image", blanks the screen and then displays "Android" for a few seconds, lastly switching to an exclamation mark in a triangle and rebooting.
)
Click to expand...
Click to collapse
CWM is not installed
flash the latest firmware using stock recovery
read read read
http://forum.xda-developers.com/showthread.php?t=892090
It almost sounds like you now have stock recovery in your Gtab.
If that's the case, then maybe copy a stock TNT update.zip onto the external Sdcard, and create recovery/command file on there with the string for SDCARD2, then reboot w power and volume+. If you do have stock recovery, that should flash it back to stick TNT. Try Stock TNT 3452, since that'll also flash a stock recovery for sure.
Jim
Looks like Brian and I crossposted each other .
For the recovery/command file on the external SDCARD, put the following text in it:
--update_package=SDCARD2:/update.zip
NOTE THE 2 DASHES AT BEGINNING OF THE LINE...
Jim
No really, I've Bricked It
So, G Tablet arrived about 5 hours ago. I got it rooted and tried to install CMod 8.1. Things went wrong but I'm not sure what. Anyway, the last thing that I did was to boot in Recovery and then I selected, Format System. Now, when the tablet is turned on, in the top right corner, I have a tiny red message, Magic Value Mismatch. I get this message whether the SD card is installed or not.
I know this information is a little vague but as a Nod, it's all that I have.
f3justusc said:
So, G Tablet arrived about 5 hours ago. I got it rooted and tried to install CMod 8.1. Things went wrong but I'm not sure what. Anyway, the last thing that I did was to boot in Recovery and then I selected, Format System. Now, when the tablet is turned on, in the top right corner, I have a tiny red message, Magic Value Mismatch. I get this message whether the SD card is installed or not.
I know this information is a little vague but as a Nod, it's all that I have.
Click to expand...
Click to collapse
I'm freaking out, I think I bricked it...
I'm only getting the black android screen, I can't seem to mount USB, suggestions?
Ive been stuck right where you are a few times, not to big of a deal, just NVFlash back and start over. I am assuming you are getting the black screen you mention is the APX mode one you get by starting your tab by pressing vol down and power at the same time.
[Q] Is there a way to disable pin lock screen with an "Update from external storage"?
Hi, I have a ZTE V8000 with stock android and locked home screen without WIFI. This is an old phone that I was going to sell for parts but I'm unable to access due to locked home screen. I'd really like to recover any app data (angry birds and what not) and any contacts. Phone is completely stock and is not rooted. I can't connect to WIFI so I can't reset via playstore. I tried connecting to computer several times. Once I was able to pull up two folders which I didn't back up and the second time after trying to access different boot mode I was able to pull up Image AMSS which I later found out was just for the radio. The phone goes straight to the android on his back with error triangle when attempting to enter recovery mode. Safe mode does nothing to bypass screen lock and holding down arrow and power boots up until it says ZTE then stops. (What does is this boot mode supposed to do?) This is very frustrating since it seems to me like there would have to be some way to access data on android internal storage? Would there be a way to modify the password lock via an update from external storage?
This has become very frustrating for me as I know EVERYTHING has a workaround . Why would there be an option to encrypt the device if the screen lock is impenetrable?
foolioGrimz said:
Hi, I have a ZTE V8000 with stock android and locked home screen without WIFI. This is an old phone that I was going to sell for parts but I'm unable to access due to locked home screen. I'd really like to recover any app data (angry birds and what not) and any contacts. Phone is completely stock and is not rooted. I can't connect to WIFI so I can't reset via playstore. I tried connecting to computer several times. Once I was able to pull up two folders which I didn't back up and the second time after trying to access different boot mode I was able to pull up Image AMSS which I later found out was just for the radio. The phone goes straight to the android on his back with error triangle when attempting to enter recovery mode. Safe mode does nothing to bypass screen lock and holding down arrow and power boots up until it says ZTE then stops. (What does is this boot mode supposed to do?) This is very frustrating since it seems to me like there would have to be some way to access data on android internal storage? Would there be a way to modify the password lock via an update from external storage?
This has become very frustrating for me as I know EVERYTHING has a workaround . Why would there be an option to encrypt the device if the screen lock is impenetrable?
Click to expand...
Click to collapse
update:
I don't know if this is relevant or not but I possibly rooted phone with SuperSU_v1.86 for engage. Still stuck with stock recovery though. I also tried to run Aroma File Manager from SD Card and had error with the signature.
foolioGrimz said:
update:
I don't know if this is relevant or not but I possibly rooted phone with SuperSU_v1.86 for engage. Still stuck with stock recovery though. I also tried to run Aroma File Manager from SD Card and had error with the signature.
Click to expand...
Click to collapse
Install the custom recovery here:
http://www.cricketusers.com/cricket-zte-engage-v8000/48531-cwm-recovery-zte-engage.html
and see if this thread can help:
http://forum.xda-developers.com/showthread.php?t=1800799
I was unable to extract any useful data from the phone after factory reset besides a few pics with data digger. My other cracked engage with screen locked i was able to use temporary recovery manager loaded by update from external storage and i was able to make a nandroid and extract anything i wanted with titanium backup pro. The temp recovery is an awesome tool and i wish it was available for all my devices
Ok, here is the deal and I hope someone can help me. I have a cheap DigiLand DL1010Q tablet to play around with. It is stock, but I rooted it with KingRoot. There was a recent OTA wireless update and after it was installed it said that it needed to go into recovery mode to install and reboot. I selected install now and reboot. This is where my problem started and has remained. It loaded into recovery mode and is in an endless boot loop. I've tried rebooting it, recovery with the recovery file and every manual reset possible to no avail. DigiLand support said that I should power down the tablet, and while holding down the Volume Down (-) hit the power button and it will boot into a Chinese recovery mode. I've tried that and it just stays on the DigiLand screen forever. (I left it there for 8 hours.) I can sideload via ADB and the drivers are installed, but it will not let me load anything. It states that the bootloader is closed. I receive the same message via Fastboot. Now here is the interesting thing. Even after selecting the factory reset within the Recovery Mode, everything is still there. I have wiped the cache and partition and user data, but nothing really happens. It is still all there. I see the recovery file, but it will not load. All I see is NO Command.
I do have a sd card that I could flash things on, but it doesn't seem to register the card. It sees the sdcard, but that is the internal drive. How do I get it to look at the sdcard that I put into the slot? Is there a bootloader unlock? Does anyone have the factory image that I can put on my sdcard? HELP!!!!
I am fairly good with computers and have rooted phones and tablets before, but I seem to be hitting my head on a bricked wall - no pun intended. Let me know what programs, files or whatever. At this point I am willing to try anything. I can send it back to China for $50 for them to redo it, but I only paid $69 for it and I'm not going to put more money into this cheap tablet. I would just like to get it to work.
To start off, I suffered, what seems to be a common problem, of the fingerprint unlock on Samsung Galaxy S6 Edge randomly being unable to recognise my fingerprint. Followed by my back-up password not being accepted. Unfortunately, I turned off my data and wifi before the phone locked so the problem doesn't seem to be able to resolve itself unless I Factory Reset the phone.
This i am happy to do as long as I can find some way to retrieve the media files from the phone (just pictures and videos). I read up and watched some videos where some people were able to use ADB through Recovery Mode or Field Test mode, and pull the files from the phone. These people however were using older models of Android phones but I decided to read numerous pages etc and go ahead and try.
I set up everything (I believe) i needed on my Mac Book pro in order to use the Adb Terminal. However when I tried to connect my phone Adb couldn't detect my device. I then decided (after reading somewhere to do so) to press "Apply update using ADB" on the Recovery menu. Again, Adb did not detect my device.
i left this screen up on my phone which resulted in "dm-verity verification failed..." appearing at the bottom of the screen. It then switched back to the Recovery menu and continues to show "dm-verity verification failed..." at the base of the screen. Now when I try and power up the phone normally, the start up screen just repeatedly flashes and it goes no further than that.
Im not completely brain dead when it comes to this stuff but I obviously don't fully understand what I am doing, So Im wondering if there is a genius out there who, even after what I've done, can help me pull the files from my phone before I have to Factory Reset!
To start off, I suffered, what seems to be a common problem, of the fingerprint unlock on Samsung Galaxy S6 Edge randomly being unable to recognise my fingerprint. Followed by my back-up password not being accepted. Unfortunately, I turned off my data and wifi before the phone locked so the problem doesn't seem to be able to resolve itself unless I Factory Reset the phone.
This i am happy to do as long as I can find some way to retrieve the media files from the phone (just pictures and videos). I read up and watched some videos where some people were able to use ADB through Recovery Mode or Field Test mode, and pull the files from the phone. These people however were using older models of Android phones but I decided to read numerous pages etc and go ahead and try.
I set up everything (I believe) i needed on my Mac Book pro in order to use the Adb Terminal. However when I tried to connect my phone Adb couldn't detect my device. I then decided (after reading somewhere to do so) to press "Apply update using ADB" on the Recovery menu. Again, Adb did not detect my device.
i left this screen up on my phone which resulted in "dm-verity verification failed..." appearing at the bottom of the screen. It then switched back to the Recovery menu and continues to show "dm-verity verification failed..." at the base of the screen. Now when I try and power up the phone normally, the start up screen just repeatedly flashes and it goes no further than that.
Im not completely brain dead when it comes to this stuff but I obviously don't fully understand what I am doing, So Im wondering if there is a genius out there who, even after what I've done, can help me pull the files from my phone before I have to Factory Reset!
The problem is, that you don't have the ability to use adb pull through the stock recovery. This kind of thing can only be done via a custom recovery like TWRP, CWM, or Philz. Now that it's not booting, pretty much the only thing to try is to install a custom recovery and boot directly into it before it tries to restart. Make sure you find one for the correct variant of your phone. If yours is a VZW or ATT version, you're in trouble because they don't have custom recoveries like that for them.