I have a Sprint device, rooted, bootloader is unlocked with s-off and unsecured kernel. I am not really wanting to flash a new Rom quite yet, so I'm stock.
I cannot get root explorer to fully remove bloatware. It all returns after reboot.
Is there an easy way to get it working properly or am I going to have to pull the unwanted files using adb?
TiBa?
sent from my humongous VZW HTC ONE MAX
I dont understand why root explorer wont work. Ive used it many times. If you actually delete something, its not magically reappearing.
Oh but it is magically reappearing. I've removed bloatware at least 6 times and as soon as I reboot it's all back
Sent from my HTC0P3P7 using Tapatalk
I remember reading at some point that they lock stock Roms somehow, and the r/w option doesn't do any good.
I've tried searching, but any combination of words pulls way to many threads.
I've never had this problem before, I've always gone with a custom Rom immediately after purchase.
Believe you have to flash the unsecure kernel to get system to allow changes.
I hoped that would work, but it didn't help. I was reading the one forums, they made an app that enables it on that phone. I tried it, didn't work.
https://play.google.com/store/apps/details?id=me.timos.htconerw
I'm guessing this is also why my damn ad blocker has been making me angry as well.
You do have your bootloader unlocked using scotty1223 method in general *or htcdev* right?
*EDIT: Verify busybox is installed and working properly
I finally got it off of mine by using custom kernel and going s-off then using es file explorer mounted to the root/system on half and titanium backup on the rest. Titanium backup is easier especially if you want to make backups of them all. I personally didn't so I just deleted them all but of course I made a nandroid backup before doing all of this just in case something went awry.
Sent from my HTC0P3P7 using xda app-developers app
You have to flash insecure kernel s off busybox
Related
My ATT HTC One is unlocked and rooted already with CWM no-touch installed.
I installed ES File explorer as well as Titanium Backup Pro and gave both root privileges when they asked for them via Super SU
I can "Uninstall", via titanium backup, all the bloatware apps but when I reboot they come back.
Similarly, through ES File explorer I run the root explorer section and choose to uninstall system apps. I then successfully remove the bloatware, but it again comes back upon reboot.
Are there any other methods I can try or any successful bloatware removals for the One from anybody here? Is it a matter, as another thread about the Incredible suggested, a matter of the kernel not allowing writes to the /system while running? If so, how do I remove bloatware from Recovery?
Thanks!
Q&A there is another thread about the same thing
Ah, thanks. Will head there! Deleting thread in a bit then.
Need a kernel which over rides this. Is an HTC code that they added to kernel.
Sent from my HTC One using xda premium
Fidelio_o said:
Need a kernel which over rides this. Is an HTC code that they added to kernel.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Gotcha, makes sense. Thank you!
Is it possible to root the Fascinate without deleting data, or at least a temporary root?
Chase716 said:
Is it possible to root the Fascinate without deleting data, or at least a temporary root?
Click to expand...
Click to collapse
Absolutely. You'd have to search/dig through older posts, but the general idea is this:
> Get a recovery .zip file that will install Superuser and put it onto the SDCARD
> Flash a custom recovery (typically ClockworkMod) using ODIN
> Reboot into recovery and install the .zip file
Basically for the Fascinate, all you really need to do is get the proper version of the Superuser application and it's corresponding su binary installed. The Samsung ODIN tool allows you to replace the stock recovery with a custom one, and that custom recovery will allow you to install Superuser/root the device. This only modifies the SYSTEM volume and does not affect any of your data at all. It's obviously more complicated, but essentially behaves as if you could just root by installing something from the Google Play Store.
There should be a TON of resources/threads out here and on other sites with how to actually accomplish this and provide the necessary files for the Fascinate, but as long as you pick a process that generally has the steps listed above, your data *should* be 100% safe.
... so get Googling and root that thing! lol :victory:
djp952 said:
Absolutely. You'd have to search/dig through older posts, but the general idea is this:
> Get a recovery .zip file that will install Superuser and put it onto the SDCARD
> Flash a custom recovery (typically ClockworkMod) using ODIN
> Reboot into recovery and install the .zip file
Basically for the Fascinate, all you really need to do is get the proper version of the Superuser application and it's corresponding su binary installed. The Samsung ODIN tool allows you to replace the stock recovery with a custom one, and that custom recovery will allow you to install Superuser/root the device. This only modifies the SYSTEM volume and does not affect any of your data at all. It's obviously more complicated, but essentially behaves as if you could just root by installing something from the Google Play Store.
There should be a TON of resources/threads out here and on other sites with how to actually accomplish this and provide the necessary files for the Fascinate, but as long as you pick a process that generally has the steps listed above, your data *should* be 100% safe.
... so get Googling and root that thing! lol :victory:
Click to expand...
Click to collapse
Well the only thing is, that I'm not supposed to root it, and I only want a temporary root to remove bloatware. Superoneclick's shell root didn't work, and neither did z4root.
Chase716 said:
Well the only thing is, that I'm not supposed to root it, and I only want a temporary root to remove bloatware. Superoneclick's shell root didn't work, and neither did z4root.
Click to expand...
Click to collapse
Well if you get more interested I suggest you try a 4.2.2 ROM you won't be disappointed
Sent from my SCH-I500 using Tapatalk 2
bbrad said:
Well if you get more interested I suggest you try a 4.2.2 ROM you won't be disappointed
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
Well that does sound really nice, especially since i enjoyed CyanogenMod on my Incredible 2, but I can not flash any ROMs, I cannot completely root, and I cannot even flash a new recovery. And if I did flash a ROM, I think it would have to be manually activated since it does not have a SIM Card, leading him to find out I rooted. I just want a temp root to remove the bloatware I do not use.
Chase716 said:
Well that does sound really nice, especially since i enjoyed CyanogenMod on my Incredible 2, but I can not flash any ROMs, I cannot completely root, and I cannot even flash a new recovery. And if I did flash a ROM, I think it would have to be manually activated since it does not have a SIM Card, leading him to find out I rooted. I just want a temp root to remove the bloatware I do not use.
Click to expand...
Click to collapse
I don't think there are any temp-root solutions out there for the Gingerbread Fascinate, as the community was well beyond using exploits by that time Could be wrong, but I looked around and didn't really find anything. It might be worth looking around for a generic Linux 2.6.35-based exploit that somebody has compiled for the ARM processor.
Question ... what would prevent you from temporarily flashing a custom recovery to make the edits you want? If you don't change anything else, it would be overwritten with the stock recovery on the next boot, thus covering your tracks (and we can get the stock recovery back on there for ya if for some reason it doesn't). Many (most?) recoveries will allow ADB access when active, so you can mount system and do what you need to do without actually rooting the stock ROM.
Also, don't worry too much about the CDMA activation status, unless you check a certain box in the Samsung ODIN tool there is almost no way to screw that information up doing what you're looking to do. The CDMA keys are stored in a super double secret location that you ordinarily can't get to. The option is called "EFS Clear", don't go anywhere near it.
If you do find a solution that fits your needs, I also recommend you have a plan to restore the SYSTEM volume back to stock in case you make a mistake, like deleting a critical file. We can help with that as well if you are ultimately willing to use the ODIN tool. I just want to make sure you're prepared for that possibility as it sounds like if you temporarily break this device you'll be in big trouble
djp952 said:
If you do find a solution that fits your needs, I also recommend you have a plan to restore the SYSTEM volume back to stock in case you make a mistake, like deleting a critical file. We can help with that as well if you are ultimately willing to use the ODIN tool. I just want to make sure you're prepared for that possibility as it sounds like if you temporarily break this device you'll be in big trouble
Click to expand...
Click to collapse
Yeah, but two more things: first, can someone give me a very detailed tutorial on ODIN for my device, and could someone also give me the files i may need in order to delete the bloatware, no flashing, no data wipes or anything like that? Because the bloatware is what I think slows my phone down. And what if something does not go right?
Sent from my Galaxy S Fascinate SCH-I500
You should be able to unroot via SuperOneClick after you've fully rooted and debloated the thing. Whoever's keeping an eye on that Fassy hopefully won't notice!
Chase716 said:
Yeah, but two more things: first, can someone give me a very detailed tutorial on ODIN for my device, and could someone also give me the files i may need in order to delete the bloatware, no flashing, no data wipes or anything like that? Because the bloatware is what I think slows my phone down. And what if something does not go right?
Sent from my Galaxy S Fascinate SCH-I500
Click to expand...
Click to collapse
Does the person you're hiding this from even know the difference between what GB and JB looks like? What's to say if you have an AOSP or CM-based JB rom that they'd even know it's not stock?
Anyway, if you buy Nova Launcher prime I know you can hide apps from your drawer, so if you wanted to say hide TiBu or Superuser you could do that and throw someone off if they're just taking a quick look at your app drawer. Nova doesn't work on GB though I think, so you might have to look for a different launcher to do that if you want to stay on stock.
For a detailed guide on pretty much anything related to rooting/flashing just check droidstyle's guide here: http://forum.xda-developers.com/showthread.php?t=1238070
For freezing or removing bloat I highly recommend buying Titanium Backup, but there are some free apps that will do that sorta stuff. Titanium will give you way more options down the road though...
Crawshayi said:
Anyway, if you buy Nova Launcher prime I know you can hide apps from your drawer, so if you wanted to say hide TiBu or Superuser you could do that and throw someone off if they're just taking a quick look at your app drawer. Nova doesn't work on GB though I think, so you might have to look for a different launcher to do that if you want to stay on stock.
Click to expand...
Click to collapse
I believe he does, since when I rooted my Incredible 2 he noticed it was completely different and not HTC Sense skinned, and I'd explained to him the Android operating system. And I use ADW EX as my default launcher, only because I can't use the TwLauncher due to lag issues. So I've hidden my bloat apps, but things still stay open in the background.
This might be a long shot, but have you ever tried to explain to him that rooting is actually more secure than having an unrooted phone? Try to get him to understand that with a rooted device you can actually make FULL backups of your device in case anything goes wrong, unlike the half-assed backups that non-rooted devices have to use. Also, rooted devices allow you to install the latest (secure) versions of android unlike non-rooted which force you to wait for updates that may never come.
Anyway, if that fails, I would recommend to root and freeze/remove with Titanium
Crawshayi said:
This might be a long shot, but have you ever tried to explain to him that rooting is actually more secure than having an unrooted phone? Try to get him to understand that with a rooted device you can actually make FULL backups of your device in case anything goes wrong, unlike the half-assed backups that non-rooted devices have to use. Also, rooted devices allow you to install the latest (secure) versions of android unlike non-rooted which force you to wait for updates that may never come.
Anyway, if that fails, I would recommend to root and freeze/remove with Titanium
Click to expand...
Click to collapse
I wish. He won't listen, and he'll just say that it's bad, I don't need to root my phone,and that I'll break it, like my old one ( NOT MY FAULT!). That is why I wanted to do it secretly, temporarily, or something like that. I know it's good, and that there are risks. So is there any way I can root (no flashing) and keep it hidden? Also, I went into the bootloader, and saw an option that said update.zip. Would that be useful, to maybe flash the EH09 Fascinate rom?
UPDATE: Thanks for the help everyone, but I'm most likely going to ditch the Fascinate for a Galaxy SIII. So maybe sometime I'll find the time to experiment with ROMS on my Fascinate sometime.
Hello,
I've managed to get my build.prop in a state where I can't update (I assume it's the build prop). I've tried the backups I have, but none of them are working. I'm currently on 4.1.1 and I was hoping someone has backup.
Thanks in advance!
for clarity: Verizon Galaxy Note II 4.1.1 Stock ROM, Stock Recovery, Rooted
The Failing update is update_SCH-I605_LL4_to_MC3 which fails with code 402
Download the stock ROM in Development and pull it from there
Sent from my SCH-I605 using xda app-developers app
Bfitz26 said:
Download the stock ROM in Development and pull it from there
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
I Downloaded the image and extracted it, now I have a "system.img" file which I assume contains the files but what do I do with it? I tried mounting/extracting and nothing worked.
Trevski13 said:
I Downloaded the image and extracted it, now I have a "system.img" file which I assume contains the files but what do I do with it? I tried mounting/extracting and nothing worked.
Click to expand...
Click to collapse
Download the recovery flashable stock rom, the zip file, and extract it from that using 7zip.
Sent from my SCH-I605 using XDA Premium HD app
Trevski13 said:
I Downloaded the image and extracted it, now I have a "system.img" file which I assume contains the files but what do I do with it? I tried mounting/extracting and nothing worked.
Click to expand...
Click to collapse
Using ES File explorer. Setup up your root explorer. and change permissions by using tools to System R/W.
Use ES File explorer to open the stock download and navigate to system/build.prop Copy it. Go back to your system and Rename the one there to build.bak. Then paste the new one there. This way you have the original saved if it turns out not to be the build.prop. My guess is. If you are on a rooted, stock rom like you said. The build.prop's are going to be identical. Thinking the culprit might be whatever you are trying to Odin is bad.
dragonstalker said:
Using ES File explorer. Setup up your root explorer. and change permissions by using tools to System R/W.
Use ES File explorer to open the stock download and navigate to system/build.prop Copy it. Go back to your system and Rename the one there to build.bak. Then paste the new one there. This way you have the original saved if it turns out not to be the build.prop. My guess is. If you are on a rooted, stock rom like you said. The build.prop's are going to be identical. Thinking the culprit might be whatever you are trying to Odin is bad.
Click to expand...
Click to collapse
I didn't know you could explore .img files with a root explorer, of course I have never tried either.
Sent from my SCH-I605 using XDA Premium HD app
So I pulled the build.prop from a stock image, but it turned out it perfectly matched one of my backups. (I had three backups, factory, factory that I played with, and OTA Stock). So in the end that didn't solve my core issue. At this point should I make a new thread with a more appropriate title or just continue this one?
shangrila500 said:
I didn't know you could explore .img files with a root explorer, of course I have never tried either.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
Actually you can't... I ended up using "Android ICS JB EXT4 imagefile unpacker" for windows, which worked nicely.
Trevski13 said:
The Failing update is update_SCH-I605_LL4_to_MC3 which fails with code 402
Click to expand...
Click to collapse
I would say just continue this thread.
I just re-read your original post. Are you trying to update from 4.1.1 to 4.1.2 via the OTA? If so, build.prop isn't your issue.
jcollier said:
I would say just continue this thread.
I just re-read your original post. Are you trying to update from 4.1.1 to 4.1.2 via the OTA? If so, build.prop isn't your issue.
Click to expand...
Click to collapse
alright, detail time!
I'm currently on 4.1.1 (I've applied one update after I bought it on release day)
I have an ota update (to what I assume is 4.1.2)
stock everything, locked boot-loader, but rooted (used Exynos Abuse)
using SuperSU
my phone lists update_SCH-I605_LL4_to_MC3 which fails to install with error code 402
my device status IS "modified" but it appears to be related to the SD card as it is "normal" when I remove it (apparently a known issue)
normally when I get an update I do the following:
1. restore build.prop
2. remove busybox
3. remove/disable any other apps that may have played with files that I think could cause issues
4. double check my root backup (Voodoo)
5. temp unroot
6. update
7. restore root
8. enjoy
this method usually works without issues :/
and the reason I suspected build.prop in the first place is that restoring it allowed me to update on another device.
I'd really rather not have to flash it back to stock, but if it's my only option, I will. So any ideas that don't involve wiping everything would be wonderful!
Trevski13 said:
alright, detail time!
I'm currently on 4.1.1 (I've applied one update after I bought it on release day)
I have an ota update (to what I assume is 4.1.2)
stock everything, locked boot-loader, but rooted (used Exynos Abuse)
using SuperSU
my phone lists update_SCH-I605_LL4_to_MC3 which fails to install with error code 402
my device status IS "modified" but it appears to be related to the SD card as it is "normal" when I remove it (apparently a known issue)
normally when I get an update I do the following:
1. restore build.prop
2. remove busybox
3. remove/disable any other apps that may have played with files that I think could cause issues
4. double check my root backup (Voodoo)
5. temp unroot
6. update
7. restore root
8. enjoy
this method usually works without issues :/
and the reason I suspected build.prop in the first place is that restoring it allowed me to update on another device.
I'd really rather not have to flash it back to stock, but if it's my only option, I will. So any ideas that don't involve wiping everything would be wonderful!
Click to expand...
Click to collapse
Really the only thing I have seen to update is to go completely back to stock.
But why do you want to do this so badly? Why not just unlock and flash the new update rom Beans provided? Thats certainly the easiest way to do it in my opinion, since you're having all these issues, and it leaves you unlocked in case you don't like one of the future updates or if you want to test out AOSP.
Sent from my SCH-I605 using XDA Premium HD app
shangrila500 said:
Really the only thing I have seen to update is to go completely back to stock.
But why do you want to do this so badly? Why not just unlock and flash the new update rom Beans provided? Thats certainly the easiest way to do it in my opinion, since you're having all these issues, and it leaves you unlocked in case you don't like one of the future updates or if you want to test out AOSP.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
I rely on my phone a lot and so even the short amount of time it would take me to fix a soft brick, or reconfigure a wiped device would be a problem. I'm not worried about bricking it, I'm worried about the time it takes to fix it. I soft bricked my old X2, and it was a real inconvenience (granted that was the first time I'd ever had to fix something like that) and I had to restore my Transformer Infinity back to stock to fix lag and glitching issues. (which lead to a whole partial root fiasco). So It's not that I can't fix the problems, it's that it takes time I don't have, and disrupts my life. If I had another 4g phone (because switching between 3g and 4g is a pain on Verizon) that I could switch to if I messed up and didn't have time to fix it, I'd totally start messing with custom roms, unlocking, and all that fun stuff, but I don't
Trevski13 said:
I rely on my phone a lot and so even the short amount of time it would take me to fix a soft brick, or reconfigure a wiped device would be a problem. I'm not worried about bricking it, I'm worried about the time it takes to fix it. I soft bricked my old X2, and it was a real inconvenience (granted that was the first time I'd ever had to fix something like that) and I had to restore my Transformer Infinity back to stock to fix lag and glitching issues. (which lead to a whole partial root fiasco). So It's not that I can't fix the problems, it's that it takes time I don't have, and disrupts my life. If I had another 4g phone (because switching between 3g and 4g is a pain on Verizon) that I could switch to if I messed up and didn't have time to fix it, I'd totally start messing with custom roms, unlocking, and all that fun stuff, but I don't
Click to expand...
Click to collapse
Well unlocking would let you go ahead and update and until you wanted to flash roms you wouldnt have to except for that first flash of the new update, which is what a stock update does.
The reason I say this is some people have had this problem and when they finally do get the update to work it soft bricks them. This is rare but it has happened. In the end for me it is just easier to unlock so I can play around when I want to and when I dont I can stay on stock.
Sent from my SCH-I605 using XDA Premium HD app
I used the thread here to root T-mobile HTC-one. I have been trying to remove several things from the phone Lookout, KidMode and google talk; however I couldn't do any of them. I tried using Titanium backup and no bloat for the removal, but they are still there. Any help appreciated.
Aroha,
I'm new to all this too, but from what I've read here, T-MaBell has it wired to reinstall the bloat when it detects it's gone or something like that.
To get around it, ya gotta flash a new kernel and/or ROM.
TiBa let's you freeze the bloatware so I guess that's the best it can get unless you start getting into deeper water.
Good luck
Sent from my HTC One using xda app-developers app
mghanem8800 said:
I used the thread here to root T-mobile HTC-one. I have been trying to remove several things from the phone Lookout, KidMode and google talk; however I couldn't do any of them. I tried using Titanium backup and no bloat for the removal, but they are still there. Any help appreciated.
Click to expand...
Click to collapse
I had the same problem on myTouch 4G ages ago. Any app that you remove that came with the phone will be reloaded when you reboot your phone. I think it has to do with the stock ROM and the way it set.
You can disable lookout and other crap in Application settings in settings. It will be on your phone but it will be completely idle
for example; once someone decrypts the phone, when i make my rom and host, when u download it, you can actually take anything you want out of the zip, thats what i do when i make a stock not root rom, i make another rom for myself, i remove everything else i dont want, change to boot animation, then i use that for my personal rom..
what you need for your rom, is a kernal with read and write access...
mdiaz33685 said:
for example; once someone decrypts the phone, when i make my rom and host, when u download it, you can actually take anything you want out of the zip, thats what i do when i make a stock not root rom, i make another rom for myself, i remove everything else i dont want, change to boot animation, then i use that for my personal rom..
what you need for your rom, is a kernal with read and write access...
Click to expand...
Click to collapse
Is that what S-Off is for, gives me a write/read access. I will just flash a custom ROM, I think that should take care of it.
mghanem8800 said:
Is that what S-Off is for, gives me a write/read access. I will just flash a custom ROM, I think that should take care of it.
Click to expand...
Click to collapse
All u need is root and a kernel..
Why not just disable it?
Sent from my HTC One using xda app-developers app
---------- Post added at 05:10 AM ---------- Previous post was at 05:04 AM ----------
mdiaz33685 said:
All u need is root and a kernel..
Click to expand...
Click to collapse
Can't seem to edit but...just disable what you don't want and it disappears from your apps. What's the difference other than a tiny amount of storage space?
Sent from my HTC One using xda app-developers app
You can also remove them from the recovery. if you have TWRP you can reboot into recovery and use the file manager to delete them from system/apps The system dir is write protected while the phone is running.
Not sure what happened. But none of the apps I have been using to write to system for various reasons are working. If I try writing to system at all it just shuts off. This has been on three different roms clean flashed. And also restored nandroids of what I was running before the ota. Any help would be appreciated.
Sent from my HTC One
Sounds like read write module is not installed or possibly something in att hboot/firmware/being s-on isnt letting it write to system..not real sure this one...
Not sure either. I think it's AT&T issue... I can r/w from twrp but not while phone is booted. Apps like gsam root companion do not install to priv-app like they are supposed to. I have to manually do it from twrp.
Sent from my HTC One