Database Users

Recovery finishes in 2 mins but fails

Hi Everyone,
Got my Shift, thought Vista was so slow decided to put on Ubuntu.
Had enough of that, hit FN F3, set recovery MBR YES and the continue.
Starts up the WINPE, I see Diskpart fly past and a few "cant find xxx" but flashes to fast to see and then says "All done, power off using slide".
Reboot and I get "BOOTMGR is missing"
The whole recovery process takes 2-3 minutes so my guess is the cant find errors are big ones as I would expect it to take a while?
Also no keyboard access or mouse. Tried USB keyboard no luck, I wanted to look at the batch files so I could slow them down. but no access.
Any ideas?
Thanks
Russ

Remove any SDHC cards from the slot if you have any.

Hi, nothing added to it. Just wondered from everyones experience when you perform a recovery from this FN 3 how long does it take?
Russ

About 8-9 minutes on WINPE and 10 minutes more starting vista for first time and rebooting until you can use the system.

RussST24 said:
Hi Everyone,
Got my Shift, thought Vista was so slow decided to put on Ubuntu.
Had enough of that, hit FN F3, set recovery MBR YES and the continue.
Starts up the WINPE, I see Diskpart fly past and a few "cant find xxx" but flashes to fast to see and then says "All done, power off using slide".
Reboot and I get "BOOTMGR is missing"
The whole recovery process takes 2-3 minutes so my guess is the cant find errors are big ones as I would expect it to take a while?
Also no keyboard access or mouse. Tried USB keyboard no luck, I wanted to look at the batch files so I could slow them down. but no access.
Any ideas?
Thanks
Russ
Click to expand...
Click to collapse
I had the same problem after installing ubuntu. You must get a recovery partition from a guy with your same language (if you want) and follow the instructions of Pof to overwrite your recovery partition. Then It will work again but I had to do it twice. Maybe first time It failed. And remember that dump/reflash last 4 hours.
Dani

Hi Thanks,
Any chance anyone knows where I can get the English UK version? I guess the US one will work too.
Thanks
Russ

Hi.
Other shift's user should dump his recovery partition for you

Hi, I hope so as HTC said they do not have any recovery CDs and I would have to return it for repair
I can install Vista myself but they wont give me access to download the drivers? They have a lot to learn if they want to move into OS support. A simple cheap DVD in the box would save all this grief.
Russ

RECOVERY Partition Fn+3 run a Recovery System and reinstall Vista OS.
My Recovery is Crashed and i wait to dump and upload Image for Recovery Image and Restor in My HTC Shift

RussST24 said:
Hi, I hope so as HTC said they do not have any recovery CDs and I would have to return it for repair
I can install Vista myself but they wont give me access to download the drivers? They have a lot to learn if they want to move into OS support. A simple cheap DVD in the box would save all this grief.
Russ
Click to expand...
Click to collapse
well I can upload the Program Files/HTC (faster than the full recovery dump), has some HTC driver stuff inside.

I am currently backing up the recovery partition on my shift as per pof's instructions (using this slax thing off usb).
I see I can expect it to go for 4 hours why is bs set to 1? any reason for that??
anyway if this works then I'll upload it. it is WWE GSM shift. just need to figure out where to upload 3GB and it won't be fast either
note: the dd command didn't work, so I tried dd if=/dev/hda of=/mnt/hda1/shift-vista-recovery.bin bs=1 skip=36773560320
with /dev/hda1 it said no such directory
note2: if you're paranoid check dmesg before doing the dd to see if you get same values for HDA as pof: http://pof.eslack.org/blog/

cmonex in PM send a FTP server for Upload a Image !!!

well, ok, I stopped dd after 4 hours because it only did 98MB and then used: dd if=/dev/hda of=/mnt/hda1/shift-vista-recovery.bin bs=16384 skip=2244480
that was very fast and file comparison utility says it's the same for the first 98MB as the bs=1 98MB file is (i didn't delete it).
if anyone knows a way to fully verify the contents then let me know, I don't want to start upload until then. thanks.

Run USb Slax
and
write dmesg in command line, find where SDA (40Gb)
mount /dev/sda1 /mnt
dd if=/dev/sda of=/mnt/shift-vista-recovery.bin bs=1 skip=36773560320

micron said:
Run USb Slax
and
write dmesg in command line, find where SDA (40Gb)
mount /dev/sda1 /mnt
dd if=/dev/sda of=/mnt/shift-vista-recovery.bin bs=1 skip=36773560320
Click to expand...
Click to collapse
but that's what i did already, and it was goddamn slow
anyway transferring the dump to my PC that is on lan, for faster upload

Go to upload on FTP.
I post Link to Download hear or PM for you .

micron said:
Go to upload on FTP.
I post Link to Download hear or PM for you .
Click to expand...
Click to collapse
I replied!

Here is my solution
boot the xp disc with usb cd/dvd drive.
Use XP to fomat the hdd again ( don't use quick format , use low level complete format. ) ... after finish format.. Reboot your htc shift ( **** ) ..., PRess FN3 .. to recover.. then it work... , sometimes, you need to try several time of recover .. to make it work..
It is the bugs in HTC.
Since HTC care in HK trying to charge me us$1000 for service charge, even I just brought it for few day... ( still with warranty ) claming that the other installing of software damage the motherboard, powerboard , touch board. , and it spoil the warrnty terms.
HTC Care ( HK ) is a act like a cheater... ( Since I use my own method to fix the Shift ) , they are telling lie to cheat customer...

F3'ed Vista. Reinstalled and updated. Blue Screen and now the HD is Slow

Hi.
Bought a second hand Shift yesterday.
Device was working fine, but i reset it with F3 to get a clean install.
Updated all over WindowsUpdate, Downloaded all drivers from HTC in the order as described.
Today i suddenly got a blue screen after the device was hanging.
After reboot the Registry was unreadable so it wouldn't boot, and it took for ever to get to the read error + a few blue screens in between.
Now when i hit F3 and reset, it takes for ever to load the initial files.
The white bar crawls about 1cm to the right in about 20minuts........
Is the HD totally F..... up or what do you think?
HD LED is constantly on, instead of the more normal constant-blink-constant behavior

So i took my Vista Ultimate CD and copied it on to a Mem stick.
Boot fine and starts the install process, but somethings not quite right.
Slow to copy files to the disk, mostly it freezes at some point.
Always stops 55% when unpacking files.
Anyone known with the Vista safe mode options, so i can run a check and perhaps repair of the partition?
Might work.

I had the same problem and sent it back to htc they reimaged it and sent me it back, it booted ok first time, then crashed and would not boot or install vista again (fn+f3 or usb imaged I had) I then sent it back again and they put in new hdd and its been fine ever since.
You could run dft (drive fitness tool) its free and can be loaded from usb, just to check hdd.

Well I might as well document my process on recovering a bad HD as i go, for later reference :
I got Vista Ultimate on my main PC, so why not try to boot from an original installation CD.
To do this we need to Copy the CD on to an USB Stick.
I Use a Kingston 8GB DataTraveler.
On your Desktop PC go :
Start -> Run -> cmd.exe (Command promt opens)
Put your USB Stick in
Type the following
diskpart
list disk (And take note of which is your USB Stick = Disk 0, Disk 1, etc.etc.)
select disk ? (As you found out above)
clean
create partition primary
select partition 1
active
format fs=fat32
assign
exit
Now we need to copy the Vista DVD on to the memory Stick (Stick is F: from now on):
Put your Vista DVD in the DVD Drive (We call that E: from now on)
Then type
xcopy e:\*.* /s/e/f f:\
It takes a while, so go ahead and surf some nasty xxx sites while you wait....you know you want to
BUT don't take out the Stick before cmd.exe is back at regular promt.
Done.
Shut down Shift Vista if it ain't already
Put the Stick in it.
Turn on and press FN+10 at the Boot menu
Choose to Boot from your Stick.
First Vista install window you choose your local settings
Then choose the Repair option/link
Deselect any HD and click Next
Open Dos/Command promt (I'm on Norwegian and it's called Ledetekst go figure) you'll recognize the Icon
The Prompt should be at X:\Sources>
HERE I WOULD LIKE TO COPY OUT RECOVERY PARTITION DATA.
If you know how to show and activate and xcopy it out of there, please do leave a comment
First we will test the drive with chkdsk :
Type :
chkdsk c:
If you get errors, try and run
chkdsk c: /b /r /f (the /b parameter should include /r which should include /f but write them all)
Hopefully it will repair your disk and mark bad Clusters accordingly.
Try to do a recovery with the FN+F3 at boot.
Mine did some repairs, but ends with an unspecified error at step 4 of 5 :-(
------------------
If not, Then :
Type :
diskpart
list disk
You should see
Disk 0 34 G bytes (This is your HD)
Disk 1 7656 M byte (This is your Stick, but would match your size)
select Disk 0
clean
create partition primary
select partition 1
active
format fs=ntfs (This will take loooong time, so just head on over to your xxx site again.)
assign
exit
Now you run chkdsk to check for faults again:
chkdsk
A) If no error, reboot and try FN+F3 to recover from the recovery disc.
If the recovery fails, you have to boot Vista installation again and do chkdsk to be sure the failed recovery haven't messed it all up again. (Mine didn't work)
B) If errors type:
format c: /p:1 this will reset every sector to 0 (back to the xxx again)
then
chkdsk /b /r /f
Hopefully you will get no errors.

Hi scott.
Haven't figured out how to get those peski Floppy dos tools to install on to an USB stick, they always want to go to A:

And anybody with knowledge of how to hide/unhide partitions in DOS/cmd, please scream out

hp usb storage tool - Will help make usb with dos tools
http://forum.xda-developers.com/showthread.php?t=390003 hide/unhide partitions in DOS/cmd

Ok thanks for the HP tip.
I have seen Mr. riki0081's thread, but i wanted to stay in Vista dos if possible.
Mainly because i only have one USB Stick, secondly because I'm stubborn
Thanks

It's going to service.
It just wont stop making read/write errors, and now it wont even show up in BIOS any more.
Has the all to well known sound klik klik klonk......klik klik klonk......etc. etc. of a failed HD

How I unbricked my Hard-Bricked Samsung Galaxy Tab 4 SM-T337A...

Hello, my name is Marc-Yvan from Douala, Cameroon and I will tell you the whole story about how I successfully unbrick my Android Tablet. My aim is to share with you some tips about how to recover from a desperate situation of having an unusable tablet.
How I hard-bricked my Tablet:
First of all, let me tell you how I hard-bricked my beloved tablet after trying to unlock it from its original network lock. I got this tablet from a relative who live in USA but it was unfortunately network locked to the AT&T network. So I tried to unlock it by multiple means (by myself). I found a cracked software called “Octopus for Samsung” who was said able to unlock any kind of Samsung phones/tablet. When I tried to unlock my Tablet, the software starts the work and then told me that the device will turn off and turn on after a short time. But the Tablet did not turn on anymore and I spend 02 months trying to bring it back from the grave.
Definition:
Let me explain to you what is called a hard-bricked smartphone/tablet. It’s simply a smartphone/tablet which is unusable, doesn’t turn on (desperate black screen) and doesn’t react to any stimulation. But you have to know that these hard-bricked devices are displayed as unrecognized devices when plugged onto a computer. So a hard-bricked device is not a physically damaged device but is a sort of hardly logically damaged device which cannot boot at all and is not recognized by common flash tools such as Odin, etc.
How I unbricked my tablet:
Lucky Context (GOD’s help):
Fortunately, GOD helps me by guiding me through this situation in order to recover from it in a miraculous manner. I will explain it to you in a couple of points:
1- My Tablet was rooted before the incident. I did it by using an application found in play store: “Kingroot.apk”.
2- My Tablet was equipped with some tools like “Es explorer” and “Terminal Emulator”. You will understand how it fortunately helped me before the incident.
3- The real hand of GOD: In my quest of finding a mean to network unlock my tablet, I tried a method which was asking to save some partitions of the eMMC (A kind of processor memory. Sorry but I’m not an expert ). So I saved it to the memory of my Tablet and then transfered it to a folder in my computer (By using command lines with “Terminal Emulator”). This actually helped me after to revive my tablet.
Advice N° 1 (Prevention)
Before trying to explore the whole abilities of your Tablet by flashing it or trying to network unlock it; Do a backup of the primary boot partition of your eMMC by executing this command in the “Terminal Emulator” of your rooted device:
cat /dev/block/mmcblk0> sdcard/mmcblk0.img
Be careful, this command could save the life of your beloved Tablet. This command will actually copy the primary boot partition of your eMMC in a disk image which has the same name. So you have to keep that disk image in a safe place such as your computer or an external removable disk.
Advice N° 2 (Resolution)
The Story:
In my desperate actions trying to revive my hard-bricked tablet, I read tremendous forum posts and tried countless methods. Which lead me to install a new OS in my computer. It was actually Linux Ubuntu 16.4. I found a method which told me to try to write some kind of partitions images down to an SDCard to boot my Tablet with. But the partitions images proposed by the method didn’t succeed in recovering my Tablet. So some days later, when I turn on my computer, I fortunately found a file opened; it was the primary boot partition image file of my tablet that I saved before the incident (The real hand of GOD). So I decided (Inspired by the Holy Spirit) to try the previous method with the original boot partition image file of my tablet.
The Tip:
You will need an SDCard with a correct format (FAT32) and size (16Gb or 32Gb). You will also need to work in a Linux command line terminal. To write the boot partition image in your SDCard you will have to execute this command line:
sudo dd if=mmcblk0.img of=/dev/sdb bs=1024k status=progress
Note: The sd card may not be sdb though. In order to confirm, before writing, browse to /Dev and look at the properties of sdb to ensure it is in fact there (it might be sda, sdb, sdc, etc...). You can also try to unplug and then plug the SDCard to see the changes.
The Last Step (Eureka!!!)
The last step is just to insert the SDCard into the slot of your Hard-Bricked device, Turn it on and then feel its vibration that will let you know that your mission is completed. Your device is alive again.
Conclusion
The only conclusion that I can give is to NEVER GIVE UP when you are trying to solve a problem. You can be closer to the solution than you think.
Good Luck!

What are the chances you would upload the boot partition for me?
I hard bricked mine also, but unfortunately I didn't make a backup. Would you be kind enough to upload the bin file you dumped? I've looked everywhere and no one seems to have an emmc dump of this thing. lol

[guide] repair hard bricked devices with deleted bootloader (sboot)

I'm writing this in android development section because this is only section for both models, i hope this is not a problem.
Also i want to say thanks to sataccount from gsmhosting, he found working map at the end.
This guide is for hard bricked phones, where bootloader is destroyed and there is no any tools which recognize phone.
When you connect phones without bootloader Windows detects them as exynos7420 in other devices in device manager.
All this is achieved using trial/error method and I still don't know real sboot map and where is what in sboot.bin.
What i found till now is that sboot consist from this parts:
1. fwbl1 bl1
2. bl2 bl2
3. el3_mon el3
4. bootloader bootloader
5. tzsw tzsw
I repaired my g925a and have files only for this model, but i will try to explain how to prepair files for any other model.
We have to use same version of bootloader which was previosly in phone, or if you are unsure use latest sboot.bin.
Download tools: http://www.mediafire.com/file/sg5m2ti3k6a63z5/USB_Down_Load_32bit.zip
In folder USB_DownLoad_Tool there is a folder Disk1
Connect phone and hold power button.
Windows will detect exynos7420 device, install Driver:
click manually,
com and lpt ports,
have disk,
point to data1 folder.
Don't run setup from Data1 folder!!!
Now we have to copy
WinDNWApi.dll
WinDNWApi.lib
in:
c:\Program Files\SAMSUNG\Exynos USB Driver\Drivers\
Probably there is no this folder, just create it and copy 2 files.
Don't copy WinDNWApi.dat as it is written in original manual, this file is for older exynos chip and procedure will not work, everything works without this file (it only has maps for 5250 and some other cpu)
Now we have to create boot files.
Download sboot.bin for your device, as i wrote best to find same bootloader which was in device before brick.
In some hex editor create 4 files (i'm using frhed, just click copy, enter offset, new file, paste, save and over again for all four files) with this map (again thanks to sataccount):
Novi1.bin 0..0x1FFF (size 0x2000 or 8192 )
Novi_2.bin 0x2000..0x31FFF (size 0x30000 or 196608)
Novi_3.bin 0x32000..0x3dfff (size 0xC000 or 49152)
Novi4.bin 0x3E000..10EFFF (size 0xD1000 or 856064)
This is all without tzsw. If phone still does not enter to odin mod, make last file from 0x3E000 to the end of the file (18F10F) and try again.
Start multiuploader.exe
Connect phone and hold power button.
Browse and find SH-usb-booting.cfg (in attached file proba folder, that is where you will probably prepare all boot files)
click start and phone will enter odin mode.
Start odin and flash sboot and everything else.

First of all thanx this is a real sharing is caring thing.I'm seeing a way to downgrade bootloader here as tzsw gets separated well this can be done by daring dev who can take risks.

I'm not sure about downgrading.
When i tried to repair my phone, first i tried with 5.1 sboot (eng and normal). It hangs on second file. It checks somethings before start to load real bootloader. Maybe to fill whole device with zeros with dd command (deleting pit can be enough, but also maybe it ignores PIT and read some specific bytes on sda) and then restoring phone as it is just builded in factory. Of course first to make backup of EFS etc...
Even with downgraded sboot, i'm not sure can we use 6.0 and 7.0 roms?
Best way is someone with IDA knowledge to find bytes for unlocking and we can write them to sboot with dd if="something" of =/dev/sdb bs=xx count=xy
At least it is now repairable if it is bricked after that

Good find, thanks.
How did you break the bootloader (sboot) anyway?

Dd if=sboot_from_925f of=/dev/block/sdb
I had engineering boot (kernel) with adb root access. And after that phone is dead.
On 925a sboot is on sdb (just sdb without numbers), cm.bin on sdc. Probably same on all variants.

Hi
I'm not sure I understood the hex files creation step.
Start byte : 0
End byte : 0x1FFF
Size : 8192 for Novi1.bin for example
Right ?

Yes, that's it
Just compare with my files if unsure.

OK Thanks
Congrats for this amazing guide

G928c dont know version inside.
I tried 7.0 but tool hang after novi1 transfer.
with android 6 sboot all 4 files transfer succeed but no download mode
if I do 0x3E000 to the end of the file, tool hang after 1st file.
according to customer 7.0 was inside before brick.

ok I tried different 7.0 which take me to on display usb recovery mode.
but phone not detected by pc after reset by keys now phone completely dead.
no exynos mode, no download mode nothing.
PC not sensing phone anymore.

Did you restore exynos mode?
Try to add tzsw ( novi4 should be from 0x3E000 to the end of sboot.bin).

yes I open phone and re-insert battery. Now exynos mode.
(novi4 should be from 0x3E000 to the end of sboot.bin) give me USB Recovery Mode. but as previous post no detection.
do sboot contain tzsw ?
if so what is address for tzsw ?

tzsw is from 10F000 to the end of file. But you added it and phone loaded when you made novi4 from 0x3E000 to the end of sboot.bin.
I think it is still problem with different sboot version, it must be same as version previously in phone. Try few more sboot bin.
You don't have to pull out battery, just press volume down and power for more then 20 seconds, it is same like you reinsert battery.

I reconfirmed version form client and he said he is sure about 7.0 version.
this variant have only 3 files of 7.0 and I tried all sboot from 3 available versions.
zogu said:
You don't have to pull out battery, just press volume down and power for more then 20 seconds, it is same like you reinsert battery.
Click to expand...
Click to collapse
yes this is the way but in my condition not reset after 30sec and I feel phone heat too. thats why I decide to open phone.

Phone enter download mode and pc does not detect it, it is really strange, like it hangs after entering mode. Maybe is phone (flash memory) broken?
try with jig cable, maybe this can help, it is only idea i have...

zogu said:
Phone enter download mode and pc does not detect it, it is really strange, like it hangs after entering mode. Maybe is phone (flash memory) broken?
try with jig cable, maybe this can help, it is only idea i have...
Click to expand...
Click to collapse
I also think this can be memory issue.
tried all possible ways but no success.
device returned to customer.
anyways thanks for this guide and your quick response.
:good:

I dd over sdb, BOTA0 BOTA1 RECOVERY CACHE and SYSTEM, am i sol on this one? Phone doesnt get detected by pc. Even tried unplugging the battery. For those curious why...I found out theres a partiton flag set on all of those partitions. Its SYSMAGIC X , X being a number. Lowering that number on the system by dd' ing sda18 and rebooting, results in a fw error, binary 3 device 4. Aka phone thinks system installed is lower then what it really is. I know u cant downgrade the bootloader using your method, but if u dump sdb, and edit the sysmagic line in a hex editor, dd it back. It will now be corrupt, I wonder if you can now downgrade to the version we faked. Anyone care to give it a trytry?

how i open multidownloder it giving massage mfc110u.dll missing when i try to install it said opreating sysytem not supported i have window 7 32 bit sp1 but its not working

jhony352 said:
how i open multidownloder it giving massage mfc110u.dll missing when i try to install it said opreating sysytem not supported i have window 7 32 bit sp1 but its not working
Click to expand...
Click to collapse
It worked for me on win 7 32 bit...
Try to reinstall Visual C++ redistributable 2012
https://www.microsoft.com/en-us/download/details.aspx?id=30679

cfg file for s6 sm-g920p
thx its working
Please can you help me from where i can download cfg file for S6 sm-g920p i have sboot.bin file it is in bin format and this file is not open and work in mfc multidownloader

shield TV 2015 bricked ?? no root no update...

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.