How to enter recovery mode on pumpkin single din unit? - MTCB Android Head Units General

RQ0110E
5.1.1
Single DIN
After trying to flash a firmware update that supposedly for my unit, it starts up but only toast messages are displayed on the screen.
I tried the same power/reset for 5 seconds method used for the double DIN units, and it seems like it works, but the screen folds down and I can't get the screen back up to select any recovery items.
Any ideas?

Pumpkin are a seller only - there are no "Pumpkin" units - "RQ0110E" is a made up name, go to settings/about device and tell us your MCU version, this will tell us what device you have, then we may be able to help

typos1 said:
Pumpkin are a seller only - there are no "Pumpkin" units - "RQ0110E" is a made up name, go to settings/about device and tell us your MCU version, this will tell us what device you have, then we may be able to help
Click to expand...
Click to collapse
TIL, thanks.
RQ00110E is on a sticker on top of the unit. The Model number in Settings says S07.
I cannot get to settings at the moment, like I said, I can only see toast messages.
But this was the version info before I tried flashing it. I made a note of it just beforehand.
MTCB-KLD5-V2.79
Sep 08 2015 20:11:32
Android 5.1.1
Screenshot
http://imgur.com/a/geCCP
It's a single Din unit with flip up screen.
Any help anyone can provide would be great.
I tried updating the firmware because when I plugged the USB DVR camera in, for some reason it disables media audio playback.
I saw that I had an older firmware, and thought I had found a newer version.

Rhoobarb2005 said:
TIL, thanks.
RQ00110E is on a sticker on top of the unit. The Model number in Settings says S07.
I cannot get to settings at the moment, like I said, I can only see toast messages.
But this was the version info before I tried flashing it. I made a note of it just beforehand.
MTCB-KLD5-V2.79
Sep 08 2015 20:11:32
Android 5.1.1
Screenshot
http://imgur.com/a/geCCP
It's a single Din unit with flip up screen.
Any help anyone can provide would be great.
I tried updating the firmware because when I plugged the USB DVR camera in, for some reason it disables media audio playback.
I saw that I had an older firmware, and thought I had found a newer version.
Click to expand...
Click to collapse
The only info we need is the MCU - "RQ00110E" is a made up number by Pumpkin and all MTCB/C headunits are called "S07".
You have a Klyde (KLD) MTCB headunit.
The MCU will not have changed unless you flashed an MCU as well.
Its good to update the firmware, but I need to know what you tried to flash to update it.
What USB port did you use for the DVR ?

typos1 said:
The only info we need is the MCU - "RQ00110E" is a made up number by Pumpkin and all MTCB/C headunits are called "S07".
Click to expand...
Click to collapse
It's a shame the whole rebranding thing seems a bit of a mess.
typos1 said:
You have a Klyde (KLD) MTCB headunit.
Click to expand...
Click to collapse
Good to know.
TBH, it does not say Pumpkin anywhere on the unit, box or anything to do with it. It was bought from Amazon as a Pumpkin HU, but nothing else seems to link it to Pumpkin.
typos1 said:
The MCU will not have changed unless you flashed an MCU as well.
Click to expand...
Click to collapse
I don't think so, it was a single file labelled update.img (see below). I'm not sure what a MCU is.
typos1 said:
Its good to update the firmware, but I need to know what you tried to flash to update it.
Click to expand...
Click to collapse
https://mega.nz/#!lFVVWS7Q!WvezHo2glWLudnsPHcT8godSdI6NvOZUoBNYnqVArUE
from this forum post:
http://www.autopumpkin.com/forum/viewtopic.php?t=1655
typos1 said:
What USB port did you use for the DVR ?
Click to expand...
Click to collapse
The USB connector labelled DVR.
The same as item 1 on the following picture;
http://www.autopumpkin.com/images/11-RQ0110E/1 Din Android 5.1 Lollipop Car GPS DVD Player (15).jpg
(although my connector also had an old ipod connector on it, not just the USB DVR port)
This camera:
https://www.amazon.co.uk/Pumpkin-Ca...qid=1502561032&sr=8-3&keywords=pumpkin+camera
The camera works and records using the software, it just seems to disable the media volume. Disconnect the camera and sound comes back. As per the following thread:
https://forum.xda-developers.com/an...ts/connecting-usb-dvr-disables-sound-t3655299
The radio doesn't work either, and I bought the 12v booster from Pumpkin too, and neither does the bluetooth obd connector :/ not having much joy at all lol.
And thanks for your help so far!
EDIT: OK, having read your links on your profile, I now know what a MCU is Bookmarked!
OK, thanks to your wiki link, I think I know why the bluetooth OBD connector doesn;t link, wrong name. Ideally it would be worth getting a rooted firmware with xposed on to run some of the MTU modules.

Rhoobarb2005 said:
It's a shame the whole rebranding thing seems a bit of a mess.
Good to know.
TBH, it does not say Pumpkin anywhere on the unit, box or anything to do with it. It was bought from Amazon as a Pumpkin HU, but nothing else seems to link it to Pumpkin.
I don't think so, it was a single file labelled update.img (see below). I'm not sure what a MCU is.
https://mega.nz/#!lFVVWS7Q!WvezHo2glWLudnsPHcT8godSdI6NvOZUoBNYnqVArUE
from this forum post:
http://www.autopumpkin.com/forum/viewtopic.php?t=1655
The USB connector labelled DVR.
The same as item 1 on the following picture;
http://www.autopumpkin.com/images/11-RQ0110E/1 Din Android 5.1 Lollipop Car GPS DVD Player (15).jpg
(although my connector also had an old ipod connector on it, not just the USB DVR port)
This camera:
https://www.amazon.co.uk/Pumpkin-Ca...qid=1502561032&sr=8-3&keywords=pumpkin+camera
The camera works and records using the software, it just seems to disable the media volume. Disconnect the camera and sound comes back. As per the following thread:
https://forum.xda-developers.com/an...ts/connecting-usb-dvr-disables-sound-t3655299
The radio doesn't work either, and I bought the 12v booster from Pumpkin too, and neither does the bluetooth obd connector :/ not having much joy at all lol.
And thanks for your help so far!
EDIT: OK, having read your links on your profile, I now know what a MCU is Bookmarked!
OK, thanks to your wiki link, I think I know why the bluetooth OBD connector doesn;t link, wrong name. Ideally it would be worth getting a rooted firmware with xposed on to run some of the MTU modules.
Click to expand...
Click to collapse
Forget the pumpkin forum, use @dsa8310's 5.1.1 firmware in this thread :
https://forum.xda-developers.com/android-auto/mtcb-software-development/mtcb-mtcc-firmware-t3632100
its rooted and it has Xposed.
I dont know what you mean by the "5 second thing for double DIN units" - not heard of that for any units, but recovery is entered by putting a pin in reset and holding down power until it beeps and the lights flash then releasing reset and then releasing power, AFAIK the single DIN units are the same, or you could try the MTCD method which is just holding power for 10 secs until it beeps then it should enter recovery.
The radio will probably be to do with the setting its on in factory settings, or its to do with your OEM booster, but we can sort that later.
Theres no advantage in using BT for OBD if its going to be permanently wired - BT is for if you want to move the devices around and both the head unit and the OBD device are static, most people use BT for it but I can never understand why - USB OBD is faster, more secure and better, still theres a way to sort it, again we can do that once youve got into recovery and flashed a ROM.

typos1 said:
Forget the pumpkin forum, use @dsa8310's 5.1.1 firmware in this thread :
https://forum.xda-developers.com/android-auto/mtcb-software-development/mtcb-mtcc-firmware-t3632100
its rooted and it has Xposed.
Click to expand...
Click to collapse
OK, will do.
typos1 said:
I dont know what you mean by the "5 second thing for double DIN units" - not heard of that for any units, but recovery is entered by putting a pin in reset and holding down power until it beeps and the lights flash then releasing reset and then releasing power, AFAIK the single DIN units are the same, or you could try the MTCD method which is just holding power for 10 secs until it beeps then it should enter recovery.
Click to expand...
Click to collapse
The 5 second thing was how Pumpkin describe putting their units into recovery, pretty much the same as you said; pin in reset and power, wait 5, release reset, wait 5 release power. Anyway, did that and it may have worked. But I can't tell as the screen closes and will not respond to the screen button to come out. So it may have worked, I just cant see it.
typos1 said:
The radio will probably be to do with the setting its on in factory settings, or its to do with your OEM booster, but we can sort that later.
Click to expand...
Click to collapse
Ok, cool.
typos1 said:
Theres no advantage in using BT for OBD if its going to be permanently wired - BT is for if you want to move the devices around and both the head unit and the OBD device are static, most people use BT for it but I can never understand why - USB OBD is faster, more secure and better, still theres a way to sort it, again we can do that once youve got into recovery and flashed a ROM.
Click to expand...
Click to collapse
It was more the lack of spare USB ports (camera in one of the USB ports, plus I want to put a large HDD in the other, my current 500GB only seems to like the front USB port. I want to keep the front USB free for cosmetic reasons, so will need to buy a drive that needs less power I think.), and I dont recall seeing a usb listed obd as compatible, but nevermind. Bluetooth is what I have, if the xposed workaround works, that will do me.

Rhoobarb2005 said:
OK, will do.
The 5 second thing was how Pumpkin describe putting their units into recovery, pretty much the same as you said; pin in reset and power, wait 5, release reset, wait 5 release power. Anyway, did that and it may have worked. But I can't tell as the screen closes and will not respond to the screen button to come out. So it may have worked, I just cant see it.
Ok, cool.
It was more the lack of spare USB ports (camera in one of the USB ports, plus I want to put a large HDD in the other, my current 500GB only seems to like the front USB port. I want to keep the front USB free for cosmetic reasons, so will need to buy a drive that needs less power I think.), and I dont recall seeing a usb listed obd as compatible, but nevermind. Bluetooth is what I have, if the xposed workaround works, that will do me.
Click to expand...
Click to collapse
The rear USB ports are not good, the front is the best, you can try sorting the rears out by adding a powered USB port (ther are threads about it in the MTCB hardware mod section). You can get USB OBD leads that work with Android, I have one, although I have to use it on the front USB, but I have dismantled my unit, added a lead and hidden it behind the unit.
Anyway I m not sure what to do about your screen disappearing, did it disappear when you updated the ROM ?

typos1 said:
The rear USB ports are not good, the front is the best, you can try sorting the rears out by adding a powered USB port (ther are threads about it in the MTCB hardware mod section). You can get USB OBD leads that work with Android, I have one, although I have to use it on the front USB, but I have dismantled my unit, added a lead and hidden it behind the unit.
Anyway I m not sure what to do about your screen disappearing, did it disappear when you updated the ROM ?
Click to expand...
Click to collapse
The screen tries to hide anytime there is power loss to the ignition 12v or the unit is trying to shut down/restart, to the point it can get annoying. It usually responds to the screen open command. Just not after doing the power and reset thing.
When I entered recovery mode when I flashed the bad firmware I did it from the settings menu, the screen went in then, but did respond to the open command.
EDIT: To clarify, the screen opens and closes fine when not attempting recovery mode.
Can do a video of the behaviour if need be
EDIT 2: Supposing that it is in recovery mode, just unseen, can I not just rotate the volume knob counter clockwise one click and hold the power button to accept the "img/mcu from USB" option (working from a bad memory here)?

Rhoobarb2005 said:
The screen tries to hide anytime there is power loss to the ignition 12v or the unit is trying to shut down/restart, to the point it can get annoying. It usually responds to the screen open command. Just not after doing the power and reset thing.
When I entered recovery mode when I flashed the bad firmware I did it from the settings menu, the screen went in then, but did respond to the open command.
EDIT: To clarify, the screen opens and closes fine when not attempting recovery mode.
Can do a video of the behaviour if need be
EDIT 2: Supposing that it is in recovery mode, just unseen, can I not just rotate the volume knob counter clockwise one click and hold the power button to accept the "img/mcu from USB" option (working from a bad memory here)?
Click to expand...
Click to collapse
So the problem atmo is that the screen is black apart from toast messages ? If so then put @dsa8310's firmware on an sd card, put it in the sd slot (the gps one if you have 2) and hopefully it will autosense the update, if it does you ll get a toast asking if you want to continue, touch ok.
---------- Post added at 09:31 PM ---------- Previous post was at 09:25 PM ----------
I would also try updating the MCU to MTCC KLD5 v2.97 (find it on either of the fileservers in my signature) - KLD Lollipop ROMs usually only work with MTCC MCUs and the very last MTCB MCUs (2.85 and 2.86), I notice your MCU is MTCB v2.79 and I m surprised its such a low version, @dsa8310's ROM has a feature that allows L ROMs to work with ANY MCU, which is one of the reasons I suggested you flash it, but updating to an MTCC MCU is a "belts n braces" approach.

typos1 said:
So the problem atmo is that the screen is black apart from toast messages ?
Click to expand...
Click to collapse
Yup, you get the lollipop splash, then 2 droids dancing around each other as the boot screen. Then to black (booted) If I insert an SD card the toast message pops ups saying sd card mounted, I think the volume slider works as well. And the "shutting down" splash works too.
typos1 said:
If so then put @dsa8310's firmware on an sd card, put it in the sd slot (the gps one if you have 2) and hopefully it will autosense the update, if it does you ll get a toast asking if you want to continue, touch ok.
Click to expand...
Click to collapse
Will do, will report back in a few, need to find my sd adapter :/ lol

Rhoobarb2005 said:
Yup, you get the lollipop splash, then 2 droids dancing around each other as the boot screen. Then to black (booted) If I insert an SD card the toast message pops ups saying sd card mounted, I think the volume slider works as well. And the "shutting down" splash works too.
Will do, will report back in a few, need to find my sd adapter :/ lol
Click to expand...
Click to collapse
Right, I think its the fact that the MCU is too old a version of MTCB/not MTCC.
You got no sd card slot ??

typos1 said:
So the problem atmo is that the screen is black apart from toast messages ? If so then put @dsa8310's firmware on an sd card, put it in the sd slot (the gps one if you have 2) and hopefully it will autosense the update, if it does you ll get a toast asking if you want to continue, touch ok.
Click to expand...
Click to collapse
"SD GPS Card mounted", but nothing else. Same in the other sd port
typos1 said:
Right, I think its the fact that the MCU is too old a version of MTCB/not MTCC.
Click to expand...
Click to collapse
OK, does that help us at all?
typos1 said:
You got no sd card slot ??
Click to expand...
Click to collapse
2x micro SD. on the front of the head unit, yes. I just didn't have the means to get it from my computer If it isn't usb I usually just use bluetooth or wifi.
I found an old micro- sd to usb, so all good. Well at least as far as that goes.

Rhoobarb2005 said:
"SD GPS Card mounted", but nothing else. Same in the other sd port
OK, does that help us at all?
2x micro SD. on the front of the head unit, yes. I just didn't have the means to get it from my computer If it isn't usb I usually just use bluetooth or wifi.
I found an old micro- sd to usb, so all good. Well at least as far as that goes.
Click to expand...
Click to collapse
The GPS port is the one you want, you can update in recovery but if you cant get into it . . . you have the MCU on the root of the sd card ?
It helps in that I think I know the problem.
Try turning it off and on again.
You can try seeing if it auto detects the update on usb not sure it will though.

typos1 said:
The GPS port is the one you want, you can update in recovery but if you cant get into it . . . you have the MCU on the root of the sd card ?
Click to expand...
Click to collapse
Only .img file that came with the download you linked to get.
typos1 said:
It helps in that I think I know the problem.
Click to expand...
Click to collapse
Is it bad?
typos1 said:
Try turning it off and on again.
Click to expand...
Click to collapse
It's a bit late to do that tonight, darkness spoils the plans, will have to be in the morning.
typos1 said:
You can try seeing if it auto detects the update on usb not sure it will though.
Click to expand...
Click to collapse
Will give that a try too.
And again, thanks for your help so far

Rhoobarb2005 said:
Only .img file that came with the download you linked to get.
Is it bad?
It's a bit late to do that tonight, darkness spoils the plans, will have to be in the morning.
Will give that a try too.
And again, thanks for your help so far
Click to expand...
Click to collapse
I d do the MCU update first, as I said earlier you want MTCC KLD5 v2.97 its on both the fileservers on my signature, it takes a ciouple of mins to do and should restore your screen. Then you can do the ROM update tamoz.

typos1 said:
I d do the MCU update first, as I said earlier you want MTCC KLD5 v2.97 its on both the fileservers on my signature, it takes a ciouple of mins to do and should restore your screen. Then you can do the ROM update tamoz.
Click to expand...
Click to collapse
OK, tried it, and only the "card mounted" toast message popped up, nothing else.

Rhoobarb2005 said:
OK, tried it, and only the "card mounted" toast message popped up, nothing else.
Click to expand...
Click to collapse
Try rebooting with the card in the unit.

typos1 said:
Try rebooting with the card in the unit.
Click to expand...
Click to collapse
Ok, tried it. Still no joy.
Going to try with the mcu and image on the usb then right turn the volume knob 3 times then hold

Rhoobarb2005 said:
Ok, tried it. Still no joy.
Going to try with the mcu and image on the usb then right turn the volume knob 3 times then hold
Click to expand...
Click to collapse
Hmm, this is where it gets tricky as usually you d just go into recovery, have you also tried with the ROM in the sd card ?

Related

MyGuide 3100 ROM sample

This is a FLASH-able ROM sample. My question is : Is there any way to edit this and add more programs to it ? (the flash is for some of the MyGuide 3100 devices on the market. another question : is it the same for my device ?)
I tried to flash my device with this... it worked but it still does'n boot. only the boot image has changed. it's still frozent at about 8-10%.
Here is the sample :
http://rapidshare.com/files/140578865/MYGUIDE_3100_DACH_Inand_Update.rar
Guess no one is able to give a hand with this ?
the persisent registry do not want to go away even after flashinf it. i guess it just replaces the os and bootloader anl does not touch the partition that holdes the registry. any ideea how can i make it delete/replace the registry too ?
the device has 3 partitions (it copies the windows folder on RAM) :
1. The bootloader
2. the registry
3. the OS ( called BINFS - i can see but not edit or copy)
hello,
once i received my myguide 3100, it did NOT start.
it rested on a bootscreen showing some kind of "progress bar".
i managed to fix this by installing the firmware again, downloaded at the manufacturers website http://www.myguidegps.com/
it worked for a few months properly. since last week, i've got the same problem again....
but unfortunateley, the manufactuerer does NOT provide any more support...
seems they are insolvent or some...
could one of you guys gife me the original firmware for this device to get it working?? the one in this thread does not.... dont know why
would be SOOO nice
myguide3100 - arival naca400
Hello!
I have a similar problem with a A_rival naca400 which is said to be a clone of myguyde3100. Can you help me with a rom and drivers for myguide3100 try to write in arival?
Bricked my device using the downloaded firmware
Hello. I also have a big problem with My 3100: I downloaded the firmware attached to the first post and fleshed it to my device. Unfortunatelly, something really is wrong , because the update never reached 100%, it allways stops at 98%. Since then (about 2 weeks) i searched all around the web but couldn't find anywhere another firmware (a good one this time). forumleecher, you mentioned you have a valid firmware. Could you be so kind to upload it somewhere for me and others who need it? The original source, www.myguide.com is no longer available, since the company bancrupted and all it's sites are gone. Would be a great help.
Please help us with some good rom for myguide3100.
Looking for a few weeks and yet I found something that works.
You should be very careful by downloading and flashing devices by accident.
There are different hardware platforms of MyGuide 3100 on the market and flashing the wrong ROM will cause boot failures.
Afaik there are no ROMs available in the net (haven't discovered yet) and MyGuide is insolvent.
Cheers
sdr you solve this problem??? and how
MyGuide 3100 GO
same problem here, i am looking 4 a good rom
OK guys. I know how to do total hard reset registry and rest MyGuide 3100(i had the same problem with registry boot keys)
Download this first
http://rapidshare.com/files/299528735/myguide_3100_total_reset.rar
1. First You have to open PNA, disconnect power supply, SD-card etc.
2. After that You have to desolder this big metal cover.
3. Under this cover You will find k9f2g08 Chip.
4. Now you have to connect pin 9 to GDN and connect the battery.
5. Now wait until progress bar start moving, after he start, disconnect Pin 9 from GND.
6. The progress bar should load normal to the end and on the screen should be picture with SD-card.
7. Disconnect battery, assemble PNA and have fun
CHIP ENABLE RUlezz
[email protected]
hi
Mice20 said:
OK guys. I know how to do total hard reset registry and rest MyGuide 3100(i had the same problem with registry boot keys)
Download this first
http://rapidshare.com/files/299528735/myguide_3100_total_reset.rar
1. First You have to open PNA, disconnect power supply, SD-card etc.
2. After that You have to desolder this big metal cover.
3. Under this cover You will find k9f2g08 Chip.
4. Now you have to connect pin 9 to GDN and connect the battery.
5. Now wait until progress bar start moving, after he start, disconnect Pin 9 from GND.
6. The progress bar should load normal to the end and on the screen should be picture with SD-card.
7. Disconnect battery, assemble PNA and have fun
CHIP ENABLE RUlezz
[email protected]
Click to expand...
Click to collapse
unfortunately not functional on MyGuide 3100 go
What exactly is happening with your PNA??>
Maybe You did something wrong.... GND connection or wrong PIN..?
Tell me what display is viewing ???
Hello
My daughter had a problem with her MYGuide 3100, it simply would not switch on any more.
I stripped the unit down and removed the big metal cover (not very well but it worked anyway) and then found this...
You can see a different chip to the Samsung one noted but I have guessed that it is just a matter of where they sourced the chips from.
Chip used to ground pin 9...
So I ground pin 9 and followed the instructions to now find that I get this...
The unit now boots but the progress bar will no longer progress beyond the amount shown in the above photo.
THe unit can no longer be switched off, but just reset. It also is not recognised by Windows and thus is not accessible.
It gives me the impression that sadly the unit is dead
In this type of nand FLASH memory, You have to connect pin nr 30 to GND and fallow with step's .
Pin 9 is NC(non connected) so that's reaction for GND connection is totally normal.
PS. I don't have email notification about post's here so if You can give me a shot about progress on my mail too ([email protected])
Thanks for what you have posted but alas it simply does not work. I found details of the chip too and realised that I needed to short a different pi, the one that you have so kindly noted, but it still does not allow the unit to boot.
This has also been noted here...
http://forums.ebuyer.com/showthread.php?t=11402&page=66
I am guessing that the ROM image is somehow corrupt and even though there is RomUpdate_RD_R01.exe available without a working USB connection, or an image to upload, then it is just a dead GPS.
Ok. So You have broken rom......Last chance to wake him up is desoldering the chip and write rom file on it in external programmer (Willem, cheapest one).
My solution is working for wrong writed registers(but rom must be ok).
Write , if You need deeper details
I appreciate your help. However the sourcing of a programmer and then the likelihood of me being able to desolder that chip has made in beyond my levels of skill to repair.
Thank you again for your help
write with what?
Mice20 said:
Ok. So You have broken rom......Last chance to wake him up is desoldering the chip and write rom file on it in external programmer (Willem, cheapest one).
My solution is working for wrong writed registers(but rom must be ok).
Write , if You need deeper details
Click to expand...
Click to collapse
I still can't find a rom image for 3100 go....
You will find him on working PCB of 3100go. This is the fastest way
Thanks Mice
Mice20 said:
You will find him on working PCB of 3100go. This is the fastest way
Click to expand...
Click to collapse
Thank you for the fast reply, unfortunately I don't have another one....
If you have a hex file or someting like that and you can post it please do it.
Now I try to find a jtag solution.

Trackball boot

PLZ help im freaking out. i accidentally booted into the blue light mode, but when i pulled the battery and rebooted the backlight wouldnt work. i could see everything and even navigate my phone but only under a light. the backlight just wont turn on during boot and changing the setting doesnt help.
i dont get it the thing was working 10 minutes ago and now i cant use it what should i do? i love this phone but i cant afford a new one. is there a way to tell it to turn on during boot in the console?
ok new update the backlight works if i have the keyboard open. i know 100% its software and not the screen. something when wrong with the boot prosses or something.
i think the trackball boot (bluelight boot) must have options but wont display on the screen maybe. like a bios menu. this is very infuriating
Why don't you restore a recent backup?
i have even went as far as downgrading with the .nbh file. and re installing the bootloader (Just the original, didnt want a brick).
Definitely NOT a software problem.
This is a HARDWARE problem -- hence the fact that it works when the keyboard is open.
When you pulled the battery, you might have twisted/pulled something.
*** I would check the ribbon cable connecting the display to the main body!!!
Bluelight mode (where you end up by booting with the trackball pushed in), is just a serial console allowing interfacing with the radio firmware. Unless you actually had a serial cable connected and punched in some commands (which happen to be security locked, therefore wouldn't work for you anyways), bluelight mode wouldn't be able to do this.
lbcoder said:
Definitely NOT a software problem.
This is a HARDWARE problem -- hence the fact that it works when the keyboard is open.
When you pulled the battery, you might have twisted/pulled something.
*** I would check the ribbon cable connecting the display to the main body!!!
Bluelight mode (where you end up by booting with the trackball pushed in), is just a serial console allowing interfacing with the radio firmware. Unless you actually had a serial cable connected and punched in some commands (which happen to be security locked, therefore wouldn't work for you anyways), bluelight mode wouldn't be able to do this.
Click to expand...
Click to collapse
if that were the case than wouldnt it flicker if i flex the screen/hinge ? ill try anything at this point cuz im outa warranty and have no money . im going to the store later trying to update to official 1.6 so i can convince them its software related and they may replace it for me.
oh forgot to mention that if i close it and open it the light stays off untill i hit end and unlock with menu again. im not to sure if that helps.
OK OK OK you are right. i just half closed it and the light stayed on untill it compleatly closed (so the screen flipped, i thought that is what triggered it) and then i got it to stay on completely closed and then the problem flipped to it wouldnt come on while open and now back to the way it was. so im going to go buy a T5 screw driver today and clean the contacts of the ribon cable and reinsert it (i have had experience with that just need to know what ribon. a pic would be nice)
projectzro said:
OK OK OK you are right. i just half closed it and the light stayed on untill it compleatly closed (so the screen flipped, i thought that is what triggered it) and then i got it to stay on completely closed and then the problem flipped to it wouldnt come on while open and now back to the way it was. so im going to go buy a T5 screw driver today and clean the contacts of the ribon cable and reinsert it (i have had experience with that just need to know what ribon. a pic would be nice)
Click to expand...
Click to collapse
There is only one ribbon running to the screen. Try THAT one.
lbcoder said:
There is only one ribbon running to the screen. Try THAT one.
Click to expand...
Click to collapse
LOL lbcoder - always practical.
lbcoder said:
There is only one ribbon running to the screen. Try THAT one.
Click to expand...
Click to collapse
lol ok didn't know that a lot of the devices I have taken apart have had 2 one for the desplay and one for the backlight. Getting a T5 screw driver in half an hour. Will post results later. Hopefully this works, therr area few more ppl with the same problem.
projectzro said:
lol ok didn't know that a lot of the devices I have taken apart have had 2 one for the desplay and one for the backlight. Getting a T5 screw driver in half an hour. Will post results later. Hopefully this works, therr area few more ppl with the same problem.
Click to expand...
Click to collapse
There are two wires going to the screen.. sounds like the "top" one is loose... The jtag photos will give you an idea (it's the two com ports next to the jtag test points)
These are usually taped down very well..
Also you need both a T5 and T6.. the "Security" (has black void sticker) screw is larger than the others.. and a small flat head screwdriver to unclip the cover..
If all else fails: replacement screens seem much cheaper than the phone on ebay.
ezterry said:
There are two wires going to the screen.. sounds like the "top" one is loose... The jtag photos will give you an idea (it's the two com ports next to the jtag test points)
These are usually taped down very well..
Also you need both a T5 and T6.. the "Security" (has black void sticker) screw is larger than the others.. and a small flat head screwdriver to unclip the cover..
If all else fails: replacement screens seem much cheaper than the phone on ebay.
Click to expand...
Click to collapse
ok got it apart 3 times and no luck its prolly the ribbon cable. im going to test that soon. i have a donor phone comming soon from a friend who dropped it in water, the ribbon cable should be fine to use. if that doesnt work im thinking maybe it is software. either way if i cant get it fixed by next month im spending $410 on a new mytouch 3G brand new from the store and getting insurance XP

CC updates and reboots non-stop since Aug 2014. No answer from Google.

Hi all. I have this issue with my CC.
In two words:
One day CC received an update, downloaded it to 100% and rebooted. After reboot update process started again. And again. This started in Aug 2014.
Tried to use original wall charger, with and without HDMI extender. Result is the same.
Factory reset doesn`t work (both - from app and by holding button). CC reboots and begins to download the update again. Without initial setup because it still remembers the configuration.
The only way to get to main screen and use the APP - is to disconnect WAN cable from router, so CC will use the WiFi network without Internet access.
Found this thread in Google Support, posted a reply. The sympthoms and all actions are the same.
https://productforums.google.com/forum/#!topic/chromecast/3L4KNPi7BIU[1-25]
In the end of Aug CC started to work normally.
For a week.
And since Sep it is useless piece of plastic for me and others in that thread of Google Support Forums.
Any ideas how to bring it to life back? Device is not rooted. Firmware version is 16041.
I was thinking of buying Teensy, but want to give a last shot here.
For me something like that happened. When it was updating, make a factory reset and when it reboots, unplug it.
Make sure that you plug it to a wall plug and using a convenient adaptor to power the chromecast. Then, plug to HDMI again, and USB and, for me, it finished.
Also check the noise of the adaptor. Put it near your ear and listen if the sound is normal. Also, if still failing, try another adaptor.
fer456 said:
For me something like that happened. When it was updating, make a factory reset and when it reboots, unplug it.
Make sure that you plug it to a wall plug and using a convenient adaptor to power the chromecast. Then, plug to HDMI again, and USB and, for me, it finished.
Also check the noise of the adaptor. Put it near your ear and listen if the sound is normal. Also, if still failing, try another adaptor.
Click to expand...
Click to collapse
Thanks for trying to help. I have tried all of cables and adaptors and TVs I have. I dont know which combos of reset+plug+unplug I have tried for this 6 months.
k3nny2k said:
Thanks for trying to help. I have tried all of cables and adaptors and TVs I have. I dont know which combos of reset+plug+unplug I have tried for this 6 months.
Click to expand...
Click to collapse
OK. Then, you have tried a lot of things. But, can you send a video of the TV image and the pilot of the chromecast?. What type of TVs you tried? You can also try to use a friend's TV.
Also, I suggest you to force a OTA update:
http://forum.xda-developers.com/showthread.php?t=3026442
If none of these things work, you should contact Google in their forums or to the warranty. But not sending feedback on the app, because that is only for feedback. i don't know for sure what you need to do for send your device. I can't help you on that [emoji20] .
But try the reset combination. Send a video if you can showing what's on TV, pilot, the process you follow to restart, and how you force OTA.
Also, you should try to unplug it, wait a bit, plug again to HDMI and press the restart button BEFORE plug USB.
Different combinations can help. Also, if you can, send in the video the last method above.
More things:
- Try without HDMI connected
- In any moment it get blank pilot?
- Your mobile recognise it?
- If doesn't work factory reset, make sure you're pressing the button in about 1 minute and very strong (for make sure youre pressing well). And tell me if the light state change on that time.
Thanks [emoji1] !
First of all, thanks a lot for options.
fer456 said:
OK. Then, you have tried a lot of things. But, can you send a video of the TV image and the pilot of the chromecast?. What type of TVs you tried? You can also try to use a friend's TV.
Click to expand...
Click to collapse
Samsung le40c550 and Toshiba 22L1353.
Also, I suggest you to force a OTA update:
http://forum.xda-developers.com/showthread.php?t=3026442
Click to expand...
Click to collapse
Thanks, that was something new and promissing. But no
If none of these things work, you should contact Google in their forums or to the warranty. But not sending feedback on the app, because that is only for feedback. i don't know for sure what you need to do for send your device. I can't help you on that [emoji20] .
Click to expand...
Click to collapse
As i wrote in OP - already contacted Google Support Forums. "Plug original adaptor, make factory reset" and so on.
Worst thing is - I cannot make replacement, though It was bought in another country.
But try the reset combination. Send a video if you can showing what's on TV, pilot, the process you follow to restart, and how you force OTA.
Click to expand...
Click to collapse
Made a short video of my efforts this evening.
https://www.dropbox.com/s/elql9jtkbnam20o/CC2.mp4?dl=0
Also, you should try to unplug it, wait a bit, plug again to HDMI and press the restart button BEFORE plug USB.
Different combinations can help. Also, if you can, send in the video the last method above.
Click to expand...
Click to collapse
Didn`t manage to make a video, too hard to do it alone
But, If I press button BEFORE plugging USB - there is no reaction at all. Held it for 2 full cycles.
- Try without HDMI connected
Click to expand...
Click to collapse
Tried. No effect. White LED (downloading, applying), Red LED - reboot.
- In any moment it get blank pilot?
Click to expand...
Click to collapse
Generally - no.
Got it for 5-10 seconds by sending reboot commands via CURL from linux console, but after a few secs it goes to reboot again.
Another option to see it for 5-10 secs - is to change language for example. But only for secs.
- Your mobile recognise it?
Click to expand...
Click to collapse
After boot, and at about 30% it can be recognized by mobile app, i can go to Devices, change any settings, view firmware version, reboot and FDR.
- If doesn't work factory reset, make sure you're pressing the button in about 1 minute and very strong (for make sure youre pressing well). And tell me if the light state change on that time.
Click to expand...
Click to collapse
You can see on the video, that button works. 1. Press the button 2. wait for blink on TV 3. LED blinks from white to red, then white again.
k3nny2k said:
First of all, thanks a lot for options.
Samsung le40c550 and Toshiba 22L1353.
Thanks, that was something new and promissing. But no
As i wrote in OP - already contacted Google Support Forums. "Plug original adaptor, make factory reset" and so on.
Worst thing is - I cannot make replacement, though It was bought in another country.
Made a short video of my efforts this evening.
https://www.dropbox.com/s/elql9jtkbnam20o/CC2.mp4?dl=0
Didn`t manage to make a video, too hard to do it alone
But, If I press button BEFORE plugging USB - there is no reaction at all. Held it for 2 full cycles.
Tried. No effect. White LED (downloading, applying), Red LED - reboot.
Generally - no.
Got it for 5-10 seconds by sending reboot commands via CURL from linux console, but after a few secs it goes to reboot again.
Another option to see it for 5-10 secs - is to change language for example. But only for secs.
After boot, and at about 30% it can be recognized by mobile app, i can go to Devices, change any settings, view firmware version, reboot and FDR.
You can see on the video, that button works. 1. Press the button 2. wait for blink on TV 3. LED blinks from white to red, then white again.
Click to expand...
Click to collapse
Thanks for the video
Really strange. Also seems that doesn´t do a factory reset as normal.
Sorry but i don´t have idea what to do. The only thing I can say is to interrupt the OTA by unplugging the chromecast and try to plug again and before turn on the light, use the reset button. But i don´t have more possible solutions.
I can provide you a support link from Google in Spanish (my languague). I will translate you all the important info but if you want, you can use a translator or ask me.
The phone number to request support. Change Spain to your country: https://support.google.com/googleplay/answer/6179357?rd=2
Google says:
- We can only replace your chromecast with a device that can be sold and used on the same country that you bought the original.
You said it before. But I suggest you to try to get a chromecast and receive it on your house using a transport business like UPS or going to that country, if it isn´t too far. Also, you can try to call to your local Google´s support phone to ask all I said above (the possibility to send it to that country and receive it with UPS) and also ask for a repair on your country if that isnt possible in any way.
Also i suggest you to open a new thread (to see if they look more on you ) with all the details like you do here and attach the video . All of that to give the support forums an idea and they wont say you that is your fault!!!!! :good: Is THEIR fault!. And see if they can give and advice to Google and fix it on a OTA update or help you too to return your Chromecast! Everything is possible...
Also take that survey after publish the thread related to setup problems. And when they ask you for comments or more problems, tell a bit resumed everything and attach the link of the thread you published.
https://docs.google.com/forms/d/1zmdQtKU41r7KB6Ys9sKSJnPbnw1lg8QE0M5t6gRow4g/viewform
Really really good luck from me!:good:
Tell us the results!!!
Yep, factory reset doesn`t work. CC always remembers his name and WiFi credentials.
You said it before. But I suggest you to try to get a chromecast and receive it on your house using a transport business like UPS or going to that country, if it isn´t too far. Also, you can try to call to your local Google´s support phone to ask all I said above (the possibility to send it to that country and receive it with UPS) and also ask for a repair on your country if that isnt possible in any way.
Click to expand...
Click to collapse
Not too far. I`m in Russia, bought from USA
And i dont have any document, that confirms purchasing, except manual. I bought it from a man in Russia, who purchased a bunch of CC in USA and resell in RU to get some profit.
In that time CC was unavailable for purchasing in RU, so the options where either to buy from local private resellers, order it on ebay or in google store through third-party, bacause google doesn`t ship goods to RU.
>>"Proof of purchase is required.
>>If you purchased your Chromecast from someone other than a Google-authorised retailer, your purchase is not covered by our warranty. Please review our Warranty policy here."
Also i suggest you to open a new thread (to see if they look more on you ) with all the details like you do here and attach the video . All of that to give the support forums an idea and they wont say you that is your fault!!!!! :good: Is THEIR fault!. And see if they can give and advice to Google and fix it on a OTA update or help you too to return your Chromecast! Everything is possible...
Click to expand...
Click to collapse
I`m not alone with the issue:
https://productforums.google.com/forum/#!searchin/chromecast/update$20loop
And the answer is one: plug out, power off router, plug usb, make fdr, plug hdmi and so on. Useless.
Thanks for trying to help.
My teensy is almost there.
Will try to get root and Eureka. Hope it works.
k3nny2k said:
Yep, factory reset doesn`t work. CC always remembers his name and WiFi credentials.
Not too far. I`m in Russia, bought from USA
And i dont have any document, that confirms purchasing, except manual. I bought it from a man in Russia, who purchased a bunch of CC in USA and resell in RU to get some profit.
In that time CC was unavailable for purchasing in RU, so the options where either to buy from local private resellers, order it on ebay or in google store through third-party, bacause google doesn`t ship goods to RU.
>>"Proof of purchase is required.
>>If you purchased your Chromecast from someone other than a Google-authorised retailer, your purchase is not covered by our warranty. Please review our Warranty policy here."
I`m not alone with the issue:
https://productforums.google.com/forum/#!searchin/chromecast/update$20loop
And the answer is one: plug out, power off router, plug usb, make fdr, plug hdmi and so on. Useless.
Thanks for trying to help.
My teensy is almost there.
Will try to get root and Eureka. Hope it works.
Click to expand...
Click to collapse
And you can't contact to this person?
Yes I see the forum post. But I said open a new one with all the info you provided me here to see if with all the info they can help you more. Because you provide very short description of the problems of the forum. So it's recommended to open new thread to give attention to the support instead using an older one. I hope that you understand me now.
I also read that sentence that google says. But I thought at first time you bought it on a store instead of second hand (or first hand but sold by other person). I suggest you to contact to that person if you can, because that seems that he give you a bugged device.
If the forums or the person you bought it doesn't do anything for you, I suggest you to buy a new one.
Is only 35€.
Finaly Google closed thread with awesome comment "The original issue that was reported here has been fixed; if you're continuing to have this issue, please start a new thread"
Okay, here we go again - https://productforums.google.com/fo...ting-from-a-supported-app/android/WBhIaPlN8Uc
https://support.google.com/store/answer/6178715?hl=en&rd=1#contact=1&ts=462610Try this. Is the same but emailing. Copy all content to the email.

KYD HU does not boot any more

Hey guys, i have a KYD HU and for some days now, it does not boot any more.
When i turn on the engine, the LEDs are flashing for a millisecond. Then darkness.
But the recovery-menu works. I can flash it with a new ROM and the power button
works too. When i chose "restart" same again, flashing led, then nothing happens.
Any ideas?
Do you need more information? Please, i don't want to buy a new HU
I have the same issue.
Same issue here: today when getting the car to drive home from office my HU didn't boot.
But I cannot enter recovery too...
Nobody has an idea?!?
Post specs of the HU
nosidefcp said:
Post specs of the HU
Click to expand...
Click to collapse
It's an EONON G2110Z
i had a issue similiar with that with a diferent HU but the solution might work the same.
connect a wire from your reverse light, positive, to the reverse in wire from the unit. star the car/radio with the reverse gear in. wait 30 seconds and disconnect reverse gear. this might make the radio bypass initial boot. if it works, replace your bootlogo/bootanimation and try again the normal way
Hey, i do not understand this. There normally is a wired connection from the reverse gear for the camera. Which connection du i have to bypass?

[SOLVED] Speakers suddenly dead!

Hello,
Both the earpiece and the other speaker suddenly stopped working on my nexus 6. I am suspecting it is a hardware issue since I performed a hard reset but the issue still persists. The odd thing is that both the earpiece and the speaker are affected at the same time. Are they connected to each other?
Is there any way I can make sure that this is indeed a hardware issue before cracking open the phone?
Thanks
backslashV said:
Hello,
Both the earpiece and the other speaker suddenly stopped working on my nexus 6. I am suspecting it is a hardware issue since I performed a hard reset but the issue still persists.
Is there any way I can make sure that this is indeed a hardware issue before cracking open the phone?
Thanks
Click to expand...
Click to collapse
Hello had the same bug super user app libs was away no root from here to now did nothing.reflashed super su, without​ super user app like supersu or magisk it dont work for me. hope i can help.
Another question, some times i turn on my display an for 3 sec i had more than max brightness, like a sun, no auto adjust always 20%, may the old nexus now die hard, hope not
Before I opened the phone, I'd boot to safe mode and see if things work. If they do, reboot and see if the problem comes back. Booting into safe mode disables all unnecessary apps, clears caches and resets settings to default. Sometimes that resolves your problem and on reboot things are working again.
ktmom said:
Before I opened the phone, I'd boot to safe mode and see if things work. If they do, reboot and see if the problem comes back. Booting into safe mode disables all unnecessary apps, clears caches and resets settings to default. Sometimes that resolves your problem and on reboot things are working again.
Click to expand...
Click to collapse
Thank you for your response. I forgot to mention I already booted to safe mode but it didn't make a difference.
backslashV said:
Thank you for your response. I forgot to mention I already booted to safe mode but it didn't make a difference.
Click to expand...
Click to collapse
So I guess it sounds like hardware. You might take s close look and see if there is damage/dirt in the jack making the device think the headphones are connected. The pin is easily bent and wears so it's probably just that. ifixit has a repair guide.
Alternatively, you might consider Bluetooth headphones [emoji4]
ktmom said:
So I guess it sounds like hardware. You might take s close look and see if there is damage/dirt in the jack making the device think the headphones are connected. The pin is easily bent and wears so it's probably just that. ifixit has a repair guide.
Alternatively, you might consider Bluetooth headphones [emoji4]
Click to expand...
Click to collapse
Thanks. I don't think it's the jack issue because I installed an app that shows a headphone icon in the status bar when a headphone is plugged in and it doesn't show it when nothing is connected.
Do you know why both speakers ceased functioning at the same time AND if there is a way for me to direct audio to only one of them, either the earpiece or the speaker, to see if one or both
are dead?
wow. I reverted back to an earlier build from Feb and now it's working. Very interesting.
speakers
backslashV said:
Hello,
Both the earpiece and the other speaker suddenly stopped working on my nexus 6. I am suspecting it is a hardware issue since I performed a hard reset but the issue still persists. The odd thing is that both the earpiece and the speaker are affected at the same time. Are they connected to each other?
Is there any way I can make sure that this is indeed a hardware issue before cracking open the phone?
Thanks
Click to expand...
Click to collapse
First, sorry to hear about your problem. But, I am actually happy to see this up at xda. Tell you why. I purchased a uesd nexus 6 from a seller on ebay. Description was everythings works. Pics showed it was in excellent condition.
Problem was when it arrived. I discovered the top speaker was trash. Total robot like voice. Of course seller denied any knowledge of it. My option was to return it to him. But judging from the way he spoke to me. I could tell it was going to be a fight. There is no way he did not know about this. I wound up eating the phone and am currently awaiting a new top speaker. So, please dont forget to ask about speakers if buying used. My concern was body and screen. I never thought to ask about speakers and I never thought there would be crooks like him. Wrong...
backslashV said:
wow. I reverted back to an earlier build from Feb and now it's working. Very interesting.
Click to expand...
Click to collapse
It is interesting. Is it possible you had a mismatch between kernel and security updates? "Newer" kernel on "older" ROM? Or vice versa. The difference doesn't have to be more than one has a security update that the other didn't.
ktmom said:
It is interesting. Is it possible you had a mismatch between kernel and security updates? "Newer" kernel on "older" ROM? Or vice versa. The difference doesn't have to be more than one has a security update that the other didn't.
Click to expand...
Click to collapse
More like mismatched or corrupted libs or drivers
Know this is an older thread, but just figured I'd post what I found regarding a similar issue I had. My phone basically took a 3 second dunk in the sink. Everything seemed fine the first hour or two, then the speakers stopped working. However, it seems like the speakers failing is some kind of water damage failsafe or something. The solution is just to turn your phone off and on around 5 times (I can't remember the exact number, but once or twice won't cut it), and you will have the speakers return to normal. Not sure if the OP had the same issue, but just an idea in case something similar happens to others.
Bumping an old thread but I had this same issue and had to flash back to previous builds. I stopped updating my phone around Jan/Feb. Tried to update to the Aug 7.1.1 build and the same thing happened again. I didn't try the turn on and off 5+ times, I'm just once again restoring my Jan/Feb build.
Can anyone else confirm this "fix" or has this same problem?
I'd boot to safe mode first. If it works then, it has something to do with an app, your app restore process or something like that.

Categories

Resources