Related
Hi,
I am very new to this android world so my queries might feel stupid. Actually i m here after 3 years and that is very long period in this world. I know about rooting(super Su), bootloader and recovery (stock,CM and TWRP) . Recently read about Magisk and got some queries. Hope you will help me out. These are not device specific but need to learn.
What i read/study i found these readings...
1. Magisk roots device systemlessly (does not touch system partition) so one can get OTA updates easily.
2.To install and run Magisk one needs to unlock the bootloader .
3.(Device Specific) My redmi MI Flash tool says,If you unlock the bootloader , you wont get OTA updates.
4.I have previously rooted my galaxy Y and uninstalled system apps. If i delete sys apps from magisk,still can we say that we are not touching system.
So all statements are true? or some? or none ?
Here my device is redmi 3s (6.0.1- MIUI 9.6.1.0 Global Stable).All these queries are just in relation to OTA system updates. Nothing related to warranty.
Thanking You
Yes.
Yes.
Don't know about Xiaomi, but I've never had issues with OTA on a device with an unlocked bootloader (I've mainly used different Google and Oneplus devices). Someone with a Xiaomi is gonna have to chime in on this one.
As long as you use Magisk's debloating feature of replacing files or directories with empty ones, you're good. The actual /system partition won't be touched. Use a module like the Debloater module by @veez21, or make a debloater module yourself.
Didgeridoohan said:
Don't know about Xiaomi, but I've never had issues with OTA on a device with an unlocked bootloader (I've mainly used different Google and Oneplus devices). Someone with a Xiaomi is gonna have to chime in on this one.
Click to expand...
Click to collapse
Ahh, Thank You.
You get OTA system updates for your STOCK ROM ?
inwell said:
Ahh, Thank You.
You get OTA system updates for your STOCK ROM ?
Click to expand...
Click to collapse
Yes. But, having both Magisk and a custom recovery (an OTA won't install with a modified boot image and a custom recovery installed) I always find it easier to download the update and flash it manually. But, like I said, I have no idea if this is true for Xiaomi.
1. Ok. i also heared that when you update your device,you lose root...not true ? Or you need to root again ?
2.In normal stock device,we get update notification and we downlaod then restart (as per convenience)device to update.
If i remove some system apps from my rooted device and unroot the device,manage to get stock recovery back ,will the OTA update system treat my device as Stock-untouched? And install updates just as stock device will do ?
3. Is boot.img and bootloader are same things? Coz i read that for re locking boot loader you need to flash boot.img from stock software. (But Some procedures just use fastboot and relock oem command-they wont use boot.img,dont know why )
I read that unrooting,restoring stock recovery and locking bootloader again is more difficult/complicated than the rooting procedure
Some one should come up with solution just like Windows Restore .If you want to go back to everything STOCK,just use that feature same as done to Restore Windows in its previous state.
Any update that also updates the boot image (which means pretty much all) will remove root. But, that's just a simple case of reflashing Magisk right after applying the update.
If you've touched /system in any way, removing system apps or even just mounting the /system partition read-write, an OTA will fail. To be able update with an OTA your /system and /vendor partitions need to be untouched and you need to have the stock boot image and stock recovery installed. If your device doesn't conform to this the OTA will fail.
Boot image and bootloader are not the same thing. That you can read up on all over the internet, so I won't go into details. If you have done any kind of modifications on your device, I suggest you leave your bootloader unlocked. It's to easy to mess things up otherwise.
Going back to full stock is usually just a matter of flashing a full factory image/firmware package/stock ROM. Quite easy... Of course, some manufacturers make it harder than others.
Didgeridoohan said:
Boot image and bootloader are not the same thing. That you can read up on all over the internet, so I won't go into details. If you have done any kind of modifications on your device, I suggest you leave your bootloader unlocked. It's to easy to mess things up otherwise.
Click to expand...
Click to collapse
Ok. As you say the two are different , but can you explain in simple words (terms) that how they both are related/linked/connected? Coz as i read some forums/posts i get to read
1. To relock/lock bootloader you need to flash boot.img which suggests these (terms) are linked/connected.
2. but same time some forums/post suggest no img file flashing but just a fastboot command(s) to relock bootloader. In this case it seems they are not linked/connected.
And if the above 2 statements are true and device specific then how the bootloader and boot image are linked and not linked in diff devices? what changes are made so that in some cases these are linked and in some not
Sorry for asking too much. But you were really very kind to help me out.Thank you once again
I'm not 100% accurate (and someone will hopefully come I'm and correct me if needed), but basically the bootloader checks that everything is alright and then starts up your device. After that the boot image (ramdisk and kernel) takes over. Ramdisk basically makes sure all the partitions are mounted, and the kernel is exactly what it sounds like. The core of the OS, making sure that everything is working as it should.
This is of course a huge over-simplification, so if you want more you'll have to search around (and there are tons of resources around the web).
The main reason I can think of right at the moment for wanting to flash a boot image before locking the bootloader is that it's generally a good idea to have your device fully stock and functional before doing so. After you've locked the bootloader there might not be any going back if things start acting up and you could end up with a nice paperweight.
Questions are good. That's how you learn. I do believe that you'd be much better of searching around the internet for your answers. They've been put out there many, many times.
Ok.Thank you very much.I will learn more ...
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
Hi guys, like the title says. I'd like to flash OK Pie onto my old but still working P9 but after so, so much time i have forgotten everything I did to my phone to get to where I currently am. I've been searching for specifics to my situation but the guide to go from EMUI 8 to OK Pie is complicated enough as it is. If I have to factor in the "back to stock" procedure etc I think my brain would explode xD
So I'm looking for any links, guides, personal help or WHATEVER may help me at least get to chinese OREO 9I think I'm capable of taking it from there)
My current setup:
EVA-L09
Build number: EVA-L09C432B378
EMUI version: 5.0
Android: 7.0
My phone is from Latin America, So IIRC I unbranded it, changed it to cust 432 and flashed the latest (stock) firmware which at the time was B378.
I also have TWRP (the latest one) installed. If I got it right, I THINK I need to go back to stock recovery, flash the latest FW and go to Chinese OREO from there before trying to flash OK Pie, right?
Could somebody please be so kind as to either help me or at least point me to a thread/guide made for idiots such as myself xD that can walk me through the steps of going from my FW to stock recovery and stock latest FW?
I'll manage to get to oreo and custom after that.
I appreciate your help in advance.
Thanks.
EDIT: Forgot to mention that yes. I kept my unlock code so thats no problem
Thanks again!
SideSkroll said:
Hi guys, like the title says. I'd like to flash OK Pie onto my old but still working P9 but after so, so much time i have forgotten everything I did to my phone to get to where I currently am. I've been searching for specifics to my situation but the guide to go from EMUI 8 to OK Pie is complicated enough as it is. If I have to factor in the "back to stock" procedure etc I think my brain would explode xD
So I'm looking for any links, guides, personal help or WHATEVER may help me at least get to chinese OREO 9I think I'm capable of taking it from there)
My current setup:
EVA-L09
Build number: EVA-L09C432B378
EMUI version: 5.0
Android: 7.0
My phone is from Latin America, So IIRC I unbranded it, changed it to cust 432 and flashed the latest (stock) firmware which at the time was B378.
I also have TWRP (the latest one) installed. If I got it right, I THINK I need to go back to stock recovery, flash the latest FW and go to Chinese OREO from there before trying to flash OK Pie, right?
Could somebody please be so kind as to either help me or at least point me to a thread/guide made for idiots such as myself xD that can walk me through the steps of going from my FW to stock recovery and stock latest FW?
I'll manage to get to oreo and custom after that.
I appreciate your help in advance.
Thanks.
EDIT: Forgot to mention that yes. I kept my unlock code so thats no problem
Thanks again!
Click to expand...
Click to collapse
General link for Open Kirin ROMs
https://openkirin.net/user_guide/openkirin-rom-installation-instructions/
P9 thread for OK ROMs (under the P9 ROMs, Kernels... collection)
https://forum.xda-developers.com/p9/development/roms-openkirin-aosp-collection-t3828806
In short:
1) You must rebrand and update your L09c432 Nougat to AL10c00 Oreo, it is PRECISELY explained in the OP posts (mainly the post #2, but read #1 - #5 to get better picture) in the corresponding thread:
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
2) Once you will be on EVA-AL10c00b540 Oreo, you have to follow the OK installation guide from the first link.
You will have to install OK Omni Pie for Android 8, not for Android 9 (there is no stock Pie for P9)
If you search for Pie in the given two XDA threads (Search box at top- right on any XDA page), you will find that many people have undergone (and some returned back from OK Pie to stock Oreo) with no problems - but it is important to carefully follow the guides, first for rebranding and installing the Chinese stock Oreo, then to install OK ROM EXACTLY as described on their site (common guide for all OK ROMs and for all Huawei phones when already updated to the stock Oreo)
zgfg said:
General link for Open Kirin ROMs
https://openkirin.net/user_guide/openkirin-rom-installation-instructions/
P9 thread for OK ROMs (under the P9 ROMs, Kernels... collection)
https://forum.xda-developers.com/p9/development/roms-openkirin-aosp-collection-t3828806
In short:
1) You must rebrand and update your L09c432 Nougat to AL10c00 Oreo, it is PRECISELY explained in the OP posts (mainly the post #2, but read #1 - #5 to get better picture) in the corresponding thread:
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
2) Once you will be on EVA-AL10c00b540 Oreo, you have to follow the OK installation guide from the first link.
You will have to install OK Omni Pie for Android 8, not for Android 9 (there is no stock Pie for P9)
If you search for Pie in the given two XDA threads (Search box at top- right on any XDA page), you will find that many people have undergone (and some returned back from OK Pie to stock Oreo) with no problems - but it is important to carefully follow the guides, first for rebranding and installing the Chinese stock Oreo, then to install OK ROM EXACTLY as described on their site (common guide for all OK ROMs and for all Huawei phones when already updated to the stock Oreo)
Click to expand...
Click to collapse
Hi, thanks for replying. I'm aware of the PROCEDURE not so sure about the "how to".
Thats why I posted. Your post basically told me what I already knew (and talked about in my post)
What I'm looking for is help going from my current TWRP/STOCK/ROOTED FW. Back to full stock so I can start updating the ORIGINAL FW. I can't find any info on how to go back to stock recovery for instance. Do I need a specific recovery for the FW I'm running? Is it generic? Where do I find it? How do I flash it? Where do I get the stock firmware? (Huawei firmaware finder?) Which one do I flash? Does flashing the stock firmware automatically flashes the stock recovery? Things like that. I appreciate you trying to help but I already read and knew the things you linked to. My issue is, like I said: going back to stock before I can follow any guide to go up to oreo.
Thanks anyway!
SideSkroll said:
Hi, thanks for replying. I'm aware of the PROCEDURE not so sure about the "how to".
Thats why I posted. Your post basically told me what I already knew (and talked about in my post)
What I'm looking for is help going from my current TWRP/STOCK/ROOTED FW. Back to full stock so I can start updating the ORIGINAL FW. I can't find any info on how to go back to stock recovery for instance. Do I need a specific recovery for the FW I'm running? Is it generic? Where do I find it? How do I flash it? Where do I get the stock firmware? (Huawei firmaware finder?) Which one do I flash? Does flashing the stock firmware automatically flashes the stock recovery? Things like that. I appreciate you trying to help but I already read and knew the things you linked to. My issue is, like I said: going back to stock before I can follow any guide to go up to oreo.
Thanks anyway!
Click to expand...
Click to collapse
If rooted by Magisk, there is Uninstall option in Magisk Manager, it will unroot.
Similarly SuperSU had an Unroot/Unistall option.
In both cases you can flaslh back the stock Boot partition but it is cleaner to unroot by using their Uninstall options.
From TWRP or Fastboot you have to flash stock Recovery (corresponding to your current stock Nougat firmware) to revert back from TWRP
Generally, if you download from FirmwareFinder update.zip corresponding to your current stock Nougat (must be from FullOTA-MF or FullOTA-MF-PV), unzip, then by using Huawei Update Extractor, you can extract Boot.img and Recovery.img that you can flash then from Fastboot or from TWRP to go back to stock Boot and to stock Recovery
Once you go back to stock Boot and Recovery, you can boot to eRecovery (switch off, connect to charger, keep pressing Vol+ and boot by Pow) and choose Download latest firmware and recovery
----
But in fact, since you already have TWRP, use the HWOTA method from this post to update to c432b504 or b505:
https://forum.xda-developers.com/showpost.php?p=75787151&postcount=2
You can do the same with HWOTA7 from the corresponding thread I gave you (before you will go to rebrand to AL10c00b399).
In both cases, you have to download three update*.zip files for eg L09c432b504 (must be FullOTA-MF), rename one or two of them as described in the OP posts (be careful, some people have Windows 10 that hides zip extension and they wrongly rename files to have double zip extension and then HWOTA/HWOTA7 scripts cannot find the file and fail to flash resulting with half-brick), put them to DLOAD file on the SD card and follow the guides
zgfg said:
If rooted by Magisk, there is Uninstall option in Magisk Manager, it will unroot.
Similarly SuperSU had an Unroot/Unistall option.
In both cases you can flaslh back the stock Boot partition but it is cleaner to unroot by using their Uninstall options.
From TWRP or Fastboot you have to flash stock Recovery (corresponding to your current stock Nougat firmware) to revert back from TWRP
Generally, if you download from FirmwareFinder update.zip corresponding to your current stock Nougat (must be from FullOTA-MF or FullOTA-MF-PV), unzip, then by using Huawei Update Extractor, you can extract Boot.img and Recovery.img that you can flash then from Fastboot or from TWRP to go back to stock Boot and to stock Recovery
Once you go back to stock Boot and Recovery, you can boot to eRecovery (switch off, connect to charger, keep pressing Vol+ and boot by Pow) and choose Download latest firmware and recovery
----
But in fact, since you already have TWRP, use the HWOTA method from this post to update to c432b504 or b505:
https://forum.xda-developers.com/showpost.php?p=75787151&postcount=2
You can do the same with HWOTA7 from the corresponding thread I gave you (before you will go to rebrand to AL10c00b399).
In both cases, you have to download three update*.zip files for eg L09c432b504 (must be FullOTA-MF), rename one or two of them as described in the OP posts (be careful, some people have Windows 10 that hides zip extension and they wrongly rename files to have double zip extension and then HWOTA/HWOTA7 scripts cannot find the file and fail to flash resulting with half-brick), put them to DLOAD file on the SD card and follow the guides
Click to expand...
Click to collapse
Thank you. Thats exactly what I was looking for. I really appreciateyour help.
Btw, no one should have the "hide extensions for known file types" checkbox marked...
Edit: Should I flash the same FW version Im currently using and then update regularly? To prevent any issues? (Cause i noticed there are some rules as to the version jumps that can be made flashing like this...
SideSkroll said:
....Should I flash the same FW version Im currently using and then update regularly? To prevent any issues? (Cause i noticed there are some rules as to the version jumps that can be made flashing like this...
Click to expand...
Click to collapse
It must be the same model and cust, c432, but safer if you also apply the same build number (b387 ?)
Once you are back on stock you should start receiving OTA updates (have WiFi and a valid SIM card). Give it some time but check also manually from Settings / System updates.
As mentioned in my previous post, you can also use eRecovery / Install latest fw and recovery (if OTA coming slow), and there is a similar option in HiSuite. You will probably not need to use HWOTA or HWOTA7 to jump from clean stock b386 up to b50x
SideSkroll said:
Thats exactly what I was looking for...
Click to expand...
Click to collapse
Did you go for OK Pie (or you stayed on Nougat, or in between on stock Oreo b540), was it Okay?
zgfg said:
It must be the same model and cust, c432, but safer if you also apply the same build number (b387 ?)
Once you are back on stock you should start receiving OTA updates (have WiFi and a valid SIM card). Give it some time but check also manually from Settings / System updates.
As mentioned in my previous post, you can also use eRecovery / Install latest fw and recovery (if OTA coming slow), and there is a similar option in HiSuite. You will probably not need to use HWOTA or HWOTA7 to jump from clean stock b386 up to b50x
Did you go for OK Pie (or you stayed on Nougat, or in between on stock Oreo b540), was it Okay?
Click to expand...
Click to collapse
Hi again. First of all I would like to thank you agaib for your help. You made the process so much sinpler and quixk for me and I do apprexiate it.
Second, I updated to the latest "original" fw for my c432 phone OTA but then had to modify the HWOTA7 procesa so I could dl and install the latest/latest fw (because it wouldnt even register when searching for it) I used huawei fw finder to verify it and dl.
After that I went to chinese Oreo, flashed the network fixes and installed a TINY OTA update which fixed some sexurity issues apparently (thankfully it went Ok cause I THINK flashing OTA in a "converted" phone is a big nono?)
Anyways, I ended up on omni pie (the latest beta whixh is 5.2 I believe) as going AOSP was the whole point of this endeavor.
So far I'm LOVING it. Its such a refreshing thing not having to deal with all the bs OEMs bake into their roms... But Im experiencing a couple of issues as well. Not sure if its the rom, my phone or the android version (particularly my issue with battery life since I was having issues with the duration way before I updates, actually that was one of my motivations for updating since I read that pie had better battery management)
Anyway, my issues are as follow. Hope you can help (once again)
Battery life SUCKS (like really, it went from bad to terrible... Not sure if stock oreo would make it better, or perhaps omni pie needs some optimizations?)
The camera (huawei one, not sure about the aosp) has issues. Multiple issues. The biggest one being that if I try to go from back to front camera the app locks in a black screen and I have to go into the app, delete data, reboot the phone and relaunch it (and that doesnt fix it everytime)
The last issue is with pop messages from apps and/or settings. Sometimes, when installing and app and/or changing aome setting a white popup shows up with ONLY an OK option. I cant read anything on the popup. Everything is white. Not sure if its an issue with the theme (I changed from default to "hell" or something like that) but it is VERY annoying not knowing what youre agreeing to.
Last but not least I have a question about the stock rexovery, factory reset and flashing new versions of omni (if and wheb they come out)
In one of the steps for flashing omni the guide asks to perfomr a factory reset from the stock rom. Thing is, it doesnt work. I mean, when I confirm the factory reset the process starts and approximately at 15% an exclamation sign appears and the process percentage stops working. I can reboot the system and everything works fine (using the phone to post this actually) but Im left with that feeling of not knowing why something failed... You know what I mean? Is that nornal?(the failure to factory reset, not the feeling ) also, does factory wiping the phone removes root access? Or does it only renove magisk manager?
Also, if I ever wabt to update the rom (not change it mind you, but flash the next beta or stable or whatever they come up with) do I need to flash the stock recovery again? (Currently rooted with magisk) or is it a separate partition? (Sinxe I had to modify the ramdisk and not flash a custom recovery) also, will I need to do the whoooole thing again? (Backup everything, restore tk factory etc etc) or is it just like with lineage for exanple where you could flash and updatr and keep your data untouched?
Thanks for EVERYTHING my friend. And I hope you can answer my questions (particularly the ones about battery life and thebfactory reset issue since Im planning on doing one last factory reset before settling with the rom. Just waiting for my new micro sd. The one that will stay in the phone)
Sorry for the typos. Writing this huge post on a phone is a PITA.
SideSkroll said:
Hi again. First of all I would like to thank you agaib for your help. You made the process so much sinpler and quixk for me and I do apprexiate it.
Second, I updated to the latest "original" fw for my c432 phone OTA but then had to modify the HWOTA7 procesa so I could dl and install the latest/latest fw (because it wouldnt even register when searching for it) I used huawei fw finder to verify it and dl.
After that I went to chinese Oreo, flashed the network fixes and installed a TINY OTA update which fixed some sexurity issues apparently (thankfully it went Ok cause I THINK flashing OTA in a "converted" phone is a big nono?)
Anyways, I ended up on omni pie (the latest beta whixh is 5.2 I believe) as going AOSP was the whole point of this endeavor.
So far I'm LOVING it. Its such a refreshing thing not having to deal with all the bs OEMs bake into their roms... But Im experiencing a couple of issues as well. Not sure if its the rom, my phone or the android version (particularly my issue with battery life since I was having issues with the duration way before I updates, actually that was one of my motivations for updating since I read that pie had better battery management)
Anyway, my issues are as follow. Hope you can help (once again)
Battery life SUCKS (like really, it went from bad to terrible... Not sure if stock oreo would make it better, or perhaps omni pie needs some optimizations?)
The camera (huawei one, not sure about the aosp) has issues. Multiple issues. The biggest one being that if I try to go from back to front camera the app locks in a black screen and I have to go into the app, delete data, reboot the phone and relaunch it (and that doesnt fix it everytime)
The last issue is with pop messages from apps and/or settings. Sometimes, when installing and app and/or changing aome setting a white popup shows up with ONLY an OK option. I cant read anything on the popup. Everything is white. Not sure if its an issue with the theme (I changed from default to "hell" or something like that) but it is VERY annoying not knowing what youre agreeing to.
Last but not least I have a question about the stock rexovery, factory reset and flashing new versions of omni (if and wheb they come out)
In one of the steps for flashing omni the guide asks to perfomr a factory reset from the stock rom. Thing is, it doesnt work. I mean, when I confirm the factory reset the process starts and approximately at 15% an exclamation sign appears and the process percentage stops working. I can reboot the system and everything works fine (using the phone to post this actually) but Im left with that feeling of not knowing why something failed... You know what I mean? Is that nornal?(the failure to factory reset, not the feeling ) also, does factory wiping the phone removes root access? Or does it only renove magisk manager?
Also, if I ever wabt to update the rom (not change it mind you, but flash the next beta or stable or whatever they come up with) do I need to flash the stock recovery again? (Currently rooted with magisk) or is it a separate partition? (Sinxe I had to modify the ramdisk and not flash a custom recovery) also, will I need to do the whoooole thing again? (Backup everything, restore tk factory etc etc) or is it just like with lineage for exanple where you could flash and updatr and keep your data untouched?
Thanks for EVERYTHING my friend. And I hope you can answer my questions (particularly the ones about battery life and thebfactory reset issue since Im planning on doing one last factory reset before settling with the rom. Just waiting for my new micro sd. The one that will stay in the phone)
Sorry for the typos. Writing this huge post on a phone is a PITA.
Click to expand...
Click to collapse
This small OTA bringing Patch02 over b540 installs even over TWRP (but that was not the case for OTA from eg b535 to b540)
Cannot discuss/compare battery for Omni Pie, since not using Omni
Problem with Camera app does not show on stock Oreo. Even if the app was somehow ported from Huawei, there are maybe problems with integration to Omni.
Various Huawei/Mate models come with different cameras, but there is only one OK Omni ROM (with one Camera app) given to work on all Huawei/Mate models
Btw, somebody else also complained about issues with Camera (and GPS) and decided to go back to stock Oreo.
Similarly, issues you described about black notifications or so must be related to the custom ROM, theme or so.
As a general rule:
- for installing OK ROM, you flash System partition, and nothing else
- you also wipe Data partitiom (containing all your installed apps, incl Magisk Manager, also containing your user settings)
It does not affect any other partition.
Therefore, changes given by NW patch persist - without, you will have (also in that OK ROMs) problems with SIM card(s) and connecting to the network
Also, Magisk, which was flashed to Ramdisk, persists. You must only install Magisk Manager again, because it is user apo, installed to Data partition that was wiped
You must check on the OK side how they advice installing the updates of OK ROMs
(It is questionable if they will get updates any more, since OK team switched to development of ROMs which install over the stock Pie, whereas on P9 you have no stock Pie - only Oreo, and most likely, we will never see stock Pie for P9.
Just check when OK team released last ROM for stock Oreo, and compare with their releases of OK ROMs for stock Pie:
https://openkirin.net/download/
Hence IMO, for updating the OK ROM (if/when it comes), you will again just need to flash its System and to wipe Data (and then to reinstall user apps like Magisk Manager).
Hopefully, you can backup and restore some apps and settings by Titanium.
Whether you don't need to wipe Data for such update - check from the OK support.
On the Open Kirin site you will find Support pages (Faq, HowTo) and also a link to the live Telegram channel
Hi. i need urgent help regarding downgrading my galaxy note 8 from pie to oreo or nougat. i am using android pie from last 1 month. some of my apps stop working so i decided to downgrade from pie to oreo. i had downloaded oreo firmware december 2018 version from sammobile and tried to flash with odin 3.13.1 but it failed. i had tried different versions of odin but every time flashing stuck at set partition nand write start.i always run odin as administrator. i also tried to flash different firmware version like sept version of oreo but still it failed. i downloaded nougat firmware from sammobile. it flashed normally and i was happy but when my phone restarted i was shocked. my device was factory reseted but with android pie version. it looked flashing nougat only formatted my device. i am tired. i tried every damn thing. i tried changing usb port, tried differant usb cable, reinstalled device drivers, made sure that usb debugging is on , even tried on differant pc. but no result. then i tried emergency software recovery in smart switch. if i connect my phone switched on then smart switch discover my device but when i connect my device in download mode then smart switch says that device not supported. i contacted service centre but they say they do not downgrade the device.please please please someone help me. i am attaching a screenshot of odin stuck at nand write start.
drvish said:
Hi. i need urgent help regarding downgrading my galaxy note 8 from pie to oreo or nougat. i am using android pie from last 1 month. some of my apps stop working so i decided to downgrade from pie to oreo. i had downloaded oreo firmware december 2018 version from sammobile and tried to flash with odin 3.13.1 but it failed. i had tried different versions of odin but every time flashing stuck at set partition nand write start.i always run odin as administrator. i also tried to flash different firmware version like sept version of oreo but still it failed. i downloaded nougat firmware from sammobile. it flashed normally and i was happy but when my phone restarted i was shocked. my device was factory reseted but with android pie version. it looked flashing nougat only formatted my device. i am tired. i tried every damn thing. i tried changing usb port, tried differant usb cable, reinstalled device drivers, made sure that usb debugging is on , even tried on differant pc. but no result. then i tried emergency software recovery in smart switch. if i connect my phone switched on then smart switch discover my device but when i connect my device in download mode then smart switch says that device not supported. i contacted service centre but they say they do not downgrade the device.please please please someone help me. i am attaching a screenshot of odin stuck at nand write start.
Click to expand...
Click to collapse
Unfortunately you can't downgrade. Once you have flashed a higher bootloader version you are stuck with it.
If you are on bootloader v5 you may be able to downgrade to the last Oreo build, I am not 100% sure on that though.
Only if they are same bootloader
Sent from SM-N950U Still Rooted Note 8
stonedpsycho said:
Unfortunately you can't downgrade. Once you have flashed a higher bootloader version you are stuck with it.
If you are on bootloader v5 you may be able to downgrade to the last Oreo build, I am not 100% sure on that though.
Click to expand...
Click to collapse
Oh.... i checked my bootloader version is 6. Is there any way to downgrade to version 5 ????
No, there is not, sorry
Ok. So the final note is that i am not able to downgrade... so let me help with other issue that might help me. Knox on my device is tripped so i cant use latest samsung health app. Earlier on oreo i was able to install older version of app and then update it. But now on pie. Older version is not installing. It always says apk not installed. Atleast help me with that
drvish said:
Ok. So the final note is that i am not able to downgrade... so let me help with other issue that might help me. Knox on my device is tripped so i cant use latest samsung health app. Earlier on oreo i was able to install older version of app and then update it. But now on pie. Older version is not installing. It always says apk not installed. Atleast help me with that
Click to expand...
Click to collapse
You need to be rooted to be able to get that working again, some roms also have that patched already...
Although the thread is about the s7 I believe it is exactly the same for our note 8.
https://www.google.com/amp/s/forum....de-how-to-s-health-devices-knox-t3543306/amp/
stonedpsycho said:
You need to be rooted to be able to get that working again, some roms also have that patched already...
Although the thread is about the s7 I believe it is exactly the same for our note 8.
https://www.google.com/amp/s/forum....de-how-to-s-health-devices-knox-t3543306/amp/
Click to expand...
Click to collapse
I dont want to root again.... rooting will not let banking apps work.moreover if i wanted to root. Root files for note 8 pie are not available right now. I installed patched app but it does not have heart rate monitor and spo2 which renders heart rate sensor useless.... thats why i am so desperate for that app
drvish said:
I dont want to root again.... rooting will not let banking apps work.moreover if i wanted to root. Root files for note 8 pie are not available right now. I installed patched app but it does not have heart rate monitor and spo2 which renders heart rate sensor useless.... thats why i am so desperate for that app
Click to expand...
Click to collapse
As far as I am aware it is not possible without root.
drvish said:
I dont want to root again.... rooting will not let banking apps work.moreover if i wanted to root. Root files for note 8 pie are not available right now. I installed patched app but it does not have heart rate monitor and spo2 which renders heart rate sensor useless.... thats why i am so desperate for that app
Click to expand...
Click to collapse
Just use Magisk Hide to disguise, that you are using root
Reaper1337 said:
Just use Magisk Hide to disguise, that you are using root
Click to expand...
Click to collapse
I dont want to root. Moreover rooting files are not available for pie update.... so i think i am left with only 1 option to wait for someone to patch samsung health app to include heart rate sensors.....
drvish said:
I dont want to root. Moreover rooting files are not available for pie update.... so i think i am left with only 1 option to wait for someone to patch samsung health app to include heart rate sensors.....
Click to expand...
Click to collapse
You can flash TWRP, copy /system/build.prop to the PC or SD Card, edit it on the PC, put it back in /system.
Once you are done, just flash stock revovery via TWRP.
It sounds hard, but it's eazy if you know what you are doing. Banking apps will still work, and with build.prop edited s health will work too.
I am not gonna walk you trough the entire process but this is a summary.
Xenos7 said:
You can flash TWRP, copy /system/build.prop to the PC or SD Card, edit it on the PC, put it back in /system.
Once you are done, just flash stock revovery via TWRP.
It sounds hard, but it's eazy if you know what you are doing. Banking apps will still work, and with build.prop edited s health will work too.
I am not gonna walk you trough the entire process but this is a summary.
Click to expand...
Click to collapse
Thats the problem bro.... i downloaded twrp from official twrp website and tried to flash it. Odin message was pass but when i rebooted my phone in recovery mode my phone was still on stock recovery.... same thing happened with my galaxy tab.
I hope someone can provide me edited s health apk
drvish said:
Thats the problem bro.... i downloaded twrp from official twrp website and tried to flash it. Odin message was pass but when i rebooted my phone in recovery mode my phone was still on stock recovery.... same thing happened with my galaxy tab.
Click to expand...
Click to collapse
Oooh that, it's nothin.
You just need to hold volume up + bixby and power just before the phone auto restarts from download mode. When you do that it will boot twrp.
If you don't understand it go watch MaxLee on youtube, his method of flashing twrp on s8/n8
Xenos7 said:
Oooh that, it's nothin.
You just need to hold volume up + bixby and power just before the phone auto restarts from download mode. When you do that it will boot twrp.
If you don't understand it go watch MaxLee on youtube, his method of flashing twrp on s8/n8
Click to expand...
Click to collapse
So there is no other method except flashing twrp.... i think i have to wait for patched s health app or to leave that.... coz i really dont want to mess with stock firmware anymore....
drvish said:
So there is no other method except flashing twrp.... i think i have to wait for patched s health app or to leave that.... coz i really dont want to mess with stock firmware anymore....
Click to expand...
Click to collapse
The way I know it, there is no way without twrp or root, and you said you don't want root because of banking apps.
If you flash twrp, do the thing with build.prop, and then flash stock recovery, you could still recive OTA updates and banking apps will work.
You just have to set up s health before the next OTA because that will revert built.prop back to normal.
But as long as you set up s health before that it will be ok.
Xenos7 said:
The way I know it, there is no way without twrp or root, and you said you don't want root because of banking apps.
If you flash twrp, do the thing with build.prop, and then flash stock recovery, you could still recive OTA updates and banking apps will work.
You just have to set up s health before the next OTA because that will revert built.prop back to normal.
But as long as you set up s health before that it will be ok.
Click to expand...
Click to collapse
Leave that bro coz m not ready to do that. Just help me with 1 thing if possible. There was other way to use s health on knox tripped device. That was downloading s health 4.8 version install it and open it. It will stuck at loading screen. Update it and it will work fine. Earlier i get it working that way when my device has oreo version. But now after pie update when i try to install any s health apk before version 5 that is 4.5, 4.7 or 4.8. I always get a message app not installed. After version 5 app get installed but again with root problem. Can u help me with installing old version. I dont know why s health old version is not getting installed. I had some other apps that are now discontinued. That apps get installed easily
drvish said:
Leave that bro coz m not ready to do that. Just help me with 1 thing if possible. There was other way to use s health on knox tripped device. That was downloading s health 4.8 version install it and open it. It will stuck at loading screen. Update it and it will work fine. Earlier i get it working that way when my device has oreo version. But now after pie update when i try to install any s health apk before version 5 that is 4.5, 4.7 or 4.8. I always get a message app not installed. After version 5 app get installed but again with root problem. Can u help me with installing old version. I dont know why s health old version is not getting installed. I had some other apps that are now discontinued. That apps get installed easily
Click to expand...
Click to collapse
The reason you can't install the modded version is because the version that was modded is less than pre-installed version on the device. As of now, you can't downgrade apps, only upgrade. Your only option is to wait for someone to patch a later version from the version you got installed on your phone.
I think someone can even just change a number in AndroidManifest.xml install it and then just upgrade.
I'm sure a patched version will pop-up again somewhere on xda, just make sure it's later version than the version pre-installed into the system.
Xenos7 said:
The reason you can't install the modded version is because the version that was modded is less than pre-installed version on the device. As of now, you can't downgrade apps, only upgrade. Your only option is to wait for someone to patch a later version from the version you got installed on your phone.
I think someone can even just change a number in AndroidManifest.xml install it and then just upgrade.
I'm sure a patched version will pop-up again somewhere on xda, just make sure it's later version than the version pre-installed into the system.
Click to expand...
Click to collapse
Hmmm.... lets wait for some godman to do the favour..... i am from medical profession so dont know much abt this coding stuff. Otherwise i would have done that myself :laugh:
Hello folks !
I just bought a galaxy S10 5G G977N and I found it difficult to work my way through all the changes made in rooting/custom roming smartphones (I had a galaxy S7 before that, it was pretty easy).
What I read for now :
How to root with magisk : https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
How to install TWRP : https://twrp.me/samsung/samsunggalaxys105G.html
What I learned :
Rooting device is far more complicated than it was before. If I do so, I won't be able to update stock rom OTA, I'll have to reflash a patched recovery (AP file) for every update. This bothers me because its not convenient, and because messing with odin is way riskier than flashing zip from custom recovery and may brick my phone, so the less I use it, the better I think.
Plus,booting the phone will be a pain in the ass, having to do the right key combination
Installing TWRP will not change that.
What I'm wondering :
I'm a bit confused on how I will be able to update stock ROM (The way I understand it, I'll have to reinstall TWRP after each update)
And I'm even more confused about how all of this will work with custom ROMs.
Let's say I root my phone and install TWRP. If I want a custom ROM and keep it rooted, how will it work ? I'll have to unzip the ROM, patch the AP file with magisk, rezip it, flash it with twrp and voilà ? And I'll have the same key combination issue where I'll have to boot a certain way to access the rooted ROM, and if I don't, I'll boot on an unrooted ROM ?
Thank you a lot for helping. I'm really used to rooted and unbloated ROM (God I've forgotten how bloated stock ROMs are !) but the complexity of the operation stops me for now. I don't want to brick my phone and I'm not sure I'll have the courage to do all of this every 3 month for each update.
Hello!
This thread is a bit old. But since I had to dig the forum to find what I was looking for (and update my knowledge), maybe my answer will be useful for somebody else.
Rooting device is far more complicated than it was before.
Click to expand...
Click to collapse
Yep. That was a shocker for me, coming from a 7 year old phone.
Plus,booting the phone will be a pain in the ass, having to do the right key combination
Click to expand...
Click to collapse
I agree! Thankfully, somebody smarter than me took care of that. You can thank ianmacd for his multidisabler (GitHub project's page; xda thread).
One of its functionality is to disable "Stock recovery auto-restoration".
If you want to see a guide for how to use it (for S10 5G Snapdragon only, but same principle apply for the others), afaneh92 wrote one! Same thing by corsicanu, but with official links to download TWRP (and his repository for the other stuff), and it works with other versions of the S10 too. corsicanu got his tools here if needed.
Be careful, you must format /data after disabling encryption with multidisabler. Back up your data first!
I won't be able to update stock rom OTA
Click to expand...
Click to collapse
No OTA if you root.
You can still upgrade the stock kernel/firmware to a newer Android version manually. Afterwards, flash TWRP, then flash multidisabler again, then run multidisabler in terminal. And, all good!
(Reflashing stock firmware disables "multidisabler")
Check for firmware updates on Samsung's changelog page.
Replace your S10 model number and CSC code in the link below:
doc.samsungmobile.com/YourModelNumber/YourCscCode/doc.html
To know which CSC you have:
Go to Settings > About phone > Software information > Service provider software version
The last line should show the current CSC (three characters), e.g. mine is KTC for Korean KTC devices.
doc.samsungmobile.com/sm-g977b/ftm/doc.html
corsicanu makes it easier for us, here is his github page for the S10.
I'm a bit confused on how I will be able to update stock ROM (The way I understand it, I'll have to reinstall TWRP after each update)
Click to expand...
Click to collapse
To flash the ROM the first time:
Flash the ROM with TWRP (adb sideload), Format data/factory reset. Formating everything will reenable encryption if you had multidisabler installed first. I think. So I guess flash it afterwards, and format data again?
For example, you can follow Lineage OS's guide. But they don't take care of vbmeta, encryption, and other issues. I'm not sure why.
To update the ROM, it's easier: no need to reinstall multidisabler after a dirty flash. (Lineage guide to update their ROM)
I'm dropping some links you might need:
To download the last version of Odin (odin3-v3-14-1_3b_patched-zip as of date): realbbb's XDA thread.
All the versions of TWRP for the beyondx (G977B and N, maybe other letters too )
Ok. That's all for now. Good luck!