Database Users

[Q] Stuck on Google Screen- Cannot enter fastboot

Hey Guys,
I've been on android since the G1. I've troubleshooted all problems I've had since flashing cyanogenmod when he was first on xda. With this Nexus 7, however, I've kept it completely stock.
I've had it for a month and it's been great. Yesterday I downloaded a homeland torrent and watched it. Put it down, came back two hours later and it was on a black screen (it was charged when I left at least to 50% after d/l and watching the video). I pressed the power button and it wouldn't start. I finally held it down for about 30 seconds and then it went to the "Google" screen all in white letters. It stayed there. I tried holding power for 10, 20, 30, 40, 50, 60 seconds and it would just reboot to the google screen. I finally tried to enter fastboot, i was able to, and got excited at being at a functional screen that I went into "recovery" and then the google screen just popped back up. Now I can't even get into fastboot.
I've tried the nexus toolkits but they both need either abd in android or the fastboot screen. I can't get into them. I finally called google play devices support and they said they will email me within two days to replace my nexus 7. However, I'd like to get my stored images, music, videos, etc off of there at the very least (although, I'd much rather fix it and keep it).
Can you guys suggest anything?
tl;dr : Stuck on google screen, can't enter fastboot. Is there anything I can do to make it boot? Option 2: how can I at least take my (emulated /virtual) sd card data out of it?
THANKS!

You are rebooting each time you try fastboot, correct?
Sent from my Nexus 7 using Tapatalk HD

Correct. It goes black for about three seconds then back to Google screen indefinitely
Sent from my HTC VLE_U using xda app-developers app

Bump?

Wow, I see criticism every time someone mentions they're "Bricked." Now that someone finally is bricked--or at least it seems like--no one is saying anything...

What happens if you hold all 3 keys for ~30-40 seconds, it should, at that point, reboot to the bootloader.

If you are in fastboot again (if this would work one time) you can do
Code:
adb pull /sdcard
Because I guess when it's at the google screen
Code:
adb devices
won't give any output?
But I guess it's a hardware problem, otherwise it wouln't just have turned off...
Sent from my SK17i running Android 4.1.2

mihahn said:
If you are in fastboot again (if this would work one time) you can do
Code:
adb pull /sdcard
Because I guess when it's at the google screen
Code:
adb devices
won't give any output?
But I guess it's a hardware problem, otherwise it wouln't just have turned off...
Sent from my SK17i running Android 4.1.2
Click to expand...
Click to collapse
ADB doesn't work in the bootloader.... ADB is Android Debug Bridge, and Android is not booted while in the bootloader.
Op, this seems like one of those weird things where you will just have to keep messing with it and it will hopefully work eventually. Mess with charging, different timing etc.
Sent from my Nexus 7 using Tapatalk HD

Thanks guys!
korockinout13 said:
ADB doesn't work in the bootloader.... ADB is Android Debug Bridge, and Android is not booted while in the bootloader.
Op, this seems like one of those weird things where you will just have to keep messing with it and it will hopefully work eventually. Mess with charging, different timing etc.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Yeah, holding all three, holding power and volume up, holding power and volume down doesn't work. I've tried holding power until it restarts and then doing power and volume down, up, and both. Nada.
I appreciate your input guys. I'll just return the product to google... hopefully they don't fix it without a full wipe and get ahold of my files! Yeek!

AW: [Q] Stuck on Google Screen- Cannot enter fastboot
korockinout13 said:
ADB doesn't work in the bootloader.... ADB is Android Debug Bridge, and Android is not booted while in the bootloader.
Op, this seems like one of those weird things where you will just have to keep messing with it and it will hopefully work eventually. Mess with charging, different timing etc.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
On my sony device I can do adb pull when I'm in recovery. And if he would be able to enter fastboot and then the recovery, I thought it could work
But I guess the best is to replace it
Sent from my SK17i running Android 4.1.2

mihahn said:
On my sony device I can do adb pull when I'm in recovery. And if he would be able to enter fastboot and then the recovery, I thought it could work
Click to expand...
Click to collapse
He said he was 100% stock.
The stock recovery doesn't start up the adbd daemon. That's typical for stock recoveries.
Proves the point that even if you stay with stock on the N7, you should unlock the bootloader as soon as you get the device. Then the option of soft-booting a different recovery (fastboot boot recovery.img) would be available for rescue situations - even if the ROM stays completely stock and unrooted.

Don't know exactly where you are......
If you OEM unlocked your device, rooted and flashed a custom recovery....I can assist.
Again going with the notion you did...
When your device is on and showing Google
Press and hold the Power key till the screen goes black
Once black, press and hold the volume down key
This will take you to fastboot
Press volume key up twice then power key to select
Device should now be in recovery mode
If you wiped the OS, use Wugs Toolkit to recover from soft brick in advanced options
If you want to push files to your device and try to recover, use MSKIP's Toolkit
Hope this helps....good luck
Sent from my Nexus 7 using XDA Premium HD app

dwny said:
Don't know exactly where you are......
If you OEM unlocked your device, rooted and flashed a custom recovery....I can assist.
Again going with the notion you did...
Click to expand...
Click to collapse
Nope, not unlocked, rooted or have a custom recovery.

[Q] Hard Bricked Nexus 7. PLEASE HELP!

Recently I have had a major issue with my nexus 7. About 2 weeks ago, it died (ran out of battery) while I was using it. When I attempted to turn it on after charging it, I would get the screen that says google, with unlocked lock icon. The tablet would be frozen at this screen. I left it running until it died again. I was running the latest stable release of cyanogenmod 10 with clockworkmod recovery with no problems before when this happened.
By now I had realized that the nexus may have been bricked. I did some googling and found that this is an issue other users have been having when their battery died on android 4.2.2. I attempted to restore the nexus. At this time I was able to access bootloader on the device by holding down all of the buttons at the same time. I think I selected the recovery option. However, I decided not to restore the nexus, and wait until a time where I would be able to turn all of my attention to the problem, and powered the device off, it may have been in recovery mode at that time but I do not remember.
But now, I can't access the bootloader! When I reboot the device by holding down power, I see the google screen for about 4 seconds, then I get a black screen (I can tell the device is still on because the screen is an illuminated black screen). Black screen remains there indefinitely. Any button combo (voldown+power, volup+power, all 3, volup+voldown (this one doesn't do anything), hard reset combo, etc) doesn't do anything except reboot the device and give me the same behavior.
I connected it to my pc (running windows 8) and used the nexus root toolkit by wugfresh to install some drivers. I could install the first driver the toolkit told me to but not the second because the device wouldn't reboot into bootloader. In device manager I see "Galaxy Nexus ADB Driver", hardware ids are USB\VID_18D1&PID_D001&REV_9999 and USB\Vid_18D1&PID_D001, so that tells me custom recovery. Running "adb devices" tells me the device is in recovery mode, but I just see a black screen. Doing adb reboot bootloader or fastboot reboot bootloader hangs and gives waiting for device respectively. Similarly wug's toolkit hangs when trying to reboot the device into bootloader.
I've opened up the back and done a literal battery pull many times. Battery connector is in place after this. I also accidentally broke off one of those tiny copper tabs next to the battery, but that's not relevant to this problem and I believe is minor, broke that after I got this problem. After I do battery pull and plug back in, I either:
a) get a battery lightning icon in the center of the screen, which begins to fill up after a few moments. Rebooting device gets me back into google then black screen mentioned above
b) get a screen with static/snow on it. There is also a hissing/humming noise coming from the back of it. Rebooting gets me to google screen again. This screen also can appear rarely with no discernable pattern to when it appears.
c) same google screen followed by illuminated black screen.
I've left the device charged in, unplugged it, let battery die, and tried many combos of buttons, but can't get anything except the three screens stated above.
I know the saying "Nexus devices are almost impossible to brick" but if I can't access the bootloader and just get black screen then I don't know if I can fix this.
I've posted a thread similar to this one before, so if your username is bftb0 then you've seen this problem already. I'm trying to repost with more information to see if any other ideas are there. Other thread is http://forum.xda-developers.com/showthread.php?p=39522179#post39522179.
So these are my theories to what the problem is:
-corrupted bootloader
-bug/corrupted clockworkmod recovery
-bad battery/power/overheating
-corrupted memory
So how can I solve this?
I know there is NVFlash but there isn't a version for nexus 7. Almost all of the things I've found involve using bootloader. Any suggestions for things I haven't tried yet?
I have obtained an RMA from Asus but I don't want to send the device in because the bootloader is unlocked, so they would probably not cover this under warranty.
Does anybody know of a way to erase evidence of having a bootloader? Or a way to convince Asus to fix the device even with bootloader unlock? What's the price of the repair if not covered under warranty? I'm a poorish student with not much money, so I hope it's not that much and that's why I'm reluctant to pay for repairs.
Also I haven't done anything stupid like fastboot erase bootloader, in fact I hadn't connected the device to pc in a week.
I think this might be a bug with android 4.2. I love android and nexus, but if this is google's fault then I might be done with Android.
Thanks so much.

if it's still bricked i would be interested in buying it for the screen (even screen only,and you keep everything else) cause mine broke today!

komakos96 said:
if it's still bricked i would be interested in buying it for the screen (even screen only,and you keep everything else) cause mine broke today!
Click to expand...
Click to collapse
Perhaps. I'll try to see if I can RMA it under warranty, probably wouldn't be covered though. I'll consider it.
Anyone else, have ideas for how to fix?

Had that problem before:
I had fixed it by opening the nexus 7 and unplugging the battery,
then I hooked it up to the charger(its screen turned on to a black one with the hissing speaker) and used the power button hard reset it,
The nexus 7 reset and gave me a really glitchy/teary black screen.
Then I unplugged it and replugged the battery and put the whole thing back together (mines tape-fixed BTW) and turned it on
Sent from my Nexus 7 using xda app-developers app

STLset said:
Had that problem before:
I had fixed it by opening the nexus 7 and unplugging the battery,
then I hooked it up to the charger(its screen turned on to a black one with the hissing speaker) and used the power button hard reset it,
The nexus 7 reset and gave me a really glitchy/teary black screen.
Then I unplugged it and replugged the battery and put the whole thing back together (mines tape-fixed BTW) and turned it on
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Still no luck... It just gave me the black screen as before. Thanks though

Hi, can you access bootloader mode???
If you not your Nexus has its /boot partition broken or formatted. That is a "Super brick" is irreversible.
Good luck!
Regards.
Sent from my Nexus 7 using xda app-developers app

/boot is kernel. It has nothing to do with his problem. He can't access bootloader.
Flowed from my HTC branded muffin...

No chance to get a free repair out of Asus right? Know of any way to get them/trick them to repair it for free?
If no, what's the price they'll charge?

Hi stereo8.
/boot is not just the kernel, is the boot loader too, and if he can't boot on boot loader mode we have the problem.
Regards.
Sent from my Nexus 7 using xda app-developers app

MlucianoEze said:
Hi stereo8.
/boot is not just the kernel, is the boot loader too, and if he can't boot on boot loader mode we have the problem.
Regards.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Excuse me, but stereo8 is right. You should probably read a bit more about the internal structure / partitions of the Nexus7.
Sent from my Nexus 7 using xda app-developers app

Update:
I think my device may just be stuck in recovery. I think I may have accidentally hit the recover button when I was able to access the bootloader. I was running clockworkmod recovery 10. Perhaps it has been corrupted.
How do I get out of the recovery using adb?

Why do you have 2 threads open for this ?
Sent from my Galaxy Nexus

patil215 said:
Update:
I think my device may just be stuck in recovery. I think I may have accidentally hit the recover button when I was able to access the bootloader. I was running clockworkmod recovery 10. Perhaps it has been corrupted.
How do I get out of the recovery using adb?
Click to expand...
Click to collapse
Connect to the usb to pc and use the adb command" adb reboot bootloader "
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium

heavy_metal_man said:
Connect to the usb to pc and use the adb command" adb reboot bootloader "
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Click to expand...
Click to collapse
I've already posted that I've tried that. The device just powers off and doesn't power on again. Turning it on with any combination of buttons puts me back in the google screen then black screen.

patil215 said:
I've already posted that I've tried that. The device just powers off and doesn't power on again. Turning it on with any combination of buttons puts me back in the google screen then black screen.
Click to expand...
Click to collapse
Ok, while the device is registered as "recovery" open a cmd and cd to your adb set up.
Try using the commands
Adb shell
#wipe data
This should wipe all user data from the tablet, maybe even the sdcard/internal memory as well. I am looking to see if you can use and to flash a bootloader for you, but it would carry heavy risks.
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium

HELP! Bricked Nexus 7, cannot boot into boot loader

Hello everyone, I'm new in this forum and have just bricked my Nexus 7 .
I was not very happy with my Nexus 7 with JB version 4.2.1, it lagged and took long time to load apps etc. I used the Nexus 7 toolkit to unlock my bootloader, flash recovery and then tried a few custom roms. I eventually flash the official 4.1.2 firmware from google but the constant notification for firmware update annoyed me and I decided to root and get rid of the firmware update notifications by installing fotakill.apk.
But when I tried to root using the Nexus 7 toolkit, I chose the option to sideload the zip files for rooting automatically. It asked to flash my boot loader to a lower version (3.34, mine was 3.41) and afterwards it rebooted the device and eventually got stuck at a screen with these lines:
now send the package you want to apply
to the device with adb sideload <filename>
after a long time without anything happening, I suspected that things went wrong and pressed the power button for a few seconds and the device turned off. Now I cannot turn it back on, when plugged in it doesn't show the charging battery, also I cannot boot into fastboot mode by holding Volume down + Power button. The screen stays black the whole time.
I even tried to open the back power and pull the battery out and in again and try to turn on the tablet, nothing happens. I remember the battery level was like roughly 90% the last time the tablet was working, so I don't know what went wrong .

Hold power + vol down button about 30 seconds
Sent from my Nexus 7 using XDA Premium HD app

semeru said:
Hold power + vol down button about 30 seconds
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I tried that but nothing happened .

Press all buttons on the side simultaniously untill fastboot/bootloader mode appears. This should work, no matter if your device is booted or not, or soft bricked or whatever. Then: http://forum.xda-developers.com/showthread.php?t=1907796 .
If it doesn't work however (like after 30-60 seconds), then connect your nexus 7 to your PC. Go to device manager and identify your device. Does it say apx-mode or something like that? Then your device is possibly hard bricked and you might find some answers here: http://forum.xda-developers.com/showthread.php?t=1879228 .
Your should not have used rootkits. Most of these topics appear after people using toolkit. Learn to use fastboot. It's the only program you'll need for the nexus 7. Yes, it's a command line tool but at least it forces you to think before flashing. For example, it was not necessary to downgrade your bootloader. I really don't get why you did that. Also, if you want to run a stable 4.1.2 without the annoying update messages, you can, for example, flash cyanogenmod 10. It's stable, very smooth, and way better than stock.

Westervoort said:
Press all buttons on the side simultaniously untill fastboot/bootloader mode appears. This should work, no matter if your device is booted or not, or soft bricked or whatever. Then: http://forum.xda-developers.com/showthread.php?t=1907796 .
If it doesn't work however (like after 30-60 seconds), then connect your nexus 7 to your PC. Go to device manager and identify your device. Does it say apx-mode or something like that? Then your device is possibly hard bricked and you might find some answers here: http://forum.xda-developers.com/showthread.php?t=1879228 .
Your should not have used rootkits. Most of these topics appear after people using toolkit. Learn to use fastboot. It's the only program you'll need for the nexus 7. Yes, it's a command line tool but at least it forces you to think before flashing. For example, it was not necessary to downgrade your bootloader. I really don't get why you did that. Also, if you want to run a stable 4.1.2 without the annoying update messages, you can, for example, flash cyanogenmod 10. It's stable, very smooth, and way better than stock.
Click to expand...
Click to collapse
Thanks I did a search and finally found an answer. I was running fine on my N7 with PACMan and suddenly it got stuck booting up. So I booted into recovery and reflashed the ROM, and wiped dalvik and cache. When I rebooted it went to "Android is upgrading" like usual after wiping dalvik, then it got stuck there. So I rebooted again and nothing. Just a blank screen. Your suggestion of holding all the buttons down for 30-60 seconds awoke my Nexus. I'm going to wipe everything and start over.

[Q] Bootloop

I installed Asphalt 8 on the G2 only to find out the graphics settings only go up to low. I looked for a fix, and found I could get access to high graphics by changing the model in the build.prop file. I think I must've entered another model nuumber for a supported phone wrong somehow, rebooted and now it's in a bootloop with the LG Logo. Can I change the build.prop WITHOUT wiping it and installing a fresh stock ROM? I'm rooted and have TWRP & Busybox.

check the location of build prop then crate a buildprop cwm zip. U can reuse one fron another device. However put in correct buildprop and correct location of this on device in the script, then flash though recovery. It should boot then. Edit it in notepad++ though.
Sent from my LG-D802

That'd be great, except I don't know how to get to twrp! I can't get a usb connection either.
Sent from my Nexus 4 using xda app-developers app

To clarify, I have TWRP installed of course, but how do I get it without using adb commands, etc.
Sent from my Nexus 4 using xda app-developers app

that I also dont know as I am not rocking custom but stock.
in many threads there speak about how to get into recovery. Go search at least the kernel thread where you got it from
Sent from my LG-D802

transfo47 said:
To clarify, I have TWRP installed of course, but how do I get it without using adb commands, etc.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Try holding Power+Volume Up.
If that fails, go to download mode by holding Volume Up while you insert your USB cable. Follow the instructions here http://forum.xda-developers.com/showthread.php?t=2432476

hamisgood said:
Try holding Power+Volume Up.
If that fails, go to download mode by holding Volume Up while you insert your USB cable. Follow the instructions here http://forum.xda-developers.com/showthread.php?t=2432476
Click to expand...
Click to collapse
I fear that during a boot loop there is little you can do.
And, as the battery cannot be removed, you need to wait for the battery to die! Then you power on to TWRP.

Power + Volume Down until the LG logo disappears and appears again. Let go of Power+Vol Down for a moment and press them back again. Should bring you to a white screen asking if you want to factory reset your phone. Press Power button to confirm and it should then bring you to recovery.

Read the updated post
Sent from my Nexus 4 using xda app-developers app

I've done something bad to my phone (tried to do a factor reset from within TWRP) and now I'm trying to get out of a boot loop myself... When I do the Power+Down trick to rest, it doesn't safely enter recovery and wait for me to do stuff, it launches some sort of recovery/reset script and reboots into my boot loop again.
Anyone know what I'm doing wrong? I was on stock firmware, rooted, with TWRP 6.3.2.1.

elreydetodo said:
I've done something bad to my phone (tried to do a factor reset from within TWRP) and now I'm trying to get out of a boot loop myself... When I do the Power+Down trick to rest, it doesn't safely enter recovery and wait for me to do stuff, it launches some sort of recovery/reset script and reboots into my boot loop again.
Anyone know what I'm doing wrong? I was on stock firmware, rooted, with TWRP 6.3.2.1.
Click to expand...
Click to collapse
Me too but I'm on CWM 6.0.4.4 I don't get that part " it launches some sort of recovery/reset script and reboots into my boot loop again." but it constantly goes in circles
Pat
I Just want to get my Build.prop file back

pfeckert said:
Me too but I'm on CWM 6.0.4.4 I don't get that part " it launches some sort of recovery/reset script and reboots into my boot loop again." but it constantly goes in circles
Pat
I Just want to get my Build.prop file back
Click to expand...
Click to collapse
You don't have to wait until your battery dies in order to shut down from a bootloop. If you hold all three buttons down, it will force shut down your phone. Not sure how long you have to hold it, but I believe you hold until after the LG logo disappears for the second time. It worked for me yesterday after I bootlooped my phone when I mistakenly enabled Thermal Daemon Mitigation instead of High Temperature Property in the Hidden Menu (don't ever do that). I'm not rooted, so I'm not sure if the function still works the same, but if you can get into TWRP after the phone is shutdown, then I believe that's the only way to do it.

[BRICK] Nexus 7 (2012) wont turn OFF (yes!!), Bricked at Boot, Cant access Recovery

The current state of my tablet is quite curious: Its stuck on Google logo and it will be this way until the battery completely drains.
What I've tried:
- Holding the Power button shuts it down for 1 second...then it boots right back up by itself.
- Recovery (POWER+VOL DOWN) doesnt work, it goes straight to Google screen.
- Connecting via USB to the computer, Windows doesnt recognize the device.
In fact, the only way I found to Turn the Tablet off is popping the back cover and unplugging the battery cable. I've left it unplugged at night, hoping it would clear some sort of Cache, didnt work. Also I've tried unplugging the battery cable, plugging it back and Turning it on with POWER+VOL DOWN in hopes of acessing recovery but it goes straight to Google screen.
Additional Info:
- This happened while I was trying to downgrade from 5.1 to 4.4.4.
- My device is the LTE version of N7 2012
- My device is currently rooted.

@RavenEffect hold down the power button for at least 20 seconds to turn it off, 1 second is not enough
How did you try to downgrade? Probably flashing went wrong? In worst cases the bootloader was erased during downgrade ... in that case ther will be no hope.

AndDiSa said:
@RavenEffect hold down the power button for at least 20 seconds to turn it off, 1 second is not enough.
Click to expand...
Click to collapse
1 second is the ammount of time the tablet remains off, not the ammount of time i've pressed it. Yes, I've held it 20 seconds obviously.
AndDiSa said:
How did you try to downgrade? Probably flashing went wrong? In worst cases the bootloader was erased during downgrade ... in that case ther will be no hope.
Click to expand...
Click to collapse
Followed this guide right here: https://drive.google.com/file/d/0Bz6x7k-VkpUJU09paVM5cmh2Xzg/view
All the steps worked until the fastboot flash boot .\boot.img command. Sometimes it would get stuck on the command prompt and the tablet was frozen in Recovery Mode. I had to close the command Prompt, reboot the tablet into recovery again and Flashing another thing first, like recovery and system and THEN i would flash the boot.img.
So theres no hope?

First of all which factory image package did you use?
Sent from my Nexus 7 using XDA Labs

AndDiSa said:
First of all which factory image package did you use?
Sent from my Nexus 7 using XDA Labs
Click to expand...
Click to collapse
The one indicated on the guide, named razorg-mob30x-factory-10b7ca08.zip, the link is in the guide link also.

I suppose you have flashed the Nexus 7(2013) images onto your Nexus 7(2012) device ... that's not a good idea.
Sent from my Nexus 7 using XDA Labs

AndDiSa said:
I suppose you have flashed the Nexus 7(2013) images onto your Nexus 7(2012) device ... that's not a good idea.
Sent from my Nexus 7 using XDA Labs
Click to expand...
Click to collapse
Oh Crap, really? Is there a fix?

Yup, same deal here, not done by me. Now I am stuck in APX mode and I need to somehow flash bootloader back into the tablet. Please, don't tell me there isn't any way to do this...

RavenEffect said:
Oh Crap, really? Is there a fix?
Click to expand...
Click to collapse
Have you tried flashing the images google gives on their website? (they also give a helpful guide)

Charles IV said:
Have you tried flashing the images google gives on their website? (they also give a helpful guide)
Click to expand...
Click to collapse
Yeah, of course, but there is one problem. I can't boot into recovery mode, the bootloader got destroyed. So the only thing I have is either google logo with padlock on the bottom or nothing with APX mode. So no ADB, no FASTBOOT.

krivulak said:
Yeah, of course, but there is one problem. I can't boot into recovery mode, the bootloader got destroyed. So the only thing I have is either google logo with padlock on the bottom or nothing with APX mode. So no ADB, no FASTBOOT.
Click to expand...
Click to collapse
I know for mediatek, there is smartphoneflashtool, which flashes to the device when it's turned off. I don't know if there is an equivalent that you can use.
I don't think NRT does it, so you might be screwed.

There is nvflash ... but only if you have backed up *your* individual device images before you need them. So if your device is already bricked there is no chance ...
Sent from my Nexus 7 using XDA Labs

krivulak said:
Yeah, of course, but there is one problem. I can't boot into recovery mode, the bootloader got destroyed. So the only thing I have is either google logo with padlock on the bottom or nothing with APX mode. So no ADB, no FASTBOOT.
Click to expand...
Click to collapse
Problem is that, when you plug the Tablet to the PC via USB, it doesnt recognize the device, like I've stated on the original post, so I cant even get to a step where I can flash any sort of file.

Well, if I think about it, only the bootloader got destroyed. The image is free on google sites. I just have to put the bootloader image into the tablet so I can get to the bootloader and flash everything else with fastboot. There has to be way to do that. I mean if the "BIOS" (screen with google logo) got destroyed, that is bad, but it is just matter of damage on free to share universal loader. There has to be way...