Develop Bugs

Downloading update..Waiting to download (for 4hrs by now)

Hi,
I just got my Nextbit Robin today after my Nexus 6 got broken screen. Super excited about the phone, I powered it up with sim card inside, added wifi and after there was a message about android system update which would be only downloadable via wifi.
Currently the situation is following, I've been on the Downloading update... screen for 4 hours. Status is Waiting to download. Wifi connection is excellent. It just simply doesn't start the download?!
I've been thinking other options as well, like flashing the nougat manually, but I'm not totally sure if its even possible because I cannot access the developer options to unlock oem + usb debugging.
Any advices? Totally lost with the case. I think it shouldn't take so long. I've tried to reboot the device, cache has been also cleared via recovery.
Any help greatly appreciated!

After you rebooted the device, what happened?

Nextbit_Khang said:
After you rebooted the device, what happened?
Click to expand...
Click to collapse
It still got stuck as before with same Waiting to download message.

I've just made the factory reset and it doesn't seems to make any change regarding the download :/

nikkis4v said:
I've just made the factory reset and it doesn't seems to make any change regarding the download :/
Click to expand...
Click to collapse
https://help.nextbit.com/hc/en-us/articles/218638257-How-to-flash-back-to-the-stock-Nextbit-OS
I'd Recommend using the 7.0 Fastboot method as it will bring you up to date :3
I'm pretty sure you can manually factory reset by entering fastboot mode and going to stock recovery.. Either that or take out your sim and disconnect wifi after a reset to ensure it doesn't connect to the download server.. Then once in the os enable oem unlocking and then use the stock image I mentioned above :3 Just my two cents.. Hope it helps

nikkis4v said:
Hi,
I just got my Nextbit Robin today after my Nexus 6 got broken screen. Super excited about the phone, I powered it up with sim card inside, added wifi and after there was a message about android system update which would be only downloadable via wifi.
Currently the situation is following, I've been on the Downloading update... screen for 4 hours. Status is Waiting to download. Wifi connection is excellent. It just simply doesn't start the download?!
I've been thinking other options as well, like flashing the nougat manually, but I'm not totally sure if its even possible because I cannot access the developer options to unlock oem + usb debugging.
Any advices? Totally lost with the case. I think it shouldn't take so long. I've tried to reboot the device, cache has been also cleared via recovery.
Any help greatly appreciated!
Click to expand...
Click to collapse
What you can do (this COULD work, im not sure if nextbit's setup app has this implemented though, it should if it's based on AOSP) tap in each corner in a clockwise pattern, starting with the top left. (top left, top right, bottom right, bottom left) this should skip setup, allowing you to A: download the update while in the OS or B allow oem unlocking to flash the update via fastboot.

I just got a nextbit robin and am experiencing this same issue. I've tried rebooting several times, but it just hangs at waiting to download.

Still shows downloading updates even after 12 hours......what to do???
---------- Post added at 08:19 AM ---------- Previous post was at 07:57 AM ----------
xBane_ said:
What you can do (this COULD work, im not sure if nextbit's setup app has this implemented though, it should if it's based on AOSP) tap in each corner in a clockwise pattern, starting with the top left. (top left, top right, bottom right, bottom left) this should skip setup, allowing you to A: download the update while in the OS or B allow oem unlocking to flash the update via fastboot.
Click to expand...
Click to collapse
Above tactic not working out....give me the solution pls.

i'm having same problem. Do you think the up date was nextbit update that is not being supported?

SAME Problem in 2018
I want to update my MI A2 LITE Android to PIE but
system update downloading ....... and After 3min it paused Without any error and Without any progress

Moto z problems

Phone - Moto Z play XT1635-02-DS
Android- 7.1.2
Installed TWRP 3.1.1.0
Viper addison 7.1.2
Here are my problem:
1. Flashed with supersu v2.79 and also v2.82, neither works. Phone still not rooted. When i tried toa access supersu app, it says "there is no su binary installed and supersu can't install it..."
2. Camera does open but it doesn't function, it stays dark. (I have custom gapps 7.1.x)
3. Proximity sensor does not seem to be working in other cases, but the phone goes dark as soon as i press dial or as soon as i pick a call and remains so untill the other party cuts the call. Otherwise i need to shut down the phone if i have to end the call from my phone.
4. When i shut down the phone, in order to reboot manually from recovery-reboot-bootloader. Otherwise it remains in twrp recovery.
Can anyone help please?

Have you tried flashing back to stock and seeing if that fixed these issues?

Pal Guite said:
Phone - Moto Z play XT1635-02-DS
Android- 7.1.2
Installed TWRP 3.1.1.0
Viper addison 7.1.2
Here are my problem:
1. Flashed with supersu v2.79 and also v2.82, neither works. Phone still not rooted. When i tried toa access supersu app, it says "there is no su binary installed and supersu can't install it..."
2. Camera does open but it doesn't function, it stays dark. (I have custom gapps 7.1.x)
3. Proximity sensor does not seem to be working in other cases, but the phone goes dark as soon as i press dial or as soon as i pick a call and remains so untill the other party cuts the call. Otherwise i need to shut down the phone if i have to end the call from my phone.
4. When i shut down the phone, in order to reboot manually from recovery-reboot-bootloader. Otherwise it remains in twrp recovery.
Can anyone help please?
Click to expand...
Click to collapse
This is not really a problem with the phone per se but the rom you chose to flash. The reboot issue can be checked by setting a command at bootloader using "fastboot oem fb_mode_clear".

gman88667733 said:
Have you tried flashing back to stock and seeing if that fixed these issues?
Click to expand...
Click to collapse
Thanks. But i don't have the stock rom. I didn't intend to use a custom rom. I tried to root it to recover some deleted photos and the moron that i am, i didn't back up the stock firmwares and while tweaking around in the recovery i somehow deleted the stock rom. This is my 1st time...

DroneDoom said:
This is not really a problem with the phone per se but the rom you chose to flash. The reboot issue can be checked by setting a command at bootloader using "fastboot oem fb_mode_clear".
Click to expand...
Click to collapse
Thanks... I tried the above command (it does recognize my device) bur this is what i get :
{bootloader} slot-count: not found
{bootloader} slot-suffixes: not found.

Pal Guite said:
Thanks... I tried the above command (it does recognize my device) bur this is what i get :
{bootloader} slot-count: not found
{bootloader} slot-suffixes: not found.
Click to expand...
Click to collapse
Is there an option for the bootloader in developer settings in your rom similar to the screenshot I attached? Make sure it's enabled.

DroneDoom said:
Is there an option for the bootloader in developer settings in your rom similar to the screenshot I attached? Make sure it's enabled.
Click to expand...
Click to collapse
Thanks for your concern. Developer option is 'on' and Multiprocess webView renderers seperately - 'on'. But i get the same problem. (and how do you attach screenshots ? I don't see any option for attaching files) In anycase, like you said, i think the problem has more to do with the rom. Can you please suggest me another rom or if possible link from where i can download stock rom for my phone.

Pal Guite said:
Thanks for your concern. Developer option is 'on' and Multiprocess webView renderers seperately - 'on'. But i get the same problem. (and how do you attach screenshots ? I don't see any option for attaching files) In anycase, like you said, i think the problem has more to do with the rom. Can you please suggest me another rom or if possible link from where i can download stock rom for my phone.
Click to expand...
Click to collapse
If your on xda with your browser, it's the paperclip icon to attach files. If you are using a 3rd party app that wraps xda into it then I can't help you there. As for going back to stock, Motorola made things a little critical when they released Nougat. Depending on how far you were on keeping the device up to date through stock, flashing the available stock images (which aren't signed) could brick the device if you aren't careful. There use to be an account on androidfilehost that uploaded current stock packages but it seems they're all gone now. If you remember the build number of the device before you rooted, that will help in picking the right stock files. I've taken a break in keeping my device rooted so I haven't kept track of the resources used to help go back to stock but they're in the MZP guide threads.
EDIT: a word of caution when reverting to stock:
-Don't use flash tools that don't let you see/edit the fastboot commands
-Do not use commands that touch modem/radio or gpt partitions
Found an upload of the latest build release keep it around when you figure out what you need to flash. It's best to clear system, data, and cache before flashing. Also have a rom (and twrp) at hand to adb sideload in case stock doesn't boot.
https://androidfilehost.com/?a=show&w=files&flid=215703
This Android version 7.1.1
Security patch: Sept 2017
Build number: NPN26.118-22-2

Thanks alot... ?

Just received OTA - Oct 5th security patches

I thought this devices was long past End of Life for software support. Just had build NWD1.171016.002 push out. Nice surprise.

I just got the update as well

I got it too. Tought this was abortet

How different is it after the latest update?
I had to install custom ROM and kernel only because of the lags, but
If its responsiveness gets better, I will go back to STOCK.

Screenshots????

Yeap, me too....

Could the next person who receives this update please use ADB to pull the OTA URL and post it here?

Changelog??

eilex17 said:
Changelog??
Click to expand...
Click to collapse
They haven't posted one as far as I know. It seems to contain the October security updates at least, based on comments on Reddit. Unfortunately that means it probably doesn't contain fixes for the KRACK WPA2 vulnerability which was officially patched in the November security updates.

lentm said:
How different is it after the latest update?
I had to install custom ROM and kernel only because of the lags, but
If its responsiveness gets better, I will go back to STOCK.
Click to expand...
Click to collapse
Performance feels about the same. No noticeable difference from my perspective.

Well dang and woohoo.
I just got the OTA after I booted my phone to recovery and was doing a nand backup. :cyclops:
I was doing other things while the backup ran and got a vibration on my wrist and then saw the white circle meaning an update was applying.
Sorry, could not capture the OTA. Weird that it downloaded after it disconnected from my phone. I tried to manually enable wifi and force the update with no luck.
Took a l-o-o-o-o-o-o-o-g time to apply and a l-o-o-o-o-o-o-o-o-o-g to boot. Got quite hot (not comfortable on my wrist), I took it off while it was booting after the ota applied. Also battery dropped from ~90% to 65%
There are now three vibration patterns under settings > sound & notifications (normal / long / double). :good:
Nothing else new I can find.
Build number - NWD1 171016 022
Versions -
Android Weatr 2.5.0.172604017
Google Play 11.5.18 (530-172535583)
Android OS 7.1.1
Android Security patch October 5. 2017
I was on the April 5, 2017 security patch until now.

I couldn't finish the download, but was able to capture the OTA:
https://android.googleapis.com/pack.../5a312231c049a531cae069dfd8346ca6f24dc1b9.zip
I will download it and adb sideload it.

lentm said:
I couldn't finish the download, but was able to capture the OTA:
https://android.googleapis.com/pack.../5a312231c049a531cae069dfd8346ca6f24dc1b9.zip
I will download it and adb sideload it.
Click to expand...
Click to collapse
Thanks! Sideloading it worked fine.

blunden said:
Thanks! Sideloading it worked fine.
Click to expand...
Click to collapse
Sideload with twrp or adb ?

brmbjn said:
Sideload with twrp or adb ?
Click to expand...
Click to collapse
Sideload with adb

vicvon said:
Sideload with adb
Click to expand...
Click to collapse
My huawei watch cannot connect to my computer ? How to fix? Adb device unautorize

brmbjn said:
My huawei watch cannot connect to my computer ? How to fix? Adb device unautorize
Click to expand...
Click to collapse
Try revoke all authorization on developer options for this case;
however, you have to boot into recovery for sideloading anyways, so connect to pc and try adb there and see if it works.
On TWRP, you have to go to install -> adb sideload.

Also got the OTA last night. Wondered what was happening. Sat on sofa and felt my watch vibrate and looked to see it with the progress bar.
Mine also took ages and got lovely and warm on my wrist!
I was surprised it just went ahead and did the update without being on charge etc.

ethanhunt123 said:
Performance feels about the same. No noticeable difference from my perspective.
Click to expand...
Click to collapse
same here, and i got the update today.

lentm said:
Try revoke all authorization on developer options for this case;
however, you have to boot into recovery for sideloading anyways, so connect to pc and try adb there and see if it works.
On TWRP, you have to go to install -> adb sideload.
Click to expand...
Click to collapse
Do you have adb driver for huawei watch ?
Because my computer cannot connect with my watch.
Driver stopped code:10
Windows 10

17.0240. 2004.9 Out

Was checking system updates and found an update.

HermesHidayat said:
Was checking system updates and found an update.
Click to expand...
Click to collapse
Yup, was posted today on telegram group...
(WW)
FOTA (incremental update from 2004.60) ;
Rename to UL-ASUS_I001_1-ASUS-17.0240.2004.9-1.1.185-user.zip
https://fota2.asus.com/delta_packag...2004.60-17.0240.2004.9-06061254-fota-user.zip
Full rom zip ;
https://dlcdnets.asus.com/pub/ASUS/...S_I001_1-ASUS-17.0240.2004.9-1.1.185-user.zip
Raw rom ;
https://drive.google.com/file/d/1T0P8CDJLjPypRAS2HDpdUn8Z-M5tfzKc/view?usp=drivesdk
Stock boot img ;
stock2004.9
Root boot img ;
root2004.9
Place rom in root of storage and reboot. Once detected click to update. Reboot again to finish.
For those with root already and wishing to keep root, simply put the rom in root of storage, reboot and click to update when prompted. BUT, DON'T reboot yet when it finishes updating. Click 'later', go to magisk manager and choose 'install magisk'. When given the options for installing, select 'after OTA' (or words like that). Once magisk is installed again, select reboot. Root will be maintained. Saving the hassle of flashing the root img via fastboot.
-----------------------------------------
For those of you who are not yet rooted but would like to be using the boot img above, see below for guidance. NOTE: if something goes wrong, I am not responsible in any way!! Also, by unlocking bootloader (which is required for root), you will void your warranty.
Also note: you must update to latest 2004.9 rom from above links before starting this process. Should you wish to do this process another time with another update, you MUST ALWAYS match the root boot img for the same rom version you are using.
1. First you need to unlock the bootloader. Download and install the apk from link, then follow instructions. NOTE: doing this wipe the device. Do not power off the device or stop the process once started. I think the device will reboot a couple of times during the process, but ican't remember sorry... Just leave it to do its thing and once finished, proceed to step 2.
Get the bootloader unlock tool, which says in the description that it's compatible with android 10, from here. You'll find it under tools/utilities.
2. Download and install Minimal ADB and Fastboot app (windows). Install it on your PC/laptop to C drive
3. Download the root2004.9 boot img from above and move/save it to (C:\Program Files (x86)\Minimal ADB and Fastboot folder)
4. Switch the phone into fastboot mode (from device being in off/powered down, hold volume up then press and hold power button). Fastboot is the first screen you see with a scrollable menu giving some other options, don't select any options... just stay in that mode. Connect the phone to pc/laptop using the SIDE port of the phone. Navigate to C:\Program Files (x86)\Minimal ADB and Fastboot folder and double click the cmd-here.exe, this will open a cmd window.
5. (optional, but recommended) Once your phone is connected in fastboot mode and you have your cmd window open, type 'fastboot devices' in the cmd window. If your device is recognised then a key/serial will be displayed. Providing this is shown, proceed to step 6.
6. Next you are going to flash the root boot img (which, if you followed the instructions, should be in the Minimal ADB folder). In the cmd window type 'fastboot flash boot magisk_patched2004.9.img'. Once completed without errors, your device will now have a rooted boot img flashed. Yey!!
7. Now you can go ahead and unplug your device and boot it up. I did this months ago when I first got the phone, so you'll have to forgive me.... I can't remember if magisk manager is installed during the above process or if you have to install it manually after. If, when you have booted to system, there is no 'magisk manager' in your app drawer, you'll need to install yourself from here scroll about half way down the page and you'll see the downloads section. Go for the latest stable (currently 7.5.1).
8. Download a root checker app from playstore to verify you have root and you're done. If you need to resort back to original boot img, download it from above and follow the same process, but instead type 'fastboot flash boot boot2004.9.img'.

reg66 said:
Yup, was posted today on telegram group...
(WW)
FOTA (incremental update from 2004.60) ;
Rename to UL-ASUS_I001_1-ASUS-17.0240.2004.9-1.1.185-user.zip
https://fota2.asus.com/delta_packag...2004.60-17.0240.2004.9-06061254-fota-user.zip
Full rom zip ;
https://dlcdnets.asus.com/pub/ASUS/...S_I001_1-ASUS-17.0240.2004.9-1.1.185-user.zip
Stock boot img ;
stock2004.9
Root boot img ;
root2004.9
Place rom in root of storage and reboot. Once detected click to update. Reboot again to finish.
For those with root already and wishing to keep root, simply put the rom in root of storage, reboot and click to update when prompted. BUT, DON'T reboot yet when it finishes updating. Click 'later', go to magisk manager and choose 'install magisk'. When given the options for installing, select 'after OTA' (or words like that). Once magisk is installed again, select reboot. Root will be maintained. Saving the hassle of flashing the root img via fastboot.
Click to expand...
Click to collapse
bro,im not saying youre disturbing or whatsoever,you should make a detailed thread.unlike me im kinda dumb,i dont understand this Root boot img and so on. and making your own thread will allow more people will see your thread as i doubt many people will come to this thread to read...

Can anyone check to confirm whether heating is still on an issue on the new version?

HermesHidayat said:
bro,im not saying youre disturbing or whatsoever,you should make a detailed thread.unlike me im kinda dumb,i dont understand this Root boot img and so on. and making your own thread will allow more people will see your thread as i doubt many people will come to this thread to read...
Click to expand...
Click to collapse
Nah, should be fine here. People will still see the update in your title and click to view content. And for those that want root who are not already rooted I'll add some instructions in a while or tomorrow about how to use the boot img's (on my phone right now, it's easier if I do it on pc). Links and details are only the second post on the page so people will still see the info they need. So yeah, if it's OK with you I'll just leave the content here rather than starting another thread with the same title
---------- Post added at 03:36 AM ---------- Previous post was at 03:35 AM ----------
TikiThePug said:
Can anyone check to confirm whether heating is still on an issue on the new version?
Click to expand...
Click to collapse
I'd like to shed some light on this for you but I'm not a heavy gamer (I assume that's when the device gets hot mainly) and have never had any heating issues with any of the builds

TikiThePug said:
Can anyone check to confirm whether heating is still on an issue on the new version?
Click to expand...
Click to collapse
i dont play games anymore on my phone but the only time it hit 74 degrees was when i left my phone in my car under the sun...
reg66 said:
Nah, should be fine here. People will still see the update in your title and click to view content. And for those that want root who are not already rooted I'll add some instructions in a while or tomorrow about how to use the boot img's (on my phone right now, it's easier if I do it on pc). Links and details are only the second post on the page so people will still see the info they need. So yeah, if it's OK with you I'll just leave the content here rather than starting another thread with the same title
Click to expand...
Click to collapse
of course its fine.i was worried people wouldnt be able to see it.

Issue with Android 10 update on tencent with WW fingerprint
@reg66 tried moving post 2 ROM into root of storage .bit the update is still failing . New update is detected and after reboot, while it initialising install it's failing at the very start
Hi I have a CN Rog2 on ww1910.64-0 and fingerprint on ww. Using Asus updater I am getting 2001.60 .but post reboot while installing it errors out in the very beginning. Any guidance would be much appreciated !

VeeJay1 said:
Hi I have a CN Rog2 on ww1910.64-0 and fingerprint on ww. Using Asus updater I am getting 2001.60 .but post reboot while installing it errors out in the very beginning. Any guidance would be much appreciated !
Click to expand...
Click to collapse
Hmm, you should be able to update from latest A9 (1910.64) to A10. I'm guessing that the updater app only downloads the small incremental updates. These will fail unless you update 1 by 1, going up one version each time.
If you wanna jump straight to latest update (currently this one) download the FULL rom zip from post 2 of this thread. Put that in root of storage and reboot. Should hopefully not fail now and you'll be on latest.

Issue with Android 10 update on tencent with WW fingerprint
@reg66 tried moving post 2 ROM into root of storage, but the update is still failing . New update is detected and after reboot, while it's initialising install it's failing at the very start
Hi I have a CN Rog2 on ww1910.64-0 and fingerprint on ww. Using Asus updater I am getting 2001.60 .but post reboot while installing it errors out in the very beginning. Any guidance would be much appreciated !

Yes, moved to 2004.9
Did the incremental update and now my tencent rog2 on ww2004.9. thanks for the pointers.They really helped.

reg66 said:
I'd like to shed some light on this for you but I'm not a heavy gamer (I assume that's when the device gets hot mainly) and have never had any heating issues with any of the builds
Click to expand...
Click to collapse
Thanks man. Basically I had issues on A10 heating up even while just browsing the web. I would open up Armory Crate > Console and the CPU temp would be around 40+ Celsius. So now I'm back on A9, which shows temps of 30 Celsius with normal use.

well, video recording while connected to usb mic still doesn't work with the asus camera app

VeeJay1 said:
Did the incremental update and now my tencent rog2 on ww2004.9. thanks for the pointers.They really helped.
Click to expand...
Click to collapse
So the incremental worked direct from 1910.64 to latest? Or you had to go through each incremental?
---------- Post added at 07:12 PM ---------- Previous post was at 07:10 PM ----------
TikiThePug said:
Thanks man. Basically I had issues on A10 heating up even while just browsing the web. I would open up Armory Crate > Console and the CPU temp would be around 40+ Celsius. So now I'm back on A9, which shows temps of 30 Celsius with normal use.
Click to expand...
Click to collapse
Man that sucks. I've had zero heating issues even with leaving X mode on permanently @120Hz

Had to do this with each incremental update!
reg66 said:
So the incremental worked direct from 1910.64 to latest? Or you had to go through each incremental?
---------- Post added at 07:12 PM ---------- Previous post was at 07:10 PM ----------
Man that sucks. I've had zero heating issues even with leaving X mode on permanently @120Hz
Click to expand...
Click to collapse

TikiThePug said:
Thanks man. Basically I had issues on A10 heating up even while just browsing the web. I would open up Armory Crate > Console and the CPU temp would be around 40+ Celsius. So now I'm back on A9, which shows temps of 30 Celsius with normal use.
Click to expand...
Click to collapse
I've also suffered from battery and performance issues in A10. A9 was just fabulous, A10 was a step back.
I'm also a heavy gamer and just updated so I'll be sure to let you know what's going on.
P.S I did manage to improve performance and some battery life by installing the only real custom kernel we have, but which is a great one - kirisakura + Naptime with doze on Google play services.

VeeJay1 said:
Had to do this with each incremental update!
Click to expand...
Click to collapse
Ahh ok, bummer!! At least it's sorted now

Hi all, I have problem with the last update, always that's stop at 9% with message error update

dracoolia said:
Hi all, I have problem with the last update, always that's stop at 9% with message error update
Click to expand...
Click to collapse
I had the same problem with the incremental update. Just use the full ROM linked in the op.

Thanks for the Rooted Image.

Hi just chasing the raw rom if anyone has it please!

General S1SC32.52-69-16 Update - Lock Screen issue - SOLVED

Guys, do not take OTA update April (375 MB), it has issue with the lock screen.
You will not able to go to homescreen once you put the phone locked (or screen off) , you need to forced reboot the phone to be able to go to homescreen.
I'm downgrading to earlier version
SOLVED, update the firmware (July Security update) and then Go HERE

I can the update and no problem for me. All works ok

mythras73 said:
I can the update and no problem for me. All works ok
Click to expand...
Click to collapse
something wrong with my phone? I flashed earlier firmware then took the ota update still got the same issue.

I can update and all iits o.k.

my lock screen issue

Had the issue on the lock screen too. Just had to go into custom features to turn off peek display and turn back on for it to work properly

Blade^ said:
Had the issue on the lock screen too. Just had to go into custom features to turn off peek display and turn back on for it to work properly
Click to expand...
Click to collapse
nice info.. I will try it

Blade^ said:
Had the issue on the lock screen too. Just had to go into custom features to turn off peek display and turn back on for it to work properly
Click to expand...
Click to collapse
just try it, and keeps doing the same issue.

Hi! I also have a lock screen issue, and now I can only downgrade

Blade^ said:
鎖屏也有這個問題。只需進入自定義功能即可關閉窺視顯示並重新打開以使其正常工作
Click to expand...
Click to collapse
這個方法沒用

zlebors said:
nice info.. I will try it
Click to expand...
Click to collapse
This method is useless
Blade^ said:
Had the issue on the lock screen too. Just had to go into custom features to turn off peek display and turn back on for it to work properly
Click to expand...
Click to collapse

I just flashed a XT2201-6 firmware to avoid the OTA updates from XT2201-2 firmware.
build number S1SF32.22-16-14-19, everything looks good.. still retcn btw.

zlebors said:
I just flashed a XT2201-6 firmware to avoid the OTA updates from XT2201-2 firmware.
build number S1SF32.22-16-14-19, everything looks good.. still retcn btw.
Click to expand...
Click to collapse
NFC use or not

Download the XT2201-6 firmware there
zlebors said:
I just flashed a XT2201-6 firmware to avoid the OTA updates from XT2201-2 firmware.
build number S1SF32.22-16-14-19, everything looks good.. still retcn btw.
Click to expand...
Click to collapse

KenHuang2022 said:
NFC use or not
Click to expand...
Click to collapse
NFC Working

KenHuang2022 said:
This method is useless
Click to expand...
Click to collapse
Weird it worked for me. But I also tried changing the peek display from weather display to just battery. Can try that too.

Had the same issue 1st reboot after update, had to reboot via long press power. But since then seems to be working ok.
BTW, it looks like "Google Play System Update" disappeared from Security menu, now i see only stock security update here.

A long press on the power button doesn't respond to any mechanism. You can only reboot by volume and power on mechanism.

Maybe the baseband is broken, because I have flashed dozens of times

zlebors said:
I just flashed a XT2201-6 firmware to avoid the OTA updates from XT2201-2 firmware.
build number S1SF32.22-16-14-19, everything looks good.. still retcn btw.
Click to expand...
Click to collapse
where do you download the firmware S1SF32.22-16-14-19?