Hey there,
in all my years using/modding android phones I was never this lost on finding the issue.
My Oneplus 5t was unlocked, had latest blue_spark TWRP 3.40 recovery and stock oos 10.0.0 with the blue spark kernel and magisk installed. I just upgraded to the 8t and wanted to revert my phone back to stock. So I made a nandroid backup in TWRP and used the unbrick tool to get the phone in the fastest way possible fully wiped back to stock.
(https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012 OOS 5.1.7).
Well after my phone was fully stock I was already kinda suspicious about it not finding any OTA updates and manually installed the latest oos 10.0.1 update. First it seemed like everything was working just fine but then I realised that the camera is not starting anymore and gives me the error "Error starting camera" ("Fehler beim Öffnen der Kamera). Since then I have tried everything possible for 2 days but I still am unable to fix the issue.
Everything I tried.
1. deleting camera app data/cache and phone cache in stock recovery
2.factory resetting the phone
3.Using the latest 9.0.11 unbrick tool from this thread https://forum.xda-developers.com/oneplus-5t/how-to/op5t-collection-unbrick-tools-t3898890
-with this my wifi was not working but the camera was working again
- and this also showed me (while using mobile data) that there is a ota update available (oos 10.0.1)
- after updating my wifi was working and the camera was not working
4.Using at least 7 or 8 different unbrick versions (still from this thread here https://forum.xda-developers.com/oneplus-5t/how-to/op5t-collection-unbrick-tools-t3898890)
- here I noticed that as soon as I had a android version below 9 it would not show me available ota updates and would not even let me manually update but camera and wifi was working
5. unlocking the bootloader, flashing twrp 3.40 and restoring my nandroid backup
- camera is not working
So as you guys can see I am really close on losing my mind with this phone and I would appreciate any help you can give me :fingers-crossed:
// looks like I need to send in my phone to Oneplus
//Oneplus "certified" service in poland was unable (my guess is they did not even bother) to find the issue and quoted a 300€ repair bill for changing the mainboard ^^
Related
New to the world of Custom ROMs. A week ago I installed CM 13 which took great courage on my part and wanted to share my experience, issues and discuss possible solutions.
My phone had the latest lollipop on it. And McCafee locked. The steps that worked for me where
1) Did a factory reset and bumped into mccafee.
2) Tried download mode but kill switch was enabled.
3) Rebooted the phone to face mccafee, tried 123465 pin which worked.
4) Disengaged McCafee but not before transferring ownership to my email.
5) Tried rooting didnt work with any method.
6) Rolled back to d software version stock lollipop.
7) Rooted with PurpleDrake
8) Replaced with CM recovery didnt work.
9) Replaced with TWRP and rebooted directly to recovery
10) Installed CM and gapps mini. Worked fine. Voila!
Issues:
1) No Custom recovery sticks, whenever I flash with a custom recovery like TWRP or Clockwork. I have to reboot into recovery immediately or the custom recovery is replaced by stock. It happens on every second reboot.
My concern is here if I get stuck into bootloop and dont have a custom recovery I might not have any other option than the stock ROM which does a full reset. How can make TWRP stick forever?
2) After installation of Custom ROM there have been random reboots, I suspect there is something here with phone app or voice. So far the reboots have been when I try to call using fb messenger, appear.in and phone app itself.
Is there a guide that tells me how to track this down?
Can I install a newer Nightly and hope this get fixed?
How can I retain my apps and data when installing a newer nightly? since all guides ask to wipe everything :S
I have a backup of system and data partitions, can I use that with other ROMs.
What ROMs have a better chance of fixing this issue?
Coudnt find Stock M for D850. Why arent those available?
Should an Official ROM be more reliable than CM for this?
3) Bad signal reception so far. It may be a generic g3 issue.
Can I hope that this issue be fixed with a different ROM or updates from Cynogen?
Someone said you may have to flash the radio partition. My question is where can I get a brief understanding of what partitions there are in android and which are risky. Which ones can be replaced, backedup and replaced back.
4) Whenever the phone reboots, it gets stuck into bootloop unless I remove the SIM card. Then I power off and install SIM Card and reboot and it boots fine.
I am already tracking CM changelog for something important. Cant post urls as of now :S
I had my OP5T rooted and was on OOS 4.7.5. Last night I tried to update to OOS Open Beta 2 by downloading the zip from the OnePlus website and flashed it with TWRP. Since then I am unable to connect to any WiFi at all.
I've tried to flash different versions of OOS and even different custom ROMs (LOS/AICP). Right now I'm on stock 4.7.2, with stock recovery and locked bootloader. Even then I cannot connect to WiFi. It's not my router, other devices can connect to it easily. I even tried to connect to a hotspot from another device. No luck.
So is there anything else that I can do? Like flashing some specific firmware? Or is it a hardware issue?! Any help is appreciated.
@jcespi2005 had the same problem, and solved it here https://forum.xda-developers.com/oneplus-5t/help/wifi-issues-rolling-to-stock-oos-t3730017/page3
Maybe he can give you more advice if that doesn't work.
Flash oos open beta 1 . .
Sent from my ONEPLUS A5010 using Tapatalk
Just to be clear, you were on 4.7.5 and flashed the OB2 and thats when you lost your wifi? That's the opposite of what most of us experience....we upgraded to the OB1 or 2 but lost it when we reverted back 4.7.X.
I got mine back finally by clean flashing 4.7.2 followed by a dirty flash of 4.7.6
I've been flashing 4.7.2/4.7.4/4.7.6/OB1/OB2 like a mad man! Nothing works. No combination of clean/dirty flash works. WiFi still busted.
Just an update : I got my phone back from the service center. They had to change the freaking motherboard! Everything work fine now (with Oreo).
Hi team
I recently purchased an ex Demo HTC One M9 as a cheap replacement to my broken Galaxy S7 Edge, as soon as I received it I decided to flash TWRP and a new ROM on it. I was able to unlock the bootloader via HTCDEV.com easily enough and I was able to flash TWRP onto it without issue but when it came to the ROM's I ran into many problems.
Any version of Android that is Nougat or lower would not boot, the phone would go straight to the white bootloader screen every time. Oreo and Pie ROMs were able to boot but I ran into separate issues with them, I could not make or receive phone calls as the whole phone would freeze and there was no audio in from the speaker. I was also unable to play any videos in Facebook, YouTube, Snapchat etc.
I tried every single ROM available here on XDA and ran into these issues. I stupidly also did not make a TWRP backup of my system so it was quite hard to revert back to what it came from factory, I managed to get a stock Marshmellow running thanks to a User here posting a TWRP backup so thanks.
Is anyone able to help me with upgrading to Nougat? I would really like to get the Viper ROM working if possible, is it a known issue getting stuck in the bootloader menu every time?
I've tried just updating through the OTA process in the menu but it says there is no update file available.
Cheers
Hi All,
I am having a strange problem with my OnePlus 5t.
I have used msm flashing tool to flash oxygen os (4.7.4) and after that if I perform an OTA update to 5.1.4 (treble) which creates a vendor partition, phone stands mis behaving (blink, freeze, screen flash like old CRT TV when it has no signal and millions of dots of different colour)
Everything works fine if I use the below link to download one by one all the full updates and perform an update via local storage. https://forum.xda-developers.com/on...s-5t-mirrors-official-oxygen-os-t3708099/amp/
don't know what is the real problem but I am flashing/reflashing all the things which I find in XDA including customer rom, different msm flash etc but problem comes back.
It has been almost 6 months since I am reflashing the stock oos using msm when ever the problem comes back.
I need some advanced help.
I think there is some problem when oos update creates vendor partition.
Hey all
I recived the miui 12.5 enchanced [ALIOTHEEAGlobal_V12.5.3.0.RKHEUXM] (2.9 GB & 466 MB) Update a few days ago via ota. My rom is stock - no root or custom Recovery. The download and installing process work fine, but then the Phone need to restart. While restarting the Phone stuck at poco Logo. Only with a few reboots (or leave it alone for a long time) the Phone comes alive again. Then there is the Info miui update failed after reboot. I also tried to Update manually the Full and increment Rom over the three dots menue. No Chance. Even if i install my current rom version [ALIOTHEEAGlobal_V12.5.3.0.RKHEUXM] again - the same problem
I searched the whole Internet and couldn't find someone with the same problem.
Please help.. Thank yo all!
FYI: I cannot do a full reset / wipe with data loss, because i have so much banking apps and accounts. I need a full day of restoring my current status and i don't have the time at the moment.
No one?
Hmm... I don't know if it possible with locked BL but try boot from B partitions? Are they for cases like this one, aren't they?
I dont know this option. How will this work?
I backed up my phone as good as possible und tried to flash with "XiaoMitTool V2" my currend rom and the 12.5.6.0 and it always endet in "miui sideload failed". WTF is here going wrong .. While sideloading it stops at 4.99% on phone screen.
Have you tried with 12.5.6 via stock recovery? (full rom ofc, not OTA). It doesn't erase your data.
I also tried ToolV2 with my F3 and no luck too.
isnt 12.5.6 eea enchanced? 12.5.3 is older update in eu
I tried to update through stock recovery and MIAssistant but no success. Like @crysus said, it stops to 4,99 on phone screen, no error but it boots to the old ROM. Maybe because is a stable beta version.
Mine updade went all good without hassles. I updated it via stock recovery but first I use 3 dots menu in system updater app just to show where update file is. (full recovery fw used, not just OTA).
The fastboot version of 12.5.6_EEA has been available for a few days now, it can be Flash with miflash.
Here the link:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com