Does anybody know how to trigger the ota process if you have an update.zip on the device?
My device has modified bootloader, so I'm not eligible for OTA... but with Wanam Exposed you can fake Offical status, and it'll download the OTA, but fail to install.
If before it fails, you copy the update.zip from /data/fota/update.zip .. then you have a copy.
My issue now though is that the normal OTA process won't let me continue with the OTA dialogs... and if I try to flash the zip in stock recovery, it can't seem to open it.
Is there a way to trigger the Samsung OTA process, with root, and have it properly process and unencrypt the update.zip upon flashing?
Cheers!
which model do you have? Most of the models have firmwares available at Sammobile so you really dont need OTAs unless u have the at&t model.
Related
I have a D2G. I rooted it.
But it now wants to do a 2.4.3 update. of course the update fails when it reboots
So my question is, could i apply the update using the bootstrap. has anyone tried doing this, would it brick my phone if i tried.
jbroderick said:
I have a D2G. I rooted it.
But it now wants to do a 2.4.3 update. of course the update fails when it reboots
So my question is, could i apply the update using the bootstrap. has anyone tried doing this, would it brick my phone if i tried.
Click to expand...
Click to collapse
You probably could if you remember to wipe data and cache, and you should probably get the Team Black Hat app and download the SBF/driver/RSD Lite files just in case.
Edit: Oh, the update file. If it's failing to install, you should probably just try the full install. I'm not sure why it wouldn't go through unless you're on stock, in which case, you HAVE to use full install.
I think he is talking about the official Verizon update. Not FRM...
When you rooted did you stop or remove any of the Blur apps? That will cause the update to fail. All of the Blurr must be there for the update to work.
If you used Z4Root to root your device, try to unroot the device with zroot and then try the update again.
You may have to re-install Zroot after it is completed to re-root the phone. But I did the update before I rooted almost the day I got the phone so I had not really done enough to notice if it wipes the device and data. My guess would be no!
Since I did this from the stock rom I did not bother to look but if the file is a zip file then chances are likely you can run it from the clockwork recovery.
But best bet is to unroot and then try it again before you go that route.
I would however get RSDLite and the stock SBF to have handy in case you run into problems.
You cannot apply the OTA update (I assume you are talking about 2.4.330 Verizon official OTA update) from the custom recovery. It must be instaled via stock recovery. But due to the way update is made (patch based) it will fail if there are alternations (missing files) in any of the system areas. You must restore all changes you made in /system/app (assuming you froze/delete some stock apps), if you are rooted it is ok, update will not bother (extra files in system do not break the checksum - update only checks original files. But if there is even a single file missing (deleted/renamed) in system area, update will fail to install. If you can't figure it out (what is missing) and update keeps failing, simply flash full SBF to return to stock, apply the OTA update then reroot and freeze/remove all apps that you don't want in system area.
I have the GT-I9300 international phone, with the New Zealand-based stock ROM installed. I rooted this phone with ODIN straight out of the box (it came on 4.0.4) and the root went fine, CWM worked. However, when I was notified of an available OTA update, no matter how many times I try to install it, the device will reboot into CWM and say that the signature verification has failed.
I have tried to disable this check, but the device seems to "forget" that setting. I've also tried installing the OTA update through Kies, which just gives an "Unknown Error".
Is there any solution to this, to get the update installed?
I'm presuming here that the OTA update is simply an update and not a new firmware version entirely? The download was only 20MB.
Kies is your solution
Or downloading and flashing an updated firmware
OTA doesn't work on rooted phones...
At least it didn't on the ones I used and tried...
Sent from my GT-I9300 using xda premium
If your phone is just rooted then OTA will work fine, the issue is when you install a custom recovery.
the OTA will fail at the flashing stage because the custom recovery will not be able to flash the OTA image (or the image won't let it).
Options are to use Kies, or better yet, download the rom on your PC and learn to use ODIN which is super easy anyway... and essential if you want to learn the root side of your phone better
Latest Chainfire root supposed to allow OTA .
jje
I recently installed a custom recovery on my exynos s9+ on stock pie. I actually thought unlocking oem and installing a custom recovery + root would trip Knox and prevent me from getting any updates but it didn't. Was roaming on my phone today and somehow found myself in the phone update menu. I tapped on check for updates and low and behold I could download an update. My problem is now that I'm on a custom recovery how would any update i download even manage to install? And even if it does is there a possibility that it might cause troubles like re-enabling dm-verity lock and bricking my phone? I wanna know what might happen if I proceed to download and install that OTA update.
drickles said:
I recently installed a custom recovery on my exynos s9+ on stock pie. I actually thought unlocking oem and installing a custom recovery + root would trip Knox and prevent me from getting any updates but it didn't. Was roaming on my phone today and somehow found myself in the phone update menu. I tapped on check for updates and low and behold I could download an update. My problem is now that I'm on a custom recovery how would any update i download even manage to install? And even if it does is there a possibility that it might cause troubles like re-enabling dm-verity lock and bricking my phone? I wanna know what might happen if I proceed to download and install that OTA update.
Click to expand...
Click to collapse
Personally I would not do the OTA as it may not update properly (if even at all). Every phone I have rooted before this was one of the cautions usually posted... I would double check in what ever tutorial, thread, utility faq you used to make sure.
I would suggest you wait for an update to be made that is flashable with your custom recovery. If your custom recovery has the feature (like TWRP) make a backup of what you have installed, flash the update and if things don't work you can restore your backup.
I miss having that kind of backup/restore ability via custom recovery on my phone.. sure comes in handy when things go sideways
Nothing happens. According to my experience and contents in the OTA zip, twrp will simply just spit it out. No dm-verity re-lock or bricking too.
You can always download one of the custom systems which are regularly updated.
Example would be Soldier ROM.
I recommend find your new firmware and flash it. You will lose all of your file and root-recovery you can have them all back
I picked up a second hand Galaxy S8 over the summer with plans to root it and install a custom ROM. I haven't activated it yet, but I was using it on my home WiFi and was notified that it downloaded an OTA update and it would be installed on the next boot. Since then I haven't touched it because I know that some updates can complicate or nullify the ability to root or install a custom bootloader, ROM, etc. I've done some searches on how to prevent the install, but haven't found anything except for how to disable your phone from downloading it to begin with. Now that the update is downloaded to my phone, is there a way to halt it's installation before I move forward with activation and customization?
I think you can let the OTA install, this because an OTA only affects Android OS and not device's bootloader .
jwoegerbauer said:
I think you can let the OTA install, this because an OTA only affects Android OS and not device's bootloader .
Click to expand...
Click to collapse
Thanks, I've heard different in the past. That OTA updates can lock you out of being able to run certain bootloaders for multiboot and such.
bump for input from others
Downloaded one S8 ota zip and checked. According to install-recovery.sh the command and path to fota package is on cache.
So going into recovery and wiping cache should do it.
edit: then again it might write it back on boot... but does it install it right away? IDK. Factory reset?
Hi, my bootloader unlocked with twrp installed lgv30 keeps complaining about a system update, but each time i choose install it just reboots into twrp.
I presume the install process needs the stock recovery for something? I'm unsure how to proceed, and it will not even let me turn off the notifications!
Correct, OTA updates cannot be applied via TWRP and require stock recovery. Fact is, you don't want to apply the OTA, because it will break the OS anyway, so don't do that.
If you want the update, since these phones are old, chances are there is a TWRP version of the update already... and/or a KDZ. Either of those can be used as well. KDZ will wipe the phone, but TWRP can be "dirty flashed" over what you already have.
In order for anyone to help further, you'd have to tell us what you have to begin with.
As for disabling the notification, you can disable the updater app to stop this from popping up at all. This is detailed in many places as well.., and, again, requires us to know what you're running now.
Thanks for the info, mine is a Stock H930DS using the lastest stock Android 9 for Australia.
I'm not that fussed about the update itself, which I believe to be a minor security patch. Disabling the updater would be great.
I have the unlocked bootloader and TWRP installed, but not magisk, I imagine I could install that again via TWRP, but wanted to get back to as original as possible.