This is my first time looking to update km the P7P. Currently running the November stable. Any chance I can update to QPR1 without wiping?
How To Guide April 17, 2024 AP1A.240405.002.B1 Japan? - April 2, 2024 AP1A.240405.002 Global - Unlock bootloader / Root Pixel 7 Pro [Cheetah] / SafetyNet
- Thread starter roirraW "edor" ehT
- Start date
-
- Tags
- bootloader pixel 7 pixel 7 pro root
Yes. The build released today is the December/QPR1 stable release, so for those on the stable builds is just a normal monthly security update, albeit a big one because it includes the QPR1 stable stuff. No wipe is needed.
Quick process from Nov to Dec update.
Unhide magisk
Patch init_boot
Edit flash_nowipe with "fastboot --disable-verity --disable-verification update image-cheetah-tq1a.221205.011.zip"
Flash no_wipe
fastboot flash init_boot m_init_boot.img
Unhide magisk
Patch init_boot
Edit flash_nowipe with "fastboot --disable-verity --disable-verification update image-cheetah-tq1a.221205.011.zip"
Flash no_wipe
fastboot flash init_boot m_init_boot.img
It's because you are rooted. Flash the stock init_boot.img to unroot and try again.
Or flash the factory image, use Android Flash Tool or Pixel Flasher. You can even sideload the full OTA image.
This was literally just answered.
If I am hoping for a miracle that Verizon gets bootloader unlocked. Is it ok if I take ota updates right now or no?
EtherealRemnant
Senior Member
It's not worth holding back your device in hopes a bootloader exploit will be found. It is extremely unlikely to happen.
I see in the release notes it mentions fixes that could pertain to the scrolling issues. anyone got any feedback on that yet?
Learning about Pixel OTAs + retain root.
* Unhide Magisk + disable modules
* Flash stock init_boot.img
* OTA or OTA side load
* Re-patch / flash init_boot.img
Question on side load. Google says to check System update before side loading?
I'm still on Oct - Pixel took it upon itself to start downloaded and I paused it.
Upon reviewing it shows resume...without any build info which I find annoying - pretty sure wants to update to Nov. It OK to sideload OTA in this paused state?
Which leads my 2nd question - is it that OTA via phone always incremental / delta. IE I need Nov OTA before Dec. 2 separate updates in this case?
But side load OTAs are full so one can jump to latest release via single ota side load?
I'm kinda leaning toward only dealing update / re-root quarterly so prefer the single update. Would also like to know how to block OTA check / auto download. Anything native or can I block with afwall+? (Auto updates was disabled in dev options but it still began downloading anyway)
Lastly will safeynet fixes periodically get broken with OTAs?
Thanks
* Unhide Magisk + disable modules
* Flash stock init_boot.img
* OTA or OTA side load
* Re-patch / flash init_boot.img
Question on side load. Google says to check System update before side loading?
I'm still on Oct - Pixel took it upon itself to start downloaded and I paused it.
Upon reviewing it shows resume...without any build info which I find annoying - pretty sure wants to update to Nov. It OK to sideload OTA in this paused state?
Which leads my 2nd question - is it that OTA via phone always incremental / delta. IE I need Nov OTA before Dec. 2 separate updates in this case?
But side load OTAs are full so one can jump to latest release via single ota side load?
I'm kinda leaning toward only dealing update / re-root quarterly so prefer the single update. Would also like to know how to block OTA check / auto download. Anything native or can I block with afwall+? (Auto updates was disabled in dev options but it still began downloading anyway)
Lastly will safeynet fixes periodically get broken with OTAs?
Thanks
Last edited:
I'm trying to run flash-all.sh but receiving this error on the Mac:
Code:
-bash: flash-all: command not foundI have everything in the platform-tools folder. init_boot.img is patched and ready to go.
I just need to run flash-all.sh.
One outstanding question from the instructions: What does
Code:
Apply Magisk Stable to it.Or do I simply flash init_boot after flash-all.sh is done?
UPDATE:
Used the Android Flash Tool to flash the update and then fastboot flash for init_boot. Booted, re-enabled Magisk, and everything's back to normal. Didn't have to reinstall Magisk.
I also learned I can't use "fastboot", needed to use "./fastboot", even thought I already have "platform-tools" in my PATH and I was already in the same directory.
Last edited:
Is it just me or I can't seem to find the new Security& Privacy hub, and the Google One VPN is still not activated after the December update? Maybe it has to do with the safetynet module in magisk?
It's not just you. Could be we need a server side update, a Google Play System update or the like. Doesn't have anything to do with the safetynet mod b/c I'm not using that.
EtherealRemnant
Senior Member
It sure feels like this update is much smoother and I had no complaints about the smoothness of the last one really. Just seems even more responsive. I wonder if they're boosting the CPU cores sooner? I'll have to watch the battery for the next week or so.
I turned on the AOD to see and it seems to get stuck on a higher brightness after getting a notification so I turned it back off. It's still not working the way it used to here where you could have always on turned off but pick up your phone and it would go to the AOD interface, it's still only sporadically showing the AOD when gently moving the phone around, still goes to the lock screen if you pick it up or tap it. This is one of the only things I miss from my OnePlus is how nice their AOD was. Incoming text messages would show up a full preview of only the text on an otherwise turned off screen. The Pixel adds a notification to the AOD but it doesn't expand it, so you have to interact with the screen anyway which kicks it to the lock screen before you can even expand the incoming message...
I turned on the AOD to see and it seems to get stuck on a higher brightness after getting a notification so I turned it back off. It's still not working the way it used to here where you could have always on turned off but pick up your phone and it would go to the AOD interface, it's still only sporadically showing the AOD when gently moving the phone around, still goes to the lock screen if you pick it up or tap it. This is one of the only things I miss from my OnePlus is how nice their AOD was. Incoming text messages would show up a full preview of only the text on an otherwise turned off screen. The Pixel adds a notification to the AOD but it doesn't expand it, so you have to interact with the screen anyway which kicks it to the lock screen before you can even expand the incoming message...
Last edited:
EtherealRemnant
Senior Member
Yes because it will reboot to recovery and tell you that you have to wipe.
My Pixel 7 is the first phone I've run rooted since my OnePlus 6T on Android 9. It appears the process to OTA update has changed since the last time I did it a few years ago. If I follow the steps in post #2 of this thread to update (running modified flash-all.bat w/ full factory image, patching the init_boot.img in Magisk, flashing patched .img), will this automatically put the new images on the inactive slot then switch it to active? Or do I need to manually switch slots first then run flash-all.bat?
Similar threads
- Poll
Top Liked Posts
-
3For what it's worth, I've seen a couple of people get the .B1 OTA update and both were in Japan.
-
53Platform-Tools is updated to 35.0.1:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for...
developer.android.com
3
Hello,
I've done the test. I've hidden the home bar pill with Pixel Expert, and Circle to Search still appear when I press the very bottom zone without the pill3 -
70Pixel 7 Pro [Cheetah]
April 17, 2024:
There's a new build, but it doesn't indicate what it's for as far as for particular carriers, or what, so I would still assume the original AP1A.240405.002 (not .B1) is the April "Global" (non-carrier specific) firmware.
Android Security Bulletins | Android Open Source Project
source.android.com
Here there be dragons.
I am not responsible for anything at all. 
VERY IMPORTANT - On the Pixel 7/Pro, we use Magisk to patch
Thanks to @edcsxz, @Lughnasadh, and @AndyYan for news about that and confirming it.init_boot.img, NOT boot.img AND we flash the patched init_boot to the init_boot partition - do not flash it to the boot partition.
Moved @mariusnoor's provided zero-day OTA.zip to Post #8 - Old news from the OP.
INDEX:
- Post #2 - Unlocking Bootloader / Rooting / Updating | SafetyNet | ADB/Fastboot & Windows USB Drivers:
- How to Root the first time / aka How to unlock the Bootloader
- Unlocking Bootloader (required in order to root)
- How to update each month (and also how to root)
[requires an unlocked bootloader for updating via this Factory Image / Android Flash Tool method]- Factory Image / Android Flash Tool method(requires an unlocked bootloader)
- OPTIONAL: If you want to flash both slots, after this first time, then after do the following
- Full OTA Zip method
- Factory Image / Android Flash Tool method(requires an unlocked bootloader)
- SafetyNet
- Optional steps when updating - flashing custom kernels
- The two schools of thought on disabling Verity and Verification
- ADB/Fastboot and Windows USB Drivers - direct download links and the most recent changelog
- Post #3 - Other, most important resources:
- A list of other important apps
- TWRP [not made for the Pixel 7 (or 6) Pro yet - will update when or if ever it has - don't hold your breath]
- Factory Images (requires an unlocked bootloader)
- Full OTA Images(doesn't require an unlocked bootloader - you can ask questions in this thread, but I won't be providing the steps necessary, as I always use the factory image)
- @mariusnoor's provided official URL to download the zero-day OTA to
TD1A.220804.031.
- @mariusnoor's provided official URL to download the zero-day OTA to
- Check warranty status
Official Google Pixel Update and Software Repair(reported as of January 23, 2022 to still not be updated for the Pixel 6/Pro - no idea if it has yet now, or if it will be for the 7/Pro)- Official Google Pixel Install fingerprint calibration software (also available at the bottom of the Update and Software Repair page above) - I believe this is only helpful if you've replaced the screen - if it's anything like the Pixel 6 Pro: if you have the screen replaced, then you *must* have the fingerprint reader replaced as well.
- Find problem apps, Magisk, and LSposed Modules by (three different methods)
- Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you do not have to manually unlock the bootloader - their site will do that on its own)
- How to determine if you already have Verity and Verification disabled (required for custom kernels for now)
- How to unroot
- Post #4 - Build ID definitions
- Post #5 - Blank
- Post #6 - Regarding P7P 5G model numbers and capabilities, and how to determine your hardware version
- Post #7 - My personal advice for how to get your device back up and running as you had it before a factory reset
- Post #8 - Old news from the OP
Thank you to the following users who have all contributed greatly to my knowledge of Pixels since I came back to XDA a year ago after a few years of mostly inactivity. Apologies if I miss anybody. In alphabetical order:
47Unlocking Bootloader / Rooting / Updating | SafetyNet | ADB/Fastboot & Windows USB Drivers
Unlocking Bootloader / Rooting / Updating:
How to Root the first time / aka How to unlock the Bootloader:
Unlocking the bootloader will factory reset your device. There is no way around this. I highly suggest never re-locking your bootloader once you unlock it. If you do ever re-lock the bootloader, only do so after restoring the phone to 100% stock by using the latest Pixel 7 Pro Factory Image or Official Google Android Flash Tool.
Verizon variants:
T-Mobile and AT&T variants:
The direct-from-Google (or other retailers who aren't U.S. Carriers), the factory Carrier Unlocked Pixels:
The rest of the world's carriers:
Other than trying the things I mentioned above, there is nothing else that anyone on XDA can do to help get OEM unlocking to be ungrayed.
Unlocking Bootloader (required in order to root)
NOTE that as @Lughnasadh has previously found and reported, both the factory image method using Flash-All.Bat, and the Official Google Android Flash Tool (webpage) cause only the most recently flashed slot to boot. If you want both slots to be bootable, you want the Full OTA Zip method a couple of sections down in this post.
How to update each month (and also how to root)
[requires an unlocked bootloader for updating via this factory image method, and for the Full OTA method if you're rooting]
- These three instructions only apply if you're already rooted and updating from one firmware version to another:
- Made sure all Magisk Modules have been updated.
- Disable all Magisk Modules.
- UNhide Magisk!
- If you are going to use the Official Google Android Flash Tool, then skip the steps I indicate with FAB(Flash-All.Bat).
- If using the Android Flash Tool to update/dirty flash, you should have the following items notselected:
- Deselect Wipe
- Deselect Force Flash all partitions (which will also wipe)
- Deselect re-lock bootloader
- If using the Android Flash Tool to update/dirty flash, you should have the following items notselected:
- Always use the latest ADB/Fastboot (SDK Platform Tools) and Windows USB Drivers.
- Unzip the Platform Tools.
- At this point, if you're going to use the Full OTA Zip method, go to the:
Full OTA Zip method
section below the next section.
Full OTA Zip method:
SafetyNet:
You do not need more than one of these:
- daboynb's PlayIntegrityNEXT (fork of @chiteroman's)
- @osm0sis PlayIntegrityFork (fork of @chiteroman's)
- @chiteroman's [MODULE] Play Integrity Fix (SafetyNet fix)
-
- @Displax Universal SafetyNet Fix Mod on XDA.
- @kdrag0n's Official Universal SafetyNet Fix released
- Also for reference, @simplepinoi177's thread How to search & find your own fingerprints [noob friendly]: A Comprehensive Guide w/ tips & Discussion for Complete Noobs (from one)
- Launch the Magisk app.
- Go to Magisk's Settings (Gear in top right).
- Click
Hide the Magisk app. - When you hide it, you'll have the optional opportunity to change the Magisk app's name to whatever you wish. It doesn't have to be complex to fool apps that check for Magisk.
- Important: When you have the Magisk app hidden or renamed, you can accidentally install a new copy of Magisk. This situation won't work at all - neither copy of Magisk will work with two installed. This is one reason why I don't completely hide Magisk, so I can tell it's installed because I have it renamed as something easily recognizable.
- Back to the Magisk app's Settings...
- Click
Systemless hosts. This adds a Magisk Module to Magisk, which you can verify in a later step. - Toggle
Zygiskon. - Toggle
Enforce DenyListon. - Click
Configure DenyList.- Add every app that you want to explicitly deny root and the existence of root.
- You can click the 3-dot menu and choose the options to display system and/or OS apps, if necessary.
- Note that for many apps, it is not enough to click the single checkmark to the right of the app name in this list. For many but not all apps, you should click on the app name and you'll see it expand to two or more entries, each with its own toggles. In this expanded state, you can now check the single top checkbox beside the main app name and it'll toggle all individual sub-entries.
- Some apps add new entries to this list from time to time, so if you find that an app used to work for you when rooted and doesn't now, check this list again and look for the entries that aren't fully checked. There will be an incomplete horizontal line above the apps that don't have all of their sub-entries toggled.
- You can use the Search button at the top of this list to find specific apps quickly.
- The most common apps you should definitely fully check in this list are:
IMPORTANT - There are some things, such as
Google Play Serviceswhich it's fine to add to the DenyList, but it's perfectly normal when used in combination with the Universal SafetyNet Fix (USNF) that it is back to being unchecked the next time you visit the DenyList. Since USNF takes care of Google Play Services, you don't even have to add it to the DenyList in the first place.- Google Play Store
- Google Services Framework
- Google Play Protect Service
- Wallet
- GPay
- Any banking apps.
- Any streaming apps that use DRM.
- Any 2FA apps, especially those for work.
- Some of those Google apps might not need denying, but it doesn't hurt to deny them.
- Any time you toggle more entries in this list, it may be necessary to reboot the phone for it to take effect.
- Click
- From the main screen in the Magisk app, go to
Modulesat the bottom. - Confirm that the
Systemless hostsMagisk Module is added to this list, and enabled. - Install the appropriate Magisk Module: Universal SafetyNet Fix referenced above these numbered instructions.
- Reboot.
-
The Play Integrity pop-up that appears should say:
[MEETS_BASIC_INTEGRITY, MEETS_DEVICE_INTEGRITY]
- Sometimes, clearing app cache and/or data for apps like the Google Play Store, GPay, Wallet and others (and then rebooting) after these steps may help pass SafetyNet as well.
-
- See @V0latyle's explanation (and further linked post) for why we can't achieve
STRONG_INTEGRITYwith an unlocked bootloader. - See @V0latyle's [DISCUSSION] Play Integrity API regarding why SafetyNet, per se, is actually defunct and replaced with Play Integrity - and New Official Universal SafetyNet Fix released by @kdrag0n v2.4.0 referenced in the steps above takes care of the latter.
Optional steps when updating - flashing custom kernels:
IF you forget to disable Verity and Verification:
My own words:
If you forget to disable Verity and Verification, then if you don't actually try to boot the phone, you can disable them and no factory reset will be required.
If you forget to disable them, and you do try to boot the phone, then yes, you'll have to factory reset.
Note that disabling or not disabling them doesn't actually wipe your device, no matter what. It's a small difference, but rather, they corrupt (or report as corrupt) your device until you wipe it manually (although that's not the only cause of corruption messages, and in at least one other case, a different solution is required).
I have chosen to never disable them, but that's my personal preference. I have one or two accidents a year anyway where I forget some step on my phone, without having to worry about disabling them.
I am hoping that the method that has been found recently on the Pixel 7 Pro, to not need to disable them for custom kernels that implement the fix, will apply to the Pixel 7 Pro, too. If not, then I won't be using custom kernels. Nothing against anyone at all, especially the Developers. I'm just too clumsy.
ADB/Fastboot & Windows USB Drivers:
25Other, most important resources
A list of other important apps: - be sure to thank the respective OPs:
- OpenHashTab for Windows
- Hash Checker for Android
- Here's the Magisk section of XDA's forums, for rooting. Magisk on GitHub.
- @kevin@TeslaCoil's section for Nova Launcher / Nova Launcher Prime - been using this since early 2012!
- @capntrips' thread [DEV] Kernel Flasher
- [KERNEL] CleanSlate |S2S|AdBlock|VIB|BatterySvr - Thanks @tbalden!
- [Kernel] [Android Stable]Kirisakura for Pixel 7/Pro aka "Pantah" - thanks @Freak07!
- [KERNEL]Despair Kernel - Thanks @DespairFactor!
- Multi Timer StopWatch - this multiple timer app is the bomb. Got widgets, customization like crazy, you name it.
- See my review with screenshots about Multi Timer StopWatch here.
- @Chainfire's thread [APP][5.0+][2020.12.22] CF.lumen v3.74 - I used to use this app to enable my phones to go extra dim before Android developed the better native capability for that, and the app has been confirmed to work on the Pixel 7 Pro for color control, too
- @jorrik98's thread [Themes / Apps / Mods] Better Internet Tiles - Bring back Wi-Fi and mobile data toggles! (non-root)
- @VR25's thread Advanced Charging Controller (ACC)
- CrazyBoyFeng's ACC Settings - my preferred lately
- OR
- MatteCarra's AccA (Advanced Charging Controller App)
- @ayush.gl's thread LSPosed Xposed Framework [8.1-13.0]. Simple Magisk Module
- @siavash79 and @Typhus_'s thread [MOD][Xposed+Magisk][14 Compatible] Pixel Xpert - System modifications for Pixel phones 12+. This is a big one for me, personally.
- Alongside Pixel Xpert above, since it removed some Theming options, I'm using and recommend the following:
- Mahmud0808's Iconify on GitHub
- OR
- @DanGLES3's thread Fullscreen/Immersive Gesture Tweaks for Android 10-14 (most up-to-date version available at the GitHub link in his OP). You configure it while flashing the module using the volume keys. I choose:
- - (Immersive)
- + (Hide keyboard buttons - Back/Switch keyboard)
- + (Reduce the size of the keyboard bar)
- + (Pick the gesture sensitivity - Low/Module Default)
- + (Enable Gcam fix)
- - (NOT Wish to disable the back gesture)
- @Osanosa's [APP][8.0+]Themed Project - I used this specifically just for the Status Bar IconPacks it includes. I prefer "Kai" for the lined Wi-Fi and Mobile Data strength indicators, and the Bluetooth connected icon, but there are a handful of others available.
- The Play Store Project Themer · Android 12⁺, I used this for QuickSetting Panel tile shapes, customized Brightness Slider, Notification style, and 100% opacity. This app is a paid app, I paid for it in 2022 just to support the developer.
- @DanGLES3's thread Fullscreen/Immersive Gesture Tweaks for Android 10-14 (most up-to-date version available at the GitHub link in his OP). You configure it while flashing the module using the volume keys. I choose:
- @Quinny899's thread [APP][ROOT][11+][19/07] Classic Power Menu - Power Menu Replacement w/ Wallet, Controls on Android 11, 12, 13+
- Swift Backup
- @j4velin's thread [APP] Wallpaper Changer - been using this since mid-2011!
- @Jawomo's thread [Themes / Apps / Mods] aodNotify - Notification Light / LED - see my post in that thread here for the proper offsets to use the front camera notification circle on the Pixel 7 Pro.
- @Jawomo's thread [APP] dynamicSpot - iPhone 14 Pro Dynamic Island for android!
- @huskydg's Magisk_OverlayFS, which has the effect to make /system r/w - not compatible with Android 14 yet, as of July 7, 2023
GitHub - HuskyDG/magic_overlayfs: Make system partition become read-write (it is also possible without Magisk)
Make system partition become read-write (it is...
github.com
How to unroot
One of these two options:
- Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you do not have to manually unlock the bootloader - their site will do that on its own).
Select the options to:- Wipe
- Force flash all partitions
- Re-lock bootloader
- Flash the completely stock init_boot.img from the same firmware version that you're on:
Code:adb reboot bootloader fastboot flash init_boot init_boot.img
TWRP [not made for the Pixel 7 (or 6) Pro yet - will update when or if ever it has - don't hold your breath]
Factory Images (requires an unlocked bootloader)
Full OTA Images (doesn't require an unlocked bootloader - you can ask questions in this thread, but I won't be providing the steps necessary, as I always use the factory image)
Check warranty status - *may* reveal if a phone is refurbished, only if the phone was refurbished through Google - thanks to @Alekos for making me aware of the site.
Official Google Pixel Update and Software Repair(reported as of January 23, 2022 to still not be updated for the Pixel 6/Pro - no idea if it has yet now, or if it will be for the 7/Pro)
Official Google Pixel Install fingerprint calibration software (also available at the bottom of the Update and Software Repair page above) - I believe this is only helpful if you've replaced the screen - if it's anything like the Pixel 6 Pro: if you have the screen replaced, then you *must* have the fingerprint reader replaced as well.
Find problem apps, Magisk, and LSposed Modules by (three different methods):
- Magisk Safe Mode.
- This can be a lifesaver and keep you from having to do a restore to 100% complete stock or even from having to do a factory reset. This will deactivate all Magisk modules, and they'll remain deactivated even after you boot normally after briefly booting to safe mode. You can re-enable the Magisk modules as you wish to try to narrow down the problem if it was caused by a Magisk module. This can even get things working again after a Magisk Module wasn't finished installing and potentially causing a bootloop.
- It has been pointed out to me (thank you, @Lughnasadh!) that Google's Help Page for Find problem apps by rebooting to safe mode only gets you into System Safe Mode, not Magisk Safe Mode.
- One of the Alpha developers (I don't know which one): "Many people wait for the animation to appear before pressing keys. They are misled by the documentation into thinking that system safe mode will trigger magisk safe mode. This is wrong, the time is wrong.
For safe mode to be recognized before the module is loaded, magisk must detect keystrokes earlier than the system. If you press the key after the animation appears, you will have missed the detection of magisk and will only trigger the system safe mode. You should press and hold volume down immediately after the bootloader unlock warning, and release it after the animation appears - if you do not want to trigger the system safe mode at the same time.
Safe mode can also be triggered through prop. When the computer is powered on, long press the restart button in the power menu and click OK on the "Reboot to Safe Mode" pop-up window, and the prop will be set. If magisk and the system read this prop the next time they are powered on, they will enter safe mode. Only in this way can we guarantee that everything will be triggered. But it is not practical, or in other words, it is meaningless to save bricks."
- You can also follow @Jon8RFC's advice:
Worked for me yesterday when I accidentally tried some old version of a Magisk Module. You have to reinstall your Magisk Modules, but if you're using a third-party widget, it won't disable them like Safe mode does. - (May only be for mis-behaving LSposed modules):
Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you do not have to manually unlock the bootloader - their site will do that on its own)
How to determine if you already have Verity and Verification disabled (required for custom kernels for now)
Alternative two more manual ways of checking:I keep seeing this asked, so I added a Magisk module for it to the linked Github release. With the module installed, you can just run:
Code:su avbctl get-verity avbctl get-verification
I spent way more time debugging that I downloaded Github's HTML of theupdate-binaryscript rather than the raw file than I care to admit.
Off to bed.
22
Indeed. My MOD is a temporary solution until kdrag0n release accurate fix.
I didn't change the update channel in the module on purpose so that everyone can upgrade to the new official version automatically without any problems. - Post #2 - Unlocking Bootloader / Rooting / Updating | SafetyNet | ADB/Fastboot & Windows USB Drivers:
New posts
-
Development [ROM][UNOFFICIAL] LineageOS 21 for Xperia 1V (XQ-DQ72)
- Latest: AJHutchinson
-
How To Guide ZTE nubia Z60 Ultra flash from Chinese to global
- Latest: goDanielgo
-
