Related
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.
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
Hello
I am enjoying the life with Redmi note 9 pro, unlocked bootloader and custom rom.
However, I was thinking, if someone gets physical access to the phone he could boot in fastboot or recovery and get inside, right?
So if this is possible, what do we do to protect our information? Is it possible to password protect the booting?
Not if you use encryption. That's why it's there. If you have unlocked phone they can get to bootloader abd for example reinstall whole system a basically make their stolen/found phone working, but that is not possible without full wipe, which means also your data.
Gajdalf said:
Not if you use encryption. That's why it's there. If you have unlocked phone they can get to bootloader abd for example reinstall whole system a basically make their stolen/found phone working, but that is not possible without full wipe, which means also your data.
Click to expand...
Click to collapse
Hi,
Is there a guide for how to enable encryption after unlocking the bootloader on the Note 9 Pro?
Thanks!
Gajdalf said:
Not if you use encryption. That's why it's there. If you have unlocked phone they can get to bootloader abd for example reinstall whole system a basically make their stolen/found phone working, but that is not possible without full wipe, which means also your data.
Click to expand...
Click to collapse
If that's the case then I am ok. My primary objective is the data to be secured.
And do you know why there is no option to encrypt the SD card? I am at MIUI 11 V11.0.4.0.QJZMIXM
BuzzyMind said:
Hi,
Is there a guide for how to enable encryption after unlocking the bootloader on the Note 9 Pro?
Thanks!
Click to expand...
Click to collapse
Hi. The easiest way to accomplish this is to go to settings and search for "encrypt". Activate the "Encrypt device using lock screen password".
Just remember that if you forget this password there is no way to get your data back, and also the microSD card is not encrypted.
BuzzyMind said:
Hi,
Is there a guide for how to enable encryption after unlocking the bootloader on the Note 9 Pro?
Thanks!
Click to expand...
Click to collapse
Unlocking has nothing to do with encryption. These 2 things are not connected in any way. So if you have encrypted system (which is usually by default) unlocking bootloader will not change that.
I don't know where exactly it is on MIUI system, but if you search for encryption in setting you should be able to find it (exactly like Smartie083 said).
If I remember correctly some systems were able to encrypt also sd-card (not sure tho). If your system allows it (you will need to have such option somewhere in security), keep in mind that this will render such sd-card usable only in that device, not anywhere else. So taking it out and connecting to PC will not work etc.
Also if you are interested in security of your system, you might be interested in ditching MIUI, installing clean rom without gapps and if you need G-services then using it through microG (although interesting, I consider this as valid option just for total paranoia people, or people which are running away from law).
Also avoiding root and ensuring that selinux is enabled is helpfull.
Hey guys, I just bought my RN10 and am waiting for it to arrive. My plan is to turn it into a DeGoogled phone (Custom ROM + MicroG) to use as a daily driver.
As someone who has no experience doing such a thing, but who has been familiarizing oneself with the topic and keeping up with this thread for a bit; I have a few questions that I was hoping I could get some help with:
1.
Is the 168 Hour waiting time a guarantee, or are there some of you who didn't have to wait that long?
-----
I plan to root the device, to pass SafetyNet, get Aurora Services, get Bromite Webview, maybe install oandbackupx, etc...
2.
What is your experience with Aurora services and Bromite Webview?
Do these (+ magisk and microG) need reinstalling after updates?
What is your preferred backup solution? I plan to back up to an SD card.
-----
I will try out some ROMs at first to see what works best for me, before I settle on one. But I am not sure if I can just use my backups from say CrDroid in DotOS for example.
These are the ROMs I am leaning towards (in order of preference): DotOS, CrDroid, and LOS:
3.
What should I be aware regarding backups when trying these ROMs? Can I use backups in different ROMs? Does it apply to oandbackupx or just TWRP ones of data partition?
Would you say they are stable enough for daily driving? (I am aware there are some minor bugs like video recording - not a problem for me)
-----
I am aware that TWRP is in alpha for the RN10 bc of the A/B partitioning system, and that it will be a long time for a stable version to come out.
Once I set on a ROM, I will wait until a stable version is released before I do updates.
4.
What should I be aware of when using TWRP? (specially this alpha version)
-----
I use Ubuntu in my system, and I wonder what is the best approach to Unlock the Bootloader and install custom ROMs there.
5.
Is anyone in this thread also using Linux? What is your experience?
What do you guys think of XiaomiTool V2? Is it reliable?
Or would you guys recommend doing these procedures via fastboot and adb? (android-tools-fastboot & android-tools-adb)
1.
there is no way around 1 week waiting. if you are unlucky you might have to wait another week. this might happen when you didn't use the phone enough in this week period, or if you reset the mi account.
also, from this unlock faq: https://c.mi.com/thread-2262302-1-0.html
If you're facing "User Portrait Scores Too Low Or Black", please create or use a new Mi Account to unlock.
Click to expand...
Click to collapse
what that means can only be speculated. in worst case this means, if you cover your camera so it is black, or if you have low light conditions in your drawer where to phone lies, or at the moment you press the unlock button, you can't unlock your phone.
or if the front camera can't recognize a face with its AI, so the portrait score is too low, it also might not unlock your phone. or if internet is blocked so it can't send the data home.
imho, this is a privacy nightmare, but there are no details anyware and everybody just seems to accept this insanity.
2.
I don't use aurora services, but webview browser work very well and magisk+microG does work if you get it installed once (this can be tricky because you have to find the right versions and variations that work together). if you choose a ROM that allows signature spoofing it isn't so much trouble, otherwise it gets more tricky. The rest works pretty easy with latest Magisk and MinMicroG (other microG variants I had trouble with).
You always have to reflash: 1) custom 3rd party recovery (like twrp), 2) Kernel, 3) magisk if you flash another ROM. this is always the same on every custom ROM.
3.
nandroid backup and restore is messy with TWRP currently. best way is to do backup with oandbackupX as root and/or a nandroid /data backup without encryption pin. backing up system is useless. in case of restoration install fresh ROM, start it up once for setting up encryption of /data, then restore /data partition.
you can't move /data partition between ROMs, you have to backup your apps with oandbackupX or the like.
nandroid backups on ext. SDCard currently don't work. better make space on your internal memory.
4.
TWRP is currently buggy or features not working correctly. don't expect anything that worked before in non virtual A/B environments to work perfectly fine here. upgrading was always tricky due to A and B slot changes, but thats not all a problem of TWRP but of the ROMs too.
Just read the older posts in the threads of CrDroid and LineageOS and TWRP and you will learn a lot what works and what doesn't work.
5.
Just install a virtual PC with windows 10 and use everything related to Xiaomi software in there. (most things are windows only). you can bridge your usb connected phone to the virtual PC.
There is no need for XiaomiTool V2 if you are on custom ROMs. just use fastboot/adb commands as needed.
1.
I plan to cover the front camera and not register the fingerprint scanner until I get a custom ROM on it. So I will discover if that is the case or not and let you guys know here.
2.
What is the best way to install microg? magisk module or flashing it via TWRP? I am under the impression one can go both ways about it.
having to flash the kernel is news to me. is there any post in this sub that I can read more about it?
3.
Okay, I will stick with oanbackupX for the time being then, and read about nandroid.
And could you further clarify what you mean by SD cards not working? Is it only for backups or at all? Does that apply to oandbackupX?
4. thanks I will read those posts. hopefully a stable is out soon though.
5.
I have a notebook that I am not sure is capable enough of running a Win VM. So i would really prefer to do these things on my Ubuntu install if I can. Plus it would be a peace of mind knowing i have all it needs and I am not dependent on having Windows machines near me should I have an emergency with the phone.
Is there any issue with XiamiTool V2? Would it not work to do the things i am trying to do?
Thanks in advace for your reply, they are very clarifying in getting me started on this!
best of luck with unlocking. hope you won't need another week. remember both cameras are eligible for face recognition and brightness measurement.
the way of installing microG may be different for each variation, ROM and phone (remember virtual A/B devices, read-only system, etc.). best way is to read the official installation manual that the microG variant provides. on virtual A/B devices you flash almost everything in Magisk with magisk-modules so you get a systemless patched system. the only thing you flash in recovery, beside kernels and other recoveries maybe, is actually magisk.
about kernels, just read the threads about the two released kernels so far.
well, you might be lucky if you try running the xiaomi software using wine, but it might not work. blame Xiaomi for not releasing all the wanted tools for all OS's.
for unlocking keep in mind that you don't change your setup, keep the same virtual PC, tool, data, etc. in place and don't change anything, they collect also PC data (os, hardware, ip - keep IP the same on PC and phone while unlocking!) for the unlocking process (also a privacy nightmare).. if you want to mitigate that you have to build much more around it than just a virtual pc, though.
I didn't use Xiaomi Tool so I can't really answer that. I think the software is outdated and it's main purpose is to remove some but not all bloatware on non rooted stock rom devices. you can do everything without that tool.
keep in mind that these are unofficial tools and there are many of them, and there are many fake ones uploaded to sharehosters which might be infected with malware. it's hard to find the right sources (but check the official sticky posts in this forum for links) and if you get all these tools by googling around chances are high you get some modified versions with malware.
I'd recommend doing things manually and learning step-by-step how to do things.
Oh damn, I will definitely cover the back camera after I test it then. Thanks for the heads up.
regarding flashing the kernels, I understand it now. I thought I had to reflash the stock kernel every time. silly me
keep IP the same on PC and phone while unlocking!
Click to expand...
Click to collapse
Do you mean keep the phone connected to the same wifi as the PC during the waiting period? bc otherwise I don't think that is possible at all, given that one must turn off wifi and use carrier data to add the Mi account to device.
I am not sure I understand what you mean :\
And the main purpose of the tool is to unlock bootloaders, install custom ROMs, etc. But you are right, latest version is one year old and I would like to avoid it if I can. Also there are 'official' links to download it from the Github page or the tool website.
I'd recommend doing things manually and learning step-by-step how to do things.
Click to expand...
Click to collapse
I agree with you, I will likely do the bootloader unlock procedure on Windows and then install TWRP via fastboot/adb on my Ubuntu laptop, and move on from there. I believe it is possible to do that much on linux right?
regarding the IP, I have the suspicion that they (xiaomi) rate the IPs that you use and for some they might block the unlocking attempt. VPN, TOR and other proxies might be suspicious to them and they might block them (this is not necessarily true for all VPNs, TOR nodes, regions, etc., though). There should be no problem with your default ISPs IP address however, but you'll let your pants down using them.
First unlocking on your phone has to be with mobile data, but you could also use VPN,Tor,etc. there, thats why I'm saying it. Some people I've talked to went as far as buying burner sims just for the unlocking process because they are afraid of what china does with their data.
there should be no problem at all if you use normal mobile data for phone Mi account and your default ISP ip on the computer with the unlock tool. They just spy monitor your phone for that week (until you delete the crap) and if the score is good you are good to unlock the phone. nobody besides them knows exactly what they do but you get a clue when you read their Terms of Service. if your ip address varies geographically very much in this week it might also look suspicious, or if the ip-range is used for many different unlocks. all that obviously plays a role in the score at the end.
ok, I didn't use any other tool for unlocking the bootloader than the original and official xiaomi unlock tool. all the rest can be done without additional tools.
the only things you might need is actually MiFlash (to reset/reflash factory ROMs), MIFlash unlock for unlocking the bootloader, and the latest fastboot+adb versions for all the rest.
fastboot+adb requires the correct phone drivers to work on windows, it might be the same on linux. if they are also available for linux it should be ok. for fastboot try the official general android drivers provided by google, they might also be available for linux (or are already implemented)
I was planning on getting a burner for this. but given the covid restrictions in where I am at, it is gonna be a hassle.
I think Xiaomi does most of that because of the people who buy their phones from China, unlock them, put a custom rom and resell them. I think I should be in the clear though, I wanna get a custom rom working asap, so I wont try using tor and vpn and risk it.
I really don't plan on reflashing the stock rom ever again, unless I absolutely need to. I think i read that there are some cases where one must reflash the stock rom in between custom rom installs(?), but I hope that it is not the case for me. I only plan to try dotos and crdroid, maybe los.
and I would think there is a way to get the drivers for Linux, given that xiomitool v2 does get drivers from somewhere and its available on Linux. I gotta do some digging here though
Please be kind if this is a stupid question - I'm very new to this and learning fast.
Would it be possible to add a signature to aromafm or to a lock pattern removal script, using the leaked Samsung platform certificate (as recently reported), and if so would that allow it to be sideloaded to stock recovery in a Galaxy S9?
I recently had to add a pattern lock - which I somehow managed to immediately forget. Even though it was a simple pattern specifically chosen to fall naturally under the hand so that I wouldn't forget it... I've tried so many variations that it's now making me wait 24 hours between attempts. It also turns out that data that I thought was backing up externally was actually only going to internal storage, so I really don't want to do a factory reset without trying absolutely everything else first.
Galaxy S9
Not rooted
Bootloader is locked
USB debugging is enabled
ADB can see the phone but it's not authorised
ADB sideload does work - but of course any scripts need the Samsung signature.
The phone is not registered with Samsung, so I can't unlock it through my Samsung account.
I realise it's clutching at straws but would the leaked platform key be a way in?
missmilla said:
Please be kind if this is a stupid question - I'm very new to this and learning fast.
Would it be possible to add a signature to aromafm or to a lock pattern removal script, using the leaked Samsung platform certificate (as recently reported), and if so would that allow it to be sideloaded to stock recovery in a Galaxy S9?
I recently had to add a pattern lock - which I somehow managed to immediately forget. Even though it was a simple pattern specifically chosen to fall naturally under the hand so that I wouldn't forget it... I've tried so many variations that it's now making me wait 24 hours between attempts. It also turns out that data that I thought was backing up externally was actually only going to internal storage, so I really don't want to do a factory reset without trying absolutely everything else first.
Galaxy S9
Not rooted
Bootloader is locked
USB debugging is enabled
ADB can see the phone but it's not authorised
ADB sideload does work - but of course any scripts need the Samsung signature.
The phone is not registered with Samsung, so I can't unlock it through my Samsung account.
I realise it's clutching at straws but would the leaked platform key be a way in?
Click to expand...
Click to collapse
While XDA prides itself on being hacker friendly, we shy away from anything that could result in legal liability, which is why we do not permit the sharing of any proprietary material, even if it's already in the public domain.
So in a nutshell....I imagine that if one did have a valid key, and signed an update package using that key, they could potentially use it to exploit their device, such as changing the props to allow bootloader unlocking, thereby permitting custom recoveries. Samsung as far as I know does not protect the system image with Verified Boot, so it is possible to modify /system without incurring a boot failure.
All that being said, the point is pretty moot, because as I pointed out we do not allow sharing anything that is licensed intellectual property, so any discussions on the topic would have to be rather...vague.
V0latyle said:
While XDA prides itself on being hacker friendly, we shy away from anything that could result in legal liability, which is why we do not permit the sharing of any proprietary material, even if it's already in the public domain.
So in a nutshell....I imagine that if one did have a valid key, and signed an update package using that key, they could potentially use it to exploit their device, such as changing the props to allow bootloader unlocking, thereby permitting custom recoveries. Samsung as far as I know does not protect the system image with Verified Boot, so it is possible to modify /system without incurring a boot failure.
All that being said, the point is pretty moot, because as I pointed out we do not allow sharing anything that is licensed intellectual property, so any discussions on the topic would have to be rather...vague.
Click to expand...
Click to collapse
Thank you, that's really helpful. I was thinking more whether simply adding a signature to a script would let that script be used directly with stock recovery, rather than unlocking the bootloader to flash a custom recovery (which I suspect would be beyond me), but it sounds as though in theory it might be worth a try. At this stage I probably have nothing left to lose as I'll have to to a full reset anyway if I can't find anonther way in.
missmilla said:
Thank you, that's really helpful. I was thinking more whether simply adding a signature to a script would let that script be used directly with stock recovery, rather than unlocking the bootloader to flash a custom recovery (which I suspect would be beyond me), but it sounds as though in theory it might be worth a try. At this stage I probably have nothing left to lose as I'll have to to a full reset anyway if I can't find anonther way in.
Click to expand...
Click to collapse
I'm honestly no expert on this kind of thing, but if I'm correct in my assumption that Samsung does not protect the system image, then yes - you could, in theory, use the leaked key to sign an update package that could patch /system to gain root. This would require knowledge of exactly how Samsung signs their updates. However, if the system image is protected, this would cause a boot failure, as AVB would detect the modification.
But.
If the above were possible, then the best course of action would be to create a script that would set ro.oem_unlock_ability=1 and sys.get_unlock_ability=1, after which the user would immediately reboot to download mode and unlock the bootloader, because once you've unlocked the bootloader, you've removed a lot of restrictions - you can flash a custom recovery, flash a root patch, flash anything you damn well pleased.
I doubt it's that easy unless you have in depth detailed knowledge of the encryption system and precisely how it's implemented. It's designed to be hard to hack. As for the stolen Samsung data be careful what you download. You may end up with something extra like a partition worming rootkit(s). boom. That was too easy.
A data recovery specialist that works with Samsung's is your best shot if you really need the data. Around $800 seems to be a going rate, maybe less but expect to pay a couple hundred.
In the future redundantly backup critical data to at least 2 hdds that are physically and electronically isolated from each other and the PC. Copy/paste only then verify the copy file size and that the backups are readable. Otherwise sooner or later you will lose data, money or both.
V0latyle said:
I'm honestly no expert on this kind of thing, but if I'm correct in my assumption that Samsung does not protect the system image, then yes - you could, in theory, use the leaked key to sign an update package that could patch /system to gain root. This would require knowledge of exactly how Samsung signs their updates. However, if the system image is protected, this would cause a boot failure, as AVB would detect the modification.
But.
If the above were possible, then the best course of action would be to create a script that would set ro.oem_unlock_ability=1 and sys.get_unlock_ability=1, after which the user would immediately reboot to download mode and unlock the bootloader, because once you've unlocked the bootloader, you've removed a lot of restrictions - you can flash a custom recovery, flash a root patch, flash anything you damn well pleased.
Click to expand...
Click to collapse
Thank you, I will do some more digging around. Would unlocking the bootloader that way not wipe the data?
blackhawk said:
I doubt it's that easy unless you have in depth detailed knowledge of the encryption system and precisely how it's implemented. It's designed to be hard to hack. As for the stolen Samsung data be careful what you download. You may end up with something extra like a partition worming rootkit(s). boom. That was too easy.
A data recovery specialist that works with Samsung's is your best shot if you really need the data. Around $800 seems to be a going rate, maybe less but expect to pay a couple hundred.
In the future redundantly backup critical data to at least 2 hdds that are physically and electronically isolated from each other and the PC. Copy/paste only then verify the copy file size and that the backups are readable. Otherwise sooner or later you will lose data, money or both.
Click to expand...
Click to collapse
Do you think it would brick the phone if I tried and it didn't like it, or would it just give the signature verification error like it does now?
Actually, looking again, I think I might have misunderstood. I thought the certificates themselves had been published (so wouldn't have to download anything), but what's shown may just be a hash of the certificate and so wouldn't give me the actual key anyway... I'm finding it all rather confusing.
It's ludicrous that Samsung won't let you unlock a phone if you can prove it's your own.
missmilla said:
Do you think it would brick the phone if I tried and it didn't like it, or would it just give the signature verification error like it does now?
Actually, looking again, I think I might have misunderstood. I thought the certificates themselves had been published (so wouldn't have to download anything), but what's shown may just be a hash of the certificate and so wouldn't give me the actual key anyway... I'm finding it all rather confusing.
It's ludicrous that Samsung won't let you unlock a phone if you can prove it's your own.
Click to expand...
Click to collapse
If in the US try a Samsung Experience center at a Best buy.
I never set locks on my phones, bios's or use encryption on data backup drives because you are always the one most likely to be locked out, sometimes through no fault of your own
Digital data is fragile unless it's redundantly backed up.
blackhawk said:
I doubt it's that easy unless you have in depth detailed knowledge of the encryption system and precisely how it's implemented. It's designed to be hard to hack. As for the stolen Samsung data be careful what you download. You may end up with something extra like a partition worming rootkit(s). boom. That was too easy.
A data recovery specialist that works with Samsung's is your best shot if you really need the data. Around $800 seems to be a going rate, maybe less but expect to pay a couple hundred.
In the future redundantly backup critical data to at least 2 hdds that are physically and electronically isolated from each other and the PC. Copy/paste only then verify the copy file size and that the backups are readable. Otherwise sooner or later you will lose data, money or both.
Click to expand...
Click to collapse
Do you think it would brick the phone if I tried and it didn't like it, or would it just give the signature verification error like it does now?
Actually, looking again, I think I might have misunderstood. I thought the certificates themselves had been published (so wouldn't have to download anything), but what's shown may just be a hash of the certificate and so wouldn't give me the actual key anyway... I'm finding it all rather confusing.
It's ludicrous that Samsung won't let you unlock a phone if you can prove it's your own.
blackhawk said:
If in the US try a Samsung Experience center at a Best buy.
I never set locks on my phones, bios's or use encryption on data backup drives because you are always the one most likely to be locked out, sometimes through no fault of your own
Digital data is fragile unless it's redundantly backed up.
Click to expand...
Click to collapse
Thank you. I'm in the UK but we do have a couple of Samsung Experience Centres here so I'll try asking. Oh I will definitely be making multiple, unencrypted backups from now on! I will also be rooting the phone and installing a custom recovery just in case.
If you start playing with the firmware bricking the device is always a real possibility especially if you don't follow the protocols correctly. I never had to flash any of my Samsung's in 12 years, all are still working today. I don't do OTA updates either, ever, the potential to brick them like that is higher with you having zero control.
Samsung would really love to sell you a new expensive phone...
Some lessons you end up learning the hard way. I lost a 30yo database that is irreplaceable
Learn from your mistakes and press on. It's a lot easier though to learn from other's mistakes.
missmilla said:
Thank you, I will do some more digging around. Would unlocking the bootloader that way not wipe the data?
Click to expand...
Click to collapse
Unlocking the bootloader will always require a data wipe.
missmilla said:
Do you think it would brick the phone if I tried and it didn't like it, or would it just give the signature verification error like it does now?
Actually, looking again, I think I might have misunderstood. I thought the certificates themselves had been published (so wouldn't have to download anything), but what's shown may just be a hash of the certificate and so wouldn't give me the actual key anyway... I'm finding it all rather confusing.
Click to expand...
Click to collapse
The stock recovery will refuse any packages that are not signed, or are signed with an unrecognized key. There's other measures in place as well.
blackhawk said:
If you start playing with the firmware bricking the device is always a real possibility especially if you don't follow the protocols correctly. I never had to flash any of my Samsung's in 12 years, all are still working today. I don't do OTA updates either, ever, the potential to brick them like that is higher with you having zero control.
Samsung would really love to sell you a new expensive phone...
Some lessons you end up learning the hard way. I lost a 30yo database that is irreplaceable
Learn from your mistakes and press on. It's a lot easier though to learn from other's mistakes.
Click to expand...
Click to collapse
Probably not something to be messing around with when I don't know what I'm doing then.
Ouch! No wonder you're so careful with backing up... as I will be too from now on. Lesson learned
V0latyle said:
Unlocking the bootloader will always require a data wipe.
The stock recovery will refuse any packages that are not signed, or are signed with an unrecognized key. There's other measures in place as well.
Click to expand...
Click to collapse
It's sounding like I'd probably better count my losses and leave it alone. And be more careful in future. All this has got me itching to try stuff out though. Possibly not on my one and only phone, but maybe if I can get a cheap second hand one to play with, or the S9 once I eventually upgrade - it sounds so much fun!
You can use the key to sideload an update, if I were you I'll try to flash a blank vbmeta and magisk boot so that you can bypass dm-verity and other measures, but the problem on this is where you can find the certificate? Nobody will tell you where you can find it because who has it remains silent and also communities do not allow this kind of sharing.
Skorpion96 said:
You can use the key to sideload an update, if I were you I'll try to flash a blank vbmeta and magisk boot so that you can bypass dm-verity and other measures, but the problem on this is where you can find the certificate? Nobody will tell you where you can find it because who has it remains silent and also communities do not allow this kind of sharing.
Click to expand...
Click to collapse
Thank you. Yeah, I thought I had seen someone publish the certificate, but I misunderstood. So wouldn't be able to get hold of it what with not being familiar with the dark web!
Skorpion96 said:
if I were you I'll try to flash a blank vbmeta and magisk boot so that you can bypass dm-verity and other measures
Click to expand...
Click to collapse
you can always flash blank vbmeta on low level (such as usbdl, edl or bootrom mode) but that's not how it works.
aIecxs said:
you can always flash blank vbmeta on low level (such as edl or bootrom mode) but that's not how it works.
Click to expand...
Click to collapse
Depends, if your device is made in USA you can't. I was only suggesting a way to bypass flashing restrictions hoping that bootloader lock don't block you. Normally bootloader lock blocks unsigned flashing but if you are able to bypass it during flash maybe you can boot unsigned firmware, I'm not sure though. To flash stuff you can use an exploit or escalate privileges with a signed app that updates a system one to become uid 1000 and after that you can do setenforce 0 or setenforce permissive to set kernel permissive
No no, locked bootloader prevents booting unsigned boot, vbmeta, etc (not flashing in first place)
@missmilla just realized you wanna break into your device? this was always possible for S9 (encrypted with default_password) but it's not easy
https://www.forensicfocus.com/news/samsung-exynos-support-in-oxygen-forensic-detective
aIecxs said:
@missmilla just realized you wanna break into your device? this was always possible for S9 (encrypted with default_password) but it's not easy
https://www.forensicfocus.com/news/samsung-exynos-support-in-oxygen-forensic-detective
Click to expand...
Click to collapse
Apparently the Qualcomm variants aren't suspectable to this hack. Only Exynos models are listed.