Related
Just got my sony version - can say this phone is beast mode. There is a pending update to .257 and someone told me that if I update to this, i will be locked out of any ROMs, including any google edition ROM. Can anyone verify this or comment? I have NOT updated to .257 yet.
Thanks in advance.
It's not that dramatic. If you update now, you'll have to downgrade again to 532 if you want to root. You'll need root and Recovery if you want to flash the GPE ROM when it gets released, so you're only saving yourself one step by not updating to 257 now
LordManhattan said:
It's not that dramatic. If you update now, you'll have to downgrade again to 532 if you want to root. You'll need root and Recovery if you want to flash the GPE ROM when it gets released, so you're only saving yourself one step by not updating to 257 now
Click to expand...
Click to collapse
Lord, good to see you again - remember you from the GT-N7000 forum! So since of course I want root, I shouldn't update to .257. Am I understanding this correctly?
LxMxFxD said:
Lord, good to see you again - remember you from the GT-N7000 forum! So since of course I want root, I shouldn't update to .257. Am I understanding this correctly?
Click to expand...
Click to collapse
Correct. There are currently no way to root 257, so we have to root 532 and update through OTA to keep root on 257.
- Use this tool to root
- Install OTA Root Keeper from the Play Store
- Since you've already received the OTA, you don't need to change the CDA in build.prop (to force the OTA), so...
- Update to 257
- The root app (i'm not sure what app it installs) may be gone, so just install SuperSU from the Play Store if it's not in your app drawer.
And you're done...
... unless you also want to unlock the bootloader:
But let's not get ahead of ourselves. You really want to take a backup of your TA partition. It holds all your unique DRM keys, and X-Reality won't work without it. Once you lose it, you can't get it back, so back it up and upload it to your Dropbox or something. So how do you backup your TA partition?
- Download this tiny tool on your computer and run it.
Are you done? Great! Let's move on to the bootloader:
- Go to Sony's dev site
- Request the unlock key and check your mail.
- Install Flashtool on your computer (follow the guide)
- Click the "lightning" icon
- Follow the steps and enter your unlock key
This may wipe your phone, so backup your stuff
And you're done...
... unless you want to install Recovery and TWRP!
Installing Recovery and TWRP is easy. Just run this tool on your computer.
Now you're all set to flash custom ROMs and all that stuff
Lord,
Thanks again. And for anyone googling this thread, you'll need the android SDK to get these scripts running. The android SDK can be downloaded here:
http://developer.android.com/sdk/index.html
Once downloaded and extracted, add it to your environment path.
Actually... You only need ADB and Fastboot. You can install this Windows installer which will do all the work for you. I'm sorry if you installed the entire SDK I should have included it in the guide.
http://forum.xda-developers.com/showthread.php?t=2317790
Sent from my C6833 using Tapatalk
Firmware link (532)
http://forum.xda-developers.com/showthread.php?t=2463701
If the Hong Kong firmware is flashed would the interface be in english?
If not, does anyone have a link to 532 ftf english/international. Thanks.
CptAwesomeTT said:
Firmware link (532)
http://forum.xda-developers.com/showthread.php?t=2463701
If the Hong Kong firmware is flashed would the interface be in english?
If not, does anyone have a link to 532 ftf english/international. Thanks.
Click to expand...
Click to collapse
You can select your language from set up wizard after installing rom. i too downloaded HK fw.
techpal said:
You can select your language from set up wizard after installing rom. i too downloaded HK fw.
Click to expand...
Click to collapse
Thank you very much.
I'm new to Sony flashing. Recently bought a XZU (6833) after learning about GPe release. I havent gotten it as yet but i've spent the last few days reading up on preparing for flashing AOSP roms. I'm still not 100% solid on the steps as information is all over the XZU section, not really organised too well. A lot of the information is out of date and there are many gaps that left me scratching my head...
As far as I can gather, these are the steps a new XZU non GPe edition owner should undergo if they would like to flash GPe roms(or any other)...please correct me if I am wrong.
1) Use flashtool 0.9 to flash older 532 firmware ftf file. (does not require root and can be done on a bone stock device non GPe device regardless of installed firmware version). Link here http://forum.xda-developers.com/showthread.php?t=2463701. Now I know Hong Kong version is ok. 532 is older than 257. 257 cannot be rooted directly hence the need to downgrade first.
2) Root using the Japanese rootkitZ Link: http://forum.xda-developers.com/showthread.php?t=2559009 (I assume this installs Superuser as there is a Superuser APK in the folder)
3) Install root keeper to retain root privilege. https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper. (temporary, must be kept installed at all times or only after OTA? If not doing OTA to 257, is this even necessary?)
4) Backup TA partition with TA backup tool 9.9 to retain original keys for xreality etc.(must be rooted to do this), If partition isnt backed up, these features would be lost forever. This works only with Sony roms anyway so if you plan on only running GPe roms, this isnt necessary?
5) Unlock bootloader using Sony method. Link:http://unlockbootloader.sonymobile.com/
6) Performing OTA update not manditory if flashing to an AOSP rom anyway? I saw mention of changing some build.prop entries for this to before OTA update shows when you check for updates? Is that necessary? If so, what are the changes?
7) Flash cwm/twrp using xzu recovery 4. Link: http://forum.xda-developers.com/showthread.php?t=2426739. The instructions specify to run superuser.bat or supersu.bat. There is only a run.bat file in the folder and this is what you must run After launching there are several options. (If using the root method from step 2, I assume you have to use the SuperUser (option2) when running the tool).
8) Flash any rom (If going back to a Sony rom, must flash to 532 first to get root. Then update through OTA.
Please can someone edit and/or add details where necessary.
---------- Post added at 03:54 PM ---------- Previous post was at 03:40 PM ----------
LxMxFxD said:
Lord,
Thanks again. And for anyone googling this thread, you'll need the android SDK to get these scripts running. The android SDK can be downloaded here:
http://developer.android.com/sdk/index.html
Once downloaded and extracted, add it to your environment path.
Click to expand...
Click to collapse
To what scripts are you referring? Can you help me by fleshing out my above post?
3) Install root keeper to retain root privilege. https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper. (temporary, must be kept installed at all times or only after OTA? If not doing OTA to 257, is this even necessary?)
Click to expand...
Click to collapse
If you're not planning on keeping the stock ROM, and you want to jump straight to a custom ROM, then no, it's not necessary to install OTA Root Keeper.
4) Backup TA partition with TA backup tool 9.9 to retain original keys for xreality etc.(must be rooted to do this), If partition isnt backed up, these features would be lost forever. This works only with Sony roms anyway so if you plan on only running GPe roms, this isnt necessary?
Click to expand...
Click to collapse
You don't need to back it up, but it's recommended even if you're going to use custom ROMs. What if you're having some issues with your ZU, and you have to send it in for repairs? Sony will notice if the DRM keys aren't there and they'll then know that you've unlocked the bootloader.
6) Performing OTA update not manditory if flashing to an AOSP rom anyway? I saw mention of changing some build.prop entries for this to before OTA update shows when you check for updates? Is that necessary? If so, what are the changes?
Click to expand...
Click to collapse
No, this part isn't necessary if you don't want to.
7) Flash cwm/twrp using xzu recovery 4. Link: http://forum.xda-developers.com/showthread.php?t=2426739. The instructions specify to run superuser.bat or supersu.bat. There is only a run.bat file in the folder and this is what you must run After launching there are several options. (If using the root method from step 2, I assume you have to use the SuperUser (option2) when running the tool).
Click to expand...
Click to collapse
Yes, run the bat-file and choose SuperSU in the terminal.
8) Flash any rom (If going back to a Sony rom, must flash to 532 first to get root. Then update through OTA.
Click to expand...
Click to collapse
Before you start flashing custom ROMs, make a NAND backup of the stock ROM. This way, if you want to go back, all you have to do is to flash a boot.img and restore it, and you'll end up exactly where you left off (with root).
I thank you for your patience I understand what you've said so far.Please bear with me a while longer.
Pertaining to point 7, that xzu recovery uses supersu apk so one would have to choose the supersu option and not superuser right?
Next, looking at the omni rom thread (http://forum.xda-developers.com/showthread.php?t=2548107), I am seeing one single download available in the OP (which is the rom itself), however on the last page (http://forum.xda-developers.com/showpost.php?p=48441587&postcount=273), I am seeing people referencing editing changing biuld.prop and flashing boot.img images.
1) How does one know when it is necessary to do any of the above.
2) I am comfortable with editing build.prop but where is the boot.img come from. How do I know when this needs to be flashed?
3) How do you flash the boot.img files? Through cwm or the flashtool?
4) Some gapps come with recovery? Why is that necessary?
A million thanks.
I gotta say, now having the phone for about 12 hours, this phone is simply impressive. I had a nexus 5 briefly which had the same cpu and ram, but it was not as smooth and speedy as the xperia z ultra. I miss the black contrast of the screen of samsung's super amoled but that is about the only thing I miss. Extremely satisfied with my purchase. First sony device.
And thanks to lord and the rest of this community for making getting root so easy!
LxMxFxD said:
I gotta say, now having the phone for about 12 hours, this phone is simply impressive. I had a nexus 5 briefly which had the same cpu and ram, but it was not as smooth and speedy as the xperia z ultra. I miss the black contrast of the screen of samsung's super amoled but that is about the only thing I miss. Extremely satisfied with my purchase. First sony device.
And thanks to lord and the rest of this community for making getting root so easy!
Click to expand...
Click to collapse
I see you're being taken care of welcome dude, good choice of phone, it's a screamer!
Sent from my C6833 using XDA Premium 4 mobile app
CptAwesomeTT said:
I thank you for your patience I understand what you've said so far.Please bear with me a while longer.
Click to expand...
Click to collapse
No problem. I quite enjoy this (yes, i'm weird)
Pertaining to point 7, that xzu recovery uses supersu apk so one would have to choose the supersu option and not superuser right?
Click to expand...
Click to collapse
That depends on which superuser app you're ending up with after rooting. I haven't used that root tool, so i don't know if it installs SuperSu or something else. If it installs SuperSU, then just choose SuperSU when you're going to install Recovery. Superuser isn't really being used that much these days.
Next, looking at the omni rom thread (http://forum.xda-developers.com/showthread.php?t=2548107), I am seeing one single download available in the OP (which is the rom itself), however on the last page (http://forum.xda-developers.com/showpost.php?p=48441587&postcount=273), I am seeing people referencing editing changing biuld.prop and flashing boot.img images.
Click to expand...
Click to collapse
Yeah, there's currently a newer build being built right now, but that shouldn't stop you from flashing it. The thing with the current build is that data isn't working, so that's why you're seeing the talk about build.prop. By modifying the build.prop you'll get the data working again, so after flashing Omni, you should kick it into Airplane Mode ASAP (thorugh the notification center), use a file explorer to move the new build.prop to /system and overwrite the old one (remember to set the correct permissions to 644 or RW-R-R). After that you reboot and data will work again
- Open QuickIMG on your computer and execute fastboot on your Ultra (Power it off and hold Vol Up and plug your USB in at the same time. A Blue LED will turn on over you screen)
- Flash boot.img and after you're done, boot into Recovery (Power + Vol Up [or power it on as usual and when the Green LED turns on press and hold VOL UP until the light turns purple])
- Wipe everything
- Flash Omni and gapps
- Reboot
2) I am comfortable with editing build.prop but where is the boot.img come from. How do I know when this needs to be flashed?
Click to expand...
Click to collapse
The only times you'll have to flash boot.img is when you're coming from stock ROM and you want to jump over to AOSP (Omni, CM etc.) and when you want to go back to stock. You'll have to do it now when you're going to flash Omni. You don't have to do it when you're updating the ROM, or if you're going to flash CM, PAC or any other AOSP builds.
3) How do you flash the boot.img files? Through cwm or the flashtool?
Click to expand...
Click to collapse
You can use QuickIMG, which is probably the easiest way. After you've flashed boot.img, flash Omni and gapps as usual. Have both of them on your device before you flash the boot.img
4) Some gapps come with recovery? Why is that necessary?
Click to expand...
Click to collapse
That's not right. Kernels come with recovery. Gapps are only Google Apps (Play Store, Maps etc.)
I'm thinking of flashing Omni today myself, so you'll probably read a lot (of cursing) from me around these parts later today :laugh: If you have some other questions, feel free to ask.
LordManhattan said:
No problem. I quite enjoy this (yes, i'm weird)
That depends on which superuser app you're ending up with after rooting. I haven't used that root tool, so i don't know if it installs SuperSu or something else. If it installs SuperSU, then just choose SuperSU when you're going to install Recovery. Superuser isn't really being used that much these days.
Yeah, there's currently a newer build being built right now, but that shouldn't stop you from flashing it. The thing with the current build is that data isn't working, so that's why you're seeing the talk about build.prop. By modifying the build.prop you'll get the data working again, so after flashing Omni, you should kick it into Airplane Mode ASAP (thorugh the notification center), use a file explorer to move the new build.prop to /system and overwrite the old one (remember to set the correct permissions to 644 or RW-R-R). After that you reboot and data will work again
- Open QuickIMG on your computer and execute fastboot on your Ultra (Power it off and hold Vol Up and plug your USB in at the same time. A Blue LED will turn on over you screen)
- Flash boot.img and after you're done, boot into Recovery (Power + Vol Up [or power it on as usual and when the Green LED turns on press and hold VOL UP until the light turns purple])
- Wipe everything
- Flash Omni and gapps
- Reboot
The only times you'll have to flash boot.img is when you're coming from stock ROM and you want to jump over to AOSP (Omni, CM etc.) and when you want to go back to stock. You'll have to do it now when you're going to flash Omni. You don't have to do it when you're updating the ROM, or if you're going to flash CM, PAC or any other AOSP builds.
You can use QuickIMG, which is probably the easiest way. After you've flashed boot.img, flash Omni and gapps as usual. Have both of them on your device before you flash the boot.img
That's not right. Kernels come with recovery. Gapps are only Google Apps (Play Store, Maps etc.)
I'm thinking of flashing Omni today myself, so you'll probably read a lot (of cursing) from me around these parts later today :laugh: If you have some other questions, feel free to ask.
Click to expand...
Click to collapse
Oh man you are so damn helpful!
Ok again I got 95% of what you said. Just to clarify:
Coming from a stock rom, going to an AOSP rom requires you to flash boot.ini prior to flashing the aosp rom. Is it correct to assume that that the boot.img in this case should be extracted from the destination (aosp) rom?
Lastly, other than the rootkitZ Japanese method of rooting an older firmware (532), what is your recommended method of acquiring root?
CptAwesomeTT said:
Oh man you are so damn helpful!
Ok again I got 95% of what you said. Just to clarify:
Coming from a stock rom, going to an AOSP rom requires you to flash boot.ini prior to flashing the aosp rom. Is it correct to assume that that the boot.img in this case should be extracted from the destination (aosp) rom?
Lastly, other than the rootkitZ Japanese method of rooting an older firmware (532), what is your recommended method of acquiring root?
Click to expand...
Click to collapse
Yeah, just do this (i did it myself 30 minutes ago)
- Download the boot.img from here (this one is from the PAC ROM and works great)
- Download QuickIMG from here (and just follow the short guide)
Once you've flashed the boot.img:
- Unplug your Ultra and power it off (in case it powers on, press and hold POWER + VOL UP until you notice some rapid vibrations)
- Now Power it on again and press and hold VOL UP when the LED lights up (green i believe, and it should go purple)
- Once you're in Recovery, flash Omni and gapps (don't forget to wipe data and dalvik (under advance) before rebooting
This one is something i learned myself half an hour ago; pull your SIM out until you've had the chance to replace the build.prop, or else it'll just reboot by itself.
And yes, the japanese rooting tool is the recommended tool. The other ones aren't safe (IMEI collectors)
LordManhattan said:
Yeah, just do this (i did it myself 30 minutes ago)
- Download the boot.img from here (this one is from the PAC ROM and works great)
- Download QuickIMG from here (and just follow the short guide)
Once you've flashed the boot.img:
- Unplug your Ultra and power it off (in case it powers on, press and hold POWER + VOL UP until you notice some rapid vibrations)
- Now Power it on again and press and hold VOL UP when the LED lights up (green i believe, and it should go purple)
- Once you're in Recovery, flash Omni and gapps (don't forget to wipe data and dalvik (under advance) before rebooting
This one is something i learned myself half an hour ago; pull your SIM out until you've had the chance to replace the build.prop, or else it'll just reboot by itself.
And yes, the japanese rooting tool is the recommended tool. The other ones aren't safe (IMEI collectors)
Click to expand...
Click to collapse
You've been so helpful. I think that's all my questions until I actually get the device in hand and start working on it. Thanks a mill.
atm the jap root method is the one I'd use. kingo might be safe and vroot might not be...
Use the one in the zip or download the v4 or v5 boot.img
v4 http://forum.xda-developers.com/showthread.php?t=2426739
v5 http://forum.xda-developers.com/showthread.php?t=2426736
if going to omni i would flash the revolution kernel http://forum.xda-developers.com/showthread.php?t=2548092
No problem!
CptAwesomeTT said:
Firmware link (532)
http://forum.xda-developers.com/showthread.php?t=2463701
If the Hong Kong firmware is flashed would the interface be in english?
If not, does anyone have a link to 532 ftf english/international. Thanks.
Click to expand...
Click to collapse
Link to .532 is gone. Is there another?
Thanks!
This is for both US Cellular Samsung S6 and S6 Edge variant. Thanks also goes to @g.lewarne for his work on Unikernel as a couple of their ramdisk/kernel commits were needed to get this going. Also, thanks to @datajosh for this template And @bpdev for testing the 925R4 version...
This will trip KNOX. It will. Trip. KNOX. IF YOU HAVE NOT TRIPPED KNOX YET - THIS WILL TRIP IT. ALSO - you CANNOT downgrade after you take the OTA so be sure you want it.
I hope that's clear enough?
Instructions:
After you've booted into OF7, go to Settings > About device and tap Build number 7 times to enable Developer Mode.
Go back and select Developer options and turn on OEM unlocking
Reboot in to download mode (Power + Home + Volume Down)
Use ODIN to flash 925R4root.tar or 920R4root.tar (depending on your device)
After your phone boots you will now have root!
If you notice constant messages about security issues because of KNOX and the kernel being permissive. To get rid of these, open Titanium Backup (or your personal favorite app freezing app) and freeze SecurityLogAgent.
Downloads
925R4 - http://1drv.ms/1HeDWXO
925R4 Source
920R4 - http://1drv.ms/1NUVJ8B This is untested...I did not have a tester for this version....
920R4 Source
The 925R4 version may or may not work with the Sprint 925P variant...no working data confirmed!
ENJOY!
Man I wish we could just find a damn exploit already lol gone this long without tripping Knox. And with the fact that I've received the "Fingerprint scanner has encountered an error, use your backup password." error 4-5x already I'm worried about tripping Knox, although you'd think they'd still fix that considering just rooting shouldn't break the scanner lol.
So this requires me to stay on that kernel huh? I couldn't go back to stock kernel huh?
cpfeifer said:
Man I wish we could just find a damn exploit already lol gone this long without tripping Knox. And with the fact that I've received the "Fingerprint scanner has encountered an error, use your backup password." error 4-5x already I'm worried about tripping Knox, although you'd think they'd still fix that considering just rooting shouldn't break the scanner lol.
So this requires me to stay on that kernel huh? I couldn't go back to stock kernel huh?
Click to expand...
Click to collapse
You could go back to the stock kernel, but you would loose root. Also as stated above you would trip knox.
someone on a sprint s5 edge said the only thing they noticed didnt work was data..just posting for them since they under 10 post..so thats awesome! if we could get data goin..we can have root!!
---------- Post added at 03:29 PM ---------- Previous post was at 03:17 PM ----------
this kernel has working data on the edge...if you could port the data stuff in yours it should be fine http://forum.xda-developers.com/spr...t/5-1-1-stock-of7-kernel-root-7-4-15-t3150350
Does this method then require flashing a custom recovery then SuperSU.zip (or CF Auto Root)? Just curious because all that's in the .rar is a boot.img and some are having issues with following the method and not having root immediately.
borxnx said:
Does this method then require flashing a custom recovery then SuperSU.zip (or CF Auto Root)? Just curious because all that's in the .rar is a boot.img and some are having issues with following the method and not having root immediately.
Click to expand...
Click to collapse
It should be flashed using ODIN...I believe I updated the link in the OP to fix that issue since I derp'd...
Sent from my SM-G920P using Tapatalk
Flashed on a 920r4, but it is not rooted.
Funny enough, I get knox warnings about threats and stuff. But when I check with root checker, I don't have root.
sintro said:
Flashed on a 920r4, but it is not rooted.
Funny enough, I get knox warnings about threats and stuff. But when I check with root checker, I don't have root.
Click to expand...
Click to collapse
Perhaps you still have to install SuperSU or another super user app.
Sent from my SM-G925R4 using Tapatalk
cpfeifer said:
Perhaps you still have to install SuperSU or another super user app.
Sent from my SM-G925R4 using Tapatalk
Click to expand...
Click to collapse
I reflashed back to stock, then installed supersu. Then opened it up, obviously it said "supersu binary not installed". Next, I flashed this kernel and once booted up supersu still repeats the previous message. In addition, root checker shows that phone is not rooted.
The only thing in the .tar file, for 920r4 at least because that's all I downloaded, is a modified kernel. Nothing about SuperSU or its binaries. This method alone does not root. This merely installs a modified SELinux permissive stock kernel. More steps are necessary to obtain root. You must flash either CF Auto Root or a custom kernel + SuperSU.zip.
Bump? Nobody? OP, amirite? Because the method you describe, and thank you so much for the SELinux permissive kernel, does not complete all of the steps between stock and fully rooted.
borxnx said:
Bump? Nobody? OP, amirite? Because the method you describe, and thank you so much for the SELinux permissive kernel, does not complete all of the steps between stock and fully rooted.
Click to expand...
Click to collapse
920R4 http://1drv.ms/1HzSj73 try this...
I've redone the ramdisk and use the exact same files on my 920P...and kept the carrier parts for US Cellular...
Let me know if this works...
djvoleur said:
920R4 http://1drv.ms/1HzSj73 try this...
I've redone the ramdisk and use the exact same files on my 920P...and kept the carrier parts for US Cellular...
Let me know if this works...
Click to expand...
Click to collapse
Thank you for redoing the ramdisk.
Will try out and let you know.
Anyone experiencing issues with 925r4? I have service but see no signal bars no matter where I go.
https://youtu.be/y7EpSirtf_E
djvoleur said:
920R4 http://1drv.ms/1HzSj73 try this...
I've redone the ramdisk and use the exact same files on my 920P...and kept the carrier parts for US Cellular...
Let me know if this works...
Click to expand...
Click to collapse
This does indeed work. Thank you so much!
Edit...Added instructions I used to complete the root process.
First of all, I wanted to thank the OP of this thread for posting this guide and getting me headed in the right direction.
Credit to @djvoleur
I just wanted to share the method I used to root my USC Galaxy S6 with the Android 5.1.1 update. You will notice that the instructions are similar in the beginning. I added the extra steps that I used to complete the root process. I do not know if this method works for the Edge version.
As the OP states: This will trip knox. Personally, it doesn’t matter to me. I am too impatient and too much of a flash-a-holic to wait for a method that doesn’t trip knox.
Also, I am not a dev and I am unable to answer any questions other than how I obtained root. I am not responsible for any damage that might happen to your phone. Follow this procedure at your own risk.
Having stated these disclaimers, it really isn’t very difficult to implement. I’ve done it twice and both times worked perfectly.
Files you will need for flashing in Odin:
Odin 3.10.7 found here: http://tinyurl.com/puyq4v9
Rooted kernel 920R4root.tar found in the OP.
TWRP 2.7.8.0 (Sprint version, but I can confirm it worked for me. YMMV.) Here: http://tinyurl.com/phvrkaf
Files for flashing in TWRP:
Updated V-Kernel 920R4-071615.zip found here: http://tinyurl.com/o2h8rv4
Super SU v2.49 (beta) found here: http://tinyurl.com/or6mmqr
Now, PLEASE read these instructions before starting so that you will have a good understanding of what to do. After reading, you may begin.
Don’t forget to put the files for flashing in TWRP on your SD card (phone) before beginning this process.
After you've booted into OF7, go to Settings > About device and tap Build number 7 times to enable Developer Mode.
Go back and select Developer options and turn on OEM unlocking
Boot into download mode (Power + Home + Volume Down)
Use ODIN to flash 920R4root.tar
Use ODIN to flash TWRP and make sure that reboot is NOT checked in options.
Unplug the phone and hold the Power + Volume Down key to reboot. When the screen goes blank, quickly hold the Power + Home + Volume Up key to boot into TWRP. If it doesn’t boot to TWRP, you may have to start over.
In TWRP flash the updated V-Kernel file first, then the Super SU file, and then reboot.
After your phone boots you will now have root!
If you notice constant messages about security issues because of KNOX and the kernel being permissive. To get rid of these, open Titanium Backup (or your personal favorite app freezing app) and freeze SecurityLogAgent. (Worked for me.)
You now should be able to install Chainfire's Super SU app from the Play Store, and you can also use Root Checker to confirm you are rooted.
Good Luck!
Would this work on G920R7... J4 (rather than OF7) 5.1.1? That's what I have.
I see there is a PC1 update available also for my G920R7 which is 6.0 marshmallow.
Hard to believe I've had this device for a year with no root... Anyone can help me get this rooted? Thanks!
so after installing the intial kernel that did not work I scrolled through and saw the updated version...you should probably update the link for the untested r4 to the working version later posted...
my problem is that Im unable to load in anything but download mode due to kernel not seandroid enforcing basically not enabling me to load into recovery mode so I need the zipped version of the kernel to install via odin in download mode if possible otherwise im waiting on a 2 hour download of the stock kernal to install
i just picked up a us cellular note 5 (SM-N920R4 on OJ5)
its trying to download and update to a new firmware so i turned off wifi and that appears to stop it but i cant do any of the gazillion updates from play store like we normally do after you receive a new phone or do a factory data reset.
please advise what i need to do since im already on OJ5 and can not connect to wifi as it will auto install whatever update its trying to download.
thanks again
en11gma said:
i just picked up a us cellular note 5 (SM-N920R4 on OJ5)
its trying to download and update to a new firmware so i turned off wifi and that appears to stop it but i cant do any of the gazillion updates from play store like we normally do after you receive a new phone or do a factory data reset.
please advise what i need to do since im already on OJ5 and can not connect to wifi as it will auto install whatever update its trying to download.
thanks again
Click to expand...
Click to collapse
Use TB to remove the update apps - green phone icons in TB. That's how it always gets stopped on any samsung.
Hello everyone,
As a first time noob trying to root my Sony Xperia Z5 Compact (E5803), I lost my DRM keys since I made no backup. Now I am searching for a way to get the functionality of the camera, bluetooth, x-reality, and more back. I currently still have an unlocked bootloader and am running stock Android Nougat (32.3.A.0.376). Can someone please tell me how I can restore the DRM keys and the TA partition? I don't need root anymore, and I have had no luck making TWRP recovery work.
Please, I just desperately want my phone to work as it did before.
Thank you very much in advance!
Gdhgeorge1 said:
Hello everyone,
As a first time noob trying to root my Sony Xperia Z5 Compact (E5803), I lost my DRM keys since I made no backup. Now I am searching for a way to get the functionality of the camera, bluetooth, x-reality, and more back. I currently still have an unlocked bootloader and am running stock Android Nougat (32.3.A.0.376). Can someone please tell me how I can restore the DRM keys and the TA partition? I don't need root anymore, and I have had no luck making TWRP recovery work.
Please, I just desperately want my phone to work as it did before.
Thank you very much in advance!
Click to expand...
Click to collapse
If your DMR Keys are deleted and you have no backup of them, than there are gone, it is not possible to get them back.
You can use a custom kernel that 'tells' the DRM keys are there, that fixes your issue.
Somewhere there is an instruction how to build your own kernel (super easy) with DRM fix. I couldn't find it so good luck looking for it
Horst the Animal said:
If your DMR Keys are deleted and you have no backup of them, than there are gone, it is not possible to get them back.
Click to expand...
Click to collapse
Thanks for replying! Yeah, I assumed that would be the case. But I found this post that says I can flash a "drmrestore" zip package so I can simulate that the keys are still there: https://forum.xda-developers.com/crossdevice-dev/sony/xperia-z1-z2-z3-series-devices-drm-t2930672
The thing is, in order to flash it, I need TWRP recovery, right? I have been unable to successfully install TWRP. Is there an easy way to install it?
Thanks again!
harry_turtle said:
You can use a custom kernel that 'tells' the DRM keys are there, that fixes your issue.
Somewhere there is an instruction how to build your own kernel (super easy) with DRM fix. I couldn't find it so good luck looking for it
Click to expand...
Click to collapse
Thanks a lot for replying! If I find this post where I can create my own kernel, I will have to unlock the bootloader again and flash the new custom firmware using flashtool, right?
Also, will I have to downgrade to Lollipop, since Nougat is pretty new on Sony phones and there's no drm fix for that?
Thanks again!
My advice to you in your situation.
dont worry about building your own kernel. I have attached the Androplus Kernel for z5c, nougat build 376 - flash this kernel onto your phone.
You have adb right?
1. unzip the attachment on this post to get the boot.img file (the androplus kernal for your current build)
2. Turn off your phone, and unplug from USB
3. Go into fastboot mode - Hold Volume Up and plug in USB cable, notice LED turns blue.
4. Run the commant "fastboot flash boot boot.img" (takes about 2 seconds to complete)
Boot your phone, go into Settings -> Display -> Image enhancement . Then check X-Reality is working by toogling it off and on and see if the image of the tomatos changes colors. If the tomatoes change color, then congratulations - you dont have to worry about your lost DRM keys! You have full functionality!
Im pretty sure everything will be ok after this. It's a great kernel - good battery and all the functionality is there.
You do not need TWRP, you do not need to downgrade to lollipop or marshmellow or anything like that.
Will try!
Dean F said:
My advice to you in your situation.
dont worry about building your own kernel. I have attached the Androplus Kernel for z5c, nougat build 376 - flash this kernel onto your phone.
You have adb right?
1. unzip the attachment on this post to get the boot.img file (the androplus kernal for your current build)
2. Turn off your phone, and unplug from USB
3. Go into fastboot mode - Hold Volume Up and plug in USB cable, notice LED turns blue.
4. Run the commant "fastboot flash boot boot.img" (takes about 2 seconds to complete)
Boot your phone, go into Settings -> Display -> Image enhancement . Then check X-Reality is working by toogling it off and on and see if the image of the tomatos changes colors. If the tomatoes change color, then congratulations - you dont have to worry about your lost DRM keys! You have full functionality!
Im pretty sure everything will be ok after this. It's a great kernel - good battery and all the functionality is there.
You do not need TWRP, you do not need to downgrade to lollipop or marshmellow or anything like that.
Click to expand...
Click to collapse
Thank you so, so much! I will try this and report back with my results!
Dean F said:
My advice to you in your situation.
dont worry about building your own kernel. I have attached the Androplus Kernel for z5c, nougat build 376 - flash this kernel onto your phone.
You have adb right?
1. unzip the attachment on this post to get the boot.img file (the androplus kernal for your current build)
2. Turn off your phone, and unplug from USB
3. Go into fastboot mode - Hold Volume Up and plug in USB cable, notice LED turns blue.
4. Run the commant "fastboot flash boot boot.img" (takes about 2 seconds to complete)
Boot your phone, go into Settings -> Display -> Image enhancement . Then check X-Reality is working by toogling it off and on and see if the image of the tomatos changes colors. If the tomatoes change color, then congratulations - you dont have to worry about your lost DRM keys! You have full functionality!
Im pretty sure everything will be ok after this. It's a great kernel - good battery and all the functionality is there.
You do not need TWRP, you do not need to downgrade to lollipop or marshmellow or anything like that.
Click to expand...
Click to collapse
I apologize for replying with my report this late.
It turns out I re-locked my bootloader in the process when I flashed Android Nougat, since I had bricked it temporarily. To do the procedure you mentioned above, I need to have it un-locked, correct?
If that is the case, when I try to unlock the bootloader, I cannot access fastboot because whenever I press VOL UP key with adb, the light flashes blue and then red and then boots into the OS normally. Same with flashmode (the light turns green, and then red, finally booting into the OS).
Does anyone have a solution for this, please?
Thank you very much!
Go into Developer settings and make sure the allow OEM unlocking option is enabled. Then follow sony's unlocking instructions. Once thats done, try again.
Dean F said:
Go into Developer settings and make sure the allow OEM unlocking option is enabled. Then follow sony's unlocking instructions. Once thats done, try again.
Click to expand...
Click to collapse
Thank you for your reply, Dean F.
OEM unlocking option and USB debugging were already enabled. It should have technically been working by now. Could it have something to do with some drivers I have to re-install?
It worked!!
Dean F said:
Go into Developer settings and make sure the allow OEM unlocking option is enabled. Then follow sony's unlocking instructions. Once thats done, try again.
Click to expand...
Click to collapse
UPDATE:
I was able to bypass the blue-red notification light problem and was able to unlock the bootloader and flash the boot.img file, so camera and X-Reality are working normally now!! Thank you so, so much for your help!
I have one question, please. Will I lose the camera functionality and X-Reality, etc., if I re-lock the bootloader?
Also, in the future, if there are any updates to the Nougat OS, will they break these functions once again?
Thanks again!
Gdhgeorge1 said:
UPDATE:
I was able to bypass the blue-red notification light problem and was able to unlock the bootloader and flash the boot.img file, so camera and X-Reality are working normally now!! Thank you so, so much for your help!
I have one question, please. Will I lose the camera functionality and X-Reality, etc., if I re-lock the bootloader?
Also, in the future, if there are any updates to the Nougat OS, will they break these functions once again?
Thanks again!
Click to expand...
Click to collapse
You can lock the bootloader again, however I dont think there is any point in doing that. You should not use auto updates anymore, or yes, it will break those functions. Auto updates technically never work on any rooted phone. If you want to updateto a newer build you will need download it and flash it with xperifirm/flashtool (which is a good reason to keep your bootloader permanently unlocked). You've already lost your DRM keys, so I think your phone should remain a rooted model for the rest of its life. Really no point in going back to stock with no keys.
Personally, I am also running 376 build, with the androplus kernel, debloated (i debloated with another kernel, once finished, then used androplus). I removed even the software update and support apps. I applied the volume fix (if you are having the low volime issue?). Considering this phone is running Android 7.0, already has the best kernel (androplus), i think its safe to leave the phone like this for the remainder of its life. I dont really care about any minor upgrates to nougat, and we are not getting Android 8.0. so I recommend if everything is working now, just leave the phone in its current state. will save you a lot of stress.
Dean F said:
You can lock the bootloader again, however I dont think there is any point in doing that. You should not use auto updates anymore, or yes, it will break those functions. Auto updates technically never work on any rooted phone. If you want to updateto a newer build you will need download it and flash it with xperifirm/flashtool (which is a good reason to keep your bootloader permanently unlocked). You've already lost your DRM keys, so I think your phone should remain a rooted model for the rest of its life. Really no point in going back to stock with no keys.
Personally, I am also running 376 build, with the androplus kernel, debloated (i debloated with another kernel, once finished, then used androplus). I removed even the software update and support apps. I applied the volume fix (if you are having the low volime issue?). Considering this phone is running Android 7.0, already has the best kernel (androplus), i think its safe to leave the phone like this for the remainder of its life. I dont really care about any minor upgrates to nougat, and we are not getting Android 8.0. so I recommend if everything is working now, just leave the phone in its current state. will save you a lot of stress.
Click to expand...
Click to collapse
Thanks for replying. My phone is actually not rooted, I just checked with the Root Checker app from the Play Store. Besides, there is no SuperSu or Superuser apps installed. Additionally, in the Xperia Service Menu, it says "Bootloader unlock allowed: Yes," so I guess this means the bootloader was re-locked somehow when I flashed the boot file.
Form the looks of things, I'm back where I started before losing the DRM keys, minus the stock Sony music equalizer (in which, even though the controls can be changed, the sound itself doesn't change). I'm guessing there's no fix for that, right?
Anyway, I checked the volume and it sounds fine, just like it did before.
Thank you so much for your assistance, Dean F!
Gdhgeorge1 said:
Thanks for replying. My phone is actually not rooted, I just checked with the Root Checker app from the Play Store. Besides, there is no SuperSu or Superuser apps installed. Additionally, in the Xperia Service Menu, it says "Bootloader unlock allowed: Yes," so I guess this means the bootloader was re-locked somehow when I flashed the boot file.
Form the looks of things, I'm back where I started before losing the DRM keys, minus the stock Sony music equalizer (in which, even though the controls can be changed, the sound itself doesn't change). I'm guessing there's no fix for that, right?
Anyway, I checked the volume and it sounds fine, just like it did before.
Thank you so much for your assistance, Dean F!
Click to expand...
Click to collapse
Correct your phone is not rooted because the androplus kernel is not a rooted kernel. It is simply a custom kernel with some optimizations, and includes the DRM fix. If you want to do some maintenance while rooted, flash a rooted kernel (i will attach one to this post for you). Once rooted do what you need to do - like debloat,remove apps with Titanium Backup, and once you are finished - flash the Androplus kernel again. The idea is just to give you root for a tempory peroid to customize your device, before going back to a safer, optimized, non rooted state for every day usage.
If you have androplus kernel, i don't believe it is possible to be in a state where DRM functions are not working, as it contains the kernel DRM fix.
Dean F said:
Correct your phone is not rooted because the androplus kernel is not a rooted kernel. It is simply a custom kernel with some optimizations, and includes the DRM fix. If you want to do some maintenance while rooted, flash a rooted kernel (i will attach one to this post for you). Once rooted do what you need to do - like debloat,remove apps with Titanium Backup, and once you are finished - flash the Androplus kernel again. The idea is just to give you root for a tempory peroid to customize your device, before going back to a safer, optimized, non rooted state for every day usage.
If you have androplus kernel, i don't believe it is possible to be in a state where DRM functions are not working, as it contains the kernel DRM fix.
Click to expand...
Click to collapse
Excellent, I see now, thanks!
Well, what I wanted before starting the entire process was a permanent root solution, one that would allow me to access features like Root Explorer on ES File Explorer, or extra features in Link2SD and such, when the opportunity arose. That is what I did with all my previous smartphones, even a Sony Z1 Compact, but this has been the hardest phone to root I've ever handled.
After all the trial and error I've faced, I will take your good advice and leave it as is for now. In the future, I will flash the rooted kernel when I need to use those functions, and use the androplus kernel you had sent me previously to get it back to normal.
Thank a bunch again for all your help, Dean F. You revived my phone, so to speak!
Cheers!
Hi everyone,
Got my RedMagic 7 today. Rooting was straightforward with Magisk 23. I have the patched boot.img in the Android Device Database - http://NewAndroidBook.com/ddb - in case anyone wants. Apparently, "Fastboot boot ..." won't be recognized, so you'd need "fastboot flash" of this image.
(Note that rooting voids warranty, etc, and also might interfere with fingerprint scanner and/or TrustZone applets)
morpheus______ said:
Hi everyone,
Got my RedMagic 7 today. Rooting was straightforward with Magisk 23. I have the patched boot.img in the Android Device Database - http://NewAndroidBook.com/ddb - in case anyone wants. Apparently, "Fastboot boot ..." won't be recognized, so you'd need "fastboot flash" of this image.
(Note that rooting voids warranty, etc, and also might interfere with fingerprint scanner and/or TrustZone applets)
Click to expand...
Click to collapse
Hello! Thx for posting this info. I have a few of questions. Can you post a simple set of instructions on how to apply this root? I have never rooted a Nubia device before but I want to root this. Will the flashing of the boot image require the bootloader unlock? Might you know if the viper4Android is working from the modules install in magisk? Thx in advance for any info you may be able to provide!
RngrYogi said:
Hello! Thx for posting this info. I have a few of questions. Can you post a simple set of instructions on how to apply this root? I have never rooted a Nubia device before but I want to root this. Will the flashing of the boot image require the bootloader unlock? Might you know if the viper4Android is working from the modules install in magisk? Thx in advance for any info you may be able to provide!
Click to expand...
Click to collapse
Also using your method would it require a user data wipe?
RngrYogi said:
Also using your method would it require a user data wipe?
Click to expand...
Click to collapse
yes, of course. it's like any standard boot loader unlocked. Which is why you do it first thing when you get the device.
Edit: I didn't see the question how to apply it -
just OEM unlock the device, and then
adb reboot bootloader
(wait for it too boot to boot loader)
fastboot flashing unlock
(accept unlocking voiding warranty, etc by pressing volume down and power)
fastboot flash boot <the boot.img>
Note that they don't recognize "fastboot boot" , which is my favorite way of rooting since it leaves the original image intact - and thus flashing is irreversible unless you get the stock OTA at a later time and flash it over. But this will not bring back the warranty and warnings.
morpheus______ said:
Hi everyone,
Got my RedMagic 7 today. Rooting was straightforward with Magisk 23. I have the patched boot.img in the Android Device Database - http://NewAndroidBook.com/ddb - in case anyone wants. Apparently, "Fastboot boot ..." won't be recognized, so you'd need "fastboot flash" of this image.
(Note that rooting voids warranty, etc, and also might interfere with fingerprint scanner and/or TrustZone applets)
Click to expand...
Click to collapse
greetings bro thanks for sharing the vbmeta.img file? didn't you use it?
few questions:
1. were did you find the stock firmware to pull the clean boot.img? Can you link it, I would like to have a backup if anything goes wrong
2. Is the patched boot.img for the North American Version?
So to lpedrot: Didn't need a vbmeta.
To superrama: Since it's the kernel, the CN/US/etc versions don't matter. That's handled at a much higher level of Android build, which is user mode. So same boot.img can be used anywhere (which btw is true in all cases - boot.img s only have kernel + Ramdisk anyway)
1. I found the original by looking for NX679 OTA . It was a rather large OTA payload.bin, which I used my imjtool to unpack the boot.img from. Don't have the link handy now, but I can probably dig up the payload.bin and put it in a link since I have it stored somewhere.
morpheus______ said:
So to lpedrot: Didn't need a vbmeta.
To superrama: Since it's the kernel, the CN/US/etc versions don't matter. That's handled at a much higher level of Android build, which is user mode. So same boot.img can be used anywhere (which btw is true in all cases - boot.img s only have kernel + Ramdisk anyway)
1. I found the original by looking for NX679 OTA . It was a rather large OTA payload.bin, which I used my imjtool to unpack the boot.img from. Don't have the link handy now, but I can probably dig up the payload.bin and put it in a link since I have it stored somewhere.
Click to expand...
Click to collapse
nice, thanks for the quick reply
morpheus______ said:
Hi everyone,
Got my RedMagic 7 today. Rooting was straightforward with Magisk 23. I have the patched boot.img in the Android Device Database - http://NewAndroidBook.com/ddb - in case anyone wants. Apparently, "Fastboot boot ..." won't be recognized, so you'd need "fastboot flash" of this image.
(Note that rooting voids warranty, etc, and also might interfere with fingerprint scanner and/or TrustZone applets)
Click to expand...
Click to collapse
On which rom you use it? Aparently its taken out from a Ianuary rom, latest being v2.32 afaik
Just whichever random firmware image I found. But you're overlooking one major thing which is - the kernel barely, if at all, changes between firmware versions . You can use this book image with any other firmware image of any date, earlier or later, and there's no reason why it wouldn't work. The Android OTA images are user mode, this is just the kernel + Ramdisk - and so are largely independent of each other. Only exception would be if there's some kernel vulnerability in that particular version of the kernel, which as far as we know now - there isn't.
Hi, thanks for the guide. I did the steps to unlock bootloader and do flash your provided boot.img.
They both worked successfully but not sure if the boot img did anything.
I have the chinese phone and I want to convert it to global. Going to the settings and choosing the local update file provided by the official website doesn't work.
Any tips?
LeonFresh said:
Hi, thanks for the guide. I did the steps to unlock bootloader and do flash your provided boot.img.
They both worked successfully but not sure if the boot img did anything.
I have the chinese phone and I want to convert it to global. Going to the settings and choosing the local update file provided by the official website doesn't work.
Any tips?
Click to expand...
Click to collapse
”we” have a telegram channel for RM7 users, join since most of them don't use XDA anymore and you'll get faster help here
D1stRU3T0R said:
”we” have a telegram channel for RM7 users, join since most of them don't use XDA anymore and you'll get faster help here
Click to expand...
Click to collapse
Rooting != Image locale change. To do an image locale change you need to get the device image for whichever locale you want (if you can find it) and then apply the usual Magisk method.
D1stRU3T0R said:
”we” have a telegram channel for RM7 users, join since most of them don't use XDA anymore and you'll get faster help here
Click to expand...
Click to collapse
Hi I just joined the TG but got banned any chance of unbanning me?
User is Indiana_Gems on TG I'm looking to change my RM7 CN to global
morpheus______ said:
Rooting != Image locale change. To do an image locale change you need to get the device image for whichever locale you want (if you can find it) and then apply the usual Magisk method.
Click to expand...
Click to collapse
Thanks, I thought the two was related. I can't find any of the img files, which is why I'm stuck I guess. For older versions of the phone like Red Magic 5 they exist.
If they don't exist, is there a process to make one? Or do I have to wait
LeonFresh said:
Thanks, I thought the two was related. I can't find any of the img files, which is why I'm stuck I guess. For older versions of the phone like Red Magic 5 they exist.
If they don't exist, is there a process to make one? Or do I have to wait
Click to expand...
Click to collapse
There is a long and painful process to make one, and it's not guaranteed to work. I'll explain:
If a given vendor (in our case, Nubia, but this applies to others as well) adheres to Google's specification their /system partition should effectively be identical to that of all other Android devices (of same version). The vendor is supposed to put the BSP or ODM specific files in /system_ext, /vendor, /product and /odm.
The language, in this case, is just a locale setting, and several other "overlay" files (which supersede those in /system) laid out in the vendor/odm/product partitions. The problem here is that all these partitions will A) differ by vendor B) be read/only and DM-verity enabled.
Thus, it would take going over the vendor's overlay files and locale settings, and changing every one. Impractical.
You're better off just going in the language settings and setting en_US, and working from there. Even on non-rooted device, you can always adb install any app you want.
morpheus______ said:
There is a long and painful process to make one, and it's not guaranteed to work. I'll explain:
If a given vendor (in our case, Nubia, but this applies to others as well) adheres to Google's specification their /system partition should effectively be identical to that of all other Android devices (of same version). The vendor is supposed to put the BSP or ODM specific files in /system_ext, /vendor, /product and /odm.
The language, in this case, is just a locale setting, and several other "overlay" files (which supersede those in /system) laid out in the vendor/odm/product partitions. The problem here is that all these partitions will A) differ by vendor B) be read/only and DM-verity enabled.
Thus, it would take going over the vendor's overlay files and locale settings, and changing every one. Impractical.
You're better off just going in the language settings and setting en_US, and working from there. Even on non-rooted device, you can always adb install any app you want.
Click to expand...
Click to collapse
morpheus______ said:
There is a long and painful process to make one, and it's not guaranteed to work. I'll explain:
If a given vendor (in our case, Nubia, but this applies to others as well) adheres to Google's specification their /system partition should effectively be identical to that of all other Android devices (of same version). The vendor is supposed to put the BSP or ODM specific files in /system_ext, /vendor, /product and /odm.
The language, in this case, is just a locale setting, and several other "overlay" files (which supersede those in /system) laid out in the vendor/odm/product partitions. The problem here is that all these partitions will A) differ by vendor B) be read/only and DM-verity enabled.
Thus, it would take going over the vendor's overlay files and locale settings, and changing every one. Impractical.
You're better off just going in the language settings and setting en_US, and working from there. Even on non-rooted device, you can always adb install any app you want.
Click to expand...
Click to collapse
Thanks for the details!
Is it impractical in terms of technical perspective , or is it just tedious to do? And do you think it will be released in future?
The reason I want to switch is that there are bugs mostly related to the google assistant. It resetting my settings like on default voice assistant app. It doesn't have ok google detection, sometimes doesn't open at all.
If that can be fixed maybe I can stay on CN rom, but honestly there's a lot of random bugs, it not only resets default apps for assistant but other apps too like fluid navigation gestures (FNG) app.
LeonFresh said:
Thanks for the details!
Is it impractical in terms of technical perspective , or is it just tedious to do? And do you think it will be released in future?
The reason I want to switch is that there are bugs mostly related to the google assistant. It resetting my settings like on default voice assistant app. It doesn't have ok google detection, sometimes doesn't open at all.
If that can be fixed maybe I can stay on CN rom, but honestly there's a lot of random bugs, it not only resets default apps for assistant but other apps too like fluid navigation gestures (FNG) app.
Click to expand...
Click to collapse
Hello. Have you found a solution to the problem? I also do not flash, says the version for the firmware is not suitable.
Morrovoker said:
Hello. Have you found a solution to the problem? I also do not flash, says the version for the firmware is not suitable.
Click to expand...
Click to collapse
Not yet, I guess we just have to wait
LeonFresh said:
Not yet, I guess we just have to wait
Click to expand...
Click to collapse
any news yet i wanna switch from global to cn lol
Im considering getting one but i have few questions:
1. Is/will it be possible to lock the bootloader? (Not relock, just lock aka return it to original?)
2. Is it possible to have paralel apps? Like Island app but no root needed?
3. Is it possible to block bloat installing every update/disable the wizard? (Again, no root)
4. Can you hide/disable every unwanted app or via adb?
5. Hows watching movies on it?
6. Will custom roms exist?
7. Apparently Samsung doesnt use A/B. Is this true?
Korothi said:
Im considering getting one but i have few questions:
1. Is/will it be possible to lock the bootloader? (Not relock, just lock aka return it to original?)
Click to expand...
Click to collapse
Please clarify on what you're asking. The bootloader comes locked by default. On unlockable devices, it is always possible to relock the bootloader, but you must perform a clean flash of the factory firmware before doing so. Attempting to lock the bootloader on custom firmware will render your device inoperable.
Korothi said:
2. Is it possible to have paralel apps? Like Island app but no root needed?
Click to expand...
Click to collapse
What do you mean by "parallel apps"?
Korothi said:
3. Is it possible to block bloat installing every update/disable the wizard? (Again, no root)
Click to expand...
Click to collapse
No. Root is required to remove bloat.
Korothi said:
4. Can you hide/disable every unwanted app or via adb?
Click to expand...
Click to collapse
Not without root.
Korothi said:
5. Hows watching movies on it?
Click to expand...
Click to collapse
This is a flagship device; I would expect movies would be just fine.
Korothi said:
6. Will custom roms exist?
Click to expand...
Click to collapse
Eventually.
Korothi said:
7. Apparently Samsung doesnt use A/B. Is this true?
Click to expand...
Click to collapse
Yes. Samsung has continued to use the bespoke recovery model. This makes Samsung devices slightly more complicated to flash, but TWRP helps make it easier.
I managed to have a duplicated app (Revolut) setting up the personal area
For social like WhatsApp this feature is integrated and easier.
V0latyle said:
Please clarify on what you're asking. The bootloader comes locked by default. On unlockable devices, it is always possible to relock the bootloader, but you must perform a clean flash of the factory firmware before doing so. Attempting to lock the bootloader on custom firmware will render your device inoperable.
Click to expand...
Click to collapse
Korothi said:
Im considering getting one but i have few questions:
1. Is/will it be possible to lock the bootloader? (Not relock, just lock aka return it to original?)
Click to expand...
Click to collapse
Worth to mention, Once you unlock bootloader and flash custom binary, you can relock bootloader later after flashing stock firmware first but still it leaves footprint and certain features will be stopped working forever. e.g Samsung Pass and Pay and may be more.
V0latyle said:
No. Root is required to remove bloat.
Click to expand...
Click to collapse
V0latyle said:
Not without root.
Click to expand...
Click to collapse
Yes you can remove, disable unwanted bloatware via ADB commands. Personally I've disabled samsung dex and similiar unwanted programs, removed swiftkey and other bloat....
Klaudas said:
Yes you can remove, disable unwanted bloatware via ADB commands. Personally I've disabled samsung dex and similiar unwanted programs, removed swiftkey and other bloat....
Click to expand...
Click to collapse
Any guide and list of what is safe to remove?
Fl1nt91 said:
Any guide and list of what is safe to remove?
Click to expand...
Click to collapse
There is a guide. Search XDA for this thread "Samsung Galaxy One UI - Optimization Guide". You will find there everything you need to debloat by your needs.
dr.ketan said:
Worth to mention, Once you unlock bootloader and flash custom binary, you can relock bootloader later after flashing stock firmware first but still it leaves footprint and certain features will be stopped working forever. e.g Samsung Pass and Pay and may be more.
Click to expand...
Click to collapse
Safetynet fix will not help?
Also what i meant was not relock state for bootloader. I meant lock. For example MSM tool in oneplus locks bootloader (locks, not relocks)
Also "parallel apps" is a feature where you can setup 2 discords for example. It can be built in or if you have root - island app.
Korothi said:
Safetynet fix will not help?
Also what i meant was not relock state for bootloader. I meant lock. For example MSM tool in oneplus locks bootloader (locks, not relocks)
Also "parallel apps" is a feature where you can setup 2 discords for example. It can be built in or if you have root - island app.
Click to expand...
Click to collapse
I don't understand still between lock and relock
As explained above by @V0latyle default state of device is locked. If you want you can unlock it. But once you unlock and flash custom binary you can never lock again as same state before you unlocked. You can relock bootloader with missing some features forever. Nothing can help to restore said functions.
Samsung have two features which give you dual app
1.Dual Apps
2.Secure folder
With both these utilities you can use same app in two environments. Again not all apps may supported.
dr.ketan said:
I don't understand still between lock and relock
As explained above by @V0latyle default state of device is locked. If you want you can unlock it. But once you unlock and flash custom binary you can never lock again as same state before you unlocked. You can relock bootloader with missing some features forever. Nothing can help to restore said functions.
Click to expand...
Click to collapse
To expand on this: Samsung uses Knox Guard and other features to detect whether custom images have been flashed to the device. If this is true, some apps and functions that depend on Knox status may not work.
This is in contrast to other OEMs such as Google - the Pixel series can be restored to factory stock with a locked bootloader, and there will be no trace of the device ever having been modified.
What you can do, on either stock or custom firmware, as long as you're rooted with Magisk, is use Magisk modules such as Universal SafetyNet Fix to spoof device responses to Play Integrity attestation, as well as "hide" Knox status. However, again, this requires root. Magisk modules cannot be used without Magisk root.
To try to explain this simply:
Stock firmware, never unlocked: Knox OK: secure functions will work.
Stock firmware, locked but previously unlocked, custom firmware never installed including Magisk patch and/or recovery, Knox should be OK.
Stock firmware, locked but previously unlocked with custom firmware, Knox tripped: secure functions will not work.
Stock/custom firmware, unlocked, rooted with Magisk, attestation responses fixed via Magisk module: Knox status should not matter, Android/Google secure functions should work but Samsung apps that depend on Knox may not.
It is not possible to reset Knox status once tripped.
Therefore, if the device has ever been modified, even if it's just a Magisk patch, re-locking the bootloader will not return it to the "pure" factory state. So, if you are wondering whether to unlock the bootloader, understand that once anything is modified, you are committed and there is no way back. If you don't intend on modifying anything, don't unlock.