Related
My previous phone was a Xperia arc. I got this Xperia T over the weekend and are still getting the hang of it. I rooted the phone successfully using Bin4ry's tool. Unfortunately it is loaded with bloatware, O2 branding and other junk that I want to get rid of but this cannot be done.
I always used ES File Explorer and was able to remove unwanted apps but now the moment I select the option "Mount File System" as writeable, it reboots the phone. Same happens when I try to use SystemCleanup by Inteks; it just reboots.
Anyone have a workaround yet, or are all those clever devs here on these forums working round the clock to correct all the wrongs? :laugh:
Looks like those cunning devs at Sony added an extra layer of security to prevent people from making changes on the system partition....
Anyway, sofar I am very happy with my phone and reluctantly have to let go of my trusty old arc....
You should re-root with Bin4ry's new v12 script. Don't unroot, just run root script again. This will fix your reboot problem.
Tested and confirmed working
Andi have the t-mobile version of skyfall in the Netherlands
Sent from my LT30p using xda premium
Awesome! That did the trick! Previously I used v11 to root, but v13 fixed the problem. Thanks again.
...now to find the location of all the junk apps. System\App does not have all of it and there is no more a folder called System\Vendor\App
Is your boot loader unlockable?
JJD809 said:
Awesome! That did the trick! Previously I used v11 to root, but v13 fixed the problem. Thanks again.
...now to find the location of all the junk apps. System\App does not have all of it and there is no more a folder called System\Vendor\App
Click to expand...
Click to collapse
For bloatware, have you checked /system/etc/customization/applications/ ?
tilal6991 said:
Is your boot loader unlockable?
Click to expand...
Click to collapse
Yes. Follow instructions on Sony's website. Takes about 3 minutes. http://unlockbootloader.sonymobile.com/
Is that specifically the O2 version? I know in general they are.
I intend to unlock it. My previous phone - arc - I had it unlocked by another member on the XDA forums. His username is Jinx13 and he does an excellent job. He charges 15 GBP for his service.
Having said that, when entering *#*#7378423#*#* on my phone and going to Service info > Configuration > Rooting Status it states my phone as Bootloader unlock allowed: No
....so I cannot do so from the Sony Website but these guys can work their magic
However, I am waiting for email from O2 after me requesting sim unlock. https://www.o2.co.uk/apps/help/help?qid=1&q1=2&route=unlocking&case=Handset Unlocking Form
After this, I will unlock the bootloader if Jinx13 or other users that advertise this service on this forum, are able to do so with this phone model. The way these guys unlock it, it also removes any sim locks as well...
@skifyr123:
No, I did not even know of that location, so thanks for that!! I was looking at the locations as it was on my xperia arc which was System\App and System\Vendor\App
I use Titanium Backup to remove all the bloatware after rooting. I've got TB Pro so I'm not sure if the free version allows it.
With TB you don't have to worry about finding the app apks - just view the Apps list in TB and uninstall whatever you want!
I just flashed the Generic UK FW on my Skyfall edition Xperia T, it removed all o2 branding, like above, used Titanium Backup to remove all bloatware. I have the pro version.
I spoke to Jinx, does he have a solution? He said right now, there is no test point solution available...?
Not sure if wrong forum section but was wondering if there was a way to block all Verizon updates without root. I keep getting notifications to install the latest update (the one that gives Advanced Calling 1.0) but I don't want to install it in case it causes issues. Is there a way to remove/block this update feature without root?
You can disable all the Verizon's apps. In the app section in settings I don't get any notifications.
mdcowby said:
You can disable all the Verizon's apps. In the app section in settings I don't get any notifications.
Click to expand...
Click to collapse
Dont think you understood my question mdcow. I wasnt talking about stopping Verizon app updates like Navigator, Visual Voicemail, Text App, etc. I was talking about the system firmware updates
jgowell said:
Dont think you understood my question mdcow. I wasnt talking about stopping Verizon app updates like Navigator, Visual Voicemail, Text App, etc. I was talking about the system firmware updates
Click to expand...
Click to collapse
Not without root unfortunately. You can only keep declining the install and that's it but eventually your phone will bend to big red's will when you're not paying attention
jgowell said:
Dont think you understood my question mdcow. I wasnt talking about stopping Verizon app updates like Navigator, Visual Voicemail, Text App, etc. I was talking about the system firmware updates
Click to expand...
Click to collapse
I've never gotten those update notifications so my disabling a lot of stuff from Verizon and moto must of prevented something.
Just curious then what is your current firmware version? Want to see if you unknowingly updated already or if your update was actually blocked
mdcowby said:
I've never gotten those update notifications so my disabling a lot of stuff from Verizon and moto must of prevented something.
Click to expand...
Click to collapse
Is your system 21.44.8 or 21.21.15?
jgowell said:
Is your system 21.44.8 or 21.21.15?
Click to expand...
Click to collapse
221.44.8 if it updated it did it without me knowing. I'm getting rid of this phone anyway. Came from insurance cause they didn't have any razr maxx in Stock. I really don't like it.
Okay it sounds like it didn't update as your firmware version matches as one without the update Advanced Calling feature. Still curious to know what you disabled so I could get rid of my notification too
I think this newer ota app came from the Turbo, it stops it on the ultras. Check the md5 against yours. Pull it with Super Manager, apk manager, bAPK. Use Explorer free to read the md5.
I posted the md5 on my Op.
http://forum.xda-developers.com/showpost.php?p=56708101&postcount=1
---------- Post added at 01:13 PM ---------- Previous post was at 01:11 PM ----------
I wanted to check where it came from anyway. If not from Turbo then you may be able to benefit too.
aviwdoowks said:
I think this newer ota app came from the Turbo, it stops it on the ultras. Check the md5 against yours. Pull it with Super Manager, apk manager, bAPK. Use Explorer free to read the md5.
I posted the md5 on my Op.
http://forum.xda-developers.com/showpost.php?p=56708101&postcount=1
---------- Post added at 01:13 PM ---------- Previous post was at 01:11 PM ----------
I wanted to check where it came from anyway. If not from Turbo then you may be able to benefit too.
Click to expand...
Click to collapse
What? Not sure what you are trying to say. Can you reword?
lafont28 said:
Not without root unfortunately. You can only keep declining the install and that's it but eventually your phone will bend to big red's will when you're not paying attention
Click to expand...
Click to collapse
actually you can block OTA's without root.
go here and use this method. without root
http://forum.xda-developers.com/showpost.php?p=57436867&postcount=26
jgowell said:
What? Not sure what you are trying to say. Can you reword?
Click to expand...
Click to collapse
I still have the old Maxx. I found that installing a newer moto ota app (my link) I could stop the ota. I have yet to determine which new moto system dump I got it from. If not from the Turbo then it may stop it too.
Md5 is unique to any app. I posted it for the unknown app.
When you boot your phone, wait until the download notification comes up then go into settings and force stop MotorolaOTA. It'll cancel the download and it won't try again until you reboot.
Cobra04 said:
When you boot your phone, wait until the download notification comes up then go into settings and force stop MotorolaOTA. It'll cancel the download and it won't try again until you reboot.
Click to expand...
Click to collapse
Look two post above by me. you can block without root
the_rooter said:
Look two post above by me. you can block without root
Click to expand...
Click to collapse
A few questions about this. Let me know if it is easier to PM you or post here
the_rooter said:
Look two post above by me. you can block without root
Click to expand...
Click to collapse
jgowell said:
A few questions about this. Let me know if it is easier to PM you or post here
Click to expand...
Click to collapse
Try this blocking method out, I believe it will work for the Turbo. It's easier than using the script. http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294
Misterxtc said:
Try this blocking method out, I believe it will work for the Turbo. It's easier than using the script. http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294
Click to expand...
Click to collapse
thanks MisterXTC. The tool seems to work like a charm, esp with the search function.
One question: the OTA is already downloaded on my phone and i keep getting a notification to install it but I have been been 'delaying' the install. When I block the "MotoralOTA" but then reboot the phone the phone, the notification comes back. Is there a way to permanently block the OTA or will I have to block it each time the phone restarts?
jgowell said:
thanks MisterXTC. The tool seems to work like a charm, esp with the search function.
One question: the OTA is already downloaded on my phone and i keep getting a notification to install it but I have been been 'delaying' the install. When I block the "MotoralOTA" but then reboot the phone the phone, the notification comes back. Is there a way to permanently block the OTA or will I have to block it each time the phone restarts?
Click to expand...
Click to collapse
Try entering recovery mode and wipe the cache. That will delete the downloaded update file. As for permanently blocking the OTA it should stay blocked until you factory reset. It's probable nagging you because of the downloaded update file. You might have to re-block the OTA after clearing cache, I'm not positive. You might need to enter your app manager and manually stop the OTA, try that first.
Misterxtc said:
Try entering recovery mode and wipe the cache. That will delete the downloaded update file. As for permanently blocking the OTA it should stay blocked until you factory reset. It's probable nagging you because of the downloaded update file. You might have to re-block the OTA after clearing cache, I'm not positive. You might need to enter your app manager and manually stop the OTA, try that first.
Click to expand...
Click to collapse
I went ahead and cleared cache and it seems to have worked. No notifications to install so far despite reboot.
Thanks again for the link and help afterwards!
Quick backstory; I rooted my 5th Gen 7" Fire a loooong time ago, with I believe a version of Rootjunky's supertool. Removed auto OS updates, all that good stuff. Accordingly, I cannot access the OS info via System Updates (tapping it gives a blank screen for a moment, then goes back to the main settings screen). I have Google Play & services installed.
So, I tried today to use the Amazon Appstore, and I'm getting a "Network Unreachable" error right when the app launches. I can't use any functions of the store. I'm thinking it's maybe because the app is such a relatively old version, Amazon's network is giving it grief, but I don't know for certain.
Like I said, I can't see for sure what OS version I have, but it has to be one of the first iterations of 5.something.
If anyone has run into this, or has any suggestions to get the appstore working again, I'm all ears. I did a factory reset, both from in the OS and from the Amazon recovery (complete with wiping cache), with no luck. Thanks in advance for any help.
scooter1979 said:
Quick backstory; I rooted my 5th Gen 7" Fire a loooong time ago, with I believe a version of Rootjunky's supertool. Removed auto OS updates, all that good stuff. Accordingly, I cannot access the OS info via System Updates (tapping it gives a blank screen for a moment, then goes back to the main settings screen). I have Google Play & services installed.
So, I tried today to use the Amazon Appstore, and I'm getting a "Network Unreachable" error right when the app launches. I can't use any functions of the store. I'm thinking it's maybe because the app is such a relatively old version, Amazon's network is giving it grief, but I don't know for certain.
Like I said, I can't see for sure what OS version I have, but it has to be one of the first iterations of 5.something.
If anyone has run into this, or has any suggestions to get the appstore working again, I'm all ears. I did a factory reset, both from in the OS and from the Amazon recovery (complete with wiping cache), with no luck. Thanks in advance for any help.
Click to expand...
Click to collapse
Have you checked the clock? Sometimes, if the time is off, my store will break. Other than that, I'd recommend you download EZ File explorer, google form the most up to date amazon store apk, uninstall yours and give it a fresh install, especially if you feel out of date is the problem.
I'd also recommend you download a custom rom and flashfire and see if you can't fix that OS info problem, especially since you've already wiped all your data anyway.
elementalcobalt said:
Have you checked the clock? Sometimes, if the time is off, my store will break. Other than that, I'd recommend you download EZ File explorer, google form the most up to date amazon store apk, uninstall yours and give it a fresh install, especially if you feel out of date is the problem.
I'd also recommend you download a custom rom and flashfire and see if you can't fix that OS info problem, especially since you've already wiped all your data anyway.
Click to expand...
Click to collapse
This won't work:
- the version of Amazon's app store is different on FireOS; I don't believe it's available for download
- I did not see the OP had wiped his data; the OS info problem is related to blocking OTA updates
---------- Post added 02-12-2017 at 12:12 AM ---------- Previous post was 02-11-2017 at 11:56 PM ----------
scooter1979 said:
Quick backstory; I rooted my 5th Gen 7" Fire a loooong time ago, with I believe a version of Rootjunky's supertool. Removed auto OS updates, all that good stuff. Accordingly, I cannot access the OS info via System Updates (tapping it gives a blank screen for a moment, then goes back to the main settings screen). I have Google Play & services installed.
So, I tried today to use the Amazon Appstore, and I'm getting a "Network Unreachable" error right when the app launches. I can't use any functions of the store. I'm thinking it's maybe because the app is such a relatively old version, Amazon's network is giving it grief, but I don't know for certain.
Like I said, I can't see for sure what OS version I have, but it has to be one of the first iterations of 5.something.
If anyone has run into this, or has any suggestions to get the appstore working again, I'm all ears. I did a factory reset, both from in the OS and from the Amazon recovery (complete with wiping cache), with no luck. Thanks in advance for any help.
Click to expand...
Click to collapse
Best solution is to install a custom ROM; however you seem satisfied with FireOS.
Next best solution IMO is to reload FireOS (which includes Amazon's app store) but you will probably want to stick with version 5.0.1 if that's what is currently installed. Obvious problem is you can't determine that through normal means. Have to be careful here; if you attempt to reload 5.0.1 and your device is currently on 5.1.x or above it will brick. You would also need to reroot, reblock OTA updates, etc. In short, everything you did before. With no guarantee it will fix your original problem (although I think it will).
One way to test for 5.0.1 is to see if it will boot TWRP. However, that can be messy if you are unfamiliar with fastboot and/or have never established a connection with the device in question.
@steve8x8 - I seem to recall you wrote a tool that can query current component/system levels. Thoughts?
p.s. You could also go with FireOS 5.3.1 which is the last build that can be rooted at present. No brick risk as 5.3.1 is >= the current version of FireOS on the device.
elementalcobalt said:
Have you checked the clock? Sometimes, if the time is off, my store will break. Other than that, I'd recommend you download EZ File explorer, google form the most up to date amazon store apk, uninstall yours and give it a fresh install, especially if you feel out of date is the problem.
I'd also recommend you download a custom rom and flashfire and see if you can't fix that OS info problem, especially since you've already wiped all your data anyway.
Click to expand...
Click to collapse
It's not the clock, that's as it should be.
Davey126 said:
This won't work:
- the version of Amazon's app store is different on FireOS; I don't believe it's available for download
- I did not see the OP had wiped his data; the OS info problem is related to blocking OTA updates
---------- Post added 02-12-2017 at 12:12 AM ---------- Previous post was 02-11-2017 at 11:56 PM ----------
Best solution is to install a custom ROM; however you seem satisfied with FireOS.
Next best solution IMO is to reload FireOS (which includes Amazon's app store) but you will probably want to stick with version 5.0.1 if that's what is currently installed. Obvious problem is you can't determine that through normal means. Have to be careful here; if you attempt to reload 5.0.1 and your device is currently on 5.1.x or above it will brick. You would also need to reroot, reblock OTA updates, etc. In short, everything you did before. With no guarantee it will fix your original problem (although I think it will).
One way to test for 5.0.1 is to see if it will boot TWRP. However, that can be messy if you are unfamiliar with fastboot and/or have never established a connection with the device in question.
@steve8x8 - I seem to recall you wrote a tool that can query current component/system levels. Thoughts?
p.s. You could also go with FireOS 5.3.1 which is the last build that can be rooted at present. No brick risk as 5.3.1 is >= the current version of FireOS on the device.
Click to expand...
Click to collapse
You are correct, I am happy with the FireOS.
I've played in fastboot before, and given EXACT instructions, I can regurgitate results, but it's not my native tongue. I don't know if the appstore version is locked to the OS version, but according to Appstore Settings under the manage Amazon apps section, I'm rocking release-9.1011.5.1.39.0_2000145010, last updated 2/12/15. Any way to link that with OS version?
If no more info can be gleaned from my device, either from the appstore version or something steve8x8 may have, I may just load 5.3.1 on and run from there. Kinda rather not, but I'd kinda rather not not have appstore access.
scooter1979 said:
... I've played in fastboot before, and given EXACT instructions, I can regurgitate results, but it's not my native tongue. I don't know if the appstore version is locked to the OS version, but according to Appstore Settings under the manage Amazon apps section, I'm rocking release-9.1011.5.1.39.0_2000145010, last updated 2/12/15. Any way to link that with OS version?
If no more info can be gleaned from my device, either from the appstore version or something steve8x8 may have, I may just load 5.3.1 on and run from there. Kinda rather not, but I'd kinda rather not not have appstore access.
Click to expand...
Click to collapse
To my knowledge there is no direct correlation of appstore version to FireOS version. Obviously there's a range but we'd need a 1-1 match to draw a comfortable conclusion.
You can test TWRP bootability by following the guidance in this post. If TWRP boots you can safely sideload FireOS 5.0.1 from here using instructions in this thread (posts #1 and #2). That said, if you have no intention of every installing a custom ROM there really isn't any advantage to retaining an older bootloader. If that's the case might as well sideload FireOS 5.3.1. Be aware there is no going back if you take this step.
Davey126 said:
To my knowledge there is no direct correlation of appstore version to FireOS version. Obviously there's a range but we'd need a 1-1 match to draw a comfortable conclusion.
You can test TWRP bootability by following the guidance in this post. If TWRP boots you can safely sideload FireOS 5.0.1 from here using instructions in this thread (posts #1 and #2). That said, if you have no intention of every installing a custom ROM there really isn't any advantage to retaining an older bootloader. If that's the case might as well sideload FireOS 5.3.1. Be aware there is no going back if you take this step.
Click to expand...
Click to collapse
Ahhhh nuts. I'm getting "FAILED (remote: unknown command)" return on my Win7 machine trying to boot TWRP, and just simple USB transmission OK output on the device. Looks like I'm over 5.0.1.
Guess it's 5.3.1 for me. I'm assuming I can just follow the directions from sd_shadow's unbrick stock recovery ADB sideload thread, yes? Thanks for all of your help, I really appreciate it.
There's a guide to find bootloader version: https://forum.xda-developers.com/amazon-fire/development/identify-bootloader-version-t3424634
Sent from my Amazon Fire using XDA Labs
---------- Post added at 06:01 AM ---------- Previous post was at 05:59 AM ----------
scooter1979 said:
Ahhhh nuts. I'm getting "FAILED (remote: unknown command)" return on my Win7 machine trying to boot TWRP, and just simple USB transmission OK output on the device. Looks like I'm over 5.0.1.
Guess it's 5.3.1 for me. I'm assuming I can just follow the directions from sd_shadow's unbrick stock recovery ADB sideload thread, yes? Thanks for all of your help, I really appreciate it.
Click to expand...
Click to collapse
Just be sure that you don't accidentally update. Don't connect to WiFi until you have KingRoot, and be sure not to let the os update finish downloading. Once you connect, it will start. Some tips I found on how to avoid updates:
Davey126 said:
- use Kingroot 4.92 or lower; avoid v5.x (nearly impossible to remove)
- partial OTA update files are erased each time the device reboots
- KingRoot reboots frequently
- find a slow AP (library, coffee shop, etc) to thoddle the pace of downloads
- enable WiFi only after KingRoot starts and kill it when run completes
- force reboot device if KingRoot hangs for a prolonged period
- you may have to repeat the process multiple times
- there are trickier approaches (eg: IP/domain blocking) with variable results; the above playbook has worked well for most
- good luck
Click to expand...
Click to collapse
Sent from my Amazon Fire using XDA Labs
PorygonZRocks said:
Just be sure that you don't accidentally update. Don't connect to WiFi until you have KingRoot, and be sure not to let the os update finish downloading. Once you connect, it will start. Some tips I found on how to avoid updates:
s
Click to expand...
Click to collapse
Along with not hooking up wifi immediately, I was thinking of using rootjunky's supertool for root & update blocking, as the tool says it's now compatible with 5.3.1. Should be good enough, as long as I don't connect to a network until ALL of the supertool fun is done (I hope).
scooter1979 said:
Along with not hooking up wifi immediately, I was thinking of using rootjunky's supertool for root & update blocking, as the tool says it's now compatible with 5.3.1. Should be good enough, as long as I don't connect to a network until ALL of the supertool fun is done (I hope).
Click to expand...
Click to collapse
You need WiFi to root. That's why you need to be careful, since update starts quickly. Here's the thread the quote was from: https://forum.xda-developers.com/amazon-fire/help/dilemma-t3545062
If you can block the domains linked to in that thread, that'll help. It's not necessary, but it's a good idea.
EDIT: here's the post with them:
HughJeffner said:
Using stock 5.3.1 fresh install here are the domain names used in the update process:
softwareupdates.amazon.com
amzdigital-a.akamaihd.net
The first one is the actual update check, blocking DNS lookup of this domain effectively disabled auto-updates for me YMMV
The second domain name is where the firmware is actually downloaded from (not verified but seems probable). Note that this could change depending on how the update check is implemented.
I recommend blocking DNS resolution of softwareupdates.amazon.com if practical in your situation
Click to expand...
Click to collapse
Sent from my Amazon Fire using XDA Labs
PorygonZRocks said:
You need WiFi to root. That's why you need to be careful, since update starts quickly. Here's the thread the quote was from: https://forum.xda-developers.com/amazon-fire/help/dilemma-t3545062
If you can block the domains linked to in that thread, that'll help. It's not necessary, but it's a good idea.
Click to expand...
Click to collapse
Ohhhhh, I didn't realize Kingroot needs internet access... Besides that, I saw in the tool's changelogs that it even removes Kingroot & puts the normal supersu in the system, so I thought everything was more or less a "normal" rooting procedure. Whoops. Thank you, I'll be DNS blocking before anything.
scooter1979 said:
Ohhhhh, I didn't realize Kingroot needs internet access... Besides that, I saw in the tool's changelogs that it even removes Kingroot & puts the normal supersu in the system, so I thought everything was more or less a "normal" rooting procedure. Whoops. Thank you, I'll be DNS blocking before anything.
Click to expand...
Click to collapse
It removes KingRoot after using it to root. AFAIK, KingRoot is the only thing that can root these tablets. Personally, I'd recommend finding your bootloader version and flashing that, but it's just a personal preference, and has no practical difference unless you have 5.0.x, which you don't. I just like having oldest I can in case a downgrade method is ever found.
Also I may have an updated appstore apk from my brother's 5.3.2.1 tablet, let me check.
EDIT: Nope, I don't. I do, however, have an (old) apk from the Amazon website. See if installing this version helps. Just out of curiosity, could you attach the apk from your current appstore? I'm wondering if it will install on Fire Nexus. The UI looks much better than the version I have downloaded.
Sent from my Amazon Fire using XDA Labs
PorygonZRocks said:
Just out of curiosity, could you attach the apk from your current appstore? I'm wondering if it will install on Fire Nexus. The UI looks much better than the version I have downloaded.
Sent from my Amazon Fire using XDA Labs
Click to expand...
Click to collapse
I'll be happy to if you give me the path, or even the full name of the apk so I can search via root explorer.
scooter1979 said:
I'll be happy to if you give me the path.
Click to expand...
Click to collapse
If you have a file manager, search /system/app and /system/priv-app for com.amazon. venezia. Or, use an app like titanium backup to back it up.
It's taking forever to upload the apk I'm using, so here's the link if you want to test if it works: https://www.amazon.com/appstore_android_app
If not, I think you will need to reflash, unfortunately.
Sent from my Amazon Fire using XDA Labs
PorygonZRocks said:
There's a guide to find bootloader version: https://forum.xda-developers.com/amazon-fire/development/identify-bootloader-version-t3424634
Click to expand...
Click to collapse
Used this method, I'm on 5.1.1 (5.4.1_112720 5.1.1). Dagnabbit, missed it by that much.
scooter1979 said:
Used this method, I'm on 5.1.1 (5.4.1_112720 5.1.1). Dagnabbit, missed it by that much.
Click to expand...
Click to collapse
Then I'd recommend flashing 5.1.1. Like I said, if a downgrade method is found, it will probably be for older versions. Plus it's harder to brick, since only one or two versions are below it.
Sent from my Amazon Fire using XDA Labs
PorygonZRocks said:
It's taking forever to upload the apk I'm using, so here's the link if you want to test if it works: https://www.amazon.com/appstore_android_app
If not, I think you will need to reflash, unfortunately.
Sent from my Amazon Fire using XDA Labs
Click to expand...
Click to collapse
No go. Got a "Application Not Installed" error.
PorygonZRocks said:
Then I'd recommend flashing 5.1.1. Like I said, if a downgrade method is found, it will probably be for older versions. Plus it's harder to brick, since only one or two versions are below it.
Sent from my Amazon Fire using XDA Labs
Click to expand...
Click to collapse
The thing there is, if the issue is indeed related to the age of the appstore, which doesn't look like it has been updated since the OS was, sideloading the same version would put me in the same boat I'm in now. If I drop 5.3.1 on there, that should fix me, assuming the age of the store is the underlying issue. Unless there's something I'm missing.
Ok, my venezia is attached.
scooter1979 said:
No go. Got a "Application Not Installed" error.
The thing there is, if the issue is indeed related to the age of the appstore, which doesn't look like it has been updated since the OS was, sideloading the same version would put me in the same boat I'm in now. If I drop 5.3.1 on there, that should fix me, assuming the age of the store is the underlying issue. Unless there's something I'm missing.
Click to expand...
Click to collapse
A while back, I found a tutorial on how to upgrade system, but keep bootloader the same. Let me look...
Also, if it isn't the age of the app store, it has no effect. You could also try Amazon Underground app. It has a different package name, so it will install alongside the Appstore you have. This way, you can see if it has to do with the store or if it's just not working.
EDIT: Having trouble finding the link. I think what it was is you can download an update file, rename it from *.bin to *.zip, extract system.img, put it on the device, flash it, root, and disable ota immediately. I'll keep looking.
Sent from my Amazon Fire using XDA Labs
Umm, you guys?...
Ya wanna hear something wacky? Just for the fart of it, I ran the apk I just uploaded on my own device, and, um, the store works now. Zero problems. Connects just fine.
Now don't I feel like a horse's patoot?
Well, if nothing else, I learned what DNS to block if I upgrade to 5.3.1, how to check my bootloader via hex editor, and to rely on the kindness of strangers to fall bassackwards into an easy solution. Yeesh.
scooter1979 said:
Ya wanna hear something wacky? Just for the fart of it, I ran the apk I just uploaded on my own device, and, um, the store works now. Zero problems. Connects just fine.
Now don't I feel like a horse's patoot?
Well, if nothing else, I learned what DNS to block if I upgrade to 5.3.1, how to check my bootloader via hex editor, and to rely on the kindness of strangers to fall bassackwards into an easy solution. Yeesh.
Click to expand...
Click to collapse
Oh. Well, I found the thread, if you want. It gives instructions for FlashFire as well.
https://forum.xda-developers.com/amazon-fire/general/howto-install-fireos-5-1-1-root-gapps-t3265594
Sent from my Amazon Fire using XDA Labs
---------- Post added at 07:37 AM ---------- Previous post was at 07:32 AM ----------
scooter1979 said:
Ok, my venezia is attached.
Click to expand...
Click to collapse
Was there a .odex in the folder, and/or a lib folder? If so, could you also upload that? If not, then it appears it will not work. Shame. Thanks for the apk.
Sent from my Amazon Fire using XDA Labs
I ordered a Nexus 6 from Ebay, and shocker, it's Account locked. I've tried many different methods, most of which involve dirty cow, but I can never get Google Account Manager to delete, so I'm stuck... I'm running 7.0 if that helps
blaziemoop said:
I ordered a Nexus 6 from Ebay, and shocker, it's Account locked.....
Click to expand...
Click to collapse
http://pages.ebay.com/help/policies/money-back-guarantee.html
NLBeev said:
http://pages.ebay.com/help/policies/money-back-guarantee.html
Click to expand...
Click to collapse
Accidentally cancelled return request, eBay only allows for 1 chance. Now neither eBay, nor the seller will respond. It's been a month
What payment method did you use to purchase the phone? If it was a credit card, perhaps you can do a charge-back through them.
I imagine eBay and/or PayPal won't be too happy though if it goes through.
Alternatively, perhaps Google support could help?
Is the N6's bootloader locked? If I flash the factory image onto my N6, it reports it was wiped recently and I need the original account to sign-in, but I don't recall seeing this from PureNexus nor LineageOS. If the bootloader is unlocked, perhaps you can just flash a custom ROM?
Something else to try (in-case the bootloader is locked and you need to get to developer options); factory-reset the device from Recovery and set-up the phone without internet access (assuming that's possible). From there, you can enable OEM unlock, then proceed to do a custom ROM.
blaziemoop said:
I ordered a Nexus 6 from Ebay, and shocker, it's Account locked. I've tried many different methods, most of which involve dirty cow, but I can never get Google Account Manager to delete, so I'm stuck... I'm running 7.0 if that helps
Click to expand...
Click to collapse
You're screwed. The seller likely bought the device like that and passed his problem on to you. Google will not help you defeat protections they have implemented, so forget that route. Bypass hacks haven't worked for months, so they're out. Seek a chargeback if you paid by card.
I don't believe @espionage724's tip will help, as I believe FRP would still kick in, but it won't hurt to try it. Just be prepared for the real possibility of having to sell this thing for parts on ebay. Next time, use Swappa to buy your device.
blaziemoop said:
I ordered a Nexus 6 from Ebay, and shocker, it's Account locked. I've tried many different methods, most of which involve dirty cow, but I can never get Google Account Manager to delete, so I'm stuck... I'm running 7.0 if that helps
Click to expand...
Click to collapse
espionage724 said:
What payment method did you use to purchase the phone? If it was a credit card, perhaps you can do a charge-back through them.
I imagine eBay and/or PayPal won't be too happy though if it goes through.
Alternatively, perhaps Google support could help?
Is the N6's bootloader locked? If I flash the factory image onto my N6, it reports it was wiped recently and I need the original account to sign-in, but I don't recall seeing this from PureNexus nor LineageOS. If the bootloader is unlocked, perhaps you can just flash a custom ROM?
Something else to try (in-case the bootloader is locked and you need to get to developer options); factory-reset the device from Recovery and set-up the phone without internet access (assuming that's possible). From there, you can enable OEM unlock, then proceed to do a custom ROM.
Click to expand...
Click to collapse
1 - If bootloader is unlocked, but OEM unlock disabled, you'll still have to sign in with the previous account...
2 - Same as 1 I guess
3 - if the bootloader is unlocked and OEM unlock is enabled, then you can flash whatever you want and setup without sign in...
But since he was presented with the login screen, I highly doubt the OEM unlock is enabled...
Good luck...
i was to having this problem but eventually solved.
kaustick said:
i was to having this problem but eventually solved.
Click to expand...
Click to collapse
Hey,
Isn't it supposed to be for Android 6.x version? Does it work on 7.x ?
Thanks...
5.1 said:
Hey,
Isn't it supposed to be for Android 6.x version? Does it work on 7.x ?
Thanks...[/QUOT
first u need to unlock the bootloader using fastboot and downgrade to 6.0.1 . then see this video and description.
if uh cant downgrade then this
https://www.google.co.in/url?sa=t&s...-ov41LXJLWJ28o2qw&sig2=R8dSIItUB0Ltx-OFoHe4yw
Click to expand...
Click to collapse
kaustick said:
5.1 said:
Hey,
Isn't it supposed to be for Android 6.x version? Does it work on 7.x ?
Thanks...[/QUOT
first u need to unlock the bootloader using fastboot and downgrade to 6.0.1 . then see this video and description.
if uh cant downgrade then this
https://www.google.co.in/url?sa=t&s...-ov41LXJLWJ28o2qw&sig2=R8dSIItUB0Ltx-OFoHe4yw[/url]
Click to expand...
Click to collapse
I know about ghostlyhaks FRP bypass, but it seems like the OP Android version incompatible. Also, since he can't skip setup, I guess unlocking the bootloader is a no-go...
Cheers...
Click to expand...
Click to collapse
its working fine for me!!
Considering the OP is running Android 7.0, and considering he cannot get into Android because of FRP, he cannot downgrade to an earlier version nor can he unlock the bootloader. If you have a means of bypassing Android 7.0 with a locked bootloader, posting a step-by-step guide here would help out the OP. Otherwise your help is unhelpful.
Any bypass for the 7.1.1 October patch??
9jarom is that a real tool?
9jarom keeps posting links to dodgy sites and forums that house this tool, which is why they keep getting deleted. There has been no evidence presented by him to verify that the app actually works, meaning no reviews and no videos. The only thing he's provided is his assurance that it works, and that simply isn't enough to go on. I would stay away from this.
9jarom said:
hello, it works perfectly and tested by me....
Click to expand...
Click to collapse
And that's not good enough. Couple that with the site with the links to Octopus boxes (used as a general term, and not permitted here) and the links to other sites which require registration to even view the content (really trustworthy there) and it's no wonder people are resistant.
You want people to use this stuff? Provide documented proof from third parties (i.e. people other than yourself) that it works. Reviews and especially videos. Stop requiring people to sign up to a website just to view content. And for heaven's sake stop posting links to sites that encourage the reader to buy an Octopus box.
Strephon Alkhalikoi said:
And that's not good enough. Couple that with the site with the links to Octopus boxes (used as a general term, and not permitted here) and the links to other sites which require registration to even view the content (really trustworthy there) and it's no wonder people are resistant.
You want people to use this stuff? Provide documented proof from third parties (i.e. people other than yourself) that it works. Reviews and especially videos. Stop requiring people to sign up to a website just to view content. And for heaven's sake stop posting links to sites that encourage the reader to buy an Octopus box.
Click to expand...
Click to collapse
I downloaded his tool and it's working. But my adb seems to not be able to connect. I can do step one. But step 2 requires adb and it's not working for me.
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 01:25 AM ---------- Previous post was at 01:23 AM ----------
9jarom said:
hello, it works perfectly and tested by me.... however for this security patch you asked for, you have to use another Tool called MOTO FOS V6 / MOTO NEXUS 6 FRP TOOL it work for the latest security pacth
Click to expand...
Click to collapse
After I put my phone into fastboot and hit 1 it doesn't seem to be able to connect to add when it reboots to the setup wizard. I'm on the latest October 5, 2017 patch not the 2016
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 01:28 AM ---------- Previous post was at 01:25 AM ----------
Also I was not required anything to buy. Only the usual adfly stuff I could skip and then it downloaded from mega. Mega is really trustworthy. Yet google told me it's infected but that's usual for modified Android software or anything that helps gain root privileges.
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 01:41 AM ---------- Previous post was at 01:28 AM ----------
Stop requiring people to sign up to a website just to view content. And for heaven's sake stop posting links to sites that encourage the reader to buy an Octopus box.
Click to expand...
Click to collapse
]
So here's the link to those files 9jarom redirected us to. It worked for me without loading any bad software or scripts even though google told me it was infected. I believe google only told me fat be sure it is an exploit that achieves root or hacks google software. It didn't work for me because my phone has some issue where it boots to fastboot instead of turning on completely. Adb doesn't work for my phone either and I'm having trouble connecting after the phone reboots. I even hit 4 and it didn't do much other than reboot it. My phone has an adb permissions issue but I bet it's due to the fact I can't access developer options because it's frp locked.
Sent from my [device_name] using XDA-Developers Legacy app
Edit: link won't be allowed by google but I will post virus scan results later tonight.
So as it stands right now, it's not working. Otherwise you would have already had FRP bypassed. In the meantime, upload the application or applications to VirusTotal and post a link to the results page. Doing so can eliminate one of the major concerns here: hidden payloads in the app.
Strephon Alkhalikoi said:
So as it stands right now, it's not working. Otherwise you would have already had FRP bypassed. In the meantime, upload the application or applications to VirusTotal and post a link to the results page. Doing so can eliminate one of the major concerns here: hidden payloads in the app.
Click to expand...
Click to collapse
Ok so here. I extracted the files and scanned the exe file. I can scan the text file too but you can explain to us what this means I guess but it hasn't seemed to affect my computer at all yet.
https://www.virustotal.com/#/file/8...2512f8e1e4d121260b0fedc9cce52c9cf09/detection
Sent from my [device_name] using XDA-Developers Legacy app
While the possibility exists that the 19 antivirus engines that detected something are simply posting false positives, I find it extremely unlikely. This file is NOT SAFE in my opinion. So I would uninstall this thing without delay and run a full and complete virus scan on your PC. Both Cyren and F-Prot detected W32/Betload.A.gen!Eldorado, a.k.a. Dorkbot. Dorkbot steals usernames and passwords. Some variants can download other malware or even have your PC participate in a DDOS attack. The AegisLab detection uses a different name, but is essentially the same thing. On top of it all, TrendMicro appears to have detected MBR Ransomware.
Any solution for simple root for our phone?
belzedj said:
Any solution for simple root for our phone?
Click to expand...
Click to collapse
There is a way. sToRm//'s Sony Xperia XZ Premium TWRP + KERNEL + ROOT + DRM fix/restore is an app that works on our XZ1 compacts. But read the thread carefully before you decide if you want to continue. The app works, I have used it on my phone and everything works perfect, with root. But to get to the point where the app works perfectly is quite difficult. Reading the thread, lots of people have unlocked their phone, broken their camera and now can't get the fix to work.
Personally I wouldn't recomend it.
Edit: Take note that unlocking your phone (required to root) is one way and can NEVER BE UNDONE. You break your phone for forever, you then have to hope that the developer will support you through further firmware upgrades.
Kingroot or any apk?
belzedj said:
Kingroot or any apk?
Click to expand...
Click to collapse
Kingroot don't do the XZ series and if they did I still wouldn't recomend it. Some Kingroot users have reported that their IMEI number has been cloned.
No apks
No quick easy root
What about xperifix ? see also
Oups, next time I'll put my brain "on" before posting
Has anyone tried xperifix 2.2 / 2.3? Supposedly some XZ1 compact updates were made.
You mentioned "to the point where the app works perfectly is quite difficult", which issues did you have?
zisforzorro said:
Has anyone tried xperifix 2.2 / 2.3? Supposedly some XZ1 compact updates were made.
You mentioned "to the point where the app works perfectly is quite difficult", which issues did you have?
Click to expand...
Click to collapse
Xperiafix 2.2 works and I used it to root my phone. But I'm now on out of date firmware (.75) as OTA stops as soon as you are rooted.
Also, I am sticking with .75 for the moment as it's the last build that Xposed works with and I have some Xposed modules that I am fond of.
The issues I had with the software were to do with getting the right drivers installed, particularly the USB drivers needed when you plug the phone in with TWRP running. Windows chooses the wrong drivers by default and you have to manually assign them or it’ll never work.
The software itself works, but ignore the progress meter built in. There are lots of posts on the Xperiafix thread of how to, so I’d say just read up first and you should be fine.
Xperiafix 2.3 is now the only option if you want up to date firmware on your phone, but it’s €20 and several users have had problems getting it to work, I’m sure the Dev will fix it soon.
So just be aware that if you buy into Xperiafix, you are dependent on the Dev for the rest of the life of your phone and forced to pay whatever he charges for the Xperiafix program
zisforzorro said:
Has anyone tried xperifix 2.2 / 2.3? Supposedly some XZ1 compact updates were made.
You mentioned "to the point where the app works perfectly is quite difficult", which issues did you have?
Click to expand...
Click to collapse
I tried the 2.3 Update (https://forum.xda-developers.com/xp...xperifix-47-1-12-145-aka-april-patch-t3777185 last entry).
I had some trouble with it, because I needed several tries and everytime I had to force close XperiFix.exe, adb.exe and fastboot.exe.
The Problem for me was, the downloaded Temp TWRP for XZ1C doesn't worked with the XperiFIX process.
If I used the downloaded temp TWRP it didn't happened nothing inside twrp.
So I had the installer from XperiFix 2.2 and extracted the Temp TWRP which I knew it would work.
I tried different ways to download the extracted TWRP into the XperiFIX.exe 2.3.
At first I got the MiniWeb HTTP Server, copied my TWRP Files into it and started the miniweb Server.
Then I Created the correct URL for me and I could download my twrp into XperiFix after I edited the devsettings.xpf file.
With my modified TWRP the installation of XperiFIX inside TWRP worked, and now I have the new magisk and XperiFIX working.
I uploaded my Files for you to get XperiFix working on XZ1C (G8441) .145 firmware.
Download it:
https://www115.zippyshare.com/v/Guov8WiU/file.html
Extract it into C:\XperIFix, Overwrite DATA/devsettings.xpf.
Start "C:\XperiFIX\miniweb\miniweb.exe"
Accept the Firewall Rule.
Start XperiFix.exe
Shutdown your Phone.
Plug in your PC and hold Volume UP to get into bootloader.
Set the Hook in XperIFIX and click on "Fix my Device".
And after 2 Minutes you have XperiFIX and magisk 16.3 working on your XZ1C (G8441) .145 FW.
At last close XperiFIx and miniweb.exe
Best regards.
Raz0Rfail
I tried Xperifix 2.4 and still have .NET error. I contacted the developer but so far no solution.
To root or not
Didgesteve said:
Xperiafix 2.2 works and I used it to root my phone. But I'm now on out of date firmware (.75) as OTA stops as soon as you are rooted.
Also, I am sticking with .75 for the moment as it's the last build that Xposed works with and I have some Xposed modules that I am fond of.
The issues I had with the software were to do with getting the right drivers installed, particularly the USB drivers needed when you plug the phone in with TWRP running. Windows chooses the wrong drivers by default and you have to manually assign them or it’ll never work.
The software itself works, but ignore the progress meter built in. There are lots of posts on the Xperiafix thread of how to, so I’d say just read up first and you should be fine.
Xperiafix 2.3 is now the only option if you want up to date firmware on your phone, but it’s €20 and several users have had problems getting it to work, I’m sure the Dev will fix it soon.
So just be aware that if you buy into Xperiafix, you are dependent on the Dev for the rest of the life of your phone and forced to pay whatever he charges for the Xperiafix program
Click to expand...
Click to collapse
Hey man,
I lost my phone last week and finally bought XZ1c. XDA is not allowed at work and i am having trouble doing research and going through the threads to understand what all to do. Since I am not getting time to do research but i want to be able to start using the phone for now, do you think it is easy/worth it to root? from what you wrote it seems difficult and not a good idea for now but our goals are same because i want it solely to be able to run xposed. I had been using moto phones for the last 7 years now, so i know how bootloaders/rooting/flashing etc works. But i am completely new to the sony world so i was wondering on what is the downside (or what i lose) of me trying to go through a lot of trouble to get xposed working, and how much time will it take me overall to get there.
Any help is appreciated, I know it sounds like a lazy man asking for a hand holding, but apologize in advance!!
---------- Post added at 02:44 PM ---------- Previous post was at 02:41 PM ----------
TheDelta said:
Hey man,
I lost my phone last week and finally bought XZ1c. XDA is not allowed at work and i am having trouble doing research and going through the threads to understand what all to do. Since I am not getting time to do research but i want to be able to start using the phone for now, do you think it is easy/worth it to root? from what you wrote it seems difficult and not a good idea for now but our goals are same because i want it solely to be able to run xposed. I had been using moto phones for the last 7 years now, so i know how bootloaders/rooting/flashing etc works. But i am completely new to the sony world so i was wondering on what is the downside (or what i lose) of me trying to go through a lot of trouble to get xposed working, and how much time will it take me overall to get there.
Any help is appreciated, I know it sounds like a lazy man asking for a hand holding, but apologize in advance!!
Click to expand...
Click to collapse
I forgot to mention that I am already going to flash the .145 UK firmware today to get fingerprint on my US phone (to be used in India). I got a link from reddit where that guy has done a lot of times so i am going to trust him on it and follow his steps.
TheDelta said:
Any help is appreciated,
Click to expand...
Click to collapse
Not much has changed since I first wrote on this thread to be honest.
It depends on what you do with your phone to say if you need to root it or not. In the past you needed to root it to kill the battery hungry apps, but that's long gone these days. The other reason for rooting was customising your phone, but you can do that without root. So to be honest, if I were to come down on one side or the other I'd say don't bother. You also need to check that you can unlock your bootloader, as some phones bought from a provider are locked and this can't be circumnavigated. (type *#*#7378423#*#* in your phone to get the service menu and then service info/configuration)
Sony have given developers the finger with this bootloader, unlocking breaks the phone, you lose your TA keys, no way to back up and lots of functions stop working, like the, err, camera.
The good news is that there's a DRM fix out there, one that will work with the latest .145. There's no loss of quality on the camera, everything is as stock.
The bad news is that the developer sToRm// has put his DRM fix app to be paid for. This app works and as long as you have the right drivers is relatively easy.
There are a couple of people who have posted a free DRM fix for XZ Premium, but as yet, there's no one has posted a free fix that works with the .145 firmware for the XZ1 compact, although there might be some tips on the previous page, you'll still need a copy of Xperiafix
There are a couple of roms that have the DRM fix built in that are good daily drivers. Check out ResurrectionRemixOreo or LineageOS 15.1 UNOFFICIAL.
To root or not to root
Didgesteve said:
Not much has changed since I first wrote on this thread to be honest.
It depends on what you do with your phone to say if you need to root it or not. In the past you needed to root it to kill the battery hungry apps, but that's long gone these days. The other reason for rooting was customising your phone, but you can do that without root. So to be honest, if I were to come down on one side or the other I'd say don't bother. You also need to check that you can unlock your bootloader, as some phones bought from a provider are locked and this can't be circumnavigated. (type *#*#7378423#*#* in your phone to get the service menu and then service info/configuration)
Sony have given developers the finger with this bootloader, unlocking breaks the phone, you lose your TA keys, no way to back up and lots of functions stop working, like the, err, camera.
The good news is that there's a DRM fix out there, one that will work with the latest .145. There's no loss of quality on the camera, everything is as stock.
The bad news is that the developer sToRm// has put his DRM fix app to be paid for. This app works and as long as you have the right drivers is relatively easy.
There are a couple of people who have posted a free DRM fix for XZ Premium, but as yet, there's no one has posted a free fix that works with the .145 firmware for the XZ1 compact, although there might be some tips on the previous page, you'll still need a copy of Xperiafix
There are a couple of roms that have the DRM fix built in that are good daily drivers. Check out ResurrectionRemixOreo or LineageOS 15.1 UNOFFICIAL.
Click to expand...
Click to collapse
Yeah, for me rooting is so that i can use xposed, i have a couple of modules that i need almost daily. (used to :'( )
Thanks for the info, i think this is what i get -
1. I can just stay stock (and flash the UK .145 firmware and get fingerprint)
2. I can use xperifix, pay that guy and get root and xposed along with a good drm fix. Down side is that i will not have any OTA or anything like that and will have to stay on .145 itself as long as i want to keep this option.
3. I can go all the way custom with DRM fix and not use stock sony at all and directly start using custom roms where everything will work (i am assuming camera and fingerprint will work as well there).
Well, i've used RR before so i would very much like the option 3. I have always felt restricted in stock in any phone i've used, i have been so used to custom roms i like it. But since the phone is new, i do want to see what sony offers. So i think i am good with no ota .145 paid option as i will only have to pay it one time now. And then i am good for at least 3-4 months (post which i will mostly get bored and move to a custom rom). Thoughts?
---------- Post added at 04:52 AM ---------- Previous post was at 04:48 AM ----------
TheDelta said:
Yeah, for me rooting is so that i can use xposed, i have a couple of modules that i need almost daily. (used to :'( )
Thanks for the info, i think this is what i get -
1. I can just stay stock (and flash the UK .145 firmware and get fingerprint)
2. I can use xperifix, pay that guy and get root and xposed along with a good drm fix. Down side is that i will not have any OTA or anything like that and will have to stay on .145 itself as long as i want to keep this option.
3. I can go all the way custom with DRM fix and not use stock sony at all and directly start using custom roms where everything will work (i am assuming camera and fingerprint will work as well there).
Well, i've used RR before so i would very much like the option 3. I have always felt restricted in stock in any phone i've used, i have been so used to custom roms i like it. But since the phone is new, i do want to see what sony offers. So i think i am good with no ota .145 paid option as i will only have to pay it one time now. And then i am good for at least 3-4 months (post which i will mostly get bored and move to a custom rom). Thoughts?
Click to expand...
Click to collapse
I forgot to mention yesterday, I had checked on this phone. Boot loader unlock says allowed/yes. :highfive:
TheDelta said:
Yeah, for me rooting is so that i can use xposed, i have a couple of modules that i need almost daily. (used to :'( )
Thanks for the info, i think this is what i get -
1. I can just stay stock (and flash the UK .145 firmware and get fingerprint)
2. I can use xperifix, pay that guy and get root and xposed along with a good drm fix. Down side is that i will not have any OTA or anything like that and will have to stay on .145 itself as long as i want to keep this option.
3. I can go all the way custom with DRM fix and not use stock sony at all and directly start using custom roms where everything will work (i am assuming camera and fingerprint will work as well there).
Click to expand...
Click to collapse
Xposed won't work with .145, it's a know issue with no workaround as yet.
.75 is the last firmware that Xposed works with.
Edit: sToRm// says that paying for Xperiafix will mean that it will stay up to date with any future firmware releases, so you will be able to go beyond .145, but not until the problems with Xposed are fixed
Didgesteve said:
Xposed won't work with .145, it's a know issue with no workaround as yet.
.75 is the last firmware that Xposed works with.
Edit: sToRm// says that paying for Xperiafix will mean that it will stay up to date with any future firmware releases, so you will be able to go beyond .145, but not until the problems with Xposed are fixed
Click to expand...
Click to collapse
Bollocks!! I don't think i know how to go back to .75 then. Guess i just have to stay on stock till i get bored or xposed runs on .145 right? or whatever is newer out there. Apparently whenever i want to flash an OTA i still have to flash it in flashmode since i am on custom UK firmware so i think i will anyhow get bored and move onto custom pretty soon :fingers-crossed:
I haven't really been much of an OTA person. I usually keep formatting full phone to put new ROM or new release version every 3-4 months. I like a clean slate, keeps the phone in shape
Btw i did buy Storm's utility in morning so guess i am future proof :silly:
One question - I keep reading "you will lose DRM Keys" I thought it meant that Sony removes/disables/dissolves their own files which are required for apps/apks to run like camera. But is that something phone specific? like specific to me? The way everyone keeps saying you will lose that and you will never get it back - i want to know what it means. Like I cannot get it back for my specific phone? or Sony in General is not going to give it out but it is just a generic key/file. Sorry, just trying to understand what it exactly means. I earlier thought it is like that CID i had to backup for my motorola phone because it was my device ID number or a key file specific for my own personal device which once removed made it generic to flash.
---------- Post added at 01:02 PM ---------- Previous post was at 12:57 PM ----------
Didgesteve said:
Xposed won't work with .145, it's a know issue with no workaround as yet.
.75 is the last firmware that Xposed works with.
Edit: sToRm// says that paying for Xperiafix will mean that it will stay up to date with any future firmware releases, so you will be able to go beyond .145, but not until the problems with Xposed are fixed
Click to expand...
Click to collapse
Bollocks!! I don't think i know how to go back to .75 then. Guess i just have to stay on stock till i get bored or xposed runs on .145 right? or whatever is newer out there. Apparently whenever i want to flash an OTA i still have to flash it in flashmode since i am on custom UK firmware so i think i will anyhow get bored and move onto custom pretty soon :fingers-crossed:
I haven't really been much of an OTA person. I usually keep formatting full phone to put new ROM or new release version every 3-4 months. I like a clean slate, keeps the phone in shape
Btw i did buy Storm's utility in morning so guess i am future proof :silly:
One question - I keep reading "you will lose DRM Keys" I thought it meant that Sony removes/disables/dissolves their own files which are required for apps/apks to run like camera. But is that something phone specific? like specific to me? The way everyone keeps saying you will lose that and you will never get it back - i want to know what it means. Like I cannot get it back for my specific phone? or Sony in General is not going to give it out but it is just a generic key/file. Sorry, just trying to understand what it exactly means. I earlier thought it is like that CID i had to backup for my motorola phone because it was my device ID number or a key file specific for my own personal device which once removed made it generic to flash.
---------- Post added at 01:03 PM ---------- Previous post was at 01:02 PM ----------
Didgesteve said:
Xposed won't work with .145, it's a know issue with no workaround as yet.
.75 is the last firmware that Xposed works with.
Edit: sToRm// says that paying for Xperiafix will mean that it will stay up to date with any future firmware releases, so you will be able to go beyond .145, but not until the problems with Xposed are fixed
Click to expand...
Click to collapse
Bollocks!! I don't think i know how to go back to .75 then. Guess i just have to stay on stock till i get bored or xposed runs on .145 right? or whatever is newer out there. Apparently whenever i want to flash an OTA i still have to flash it in flashmode since i am on custom UK firmware so i think i will anyhow get bored and move onto custom pretty soon :fingers-crossed:
I haven't really been much of an OTA person. I usually keep formatting full phone to put new ROM or new release version every 3-4 months. I like a clean slate, keeps the phone in shape
Btw i did buy Storm's utility in morning so guess i am future proof :silly:
One question - I keep reading "you will lose DRM Keys" I thought it meant that Sony removes/disables/dissolves their own files which are required for apps/apks to run like camera. But is that something phone specific? like specific to me? The way everyone keeps saying you will lose that and you will never get it back - i want to know what it means. Like I cannot get it back for my specific phone? or Sony in General is not going to give it out but it is just a generic key/file. Sorry, just trying to understand what it exactly means. I earlier thought it is like that CID i had to backup for my motorola phone because it was my device ID number or a key file specific for my own personal device which once removed made it generic to flash.
---------- Post added at 01:04 PM ---------- Previous post was at 01:03 PM ----------
TheDelta said:
Bollocks!! I don't think i know how to go back to .75 then. Guess i just have to stay on stock till i get bored or xposed runs on .145 right? or whatever is newer out there. Apparently whenever i want to flash an OTA i still have to flash it in flashmode since i am on custom UK firmware so i think i will anyhow get bored and move onto custom pretty soon :fingers-crossed:
I haven't really been much of an OTA person. I usually keep formatting full phone to put new ROM or new release version every 3-4 months. I like a clean slate, keeps the phone in shape
Btw i did buy Storm's utility in morning so guess i am future proof :silly:
One question - I keep reading "you will lose DRM Keys" I thought it meant that Sony removes/disables/dissolves their own files which are required for apps/apks to run like camera. But is that something phone specific? like specific to me? The way everyone keeps saying you will lose that and you will never get it back - i want to know what it means. Like I cannot get it back for my specific phone? or Sony in General is not going to give it out but it is just a generic key/file. Sorry, just trying to understand what it exactly means. I earlier thought it is like that CID i had to backup for my motorola phone because it was my device ID number or a key file specific for my own personal device which once removed made it generic to flash.
---------- Post added at 01:02 PM ---------- Previous post was at 12:57 PM ----------
Bollocks!! I don't think i know how to go back to .75 then. Guess i just have to stay on stock till i get bored or xposed runs on .145 right? or whatever is newer out there. Apparently whenever i want to flash an OTA i still have to flash it in flashmode since i am on custom UK firmware so i think i will anyhow get bored and move onto custom pretty soon :fingers-crossed:
I haven't really been much of an OTA person. I usually keep formatting full phone to put new ROM or new release version every 3-4 months. I like a clean slate, keeps the phone in shape
Btw i did buy Storm's utility in morning so guess i am future proof :silly:
One question - I keep reading "you will lose DRM Keys" I thought it meant that Sony removes/disables/dissolves their own files which are required for apps/apks to run like camera. But is that something phone specific? like specific to me? The way everyone keeps saying you will lose that and you will never get it back - i want to know what it means. Like I cannot get it back for my specific phone? or Sony in General is not going to give it out but it is just a generic key/file. Sorry, just trying to understand what it exactly means. I earlier thought it is like that CID i had to backup for my motorola phone because it was my device ID number or a key file specific for my own personal device which once removed made it generic to flash.
---------- Post added at 01:03 PM ---------- Previous post was at 01:02 PM ----------
Bollocks!! I don't think i know how to go back to .75 then. Guess i just have to stay on stock till i get bored or xposed runs on .145 right? or whatever is newer out there. Apparently whenever i want to flash an OTA i still have to flash it in flashmode since i am on custom UK firmware so i think i will anyhow get bored and move onto custom pretty soon :fingers-crossed:
I haven't really been much of an OTA person. I usually keep formatting full phone to put new ROM or new release version every 3-4 months. I like a clean slate, keeps the phone in shape
Btw i did buy Storm's utility in morning so guess i am future proof :silly:
One question - I keep reading "you will lose DRM Keys" I thought it meant that Sony removes/disables/dissolves their own files which are required for apps/apks to run like camera. But is that something phone specific? like specific to me? The way everyone keeps saying you will lose that and you will never get it back - i want to know what it means. Like I cannot get it back for my specific phone? or Sony in General is not going to give it out but it is just a generic key/file. Sorry, just trying to understand what it exactly means. I earlier thought it is like that CID i had to backup for my motorola phone because it was my device ID number or a key file specific for my own personal device which once removed made it generic to flash.
Click to expand...
Click to collapse
Bollocks I wrote that so many times!!!
TheDelta said:
Bollocks I wrote that so many times!!!
Click to expand...
Click to collapse
There is a partition on your phone called the TA partition with a set of encrypted keys on it that are unique to your phone. So far no one has worked out how to copy the partition and backup the keys. The keys engage with the DRM software and enable higher function apps, like the camera, X-Reality, etc etc.
Unlocking your phone deletes that partiton, you can't get your keys back, gone forever.
Xperiafix engages with the DRM software and fools it into thinking keys are present, all higher funtion apps work as per usual.
Lots of people who don't understand suggest a loss in quality of the camera, but it doesn't work like that. DRM is broken or fixed, the camera is broken or fixed. Simple.
Edit: Magisk 16.4 is working and that has many modules you can add that are similar to Xposed modules. Just don't try adding Xposed until there is a new build released.
Didgesteve said:
There is a partition on your phone called the TA partition with a set of encrypted keys on it that are unique to your phone. So far no one has worked out how to copy the partition and backup the keys. The keys engage with the DRM software and enable higher function apps, like the camera, X-Reality, etc etc.
Unlocking your phone deletes that partiton, you can't get your keys back, gone forever.
Xperiafix engages with the DRM software and fools it into thinking keys are present, all higher funtion apps work as per usual.
Lots of people who don't understand suggest a loss in quality of the camera, but it doesn't work like that. DRM is broken or fixed, the camera is broken or fixed. Simple.
Edit: Magisk 16.4 is working and that has many modules you can add that are similar to Xposed modules. Just don't try adding Xposed until there is a new build released.
Click to expand...
Click to collapse
That actually makes sense now. Reminds me of the time when my moto razr was not allowed to unlock bootloader so a hijack was invented and it did so much just like a normal unlock!
yeah, i got bored of the fingerprint scanner in like <24 hours. Guess it is not for me :silly:
I feel like i like I might get bored of sony pretty soon and just get RR. although would you know if people have found a way to keep the 3d creator or sony camera app etc on custom roms? or what exactly do people use as camera app? I feel like other app should still do pretty much same things for taking the photo as hardware is same? Anyhow i will finally get some time over weekend to research all that before taking the plunge. So far only the 3d creator impressed me, camera settings seem pretty same as other phones so probably won't loose much by going custom?
I did not know magisk had modules, that's new. Will research on that over weekend, who knows maybe it will get me what i need :fingers-crossed:
BTW, sorry i am asking more questions, but do you know if i can install 2nd rom? I mean with recovery i should be able to dual boot right? The idea would be to keep primary stock with rooted .145 without xposed to go back to whenever i want to do the 3d stuff and use custom rom as daily driver. Do you know if that is still possible? I do have a spare 64 GB card from my gopro that i can use here to get more space for other stuff.
TheDelta said:
That actually makes sense now. Reminds me of the time when my moto razr was not allowed to unlock bootloader so a hijack was invented and it did so much just like a normal unlock!
yeah, i got bored of the fingerprint scanner in like <24 hours. Guess it is not for me :silly:
I feel like i like I might get bored of sony pretty soon and just get RR. although would you know if people have found a way to keep the 3d creator or sony camera app etc on custom roms? or what exactly do people use as camera app? I feel like other app should still do pretty much same things for taking the photo as hardware is same? Anyhow i will finally get some time over weekend to research all that before taking the plunge. So far only the 3d creator impressed me, camera settings seem pretty same as other phones so probably won't loose much by going custom?
I did not know magisk had modules, that's new. Will research on that over weekend, who knows maybe it will get me what i need :fingers-crossed:
BTW, sorry i am asking more questions, but do you know if i can install 2nd rom? I mean with recovery i should be able to dual boot right? The idea would be to keep primary stock with rooted .145 without xposed to go back to whenever i want to do the 3d stuff and use custom rom as daily driver. Do you know if that is still possible? I do have a spare 64 GB card from my gopro that i can use here to get more space for other stuff.
Click to expand...
Click to collapse
Apparently Open Camera has lots of good reviews as an alternative to the stock.
Speaking from personal experience, the 'superior auto' isn't all that good, sort of ok if you're in a hurry. But most of the time is doesn't shoot HDR and for some reason a lot of the pictures are 'soft'. So manual is the way to go, HDR on and try and drop the ISO down to 200 and the shutter speed down to 1/15, which is pretty slow, so you might need to rest it on something. Sounds daft saying a mobile phone camera works best if you tripod it, but there we are. Turn of the object tracking and shoot in native 19Mp, edit it to letterbox later if you want that shaped picture, but at least shoot one to one pixel ratio.
No 2nd rom boot option for Oreo TWRP as far as I'm aware. I'm not even sure you can do a successful restore from TWRP, maybe the data partition, but you can't restore a build, there's something to do with encryption that gets in the way. I'm not an expert, maybe ask on the TWRP thread. So TWRP is really just a way of flashing stuff, I don't think you can use it for backup/restore, but I'd love someone to correct me on that.
Didgesteve said:
Apparently Open Camera has lots of good reviews as an alternative to the stock.
Speaking from personal experience, the 'superior auto' isn't all that good, sort of ok if you're in a hurry. But most of the time is doesn't shoot HDR and for some reason a lot of the pictures are 'soft'. So manual is the way to go, HDR on and try and drop the ISO down to 200 and the shutter speed down to 1/15, which is pretty slow, so you might need to rest it on something. Sounds daft saying a mobile phone camera works best if you tripod it, but there we are. Turn of the object tracking and shoot in native 19Mp, edit it to letterbox later if you want that shaped picture, but at least shoot one to one pixel ratio.
No 2nd rom boot option for Oreo TWRP as far as I'm aware. I'm not even sure you can do a successful restore from TWRP, maybe the data partition, but you can't restore a build, there's something to do with encryption that gets in the way. I'm not an expert, maybe ask on the TWRP thread. So TWRP is really just a way of flashing stuff, I don't think you can use it for backup/restore, but I'd love someone to correct me on that.
Click to expand...
Click to collapse
Finally weekend is here!!
I agree on the camera thing you are saying although I don't get what shaped photos mean. I haven't used letter box.
You brought up backup restore, you thought I am talking about switching ROMs using backup restore ?? Yeah I don't think I will) go through that much pain if I cannot just dual boot.
I am just thinking j will read up through the threads this weekend and put lineage or rrr based on what I find out
.75
Didgesteve said:
Apparently Open Camera has lots of good reviews as an alternative to the stock.
Speaking from personal experience, the 'superior auto' isn't all that good, sort of ok if you're in a hurry. But most of the time is doesn't shoot HDR and for some reason a lot of the pictures are 'soft'. So manual is the way to go, HDR on and try and drop the ISO down to 200 and the shutter speed down to 1/15, which is pretty slow, so you might need to rest it on something. Sounds daft saying a mobile phone camera works best if you tripod it, but there we are. Turn of the object tracking and shoot in native 19Mp, edit it to letterbox later if you want that shaped picture, but at least shoot one to one pixel ratio.
No 2nd rom boot option for Oreo TWRP as far as I'm aware. I'm not even sure you can do a successful restore from TWRP, maybe the data partition, but you can't restore a build, there's something to do with encryption that gets in the way. I'm not an expert, maybe ask on the TWRP thread. So TWRP is really just a way of flashing stuff, I don't think you can use it for backup/restore, but I'd love someone to correct me on that.
Click to expand...
Click to collapse
I think I will stay on stock to see how much I enjoy the 960 fpsmode. Do you think I can flash .75 over
145 ? Any risks maybe?? Using xperifirm I can if I have files right?? Any chance you have the .75 version that you can upload or gdrive for me¿