I just got Google's official USB Type-C to USB A cable today. Weirdly, upon plugging my N5X into my computer for the first time, the file system did not come up as expected. What show as folders locally on my device, show up as binary files in Nautilus on Ubuntu 15.10. Never seen this behaviour before in any Android device. Using an MTP connection.
Screenshot attached helps to explain the issue a little bit better.
Additionally:
Code:
$ pwd
/run/user/1000/gvfs/mtp:host=%5Busb%3A001%2C014%5D/Internal storage
$ ls -la
total 29
drwx------ 1 sec sec 0 Dec 31 1969 .
dr-x------ 1 sec sec 0 Dec 31 1969 ..
drwx------ 1 sec sec 0 Jan 29 1970 Alarms
drwx------ 1 sec sec 0 Nov 21 16:38 Android
-rw------- 1 sec sec 4096 Nov 21 20:40 APG
-rw------- 1 sec sec 4096 Nov 21 20:40 data
drwx------ 1 sec sec 0 Nov 21 20:54 DCIM
drwx------ 1 sec sec 0 Nov 21 20:41 Download
-rw------- 1 sec sec 4096 Nov 21 20:40 Kik
drwx------ 1 sec sec 0 Jan 29 1970 Movies
drwx------ 1 sec sec 0 Jan 29 1970 Music
-rw------- 1 sec sec 11 Nov 21 20:38 .nds
drwx------ 1 sec sec 0 Jan 29 1970 Notifications
drwx------ 1 sec sec 0 Nov 21 20:30 owncloud
-rw------- 1 sec sec 63 Nov 21 20:46 pia vpn.txt
drwx------ 1 sec sec 0 Nov 21 20:45 Pictures
drwx------ 1 sec sec 0 Jan 29 1970 Podcasts
drwx------ 1 sec sec 0 Jan 29 1970 Ringtones
-rw------- 1 sec sec 4096 Nov 21 20:40 .secure
-rw------- 1 sec sec 4096 Nov 21 20:40 Snapseed
-rw------- 1 sec sec 8192 Nov 21 20:40 Tumblr
drwx------ 1 sec sec 0 Nov 21 21:41 yahoo
Notice that `APG`, `data`, `Kik`, `.secure`, `Snapseed`, and `Tumblr` all show as -rw------- files and not as regular directories. What gives? Anyone have a similar problem / solution?
Saw the same thing with that version of Ubuntu. It is known to have issues with android
zelendel said:
Saw the same thing with that version of Ubuntu. It is known to have issues with android
Click to expand...
Click to collapse
Strange. I had no issues with my old Moto G (on 5.1.x) on the same machine running 15.10. Do you have any more information? Can you point to a source that says this is true? 15.10 is a stable release and I can't think of a reason why a broken version of gvfs would be shipped with it.
Narwhal73 said:
Strange. I had no issues with my old Moto G (on 5.1.x) on the same machine running 15.10. Do you have any more information? Can you point to a source that says this is true? 15.10 is a stable release and I can't think of a reason why a broken version of gvfs would be shipped with it.
Click to expand...
Click to collapse
2 very different devices and very different OS versions. 15.10 has its own issues and many android developers have advised against using it. Even Google developers don't advise it.
You can have a look in the Ubuntu forums. I came across it awhile ago when android M first came out.
zelendel said:
2 very different devices and very different OS versions. 15.10 has its own issues and many android developers have advised against using it. Even Google developers don't advise it.
You can have a look in the Ubuntu forums. I came across it awhile ago when android M first came out.
Click to expand...
Click to collapse
I've done a lot of searching through the Ubuntu forums as you've mentioned and come up with nothing. I asked this same question on AskUbuntu, but no one else seems to know what's going on...
I have however determined it's not an issue with Ubuntu. I tested on a recent Arch Linux installation, and I got my hands on a Windows computer to test the issue, and its the same thing. Those folders still show up as files over MTP, which is really annoying and kind of concerning. Any leads on what I can do to fix it?
Narwhal73 said:
I have however determined it's not an issue with Ubuntu. I tested on a recent Arch Linux installation, and I got my hands on a Windows computer to test the issue, and its the same thing. Those folders still show up as files over MTP, which is really annoying and kind of concerning. Any leads on what I can do to fix it?
Click to expand...
Click to collapse
So it was definitely an issue with the Android file system. No idea what, why or how it happened, but obviously something went funky with some the folders on my device (still really curious as to what though).
Issue was fixed by painstakingly recreating the folder structures and moving files via Amaze File Manager from the old [corrupt?] folders to the new ones on my Nexus 5X. Hard problem to explain, easy enough to solve though I guess.
Thankfully data integrity was kept and I've yet to encounter any further issues with MTP on Ubuntu 15.10, Arch Linux, nor Windows 8.1. :good:
@Narwhal73. Just experienced the same folder problem. Occurred when Titanium Backup created it's backup folder. It was normal with ES or Root Explorer on the device, but on the computer (USB/MTB) it was a 4K file. Deleted it on the device, created the backup folder on the computer, ran TiBu and it's all normal now. Some crazy stuff going on. (Win7, 5X 6.0.1 Pure Nexus)
Update 1/18/16: (Found this -possible- solution on reddit)
Figured it out. Just in case anyone else is having the same problem, what you need to do is go to Settings>Apps> click on the three dots and "show system apps". Then delete the data from the External Storage and Media Storage apps. After a restart, everything should show up again once you are plugged in.
Click to expand...
Click to collapse
Mesmurized said:
@Narwhal73. Just experienced the same folder problem. Occurred when Titanium Backup created it's backup folder. It was normal with ES or Root Explorer on the device, but on the computer (USB/MTB) it was a 4K file. Deleted it on the device, created the backup folder on the computer, ran TiBu and it's all normal now. Some crazy stuff going on. (Win7, 5X 6.0.1 Pure Nexus)
Click to expand...
Click to collapse
I wish I knew of a way to reliably reproduce this issue... This happened for me on the stock ROM, but if it's happening on Pure Nexus too then it's definitely an issue in AOSP. A bug report should probably be made. I'll get around to that sometime soon, though I don't know how useful the report would be without instructions to reproduce it. :\
Related
I had to wipe my misc partition, and I've lost the WiFi and Bluetooth MAC addresses. It generates new ones in cache, but every time I wipe cache they're reset. I need a clean file, preferably from a tab running 20B, so I can put my own MACs in it. Without a sample, I don't know the necessary offsets/format. Can anyone get this for me? It zips down to only 16KB.
Thanks in advance.
cpurick said:
I had to wipe my misc partition, and I've lost the WiFi and Bluetooth MAC addresses. It generates new ones in cache, but every time I wipe cache they're reset. I need a clean file, preferably from a tab running 20B, so I can put my own MACs in it. Without a sample, I don't know the necessary offsets/format. Can anyone get this for me? It zips down to only 16KB.
Thanks in advance.
Click to expand...
Click to collapse
Not even going to ask why you needed to blank it... :silly:
This is from 20d.
Wifi is at offset 3000 I marked it by setting it to 12 34 56 78 9A BC enter MAC as it appears in hex
Bluetooth is at offset 4000 I marked it by setting it to 12 34 56 78 9A BC also, enter MAC as it appears in hex
The tablet serial is at offset A800 I marked it by setting to 12 34 56 78 9A BC DE F1 23 45 67 89 AB CD, enter it as text as it appears on back of tablet
The tablet CSN is at offset F000. I marked it by 00 the last 7 numbers. Enter as text in format LG0000600000000. No idea where to get for yours.
Wonder what offset 2000 is? looks like CB51S131024000XXX
Thanks, can't tell you how grateful I am.
I was applying various updates to rooted v20B when the tab dropped out to TWRP and would not boot system. Autoprime felt that it was trying to apply OTA, and suggested wiping misc and fota. That recovered the tab, but we didn't count on these other problems. It now comes up after every reboot with new S/N, MAC and Bluetooth addresses.
Hopefully you've given me just enough to get it back online. Again, thank you!
Update: CSN is on the package, a second bar code above the SN. Thankfully I still have my box.
Yours has something about blown qfuse. Since you have 20d and mine's been working okay without that string, I took it out.
That value at offset 2000, CB51S131024000XXX, is actually in there twice. It's also at the end of the large block that begins at 10000.
The device is booting and the addresses are holding. Serial number not displaying correctly in the device, but looks right in the editor. Don't know if there's something else in the file that's supposed to match it.
Do you figure any of these values are part of DRM?
Yeah, DRM is toast. Can't play the preload 4K vids anymore. Oh well.
Hi, time is urgent here because the longer I wait more of my files go.
I missed class and have been spending around 10 hours today nonstop didn't even eat.
This is for my AT&T Samsung Galaxy Note 3
I was following this guide
http://forum.xda-developers.com/gal...de-internal-memory-data-recovery-yes-t1994705
I am stuck at the part where I have to enter
nc 127.0.0.1 5555 | pv -i 0.5 > mmcblk0p12.raw
(My memory block is mmcblk0p25 I believe)
I entered that and NOTHING happens at all. For some reason pv wasn't automatically in there as well as nc. I manually took nc from the netcat folder and put it in the bin. Then I download pv from sourceforge and put it in the bin(maybe this is what I did wrong).
I am stuck at this point and really sad all my photos are gone(I think I accidentally deleted the camera folder in the gallery).
Thanks for any help.
UPDATE: So I got past that now my problem is that It says 0 Bytes.
Hey, are you guys fine?
So, I've tried to install the new update to Xperia S (lt26i) using the aosp_marshmallow_r2.zip, but something was wrong. I tried to use the ADB Shell commmands but how I was in the dark cause I don't know how to use, I made some "d" "line(14 for exemple)" but I dont know how, after this, my cellphone dont turn it on anymore. Just, when I open Flashtool, shows "device connected with USB debugging off", but the led doesn't turn on too, and the steps to install kernels or roms aren't working. When I do the steps, and the last one is "connect the phone with the button "x" pressed", the only thing that happens is that the phone show: device connected with USB debugging off, nothing more. :crying:
Takamasu said:
Hey, are you guys fine?
So, I've tried to install the new update to Xperia S (lt26i) using the aosp_marshmallow_r2.zip, but something was wrong. I tried to use the ADB Shell commmands but how I was in the dark cause I don't know how to use, I made some "d" "line(14 for exemple)" but I dont know how, after this, my cellphone dont turn it on anymore. Just, when I open Flashtool, shows "device connected with USB debugging off", but the led doesn't turn on too, and the steps to install kernels or roms aren't working. When I do the steps, and the last one is "connect the phone with the button "x" pressed", the only thing that happens is that the phone show: device connected with USB debugging off, nothing more. :crying:
Click to expand...
Click to collapse
What did you do?
Repartition?
Are you sure you delete p14 or p1?
Your device turn off it self or you restsrt it?
darknessmc said:
What did you do?
Repartition?
Are you sure you delete p14 or p1?
Your device turn off it self or you restsrt it?
Click to expand...
Click to collapse
Yes, I deleted p14, p13 and p12, after this I try to create the new partition, but I didn't know how to, so I just uploaded the files (aosp_marshmallow_r2.zip and the gapps.zip) and made the instalation by TWRP.
Takamasu said:
Yes, I deleted p14, p13 and p12, after this I try to create the new partition, but I didn't know how to, so I just uploaded the files (aosp_marshmallow_r2.zip and the gapps.zip) and made the instalation by TWRP.
Click to expand...
Click to collapse
Oh god! On which guide you read that for repartition you have to delete p13 n p12....I think you bricked it hard...may be some 1 can help you in this situation...
nageswarswain said:
Oh god! On which guide you read that for repartition you have to delete p13 n p12....I think you bricked it hard...may be some 1 can help you in this situation...
Click to expand...
Click to collapse
:crying::crying::crying::crying::crying::crying::crying:
I hope that this can happen. I love this phone :c
Takamasu said:
:crying::crying::crying::crying::crying::crying::crying:
I hope that this can happen. I love this phone :c
Click to expand...
Click to collapse
Is there any symptoms of life on your phone?
nageswarswain said:
Is there any symptoms of life on your phone?
Click to expand...
Click to collapse
There is two kind of symptoms.
01 - When I plug the Data Cable on PC, shows (on PC only) a connected device, but the PC can't recognize it.
02 - When I plug the phone into the socket without battery, it lights the red light, just not like before when operated normally. This time the LED blinks rapidly and appears in a weaker tone, as if without strength enough.
Takamasu said:
There is two kind of symptoms.
01 - When I plug the Data Cable on PC, shows (on PC only) a connected device, but the PC can't recognize it.
02 - When I plug the phone into the socket without battery, it lights the red light, just not like before when operated normally. This time the LED blinks rapidly and appears in a weaker tone, as if without strength enough.
Click to expand...
Click to collapse
Then Read here and know your device situation and follow the procedures to solve...Best of Luck (Remember in most cases Rubber band trick works well)SO read that part carefully and follow...)
Code:
7 0 19782 loop0
179 0 31162368 mmcblk0
179 1 2048 mmcblk0p1
179 2 512 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 1 mmcblk0p4
179 5 512 mmcblk0p5
179 6 3072 mmcblk0p6
179 7 3072 mmcblk0p7
179 8 3072 mmcblk0p8
179 9 5120 mmcblk0p9
179 10 8192 mmcblk0p10
179 11 16384 mmcblk0p11
179 12 1048576 mmcblk0p12
179 13 256000 mmcblk0p13
179 14 2097152 mmcblk0p14
179 15 27064320 mmcblk0p15
This is the phone Partition Table. If he deleted partition 14, 13 and 12
Then he deleted data partition (14), Cache partition (13) and system partition (12).
You should still be able to boot into recovery. Boot into TWRP>Change partition again you will be ok. Alternatively, Flash using flashtool you will be more than ok.
Hi Friends,
For past two years Yu Yureka is (was) a reliable phone for me. It's giving me problems as mentioned below and wanted to know what would be a proper resolution for it.
Recently the phone started giving heating problems , slow than expected screen response, and faster battery draining. Thought there must be a Virus / malware / spyware / etc on my system. Till date I did not have a AntiVirus on my phone and thought that's the reason. So I downloaded McAfee AntiVirus, performed a scan but did not find any. The phone worked fine for a day or so. I don't recollect why .. but I went for a phone reboot and since then all the problem started.
Post reboot I got "Android is starting ..... Optimising app 12 of 114". The optimising process would complete in approx 30-45 mins and the phone would reboot and same process would get repeated. Effectively the phone was rebooting continuously in a loop. Out of desperation I removed the battery and put it back in. I recollected that to bring up the recovery screen one had to press power button alongwith volume up and down button ... all three buttons simultaneously for 15-20 seconds to bring up the recovery screen from powered off state. I did the same and got recovery screen. Tried cleaning cache partition which did not help. So the last option was to clean all partitions (don't recollect the option) which effectively formatted the phone. I lost the data but the phone recovered and got the phone's GUI.
I started installing my previous applications on the phone. Few of the applications worked fine. After installing "TypeApp" application the phone screen started behaving weirdly. The screen would flash / blink three times and then move to a previous screen which worked. If I press the home button same issue of blinking would occur. If I move from that screen to anyone other application screen by pressing the left button (application list button) that would also work. But I would not be able to land up on home screen by pressing the home button and effectively I cannot start a new application. At this stage please note that "TypeApp" Application was working on my phone for past two years.
Now I reboot the phone and again I got "Android is starting ... Optimising app". I allowed sufficient time in hours for the phone to boot properly but that never happens. Eventually I again need to go for wipe all data from the recovery screen and the phone boots up properly.
Could someone suggest how can I install all the applications and still have the phone in usable state.
Thanks !
Platform details
Device : AO5510
Cyanogen OS version : 12.1-YOG4PAS8A4
Android Version : 5.1.1
Andriod Security Patch Level : 2016-05-01
Build Date : Sun Apr 10 21:21:23 PDT 2016
Kernel Version : 3.10.49-cyanogenmod-gbca6118 [email protected] #1 Sun Apr 10 21:40:30 PDT 2016.
tarokon said:
Device : AO5510
Cyanogen OS version : 12.1-YOG4PAS8A4
Android Version : 5.1.1
Andriod Security Patch Level : 2016-05-01
Build Date : Sun Apr 10 21:21:23 PDT 2016
Kernel Version : 3.10.49-cyanogenmod-gbca6118 [email protected] #1 Sun Apr 10 21:40:30 PDT 2016.
Click to expand...
Click to collapse
Try this
https://androidfilehost.com/?fid=24533103863137354
hitting thanks [emoji106] button keeps encourage me
Rajendran Rasa said:
Try this
https://androidfilehost.com/?fid=24533103863137354
hitting thanks [emoji106] button keeps encourage me
Click to expand...
Click to collapse
Hi,
If I'm not mistaken following should be the steps.
1) Download the 600+ MB file from the location and copy it into some phone location.
2) Goto Cyanogen boot loader / recovery screen and select "Apply Update" and select this file.
Just making sure so that I don't screw up my phone.
Thanks.
I believe the version that I have is
"Cyanogen OS version : 12.1-YOG4PAS8A4"
which is identical to what is present at previously mentioned URL as
cm-12.1-YOG4PAS8A4-tomato-signed-fastboot-a7a306cebd.zip
Correct ?
So then why to reinstall the same image ?
tarokon said:
I believe the version that I have is
"Cyanogen OS version : 12.1-YOG4PAS8A4"
which is identical to what is present at previously mentioned URL as
cm-12.1-YOG4PAS8A4-tomato-signed-fastboot-a7a306cebd.zip
Correct ?
So then why to reinstall the same image ?
Click to expand...
Click to collapse
Maybe your system software is corrupted that's why it is misbehaving
The link I'm posted is a fastboot signed zip
It means it should be flashed via fastboot command throught pc
Extract cm zip and flashtool zip in same folder
Run flash-all.bat file
For more info/tutorial search xda or watch YouTube
hitting thanks [emoji106] button keeps encourage me
Some apps causes this
I too got the same issue after facebook was updated from playstore. When I reboot, it got stuck in the optimization screen. For fix, do a factory reset and reboot. Don't install facebook app and it worked for me. Yesterday got the same issue after paytm was updated. Now, I had to add these 2 apps in my blocklist and Yureka works good for me.
Hello
I have a shield tv 2015 with nvidia experience 8.1 (android 9) - last October 2, I upgraded to 8.0.1, installed and when it was to restart, turned off and did not turn on.
Turns on the 2 sec green light and turns it off and the disc works (it seems to be in standby).
I opened a ticket (on nvidia) but it is being useless because the procedures that give me do not work.
I found that underneath is a snap-in cover. so i turned off the hard drive it always turns on the green light but i can't get into fastboot / recovery mode.
At the moment when I connect the usb cable to the pc I have an APX device. does anyone know anything about APX?
Thanks help me please i´m a nood
Your only bet is to get help from nvidia costumer support since it's not a pro version.
Apx mode = your device is bricked.
Mine is the 500GB version I suppose is the PRO version.
I've been reading here in the forum ... in the PRO version the
All software is on the hard drive. So I was trying to create the hard drive with a 500GB disk but to no avail.
parfuar said:
Mine is the 500GB version I suppose is the PRO version.
I've been reading here in the forum ... in the PRO version the
All software is on the hard drive. So I was trying to create the hard drive with a 500GB disk but to no avail.
Click to expand...
Click to collapse
You can try what has been done in this thread https://forum.xda-developers.com/shield-tv/general/bricked-shield-tv-pro-2015-version-t3841024
Or something like this https://forum.xda-developers.com/shield-tv/general/guide-migrate-to-ssd-hdd-size-satv-pro-t3440195
Hi,
One question.
My original hard drive
Info:
[email protected]:/home/ubuntu# hdparm -i /dev/sda
Model=ST500LM000-1EJ162, FwRev=SM16, SerialNo=W763XDYH
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
BuffType=unknown, BuffSize=unknown, MaxMultSect=16, MultSect=off
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=976773168
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6
AdvancedPM=yes: unknown setting WriteCache=enabled
Drive conforms to: Reserved: ATA/ATAPI-4,5,6,7
* signifies the current active mode
-------------------------------------------------------------------------------------------------------------------------------------
fdisk -l
Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xb22c3a15
my new hard drive
info:
[email protected]:/home/ubuntu# hdparm -i /dev/sda
Model=HGST HTS545050A7E380, FwRev=GG2OACD0, SerialNo=TE85113R0Y5TPK
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
BuffType=DualPortCache, BuffSize=8192kB, MaxMultSect=16, MultSect=16
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=976773168
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6
AdvancedPM=yes: mode=0x01 (1) WriteCache=enabled
Drive conforms to: unknown: ATA/ATAPI-2,3,4,5,6,7
* signifies the current active mode
----------------------------------------------------------------------------------------------------------------------
--->> fdisk -l
Disk /dev/sda: 465,8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x4ca778fd
Hard drives are the same, I should with the tutorial, be able to get the shield to work without major problems.
what is wrong?
commands used:
dd if=start.bin of=/dev/sdX bs=4M
dd if=end_976574630.bin of=/dev/sdX seek=976574630
with these files:
https://forum.xda-developers.com/sho...2&postcount=23
My shield(2015 pro) was also bricked by the update reboot loop at nvidia logo and factory reset did not help and fastboot couldn't flash anything, so used this opportunity however to put a ssd in.
Used beginning disk image from here:
https://forum.xda-developers.com/showpost.php?p=67426622&postcount=23
Just booted it up and its gotten past nvidia logo atleast so far
First time it bricked was updating to 8.0, after recovery it was able to get the updates up to 8.0, when i did the 8.0.1 update i also got the same error as those above where turns on then off and does not even wake the display.
HellToupee_nz said:
My shield(2015 pro) was also bricked by the update reboot loop at nvidia logo and factory reset did not help and fastboot couldn't flash anything, so used this opportunity however to put a ssd in.
Used beginning disk image from here:
https://forum.xda-developers.com/showpost.php?p=67426622&postcount=23
Just booted it up and its gotten past nvidia logo atleast so far
Click to expand...
Click to collapse
It worked?
what version of android is it?
on mine it didn't work. only worked with the first part (firstpart.bin which is like this) and with the 5kb file that speak at the end of this thread.
parfuar said:
It worked?
what version of android is it?
on mine it didn't work. only worked with the first part (firstpart.bin which is like this) and with the 5kb file that speak at the end of this thread.
Click to expand...
Click to collapse
In my case, I have the fastboot. but this is difficult because we don't have active developer mode.
Yes, i had done a factory reset also, u can get stuck at the spinning android logo forever without that i find. For the end part of the disk i used my own from my disks image, i've just done it all again and updated back to 7.2.3 stopped there and copied my widevine key off my orginal image so got L1 support and going to make backup of its current state.
parfuar You don't use "sdX" you change the "X" to the letter your drive is from fdisk -l , looks like you need to use "sda", after after you write the two bin files reboot directly into bootloader and select boot recovery kernel which will bring up t wrp recovery and you need to perform a factory reset wipe then reboot and Android should boot up and you will have Nvidia experience 3.3 and you have to do a couple updates to get up to 8.0 just make sure you turn off automatic updates cuz mine automatically updated to 8.0.1 and crashed my hard drive a second time. I used my original hard drive
also posting here that my 2015 500gb gets bricked with 8.0.1. hdd swapped out for crucial mx500. i think the guy here said it happened on his stock 500 sshd?
OK... This is how I got it to work.
Using "DD for Windows"... since I don't have a Linux PC (tested working perfectly on Windows 10 x64)
Download link:
http://www.chrysocome.net/downloads/dd-0.6beta3.zip
Unzip the "dd.exe" file and copy it to:
%USERPROFILE%\AppData\Local\Microsoft\WindowsApps
This gives you the ability to use DD system wide.
Use the beginning disk image from here:
https://forum.xda-developers.com/showpost.php?p=67426622&postcount=23
Connect your drive. I highly suggest using a Desktop PC because it is much faster than a USB to Sata cable.
If you don't have any open Sata slots, just disconnect your CD-rom drive temporarily and use the connectors.
Now:
1) Put the "start.bin" file in the root directory of drive C (example C:\start.bin)
2) Open a command prompt as Administrator and change directory to C: (command: cd C:\ )
3) Type command dd --list to determine the correct disk you want to write to.
4) Use command dd if=start.bin of=\\?\Device\HarddiskX\Partition0 --progress
whereas X is the drive number you determined earlier with the dd --list command
(replace the X with the drive number you want to write to)
5) Watch the write progress and stop the process at about 6GB (around byte 6,500,000,000)
(you can actually see the write counter running)
There is no need to write the "end file". Shut down the PC once finished and remove the drive.
6) Install the drive back into your Shield Pro and start. The green NVIDIA logo should show up soon.
Wait for about 10 minutes and if nothing happens unplug the Shield and do a restart.
Now wait patiently.... it will eventually boot past the green logo and the Android colors.
Now let your Shield self-update to whatever version you desire. It starts with version 3.0
That's it! You just successfully de-bricked your Shield Pro
Enjoy!