Hello everyone.
I have downgraded my z play from 7.1.1 to android 6. by just deletin the boot and gpt bin lines in the flashfile. All went well.
But my question is, can I do the security patches, or will them cause a brick in my phone ??
Miguelkf said:
Hello everyone.
I have downgraded my z play from 7.1.1 to android 6. by just deletin the boot and gpt bin lines in the flashfile. All went well.
But my question is, can I do the security patches, or will them cause a brick in my phone ??
Click to expand...
Click to collapse
Just flash MM ROM by @flashallthetime - it have dec security patches and works pretty well. But if you don't want to have hard brick - don't receive any OTA.
I just got a second hand Moto Z2 Play which is a XT1710-09 on android 7.1.1 with security patch level February 1, 2018 and reteu Software Channel with build number NPSS26.118-19-22.
It was already reset when I got it and after I done my initial setup I got a prompt to update to android 8.0, April 1, 2018, OPS27.76-12-25 but after I wait for the download to finish (tried on both wifi and mobile data) it says the update couldn't be validated and to try again.
I went ahead in the recovery and deleted cache and factory reset once again and I get the same issue. The bootloader also shows the software as being modified and not official.
Any tips ? I really wouldn't want to return the phone because I love it so far but if there's no solution I'll just have to go ahead and get my money back
Ich guess your bootloader ist unlocked? Well then you cant make ota Updates anymore, but you can Install a full rom via Fastboot.
It says oem_locked when I boot into fastboot mode :/ I was able to update to February 2019 security patch and Android 8.0.0 by using fastboot tho. Is this the latest security patch available ?
Hir0xM said:
It says oem_locked when I boot into fastboot mode :/ I was able to update to February 2019 security patch and Android 8.0.0 by using fastboot tho. Is this the latest security patch available ?
Click to expand...
Click to collapse
Yep, that's indeed the last one.
That's the one I have.
It came from openmx rom, I decided to use lineage os 17.1 everything ok except for the mods that I could not use, I decided to go to lineage os 16 to enjoy the dark mode at 100% but when updating ... I stayed in bootloop it restarted, I opted for install lineage os 17 again, and ran out of baseband I have been downloaded all the variants and I can not return the baseband, any solution?
IrvinGarcia1821 said:
It came from openmx rom, I decided to use lineage os 17.1 everything ok except for the mods that I could not use, I decided to go to lineage os 16 to enjoy the dark mode at 100% but when updating ... I stayed in bootloop it restarted, I opted for install lineage os 17 again, and ran out of baseband I have been downloaded all the variants and I can not return the baseband, any solution?
Click to expand...
Click to collapse
Stop flashing things and do not re-lock your bootloader for any reason, it doesn't fix anything. What was your original software channel?
41rw4lk said:
Stop flashing things and do not re-lock your bootloader for any reason, it doesn't fix anything. What was your original software channel?
Click to expand...
Click to collapse
ok, the only thing i remember is that it was openmx, but i already installed all the mexican roms and my baseband doesn't come back.
I have a complete backup of the system but it cannot be restored well and the moto logo does not pass, I have the following data from the recovery of the twrp.
ro.boot.bootdevice=1da4000.ufshc
ro.boot.bootloader=MBM-3.0-nash_retail-43c7c77-190920
ro.boot.veritymode=disabled
ro.boot.slot_suffix=_a
ro.boot.wifimacaddr=60:1D:91:24:0E:42,60:1D:91:24:0E:43
ro.boot.usbcontroller=a800000.dwc3
ro.boot.write_protect=0
ro.boot.powerup_reason=0x00000080
ro.boot.secure_hardware=1
ro.boot.verifiedbootstate=orange
ro.omni.device=nash
ro.omni.version=16.1.0-20191027-nash-HOMEMADE
ro.omni.version.security_patch=
ro.twrp.boot=1
ro.twrp.version=3.3.1-0
ro.vndk.lite=true
ro.vndk.version=28
ro.wifi.channels=
ro.allow.mock.location=1
ro.build.id=PQ2A.190405.003
ro.build.date=Sun Oct 27 15:17:42 UTC 2019
Double Post sorry.
What do you mean by all mexican roms? If openmx was your provider, then you need to flash the latest openmx firmware and you should generate your own flashall for the firmware. Flashalls aren't universal, so if you just grabbed one it could be possible that it isn't flashing everything you need. I can attach a flashall gen script if needed.
Hey, guys! This is my first time posting, so I apologize if my post is missing some key details or isn't of quality in some other way.
I am currently looking into installing LineageOS onto my Samsung Galaxy A7 (SM-A720S); on the LineageOS installation documentation, it said to make sure that my device was running Android Oreo (Android 8.0). Since my device had Android Pie (Android 9.0) installed, I downloaded the Android 8.0 stock ROM for my device and region from SamMobile, and I also downloaded Odin v3.14.1 (un-patched as I am using a ROM for the same region) from the XDA forums.
Furthermore, I turned on developer settings on my phone and enabled OEM unlocking and USB debugging. Attempting to flash Android 8.0 onto my device resulted in the following error message:
SW Rev. Check Fail (Bootloader) Device: 5 Binary: 3
Click to expand...
Click to collapse
From poking around in the forums, I learnt that this means there is a mismatch between the bootloader version and the binary I am trying to flash. Is there any way to either downgrade the bootloader in order to be able to flash Android 8.0 or is there some way to trick the device/odin into thinking that the Android 8.0 has a binary of 5?
I really want to try LineageOS. so I would appreciate any advice on how to work around this issue.
That was a slight oversight on my end, because there aren't many A720S users. Your pie bootloader is fine, you can flash lineage.
Too many people are trying to use firmware to make money, so I decided to release them for free!
I got them from a site that distributes them for $10.
DOWNLOAD
Password is:
Code:
https://androplus.org
How to flash:
Plug the USB Type-C cable into the port on the side
Reboot into bootloader
Extract RAW firmware zip and run flashall_AFT.cmd
You'll see "FLASH COMPLETE. RESTART!" when flashing is completed
Rebooting will open recovery, so do a Factory data reset.
Done!
(The guide is also on my blog)
The functionality of fingerprint sensor and Widevine L1 remain intact when flashing global RAW firmware on CN hardware.
How to delete HardwareStub notification:
Use my Magisk module.
You can extract boot.img from RAW firmware or payload.bin found in official OTA zip.
Good idea to create a separate thread for this, information has been spread around the forum so this makes it easy.
Thanks for sharing the firmware, more and more people should be receiving their devices so this will be useful. I think the mods should make this a sticky.
Re the magisk module for hardware stub notification - any way to get rid of the notification without having root? I will be selling my CN version of the device with WW hardware, so dont want to give the buyer a rooted phone.
I bought a 512GB global version of the device
AndroPlus said:
Too many people are trying to use firmware to make money, so I decided to release them for free!
I got them from a site that distributes them for $10.
DOWNLOAD
How to flash:
Plug the USB Type-C cable into the port on the side
Reboot into bootloader
Extract RAW firmware zip and run flashall_AFT.cmd
You'll see "FLASH COMPLETE. RESTART!" when flashing is completed
Rebooting will open recovery, so do a Factory data reset.
Done!
(The guide is also on my blog)
The functionality of fingerprint sensor and Widevine L1 remain intact when flashing global RAW firmware on CN hardware.
How to delete HardwareStub notification:
Use my Magisk module.
You can extract boot.img from RAW firmware or payload.bin found in official OTA zip.
Click to expand...
Click to collapse
One more question about your magisk module for the hwstub notification - will the fix remain if you root, flash the magisk module, and then remove magisk/root? or will it need the magisk module to be active on the phone to keep the fix?
mahdibassam said:
One more question about your magisk module for the hwstub notification - will the fix remain if you root, flash the magisk module, and then remove magisk/root? or will it need the magisk module to be active on the phone to keep the fix?
Click to expand...
Click to collapse
Notification fix works only when Magisk module is active.
Maybe there's a way to fix without root, but I don't know.
mahdibassam said:
One more question about your magisk module for the hwstub notification - will the fix remain if you root, flash the magisk module, and then remove magisk/root? or will it need the magisk module to be active on the phone to keep the fix?
Click to expand...
Click to collapse
Instead of using a Magisk module, you *might* be able to root, then use a non-invasive tool like App Manager (link below) with SU access to unflag POST_NOTIFICATION under App Ops for HW Stub and then remove root if that's what you really want. The solution should be permanent. I may be able to test it when I find some time, or you can have a go yourself and confirm. No risk of breaking anything:
App Manager - Android package manager | F-Droid - Free and Open Source Android App Repository
A full-featured open source package manager for android.
f-droid.org
Does this root the phone, if so would LSPosed and Island work? I'm planning to get the international/HK version of the 6 Pro since there's no warranty for CN models here. Or should I wait for TWRP instead?
williamcll said:
Does this root the phone, if so would LSPosed and Island work? I'm planning to get the international/HK version of the 6 Pro since there's no warranty for CN models here. Or should I wait for TWRP instead?
Click to expand...
Click to collapse
No, this guide only flash stock global ROM.
You just need to extract boot.img by unpacking raw img, then patch it in Magisk app and flash it in fastboot: fastboot flash boot magisk_patched.img
Installation
The Magic Mask for Android
topjohnwu.github.io
AndroPlus said:
No, this guide only flash stock global ROM.
You just need to extract boot.img by unpacking raw img, then patch it in Magisk app and flash it in fastboot: fastboot flash boot magisk_patched.img
Installation
The Magic Mask for Android
topjohnwu.github.io
Click to expand...
Click to collapse
Well, that's kind of useless considering the one I am going to buy has the global rom.
williamcll said:
Does this root the phone, if so would LSPosed and Island work? I'm planning to get the international/HK version of the 6 Pro since there's no warranty for CN models here. Or should I wait for TWRP instead?
Click to expand...
Click to collapse
You can root & run LSPosed on these devices with no issues. The WW (HK) version is great and it's a genuine global version which is the way to go (the only way to go if you ask me). I have the same WW-HK versions of 3 and 5 and have set up a same version 6 for someone, all rooted, running LSPosed and everything else 100% smooth. TWRP is not a must although definitely a nice to have once available for the 6.
Deleted
THANK YOU!
Code:
sed -i 's/\.\///g' * && sudo flash flashall_AFT.sh
Is what I used to run it from my linux and it worked great.
wanted to try the chinese version and see this better battery stuff
AndroPlus said:
Too many people are trying to use firmware to make money, so I decided to release them for free!
I got them from a site that distributes them for $10.
DOWNLOAD
Password is:
Code:
https://androplus.org
How to flash:
Plug the USB Type-C cable into the port on the side
Reboot into bootloader
Extract RAW firmware zip and run flashall_AFT.cmd
You'll see "FLASH COMPLETE. RESTART!" when flashing is completed
Rebooting will open recovery, so do a Factory data reset.
Done!
(The guide is also on my blog)
The functionality of fingerprint sensor and Widevine L1 remain intact when flashing global RAW firmware on CN hardware.
How to delete HardwareStub notification:
Use my Magisk module.
You can extract boot.img from RAW firmware or payload.bin found in official OTA zip.
Click to expand...
Click to collapse
Thanks!!
Could you also provide the boot.img & patched magisk boot.img from this raw file? I don't mind paying for it..
finallau said:
Thanks!!
Could you also provide the boot.img & patched magisk boot.img from this raw file? I don't mind paying for it..
Click to expand...
Click to collapse
OK, I uploaded here:
WW-AI2201-32.2810.2205.63 - Google Drive
drive.google.com
AndroPlus said:
OK, I uploaded here:
WW-AI2201-32.2810.2205.63 - Google Drive
drive.google.com
Click to expand...
Click to collapse
thanks!!
I'll donate you once i got everything working!
What people outside of cn buying the cn version don't understand is, it will probably not have the same 5g reception as the global version. A phone at that price range deserves some patience. Also you sure you have nfc on the cn hardware?
I couldn't use G Pay now because my play protection certification isn't certified after changing to WW rom running latest rom, bootloader locked & unrooted..
Safety net check all passed except for cts profile match fail..
I tried clearing data on services, play store & framework still can't get it solved..
Any solution other than using magisk/root to bypass it?
AndroPlus said:
OK, I uploaded here:
WW-AI2201-32.2810.2205.63 - Google Drive
drive.google.com
Click to expand...
Click to collapse
Just tipped you ✓
finallau said:
I couldn't use G Pay now because my play protection certification isn't certified after changing to WW rom running latest rom, bootloader locked & unrooted..
Safety net check all passed except for cts profile match fail..
I tried clearing data on services, play store & framework still can't get it solved..
Any solution other than using magisk/root to bypass it?
Click to expand...
Click to collapse
I'm thinking of buying the tencent version if everything goes well.
Did you change fingerprint to CN > WW ?
>When rooted, use ROOT EXPLORER APK
>Inside app, change MOUNT R/W to R/O.
>Navigate to the /Vendor/Factory
>Find file COUNTRY.
>Change CN to WW
It should stay permanent even after factory reset & unroot.
It worked well for me at least for my ROG Phone 2.
atsushiboy said:
I'm thinking of buying the tencent version if everything goes well.
Did you change fingerprint to CN > WW ?
>When rooted, use ROOT EXPLORER APK
>Inside app, change MOUNT R/W to R/O.
>Navigate to the /Vendor/Factory
>Find file COUNTRY.
>Change CN to WW
It should stay permanent even after factory reset & unroot.
It worked well for me at least for my ROG Phone 2.
Click to expand...
Click to collapse
Yeah I did otherwise manually update would had failed since fingerprint not changed.
I did a re-flash back from provided raw firmware it got certified again but then after I did an update & wiped data, same issue cts profile match fail...
atsushiboy said:
I'm thinking of buying the tencent version if everything goes well.
Did you change fingerprint to CN > WW ?
>When rooted, use ROOT EXPLORER APK
>Inside app, change MOUNT R/W to R/O.
>Navigate to the /Vendor/Factory
>Find file COUNTRY.
>Change CN to WW
It should stay permanent even after factory reset & unroot.
It worked well for me at least for my ROG Phone 2.
Click to expand...
Click to collapse
Just realize my fingerprint isn't WW upon checking from device info HW app. However going back the COUNTRY file in root explorer did show WW..
Any solution? I did a 2nd reflash of the WW raw firmware still no change..
Any solution?
Also, tapping "mount r/w" has no changes in ROOT explorer but I have root checker checked..