flash a recovery image with adb, without usb debuging, becaouse tablet isnt booting - Android Q&A, Help & Troubleshooting

So i want to flash the recovery image for my nvidia shield tablet, becaouse it isnt booting at all (and no, nvidia didnt killed it, i bricked it :crying: :crying: ) So i got the drivers for adb, but since i cant boot/start the device i cant use adb at all, because it isnt showing any conected devices. I cant access recovery mode either. idk why, but i didnt turn on the usb debuging, so can i do smth to fix this? I would be thankful to anyone who helps me!

Related

Bricked Tablet

I really Need Help! My computer wont recognize my tablet in fastboot mode, and my tablet wont read my micro SD card, also when i turn it on normally it stays at splash screen and when its plugged in to the computer the computer starts installing the drivers and it fails to install each time. I go to troubleshooting options and it states code 10. which states device cannot start.
I Have looked for ways around this, like manually installing the drivers, and my computer wont let me. Also the tablet can go to both: bootloader, and Clockworkmod recovery.
I factory reset my tablet so I cannot install anything, untill i get it to connect to my computer.
I am running Windows 7 64-bit on my computer!
Any help is very much appreciated!
Thanks!
NewDev4IOS said:
I really Need Help! My computer wont recognize my tablet in fastboot mode, and my tablet wont read my micro SD card, also when i turn it on normally it stays at splash screen and when its plugged in to the computer the computer starts installing the drivers and it fails to install each time. I go to troubleshooting options and it states code 10. which states device cannot start.
I Have looked for ways around this, like manually installing the drivers, and my computer wont let me. Also the tablet can go to both: bootloader, and Clockworkmod recovery.
I factory reset my tablet so I cannot install anything, untill i get it to connect to my computer.
I am running Windows 7 64-bit on my computer!
Any help is very much appreciated!
Thanks!
Click to expand...
Click to collapse
Did you install the naked driver from here? http://forum.xda-developers.com/showthread.php?t=1426502 if not do that first once you get that working... then you should be able to fastboot to the pc... next thing I would concider is going to twrp recovery instead of cwm....either go for an older version or go the full gambit of nvflash then install the latest twrp... after that you should be set.....I can comment more on it if you need it....
Bricked Tablet Help
Gage_Hero said:
Did you install the naked driver from here? http://forum.xda-developers.com/showthread.php?t=1426502 if not do that first once you get that working... then you should be able to fastboot to the pc... next thing I would concider is going to twrp recovery instead of cwm....either go for an older version or go the full gambit of nvflash then install the latest twrp... after that you should be set.....I can comment more on it if you need it....
Click to expand...
Click to collapse
I tried installing those drivers but it didnt work
also i used WSG_Unbricker v.1.0.3
my system is wiped
is there any way to install the operating system on it
i need a link for an update.zip
thanks
i can now only go to fastboot mode and wipe data mode.
NewDev4IOS said:
I tried installing those drivers but it didnt work
also i used WSG_Unbricker v.1.0.3
my system is wiped
is there any way to install the operating system on it
i need a link for an update.zip
thanks
i can now only go to fastboot mode and wipe data mode.
Click to expand...
Click to collapse
What do you see in device manager with the tablet plugged into the pc and running in fastboot?
Maybe this helps
I had a similar issue but my tablet couldn't be identified by windows, at first i thought it was my drivers so i tried to install new ones but windows wouldn't let me stating the same code 10. At the end it was a defective usb cable, i bought a new one and everything worked all right the first time i plugged it in. And by the way i was stucked at the CWM loop. Hope this helps and sorry for my bad english.
Bricked tablet
sj010489 said:
I had a similar issue but my tablet couldn't be identified by windows, at first i thought it was my drivers so i tried to install new ones but windows wouldn't let me stating the same code 10. At the end it was a defective usb cable, i bought a new one and everything worked all right the first time i plugged it in. And by the way i was stucked at the CWM loop. Hope this helps and sorry for my bad english.
Click to expand...
Click to collapse
Thanks
Im not sure if it is a bad usb cable, i think it is my computer because my computer doesnt even recognize my iphone and i have itunes installed,
i think it is partially due to a funky computer for me.
BRICKED
Gage_Hero said:
What do you see in device manager with the tablet plugged into the pc and running in fastboot?
Click to expand...
Click to collapse
It says fastboot
I sent my tablet in to asus
just waiting on them to reply

(android 4.0) wintouch q74 tablet bricked

i update my tablet with a liquid rom using default android recoverymode. the installation was succesful but when i reboot my tablet, logo appears as usual and get stack in blackscreen. i could still enter android recovery mode but it only reads internal storage so i cant update anymore, usb debugging was not turned on. how could i get it back to life/unbrick my tablet. (it is not rooted anyway.)
so i tried livesuit v1.09 and connect my tablet while in recovery mode, (the computer detects it as softwiner761) still livesuit doesnt start even if i already selected an img file. system upgrade says "no available device". then i just nomally boot my tab and the computer detects it as an unspecified android, still livesuit doesnt start any progress. turned off tablet doesnt do anything so what should i do?
from wintouch site ive downloaded the the img and downloaded the latest livesuit.
fastboot devices doesnt work too. i have no more idea how could i unbrick this tablet. please help me how could i repair this.:crying:
please help me :crying: :crying: :crying:

how to fix smartphone's dead system

hi everyone.! i had a rooted vodafone smart 2 (alcatel v860) with recovery installed..one day i tried to port kitkat rom but system flash stopped in the middle of proccess and phone turned off.. now recovery and system doesnt work.. only first android image and stuck.. my pc cant recognise my device and doesnt install drivers to fix it using fastboot.. Maybe cause it hasn't got some system installed..to install drivers needs usb debugging enable but i cant without system.. any help?

Access of USB debugging with soft brick

Hello everybody driving nuts with a solution for this:
Phone AGM X1 Chip MTK
Phone is root with Magisk.
Android. 6.1
It happens after flashing some magisk modules, never pass on the loading logo of Linage anymore. The Usb isnt activate.
And I donĀ“t have TWRP installed (bc the phone never let me do it) I did flash in the past with fastboot and TWRP but never installed by default in the phone, always keep only the android recovery.
So I can only have access to Android recovery and bootloader, not to anything else, the screen is not broken, if I get the access to activate Usb debuggin somehow I could restore my phone .
Any clues, tips?.

Acer iconic B3-A30 stuck on boot

Hey everyone
My tablet just doesn't start anymore
it's stuck on the Acer start up logo and I literally don't know what do to anymore
I found a thread which said that i needed to re-flash the Rom with SP Flash Tools
but i'm getting this error S_BROM_DOWNLOAD_DA_FAIL (2004)
tried changing download agent and unchecking preloader too still not working, tried all my pc usb ports still not working
the usb drivers are the official ones from the Acer website
I also tried to do an hard reset but i'm unable to go into Recovery mode
I do all the steps but the tablet just doesn't boot at all
the only thing i managed is to go into the fastboot mode, but adb doesn't find the device
if anyone could help me with this, I would really appreciate that.
Same thing here, but for me adb finds the device, maybe it's just faulty hardware?

Categories

Resources