I have been having this problem for a while and I can't seem to find one similar to the issue I am having after searching. My phone has done this pretty much since I got it a year ago.
When I plug the phone in, it doesn't recognize the cable and doesn't start charging. however if I pull down the notification menu I get an option that says "Android System - Charging connected device via USB" if i click on that, I get two options.
USB controlled by:
- Connected device
- This Device
It's always defaulted to connected device. If I change it to "this device" it starts charging. And it will stay on "this device" generally until fully charged and then it switches back to "connected device" the next time I plug it in to charge.
Does anyone know why it's doing this? Or how to make it default to "This Device"?
buugiewuugie said:
I have been having this problem for a while and I can't seem to find one similar to the issue I am having after searching. My phone has done this pretty much since I got it a year ago.
When I plug the phone in, it doesn't recognize the cable and doesn't start charging. however if I pull down the notification menu I get an option that says "Android System - Charging connected device via USB" if i click on that, I get two options.
USB controlled by:
- Connected device
- This Device
It's always defaulted to connected device. If I change it to "this device" it starts charging. And it will stay on "this device" generally until fully charged and then it switches back to "connected device" the next time I plug it in to charge.
Does anyone know why it's doing this? Or how to make it default to "This Device"?
Click to expand...
Click to collapse
Interesting issue....what device are you connecting your Pixel XL to? Are you on Android P / September update? I am seeing different deault behavior I am on a Pixel XL, Android P, September 2018 update. When I plug my phone into my computer via the USB to USB-C cable, it defaults to charge the Pixel FROM the computer. However, one of the comments in the linked article below sounds like if plugging to a Battery back - the phone defaults to CHARGE TO the battery (if the battery isn't ON when connected to the phone). This sounds similar to your scenario. Not sure there is a fix yet - but thought it sounded similar to your experience.
https://www.androidpolice.com/2018/...files-charge-connected-device-simultaneously/
The comment I referenced:
Shawn Kovalchick • 6 months ago
I have an Anker USB-C battery and if I use the USB-C to USB-C cable and don't turn the battery on (or it hets turned off for some reason), then the phone will charge the battery. I wonder if this will fix that.
1
AP Staff Shawn Kovalchick • 6 months ago
I have an Anker battery like that, and I just tested what happens if I plug in and don't turn it on first.
Not only does it start charging from the Pixel 2, as before, the USB option to charge a connected device is automatically on and DOES NOT TURN OFF even if I toggle it off. The charging of the battery pack continues, and if I leave the screen and come back to it, the option is magically checked on again.
I hope they fix this, but even if they do, I don't think it'll actually remember your selection and specific device and will just reset to ON the next time you connect.
sb1893 said:
Interesting issue....what device are you connecting your Pixel XL to? Are you on Android P / September update? I am seeing different deault behavior I am on a Pixel XL, Android P, September 2018 update. When I plug my phone into my computer via the USB to USB-C cable, it defaults to charge the Pixel FROM the computer. However, one of the comments in the linked article below sounds like if plugging to a Battery back - the phone defaults to CHARGE TO the battery (if the battery isn't ON when connected to the phone). This sounds similar to your scenario. Not sure there is a fix yet - but thought it sounded similar to your experience.
https://www.androidpolice.com/2018/...files-charge-connected-device-simultaneously/
The comment I referenced:
Shawn Kovalchick • 6 months ago
I have an Anker USB-C battery and if I use the USB-C to USB-C cable and don't turn the battery on (or it hets turned off for some reason), then the phone will charge the battery. I wonder if this will fix that.
1
AP Staff Shawn Kovalchick • 6 months ago
I have an Anker battery like that, and I just tested what happens if I plug in and don't turn it on first.
Not only does it start charging from the Pixel 2, as before, the USB option to charge a connected device is automatically on and DOES NOT TURN OFF even if I toggle it off. The charging of the battery pack continues, and if I leave the screen and come back to it, the option is magically checked on again.
I hope they fix this, but even if they do, I don't think it'll actually remember your selection and specific device and will just reset to ON the next time you connect.
Click to expand...
Click to collapse
Thanks for the reply. It doesn't matter what I plug the phone into, I have to change this setting for it to recognize. I have tried, the factory Pixel cable and charger. My wife's Galaxy S8 charger with my cable and hers, aftermarket cables. Plugging into a car charger and the built in USB for Android Auto (I have to switch this setting every time I want to user Android Auto), or a computer. The battery is stock, I am not using a battery pack or anything like that.
I am on Android P August update, in the beta program. I have just opted out of the beta. But it was doing this since I got the phone, I switched to the beta to see if it would fix the issue.
buugiewuugie said:
Thanks for the reply. It doesn't matter what I plug the phone into, I have to change this setting for it to recognize. I have tried, the factory Pixel cable and charger. My wife's Galaxy S8 charger with my cable and hers, aftermarket cables. Plugging into a car charger and the built in USB for Android Auto (I have to switch this setting every time I want to user Android Auto), or a computer. The battery is stock, I am not using a battery pack or anything like that.
I am on Android P August update, in the beta program. I have just opted out of the beta. But it was doing this since I got the phone, I switched to the beta to see if it would fix the issue.
Click to expand...
Click to collapse
Really strange. Are you unlocked? Rooted? Have you tried / can you try a factory reset? If unlocked you could flash factory and retain data...sounds like you have some hidden default setting messed up. No idea where that default value is stored though....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I also noticed from your link that my USB options look completely different than Oreo and Pie
sb1893 said:
Really strange. Are you unlocked? Rooted? Have you tried / can you try a factory reset? If unlocked you could flash factory and retain data...sounds like you have some hidden default setting messed up. No idea where that default value is stored though....
Click to expand...
Click to collapse
The phone is straight from Google. So I guess that means it's unlocked. I have not rooted it. I tried a factory reset months ago when I couldn't find an answer. I can do it again though.
buugiewuugie said:
I also noticed from your link that my USB options look completely different than Oreo and Pie
Click to expand...
Click to collapse
Ehhh - that article was from back in March 2018 so likely based on one of the developer previews of Android P....I'm guessing it evolved a bit since then from a visual standpoint - mine looks the same as yours does...
---------- Post added at 10:50 AM ---------- Previous post was at 10:47 AM ----------
buugiewuugie said:
The phone is straight from Google. So I guess that means it's unlocked. I have not rooted it. I tried a factory reset months ago when I couldn't find an answer. I can do it again though.
Click to expand...
Click to collapse
If you are unlocked I would just flash the latest factory image. Be sure to remove the "-w" from the flash-all.bat if you want to retain your data. (Although, depending on where that default preference for charging behavior is stored - retaining data may retain that "bad" default value as well.) Maybe try factory flash with retaining data first and see if it works...before doing the full factory flash and needing to reset up the entire phone and restore your data manually.
Another one bites the dust
Exact same problem with my Pixel XL.
It's difficult to charge the phone because every short power disconnect I have to manually choose "this device" again on else it won't charge.
I'm not rooted but bought it unlocked.
Grts
---------- Post added at 12:51 PM ---------- Previous post was at 12:46 PM ----------
https://www.multitopicblog.com/usb-supplying-power-attached-device-pixel/#comment-133
Same Problem
I have the same problem with my Pixel 3 XL. Did you find a solution?
Just started experiencing this issue 8/1/2019 on a standard Pixel XL
Same issue, started in September. It's completely killed Android Auto for me and routinely leaves me with a dead battery. I've found mention of the issue all over the net but no solution. If anyone comes up with something, please share, it's driving me nuts.
Pixel 2 XL on Android 10 (QP1A. 191005.007.A1)
Related
Hello All,
Recently I bought a X18i from PandaWill (Sorry linking is not permitted for me at this moment)
This model is similar to Sony Xperia Arc. It has 2.3.4 Android and many features but It misses other for me important as Google Talk and other I would like to uninstall (chinese apps).
Anybody can help me for rooting this phone? I tried many methods for other models but I couldn't.
Is it possible to put other ROM than installed?
Thanks in advance
Hi
I´m from Madrid too.
I read in a comment of youtube, that you can root this phone with Super One Click v2.2.
Dou you find other rom for x18i?
Dou you know the official web site of manufacturer Star x18i?
Thank you very much
Hello,
I've just rooted the phone with Super One Click and I could delete all chinese apps from factory.
The problem for this phone is the manage of two sims, I guess that there aren't any ROMS with this function implemented.
If any people knows about it please, post it.
I don't know the manufacturer web
Regards
What ROM would you root it too? Doesn't this already come with Gingerbread 2.3.4
Anything more than that is probably going to be to much for the processor
remember it's only 650mhz, I would just keep what you have, root it, remove the
bloatware and customize it to your taste, that's just me speaking though. Until more is known about the phone, I wouldn't do anything at all.
Yes. You are right. I rooted the phone and deleted all annoying apps. Now I'm wondering if there is any ROM suitable for it.
Now I'm trying to look for google talk app because the phone doesn't has.
Thanks!
Problmes in rooting
autoca said:
Yes. You are right. I rooted the phone and deleted all annoying apps. Now I'm wondering if there is any ROM suitable for it.
Now I'm trying to look for google talk app because the phone doesn't has.
Thanks!
Click to expand...
Click to collapse
Hi autoca:
This is my first post since i was looking someone having same cell phone and who could root it.
I have tried several times with SuperOneClick, but it stops on step #7 Waiting for device so long.
How have you make it? Could you please explain it in more detail.
I am form Spain too
Thanks a lot
is this SE?
you can root with newer flashtool
then install titanium back up pro
uninstall app that you needed
it is a SE clone... and i do not know if this will work. I've tried with SuperOneClick and z4root but nothing.
I am finding some new strange things happening on mi x18i cell phone:
- I cannot see the front LED light indicator of battery status, charging and other info (messages, missing calls...)
- I cannot operate the cell phone while it's being charged: it starts to open apps and type randomly by itself... and it opens the notification bar, activate and deactivate wifi, GPS...
Has anybody similar experiences?
Thanks in advance
sentito said:
I am finding some new strange things happening on mi x18i cell phone:
- I cannot see the front LED light indicator of battery status, charging and other info (messages, missing calls...)
- I cannot operate the cell phone while it's being charged: it starts to open apps and type randomly by itself... and it opens the notification bar, activate and deactivate wifi, GPS...
Has anybody similar experiences?
Click to expand...
Click to collapse
Hi, I don't have x18i phone myself yet but I ordered one and I wait still for delivery. I've found in a Russian forum a discussion about the x18i phones and they say
- it doesn't have any status LED
- the charging problem is caused (maybe only partially) by the charger supplied with the phone. If it is charged from a computer there is no paranormal activities with the phone. So they buy another USB charger to replace the charger supplied with the phone.
Hello,
I used SuperOneClick without problems. I didn't do any special for rooting the phone.
As Anjolle said, phone doesn't have any led for signalling and the problem with the charger I never had because I always charge the phone with a samsung charger or with computer.
Hello X18i users,
I have this phone since 2 weeks and I'm satisfied by the overall functionalities.
No issue observed yet except about the poor quality of the USB cable
On some PCs, it was not possible to synchronise the phone with computer or to activate the usb storage (to see SD card folders on PC).
So I decided to buy a new usb cable with better quality and now everything is working perfectly.
So the issue came from usb cable ...
regards
---------- Post added at 11:39 PM ---------- Previous post was at 11:23 PM ----------
Anjolle said:
Hi, I don't have x18i phone myself yet but I ordered one and I wait still for delivery. I've found in a Russian forum a discussion about the x18i phones and they say
- it doesn't have any status LED
- the charging problem is caused (maybe only partially) by the charger supplied with the phone. If it is charged from a computer there is no paranormal activities with the phone. So they buy another USB charger to replace the charger supplied with the phone.
Click to expand...
Click to collapse
Hello Anjolle, hello Sentito,
Here is my feedback about status LED on x18i:
- on my phone, a red led is flashing slightly on front panel when the phone is in line.
It's the only situation when the LED is visible (nothing during charging or to indicate you missing call ...)
- No problem when phone is connected to PC by USB cable since I replaced the USB cable by newer with best quality
The slightly flashing red LED is part of proximity sensor. It turns off the touch screen when the phone is near your face.
By the way some of the X18i phones have the proximity sensor installed and some don't as people have reported in other forums.
you're right. when approaching the phone to the ear (or put your finger on the sensor), the screen turns off and switch on again as soon as the phone is away. Interesting to know... Thank you for the information.
About root procedure of this device, is someone could share a clear procedure to do it (with SuperOneClick for example) ? Thank you in advance.
I saw also a procedure where people used gingerbreak to root most of known device, but not sure it will work with x18i ...
best regards
I used SuperOneClick without problems. I didn't do any special for rooting the phone.
For some reason I cannot root my phone using superoneclick I tried it at in freezes everytime on the first process on two different computers, I think depending on who you buy it from, some may lock the bootloader some may not. But there is always wH around it, it your having issues with rooting try clokworkmod from the recovery screen via the sd card.
Hi
Do you have the same boot menu than this person from youtube video (see at 2:30)
youtube.com/watch?v=9vExc21fUKc&feature=related
Mine is only twice the bee and a blue droid ...
Do you think this device is rooted ?
Hi all,
I was trying another charger and doing it by PC-USB connection and there is not any problem with the cell phone, so really the problem comes from the carger!! Thanks
Mine have no LED nor proximity sensor as indicated in previous posts... I will try to contact again supplier.
Regarding the rooting: I will try with other USB cable just in case...
Thanks to all.
Other question: do you now if I can use the TV reveiver with DVB (TDT) non-analogic but digital signals??
Cheers
Anjolle said:
Hi, I don't have x18i phone myself yet but I ordered one and I wait still for delivery. I've found in a Russian forum a discussion about the x18i phones and they say
- it doesn't have any status LED
- the charging problem is caused (maybe only partially) by the charger supplied with the phone. If it is charged from a computer there is no paranormal activities with the phone. So they buy another USB charger to replace the charger supplied with the phone.
Click to expand...
Click to collapse
I´m from Madrid too.
I read in a comment of youtube, that you can root this phone with Super One Click v2.2.
Dou you find other rom for x18i?
Dou you know the official web site of manufacturer Star x18i?
Thank you very much
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
sentito said:
Other question: do you now if I can use the TV reveiver with DVB (TDT) non-analogic but digital signals??
Click to expand...
Click to collapse
No, the TV receiver is analog. It can't show you digital broadcast.
It's useless in my country too, so I uninstalled the TV app but unfortunately the FM Radio app was uninstalled as well. I can't figure out how to restore the FM radio app.
hon kong is great.
Hello, new member here. I recently purchased an HTC One M8 from AT&T, unrooted to put superuser on my phone since I really disagree with an operating system telling me what I can and cannot do with the device I purchased. I did not know about S-OFF before this issue so no, it is currently S-ON I believe.
Just to be clear, my phone worked fine after this for ~2 months at least.
Anyways, to the issue. When I try plugging in my charging cable it says:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Although, I do have to say not even all the time. Most of the time when it's plugged in I get zero response that it is. It didn't use to be that way, this was a progression. It started charging fine, then the Car app started booting up asking to accept or decline. The car app doesn't even open up anymore.
So here I'm thinking, either the battery is broken, or the micro USB port.
However, I CAN charge the phone if I have fastboot turned ON and I turn off the phone. It's my understanding that fastboot only puts the phone in a hibernation state and it's not really turned off. When it is in this state, I can plug my charger in and I see the battery appear on the screen charging.
This is the only way I can charge my phone, by turning it off.
I cannot communicate with a PC, I cannot charge while it is turned on. This leads me to believe that this is in fact a software issue and not a hardware issue. However, this issue prevents me from communicating with a PC through USB which removes a number of options for me to test why this is happening.
I can transfer files over WIFI, and I have done so. Yesterday I transferred Android Revolution HD 11.1 to my phone over WIFI and was able to flash it, though I think I have a bad flash and just need to reflash due to a few minutes boot time, and I already read up that you need to try a few times until you get a fast response signifying you got a good image or something like that.
If anyone has any suggestions I am willing to try them, I have everything I need from the phone backed up. I have subscribed to this thread so I should receive a notification.
Tricks that I have tried:
Turning the phone on while the sensor is facing a bright light. Not sure why that would do anything but it was a common "solution".
Powering off the device and holding the power button as well as both volume buttons. This supposedly resets the "charge mode", no result. I was able to boot up to safe mode so I learned that I guess. No it doesn't charge in safe mode.
Draining the battery 100%, holding the power button until no response. Then charging. However, this was a nightmare, as when I tried doing this I got this guys problem: youtube.com/watch?v=r_Nll_01jG0 — This only happens when fastboot is off, or in this case, the power drained and the phone actually turned off, so it clearly only charges in hibernation.
Tricks that I have not tried:
Spraying the port with WD-40 while the device is turned off. Yea okay, I guess I'm worried about putting a liquid/oil in my phone.
They ended up only being tricks, not solutions to the problem. IF it was hardware I would understand completely. I no longer get a response from the phone when it is plugged in except for the occasional error message as the image above. HOWEVER, it charges in hibernation mode, every attempt, nothing weird, it just charges like it should. This is weird to me, because if it was hardware then this should not work. It makes no sense.
I tried an app called USB Host Diagnostics, I'm not sure if this is even going to provide any information to help or not but here is the result: usbhost.chainfire.eu/?search=455254
Since I've changed the ROM / OS of the phone to Android Revolution HD 11.1, and the problem still persists, then the next step down would be the... kernel? So it is either hardware or the kernel? That's just me guessing really... it's so hard to imagine it's the hardware. I take great care of my phone, never dropped it, don't overcharge it, I just don't understand what it could be other than the software of the phone just not recognizing the port while it is turned on, and whatever functions are turned on during hibernation are working correctly. Unless it's a voltage issue where it disables it to protect the motherboard, and during hibernation it isn't a risk, if that's even a thing. If it was a voltage thing, why then would it not charge when fastboot is turned off and the phone is off? It starts up with a battery on the screen then reboots in an endless loop like the video showed above. I just don't understand, wish there was something more to figure out other than it telling me that it's in host mode and can't charge, and by extension can't connect to a PC.
I found something out while just randomly rebooting the device. I rebooted my phone while it was still plugged into the computer and opened up the... bootloader? (Power button + volume down), and then I went to the Fastboot option and I heard the chime on my computer of a new device being detected, and it installed android 1.0 driver or something. I wasn't able to see storage or anything (probably because I was in a bootloader), but I actually heard a response from my computer.
If I toggled between the main menu and FASTBOOT the chime would go on and off between detected and removed.
This really makes me confused, it has to be a software issue right? I've reflashed the android revolution HD ROM multiple times so I don't think it's that... is it my kernel? I am so lost here. The fact that my computer made that chime and installed a driver proves that it can work, but why won't it work when it's turned on?
Hi b.white,
Have you found any solution.
My HTC has shown the same USB in OTG so can't charge problem. It is the first time I have seen this message and problem on my phone. I have my phone for the last few months. I also want to mention that it is as stock as it can get. Never even rooted. I have no popping up CAR app problem. Maybe because it is just been a few minutes the problem showed up. So maybe I'll be seeing the car app later on. But I had about 10% battery on my phone which died out during the few tests I've made.
So right now my phone is turned off (because of battery got to 0%) and is plugged in using standard cable and charger in to a wall socket. It shows that it is charging by using the animation and the percentage is growing continuously. The LED is stable and Amber which means that it is charging.
During the last few battery moments, I turned off the car app through its settings. Never had the daydream setup or turned on anyway. But my fastboot from the settings is off. It was like this when the phone came, and never needed to change this setting.
I also tried this but I'm not sure that I did it correctly and it hasn't showed any difference either.
http://forum.xda-developers.com/showpost.php?p=46415840&postcount=1
While I was keeping the three buttons pressed the phone kept turning on the the htc logo and going back to black screen. I don't think that should have happened, or at least the original thread didn't mentioned this behavior.
This is my main phone. And I am really worried about this problem.
Please help. :crying:
USB Host Mode charging issue (plus Car Mode) just started happening to me last night. I can intermittently charge while the phone is on, but it's inconsistent. Nothing I've tried so far has fixed it for more than a few minutes. Probably will have to send it in for warranty service.
Sent from my Nexus 7 using Tapatalk
OK, so now after I charged my phone to 100% while it was off and turned it back on, I am also having the same CAR mode app problem.
Maybe the latest update that is coming our way can solve this problem. I am talking about the update with the EYE enhancements etc.
I just received my Nexus 7 Gen 2 from an Ebay seller. It came with LineageOS 14.1-20180913-NIGHTLY-Flo installed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have it running carplay pretty flawlessly with the carlinkit wireless carplay adapter (USB dongle).
Now, I have 2 really big issues I need to resolve:
1) I cannot charge the Nexus while the dongle is connected. When I hook a wireless charger to the Nexus, it will only charge when nothing is plugged into the micro USB slot.
2) The only way to wake the screen (after it goes to sleep with the set 5 minute timeout) is to press the top power button. That button is very hard to locate when driving. I need to activate touch to wake or swipe to wake or something.
For 1 and 2 above, what are my options? Is there a version upgrade of the LineageOS that I can get that will address those 2 issues? If not, what would you suggest? Thanks in advance. I'm sure this is going to be great but these 2 issues are a major buzzkill for my carplay joy.
- Scott
Here are some pics of my N7 wireless carplay setup
FWIW, here are a few shots of my setup with the Nexus 7, the Carlinkit wireless carplay adapter, the 3 tail USB adapter cable (I purchased in the event wireless charging + OTG not possible and I have to connect a charger cable to the micro USB slot to make this work). I'm also using the analog audio output of the tablet to route the sound through my car audio.
vestaviascott said:
...1) I cannot charge the Nexus while the dongle is connected. When I hook a wireless charger to the Nexus, it will only charge when nothing is plugged into the micro USB slot.
2) The only way to wake the screen (after it goes to sleep with the set 5 minute timeout) is to press the top power button. That button is very hard to locate when driving. I need to activate touch to wake or swipe to wake or something.
For 1 and 2 above, what are my options? Is there a version upgrade of the LineageOS that I can get that will address those 2 issues? If not, what would you suggest? Thanks in advance. I'm sure this is going to be great but these 2 issues are a major buzzkill for my carplay joy.
- Scott
Click to expand...
Click to collapse
Both issues can be resolved with ElementalX kernel, which features:
doubletap2wake
USB OTG + charge mode
If "USB OTG + charge mode" does not work, make no-battery mod which is preferred for car installations anyway.
:good:
k23m said:
Both issues can be resolved with ElementalX kernel
Click to expand...
Click to collapse
Sweet! So, basically I can install that kernal over top of my existing 14.1 LOS or is there more to it than that? I haven't modded a device before, this one, luckily, already came with LOS pre-installed.
Reading through that opening post, it appears all those functions are "optional". I suppose I'll figure out how to opt-in soon enough, lol.
Also, it says "For fixed-install (Complete working OTG+charge mode) Use version 5.16", so I guess I should follow that?
vestaviascott said:
Sweet! So, basically I can install that kernal over top of my existing 14.1 LOS or is there more to it than that? I haven't modded a device before, this one, luckily, already came with LOS pre-installed.
Reading through that opening post, it appears all those functions are "optional". I suppose I'll figure out how to opt-in soon enough, lol.
Also, it says "For fixed-install (Complete working OTG+charge mode) Use version 5.16", so I guess I should follow that?
Click to expand...
Click to collapse
Yes, for LOS14.1 just install ElementalX-N7-6.17. "Optional" means that you need to activate it during setup.
First try "OTG+charge mode" with your existing LOS. If it does not work AND you don't like the no-battery mod, then do:
install TWRP, backup your LOS and copy the backup to a PC
install stock 6.0.1 - RESTOCK simplifies the process
install ElementalX-N7-5.16 ("For fixed-install - Complete working OTG+charge mode")
:highfive:
k23m said:
First try "OTG+charge mode" with your existing LOS.
Click to expand...
Click to collapse
OK, I don't think my existing LOS (14.1 as indicated in my opening post screenshot) has an OTG+charge mode option, so I expect what you mean by that is to install ElementalX. To be certain, which version are you referring to? ElementalX-N7-6.17 or ElementalX-N7-5.16-cm (I'm assuming "cm" stands for "charge mode") or something else?
k23m said:
If it does not work AND you don't like the no-battery mod
Click to expand...
Click to collapse
After checking out the video, it looks pretty interesting but my concern is that the tablet will basically have to reboot with every time the car engine stop and starts? Unless there is something I'm missing?
The "no battery" option, the more I read about it, may just be the way to go. I just need to figure out where/how to tap a source of constant power to supply to the tablet. I've just purchased a "new" N7 battery from ebay to use as a backup in the event I screw mine up doing this mod. I thought I might be able to buy a ready made cable but no searches returned on ebay for that.
One thing I'm still not certain about is if the no battery option compromises in any way, my ability to connect an OTG device to the tablet. Because the carplay dongle adapter MUST be connected to tablet and its the heart of my carplay solution I'm doing all this for.
With that done, I suppose I'd just need the swipe/touch to wake functionality. Is there an easy way to get that added as a one-click install through the Google Play store over top of my existing LOS 14.1?
vestaviascott said:
OK, I don't think my existing LOS (14.1 as indicated in my opening post screenshot) has an OTG+charge mode option, so I expect what you mean by that is to install ElementalX. To be certain, which version are you referring to? ElementalX-N7-6.17 or ElementalX-N7-5.16-cm (I'm assuming "cm" stands for "charge mode") or something else?
After checking out the video, it looks pretty interesting but my concern is that the tablet will basically have to reboot with every time the car engine stop and starts? Unless there is something I'm missing?
Click to expand...
Click to collapse
vestaviascott said:
The "no battery" option, the more I read about it, is definitely the way to go. I just need to figure out where/how to tap a source of constant power to supply to the tablet. I've just purchased a "new" N7 battery from ebay to use as a backup in the event I screw mine up doing this mod. I thought I might be able to buy a ready made cable but no searches returned on ebay for that.
With that done, I suppose I'd just need the swipe/touch to wake functionality. Is there an easy way to get that added as a one-click install through the Google Play store over top of my existing LOS 14.1?
Click to expand...
Click to collapse
Let's clarify:
ElementalX-N7-6.17 - use with LOS14.1 or stock 6.0.1
ElementalX-N7-5.16 - use with stock 6.0.1
ElementalX-N7-5.16-cm - use with Cyanogenmod (obsolete version of LOS), don't consider it
cm = Cyanogenmod, not "charge mode"
no-battery mod power connection --> ACC/ACCESSORY ignition position or car-battery-direct (*)
doubletap2wake - no Play Store alternative
OTG - no conflict with the no-battery mod
The no-battery mod is really recommended as Li-po batteries do not last long in cars. However without the mod, make sure to activate "Battery life extender" in the kernel's setup.
(*) in direct connection, N7 will drain the car battery after ~2 months of parking (50mA @ screen off) if you don't turn it off.
Thanks for the help. So my task is to install ElementalX-N7-6.17 onto my N7.
I could not find ElementalX-N7-6.17 through a Play Store search, so I'm assuming maybe I will need to download the ROM to a PC/Mac (I have Macs, no PCs) and then connect the N7 to the PC and unzip/extract/copy the 6.17 files over to the N7, disconnect and then restart the N7 to finish the install.
Is that about right? I'm sure I'm oversimplifying. Or should I simply be able to direct install the EX 6.17 software onto my device through the Play Store?
Update: I found a video that seems to be on point for the level I'm at (total newbie to modding devices) and it appears I first need to install a "Custom Recovery" app onto my N7, Based on your suggestions above, I expect that's the TWRP app?
https://www.youtube.com/watch?v=RIi4KXgZYsI
k23m said:
Yes, for LOS14.1 just install ElementalX-N7-6.17. "Optional" means that you need to activate it during setup.
First try "OTG+charge mode" with your existing LOS.
Click to expand...
Click to collapse
How? Do I need to use TWRP for this or should I just be able to do a Play Store search for "ElementalX-N7-6.17" and install it. I'm guessing not, because that search does not appear to return the result. In the response below, it appears to indicate if the above fails, THEN use TWRP, so I'm stuck at this point because after installing TWRP, the "TWRP Flash" option does not offer ElementalX-N7-6.17 as an option. It does offer several "device images" to choose from so I choose what appears to be the latest one at the top of the list "twrp-3.3.1-0-flo.img" which takes me to a download page. After downloading the img, opening it just appears to have downloaded a web page, not an img.
k23m said:
If it does not work AND you don't like the no-battery mod, then do:
install TWRP, backup your LOS and copy the backup to a PC
install stock 6.0.1 - RESTOCK simplifies the process
install ElementalX-N7-5.16 ("For fixed-install - Complete working OTG+charge mode")
:highfive:
Click to expand...
Click to collapse
Kinda spinning in circles here, but after finding no mirrors available to download ElementalX-N7-6.17, I installed "Root Checker" and find that it says "Sorry! Root access is not properly installed on this device"
Maybe I need that for above stuff to work? I probably just need to walk away and come back later. Confused.
Update: I was finally able to get a mirror to download the ElementalX-N7-6.17.zip to my Nexus. Appreciate any help on what to do next. Since this is just a zip file and does not appear to contain an installer, I suppose I need one. Not sure which or how. Thanks in advance for clearing the path for me to get this installed.
vestaviascott said:
Kinda spinning in circles here, but after finding no mirrors available to download ElementalX-N7-6.17, I installed "Root Checker" and find that it says "Sorry! Root access is not properly installed on this device"
Maybe I need that for above stuff to work? I probably just need to walk away and come back later. Confused.
Update: I was finally able to get a mirror to download the ElementalX-N7-6.17.zip to my Nexus. Appreciate any help on what to do next. Since this is just a zip file and does not appear to contain an installer, I suppose I need one. Not sure which or how. Thanks in advance for clearing the path for me to get this installed.
Click to expand...
Click to collapse
I assume that the previous N7 owner had installed TWRP already to flash LOS, if so please do:
copy ElementalX-N7-6.17.zip to N7
boot TWRP
in TWRP "install" the zip and preset desired ElementalX options
boot system - all done
If the above does not work for some reason, here is the complete setup:
copy ElementalX-N7-6.17.zip to N7
setup fastboot on Mac
boot N7 in fastboot mode and connect it to your Mac
install TWRP
boot TWRP
in TWRP "install" the zip and preset desired ElementalX options
boot system - all done
:fingers-crossed:
k23m said:
I assume that the previous N7 owner had installed TWRP already to flash LOS, if so please do:
Click to expand...
Click to collapse
If they did, they must have deleted it. I've installed it via the Play Store.
k23m said:
1. copy ElementalX-N7-6.17.zip to N7
Click to expand...
Click to collapse
I've downloaded the zip via the N7 browser. Check.
2. boot TWRP
Click to expand...
Click to collapse
Assume by "boot" you mean just launch the application on the N7. Done.
3. in TWRP "install" the zip and preset desired ElementalX options
Click to expand...
Click to collapse
There is no "install" button per say, there are 3 options I see, they are:
TWRP Flash
Backup Existing Recovery
Network Statistics
Opening TWRP Flash it asks me to "Select Device". I choose "Asus Nexus 7 2013 WI-FI -- Flo
Next screen shows "Current Device: flo" then "Select a device image to download", there are several files labeled "twrp-x.x.x-0-flo.img".
Not sure what to do next, there is nowhere there to install the zip I downloaded. Perhaps it has to be placed in a certain directory.
ME >>> :fingers-crossed:
vestaviascott said:
If they did, they must have deleted it. I've installed it via the Play Store.
I've downloaded the zip via the N7 browser. Check.
Assume by "boot" you mean just launch the application on the N7. Done.
There is no "install" button per say, there are 3 options I see, they are:
TWRP Flash
Backup Existing Recovery
Network Statistics
Opening TWRP Flash it asks me to "Select Device". I choose "Asus Nexus 7 2013 WI-FI -- Flo
Next screen shows "Current Device: flo" then "Select a device image to download", there are several files labeled "twrp-x.x.x-0-flo.img".
Not sure what to do next, there is nowhere there to install the zip I downloaded. Perhaps it has to be placed in a certain directory.
ME >>> :fingers-crossed:
Click to expand...
Click to collapse
You've got a lot to learn. Turn off your N7, Boot into Recovery(TWRP) by holding POWER an Volume Up buttons simultaneously. Install the elementalkernel.zip file from there. There are tutorials around the web with complete step by step instructions that you should check out.
Genestealer said:
You've got a lot to learn. Turn off your N7, Boot into Recovery(TWRP) by holding POWER an Volume Up buttons simultaneously. Install the elementalkernel.zip file from there. There are tutorials around the web with complete step by step instructions that you should check out.
Click to expand...
Click to collapse
Perfect, thanks. And also thanks to K23m for extreme patience and the PM sent last night which essentially said the same thing. The missing link was:
Genestealer said:
Turn off your N7, Boot into Recovery(TWRP) by holding POWER an Volume Up buttons simultaneously. Install the elementalkernel.zip file from there
Click to expand...
Click to collapse
Done and now I'm upgraded. I can't believe how simple it was once I understood exactly how to do it. They key was what "Boot" actually means and specifically "Boot into Recovery" and how to do it with POWER and VOLUME UP.
Can’t say enough how much I appreciate the help on this leading me through my first attempt at customizing an OS.
The tablet now wakes up when the screen is tapped. I can’t yet get swipe to wake or swipe to sleep working (I did enable those options during install) but most importantly the tablet now charges in my car while the car play adapter is connected to USB.
I have the screen sleep set at max 30 mins and it still steadily gains charge faster than I expected with CarPlay connected and audio output from the 3.5mm audio out. As a bonus, if the tablet is sleeping, it wakes as soon as I turn in the car due to fact it’s connected via the accessory power (cigarette lighter socket with 2.4amp USB adapter plugged in).
One interesting thing is that the OTG device (the CarPlay dongle) does not appear to get power from the battery. It only works when I plug a usb power source into the pigtail adjacent to the dongle. I suppose this is normal?
Some things I’d still like to do I’m not sure if possible via the elementalX options:
1) Force sleep when the power is cut.
2) get swipe to sleep to work
3)
vestaviascott said:
One interesting thing is that the OTG device (the CarPlay dongle) does not appear to get power from the battery. It only works when I plug a usb power source into the pigtail adjacent to the dongle. I suppose this is normal?
Some things I’d still like to do I’m not sure if possible via the elementalX options:
1) Force sleep when the power is cut.
2) get swipe to sleep to work
3)
Click to expand...
Click to collapse
OTG+Charge mode disables self-powered OTG, external power source required.
For sleep when power is cut look into apps like Tasker or MacroDroid.
Swipe to sleep, make sure you doing it right. I'm using ElementalX 7.0, it's a quick swipe LEFT on the NAV bar, not status/notification bar. Some other kernel i used long ago (might have been older elementalx) was a swipe right on notification bar. Try different swiping combinations.
Genestealer said:
OTG+Charge mode disables self-powered OTG, external power source required.
For sleep when power is cut look into apps like Tasker or MacroDroid.
Swipe to sleep, make sure you doing it right. I'm using ElementalX 7.0, it's a quick swipe LEFT on the NAV bar, not status/notification bar. Some other kernel i used long ago (might have been older elementalx) was a swipe right on notification bar. Try different swiping combinations.
Click to expand...
Click to collapse
Thanks. I'll check my gestures and location for swipe to sleep. On the self-powered OTG issue, I believe its confusing my "Carlinkit wireless carplay dongle" a bit - which the developer is actively updating to address issues so maybe its the dongle and not the new settings on the tablet or maybe its a combination. Its like the dongle is not getting power some of the time despite that its connected the exact same as a previous driving session where it worked as expected. This dongle connects via Wifi to the phone. And I'm using a 3 way splitter to allow the dongle and a power cable to be connected at the same time.
Between driving sessions, its hit or miss whether it connects or not. I had to reboot the tablet once to get the dongle to come alive. I'm going to have to troubleshoot what's going on. I haven't had the dongle long enough to know if the problem is with it or with the new settings on the table for OTG_Charge mode.
I suppose it could be one of a few things:
- The tablet
- The dongle
- The cable
- The Power source (a 2 port USB adapter connected to the 12 volt cigarette lighter socket)
FWIW, here's my new carplay setup and thanks to you guys help:
The tablet fits just about perfect in that location. I currently have the two left and right dashboard panel covers slightly ajar and the bottom tablet corners wedge fit behind them. The tablet hasn't budged all day while driving. I'm going to cut out recesses in those panels to allow the tablet to slide in there. In person, It actually appears close to a factory setup but for USB and audio cables coming off the tablet - those are routed behind those cover plates out of sight.
I spent some more time today working with the tablet after the ElementalX upgrade and I believe I understand what's happening now with the connected OTG device failing to come back online after power shut off.
So, since the OTG device is now getting its power from the same cable that's now responsible for charging the N7 (rather than from the battery), when I cut off my car engine, the accessory power source is shut off and the OTG device loses power abruptly. With battery power it would not have to deal with this every time the car engine/accessory power is stopped/started.
So, what appears to be happening is that the OTG device does not like losing power in that way and the only way I can get it to connect again once that happens, is to reboot the Nexus.
I suppose the "No Battery" hack would resolve the issue, since the OTG device would never be shut down and should remain in a ready state at all times.
Short of that, I guess I'll just have to keep rebooting the N7 whenever the dongle crashes. I've tried shutting down the "Autokit" application before shutting down the car engine, but the device is still crashing when power is lost.
A week or so ago my wife's Pixel started really acting up. I'm not 100% sure that it's not related to the June update as they happened within a day of each other. I'm wondering if the download didn't finish or was half installed originally. Anyway, the June update DID eventually install according to the About Phone screen. Here's the issue:
1. Pixel battery started hemorrhaging battery. It loses about 20% per hour in a 45 degree line down the screen when looking at batter stats.
2. Pixel is all of a sudden extremely finicky about what chargers it will work with
a. It will NOT charge with any cable plugged into a brick in a wall outlet
b. It WILL charge with almost any cable plugged into a PC or a charging dock
c. It WILL charge with our wireless charging dock
3. I've done a factory data reset 2x to see if it was an OS install issue or an app issue and nothing has changed
4. On the last reset we didn't install a single app from Play Store, in fact, I didn't even add a Google Account for a day or two
5. After digging around in the charging port and getting out some lint, the phone will now charge with most cables including the OEM brick
6. The battery is still just bleeding power while the phone is sitting there doing nothing
Here's the kicker, I cannot get it to plug in and be recognized by any of the PC's in my house or office. Therefore, I cannot flash it with either a custom ROM or downgrading to a previous Google update. A
Same problem
Jank4AU said:
A week or so ago my wife's Pixel started really acting up. I'm not 100% sure that it's not related to the June update as they happened within a day of each other. I'm wondering if the download didn't finish or was half installed originally. Anyway, the June update DID eventually install according to the About Phone screen. Here's the issue:
1. Pixel battery started hemorrhaging battery. It loses about 20% per hour in a 45 degree line down the screen when looking at batter stats.
2. Pixel is all of a sudden extremely finicky about what chargers it will work with
a. It will NOT charge with any cable plugged into a brick in a wall outlet
b. It WILL charge with almost any cable plugged into a PC or a charging dock
c. It WILL charge with our wireless charging dock
3. I've done a factory data reset 2x to see if it was an OS install issue or an app issue and nothing has changed
4. On the last reset we didn't install a single app from Play Store, in fact, I didn't even add a Google Account for a day or two
5. After digging around in the charging port and getting out some lint, the phone will now charge with most cables including the OEM brick
6. The battery is still just bleeding power while the phone is sitting there doing nothing
Here's the kicker, I cannot get it to plug in and be recognized by any of the PC's in my house or office. Therefore, I cannot flash it with either a custom ROM or downgrading to a previous Google update. A
Click to expand...
Click to collapse
Started days after June update and my problem is that PC can't connect to phone. Phone charges from PC and oddly the PC in device manager sees the 3 xl as an Acer deice and loads the drivers for that. Anyone know of a way to force my PC to upload the Google USB drivers? It should just by connecting to the pixel but I keep getting the Acer ADB Interface.
ahunter said:
Started days after June update and my problem is that PC can't connect to phone. Phone charges from PC and oddly the PC in device manager sees the 3 xl as an Acer deice and loads the drivers for that. Anyone know of a way to force my PC to upload the Google USB drivers? It should just by connecting to the pixel but I keep getting the Acer ADB Interface.
Click to expand...
Click to collapse
Mine sees a Samsung device!
Jank4AU said:
Mine sees a Samsung device!
Click to expand...
Click to collapse
My PC keeps trying to install a Samsung device driver for some reason.
I can pretty much confirm its due to the update, but the may update was the one that messed with the charging procedure in my case. I give you a few tips to clear system cache and reset the device health services.
1: You need to charge the phone fully using the a charger.
2: With the charger still plugged in ...press power and the vol buttons together and let it cycle 4 or 6 times. You will notice that the reboot cycle is much faster on the second boot, this is the one that wipes the system cache and history. 4 times is plenty as the its the second boot that clears it.
3 Let is charge fully again.
4: Go into settings and wipe all data from device health services including ambient display. Uninstall the device health update and restore the factory version and reboot.
This isnt a myth its a low level cache wipe for corrupt cache....you just manually triggering it. Thats all there is to it. You can re install the update to device health after.
---------- Post added at 05:47 PM ---------- Previous post was at 05:42 PM ----------
ahunter said:
Started days after June update and my problem is that PC can't connect to phone. Phone charges from PC and oddly the PC in device manager sees the 3 xl as an Acer deice and loads the drivers for that. Anyone know of a way to force my PC to upload the Google USB drivers? It should just by connecting to the pixel but I keep getting the Acer ADB Interface.
Click to expand...
Click to collapse
You can manually update the driver yourself but i wouldnt advice it, if the pc is recognizing the device as another model you could cause a blue screen by updating the driver to use a google one, i think the best way is to delete the acer drivers so windows uses the generic version that ships with windows 10
My pc uses leedroid adb interface and it works perfectly fine with the google line up. Your pc does this because the adb drivers are basically the same, the pc sees a newer version of this driver and installs it.
Thanks
boe323 said:
I can pretty much confirm its due to the update, but the may update was the one that messed with the charging procedure in my case. I give you a few tips to clear system cache and reset the device health services.
1: You need to charge the phone fully using the a charger.
2: With the charger still plugged in ...press power and the vol buttons together and let it cycle 4 or 6 times. You will notice that the reboot cycle is much faster on the second boot, this is the one that wipes the system cache and history. 4 times is plenty as the its the second boot that clears it.
3 Let is charge fully again.
4: Go into settings and wipe all data from device health services including ambient display. Uninstall the device health update and restore the factory version and reboot.
This isnt a myth its a low level cache wipe for corrupt cache....you just manually triggering it. Thats all there is to it. You can re install the update to device health after.
---------- Post added at 05:47 PM ---------- Previous post was at 05:42 PM ----------
You can manually update the driver yourself but i wouldnt advice it, if the pc is recognizing the device as another model you could cause a blue screen by updating the driver to use a google one, i think the best way is to delete the acer drivers so windows uses the generic version that ships with windows 10
My pc uses leedroid adb interface and it works perfectly fine with the google line up. Your pc does this because the adb drivers are basically the same, the pc sees a newer version of this driver and installs it.
Click to expand...
Click to collapse
Thanks I was going to start your procedure but I hesitate. I had a second laptop that I had just restored to factory default and the phone communicates fine with it. In fact I am transferring music files to the phone as I write. So this leads me to the computer being the problem. On my working laptop the phone shows up as a portable device\Pixel 3 XL. On my problem laptop it is showing as an ACER Device\ACER ADB Interface and I have tried to update & uninstall this device but it always returns when I do a scan for hardware changes.
Had a very similar problem where all of a sudden all of my chargers would only slow charge except for the type C fast chargers, it wouldn't recognize the headphone jack adapter and my phone wouldn't deep sleep at all due to a kernel wakelock that only applies to when a cable is plugged into the phone (can't remember the exact name of it).
Multiple fresh flashes including one with a complete wipe and fresh start would not fix it. I even tried blocking the wakelock and nothing.
Unfortunately the problem has fixed itself randomly and hasn't shown up again so I have no clue what caused it and what fixed it. I thought it was maybe a bad charger port or something got stuck in there but no clue. The only remnant is that the phone will say charging slowly when it gets to around 80-85%.
Forgot to add that I'm actually on the last update for Android 9 instead of 10 but figured I'd chime in just in case
Downloaded a link from this article on XDA https://www.xda-developers.com/pixel-6-november-update-fingerprint-bug-fixed/
but didn't realise they had posted the wrong link and instead used the link for pixel 5a. Phone will connect and disconnect whenever i press power button or either volume buttons. Tried the usual force restart and bootloader button but still black screen and laptop not recognising phone except showing as USB serial device briefly when it does connect
muzab a said:
Downloaded a link from this article on XDA https://www.xda-developers.com/pixel-6-november-update-fingerprint-bug-fixed/
but didn't realise they had posted the wrong link and instead used the link for pixel 5a. Phone will connect and disconnect whenever i press power button or either volume buttons. Tried the usual force restart and bootloader button but still black screen and laptop not recognising phone except showing as USB serial device briefly when it does connect
Click to expand...
Click to collapse
I was messing around with my 6 Pro and ended up in recovery mode. None of the normal button combos were wrorking.
I ended up holding the power button / vol down for nearly 30 seconds and it rebooted back to the fastboot/bootloader mode.
Not sure if this will help you but the usual shorter time needed to boot wasn't working for me, but holding for 30 seconds did.
Good luck!
You could always try Official Google Pixel Update and Software Repair or Official Google Android Flash Tool.
Also, always go directly to the source Pixel 6 Pro Factory Images, don't trust anyone else's links.
didn't work but i can see it connecting and disconnecting constantly. did you have the device show up as USB serial device. Also what kind of cable did use (usbc to usbc?)
muzab a said:
didn't work but i can see it connecting and disconnecting constantly. did you have the device show up as USB serial device. Also what kind of cable did use (usbc to usbc?)
Click to expand...
Click to collapse
You might want to "Reply" or "Quote" the person you're responding to, so they get a notification that they're tagged and know that you have a question for them. I assume you're responding to @Az Biker.
When you have it plugged into your computer, do you see it in Device Manager? USB-C <-> USB-C or USB-A <-> USB-C shouldn't matter, as long as it's the original or a quality cable (Anker or from a previous PIxel or other quality OEM cable).
You can attach a screenshot of your Device Manager if you're not sure what you're looking for.
roirraW edor ehT said:
You might want to "Reply" or "Quote" the person you're responding to, so they get a notification that they're tagged and know that you have a question for them. I assume you're responding to @Az Biker.
When you have it plugged into your computer, do you see it in Device Manager? USB-C <-> USB-C or USB-A <-> USB-C shouldn't matter, as long as it's the original or a quality cable (Anker or from a previous PIxel or other quality OEM cable).
You can attach a screenshot of your Device Manager if you're not sure what you're looking for.
Click to expand...
Click to collapse
sorry , its showing as USB serial device (COM3) under ports section.
muzab a said:
sorry , its showing as USB serial device (COM3) under ports section.
Click to expand...
Click to collapse
No sweat! And it doesn't have an exclamation point through it's icon in Device Manager, right? (which would mean you need to install the latest Google USB Driver).
roirraW edor ehT said:
No sweat! And it doesn't have an exclamation point through it's icon in Device Manager, right? (which would mean you need to install the latest Google USB Driver).
Click to expand...
Click to collapse
nope no exclamation mark. google USB driver installed too
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
muzab a said:
nope no exclamation mark. google USB driver installed too
Click to expand...
Click to collapse
Are you able to shut the phone off? If so, shut it off, wait 10 minutes, then try it again.
Follow Google's instructions exactly on the Official Google Pixel Update and Software Repair or Official Google Android Flash Tool web page.
Try another USB port.
Try another USB cable.
If a desktop PC, try one on the back instead of the front - although I think this has been making less and less of a difference in recent years.
Try rebooting the PC/laptop.
Have a spare PC/laptop to try fresh?
roirraW edor ehT said:
Are you able to shut the phone off? If so, shut it off, wait 10 minutes, then try it again.
Follow Google's instructions exactly on the Official Google Pixel Update and Software Repair or Official Google Android Flash Tool web page.
Try another USB port.
Try another USB cable.
If a desktop PC, try one on the back instead of the front - although I think this has been making less and less of a difference in recent years.
Try rebooting the PC/laptop.
Have a spare PC/laptop to try fresh?
Click to expand...
Click to collapse
cant tell if phone is shut off or not, but it is a black screen and have tried power button and vol up and down for 30 sec (but no indication that its force shut off), tried another cable and another laptop and same symptoms.
muzab a said:
cant tell if phone is shut off or not, but it is a black screen and have tried power button and vol up and down for 30 sec (but no indication that its force shut off), tried another cable and another laptop and same symptoms.
Click to expand...
Click to collapse
I think it's time that you need to contact Google, unfortunately. Unless someone else has some better ideas. Sorry to hear.
muzab a said:
cant tell if phone is shut off or not, but it is a black screen and have tried power button and vol up and down for 30 sec (but no indication that its force shut off), tried another cable and another laptop and same symptoms.
Click to expand...
Click to collapse
Try just power button for 30-45 seconds.
Long shot idea here.
Plug the phone into the charger, see if you get a charging symbol (indicating it is off).
If no charging symbol, should indicate device is still on, allow battery to run out. After a day or two, start plugging in the device momentarily to see if charging animation comes up.
Maybe after shutting down/running out of battery, you can recharge and get into bootloader?
Like I said, long shot idea..
Best of luck!
Az Biker said:
If no charging symbol, should indicate device is still on, allow battery to run out. After a day or two, start plugging in the device momentarily to see if charging animation comes up.
Maybe after shutting down/running out of battery, you can recharge and get into bootloader?
Click to expand...
Click to collapse
I agree. I have definitely had to do something similar, I believe with my LG G3 once or twice. Had to turn it off or let it die, then leave it alone for a while. Sounds crazy, but whatever works...
roirraW edor ehT said:
I agree. I have definitely had to do something similar, I believe with my LG G3 once or twice. Had to turn it off or let it die, then leave it alone for a while. Sounds crazy, but whatever works...
Click to expand...
Click to collapse
When they switched to non-removable batteries and you had to let it die instead of simply pulling the battery
Good times
Az Biker said:
Try just power button for 30-45 seconds.
Long shot idea here.
Plug the phone into the charger, see if you get a charging symbol (indicating it is off).
If no charging symbol, should indicate device is still on, allow battery to run out. After a day or two, start plugging in the device momentarily to see if charging animation comes up.
Maybe after shutting down/running out of battery, you can recharge and get into bootloader?
Like I said, long shot idea..
Best of luck!
Click to expand...
Click to collapse
Thanks will try this. I have spoken to google to get a replacement but hopefully i can get this current one working again
This isn't the kind of mis-flash I'd expect a phone to survive. Pixels tend to accept whatever firmware you throw at them with practically zero version or compatibility checks. In your case, going from a Qualcomm to a Samsung bootloader is likely fatal.
I'm surprised it even shows a device. Maybe a rescue path, but I wouldn't even know where to begin with drivers if generics aren't good enough. If you aren't getting a "fastboot devices" response, that's game over. How did you flash this in the first place? How far did it get?
just a heads up, that link under pixel 6 pro Global is still incorrect and is pointing to pixel 5a
LLStarks said:
This isn't the kind of mis-flash I'd expect a phone to survive. Pixels tend to accept whatever firmware you throw at them with practically zero version or compatibility checks. In your case, going from a Qualcomm to a Samsung bootloader is likely fatal.
I'm surprised it even shows a device. Maybe a rescue path, but I wouldn't even know where to begin with drivers if generics aren't good enough. If you aren't getting a "fastboot devices" response, that's game over. How did you flash this in the first place? How far did it get?
Click to expand...
Click to collapse
wasn't familiar with the p6 pro codename so when i used the link under the XDA article i guess i didn't pay attention to the name of the file. Lesson learnt
Reported it and it's fixed now.
@muzab a
Kindly share the hardware ID of the USB Serial Device.
Since the Pixel 6 family's Google Tensor silicon is somewhat based on the Exynos chipset, it could be possible to use the Exynos hard brick recovery method to revive the device (context: 1, 2).
If possible, initiate the replacement process. But discovering a community-supported method for unbricking these devices would be great. For your information, we never got our hands on the low-level firmware packages for the older Pixels with Snapdragon family of SoCs.