Hi all,
I have flashed a pre-rooted 14.6.A.0.368 on my phone with Locked Bootloader, and that is the firmware version on my phone at the moment.
Sony is offering me an OTA update, but I do not want to lose root, so I downloaded FlashFire but the app does not automatically detect the OTA file. I have managed to track the file down to /sdcard/recovery/update_package but FlashFire does not recognise the file as an OTA package (presumably because it doesn't have a file extension). Adding a .zip extension to the file reveals that it is not a ZIP.
What options are available for me to upgrade to the latest official firmware and retain root? (Or lose and regain it?)
kha1rul said:
Hi all,
I have flashed a pre-rooted 14.6.A.0.368 on my phone with Locked Bootloader, and that is the firmware version on my phone at the moment.
Sony is offering me an OTA update, but I do not want to lose root, so I downloaded FlashFire but the app does not automatically detect the OTA file. I have managed to track the file down to /sdcard/recovery/update_package but FlashFire does not recognise the file as an OTA package (presumably because it doesn't have a file extension). Adding a .zip extension to the file reveals that it is not a ZIP.
What options are available for me to upgrade to the latest official firmware and retain root? (Or lose and regain it?)
Click to expand...
Click to collapse
Personally, I would try making a backup, and dirty flash a pre-rooted .236, (if you're trying to save data, if not, just wipe everything and flash 236) If that didn't work, use Titanium to backup, then flash 236, then restore.
levone1 said:
Personally, I would try making a backup, and dirty flash a pre-rooted .236, (if you're trying to save data, if not, just wipe everything and flash 236) If that didn't work, use Titanium to backup, then flash 236, then restore.
Click to expand...
Click to collapse
Lol, I only just realised how stupid my question was! Managed to easily find the 236 PRF here from the same dev @Mirhawk.
Thanks for the help!
Related
I bought a second hand Samsung Galaxy Tab S a few months ago and it has been working fine.
However, when I looked at version of Android then seems a bit old (5.0.2) and when I did a check for updates it said that it couldn't update because "The operating system on your device has been modified in an unauthorised way". When I checked then it seems that the device has been rooted.
A quick search suggested I should run SuperSU to remove the root. So, I had to download and install this, but, when I run it says "The SU binary needs to be updated. Continue?" - if I do then I get another message "If you have a custom recovery like TWRP or CWM that can be used to (try to) install the SU binary" and gives me a choice of Normal or TWRP/CWM. I am struggling to know how to proceed.
So, should it be possible to remove the root and still preserve all my data, apps, settings, etc?
If so, is SuperSu the way to go or are there other tools I should look at, such as Kingo Android Root?
Or, am I faced with rebuilding with a stock ROM?
Thanks
There is no update. 5.0.2 is the latest.
ashyx said:
There is no update. 5.0.2 is the latest.
Click to expand...
Click to collapse
OK, thanks for info.
However, I would still like to remove Root and would appreciate advice on this, please!
MysteryMan1 said:
OK, thanks for info.
However, I would still like to remove Root and would appreciate advice on this, please!
Click to expand...
Click to collapse
If your root manager is supersu then it has the option to unroot in it's settings.
Sent from my SM-T800 using XDA Premium HD app
3DSammy said:
If your root manager is supersu then it has the option to unroot in it's settings.
Sent from my SM-T800 using XDA Premium HD app
Click to expand...
Click to collapse
I've tried to fire up SuperSU, but, run into problems, as described in my initial post, and this is what I need to resolve.
Any ideas?
MysteryMan1 said:
... A quick search suggested I should run SuperSU to remove the root. So, I had to download and install this, but, when I run it says "The SU binary needs to be updated. Continue?" - if I do then I get another message "If you have a custom recovery like TWRP or CWM that can be used to (try to) install the SU binary" and gives me a choice of Normal or TWRP/CWM. I am struggling to know how to proceed.
...
Click to expand...
Click to collapse
I'm having a bit of trouble understanding the end goal. As stated Android v5.0.2 is the latest non-custom firmware available. As a previous owner has unlocked the bootloader and seems to have flashed a SuperSu version that modification is blocking any OTA update to v5.0.2. It is also clear your trying to avoid loosing user data.
Would it be acceptable to be rooted and use a different method to apply the latest Samsung stock firmware for your region? If the answer is yes install a TWRP recovery for your device model but you'll loose your warranty by tripping KNOX (you may already be in that state). Follow the instructions in the TabS TWRP thread.
Then finish the SuperSU install (where your stuck today). Then install Flashfire. With Flashfire and the downloaded latest Samsung firmware package you can flash the boot and system images to update your install then use ODIN to update the Bootloader image from that download firmware. You could also flash the recovery image but that would overwrite TWRP and in your case I don't see the point. Flashfire needs the whole Samsung firmware file to be available on the device itself unlike when using ODIN to flash the Bootloader image.
As I'm rooted but retained my warranty I use FlashFire and ODIN to update to the latest stock firmware and never loose user data. Unfortunately to root and not trip KNOX I did wipe my user data that first time so it does not seem to be an option for you.
Hope that gives you some ideas. In your current state it maybe as simple as completing the SuperSU install (assuming a custom recovery (TWRP/CM) is already installed) then using Flashfire and ODIN as described.
Good luck
3DSammy said:
I'm having a bit of trouble understanding the end goal. As stated Android v5.0.2 is the latest non-custom firmware available. As a previous owner has unlocked the bootloader and seems to have flashed a SuperSu version that modification is blocking any OTA update to v5.0.2. It is also clear your trying to avoid loosing user data.
Would it be acceptable to be rooted and use a different method to apply the latest Samsung stock firmware for your region? If the answer is yes install a TWRP recovery for your device model but you'll loose your warranty by tripping KNOX (you may already be in that state). Follow the instructions in the TabS TWRP thread.
Then finish the SuperSU install (where your stuck today). Then install Flashfire. With Flashfire and the downloaded latest Samsung firmware package you can flash the boot and system images to update your install then use ODIN to update the Bootloader image from that download firmware. You could also flash the recovery image but that would overwrite TWRP and in your case I don't see the point. Flashfire needs the whole Samsung firmware file to be available on the device itself unlike when using ODIN to flash the Bootloader image.
As I'm rooted but retained my warranty I use FlashFire and ODIN to update to the latest stock firmware and never loose user data. Unfortunately to root and not trip KNOX I did wipe my user data that first time so it does not seem to be an option for you.
Hope that gives you some ideas. In your current state it maybe as simple as completing the SuperSU install (assuming a custom recovery (TWRP/CM) is already installed) then using Flashfire and ODIN as described.
Good luck
Click to expand...
Click to collapse
Thank you for your very helpful and comprehensive reply. I can't profess to understanding all of it, but, I am sure I will get there eventually!
I shall follow your suggestion of trying to get get SuperSU installed first.
:good:
If you want to go back to stock just flash the latest firmware with odin.
my question is regarding updating rooted V20D EUR to V20G via TWRP (without losing root, data and twrp recovery)? Are there flashable zips, like for 20D?
http://forum.xda-developers.com/g4/development/stock-h815-20d-images-kdz-flashable-t3301366
I really try to avoid rerooting, backing up and restoring anything, I admit :angel:
i will try it. Wait my reply.
sure, no problem, patience is a virtue
That's interesting for me, too!
An error message says you are rooted so wont install. This then deletes the 500Mb update (and seems to be redownloading later for me; will have to disable ota somehow)
i know that OTA won't work, but I am asking for a flashable zip. There were flashable zips up to v20d:
http://downloads.codefi.re/autoprime/LG/LG_G4/H815/
Or does anybody know how to convert dlpkgfile to flashable zip? I heard it's an encrypted update.zip, but I have no idea how to decrypt or extract it. 7zip won't help.
it's called dirty flashing. There are rom with recent os like imperium or genisys.
Dirty flashing is not recommended, it will cause instability. You better wipe everything
Seems there is no way to update my unlocked LG G4 to V20G. So can anybody tell me how I can wipe everything and perform the update, please?
There is a Twrp flashable V20g zip,I've updated V20d like that
Here
http://forum.xda-developers.com/g4/development/stock-h815-20g-images-kdz-flashable-t3450503/page1
yes, now there is, but it did not exist at the time I started this thread Anyways, I managed to update with LG Bridge without losing data and then in just a few easy steps regain root and TWRP, so it's OK, but flashable zip would have been a better option...
I live in india. When I update my device via system update, 270 mb file is getting downloaded but while installing it loading TWRP recoveey mode and on rebooting os version is still in 3.2.1. My device is rooted. Is there any specific flashable zips for indian version available or please guide me if any other solution is available.Not able to find specific solution. I dont wont to loss datas for this small incremental update
you have to be unrooted and on stock recovery to flash an OTA.
you can also download signed firmwares from oneplus forums which can be flashed through twrp but i think you'll have to download the whole firmware.
What ^said, if you are rooted you can flash the whole firmware using TWRP, all you need to do is flash SuperSU afterwards.
However, i was rooted when I got the OTA for 3.2.4, it told me I was rooted and made me download the whole firmware, I flashed it in TWRP them SuperSU and I was golden.
k.s.deviate said:
What ^said, if you are rooted you can flash the whole firmware using TWRP, all you need to do is flash SuperSU afterwards.
However, i was rooted when I got the OTA for 3.2.4, it told me I was rooted and made me download the whole firmware, I flashed it in TWRP them SuperSU and I was golden.
Click to expand...
Click to collapse
Thanks for the reply deviate. Will there be any data loss(installed app, songs, videos etc). So that I will follow that method else i need to nandroid backup i guess
jaganmohans said:
Thanks for the reply deviate. Will there be any data loss(installed app, songs, videos etc). So that I will follow that method else i need to nandroid backup i guess
Click to expand...
Click to collapse
No data loss on my end. It treated the flash like an OTA, it booted itself into recovery(TWRP), flashed and rebooted.
I would like to get to the point where I'm able to OTAs instead of manually flashing factory images but I'm not passing safety net when I uninstall magisk and reinstall it when the update reaches step 2. I'm not sure what is causing the update to fail. I recently switched from system root via supersu (obviously wouldn't pass safety net) to systemless root with magisk. I'm running 8.1 feb. security update with the following apps installed: adaway, busybox, CF. Lumen, greenify, magisk manager, & titanium backup. (rootless substratum & andromeda as well).
I do not have TWRP installed, I only boot to it to flash magisk and kept TWRP systemless. The purpose for this post I guess is to try understand which of the installed apps listed may affect the /system files. I was under the impression that since i now root systemlessly I would be able to accept OTAs. What am I missing here?
As far as I know you cannot be rooted and/or have a custom recovery. You can have a unlocked bootloader but you have to be stock in order to receive OTAs.
I really don't get the problem. Just flash full ota file via TWRP and then flash again magisk and twrp again.
With TWRP, flashing full OTA files is a breeze... I think incremental otas can be done in the same way, but better to flash full ota files...
onesolo said:
I really don't get the problem. Just flash full ota file via TWRP and then flash again magisk and twrp again.
With TWRP, flashing full OTA files is a breeze... I think incremental otas can be done in the same way, but better to flash full ota files...
Click to expand...
Click to collapse
......... you can flash full OTAs from TWRP?? I knew I was missing something.
So download the full OTA to internal storage. flash in TWRP. then magisk and if i choose not to install TWRP (i usually only boot to it), I'm done?
onesolo said:
I really don't get the problem. Just flash full ota file via TWRP and then flash again magisk and twrp again.
With TWRP, flashing full OTA files is a breeze... I think incremental otas can be done in the same way, but better to flash full ota files...
Click to expand...
Click to collapse
Wait, doesn't flashing the full OTA get rid of TWRP?
Do you have instructions how to install full images without TWRP being uninstalled?
Also... How do you get ota to install if the original bootloader is replaced by twrp? I thought installing twrp permanently voids the possibility to install ota...!
How to root first time phone with latest update with magisk method?
I'm find this simple way without TWRP
Is this way good?
No need to install TWRP in this way and no need some other .zip files like "no verify opt encrypt"
or something like that is not necessary. Is that a good idea? What are these additional .zip files for?
I have some experience with root on older samsung phones that have been routed by installing TWRP and flashing .zip magisk pach.
Nothing more was needed.
In short,
This way from joutube goes like this:
First the OEM is unlocked, magiskmanager.apk is downloaded and installed apk. After that the AP file that we downloaded before of firmware is patched with magisk app and inserted into the downloads folder.
After that, we flash the patched AP file over the odin and that's it. Will this work for me on the latest firmware?
I found this way that involves installing TWRP and some zip file.
xxsen said:
How to root first time phone with latest update with magisk method?
I'm find this simple way without TWRP
Is this way good?
No need to install TWRP in this way and no need some other .zip files like "no verify opt encrypt"
or something like that is not necessary. Is that a good idea? What are these additional .zip files for?
I have some experience with root on older samsung phones that have been routed by installing TWRP and flashing .zip magisk pach.
Nothing more was needed.
In short,
This way from joutube goes like this:
First the OEM is unlocked, magiskmanager.apk is downloaded and installed apk. After that the AP file that we downloaded before of firmware is patched with magisk app and inserted into the downloads folder.
After that, we flash the patched AP file over the odin and that's it. Will this work for me on the latest firmware?
I found this way that involves installing TWRP and some zip file.
Click to expand...
Click to collapse
I have used the method on a Samsung Galaxy Xcover 4s with new firmware.
However I don't know if it will work with Samsung Galaxy S9 due to the need for "dm-verity and force encryption disabler".
Have you rooted?