yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] kesztió:
Many users report that FYT boards (Android 8 Joying) give a much better navigation performance than PX5 MTCE boards (Android 8 Dasaita, Wondefoo etc.) Despite that latest PX5 MTCE boards (Rev. 8.0) all use a performant, latest generation U-Blox M8030 GNSS chip.

Want to find out why, so, as a first question:

Does somebody know which on-board GPS chip is used on PX5 FYT boards (the ones which power the recent Joying head units)?
[Android Head-Units] looxonline:
Just because I'm afraid you may post this question in every thread on the forum unless someone answers....here you go http://www.icofchina.com/d/file/xiazai/2016-12-05/b1be6f481cdf9d773b963ab30a2d11d8.pdf :)

You will notice that the specs are worse than that of the UBLOX but when considering GNSS performance it's not all about the chipset. They (MTC) could have used a XO instead of a TCXO which would make the performance very poor. Alternatively their RF impedance matching may be poor. There are a number of reasons why the FYT implementation could be better.
[Android Head-Units] emre33:
px5:

9600 port speed.

1HZ.

SBAS nad Glonass not workig (nem működik)

MTC Adroid API bad (rossz, nincs jól implementálva)
[Android Head-Units] kesztió:
Jut have contacted a big PX5 MTC reseller on facebook, he was very helpful and there are good chances that he’ll forward our concerns to the manufacturer.

BTW, please note that using U-blox U-center application the chip performs really decent, even good, just a bit less performant compared to the crystal-driven, high-end Neo M8N + a fairly expensive, mid-range professional antenna. So I don’t think there would be necessarily a bad hardware installation, Android 8 is the faulty piece here.

I’ll keep you informed once I find new information.

(Üdv, és inkább folytassuk 100%-ban angolul, hogy többiek is értsék.)
[Android Head-Units] looxonline:
I highly doubt that Android 8 is doing anything wrong. It interfaces with the chip using NMEA protocol. So old and so standard that it would be a challenge to get wrong. The only thing Android may be messing up is feeding ephemeris data to the chip so that it can hot start. In any case that will not affect the tracking capability.
[Android Head-Units] surfer63:
He is asking for the FYT model, not the QD model.

Glonass works fine on the FYT model, not on the QD model.
[Android Head-Units] kesztió:
Won’t be so sure. How you can explain that I can select any constellations I want from U-center and the satellite data (including SBAS corrections) work as expected – but switching to any Android GPS test application instantly „kills” Glonass and SBAS satellites? Interesting that (in conformity to the USING GNSS RAW MEASUREMENTS ON ANDROID DEVICES white paper) a new location API is implemented since Android Nougat – and exactly this was the moment when things suddenly went wrong on MTC PX5 systems (users report that on Marshmallow everything was OK).
[Android Head-Units] kesztió:
Thanks a lot for your help, you received the thanks point. :)

See my remarks for emre33 about the possibly wrong hardware implementation of the U-Blox M8030.
[Android Head-Units] 96carboard:
"Android" does not interface with the GPS at all. Its the HAL's job to interface with the hardware. It is the vendor's responsibility to write a HAL for their hardware, and as you can imagine, the budget chinese hardware vendors don't do that great of a job at that. The HAL uses callbacks to feed data into Android.
[Samsung Galaxy S7 Questions and Answers] Eyadoo13:
Hello,

I have the G930FD version of S7 (the dual sim version).

I am on the official samsung Firmware but I don't receive OTA updates. Even when I connect to Samsung Kies it also shows there are no updates. last update was security update for April 2017 !!

Please help me.
[Samsung Galaxy S7 Questions and Answers] Beanvee7:
Who's your carrier and where are you located?

Otherwise flashing the last firmware with Odin and using home_csc will update you without data loss.
[Samsung Galaxy S7 Questions and Answers] Eyadoo13:
I use the unlocked version of the mobile which I bought from Saudi Arabia. how can I use home_csc since I am a bit noob in these things :eek:
[Samsung Galaxy S7 Questions and Answers] Beanvee7:
https://updato.com/how-to/how-to-install-an-official-samsung-stock-firmware-using-odin

Boot into download mode (VOL DOWN + HOME + POWER until screen goes light blue) to confirm your model number, download the firmware for that model, and put the files into their slots in Odin (i.e. the files called BL_G930FXXX goes into the 'BL' slot etc, but for CSC put use Home_CSC and not normal CSC.
[Shield Android TV General] mrdude2478:
Yep, I know :( - stupidly I flashed the wrong image to the Shield TV pro (2015) and am stuck in apx mode.

I read somewhere I can flash a hard drive image and lose access to netflix etc due to keys. Can someone point me the way to the guide/image download so I can try and recover with this just now before I throw the box in the bin and get a new one.

Thanks.
[Shield Android TV General] BostonDan:
Unfortunately I do not have access to my widevine keys as my hard drive is completely toast. Do you know if the widevine keys are required, or just the DTB fastboot flashing?

Cheers,

B.D.
[Shield Android TV General] afgok:
no you cant. APX mode=ysf. send it back to nvidia
[Shield Android TV General] mrdude2478:
Ok, quick update.

I was able to recover by putting the drive in a USB caddy, In windows 10 I used winhex in admin mode and flashed the first GB of the drive with one of the backups that someone on here provided.

So that's me up and running now. Does anyone know the location on the drive on where the widevine keys are stored? I made a backup of the gig I overwrote before flashing, so I assume they are in that area.

Thanks.

Edit: OK I found them in broken image dump at address 0x2200000

I copied the hex from 0x2200000 (2178336 bytes) and then flashed that to the fixed drive at the same location, now Widevine is back to Level 1, so I guess that's me back up and running to the state before I bricked now.
[Shield Android TV General] JeffDC:
Well done. Wish I had your tech knowledge.
[Shield Android TV General] mrdude2478:
It's not all that complex really to do, as I bricked the files written were to do with the boot procedure wiping out the first stage boot loader. As the Pro (500 GB) version boots from hard drive rather than a chip it was a case of restoring the boot part - which resides at the start of the drive. As I was able to download a dump from the net (and the partition table is stored at the end of the drive - so no chance this would be wiped out), I could flash that boot loader, and then get into adb/fastboot to restore an image downloaded from Nvidia.

Now as it happens, I didn't know where the widevine keys (for DRM) were stored, and I overwrote them when I flashed the backup (and someone else's keys), so Netflix and Amazon prime video didn't work - luckily I made a backup of the first gig of my drive before I started (probably to be even safer I should have just used a spare sata drive to flash to), so I assumed if my keys were lost that they would be in that image dump (which they were). Someone was kind enough to post this:

https://nv-tegra.nvidia.com/gitweb/...11dd2d9103a205c9ed66e695664;hb=rel-29-partner

Which I was able to figure out the exact location of where the EKS partition was (where the keys are stored), so I then extracted those from my dump and flashed them back to my drive. (winhex makes that easy to do).

I've now made a backup of the first part of my drive and the last part - so if ever in the future I mess up, I can restore (brick proof). Also I had a spare 120GB SSD, so I also made a spare drive with the newest shield firmware on so I can just swap drives out if the original drive breaks down.

Instructions are here on how to do that:

https://xdaforums.com/shield-tv/development/nvidia-shield-tv-ssd-t3402580

https://xdaforums.com/shield-tv/general/guide-migrate-to-ssd-hdd-size-satv-pro-t3440195

So really I'm not technical at all as I was just following guides (apart from the winhex stuff).
[Shield Android TV General] afgok:
outstanding work well done my understanding was apx mode was the proprietry nvidia bootloader and this could not be messed with welldone once again
[Shield Android TV General] rockspin:
Very interesting! I'm glad I didn't trash my 2015 Shield TV those many months ago!
[Shield Android TV General] mrdude2478:
If it's a pro (500GB internal drive), it's brick proof. Even APX mode - can't break it.

If you have a spare 500GB drive, you can use that to test - use the guides I put links to - then flash someone else dumped image using those guides (using a sata drive caddy). Then on your original drive - extract the widevine keys - and flash those to the new drive. Once you're up and running - you can clone your working drive back to your orignal drive (that way you'll always have a spare and be brickproof forever).
[Shield Android TV General] rockspin:
I have the NON pro version, do you think this method will work?
[Shield Android TV General] mrdude2478:
Not with the non pro - the bootloader/software is held on the nand/nor (16GB chip that holds the firmware - I can't remember off the top of my head what type of chip it is). You'd need to find the pinouts of that chip to reprogram it with a hardware programmer.

Another way would be like the way that Nintendo switch is hacked - (purposely put into apx mode), then a modded apx driver loads software from USB (or via usb dongle/computer/chip) which would then allow you to reflash via the Fusée Gelée hack. I think if you go to the switch hacking scene, and visit https://www.ktemkin.com/ - ktemkin was looking for a bricked switch so he/she could write a driver for it for unbricking purposes - he/she has a twitter feed and was asking on there. Maybe you could make

contact and get help on unbricking via software as that would be far easier than removing a chip and flashing it with a programmer.

The difference from booting via a hard drive is that - the software is stored on the drive - not on a chip - so it's easy to recover via a PC. If there's a way to add a hard drive to a 16GB model - that would probably work, but you'd need to compare motherboards to see the difference on how the chip version differs from the HD version - I would imagine both motherboards are similar - if you somehow managed to boot a HD on a 16GB chip model - you could most likely be able to access your flash memory that way to reprogram - but that might be out of your skill level, and the time it would take to do it - you'd most likely be cheaper just buying a new shield.

If I was you though - keep hold of the shield - you may get a modded apx driver at some point in the future and be able to reflash that way.

If you have the 2015 (16GB) version - it could be possible to boot from sata - but you'll need a 500GB drive and a working dump (already posted in this site), and some soldering skills - read this entire page for info on soldering info, adding capacitors - https://www.eevblog.com/forum/reviews/teardown-nvidia-shield-tv/
[Shield Android TV General] kirillinfinite:
First of all , thanks!! I have exact same problem :(

How did you copy the hex? I'm not sure how to do it . .. :(
[Shield Android TV General] oldshanshi:
Thank you for your work.，Can you backup the 1GB data including EKS? My devices widevine keys (for DRM) is Level 3, thanks!!
[Shield Android TV General] Andy4Shurr:
That's not how it works, you have to back up YOUR keys that came on your device hard drive. That's the only way it will match the keys to the hardware on your shield TV.
[Shield Android TV General] Andy4Shurr:
Ok I'm having the same issue you did, bricking the pro with a bad flash.

I'm just editing the hex for my backup to retrieve the keys from my EKS partition. Can I ask you to confirm/clarify ..

1. The blocks you copied are at curser offset 2200000 (I've got that far, I can read the hex stating that the eks partition starts there).

2. You then copied 2178336 bytes of data from that curser offset?

The reason I'm asking is that I can't see any bytes of data around that end curser offset to start a new partition etc. so I want to make sure I get all the EKS data needed.

Thanks, the info you posted here has been really valuable in getting me to this point.

EDIT: Yeah, that all worked out in the end. The actual amount of data in that EKS partition is very minimal, it doesn't use all of those 2178336 bytes at all and I didn't even copy the hex for all of it as most of it was simply empty! Anyway, I've managed to restore my shield with Netflix etc all working so thank you again for sharing this information!
[Shield Android TV General] Andy4Shurr:
Once you've got your backup file it will be in a .bin format, I'm presuming you've got that far. Once you've got that you need to read the hex data with a hex editor, any should do it really. Then you want to go to address 0x2200000 (that's at curser offset 2200000 in hex mode). You'll see a header in the translation window which indicates it's EKS data. You need to copy that data until it stops and there's just zeros).

You then need to open the .bin file that you downloaded which you want to restore (this won't have your eks partition data in it yet) and find the same data with the hex editor as you did before. You then want to overwrite it with the data from your back up. It needs to be copied in the exactly the same location so make sure of that.

Once you've done that you can flash the data using DD commands in Linux and follow the tutorials linked before.
[Shield Android TV General] mrdude2478:
[MENTION=3240717]andy4[/MENTION]shure, well done on fixing your Shield, here's some info for future reference:

Shield Pro SSHD Drive Size: 500107862016 bytes (0x7470C06000)

Shield Operating System (7.1):

Start Offset: 0x0

To Offset: 0xD2913BFF (Total Size: 3532733440 bytes)

Widevine Keys Location: (back these up before doing anything - or you'll lose access to widevine level 1)

(Search for Hex: 902100004E56454B5350)

Start Offset: 0x2200000

End Offset: 0x22021FF (Total Size: 8704 bytes)

Partition Table - (Stored at the end of the drive - required on a new drive so the drive can boot and access partitions - you'll need these for a new drive):

From Offset:0x7470C04C00 (sector 976773158)

To Offset: 0x7470C05FFF (Total Size: 5120 bytes)

If you flash someone else's dump, or reflash the firmware - wipe the user data - or you might get stuck on the nvidia logo:

Erase Userdata:

fastboot erase userdata

fastboot erase cache

or

fastboot format userdata

fastboot format cache
[Shield Android TV General] Andy4Shurr:
After having restored my Shield TV with the shared image and my DRM keys I have realised that there is another key which I needed to restore - the serial number of the device. Not everyone may be bothered about restoring this back to the original as it doesn't affect use of Netflix or any DRM restriced content but there are definitely some use cases. If your device is still under warranty then Nvidia will ask for this (although my warranty is long expired). If you're selling the device and want it to match the packaging serial number then you will have to do this as well. In my case however, I actually had app licences tied to this serial so I needed to restore the original key for that reason.

Now after looking into this serial number a little further it is a 20 character key and although my serial is all numeric I have seen evidence that it can also be alphanumeric.

Also, the key is split into 2 parts...

- The first 14 characters are declared within a partition on the drive and *I think* these are all numeric. As it is declared in a drive partition this means it is editable and can be restored back to the original.

- The last 6 characters seem to be derived from hardware and are not declared anywhere on the drive. This isn't a problem though as this means that they will remain the same no matter if you have the original first part or not!

After looking through the dump of the HDD the serial is actually mentioned in a number of places, however, most seem to be boot logs (mainly from twrp). The actual declaration of the key can be found at address 0x10502156 and the block size to replace is 14 bytes, literally just the first 14 characters of the serial.

Once that is replaced the Shield TV picks up on it straight away on next boot and I didn't need to wipe any cache or anything.

Hopefully this will help someone else that comes across this thread looking for help like I did! Thanks again to [MENTION=2918756]mrdude2478[/MENTION] as I would probably still have a bricked shield if it weren't for him sharing info on how he restored his device.
[Shield Android TV General] mrdude2478:
Can you do a screenshot - I checked my dump (or what I restored from), and it doesn't look like a serial at that address: Mine are all at different addresses (but in plain text).

Thanks.
[Shield Android TV General] Andy4Shurr:
That definitely doesn't look like mine did, I'll check my dump and take a screenshot ASAP. It could be a few days to a week though, we're doing some work to the spare bedroom where my PC is so I can't get to it at the moment.

I'll update this post when I've got it :)
[Shield Android TV General] efek_poznan:
[MENTION=2918756]mrdude2478[/MENTION] offset which [MENTION=5889181]Andy4Shurr[/MENTION] wrote is correct but it's decimal. Correct hex offset: 0xa0400C
[Shield Android TV General] Vartom:
You can’t just take and rewrite the serial number, in this section the checksum will change. Information will be ignored and the console will go into APX mode.
[Shield Android TV General] efek_poznan:
I disagree. I've modified SN the way [MENTION=5889181]Andy4Shurr[/MENTION] described and it works flawlessly without any further adjustments.
[Shield Android TV General] Vartom:
In any case, on the shield tablet it was just that.
[Shield Android TV General] das_kern:
If any of you got any problems with WV L1 DRM the solution is here :

https://xdaforums.com/showpost.php?p=82385839&postcount=554
[Shield Android TV General] TuGa121:
Im re-flahing shield now but using image i have saved on pc i plugged in the ssd to sata using program to burn image...
[Shield Android TV General] fr500:
my ribbon cable died... is there any source for the ribbon cable replacement?

can't find it anymore
[Shield Android TV General] earickb:
can I get that backup? and how you did It please? Im in APX mode as well
[Shield Android TV General] vinsta7:
hi do you think this solution will work with the 2017 Nvidia shield pro 500gb, ive done exactly the same now im stuck in apx mode, I hear the shield connection to pc but do not get any flash boot menus anymore. ive only got a few hairs left on my head now spending hours every night thinking ive got the solution lol thank you for sharing your hard work too
[Shield Android TV General] DJ 1:
I have a shield TV 2015 500GB..

Right, did a complete wipe of the new SSD, (could not copy original shield HDD, as it turns out when I went to copy it, windows must have popped up asking to 'initialise disk', which nuked it)

Which must be what put it into Apx (plugged into pc, device manager shows apx)

I flashed the start.bin & end.bin files from the 'ssd done thread to the ssd, can't get shield into any bootloader or fastboot??

It says plug in, wait 2secs, touch the Nvidia power sensor (& hold) for 5-6 secs, but all that happens is it turns off??

However, the instant it's power is plugged in, the green light comes on, so I don't really really get to wait the 2secs before touching the power sensor,

Makes zero sense...

??

Cheers.
[Sony Xperia XZ1 Compact Questions & Answers] Dean F:
How can I stop the software update app from re-installing this dam apps after every reboot? (non-root solution please!)

You can see the apps the the bottom of the screen shot. They are pending installation when connected to wifi. ps, news suite, etc, sketch etc.

I have tried the ADB uninstall for users. But the apps are back after reboot... arg.

If I disable auto update, then they just sit in these grayed out icons waiting for installation.

Thanks in advance.
[Sony Xperia XZ1 Compact Questions & Answers] Inerent:
Disable those apps in app manager. I did that and works
[Samsung Galaxy Tab A series Questions & Answers] tdvolland:
I have rooted my SMT580 and checked it with Root Checker.

SU works, Root explorer File manager works and deletes some bloatware

I have then installed System App Safe Remover (Which works fine on my ASUS tablet). It will remove my installed apps, but none of the System Apps. No matter which one it tries to install, the pop up window alwas says:

Done, 1 failed Uninstall, Yes

(see attached picture)

What am I doing wrong?

Thanks
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] Shivam Kumar Jha:
ArrowOS

​

ABOUT

ArrowOS is an AOSP inspired open source project started with the aim of keeping things simple, clean and neat. We added just the right and mostly used stuff that will be actually USEFUL at the end of the day.

Website: https://arrowos.net

Telegram: Channel | Group

Github: https://github.com/ArrowOS

Code Review: review.arrowos.net

E-mail: arrowos.contact

To apply for maintainership Check this out

WHAT WORKS?

Almost everything

WHAT DOESN'T WORK?

Encryption

Selinux is permissive

You tell me

Be sure to include a log : check how to

INSTRUCTIONS

Clean Flash

Download The ROM & GApps

Wipe: System, Data, Dalvik, Cache

Flash ROM + GApps

Reboot & Enjoy

Dirty Flash

Download the ROM

Wipe: Dalvik and Cache

Flash ROM (+Magisk if rooted previously or if want root)

Reboot & Enjoy

DOWNLOADS

ROM: Click Here for ROM

AFH Mirror

Gapps: Click Here for GApps(ARM64)

Note : Pico, Nano or Micro Gapps are recommended. We don't prefer STOCK/HEAVY Gapps

Source Code

Device, Kernel & Vendor source

Special thanks to

AOSP

LineageOS

Ezio Lacandia Bijelkic

Maxwen

Alex Cruz

scoute-dich

Tibor Kaputa

POSP

[MENTION=5834335]Agent_fabulous[/MENTION]

[MENTION=7426783]beingmishra[/MENTION]

And all other Open Source - Developers,Teams and Organisations

DM if we missed someone - you can always look at GitHub to find more contributors! :highfive:[/QUOTE]

XDA:DevDB Information

[ROM][X00TD][9.x] Arrow OS [UNOFFICIAL], ROM for the Asus ZenFone Max Pro M1

Contributors

Shivam Kumar Jha

Source Code: https://github.com/ArrowOS

ROM OS Version: 9.x Pie

ROM Kernel: Linux 4.x

ROM Firmware Required: Latest firmware + Unlocked bootloader + TWRP

Based On: AOSP

Version Information

Status: Beta

Created 2018-09-11

Last Updated 2018-09-11
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] Shivam Kumar Jha:
Changelog:

20180911: Initial build.

20180912: Enabled ANT & NFC (for russian model) + updated ims.apk

20180919
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] Mahz4130:
404 not found.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] AkashAlien:
what u mean, link working
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] cjcool_123:
in call volume?
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] anandushari:
Can I dirty flash over havoc os ( Oreo ) ROM
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] gusbalaa:
Hope not facing slow charging. T.T
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] cjcool_123:
any1 tried this rom?
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] Nitesh121:
Clean flash required if you are switching to another rom :good:
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] boosters:
JIO Volte is not working, unable to call.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] theraaj:
1+
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] boosters:
Another bug - Bluetooth is not working while transferring the files from desktop mobile, bluetooth crashed.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] anandushari:
I have switched from various Oreo roms

RR - havoc no issues in dirty flash .. but I don't know about switching to two versions Oreo to pie !
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] chengalrayan:
Charging speed

Can some one please confirm about charging speed ?

.