Develop Bugs

Root: Joying 5.1.1 Unit

I ended spending a fair amount of time chasing down a working root method, in the interest of saving time for anyone else who is looking I wanted to post the steps I took.
1.) Settings > Factory Settings > Enter Password: *#hct#root#
2.) Install Kingo Root: https://root-apk.kingoapp.com/kingoroot-download.htm
3.) Install SuperSU
3.) Install SuperSU Me: https://sites.google.com/site/androidxdacom/file/supersu-me-v6.7.apk?attredirects=0
Device will reboot, you'll want to update the SSU binary, and you'll be good to go.

Thank You for this info, it worked for me :good:

This works on every joying 5.1 unit?
How do you like the Joying brand?

Worked on mine. Thanks man
Sent from my SM-G935T using Tapatalk
---------- Post added at 09:23 PM ---------- Previous post was at 09:20 PM ----------
I have the double din 7 inch in my wrx, finding a proper trim kit that fit around the unit for me was tricky.. as they are a few mm bigger side to side and up an down that standard double dins. But was able to finally find one that was seamless for the wrx. Personally love mine. The pioneers and alpine are getting better but still think my joying is superior.. that's just my opinions.
Sent from my SM-G935T using Tapatalk

Just wanted to confirm for anyone interested that this process is still valid for the latest Joying build (6/12).
http://forum.xda-developers.com/and...tcd-device-t3385309/post67428387#post67428387

what are you doing with root access on the head unit?

bumpaudio said:
what are you doing with root access on the head unit?
Click to expand...
Click to collapse
AD blocking.
Tasker needs root to make some things with hardware.
Отправлено с моего Nexus 6 через Tapatalk

bumpaudio said:
what are you doing with root access on the head unit?
Click to expand...
Click to collapse
Replacing system apps, backups, etc.

w0rdie said:
I ended spending a fair amount of time chasing down a working root method, in the interest of saving time for anyone else who is looking I wanted to post the steps I took.
1.) Settings > Factory Settings > Enter Password: *#hct#root#
2.) Install Kingo Root: https://root-apk.kingoapp.com/kingoroot-download.htm
3.) Install SuperSU
3.) Install SuperSU Me: https://sites.google.com/site/androidxdacom/file/supersu-me-v6.7.apk?attredirects=0
Device will reboot, you'll want to update the SSU binary, and you'll be good to go.
Click to expand...
Click to collapse
I've got an MTCD in the mail and am trying to figure out the best way to take control over it.
That part about "kingo root" is scary as all hell. Who knows what its doing! And despite replacing it later on with "supersu" (which is not much less frightening, since it too is closed source), that is no guarantee that you are removing all remnants of it.
I suggest that this is not a good process to follow.
From what I understand, the recovery on these devices does NOT enforce signed updates. That means that the proper way to install something like this, is to inject it directly into an update. Just skip the exploit step altogether.
/////CANCEL QUESTION: One question I have though; what does the factory settings password actually do?//////
Answer: This turns on root. The silly things comes WITH ROOT ALREADY AVAILABLE!
Its actually better to NOT install any kind of root (kingoroot or supersu), since its already there, just blocked from the android side. This is more secure than leaving the device open to potential exploit, and gives you an avenue to go in and mess with things.

I
I am attempting this method and followed your instructions. I got a message that said adb root and I installed king root and my device rebooted. Super SU says my device is not rooted and Super-Sume gets stuck at "Preparing environment please wait..."
Can I get help?

Anyone know if it is possible to install TWRP? Anyone tried?

Well mine worked fine, then supersu app disappeared and reboot, now I'm stuck with bootloop and can't get into recovery!! Help! RK3188 800*480 MTCD.
Sent from my A0001 using XDA-Developers mobile app

Hi guys, I was able to fix my HU which was completely munted by following this thread.
https://forum.xda-developers.com/an...lopment/rom-malaysk-roms-mtcd-device-t3385309
I used the SD tool to create a boot card, then got the error which is shown in the thread then followed the next page which tells you to use the SD card and a USB thumb drive with the update file on it.
When the error shows up you eject the SD card and the system goes to recovery. Use the install from USB and clear all function and it does its thing.
The joying screen showed up for some time (about 5-10mins) but after booted to system and I'm in business again.
Don't follow my instructions here this is just a brief explanation of what I did, use the link above and try all steps and follow carefully.
Attached photo of the error screen I had in recovery FYI.
Please note this was after I used root method of factory settings code, king root and super su and I did have root access/ the binaries updated etc etc, so don't be scared to try as you can recover your system.
Also the firmware I used was the latest 5.1.1 from Joying website.
My unit is: RK3188 (800*480) MTCD which shipped in December 2016 with android 5.1.1.
{
"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"
}
Sent from my A0001 using XDA-Developers mobile app

[email protected] said:
Anyone know if it is possible to install TWRP? Anyone tried?
Click to expand...
Click to collapse
anyone?

An FYI,
I just got an Eonon GA 2155 w/ Android 5.1.1.
I tried other rooting methods without any success.
I used Kingoroot and it worked great. Compared to my Galaxy phones, a pie of cake.
Thanks to the OP

joying 5.1.1
I don't see a factory settings menu! Did they hide it or are my glasses in need of an upgrade.

rvroamer said:
I don't see a factory settings menu! Did they hide it or are my glasses in need of an upgrade.
Click to expand...
Click to collapse
They moved it to car settings and removed the ability to root through factory settings. (password for factory settings is 3368) there is no * or # button. Can someone please find a work around?!?!

jaaluk said:
They moved it to car settings and removed the ability to root through factory settings. (password for factory settings is 3368) there is no * or # button. Can someone please find a work around?!?!
Click to expand...
Click to collapse
I have one of these units coming, I would like to know as well how to root it since it's apparently disabled.

Anyone ? No more possibilities to root now ?

i tried hooking up an USB keyboard to be able to type in the missing characters, but no success.

Bad screen casting on Android Auto

There is a 1.5 cm black margin between the Android Auto (AA) content and the top of the car's display, which is only visible when I connect Xiaomi A2 lite. It didn't happen with my previous phone. Moreover, the bottom part of the AA content is not shown at all, so that this app became not usable at all.
This happens also when casting with Google photos to my home smart TV, so I don't think that AA is the problem.
Any suggestion of how to fix this issue?

i can confirm the issue. i already read about xiaomi had this problem in conjunction with the MI-UI.
with stock android one on the a2 lite it's obvious this is a general xiaomi problem.
by the way, the mi a1 didn't have the issue...

Eitaje said:
There is a 1.5 cm black margin between the Android Auto (AA) content and the top of the car's display, which is only visible when I connect Xiaomi A2 lite. It didn't happen with my previous phone. Moreover, the bottom part of the AA content is not shown at all, so that this app became not usable at all.
This happens also when casting with Google photos to my home smart TV, so I don't think that AA is the problem.
Any suggestion of how to fix this issue?
Click to expand...
Click to collapse
devlahr said:
i can confirm the issue. i already read about xiaomi had this problem in conjunction with the MI-UI.
with stock android one on the a2 lite it's obvious this is a general xiaomi problem.
by the way, the mi a1 didn't have the issue...
Click to expand...
Click to collapse
the problem seems caused by the aspect ratio (18:9)
There's on solution out there, quiet uncomfortable but's working:
- root your device with magisk
- install "SecondScreen - better screen mirroring for Android Braden Farmer" from play store
- create profile in secondscreen and activate:
Resolution: 800x480
Density: 120 dpi (hpi)
-> android car is fully working on HUR but the screen on handy is due the bad dpi very wired
may be some dev can provide a solution which only changes resolution and dpi on the HUR and keep the device screen on native resolution / dpi

hello, i can also confirm this issue.
attached is two snapshots. The first one is with My Samsung Galaxy S7, here is also good.
The secound one is the snapshot with Xiaomi Mi A2 Lite. Top and bottom have a black border.
I testet this device in a Hyundai i30 (Bj 2018) and Seat Leon (Bj 2018). Also the same problem.
1:
{
"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"
}
2:

Problem me too, Xiaomi Mi a2 lite and JVC M730BT, big black band above and below the screen

Unfortunately I've the same problem with my new A2 lite. On Redmi 4 note (stable Miui 9) works very well.

Lali_Papi said:
Unfortunately I've the same problem with my new A2 lite. On Redmi 4 note (stable Miui 9) works very well.
Click to expand...
Click to collapse
Is this a google fix or a xiaomi fix

New update now with patch 5 august. We Hope that Android Auto is ok!
Nothing nothing, test but fail screen

Nope
silviox said:
New update now with patch 5 august. We Hope that Android Auto is ok!
Nothing nothing, test but fail screen
Click to expand...
Click to collapse
unfortunately, patch 5 august didn't solve the problem. The problem persist.

Same problem.... on an audi A4, hope XIAOMI will solve it quickly.

Guys, A2L phones come with an app named something like "comments" (in Portuguese it's named "comentários", not 100% sure of its name in English) with an orange icon. This app allows you to report bugs directly to the dev team.
I already sent the navigation bar issue when using some apps (such as Spotify).
Try sending the photos you posted here so they can fix that issue sooner or later.
Also, the more people send all those issues, the more they will realize how critical the fixes are.

I can confirm this issue on a Mazda 2 ?

lbsilva said:
Guys, A2L phones come with an app named something like "comments" (in Portuguese it's named "comentários", not 100% sure of its name in English) with an orange icon. This app allows you to report bugs directly to the dev team.
I already sent the navigation bar issue when using some apps (such as Spotify).
Try sending the photos you posted here so they can fix that issue sooner or later.
Also, the more people send all those issues, the more they will realize how critical the fixes are.
Click to expand...
Click to collapse
I've done it.

OK, I execute your orders

silviox said:
OK, I execute your orders
Click to expand...
Click to collapse
Saw someone post it on Reddit /r/ Android & Xiaomi

Lali_Papi said:
I've done it.
Click to expand...
Click to collapse
Me too!

silviox said:
OK, I execute your orders
Click to expand...
Click to collapse
paddl82 said:
Me too!
Click to expand...
Click to collapse
Too late for me, I deleted the app ><

soulz said:
Too late for me, I deleted the app ><
Click to expand...
Click to collapse
Same problem here on a Hyundai Ionic and a Peugeot 308.
I've sent the query with the "Comment" App right now, I hope the multiple warnings will be of use.

solved by flashing lineage os 15.1 - treble
I found a rom which makes Android Auto working.
Upfdate: I also tried out ASOp from phh treble https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659
- Android Auto is also working
- the notch is working here!
I downloaded lineage os Image for ARM64 A/B device with gapps from here: https://forum.xda-developers.com/pr...evice-development/lineage-phh-treble-t3767690
I followed instructions from section "Flash GSI without TWRP": https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
So what did i do exactly?
1. Unlock bootloader (my was already unlocked)
2. Download https://github.com/phhusson/treble_...load/lineage-v21/system-arm64-ab-gapps-su.img
3. Reboot to your device’s stock recovery using either a button combination when booting or issuing the following ADB command when booted in Android: adb reboot recovery. Once here, use the volume keys to navigate and the power button to select the factory reset option.
4. Once your device has been factory reset, reboot to your device’s bootloader using either a button combination when booting or issuing the following ADB command when booted in Android: adb reboot bootloader
5. With your device connected to your PC, open up a command prompt or terminal window in the same directory where you downloaded your GSI of choice.
Enter the following command: fastboot erase system
Enter a command in the following format: fastboot -u flash system-arm64-ab-gapps-su.img
Allow the image to flash, it could take a few minutes. Once it has completed, reboot your device either manually via power key or by entering fastboot reboot.
P.S. the rom doesn't know the notch, bust rest like camera etc. is working!

fizze17 said:
I found a rom which makes Android Auto working.
Upfdate: I also tried out ASOp from phh treble https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659
- Android Auto is also working
- the notch is working here!
I downloaded lineage os Image for ARM64 A/B device with gapps from here: https://forum.xda-developers.com/pr...evice-development/lineage-phh-treble-t3767690
I followed instructions from section "Flash GSI without TWRP": https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
So what did i do exactly?
1. Unlock bootloader (my was already unlocked)
2. Download https://github.com/phhusson/treble_...load/lineage-v21/system-arm64-ab-gapps-su.img
3. Reboot to your device’s stock recovery using either a button combination when booting or issuing the following ADB command when booted in Android: adb reboot recovery. Once here, use the volume keys to navigate and the power button to select the factory reset option.
4. Once your device has been factory reset, reboot to your device’s bootloader using either a button combination when booting or issuing the following ADB command when booted in Android: adb reboot bootloader
5. With your device connected to your PC, open up a command prompt or terminal window in the same directory where you downloaded your GSI of choice.
Enter the following command: fastboot erase system
Enter a command in the following format: fastboot -u flash system-arm64-ab-gapps-su.img
Allow the image to flash, it could take a few minutes. Once it has completed, reboot your device either manually via power key or by entering fastboot reboot.
P.S. the rom doesn't know the notch, bust rest like camera etc. is working!
Click to expand...
Click to collapse
Uh was trying to avoid flashing my pure Android One . Maybe when official Iineage OS comes to A2 Lite

Development [Somewhat DISCONTINUED [Script] Advanced rootless debloater for Samsung phones (and Tablets)

JBNCK One UI Experience - a customized rootless debloater for Samsung phones
NOTE THAT THIS IS A PRE-RELEASE!!! Not every feature works!
{
"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"
}
#
The script is written in python so you need to have python installed (most linux distros come with it anyways). A download link is provided on GitHub.
How to use:
1. In order to have a flawless and smooth experience, back up your data and do a factory reset.
2. Enable USB Debugging
3. Download the program and run it. A window should pop up on your phone. Please confirm.
4. Type in "Y" if you are asked if you are running it for the first time. This will completely nuke your phone and leave you with a settings app
5. After thats done chose a preset (right now only the default Samsung one works!!!)
6. After its done you can either set up your phone like normal or chose from the other options (for example if you want software updates or NFC support).
If a feature you use gets removed:
1. Install package names viewer from play store and look for the package name of the app/feature.
2. Run the program and enter "N" if you are asked if you are running the script for the first time
3. Chose option 10 and enter the package name
If you encounter any other problems feel free to tell me about it here.
Download: https://github.com/JBNCK/One-UI-Experience/releases​

to get back the default settings i just do a factory reset or do I have to flash the rom?

M4jQ said:
to get back the default settings i just do a factory reset or do I have to flash the rom?
Click to expand...
Click to collapse
You just need to do a factory reset, no need to flash the firmware

Trojan:Win32/Wacatac.H!ml
Why?

Vega56 said:
Trojan:Win32/Wacatac.H!ml
Why?
Click to expand...
Click to collapse
pretty sure this is not a trojan lmao you can even see the source code on github

JanBoyGamer23 said:
pretty sure this is not a trojan lmao you can even see the source code on github
Click to expand...
Click to collapse
Yeah, but why is this showing? ...

in which file?

!!! Warning
The program I used in order to compile the python file is probably malicious. The py file is undetected by virustotal but the compiled exe is. I will remove the download until I fixed the problem!
DO NOT RUN THE .EXE UNTIL I PROVIDED A NEW DOWNLOAD LINK!!!

NOICE! NICE

Update:
Ok I repacked the script without the malicious .exe. Once again, I apologize for the inconvenience. Now you also need to have python3 installed on windows. A download link is provided on GitHub.
Also, next release will add the missing features.
Have fun with my little script!

Works perfect.
Hope option 3 comes soon.

when i connect the phone to pc nothing happens, no popup.
usb debug on, i did factory reset.
i connect the phone and the phone asks me if i want to share files with pc, i consent and then i open up your program but nothing happens
Edit: well i solved coping the script in adb

Vega56 said:
Works perfect.
Hope option 3 comes soon.
Click to expand...
Click to collapse
Glad it worked and thanks for the positive feedback I'm working on the other options and will release them in the next couple of days. I'm a bit busy right now because of school but I try to deliver it as fast as possible

Khaver89 said:
when i connect the phone to pc nothing happens, no popup.
usb debug on, i did factory reset.
i connect the phone and the phone asks me if i want to share files with pc, i consent and then i open up your program but nothing happens
Edit: well i solved coping the script in adb
Click to expand...
Click to collapse
Nice to hear that you managed to solve the problem, however, did you try installing the USB drivers from Samsung? (either manually or by connecting your phone to your computer with usb debugging on and performing a windows update)

which applications are needed to make samsung findmyphone work and to enable backup of Secure Folders?

Can i remove google services with that too?
Are there any description what each of the options do? (more detailed?)

Can you please add an option to debloat GOS, game booster and Game launcher also any other system app that may be throttling the tabs performance?
Thanks

HARNATH said:
Can you please add an option to debloat GOS, game booster and Game launcher also any other system app that may be throttling the tabs performance?
Thanks
Click to expand...
Click to collapse
you can use ADB AppControl to find apps and remove it or find names and add it to this script
edit:
I also found Universal Android Debloater GUI

M4jQ said:
which applications are needed to make samsung findmyphone work and to enable backup of Secure Folders?
Click to expand...
Click to collapse
sorry for the late reply
The packages are
com.samsung.knox.securefolder
com.samsung.android.fmm

luffy786 said:
Can i remove google services with that too?
Are there any description what each of the options do? (more detailed?)
Click to expand...
Click to collapse
Yes but it is not a root debloat so you cant replace them with microg. To remove gms from your phone you have to choose option 11 and type in com.google.android.gms and com.google.android.gsf

Question Keeping Stock Camera App, Throwing out Google Analytics (boot.img, Magisk, Debloater?)

Hello community,
I have no programming experience whatsoever but I am interested in having my Oneplus 9 Pro degoogled because I value my privacy.
Installing a Custom ROM is not an option yet because I don't seem to have found a Camera app that is as satisfying as the stock one (I especially like its Pro mode).
My friend suggested installing Magisk and Debloater, delete all Google services and stay with the Stock rom. So I unlocked the bootloader, booted into fastboot, booted TWRP. I flashed an official firmware Update (Oxygen OS 11.2.10.10.LE15AA), it loaded up to 47% and then showed an Error. I pushed some buttons until I was stuck in a Fastboot-Loop. Luckily I soon found a thread and tried out "fastboot --set-active=b" which solved the issue by booting into Oxygen OS 11.2.10.10.
I would like to understand what happened - I guess I tried to flash an update that was not full and somehow got mixed up with the slots, but the Update was installed anyway on the other slot which I was able to access with changing active slots - but I don't really know.
Anyway, what I really like to know is if anyone has any suggestions for me how to move on from here.
I downloaded the Magisk App but wasn't able to install it properly as I wasn't able to extract the boot.img. I tried with Python 3.8 and payload dumper on my Mac but the command "pip install -r requirements.txt" doesn't work (neither does python -m pip install -r requirements.txt or putting ./ in front of it - it always answers with "no such file or directory").
I also couldn't flash it with TWRP as I don't have the zip file and I heard conflicting opinions about that confused me.
Can somebody help me with a guide for dummies? Or maybe even come up with a different solution for my need to access the Stock Camera App but not having Google Tracking involved in any of my phone activities.
Thank you, this will be highly appreciated!

lai.sha said:
Hello community,
I have no programming experience whatsoever but I am interested in having my Oneplus 9 Pro degoogled because I value my privacy.
Installing a Custom ROM is not an option yet because I don't seem to have found a Camera app that is as satisfying as the stock one (I especially like its Pro mode).
My friend suggested installing Magisk and Debloater, delete all Google services and stay with the Stock rom. So I unlocked the bootloader, booted into fastboot, booted TWRP. I flashed an official firmware Update (Oxygen OS 11.2.10.10.LE15AA), it loaded up to 47% and then showed an Error. I pushed some buttons until I was stuck in a Fastboot-Loop. Luckily I soon found a thread and tried out "fastboot --set-active=b" which solved the issue by booting into Oxygen OS 11.2.10.10.
I would like to understand what happened - I guess I tried to flash an update that was not full and somehow got mixed up with the slots, but the Update was installed anyway on the other slot which I was able to access with changing active slots - but I don't really know.
Anyway, what I really like to know is if anyone has any suggestions for me how to move on from here.
I downloaded the Magisk App but wasn't able to install it properly as I wasn't able to extract the boot.img. I tried with Python 3.8 and payload dumper on my Mac but the command "pip install -r requirements.txt" doesn't work (neither does python -m pip install -r requirements.txt or putting ./ in front of it - it always answers with "no such file or directory").
I also couldn't flash it with TWRP as I don't have the zip file and I heard conflicting opinions about that confused me.
Can somebody help me with a guide for dummies? Or maybe even come up with a different solution for my need to access the Stock Camera App but not having Google Tracking involved in any of my phone activities.
Thank you, this will be highly appreciated!
Click to expand...
Click to collapse
Never mind - I just found it here: https://forum.xda-developers.com/t/guide-magisk-unlock-root-keep-root-oos-12-c-65.4252373/
I'm stil open for better solutions if someone has them!

Hey there!
Loading up to 47% and then throwing an error is actually quite normal, it should still succeed.
Anyway, some intelligent person was able to manage to move the stock OOS cam to custom ROM's. I'm currently running Nameless which is Android 12 which has the OOS cam.
Since you asked for a non-gapps build, you should look for a 'pristine' or 'vanilla' build. I know out of the top of my head that StagOS has builds like this, but you can also search the forums yourself. If the title of the ROM says [OOS Cam] then the stock camera app is included.
You can also use ADB to debloat (remove) all google stuff from your phone. This is a guide which could be helpful: https://forum.xda-developers.com/t/...bloating-thread-for-the-s20-u-series.4089089/
This way, you can keep the same stock software without having to go through the hassle of installing a custom ROM

GolovaRaoul said:
Hey there!
Loading up to 47% and then throwing an error is actually quite normal, it should still succeed.
Click to expand...
Click to collapse
Oh thank you, that is very satisfying to know. Why is that?
GolovaRaoul said:
Anyway, some intelligent person was able to manage to move the stock OOS cam to custom ROM's. I'm currently running Nameless which is Android 12 which has the OOS cam.
Click to expand...
Click to collapse
Are you thinking of this one: https://forum.xda-developers.com/t/apk-oneplus-camera-for-any-a11-custom-rom.4350205/ That's the 7 Pro App, which is crashing on my friend's phone on Lineage OS in macro mode
GolovaRaoul said:
Since you asked for a non-gapps build, you should look for a 'pristine' or 'vanilla' build. I know out of the top of my head that StagOS has builds like this, but you can also search the forums yourself. If the title of the ROM says [OOS Cam] then the stock camera app is included.
You can also use ADB to debloat (remove) all google stuff from your phone. This is a guide which could be helpful: https://forum.xda-developers.com/t/...bloating-thread-for-the-s20-u-series.4089089/
Click to expand...
Click to collapse
Great, thank you! As I got Magisk running, I prefer the debloater as I can play with it without Laptop access
GolovaRaoul said:
This way, you can keep the same stock software without having to go through the hassle of installing a custom ROM
Click to expand...
Click to collapse
Thank you for all your help!

lai.sha said:
Oh thank you, that is very satisfying to know. Why is that?
Are you thinking of this one: https://forum.xda-developers.com/t/apk-oneplus-camera-for-any-a11-custom-rom.4350205/ That's the 7 Pro App, which is crashing on my friend's phone on Lineage OS in macro mode
Great, thank you! As I got Magisk running, I prefer the debloater as I can play with it without Laptop access
Thank you for all your help!
Click to expand...
Click to collapse
Eeehm I don't know why it gets stuck at 47%. It's a common issue, you can google it and you'll find lots of results
{
"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"
}
And I mean these ROM's for example. Maybe some of these ROMs in the list also have the OxygenOS cam but I don't know. They are pre-built into the ROM so you don't need to do anything, just install the ROM and you should have the OxygenOS cam also

GolovaRaoul said:
Eeehm I don't know why it gets stuck at 47%. It's a common issue, you can google it and you'll find lots of results
View attachment 5742135
And I mean these ROM's for example. Maybe some of these ROMs in the list also have the OxygenOS cam but I don't know. They are pre-built into the ROM so you don't need to do anything, just install the ROM and you should have the OxygenOS cam also
Click to expand...
Click to collapse
Interesting, I thought that maybe that's what you meant but I wasn't sure if it just means "compatible" with...
Thank you so much, I guess it's time to play

Development Android 14 Beta Program DP 1

We don't recommend installing this on your main device, and especially if you're not familiar with development or alpha/beta testing. There are quite a few known issues right off the bat:
{
"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"
}
Developer Preview 1
WLAN malfunctions in certain scenarios
Connection fails when casting to a TV display
Red screen is seen when switching from Guest mode to Owner mode in certain scenarios
Manual connection fails after the phone is disconnected from the tablet
WeChat calls may not ring with Bluetooth headsets
Red screen flashes when creating a new calendar
Screen freezes when taking picture with the front camera in WhatsApp
Which devices support the preview?​
OnePlus 11 (all variants except carrier-branded e.g. TMO/VZW)
Where can I get the preview?​Before installing, be aware that installing a developer preview carries a risk of bricking your phone. Make sure you know what you're doing, and backup your files/media before proceeding. Also ensure your battery level is at least 30% and you have at least 5GB space left on your device.
Refer to the forum threads for more information:
OnePlus 11:
Developer Preview 1
Can I revert to the stable version of OxygenOS?​Yes, please read the forum thread of your device as linked above for detailed instructions. Rolling back will completely wipe all your data, so please take a backup before proceeding.
Below is the rollback/downgrade packages for the OnePlus 11. Make sure you choose the correct rollback package for your device and region. We are providing these links purely for your convenience, as rolling back isn't natively supported by our app. After downloading the correct rollback package, move the file from the "Downloads" directory to the topmost directory of internal storage (the same directory that the "Downloads" folder is in). You may also have to rename ".jar" to ".zip".
Then, open Settings -> About device -> Version and tap "Build number" 7 times. This will enable Android's built-in "developer mode" (you might have to enter your phone's PIN/password too). Once this is done, "Local upgrade" will once again be visible in Settings -> About device -> Software update -> top-right button. It it doesn't show up, download & install OPLocalUpdate_For_Android13.apk, and use that to install updates locally.
Rollback packages​The following packages will rollback your device to Android 13, and will wipe all your data. Note that these rollback ZIPs will take you back to A.09 even though the latest OOS13 stable version at the time of writing is A.10. These are not the packages you should download if you're looking to update to Android 14/U.
OnePlus 11 / Rollback packages :
OnePlus 11 NA Version (A.09)
OnePlus 11 IN Version (A.09)
OnePlus 11 EU Version (A.09)
OnePlus 11 GLO Version (A.09)
Thumbnail and image credits: Google/AOSP/OnePlus
Source: Oxygen updater/OnePlus firum

Rollback packages can be very helpful to convert CN Modele to IN, EU or GLO and also to be flashed to solve softbrick devices.

Init_boot_CPH2449_Android 14_DP1

Steve0007 said:
Init_boot_CPH2449_Android 14_DP1
Click to expand...
Click to collapse
do you think flashing 2449glo on my 2451 would change it to a 2449glo? or is it just the reverts that work like that?

kevp75 said:
do you think flashing 2449glo on my 2451 would change it to a 2449glo? or is it just the reverts that work like that?
Click to expand...
Click to collapse
The rollback packages are very fresh, so untill someone try, it is difficult to say.
But theoretically it could work. At least with 2551 you will be able to get full OTA updates

Steve0007 said:
The rollback packages are very fresh, so untill someone try, it is difficult to say.
But theoretically it could work. At least with 2551 you will be able to get full OTA updates
Click to expand...
Click to collapse
exactly what I was thinking lololol

In the meantime... here's CPH2451 A14 Stock and Magisk Patched init_boots

@Steve0007
Could you please rename the topic to something more understandable and manageable?
E.g. "Android 14 beta 1 (DP) for OnePlus 11"
I don't understand why you called it "Google 14" - it just makes no sense.
Thanks.

Hey finally I can convert my phone back to the US firmware.

My OP 11 is stucked/rebooting in fastboot mode after flashed 14 beta EU. Booting to black screen. Can reboot to fastboot mode.
Tried to repaired via Fastboot Enhance and roll back package with no success.. I have to ignore some partinations. Any solutions?

lassetth said:
My OP 11 is stucked/rebooting in fastboot mode after flashed 14 beta EU. Booting to black screen. Can reboot to fastboot mode.
Tried to repaired via Fastboot Enhance and roll back package with no success.. I have to ignore some partinations. Any solutions?
Click to expand...
Click to collapse
Try switching fastboot slot. This fixed for me, although it will take you back to a13

JPower123 said:
Try switching fastboot slot. This fixed for me, although it will take you back to a13
Click to expand...
Click to collapse
Thanks, fixed!

cabagekiller said:
Hey finally I can convert my phone back to the US firmware.
Click to expand...
Click to collapse
what are/were you on for firmware?

Steve0007 said:
The rollback packages are very fresh, so untill someone try, it is difficult to say.
But theoretically it could work. At least with 2551 you will be able to get full OTA updates
Click to expand...
Click to collapse
mmm... 2451 only gets incrementals. I'm testing the 2449 A.09 downgrade right now

kevp75 said:
mmm... 2451 only gets incrementals. I'm testing the 2449 A.09 downgrade right now
Click to expand...
Click to collapse
Steve0007​Welp... I can confirm.
The downgrade for CPH2449 GLO for my CPH2451 US boots.
Tested: calls, texts, wifi, camera, bluetooth, etc... all work fine.
About to root, and then upgraded to A.10

kevp75 said:
Steve0007​Welp... I can confirm.
The downgrade for CPH2449 GLO for my CPH2451 US boots.
Tested: calls, texts, wifi, camera, bluetooth, etc... all work fine.
About to root, and then upgraded to A.10
Click to expand...
Click to collapse
Rooted fine, and upgraded to A.10 fine... (and now I have a full OTA package! lololol)

kevp75 said:
Rooted fine, and upgraded to A.10 fine... (and now I have a full OTA package! lololol)
Click to expand...
Click to collapse
Yep, as we thought

Hi, a stupid question, will running the downgrade from color os directly works fine? ;-D

t0ng00 said:
Hi, a stupid question, will running the downgrade from color os directly works fine? ;-D
Click to expand...
Click to collapse
Most probably yes if you want to go back to Color os. There is already an Android 14 DP 1 available.

Steve0007 said:
Most probably yes if you want to go back to Color os. There is already an Android 14 DP 1 available.
Click to expand...
Click to collapse
Sorry for not making myself clear, I mean, downloading the apk from the forum and take it to a CN color os device and forcefully "downgrade" it to the 13 ROM - could it be even possible?
Or forcefully for to DP1 NA first and then, down?