Related
Hi all,
I think I just toasted my Nexus 7 3G while trying to upgrade the radio/bootloader, but before I toss it in the trash I wanted to see if many someone had any ideas I have yet to try.
Thanks in advanced to anyone who can help me!
The Problem:
Nexus 7 wont boot and is stuck on the Google logo with the unlocked bootloader icon. Cant boot to boot loader using Power + Volume Down. When I do Power + Both Volume Up and Down the screen goes black after showing the Google logo and my PC detects the device but cant find drivers and dont get anything out of fastboot commands. Power + Volume up does nothing.
Because the unlocked bootloader icon I doubt I could get away with sending it back.
What I did:
I was running CM10.1 with Bootloader unlocked
I installed the following 4.3 ROM - http://forum.xda-developers.com/showthread.php?t=2381991
Rebooted <-- Everything was fine but running on older Radio/Bootloader
I started following the following instructions to upgrade radio + bootloader - http://forum.xda-developers.com/showthread.php?t=2175086
I used TWRP to install the Recovery zip
Rebooted to bootloader
Fastboot Flashed bootloader
<<Forgot to Flash Recovery>>
Rebooted <-- everything was working
Rebooted to bootloader
Fastboot Flashed Radio
Rebooted << TWRP launched instead of stock recovery
Rebooted to bootloader
Fastboot Flashed bootloader
Fastboot Flashed recovery << Did not reflash recovery zip first >>
Rebooted <-- seemed ok
Rebooted to bootloader
Fastboot Flashed radio
Rebooted <<No Recovery Showed Up>>
Stuck with Google logo with unlocked bootloader icon and cant get back into bootloader
Hi Mazeri,
I having the same issue as I explained in the original thread.
I was flash the bootloader recovery and radio. Recovery and Bootloader flashes seemed to be ok but the radio flash run ok but when the n7 rebooted got stuck in the google logo.
I have tried all kind of key combinations with no success.
Here is the transcript of my flash commands:
Code:
~/Downloads ⮀ fastboot flash bootloader bootloader-tilapia-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.258s]
writing 'bootloader'...
OKAY [ 4.140s]
finished. total time: 4.399s
~/Downloads ⮀ fastboot flash recovery Recovery_Stock_Tilapia_4.3.img
sending 'recovery' (10240 KB)...
OKAY [ 1.223s]
writing 'recovery'...
OKAY [ 2.453s]
finished. total time: 3.676s
~/Downloads ⮀ fastboot reboot
rebooting...
finished. total time: 0.020s
~/Downloads ⮀ fastboot devices
015d2XXXXXX0d fastboot
~/Downloads ⮀ fastboot flash radio radio-tilapia-1231_0.18.0_0409.img
sending 'radio' (16384 KB)...
OKAY [ 1.943s]
writing 'radio'...
OKAY [ 4.760s]
finished. total time: 6.702s
~/Downloads ⮀ fastboot reboot
rebooting...
finished. total time: 0.020s
~/Downloads ⮀ fastboot devices
~/Downloads ⮀ fastboot devices
How do you detect the device in your pc? What command are you running?
Im on a mac os x. If I do a fastboot reboot recovery, I get a 'waiting for device' message but there is no information for any combination of key presses.
If you are on a PC, have you tried any toolkit? I've read in a couple of thread that Wug's toolkit have worked to unbrick some devices with issues with the bootloader.
All I did was hold power until the screen goes black, then press and hold both volume up and down. The Google logo shows up and then the screen goes black. Windows then detects a device... but is unable to install a driver for it and it shows up as an unknown device.
Mazeri said:
All I did was hold power until the screen goes black, then press and hold both volume up and down. The Google logo shows up and then the screen goes black. Windows then detects a device... but is unable to install a driver for it and it shows up as an unknown device.
Click to expand...
Click to collapse
Also, I tried with the Nexus 7 tool kit and it failed to detect ADB. Fastboot also does not see the device.
Wug Toolkit also does not seem to work as it requires ADB or Fastboot to be working.
If I could get the device driver to kick in that might work... but something we did while flashs is making the device show up without details such as no device name and no mfg info... so Windows just shuts it down and calls it unknown.
I've got the same prolem Wug or Nexus toolkits cannot detect my N7 .... hix
I just flash the radio and my N7 stuck at Google logo....
amakaru said:
I've got the same prolem Wug or Nexus toolkits cannot detect my N7 .... hix
I just flash the radio and my N7 stuck at Google logo....
Click to expand...
Click to collapse
Maybe we should check what do ourt n7's have in common... It's strange that the flash worked for other n7 but not for ours.
Maybe that radio file is intended for certain devices (?).
Mine is a EU Nexus7 3G bought in early January this year. I guest is in warranty yet but because of the unlock icon in the start screen, the warranty is void
But I think this is not a problem related with the bootloader since the google logo appears and the unlock icon (so the n7 bootloader detects that it is unlock).
The flashing worked with the bootloader but it crashed when the radio was flashed for the three of us, so it is something related with the baseband. The OS installed should not be related since the bootloader and radio baseband are independent from the OS (Maybe you can get a soft brick, stuck in the colored X logo but bootloader should work).
I'm going to try to work finding a solution... but personally Im not feeling very optimistic
Now when I use three button (hold down power & vol + & vol - ) my computer show in device manager : "Android devices/ASUS Transformer APX Interfaces"
Sorry to say, but unless you can get your devices to fastboot mode, I think you're out of luck. It sounds like it doesn't get completely into the bootloader, which is problematic.
It was discussed a while back, and APX mode is a programming mode, but we lack the proper drivers and software to be able to recover anything on the N7 from that. Sorry.
I have a US Nexus 7 3G, got it right when they went on sale.
ameinild said:
Sorry to say, but unless you can get your devices to fastboot mode, I think you're out of luck. It sounds like it doesn't get completely into the bootloader, which is problematic.
It was discussed a while back, and APX mode is a programming mode, but we lack the proper drivers and software to be able to recover anything on the N7 from that. Sorry.
Click to expand...
Click to collapse
Bummer news :'( but I was expecting as much. If we don't find a fix, can we replace the main board to fix or is this problem beyond that point? Don't think selling a bricked device is worth it unless we have 0 options.
adb/fastboot commands
Another one bites the dust.
I should have followed the thread more closely. One of the steps (noticed this after the fact) is to "fastboot reboot", unfortunately this does not reboot the bootloader.
I should've noticed this yesterday after the initial fastboot reboot when I flashed the recovery image. Anywho, I believe the last step after flashing the radio should be "fastboot reboot-bootloader" not "fastboot reboot"? Maybe someone with more adb/fastboot experience could verify? Thanks.
bootloop after radio update!!!
my nexus 3g is from poland!!!
please, help!!!
Still no update guys, and no luck also
Right now I am thinking we will need to replace the main board, but I want to get that confirmed before buying a replacement.
I think that radio and bootloader must flashed first before upgrade to 4.3 . I do that with my N7 3G and now it works fine
my radiobands for device is for Poland Region
i hate myself
the only way is to flash radiomodule via APX, i have installed drivers, but have not .cfg and other parameters to flash Nvidia chip.
sambistt said:
my radiobands for device is for Poland Region
i hate myself
the only way is to flash radiomodule via APX, i have installed drivers, but have not .cfg and other parameters to flash Nvidia chip.
Click to expand...
Click to collapse
There isn't a place to know the parameters or whatever we need?
What can we change physically (motherboard, or any specific chip) to solve this problem?
If we return it to Asus or Google can it be repeaired? How much does it cost? Assuming the warranty is void because of the unlock icon..
---------- Post added at 01:25 PM ---------- Previous post was at 12:31 PM ----------
eternal70 said:
I think that radio and bootloader must flashed first before upgrade to 4.3 . I do that with my N7 3G and now it works fine
Click to expand...
Click to collapse
That was not the reason. I didnt upgrade to 4.3 before flashing the bootloader and the radio and I got the same result. The bootloader is not connected to the OS, but the OS is connected to the bootloader. I mean that it doesnt matter the OS in order the bootloader to run. But maybe it is possible to have the n7 soft bricked if the bootloader installed is not compatible with your OS.
Softbricked is when you are stuck in the OS logo (in case of the stock version is the colored X). This is very easy to fix, just runt in fastboot mode and flash the new OS and that's all. Everyone has experienced this situation eventually.
Our n7 are hard bricked. This mean that the bootloader or the radio (or both) are corrupted or bad flashed. In our case is the radio band (since we can see the google logo that is the bootloader). The weird thing is that while the bootloader is running (we can see the google logo and the unlock icon), we can't enter in the fastboot mode. Since we cant put the n7 in fastboot mode then we cannot flash anything (not os, not radio, not bootloader).
For now, the only way to flash bootloader and radio chip of the n7 is via APX. the problem is the APX configuration to flash the nvidia chips has not been released (as far as I understand, correct me if im wrong), so there is no way to know how to do it.
The only hope is changing this chips physically. Because everything is integrated, that means to change the motherboard, my guess (you can find tutorials in iFixit). What's the downside? The motherboard is basically the N7 so if you change it you change everything (the storage, the 3G, etc). You can check for motherboards in ebay easily just with search: Nexus 7 Motherboards. Range price varies from 20$ for 8GB to 140$ for 3G . Another question is if we can put a 8GB or 16 GB motherboards in our 3G N7, but I think so... it would not be a problem.
Everything I said a personal opinions and I can be wrong, so correct me if I'm wrong.
I have to say, I still have a very very very little hope that could be a fix for this, since we can see the google logo. But I'm thinking in ordering a 8G motherboard just in case
i`m thinking to give my n7 3g to my brother for parts and never buy tablet anymore, only ultrabooks.
My brother had the same problem and he managed to flash 4.2.1 with the nexus 7 toolkit.
The device got back to life again and then took the 4.3 OTA.
Sent from my Galaxy Nexus using xda app-developers app
There isn't a place to know the parameters or whatever we need?
Click to expand...
Click to collapse
no and never`ll be
easyflash only for transformer pad
i think to easy buy new nexus 7 2 gen or never buy tablet anymore
347 $ in trash
the new PS4 console is selling ~ 399$ - i think, it better to purchase new console that tablet
---------- Post added at 01:52 PM ---------- Previous post was at 01:44 PM ----------
DomieMic65 said:
My brother had the same problem and he managed to flash 4.2.1 with the nexus 7 toolkit.
The device got back to life again and then took the 4.3 OTA.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
really? your brother flashed radio module?
sambistt said:
no and never`ll be
easyflash only for transformer pad
i think to easy buy new nexus 7 2 gen or never buy tablet anymore
347 $ in trash
the new PS4 console is selling ~ 399$ - i think, it better to purchase new console that tablet
---------- Post added at 01:52 PM ---------- Previous post was at 01:44 PM ----------
really? your brother flashed radio module?
Click to expand...
Click to collapse
I don't know. Sorry.
I just mentioned this in case it may give you a clue.
I will ask and report.
Sent from my Galaxy Nexus using xda app-developers app
hi,
before updating to 4.3 via OTA i was rooted via chinese method and had problems with my wifi, i decided to wipe my note using fastboot -w, to see if it would fix the wifi issue, afterwards it booted up and i installed the 4.3 OTA, i think it installed but my device went into a bootloop and i can not get ADB or Fastboot to recognise it (I know the drivers work, they recognise my LG G2), the only device showing up in device manager is APX. I did some googling and found that its Nvidia low level recovery system. Is there any way to get my TN7 out of APX or do I wait until Nvidia release the relevant blobs? (Am I right in saying that Nvflash doesnt support Tegra 4 yet?) Can you guys think of any solutions? I am happy to try experimental, pre-alpha stuff!
Thanks in advance,
Aliaksei
aliaksei said:
hi,
before updating to 4.3 via OTA i was rooted via chinese method and had problems with my wifi, i decided to wipe my note using fastboot -w, to see if it would fix the wifi issue, afterwards it booted up and i installed the 4.3 OTA, i think it installed but my device went into a bootloop and i can not get ADB or Fastboot to recognise it (I know the drivers work, they recognise my LG G2), the only device showing up in device manager is APX. I did some googling and found that its Nvidia low level recovery system. Is there any way to get my TN7 out of APX or do I wait until Nvidia release the relevant blobs? (Am I right in saying that Nvflash doesnt support Tegra 4 yet?) Can you guys think of any solutions? I am happy to try experimental, pre-alpha stuff!
Thanks in advance,
Aliaksei
Click to expand...
Click to collapse
Sorry to say that no one has yet got NvFlash working with Tegra 4 SoC, bar in-house developers and wholesalers.
If you can't get the device into fastboot then your only alternative is to return the tablet on warranty since you are not getting a proper bootloader which is a sign of an early released unlocked tablet where legally there was no hindrance to tinkering. To get fastboot try;
Starting up the device with the POWER-BUTTON + TOP VOLUME-BUTTON held down at same time. The device will boot and as soon as you see the logo, then release only the POWER-BUTTON so that the device doesn't do a unwanted restart on you. What you should be trying to archive with this is get to a menu based bootloader if you have one. There, you should be able to toogle on fastboot and recover the device.
I hope that helps.
If I return it on warranty, will they be able to see that it was rooted, invalidating my warranty?
Sent from my LG-D802 using xda app-developers app
Hello this is my first post. I have searched the threads and internet for answers but I have not been able to find a solution.
I have been customizing my phones since the days of baked black bean on my galaxy S1, but I am no expert at this stuff. Until about a week ago, I was happily running RR on the OPO (great ROM) but it has gotten a bit slow so I figured it was time to get a OP5.
When I boot into fastboot, my device is recognized with the command fastboot devices. My phone showed the following:
fastboot mode
product_name - QC_Refernce_Phone
VARIANT - MSM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - c7ccda2
SECURE BOOT - yes
DEVICE STATE - locked
When I ran fastboot oem unlock, CMD prompt shows FAILED, however, the option to unlock the bootloader shows up on the OP5. I go through the process and wipe data. My phone now shows that it is unlocked, and I go into developer options to get advanced reboot/USB debugging/verify OEM unlock is still enabled. When I go back to fastboot, I am unable to flash TWRP. I have now seen a number of errors, usually:
FAILED (remote: Requested download size is more than max allowed) or target did not report max download size, or command write failed (no error). I have tried installing 4 different versions of ADB/fastboot from different sources, and I have tried TWRP cheeseburger 46, 58, and 62. I have also tried two different USB ports and 4 different USB drivers.
Does anyone know what could cause these issues or how to get TWRP installed? Any help would be much appreciated. I really want to get rooted and get substratum running.
hmm
did you type fastboot devices to check that u got connection ? do you have another pc to try ? another usb port
edit: also try disable developer option and aplly it again with oem unlock tapp
EDIT2: if you cant still get it work you can try
Advanced settings -> Backup & reset -> Reset all settings and after that unlock bootloader
I was able to solve this by using a friend's laptop and installing the drivers and abd. Worked like a charm and I was able to flash magisk for root.
For anyone else having this issue, try another pc if you can. I'm guessing this was either an issue with adb on my machine or a problem with the device drivers.
bro do u find solutions for this
I found an actual fix for this problem. Basically I had to download Large Address Allocation Tool (LAA) which you can find online. I would link to it but I do not have the website handy.
I found this solution after soft bricking my phone by installing Oreo (I don't suggest using VPN to pretend you are in Canada. Just run the beta or wait for the US release).
Essentially, you just need to run this tool on your adb.exe. From what I understand, the issue is just that adb is not using enough RAM. I think you'll need to be running Windows 7 64bit with at least 4GB RAM. I hope this info can help someone else!
jsnell said:
I was able to solve this by using a friend's laptop and installing the drivers and abd. Worked like a charm and I was able to flash magisk for root.
For anyone else having this issue, try another pc if you can. I'm guessing this was either an issue with adb on my machine or a problem with the device drivers.
Click to expand...
Click to collapse
Ever since i ditched windows and went with ubuntu i have not had one single driver issue, not one single hiccup on anything. It's been two months.. I'm never going back. lol. Every time I use adb and or fastboot it always works.
I got an update notification. And clicked to update.
When restarted the phone, the phone went to die. I could not start my phone.
I tried these:
1) Kept my fingers on VOL Down and POWER buttons for 2 minutes (even more), but NO USE.
2) Tried to open screws but my screwdrivers could not fit for them.
I bought it 3 months back, but in Flipkat and no service center near me. Any solution for it?
What update did you flash, and what OS were you on?
What device did you have, and was it charged up when you accepted the update?
echo92 said:
What update did you flash, and what OS were you on?
What device did you have, and was it charged up when you accepted the update?
Click to expand...
Click to collapse
* I got June update I guess.
* My device is moto g4 plus 1643 model India variant.
* When I connected charger, LED light blinks that was near Fingerprint zone.
* Tried device manager software, it helped nothing.
* Tried to put my fingers on POWER and VOLUME DOWN buttons, but no use.
Really disappointed as it was a gift from my brother.
TrueUniue said:
* I got June update I guess.
* My device is moto g4 plus 1643 model India variant.
* When I connected charger, LED light blinks that was near Fingerprint zone.
* Tried device manager software, it helped nothing.
* Tried to put my fingers on POWER and VOLUME DOWN buttons, but no use.
Really disappointed as it was a gift from my brother.
Click to expand...
Click to collapse
Just to clarify - you installed the update and then rebooted or just accepted the notification to begin the update (and then rebooted, after which your device failed to boot)?
Did you have TWRP/root and were you on the stock ROM prior to flashing (or a custom stock ROM)?
echo92 said:
Just to clarify - you installed the update and then rebooted or just accepted the notification to begin the update (and then rebooted, after which your device failed to boot)?
Did you have TWRP/root and were you on the stock ROM prior to flashing (or a custom stock ROM)?
Click to expand...
Click to collapse
The update was downloaded, when installing it went blank and never started up.
* I have TWRP custom ROM before it.
TrueUniue said:
The update was downloaded, when installing it went blank and never started up.
* I have TWRP custom ROM before it.
Click to expand...
Click to collapse
Did you flash a stock recovery before attempting to update? Having TWRP might be causing the hang; try these suggestions from abhi212b https://forum.xda-developers.com/mo...date-build-t3584982/post72114657#post72114657
Can I ask which custom ROM you were on? You won't be able to flash stock OTA updates with TWRP/customised stock ROM.
echo92 said:
Did you flash a stock recovery before attempting to update? Having TWRP might be causing the hang; try these suggestions from abhi212b https://forum.xda-developers.com/mo...date-build-t3584982/post72114657#post72114657
Can I ask which custom ROM you were on? You won't be able to flash stock OTA updates with TWRP/customised stock ROM.
Click to expand...
Click to collapse
My phone is in blank screen. NO start up. No fastboot or recovery mode available. Only light blinks when charger is connected. Then how can I do your suggestions? You didn't understand my problem.
TrueUniue said:
My phone is in blank screen. NO start up. No fastboot or recovery mode available. Only light blinks when charger is connected. Then how can I do your suggestions? You didn't understand my problem.
Click to expand...
Click to collapse
My apologies - I looked through your post history and was wondering if the TWRP/rooting performed previously might have prevented your device from booting.
What is your device detected as when you plug it into your computer, is it Moto G4 or is it Qualcomm HS-USB- 9008 (or similar)?
echo92 said:
My apologies - I looked through your post history and was wondering if the TWRP/rooting performed previously might have prevented your device from booting.
What is your device detected as when you plug it into your computer, is it Moto G4 or is it Qualcomm HS-USB- 9008 (or similar)?
Click to expand...
Click to collapse
When I connected to laptop, it took detected and installed port Qualcomm HS-USB- 9008. But I didn't see special drive detecting beside my other drivers.
TrueUniue said:
When I connected to laptop, it took detected and installed port Qualcomm HS-USB- 9008. But I didn't see special drive detecting beside my other drivers.
Click to expand...
Click to collapse
Right, 2 things to try:
1) Try holding the power button down for 2-3 minutes, this may force a hard restart which might break your device out of whatever state it's in.
2)If 1 doesn't work, you may wish to look into trying a blank-flash (here: https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016 or here: https://forum.xda-developers.com/showpost.php?p=71405834&postcount=23 ) Depending on what happened with the update, you might be lucky. You may wish to have a look at these blank-flashes too, heed the warning: https://forum.xda-developers.com/showpost.php?p=73151763&postcount=6
3)If 1 and 2 don't work, then unfortunately you'll have to locate a repair centre (or try to find a Motorola service centre) that you could send the device to, or ask Flipkart for assistance. Alternatively, save up for another device. Currently, we don't have another option, though it appears that a member is trying to patch a blankflash for the new update: https://forum.xda-developers.com/showpost.php?p=73152979&postcount=21
echo92 said:
Right, 2 things to try:
1) Try holding the power button down for 2-3 minutes, this may force a hard restart which might break your device out of whatever state it's in.
2)If 1 doesn't work, you may wish to look into trying a blank-flash (here: https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016 or here: https://forum.xda-developers.com/showpost.php?p=71405834&postcount=23 ) Depending on what happened with the update, you might be lucky. You may wish to have a look at these blank-flashes too, heed the warning: https://forum.xda-developers.com/showpost.php?p=73151763&postcount=6
3)If 1 and 2 don't work, then unfortunately you'll have to locate a repair centre (or try to find a Motorola service centre) that you could send the device to, or ask Flipkart for assistance. Alternatively, save up for another device. Currently, we don't have another option, though it appears that a member is trying to patch a blankflash for the new update: https://forum.xda-developers.com/showpost.php?p=73152979&postcount=21
Click to expand...
Click to collapse
I got this when I clicked blankflash:
C:\Users\*****\Downloads\Compressed\blankflash1\blankflash>.\qboot.
exe blank-flash
Motorola qboot utility version 3.40
[ 0.000] Opening device: \\.\COM3
[ 0.002] Detecting device
[ 4.009] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.009] Check qboot_log.txt for more details
[ 4.010] Total time: 4.010s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()
->IO error
C:\Users\*****\Downloads\Compressed\blankflash1\blankflash>pause
Press any key to continue . . .
I think, if any one can find new blankflash, I can fix my phone. I think those blankflases are old. I'm on April update, and failed when I tried for June update.
Hi I am having issue with a device which I bought and can not return. The nvidia shield pro 500GB is stuck in fastboot mode.
Every time I turn the device off and on all I get is the options you get in fast boot.
I have tried to boot recovery kernel, force recovery etc and I just get the same screen again.
I have tried to unlock the device to see if I can flash with factory rom but having no luck. When trying to unlock using ADB Fastboot I get a error on screen eventually saying can not unlock.
Error says (bootloader) Device cannot be unlocked.
OKAY [41.012s]
Finished. Total time 41.012s
I can see the device when I run the command Fastboot devices.
Any suggestions would be great. Thank you
wax_786 said:
Hi I am having issue with a device which I bought and can not return. The nvidia shield pro 500GB is stuck in fastboot mode.
Every time I turn the device off and on all I get is the options you get in fast boot.
I have tried to boot recovery kernel, force recovery etc and I just get the same screen again.
I have tried to unlock the device to see if I can flash with factory rom but having no luck. When trying to unlock using ADB Fastboot I get a error on screen eventually saying can not unlock.
Error says (bootloader) Device cannot be unlocked.
OKAY [41.012s]
Finished. Total time 41.012s
I can see the device when I run the command Fastboot devices.
Any suggestions would be great. Thank you
Click to expand...
Click to collapse
Please be more specific, exactly what did you do before it got stuck in fastboot and what were or are you trying to do
I bought the nvidia shield from a auction so I haven't a clue what was done before. When I switched it on it would go straight to the boot menu and no further.
Ideally I just want to get the device to a state where it boots into the android software.
wax_786 said:
I bought the nvidia shield from a auction so I haven't a clue what was done before. When I switched it on it would go straight to the boot menu and no further.
Ideally I just want to get the device to a state where it boots into the android software.
Click to expand...
Click to collapse
my guess is someone messed it up previously and you should get the Nvidia 5.2 version flash that and then let it update to 6.0
Is it possible to flash without unlocking the bootloader?
wax_786 said:
Is it possible to flash without unlocking the bootloader?
Click to expand...
Click to collapse
wow sorry about that yeah bootloader needs to be unlocked, so you tried fastboot oem unlock and you get that error?
Yes that's the error I get when trying to unlock bootloader. That's what I need help with.
wax_786 said:
Yes that's the error I get when trying to unlock bootloader. That's what I need help with.
Click to expand...
Click to collapse
did you follow the tutorial? are your drivers updated? do you see shield in your device manager on your pc?
I followed a tutorial, I've done it before so kinda have a idea.
The device does show up in device manager, shows as android bootloader interface.
Although not sure how upto date the drivers are.
wax_786 said:
I followed a tutorial, I've done it before so kinda have a idea.
The device does show up in device manager, shows as android bootloader interface.
Although not sure how upto date the drivers are.
Click to expand...
Click to collapse
I have seen a couple people use windroid to unlock their bootloader when they ran into problems but I have no experience in that, it really sounds like the os is gone< i have had similar experience where I could get into recovery, but it would do absolutely nothing no matter what I tried, I had to rma . I know nvidia ssays if the device shows up as apx then its hardware failure
I'll give windroid a try, when you did a rma did nivida not question what had happened ?
Is there anyway I could clone another a hard drive from another nvidia with os on the drive?
wax_786 said:
I'll give windroid a try, when you did a rma did nivida not question what had happened ?
Is there anyway I could clone another a hard drive from another nvidia with os on the drive?
Click to expand...
Click to collapse
No they dont ask what happened you just tell them the problem and they run you through some steps depending on the problem and if that doesnt work they start the rma process, You can clone another drive but from what I hear netflix thats installed on the shield wont work because its console specific I believe
Looks like windroid didn't work either.
Will speak to nvidia at some point next week to see what they say. Thank you for your help & reply much appreciated.
wax_786 said:
Looks like windroid didn't work either.
Will speak to nvidia at some point next week to see what they say. Thank you for your help & reply much appreciated.
Click to expand...
Click to collapse
Welcome, sorry I couldnt do more
That's fine you gave me some advise I go away with.
One last thing could this work? I'm not too fussed about Netflix.
https://www.google.co.uk/amp/s/andr...-hard-drive-with-a-speedier-ssd-20160720/amp/
wax_786 said:
That's fine you gave me some advise I go away with.
One last thing could this work? I'm not too fussed about Netflix.
https://www.google.co.uk/amp/s/andr...-hard-drive-with-a-speedier-ssd-20160720/amp/
Click to expand...
Click to collapse
Yes it does, here is the thread https://forum.xda-developers.com/shield-tv/development/nvidia-shield-tv-ssd-t3402580