Hi all, following on from kurohyou's excellent work on the KF2, I thought I would go about trying to develop a tutorial for unbricking a hardbricked Kindle Fire HD 7". This would be for the 2012 model, NOT the 2013.
A little bit of background on myself. I have always had a keen interest in electronics and studied microelectronics at college. I am pretty good at soldering etc even on small SMD devices, even more so now I have spent out on some decent kit (helping hands, rework station etc). Now I have decided to carry out this project as a summer hobby and hopefully I will get some support from you guys.
I have managed to piece together enough information that I think will enable me to complete this tutorial, with the exception of Linux, something that I am very new to and would need some assistance with.
I have seen common names among the forums when it comes to this type of subject, stunts513, soupmagnet, hashcode to name a few. I am hoping with the assistance of these members I can complete a comprehensive guide on unbricking a Kindle Fire HD 7", similar to http://forum.xda-developers.com/showthread.php?t=2415870
But please beware, IF YOU HAVE ANYTHING OTHER THAN A KINDLE FIRE HD 7" DO NOT USE THIS GUIDE!!
My main goal is to acquire a dead Kindle Fire HD 7" motherboard, as easily as possible. Unfortunately looking on eBay there seem to be very few from the UK and they are normally very expensive. I will keep looking but if anyone is willing to donate a non working or working motherboard for this cause I would be very grateful, just PM me if you can help. Just bear in mind due to the process it needs to go through, you will not get a working motherboard back, should you want it returned.
I aim to completely remove the eMMC from the motherboard and get exact pinout locations, as kurohyou did with his excellent KF2 guide. I will then use the same USB SD Card adaptor to see if the eMMC can even be read in the same way as the KF2. I have working knowledge of GParted in linux so I will also be using this to verify partition layouts and sizes. Once I have had any success in doing this I will update this post to reflect my progress.
There is my plan so far, if this has already been done, someone please tell me as I cannot find it anywhere.
overlode said:
Hi all, following on from kurohyou's excellent work on the KF2, I thought I would go about trying to develop a tutorial for unbricking a hardbricked Kindle Fire HD 7". This would be for the 2012 model, NOT the 2013.
A little bit of background on myself. I have always had a keen interest in electronics and studied microelectronics at college. I am pretty good at soldering etc even on small SMD devices, even more so now I have spent out on some decent kit (helping hands, rework station etc). Now I have decided to carry out this project as a summer hobby and hopefully I will get some support from you guys.
I have managed to piece together enough information that I think will enable me to complete this tutorial, with the exception of Linux, something that I am very new to and would need some assistance with.
I have seen common names among the forums when it comes to this type of subject, stunts513, soupmagnet, hashcode to name a few. I am hoping with the assistance of these members I can complete a comprehensive guide on unbricking a Kindle Fire HD 7", similar to http://forum.xda-developers.com/showthread.php?t=2415870
But please beware, IF YOU HAVE ANYTHING OTHER THAN A KINDLE FIRE HD 7" DO NOT USE THIS GUIDE!!
My main goal is to acquire a dead Kindle Fire HD 7" motherboard, as easily as possible. Unfortunately looking on eBay there seem to be very few from the UK and they are normally very expensive. I will keep looking but if anyone is willing to donate a non working or working motherboard for this cause I would be very grateful, just PM me if you can help. Just bear in mind due to the process it needs to go through, you will not get a working motherboard back, should you want it returned.
I aim to completely remove the eMMC from the motherboard and get exact pinout locations, as kurohyou did with his excellent KF2 guide. I will then use the same USB SD Card adaptor to see if the eMMC can even be read in the same way as the KF2. I have working knowledge of GParted in linux so I will also be using this to verify partition layouts and sizes. Once I have had any success in doing this I will update this post to reflect my progress.
There is my plan so far, if this has already been done, someone please tell me as I cannot find it anywhere.
Click to expand...
Click to collapse
Great job,will be useful to a lot of people if successful. And as for the support,we're all here to help ya
A lot of people spend time tinkering with Linux partitions,so getting support won't be as difficult as getting a dead motherboard,which is what worries me now. I would suggest you to buy a Fire HD,root it and leave the rest to your imagination (I would try to flash a Galaxy S3 Kernel using Odin or something )
Anyway,good luck!
I have managed to get myself a cheap Fire HD so just waiting for it to come in the post.As far as I can tell the Fire HD uses a very similar eMMC chip as the Fire 2 so I am hoping the partition structure is the same. If /dev/sdc2 is 256Kb and listed as bootloader then I think it should be straightforward to flash in the same way using the dd command.
Anyway, more updates to come
Update - I have now got a motherboard from a Kindle Fire HD 7", will go ahead and solder USB adaptor in the next few days and see what happens - more details to follow.
Ok, so I have opted to try and use a mini SD card adaptor for this project as it is very easy to kill a USB SD card adaptor if you get just one wiring point wrong, although this does have an increased risk of frying your USB port if you are VERY unlucky.
The SD card is wired like so -
https://www.dropbox.com/s/9zsrbevo97ifccj/SD%20Card%20wiring.JPG?dl=0
I drilled some very small holes close to the end of the mini SD internal connections to add stability to the wires. I used Valery_'s image to get the connection labels -
https://www.dropbox.com/s/fur0gxy72lox6yb/SD%20Card%20pinout.jpg?dl=0
For the VCC and VccQ wires, because there are two paired together it was not going to be possible to fit them into the SD card adaptor so I made a fly lead off of the main VCC wire -
https://www.dropbox.com/s/ocmw7p2dgsp4ia6/VCC%20fly%20lead.JPG?dl=0
Next I will be attempting to solder each wire onto the KFHD7 motherboard.
All done. I haven't cut the tracks that have been indicated in this picture as my PC recognises the eMMC under Windows 8 -
https://www.dropbox.com/s/1lyumxvw5h7agx4/Fire%20HD%20Pinout%20with%20VDDI.jpg?dl=0
So here is the motherboard soldered up -
https://www.dropbox.com/s/n30jpvbyhapoub7/Motherboard%20wiring%20KFHD7.JPG?dl=0
Update - after the eMMC was not recognised by Ubuntu I cut the 2 tracks in question, and still nothing. I am also now getting 0v from the card reader however the laptop still recognises SD cards inserted. I will acquire some more USB SD card adaptors and try again with those. More to follow.
Ok, a little frustrating but after checking and rechecking the solder points on the motherboard they are definitely correct, however Vcc, VccQ and Vss are still casting some doubt in my mind, considering that the VccQ and Vss points are both sides of capacitor 801 (C801). I am not 100% convinced that Vcc, VccQ and Vss have other points on the board. Reading the eMMC specifics here there are lots of Vcc, Vss and VccQ. I am not totally sure if there is a definite one that needs connecting
Any help on this would be much appreciated.
Ok, another post, sorry
Been doing some more research on the eMMC chip and I have found an official data sheet for the chip here
It seems that there are different pins for Vss and Vcc and I am wondering if this is causing the problem as I may be supplying power to the wrong part of the eMMC. Will see if R10 and T10 on the schematic lead to anywhere else and negate the need to cut the tracks, something which I still don't quite fully understand. Edit - R10 (Vss) does not seem to have a place on the board
As you can see from the following table it lists all the necessary locations for applying power to modify the eMMC -
https://www.dropbox.com/s/a7f299p492gf7qe/eMMC%20Pinout.jpg
VDDF is Vcc and VDD is VccQ .
I will check out these two pins later on and see where they lead on the board.
More to follow...
overlode said:
Ok, a little frustrating but after checking and rechecking the solder points on the motherboard they are definitely correct, however Vcc, VccQ and Vss are still casting some doubt in my mind, considering that the VccQ and Vss points are both sides of capacitor 801 (C801). I am not 100% convinced that Vcc, VccQ and Vss have other points on the board. Reading the eMMC specifics here there are lots of Vcc, Vss and VccQ. I am not totally sure if there is a definite one that needs connecting
Any help on this would be much appreciated.
Click to expand...
Click to collapse
http://forum.xda-developers.com/attachment.php?attachmentid=2784284&d=1402079403
http://forum.xda-developers.com/showthread.php?t=2775022
good luck
Valery_ said:
http://forum.xda-developers.com/attachment.php?attachmentid=2784284&d=1402079403
http://forum.xda-developers.com/showthread.php?t=2775022
good luck
Click to expand...
Click to collapse
Ok, I have put your image side by side with your top image and colour coded the points (Just bear in mind the right hand image is a mirror image of the BGA). No matter how I look at it, everything is correct and all Vcc, VccQ and Vss points are interconnected so I do not see how it is not working. Can you explain to me the need for cutting the tracks in your original image and what the version 1 and version 2 mean please?
How have you got on with this? The closest I have been is Windows 8 detecting something but Ubuntu doesn't see anything.
Cheers
overlode said:
Can you explain to me the need for cutting the tracks in your original image and what the version 1 and version 2 mean please?
Click to expand...
Click to collapse
Cutting the tracks had two goals: 1. to decrease power of supply from cardreader, 2. to protect the chips which are supplying 1.8 V
Additionally I used diode Schottky to decrease voltage to 1.6 V
There were impulses CMD and CLK, but there was a problem with signals Data0 - Data3. Level on these pinouts didn't change, was about 1 V
Supposedly the processor blocked Data0..3
I tried to connect cardreader with signal Reset on the motherboard, but there weren't Data0..3
So both in the case with 1.8 V and in the case with 3.3 V on the contact VccQ, there was a voltage about 1 V on Data0..3
I think there is a possibility of access to eMMC if OMAP is blocked and then it will make Data0..3 free (third output state Z)
Valery_ said:
Cutting the tracks had two goals: 1. to decrease power of supply from cardreader, 2. to protect the chips which are supplying 1.8 V
Additionally I used diode Shotky to decrease voltage to 1.6 V
There were impulses CMD and CLK, but there was a problem with signals Data0 - Data3. Level on these pinouts didn't change, was about 1 V
Supposedly the processor blocked Data0..3
I tried to connect cardreader with signal Reset on the motherboard, but there weren't Data0..3
So both in the case with 1.8 V and in the case with 3.3 V on the contact VccQ, there was a voltage about 1 V on Data0..3
I think there is a possibility of access to eMMC if OMAP is blocked and then it will make Data0..3 free (third output state Z)
Click to expand...
Click to collapse
I can't understand why they changed it so radically just for the KFHD 7" as the eMMC on the KF2 and the KFHD 8.9" are both easily accessible. It seems weird how they would use the OMAP to block it just on this model. Looking at the datasheet, are we missing something with VDDI, there is a suggestion to ground it via a 0.1 micro farad capacitor. Any thoughts on this?
VDDi Connections
The VDDi (K2) ball must only be connected to an external capacitor that is connected to VSS. This signal may not be left floating. The capacitor’s specifications and its placement instructions are detailed below.
The capacitor is part of an internal voltage regulator that provides power to the controller.
Caution: Failure to follow the guidelines below, or connecting the VDDi ball to any external signal or power supply, may cause the device to malfunction.
The trace requirements for the VDDi (K2) ball to the capacitor are as follows:
• Resistance: <2 ohm
• Inductance: <5 nH
The capacitor requirements are as follows:
• Capacitance: >=0.1 uF
• Voltage Rating: >=6.3 V
• Dielectric: X7R or X5R
Click to expand...
Click to collapse
Thanks to RolF2 from this post
SanDisk iNAND has three power domains assigned to VCCQ, VCC and VDDi, as shown in Table
10.
Table 10 - Power Domains
Pin Power Domain Comments
Supported voltage ranges:
High Voltage Region: 3.3V (nominal)
VCCQ Host Interface
Low Voltage Region: 1.8V (nominal)
VCC Memory Supported voltage range:
High Voltage Region: 3.3V (nominal)
VDDi Internal VDDi is the internal regulator connection to an
external decoupling capacitor.
Page 25+26 of this document explains it more. Looks like we may only need to ground VDDI with a 0.1uf capacitor. From what I can see on the motherboard all other connections already have capacitors grounding Vcc and VccQ.
Found the connection for VDDI -
https://www.dropbox.com/s/gzk11dywlmxzcmk/Fire%20HD%20Pinout%20with%20VDDI.jpg
overlode said:
Found the connection for VDDI -
https://www.dropbox.com/s/gzk11dywlmxzcmk/Fire%20HD%20Pinout%20with%20VDDI.jpg
Click to expand...
Click to collapse
I think that this will not resolve the problem. Connection of capacitor is strange. But this finding is a plus in the investigation.
Valery_ said:
I think that this will not resolve the problem. Connection of capacitor is strange. But this finding is a plus in the investigation.
Click to expand...
Click to collapse
The thing that confuses me is the fact that there are no other connections to the BGA array that come from a different source, all Vcc, VccQ and Vss connections are linked and already grounded with capacitors so you should be able to apply power to anywhere of these points. The fact that it is stated that this particular chip has 3 power domains, not 2 like the previous chips is encouraging.
As for your comment about the OMAP blocking access to the eMMC I don't think this is the case as the chip is used in a lot of nand flash technologies that do not have any OMAP device paired with them.
As soon as I get my next motherboard I am going to try the VDDI connection, it cannot do any harm as it controls internal voltage to the eMMC.
I will keep digging but I am pretty sure there is nothing more we have missed as I have been over the data sheet again and again.
Ok, I understand VDDI now, you don't need to touch this connection as it is used internally to regulate chip voltage. So back to the drawing board
Ok, I am going to make a simple voltage regulator to go inline with my USB card reader to make sure input voltage to the eMMC is 3.3v as I suspect over voltage may be causing a malfunction within the internal voltage stabiliser circuit of the eMMC. It seems over voltage triggers complete shutdown of the eMMC using internal diodes so this may explain the 1v or less output from the DAT pins.
Valery_, if I make sure input voltage is 3.3v then that would dismiss the need to cut the tracks yes?
Ok, I think this project has to be put on hold again. No matter what I try Ubuntu will not recognise the partitions of the eMMC even though the SD card adaptor flashes and then stops flashing as if being read properly. Connecting to VDDI fries your card reader instantly so do not try this!!
I just cannot see what we are missing and why this motherboard is so different from the KF2 yet not?
There has to be some way to gain access to the eMMC as the chip is so commonly used with other devices.
I will continue this project if I make any break through or if someone finds out something that we may be missing.
For the meantime I will continue with the KF2 unbricking as that is going rather well for me at the moment.
Reserved
overlode said:
Reserved
Click to expand...
Click to collapse
Maybe this information will be useful:
The MAX3002 accept VL voltages from +1.2V to +5.5V and VCC voltages from +1.65V to +5.5V, making them ideal for data transfer between low-voltage ASICs/PLDs and higher voltage systems.
Valery_ said:
Maybe this information will be useful:
The MAX3002 accept VL voltages from +1.2V to +5.5V and VCC voltages from +1.65V to +5.5V, making them ideal for data transfer between low-voltage ASICs/PLDs and higher voltage systems.
Click to expand...
Click to collapse
Isn't this just what we have been supplying though? My simple voltage regulator supplied 3.3v
picture not load
overlode said:
Ok, so I have opted to try and use a mini SD card adaptor for this project as it is very easy to kill a USB SD card adaptor if you get just one wiring point wrong, although this does have an increased risk of frying your USB port if you are VERY unlucky.
The SD card is wired like so -
Update - after the eMMC was not recognised by Ubuntu I cut the 2 tracks in question, and still nothing. I am also now getting 0v from the card reader however the laptop still recognises SD cards inserted. I will acquire some more USB SD card adaptors and try again with those. More to follow.
Click to expand...
Click to collapse
can you fix those picture? . it was prolem with dropbox
Thanks
kero2005 said:
can you fix those picture? . it was prolem with dropbox
Thanks
Click to expand...
Click to collapse
Pictures fixed, for what it's worth
Related
I've bought a used xv6600 off ebay which I'm going to convert to a carpc.
As a first time BA user, i have a few questions.
I have read the wiki/searched the forum, but I'm a bit mixed up and hence posting this thread.
installed versions on the phone:
model: PH20A2
ROM version: 1.36.00 WWE
ROM date 01/13/05
radio HA01_151
protocol AA.3.3.3.01
PRL 50619
extrom 1.36.116 WWE
hardware version 0041
a few notes:
- Its not going to be used as a phone as I can't register it with my local cellular provider (although they do support CMDA EVDO) - so I couldnt care less about if its radio works..
- Its going to be paired to a BT GPS from socket.
- the BA/xv6600 is going to be permanently mounted into the car (I'm still designing how, it would be in horizontal mode though).
- since It'll be permanently mounted, I won't (and couldnt) use the keyboard..
- audio out is going to be used to connect to an external speaker
- the BA will be charged from the car's 12v (always connected).
my questions are:
1) where could I find schematics for getting audio output (if exists), as well as where to connect the charge directly to the BA's connector.
I have only a cradle, no sync cable, which means I'd probably have to open up the BA and soldier directly, or get a connector...
2) should I connect audio out to the connector (if possible?) or the 2.5mm output on top of the device.. ?
3) I'd be interested in upgrading to WM5, I've read on the forums that it isn't possible on the CDMA versions because the radio doesnt work (or does it?). Since I don't care about the radio, could I install WM5 ? which ROM would be suitable for my BA model ?
awaiting your answers,
thanks!
Sounds like a neat project
ido said:
- the BA will be charged from the car's 12v (always connected).
Click to expand...
Click to collapse
Might be a bad idea...car batteries are designed to give out high power for short periods, not low constant drains. Personally I'd connect it to the ignition circuit so it's only powered when the ACC line is live. This will also turn it off for you after X minutes if you use the "auto-power off on batteries" function. It may even turn it on for you!
1) where could I find schematics for getting audio output (if exists), as well as where to connect the charge directly to the BA's connector.
I have only a cradle, no sync cable, which means I'd probably have to open up the BA and soldier directly, or get a connector...
2) should I connect audio out to the connector (if possible?) or the 2.5mm output on top of the device.. ?
Click to expand...
Click to collapse
The connector does have audio available. Buy a cable and hack it because if you mess it up you just buy another. Messing up the connector itself on the phone is more fatal. I think the schematic is on the wiki for the actual pin outs.
You might also find these useful:
http://wiki.xda-developers.com/index.php?pagename=Connectors
http://forum.xda-developers.com/archive/index.php/t-235616.html
yes after constant searching , i also found those threads.
Yet I'm wondering, some connectors don't include all 22 pins, but only the ones actually used for charging (for example) - and then it'll be really hard to hack them.
I guess i'll just have to hope I buy one that does have all 22 pins installed... unless you have other idea's for me.
Also, for the charger, you're right, I didn't mention that, but thats somewhat my intention.
Since the unit will be permanently mounted, I won't be able to sync it (unless I bring a laptop to my car) - could I somehow get a two SD cards installed at once to the unit ?
ido said:
yes after constant searching , i also found those threads.
Yet I'm wondering, some connectors don't include all 22 pins, but only the ones actually used for charging (for example) - and then it'll be really hard to hack them.
Click to expand...
Click to collapse
Yes, that's correct. If you get a charge & sync cable you'll have most. Might need to take audio from the 2.5mm jack in that case. That's probably the simplest solution if you cannot get a fully wired one. I'm interested in this sort of thing, so if you could post an update on what you go with I'd be grateful.
Since the unit will be permanently mounted, I won't be able to sync it (unless I bring a laptop to my car) - could I somehow get a two SD cards installed at once to the unit ?
Click to expand...
Click to collapse
I doubt you could get two SD cards. What may be possible is some sort of SD card extension device. Never seen one (never looked), but if it existed you could have a dash-mounted SD card.
Bluetooth or WiFi might help you e.g. with WiFi you could browse a network share to copy music over from your house. Also, there is a tool for WM5 that turns the phone into a keydrive, i.e. a USB mass storage device. Unless you need contacts etc sync'ed, that might be a bit simpler & give you more options to what you can hook up for.
PS bluetooth on WM5 isn't all that great. There is a "fix" that wakes the device now and then. This would light up your car overnight and might possibly be a thief magnet. On the other hand, if the battery dies on WM2003, you lose the data on it.
- At first I thought of making the device extractable, so I thought it'll be better to use the connector on the bottom for audio, but I've decided not to go this route (more complications and harder to make - also makes it easier for thieves.
So I'm probably going to go for the 2.5mm jack for audio.
- as for SD, since the SD slot won't be accessible, I thought of making an SD slot on the dashboard - and I'd like to switch between both.
an SD is connected via 9 pins, meaning making an SD switch is possible, but you wouldn't be able to use both.. thus I was wondering if software/hardware wise there is a builtin capabilty of such a thing as using two SD's at once. that'll be really cool.
- unfortunatly my XV6600 does not have WIFI, and BT is NOT an option for syncing (too slow !! - just imagine syncing 2gb of audio/vid via bluetooth..)
the two idea's I've had is making a USB connector on the dash (just incase I can get a laptop in the car..)
and the other, was the dash SD slot..
- for bluetooth, can't I just disable auto wakeup ?
- how will upgrading to WM5 save my data even if the battery drains ? its the same RAM chip's, not flash ROM, isn't that right ?
- as for HR's, the question is if I can somehow get the unit to 'working order' by installing software from the SD card, without actually syncing it to a computer..
fraser: Since I'm going to be connecting the ppc to the ignition circuit, and I'd also like to have a USB connector on the dashboard, I'd need to switch between the two.
i already have a car 12v connector -> usb charger device.
Should I buy a SYNC cable and convert it to charger, or car charger and convert it to USB cable ?
(although car charger might not have all the right pins..)
ido said:
thus I was wondering if software/hardware wise there is a builtin capabilty of such a thing as using two SD's at once. that'll be really cool.
Click to expand...
Click to collapse
Never heard of that I'm afraid. A switcher may work, but make sure there aren't any other physical switches that get tripped when you put a card in.
- for bluetooth, can't I just disable auto wakeup ?
Click to expand...
Click to collapse
No, this BT issue is the biggest one on WM5
- how will upgrading to WM5 save my data even if the battery drains ? its the same RAM chip's, not flash ROM, isn't that right ?
Click to expand...
Click to collapse
No, it's different ones. WM5 uses the "storage" area for your personal data; you now no longer have /storage as it's all in there. The RAM becomes proper RAM, although you can use some of it as a ramdisk with the same loss-of-power issues as WM2003.
- as for HR's, the question is if I can somehow get the unit to 'working order' by installing software from the SD card, without actually syncing it to a computer..
Click to expand...
Click to collapse
That's exactly what I do. I've stopped using the PC installers, there is enough junk on my PC. Just find the cabs for the apps and keep a copy on the SD card.
Not all apps have cabs.. so that might be a problem.
as well as I'll have to make pre-made .reg fixes just incase I'll have to HR.
as for WM5, if I install it, won't I have less free space then ?
ido said:
Not all apps have cabs.. so that might be a problem.
Click to expand...
Click to collapse
You can extract the cabs in various ways. Some exe's can even be opened in winrar.
as for WM5, if I install it, won't I have less free space then ?
Click to expand...
Click to collapse
You can reformat the storage area to 60 meg before the upgrade. Only before though. You don't get a memory slider like in WM2003.
Still, I'm not so sure on WM5 being the best for you. You'd want to have reliable BT and I'm not sure it is on WM5.
So I guess I'll stick with WM2003 for the time being.
I'm ordering an SD slot for the dashboard, as well as a USB connector.
Another Idea I've had is the need for the hardreset as well as reset button.
to which version should I upgrade my rom then ?
ido said:
- an SD is connected via 9 pins, meaning making an SD switch is possible, but you wouldn't be able to use both.. thus I was wondering if software/hardware wise there is a builtin capabilty of such a thing as using two SD's at once. that'll be really cool. ..
Click to expand...
Click to collapse
sorry to butt-in but, someone had done that before: SD-WiFi & SD Mem Card in parallel on the same 9 pin source: pda sd expansion.
a switch might be of help if you don't want to use the two slots simultaneously.
Yes I've seen that. Its a pretty lame hack if you read it to the end.
there's a better link with larger photo's for anyone interested:
http://homepage.ntlworld.com/david.hutchinson27/pockpc/
also, his project doesnt seem to work at the same time, and I've decided not to go with the switch route.
I'm reading a lot of the SD specs, So there is a very slim possibility I'll be able to get two cards to co-exist (and I would love some proffesional help if any of you guys know more about SD's then I do).
if not, then I'll just make an SD slot on the dashboard..
This guide adds to the disassemble guide found in the Shift section. I will show you how to successfully install a 100GB Toshiba hard drive.
1) Follow the disassemble guide until the back cover on the Shift is removed.
2) Carefully pull back the tape found on the ribbon cable connecting to the hard drive.
3) Pull gently the ribbon cable that connects to the hard drive interface. I used pliers with electrical tape around the pinchers to not scuff/scratch the ribbon cable. The hard drive connector is of LIF type (Low Insertion Force) meaning it's on there simply by pressure and not secured by any clips. It should slide out easily.
4) Remove the rubber casing around the hard drive and store somewhere. It can't be used with the 8mm 100GB hard drive due to the depth difference between the two. (trust me... i tried).
5) Using a thin rubber patch (like those for bike tires/air mattresses), place it in the area where the 100GB hard drive will sit, in this way the drive sits on top of the rubber patch.
6) Push the ribbon cable into the LIF connector on the Toshiba 100GB Hard Drive. It should slide in fairly easily. Note: there are no audible clicks, just push it in as far as you can and secure it with the tape the same way the 40GB was.
7) Close the back cover and secure it with the screws. It should close fairly snug in the area where the 100GB is; nonetheless, it should close. If it doesn't, check your drive positioning.
8) Follow the disassemble guide to replace the keyboard (do the reverse).
9) Boot the system and the BIOS will automatically detect the new 100GB drive!
10) Enjoy! (remember, this is just a guide... i am not responsible for damages or warranty void)
Hello,
Thanks for this guide...
This is the very same HDD I installed into my Shift. You wrote :
Remove the rubber casing around the hard drive and store somewhere. It can't be used with the 8mm 100GB hard drive due to the depth difference between the two. (trust me... i tried).
Click to expand...
Click to collapse
I had to sort out the Rubber thing too.
But on you picture, the rubber is still in place... So, just to make it crystal-clear to readers: confirming this is the rubber that should be removed (following maestro2mil's advice) or modified...
[adding] Btw, a thread is already live on this topic :
HERE
do you need to have copied accross the recovery image onto the 100gb drive (from the existing 40gb one) before you can do this?
salmon said:
do you need to have copied accross the recovery image onto the 100gb drive (from the existing 40gb one) before you can do this?
Click to expand...
Click to collapse
No, you can avoid that (as you will need a specific adapter in order to have the 100GB plugged via USB. One time adapter in this case). You should make a HDD image of your 40GB before taking it out the Shift, put it onto a external HDD or a USB dongle, then back to the 100GB once it is installed. Using Acronis or equivalent tool.
If you want to start from scratch, with the recovery partition, then go for search in the forum, there is several ways to do it : copying it while hidden, via Linux tools or have it visible, before using Acronis tool.
[editing] Of course, you may want to have the recovery partition copied to keep the recovery capability on-board. Not really necessary if you keep safe aside a clean image of the former 40GB HDD partition.
Hi Folks
Thanks alot for all this information! I am absolutely keen to do that to, so would you please specify wht drive exactly you've bougth and used and what I may additionally need for the upgrade? I already have an image of the Shift for install via USB ready and waiting ...
Thanks alot!
Lutz
Hello Lutzh,
Please, have a careful reading to this thread :
Upgrading the HDD
Regarding the Hard Drive model used here: just look at the pictures!
Hi Yann
Thanks for the feedback - I did what you've said and I got one on eBay for 90 €, so now I am waiting for delivery...
Cheers, Lutz
LIF or ZIF or... ?
Hi ,I am new to this forum , live in germany and sorry for my poor english ( only with dictionary )
Can anyone help, because of my bad english it is hard, to translate all threads and postst.
Here is my question:
I am a bit confused about new HDD for shift.
I read, we need LIF-connector
In an other thread ( http://forum.xda-developers.com/showthread.php?t=385578 ) they write , we need ZIF-connector.
What is the difference and what is correct?
I am thinking about buying a shift and about a new HDD.
Do I need a " GAH " or a " GAL " ? Or what should I order?
http://www.sdd.toshiba.com/main.aspx...ives/MK8025GAL
Thank You for Your help and sorry for my poor english.
Best regards!
T. Brumm
Hi T
I am expecting delivery this days - since I am German too, I'll report my experiences then, ok?
Lutz
Hello t.brumm,
I'm the one mentionning ZIF... I wonder why!
I added a post in the thread you're mentionning to correct my mistake...
HTC Shift is using a 40GB HDD with LIF connector so the model you plan to buy is quite ok.
"GAH" or "GAL" are not related to connector : HTC Shift is shipping with a MK400GAL and I changed it for a MK1011GAH, osome others for a MK1214GAH, etc...
Definitely, go for the MK8025GAL is it has the suitable heigh (5mm). Much more easy to make it fit into the case than those 8mm models.
Hello Yann,
thank You so much for Your help.
It is really not easy, to read all posts with dictionary. So Your answer becomes special importance for me.
But, The MK8025GAL has here 8mm, not 5mm!? What is correct?
http://www.storage.toshiba.eu/index.php?id=3&pid=229&sid=3
May I ask still an other question?
I have a desktop pc , which has a hidden recovery-partition too.
I did try to visible this partition (like it is written here ) but this does not work. ( maybe, because I have Windows XP and not Vista ? )
Then I used " Powerquest Drive Image 7 ".
This program sees the hidden partition and I can backup this hidden partition to another HDD too!
If I restore it somewhere on my HDD, this partition is not hidden anymore, it is visible and with " Partition Magic 7 " I can not hide this partition.
If I would do this on the shift ( I would like to change the HDD at first step and this procedure would be very easy)
could I than recover the system from the visible partition or should this partition generally invisible?
Thank You and best greetings!
T. Brumm
Thank
But, The MK8025GAL has here 8mm, not 5mm!? What is correct?
http://www.storage.toshiba.eu/index....&pid=229&sid=3
Click to expand...
Click to collapse
Strange... I've to admit you pinpointed something: Toshiba is inconsistent here... To be safe, I would bet it's a 8mm. Still feasible, but more tricky.
Don't get me wrong: a 8mm heigh HDD fits but... and I guess you already read my comments on the other threads... the result is not really safe on the mechanical side. Still, with a little extra caution when moving around your Shift, everything is fine.
About Recovery partition, see this thread : Recovery from USB drive
Riki0081 is not hiding the Recovery Partition in order to boot on it from an USB dongle. Using a 4GB USB dongle is a very good solution...
Because as Riki0081 wrote HERE, Recovery boot (Fn+F3) won't work anymore if Recovery partition remains visible on the internal HDD.
By the way, I did it the lazy way: avoiding to deal with the Hidden Partition when possible.
Few weeks before getting the my 100GB HDD on-board, I let the Shift doing a Fresh install of Vista from the Recovery Partition. I rebooted on a CD with the Partition tool (Acronis), to copy the installed Vista onto an USB External HDD. At that time, I killed the Recovery Partition in order to save some space on the 40GB...
When my 100GB HDD arrived, I replaced the 40GB HDD with it, copying the initial Partition image (the "Fresh Vista installation") from the external storage back to the new 100GB HDD. Re-installing/organizing Applications and Data onto 2 "large" Logical partitions...
Hope my bad English is readable enough!
Hello Yann and thank You!
I think, I did understand Your post and I know, what to do!
And Your english is better than mine
Best regards!
T.Brumm
SDD or HD
Somebody who did the step to SDD drive already?
Is it wise while the shift bis open to build in a SDD?
If so please share model and connections
Thanks and regards
sorry kinda random information
but having an acer aspire one means i have had to upgrade my **** 8gb ssd to a hdd
and we have a zif connecting ssd
and this question came up many times in the forum
what is the difference between zif and lf
well z is for zero and l is for low
oif is for insertion force
basically toshiba realised it wasnt zero inserton force at all, and their drives are LIF.
hitachi drives are ZIF (as far as I know) yet both require the same amount of force o push the cable in (basically none)
but hitachi drives require a flip cable as their pinouts are reversed or something like that, so for the shift i would guess you can only have toshiba
plus if anyone doesnt want their ld drives, im sure people at www.aspireoneuser.com/forum/index.php would love them for a price, to save getting them of ebay
email me at [email protected] if youre interested
Rory
Hey guys,
Im looking to unbrick my G1 (no bootloader). I have asked some questions previously but haven't had the time to do anything besides that up to now.
I haven't had any luck here in India locating what I need with confidence, but today I happened across a helpful website.
Could anyone tell me if this is what Im looking for?
wiggler-clone
robokits.co.in/shop/index.php?main_page=product_info&cPath=12&products_id=240
pc-serial
robokits.co.in/shop/index.php?main_page=product_info&cPath=6_64&products_id=64
The wiggler look-a-like says its compatible with GCC OCD.
The pc-serial page offers a driver under the name of pl230.
I am hoping to be able to follow the unbrick page here: wiki.cyanogenmod.com/index.php?title=JTAG_for_Dream/Magic
Thanks
The unbrick process originated on this forum and was really moved along by member ezterry. You really ought to read the threads here in the dev section about this. They do tend to be long, but there is every bit of information you could possibly want to know about unbricking a dream.
http://forum.xda-developers.com/showpost.php?p=5911627&postcount=302
http://forum.xda-developers.com/showpost.php?p=5934885&postcount=6
thanks for the links. i am currently working through the multitude of posts.
Hey,
I am learning a lot and have what i think is my last issue before i order some parts. The pc-serial cable should be at 2.8 v but i only have access to converters that give 5 v output.
I first consulted the datasheet for the pl2303hx (link provided above) which states:
"RS-232 VDD. The RS-232 output signals (Pin 1 ~ Pin 3) are
designed for 5V, 3.3V or 3V operation. VDD_232 should be
connected to the same power level of the RS-232 interface.
(The RS-232 input signals are always 5V~3V tolerant.)"
which was a little confusing, so i consulted the vendor:
"It will output 5V if the jumper is shorted or else it will be 0V. But the unit is self powered and can accept 3.3V input and output levels.
which is self contradictory. but, from what i gather, the serial output will be the same as the usb input.
Lastly, from this google group discussion:
groups.google.com/group/android-platform/msg/bf66abf4515132fb
Someone states that they used an lm317 circuit to drop voltage to 2.8, and it seems like this is the route ill take.
Question is, which voltage do i control? I think if i drop usb vcc voltage i should be good?
I think i just going to buy it and see, whats 400 INR anyways (its like 8 bucks)
salsavirdi said:
"RS-232 VDD. The RS-232 output signals (Pin 1 ~ Pin 3) are
designed for 5V, 3.3V or 3V operation. VDD_232 should be
connected to the same power level of the RS-232 interface.
(The RS-232 input signals are always 5V~3V tolerant.)"
Click to expand...
Click to collapse
If you can't understand that, then you should find someone to assist you who does.
I suppose im being a overly paranoid, and would like some corroboration. Id really hate to fry my phone, im rather attached to it.
Hi!
As a new member, I cannot post to developer section, so I try to ask this question here. Nook Color PCB contains solder pads for Sierra SL808x AirPrime 3G module (probably non-GPS versions - GPS antenna pin is not used), connected to OMAP ULPI port probably via TUSB1211 ULPI transceiver (absent 36 pin TFBGA chip near flash disk chip - PCB pinout seems to be identical to TUSB1211 pinout). I will try to order several transceivers, solder one and several required SMD decoupling caps (I have experience in BGA rework and soldering, so I hope this task will be not so tricky) and try to get this internal USB working. The question is simple - have someone trying this hardware hack already? Is the last CM7 kernel able to support additional integrated OMAP 3621 ULPI port or such hack needs research and kernel/ULPI module patching?
Thank you in advance, Gleb.
P.S.: sorry for my bad english - I'm more a reader, than a writer.
I am trying to recover files from the built-in (32GB) eMMC of a water damaged Huawai P9 (motherboard is corroded and no longer boots..). I'd like to somehow create a logical dump of the contained file system preferably using the least intusive method suitable for the task.
(unfortunately I am not allowed to link to the photo here.. so you'll have to manually patch the respective URL: www-wothke-ch*p9*motherboard.jpg )
Looking at the schematics ("14. eMMc AND LpDDR3") I see that various eMMC related test points are exposed on the PCB (i.e. DAT0, CLK, VSP1, VSP2, VSP3, VSP4) and I might be able to directly patch into those, to directly connect to some SD adapter (like this one: %&&ç - unfortunately I am not allowed to post the link - but you can google for "dumping-the-emmc-nand-on-the-nintendo-switch").. eventhough those pads are terribly small and I guess I'd still have to find CMD, 1v8 & 3v0 somewhere else on the PCB. however I have no experience if the remaining stuff on the PCB might just interfere too much for a respective patch to actually work.. any thoughts? Would I rather need to desolder the eMMC chip and to directly connect to the SD adapter?
Is Huawai actually using the on-chip (eMMC) controller or are they using some separate controller, so that using the on-chip one would not actually recover the logical image (if the on-chip controller was even functional and not some cheaper defective version that Huawai might be sourcing to save money - like those 1$ eMMC/SD adapters that can be found on aliexpress)?
The phone supposedly was *not* password protected. Does this automatically mean that the data on the eMMC is not encrypted or does Huawai use some kind of additional built-in/proprietary encryption scheme?
I found the JTAG pads on the PCB but if I understand it correctly those would at best allow me to recover a physical dump. So I'd need addtional hardware to even connect to those and then some expensive analyzer software to transfrom the physical dump to the logical image that I actually need... right?
There are also some ISP related test points exposed on the PCB.. but I guess using those (if they even still work on the damaged board )would lead to situation similar to the JTAG one, right?
Anything I have missed? Any recommendations?