{
"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 4a 5G Bramble
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:
Google Pixel 4a (5G) (bramble) - Pixel Experience
Google Pixel 4a (5G) (bramble) - Pixel Experience
download.pixelexperience.org
Stay tuned
Our Telegram channel
Our blog
Pixel Experience Telegram Chat Channel:
PixelExperience - Official chat
Welcome to PixelExperience official chat Group rules ? Type /rules Website: get.pixelexperience.org Twitter: twitter.com/PixelExpRom Github: github.com/PixelExperience Gerrit: gerrit.pixelexperience.org News: t.me/PixelExperience
t.me
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.
Changelog: January:
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
Reserved:
Install PixelExperience on brambleWARNING: I copy and pasted thes instuctions. Please go to the offical guide for your device Bramble 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 12 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.
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 are 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
flashed the latest PE+ on bramble, so far very good
creezalird said:
flashed the latest PE+ on bramble, so far very good
Click to expand...
Click to collapse
Does GPay work? After using for the weekend, would you recommend it?
xsnipuhx said:
Does GPay work? After using for the weekend, would you recommend it?
Click to expand...
Click to collapse
I am not using GPay or anything related, so I cannot say if it works or not. Besides I am rooted with Magisk, but using Denylist for all Banking/Work related apps. No issue with that.
In general, all is working well same as the stock rom, with few additional customizations example for statusbar etc. Battery life seems comparable to stock rom too. The face unlock is a bit slow, like you need to hold about 2 seconds before it really detects your face, but maybe it is the 4a5g hardware itself not officially being supported for faceunlock.
xsnipuhx said:
Does GPay work? After using for the weekend, would you recommend it?
Click to expand...
Click to collapse
Yes it works
Not sure if this bug is specific to this rom. Im using the latest + version, and the latest camera update causes instant fc. Just uninstall the update from the play store.
brandonabandon said:
Not sure if this bug is specific to this rom. Im using the latest + version, and the latest camera update causes instant fc. Just uninstall the update from the play store.
Click to expand...
Click to collapse
It's a known issue that will be fixed in the july update.
Help me flash PE Plus Pixel 4a 5G, please.
Astra1703 said:
Help me flash PE Plus Pixel 4a 5G, please.
Click to expand...
Click to collapse
Install PixelExperience on bramble - PixelExperience Wiki
Install PixelExperience on bramble - PixelExperience Wiki
wiki.pixelexperience.org
[ROM][13][bramble] PixelExperience [AOSP][OFFICIAL]
PixelExperience for Pixel 4a 5G Bramble 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...
forum.xda-developers.com
Slim2none4u said:
It's a known issue that will be fixed in the july update.
Click to expand...
Click to collapse
Yes it's fixed. Thx
New builds up!
Google Pixel 4a (5G) (bramble) - PixelExperience
Google Pixel 4a (5G) (bramble) - PixelExperience
download.pixelexperience.org
Hi, thanks for the heads up. I just wanted to know why if I try to install the latest recovery, I get bootloops
I kinda figured it out.
I had to go back to the older vendor_boot and boot images (from 12) in order to reboot into recovery. So that means that there is a problem with either the latest vendor or boot . Anyway, I could flash the zip with the oldest recovery and it's working pretty fine out of the box. Later I will tell you how it goes.
Ayax28 said:
I kinda figured it out.
I had to go back to the older vendor_boot and boot images (from 12) in order to reboot into recovery. So that means that there is a problem with either the latest vendor or boot . Anyway, I could flash the zip with the oldest recovery and it's working pretty fine out of the box. Later I will tell you how it goes.
Click to expand...
Click to collapse
Nevermind, "connectivity thermal power management" keeps crashing and the phones heats up A LOT, so thanks but gonna skip.
Ayax28 said:
Nevermind, "connectivity thermal power management" keeps crashing and the phones heats up A LOT, so thanks but gonna skip.
Click to expand...
Click to collapse
I couldn't even get that far lol.
I'm not a maintainer or even associated with PE. I just share the info.
Related
{
"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"
}
It has LINUX/UNIX and MAC support!
Due to the fact that there is another tool for Android called Android Multi Tools, I decided to rename this one to Lx Multi Tool, future releases will go under this name.
Features: Fastboot
- Unlock/Lock Bootloader
- Flash Recovery Menu (you can choose and add recoveries) - TWRP 2.8.7.1 Included
- Flash any partition (Flashing submenu)
- Flash full Stock images (you can choose and add images)
- Erase partitions (you can choose which of the partitions)
- Reboot (you can choose again...)
Adb
- Sideload .zip files (you can choose and add .zip files) - SuperSU v2.65 (Systemless!) included
- Backup (you can choose the name and place for your backup)
- Restore (you can choose your backup)
- Version (it just shows the version of your adb binaries) - platform-tools 23.1 included
- Logs (DMESG and Logcat)
- Screenshots (you can directly take screenshots to your PC with no Root)
- Reboot (lots of choices)
Others
- Refresh and delete files/folders from menus (Right click or key F5 and Del)
- Open tool folders from the menus (to add your own kernel/stock image/recovery/sideload zip files)
- Tab key support for easier keyboard navigation
- Tool-tips for all buttons
- Check for updates
- Link to xda-thread (here)
Download links: Windows x86|x64 - Linux x64 - MAC x64
All released versions can be found here.
[ROOT] Use SuperSU 2.62 or higher from here systemless for 6.0.1 and above.
Known bugs/limitations: - For partition Flashing, it is recommended(mandatory?) to do a reboot-bootloader if you want to flash multiple partitions one after the other. (according to the Google flashing scripts) (Implemented in 1.2.1)
- For return to stock, the tool will be stuck after your phone successfully boots, you need to reboot to fastboot again in order to flash the Radio and finish the full return to stock. (Fixed in 1.2.0)
Changelog:
Check the changelog for each release here.
Tutorials/FAQ:
Q: How do I get in bootloader/fastboot mode?
Turn off the phone and turn it on by using Volume down + Power key.
Q: How do I check for updates in your tool?
Follow the instructions in the screen below.
Q: Where can I find the device driver to install it for windows?
Click here, download the driver and run the setup.
Q: How do I root my stock phone?
- Unlock bootloader.
- Flash recovery.
- Use SuperSU 2.62 systemless or higher from here.
(Usually the latest version upon tool release is included in the Sideload folder of the tool, you can either sideload it or copy it to recovery and flash it manually)
Q: I get an error "Cannot open file" on MAC, what should I do?
Open the terminal, go to your application path and paste this command:
Code:
chmod +x LxMultiTool.app/contents/macos/*
Q: What do I need to do in order to be in Fastboot or in ADB mode.
Fastboot mode will be detected only while being in bootloader.
ADB mode will be detected from Recovery (custom) and actual ROM with USB debugging active.
Refresh button needs to be used in order to check for what mode you are in.
Q: Are there any other software that I need to install in order to run this tool?
On Windows and MAC everything is bundled, so nothing needs to be installed, just run.
On Linux you need to install from your package manager libQt5Core, libQt5Widgets, libQt5Gui, libQt5Network.
If it's not enough, use ldd LxMultiTool in terminal to find out what you're missing from your environment.
Q: I have an yellow/orange/red text screen during boot, what's that?
When you unlock you usually get the Orange screen and it's normal, but if you really want to know what's this about, give a reading to this.
Q: Hey, my device is not detected, why?
On windows, you need to manually install the USB drivers, they are not included and probably they won't be included in this tool.
Also, make sure you click the connection Refresh button after connecting the device to your PC.
Q: What do i need to do in order to install a custom ROM?
1. Unlock Bootloader.
2. Flash a custom recovery of your choice.
3. Flash an insecure kernel (boot).
4. Flash custom ROM with no problems via recovery.
All those things are found and can be done via this tool.
Q: Hi, i just downloaded this tool, how do i use it?
First, extract the folder somewhere.
After that, run LxMultiTool.exe on windows by double clicking it, LxMultiTool on linux and the same on mac.
Q: Do I need android-sdk installed or something else?
No! This tool uses it's own supplied binaries for adb and fastboot, if you have android-sdk installed it will be ignored anyways.
This tool is fully portable and stand-alone.
Q: I get an error while trying to unlock the bootloader -> FAILED(remote: oem unlock is not allowed), what now?
Starting with Android 5.0, you need to enable Bootloader Unlocking from the developer settings, in order to do that, follow these steps:
- Enable Developer options
- Enable USB Debugging
- Look for the ‘OEM Unlock’ Option and toggle it.
Q: How do I use the return to stock feature?
First download the latest package from here, then extract the contents (there is an archive in the archive) untill you get the a folder like angler-mda89d
that contains the images, that folder needs to be copied in the /Data/StockPackages folder in order to be visible.
Easier steps -> Get your device in bootloader -> Start the tool -> Hit refresh -> go to Stock -> hit open folder -> copy the extracted folder with the name angler-xxxxxx in there, hit F5 or Right-click + Refresh -> you should see the folder in there like in the following screenshot. Thanks @ursa08 for the screenie.
Q: How do I enable Developer options?
- Launch the Settings
- Scroll Down and Tap on About Phone(or About Device)
- Locate the Build Number Section
- Tap on the Build Number Option 7 Times
- Go Back to the Main Settings Page
- Scroll Down and Tap on Developer Options
Q: Hi, i just bought a phone what should i do now?
Well, you firstly need to unlock your bootloader...
Q: What is logcat?
Well, you can pretty much use google for that answer, but to put it short, is that thingy that tells you what is happening behind the scenes of your phone.
It is usually used for debugging and entertaiment(?).
When you report an error/bug to somebody, it will be a blessing to provide a logcat (logfile)!
Q: What is a Custom Recovery and why do i need one?
A custom recovery is that thingy that let's you flash .zip files, use your logic and you wil get it why you need one.
Q:There are others guides/tutorials out there, should i check them instead of this?
If you manage to get things done using this one, no, otherwise yes, note that some could be outdated...
Q:What is sideload and how do I use it?
Sideload is a function from adb that let's you flash a zip file while in recovery directly from your PC.
Please note that you need to be in sideload mode on your recovery before doing this.
To enter sideload mode, in TWRP go to Advanced -> ADB Sideload -> Swipe to sideload
Sources: The official and original repository can be found here.
Bug reports/Feature requests: If you have any bug, or you consider a feature to be a must-have, please use the issue functionality on github for more traceability here.
Licensing: Please note that this tool is open source and released under GPL v3 licence which can be read here.
Make sure you understand at least the short version of the license that's provided in the tool before using it or before contributing/forking and other related stuff.
Tech and stuff: Some additional marketing for stuff used in this tool
Qt - An awesome cross-platform IDE
Vmware - For letting me test this tool on all platforms (Linux and MAC).
Icons8 - A nice platform for good-looking FREE icons. (Big thanks!)
UnixUtils - For the sed utility for Windows.
AndroidFileHost - For the awesome file-management platform for developers.
Donations: Even though this tool is provided free of charge, full open-source, donations are very welcome to support the future development of this tool and to buy me a beer while coding future improvements on it.
This section will also include the hall of fame for donors, as well as on the github repository.
Special thanks for donations:
- @john7760
Disclaimer:I will not be responsible for smashed screens, bricked phones or any other things that you can accuse me of, i've done this tool to help people, use it at your own risk and consider giving a THANKS if you use it and like it.Please consider leaving some feedback, what to improve, what could be done better, what annoys you, it really helps me improve the tool.
Also, to avoid useless threads on general, Q&A or useless posts, please read the FAQ section upside, it's like a Mini-Guide!
Nice! Quick question, will this work for other phones other then nexus 6. Like sam note 3
Sent from my Nexus 6 using Tapatalk
warfenix said:
Nice! Quick question, will this work for other phones other then nexus 6. Like sam note 3
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
This tool has support only for 4 nexus devices, some features might work, some not, it's all down if the commands that are used by the tool are supported by the other device.
For example all fastboot flashing commands use the command:
Code:
fastboot flash <partition> <file_to_flash>
The same goes for the rest of the commads, I will try to investigate more and see if it's worth it to create a Sam Note 3 package for the tool.
The adb features should work though.
That would be awesome as i run only linux. And cant seem to get odin or heindall to work. Tried multiple times. So if there is something you could cook up. Amazing sauce. Its a att note 3. Either way. This will work great for my n6
Sent from my Nexus 6 using Tapatalk
New update with some fixes that should have been implemented a long time ago...
- Fixed Sideload flashing
- Enabled Recovery rebooting
- Fixed open folder for Stock menu
Wow - Great work on this. Love the fact that it supports mac/nix as well.
Nice! Keep up the good work.
Thank you!
This still the go to way to unlock and flash twrp? I'm on latest stock marshmallow.
bL33d said:
This still the go to way to unlock and flash twrp? I'm on latest stock marshmallow.
Click to expand...
Click to collapse
Yes, you can unlock the bootloader and flash TWRP recovery with it.
Support to Nougat?
ipan gulopuan said:
Support to Nougat?
Click to expand...
Click to collapse
Nougat should work with no problems, I personally used it to flash bootloader, radio and vendor images for Nougat update.
EXPERIMENTAL AND MOST LIKELY BROKEN
{
"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"
}
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.
*/
Android "Q" is the upcoming ninth major version of the Android operating system. It was first announced by Google on March 2019, and the first developer preview was released on the same day. The second developer preview is expected to be released at the next Google I/O developer conference.
[more stable] Pixel: Ported from Pixel 2 firmware (walleye)
Generic: Ported from Google GSI with gapps
GET UPDATES FROM: https://t.me/androidqgsi
Requirements :
Treblized device with 8.1 or P vendor
Global Bugs :
VoLTE
Device specific Bugs :
...
Instructions :
for A-Only :
Install img into system partition
Flash permissiver_v2.zip or make your boot partition selinux permissive
Flash FixZygote.zip
Reboot
for AB :
Install img into system partition
Flash permissiver_v2.zip or make your boot partition selinux permissive
Reboot
Downloads :
Q Developer Preview
Notes :
Fix gapps: install google play services with "adb install"
if images didn't worked properly post your logs(logcat and console-ramoops) on telegram group i'll come for help : @androidqgsi
Logcat without PC: take /data/local/tmp/logs/log
Enable adb before boot using this command in TWRP:
Linux/mac :
Code:
adb push ~/.android/adbkey.pub /data/misc/adb/adb_keys
Win :
Code:
adb push C:\Users\<userName>\.android\adbkey.pub /data/misc/adb/adb_keys
Donate:
My paypal: https://www.paypal.me/erfanoabdi
Tested on:
give me logs if didn't worked, or donate me a device
Tested by myself:
Moto Z (A-only)
Moto X4 (AB)
Thanks
ENJOY!
[DEV-ONLY] Bug Fixing
NVM
Ah actually this is ridiculous to have bug fixing post here, and i hate my port, real P GSI shouldn't done like this. but anyway this is ported from closed source P and i can point in most popular fixable bugs here...
by looking into logs(adb logcat -b all) if we see :
1) library "libxxxxxxxxx.so" not found
fix of this error is very simple as you guys all know we just need to put needed lib from system image of base rom in https://github.com/erfanoabdi/P_sem...GSI_Patches/Vendor/P Blobs/POST-sGSI_1/vendor
and zip up "POST sGSI 1" with new libs
Feel free to make pull request new libs in github
2) cannot locate symbol :
for example LG RIL error was like this:
Code:
CANNOT LINK EXECUTABLE "/vendor/bin/hw/rild": cannot locate symbol "_ZN7android8hardware5radio4V1_08toStringENS2_22CdmaSmsWriteArgsStatusE" referenced by "/vendor/lib64/[email protected]"...
a) here we need to find where is unknown symbol located in 8.1 system image
so in terminal goto system/ and :
Code:
grep -r "_ZN7android8hardware5radio4V1_08toStringENS2_22CdmaSmsWriteArgsStatusE"
output in this case is :
Code:
Binary file lib/[email protected] matches
Binary file lib64/[email protected] matches
(here you may get long list of blobs, only find and grab needed ones)
b) now just copy libs to vendor and rename them
in this case i renamed [email protected] to [email protected]
***important rule keep string name same as original file only replace one letter (a->W)***
c) and sed renamed lib (in my case) :
Code:
sed -i "s/[email protected]/[email protected]/" "P_semiGSI/POST_sGSI_Patches/Vendor/P\ Blobs/POST-sGSI_1/vendor/lib/[email protected]"
sed -i "s/[email protected]/[email protected]/" "P_semiGSI/POST_sGSI_Patches/Vendor/P\ Blobs/POST-sGSI_1/vendor/lib64/[email protected]"
we're almost done here
d) now open POST-sGSI_2 and sed "referenced by" lib from error line in log
like this : https://github.com/erfanoabdi/P_sem...ETA-INF/com/google/android/update-binary#L154
e) and zip up "POST sGSI 1/2" with new libs
Feel free to make pull request new libs/hax in github
3) more...
NVM
WIKI : https://github.com/erfanoabdi/P_semiGSI/wiki
i hope we get a full GSI eventually one P is released, been waiting a while for this. at least now its semi done, it should be easier to create a full GSI for kirin (aka my H9) and MTK devices.
Hi, will it support Honor9?
I'm waiting for kirin chipset supported gsi
Dumpling- Needs mokee vendor
waiting support kirin960 and more?
Sent from my Honor V9 using XDA Labs
Jamie_oppo said:
Do you need to be a on a treble rom before flashing this?
Ive got a 5t (dumpling) and flashed the open beta which gave treble. Then flashed a normal custom rom. I tried all the zip at this point and no luck decrypted.
Click to expand...
Click to collapse
Same phone here, I flashed the rom, but it reboots every time to the bootloader...
ChristiaanP said:
Same phone here, I flashed the rom, but it reboots every time to the bootloader...
Click to expand...
Click to collapse
were u on a treble rom? Or normal non treble custom rom
Edit: apparently ob 11 vendor image is broken and mokee one boots.
Jamie_oppo said:
were u on a treble rom? Or normal non treble custom rom
Edit: apparently ob 11 vendor image is broken and mokee one boots
Click to expand...
Click to collapse
I was on OB 11
Awesome... btw Currently booting phones
Mi 5 (gemini)
Redmi 4 Prime (markw)
Redmi 4x (santoni)
Redmi 3s/3x/Prime (land)
Zuk Z2 Plus (z2_plus)
Redmi Note 4 sd (mido) (Tested on PE and Lineage-ex vendors)
Lenovo P2 (kunato)
Redmi Note 5 Pro (whyred) (With mokee vendor)
Mi 6 (sagit) LG V30 (h930)
Redmi 5 Plus (vince) (Tested with cardinal-aosp vendor)
Exynos S9+ (Unstable as **** as its not QCOM)
Redmi 4A (rolex) (crDroid Treble)
OnePlus 5/T (Only one user has reported it to work with proof though)(Mokee trees)
Bugs for land or all devices!
- half volte is working (only outgoing call and volume for jio left to fix)
- app opening time is extra
None volte users r really lucky
Also jio4gvoice app is not working
Update for DP5
THE MEGAPOST OF NOTES FOR THE P GSI HERE
Wiki page: https://github.com/erfanoabdi/P_semiGSI/wiki/OnePlus-5T and https://github.com/erfanoabdi/P_semiGSI/wiki/OnePlus-5 (Thanks to timocapa)
OnePlus 5/5T users, you MUST be decrypted in order to boot this GSI. This means flashing the noverity zip and formatting data. The link to the zip which I used to get it working is here: https://drive.google.com/file/d/1BtZKnNc2ooe9lcDd0JJ8eHzylA0StSm2/view The recovery I am using is the latest codeworkx recovery here: https://sourceforge.net/projects/ch....1-0-20180414-codeworkx-dumpling.img/download for dumpling and https://sourceforge.net/projects/ch...-20180414-codeworkx-cheeseburger.img/download for cheeseburger.
Some things to take into consideration before I followed these steps: I was using OB11 as my daily driver since it's release and I have always been encrypted.
This is exactly how I managed to get it booting on my 5T:
1) format data to remove encryption (I'm on OOS OB11 before doing this)
2) reboot recovery
3) factory reset
4) flash Mokee ROM (latest nightly)
5) flash noverity zip
6) reboot into OS
7) get past set up and reboot into TWRP
8) factory reset
9) install P GSI
10) mount vendor
11) install all the latest POST zips in the order of 1 to 3
12) reboot into OS
OPTIONAL: After you have booted into Android P and the lockscreen shows. You can reboot back into TWRP and install the latest BETA version of Mqgisk
Click to expand...
Click to collapse
Alternative instructions if you are getting kicked back into the recovery with the display log saying "RescueParty", do all of the above but replace step 11 with the steps below (Thanks to @jelousdogs for his method):
11) Flash POST Zip 1,2 (Dont flash zip 3 Yet)
12) Reboot to system (You will see the rom booting and reboot to recovery suddenly)
13) Flash POST zip 3 in recovery and reboot to system
If this STILL does not work, try this: After completing all of these steps, mount vendor partition in TWRP, then use the TWRP File Manager. Copy the build.prop file from the vendor partition to your internal storage (/sdcard) and move it to your PC via MTP in recovery. Add "persist.sys.disable_rescue=true" (without quotes) to the bottom of the build.prop file you have just copied to your PC. Save and transfer it back to your internal storage. Copy the build.prop from your internal storage to /vendor, replacing the original file. Press on the build.prop file in your /vendor partition and press "chmod". Remove all of the "0000" numbers in the text box and type "0600", then confirm the chmod. Reboot to the OS.
Click to expand...
Click to collapse
DIRTY FLASHING DP5 FROM DP4 (Thanks to timocapa):
1) reboot into TWRP and flash the DP5 GSI.
2) reboot into the OS.
Simple as that.
Click to expand...
Click to collapse
Notes:
- If you get kicked into recovery after trying to boot the GSI, look at TWRP's display log where flashable zip text are printed out and see if "init_user0_failed". This means you are encrypted and the GSI is having trouble with it. You must be decrypted as said above.
- Yes, this includes the new gesture pill nav bar. SETTINGS > SYSTEM > GESTURES > SWIPE UP ON HOME BUTTON (Your stock launcher must be working, i.e. not Force Closing, in order for this to work because the new overview app switcher is part of the stock Pixel Launcher).
- Weird software issues like apps not opening, random FCs, settings going blank? Try a factory reset in TWRP and reboot to see if it has fixed any problems!
Click to expand...
Click to collapse
Known bugs confirmed by a number of 5/t users:
- Potato quality camera, you can use GCam to remedy the problem but expect blue dots in HDRmode (OnePlus problem)
- Front facing camera can only be used in OOS camera (wait for official sources)
Click to expand...
Click to collapse
To get rid of the three persistent notifications:
1) install GMS update (https://www.apkmirror.com/apk/googl...2-8-72-100400-202717283-android-apk-download/)
2) Tap on the blue finishing setup notification and connect to wifi, then force close the pixel setup so it re-appears again
3) Go to settings > accounts > sign into google
4) Tap on the blue notification again and you should be able to go further than "pixel is finishing setup" page.
5) Force stop play store to remove the play store persistent notification
Click to expand...
Click to collapse
Hope this helps other OP5/5T users out there who are having trouble booting this.
Can someone tell me if boot this rom on mi mix2s It is able for treble rom i tryied to flash but doesnt boot.
Reserved for review
Boots
Could someone please tell me if this is a Pixel experience in terms of new nav gestures+copy/paste in multitasking overview?
unrealmac said:
Could someone please tell me if this is a Pixel experience in terms of new nav gestures+copy/paste in multitasking overview?
Click to expand...
Click to collapse
No
ZeroInfinity said:
OnePlus 5/5T users, you MUST be decrypted in order to boot this GSI. This means flashing the noverity zip and formatting data. The link to the zip which I used to get it working is here: https://drive.google.com/file/d/1BtZKnNc2ooe9lcDd0JJ8eHzylA0StSm2/view The recovery I am using is the latest codeworkx recovery here: https://sourceforge.net/projects/ch....1-0-20180414-codeworkx-dumpling.img/download for dumpling and https://sourceforge.net/projects/ch...-20180414-codeworkx-cheeseburger.img/download for cheeseburger.
This is exactly how I managed to get it booting on my 5T:
1) format data to remove encryption (I'm on OOS OB11 before doing this)
2) reboot recovery
3) factory reset
4) flash Mokee ROM (latest nightly July 15th is what I used)
5) flash noverity zip
6) reboot into OS
7) get past set up and reboot into TWRP
8) factory reset
9) install P GSI
10) mount vendor
11) install all the latest POST zips in the order of 1 to 3
12) install in-call audio fix
13) reboot into OS
OPTIONAL: After you have booted into Android P and the lockscreen shows. You can reboot back into TWRP and install magisk. I recommend this version as it was the only one working for me: https://drive.google.com/open?id=10LV_j43YUmmHNe0PjE_GNo9kkb-1gAnD
Notes:
- If you get kicked into recovery after trying to boot the GSI, look at TWRP's display log where flashable zip text are printed out and see if "init_user0_failed". This means you are encrypted and the GSI is having trouble with it. You must be decrypted as said above.
- If you get kicked into recovery and TWRP's display log shows something about RescueParty, flash the POST 3 zip again and rebooting. You might want to try this 2-3 times if it did not work the first time.
- Yes, this includes the new gesture pill nav bar. SETTINGS > SYSTEM > GESTURES > SWIPE UP ON HOME BUTTON
Bugs that I have encountered personally but may not affect you, need confirmation:
- MTP isn't working, even with the workaround.
- ADB is detected but when doing "adb devices", it will stay on the "connected" status so you can't issue any adb commands via PC.
- Fingerprint not even detected, no option to enrol in security settings.
To get rid of the three persistent notifications:
1) force stop pixel setup in app settings
2) install GMS update (https://apkdot.com/apk/google-llc/g...s-12-8-66-100400-200774163-beta-041/download)
3) when the blue notification appears again, open it and connect to wifi
4) force stop pixel setup again
5) the next time the notification appears, it should allow you to finally finish the setup
Hope this helps other OP5/5T users out there who are having trouble booting this.
Click to expand...
Click to collapse
Thanks! It worked!
{
"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"
}
All variants are supported (TicWatch Pro, Pro 2020, Pro 4G/LTE)
I present to you: Kali NetHunter for the TicWatch Pro WearOS
Kali NetHunter is an Android ROM overlay that turns an ordinary phone into the ultimate Mobile Penetration Testing Platform. Now it's available for your smartwatch with some limitations.
The overlay includes a custom kernel, a Kali Linux chroot, an accompanying Android application, which allows for easier interaction with various security tools and attacks.
Beyond the penetration testing tools arsenal within Kali Linux, NetHunter also supports several additional classes, such as HID Keyboard Attacks, BadUSB attacks, WPS attacks, and much more. For more information about the moving parts that make up NetHunter, check out our NetHunter Components page.
NetHunter is an open-source project developed by Offensive Security and the community.
## 1. Unlock the bootloader
- Connect your watch to your PC with it's USB cable, and fire up a terminal.
- If you have set up your watch on the phone you can access settings, otherwise hold both buttons for a few seconds on the welcome screen.
- Enable developer settings by going to System -> About -> tap Build number 10 times
- Enable ADB, re-plug USB and accept debug from PC
- Reboot into bootloader with "adb reboot bootloader" from the terminal
- Unlock bootloader with "fastboot flashing unlock"
## 2. Flash vendor image, TWRP, and optimized WearOS
Download and extract the installation files into a folder. Please not this tutorial is for the TicWatch Pro 2020 (catfish), your ROM might be different on other models, please refer to @janjan's repo found here for the other ROMs.
Please note Magisk 21.0 is recommended, included in the following link.
Download link for ROM, vendor, TWRP, and Magisk: https://build.nethunter.com/contributors/re4son/catfish/
Download link for NetHunter zip. Scroll down to TicWatch for latest release: https://www.kali.org/get-kali/#kali-mobile
- Again enable ADB, and reboot to bootloader with "adb reboot bootloader"
- "fastboot flash vendor vendor.img"
- "fastboot flash recovery twrp-3.4.0-0-catfish.img"
- Boot into recovery by selecting it with the side buttons (switch with bottom one, select with upper button)
- Select "Wipe -> next page -> Format Data"
- Reboot to Recovery
- Select "Install -> ADB Sideload" and tick "Wipe Dalvik Cache, Wipe Cache
- "adb sideload 2-ROM-PWDD.190617.074-AUG-09.zip"
- Reboot & do initial setup (pair with your phone through WearOS app)
## 3. Resize system partition in TWRP
- Again enable ADB
- "adb reboot recovery"
- Select Wipe -> next page -> File System Options - select System - Resize (to have ~175MB free on /system instead of 0)
## 4. Flash and launch Magisk app to finish the rooting process
- "adb sideload Magisk-v21.0.zip"
- Reboot to System
- Launch Magisk Manager
- You might want to disable auto-update, set grant access in auto response, and disable toast notifications for easier navigation in the future
## 5. Flash NetHunter
- "adb reboot recovery"
- Select Install -> ADB Sideload
- "adb sideload" NetHunter image
- Reboot
- Start NetHunter app & chroot
- Reboot
## 6. Set NetHunter watch face
- Install Facer onto your phone from Play Store
- Search for NetHunter
- Install Facer companion app to watch
- Select & Sync
## Download link
TicWatch_Pro_NetHunter_files.zip | by yesimxev for Ticwatch Pro (2018)
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
## Additional supported apps
- Drivedroid: use "adb install" to install the latest version
Download link: https://store.nethunter.com/repo/com.softwarebakery.drivedroid_105000.apk
- TotalCommander: useful for selecting eg. a Ducky script, use "adb install" method
Download link: https://www.totalcommander.ch/android/tcandroid323-armeabi.apk
## Supported features
- Kali services
- Custom Commands
- MAC Changer
- HID Attacks
- DuckHunter
- Bad USB
- Nmap Scan
- WPS Attacks
## Upcoming features (not guaranteed)
- Nexmon, as the chipset is supported, needs some time
- Bluetooth Arsenal (internal bluetooth via blueblinder, as carwhisperer fails to r/w when SCO channel is connected)
- Router Keygen (to be optimised)
- Hijacker (if nexmon succeeds)
- Mifare Classic Tool (need to build OS with android.hardware.nfc enabled)
## Hardware limitations
- Power resource is not enough for any external adapters
Credits: The Offensive Security Team and the NetHunter community
Another extremely big thanks for @janjan for making this possible!
WearOS version: 2.17
XDA: DevDB Information
Kali Nethunter, Kernel & ROM for the TicWatch Pro
Contributors
@yesimxev
Source Code: https://gitlab.com/kalilinux/nethunter/
Kernel Source: https://github.com/yesimxev/msm-catfish-9.0-wear-os
RESERVED
Excited to try this with Catshark!
Thank you!
@yesimxev a fantastic contribution, just for the pleasure that "you do it because you can" you have my full support.
Can you upload screenshots or video, I'm curious how it interacts with the ROM when you do WPS attack, NMAP scan or any other of the functions you have enabled.
Is the ROM adapted to the much smaller screen size that the watches have?
bernarbernuli said:
@yesimxev a fantastic contribution, just for the pleasure that "you do it because you can" you have my full support.
Can you upload screenshots or video, I'm curious how it interacts with the ROM when you do WPS attack, NMAP scan or any other of the functions you have enabled.
Is the ROM adapted to the much smaller screen size that the watches have?
Click to expand...
Click to collapse
Yes I've optimised the NH app to fit. See some of my videos for HID, WPS attacks and even Konboot:
@yesimxev
Any advice for me please?
Failed before Last item in step 2. Reboot & do initial setup (pair with your phone through WearOS app)
Symptom long Boot animation for 90 seconds and booted to TWRP.
Attempt 1 using above process + JanJan files for Catshark.
Attempt 2 using Modified step + JanJan files
Modified step - Forum Post- https://forum.xda-developers.com/t/...kipjack-9aug20.3821013/page-186#post-82992173 (#3,714)
You don't need to flash the twrp. It usually cause bootloop. Use
adb reboot bootloader
fastboot boot name-of-the-twrp.img
## 1. Unlock the bootloader
## 2. Flash vendor image, TWRP, and optimized WearOS
Attempt 1
Manually
Reboot to bootloader with "adb reboot bootloader"
Fastboot flash vendor vendor.img
From TicWatch-Pro(4G)(Catshark)-EU-&-USA\TicWatch-Pro(4G)(Catshark)-EU-&-USA\Custom-ROM\TicWatch-Pro-4G-USA\ROM\2020\27-January-2020\Vendor-27-Jan-2020.zip (Vendor.img)
fastboot format userdata
fastboot format cache
"fastboot flash recovery catshark-4G-recovery.img"
From TicWatch-Pro(4G)(Catshark)-EU-&-USA\TicWatch-Pro(4G)(Catshark)-EU-&-USA\Custom-ROM\TicWatch-Pro-4G-USA\TWRP (catshark-4G-recovery.img)
Boot into recovery by selecting it with the side buttons (switch with bottom one, select with upper button)
Select "Wipe -> next page -> Format Data"
Reboot to Recovery
- Select "Install -> ADB Sideload" and tick "Wipe Dalvik Cache, Wipe Cache
"adb sideload Ticwatch-4G-USA-PWDD.190617.032-XDA-27-JAN-2020-LMKiller.zip"
- Reboot-
Symptom long Boot animation for 90 seconds and booted to TWRP.
Attempt 2
Manually
Reboot to bootloader with "adb reboot bootloader"
Fastboot flash vendor vendor.img
From TicWatch-Pro(4G)(Catshark)-EU-&-USA\TicWatch-Pro(4G)(Catshark)-EU-&-USA\Custom-ROM\TicWatch-Pro-4G-USA\ROM\2020\27-January-2020\Vendor-27-Jan-2020.zip (Vendor.img)
Fastboot format userdata
Fastboot format cache
Fastboot boot catshark-4G-recovery.img"
From TicWatch-Pro(4G)(Catshark)-EU-&-USA\TicWatch-Pro(4G)(Catshark)-EU-&-USA\Custom-ROM\TicWatch-Pro-4G-USA\TWRP (catshark-4G-recovery.img)
Boot into recovery by selecting it with the side buttons (switch with bottom one, select with upper button)
Select "Wipe -> next page -> Format Data"
Reboot to Recovery
- Select "Install -> ADB Sideload" and tick "Wipe Dalvik Cache, Wipe Cache
"adb sideload Ticwatch-4G-USA-PWDD.190617.032-XDA-27-JAN-2020-LMKiller.zip"
- Reboot-
Symptom long Boot animation for 90 seconds and booted to TWRP.
Roll back a build. Here's some instructions used by security researcher Lucas Stefanko
Installing NetHunter On the TicWatch Pro | Kali Linux Documentation
All variants are supported (TicWatch Pro, Pro 2020, Pro 4G/LTE) From unpacking to running NetHunter in 6 steps: Unlock the bootloader Flash vendor image, TWRP, and optimized WearOS Resize system partition in TWRP Flash and launch Magisk app to finish the rooting process Flash NetHunter Set...
www.kali.org
Achi Shukuteki said:
Roll back a build. Here's some instructions used by security researcher Lucas Stefanko
Installing NetHunter On the TicWatch Pro | Kali Linux Documentation
All variants are supported (TicWatch Pro, Pro 2020, Pro 4G/LTE) From unpacking to running NetHunter in 6 steps: Unlock the bootloader Flash vendor image, TWRP, and optimized WearOS Resize system partition in TWRP Flash and launch Magisk app to finish the rooting process Flash NetHunter Set...
www.kali.org
Click to expand...
Click to collapse
Thank you!,
If I am comprehending correctly this great write up includes the build for catfish only.
Meaning other models, must refer to @janjan's repo found here for the other ROM.
I used the only build for my device that is available in JanJan's repo.
Thanks for your patience.
Dmcpen said:
Thank you!,
If I am comprehending correctly this great write up includes the build for catfish only.
Meaning other models, must refer to @janjan's repo found here for the other ROM.
I used the only build for my device that is available in JanJan's repo.
Thanks for your patience.
Click to expand...
Click to collapse
Indeed. Keep us posted. I havent had the time, yet, to mod mine.
Achi Shukuteki said:
Roll back a build. Here's some instructions used by security researcher Lucas Stefanko
Installing NetHunter On the TicWatch Pro | Kali Linux Documentation
All variants are supported (TicWatch Pro, Pro 2020, Pro 4G/LTE) From unpacking to running NetHunter in 6 steps: Unlock the bootloader Flash vendor image, TWRP, and optimized WearOS Resize system partition in TWRP Flash and launch Magisk app to finish the rooting process Flash NetHunter Set...
www.kali.org
Click to expand...
Click to collapse
The kali[.]org and these instructions are the same. I've updated both in the same time. I'm afraid you might have a different way to flash. Or try the stock, you don't really need to be on the custom ROM. The NetHunter kernel will be the same and if you don't need any Mobvoi apps, we'll google how to remove them
Also, are you sure you've got a US model?
yesimxev said:
The kali[.]org and these instructions are the same. I've updated both in the same time. I'm afraid you might have a different way to flash. Or try the stock, you don't really need to be on the custom ROM. The NetHunter kernel will be the same and if you don't need any Mobvoi apps, we'll google how to remove them
Also, are you sure you've got a US model?
Click to expand...
Click to collapse
Thanks!
Success!
Nethunter works
Call and Text on 4G Works!
Dmcpen said:
Thanks!
Success!
Nethunter works
Call and Text on 4G Works!
Click to expand...
Click to collapse
What was the issue?
Please note I am very new to this and was only able to get this far because of hard work by @[yesimxev] and [@janjan]
Here are my notes. Use at own risk.
I had 3 failed attempts, and used [@janjan] return to stock process from:
[ROM+KERNEL+TWRP][Ticwatch Pro(Catfish)(Catshark-4G)]+[Ticwatch C2(Skipjack)[9Aug20]
-[Ticwatch Pro 4G/LTE (EU) (Catshark)-PWDD.190617.059]-[30-5-2020] - [Ticwatch Pro 2020 (Catfish-Ext)-PMP2.191203.001]-[22-6-2020] - [Ticwatch Pro (Catfish)-PWDD.190617.074]-[09-8-2020] ############################# - [Ticwatch Pro 4G/LTE (USA)...
forum.xda-developers.com
Hopefully you can learn from my mistakes with the details below.
Please note this is for the:
Ticwatch-Pro-4G(Catshark)-USA-PWDD.190617.032, your ROM might be different on other models, please refer to [@janjan](https://forum.xda-developers.com/m/490110/)'s [repo found here for the other ROM]https://forum.xda-developers.com/t/...shark-4g-ticwatch-c2-skipjack-9aug20.3821013/
Download and extract the installation files into a folder.
Please note Magisk 21.0 is recommended, included in the following link.
Download link for Magisk and Nethunter:
[https://build.nethunter.com/contrib...d.nethunter.com/contributors/re4son/catfish/)
[TicWatch_Pro_NetHunter_files.zip](https://build.nethunter.com/contributors/re4son/catfish/TicWatch_Pro_NetHunter_files.zip "TicWatch_Pro_NetHunter_files.zip")
Download link for NetHunter zip. Scroll down to TicWatch for latest release: [https://www.kali.org/get-kali/#kali-mobile](https://www.kali.org/get-kali/#kali-mobile)
**## 1. Unlock the bootloader**
- Connect your watch to your PC with it's USB cable, and fire up a terminal.
- If you have set up your watch on the phone you can access settings, otherwise hold both buttons for a few seconds on the welcome screen.
- Enable developer settings by going to System -> About -> tap Build number 10 times
- Enable ADB, re-plug USB and accept debug from PC
- Reboot into bootloader with "adb reboot bootloader" from the terminal
- Unlock bootloader with "fastboot flashing unlock"
**## 2. Flash TWRP, and optimized WearOS
- Again enable ADB, and reboot to bootloader with "adb reboot bootloader"
- "fastboot flash recovery catshark-4G-recovery" (From [@janjan] )
- Boot into recovery by selecting it with the side buttons (switch with bottom one, select with upper button)
- Select "Wipe -> next page -> Format Data"
- Reboot & do initial setup (pair with your phone through WearOS app)
**## 3. Resize system partition in TWRP**
- Again enable ADB
- "adb reboot recovery"
- Select Wipe -> next page -> File System Options - select System - Resize (to have ~175MB free on /system instead of 0)
**## 4. Flash and launch Magisk app to finish the rooting process**
- "adb sideload Magisk-v21.0.zip"
- Reboot to System
- Launch Magisk Manager
- You might want to disable auto-update, set grant access in auto response, and disable toast notifications for easier navigation in the future
**## 5. Flash NetHunter**
- "adb reboot recovery"
- Select Install -> ADB Sideload
- "adb sideload" NetHunter image
- Reboot
- Start NetHunter app & chroot
- Reboot
**## 6. Set NetHunter watch face**
- Install Facer onto your phone from Play Store
- Search for NetHunter
- Install Facer companion app to watch
- Select & Sync
Thank you and good luck.
yesimxev said:
The kali[.]org and these instructions are the same. I've updated both in the same time. I'm afraid you might have a different way to flash. Or try the stock, you don't really need to be on the custom ROM. The NetHunter kernel will be the same and if you don't need any Mobvoi apps, we'll google how to remove them
Also, are you sure you've got a US model?
Click to expand...
Click to collapse
Ha! I didn't notice the equivalence of the instructions. I should've read the first one in its entirety. I skimmed it thinking it was for a newer build. My bad.
Achi Shukuteki said:
Ha! I didn't notice the equivalence of the instructions. I should've read the first one in its entirety. I skimmed it thinking it was for a newer build. My bad.
Click to expand...
Click to collapse
Try stock for the win!
I followed the instructions to the letter on my ticwatch pro but after I adb sideloaded nethunter-2022.2b-ticwatchpro-wearos-kalifs-nano.zip and rebooted... it's not there.
I did it a few times and always the same result: I don't see it in the apps list, am I missing some hidden step?
Jackomel said:
I followed the instructions to the letter on my ticwatch pro but after I adb sideloaded nethunter-2022.2b-ticwatchpro-wearos-kalifs-nano.zip and rebooted... it's not there.
I did it a few times and always the same result: I don't see it in the apps list, am I missing some hidden step?
Click to expand...
Click to collapse
Did you setup the watch before flashing? Show me the /tmp/recovery.log using pastebin
yesimxev said:
Did you setup the watch before flashing? Show me the /tmp/recovery.log using pastebin
Click to expand...
Click to collapse
How do I extract that file from the watch? There is no terminal installed, even though I flashed nethunter
Just wanted to add to this that it's possible to get into the settings menu to enable ADB before pairing with your phone, by holding the top button for a couple seconds on the pairing screen. Should let you save a good chunk of time from installation by avoiding setting the watch up repeatedly
androidyl said:
Just wanted to add to this that it's possible to get into the settings menu to enable ADB before pairing with your phone, by holding the top button for a couple seconds on the pairing screen. Should let you save a good chunk of time from installation by avoiding setting the watch up repeatedly
Click to expand...
Click to collapse
I know, but left 'both buttons' in the instructions.
Jackomel said:
How do I extract that file from the watch? There is no terminal installed, even though I flashed nethunter
Click to expand...
Click to collapse
Flash NH in twrp, then run 'adb shell cat /tmp/recovery.log'
{
"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"
}
ArrowOS for OnePlus 9R (lemonades)ABOUTArrowOS is an AOSP/CAF based project started with the aim of keeping things simple, clean and neat.
Website: https://arrowos.net
Telegram: Channel | TG Portal/Links
Github: https://github.com/ArrowOS
Code Review: review.arrowos.net
E-mail: arrowos.contact
PayPal: Donate to us
Blog: blog.arrowos.net
Checkout more documentation at (maintainership/contributing): Check this out
WHAT WORKS?Almost everything.
Bugs: You tell me.
DOWNLOADSClick here to Download
Tip: Select OEM -> Device, choose Arrow version, choose the build type: "GAPPS" or "VANILLA" to download.
INSTALLACTION- Please note: Be sure that your phone is already OOS12 based !!!
- Download Recovery here
- Download script here
- Download ROM zip file.
- Reboot phone to Fastboot mode
Code: fastboot boot recovery.img
Install in ADB -> copy-partitions-20220613-signed.zip -> Advanced -> reboot to bootloader
fastboot boot recovery.img -> Factery Reset -> Install in ADB -> ROM.zip
- Reboot
INSTRUCTIONSRead our blog article/post about:
* HOW-TO report a bug
* GAPPS and VANILLA variants
* Checking build integrity
ROM Source: https://github.com/ArrowOS
Kernel Source: https://github.com/ArrowOS-Devices/android_kernel_oneplus_sm8250
The download link seems broken. Also what firmware is ROM based on OOS 11 or 12 ?
With the kebab version should also work
ArrowOS - Downloads
Thanks for your work. Also I want to ask, should I use oos11 or oos12 firmware?
exthomeboy said:
With the kebab version should also work
ArrowOS - Downloads
Click to expand...
Click to collapse
I tried it, but it doesn't work.
slatera18 said:
The download link seems broken. Also what firmware is ROM based on OOS 11 or 12 ?
View attachment 5670887
Click to expand...
Click to collapse
Now it's possible, OOS 11
hiper25 said:
Now it's possible, OOS 11
Click to expand...
Click to collapse
Is also a version only for the 9R. Almost every other rom is flashable on the 8T and 9R, but not here
exthomeboy said:
Is also a version only for the 9R. Almost every other rom is flashable on the 8T and 9R, but not here
Click to expand...
Click to collapse
On my test 9R can't flash 8T ROM
They have to have to separate
hiper25 said:
Now it's possible, OOS 11
Click to expand...
Click to collapse
Yes able to download.
But there is an issue with mic volume when talking on calls. The other person hears feeble voice of me on call.
hiper25 said:
fastboot boot recovery.img
Click to expand...
Click to collapse
Isn't it the code supposed to be fastboot flash recovery <recovery_filename>.img
hiper25 said:
Reboot phone to Fastboot mode
Code: fastboot boot recovery.img
Install in ADB -> copy-partitions-20220613-signed.zip -> Advanced -> reboot to bootloader
fastboot boot recovery.img -> Factery Reset -> Install in ADB -> ROM.zip
- Reboot
Click to expand...
Click to collapse
I'm a newbie here, the last time I have installed a custom ROM on Asus phone over five years ago with lineage os.
Will I be successful if I follow below instructions, as your instructions above are short and suited for pros.
search
Install LineageOS on kebabkeyboard_arrow_left Back to the overview
warning
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.
Make sure that your model is actually listed in the “Supported models” section here (exact match required!)
warning
WARNING: Before following these instructions please ensure that the device is currently using Android 12 firmware.
If the vendor provided multiple updates for that version, e.g. security updates, make sure you are on the latest!
If your current installation is newer or older than Android 12, please upgrade or downgrade to the required version before proceeding (guides can be found on the internet!).
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 LineageOS 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 Up + 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 oem 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 dtbo partitionwarning
WARNING: This platform requires the dtbo partition to be flashed for recovery to work properly, the process to do so is described below.
Download dtbo file from here. Download the file named dtbo.img from the directory named with the latest date.
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 file to your device by typing (replace <dtbo> with the actual filename!):
fastboot flash dtbo <dtbo>.img
Installing a custom recovery using fastboot
Download Lineage Recovery. Simply download the latest recovery file, named something like lineage-19.1-20220825-recovery-kebab.img.
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 Up + 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!
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.
Flash recovery onto your device (replace <recovery_filename> with the actual filename!):
fastboot flash recovery <recovery_filename>.img
Now reboot into recovery to verify the installation.
Use the menu to navigate to and to select the Recovery option.
Ensuring all firmware partitions are consistentinfo_outline
NOTE: The steps below only need to be run once per device.
In some cases, the inactive slot can be unpopulated or contain much older firmware than the active slot, leading to various issues including a potential hard-brick. We can ensure none of that will happen by copying the contents of the active slot to the inactive slot.
To do this, sideload the copy-partitions-20220613-signed.zip package by doing the following:
Download the copy-partitions-20220613-signed.zip file from here. It should have a MD5 sum of 79f2f860830f023b7030c29bfbea7737 or a SHA-256 sum of 92f03b54dc029e9ca2d68858c14b649974838d73fdb006f9a07a503f2eddd2cd.
Sideload the copy-partitions-20220613-signed.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 copy-partitions-20220613-signed.zip
info_outline
NOTE: The copy-partitions script was created by LineageOS developer erfanoabdi and filipepferraz
Now reboot to recovery by tapping “Advanced”, then “Reboot to recovery”.
Installing LineageOS from recovery
Download the LineageOS installation package that you would like to install or build the package yourself.
(Optionally): If you want to install an application package add-on such as Google Apps (use the arm64 architecture), please read and follow the instructions on Google Apps page
If you are not in recovery, reboot into recovery:
With the device powered off, hold Volume Down + Power.
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 LineageOS .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 the process succeeds the output will stop at 47% and report adb: failed to read command: Success. 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.
(Optionally): If you want to install any add-ons, click Advanced, then Reboot to Recovery, then when your device reboots, click Apply Update, then Apply from ADB, then adb sideload filename.zip those packages in sequence.
info_outline
NOTE: Add-ons aren’t signed with LineageOS’s official key, and therefore when they are sideloaded, Lineage Recovery will present a screen that says Signature verification failed, this is expected, please click Continue.
info_outline
NOTE: If you want the Google Apps add-on on your device, you must follow this step before booting into LineageOS for the first time!
Once you have installed everything successfully, click the back arrow in the top left of the screen, then “Reboot system now”.
hiper25 said:
INSTALLACTION- Please note: Be sure that your phone is already OOS12 based !!!
- Download Recovery here
- Download script here
- Download ROM zip file.
- Reboot phone to Fastboot mode
Code: fastboot boot recovery.img
Install in ADB -> copy-partitions-20220613-signed.zip -> Advanced -> reboot to bootloader
fastboot boot recovery.img -> Factery Reset -> Install in ADB -> ROM.zip
- Reboot
Click to expand...
Click to collapse
Newbie here.
Need instructions from unlocking the bootloader.
It took almost four hours to figure out and use MSM tool
Please do give me instructions from unlocking the bootloader
{
"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"
}
exTHmUI v12.0 Android 12 For Poco X3 GT (choping) OR Redmi Note 10 PRO 5G (chopin)
By:FurkiCan
What's This?
exTHmUI is an open source Android project with Touhou element, based LineageOS.
Feature
Status bar settings
Status bar lyric (works with Aplayer, QQ Music, Netease Music...) (Need APP SUPPORT!)
Customized button settings
A brand new theme engine(only for exthmui themes)
Yellow Page
Copyable SMS 2FA code
Gaming mode Plus++
Other Customization settings
Improved battery performance
Improved System performance
A better installation screen
and much more....
Device Build
12.5.7
Bugs
You tell me...
Special Thanks
LineageOS Team
exTHmUI Team
CFhan
Junko
Download
Chopin https://bit.ly/3blgO3f
ChopinG https://bit.ly/3Q6S1yC
Kernel Source (Prebuilt): https://xiaomifirmwareupdater.com/miui/chopin/stable/V12.5.7.0.RKPMIXM/
OEM Kernel Source: https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/chopin-r-oss
HOW TO FLASH ROM
!!You need a PC or laptop that can connect to phone!!
!!TWRP flashing method is currently not supported, and we cannot provide specific operation steps!!
!!BACKUP YOUR DATA FIRST!!
You need to install ADB and Fastboot on your PC(find install guide on Google or YouTube)
1.Download boot images with Lineage Recovery and ROM on your PC
2.Turn your phone into fastboot mode,type fastboot flash boot_ab <boot images filename> to flash boot images with Lineage Recovery,then type fastboot reboot recovery to reboot to recovery
3.Use volume key to move , power key to choose. First you should format userdata Factory reset > Format data/factory reset > Format data
4.When format is done, back to main page, choose Apply update > Apply from ADB , then turn to your PC's CMD,type adb sideload <package filename> to sideload ROM package
5.When ADB starts sideloading ROMs, you can go and enjoy some afternoon tea
6.When ROM flash done,choose Reboot system now, and enjoy yourself
Magisk 25.2 exTHMui
fastboot flash boot exroot.img
120 Hz Enable
screen-20220801-130139_1
Watch "screen-20220801-130139_1" on Streamable.
bit.ly
Sir thanks for your hard work. Can u port lineage os too?
good bro
Does it include GAPPS?
symbuzzer said:
Does it include GAPPS?
Click to expand...
Click to collapse
yes
1. Safetynet check failed. Any idea how to flash an safetynet zip file without TWRP?
2. No Volte and Vowifi.
After fastboot flash boot_ab chopin-los-rec.img
when i write fastboot reboot recovery
it says unknown reboot target recoveryand im bootlooping now help
Scatz. said:
After fastboot flash boot_ab chopin-los-rec.imgwhen i write fastboot reboot recoveryit says unknown reboot target recoveryand im bootlooping now help
Click to expand...
Click to collapse
I was on miui 13.0.4 global rooted
Scatz. said:
After fastboot flash boot_ab chopin-los-rec.imgwhen i write fastboot reboot recoveryit says unknown reboot target recoveryand im bootlooping now help
Click to expand...
Click to collapse
"After fastboot flash boot_ab chopin-los-rec.img"Type "fastboot reboot" and immediately keep holding the Vol + (do not release), it will get into recovery ,
Once it is in recovery mode, continue step 2, format it.
Then step 3.....
"fastboot reboot recovery" does not work, it show error, just ignore this command.
kirinin said:
"After fastboot flash boot_ab chopin-los-rec.img"Type "fastboot reboot" and immediately keep holding the Vol + (do not release), it will get into recovery ,
Once it is in recovery mode, continue step 2, format it.
Then step 3.....
"fastboot reboot recovery" does not work, it show error, just ignore this command.
Click to expand...
Click to collapse
Still goes to bootloop, here is my cmd screen, adb devices command shows no devices but it can flash img
Scatz. said:
After fastboot flash boot_ab chopin-los-rec.imgwhen i write fastboot reboot recoveryit says unknown reboot target recoveryand im bootlooping now help
Click to expand...
Click to collapse
now that I am using sdk platform tools, I don't receive unknown reboot target recovery, however fastboot reboot recovery leads to bootloop.
Okay fixed by doing these, idk which one has fixed the issue;
1-installing 12.5.7 global fastboot rom
2-enabling usb tethering and file transfer
3-charging my phone from %20 to %50
4-adding environmental variable path of adb platform tools
Rom is fast and working well. However my issue of noise reduction still continues. When talking on 3rd party like whatsapp, google duo, discord (not default phone app), other person hears me like I am under water if we talk at the same time, or a sound comes from my speakers. Can you test this?
Noise cancellation too sensitive
Noise cancellation too sensitive to spoil user experience on video call and in game talk. When there's music, video or external noise happen, ppl on the other side not able to hear me. Say I sound like under water. Anyone encountered this issue...
forum.xda-developers.com
Scatz. said:
Rom is fast and working well. However my issue of noise reduction still continues. When talking on 3rd party like whatsapp, google duo, discord (not default phone app), other person hears me like I am under water if we talk at the same time, or a sound comes from my speakers. Can you test this?
Noise cancellation too sensitive
Noise cancellation too sensitive to spoil user experience on video call and in game talk. When there's music, video or external noise happen, ppl on the other side not able to hear me. Say I sound like under water. Anyone encountered this issue...
forum.xda-developers.com
Click to expand...
Click to collapse
There may be a problem with your phone
I don't have this issue.
How about if your phone is with Miui rom?
kirinin said:
I don't have this issue.
How about if your phone is with Mi
Click to expand...
Click to collapse
all have the issue. Default gsm application works fine with loudspeaker on. Other person can hear me good. The issues is with 3rd party apps. Since I communicate mostly over internet I am frustrated.
Scatz. said:
I have tried miui versions:
global 12.5.7
global 13.0.4
turkey 12.5.7
turkey 13.0.3
all have the issue. Default gsm application works fine with loudspeaker on. Other person can hear me good. The issues is with 3rd party apps. Since I communicate mostly over internet I am frustrated.
Click to expand...
Click to collapse
I have only tried flashing fastboot roms with fastboot. Should I give updating firmware a try? Does it matter or flashing fastboot already changes firmware too?