Here’s how to fix ADB Error – “FAILED (remote: variable not found)” if you get this error while trying to update your Android smartphone, which may likely happen on newer phones like the Pixel 2, Pixel 2XL, Pixel 3, or Pixel 3XL
If your ODIN is failing to flash or stuck while flashing hidden.img while flashing stock firmware on your Samsung Android devices such as Samsung Galaxy S2, S3, S4, S5, S6, S6 Edge, or any other Samsung device, there is a SIMPLE solution.
When flashing stock firmware on Android devices like Nexus 6, 6P, Pixel, Pixel 2, or others using fastboot command, you may run into problems when running the flash-all.bat or using the command, “fastboot -w update image.zip”.
For those of you having trouble flashing stock firmwares on latest Oreo firmwares with Samsung Galaxy smartphones(most likely with newer Galaxy S8, S8 plus, Note 8, S9, and S9 Plus) and getting stuck at “sboot.bin.lz4”, this is most likely caused by using ODIN version older than v3.13.1. Samsung is using new lz4 compression on firmwares which means older ODIN are not able to decompress the files before flashing to your phone.
Are you trying to install Samsung stock firmware using ODIN and getting stuck at fota.zip?
This will happen on newer devices like Galaxy S7 Edge, Galaxy S7, Galaxy S6, etc…etc… The reason why it gets stuck is because you are using older version of ODIN.
Recently on my trip to Thailand, I was connected to the WiFi of my mother-in-law’s house in Thailand. Sometimes in random fashion when browsing the web on my Android smartphone, it would redirect me to OnClickAds.net then to a site telling me I have a virus on my Android. Of course, as someone who is genuinely into fixing stuff like this, I digged deeper and found a solution.
If you get stuck in bootloop after updating via OTA(Over-The-Air) on Android N or you just installed Android N but doesn’t boot, there’s a fix Google has provided.