Update rooted/non-encrypted SGS9+/SM-G965F - Samsung Galaxy S9+ Questions & Answers

Is that even possible ? I have a rooted SM-G965F (EU chip), which I set up from scratch - OEM unlock, flashed the then-current stock ROM, flashed TWRP, installed Magisk and no-verity-opt-encrypt. Ended up happily with a current, rooted phone in factory conditions.
But it's been a while, and there have been plenty of updates for the phone, including critical security changes. I would like to put a newer stock/system on it, but I would prefer not to have to reinstall and reconfigure all my stuff. But the process I followed suggested that repeating it would force me to delete everything on the phone again (due to the encryption issues).
Is there a way for me/someone with a rooted phone to update to a current/newer ROM without losing all settings and such ? Naturally, I want the new ROM to be rooted again.

Still looking for advice with this

Mietschein said:
Is that even possible ? I have a rooted SM-G965F (EU chip), which I set up from scratch - OEM unlock, flashed the then-current stock ROM, flashed TWRP, installed Magisk and no-verity-opt-encrypt. Ended up happily with a current, rooted phone in factory conditions.
But it's been a while, and there have been plenty of updates for the phone, including critical security changes. I would like to put a newer stock/system on it, but I would prefer not to have to reinstall and reconfigure all my stuff. But the process I followed suggested that repeating it would force me to delete everything on the phone again (due to the encryption issues).
Is there a way for me/someone with a rooted phone to update to a current/newer ROM without losing all settings and such ? Naturally, I want the new ROM to be rooted again.
Click to expand...
Click to collapse
In general if you are going to upgrade your firmware you will have to start over again. IE: Twrp, Root etc..
In regards to apps and data do a backup first.

Mietschein said:
Is that even possible ? I have a rooted SM-G965F (EU chip), which I set up from scratch - OEM unlock, flashed the then-current stock ROM, flashed TWRP, installed Magisk and no-verity-opt-encrypt. Ended up happily with a current, rooted phone in factory conditions.
But it's been a while, and there have been plenty of updates for the phone, including critical security changes. I would like to put a newer stock/system on it, but I would prefer not to have to reinstall and reconfigure all my stuff. But the process I followed suggested that repeating it would force me to delete everything on the phone again (due to the encryption issues).
Is there a way for me/someone with a rooted phone to update to a current/newer ROM without losing all settings and such ? Naturally, I want the new ROM to be rooted again.
Click to expand...
Click to collapse
yes, just flash the HOME_CSC in twrp and you wont lose any settings. Might loose root, but its easy AF to fix
spawnlives said:
In general if you are going to upgrade your firmware you will have to start over again. IE: Twrp, Root etc..
In regards to apps and data do a backup first.
Click to expand...
Click to collapse
uhm, not at all man. the home_csc negates what you said

I'm mostly worried about drive encryption, or whatever that is called exactly. I (had to, I think) disable it when I originally rooted, and in the process it wiped my entire phone (which I was fine with). I'm worried that if I update the firmware, it will re-enable encryption, and then when I root again, it will get wiped again. Is that a concern, or am I worried about nothing ?
Also, as for backups, I use Titanium. Is that still a good idea ? I bought it ages ago and don't know if it's still current.

Mietschein said:
I'm mostly worried about drive encryption, or whatever that is called exactly. I (had to, I think) disable it when I originally rooted, and in the process it wiped my entire phone (which I was fine with). I'm worried that if I update the firmware, it will re-enable encryption, and then when I root again, it will get wiped again. Is that a concern, or am I worried about nothing ?
Also, as for backups, I use Titanium. Is that still a good idea ? I bought it ages ago and don't know if it's still current.
Click to expand...
Click to collapse
If you update your firmware it will re-encrypt your phone. If you do want to install twrp and root then the formatting will have to be done again. You can do this first then restore your backup.
Titanium backup should be fine ( I have it but don't use it,also have the pro version ). Just download latest version from playstore it was last updated April this year.
What ever your backup method keep it on your sd card or computer.

Mietschein said:
I'm mostly worried about drive encryption, or whatever that is called exactly. I (had to, I think) disable it when I originally rooted, and in the process it wiped my entire phone (which I was fine with). I'm worried that if I update the firmware, it will re-enable encryption, and then when I root again, it will get wiped again. Is that a concern, or am I worried about nothing ?
Also, as for backups, I use Titanium. Is that still a good idea ? I bought it ages ago and don't know if it's still current.
Click to expand...
Click to collapse
Well, I thiiiiiink the forced encryption is enabled on the kernel and only happens when you allow the phone to boot.
So, in THEORY you can update via Odin, and IMMEDIATELY after you flash stock updated firmware via Odin, flash TWRP and immediately boot to TWRP before you give the phone time to boot. And flash the encryption remover again and also root zip and then reboot. But I think it will still wipe your apps clean.
To make this whole process easier, disable auto-reboot in Odin so that you can manually reboot your phone and be ready to boot to download mode immediately. If you get anywhere past the splash screen (black screen after it or bootanimation) you can consider your phone encrypted again. So I would practice catching download mode a few times after a forced reboot before you attempt all of this lol
---------- Post added at 11:14 AM ---------- Previous post was at 11:04 AM ----------
So, just to cover all bases, this is what you do:
->Boot to download mode
->Disable auto-reboot from Odin
->Flash updated firmware in Odin
->After its finished, you should get PASS in Odin but the phone does not reboot
->Manually reboot your phone and immediately after you see the screen turn off, press the buttons to enter download mode again
->Make sure auto-reboot is still turned off in Odin
->Flash TWRP
->Manually reboot your phone and immediately after you see the screen turn off, press the buttons to enter TWRP
->Flash the encryption remover and the root zip
->Quite honestly, I'd recommend a normal wipe to maximize battery life and performance on the new firmware
Good luck.

Related

Will I lose root?

Forgive my novice status with both my first Android phone and this site. Galaxy S6 which I rooted using Odin and I believe a kernel it was, from here.
If I run the os upgrade from Smartswitch, what effect will that have one the phone as far as being rooted and all the stuff I've done since being rooted. Thank you very much.
If you update, you will lose root. I would not update via Smart Switch, being that you are rooted with a custom kernel. Your best bet would be to update via Odin. Check the subforum here @ xda for your variant of the S6 for further info. You should find what you need in the General forum of that subforum.
es0tericcha0s said:
If you update, you will lose root. I would not update via Smart Switch, being that you are rooted with a custom kernel. Your best bet would be to update via Odin. Check the subforum here @ xda for your variant of the S6 for further info. You should find what you need in the General forum of that subforum.
Click to expand...
Click to collapse
Thank you sir. Is it simply a matter rerooting the device? Or will every other change I made from root be gone too?
It will wipe your phone, so you will have to redo any mods or settings.
es0tericcha0s said:
It will wipe your phone, so you will have to redo any mods or settings.
Click to expand...
Click to collapse
It wipes the phone every time you do an operating system update? Why would anybody ever do it unless something wasn't working? Unless it's only when rooted? I have good pc skills and some understanding of Linux even, but man I have a lot to learn about these phones.. What about Smart Switch backups? It wipes the phone, how close to before the update will that get somebody? I don't have time to research all this. I may just leave it. This update I'm talking about is a gigabyte btw. That seems pretty huge for a phone.
It wipes the phone when you update via Odin (unless modded by a dev to not wipe for some versions). The reason that this needs to be done is that when you are rooted and have changed system files, OTA updates usually cause issues like bootloops / soft brick. Typically when you have a Samsung with a modded kernel and system, the regular Samsung tools like Kies and Smart Switch fail. Your results may vary, but I would have the firmware downloaded to reload via Odin in case that does not work. I am not familar with Smart Switch as it just came out for the S6 and newer stuff and I have never had use for Samsung's tools like that because I prefer to use Google and Titanium Backup to backup and restore my apps, contacts, texts, call logs, etc. As far as the updates go, 1 GB is actually kind of small for newer versions. It's probably bigger once unzipped. Some newer phones have systems that are well over 2 GBs. Most people here usually update via custom rom as it's easy to do on the phone once you have a working custom recovery and doing a factory reset there will not wipe the internal storage @ /data/media. If you prefer to be stock rooted, there most likely is a version already posted in the subforum for your phone. If you are updating whole Android versions and not minor updates, it might be required to install additional firmware files with Odin or Chainfire's Flashfire tool. If so, the developer will mention that in the OP of the thread.
es0tericcha0s said:
It wipes the phone when you update via Odin (unless modded by a dev to not wipe for some versions). The reason that this needs to be done is that when you are rooted and have changed system files, OTA updates usually cause issues like bootloops / soft brick. Typically when you have a Samsung with a modded kernel and system, the regular Samsung tools like Kies and Smart Switch fail. Your results may vary, but I would have the firmware downloaded to reload via Odin in case that does not work. I am not familar with Smart Switch as it just came out for the S6 and newer stuff and I have never had use for Samsung's tools like that because I prefer to use Google and Titanium Backup to backup and restore my apps, contacts, texts, call logs, etc. As far as the updates go, 1 GB is actually kind of small for newer versions. It's probably bigger once unzipped. Some newer phones have systems that are well over 2 GBs. Most people here usually update via custom rom as it's easy to do on the phone once you have a working custom recovery and doing a factory reset there will not wipe the internal storage @ /data/media. If you prefer to be stock rooted, there most likely is a version already posted in the subforum for your phone. If you are updating whole Android versions and not minor updates, it might be required to install additional firmware files with Odin or Chainfire's Flashfire tool. If so, the developer will mention that in the OP of the thread.
Click to expand...
Click to collapse
It just occurred to me. Firmware IS the Android OS on these phones. That's not the same as a kernel though? With the regular Linux os it isn't. Forgive my ignorance. Like I say this is my first one.
Unfortunalely, firmware is one of those terms that can mean a few different things depending on the situation (like flashing). Firmware in this instance refers to the bootloader and modem files as well for Samsungs. If you don't have the bootloader and modem files (which roms do not install) correctly matched to the OS then you might have issues like not being able to boot or cell service issues.
es0tericcha0s said:
It wipes the phone when you update via Odin (unless modded by a dev to not wipe for some versions). The reason that this needs to be done is that when you are rooted and have changed system files, OTA updates usually cause issues like bootloops / soft brick. Typically when you have a Samsung with a modded kernel and system, the regular Samsung tools like Kies and Smart Switch fail. Your results may vary, but I would have the firmware downloaded to reload via Odin in case that does not work. I am not familar with Smart Switch as it just came out for the S6 and newer stuff and I have never had use for Samsung's tools like that because I prefer to use Google and Titanium Backup to backup and restore my apps, contacts, texts, call logs, etc. As far as the updates go, 1 GB is actually kind of small for newer versions. It's probably bigger once unzipped. Some newer phones have systems that are well over 2 GBs. Most people here usually update via custom rom as it's easy to do on the phone once you have a working custom recovery and doing a factory reset there will not wipe the internal storage @ /data/media. If you prefer to be stock rooted, there most likely is a version already posted in the subforum for your phone. If you are updating whole Android versions and not minor updates, it might be required to install additional firmware files with Odin or Chainfire's Flashfire tool. If so, the developer will mention that in the OP of the thread.
Click to expand...
Click to collapse
What I'm wondering is if there's any to have this galaxy s6 just like it is now after many hours of tweaking after one of these updates. I couldn't make heads or tails out of Titanium update.
You are being very helpful sir. Thank you.
Depends on what tweaks you've done and which update that it is. If it is a minor security update, then usually someone will post a flashable via custom recovery version and often you can get away with installing that over your current system while just wiping cache and dalvik cache. If it is a major update, like when Marshmallow comes out, it would benefit you to do a factory reset before updating. Yea, it sucks having to set up your phone again, though with all the tools available, it's really not that bad, but better to start fresh instead of wondering if the phone is slow or buggy because you didn't.
es0tericcha0s said:
Depends on what tweaks you've done and which update that it is. If it is a minor security update, then usually someone will post a flashable via custom recovery version and often you can get away with installing that over your current system while just wiping cache and dalvik cache. If it is a major update, like when Marshmallow comes out, it would benefit you to do a factory reset before updating. Yea, it sucks having to set up your phone again, though with all the tools available, it's really not that bad, but better to start fresh instead of wondering if the phone is slow or buggy because you didn't.
Click to expand...
Click to collapse
You're making sense. I totally get it. (about starting from scratch) Can I then re-root it with the same UniKernel-v5-920P-072715.tar as before or will I need a new one of those too.? Thanks again.
This is the update SmartSwitch is telling me is available. I don't even know which of this stuff we've been discussing this is. Firmware, ROM or OS update.
Current version: PDA:0H1 / CSC:0H1/ PHONE:0H1 (SPR)
Latest version: PDA:011 / CSC:011 / PHONE:011 (SPR)
Size: 1612 MB
That's just a minor security update. I would not use that kernel to reroot. I believe the only option available for the update you are on and the update that is available is via TWRP + SuperSU zip.
es0tericcha0s said:
That's just a minor security update. I would not use that kernel to reroot. I believe the only option available for the update you are on and the update that is available is via TWRP + SuperSU zip.
Click to expand...
Click to collapse
Whatsa TWRP + SuperSU zip Is that a tool and file for getting this update?
Sorry man. I've had this phone for less than 2 months and it's my very first one.
I do appreciate your patience. I've been a PC support guy for 16 years. I know what it's like.
TWRP = Team Win Recovery Project. It replaces the stock recovery that the phone uses to perform factory resets and updates signed by Samsung. This allows you multiple benefits such as complete system/data/kernel backups, being able to wipe any combo of system/data/caches/internal storage, factory data reset without wiping internal storage, terminal commands, and installing custom files, roms, mods, etc not signed by Samsung to name a few. SuperSU is the popular root binary and root permissions app made by the developer Chainfire. If you needs links, I can provide, but assuming you're familiar with Googling things being a support guy. ☺
es0tericcha0s said:
TWRP = Team Win Recovery Project. It replaces the stock recovery that the phone uses to perform factory resets and updates signed by Samsung. This allows you multiple benefits such as complete system/data/kernel backups, being able to wipe any combo of system/data/caches/internal storage, factory data reset without wiping internal storage, terminal commands, and installing custom files, roms, mods, etc not signed by Samsung to name a few. SuperSU is the popular root binary and root permissions app made by the developer Chainfire. If you needs links, I can provide, but assuming you're familiar with Googling things being a support guy.
Click to expand...
Click to collapse
I have SuperSU already.
These are some truly terrible directions unless you already know enough to not need them.
https://twrp.me/devices/samsunggalaxys6sprint.html
Will installing TWRP effect the root method I've already used?
Will installing recovery effect any of the multitude of configurations I've already done?
Does this then allow manual installs of OTA updates without losing root or any of your configuration customizations?
Is it JUST the recovery partition were dealing which stands alone from the os?
Does Nandroid backup then encompass the recovery and os and rom etc? Meaning are they all backed up and custom recovery via TWRP was what made that possible? Or do you have to make your current config the recovery itself in order to do a ghost style backup and restore if you jack yourself up later? OR is not even this a ghost style restore?
Maybe it's just me, but the terminology is very confusing and I can't make heads or tails of what I'm even talking about with all this.
Tried to make backup with TWRP...
I guess whatever I flashed it with last time won't let it boot into recovery or the bootloader or whatever it's called. If I tell TWRP manager to reboot and do backup it just goes to the menu for rebooting and wiping cache etc. If I specifically go to "reboot to bootloader" it just reboots into android. I went to install a custom recovery and it said that if the location for the recovery is wrong it could brick the phone. I have no idea if it's right or wrong or if the root method I've already used is effecting this or not.
Installing a custom recovery will not affect your OS or any settings (as long as the recovery version is compatible with your phone and update). It is installed in a different partition than where the OS resides. It will not let you install official OTA zips. It is only for installing files not directly signed with Samsung's special key. When you do a nandroid backup, it will give you options on which parts of the phone you would like to backup. The important ones are boot, system, data, and EFS (though this is not typically needed when you restore, just as a precaution because it holds important data and settings of your IMEI and such - only restore if needed). Boot is the kernel, which controls many drivers for stuff like wifi, BT, CPU and GPU processes as well as others. System contains preloaded software, as in if you just restored boot and system, it would be like you factory reset the device and would need to setup your accounts and settings. Data is the apps, data, settings you have changed or added. A factory reset in the stock recovery would also wipe your /data/media storage which your phone sees as your internal storage. TWRP allows a factory reset that skips this so you will not lose the stuff you have accumulated on the phone such as pictures, music, downloads, etc.
The reason that when you are using TWRP Manager to install the recovery and reboot to it and it is still stock is probably due to the system has a script built in that notices if you change the recovery and will rewrite the stock recovery back to it upon rebooting. You can avoid this by renaming the script with a root enabled file browser. You will find this script in /system/etc/install-recovery.sh (or something similar). Just rename it to something like install-recovery.sh.bak.
es0tericcha0s said:
Installing a custom recovery will not affect your OS or any settings (as long as the recovery version is compatible with your phone and update). It is installed in a different partition than where the OS resides. It will not let you install official OTA zips. It is only for installing files not directly signed with Samsung's special key. When you do a nandroid backup, it will give you options on which parts of the phone you would like to backup. The important ones are boot, system, data, and EFS (though this is not typically needed when you restore, just as a precaution because it holds important data and settings of your IMEI and such - only restore if needed). Boot is the kernel, which controls many drivers for stuff like wifi, BT, CPU and GPU processes as well as others. System contains preloaded software, as in if you just restored boot and system, it would be like you factory reset the device and would need to setup your accounts and settings. Data is the apps, data, settings you have changed or added. A factory reset in the stock recovery would also wipe your /data/media storage which your phone sees as your internal storage. TWRP allows a factory reset that skips this so you will not lose the stuff you have accumulated on the phone such as pictures, music, downloads, etc.
The reason that when you are using TWRP Manager to install the recovery and reboot to it and it is still stock is probably due to the system has a script built in that notices if you change the recovery and will rewrite the stock recovery back to it upon rebooting. You can avoid this by renaming the script with a root enabled file browser. You will find this script in /system/etc/install-recovery.sh (or something similar). Just rename it to something like install-recovery.sh.bak.
Click to expand...
Click to collapse
You sir, are one patient and helpful man I very much appreciate your suffering through my whining. Interestingly, the boot loop just stopped in it's own and now I have the TWRP interface in place of the stock menu where the option was to wipe the cache partition.
Does this THIS mean I have a custom recovery now? Meaning, a different restore image than the one that came with the phone? Or does this now let me install that?
About this....
You were saying up HERE that if I run this update with smart switch I would lose root, but if I use TWRP to do it, I won't? Is that right? Thanks again.
Tiribulus said:
You sir, are one patient and helpful man I very much appreciate your suffering through my whining. Interestingly, the boot loop just stopped in it's own and now I have the TWRP interface in place of the stock menu where the option was to wipe the cache partition.
Does this THIS mean I have a custom recovery now? Meaning, a different restore image than the one that came with the phone? Or does this now let me install that?
Click to expand...
Click to collapse
This should mean that the recovery is installed. You can verify by using the app to boot to recovery or via powering the phone on by holding the Power, Volume Up, and Home buttons together as you restart. You should notice a recovery booting message in the top left and then you can let go of the buttons. Once there, you should perform a backup of the boot, system, and data partitions. If you have an EFS option, I would back that up too for safe keeping. It's rare that it would get corrupted, but best to have a backup just in cause.
If you update via Smart Switch, you will definitely lose root, as well as TWRP. Most likely, a developer has posted a rooted version of the update that you can use TWRP to install.
So I was looking into this a little closer for you and realized that the preferred method of updating and rooting the update you are trying to get involves using Odin to install the full update package, then reflashing TWRP, and using a newer version of the kernel to root. However, from some of the user comments about it, it seems like it might be better to wait till Samsung has released the source code of the kernel for the OI1 update. The kernels based on the slightly older 5.1.1 builds will work, but some people were experiencing random issues such as reboots or other oddities. I don't think OI1 has anything in it that would be worth losing root over or possibly having things run oddly. The alternative would be to update via a rom like this http://forum.xda-developers.com/spr...ment/ram9200-ofe-rom-thread-v3-5-1-1-t3173417

OnePlus X soft-bricked after version update

tl;dr - Can't seem to find my way out of a software brick. Have sideloaded the stock OS from 1+ but still forever getting the spinning dots or fastboot screen, depending on which mode i boot into.
Hi all. Signed up to make this thread, but i've been lurking for years.
I have a OnePlus X that is about the least modded smartphone i've ever owned. I've never been pleased enough with a retail product that i didn't feel compelled to strip out the bloat and start over, until this phone. Other than stock, i've just got a gallery app, some apps for manipulating text files or compiling code, couple games, and social media apps.
Anyway, a few days ago i got a notification about a software update. Downloaded. Installed. Updated. No problem.
Maybe yesterday or the day before, it showed up again. This morning i downloaded, installed, and suddenly i have apps closing. It's been over 12 hours so i'm hazy on how it all started, but i was getting something like "package installer" errors when attempting to open some apps. Same deal when i went to adjust permissions of those affected apps. Every time i unfocused a box that had pulled up swype, i would get an error message saying swype crashed or closed or something.
So i started uninstalling third party apps (i don't keep many, and most i've had for years so i think they're probably trustworthy). Same deal. Started uninstalling updates to google apps. Same deal. Went to uninstall and reinstall some non stock apps that i'd kept previously. Nothing.
I went to cook breakfast while an app was reinstalling, and i came back to a red dot on my screen with two white dots chasing each other around it. From what i'm reading that's a sign of a bootloop or software brick. I've taken all steps i could find, including wiping cache and sideloading a fresh stock OS, but to no avail.
Is it that i've ruined my google apps somehow and need to restore them? How would i even go about figuring out what the problem is? Any advice or guidance is appreciated
Hi,
As your device is in bootloop state, try flashing the stock rom. Make sure you wipe data and cache. As far as after update problems, i faced it few times. After updating many app crashed and phone hangs. So i prefer clean flash over dirty flashing, to make sure everything is hazel free. For the time being i upgraded from 3.1.2 to 3.1.3 without wiping data or cache and facing no problem( of course since it was an OTA). But sometimes situation comes when after update phone act weird, so tbe option which i prefer then is clean flashing the stock rom. Hope this helps.
"A09" said:
Hi,
As your device is in bootloop state, try flashing the stock rom. Make sure you wipe data and cache. As far as after update problems, i faced it few times. After updating many app crashed and phone hangs. So i prefer clean flash over dirty flashing, to make sure everything is hazel free. For the time being i upgraded from 3.1.2 to 3.1.3 without wiping data or cache and facing no problem( of course since it was an OTA). But sometimes situation comes when after update phone act weird, so tbe option which i prefer then is clean flashing the stock rom. Hope this helps.
Click to expand...
Click to collapse
I have wiped cache, deleted data, tried a factory reset in the stock bootloader, and i have used ADB to sideload a full stock rom (not upgrade package) that i downloaded from OnePlus.
Flash old stock recovery then 2.2.3. From there you can flash any MM stock firmware.
Exodusche said:
Flash old stock recovery then 2.2.3. From there you can flash any MM stock firmware.
Click to expand...
Click to collapse
Pardon me for being nooby, but how do i do this? Do i just sideload in ADB like i did the ROM? Most instructions i'm finding assume access to the OS either normally or through fastboot. I'm just stuck in the default recovery.
Thanks for the tip, though. Looking for a copy of the old stock recovery now. Did OnePlus alter their stock recovery recently? In some threads i've seen people say that a recent update made them unable to load a non-stock ROM. Is that the new recovery blocking access to non-1+ operating systems?
jtg1984 said:
Pardon me for being nooby, but how do i do this? Do i just sideload in ADB like i did the ROM? Most instructions i'm finding assume access to the OS either normally or through fastboot. I'm just stuck in the default recovery.
Thanks for the tip, though. Looking for a copy of the old stock recovery now. Did OnePlus alter their stock recovery recently? In some threads i've seen people say that a recent update made them unable to load a non-stock ROM. Is that the new recovery blocking access to non-1+ operating systems?
Click to expand...
Click to collapse
Fastboot flash easiest way. Make sure it's the old recovery from 2.2.2. Not the new mm stock recovery.
Yes, but how do i install the old stock recovery? I dug around on the forums and found the file, but the phone rejects it when sideloading and doesn't show the .img in the filesystem when inserted on a SD card.
Have to send it off to 1+ maybe? Literally all i can access right now is the (new) stock recovery. I never modded, rooted, etc before the software update sent me into the chasing dots
jtg1984 said:
Yes, but how do i install the old stock recovery? I dug around on the forums and found the file, but the phone rejects it when sideloading and doesn't show the .img in the filesystem when inserted on a SD card.
Have to send it off to 1+ maybe? Literally all i can access right now is the (new) stock recovery. I never modded, rooted, etc before the software update sent me into the chasing dots
Click to expand...
Click to collapse
I m not a dev, i m a newbie like you. i hv done a lot of experiments with my oneplus-x, as for u the first update u got few days back should be oos 3.1.2 and the one u got 2 days before should be 3.1.3. When u upgrade from lollipop to marshmellow, even your stock recovery got upgraded to latest version, which is something different from old lollipop recovery.
You said you have access to recovery mode. thts pretty much gud, what u can do is that wipe data and cache through stock recovery and do a clean install of oos 3.1.3. I ll be providing all the necessary links down below. If you need assistance with fastboot cmds and anything feel free to ask.
Thanks to original link provider @Sachin7843
Useful Links: -
1. Stock Lollipop Recovery - https://s3.amazonaws.com/oxygenos.oneplus.net/OPX_recovery.img
2. Official TWRP Recovery - https://dl.twrp.me/onyx/
3. Blu Spark Recovery - http://forum.xda-developers.com/devdb/project/dl/?id=20236
4. SuperSU for OOS 3.x.x - https://drive.google.com/file/d/0B4K5cvm1zdldcmZpc3RuVnRjUUE/view
5. Unbrick Guide - http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
6. Official Oxygen OS 3.1.3 link - https://s3.amazonaws.com/oxygenos.o...OTA_018_all_201609291837_741146bcf28e4587.zip
7. SD Card Writable fix in MM - http://forum.xda-developers.com/android/software/fix-extsd-fix-v1-0b-2016-01-18-t3296266
8. For Stock MM Recovery - http://forum.xda-developers.com/oneplus-x/general/oxygenos-3-1-0-marshmallow-community-t3445043
Sorry for my bad english
jtg1984 said:
Yes, but how do i install the old stock recovery? I dug around on the forums and found the file, but the phone rejects it when sideloading and doesn't show the .img in the filesystem when inserted on a SD card.
Have to send it off to 1+ maybe? Literally all i can access right now is the (new) stock recovery. I never modded, rooted, etc before the software update sent me into the chasing dots
Click to expand...
Click to collapse
Don't sideload it, use fastboot to flash it. "Fastboot flash recovery name.img" - without he quotes and the image name.
Sorry for vanishing. Had a busy week.
Not sure what happened the first time i tried to put the 2.2.3 image on the SD card, because the file didn't show up in my recovery, but i tried again later (after giving up on flashing the old recovery, since i couldn't figure out how to do that in recovery) and managed to do a clean install of the older OOS version.
That did the trick, and after booting up, my phone proceeded to update again - this time without any crashes or errors with my apps afterward. The phone still does the red dot with the white dots chasing around it when it boots up, which must be the new boot screen. It also seems to stay on that screen for much longer than it stayed on the old morphing shape boot screen, but it still boots up reliably now after 30-60 seconds rather than freezing in boot forever.
I've since enabled dev mode on my phone. Is that going to be enough to enable ADB commands from recovery? I kind of like that i've kept my phone stock, so i'll leave it that way if i can, but it would have been much easier to fix this problem if i'd had access to most of my debug commands. As it was, without dev mode and in the standard recovery, it seemed that sideload was the only command i was able to use, and only when the phone was requesting a sideload over usb

Have I bricked my phone? (I9300)

I've been using CM13 on my phone for a long while, but it was heavily bugged (my camera kept crashing, I've kept losing cell reception, couldn't receive calls etc), so I finally decided to try another ROM. I've heard good things about ResurrectionRemix ROMs, so I've decided to give it a try. I did factory reset and wiped cache (using CWM 6. something) and flashed RR 7.1 along with the appropriate gapps and rebooted the phone. It's worth noting that I've put the ROM and Gapps zip files on USB stick and connected it to the phone via micro USB cable. It all went smoothly, and the phone booted right up. However, once I got into the startup setting and choosing the language suddenly it just rebooted all on its own. Same thing happened 2 more times, and I got stuck in a bootloop after that.
So I figured I should flash another ROM, and I wanted to give RR 6.0 a try. I've downloaded it and saved it to my USB stick, however, when I tried to flash any zip files from my stick, it just kept randomly unmounting, disrupting the process, giving me "USBdisc0 idle-unmounted" message. Since I don't have an SD card, only thing I could do was push files to my phone, and I've managed to do so via Quick ADB Pusher. This time, flashing went without a hitch, however, I've tried cleaning my phone completely (formatting all the data and system files), and I think I messed it up a bit when I did that, since I didn't flash SuperSU along with ROP and gapps. Again, I got stuck in a bootloop without any signs of the ROM working.
So I decided to flash CM13 again. At least I was sure it was working on my phone, and I figured it was better to have a crappy phone than no phone at all. So I pushed the CM13 file onto the phone and flashed it, but still got stuck in bootloop. I finally remembered about SuperSU and tried to flash it too, but now my phone kept restarting in the middle of the flashing process. I've tried doing the factory reset and cache wipe, but I can't flash any files now without it restarting only few seconds into the process.
I have no idea what's going on, but seems that my phone is doing worse and worse as time moves on. At least I can still boot into recovery and download mode, so (hopefully) something can still be done. As it's probably painfully obvious, I'm not too knowledgeable about this stuff, I'm just following instructions people smarter than me put out, but seems I've messed it up good this time. Am I beyond help?
Try to download newest firmware from sanmobile.com and flash it with odin. Then root it make backup flash recovery and flash rom that you choose with recovery. There are lots of tutorials here on xda and on youtube. Just remember that flashing stock firmware with odin will delete all of your data so try to back them up somehow (i think that if you boot phone in recovery (twrp) the pc will see it like a pendrive)
Sirius8 said:
...
As it's probably painfully obvious, I'm not too knowledgeable about this stuff, I'm just following instructions people smarter than me put out, but seems I've messed it up good this time. Am I beyond help?
Click to expand...
Click to collapse
TBH you made the mistake many beginners make... Going ahead too fast with insufficient knowledge. But never too late to learn that lesson
Since you are getting more and more confused and your phone seems acting strange I recommend starting from scratch an be analytic about it. This will take just a few minutes more but you can be sure where a problem comes from.
First of all: Take 30 minutes to get acquainted with the basics and read through the first thread in my signature (just do it...)
If you can still get in download mode, get your latest stock rom e.g. from sammobile.com and flash it via ODIN. Run stock for a few minutes to see if everything works correctly (test camera, outgoing/incoming calls, mobile data, wifi, gps etc.). If something does not work STOP HERE and report back.
If all is fine go back to ODIN and install latest TWRP (cwm is seriously outdated, can cause lots of errors). Then boot into TWRP and flash whatever custom rom you like. If you install e.g. LOS 14.1 or RR 7.1.1 make sure you install gapps direcly after you flash the rom (do not reboot in between).
Any questions pop up: Shoot. I'm happy to help.
---------- Post added at 04:49 PM ---------- Previous post was at 04:42 PM ----------
McXred said:
Try to download newest firmware from sanmobile.com and flash it with odin. Then root it make backup flash recovery and flash rom that you choose with recovery. There are lots of tutorials here on xda and on youtube. Just remember that flashing stock firmware with odin will delete all of your data so try to back them up somehow (i think that if you boot phone in recovery (twrp) the pc will see it like a pendrive)
Click to expand...
Click to collapse
Since he already wiped system and data there is no point in a backup of those partitions. Only thing worth saving would be the efs partition.
And you don't need to root stock rom to go further...
If you are unrooted you have to REMOVE the "auto-reboot" checkmark in odin options and then - after the flash of twrp - reboot to recovery (TWRP) manually via holding Power+Home+VolUp for a few seconds.
If you do not uncheck that "auto-reboot" box, an thus allow the unrooted system (stock samsung system) to boot, it will overwrite the new twrp recovery you flashed 2 seconds before...
This is the point where I believe many confusion comes from. If you root first, any recovery you flash will not be overwritten. That is - I think - why many tutorials/tips say you must root stock first before installing a custom rom, which is simply not true.
But you are right that it would help to flash TWRP fist as outlined above, boot into it and make a backup to a microSD card... but of the efs partition (!) as the very first step. Then keep that backup safe and go from there with stock rom, testing for any problems.
So to reiterate the steps I would go:
1) Flash TWRP via odin and boot directly into it
2) Backup efs partition to a microSD card
3) Flash stock rom via ODIN and test
4) Go from there / report baback
Thank you so much for the replies guys, I'm glad there's still hope for my trusty SIII.
Are there any alternatives for sammobile.com though, since it requires premium account for the firmware I need. I've found another mirror on the site mrcrab.net/stockrom/2444.html (mirror 1 leads to sammobile.com, while mirror 2 leads directly to rapidgator), but can I trust it not to mess my phone up further?
Try updato.com for the firmware.
Hawaiihemd said:
If you can still get in download mode, get your latest stock rom e.g. from sammobile.com and flash it via ODIN. Run stock for a few minutes to see if everything works correctly (test camera, outgoing/incoming calls, mobile data, wifi, gps etc.). If something does not work STOP HERE and report back.
Click to expand...
Click to collapse
I've manage to flash stock ROM via Odin, however, as soon as the phone booted up it gave me the "low battery" message, even though I think there was plenty of battery left. But I figured the flashing process must have drained it. As I've tried to tap the OK button, the screen just froze and remained frozen for over 5 minutes. I took battery out and reinserted it, since nothing else worked, and got stuck in bootloop again, just as before flashing stock firmware.
Sirius8 said:
I've manage to flash stock ROM via Odin, however, as soon as the phone booted up it gave me the "low battery" message, even though I think there was plenty of battery left. But I figured the flashing process must have drained it. As I've tried to tap the OK button, the screen just froze and remained frozen for over 5 minutes. I took battery out and reinserted it, since nothing else worked, and got stuck in bootloop again, just as before flashing stock firmware.
Click to expand...
Click to collapse
Try to charge phone without turning it on, when it says its fully charged try to flash it again.
McXred said:
Try to charge phone without turning it on, when it says its fully charged try to flash it again.
Click to expand...
Click to collapse
Good idea. I would also keep it on the charger while booting.
This could be a symptom of a defective battery. So these steps might help.
Looks like you were right guys. I've recharged the battery and tried to flash the stock firmware again, but for some odd reason (it seems like I can't do the same thing twice with this phone ) Odin was giving me grief and couldn't establish proper connection with my phone, even though it recognized it at the beginning of the process. I've tried changing cables and ports, but with no avail.
After I gave that up, I tried booting the phone up anyway, but keeping it plugged in the charger this time. It booted right up, but I expected it to crash and reboot at any moment. So I sped up through the settings a and login processes, but it still worked like a charm. I've checked the camera and everything worked perfectly. So I kept it on charger for a couple of hours, to check if I would have any random crashes, but nothing happened. After I was sure it was stable, I unplugged the charger, and within the second I did that the phone crashed and got stuck in the bootloop again.
I've plugged the charger back in and it booted up just fine. The battery level was 89%, and I left it on charger the whole night (12+ hours). It had 90% when I woke up, it's back at 89% right now.
So, everything points to a faulty battery, but it seems strange to me this happened just as I was flashing another ROM, even though I never had any problems with it before. And even though it wouldn't let me boot, I could use recovery and download mode for as long as I liked, and once I did boot with the charger plugged in, the battery wasn't drained but it was around 90%.
Hawaiihemd said:
TBH you made the mistake many beginners make... Going ahead too fast with insufficient knowledge. But never too late to learn that lesson
Since you are getting more and more confused and your phone seems acting strange I recommend starting from scratch an be analytic about it. This will take just a few minutes more but you can be sure where a problem comes from.
First of all: Take 30 minutes to get acquainted with the basics and read through the first thread in my signature (just do it...)
If you can still get in download mode, get your latest stock rom e.g. from sammobile.com and flash it via ODIN. Run stock for a few minutes to see if everything works correctly (test camera, outgoing/incoming calls, mobile data, wifi, gps etc.). If something does not work STOP HERE and report back.
If all is fine go back to ODIN and install latest TWRP (cwm is seriously outdated, can cause lots of errors). Then boot into TWRP and flash whatever custom rom you like. If you install e.g. LOS 14.1 or RR 7.1.1 make sure you install gapps direcly after you flash the rom (do not reboot in between).
Any questions pop up: Shoot. I'm happy to help.
---------- Post added at 04:49 PM ---------- Previous post was at 04:42 PM ----------
Since he already wiped system and data there is no point in a backup of those partitions. Only thing worth saving would be the efs partition.
And you don't need to root stock rom to go further...
If you are unrooted you have to REMOVE the "auto-reboot" checkmark in odin options and then - after the flash of twrp - reboot to recovery (TWRP) manually via holding Power+Home+VolUp for a few seconds.
If you do not uncheck that "auto-reboot" box, an thus allow the unrooted system (stock samsung system) to boot, it will overwrite the new twrp recovery you flashed 2 seconds before...
This is the point where I believe many confusion comes from. If you root first, any recovery you flash will not be overwritten. That is - I think - why many tutorials/tips say you must root stock first before installing a custom rom, which is simply not true.
But you are right that it would help to flash TWRP fist as outlined above, boot into it and make a backup to a microSD card... but of the efs partition (!) as the very first step. Then keep that backup safe and go from there with stock rom, testing for any problems.
So to reiterate the steps I would go:
1) Flash TWRP via odin and boot directly into it
2) Backup efs partition to a microSD card
3) Flash stock rom via ODIN and test
4) Go from there / report baback
Click to expand...
Click to collapse
Still on charger, still 90 percent.

Samsung S9+ 256GB will freeze after root when it goes in to sleep.

It doesn't seems to be working to root an S9+ 256GB DUOS SM-G965F (NEE - BRF8). NEE is Finland but it seems to be used in the whole Nordic.
After doing all the steps everything works but when the phone goes to sleep (the screen turns off and after a minute or two)) it will freeze (someone wrote it was AOD but it doesn't matter if it is running or not).
I also noticed the phone is lagging when using the startup guide, but it disappear after a reboot, but if i leave the phone and letting it fall in to sleep it will freeze and won't wake up again.
The only difference between "SuperSU 2.82-SR5" and "Magisk 16.6" is that with Magisk the phone is lagging at the startup guide and with SuperSU i have no SuperSU icon in apps to run.
And believe me, i have rebooted, but it won't help, no SuperSU icon. When the phone goes to sleep it freezes again.
I install TWRP with ODIN and Wiped the phone and rebooted into recovery, then i did:
1. no-verity-opt-encrypt-6.0-star.zip
2. rebooted into recovery
3. RMM-State_Bypass_Mesa.zip (i have even tryed RMM-State_Bypass_Mesa_v2.zip)
4. SR5-SuperSU-v2.82-SR5-20171001224502.zip (or Magisk 16.6)
5. samsung-antiroot-removal-2.4.zip (i have even tryed samsung-antiroot-removal-4.1.zip)
6. reboot and wait
The phone will always show the "OEM unlock" so i don't need to wait 7 days for it to appear.
Any advice on how i should proceed?
Additional information:
I have now restored the phone back to default (ODIN and the 4 firmware files) and now it won't freeze anymore and "OEM unlock" is still enabled with this text below "Bootloader is already unlocked". Unfortunately the phone isn't rooted now
It seems that if i only flash TWRP i get the same behavior, it freeze after a while after the screen has turn it self off.
Samsung galaxy s9+ 64GB
Hi, first thing I want to say is I registered on this site just now. This is my first reply so please be a bit forgiving if I'm doing something wrong. That said....
I have the exact same problem.
I have the s9+ 64GB SM-G965F.
Here's what I did...
I flashed twrp through Odin which works perfect. On reboot into recovery I formatted data.
Reboot into recovery again and flash no-verity.
Reboot into recovery again and flash RMM.
Without rebooting also flahed superSU and antiroot.
The versions of those files are the exact same as mentioned above and in all the guides....
After all this system reboots and starts up just fine.
All seems okay but when my screen turns off it freezes after a minute or so and the only remedy is a hard reset by holding volume down and power.
It reboots perfectly fine then but the same thing.
When the screen goes of it freezes..
At first I thought it could be the official Samsung firmware so I completely wiped the entire system and flashed resurrection remix rom. All works but when I root this rom the same thing happens. Only this time the root seems to work while flashing but on reboot there's no SuperSU app and it's not rooted according to root checker. Same thing with the freezing though....
So I downloaded the latest official firmware from Samsung, BRF8 I think. Flashed that through odin and all works fine. No freezing. But also no root and no twrp or any custom rom.
So I'm thinking it has to be the rooting that causes it. Tonight I will try to only flash twrp and flash no-verity and RMM, I'll leave the root itself out of it just to see what happens.
I'll post the results back here... If anyone has any ideas it would be appreciated very much!
OH another thing to mention.... I have had oem unlock activated all the time, I checked on each boot and it was always active for me too.....
SHOTOKANKATANA said:
So I'm thinking it has to be the rooting that causes it. Tonight I will try to only flash twrp and flash no-verity and RMM, I'll leave the root itself out of it just to see what happens.
Click to expand...
Click to collapse
If i only flash TWRP i get the same freeze. I used twrp-3.2.1-2-star2lte.
Oh... You beat me to it...
That's no good then, if it's caused by twrp there isn't much we can do I guess. It all starts with twrp.
I'm using the same version as you are.
Maybe we can try a previous version, I don't know what that's going to do though, if it would even be compatible...
I did find a separate official recovery file.
Maybe it's an idea to install the official recovery after acquiring root?
I'm not sure if the file is legit though, I've never done that before. Twrp always worked for me, on all phones I owned.
What's your though on that....?
I wondering if this should be reported to the Github issues log for TWRP? The problem seems to be TWRP.
Maybe we are doing something wrong I'm not sure.
I know I followed multiple guides up to the smallest detail. The result is the same every time. There's 1 thing I noticed though.
I'm using the BRF8 firmware as are you, maybe that's the problem? In the video guides they're mostly on BRE5.
It looks like it's just us with this issue. I can't find any other info on this particular matter...
I've posted this question on another thread.
Here's the link in case you want to follow....
https://forum.xda-developers.com/ga...cross-device-development/twrp-exynos-t3763464
I found the solution. I got it working now...
I installed twrp 3.2.1-1 instead of 3.2.1-2.
Has to be some kind of issue in the latest version...
I used the same install procedure as supposed to.
Only used the other twrp version.
My phone hasn't froze for the last 2 hrs so I'm pretty confident it's working now...
Ahhh cancel that. It just froze again!
Could you see if you can find the tmp/recovery.log?
On the github TWRP ask for it: "/tmp/recovery.log"
and the output of "dmesg" --> "/tmp/recovery.log"
really hoping we could find the fix for this.
The freeze happen because of the real time kernel protection. You need to flash custom kernel before root.
ione2380 said:
The freeze happen because of the real time kernel protection. You need to flash custom kernel before root.
Click to expand...
Click to collapse
LOL, it's right in the twrp instructions, including the phrase"flash custom kernel before root or be screwed"
Thanks you
The problem is solved.
vannsangha said:
Thanks you
The problem is solved.
Click to expand...
Click to collapse
What did you do? I'm still geting freezes with custom rom so i wondering what i'm doing from?
jagflashardinxbox360 said:
It doesn't seems to be working to root an S9+ 256GB DUOS SM-G965F (NEE - BRF8). NEE is Finland but it seems to be used in the whole Nordic.
After doing all the steps everything works but when the phone goes to sleep (the screen turns off and after a minute or two)) it will freeze (someone wrote it was AOD but it doesn't matter if it is running or not).
I also noticed the phone is lagging when using the startup guide, but it disappear after a reboot, but if i leave the phone and letting it fall in to sleep it will freeze and won't wake up again.
The only difference between "SuperSU 2.82-SR5" and "Magisk 16.6" is that with Magisk the phone is lagging at the startup guide and with SuperSU i have no SuperSU icon in apps to run.
And believe me, i have rebooted, but it won't help, no SuperSU icon. When the phone goes to sleep it freezes again.
I install TWRP with ODIN and Wiped the phone and rebooted into recovery, then i did:
1. no-verity-opt-encrypt-6.0-star.zip
2. rebooted into recovery
3. RMM-State_Bypass_Mesa.zip (i have even tryed RMM-State_Bypass_Mesa_v2.zip)
4. SR5-SuperSU-v2.82-SR5-20171001224502.zip (or Magisk 16.6)
5. samsung-antiroot-removal-2.4.zip (i have even tryed samsung-antiroot-removal-4.1.zip)
6. reboot and wait
The phone will always show the "OEM unlock" so i don't need to wait 7 days for it to appear.
Any advice on how i should proceed?
Additional information:
I have now restored the phone back to default (ODIN and the 4 firmware files) and now it won't freeze anymore and "OEM unlock" is still enabled with this text below "Bootloader is already unlocked". Unfortunately the phone isn't rooted now
It seems that if i only flash TWRP i get the same behavior, it freeze after a while after the screen has turn it self off.
Click to expand...
Click to collapse
Hey how do I restore my phone back to default. I have the same problem as you. My phone keeps freezing HELP PLEASE!
Benjamony said:
Hey how do I restore my phone back to default. I have the same problem as you. My phone keeps freezing HELP PLEASE!
Click to expand...
Click to collapse
I suggest you to download the latest Firmware from Sammobile for your Device and flash it with Odin .
Btw i would always check how to Recover my Phone before i do Modefication like this , then its much more easy to go back to Stock if something goes wrong .
Benjamony said:
Hey how do I restore my phone back to default. I have the same problem as you. My phone keeps freezing HELP PLEASE!
Click to expand...
Click to collapse
I'm running DevBase and it is now working perfect. Try to install it. I don't believe you need to go to stock first.
https://forum.xda-developers.com/ga...-development/rom-u1arc5-devbase-v5-2-t3764822
SHOTOKANKATANA said:
Maybe we are doing something wrong I'm not sure.
I know I followed multiple guides up to the smallest detail. The result is the same every time. There's 1 thing I noticed though.
I'm using the BRF8 firmware as are you, maybe that's the problem? In the video guides they're mostly on BRE5.
It looks like it's just us with this issue. I can't find any other info on this particular matter...
I've posted this question on another thread.
Here's the link in case you want to follow....
https://forum.xda-developers.com/ga...cross-device-development/twrp-exynos-t3763464
Click to expand...
Click to collapse
its not the csc. i'm on csf2 and i have the same problem

Need help getting Magisk onto my x829

I got TWRP on it and working, no problem. When I initially rooted it, I used SuperSU, not knowing that would lock me out of some apps that refuse to run on a rooted device. When I uninstalled SuperSU (with the "remove root" button in its settings) and then tried to install Magisk, I kept getting the error that my boot.img is patched.
I'm on EUI 5.8.016S (US Version), and I would greatly appreciate it if someone could get me the (unmodified?) boot.img that Magisk will accept. (I'd ask for one pre-patched for Magisk, but then I wouldn't have the second unmodified copy for Magisk to work with, and I might as well use SuperSU.) Alternately, a Magisk installer that works with the 16S boot.img. I've tried fastboot flashing in the boot.img from every 16S ROM package I could find, with no luck. (Using the command .\fastboot flash boot boot.img.)
Please help? I greatly enjoy the openness that rooting brings, but the fact that some apps lock you out is supremely frustrating.
same happen to me and I wasn't able to solve it. I'm on SuperSu
First a disclaimer: I ditched EUI almost immediately, so I'm going off info I've read around the 'net and my personal experience with other phones.
First step is make a full backup, copy to your PC, Google Drive, or anywhere you trust other than on the phone itself. You may want to backup individual files as well.
Second step gather all the files you need for a clean install of EUI (not using the backup) on your PC. I don't have the files, but a quick search of the forums should get you what you need.
Third step Factory Data Reset. You'll lose everything. Reboot, try setting up as new, you can sign into your Google account, but don't restore apps yet just in case. Get the basics working (WiFi, APN settings, updates to installed apps, etc) then reboot into TWRP. Install the latest non-bleeding edge beta of Magisk (17.2 as of time of writing). Reboot and see if it's working.
Fourth hopefully unnecessary step: If the above steps still fail, destructively wipe the phone. DO NOT follow this step if you're not sure, if there's a nagging voice in the back of your head saying maybe you shouldn't, etc. You could wind up with a bricked phone or a multiple hour headache to get it working again. Restore your backup and hope someone posts a clean boot.img. OK, warning out of the way. Wipe everything except internal. You might need to individually format each type to be certain, formatting them to something other than ext4 then reformatting back to ext4. Reboot through TWRP back to recovery to avoid mounting issues. It will give you the no os installed message. Once back in recovery reinstall EUI, boot and set up as outlined in third step. You'll have to reinstall TWRP if EUI overwrites it with stock recovery.
I hope this helps if no one has a clean boot.img for you. One last piece of advice to everyone: if you think you'll ever install Magisk, skip SuperSU completely. Older versions, before the original developer left completely, were better but they're outdated. For some reason SuperSU currently leaves "pieces" behind, even when uninstalled properly, that often cause problems.

Categories

Resources