Related
Check out this site, it's the guys from Mobile01 again trying to replace the existing HDD to CF card disk, you will see the RAM and HDD in closer view.
Result......? it doesn't work, because after install the CF disk, it needs to proceed to re-install the OS, and the OS is store in the original HDD, guess this guy didn't find a solution into this. However i do believe we will be able to sort this out in the near future.
Also replacing the RAM is currently not possible, there are no 2G module out there for sell yet, I guess we need to wait for the Hardware to catch up.
Go and check out the pic in this link:
http://www.mobile01.com/newsdetail.php?id=5414
how about cloning the disk to CF first ?
Maybe use a clone proggy to clone the actual HDD to the CF card first, then mount / solder it ?
Maybe i'm too dumbed down by windows OS'es, but if you clone the HDD bit for bit to the CF card, my guess is that it will boot straight away.
Maybe one needs to fiddle a little with the MBR, or the device ID, but that should be it really.
Please keep us posted.
Are the installation files on the harddisk?
I read in another thread that the installation files are in ROM soldered to the motherboard and that all you need to do after installing a new harddisk is to press FN F3 at bootup to restore Vista. This might be wrong and I'd actually wonder what the hidden HD partition would be for if it should be true.
Anyway, if they didn't make any mistakes installing the CF card, they should be able to install Windows from a USB drive.
However, have you seen what they installed instead of the 40GB HD? A 8GB CF card. This will never be enough to hold Vista, so I wouldn't be surprised if that was the cause for their problems, the installation routine might just balk at "insufficient space".
As the linked website is using Chinese (I guess, or is it Japanese, Korean, ...) characters and language, somebody able to read this would have to evaluate what they are doing.
Swop hdd
The problem with swopping the hard drive is it has since been discovered that the drive is artificially sized down to protect a HIDDEN partition using special features of IDE drives in conjunction with the BIOS.
I'm aware of no program on windows that will clone this special hidden area as the drive removes it and it is only visible on boot. However linux can see there is a hidden partition but i'm unsure not knowing much about linux whether it can clone it.
If you simply swop out the hard drive you will lose the ability to FN+F3 on boot to restore the image.
I would suggest therefore you do the following before the swop out.
1. Boot Shift
2. FN+F3
3. Do a full factory restore
4. Switch off when directed
5. Attached external USB CDROM/DVD drive
6. Use BartPE
7. Power on Shift and boot immediately to BartPe
8. Once booted insert a usb hard drive / key using the 3-way hub, so you have the cd and hdd connected via USB
8. Ghost / clone the drive from C: to your external hard drive / pen
You now have ghost image that you can restore to on the new hard drive (ie. not a FN+F3 restore process but a CLEAN ready to initial boot installation of Vista).
Regards
Blitz
The vista installation files are in a hidden partition on the hard drive.
This is why the 40gb drive shows as a 34.2Gb drive.
mw65719 said:
I read in another thread that the installation files are in ROM soldered to the motherboard and that all you need to do after installing a new harddisk is to press FN F3 at bootup to restore Vista. This might be wrong and I'd actually wonder what the hidden HD partition would be for if it should be true.
Anyway, if they didn't make any mistakes installing the CF card, they should be able to install Windows from a USB drive.
However, have you seen what they installed instead of the 40GB HD? A 8GB CF card. This will never be enough to hold Vista, so I wouldn't be surprised if that was the cause for their problems, the installation routine might just balk at "insufficient space".
As the linked website is using Chinese (I guess, or is it Japanese, Korean, ...) characters and language, somebody able to read this would have to evaluate what they are doing.
Click to expand...
Click to collapse
The reason why they install 8G CF card is for faster read/write speed, and i guess it will also decrease battery usage since it's not mechanic moving like the original HDD.
Thanks very much wu5262 - I fully understand why they want to use a CF card instead of the harddisk .
I was pointing at the meager 8GB size they picked.
If you want to install Vista, use at least a 16GB card. If you can get your hands on one, use a 32GB card (admittedly not so cheap). For an example: http://www.amazon.de/Components-32GB-CompactFlash-HighSpeed-Karte/dp/B00162ZOPW.
I've been having an absolutely horrendous time installing Window 8 onto an SSD i bought. Let me give you a rundown of what's going on.
I bought a 120gb SSD off of my friend for a new laptop I was getting. My intentions were to replace the 1TB HDD in this laptop with the SSD and use the HDD as an external, so I can have massive speed increases in everyday computing activity. Originally, I thought the laptop had 2 hard drive bays, making it simple to install Windows onto it. However, due to my negligence to pay attention, it turns out that this laptop only has 1 hard drive bay. So next, I say, "oh simple, I'll just get an external HDD enclosure and install windows that way." Nope, cockblocked by Microsoft on this one; I figure out the hard way that one cannot install Windows onto a device via usb. I then researched some more and found "Windows 7 USB DVD Download Tool". I tried installing Windows onto a flash drive, but then accidentally formatted my camera's 16gb memory card losing hundreds of pictures. In vain, I should add, since it didn't even work in the end. Currently, I am stuck on how to install windows 8 onto my external SSD to later swap with the internal HDD. Hopefully this paragraph made sense lol. Any help here is greatly appreciated.
You've got the enclosure you need for the 1TB drive, right? What's stopping you from swapping the drives now, and installing the OS on the SSD when it's mounted internally? Alternatively, create a new partition on the current drive that is the same size or smaller as the SSD, and then install Win8 there. You can then copy that partition (the whole thing, using something like dd on linux) to the SSD, although getting the bootloader to come along for the ride would be tricky.
Also, with all due respect, if you managed to lose hundreds of pictures that weren't yet copied off the camera card while attempting (and failing) to install Win8 on a flashdrive, this might be a "don't try this at home" moment. I'm sorry for your loss, and I realize it was probably a very simple accident - confusion of which drive you were targeting, perhaps - but messing around with disk partitioning and advanced installation techniques without somebody who knows what they're doing guiding you is a dangerous idea.
Windows 2 Go locks down a number of system features, which limit its usefulness as a day-to-day OS. There's some configuration in the registry that controls this, so you might be able to use the W2G installation and then "fix" it, but you may want to do some research into W2G before attempting this.
I guess one could call me a noob when it comes to Windows lol... my expertise is Android
So I can swap the ssd and hdd while the computer is running? Wouldn't that cause all sorts of errors? Because when I tried swapping them, I couldn't get windows to boot from the hdd (which was in the external enclosure)
Sent from my DROID4 using xda app-developers app
Take the HDD out. Put SSD in. Put windows install disk in (not upgrade disk, most disks sold are upgrade only, you need install). Boot from instrall disk, follow instructions.
The hard disk replacement can only be dome when powered off. SATA devices do not support hit swapping and may even be damaged by it.
We ignore the HDD completely. Once win8 is on the SSD then you can put the HDD in the USB enclosure, plug it into your laptop now running win 8 and retrieve your files.
Copying wijndiws between different hard disks rarely works in my experience.
Oh, for the SD thing. Partitioning SD cards is not recommended, not all laptops can boot from SD either so it may have been completely futile.
If you don't have an install disk (only upgrade), you can copy the contents of your current Windows OS volume onto the SSD and then do the swap, which should cause the installer to think you already have Windows installed (if perhaps in a corrupted form). If you can do a full partition clone, then it needn't even be a corrupted copy; you could simply clone Windows onto the SSD (it may demand to be reactivated if you do this; ignore that) and then use an upgrade install.
Contrary to the name, upgrade installs do not need to be in-place upgrades; you can in fact wipe the entire SSD (and I recommend you do so) using the advanced install options once the installer has verified that these is (or was) a Windows install there.
I've done it on my HP DV6, the process was with a samsung ssd to clone the hard drive on the ssd with the program furnished by samsung. I expect there are other programs doing the same. I used a second external HD to take the files that didn't enter the SSD (256 GB).
Then I swap the disks (SSD internal) and I replace the DVD reader by the old HD repartition and format it (Now I use an external DVD Writer.
Then I upraded with win 8.
Take a bit of time but works
I hope it helps
François
Sent from my ASUS Transformer Pad TF300TG using xda app-developers app
Hi,
Bit of a coincidence, but after the 7.02 update, my shield died. After investigation I found that the Hdd had fried. I have bought from Amazon an exact replica of the 500gb hdd that was installed in the shield.
My problem now is trying to get any firmware onto the brand new HDD. When plugged into the PC (win 10) all i get in device manager, is an unrecognized APX device, with the yellow warning triangle. I have downloaded and tried to update the drivers to this device from the Nvidia developers site, these are not recognized. I have adb and fastboot installed, this also does not recognize the device. obviously, i cannot
get the device into fastboot via the power button, due to the hdd being blank, and unable to get any bootloader or image transferred onto the HDD. I have searched the internet for fixes, but as yet no avail. So to summarize, Brand new HDD of original specs in the 500GB 2015 shield, not recognized by windows, and cannot get adb fastboot to see it, or put the shield itself in fastboot mode. Any ideas much appreciated.
Fried Hard Drive
chromedome21 said:
Hi,
Bit of a coincidence, but after the 7.02 update, my shield died. After investigation I found that the Hdd had fried. I have bought from Amazon an exact replica of the 500gb hdd that was installed in the shield.
My problem now is trying to get any firmware onto the brand new HDD. When plugged into the PC (win 10) all i get in device manager, is an unrecognized APX device, with the yellow warning triangle. I have downloaded and tried to update the drivers to this device from the Nvidia developers site, these are not recognized. I have adb and fastboot installed, this also does not recognize the device. obviously, i cannot
get the device into fastboot via the power button, due to the hdd being blank, and unable to get any bootloader or image transferred onto the HDD. I have searched the internet for fixes, but as yet no avail. So to summarize, Brand new HDD of original specs in the 500GB 2015 shield, not recognized by windows, and cannot get adb fastboot to see it, or put the shield itself in fastboot mode. Any ideas much appreciated.
Click to expand...
Click to collapse
Sorry to hear your HD died, mine died last month. First you can not see anything on the HD, because it has special encryption. Just using a firmware will not work. You need to have a new SSHD drive, or as i did replace with 500 gig SSD. Now here is the problem you need to make a bit by bit image of the drive, if it is fried, you will not be able to do it. I was lucky, my son has the same drive so i was able to make my image, There are many steps to getting a new drive up and running. First you need to find a Friend or someone who would let you use there Shield Tv Pro, you need to ope the Shield tv and take the HD out of the borrowed one, then you need a USB SATA connector for the HD from the Borrowed HD and you need to have 500 gig of space on a PC or Laptop HD to store the Image to, it takes about 4 hours to make image, then you hook up the New HD Drive to the SATA Connection and then copy the image From PC to the new drive, that takes about 3 hours, then carefully put drives back in there Shield Tv boxes. there is a small image software to do the image making, i don't remember the name of it. so as you see it is a long process
I'm trying to find out the Android requirements to properly format a USB drive from either a Windows or macOS computer (Linux if required) so (A) I can mount it on Shield TV 2017 (16GB) and (B) TWRP 3.2.3.0 Recovery Project can actually read the files on it.
What are the exact requirements to format the USB drive so Android doesn't have to modify or update anything?
FAT32/NTFS/XFAT/Other ? from what I've read FAT32 seems to be the most preferable.
MBR/GDP/Other ?
Primary/Logical ?
What tool is the best to format this so there's no issues?
I've tried Gparted, Windows Format, Acronis, Disk Utility, MiniTool Partition Wizard, and a few others.
Are their any requirements to copy data (i.e. boot.img, boot.zip, readme.txt, etc...) files from Windows/macOS/Linux onto the USB drive so it's readable?
These may sound like primitive or stupid questions, however I've spent several hours trying to boot my Shield TV (usb keyboard holding keys A and B) to then launch TWRP 3.2.3.0 Recovery to then mount the USB and read its files to Install them. So far I've tried just about everything I've learned from the internet and nothing seems to work. I've even formatted the USB drive using a Sony Android (7.0) TV however when I attempt to insert that onto either a PC or Mac both require the drive to be initialized. When my Shield TV was still working any USB drive I inserted required it be formatted or updated in some way so it could read it.
Currently if I format the USB drive can be detected by Shield TV and mounted by TWRP however none of the files I've copied onto it can be viewed by TWRP. I understand that TWRP filters files so if one needs to load an *.img file one needs to press the correct button to "view" and "access" those file types.
I'm starting to believe it's not the USB it's TWRP but I can't tell for certain.
Does one need to create Android-x86 (android-x86_64-8.1-rc2.iso) in VMware to accomplish this task? It's mind boggling that this is seems to be so difficult when it should be rather straight forward.
whiteak said:
You have tried mounting the USB I take it? I would try a different USB Stick if you have one for sure, it doesn't have to be any special format at all, just a simple fat32 format through Windows is all it needs. Without actually physically seeing what is going on, I can't really say what is going on, power is actually getting to the USB, eg, can you see any lights flashing etc?
Click to expand...
Click to collapse
Hello whiteak, Shield TV sees the USB drive, TWRP is able to mount it, navigate to it and list folders but no files are displayed either through Install (to see boot.img, readme.txt or boot.zip) even when toggling the IMG or ZIP button. I've also attempted to use TWRP's File Manager to review this data, no success. In an alternate test to prove that TWRP can see any *.img file I navigated to the Downloads folder (internal storage) and it can see recovery.img just fine. Using TWRP's File Manager I've attempted to change the file permissions (chmod 755, 777, etc...) to the usb-otg but that didn't change anything either.
At this point I'm unsure what to think? Is it the way the USB drive is formatted? Is it file/folder permissions on the USB drive? Is it TWRP limiting things that are actually there but refuses to read them for security or some other reasons? Hard to tell...
SOLVED
I solved the problem. I'll post the exact steps later but in short, create a Virtual Machine, install Android 8.1, insert the USB drive, format it and quit. Once this is done PROPERLY I later copied the necessary files using macOS TERMINAL from macOS to the USB drive. Now TWRP sees everything. What a pain in the @$$ to do such a simple task.
nadia p. said:
I solved the problem. I'll post the exact steps later but in short, create a Virtual Machine, install Android 8.1, insert the USB drive, format it and quit. Once this is done PROPERLY I later copied the necessary files using macOS TERMINAL from macOS to the USB drive. Now TWRP sees everything. What a pain in the @$$ to do such a simple task.
Click to expand...
Click to collapse
i havent used twrp on my shield tv before but i typically prefer to use twrp's adb terminal for that type of stuff..
it sounds like u had something formatted wrong or maybe even some type of encryption on the usb so it couldnt see the files... u def. shouldnt have to do all that lol
elliwigy said:
i havent used twrp on my shield tv before but i typically prefer to use twrp's adb terminal for that type of stuff..
it sounds like u had something formatted wrong or maybe even some type of encryption on the usb so it couldnt see the files... u def. shouldnt have to do all that lol
Click to expand...
Click to collapse
Hello elliwigy, I'm quite new at all this so I didn't know how to format a USB drive using ADB, I didn't even know this was possible. I'll have to look into this next time. My workaround installing Android in VMware worked out well.
I downloaded the torrent that was uploaded to this forum with the bin files, ran the DD commands, but when I do, the drive becomes inaccessible. Not sure what is going on. The SSD is a Samsung 500gb 870 EVO. I'm using Ubuntu for the process. Should I use a different version of Linux? I formatted the drive to GPT/FAT32. Also tried GPT/EXT4. I'll upload a picture in the replies of what the folder shows me after the process.
Also, my Shield drive died, so I can't just clone it, unless it's possible for someone to send an img/iso of theirs, then I can use HDD Raw Cloner or whatever it's called on Windows. But I don't know if someone else's img would work.
Just tried it on Mint. Same issue. SSD just disappears off the devices list as soon as the DD command goes through.
This is what I can see before the drive becomes inaccessible. Says 14 gigs are the size of the files, but then it says 32.8kb used. Makes no sense.
Capitalized the C in sdC. No error this time, terminal didn't say there was no more space. Drive didn't disappear or become inaccessible. But there's no files on the drive.
Oh and I tried removing the 1 from sdc1, seems to make no difference as long as C is capitalized.