Hi,
So I have Nokia 6.1 Plus with bootloader unlock. I have reverted to the stock image via OST many times in Oreo. After the Pie OTA (which Nokia rushed out, completely buggy) I decided I didn't want to keep it just yet and loaded Oreo back via OST.
But it seems after a clean Oreo OST the Google setup forces you to download the Pie OTA. It doesn't let you skip it, regardless if you pull out the SIMs and skip Wifi setup. It won't allow you to get into the phone without an online setup first (I assume this is Google Factory Reset Protection)
Does any one know how to bypass this?
For me it worked like you discribed:
Flash Oreo Rom via fastboot
Set up the phone with internet connection
Pause the update in settings (or block it on your firewall / router
Maybe root the phone and disable update app
Otherwise pause the update everytime you boot
Related
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.
Folks,
I'm facing an issue with my new Nokia 6.1 Smartphone. After unboxing and during the first start and intial setup it attempted to perform an update. However, this failed after downloading the content (via WIFI) with the error message "couldn't update phone - Installation problem". Afterwards I performed the initial setup offline as there was no possibilty to skip the update whilst connected to WIFI. This worked out and I was able to finish the intial setup to get access to the OS. I re-connected to WIFI and forced the update via settings -> system etc. Unfortunately, same result but a bit more information - Android 8.1 Oreo update (V2.13B) update size 804MB. Today I tried again and appearently a new OTA update has been released - Android 8.1 Oreo update (V2.22A) - slight hope that my issue is fixed with this release, but same isse again!
I tired also hard reset via recovery console. No luck....
I can't rule out a general issue with the phone but would like to explore other options before I return it.
Any suggestions or similar experiences?
Thanks in advance.
Rax18 said:
Folks,
I'm facing an issue with my new Nokia 6.1 Smartphone. After unboxing and during the first start and intial setup it attempted to perform an update. However, this failed after downloading the content (via WIFI) with the error message "couldn't update phone - Installation problem". Afterwards I performed the initial setup offline as there was no possibilty to skip the update whilst connected to WIFI. This worked out and I was able to finish the intial setup to get access to the OS. I re-connected to WIFI and forced the update via settings -> system etc. Unfortunately, same result but a bit more information - Android 8.1 Oreo update (V2.13B) update size 804MB. Today I tried again and appearently a new OTA update has been released - Android 8.1 Oreo update (V2.22A) - slight hope that my issue is fixed with this release, but same isse again!
I tired also hard reset via recovery console. No luck....
I can't rule out a general issue with the phone but would like to explore other options before I return it.
Any suggestions or similar experiences?
Thanks in advance.
Click to expand...
Click to collapse
I had the same issue while updating to the May Security Patch. All you need to do is connect your phone to the power source and then update using wifi only, keep your phone connected to the power source throughout the whole update process. No error will occur.
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,
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
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