Try restart to recovery, it helps for me"Package is for product op9pro but expected lemonadep" how do I solve this problem?
Try restart to recovery, it helps for me"Package is for product op9pro but expected lemonadep" how do I solve this problem?
are you on the right recovery (boot.img)?I tried but it doesn't work, i was already on nameless i had done factory reset to make a clean flash but keep telling me that message
Looks like I'll be waiting for the next update before I update to this. Its kinda annoying on the earlier build when I constantly have to unplug and plug the cable just to warp charge. The build I'm using is stable enough for me at the moment.Yes I have the same issue. Gotta disconnect the cable and connect it again so it charges fast again. Is there any fix to that ?
Everything is okay for me , using c62 ind version for fwYes I have the same issue. Gotta disconnect the cable and connect it again so it charges fast again. Is there any fix to that ?
By using the correct recovery."Package is for product op9pro but expected lemonadep" how do I solve this problem?
I know its off topic but do you know how to get drivers to install on a surface pro x it has a arm 64 processor and for the life of me i cant seem to install them.i ask you cause i know you have alot of knowledge with android and stuff.
I'll walk you through it, the instructions have been so confusing for me but I finally got it working
-Unlock your bootloader
-When you reboot, skip through setup, enable developer options again and re-enable USB debugging
-Boot into fastboot/bootloader (adb reboot bootloader)
From here, you need to download 5 files
dtbo.img and vendor_boot.img are found HERE
- dtbo.img
- vendor_boot.img
- boot.img
- latest version of nameless rom
- copy-partitions-20210323_1922.zip
boot.img and nameless rom are found on the download link in the main post, HERE if you're lazy
copy partitions zip is found HERE
-In fastboot, type these in order
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash boot boot.img
Obviously, if the img files aren't in the root adb.exe folder, then you put the path to the file
E.g - fastboot flash dtbo C:\Users\lol\Desktop\dtbo.img
At this point you've flashed the nameless recovery, and you're still in fastboot. Now you need to boot into the recovery.
-Press the volume down button twice so it says "recovery mode" at the top, then press the power button. You're now booting into the recovery.
-In the recovery, select "Apply Update", then "Apply from ADB"
-On your PC, type in 'adb sideload copy-partitions-20210323_1922.zip' (Or whatever you've named the copy-partitions zip)
This is a script that will copy everything from the current slot into the inactive slot. You NEED to do this if you haven't flashed your OOS update twice. Might as well do it anyway just in case.
-After it's done, click the back button on the top left and get back to the main screen
-Click advanced, then reboot to recovery
-Once it reboots into recovery again, click factory reset and follow the instructions
-When you've factory reset, go back to the main screen again, and go to "Apply Update", then "Apply from ADB" again like you did before
-Type 'adb sideload nameless.zip' (nameless.zip being the rom, type whatever you've called it, and yes you can rename the zip files for ease)
-Reboot
-Enjoy
NOTE:
If you use windows powershell, you might get a 'cannot read' error when flashing the rom
Try using command prompt instead
When you flash, it might appear as if it's frozen (it was stuck at 47% for me), don't touch it, just leave it and it will install just fine.
If no devices are showing up in fastboot, use this tutorial HERE
What issue? What ROM are you currently ON?Hi,
I've updated the ROM from the previous (C48) version to the latest version by following the steps here exactly, even switched the slot and flashed the dumped ROM stuff. I downloaded the original ROM from the Oxygen Updater app.
After flashing the updated OP9Pro ROM (original, not Nameless), I rebooted into the system and saw that the system was running normally. Then rebooted into recovery once again to sideload the Nameless ROM. I have flashed it for both slots, however, after booting into the system, the Google logo (the last few seconds of the boot up animation) plays repeatedly in intervals of a few seconds, allowing me just enough time to enter my SIM PIN in between the loops.
I installed the last (C48) version by following the instructions below (formatted the system):
Is there a way to fix this issue without formatting?
Thank you in advance
I'm currently on Nameless ROM, the latest build. And as for the OP build, it should be the C62 version after following the LineageOS Update instructions.
I watched a review on YouTube that stated this apparently maintains the OnePlus Camera & OnePlus settings tab, is this true?![]()
Nameless AOSP for OnePlus 9 Pro [lemonadep]
Nameless AOSP is based on Android Open Source Project, inspired by Google Pixel. We offer a smooth and stable experience for your device with a selected set of amazing features that provide an exceptional user experience.
Whats working?
Everything working
Known issues
Nothing yet
You tell me
Flash Instructions
Install LineageOS on lemonadep | LineageOS Wiki
wiki.lineageos.org
Download
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED !
Donate
Chris Chen PayPal
Chandu Dyavanapelli PayPal
UPI ID: [email protected]
Team
Chris Chen - Founder & lead Developer
Chandu Dyavanapelli - Co Founder & lead Developer
Credits
Android Open-Source Project
Pixel Experience
AospExtended
Proton AOSP
LineageOS
Havoc OS
Arrow OS
Krypton
Others, I may have forgot to mention
Stay tuned
Our Telegram Group
- Android OS version: 12.1/12L
- Security patch level: Augest 2022
- Build author/Device Maintainer: Chandu Dyavanapelli
- Kernel Source code: https://github.com/chandu078/android_kernel_oneplus_sm8350
- Source code: Nameless AOSP
- Screen Shots: Screenshots
If you're asking if this rom has the OP Camera installed, than it's a clear no. Afaik OP never released the camera.I watched a review on YouTube that stated this apparently maintains the OnePlus Camera & OnePlus settings tab, is this true?
They never are on Android 12.
There seems to be a bug with fast charging. Fast charging only works for sometime and then drops to 500mA. It's really annoying.
In regards to the gif/video issue, on the lineage posts describing this, someone suggested changing this setting in developer options to Disabled. Seems to have worked for me.i'm thinking of flashing another rom because the real problems (camera crashing/blurry/black screen, gifs/videos not loading in apps like reddit or twitter, bad bluetooth audio call quality...) don't seem to get fixed. Has anyone had that same experience with other roms? Is it a base problem ?
I had this problem as well!! Even after taking logs and searching multiple threads, I could not figure out what was causing it so I switched roms. I have flashed numerous roms since (Stag OS, CrDroid, Lineage OS, Watchdogs, Xtended, etc).Hi everyone! I'm having a problem with Google messaging RCS (Chat features) in the stock Google Messages App. I think it could be related to this ROM because on Oxygen OS I never had this issue.
What happens is when I talk to a known Chat user in Google Messages it keeps forcing me to SMS mode several times throughout the day. When the Chat user sends me a message it shows that it was sent via "Chat" but when I then reply, it puts my reply to "SMS". Resetting network settings (,including pulling the SIM) and clearing the app cache does not solve the issue.
I've done lots of App troubleshooting but to no avail.
On OxygenOS13, I could use RCS features with anyone who used them on their end and it would never force me to SMS. Thanks to anyone who could advise!
I have been using this rom for 3 months. There are no complaints. Thanks to the developer
I Updated to C.48, so what do I do next? Any help would be greatly appreciated