Related
Hello,
I have looked at the pinouts on the Wiki for the Wallaby and Himalaya and was wondering if it was the same on the Alpine, so that I could hook up to the serial console port on a switch to manage it locally. I have installed Putty and it looks as though it provides the right functions, just the lead to worry about now.
Has anyone done it, or have any advice?
Thank you,
Andrew
the pinout is the same, I have used a serial gps with my apline so i know the serial port is correct and functional
as far as i know for comms you only need TxD, RxD and ground (wired to 2,3 and 5 on a 9 pin serial port)
Thank you Maltloaf, I have a spare USB and serial leads here so I will give it a whirl later.
Thanks again,
Andrew
I thought I would just report on the fact it works perfectly. I made a fully occupied serial lead (null modem type) and have been happily administrating the access points. It was a total pain in the backside to solder to those little tiny connections but it was worth it.
Thank you,
Andrew
Hey all,
I was wondering if it is possible to communicate with an Arduino with a Tilt through the Tilt's USB port? I've just gotten into device application development and I had a cool idea I was wanting to make but the biggest hurdle is how to communicate between the Arduino microcontroller and the Tilt.
For those that don't know what an Arduino is (I feel sorry for you ), it is a microcontroller platform based off of the AVR Atmel168 processor. The version I've got on hand right now is a Seeeduino that has a mini-USB port on-board communicating to the Atmel168 through an FTDI USB-Serial chip (shows up as a serial port when plugged into the computer). It would be great if the Arduino showed up as a new serial port on the phone when plugged in, but I doubt it will be that easy. Does anyone know if the Tilt/Kaiser USB port can host other devices?
If anyone has a suggestion or has tried something like this, please comment. Or if I'm just crazy for thinking the phone can do this, tell me so.
Thanks all!
-Jeremy
USB drivers
Im not sure how much this could help, but it may get you off to a good start http://forum.xda-developers.com/showthread.php?t=480899
i noticed it said serial port in there somewhere, so i hope it helps!
You can have a try with the drivers mentioned above. If this fails, hook a Bluetooth module to your Arduino and forget about wires
When I was waiting for a haircut today, I was fiddling in the task manager and looked at the devices tab. Just thought I'd run these by you all:
Com 8: serialusbfn.dll (\Drivers\USB\FunctionDrivers\Serial_Class)
Com 9: Serial_UART.dll (Drivers\BuiltIn\SERIAL_UART3)
I haved searched around or messed with these yet but what in the world could com 8 be being used for right now?
-Jeremy
P.S. I did see that link and that will be the next thing I'll try, Thanks!
AFAIK there are some internal peripherals that are connected to the main processor through serial ports. That might be those.
Use I2C - you can get at it through the DS2746... when looking at the PCB on the side with all of the metal-enclosed areas, it's on the left, and towards the bottom (IIRC)... should be able to run 4 wires (get a ribbon cable) out the bottom (into the battery compartment)...
I've been considering this seriously... I2C is a damn useful bus, and it's underused in this device (only battery chip, touch screen, and camera control, AFAIK)....
The bus itself is two wires - SDA (data) and SCL (clock), and you'll also need +5v and ground.
Would be nice to hook up a spare ds1621 (you can get these as free samples) or a compass/accelerometer chip
I thought I would put all of my findings in one thread, feel free to ask questions below.
Dock Connector
The dock connector is functional in the latest branch of the Nexus 7 kernel found on android source (android-tegra3-grouper-3.1-jb-mr1-fr). The top pin is ground, the second is the right audio channel, the third the left and the bottom pin is 5V. Upon connecting the ground and 5V lines the audio on the dock connector is enabled and the internal speaker is disabled. I used a piezo element to check so I'm not sure how good the audio is, but it is definately there.
Variants
From the kernel source code there are 3 different project ids but 4 names. Nakasi (the standard Nexus 7), Nakasi 3G, Bach and ME370TG. Nakasi 3G and Bach share the same project ID. This is interesting as the project id table states that Nakasi and ME370T are the same, but also separates the ME370TG and Nakasi 3G. It is also revealed that there are, or have been, two power management ICs and two GPS ICs used in the product. For power management both a TI chip and a Maxim chip have been used, though I believe all? of the current Nexus 7 have the Maxim one. The two GPS' used have been the BCM47511 and BCM4751. In addition to this there have been 4/6 PCB revisions. SR3 appears to be very early as some of the code excludes it, and it also has ID 0 assigned. ER1-ER3 appear to be the current series and my C9O Nexus 7 is revision 3, this can be checked in the bootloader, it is noted as "HW VERSION" or version-hardware in fastboot ("fastboot getvar all").
In my kernel compile below I have added a simple debug output that displays the PMIC ID, project ID and pcb ID. If you decide to test the below kernel for the dock functionality it'd be appreciated if you post the output from /proc/kmsg. The line that I have added looks something like "HEADSET: PMIC: 0 Project ID: 0 Revision: 3 UART_enable:1". This means that I have the Maxim PMIC, it's a Nakasi device and the PCB is revision ER3. The reason it's in headset is explained below.
Fastboot OEM Commands
The oem lock and oem unlock commands are well known, however through looking at the bootloader run through strings I have found 4 additional commands that may be of use. I have found oem off-mode-charge 0 and oem off-mode-charge 1. These appear to enable or disable off mode charging, eg charging without the device being on. The more interesting command is however oem uart-on (and oem uart-off). This causes the bootloader to pass debug_uartport=lsport,0 to the kernel, I am not sure however where "lsport" is but it is referenced in arch/arm/mach-tegra/common.c, if uart is not enabled in the bootloader (evident by fastboot getvar all showing uart-on as no) then the bootloader passes debug_uartport=hsport. The 0 appears to indicate the port it outputs on.
Headset UART Output
In the headset driver (/sound/soc/tegra/headset.c) there is reference to a debug board that can be used to get a UART output. From what I understand this is enabled by setting a line-out pin low, however I am having issues working out which one. I have also attempted to enable this for anything inserted, and while this worked, my simple 4 connector 3.5mm plug breakout didn't reveal any data. I'm leaving this one out there for other people to try. For reference, https://android.googlesource.com/kernel/tegra/+/b0d6be9e2033745e46624e518f55e067b75bcd50 is the commit when the debug board was added. I also commented out it's PMIC check to ensure that it did not stop because I have a Maxim PMIC. This should not matter I believe it is just a way to filter out retail Nexus 7s as it can supposedly cause issues with powered headphones.
The driver also shows the possibility for headset support, however I have yet to investigate this.
Kernel Build
I have built a kernel in an attempt to enable as much of the above as is possible. It has working dock functionality and some additional debug information in relation to the headset UART output. My only changes from the default branch are in headset.c and are as follows:
Code:
if(project_info == GROUPER_PROJECT_BACH ||
(project_info == GROUPER_PROJECT_NAKASI/* && pmic_id ==GROUPER_PMIC_TI*/))
UART_enable = true;
revision = grouper_query_pcba_revision();
printk("HEADSET: PMIC: %i Project ID: %i Revision: %i UART_enable: %i\n", pmic_id, project_info, revision, UART_enable);
It should be fairly obvious what bit of code it replaces, it's in headset_init(void).
I have only provided the kernel as a ramdisk and zImage as the ramdisk depends upon the ROM you use. If you use CM10 then these will work, else you'll have to extract the ramdisk from your current boot.img with a tool such as abootimg. This can be run using the fastboot boot command, "fastboot boot zImage initrd.img" or by using the fastboot flash:raw command, "fastboot flash:raw boot zImage initrd.img". The latter is permanent while the former is once only.
This kernel does not support overclocking, special IO schedulers or any special "optimizations". It never will, it is purely to work out how to activate some of the hidden functions in our Nexus 7s.
Note to Moderators
Wasn't really sure where this thread should go, if you feel this should be moved then please do.
Update
Update to the status of UART. I have successfully got it recognizing the headphone port as a debug board, however I cannot yet get any output. To make it see a debug board, ensure that you have a 4 piece connector (yes the Nexus 7 hardware supports a headset) and connect ground to band 3 (band 1 being the tip) and 3.3v to band 4. When you plug it in it'll be reported as debug board if using my kernel.
So to make a speaker dock, is it really just as basic as hooking up the right speaker to the right pogo pin for sound to start playing?
That and 5V to the respective pins. You will also need a kernel based on the newer android-tegra3-grouper-3.1-jb-mr1-fr branch. The kernel I posted above will work.
ben1066 said:
That and 5V to the respective pins. You will also need a kernel based on the newer android-tegra3-grouper-3.1-jb-mr1-fr branch. The kernel I posted above will work.
Click to expand...
Click to collapse
Right. Of course. It is just that I remember when someone was reverse engineering the galaxy nexus dock I believe the dock had like a motherboard and chip that needed to be decoded for the dock (and everything else) to work properly.
But this is so simple! Maybe I will take the plunge with this one to try and build myself.
Not so here, it works straight off the bat. Also got the ME370T schematic and it appears I'm connecting to the UART right, I think maybe the kernel is doing something wrong, or I've killed the port on my Nexus 7 with a massive 3.3V, that seems unlikely as I was also using 3.3V to make it detect it as a debug board.
ben1066 said:
Also got the ME370T schematic
Click to expand...
Click to collapse
Omg please share
Google is your friend, it's not that hard to find. I shouldn't really post a direct link.
ben1066 said:
Google is your friend, it's not that hard to find. I shouldn't really post a direct link.
Click to expand...
Click to collapse
Do you mean the one on baidu? I was hoping for one that has the full 90 pages
I only have the 44 page one unfortunately, however it does contain the UART specific bit. I'm now wondering if the odm_production_mode fuse disables it. I don't suppose if anyone still has an ICS Nexus 7 and if they could get me in touch with them?
Coming soon to a Nexus 7 near you.
jonnyg1097 said:
So to make a speaker dock, is it really just as basic as hooking up the right speaker to the right pogo pin for sound to start playing?
Click to expand...
Click to collapse
I'm going to assume that this will be a line level signal. You will need a preamp/amplifier to power your speaker.
Mr. Thompsn said:
I'm going to assume that this will be a line level signal. You will need a preamp/amplifier to power your speaker.
Click to expand...
Click to collapse
I see, I am no sound expert so I got a question to ask... if I dont have one of those attached to it will sound still come out but just not clearly or not come out at all? Or what if I were to use put one in and it's not needed would it affect it in any way?
You will need amplification to get any reasonable volume above that for headphones.
Can we charge the N7 through those +5v and ground pins? Possible touchstone charger case mod?
We can charge however the kernel will need modifying to ignore it when it comes down to audio, otherwise you will end up having no audio out while it's charging, at least through the speaker. Headphone port overrides the dock.
Asus dock
I had wondered what those pins were for when I unboxed my N7. Isn't Asus supposed to be coming out with a dock for this thing? I saw a picture of it a week or two ago and I really want it.
Not to sound pessimistic, but I think the Nexus 7 II will be shipping before anyone gets around to making a pogo dock...
Sent from my Nexus 7 using Tapatalk 2
ben1066 said:
We can charge however the kernel will need modifying to ignore it when it comes down to audio, otherwise you will end up having no audio out while it's charging, at least through the speaker. Headphone port overrides the dock.
Click to expand...
Click to collapse
I'm not really interested in the sound part. The only thing I miss from my HP Touchpad is the inductive charging. These pogo pins seem like the easiest way to add inductive charging to my N7.
Sent from my Nexus 7 using Tapatalk 2
ben1066 said:
That and 5V to the respective pins. You will also need a kernel based on the newer android-tegra3-grouper-3.1-jb-mr1-fr branch. The kernel I posted above will work.
Click to expand...
Click to collapse
so clarify this for me. There is only single channel audio from the pogo dock port?
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
You're a power user. Can the Google Pixel 2 keep up? Rate this thread to express how "healthy" the development scene is for the Google Pixel 2. A higher rating indicates available root methods, kernels, and custom ROMs.
Then, drop a comment if you have anything to add!
How in the hell does Google let their devices languish in locked bootloader prison with carriers anymore? Why don't they give us the ability to root the phone if we're developers? You'd think you could just jump right in and unlock your bootloader on the Google Store purchased ones (unlocked ones - not Verizon trash) except they don't provide a cable TO CONNECT TO YOUR PC WTF WHY AM I YELLING
Wartickler said:
How in the hell does Google let their devices languish in locked bootloader prison with carriers anymore? Why don't they give us the ability to root the phone if we're developers? You'd think you could just jump right in and unlock your bootloader on the Google Store purchased ones (unlocked ones - not Verizon trash) except they don't provide a cable TO CONNECT TO YOUR PC WTF WHY AM I YELLING
Click to expand...
Click to collapse
am i missing something? i got my pixel 2 from google store, and unlocked / rooted it easily the same day i received it thanks to awesome members here at XDA
it also included the necessary USB-C cable (and adapter to connect to type A usb ports)
Dev strength
xdaninja said:
it also included the necessary USB-C cable (and adapter to connect to type A usb ports)
Click to expand...
Click to collapse
The cable I got was USB-C to USB-C to plug into the phone and the charging brick. The adapter I got was USB-C male/USB-A female so you could attach it to an old phone and transfer contacts. You telling me you got a cable/adapter that let you connect your new phone to your PC?? I'm even more pissed off if that's the case...poor distribution QA on top of the other issues too?!
Wartickler said:
The cable I got was USB-C to USB-C to plug into the phone and the charging brick. The adapter I got was USB-C male/USB-A female so you could attach it to an old phone and transfer contacts. You telling me you got a cable/adapter that let you connect your new phone to your PC?? I'm even more pissed off if that's the case...poor distribution QA on top of the other issues too?!
Click to expand...
Click to collapse
I received the same as you. I used the cable from my moto z2, not sure how it could have come with anything different than what we received.
Yes Google should have included a USB C to USB A male vs female for sure.
Wartickler said:
The cable I got was USB-C to USB-C to plug into the phone and the charging brick. The adapter I got was USB-C male/USB-A female so you could attach it to an old phone and transfer contacts. You telling me you got a cable/adapter that let you connect your new phone to your PC?? I'm even more pissed off if that's the case...poor distribution QA on top of the other issues too?!
Click to expand...
Click to collapse
So Google is now responsible for you having a PC without the proper connections to plug your phone in?
Or are they responsible for you not being able to order a Micro USB to USB C adapter for a few bucks?
Which one is it I wonder...
kendong2 said:
So Google is now responsible for you having a PC without the proper connections to plug your phone in?
Or are they responsible for you not being able to order a Micro USB to USB C adapter for a few bucks?
Click to expand...
Click to collapse
I really want you to be saying this in a sarcastic tone, but since this is the internet and I can't read tone I'm just going to fly into a rage instead.
Are you seriously suggesting that once the pixel 2 comes out everyone on the planet immediately gained the ability to connect USB-C straight to their computers? Or is it that you are seriously suggesting that it is somehow nonsensical to at least include an extra adapter that mates this new cable type to everyone's existing computer connections? Yes we can purchase a crap-ton of adapters that get us from the phone to the ISS but for the minimal cost of this simple connection type and for the cost I paid I would expect that I would be able to connect my development machine to this device in the exact same fashion I've been able to connect EVERY OTHER DEVICE I'VE EVER HAD. They've all been able to connect to my PC out of the box. This is the first time I've opened a new device box and been at a loss for how to immediately get to working on it. Somehow I believe this was an oversight on the part of Google.
Wartickler said:
I really want you to be saying this in a sarcastic tone, but since this is the internet and I can't read tone I'm just going to fly into a rage instead.
Are you seriously suggesting that once the pixel 2 comes out everyone on the planet immediately gained the ability to connect USB-C straight to their computers? Or is it that you are seriously suggesting that it is somehow nonsensical to at least include an extra adapter that mates this new cable type to everyone's existing computer connections? Yes we can purchase a crap-ton of adapters that get us from the phone to the ISS but for the minimal cost of this simple connection type and for the cost I paid I would expect that I would be able to connect my development machine to this device in the exact same fashion I've been able to connect EVERY OTHER DEVICE I'VE EVER HAD. They've all been able to connect to my PC out of the box. This is the first time I've opened a new device box and been at a loss for how to immediately get to working on it. Somehow I believe this was an oversight on the part of Google.
Click to expand...
Click to collapse
Sure sure. Totally an oversight on the part of Google that you did not check which accessoires come with the phone, totally agree.
BTW, what do you think of the included headset? I think the volume is much too low, I can't hear anything. On the other hand, I never had the cables twisted yet!
kendong2 said:
BTW, what do you think of the included headset? I think the volume is much too low...
Click to expand...
Click to collapse
I... :crying: :silly: ... I'm dead.
My 200 dollar Acer laptop has a USB C port and the provided cable works fine for me. USB C is the modern standard that everyone is moving to. Is it that unreasonable to think that Google would provide cabling for the modern standard that most manufacturers are adopting?
I can't be more happy with this phone.
The only thing I'd improve is to have 4 years of Android updates instead of 3.
In development they will always be on the top because of the open binaries / developers previews etc.
However....I think that over the last years security became a top priority and now a lot of people don't open the boot loader. Even Google disabled android pay when you open it.
And the price is not in favour neither. I think Google needs to release a budget Pixel at lower price...something like 400-450$.
Theres the kernels and some homebrew ROMs.
Feels like this device is hard to work on.
TWRP now fails to decrypt after the February update.
A/B partition seems hard to support so theres no official custom ROMs for Pixel 2.
So far this phone is not what I would recommend for the serial flashers and customizers.
Just a normal phone for normal users.
I see development at Linage, at AICP for our device.
GApps are now available for Android 8.1. Many changes had to be made because of project Treble.
There is development, but for now many ppl look into things on their own and not as collective.
bland.life said:
A/B partition seems hard to support so theres no official custom ROMs for Pixel 2.
Click to expand...
Click to collapse
It's something we came up with at Citibank in about 1989 - update to an unused part of storage. If it works, point whatever is using that part of the firmware at the update and use the place the old version sat as the next update space. The update crashed right on the last byte? No problem. You haven't repointed to it, so it's just empty space until the next try. Better than a bricked phone because the battery died right at the end of an update. It's about time Google caught up to the late 80s. (Yes, that was sarcasm.) My only complaint is the SD card - I have to carry an adapter around with me, and keep the SD card and adapter in my pocket. 128GB internal and 256GB external would have been nice. (I already have about 50GB used, and that's with only one TWRP backup.)
Maybe it's time to flash a kernel with speed adjustment, although it seems to be idling around 430-450MHz.