Hi all,
I've been putting different ROMS on my i9000 for a while now.
I got a new phone and my wife wants to use my i9000 to read her work mail. It needs an app that somehow does not want to install on stock 2.3.6. giving the "There was a problem parsing the package" error. Reading on the internet I understand that this error might come from not allowing installing from unknown sources or that the android version is too old for the app. I have allowed installing from unknown sources so I'm guessing the 2.3.6 android version is too old for the app.
So here's my question, I think I know the answer but not 100% sure. Is it possible to install a newer custom android rom on the i9000 without rooting? Or installing the ROM and somehow unrooting?? I'd prefer SlimBean or SlimKat, as clean as possible...
Hope to hear some positive news from you guys.
remichi said:
Hi all,
I've been putting different ROMS on my i9000 for a while now.
I got a new phone and my wife wants to use my i9000 to read her work mail. It needs an app that somehow does not want to install on stock 2.3.6. giving the "There was a problem parsing the package" error. Reading on the internet I understand that this error might come from not allowing installing from unknown sources or that the android version is too old for the app. I have allowed installing from unknown sources so I'm guessing the 2.3.6 android version is too old for the app.
So here's my question, I think I know the answer but not 100% sure. Is it possible to install a newer custom android rom on the i9000 without rooting? Or installing the ROM and somehow unrooting?? I'd prefer SlimBean or SlimKat, as clean as possible...
Hope to hear some positive news from you guys.
Click to expand...
Click to collapse
System is too old for this .apk package. Root itself is just included as "su" binary, so unless ROM has it implemented, it will not be here (95% of ROMs have it). No point to avoid root if flashing custom ROM. However you can "unroot" by deleting a few files (/system/xbin/su and /system/app/Superuser.apk or /system/priv-app/Superuser.apk).
devloz said:
System is too old for this .apk package. Root itself is just included as "su" binary, so unless ROM has it implemented, it will not be here (95% of ROMs have it). No point to avoid root if flashing custom ROM. However you can "unroot" by deleting a few files (/system/xbin/su and /system/app/Superuser.apk or /system/priv-app/Superuser.apk).
Click to expand...
Click to collapse
Thanks Devloz. So if I flash SlimICS for example, I can delete the files you mentioned and it should not be rooted anymore? Will give it a try.
Related
Hi,
I plan to root a HTC Desire C only for sim unlocking it. So far I am pleased with the original firmware (ICS 4.0) - after disabling some apps the phone runs fast and smooth.
The question is: does rooting modify the original OS in such a way that instabilities may occur?
Thanks.
dr.pythagora said:
Hi,
I plan to root a HTC Desire C only for sim unlocking it. So far I am pleased with the original firmware (ICS 4.0) - after disabling some apps the phone runs fast and smooth.
The question is: does rooting modify the original OS in such a way that instabilities may occur?
Thanks.
Click to expand...
Click to collapse
Rooting itself doesn't modify anything besides installing an app called Superuser.
You deleting/disabling apps that were not meant to be disabled does.
dr.pythagora said:
Hi,
I plan to root a HTC Desire C only for sim unlocking it. So far I am pleased with the original firmware (ICS 4.0) - after disabling some apps the phone runs fast and smooth.
The question is: does rooting modify the original OS in such a way that instabilities may occur?
Thanks.
Click to expand...
Click to collapse
Please, read this for first before doing anything: http://forum.xda-developers.com/showthread.php?t=2323518
(Thanks to @aashay960 )
smoza said:
Please, read this for first before doing anything: http://forum.xda-developers.com/showthread.php?t=2323518
(Thanks to @aashay960 )
Click to expand...
Click to collapse
Thank you for the related link. Helpful.
As I like, for the moment, to stick to the original firmware (to me, it is the most stable among all avalable roms for HTC Desire C), I still have two more questions:
- will the rooting stop the handset from receiving official updates?
- assume I root the handset and install cwm recovery and backup the current rom.
if ever I like to restore this backup, I will need to flash a kernel boot.img.
can I extract the kernel related to my current firmware so I can flash it after I restore?
Thanks.
dr.pythagora said:
Thank you for the related link. Helpful.
As I like, for the moment, to stick to the original firmware (to me, it is the most stable among all avalable roms for HTC Desire C), I still have two more questions:
- will the rooting stop the handset from receiving official updates?
- assume I root the handset and install cwm recovery and backup the current rom.
if ever I like to restore this backup, I will need to flash a kernel boot.img.
can I extract the kernel related to my current firmware so I can flash it after I restore?
Thanks.
Click to expand...
Click to collapse
- As far as I know, you can receive updates but you cannot apply them. It will show in the notifications "Software Update, Click to download" when you download it, it will reboot to recovery and stop there. Again, I'm not 100% sure about this but this happened to me once.
- If you flash a custom kernel like Prometheus Kernel, then you will have to flash the stock boot.img if you wanna go back to stock completely. But if you never changed your kernel from stock, then you don't need to do anything. I have provided the link to stock kernel and stock recovery as well, in the Index thread. (Link in my signature)
PS - As far as Custom ROMs go, you should try the Sense Roms. All of them are based on the stock ROM so all of them are completely stable. You can always put the 'Stock theme' on these roms to make them look like the Stock ROM and you will end up with a ROM that looks exactly like Stock but performs much better and has increased functionality
Hope this was helpful. I'll be glad to answer any further questions.
It will not definitely modify your system it will add a folder to your system to access the system... and also it adds app called Superuser or SuperSU ....
Features of Rooting:
Android rooting is the process of allowing users of smartphones, tablets, and other devices running the Android mobile operating system to attain privileged control (known as "root access") within Android's subsystem.
Rooting is often performed with the goal of overcoming limitations that carriers and hardware manufacturers put on some devices, resulting in the ability to alter or replace system applications and settings, run specialized apps that require administrator-level permissions, or perform other operations that are otherwise inaccessible to a normal Android user. On Android, rooting can also facilitate the complete removal and replacement of the device's operating system, usually with a more recent release of its current operating system. Most of the time,[citation needed] rooting a device voids its warranty.
From Wikipedia ...
Hi all ,
This problem is facing very one how install kingroot and made his/her device rooted with kingroot , the root is done will , but after Root we can receive ota updates but when we download and install the ota update a problem found :
Unexpected error : install-recovary.sh status 7
I have trying to make full un-root by kingroot , or superus and nothing fixed until now !!!
Some people told me that you must install stock-rom !?
But why stock-rom if there is better and easy solution ?
I need your help developers I guess this problem not hard one for you ^_^ .
So who is the hero that's will save the day
Thanks.
As I've told you, you need the stock install-recovery.sh for your device (LUZ17x or LUZ59x?)
Everything else it way too complicated! (You will need an unlocked Bootloader, modded stock-recovery or TWRP, patched updater-script, etc...)
But it seems, nobody here is willing to pull the file (or even better a stock system.img) from their device.
I forgot to pull a system.img before rooting, so I can't help.
Seems, that there is unfortunately no real active community in Thailand or Turkey (apart from the language barrier), when it comes to these devices.
At least until now.
update
theeteempire said:
Hi all ,
This problem is facing very one how install kingroot and made his/her device rooted with kingroot , the root is done will , but after Root we can receive ota updates but when we download and install the ota update a problem found :
Unexpected error : install-recovary.sh status 7
I have trying to make full un-root by kingroot , or superus and nothing fixed until now !!!
Some people told me that you must install stock-rom !?
But why stock-rom if there is better and easy solution ?
I need your help developers I guess this problem not hard one for you ^_^ .
So who is the hero that's will save the day
Thanks.
Click to expand...
Click to collapse
if you want update then why u rooted your device? this is the basic thing you have to keep in mind before root you device that you cant install OTA if your device is rooted or any thing is changed into the system(i.e. cant be done without root).
The people telling you about installing stock rom, is the best and last solution according to me... search the net you will surely find the stock rom and its procedure to install as well...
Best of luck with searching and flashing the stock rom:good:
sagar27691 said:
if you want update then why u rooted your device? this is the basic thing you have to keep in mind before root you device that you cant install OTA if your device is rooted or any thing is changed into the system(i.e. cant be done without root).
The people telling you about installing stock rom, is the best and last solution according to me... search the net you will surely find the stock rom and its procedure to install as well...
Best of luck with searching and flashing the stock rom:good:
Click to expand...
Click to collapse
I think that un-root will solve this problem with out need to make stock-rom
vel_tins said:
As I've told you, you need the stock install-recovery.sh for your device (LUZ17x or LUZ59x?)
Everything else it way too complicated! (You will need an unlocked Bootloader, modded stock-recovery or TWRP, patched updater-script, etc...)
But it seems, nobody here is willing to pull the file (or even better a stock system.img) from their device.
I forgot to pull a system.img before rooting, so I can't help.
Seems, that there is unfortunately no real active community in Thailand or Turkey (apart from the language barrier), when it comes to these devices.
At least until now.
Click to expand...
Click to collapse
I need stock " install-recovary.sh for LUZ17E ". But no one help me to do that , I think there is no real developers here in second generation
theeteempire said:
I think that un-root will solve this problem with out need to make stock-rom
Click to expand...
Click to collapse
If you don't have a backup of that file (either made by yourself or the rooting software you have used), then 'unrooting' cannot help. That file is gone.
I went through @Sadronis's LUZ17E rom dump, extracted install-recovery.sh and attached it for you. But next time, please remember to backup the original file before rooting since especially for non-Nexus devices, stock ROMs (and thus files inside them) are not easy to find.
pawitp said:
If you don't have a backup of that file (either made by yourself or the rooting software you have used), then 'unrooting' cannot help. That file is gone.
I went through @Sadronis's LUZ17E rom dump, extracted install-recovery.sh and attached it for you. But next time, please remember to backup the original file before rooting since especially for non-Nexus devices, stock ROMs (and thus files inside them) are not easy to find.
Click to expand...
Click to collapse
Thank you man.
I can't replace the file or. Overwrite it , I have the root for my device but I can do nothing do you know why ?
theeteempire said:
Thank you man.
I can do nothing do you know why ?
Click to expand...
Click to collapse
Yes, you have to mount /system as "rw", for example:
Code:
adb remount
vel_tins said:
Yes, you have to mount /system as "rw", for example:
Code:
adb remount
Click to expand...
Click to collapse
Thank youuuuuuuuuu you help me a lot man
It's all done good .
I wanna ask you the stok rom that shared in this forum , can it be updated normally or not ?
First of all king root did not support on mine tablet but after a week ,i install 4.6 version of kingroot and it work but after a day when i want to update mine tablet galaxy 4 10.1 with ota ,it seem that the operating system of your device has been ........try to connect pc and etc.please help me ,i try lots of things like wipe cage, re factory etc others but now please help me without using pc.
Hi,
So i have a Moto G 2 XT-1068 with Android 5.0.2 and system version 22.21.28.titan_retaildsds.retaildsdsall.ex.03 reteu.
I rooted it and installed Xposed.
Since some days, my phone notify me that there is a new (official) update avalaible :
22.56.3.en.03
My first reflex was to post in the Xposed forum :
I have a Motorola Moto G 2nd edition (2014 XT-1068) with Android 5.0.2 and these xposed versions installed :
XposedInstaller_3.0_alpha4.apk
xposed-v75-sdk21-arm-1
This morning, my phone notify me that there is a newsoftware update available :
22.56.3.en.03
Can i update ?
Will Xposed still running or do i have anything to do before or after update ?
Click to expand...
Click to collapse
then :
Yes i'm rooted (i didn't know i could install exposed without root ?!) and i ask the question to rooted users : what is the recommended behavior to have when we are rooted and there is an official update like this one ? Should i ignore it ? Should i wait ? Should i update (with one of your solutions) ?
Click to expand...
Click to collapse
and this is the reply i had :
You'll have to ask how an OTA works for that in your device forum.
For Google Android (untouched by OEM) in Kitkat, OTA used to check each important file individually and if one was modified, OTA would fail. This did not check all existing files or added files such as root, so as long as you uninstalled Xposed properly (restoring the original app_process files etc) then an OTA would be fine.
Since Lollipop, OTA checks the /system partition as a single item so any modification in any file, or any additional file will make the OTA fail. In which case, the only way to update would be to flash a stock ROM.
You will need to find out in your device forum which of these applies to your device.
Click to expand...
Click to collapse
So this is it, i make a post in this Moto G 2014 forum
Doing the OTA will most likely delete the XposedBridge.jar so you will have to flash it again.
Else the Xposed app will still be available but the Framework won't be installed.
If it doesn't update because the /system partition has been modified, you'll have to flash the whole rom to update.
Ok, so i can try without risk ?
And what about my root ?
nonobio said:
Ok, so i can try without risk ?
And what about my root ?
Click to expand...
Click to collapse
Root will be gone too. You'll have to root it again by flashing SuperSu Zip though a custom recovery. (TWRP)
Restore the nandroid backup of the stock system you made in TWRP before you rooted.
You also need the stock recovery for the OTA to install.
You made a backup of your system before you rooted, right?
Hi
TheKill69 said:
Root will be gone too. You'll have to root it again by flashing SuperSu Zip though a custom recovery. (TWRP)
Click to expand...
Click to collapse
Ok.
Seriously said:
Restore the nandroid backup of the stock system you made in TWRP before you rooted.
You also need the stock recovery for the OTA to install.
You made a backup of your system before you rooted, right?
Click to expand...
Click to collapse
I'm note sure i made a backup before i rooted cause i'm note sure i knew i could install recovery without root but i checked my backup plan and my oldest backup is post root
So, what do you recommand when there is OTA like this ? Should i ignore them ?
It seems to be a hard process (flash stock recovery and root again and not sure if it will be possible anyway, is it ?) for maybe a little update ?
Maybe i should wait for the next big OTA like Android 6, then be sure that a new rooting process exist before update, and also be sure that Xposed will be supported ?
So if i ignore this 22.56.3.en.03, will i be notifyed for others newer OTA (like Android 6 for instance) ?
Thanks
nonobio said:
Hi
Ok.
I'm note sure i made a backup before i rooted cause i'm note sure i knew i could install recovery without root but i checked my backup plan and my oldest backup is post root
So, what do you recommand when there is OTA like this ? Should i ignore them ?
It seems to be a hard process (flash stock recovery and root again and not sure if it will be possible anyway, is it ?) for maybe a little update ?
Maybe i should wait for the next big OTA like Android 6, then be sure that a new rooting process exist before update, and also be sure that Xposed will be supported ?
So if i ignore this 22.56.3.en.03, will i be notifyed for others newer OTA (like Android 6 for instance) ?
Thanks
Click to expand...
Click to collapse
You might have to flash the whole stock firmware back to get the stock recovery. Big waste of time.
Then rooting back means using CF Auto Root Commands again..
You have to update to it though if you want Android 6.0.
Since it won't be soon, you rather go for CM13 once it gets really stable.
Also by the way, Xposed is already supported on MM.
Thanks for these precisions.
So if i can resume : a custom rom is easier for enjoy Android updates than just Xposed.
Hi,
Can you confirm :
For someone searching advanced features like customize status bar, quick settings, shutdown menu, hardware buttons, etc : customs roms and "stock rom + exposed" are two solutions. BUT, for someone searching these same advanced features but also keep his device up to date : custom rom is really a better solution. Isn't?
I was happy when i discovered xposed as it seemed to be a easier process that flashing a custom rom, but i didn't know that i couldn't update easily..
So, what is the advantage to use xposed instead of custom rom?
Hi,
I am always thinking if i will update my stock rooted xposed rom, or if i will install a custom rom prerooted like Cyanogen mod (o have easier future updates).
i have some questions :
1- Is it possible to install xposed and modules on a custom rom like cyanogen mod ? I think yes but can you confirm ?
I know that CM come with inbuilt tweaks but i discover some great xposed module i would continue to use, even if i install CM.
2-If i keep my stock rooted xposed rom, and don't make this "little" Android 5 OTA update, will be i notified for "Android 6" ?
(i don't want to lose my time to reflash my rom, reroot mydevice, etc.., just for a little update, but i could do that for a more important update like Android 6...
3- We are agree that if i flash a custom rom like CM, it will resolve my "ota update" problem, cause there won't be "Motorola OTA" anymore, but there will be CM updates easy to make, isn't ? If yes, what could be the advantage to use stock rom rooted + xposed vs custom rom + xposed ?
Thanks
so i have confirmed my s5 is rooted, i downloaded the XposedInstaller_3.0-alpha4.apk and i get the message (The Xposed framework is not installed. please download the latest ZIP file from XDA and flash it manually via recovery..... ( now i tried a few files from the index due to confusion, im still confused so hopefully someone can clear it up for me but i chose sdk23 due to the fact its 6.0.1 marshmallow , then i chose arma since i figured the phone is 32 bit, but i dont know which version to choose???? also i dont have an sd card, can this be completed with adb sideload, or perhaps flashfire ? please help im racking my brain over this lol.
makatwin said:
so i have confirmed my s5 is rooted, i downloaded the XposedInstaller_3.0-alpha4.apk and i get the message (The Xposed framework is not installed. please download the latest ZIP file from XDA and flash it manually via recovery..... ( now i tried a few files from the index due to confusion, im still confused so hopefully someone can clear it up for me but i chose sdk23 due to the fact its 6.0.1 marshmallow , then i chose arma since i figured the phone is 32 bit, but i dont know which version to choose???? also i dont have an sd card, can this be completed with adb sideload, or perhaps flashfire ? please help im racking my brain over this lol.
Click to expand...
Click to collapse
Check out:
http://forum.xda-developers.com/showthread.php?t=3113463
Since you are using stock Samsung ROM. Official xposed doesn't work properly with stock Samsung.
You don't need an external SD card to flash, just custom recovery, though something like flashfire might work. It worked to flash xposed on my LG tablet
mattzeller said:
Check out:
http://forum.xda-developers.com/showthread.php?t=3113463
Since you are using stock Samsung ROM. Official xposed doesn't work properly with stock Samsung.
You don't need an external SD card to flash, just custom recovery, though something like flashfire might work. It worked to flash xposed on my LG tablet
Click to expand...
Click to collapse
i have a custom recovery and its working good, i just need to go buy an sd card which im about to go do, and im also confused on what you mean by samsung ROM, you mean i have a jailbroken phone but i need to actually download a custom rom like ( CyanogenMod 13.0 ) to alow the xposed firmware to run properly ? and also confused because what you linked me to is for lollipop i thought my phone was running off marshmellow hence (6.0.1), perhaps you could clarify im very new to this, thanks for the response though!
(ALSO FORGOT TO ASK) will downloading cyanogenmod 13.0 on a phone that is already rooted ruin the phone? or is it not a jailbreak its just modifications, etc?
makatwin said:
i have a custom recovery and its working good, i just need to go buy an sd card which im about to go do, and im also confused on what you mean by samsung ROM, you mean i have a jailbroken phone but i need to actually download a custom rom like ( CyanogenMod 13.0 ) to alow the xposed firmware to run properly ? and also confused because what you linked me to is for lollipop i thought my phone was running off marshmellow hence (6.0.1), perhaps you could clarify im very new to this, thanks for the response though!
(ALSO FORGOT TO ASK) will downloading cyanogenmod 13.0 on a phone that is already rooted ruin the phone? or is it not a jailbreak its just modifications, etc?
Click to expand...
Click to collapse
i need to actually download a custom rom like ( CyanogenMod 13.0 ) to alow the xposed firmware to run properly ?
Click to expand...
Click to collapse
No, you just need the correct version of Xposed
what you linked me to is for lollipop i thought my phone was running off marshmellow hence (6.0.1)
Click to expand...
Click to collapse
What I linked you was the thread for a special build of Xposed for stock Samsung devices, it has Xposed for Marshmallow as well as Lollipop, you need to read through the thread.
(ALSO FORGOT TO ASK) will downloading cyanogenmod 13.0 on a phone that is already rooted ruin the phone? or is it not a jailbreak its just modifications, etc?
Click to expand...
Click to collapse
Modifying phones like putting custom ROMs and recoveries will void your warranty, but usually won't ruin them in most cases, but there is always the potential.
I'm going to put this out there, and please don't get offended. I would advise you not pursue this further until you do some more reading and learning, as you yet have grasped fully what you are doing. Since you don't have someone who knows what they are doing right there with you. And troubleshooting via a forum can be difficult to do since it isn't real time.
1. Android phones are not jailbroken, they are rooted.
2. ROM refers to the version/setup of Android for a device.
3. I said you didn't need an external SD card. Though, it does make it easier if you have one to do things like backup your ROM before you do any modifications like this, so if it goes south you can restore it to it's current state.
You can PM me more about this if you like instead of cluttering the thread.
I had to manually go to my applications and check storage permissions for xposed installer, although i deleted smart manager with titanium backup so could be why it wasnf automatically asked at installation.
SOLVED
https://www.androidfilehost.com/?w=files&flid=78069 install
xposed-v86.0-sdk23-arm-custom-build-by-wanam-20160709.zip
Hi,
about 2 years ago I rooted my S2 Galaxy Tab (T719) and now I would like to upgrade from Android 6.0.1 to Android version to 7 or 8. I have googled for instructions on how to upgrade a rooted S2 Tab but did not find anything useful (most info is on OTA upgrades which no longer works on rooted devices). Could someone please post step-by-step instructions (please bear in mind that I only ever deal with this kind of thing once every 2-3 years so I do not have much experience). I have TWRP v 3.0.2 installed (do I need to update this as well?) and the tablet is not encrypted (so hopefully I won't have to wipe the system partition and re-install all the app?!?). Thanks.
I also noticed that there is now a huge variety of ROMs out there. How can one know which ones are trustworthy? The main reason I rooted the tablet was to be able to increase privacy (control app permissions with XPrivacy). So I do not want to install some custom ROM that maybe contains spyware or other compromising features. Any advice on this would be greatly appreciated. Given my motivation (privacy) for rooting, would it maybe be better to go back to Stock ROMs (i.e. non rooted) and simply control web access via netguard (by preventing net access for some apps, they may still spy on my contacts, location, or email but cannot phone home to transmit the information)? At least I would still get OTA updates because being excluded from the OTA channel also poses a security risk in itself I suppose. Ok so any advice would be appreciated.
Thank you in advance!
There is no official Android 8 for our device. If you want 8 or 9 you have to install a custom ROM like LuK1337's LineageOS port. It is as safe as LineageOS is by itself on any device. Only problem you might have then is that calling is not possible anymore for now, but LTE works. If you want to use LOS, you HAVE to format data because it's not compatible at all. If you wanna stay on official Android you might keep it. Installing is done by flashing the official firmware with the correct country code over Odin. This will remove TWRP at first so you have to reflash it by Odin afterwards. For firmware download I always use: https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647 and Odin is found by google. If you wanna got the way to LOS you have to do all the steps I mentioned before too anyways to have a recent Modem firmware and bootloader. In that case you just have to flash LOS and OpenGAPPS by TWRP and delete /data aka Factory reset.
Regardless what you do, after ODIN is done, you HAVE TO boot into TWRP immediately to keep it from being removed by official firmware. While you are in there anyways you can install magisk to keep it from encrypting /data
Many thanks emuandco. So I guess I will stick with the Android 7 as I do not want to reformat the tablet and reinstall all the apps. I have started to download the Android 7 stock ROM, but it is taking quite long so in the meantime just to confirm, the steps to follow are:
1- use odin to flash the stock ROM (no steps required prior to this? I simply overwrite the existing ROM? I suppose that I will loose root then and need to re-root the device using the standard procedure as explained here: http://www.samsungsfour.com/tutoria...nougat-7-0-using-cf-auto-root-all-models.html ?)
2- use odin to flash TWRP (I will need the newest version I guess and cannot use the same as for Android 6?)
3- boot into recovery mode to ensure that TWRP does not get overwritten
4- done
Is this correct? Do I then need to reinstall Xposed, SuperSU and Xprivacy or will they be preserved?
Thanks again!
P.S.: BTW, I also found these instructions: https://forum.xda-developers.com/tab-s2/development/twrp-3-0-2-1-galaxy-tab-s22016-sm-t713-t3390627 which are slightly different from http://www.samsungsfour.com/tutoria...nougat-7-0-using-cf-auto-root-all-models.html and require a wipe of the data partition. Does this mean that for an update to Android 7 I definitely do need to wipe the data partition? If this is the case then this would be a major disadvantage of rooting in the first place and maybe I simply flash the stock ROM and do not root at all but go the "netguard" route as mentioned in my original message?
I never used the official Firmware that much. Fist thing I did was going on LuK1337's nerves to get a port of LOS for it up and running So no clue if Samsung manages to keep /data but I guess so. Yeah, looks fine what you list there. You COMPLETELY overwrite ANY modification in kernel or /system, so reflash your mods and root (Magisk). I always recommend to uase the MOST recent TWRP. (https://dl.twrp.me/gts28velte/ should be it in your case).
Ah and looking at your manuals... Check OEM unlock just to be rather safe than sorry if things go mad.
emuandco said:
I never used the official Firmware that much. Fist thing I did was going on LuK1337's nerves to get a port of LOS for it up and running So no clue if Samsung manages to keep /data but I guess so. Yeah, looks fine what you list there. You COMPLETELY overwrite ANY modification in kernel or /system, so reflash your mods and root (Magisk). I always recommend to uase the MOST recent TWRP. (https://dl.twrp.me/gts28velte/ should be it in your case).
Ah and looking at your manuals... Check OEM unlock just to be rather safe than sorry if things go mad.
Click to expand...
Click to collapse
Deleted