Hi,
I wonder since there's so much effort on rooting several devices, is there any thread about hardware-rooting the cheap Amazon Fire 7" Tablet?
I have all my old tablets rooted and replaced before Amazon's exploitable bugs were closed.
However I would be interested in a few more tablets from time to time.
Recently I had to recover one defect tablet, and desoldered the eMMc.
I have jumpwired the chip with a micro-sd card adapter (4bit transfer) and retrieved clean partitions.
Interesting sidenote:
There must be a big bug in the Linux sdcard driver support, when I have jumpwired only 1bit transfer the sdcard shown on the linux system contained the content of my harddisk instead of the eMMc.
[edit - after writing all that already] reconnecting the jumpwired 4bit microsd card resulted in further linux kernel driver issues
Only a clean linux boot and attaching the microsd/emmc card once works without any problem (I have pulled all my old apps and data without any problem)
According to the datasheet of the 8gb flash the flash can handle 3.3v (which makes it ideally for a micro-sd adapter
(eg. https://www.amazon.de/SanDisk-Micro-SD-Adapter-auf-SD/dp/B001PFAF9U I have just cut half of the top and soldered the pins)
eMMC Datasheet:
https://www.verical.com/datasheet/samsung-module-klmag2gend-b031-1212321.pdf
Flash used in the Kindle Fire 7" Tablet KLM8G1GEND (pinout is the same as for the KLMAG2GEND)
Did anyone already try to jumpwire a microsd card directly with the testpoints?
- CMD
- DATA0
- CLOCK
- 1v8
- 3v3
pins are exposed on the small firetv 7" tablet.
Code:
181.211397] mmc0: new high speed MMC card at address 0001
[ 181.348615] mmcblk0: mmc0:0001 8GND3R 7.28 GiB
[ 181.348731] mmcblk0boot0: mmc0:0001 8GND3R partition 1 4.00 MiB
[ 181.348915] mmcblk0boot1: mmc0:0001 8GND3R partition 2 4.00 MiB
[ 181.365707] mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12 p13
[ 182.507434] EXT4-fs (mmcblk0p11): recovery complete
[ 182.545003] EXT4-fs (mmcblk0p11): mounted filesystem with ordered data mode. Opts: (null)
[ 182.760939] EXT4-fs (mmcblk0p13): recovery complete
[ 182.760945] EXT4-fs (mmcblk0p13): mounted filesystem with ordered data mode. Opts: (null)
[ 183.576743] EXT4-fs (mmcblk0p12): recovery complete
[ 183.576754] EXT4-fs (mmcblk0p12): mounted filesystem with ordered data mode.
# ls /media/xtec/57f8f4bc-abf4-655f-bf67-946fc0f9f25b1/
acdapi @btmtk logd resource-cache
adb bugreports lost+found securedStorageLocation
agps_supl crashreport media securestop
anr dalvik-cache mediadrm SecureTD
app data metrics security
app-asec debug_service misc system
app-lib dontpanic nfc_socket tombstones
app-private drm nvram user
autotrace gps_mnl playready vitals
backup key_provisioning property vp
bootchart local radio
# ls /media/xtec/57f8f4bc-abf4-655f-bf67-946fc0f9f25b2/
backup dalvik-cache lost+found recovery
# ls /media/xtec/57f8f4bc-abf4-655f-bf67-946fc0f9f25b
app etc lib priv-app tts xbin
bin fonts lost+found recovery-from-boot.p usr
build.prop framework media security vendor
I don't have equipment for reballing here so I'm a bit limited with my ability to do further testing.
My internet is terrible at the moment... I'm having some issues with uploading the pictures
just another try here.
[ok you can delete this reply, I saw that the first post is ok everything's so slow here due to my unreliable DSL ...]
tf101crasher said:
Hi,
I wonder since there's so much effort on rooting several devices, is there any thread about hardware-rooting the cheap Amazon Fire 7" Tablet?
I have all my old tablets rooted and replaced before Amazon's exploitable bugs were closed.
However I would be interested in a few more tablets from time to time.
Recently I had to recover one defect tablet, and desoldered the eMMc.
I have jumpwired the chip with a micro-sd card adapter (4bit transfer) and retrieved clean partitions.
Interesting sidenote:
There must be a big bug in the Linux sdcard driver support, when I have jumpwired only 1bit transfer the sdcard shown on the linux system contained the content of my harddisk instead of the eMMc.
[edit - after writing all that already] reconnecting the jumpwired 4bit microsd card resulted in further linux kernel driver issues
Only a clean linux boot and attaching the microsd/emmc card once works without any problem (I have pulled all my old apps and data without any problem)
According to the datasheet of the 8gb flash the flash can handle 3.3v (which makes it ideally for a micro-sd adapter
(eg. https://www.amazon.de/SanDisk-Micro-SD-Adapter-auf-SD/dp/B001PFAF9U I have just cut half of the top and soldered the pins)
eMMC Datasheet:
https://www.verical.com/datasheet/samsung-module-klmag2gend-b031-1212321.pdf
Flash used in the Kindle Fire 7" Tablet KLM8G1GEND (pinout is the same as for the KLMAG2GEND)
Did anyone already try to jumpwire a microsd card directly with the testpoints?
- CMD
- DATA0
- CLOCK
- 1v8
- 3v3
pins are exposed on the small firetv 7" tablet.
Code:
181.211397] mmc0: new high speed MMC card at address 0001
[ 181.348615] mmcblk0: mmc0:0001 8GND3R 7.28 GiB
[ 181.348731] mmcblk0boot0: mmc0:0001 8GND3R partition 1 4.00 MiB
[ 181.348915] mmcblk0boot1: mmc0:0001 8GND3R partition 2 4.00 MiB
[ 181.365707] mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12 p13
[ 182.507434] EXT4-fs (mmcblk0p11): recovery complete
[ 182.545003] EXT4-fs (mmcblk0p11): mounted filesystem with ordered data mode. Opts: (null)
[ 182.760939] EXT4-fs (mmcblk0p13): recovery complete
[ 182.760945] EXT4-fs (mmcblk0p13): mounted filesystem with ordered data mode. Opts: (null)
[ 183.576743] EXT4-fs (mmcblk0p12): recovery complete
[ 183.576754] EXT4-fs (mmcblk0p12): mounted filesystem with ordered data mode.
# ls /media/xtec/57f8f4bc-abf4-655f-bf67-946fc0f9f25b1/
acdapi @btmtk logd resource-cache
adb bugreports lost+found securedStorageLocation
agps_supl crashreport media securestop
anr dalvik-cache mediadrm SecureTD
app data metrics security
app-asec debug_service misc system
app-lib dontpanic nfc_socket tombstones
app-private drm nvram user
autotrace gps_mnl playready vitals
backup key_provisioning property vp
bootchart local radio
# ls /media/xtec/57f8f4bc-abf4-655f-bf67-946fc0f9f25b2/
backup dalvik-cache lost+found recovery
# ls /media/xtec/57f8f4bc-abf4-655f-bf67-946fc0f9f25b
app etc lib priv-app tts xbin
bin fonts lost+found recovery-from-boot.p usr
build.prop framework media security vendor
I don't have equipment for reballing here so I'm a bit limited with my ability to do further testing.
Click to expand...
Click to collapse
In this I can not help you because I'm not good at hardware mods . Maybe @<br /> can help you.
tf101crasher said:
Hi,
I wonder since there's so much effort on rooting several devices, is there any thread about hardware-rooting the cheap Amazon Fire 7" Tablet?
I have all my old tablets rooted and replaced before Amazon's exploitable bugs were closed.
However I would be interested in a few more tablets from time to time.
Recently I had to recover one defect tablet, and desoldered the eMMc.
I have jumpwired the chip with a micro-sd card adapter (4bit transfer) and retrieved clean partitions.
Interesting sidenote:
There must be a big bug in the Linux sdcard driver support, when I have jumpwired only 1bit transfer the sdcard shown on the linux system contained the content of my harddisk instead of the eMMc.
[edit - after writing all that already] reconnecting the jumpwired 4bit microsd card resulted in further linux kernel driver issues
Only a clean linux boot and attaching the microsd/emmc card once works without any problem (I have pulled all my old apps and data without any problem)
According to the datasheet of the 8gb flash the flash can handle 3.3v (which makes it ideally for a micro-sd adapter
(eg. https://www.amazon.de/SanDisk-Micro-SD-Adapter-auf-SD/dp/B001PFAF9U I have just cut half of the top and soldered the pins)
eMMC Datasheet:
https://www.verical.com/datasheet/samsung-module-klmag2gend-b031-1212321.pdf
Flash used in the Kindle Fire 7" Tablet KLM8G1GEND (pinout is the same as for the KLMAG2GEND)
Did anyone already try to jumpwire a microsd card directly with the testpoints?
- CMD
- DATA0
- CLOCK
- 1v8
- 3v3
pins are exposed on the small firetv 7" tablet.
I don't have equipment for reballing here so I'm a bit limited with my ability to do further testing.
Click to expand...
Click to collapse
I'm not an expert in this or anything but I don't think you have to desolder the emmc. @<br /> made a hardmod to root the he 8 here. he soldered to test pads. Maybe we can do something similar to the hd 7. The test pads may or may not be in the same spots as the hd 8.
tf101crasher said:
Hi,
I wonder since there's so much effort on rooting several devices, is there any thread about hardware-rooting the cheap Amazon Fire 7" Tablet?
I have all my old tablets rooted and replaced before Amazon's exploitable bugs were closed.
However I would be interested in a few more tablets from time to time.
Recently I had to recover one defect tablet, and desoldered the eMMc.
I have jumpwired the chip with a micro-sd card adapter (4bit transfer) and retrieved clean partitions.
Interesting sidenote:
There must be a big bug in the Linux sdcard driver support, when I have jumpwired only 1bit transfer the sdcard shown on the linux system contained the content of my harddisk instead of the eMMc.
[edit - after writing all that already] reconnecting the jumpwired 4bit microsd card resulted in further linux kernel driver issues
Only a clean linux boot and attaching the microsd/emmc card once works without any problem (I have pulled all my old apps and data without any problem)
According to the datasheet of the 8gb flash the flash can handle 3.3v (which makes it ideally for a micro-sd adapter
(eg. https://www.amazon.de/SanDisk-Micro-SD-Adapter-auf-SD/dp/B001PFAF9U I have just cut half of the top and soldered the pins)
eMMC Datasheet:
https://www.verical.com/datasheet/samsung-module-klmag2gend-b031-1212321.pdf
Flash used in the Kindle Fire 7" Tablet KLM8G1GEND (pinout is the same as for the KLMAG2GEND)
Did anyone already try to jumpwire a microsd card directly with the testpoints?
- CMD
- DATA0
- CLOCK
- 1v8
- 3v3
pins are exposed on the small firetv 7" tablet.
Code:
181.211397] mmc0: new high speed MMC card at address 0001
[ 181.348615] mmcblk0: mmc0:0001 8GND3R 7.28 GiB
[ 181.348731] mmcblk0boot0: mmc0:0001 8GND3R partition 1 4.00 MiB
[ 181.348915] mmcblk0boot1: mmc0:0001 8GND3R partition 2 4.00 MiB
[ 181.365707] mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12 p13
[ 182.507434] EXT4-fs (mmcblk0p11): recovery complete
[ 182.545003] EXT4-fs (mmcblk0p11): mounted filesystem with ordered data mode. Opts: (null)
[ 182.760939] EXT4-fs (mmcblk0p13): recovery complete
[ 182.760945] EXT4-fs (mmcblk0p13): mounted filesystem with ordered data mode. Opts: (null)
[ 183.576743] EXT4-fs (mmcblk0p12): recovery complete
[ 183.576754] EXT4-fs (mmcblk0p12): mounted filesystem with ordered data mode.
# ls /media/xtec/57f8f4bc-abf4-655f-bf67-946fc0f9f25b1/
acdapi @btmtk logd resource-cache
adb bugreports lost+found securedStorageLocation
agps_supl crashreport media securestop
anr dalvik-cache mediadrm SecureTD
app data metrics security
app-asec debug_service misc system
app-lib dontpanic nfc_socket tombstones
app-private drm nvram user
autotrace gps_mnl playready vitals
backup key_provisioning property vp
bootchart local radio
# ls /media/xtec/57f8f4bc-abf4-655f-bf67-946fc0f9f25b2/
backup dalvik-cache lost+found recovery
# ls /media/xtec/57f8f4bc-abf4-655f-bf67-946fc0f9f25b
app etc lib priv-app tts xbin
bin fonts lost+found recovery-from-boot.p usr
build.prop framework media security vendor
I don't have equipment for reballing here so I'm a bit limited with my ability to do further testing.
Click to expand...
Click to collapse
You can compare your outcome with my attempts back in September, I had some success initially.
In subsequent testing I destroyed/ruined the DAT0 pad on the PCB and should abandon my investigation.
Also that was the only Fire 7" 5th Generation I had to do my investigation, so I lost my unique testing tablet.
Here are the links to the information I could gather and a picture with the pads:
* https://forum.xda-developers.com/showpost.php?p=77501192&postcount=365
* https://forum.xda-developers.com/showpost.php?p=77886908&postcount=381
After that I bought also a Fire 7" 7th Gen. and a friend gifted me with a broken Fire 7" tablet, also a 7th Gen.
So I started to trace-out the pads for doing the same tests, as you have come to know a slow and tedious process.
I am almost finished, I found almost all the needed signals CMD, DAT0, 3.3V and 1.8V I am only missing the CLOCK line.
The EMMC is a 16GB Samsung KMFE10012M-B214 which is a 221 BGA package.
One trick someone suggested, if the reading seems to fail, is to have 100 ohm pull-up resistors to 1.8V for both CMD and DAT0 lines.
I am obviously interested in your testing, so please report your success and your setup as detailed as you can, possibly with photos.
One interesting improvement is that you are taking the 1.8Vccq from a resistor which is much more solid then the pad I was using.
In fact I would suggest to avoid pads at any cost if there are alternative soldering points, these pads are easily ripped of the PCB by
sudden pulls of the connected cable or too many attempt with the soldering iron, due to the heat and too small nearby traces.
Well ... happy hacking I wish you success !
.:HWMOD:.
hwmod said:
You can compare your outcome with my attempts back in September, I had some success initially.
In subsequent testing I destroyed/ruined the DAT0 pad on the PCB and should abandon my investigation.
Also that was the only Fire 7" 5th Generation I had to do my investigation, so I lost my unique testing tablet.
Here are the links to the information I could gather and a picture with the pads:
* https://forum.xda-developers.com/showpost.php?p=77501192&postcount=365
* https://forum.xda-developers.com/showpost.php?p=77886908&postcount=381
After that I bought also a Fire 7" 7th Gen. and a friend gifted me with a broken Fire 7" tablet, also a 7th Gen.
So I started to trace-out the pads for doing the same tests, as you have come to know a slow and tedious process.
I am almost finished, I found almost all the needed signals CMD, DAT0, 3.3V and 1.8V I am only missing the CLOCK line.
The EMMC is a 16GB Samsung KMFE10012M-B214 which is a 221 BGA package.
One trick someone suggested, if the reading seems to fail, is to have 100 ohm pull-up resistors to 1.8V for both CMD and DAT0 lines.
I am obviously interested in your testing, so please report your success and your setup as detailed as you can, possibly with photos.
One interesting improvement is that you are taking the 1.8Vccq from a resistor which is much more solid then the pad I was using.
In fact I would suggest to avoid pads at any cost if there are alternative soldering points, these pads are easily ripped of the PCB by
sudden pulls of the connected cable or too many attempt with the soldering iron, due to the heat and too small nearby traces.
Well ... happy hacking I wish you success !
.:HWMOD:.
Click to expand...
Click to collapse
That's very strange. Can you post a picture of your fire 7th gen? I have a fire 7 7th gen too, and the emmc chip is skhynix, not samsung. Also it is a hybrid chip combining both dram and emmc in one. There's only one testpoint, here's my picture: https://i.imgur.com/fBx88CN.jpg Mine's 8gb model though, so maybe they use completely different PCB layouts?
xyz` said:
That's very strange. Can you post a picture of your fire 7th gen? I have a fire 7 7th gen too, and the emmc chip is skhynix, not samsung. Also it is a hybrid chip combining both dram and emmc in one. There's only one testpoint, here's my picture: https://i.imgur.com/fBx88CN.jpg Mine's 8gb model though, so maybe they use completely different PCB layouts?
Click to expand...
Click to collapse
Here are the pictures you requested (external to XDA):
The front & back of the FIre 7" 7th Generation PCB.
I am sure the 16GB LpDDR EMMC in my PCB is a Samsung KMFE10012M-B241 (moviNAND series).
Attached to this message you can find relevant EMMC pictures which leaves no doubts about that.
Your pictures are taken from a different angle but to me it looks like they are the same PCB.
As you said, it may be that the 8GB and 16GB EMMC versions have different vendor/manufacturer.
Nothing strange about that.
.:HWMOD:.
hwmod said:
Here are the pictures you requested (external to XDA):
The front & back of the FIre 7" 7th Generation PCB.
I am sure the 16GB LpDDR EMMC in my PCB is a Samsung KMFE10012M-B241 (moviNAND series).
Attached to this message you can find relevant EMMC pictures which leaves no doubts about that.
Your pictures are taken from a different angle but to me it looks like they are the same PCB.
As you said, it may be that the 8GB and 16GB EMMC versions have different vendor/manufacturer.
Nothing strange about that.
.:HWMOD:.
Click to expand...
Click to collapse
Oh yeah my bad I didn't realize it was also a hybrid chip in the 16gb case.
Can you take the shielding off and take another photo?
Putting some needle adapter on the traces shouldn't be a problem.
I won't be here for 4 month now ... too bad that I started to look at that so late.
If you short the test point under the shield (which is the eMMC CMD line) to ground, you can put the bootrom into download mode and exploit it the same way I did in https://forum.xda-developers.com/hd...fire-hd-8-2018-downgrade-unlock-root-t3894256. No need to solder the adapter.
tf101crasher said:
Can you take the shielding off and take another photo?
Putting some needle adapter on the traces shouldn't be a problem.
I won't be here for 4 month now ... too bad that I started to look at that so late.
Click to expand...
Click to collapse
On these PCB the shielding is not removable easily it is soldered to the PCB and must be cut off with a sharp and robust enough hand cutter with small/thin blades.
Since the board was not functional, I did the job with an electric multifunction rotary cutter/grinder tool, consider the danger of cutting components or traces.
Hot air gun would not fit the job since the heat needed is likely to melt all the components around the PCB.
However attached here is a photo of a PCB with part of the shielding removed (not the same PCB in previous photos).
.:HWMOD:.
hwmod said:
On these PCB the shielding is not removable easily it is soldered to the PCB and must be cut off with a sharp and robust enough hand cutter with small/thin blades.
Since the board was not functional, I did the job with an electric multifunction rotary cutter/grinder tool, consider the danger of cutting components or traces.
Hot air gun would not fit the job since the heat needed is likely to melt all the components around the PCB.
However attached here is a photo of a PCB with part of the shielding removed (not the same PCB in previous photos).
.:HWMOD:.
Click to expand...
Click to collapse
I took the risk and removed the shield but not without board damage. luckily it still works
https://imgur.com/a/YRxzM6y
I used a pocket knife and needle nose pliers to remove my shield
hwmod said:
On these PCB the shielding is not removable easily it is soldered to the PCB and must be cut off with a sharp and robust enough hand cutter with small/thin blades.
Since the board was not functional, I did the job with an electric multifunction rotary cutter/grinder tool, consider the danger of cutting components or traces.
Hot air gun would not fit the job since the heat needed is likely to melt all the components around the PCB.
However attached here is a photo of a PCB with part of the shielding removed (not the same PCB in previous photos).
.:HWMOD:.
Click to expand...
Click to collapse
it's this pin
https://imgur.com/a/0vLj8FS
https://forum.xda-developers.com/am...-softbrick-t3894671/post78798153#post78798153
ANDROID2468 said:
it's this pin
https://imgur.com/a/0vLj8FS
https://forum.xda-developers.com/am...-softbrick-t3894671/post78798153#post78798153
Click to expand...
Click to collapse
But where have you connected? What is the other pin?
EDIT: I confirm that it can be done without removing the shield. You need to have a little precision to put the metal through a hole (see attatchments). The problem is that I do not know where the other point is.
Rortiz2 said:
But where have you connected? What is the other pin?
EDIT: I confirm that it can be done without removing the shield. You need to have a little precision to put the metal through a hole (see attatchments). The problem is that I do not know where the other point is.
Click to expand...
Click to collapse
The other end is the ground plane, so for example the metal shield above it would work.
ANDROID2468 said:
it's this pin
https://imgur.com/a/0vLj8FS
https://forum.xda-developers.com/am...-softbrick-t3894671/post78798153#post78798153
Click to expand...
Click to collapse
Yes that is the pin that should be temporarily connected to GND (the shield for example).
However FYI that pin is the CMD signal not the CLK signal, it doesn't make any difference in our case.
I wanted to underline the fact because I believe I have seen reference to it as the CLK (clock signal).
.:HWMOD:.
Hard Bricked
I figured I would try the method of using a metal object under the shield to see if it would work. This is an extra tablet for me, so I wanted to see what would happen. I had issues with the TTY serial port on my Ubuntu setup. The tablet kept turning on after being plugged in to USB. At some point it ceased to turn on at all. I shorted something.
I will say that the cover of this tablet is exceedingly easy to remove and reinstall without any damage to the tablet whatsoever. It is clipped on without glue.
If I had another tablet to mess with, I would use a dremel and trim away a small part of the shield over the solder point in question.
Thank you all for your fascinating and hard work. I have enjoyed following these threads.
My friend you can use this adapters for read all emmc (Aliexpress-1$)
USB 2.0 eMMC Adapter 153 169 (eMCP 162 186) eMCP PCB Main Board without Flash Memory eMMC Adapters Integrated Circuits
for easy removal of the screen at the place of soldering, fill in the Rose or Wood alloy
You can also to root a new Fire 7 2019 via eMMC Hardware
Related
HITACHI 8GB MICRODRIVE 35(36 ?) PIN - ZIF connector / PATA interface, 40 x 30 x 5 mm.
Compact Flash have 50 pin interface, 43×36×3.3 mm.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(Citation from WIKIPEDIA) - Main article: Microdrive
Microdrives are tiny hard disks—about 25 mm (1 inch) wide—packaged with a CompactFlash Type II form factor and interface. They were developed and released in 1999 by IBM in a 170 megabyte capacity. IBM then sold its disk drive division, including the Microdrive trademark, to Hitachi in December 2002. There are now other brands of Microdrives (such as Seagate, Sony, etc), and, over the years, these have become available in increasing capacities (up to 8 GiB as of late 2008).
While these drives fit into and work in any CF II slot, they draw more current (500 mA maximum) than flash memory (100 mA maximum) and so may not work in some low-power devices (for example, NEC HPCs). As they are mechanical devices, Microdrives are more susceptible to damage from physical shock or temperature changes than flash memory. However, Microdrives are not subject to the write cycle limitation inherent to flash memory.
The once popular iPod mini, Nokia N91, iriver H10 (5 or 6GB model), PalmOne LifeDrive and Rio Carbon all used a CF Microdrive to store data.
--------------------------------------------------------
HITACHI 8GB MICRODRIVE
Manufacturer: Hitachi
Models: 0A40701, HMS361008M5CE00
Specifications
Configuration
Interface: ZIF connector PATA interface
Capacity (GB): 8
Sector size (bytes): 512
Disks: 1
Areal density (Gbits/sq.inch, max): 119
Performance
Data buffer (KB): 128
Rotational speed (RPM): 3600
Latency average (ms): 8.33
Media transfer rate (Mbits/sec): 68 131
Interface transfer rate (MB/sec, max): 33 Ultra DMA mode-2
Sustained data rate (MB/sec): 5.1 - 10.0
Seek time (read, typical)
Average (ms): 12
Track to track (ms): 1
Full track (ms): 24
Reliability
Error rate (non-recoverable): < 1 per 1.0 E 13 bits transferred
Load/unload cycles: 300,000
Power
Requirement: +3.3VDC (+5% / -15%)
Current (read/write): 190mA
Current (peak): 310mA
Physical Size
Height (mm): 5 / 0.1
Width (mm): 40 / 0.2
Depth (mm): 30 / + 0.0 / - 0.4
Weight (g, typical): 13
Environmental Characteristics
Operating
Temperature: 5 to 60 Degrees C
Shock (half sine wave): 400 G (2 ms)
Random Vibration (RMS): 0.67 G (5 to 500 Hz)
Altitude: -300 to 3048m
Acoustics (Bels, Idle (Typical)): 1.8
Non-operating
Ambient temperature: -40 to 70 Degrees C
Shock (half sine wave): 2000 G (1 ms)
Random Vibration (RMS): 3.01 G (5 to 500 Hz)
RoHS Compliant: Yes
Manual about microdrive from site: Hitachi.com
What is Compact Flash?
Compact Flash (CF) is a standard for a small form factor device that encompasses CF flash data storage cards including magnetic disk cards, such as the Hitachi Microdrive. The CF card provides high capacity storage and I/O functions that electrically comply with the PCMCIA standard. While only the size of a matchbook, CF cards can be used to store a large amount of data.
Are CF and CF+ the same or are they different?
While the standards are similar, they do have several differences. First, the CF+ standard supports I/O mode and non-Flash storage (true IDE mode). Additionally, the CF+ standard calls for power levels up to 500ma for both 3.3vdc and 5.0vdc power sources.
For more information on the Compact Flash specification, please visit the following URL: http://www.compactflash.org/
If I format a Hitachi Global Storage Technologies Microdrive using my PC, can I still use the Microdrive with my digital camera?
For best results, we recommend that you format the Hitachi Microdrive using the device that you will be using the most. Most devices will format the Microdrive using that FAT16 file system. 4GB and higher Microdrives require the FAT32 file system to be able to use the full capacity of the drive. Some digital cameras are not able to support FAT32. Check with the device manufacturer for any firmware updates that may be available.
Are drivers required when using the Hitachi Microdrive in Windows, 95, Windows 98, or Windows ME?
To use a Microdrive with Windows 95, Windows 98, or Windows ME device drivers may be required. The device drivers and installation instructions can be found at the following URL: http://www.hitachigst.com/hdd/support/mddwnld.htm
Note: These drivers are ONLY for Windows 95, Windows 98, and Windows ME. Windows 2000 and Windows XP do not require any drivers to use the Microdrive.
Can a Hitachi Microdrive be used with a Macintosh?
Yes, a Hitachi Microdrive can be used with a Macintosh. The Macintosh will require at minimum OS 8.0. We also recommend checking with Apple to verify compatibility with your specific system.
I am having problems getting my Hitachi Microdrive to work in my digital camera or hand-held device. What can I do?
First, check with your system manufacturer to verify compatibility between the Hitachi Microdrive and your camera or hand-held device.
If your device has been tested compatible by the device manufacturer, verify that it is operating properly by checking the following items:
* Does your camera or hand-held device support the capacity and file system of the drive?
* Are there any firmware updates for your camera or hand-held device?
* Does the drive work in any other devices/systems?
* Does your camera or hand-held device work with a CF memory card?
* Where you able to format (initialize) the Microdrive?
* Was there a possible cause for error, such as using the Microdrive above or below the operating temperatures of 5 to 55 degrees Celsius? Has the Microdrive suffered an impact or mishandling? Has the Microdrive been subjected to high humidity or static electricity?
How do I format my Hitachi Microdrive?
The factory format of a 2GB or smaller Hitachi Microdrive is FAT16 while the factory format of a 4GB or larger Microdrive is FAT32.
If you are formatting the Hitachi Microdrive in Microsoft Windows (the recommended platform), you can right click on the drive icon and choose Format. If you are formatting the Microdrive in the Mac Operating System, you can use the Disk Utility program. For formatting instructions for your camera, handheld system, or PDA, please see the device’s documentation.
Are there any limitations as to how many times data can be written to a Hitachi Microdrive?
Because the Hitachi Microdrive is actually a hard disk drive, there are no limitations as to how many times data can be written to the drive.
Can the Hitachi Microdrive be used to copy data from a PC?
If you are using a card reader that is compatible with the Hitachi Microdrive it is possible to copy data from the PC to the Microdrive. In case of a notebook PC it is possible by way of the PC Card slot. In this case, a PC Card adapter which corresponds to CF+ Type II is necessary.
What do I do if I am unable to remove the Hitachi Microdrive from the CF card slot?
Please try the following methods to remove the Hitachi Microdrive:
1. If one is available for the CF slot, try pushing the eject button. If it does not work at first, try again.
2. Try using the operating system to eject the drive. If the operating system thinks a program is currently using the drive, you may have to reboot first.
3. Try lightly pinching the corners of the drive with thumb and finger to dislodge the drive. Do not use pliers to get the Microdrive out of the CF card slot or pinch the drive in the center as this may damage the drive.
If you still cannot remove the Microdrive, contact the CF device manufacturer.
Can the Hitachi Microdrive be removed from a CF card slot while the power is still on?
It is possible to remove the Hitachi Microdrive while the power is on, but if the drive is performing a write or save, removing it at this point could result in loss or corruption of data or possibly damage to the drive. Please wait until the drive is finished with its current operation before attempting to remove the Microdrive.
Will the X-ray machine at airport baggage inspection stations damage my Hitachi Microdrive?
X-Ray machines at the airport will not have a direct effect on a Hitachi Microdrive.
Can I carry the Hitachi Microdrive in my pocket without using the carrying case?
We highly recommend using the carrying case when transporting the Hitachi Microdrive. The case provides protection from impact and static electricity.
When I shake the Hitachi Microdrive, it makes a sound. Is this normal?
The sound that is heard when you shake a Hitachi Microdrive comes from the headlock mechanism. However, shaking a Microdrive can lead to damage and or failure of the device. Please do not shake it.
Is it possible to get the Hitachi Microdrive repaired if it is damaged or does not work?
If the drive is still in warranty and the conditions of the warranty are met, the warranty stipulation of replacing the drive will be satisfied. There are currently no companies we are aware of that have the proper machinery to physically repair a Hitachi Microdrive.
Will static electricity damage the drive?
Yes, static electricity can and will cause damage to the Hitachi Microdrive. Be sure to follow precautions when handling the Microdrive and when the drive is not in use, store it in the carrying case.
Can the PC Card Adapter which is used with the 340MB, 512MB and 1GB Hitachi Microdrive also be used with the 2GB, 4GB, or 6GB Microdrives?
Yes, because the PC Card adapter conforms to CF+ Type II standards regardless of the capacity.
Can a PC Card adapter, other than a HITACHI made adapter, be used with the Hitachi Microdrive?
You can use a PC Card adapter, provided that the PC Card adapter conforms to the CF Type II standard. Please check with the PC Card adapter manufacturer to verify compatibility.
I accidentally formatted my 4GB or higher Hitachi Microdrive in my camera and now it is only being detected as 2GB. How do I get my drive back to the full capacity?
If for any reason your drive is no longer being seen at the correct capacity, you have two options:
1. If you are using a Windows 2000 or Windows XP system, you can contact the Technical Support Center to obtain a utility that will reformat the drive to the correct capacity. The utility must be run from within Windows XP or 2000 and only while the drive is connected via card reader or PC Card adapter.
2. 2. Connect your drive (via card reader) to a Windows 98 system and run Fdisk on the drive. You will need to delete the current partition and then recreate a partition using the entire capacity of the drive. After you created the new partition, you can then format the drive and begin using the drive again.
Why will my Hitachi Microdrive work in my PC, but not in my camera or PDA?
Most likely, the drive is a white label (True IDE) version of the Hitachi Microdrive instead of the blue label (CFII+) Microdrive. The majority of white label Microdrives were intended for use as embedded storage in specific systems and may or may not function correctly in another environment.
Shown: White Label Microdrive Shown: Blue Label Microdrive
After using my Hitachi Microdrive to take pictures, I connected the drive to my computer to download the pictures but am being asked to format the drive. How do I get my pictures?
Somehow, the information on the drive became corrupt. This can occur any numbers of ways ranging from software being written incorrectly to a physical problem with the Hitachi Microdrive. If the drive is still being detected by the system, you may still be able to recover the data from the drive. You would need to use a data recovery program designed to recover data from inaccessible devices. Below is a link to a Google search on data recovery software.
http://www.google.com/search?hl=en&lr=lang_en&safe=off&q=data+recovery+software
My Hitachi Microdrive is not detected properly or is not working correctly in my digital camera. Is the drive bad?
Before replacing the Hitachi Microdrive, we recommend visiting the camera manufacturer’s website to obtain the latest firmware for your camera. Many times, a firmware update is able to resolve compatibility issues or certain conflicts that may cause the Microdrive to appear defective.
Can I install the Hitachi Microdrive even though my system is not the compatibility list?
While we make every effort to test the compatibility of the Hitachi Microdrive with a wide variety of systems, it is not possible for us to include all makes and models. This does not mean that the Microdrive will be incompatible with your system. If your system is not listed, it could just mean we have not been able to test that configuration. If your system is not listed in the compatibility list, try contacting the device manufacturer to see if they have performed any compatibility testing with the Microdrive.
hi, i cant access my Microdrive (8GB Hitachi) from my Dopod U1000, i tried to do format microdrive from Start>programme>format/recover microdrive, but it didn't worked. so what to do know? or where can i buy same 8GBHitachi Microdrive in India in Maharashtra? Is it ok if i replace it by 16 or 32GB Microdrive? will it work?
Plz reply me on
[email protected]
Is there someone who found an adapter for the 35-pin proprietary ATA connector of this drive?
Iade
While chatting with dougie187 in the ##adamroot IRC, I was wondering if the antenna was still included in units that are ordered without 3G.
Then got to thinking the possibilities and options available in using the mini PCI-e port. There are a few CDMA cards, I am assuming it would be a matter of drivers and then it was mentioned, the issue with it asking for a SIM card.
Other options I saw was a DIY Sata SSD PCI-e adapter, CF Card to Mini PCI-E Adapter and ZIF CE 1.8 Inch HDD to Mini PCI-E Adapter.
Any ideas?
-CC
i.e. :http://www.amazon.com/RunCore-70mm-50mm-Converter-Adapter/dp/B003BK4OZ8
http://www.amazon.com/CablesToBuy-I...?ie=UTF8&s=electronics&qid=1296584829&sr=1-23
http://www.amazon.com/CF-Card-Mini-PCI-Adapter/dp/B003MMS4SS/ref=pd_cp_e_3
dougie187 linked http://www.hwtools.net/CardReader/MR04R.html
Antenna shouldn't be a problem, they normally come with the card and according to the pictures relatively easy to fit in. The question will be, is the Sim Card connector installed.
I'd like to see if we can upgrade to a bigger flash drive. 8 gb is kinda weak.
Greg G said:
I'd like to see if we can upgrade to a bigger flash drive. 8 gb is kinda weak.
Click to expand...
Click to collapse
You can't "upgrade" the internal 8GB, but you can pop in an sd card and/or usb drive for an additional 128GB +/-...
-CC
clockcycle said:
You can't "upgrade" the internal 8GB, but you can pop in an sd card and/or usb drive for an additional 128GB +/-...
-CC
Click to expand...
Click to collapse
You *might* be able to upgrade the internal 8GB, but it would take some serious modding. It would not be an easy upgrade by any means, and would require some soldering, if it's possible at all. I would not recommend it to anyone for that matter, but someone who REALLY wanted to do it, might be able to.
jupppo said:
Antenna shouldn't be a problem, they normally come with the card and according to the pictures relatively easy to fit in. The question will be, is the Sim Card connector installed.
Click to expand...
Click to collapse
I have a LCD version without 3G. According to the manual the 3G slot sits directly next to the micro sd slot (bottom front corner) so I assume its some sort of shared module or they conveniently sit right next to each other. My version only has a sd slot so I am doubting any 3G hardware is installed. My guess of course.
techboydino said:
I have a LCD version without 3G. According to the manual the 3G slot sits directly next to the micro sd slot (bottom front corner) so I assume its some sort of shared module or they conveniently sit right next to each other. My version only has a sd slot so I am doubting any 3G hardware is installed. My guess of course.
Click to expand...
Click to collapse
Thanks for clarifying it, seems paying the extra $ for the hardware may be worth it.
-CC
clockcycle said:
You can't "upgrade" the internal 8GB, but you can pop in an sd card and/or usb drive for an additional 128GB +/-...
-CC
Click to expand...
Click to collapse
Where would the sd card connect? Assume you don't mean micro sd or we would be talking 32g. Too bad NI didn't go with an SDHC slot instead of the micro sd. Seems like there would be plenty of room for it.
EDIT: Reread your first post. Guess you are thinking we can tie into the mini PCI-e port. That's there or 3G?
Installing 3G doesn't seem to be an option, when there is no sim card connector. As for the internal memory upgrade I see two possibilities:
1) when the miniPCe is fully connected an we find an android tablet with a SSD that provides the device drivers, so that we can port them to the Adam
2) physically mount an usb flash drive internally, reworking one of the external usb ports to do this. There seems to be enough space internally that could fit a dismantelled jump drive..
Any of those SSD adaptors are likely only meant to support the non-standard MiniPCIe implementation that you find in Eee PCs.
tgoode said:
Any of those SSD adaptors are likely only meant to support the non-standard MiniPCIe implementation that you find in Eee PCs.
Click to expand...
Click to collapse
Regardless what miniPCIe implementation you use, you need two things to make it work:
1) Firmware/Bios support
2) Android drivers
My hope lies on the new tablets coming out with SSD's, so that Firmware can be ported and drivers can be used.
jupppo said:
Regardless what miniPCIe implementation you use, you need two things to make it work:
1) Firmware/Bios support
2) Android drivers
My hope lies on the new tablets coming out with SSD's, so that Firmware can be ported and drivers can be used.
Click to expand...
Click to collapse
Perhaps I need to be clearer.
A majority of MiniPCIe SSDs are designed specifically to only work with the eee PC or Dell Mini 9 netbooks. In these non-standard implementations, the PCIe lanes in the MiniPCIe slot are replaced with USB2.0 or SATA depending on if it is the Asus or Dell implementation. They are electrically incompatible with slots that are designed to the true MiniPCIe specification, which is what you most often see being used for 3G modems.
So - here is the question - Does the Adam have a true MiniPCIe slot (likely) or a Dell or Asus implementation (unlikely)?
Oh the possibilities huh...lets see then what are some of the possibilities.
Of course mPCIe card add-ons provided they are non-variant implementation (as stated above, i never knew) not sure how to tell the difference. more info
Open aux port on the 3G card so a external antenna plug.
Swap out microSD for Standard size SD.
Magsafe power cord
Vibration
Laptop Lockdown port
One True white Bright LED
or
A crap ton of ugly rainbow LEDs (and the obligatory clear case *yuck)
Built in induction charger
Audio-in jack
A barometer
As mentioned internal Flash drive.
Add near field communications chip
Back track pad.
Add Infra Red
Solder on more internal memory.
Wacom Pen
I would not know how to do much of anything on this list, just looking for a jumping off point for people. Anyone else got any ideas?
tgoode said:
Perhaps I need to be clearer.
A majority of MiniPCIe SSDs are designed specifically to only work with the eee PC or Dell Mini 9 netbooks. In these non-standard implementations, the PCIe lanes in the MiniPCIe slot are replaced with USB2.0 or SATA depending on if it is the Asus or Dell implementation. They are electrically incompatible with slots that are designed to the true MiniPCIe specification, which is what you most often see being used for 3G modems.
So - here is the question - Does the Adam have a true MiniPCIe slot (likely) or a Dell or Asus implementation (unlikely)?
Click to expand...
Click to collapse
Are you sure? I've done quite a bit of searching around and it seems post MiniPCIe implementations have either a SATA or PATA controller embedded. For example: Search newegg for SSDMAEMC040G2C1 (Sorry about the link, but apparently I don't have enough posts to be link trustworthy :\)
Am I correct in assuming this should work once drivers are provided?
BuckeyBall said:
Are you sure? I've done quite a bit of searching around and it seems post MiniPCIe implementations have either a SATA or PATA controller embedded. For example: www (dot) newegg (dot) com/Product/Product (dot) aspx?Item=N82E16820167039&cm_re=MiniPCIe-_-20-167-039-_-Product[/url]
Am I correct in assuming this should work once drivers are provided?
Click to expand...
Click to collapse
No, there needs to be BIOS support for SATA/PATA as well. All SSD's (and USB storage) needs to have some kind of controller, that's normal.
And as said earlier, some SSD's won't work due to incompatibility, but they normally say that in the specs of the SSD.
When Defy's 512MB RAM is not enough one may think of replacing it with newer model, but what if...
Suppose that:
1. TI's OMAP3610 can handle >512MB of RAM (seems reasonable)
2. A29 address line track is present on PCB (could be; it would require disassembling Defy, desoldering RAM IC and checking)
3. There's a way to alter amount of RAM that is seen by Android (how to do it?)
If all of the above could be achieved then it would mean we could expand Defy's RAM by replacing RAM IC and introducing some changes to the Android (kernel I guess).
What do you think?
EDIT:
1. Is true according to "OMAP36xx Multimedia Device Silicon Revision 1.0" (SWPU177B)
SDRAM controller (SDRC):
– Mobile single data rate (M-SDR) SDRAM and low-power double data rate (LPDDR) SDRAM
– 16-bit or 32-bit data, two chip-selects, configurations for a maximum of 1-GB address space per chip-select
The problem may be the SDRAM may be stacked on the OMAP's top.
The device includes two external memory interfaces supporting the stacking of a multichip memory
package using the generic POP interface.
It must be checked. All we need to know at the point would be to get some broken Defy, disassemble it and see if the SDRAM is separate or stacked. If separate then too desolder it and check if the address line was routed.
I've had my Toshiba Satellite C660-15R since 2010 and I'm not sure if it's time to replace the 320GB Hitachi 10080PBN200CSHPN HDD that was Installed by Toshiba, as Ubuntu Linux says the HDD has 1 Bad Sector back when I was using Ubuntu, but using Segate Sea Tools for Windows its passed all tests.
I'm unsure if it would be wise to replace the HDD based on its age, or stick with it due to the test results from Sea Tools for Windows?
Roland
Id say keep it, 1 bad sector equates to a negligible amount of data (handful of Mb) and isn't necessarily an indicator that the disk is dying, it could have just been scratched if the laptop moved during a write operation ir anything.
It may fail soon, it may not, I have an 80gb drive as a secondary in my desktop which is date stamped as 2003, my old laptops first hard drive lasted just 2 years.
Only reason I would swap the laptop in that machine if the disk is still working is as an upgrade to a bigger size or an SSD or something and that may not even be required
SixSixSevenSeven said:
Id say keep it, 1 bad sector equates to a negligible amount of data (handful of Mb) and isn't necessarily an indicator that the disk is dying, it could have just been scratched if the laptop moved during a write operation ir anything.
It may fail soon, it may not, I have an 80gb drive as a secondary in my desktop which is date stamped as 2003, my old laptops first hard drive lasted just 2 years.
Only reason I would swap the laptop in that machine if the disk is still working is as an upgrade to a bigger size or an SSD or something and that may not even be required
Click to expand...
Click to collapse
Ok thanks.
I've swapped it out for a 1TB HDD, since I've been upgrading the Wifi Card and adding a new battery when it arrives, going to use the old drive in a USB caddy attached to the Router as a backup drive.land
It's also given me a reason to have a fresh start and sort out what needs to be on my HDD and what can go on the Network drive.
Ro
I've been looking around at all the forums an am yet to find a success story on this, I must admit if I'd known it was a hdd I may have just gone with the 16gb.
Has anyone out there made the swap to SSD?
My thoughts and I'm no expert would be to try and install on the SSD then swap out in the shield just to get it booted up and go from there but if was that simple better people than me would have done so already...
Any ideas?
I doubt the board has a transitional SATA header. The built in HDD might be soldered or use some other method of power and data connection.