Database Develop

Nexus Stuck in Setup Wizard - Locked BL - Update Method?

A friend gave me a phone, I'm guessing the phone is a brick, but never hurts to make a thread and ask
Background
Its running 6.0.1 31E. After the update, I can't get through the Setup Wizard. It gets to the Gmail login part and force closes. No big deal, figured I'd just reupdate it. NOPE! Bootloader being locked, I can't seem to flash ANY system images. No TWRP on device either
I was going to try to update it to the newest firmware from Google for 7.1.1, but I keep getting failures in CMD. This isn't my first nexus (as you can see in my description). I also tried down grading, same results
So during the setup wizard, I managed to find my way into the Settings app, to attempt a bypass.
1.) Open Keyboard, hold @ symbol to open Keyboard Settings
2.) Go to Text Corrections, then Personal Dictionary, English, and enter a new word
3.) Highlight and hit Share
4.) Hold your finger down on Drive to open it in Settings to disable it
5.) Open Gmail in Settings, Select Notifications, and then App Settings, then top right, Manage Accounts... this opens the Full Settings app
From here, i could normally enable dev settings and such, but it doesn't allow it.
This is where I'm stuck. I've tried several things, including the frp bypass (even though this isn't FRP locked, it just crashes at login), but to no avail
Any ideas on how to re-run this update? I do have the files for 5.0, 6.0.1 31E, another newer 6.0.1 and 7.1.1. I've tried manual flashing and everything

Download an Android 7.1.1 OTA image from Google and sideload it using the existing recovery. Since the OTA is a full system image, it should resolve your issue unless you have a hardware problem.

I tried that with other recent google released OTAs via recovery and always get a failure, but i'll try that again
update
tried via apply via adb update on recovery... indicates the footer is wrong and aborts. th download i used is directly from google. better link maybe?

UPDATE 2
Downloading and installing the newest 7.1.1 from google through recovery worked. thanks. I had tried that on older 6.0.1's that were newer than 31e but they didn't work

Want to Block OTA G4 h811 20 x

I am using custom custom "Imperium Rom". Even after I delete /cache/update.zip, the OTA downloads again. I cannot find the app to disable/freeze or how to clear the icon in the notification panel.d The update fails because the custom recovery, TWRP is installed. I believe that if the actual update will break Imperial Rom.
Any ideas?

king200 said:
I am using custom custom "Imperium Rom". Even after I delete /cache/update.zip, the OTA downloads again. I cannot find the app to disable/freeze or how to clear the icon in the notification panel.d The update fails because the custom recovery, TWRP is installed. I believe that if the actual update will break Imperial Rom.
Any ideas?
Click to expand...
Click to collapse
It's not a full block, but after trying to install it, it will fail (it will just boot into TWRP, just tell TWRP to reboot back to System). It'll give you a notification that there is an update. Go into the update page and you can "pause" the update. This disables the download and stops it from giving the notification until you resume it. I've had mine paused for a week so far without issues while I look into how to install this update. (It does have a new radio firmware, so it's worth at least that).

pizzaboy192 said:
It's not a full block, but after trying to install it, it will fail (it will just boot into TWRP, just tell TWRP to reboot back to System). It'll give you a notification that there is an update. Go into the update page and you can "pause" the update. This disables the download and stops it from giving the notification until you resume it. I've had mine paused for a week so far without issues while I look into how to install this update. (It does have a new radio firmware, so it's worth at least that).
Click to expand...
Click to collapse
I followed your information and paused the update. The phone is working well without problem so I don't need the update. I think there is a security update too.
I have a TWRP backup of stock with stock recovery. This would likely accept the update but I worry that restore of the Imperial Rom will cause problem.

Easy way is dial code 277634#*# then wifi test option then Ota setting disable so you won't get it if set to download over wifi hope this helps

How can I prevent T-Mobile OTA pie update and stay on 8.1?

I have a Galaxy note 9 running 8.1 and would like to stay there. My phone is the T-Mobile branded one. Unfortunately it seems that my phone has downloaded the OTA update to pie and is asking me to install it. I clicked "Later" but I'm afraid that won't last forever. How can I delete the downloaded data and also disable the update from happening in the future?
I am a complete novice when it comes to software stuff so things like "flashing" memory etc may be beyond my scope unless it's very simple. I do follow instruction well though
I understand that I am forgoing security updates and I'm ok with that. After finishing up with a Galaxy S7 that was painfully slow on its last update and having it eat battery, I'd like to stick with the original software. There are other things like the camera app, layout, etc. that I'd just rather stick to.
Aside from rooting the phone, is there any way to just kill the update program? How can I delete the downloaded update to free up memory? I read someplace that rebooting the phone would install the update - so do I need to factory data reset and start over? (I just got the phone so I'm ok doing that)

ucladave said:
I have a Galaxy note 9 running 8.1 and would like to stay there. My phone is the T-Mobile branded one. Unfortunately it seems that my phone has downloaded the OTA update to pie and is asking me to install it. I clicked "Later" but I'm afraid that won't last forever. How can I delete the downloaded data and also disable the update from happening in the future?
I am a complete novice when it comes to software stuff so things like "flashing" memory etc may be beyond my scope unless it's very simple. I do follow instruction well though
I understand that I am forgoing security updates and I'm ok with that. After finishing up with a Galaxy S7 that was painfully slow on its last update and having it eat battery, I'd like to stick with the original software. There are other things like the camera app, layout, etc. that I'd just rather stick to.
Aside from rooting the phone, is there any way to just kill the update program? How can I delete the downloaded update to free up memory? I read someplace that rebooting the phone would install the update - so do I need to factory data reset and start over? (I just got the phone so I'm ok doing that)
Click to expand...
Click to collapse
you may have a couple of options.
I have heard that if you reboot in to the bootloader mode and clear cache then it will get rid of the downloaded firmware update.
I'm not sure.
you can download package disabler pro and disable the update services. I went back to oreo after pie update was horrible.
in package disabler pro follow the directions to enable it
search in the app for "update"
I disabled
"Software update" (com.sec.android.soagent)
"Software update" (com.wssyncmldm)
"System updates" (com.samsung.sdm)
No more updates or notifications
Good luck

jd14771 said:
You can flash the unlocked 8.1 oreo ROM and it will remove the ability to receive updates all together. it will also remove all the bloatware from tmobile. You will have to flash this with odin. After downloading the .zip ROM, Unzip it and flash all 4 files.
You want the XAA download.
https://forum.xda-developers.com/ga...ck-960u-firmware-att-vzw-tmo-spr-usc-t3837086
Click to expand...
Click to collapse
You still need package disabler pro or some kind if service blocker.
I down graded to Oreo on two devices using XAA and I still got firmware update messages for pie. Once I set up the phone.
Blocking the services keeps the phone from checking and downloading the update.

ucladave said:
I have a Galaxy note 9 running 8.1 and would like to stay there. My phone is the T-Mobile branded one. Unfortunately it seems that my phone has downloaded the OTA update to pie and is asking me to install it. I clicked "Later" but I'm afraid that won't last forever. How can I delete the downloaded data and also disable the update from happening in the future?
I am a complete novice when it comes to software stuff so things like "flashing" memory etc may be beyond my scope unless it's very simple. I do follow instruction well though
I understand that I am forgoing security updates and I'm ok with that. After finishing up with a Galaxy S7 that was painfully slow on its last update and having it eat battery, I'd like to stick with the original software. There are other things like the camera app, layout, etc. that I'd just rather stick to.
Aside from rooting the phone, is there any way to just kill the update program? How can I delete the downloaded update to free up memory? I read someplace that rebooting the phone would install the update - so do I need to factory data reset and start over? (I just got the phone so I'm ok doing that)
Click to expand...
Click to collapse
Easiest thing to do is to flash a different version modem for your device. Just flash the previous version modem file with Odin and you'll be set. If you want ota again, just flash the modem for your device matching the software update your device has installed.
I was on Oreo running the Pie modem and never got the Pie ota alert.

Jammol said:
Easiest thing to do is to flash a different version modem for your device. Just flash the previous version modem file with Odin and you'll be set. If you want ota again, just flash the modem for your device matching the software update your device has installed.
I was on Oreo running the Pie modem and never got the Pie ota alert.
Click to expand...
Click to collapse
My phone has already downloaded the update and is prompting me to install it. If I flash or run a package disabler at this point will it be effective? How can I erase the update data so it isnt eating space? Do I need to factory reset the phone first to wipe all that out before I flash or run disabler?

ucladave said:
My phone has already downloaded the update and is prompting me to install it. If I flash or run a package disabler at this point will it be effective? How can I erase the update data so it isnt eating space? Do I need to factory reset the phone first to wipe all that out before I flash or run disabler?
Click to expand...
Click to collapse
You could try clearing cache like an earlier poster suggested.

Updating Pixel 4 To March 2020 OTA w/Magisk

I went to check for system updates today and my pixel initially started to download the latest patch and then after a couple of seconds went straight to telling me that there is no update available. Anyone else have this issue and/or successfully update to the March 2020 OTA via the process below?
Updating Phone Once Rooted:
- Check for device updates, when found:
- Tap uninstall in 'Magisk Manager'
- Tap restore images
- install OTA (do not reboot)
- Back to magisk, tap install > select install to inactive slot
- When magisk installed, press the reboot button in it. It'll force to the other slot AND you'll be updated AND rooted​
I assume I should be able to go under 'System' -> 'Advanced' and get the OTA under 'System Update'. I've already disabled 'Automatic system updates' under 'Developer Options'. Just making sure google is somehow not blocking the update on rooted devices and that the above steps are correct. Thank you in advance!

Found similar thing on reddit here.

It's very common for unlocked and rooted Pixel phones to not "find" or complete the monthly OTA updates. There must be some sort of check in the OTA process that fails on rooted phones.
You should get familiar with the "sideloading" process of manually flashing OTA images.
Here is a set of instructions that I wrote in my Pixel 3a rooting guide. The process is exactly the same for the Pixel 4 series.
Taking an OTA update should be as easy as the above instructions. However there is another option available to install an OTA update called sideloading. Sometimes the update doesn't appear on the phone in a timely manner and you may want to manually install the update. Other times the OTA update seems to fail for some reason. In the end, you may decide to sideload the OTA instead of trying get it via the update feature on the phone. Surprisingly, it's actually faster to install the update via sideloading than it will be to take the OTA normally. I'll walk through the sideloading steps.....
Optional Step 1 - Uninstall Magisk (so that it restores the stock boot.img). If you find yourself unable to boot into recovery, you will have to restore the stock boot.img. I've run into this issue on some Android 10 images, but not all.
Step 2 - Download to your computer the correct OTA image from here
Step 3 - Connect to your phone via ADB on your computer. You should see the device listed if you type the command "adb devices".
Step 4 - Boot your phone into recovery (type the command "adb reboot recovery").
Step 5 - The phone will have a green android robot with a red sign over it's open access panel. Press the power button and then the volume up button while still holding down the power button.
Step 6 - Select "Apply update from ADB" using the volume buttons to highlight the choice and the power button to select it to enter the sideload mode.
Step 7 - Using your computer, type "adb sideload ota_file.zip" where ota_file.zip is the name of the OTA file you downloaded in step 2.
Step 8 - Once the update finishes, reboot the phone to complete the update process. (See note below about initial boot times).
Step 9 - To obtain root again, please use one of the two root methods listed above
Please note, the initial boot may take quite a while. I've seen the process take upwards of 20 minutes and longer. I think part of the reason it can take so long is that it optimizes the apps during this boot process. The more apps you have, the longer the process may take. When you take a regular OTA update, the phone will change to a screen where is specifically tells you it is optimizing the apps and counts up as the apps are optimized to give you status updates. When you use the the side-load method, it all happens with just the regular boot animation running and without any status updates. Because of this, it is easy to assume something has gone wrong with the boot process while in fact the phone is working through the process normally. If it isn't boot looping (showing the initial power screen before moving back to the boot animation), everything is fine and you just be patient and let the phone complete the process.
Click to expand...
Click to collapse

sic0048 said:
It's very common for unlocked and rooted Pixel phones to not "find" or complete the monthly OTA updates. There must be some sort of check in the OTA process that fails on rooted phones.
You should get familiar with the "sideloading" process of manually flashing OTA images.
Here is a set of instructions that I wrote in my Pixel 3a rooting guide. The process is exactly the same for the Pixel 4 series.
Click to expand...
Click to collapse
Thanks for the reply! I'm very used to sideloading/dirty flashing the updates, was hoping to use the Magisk method . Seems like google is getting smarter with their updates. I am guessing the current inability to see the OTA is due to the updates with google pay and google wanting to ensure banks it is safe.
I just finished sideloading March's OTA and patching the boot.img and everything seems to work, just a bit more effort than leveraging Magisk.

I had something funny happen. I was rooted in the January update. I just decided to check for updates. It always shows there's an update but always fails to download it. This time it downloaded and installed it. All the way to the March update. This unrooted me. I still had Magisk and all my modules but it was disabled.
I've tried the usual methods to reroot it. I downloaded the March update. Extracted the boot image. Patched it in Magisk. Put it on my PC and flashed it. The phone restarted and displayed the Google start up screen and a waiting bar like it was optimizing apps. But when that was done it went to a black screen and never left it. I put the phone down and came back to it over an hour later and it was still black. I had to reflash the stock OTA update.
Anyone know why that happened?

I experienced same exact thing. Looks like it saw the update at first then after a few seconds reverted to No updates available. About to try uninstalling Magisk, if no bueno, then gonna just sideload.

Spookymyo said:
I had something funny happen. I was rooted in the January update. I just decided to check for updates. It always shows there's an update but always fails to download it. This time it downloaded and installed it. All the way to the March update. This unrooted me. I still had Magisk and all my modules but it was disabled.
I've tried the usual methods to reroot it. I downloaded the March update. Extracted the boot image. Patched it in Magisk. Put it on my PC and flashed it. The phone restarted and displayed the Google start up screen and a waiting bar like it was optimizing apps. But when that was done it went to a black screen and never left it. I put the phone down and came back to it over an hour later and it was still black. I had to reflash the stock OTA update.
Anyone know why that happened?
Click to expand...
Click to collapse
Did you disable 'Automatic system updates' on the phone? That should still allow the download to occur just not the install. It seems like google got smarter with this update to detect rooted phones.

Gooch4130 said:
Did you disable 'Automatic system updates' on the phone? That should still allow the download to occur just not the install. It seems like google got smarter with this update to detect rooted phones.
Click to expand...
Click to collapse
Yes I disabled automatic updates. It didn't do it automatically, I clicked the check for update button. Normally when I do that it says there's a download available and then I know to check online for the flash file. This time it updated without stopping.

FAILED (remote: Failed to write to partition Not Found)
what i am doing wrong ????
---------- Post added at 12:21 PM ---------- Previous post was at 12:17 PM ----------
Boot loader is unlocked...
10.0.0 (QQ2A.200305.003, Mar 2020, All carriers except AT&T)
this version i did ota update
i am from germany.

okay, i found a way to root, but how is it with safety net fix ???
anyone an idea ???

Deleted

Spookymyo said:
I had something funny happen. I was rooted in the January update. I just decided to check for updates. It always shows there's an update but always fails to download it. This time it downloaded and installed it. All the way to the March update. This unrooted me. I still had Magisk and all my modules but it was disabled.
I've tried the usual methods to reroot it. I downloaded the March update. Extracted the boot image. Patched it in Magisk. Put it on my PC and flashed it. The phone restarted and displayed the Google start up screen and a waiting bar like it was optimizing apps. But when that was done it went to a black screen and never left it. I put the phone down and came back to it over an hour later and it was still black. I had to reflash the stock OTA update.
Anyone know why that happened?
Click to expand...
Click to collapse
It installed the OTA for me too, now I'm afraid to restart my phone.

mattcoz said:
It installed the OTA for me too, now I'm afraid to restart my phone.
Click to expand...
Click to collapse
I would flash Magisk again before you restart.
I still can't get my phone rooted. I'm not sure what's going on. I wonder if other people have been able to successfully root the March update.

I successfully rooted the March update, using the boot.img method.

Spookymyo said:
I would flash Magisk again before you restart.
I still can't get my phone rooted. I'm not sure what's going on. I wonder if other people have been able to successfully root the March update.
Click to expand...
Click to collapse
I rooted with boot.img method, as well

sruel3216 said:
I rooted with boot.img method, as well[/QUOTE
I ended up following this
https://www.youtube.com/watch?v=kZY8qiz2SZ0
Click to expand...
Click to collapse

I got it rooted. It ended up taking a factory reset. It must have been some file interfering with the process. Once I reset my phone the rooting process went without incident.

As I'm searching for a more Phone based update wy, I'm thinking about to use maybe the Implemented OTA Process, but download the OTA-File manually... But for that We must know,how the OTA process is working. Did someone know:
- Where the update stores the download fine (I found a OTA and a OTA_Packge directory in the /Data/ folder)
- is there maybe a setting or information which must be injected somewhere (maybe a txt file)
- after that the ota update could then maybe started by hand
Has someone informations on that? If maybe someone where the ota still works and stil has root could check the files and places?

Chris.C said:
sruel3216 said:
I rooted with boot.img method, as well[/QUOTE
I ended up following this
https://www.youtube.com/watch?v=kZY8qiz2SZ0
Click to expand...
Click to collapse
Worked like charm!! Thanks!! :good:
Click to expand...
Click to collapse

I unlocked the bootloader, sideloaded the August 2020 OTA and flashed the patched boot image. Kept bootlooping, then I restored to the original, booted in, installed Magisk Manager and then flashed the patched image again. Just leaving this here in case it helps someone.

Question MIUI Rollback 13.0.17.0.SKFEUXM to 13.0.16.0.SKFEUXM

Hello!
the latest MIUI update I've received, 13.0.17.0.SKFMIXM, is not owrking as good as the one I was using, namely 13.0.16.0.SKFMIXM.
I've found and downloaded the 3.41 GB and something full rom and the OTA update of 266.39 MB.
I've tried with each one the following procedure:
rename the file to update.zip
copy it into the root folder of the phone
tap various time on the miui 13 logo to get the "select update package menu"
...every time it says that can't verify the update package, try via usb.
I was so happy with the 10.0.16.0. what can I do? I fear that a factory restore and a subsequent update will bring it back to 13.0.16.0.
Thank you in advance for the help.

awambawamb said:
Hello!
the latest MIUI update I've received, 13.0.17.0.SKFMIXM, is not owrking as good as the one I was using, namely 13.0.16.0.SKFMIXM.
I've found and downloaded the 3.41 GB and something full rom and the OTA update of 266.39 MB.
I've tried with each one the following procedure:
rename the file to update.zip
copy it into the root folder of the phone
tap various time on the miui 13 logo to get the "select update package menu"
...every time it says that can't verify the update package, try via usb.
I was so happy with the 10.0.16.0. what can I do? I fear that a factory restore and a subsequent update will bring it back to 13.0.16.0.
Thank you in advance for the help.
Click to expand...
Click to collapse
Google fastboot flash with PC or recovery flash via custom Recovery.
For both the bootloader has to be unlocked. In my opinion there's no other way to rollback .

I've downloaded the right version (EEA) and now I'm getting the message "impossible to downgrade".
ahahah. this is so stupid.
I had a nice, fully working phone, now it's back to garbage and I can't rollback. starting from the battery usage - now I can't activate the battery saver and the drop down menu is transparent and unreadable unless i turn off the battery saver.
My only option is to navigate a jungle of fake infos and obscure downloads to flash the phone - since there is no clear guide. I might be wrong; if there is a CLEAR guide on how to properly flash a Redmi Note 10 Pro, where can I find it?
Cheers.
A

awambawamb said:
....
My only option is to navigate a jungle of fake infos and obscure downloads to flash the phone - since there is no clear guide......
Click to expand...
Click to collapse
I advise to search for the right information on XDA and the downloads from Xiaomi servers.

awambawamb said:
I've downloaded the right version (EEA) and now I'm getting the message "impossible to downgrade".
ahahah. this is so stupid.
I had a nice, fully working phone, now it's back to garbage and I can't rollback. starting from the battery usage - now I can't activate the battery saver and the drop down menu is transparent and unreadable unless i turn off the battery saver.
My only option is to navigate a jungle of fake infos and obscure downloads to flash the phone - since there is no clear guide. I might be wrong; if there is a CLEAR guide on how to properly flash a Redmi Note 10 Pro, where can I find it?
Cheers.
A
Click to expand...
Click to collapse
Downgrading using the rename trick is not possible now due to OTA validation. But still, downgrading is still possible as long as the bootloader is unlocked (you can re-lock bootloader afterwards btw so no worry about banking apps).
Procedure might be something similar to this:
1. Unlock bootloader
2. Flash any latest OSS ROM (this is just to remove MIUI)
3. Use MiFlash and fastboot method to install old versions (re-lock if you want)
Alternatively, after No.2 you can directly install the old update through custom recovery and just keep bootloader unlocked. Though this means that you'll have to deal with hiding rooting and passing safetynet.
PS: Just to add, Anti-Rollback is not yet enabled for sweet so no worries with getting bricked while downgrading. Just be careful and flash appropriately.

Thanks for the kind reply, @BigChungus321 . Glad to hear that I can still unlock and lock the bootloader! at least for those 6 months of warranty.
Just one thing, in the step you suggested you said:
1. Unlock bootloader​2. Flash any latest OSS ROM (this is just to remove MIUI)​3. Use MiFlash and fastboot method to install old versions (re-lock if you want)​Alternatively, after No.2 you can directly install the old update through custom recovery and just keep bootloader unlocked. Though this means that you'll have to deal with hiding rooting and passing safetynet.​​Directly installing the old update ( MIUI 13.0.16.0.SKFEUXM ) isn't the same as using MiFlash and fastboot to install the old version, or I am missing a part here?
In this very moment I've made a backup of all the pictures and a list of all the apps installed, to help googling them again later, in preparation for asking the MIUI lords the permit to unlock my device.
Also, I've a friend who has the same phone but it has never been updated; based on my personal experience, if I'd like her to avoid the issues I've found in 13.0.17.0, would it be safe to tell her to manually update the phone with the "select update package menu"?

wow.
I was ready to unlock the phone, but I forgot to unlock the "Mi unlock" in the developer options. So I went there and seems that I cannot unlock: I keep receiving the message "connect to the netwrok and try again".
Am I missing some piece of information here?

awambawamb said:
Directly installing the old update ( MIUI 13.0.16.0.SKFEUXM ) isn't the same as using MiFlash and fastboot to install the old version, or I am missing a part here?
Click to expand...
Click to collapse
It is the same but I do encounter people who face anti-rollback error rejecting the downgrade if flashing from MIUI to MIUI. But going from OSS to MIUI, this arb check does not seem to occur.
awambawamb said:
In this very moment I've made a backup of all the pictures and a list of all the apps installed, to help googling them again later, in preparation for asking the MIUI lords the permit to unlock my device.
Also, I've a friend who has the same phone but it has never been updated; based on my personal experience, if I'd like her to avoid the issues I've found in 13.0.17.0, would it be safe to tell her to manually update the phone with the "select update package menu"?
Click to expand...
Click to collapse
No clue if that prevents the issue/bug you encounter. I usually just dirty flash the full rom update (not the incremental which is around ~200mb) in recovery and I don't seem to get issue this way, aside from recovery being replaced because dm-verity is getting activated again.
awambawamb said:
wow.
I was ready to unlock the phone, but I forgot to unlock the "Mi unlock" in the developer options. So I went there and seems that I cannot unlock: I keep receiving the message "connect to the netwrok and try again".
Am I missing some piece of information here?
Click to expand...
Click to collapse
I've seen many people who have this issue too. Again, no clue how to fix this. Maybe reboot, and just enable mobile data. Try changing sim card or switching sim card slots. Use other Mi Account for unlocking. I did see discussions about how using the same sim card and same Mi account can on a different device can cause this. I still have no clue how to fix this though so sorry. Might be a good idea to use a fresh sim card and mi account if you still encounter it.