Related
I have the AT&T version, but I did S-Off, converted to the Dev Edition (CID BS_US002) and now have the stock recovery back on because I'm trying to apply the OTA update which provides a patch to the GPS.
I've applied a previous OTA successfully (after I went back to a stock recovery, of course).
But this time, it fails partway through and shows the red triangle with exclamation point. I was able to boot the phone to Recovery and do a Vol+ & Power which enabled me to select a handful of different options, chose to do the option of installing an OTA .zip file. Anyways I browsed to the OTA file in internal phone storage, executed it and it stops and fails on the following message: "cimext9.odex has unexpected contents". I am stumped because Google couldn't help. But, something similar happened to another person and they had installed Adaway which must have changed system files. I did have AdblockPlus installed for a while but uninstalled it - so could ABP be the culprit, and now what are my options that would enable this OTA to get installed on my phone?
Thanks in advance. Still learning, appreciate the help this board has provided me so far.
I had the same issue with this update, even though previous ones had installed fine. I didn't have adaway installed and never found out what was causing my issue, in the end I flashed a clean .3 and done the update, which installed fine. Then I used Helium to install all my app data and rooted it after that. Had to setup all my root apps again but now running .4
It looks like I'm going to have to flash the stock ROM again because something apparently isn't stock anymore.
Can I do this but keep the apps installed, contacts, music/files, etc? Or does it go back to factory reset?
When I done it i had to install all my apps and stuff again but there might be a way of saving all your stuff, someone else might be able to help you with that, I haven't had an android device that long
oaklandm said:
I had the same issue with this update, even though previous ones had installed fine. I didn't have adaway installed and never found out what was causing my issue, in the end I flashed a clean .3 and done the update, which installed fine. Then I used Helium to install all my app data and rooted it after that. Had to setup all my root apps again but now running .4
Click to expand...
Click to collapse
Thanks. This will show my ignorance, but by flash the .3, do you mean get the .3 OTA and flash that in the stock recovery, or do you mean grab a .3 nandroid backup?
oaklandm said:
I had the same issue with this update, even though previous ones had installed fine. I didn't have adaway installed and never found out what was causing my issue, in the end I flashed a clean .3 and done the update, which installed fine. Then I used Helium to install all my app data and rooted it after that. Had to setup all my root apps again but now running .4
Click to expand...
Click to collapse
oaklandm said:
When I done it i had to install all my apps and stuff again but there might be a way of saving all your stuff, someone else might be able to help you with that, I haven't had an android device that long
Click to expand...
Click to collapse
Yeah I do not have THAT much, but I've done this a few times and have things just the way I like them. Oh well.
us3rnotfound said:
Thanks. This will show my ignorance, but by flash the .3, do you mean get the .3 OTA and flash that in the stock recovery, or do you mean grab a .3 nandroid backup?
Click to expand...
Click to collapse
I meant grab the nandroid backup, don't know if just a factory restore from the menu would do the job. I just thought that if I'm starting from scratch then I might as well flash .3 : )
I rooted using PurpleDrake...
That said my questions are:
If I restore the Stock boot.img & Stock recovery.img then perform a *full Unroot in SuperSU can I install the OTA without issue?
How about system files... Does PurpleDrake change them in any way that could cause the OTA to fail even after reverting back to stock boot, stock recovery and Un-rooting?
* not positive this step is necessary or will even work?
TIA to anyone with input!
AndroidUzer said:
I rooted using PurpleDrake...
That said my questions are:
If I restore the Stock boot.img & Stock recovery.img then perform a *full Unroot in SuperSU can I install the OTA without issue?
How about system files... Does PurpleDrake change them in any way that could cause the OTA to fail even after reverting back to stock boot, stock recovery and Un-rooting?
* not positive this step is necessary or will even work?
TIA to anyone with input!
Click to expand...
Click to collapse
Wondering same thing. How to get update, the reroot without having to do a full return to stock first.
Try it and let us know. As long as you don't have twrp installed you won't bootloop. If it does get hung up at all just battery pull and boot normally. At worst it won't take and you'll stay on c.
It worked!
Swizzle82 said:
Try it and let us know. As long as you don't have twrp installed you won't bootloop. If it does get hung up at all just battery pull and boot normally. At worst it won't take and you'll stay on c.
Click to expand...
Click to collapse
Here's the steps that worked for me, your mileage may vary.
Made sure all factory apps were present and or defrosted.
Restored the factory recovery and factory boot image (thanks autoprime) with Flashify.
Then I restored "b1847cae892006ffa11c6822a408fe8528142a54.D85110c_00-D85110m_00_update.zip" to the Cache folder.
Re-Enabled OTA using dialer code for hidden menu.
Opened Settings > About phone > Update Center > System updates and was met with the Android System Update screen showing the update "Downloaded and verified 154.6MB", hit the "Restart & install" button and it rebooted to factory recovery installed the update without issue.
No data was lost, No reflashing factory "c" image wiping all your data and having to upgrade from there.
I did lose root but it took <2 minutes to get it back.
I know I could have waited for a TWRP update zip but I ran out of patience.
AndroidUzer said:
Here's the steps that worked for me, your mileage may vary.
Made sure all factory apps were present and or defrosted.
Restored the factory recovery and factory boot image (thanks autoprime) with Flashify.
Then I restored "b1847cae892006ffa11c6822a408fe8528142a54.D85110c_00-D85110m_00_update.zip" to the Cache folder.
Re-Enabled OTA using dialer code for hidden menu.
Opened Settings > About phone > Update Center > System updates and was met with the Android System Update screen showing the update "Downloaded and verified 154.6MB", hit the "Restart & install" button and it rebooted to factory recovery installed the update without issue.
No data was lost, No reflashing factory "c" image wiping all your data and having to upgrade from there.
I did lose root but it took <2 minutes to get it back.
I know I could have waited for a TWRP update zip but I ran out of patience.
Click to expand...
Click to collapse
Hey, I've been searching through the forums trying to find the stock recovery/boot images for the last hour to no avail. Would it be possible for you to post links to where you found them? Thanks!
EDIT: Annnnnnnnnnd of course as soon as I ask, I find it in another thread I was reading http://forum.xda-developers.com/showpost.php?p=55359856&postcount=125
Where can i found the stock boot.image and stock recovery.img
bjg020683 said:
Where can i found the stock boot.image and stock recovery.img
Click to expand...
Click to collapse
Link in post just above yours...
Thanks
Hi, I think I follow all of your steps except confused about this one:
"Then I restored "b1847cae892006ffa11c6822a408fe8528142a54.D85110c_ 00-D85110m_00_update.zip" to the Cache folder."
Can someone explain what the above means? Thanks!
laoh said:
Hi, I think I follow all of your steps except confused about this one:
"Then I restored "b1847cae892006ffa11c6822a408fe8528142a54.D85110c_ 00-D85110m_00_update.zip" to the Cache folder."
Can someone explain what the above means? Thanks!
Click to expand...
Click to collapse
That is the actual "m" build OTA update zip file. Why not go straight to "r"?
The only reason I had to restore it was because I had deleted it in the 1st place.
Check your Cache folder for any update zip that may be waiting already.
I did it this way only because I was too impatient to wait for the update zips to be posted here.
But now they exist...
Here is a better way:
If you are already rooted go Here > http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667 and follow the TWRP instruction for flashing KK builds D85110 C, M, R Untouched_Stock_Restore.zip or even Lollipop D85120B
This will allow you to go straight to "r" skipping "m" all together.
If you are feeling brave and competent you could go straight to Lollipop...
Be sure to also flash SuperSu and TWRP after flashing the restore zip and before rebooting or you will lose root and your custom recovery.
Good luck!
AndroidUzer said:
That is the actual "m" build OTA update zip file. Why not go straight to "r"?
The only reason I had to restore it was because I had deleted it in the 1st place.
Check your Cache folder for any update zip that may be waiting already.
I did it this way only because I was too impatient to wait for the update zips to be posted here.
But now they exist...
Here is a better way:
If you are already rooted go Here > http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667 and follow the TWRP instruction for flashing KK builds D85110 C, M, R Untouched_Stock_Restore.zip or even Lollipop D85120B
This will allow you to go straight to "r" skipping "m" all together.
If you are feeling brave and competent you could go straight to Lollipop...
Be sure to also flash SuperSu and TWRP after flashing the restore zip and before rebooting or you will lose root and your custom recovery.
Good luck!
Click to expand...
Click to collapse
Thanks for the lengthy explanation. Can I verify if what I'm trying to do is same as what you've done? Here's my situation.
- I have the stock LG 4.4.2 KK rom for D851. Not stock AOSP or CM or any other "custom ROM".
- It is rooted and have TWRP
- The only thing I've really done to the rom is to debloat - used Titanium to freeze lots of apps that came with the LG rom. I have not deleted any since I've read before that if you delete them, it will make it a pain to upgrade to newer Android versions.
So I've learned the hard way trying to update my phone from 4.4.2 to 5.0.1 LG rom.
- I took the OTA and tried to install it. Big mistake. I ended up in a TWRP bootloop. Had me cringing thinking I just lost everything until I found this post http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508 and fixed it with LG_G3_Flash2FixStuckRecovery.zip (flashed it with TWRP). What a godsend it was. Got me out of bootloop and I didn't have to do factory reset or anything. All my apps and data are intact just the way it was before I began OTA.
- So now I'm back to where I started originally before attempting to OTA to Lollipop.
If I'm reading correctly, what I need to do are:
- Unfreeze all apps
- Restore stock recovery (recovery.img) and boot file (boot.img) - this essentially reverses root and custom recovery. Use Flashify to do so.
- Flash the stock LG Lollipop update (btw - the phone says that the new ROM is already downloaded and ready to go but there's nothing in the cache folder... is there somewhere else I should be looking?)
- Before I reboot - I should flash SuperSU and TWRP which restores root and custom recovery
- Reboot phone, cross fingers.
Somewhere in the middle, am I reading that you need to restore LG stock Kitkat rom first (which I already am on), then update to Lollipop? I'm reading that from this part "This will allow you to go straight to "r" skipping "m" all together. If you are feeling brave and competent you could go straight to Lollipop..."
I'm confused here...
One last thing - Once I'm upgradded to Lollipop, is there an easy way to freeze all the apps I had frozen before instead of going one by one? I have the paid Titanium version but I can't figure out if it has a batch/mass freeze feature.
Thanks!!
No, sorry but you are way off base. I think you either did not read my post carefully or you totally misunderstood what I was trying to say.
You don't have to do the steps I did, they are not necessary with the files available at the linked post below.
Yes you can go straight to lollipop but for someone like yourself I would reccomend downloading and flashing KK build "r"
If you are already rooted go Here > http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667 and READ THE ENTIRE OP CAREFULLY then follow the TWRP Files/flashing guide for flashing KK build D85110R-Untouched_Stock_Restore.zip
*Be sure to also flash SuperSu and TWRP after flashing the restore zip and before rebooting or you will lose root and your custom recovery.
This will at least update you to the last build "r" of Kit Kat
Lollipop for the D851 still has some bugs to be worked out but you can flash it if you want.
You are on your own now...
Good luck!
AndroidUzer said:
No, sorry but you are way off base. I think you either did not read my post carefully or you totally misunderstood what I was trying to say.
You don't have to do the steps I did, they are not necessary with the files available at the linked post below.
Yes you can go straight to lollipop but for someone like yourself I would reccomend downloading and flashing KK build "r"
If you are already rooted go Here > http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667 and READ THE ENTIRE OP CAREFULLY then follow the TWRP Files/flashing guide for flashing KK build D85110R-Untouched_Stock_Restore.zip
*Be sure to also flash SuperSu and TWRP after flashing the restore zip and before rebooting or you will lose root and your custom recovery.
This will at least update you to the last build "r" of Kit Kat
Lollipop for the D851 still has some bugs to be worked out but you can flash it if you want.
You are on your own now...
Good luck!
Click to expand...
Click to collapse
I appreciate all of your advice. The thing is, I'm trying to upgrade to Lollipop... I'm already on Kitkat and not really interested in upgrading to a latter dot version of Kitkat.... It just seems like a difficult proposition to do OTA upgrade if you rooted and have non-stock recovery. Since I'm on tmobile d851 stock Kitkat (rooted with frozen apps), I should've never put put TWRP. I thought I might put custom ROM on it but never got around to it and since you pretty much lose wifi calling with non-Tmobile ROMs, I just never did... More of a pain now....
I have a Nexus 7 (2013) running Kit Kat (4.4.4) and recently got the the OTA update to 5.0.1, but haven't installed it yet. I rooted it using the WugFresh Nexus Root Toolkit sometime some the last OTA update.
So how do I update to Lollipop? Do I need to unroot with the toolkit first? Will I need to backup my apps first and restore after the update?
Also, for some unknown reason, I no longer have the OTA update although I was notified that it had been downloaded. Odd! Guess I'll have to manually download it and side load it.
Thanks in advance...
skallal said:
I have a Nexus 7 (2013) running Kit Kat (4.4.4) and recently got the the OTA update to 5.0.1, but haven't installed it yet. I rooted it using the WugFresh Nexus Root Toolkit sometime some the last OTA update.
So how do I update to Lollipop? Do I need to unroot with the toolkit first? Will I need to backup my apps first and restore after the update?
Also, for some unknown reason, I no longer have the OTA update although I was notified that it had been downloaded. Odd! Guess I'll have to manually download it and side load it.
Thanks in advance...
Click to expand...
Click to collapse
In order to run the stock OTA you need to put your system back to stock. That means stock recovery, remove ALL modifications to the system partition (root, ad blocks, etc...) then you can run it. If that sounds like too much work - just back up and flash the factory image then restore.
I was rooted with the Wugfresh toolkit. I downloaded the 5.0 (and later 5.0.1) factory image from Motorola and unpacked it. I edited the flash-all.bat batch file (right click, Edit -or- right click, Open With, select notepad/wordpad) and removed the -w flag from the end of the file. It's not the very end, but very close. Just delete the -w and any excess spaces and save the file. The -w flag is what tells it to do a wipe of all data, removing it will prevent that. Put your Nexus into bootloader mode and double click the batch file.
Once it finishes flashing, it will boot up and say "optimizing apps" or "Android is updating" or something like that. Mine took about 15 minutes. After that, run the Chainfire Auto Root (CFAR) script to get root access back, and you're back in business.
Note: flashing Factory Images and running CFAR require an unlocked bootloader. CFAR will unlock the bootloader AUTOMATICALLY as part of the script. This WILL RESULT IN A LOSS OF DATA. If you are already unlocked, you're fine, as long as you remove the -w flag from the batch file.
Also, you do not need to go from 4.4.4 to 5.0 to 5.0.1, you can jump straight from 4.4.4 to 5.0.1.
There is also this:
http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22c-t2960745
At least a few of us have used that with no issues. I was running stock rooted 4.4.4 with TWRP, so I updated my bootloader, rebooted into recovery, wiped cache and Dalvik (probably not necessary before flashing), flashed the ROM, wiped cache and Dalvik again, and rebooted, and it's working great with no loss of data.
Telyx said:
There is also this:
http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22c-t2960745
At least a few of us have used that with no issues. I was running stock rooted 4.4.4 with TWRP, so I updated my bootloader, rebooted into recovery, wiped cache and Dalvik (probably not necessary before flashing), flashed the ROM, wiped cache and Dalvik again, and rebooted, and it's working great with no loss of data.
Click to expand...
Click to collapse
^I am going to do this, after reading similar reports of success.
However, to OP I want to stress that it is important that you update your bootloader before flashing the ROM. The patch is attached to the linked post.
While I am definitely tech savvy, I am not that comfortable with the WugFresh toolkit. For example, I just updated it to v1.9.9 and connected my device. While I know I previously unlocked the boot loader and rooted my device, the toolkit itself does NOT tell me if my device is unlocked or rooted.
Is there a tutorial somewhere describing how to update to Lollipop with the WugFresh toolkit? Thanks to @fury683 for the comment about editing the batch file. But I don't know what that means with respect to the toolkit user interface, that is what buttons are clicked in what order. I need a step by step list of instructions before starting.
@OrBy, by flash the stock image, do you mean the 4.4.4 image or the new 5.0.1 image? And how do I flash the image? WugFresh toolkit?
I used the WugFresh toolkit a few months ago, but have forgotten the steps I took. Should have written it down. I'll try to stick with the WugFresh toolkit.
Thanks for all the comments
Factory images and Wugfresh are not used together. Wugfresh is a collection of things while factory images return the device to 100% factory stock out of the box. If you modify the batch file as detailed above, no user data/apps are removed, just the system, recovery, etc partitions.
Factory images are a one click method that has a very similar end result as Wugfresh does to return to stock. I would go with factory images as it is the easiest and most straight forward method. Run batch, confirm, wait about 1-2 minutes, done.
skallal said:
@OrBy, by flash the stock image, do you mean the 4.4.4 image or the new 5.0.1 image? And how do I flash the image? WugFresh toolkit?
Click to expand...
Click to collapse
Well if your hung up on running the OTA then the 4.4.4 but if I were you I would just flash the 5.0.1 and skip the who OTA.
I managed to update to 5.0.1 without wiping the device using WugFresh. I went to the WugFresh site, read the FAQ, and found how to update without wiping clean. Turns out there is an option to disable wipe without editing the batch file. I was able to do the while procedure leaving the device unlocked.
I did have an unexpected issue. I had to reinstall in the USB drivers on my PC before I could re-root it. WugFresh made this part easy too, though I'm surprised a reinstall was even required. Once that was done, USB connection was restored and I could complete the rooting process.
I always stress out whenever updating Android in any way. The rules are different with each device and OS version.
One change I've noticed I'd that my Nexus 7 brightness I'd dimmer and I have to turn to setting higher. Hope the update is worth the trouble.
Follow up: after all the work upgrading to 5.0.1, I decided I didn't like the new version. I did the upgrade without a clean wipe. But I did the downgrade with a clean wipe.
The WugFresh toolkit is quite capable utility. I couldn't imagine doing it the hard way with the adb command line interface. At least know how to recover and rebuild my system should the need ever occur in the future. And Titanium Backup is indispensable too.
I found Lollipop to be a battery hog. Perhaps I'll try it again when some of the issues are worked out. There is no compelling reason change from Kit Kat at this time, IMHO.
OrBy said:
In order to run the stock OTA you need to put your system back to stock. That means stock recovery, remove ALL modifications to the system partition (root, ad blocks, etc...) then you can run it. If that sounds like too much work - just back up and flash the factory image then restore.
Click to expand...
Click to collapse
This is NOT true. I upgraded while rooted and it went fine. Just beware of xposed and other tools that mess up with /system and thus the upgrade scripts.
While I was able to update from KK (4.4.4) to LP (5.0.1) without wiping the data, it didn't work out for me. The battery life was terrible. It drained at least twice as fast compared to before the update. I was trying to avoid the pain of a clean install. But in the end, it wasn't worth with it.
I ended up going back to KK, and then to LP again but with a clean install. When installing LP the second time, I wiped the data and let Google reinstall all of the apps. There were a small number of apps, that I later restored the data from Titanium Backup, for example games with previous scores.
This made a huge difference in battery life. Plus the look and feel of many apps changed to the new Material design.
I'm not entirely sure I like the look of LP. I'd prefer LP under the hood, but the look of KK. Oh well!
Bottom line: don't do OTA updates with a major new release.
Hi all, first of all...sorry if I did not provide enough information...I am first time doing this whole flashing thing on my own...
My phone's CID number: HTC_044
Version main: EMPTY <<< is this normal?
Version bootloader: 3.19.0.0000
Using stock ROM i suppose...didn't flash any other third party's ROM before
My phone was rooted for sometime and lately I want to upgrade my phone to Lollipop...I thought I need to unroot first and therefore I found solution online...everything went fine and I was able to upgrade to Lollipop using the official way (update through phone).
However, later on I was trying to root it back...tried to download SU from Google Play and it just can't install properly...I then thought have to re-do everything again (restore back to basic OS version).
Then this second time I do, I wiped the data, cache, and dalvik cache (I did not do this for the first attempt). Then things start to go haywire...my Android files are not going into the internal storage...instead...it is being installed in my external SD card.
I then tried numerous time flasing back to basic OS version (Kit Kat 4.4.2) and update to Lollipop again...still no luck...
Until yesterday I thought everything worked out fine...and I tried installing Facebook...it says cannot install...
Can anyone help me on this? I also not quite sure what went wrong...hope you guys can enlighten me...will try to provide as much information as possible.
jkidz91 said:
However, later on I was trying to root it back...tried to download SU from Google Play and it just can't install properly...I then thought have to re-do everything again (restore back to basic OS version).
Click to expand...
Click to collapse
That is not the proper way to root. Installing SU from the store does not root the phone. It just install the app, not the SU binary.
To root, unlock the bootloader, install TWRP and flash the proper version SuperSU zip in TWRP.
---------- Post added at 10:38 AM ---------- Previous post was at 10:36 AM ----------
jkidz91 said:
Then this second time I do, I wiped the data, cache, and dalvik cache (I did not do this for the first attempt). Then things start to go haywire...my Android files are not going into the internal storage...instead...it is being installed in my external SD card.
I then tried numerous time flasing back to basic OS version (Kit Kat 4.4.2) and update to Lollipop again...still no luck...
Until yesterday I thought everything worked out fine...and I tried installing Facebook...it says cannot install...
Click to expand...
Click to collapse
Its not clear to me what you did, but it might be best to RUU to full stock using the link I provided in the other thread you posted to.
redpoint73 said:
That is not the proper way to root. Installing SU from the store does not root the phone. It just install the app, not the SU binary.
To root, unlock the bootloader, install TWRP and flash the proper version SuperSU zip in TWRP.
---------- Post added at 10:38 AM ---------- Previous post was at 10:36 AM ----------
Its not clear to me what you did, but it might be best to RUU to full stock using the link I provided in the other thread you posted to.
Click to expand...
Click to collapse
Noted bro! You r really helpful!
My phone is 8.1 rooted stock from Boost. I couldnt update over air but using smart switch and its updating! Maybe its 9 be cool if it was 10 lol. Ill let you know how it goes. Ill want to root it again . Magisk 19.2 is used for 8.1 what Magisk is for 9 ?
pda:SK1
I didnt have enough room so deleted some stuff. Im trying again . The last one was SF2 this says SK1. Now phone is configuring software update environment. Iuse phone for internet so just gonna sit back and let it do its thing. About time for an update official ! oh its 2.25 or 2.5 gig u update so be sure you have room or youll have to start over like me. Ill post pics when running it.
It's still android 8.1. I had to keep reconnecting smart switch . It wouldn't load up had that android on blue screen . I flashed twrp 3.3.1.1 , and then it boot looped, wiped cache , dalvik, still boot loop . I factory reset it. So luckily I had older memory card attached as otg, and tried flashing magick 19.2. It worked again and loaded up . Oh for anyone doing this you may not have to factory reset. Oh and since it booted up , magisk should have my original boot.img . I wanted it before , if anyone can point me to where it's kept I'd like to make copy and store on computer. So I may do twrp backup after my apps restore .
Before when I updated it made standard backup after flashing magisk and my original boot.img was gone when I restored it.
So hopefully now I know backing up system image completely restores it , my boot image should be saved . If anyone else updates tell me if you see any new features . Gonna go look for some. Happy rooting and updating !
Tigerevo said:
It's still android 8.1. I had to keep reconnecting smart switch . It wouldn't load up had that android on blue screen . I flashed twrp 3.3.1.1 , and then it boot looped, wiped cache , dalvik, still boot loop . I factory reset it. So luckily I had older memory card attached as otg, and tried flashing magick 19.2. It worked again and loaded up . Oh for anyone doing this you may not have to factory reset. Oh and since it booted up , magisk should have my original boot.img . I wanted it before , if anyone can point me to where it's kept I'd like to make copy and store on computer. So I may do twrp backup after my apps restore .
Before when I updated it made standard backup after flashing magisk and my original boot.img was gone when I restored it.
So hopefully now I know backing up system image completely restores it , my boot image should be saved . If anyone else updates tell me if you see any new features . Gonna go look for some. Happy rooting and updating !
Click to expand...
Click to collapse
Tô restore your SYSTEm flash with Odin your official rom
---------- Post added at 08:32 PM ---------- Previous post was at 08:23 PM ----------
I always recommend installing the latest official version for example in the case of the j7 pro we have used the Android 9 version. I recommend that you update your phone to the latest version. if you want to root your device you must follow the tutorial here on the root forum on Android 9 you will need to access the settings menu of your phone in the original rom and in the settings menu select unlock by oem then restart the phone do a factory reset flash twrp and immediately enter recovery and flash magisk then flash dm-verity and force encryption disabler 6.1 zip.
---------- Post added at 08:33 PM ---------- Previous post was at 08:32 PM ----------
https://forum.xda-developers.com/s7-edge/development/root-galaxy-s7-g935f-android-8-x-9x-t4054583
Root method