[Q&A] Noob -Friendly Q&A Help Thread - Ask Your Questions Here!

[pololovestreks]

If you're waiting 10 minutes or so after flashing the rom & GApps and it's still not booted then I don't know what's wrong.

can't figure it out either, tried flashing Lineage and it's stuck on the boot animation too.

Any clue at all?

 

[Sam Nakamura]

can't figure it out either, tried flashing Lineage and it's stuck on the boot animation too.

Any clue at all?

This command should give you info about the bootloader status, post the output. I was under the impression that the stock reset tool locks the bootloader, so you're in a factory state when you successfully ran it but I never needed to use it myself in my OP2 days....

fastboot oem device-info

Also try flashing Magisk 17.1 along with the custom ROM, maybe it's a kind of encryption issue that magisk can handle, there was a similar case already on this thread which was solved successfully but I can't remember if it was the exact same thing and what was done exactly, I'll check later when I have time to find it and report back when I have a clue or you can also check the thread via the search bar to find corresponding posts...

Sent from my OnePlus5T using XDA Labs

 

[Spannaa]

This command should give you info about the bootloader status, post the output. I was under the impression that the stock reset tool locks the bootloader, so you're in a factory state when you successfully ran it but I never needed to use it myself in my OP2 days....

fastboot oem device-info

Also try flashing Magisk 17.1 along with the custom ROM, maybe it's a kind of encryption issue that magisk can handle, there was a similar case already on this thread which was solved successfully but I can't remember if it was the exact same thing and what was done exactly, I'll check later when I have time to find it and report back when I have a clue or you can also check the thread via the search bar to find corresponding posts...

Sent from my OnePlus5T using XDA Labs

I was under the impression that @pololovestreks used my unofficial Oxygen OS 3.0.2 fastboot zip and then updated to OOS 3.6.1 so his bootloader shouldn't be locked but, as you said, fastboot oem device-info would clarify this.

I didn't think that OOS for the OP2 was encrypted by default?

 

[Sam Nakamura]

I didn't think that OOS for the OP2 was encrypted by default?

Yeah, now as you said it I remember there's definitely no default encryption on OP2... I'm very sure about it, I would also be surprised if you weren't right about the reset tool but let's see the command line output


Sent from my OnePlus5T using XDA Labs

 

[pololovestreks]

I was under the impression that @pololovestreks used my unofficial Oxygen OS 3.0.2 fastboot zip and then updated to OOS 3.6.1 so his bootloader shouldn't be locked but, as you said, fastboot oem device-info would clarify this.

I didn't think that OOS for the OP2 was encrypted by default?

Which is what I have done!
had corrupted my EFS partition I think and didn't have a backup!

---------- Post added at 02:16 PM ---------- Previous post was at 02:15 PM ----------

Yeah, now as you said it I remember there's definitely no default encryption on OP2... I'm very sure about it, I would also be surprised if you weren't right about the reset tool but let's see the command line output


Sent from my OnePlus5T using XDA Labs

Which is what I thought,but bootloader is unlocked

---------- Post added at 02:17 PM ---------- Previous post was at 02:16 PM ----------

This command should give you info about the bootloader status, post the output. I was under the impression that the stock reset tool locks the bootloader, so you're in a factory state when you successfully ran it but I never needed to use it myself in my OP2 days....

fastboot oem device-info

Also try flashing Magisk 17.1 along with the custom ROM, maybe it's a kind of encryption issue that magisk can handle, there was a similar case already on this thread which was solved successfully but I can't remember if it was the exact same thing and what was done exactly, I'll check later when I have time to find it and report back when I have a clue or you can also check the thread via the search bar to find corresponding posts...

Sent from my OnePlus5T using XDA Labs

I'll try this and update!
LEt me know in case you find it

Here it is

(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device is_verified: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_locked: 1
(bootloader) exec_console_unconsole: 0
OKAY [ 0.094s]

 

[Spannaa]

had corrupted my EFS partition I think and didn't have a backup!

When you restored to OOS 3.0.2 with the fastboot zip and then upgraded to OOS 3.6.1, was your EFS still corrupt?
Did both sim slots have an IMEI number? (Different IMEIs and neither of them 0)?

If so, then your EFS probably isn't corrupt.

 

[pololovestreks]

When you restored to OOS 3.0.2 with the fastboot zip and then upgraded to OOS 3.6.1, was your EFS still corrupt?
Did both sim slots have an IMEI number? (Different IMEIs and neither of them 0)?

If so, then your EFS probably isn't corrupt.

EFS isn't corrupt anymore.

Its just that OOS 3.6.1 and RR Oreo have vast differences, that's why I'm looking to shift

---------- Post added at 04:53 PM ---------- Previous post was at 04:39 PM ----------

When you restored to OOS 3.0.2 with the fastboot zip and then upgraded to OOS 3.6.1, was your EFS still corrupt?
Did both sim slots have an IMEI number? (Different IMEIs and neither of them 0)?

If so, then your EFS probably isn't corrupt.

I vaguely remember there being a modified twrp recovery file for some reason, maybe that would help.

Do you have a link to that?

 

[Spannaa]

EFS isn't corrupt anymore.

Its just that OOS 3.6.1 and RR Oreo have vast differences, that's why I'm looking to shift

---------- Post added at 04:53 PM ---------- Previous post was at 04:39 PM ----------




I vaguely remember there being a modified twrp recovery file for some reason, maybe that would help.

Do you have a link to that?

IIRC, the modified TWRP was for switching between H2OS and OOS 2 so it'd be of no use here.

Have you asked about your issue in the RR thread?

 

[pololovestreks]

IIRC, the modified TWRP was for switching between H2OS and OOS 2 so it'd be of no use here.

Have you asked about your issue in the RR thread?

Yes, I have!
Haven't got any solution (yet)

 

[Sam Nakamura]

Yes, I have!
Haven't got any solution (yet)

Sure you flash correctly, you do the necessary wipes of system, data, cache and Dalvik/ART?
And you have a compatible version of TWRP for flashing? Did you check the custom ROM thread for a recommendation of TWRP?

The only modified TWRP I know for OP2 is hybrid twrp, used when different bootloaders (OOS vs. H2OS) made issues and normal TWRP wasn't able to handle this but this issues are long gone and hybrid TWRP is outdated...

Sent from my Nexus 4 using XDA Labs

 

[pololovestreks]

Sure you flash correctly, you do the necessary wipes of system, data, cache and Dalvik/ART?
And you have a compatible version of TWRP for flashing? Did you check the custom ROM thread for a recommendation of TWRP?

The only modified TWRP I know for OP2 is hybrid twrp, used when different bootloaders (OOS vs. H2OS) made issues and normal TWRP wasn't able to handle this but this issues are long gone and hybrid TWRP is outdated...

Sent from my Nexus 4 using XDA Labs

Wiped it!
TWRP ver 3.2.1.0
GApps : arm 64 8.1 pico

 

[abhijiths362]

Can we enable treble support even if it is not supported by oems??

 

[chewbaccadoggie]

Just updated my op2 to lineage os 16.0 (pie). Haven't used it too much to say much but here are some stuffs I've been noticing.
1) I was running pixel experience ( 9.0 ) before but it seem to had some issue with a few games so I switched to this. The first time I installed this it got stuck in a boot loop I restored my phone back to PE ( I had a backup ) but that too got stuck in a boot loop too. I wiped data, cache and internal data too. And it worked. Now I re-flashed Lineage os and gapps and everything its working perfectly fine but at some points I'm getting pixel notifications which I did on Pixel experience rom ( " continue setting up your pixel " etc ). Any comments ?
2) Whenever I try changing my display to dark mode from display settings my settings crash.

That's all for now.
PS: I'm using TWRP recovery. And I'm more or less a noob to this and know only most of the stuff due to YouTube research.
Thanks for reading :fingers-crossed:

PPS: Which will be the best kernel to get most performance out of my device ? I'm using stock kernel for as far as I know because I've not yet done anything to kernel.

 

[wulfhunter17]

Oneplus 2 camera not working

Hi guys
I have an issue with my oneplus 2 camera.
I have tried reflashing completely. Reverted to stock. Unrooted, etc. Flashed different kind of roms but still to no avail. I've flashed different camera zips also. I even replaced the camera module. Nothing seems to work. Camera won't open just FCs.
OnePlus 2 on Liquid rom
Androi 9
Build number : PQ3A. 190801.002
Any help on this would be highly appreciated. Thank you.

P. S i have attached the crash log below also.


time: 1574178277877
msg: java.lang.IllegalArgumentException: No HDR+ compatible raw format supported.
stacktrace: java.lang.IllegalArgumentException: No HDR+ compatible raw format supported.
at com.google.googlex.gcam.hdrplus.MetadataConverter.getGcamRawFormat(PG:29)
at com.google.googlex.gcam.hdrplus.MetadataConverter.convertToGcamStaticMetadata(PG:160)
at dfa.b(PG:55)
at dfc.a(PG:18)
at dfn.get(PG:39)
at qdl.get(PG:9)
at dfs.run(PG:13)
at izb.run(Unknown Source:2)
at lqd.run(PG:3)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:458)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:301)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:764)
at loy.run(PG:6)

 

[iamsuperuser]

Battery issue

My OnePlus 2 battery dropped from 28% to 0% battery when screen was off for 15-20mins.

This happened first time for me.

Is there a problem with my OnePlus 2 battery??

 

[Mricecool]

Hello Brothers,

I have a Full Stock Oxygen Os Oneplus 2. While i was Using the Phone and it was on Charge the Phone Hanged, Rebooted into BootLoop at the Oneplus Screen, But Sometimes after 10-15 or if the Phone was Left off for a while maybe after 2-3 Bootlooops the Phone Starts Loading the ROM but the moment the Login Screen appears the Phone Becomes Unresponsive and again starts the BootLoop....While in Bootloop i cannot Enter the Stock Recovery But when the Phone is in the Ability to Boot Rom Status the Recovery will Load on the Pressing of Key Combinations...Please Guide as how to Backup of Data or Can i Flash Just the Boot Partiton with Stock Boot from Fastboot as Fastboot is Working...Thanks in advance as i dont want to Loose my Data and App Data

 

[sidaparakevin]

Hello Brothers,

I have a Full Stock Oxygen Os Oneplus 2. While i was Using the Phone and it was on Charge the Phone Hanged, Rebooted into BootLoop at the Oneplus Screen, But Sometimes after 10-15 or if the Phone was Left off for a while maybe after 2-3 Bootlooops the Phone Starts Loading the ROM but the moment the Login Screen appears the Phone Becomes Unresponsive and again starts the BootLoop....While in Bootloop i cannot Enter the Stock Recovery But when the Phone is in the Ability to Boot Rom Status the Recovery will Load on the Pressing of Key Combinations...Please Guide as how to Backup of Data or Can i Flash Just the Boot Partiton with Stock Boot from Fastboot as Fastboot is Working...Thanks in advance as i dont want to Loose my Data and App Data

Same problem here bro..
Can't find any solution..

Can someone help plzz

 

[coen4d]

edit: Never mind my following question, what I did to fix it is install the correct ROM recovery file.

Hi I am a first time noob, I just "unlocked" my phone, and now have root privilege, I have TWRP installed, however I can't seem to install a new ROM correctly.
I am trying to install this ROM from the XDA original development forum: ROM OFFICIAL LineageOS 17.1 for Oneplus2 | Android 10
And I use open_gapps-arm64-10.0-pico as gapps.
The installation is successful, however my phone does not seem able to boot into the the OS.
Restoration works fine, and I can use my old, oxygen install, so no major problem.
But what am I doing wrong?

---------- Post added at 11:28 AM ---------- Previous post was at 11:13 AM ----------

Same problem here bro..
Can't find any solution..

Can someone help plzz

I had the same kind of issue, I booted into recovery, (hold volume down and power button) I then reinstalled the original OS with files from the OnePlus website.
And flashed the original boot loader.
I think it's because if a mismatch between OS and the bootloader, but I am noob myself, so take it with a grain of salt.

 

[BringBackJerseyShowah]

Really hoping this is the correct thread

I have a OP2 running LineageOS 17.1, latest stable release. Works great, love it. But ~August it developed a small quirky problem -- my apps that backup to the cloud when on wifi seem to think it's still only connected to the cell network, and won't backup. This is even when in the wifi connection's settings I set it as an 'unmetered' connection.

The two apps are Google Photos & Nextcloud client. Because of both apps having the same issue, I am presuming that this is an Android problem.

Has anyone else had this? Perhaps any suggestions? Any help is greatly appreciated.