Related
Hi Guys,
I've been researching about this topic now for quite a while, but i am still not certain, whether if the eMMC of my DZ is fried..
Story is as follows:
Just rooted my newly bought DZ (lost my old one )using downgrade, then gfree, everything went fine so far.
After that i went to recovery, flashed virtuous affinity and rebooted. I gave it time to boot, but it got stuck on the "loading initial setup" screen (waited patiently about 20 mins or so). I thought it would be no big deal to pull the battery and let it boot again (Did this with my previous DZ numerous times and all was fine)
On second boot nothing happened, so i checked recovery and saw that the /data and /cache were obviously corrupt. Formatting was not possible by any means, neither by the tools in recovery, nor through flashing superwipe.
I can confirm that my eMMC is one of those possible faulty M4G2DE, see: http://forum.xda-developers.com/showthread.php?t=1039504&highlight=can+t+format&page=3
But it is mentioned in the thread, that it could be either a faulty chip or a defective partition table, which should be possible to rebuild either with a RUU or by adb shell:
Code:
mke2fs -t -ext3 /dev/block/mmcblk0p27
It was also mentioned to check whether
Code:
cat /proc/kmsg | grep mmc0
would say anything about an initialization error, which is not the case for me:
Code:
cat /proc/kmsg | grep mmc0
<3>[ 7.565124] mmc0: No card detect facilities available
<6>[ 7.565765] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 7.565917] mmc0: Platform slot type: MMC
<6>[ 7.566162] mmc0: 4 bit data mode disabled
<6>[ 7.566284] mmc0: 8 bit data mode enabled
<6>[ 7.566528] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 7.566680] mmc0: Slot eject status = 0
<6>[ 7.566802] mmc0: Power save feature enable = 1
<6>[ 7.567077] mmc0: DM non-cached buffer at ffa0c000, dma_addr 0x2a924000
<6>[ 7.567199] mmc0: DM cmd busaddr 0x2a924000, cmdptr busaddr 0x2a924300
<6>[ 7.723022] mmc0: new high speed MMC card at address 0001
<6>[ 7.724884] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
I know, from this point, being unable to do a RUU, nor flash a PC10IMG.zio via fastboot, nor recreate partitions in any other way, would suggest that the eMMC is fried and i should see that i send it in for repair.
BUT
I came across this:
http://tjworld.net/wiki/Android/HTC/Vision/EmmcPartitioning
Basically he is saying, that the hboot is trying to create an extended partition on the end of the blocks, if unallocated blocks are still available this should do no harm. But if the disk is fully partitioned, it simply overflows and creates the partittion at the beginning of the disk. According to that, this causes the usual tools to be unable to reformat the disk, because they get stuck in the same overflow.
He mentions a way to fix this, by unallocating the last partition, but i am not sure how this could be done.
Can the hboot be the problem? The new DZ runs eng hboot 84.2000, on my old one i used to have the normal pvt ship (see sig)
Maybe some of you would like to help me think
And maybe we can find a solution for some of the fried eMMC's
Hi Xadro
unfortunatly i have currently exactly the same problem. I can't manage to format the system partition (mmcblk0p25) and the cache partition (mmcblk0p27).
Do got any solution for it?
Thx in advance
Chris
Small update:
I managed to format each in 4EXT with tools formating to use ext3. Now my info is showing me the attatched screeni. Before that he crashed everytime when I opend that view and system and cache was ext4 but also without size values.
Kind of an awkward way of thinking, but... I see that you have a 32GB Sd Card.
Could that have any link to your problem?
Mhh dont know. Shouldn't as i never had problems before.
My target was to use Android Revolution HD 7.0.2 and I may should add the whole story in short form:
followed http://forum.xda-developers.com/showthread.php?t=1178912 to do a downgrade -> worked perfectly
followed the rest of http://forum.xda-developers.com/wiki/HTC_Vision#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD to gain perm root until step 7. -> worked perfectly
used http://forum.xda-developers.com/showthread.php?t=1493404 to gain a new rom
it was written to use 4EXT -> so installed what worked and also the info was displaying the correct sizes
applied ZIP and restarted -> waited 30min but only boot animation was displayed and after some time it restarted -> boot loop
applied the ZIP again -> same result
found in http://forum.xda-developers.com/showthread.php?t=840040 to load SuperWipe...what i did and it reformated worked with out error
applied ZIP again
didn't started anymore -> stucked there
During all the restartings it can be that i may interrupt some important "reallocating" of partitions...but not sure.
But I can try replace the SD with the original one. But not thinking that it is a problem, cause it is normal accessable :/
Any way big thanks for trying to help me!
try a fastboot wipe, cleaner than even your best superwipe - then when you pick a rom to flash pick an old tried and true like the stable cm7 or miui.us
Hi,
unfortunatly that didn't worked
if I start "fastboot erase system -w" (i think you ment that) he just writing "erasing 'system'..." and just stops there. my phone is displaying the whole time the fastboot white screen, but i can't do anything there anymore (vol up/down...). I waitet 2h...only could remove battery
I realy appresiate any other recommendation :/
Update:
Also this hangs:
Code:
./fastboot -w
erasing 'userdata'...
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 3627.265s
Phone needs to be in flashboot usb, and when you open cmd on your comp you need to open it to where you have fastboot stored or change directories to it. Or you can add it to your variables and open it anywhere.
Sent from my HTC Desire Z using xda premium
Sorry for answering a bit late, but was in weekend holidays
Of course i did it in the fastboot folder and my phone was in fastboot usb (red blinking on phone screen). Otherwise i would get "<waiting for device>". Just got that error message posted above. Any ideas left? Otherwise it seams to be a broken eMMC
So when conected phone displayedfastboot usb in red? If so when you typed fastboot devices did it display one?
Sent from my T-Mobile G2 using xda premium
Yepp, it does show serial and "recovery".
And if you try to flash the hboot/spl now what happens?
Sent from my T-Mobile G2 using xda premium
Hi again,
I tried to flash the hboot while in fastboot with following message:
Code:
C:\android-sdk-windows\platform-tools\rom_26>fastboot flash hboot hboot_7230_Vision_HEP_0.85.0005_101011.nb0
sending 'hboot' (1024 KB)...
OKAY [ 0.183s]
writing 'hboot'...
FAILED (remote: image update error)
finished. total time: 2.904s
Also tried to do it with "dd" what seem to work but as soon as i restart the phone it still says it is in an "VISION PVT ENG S-OFF" while i was flashing a non-ENG hboot...and the version also not matching "HBOOT-0.84.2000" while flashing 0.85.0005
I also tried to put a newer (2.42.405.2) PC10IMG.zip from RUU on SD Card but it fails with message "BOOTLOADER - Fail-PU" and "Partition update fail! Update Fail!"
I realy think the eMMC got bricked...If you do not have any advices anymore i will look for a replacement from somewhere.
I still searched around and found that post: http://forum.xda-developers.com/showthread.php?t=1039504&page=6#post14645519
Its exactly my situation with same outputs and also the "bad" eMMC. I will try to send it in. Reading all that i have to admit that i already had before trying rooting it, i couldn't do a normal restart (just had a black screen after splash screen). It must have been connected to USB to be able to do a restart. So I think i didn't done anything wrong...just have a hardware issue
Sorry for not answering you chrisdeath, was busy with other stuff lately, so i hadn't had the time to stop by here. Have you been sending in your phone already? Telling from the stuff you wrote earlier, it is very likely a fried emmc. There is a way to confirm this, using two shells. With one shell, you need to display the log using
Cat /proc/kmsg ¦ grep emmc0
With the other shell, try to do any kind of write access (e.g. format partition or dd anywhere)
If there are any errors in the log referring to the write fail, your chip is bricked.
It will probably get fixed free of charge, even if the phone is rooted, others have told me that they got it new without payment. If your new one has the same chip, you should if by any means possible, never pull the battery during operation, as this seems to be the main cause for bricking the chip.
Sent from my HTC Vision using XDA
Hello everyone. Here's my story
I've been using CM13. After installing their OTA update it ruined my android. So I downloaded new cm13 rom, wiped everything, accidentally clicked reboot (without flashing new rom) and it was over (At least I think this happened, it was some time ago and I'm already trying to fix this for a long).
I am stuck in LG logo. Can't access recovery (I've had this issue before. Could get to recovery only by command from adb).
I can get to Download mode. But PC can't see my device. Tried several PC's, windows, ubuntu. I flashed other phones with this method, only G2 is not visible. I'm doing here everything fine.
Also I tried this:
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
Success but my phone keeps flashing on and off. I've got access to partitions like every 5 seconds and only for a second. I think I managed to flash those 3 partitions, but there's no difference, pc still can't see phone when in download mode.
Should I trow it to the ocean?
Keep it
Here is my story
Bricked my device (d802) with your stuation no recovey no download mode
My phone's partition table deleted any way, tried wire method which you've already tried
Tried several times and release this wire method put in 2 seperate modes
Found the mode it shows in ubuntu a sda block (with several tries with wire method)
I've got full 32 gig backup, thats my advantage between your stuation
In ubuntu fdisk - l shows all disk and shows my phone as a disk but no information about disk or partitions etc. only sda block
In the end pushed the 32 gig backup with dd if=/(path of my backup) of=/dev/block/sd* bs=4k
Wait some time until process done (30-45 minutes I guess)
Thats all, phone boots normally everything is fine
If you're using 32 gig version I can send you my backup (with imei deleted) so you can boot your device and install kdz
Or I can show you how to backup another LG phone and recover from that backup. http://forum.xda-developers.com/lg-g2/general/how-to-backup-data-16-gb-32-gb-size-t3236558
Thank you for your reply lynxrz
I've got bigger problem. When I enter qhsusb mode, backlight of my screen keeps switching on and off every 3-4 seconds. I can see partition only for a second.
Vergil333 said:
Thank you for your reply lynxrz
I've got bigger problem. When I enter qhsusb mode, backlight of my screen keeps switching on and off every 3-4 seconds. I can see partition only for a second.
Click to expand...
Click to collapse
Not necesaary to see partitions
In ubuntu or any linux enviroment open up a teeminal emulator and "sudo fdisk -l" and it will be like that;
Code:
$ sudo fdisk -l
Disk /dev/sda: 8589 MB, 8589934592 bytes
255 heads, 63 sectors/track, 1044 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00008ec7
Device Boot Start End Blocks Id System
/dev/sda1 * 1 1013 8136891 8e Linux LVM
/dev/sda2 1014 1044 249007+ 5 Extended
/dev/sda5 1014 1044 248976 83 Linux
sda sdb sdc means a phisicial disk. sda1 sda2 sda3 means partitions of "sda" disk. My process depends on overwriting sda disk not partitions, so you don't need to see partitions
Just type "sudo fdisk -l" and tell me you can see any sdb sdc phisical disk permenately. We must know connection can be dropped or not(it can be bootloop). Partitions might disappear but phisical disk have to be there. Look for it.
If you can't see in qhsusb mode try another mode, this is the lucky part of tring the wire method. I don't know exactly how to swich "another" mode but you can detect in window device manager, then switch to linux (Don't be afraid to losing this mode it stays when you plug off usb if you connected battery)
Sorry I don't remember that "another" mode's name but it is exists
Firstly you need to know qhsusb mode can see a "phisical" disc or not?
I'm in work now, but I tried this yesterday.
Phone appears as sdc when I typed
Code:
$ ls /dev/sd*
while in qhsusb mode. (I had to type it several times repeatedly to catch the right moment)
I can get to download mode, so I typed
Code:
$ sudo fdisk -l
and couldn't see sdc there.
Vergil333 said:
I'm in work now, but I tried this yesterday.
Phone appears as sdc when I typed
Code:
$ ls /dev/sd*
while in qhsusb mode. (I had to type it several times repeatedly to catch the right moment)
Click to expand...
Click to collapse
Probably it can be bootloop.
Did you plug off the battery when touching capacitor ? Just asking to be sure.
Sure, I unplugged the battery So qhsusb not stable and download mod not visible to computers.
I already gave up of hope
Ok I will solve how to enter "another" mode (not qhsusb)
But I need time to backup all my data in any case
If I solve, prepare a backup for you and it'll be 32 GB
Edit: Can not find out "another" mode because of data cable problem (severed usb cable charging but not transferring data) You're on your own now to find another usb mode, It can be the "holding time" of cable on capacitor.
Good luck with that
Prepairing your backup with otg
Really thanks for your help lynxrz. I appreciate all effort
Vergil333 said:
Really thanks for your help lynxrz. I appreciate all effort
Click to expand...
Click to collapse
You're welcome
PS: Did I send pm the download link?
You did. 29.1GB rar file. I have no use for it till I find another mode to be able to flash partition.
I already bought G3. Probably I will sell G2 for parts
Uploading now and it was %17 maybe tomorrow will be uploaded %100
20,4 GB and compressed seperated 1 GB rar parts (21 parts)
Realised by you broken usb, I'll solder it but no time for that now, 2 days later I'll try it.
I'm stuborn as hell with that Just wait we'll fix it don't sell
Maybe I can make a tutorial and help the others
UPDATE: Usb works I'll try it tomorrow
Hi,
I never root or do anykind of development or advance usage of my shield 2015 pro,
but about 15days ago it just deside do not boot anymore . i don't think it got the last update, so i have no clue why it suddenly not boot anymore
The green light is there, but there is no output.
i tried to invoke the android fastboot with this nethod : http://nvidia.custhelp.com/app/answ...NNXg0SmNhUFlvNHpHMGkwM29mRlZxTVdQUVElMjElMjE=
i also tried to factory reset with :
http://nvidia.custhelp.com/app/answ...hen-you-are-unable-to-access-android-settings
but didn't succeed to see anything, there is no output at all (the TV says so, and i try other stuff the TV works)
i don't know what to do ?
is it actually bricked ? can i do somthing about it ?
Thank you in advance
Bobzer
bobzer said:
Hi,
I never root or do anykind of development or advance usage of my shield 2015 pro,
but about 15days ago it just deside do not boot anymore . i don't think it got the last update, so i have no clue why it suddenly not boot anymore
The green light is there, but there is no output.
i tried to invoke the android fastboot with this nethod : http://nvidia.custhelp.com/app/answ...NNXg0SmNhUFlvNHpHMGkwM29mRlZxTVdQUVElMjElMjE=
i also tried to factory reset with :
http://nvidia.custhelp.com/app/answ...hen-you-are-unable-to-access-android-settings
but didn't succeed to see anything, there is no output at all (the TV says so, and i try other stuff the TV works)
i don't know what to do ?
is it actually bricked ? can i do somthing about it ?
Thank you in advance
Bobzer
Click to expand...
Click to collapse
You didn't mention it so i ask, did you try with other HDMI cables? If still no go and as it is the pro which is more tricky, then better request RMA.
Have you also tried running fastboot commands blindly? I mean do the steps to boot into fastboot/bootloader mode, then if you haven't installed windows drivers try to do so, check device manager, does it recognize your device? What does it show?. If your device is recognized by your PC in fastboot mode and you succeed to install drivers then that will tell us something, otherwise is hard brick but still could be a hardware issue.
Sent from my Tapatalk beta Hub
If I helped hit the Thanks button. Follow Me! ~ DroidMote user ~ Full Android for Shield TV and Nexus Player
lavero.burgos said:
You didn't mention it so i ask, did you try with other HDMI cables? If still no go and as it is the pro which is more tricky, then better request RMA.
Have you also tried running fastboot commands blindly? I mean do the steps to boot into fastboot/bootloader mode, then if you haven't installed windows drivers try to do so, check device manager, does it recognize your device? What does it show?. If your device is recognized by your PC in fastboot mode and you succeed to install drivers then that will tell us something, otherwise is hard brick but still could be a hardware issue.
Sent from my Tapatalk beta Hub
If I helped hit the Thanks button. Follow Me! ~ DroidMote user ~ Full Android for Shield TV and Nexus Player
Click to expand...
Click to collapse
Hi,
thanks for trying to help me,
I tried the cable with another device so the cable is fine
i tried the fastboot blindly but no success (maybe/probably/hopefully i don't do it correctly )
about windows i didn't saw it on windows at all, but that wasn't worry me at that time because i didn't know where to look, so i thought it was maybe normal
about driver no idea of what should i do. during my search i saw little bit about adb
all my search bring me to topic where people did stuff to there shield (root, try rom , etc) i didn't do anything so i don't know what information is relevant for me or not
tonight i will install driver and try again.
just to summarize :
After installing the driver:
- if i see the device in the device manager there is hope
- if not it's hard brick and so i can do nothing ?
if that true ?
thanks you
I would have a look at the SSHD to SSD migration Threads here on XDA (Shield TV), and attempt to make a backup of the SSHD. (If possible). This will of course be of MAJOR IMPORTANCE if you wish to retain any of the Widevine L1 DRM Provider Content (e.g. Amazon, and Netflix. etc.. etc...)
It seems to me that the Bootloader got wiped / corrupted (Which is actually the good news), or the SSHD has died. (Well it probably can't get worse than that.)
In the SSD Migration Thread there is a link to download an Backed up version of someone else's Shield TV. I managed to use this to recover a hard bricked Shield before. My mistake was not making a backup of the Security Sectors of that Device, and I lost all those Services.
It is however possible to rewrite that backup over a working backup to recover the correct L1 Widevine Keys though. IF YOU REMEMBER to make that Backup first. So it's probably not too late to do that. The worst case scenario? Your just gonna lose a buttload of DRM Services that you may, or may not even depend on. If your more of a Kodi Person, than this shouldn't even affect you much. But, of course it would be wiser to try and, retain those Widevine Keys if possible.
bobzer said:
Hi,
thanks for trying to help me,
I tried the cable with another device so the cable is fine
i tried the fastboot blindly but no success (maybe/probably/hopefully i don't do it correctly )
about windows i didn't saw it on windows at all, but that wasn't worry me at that time because i didn't know where to look, so i thought it was maybe normal
about driver no idea of what should i do. during my search i saw little bit about adb
all my search bring me to topic where people did stuff to there shield (root, try rom , etc) i didn't do anything so i don't know what information is relevant for me or not
tonight i will install driver and try again.
just to summarize :
After installing the driver:
- if i see the device in the device manager there is hope
- if not it's hard brick and so i can do nothing ?
if that true ?
thanks you
Click to expand...
Click to collapse
Right, if your PC recognize your shield in fastboot mode then it means is alive. When people have hard bricked their devices by corrupted bootloader some are able to boot into APX mode, which confirms their device won't be able to recover (unless Nvidia release the tools), but for others the device won't even turn on.
If your pc recognizes your shield tv in fastboot mode and you are able to install windows drivers and you get an id when typing fastboot devices in cmd, then there is a 50/50 chance of recovering, don't forget the possibility of hardware failure.
The following video can help you, just follow until i open command line and start typing fastboot commands but you just have to type "fastboot devices" command nothing else, if you get an id it means that the link with your shield tv is successful.
https://youtu.be/LQaYb4oVHVc
Report back!. Oh but still try other good hdmi cable(s), i tell you for experience, weird **** happens. I have had weird issues with hdmi port and hdmi cable (Amazon basics brand) in the past.
Ichijoe said:
I would have a look at the SSHD to SSD migration Threads here on XDA (Shield TV), and attempt to make a backup of the SSHD. (If possible). This will of course be of MAJOR IMPORTANCE if you wish to retain any of the Widevine L1 DRM Provider Content (e.g. Amazon, and Netflix. etc.. etc...)
It seems to me that the Bootloader got wiped / corrupted (Which is actually the good news), or the SSHD has died. (Well it probably can't get worse than that.)
In the SSD Migration Thread there is a link to download an Backed up version of someone else's Shield TV. I managed to use this to recover a hard bricked Shield before. My mistake was not making a backup of the Security Sectors of that Device, and I lost all those Services.
It is however possible to rewrite that backup over a working backup to recover the correct L1 Widevine Keys though. IF YOU REMEMBER to make that Backup first. So it's probably not too late to do that. The worst case scenario? Your just gonna lose a buttload of DRM Services that you may, or may not even depend on. If your more of a Kodi Person, than this shouldn't even affect you much. But, of course it would be wiser to try and, retain those Widevine Keys if possible.
Click to expand...
Click to collapse
thanks, for the idea, i'll first check with the driver.
and after i'll backup the drive at the same time i'll check if there is smart value. in case is the drive which is in a bad state
lavero.burgos said:
Right, if your PC recognize your shield in fastboot mode then it means is alive.
Click to expand...
Click to collapse
to entering the fastboot mode the only way is pressing for about 3sec after powering up or thanks to the drivers it will enter automatically ?
lavero.burgos said:
The following video can help you, just follow until i open command line and start typing fastboot commands but you just have to type "fastboot devices" command nothing else, if you get an id it means that the link with your shield tv is successful.
https://youtu.be/LQaYb4oVHVc
Click to expand...
Click to collapse
thanks i can't watch it right now but i'll as soon as possible tonight
lavero.burgos said:
Report back!. Oh but still try other good hdmi cable(s), i tell you for experience, weird **** happens. I have had weird issues with hdmi port and hdmi cable (Amazon basics brand) in the past.
Click to expand...
Click to collapse
I will thanks
bobzer said:
to entering the fastboot mode the only way is pressing for about 3sec after powering up or thanks to the drivers it will enter automatically ?
Click to expand...
Click to collapse
Better to do it manually as i show in the video, the other method from windows never worked for me and for many.
lavero.burgos said:
Better to do it manually as i show in the video, the other method from windows never worked for me and for many.
Click to expand...
Click to collapse
ok thanks
looking forward to try this
so i'm currently trying and sadly i can confirm that the green light is on, cable plug to shield but not recognize at all in the device manager
lavero.burgos said:
Better to do it manually as i show in the video, the other method from windows never worked for me and for many.
Click to expand...
Click to collapse
i did exactly as explained and the nothing happend except that the green light turn off
so when i plug the cable i remove my fing and put it back on the shield and waiting and after a few second the light goes off and stay off but windows still not recognize
Ichijoe said:
I would have a look at the SSHD to SSD migration Threads here on XDA (Shield TV), and attempt to make a backup of the SSHD. (If possible). This will of course be of MAJOR IMPORTANCE if you wish to retain any of the Widevine L1 DRM Provider Content (e.g. Amazon, and Netflix. etc.. etc...)
It seems to me that the Bootloader got wiped / corrupted (Which is actually the good news), or the SSHD has died. (Well it probably can't get worse than that.)
In the SSD Migration Thread there is a link to download an Backed up version of someone else's Shield TV. I managed to use this to recover a hard bricked Shield before. My mistake was not making a backup of the Security Sectors of that Device, and I lost all those Services.
It is however possible to rewrite that backup over a working backup to recover the correct L1 Widevine Keys though. IF YOU REMEMBER to make that Backup first. So it's probably not too late to do that. The worst case scenario? Your just gonna lose a buttload of DRM Services that you may, or may not even depend on. If your more of a Kodi Person, than this shouldn't even affect you much. But, of course it would be wiser to try and, retain those Widevine Keys if possible.
Click to expand...
Click to collapse
so i removed the sshd and try to backup it...
that's first that i wasn't able to recover anything from a drive that's appear on my computer
it's so strange because it's there the smart see it but i can't read nothing at all :
Code:
[email protected]:/mnt/raid/backup/shield# ls -l /dev/sdb
brw-rw---- 1 root disk 8, 16 juin 14 02:56 /dev/sdb
[email protected]:/mnt/raid/backup/shield# fdisk -l /dev/sdb
fdisk: impossible d'ouvrir /dev/sdb: Aucun fichier ou dossier de ce type
[email protected]:/mnt/raid/backup/shield# ddrescue -f -n /dev/sdb shield.dd mapfile
GNU ddrescue 1.19
Press Ctrl-C to interrupt
rescued: 0 B, errsize: 0 B, current rate: 0 B/s
ipos: 0 B, errors: 0, average rate: 0 B/s
opos: 0 B, run time: 1 s, successful read: 1 s ago
Finished
commande : 'smartctl' -i -H -c '/dev/sdb'
smartctl 6.4 2014-10-07 r4002 [x86_64-linux-3.16.0-4-amd64] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Seagate Laptop SSHD
Device Model: ST500LM000-1EJ162
Serial Number: W764J2R0
LU WWN Device Id: 5 000c50 082dc3e28
Firmware Version: NV9D
Rotation Rate: 5400 rpm
Form Factor: 2.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 1.5 Gb/s)
Local Time is: Wed Jun 14 03:02:44 2017 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART Status not supported: Invalid status byte (0x00) [JMicron]
SMART overall-health self-assessment test result: PASSED
Warning: This result is based on an Attribute check.
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 139) seconds.
Offline data collection
capabilities: (0x73) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 99) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x10b1) SCT Status supported.
SCT Feature Control supported.
SCT Data Table supported.
here the dmesg :
[270724.389743] usb-storage 3-2:1.0: USB Mass Storage device detected
[270724.389819] scsi6 : usb-storage 3-2:1.0
[270724.389901] usbcore: registered new interface driver usb-storage
[270727.372913] scsi 6:0:0:0: Direct-Access ST500LM0 00-1EJ162 PQ: 0 ANSI: 2 CCS
[270727.373406] sd 6:0:0:0: Attached scsi generic sg2 type 0
[270730.079345] sd 6:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).
[270730.079514] sd 6:0:0:0: [sdb] 72057594037927936 512-byte logical blocks: (0 B/0 B)
[270730.079798] sd 6:0:0:0: [sdb] Write Protect is off
[270730.079802] sd 6:0:0:0: [sdb] Mode Sense: 28 00 00 00
[270730.080127] sd 6:0:0:0: [sdb] No Caching mode page found
[270730.080137] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[270730.080827] sd 6:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).
[270730.081756] sdb: unknown partition table
[270730.082349] sd 6:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).
[270730.083081] sd 6:0:0:0: [sdb] Attached SCSI disk
[270736.012772] usb 3-2: USB disconnect, device number 5
someone ? do you have any idea ? what could i do ?
Did you follow this Guide?* Essentially you make this backup in Two parts uninspiredly called "firstpart.bin" (Which is the first Six Gigabytes of the SSHD which also encompasses the unique DRM Keys for your Shield.). The lastpart.bin is more or less just the list of checksums for the GPT Partitions.
I wouldn't expect that you would, could or should be able to see anything from the Drive. As most of it is written in a RAW Partition. That is personally beyond my knowledge of how to mount it. That's why you have to make *.bin files which you can then view with a Hex Editor. If you wanted to.
*https://forum.xda-developers.com/shield-tv/general/guide-migrate-to-ssd-hdd-size-satv-pro-t3440195
Ichijoe said:
Did you follow this Guide?* Essentially you make this backup in Two parts uninspiredly called "firstpart.bin" (Which is the first Six Gigabytes of the SSHD which also encompasses the unique DRM Keys for your Shield.). The lastpart.bin is more or less just the list of checksums for the GPT Partitions.
I wouldn't expect that you would, could or should be able to see anything from the Drive. As most of it is written in a RAW Partition. That is personally beyond my knowledge of how to mount it. That's why you have to make *.bin files which you can then view with a Hex Editor. If you wanted to.
*https://forum.xda-developers.com/shield-tv/general/guide-migrate-to-ssd-hdd-size-satv-pro-t3440195
Click to expand...
Click to collapse
i did follow this topic but the problem is that dd doesn't works event fdisk don't work
Code:
[email protected]:/mnt/raid/backup/shield# fdisk -l /dev/sdb
fdisk: impossible d'ouvrir /dev/sdb: Aucun fichier ou dossier de ce type
it's fdisk telling me that it can't open my drive sdb no file or directory
i even tried ddrecue so i feel like i'm screwed
but i don't understand because i never saw this kind of problem with dd, i mean even a damage drive i always could start at least , copy a few bytes ... i don't understand what i miss ...
Did you remember to enter elevated root first?
Code:
$ sudo -s
If you don't do this, or you just throw up a sudo fdisk -l. I don't think it'll work. You have to be in an elevated root shell first.
Then you can use:
Code:
# fdisk -l
To list all the Drives currently in your System. Which will be more complicated depending on how many Drives you have.
Again this should list all the Drives currently on your System. You can easily, spot the Shields SSHD by the fact that it is exactly 499GB. Within in this context is the Drive Address. For me this has always been /dev/sda. Where as the local OS was on dev/sdb.
So when you get to this point:
Code:
dd if=/dev/sdX of=firstpart.bin count=6899870
You need to replace sdX with the correct Address of the Shield TVs SSHD. This will then hopefully create a ~3GB File called 'firstpart.bin'
Likewise
Code:
dd if=/dev/sdX bs=512 skip=976773158 of=lastpart.bin
Will create a 5kb File that hosts the Partition Map?
Again you have to replace sdX with the correct Address where the Shield TVs SSHD is hosted.
Ichijoe said:
Did you remember to enter elevated root first?
Code:
$ sudo -s
If you don't do this, or you just throw up a sudo fdisk -l. I don't think it'll work. You have to be in an elevated root shell first.
Then you can use:
Code:
# fdisk -l
To list all the Drives currently in your System. Which will be more complicated depending on how many Drives you have.
Again this should list all the Drives currently on your System. You can easily, spot the Shields SSHD by the fact that it is exactly 499GB. Within in this context is the Drive Address. For me this has always been /dev/sda. Where as the local OS was on dev/sdb.
So when you get to this point:
Code:
dd if=/dev/sdX of=firstpart.bin count=6899870
You need to replace sdX with the correct Address of the Shield TVs SSHD. This will then hopefully create a ~3GB File called 'firstpart.bin'
Likewise
Code:
dd if=/dev/sdX bs=512 skip=976773158 of=lastpart.bin
Will create a 5kb File that hosts the Partition Map?
Again you have to replace sdX with the correct Address where the Shield TVs SSHD is hosted.
Click to expand...
Click to collapse
thanks I will double check tonight but i'm pretty sure that i was root
Ichijoe said:
Did you remember to enter elevated root first?
Code:
$ sudo -s
If you don't do this, or you just throw up a sudo fdisk -l. I don't think it'll work. You have to be in an elevated root shell first.
Then you can use:
Code:
# fdisk -l
Click to expand...
Click to collapse
fdisk don't see the disk
i don't know what to do
I bought a new adapter because at first i thought it could be the adapter but no it's the drive that is like dead. so i bought a new drive but because i can't get a backup of the old one i don't know what to do
can i find somewhere a full backup that i could put in my drive ?
thx
i try to copy with dd and ddrescue, until now i got 0 bytes rescued so i guess my only luck would be to get a backup somewhere else, but even there would i be able to run netflix ?
You should contact Nvidia for replacement, hardware died, not your fault. Unfortunately if you didn't backup the relevant partitions containing your keys, then no you wont be able to watch Netflix.
Sent from my Tapatalk beta Hub
If I helped hit the Thanks button. Follow Me! ~ DroidMote user ~ Full Android for Shield TV and Nexus Player
Hiyas. Welcome a fresh corpse.
Shield 2015, non-pro, bricked by flashing a wrong image.
Bricked well, no adb, no screen, no button - just green led on powerup.
Nvidia says there's no official service in our swamps (lovely, huh) and I'm up to myself.
Anyone with succesful revival? Thanks guys.
Well, I finally got it together and figured out how to use the ROM bootloader on the iMX6 Nooks (Glow2, 3, 4).
You can get into u-boot even with a trashed disk.
Of course, that may not be the end of your problems.
You may have to repair stuff.
Having a UART console wired up will certainly make things clearer/easier.
So, if you have a bricked Glow (that still bongs when you plug it into a computer),
I have a program for downloading the u-boot.
I can try to make a version of u-boot that goes straight into fastboot.
So, does anybody have a bricked Glow?
You can check in Device Manager (devmgmt.msc) if you can find:
Code:
Human Interface Device
USB Input Device
USB\VID_15A2&PID_0063
Well, I've been playing around with all this.
I got a bit too arrogant playing around and swapping u-boots.
If you have a SBL (secondary bootloader, possibly u-boot) that looks good enough to the ROM bootloader
but doesn't actually work, you can sort of lock yourself out.
I had to disable (by grounding a test point) the eMMC to allow the ROM bootloader to run.
I've got to wiggle out and see if the boot options actually have their own test points.
I'm trying to get some more UARTs configured for GPS sensors.
The iMX6 bootloader is a known thing, but all the software out there seems half baked.
I tried one that was 7 Megs in size, but it didn't actually work.
My version weighs in at 68k, i.e. 1/100th the size.
So, I've got a cleaned up version (available in the signature).
Code:
C:\>imxboot
Found iMX6SL, VID=15a2, PID=0063
Security: Unlocked
Status: Idle
C:\>imxboot ub3
Load addr 87800400, DCD offset 002c, DCD size 0220
Found iMX6SL, VID=15a2, PID=0063
67 DCD ops processed
Write, addr 87800400, size 00039270
**********************************************************************************************************
Jumping to 87800400
Device disconnected correctly
Hi.
I have bricked Glow 3.
I tried to restore the bootloader according to your instructions and I have a problem
Code:
C:\>imxboot
Found iMX6SL, VID=15a2, PID=0063
Could not write device
companion79 said:
Code:
Could not write device
Click to expand...
Click to collapse
Hmm, strange.
Hold the reset button for 10 seconds. It should get a disconnect "bong".
Hold the reset button for 3 seconds. It should get a connect "bong".
Try imxboot by itself again.
It's strange because I have a separate error if the connection got disconnected.
I've been using imxboot alot myself on a Glow3 and never a problem.
Renate NST said:
Hmm, strange.
Hold the reset button for 10 seconds. It should get a disconnect "bong".
Hold the reset button for 3 seconds. It should get a connect "bong".
Try imxboot by itself again.
It's strange because I have a separate error if the connection got disconnected.
I've been using imxboot alot myself on a Glow3 and never a problem.
Click to expand...
Click to collapse
Reset button on the book? Where is this button? Perhaps I do not understand, perhaps you need to connect through the UART module? I was connecting through the command line.
companion79 said:
Reset button on the book? Where is this button?
Click to expand...
Click to collapse
Err, I meant the power button.
Renate NST said:
Hold the reset button for 10 seconds. It should get a disconnect "bong".
Hold the reset button for 3 seconds. It should get a connect "bong".
Try imxboot by itself again..
Click to expand...
Click to collapse
I performed all the actions, but the result is the same.
Code:
Could not write device
So write about an attempt to restore bricked nook Glow3, now position here is such
Code:
C:\>imxboot
Found iMX6SL, VID=15a2, PID=0063
Security: Unlocked
Status: Idle
C:\>imxboot ub3fb
Load addr 87800400, DCD offset 002c, DCD size 0220
Found iMX6SL, VID=15a2, PID=0063
67 DCD ops processed
Write, addr 87800400, size 00039270
**********************************************************************************************************
Jumping to 87800400
Could not read device
Now in Device Manager I find
Android ADB Interface:
USB\VID_18D1&PID_0D02&REV_0311
USB\VID_18D1&PID_0D02
I trying to run
Code:
C:\>adb reboot fastboot
error: no devices found
please help me what should I do next
companion79 said:
Now in Device Manager I find
Android ADB Interface:
USB\VID_18D1&PID_0D02&REV_0311
USB\VID_18D1&PID_0D02
Click to expand...
Click to collapse
Oops, sorry, my stupid. Fastboot uses its own bogus VID/PID.
You booted ub3fb, therefore you should be looking for fastboot, not ADB.
Windows handling of WinUSB drivers makes this all a bit obtuse.
Code:
C:\>imxboot ub3fb
...
Jumped to ...
...
C:\>fastboot devices
12345678 fastboot
C:\>fastboot boot nnglow3.img
C:\>adb shell
# ls -l
That's what I see now
Code:
C:\>imxboot ub3fb
...
Jumped to ...
...
C:\>fastboot devices
???????????? fastboot
C:\>fastboot boot nnglow3.img
Sending
Booting
Finished.
C:\>adb shell
Error: no devices/emulators found
After that, the device in the Device Manager disappears and is not detected again, reboot again returns the device to its original state.
companion79 said:
After that, the device in the Device Manager disappears and is not detected again.
Click to expand...
Click to collapse
Ok, but if at this point you pull the USB connection does Windows make a "bong" that something has been disconnected?
If so, that means that you've got something there and that the problem could be drivers for the ADB.
If not, that could mean your hwcfg is badly broken.
Try with the just-now uploaded Neo Noogie images that should be more resilient to bad NTX hwcfg.
https://forum.xda-developers.com/no...store-glow2-glow3-t3784575/page3#post81256205
Hi! In response to "imxboot ub3fb" the request writes "Could open file ub3fb". Where can I get this file? Please help!!!
egor_omsk said:
Where can I get this file?
Click to expand...
Click to collapse
Mmm, it's attached.
(It's the stock u-boot for the Glow3 with automatic jump to fastboot.)
Renate NST said:
Mmm, it's attached.
(It's the stock u-boot for the Glow3 with automatic jump to fastboot.)
Click to expand...
Click to collapse
Thank you very much
---------- Post added at 05:49 PM ---------- Previous post was at 05:45 PM ----------
imxboot
Found iMX6SL, VID=15a2, PID=0063
Security: Unlocked
Status: Frozen
egor_omsk said:
Status: Frozen
Click to expand...
Click to collapse
Yeah, that's an undocumented status that I get from the bootloader when it tried to load once, failed and didn't do a complete reset.
Do a long (10 sec) power off press, then a long (3 sec) power on press.
Renate NST said:
Yeah, that's an undocumented status that I get from the bootloader when it tried to load once, failed and didn't do a complete reset.
Do a long (10 sec) power off press, then a long (3 sec) power on press.
Click to expand...
Click to collapse
do not work
egor_omsk said:
do not work
Click to expand...
Click to collapse
Umm, you could be more specific.
You can't power it down, up, it acts the same?
Is it making USB up/down "bongs" on your desktop?
If nothing else, open the case, disconnect the battery for a few seconds.
Renate NST said:
Umm, you could be more specific.
You can't power it down, up, it acts the same?
Is it making USB up/down "bongs" on your desktop?
If nothing else, open the case, disconnect the battery for a few seconds.
Click to expand...
Click to collapse
Unfortunately it didn't work out
I wanted to share my experience in reviving my 2017 Shield Pro 500gb. I was at the point that it wouldn’t even turn on and all I would get is a black screen then after some time I would get 3 green flashes then the Shield would power off.
I was at the stage in which I couldn’t even backup the device and starting from scratch seemed very unlikely from my reading online. I had tried so many different things before I finally came to what follows.
Things I used
Samsung Evo 500GB
Nvidia shield TV pro files (someone kindly uploaded online) https://forum.xda-developers.com/t/nvidia-shield-tv-ssd-done.3402580/page-2#post-67426622
nv-recovery-image-shield-atv-pro-7.2.3-dev_rooted https://drivers.softpedia.com/get/g...Android-TV-Pro-Developer-Firmware-7-2-1.shtml
DD command line using Linux ( you can use Windows)
Rufus
OTG cable
ADB and Fastboot Drivers
SATA Adapter
First up I dismantled the Shield which although not overly complicated, you just have to be careful with the wires as the must be unplugged and SATA connector from the HDD.
So the HDD being completely dead I decided if I was going to successfully revive the shield I would use a SSD instead. I plugged the SSD into my windows laptop and reformatted it to a GPT partition scheme with a FAT32 filesystem using Rufus.
Now I would switch from Windows to Linux (I know you can do this with windows but all my previous successes have been through Linux) and find the folder containing – start.bin and end_976574630.bin and open your terminal. Plug your ssd into your linux running computer. Here I would use the command $sudo su and then the command fdisk -l to find what letter your drive is identified by. Let’s say the drive is identified as sdd.
Next write the command $dd if=start.bin of=/dev/sdd bs=4M
This process can take around 15 minutes give or take. Once the process has been completed enter $dd if=end_976574630.bin of=/dev/sdd seek=976574630. This will not take as long as the previous process. Make sure that you can see no errors once the process is complete and safely eject the drive.
Now it’s time to reassemble the Shield making sure again not to damage any wires and everything is correctly reconnected.
After I plugged it bag into power I just let it sit trying to boot for about ten minutes before turning it off.
For the next part I used Windows and you need to make sure you have the ADB and fastboot drivers installed on your computer. Find the folder named nv-recovery-image-shield-atv-pro-7.2.3-dev_rooted and open terminal, PowerShell etc here.
Fastboot reboot the hardware way
- Disconnect power cable
- Connect Shield to a computer using an USB cable connected to the micro USB port of the Shield.
- Connect power cable to SHIELD
- As soon as the green LED turns on -BUT NOT BEFORE- hold down the power button
- Count to three, then immediately release the power button
- i.e. one-one thousand, two-one thousand, three-one thousand.. LIFT!
- You should now see the fastboot menu on the screen.
To confirm the device is in fastboot mode type the command $fastboot devices and you should see your device listed. Now one at a time type the following commands.
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
Your Shield will begin to boot and will probably appear to stay on the four dots that turn into the Android logo for a little while. Give it 15 min and then unplug the power and repower the Shield. Now you will see your past boot and next setting the language and internet settings. Once you’ve done that you will be asked for Google credentials and the moment you’ve been waiting for the Nvidia Shield home screen. When I did it there was an update for 8.0 available which I did and everything worked fine. I then noticed an update for 9.0. Do not do this you will be back to square one which I found the hard way. For some reason it seems 8.0 that is compatible for this Shield model.
I just want to say a lot of this in formation has come from sources and articles I have read and have put together to suit my needs.
Big thanks to Tilator from XDA Developers and to Yaneca XDA Developer
Hey.. I have a nvidia shield 2017 Pro (I think? Not sure if the 2017 has a pro or not).
When I try and flash anything in TWRO with adb sideload I get error:
failed to read 16777216 bytes data at offset xxxx: I/O error
Im unable to to anything with it.. tried to format and tried a lot of things.. But I suspect disk is basically dead..
Do you think I can open it up and exchange drive to a regular 2.5" SSD and solve it?
Riverphoenix said:
I wanted to share my experience in reviving my 2017 Shield Pro 500gb. I was at the point that it wouldn’t even turn on and all I would get is a black screen then after some time I would get 3 green flashes then the Shield would power off.
I was at the stage in which I couldn’t even backup the device and starting from scratch seemed very unlikely from my reading online. I had tried so many different things before I finally came to what follows.
Things I used
Samsung Evo 500GB
Nvidia shield TV pro files (someone kindly uploaded online) https://forum.xda-developers.com/t/nvidia-shield-tv-ssd-done.3402580/page-2#post-67426622
nv-recovery-image-shield-atv-pro-7.2.3-dev_rooted https://drivers.softpedia.com/get/g...Android-TV-Pro-Developer-Firmware-7-2-1.shtml
DD command line using Linux ( you can use Windows)
Rufus
OTG cable
ADB and Fastboot Drivers
SATA Adapter
First up I dismantled the Shield which although not overly complicated, you just have to be careful with the wires as the must be unplugged and SATA connector from the HDD.
So the HDD being completely dead I decided if I was going to successfully revive the shield I would use a SSD instead. I plugged the SSD into my windows laptop and reformatted it to a GPT partition scheme with a FAT32 filesystem using Rufus.
Now I would switch from Windows to Linux (I know you can do this with windows but all my previous successes have been through Linux) and find the folder containing – start.bin and end_976574630.bin and open your terminal. Plug your ssd into your linux running computer. Here I would use the command $sudo su and then the command fdisk -l to find what letter your drive is identified by. Let’s say the drive is identified as sdd.
Next write the command $dd if=start.bin of=/dev/sdd bs=4M
This process can take around 15 minutes give or take. Once the process has been completed enter $dd if=end_976574630.bin of=/dev/sdd seek=976574630. This will not take as long as the previous process. Make sure that you can see no errors once the process is complete and safely eject the drive.
Now it’s time to reassemble the Shield making sure again not to damage any wires and everything is correctly reconnected.
After I plugged it bag into power I just let it sit trying to boot for about ten minutes before turning it off.
For the next part I used Windows and you need to make sure you have the ADB and fastboot drivers installed on your computer. Find the folder named nv-recovery-image-shield-atv-pro-7.2.3-dev_rooted and open terminal, PowerShell etc here.
Fastboot reboot the hardware way
- Disconnect power cable
- Connect Shield to a computer using an USB cable connected to the micro USB port of the Shield.
- Connect power cable to SHIELD
- As soon as the green LED turns on -BUT NOT BEFORE- hold down the power button
- Count to three, then immediately release the power button
- i.e. one-one thousand, two-one thousand, three-one thousand.. LIFT!
- You should now see the fastboot menu on the screen.
To confirm the device is in fastboot mode type the command $fastboot devices and you should see your device listed. Now one at a time type the following commands.
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
Your Shield will begin to boot and will probably appear to stay on the four dots that turn into the Android logo for a little while. Give it 15 min and then unplug the power and repower the Shield. Now you will see your past boot and next setting the language and internet settings. Once you’ve done that you will be asked for Google credentials and the moment you’ve been waiting for the Nvidia Shield home screen. When I did it there was an update for 8.0 available which I did and everything worked fine. I then noticed an update for 9.0. Do not do this you will be back to square one which I found the hard way. For some reason it seems 8.0 that is compatible for this Shield model.
Riverphoenix said:
I wanted to share my experience in reviving my 2017 Shield Pro 500gb. I was at the point that it wouldn’t even turn on and all I would get is a black screen then after some time I would get 3 green flashes then the Shield would power off.
I was at the stage in which I couldn’t even backup the device and starting from scratch seemed very unlikely from my reading online. I had tried so many different things before I finally came to what follows.
Things I used
Samsung Evo 500GB
Nvidia shield TV pro files (someone kindly uploaded online) https://forum.xda-developers.com/t/nvidia-shield-tv-ssd-done.3402580/page-2#post-67426622
nv-recovery-image-shield-atv-pro-7.2.3-dev_rooted https://drivers.softpedia.com/get/g...Android-TV-Pro-Developer-Firmware-7-2-1.shtml
DD command line using Linux ( you can use Windows)
Rufus
OTG cable
ADB and Fastboot Drivers
SATA Adapter
First up I dismantled the Shield which although not overly complicated, you just have to be careful with the wires as the must be unplugged and SATA connector from the HDD.
So the HDD being completely dead I decided if I was going to successfully revive the shield I would use a SSD instead. I plugged the SSD into my windows laptop and reformatted it to a GPT partition scheme with a FAT32 filesystem using Rufus.
Now I would switch from Windows to Linux (I know you can do this with windows but all my previous successes have been through Linux) and find the folder containing – start.bin and end_976574630.bin and open your terminal. Plug your ssd into your linux running computer. Here I would use the command $sudo su and then the command fdisk -l to find what letter your drive is identified by. Let’s say the drive is identified as sdd.
Next write the command $dd if=start.bin of=/dev/sdd bs=4M
This process can take around 15 minutes give or take. Once the process has been completed enter $dd if=end_976574630.bin of=/dev/sdd seek=976574630. This will not take as long as the previous process. Make sure that you can see no errors once the process is complete and safely eject the drive.
Now it’s time to reassemble the Shield making sure again not to damage any wires and everything is correctly reconnected.
After I plugged it bag into power I just let it sit trying to boot for about ten minutes before turning it off.
For the next part I used Windows and you need to make sure you have the ADB and fastboot drivers installed on your computer. Find the folder named nv-recovery-image-shield-atv-pro-7.2.3-dev_rooted and open terminal, PowerShell etc here.
Fastboot reboot the hardware way
- Disconnect power cable
- Connect Shield to a computer using an USB cable connected to the micro USB port of the Shield.
- Connect power cable to SHIELD
- As soon as the green LED turns on -BUT NOT BEFORE- hold down the power button
- Count to three, then immediately release the power button
- i.e. one-one thousand, two-one thousand, three-one thousand.. LIFT!
- You should now see the fastboot menu on the screen.
To confirm the device is in fastboot mode type the command $fastboot devices and you should see your device listed. Now one at a time type the following commands.
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
Your Shield will begin to boot and will probably appear to stay on the four dots that turn into the Android logo for a little while. Give it 15 min and then unplug the power and repower the Shield. Now you will see your past boot and next setting the language and internet settings. Once you’ve done that you will be asked for Google credentials and the moment you’ve been waiting for the Nvidia Shield home screen. When I did it there was an update for 8.0 available which I did and everything worked fine. I then noticed an update for 9.0. Do not do this you will be back to square one which I found the hard way. For some reason it seems 8.0 that is compatible for this Shield model.
I just want to say a lot of this in formation has come from sources and articles I have read and have put together to suit my needs.
Big thanks to Tilator from XDA Developers and to Yaneca XDA Developer
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Riverphoenix said:
I just want to say a lot of this in formation has come from sources and articles I have read and have put together to suit my needs.
Big thanks to Tilator from XDA Developers and to Yaneca XDA Developer
Click to expand...
Click to collapse
Hello,
which exact model EVO 500gb did you use ?
I have tried with the EVO 950, EVO 960 and the EVO 970 500Gb drives and neither of them are able to finish the second image file end_976574630.bin
The disk runs out of capacity. I had even tried to alter the seek sector value but then drive remains dead.
Here is my output as I posted in Tilator’s original thread
dd if=end_976574630.bin of=/dev/sdb seek=976574630
dd: writing to '/dev/sdb': No space left on device
198535+0 records in
198534+0 records out
101649408 bytes (102 MB, 97 MiB) copied, 27.1625 s, 3.7 MB/s
@Riverphoenix, I tried to write those 2 files to my ssd the other day and I am getting the "permissions denied" error. I am on a mac using terminal. Shouldn't be too different. I didn't use the sudo command though. Is that something I need to do? I am "newish" at this sort of thing and trying to understand it all. Also did you just plop the 2 files on your linux desktop or how did you access those files after you moved from your windows machine to your linux machine? Do i need to terminal into the folder with those files or terminal into the drive I am writing those files to?