yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] Sztarkel:
Hello.

I'm a new owner of android, chinese brand, double din head unit and I already regret I didn't know this part of forum before purchase, but let's move forward.

Here's a photo of "about my device":

[IMG="About my device"]https://i.ibb.co/Y7GzSQk/IMG-20190408-094640.jpg[/IMG]

So here's my problem: The device doesn't shut down/turn on with the ACC as it should. When I was wiring this unit I made everything with connection blocks so I can easily switch the connections before soldering. I did yellow to yellow as 12V constant, and red to red wire as ACC (it was described the same in my car as in the android unit). After connecting it this way I've seen that the unit doesn't turn on/off with ACC - so the first thing I did is I swapped yellow and red - Yeah! this is it! The unit started turning on and off with the ACC correctly so I was happy. When driving with the unit connected this way I started noticing weird things - on loading screen the unit was always playing radio at 87,5 kHz which is white noise, also the EQ was flat every on/off. I asked the seller and he said this is the problem with memory caused by wrong connection. That's the time when I got my multimeter and re-checked everything. The resault was that my first connection was correct, and right now I had swapped 12V constant with ACC wire. I re-soldered everything to the first way, with yellow to yellow and red to red and the problem with not turning on/off came back, but memory problem is now gone. The unit at loading plays my last played station and the EQ is always set up like i like it. Of coarse i contacted the seller again (it's JUNSUN btw), they still think it is wiring problem - so maybe you guys will help me.

The seller asked me about videos, so here they are:

https://youtu.be/yN690qvpzHY - here's red to ACC pin at the radio and black to GND, you can see how the volts are changing.

https://youtu.be/zH1wrjoabng - this is first turn on after plugging in. It's turning on automatically, but every other turn of key doesn't work

https://youtu.be/qPVej4Us_xM - some basic functioning of the unit. Like not turning manually ON without ACC ON (so.. the unit knows that ACC isn't on)

My next question is - can I do "factory reset" without losing the preinstalled apps? Is this reset going to recover the state of first-turn on by me or to clean android?

Sorry for whole story, most of it was probably unnecessary, but I felt like sharing it with you. Hope you don't mind!

Edit: Should i maybe post it in "Android head units"?
[Android Head-Units] Sevennl:
Also the Brand and type of car is important.

As my guess is you have a canbus car system, if so, connect the red wire to the positive (middle) of your cigarette lighter.
[Android Head-Units] Sztarkel:
I forgot to mention! It's 2006 Hyundai Sonata without canbus. The red wire acc works as it should (tested with voltmeter). The unit "knows" that ACC is off as it cant be turned on by holding the volume knob without key at ACC position. I must put the key to ACC position and then turn the radio on by holding the volume key.

It's weird and it seems like software problem to me. Should I maybe start with factory reset?

Oh and I have "shutdown delay" set to "no delay".
[Android Head-Units] Sztarkel:
Maybe I should try rooting the device or updating firmware?

Sorry for double post.
[Google Pixel 3 XL Questions & Answers] Sepkov:
Hi I was trying to enable qualcomm diag mode in my pixel 3 xl. I was able to do it on my old pixel 1 phone with flashing Google's vendor images. It was enabling debug mode. But when I try to do the same thing on my pixel 3 xl, I always get "Your device is corrupted" screen and phone is stuck at boot. I tried both first and last firmwares with first and last vendor binaries. I'm using generic "fastboot flash vendor vendor.img" command. This only happens with external vendor images. When I try original vendor.img phone works. But external, no luck. Any help is welcome. If wanted I can supply more info.

BTW cause of my struggling is when I was messing with custom roms I deleted my original IMEI number. Now I want it back.
[Google Pixel 3 XL Questions & Answers] SacredDeviL666:
when say original vendor.img and external vendor.img what does it mean ? external vendor images which is modified by an user? sorry for my noobish question just curios ...

you can download the latest factory image for pixel 3xl april build, extract the zip edit the flash.all bat file to remove -w which will get your phone back to original state without wiping your internal data/storage files.

you can alternatively try flashing the vendor image through fastboot to both slots using command and see if it helps either. not sure if IMEI loss will stop this process from happening.

fastboot flash vendor_a vendor.img

fastboot flash vendor_b vendor.img
[Google Pixel 3 XL Questions & Answers] Sepkov:
Hello sir. Thanks for your answer.

When I mean original vendor image, I mean the one inside in the factory image.

When I mean external vendor image, I mean the one google provides apart from factory image located in here:

https://developers.google.com/android/images#crosshatch

I'm pretty sure I'm using the one has same software version.

Sorry for my english, I'm not a native english speaker. So in order to give this topic a little clarity I'm going to type the steps I'm following with the device behaviour, hope it helps.

Steps:

1 - Downloading latest factory image (version: PQ2A.190405.003) and flashing to device with ./flash-all.sh >> device is rebooting and starting just fine

2 - Downloading external vendor image google provides from the link I mentioned above and flashing with

"fastboot flash vendor_a vendor.img && fastboot flash vendor_b vendor.img" >> Device says it's corrupted and not booting stuck at splash.

Also just "fastboot flash vendor vendor.img" >> Just same doesn't turn on stuck at splash.

I'm probably missing something because I was able to do this in my pixel 1 device.

The whole thing I'm trying to do is to recovery my imei with qpst firmware. To do this I need diag mode.

With my regards.
[Google Pixel 3 XL Questions & Answers] SacredDeviL666:
All good as long as we understand each other that serves the purpose of a language :good:

This is strange as both should have same vendor.img from the full factory image. This is the factory image which you have downloaded and said to be flashing fine.

Could you please link me the exact vendor.img link you are downloading from ? why are you flashing vendor image again if the factory images already flashes them. or why not extract it from the existing the factory image which is getting flashed successfully.

Is this the reason you need to flash vendor.img again even after the factory image i linked above flashes those.
[Google Pixel 3 XL Questions & Answers] Sepkov:
Hello sir. Thanks for your reply.

On factory images google provides only release vendor image, which has necessary debugging features disabled. But the one from the link I provided has debugging features enabled. I can see the necessary lines in that external vendor image. But not on the one inside the factory zip. Here is the link of vendor image I downloaded:

https://dl.google.com/dl/android/aosp/google_devices-crosshatch-pq2a.190405.003-86ca23db.tgz

You may need a linux like shell in order to use the file provided from google.
[Google Pixel 3 XL Questions & Answers] SacredDeviL666:
I am at a loss when it comes to Linux sorry for that :( can you replace this vendor image you mentioned above to the vendor in factory image you have downloaded and see if it gets flashed fine along with the factory image?

The only reason i could think of is the vendor files aren't matching the requirement an thus giving image corrupt error.

Sorry couldn't be of much help if the above doesn't help then i would suggest to wait for opinions from experts around.

I could request [MENTION=3690061]karandpr[/MENTION] to check and verify if the vendors are matching from both source or probably help you troubleshoot you further.

[MENTION=1566190]efrant[/MENTION] has got pixel 3 maybe he could if not karan...
[Google Pixel 3 XL Questions & Answers] wangdaning:
The file you linked is just the script to pull the vendor blobs from the phone, it is not a vendor.img
[Google Pixel 3 XL Questions & Answers] dd805bb:
Imei should can back once you connect to WiFi or insert a Sim. It will not because if you use an esim you get a different imei. If you use a regular aim you get the imei in phone.

And don't flash generic anything. Maybe a gsi but vendor & radio you keep the same. Boot can be patched and do whatever. In no way even with a gsi do you ever flash custom vendor images. Most custom ROMs if not all want you to have the latest vendor and radio images. Those tell the rom what it is working with. No way is anything to do with that is generic.
[Google Pixel 3 XL Questions & Answers] Sepkov:
No sir you are wrong it's a bash script designed to work with Macos and Linux. Even in Windows subsystem for Linux.
[Google Pixel 3 XL Questions & Answers] Sepkov:
But the file I'm trying to flash is provided by Google for my software. What's wrong with that?
[Google Pixel 3 XL Questions & Answers] Sepkov:
Just to give this topic a little clarity I'm basicly trying to do this:

https://xdaforums.com/showpost.php?p=77262880&postcount=54

It was working on pixel 1 as I mentioned but not on pixel 3 xl.

WHYY
[Google Pixel 3 XL Questions & Answers] Homeboy76:
[MENTION=5270407]Sepkov[/MENTION] [MENTION=4521676]Xdevillived666[/MENTION]

I don't think this works on the Pixel 3/Pixel 3XL. At least not fully, according to these post:

QPST ports open on pixel 3 by Xdevillived666

Update:QXDM Pixel 3 limited success (help) by Xdevillived666

¯\_(ツ)_/¯
[Google Pixel 3 XL Questions & Answers] wangdaning:
I don't think he meant he was flashing the pixel vendor, he meant he was using that process with the pixel 3 downloads.
[Google Pixel 3 XL Questions & Answers] Sepkov:
Exactly I was mentioning this
[Google Pixel 3 XL Questions & Answers] dd805bb:
Those are not generic images you are linking. Those device specific images. Dev images which I would not be messing with unless you know what you are doing. And from the sound of it, no one in here should be screwing with those. I took two minutes to look at this and laugh. One. No such thing as a generic vendor image. There are Dev Google device specific vendor images that render your phone useless except talking to your computer. If that is ok with you and the goal, go for it. But this post is about files that don't exist trying to make work. And from what Google puts out, you flashed it right, and is working right if you got it to boot. User would not see a difference except not being able to do anything except USB dialogue to your computer. So what is the point? Dev? Hell if you can t even flash a simple device specific file, you shouldn't be doing Dev work.

---------- Post added at 02:37 PM ---------- Previous post was at 02:23 PM ----------

Also after reading, these will not work with the stock rom. You need a custom rom these binaries from Google. The factory image doesn't mix with these images. The factory images contain the vendor image. From the quick run down Google actually gives, these are not meant to mix with the factory rom. These are meant outside of the factory rom getting asop custom ROMs going. Gsi and such.
[Google Pixel 3 XL Questions & Answers] Sepkov:
Deleted
[Google Pixel 3 XL Questions & Answers] dd805bb:
https://developers.google.com/android/drivers
[Google Pixel 3 XL Questions & Answers] Sepkov:
Hello. Thanks for your answer.

So I need an aosp rom in order to use these "debug enabled vendor" images. Is that correct? If so I still don't understand why it was working well with the pixel 1.

Google must have done something different. Thanks sir I will look on to it.
[Google Pixel 3 XL Questions & Answers] dd805bb:
It is not they won't work. You for one are not going to Google or those other posts. The pixel XL and pixel 3 xl are not the same phones. I have both actually. One rooted on Q and on not rooted on Q. Pixel 3 xl no root. These images you speak of are for custom ROMs. Go read the link I provided. Asop ROMs to be exact. These are for people that build ROMs. To get the binaries to communicate with their ROMs. Vendor GPS to be exact. A factory rom has these are ready. Why are you mixing custom and factory images. They don't work together.
[Google Pixel 3 XL Questions & Answers] Sepkov:
The reason I'm trying to flash Google supplied vendor.img is that I'm trying to restore my imei using qpst software. I was able to do this with flashing Google provided vendor.img that has same build number as the pixel has. In that phone(pixel 1) I was able to type "setprop sys.usb.config diag,adb,mtp" (ofc after rooting) and after that I could see my phone in qpst software. I want to mention here I was not using any different rom than Google factory rom. It was working flawlessly. On pixel 3 xl I was trying to do the same steps with latest pixel 3 xl factory image and corresponding vendor.img. But I am not able to succeed. I will compile aosp for myself because I was not able find a aosp rom build ready. Then look for enabling diag mode. Thanks for your reply, I was missing aosp part in drivers section.
[Google Pixel 3 XL Questions & Answers] dd805bb:
Also one of the links to the other thread, guy said he compiled the vendor image to work with the factory rom. The said they took the binary and applied it to their custom rom. What is the point here?

---------- Post added at 03:03 PM ---------- Previous post was at 03:01 PM ----------

That will not restore your imei. You either need to wipe your m drive and connect to WiFi or pop in a Sim. Imei don't show unless you have a Sim in or have your esim active. Imei can change. It is the phone imei stored for the phone if you use a physical nano SIM. If you use the esim inside it gains the imei from the carrier it linked to.
[Google Pixel 3 XL Questions & Answers] Sepkov:
Actually as I mentioned before my main language is not Turkish. If I got your first sentence sorry for that. I don't know any answer to that the thing I'm sure it was working on pixel 1.

Before flashing latest factory rom my imei was starting with 99 and now it's 004400152020002. I can type it here because if you search this imei on google you can see a lot of person see this imei when they lost their imei.

I'm trying to insert my sim now.

I inserted my sim card. No signal. IMEI still same 004400.

Factory resetted phone. Still same no signal no IMEI.
[Google Pixel 3 XL Questions & Answers] dd805bb:
The basic imei will be the same. The last digits and /number will change. So say you kick a phone on and have not connected to a carrier. It will not show. Best thing to do, this will get your mdrive to reset but will wipe the phone. Go into factory recovery, data wipe , watch it and mkae sure it says it is wiping the m drive. That stores the inform for carrier, imei, iccid, uid. Boot it. Connect to a WiFi. It will ask for a Sim or enter a carrier for esim. Do either. You have to do one for it to show sometimes. On a fresh start with no carrier information in the phone it may or may not show the imei. I know mine I had to pop in a Sim for it to show anything. I use an esim now. No need for physical Sims. TMobile, Sprint, Verizon or any carrier that uses an iPhone can do it. When I had a physical Sim my imei didn't have the extra slash and numbers. That is why I said it could change. Different carrier have different lengths of number. Sprint runs a few extra digits. Google fi I use the esim. It has more numbers than the imei on my box. I know I had my imei disappear and got it back by wiping and connecting back to my carrier.
[Google Pixel 3 XL Questions & Answers] Sepkov:
Okay sir I'm trying now.
[Google Pixel 3 XL Questions & Answers] Sepkov:
Sir I realized something, on fastboot when I choose BarCode I can see my original imei. But it's having a problem with connection to gsm network. I'm in Turkey btw. I can't wipe modem related files, can I? If so factory image is reflashing it. Am I wrong?
[Google Pixel 3 XL Questions & Answers] dd805bb:
Oh yeah, you are just having a rom problem. If fastboot shows your imei, something is up with the rom. System isn't seeing it. Try resetting in factory recovery. If that doesn't work yes reflash the factory images. You are in the good with that imei shows in barcode. You didn't mess it up that bad. These phones are finicky when flashing. Sometimes you have to do it twice. If get the ota you can adb sideload to the other slot, get it boot in the other slot and flash the factory image to the other slot. Sometimes they do weird stuff not having both slots the same.
[Google Pixel 3 XL Questions & Answers] Xdevillived666:
They do work with stock as I did it with my original pixel. However, usb diag has been removed as of pixel 2 in Dev images(vendor).

---------- Post added at 08:16 PM ---------- Previous post was at 08:14 PM ----------

You should have backed up rom first, and second, you should only be flashing images that correspond to your device . Sucks but that's the truth.
[Google Pixel 3 XL Questions & Answers] dd805bb:
Pixel XL is way different. Pixel 2 had it removed. Pixel 3 xl indefinitely has no support then for usb dialog. The pixel XL is pretty open when it comes to Dev. I think Google learned a lot since then. Q is proof. So many storage and security changes now. I have root on my Marlin and my crosshatch doesn't. Logical partitions. And from launch they have been this way, just now it is getting implemented since Q.
[Google Pixel 3 XL Questions & Answers] Xdevillived666:
That is correct. Pixel 3 is locked down tight.
[Google Pixel 3 XL Questions & Answers] dd805bb:
Any devices now launched with pie and from now will be that way. Samsung and maybe a few other oems won't adopt it because they just don't. But most will be locked down tight. It is good and bad. One good thing it leaning more towards being a real desktop, which means terminal and root are not that far away, as it being like a desktop root and just enter a command via terminal. First Google will block root apps,( pixel XL on Q can block background even if rooted). On pie I would get gpay working then a few reboots later nope. Had a major issue that the phone wouldn't boot after just charging and off. Said avbverifybooterror. In other words they checked the phone and flipped the switch that says my a/b boot isn't the same. They are starting to detect magisk and all root apps again. In the past two weeks it has happened twoce, once with all a lot of mods, second time I only themed stuff via substratum and got no boot and that error trying to boot twrp via fastboot. They are getting smarter.
[OnePlus 3T Questions & Answers] simbapk:
Hello every one,

Hope every body fine and shine.. :)

My first post here jn XDA forum,

I have problem with my oneplus 3t..

Not booting up,

Blinking and vibrating in logo,

Can go to fast mood but not in recovery,

Install 2 times ROM with MSM tool

But problem still same

Please help..

Thanks in advance.
[OnePlus 3T Questions & Answers] Droidriven:
Open a terminal on PC then boot to fastboot mode, connect your device then type this command:

fastboot devices (press enter)

If that commands returns a serial number then you're connected.

Now type this command:

fastboot erase cache (press enter)

Now, reboot your device.
[OnePlus 3T Questions & Answers] simbapk:
Thanks for replying dear,

I tried all these things

Message came as

Partitions erase is not allowed..

Even I tried to install twrp recovery but not allowed.
[OnePlus 3T Questions & Answers] Droidriven:
You probably need to unlock the bootloader to get fastboot commands to work.
[OnePlus 3T Questions & Answers] simbapk:
I entered command,

fastboot oem unlock

But error message partitions not allowed.
[Samsung Galaxy S8 Questions and Answers] choy188:
Hey guys I was wondering if anyone had a ROM to get an S8 Active (G892A) to pie? Thanks in advance.
[Samsung Galaxy S8 Questions and Answers] TheMadScientist:
Nope wait for the update
[Samsung Galaxy S8 Questions and Answers] chutun:
att pie

https://yadi.sk/d/LoSvL86_HFKyEw
[Windows 10 Mobile] wkfy:
Hello!

My Lumia 640XL (OS build 10.0.15063.1689) can't install the latest update (2019-04 1703). I get the error code 0x8024001e and the message that there's not enough free space.

I uninstalled my apps and tried again but the same happens.

I have 3.5GB free of internal memory and 7GB on the SD-Card (all my pictures, music, videos and downloads are saved on it).

Never had problems updating before... :confused:
[Moto X4 Questions & Answers] camil2003:
Hello I recently bought a brand new in box Moto x4 Android one I think and when I got the phone it lasted two days before it went full black, wouldn't cut on, wouldn't light on the charger and acted pretty much dead.

The first time it happened after I unlocked the bootloader, wiped my phone and installed lineage on and TWRP on it from a cmd booted up TWRP.

I got a replacement phone and this one didn't last a night as I tried to do the same thing but I payed attention and noticed the screen darkening as I unlocked the bootloader as a sign of things to come but the same thing happened after I installed lineage and tried to reboot.

I sent the phone back again today and wanted to ask experts here if I might have done anything wrong as I followed instructions from the lineage website and bootloader unlock instructions from Motorola.

This also isn't my first time rooting or installing custom order as I have a 3 year old Moto g4 play rooted with lineage os that's been rough but has been good to me but it's showing it's age(Sim slot went out, speaker messed up, weak antenna).
[Mogul, XV6800 ROM Development] xhorntail:
I installed the GPS/REV A Rom, everything worked as advertised! After restoring a backup from before the ROM update, to get all my stuff back, the volume and GPS didn't work. I managed to locate the volume problem file as audio.fl I think.. Anyway, if anyone knows what registry settings or files that might be changed that would disable GPS, much appreciated!

I have toggled the Emergency Location setting on and off to see if that would fix it, but to no avail.
[Mogul, XV6800 ROM Development] friguy33:
here ya go....

http://forum.ppcgeeks.com/showthread.php?t=25662
[Mogul, XV6800 ROM Development] Keystone:
Whenever restoring a backup of an older ROM onto a

different

ROM will present problems. Solution? Do not do it. Restore your files & contacts, but when upgrading your phone be prepared to reinstall your software.

You did not mention how your did a backup or restore. Sprite backup will recognise that the ROM has changed before you restore and provide a warning and options for a restore. Even by selecting an its OS or ROM restore, you will still not achieve perfection.
[Mogul, XV6800 ROM Development] xhorntail:
I got it resolved. I was using Sprite Backup, usind restore level 1. For reference though, here was my solution:

Hard reset and create a backup. Run the older backup. Now run the backup you just made and install the GPS, COM, and Drivers registry. Works flawlessly. No othe problems noted yet, however I haven't found out how to check if REV A is working.
[Samsung Galaxy A50 Questions & Answers] Brajabandhu:
Iam recently buy Samsung Galaxy a50 it's a great device for me and Samsung doing a great job with Samsung Galaxy a50 iam downloade some Google camera it's work but portrait night sight no developers are working on it why other devices like xiaomi redmi note7 pro their are developers are working but not in Samsung why the Samsung Galaxy a50 have camera 2api out of this box but their are no Google camera apk for Samsung Galaxy a50 pls do something their is many Samsung Galaxy a50 user wants to install Google camera apk for their devices pls help