I was wondering what bloat-ware can we remove? I set the phone up now, and the last thing for me to do is delete the bloat...
Are you rooted? Are you taking about disable or completely remove?
sent from LenoMoto X
I am and unlocked. I want to delete the stock junk. But I don't know what's safe h to delete
Be careful about deleting files. You may want to just freeze any system apps you are thinking about deleting. That way you can unfreeze them for taking future updates.
We will retain root and unlocked BL when we update from 4.4 right
mroneeyedboh said:
We will retain root and unlocked BL when we update from 4.4 right
Click to expand...
Click to collapse
Yes.. may need to flash twrp again but should be easy..
Related
Hi guys, need some clarification please
Have had my M7 for a few weeks now. I unlocked the bootloader and 'perm rooted' using the toolkit. It still has the stock rom on it.
I am trying to remove the root but I have read conflicting information.
1. I have managed to relock the bootloader (shows RELOCKED and TAMPERED) so does this mean I cannot put a stock ROM back on to unroot it? Do I need to unlock it, put on stock ROM and then relock it?
2. I looked at Mike1986's stock ROM but it has issues with installing paid apps. So, is there any other ROM I can use to return to stock?
I think that's why people don't like unlocking because you can't get rid relocked
I don't mind the fact that it says 'relocked' (have unlocked it again) but want to remove root if possible
bob 6600 said:
I don't mind the fact that it says 'relocked' (have unlocked it again) but want to remove root if possible
Click to expand...
Click to collapse
You will have superuser on your phone in the settings it will say unroot after that uninstall superuser all done
I guess it's an issue of warranty. If it says 'Relocked', is it still void? I didn't know this to be an issue until I saw it, guess I was spoiled with the Gnex lines.
jaythenut said:
You will have superuser on your phone in the settings it will say unroot after that uninstall superuser all done
Click to expand...
Click to collapse
Tried that - pressed unroot, it closed and removed the app but it is still rooted
You sure you will still be unlocked get a root checker app and see
I am also facing the same problem. Tried the uninstall on supersu but after rebooting the phone, supersu is still there.
jaythenut said:
You sure you will still be unlocked get a root checker app and see
Click to expand...
Click to collapse
Yep, Tibackup and LP still have root access and SuperSU is back on reboot
if I have already upgraded to kit kat 4.4.2? I take it that since the 4.4.2 OTA hasn't been pushed for my Verizon Dev Ed device, that the factory images I have been given by Motorola are for 4.4.
But once the 4.4.2 OTA is pushed, the factory images I have now would be out of date because those are for 4.4., right? Then will Motorola release 4.4.2 factory images later?
Also, what does it mean when in bootloader mode it says Device is UNLOCKED. Status Code: 3. What is the status code 3?
Cozume said:
if I have already upgraded to kit kat 4.4.2? I take it that since the 4.4.2 OTA hasn't been pushed for my Verizon Dev Ed device, that the factory images I have been given by Motorola are for 4.4.
But once the 4.4.2 OTA is pushed, the factory images I have now would be out of date because those are for 4.4., right? Then will Motorola release 4.4.2 factory images later?
I have a verizon unlocked dev ed. Also, what does it mean when in bootloader mode it says Devide is UNLOCKED. Status Code: 3. What is the status code 3?
Click to expand...
Click to collapse
It gives you the stock recovery, the stock system image with all the applications, and the ability to update over the air (OTA). People re-flash the factory images either when they think they messed up their phone, or when they want the latest update via OTA instead of waiting for a SBF package. In short, it returns the phone to the default/non modded status.
I am fairly certain that a SBF will be made for 4.4.2, it just is taking a bit longer this time, maybe they are busy, especially since there is no new updates around the corner any time soon. Since you have already updated to 4.4.2 (like myself) there is no way to go back to stock unless you have made a recovery image in TWRP/CWM. Then all you have to do to update, is reflash the stock recovery image and then you can take a system OTA.
The bootloader on this phone cannot be downgraded, due to the eFuse system incorporated into it. If you attempt to load a lower bootloader in RSD Lite, it will simply fail to install and nothing else bad will happen, however, if you force the bootloader overwrite then you have a nice new paperweight (aka hard brick), because this trips the eFuse.
Status code 3 is basically the computer flag telling the future firmware updates that your bootloader has already been unlocked, so if you update using that same carrier/firmware, you don't lose your unlocked bootloader status. Another reason why you need to simply stick with your own firmware. As there have been reports that loading another regions/phones firmware can lock your bootloader again because the flag isn't there.
mastarifla said:
In short, it returns the phone to the default/non modded status.
Click to expand...
Click to collapse
It restores everything I modded? I erased the clogo.bin file and then I think I flashed with some other bin file to clogo and of course, didn't save a backup. Now I can't get the Kit Kat easter egg when I tap the build version so clearly it has something to do with the clogo file I messed with. I can live without the easter egg, but I don't want to brick my device. So I guess I should just flash the factory images and see what happens.
mastarifla said:
The bootloader on this phone cannot be downgraded, due to the eFuse system incorporated into it. If you attempt to load a lower bootloader in RSD Lite, it will simply fail to install and nothing else bad will happen, however, if you force the bootloader overwrite then you have a nice new paperweight (aka hard brick), because this trips the eFuse.
Click to expand...
Click to collapse
and even if your bootloader is unlocked, you have a hard brick and there is no way to correct that?
mastarifla said:
Status code 3 is basically the computer flag telling the future firmware updates that your bootloader has already been unlocked, so if you update using that same carrier/firmware, you don't lose your unlocked bootloader status. Another reason why you need to simply stick with your own firmware. As there have been reports that loading another regions/phones firmware can lock your bootloader again because the flag isn't there.
Click to expand...
Click to collapse
If my bootloader were to ever get locked again, can't I use the same 20 digit unlock key that Motorola emailed me to unlock it?
Many thanks again, and sorry I cannot hit the thanks button until tomorrow!
Cozume said:
It restores everything I modded? I erased the clogo.bin file and then I think I flashed with some other bin file to clogo and of course, didn't save a backup. Now I can't get the Kit Kat easter egg when I tap the build version so clearly it has something to do with the clogo file I messed with. I can live without the easter egg, but I don't want to brick my device. So I guess I should just flash the factory images and see what happens.
Click to expand...
Click to collapse
If you are already on 4.4.2 then you can flash the 4.4.2 "factory image" when it is released and it should be fine/back to normal.
Cozume said:
and even if your bootloader is unlocked, you have a hard brick and there is no way to correct that?
Click to expand...
Click to collapse
Correct, all the phones have the same eFuse system, even the developer phones. This "supposedly" prevents people from screwing up their phones more. (Personally I think it's silly, but I also have a Nexus, so it doesn't bother me).
Cozume said:
If my bootloader were to ever get locked again, can't I use the same 20 digit unlock key that Motorola emailed me to unlock it?
Many thanks again, and sorry I cannot hit the thanks button until tomorrow!
Click to expand...
Click to collapse
You should be able to (if you still have your IMEI), however there are reports that some people are losing their IMEI too, if this gets lost and there is no way to recover it then you are out of luck, because in order to unlock the bootloader it has to verify that the code works for your IMEI (which is carrier specific).
mastarifla said:
Correct, all the phones have the same eFuse system, even the developer phones. This "supposedly" prevents people from screwing up their phones more. (Personally I think it's silly, but I also have a Nexus, so it doesn't bother me).
Click to expand...
Click to collapse
It seems like the eFuse is the cause of people screwing up their phones. I suppose they do these sorts of things to satisfy potential corporate customers who want secure devices for their corporate communications.
mastarifla said:
You should be able to (if you still have your IMEI), however there are reports that some people are losing their IMEI too, if this gets lost and there is no way to recover it then you are out of luck, because in order to unlock the bootloader it has to verify that the code works for your IMEI (which is carrier specific).
Click to expand...
Click to collapse
Wow, that is awful but can't an IMEI be restored somehow if you know what it is? I not only have my box, Verizon has all my IMEI's stored on their system.
Cozume said:
It seems like the eFuse is the cause of people screwing up their phones. I suppose they do these sorts of things to satisfy potential corporate customers who want secure devices for their corporate communications.
Click to expand...
Click to collapse
Sadly corporate security is much less of a concern to them and actually something else entirely (see Samsung's encryption protocol for enterprise - SAFE). Motorola doesn't want to bother with supporting people on lower firmwares, and this prevents them from having to worry about it because they will always require you to be on the latest firmware for support, this eFuse system basically prevents people from using exploits in previous versions of the system (aka getting root on a non-unlocked phone, etc).
Cozume said:
Wow, that is awful but can't an IMEI be restored somehow if you know what it is? I not only have my box, Verizon has all my IMEI's stored on their system.
Click to expand...
Click to collapse
If you have your EFS files backed up then you are okay, you can just restore it and you are good to go again. However, the IMEI is a secure file, so you cant make a new one if its gone (nor can your cell company), this system in effect prevents people stealing phones and changing the IMEI in order to not be blacklisted. This system is in place for a very good reason, while not perfect (try selling a used phone to someone who understands this), its the best deterrent against theft currently available.
mastarifla said:
If you have your ESF files backed up then you are okay, you can just restore it and you are good to go again.
Click to expand...
Click to collapse
If I do a nandroid backup does it back those files up? if not, what can I use to back them up?
Also, I will have to come back tomorrow and the next day to hit the thanks button because I will use up all my thanks again tomorrow on you, lol!
Cozume said:
If I do a nandroid backup does it back those files up? if not, what can I use to back them up?
Also, I will have to come back tomorrow and the next day to hit the thanks button because I will use up all my thanks again tomorrow on you, lol!
Click to expand...
Click to collapse
There are tools available to backup your EFS partition in case a nandroid doesn't work correctly. Some CWM/TWRP versions do EFS partition backups, some don't, be sure to read through the threads and make sure. Asking a question goes a long way.
I just want to root my HTC Desire 510 in order to use Xmod game assistant and just to delete bloatware. I tried using kingoroot, it said success, but it actually didn't even work. I found out that you need to unlock the bootloader. I don't really want to this, i have no interest in it. I was thinking of using Kingoroot's HTC bootloader unlock to unlock it, then root it using the kingoroot rooter, then re-lock the bootloader with the Kingoroot bootloader program. Is it risky? Please note my phone has no important data, it's new. And I do not want to install anything custom. Just get xmod and remove bloatware. That's all I need.
Would this all work? Please help.
uRager said:
I just want to root my HTC Desire 510 in order to use Xmod game assistant and just to delete bloatware. I tried using kingoroot, it said success, but it actually didn't even work. I found out that you need to unlock the bootloader. I don't really want to this, i have no interest in it. I was thinking of using Kingoroot's HTC bootloader unlock to unlock it, then root it using the kingoroot rooter, then re-lock the bootloader with the Kingoroot bootloader program. Is it risky? Please note my phone has no important data, it's new. And I do not want to install anything custom. Just get xmod and remove bloatware. That's all I need.
Would this all work? Please help.
Click to expand...
Click to collapse
No this won't work and the number one reason is because if you root the phone and then spend your time deleting all the bloatware you'll be wasting your time if you don't install a kernel with write protection removed because as soon as you reboot the phone will reinstall everything! So you need to unlock the bootloader and then install the custom recovery and then make a backup first before doing anything else and then install the kernel with write protection removed and then delete bloatware!
Ok, I decided I don't want to remove bloatware. I am just rooting so I can download Xmodgames and such apps that need a rooted device. No custom ROMS or anything. Would I be fine?
uRager said:
Ok, I decided I don't want to remove bloatware. I am just rooting so I can download Xmodgames and such apps that need a rooted device. No custom ROMS or anything. Would I be fine?
Click to expand...
Click to collapse
Yes. Although be warned rooting will restore the phone to stock after unlocking the bootloader.
Can you even use the phone if you make changes? What I mean is isn't the point behind a locked bootloader to keep changes from being made? So if you unlock -> make a change (rooting for example) -> then relock .... doesn't that equal bootloop when the bootloader notices you've changed something?
For my two cents... I'm probably more of a noob than you @uRager, and I got through the unlocking and rooting process with not too much trouble. I think the good old fashioned way will probably serve you the best. And there are several kernels that are just a modified version of the stock kernel (write protection removed) so a couple more minutes will get the bloat removed as well. Also don't be afraid to ask questions, from what Ive seen they usually get answered.
Hey guys it's it still worth it to root right now if we're already on pie? And if I unlock my bootloader will I still get software updates
jmcandrews83 said:
Hey guys it's it still worth it to root right now if we're already on pie? And if I unlock my bootloader will I still get software updates
Click to expand...
Click to collapse
Unroot only if you have an app that needs it or you want to remove unused apps completely from your system folder. Otherwise there is no point. You will still get updates with an unlocked bootloader.
ptn107 said:
Unroot only if you have an app that needs it or you want to remove unused apps completely from your system folder. Otherwise there is no point. You will still get updates with an unlocked bootloader.
Click to expand...
Click to collapse
Cool thanks for the feedback ?
I'm just wondering if it's possible to like...
Unlock bootloader then restores your Titanium backup apps and then relock.. or no?
Because as far as I know there's no twrp that can read the encrypted memory and MIUI automatically encrypts the system right?
So basically there's no way to install Magisk ..
If anyone know if it's possible let me know please
I don't understand your question.
I have unlocked my Mi9, installed TWRP,deleted DATA partition, flashed xiaomi.eu,flashed magisk than restored a titanium backup taken from my old phone simply by transfer the folder with pc....
And I don't understand why people wanna relock bootloader!? In most cases you brick your phone, because it's not stock.
Guys I mean with stock global ROM not with xiaomi.eu or any other none official ROM.
I wanna lock bootloader in case my device gets stolen, lost etc.
You never know on which hands it can end.
Relock bootloader only if you flash the stock untouched image. It'useless to have a rooted locked device.... And you may cause a brick.
Yeah as we said... Don't do it if you rooted your device or flashed TWRP or anything. Relock only if it's totally stock. You may risk to brick your phone otherwise.
I was asking if it's possible to root only to being able to restore titanium apps, then remove root and then somehow restore default boot img and re lock bootloader.
PriPhaze said:
I was asking if it's possible to root only to being able to restore titanium apps, then remove root and then somehow restore default boot img and re lock bootloader.
Click to expand...
Click to collapse
I wouldn't try that. It's maybe possible but it's also possible to brick phone while there is something more changed after root and twrp. I don't know I'm not a Dev.
PriPhaze said:
I was asking if it's possible to root only to being able to restore titanium apps, then remove root and then somehow restore default boot img and re lock bootloader.
Click to expand...
Click to collapse
I think you will mess the storage due to encription....