Related
I own a registered (with Xperia Care [warranty]) Z5C E5823 phone. This phone was purchased from eBay US, but I believe the phone came from China as I had to manually switch from Chinese to English during the first initialization. Although at the time I got this phone (mid 2016), several build and android version updates existed, mine never updated. It is still stuck with Android 5.1.1, build 32.0.A.4.11, kernel 3.10.49-perf-g6b847e2. The phone, PC companion and everything else claims it's the latest update/version for the E5823.
I wanted to know what is happening and how to solve this. The phone is completely stock. Never rooted.
Thank you.
Thats why i payed extra 300$ to Sony
(my previous SONY was from alternative store, although the phone still was real and not fake replica it didnt get OTA updates so i had to used flashtool to update)
anyway you dont lose much.. wait for android 7 and update from flashtool
you can try use sony site to see if you supposed to get update
http://support.sonymobile.com/global-en/xperiaz5/software/
Superrman said:
wait for android 7 and update from flashtool
you can try use sony site to see if you supposed to get update
http://support.sonymobile.com/global-en/xperiaz5/software/
Click to expand...
Click to collapse
I've noticed something strange... I went to the link provided and inserted my IMEI number. The website claimed I have the latest version of everything, "as usual". But it showed the following message: "Your Xperia™ Z5 is up to date! 32.0.A.7.3.
That's not my build number and it also claims my phone as a Z5 and not Z5C. I don't know if this is relevant or not, but definitely strange.
Anyways, I believe that to use this flashtool I would have to root the phone. In this case I'm a bit concerned as the first android I ever tried to root was bricked instead. So I try to stand clear of doing that as I've been traumatized by my experience hahahahahaha. Well, unless there is a step-by-step-foolproof-recipe solution, I don't want to risk bricking my phone or voiding warranty (still in effect) if an update to marshmallow is not all that great.
l_abaurre said:
I've noticed something strange... I went to the link provided and inserted my IMEI number. The website claimed I have the latest version of everything, "as usual". But it showed the following message: "Your Xperia™ Z5 is up to date! 32.0.A.7.3.
That's not my build number and it also claims my phone as a Z5 and not Z5C. I don't know if this is relevant or not, but definitely strange.
Anyways, I believe that to use this flashtool I would have to root the phone. In this case I'm a bit concerned as the first android I ever tried to root was bricked instead. So I try to stand clear of doing that as I've been traumatized by my experience hahahahahaha. Well, unless there is a step-by-step-foolproof-recipe solution, I don't want to risk bricking my phone or voiding warranty (still in effect) if an update to marshmallow is not all that great.
Click to expand...
Click to collapse
As long as you are flashing an official ROM with flashtool, you don't need to root your phone.
I was sick of waiting for my Z5 compact to get the OTA for whatever firmware I initially had, so I just flashed unbranded Nordic with no problem without being rooted.
There are a few threads here on XDA that will explain what you need to do to use flashtool.
The wrong IMEI and Chinese first boot screen suggests your phone came from shady sources, otherwise there's no reason for the discrepancy. Did you check and see if the IMEI number matches the one on the box?
If I were you, I'd seek out the ebay seller and ask for an explanation and refund or replacement, fraudulent IMEI's are no joke, I mean what if the IMEI is reported stolen? You'd probably get tracked down and paid a visit by unpleasant people or something. Sure, you'd likely be able prove your innocence, but not worth the risk or hassle IMO. Then again, you have been using it for half a year already, chances are nobody's going to bother you, ever.
It's possible that the mismatch is the reason why you never got an OTA update notice. Like other members have suggested, you can use flashtool to flash the latest firmware, but it's certainly not as easy and painless as an OTA update. Going down the road, I don't think you'll ever get to update OTA with your device, so if you want to hang on to it and keep it up to date, learn how to download official firmware using xperifirm, convert to FTF and flash using Flashtool .
Next time, buy from credible and reputable vendors.
Thanks for the reply guys. Unfortunately, there was no suspicion at the time about the phone being "fake" or something like that. But after this IMEI situation and this problem as well (worth checking), I'm kinda suspicious. I don't have the box with me, I'll only be able to compare this in february, as I'm abroad. But I've registered my phone with Sony and I didn't have any problems. I even have the limited warranty available.
By the way, can this warranty be used to replace the phone in a case like this? Even considering the LED issue mentioned in the link above?
I guess I'll have to educate myself about flashing firmware with flashtool. I don't mind the extra hassle, as long as I don't brick the phone.
l_abaurre said:
Thanks for the reply guys. Unfortunately, there was no suspicion at the time about the phone being "fake" or something like that. But after this IMEI situation and this problem as well (worth checking), I'm kinda suspicious. I don't have the box with me, I'll only be able to compare this in february, as I'm abroad. But I've registered my phone with Sony and I didn't have any problems. I even have the limited warranty available.
By the way, can this warranty be used to replace the phone in a case like this? Even considering the LED issue mentioned in the link above?
I guess I'll have to educate myself about flashing firmware with flashtool. I don't mind the extra hassle, as long as I don't brick the phone.
Click to expand...
Click to collapse
You can't go to Sony and ask them to replace it. Ok, you can always try, but based on normal warranty, they won't replace it.
In your case, it's up to the dealer/store to fix your problem with IMEI, maybe a faulty ROM and so on. Or you can flash the update yourself
--jenana-- said:
You can't go to Sony and ask them to replace it. Ok, you can always try, but based on normal warranty, they won't replace it.
In your case, it's up to the dealer/store to fix your problem with IMEI, maybe a faulty ROM and so on. Or you can flash the update yourself
Click to expand...
Click to collapse
It's been a while since I've bought the phone, so I don't believe the vendor will do much.
I've read about the process of flashing the firmware. The only thing I did not understand is about the selection of the firmware itself. I'm presented with a list of firmwares of various countries (market) and carriers (operator) in XperiFirm. How do I know which one to select? A natural choice would be to select one from my region/carrier, but I can't find any or both for my phone. The guides I found doesn't elaborate on this.
Another thing. Will a simple backup with Xperia Companion or Factory Reset (from the phone itself) revert to the original firmware? Do I need to create a backup firmware?
Ahh, so the weird LED color thingy was you too. Your phone is off the charts fishy.
Your vendor should definitely be held accountable, try negotiating first. If things go sour, threaten to sue and see if they change their tune.
You select the firmware from your region, and don't select the carrier branded firmware, they're for locked phones sold by carriers, one normally wouldn't want to use that.
If I'm not mistaken, what you're trying to ask is if you're currently on firmware version A and flash version B, could you revert back to version A using Xperia Companion or via the factory reset, correct? The answer is no. You can however use Flashtool to flash version A regardless of what version firmware is currently installed on your phone, but I'm not sure if it's advisable to retain user data when you downgrade firmware.
Usually there's no need to make a backup of the original firmware. The factory reset function is basically just a data wipe, firmware version doesn't change. You should always backup your personal files before attempting to flash a firmware just in case. Personally I use Sony's preinstalled Backup and Restore app, it works for me - don't backup apps though it's pointless, takes up too much time and free space and is basically redundant. If you want to make a backup of the entire phone including the firmware, you will need a custom recovery solution like TWRP, but in your case I don't think you'll need to go that far, it's more stuff to learn and potentially go wrong.
mhaha said:
You select the firmware from your region, and don't select the carrier branded firmware, they're for locked phones sold by carriers, one normally wouldn't want to use that.
Click to expand...
Click to collapse
By region you mean the region I live or the region of the original firmware? I matched the CDA of the one that shows on the cellphone with one on the list of available firmwares. Not surprisingly, it shows that it is from Hong Kong and "customized HK" as operator. Intuition says I should try and flash that one...
So, usually backing up your current firmware is not needed/common?
Depends on what you're doing, because you're just upgrading and not messing with custom ROMs or kernels or whatever, then yeah you don't need to backup the entire phone/firmware, just backup your data.
I suggest picking the region you're living in, although it doesn't really matter since you can always change your language and uninstall/disable any localized apps. For example if you're in Russia, then you'd probably prefer the default search engine set to Yandex and local Russian apps preinstalled; or if you're in China, then you'd want Baidu instead and Chinese specific apps... etc. Or another possibility, US-based firmware may have the DST setting enabled by default, but nothing you can't change afterwards.
mhaha said:
I suggest picking the region you're living in, although it doesn't really matter since you can always change your language and uninstall/disable any localized apps.
Click to expand...
Click to collapse
I live in Brazil but I travel to the US all the time. I didn't find any firmware from these locations for my phone. So judging from what have I read so far, I can pick whatever as long as it's not carrier locked or something like that.
So I guess I'll pick whichever firmware is the most recent from the list and cross my fingers...
Just to give an update to whomever it may concern. I've decided to flash an Australian firmware (I belive it was the most recent one) after some more reading.
Although flashtool failed to flash the first time, I just repeated the process step by step and it worked like a charm the second time.
Although my backup didn't do much (I've deleted EVERYTHING from my phone, as recommended) everything worked and the phone is up to date.
Now I'm waiting for the Nougat!
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,
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
Hey everyone,
So! I bought a Sony Xperia 1 (J8110-2019) phone from someone on Facebook Marketplace at a very solid price of £250 (RRP is still £850 in the UK) due to the seller describing it as 'in retail demo mode' so they lowered the price. I jumped the gun thinking I was getting a solid deal and just stupidly assumed it to be a feature I could just disable with *#*#73556673*#*#- me believing I was some insane developer with mad coding skills where in realityI had once flashed and rooted my Xperia XZ back in 2016. [Insert 'Hackerman' meme]
Yes... I am fully aware I'm a complete idiot for not doing a full assessment on the phone and am now having to learn a very important lesson from this situation!!
It seems to have a Store Front firmware installed and unsure what firmware to download and flash? I've tried some of the official stock ROMs from XperiFirm and it just continues to boot into constant 10-second cycles of demo videos making general functionality like phone calls pretty much impossible. without interruption. I've tried Customized and UK Service Provider Firmware such as EE and O2 but it always goes back into Store mode.
I was hoping if anyone would have or could elaborate on how to make an executable system flash zip for a 2019 Xperia 1? When I extract files from XperiaFirm ROMS (FTF,ZIP,SIN etc), I don't seem to get any META-INF files and thus cant make the proper .zip that TWRP needs to successfully flash a new repacked stock ROM? It always ends in a boot loop."
Here are some key points to hopefully give you some background:
I've installed TWRP successfully and have attempted to use 3 official firmware to flash whilst in recovery but have been unsuccessful each time with 'Invalid .ZIP format'. I've only a few times got booted whilst bundling together FTF files via Flashtool and doing it that way round but only ever seems to solve half the problem
I can't use the SinExtract feature in Flashtools as the SIN file errors as not being supported yet to use different file versions.
I can't use PRFCreator as it errors as the FTF file being unsupported (Due to it being new I assume)
I attempted to create my own META-INF>Updater-script but am unable to identify what partition my phone would use for mounting on "/dev/block". I only ever seem to get MANIFEST.MF from the files and nothing else. On my XZ I think I used something like:
(package_extract_file("boot.img", "/dev/block/mmcblk0");
package_extract_file("system.sin","/dev/block/platform/msm_sdcc.1/by-name/system");
Click to expand...
Click to collapse
I have been able to install Magisk for rooting and verified.
I have used Minimal ADB and Fastboot to install programs like TWRP, SuperSu, Magisk but have never attempted, nor would I even know how to wipe my phone completely and install a clean stock ROM - is this possible?
All drivers, software, and systems are correct and up to date (as far as I am aware)
Would installing the' Service Exchange Firmware' be recommended (if I ever make it that far!) due to it being StoreFront?
I checked the IMEI number to see if it was blacklisted/blocked and it's all good. Not lost or stolen.
Thank you for your time to read and wallow in my woes with me my lovelies! Any help would be GREATLY appreciated you magnificent beasts! x
Bump x
...
the last chance... :good:
New here. Didn't see a forum for the Moto G Pure XT2163. Mods - I am sorry. Please move wherever's best.
Discovered that the version Verizon is selling (notably the slickdeals thread on the one from Visible) is different. It's -2 vs. -4.
Looks like VZW disabled most of the bands that T-Mobile/Sprint use - 25, 41, 71, for example.
Looking to see if it's possible to enable those bands. One report on SD thread says they bricked their device trying RETUS version but IDK if the bootloader needs to be unlocked first, or if it would even help. Probably more work to unlock these bands if it's even possible.
Downloads look available here https://mirrors.lolinet.com/firmware/moto/ellis/official/
Haven't messed with flashing a phone in years. May be able to try later but hoping anyone else here can look into this.
I'm going to guess as is the case with most other Android devices branded by Verizon that the bootloader will be restricted from being unlocked. There is really no way around this as it's an OEM based policy. If you want to play with custom ROMs or root based modding, I would highly recommend ditching the Verizon or any other carrier branded variant with the exception of T-Mobile/Metro and Google Fi (there are others) that actually allow OEM unlock. Not only that, but if you're looking for certain connectivity bands, you don't want to settle for a carrier device variant designed to use a particular set of bands which don't include the ones you need. No sense getting a Verizon variant to run on T-Mobile/Sprint bands when you can, you know, get the T-Mobile variant in the first place. Get the global unlocked variant model if you can and start from there. Far easier than the headaches you'll get trying to transform VZW to TMUS.
Cross-flashing is not going to unlock bands, you need to change modem configuration. Throw your SoC(Mediatek) followed by "unlock bands" into Google and see if you have any luck.
I also didn't see a forum for the Moto G Pure and was wondering if anyone knows of a custom bootloader like TWRP or CWM for it? I think I have enough understanding of how to sideload the app, I just need something to send the phone. I tried using a random TWRP mod on it but it fails, invalid signature. I haven't tried doing the phone rooting thing in years now, but I have this Moto G Pure phone without any service on it that I'm willing to experiment on. It can be used as a test bed or data extraction device to put code from it on the internet if someone needs it to help custom rom makers for example by testing stuff on it. Perhaps that's why no one has a custom recovery for it yet.
I don't know exactly how to extract the phones current ROM data so all I've done so far is unlock the bootloader. The phone's carrier based on the unactivated sim card shows it's a T-Mobile branded device, but the T-Mobile and other carrier software is inactive other than the few Moto apps. An article on XDA say's the phone's suck, but that's just not true at least not to me. It's a fine phone like it is, but if I can format it's SSD and only install what I want it to have on it that would be great. It's just a spare sim locked phone that I can't use my active sim card in. So with that it's now a project phone. I would like to mainly just unbloat it and free up all that used space occupied by the recovery partition. I don't necessarily need a whole new ROM, just want to root it. That's the only way to erase those factory files that I know of.
For me unlocking the bootloader wasn't to hard to do. You have to make sure the drivers from Motorola are installed and have a current version of ADB available on a computer. I still had a version of ADB tools that was almost a decade old now so I had to update that for the fastboot oem_unlock_unlockcode (automated code from Motorola support) command to work. To find out if it can be unlocked or not go here:
https://motorola-global-portal.custhelp.com/app/standalone%2Fbootloader%2Funlock-your-device-b
At the Moto site they will guide you on how to generate the code they want you to send them. You have to sign in to their site to use that function though. After I finally figured out what to type in the CMD window it generated that code and I edited it down to one long line of numbers and give it to the page. In seconds I had an email with the unlock code inside.
Unlocking it seems to help with uninstalling some of the built in stuff, before I could only disable most of the apps that come with it. The apps are still probably on there I just have to factory reset it and they'll come back. Now however the removed apps don't show as using any internal storage, all the apps info numbers go to 0 bytes, but still even doing that it's still over 10GB of unmovable data. When it should really be more like 2-3 GB for the entire system. I hate how Google just inserts itself in your life even when you don't want it at all.
I anyone passing by reading this post needs more details please let me know and I'll try to get the information or even data files from the phone. Would a copy of it's stock firmware be of any help? If so let me know how I would go about saving a copy of it. I'll keep looking for answers but it seems this phone is not high on the priority list or is new or something. So there is only scam guides trying to tell you "How to unlock your phone" or "Install TWRP on Motorola devices" and other clearly click bait sites. I can't even find the stock rom for it on Motorola's site, just outdated versions from 2016, with different build numbers, that can't be right.
All I know is unlocking the bootloader was the first step on all the guides and I've done that. Got a warranty voided notice and everything. There currently isn't a custom recovery mod for this model as far I can tell. If I can ever find that then I can try Linage or just debloat Android 11 which is probably the safer and easier option provided I can find that Custom Covery'.
When it boots up now, it has to tell me it's unlocked and all the dangers it poses. Dangerous if you cared about what was on it I suppose. There is nothing on it I can't just copy back over to it, other than the stock operating system.
Oh yeah, it's model number and other side of the box information is:
Model Name: Moto G PURE
SKU: MO-XT21634-AJB (MOXT21634AJB)
Software Version RRH31.Q3-46-20
Production date was 12/15/2021
I'm not sure what other information to include.
BrittonCBurton said:
I also didn't see a forum for the Moto G Pure and was wondering if anyone knows of a custom bootloader like TWRP or CWM for it? I think I have enough understanding of how to sideload the app, I just need something to send the phone. I tried using a random TWRP mod on it but it fails, invalid signature. I haven't tried doing the phone rooting thing in years now, but I have this Moto G Pure phone without any service on it that I'm willing to experiment on. It can be used as a test bed or data extraction device to put code from it on the internet if someone needs it to help custom rom makers for example by testing stuff on it. Perhaps that's why no one has a custom recovery for it yet.
I don't know exactly how to extract the phones current ROM data so all I've done so far is unlock the bootloader. The phone's carrier based on the unactivated sim card shows it's a T-Mobile branded device, but the T-Mobile and other carrier software is inactive other than the few Moto apps. An article on XDA say's the phone's suck, but that's just not true at least not to me. It's a fine phone like it is, but if I can format it's SSD and only install what I want it to have on it that would be great. It's just a spare sim locked phone that I can't use my active sim card in. So with that it's now a project phone. I would like to mainly just unbloat it and free up all that used space occupied by the recovery partition. I don't necessarily need a whole new ROM, just want to root it. That's the only way to erase those factory files that I know of.
For me unlocking the bootloader wasn't to hard to do. You have to make sure the drivers from Motorola are installed and have a current version of ADB available on a computer. I still had a version of ADB tools that was almost a decade old now so I had to update that for the fastboot oem_unlock_unlockcode (automated code from Motorola support) command to work. To find out if it can be unlocked or not go here:
https://motorola-global-portal.custhelp.com/app/standalone%2Fbootloader%2Funlock-your-device-b
At the Moto site they will guide you on how to generate the code they want you to send them. You have to sign in to their site to use that function though. After I finally figured out what to type in the CMD window it generated that code and I edited it down to one long line of numbers and give it to the page. In seconds I had an email with the unlock code inside.
Unlocking it seems to help with uninstalling some of the built in stuff, before I could only disable most of the apps that come with it. The apps are still probably on there I just have to factory reset it and they'll come back. Now however the removed apps don't show as using any internal storage, all the apps info numbers go to 0 bytes, but still even doing that it's still over 10GB of unmovable data. When it should really be more like 2-3 GB for the entire system. I hate how Google just inserts itself in your life even when you don't want it at all.
I anyone passing by reading this post needs more details please let me know and I'll try to get the information or even data files from the phone. Would a copy of it's stock firmware be of any help? If so let me know how I would go about saving a copy of it. I'll keep looking for answers but it seems this phone is not high on the priority list or is new or something. So there is only scam guides trying to tell you "How to unlock your phone" or "Install TWRP on Motorola devices" and other clearly click bait sites. I can't even find the stock rom for it on Motorola's site, just outdated versions from 2016, with different build numbers, that can't be right.
All I know is unlocking the bootloader was the first step on all the guides and I've done that. Got a warranty voided notice and everything. There currently isn't a custom recovery mod for this model as far I can tell. If I can ever find that then I can try Linage or just debloat Android 11 which is probably the safer and easier option provided I can find that Custom Covery'.
When it boots up now, it has to tell me it's unlocked and all the dangers it poses. Dangerous if you cared about what was on it I suppose. There is nothing on it I can't just copy back over to it, other than the stock operating system.
Oh yeah, it's model number and other side of the box information is:
Model Name: Moto G PURE
SKU: MO-XT21634-AJB (MOXT21634AJB)
Software Version RRH31.Q3-46-20
Production date was 12/15/2021
I'm not sure what other information to include.
Click to expand...
Click to collapse
hey i just came up on one of these today, nice phone considering... Any luck with trying to find a custom recovery? I have been looking as well but development seems pretty sparse right now. I am in the same boat as you, unlocked bootloader, locked everything else lol. I cant even find a way to root it without TWRP! I am curious if one of the other moto G series phones would have the same TWRP? Also check this out. It sounds legit but IDK...https://www.getdroidtips.com/root-motorola-g-pure-xt2163/
Agent_Orange1488 said:
hey i just came up on one of these today, nice phone considering... Any luck with trying to find a custom recovery? I have been looking as well but development seems pretty sparse right now. I am in the same boat as you, unlocked bootloader, locked everything else lol. I cant even find a way to root it without TWRP! I am curious if one of the other moto G series phones would have the same TWRP? Also check this out. It sounds legit but IDK...https://www.getdroidtips.com/root-motorola-g-pure-xt2163/
Click to expand...
Click to collapse
Well I was able to use Magisk to "root" it with the patched boot file trick, but still that's not the same thing as I did before with a Samsung phone and the CWM recovery deal. That gave the user all the control they wanted. Even though the phone claims I have root access, I'm not sure what to do with Magisk's root trick. I still don't see a way to backup or install a different operating system or just a blank Android 11 OS. My knowledge there is limited and there isn't a custom recovery for this model as far as I can tell.
So I still can't wipe the drive or remove the OEM partition that contains the installers for the bundled stuff. I'd still need some form of interface that has more features than the stock Fastboot and Bootloader modes offer I guess, or I just don't know how to use the software tools correctly. It's still locked even with root as far as I can tell but if there is something more I'm missing or an additional app to install for example, like SU. Is that still a thing? If I'm on the right track let me know.
BrittonCBurton said:
Well I was able to use Magisk to "root" it with the patched boot file trick, but still that's not the same thing as I did before with a Samsung phone and the CWM recovery deal. That gave the user all the control they wanted. Even though the phone claims I have root access, I'm not sure what to do with Magisk's root trick. I still don't see a way to backup or install a different operating system or just a blank Android 11 OS. My knowledge there is limited and there isn't a custom recovery for this model as far as I can tell.
So I still can't wipe the drive or remove the OEM partition that contains the installers for the bundled stuff. I'd still need some form of interface that has more features than the stock Fastboot and Bootloader modes offer I guess, or I just don't know how to use the software tools correctly. It's still locked even with root as far as I can tell but if there is something more I'm missing or an additional app to install for example, like SU. Is that still a thing? If I'm on the right track let me know.
Click to expand...
Click to collapse
Thanks for the reply!!! I am speaking from a place of semi-ignorance here but I would thing that you could install SuperSU from inside the system, right? As long as the root binary is there...idk though and from what I hear, chainfire is not responsible for SuperSU anymore so it has become somewhat sketchy. I saw a post (about this phone, I think) that mentioned having to install terminal emulator and running root command from there to achieve legit root after flashing the patched boot.img. I will see if I can find the post again and update you. Is there anyway you could post the boot.img? Or give me a link for it?
Agent_Orange1488 said:
Thanks for the reply!!! I am speaking from a place of semi-ignorance here but I would thing that you could install SuperSU from inside the system, right? As long as the root binary is there...idk though and from what I hear, chainfire is not responsible for SuperSU anymore so it has become somewhat sketchy. I saw a post (about this phone, I think) that mentioned having to install terminal emulator and running root command from there to achieve legit root after flashing the patched boot.img. I will see if I can find the post again and update you. Is there anyway you could post the boot.img? Or give me a link for it?
Click to expand...
Click to collapse
Well I can try and learn how to extract the phones information to my computer. I don't know how to do that exactly. The way I was able to get a hold of the phones stock firmware data was by using Lenovo's Smart Rescue and Recovery software.
You have to enable usb debugging mode, attach the phone to the computer with the software running and make sure that you didn't disable/delete Device Help. That app is what makes the Lenovo software work, otherwise the Recovery software fails to see the phone. If it sees the phone correctly then you can see the preselected target firmware it wants you to download under the Rescue tab along the top.
So I did that and grabbed the files it created without actually applying them to the device. The whole thing is a little over 2GB and difficult to host but I put the stock boot.img file here for anyone who needs it. If anyone wants all the files I can try to upload the whole thing one file at at time. That's the way it was sent to me, an uncompressed folder. If I zip it all up and try to upload it most sites will say file size exceeded. Anyway here's the link...
boot
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Thanks I was able to patch it with Magisk and achieve root. It looks like Magisk is an SU manager anyway. I have never used it before so this is a first for me. The root and bootloader unlock seem a little pointless without any recovery or ROM though....I guess it's time to learn how to compile one lol
I just picked up the Moto G Pure (XT2163-4) Android 11 aka Red Velvet Cake *sounds yummy lol*....I've been searching around and not seen any info about any rooting method for this device....besides the "Root All Motorola Phones" crap...and I don't feel like risking making a paper weight with it. Even on here it doesn't show up in the...add device list....was going to add to my profile...but can't.
Agent_Orange1488 said:
Thanks I was able to patch it with Magisk and achieve root. It looks like Magisk is an SU manager anyway. I have never used it before so this is a first for me. The root and bootloader unlock seem a little pointless without any recovery or ROM though....I guess it's time to learn how to compile one lol
Click to expand...
Click to collapse
Yeah now we're on the same page then. I thought the same thing, not much use to have an unlocked boot loader and root access without software to make use of it. I gave the phone to my nieces to play with for now, but it's with in arms reach if I need it for instructions yet to be defined. I should receive updates to this post if anyone else responds.
Gamekeeper408 said:
I just picked up the Moto G Pure (XT2163-4) Android 11 aka Red Velvet Cake *sounds yummy lol*....I've been searching around and not seen any info about any rooting method for this device....besides the "Root All Motorola Phones" crap...and I don't feel like risking making a paper weight with it. Even on here it doesn't show up in the...add device list....was going to add to my profile...but can't.
Click to expand...
Click to collapse
Yeah appears it was produced in late 2021 or sold at that time so it's new and no one has made any custom firmware's or recoveries for it as far as I know. I don't know how to do that, requires computer programming skills. I don't have any of those.
Gamekeeper408 said:
I just picked up the Moto G Pure (XT2163-4) Android 11 aka Red Velvet Cake *sounds yummy lol*....I've been searching around and not seen any info about any rooting method for this device....besides the "Root All Motorola Phones" crap...and I don't feel like risking making a paper weight with it. Even on here it doesn't show up in the...add device list....was going to add to my profile...but can't.
Click to expand...
Click to collapse
I feel your pain! Had mine a few days and of course came to XDA immediately to find the DL on this joint but no luck... Ya I definitely don't recommend one click root method for this. If you want, I can post/link the patched boot.img i made with magisk. Mine boots with it and have confirmed root.
BrittonCBurton said:
Yeah now we're on the same page then. I thought the same thing, not much use to have an unlocked boot loader and root access without software to make use of it. I gave the phone to my nieces to play with for now, but it's with in arms reach if I need it for instructions yet to be defined. I should receive updates to this post if anyone else responds.
Click to expand...
Click to collapse
Excellent, it's nice to be caught up with everyone else haha!! I am going to do some digging and posting and whatnot to try to find some info on porting a recovery for this model. I feel like it can't be too different from at least one or two of the other G series phones. I will see updates as well so please post if you come up with anything!!
BTW does anyone know the process of creating a device page for this joint?! I think this phone is definitely worth some development...
Agent_Orange1488 said:
Excellent, it's nice to be caught up with everyone else haha!! I am going to do some digging and posting and whatnot to try to find some info on porting a recovery for this model. I feel like it can't be too different from at least one or two of the other G series phones. I will see updates as well so please post if you come up with anything!!
BTW does anyone know the process of creating a device page for this joint?! I think this phone is definitely worth some development...
Click to expand...
Click to collapse
Good luck finding anything that will load onto the phone. Seems like it would be possible to install LineageOS on it if nothing else. You'd think by now installing a phone's operating system would be similar to how operating systems are installed on other computers. All I get is invalid signature, way to much security (for them) on phone OS'es. With phones and PDA's apparently you can't just find the OS you want to use and install it. Where's the generic and bloat free Andriod 11 stock OS/firmware at? No such thing? It's either "Gaggles" way or nothing apparently. (It's ok if you don't know either, maybe someone else has more information about that.)
BrittonCBurton said:
Good luck finding anything that will load onto the phone. Seems like it would be possible to install LineageOS on it if nothing else. You'd think by now installing a phone's operating system would be similar to how operating systems are installed on other computers. All I get is invalid signature, way to much security (for them) on phone OS'es. With phones and PDA's apparently you can't just find the OS you want to use and install it. Where's the generic and bloat free Andriod 11 stock OS/firmware at? No such thing? It's either "Gaggles" way or nothing apparently. (It's ok if you don't know either, maybe someone else has more information about that.)
Click to expand...
Click to collapse
Ya I'm definitely not going to try anything on the actual device, (ESPECIALLY if I am trying to put it together myself) but I am pretty sure you can test that stuff on a virtual system. Some kind of android emulator or whatever. As for a stock/debloated/de-odexed ROM, I haven't seen one but that couldn't be all that difficult to put together, right? I mean as long as the patched boot.img is included anyway. I feel like a recovery would be a higher priority though...? BTW, I have never used Lineage before, how is it?
Agent_Orange1488 said:
I feel your pain! Had mine a few days and of course came to XDA immediately to find the DL on this joint but no luck... Ya I definitely don't recommend one click root method for this. If you want, I can post/link the patched boot.img i made with magisk. Mine boots with it and have confirmed root.
Click to expand...
Click to collapse
That would be great if you could share that patched boot.img......it is for the XT2163-4 MOTO G PURE correct?
Gamekeeper408 said:
That would be great if you could share that patched boot.img......it is for the XT2163-4 MOTO G PURE correct?
Click to expand...
Click to collapse
Agent_Orange1488 said:
I feel your pain! Had mine a few days and of course came to XDA immediately to find the DL on this joint but no luck... Ya I definitely don't recommend one click root method for this. If you want, I can post/link the patched boot.img i made with magisk. Mine boots with it and have confirmed root.
Click to expand...
Click to collapse
I would also like the patched boot.img if it is for the XT2163-4. Thanks
Hey boys I actually got rid of the moto g pure...for now at least lol! GREAT phone and I would be willing to get it back once there is some dev work done on it...will definitely be watching the threads on it. Good luck boys!!!
Hi
I read the above posts, and it seems like even if I am able to root it using Magisk, I won't be able to flash it with custom rom?
Thank you Agent_Orange1488 for the posts.