Related
hey i am new to android and got myself a acer liquid e2 as was told it was a good phone for the price etc, i do find this phone very surprising and i am totally happy with it apart from 1 problem i come across about 20 times a day, "storage space" i have plenty of space on my sd card it is the phone that is the problem, and every day i need to keep clearing my data and cache as it shuts all my emails etc down when the space has run out which is annoying when it is servral times a day, i have apps on my phone which i dont use and dont need but cant delete these, ive been reasearching this now for a few weeks and everything that i have came across says root and delete, its not that simple is it? i would say that i can be quite good at this sort of stuff as ive made quite alot of my stuff to operate the way i want it, but every time i see anything about rooting it always say your phone can be bricked and i cant afford it to be bricked, i need it beleive it or not, anyway this site seems to have alot of very brainy and smart people on it, hence why i joined :good: can anyone help me with this problem, easy and safest way, will be most appreciated, i was just about to go down the kingo app way but decided to do more reasearch on it before hand and that has put me off it as people are saying there is stuff about spy cams and malware etc iplease help thanks. oh i ment to say i manage to turn my developer options on by total mistake and playing around with my phone so i have that on , if that helpsnetwork 3 in uk cheers guys.:cyclops: p.s. i have jelly bean 4.2.2
bazzaboy1 said:
hey i am new to android and got myself a acer liquid e2 as was told it was a good phone for the price etc, i do find this phone very surprising and i am totally happy with it apart from 1 problem i come across about 20 times a day, "storage space" i have plenty of space on my sd card it is the phone that is the problem, and every day i need to keep clearing my data and cache as it shuts all my emails etc down when the space has run out which is annoying when it is servral times a day, i have apps on my phone which i dont use and dont need but cant delete these, ive been reasearching this now for a few weeks and everything that i have came across says root and delete, its not that simple is it? i would say that i can be quite good at this sort of stuff as ive made quite alot of my stuff to operate the way i want it, but every time i see anything about rooting it always say your phone can be bricked and i cant afford it to be bricked, i need it beleive it or not, anyway this site seems to have alot of very brainy and smart people on it, hence why i joined :good: can anyone help me with this problem, easy and safest way, will be most appreciated, i was just about to go down the kingo app way but decided to do more reasearch on it before hand and that has put me off it as people are saying there is stuff about spy cams and malware etc iplease help thanks. oh i ment to say i manage to turn my developer options on by total mistake and playing around with my phone so i have that on , if that helpsnetwork 3 in uk cheers guys.:cyclops:
Click to expand...
Click to collapse
Unfortunately removing the preloaded apps won't help your storage issues at all. Those apps are located in a different part of the system (/system/app) than the apps and data (/data/app + /data/data) that you add. You can (if rooted) move apps to the /system/app partition, but they don't always work or update correctly from there as it requires special permissions to run from there. But there really isn't much to do besides rooting it and doing some modifications to your set up. They don't call em budget phones for nothing.
Options include swapping the internal and external mount points so it reads your external as your main internal storage, creating a partition on your external and using a script to link your /data/app and/or /data/data folders to that partition so it reads as one big space (however big you make that partition), or using an app like Folder Mount to create a link between big folders on the internal to the external (mostly helpful for big game data). All of these require a bit of knowledge, but nothing that some time and reading can't help you with. It is not exactly rocket science. Knowing what update you are on though is important, both so you pick the right rooting method (there are multiple options if not on 4.2.2 yet) as well as, if, worst case happens, you know what version of the software you need to reload. You can find this info under Settings / About Phone. Make note of not just the android version, but the build or system version as well as there can be mini updates to software that changes things but not the actual android version.
As far as Kingo, I've never read anything other than hearsay about any potential malicious activity on their part. The reason you see most people freaking out about it is because when it first was introduced, it was known to send IMEI info back to their servers in China. Kingo never tried to hide the fact, explained their position about why they were doing it (diagnostics), and promptly changed how that was done. Now, by nature of what it is doing (root = gaining admin access to the operating system), it needs to download closed sourced scripts and files to gain this access . They don't want to disclose their sources for 2 reasons: 1) if the manufacturers of the phones that don't want it rooted see how it is done, then it's much easier to patch that on the next update and 2) so other people don't steal their work. Makes sense to me, but some people are concerned about closed sources (even though many apps already installed or that you download are closed source as well). I've used it on quite a few devices and have never had problems. You can uninstall the companion app it installs (it does this for some devices to help gain access through a backdoor) and update the SuperSU app and binary it installs via the Play Store, so don't really see it as an issue.
bazzaboy1 said:
hey i am new to android and got myself a acer liquid e2 as was told it was a good phone for the price etc, i do find this phone very surprising and i am totally happy with it apart from 1 problem i come across about 20 times a day, "storage space" i have plenty of space on my sd card it is the phone that is the problem, and every day i need to keep clearing my data and cache as it shuts all my emails etc down when the space has run out which is annoying when it is servral times a day, i have apps on my phone which i dont use and dont need but cant delete these, ive been reasearching this now for a few weeks and everything that i have came across says root and delete, its not that simple is it? i would say that i can be quite good at this sort of stuff as ive made quite alot of my stuff to operate the way i want it, but every time i see anything about rooting it always say your phone can be bricked and i cant afford it to be bricked, i need it beleive it or not, anyway this site seems to have alot of very brainy and smart people on it, hence why i joined :good: can anyone help me with this problem, easy and safest way, will be most appreciated, i was just about to go down the kingo app way but decided to do more reasearch on it before hand and that has put me off it as people are saying there is stuff about spy cams and malware etc iplease help thanks. oh i ment to say i manage to turn my developer options on by total mistake and playing around with my phone so i have that on , if that helpsnetwork 3 in uk cheers guys.:cyclops: p.s. i have jelly bean 4.2.2
Click to expand...
Click to collapse
es0tericcha0s said:
Unfortunately removing the preloaded apps won't help your storage issues at all. Those apps are located in a different part of the system (/system/app) than the apps and data (/data/app + /data/data) that you add. You can (if rooted) move apps to the /system/app partition, but they don't always work or update correctly from there as it requires special permissions to run from there. But there really isn't much to do besides rooting it and doing some modifications to your set up. They don't call em budget phones for nothing.
Options include swapping the internal and external mount points so it reads your external as your main internal storage, creating a partition on your external and using a script to link your /data/app and/or /data/data folders to that partition so it reads as one big space (however big you make that partition), or using an app like Folder Mount to create a link between big folders on the internal to the external (mostly helpful for big game data). All of these require a bit of knowledge, but nothing that some time and reading can't help you with. It is not exactly rocket science. Knowing what update you are on though is important, both so you pick the right rooting method (there are multiple options if not on 4.2.2 yet) as well as, if, worst case happens, you know what version of the software you need to reload. You can find this info under Settings / About Phone. Make note of not just the android version, but the build or system version as well as there can be mini updates to software that changes things but not the actual android version.
As far as Kingo, I've never read anything other than hearsay about any potential malicious activity on their part. The reason you see most people freaking out about it is because when it first was introduced, it was known to send IMEI info back to their servers in China. Kingo never tried to hide the fact, explained their position about why they were doing it (diagnostics), and promptly changed how that was done. Now, by nature of what it is doing (root = gaining admin access to the operating system), it needs to download closed sourced scripts and files to gain this access . They don't want to disclose their sources for 2 reasons: 1) if the manufacturers of the phones that don't want it rooted see how it is done, then it's much easier to patch that on the next update and 2) so other people don't steal their work. Makes sense to me, but some people are concerned about closed sources (even though many apps already installed or that you download are closed source as well). I've used it on quite a few devices and have never had problems. You can uninstall the companion app it installs (it does this for some devices to help gain access through a backdoor) and update the SuperSU app and binary it installs via the Play Store, so don't really see it as an issue.
Click to expand...
Click to collapse
Wow thanks very much, a was not exspecting that reply and so quickly, so thanks , well as i said i am new to the android, and the whole rooting thing makes me nervous as i havent done it before, and i dont want to break my phone, i do know there is always a risk in anything really, but would like to know if possible the best for my phone, i am on jelly bean 4.2.2 and kernel 3.4.5 and is it the build number you need or the custom build version? also i dont know if this is important but i actually dont have wifi and use the usb tethering for my pc to get online, is it still possible to do it this way? cheers
bazzaboy1 said:
Wow thanks very much, a was not exspecting that reply and so quickly, so thanks , well as i said i am new to the android, and the whole rooting thing makes me nervous as i havent done it before, and i dont want to break my phone, i do know there is always a risk in anything really, but would like to know if possible the best for my phone, i am on jelly bean 4.2.2 and kernel 3.4.5 and is it the build number you need or the custom build version? also i dont know if this is important but i actually dont have wifi and use the usb tethering for my pc to get online, is it still possible to do it this way? cheers
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2518094
That's a guide with everything you should need to fix the phone if anything were to happen or to just return it to it's original state if wanted / needed. Read through the thread a bit and see where other members were having trouble and the solutions to those. If you get comfortable with that and how it works, then modding your phone becomes much less scary. And once you are rooted, tethering is even better because you can typically hide your activity much more. I don't know if it is a big deal with carriers around where you live, but here, most people have to pay for tethering or make sure to have special plans that typically cost more than ones that don't include it.
es0tericcha0s said:
http://forum.xda-developers.com/showthread.php?t=2518094
That's a guide with everything you should need to fix the phone if anything were to happen or to just return it to it's original state if wanted / needed. Read through the thread a bit and see where other members were having trouble and the solutions to those. If you get comfortable with that and how it works, then modding your phone becomes much less scary. And once you are rooted, tethering is even better because you can typically hide your activity much more. I don't know if it is a big deal with carriers around where you live, but here, most people have to pay for tethering or make sure to have special plans that typically cost more than ones that don't include it.
Click to expand...
Click to collapse
Thanks very much!! a will go have a look at the thread just now, really appreciate your help and time, thanks
I own a Xperia Z2 D6502 with android 5.1.1 and build number 23.4.A.1.232 which I would like to root. I have never rooted any of my phones before so I dont know anything about it. After spending much time on this forum I found this link but I am not sure if these are the right instructions for my xperia Z2 5.1.1 23.4.A.1.232.
What I understood after reading this article was that after following these instructions I would have a rooted lollipop 5.1.1 version on my phone. However I dont want this. I want any suitable(which makes my phone faster and doesnt affect camera quality) rom(I dont know much about them either) with KitKat on my xperia device.
Can anyone please help me to achieve the above with all the detailed steps as I am totally new to this?
Any help will be highly appreciated.
Follow that guide but in step 3 (Then flash the latest*23.4.A.0.546*zip file, which is pre rooted) flash your kitkat rom or whatever you want. Look in the dev section.
Sent from my D6503 using Tapatalk
o0 Matt 0o said:
Follow that guide but in step 3 (Then flash the latest*23.4.A.0.546*zip file, which is pre rooted) flash your kitkat rom or whatever you want. Look in the dev section.
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
Thank You so much. Can you please suggest me a ROM? And provide a download link?
berbatov93 said:
Thank You so much. Can you please suggest me a ROM? And provide a download link?
Click to expand...
Click to collapse
Which ROM you'll prefer is a personal thing, so read about the different ones, look at any pictures and try one. While looking and researching them you'll find the download links.
Having said that I'm just running a rooted version of the Sony 5.1.1 ROM, version 23.4.A.1.232 and quite like it. Sure it has a heap of apps I don't use but I'm not out of space and everything works.
I've got a few different devices with different builds of AOSP based ROMs on them, it varies as the developers for different devices vary so you end up using what's available for your device.
Given you've never rooted your phone before I'm not sure all of the advanced options of some of the ROMs will do much for you, you can spend hours and hours setting things up how you want and then another update turns up and they don't all handle dirty flashes well.
Why do you want root access and what are you expecting it to do for you?
Cluey said:
Which ROM you'll prefer is a personal thing, so read about the different ones, look at any pictures and try one. While looking and researching them you'll find the download links.
Having said that I'm just running a rooted version of the Sony 5.1.1 ROM, version 23.4.A.1.232 and quite like it. Sure it has a heap of apps I don't use but I'm not out of space and everything works.
I've got a few different devices with different builds of AOSP based ROMs on them, it varies as the developers for different devices vary so you end up using what's available for your device.
Given you've never rooted your phone before I'm not sure all of the advanced options of some of the ROMs will do much for you, you can spend hours and hours setting things up how you want and then another update turns up and they don't all handle dirty flashes well.
Why do you want root access and what are you expecting it to do for you?
Click to expand...
Click to collapse
I just want to explore and learn things. Some problems I face with xperia Z2 are wifi connectivity, my voice isnt clear to other side while on call, low battery life and runs slow given its hardware specifications.
Cant you unistall the apps which occupy your memory given your device is rooted?
And what if I dont update my device?
I also read about losing my drm keys after flashing, though I didnt understand completely what it meant.
I want to install rooted version of Sony 4.4.4 rom but after searching the forum I cant decide which one I should download. Please help.
Cluey said:
Which ROM you'll prefer is a personal thing, so read about the different ones, look at any pictures and try one. While looking and researching them you'll find the download links.
Having said that I'm just running a rooted version of the Sony 5.1.1 ROM, version 23.4.A.1.232 and quite like it. Sure it has a heap of apps I don't use but I'm not out of space and everything works.
I've got a few different devices with different builds of AOSP based ROMs on them, it varies as the developers for different devices vary so you end up using what's available for your device.
Given you've never rooted your phone before I'm not sure all of the advanced options of some of the ROMs will do much for you, you can spend hours and hours setting things up how you want and then another update turns up and they don't all handle dirty flashes well.
Why do you want root access and what are you expecting it to do for you?
Click to expand...
Click to collapse
Sorry to hijack the tread.... Did you have "full root"?
I think i'm having issues on SELinux or mounting permissions.
I can't remove system apps( w/ root uninstaller ), or change system files.
I manually changed selinux (su -c "setenforce 0"), solve it but was not persistent. Installed SELinuxmodechanger, but i think it's not fully working after reboot...
clawpt said:
Sorry to hijack the tread.... Did you have "full root"?
I think i'm having issues on SELinux or mounting permissions.
I can't remove system apps( w/ root uninstaller ), or change system files.
I manually changed selinux (su -c "setenforce 0"), solve it but was not persistent. Installed SELinuxmodechanger, but i think it's not fully working after reboot...
Click to expand...
Click to collapse
Do you have nuts deul recovery installed? Thats meant to disable RIC during boot to make /system rw, allowing you to remove system apps.
Sent from my D6503 using Tapatalk
berbatov93 said:
I just want to explore and learn things. Some problems I face with xperia Z2 are wifi connectivity, my voice isnt clear to other side while on call, low battery life and runs slow given its hardware specifications.
Cant you unistall the apps which occupy your memory given your device is rooted?
And what if I dont update my device?
I also read about losing my drm keys after flashing, though I didnt understand completely what it meant.
I want to install rooted version of Sony 4.4.4 rom but after searching the forum I cant decide which one I should download. Please help.
Click to expand...
Click to collapse
Keep reading mate. If you lose the DRM keys you can't get them back without a backup, you can't use ones someone else backed up either.
I can uninstall some of the preinstalled apps if I want but as I haven't run out of space I haven't yet. I'm also interested in seeing what Sony does with them, some I'll not use and others I glance at.
Battery life is pretty impressive for me but it varies with how you use your device. I play Ingress and if I'm out playing I get five hours, that's with the screen on, GPS and data going. Not many phones can do that.
Calls are normally clear although I've noticed that if I'm lying on my bed talking it doesn't cope very well, I have to twist my head so the ear I'm using is away from the pillow. I assume it's because the noise cancelling microphone is on the top and gets confused/muffled as when I move my head it's great. I've had people comment on how clear I sound on this phone.
I've not had any trouble with WiFi and haven't felt the phone is slow. So how are you determining that your device is slow? What is it doing which makes you feel it is slow?
Not sure what you mean by not updating your device. If you mean not updating the ROM nothing really happens but as time passes there is a greater chance that apps will stop working, it depends on what you use and if the makers of them what a minimum Android version for them. Also if there are security flaws the longer you used an unpatched device the greater the chance that you'll get compromised. It is quite irritating that we're not fully patched for Stagefright yet.
As for the original question about how to root this ROM version, the short answer is, you can't. Well not yet that I've seen.
To root the phone you have to downgrade, gain root and then upgrade to what you want to run while keeping root. You found the guide already, follow it. If you don't understand or aren't confident about doing it I'd suggest not doing it. If it's your only device and primary phone is it worth breaking it and being without a phone?
If you want to learn about Android devices in general pick up a cheap device to play with and learn on, the Z2 is still quite expensive. You could probably pick up one with a broken screen pretty cheaply online, as long as you can read the screen you can play around and learn on it. Just plug a mouse in if the digitiser doesn't work.
I used a stock Samsung GS2 for years while reading about things, then I got a tablet and started playing with that as it was just inconvenient to me if I broke it, I still had a working phone.
@clawpt I'm not sure what you mean by "full root". I can uninstall things if I want though, perhaps Matt's reply will help you.
o0 Matt 0o said:
Do you have nuts deul recovery installed? Thats meant to disable RIC during boot to make /system rw, allowing you to remove system apps.
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
Yes. I'm using "Z2-lockeddualrecovery2.8.x-RELEASE.flashable.zip". I'm on unlocked bootloader, maybe i need to use the other variant (i'm on stock kernel, should not be a problem)?
Cluey said:
@clawpt I'm not sure what you mean by "full root". I can uninstall things if I want though, perhaps Matt's reply will help you.
Click to expand...
Click to collapse
Meaning that you also have rw permissions.
I can't delete system apps, i can't modify/create a file at "/".
Cluey said:
Keep reading mate. If you lose the DRM keys you can't get them back without a backup, you can't use ones someone else backed up either.
Click to expand...
Click to collapse
I will try to back them up given they are still there because I already rooted my phone to pre rooted stock rom 5.1.1 as mentioned in the guide I found.
Calls are normally clear although I've noticed that if I'm lying on my bed talking it doesn't cope very well, I have to twist my head so the ear I'm using is away from the pillow. I assume it's because the noise cancelling microphone is on the top and gets confused/muffled as when I move my head it's great. I've had people comment on how clear I sound on this phone.
Click to expand...
Click to collapse
Maybe I have hardware issues or network problems as people usually complain about my voice being not clear.
I've not had any trouble with WiFi and haven't felt the phone is slow. So how are you determining that your device is slow? What is it doing which makes you feel it is slow?
Click to expand...
Click to collapse
Sometimes my device doesnt connect to saved wifi networks automatically, I have to connect it manually.
If I open too many tabs in my chrome browser, chrome crashes. Sometimes dialer also takes too much time to open.
Not sure what you mean by not updating your device. If you mean not updating the ROM nothing really happens but as time passes there is a greater chance that apps will stop working, it depends on what you use and if the makers of them what a minimum Android version for them. Also if there are security flaws the longer you used an unpatched device the greater the chance that you'll get compromised. It is quite irritating that we're not fully patched for Stagefright yet.
Click to expand...
Click to collapse
I meant update that sony provides. After rooting my phone I am still getting updates from sony(I didnt expect them), so if I update using sony updates will my phone lose its root status(I mean will it still be rooted)?
As for the original question about how to root this ROM version, the short answer is, you can't. Well not yet that I've seen.
To root the phone you have to downgrade, gain root and then upgrade to what you want to run while keeping root. You found the guide already, follow it. If you don't understand or aren't confident about doing it I'd suggest not doing it. If it's your only device and primary phone is it worth breaking it and being without a phone?
Click to expand...
Click to collapse
I wasnt much confident but still I proceeded with the steps mentioned in the guide and with a little help from google, I was fortunately able to root my device. Yes, its the only phone I have but I couldnt afford a new one and I waited too long for its warranty to expire.
Can you please provide me with a source to learn about general concepts involved in rooting like flashing, busybox, unlocking boot loader, etc. I am trying to google each thing individually, but i cant seem to find a place where I could learn things in a proper order, moving from basics to more advanced concepts.
Thank you so much for your help.
I would like you to clear one more thing for me, when I followed the guide, I first flashed my device with 17.1.2.A.0.314 ftf file and then installed flashable_D6502_23.4.A.0.546.zip from the recovery menu. So what is a ftf file and what is the difference between the two steps I followed. In my understanding, both basically did the same thing, i.e., installing a new rom. Is ftf file sony specific?
Thanks again.
@berbatov93 definitely back up the DRM keys before unlocking the boot loader, it was a fairly simple process from memory.
We need more information on the sound problem. Does it happen consistently? If it isn't consistent look for a common situation when you have the problem, like loud noises, high wind etc. Have you used the diagnostics tool to test the microphone? It's in Settings > About phone > Diagnostics.
Thinking about it a bit more, sometimes there seems to be a little pause for people to hear me. I'm not sure if it's phone or network based, I guess it could be phone related while it works out the background noise cancelling magic.
WiFi being slow to connect is a better description than, "my device is too slow."
Sometimes I notice that it hasn't automatically connected to my WiFi when I get home but by the time I notice and look it's connecting. Is that what you mean?
What setting do you have the WiFi on when the phone is asleep? Settings > WiFi > ... menu > Advanced > Keep Wi-Fi on during sleep.
Everything is slow with lots of Chrome tabs open, you could try a different browser or just be better at closing tabs.
I've never noticed any slow launching with the dialer, perhaps your call history is huge? Try backing it up with an app from the Play Store and then deleting it to see if that is the cause. Each time you open it it looks at that to display it.
As you're on a stock ROM it will notify you that there is a new update. If you let it update though you'll lose root and then have to downgrade again to get it back. I just wait for the update to be available through XperiFirm, download it and make a pre-rooted flashable zip. There is a thread about how to do that here. That thread will also answer your question about what you did which seemed like flashing two ROMs, you did but in different ways.
I still don't know enough so I can't answer your questions but it looks like your Google Fu is weak. :silly:
Try this link, it won't always be the top search result though.
There are lots of different summaries about what rooting does for you, I don't want to try and summarise them for you. (I'd rather go to bed, it's 4:30am for me!)
Just reading a description of one of the various Busybox installers on the Play Store should answer that question, I bought this one. I can't remember if a friend recommended it to me or something I read somewhere, but I bought it as I appreciated the effort the developer put in for the rest of us to use. The same with SuperSU Pro.
Bootloaders are trickier, probably something you'll get better answers by reading more or using Google. These days they seem to all be locked with a way of unlocking them from the device manufacturer which lets them record your IMEI or serial number. I assume they do this so if you send it back for a warranty claim they can see you've unlocked it and then charge you to fix something you've screwed up. I've never taken anything back so I don't know.
They're something I have to learn more about too but if you find out more before me please fill me in.
Cluey said:
definitely back up the DRM keys before unlocking the boot loader, it was a fairly simple process from memory.
Click to expand...
Click to collapse
Should I use this to take backup? And what kind of backup should I take to recover my device from bootloop? I wanted to install xposed on my device, but it was warned somewhere that sony devices might go into bootloop and that I should take a backup to restore my device. What kind of backup can help me recover my device from bootloop or soft brick?
We need more information on the sound problem. Does it happen consistently? If it isn't consistent look for a common situation when you have the problem, like loud noises, high wind etc. Have you used the diagnostics tool to test the microphone? It's in Settings > About phone > Diagnostics.
Thinking about it a bit more, sometimes there seems to be a little pause for people to hear me. I'm not sure if it's phone or network based, I guess it could be phone related while it works out the background noise cancelling magic.
Click to expand...
Click to collapse
It happens most of the time, even when I am in a closed room with no background disturbances.
WiFi being slow to connect is a better description than, "my device is too slow."
Click to expand...
Click to collapse
That was a wifi issue, it just didnt connect automatically, I had to do it manually even for saved networks.
Sometimes I notice that it hasn't automatically connected to my WiFi when I get home but by the time I notice and look it's connecting. Is that what you mean?
What setting do you have the WiFi on when the phone is asleep? Settings > WiFi > ... menu > Advanced > Keep Wi-Fi on during sleep.
Click to expand...
Click to collapse
It just shows connecting but doesnt connect until select the network. Keep wifi on during sleep was enabled.
Everything is slow with lots of Chrome tabs open, you could try a different browser or just be better at closing tabs.
Click to expand...
Click to collapse
Then maybe its a chrome issue.
As you're on a stock ROM it will notify you that there is a new update. If you let it update though you'll lose root and then have to downgrade again to get it back. I just wait for the update to be available through XperiFirm, download it and make a pre-rooted flashable zip. There is a thread about how to do that here. That thread will also answer your question about what you did which seemed like flashing two ROMs, you did but in different ways.
Click to expand...
Click to collapse
I needed 4.4.4 pre rooted stock ROM for D6502 but cant seem to find it anywhere. I read the steps in the thread you mentioned about creating a pre rooted ROM, but steps are not explained in detail for someone new like me. I am also scared a little to try something new on my device as I am already facing a few problems. Can you provide me with a link with much more detailed steps?
I still don't know enough so I can't answer your questions but it looks like your Google Fu is weak. :silly:
Try this link, it won't always be the top search result though.
Click to expand...
Click to collapse
I feel silly now.
Bootloaders are trickier, probably something you'll get better answers by reading more or using Google. These days they seem to all be locked with a way of unlocking them from the device manufacturer which lets them record your IMEI or serial number. I assume they do this so if you send it back for a warranty claim they can see you've unlocked it and then charge you to fix something you've screwed up. I've never taken anything back so I don't know.
They're something I have to learn more about too but if you find out more before me please fill me in.
Click to expand...
Click to collapse
Will sony be able to fix my device in case I screwed up and bricked it?
Thanks.
@berbatov93 I'm sure Sony will fix it if you pay them too!
Hopefully it won't come to that though, they're pretty hard to brick because of the way they've set things up. Even if you soft brick it you can power it off, fire up the flash tool and then hold volume down and plug USB in, press flash and it'll put a base Sony ROM on for you. I've kept the D6503_17.1.A.2.55_Generic AU 1281-9715.ftf file on my PC for just that reason but I haven't had to reuse it yet.
I don't know of any other instructions for making your own pre-rooted zip file, it took me a fair bit of reading and looking at menu options to work it out the first time but it's pretty easy. You won't screw your phone up with it as it will fail before you get it to the phone if you do it incorrectly. As with most things in life you have to learn from experience, just follow the instructions with the programs open so you can refer back to them. You could try Google for better instructions, I'm not sure if anyone wrote something more newbie friendly.
As for the WiFi problem perhaps a different ROM version will sort it out, also you might want to get all your data off your phone and do a completely fresh install on it and see if that sorts it out. The backups people talk about as Nandroids are done from in the custom recovery, have a look in there now you've got it working again. I'm not going to reply to the other thread as I see you did it all again.
I doubt there are any pre-rooted 4.4.4 still around as most people have moved on. There's probably no need to make a pre-rooted one though, one of the root exploits works on it so you could just download, via XperiFirm, the 4.4.4 you want and flash it, then root it. I've never downloaded a pre-rooted ROM as I'm overly cautious, I'm not even keen on using the one click root programs as I can't read what they're doing!
You could call it a Chrome problem but I'd really call it a user problem. Like I said originally you could try another browser and see if it copes better but they aren't really designed to have lots of tabs open. Each tab takes up memory, so you'll fill it all up and then it will start using virtual memory but eventually it will crash. It happens on desktop computers too, I've got 8GB of RAM in my PC but Chrome eats it all up if I open too many tabs.
I don't know what to do about your mic problems in call, I'd take it back to where you got it from and see what they say. But I'm pretty sure you've waited too long as you indicated it was out of warranty which is why you've started looking at root options now. If you've been having problems for a while you should have taken it back before you lost that. It's still worth asking the store/phone company about it though, just make sure they don't go charging you anything to fix it without asking you about it.
You might just have to chalk it up to experience and live with it. Never be afraid to ask for things to be looked at while the warranty is valid, it might be inconvenient but if something needs fixing it's better to use the warranty than pay for it.
The other option would be to use a headset for calls, I picked up an SBH52 and I'm pretty happy with it. As long as you don't lose or break it it will work with whatever phone you end up replacing your Z2 with.
Long time, no post. So, I'm wondering if anyone else has been having RAM issues with their S9+? I've attached a few screenshots. My RAM fills up 1-3 times a week with 300-600MB free, and I have to reboot the device because the phone becomes so slow that it's unusable. Music playback will get choppy, the UI lags badly... A reboot fixes it.
My device is unlocked, carrier is Viaero, so no odd carrier bloatware.
I am using the stock ROM, all up to date, and stock launcher. Most of the bloatware has been disabled, including the unfortunate Bixby. I've had this phone since June and the memory leak has been a constant feature across updates. I cannot pinpoint an app that would be causing it, and using the in built device management will never show me what's hogging up memory. The tool itself will only clear 200-400MB out of RAM, and the device will faithfully fill it back in while remaining sluggish.
Does anyone have some ideas what I can do aside from resetting the device? I hate to waste several hours of my life only to be back in the same boat.
This is bad enough that I am considering seeing if my carrier will just take it back and buying a OnePlus 6T.
kozad said:
Long time, no post. So, I'm wondering if anyone else has been having RAM issues with their S9+? I've attached a few screenshots. My RAM fills up 1-3 times a week with 300-600MB free, and I have to reboot the device because the phone becomes so slow that it's unusable. Music playback will get choppy, the UI lags badly... A reboot fixes it.
My device is unlocked, carrier is Viaero, so no odd carrier bloatware.
I am using the stock ROM, all up to date, and stock launcher. Most of the bloatware has been disabled, including the unfortunate Bixby. I've had this phone since June and the memory leak has been a constant feature across updates. I cannot pinpoint an app that would be causing it, and using the in built device management will never show me what's hogging up memory. The tool itself will only clear 200-400MB out of RAM, and the device will faithfully fill it back in while remaining sluggish.
Does anyone have some ideas what I can do aside from resetting the device? I hate to waste several hours of my life only to be back in the same boat.
This is bad enough that I am considering seeing if my carrier will just take it back and buying a OnePlus 6T.
Click to expand...
Click to collapse
Have you looked in developer options > running services? Worth sending a screenshot of that
mtm1401 said:
Have you looked in developer options > running services? Worth sending a screenshot of that
Click to expand...
Click to collapse
How do I access the Dev options on this phone?
kozad said:
How do I access the Dev options on this phone?
Click to expand...
Click to collapse
About phone > software information > spam build number
Here you go. =)
kozad said:
How do I access the Dev options on this phone?
Click to expand...
Click to collapse
About phone > software information > spam build number
I guess when the damn thing decides to bog down again, I'll pop into this, or try to at least, and see what Samsung's malfunction is - I'll post a screenshot of it as well.
kozad said:
Here you go. =)
Click to expand...
Click to collapse
Nothing stands out on that, but it is saying you've got 2gb free. Have a look again when it slows down?
The one app that really made my phone choppy was Snapchat when its running in the background as it's so badly coded
---------- Post added at 09:33 AM ---------- Previous post was at 09:31 AM ----------
kozad said:
I guess when the damn thing decides to bog down again, I'll pop into this, or try to at least, and see what Samsung's malfunction is - I'll post a screenshot of it as well.
Click to expand...
Click to collapse
Actually check your cached processes as well see if there's anything big in there
mtm1401 said:
Actually check your cached processes as well see if there's anything big in there
Click to expand...
Click to collapse
I'm trying - the damn thing refreshes constantly, so you'll see duplicates in these.
kozad said:
I'm trying - the damn thing refreshes constantly, so you'll see duplicates in these.
Click to expand...
Click to collapse
Still looks like you've got plenty of ram free. I'd suggest getting something like simple system monitor and check it whenever you get lags
Also when you factory reset did you install from fresh or restore your apps?
I just want to chime in and say that I have this EXACT same issue. It the issue first began to occur back in an August 2018 update; the issue started every 3 days and now it is every single day I have to reboot. Once the ram gets down to 2-300 MB available, the system just tanks and becomes extremely sluggish, laggy and unusable - not to mention HOT.
I have tried uninstalling apps, googling fixes that other similar users experience... no fix. However, the more and more I read about the issue, I am beginning to believe we may have a botched firmware update or something, but definitely something bad on Samsung's end - and a memory leak sounds very plausible.
mtm1401 said:
Still looks like you've got plenty of ram free. I'd suggest getting something like simple system monitor and check it whenever you get lags
Also when you factory reset did you install from fresh or restore your apps?
Click to expand...
Click to collapse
Never bothered doing a restore - it takes forever to get everything re-installed.
And yes, memory was fine at time of screens, I will take some more and post them here when the phone bogs down again. =)
I want to say I was having a similar problem. I have an unlocked s9+ on Sprint. Running stock (no root of course), applied the hotspot hack, disable bixby, disabled most Samsung apps that I could run Google's alternatives (including Pixel launcher), bxactions for torch. I would get the slow down every 1-2 days requiring a restart. I've since did a factory reset and only applied the hotspot app and hid the Samsung apps in a folder that I downloaded Google alternatives for instead of disabling them with SAC. I can say that I've only had one slow down that eventually resolved itself after about 10 seconds not requiring a restart. It's been over a week and it looks promising.
I have the unlocked international version. The phone slowed to a crawl once and I uninstalled some apps I wasn't using. Can't remember which but the lag disappeared.
I really think theres something wrong with these phones, whether it be a specific batch of hardware or software or both.
Another case with the exact same problem.
https://forums.androidcentral.com/s...ystem-apps-usage-over-4gb-no-recent-apps.html
Happening again right now. Nothing is jumping out at me. Got screenshots here. Dipping down to 230MB, up to 480. Lots of lag, phone is very sluggish.
kozad said:
Happening again right now. Nothing is jumping out at me. Got screenshots here. Dipping down to 230MB, up to 480. Lots of lag, phone is very sluggish.
Click to expand...
Click to collapse
Nothing looks untoward in there, might be worth going in cached again as that's where most of the RAM is being taken (note that list doesn't add up to the amount being used) . The other consideration is that low 'free RAM' isn't necessarily a bad thing, it just means it's being utilised. (Cached processes should be automatically closed down if more RAM is required) It's likely that a rogue app is hogging a processor (I find Snapchat makes my phone very laggy as it's poorly coded). If you can't find anything untoward I'd recommend doing a reset and manually restoring. Appreciate it's a pain but not sure what else you can do. If it persists then take it back to Samsung
mtm1401 said:
Nothing looks untoward in there, might be worth going in cached again as that's where most of the RAM is being taken (note that list doesn't add up to the amount being used) . The other consideration is that low 'free RAM' isn't necessarily a bad thing, it just means it's being utilised. (Cached processes should be automatically closed down if more RAM is required) It's likely that a rogue app is hogging a processor (I find Snapchat makes my phone very laggy as it's poorly coded). If you can't find anything untoward I'd recommend doing a reset and manually restoring. Appreciate it's a pain but not sure what else you can do. If it persists then take it back to Samsung
Click to expand...
Click to collapse
Typically my phone will have anywhere between 1.1 and 2GB free. I check it periodically because of the slowdowns, and it only gets that low when the phone bogs down. it's the same on my desktop computer, when my Ram gets really low the computer comes to a crawl, so it just seems to be something emblematic of technology in general.
Also, screenshots of cached are in the mix with these other screenshots. the phone was so slow while I was trying to scroll down the list of cached apps, the list would just completely go blank and then repopulate with a different apps. ?
And I do not use Snapchat, but I've heard that complaint often about the Android version of the app.
Sadly I cannot take it back to Samsung, I did not buy it from them. I am making payments to my carrier for the phone and they refuse to simply let me relinquish the device.
When I get time off of work, I will probably go ahead and do the restore, although I would much rather just smash the phone on the ground and stomp on it until there's nothing left that can't be vacuumed up. That honestly sounds like a more productive waste of time to me. ?
After this experience, I will probably just go ahead and cough up the $800 to pay this darn thing off and throw it on eBay for $500 or whatever it is they are going for these days. I feel very burnt by Samsung and my carrier as well.
kozad said:
Typically my phone will have anywhere between 1.1 and 2GB free. I check it periodically because of the slowdowns, and it only gets that low when the phone bogs down. it's the same on my desktop computer, when my Ram gets really low the computer comes to a crawl, so it just seems to be something emblematic of technology in general.
Also, screenshots of cached are in the mix with these other screenshots. the phone was so slow while I was trying to scroll down the list of cached apps, the list would just completely go blank and then repopulate with a different apps. ?
And I do not use Snapchat, but I've heard that complaint often about the Android version of the app.
Sadly I cannot take it back to Samsung, I did not buy it from them. I am making payments to my carrier for the phone and they refuse to simply let me relinquish the device.
When I get time off of work, I will probably go ahead and do the restore, although I would much rather just smash the phone on the ground and stomp on it until there's nothing left that can't be vacuumed up. That honestly sounds like a more productive waste of time to me. ?
After this experience, I will probably just go ahead and cough up the $800 to pay this darn thing off and throw it on eBay for $500 or whatever it is they are going for these days. I feel very burnt by Samsung and my carrier as well.
Click to expand...
Click to collapse
Can you not do scroll capture to get everything?
Yea Snapchat won't be the only rogue app, that's why I suggest getting an app that can monitor your processor usage.
So I'm in the UK - don't know how US warranty laws work but i would assume there is a year's manafacturer warranty were they have to look at your phone within a certain period regardless of the carrier? Between them and your carrier I'm sure you'd be covered if there is something wrong with the phone that's not your fault? (I'm ignorant of US contract law so might be wrong, I'll have a Google when I get a second )
Samsung UK have actually been quite good to me so it's worth giving the US guys a call!
mtm1401 said:
Can you not do scroll capture to get everything?
Click to expand...
Click to collapse
Is that an app?
Also. I will need to look into the warranty process. If I have to mail the phone off, I'll still need to buy a new phone because I'll die of boredom at work without one.
Aight so I have this Samsung Galaxy J7 Max that I've been trying to unlock for more than 2 years now. I of course, don't want to lose the super important data it holds. It got locked out randomly and hasn't been able to take up the pattern I had put on it till date. I'm absolutely sure no one changed its lock screen pattern and its the phone that is unable to recognize the exact same password it had before this happening. I got hold of it today and yet again, started looking for solutions on YouTube and the internet itself. After all of my research, one thing is clear. There is only one way that the pattern lock can be removed in such a condition; by deleting this system folder called gesture.key that lies within the phone itself. I am by no means a nerdy software dev or something but I do have very little knowledge about these workarounds. I used an ADB via a cmd terminal to contact my phone. But it turns out that due to my usb debugging setting not being turned on in my phone, the adb didn't have the required authorization to make any changes to the target. I then got my phone into stock recovery mode and chose the Install through ADB option there. Now when I input the command adb devices, the prompt showed me my device ID, but instead of the "unauthorized" indicator beside it, it now had the indicator "sideload". I had no idea of what had to be done when such happens, so I tried the adb shell > cd data/system > su > rm *.key [taken from an XDA forums thread] commands again. But right on the second step it displayed error this time. I have tried using a key eraser via sd card too, but it just doesn't happen, the sd card folder in the stock mode does not display the contents of the folder.
Now the phone isn't being an obstacle in my life right now, but I really hope there's a way to fix it. Early help would be appreciated. Thank You.
If the data is super important why isn't it redundantly backed up?
Having a set lock screen and storing data on the OS is a sure fire way to lose data, eventually.
Maybe you'll get lucky... is that drive encrypted?
If not it may still be corrupted and unusable.
Don't put yourself in this position again... been there, done that
@blackhawk As I said, this was an absolutely random incident, had never even thought this could've been the case someday. Its not like the phone crashed and then this happened, I turned off my phone's display and the next time I woke it up, the pattern wasn't working anymore. Furthermore, the timed attempts that happen after 5 incorrect tries wasn't existing anymore. Now it could be that someone did get the timed attempts wrong as well [it isn't my own phone]. But I really don't see any other reason to that occurrence.
About the backups, I mean cmon, I was 15 back then, a medico student even more so. I never got my hands around backing up anything. But yes, have been backing up every single bit of data within these two years.
The storage drive shouldn't be encrypted. It was a regular phone bought online that had pdfs, images, recordings and videos stored. The google account was not that of the owner either! It was my uncle's account that was being used ever since he bought it. And since there was never a problem having used his account for quite a while, we never cared to change it to a new google account. Now my uncle's google account itself handles another device, his own phone, exact same model, Galaxy J7 Max. I have tried using his account at the Google Find My Device app to locate and unlock the phone that way [I hope you know it has the three options Ring, Secure and Erase Data]. But it happens so that the Secure phone with password option only for devices that have been lost and don't have a security lock already setup, which wasn't, unfortunately, my case. So that option was greyed out.
For the data corruption, you might be correct. But that phone still does receive SMS texts, calls, whatsapp texts and other notifications. They just don't show up on the lock screen anymore. I honestly had the "Screw the data, I'll erase it anyway" thought yesterday, but during my latest tries, I found the XDA forums website to be quite helpful. Had not it been the damn USB debugging, the solution I approached from this forum would've got the job done in a couple minutes. Again, if the data might've gone corrupted, I will erase the data [I mean I would have to]. But this little glimmer of hope that I experienced yesterday is what is preventing me from doing that. I really hope there is a fix to my situation.
@Chinmay47
a phone can get booted into these modes
Normal ( AKA Android OS )
Recovery
Fastboot
Sideload
EDL
Sideload mode is used to flash OTAs and/or ROMs.
Recovery mode allows you to perform some ADB actions as e.g. pull userdata, but this reqires ADB ( read: USB debug ) got enabled.
So my guess is you can't recover phone's userdata at your own, this would have to be done by an external service who can pull out phone's internal SD-card and has the forensic tools to read it.
@jwoegerbauer Surprisingly the idea of taking the phone to a forensic service struck me yesternight too. As you mentioned, since I can't recover the phone's data myself, all tips and tweaks on the web should now be struck off of my list of solutions. I'll leave the data to some forensic services then. Let's hope the recovery is worth the hassle. The thread is still open to more suggestions though. Thanks for the replies everyone. Really appreciate it!
Chinmay47 said:
@jwoegerbauer Surprisingly the idea of taking the phone to a forensic service struck me yesternight too. As you mentioned, since I can't recover the phone's data myself, all tips and tweaks on the web should now be struck off of my list of solutions. I'll leave the data to some forensic services then. Let's hope the recovery is worth the hassle. The thread is still open to more suggestions though. Thanks for the replies everyone. Really appreciate it!
Click to expand...
Click to collapse
It not a card they can pull. More than likely it's on a BGA chipset, the hardest kind there is to work with.
If they can't access the data on/with the mobo they will have to unsolder the chipset without damaging it then put it into a test jig or another mobo (after pulling that mobo's matching chipset).
If they can access the data on the mobo, not so bad. Otherwise not so good.
Let us know how this plays out for you.
Here's one I found showing you this complex procedure: https://flashfixers.com/recover-data-dead-phone-chip-off-data-recovery/
They may be able to help you, but I have no personal knowledge of this company.
blackhawk said:
If they can't access the data on/with the mobo they will have to unsolder the chipset without damaging it then put it into a test jig or another mobo (after pulling that mobo's matching chipset).
Click to expand...
Click to collapse
Actually thought of this idea right after a couple days from the beginning of the problem. Yes its gonna take loads of precision and patience but it does sound doable. Maybe that's what is gonna be the last option for the forensic service too in case, god forbid, they aren't able to do it the "simple" way. Can't say yet, but I'm gonna keep this thread updated with all the developments that take place.
Chinmay47 said:
Actually thought of this idea right after a couple days from the beginning of the problem. Yes its gonna take loads of precision and patience but it does sound doable. Maybe that's what is gonna be the last option for the forensic service too in case, god forbid, they aren't able to do it the "simple" way. Can't say yet, but I'm gonna keep this thread updated with all the developments that take place.
Click to expand...
Click to collapse
If they need to remove the chipset the chances of failure increase. Flash memory retension is generally good for 10+ years but it may be damaged in the removal process if so, snake eyes.
Get price quotes up front for the whole process.
Once they got the phone, they got you by the balls. Not saying they aren't trustworthy but feel them out. If it's a couple hundred and you get the data back, you did good.
No idea of the cost though, my guess is $400-1000+ especially if they need to pull the chipset.
That's high risk even if they do it by the book.
If their policy is no data, no charge... expect higher rates to cover their loses.
@blackhawk All of that sounds kinda terrifying if you ask me. Well I mean, there is always a first option that can be tried without any mentions of pull-aparts. Yet I will surely judge the person well before I hand my device in his hands. I would try my level best to not take it to the critical stage, but if it needs be and there is a really high chance of losing my data, I can factory reset my data at home by myself too can't I? Future shall tell I suppose.
If you factory reset it all data will be lost.
It will not be recoverable!
If you want the data you will need to use a service like I showed you. They will need physical access to the phone to recovery the data.
The phone may be scrape afterwards
@blackhawk Sure does look like it would be! But paying to get your phone reset for you is way to harsher than doing it yourself. It is only in case the data is nearly impossible to recover that I'll reset the phone myself.
Chinmay47 said:
@blackhawk Sure does look like it would be! But paying to get your phone reset for you is way to harsher than doing it yourself. It is only in case the data is nearly impossible to recover that I'll reset the phone myself.
Click to expand...
Click to collapse
Reset? Most likely destroyed.
Do you really want the data?
blackhawk said:
Reset? Most likely destroyed.
Do you really want the data?
Click to expand...
Click to collapse
I actually do though. But well, if it ain't coming back then why wish for it. Yeah the data was really important.
Chinmay47 said:
I actually do though. But well, if it ain't coming back then why wish for it. Yeah the data was really important.
Click to expand...
Click to collapse
Call them up and see what they say.
Since it's not physically damaged they may be able to access it none invasively.
blackhawk said:
Call them up and see what they say.
Since it's not physically damaged they may be able to access it none invasively.
Click to expand...
Click to collapse
I'll do that and report back ASAP. Thanks for the help sire!
Pretty much as the title says. I'm stock and unrooted, but the idea of an update that blows a physical fuse and can't be undone gives me the shakes. So I held off since it came out. We're about a month into deployment of the update, so I'm now considering applying it. Has anything in terms of major bugs/performance problems come out that should factor into my decision? I've read various threads here and not seen much major stuff.
Thoughts and input? Thanks in advance.
One reason for not going to Android 13 would be that It can mess up the wireless charging function . Mine has not worked properly since I updtaed , even after the patch ( which was supposed to fix it ) it still doesnt work .
Thanks. I've never used wireless charging but I appreciate this caveat to the A13 update.
Other than that all seems good , bit annoying for me as I use wireless charging a lot , have one in my car and this was a major factor in me buying a Pixel 6 . Had high hopes when they rolled out a patch pretty quick but nothing seemd to of changed .
Sad to hear it broke.
I'm afraid to accept major updates after the very final update ever for my OnePlus 6T broke several key functionalities I relied on. That led me to the Pixel 6, which I don't love but it is working "fine" and I hope A13 won't nuke me. I will likely update this weekend unless I hear something widespread and impactful to how I use the phone.
accessibility service not possible in non-store apps
miss said:
accessibility service not possible in non-store apps
Click to expand...
Click to collapse
WHAT... That's horrible... ACR won't work ) :
miss said:
accessibility service not possible in non-store apps
Click to expand...
Click to collapse
Just go to app info, click on 3 dot menu to bypass restriction.
I updated and I'm pretty happy. IIRC there's now a "developer" Android 12 build that works on the Android 13 bootloader if it ends up not being for you for any reason. I haven't seen any significant issues, though now I see people mentioning wireless charging I did notice it kept popping up the little "100%" screen every 5 or 6 minutes like I'd just put it on the charger when I was using the one in my car, after it hit full, but not the one in my room that provides a higher wattage. Either way, not a big issue to me.
Just be sure to read the other threads about updating to 13 and sideload the OTA after you update if you want to be certain you won't accidentally brick booting the un-updated partition after updating. It gave me a hassle sideloading from both of my PCs, but if you use USB 2.0 it'll go through, just... reeeeeally... sloooowly - so you could let it go overnight.
Jaitsu said:
I updated and I'm pretty happy. IIRC there's now a "developer" Android 12 build that works on the Android 13 bootloader if it ends up not being for you for any reason. I haven't seen any significant issues, though now I see people mentioning wireless charging I did notice it kept popping up the little "100%" screen every 5 or 6 minutes like I'd just put it on the charger when I was using the one in my car, after it hit full, but not the one in my room that provides a higher wattage. Either way, not a big issue to me.
Just be sure to read the other threads about updating to 13 and sideload the OTA after you update if you want to be certain you won't accidentally brick booting the un-updated partition after updating. It gave me a hassle sideloading from both of my PCs, but if you use USB 2.0 it'll go through, just... reeeeeally... sloooowly - so you could let it go overnight.
Click to expand...
Click to collapse
So, even unrooted and stock I have to fuss with the side load update thing?
Frankenscript said:
So, even unrooted and stock I have to fuss with the side load update thing?
Click to expand...
Click to collapse
You don't have to, it's just eliminating an unlikely risk. It'll work fine after just updating. Even if the update somehow failed you'd be safe as it would just roll back; the risk only lies in if you update, successfully boot, and then something causes Android to fail to boot, which should never happen if you're not rooted and tinkering with things.
Basically:
* Your phone has two "system" slots.
* Either taking an OTA from an automatic system update, or manually sideloading it, updates the slot you're not on, then switches to it.
* When you update to 13 and it successfully boots, a flag is set that permanently prevents booting with an older bootloader. (This is a one-time thing and shouldn't happen again with future updates.)
* At this point, if something caused Android to fail to boot, it might try to boot into the un-updated system slot. Because that flag is set and it still has the old bootloader, it wouldn't boot and would be bricked.
* Sideloading the OTA again (or even getting another automatic update, but that won't happen immediately) ensures this won't happen by updating the other slot.
Personally I'd just do it because I'm paranoid (and moreso because I personally do root and tinker with things I shouldn't all the time ).
Lughnasadh said:
Just go to app info, click on 3 dot menu to bypass restriction.
Click to expand...
Click to collapse
with any apk file, any application?
I use many that are not from any official store, such as motomedialink, which needs to have accessibility permission to work
miss said:
with any apk file, any application?
I use many that are not from any official store, such as motomedialink, which needs to have accessibility permission to work
Click to expand...
Click to collapse
As long as the accessibility permission has been restricted for that app because of the new policy (applies to Notification Access permission as well), it should work.
So far the update to A13 seems to have gone smoothly. I honestly haven't noticed anything different yet.
For what it's worth, one benefit I've noticed so far is that certain applications don't get shut down so aggressively as under A12. Despite all the tweaks I made previously, Angry Birds 2 would get shut down pretty much as soon as I did anything else on the phone, and Sound Profile would shut down randomly. Both of these seem fixed under A13.
Haven't noticed a downside yet in terms of how I use the phone.
I've been on A13 for two weeks now and everything seems to run smoothly, definitely dropped phone temperatures. I don't use wireless charging so can't tell about that. I'm on 13.0.0 (TP1A.220624.021.A1, Aug 2022) rooted. Tried loading 13.0.0 (TP1A.220905.004.A2, Sep 2022) but it won't boot, I'm getting "your device is corrupt it can't be trusted and may not work properly" error, had to revert back to previous one. Shame as I'm struggling with biometrics and this new update was suppose to fix the issue. Might try to flash_all with -w option this weekend to see if it makes any difference, can't be asked to be setting up my phone from scratch after three days of festival