"/device jasmine_sprout" - no, it is not.@T1mb3 I'm suffering from this issue: https://gitlab.com/LineageOS/issues/android/-/issues/2514
Is this already included in the dumpling build?
Also I still have the issue that the camera roll doesn't show taken pictures for about one hour (they're in the DCIM folder though) I had since the unofficial build. Any ideas?
Why don't you just type password in twrp? Or click cancel at that point and reboot.I'm having a strange problem that I have never encountered before.
The only thing I did was reboot my phone to recovery using the advanced power menu. My intention was to take a backup in TWRP before updating lineage. I realized when TWRP loaded that I had forgotten to remove my screen lock, so I powered off the device so I could remove it. The problem is that my phone keeps booting back into TWRP. I can't do anything in TWRP because the data can't be decrypted due to the screen lock and I can't boot into Lineage because the phone goes straight to TWRP each time. I'm stuck.
I am able to boot into fastboot but I can't get any of my computers to see the device. I believe I disabled USB debugging at some point.
If anyone has any ideas that might help please let me know.
I tried both. This is why its such a strange issue for me. When I enter the password (its actually a numeric pin) it tells me "password failed, please try again!".Why don't you just type password in twrp? Or click cancel at that point and reboot.
I appreciate the suggestion.I had similar issue. I was able to fix by installing the lineageos recovery. I think afterwards i was able to boot back into the system again.
You might try this at your own risk if there are no other ideas.
It's strange that adb works fine but fastboot doesn't on the same machine. I'm assuming you have used fastboot before on the PC with the phone?I appreciate the suggestion.
The trouble is I am unsure how to flash it in my current situation. I can't use TWRP since it won't accept my screen lock pin and I can't use fastboot since none of my 3 computers are able to detect the device.
Out of curiosity I checked to see if it could be seen using adb instead of fastboot. While in TWRP at the password prompt my device is listed as an attached device there (see attached picture).
View attachment 5420325
I'm not familiar enough with adb to know if its possible to flash recovery images with it. All of the tutorials I remember following used fastboot for flashing. I'm doing some research now to see if this could potentially be an avenue to save my phone.
If you or anyone else reading this knows better than I do, I would appreciate some feedback.
That is correct, I have used fastboot successfully from this machine before. In regards to fastboot not seeing the device, I believe its because I disabled USB debugging at some point.It's strange that adb works fine but fastboot doesn't on the same machine. I'm assuming you have used fastboot before on the PC with the phone?
If adb devices gives you something, have you tried adb reboot bootloader command? (I don't know if it's bootloader or fastboot). TWRP reboot has option to reboot into bootloader mode, I don't know of you have tried that one?
If adb is there and if you don't care about data, maybe you can try adb sideload official OOS zip? If sideload works then it will replace OS and also recovery. You can factory reset from that recovery and get somewhere?
Yes the volume while recording sound is very low, some issues with mic while recordingAnyone else have issues with quiet voice messages (whatsapp, telegram)? When speaking into the ear speaker the sound is much louder. It seems the bottom mic is not working properly.
I have no problems with calls. I also cleaned it allready.
YES!!! You are my hero! That totally worked! I was able to get my device recognized in fastboot. I coupled that with @IXI Mo IXI suggestion of flashing lineage recovery and I was able to successfully boot back into lineage.ooh, ooh !!!
it may well be that windows has "fixed" the usb driver for you at some stage after your initial install on the oneplus, making it useless
have a look here :
reinstall the usb driver, as directed (more complex to get into advanced startup than quoted, but google for it)
my comment in that thread says it all:
the mystery of not getting it recognised in adb (but happily visible in debug mode) was doing my head in until i came across this thread
windoze tries so hard to save us from being free, that it is painful
even getting to the advanced startup screen is now more complicated than the posted intructions here, but thanks be to google for letting me get there in the end
a squillion thanks @Mbektic - you rock !
good luck; hope that helps
@T1mb3 I'm suffering from this issue: https://gitlab.com/LineageOS/issues/android/-/issues/2514
Is this already included in the dumpling build?
Also I still have the issue that the camera roll doesn't show taken pictures for about one hour (they're in the DCIM folder though) I had since the unofficial build. Any ideas?
I checked, same fix is no-op, (it was basically a false revert of a upstream commit, fix was reverting the reverted upstream revert).@T1mb3 This soft reboot bug has also been reported for Dumpling: https://gitlab.com/LineageOS/issues/android/-/issues/3287
For me it makes using 18.1 virtually impossible and I downgraded to a home build version of 16.0.
So I guess what @binarious is referring to by linking to the jasmine_sprout issue is mikeng's fix for that specific tree.
@T1mb3 Thanks for your efforts, very much appreciated! One more question though: Are you and Georg even monitoring the issue tracker over at GitHub? I'm just asking, cause none of the open issues for Dumpling are getting commented by or assigned to a dev. Is it the best option to always report here in the forum?I couldn't reproduce the issue myself, but I will look around if I'd be able to find something.
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/