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.
I was having trouble with ADB on my newly acquired ViewSonic ViewPad E100. I thought rooting it and/or installing a new OS/ROM might help.
I saw this thread:
http://forum.xda-developers.com/showthread.php?t=2021203
Where someone pointed a guy to a universal root tool:
http://forum.xda-developers.com/showthread.php?t=1886460
I got the tool to run, and tried to use the #1 - New Standard Root - it got as far as to reboot the device.
Maybe I wasn't in trouble yet. But I waited for a bit and the device was still on the "ViewSonic" boot animation. I stupidly pulled the usb plug out to check out the device closer. It didn't boot. Then I restarted. I can no longer get farther than the "View Sonic" boot animation.
Okay, I know there's some special boot methods in Android, so I try a bunch of key combinations. Power+volume down doesn't seem to do anything [yet] but when I press Power+volume up, I get the android guy with a red exclamation in his belly:
http://i.stack.imgur.com/kcSE4.jpg
It's possible I see a flash of a better image, like this one:
http://www.android-hilfe.de/attachm...ery-rotes-warndreieck-2012-09-22-03.41.16.jpg
So no idea what to do. I figured it couldn't get much worse, so put a recovery "update.img" for a gtab on an SD card and then tried to reboot, with holding vol+power, just power, no luck with any combination.
Then I discovered 'nvflash'
http://raywaldo.com/2011/01/nvflash-for-dummies/
I think I'm following the steps right (for a gtab at least), but I can't get into APX mode. I can get *something* when I hold vol-down+power, I actually get my computer (Windows) to show me some internal storage of the device I guess... There's no way for me to install APX drivers, and I don't see the screen "flash" either, just sometimes I get USB storage attached.
Can I recover from this? Are there any more things I should be trying? Does anyone else out there have this device? Where else can I look for help? I just got this device this week and was hoping to use it for development!
Thanks in advance.
I'm not an expert in Android, nor am I an expert with computers, just an average joe in the Android world. Since the time I got myself into this community I never stopped learning something small. I was able to root my phone, install custom firmwares, unroot my device, do a NANDroid back up. All of this done with the help I got from an online source. Now, I'm looking forward to do further tweaks in my device's system. It might sound risky, but I'm enticed by how far an android device can be further improved. But before I do any of this, I'd like to know the appropriate steps to do when something goes wrong like what if device ends up on boot loop.
Questions:
1) What is boot loop?
2) What causes boot loop?
3) Is it the same with a bricked phone?
4) Can the phone be recovered from it (boot loop / brick)?
5) What should be done when a phone is on boot loop?
I humbly ask everone to share a bit of your knowledge about this.
Thank you.
1 - Is kinda of obvious. Bootloop is when your device is stuck at some of bootscreens (model screen, Samsung logo screen) and it doesn't boot properly. Even if you remove the battery and insert it again to turn it on, it doesn't turn on.
2 - There are various reasons: incompatible kernel, incompatible rom, edits on build.prop, rom poorly flashed. And, for our device, if you try to reboot into recovery directly and it has CWM installed, it may enter on recovery bootloop.
3 - I''d say it is a "soft bricked phone". If you has access to recovery or download mode, congrats, you can undo the mess. But if you can't, you got a hard brick. So, it will need repairs.
4 - As I said before, if you has access to recovery or download mode, it is possible to recover it.
5 - It depends. First I would undo my last actions. If I don't have success, I would reflash stock rom, it's almost guaranteed.
So, it happened to my phone when I attempted to do a "Recovery Back Up" using "[ROOT] Rashr" app. I had a Recovery Boot Loop, which boots only into Recovery Mode. But it's fixed now. Here's the thread: http://forum.xda-developers.com/grand-quattro/help/s-o-s-device-boots-cwm-t2981980
This is a reference for those who have the same problem.
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...
Model: SHT-AL09, shipped with C636 (Asia) firmware. It may have originally been C00. Bootloop became a no-boot (it doesn't get past 'this device is unlocked' and load animation) after I flashed some system.img files in an attempt to fix.
I am willing to start from scratch. Fastboot works and Multi-tool works. Bootloader remains unlocked. Stock recovery is currently of no help.
I would greatly appreciate assistance. In the mean time, I'd love to know if it is possible to turn the screen off without letting the battery die out.
What did I initially do? I wanted to test some small changes to my build.prop (which I had already successfully tweaked). They were conservative changes that I felt for sure would not give me a bootloop. Worst case, I had a good build.prop file I could push via adb.
Turns out - a.) bootloop, b.) if USB debugging is not enabled adb is useless.
Early on, the device auto-booted into recovery, and I don't know if I pressed the power button or what, but some recovery process began. I didn't want to risk a wipe at that time, so I booted into download mode while process was at maybe 8%. I don't know if anything was wiped.
I was successfully able to flash system.img from c00/c434 firmwares....as noted that didn't get me anywhere....