{
"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 Moto G7 [river]
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 12
Whats working?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FM radio
Fingerprint reader
NFC
Lights
Sound/vibration
Known issues
Nothing yet
You tell me
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
Download from PixelExperience website
Donate
Liked my work? Give me a beer
Translation
Help with project translation
Stay tuned
Our Telegram channel
Our blog
Android OS version: 12
Security patch level: January 2022
Build author/Device Maintainer: JarlPenguin
Device Source code: https://github.com/PixelExperience-Devices
Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09
hello, I have ErrorCode::kInstallDeviceOpenError when sideload the rom with latest river twrp
bitgamer said:
hello, I have ErrorCode::kInstallDeviceOpenError when sideload the rom with latest river twrp
Click to expand...
Click to collapse
Please follow the instructions here. Keep in mind that TWRP isn't supported.
I get the same error as previously posted by bitgamer. I can get PE 11 to work fine. Any help would be appreciated.
I made it!
Follow these steps:
* Reboot into bootloader
*fastboot flash oem
*fastboot flash system
*fastboot flash vendor
*fastboot flash boot
*fastboot flash dtbo
* Reboot into recovery (if not reboot by cmd, reboot manually)
*Apply update by adb
*In CMD window type adb sideload followed by PE12 ROM click enter
* Reboot system
eltuzz said:
I made it!
Follow these steps:
* Reboot into bootloader
*fastboot flash oem
*fastboot flash system
*fastboot flash vendor
*fastboot flash boot
*fastboot flash dtbo
* Reboot into recovery (if not reboot by cmd, reboot manually)
*Apply update by adb
*In CMD window type adb sideload followed by PE12 ROM click enter
* Reboot system
Click to expand...
Click to collapse
can u help me pls? i cant install it
silvatuzkii said:
can u help me pls? i cant install it
Click to expand...
Click to collapse
Download SUPER IMAGES from: https://t.me/ClubJarlPenguin/2420
Download boot.img (recovery) and dtbo.img from: https://t.me/ClubJarlPenguin/2421
Download Pixel Experience ROM from: https://download.pixelexperience.org/river
Download copy-partitions-20210323_1922.zip
Extract super_images.zip in your platform-tools or ADB folder
Copy boot.img and dtbo.img in your platform-tools or ADB folder
Copy the Pixel Experience .zip package in your platform-tools or ADB folder
Copy "copy-partitions-20210323_1922.zip" in your platform-tools or ADB folder
Enable USB debug option in your phone (you need to enable developer options)
Code:
adb devices
adb reboot bootloader
fastboot flash oem super_oem.img
fastboot flash system super_system.img
fastboot flash vendor super_vendor.img
fastboot flash dtbo dtbo.img
fastboot flash boot boot.img
Reboot to recovery mode with volume and power keys. (this recovery looks like the factory recovery)
Sideload the copy-partitions-20210323_1922.zip package by doing the following:
On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
On the host machine sideload the package using:
Code:
adb sideload copy-partitions-20210323_1922.zip
Now reboot to recovery by tapping “Advanced”, then “Reboot to recovery”.
On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
On the host machine sideload the package using:
Code:
adb sideload PixelExperience_river-12.0-20220126-1621-OFFICIAL.zip
Tap factory reset
Reboot
Enjoy
Can I dirty flash over last PE Plus 11 (Oct 2021 build)
I can't flash PE recovery at all: "(bootloader) image not signed or corrupt"
Yes I can boot TWRP recovery very easy, but this ROM requires PE recovery for flashing. Is there alternative method to flash or boot PE recovery???
demijan said:
I can't flash PE recovery at all: "(bootloader) image not signed or corrupt"
Yes I can boot TWRP recovery very easy, but this ROM requires PE recovery for flashing. Is there alternative method to flash or boot PE recovery???
Click to expand...
Click to collapse
Download boot.img (recovery) from: https://t.me/ClubJarlPenguin/2421
Code:
fastboot flash boot boot.img
Reboot to recovery mode with volume and power keys.
(this recovery looks like the factory recovery not like the PE, works perfect)
I successfully upgraded from PE 11 to new PixelExperience 12 ROM
Sideload the copy-partitions-20210323_1922.zip is unnecessary in my case.
Thank you so much for your help!
I can't seem to sideload the copy-partitions file. It always gives the error message "failed to find META-INF/com/android/metadata, failed to parse metadata in the zip file. Installation from ADB completed with status 2. Installation aborted"" I downloaded the copy-partions file several times in case of a bad download. Any suggestions to get this to work. Also could i continue to sideload the PE rom after this error? Thanks
My problem in this PE 12 ROM is that the wifi connection is generally poor and not always constant. Yes, and one more thing, the antutu benchmark result in this ROM is about 50% lower than in the PE 11 ROM!
dwilbur said:
I can't seem to sideload the copy-partitions file. It always gives the error message "failed to find META-INF/com/android/metadata, failed to parse metadata in the zip file. Installation from ADB completed with status 2. Installation aborted"" I downloaded the copy-partions file several times in case of a bad download. Any suggestions to get this to work. Also could i continue to sideload the PE rom after this error? Thanks
Click to expand...
Click to collapse
I too am having this issue. Opening the file with 7zip shows there is no "/android/metadata" subfolder. Looked for an older version of the file and it's almost the same. ie instead of "/android/metadata" there is "/google/andriod" with the following files
update-script
update-binary
I can get to fastboot mode and into recovery mode but that's about it. Any help to either complete the PE install or revert to stock would be appreciated.
Restoring to the original android 10 ROM is very easy, just download the appropriate stock ROM from this site: https://motostockrom.com/motorola-moto-g7-xt1962-5
and flash it according to simple instructions. The procedure is completely safe and painless
JarlPenguin said:
Please follow the instructions here. Keep in mind that TWRP isn't supported.
Click to expand...
Click to collapse
Please!!!!....when will we have an update?
Seriously, to install this rom is it necessary to install an image first? LOL
I hope that in an eventual update (if there is one) it will be an installation with fewer steps, as usual.
JarlPenguin said:
PixelExperience for Moto G7 [river]
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 12
Whats working?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FM radio
Fingerprint reader
NFC
Lights
Sound/vibration
Known issues
Nothing yet
You tell me
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
Download from PixelExperience website
Donate
Liked my work? Give me a beer
Translation
Help with project translation
Stay tuned
Our Telegram channel
Our blog
Android OS version: 12
Security patch level: January 2022
Build author/Device Maintainer: JarlPenguin
Device Source code: https://github.com/PixelExperience-Devices
Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09
I
Click to expand...
Click to collapse
It doesn't work Very well on mine, it constantly Closes my keyboard makeing it so I can't have my keyboard open for More than a second. And my mobile data flickers on and off (I'm on TMobile)
This is very strange behavior, did you try factory reset maybe?
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"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* 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 the finger at us for messing up your device, we will laugh at you.
*
*/
Features:
- Always updated with latest twrp changes
- Decryption Works "Official miui, custom roms"
- Works with any 32bit and 64bit roms
- Treble enabled
- F2FS support
- FDE/FBE & SAR/NON-SAR Unified support
Notes:
- It works only with pie fw
Install guide: "You must have the Bootloader unlocked"
- Install ADB & Fastboot tools on your pc
- Go on fastboot mode
- Run "fastboot flash recovery yourrecoveryimage.img"
- Reboot and enjoy
Bugs:
- Maybe something i didn't saw during my usage, in case send logs if you encounter in a bug
Download:
Here
Support Group:
Here
Source code:
TWRP
Device tree
Kernel
Credits:
@Dees_Troy
@krasCGQ
@mahajant99
@Lostark13
@m_vaisakh
ROM OS Version: Android 9
ROM Kernel: Linux 4.x
ROM Firmware Required: pie
Based On: OMNI
Version Information
Status: Stable
Current Stable Version: 20210130
Stable Release Date: 2021-01-30
Created 2021-01-30
Last Updated 2021-01-30
11/08/2021 Build
HTML:
Source Changelog:
- Synced with latest twrp.me changes
- Merge aosp/pie-gsi changes
- Update f2fs-tools to v1.14.0
- Update nano to v5.2
- Squeeze performance while flashing a zip
- Start progress bar thread only when is required
- General fixes
Device Changelog:
- Build toybox
- Build userspace ExFAT driver
- Fixup encryption issues
- General fixes
Old Builds:
Spoiler
01/03/2021 Build
HTML:
Device changelog:
- Synced with latest twrp changes
- Readd /cust on partitions list
- Backup /persist as image
- Rename /sdcard1 to /external_sd
- General bug fixes
New update is out https://androidfilehost.com/?fid=17248734326145746072
changelog https://forum.xda-developers.com/t/...p-3-5-0_9-1-ysl-unified.4226279/post-84394617
twrp release: 3.5.1_9 · TeamWin/[email protected]
Change-Id: I13dfadea507d7050cec35d00d5cfabdf25462b15
github.com
everything is setted up for the first unofficial 3.5.1 release
waiting for seeing whole changelog on twrp.me ...
interesting, even if i write it, and i can see in cmd that is erasing and writing, getting okay message, bootloader is unlocked, and full adb acces, and still, my recovery is still the stock one, may im doing something wrong?
gherv1 said:
interesting, even if i write it, and i can see in cmd that is erasing and writing, getting okay message, bootloader is unlocked, and full adb acces, and still, my recovery is still the stock one, may im doing something wrong?
Click to expand...
Click to collapse
Reboot directly to twrp after you flashed it via fastboot "vol + and power button"
Miui replace the custom recovery with the stock one
Its_Vixano said:
Reboot directly to twrp after you flashed it via fastboot "vol + and power button"
Miui replace the custom recovery with the stock one
Click to expand...
Click to collapse
maybe this is what i was doing wrong, but i've one problem, my buttons band is not working, it's kinda removed from the phone, long story )
so i can boot recovery just from adb
i typed adb reboot bootloader
fastboot flash recovery twrp.img
fastboot boot twrp.img (and is just staying stuck there forever)
as i know is unlickely to restart into recovery from fastboot. Exist some solutions for me in this case?
Tried fastboot reboot and after that adb reboot recovery, so it's start making logic i need to boot directly onto recovery.
It's possible to flash it from test point?
also, i was thinking of a downgrade, but idk if ill work to reboot from fastboot and after that adb reboot recovery.
gherv1 said:
maybe this is what i was doing wrong, but i've one problem, my buttons band is not working, it's kinda removed from the phone, long story )
so i can boot recovery just from adb
i typed adb reboot bootloader
fastboot flash recovery twrp.img
fastboot boot twrp.img (and is just staying stuck there forever)
as i know is unlickely to restart into recovery from fastboot. Exist some solutions for me in this case?
Tried fastboot reboot and after that adb reboot recovery, so it's start making logic i need to boot directly onto recovery.
It's possible to flash it from test point?
also, i was thinking of a downgrade, but idk if ill work to reboot from fastboot and after that adb reboot recovery.
Click to expand...
Click to collapse
Might be tricky but it should be fine
- Get the stock boot img from a stock recovery rom, or download this "took from china latest release, should works fine"
- Patch it with magisk app "it will disable dm verity"
- Reboot to bootloader and flash the patched boot img "fastboot flash boot patched_boot.img"
- Reboot to system
If magisk app say that magisk is installed, you can flash the twrp with flashify
I forgot also to say that fastboot boot is broken on our device "the reason is still unknown"
Its_Vixano said:
Might be tricky but it should be fine
- Get the stock boot img from a stock recovery rom, or download this "took from china latest release, should works fine"
- Patch it with magisk app "it will disable dm verity"
- Reboot to bootloader and flash the patched boot img "fastboot flash boot patched_boot.img"
- Reboot to system
If magisk app say that magisk is installed, you can flash the twrp with flashify
I forgot also to say that fastboot boot is broken on our device "the reason is still unknown"
Click to expand...
Click to collapse
Ok, i tried right now, flashed it, and now rebooted to the system, i see miui logo, and is not moving from there ) and i've the latest stock update, i guess is similar to global ver
removed the battery, and now is fastboot bootloop, so i guess the boot.img was the problem
gherv1 said:
removed the battery, and now is fastboot bootloop, so i guess the boot.img was the problem
Click to expand...
Click to collapse
I had only this one on my drive disk, try to extract it from https://bigota.d.miui.com/V12.0.2.0.PEFMIXM/miui_HMS2Global_V12.0.2.0.PEFMIXM_668a87d737_9.0.zip
sorry for the inconveniences
Its_Vixano said:
I had only this one on my drive disk, try to extract it from https://bigota.d.miui.com/V12.0.2.0.PEFMIXM/miui_HMS2Global_V12.0.2.0.PEFMIXM_668a87d737_9.0.zip
sorry for the inconveniences
Click to expand...
Click to collapse
There is something else wrong, i just downloaded this one https://xiaomifirmwareupdater.com/miui/ysl/stable/V12.0.2.0.PEFMIXM/
flashed the boot img, and it's still stuck at miui logo, i mean, i have some experience with dead phones, but this one is very strange, oopa, worked now, so it was just the cn boot img, and needed a little bit of time to boot with his normal one
ill try to mod with magisk and flash again, i keep you in touch
I also flashed cache.img, i don't know if helped, but just in case if someone else have same problem
O yeaa, is working ) i can't belive it, i searched a lot on the internet, and not even one solution was helping me, so everything you need is just a smart person who know even better than the internet, thanks you a lot mate, now i can use google camera yay
gherv1 said:
O yeaa, is working ) i can't belive it, i searched a lot on the internet, and not even one solution was helping me, so everything you need is just a smart person who know even better than the internet, thanks you a lot mate, now i can use google camera yay
Click to expand...
Click to collapse
You are welcome
New update is out https://androidfilehost.com/?fid=7161016148664784278
changelog https://forum.xda-developers.com/t/...p-3-5-0_9-1-ysl-unified.4226279/post-84394617
Greetings to the creators of twrp recovery and to the moderators of this thread
I wonder if anyone knows if there are themes to customize this version of recovery 3.5.2 9 0?
Thanks
{
"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:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Flashing Instructions:
Pre-installation:
Until TWRP is ready, this version of crDroid comes with prebaked core Gapps
Download LOS recovery
Download Tiny ADB & Fastboot
First time installation (clean flash):
It is recommended to come clean from latest OOS installation
Backup your data to PC, OTG flash drive
Reboot to bootloader (fastboot)
Run fastboot devices to confirm there is connection to the phone
Install LOS recovery with following command fastboot flash boot lineage-18.1-20210615-recovery-lemonadep.img
Power off and reboot to recovery by pressing VOL down + Power from shutdown state
Navigate with volume keys to Factory Reset -> Format data/factory reset and confirm format of data
Go back to main menu and choose Apply update and Apply from ADB
Now adb sideload latest crDroid package with adb sideload crDroid.zip
When asked to confirm flash, do confirm it
Sideload push will go up to 47% and fail - no worry is normal
Reboot to system
Update installation:
Through recovery:
Download latest crDroid zip and reboot to recovery
Choose Apply update and Apply from ADB
Now adb sideload latest crDroid package with adb sideload crDroid.zip
Sideload push will go up to 47% and fail - no worry is normal
Reboot to system
Built-in OTA (slower):
When ready
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/crdroidandroid/android_kernel_oneplus_sm8350
Download:
ROM https://crdroid.net/lemonadep#crDroid-v7
Changelog: https://crdroid.net/lemonadep#crDroid-v7/changelog
Known issues:
- waiting for more feedback to see
Visit official website @ crDroid.net
crDroid OnePlus 9 Pro Telegram
crDroid Community Telegram
crDroid is built with passion by @neobuddy89 and @gwolfu
If you like our work, do consider a donation to support further device development
ROM OS Version: Android 11
ROM Kernel: Linux 5.4
Awesome.
I have the Tmobile version of OP9pro. Will I need to flash the tmobile modem.img?
burtonlax said:
I have the Tmobile version of OP9pro. Will I need to flash the tmobile modem.img?
Click to expand...
Click to collapse
Testing of this rom has been done on the EU variant
I am not sure how Tmobile version works, but rom side, is same as on LOS
gwolfu said:
Testing of this rom has been done on the EU variant
I am not sure how Tmobile version works, but rom side, is same as on LOS
Click to expand...
Click to collapse
it's best to go global first coming from tmo. No, as long as you don't do an ota on Global. so flash global then boot, then flash custom rom(following their guide).
If u lose service modem is provided (Just unzip) Bootloader fastboot command "fastboot flash modem modem.img
This of course is assuming u got unlock.bin and unlocked Bootloader
Here we go!
Welcome @gwolfu
Hopefully we don't need 11.2.7.7?? It's not out here in EU yet, what's the reason most of the custom roms seem to want the EU build by the way?
CRDroid, fantastic to see this here my favorite ROM since the days of my LG G3! Can't wait to try this out, will sadly be waiting till TWRP tho as I'd prefer to avaoid gapps. Unless there is any chance of a non gapps build also? Cheeky....!
I'll flash and report tomorrow .
post logs through here or telegram?
ryantf420 said:
I'll flash and report tomorrow .
post logs through here or telegram?
Click to expand...
Click to collapse
preferably here as to better keep track of stuff
I know it may not be recommended, but has anyone been able to flash this without using a computer?
phr0zen said:
I know it may not be recommended, but has anyone been able to flash this without using a computer?
Click to expand...
Click to collapse
Since the instructions specify using fastboot (as well as sideloading the rom), that's not possible.
phr0zen said:
I know it may not be recommended, but has anyone been able to flash this without using a computer?
Click to expand...
Click to collapse
without TWRP, not possible
TWRP is death.
This is awesome news brother
So I've been out of the root and rom flashing game for a bit, got it side loaded and everything my issue is i cant get root permissions working wasn't sure how i go about setting it up since all i have worked with on the one plus is magisk and having to install to a .img and input on how to get it working?
crazyvash1 said:
So I've been out of the root and rom flashing game for a bit, got it side loaded and everything my issue is i cant get root permissions working wasn't sure how i go about setting it up since all i have worked with on the one plus is magisk and having to install to a .img and input on how to get it working?
Click to expand...
Click to collapse
extract crdroid.zip content
extract boot.img from payload.bin file using payload dumper
install magisk apk on phone as any other apk (I know we are not rooted yet)
copy boot.img to internal phone storage
open magisk and click on top install button
choose "select and patch a file"
select the boot.img from internal storage
after done, copy magisk patched boot image from Download folder on phone storage, to PC
now on PC, reboot to bootloader and run
Code:
fastboot flash boot magisk_patched-23000_xxxxx.img
check file name to match xxxxx = random generated text
reboot to system and enjoy
gwolfu said:
extract crdroid.zip content
extract boot.img from payload.bin file using payload dumper
install magisk apk on phone as any other apk (I know we are not rooted yet)
copy boot.img to internal phone storage
open magisk and click on top install button
choose "select and patch a file"
select the boot.img from internal storage
after done, copy magisk patched boot image from Download folder on phone storage, to PC
now on PC, reboot to bootloader and run
Code:
fastboot flash boot magisk_patched-23000_xxxxx.img
check file name to match xxxxx = random generated text
reboot to system and enjoy
Click to expand...
Click to collapse
Think you missed the last step to use Magisk again to root the installed boot image?
djsubterrain said:
Think you missed the last step to use Magisk again to root the installed boot image?
Click to expand...
Click to collapse
Not need
I used fastboot flash not fastboot boot so boot is already patched
No temp boot and patch after
gwolfu said:
Not need
I used fastboot flash not fastboot boot so boot is already patched
No temp boot and patch after
Click to expand...
Click to collapse
Didn't notice that, totally right. Sorry.
truly have found nothing broken
except power menu settings only work in crdroid Settings not in System>Gestures>power menu...
Great job
{
"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:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/12.1/README.mkdn
Flashing Instructions:
Pre-installation:
OOS 12 firmware is required (from download page, firmware button)
Download KIT files (download - this includes dtbo.img and vendor_boot.img)
Download recovery (from download page, recovery button)
Optional NikGapps core (download - note that you may also need setup wizard addon if you rely on Google restore)
Optional Magisk (boot.img used to patch with Magisk in order to get root, can be found in recovery folder from download page)
First time installation (clean flash):
Backup your data to PC, OTG flash drive
Make sure you have OOS 12 firmware installed (see above to download)
Enter fastboot
Flash dtbo.img
Code:
fastboot flash dtbo dtbo.img
Flash vendor_boot.img
Code:
fastboot flash vendor_boot vendor_boot.img
Flash boot.img
Code:
fastboot flash boot boot.img
Boot to recovery (can do from bootloader or with buttons from power off state)
Now in recovery go to factory reset and confirm the reset
Reboot to recovery
Choose apply update and Apply from ADB
Now install crDroid zip via sideload
Code:
adb sideload crDroid.zip
Go back to main menu and reboot to recovery to install gapps (if you don't want gapps, reboot to system)
To install gapps, simply sideload gapps.zip the same way you installed crDroid.zip then reboot to system
Update installation:
Via recovery:
Boot to recovery
Choose apply update and Apply from ADB
Now install crDroid zip via sideload and reboot
Code:
adb sideload crDroid.zip
If you had gapps, reboot to recovery and sideload gapps.zip and reboot
Via OTA:
Go to Settings -> System -> Updater and download latest build
Choose install and let it finish
If you have Magisk installed, don't click reboot when prompted and go to Magisk and choose install to inactive slot
Reboot
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/crdroidandroid/android_kernel_oneplus_sm8350
Download:
ROM https://crdroid.net/lemonadep
Known issues:
- let me know
Visit official website @ crDroid.net
crDroid OnePlus 9 Pro Telegram
crDroid Community Telegram
If you like my work, consider a donation > My Paypal
I will flash crDroid 8 in day or two, see what it brings new. You guys did fantastic job with A11 let hope it brings something better with A12. Performance, stability and smoothness.
Thanks a lot for non-gapps build.
Warrkill said:
Thanks a lot for non-gapps build.
Click to expand...
Click to collapse
guess anyone can install gapps when they want google stuff added
so with crDroid 8, we no longer per-bundle gapps
Do we need to come from OxygenOS11 or 12?
djsubterrain said:
Do we need to come from OxygenOS11 or 12?
Click to expand...
Click to collapse
As always, only OOS11, CLEAN flash.
Just installed it. So far no issues. Will post a detailed feedback after testing for couple of days.
GOOD JOB team !!!
#POSITIVES
- UI is fairly stutter-free.
- Clean A12 experience
#ISSUES
- The fingerprint authentication is a hit or miss. Isn't working consistently.
- Sometimes there is no response on pressing power button or double tap on screen to wake the phone.
Have one issue - even with FK manager overclock I notice massive lags while scrolling in Spotify
Didn't have them on 11 android
Does it support signature spoofing?
Ravel7774 said:
Does it support signature spoofing?
Click to expand...
Click to collapse
yes
if anyone gets stuck on installing boot.img/magisk-boot.img set your active slot to A and try again
Had a hard time getting microg working. It works with microg now and passes safetynet.
However, it shows as slow charging on the lock screen. Is that normal?
For microg to work,
Flash magisk boot image
Boot into recovery
Adb sideload crdroid and magisk canary
When crdroid is booted, use magisk to install microg installer revived, magiskhide, shamiko and universal safetynet fix
Activate zygisk, Hide magisk, add your banking apps to denylist
Ravel7774 said:
Had a hard time getting microg working. It works with microg now and passes safetynet.
However, it shows as slow charging on the lock screen. Is that normal?
Click to expand...
Click to collapse
Did you use any modules to pass safety net? Or just zygisk deny list?
Warrkill said:
Did you use any modules to pass safety net? Or just zygisk deny list?
Click to expand...
Click to collapse
For safetynet, the microg has to be microg installer revived magisk module. The fdroid microg will fail safetynet. Will also need universal safetynet fix magisk module, which needs zygisk
Shamiko and hiding magisk were required to stop banking apps from detecting magisk. Remember to disable enforce denylist for shamiko to work
Not sure if magiskhide was needed but still installed it.
Ok, thanks for reply
Trying to flash this latest version.
I was on OxygenOS12, used EU MSM to go back to OxygenOS11
Updated to the latest version of that
Rebooted to fastboot, performed OEM unlock
Tried following the instructions, I'm in recovery but when I try sideloading the rom I'm getting a stream of "Failed to read XXXXXX bytes data at offset XXXXXX"
I had tried flashing to the rooted boot first, then noticed the instructions for clean boot, so I flashed the normal one instead, performed the factory reset, rebooted back into recovery.
Still failing with the same messages then a prompt "Signature verification failed. Install anyway?"
Tried re-downloading in case it was a bad download but still just getting the same
Any ideas?
djsubterrain said:
Trying to flash this latest version.
I was on OxygenOS12, used EU MSM to go back to OxygenOS11
Updated to the latest version of that
Rebooted to fastboot, performed OEM unlock
Tried following the instructions, I'm in recovery but when I try sideloading the rom I'm getting a stream of "Failed to read XXXXXX bytes data at offset XXXXXX"
I had tried flashing to the rooted boot first, then noticed the instructions for clean boot, so I flashed the normal one instead, performed the factory reset, rebooted back into recovery.
Still failing with the same messages then a prompt "Signature verification failed. Install anyway?"
Any ideas?
Click to expand...
Click to collapse
Which recovery did you use? Use LOS recovery
break.cold said:
Which recovery did you use? Use LOS recovery
Click to expand...
Click to collapse
The one that gets installed with the boot image in the first post. Special crDroid version
djsubterrain said:
The one that gets installed with the boot image in the first post. Special crDroid version
Click to expand...
Click to collapse
I tested the rom day ago, using LOS recovery to install crDroid A12 with LOS recovery NikGapps omni and flashing magisk 24.1 from crDroid recovery. Once the crDroid rom install successfully through LOS recovery, it will automatically install crDroid recovery with that you can install Gapps and magisk.
{
"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:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/13.0/README.mkdn
Flashing Instructions:
Pre-installation:
Recovery (Download from here)
Gapps (for vanilla variant) (Download from here)
Magisk Delta 25.0 or newer for root (after first boot) - (Download from here)
Pixel 2 XL Product partition extender zip (repartition): Instructions here
First time installation:
Wipe all partitions. Boot into fastboot and execute:
fastboot erase system_a
fastboot erase system_b
fastboot erase product_a
fastboot erase product_b
fastboot erase vendor_a
fastboot erase vendor_b
After that, follow instructions:
Boot into TWRP: fastboot boot <recovery_filename>.img
Swipe to allow modifications
Go to Advanced - ADB sideload
Flash pixel 2xl extender zip: adb sideload <zip_name>.zip
After finished, reboot into fastboot
Activate opposite slot you want to flash: fastboot --set-active=b to flash in slot A and vice versa
Boot into TWRP Recovery: fastboot boot <recovery_filename>.img
After TWRP booted, swipe to allow modifications
Go to Advanced - enable ADB Sideload
In Terminal, execute: adb sideload <rom_name.zip>
Wait to get finished.
Go to Reboot and reboot to bootloader
Set active slot where you installed ROM (ex. A): fastboot --set-active=a
Wipe data with fastboot -w
Boot into system. Enjoy
Note:
For Vanilla build, extra steps are:
Do steps from 1 to 13 also. After that:
Boot into TWRP Recovery: fastboot boot <recovery_filename>.img
After TWRP booted, swipe to allow modifications
Go to Advanced - enable ADB Sideload
In Terminal, execute: adb sideload <gapps_name.zip>
Reboot to bootloader
Wipe data with fastboot -w
Boot into system. Enjoy
Update installation:
Option 1:
Use seamless OTA.
Option 2 (Recommended):
Boot into fastboot mode
Set opposite active slot (ex. if you installed ROM in slot A, change to B): fastboot —set-active=b
Boot into TWRP: fastboot boot <recovery_filename>.img
Swipe to allow modifications
Go to Advanced - ADB sideload
Dirty flash ROM with command and wait to finish: adb sideload <rom_name.zip>
After it's finished, go to Reboot and select slot where you installed ROM
Reboot to system and enjoy
Note:
For Vanilla, do steps from 1 to 7 but skip point 8 and do this:
Reboot to bootloader
Boot into TWRP Recovery: fastboot boot <recovery_filename>.img
After TWRP booted, swipe to allow modifications
Go to Advanced - enable ADB Sideload
In Terminal, execute: adb sideload <gapps_name.zip>
Reboot to bootloader
Wipe data with fastboot -w
Boot into system. Enjoy
If you installed Magisk, do steps from 1 to 7 but skip point 8 and do this:
For Vanilla do steps from note before Magisk!
Reboot to bootloader
Boot into TWRP: fastboot boot <recovery_filename>.img
Swipe to allow modifications
Go to Advanced - ADB sideload
Flash Magisk zip: adb sideload <magisk_name.zip>
Wait to finish
Reboot to system and good to go
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/crdroidandroid/android_kernel_google_wahoo
Download:
ROM
Vanilla: https://crdroid.net/taimen
Gapps (unofficial): Download
Changelog: https://crdroid.net/taimen/9#changelog
Known issues:
None, please report if you find any into
Visit official website @ crDroid.net
crDroid Device Telegram
crDroid Community Telegram
crDroid Updates Channel
Donate to help our team pay server costs
Update 18.05.2023
Changelog:
* Android May 2023 Security
* Switch completely to AOSP Monet implementation
* Use Google Lens as QR code scanner when google search is installed
* Fix crash in rare instance while opening notification panel
* Added new QS header images
* Fixed systemui crash on QS panel pull down in rare instances
* Fixed few overlapping lockscreen fonts
* Various fixes and trivial optimizations
Download:
Vanilla
Gapps (unofficial)
Update 17.04.2023
Changelog:
Device changes:
* Enable Smart Charging
* Removed some unnecessary packages and blobs as included in March Security updates
Rom changes:
* Initial crDroid 9.4 release
* Updated to April 2023 security patches (android-13.0.0_r41)
* Allow toggling VoWiFi while roaming by default
* InternetDialog: Require unlocking to turn on hotspot
* Added back support for unlinked ringer streams
* Fixed Eleven options such as "use as ringtone" and "delete" media due to missing MANAGE_EXTERNAL_STORAGE permission
* Update Chromium Webview to 112.0.5615.101
* Updated translations
* Bug fixes
Download:
Vanilla
Gapps (unofficial)
Update 01.04.2023
Changelog:
Device changes:
* Enable Smart Pixels
* Enable FPS Info
* Fixed some sepolicy issues
Rom changes:
* March Security 2023 Update
Download:
Vanilla
Gapps (unofficial)
Update 01.03.2023
Changelog:
Device changes:
* Fix rounded corner rendering issues
* Enable app suggestions
* Use AiAi for app predictions
Rom changes:
* Introduce App Lock
Download:
Vanilla
Gapps (unofficial)
===========================
Update 25.02.2023
Changelog:
Vanilla:
* Android February 2023 Security update
* Updated and fixed Safety Net checks without root by default
* Various under the hood optimizations for performance
Gapps:
* Same as Vanilla
Download:
Vanilla
Gapps (unofficial)
Check flashing instructions for steps!
Also this ROM needs repartition. For more info, check flashing instructions.
Report bugs: Telegram group
Awesome...cant wait to boot this bad boy! Mahalo!
We became official! xD
So I gave it a go, and it all booted and ran great! But it will not work with Verizon. It recognizes the network, but says it's not available. On other ROMs it's available, but I can't send text.
ieatabiscuit said:
So I gave it a go, and it all booted and ran great! But it will not work with Verizon. It recognizes the network, but says it's not available. On other ROMs it's available, but I can't send text.
Click to expand...
Click to collapse
can you attach logs? also do you have Telegram? please join group and report there if you have. Thanks.
Hello,
Is this offer unlimited google photo backup in original quality?
Rajaasim1980 said:
Hello,
Is this offer unlimited google photo backup in original quality?
Click to expand...
Click to collapse
Hello. Yes, it does
IonutGherman said:
Hello. Yes, it does
Click to expand...
Click to collapse
Great mate i will try this thanks
Is current build enforcing or permissive? Google Pay with Magisk probably works, right? Thank you, great job, @IonutGherman.
Yahoo1 said:
Is current build enforcing or permissive? Google Pay with Magisk probably works, right? Thank you, great job, @IonutGherman.
Click to expand...
Click to collapse
Enforced. Yes, works if you know how to hide it properly.
hello when i try to flash rom in twrp then it gives this error
failed to mount /vendor(device or resource busy)
flashing from stock android 11 with unlocked bootloader
any solution would be appreciated ?
ieatabiscuit said:
So I gave it a go, and it all booted and ran great! But it will not work with Verizon. It recognizes the network, but says it's not available. On other ROMs it's available, but I can't send text.
Click to expand...
Click to collapse
Just flashed this again. Full data format/wipe. Have data on Verizon no prob. Text sending doesn't work for me either. BUT... I can send gifs, emojis, pics, AND recorded voice msgs. With mic button on text line,, not mic button that's on tool line that writes out text. It's VERY strange. Still haven't received a response from anyone I sent logs to.
I realized that I was getting error because of not doing re-partition before flashing the ROM as was on stock android 11. I actually wasted so many hours in failed attempt of flashing so many ROMS and has to flash stock factory image many times ..don't know why no flashing instructions in here mention this important part of doing re-partition
Rajaasim1980 said:
I realized that I was getting error because of not doing re-partition before flashing the ROM as was on stock android 11. I actually wasted so many hours in failed attempt of flashing so many ROMS and has to flash stock factory image many times ..don't know why no flashing instructions in here mention this important part of doing re-partition
Click to expand...
Click to collapse
Forgot to mention that, will update main thread in the next couple of days. I am busy now with studying.
KC69 said:
Just flashed this again. Full data format/wipe. Have data on Verizon no prob. Text sending doesn't work for me either. BUT... I can send gifs, emojis, pics, AND recorded voice msgs. With mic button on text line,, not mic button that's on tool line that writes out text. It's VERY strange. Still haven't received a response from anyone I sent logs to.
Click to expand...
Click to collapse
Where did you sent logs? To who?
Sorry guys, I builded in a hurry and made this topic kinda in a hurry too, next weekend will be free and will put everything to have a smooth installation and good experience. Also will bring new update. Thank you.
IonutGherman said:
Where did you sent logs? To who?
Click to expand...
Click to collapse
To los team. I don't know how to send a log here. Tell me how on xda and I'll send you one.
KC69 said:
To los team. I don't know how to send a log here. Tell me how on xda and I'll send you one.
Click to expand...
Click to collapse
LOS Team doesn't have anything to do with crDroid. If you have Telegram, join this group: https://t.me/ionutbuilds
or when you reply, you have a button to attach files. from Matlog app, go to 3 dots - Save zip and upload that zip here or in the Telegram group.
IonutGherman said:
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/13.0/README.mkdn
Flashing Instructions:
Pre-installation:
Recovery (Download from here)
Gapps (Download from here)
Magisk Delta 25.0 or newer for root (after first boot) - (Download from here)
First time installation:
step 1: Boot into TWRP
step 2: Format Data, Wipe other. Reboot to another slot and repeat.
step 3: Flash crDroid zip
step 4: Reboot to Bootloader, boot to TWRP
step 5: Flash Gapps - (optional and only for Vanilla)
Update installation:
Option 1 (Preferred):
Use seamless OTA.
Option 2 (Preferred):
step 1: Reboot to inbuilt recovery (From Either Advance restart - after holding the power button, when phone is on OR Press Volume up and power from power off state.)
step 2: Navigate to "Apply Update" -> "From ADB"
step 3: From your computer issue command "adb sideload <FILENAME>
step 4: Flash Gapps using sideload - (optional and only for Vanilla).
step 5: Reboot
Option 3:
step 1: Boot into TWRP
step 2: Flash crDroid
step 3: Reboot to Bootloader, boot to TWRP
step 4: Flash Gapps - (optional and only for Vanilla).
step 5: Reboot
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/crdroidandroid/android_kernel_google_wahoo
Download:
ROM
Vanilla: https://crdroid.net/taimen
Gapps (unofficial): Download
Changelog: https://crdroid.net/taimen/9#changelog
Known issues:
None, please report if you find any into
Visit official website @ crDroid.net
crDroid Device Telegram
crDroid Community Telegram
crDroid Updates Channel
Donate to help our team pay server costs
Click to expand...
Click to collapse
Will there be an official build for the regular Pixel 2 sometime in the future?
{
"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"
}
StatiXOS for OnePlus 9/9 Pro (lemonade/lemonadep)
What is StatiXOS?
StatiXOS is a custom ROM based on the Android Open Source Project aiming to be minimal while providing quality of life improvements and up to date security patches.
Spoiler: Known Issues
None from my testing!
Please report anything you run into!
Spoiler: Download StatiXOS Here!
Primary
Spoiler: How To Flash
Detailed Flashing instructions in Post #4
Download the fastbootimage zip
Unlock your bootloader, and reboot to bootloader
Type in
Bash:
fastboot -w
[This will format all of the data in your phone including internal storage (photos, files, everything!)] (Skip this step if you are coming from a previous build)
Connect your phone to PC and type in
Bash:
fastboot update statix_lemonadep-XXXXXX-13-v6.2-TIRAMISU-img.zip
(XXXXXX denotes the date of the build)
Wait for a while until the flashing process completes, it will reboot your device
Enjoy!
Spoiler: Stay in touch with our Telegram channels!
Official Chatroom
Official Releases & Announcements Channel
Android version: 13
Linux Kernel Version: 5.4.x
Source code: GitHub
Code Review: Gerrit
Device Sources
1. Device Specific Tree
2. Common OnePlus SM8350 Tree
3. Kernel Source Code
Changelogs
16th April 2023
Initial release
21st April 2023
April security patch
Fixed low mic volume
Fixed pickup sensor functionalities
Fixed weird resolution in recovery
Improved rounded corners
Upgraded blobs to F21
Enabled UI blur
19th May 2023
May security patch
Newer pickup sensor handling
Improved perf and smoothness using libperfmgr
Support for OnePlus 9 (non-pro)
22nd June 2023
June Security Patch
Upgraded to blobs EX01 firmware
Dropped Gcam in favour of Aperture
Fixed autobrightness
Force refresh rate to 60 on keyguard
Disable UI Blur
Fix VoIP call volume stuck at max
Detailed Flashing instructions:
NOTE: These instructions are for first time users only! If you are upgrading from previous StatiX Builds, you DO NOT NEED TO FORMAT DATA!
To flash StatixOS, you need these pre-requisites:
A PC with ADB/Fastboot installed
OnePlus 9 Pro device
USB Cable
StatiXOS Build
Backup your internal storage before this process.
This guide assumes you are coming from OOS 13.x with an unlocked bootloader.
For Windows Users:
Download SDK platform tools for Windows (I do not recommend using the latest ones because it breaks flashing) and extract it to anywhere you like.
Install ADB/Fastboot Drivers
Assuming you have unlocked bootloader, and enabled Developer Options, navigate to System > Developer Options, scroll down to find USB Debugging, and enable it.
Connect your device to PC
From your PC, navigate to the extracted platform-tools
In the folder you need to check if there are some dll files and a few executables (.exe files). We're majorly concerned with adb.exe and fastboot.exe.
Whilst pressing Shift key, Right click in the folder, and there shall be an option to "Open powershell window here" or "Open Command Prompt here"
In the powershell window, type in .\adb.exe devices, now check your phone, there will a window asking to allow connection, allow it on phone. (If you don't do quicky, it may show as unauthorised in the powershell window, which is nothing to be worried about, just repeat the command)
Once the device is authorised, type in .\adb.exe reboot bootloader, your device shall reboot to a FASTBOOT screen, this is the bootloader mode.
Now ensure your drivers are proper. Type in .\fastboot.exe devices. If it shows nothing, it means that your drivers are not proper, google search on how you should fix them as it is out of the scope of this guide. Once you get an output like 2398534953 fastboot, it means that your device is detected.
(You do not have to do this step if you are upgrading from a previous StatiXOS build) In powershell, type in .\fastboot.exe -w, this will completely wipe your internal storage.
Now, type in .\fastboot.exe update ''path\to\StatiXOS\Build\zip'' (replace path\to\StatiXOS\Build\zip with actual path to the fastboot images zip file) Pro Tip: You can right click and copy the zip and then paste into powershell window. Make sure you paste in between the quotes ' '.
It should show some details and start flashing immediately. It will reboot your device automatically to fastbootd mode in Statix Recovery. DO NOT DISCONNECT THE DEVICE DURING THIS PROCESS!
Wait till the process finishes, it will reboot the device automatically.
That's all! Enjoy StatiX on your device!
For Linux Users:
Install adb and fastboot according to your distro, and install proper udev rules.
Assuming you have unlocked bootloader, and enabled Developer Options, navigate to System > Developer Options, scroll down to find USB Debugging, and enable it.
Connect your device to PC
From your PC, open Terminal
In the terminal window, type in adb devices, now check your phone, there will a window asking to allow connection, allow it on phone. (If you don't do quicky, it may show as unauthorised in the powershell window, which is nothing to be worried about)
Once the device is authorised, type in adb reboot bootloader, your device shall reboot to a FASTBOOT screen, this is the bootloader mode.
Type in fastboot devices, you'll get an output like 2398534953 fastboot, it means that your device is detected.
(You do not have to do this step if you are upgrading from a previous StatiXOS build) In powershell, type in fastboot -w, this will completely wipe your internal storage.
Now, type in fastboot update ''path/to/StatiXOS/Build/zip'' (replace path/to/StatiXOS/Build/zip with actual path to the fastboot images zip file).
It should show some details and start flashing immediately. It will reboot your device automatically to fastbootd mode in Statix Recovery. DO NOT DISCONNECT THE DEVICE DURING THIS PROCESS!
Wait till the process finishes, it will reboot the device automatically.
That's all! Enjoy StatiX on your device!
Nice, easy to install too, does it comes with Eva kernel!? It would be nice to know what customizations it have, OOS camera, gapps?
Sending sparse 'super' 1/1 (4194303 KB) FAILED (Sparse file is too large or invalid)
fastboot: error: Command failed
Every time I try to install, it fails.
edit: I was using platform tools r34.0.1
reverted to version r33.0.1 and install worked fine.
Oos cam inbuilt ?
megafan said:
Nice, easy to install too, does it comes with Eva kernel!? It would be nice to know what customizations it have, OOS camera, gapps?
Click to expand...
Click to collapse
Paras_w said:
Oos cam inbuilt ?
Click to expand...
Click to collapse
It does come with Eva Kernel but, it's an older version. GApps is there by default and OOS camera is not shipped by default.
How can i install oos cam ?
Paras_w said:
How can i install oos cam ?
Click to expand...
Click to collapse
you can't.
Please add in next build it's request
Get this message when I`m flashing "FAILED (Sparse file is too large or invalid)" ?
I came from Nameless.
I found the solution a bit above
No cell service in LE2125 for Verizon
kodayoda713 said:
No cell service in LE2125 for Verizon
Click to expand...
Click to collapse
TMO?
I get this "FAILED (remote: Partition not found)?
Try to flash from Fastboot D and get "FAILED (remote: Unable to set slot)"?
Next try I got this Sending sparse 'odm_a' 1/2 (772978 KB) FAILED (remote: 'Invalid size')?
Must I start from Stock? to be able to flash StatiXOS?
TheGhost1951 said:
TMO?
Click to expand...
Click to collapse
Unlocked
OOS Cam?
kodayoda713 said:
Unlocked
Click to expand...
Click to collapse
Is T-Mobile your carrier
TheGhost1951 said:
Is T-Mobile your carrier
Click to expand...
Click to collapse
Verizon
kodayoda713 said:
Verizon
Click to expand...
Click to collapse
Search for Verizon modem.img and flash it in fastboot, but in meantime, shutdown phone, remove sim card, then boot phone, then shutdown phone insert sim card and reboot to see if it aquires cell service....