{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is a small project based on AOSP. We try to be a platform for beginners and support the Custom ROM community with our own unique contributions as well. This ROM exists thanks to inspiration of AOSiP, Thank you! #StayDerped
Code:
/* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Features
GApps included!
- Signed with release keys like stock
- Google network stack
- Google PSU support
- Google APN's and CarrierConfig
- Accent color, font, icon shape, icon pack customizations from Bootleggers
- Statusbar icons tuner
- App lock
- Face unlock
- Expandable volume panel
- Omni weather
- Gvisual Mod
- Advanced gesture navigation options
- FOD icon picker and wallpaper based color option
- FOD Animations
- Custom logo customizations
- Custom Carrier Label & Carrier Label Placement
- AOD Schedule options
- 3 finger swipe to screenshot
- Cycle through ringer modes
- Adaptive playback
- Long press power button to toggle flashlight
- Long press volume button to skip track
- Advanced reboot options
- Additional lockscreen sclocks
- QS tile styles
- Switch styles
- Custom QS headers
- Edge light options
- Battery light toggle
- Scrolling screenshot (Asus stitchimage)
- Battery icon styles (circle/bar/hidden)
- QS quick pulldown
- Bunch of useful QS tiles in addition to AOSP ones:
- AOD
- Caffeine
- Data Switch
- Location modes
- HeadsUp (peek notifications)
- Kill app
- Weather
- USB tethering
- Screenshot (partial/full)
- Sound (ringer modes)
- Sound search
- Reboot (system/recovery)
- Mono/Stereo
- Notifications clear all button
- OOS-inspired QS tiles layout
- Data usage under QS
- Small oreo-like data type icon
- Traffic indicator for wifi and mobile data
- OOS-inspired Network speed indicator
- VoLTE/VoWiFi multi-sim icon
- Lockscreen media art and blur level controls
- Improved statusbar pulldown blur
- Added blur to power menu
- Double tap to sleep on statusbar, launcher, lockscreen
- Finer control over font size
- Mini panels for wifi, bluetooth, NFC
- Per-app network restrictions
- Allow hotspot/tethering to use VPN (toggleable)
- Additional charging info on lockscreen
- Statusbar bluetooth battery level
- NFC tile for devices with nfc
- Multi SIM ringtone setting
- Screen recorder stop dot and low quality options
- Bring back 2 button navigation from pie
- Delete button for screenshots
- Show 3 QS columns when media player is inactive
- Faster fingerprint wakeup
- Pixel offline charging animation (for supported devices)
- Enabled iorap and zygote preforking (for faster app launch)
- One click to add/remove QS tiles
- Hacks to bypass safetynet and root detection
- Few pixel features like assist disclosure, live captions, adaptive connectivity
- Optimizations and fixes from AOSPA, ProtonAOSP & upstream AOSP master
- CAF functionality improvements/enhancements:
- Bluetooth A2DP hardware offload
- Audio policy extensions
- Camera extensions
- Telephony framework
- Individual sim toggle (for some dualsim devices)
- WiFi display/miracast
- Hardware accelerated screen recording
- NQ NFC support (for nfc supported devices)
- Power off alarm in inbuilt clock app
- Touch response optimizations
- Performance improvements & fixes throughout the system
What's broken?
DT2W
You tell me!
ROM: https://www.androidfilehost.com/?fid=17825722713688277214
MD5: E339DDE03A10FA105048BE3F524ECB94
RECOVERY: https://www.androidfilehost.com/?fid=17825722713688277217
MD5: 086AD719B76BEB04C2C910EE77765B89
INSTRUCTIONS
1. Download the ROM and Recovery image
2. Boot into bootloader/fastboot mode | [adb reboot bootloader]
3. Flash the Recovery image | [fastboot flash recovery recovery.img]
4. Boot into Recovery | [fastboot reboot-recovery]
5. Perform a Factory Reset/Wipe in Recovery
6. Go to Apply Update and choose Apply from ADB
7. Sideload the ROM | [adb sideload rom.zip]
Reboot and voila!
Follow us on Telegram
Credit/Thanks:
Google for Android and AOSP
LineageOS
AOSiP
AICP
ABC ROM
AquariOS
BootleggersROM
PixelExperience
OmniROM
Cory Collins
---------
Any others we may have forgotten to credit
And last but not the least, all our testers, who have helped us to squash many bugs so that we can try to release builds that as are flawless as possible
DerpFest, ROM for the OnePlus Nord N10 5G
Contributors: @iamsaalim, @kronflux
ROM source: https://github.com/DerpFest-11/
Device sources: https://github.com/kronflux/device_oneplus_billie
Kernel source: https://github.com/danascape/kernel_oneplus_sm6350
ROM OS Version: 11.x
ROM Kernel: 4.19.125
ROM Firmware Required: OxygenOS 11.x
Based On: AOSP
Version Information
Status: Beta
Created 27-01-2022
Last Updated 27-01-2022
Old post
I keep getting error 7 / status 1 after the sideload.
How does one update the full system to android 11, like MSM tool or equivelant? Or is this only possible as OTA?
EDIT: @kronflux
Just wanted to mention that I did start from a clean flash (MSM Tool - but of course that is android 10), and subsequently re-unlocked the bootloader, but still no dice. I know I'm missing something I just can't figure what.
Usually I would upgrade to the same android version as the custom os (11 in this case) and I did try that once as well, and it still didn't work.
What is the legit way to update both slots to a new stock OS so that users can flash an upgraded custom OS?
I am still reading everything I can in this device forum, trying to figure out what I missed.
I finally managed to get this ROM flashed. Seems that, at least in my case, the ROM flash doesn't cause the slot to be switched after reboot. I need to basically do this:
(optional) - Boot to opposite desired slot.
Flash Recovery
Boot to recovery
Factory Reset
Flash Rom (sideload)
Reboot to bootloader
change slots
Reboot to bootloader again (ensure slot change)
(optional) Flash Recovery to new/current slot
(optional) Then Flash GApps (if allowed for the ROM, not this one as GApps are included)
Boot ROM from bootloader
This manual slot change is not something I see from any of the instructions on this entire device sub forum, even for other posted/supported ROMs. I know that usually the slot change is automatic, but in my case for some reason it is not.
Move...
I asked if this can be flashed over the earlier beta as-is ?
I did so earlier with the beta using TWRP, but it was originally installed on A10.
I don't have any issues with sideloading any rom but this one i keep getting "adb: failed to read line: no error"
CodeNotSoGenious said:
I don't have any issues with sideloading any rom but this one i keep getting "adb: failed to read line: no error"
Click to expand...
Click to collapse
turns out minimal adb and fastboot wasn't working so I had to use android sdk tools
gaww said:
Move...
Click to expand...
Click to collapse
Once again - can I flash over original one with TWRP?
TheArkive said:
Old post
I keep getting error 7 / status 1 after the sideload.
How does one update the full system to android 11, like MSM tool or equivelant? Or is this only possible as OTA?
EDIT: @kronflux
Just wanted to mention that I did start from a clean flash (MSM Tool - but of course that is android 10), and subsequently re-unlocked the bootloader, but still no dice. I know I'm missing something I just can't figure what.
Usually I would upgrade to the same android version as the custom os (11 in this case) and I did try that once as well, and it still didn't work.
What is the legit way to update both slots to a new stock OS so that users can flash an upgraded custom OS?
I am still reading everything I can in this device forum, trying to figure out what I missed.
I finally managed to get this ROM flashed. Seems that, at least in my case, the ROM flash doesn't cause the slot to be switched after reboot. I need to basically do this:
(optional) - Boot to opposite desired slot.
Flash Recovery
Boot to recovery
Factory Reset
Flash Rom (sideload)
Reboot to bootloader
change slots
Reboot to bootloader again (ensure slot change)
(optional) Then Flash GApps (if allowed for the ROM, not this one as GApps are included)
Boot ROM from bootloader
This manual slot change is not something I see from any of the instructions on this entire device sub forum, even for other posted/supported ROMs. I know that usually the slot change is automatic, but in my case for some reason it is not.
Click to expand...
Click to collapse
Slot logic, I guess.
It was b slot on the old roms because we started out on A as the active partition, so maybe we just have to switch to the inactive slot when flashing.
Realized this a couple nights ago, but my device went into kernel panic anyway so I couldn't really verify.
Thank you.
gaww said:
I asked if this can be flashed over the earlier beta as-is ?
I did so earlier with the beta using TWRP, but it was originally installed on A10.
Click to expand...
Click to collapse
No, this has to be installed over A11.
This rom depends on the updated kernel, so flashing over a new version of the ROM won't just work.
Hello, I am encountering this error, 'adb: failed to read command: No error', what is the problem?
kinfrayt said:
Hello, I am encountering this error, 'adb: failed to read command: No error', what is the problem?
Click to expand...
Click to collapse
Update your adb.
https://forum.xda-developers.com/t/...latest-official-adb-fastboot-drivers.4228853/
ninjasinabag said:
Update your adb.
https://forum.xda-developers.com/t/...latest-official-adb-fastboot-drivers.4228853/
Click to expand...
Click to collapse
I downloaded too much adb, I changed the version, it didn't work no matter what I did. Qualcomm went all the way to crushdumb mode.
The operation was not successful. I am using Android 11.
My device Oneplus n10 5G BE86AA
I tried 10-15 times but all failed. I would really appreciate it if anyone can help me out and have had this problem.
I'm using google translate, it may be misspelling.
For everyonw that have problems by sideloading. I recommend to use exactly the recovery they provide there, don't even thing using twrp or orange fox, because those sideload are just broken.
also, the standard fastboot drivers include x86 adb, that would not work correctly always.
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
download this, and use adb sideload rom.zip exactly with those tools. for me, it was the single thing that did worked.
Later Edit: needed to change the A/B Slot
# boot the phone into fastboot either if in the bootloader
#
sudo fastboot reboot fastboot
#
# or if the phone is booteind into the recovery or in the normal mode
#
adb reboot fastboot
# wait until the phone is booted in fastboot mode
# get the current slot
#
sudo fastboot getvar current-slot
# change the current slot
#
sudo fastboot set_active b
# check the result
#
sudo fastboot getvar current-slot
# reboot the phone from new current-slot
#
sudo fastboot reboot
gherv1 said:
For everyonw that have problems by sideloading. I recommend to use exactly the recovery they provide there, don't even thing using twrp or orange fox, because those sideload are just broken.
also, the standard fastboot drivers include x86 adb, that would not work correctly always.
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
download this, and use adb sideload rom.zip exactly with those tools. for me, it was the single thing that did worked.
Later Edit: needed to change the A/B Slot
# boot the phone into fastboot either if in the bootloader
#
sudo fastboot reboot fastboot
#
# or if the phone is booteind into the recovery or in the normal mode
#
adb reboot fastboot
# wait until the phone is booted in fastboot mode
# get the current slot
#
sudo fastboot getvar current-slot
# change the current slot
#
sudo fastboot set_active b
# check the result
#
sudo fastboot getvar current-slot
# reboot the phone from new current-slot
#
sudo fastboot reboot
Click to expand...
Click to collapse
Well, most people are using gsi Roms on this phone. I am running Crdoid android 13 April 2023 build and security patch on my nord n10 5g with magisk and 5 volte/vo5g both working
Im quite liking this rom, but i keep getting a QUALCOMM CrashDump Mode a bit after plugging it in to charge at night... it sticks in this mode until i hard reset, then its fine. The lack of auto-reboot really sucks since i cant trust this phone as an alarm right now.
Also, this doesnt happen every time i plug it in... seems to be about every other night so far, might be related to how low the battery gets, not sure.
Running this on a BE2026 model on Cricket (ATT network), also have done some customization installing magisk and a few modules... im pretty sure the first crash was before i had all the modules installed, but ill be trying to disable some of them and see if it helps at all. its hard to test something when there's not an easy way to trigger it...
There is an error included too, been trying to decrypt it but not having a lot of luck:
Code:
EX:kernel:0x0:SNS_SEE_P_1:0x1000000e:PC=0xf02baadc:LR=0xf0215f78
subsys_err_fatal_intr_handlersubsys-restart: Resetting the SoC - adsp crashed.
subsys_unregister
Another SERIOUS issue I discovered today - I cant disable wireless emergency alerts. The settings app will crash when I try to open the settings for it, and trying to get to it from the messages app does nothing. It seems there's no way to turn off these ridiculously loud amber alterts.
jamescable said:
Well, most people are using gsi Roms on this phone. I am running Crdoid android 13 April 2023 build and security patch on my nord n10 5g with magisk and 5 volte/vo5g both working
Click to expand...
Click to collapse
Hi!
In the CrDroid GSI, Did you experience any sort of bugs regarding calling?
I've also experience some bugs/quirks like the "high pitched voice" while calling someone through Internet apps like Signal/WhatsApp/Anyotherapp.
Related
[ROM][UNOFFICIAL][6.0.1][E6653/E6603] CyanogenMod 13 for the Sony Xperia Z5 [ALPHA]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CyanogenMod 13 for the Sony Xperia Z5 E6653 and E6603
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0 (Marshmallow), which is designed to increase
performance and reliability over stock Android for your device.
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be
used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps).
CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Before you start
This ROM is only for the E6653 and the E6603
Code:
*
* Your warranty may be voided !
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
Special Thanks
@CTXz for getting the ball rolling on CyanogenMod for Z5 series and stemming the lion's share to get this working
@oshmoun for providing fixes ASAP
@AndroPlus for providing a great kernel that works with many recoveries
@moonbutt74 for reminding me that smashing your device can provide a solution
@sub77 for teaching me how to work with QCOM (I was on exynos before)
@Joeisgood99 for providing a solid working TWRP-3.0.0.0 build until we had our own
@bazhip for providing a well working twrp 2.8.7.0 for restoring until we had our own
@alphatact1cs has a great overview on lots of topics for the Z5 device family
@auras76 for his great Custom ROM
@infected_ for his experience
Thanks to @mpro420 for help to get Viper4Android working !
Thanks to @jimRnor for Project DiVA SoundMod !
The Sonyxperiadev team for releasing their sources to the public
SonyAOSP team
SonyCM team
Sony Xperia (community) devs
And ofcourse the entire CyanogenMod team!
(Known) Issues
Video Recording
Bluetooth (keeps restarting) (might be fixed, needs feedback + testing)
Camera Colors (can be circumvented by using specific apps CameraNext Mod )
Camera Focus & Sharpness (driver issue, probably since it uses Xperia Z (original) drivers but different lenses ?)
Camera lowlight pictures (might improve with release of Sony's "Experimental AOSP Camera" for the Z5 series, porting of other Framework + Stock Cam app; partially needs DRM magic)
Camera Focus (even with VCM2 actuator changes focus is still kind of murky)
Fingerprint sensor (might work depending on build date of ROM)
Lag after booting up device (Will resolve: lock screen after boot and waiting a few seconds)
Long bootup times & less smoothness with "stock" (prebuilt) kernel
What can not be fixed, changed - aka WONTFIX - NOTOURPROBLEM
There might be potential speed issues with Class 10+ microSD cards not properly being "tuned", in that case switch to slower cards or RMA it which should hopefully solve it. There is a possibility to force slower speeds on cards but that is not really the optimal solution with ultra speed cards and needs further investigation. Samsung (EVO/EVO+) cards, Transcend cards and a few others UHS-I(+) and faster are affected.
What has been Fixed
Horizontal color lines and color glitches during bootup
Gapps
Sudden Lag after some time
NFC
Odd calling numbers
In-call mic
Sound on calls
Camera button
Microphone
Thermal regulation
Red flashy frames
RIL (SIM detection)
Dex pre-optimization
Camera
Sensors
Crash after locking device
microSD access
Flash light / Torch
Full brightness (should be fully working)
Gapps (permissions issues) [occurs occasionally and should be circumvented by full-wipe approach (incl. internal storage)
Hang/Loop during boot stage (should be circumvented by full-wipe approach (incl. internal storage)) (use Custom Kernel, under investigation)
High battery drain [~ 10%-20% per hour] when dirty-flashing system (fastboot -S 256M flash system system.img), make sure to have data backed up, then format /data ; OTA updates should be fine though [need feedback] ); causes are: dirty flashing, certain apps, ROM issues, etc.
Guides/Instructions
Unlocking Bootloader
Warning! The following procedure may void your warranty and will wipe EVERYTHING
Visit Sonys Official Bootloader Unlock guide (Details to all the risks you are taking are located on their site)
After Unlocking your bootloader you can proceed with the next steps
Steps on how to Fastboot, Flashmode, Recovery, Emergency/Force Poweroff
@alphatact1cs has a great overview on lots of topics for the Z5 device family
over at [GUIDE] Sony Xperia Z5 - UNLOCK / ROOT / TWEAKS - OS 5.1.1 / 6.0
There go to the [GUIDE] StockROM section , open it up and under #GENERAL you'll find everything you need to know.
Setting up fastboot and how to use it
For windows users
Please checkout this guide on how to use fastboot on windows
If you prefer to keep a low footprint instead of installing the whole Android SDK, take a look at its thread
[TOOL]Minimal ADB and Fastboot [8-28-15]
For Linux users
Installation
Debian based distros (Debian, Ubuntu etc.)
Open a terminal and enter the following :
Code:
sudo apt-get update && sudo apt-get install android-tools*
Confirm the installation by either hitting enter or typing y
Gentoo based Distros (Gentoo, Funtoo, Sabayon, Scientific Linux)
Once you're in a terminal, enter the following:
Code:
emerge dev-util/android-sdk-update-manager
Other distros (Arch, Fedora, Open Suse etc.)
Please find the apropriate packages to install android fastboot tools for your distro
How to use
Open a terminal in the location your .img file is located or cd into that directory like this:
Code:
cd <path to your directory that contains the .img files>
Replace <path to your directory that contains the .img files> with your actuall path
To boot temporarely into a .img (ex recovery) use the following command (replace <your.img> with your .img file) :
Code:
fastboot boot <yourfile>.img
To flash a kernel image enter the following (replace <your.img> with your .img file):
Code:
fastboot flash boot <your.img>
To flash a recovery image enter the following (replace <your.img> with your .img file):
Code:
fastboot flash recovery <your.img>
To exit fastboot enter :
Code:
fastboot reboot
How to install CM 13
Above all - do a Backup of ALL your data
When I write ALL I mean ALL (this includes the data on your micro SD card,
don't come whining to me if you lose your wedding photos/videos, kids' photos/videos or other important stuff !
For optimal experience I'd recommend my built custom kernel (quicker boot times, higher reliability, more tweakability)
General, in-depth instructions
Download one of the newer Z5 AndroPlusKernels v20+ by @AndroPlus from his official website (Scroll down and select Z5, then on AndroidFileHost search for Z5_AndroPlusKernel_Permissive_v2 (v20 - v23) and download it)
Extract the flashable zip-file e.g. Z5_AndroPlusKernel_Permissive_v23.zip
Download our TWRP 3.0.1-0 build for the Z5)
Download the appropriate gapps from below (Can be downloaded on your device)
Download the CM 13 Zip for the Z5 from below (Can be downloaded on your device)
Move the GAPPS zip and the CM 13 to your Z5 if you haven't downloaded them on your device
Power Off your Z5 and wait about 10-15 seconds to make sure it's off
To enter fastboot mode hold VOL UP and while holding VOL UP connect your device to your pc via cable
When the notification LED has turned blue you are in fastboot mode
On your PC flash the boot.img that has been extracted from the Z5_AndroPlusKernel_Permissive_v23.zip using fastboot (
Code:
fastboot flash boot boot.img
)
Now flash twrp-3.0.1-0-E6653-20160403.img by using fastboot (
Code:
fastboot flash recovery twrp-3.0.1-0-E6653-20160403.img
)
Once both of those images have been flashed you can reboot the device like so:
Code:
fastboot reboot
Quickly pull the usb cable from the computer (you can leave the other end in the phone's port)
When booting up wait for the notification light to turn yellow at the Sony logo
Once it has turned yellow, you will enter TWRP by pressing VOL UP (or VOL DOWN - up works more reliably)
If you've missed the step above, reboot your device and try the step above again
Alternatively you can force turn off the device via: Power Button + Volume Up , then turn it on again via Power Button
If TWRP asks you to enable read and write, swipe to continue
Go to settings and lower the max brightness to the minimum or one of the lower levels to preserve energy
In TWRP make a full backup to the microSD in case you want to revert back to stock.
After it has finished, in this case Reboot -> System.
Copy over the TWRP folder from the external microSD to your computer (reason: you might not have access to your external SD or have to reformat it
Thank Microsoft, Sony, etc. for that: "Stock" ROM uses texfat , AOSP, CM, etc. uses exfat, ext4, ntfs
The files on the microSD might get corrupted (filesystem problem) or the microSD going crazy (I already had both cases)
Now Power on your phone and follow the steps again to get into TWRP
Swipe to continue (?)
select Wipe > Advanced Wipe
Now ONLY tick Dalvik/ART cache, System, Cache and Data
WARNING! THE NEXT STEP WILL WIPE YOUR SYSTEM AND DATA, MEANING YOU WILL DELETE YOUR STOCK SONY SYSTEM AND ALL YOUR APPS
(You already DID a Backup of your files so nothing to worry about)
Once you've ticked the correct boxes, swipe to wipe
Once the wipe is complete, return to the main menu and select Install
Locate and select your CM 13 Zip
Select "Add more Zips" and add your GAPPS package and finally swipe to install
Once the installation succeeded you can select "Reboot System"
Wait for CM 13 to boot up (Can take several minutes)
Enjoy CM13
OPTIONAL: You can remove your TWRP backup that is located in the TWRP folder if you feel like you will no longer need it
How to ROOT
In CM 13, enable the developer options
Select Root access
Select Apps Only (Or Apps and ADB if you use ADB)
Done
How to disable the Thermal Manager
Before we start I want to set a few questions and warnings. Disabling the thermal manager will cause you device to run slightly hotter, do this at your own risk.
Let's start out with why you would want to disable the thermal manager. At this point it's not recommended to disable the thermal manager as it has been fixed. However some people still want the max performance out of their device. The average heat without the thermal manager will be roughly the same, if not less compared to the stock ROM with it's thermal manager enabled.
So why is the thermal manager even included if it the device runs mostly fine without it. As most of you already know, the Snapdragon 810 (MSM8994) has overheating problems. The first CM boot after flash is responsible for optimizing apps and android and can become extremely resource hungry at that point. Due to that, the device can heat tremendously! Not only can that cause a panic reboot but it can also damage your device in rare cases. To avoid that issue a thermal manager shrinks down process and slowers the boot animation (That's why the CM logo may lag at first boot).
Enough said, let's get going..
To disable the thermal manager you must do the following :
First enable root access (See "How to ROOT" guide)
Open the CM file manager
Go to settings > General Settings > Access Mode
Select root acess mode
Go back to the file manager
Swipe from left to right or press the menu button in the upper left corner
Select Root folder
Open the folder/directory called etc
Delete thermanger.xml
Reboot
Done
How return back to stock via TWRP backup
Reboot your device
Wait for the notification light to turn purple at the Sony logo
Once it has turned purple, you will enter TWRP by pressing VOL UP or VOL DOWN
If you've missed the step above reboot and try again
If TWRP will ask you to enable read and write, swipe to continue
In TWRP select restore and select your backup, then swipe to restore
Once the restore is done you can select "Reboot System"
If your device hangs at the Sony wave boot animation, force shut down and power your device up again.
Downloads
Latest recommended CyanogenMod release for the Sony Xperia Z5 E6653/E6603 :
6.0.1_13.0-20160626-UNOFFICIAL-sumire_r46_alternate
Latest recommended Kernel for the CM release for the Sony Xperia Z5 E6653/E6603 :
6.0.1_13.0-20160626-UNOFFICIAL-sumire_r46_alternate
All my releases can be found here on : Android File Host
TWRP for CM/AOSP-based ROMs:
[TWRP][E6653/E6603/E6633/E6683] 3.0.2 , for CM/AOSP ROMs
Gapps (Select ARM64 > 6.0) :
Open Gapps
[GAPPS][6.0/5.1/5.0][arm/arm64] Official Slim GApps ( recommended )
XPosed for Android:
[OFFICIAL] Xposed for Lollipop/Marshmallow (Installer in Thread)
XPosed Releases
SuperSU in SystemMode:
SuperSU in System-Mode [v2.65-STABLE] [v2.68-BETA] [v2.70-WIP/BETA-RC]
Sound MODs:
[Sound Mod ][Project DiVA][6.0 MM_Z5 series] KitaKami sound mod Prototype 01 (any effect ?)
A.R.I.S.E. Sound Systems - Auditory Research in Sound Enhancement - Exodus RC8.3 (works (RC8.3))
[SOUNDMOD][JB/KK/LP/MM]Project Yume Final, You are the Legend (needs testing)
[SUPER MOD][4.4+/6.0/N][ v7.5.2 ] XTREMEMusic™ THE SOUND THAT YOU'VE NEVER HEARD! (NOT working (7.4), needs testing of 7.5*
[Audio Mod] eXtremeBeats Aural Maximizer (needs testing)
[APP]Material ViPER4Android 2.4.0.1[Light/Dark][LP/MM]
mpro420 said:
1.)zip file install via twrp.
2.)reboot to system.
3.)enable v4a "write to sdcard" permission in setting/apps/viper4android/permission.
4.)open v4a and gain root permission.
5.)install driver for v4a.
6.)reboot system.
7.)[emoji39]
Click to expand...
Click to collapse
Questions and bug reporting
The following questions will be ignored
Inappropriate questions
Requests for other devices
Forced orders, EX. : "PLS FIX!!!!!!"
ETA's
Often repeated questions or requests usually by the same user
Requests that are out of CM's framework (Ex. Adding Sony Apps)
How to report a bug/issue
Explain exactly what happens
Mention a log if you can (Please use hastebin or any other paste site to keep the thread clean)
If you can't mention a log, explain as precise as possible when, why and where it occurs!
Source Code
All Source Code can be obtained from:
https://github.com/Sony-Kitakami
https://github.com/SonyAosp
https://github.com/sonyxperiadev
https://github.com/CyanogenMod
https://github.com/zachariasmaladroit/android_kernel_sony_msm8994_kitakami_r2
Kernel Source code can be obtained from : zachariasmaladroit/android_kernel_sony_msm8994_kitakami_r2
We gladly accept any developers that are willing to contribute to this project! Please PM @CTXz if you are interested in joining this project!
Build from Source
http://forum.xda-developers.com/xperia-z5/general/guide-build-cm13-source-z5-z5c-z5p-t3357040
Screen Shots (Z5 compact)
XDA:DevDB Information
CyanogenMod 13 for the Sony Xperia Z5 E6653 and E6603, ROM for the Sony Xperia Z5
Contributors
CTXz, Moonbutt74 , zacharias.maladroit , oshmoun , infected_
Source Code:
https://github.com/Sony-Kitakami
https://github.com/SonyAosp
https://github.com/sonyxperiadev
https://github.com/CyanogenMod
https://github.com/zachariasmaladroit/android_kernel_sony_msm8994_kitakami_r2
ROM OS Version: 6.0.x Marshmallow
ROM Firmware Required: 6.0 Recommended
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2016-04-11
Last Updated 2016-06-28
Changelog
Code:
2016/05/06
[LIST]
[*]Dual SIM support (ROM) [COLOR="Red"][B][WIP][/B][/COLOR]
[*]Dual SIM support (Kernel) [COLOR="Red"][B][WIP][/B][/COLOR]
[*]smoother brightness (automatic & manual), lower default and manual brightness
[*]weather provider support (CM)
[*]thermal manager improvements (CM)
[*]potential stability-fixes (CM)
[*]brightness dimming disabled (once temperature raises)
[*]VCM2 camera actuator (presumably working focus) == feature complete camera [LED torch still needs work]
[*]adb enabled from the start (diagnostics at this early ROM stage)
[*]upstream ROM + Kernel changes
[*]
[*] Sim-specific change: add DSDS (dual sim) detection script that starts second ril-daemon
[*]
[*] Custom Kernel changes:
[*] Intelliplug + Intellithermal by default [[B][COLOR="Red"]stability testing[/COLOR][/B]]
[*] added Quick Wakeup, PowerSuspend,
[*] added AdrenoIdler
[*] CPU and general Kernel optimized compiler flags
[*] re-enabled efficient WorkQueue [[B][COLOR="Red"]stability testing[/COLOR][/B]]
[*] re-enabled nop idle governor for CPUIDLE driver [[B][COLOR="Red"]stability testing[/COLOR][/B]]
[*]
[/LIST]
2016/04/19
- LiveDisplay (CM upstream) should work more reliably and should not cause instabilities and (boot)loops anymore
- torch should work now (ROM)
- changes, improvement to Bootup (Kernel side) - should make prebuilt kernel more reliable
2016/04/17 [suzuran]
- Fixed Brightness
- Fixed Torch
- Fixed Double Tap 2 Wake
- Added CPU core optimization
- Added USB gadget support
- Synced with the latest CM sources
-----------------------------------------------
* For devs
- Added Kitakami patcher to manifests
2016/04/15
- Full brightness range + maximum brightness (ROM + Kernel)
- KCAL support (Kernel)
- alucard, elementalX, zzmoove governors (Kernel)
- upstream sync (Kernel), perhaps better, more reliable WiFi
- more battery efficiency during video playback (Kernel), [needs testing, lags ?]
- adreno (GPU) governor, lower default frequency (Kernel), perhaps lower battery consumption, [needs testing, lags ?]
- vibrator intensity control (Kernel) [needs testing]
- some more battery efficiency tweaks (Kernel)
- NTFS, exFAT filesystem support (for microSD) (Kernel)
- tweaks and reliability improvements (Kernel)
- Driver wakelock control (Kernel)
- NEON/FPU compiler optimizations (Kernel)
- improved Hotplug reliability and stability (Kernel)
2016/04/12 [suzuran]
- Fixed sdcard recognition
- Updated binaries to v4
- Released CM build guide
- Synced with newest sources
2016/04/11
- CM 13 For the Z5 E6653 Released
2016/04/10
- CM 13 For the Z5 Premium E6853 Released
2016/04/05
- Fixed GApps
- Partially fixed Bluetooth
- Synced to latest CM sources
2016/03/27
- Fix thermal manager lag
- Fix NFC
- Updated kernel configs
- Added ffmpeg codecs support
- Synced with newest CM sources
-------------------------------------------
* For devs
- Cleaned up suzuran and satsuki tree
- > Moved common media configs to kitakami common tree
- > Moved acdb files to vendor tree
2016/03/24
- Fix In-call Mic
- Add support for the E5803
- Add option to boot into recovery (On purple LED at Sony logo press VOL UP or VOL DOWN to enter recovery)
- Update Thermal manager
- Merge latest AOSP kernel commits
- Sync to newest CM source
2016/03/22
- Fix microphone
- Add settings for camera button
- Add settings for volume rockers
- Fix sound on calls
2016/03/20 - RIP TonyStark, you were a great moderator and we'll all miss you.
- Added Thermal regulation to avoid overheating problems
- Fixed Red flashy frames
- Fixed RIL (SIM detection)
- Fixed Dex pre-optimization
- Fixed Camera
- Fixed Sensors
- Fixed Crash after locking device
2016/03/18 - CM 13 For the Z5 Compact E5823 Released
Reserved 02
Reserved 03
(and another one)
You know the drill:
the most important part is the phone functionality (well, it's a smartphone ),
please test that after you've done the initial set-up and tell, whether it works
Finally get there....
Great job man!
Hope there will be dual sim support asap.
Nice jobe, I'll wait for a more stable version to test it
keep up the good work
best regards.
Well done again to Sony Kitakami Developer Organization!
Sooooo much time and effort represented in those CM13 github projects. Total Respect.
Nuf said.
JerryLaiHMmmmmm said:
Finally get there....
Great job man!
Hope there will be dual sim support asap.
Click to expand...
Click to collapse
I've taken a look but haven't figured out yet on how to make it work,
if there are any developers out there with DSDS (dual sim) devices, interested on getting this working and read this - please take a look at it
Thanks !
korom42 said:
Nice jobe, I'll wait for a more stable version to test it
keep up the good work
best regards.
Click to expand...
Click to collapse
Okay
Thanks
Joeisgood99 said:
Well done again to Sony Kitakami Developer Organization!
Sooooo much time and effort represented in those CM13 github projects. Total Respect.
Nuf said.
Click to expand...
Click to collapse
Thanks ! <3
Will you be making a guide on building this rom from source? And of course, thank you for all your hard work we all greatly appreciate it.
Uclydde said:
Will you be making a guide on building this rom from source? And of course, thank you for all your hard work we all greatly appreciate it.
Click to expand...
Click to collapse
Very soon mate
Uclydde said:
Will you be making a guide on building this rom from source? And of course, thank you for all your hard work we all greatly appreciate it.
Click to expand...
Click to collapse
Build from Source
The guide on how to build your own Z5 ROM will be posted once we feel like this ROM is ready enough
Click to expand...
Click to collapse
Take a look at the source and the repos, the guides are out there ...
... you got a PM
CTXz said:
Very soon mate
Click to expand...
Click to collapse
beat me to it
zacharias.maladroit said:
[ROM][UNOFFICIAL][6.0.1][E6653/E6603] CyanogenMod 13 for the Sony Xperia Z5 [ALPHA]
if you loose your wedding photos/videos,
Click to expand...
Click to collapse
If it's "loose", put some glue on it!
lol
m3ta said:
If it's "loose", put some glue on it!
lol
Click to expand...
Click to collapse
lol - I get those mixed up quite a bit, sometimes due to typos, too
Status Update:
Uploaded new img files and a flashable zip-file for TWRP (haven't tried it out myself, currently evaluating Resurrection Remix)
Sorry for the inconvenience so far
Give it a try, if you dare
Okay, so I followed the steps for "General installation", and the rom is surprisingly smooth. The only issue I've noticed that isn't addressed in the original post is that vibration intensity is WAY higher than in the stock rom. Like it's actually pretty loud. I know it's a minor issue compared to some of the other things, but I'm just throwing that out there. I'll point out anything else I find.
Absolute legend! Thanks man. I'll get to testing once i get home off this drilling rig
Uclydde said:
Okay, so I followed the steps for "General installation", and the rom is surprisingly smooth. The only issue I've noticed that isn't addressed in the original post is that vibration intensity is WAY higher than in the stock rom. Like it's actually pretty loud. I know it's a minor issue compared to some of the other things, but I'm just throwing that out there. I'll point out anything else I find.
Click to expand...
Click to collapse
Thanks for testing
Actually it already was higher on AOSP, if recall correctly, but I'll ask the other devs if they noticed something out of the ordinary
Thanks
atanu89 said:
Absolute legend! Thanks man. I'll get to testing once i get home off this drilling rig
Click to expand...
Click to collapse
Thanks
Thanks for this great rom, the only problem i encounter is that my phone keeps stuck in first startup (cyanogenmod logo) and that keeps going i force my phone to switch off after 45 minutes, is there something i do wrong i followed the in depth guide
Sovjet-Command said:
Thanks for this great rom, the only problem i encounter is that my phone keeps stuck in first startup (cyanogenmod logo) and that keeps going i force my phone to switch off after 45 minutes, is there something i do wrong i followed the in depth guide
Click to expand...
Click to collapse
That partially is caused by the "stock" built kernel,
you can see whether is improved by flashing my custom kernel.
One observation (according to @moonbutt74 afaik) led to the conclusion that the upstream (from sonyxperiadev) setting of coherent_pool=8M doesn't match with Sony's ("Stock ROM") setting of coherent_pool=2M,
and does no good for startup time (and reliability ?).
Another factor (like in most AOSP-based ROMs, Kernels) is that the kernel was built with a less tuned toolchain (gcc),
can't directly explain though why does leads to exactly that behavior.
Tl;dr:
Give the custom kernel a try - the "stock" kernel should work but for some reason sometimes it does not
custom has exfat + ntfs support to make microSDs work reliably and other things
Thanks
Code:
/*
* Your warranty is not void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* make sure you are aware of any risks associated with using the options in
* the toolkit BEFORE using it! YOU are choosing to use this toolkit, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Do you want to unlock your bootloader and root? Or switch to another ROM? Are you asking yourself which one of the 100s of guides here on xda should I use? Well no need for any guides! Use this toolkit and be bootloader unlocked and rooted or on a different ROM within MINUTES! Super simple to use, just a couple of clicks and the toolkit does everything else!
COMPATIBILITY
Supports A2017, A2017G, and A2017U (all software builds)
Windows 7 and up
FEATURES
- Automatic file downloads with hash verification
- OTA updates
- ADB and Qualcomm EDL driver Installation
- ADB and Fastboot Test
- Backup apps+data
- Restore apps+data
- Backup system/data/boot partitions
- Restore system/data/boot partitions
- Unlock bootloader on ALL software builds (Marshmallow and Nougat) without voiding your warranty!
- Lock bootloader
- Flash TWRP and disable dm-verity and forced encryption
- Root with SuperSU
- Restore to stock/ Recover from hard bricking with EDL restore packages
- Flash an unlimited amount of ROM, kernel, and other zips at once!
-Magisk root (Coming soon)
-Unroot (Coming soon)
-Remove ZTE bloatware (Coming soon)
DOWNLOAD
You may need to disable your antivirus as the EXE file may get quarantined or removed due to "malware". This is because of the BAT to EXE compiler used and is a false positive. More information available here: [url]https://superuser.com/questions/1117747/why-do-av-software-thinks-that-all-compiled-batch-files-are-viruses[/URL] (read the answer)
CREDITS
ZTE of course for the Axon 7
Google for Android
@Unjustified Dev for being the reason why there is any development in the first place
@Koush for Universal ADB Drivers
@Dees_Troy and @jcadduono for TWRP
Xiaomi for MiFlash
@jcadduono for MiFlash method and A2017U packages
@djkuz for A2017 and A2017G MiFlash packages
@Chainfire for SuperSU
@WugFresh for his awesome Nexus Root Toolkit and inspiring me to make one for the Axon 7
Anyone on Stack Overflow who helped me with batch commands
AFH for hosting setup files
Github for hosting masterlist files
Any one else who I forgot to mention (sorry)
And of course...me!
Please make sure you are aware of any bugs/issues BEFORE trying any of the toolkit options!(4th post)
XDA:DevDB Information
Axon7Toolkit, Tool/Utility for the ZTE Axon 7
Contributors
bkores
Version Information
Status: Stable
Current Stable Version: 1.2.1
Stable Release Date: 2017-09-04
Created 2017-03-14
Last Updated 2017-10-16
FAQs and Troubleshooting
I want to switch to [insert ROM name]How?
1) Use the Install Drivers option
2) Use the ADB+Fastboot test option to test the ADB and fastboot drivers
3) Use the backup apps+data option
4) Use the bootloader unlock option
4) Download the ROM of your choice, along with gapps (such as Opengapps arm64 7.1) and anything else you want to flash. Make sure you download the universal bootloader and modem for your variant as well from the lineage thread otherwise THE ROM WILL NOT FLASH!
5) (optional) Use the Flash TWRP option.
6) Use the flash zips option to flash the ROM along with everything else
7) (optional) Use the root option.
Profit!
The adb restore apps+data option did not work on my device.
Unfortunately, this is a ROM issue as some ROMs have broken backup managers. There is no other way to restore the backup through the adb way, however there is a way to restore a backup on the device. This method requires an unlocked bootloader and root. It also requires a paid app.
1) Download Titanium Backup from the Play Store: [url]https://play.google.com/store/apps/details?id=com.keramidas.TitaniumBackup[/URL]
2) Download the Pro key. It costs $5.99 US but the app itself is extremely worth it (from my experience) : https://play.google.com/store/apps/details?id=com.keramidas.TitaniumBackupPro&hl=en
3) Open up the app on your device. You should get a Superuser request popup. Tap `Grant`.
4) Connect your device to your computer with the factory USB-C cable. Open a command window anywhere by holding down shift and then right clicking. Click on 'Open command window here' from the menu options.
5) Execute the following command to push the backup file to your internal storage:
Code:
C:\Axon7Development\Axon7Toolkit\adb push filepath /sdcard/
where filepath is the location and name of your backup such as C:\Axon7Development\Axon7Toolkit\backups\my-backup.ab
6) If there is no menu option in the app execute the following command to emulate a "menu" key press:
Code:
C:\Axon7Development\Axon7Toolkit\adb shell input keyevent 82
This should bring up Titanium Backup's menu options.
7) Scroll down to 'Extract from ADB backup' and select it. This will bring up a list of "Open with" options. Choose any installed file manager on your device, such as the one pre-installed with the stock ROM or a third-party file manager such as ES File Explorer.
8) Navigated to the /storage/emulated/0 directory and find your backup file and select it.
9) Restore the backup on your device.
The partition restore option did not work on my device.
Follow the instructions above but use the 'Extract from Nandroid backup' option instead.
My device is stuck on an 'Enter your password to start Android' screen.
Unfortunately this requires a factory reset.
1) Boot your device into recovery mode by pressing and holding the power and volume up buttons for 10-15 seconds.
2) Stock Recovery: Use the volume down key to go down to 'Wipe data/factory reset' and press power to select. Press the volume down key again to go down to 'Yes' and press power to select.
TWRP Recovery: Tap "Wipe" < Tap "Advanced Wipe" < Check the box next to "data" < Tap "Repair or change file system" < Tap "EXT4" < Swipe to confirm.
3) Reboot your device.
The download of a file keeps failing even though I am definitely connected to the Internet.
-There may be problems with the link or server, usually in the event of high traffic. In this case use the import option. Please let me know if this happening for longer than 24 hours so I can investigate it.
-If you are on versions 1.0.0-1.1.1 the download agent is outdated. Download and run the fix here: [url]https://drive.google.com/open?id=0B2VBJePGznYjdXNUUkY5UzFJTm8[/URL]
Can I access the source code?
No.
Changelog
v1.2.1
-New design
-Added back Driver Installation option
-Added back variant auto-detection
-Added android version auto-detection
-Fixed adb backup save location/name bug
-Remove system apps backup option for better chance of successful adb restore
-Fixed system partition restore bug
-Fixed flash zips option
-Fixed "boot failed" error
-Fixed bootloader lock brick for some users
-Fixed Android Marshmallow compatibility issues
-Other minor enhancements and bug fixes
v1.2.0
-Dropped support for Windows XP and Vista
-All drivers now installed during setup
-New popup design and system
-Revised some popups with more helpful information
-Revised and removed some notifications
-Faster launch (~15 seconds)
-Minimized use of temp files
-Completely new downloader with new UI, integrated hash verification, fixed hash mismatch bug, revised import option, and option to override hash verification
-Downgraded adb version to 1.0.36 to fix toolkit hang bug for some users
-Updated download agent (wget) to latest version
-Completely new updater with automatic installation and logging
-New simplified toolkit: removed Advanced Utilities and Driver Installation/Test
-Added emulator check on startup to prevent conflicts
-Build no longer required, just variant
-Added ADB+Fastboot Test option
-Added Flash TWRP option
-User can now set backup name and location for the backup options, default path is the toolkit's backup folder
-Fixed restore apps+data(ADB) option
-Revised miflash unlock package (it's the A2017G unlock package from the Russian forum)
-New toolkit UI
-Fixed numerous minor bugs
-Minor enhancements
-Updated MiFlash to latest version
-EDL connectivity checking and driver replacing now done by the toolkit
-Implemented more error checking
-Toolkit will launch FileDependencyChecker instead of exiting if file dependency is missing
-Fastboot and aboot images will be reflashed before bootloader lock to guarantee success
-Added A2017G B10 for restore stock option
-Added A2017U B19 for restore stock option
-Fixed bugs with restore stock option
-Fixed wipe system and data loop bug for flash zip option
-Fixed toolkit crashing when choosing file with spaces or special characters in path or name for import
-Zips no longer need to be imported for flash zip option, the toolkit can now use the original path
-Cache and dalvik now wiped automatically for all zip flashing
-Added limit download rate for downloader to settings
-Added view most recent update log to settings
-New uninstaller
v1.1.1
-FULL SUPPORT FOR A2017G! This means if you are on the G variant you can now UNLOCK YOUR BOOTLOADER and (in the future) RESTORE TO STOCK!
-Miscellaneous bug fixes
-Fixed "hashcheck mismatch" bug when importing a file dependency
-Added FAQs & Troubleshooting option
-Option to auto-detect device variant/build on startup
-Minor improvements to UI and options
-NEW ADVANCED OPTION! Bugreport generator
-Added options to filter log output by verbose, debug, info, warning, error, fatal or silent for Logcat generator
-Fixed unable to uninstall toolkit from Settings
-System write protection is now automatically disabled for root option
-Fixed incorrect canceling of download dependencies when inputting cancel option after failed download or hashcheck mismatch
v1.1.0
-Added support for B19_N
-Full support for A2017! This means those of you with the Chinese variant can now unlock your bootloader and restore to stock B13! (Set your build to "Any A2017")
-Option to choose "Any" build for A2017G variants or unsupported builds
-Fixed inability to change theme and build in settings
-THE MIFLASH ISSUE IS COMPLETELY FIXED! THIS MEANS THAT THOSE OF YOU HAVING TROUBLE USING MIFLASH FOR THE BOOTLOADER UNLOCK AND RESTORE TO STOCK OPTIONS THEY WILL NOW WORK!!!
-Option to skip ADB check for bootloader unlock & restore to stock options if your device is already in EDL mode
-Cache and dalvik will now be wiped automatically when flashing zips
-Removed all powershell commands for better compatibility
-Added option to wipe system and data before flashing a Custom ROM zip
-NEW OPTION! Support for twrp adb backups and restore in TWRP 3.1.0
-Changed the "Flash TWRP and/or root" option to just "root". If you want to flash TWRP permanently, use the fastboot flash recovery option in Advanced Utilities
-minor enhancements to UI and options
-B29 added as restore stock option along with B15_N with @jcaudanno's MiFlash package and @DrakenFX's TWRP package for A2017U
-Screenshots and screen recordings are now pulled from device to PC
-Added rotate 90 degrees and verbose logging options for screen record
-Option to backup system and shared storage applications for adb backup
-Downgraded ADB version to 1.0.31 and revised syntax to fix adb backup issues
-completely new ADB check method to prevent false "device connected" for instances when device is not actually connected
-Downloader will now launch the AFH download page of all dependencies instead of the direct download link for failed file dependency
downloads in case the direct download link is no longer working
-Updater will now launch the AFH download page for all toolkit versions if downloading of the update package fails
-List connected devices option now shows device state in addition to serial number for ADB
-NEW ADVANCED OPTION! ADB logcat
v1.0.2
-fixed syntax errors for flash zip option
v1.0.1
-fixed application closing during fastboot check for bootloader unlock option
v1.0.0
-Initial release
Bugs/Issues:
-TWRP gets stuck in loop when wiping system for flash zips option if system is mounted read-only
Thanks man. It's good to see more developers for Axon 7.
Cool, will probably check it out later. You should post up some sceenshots so we can see how it works.
Just one thought, does bootloader lock warn user to have untouched system? Lots of people lock on custom rom/modified stock for some reason.
lafester said:
Cool, will probably check it out later. You should post up some sceenshots so we can see how it works.
Just one thought, does bootloader lock warn user to have untouched system? Lots of people lock on custom rom/modified stock for some reason.
Click to expand...
Click to collapse
Yep. You'll get a popup that says you have to be complete stock to use it otherwise you'll be hard bricked.
I kinda wish we'd scrap all of the unlock and recover methods and just have all of the devs making threads to just resort to a Wugfresh tool like this. Any way to make unlock/locking/restoring/recovering hands off and safe would really help a lot of us out.
We could implement a bunch of backing up, signature verifications, and delays before steps occur so it's more foolproof and not have to rely on timing of key combinations and picking which file to use for whatever.
Here are some screenshots i just took. Thanks for your work on this, bkores.
http://imgur.com/a/qS4Ib
sm.bxsq said:
Here are some screenshots i just took. Thanks for your work on this, bkores.
http://imgur.com/a/qS4Ib
Click to expand...
Click to collapse
Thanks. You beat me to it lol.
Also, since you're using it please let me know of any bugs or improvements. Thanks!
Wow, nifty. Thanks, man.
Thanks for providing this to the community! Good work!
I'm planning to release a new version soon with support for adb backups in TWRP, restore to stock using TWRP, and an option to restore to B29 in edl for those who don't want B15.
Stay tuned
This does not seem to be working for me. When attempting to unlock the bootloader the application puts my phone into fastboot mode, and closes. ZTE Axon 7 factory nougat upgrade (B15). Have downloaded the MiFlash application as requested, but option 4 just places my phone into fastboot mode and then the application just exits.
Phone will now only boot to Team Win asking for a password (I didnt have a password set). Looks like my phone may be dead.
wyrethewolf said:
This does not seem to be working for me. When attempting to unlock the bootloader the application puts my phone into fastboot mode, and closes. ZTE Axon 7 factory nougat upgrade (B15). Have downloaded the MiFlash application as requested, but option 4 just places my phone into fastboot mode and then the application just exits.
Phone will now only boot to Team Win asking for a password (I didnt have a password set). Looks like my phone may be dead.
Click to expand...
Click to collapse
Hold on let me look into this.
@wyrethewolf The issue has been fixed. I'll upload the new version as soon as possible. For the time being if you are in TWRP you should be able to boot to system by pressing cancel on the decryption screen and then going to Reboot<System.
It was a tiny typo in the fastboot check which screwed up the entire script lol.
bkores said:
@wyrethewolf The issue has been fixed. I'll upload the new version as soon as possible. For the time being if you are in TWRP you should be able to boot to system by pressing cancel on the decryption screen and then going to Reboot<System.
It was a tiny typo in the fastboot check which screwed up the entire script lol.
Click to expand...
Click to collapse
Thank you, I will give this a try. Thank you for checking in on this!
New version is up! This should *hopefully* fix the application closing issue with the bootloader unlock option.
If you already have the toolkit, no need to download this one. It'll automatically be downloaded when you launch the toolkit.
Also if you get any errors of failing to close adb.exe during installation just press ignore. I've already fixed this for future releases.
@wyrethewolf tell me if the update fixed the issue. Thanks!
@bkores thanks for all you hard work
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
AOKP-Android Open Kang Project
For Huawei P9 Lite
DONOT COPY MY WORK, Ask for Permissions or Gather it yourself,,,
This ROM is only for Firmwares based on EMUI 5.X only...
Code:
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm
* App failed. Please do some research if you have any concerns
* about features included in this ROM before flashing it,
* YOU are choosing to make these modifications, and if you
* point finger at me for messing up your device, i will laugh at you.
*
*/
Introduction:
What is AOKP ?
AOKP stands for Android Open Kang Project. It is a custom ROM distribution for several high-end Android devices. The name is a play on the word kang and AOSP (Android Open Source Project). The name was sort of a joke, but it just stuck, just like our infatuation with unicorns.
We fork the source code of Android that Google puts out in the open with every major version release, and we then add the magical unicorn bytes (read: we add some of the coolest features that are both useful and make your ROM awesome).
With AOKP, you can generally do a lot more with your device than what you could do with the original firmware that came installed on it.
Click to expand...
Click to collapse
Features of AOKP:
*Unsecure boot.img (stock AOSP kernel)
*Superuser & Busybox preinstalled
*Deodexed
*180 Degree rotation
*Built in performance/init.d configuration (Thanks Kejar & company)
*CM Launcher/ Power Menu
*CM Brightness slider
*Custom color for anything in RC
*Clock Color/Location: Right, Center, Disable
*Battery Icon/ Color Picker: CircleMod, Bar, Text Only, Icon Only, Icon+Text or None
*Battery Bar in Status Bar or Nav Bar, Bar Thickness, Charging animation
*Nav Bar Transparency
*Nav Bar Button Reorder: Back-Home-Search-Menu
*Nav Bar Color Picker
*Nav Bar Button Glow Duration: Off, Fast, Slow
*Nav Bar: Long press to Search button
*Nav Bar Hide on Lockscreen
*Toggles in Pull Down Menu: Auto rotate, Bluetooth, GPS, Wi-Fi, Aiplane mode, Vibrate, Silent, Sync, Data, 4G, Tethering, Torch, *Brightness
*LCD Density (Careful with this)
*Menu Button location: Right, Left, both, Remove
*Menu Button Visability: Always show, Always show Invisible Icons
*Lockscreen Style: Quad, Octo, Stock
*Lockscreen SMS customizable shortcut
*Lockscreen Horizontal Option
*Performance Menu: (Use With Caution) Max/ Min CPU, Scaling Governor
*Unlock Sceen with Legacy Menu Icon
*Volume Key to Wake Screen
*Volume Key to Skip Tracks
*Long-press back button to kill process
*Disable CRT off animation
*LED pulse settings (time on/off)
*ICS ringtones/notification sounds
*Customize carrier text to whatever.
*Power Menu options: Boot to recovery/ Boot loader, Reboot, Screenshot
*Facebook contact sync integration (must wipe to get this)
*Disable Boot animation
*Keyboard: Volume keys act as a cursor while typing -- disable in keyboard options
*Long press home for recent apps (thanks brucekey)
Installation Instructions:
* -- AOKP only supports TWRP recovery. Use any other recovery at your own risk.
* -- AOKP only supports EliteKernelReborn. I will not provide support for those using other kernels.
* -- Download the Latest AOKP 7.1.2 from 2nd Post...
* -- Delete all your Fingerprints from Stock or Elite ROM.
* -- Ensure the latest version of TWRP Recovery is installed.
* -- Ensure that Stock/unmodified P9 Lite vendor is installed... (if you are on Elite ROM, any version, you are on stock vendor)
* -- Do Complete TWRP Backup...
* -- Wipe only Data, Dalvic, Cache, System... Dont touch other Partitions...
* -- Install AOKP 7.1.2
* -- Install GApps (optional)
* -- Install SuperSU or Magisk (optional)
* -- Reboot with Pray
Click to expand...
Click to collapse
Bugs:
You tell me
READ FAQ in 4th Post to fix common things then post for new issues if you got one...
If You are having RIL Disconnecting issue, Please Flash your Original CUST Partition.... (Elite ROM has different Region CUST)
This took Countless hours to get ready... If you like it, Please Support by Donation
Special Thanks:
@Meticulus for creative & Endless work on Nougat & MM Codes.... Hats off bro...
@petya230 for his support
@felix-development for his support
Source Codes:
AOKP Source Codes
GPLv2: https://github.com/HassanMirza01/android
Contributors:
@HassanMirza01
ROM OS Version: AOKP 7.1.2
ROM Kernel: EliteKernelReborn v6+ Upstreamed to 4.1.46
ROM Firmware Required: Bootloader Unlocked / TWRP / EMUI 5.X Firmware
Based On: AOKP
Version Information:
Status: Stable
Created on: 2017-12-06
Last Updated on: 2018-02-07
Download Links:
AOKP:
aokp-7.1.2-20180207-hi6250-UNOFFICIAL-HassanMirza01
aokp-7.1.2-20171205-hi6250-UNOFFICIAL-HassanMirza01
All my ROMs are available on my Blog too,,, HassanMirza01.blogspot.com
Elite TWRP Project
Press Thanks and donate if you like it
CHANGELOG:
2018-02-07 aokp-7.1.2-20180207-hi6250-UNOFFICIAL:
*Updated Security Patch
*Added vulkan Support
*Bluetooth: possibly fix BLE (Bluetooth Low Energy)
*Fix bug which always made performance the effective power profile
*Add config for VOLTE on provision.(Not Tested)
*Fixed inputchannel crash/soft-reboot
*Added BLL Support
*Ril Fixed...
*Updated to December Security Patch
*OTG automatic now...
*Kernel Upstreamed to 4.1.46
*P10 Lite Support Added
*More tweaks and improvements
2017-12-06 aokp-7.1.2-20171205-hi6250-UNOFFICIAL:
*initial release
FAQ:
1.) What to do if My Phone got bootloop or not booting ??
You have changed vendor, or modified vendor(not stock), OpenKirin vendor will never ever work,, so get Pure stock vendor of your device... it will work for sure... if still not, change you data filesystem...
2.) What to do if my SIMs are not working ??
Go to Extras, disable dual sim, reboot phone,, now read carefully,,
1. Install hex editor app from playstore
2. Make sure you have file explorer with root privileges
3. Open hex editor and find modem,id file on this location root/sys/firmware/devicetree/base/hisi,modem_id and open it.
4. Write down all numbers in first row
5. Then go to root/system/vendor and find phone.prop and open it with text editor.
6. Find your modem id by using search and type 0x3xxxxxx where X is your number from hex reader
7. Then make it look like this:
3.) What to do if my SafetyNet is not passed ??
Update Magisk to latest beta version, tick Magisk Hide and enable usb debugging...
reserve4
GREAT!
---------- Post added at 01:05 PM ---------- Previous post was at 01:04 PM ----------
so i can flash this rom from stock rom? Or from any your elite roms?
i have problem- bootloop. System file is changed...
Sim not working here p8 lite 2017
HassanMirza01 said:
reserve4
Click to expand...
Click to collapse
Where are credits to Meticulus? You copied his extra settings and source
Coolyou said:
Where are credits to Meticulus? You copied his extra settings and source
Click to expand...
Click to collapse
First post in SPECIAL thanks???
Odoslané z HUAWEI VNS-L01 pomocou Tapatalku
Coolyou said:
Where are credits to Meticulus? You copied his extra settings and source
Click to expand...
Click to collapse
First of all, i think you dont need to bother yourself...or me....
And 2nd thing, i assume that you didnot read whole OP carefully
Hi, First Big Big thanks for this awesome rom.
My device is GR5 Mini. NMO-L31C636
wipe data, dalvik, cache, system.
flash rom, Reboot.. But not booted.
Then reboot recovery.
Format data. (Now data is automatically f2fs.)
Reboot recovery & change the file system to ext4.
Reboot recovery then reboot system.
Now the device booted.. (Me & My 3 years old son like the boot Animation...... He want's this type of Horse now....)
Now booted. All is very fast & smooth.
Video cam working great. But I have some question :
01. As per op, Busy box pre installed. But with busy box checker " no busy box found", Is it OK? ( need Busy box for Viper4 ? )
02. Pc Suit "allow this device....." authorization is not showing.
So after connecting with computer, Pc suit connected with device, without enable file transfer. I can access contacts, apps, message. But can not access internal / external Sd card.
If I enable file transfer, pc suit disconnected. No Device showing, Restart both Pc & Device several times.
What can I do? Thanks.
Anonda said:
Hi, First Big Big thanks for this awesome rom.
My device is GR5 Mini. NMO-L31C636
wipe data, dalvik, cache, system.
flash rom, Reboot.. But not booted.
Then reboot recovery.
Format data. (Now data is automatically f2fs.)
Reboot recovery & change the file system to ext4.
Reboot recovery then reboot system.
Now the device booted.. (Me & My 3 years old son like the boot Animation...... He want's this type of Horse now....)
Now booted. All is very fast & smooth.
Video cam working great. But I have some question :
01. As per op, Busy box pre installed. But with busy box checker " no busy box found", Is it OK? ( need Busy box for Viper4 ? )
02. Pc Suit "allow this device....." authorization is not showing.
So after connecting with computer, Pc suit connected with device, without enable file transfer. I can access contacts, apps, message. But can not access internal / external Sd card.
If I enable file transfer, pc suit disconnected. No Device showing, Restart both Pc & Device several times.
What can I do? Thanks.
Click to expand...
Click to collapse
No busybox there ?? Weird.... May be its in rom control to install manually... Didnot search that much... And about 2nd issue, u can do one thing at one time... Try to see if usb debugging option have the option of debugging in charge only mode or like that...
Is the nfc,sim,bluetooth, and 60fps video playback working ??
Wiguna said:
Is the nfc,sim,bluetooth, and 60fps video playback working ??
Click to expand...
Click to collapse
Yes... We are not OpenKirin.... we are working on different codes... And those bugs are not present in our builds....
HassanMirza01 said:
No busybox there ?? Weird.... May be its in rom control to install manually... Didnot search that much... And about 2nd issue, u can do one thing at one time... Try to see if usb debugging option have the option of debugging in charge only mode or like that...
Click to expand...
Click to collapse
Hi Hassan, Before connect to Pc, usb debugging option changed to MTP. Hisuit not connected.
then charging mode, hi suit connected. But no access on internal or external sd card.
PTP mode, Here I can access only internal Sd card DCIM & Picture folder. I can paste anything here. But sd card not accessible.
Need the "always allow hisuit ......" authorization required.
Anonda said:
Hi Hassan, Before connect to Pc, usb debugging option changed to MTP. Hisuit not connected.
then charging mode, hi suit connected. But no access on internal or external sd card.
PTP mode, Here I can access only internal Sd card DCIM & Picture folder. I can paste anything here. But sd card not accessible.
Need the "always allow hisuit ......" authorization required.
Click to expand...
Click to collapse
hisuite will never work as u dont have hisuite switch in roms other than emui,,,
Anonda said:
Hi, First Big Big thanks for this awesome rom.
My device is GR5 Mini. NMO-L31C636
wipe data, dalvik, cache, system.
flash rom, Reboot.. But not booted.
Then reboot recovery.
Format data. (Now data is automatically f2fs.)
Reboot recovery & change the file system to ext4.
Reboot recovery then reboot system.
Now the device booted.. (Me & My 3 years old son like the boot Animation...... He want's this type of Horse now....)
Now booted. All is very fast & smooth.
Video cam working great. But I have some question :
01. As per op, Busy box pre installed. But with busy box checker " no busy box found", Is it OK? ( need Busy box for Viper4 ? )
02. Pc Suit "allow this device....." authorization is not showing.
So after connecting with computer, Pc suit connected with device, without enable file transfer. I can access contacts, apps, message. But can not access internal / external Sd card.
If I enable file transfer, pc suit disconnected. No Device showing, Restart both Pc & Device several times.
What can I do? Thanks.
Click to expand...
Click to collapse
How to you repair sim export? When i open modem,id it look like: https://zapodaj.net/853691ec0b8b1.png.html
Can you help me?
HassanMirza01 said:
hisuite will never work as u dont have hisuite switch in roms other than emui,,,
Click to expand...
Click to collapse
I will uninstall hisuit and try again.
1. Adb shows device is offline.
Then what should I do?
Confirming, very very fast ROM, no lagging. Huge customization option.
Viper working great, without flashing Busy box.
2. Did not find manually busybox install option.
Is it required/necessary to flash busybox with twrp?
Anonda said:
I will uninstall hisuit and try again.
1. Adb shows device is offline.
Then what should I do?
Confirming, very very fast ROM, no lagging. Huge customization option.
Viper working great, without flashing Busy box.
2. Did not find manually busybox install option.
Is it required/necessary to flash busybox with twrp?
Click to expand...
Click to collapse
Which busybox App you use?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PixelExperience for Pixel 5a Barbet
What is this?
PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 13
Whats working?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FM radio
Fingerprint reader
Face unlock
NFC
Lights
Sound/vibration
Known issues
Nothing yet
You tell me
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
Downloads:
OFFICIAL:
https://download.pixelexperience.org/barbet
UNOFFICIAL:
Standard
PixelExperience_barbet-13.0-20230109-0542-UNOFFICIAL.zip
drive.google.com
Plus ver.
PixelExperience_Plus_barbet-13.0-20230109-0353-UNOFFICIAL.zip
drive.google.com
Stay tuned
Our Official Telegram channel
Our blog
Install PixelExperience on barbetWARNING: I copy and pasted thes instuctions. Please go to the offical guide for your device Barbet https://wiki.pixelexperience.org/devices/barbet/install/
WARNING: These instructions only work if you follow every section and step precisely.
Do not continue after something fails!
Basic requirements
Read through the instructions at least once before actually following them, so as to avoid any problems due to any missed steps!
Make sure your computer has adb and fastboot. Setup instructions can be found here.
Enable USB debugging on your device.
warning
WARNING: Before following these instructions please ensure that the device is on the latest Android 13 firmware.
This is not necessarily the newest available version! Please up- or downgrade to the required version before proceeding (guides can be found on the internet!).
Flashing the vendor boot partitionwarning
WARNING: This platform requires the vendor boot partition to be flashed for recovery to work properly, the process to do so is described below.
Download this vendor_boot.img file.
Power off the device, and boot it into bootloader mode:
With the device powered off, hold Volume Down + Power.
Flash a the downloaded images to your device by typing (replace <vendor_boot> with the actual filename!):
fastboot flash vendor_boot <vendor_boot>.img
Unlocking the bootloaderinfo_outline
NOTE: The steps below only need to be run once per device.
warning
WARNING: Unlocking the bootloader will erase all data on your device! Before proceeding, ensure the data you would like to retain is backed up to your PC and/or your Google account, or equivalent. Please note that OEM backup solutions like Samsung and Motorola backup may not be accessible from PixelExperience once installed.
Enable OEM unlock in the Developer options under device Settings, if present.
Connect the device to your PC via USB.
On the computer, open a command prompt (on Windows) or terminal (on Linux or macOS) window, and type:
adb reboot bootloader
You can also boot into fastboot mode via a key combination:
With the device powered off, hold Volume Down + Power.
Once the device is in fastboot mode, verify your PC finds it by typing:
fastboot devices
If you don’t get any output or an error:
on Windows: make sure the device appears in the device manager without a triangle. Try other drivers until the command above works!
on Linux or macOS: If you see no permissions fastboot try running fastboot as root. When the output is empty, check your USB cable and port!
Now type the following command to unlock the bootloader:
fastboot flashing unlock
info_outline
NOTE: At this point the device may display on-screen prompts which will require interaction to continue the process of unlocking the bootloader. Please take whatever actions the device asks you to to proceed.
If the device doesn’t automatically reboot, reboot it. It should now be unlocked.
Since the device resets completely, you will need to re-enable USB debugging to continue.
Flashing the vendor boot partitionwarning
WARNING: This platform requires the vendor boot partition to be flashed for recovery to work properly, the process to do so is described below.
Download this vendor_boot.img file.
Power off the device, and boot it into bootloader mode:
With the device powered off, hold Volume Down + Power.
Flash a the downloaded images to your device by typing (replace <vendor_boot> with the actual filename!):
fastboot flash vendor_boot <vendor_boot>.img
Temporarily booting a custom recovery using fastboot
Download the PixelExperience Recovery. Simply download the latest recovery file.
Connect your device to your PC via USB.
On the computer, open a command prompt (on Windows) or terminal (on Linux or macOS) window, and type:
adb reboot bootloader
You can also boot into fastboot mode via a key combination:
With the device powered off, hold Volume Down + Power.
Once the device is in fastboot mode, verify your PC finds it by typing:
fastboot devices
If you don’t get any output or an error:
on Windows: make sure the device appears in the device manager without a triangle. Try other drivers until the command above works!
on Linux or macOS: If you see no permissions fastboot try running fastboot as root. When the output is empty, check your USB cable (preferably use a USB Type-A 2.0 one or a USB hub) and port!
check
TIP: Some devices have buggy USB support while in bootloader mode, if you see fastboot hanging with no output when using commands such as fastboot getvar ... , fastboot boot ..., fastboot flash ... you may want to try a different USB port (preferably a USB Type-A 2.0 one) or a USB hub.
Temporarily flash a recovery on your device by typing (replace <recovery_filename> with the actual filename!):
fastboot flash boot <recovery_filename>.img
info_outline
NOTE: Outdated fastboot releases dropped legacy A/B support, so it might attempt to flash to boot__a / boot__b rather than boot_a / boot_b if you try to flash boot. In this case, you must update fastboot to a release newer than or equal to 31.0.2. Alternatively, you can manually specify which slot to flash to based on what slot fastboot failed to flash to. For example, if fastboot fails to flash to boot__a, you must flash to boot_a.
Installing PixelExperience from recovery
Download the PixelExperience installation package that you would like to install or build the package yourself.
If you are not in recovery, reboot into recovery:
With the device powered off, hold Volume Down + Power. Then use the menu to select Recovery Mode.
Now tap Factory Reset, then Format data / factory reset and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage, as well as format your cache partition (if you have one).
Return to the main menu.
Sideload the PixelExperience .zip package:
On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
On the host machine, sideload the package using: adb sideload filename.zip.
check
TIP: Normally, adb will report Total xfer: 1.00x, but in some cases, even if adb: failed to read command: Success/No error. In some cases it will report adb: failed to read command: No error or adb: failed to read command: Undefined error: 0 which is also fine.
Once you have installed everything successfully, click the back arrow in the top left of the screen, then “Reboot system now”.
info_outline
NOTE: The first boot usually takes no longer than 15 minutes, depending on the device. If it takes longer, you may have missed a step, otherwise feel free to get assistance
check
TIP: If the installation process reports the message "(~47%) adb: failed to read the command: No error", do not worry, the process was completed successfully and you can restart the device.
I am not connected to Pixel Experience rom in any way.
Just posting to share.
I am not providing help and am not responsible for anything that happens.
Help each other!
If a P.E. maintainer wants this down. Please do so.
RESERVED:
Jan. Changelog:
January and December (2022) security patch
Google Apps updated
Fixed battery drain and lag spike caused by Pixel Launcher (Need to uninstall previous updates of Android System Intelligence or do a clean flash if the issue persists)
Minor issues fixed
Plus Version:
13 Plus version is here!First of all we hope you all are doing well. After the last two months of delayed updates it feels good to push an update in the perfect time period!
As the title says we are here with the PixelExperience Plus version.
Clean flash is not required if coming from normal version
Click to expand...
Click to collapse
Now coming to the feature list for the Plus version:-
LiveDisplay (color profile, display mode, reading mode, color calibration)
Hide Notch support.
StatusBar shortcuts
Rotation settings
Lock screen display (media cover, music visualizer, power menu)
Per-app volume settings
Increasing ring volume
Different gestures
Power and Volume button customisations
Network traffic monitor
Brightness (brightness slider, auto brightness, brightness control)
Quick settings (quick pulldown, title visibility, vibrate on touch, rows, columns)
There is more stuff one can unearth – this list was just a start off for the long feature list we have.
Just to be clear. Not a maintainer. Not affiliated with PixelExperience. Not Responsible for your choices!
Just creating a thread to spread the word my friends
Thanks for this, exactly what I've been looking for (stock ROM with volume button playback control, let's go!)
Flashed using instructions (factory reset, sideload). No issues, things seem to be working smoothly. Will observe battery life over the next few days but not expecting much difference either way.
Thanks for the nice Rom
Is there a version of PixelExperience for Pixel 5a Barbet but Android 11 (Plus edition)?
ALWA7SH6 said:
Thanks for the nice Rom
Is there a version of PixelExperience for Pixel 5a Barbet but Android 11 (Plus edition)?
Click to expand...
Click to collapse
No. Not that i know of. Give thanks to the PE team.
rhewins2268 said:
No. Not that i know of. Give thanks to the PE team.
Click to expand...
Click to collapse
Who is know?
ALWA7SH6 said:
Who is know?
Click to expand...
Click to collapse
I am just saying that i don't know of any Official PixelExperience Android 11 (Plus edition)
rhewins2268 said:
I am just saying that i don't know of any Official PixelExperience Android 11 (Plus edition)
Click to expand...
Click to collapse
TY
ALWA7SH6 said:
Thanks for the nice Rom
Is there a version of PixelExperience for Pixel 5a Barbet but Android 11 (Plus edition)?
Click to expand...
Click to collapse
there is none, pixel experience crew stopped with support for android 11, all projects moved to android 12
ALWA7SH6 said:
Thanks for the nice Rom
Is there a version of PixelExperience for Pixel 5a Barbet but Android 11 (Plus edition)?
Click to expand...
Click to collapse
you might be able to build your own rom and switch to the branch eleven-plus, but not sure if it would actually work or not. also i am sure it would be outdated for kernel security patches and other updates. build time on my dual cpu e5-2667v2 (32 cores total), 160gb of mem, WD SN750 1tb nvme and 1gbp internet running debian bookwork with tkg kernel is about 2hrs from start to finish. i just build a twelve-plus yesterday and i was surprised that everything worked out of the box using adb sideload on the unoffical twrp. the experience recovery actually installed and worked this time. rom is very smooth or i should say smoother than it was. a few new features were added. some were moved to a different spots. magisk install was easy with the working experience recovery allowing adb sideload to flash magisk. i might actually stick with this rom for a while.
rchris494 said:
you might be able to build your own rom and switch to the branch eleven-plus, but not sure if it would actually work or not. also i am sure it would be outdated for kernel security patches and other updates. build time on my dual cpu e5-2667v2 (32 cores total), 160gb of mem, WD SN750 1tb nvme and 1gbp internet running debian bookwork with tkg kernel is about 2hrs from start to finish. i just build a twelve-plus yesterday and i was surprised that everything worked out of the box using adb sideload on the unoffical twrp. the experience recovery actually installed and worked this time. rom is very smooth or i should say smoother than it was. a few new features were added. some were moved to a different spots. magisk install was easy with the working experience recovery allowing adb sideload to flash magisk. i might actually stick with this rom for a while.
Click to expand...
Click to collapse
Can you share it ty?
ALWA7SH6 said:
Can you share it ty?
Click to expand...
Click to collapse
yeah.
steps
1. unlocked bootloader
2. flashed fresh factory image (12.1.0 (SP2A.220405.003, Apr 2022)) from google dev site (check marked full wipe & force flash all partitions)
3. waited for phone to fully boot up. did offline setup skipping everything until i hit home screen
4. went to settings enabled developer mode & usb debugging
5. rebooted to bootloader (adb reboot bootloder)
6. toggled bootloader until i seen recovery then booted into stock reocovery
7. power + vol up for 3 sec then release you should get the stock recovery menu. do a factory reset / wipe data
8. reboot back to bootloader in the menu options of stock recovery
9. boot unoffical trwp from nijel8 (fastboot boot twrp-3.6.0_11-0-barbet.img)
10. in twrp go to advanced and adb sideload. set twrp to adb sideload
11. download https://drive.google.com/file/d/1yJdmMDap95-vYVZEhUUrZ2m3E45Y6ARg/view?usp=sharing (sha-256 checksum) or https://drive.google.com/file/d/1yJdmMDap95-vYVZEhUUrZ2m3E45Y6ARg/view?usp=sharing (untouched rom direct from pixel experience) if you don't care about checksum you can skip it.
12. adb sideload the rom (PixelExperience_Plus_barbet-12.1-20220423-2211-UNOFFICIAL.zip) note it fails at 47% and you might see a bunch of red warning on twrp. just ignore them and reboot the phone. pixel experience is now loaded on the phone. i had to do the whole process twice because twrp messed up the first time due to it not being officially up to 12 and sideload sometimes being flaky.
13. after setup was done i enabled debugging again and booted to bootloader, then recovery mode. pixel experience recovery should now be loaded. its touch screen or volume controlled. select adb sideload and side load magisk 24.3.apk or you can rename it to zip. doesnt matter. reboot phone. check app drawer. magisk will be there. if not give it a second it will pop up. tap the app to download full version. enjoy rooted & pixel experience
the rom is compiled directly from pixel experience source. i do not mod or edit anything. i just let my computer sweat at 100% usage for 2hrs and hope like hell the rom works.
i can try an eleven-plus build if you want but i doubt it will work and would probably end up bricking your phone.
this is the process i used. i take not responsibility if you brick your phone.
usually your brick is a soft brick holding power + vol up + vol down for 30sec will force restart your phone. then power off then power + vol dow to get back to bootloader so you can work with it again (factory flash or whatever)
android base is 12.1.0_r4
rchris494 said:
yeah.
steps
1. unlocked bootloader
2. flashed fresh factory image (12.1.0 (SP2A.220405.003, Apr 2022)) from google dev site (check marked full wipe & force flash all partitions)
3. waited for phone to fully boot up. did offline setup skipping everything until i hit home screen
4. went to settings enabled developer mode & usb debugging
5. rebooted to bootloader (adb reboot bootloder)
6. toggled bootloader until i seen recovery then booted into stock reocovery
7. power + vol up for 3 sec then release you should get the stock recovery menu. do a factory reset / wipe data
8. reboot back to bootloader in the menu options of stock recovery
9. boot unoffical trwp from nijel8 (fastboot boot twrp-3.6.0_11-0-barbet.img)
10. in twrp go to advanced and adb sideload. set twrp to adb sideload
11. download https://drive.google.com/file/d/1yJdmMDap95-vYVZEhUUrZ2m3E45Y6ARg/view?usp=sharing (sha-256 checksum) or https://drive.google.com/file/d/1yJdmMDap95-vYVZEhUUrZ2m3E45Y6ARg/view?usp=sharing (untouched rom direct from pixel experience) if you don't care about checksum you can skip it.
12. adb sideload the rom (PixelExperience_Plus_barbet-12.1-20220423-2211-UNOFFICIAL.zip) note it fails at 47% and you might see a bunch of red warning on twrp. just ignore them and reboot the phone. pixel experience is now loaded on the phone. i had to do the whole process twice because twrp messed up the first time due to it not being officially up to 12 and sideload sometimes being flaky.
13. after setup was done i enabled debugging again and booted to bootloader, then recovery mode. pixel experience recovery should now be loaded. its touch screen or volume controlled. select adb sideload and side load magisk 24.3.apk or you can rename it to zip. doesnt matter. reboot phone. check app drawer. magisk will be there. if not give it a second it will pop up. tap the app to download full version. enjoy rooted & pixel experience
the rom is compiled directly from pixel experience source. i do not mod or edit anything. i just let my computer sweat at 100% usage for 2hrs and hope like hell the rom works.
i can try an eleven-plus build if you want but i doubt it will work and would probably end up bricking your phone.
this is the process i used. i take not responsibility if you brick your phone.
usually your brick is a soft brick holding power + vol up + vol down for 30sec will force restart your phone. then power off then power + vol dow to get back to bootloader so you can work with it again (factory flash or whatever)
android base is 12.1.0_r4
View attachment 5597359
Click to expand...
Click to collapse
(a few new features were added)
Like what?
ALWA7SH6 said:
(a few new features were added)
Like what?
Click to expand...
Click to collapse
rhewins2268 said:
Plus Version:
April Update: 12 Plus version is here!First of all we hope you all are doing well. After the last two months of delayed updates it feels good to push an update in the perfect time period!
As the title says we are here with the PixelExperience Plus version.
Now coming to the feature list for the Plus version:-
LiveDisplay (color profile, display mode, reading mode, color calibration)
Hide Notch support.
StatusBar shortcuts
Rotation settings
Lock screen display (media cover, music visualizer, power menu)
Per-app volume settings
Increasing ring volume
Different gestures
Power and Volume button customisations
Network traffic monitor
Brightness (brightness slider, auto brightness, brightness control)
Quick settings (quick pulldown, title visibility, vibrate on touch, rows, columns)
There are more stuff one can unearth – this list was just a start off for the long feature list we have.
Click to expand...
Click to collapse
How is fingerprint sensor working, does it also have lag if AOD is not enabled? March update introduced 2 seconds delay after FP sensor registers your finger before it shows you your home screen. If you use AOD that issue is not present.
rhewins2268 said:
Plus Version:
April Update: 12 Plus version is here!First of all we hope you all are doing well. After the last two months of delayed updates it feels good to push an update in the perfect time period!
As the title says we are here with the PixelExperience Plus version.
Now coming to the feature list for the Plus version:-
LiveDisplay (color profile, display mode, reading mode, color calibration)
Hide Notch support.
StatusBar shortcuts
Rotation settings
Lock screen display (media cover, music visualizer, power menu)
Per-app volume settings
Increasing ring volume
Different gestures
Power and Volume button customisations
Network traffic monitor
Brightness (brightness slider, auto brightness, brightness control)
Quick settings (quick pulldown, title visibility, vibrate on touch, rows, columns)
There are more stuff one can unearth – this list was just a start off for the long feature list we have.
Click to expand...
Click to collapse
I noticed that sometimes the scanner simply refuses to understand the finger, I also noticed that when AOD is on, if you put the phone with the screen down, it does not go out, but if you turn up the screen and close the proximity sensor, it goes out
fackstrot said:
I noticed that sometimes the scanner simply refuses to understand the finger, I also noticed that when AOD is on, if you put the phone with the screen down, it does not go out, but if you turn up the screen and close the proximity sensor, it goes out
Click to expand...
Click to collapse
Please open bug on pixel experience GitHub, since main developer is not following this thread and PE community usually only fixes issues reported on official page.
Issues · PixelExperience/android-issues
Issue tracker. Contribute to PixelExperience/android-issues development by creating an account on GitHub.
github.com
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PixelExtended ROM for Oneplus8T [kebab]
What is this?
PixelExtended ROM (or PEX for short), We are Combining Pixel Goodies with some essential features you were missing in Pixel Experience, delivering a ROM that promise you stabilty and being feature-rich at the same time . TBH this ROM will keep it's Pixel' idea intact and won't be bloat with unwanted features .
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 13 (T)
FeaturesEverything You've Always Wished For With Pixel Experience> OOS (Oxygen OS) Styled Traffic Indicators
> VoLTE Icon Customization
> Smart Charging
> Adaptive Media Playback
> Notification Counter/Logs
> G-Visual Mod
> FOD (Fingerprint On Display) Customizations
> Status Bar Customizations
> Volume Panel Customizations
> LS (Lock Screen) Clock
> Switch Styles
> Tinted QS (Quick Settings) Tiles
> App Lock with Face Unlock
> QS Customizations
> Gesture Customizations
> New Accents/Fonts/Primary Colors
Whats working?
All
First Time Install / Clean Flash
1. Be on the OOS13 (F13 or F15, F62)
2. Download copy_partitions, vbmeta, dtbo, recovery, and rom for your device from here
3. Reboot to bootloader
4.fastboot flash vbmeta vbmeta.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot reboot recovery
5. While in recovery, navigate to Apply update -> Apply from ADB
6. adb sideload copy_partitions.zip (press "yes" when signature verification fails) and then reboot to recovery
7. Repeat step 5 and adb sideload rom.zip (replace "rom" with actual filename)
8. Format data, reboot to recovery
Update
1. Reboot to bootloader
2. While in recovery, navigate to Apply update -> Apply from ADB
3. adb sideload rom.zip (replace "rom" with actual filename)
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
Download from Mega
Android OS version: 13.0_r43
Security patch level: May 2023
Build author/Device Maintainer: bojantanasic
Source code: https://github.com/PixelExtended
Prebuilt kernel:
GitHub - bojantanasic/android_kernel_oneplus_sm8250: Android 13 kernel for oneplus 8T
Android 13 kernel for oneplus 8T. Contribute to bojantanasic/android_kernel_oneplus_sm8250 development by creating an account on GitHub.
github.com
PixelExtended Developer: Aryan Gupta
Changes 23.05.2023.
-brightnes fix
-fix for theme and fonts
-switch to erofs (now system is fluid like butter)
-add App lock (Settings/Security/More security/App lock)
Kernel
- update kernel to v4.19.283
Includes OOS Cam?
kuto232 said:
Includes OOS Cam?
Click to expand...
Click to collapse
OOS cam not include in rom, you can use LMC8.4 for better result then OOS cam.
Hasli: LMC8.4_R13
Download LMC8.4_R13 by Hasli.
www.celsoazevedo.com
and use config for better result.
Thank you for the ROM.
I would like to ask if anybody knows - does dual SIM work on this ROM (specifically enabling and disabling certain SIMs on the fly)? I know Lineage has issues with that along with auto brightness (jumps from low brightness to too bright with no in between) on KB2005.
netusername said:
Thank you for the ROM.
I would like to ask if anybody knows - does dual SIM work on this ROM (specifically enabling and disabling certain SIMs on the fly)? I know Lineage has issues with that along with auto brightness (jumps from low brightness to too bright with no in between) on KB2005.
Click to expand...
Click to collapse
Brightness working just fine,as you can see in screenshot.I don't have second sim card to test, but I think that is fine too.
Can't download the vbmeta and copy partition files from the link you provided.
silverhazesupreme said:
Can't download the vbmeta and copy partition files from the link you provided.
Click to expand...
Click to collapse
Sourceforge delete files from server, very strange. I will upload on mega today.
For install temporary use this files
recovery:
https://mirrorbits.lineageos.org/recovery/kebab/20230119/lineage-20.0-20230119-recovery-kebab.img
vbmeta:
https://mirror.math.princeton.edu/pub/lineageos/full/kebab/20230119/vbmeta.img
copy_partitions:
https://mirrorbits.lineageos.org/tools/copy-partitions-20220613-signed.zip
Thanks LineageOs team for files
Sourceforge has problem with files today!
Good as a daily driver? No stuttering, just fluid?
Goat24K said:
Good as a daily driver? No stuttering, just fluid?
Click to expand...
Click to collapse
Here is small video how fluid is rom, no stuttering. Kernel is great in turns of battery and performance.
Kernel is Illusionx with small performance upgrade by me.Thanks Blaster4385 for kernel.
Video
Streamable Video
Watch this video on Streamable.
streamable.com
Does USB-C video out work? I haven't run a customer rom in a while and I specifically want to install one that has video out working. I can't recall if it was a pixel experience rom or not the last time I had it working.
bookofjoshua said:
Does USB-C video out work? I haven't run a customer rom in a while and I specifically want to install one that has video out working. I can't recall if it was a pixel experience rom or not the last time I had it working.
Click to expand...
Click to collapse
I don't have adapter to test, if you are on OOS13 and if it is working and if this is essential for you than is better to stay on OOS13. If I find cable I will test.
bojantanasic said:
I don't have adapter to test, if you are on OOS13 and if it is working and if this is essential for you than is better to stay on OOS13. If I find cable I will test.
Click to expand...
Click to collapse
Thanks for the reply. I am not, I have a KB2007 and there isn't a OOS13 available (yet, as far as I know). I can just load it and see I guess.
bookofjoshua said:
Thanks for the reply. I am not, I have a KB2007 and there isn't a OOS13 available (yet, as far as I know). I can just load it and see I guess.
Click to expand...
Click to collapse
This rom is for F13 or F15 firmware, if you are on Android 12 then this rom is not for you, because touch wil not work.
I was upgrading from clean OOS13 F15 and when sideloading the ROM, I've got:
Error applying update: 63 (ErrorCode::kPostInstallMountError)
ERROR: recovery: Error in /sideload/package.zip (status 1)
Full logs here: https://gist.github.com/ivirtex/3a1c8fc464050e0310c37c795346aaae
ivirtex said:
I was upgrading from clean OOS13 F15 and when sideloading the ROM, I've got:
Error applying update: 63 (ErrorCode::kPostInstallMountError)
ERROR: recovery: Error in /sideload/package.zip (status 1)
Full logs here: https://gist.github.com/ivirtex/3a1c8fc464050e0310c37c795346aaae
Click to expand...
Click to collapse
You need to update the recovery through the bootloader before you can flash the Rom.You on Los recovery now?
bojantanasic said:
You need to update the recovery through the bootloader before you can flash the Rom.You on Los recovery now?
Click to expand...
Click to collapse
Yes, I flashed provided lineage-20.0-20230119-recovery-kebab
ivirtex said:
Yes, I flashed provided lineage-20.0-20230119-recovery-kebab
Click to expand...
Click to collapse
Did you format data?
And did you copy partition?
You mast format data and after that copy partition.
And after that adb sidload rom.zip.
I just update mega directory with pixelextended recovery, try to install and then tray to install rom.
Sorry if install instructions not clear
Did you install dtbo.img, if not that is problem.
Here is install instruction
Flashing additional partitions
warning
Warning: This platform requires additional partitions to be flashed for recovery to work properly, the process to do so is described below.
Download the following files from the directory named with the latest date here.
dtbo.img
vbmeta.img
Power off the device, and boot it into bootloader mode:
With the device powered off, hold Volume Up + Volume Down + Power.
Flash the downloaded image files to your device by typing (replace <...> with the actual filenames!):
fastboot flash dtbo <dtbo>.img
fastboot flash vbmeta <vbmeta>.img
bojantanasic said:
Did you format data?
And did you copy partition?
You mast format data and after that copy partition.
And after that adb sidload rom.zip.
I just update mega directory with pixelextended recovery, try to install and then tray to install rom.
Sorry if install instructions not clear
Did you install dtbo.img, if not that is problem.
Here is install instruction
Flashing additional partitions
warning
Warning: This platform requires additional partitions to be flashed for recovery to work properly, the process to do so is described below.
Download the following files from the directory named with the latest date here.
dtbo.img
vbmeta.img
Power off the device, and boot it into bootloader mode:
With the device powered off, hold Volume Up + Volume Down + Power.
Flash the downloaded image files to your device by typing (replace <...> with the actual filenames!):
fastboot flash dtbo <dtbo>.img
fastboot flash vbmeta <vbmeta>.img
Click to expand...
Click to collapse
Thanks, flashing dtbo.img allowed me to install the ROM and everything seems to work fine, please update your instructions, so others won't have this problem.
New build are up
Happy flashing
Decent but the sound externally is awful. Very low and static-like. I usually have to turn it down, but i had to turn this ll the way up and i barely heard the song. *sigh* any suggestions? It's the same with the ring tones, they're VERY low.. what is going on here?