Hi, I have some questions... I have 7.1.1 stock room, I want to root... The only thing that I have to do is flash this kernel https://forum.xda-developers.com/x-compact/development/kernel-xc-genesis-kernel-v1-01-t3525060/, then the Twrp, and the magisk?
That's it?
Because I read that I have to do a backup TA, and drm, and I do not know what that is, is it necessary?
Thanks, and sorry I noob ?
manuel1496 said:
Hi, I have some questions... I have 7.1.1 stock room, I want to root... The only thing that I have to do is flash this kernel https://forum.xda-developers.com/x-compact/development/kernel-xc-genesis-kernel-v1-01-t3525060/, then the Twrp, and the magisk?
That's it?
Because I read that I have to do a backup TA, and drm, and I do not know what that is, is it necessary?
Thanks, and sorry I noob
Click to expand...
Click to collapse
TA partition includes certain files related to camera quality. So, if you don't back it up, you will lose it permanantly when you unlock the bootloader, (which is typically required for any custom kernel). If you're not too hung up on camera quality, you might not miss it. The difference is noticeable, but small. Backing up the TA will probably require a downgrade to MM.
levone1 said:
TA partition includes certain files related to camera quality. So, if you don't back it up, you will lose it permanantly when you unlock the bootloader, (which is typically required for any custom kernel). If you're not too hung up on camera quality, you might not miss it. The difference is noticeable, but small. Backing up the TA will probably require a downgrade to MM.
Click to expand...
Click to collapse
OK! Well I unlocked the bootloader 2 years ago, so... I supuse that a lost the camera's quality and I'm fine. What is drm? And what comes?. Thank so much.
manuel1496 said:
OK! Well I unlocked the bootloader 2 years ago, so... I supuse that a lost the camera's quality and I'm fine. What is drm? And what comes?. Thank so much.
Click to expand...
Click to collapse
Drm has to do with ta also, so it's not an issue for you. There is something out there called 'drm fix' which is supposed to mimic the effects that you lost when you wiped ta, but if you're fine with the camera, don't worry about it. You should be able to flash Genesis kernel and have root, if you are planning on staying on N...
levone1 said:
Drm has to do with ta also, so it's not an issue for you. There is something out there called 'drm fix' which is supposed to mimic the effects that you lost when you wiped ta, but if you're fine with the camera, don't worry about it. You should be able to flash Genesis kernel and have root, if you are planning on staying on N...
Click to expand...
Click to collapse
OK ok, well to finish, I flash the Genesis kernel, then the Twrp, and the magisk. Right?
manuel1496 said:
OK ok, well to finish, I flash the Genesis kernel, then the Twrp, and the magisk. Right?
Click to expand...
Click to collapse
Should be fine. You might want to reboot after each one, just in case something doesn't work, so you know where the problem is... Read Genesis thread carefully to make sure you get the right version, etc...
Related
Hello there everyone, this is my very first thread and yes I did run a search but couldn't find ALL the information I was looking for.
I intend to use Nandroid as a complete restore-point so I could go back if I mess things up. And the phone would be like "What problems bro, shiet never happened to me". Lets say I want to try a custom ROM/Kernel/Anything but I am not sure whether it will work as I expect it to, it could brick my device. I don't know. My questions are:
1. If I make a complete Nandroid backup will it be able to bring my mobile back to life should things go wrong?
2. Will my Boot-loader stay unlocked? (I will make the backup after unlocking/flashing TWRP/rooting)
3. Will it preserve all essential things like ROM/Kernel/Custom Recovery (TWRP)/SuperSU/BusyBox? (I don't care about multimedia stuff)
Basically, is it a time-machine?
Replies are much appreciated, Thanks!
1. Yes, so long as it isn't a hardware fault
2. Yes
3. Yes as it is a complete snap-shot of the system in its entirety
Whoa, insanely fast reply!
Thanks mate, you cleared my doubts!
\o/
I also got some questions.
Is there any way to get a nandroid with my stock room, i mean, just do the nandroid backup without root, unlock bootloader etc... etc.. ?
Will I receive OTA updates from Google if I just unlock bootloader, root and change Kerne (trinity) l/ install Custom Recovery (TWRP)/SuperSU/BusyBox ?
I'm asking it because I have huge problems with my Sound (phones, speakers / they are to weak) and with my Vibration .... ugh, its weak too. Any hints about it ?
Thanks a lot!
CaixaDagua said:
I also got some questions.
Is there any way to get a nandroid with my stock room, i mean, just do the nandroid backup without root, unlock bootloader etc... etc.. ?
Will I receive OTA updates from Google if I just unlock bootloader, root and change Kerne (trinity) l/ install Custom Recovery (TWRP)/SuperSU/BusyBox ?
I'm asking it because I have huge problems with my Sound (phones, speakers / they are to weak) and with my Vibration .... ugh, its weak too. Any hints about it ?
Thanks a lot!
Click to expand...
Click to collapse
You can't do a Nandroid Backup if you have the stock recovery. You need a custom one for that. And for a custom recovery, you need to unlock your bootloader.
abaaaabbbb63 said:
You can't do a Nandroid Backup if you have the stock recovery. You need a custom one for that. And for a custom recovery, you need to unlock your bootloader.
Click to expand...
Click to collapse
Ok buddy!
Thanks for the quick answer!
I'll try to do it
Have a nice day!
I know it was possible previously to root without unlocking the bootloader.
Is it still possible? something people are working on? or not possible and backup everything first.
Thanks in advance
Mark
mark1holland1 said:
I know it was possible previously to root without unlocking the bootloader.
Is it still possible? something people are working on? or not possible and backup everything first.
Thanks in advance
Mark
Click to expand...
Click to collapse
I didn't know that was ever possible on the Nexus 7. I bought one of the first available, and from the moment I got it I had to unlock the BL to root. Thought it was always like that. Nothing's changed as far as I can tell. On other devices, sure you can root with a locked BL, but for the N7, you've always had to unlock first, and with it being so easy, I don't think anyone's motivated enough to cook up a workaround.
absinthesummer said:
I didn't know that was ever possible on the Nexus 7. I bought one of the first available, and from the moment I got it I had to unlock the BL to root. Thought it was always like that. Nothing's changed as far as I can tell. On other devices, sure you can root with a locked BL, but for the N7, you've always had to unlock first, and with it being so easy, I don't think anyone's motivated enough to cook up a workaround.
Click to expand...
Click to collapse
Hi, absinthesummer...
Yes, there was (and still is, if you're still on JB 4.2.2) a method available of rooting without unlocking the bootloader. And it was ridiculously easy to do. Avoiding unlocking the bootloader also avoids the factory reset, and consequential wipe.
Sadly however, under Jellybean 4.3, this exploit no longer works, and it seems unlikely a similar root-without-unlocking-the-bootloader type exploit, will become available anytime soon. Which, from a security point of view, is actually (probably) a good thing.
mark1holland1 said:
I know it was possible previously to root without unlocking the bootloader.
Is it still possible? something people are working on? or not possible and backup everything first.
Thanks in advance
Mark
Click to expand...
Click to collapse
Hi, mark1holland1...
As, I've mentioned, the old 'motochopper exploit' no longer works under JB4.3, so if you want root, you're going to have to do it the old fashioned way...
------------------------------------------
Backup the stuff on your Nexus 7...
Unlock the bootloader...
Fastboot flash a Custom Recovery (CWM or TWRP)...
Using that Recovery, flash Chainfires SuperSU root updater zip...
Copy all your stuff back to the Nexus 7...
Not difficult to do... just tedious and time consuming.
------------------------------------------
...it's either the above, or wait around indefinitely for a genius developer to find another exploit, which, given the security enhancements of JB4.3 does seem hugely unlikely.
Rgrds,
Ged.
GedBlake said:
Hi, absinthesummer...
Yes, there was (and still is, if you're still on JB 4.2.2) a method available of rooting without unlocking the bootloader. And it was ridiculously easy to do. Avoiding unlocking the bootloader also avoids the factory reset, and consequential wipe.
Sadly however, under Jellybean 4.3, this exploit no longer works, and it seems unlikely a similar root-without-unlocking-the-bootloader type exploit, will become available anytime soon. Which, from a security point of view, is actually (probably) a good thing.
Hi, mark1holland1...
As, I've mentioned, the old 'motochopper exploit' no longer works under JB4.3, so if you want root, you're going to have to do it the old fashioned way...
------------------------------------------
Backup the stuff on your Nexus 7...
Unlock the bootloader...
Fastboot flash a Custom Recovery (CWM or TWRP)...
Using that Recovery, flash Chainfires SuperSU root updater zip...
Copy all your stuff back to the Nexus 7...
Not difficult to do... just tedious and time consuming.
------------------------------------------
...it's either the above, or wait around indefinitely for a genius developer to find another exploit, which, given the security enhancements of JB4.3 does seem hugely unlikely.
Rgrds,
Ged.
Click to expand...
Click to collapse
Many thanks for a recent concise and informative post!
I was mainly being lazy with regards to not wanting to wipe everything and start again! I have helium installed to back everything up, guess Ill try to get a clear day to do it all........
GedBlake said:
Hi, absinthesummer...
Yes, there was (and still is, if you're still on JB 4.2.2) a method available of rooting without unlocking the bootloader. And it was ridiculously easy to do. Avoiding unlocking the bootloader also avoids the factory reset, and consequential wipe.
Sadly however, under Jellybean 4.3, this exploit no longer works, and it seems unlikely a similar root-without-unlocking-the-bootloader type exploit, will become available anytime soon. Which, from a security point of view, is actually (probably) a good thing.
Hi, mark1holland1...
As, I've mentioned, the old 'motochopper exploit' no longer works under JB4.3, so if you want root, you're going to have to do it the old fashioned way...
------------------------------------------
Backup the stuff on your Nexus 7...
Unlock the bootloader...
Fastboot flash a Custom Recovery (CWM or TWRP)...
Using that Recovery, flash Chainfires SuperSU root updater zip...
Copy all your stuff back to the Nexus 7...
Not difficult to do... just tedious and time consuming.
------------------------------------------
...it's either the above, or wait around indefinitely for a genius developer to find another exploit, which, given the security enhancements of JB4.3 does seem hugely unlikely.
Rgrds,
Ged.
Click to expand...
Click to collapse
Hmm, wow thanks for the info. I never knew that! I just remember my first N7 every post said Step 1:Unlock your bootloader... lol had I known there was a way around it I might have tried it! But my first 16gb and my later 32gb were both unlocked and rooted within hours of buying them, so perhaps I just wasn't motivated enough to look for it.
I could see how or why that would be desirable though I guess... before I bought my S3, I had an LG L9 that the only way you could unlock the BL was to root then flash/update (LG Update tool hack) the firmware meant for the international version of the phone, which mirrored(!!!) the entire display both horizontally and vertically. Then fastboot the oem unlock and unlock the best way you could with that kind of touch screen lol, THEN re-flash standard rooted firmware for the US back over it... Seriously NOT worth it! Because even if the mirroring went away with the right firmware, the boot logo would still be mirrored and it was possible your screen would not return to normal. So forget about any warranty at that point. But, I gotta hand it to the devs on that device- now they were some motivated folks. They went to a lot of trouble to unlock that BL. You could root and install CWM without unlocking, but if you flashed CM and it was buggy or something, there was no turning back to stock. We were left with mods only unless we wanted to do alll that work.
That just reminds me how thankful I am for my S3 and N7s.
I cant hold myself back to share my thoughts about general hysteria about unlocking bootloader and therefore losing DRM keys. While I understand, that many users are pissed off, there are some points to consider before putting blame on Sony:
- losing DRM keys in no way cripples or disables hardware in your phone. DRM keys protect some "exclusive" functions that Sony offers to users of its Stock ROMs, mainly Camera and Display Enhancements.
- Its up to you, to decide whether you want to go on with pure Iron and add functions you want, including any Image enhancements you want to add on top of raw data processing, or go full blown Sony with all bells and whistles.
- One should be clear, what he needs unlocking bootloader for. Root only, or Custom ROM/CM.
- even without "artificial" enhancements to Camera and Display, Z3 (and Z2 as well) is impressive piece of hardware and it will be pleasure to run swift clean Android/CM on it
- I blame Sony of course for not telling users the full story behind unlocking bootloader. It would be fair from Sony to offer re-flashing Stock including DRM to users, who unlocked bootloader before they knew that they will lose certain software functionality.
Howgh.
For me it's more about losing the warranty
ziemny said:
For me it's more about losing the warranty
Click to expand...
Click to collapse
Well, that's quite obvious It would be awesome to have hardware warranty separate
I'm using remote play so I do not want to loose my DRM keys...
You can root with giefroot (works in some versions) backup TA partition and then unlock.
3x3cUt0r said:
You can root with giefroot (works in some versions) backup TA partition and then unlock.
Click to expand...
Click to collapse
The point is that giefroot works seldom. I cant use it, at least not now, simply doesnt work on certain models. Having TA/DRM backed up is good, but only for eventual reflashing stock. Maybe in future there will be some use for your DRM keys in CM or other ROM if there will be app requiring it or somebody makes Sony apps working..
SweDunda said:
I'm using remote play so I do not want to loose my DRM keys...
Click to expand...
Click to collapse
If you root without unlocking the bootloader, do you still lose the DRM keys? I use Remote Play as well and that would really suck to have to choose between root or remote play and usable pics from the camera. I'm on a D6616 (T Mobile), so rooting doesn't work with the existing method yet, but hopefully it will soon.
jordanyork said:
If you root without unlocking the bootloader, do you still lose the DRM keys?
Click to expand...
Click to collapse
No. And after you can back the TA partition up and restore it whenever you like. The TA partition contains your DRM keys.
Newt182 said:
No. And after you can back the TA partition up and restore it whenever you like. The TA partition contains your DRM keys.
Click to expand...
Click to collapse
Fantastic! I'll just sit here and wait patiently for D6616 support. Thanks for the reply.
jordanyork said:
Fantastic! I'll just sit here and wait patiently for D6616 support. Thanks for the reply.
Click to expand...
Click to collapse
I'm with you. I'm just going to creep xda till somthing amazing happens lol.
4.4 roms would be great imo, dont know why noone pays them attention
So from what I gathered you can root first, backup TA which includes the DRM Keys, then unlock bootloader?
Then if one wants to restore the DRM keys, restore the TA DRM backup and lock bootloader? and the phone is back to stock with the super duper enhancements? Correct?
Someone kindly confirm the above as im looking to pick one up if there is a backup / restore option available?
I will be looking to purchase a UK model.
Thanks.
nrd\ said:
So from what I gathered you can root first, backup TA which includes the DRM Keys, then unlock bootloader?
Then if one wants to restore the DRM keys, restore the TA DRM backup and lock bootloader? and the phone is back to stock with the super duper enhancements? Correct?
Someone kindly confirm the above as im looking to pick one up if there is a backup / restore option available?
I will be looking to purchase a UK model.
Thanks.
Click to expand...
Click to collapse
Before restoring, flash to stock first. And then restore drm keys.
How can you restore drm keys without root??? surely it needs block level access to that flash partition???
Anyway, only reason I want root is to re-enable r/w access to sd card, which apparently lolipop will have anyway
g
With plain root, what would i loose? The dilemma is loosing something special out of a special phone. And whats drm to be exact? Sorry for being such a noob. The last time i explored rooting and custom roms are back when i was using an r800i Xperia Play.
bhavei said:
With plain root, what would i loose? The dilemma is loosing something special out of a special phone. And whats drm to be exact? Sorry for being such a noob. The last time i explored rooting and custom roms are back when i was using an r800i Xperia Play.
Click to expand...
Click to collapse
You will lose nothing. Unless you unlock the bootloader which will mess with the TA, from there then you'll lose Sony abracadabra magic image processing and low light camera performance. DRM = TA
DRM is unique for each device, if I were to give you my DRM and you restore it, you'll hard brick your device for sure. It's like an identity card or a car plate (hopefully you get the idea) DRM is the one in charge of the magic sony has. This bad boy is very sensitive, be sure to back it up if you want to unlock bootloader.
All in all, root doesn't disturb this bad boy in his deep sleep lol
Cheers,
T
Any chance that lifelog is affected by the loss of drm keys as well? It stopped tracking since unlocked...
Julián
Google Camera
Is the DRM for the camera only for the Sony camera? If I unlock the bootloader and use the google camera from the play store will it be worse than using the stock camera when it was locked?
Thanks Thraxzzz for the Idea, i now get it, i guess i was Looking for a General "need to know" thread here is the General but there's none "i guess" i have a full understanding "somehow" now. It wasn't this complicated back then when i still have my r800i, maybe someone should start a Sticky Thread about abbreviations and what must and must not. If i rushed in and unlocked my Bootloader, then i could have lost what i actually paid for from the beginning. Its interesting to start learning the do's and don't.
which app to use to backup ta (drm keys)?
For those who didn't know already: yes, there's a way to root Z5 compact with MM. Bootloader needs to be unlocked.
(1) Install Marshmallow. I did it with flashtool. (I used E5823_32.1.A.1.163_1299-0270_R7C)
--> Clean install, if not, you'll get Google Play Store and Google Play Service to be forced to close.
(2) Install another kernel over here. It's AndroPlus kernel, and I choose the latest version (v20).
--> extract boot.img
-->> (in fastboot mode: power down + press vol up + insert USB) fastboot flash boot boot.img
Edit 20/03/2016: Don't use this version of TWRP. It won't work.
(3) Install TWRP over here, like found in this threat. It's TWRP 3.0.0
--> rename recovery.img
-->> fastboot flash recovery recovery.img
(4) Flash SuperSU like you can find here. I flashed v2.65
You can reboot, your Z5 compact will be on Android 6.0 with Root Access.
By the way, read this before you try to install Xposed.
It's possible to install Xposed. I used v80-sdk23-arm64.zip (framework to flash) and XposedInstaller_3.0_alpha4.apk as installer.
thanks for the summary. It might be worth mentioning that there's a way to keep the DRM functionalities with unlocked bootloader, even when the keys are erased. http://forum.xda-developers.com/xperia-z5/development/sony-credentials-restore-unlocking-t3296383
Didn't try it for myself, but according to the replys, it looks very promising.
Won't hurt you to mention its for Unlocked Bootloader (UB)...
Thanks for the guide, I'll try this once I get home.
E: Clean install means I should wipe my userdata?
bubimir13 said:
Won't hurt you to mention its for Unlocked Bootloader (UB)...
Click to expand...
Click to collapse
You're 100% right. I didn't think about that, because my bootloader was already unlocked.
Kallu609 said:
Thanks for the guide, I'll try this once I get home.
E: Clean install means I should wipe my userdata?
Click to expand...
Click to collapse
Clean install = you need to wipe userdata (not SD card)
Dirty install = you flash new ROM without changing existing userdata.
So indeed, you need to start on a blank canvas and reinstall your apps.
--> If you're using a password manager, like LastPass or something else, it's way easier to start off from a clean system. If you're not using a password manager yet, maybe it's time to reconsider using one.
for me a big point to mention here: sdcard is not workin gat the moment..
so you do have to place all things you need to flash on internal storage.
youvedone said:
for me a big point to mention here: sdcard is not workin gat the moment..
so you do have to place all things you need to flash on internal storage.
Click to expand...
Click to collapse
Weird...
For me, having root access didn't change anything to SD card performance. Which means (for me):
- no problem to install/flash SuperSU using my external SD card.
- no difference after root was installed. I still can flash anything from SD Card.
does it have to be E5823_32.1.A.1.163_1299-0270_R7C?
I'm currently on 32.1.A.1.163_1298_7782_R9C.
should i flash the R7C one?
youvedone said:
for me a big point to mention here: sdcard is not workin gat the moment..
so you do have to place all things you need to flash on internal storage.
Click to expand...
Click to collapse
Helleren said:
does it have to be E5823_32.1.A.1.163_1299-0270_R7C?
I'm currently on 32.1.A.1.163_1298_7782_R9C.
should i flash the R7C one?
Click to expand...
Click to collapse
I only wanted to share the way *I* did it. (because different people mentioned there's no root for Z5C)
I guess it will work with any E5823_32.1.A.* and. it. could also work with other/newer kernels/TWRP/superSU... but I didn't test anything else than this device and this setup. + I know for me it didn't work with TWRP 2.8.7.
toxic_garden said:
thanks for the summary. It might be worth mentioning that there's a way to keep the DRM functionalities with unlocked bootloader, even when the keys are erased. http://forum.xda-developers.com/xperia-z5/development/sony-credentials-restore-unlocking-t3296383
Didn't try it for myself, but according to the replys, it looks very promising.
Click to expand...
Click to collapse
The solution to restore drm functions is already included in the Andropluskernel
---------- Post added at 07:16 PM ---------- Previous post was at 07:15 PM ----------
youvedone said:
for me a big point to mention here: sdcard is not workin gat the moment..
so you do have to place all things you need to flash on internal storage.
Click to expand...
Click to collapse
For me sdcard is working normally under Marshmallow, but can't be mounted in TWRP
--jenana-- said:
I only wanted to share the way *I* did it. (because different people mentioned there's no root for Z5C)
I guess it will work with any E5823_32.1.A.* and. it. could also work with other/newer kernels/TWRP/superSU... but I didn't test anything else than this device and this setup. + I know for me it didn't work with TWRP 2.8.7.
Click to expand...
Click to collapse
Allright,I'll give it a go with the Nordic combined firmware.
Has anybody tried to encrypt after rooting?
Anybody knows if this could work on a E5803 model?
Sent from my E5803 using Tapatalk
I don't really understand the Kernel stuff. But would this just be a workaround to get root for now?
Is it stable?
Would you recommend waiting for a future release?
Thanks!
vibo2013 said:
The solution to restore drm functions is already included in the Andropluskernel
Hang on.... so do i have to follow the guide to update the drm functions or you saying the kernel already has this built in? as in all i need to do is flash the kernel and rom
And can i backup my TA like on the z1c.
Thanks
kam
Click to expand...
Click to collapse
do_salah said:
vibo2013 said:
The solution to restore drm functions is already included in the Andropluskernel
Hang on.... so do i have to follow the guide to update the drm functions or you saying the kernel already has this built in? as in all i need to do is flash the kernel and rom
And can i backup my TA like on the z1c.
Thanks
kam
Click to expand...
Click to collapse
"...Added DRM functions restore patch (thanks tobias.waldvogel)
--This is just a fallback and you have to delete contents of /data/credmgr to enable restore patch...."
Thats what the Changelog on the Androplus Kernel Website says
Click to expand...
Click to collapse
For me scared is working to! I also did not wipe my user data. I just flashed the german vodafone firmware over my existing LP 5.0.2 using flashtool, which kept all my apps. The rest was done as described in the first post. The only app which caused trouble was spotify, I just reinstalled it and everything was fine ...
kevinwu128 said:
I don't really understand the Kernel stuff. But would this just be a workaround to get root for now?
Is it stable?
Would you recommend waiting for a future release?
Thanks!
Click to expand...
Click to collapse
No, nothing about this is stable.
-- Dirty flash of MM could mean that certain apps or parts of the system become unstable.
-- TWRP 3.0 is only released a few days ago. Could contain bugs, who knows...
-- AndroPlus kernel is work in progress. Literally "status: testing". And for more info about that kernel, you can always read/ask in that threat (I don't know the ins and outs of kernels at all)
-- Xposed + it's modules: all work in progress. Some could be stable, some could be buggy.
For now, this is a way to get root. Maybe other developers come with different methods to root, maybe not. But getting root access means: f*ck*ng around with your system on the deepest possible level and breaking some "stability" sony intended to give us. If you would like to take advantage of what root access can give you: give it a try. If you're afraid to break anything: stay away from it or be prepared that you'll have to start over from scratch.
Yes forgot that to clear. Sdcard is working in running system, but not in twrp. Thats no big deal, only nice to know...
And I've tried it german customied did work.. Schud not make any difference as long as it the same version number...
Drm restoration I couldnt check until now.
Nice that I now can restore my app data with titanium backup
---------- Post added at 12:25 AM ---------- Previous post was at 12:20 AM ----------
--jenana-- said:
Weird...
For me, having root access didn't change anything to SD card performance. Which means (for me):
- no problem to install/flash SuperSU using my external SD card.
- no difference after root was installed. I still can flash anything from SD Card.
Click to expand...
Click to collapse
I'll think I have to try again. Perhaps the first boot something was going wrong.. But I couldn't access sdcard and flash supersu from the card with twrp. SoI booted, copied supersu to internal "sdcard" and from there it worked.. I also tried to mount sdcard.. No reaction (but also only at first boot)
--jenana-- said:
No, nothing about this is stable.
-- Dirty flash of MM could mean that certain apps or parts of the system become unstable.
-- TWRP 3.0 is only released a few days ago. Could contain bugs, who knows...
-- AndroPlus kernel is work in progress. Literally "status: testing". And for more info about that kernel, you can always read/ask in that threat (I don't know the ins and outs of kernels at all)
-- Xposed + it's modules: all work in progress. Some could be stable, some could be buggy.
For now, this is a way to get root. Maybe other developers come with different methods to root, maybe not. But getting root access means: f*ck*ng around with your system on the deepest possible level and breaking some "stability" sony intended to give us. If you would like to take advantage of what root access can give you: give it a try. If you're afraid to break anything: stay away from it or be prepared that you'll have to start over from scratch.
Click to expand...
Click to collapse
Thanks for the reply, i can't stand lollipop anymore so i'll give it a try ! I'll update once done!
Since the Oreo update, notifications from ALL play store apps are barely audible. Built in/system sounds are not effected. Have tried uninstalling/reinstalling apps, and a factory reset. Issue still persists. Like so low that I can't even hear them with the volume on max unless the phone is right next to my head.
Phone is not rooted and never has been. It is also NOT the Amazon variant, it is non carrier specific purchased from Walmart. Do I just need to follow a rooting guide for Oreo, then simply fastboot flash stock 7.0 & be sure to disable the update service afterwards? Do I need to worry about bootloader stuff or anything else? Or just flash the stock 7.0 image as is?
plastic_green_head said:
Since the Oreo update, notifications from ALL play store apps are barely audible. Built in/system sounds are not effected. Have tried uninstalling/reinstalling apps, and a factory reset. Issue still persists. Like so low that I can't even hear them with the volume on max unless the phone is right next to my head.
Phone is not rooted and never has been. It is also NOT the Amazon variant, it is non carrier specific purchased from Walmart. Do I just need to follow a rooting guide for Oreo, then simply fastboot flash stock 7.0 & be sure to disable the update service afterwards? Do I need to worry about bootloader stuff or anything else? Or just flash the stock 7.0 image as is?
Click to expand...
Click to collapse
I would suggest that the only way to do it safely is to unlock and root, then do a clean flash of the TWRP flashable nougat builds.
If you go from Oreo to nougat you will lose your IMEI, unless you change ownership of specific files and folders in your persist partition. There's no way to do that without root.
https://forum.xda-developers.com/g5-plus/development/twrp-flashable-stock-builds-t3813351
NZedPred said:
I would suggest that the only way to do it safely is to unlock and root, then do a clean flash of the TWRP flashable nougat builds.
If you go from Oreo to nougat you will lose your IMEI, unless you change ownership of specific files and folders in your persist partition. There's no way to do that without root.
https://forum.xda-developers.com/g5-plus/development/twrp-flashable-stock-builds-t3813351
Click to expand...
Click to collapse
Thanks. It looks like backing up my persist & ESF should eliminate any worries regarding loss of IMEI.
plastic_green_head said:
Thanks. It looks like backing up my persist & ESF should eliminate any worries regarding loss of IMEI.
Click to expand...
Click to collapse
Well if by backing up you mean backing up persist and efs on Oreo then u might have issues. I dont think Oreo backup would work on Nougat. There was a thread tho on this exact topic. So you need to leave out gpt and some other partition if u fastboot flash it. You cannot downgrade the bootloader. I'm sure u know that. Safer way would be to flash via TWRP.
GL:good:
debdeep98 said:
Well if by backing up you mean backing up persist and efs on Oreo then u might have issues. I dont think Oreo backup would work on Nougat. There was a thread tho on this exact topic. So you need to leave out gpt and some other partition if u fastboot flash it. You cannot downgrade the bootloader. I'm sure u know that. Safer way would be to flash via TWRP.
GL:good:
Click to expand...
Click to collapse
Hmmmm. TWRP it is then. I have plenty of experience with TWRP, but I haven't flashed a phone in MANY years. One thing about the page you linked to. It states "An important note for those who have flashed custom Oreo roms. It is a frequent issue regarding Oreo roms that the device's IMEI is set to 0 in certain conditions."
So since my phone is on stock ota Oreo & not a custom Oreo rom... do I need to even worry about losing IMEI? Maybe I should ask in that thread?
plastic_green_head said:
Maybe I should ask in that thread?
Click to expand...
Click to collapse
Yes that sounds good.