Database Info

[REF]Nexus Player Stock OTA URLs

Introduction:
This is a list of all known OTA's for the Nexus Player
Click to expand...
Click to collapse
File List:
LRX21M → LRX21V
LTW87L → LRX21V
See ASUS Nexus Player # Official ROMs - XDA Wiki for a list of files
Click to expand...
Click to collapse
How to flash:
Requirements:
Stock recovery
Unmodified /system
Unmodified /oem
Unlocked bootloader
Basic understanding of command line/shell
Unlock your bootloader
Download and set up adb and fastboot
Reboot into fastboot mode
Open up a command prompt/shell where you saved fastboot
enter into command prompt/shell: "fastboot oem unlock"
Enter recovery mode via onscreen buttons
Enable recovery ui
(How do you do this for this device?)
Set up adb
Select apply update from adb
enter into command prompt: "adb sideload <path to saved update.zip>
Click to expand...
Click to collapse
FAQ:
How to find the ota?
If you're rooted, wait for the device to prompt you to update, then check /cache for the file
If you're not rooted, wait until the same time and do an adb logcat and look for a line with .zip in it
Why isn't the latest ota listed?
We can only list what we have, if the ota from Build X to Build Y isn't listed, we dont have the file for it yet.
How do you setup adb/fastboot
Please read the stickies in the general subforum, this is not a formal guide
Do I need to unlock the bootloader to flash the update zip?
Yes, if you wish to do it manually.
If you allow android to prompt for the update, you do not need to unlock
Can I flash this if I have a custom rom?
No, you must be on a unmodified rom
Can I flash this if I'm rooted?
No, rooting modifies /system.
Click to expand...
Click to collapse
Credits:
Click to expand...
Click to collapse
Changelog:
Nov 29, 2014: Added LRX21V
Nov 18, 2014: Added LTW87L → LRX21M
Oct 15, 2014: Initial page
Click to expand...
Click to collapse
2char

Can Nexus Player images be loaded and bootted on a similarly specced Intel Atom based PC?

kettal said:
Can Nexus Player images be loaded and bootted on a similarly specced Intel Atom based PC?
Click to expand...
Click to collapse
It's too soon to tell and it depends on what the bootloader allows for it.
Just because goog might include one that isnt locked down, it doesnt mean it's automatically bios or uefi complient.
Loading linux on it is one thing, but expecting it to work like a normal pc with linux or even windows isnt something you can assume.
Goog's bootloaders are not all universally uefi complient even though other similar devices include them (winrt/wp8/assorted android devices have complient bootloaders)
Also, this is off topic for this thread.

https://groups.google.com/forum/?hl=en&nomobile=true#!topic/android-building/bm3iwCrjO2s said:
Hi all,
Builds for Android 5.0 have been released.
The following are the builds, tags, and devices supported:
- LRX21M, android-5.0.0_r2, Nexus Player fugu
- LRX21L, android-5.0.0_r1, Nexus 9 volantis
Additional devices support are coming soon.
Thanks!
bill
Click to expand...
Click to collapse
The NP will also have an ota before release.

Factory image posted:
https://developers.google.com/android/nexus/images#fugu
Version: 5.0 (LRX21M)
Download: Link
MD5 Checksum: b5380180959cdf8b99a24339b4800b64
SHA-1 Checksum: aeed3bef8331aba50c94c188ce3753d3ae9afd83

TheManii said:
The NP will also have an ota before release.
Click to expand...
Click to collapse
There is an ota from LTW87L → LRX21M, I do not have the ota yet.
Also: the NP is unlockable without having to go to setting first, unlike the N6/N9: PSA: OEM Unlock On The Nexus 6 And 9 Requires Checking A Box In Developer Options

Update: PSA: New Lollipop OTA Procedure On Nexus Devices Means Your Update Will Fail If Your System Is Modified In Any Way At All
For future otas, rooting will not break your ability to ota (rooting itself wont, if you modify files you will still break ota due to that)
The NP's kernel does not have dm-verity / secure /system enabled, and it must be enabled prior to the first OTA to stay consistant. (technical note, it's still possible to deploy consistant/secure /systems without it, but the kernel itself wont bother checking, so it's unlikely an issue at all)
Goog can still deploy it after the fact, but it would require a full rom ota instead of merely a delta/patch ota, this is highly unlikely to happen.
This will be reconfirmed once I have the file and url for the first ota.
Edit: see below

Update: LTW87L → LRX21M
The NP does use secure /system otas, ROOTING WILL BREAK OTAS.
If you are rooted or have modified your /system in any way, you will need to use factory images to update

LTW87L → LRX21V
LRX21M → LRX21V

URL for the 5.1.1 OTA
http://android.clients.google.com/p...6.signed-fugu-LMY47V-from-LMY47D.99b5efed.zip

MPZ44Q to MPZ79N OTA zip
Here is the zip for upgrading the first Android M preview to the Dev preview
Sorry for sort-of breaking the rules. Links are in the attached text file.

doesn't sound like this ota url thread is really being maintained anymore, but anyways....Nov security patch:
https://android.googleapis.com/pack...d2918bc567.signed-fugu-MRA58N-from-MRA58K.zip

Sourced from jduck:
https://android.googleapis.com/pack...5af.signed-signed-fugu-MMB29U-from-MMB29T.zip
MMB29U-from-MMB29T

MMB29V-from-MMB29U
Code:
https://android.googleapis.com/packages/ota/google_fugu_fugu/8793bbdb81c005f5cb0f2a224b20e03365e0a974.signed-fugu-MMB29V-from-MMB29U.zip

MOB30D from MMB29V
https://android.googleapis.com/pack...afd.signed-signed-fugu-MOB30D-from-MMB29V.zip

MOB30W from MOB30P
https://android.googleapis.com/pack.../0825452c453e9fa32a2988c6fce122c530e8654d.zip
by Jduck

[help]trying to build chroma rom

Please be patient as i am new in building roms[built 3-official roms], now am building chroma rom but bacon is an unsupported device. i have cloned all the proprietary blobs and kernel. but on 'lunch' i do not see my device.
any advice?
Code:
Lunch menu... pick a combo:
1. aosp_arm-eng
2. aosp_arm64-eng
3. aosp_mips-eng
4. aosp_mips64-eng
5. aosp_x86-eng
6. aosp_x86_64-eng
7. full_fugu-userdebug
8. aosp_fugu-userdebug
9. mini_emulator_arm64-userdebug
10. m_e_arm-userdebug
11. m_e_mips64-eng
12. m_e_mips-userdebug
13. mini_emulator_x86_64-userdebug
14. mini_emulator_x86-userdebug
15. aosp_dragon-userdebug
16. aosp_dragon-eng
17. aosp_flounder-userdebug
18. aosp_angler-userdebug
19. aosp_bullhead-userdebug
20. hikey-userdebug
21. aosp_shamu-userdebug

You have modify device tree for building ROM
Take reference of other device's tree
Sent from my OnePlus One using XDA Labs

nathsagar96 said:
You have modify device tree for building ROM
Take reference of other device's tree
Sent from my OnePlus One using XDA Labs
Click to expand...
Click to collapse
I am trying to do that, but i am finding it very difficult, as i am starting building roms. And there aren't any latest guides about building unofficial roms.

This would help you
https://www.youtube.com/shared?ci=XJk1GDuh9gg
Sent from my OnePlus One using XDA Labs

I guess you are missing a file called vendorsetup.sh in your device tree.

Bongofriend said:
I guess you are missing a file called vendorsetup.sh in your device tree.
Click to expand...
Click to collapse
i set it up...noe the device shows in lunch menu...but on compiling i get errors....
Code:
No private recovery resources for TARGET_DEVICE bacon
Checking API: checkpublicapi-last
out/target/common/obj/PACKAGING/public_api.txt:1966: error 17: Field android.R.style.TextAppearance_Material_Wi
dget_Button_Inverse has changed value from 16974548 to 16974565
out/target/common/obj/PACKAGING/public_api.txt:2011: error 17: Field android.R.style.ThemeOverlay_Material_Dial
og has changed value from 16974550 to 16974564
out/target/common/obj/PACKAGING/public_api.txt:2012: error 17: Field android.R.style.ThemeOverlay_Material_Dial
og_Alert has changed value from 16974551 to 16974566
out/target/common/obj/PACKAGING/public_api.txt:2120: error 17: Field android.R.style.Theme_Material_Light_Light
StatusBar has changed value from 16974549 to 16974563
******************************
You have tried to change the API from what has been previously released in
an SDK. Please fix the errors listed above.

[rom][treble]phh aosp 8.1[lm-g710em]

HI Guys , its me again so after a long working night of disabling encryptions and verifications i finaly was able to boot a AOSP Generic System Image on my LG G7 (EUROPEAN VARIANT ONLY) and now im here to show you how to install​
How to install ?​​
Download the GSI from PHH AOSP thread , take a/b ones with ot without gapps as you like
Download my SecuretyOff-Vendor-image and my Permissive boot.img
Reboot to fastboot and unlock your bootloader if you havent done it yet (you can find tutorials online, same method as on g6 and previous)
flash the magisk enabled securetyoff permissive kernel with the command "fastboot flash boot_a pathtoimghere"
Reboot your G7 to LG Stock os and install magisk manager and TerminalEmulator from PlayStore
Now copy the Downloaded Vendor file to your internal sdcard and rename it to vendor.img
Open TerminalEmulator (adb shell works aswell) and type su, hit enter, then type "dd if=/sdcard/vendor.img of=/dev/block/bootdevice/by-name/vendor_a" , hit enter m this will take some time pls be patient
Once youre done with flashing the new vendor reboot to fastboot again and flash the GSI with the following command "fastboot flash system_a pathtoimghere"
One last step before you can enjoy AOSP type "fastboot -w" and then "fastboot reboot"
Whats Working ?​
So for me everyting works so far i just noticed 2 small bugs till now
1. the Notification LED wont stop blinking (im on that already)
2.sometimes the display turns black for about 0,5secs
3. if your headphone jack doesn't work open up a root shell and enter "setprop persist.sys.overlay.devinputjack true"​
Credits​
Me for testing and patching the **** out of that boot.img and vendor.img
AutoPrime for his G7 system Dump
Phhuson for his brilliant work on GSI's
Zefie for recommending me the right tool to repack kernel without bootloops (xD)
SGMarkus for providing ideas and additional Help

reserved

reserved 2

Update , Ressurection Remix Gsi and LineageOS Gsi work too , also i was able to fix the blinking led , but it doesnt work at all anymore (lights hal doesnt load will investiagte tomorrow) but RR or Los doesnt have gapps packed with them so you will need to wait for twrp to be ready (i think i will finish it in next few days)

J0SH1X said:
HI Guys , its me again so after a long working night of disabling encryptions and verifications i finaly was able to boot a AOSP Generic System Image on my LG G7 (EUROPEAN VARIANT ONLY) and now im here to show you how to install
How to install ?
Download the GSI from PHH AOSP thread , take a/b ones with ot without gapps as you like
Download my SecuretyOff-Vendor-image and my Permissive boot.img
Reboot to fastboot and unlock your bootloader if you havent done it yet (you can find tutorials online, same method as on g6 and previous)
flash the magisk enabled securetyoff permissive kernel with the command "fastboot flash boot_a pathtoimghere"
Reboot your G7 to LG Stock os and install magisk manager and TerminalEmulator from PlayStore
Now copy the Downloaded Vendor file to your internal sdcard and rename it to vendor.img
Open TerminalEmulator (adb shell works aswell) and type su, hit enter, then type "dd if=/sdcard/vendor.img of=/dev/block/bootdevice/by-name/vendor_a" , hit enter m this will take some time pls be patient
Once youre done with flashing the new vendor reboot to fastboot again and flash the GSI with the following command "fastboot flash system_a pathtoimghere"
One last step before you can enjoy AOSP type "fastboot -w" and then "fastboot reboot"
Whats Working ?
So for me everyting works so far i just noticed 2 small bugs till now
1. the Notification LED wont stop blinking (im on that already)
2.sometimes the display turns black for about 0,5secs
Credits
Me for testing and patching the **** out of that boot.img and vendor.img
AutoPrime for his G7 system Dump
Phhuson for his brilliant work on GSI's
Zefie for recommending me the right tool to repack kernel without bootloops (xD)
SGMarkus for providing ideas and additional Help
Click to expand...
Click to collapse
Amazing work friend

What about the rom with the DAC? I can change this in the settings of the sound more precise. So not like the lg rom, the preset sound profiles?

Look forward to this! Many thanks +++

what about the dac? sound does not work over jack connection.

Hi.
Does the wide camera work with this rom?
And does the radio fm work?
Where can I find the last release?
Thanks.
Sent from my LM-G710 using Tapatalk

ricxgp said:
Hi.
Does the wide camera work with this rom?
And does the radio fm work?
Where can I find the last release?
Thanks.
Sent from my LM-G710 using Tapatalk
Click to expand...
Click to collapse
wide angle works on aosp rom , fm radio idk but try , you can find the latest release in treble enabled device section of xda

Any word on AOSP 9? As far as I know it requires vndk 8.1 but the g7 launched with Android 8. Do we have to wait for Android 8.1/9 from LG for AOSP 9?

https://highonandroid.com/android-r...oject-treble-unlocked-bootloader-twrp-method/
I saw a video on youtube by max lee i do believe he said you could install this as long as you had twrp recover
I have the sprint verison so i cant try but if anyone with twrp can try and comment

LameMonster82 said:
Any word on AOSP 9? As far as I know it requires vndk 8.1 but the g7 launched with Android 8. Do we have to wait for Android 8.1/9 from LG for AOSP 9?
Click to expand...
Click to collapse
does not work will maybe never work

Guys, can anyone pls do this in adb (or if you have root with terminal app):
echo 0 > /proc/sys/kernel/kptr_restrict
cat /proc/kallsyms >/sdcard/kallsyms.txt

UltraM8 said:
Guys, can anyone pls do this in adb (or if you have root with terminal app):
echo 0 > /proc/sys/kernel/kptr_restrict
cat /proc/kallsyms >/sdcard/kallsyms.txt
Click to expand...
Click to collapse
With the stock ROM or with aosp?

LameMonster82 said:
With the stock ROM or with aosp?
Click to expand...
Click to collapse
Doesn't really matter

so the headphone jack is now fixed open up a root shell and type setprop persist.sys.overlay.devinputjack true then reboot and it will work

UltraM8 said:
Guys, can anyone pls do this in adb (or if you have root with terminal app):
echo 0 > /proc/sys/kernel/kptr_restrict
cat /proc/kallsyms >/sdcard/kallsyms.txt
Click to expand...
Click to collapse
Hello, sorry for being so late but i finaly got the files that youre looking for. "Kptr_restrict" is attached in the post but "kallsyms" is too big so i uploaded it to my google drive. The link is:
https://drive.google.com/file/d/1Mn9jeS7n681dbRWvZqlundCuTAvNF4FJ/view?usp=drivesdk

LameMonster82 said:
Hello, sorry for being so late but i finaly got the files that youre looking for. "Kptr_restrict" is attached in the post but "kallsyms" is too big so i uploaded it to my google drive. The link is:
https://drive.google.com/file/d/1Mn9jeS7n681dbRWvZqlundCuTAvNF4FJ/view?usp=drivesdk
Click to expand...
Click to collapse
thx man!

LameMonster82 said:
Hello, sorry for being so late but i finaly got the files that youre looking for. "Kptr_restrict" is attached in the post but "kallsyms" is too big so i uploaded it to my google drive. The link is:
https://drive.google.com/file/d/1Mn9jeS7n681dbRWvZqlundCuTAvNF4FJ/view?usp=drivesdk
Click to expand...
Click to collapse
I've checked kallsyms, how did you get it? via terminal app, or adb (or even twrp maybe if it's possible on g7)? The prob is that functions addresses are zeros, that's not good.

[ROM] [Unofficial] [Stable] GrapheneOS 10 Pre-Rooted

**** Disclaimer: I'm not responsible if you destroy your device. Use at your own risk!!! ****
GrapheneOS is an open source privacy and security focused mobile OS with Android app compatibility. It's focused on the research and development of privacy and security technology including substantial improvements to sandboxing, exploit mitigations and the permission model. Currently it is based on AOSP.
Link: (Mod Edit: Link removed)
Important information:
1. This ROM does NOT include Gapps or Google Play Service and hasn't Signature Spoofing Support. If you rely on the mentioned things this Rom isn't for you.
2. I take the official releases, modify the install script and include a pre-patched Magisk boot image. I'm not in contact with the GrapheneOS dev which is the reason why i mark this ROM as Unofficial.
3. Due of point two: Please don't ask questions on the official channels as reddit. Leave comments etc here on this thread.
4. You need a unlocked bootloader to flash this rom and must have adb+fastboot installed on your computer. If this is not the case download it from here: https://developer.android.com/studio/releases/platform-tools
I plan to make unofficial releases when new official builds are available.
Features:
AOSP 10
Built-in Firewall
Built-in local backup function (it's not working on all Apps; some doesn't support it)
Improved MAC Randomization
Hardened Kernel
Expanded Permissions (sensors)
Force calls to 4G only
Bugs
- Receiving text over verizon sim doesn't work reliable. Thx @wolfu11 for reporting.
Download: (Mod Edit: Link removed)
Installation:
Notice 1: The First-time installation will wipe your data. Backup first (i recommend this too when you follow the update instructions to be safe)
Notice 2: I recommend to have the newest stock firmware before the First-time installation
First-time installation:
1. Download the zip from the linked download page and unzip it on your computer
2. Copy the following files into the plattform-tools folder:
-> coral zip
-> bootloader img
-> radio img
-> flash-all_first_install.bat for Windows or flash-all_first_install.sh for Linux
3. Boot your phone into fastboot mode and verify that the phone is recognized from your computer
4. In Terminal (Linux) or Powershell (Windows): Run the appropriate script
5. Install the Magisk Manager App
10. Be happy with a rooted GrapheneOS
Update:
Notice: I assume that fastboot+adb is still installed on your computer.
1. Download the newest zip from the linked download page and unzip it on your computer
2. Copy the following files into the plattform-tools folder:
-> coral zip
-> bootloader img
-> radio img
-> flash-all.bat for Windows or flash-all.sh for Linux
If your computer asks you to overwrite the current files in the plattform-tools folder, confirm it.
3. Boot your phone into fastboot mode and verify that the phone is recognized from your computer
4. In Terminal (Linux) or Powershell (Windows): Run the appropriate script
5. Start the system once. This need a few more time than the first installation cause the data partition remains. Be patient.
6. Install the Magisk Manager App
7. Be happy with a rooted GrapheneOS
Sources:
https://github.com/GrapheneOS
https://grapheneos.org/releases
https://github.com/GrapheneOS/kernel_google_coral
https://github.com/GrapheneOS/device_google_coral-kernel
All Credits go to:
- The GrapheneOS team
- wolfu11 for reporting the verizon bug and testing the windows scripts
- and topjohnwu for his amazing Magisk
Created: 09.08.2020
Based on: Android 10
Updated: 21.08.2020
Current Version: 2020.08.07.01

Changelog from 09.08.2020
New Release: 2020.08.03.22
SHA3-512 Hash for Complete zip:
Code:
773c67b8571927c6f884a98ee67a10f96c3a759e34f925f7a8aaab7c19a4ca6b1ff53bb6dc500b4fe7c306b73853189a1c559889df6d9b4f2e8a90258d3d26c9
SHA3-512 Hash for Unpatched boot.img:
Code:
9b584f6941d37f60a7ed17ec4108b7bf484c3cbf1b63f2be6af1e59f452ed1d06e1b64704785d6ca3b38a3c09c8f29657f88c757bda993df509ef001d9842f00
Changes:
full 2020-08-01 security patch level
full 2020-08-05 security patch level
rebased onto QQ3A.200805.001 release
fix secondary stack hardening when a non-page-size multiple stack size is specified
fix picking up previous build date when doing incremental builds
Vanadium: update Chromium base to 84.0.4147.89
Vanadium: update Chromium base to 84.0.4147.105
Vanadium: update Chromium base to 84.0.4147.111
Vanadium: remove Chromium logo in chrome://version
kernel (Pixel 4, Pixel 4 XL): read-only data expansion

Changelog from 11.08.2020:
Updated the OP with some more informations
Rewrite the instruction cause i believe that they were not fully correct.
Reupload the 2020.08.03.22 unofficial release with new structure. I patched the boot.img which come with GrapheneOS in the zip with Magisk and then replaced the original GrapheneOS boot.img in the zip with the patched version.

Hi good evening to all,
Can somebody try to install this Rom with the updated instructions? I think they should work now (at least on Linux) but i would appreciate a confirmation to be safe.

dhacke said:
Changelog from 11.08.2020:
Updated the OP with some more informations
Rewrite the instruction cause i believe that they were not fully correct.
Reupload the 2020.08.03.22 unofficial release with new structure. It isn't needed anymore to flash Magisk separately from the zip. I replaced the stock boot.img in the zip with the pre-patched one.
Click to expand...
Click to collapse
Just a heads up - you really aren't meant to pre-patch a boot image for Coral/Flame, as you are only meant to patch the boot image from your own individual device, as per the man topjohnwu himself
See: https://twitter.com/topjohnwu/status/1272136975022084097?s=19

Can you supply the unpatched boot img?
Thank you

wolfu11 said:
Can you supply the unpatched boot img?
Thank you
Click to expand...
Click to collapse
Done. Look here: (Mod Edit: Link removed)
I added an SHA3-512 Hash for file checking,too (see changelog from 11.08.2020).

Changelog from 15.08.2020
New Release: 2020.08.07.01
SHA3-512 Hash for Complete zip:
Code:
f3a2b088e0ec503296d5a2527a3766951cb2a3ccd1955ced14d304222e76ed3f341dd9d84b6e186a534eddac335065b756c1fdc89d0f1db3985314424e7f9eea
SHA3-512 Hash for unpatched boot image:
Code:
11abb901511ce8e39911bc951be4b1a349158c5d8389e74766942159c0f83aa9730ed39d8c8ae6c3cc66be559e3c165b5d4f35e0962d20a7be0b1532673a0287
Changes:
SELinux policy: fix executing apk libraries as executables for third party applications
Installation Notices:
From 2020.08.03.22 => No wipe needed. Just take the update scripts and let the right one running (see OP).
From Stock Rom => Use the install_first scripts. Be aware: This will wipe your data
Apart from that i recommend to make a backup first always (to be safe).

Wireguard Kernel integration
dhacke said:
Hi good evening to all,
Can somebody try to install this Rom with the updated instructions? I think they should work now (at least on Linux) but i would appreciate a confirmation to be safe.
Click to expand...
Click to collapse
Hi, great work!! It was exactly what I was looking for, GrapheneOS with root. Are you able to integrate wireguard into the kernel?

[email protected] said:
Hi, great work!! It was exactly what I was looking for, GrapheneOS with root. Are you able to integrate wireguard into the kernel?
Click to expand...
Click to collapse
Hi Cryptt33,
first thx for your praise.
Regarding wireguard integration:
You should be able to use Wireguard independently from the kernel if i understand the description from the wireguard f-droid app right (https://f-droid.org/en/packages/com.wireguard.android/).
Then Wireguard runs in a userspace version. Apart from that i have found a xda thread already regarding wireguard integration. I guess i will at least try it and mayby i will be successful with the help of the thread. But i can't give a eta. I built roms from sources in the past but i until now i didn't try to modify them before the compiling step.
Best regards
dhacke

dhacke said:
Hi Cryptt33,
first thx for your praise.
Regarding wireguard integration:
You should be able to use Wireguard independently from the kernel if i understand the description from the wireguard f-droid app right (https://f-droid.org/en/packages/com.wireguard.android/).
Then Wireguard runs in a userspace version. Apart from that i have found a xda thread already regarding wireguard integration. I guess i will at least try it and mayby i will be successful with the help of the thread. But i can't give a eta. I built roms from sources in the past but i until now i didn't try to modify them before the compiling step.
Best regards
dhacke
Click to expand...
Click to collapse
Just need to add this to local_manifest for WG support
If unfamiliar with local_manifest, it's located in /.repo/local_manifests/ - it'll be the only file in that dir, often it's called room service.xml but it could be something like graphene_manifest.xml. Either way, it'll be the only file there and it'll be an XML - add those lines above to it and sync and you should have WireGuard support.
<remote name="zx2c4" fetch=https://git.zx2c4.com/>
<project remote="zx2c4" name="android_kernel_wireguard" path="kernel/wireguard" revision="master" sync-s="true" />

dhacke said:
Hi good evening to all,
Can somebody try to install this Rom with the updated instructions? I think they should work now (at least on Linux) but i would appreciate a confirmation to be safe.
Click to expand...
Click to collapse
I've tried this several time with a windows computer with no luck the shell opens briefly with red writing on the top and closes.
i must be doing something wrong but can't put my finger on it..... i run windows ltsb but i don't have any issues up and downgrading my p4 xl on it i am running the latest platform tools but get this message:
C:\Users\Wolf's laptop\Desktop\platform-tools_r30.0.4-windows\platform-tools>flash-all_first_install
fastboot : The term 'fastboot' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:10
+ $version=fastboot --version; try { $verNum = $version[0].substring(17 ...
+ ~~~~~~~~
+ CategoryInfo : ObjectNotFound: (fastboot:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
fastboot too old; please download the latest version at https............

wolfu11 said:
I've tried this several time with a windows computer with no luck the shell opens briefly with red writing on the top and closes.
i must be doing something wrong but can't put my finger on it..... i run windows ltsb but i don't have any issues up and downgrading my p4 xl on it i am running the latest platform tools but get this message:
C:\Users\Wolf's laptop\Desktop\platform-tools_r30.0.4-windows\platform-tools>flash-all_first_install
fastboot : The term 'fastboot' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:10
+ $version=fastboot --version; try { $verNum = $version[0].substring(17 ...
+ ~~~~~~~~
+ CategoryInfo : ObjectNotFound: (fastboot:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
fastboot too old; please download the latest version at https............
Click to expand...
Click to collapse
Hi wolfu11,
i know this message in similar way on Linux. To fix it on linux i need to run all fastboot commands and scripts with './' before.
So for example:
./fastboot devices instead of fastboot devices or ./flash-all.sh instead of flash-all.sh.
I done this in the scripts for linux already cause i know it is needed there but didn't thought that it is needed on windows, too.
So please go into the script and make this before all fastboot commands:
./
Save it and execute it in the plattform-tools folder with ./ again in the shell. Hopefully it runs then.
If this fixes your issue, i will update the windows scripts.

dhacke said:
Hi wolfu11,
i know this message in similar way on Linux. To fix it on linux i need to run all fastboot commands and scripts with './' before.
So for example:
./fastboot devices instead of fastboot devices or ./flash-all.sh instead of flash-all.sh.
I done this in the scripts for linux already cause i know it is needed there but didn't thought that it is needed on windows, too.
So please go into the script and make this before all fastboot commands:
./
Save it and execute it in the plattform-tools folder with ./ again in the shell. Hopefully it runs then.
If this fixes your issue, i will update the windows scripts.
Click to expand...
Click to collapse
I will try it when I get home today thank you

wolfu11 said:
I will try it when I get home today thank you
Click to expand...
Click to collapse
that didn't work either i downloaded the latest platform tools so im at a loss about the fastboot issue.
I'm going keep trying
Update: I was able to get the official Graphene to work via putting the image into a working stock update platform tools folder and renaming it to the stock image. it wouldn't work per instruction on the website very strange.

wolfu11 said:
that didn't work either i downloaded the latest platform tools so im at a loss about the fastboot issue.
I'm going keep trying
Update: I was able to get the official Graphene to work via putting the image into a working stock update platform tools folder and renaming it to the stock image. it wouldn't work per instruction on the website very strange.
Click to expand...
Click to collapse
Well it was worth a shot texts don't work on verizon so i guess i'll just give up.
thank you

wolfu11 said:
Well it was worth a shot texts don't work on verizon so i guess i'll just give up.
thank you
Click to expand...
Click to collapse
Hi wolfu11,
i tested the bat script (more precisely flash-all.bat) with './' on my dedicated gaming machine with win 10 2004 education, too. First i got the same problem as you: It didn't run whether i made './' before all fastboot commands in the scripts.
Then i removed all the './' before all fastboot command except at this line:
Code:
$version= fastboot --version; ^
So the line looks now:
Code:
$version=./fastboot --version; ^
And hurray the script worked without problems on my machine (see attached screenshots).
Only as reminder: The bat scripts are from the 2020.08.07.01 unofficial release so you need the radio, bootloader and image files from that release.
i attached the new scripts with my mentioned modification, too. Xda doesn't allow bat files so i made them into a zip file. Please test once more. Thx in advance.

dhacke said:
Hi wolfu11,
i tested the bat script (more precisely flash-all.bat) with './' on my dedicated gaming machine with win 10 2004 education, too. First i got the same problem as you: It didn't run whether i made './' before all fastboot commands in the scripts.
Then i removed all the './' before all fastboot command except at this line:
Code:
$version= fastboot --version; ^
So the line looks now:
Code:
$version=./fastboot --version; ^
And hurray the script worked without problems on my machine (see attached screenshots).
Only as reminder: The bat scripts are from the 2020.08.07.01 unofficial release so you need the radio, bootloader and image files from that release.
i attached the new scripts with my mentioned modification, too. Xda doesn't allow bat files so i made them into a zip file. Please test once more. Thx in advance.
Click to expand...
Click to collapse
That script worked thanks

wolfu11 said:
That script worked thanks
Click to expand...
Click to collapse
Yeah finally. I'm happy to read that. Then i will update the OP & scripts in the next days and take you on the credit section. Thx very much for your windows testing.
Now the next on the to-do list is the building of this rom from source and adding Wireguard support into the kernel

dhacke said:
Yeah finally. I'm happy to read that. Then i will update the OP & scripts in the next days and take you on the credit section. Thx very much for your windows testing.
Now the next on the to-do list is the building of this rom from source and adding Wireguard support into the kernel
Click to expand...
Click to collapse
No problem i'm happy to test. unfortunately the still is an issue with texting on verizon which is what i use this phone on. the texts send but receiving them is not reliable. I tested on an att sim and it didn't have an issue so it's something on verizon's end.

[DEV][WIP] brcmfmac wifi driver & qcwcn libs for MSM8974-based devices like Sony Shinano

The intention behind this thread is to share some experience of a little project where I try to migrate the Sony Xperia Shinano devices (based on Qualcomm MSM8974 chipset with a Broadcom BCM4339 wifi/bluetooth chip) from the old bcmdhd wifi driver to a close-to-mainline brcmfmac driver. I want to share the progress and status here, and maybe get some hints. It is work in progress, and for sure it still contains some mistakes - I haven't done something like this before and am still learning.
Why?
The Shinano devices are still maintained by the LineageOS, and some devices are currently on the official LineageOS 17.1 stream.
The kernel however is terribly outdated, based on msm-3.4
There are some wifi issues with all LineageOS-based ROMs since years, like weak 5GHz connections and non-working wifi in some countries. There are some hacks around that, but they work (afaik) by practically disabling the kernel-level regulatory system by e.g. setting a static country code like "DE".
I am curious if we can improve that by updating the kernel drivers and network/wifi components, and maybe also the firmware (to the latest release available from Broadcom, 6.37.34.43 ?) . I got the ideas from Sonyxperiadev/Loire (+ related platform config), the Linux Backport Project and other MSM8974 based devices.
Working so far:
Did a few tests only so far, STA with WPA2 and p2p (hotspot) seem to work
Wifi connection is stable on 2,4GHz on 00 world regulatory domain (tested on a Z3 and a Z3c)
5GHz manually setting a country code (could only test DE)
Switching countries / setting new regulatory domains is now working, too
Download speed looks OK to me, in my case at least better than before Download >60MBit, Upload >30 Mbit on some initial tests.
Not working yet:
WifiHAL (qcom-caf) does not work correctly. This may create multiple issues, tbd.
Connection bandwidth seems to be not reported correctly
I don't know if wowlan works (interrupts working?)
Stability: After 1-2 days without reboot wifi sometimes crashes but immediately reconnects. Reason not yet understood.
Patches & Picks
Kernel:
backported and configured brcmfmac, cfg800211 wireless configuration API and wireless network stack from linux-stable v5.8 by adopting the compatibility patches from the linux backporting project.
updated Shinano device tree, updated Z3, Z3c and Z2 (Z2 test needed!) defconfigs (unset bcmdhd and enabled brcmfmac) and removed board-sony_shinano-wifi.o in the arch-msm makefile
Note: the backported drivers and compatibility-patches are located in a separate backports/ subdirectory
Sorry, this is work in progress and contains some hacks, to be cleaned up later
--> https://github.com/LineageOS/androi...1...Tom1000:lineage-17.1-driver-backport-v5.8
Vendor blobs / device z3(c): removed proprietary firmware and replaced that by publicly available firmware for bcm4339 on linux-firmware.git
z3c --> https://github.com/LineageOS/androi.../lineage-17.1...Tom1000:lineage-17.1-brcmfmac
z3 --> https://github.com/LineageOS/androi.../lineage-17.1...Tom1000:lineage-17.1-brcmfmac
Shinano-common: Use qcwcn instead of bcmdhd WLAN device, serve wpa_supplicant_overlay.conf
--> https://github.com/LineageOS/androi.../lineage-17.1...Tom1000:lineage-17.1-brcmfmac
msm8974-common: raise wpa_supplicant version (unknown if we need that) and update sysfs node for MAC address
--> https://github.com/LineageOS/androi.../lineage-17.1...Tom1000:lineage-17.1-brcmfmac

As a follow up, the driver seems to work quite stable already. I still have issues with nl80211 private commands, as a mainline brcmfmac does not seem to accept command strings passed via a libnl control socket like this:
qcwcn/wpa_supplicant_8_lib/driver_cmd_nl80211.c
@vknecht : I've seen your backporting work for the Xperia X. How does this work for Loire with SODP? Does e.g. a "set country code request" work for you, and if so, can you give me a hint?

I need some feedback from people with a Z3/Z3c/Z3Dual to see if the new builds work in affected countries, where 5GHz wifi is not working on current custom ROMs like e.g. LineageOS 17.1. I would appreciate if you test one of the builds below and send me a full log.
WARNING: The following builds are for debugging purpose only. Do not use them as a daily driver, as they have SELinux disabled and create excessive log entries. This ROM is not stable, some features are not yet implemented.
Xperia Z3 (D6603):
lineage-17.1-20201227-UNOFFICIAL-z3.zip
drive.google.com
Xperia Z3c (D5803):
lineage-17.1-20201227-UNOFFICIAL-z3c.zip
drive.google.com
Xperia Z3Dual (D6633) Update 10Jan2021:
lineage-17.1-20210110-UNOFFICIAL-z3dual.zip
drive.google.com
Z3Dual build has SELinux enabled already
If possible, please follow these steps:
Install ROM with TWRP for Android 10 or Lineage Recovery for 17.1
If possible, factory reset the device. Be sure to get rid of all former Magisk modules which try to set country codes etc. (if applicable).
Make sure a a local SIM card is inserted.
Boot the device. Enable mobile data and enable wifi. Connect to a 5GHz capable access point or router.
Optional: Increase log buffer size. This may be required as the kernel is set to verbose logging, creating large logfiles. You can do this via settings/developer options or via adb:
adb logcat -G 8M
Get close to the access point or router, so that the device would prefer 5GHz over 2.4GHz.
Reboot the device and let wifi connect. Check if device uses a 5Ghz connection. (Ignore bandwith / speed for now.)
Create a logfile, e.g. with this command via adb:
adb shell logcat -d -b all > mylog.log
The logfile may contain private information, so I recommend not to post them public. Together with the ligfile I would like to know
a) Wifi 5GHz working?
b) The country in which you have tested this.

nice work bro.
i live in iran and in this build my Z3 Dual detects wifi networks while the sim card is also connected.
but in 10 Jan 2021 update my phone can't detect my router's wifi unfortunately while the previous build could do it without problems.
hotspot turns on on both 2.4GHz and 5GHz.
in this new build cellular network and data are working.

Thanks @TheShadowOfAGhost20 !
Can you please run a root shell (E.g. by connecting via ADB, run adb root, then adb shell) and then
$> iw wlan0 scan → scan for networks
and then look if your access point is found?
Furthermore, can you please check which WiFi channel this particular router ist set to, and if possible the bandwidth?

Mr.Tom_Tom said:
Thanks @TheShadowOfAGhost20 !
Can you connect via ADB, run adb shell and then
$> iw wlan0 scan → scan for networks
and then look if your access point is found?
Furthermore, can you please check which WiFi channel this particular router ist set to, and if possible the bandwidth?
Click to expand...
Click to collapse
i did that but got this error: "/system/bin/sh: iw: inaccessible or not found"
but i found the cause: my wifi channel was set to 12. i changed it and then got detected!

TheShadowOfAGhost20 said:
i did that but got this error: "/system/bin/sh: iw: inaccessible or not found"
Click to expand...
Click to collapse
Sorry I forgot to write that you have to do this as root, I edited the post accordingly.
TheShadowOfAGhost20 said:
i found the cause: my wifi channel was set to 12. i changed it and then got detected!
Click to expand...
Click to collapse
Tha sounds reasonable. However, Channel 12 should be usable in IR.

Mr.Tom_Tom said:
Sorry I forgot to write that you have to do this as root, I edited the post accordingly.
Tha sounds reasonable. However, Channel 12 should be usable in IR.
Click to expand...
Click to collapse
channel 13 has detection problem too. the others are OK

.sorry erroneous post

New builds​Feedbacks have been positive so far, so here are some updated builds.
Lineage Sources* as of 20 March 2021
Kernel sources* based on Linux 3.4.113 with backported wifi from 5.8.18 plus cherry-pick of the following changes:
bluetooth: fixed #ifdef'ed PM callbacks ("BTLowPower" wakelock) 50f16d16b32871c5ce97b029e68692008c848bb2
SELinux enforcing
Build as userdebug, normal loglevels
* For links to sources see 1st post. Z3Dual does not have official Lineage17.1 sources yet, bringup is in progress.
Xperia Z3 (D6603):
HiDrive
hidrive.ionos.com
md5: d7aaf1fea120df3e2aad10b3a2d32226
Xperia Z3c (D5803):
HiDrive
hidrive.ionos.com
md5: 456ff87441c3a63e8dc8c7a8d03bdf39
Xperia Z3Dual (D6633):
HiDrive
hidrive.ionos.com
md5: 1848681c82d608f3212f1ace621327cb
As always, feedback is welcome.

Has anyone found a bug/installed this latest build yet? lineage-17.1-20210320-UNOFFICIAL-z3dual
Finding this super stable.. The only thing that does not work for me is the advanced boot recovery that goes back into system, But that's a known issue.

Mr.Tom_Tom said:
New builds​Feedbacks have been positive so far, so here are some updated builds.
Lineage Sources* as of 20 March 2021
Kernel sources* based on Linux 3.4.113 with backported wifi from 5.8.18 plus cherry-pick of the following changes:
bluetooth: fixed #ifdef'ed PM callbacks ("BTLowPower" wakelock) 50f16d16b32871c5ce97b029e68692008c848bb2
SELinux enforcing
Build as userdebug, normal loglevels
* For links to sources see 1st post. Z3Dual does not have official Lineage17.1 sources yet, bringup is in progress.
Xperia Z3 (D6603):
HiDrive
hidrive.ionos.com
md5: d7aaf1fea120df3e2aad10b3a2d32226
Xperia Z3c (D5803):
HiDrive
hidrive.ionos.com
md5: 456ff87441c3a63e8dc8c7a8d03bdf39
Xperia Z3Dual (D6633):
HiDrive
hidrive.ionos.com
md5: 1848681c82d608f3212f1ace621327cb
As always, feedback is welcome.
Click to expand...
Click to collapse
hi mr.tom. it's perfect as always, found no bug except wifi signal power, it's weak compared to stock roms but there was no difference in speeds. maybe it's because of wifi icon that shows little weaker signal.
and about overheating: i didn't test this build for long but while working with it i have noticed that my device is cooler than previous builds, maybe it's because of this new kernel.
i have recorded 4k for about 7 minutes then my phone rebooted i think that was because of too much heat, then i've reinstalled stock rom, however, stock rom's camera won't let me record much and the app shuts down because of heat, so i can't find out if stock rom can record 4k at least without rebooting.
i need to test this build for more time i hope the heating is now gone
and one question: can you port cyberian camera mod for these roms? or is that possible?

netwave said:
Has anyone found a bug/installed this latest build yet? lineage-17.1-20210320-UNOFFICIAL-z3dual
Finding this super stable.. The only thing that does not work for me is the advanced boot recovery that goes back into system, But that's a known issue.
Click to expand...
Click to collapse
lineage os recoveries have these problems yet, there's no fix for that, only the developer can fix it. currently the twrp works if you flash it to FOTAKernel partition but i think the twrp is useless because it doesn't install these builds.

Surely better to do: fastboot boot recovery-20201012-TESTING-z3dual.img rather than a "flash" recovery. What would be the point in flashing a recovery if its not working.

Hey
Thanks @Mr.Tom_Tom for new build and @TheShadowOfAGhost20 for testing dev builds!
today i installed the new release
but i have some problems with recovery and boot
after installing Lineage i cannot boot to recovery again
i tried adb, android advanced boot options and "fastboot boot image.img"
none of them taken me to recovery mode
so i needed to install Magisk , OpenGApps , and rom itself with adb sideload and reboot to system because i can't boot to recovery again
i'm now installing my apps for daily usage testing - i need about one or two week to test and use and see if anything is wrong or not
for now WiFi problem is gone , i have full wifi access and both sims antenna
again , thanks to everyone puts effort on this project (and sorry for bad English)
i will update this post if i found anything

navidmafi said:
today i installed the new release
but i have some problems with recovery and boot
after installing Lineage i cannot boot to recovery again
i tried adb, android advanced boot options and "fastboot boot image.img"
none of them taken me to recovery mode
Click to expand...
Click to collapse
If your going to settings\system\developer options\advanced restart\power\restart recovery , Forget it! this method doesn't work for now, & will only boot you back into Lineage. It's an issue that hopefully get's fixed in the future.
But here's a better way of entering recovery without having to flash it...
Check all your drivers are installed correctly & make sure you have the correct recovery to hand.
Here's what I Command:
adb devices
adb reboot bootloader
fastboot devices
fastboot boot recovery-20201012-TESTING-z3dual.img
Good luck!

Hey again
Thanks to @netwave i can now boot to recovery without problems by going to fastboot from adb , and booting image directly by "fastboot boot"
while using devices after installing new release , i have a problem with WiFi connectivity
when i lock the screen by power button , the wifi disconnects
for example i use whatsapp a lot and when screen is locked wifi is not connected
i checked power settings - and even set the battery profile to "Quick" (and battery saver is off) but it did not help
is this a bug or a feature?

navidmafi said:
Hey again
Thanks to @netwave i can now boot to recovery without problems by going to fastboot from adb , and booting image directly by "fastboot boot"
while using devices after installing new release , i have a problem with WiFi connectivity
when i lock the screen by power button , the wifi disconnects
for example i use whatsapp a lot and when screen is locked wifi is not connected
i checked power settings - and even set the battery profile to "Quick" (and battery saver is off) but it did not help
is this a bug or a feature?
Click to expand...
Click to collapse
Have you tried without Magisk installed? Don't use v22.0 what ever you do as it disables WiFi

Ow
I'm using Magisk and it is version 22.0
and even root not works
should i reflash ?
Edit : Ok i'm flashing again now

navidmafi said:
Ow
I'm using Magisk and it is version 22.0
and even root not works
should i reflash ?
Click to expand...
Click to collapse
Install the Magisk uninstall.zip from recovery
when your back in Lineage your still have a disabled WiFi as Magisk does not uninstall correctly.
So Install the original boot extracted from the Lineage.zip to get things working again.
- adb devices
- adb reboot bootloader
- fastboot devices
- fastboot flash boot boot.img
- fastboot reboot
Then your be sorted.