Hi everyone.....so does anyone know a way to remove those stupid stock apps that come with the prime?? and btw I'm NOT rooted.
Thanks
You can 'disable' many of the stock apps with standard apps tool under ICS. To remove system apps you can't disable you need to be rooted.
Stefan662 said:
You can 'disable' many of the stock apps with standard apps tool under ICS. To remove system apps you can't disable you need to be rooted.
Click to expand...
Click to collapse
ok thanks ill check it out....and do u kno a good and safe way to root?? also is there a way to unroot?
If you are on .21 firmware it is not so easy to root.
1. you have to downgrade to .15 (see here). Beware this is not without risk please read the instructions very carefully.
2. root (see here) and protect the root status with 'OTA rootkeeper'.
3. update via OTA to .21 and restore root with OTA Rootkeeper.
Stefan662 said:
If you are on .21 firmware it is not so easy to root.
1. you have to downgrade to .15 (see here). Beware this is not without risk please read the instructions very carefully.
2. root (see here) and protect the root status with 'OTA rootkeeper'.
3. update via OTA to .21 and restore root with OTA Rootkeeper.
Click to expand...
Click to collapse
Thanks for the answer but i disabled the apps from the settings like you said and everything is fine, thanks anyway.
nabil alami said:
Hi everyone.....so does anyone know a way to remove those stupid stock apps that come with the prime?? and btw I'm NOT rooted.
Thanks
Click to expand...
Click to collapse
Be aware if you uninstall stock application you may not be able to receive OTA updates!!
As in software updates???
As the title says, I'm currently rooted and using the original .532 firmware.
What is the simplest way of upgrading to the latest update keeping root intact?
I'm able to update via wi-fi or over the air.
I read somewhere about rootkeeper?
Please could someone advise me on how to do this without wiping data and root.
Thanks xda members.
http://forum.xda-developers.com/showthread.php?t=2502185
natispain said:
http://forum.xda-developers.com/showthread.php?t=2502185
Click to expand...
Click to collapse
Thanks for the link. However, is there not an alternative & quicker method?
A user claims to have updated ota without losing root only by using rootkeeper.
I don´t know, but that method is quick and easy.
You must have the bootloader unlocked, do not have recovery installed, only change the build.prop with rooy explorer (you can try without changing it), keep the root with rootkeeper and update with sony update center.
You can try it with your original 532, I think.
rooted and on original software (condensed from http://forum.xda-developers.com/showthread.php?t=2502185). You do not need unlocked bootloader for this.
1. OTA Rootkeeper - install and protect root
2. Perform OTA to 257
3. Enjoy
If OTA fails
1. TiBu - make full backup of your apps & necessary system apps (wifi locations, SMS, etc)
2. FlashTool - Reinstall 532 FTF
3. Root (vRoot is suspect, but go ahead if you like living dangerously, we all do)
4. OTA Rootkeeper - install and protect root
5. Perform OTA to 257
6. Restore Apps via TiBu
7. Enjoy
* Of course, if you're doing it via OTA failure method, you should make sure all your app config files are exported out and saved (Nova, LightFlow, etc)
hey dude do nothing. do not unlock bootloader or anything else. if you have root just ota thats it no need for a rootkeeper or anything else.
can it be any simple than that???
the duderino said:
hey dude do nothing. do not unlock bootloader or anything else. if you have root just ota thats it no need for a rootkeeper or anything else.
can it be any simple than that???
Click to expand...
Click to collapse
That's what I did last time but root was lost.
I may skip the update and wait for Kitkat 4.4 and root.
I noticed no difference or improvement whatsoever when I had 257.
kanej2006 said:
That's what I did last time but root was lost.
I may skip the update and wait for Kitkat 4.4 and root.
I noticed no difference or improvement whatsoever when I had 257.
Click to expand...
Click to collapse
hmmmm it worked for me tough.
Hi,
I have a UK unbranded xperia z2 and just received notification that there is new firmware.
It says I can download it via wifi without connecting to a PC.
I have previously rooted the device without unlocking the bootloader. I am wondering - if I update the firmware over wifi will I lose root?
If so is rooting it again as easy as it was the first time? I think the first time I used easy rooter app
Thanks
xiphrex said:
Hi,
I have a UK unbranded xperia z2 and just received notification that there is new firmware.
It says I can download it via wifi without connecting to a PC.
I have previously rooted the device without unlocking the bootloader. I am wondering - if I update the firmware over wifi will I lose root?
If so is rooting it again as easy as it was the first time? I think the first time I used easy rooter app
Thanks
Click to expand...
Click to collapse
Yes and Yes, you will loose root but rooting with your favourite root exploit should be identical procedure.
ghostofcain said:
Yes and Yes, you will loose root but rooting with your favourite root exploit should be identical procedure.
Click to expand...
Click to collapse
Thanks.
I just tried OTA update and it said it "could not verify" - after some research seems I have to remove root. But I dont want to have to wipe my phones data.
Is there a way to remove root without wiping data? In superSU, there is a "Full Unroot" option but will this actually remove root so I can update?
Flash the unbranded ftf for 314 UK, via flashtool, specifying no wipe for data and you should be OK although you'll have to reroot afterwards.
xiphrex said:
Thanks.
I just tried OTA update and it said it "could not verify" - after some research seems I have to remove root. But I dont want to have to wipe my phones data.
Is there a way to remove root without wiping data? In superSU, there is a "Full Unroot" option but will this actually remove root so I can update?
Click to expand...
Click to collapse
OTA update generally removes root. But you should be able to root again with the same procedure. The full unroot option in SuperSU does actually what it says and will fully unroot your device allowing you to update the firmware.
Just give it a try.
Hit thanks if it helped
If I take a system update will I lose root? I've blocked updates but was just wondering.
Matt1024 said:
If I take a system update will I lose root? I've blocked updates but was just wondering.
Click to expand...
Click to collapse
Most likely.
Matt1024 said:
If I take a system update will I lose root? I've blocked updates but was just wondering.
Click to expand...
Click to collapse
If you have made any system changes, you will not be able to accept it anyways. It will just fail.
Matt1024 said:
If I take a system update will I lose root? I've blocked updates but was just wondering.
Click to expand...
Click to collapse
Best practice is to wait and see if those that have taken an update are able to Root afterwards, if so then your good!
Personally... I'm just keeping my phone on the 10B firmware until a custom recovery comes. My phone runs great right now.
If for some reason we make it to the Android L update before we get an unlock, then I'm wait and see if it's possible to Root and unlock that prior to updating.
My S4 was on 4.4.4 and really being on 4.4.2 were not missing anything.
- Tapatalked from the G3
Matt1024 said:
If I take a system update will I lose root? I've blocked updates but was just wondering.
Click to expand...
Click to collapse
You would lose root.
It's a toss up of whether you would even be able to take the update.
Depends on how they check the file system. Definitely if you are running Xposed, you won't be able to OTA unless you go back to stock.
Somewhat OT, but I was a bit surprised to see that I kept root after a factory reset (TiBu borked myself into a bootloop). Just re-downloaded and installed SuperSU, and good to go.
As per the title, I read something somewhere to the effect that from here on out, OTA updates will fail on most phones if they have been rooted, and this seems to be true for the Z Ultra GPE. So, what changed when I rooted my phone, and how do I undo it so that I can do the OTA update? I have looked through the forum, but nobody seems to answer it. I am rooted with Supersu using the Towelroot method. I am hoping to not have to unlock the bootloader or anything, just want to do this the official way. (I did backup my TA partition though).
jeraldjunkmail said:
As per the title, I read something somewhere to the effect that from here on out, OTA updates will fail on most phones if they have been rooted, and this seems to be true for the Z Ultra GPE. So, what changed when I rooted my phone, and how do I undo it so that I can do the OTA update? I have looked through the forum, but nobody seems to answer it. I am rooted with Supersu using the Towelroot method. I am hoping to not have to unlock the bootloader or anything, just want to do this the official way. (I did backup my TA partition though).
Click to expand...
Click to collapse
If your GPe is rooted only, the OTA should install just fine. If you made any system changes, you'll need to revert those though. I ran the OTA while I was rooted and didn't have any problems.
Visa Declined said:
If your GPe is rooted only, the OTA should install just fine. If you made any system changes, you'll need to revert those though. I ran the OTA while I was rooted and didn't have any problems.
Click to expand...
Click to collapse
Not so. See:
http://bgr.com/2014/11/14/android-5-0-lollipop-updates-and-root/
As mine is rooted, no dice, the OTA fails. So, how to unroot it so that the update takes?
jeraldjunkmail said:
Not so. See:
http://bgr.com/2014/11/14/android-5-0-lollipop-updates-and-root/
As mine is rooted, no dice, the OTA fails. So, how to unroot it so that the update takes?
Click to expand...
Click to collapse
well at the moment that doesn't effect the GPe, and may never. There will have to be a system image flashed to put the block device in a known state before the new way could ever be used, and if there is a system.img we can always flash that to get the OTA to work... no big deal I don't think.
jeraldjunkmail said:
Not so. See:
http://bgr.com/2014/11/14/android-5-0-lollipop-updates-and-root/
As mine is rooted, no dice, the OTA fails. So, how to unroot it so that the update takes?
Click to expand...
Click to collapse
First of all, BGR is a garbage site, and I wouldn't believe anything they say, ever. Second, that article is talking about avoiding root AFTER Lollipop is installed.
Having root will not cause the OTA to fail. If your OTA is failing, it's because you made a system change on your device.
*edit
If you were using Xposed, then that is more than likely why your OTA is failing.
What is Xposed? How would I check to see if it has affected my device? Only thing I did was Towelroot and running SuperSU. I may have done something to allow writing to the external SD card, but forget how I did that. I was intentionally trying to keep this phone basically stock so that it would easily update to Lolipop. I did a Titanium backup to the externalSD card and reset it to factory and the OTA update still fails though. I assume this was due to the fact that I rooted it. The bootloader is still unmodified, secureboot is still green - yes, lock state is locked. Only other thing I can think of is I installed an app that allowed me to set permissions by app (turn off location settings by app, etc) Sorry I can't give any more details than that...
jeraldjunkmail said:
I may have done something to allow writing to the external SD card, but forget how I did that.
Click to expand...
Click to collapse
jeraldjunkmail said:
Only other thing I can think of is I installed an app that allowed me to set permissions by app (turn off location settings by app, etc) Sorry I can't give any more details than that...
Click to expand...
Click to collapse
If you can't figure out what system change you made to your phone, just factory reset it, and run the OTA again. There was multiple people(me included) that took the OTA successfully, our phones were rooted and SuperSU was installed.
Visa Declined said:
If you can't figure out what system change you made to your phone, just factory reset it, and run the OTA again. There was multiple people(me included) that took the OTA successfully, our phones were rooted and SuperSU was installed.
Click to expand...
Click to collapse
As mentioned before, I factory reset this and wiped the cache from the stock recovery mode. Update won't take, stops shortly after it fails with "system update error". Since my last reset (been done a few times) it won't prompt me to get the OTA update, after my last reset last night. Any help is appreciated. Thanks!
{Damn thing won't work... (*&^&%^$$#}
jeraldjunkmail said:
As mentioned before, I factory reset this and wiped the cache from the stock recovery mode. Update won't take, stops shortly after it fails with "system update error". Since my last reset (been done a few times) it won't prompt me to get the OTA update, after my last reset last night. Any help is appreciated. Thanks!
{Damn thing won't work... (*&^&%^$$#}
Click to expand...
Click to collapse
The only fail-safe way I can see is to:
root
back up TA
unlock BL
hotboot custom kernel with recovery
flash 4.4.2
OTA to 4.4.3
OTA to 4.4.4
root and restore TA if you want a working camera
OTA to 5.0
blueether said:
The only fail-safe way I can see is to:
root
back up TA
unlock BL
hotboot custom kernel with recovery
flash 4.4.2
OTA to 4.4.3
OTA to 4.4.4
root and restore TA if you want a working camera
OTA to 5.0
Click to expand...
Click to collapse
As often happens, I sometimes see a solution I don't care to implement and begin to procrastinate. So, haven't looked at this problem for a while. I may have found the solution to my problems, but want to know if anyone has experience with it before proceeding. I re-installed superSU and went through the options. Buried in the options list is a box that offers "Full unroot, Cleanup for permanent unroot". What happens when I do this? does it just remove superSU or does it restore the phone back to factory status, before it was rooted? Thanks!
PS: @ blueether the solution is fine and I am sure it would work (I was going to go ahead with it until I saw that option in superSU), but have been hesitant to unlock the bootloader, etc, due to my unfamiliarity with hacking Sony products, and only want to do it as a last, final, no other option solution. Thanks for your help!
jeraldjunkmail said:
As often happens, I sometimes see a solution I don't care to implement and begin to procrastinate. So, haven't looked at this problem for a while. I may have found the solution to my problems, but want to know if anyone has experience with it before proceeding. I re-installed superSU and went through the options. Buried in the options list is a box that offers "Full unroot, Cleanup for permanent unroot". What happens when I do this? does it just remove superSU or does it restore the phone back to factory status, before it was rooted? Thanks!
PS: @ blueether the solution is fine and I am sure it would work (I was going to go ahead with it until I saw that option in superSU), but have been hesitant to unlock the bootloader, etc, due to my unfamiliarity with hacking Sony products, and only want to do it as a last, final, no other option solution. Thanks for your help!
Click to expand...
Click to collapse
That's fine and I take no offence at you not wanting to unlock the BL.
I haven't tried the full unroot option in supersu so I'm not sure what the outcome is. One of the other GPe users care to comment?
Well, turns out that the solution to unrooting the phone is to install superSU and than look inthe settings. It will offer you an option to completely uninstall root. It did what it says, and than you can check it with a check root app from the market. It reports that the phone is not rooted. Now the question is, will it pick up the OTA update... No luck with that after a clean factory reset, so not sure what to do next.
2 questions: If I unrooted my phone, and it says it is unrooted, is this true, in the fullest extent? Does towelroot do anything more than adding some permissions ans the superuser file?
If the phone won't pick up the OTA update, why? What went wrong?
Thanks!
jeraldjunkmail said:
Well, turns out that the solution to unrooting the phone is to install superSU and than look inthe settings. It will offer you an option to completely uninstall root. It did what it says, and than you can check it with a check root app from the market. It reports that the phone is not rooted. Now the question is, will it pick up the OTA update... No luck with that after a clean factory reset, so not sure what to do next.
2 questions: If I unrooted my phone, and it says it is unrooted, is this true, in the fullest extent? Does towelroot do anything more than adding some permissions ans the superuser file?
If the phone won't pick up the OTA update, why? What went wrong?
Thanks!
Click to expand...
Click to collapse
It sounds like the OTA is not being pushed at the moment/anymore. You could copy it to there the recovery can see it and manually install it
blueether said:
It sounds like the OTA is not being pushed at the moment/anymore. You could copy it to there the recovery can see it and manually install it
Click to expand...
Click to collapse
Can you point me inthe right direction for instructions on this process? Thanks!
Visa Declined said:
First of all, BGR is a garbage site, and I wouldn't believe anything they say, ever. Second, that article is talking about avoiding root AFTER Lollipop is installed.
Having root will not cause the OTA to fail. If your OTA is failing, it's because you made a system change on your device.
*edit
If you were using Xposed, then that is more than likely why your OTA is failing.
Click to expand...
Click to collapse
Your post is two years ago but i think you can help me,there is a new update for my phone and i am rooted i also have xposed installed so this mean i cannot update my sytem? Do i need to uninstall xposed? Im on stock rom and with TWRP recovery it would be a big help if you reply thanks.