Either your device is not detected correctly in the windows OS or an admin/elevated command prompt is required but from the error msg, it's more likely that the image file (super_empty. Img) is not in the current (platform tools) folder.
Either your device is not detected correctly in the windows OS or an admin/elevated command prompt is required but from the error msg, it's more likely that the image file (super_empty. Img) is not in the current (platform tools) folder.
Hi,
Can anyone try OnePlus Camera 3.14.40 with OnePlus Camera services 2.4.3 is it work or not??
Is there any other way to port OnePlus Camera?View attachment 5870017
Didn't try camera since the services apk is conflicting
Did you do a dirty flash or full reset and update?I've upgraded from PE12 (unofficial/non-retrofit from @SevralT) to PE13 (official/retrofit).
Let me know if that's what you want to do.
full reset via Qualcomm MDM and update via EVO-X images for retrofitting and installing PE13 ROM.
adb reboot bootloader
fastboot devices
fastboot flash vbmeta_a "D:\Android Dev\PE13\evo-x-vbmeta.img"
fastboot flash vbmeta_b "D:\Android Dev\PE13\evo-x-vbmeta.img"
fastboot flash boot_a "D:\Android Dev\PE13\evo-x-boot.img"
fastboot flash boot_b "D:\Android Dev\PE13\evo-x-boot.img"
fastboot wipe-super "D:\Android Dev\PE13\super_empty.img"
fastboot set_active other
fastboot wipe-super "D:\Android Dev\PE13\super_empty.img"
fastboot set_active other
fastboot getvar all
(for fun and detailed info)fastboot boot "D:\Android Dev\PE13\TWRP-3.7.0_12-fajita-2.img"
adb sideload "D:\Android Dev\PE13\PixelExperience_Plus_fajita-13.0-20230303-0553-OFFICIAL.zip"
I am already trying to add it. Some changes are needed in frameworks_av & hardware_oneplus and needs code review.
Thanks for all this information. Where can I find vbmeta.img & boot.img and super_empty.img ?full reset via Qualcomm MDM and update via EVO-X images for retrofitting and installing PE13 ROM.
01. Prep Work: Gather all assests in a sample folder such as D:\Android Dev\PE13\
- vbmeta.img & boot.img (from evo-x ROM)
- super_empty.img
- TWRP-3.7.0_12-fajita-2.img (retrofit TWRP)
- PixelExperience_Plus_fajita-13.0-20230303-0553-OFFICIAL.zip (latest Official PE13 or PE+13 ROM)
- platform-tools_r34.0.0-windows.zip (Latest Android Platform Tools for Windows)
Here you can find the information:Thanks for all this information. Where can I find vbmeta.img & boot.img and super_empty.img ?
I use LOS 20 on my OnePlus 6T and OP Camera apk version 3.8.43 works fine for me. The newer versions do not.
Can you pass me the steps to flash latest build. I,ve followed the steps from OP but it was fails. End up bootlooping.I am daily driving this rom and it works perfectly fine. It is completely stable and passes SafetyNet Attestation and Banking apps work normally. There are no ground breaking bugs except these 2 I found:
Now Playing does not seem to work. There is an option shown after searching it in settings (attachment below) but tapping on it does not open anything. I did install the "Ambient Music Mod" and it works fine but it would have been nice if it was built directly into the rom.
The recorder app does not transcribe anything and on going to settings and opening transcription language it does not show any options (attachment below). Though if I open the live transcribe feature from quick settings it does work perfectly fine in every language. Only the recorder app does not work.
(A requested feature: Can we have an inbuilt applocker? and can we get widevine l1 support back?)
hi can i get some help? i followed all the steps properly but after sideloading it says no os installedfull reset via Qualcomm MDM and update via EVO-X images for retrofitting and installing PE13 ROM.
01. Prep Work: Gather all assests in a sample folder such as D:\Android Dev\PE13\
- vbmeta.img & boot.img (from evo-x ROM)
- super_empty.img
- TWRP-3.7.0_12-fajita-2.img (retrofit TWRP)
- PixelExperience_Plus_fajita-13.0-20230303-0553-OFFICIAL.zip (latest Official PE13 or PE+13 ROM)
- platform-tools_r34.0.0-windows.zip (Latest Android Platform Tools for Windows)
02. Connect phone to PC while USB Debugging enabled in "Developer Options", preferably original USB Cable
03. Launch Command Prompt (preferred) or Powershell in Administrator Mode and enter the installation directory of platform-tools
04. Reboot phone to Bootloader
adb reboot bootloader
05. List/Detect the phone
fastboot devices
(must display a valid Android ADB Interface in Device manager for Windows as well as a valid output of this command)
06. Flash the new retrofit dynamic partitions (boot & vbmeta) for each slot
fastboot flash vbmeta_a "D:\Android Dev\PE13\evo-x-vbmeta.img" fastboot flash vbmeta_b "D:\Android Dev\PE13\evo-x-vbmeta.img" fastboot flash boot_a "D:\Android Dev\PE13\evo-x-boot.img" fastboot flash boot_b "D:\Android Dev\PE13\evo-x-boot.img"
07. While still in the bootloader on the Phone, Goto Recovery via Bootloader -> choose Advanced -> Enter FastbootD mode
08. Initialize the retrofit super partitions for each slot:
fastboot wipe-super "D:\Android Dev\PE13\super_empty.img" fastboot set_active other fastboot wipe-super "D:\Android Dev\PE13\super_empty.img" fastboot set_active other fastboot getvar all
(for fun and detailed info)
09. Reboot into TWRP recovery
fastboot boot "D:\Android Dev\PE13\TWRP-3.7.0_12-fajita-2.img"
then Goto Advanced -> ADB Sideload mode
10. Finally install the ROM while merely booted via TWRP (since we didn't install it at all in above step)
adb sideload "D:\Android Dev\PE13\PixelExperience_Plus_fajita-13.0-20230303-0553-OFFICIAL.zip"
Reboot your phone and viola!
Try not doing the clear step and ensure you have the Hydrogen/OxygenOS link OP providedCan you pass me the steps to flash latest build. I,ve followed the steps from OP but it was fails. End up bootlooping.
Follow this link but replace the evolution os x rom with pe 13 rom and everything else same.Can you pass me the steps to flash latest build. I,ve followed the steps from OP but it was fails. End up bootlooping.
I don't personally use the Microsoft authenticator but I know the Google one works as well as an open source one I like to use called authenticator pro, so most likely the Microsoft one works too.Hello, I'm planning to install this ROM in the next few days... are any of you aware of any possible problems with Microsoft Authenticator? (I occasionally use the phone for work and asking might save me some trouble)
I am using MS Authnicator with several Apps & it is working fine. I generally first take backup of Authenticator from my previous installation & then restore the cloud backup & configurethe one's where restoration doesn't work.Hello, I'm planning to install this ROM in the next few days... are any of you aware of any possible problems with Microsoft Authenticator? (I occasionally use the phone for work and asking might save me some trouble)