Update crash

[Mike ryan]

Android trying to update but stops at 32% reads error then phone freezes. Only message reads custom binary blocked by frp lock.
Phone now won't turn on. Help please

 

[lunatic59]

I assume you are using the app? Sometimes the database gets out of sync. Simply logging out and logging back in will fix it.

 

[MoodyBlues]

Only message reads custom binary blocked by frp lock.

So you're running a custom ROM? Updating Android with a custom ROM installed....I don't think so.

Plus it looks like you've tripped Android's FRP protection.

Please give us more details, such as the name of your device, what ROM you're using, which Android version it originally had, and how you're attempting to update Android.

 

[MrJavi]

Yes, custom binary is indicative of some form of root and/or busybox binaries. Generally, an OTA update will not be possible unless you first unroot your device (remove custom binaries). Much depends on which root method was used. Magisk is better suited for OTA updates but it requires a step by step procedure. Furthermore, you will also need your Google accout password inorder to get past Factory Reset Protection lock (FRP).

It's best to search your specific model of phone beforehand. For instance, I have a Sprint Note 4. The specific model is SM-N910P. With my device I use Odin on PC to flash official factory firmware instead of OTA's. Good luck



This link is just to familiarize yourself with general info.

https://www.thecustomdroid.com/install-ota-update-rooted-android-device-guide/

 

[MoodyBlues]

I assume you are using the app? Sometimes the database gets out of sync. Simply logging out and logging back in will fix it.

I'm clearly missing something that @ocnbrze and @MrJavi are not.

What app? What database?

The OP said: "Android trying to update but stops at 32% reads error then phone freezes. Only message reads custom binary blocked by frp lock.
Phone now won't turn on. Help please"

 

[MrJavi]

I'm clearly missing something that @ocnbrze and @MrJavi are not.

What app? What database?

The OP said: "Android trying to update but stops at 32% reads error then phone freezes. Only message reads custom binary blocked by frp lock.
Phone now won't turn on. Help please"

Not sure about the "app" but custom binary usually mean root and/or BusyBox applets (binaries) have been installed. I'm guessing thats why the OTA update stops at 35%. Without knowing the specific device or tge OS theres no way to know if it's a system or systemless root method. Just not enough info provided by the op.

PS: In fact, I'm assuming it was an OTA update but it may have been a flashed.

 

[MoodyBlues]

Not sure about the "app" but custom binary usually mean root and/or BusyBox applets (binaries) have been installed

Yes, I know--refer to my first reply in this thread.

I was specifically questioning @lunatic59's response, which you and @ocnbrze 'liked,' that said: "I assume you are using the app? Sometimes the database gets out of sync. Simply logging out and logging back in will fix it."

I want to know what app and database he's referring to. Since you liked it, I assumed you knew something I had missed!

 

[svim]

Android trying to update but stops at 32% reads error then phone freezes. Only message reads custom binary blocked by frp lock.
Phone now won't turn on. Help please

Allowing OTA updates is generally not recommended when you use a custom firmware. You should be using whatever update process is supported by the developer(s) of the custom ROM.
If your device won't boot up properly, and if it's just soft-bricked, you should try flashing your device with its appropriate stock ROM. A stock ROM should restore your device to working condition again, then you can root it and install whatever custom ROM you were using. (and be much more judicious about allowing manufacturer and carrier OTA updates). If your device is hard-bricked however that will be more of a problem, a trip to a local service shop might be required.