Hello,
Recently the forced upgrade of the Sony Xperia X OS to Oreo destroyed certain functionalities which were critical to my phone's utility. Functionalities for which I had indeed selected and purchased the phone in the first place. Having suffered similar problems in the past, I postponed the upgrade for weeks and sought advice from Sony on declining the update. Of course they said this was not an option and that my files would be unaffected, and of course this was false information.
As someone on the Autism spectrum, I have always struggled with digital merchandise and the tendency for suppliers to alter their products after I have purchased them. It is necessary for me to have consistency, and to be able to organize things in a certain way without worry of having them altered. I familiarize myself with how to use the product and then, silently, menus change, operations reorganize themselves entirely and it becomes difficult to perform the basic tasks that I have learned at great personal difficulty to navigate on my device already. This is a big problem. I do not want the latest and the greatest. I want consistency. I want my device to continue operating as it did when I purchased it less than a year ago.
All of this is to say that when the latest update destroyed the very things that gave my phone value to me and for which I had painstakingly selected it, I was thrown into a mild state of panic. After confirming with Sony that the upgrade was irreversible, and finding no other alternative, I elected to purchase the very same phone that I already owned for a second time, knowing that the Operating System would not yet have been upgraded.
The problem, now, is how to use the phone without risking the same forced OS upgrade and rendering the repurchase entirely pointless.
My understanding is that the only way to accomplish this would be to root the new phone. Please correct me if I am wrong. Given my circumstances, I have always seemed an obvious candidate for rooting my devices in order to maintain control of operations. Unfortunately I am not very technically inclined, and Root tutorials simply bamboozle me with their jargon. Given the sensitive nature of the rooting process, in that it seems very easy to make a misstep or run into complications, I have been excluded from taking advantage of this obvious solution.
Yet here I am, with a brand new phone that I cannot use unless I am able find a way to prevent the Operating System from updating.
My questions are:
Is there any way to block OS updates without rooting, that I am unaware of?
If rooting is the only method, what is the safest way that a layman like myself might confidently pursue this route?
Thank you for your time.
wynden said:
My questions are:
Is there any way to block OS updates without rooting, that I am unaware of?
If rooting is the only method, what is the safest way that a layman like myself might confidently pursue this route?
Thank you for your time.
Click to expand...
Click to collapse
No. But if I remember correctly, you can just not update your phone. Or you can try to unpack the firmware, edit it manually, delete the app which updates your system, repack the firmware and flash it. Or you can freeze it through ADB... But, the best way, of course, is root.
It's quite easy if you'll follow the instructions.
In short:
Flash Android 6.0 through Flashtool. Not as hard as it sounds, but it's mandratory.
Save your TA partition. One bat-script on Android 6.0 with locked bootloader, and you are ready.
Unlocking your bootloader. Sony have their own instructions which are pretty easy to follow.
Delete the app which updates your system. The easiest step.
Last: if something went wrong with your hardware - just relock your bootloader with the keys you've backed up - and you have your phone in a factory new condition!
Good luck! Ask here if you need any additional information!
Gray47Maxx said:
No. But if I remember correctly, you can just not update your phone.
Click to expand...
Click to collapse
Gray, thank you for your reply. It does not seem that just not updating is an option, as the phone keeps harassing the user to download the update, and there is no way to disable those push notifications, as far as I am aware.
In short:
Flash Android 6.0 through Flashtool. Not as hard as it sounds, but it's mandratory.
Save your TA partition. One bat-script on Android 6.0 with locked bootloader, and you are ready.
Unlocking your bootloader. Sony have their own instructions which are pretty easy to follow.
Delete the app which updates your system. The easiest step.
Click to expand...
Click to collapse
I appreciate the summary, but I don't know what a flash tool is, or a TA partition, or a bat-script, or a bootloader, etc. This is why I feel unqualified to tackle such a sensitive operation. I have googled instructions on rooting, but since I do not understand what is being asked of me, I cannot proceed. What is the best way for a layman who is easily overwhelmed to familiarize themselves with the technology to become reliably competent at tackling such a project?
Last: if something went wrong with your hardware - just relock your bootloader with the keys you've backed up - and you have your phone in a factory new condition!
Click to expand...
Click to collapse
My understanding was that a root was irreversible. This is a major contributor to my trepidation. Is this not the case?
Additionally, I have gathered from various forums that the process of rooting Xperia has been particularly problematic and frequently unsuccessful. Do you know if there is any truth to this? I would not have a clue what to do if I encountered a problem.
wynden said:
Gray, thank you for your reply. It does not seem that just not updating is an option, as the phone keeps harassing the user to download the update, and there is no way to disable those push notifications, as far as I am aware.
Click to expand...
Click to collapse
It's only a push notification, and it can easily be ignored. But it's very annoying, I know.
wynden said:
I appreciate the summary, but I don't know what a flash tool is, or a TA partition, or a bat-script, or a bootloader, etc. This is why I feel unqualified to tackle such a sensitive operation. I have googled instructions on rooting, but since I do not understand what is being asked of me, I cannot proceed. What is the best way for a layman who is easily overwhelmed to familiarize themselves with the technology to become reliably competent at tackling such a project?
Click to expand...
Click to collapse
The best way is to try to find a person who is familiar with Sony devices - then you'll have less chances to break something. If you don't have anyone familiar with Sony - then XDA have some good threads (this or this, for example) for self-learning.
My own experience with rooting, tweaking, making things started with bootloader unlocking, and my only helpers were guides and members of one famous Russian geek forums. So, maybe soon you'll join this community as a full member. Who knows ;^)
wynden said:
My understanding was that a root was irreversible. This is a major contributor to my trepidation. Is this not the case?
Additionally, I have gathered from various forums that the process of rooting Xperia has been particularly problematic and frequently unsuccessful. Do you know if there is any truth to this? I would not have a clue what to do if I encountered a problem.
Click to expand...
Click to collapse
Root is reversible, so do bootloader unlocking. A little bit complicated, but possible.
Yes, and as someone mentioned there, in terms of security Sony is an Apple of Android world here. Their devices are hardest to modify, they are overcosted, but there is nothing impossible.
So, in short:
You have two ways:
You can downgrade your phone, ignore that push notifications and keep your phone intact.
You can unlock your bootloader, root your phone and delete the app that updates your phone.
P.S. If I remember correctly, there was a way to "freeze" (force app to stop all of its activity) this app without rooting, unlocking, and so on. If I'll find it - I'll share it here
Thank you for your reply.
Gray47Maxx said:
It's only a push notification, and it can easily be ignored. But it's very annoying, I know.
Click to expand...
Click to collapse
No, not at least not in my case. Moreover it is only too easy to accidentally enable it when you are trying to do something else, entirely.
Thank you for directing me to those links, I will investigate the guides and see if they are any more illuminating than others I have read. I do not have a personal acquaintance familiar with Sony devices, unfortunately. They seem rather hard to come by even online.
If Sony devices are, indeed, the hardest to modify, then I feel my apprehension is justified. Is it wise to proceed without a technical expert to consult? Is there anyplace where I might find help if I need it? How likely is it that I will do irreparable damage to the device?
You can downgrade your phone, ignore that push notifications and keep your phone intact
Click to expand...
Click to collapse
When you say "downgrade", do you refer to restricting the second model I purchased to the OS it came with, or do you mean to suggest that my original phone can be downgraded? I had been told that even with root an OS update could not be reversed.
P.S. If I remember correctly, there was a way to "freeze" (force app to stop all of its activity) this app without rooting, unlocking, and so on. If I'll find it - I'll share it here
Click to expand...
Click to collapse
That is definitely something I would be interested in exploring before proceeding with more drastic alternatives. If you have any suggestions as to where I might look for more information, please do let me know.
Again, thank you very much for your help and correspondence in this matter. It is greatly appreciated.
wynden said:
Is it wise to proceed without a technical expert to consult? Is there anyplace where I might find help if I need it? How likely is it that I will do irreparable damage to the device?
Click to expand...
Click to collapse
1. If you've learned everything from the threads and you are following instuctions step-by-step - then yes, it is OK.
2. The great place to find a man who can help you is to check some local repair shops (especially ones where you can repair Sony phones) and make some good relations with a local master/technician. If something went wrong - they'll fix it! Plus if you make friends with them, I'm sure they will help you in such a hard procedure.
3. Only one thing is irreparable - DRM keys. So, you must save them before doing anything. Everything else can be fixed pretty easily.
wynden said:
When you say "downgrade", do you refer to restricting the second model I purchased to the OS it came with, or do you mean to suggest that my original phone can be downgraded? I had been told that even with root an OS update could not be reversed.
Click to expand...
Click to collapse
Thankfully, it can be reversed - it's Android after all. There's a special program for doing updates and downgrades - it's called Flashtool. And, of course, you can downgrade your phone to 6.0 without unlocking bootloader with this program. There you can download an OS and here is a complete video how to flash your device through it.
wynden said:
That is definitely something I would be interested in exploring before proceeding with more drastic alternatives. If you have any suggestions as to where I might look for more information, please do let me know.
Again, thank you very much for your help and correspondence in this matter. It is greatly appreciated.
Click to expand...
Click to collapse
Sure!
Good luck in Flashtool using!
P.S. It looks like you can stop downloading your OS update.
When you'll downgrade to 6.0, go to Updater app -> Settings -> Automatic updates download -> OFF. Boom, only notification left.
SONY IS THE APPLE OF ANDROID ( WELL SAID) (Y)
its a Cryptex scroll, one key wrong and the secret is destroyed for ever!
as 8 years Sony Xperias user coming from various devices, era, and Security policies of SONY here what i have found
1. SE phones were the easiest to root , Pre 2012 (last known device Xperia Ion)
2. 2013, Z series launched and thru out life of Z (c6602 / C6603 ) rooting was Piece of cake
3. then came Z3 with Devil in the Details. Sony Started using DRMKEYS (Digitial Rights Managment Keys) the are Stored in Hidden Partition and Every time you wana use Premium features (which you paid for) ( such as Image Enhancement Features withing Camera and Movie Player) (Blue Tooth 5 technology) ( FastCharge options) ( SD cards above 32Gb support) and much more, Xperia will ask KERNEL to Check where DRM KEYS are Instated or not. if Kernel output is 1 then all these features works perfect.
4. Z3, Z3+ Z4v , Z5 and Finally Z5p etc landed in hands having LP (android lollypop) kernels (KK for Z3) and KINGROOT was able to Find Android Exploits and used to Root easily! however from MM kernel, when SONY gripped its security with SONY RIC, every attempt from KINGROOT to root Xperia went on BOOTLOOPS. hence the only way to ROOT sony was to FLASH MODIFIED KERNEL. and to FLASH MODIFIED kernel you must UNLOCK the BOOTLOADER and when you do that, TA partition will be WIPED and you will loose you DRM KEYS FOREVER. even when you root your Stockrom and have /system access, failure kernel finding drmkeys will always make your sony device entry level droid.
5. A fresh breeze , when DIRTY COW script found this exploit in MM kernel when newly purchased Xperia (like X) came in to your hands having Android 6.01, just connect it to WIndows PC, enable usb debugging and run the TA Backup Script AKA dirtycow script and it will SPEW this TA-xxxx-xxxx-xxxx-xxx.img file (2mb) in the same folder! run it more than one! it will spew same file with different timestamp in that same folder. So now you have something SONY never wanted you to have!
6. More Over a very amazing Kernel Modding script called ROOTKERNEL SCRIPT by @tobias.waldvogel was primed and later taken over by @serajr which basically takes given kernel.elf file from the downloaded Stockrom and switch off all securties and add line in kernel to always prompt all SONY APPS for the existance of DRM KEYS Provisioned! even if they arent. this scripted supported z3, z3+, z4v, Z5c, X5 , z5p, X, Xc, Xperf, Xz and XZs from kernels LP, MM, N and O making whole drm keys concept mockery for Sony.
7. from XZP sony changed the way drm works and now for every device there is hidden location where you cannot know and even if you add line in kernel to point memory block for existing drmkeys. it will fail so kernel fix for DRM is gone. However the controversial commercialized xperifix by member name //storm does the job.
coming back to you
your X falls under the glory period of numerious options and fixes where not only drmfix is possible in kernel but also you can extract your drm keys TA.img and one day you can use to relock your bootloader !
I would suggest you to
1. use dirtycow script! extract TA.img
2. unlock boodloader
3. ROOT your MM kernel , disable all software updates!
4. relock the bootloader using that same TA.img (if you want)
and i agree! all sony devices came in my hands were always the BEST with the OS; they left the FACTORY! later it was just unfinished Roms to SUPPORT its successors! , for X the OREO is horrible! its designed to Support XZ2 and XZP but since the tree starts from X so they had to include X also.
YasuHamed said:
For X the OREO is horrible! its designed to Support XZ2 and XZP but since the tree starts from X so they had to include X also.
Click to expand...
Click to collapse
Completely disagree with you. Oreo for X is the best stock ROM I've used so far. Stable, fast, battery life friendly, secured and just ideal. Why do you think it is bad?
BTW I've used XZ2 less than a week ago, both of them runs almost equal. So...
Gray47Maxx said:
The great place to find a man who can help you is to check some local repair shops
Click to expand...
Click to collapse
I was unable to locate a mobile repair shop anywhere near me, although that is what I had initially hoped I would be able to do. Still, I expect they would take exception with me if I wanted them to assist me in doing something that the manufacturers disallow, so I don't know that it would have helped.
It is news to me that the phone can be downgraded, contrary to what Sony informed me. Do you think it would be better for me to go this route before attempting a root?
I suspect a root will still be necessary, if only because it will continue prompting me to update. You mentioned that I can turn Automatic updates off, but I believe what you are referring to is a setting I had already enforced. I made sure that the phone does not automatically download the updates in the settings, but it nonetheless harasses me with push notifications that I cannot dismiss.
Thanks again for directing me to these resources and helping me begin to understand the nuances of what I'm attempting.
YasuHamed said:
coming back to you
your X falls under the glory period of numerious options and fixes where not only drmfix is possible in kernel but also you can extract your drm keys TA.img and one day you can use to relock your bootloader !
I would suggest you to
1. use dirtycow script! extract TA.img
2. unlock boodloader
3. ROOT your MM kernel , disable all software updates!
4. relock the bootloader using that same TA.img (if you want)
Click to expand...
Click to collapse
Thank you for the overview, it does help me better understand the conflicting information I have been finding online, and your remarks about the X are very reassuring and do give me some confidence and hope for success. Are there any simplified, step-by-step tutorials for implementing this method that you have recommended, which you could direct me to? Figuring out which one to follow is one of my primary points of confusion.
Gray47Maxx said:
Completely disagree with you. Oreo for X is the best stock ROM I've used so far. Stable, fast, battery life friendly, secured and just ideal. Why do you think it is bad?
BTW I've used XZ2 less than a week ago, both of them runs almost equal. So...
Click to expand...
Click to collapse
Third generation of Oreo for Sony X is less horrible .2.50 but still heatsup more than Nougat and starts hanging, lagging. Since I reside in a country where its 45C usually,for me Nougat .0.252 (came dec2017) was the best rom!
wynden said:
Thank you for the overview, it does help me better understand the conflicting information I have been finding online, and your remarks about the X are very reassuring and do give me some confidence and hope for success. Are there any simplified, step-by-step tutorials for implementing this method that you have recommended, which you could direct me to? Figuring out which one to follow is one of my primary points of confusion.
Click to expand...
Click to collapse
I own X so Trust me The device is over all LOVE,
1. the modified kernels, instruction, Trivia can be found in my post https://forum.xda-developers.com/xperia-x/how-to/root-xperia-x-f5122-android-n-34-2-2-47-t3594502
2. BASIC INFO about Xperias, Unlocking bootloader and using Dirtycow Script MUST BE READ at https://forum.xda-developers.com/showpost.php?p=72141176&postcount=7
3. Since you are on Android MM, Enable usb Debugging from Developer Options and run Dirtycow Script - FULL GUIDE at
https://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236
4. The Only Shepard for flashing Xperias EVEN when Sony's own Xperia Compainion Fails (many times) to flash your device is THE FLASHTOOL, www.flashtool.net , once boot is unlocked! sony will no longer recognize your device. Flashtool has inbuilt Xperfirm and you can download firmwares of all device across time (selective)
(literature)
. A very Promising Detailed, Library level guide by @DHGE on DRM KEYS CONCEPT at https://forum.xda-developers.com/showpost.php?p=70504721&postcount=2
YasuHamed said:
Third generation of Oreo for Sony X is less horrible .2.50 but still heatsup more than Nougat and starts hanging, lagging. Since I reside in a country where its 45C usually,for me Nougat .0.252 (came dec2017) was the best rom!
Click to expand...
Click to collapse
That's strange. My phone was fast as hell on all of the Oreo ROMs. Maybe I haven't noticed any heatups, because I have the latest revision (and mfg date is 06.2017) and everything is OK with the hardware there, so it just CAN'T heat up in my case...
Anyways, maybe you should try XGEN + FSC + Debloater?)
Gray47Maxx said:
That's strange. My phone was fast as hell on all of the Oreo ROMs. Maybe I haven't noticed any heatups, because I have the latest revision (and mfg date is 06.2017) and everything is OK with the hardware there, so it just CAN'T heat up in my case...
Anyways, maybe you should try XGEN + FSC + Debloater?)
Click to expand...
Click to collapse
I am actually on Xgen which is built on latest! its bit cooler and makes me survive the lagging!
the temperature in my country goes up to 50C
A few suggestions:
Turning off notifications:
(not certain it applies to those "forced" notifications by the update app, but I suspect if you disable the "fota service" and "fota application" [search for similar terms] it'll stop being displayed)
https://www.digitaltrends.com/android/how-to-turn-off-notifications-in-android/
https://www.techadvisor.co.uk/how-t...how-disable-notifications-in-android-3614881/
In any case - you can attempt to disable the (most likely) offending apps, being the "fota" components via adb:
(for this you need to enable "USB debugging" via "developer options": Settings -> about phone -> Build number -> Tap 7 times)
https://www.reddit.com/r/Android/comments/3eav7t/get_rid_of_unwanted_system_apps_adb_shell_pm_hide/
https://forum.xda-developers.com/lg-g3/general/disable-apps-root-disabled-disable-t3491624
https://android.stackexchange.com/questions/56620/enable-and-disable-system-apps-via-adb
Doing it the root way would be installing Magisk (= root) and purchasing & installing "Titanium Backup root" + the "Titanium Backup PRO Key root".
https://forum.xda-developers.com/xp...peria-x-to-t3785135/post76404647#post76404647
How exactly to do that:
others please chime in
Hope that helps in any way
zacharias.maladroit said:
In any case - you can attempt to disable the (most likely) offending apps, being the "fota" components via adb:
(for this you need to enable "USB debugging" via "developer options": Settings -> about phone -> Build number -> Tap 7 times)
https://www.reddit.com/r/Android/comments/3eav7t/get_rid_of_unwanted_system_apps_adb_shell_pm_hide/
https://forum.xda-developers.com/lg-g3/general/disable-apps-root-disabled-disable-t3491624
https://android.stackexchange.com/questions/56620/enable-and-disable-system-apps-via-adb
Click to expand...
Click to collapse
That's what I was looking for. IMHO this is the best variant if you don't want to upgrade or unlock your bootloader. You should give it a try!
Do not worry
good afternoon
Since you have a "limitation" I will try to guide you as best as possible in what you want to do.
I do not know how the "spectrum of autism" works, but if I'm too technical, you can mention it and I can try to break down a bit more what I'm trying to say.
First, Sony as a company that creates devices with "updates" will always sell the idea that the updates are irreversible, is common and normal in the software and telecommunications companies so it goes without saying that they "destroyed your phone " second: no, it was not necessary to buy another phone, with which you had the problem could be solved only if it is normal that among "non-technical" users are at a crossroads when updates make notable changes to the system and often create confusion.
Now, your simplest solution is to find a trustworthy technical service that can return your phone to a later version for which you are more familiar. probably this version is the initial with which the phone came at the time of its release to the market, in this case with xperia x was 6.0.1 named with its own name as "marsmallow".
then, if what you want is to try to solve it for yourself there is a lot of information in this forum, very helpful and in some cases quite explained so that less experienced users manage to make various changes or modifications to their phones.
take it easy, an update does not damage your phone, it is understandable that you feel fear or disappointment but these things that you tell us that happened to you with your phone have a solution, if you want more information I can help you through this means. or you can read and inform yourself about everything that goes with it.
Finally, words like: fastboot, root, flashtools, are just slang for processes that are not usually so complicated, there are even videos on YouTube that explain them very detailed.
luck and I hope your problem can be solved :laugh:
PS: I'm sorry for my bad English
winsters said:
good afternoon
Since you have a "limitation" I will try to guide you as best as possible in what you want to do.
I do not know how the "spectrum of autism" works, but if I'm too technical, you can mention it and I can try to break down a bit more what I'm trying to say.
First, Sony as a company that creates devices with "updates" will always sell the idea that the updates are irreversible, is common and normal in the software and telecommunications companies so it goes without saying that they "destroyed your phone " second: no, it was not necessary to buy another phone, with which you had the problem could be solved only if it is normal that among "non-technical" users are at a crossroads when updates make notable changes to the system and often create confusion.
Now, your simplest solution is to find a trustworthy technical service that can return your phone to a later version for which you are more familiar. probably this version is the initial with which the phone came at the time of its release to the market, in this case with xperia x was 6.0.1 named with its own name as "marsmallow".
then, if what you want is to try to solve it for yourself there is a lot of information in this forum, very helpful and in some cases quite explained so that less experienced users manage to make various changes or modifications to their phones.
take it easy, an update does not damage your phone, it is understandable that you feel fear or disappointment but these things that you tell us that happened to you with your phone have a solution, if you want more information I can help you through this means. or you can read and inform yourself about everything that goes with it.
Finally, words like: fastboot, root, flashtools, are just slang for processes that are not usually so complicated, there are even videos on YouTube that explain them very detailed.
luck and I hope your problem can be solved :laugh:
PS: I'm sorry for my bad English
Click to expand...
Click to collapse
your English is perfect <3 WOW!
please convert my graffiti, gibberish instructions to your perfect English Guide <3
1 . https://forum.xda-developers.com/showpost.php?p=72141176&postcount=7 ( wrote few months ago)
2. https://forum.xda-developers.com/showpost.php?p=76429289&postcount=7 ( wrote recently)
3. https://forum.xda-developers.com/showpost.php?p=76484508&postcount=2 ( wrote recently)
Gray47Maxx said:
That's strange. My phone was fast as hell on all of the Oreo ROMs. Maybe I haven't noticed any heatups, because I have the latest revision (and mfg date is 06.2017) and everything is OK with the hardware there, so it just CAN'T heat up in my case...
Anyways, maybe you should try XGEN + FSC + Debloater?)
Click to expand...
Click to collapse
I am too facing problems in oreo, and will probably go bak to 6 for more mods / better battery life
Related
Hello, just got my Z4 after my old Z just got in the hand of my 2-year old son
I had rooted and installed a custom rom on that one (CM 12), but I never bothered with Sony own "things" such as the Bravia engine and all.
Now, given that there are not yet any interesting roms for the Z4 and that the developers' scene has never been so active for Sony's products (hence we won't probably see anything interesting for a while, in terms of rom), what are the true disadvantages of JUST rooting the device to install stuff like adaway, titanium backup and the rest of the goodies that rooting allows? Will I lose OTAs by simply unlocking the bootloader and rooting? Since the TA partition will be gone forever, what else are the side-effects of the rooting procedure?
Thanks for any help to a semi-noob.
Luca
astrovale said:
Hello, just got my Z4 after my old Z just got in the hand of my 2-year old son
I had rooted and installed a custom rom on that one (CM 12), but I never bothered with Sony own "things" such as the Bravia engine and all.
Now, given that there are not yet any interesting roms for the Z4 and that the developers' scene has never been so active for Sony's products (hence we won't probably see anything interesting for a while, in terms of rom), what are the true disadvantages of JUST rooting the device to install stuff like adaway, titanium backup and the rest of the goodies that rooting allows? Will I lose OTAs by simply unlocking the bootloader and rooting? Since the TA partition will be gone forever, what else are the side-effects of the rooting procedure?
Thanks for any help to a semi-noob.
Luca
Click to expand...
Click to collapse
Apart from the minor Sony stuff that gets lost with the TA partition, I think I read you'll indeed lose the OTA updates abd the only way to upgrade your ROM is with Flashtool (from flashtool.net). Which is also no big deal, really. Just inconvenient, especially on Windows 8+, which you'll have to boot into a mode in which it accepts installation unsigned drivers needed for the tool.
Another potentially big disadvantage is warranty-related, of the bootloader unlocking. Depends on country and vendor.
Thanks a lot for your help Jelbo. Don't worry too much about using flashtool (done already). I remember though that there used to be a tool to backup TA partition. I'll look into it, but I guess that, if it's not here....
Never worried about warranty as well. I just hope I'll be lucky, I guess!
jelbo said:
Apart from the minor Sony stuff that gets lost with the TA partition, I think I read you'll indeed lose the OTA updates abd the only way to upgrade your ROM is with Flashtool (from flashtool.net). Which is also no big deal, really. Just inconvenient, especially on Windows 8+, which you'll have to boot into a mode in which it accepts installation unsigned drivers needed for the tool.
Click to expand...
Click to collapse
:crying::crying::crying: Another drawback which I haven't known. Meybe it's more comfortable to use virtual machine with flashtool.
astrovale said:
Thanks a lot for your help Jelbo. Don't worry too much about using flashtool (done already). I remember though that there used to be a tool to backup TA partition. I'll look into it, but I guess that, if it's not here....
Never worried about warranty as well. I just hope I'll be lucky, I guess!
Click to expand...
Click to collapse
Backing up your TA is only possible when you have acquired root on your device without unlocking the bootloader. This is impossible as of now on the Z4 Tablet. Well, technically it might be possible, but no one has found an exploit yet. Maybe one will be found someday, but I wouldn't wait on it.
alex009988 said:
:crying::crying::crying: Another drawback which I haven't known. Meybe it's more comfortable to use virtual machine with flashtool.
Click to expand...
Click to collapse
Haha, don't see things so badly. There's lots to enjoy on the Z4T right now.
Running Flashtool with the flashmode driver in a VM is impossible I think. The driver thing on Windows 8+ is really easy tough.
Thanks Jelbo. I went and researched the subject and the first I read was that you need to be rooted to backup your TA partition (indeed I used for my Z the doomlord tool). Well, I guess I'll wait as much as I can, but I really miss adaway most: I hate those ads everywhere cluttering my apps!
Eventually, I'm afraid I'll root and forget about it! I was just wondering also what is the meaning of loosing the bravia engine, but I'll research that too and see. All I know is that I guess I lost it on my Z...but never missed it anyway, so I guess it isnt' that fundamental to enjoy a good tablet like the sony Z4!
Bye
Luca
astrovale said:
Thanks Jelbo. I went and researched the subject and the first I read was that you need to be rooted to backup your TA partition (indeed I used for my Z the doomlord tool). Well, I guess I'll wait as much as I can, but I really miss adaway most: I hate those ads everywhere cluttering my apps!
Eventually, I'm afraid I'll root and forget about it! I was just wondering also what is the meaning of loosing the bravia engine, but I'll research that too and see. All I know is that I guess I lost it on my Z...but never missed it anyway, so I guess it isnt' that fundamental to enjoy a good tablet like the sony Z4!
Bye
Luca
Click to expand...
Click to collapse
You won't miss the image 'enhancements' that are lost, especially when you care for color accuracy.
A cool thing I found out is that the Z4T supports 'KCAL', which enables you to tweak all kinds of image parameters using a tool like Kernel Adiutor.
Apart from killing ads, the thing I'm second most happy about with being rooted is the ability to permanently hide the soft keys using a build.prop edit, while keeping the ability to type anywhere. I mapped the back and home controls to sliding gestures from the left and right screen edges using a GMD app.
ok so please be gentle here, coming back here after 7 years, from old Windows Mobile days!
I am a newbie to Android and want to root my Z5 compact. The only reason I want to root it is to enable some apps like Greenify and GSam battery monitor to work with all their features enabled. I do not want to flash a new ROM. I am happy with Sony's stock ROM.
Is it possible to get root access without installing / flashing a new ROM?
I have searched the internet but people talk about flashing every time I read about rooting. Then I also saw this thread: http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
Lots of geeky stuff there which is fine, but again, it seems to talk about flashing the ROM, which I really do not want to do or do not see the need (yet).
Unlock boot loader:
I see that Sony lets me unlock the boot loader from their dev site. I am willing to unlock the boot loader. (Not sure if I want to do that first. Maybe unlocking BL is all I need?)
rajdude said:
ok so please be gentle here, coming back here after 7 years, from old Windows Mobile days!
I am a newbie to Android and want to root my Z5 compact. The only reason I want to root it is to enable some apps like Greenify and GSam battery monitor to work with all their features enabled. I do not want to flash a new ROM. I am happy with Sony's stock ROM.
Is it possible to get root access without installing / flashing a new ROM?
I have searched the internet but people talk about flashing every time I read about rooting. Then I also saw this thread: http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
Lots of geeky stuff there which is fine, but again, it seems to talk about flashing the ROM, which I really do not want to do or do not see the need (yet).
Unlock boot loader:
I see that Sony lets me unlock the boot loader from their dev site. I am willing to unlock the boot loader. (Not sure if I want to do that first. Maybe unlocking BL is all I need?)
Click to expand...
Click to collapse
The only reason to use that guide is to backup ta keys for whatever reason you'd want to do that.
If you're after root on stock ROM the single easiest way is to unlock bootloader, flash twrp 3.0.2, flash xpower 3.0, and that's it. Solid marshmallow with root goodies. Xpower has everything and is deodexed and ready for xposed framework.
just a little more clarification please?
civicsr2cool said:
.....easiest way is to unlock bootloader, flash twrp 3.0.2, flash xpower 3.0, and that's it. ......
Click to expand...
Click to collapse
Ok thanks.....that sounds straight forward.....but isn't TWRP a ROM? (sorry, the moment I hear flashing...I think ROM)
And I am looking up xpower...not sure what that is (yet) and why do I need it
I do want xposed framework though.
I wish there was a simple straightforward answer
rajdude said:
Ok thanks.....that sounds straight forward.....but isn't TWRP a ROM? (sorry, the moment I hear flashing...I think ROM)
And I am looking up xpower...not sure what that is (yet) and why do I need it
I do want xposed framework though.
I wish there was a simple straightforward answer
Click to expand...
Click to collapse
Twrp is your recovery,you flash through fastboot, xpower 3.0 is the ROM, just a pre-modded stock ROM with options of xperia x addons. Use lite and stock kernel for xpower and you'll be set.
still a little confused
civicsr2cool said:
Twrp is your recovery,you flash through fastboot, xpower 3.0 is the ROM, just a pre-modded stock ROM with options of xperia x addons. Use lite and stock kernel for xpower and you'll be set.
Click to expand...
Click to collapse
Ok thanks! So my understanding (so far) is :
We "must" flash a ROM in order to root a phone. Did I get that correct?
Since I said I like the stock Sony ROM, you recommended the xpower 3.0 ROM.........but the point is.....I still have to flash ROM.
A little confused here...
I am a systems engineer (my day job). In Linux or Windows OS, if we want root access (to run some software or a low level command, like partitioning a disk etc), we either run SU command and put root's password OR right click and run as administrator......
We never have to install a brand new Operating System to get root access.
Just a total newbie question.....Why do we have do install a whole new OS (flash new ROM) on our Android phones to get root access?
rajdude said:
Ok thanks! So my understanding (so far) is :
We "must" flash a ROM in order to root a phone. Did I get that correct?
Since I said I like the stock Sony ROM, you recommended the xpower 3.0 ROM.........but the point is.....I still have to flash ROM.
A little confused here...
I am a systems engineer (my d Linux or Windows OS, if we want root access (to run some software or a low level command, like partitioning a disk etc), we either run SU command and put root's password OR right click and run as administrator......
We never have to install a brand new Operating System to get root access.
Just a total newbie question.....Why do we have do install a whole new OS (flash new ROM) on our Android phones to get root access?
Click to expand...
Click to collapse
Android is Linux, to gain root in the ROM you have on your phone currently all you need is an unlocked bootloader to run SU, but then you'll be left with a phone that still needs a customized kernel to keep root and a DRM fix for the camera. Xpower 3.0 is that package.
You could really benefit from reading more. Google up on dm-verity and Sony Ric, and fastboot/adb for a little better understanding of what you're getting into without a pre compiled ROM. Messing around with any Android you'll have the majority of the same steps, unlock bootloader with fastboot, flash Supersu, customized kernel.. Etc
Why use a stable compiled ROM?
Let me list down and explain to you why it's best to use a stable compiled ROM. But first you need to understand these few things before you decide to unlock your bootloader and root.
Before Sony Z models kicked in, every rooted Sony device are still able to retain all the features that came together with the phone before it was rooted. When Sony introduce the first Z model, they start to create these things called DRM keys. DRM keys are unique algorithm (i guess i should put it that way) which is attached to every phone the same way an IMEI number is attached to every phone. In short, my DRM keys cannot be used on your phone and vice versa.
DRM key: It's a unique algorithm that holds all the unique features that an unrooted Sony phone boast such as camera quality, X-reality, High Res Audio etc etc.
The moment you unlock your bootloader, that's the moment your DRM keys will be lost. But don't panic, the wonderful devs on XDA have prepared a tool to backup your TA partition (a partition that contains your DRM key) for your own convenience if you want to relock your bootloader.
Then recently Sony/Android come up with new features called Sony RIC and dm-verity. (You may Google what these are all about but to my understanding it is placing limitations to people who root their phones to meddle around with the system settings of thier phone)
With all these "hurdles", it have taken some time for devs here to find a work around and like every fairytale ending, they manage to find a way.
Now you're wondering if you can actually root without flashing another rom. Good news for you: you can! There's a guide that will teach you how to actually root and apply the work around after unlocking your bootloader and rooting.
.. But ask yourself what's the point of going through the hassle of rooting and your phone is not tweaked for performance or for theming purposes?
That's when people flash roms and in Z5 compact's case, XPower is the best rom there is. It gives you all the performance tweak you need to make your phone lag free, it has a lite version that removes all the unnecessary system apps you can't delete without root, it gives you an option to add themes and framework from Xperia X with all those work around in place.
For your second question: why is there a need to install TWRP?
TWRP is a recovery tool which is a need for all rooted phone. It's also a tool for you to backup and restore your current rom so that you can rollback to the last working configuration if your phone went into a bootloop etc. Plus i believe all these guides require you to actually use TWRP to flash the SuperSU to successfully root your phone.
I hope this explains your doubts.
Thanks a lot but...
firdyRAY, thanks a lot for the comprehensive reply to my questions. And yes, it has shed a LOT of light on my doubts.
I googled Sony RIC and dm-verity:
I could not get find much on ric
Dm-verity seems to me a way to check if the boot image has been modified from the last boot, and if it has, stop from booting. Sounds like a good idea until we understand that to flash a ROM dm-verity needs to be bypassed/turned off.
So to compile what I have understood so far:
By unlocking bootloader, you lose DRM keys. There is a way to backup DRM keys which are in the TA partition, but this is to be done BEFORE you unlock bootloader. Good that I have not done anything to my X5c yet.
The next steps for me would be to look into XPower 3 ROM…which I did and here is what I found out:
http://forum.xda-developers.com/z5-compact/development/rom-xpower-v1-0-aroma-debloat-custom-t3371100
First, what's up with the scary looking warning in RED right at the top of the first thread. I did read the OP and the second post, I did not see anything in there which IF I missed will cause my phone to explode! That is probably posted to make noobs read all instructions, right?
Second, I do not see any step in there to backup the DRM / TA partition. I guess the dev is assuming the phone already has lost the DRM, right? So I gotta find instructions on how to backup DRM / TA
Then I searched for problems in this ROM and seems to me that the fingerprint sensor is reported by many to be not working and/or buggy. I rely on the fingerprint sensor day and night. I have many apps which rely on that, like lastpass. That would be a major deal breaker for me.
So going back to stock ROM option…I remember you said "There's a guide that will teach you how to actually root and apply the work around after unlocking your bootloader and rooting."
Could you please post a link to that?
Thanks again!
I think this is a pretty great thread rajdude. It's getting people to spell out a lot of information to noobs like us that it seems most posters have taken for granted over time.
I'm a complete novice at all of this. Sort of gleaning information as I go along, but I used this guide: http://twigstechtips.blogspot.hk/2016/04/sony-z5-compact-root-without-losing-ta.html?m=0
Along with this guide: http://forum.xda-developers.com/xperia-z5/general/guide-rooting-unlocking-bootloader-t3354307
The first guide is pretty basic step-by-step instructions. It unfortunately occasionally kind of skips over a couple very small things (that will be clear as you go along), or occasionally words things in such a way that might not be completely intuitive, but maybe that's cause I need things explained to me like I'm five sometimes. Any time I might have had a question about something in the the first guide, I went to the other and found the answer. It didn't take me long to get the gist of the whole thing though, and overall, it wasn't as scary as I thought it was going to be. It'd be fantastic if someone created a video walkthrough, but so far as I know, no one has done that yet.
The guide will help you back up your TA Partition where your DRM keys are stored, unlock your bootloader, root your device, and then restore your DRM keys. In order to do this you need to downgrade to Lollipop (if you're not already on it), and then upgrade back up to Marshmallow. It will also install TWRP (which I had no clue was installed until I went into "recovery mode" by pressing UP when I saw the LED flash yellow during boot). There may be an easier way to go about this whole process, but this is the process I used.
Before jumping into anything, I'd hold off until you heard more from firdyRAY or someone more experienced. They may look at the guide I linked and be horrified.
And yeah, I haven't installed xpower yet for the same reasons you haven't. Sounds like there's even an xpower 4.0 that was released recently, but still seems kinda buggy. Being rooted with stock I've been able to give Greenify access to root. Install Adaway (which was worth getting root to begin with). Install sound/music mods like DiVA-X, Viper4Android and Dolby Atmos. Install Titanium Backup. And make a few other minor tweaks (that I've since reversed). I still don't know much about custom ROMs and all that jazz, so I'm holding off until I get more understanding. I'd love to install the xpower ROM (when the bugs are worked out), and maybe some sort of sound ROM. I also need to get more understanding on some of the other vernacular like what exactly a "dirty flash" is.
rajdude said:
firdyRAY, thanks a lot for the comprehensive reply to my questions. And yes, it has shed a LOT of light on my doubts.
I googled Sony RIC and dm-verity:
I could not get find much on ric
Dm-verity seems to me a way to check if the boot image has been modified from the last boot, and if it has, stop from booting. Sounds like a good idea until we understand that to flash a ROM dm-verity needs to be bypassed/turned off.
So to compile what I have understood so far:
By unlocking bootloader, you lose DRM keys. There is a way to backup DRM keys which are in the TA partition, but this is to be done BEFORE you unlock bootloader. Good that I have not done anything to my X5c yet.
The next steps for me would be to look into XPower 3 ROM…which I did and here is what I found out:
http://forum.xda-developers.com/z5-compact/development/rom-xpower-v1-0-aroma-debloat-custom-t3371100
First, what's up with the scary looking warning in RED right at the top of the first thread. I did read the OP and the second post, I did not see anything in there which IF I missed will cause my phone to explode! That is probably posted to make noobs read all instructions, right?
Second, I do not see any step in there to backup the DRM / TA partition. I guess the dev is assuming the phone already has lost the DRM, right? So I gotta find instructions on how to backup DRM / TA
Then I searched for problems in this ROM and seems to me that the fingerprint sensor is reported by many to be not working and/or buggy. I rely on the fingerprint sensor day and night. I have many apps which rely on that, like lastpass. That would be a major deal breaker for me.
So going back to stock ROM option…I remember you said "There's a guide that will teach you how to actually root and apply the work around after unlocking your bootloader and rooting."
Could you please post a link to that?
Thanks again!
Click to expand...
Click to collapse
sony ric is a layer of security for sony roms so that they can protect nfc and fingerprint stuff. samsung and htc have there own variants as well.
yes lol the big red lettering is there to make you read, although hes not far off on the melting your phone part, the s810 is ridiculously hot.
the xpower thread doesnt not include the drm backup instructions because: 1) you need bootloader unlocked to flash it. and 2) because it includes the drm fix in it so you dont have to backup your ta keys.
the fingerprint sensor bug is on any bootloader unlocked phone, the hardware fails after x amount of hours and requires a reboot to work again. xpower is a stock rom, the only thing different is its pre-rooted, de-bloated, and deodexed for xposed to work. we have a separate thread for the fingerprint sensor bug and its been solved.
rajdude said:
firdyRAY, thanks a lot for the comprehensive reply to my questions. And yes, it has shed a LOT of light on my doubts.
I googled Sony RIC and dm-verity:
I could not get find much on ric
Dm-verity seems to me a way to check if the boot image has been modified from the last boot, and if it has, stop from booting. Sounds like a good idea until we understand that to flash a ROM dm-verity needs to be bypassed/turned off.
So to compile what I have understood so far:
Click to expand...
Click to collapse
Sony RIC main function is to disable /system write even you got root permission(you still able to do /system write but after a reboot will restore to original). There is a workaround but very trouble, TWRP recovery file manager can bypass Sony RIC(it works in the old day for me, not sure about now). BTW, all 3rd kernel should be disabled RIC nowadays. For any regular computer, there is no hardware or software lock to prevent you gain root access in linux but there are many such trouble stuffs in the android world... lol
I'm running XPower 3.0 Full as a daily driver since June and been very happy. Battery life, stability and speed is good.
Please note, that you MAY lose your warranty when you lose your DRM keys. That's why I didn't unlocked my phone before there was a way to backup TA partition. Now I'm after warranty repair, and before it I was able to fully restore stock ROM with DRM and all features fully functional. In my country, there is only one Sony approved repair center and they check DRM keys before repairing anything - even if it's mechanical fault.
When I had Z1c in KitKat days, it didn't had dm-verity and Sony RIC. It was possible to gain permanent root with bootloader locked, so I was happily using stock ROM and kernel. In Z5c case, first thing I tried was to do the same and it was possible (just backup TA, unlock bootloader, and flash TWRP with patched kernel (dm-verity and Sony RIC disabled) to begin with), but going XPower way was much more confident - I didn't had to think about removing every bloat app. I just flashed lite version in June and I'm using it till this day without any problems at all
Another thing is that you lose OTA (Over-The-Air Update) functionality when you unlock bootloader and disable Sony RIC and dm-verity. Updating to newer versions of firmware, even on stock ROM is problematic when you modify it.
michuroztocz said:
Another thing is that you lose OTA (Over-The-Air Update) functionality when you unlock bootloader and disable Sony RIC and dm-verity. Updating to newer versions of firmware, even on stock ROM is problematic when you modify it.
Click to expand...
Click to collapse
It's simply not possible. If you are rooted you can't apply OTA updates and neither should you.
flopower1996 said:
It's simply not possible. If you are rooted you can't apply OTA updates and neither should you.
Click to expand...
Click to collapse
That's just what I wrote - just put it in another words
Good morning
Been playing with my new Z5C for a week now and amongst all the things that i like about it (size, weight, responsiveness, ease of use) i have to say that i am not satisfied with its battery (thats why i bought it) and the fact that i really i miss my silent button on my old iphone!
Searched the forums for a solution, especially for the battery and i realized that i have to Root my device since Greenify does not offer me the battery extend i wish. I am not good with tech and hacking so i would like to check if there is any secure and working 'root 101 for dummies' that i can refer to, for solving my issues and getting rid of all those factory installed apps that i have no use for. I dont want paly around all day on my phone, i want it to be fast, light in background process and with a good battery.
Thanks for all the help and advise. Have a good month everybody
AndreasE
Not really. In this forum you can already find different guides about how to root your device and also about how to make a backup of your TA-partition if you want such backup before unlocking your bootloader.
But rooting your phone isn't anything (at all) for dummies, and there is no one-click-solution for most of the possible issues. And it won't be secure, because you're dealing with highly experimental software and "hacks". This means your phone could get (much) more unexpected behavior.
http://forum.xda-developers.com/z5-compact/general/how-to-backup-restore-ta-partition-root-t3479532
There are honestly no good instructions that can take even someone familiar with rooting through the process. When I first got the Z5C, I tried rooting it and made a mistake when backing up my TA. Thank god the phone was still under warranty. If you find it difficult, don't do it. It's not very simple.
The steps are actually quite simple.
1. Downgrade to LP to backup TA partition.
2. Upgrade to MM.
3. Unlock bootloader
4. Flash either custom kernel or stock (patched) kernel
5. Flash supersu.
6. Done.
DEPRECATED
This firmware is old and deprecated.
See the below link for new firmware and a better root method.
https://forum.xda-developers.com/galaxy-s8/development/root-partcyborgrom-aqi6-deodexed-t3702988
You can just flash the BL_ tarball if you don't want to install a new system
but want the better screen and modem drivers.
PART 2: FIRMWARE RELOADED
I have done extensive research into the issues reported by those of you who are still experiencing screen issues.
I was unable to reproduce the screen issue on my then-current firmware with this update.
Not being content to leave people with buggy screens, I learned as much as I could about the s8 firmware.
This is what I did with that information.
Flashable Custom Firmware Package For ALL SM-G950U/U1 ON US CARRIERS
If you have a non-us G950U and want to install this pm me or ask in the thread and ill make one. Its very simple but I wanted to get this out to everyone else ASAP
NOTICE!
This an UPDATE (and More) to the Green/Garbled Screen Issue firmware.
There is NEW firmware to download below, and everyone who is rooted should read on, even if you installed the previous version.
Background
At the core of the issue with the garbled screen, modem panics, and sd card issues are two central themes: Bugs, and Incompatibilities. The S8 family of phones was fraught with issues early in its release, including the infamous "Red Tint', Fingerprint scanner malfunctions, mysteriously poor battery life, and surely a bunch of smaller others. Many of these bugs were caused by issues in the device's underlying firmware. Like most devices, Samsung has worked to fix these bugs and improve device performance throughout the phones lifetime for sale in public.
Root Bugs
The problem was unfortunately worse for users of one of the rooting methods for the S8. The biggest reason for this is that in order to relax security constraints enough to make rooting possible, a "non-user oriented", "factory" combination firmware was used. This firmware, being designed apparently for configuration/repair processes inside a factory, was not tuned to the normal level as the public firmware, likely did not go through the same testing, and ultimately any bugs unique to this "Combination" firmware that did not directly affect basic functionality or also stock were probably largely initially ignored.
This is where most of the issues that you all have had come from.
Finding a Solution
As I was unable to reproduce the issue on my device without resorting to the original firmware shipped out with the root method I used, I decided to think about what made my device different than the other devices reporting these issues. While sure we may have slightly varying hardware and that may contribute to these issues as well. What I am absolutely certain of is that most of us have different releases of software from each other. Not only have people essentially ad-hoc upgraded from the original firmware they rooted with until now, many have not upgraded at all or, only partially upgraded (such as with the pervious version of this).
While I could have simply packaged up my firmware/bootloader flashfire backup, I decided to take it a step further.
THE GOODS
Without further ado, I present to you:
S8Root Improved: A SM-G950U1 Custom Firmware Package for Root Users
This package contains a custom mix of the latest AQH3 STOCK (not combination) firmware used wherever possible with the Necessary boot/kernel images from the combination firmware necessary to keep root working with permissive SELinux. It contains all of the improvements from the previous version, and many more.
RESULTS
I can only speak for myself, but the results I experienced were amazing:
- Better UI Responsiveness.
Things surprise me how they move
- Sharper/brighter screen colors
I thought it couldn't get better than the last version but it has! Everything just looks crisper and are super bright without being oversaturated like with the Adaptie Mode.
- POSSIBLY Improved LTE network connectivity.
Note I said POSSIBLY. I personally regularly experienced 8-10Mb/s download bumps and 2-3Mb/s upload bumps in LTE while moving back and forth from this new firmware. I have my LTE radio locked to a specific channel (there are two i pick up at my place and one is terrible) and I carefully measured -107 to -112 dBm RSRP and -13 to -14 dB RSRQ prior to each measurement. I almost left this out but I figured it would be better to give you the information with no conclusion either way. It ABSOLUTELY could be Atmospheric changes, Traffic level changes, or any other of a million thins. YMMV
- Could POTENTIALLY still any remaining fix long-standing SDCard issues
I did not experience this, but had a few reports from users that did. The same pieces used in that version that would touch SDcard usage are used here, so that fix/improvement will carry over.
DISCLAIMER
Unfortunately proving beyond any shadow of a doubt that this package fixes the issue was impossible . I have TRIED AND TRIED AND TRIED to trigger the screen issues, including tweaking on and off every setting (auto brightness, multiple DPIs, different graphs modes, etc) I could get my hands on and it just was not happening. I used every software/systems trick I could think of to break this again, and I was completely unable to tickle the bug on this firmware, despite being able to reliably trigger it almost on command using my previous firmware.
The only thing left to do is either:
- Get the source from samsung, fix the bug myself, and get them to sign my new kernel image with their key so our locked bootloaders would allow it (HAHA I DOUBT IT)
- Acquire a large fleet of S8s (and S8+s) to run distributed integration testing (like the kind Android use at Google). Well if someone wants to buy me a few dozen s8s and s8+s (each) sure I'll take a month off work and squash this, but otherwise not gonna happen either.
If it STILL happens for you, I'm sorry.
I have done everything I can think of, and if it happens to you and you have suggestions, I'm all ears.
BUT HEY, but this is XDA right? Land of mods like Xposed which will brick one persons device and work flawlessly on the identical one next to it. And we love Xposed don't we?
Despite absolutely hilarious comments to the contrary, this package absolutely meets the (aka "BugFix") as well as just about any android update ever does, given the wide variety of environments, usecases and software configurations out there. I surely hope that this works for you.
Instructions
1) Download the package from the link above.
- Here it is Again for good measure.
2) Reboot into download mode and flash using Comsy Odin
Thats it! I packaged this in a way to make the process as smooth as possible.
There is NO reinstall, NO wipe of any kind, nor ANY further work on your part needed to install and use this.
The file size is small so the download is fast, and again, there is NO WIPE or config change needed.
if (for some inexplicable reason) you want to roll back, or go to 100% stock sans root, that process should not be made any more difficult as well.
Legacy Information
If you were here before and either looked at or downloaded the previous version, AND YOU HAVE NO QUESTIONS you can skip this part.
If you have questions, please read through to the end of the post before asking them, as I tried to answer as many as I could before hand and all of this information still applies.
WHAT IT IS NOT:
I wanted to outline a few things it is NOT about, to make a valliant effort to stem off the flow of questions before they begin (ha!):
NOT: A new Stock ROM for Your Phone
THIS IS NOT A FULL OS BUILD! DO NOT DOWNLOAD THE WHOLE THING AND FLASH IT EXPECTING AN ENTIRELY UPGRADED OS.
There is no full stock AQI1 image I have found. Believe me I looked a bunch of places after I found it
NOT: Oreo Early Preview
Given the predictions that the next release from Samsung would likely be Oreo, there was some initial over excitement. This wound up being NOT the case and if you read at least current Samsung Oreo projections they are predicting AQB now.
NOT: A Fix for the 80% Battery Issue
I know this is completely futile to hope for but:
THIS DOES NOT FIX THE 80% BATTERY ISSUE!!!!
NO WE DO NOT HAVE A FIX FOR THAT OR ONE COMING ANY TIME SOON!
YES SOME PEOPLE ARE STILL TRYING!
PLEASE DO NOT ASK! OFF TOPIC FOR THS THREAD
NOT: Currently Tested by ANYONE but ME
Since the moment I installed this I have not had ONE SINGLE screen issue, where previously I would have them several times throughout the day (at least 3 sometimes upwards of 6). For the case of ME and MY device, I am confident in declaring that this boot ROM does not have the same kernel bug that was causing the issue on the boot.img provided as part of your traditional root method.
NOTE: This is for the s8 G950 US Snapdragon models ONLY! Do NOT Flash this on your exynos, your Chinese/HK S8, your N8, your MOTO RAZR flip phone, whatever else you have. Kernels/boot.img files are very device specific and you will surely break it if not completely brick it.
DISCLAIMER:
YOUR WARRANTY IS ALREADY VOID if you are paying attention and are doing this to fix bugs with the existing sampwnd root.
HOWEVER IT IS EVEN VOIDER NOW. FLASH THUS TO YOUR DEVICE AT YOUR OWN RISK!
and if you break it I AM NOT RESPONSIBLE! FLASH AT YOUR OWN RISK!
As I said I have not tested this anywhere but my phone as I dont have any other s8s nor do I have access to any locally. I hope it works for you as well as it has for me.
STEPS
Download Boot Image
Use the URL here to Download the AQI1 boot.img file: Go Download the New Hotness
Prepare Phone for Flashing in FlashFire
If you did not download it on your phone, copy it somewhere FlashFire can see it.
Flash it
Open up FlashFire
Hit the "+" button
Select the "Flash Firmware Package" option, NOT the "Flash Zip or OTA" option!
You should see a popup window thing that has a checkbox next to the word BOOT, with "boot.img, 22MiB" underneath.
Make sure the checkbox is checked.
Make sure that it says BOOT above boot.img.
I have no idea if its possible for this to get messed up, but BOOT implies flashing the BOOT partition so if it says something else you are headed towards brick town, abort immediately.
Press the Check mark at the top right corner once you have confirmed the two things above.
MAKE SURE EVER ROOT IS DISABLED!!!
Click on the "Reboot" box, and choose "Recovery". MAKE SURE PRESERVE RECOVERY IS NOT CHECKED!
Back at the main menu, click the lightening bolt next to the word FLASH. Confirm.
Wait for FlashFire to do its thing. Sometimes it takes a minute for FF to wake up and start flashing. Occasionally for me it never happens, if this happens DO NOT PANIC ITS FINE. Hold down power+volDown until you eventually wind up in upload mode, then just reboot normally and everything will come back fine.
When FlashFire finishes (it will go really fast, the image is only 22MB we arent flashing a 5GB system here), it will auto-reboot your device into the recovery men
Select Wipe Cache and Confirm
This will wipe cache which is fine and safe. Again maybe not needed, feel free to skip if you know what you are doing. If you mess up and accidentally click factory reset instead, please tell me so I can laugh at you.
Reboot into a Clear New World
Select reboot and boot the system normally. If you formatted the cache partition above, it will take a little longer to start your phone. This is just the first time per normal.
Thats it! Welcome to the world of clear screens and bright colors. It could be a total placebo effect but I actually think this kernel drives the display better sometimes.
Please let me know what you think, and if this works for you. I wi;; be here for a while to answer questions or fix anything i typoed above or whatever.
FYI: A s8+ thread is coming too, as I sprung for purchasing both downloads to be an equal opportunity XDAer (at least with US flagship Samsung devices lol) but since I have an s8 and thus had the files locally already I made this one first
@jhofseth for nerding out with me the last few nights on trying crazy **** to get a bootloader unlock which prompted me to dig at this in the first place
Most of all, all of the tons of you who have made so many aewesome mods, themes, apps, what have you that I use every day and that make me enjoy my device all the more. I could not be happier to have the opportunity to give back a little.
Here is the restof the s8 combo firm if you are interested, but don't just flash this as its not a full OS:
EDIT: DOWNLOAD THE NEW ONE ABOVE
Can I Get The Link To The S8+ Boot im willing to try it
Mark805 said:
Can I Get The Link To The S8+ Boot im willing to try it
Click to expand...
Click to collapse
Coming very soon I promise! 10m max
Ok thanks
Mark805 said:
Can I Get The Link To The S8+ Boot im willing to try it
Click to expand...
Click to collapse
Its up now! https://forum.xda-developers.com/ga...sampwnd-root-green-screen-corruption-t3673815
whats the bootloader verison? it can be found by booting into download mode manually.
Cameron581 said:
whats the bootloader verison? it can be found by booting into download mode manually.
Click to expand...
Click to collapse
This isn't a bootloader change, it's boot.img which is the kernel and root filesystem essentially
Hey, btw this does not void warranty. I understand it's a standard disclaimer but it doesn't void it. It doesn't trip knox, so warranty is still very intact.
mweinbach said:
Hey, btw this does not void warranty. I understand it's a standard disclaimer but it doesn't void it. It doesn't trip knox, so warranty is still very intact.
Click to expand...
Click to collapse
Uh just because their service does not catch you does not mean that technically you are not violating your warranty contract thus making using technically illegal
That would be like saying "it's not murder if you leave no forensics!" Lol
wildermjs8 said:
Uh just because their service does not catch you does not mean that technically you are not violating your warranty contract thus making using technically illegal
That would be like saying "it's not murder if you leave no forensics!" Lol
Click to expand...
Click to collapse
i mean legally a warranty can not be void through software modifications unless it causes physical damage to the device. Since the efuse was not tripped no physical damage has been caused and no warranties have legally been void.
I had the green screen/graphics corruption after flashing this still...
goliath714 said:
I had the green screen/graphics corruption after flashing this still...
Click to expand...
Click to collapse
Apparently this happens to some people. I am fairly certain it is a firmware combination issue but I haven't been able to track it down. One thing you can do to eliminate it if you have the issue still (please let me know if this does not work) is to disable auto brightness.
wildermjs8 said:
Apparently this happens to some people. I am fairly certain it is a firmware combination issue but I haven't been able to track it down. One thing you can do to eliminate it if you have the issue still (please let me know if this does not work) is to disable auto brightness.
Click to expand...
Click to collapse
I have auto brightness off and still get it here and there.
goliath714 said:
I had the green screen/graphics corruption after flashing this still...
Click to expand...
Click to collapse
Please check out the OP again and download/flash the new version. Rather than just a few files, its a whole new entire bootloader/kernel package that I assembled piece by piece to have as much latest stock firmware as possible while maintaining what we need for root.
My primary suspect for why some people experience this regression is having older parts of their system. Rather than push everyone to upgrade, I made a painless upgrade process for all of their firmware instead
This includes the Radio drivers and bootloaders, kernels and flash layer libraries. Its all either latest stock or its AQI1 Combination because it was absolutely necessary.
wildermjs8 said:
Please check out the OP again and download/flash the new version. Rather than just a few files, its a whole new entire bootloader/kernel package that I assembled piece by piece to have as much latest stock firmware as possible while maintaining what we need for root.
My primary suspect for why some people experience this regression is having older parts of their system. Rather than push everyone to upgrade, I made a painless upgrade process for all of their firmware instead
This includes the Radio drivers and bootloaders, kernels and flash layer libraries. Its all either latest stock or its AQI1 Combination because it was absolutely necessary.
Click to expand...
Click to collapse
We flash the tar in the AP slot correct?
CloudyxVision13 said:
We flash the tar in the AP slot correct?
Click to expand...
Click to collapse
Yep
---------- Post added at 08:29 PM ---------- Previous post was at 08:28 PM ----------
Seems to be running better to me. Thanks bro
CloudyxVision13 said:
We flash the tar in the AP slot correct?
Click to expand...
Click to collapse
It actually does not matter, as Odin will do the right thing no matter what.
Sorry I should have made that clear. I will update the op to make that clear
Just wanna make sure of something. First, I flash the first download files through modded doin, then afterwards, flash the second file in ff?
AngelIsL33T said:
Just wanna make sure of something. First, I flash the first download files through modded doin, then afterwards, flash the second file in ff?
Click to expand...
Click to collapse
Nope, only need the tar file bud. The old boot.img file is just basically the previous version of this.
AngelIsL33T said:
Just wanna make sure of something. First, I flash the first download files through modded doin, then afterwards, flash the second file in ff?
Click to expand...
Click to collapse
The old image is actually part of the new tar, do you will have it anyway . I packaged it in Odin this time because there are some pieces of firmware FF either can't or warns against using it for. Plus one clean simple tar seemed easier, no?
Do you see the boot.img in the op? I thought I nixed all the instances of the link but I may have missed one.
I almost rewrote all the old text to reflect now but it felt like editing history so I tried to preserve what made the most sense still. It sounds like it's still a little confusing sobrskr another crack at it shortly.
Please let me know if you have any trouble! I'll be here to help all evening
Hello guys this guide is for who want to root phone without disabling ota updates.
(BOOTLOODER SHOULD BE UNLOCK)
BIG THANKS FOR MAKING PATCHED BOOT IMg @Jan.Pul
IAM NOT RESPONSIBLE FOR ANY CAUSE OF YOUR DEVICE DO IT ON OWN RISK)
1)Download patched boot.img from link below
2)copy that patched boot.img to your adb folder
3) adb debugging should be on and oem unlock should be on for unlock bootlooder
4)turn off your device and go into fastboot mode by pressing holding volume down and power key
5) check whether fastboot detect your device or not by typing this command on (cmd) FASTBOOT DEVICES
6) if fastboot shows that your device is connected your good to go
7) you need to boot into patched boot.img for this type a command FASTBOOT BOOT patched_boot.img your device will boot automatically
8) download magisk manager apk from google and. Open ur magisk manager and install ad direct method and reboot
If you get bootloop dont worry just press your power key for 5sec it will boot automatically
PATCH BOOT IMG : https://drive.google.com/file/d/1cU6qOMiHlGdSAbRtMVgTlHummcGksnt6/view?usp=drivesdk
Guessing this is for the Indian/Chinese version and the bnd-l24 is still sitting on the shelf? And rooting without making a backup isn't usually the smartest thing to do but we all know that.
Is there a source this came from by any chance?
Yes..But Why?
maximran said:
maximran said:
this guide is for who want to root phone without disabling ota updates.
(IAM NOT RESPONSIBLE FOR AMY CAUSE OF YOUR DEVICE DO IT ON OWN RISK)
Click to expand...
Click to collapse
str8stryk3r said:
rooting without making a backup isn't usually the smartest thing to do but we all know that.
Is there a source this came from by any chance?
Click to expand...
Click to collapse
I Eh... Would Love To See This Happen..
I'm... still at a loss to understand why so many people want to root the 7x... Now?
There is an adaway substitute available... ( Search it if you care to ) no root needed.
You can adjust DPI...
You have Themes....
You can remove apps from user view... ( Search it if you care to )
And.... removing unwanted apps WILL NOT free up more RAM.. RAM Management will just fill the allotted space with something else...
You need to make a backup ??? Eh.... Your Stock Software WILL NOT FAIL Unless you are in there messing with it or, are installing illegal apps that are cancering your unit.
Battery Management apps like Greenify? really? how many of you even have to use the Power Saving options already installed in the 7x? I'm getting a day and a half easy.. without using any of the Power Saving options.. YMMV of course.
Oreo is 3 to 4 weeks away.
There still, is No Stock Image Available from Honor to turn to should your Rooting efforts fail you.
So, What possible benefits are you getting by Rooting Nougat Now..
It's YOUR device.. and I wish you the best of luck should you find a reason that you feel justifies the need to root right now..
I'm going to Root my 7x as well... once a Stock Image is available from Honor and, EMUI / OREO 8.0 , The Updated Security Patch and Facial Unlock / AR options are delivered.. That will hold me for the 6 - 7 months I'll own the 7x.
I am just so curious why so many would gamble with Root.. with no clear cut method of being able to recover from a catastrophe.... and no real benefit at this time.
Click to expand...
Click to collapse
RaiderWill said:
maximran said:
I Eh... Would Love To See This Happen..
I'm... still at a loss to understand why so many people want to root the 7x... Now?
There is an adaway substitute available... ( Search it if you care to ) no root needed.
You can adjust DPI...
You have Themes....
You can remove apps from user view... ( Search it if you care to )
And.... removing unwanted apps WILL NOT free up more RAM.. RAM Management will just fill the allotted space with something else...
You need to make a backup ??? Eh.... Your Stock Software WILL NOT FAIL Unless you are in there messing with it or, are installing illegal apps that are cancering your unit.
Battery Management apps like Greenify? really? how many of you even have to use the Power Saving options already installed in the 7x? I'm getting a day and a half easy.. without using any of the Power Saving options.. YMMV of course.
Oreo is 3 to 4 weeks away.
There still, is No Stock Image Available from Honor to turn to should your Rooting efforts fail you.
So, What possible benefits are you getting by Rooting Nougat Now..
It's YOUR device.. and I wish you the best of luck should you find a reason that you feel justifies the need to root right now..
I'm going to Root my 7x as well... once a Stock Image is available from Honor and, EMUI / OREO 8.0 , The Updated Security Patch and Facial Unlock / AR options are delivered.. That will hold me for the 6 - 7 months I'll own the 7x.
I am just so curious why so many would gamble with Root.. with no clear cut method of being able to recover from a catastrophe.... and no real benefit at this time.
Click to expand...
Click to collapse
Oh I agree with ya. I'm not fooling with mine until a definitive stable method comes out after oreo. I might even hold off until we start getting some custom rooms and kernels. I've unlocked my bootloader and that's about the extent of my Honor 7x modding for the time being.
Click to expand...
Click to collapse
A Question Sir..
str8stryk3r said:
RaiderWill said:
Oh I agree with ya. I'm not fooling with mine until a definitive stable method comes out after oreo. I might even hold off until we start getting some custom rooms and kernels. I've unlocked my bootloader and that's about the extent of my Honor 7x modding for the time being.
Click to expand...
Click to collapse
Have You Tried "Re-Locking" Your Bootloader.. And Then Doing A Factory Reset?
Just asking because.. I thought.. (And I Could Be 100% WRONG) I read somewhere that, relocking using the command line causes the 7x to brick..
Click to expand...
Click to collapse
RaiderWill said:
str8stryk3r said:
Have You Tried "Re-Locking" Your Bootloader.. And Then Doing A Factory Reset?
Just asking because.. I thought.. (And I Could Be 100% WRONG) I read somewhere that, relocking using the command line causes the 7x to brick..
Click to expand...
Click to collapse
No I unlocked the bootloader so I wouldn't have to in the future. Why, bootloader unlocking China cause me to not be able to do ota updates? I was under the impression that only rooting and installing twrp would cause issues with ota but I could've read wrong
Click to expand...
Click to collapse
@maximran, root with Magisk "KEEPFORCEENCRYPT=true"; but if I change to "false", should work too?
str8stryk3r said:
RaiderWill said:
No I unlocked the bootloader so I wouldn't have to in the future. Why, bootloader unlocking China cause me to not be able to do ota updates? I was under the impression that only rooting and installing twrp would cause issues with ota but I could've read wrong
Click to expand...
Click to collapse
True, even I have unlocked my bootloader but I still received OTA.
Click to expand...
Click to collapse
kilroystyx said:
@maximran, root with Magisk "KEEPFORCEENCRYPT=true"; but if I change to "false", should work too?
Click to expand...
Click to collapse
It will not work
Interesting!
str8stryk3r said:
RaiderWill said:
No I unlocked the bootloader so I wouldn't have to in the future. Why, bootloader unlocking China cause me to not be able to do ota updates? I was under the impression that only rooting and installing twrp would cause issues with ota but I could've read wrong
Click to expand...
Click to collapse
Asder.mko said:
str8stryk3r said:
True, even I have unlocked my bootloader but I still received OTA.
Click to expand...
Click to collapse
Really ?
Please.. let me know once the update arrives.
I've NEVER seen a Signed O.T.A. software update package walk through the front door of a device with an Unsecured Bootloader.
Aren't you guys getting the "Exclamation Warning" screen when you first boot up letting you know your device is officially "Unsecure" ?
I'm not rooting Nougat.. just curious.. you normally get an "Update Failed!" message.. Thanks!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
RaiderWill said:
str8stryk3r said:
Asder.mko said:
Really ?
Please.. let me know once the update arrives.
I've NEVER seen a Signed O.T.A. software update package walk through the front door of a device with an Unsecured Bootloader.
Aren't you guys getting the "Exclamation Warning" screen when you first boot up letting you know your device is officially "Unsecure" ?
I'm not rooting Nougat.. just curious.. you normally get an "Update Failed!" message.. Thanks!
Click to expand...
Click to collapse
Well, I got the OTA in December itself but since I had rooted and installed twrp recovery, I wasn't able to install the update.
Yes, we get that " your device is not secure... Blah blah blah..."
Click to expand...
Click to collapse
Click to expand...
Click to collapse
RaiderWill said:
str8stryk3r said:
Asder.mko said:
Really ?
Please.. let me know once the update arrives.
I've NEVER seen a Signed O.T.A. software update package walk through the front door of a device with an Unsecured Bootloader.
Aren't you guys getting the "Exclamation Warning" screen when you first boot up letting you know your device is officially "Unsecure" ?
I'm not rooting Nougat.. just curious.. you normally get an "Update Failed!" message.. Thanks!
Click to expand...
Click to collapse
Before I went ahead an unlocked my bootloader I checked as many sources as I could about if whether or not I'd still be able ota update and the vast majority of the things I read states that what causes the update to fail is not having stock rom and not having stock recovery. The bootloader being unlocked doesn't modify those or any system files so everything should be fine. Unless Huawei changed things specifically for our Honor 7x then there shouldn't be any problems with ota updates. I guess I'll find out when the L24 people start saying they got updates and I don't receive it or can't install it
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Well, that's quite right. I don't know whether Huawei/Honor implemented THAT thing, but yeah reverting back to stock conditions wand applying OTA wouldn't be an issue!
( P.S - I'm stuck here too as I have OTA update since December but haven't reverted to stock to install it. I don't yet know properly about manual installation! )
(I haven't received my 7x yet and I haven't had any recent experience with Huawei OTA updates and I am not advocating that anyone should alter their phones in any way which would void their warranties... )
However, I was surprised to hear in this forum that Huawei has made things more restrictive since the Mate2. Given that you can still obtain bootloader unlock codes (and the only reason AFAIK is to allow you to flash a new recovery) and that Huawei has publicly committed to open-source and has given 7x's to developers, it seems contrary to a "lockdown" philosophy. Rather, it would appear as they are still encouraging 3rd party development to prolong product lifespan in order to attract cheapskates like me who still use a 4-year old phone.
Things may have changed but In order to get OTA updates, here were some of the issues on the Mate2 :
Some people had a difficult time obtaining the bootloader unlock codes. Either you can get a code or you couldn't. Without an unlocked bootloader, you can't flash a different recovery.
You "can't" flash TWRP. That's not entirely true. You needed to restore the appropriate version of Huawei recovery before each OTA, because update.zip can only be interpreted by the appropriate recovery. (Think format differences between CWM and TWRP.)
You were able to root and still obtain OTA. (Albeit, there was only one OTA. The rest had to be downloaded to SD and flashed. But that was okay back then 'cause no one outside of China really knew about Huawei.) The updates weren't checking whether you had modified the existing software or not. Once you've voided your warranty, Huawei didn't care if you then decide to then make your phone more vulnerable or accidentally brick it. The problem was that the update could fail if you remove a piece of bloatware that Huawei decided to update. (The folders would be missing for example. And the update would not recover gracefully.)
But a big THANKS to previous posters which reminded me to backup everything (basically as soon as I receive my 7x).
Oh....if you are flashing a custom recovery, you should also backup the "stock" recovery after each OTA update. Sometimes the recovery is also updated. (That's what I meant by "appropriate" version.)
iammudd said:
(I haven't received my 7x yet and I haven't had any recent experience with Huawei OTA updates and I am not advocating that anyone should alter their phones in any way which would void their warranties... )
However, I was surprised to hear in this forum that Huawei has made things more restrictive since the Mate2. Given that you can still obtain bootloader unlock codes (and the only reason AFAIK is to allow you to flash a new recovery) and that Huawei has publicly committed to open-source and has given 7x's to developers, it seems contrary to a "lockdown" philosophy. Rather, it would appear as they are still encouraging 3rd party development to prolong product lifespan in order to attract cheapskates like me who still use a 4-year old phone.
Things may have changed but In order to get OTA updates, here were some of the issues on the Mate2 :
Some people had a difficult time obtaining the bootloader unlock codes. Either you can get a code or you couldn't. Without an unlocked bootloader, you can't flash a different recovery.
You "can't" flash TWRP. That's not entirely true. You needed to restore the appropriate version of Huawei recovery before each OTA, because update.zip can only be interpreted by the appropriate recovery. (Think format differences between CWM and TWRP.)
You were able to root and still obtain OTA. (Albeit, there was only one OTA. The rest had to be downloaded to SD and flashed. But that was okay back then 'cause no one outside of China really knew about Huawei.) The updates weren't checking whether you had modified the existing software or not. Once you've voided your warranty, Huawei didn't care if you then decide to then make your phone more vulnerable or accidentally brick it. The problem was that the update could fail if you remove a piece of bloatware that Huawei decided to update. (The folders would be missing for example. And the update would not recover gracefully.)
But a big THANKS to previous posters which reminded me to backup everything (basically as soon as I receive my 7x).
Oh....if you are flashing a custom recovery, you should also backup the "stock" recovery after each OTA update. Sometimes the recovery is also updated. (That's what I meant by "appropriate" version.)
Click to expand...
Click to collapse
My thoughts exactly. Why would they provide they website to unlock the bootloader if that kept ota updates from going through. The only thing that's really holding back the development of this device is Huawei hasn't released the full stock firmware package yet. I have the L24 version so it's exciting seeing L21/A10 making some progress because it's only a matter of time until things start to kick off all around.
str8stryk3r said:
My thoughts exactly. Why would they provide they website to unlock the bootloader if that kept ota updates from going through. The only thing that's really holding back the development of this device is Huawei hasn't released the full stock firmware package yet. I have the L24 version so it's exciting seeing L21/A10 making some progress because it's only a matter of time until things start to kick off all around.
Click to expand...
Click to collapse
No need for full fw broh need vendor partitions, device tree, kernel sources
maximran said:
No need for full fw broh need vendor partitions, device tree, kernel sources
Click to expand...
Click to collapse
Lmao, and that's why I'm not a developer. I just know having the stock image files is important so that when something gets screwed up got have something to fall back on.
Bringing Up The Rear...
Asder.mko said:
Yes, we get that " your device is not secure... Blah blah blah..."
Click to expand...
Click to collapse
That Answers My Question As To Wether Or Not You Do See The Unsecure Msg..
Anyway.. Great Discussion.
Fact or Fiction... who will get the updates via O.T.A. ? The Non-Rooted, The Rooted.. or Both.
Even with Project Treble... will this device ever take off with Developer support ?
Will Huawei / Honor release a stock image of Nougat and Oreo ? ( Eh, Honor.. it's been 60 days since Kernel source was released.. and you know people are Rooting away.. why have you not released the stock Nougat image for the 7x?) and don't use working on EMUI & OREO as an excuse.. that's simply not good enough.. :angel:
I'm going to enjoy laying back... and watching how this unfolds.
Re-Reading my own words, as to what is the motivation for everyone Rooting Nougat now.. and what is anyone getting out of doing it.. because so much of what you would normally do with Admin Access is already incorperated into the 7x.. is there really a need to even Root whats coming without something like a Stable Linage / Franco Kernel combo ROM available vs a 100% stable Factory Fresh EMUI / Oreo 8.0 setup.
For me, it will be a fun to see what key Developers, ROM's and support in general.. the 7x actually gets.. and at what point they release firmware for restoration purposes.
You Just Never Know.
RaiderWill said:
That Answers My Question As To Wether Or Not You Do See The Unsecure Msg..
Anyway.. Great Discussion.
Fact or Fiction... who will get the updates via O.T.A. ? The Non-Rooted, The Rooted.. or Both.
Even with Project Treble... will this device ever take off with Developer support ?
Will Huawei / Honor release a stock image of Nougat and Oreo ? ( Eh, Honor.. it's been 60 days since Kernel source was released.. and you know people are Rooting away.. why have you not released the stock Nougat image for the 7x?) and don't use working on EMUI & OREO as an excuse.. that's simply not good enough.. :angel:
I'm going to enjoy laying back... and watching how this unfolds.
Re-Reading my own words, as to what is the motivation for everyone Rooting Nougat now.. and what is anyone getting out of doing it.. because so much of what you would normally do with Admin Access is already incorperated into the 7x.. is there really a need to even Root whats coming without something like a Stable Linage / Franco Kernel combo ROM available vs a 100% stable Factory Fresh EMUI / Oreo 8.0 setup.
For me, it will be a fun to see what key Developers, ROM's and support in general.. the 7x actually gets.. and at what point they release firmware for restoration purposes.
You Just Never Know.
Click to expand...
Click to collapse
People like to root and mod their own devices for their own reasons but you're right, a lot of the reasons I modded past devices was because the roms almost always ran better than stock but the 7x imho runs great. Used to be kernels for better battery life and such. I like custom roms because I like to be able to do certain things that stock roms limited as far as customizing goes. A lot of people hate bloat and end up deleting every file on the phone that isn't necessary or to their liking to make the rom as minimal as possible.
But as of now I'm happy with the phone and don't feel the urge to need to root and and a custom recovery. The roms that eventually come would have to offer something worthwhile to flash. But hell, that's subject to change given how I'm feeling that day lol. There's a new AOSP based rom in another thread that sounds promising
RaiderWill said:
Will Huawei / Honor release a stock image of Nougat and Oreo ? ...
Re-Reading my own words, as to what is the motivation for everyone Rooting Nougat now.. and what is anyone getting out of doing it.. because so much of what you would normally do with Admin Access is already incorperated into the 7x..
Click to expand...
Click to collapse
I assume that you already know this ... but I should mention it for others that you can run TWRP (if there is a version for one's phone) without flashing it. (I don't have my 7x yet, so I prob really shouldn't be trying to give detailed instructions anyways.) From there, you can make backups of the stock image, stock recovery, etc. (So thx again to this forum for reminding me that I should backup all stock images as soon as I receive my 7x so that MY fingerprints are not all over the backups.)
As to rooting, there ARE at least 2 things that Huawei hasn't provided without root:
Yes, I can make app backups (and/or use the Huawei "easy transfer"... not sure what app that is at the moment) but I'd assume that I won't be able to transfer it to a non-Huawei device. That's why I continue to use Titanium Backup.
USB Mass Storage Enabling (and by extension Selinux Passive mode). I want fast transfer to my desktop, etc.... and I want a drive-letter (yes, there are Win programs which only work with drive letters). Without UMS, I haven't found a way to do that.