Develop Bugs

Remove completely Experience ROM

Hi all,
I bought an old Oneplus 3 which have been flashed Experience ROM (https://forum.xda-developers.com/oneplus-3/development/rom-experience-rom-v1-0-t3522259). Now I want to remove it completely.
I can enter fastboot then run command to boot recovery (http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img) then adb sideload to flash (http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_4.0.2/).
Stock ROM works well but the boot screen still is Experience ROM.
{
"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"
}
I think that causes some problems with my later development.
Please help me to find out which partition of flash may not reset to original, or is there any way to flash completely as stock production?
Thanks all.

I think you need to just flash the original boot logo.

Wipe System, Data, cache and sideload stock from then you will be full stock for sure!

https://forum.xda-developers.com/oneplus-3/themes/mod-custom-boot-logo-pack-op3-t3525143
You can try one of these... They are way too good or you can flash the original one given in the OP.
Hope it helps... Thanks!

I wonder if there is any way to flash all flash of Oneplus 3 as stock. That mean flash all recovery, boot, system ...

Puddi_Puddin said:
Wipe System, Data, cache and sideload stock from then you will be full stock for sure!
Click to expand...
Click to collapse
This does not work. I've tried it before. Complete stock sideload, both OB11 and stable.
FYI: Jamal has removed the bootlogo on his latest releases

Shresth45 said:
This does not work. I've tried it before. Complete stock sideload, both OB11 and stable.
FYI: Jamal has removed the bootlogo on his latest releases
Click to expand...
Click to collapse
Boot logo and animation is stored on the System partition. By wiping it and overwriting it by flashing stock rom it should dissepear.

200791 said:
I wonder if there is any way to flash all flash of Oneplus 3 as stock. That mean flash all recovery, boot, system ...
Click to expand...
Click to collapse
There is a tool that's used to unbrick the op3, this tool flashes every partition to full stock again.
You need to look at the mega unbrick thread and use the full unbrick tool that wipes everything.

Any custom Nougat or Oreo ROMS compatible with XT1799-2??

Hi,
It seems I am unlucky to invested in the latest model in the Montana family as I cannot find a single custom ROM compatible with this phone. Each time I flash any Montana custom ROM via TWRP it reboots to Recovery and never boots into system. I wish someone has some positive news I have overseen. On my old Xiaomi I ran CM and the Lineage for many years, but that is now out of question.
Be happy for any information on how to install any of the custom roms that would work keep the functionality of the device operational including nfc and front camera (which differs from classic G5S)
Cheers
Six

Did you get the ROM? I'm also searching a way to get the front cam and nfc to work with oreo.

Adaptation of ROM STOCK Android 8.1.0 Oreo for XT1799-2 MONTANA_RETCN
Any actions with the phone you do at your own risk! Used for adaptation MONTANA_RETAIL_8.1.0_OPPS28.65-37-7-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml the firmware is taken from https://mirrors.lolinet.com. Original publication I...
forum.xda-developers.com
This is OK for moto g5s xt1799-2.
I tested it.
Front camera works for xt1799-2. Only 400MP for front camera.
But only 32bit.
1. You'd better backup the 'efs‘ and 'persist' folder via twrp. (You may not see the 'persist' folder in some early twrp version, change a newer version twrp.
2. Use magisk to root your system, then back the 'persist' and 'cid' files in the following path:
/dev/block/bootdevice/by-name/
’persist‘ and ’cid‘ files
See:https://bbs.ixmoe.com/t/topic/27722
{
"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"
}
Some device may not see the persist folder in twrp, but efs folder is a must!
These 4 files backups are must in cast your imei turn 0 and your baseband not found or been changed and lost signal when you flash rom.
If your imei turns 0, your just restore the 'efs' backup via twrp.
Lineageos 18.1 also works fine for xt1799-2. but the battery drops down very fast! A little bit abnormal.
Moto 8.1.0 oreo stock rom
Lineageos 18.1

Question Virtual a/b device?

Does anybody know if this device has implemented virtual a/b or if it's just normal a/b?
I need to know this to finish building my device tree.
{
"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"
}

this is very important when you want a custom rom for A52s phone

TheYellowRay said:
Does anybody know if this device has implemented virtual a/b or if it's just normal a/b?
I need to know this to finish building my device tree.
View attachment 5595041
Click to expand...
Click to collapse
As far as i can tell it has neither one. The treble info app says our device doesn't support seamless updates witch indicates A-only.
After some searching it seems like Samsung doesn't implement (virtual) A/B to any of it's devices (yet?).

It does have A/B, but I'm not sure about virtual a/b
ROO3VER said:
As far as i can tell it has neither one. The treble info app says our device doesn't support seamless updates witch indicates A-only.
After some searching it seems like Samsung doesn't implement (virtual) A/B to any of it's devices (yet?).
Click to expand...
Click to collapse
Don't use treble check, it is inaccurate
Phh recommends treble info

Treble info says A/B, but no idea about virtual

TheYellowRay said:
Treble info says A/B, but no idea about virtual
Click to expand...
Click to collapse
I'm using treble info by @hackintosh5, the one i believe is recommended by Phh.
The screenshot i posted is from this app...

TheYellowRay said:
Treble info says A/B, but no idea about virtual
Click to expand...
Click to collapse
Does the treble info app say your A52S supports seamles updates??

Ah my bad
Your screenshot does indicate that the phone is A/B
Also not having seamless updates doesn't necessarily mean the device isn't virtual A/B

TheYellowRay said:
Ah my bad
Your screenshot does indicate that the phone is A/B
Also not having seamless updates doesn't necessarily mean the device isn't virtual A/B
Click to expand...
Click to collapse
The screenshot indicates we should use an A/B system, this doesn't necessarily mean we have an A/B partition.
Every device with an android 9 or higher vendor has to use an A/B system even the A-only ones.
If we have (virtual)A/B it would be very strange seamless updates aren't supported...

Well I can confirm that the device uses A/B partitions due to the development tree template generation.
I'm more concerned about virtual.

TheYellowRay said:
Well I can confirm that the device uses A/B partitions due to the development tree template generation.
I'm more concerned about virtual.
Click to expand...
Click to collapse
when will the TWRP be ready?

Stonecroissant said:
when will the TWRP be ready?
Click to expand...
Click to collapse
Arobase will know, for this time everyone not know

TheYellowRay said:
It does have A/B, but I'm not sure about virtual a/b
Don't use treble check, it is inaccurate
Phh recommends treble info
Click to expand...
Click to collapse
A bit off topic but have you tried phh's gsi on our device?

[ROM][OFFICIAL][13] AncientOS 7.1 - TexasCake - Steel [24/05/2023]

AncientOS 7.1 for OnePlus Nord [avicii]​
{
"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"
}
Download
[Changelog and installation guide is available on the website]
Telegram Support Group
Donate to support the build
UPI : [email protected]
PayPal​
Maintainer: Sreeshankar K
ROM Source: https://github.com/Ancient-Roms
Device tree: https://github.com/Sanju0910/android_device_oneplus_avicii-ancientos
Kernel Source: https://github.com/Sanju0910/android_kernel_oneplus_avicii

Reserved

Reserved

Reserved

Looks good. Will I need to erase my phone if I move from rising os android 13 ?

princen41 said:
Looks good. Will I need to erase my phone if I move from rising os android 13 ?
Click to expand...
Click to collapse
Take complete backup before flashing this ROM. QPR1 based roms. Sometimes clearing data partition only will not boot the ROM. So, you will be to format Internal storage + data.

Sreeshankar K said:
Take complete backup before flashing this ROM. QPR1 based roms. Sometimes clearing data partition only will not boot the ROM. So, you will be to format Internal storage + data.
Click to expand...
Click to collapse
Ok.

I'm unable to register finger about 15% is going through, need help....

Godslayerbezerker said:
I'm unable to register finger about 15% is going through, need help....
Click to expand...
Click to collapse
Clear dalvik/art cache using custom recovery. If that doesn't work, then clean flash the rom.

Which custom recovery would you recommend? Orange fox is getting over written tried multiple times.

Godslayerbezerker said:
Which custom recovery would you recommend? Orange fox is getting over written tried multiple times.
Click to expand...
Click to collapse
Pitchblack or OrangeFox.
It is the default behaviour while updating/flashing the rom. So, if you need to continue to use the custom recovery. Then flash the recovery zip file after updating/flashing the rom zip file before the first boot. Then you you can use the custom recovery.

How to install FLO build on DEB device

Could you explane me how to install lineage-18.1 on LTE device. I'm ready to abandon the use of LTE in favor of the new Android.
Thanks a lot

Do you mean FLO (Wifi) vs DEB (LTE)?

V0latyle said:
Do you mean FLO (Wifi) vs DEB (LTE)?
Click to expand...
Click to collapse
Yeap, my mistake. I have Nexus 7 2013 LTE and i want install lineage 18

EgaRock said:
Yeap, my mistake. I have Nexus 7 2013 LTE and i want install lineage 18
Click to expand...
Click to collapse
I don't think it should make any difference whether your device is LTE or WiFi - except for maybe the kernel, due to the slightly different hardware.
I'm also not familiar with the Nexus 7, so what problems are you having or you think you are going to have?

V0latyle said:
I don't think it should make any difference whether your device is LTE or WiFi - except for maybe the kernel, due to the slightly different hardware.
I'm also not familiar with the Nexus 7, so what problems are you having or you think you are going to have?
Click to expand...
Click to collapse
My Error when im try install last Lineage os for my LTE device
Spoiler: my Error
{
"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"
}

Maybe try LineageOS 20.0?
I think there's a way to edit the installation script in the ROM zip so that it'll install on your hardware but I am not a developer so I have no idea how.
Maybe you could be the first to build LOS 18.1 for DEB?

Basically, custom ROM installation process for nexus 7 2013 is similar as below.
1. Boot to Fastboot
2. <optional> Unlock OEM LOCK if state LOCKED
3. Flash recent TWRP recovery image and enter recovery mode
4. <optional> Adjust partition with script to get sufficient size of system partition, and reboot into recovery mode to get renewed partition info by TWRP recovery
5. Put pre-built custom ROM image on internal storage
6. Install image and reboot
Nothing is different for installation process even though you try install any other kind of custom ROMs.
It's another word to install flox ROM on deb device. Parse installation script in zip file and revise device detection script. I may works, but OS may not work properly after installation because kernel is different.