yashsingh1/xdaforums huggingface dataset:
[Honor 8 Questions & Answers] hassanjavaid8181:
God to has you solved your issue.. Enjoy.:good:
[Honor 8 Questions & Answers] Rayan19997:
You can find it in settings, in device informations, at the end of the build number (ex:B394)
[Honor 8 Questions & Answers] PalakMi:
Can you explain more?!
[Honor 8 Questions & Answers] Rayan19997:
Settings>about phone>Build Number

It may change on your phone because I'm running a custom ROM
[Honor 8 Questions & Answers] PalakMi:
Ah, got it
[Google Pixel 2 XL Questions & Answers] thegios:
If I search an image from Chrome, when I save it locally it's stored into download folder.

What about from search box? It stores the image in a "/document/XYZ" location I cannot find, and as a matter of fact images saved this way don't even appear in Google Photos.
[Google Pixel 2 XL Questions & Answers] thegios:
Anyone?
[Google Pixel 2 XL Questions & Answers] NIKEstickER:
Same issue. Had that issue with my htc 10 that was rooted and unlock bl and couldn't find it anywhere, although in g photos it says the location is in "/document/500" . Now with a stock pixel 2 xl same issue. Can't remember if it was an issue with nougat or not. Doesn't even give you an option to upload to photos while viewing. Very annoying.
[Google Pixel 2 XL Questions & Answers] Bwyan Benton:
Yeah, there's no fix that I know of, but if you go into downloads icon from the app drawer everything appears there. Then you can move it and it will show everywhere. Very annoying actually.
[Google Pixel 2 Guides, News, & Discussion] krelvinaz:
According to Google's bulletin page, the firmware images won't be available until tomorrow (December 5th). OTA updates usually roll out after the images are posted, so tomorrow will probably be our first chance to get a look at the new builds. There will be two patch levels this month: 12-1 and 12-5. The Nexus/Pixel builds should all be 12-5.*

- from http://www.androidpolice.com/2017/1...system-updates-go-live-tomorrow-december-5th/
[Google Pixel 2 Guides, News, & Discussion] jayochs:
hope they don't mess up battery life anymore like the November patch did...
[Google Pixel 2 Guides, News, & Discussion] Large Hadron:
November patch had no effect on my battery life. I don't know what fraction of devices were affected, but it certainly wasn't universal.
[Google Pixel 2 Guides, News, & Discussion] cosmin_tocaciu:
It seems like the stable version of 8.1 is rolling out today according to android authority, sorry can't post the link just yet.
[Google Pixel 2 Guides, News, & Discussion] iron.maaasel:
https://www.androidauthority.com/android-8-1-oreo-stable-final-release-820097/ there it is...

Gesendet von meinem Pixel 2 mit Tapatalk
[Google Pixel 2 Guides, News, & Discussion] heiserhorn:
Anyone on the beta program got the update?
[Google Pixel 2 Guides, News, & Discussion] mikeyinid:
It's not rolling out just yet. The factory images will probably be posted some time today or tomorrow, the OTA's will start going out a day or two later.

---------- Post added at 11:13 AM ---------- Previous post was at 10:31 AM ----------

Factory images and OTA zips are up!

https://developers.google.com/android/ota

---------- Post added at 11:19 AM ---------- Previous post was at 11:13 AM ----------

Lame, I'm on DP2 and the update fails because it's older than DP2...
[Google Pixel 2 Guides, News, & Discussion] heiserhorn:
You sideloaded?
[Google Pixel 2 Guides, News, & Discussion] mikeyinid:
Yes, it failed. I had to opt out of the beta and go back to 8.0.0

Not a big deal for me, it only takes me 10 minutes to set my phone back up. I'm just curious if people on the beta will even get the OTA since the updater sees the 8.1 final as being older.
[Google Pixel 2 Guides, News, & Discussion] thesebastian:
Maybe we 8.1 DP2 will jump to 8.1 January Patch directly.

But generally Google takes 0-2 weeks to start moving people from Beta to Stable. So It would be extraordinary and update in 4 weeks.
[Google Pixel 2 Guides, News, & Discussion] MaxNXS:
Trying to sideload 8.1 from the .25 build and I get stuck at "Verifying package"
[Google Pixel 2 Guides, News, & Discussion] krelvinaz:
It's not Jan, why would they have a January patch before Jan. The Pixel 2 arrived brand new with Sep 2017 but didn't get an Oct patch, The first security update for it was Nov.

I suspect that some might just get the 8.1 upgrade with the Dec 2017 patch included instead of just the Dec 2017 patch.
[Google Pixel 2 Guides, News, & Discussion] mikeyinid:
The Dec 2017 patch is 8.1
[Google Pixel 2 Guides, News, & Discussion] thesebastian:
I was talking about the OTA from 8.1 DP2 to 8.1 non Beta.

If the 8.1 DP2 is newer than the just released 8.1, then the 8.1 DP2 will upgrade to another version. (Maybe in January, maybe before January).

This wouldn't be the first time Google push the ota from Beta to Stable in a delayer manner
[Google Pixel 2 Guides, News, & Discussion] seos83:
I have the same issue. Anyone have a solution for this?
[Google Pixel 2 Guides, News, & Discussion] Stretlow:
I had to relock my bootloader before it would sideload.

All updated fine after that
[Google Pixel 2 Guides, News, & Discussion] 760hacker:
Was this convo stemmed from the fact that you are enrolled in the beta and haven't seen the 8.1 final OTA yet? That is the case with me....
[Google Pixel 2 Guides, News, & Discussion] clcdev:
Are you rooted? I re-flashed the stock kernel/dtbo from November before sideloading the ota and had no issues
[Google Pixel 2 Guides, News, & Discussion] Matterhorn:
I was running DP2 and just got the official 8.1 OTA update. It was only about 45 megabytes, so they didn't change much.
[Google Pixel 2 Guides, News, & Discussion] mikeyinid:
Do you still get the beta popup when your phone boots?
[Sony Xperia XZ Premium Questions & Answers] TheKorbenDallas:
So, what is the situation with Galileo support? I see that Sony's official forum states that XZ Premium will not support Galileo in "US territory". But it is still unclear what they mean:

no support for Galileo in US-specific firmware (similar to fingerprint sensor), or

automatic disabling of Galileo support at firmware level once the phone "realizes" that it is being used in USA (regardless of firmware version)?

Which one is that?

And if international (non-US) models are supposed to see Galileo satellites, then how come I don't see any in GPS Test on my international XZ Premium in USA? No satellites yet? Or the phone just doesn't want to see them?
[Sony Xperia XZ Premium Questions & Answers] Artyomska:
Galileo support is pretty strange. Sometimes I see many Galileo satellites on GPS Test, sometimes I see nothing. I even caught Japanese QZSS satellites in some instances. At least Beidou, GLONASS and GPS are always there, but Sony must fix the spotty Galileo reception.
[Sony Xperia XZ Premium Questions & Answers] TheKorbenDallas:
So, you see it in GPS Test on XZ Premium? Or are you using some other device?
[Sony Xperia XZ Premium Questions & Answers] Artyomska:
Well I am posting in the XZ Premium section, so I am more than sure I am actually using this phone ;)
[Sony Xperia XZ Premium Questions & Answers] TheKorbenDallas:
Well, the question I actually meant to ask is what version of XZ Premium you are using (US firmware?) and were from (US territory?).

So far from California I managed to catch a QZSS satellite and a SBAS satellite - both on the edge of the field. Still no Galileo though.
[Sony Xperia XZ Premium Questions & Answers] Artyomska:
I am using CE1 Customization, version 47.1.A.5.51, in Romania, Europe.
[OnePlus 3 Questions & Answers] Shandroid_94:
Hi guys,

I updated my op3 to latest beta 28 but I got random reboots when I'm not using it;

in fact, usually it reboots when charging or when it's in standby, and other moments like that.. I really don't know why!

I checked the MD5 of the zip, I flashed with the latest bluspark 8.54 and I did a full wipe;

I also reflashed with a dirty flash the ROM(and other ROMs based on Oxy).

Nothing changed.. it appears 2-3 times per day.

Anyone of you got the same error? which could be a solution?
[OnePlus 3 Questions & Answers] Kshysiek:
I had exactly the same problem, but flash rom via adb fixed that.
[OnePlus 3 Questions & Answers] NOSTALGIA:
not experiencing any.. stock non rooted...
[OnePlus 3 Questions & Answers] Shandroid_94:
Sounds interesting.. will try! Thx in advance :cowboy:
[OnePlus 3 Questions & Answers] basvanasperdt:
Morning! You're not the onlyone having troubles with OB28, I'm facing similar issues aswell. Decided to wipe all and perform another clean install (not via adb as suggested above) yesterday afternoon and no issues so far. Will keep you updated

Running ExperienceOS by Jamal btw, which is based on stock OB28
[OnePlus 3 Questions & Answers] candiesdoodle:
I have had this as well. Just keeps rebooting randomly.

Dirty flashing the rom ob28 helps and keeps it stable. But then it reappears after some time randomly. It could be after a few hours or a day or two as well. Yesterday it just started rebooting while it was lying on the desk.

I suspect it could be because of a custom kernel. I have moved from custom to stock (rooted) for now. Lets see
[OnePlus 3 Questions & Answers] pcxtx:
Having same with ob28 also with 5.0. Sometimes it starts rebooting when charging, sometimes while just laying on the desk. 2 times I had it rebooted to recovery. I have even missed an alarm. I found a phone rebooted to recovery in the morning.

Yesterday clean installed 5.0. Rebooted 10 minutes ago. Dirty flashed ob28, retooting also.
[OnePlus 3 Questions & Answers] basvanasperdt:
In another thread, someone suggested rooting with SuperSU instead of Magisk. Tried that and now stable of over 2 days. You might give it a try
[OnePlus 3 Questions & Answers] pcxtx:
It has something to do with magisk or bluspark twrp in combination with something. Tried installing Supersu. Rebooting stopped, but dm-verity message appeared when booting. Decided to format everything. Flashed original recovery, but it could not decrypt file system. Tapped on forgot my password and it wiped everything. Sideloaded OOS 5.0, rebooted, then flashed twrp via fastboot. Flashed magisk 14.5. Stable for 2 days.
[OnePlus 3 Questions & Answers] creezalird:
I have 2 oneplus 3 (one for me and my wife). I installed on both the latest beta Hydrogen OS (basically the same version as OB28).

On both devices, magisk 14.5 is installed.

And yes, I received random reboots maybe 1-2 days one time. And once rebooted, sometimes it will reboot again few seconds after that for few times.

Usually to stop that, after the reboot done, I will reboot the phone manually as fast as possible. And it will be okay for another 1-2 days.

So far I can live with this. But I might downgrade my wife's phone to something else stable
[OnePlus 3 Questions & Answers] simpele:
Same behaviour here on OxygenOS 5.0 with Magisk 14.5 and Boeffla kernel. I usually wipe cache and dalvik in TWRP 3.2 and then it's fine for a couple of hours (or days, if I'm lucky).
[OnePlus 3 Questions & Answers] basvanasperdt:
Quick update from my side. It's been 6 days since I replaced Magisk and rooted with SuperSU and it definitely solved my issues. No reboots or whatsoever.
[OnePlus 3 Questions & Answers] candiesdoodle:
Same here

Been in SuperSU for 3 days. No issues so far

Op3 ob28
[OnePlus 3 Questions & Answers] strange1712:
I had random reboots on Freedom OS 3.1 after about two weeks of use with stock kernel and Magisk 14 (no issues before that). Flashed Blu Spark 207, didn't help. Flashed FOS 3.2: neither. Somebody suggested aggressive dose to be the culprit. It wasn't as I didn't had it enabled for starters. I Flashed official OB28 + magisk and stock kernel... And after one day, reboot. Flashed Blu Spark 208, reboot. But after a couple more reboots last week, they seem to have gone by themselves:

$ uptime

02:00:49 up 4 days, 6:48, load average: 2.98, 2.01, 2.24

*I had not tried using super su instead.

What can we do to debug this issue? Seems like everybody is trying to guess in the dark...

---------- Post added at 09:31 AM ---------- Previous post was at 09:10 AM ----------

If I may suggest, there seems to be a sort of "environmental" origin for this... I've noticed some "correlated incidence of reboots" between unrelated devices, regardless of specific OB variant (OB, FOS, EOS), kernel (stock, Blu), and root method, based on number of complaints and reports of generically unsuccessful attempts to solve the issue in the respective ROM threads, and here too.

Besides, I've not been able to identify any usage related trigger: this has happened to me while phone is idle, while browsing this thread, while driving thru unknown and dangerous streets guided by Waze, while commuting on the subway and only listening music...

Some more rigurous analysis of the prevalence of these reboots as a function of time might prove useful...

Also, there seems to be a growing incidence between users. There seems to be also a "incubation time" for most of us (but not for everybody). Are we sure we are not talking about some disease?
[OnePlus 3 Questions & Answers] simpele:
Just had another reboot. No Magisk log created...

But on every reboot I seem to lose some settings (in the settings app). Which setting is lost, seems completely random: battery optimization setting, LED notification setting, configured sounds,...
[OnePlus 3 Questions & Answers] strange1712:
Aaand..... Two reboots lastima friday, and about 5 today...

This Is turning into a real deal breaker...
[OnePlus 3 Questions & Answers] abhibnl:
Experiencing back to back reboots form morning on stable Oreo op3. Imma switch back to 7.1 til the time its solved
[OnePlus 3 Questions & Answers] Kshysiek:
I also have problems with reboots, but they have given way. Now I have a problem with the phone's sudden heating and battery drain this.
[OnePlus 3 Questions & Answers] candiesdoodle:
Those experiencing reboots .. pls specify if it's with or without magisk. And if it's with, which version. And if it's without, what other modding have you done.

Will be helpful to establish the common thing in the setup causing the reboots
[OnePlus 3 Questions & Answers] strange1712:
With magisk 14.0 and later magisk 14.5. Now I'm testing without root at all, as it seems to be magisk related, it is also reported on the magisk thread.
[LG V30 Questions & Answers] oOII TAHA IIOo:
Since the H930 has just had the bootloader unlock made official, is there any chance to get a .kdz of the SW just like the H930G model? Would help a lot with testing.

EDIT: Never mind, found the firmware! https://lg-firmwares.com/lg-h930-firmwares/
[MTCD  Android Head Units Q&A] Kayhan 17#:
Hey guys,

something went wrong when i flashed the MTCE 2.72 GS File, my unit is now totally black and dead, no response.

What options do i have?

Kind Regards

kaya
[MTCD  Android Head Units Q&A] FauxDreams:
Recovery & Re-flash.

Cheers
[MTCD  Android Head Units Q&A] Kayhan 17#:
The Question is how, do all of these units have an internal USB??

I do hesitate to open up the case and end up in a missing USB Port, when i played around with ADB i could only access USB1 and USB3 before i bricked the unit.
[MTCD  Android Head Units Q&A] Kayhan 17#:
OK, i am doomed...or someone just has a clue where i might solder USB and recover with "Rockchip Assitant"? :crying::crying::crying:
[MTCD  Android Head Units Q&A] marchnz:
See links in my signature.
[MTCD  Android Head Units Q&A] Kayhan 17#:
I already saw your thread buddy, but i absolutely dont have a clue where those USB1 Connections are.

i could find some stuff in the front of the Board like M-USB, L-USB, R-USB and a few centimeters far away +5V USB but dont know exactly where to solder.

Oh and i dont get it why i have to lift 27 and 28 of that chip, so there is no way to hard install this for later applications?

I mean like let 27 and 28 open so i can have 3-USB Ports? AFAIK that 3rd USB is for ADB and Recovery?
[MTCD  Android Head Units Q&A] Kayhan 17#:
Hey Guys,

i tested my px3 board on a different unit and its working, so it seems that my android system is gone. Any ideas how i may fix this?
[MTCD  Android Head Units Q&A] ikerg:
but...the PX3 coreboard has the Android image included...if that worked on other unit....the problem is your MainBoard, not the CoreBoard
[MTCD  Android Head Units Q&A] Kayhan 17#:
yeah, thats what i am thinking of too??

so how the hell is this one dead after firmware update?
[MTCD  Android Head Units Q&A] marchnz:
Agree, sounds like your MCU is corrupt/bad. Replace the mainboard.
[MTCD  Android Head Units Q&A] Kayhan 17#:
impossible, as the old bricked one(which was not bricked!) does work in the new radio, the new mcu of the NEW Radio does not work in my OLD radio shown in the pics above. It still has a black screen and no illumination on the buttons and behaves dead with a definitely working MCU
[MTCD  Android Head Units Q&A] marchnz:
Replace mainboard not som.
[MTCD  Android Head Units Q&A] Wadzio:
I found that video: https://www.youtube.com/watch?v=DkA6o2P_hTc&t=127s

It could help you...but important question is: where to find ha_256_FULL.bin ??
[MTCD  Android Head Units Q&A] Kayhan 17#:
Hey Buddy,

i already flashed the newest file with your mtcdtool (img to bin), but you said in a different thread that it wont turn on because the bootloader is missing, i ordered another unit and will try to do a read and put it on my device to recover it.

if you could do a dump or find that file, dont hesitate to send it to me =)
[MTCD  Android Head Units Q&A] marchnz:
From video, note start address. Is it possible he only flashes standard MCU file?'
[MTCD  Android Head Units Q&A] Wadzio:
ok....but....

What is it?

For me its look like simple RS232ToUSB converter. It's wrong tool.

You should use ST-Link, for example:

and connect it to MCU pins: SYS_SWCLK, SYS_SWDIO. Some boards has special pinpad for that:

On your board I can't find it (picture is poor quality)

---------- Post added at 09:19 AM ---------- Previous post was at 09:14 AM ----------

I don't think so. On video we see 0x08000000

"standard" MCU files (the ones we upload to unit 'dmcu.img') has start address 0x08004000
[MTCD  Android Head Units Q&A] Kayhan 17#:
I have an USBtoTTL aswell and an USBtoUART:

The one in the picture is the UART-adapter and i could flash with the Flashloader-DemonstratorGUI(also from STM)

I used 0x8000 as start adress but as you stated it possibly starts at 0x8004000

I found out that i did a mistake on PIN74 and instead used PIN72 for VSS - but nevermind it worked two weeks ago and it still does =)

I wanted to post here earlier but i had exams and the new board didnt arrive yet =)

EDIT: for the other interested guys, this is what i bought years ago USBtoUART 6-pin CP2102 Adapter
[MTCD  Android Head Units Q&A] Wadzio:
If you have read the topic PX5 Oreo ROM you probably already know that the owner of magintolog.ru (along with the youtube channel) is @kumarai.

He has such a file. Unfortunately, on the 4PDA forum, I found such like this: (=> )

At the moment, there is an opportunity to raise dead MCU chips (MTCD and future MTCE), pull it out of any state. Unfortunately, the existing version will not be published for a number of reasons, excuse me. I can say that the MCU is almost not killed, you really have to make a mistake to kill the MCU. No one is immune from a hardware failure.

You can try to ask him, maybe something has changed since then.

Also be careful when you will try read by the BOOT0 method. This is also from him (=>):

This is excluded. You have to be an idiot manufacturer to give you the opportunity to read the chip. Moreover, when you try to read, the chip will no longer start up, it will wrap up the boot-old firmware from such read attempts.

If you read the datasheet on the protsyk, there are three levels - 0, 1, 2. If transferred to the second level, only the replacement of the protsyk. But it makes sense to change if there is protsik's firmware.

Result: If you tried to do a reading of the protsik, he is in the block, the radio tape recorder is a corpse. Transfer to mode 2

[MENTION=372651]level[/MENTION] 2: chip readout protection, debug features (Cortex®-M0 serial wire) and boot in RAM selection disabled @

Disables the chip firmware option.
[MTCD  Android Head Units Q&A] Kayhan 17#:
He is a professional, i dont think he is gonna give out that file :\
[MTCD  Android Head Units Q&A] Wadzio:
I prepared simple recovey image (based on KLD_V257): https://www.sendspace.com/file/wsvj55

If you want to try flash it and tell us is it works.
[MTCD  Android Head Units Q&A] Kayhan 17#:
Unfortunately, this didnt work either =(

Start Adress is 0x8000000 right?
[MTCD  Android Head Units Q&A] Wadzio:
:(

Yes, six zeros after eight.

I don't have any experiences with Flash Loader Demonstrator

What targets was automatically selected? (and all pages are writable? green icons)

And just in case I ask:

- options bytes you left blank? BOOT1 should be not set (BOOT1=x, BOOT0=0 => Main Flash memory)

- download operation finished successfully ?

- after downloading, you connected BOOT0 to GND and turned on the power again?
[MTCD  Android Head Units Q&A] Kayhan 17#:
Hey mate,

i made a video for you to demonstrate what i did

-i dont have a clue how to set those option-bytes

-download finishes fine as you can see

-didnt know that i had to set PF11/BOOT0 to GND, i did but it still doesnt works

Video Link
[MTCD  Android Head Units Q&A] Wadzio:
It looks like my recovery.bin does not work :(

- good news for you is that your mcu is alive

- option-bytes: left not set as you done should be enough

- BOOT0 pulled down with 10K (as at schematic), but I think GND or even not connected should be enough too
[MTCD  Android Head Units Q&A] Kayhan 17#:
So there is no way i can dump the FW without bricking the new unit, this thread is useless for now =)
[MTCD  Android Head Units Q&A] Wadzio:
It probably does not matter but you test it without SOM?

If without SOM, can you tell what is the status of pin 84 (PD3) ?
[MTCD  Android Head Units Q&A] Kayhan 17#:
I assume you want me to check the voltage?

ill test and edit post in a few minutes

P84 : 2.75V
[MTCD  Android Head Units Q&A] Wadzio:
Hmmm. Not 0 and not ~3.3 :) At the beginning (quite) firmware sets this pin to Hi.

If you want try another recovery.bin I can prepare one.

Now, at the beginning firmware sets to Lo pins: PWR_12V(PB8-95), PWR_5V(PB9-96), PWR_ARM(PB3-89) (of course you can chceck state of those pins now)

I can try to change firmware to set Hi state instead Lo.
[MTCD  Android Head Units Q&A] Kayhan 17#:
Mate youre free to do as many firmwares you want, as long as i dont have my new mainboard. I will flash everything on this what i get.

One goal is to fix, one is to learn and discover future methods in case sonething goes wrong. :)
[MTCD  Android Head Units Q&A] Wadzio:
Did you check state of pins PWR_12V(PB8-95), PWR_5V(PB9-96), PWR_ARM(PB3-89) ?

I'm curious what state of pins will be after flashing this: https://www.sendspace.com/file/5011gg
[MTCD  Android Head Units Q&A] marchnz:
Just a thought - if bootloader is OK, have you thought about installing SOM, force SOM +5v on (by pulling up +3.3v on enable pin 2 of +5vsys psu smps regulator IC - I did this recently to prevent the MCU 'watchdog' powercycling SOM during OTG)

Also pull SOM recovery pin +3.3v (you have to remove some header pin or MCU will sink logic low)

This will power on your SOM into recovery where you could try to flash MCU with MCU image file.

Definitely don't want to take anything away from trying the method you guys are working on...just a thought.

This is one of the best threads in MTCD. Great work guys.
[MTCD  Android Head Units Q&A] Kayhan 17#:
I flashed, put wires on PCs PSU -> measured this after a minute...

PD3 - 2.75V

PB3 - 3.22V

PB8 - 3.22V

PB9 - 3.22V

[MENTION=4974080]marchnz[/MENTION], i would test that later after wadzios reaction but you may need to help me with the circuits, okay? =)

EDIT: i´ve put on the px3 but its still not working =)

Good news for you guys, i got an email from erisin, they will order my Mainboard after february(chinese new year) -> bad news for me, no voice in the car :eek: