Database Info

[Q] Motorola Moto G Lost OS

Hey guys,
Recovery : TWRP 2.6.3.3
USB Debugging : Off
Cannot connect to PC.
Recently, I accidently formatted my Moto G through the advanced wipe and I selected all the partitions to be wipe such as dalvik cache, data, internal storage, cache and system. And now my Moto G doesn't have any OS in it and I can't reboot it at all. I don't have any idea what to do right now. Can someone please help me how can I install a new rom for my Moto G so I can use it like a normal phone again. Please no harsh words, I know it's my mistake and I really need help.

Make sure you post things like this in the Q&A section ull get better help over there then in this General section

Xavier102296 said:
Make sure you post things like this in the Q&A section ull get better help over there then in this General section
Click to expand...
Click to collapse
Thanks

You just need to flash a ROM.

Ammar115 said:
Hey guys,
Recovery : TWRP 2.6.3.3
USB Debugging : Off
Cannot connect to PC.
Recently, I accidently formatted my Moto G through the advanced wipe and I selected all the partitions to be wipe such as dalvik cache, data, internal storage, cache and system. And now my Moto G doesn't have any OS in it and I can't reboot it at all. I don't have any idea what to do right now. Can someone please help me how can I install a new rom for my Moto G so I can use it like a normal phone again. Please no harsh words, I know it's my mistake and I really need help.
Click to expand...
Click to collapse
If you are able to go to recovery(which you should be able to do), download any custom ROM of your choice like PA, CM, SLIM etc.. flash that rom by following the Installation instructions in the thread. YOu should be able to get the phone back to normal. And if you want the stock ROM, then download the stock files and flash it, you might loose custom recovery, then follow the same things you did to get TWRP in the first place.

phanitej said:
If you are able to go to recovery(which you should be able to do), download any custom ROM of your choice like PA, CM, SLIM etc.. flash that rom by following the Installation instructions in the thread. YOu should be able to get the phone back to normal. And if you want the stock ROM, then download the stock files and flash it, you might loose custom recovery, then follow the same things you did to get TWRP in the first place.
Click to expand...
Click to collapse
I would if I could. The problem is I formatted the whole phone which included the internal storage too. My CM Rom is in the internal storage and it's already deleted. I tried to connect my phone to the pc so that I could transfer a rom into it but failed cause my pc won't recognized my phone as the media transfer devices. It's only recognized my phone as fastboot falcon s. I've installed Motorola Device Manger but it's also failed. I also tried to install using adb sideload but I got device not found error and my phone doesn't listed in the device attached after I typed 'adb devices'. For the OTG and memory card reader method I haven't try yet because I don't have any of it.

Ammar115 said:
I would if I could. The problem is I formatted the whole phone which included the internal storage too. My CM Rom is in the internal storage and it's already deleted. I tried to connect my phone to the pc so that I could transfer a rom into it but failed cause my pc won't recognized my phone as the media transfer devices. It's only recognized my phone as fastboot falcon s. I've installed Motorola Device Manger but it's also failed. I also tried to install using adb sideload but I got device not found error and my phone doesn't listed in the device attached after I typed 'adb devices'. For the OTG and memory card reader method I haven't try yet because I don't have any of it.
Click to expand...
Click to collapse
What does it say when you try
Code:
adb devices
or
when you reboot to bootloader with phone connected and type
Code:
fastboot devices
If it shows a device for fastboot devices then follow this to flash back to stock. Make sure you download the right stock firmware for your phone.

phanitej said:
What does it say when you try
Code:
adb devices
or
when you reboot to bootloader with phone connected and type
Code:
fastboot devices
If it shows a device for fastboot devices then follow this to flash back to stock. Make sure you download the right stock firmware for your phone.
Click to expand...
Click to collapse
when I type 'adb devices' it give me an error saying that my device is not found. for the 'fastboot devices', I tried it too but also an error. It say, 'fastboot' is not recognized as an internal or ecternal command, operable program or batch file.

Ammar115 said:
when I type 'adb devices' it give me an error saying that my device is not found. for the 'fastboot devices', I tried it too but also an error. It say, 'fastboot' is not recognized as an internal or ecternal command, operable program or batch file.
Click to expand...
Click to collapse
It seems like you dont have fastboot files. Follow the same link that i posted in the previous one. It has portable adb & fastboot files. Download that and then follow instructions. You should be able to get to fastboot. Once you are there the job is almost done. Hope it helps
Edit: Here is the link to download and install the minimal adb & fatsboot files

phanitej said:
It seems like you dont have fastboot files. Follow the same link that i posted in the previous one. It has portable adb & fastboot files. Download that and then follow instructions. You should be able to get to fastboot. Once you are there the job is almost done. Hope it helps
Edit: Here is the link to download and install the minimal adb & fatsboot files
Click to expand...
Click to collapse
This is what I get using minimal adb and fastboot. What does it mean?

phanitej said:
It seems like you dont have fastboot files. Follow the same link that i posted in the previous one. It has portable adb & fastboot files. Download that and then follow instructions. You should be able to get to fastboot. Once you are there the job is almost done. Hope it helps
Edit: Here is the link to download and install the minimal adb & fatsboot files
Click to expand...
Click to collapse
I've followed all the instructions but my phone still not rebooting. When I try to reboot it, it only show me the warning of unlocked bootloader screen, black screen, warning of unlocked bootloader screen then dead android screen. What should I do now?

It means your phone is in fastboot mode and recognised by your PC. Next you'll have to "fastboot flash" the necessary files to install a recovery and a system, and you should be good to go.

Few weeks back I ****ed up soft bricked my phone had kindda same issue when I switch my phone on I get a dead android logo. Gave to the service center in India and got a replacement a new xt1033
P.s I was trying to root and my warranty was void still got a new one try your luck bruhhh
Sent from my XT1033 using XDA Free mobile app

SbM_ said:
It means your phone is in fastboot mode and recognised by your PC. Next you'll have to "fastboot flash" the necessary files to install a recovery and a system, and you should be good to go.
Click to expand...
Click to collapse
I only want to connect my phone to my pc so I can transfer any rom to my phone so that I can install the rom. But right now, my pc won't recognized it as media transfer that's why I can't transfer any file to my phone. I tried everything. I've installed motorola device manager but all that I got is motorola adb interface that make my phone can connect to the pc when in bootloader mode.I don't have any OTG cable or mobile sd card reader.

phanitej said:
It seems like you dont have fastboot files. Follow the same link that i posted in the previous one. It has portable adb & fastboot files. Download that and then follow instructions. You should be able to get to fastboot. Once you are there the job is almost done. Hope it helps
Edit: Here is the link to download and install the minimal adb & fatsboot files
Click to expand...
Click to collapse
Hey, I've done all of the flashing instruction from the xda forum link that you gave me. My problem for now is, why is my phone not rebooting? The only thing that happen after the flashing is my phone only show the 'warning bootloader unlocked' and the dead android with red triangle screen. It won't boot into the stock rom that I've flashed. The stock rom/firmware that I used is correct. Please help me.. I really need to use my phone.

Ammar115 said:
Hey, I've done all of the flashing instruction from the xda forum link that you gave me. My problem for now is, why is my phone not rebooting? The only thing that happen after the flashing is my phone only show the 'warning bootloader unlocked' and the dead android with red triangle screen. It won't boot into the stock rom that I've flashed. The stock rom/firmware that I used is correct. Please help me.. I really need to use my phone.
Click to expand...
Click to collapse
K there's a resolve for this...Provided that you haven't ****ed up your phone by making it hard bricked...
1 - Get a freaking rom and sideload it through TWRP to boot into system...
+ Download a ROM
+ Put it in the same folder as ADB and Fastboot and rename it to something easier that you can type exactly (ex: 1.zip, backup.zip...)
+ Shift + Right Click at a blank field in the window
+ Choose Open Command....
+ On TWRP, go to Advanced => Sideload => Tick the 2 boxes => Swipe to start sideloading
+ Type in adb sideload <yourzipname>.zip on the cmd (on your computer)
+ Wait for the process to finish, then you now have a working phone...
2 - Follow this guide using the proper firmwares that match your original one : http://forum.xda-developers.com/showthread.php?t=2542219

Zerelth said:
K there's a resolve for this...Provided that you haven't ****ed up your phone by making it hard bricked...
1 - Get a freaking rom and sideload it through TWRP to boot into system...
+ Download a ROM
+ Put it in the same folder as ADB and Fastboot and rename it to something easier that you can type exactly (ex: 1.zip, backup.zip...)
+ Shift + Right Click at a blank field in the window
+ Choose Open Command....
+ On TWRP, go to Advanced => Sideload => Tick the 2 boxes => Swipe to start sideloading
+ Type in adb sideload <yourzipname>.zip on the cmd (on your computer)
+ Wait for the process to finish, then you now have a working phone...
2 - Follow this guide using the proper firmwares that match your original one : http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
Done but still, the same thing happened.

Ammar115 said:
I only want to connect my phone to my pc so I can transfer any rom to my phone so that I can install the rom. But right now, my pc won't recognized it as media transfer that's why I can't transfer any file to my phone. I tried everything. I've installed motorola device manager but all that I got is motorola adb interface that make my phone can connect to the pc when in bootloader mode.I don't have any OTG cable or mobile sd card reader.
Click to expand...
Click to collapse
Your PC will not recognize it as media transfer / storage while you are in bootloader / fastboot mode, its perfectly normal. When you type fastboot devices it should show you a number which means it working as intended. This is an old thread but it shows how to transfer your ROM to sdcard via adb push command. http://forum.xda-developers.com/showthread.php?t=1667929

Ammar115 said:
I only want to connect my phone to my pc so I can transfer any rom to my phone so that I can install the rom. But right now, my pc won't recognized it as media transfer that's why I can't transfer any file to my phone. I tried everything. I've installed motorola device manager but all that I got is motorola adb interface that make my phone can connect to the pc when in bootloader mode.I don't have any OTG cable or mobile sd card reader.
Click to expand...
Click to collapse
The output of the "fastboot devices" command clearly shows your phone is recognised by your PC. As I said all you need to do now is use the correct "fastboot flash" commands to restore recovery and system. Tutorials can be found in this forum.

Thank you.
I would like to say thank you to all peoples who help me solving my lost os problem. Thanks for all the informations. My moto G is working perfectly normal right now.

[Q] M4 soft-bricked! Cannot restore backup! Need help!!!

Hey guys,
I seriously need help with my M4. I think I might have soft-bricked it :crying:
Here's what I have done:
I unlocked it and installed TWRP 2.7.1.1 to install a custom ROM. The thing is, I didn't know it was branded (as I found out too late, the CID is VODAP102), so the ROM wouldn't install. Now, I tried to change the CID to a SuperCID (11111111) but ran out of luck. So I thought I'd simply revert to Stock. So far, so good. Yesterday I got an update notification for a Sense 6.0 update but it wouldn't install. So I successfully flashed the stock recovery but the installation of the update halted (red exclamation mark). I then went back to flashing the boot.img too (from an UL rom, unfortunately) and relocked the bootloader. Still the same error. Then I read I should factory reset in the bootloader. So I did and the result was I got stuck on the bootscreen!! So I unlocked it again, re-installed the TWRP recovery to at least get back to the backup I made before, but the thing is: My storage got wiped and TWRP won't mount OTG-USB!!! I guess it's that some partitions/files are now messed up. Now I cannot do anything anymore. I don't have the stock ROM as a flashable zip, only the TWRP backup.
Here's what still works:
Fastboot & Recovery
What doesn't work:
ADB (because phone won't boot), ExtSDcard (naturally!) and flashing ROMs via fastboot because I need one that matches that damn Vodafone CID
I think if someone could upload their Vodafone Germany M4 ROM as a zip or exe, I could manage it. If someone has it, PLEASE give it to me!
If someone has any other idea how to get this phone to work, or at least get TWRP to mount the USB-stick, please HELP!!! I'm totally at a loss :crying:

You can ADP from TWRP so all is not lost

apjashley said:
You can ADP from TWRP so all is not lost
Click to expand...
Click to collapse
Well, if I start ADB sideload in TWRP, it says it is starting but then nothing happens. Or does it take more than 5 minutes? Because cmd says no devices found :/

It doesn't have to be sideload. You could ADB any old ROM from any screen, and then install it. It would at least get you back on your feet.

apjashley said:
It doesn't have to be sideload. You could ADB any old ROM from any screen, and then install it. It would at least get you back on your feet.
Click to expand...
Click to collapse
Could you explain this? I go into TWRP while connected to the PC and then? When I type 'adb devices' it shows nothing, so I though I need to go into 'Adcanced > ADB sideload' in TWRP...

kumpelfred said:
Could you explain this? I go into TWRP while connected to the PC and then? When I type 'adb devices' it shows nothing, so I though I need to go into 'Adcanced > ADB sideload' in TWRP...
Click to expand...
Click to collapse
What does your Windows device manager show when you're in TWRP but not sideload mode?
I've been wrong before but I believe from sideload mode "adb push firmware.zip /sdcard/" should work as normal.

Hi, thanks for your reply.
The device manager lists it as HTC One Mini but with a yellow question mark. When I plug it in, it recognizes it and installs all the drivers with the exception of the MTP driver, and it won't let me manually install it. In fastboot, it is listed as "MyHTC".
When I go into adb sideload mode in TWRP it gets stuck on telling me it starts the service but nothing happens. "adb devices" remains empty in the cmd console.
As I said, I DO have a backup, only I cannot restore it as TWRP is unable to mount the USB-OTG. I simply cannot check the box (all other partitions data, system etc. work)! I tried 3 different sticks and TWRP versions 2.6.3, 2.7.1.0 & 2.7.1.1. On a friend's M7 TWRP loads that stick in a few seconds. ADB is not working as I said, otherwise I could simply push the file to the internal SD and see if I can restore it from there :/ I think it may have something to do with TWRP not being able to fix permissions, too (it tells me to boot the system once after factory reset, which I cannot do of course!) but I'm not sure....
What I have also tried is setting back the phone (relocked, stock recovery, cache erased) via rebootRUU and a Vodafone DE firmware zip but it tells me "read zipped android info fail" and aborts. Probably because I'm on a higher hboot version than the one in the firmware zip and I cannot go S-OFF without ADB working -.-
I'm struggling with this for 3 days now... Is there nothing I can do to get it booted into anything???

Duh! The Mini is back to life! Weirdly, when I uninstalled the HTC drivers and installed an older package, my device - in recovery mode - showed up under 'adb devices' and I pushed the whole TWRP backup to the sdcard, did a restore and there it is! The only thing that bothers me is that now the Windows device manager shows a yellow question mark on 'CDC Serial'. What does that mean? And why is my device not listed under 'adb devices' anymore after restoring? Very weird
But thanks again!!! Very happy now :good:

kumpelfred said:
Duh! The Mini is back to life! Weirdly, when I uninstalled the HTC drivers and installed an older package, my device - in recovery mode - showed up under 'adb devices' and I pushed the whole TWRP backup to the sdcard, did a restore and there it is! The only thing that bothers me is that now the Windows device manager shows a yellow question mark on 'CDC Serial'. What does that mean? And why is my device not listed under 'adb devices' anymore after restoring? Very weird
But thanks again!!! Very happy now :good:
Click to expand...
Click to collapse
could u share that drivers pls. i have same problem ((

[email protected] said:
could u share that drivers pls. i have same problem ((
Click to expand...
Click to collapse
Hey, I was wrong about the HTC drivers, this was not the issue. The issue was that the latest TWRP recovery (2.7.1.1) did not work in adb mode for whatever reasons. The solution was not older drivers (as they update anyway) but to install an older TWRP version (2.6.3.0 worked for me).
This is only when you cannot boot into your system and have to adb push something to your sdcard. If the phone is not recognized when connected with a booted system running, the only fix is to remove drivers and programs that could interfere (Samsung Kies, HTC Sync, e.g.), reboot, reinstall the drivers, plug your phone into a different USB port and just hope 'adb devices' gets a result, otherwise try all over again.

Bricked Device Help

Hello, my OPO device was bricked after I accidentally wiped the internal memory and it has no rom installed either. However, I have access to the fastboot mode and also TWRP. I've tried to use adb push to put in a rom but it says device not found when I try. Also while connected to my computer, the device doesn't show up, but in device manager it will show up as just "One".
When typing adb devices, nothing shows up, when typing fastboot devices my phone's ID will show with fastboot to the right.

Kogecha said:
Hello, my OPO device was bricked after I accidentally wiped the internal memory and it has no rom installed either. However, I have access to the fastboot mode and also TWRP. I've tried to use adb push to put in a rom but it says device not found when I try. Also while connected to my computer, the device doesn't show up, but in device manager it will show up as just "One".
When typing adb devices, nothing shows up, when typing fastboot devices my phone's ID will show with fastboot to the right.
Click to expand...
Click to collapse
You can do a couple things:
1. Flash COS12.1 from here via instructions in the linked thread
2. Download TWRP and flash it via fastboot commands, reboot to recovery and transfer a nightly and gapps and flash
You are not bricked at all, last time I managed to brick my phone the screen was black no matter what I did, you can easily get back from fastboot

Renosh said:
You can do a couple things:
1. Flash COS12.1 from here via instructions in the linked thread
2. Download TWRP and flash it via fastboot commands, reboot to recovery and transfer a nightly and gapps and flash
You are not bricked at all, last time I managed to brick my phone the screen was black no matter what I did, you can easily get back from fastboot
Click to expand...
Click to collapse
I can't transfer files into the phone as windows doesn't recognize the device anymore, and there is no device found when I try to use adb to push files into /sdcard/
I will try the first option and will let you know.
Edit: First option worked, phone is working fine now. Thanks for your help and I'll be more careful in the future.

Kogecha said:
I can't transfer files into the phone as windows doesn't recognize the device anymore, and there is no device found when I try to use adb to push files into /sdcard/
I will try the first option and will let you know.
Edit: First option worked, phone is working fine now. Thanks for your help and I'll be more careful in the future.
Click to expand...
Click to collapse
Twrp also has USB-OTG function .. Even if you don't have any ROM on phone .. You can download a rom to a usb pendrive and connect it to phone twrp will recognize the USB pendrice and then can install rom from that ..
sent from Bacon (OnePlus One)

How to update early TWRP withoput adb and spooling rom problem

I'd like to know how to update my TWRP from v 2.4.4.0 to a later version. This version doesn't seem to allow flashing of an img file on external sd card. I have tried without success on 2 computers to get windows to recognise this android, so I'm hoping there is another way. Eventually I'd like to install Katkiss,Gapps and SU on this android. At present it has no rom.
Secondly, I tried to install Cromi X and all goes well up until I reboot and it continually spools on the opening screen so I don't know what that is about but hoping with a later TWRP I may be able to set the partitioning better which may or may not be part of the cause.

Reboot recovery twrp.
Go to install.
Click on install image.
Search downloaded recovery.
Select recovery.
And install.
Done
sent from moto g2014 with cm13
---------- Post added at 03:12 AM ---------- Previous post was at 03:11 AM ----------
Ot use flashify app.
It requires root.
sent from moto g2014 with cm13

There is no 'install image' on v2.4.4.0 and that version of TWRP does not seem to recognise .img files on the external sd card. On a later version of TWRP your solution would work.

If you want to flash the recovery in recovery it has to be inside a flashable zip (except for the latest versions).
You can use the Kang TWRP 2.8.x from post 2 here: http://forum.xda-developers.com/tra...overy-kang-twrp-tf700t-2-8-x-xarea51-t3049395
You can flash Katkiss with it no problem, and it supports the dock SD which the official TWRP does not do.
Somewhere there's also a thread where some dude keeps posting TWRP 3.x in a flashable zip, but I can't think of where right now.
That CROMi-X does not boot can have a number of reasons:
You did not format data before flashing the rom
You are on an outdated bootloader
Something is physically wrong with your emmc.
Your problem to get the tablet recognized in Windows is almost certainly a driver problem an you should get that fixed. At minimum it sucks not to have fastboot access to the tablet. And it easily could be lethal. For the tablet - not for you
Could also be a problem with a cheap knock-off replacement USB cable. If you are not using the original Asus cable that's worth investigating. And if you are using the original it may become worn. Mine is starting to allow a connection only in certain positions... Age....
Make sure the device drivers are installed and try the Google Universal Naked drivers. Minimal ADB and fastboot is an excellent tool that shimp208 still keeps current after all this time, and if none of those work try the 15 second adb installer if you are on Win 7 or earlier (just google it).

Hello my old friend. Well I have finally managed to get an adb connection and am going over to old posts of previous help you gave me with this device. Although the device is now recognised I can't get any commands to work e.g. fastboot devices simply returns me to the c:/adb prompt and adb reboot bootloader just takes the flashing underline symbol to the next line and nothing happens. I have hope that I will be able to get this working OK now I have adb access. How do I know if I am on an outdated bootloader? thanks

plato2 said:
Hello my old friend. Well I have finally managed to get an adb connection and am going over to old posts of previous help you gave me with this device. Although the device is now recognised I can't get any commands to work e.g. fastboot devices simply returns me to the c:/adb prompt and adb reboot bootloader just takes the flashing underline symbol to the next line and nothing happens. I have hope that I will be able to get this working OK now I have adb access. How do I know if I am on an outdated bootloader? thanks
Click to expand...
Click to collapse
This is not the same device you helped me with earlier...it now purrs beautifully.... this is a new challenge.

plato2 said:
Hello my old friend. Well I have finally managed to get an adb connection and am going over to old posts of previous help you gave me with this device. Although the device is now recognised I can't get any commands to work e.g. fastboot devices simply returns me to the c:/adb prompt and adb reboot bootloader just takes the flashing underline symbol to the next line and nothing happens. I have hope that I will be able to get this working OK now I have adb access. How do I know if I am on an outdated bootloader? thanks
Click to expand...
Click to collapse
Thought you looked familiar..... :cyclops:
Time to re-read this I think http://forum.xda-developers.com/showthread.php?t=2688891
Boot into the bootloader and read the small script. The last bootloader for this tablet is 10.6.1.14.10.

Yes, that is the bootloader I have. Typing fastboot devices takes me back to the/adb prompt and then typing
fastboot -i 0x0B05 flash recovery <name-of-file>
I get a <waiting for device> but nothing happens.

plato2 said:
Yes, that is the bootloader I have. Typing fastboot devices takes me back to the/adb prompt and then typing
fastboot -i 0x0B05 flash recovery <name-of-file>
I get a <waiting for device> but nothing happens.
Click to expand...
Click to collapse
Yeah, so you have a driver problem. This is nothing you have to do now. Just download the flashable zip of Kang TWRP and flash it in your current recovery.
But when you have some time to kill open Device Manager and connect and disconnect the cable to the tablet. It should give you SOME change in device manager. If it doesn't, reboot both tablet and PC and try again.
Then try a different cable.
Still nothing? This could take longer. Driver problems suck in Windows....
So - you got yourself another TF700? Had just too much fun getting Katkiss to work on the last one, eh?

berndblb said:
Yeah, so you have a driver problem. This is nothing you have to do now. Just download the flashable zip of Kang TWRP and flash it in your current recovery.
But when you have some time to kill open Device Manager and connect and disconnect the cable to the tablet. It should give you SOME change in device manager. If it doesn't, reboot both tablet and PC and try again.
Then try a different cable.
Still nothing? This could take longer. Driver problems suck in Windows....
So - you got yourself another TF700? Had just too much fun getting Katkiss to work on the last one, eh?
Click to expand...
Click to collapse
Just download the flashable zip of Kand TWRP and flash it in your current recovery.
I don't know what you mean here.... how do I 'flash it in my current recovery' I have v 2.4.4.0 and it doesn't see img files on external sd.

plato2 said:
Just download the flashable zip of Kand TWRP and flash it in your current recovery.
I don't know what you mean here.... how do I 'flash it in my current recovery' I have v 2.4.4.0 and it doesn't see img files on external sd.
Click to expand...
Click to collapse
If you downloaded from the second link, the flashable zip, you will see a zip file, not an img file.
Just hit Install, select the zip and swipe the button. Reboot when the flash is finished

All good so far. Up to the wiping data bit before converting to f2fs but this guide is missing, not sure why. I recall it was only a short set of instructions: Once that is done follow this guide to convert internal data to f2fs: http://forum.xda-developers.com/tran...p-2-8-t3073471. Can you recall that part? thanks

Got it, found it or rather another post of yours here: tf700/help/how-to-update-twrp-withoput-adb-t3437702/post68163144#post68163144 so did that and successfully installed Katkis, Gapps pico and SU....another beautiful TF700T purring...many thanks yet again...

bricked shield?

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?