My OTA is broken, Please help - Huawei Mate 20 X Questions & Answers

I downgraded my EVR-29 from 10.1 down to 9.0 using Hisuite. This was in order to try brute force until I realised it took something like 50,000+ years I forgot the exact number.
So instead I thought I'd go back to 10.1 but boom my OTA is broken and it says 9.0 is the latest official version. I remember even in 9.1 and 10 it showed I have updates pending. But when I went to 9.0, no more updates available.
I can't seem to use dload method because it always fails. Using Hisuite proxy method also either fails or says group version not match. Hisuite proxy method did allow me to get upto 9.1 but I'm just stuck there now.
Please help
Build version before issue started https://i.imgur.com/tx9z7eY.jpg
Build Version after issue started https://i.imgur.com/ZUokjUA.jpg

Related

How to stop OTA updates and upgrades?

I have, apparently, one of those sw3's that will not accept the MM OTA so that the watch will work after is successfully installs. I am having to reinstall the LCA43 ROM in order to get the watch to work. While I would like to have MM, I can't seem to find the right ROM to install and XC is no help in either the software repair or update. The issue is when MM is on the watch, it continually stops at the 4 dots or symbols and never goes any further. I am using Ubuntu to connect to the watch for repair.
Is there a way to stop the OTA updates while still being connected to the phone via BT? I was happy to get this watch going again, but was disappointed this morning when it tried to boot in MM without me installing it.
Edit: This may be resolved. I installed a different ROM yesterday, 5.1.1.2, and it did not automatically try to upgrade last night so I may be good to go.

CM13: Updating to newer Nightlies locks me out of my phone

For the last 2.5 weeks I have been unable to update to any of the newer Nightlies for Cyanogenmod 13 on my Asus Zenfone 2. After the update is finished my phone claims I am using the wrong password to try to access my phone. I am not using the wrong password, updating seems to change it for some reason. Because I am unable to access my phone I am forced to boot into TWRP and revert to the last build that was stable for me. So far I have only tried two newer builds, the most recent one as of this post (August 3rd) and another one last week (July 27th). Neither work, the build I currently run that works with my current lock screen password is July 17th.
Nightlies for my specific device.
I have done a bunch of forum and google searching and nobody else seems to have ever had a problem like this. I would try to report this as a bug to the CM team but bug reports aren't allowed for Nightlies.
Any help is greatly appreciated.
Edit: Fixed
I fixed the issue by disabling the lock screen, updating to the latest nightly, and re-enabling the lock screen.
Have you tried clean flash?

Stuck on Open Beta 12 Firmware?

Hi,
I am currently on LineageOS 14.1 on my OP3, I am on the March 9th build, and to do so I had to flash the Open Beta 12 Firmware + Modem. But now I am trying to go to either VertexOS or FreedomOS, but after flashing either rom, my phone is unable to connect to WiFi. It says that it is an Authentication Error and a message saying "Password may be incorrect" pops up on the bottom, even though it isnt. I have tried flashing 4.1.0 firmware before flashing VertexOS but that does not help either. But when i restore my TWRP backup to LineageOS, the wifi works normally. Is there anyway to fix this?

Android 10 Update/Upgrade a705mn/ds Variant

Hi,
Is there another way to flash the firmware of A70 without using ODIN. I've updated my A70 yesterday via OTA trough ANDROID 10. It Updated successfully but when the phone restarts the phone no longer charges and can't recognize charging. Battery Icon shows 0% and keeps rebooting by itself.
I've already try clearing the cache/ reset to factory via recovery. same issue.
Try to download official firmware from Samsung. Flash successfully via ODIN. Still Same Issue (Android 10)
Try to Downgrade Official Firmware (Android 9) flash trough ODIN And still The Same.
Any Help Will Do. Thanks
By the way my Phone is a A705mn/ds (XTC Firmware)
Solution Found.
I manage to recover the device. using the latest ODIN (version 3.13.1) downgrade to XTC-A705MNXXU5ATA3-20200211101340 (Last Android 9 Update for A70 (January 2020 Patch)). Booted up normally.
But the weird thing is when I try to FLASH the Android 10 Firmware using ODIN (A705MNXXU5BTC2_CL17976949_QB29690579_REV00) the problem happens again. Auto Reboot, Battery Not Recognize, Charging Port Not Charging. Can't Even Use it for a couple of minutes.
I think there is a problem with the Android 10 Update on a705mn/ds variant. tried and tested via OTA and Manual Upgrade ODIN Flash. =(
By the way in order for you guys to stop the Update Just go to
Settings > Software Update > Disable Auto-Download over WIFI
then go back to
Settings > Biometric and Security > Other Security Settings > Disable Security Policy Update
then go back to
Settings > About Phone > Software Info > Tap Build Number 7 times (For Developer Option) if not done yet
then go back to
Settings > Developer Option > Turn off Auto Update System
This should STOP the update process
Hope this helps!
P.S. If you have an a705mn/ds variant give some feedback did you successfully update your device on Android 10?
Hey. I have SM-A705MN and the Android 10 update is working well. The only issue so far is minor. Task Changer interferes with the ability to swipe down for notifications unless turned off/on (problem arises after reboot).
I did foolishly try to install TWRP and after the second failed attempt i could not restore firmware in (any version) Odin. Finally after messing with Heimdall and getting odd responses i flashed bl, restarted Odin and flashed all 4 parts.
After that i patched AP in Magisk. I then flashed all four files in Odin with HOME csc and it looped so i went to recovery and after a factory reset i have root with the button start method.
---------- Post added at 08:09 AM ---------- Previous post was at 08:01 AM ----------
I'm going to tweak the csc files now (after a run through the decoder). I'll post whatever tweaks i use that work if you plan on rooting.
it's always preferable to use the latest Odin , your is v3.13.1
here it is : Odin v3.14.1
https://dl2018.sammobile.com/Odin3-v3.14.1.zip
hyperkamote said:
Solution Found.
I manage to recover the device. using the latest ODIN (version 3.13.1) downgrade to XTC-A705MNXXU5ATA3-20200211101340 (Last Android 9 Update for A70 (January 2020 Patch)). Booted up normally.
But the weird thing is when I try to FLASH the Android 10 Firmware using ODIN (A705MNXXU5BTC2_CL17976949_QB29690579_REV00) the problem happens again. Auto Reboot, Battery Not Recognize, Charging Port Not Charging. Can't Even Use it for a couple of minutes.
I think there is a problem with the Android 10 Update on a705mn/ds variant. tried and tested via OTA and Manual Upgrade ODIN Flash. =(
By the way in order for you guys to stop the Update Just go to
Settings > Software Update > Disable Auto-Download over WIFI
then go back to
Settings > Biometric and Security > Other Security Settings > Disable Security Policy Update
then go back to
Settings > About Phone > Software Info > Tap Build Number 7 times (For Developer Option) if not done yet
then go back to
Settings > Developer Option > Turn off Auto Update System
This should STOP the update process
Hope this helps!
P.S. If you have an a705mn/ds variant give some feedback did you successfully update your device on Android 10?
Click to expand...
Click to collapse
Hello I'm currently experiencing random reboot on my device (SM-A705MN/DS). It started last February 27, 2021 when i download patch update for Android 10. Prior to this update I'm already on Android 10 and everything seems to work fine back then. However this last Android 10 update cause this strange behavior. The phone will freeze then goes off and the it will boot again. After reboot it will work for say 30secs to a minute then it will freeze again and goes off.. It goes to this process multiple times until it gets hot on the upper half portion of the phone. What i do is let it rest and cool for good 1 hour or more and then when i reboot it manually it will work fine for the rest of the day. After nearly 24hrs or up to 36hrs it will work well. Until it resets itself and do the multiple restart again. I experienced this on a daily basis now even after upgrading to Android 11.
Do you think downgrading to Android 9 will resolve this issue? I already visited Samsung Service Center and initially they thought it was already fixed. So i did not left the service center immediately and test the unit first. I see that my unit is still Android 10 and factory reseted. After quite some time it reboots randomly. That's when the Samsung service tech concluded that it's a malfunctioning circuit board. However i am not quite convinced since my phone works perfectly and the issue only manifested after that particular update and the proceeding ones.
Does downgrading to Android 9 and upgrading straight to Android 11 can prevent this issue. I hope you could help me. By the way Noypi here. I supposed Noypi ka din coz it's obvious base on your username. hehe

Oneplus 5t issues with hard reset

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 ^^

Categories

Resources