yashsingh1/xdaforums huggingface dataset:
[One (M8) Q&A, Help & Troubleshooting] brokenm8:
Yes the current condition happened directly after getting wet.

Mine doesn't go into fastboot by default when booted into bootloader while connected to PC. While at the HBOOT main screen, Fastboot is at the top of the list of options available to select followed by Recovery, Factory Reset, etc... The power button does not activate any of the options in HBOOT but it works just fine to power the phone on or off and in combination with the Vol Up button to boot the OS which always goes into safemode. However, the Vol Down button doesn't work anywhere. This seems to indicate to me that HBOOT and/or the firmware might be corrupted? As I mentioned earlier, I am able to move files around with no problem. Pretty sure I can't put a RUU into the root directory and fix this because I'm unable to relock the bootloader due to fastboot not working right? If so, is there a way to load/flash a good copy of HBOOT and/or firmware to the phone via my sd card?
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
I'd say that is a big leap of logic, and probably not a correct one. Hboot is required for the very basic functioning of the phone. Hboot corruption usually equals hard brick (screen won't even come on).

I'd say it's more likely the water damage caused hardware failure of the vol down button.

You can only flash RUU or firmware with an unlocked bootloader, if the device is s-off.

You also can't flash hboot separately unless you have s-off. You can flash firmware, which contains hboot. But again, unless you have s-off or can relock the bootloader, you can't flash firmware.
[One (M8) Q&A, Help & Troubleshooting] Glasskeramika:
Hi there

I got the same exact problem with my m8. At the screen telling : s-on, locked..., the power button and the vol down button are not working, the vol up button is scrolling down instead of scrolling up. It appears that I am stuck in Hboot only I can't use fastboot or any other option. This is the second time I am facing that problem. The first time, I have replaced the motherboard, but since then I didn't flash any rom or done any mod on my htc and here I am now with the same mess.
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
Did you drop it in water, like the OP?

I would suggest anyone refrain from saying you have the "exact same problem" on this forum. I've seen that phrase (or similar) posted dozens (probably

hundreds

) of times. And not

once

, have I found (after digging for details) that statement to actually be true. Way too many variables in phone versions, software, what was done to it, etc.

Your time is much better spent giving specific details on the phone, and letter us go from there.
[One (M8) Q&A, Help & Troubleshooting] Glasskeramika:
I did not drop in the water.

It went off after battery fully drained. When I tried to turn it on after I plugged it in my computer to charge it, the screen in the attachment showed off. It does show options like fastboot, recovery..etc, but I can't select any of them : the power button (on that screen) doesn't work but it does turn on my phone, the volume down button doesn't work at all (neither on safe mode nor on the attached screen). The vol up button works good when it's running on safe mode, but it plays the role of the vol down button once on that screen (it scrolls down instead of scrolling up).

I need to mention that I had that problem (the same exact haha) two years ago when I rooted my htc m8. Everything was just fine till one day, my phone suddenly started lagging a lot. When I tried to reboot it, that famous screen showed off. I took it to a guy who has replaced the motherboard :crying:. The phone was doing good, I didn't mod anything or rooted it, but it wasn't recognizing the second camera (once on the htc's camera app, it says that my finger is hiding the second camera). But everything was all good for about 1 year, till I got that problem again.

[IMG="Screen"]https://imgur.com/a/yPYZ4rX[/IMG]

---------- Post added at 08:09 AM ---------- Previous post was at 07:54 AM ----------

Link (remove all space, please) to the mentioned screen : https: // imgur. com/a/yPY Z4rX

(The image doesn't appear in the previous post that I couldn't edit, oh yeah spam :rolleyes:)
[Android Head-Units] jorisvervuurt:
I have a PX5 head unit running Android 8.0 Oreo. I’ve already connected a rear view camera that works great, but I’d also like to connect a front view camera. I’ll be connecting the camera to the composite/CVBS AV IN video input.

I don’t expect any problem using it simply as a front view camera by launching the AV IN app to view the video signal, but I was wondering if it is possible to use the same video signal for the DVR dash cam app (I know the quality won’t be all that great, but still)?

Also, the AV cable harness of my head unit includes a red ‘CAM POW’ wire. I haven’t measured yet, but perhaps somebody knows if it gets 12V when the radio is on? Otherwise I’ll have to look for a different 12V source. I’ve already enabled the ‘Front cam’ option in the Factory settings and I’ve set the ‘DVR’ option to ‘USB+CVBS’.
[Android Head-Units] jorisvervuurt:
Nobody? :crying:
[Android Head-Units] vassandrei:
The cam pow wire will output 12v when the F-cam app is open (or when reverse gear is triggered via the reverse wire).

I don’t know of a way to use that video for the DVR app, and moreover the front/rear cameras typically have a voltage converter from 12v to whatever lower voltage the camera itself uses. This is integrated either into the camera or on the wire somewhere and it warms up very quickly. The camera isn’t meant to be on all the time as a result because it overheats and can stop working.

The DVR app is made to receive a signal from a certain type of USB camera only afaik. You can find them on AliExpress too.. then again I gotta check my settings, because I’ve never messed around with it.
[Android Head-Units] jorisvervuurt:
I see, thanks for the detailed reply!

I’ll forget about using this camera as a dash cam. ;)

Do you know if the CAM POW wire also outputs 12V when the AV IN app is open? Or is it just when the F-Cam app is open (and set to the front cam)?
[Android Head-Units] vassandrei:
That's a good question.. I haven't tested. I'll try tomorrow and tell you the result. I'm going to lean towards no though, because otherwise anytime that AV-in would be open my rear/front camera and parking system would turn on, which would be inconvenient if watching some AUX video in source (like a console).
[Android Head-Units] jorisvervuurt:
Awesome, thanks!

Another question...

My head unit only has two (yellow) RCA video inputs.

One is labeled 'CAM VIN', to which my reverse camera is connected.

The other input is labeled 'AUX VIN' (also a yellow RCA).

Is my assumption that F-Cam uses the 'AUX VIN' signal correct (so, the same signal that is shown in the AV IN app)?
[Android Head-Units] vassandrei:
Alright so I tested and the AVIN app has no effect on the CAM-POW pin, because my parking sensors and rear/front cameras definitely don’t turn on when I open the avin app.

Cam-VIN is your reverse camera in most likely. It will show when you give the reverse pin 12v and thereby activate the reverse camera app (or open the f-cam app and switch to rear view mode via the button on the screen).

Aux vin is what the AVIN app shows, and is not tied to any power pin as far as I know.

F-cam in is separate from those two and the connector isn’t always present on all units. You might have the f-cam in pin on a second AV connector that doesn’t have any plugs included for it (for instance on my unit f-cam in is on a small 8 pin connector next to my main av connector which I had to make my own cables for)

Check the front parking camera mod thread on here, I posted pictures of what my Witson unit looks like.
[Android Head-Units] jorisvervuurt:
Thank you so much!

I've checked the other thread and I may be in luck with the 8 pin connector.

Mine's also a Witson unit: http://www.witson.com/en/displayproduct.html?proID=102131570

I don't have a photo of the actual unit in my car, but according to Witson's product photo it does have the 8-pin connector:

I currently have my reverse camera connected to CAM VIN (video signal, yellow RCA) and the +12V to the brown REVERSE wire on the main ISO harness.

That brown REVERSE wire gets +12V when I manually change gear to the reverse gear (otherwise it's at 0V, I've measured it), but clicking the reverse camera button in F-Cam doesn't get me +12V on that wire. :(

If I understand correctly, you have both your front view camera and your reverse camera connected to the red CAM POW wire on the AV-harness?

Does the radio output +12V on the red CAM POW wire when you manually change gear to the reverse gear AND when clicking the reverse camera button in F-Cam?

If so, I'll have to change the wiring.

As for the 8-pin connector: what is it called and where can I order the correct harness?

Thanks again for all the useful info!!!
[Android Head-Units] vassandrei:
The reverse wire is meant to receive 12v+ into the head unit as a signal of you having changed gears. It's typically hooked up to your reverse light (as it turns on when you switch into reverse).

and YES! The CAM POW wire outputs 12v BOTH when in reverse gear (triggered by the reverse signal wire receiving 12v) AND when opening the f-CAM app!! It's actually super cool because not only is it an automatic parking assistance system (for both front and rear) but you can totally check either camera at ANY time, even during driving, or being stuck in traffic. It's quite fun :)

Yes, I currently have both my front and rear camera powered by the CAM POW wire. I did use a relay though, so as not to overload the one pin (because I have a video-based parking sensor system installed on both the front and rear as well).

The 8 pin connector -- I have no idea what it's called. I just dug around through my old head unit connectors from my other car and found one that was the same size but wider. I cut it so that it was 4 pins (instead of something like 16). So, if someone else knows what those types of connectors are called, that would be helpful.
[Android Head-Units] jorisvervuurt:
My head unit has two brown REVERSE wires; one on the main ISO harness and one on the AV harness. The one on the AV harness never outputs +12V, as it is the trigger wire. The REVERSE wire on the main ISO harness however, does output +12V when I manually select reverse gear. This is done through the CANbus system. My reverse camera is not connected to the reverse light wiring. ;)

That sounds great! I’ll be measuring some of these wires soon, as I’m probably going to change the wiring. :) It’ll be particulary useful to read license plates of cars that are ‘bumperklevers’ as we call them in Dutch. :p

Hmm, okay. Will that also be necessary when connecting two simple cameras, of which one has four white LEDs? I guess they won’t use that much power. :confused:

Aha, okay. I’ll ask the seller of my radio. ;)
[Android Head-Units] jorisvervuurt:
[MENTION=6315788]vassandrei[/MENTION] I have just (without taking the radio out of the dashboard) measured the red CAM POW wire on the AV-harness.

Good news! Normally, the wire reads 0V. When I open the F-Cam app - no matter if the front or back camera is selected - it reads +12V. This is also the case when the reverse gear is selected, even when the F-Cam app is not opened. :cool:

Note that all of the above is working without having the reverse trigger wire connected to the reverse light positive; all through the CANbus system.:laugh:

I’m going to change how my reverse camera is connected, as it right now only gets power when I select the reverse gear.
[Android Head-Units] jorisvervuurt:
Bad news! :crying:

I just took my radio out to see if it has the 8-pin connector.

Unfortunately, it doesn’t actually have the connector installed, though it does look like everything on the PCB in place; it’s just the connector that wasn’t soldered on during production (probably to save cost). :(

I could open the unit and manually solder a connector on, but I assume that will void my warranty...
[Android Head-Units] vassandrei:
Awww man that sucks! I would still consider soldering.. the warranty isn’t worth much (huge pain in the butt to send for repairs anyway ). The convenience and novelty are worth it for me :)
[Android Head-Units] jorisvervuurt:
Yeah, I’m definitely considering soldering directly to the board (I’m quite experienced in soldering so that is no problem at all). Instead of ordering through e.g. AliExpress, I ordered the radio through Icebox Auto in the UK, so should I need the warranty, it shouldn’t be a very big problem as I also live in the EU (The Netherlands). ;)

I’ve emailed them to ask about soldering to the board. Preferably, I’d solder the correct female connector to the PCB, but I haven’t found the name of the 8 pin connector so far. :crying:

Here’s a photo of how my radio looks from the back:
[Android Head-Units] vassandrei:
Yeah the one to the left of the circle hole is it. I can even see the bits of solder on the pads! I would solder a wire directly to the board, not bothering with connectors
[Android Head-Units] jorisvervuurt:
Yep, it really looks like they just saved on production costs and figured we wouldn’t need the connector. Soldering wires would work too, though I prefer the connectors to be as they would be from the factory. :) I’ve been looking around the internet and it looks like it’s a 2x4p PHB wire-to-board connector with 2.0mm spacing. Not entirely sure though, but they look identical...

Will keep this thread updated once I hear from Rob at Icebox Auto. :good:

By the way, which pins are needed for the F-CAM RCA-in? I assume ground and signal, but which ones are they on the 8-pin connector? :)
[Android Head-Units] vassandrei:
This is the way I have it on mine:
[Android Head-Units] jorisvervuurt:
Awesome, thanks for the clear picture!
[Android Head-Units] jorisvervuurt:
Today I went ahead and took out the radio (again); this time including the wiring...

I've rewired the rear view camera, so that I can enable it even while driving forward. :D

I've modified the AV-harness so that I have two +12V wires (with bullet connectors) coming from the CAM-POW wire. See attached photo.

Almost all preparations for a future front-view camera are finished. Modifying the radio's PCB is the only thing left to do, but I'm gonna wait for Icebox Auto's response regarding the warranty.

It's kind of funny to enable the rear view camera while driving forward. :silly:
[Android Head-Units] jorisvervuurt:
[MENTION=6315788]vassandrei[/MENTION] An additional question regarding the CAM-POW wire:

Do you know how much current (mA) the CAM-POW wire can provide?

As you can see in my previous post, I’d like to connect two cameras to the CAM-POW wire. One of those cameras has 4 white LEDs built-in. How does a relay setup look and when is it needed? Or will two cameras work just fine?
[ZTE Axon 7 Questions & Answers] Waancho:
Hey,

I have axon 7 U model.

I have AEX 5.5 installed.

I installed Nfound's twrp 3.2.1.7.

Then I used the 'remove inscription' tool from his twrp.

Then I shut down.

But now I can not power up again.

Only when I long press power I get a short vibrate and short light flash.

What can I do?
[ZTE Axon 7 Questions & Answers] Choose an username...:
You shouldn't have, because that was only for the G model.

There's a guide in Russian, just use the translator

https://4pda.ru/forum/index.php?s=&showtopic=814221&view=findpost&p=73877855
[ZTE Axon 7 Questions & Answers] Waancho:
Thank you!

Should I only flash a full EDL image and that's it?
[ZTE Axon 7 Questions & Answers] Choose an username...:
I didn't even read that guide but yeah, that'll work

I asked NFound if he would add a disclaimer for the del inscription button and he basically told me to f00k off and gave me that link
[ZTE Axon 7 Questions & Answers] Waancho:
Thanks for pointing me the way m8, i managed to fix it!
[OnePlus 6 Guides, News, & Discussion] xdaman85:
In this video I test out both dash charging on the Oneplus 6, and adaptive faster charging on the Samsung Galaxy Note 8 to see which one is faster.

Both devices have a 3300mah battery.

mod edit - link removed

:D
[OnePlus 6 Guides, News, & Discussion] zige:
And i can say without watching and without click-baiting that dash charger is much faster! You can calculate it for yourself too. Samsung adaptive fast charging is based old Qualcomm Quick Charge 2.0 and output power is ~15W. Dash charger is 20W.

But nice video still! ;)
[OnePlus 6 Guides, News, & Discussion] intruda119:
Does it really matter?
[OnePlus 6 Guides, News, & Discussion] Manivannan9444:
Yea everyone will just try to find a way or to prove that the phone they bought is best so they do useless comparison all going to change phone within a year it doeent matter stop speaking for thr company just use the phone no offence for the post:)
[OnePlus 6 Guides, News, & Discussion] rav101:
I've not watched the video but something else to consider.

Dash charge does hot heat up the phone whilst charging. As such, it's not only quicker but it also does it in a way that is better for battery longevity.

You can use this charging solution whilst driving in the car with GPS and Bluetooth for example without hearing issues which you really can't do on Samsung adaptive charge or other battery charging technologies.
[OnePlus 6 Guides, News, & Discussion] intruda119:
My phone gets warm/hot aka nothing alarming. But the same way op6 charges with dash is no different than the note 8 I used for 6+ months.

It's quicker but not night and day. It's not 2013 anymore. Fast charger with my mate 8/9 was just as fast and battery lasted just as long with all the bells and whistles.

But I personally don't live in a 3rd world country where chargers/outlets arent available.

I thought it was the company I avoided but the community (mostly op forums) are reaching for anything. Battery life and maybe dev community are the only positives.

Never personally had a issue with any other battery technologies.
[Moto Z2 Force  Questions & Answers] neonblur:
Hello! I have a TMO stock unrooted phone and purchased a micro sd 64G. I have done some digging but am coming up with nothing. Are we not able to format as internal OR move apps to SD?? The official online help manual for phone clearly shows that I should be able to format as internal but I do not have that option. I have also ticked the option in dev options to force allow apps to be written to SD but it made no difference. Am I missing something? Any input would be appreciated

**nevermind looks like it is basically unsupported now, don't know why they left the option in dev opts tho**
[Moto Z2 Force  Questions & Answers] propov:
I think that Android Oreo is the answer. In Oreo on default app to SD is imposible. Probably you read manual for Z2 with Android N..In N this was posible.
[Upgrading, Modifying and Unlocking] SubwayChamp:
I´m not familiar with this device.

There is a method to root newer devices through Magisk letting it to patch the boot and then flashing it onto your device but if you don´t unlock before bootloader then you have some risky that it gets in bootloop.

There are two commands that you can try to unlock that I didn´t see before in your attempts (at a quick glance), try with:

Before go further is mandatory to type fastboot devices to see your device, then....

The most commom: fastboot oem unlock

or maybe can work: fastboot flashing get_unlock_ability

If there is some twrp in the market there´ll other methods.
[Upgrading, Modifying and Unlocking] summersolstice:
Hi SubwayChamp, Thank you for your reply.

I tried the commands you listed and unfortunately neither work.

Here is what I used.

#1 adb reboot bootloader (device rebooted with black screen writing "fastboot downloading...."

#2 fastboot devices (shows me my device)

#3 fastboot oem unlock

FAILED (remote: unknown command)

finished. total time: 0.003s

#3 fastboot flashing get_unlock_ability

FAILED (remote: unknown command)

finished. total time: 0.003s

I looked for magisk method too, but there isn't a magisk version for this device and I don't have boot.img, its not listed anywhere online.

Two weeks ago I wrote an email to manufacturer in 3 countries asking for root instructions and original rom. none replied back. :(
[Upgrading, Modifying and Unlocking] SubwayChamp:
Usually Magisk can patch almost any boot but the problem here is that there is not firmware available for your device to get the boot and you can't dump it without root.

Maybe you can find the way executing fastboot like admin or changing for other version of fastboot.

Just for sure check if you didn't type before fastboot oem unlock bootloader cause I saw this, the word bootloader here is not needed
[Upgrading, Modifying and Unlocking] summersolstice:
I typed just this fastboot oem unlock

What version of bootloader is this?

C:\WINDOWS\system32>adb bugreport | find "bootloader"
<6>[ 0.821835] mdss_mdp_probe: mdss version = 0x100e0000, bootloader display is on, num 1, intf_sel=0x00000100
[ro.bootloader]: [unknown]
[Upgrading, Modifying and Unlocking] summersolstice:
After more searching I found out this is some type of hisense device hs8937QC (qualcomm).

There are few devices listed here with the same CPU: https://www.devicespecifications.com/en/model-cpu/bad84051

I tried installing adb drivers from here https://freeandroidroot.com/download-hisense-usb-drivers/, but they are old from 2014.

Maybe too old and incompatible?
[Upgrading, Modifying and Unlocking] SubwayChamp:
The trick is in the fastboot drivers, find and try other version/s of fastboot, many users refers ever this trouble, some works better than other. Change too of port connection.

Put your adb folder in main drive.

But I hope that this is not the cause although there are some bootloader that are not unlockeable. to see an example, I guess this is not the case but the newer One Plus are unlockeable only phisically.

Other info; I had in the past an mtk device that allows to flash supersu.zip through update feature using recovery stock, you can try it but I can´t predict what mighjt happen in this case.
[Upgrading, Modifying and Unlocking] summersolstice:
Hi!

Finally have the boot image but it is in the boot.img.p format and magisk tells me it is unable to unpack boot.img.p

I searched on forum and didn't find useful info. Only very old posts from 2011.

Am I supposed to modify/patch this boot.img.p somehow?

Uploaded two versions of boot.img.p file

version 1 is 600MB+ update from January 2018

version 2 is 55MB update from April 2018

Download link to boot.img.p

https://www.dropbox.com/sh/cmmie129b86xqlj/AACd4wAGITlJ-mJ9rKmnk_79a?dl=0
[Upgrading, Modifying and Unlocking] SubwayChamp:
Extract boot.img that is inside using 7zip and try it again but I´m not sure if Magisk can deal with this kind of boot that you will find into the compressed format .p

If Magisk is capable to act like a linux machine or a good hex editor to unpack the header of this "cheap" structure use the file that you called 600MB cause the first plain won´t work.
[Upgrading, Modifying and Unlocking] DnCkY:
Hi,

Someone managed to root this device?
[Upgrading, Modifying and Unlocking] LdotQ:
Did anybody manage to find a stock firmware for this device mine is in live demo unit mode
[Upgrading, Modifying and Unlocking] npinho:
I have 2 old LDU (live demo unit) retired from a store, if anyone has a way to unlock the phone to use ... I would appreciate it!

Action-X3 and Core-X3
[Upgrading, Modifying and Unlocking] vkoniv:
hi, has anyone finally managed to root this mobile (action x3) ??
[Upgrading, Modifying and Unlocking] freechelmi:
I will get an X3 to try next week

Crosscall has answered my that series 5 can be unlocked without saying how :-)
[Upgrading, Modifying and Unlocking] Dcosmos:
I have an core X3 already to try something.