Database Users

2.2.1 SBF for Motorola Bravo (links working)

This guide was created by jorgonv, All credits to him, I was too lazy to create another one .
I just replaced the dead links with working links.
-------------------------------------------------------------------------------------------
Anything YOU do to YOUR phone is not my fault, please proceed with caution​To flash your phone:​
1. Download RSD Lite, Drivers, and .sbf files from below
2. Install RSD Lite
3. Open RSD Lite as administer (hold shift, right-click on RSD Lite, select Run as administer)
4. Unzip the .gz and extract the .sbf
5. Open RSD Lite, browse for the .sbf file and select it.
6. Power your phone into the bootloader mode (hold volume up and power on, should be a black screen with white text)
[If the bootloader screen says Cannot program, your battery is too low to apply .sbf]
7. Plug phone in and run the driver installer. (You can install drivers before doing all of this)
8. RSD lite should recognize your phone now.
9. Select you phone on list in RSD Lite and press Start
10. Wait for it to finish
Whatever you do, do not unplug your phone from computer or disconnect them in any way
​
Note: If you bootloop and are stuck at the red M logo, you need to wipe data in stock recovery. To do that, hold the volume down button and continue holding it when you power up the phone. Then, once you see the triangle and android, press both volume buttons at the same time. After that, scroll down and select wipe data/factory reset.​
Downloads:​
MOTOROLA Drivers: http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
SBF file: http://www.4shared.com/archive/kymHVVwK/p4_kobe_umts_kobe_user_342-125.html Updated!
RSD Lite 5.0: http://www.4shared.com/file/5zh6sjdb/rsdlite_50.html​Root with Simple Root & Recovery Installer! or
SuperOneClick (with psneuter or Gingerbreak) and enable non-market apps:
http://forum.xda-developers.com/showthread.php?t=803682​

what's the password for RSD?

feistygoat10 said:
what's the password for RSD?
Click to expand...
Click to collapse
Does it have a password?
I'll upload it again without password, sorry about that!
EDIT:
Done, everything is fine.

Just to clarify, with this we can go back to stock entirely. Losing root, 2nd init, bootmenu, etc, right?

corvx said:
Just to clarify, with this we can go back to stock entirely. Losing root, 2nd init, bootmenu, etc, right?
Click to expand...
Click to collapse
You are right.
But this is just in case there is no way to enter to custom recovery (2init defy) and your phone doesnt boot!

you sir are a lifesaver

Is this OK to get a stock 2.2 that I can then root and restore my apps?
I can't do OTA from 2.1, it fails telling me dlna.apk is missing.
Thanks.

Went ahead and did it anyway, painless and worked very well.
Thanks.

HELP
after step 10 get the status "Please manually power up this phone".
No way hitting power/volume buttons. No response, just the red M (motorola logo)
please help!

dsafdie said:
after step 10 get the status "Please manually power up this phone".
No way hitting power/volume buttons. No response, just the red M (motorola logo)
please help!
Click to expand...
Click to collapse
With the phone off press volume down button and powet button at the same time. You will access recovery this way!

SBF File: Link Down...

link down to sbf file
yup link is down please fix

chelesoft said:
SBF File: Link Down...
Click to expand...
Click to collapse
scottman0830 said:
yup link is down please fix
Click to expand...
Click to collapse
Sorry about that, tonight Im uploading the SBF file.
The problem is that my internet conection is not the best and it will take a while!
Tomorow will be on!

New link is up in the first page!

No PC Fast Root!
Is their a root that doesn't include a pc? Or less downloading but I have no usb chord. Is their a hack for my Motorola 2.1.1 Bravo? Im new and id like to learn a trick hack or sumthing. Please get back at me soon...

WhiteBoyFresh said:
Is their a root that doesn't include a pc? Or less downloading but I have no usb chord. Is their a hack for my Motorola 2.1.1 Bravo? Im new and id like to learn a trick hack or sumthing. Please get back at me soon...
Click to expand...
Click to collapse
You can use any microusb cable, from a bb or any other phone.
Why dont you download from the market "sideload enabler for bravo"? If you live in usa and ypu are using at&t you can download it and enable install apps off market. Dont know if that is working with 2.1
Then copy or download gingerbreak 1.20. Apk, install it and click on root.

josuearisty said:
You can use any microusb cable, from a bb or any other phone.
Why dont you download from the market "sideload enabler for bravo"? If you live in usa and ypu are using at&t you can download it and enable install apps off market. Dont know if that is working with 2.1
Then copy or download gingerbreak 1.20. Apk, install it and click on root.
Click to expand...
Click to collapse
+1 -- That's pretty much the only way to do it w\o a pc handy.
I'll upload the sbf to mediafire later this evening. About to go to work.

Realicé el proceso mostrado y solo queda en el logo de Motorola y no puedo ingresar al Stock recovery, ¿que estoy haciendo mal??

deftonesforever said:
Realicé el proceso mostrado y solo queda en el logo de Motorola y no puedo ingresar al Stock recovery, ¿que estoy haciendo mal??
Click to expand...
Click to collapse
If you read very well instructions you will find how to solve that problem.
Entra al stock recovery, apaga el cel y presiona volumen abajo y boton encender, cuando te presente el android presiona ambos botones de volumen y despues wipe data y cache.

And one more mirror sbf, if you suddenly remove a file hosting. - http://cm.aleeyt.com/ (Section Bravo SBF)

[Q] stuck with Stock recovery no usb available

I need advanced help! This is a great challenge!
I used to have CM7 in the defy.
The problem is the phone only powers on when connected to AC power. It does not power up with any computer usb. No idea why the difference.
The battery reads 100% charge.
When the phone is on, I can access stock recovery (not CWM recovery). I did both wipes several times and now I cannot access cm7.
My question is, can I flash any stock update.zip from this stock recovery??
Using RSD Lite is impossible since I cannot power on my phone with the pc. Also, I have downloaded .sbf files, but it looks I need a "update.zip".
thanks in advance for your help!

No podés prender el celular en bootloader mientras lo tenés encufado a la corriente y una vez en el bootloader lo conectas al usb y flasheas tu sbf ?

ArielitoARG said:
No podés prender el celular en bootloader mientras lo tenés encufado a la corriente y una vez en el bootloader lo conectas al usb y flasheas tu sbf ?
Click to expand...
Click to collapse
If I unplug it from the wall, it just turns off again. So no, I cannot try it that way.

you seems to have motherboard problem if your phone is in warranty claim it.
I was having the same issue, i gave my phone yesterday for motherboard replacement.

md.mujeeb said:
you seems to have motherboard problem if your phone is in warranty claim it.
I was having the same issue, i gave my phone yesterday for motherboard replacement.
Click to expand...
Click to collapse
That's what I suspect, but I have installed cyanogenmod and I would like to restore it to stock to avoid trouble, you know...

runaway64 said:
That's what I suspect, but I have installed cyanogenmod and I would like to restore it to stock to avoid trouble, you know...
Click to expand...
Click to collapse
you can do that without connecting USB.
if u have backup ur stock rom restore it through CWM and if you didnt backup
ask other users to create backup file and upload you can put in SD by putting ur SD in other phone or any card reader and put the backup file in CWM folder and restore it

md.mujeeb said:
you can do that without connecting USB.
if u have backup ur stock rom restore it through CWM and if you didnt backup
ask other users to create backup file and upload you can put in SD by putting ur SD in other phone or any card reader and put the backup file in CWM folder and restore it
Click to expand...
Click to collapse
I cannot access the cwm recovery, only the motorola recovery.
I cannot get to access to the stock bootloader either

Huawei P9 Lite (2017) Stuck at Your device is booting now

HI i have a Huawei P9 Lite (2017)
Model: PRA-LX1
Its stuck at the your device has been unlocked and cant be... To learn visit.. Your device is booting now...
Can any one help me?
Or give me the stock firmware(update.app) for PRA-LX1.
Please help.

What tutorial did you use to unlock your bootloader?
What did you do exactly?

just re flash your stock rom by dload using three buttons method

Arsaam said:
just re flash your stock rom by dload using three buttons method
Click to expand...
Click to collapse
I am having the same issue, and absolutely NO combination of power/vol buttons changes the outcome....still just boots to that message. (Nova (P8) lite PRA-LX2 Telkom)
After clicking on an infected MMS (yes, hindsight is wonderful), the phone display started scrambling and turned off (3 days ago). After that, it wouldn't boot up. I have spent the past 3 days working to get it going. Managed to connect to ADB, then scoured the web looking for the correct firmware package. I managed to get a boot.img recovery.img and system.img that would flash but ZERO cust.img files flash. All of these failed with various flashing error messages. Last night, just before this happened, after flashing the above PLUS a TWRP.img file I found, the phone rebooted to the usual splash animation but then went to bootloop to the splash.
I thought "YES....progress!"
Then thru ADB again, I tried to flash a different CUST.img I found and after reboot got stuck at "your device is booting now".......
No recognition in adb....no change is bootup (even with any update.app and au_temp.cfg loaded on sd card)
So.....no, no buttons working, no D/L mode, no fastboot..........nada
Any other assistance would REALLY REALLY be appreciated
Thanks
---------- Post added at 10:23 AM ---------- Previous post was at 09:45 AM ----------
**UPDATE**
After leaving the device on until the battery ran out I pressed the vol up/down and power I rebooted till the very last drop of juice. Then when it had nothing left in the tank I plugged in the charger (not connected to the laptop) and simultaneously pressed all buttons....and it booted up into eRecovery (which incidentally is USELESS), but at least now I can keep trying to flash roms until one day (hopefully before the end of days) I find one that works......

your device is booting now
hola tengo el mismo problema, el telefono queda en "Your device is booting now" y no funcina ninguna combinacion de botones, mejor dicho, haga lo que haga, siempre termina en esa pantalla y el problema mayor es que la PC no lo reconoce, lo conecto a la pc y no aparece conectado.
por favor si alguien sabe de que manera reparar el sistema.
gracias
hello sorry my english is not good I have the same problem, the phone is in "Your device is booting now" and it does not work any combination of buttons, that is to say, whatever it does, it always ends in that screen and the biggest problem is that the PC does not recognize it, I connect to the pc and it does not appear connected.
please if anyone knows how to repair the system.
Thank you

juanchocapital said:
hola tengo el mismo problema, el telefono queda en "Your device is booting now" y no funcina ninguna combinacion de botones, mejor dicho, haga lo que haga, siempre termina en esa pantalla y el problema mayor es que la PC no lo reconoce, lo conecto a la pc y no aparece conectado.
por favor si alguien sabe de que manera reparar el sistema.
gracias
hello sorry my english is not good I have the same problem, the phone is in "Your device is booting now" and it does not work any combination of buttons, that is to say, whatever it does, it always ends in that screen and the biggest problem is that the PC does not recognize it, I connect to the pc and it does not appear connected.
please if anyone knows how to repair the system.
Thank you
Click to expand...
Click to collapse
Hello,
One solution that should work: Leave the phone until it discharge completely, then keep pressing the volume down button then plug the phone in pc (while you are pushing the volume down button). This will boot the phone in fastboot mode. Right then you can flash the recovery with stock recovery or with TWRP (TWRP 3.1.1 should work)
BR,
Alaa.

[SOLVED] Need help with fixing unknown model in LGUP

I flashed the Fulmics ROM on my G6 and could not go back to stock using LGUP. Under Model and Port it shows "Unknown" and "Com 5, Fulmics" preventing me from proceeding.
I, however, managed to flash the stock rom from a zip provided in one of the threads. Still when I connect the phone to computer, LGUP says "Unknown" and "Com 5, Fulmics".
How can I fix this so that I can use LGUP again? (I also tried the Flashtool with no success)
Thanks

Go to
Code:
C:\Program Files (x86)\LG Electronics\LGUP\model\common
paste this file there https://drive.google.com/open?id=0B8K3M8fXJmgzX1hMNTBkZ3p2M1E

Did that before. Didn't make a difference.

backslashV said:
Did that before. Didn't make a difference.
Click to expand...
Click to collapse
Did you install the drivers properly and have you tried using a different USB?

Mavelos said:
Did you install the drivers properly and have you tried using a different USB?
Click to expand...
Click to collapse
Yes. I even tried another computer. It appears that something about this Fulmics rom is hard coded into the phone. The developer of the rom isn't responding so I don't know what else to do.

backslashV said:
Yes. I even tried another computer. It appears that something about this Fulmics rom is hard coded into the phone. The developer of the rom isn't responding so I don't know what else to do.
Click to expand...
Click to collapse
Well, I use Fulmics also and i can say nothing is hardcoded. When you connect your G6, check the device manager on your PC to be sure your phone is detected.

Mavelos said:
Well, I use Fulmics also and i can say nothing is hardcoded. When you connect your G6, check the device manager on your PC to be sure your phone is detected.
Click to expand...
Click to collapse
It is detected. I even tried changing the com port but nothing happened. So when you connect your phone to pc in download mode LGUP recognizes it?

backslashV said:
It is detected. I even tried changing the com port but nothing happened. So when you connect your phone to pc in download mode LGUP recognizes it?
Click to expand...
Click to collapse
yes it does. Have you used LGUP before?

Yes I have. I used it to go back to stock from lineage os.

Good news. I found this guide and it did the trick:
https://forum.xda-developers.com/showthread.php?t=3565508

backslashV said:
Good news. I found this guide and it did the trick:
https://forum.xda-developers.com/showthread.php?t=3565508
Click to expand...
Click to collapse
Hi, how do you solve this issue?
i face same problem.
i even cannot tun off the G6 and cannot enter download mode
when i connect my G6 to PC via uppercut, it says unkonown model and i cannot go on the process.
in the link you put above. we have to enter download mode. how do you do that?
thanks

Just hold volume down and power button at same time to power off.
Sent from my LG-H870 using Tapatalk

i have a same problem with my LG Aristo 2
necesito el dll para flashear Lg Aristo 2 (LM-X210MA)

@ade_k012 I have exactly the same problem you just described. Were you able to resolve?

Yes i have solved it and i can update my g6 to the firmware i want. But sorry, i forgot the steps. It was quite long time ago..

Hola yo lo resolvi usando este tutorial
en el ultimo paso donde tienen que crear el common ddl, no lo hagan, solo descarguen el archivo ddl que proporcionan al principio de este post y lo pegan en la ruta especificada. Lo probe en mi lg h873 y funciono perfecto pude flashear y desbriquear mi telefono que se quedaba en el logo de lg

2017 16GB APX Mode after trying to flash dev image.

So, i guess its totally my fault, because i did not read the instructions to the end.
What i did is basically get into bootloader
and run 3 these commands
fastboot flash staging blob
fastboot flash boot boot.img
fastboot reboot
and not the green led does not turn on and when connected to pc it says APX in the device manager.
Is it totally broken or can i revive it yet? I already read about nvflash but it seems like its not possible at this point.
Please help, don't want to waste another 200 eur on this thing

What image did you flash? nv-recovery-image-shield-atv-7.0.2-dev_rooted? Because I think I flashed it correctly, but it seems like it bricked my device anyway.
mtrixfroml said:
So, i guess its totally my fault, because i did not read the instructions to the end.
What i did is basically get into bootloader
and run 3 these commands
fastboot flash staging blob
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
What do you mean with you didn't read the instructions to the end?
That's the same commands that flash-all.sh / flash-all.bat execute in the beginning. After all those scripts are included in the zip file. HowTo-Flash-Recovery-Image.txt (the instructions that are linked on the download page) has a separate section for "SHIELD UNITS WITH ANDROID MARSHMALLOW OR NEWER" where it skips the reboot part. But that file also mentions stuff like pressing the power button, and the 2017 16 GB version doesn't even have one.
I executed the following commands from the Marshmallow section,
Code:
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot reboot
and I have the same problem that the green LED doesn't turn on anymore. I can't access fastboot either (by holding A & B on a USB keyboard). There's just no graphical output at all. I plugged in a USB cable to my laptop, and neither adb nor fastboot see the Shield TV.

MWin123 said:
What image did you flash? nv-recovery-image-shield-atv-7.0.2-dev_rooted? Because I think I flashed it correctly, but it seems like it bricked my device anyway.
What do you mean with you didn't read the instructions to the end?
That's the same commands that flash-all.sh / flash-all.bat execute in the beginning. After all those scripts are included in the zip file. HowTo-Flash-Recovery-Image.txt (the instructions that are linked on the download page) has a separate section for "SHIELD UNITS WITH ANDROID MARSHMALLOW OR NEWER" where it skips the reboot part. But that file also mentions stuff like pressing the power button, and the 2017 16 GB version doesn't even have one.
I executed the following commands from the Marshmallow section,
Code:
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot reboot
and I have the same problem that the green LED doesn't turn on anymore. I can't access fastboot either (by holding A & B on a USB keyboard). There's just no graphical output at all. I plugged in a USB cable to my laptop, and neither adb nor fastboot see the Shield TV.
Click to expand...
Click to collapse
yeah, thats the one i flashed.
interesting though, i though maybe the rebooting before flashing the recovery was a wrong move, but you did what i would think i would do.
i had this feeling of "do not upgrade or you will regret it" seems i was correct
well at least i did all the backups before attempt, i am not sure what i did wrong then.
But maybe there are some advanced users who can do a tutorial(if there is one) for nvflash and APX mode, because thats the one you get.

after some research, it seems like it could be nVidia fault
at first i thought "maybe i downloaded wrong zip file" so i went to dev site and started checking.
so when you try to download
"Shield Android TV" the link is usually :https://developer.download.nvidia.c...secure/ShieldATVRecoveryImageDevRooted_7.0.1/.....
"Shield TV 2017" goes: https://developer.download.nvidia.c...ownloads/secure/ShieldATVDevRooted2017_7.0.1/......
and when you try to download 7.0.2 for 2017 the link goes: https://developer.download.nvidia.com/assets/mobile/secure/images/shield_atv/7_0_2/
then if you try to download 7.0.2 recovery image the link goes :https://developer.download.nvidia.c...ry-image-shield-atv-2017-7.0.2-dev_rooted.zip
so i am not sure they posted the right image there....
and i think we might have flashed 2015 onto 2017 here

mtrixfroml said:
i had this feeling of "do not upgrade or you will regret it" seems i was correct
Click to expand...
Click to collapse
From what image did you upgrade? I was already on nv-recovery-image-shield-atv-7.0.1-dev_rooted but that OTA upgrade notification for 7.0, that I couldn't even install, kept nagging me.
mtrixfroml said:
after some research, it seems like it could be nVidia fault
Click to expand...
Click to collapse
I do hope so. There are other threads on XDA about boot loops and problems with Oreo, so I hope Nvidia comes up with a fix or at least offers to fix the Shield TVs, that bricked after installing Oreo.
mtrixfroml said:
so i am not sure they posted the right image there....
and i think we might have flashed 2015 onto 2017 here
Click to expand...
Click to collapse
I just checked my download history and fortunately the last three images are still there:.
Code:
http://developer.download.nvidia.com/assets/mobile/secure/images/shield_atv_2017/6_3_0/nv-recovery-image-shield-atv-6.3.0-dev_rooted.zip
https://developer.download.nvidia.com/assets/gameworks/downloads/secure/ShieldATVDevRooted2017_7.0.1/nv-recovery-image-shield-atv-7.0.1-dev_rooted.zip
https://developer.download.nvidia.com/assets/mobile/secure/images/shield_atv/7_0_2/nv-recovery-image-shield-atv-7.0.2-dev_rooted.zip
After that I extracted the system.img from 7.0.1 and 7.0.2 with simg2img, and mounted them.
Truncated build.prop from nv-recovery-image-shield-atv-7.0.1-dev_rooted
Code:
ro.build.id=OPR6.170623.010
ro.build.display.id=OPR6.170623.010.3019194_1155.5338
ro.build.version.incremental=3019194_1155.5338
ro.build.version.sdk=26
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=8.0.0
ro.build.version.security_patch=2018-05-05
ro.build.version.base_os=
ro.build.date=Thu Jun 7 16:13:32 PDT 2018
ro.build.date.utc=1528413212
ro.build.type=user
ro.build.user=NVIDIA
ro.build.host=mobile-u64-731
ro.build.tags=release-keys
ro.build.flavor=darcy-user
ro.product.model=SHIELD Android TV
ro.product.brand=NVIDIA
ro.product.name=darcy
ro.product.device=darcy
Truncated build.prop from nv-recovery-image-shield-atv-7.0.2-dev_rooted
Code:
ro.build.id=OPR6.170623.010
ro.build.display.id=OPR6.170623.010.3019194_1174.8512
ro.build.version.incremental=3019194_1174.8512
ro.build.version.sdk=26
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=8.0.0
ro.build.version.security_patch=2018-05-05
ro.build.version.base_os=
ro.build.date=Fri Jun 22 19:59:46 PDT 2018
ro.build.date.utc=1529722786
ro.build.type=user
ro.build.user=NVIDIA
ro.build.host=mobile-u64-592
ro.build.tags=release-keys
ro.build.flavor=foster_e-user
ro.product.model=SHIELD Android TV
ro.product.brand=NVIDIA
ro.product.name=foster_e
ro.product.device=foster
So, one file says the device name is darcy, and the other says it's foster. It seems like you are right about flashing the 2015 image!
Wow, this sucks. I guess if there's no fix available, it depends on Nvidia admitting that they are at fault and uploaded the wrong image? Because they could just say that we flashed the wrong image, and it's our fault.

i upgraded from 6.3 to 7.0.2 OTA, however i need root access for some apps, so i tried this image

Same here grrrrfrrrdrddfrrrrrrr
Same problem here, ive had new Shield TV 2017 16G for about 1 week, had tried 3 different roms, 620, 630 and 701. I was updating to new developers image when it BRICKED.
Ive had 4 android phones and 2 tv boxes as well as modded gaming consoles. This is the first time its gone all bad.
Ggggrrrrrrrr NVIDIA
Has NVIDIA responded yet and explained why a simple file placement on their servers has bricked numerous clients worldwide ?

Nope, no response yet, atleast not on the forum.
https://forums.geforce.com/default/...dev-image-hard-brick-image-is-for-2015-16gb-/
Guess not enough people has posted about it for them to bother doing anything.

+1. I thought for sure that I downloaded the wrong file or something... but seems like nVidia posted the wrong one and everyone who tries to flash it is ending up with a brick.
Normally I don't even consider this, but would it still be morally wrong to buy another one and return the brick since it was nVidia's fault?! "asking for a friend".

FYI, nVidia has replied here:
https://forums.geforce.com/default/topic/1061747/shield-tv/warning-do-not-use-the-2017-16gb-7-0-2-dev-image-hard-brick-image-is-for-2015-16gb-/2/?offset=17#5831264
Hi everyone, the images have been fixed. For those that are effected by this, I'll PM you so we can RMA the unit. Thanks.
-GeforceDave
Click to expand...
Click to collapse

rossbeck said:
FYI, nVidia has replied here:
https://forums.geforce.com/default/topic/1061747/shield-tv/warning-do-not-use-the-2017-16gb-7-0-2-dev-image-hard-brick-image-is-for-2015-16gb-/2/?offset=17#5831264
Click to expand...
Click to collapse
Unfortunately it seems like the new image they uploaded is still the wrong image as more people are experiencing bricks.
I'd stay away from the dev images until they sort this out.

rossbeck said:
FYI, nVidia has replied here:
https://forums.geforce.com/default/topic/1061747/shield-tv/warning-do-not-use-the-2017-16gb-7-0-2-dev-image-hard-brick-image-is-for-2015-16gb-/2/?offset=17#5831264
Click to expand...
Click to collapse
...except they've now uploaded the wrong firmware (still Foster) with the correct filename.
I've bricked my device. Not happy.

I also restore apx nvidia shield tv 2015 and 2017!
---------- Post added at 11:10 PM ---------- Previous post was at 11:09 PM ----------
https://forum.xda-developers.com/sh...ver-y01-battery-shield-tablet-t3199153/page15

any news how to restore 2017 version?

Same problem
I have the same problem, some solution? one day I left the shield tv on stand-by and when I wanted to use it again I did not turn on anymore, I connected it to the PC on the days to see and it shows an unknown device with the name APX, I wrote to Nvidia and they told me that I could solve it with some instructions that they gave me, to realize them I need the original Joystick Shield and I do not have it, so I could not try, since he told me that with the PC keyboard it was not going to work, they told me they changed it for a new one but the problem is that I live in Argentina and can not advance with the RMA because the device is not sold officially in Latin America, so for now I am a very cute black adornment with green details :/

johandyojeda89 said:
I have the same problem, some solution? one day I left the shield tv on stand-by and when I wanted to use it again I did not turn on anymore, I connected it to the PC on the days to see and it shows an unknown device with the name APX, I wrote to Nvidia and they told me that I could solve it with some instructions that they gave me, to realize them I need the original Joystick Shield and I do not have it, so I could not try, since he told me that with the PC keyboard it was not going to work, they told me they changed it for a new one but the problem is that I live in Argentina and can not advance with the RMA because the device is not sold officially in Latin America, so for now I am a very cute black adornment with green details :/
Click to expand...
Click to collapse
Mate,do you have those instructions given by Nvidia,i have NvidiaShield TV 2015 16GB in APX mode,so any help will bee highly appreciated.
Thanks in advance and cheers

@[email protected] said:
Mate,do you have those instructions given by Nvidia,i have NvidiaShield TV 2015 16GB in APX mode,so any help will bee highly appreciated.
Thanks in advance and cheers
Click to expand...
Click to collapse
Yes take, just traduce is in spanish,
Cristina: A.
1. Desconecte todos los cables de la consola u otros accesorios que haya conectado y deje la unidad encendida durante 2 o 3 minutos.
2. Conecte el cable de alimentación, el controlador a través del cable USB (cableado) y el cable Ethernet a la consola. No conecte el cable HDMI.
3. La unidad se encenderá. Ahora deje la unidad apagada durante 5 minutos y luego presione repetidamente el botón A en el controlador. Continúe presionando el botón A en el controlador por unos segundos.
4. Deje el dispositivo sin el cable HDMI conectado durante 15 a 20 minutos, y luego conecte el cable HDMI.
5. Comprueba si tienes pantalla ahora.
B.
1. Desenchufe usted alimentación eléctrica de la Shield TV.
2. Conecte el mando a la Shield TV a través del cable USB (el puerto más cercano del puerto HDMI)
3. Mientras mantiene usted pulsados los botones A y B al mismo tiempo, enchufe la Shield TV a la alimentación eléctrica.
4. Aquí le aparecerá un menú con más opciones – debe seleccionar Reboot Recovery Kernel
5. Navegue usted utilizando los botones X e Y (Y para ir arriba X para ir abajo) y use esta opción con el botón A.
6. En la pantalla “No Command” usted tiene que pulsar el botón B.
7. Elija usted Wipe Data/Factory reset y confirme (usando los botones X e Y para navegar y A para seleccionar).

Thanks mate, will try those...cheers and all best.

@[email protected] said:
Thanks mate, will try those...cheers and all best.
Click to expand...
Click to collapse
Let me know if u can fix u shield tv, good luck

Hi again,i have to appologize first at i should mention that i have Nvidia Shield TV 2015 16GB....so sorry, anyways can not do anything with those instructions above...
anyway thanks buddy