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.
Just bought this as a replacement for another tablet. When I got it, the wifi would not turn on properly so I flashed this rom going through the recovery menu. Now upon booting, the screen with the android robot comes up, and then switches to a black screen with the backlight on and nothing happens. What I've tried:
-adb devices does show that it sees the devices
-abd reboot recovery results in a restart and nothing else (that I can see)
-abd reboot bootloader also results in nothing
-adb shell results in " - exec '/system/bin/sh' failed: no such file or directory (2) -"
-allowing the tablet to die and then recharging it does nothing
Trying to flash via livesuit results in device not found error, and I can't boot into recovery via the hardware buttons. Should I just give up and send it back to the manufacturer?
This tablet comes rooted. CWM is not installed. Pretty much everything I've found involves either CWM or the recovery menu, neither which I can access. Any other ideas, or is it time to give up?
HELP!!!! bricked trio stealth 4.0
Ok so I havE the exact same tablet as you and have done the exact same thing and come to the exact same finally. No luck get passed the backlit screen. Have you been able to bring yours back yet
ftkatyowser said:
Just bought this as a replacement for another tablet. When I got it, the wifi would not turn on properly so I flashed this rom going through the recovery menu. Now upon booting, the screen with the android robot comes up, and then switches to a black screen with the backlight on and nothing happens. What I've tried:
-adb devices does show that it sees the devices
-abd reboot recovery results in a restart and nothing else (that I can see)
-abd reboot bootloader also results in nothing
-adb shell results in " - exec '/system/bin/sh' failed: no such file or directory (2) -"
-allowing the tablet to die and then recharging it does nothing
Trying to flash via livesuit results in device not found error, and I can't boot into recovery via the hardware buttons. Should I just give up and send it back to the manufacturer?
This tablet comes rooted. CWM is not installed. Pretty much everything I've found involves either CWM or the recovery menu, neither which I can access. Any other ideas, or is it time to give up?
Click to expand...
Click to collapse
So a friend recently bought this spanish voxter tab 97 IPS (16GB) and after a few days of usage and several attempt to install a custom ROM, the tablet stopped booting. According to him, he tried loading a "compatibility bla bla bla.zip" file with CMW which I really do not know what it is, and since he did the installation, the tab stopped booting into system. Every time it's turned on, it just stops at the boot screen and nothing more. Although before this, he had installed a custom recovery and had also done a Nandroid backup with the recovery. However, what baffles me is, CMW is no longer accessible through the normal "power + volume up" key combo and I'm quite unsure of how to boot into fastboot.
That aside, I tried booting into recovery with adb because apparently, adb recognizes the device whenever it's stuck at boot screen, this also failed, neither did rebooting into fastboot via adb work. All I need to know is if this device is totally bricked, or if there's still something I can do. If there's any, I really would appreciate every help offered. Thanks..
Hello there i need some help this is what happened.
I had this phone with purple screen so i download the room and flash it tru the sd card with the method of the buttoms (voluime up+ volumne - and power) the phone start doing the proces finish but never boot up it stay on a black screen.
After a while checking what when wrong i find out that i flashed a wrong firmware i used y210-0100 when i had to use y210-0151, so i download the new sofware and tried again but this time the phone does not go in to the flash mode wiith the botom (or any other mode)at least does not show nothing on the screen.
Right now the phone vibrates when i turn it on but does not show nothing on the screen only a black screen adb system in the computer recognize the phone but only when i conected in recovery mode (but nothing shows in the screen).
I have tried to flash it again with adb but nothing has work yet even thought to flash it tru the sdcard with adb but nohting has work yet, actually i am not an expert with the adb thing maybe you can recomend some comands that may work.
When i trien comands like "fasrboot -w" adb says waitng for device and get stuck there forever also with "fasboot flash file" or something likes that
So i will like to know if some one has any suggestion please let me know it may help me to fix this problem.
Y210-0100 Black Screen
Same thing happen to me after upgrading. HELP!!!
So my friend was trying to get some stupid game to work on my phone that my phone didn't support, so he tried replacing the build.prop for my Pantech Flex with one for the Galaxy s3. Which needless to say bricked it.
I can start up the phone, and I assume it starts up normally and goes to the lock screen. But everything after the pantech logo is black screen.
Here is what I've tried:
1. Pulling my current build.prop and editing it, then pushing it back with ADB. Pulling it works, but when I push it, nothing seems to happen. It says "Success" but when rebooting the device, my phone is still ****ed up. And when I pull the build.prop back again, it's the one for the Galaxy s3 and not the one I just pushed.
I read that the reason this is happening is because ADB doesn't have root permissions. Not sure if thats true though, as I obviously have rooted my phone.
2. Booting the device into recovery. For a while now, trying to boot into recovery leaves me stuck on the Pantech logo. I think this may be due to me flashing a recovery that wasn't for my device a while back. So I can't get into my recovery to factory reset it.
3. Booting into fastboot mode. The Flex is a strange creature, so there is no standard bootloader apparently so when using "adb reboot bootloader" it reboots into fastboot instead of a bootloader. Meaning on the screen is just white text saying "FAST BOOT mode" and adb disconnects, and fastboot devices sees the device now.
Trouble here is, I have the stock recovery for the Flex. But when I use Fastboot boot recovery.img or Fastboot flash recovery recovery.img or fastboot wipe data or anything in fastboot really, I get a "Not support!!" error. Which I assume means my phone is a piece of **** and can't be used with fastboot.
So now I'm at my wits end and don't know what else to do. I am dead broke and need my phone for work.
Is there anyway I can fix the build.prop or factory reset my phone?
Fukesh said:
So my friend was trying to get some stupid game to work on my phone that my phone didn't support, so he tried replacing the build.prop for my Pantech Flex with one for the Galaxy s3. Which needless to say bricked it.
I can start up the phone, and I assume it starts up normally and goes to the lock screen. But everything after the pantech logo is black screen.
Here is what I've tried:
1. Pulling my current build.prop and editing it, then pushing it back with ADB. Pulling it works, but when I push it, nothing seems to happen. It says "Success" but when rebooting the device, my phone is still ****ed up. And when I pull the build.prop back again, it's the one for the Galaxy s3 and not the one I just pushed.
I read that the reason this is happening is because ADB doesn't have root permissions. Not sure if thats true though, as I obviously have rooted my phone.
2. Booting the device into recovery. For a while now, trying to boot into recovery leaves me stuck on the Pantech logo. I think this may be due to me flashing a recovery that wasn't for my device a while back. So I can't get into my recovery to factory reset it.
3. Booting into fastboot mode. The Flex is a strange creature, so there is no standard bootloader apparently so when using "adb reboot bootloader" it reboots into fastboot instead of a bootloader. Meaning on the screen is just white text saying "FAST BOOT mode" and adb disconnects, and fastboot devices sees the device now.
Trouble here is, I have the stock recovery for the Flex. But when I use Fastboot boot recovery.img or Fastboot flash recovery recovery.img or fastboot wipe data or anything in fastboot really, I get a "Not support!!" error. Which I assume means my phone is a piece of **** and can't be used with fastboot.
So now I'm at my wits end and don't know what else to do. I am dead broke and need my phone for work.
Is there anyway I can fix the build.prop or factory reset my phone?
Click to expand...
Click to collapse
Also, maybe there is a way to set up a VNC server of some sort to use the phone from the computer??