Related
Tried various possible solutions and still can't get past the Google logo. Installed adb and Samsung driver but when executing commands such as "abd remount" or "adb push file.zip \sdcard\" in cmd I get an error saying "device not found".
Does anyone know how I could resolve this issue?
I tried clearing the cache and wiping the data from the phone, and even heating the phone with a hair dryer. I'd very much appreciate any help.
looks like you still be able to get in reovery ? if so , then nothing you should worry , just flash a new ROM
Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!
nodstuff said:
Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!
Click to expand...
Click to collapse
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.
leeroy88 said:
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.
Click to expand...
Click to collapse
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...
leeroy88 said:
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...
Click to expand...
Click to collapse
Hmmm try going to cmd prompt and typing in adb devices, if you get nothing then your adb isn't set up properly and you need to go into setting and change the path on your computer.
I know the details are sketchy but gimme a min and I will find you a link
---------- Post added at 03:05 AM ---------- Previous post was at 03:00 AM ----------
http://forum.xda-developers.com/showthread.php?t=1161776
Find the Android sdk folder in your computer, move it to the root of C.
I don't think adb is where this guide says it is, there is a read me in the folder where it was saying it has moved to the platform tools folder.
So anyway find the path to the file and put it where the guide says and you should be on the ball.
Forget adb. You need to use fastboot.
Open a command prompt in the directory with fastboot or cd into it.
Put phone in fastboot mode.
On the command prompt type fastboot devices.
You will see your serial number. If you don't recheck and make sure you did everything. Sdk PDA drivers if need be etc.
Fastboot flash recovery custom recovery img name.img
Boot into recovery
Mounts and storage.
Mount SD card
Put a rom for you device on there.
Unmount
Wipe everything but sdcard from recovery.
Flash the rom by going to install zip from SD card......
Okay still stuck trying to connect to my phone. I haven't been able to get my serial number show when typing fastboot devices in cmd. adb is set up and seems to be working but the list of devices is blank when I type in adb devices. The phone was put into fastboot mode both times. I get <waiting for device> when I try
fastboot flash recovery clockwork-5.0.2-crespo.img
I think the bootloader may be locked as it does say LOCKED under lock state, which is probably the reason why I can't get the recovery image to work. I couldn't install PDANet as it wanted to connect to my phone while in debugging mode at the end of the installation. Would it be possible that fastboot oem unlock won't work with without having PDANet installed? I'd really appreciate any further help on this topic.
You need the drivers.
albundy2010 said:
You need the drivers.
Click to expand...
Click to collapse
I have the Google USB driver package installed from SDK Manager. I had tried to install some other Samsung driver found on another post but it wouldn't install.
Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?
leeroy88 said:
Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?
Click to expand...
Click to collapse
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782
ismailham said:
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782
Click to expand...
Click to collapse
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.
leeroy88 said:
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.
Click to expand...
Click to collapse
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?
nodstuff said:
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?
Click to expand...
Click to collapse
After typing fastboot oem unlock I get three dots ...
Pretty much straight away it fails and says something about "too many links".
Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?
kvaju said:
Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?
Click to expand...
Click to collapse
Thanks for your reply, I followed the steps just now and got the exact same error. Before I was trying fastboot oem unlock while in platform-tools but this time I had downloaded the nexussrootICS.zip file, and extracted it to the root of C. I tried fastboot devices and my serial shows up and after fastboot oem unlock I get "status read failed: too many links."
The only difference I seem to have is that in my device manager I have Android Device > ADB Interface, as opposed to SAMSUNG Android Device > ADB Interface.
Not a big difference but that's all I can think of.
the same issue for me. is there any working solution for that?
I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147
GnubbyaBush said:
I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147
Click to expand...
Click to collapse
Thanks! I'll try to do this fancy dancing
I'm trying to get into fastboot
reboot while holding vol down
select the USB icon and press vol up
but I am stuck at "Starting Fastboot USB download protocol"
am i doing something wrong?
xdeslitx said:
I'm trying to get into fastboot
reboot while holding vol down
select the USB icon and press vol up
but I am stuck at "Starting Fastboot USB download protocol"
am i doing something wrong?
Click to expand...
Click to collapse
No you are doing it right. THAT IS IS FASTBOOT. If you run the fastboot commands from your pc you will see it working on the pc.
xdeslitx said:
I'm trying to get into fastboot
reboot while holding vol down
select the USB icon and press vol up
but I am stuck at "Starting Fastboot USB download protocol"
am i doing something wrong?
Click to expand...
Click to collapse
sbdags said:
No you are doing it right. THAT IS IS FASTBOOT. If you run the fastboot commands from your pc you will see it working on the pc.
Click to expand...
Click to collapse
The above is correct, you are in fastboot if you see this (similar to download mode on samsung devices for use with ODIN).
Be sure to add path to environmental variables so that you can use fastboot commands at prompt (if in NT (windows) environment)
sbdags said:
No you are doing it right. THAT IS IS FASTBOOT. If you run the fastboot commands from your pc you will see it working on the pc.
Click to expand...
Click to collapse
i tried running the command " fastboot devices" and it doesnt see my tf700
i have all drivers loaded
Poser said:
The above is correct, you are in fastboot if you see this (similar to download mode on samsung devices for use with ODIN).
Be sure to add path to environmental variables so that you can use fastboot commands at prompt (if in NT (windows) environment)
Click to expand...
Click to collapse
i added the path to environmental variables.
Fastboot works fine for me.
Suggest you go over to the nvflash thread and download the windows drivers.
---------- Post added at 07:54 PM ---------- Previous post was at 07:52 PM ----------
xdeslitx said:
i tried running the command " fastboot devices" and it doesnt see my tf700
i have all drivers loaded
Click to expand...
Click to collapse
Isn't that adb commands you are trying to run. I.e., adb devices. I think you are confusing fastboot.
What are you trying to do?
sbdags said:
Fastboot works fine for me.
Suggest you go over to the nvflash thread and download the windows drivers.
---------- Post added at 07:54 PM ---------- Previous post was at 07:52 PM ----------
Isn't that adb commands you are trying to run. I.e., adb devices. I think you are confusing fastboot.
What are you trying to do?
Click to expand...
Click to collapse
fastboot devices is also a fastboot command from what i understand...i was trying to run that command to see if the computer can even see my tablet in fastboot...which it doesnt.
and i actually did get the drivers from the nvflash thread because that's what i am trying to accomplish
what does your tablet look like when you are in fastboot mode?
because i am doubting the fact that mine is even in that mode...i get the feeling that it gets stuck when trying to load fastboot
xdeslitx said:
fastboot devices is also a fastboot command from what i understand...i was trying to run that command to see if the computer can even see my tablet in fastboot...which it doesnt.
and i actually did get the drivers from the nvflash thread because that's what i am trying to accomplish
what does your tablet look like when you are in fastboot mode?
because i am doubting the fact that mine is even in that mode...i get the feeling that it gets stuck when trying to load fastboot
Click to expand...
Click to collapse
It just says starting Fastboot mode. It never changes from that.
im going to try and uninstall/reinstall the drivers to see if thatll work
finally got it to work...had to reload my drivers
haha so i did the whole nvflash thing but i dont really know how it works
all i know is that itll keep me from bricking my tf700
xdeslitx said:
finally got it to work...had to reload my drivers
haha so i did the whole nvflash thing but i dont really know how it works
all i know is that itll keep me from bricking my tf700
Click to expand...
Click to collapse
You can still brick your device but it's 100% recoverable, at least if it's not a hardware failure. Just make sure to keep your backup files safe.
Pretoriano80 said:
You can still brick your device but it's 100% recoverable, at least if it's not a hardware failure. Just make sure to keep your backup files safe.
Click to expand...
Click to collapse
are there any instructions on how to recover using these files in case of brick?
i didnt see any on the thread under development
xdeslitx said:
are there any instructions on how to recover using these files in case of brick?
i didnt see any on the thread under development
Click to expand...
Click to collapse
There's no guide so far, but i'm sure you would get some help from xda users when needed.
cool thanks for the replies
I'm stuck at fastboot mode with my TF700. Windows XP recognizes my device but the command "fastboot devices" doesn't show up my TF700. I tried to reinstall drivers from univeral naked drivers package 0.7 with success - tried it three times. Bootet up TF700 in fastboot mode but still fastboot doesn't see my device.
Has anyone an idea what I can do? I tried it also in my virtual linux machine without succes. I want to flash new CWM recovery over old TWRP recovery to update to JB and after this to get proprietary files needed to build CM10 from sources.
As I understand, without fastboot, I can't update my bootloader to JB. Not a nice device...
thunderger said:
I'm stuck at fastboot mode with my TF700. Windows XP recognizes my device but the command "fastboot devices" doesn't show up my TF700. I tried to reinstall drivers from univeral naked drivers package 0.7 with success - tried it three times. Bootet up TF700 in fastboot mode but still fastboot doesn't see my device.
Has anyone an idea what I can do? I tried it also in my virtual linux machine without succes. I want to flash new CWM recovery over old TWRP recovery to update to JB and after this to get proprietary files needed to build CM10 from sources.
As I understand, without fastboot, I can't update my bootloader to JB. Not a nice device...
Click to expand...
Click to collapse
Try to use this command to check if fastboot it's working : " fastboot -i 0x0b05 reboot ". If your device reboot after sending that command it means you can use fastboot just fine.
To be honest i've seen many bricks reports from people that tried to only flash the JB bootloader so imo the best way to get the JB bootloader is to flash the official JB firmware, then install the latest TWRP OR CWM recovery via fastboot, use the custom recovery to make a backup of the stock rom. Once you've did all that you can install CM10 just fine but also you will have the opportunity to go back to stock JB in case you need to.
thunderger said:
I'm stuck at fastboot mode with my TF700. Windows XP recognizes my device but the command "fastboot devices" doesn't show up my TF700. I tried to reinstall drivers from univeral naked drivers package 0.7 with success - tried it three times. Bootet up TF700 in fastboot mode but still fastboot doesn't see my device.
Has anyone an idea what I can do? I tried it also in my virtual linux machine without succes. I want to flash new CWM recovery over old TWRP recovery to update to JB and after this to get proprietary files needed to build CM10 from sources.
As I understand, without fastboot, I can't update my bootloader to JB. Not a nice device...
Click to expand...
Click to collapse
Fastboot devices does not work on this device. I've used fastboot to swap recovery images several times and update to the JB bootloader by itself. It definitely works as a whole.
Pretoriano80 said:
Try to use this command to check if fastboot it's working : " fastboot -i 0x0b05 reboot ". If your device reboot after sending that command it means you can use fastboot just fine.
To be honest i've seen many bricks reports from people that tried to only flash the JB bootloader so imo the best way to get the JB bootloader is to flash the official JB firmware, then install the latest TWRP OR CWM recovery via fastboot, use the custom recovery to make a backup of the stock rom. Once you've did all that you can install CM10 just fine but also you will have the opportunity to go back to stock JB in case you need to.
Click to expand...
Click to collapse
I've tried this command many times, and all I ever get is < waiting for device > and nothing else. This is getting annoying as hell. I've tried so many different things, all with the same result. I guess I'll just have to wait until there is an exploit found to root the JB firmware without having to use fastboot, then use TWRP from Goomanager, and hopefully by then there will be a zip of CWM Recovery.
hey guys i have a question.. i made a total n00b mistake and now i am not sure what to do..
I have a htc one s
-i rooted the phone and put twrp 2.8 the newest one then i tried to load a custom rom.. i read somewhere on line that you did not need s off to do this so i tried and now everytime the phone boots it loads the htc screen but goes to a black screen which is kind of dim .. anyway my bootloader is unlocked its version 2.15 and i can get back in to my recovery and mount it i tried several roms but none work.. i was wondering if someone here has a stock rom or something that can get my phone to boot in to a os.. i have tried using fastboot to try and s off but everywhere i read it says u need debugging on my drivers are installed correctly but when u do adb devices it shows empty space.. ive tried many drivers even the google generic i cannot get it to work for the life of me... any help will be appriciated
cheers
Sam
Well let's take it easy. There were some things you've missed when reading so that's why you run into problems.
First thing you missed is that YOU MUST FLASH THE KERNEL IN FASTBOOT if you're S-On. That is EVERYTIME you flash a ROM.
Second, when you're in fastboot, you won't have "ADB devices" command working, you'll have to use "fastboot devices" command instead, ADB does not work while in fastboot.
What you'll have to do is like this:
1. Take any ROM you'd like to flash, place it on your sdcard (while you're in recovery you can mount sdcard to be accessible from pc)
2. Extract from the rom and save it on your pc (in the same folder where adb/fastboot commands are, usually /android-sdk/platform-tools) the "boot.img" file that's in the root of the ROM zip. That'll be called generic "the kernel".
3. Flash the ROM in recovery
4. Reboot to bootloader then while still connected to pc via USB, select fastboot mode. On your screen the "fastboot USB" will be shown.
5. Check if fastboot drivers are installed and fastboot commands are working by issuing "fastboot devices" command. If it'll not return your device then check if drivers are installed properly and you are not using an USB 3.0 port on windows 8.1 (were reported some issues with this configuration).
6. Having fastboot working, open command prompt in the location where fastboot is (and where you have saved the boot.img file) and issue the command: "fastboot flash boot boot.img"
7. Reboot
Now your new ROM should boot and work. Pay attention to choose the right ROM for your hboot and don't forget to do these steps EVERYTIME you're flashing a ROM.
If you're still looking for a stock ROM to flash, there's a thread with all RUUs linked, choose the one for your carrier or model type and run that one but I guess you won't need that
Good luck
Sent from nowhere over the air...
Hello guys. I have HTC Sensation, Bootloader unlocked, S-ON, HBOOT-1.27.0000
Yesterday I tried to flash TWRP using fastboot. I have downloaded ADB drivers and also HTC drivers. Connected device and everything was working good. ADB showed my device serial number (or what it is, I don't remember) when I type "adb devices" in command. Then I typed "cd Downloads" to point to download directory (this is where I have twrp.img) and at least "adb reboot bootloader" . Device rebooted into bootloader, but, suddenly, popup appeared on my laptop, it was saying "USB device not recognized". I have closed it and go into command, I typed "adb devices" again, but it didn't show anything at this time. Then I run command "fastboot flash recovery twrp.img" and it returned "Waiting for device...".
After no luck., I have tried to install twrp.img though Flashify. It successfully flashed. I go into recovery, make a backup, perform clean wipe and tried to flash CM12. But it didn't flash. Then I go to restore tab but I can't see my backup. So, TWRP is not flashing anything, I have even tried stock ROM, also it's not backing up things. So now, I'm in bootloop, no OS is installed on my sensation and every time I boot up device, it automatically going into recovery.
I have laptop running Windows 10. I want to make ADB working in bootloader mode or make TWRP working to flash something.
Thanks in advance.
DroidTwe4kz said:
Hello guys. I have HTC Sensation, Bootloader unlocked, S-ON, HBOOT-1.27.0000
Yesterday I tried to flash TWRP using fastboot. I have downloaded ADB drivers and also HTC drivers. Connected device and everything was working good. ADB showed my device serial number (or what it is, I don't remember) when I type "adb devices" in command. Then I typed "cd Downloads" to point to download directory (this is where I have twrp.img) and at least "adb reboot bootloader" . Device rebooted into bootloader, but, suddenly, popup appeared on my laptop, it was saying "USB device not recognized". I have closed it and go into command, I typed "adb devices" again, but it didn't show anything at this time. Then I run command "fastboot flash recovery twrp.img" and it returned "Waiting for device...".
After no luck., I have tried to install twrp.img though Flashify. It successfully flashed. I go into recovery, make a backup, perform clean wipe and tried to flash CM12. But it didn't flash. Then I go to restore tab but I can't see my backup. So, TWRP is not flashing anything, I have even tried stock ROM, also it's not backing up things. So now, I'm in bootloop, no OS is installed on my sensation and every time I boot up device, it automatically going into recovery.
I have laptop running Windows 10. I want to make ADB working in bootloader mode or make TWRP working to flash something.
Thanks in advance.
Click to expand...
Click to collapse
adb doesn't work in bootloader, only fastboot
when you enter in bootlaoder choose fastboot
in the hboot screen you will see fastboot usb
then you can use any fastboot command
i suggest to change the recovery to 4ext
http://d-h.st/rG7
extract the recovery.img and flash it via fastboot command
then before flashing the new rom from 4ext enable smartflash from it(because you are on S-ON)
rzr86 said:
adb doesn't work in bootloader, only fastboot
when you enter in bootlaoder choose fastboot
in the hboot screen you will see fastboot usb
then you can use any fastboot command
i suggest to change the recovery to 4ext
http://d-h.st/rG7
extract the recovery.img and flash it via fastboot command
then before flashing the new rom from 4ext enable smartflash from it(because you are on S-ON)
Click to expand...
Click to collapse
It doesn't even works in fastboot too :/ So I can't use any fastboot command
DroidTwe4kz said:
It doesn't even works in fastboot too :/ So I can't use any fastboot command
Click to expand...
Click to collapse
Probably win 10 is the issue
rzr86 said:
Probably win 10 is the issue
Click to expand...
Click to collapse
Drivers and SDK is compatible with Windwos 10. I don't think it's the problem, but thanks anyways.
DroidTwe4kz said:
Drivers and SDK is compatible with Windwos 10. I don't think it's the problem, but thanks anyways.
Click to expand...
Click to collapse
use usb 2.0 ports not 3.0
if nothing works then a ruu.exe to return back to stock
http://forum.xda-developers.com/showthread.php?t=1672425
by the way did you enable usb debugging mode from settings?
rzr86 said:
use usb 2.0 ports not 3.0
if nothing works then a ruu.exe to return back to stock
http://forum.xda-developers.com/showthread.php?t=1672425
by the way did you enable usb debugging mode from settings?
Click to expand...
Click to collapse
OK thanks, I'll try them.
Well, I'm not that much noob USB Debugging is enabled.
hi guys,
i my shield is stuck on the nvidia logo when booting normally, if it brings up the bootloader, it shows unlocked but hitting continue caused it to freeze on the screen, recovery freezes on nvidia logo and fastboot protocol just brings it back to this screen. i orginally installed twrp and it confirmed successful flash of new os .... on reboot it bricked to its now state, i cant get into twrp or get my pc to see it to install a new copy
anyone got any ideas
thanks
@Fairmax don't click continue, it freezes because there is nothing to continue to, as long as you can enter bootloader your device isn't fully bricked. So, to fix your problem you will have to download official ROM from nvidia's site (https://developer.nvidia.com/shield-open-source find your model and click recovery images).
When you download latest ROM unzip it and follow the textual guide, but, there will be one file missing (i can't remember which one, user data maybe or something like that), don't worry and just continue with the next step. After you flash just reboot to system by holding power button. Good luck !
i cant seem to get it to be recognised by windows all i get is this-- Windows has stopped this device because it has reported problems. (Code 43) A request for the USB device descriptor failed.--
trying to install nvidia usb driver via have disk bring up an error that the file is not usable with x64 system
ok after many driver reinstall iv got device manager to say android adb interface but still not showing on on device list in cmd
Fairmax said:
ok after many driver reinstall iv got device manager to say android adb interface but still not showing on on device list in cmd
Click to expand...
Click to collapse
Which command did you type in?
fpozar said:
Which command did you type in?
Click to expand...
Click to collapse
adb devices shows no devices
i tried the 3 different option in the driver install which was android adb, bootloader, and something else and nothing shows in devices. i tried it on my laptop and a different cable and cant get adb to list the device :crying:
Fairmax said:
adb devices shows no devices
i tried the 3 different option in the driver install which was android adb, bootloader, and something else and nothing shows in devices. i tried it on my laptop and a different cable and cant get adb to list the device :crying:
Click to expand...
Click to collapse
Well of course adb devices shows no devices because you are not actually in adb mode, you are in the bootloader mode. Just download minimal fastboot and adb, install it and extract recovery image into the folder where you installed minimal adb and fastboot (you don't need any other drivers).After you did this and your device is in bootloader and connected, click on the path in your fastboot & adb folder and delete everything and type cmd. No need to do adb devices, just proceed with fastboot flash ...
fpozar said:
Well of course adb devices shows no devices because you are not actually in adb mode, you are in the bootloader mode. Just download minimal fastboot and adb, install it and extract recovery image into the folder where you installed minimal adb and fastboot (you don't need any other drivers).After you did this and your device is in bootloader and connected, click on the path in your fastboot & adb folder and delete everything and type cmd. No need to do adb devices, just proceed with fastboot flash ...
Click to expand...
Click to collapse
ah now that makes sence....silly me i dont do this very often . so fastboot saw device and iv uploaded all parts of the recovery image and rebooted but it is still stuck on the nvidia logo, that was the original file so now il try 5.2.0 and see if that works
Fairmax said:
ah now that makes sence....silly me i dont do this very often . so fastboot saw device and iv uploaded all parts of the recovery image and rebooted but it is still stuck on the nvidia logo, that was the original file so now il try 5.2.0 and see if that works
Click to expand...
Click to collapse
You can also try flashing twrp and then lineageos or something from twrp.
fpozar said:
You can also try flashing twrp and then lineageos or something from twrp.
Click to expand...
Click to collapse
good news after a few hours of trying (usb dropped connection a few times then battery died) it finally works again .....been over 2 years since iv had this shield running after nvidia did the recall , now goto put a different rom on there so it dosnt update and kill itself
Hello I had a similar issue with my k1 tablet and ended up flashing factory images via adb fastboot and all flashed fine. Now my tablet is stuck on the boot screen with the green and white nvidia logo. How long does it take to boot please?
I have same issue too. I can load TWRP and flash the other partitions but TWRP shows un-mountable partitions and even a full stock ROM flash will not allow it to boot. I have a similar issue with a recall tablet. what did you do to fix it?