Related
I AM VERY SORRY, I THINK I AM IN THE WRONG FORUM!
Hi Guys, has anyone rooted the latest Asus Zenfone 4 Lollipop? The new OTA can be downloaded from here
http://www.asus.com/ph/supportonly/ASUS ZenFone 4/HelpDesk_Download/
Thanks in advance.
BTW. more details
Version WW_7.3.3 (Android L)
ASUS ZenFone4(T00I) software Image: V7.3.3 (Android L) for WW only*
Note1: Please make sure update software version V6.6.3 first before update to software version V7.3.3
Note2: Download the OTA file and put the file to the device root directory directly.
Please note! The listed apps below will be removed once the
Android 5.0 Lollipop upgrade is complete.
1. Battery Widget
2. Google Text-To-Speech
3. Movie Studio
Please notice that below new apps will be added in this system upgrade.
1. TripAdvisor
2. Gameloft
3. CleanMaster
4. Zinio
5. ASUS Auto-start Service Manager:
Prevent unwanted apps from automatically starting up and using RAM
Stop services immediately and prevent Android from restarting these apps again
6. ASUS Support
Add Assistance in ASUS Help
Support bug reporting mechanism?
Enable Push notification service
Add unread count badge
Add new item reminders for articles
Support Google Analytics mechanism
Please notice that some feature changes in this system upgrade.
1. Lockscreen: remove standalone wallpaper & weather info
2. Dialer/Contacts: reduce tab count from 5 to 3; remove group tab name/photo
3. InCall screen: remove inCall animation & cover
4. Quick settings/Recent app layout change
Steps of Update:
1.Check software version of your device**
2.Download device software and Update SOP (From “Manual” Item)
3.Only apply to same SKU update, Example: WW->WW, CN->CN, TW->TW.
4.Software update cannot transfer the software SKU and downgrade the software version.
5.Wrong SKU may cause update failure, please update the same SKU version only.
*How to know the device model?
Path: Settings->About-> Model number
Example: ASUS_T00I
**How to know the device software version?
Path: Settings->About-> software information->Build number
***System upgrade may cause part of data missing, please buckup your important data before system upgrading.
Root not working
Root not working, error during update install.
Subhajitdas298 said:
Root not working, error during update install.
Click to expand...
Click to collapse
Sorry dude... I do not have root myself just yet. Let's wait for other to share root..
Asus Zenfone 4 lollipop can be easily rooted using temporary cwm session for intel device method. T2 method works fine. I have tried this and it works fine.
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
As title says, anyone done it?
I had lots of troubles with my phone when I got it. ****ty battery and lag. Found a thread here and manually updated to 180, and all the problems where gone. But I have since not gotten any updates. And it says nothing in the phones update notes for the update I manually installed(Probably normal after a manual update). Just worried that now I won't get any OTA for newer updates. It's a Norwegian phone. No phones here are branded.
Hi.
EVA L09 or VIE L09 ?
I done for VIE (P9 Plus)
I followed this thread (allready for VIOE L09)
Eva L09
iaitoo said:
Eva L09
Click to expand...
Click to collapse
You are under C432 ?
Maybe update is longer to come..
Maybe you should update manualy
=>
gamingprod02 said:
FOLLOW MY INSTRUCTIONS
I already posted those instructions on another thread.
- Make sure that you're on VIE-L09C432B181
- Make sure that you have more than 60% battery
- Now make a backup from your PC with HiSuite
- Now install Firmware Finder from Play Store (link)
- Now go to the Settings -> Advanced settings ->Security -> Device administration ->> NOW activate "Unknown sources"
- Now open Firmware Finder and select your model (ex: VIE-L09C432)
- Now click on "GET FIRMWARE LIST"
- Now go to the Settings of Firmware Finder & activate "Installation via system update"
- You will see a pop up "Huawei Firmware Finder Proxy" click "DOWNLOAD ADDON"
- When download is finished, install in on your mobile & open it
- Re open settings of Firmware finder & check if "Installation via system update" activated, if not activate it for the 2nd time
-- Now on Firmware Finder and select your model as VIE-L09C432 (only if your model is this)
- Now click on "GET FIRMWARE LIST" & select first one where you see "VIE-L09C432B360" date:03.03.2017 TypeTA Size:1.334GB
- When you selected "VIE-L09C432B360" now you'll see an option "SEND FIRMWARE TO UPDATER" click on it
- Now it will automatically open a page "Firmware Finder Proxy"
- Now go to the Wi-Fi & connect to one Wi-Fi and now "Modify network" then "Show advanced options" now select "Proxy" as "Manuel"
- On write on Proxy hostname: localhost
- On write on Proxy port: 8080
- Now go to Settings -> System update & now click on "CHECK FOR UPDATES"
- Now you'll gonna see an update name "VIE-L09C432B360VIE-L09C432B360 -1430186368,00 B" don't download this one ! this one is not the correct one !
- Back to System update & you'll still this the wrong update, don't worry, click on "MENU" & click on "Download latest full package"
- Now you'll see the correct update "VIE-L09C432B360 2,39 GB" now just click on "Quick update"
- It will not download, don't worry, just go to the Wi-Fi settings and disable "Proxy"
- Go again to System update and click on pause & resume
- Wait till the end of the download & after your mobile will install automatically the update you downloaded
If you followed my instructions, it will install successfully B360.
Click to expand...
Click to collapse
Found here
I've tried that and can't get it to show me a 2+GB version. It still sticks to 1.3nGB, downloads and fails when doing the pre-install check.
Only difference is I'm on B180 not B181 (EVA-L09C432B180).
hi care app and huawei id. in hicare is operating system section, where you need to be able to sign up for nuget!
Update: Tried again. Downloaded and installed, but I lost a number of apps (camera, system update etc) and doing a reset, I'm now stuck on NRD90M test keys as a build.
What's most annoying is that the default keyboard is gone, so I can only enter text using Google voice (and that doesn't let me log in to Google) so the phone is as good as bricked until I can figure out if I want to waste time trying to side load a keyboard etc.
Can't even do a full download/restore as that fails.
What the heck happened? The advice from gamingprod02 seemed solid, but can cause big problems!
Install full b136 by dload... No choice I guess..
Enviado desde mi EVA-L09 mediante Tapatalk
Hi,
this thread aims at keeping the LineageOS 13.0 version alive for the Moto G 2015 (osprey) device with current security patches from LineageOS (branch 'cm-13.0'). The build here has already a history in this thread on XDA - it may be worth to scroll through it to find additional information.
The build has got the following features:
LineageOS 13 with current security patches
Patched for microG (see https://microg.org, signature spoofing as switchable permission)
Squid kernel for the Osprey device (own fork)
LineageOS Jelly Browser
Current Android System Webview
CMUpdater is not part of this build
Renewed CA-certificates from AOSP master branch
VoLTE (may not work in all cases!)
Current build data
Download here
AOSP tag android-6.0.1_r81
Security string 2018-06-01
Android System Webview on M66 (stable, taken from LineageOS 14.1)
Contains the fix for the KRACK attack against WPA2
Root access included (can be switched on/off in developer settings)
Unofficial microG-build as 2nd build variant
Download here
Hardened build with pre-installed microG apps. For more information, see https://lineage.microg.org/
(This is an unofficial build for LineageOS 13 f. osprey based on the work described on the project page)
Different from the 1st build, the following features apply, everything else is the same:
No root available (can be flashed separately)
Pre-installed microG apps (see lineage.microg.org page)
SQLite 'secure delete' feature enabled
Access to /proc/net blocked for user apps
Enhanced Privacy Guard (1): Switches for motion sensors and other sensors available
Enhanced Privacy Guard (2): Switches for read phone state and storage (read/write) available
Oreo backport: SET_TIME_ZONE permission restricted to system apps
Oreo backport: Access to timers in /proc restricted
Cloudflare DNS (1.1.1.1) as default fallback
Privacy-preferring default settings
Source Code links
LineageOS: https://github.com/LineageOS
Kernel: https://github.com/MSe1969/android_kernel_motorola_msm8916/tree/mse_cm13
microG patch: https://github.com/microg/android_p...aster/patches/android_frameworks_base-M.patch
microG-Build: https://github.com/lineageos4microg
local manifest: https://github.com/cm13-microG/local_manifests
hardening features: see reserved post further below
Installation instructions
YOU ARE RESPONSIBLE SOLELY YOURSELF FOR ANY ACTIONS YOU DO WITH YOUR DEVICE !!!
Please note - I won't explain any single aspect (e.g. how to install 'fastboot' on your PC or troubleshoot USB connectivity issues under Windows). Search the net and consult the search engine of your choice or look here in XDA, there is plenty information available.
Pre-Requisites
Get familiar with the hardware keys of the Motorola Moto G 2015 (osprey) device, especially how to enter fastboot mode (switch phone off hold power + volume down together for about 3 seconds) and recovery mode (in fastboot mode, switch with volume key to the reboot recovery option and select with power key)
Have fastboot and adb installed on your PC and make sure, you can connect via USB to your device in fastboot mode and via adb
Download the most current .ZIP file of this ROM and place it to your phone's internal memory or SD card
If you wish to install Google apps (GApps), please refer to the GApps section further below
An unlocked bootloader (read the warnings carefully and backup your data!
Install TWRP recovery
If you come from stock ROM and have just unlocked your boot loader, this is the next thing to do. If you have already a working custom recovery on your device, there is no necessity to replace it.
However - I recommend to use the TWRP recovery linked here. The following instructions are based on TWRP.
To install TWRP, download the TWRP.img file (Note: replace "TWRP.img" in the following instructions with the real file name) from this section to your PC, get it into 'fastboot mode', connect the device via USB to your PC and enter the following command on your PC:
Code:
fastboot flash recovery TWRP.img
Afterwards, directly boot into 'recovery mode' (see above) - I recommend not to boot the phone's Android system after having flashed TWRP. Once TWRP has been launched, you may decide to reboot your phone and install the ROM at any time later. But the first boot after flashing TWRP should be TWRP in recovery mode.
Advanced Wipe
ONLY perform the steps described here, if you come from Stock ROM or a different Custom ROM!
Boot into recovery mode. In TWRP, choose "Wipe", "Advanced" and spefify "Dalvik", "System", "Cache" and "Data" to be wiped.
Make sure NOT to wipe "Internal memory" or "SD Card". Swipe to confirm the deletion and get back into the main menu.
GApps
The following instructions only apply for the 1st variant, do not flash Gapps over the "microG build":
You do not need to install GApps, but you may wish to do so. In that case, download GApps from here and put the .ZIP also to the SD card or Internal memory of your device.
Choose ARM as platform, Android 6.0 and the flavor of your choice. I recommend "pico", as this leaves you the most freedom to only install, what you really need; you can later still install all the Google products you want and do not need to live with pre-installed Google applications you have no use for. The 'microG patch' in this ROM has no negative impact on installing Gapps.
Install the ROM
In the TWRP main menu, choose "Install". A file manager appears to let you navigate to your internal memory (path /sdcard) or your SD card (path /external_sd).
Choose the .ZIP file of this ROM and swipe to flash. If you update from a previous version of this ROM, you don't need to perform a wipe.
If you had GApps already installed before the update, there is no need to flash them again. They will be automatically restored during the flash process.
(Note: If you wish to get rid of GApps, navigate to TWRP's file manager in the Advanced section of the main menu, go to path /system/addon.d and delete the file 70-gapps.sh, before flashing the ROM update)
If you come from a different ROM (or stock firmware), make sure that you have performed the Wipe steps above.
If you wish to install GApps, select the respective .ZIP file directly afterwards, do not boot into Android before having flashed GApps. When finished flashing, return to the main menu, choose "Reboot" and then "System", which will cause your phone to boot into Lineage OS 13.0 - be patient, the first boot after flashing a new ROM takes quite long!
microG Installation
These instructions apply to the 1st 'default' variant, not the 'microG build' (which has already microG installed)
The ROM is patched for the use of microG, but it does not contain the microG system components.
The best way to obtain them is to include the microG repository into the F-Droid store as described on the microG Download page, where you will also find links for the direct download of the .apk files.
Please refer to the official installation instructions. However, there are three pieces of information, which are explained on the microG pages, but unfortunately not directly in the installation instructions, so I would like to point them out here:
Download the 'unstable' Gms Core version 0.2.4-105-... to avoid "outdated play services" warnings
The Location Provider functionality is included in Gms Core, but also available as separate application. I recommend Gms Core - however, the explanation is not included in Gms Core, but only here
To grant the signature spoofing permission, go to Settings - Apps - Advanced (the 'gear' icon) - App Permissions - Spoof package signature; it is not possible when you enter the individual app's permissions menu
Credits
Android Open Source project (AOSP)
LineageOS project
squid2 (Kernel)
microG project
XDA:DevDB Information
Osprey LineageOS 13 with microG patch, ROM for the Moto G 2015
Contributors
MSe1969
Source Code: https://github.com/cm13-microG/local_manifests
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Testing
Created 2017-10-23
Last Updated 2018-07-24
Change Log
June 20th, 2018
Announcement to discontinue the cm-13.0 builds - please visit my Lineage OS 14.1 microG thread, which continues with LineageOS 14.1
June 10th, 2018
Security string 2018-06-01
May 22nd, 2018
Security string 2018-05-01
Android System Webview M66
Cloudflare DNS as default (instead of Google)
Privacy-preferred default settings
Kernel fix for in-call sound issue
April 11th/12th, 2018
Security string 2018-04-01
Android System Webview M65
March 16th/17th, 2018
Security string 2018-03-01
Squid Kernel r22c (Oreo)
Renewed CA certificates from AOSP master branch
Bugfix of date/time reset on reboot, when no carrier sync
Bugfix in microG build: Always skip GMS page in SetupWizard
February 19th, 2018
Update after ASB merge in LineageOS 13.0
Webview now on stable M64
February 10th, 2018
Security string 2018-02-01
Squid Kernel r22c (Oreo)
Privacy Guard enhancements
Further security hardening in 2nd "microG build" variant
January 16th, 2018
Security string 2018-01-01
Squid Kernel r22 (Oreo)
System Webview switched back to M63-stable
2nd build variant "unofficial microG build"
December 21st, 2017
Security string 2017-12-01
Squid Kernel r21 (Oreo) forked
Recent Jelly build
Android System Webview 64.0.3282.30 (beta)
November 24th, 2017
Security string 2017-11-01
Squid Kernel (Nougat) forked and merged 3.10.108 updates from kernel.org
October 23rd, 2017
Fix of KRACK attacks
Security string 2017-10-01
AOSP tag 6.0.1_r81
Android System Webview updated to M64
Squid Kernel (Nougat)
- - - - - - - - - - - - - - - - - - - - - - - - - - - -
Historical entries from this thread:
September 21st, 2017
Security string 2017-09-01
AOSP tag 6.0.1_r80
Jelly updates
Fix of 'Blueborne' attack (part of Sept. security patches)
September 2nd, 2017
Security string 2017-08-01
Android System Webview updated to M60
July 14th, 2017
Security string 2017-07-01
June 14th, 2017
Security string 2017-06-01
Android System Webview updated to M59
May 28th, 2017
Replaced Gello with new LineageOS Jelly Browser
Android System Webview updated to M58
May 26th, 2017
Security string 2017-05-01
April 17th, 2017
Security string 2017-04-01
AOSP tag 6.0.1_r79
March 24th, 2017
Security string 2017-03-01
Included Kernel from cm-14.1 branch to regularly receive sec. patches
March 13th, 2017
Security string 2017-02-01
February 21st, 2017
Security string 2017-01-01
Rebranded LineageOS
Security Hardening (microG build)
Details about additional security hardening in the "microG build"
1. SQLite 'Secure Delete' feature
This sanitizes deleted data by overwriting it with zeroes, rather than having it persist within SQLite's free list.
Backport from Oreo, see https://android-review.googlesource.com/q/topic:"secure_delete"
2. Restrict SET_TIME_ZONE permission to system apps
Backport from Oreo, see here
3. Enhanced Privacy Guard (1) - Sensor permission switches
An own sensor template to control access to motion sensors (ask mode) and all other sensors (allowed by default, but can be restricted) has been implemented into the Privacy Guard. Commits: (1), (2), (3)
4. Enhanced Privacy Guard (2) - Switches for 'Read phone state' and 'Storage'
The existing AppOps to read the phone's IMEI and to control access to the SD card have been made accessible.
This is a cherry-pick of the proposed LineageOS change here
5. Restrict access to /proc/net for user apps
An adapted SELinux policy prevents user apps from accessing the /proc/net pseudo file system, which can be misused to monitor and track the phone's internet traffic. For technical backgrounds, see here. This is the main commit. For the legitimate use case of the smart phone owner him/herself monitoring the network traffic to see, what the installed apps do, the app Privacy-Friendly Network Monitorhas been bundled
6. Access to timing information in /proc restricted
To prevent side-channel attacks as described here, the respective Oreo patch has been back-ported.
7. Cloudflare (instead of Google) default DNS
Cloudflare DNS has a better privacy policy than Google Public DNS and has DNS-over-TLS and DNS-over-HTTPS. In the deafult DNS settings (as fallback) and network diagnostics, the Cloudflare DNS adresses 1.1.1.1 and 1.0.0.1 are specified as defaults (instead of Google's 8.8.8.8 and 8.8.4.4)
8. Privacy-preferred default settings
When newly installed, the below settings are defaulted, different from standard LineageOS 14.1 (all setting can be changed at any time later):
Privacy Guard is enabled on install (proposal during Setup)
Anonymous LineageOS statistics disabled (proposal during Setup)
The standard browsing app does not get the location runtime permission automatically assigned
Sweet..
Nice. Good to see this as separate post.
Every time the ambient display lights up the screen, it is in on a high brightness mode. And the moment I tap, it gets back to normal brightness. I know this could be a cm13 issue but, any way to resolve this ?
shadowbone said:
Every time the ambient display lights up the screen, it is in on a high brightness mode. And the moment I tap, it gets back to normal brightness. I know this could be a cm13 issue but, any way to resolve this ?
Click to expand...
Click to collapse
I haven't observed this behavior on my device, can you provide some more details?
MSe1969 said:
I haven't observed this behavior on my device, can you provide some more details?
Click to expand...
Click to collapse
It isn't that big a difference but perhaps I could provide you a log, if that could help.
shadowbone said:
It isn't that big a difference but perhaps I could provide you a log, if that could help.
Click to expand...
Click to collapse
Thanks - will have a look later
MSe1969 said:
Thanks - will have a look later
Click to expand...
Click to collapse
Sure thing.
Also, is this volte supported or should I flash the volte patch ? Because I can't seem to get it work. I am on the latest build.
VoLTE
As you can see in the old thread, there have been some discussions about VoLTE support (and also some attempts from my side to get it running).
Let me quickly summarize:
I have tried the VoLTE patch(es) from XDA - VoLTE menu was there but no VoLTE calls on my phone
I have tried to create a test build with the contents of those patches and also looked at what was done in cm-14.1 - same result: menu there, but no VoLTE calls (LTE symbol disappears when calling)
Got mixed feedbacks from people using the test build - works well for the ones and does not work or stops working after reboot for others . . .
LineageOS 14.1 is supposed to have VoLTE support f. osprey - same story, not on my phone (menu entry there, but *#*#4636#*#* menu and IMS status there tells VoLTE not available - tested with SIM cards from different carriers)
So I'm having trouble to get it working on my device (XT1541 16GB) at all. On my repo's at github, the msm8916 device and vendor tree have two volte branches for testing.
Any insight, advice and/or build suggestions welcome
shadowbone said:
It isn't that big a difference but perhaps I could provide you a log, if that could help.
Click to expand...
Click to collapse
dear user, could you tell me what application I can get this file (
File Type: txt 2017-10-25-14-38-27.txt), since I have some errors in the rom, thanks.
MSe1969 said:
As you can see in the old thread, there have been some discussions about VoLTE support (and also some attempts from my side to get it running).
Let me quickly summarize:
I have tried the VoLTE patch(es) from XDA - VoLTE menu was there but no VoLTE calls on my phone
I have tried to create a test build with the contents of those patches and also looked at what was done in cm-14.1 - same result: menu there, but no VoLTE calls (LTE symbol disappears when calling)
Got mixed feedbacks from people using the test build - works well for the ones and does not work or stops working after reboot for others . . .
LineageOS 14.1 is supposed to have VoLTE support f. osprey - same story, not on my phone (menu entry there, but *#*#4636#*#* menu and IMS status there tells VoLTE not available - tested with SIM cards from different carriers)
So I'm having trouble to get it working on my device (XT1541 16GB) at all. On my repo's at github, the msm8916 device and vendor tree have two volte branches for testing.
Any insight, advice and/or build suggestions welcome
Click to expand...
Click to collapse
You could get some help from this post.. check by integrating this patch. https://forum.xda-developers.com/2015-moto-g/themes-apps/osprey-volte-patch-android-n-roms-t3527635
Edit - post added
Erick_Summer said:
dear user, could you tell me what application I can get this file (
File Type: txt 2017-10-25-14-38-27.txt), since I have some errors in the rom, thanks.
Click to expand...
Click to collapse
Well, if you meant taking a log, there are plenty. The one I used is 'matlog'. You can get it from playstore.
rahul9999 said:
You could get some help from this post.. check by integrating this patch. https://forum.xda-developers.com/2015-moto-g/themes-apps/osprey-volte-patch-android-n-roms-t3527635
Edit - post added
Click to expand...
Click to collapse
I used this post and its patches always as a base for my test builds. Tried now the most current MM patch , which was uploaded in October - same result, does not work on my device.
shadowbone said:
It isn't that big a difference but perhaps I could provide you a log, if that could help.
Click to expand...
Click to collapse
Hi, haven't really noticed anything unusual in the log, I also use afwall and Xprivacy. Only noticed you use a battery app, but log does not indicate any issues... So I am afraid I can't really help, as I can't reproduce this behavior on my device.
MSe1969 said:
Hi, haven't really noticed anything unusual in the log, I also use afwall and Xprivacy. Only noticed you use a battery app, but log does not indicate any issues... So I am afraid I can't really help, as I can't reproduce this behavior on my device.
Click to expand...
Click to collapse
Yeah, I use the betterbatterystats from xda. I guess I will try and do a dalvik cache clear and if possible do a clean rom flash in the near future and try again. Else, it must be some device specific issue.
Anyway thanks a lot for your time. I appreciate it.
My daily ROM, please update.
The best ROM tk!
kurapika7 said:
My daily ROM, please update.
The best ROM tk!
Click to expand...
Click to collapse
This is marshmallow, correct. Why is it better than
Nugget?
Thanks for sharing!
Also, your experience with no Google services.
melp57 said:
This is marshmallow, correct. Why is it better than
Nugget?
Thanks for sharing!
Also, your experience with no Google services.
Click to expand...
Click to collapse
have a better use of ram
This is the support thread of PixelFlasher
(PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features).
Note: This thread is meant for issues and problems faced in Google Pixel 5 devices, generic issues that are device agnostic should be discussed in the main thread.
For full details on where to download / usage and feature set of the tool, visit the main thread at XDA or the project's Github page.
Troubleshooting:
If you need support or assistance, the best way to get is by generating a support file from within PixelFlasher.
You can hit that big Support button on the main screen, or select it from the Help menu.
The generated support.zip file is sanitized (redacted) to keep your sensitive information (username device id ...) private.
Placeholder
Placeholder
Placeholder
just asking if it will work on 4a5g too due to similarities with Pixel5 or not?
creezalird said:
just asking if it will work on 4a5g too due to similarities with Pixel5 or not?
Click to expand...
Click to collapse
Yes it should, although I don't have one and hence I have not tested it, but the program should work for all Pixel phones, and possibly all Google made phones. There is no difference in the process amongst these phones.
New Release: (See full details here on xda or here at github)
April 03, 2022 v2.0.0.0-pre release.
Major refactoring
Added Advanced (Expert) mode UI.
Basic mode keeps UI simple and hides expert features.
Support for setting active slot.
Reboot options (recovery, system, bootloader)
Moved custom ROM options to expert mode.
Added custom flashing to expert mode, can now flash to live (temporary root), or custom flash any image to any partition.
Moved flashing to both slots, disabling verity / verification to expert mode.
Many other improvements, validations and checks.
Updated documentation.
Update:
Version 2.0.1 which includes a hotfix for issue reported here.
New Release:
April 06, 2022 v2.1.0 release
Setup dedicated profile directory.
Put logs in the profile directory and maintain log history.
Plumbing for Linux support (just the flashing part is left to do).
Plumbing for new workflow.
Bugfix to handle name conflict in ROM filename.
Various minor improvements.
Update documentation.
New release:
April 10, 2022 v2.2.0 release
Linux support.
Remember last window position.
List Magisk modules, when Magisk is detected.
Added fastboot verbose option.
Added more checks and validations.
Added more details when errors are encountered.
Cleaner message box (better formatting).
Notice to the user in case fastboot drivers are not setup properly.
More plumbing work for the new upcoming workflow.
Add notes on how to build the Linux version.
New release:
April 11, 2022 v2.2.2 release
Linux Improvements, warn user if selected SDK is old.
New Release:
April 19, 2022 v2.4.0 release
Magisk modules management, enable / disable modules selectively, this comes in handy to disable suspect modules before an upgrade.
Autoscroll the console.
Code cleanup.
April 17, 2022 v2.3.0 release
Optional automatic check for updates feature.
Added help menu links to:
- Report an issue
- Feature Request
- PixelFlasher Project Page
- PixelFlasher Community (Forum)
- Homeboy76's Guide
- V0latyle's Guide
- Open Configuration Folder
- Check for New Version
Icons for menu items.
Link to download Pixel Firmware.
Link to download Android Platform Tools.
Unlock Bootloader.
Lock Bootloader.
SOS (experimental) - disable Magisk modules to get out of bootloop.
Additional flashing options:
- product
- system
- system_ext
- system_other
- vbmeta_system
- vbmeta_vendor
Added sideload flashing option.
Updated documentation.
Further improved console messages for troubleshooting.
Linux build using Github Actions.
Manual build for Kali Linux.
Bug fix release:
April 20, 2022 v2.4.1 release
Bug Fixes: Error message during flashing, introduced by code reshuffle.
It turns out that some Magisk Modules don't set the id, which was expected to be present, which caused Magisk module management screen not to display.
New Release:
April 30, 2022 v3.0.0 release
New workflow, no more package preparation, select options and flash all dynamic.
boot.img caching and management UI with details about the state of boot.img files.
Faster as there is no more need to zip a package.
Other optimizations and improvements.
Update documentation.
Check the main thread or the Github page for details about the new workflow, hope you find it useful.
New Release
May 02, 2022 v3.1.0 release
Fixed a missing step in the final flashing of boot.img
Decoupled Firmware / ROM processing from selecting the files, now we have a separate button to process, makes it clearer and does not give the impression that selecting the file is hanging.
Added splash screen (v3.0.1), the GUI refresh hiccup is gone.
Made the boot.img management delete function more extensive.
I flashed my phone with the May drop using this version.
badabing2003 said:
New Release
May 02, 2022 v3.1.0 release
Fixed a missing step in the final flashing of boot.img
Decoupled Firmware / ROM processing from selecting the files, now we have a separate button to process, makes it clearer and does not give the impression that selecting the file is hanging.
Added splash screen (v3.0.1), the GUI refresh hiccup is gone.
Made the boot.img management delete function more extensive.
I flashed my phone with the May drop using this version.
Click to expand...
Click to collapse
I would like to make a request for your tool if that's ok could you give the option to open up diag for the Pixel 5?
elong7681 said:
I would like to make a request for your tool if that's ok could you give the option to open up diag for the Pixel 5?
Click to expand...
Click to collapse
what is diag?
what Am I going to open?
badabing2003 said:
what is diag?
what Am I going to open?
Click to expand...
Click to collapse
Diag port for using QPST from Qualcomm
elong7681 said:
Diag port for using QPST from Qualcomm
Click to expand...
Click to collapse
Is this what you want?
Code:
adb shell "su -c 'setprop sys.usb.config diag,adb'"
just type this and see if it works, if it does, very easy to add.
I don't have a Qualcomm device to test with
badabing2003 said:
Is this what you want?
Code:
adb shell "su -c 'setprop sys.usb.config diag,adb'"
just type this and see if it works, if it does, very easy to add.
I don't have a Qualcomm device to test with
Click to expand...
Click to collapse
Code:
adb shell
su
resetprop ro.bootmode usbradio
resetprop ro.build.type userdebug
setprop sys.usb.config diag,diag_mdm,adb
diag_mdlog
cancel (ctrl+c) once it starts to "hang" at failed to open diag socket
change usb config (file transfer, no file transfer)
This is how it is done for the Pixel 5
Hiya XDA People, Today I will be showing you how to install GMS with full downgrade, this tutorial works flawlessly and you can give it a shot!
Let's get started
-------------------------------------------------------------------------------------------------------------------------------------------------------------
Step 1:
To downgrade from EMUI 12 to EMUI 10, we need to firstly downgrade to EMUI 11
To do that here's what to do:
1. Download HiSuite 11.0.0.610 (Downloads Provided)
2. Set it up, and plug your phone in and do the process
3.(WARNING WITHOUT HISUITE PROXY) Press check for updates and wait
4. After you waited for a while, there should be a button that says switch version to EMUI 11.0.0.260
5. Downgrade your phone into EMUI 11.0.0.260
Step 2:
Now we need to downgrade from EMUI 11.0.0.260 to EMUI 11.0.0.230 (The Dload file attached is for C432, the dload file has been tested to work with all CXXX codes, Has been tested on C185 P40 Pro)
1. Download the file provided
2. Get an OTG flash drive, NM card or any flash drive that can work on both a PC and the P40 Pro
3. Once downloaded open the file and go to Software, you should see a folder named dload copy the file and paste it on your flash drive
4. Plug the flash drive to your phone with the dload file in the flash drive
5. once plugged in, go to the dialer app and write "*#*#2846579*#*#*", Then go to software upgrade then Memory card upgrade then press yes and wait for the downgrade
Step 3:
Once downgraded, we need to downgrade from EMUI 11.0.0.230 to EMUI 10.1.0 Supported GMS version
1. Install HiSuite 11.0.0.530 (Uninstall the old HiSuite 11.0.0.610), Plug your phone and do the process, once HiSuite is installed on the phone, uninstall HiSuite 11.0.0.530 ONLY FROM THE PC, then download HiSuite 10.1.0.550 and HiSuite Proxy 2.4.0 (Downloads Provided), then go to https://professorjtj.github.io and then go on your phone, on your phone go to the dialer app and write "*#*#2846579*#*#", once written go to veneer information and Version Info, then scroll all the way to the end until you see Base, Cust And Preload Software Version, in the CUST section, Take the first 2 codes EX:/ELS-NXX and paste it in the website as phone model, then in the same CUST section, in the brackets (CXXX) copy it and paste it on the website Region (CXXX), keep in mind all the website data should be entered on the pc AND NOT THE PHONE
2. Once done, Open HiSuite Proxy and go back to the website, then find the CUST and Preload file, as for the base make sure the version is between 10.1.0.130-10.1.0.135, and press Add ROM for all 3 files
3. Once added go back to HiSuite Proxy and press Roll Back and then press setup and wait, once successful close the CMD tab AND NOT HISUITE PROXY
4. Open HiSuite and plug the phone in, then write the code and press check for update and wait
5. Once done, press switch to an older version and check if the version is between 10.1.0.130-10.1.0.135, if so downgrade it
6. Wait for the downgrade to finish downloading
-------------------------------------------------------------------------------------------------------------------------------------------------------------
Now, Downgrading is done, we will move onto downloading Google Play (KEEP IN MIND, DO NOT UPDATE YOUR PHONE UNTIL THE WHOLE PROCESS IS DONE)
Lets start!
Step 1:
1. Download the APK Bundle to the phone
2. Once downloaded, extract the file onto your phone
3. Go into the folder and there should be numbered folder and apk files
4. Copy a folder named "Backup" and paste it into a folder named "Huawei" onto the main directory
5. Once done, go to settings and then System & Updates then date and time and set it to manual, and change the date into 2015 (day and month don't matter)
6. Go to settings, Apps, Apps and then press on the 4 dotted square on the top right
7. Press show system process and search for "Backup", then uninstall it
8. After that, go back to the APK bundle folder and install the backup apk provided
9. Once downloaded, go to settings, System & Update then Backup & Restore, press on the 4 dotted square on the top right and press Restore from internal storage
10. It should be one file, that's an app then press restore, the password is "ictfix1net' (Password provided as the hint, QUICK NOTE, THE FOLDER IS NOT MINE AND I DO NOT OWN IT)
11. Go to the app downloaded on the phone and press on the big blue button on the bottom, then press activate and press the blue button again, make sure that everything is starting to load
12. Once everything started to load, go back to settings, System & Updates, date and time then set it back to automatic
13. Go back to the APK bundle and install MicroG Huawei, then open it
14. Press on add account (if it crashes its okay it happens, just press add account again and it will work), then add your google account
15. Once added, go back to the APK Bundle and install every app numbered from 2-6 (DO NOT INSTALL GMS IN THE PROCESS YET)
16. Once all installed, go and uninstall MicroG Huawei then go to Settings, User & Accounts then check if your google account is there, if so go to it and press on it then start syncing it (if the google account is not there, proceed to step 24 )
17. Go back to the APK Bundle folder and install GMS.apk (ONLY GMS, NUMBERED 7)
18. Once downloaded, open Google Play and check if it works
19. Go to settings, Apps, Apps, 4 dotted square on the top right and press show system process
20. search for "Google" and go to Google Account Manager, Google Play Games and Google Service Framework, force stop them and clear their data (KEEP IN MIND, DO IT FOR THOSE 3 ONLY)
21. Once done' reboot your phone
22. Once rebooted, go back to APK Bundle folder, then install GMS Notification Fix.apk (ONLY GMS NOTIFICATION FIX, NUMBERED 8), after installing it repeat step 20 and 21
23. Once rebooted, go back to APK Bundle folder, then install GMS Play Protect Certified Fix.apk, once downloaded go to Google Play and search for any app, if no results show go back to settings, Apps, Apps then search for "Google Play Store" and force stop, then clear the data and it will work
24. If it did not work, message me on my telegram, https://t.me/MohammedAwsXDA (The services are FREE, but if you would like to contribute to help me make all those free services possible, you can donate)
IMPORTANT NOTE, DISABLE AUTO UPDATE OR THEN IT WILL STOP WORKING, MAKING YOU REPEAT EVERY SINGLE STEP
To disable it go to Google Play Store, Press on the Profile Picture, Settings, Network Preferences and press Auto-Update Apps then press Don't Auto-Update Apps
ANOTHER IMPORTANT NOTE, ANY DAMAGE DONE TO THE DEVICE I AM NOT RESPONSIBLE, PROCEED WITH CAUTION
Files:
Downgrade dload file: https://androidhost.ru/Z6c
HiSuite Proxy: https://drive.google.com/file/d/1O5UczUz5BExvjYQPE5OUuJHAW0xoUVnD/view?usp=sharing
HiSuite 11.0.0.610: https://drive.google.com/file/d/1n2KML4M7FeghdfYX0Loy8YoPT5se0Wpj/view?usp=sharing
HiSuite 11.0.0.530: https://drive.google.com/file/d/1542BL9qlP0xxgqD-sV7l8FGHqT53p0Eq/view?usp=sharing
HiSuite 10.1.0.550: https://drive.google.com/file/d/1yCQdeGZhFTYa3MKgy4EQuTQ5_v0VlSvP/view?usp=sharing
APK Bundle: https://drive.google.com/file/d/11ZVz2rAv0j4Li_D43-dBUuLb5EqkQ_xf/view?usp=sharing
Credit goes to https://forum.xda-developers.com/m/badmania98.619592/ for providing the Proxy, HiSuite and dload files
”12.1. Give credits where due - Credits and acknowledgements for using and releasing work which is based on someone else's work are an absolute must. Works reported to have no credits will be taken down until proper acknowledgements are added by the member in question;”
📚 XDA Developers Forum Rules 📚
XDA-Developers FORUM RULES List of Forum Moderators, click HERE Delete Your XDA Account HERE 1. Search before posting. Use one of our search functions before posting or creating a new thread. Whether you have a question or just something new...
forum.xda-developers.com
badmania98 said:
”12.1. Give credits where due - Credits and acknowledgements for using and releasing work which is based on someone else's work are an absolute must. Works reported to have no credits will be taken down until proper acknowledgements are added by the member in question;”
📚 XDA Developers Forum Rules 📚
XDA-Developers FORUM RULES List of Forum Moderators, click HERE Delete Your XDA Account HERE 1. Search before posting. Use one of our search functions before posting or creating a new thread. Whether you have a question or just something new...
forum.xda-developers.com
Click to expand...
Click to collapse
Credit already given at the last line.
I hv Huwaei P40 pro still stuck on emui 10.1.0.112 emui 10.1.1 android version 10 its not updating can someone help
Prince 1248 said:
I hv Huwaei P40 pro still stuck on emui 10.1.0.112 emui 10.1.1 android version 10 its not updating can someone help
Click to expand...
Click to collapse
Try to update it using HiSuite
Prince 1248 said:
I hv Huwaei P40 pro still stuck on emui 10.1.0.112 emui 10.1.1 android version 10 its not updating can someone help
Click to expand...
Click to collapse
i can use hisuite last version,it work
MohammedAws said:
Hiya XDA People, Today I will be showing you how to install GMS with full downgrade, this tutorial works flawlessly and you can give it a shot!
Let's get started
-------------------------------------------------------------------------------------------------------------------------------------------------------------
Step 1:
To downgrade from EMUI 12 to EMUI 10, we need to firstly downgrade to EMUI 11
To do that here's what to do:
1. Download HiSuite 11.0.0.610 (Downloads Provided)
2. Set it up, and plug your phone in and do the process
3.(WARNING WITHOUT HISUITE PROXY) Press check for updates and wait
4. After you waited for a while, there should be a button that says switch version to EMUI 11.0.0.260
5. Downgrade your phone into EMUI 11.0.0.260
Step 2:
Now we need to downgrade from EMUI 11.0.0.260 to EMUI 11.0.0.230 (The Dload file attached is for C432, the dload file has been tested to work with all CXXX codes, Has been tested on C185 P40 Pro)
1. Download the file provided
2. Get an OTG flash drive, NM card or any flash drive that can work on both a PC and the P40 Pro
3. Once downloaded open the file and go to Software, you should see a folder named dload copy the file and paste it on your flash drive
4. Plug the flash drive to your phone with the dload file in the flash drive
5. once plugged in, go to the dialer app and write "*#*#2846579*#*#*", Then go to software upgrade then Memory card upgrade then press yes and wait for the downgrade
Step 3:
Once downgraded, we need to downgrade from EMUI 11.0.0.230 to EMUI 10.1.0 Supported GMS version
1. Install HiSuite 11.0.0.530 (Uninstall the old HiSuite 11.0.0.610), Plug your phone and do the process, once HiSuite is installed on the phone, uninstall HiSuite 11.0.0.530 ONLY FROM THE PC, then download HiSuite 10.1.0.550 and HiSuite Proxy 2.4.0 (Downloads Provided), then go to https://professorjtj.github.io and then go on your phone, on your phone go to the dialer app and write "*#*#2846579*#*#", once written go to veneer information and Version Info, then scroll all the way to the end until you see Base, Cust And Preload Software Version, in the CUST section, Take the first 2 codes EX:/ELS-NXX and paste it in the website as phone model, then in the same CUST section, in the brackets (CXXX) copy it and paste it on the website Region (CXXX), keep in mind all the website data should be entered on the pc AND NOT THE PHONE
2. Once done, Open HiSuite Proxy and go back to the website, then find the CUST and Preload file, as for the base make sure the version is between 10.1.0.130-10.1.0.135, and press Add ROM for all 3 files
3. Once added go back to HiSuite Proxy and press Roll Back and then press setup and wait, once successful close the CMD tab AND NOT HISUITE PROXY
4. Open HiSuite and plug the phone in, then write the code and press check for update and wait
5. Once done, press switch to an older version and check if the version is between 10.1.0.130-10.1.0.135, if so downgrade it
6. Wait for the downgrade to finish downloading
-------------------------------------------------------------------------------------------------------------------------------------------------------------
Now, Downgrading is done, we will move onto downloading Google Play (KEEP IN MIND, DO NOT UPDATE YOUR PHONE UNTIL THE WHOLE PROCESS IS DONE)
Lets start!
Step 1:
1. Download the APK Bundle to the phone
2. Once downloaded, extract the file onto your phone
3. Go into the folder and there should be numbered folder and apk files
4. Copy a folder named "Backup" and paste it into a folder named "Huawei" onto the main directory
5. Once done, go to settings and then System & Updates then date and time and set it to manual, and change the date into 2015 (day and month don't matter)
6. Go to settings, Apps, Apps and then press on the 4 dotted square on the top right
7. Press show system process and search for "Backup", then uninstall it
8. After that, go back to the APK bundle folder and install the backup apk provided
9. Once downloaded, go to settings, System & Update then Backup & Restore, press on the 4 dotted square on the top right and press Restore from internal storage
10. It should be one file, that's an app then press restore, the password is "ictfix1net' (Password provided as the hint, QUICK NOTE, THE FOLDER IS NOT MINE AND I DO NOT OWN IT)
11. Go to the app downloaded on the phone and press on the big blue button on the bottom, then press activate and press the blue button again, make sure that everything is starting to load
12. Once everything started to load, go back to settings, System & Updates, date and time then set it back to automatic
13. Go back to the APK bundle and install MicroG Huawei, then open it
14. Press on add account (if it crashes its okay it happens, just press add account again and it will work), then add your google account
15. Once added, go back to the APK Bundle and install every app numbered from 2-6 (DO NOT INSTALL GMS IN THE PROCESS YET)
16. Once all installed, go and uninstall MicroG Huawei then go to Settings, User & Accounts then check if your google account is there, if so go to it and press on it then start syncing it (if the google account is not there, proceed to step 24 )
17. Go back to the APK Bundle folder and install GMS.apk (ONLY GMS, NUMBERED 7)
18. Once downloaded, open Google Play and check if it works
19. Go to settings, Apps, Apps, 4 dotted square on the top right and press show system process
20. search for "Google" and go to Google Account Manager, Google Play Games and Google Service Framework, force stop them and clear their data (KEEP IN MIND, DO IT FOR THOSE 3 ONLY)
21. Once done' reboot your phone
22. Once rebooted, go back to APK Bundle folder, then install GMS Notification Fix.apk (ONLY GMS NOTIFICATION FIX, NUMBERED 8), after installing it repeat step 20 and 21
23. Once rebooted, go back to APK Bundle folder, then install GMS Play Protect Certified Fix.apk, once downloaded go to Google Play and search for any app, if no results show go back to settings, Apps, Apps then search for "Google Play Store" and force stop, then clear the data and it will work
24. If it did not work, message me on my telegram, https://t.me/MohammedAwsXDA (The services are FREE, but if you would like to contribute to help me make all those free services possible, you can donate)
IMPORTANT NOTE, DISABLE AUTO UPDATE OR THEN IT WILL STOP WORKING, MAKING YOU REPEAT EVERY SINGLE STEP
To disable it go to Google Play Store, Press on the Profile Picture, Settings, Network Preferences and press Auto-Update Apps then press Don't Auto-Update Apps
ANOTHER IMPORTANT NOTE, ANY DAMAGE DONE TO THE DEVICE I AM NOT RESPONSIBLE, PROCEED WITH CAUTION
Files:
Downgrade dload file: https://androidhost.ru/Z6c
HiSuite Proxy: https://drive.google.com/file/d/1O5UczUz5BExvjYQPE5OUuJHAW0xoUVnD/view?usp=sharing
HiSuite 11.0.0.610: https://drive.google.com/file/d/1n2KML4M7FeghdfYX0Loy8YoPT5se0Wpj/view?usp=sharing
HiSuite 11.0.0.530: https://drive.google.com/file/d/1542BL9qlP0xxgqD-sV7l8FGHqT53p0Eq/view?usp=sharing
HiSuite 10.1.0.550: https://drive.google.com/file/d/1yCQdeGZhFTYa3MKgy4EQuTQ5_v0VlSvP/view?usp=sharing
APK Bundle: https://drive.google.com/file/d/11ZVz2rAv0j4Li_D43-dBUuLb5EqkQ_xf/view?usp=sharing
Credit goes to https://forum.xda-developers.com/m/badmania98.619592/ for providing the Proxy, HiSuite and dload files
Click to expand...
Click to collapse
Thanks. It worked for a while. after a while (after i woke up from my sleep), all google apps showed not supported and forced me out.
miyaki84 said:
Thanks. It worked for a while. after a while (after i woke up from my sleep), all google apps showed not supported and forced me out.
Click to expand...
Click to collapse
apologies for my late response, but I have another tutorial that is supposed to be followed which is updating GMS, so follow that one and you're good to go.