Is it okay to install the updates Htc sends being rooted? I have an update for the lockscreen and don't know if I should update it or not.
Sent from my PG86100 using XDA App
I got it and no harm done
Sent from my PG86100 using Tapatalk
tomp517 said:
Is it okay to install the updates Htc sends being rooted? I have an update for the lockscreen and don't know if I should update it or not.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
yea, i think there is a lockscreen/few app update should be fine. although these types of updates have been uncommon on my EVO so not sure if these small and narrowly focused OTA updates will be common or not on the EVO 3D. this is the first update of this type i've seen on the evo/evo3d series. it only patches a few applications and doesn't touch the bootloader/hboot/radio/recovery.
as a general warning, most OTAs from HTC, especially larger in size, have the potential to reset root access on the device and lock the user out. keep in mind when running most OTAs, especially larger ones, you do run the risk of losing root access.
if you want to do some investigating yourself, the OTA files are always downloaded to the /cache partition. download the file, but do not install. after the file has been downloaded, adb pull the downloaded .zip from the /cache partition. you can open this .zip up in 7zip/winrar and maybe also winzip. inside the .zip you can see all the pieces it plans on loading and can determine which parts of the phone will be modified, i.e. hboot, radio, kernel, recovery, apps, etc.
hope that helps!
Related
what is this new update and should I except it? I see now..I'm running flipz and its old build....
Sent from my EVO using xda premium
No
darrick913 said:
what is this new update and should I except it?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
If you plan on rooting your phone. DO NOT UPDATE It will change your hboot of the phone. HTC did this to the evo 3d and screwed up the phone. If you want the updates without the changed hboot. Root your phone and the devs have made a flashable zip that has all the good updates and no hboot change.
No do not ota. Download this:
http://d-h.st/elt
Rename it to PJ75IMG.zip
Place it on sdcard - not in any folders, in the main directory
Reboot into bootloader and say yes to update
Rename or remove it from sd card
Hello,
I have a stock rooted ROM from viper that has all of the bloatware an sprint apps on it. I've tried removing the apks from ES file browser, android terminal emulator, and titanium backup uninstall. They are removed from the app drawer but then reappear (and sometimes update) whenever I reboot the phone.
How do I prevent this and remove them permanently?
Also, on an unrelated note, I'm using the OMJ mod pack and hot reboot doesn't work. It reboots to lock screen and then turns off completely. Has anyone found a fix for that too?
g2nightmare said:
Hello,
I have a stock rooted ROM from viper that has all of the bloatware an sprint apps on it. I've tried removing the apks from ES file browser, android terminal emulator, and titanium backup uninstall. They are removed from the app drawer but then reappear (and sometimes update) whenever I reboot the phone.
How do I prevent this and remove them permanently?
Also, on an unrelated note, I'm using the OMJ mod pack and hot reboot doesn't work. It reboots to lock screen and then turns off completely. Has anyone found a fix for that too?
Click to expand...
Click to collapse
This has to do with not being able to make system changes while S-ON after the JellyBean update.
Urgh, I can't post outside links yet. Google this article to read more:
"Bootloader in Jelly Bean update causes huge headaches for rooted, S-ON HTC EVO 4G LTE owners" at Pocketables
A few options:
You could install MeanBean which has a fix to allow S-ON users to make system changes so that your uninstalls will persist.
Or you could check out App Quarantine ROOT/FREEZE, which you can use to freeze apps. I used this before MeanBean had the system changes fix and I didn't have any problems with the changes reverting. Titanium Backup has the option too, but the freeze option is only in the pay version.
Another option that I do personally due to this issue is remove all associated apk and odex files in the zip of the app you don't want in the Rom before transferring it to your sdcard and flashing... Takes a few minutes but ensures the app isn't installed upon bootup...just another option in case its a Rom that doesn't have meanrom's s-on workaround....
Sent from my EVO using xda app-developers app
onefasttreopro said:
Another option that I do personally due to this issue is remove all associated apk and odex files in the zip of the app you don't want in the Rom before transferring it to your sdcard and flashing... Takes a few minutes but ensures the app isn't installed upon bootup...just another option in case its a Rom that doesn't have meanrom's s-on workaround....
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
spursdude said:
This has to do with not being able to make system changes while S-ON after the JellyBean update.
Urgh, I can't post outside links yet. Google this article to read more:
"Bootloader in Jelly Bean update causes huge headaches for rooted, S-ON HTC EVO 4G LTE owners" at Pocketables
A few options:
You could install MeanBean which has a fix to allow S-ON users to make system changes so that your uninstalls will persist.
Or you could check out App Quarantine ROOT/FREEZE, which you can use to freeze apps. I used this before MeanBean had the system changes fix and I didn't have any problems with the changes reverting. Titanium Backup has the option too, but the freeze option is only in the pay version.
Click to expand...
Click to collapse
I'll try these and update you!
onefasttreopro said:
Another option that I do personally due to this issue is remove all associated apk and odex files in the zip of the app you don't want in the Rom before transferring it to your sdcard and flashing... Takes a few minutes but ensures the app isn't installed upon bootup...just another option in case its a Rom that doesn't have meanrom's s-on workaround....
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
This worked perfectly! I deleted the apks while it was still zipped in Winrar and reflashed.
Best option: just get s-off.
Yes it may sound scary, but you will never want to go back to s-on again.
No more flashing kernels before a new Rom, none of that.
Just go to the dirty racun thread and go from there.
Sent from my EVO using Tapatalk 2
bennyboy78 said:
Best option: just get s-off.
Yes it may sound scary, but you will never want to go back to s-on again.
No more flashing kernels before a new Rom, none of that.
Just go to the dirty racun thread and go from there.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
^^^^^^ this and also try RomCleaner
http://forum.xda-developers.com/showthread.php?t=1832162
g2nightmare said:
This worked perfectly! I deleted the apks while it was still zipped in Winrar and reflashed.
Click to expand...
Click to collapse
Glad it worked out...its a bit of a pain knowing the file names for each app but gets the job done...enjoy
Sent from my EVO using xda app-developers app
tried this solution because i becoming a pain in the neck this apps that reinstall, but did not work for me. When i do the reinstall in recovery it tells me looking for update than update aborted..... do not know what to do next to get finally rid of all the garbage, at least what is for me!
I am always low on space on my phone, Sprint EVO 3D ICS. I have been using DiskUsage to free up space when I update apps. DiskUsage shows my "System Data" to be 358MB. When searching I found multiple threads that suggest that I need to root to be able to see what is in the system data folder using all the space. I am ignorant on this part of it. I looked at a few root guides and they seemed very involved and potentially beyond my comfort level. I am not technology stupid, but I do not know anything about Android's file system.
What is the path of least resistance for me to find out what in System Data is using all my space?
Will es file explorer allow to to view without root?
sent from MY BAD A$$ ET4G
Yeah I would use explorer if your not rooted and root explorer if you are rooted
Sent from my PG86100 using xda premium
patrao_n said:
Will es file explorer allow to to view without root?
sent from MY BAD A$$ ET4G
Click to expand...
Click to collapse
I tried using ES File Explorer and it shows nothing in the contents of \data\data so it appears I need root.
Is there any easy way to root the phone to give that ES File Explorer process the correct permissions?
Thanks
Is there anyway to view and delete the files using my PC with the SDK tools?
In order to do anything with the root of the phone, you need to first obtain root permissions, by rooting.
Sent from my PG86100 using xda app-developers app
kiewee3 said:
In order to do anything with the root of the phone, you need to first obtain root permissions, by rooting.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
The root instructions I see say that it will restore the phone to the factory rom, which defies the point of what I am trying to do. I tried the temporary root instructions on the site and all failed. So evidently I have no choice. It sucks that Android is locked down to the point of becoming unusable.
If you are just trying to see what's there use explorer. It will work with non-rooted phones
Sent from my PG86100 using xda premium
Its not all android phone. Htc is the hard one. Moto is worse though. Good luck. I would gain s-off while you are at it. Should you need it one day. Its much easier to gain s-off now then later after having all your data just the way you want it.
Sent from my GT-P5113 using Tapatalk 2
patrao_n said:
Its not all android phone. Htc is the hard one. Moto is worse though. Good luck. I would gain s-off while you are at it. Should you need it one day. Its much easier to gain s-off now then later after having all your data just the way you want it.
Sent from my GT-P5113 using Tapatalk 2
Click to expand...
Click to collapse
I am going to be getting a new phone soon, I am just trying to make this one livable until I can get rid of it. Everything I have tried has failed to get access to the system data directory to find out what is using all the space. It is so very frustrating.
cr0wbar said:
I am going to be getting a new phone soon, I am just trying to make this one livable until I can get rid of it. Everything I have tried has failed to get access to the system data directory to find out what is using all the space. It is so very frustrating.
Click to expand...
Click to collapse
Boot your recovery and "flash" Aroma File Manager 1.80. Once it starts you may have to mount your volumes (select "Automount all devices on start" in settings), but then you should be able to access the contents of the /data directory.
If you don't have a custom recovery installed this isn't going to work but you can HTC unlock and flash a custom recovery without having to root your stock ROM.
ramjet73
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
For those who want to stay on 1.85.605.9 for now. Must be S-0ff, rooted, and custom recovery.....
If you have 1.85.605.9 rooted with custom recovery, Nougat will not be able to install.
But it will still give nags to update and keep trying, over and over again.
If this annoys you, there is a way to stop the update nags in 3 steps.
Install Root Exporer. Go to root/system/etc-security. Set to mount R/W.
Rename otacerts.zip to “otacerts.zip.bak”.
Next, go to root/system/priv-app/HtcOMADM_VZW and rename HtcOMADM_VZW.apk to “HtcOMADM_VZW.apk.bak”.
Finally, go to root/system/priv-app/HtcOMADM_VZW/OAT/ARM
And rename HtcOMADM_VZW.odex to “HtcOMADM_VZW.odex.bak”.
Works so far for me.
Good post, my friend. I'm sure many will benefit from this who aren't happy on the recent nougat update. Removing those applications have always worked best to stop OTA nag IMO. I've also found oddly once you remove the apps that 'Configuration version' will change to 'unknown' in the Settings menu.
Thanks for the info. Can I do this with a file manager Amaze which has root explorer? I tried locating these files but could not find them.
Sent from my HTC6545LVW using XDA-Developers Legacy app
legaldeejay said:
Thanks for the info. Can I do this with a file manager Amaze which has root explorer? I tried locating these files but could not find them.
Sent from my HTC6545LVW using XDA-Developers Legacy app
Click to expand...
Click to collapse
Would try to download free version of Root Explorer. Must be rooted to use it.
Those files are definitely in stock Verizon RUU 1.85.605.9, but may not appear in Viper or other RUU's.
Get into Root, System, and you can navigate to each one by going into the named trees in OP.
Good luck....
I found them. otacerts.zip is located at system/etc/security and the htcOMADM files are at system/priv-app. I presume just renaming them in Amaze should work?
Sent from my HTC6545LVW using XDA-Developers Legacy app
legaldeejay said:
I found them. otacerts.zip is located at system/etc/security and the htcOMADM files are at system/priv-app. I presume just renaming them in Amaze should work?
Sent from my HTC6545LVW using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes, that'll do it. Note AndyBones above (who knows more about HTC roms than I) says he's had luck just deleting those apk's and odex.
I am timid about deletes and after-effects, so I just rename to .bak so I can undo my damage if needed.
Your call.
Freezing HtcDm in TB worked on my end without any issues. Waiting for Xposed to be released for Nougat first before taking the update.