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.
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.
Hello.
How it happened
I rooted my HTC One S, then flashed CyanogenMod on it. Used it for a few months, very happy with it. Then I tried to update - automatically, not manually (that was mistake number 1). The phone was then stuck in a bootloop into recovery. (Off>Recovery>Off>Recovery). I didnt know what to do, so I pressed 'Reset phone', or something like that. Since then, the problem has gotten much worse. Now there's a different bootloop: Off>HTC opening screen. That's it. Im desperately trying to access recovery mode, to flash a new ROM to fix the situation.
What did I try
1. Power + VolumeDown does nothing.
2. Installed the HTC One S toolkit. When pressing 'boot into recovery', it says 'device not found'.
3. Tried to boot into recovery from ABD tools, but it says device not found. I tried putting screenshots here, but XDA forum new user limitation doesnt let me. Anyway, if you add this to the imgur url, youll see the screenshots (sorry about this inconvenienace):
/SblBm3M
/6HEvZDk
TL;DR
Phone is stuck in a bootloop. Cant access recovery. Is there any way to fix this situation?
Thank you very much in advance for your time to help me out.
Hi all.
I have an Asus TF103C that had been updated to lollipop that is currently (soft?) Bricked
I've been through pretty much all the threads and tried all of the fixes. Still unable to boot into android. I am unsure what step to take next. I cant apply official firmware updates via SD card nor sideload via ADB
Currently I can get it to boot up to a UEFI BIOS screen(where I can only scroll up and down via volume keys on the first page and nothing else.) or a fast boot screen showing firmware version ( 209.05 just incase its needed.) I can get it back to a droidboot screen, but I still cant flash any system img. If it's important this tablet uses an Intel Z3745.
Just a quick bump. Still only have access to the fastboot screen and recovery. I attempted flashing images again, and while it eventually goes through after breaking the image down into smaller parts, upon reboot I'm stuck at the android screen.
Open to any help what so ever.
It should also be noted that upon flashing via fastboot, after the system image goes through, I get the error " Flash Capsule Failed." And then it reboots to just the android screen.
Mine also bricked
Hi cronus2
Did you manage to solve this problems? I gather from your second post that you managed to get past uefi... I'm still stuck there: how did you do that?
Thanks to anyone who can give me some help here...
Hello. I have tried to install a custom recovery (TWRP) on my Samsung Galaxy Tab A 8.0" (SM-T290) today, however, it has not exactly gone to plan. I will run over exactly what I did, and what troubleshooting steps I have taken so far.
I downloaded this version of ODIN: https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/
I unlocked the bootloader through the bootloader menu and enabled USB debugging after the tablet had turned on.
I downloaded and used the latest .md5.tar TWRP file from here: https://forum.xda-developers.com/t/...-2-for-2019-galaxy-tab-a-8-0-sm-t290.4185235/
ODIN Successfully flashed TWRP and the device rebooted. I attempted to get straight into the recovery by holding volume up, however, the screen remained black.
The tablet now cannot boot into recovery, download mode, etc, and only the backlight of the screen turns on. The tablet does eventually "boot up" and give the little vibration, at which point my computer recognises it, but I cannot see any files on the tablet. I can also see the tablet with ADB using the command "adb devices", however it tells me the tablet is "unauthorized", meaning I cannot use any ADB commands to attempt to reboot into recovery, download mode, etc.
I have tried disconnecting the battery and just powering on with the cable to no avail. I am assuming the device is fully bricked at this point, however, I would be appreciative if any possible solutions could be suggested, and if where I went wrong can be pointed out so I do not make the same mistake in the future.
Thanks in advance.
It's always risky to apply mods.
To get rid off of all mods you applied re-flash tablet's Stock ROM.
If this doesn't work for you then take it to authorized service center and let them try to fix it.
jwoegerbauer said:
take it to authorized service center and let them try to fix it.
Click to expand...
Click to collapse
They never fix anything. The only thing they do is charge you an absurd price and replace the motherboard or the entire tablet.
I'm on the same boat. Tablet can't get into download mode, just shows "This device has unauthorized software on it and is locked". Tried all possible button combinations to no avail.
SmiffyJ said:
Hello. I have tried to install a custom recovery (TWRP) on my Samsung Galaxy Tab A 8.0" (SM-T290) today, however, it has not exactly gone to plan. I will run over exactly what I did, and what troubleshooting steps I have taken so far.
I downloaded this version of ODIN: https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/
I unlocked the bootloader through the bootloader menu and enabled USB debugging after the tablet had turned on.
I downloaded and used the latest .md5.tar TWRP file from here: https://forum.xda-developers.com/t/...-2-for-2019-galaxy-tab-a-8-0-sm-t290.4185235/
ODIN Successfully flashed TWRP and the device rebooted. I attempted to get straight into the recovery by holding volume up, however, the screen remained black.
The tablet now cannot boot into recovery, download mode, etc, and only the backlight of the screen turns on. The tablet does eventually "boot up" and give the little vibration, at which point my computer recognises it, but I cannot see any files on the tablet. I can also see the tablet with ADB using the command "adb devices", however it tells me the tablet is "unauthorized", meaning I cannot use any ADB commands to attempt to reboot into recovery, download mode, etc.
I have tried disconnecting the battery and just powering on with the cable to no avail. I am assuming the device is fully bricked at this point, however, I would be appreciative if any possible solutions could be suggested, and if where I went wrong can be pointed out so I do not make the same mistake in the future.
Thanks in advance.
Click to expand...
Click to collapse
Hi,
I have the exact same problem, did you manage to recover the tab?
Thanks heaps