…Enter suggestions to improve documentation in this category. Do not raise bugs or issues here…
Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online services
I assume this documentation was copied from LineageOS?
However LineageOS has two variants of this tablet, a “Pad 2 Pro” (OPD2413) and a “Pad 3” (OPD2415). While I’m not entirely sure on the details, I believe it was launched as the “Pad 2 Pro” in China and/or Asia and shortly after as the “Pad 3” globally. Regardless they are basically two identical devices, even sharing the same codename “erhai” and LineageOS builds images from the same device tree.
/e/OS should probably have device pages for both variants as well. Or one combined page.
If it’s not an accident and there’s some reason why only a single variant is documented, I think it’d be better to have a page for the “Pad 3” instead, as that is the name most of the english-speaking internet knows this tablet by.
1 Like
according to Supported devices - Google Play Help - Google Support
| Retail Branding | Marketing Name | Device | Model |
|---|---|---|---|
| OnePlus | 一加平板 2 Pro | OP615EL1 | OPD2413 |
| OnePlus | Pad 3 | OP6190L1 | OPD2415 |
1 Like
Around the new year I flashed this image on my Pad 3. And I can confirm that the erhai image works on the OnePlus Pad 3 (OPD2415) with no major issues. The only issues I noticed were that the lock screen is always portrait and the stock launcher acted a bit funny, but I suspect this is more of a general tablet support issue rather than a device-support issue. Typical features like networking, camera, audio and video playback all work fine.
The device requires flashing additional partitions like vbmeta, so I nabbed those from LineageOS instead.
Also the device image used for erhai is wrong. It’s not a photo of the OnePlus Pad 2 Pro or OnePlus Pad 3 (Which look identical) which have standard corner cameras, not the large and centered camera circle.
The image used on the page is of the OnePlus Pad 2 (caihong) which is a different and unrelated device.
“erhai” was released as the “Pad 2 Pro” in China, and “Pad 3” internationally.
“caihong” is the unrelated “Pad 2”
Dunno why OnePlus named them this way.
Yesterday, I got my new OnePlus Pad 3 (OPD2415) and I was eager to finally flash e/os (3.4 A15) on it.
It went absolutely smoothly and took me just about 30 minutes (except of the preparation time like finding and downloading the specific images).
I used:
e/os image:
missing lineageOS partition-images:
adb/fastboot software:
e/os installation link:
Actually, I wanted to wait until the officially supported image was available (announced in December), but I wasn’t patient enough.
The Pad 3 was delivered with A15 and prompted me to install a software update, but since this was the same Android version as e/OS, I skipped the update of stock OS.
Thanks to all developers and supporters of e/OS. With your help, I was able to get a state-of-the-art tablet without an intrusive tracking OS for just about 400€. 
1 Like
Hey there,
because I couldn’t find anything about it here, I have come with a warning and a question regarding Android 16 and ARB.
It seems OnePlus changed something with the new update so the ARB (Anti roll back) counter is set to 1. This means you can not downgrade to a version or ROM with ARB0.
If you’ll do, a fuse will break leaving you with a bricked device. At the moment the only way to repair this, is by changing the motherboard.
From what I have read lineage will include the fw-part with arb1 in all future builds.
I got my pad 3 but it is already updated to A16 so my ARB is at 1 and for that the A15 Version of e/os would brick my pad3.
What I came to ask is, how will you guys handle this?
Will you include the arb1 parts in the ROM too, like lineage?
Will there be a A15 with ARB1?
Maybe a warning regarding this on the installpage could help/ warn other users.
Greetings
flex0
Hello @flex0, Welcome to the /e/ users forum.
dev team is not here,
but i can answer that /e/OS is a LineageOS fork.
current /e/ builds include related firmware parts
so i bet all needed changes will be applyed.
Thanks for sharing the details. Will pass it to the build team and get back with their response.
Update: For now, users are advised to wait for A16 to roll out for the devices and not downgrade devices to A15.
1 Like
Hey thanks for your reply.
Is there an estimated release date for the A16 Version?
If it isn’t ‘right around the corner’ you realy should issue a warning or write something in the install wiki, cause right now it even tells you to downgrade if release versions differ.