I have busybox installed, I'm rooted, and have custom recovery. Can I just flash stock recovery back and get the ota?
Or do I need to set my phone up as new and take the ota?
Was hoping for the first option.
Thanks
Sent from my HTC One_M8 using XDA Free mobile app
joho5 said:
I have busybox installed, I'm rooted, and have custom recovery. Can I just flash stock recovery back and get the ota?
Or do I need to set my phone up as new and take the ota?
Was hoping for the first option.
Click to expand...
Click to collapse
For OTA, you need stock recovery, and no changes to system apps. Root is okay, and busybox should be, too. But if you removed any system apps, froze them, added system apps, you will either need to restore them to their "stock" condition, or flash a stock ROM.
Unlocked bootloader is okay for OTA as well.
redpoint73 said:
For OTA, you need stock recovery, and no changes to system apps. Root is okay, and busybox should be, too. But if you removed any system apps, froze them, added system apps, you will either need to restore them to their "stock" condition, or flash a stock ROM.
Unlocked bootloader is okay for OTA as well.
Click to expand...
Click to collapse
If I have viper4android installed in system/priv-app will that fail ota? My whole system is stock other than that... It's 90% of why I root... To install Viper.
I want to be able to accept the sense 7 update when it comes though.
Thanks for all your help.
Sent from my HTC One_M8 using XDA Free mobile app
joho5 said:
If I have viper4android installed in system/priv-app will that fail ota?
Click to expand...
Click to collapse
Pretty sure it will fail. Adding apps to /system would constitute a modification. Viper will be wiped out when you OTA anyway, so no reason to leave it in place (only to cause complications).
redpoint73 said:
Pretty sure it will fail. Adding apps to /system would constitute a modification. Viper will be wiped out when you OTA anyway, so no reason to leave it in place (only to cause complications).
Click to expand...
Click to collapse
I don't mind deleting and reinstalling after... Just was wanting to know if that's what I needed to do.
Sent from my HTC One_M8 using XDA Free mobile app
Related
Hello,
I have a new thunderbolt, which is not rooted. What is the best way to get rid of apps such as Blockbuster, v-cast stuff, etc., etc, while keeping the phone stock? Is this even possible?
Sorry for the newb question and thanks for any help
If you don't root, you can't remove them.
yareally said:
If you don't root, you can't remove them.
Click to expand...
Click to collapse
Yep, not possible unless you root. One of the nice things about Gingerbread is you can default to frequently used apps and never see the bloatware.
Sent from my ADR6400L using xda premium
Thanks for the replies
It is possible, of course, to root the phone and not install another ROM, correct? To just leave the OS as it is, and use something like Titanium Backup to delete stuff from there?
daniel178 said:
Thanks for the replies
It is possible, of course, to root the phone and not install another ROM, correct? To just leave the OS as it is, and use something like Titanium Backup to delete stuff from there?
Click to expand...
Click to collapse
ROM does not necessarily mean custom. There are stock ROMs pulled from the updates/leaks that are not modified by anyone. Using one of those would be what you want.
But is it possible not to install/flash anything after rooting? Just leave it as it is?
Use revolutionary method and you can stick with stock rom and be rooted. It'll replace your hboot with a custom one with s-off, then flash clockwork for custom recovery, then install superuser via recovery. Your rom will be complete stock with root then.
Sent from my HTC ThunderBolt using Tapatalk
revolutionary method?
http://revolutionary.io/
Don't use the one click methods, use the adb method or revolutionary method. Adb method will delete your data, revolutionary will let you keep your data, but it takes extra steps to revert to the stock bootloader.
So I just bought a Sprint SIII, and avoided the OTA like any tinkerer would. I flashed CWM, and rooted successfully, but I don't know what to do with the OTA. As this is a shared device, the other user is likely to install the update. Will we lose root after the update? There's been a lot of talk of updates here and all the searching still hasn't gotten me the info I need. Can a fellow get a hand? If it takes root, will OTA root keeper work? Can I just re-do the entire process using the toolkit and the AIO option?
You can't update with the OTA if you're rooted by going into Settings, so you should be okay.
Sent from my SPH-L710 using xda app-developers app
Jamesyboy said:
So I just bought a Sprint SIII, and avoided the OTA like any tinkerer would. I flashed CWM, and rooted successfully, but I don't know what to do with the OTA. As this is a shared device, the other user is likely to install the update. Will we lose root after the update? There's been a lot of talk of updates here and all the searching still hasn't gotten me the info I need. Can a fellow get a hand? If it takes root, will OTA root keeper work? Can I just re-do the entire process using the toolkit and the AIO option?
Click to expand...
Click to collapse
i was on LF9 then rooted it and flashed CWM so yes you can update or just flash this http://forum.xda-developers.com/showthread.php?t=1747560 it will update you to LF9
EDIT: it very well could lose root but yes it can be regained
jamcar said:
i was on LF9 then rooted it and flashed CWM so yes you can update or just flash this http://forum.xda-developers.com/showthread.php?t=1747560 it will update you to LF9
EDIT: it very well could lose root but yes it can be regained
Click to expand...
Click to collapse
So it won't touch CWM
Edit: The notification was there before we rooted, which is why, I imagine we still got it.
Clicked thanky.
Total confusion. So I have to apply the update and reroot in CWM...then the update will rewrite the stock recovery, and I reflash CWM...say, with the toolkit?
Jamesyboy said:
So it won't touch CWM
Edit: The notification was there before we rooted, which is why, I imagine we still got it.
Clicked thanky.
Total confusion. So I have to apply the update and reroot in CWM...then the update will rewrite the stock recovery, and I reflash CWM...say, with the toolkit?
Click to expand...
Click to collapse
Yes pretty much. If you apply the update on the stock rooted ROM you will loose CWM recovery , but you can get it back by using ODIN or the toolbox to guide you through it
Sent from my SPH-L710 using Tapatalk 2
I'm s-off with a custom rom installed. I ran the zip to remove the OTA from this thread, but it did not work (the notification is still present). The update will allegedly force itself onto my phone today. Will this potentially brick my device? Any help would be greatly appreciated.
Use this one http://forum.xda-developers.com/showthread.php?t=2169022
Sent from my HTC6435LVW using Tapatalk 2
You can't take the ota if you have a custom recovery. So don't worry.
And if you are on viper, are you sure it's not the roms ota, as opposed to vzws
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
You can't take the ota if you have a custom recovery. So don't worry.
And if you are on viper, are you sure it's not the roms ota, as opposed to vzws
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
When you say "You can't", do you mean the process will cancel itself and not install anything when it tries to run?
I am on Viper, but I'm not sure if it's their OTA. The persistent notification just says "System update is available, Tap to download the system update". It occurs to me now that the verizon OTA may not even show up outside of the stock ROM (though I'm not sure how that works)
morph2k4 said:
When you say "You can't", do you mean the process will cancel itself and not install anything when it tries to run?
Click to expand...
Click to collapse
Yep, it'll download the ota and boot into recovery and just sit there.
morph2k4 said:
I am on Viper, but I'm not sure if it's their OTA. The persistent notification just says "System update is available, Tap to download the system update". It occurs to me now that the verizon OTA may not even show up outside of the stock ROM (though I'm not sure how that works)
Click to expand...
Click to collapse
tap the notification. There's a good chance it's the Viper ota if you haven't already installed. And the newest viper version has the Verizon ota stuff removed so you don't have to worry.
Sent from my HTC6435LVW using xda app-developers app
What version of Viper are you running? The latest is 1.1.3.
That's Viper's OTA. Verizon's just begins downloading, it doesn't ask you. Definitely accept it. If you're using TWRP recovery it'll install itself. If you're using ClockworkMod recovery you'll need to select the zip from the sdcard once it's downloaded and say yes when it asks to accept the unsigned zip.
If you're running an older version then you'll get a few in a row (as in after you update to 1.1.1, it'll tell you there's an upgrade to 1.1.2 available, etc.). They're only 16MB each and go pretty quick. DON'T WIPE, it's just an update.
Sent from my ADR6425LVW using xda app-developers app
I have an s-off'd custom rom with AmonRa recovery... offered update??
I just want to have it ignore the update.
Apparently, the software doesn't know the
recovery system is not stock ... so it tries
and fails. I wonder if there is a way to extract
the new fingerprint to trick the update process
into thinking the updates already applied?
Or is there a way to just suppress it all together?
Well I'm pretty much chicken so I'm basically stock but rooted but the ota update keeps falling. I tried unrooting so the update could work but it still failed. Not sure why...
Sent from my ADR6425LVW using xda app-developers app
Same here
I am having the same issue, as well. Rooted, debloated stock sense. Recovery is Amon-Ra.
So I read another thread that made it seem like I needed to re-lock the bootloader so I did that and now when I try to update it goes into the bootloader menu instead of starting the update. Do I need to unroot or do another step for this to work?
Sent from my ADR6425LVW using xda app-developers app
Did you debloat at all? I was stock+root (no debloating) and the install went fine.
Sent from my ADR6425LVW using xda premium
Well, when the ota update downloads and you press the button to update, the updater immediately begins to check the system utilizing a checksum system for any modification, such as a deodexed system/app folder or binaries that weren't originally present. It wants to make sure all system/apps are still there and untouched and all the binaries are still kosher. If it detects something is "off" it will usually abort. If everything checks out it will boot to bootloader and attempt to install the update in the stock recovery. It will fail here of course if a custom recovery is installed.
You can kill your phone from even attempting to check for any otas by using Root Explorer or something similar, go to system/app and add bak to the end of each of these files:
HtcCOTAClient.apk
HtcCOTAClient.odex
You want them to look like:
HtcCOTAClient.apkbak
HtcCOTAClient.odexbak
You could also remove them.
I have an s-off'd custom rom with AmonRa recovery... offered update??
wildstang83 said:
Well, when the ota update downloads and you press the button to update,
the updater immediately begins to check the system utilizing a checksum system for any modification,
such as a deodexed system/app folder or binaries that weren't originally present. It wants to make sure
all system/apps are still there and untouched and all the binaries are still kosher. If it detects something
is "off" it will usually abort. If everything checks out it will boot to bootloader and attempt to install the
update in the stock recovery. It will fail here of course if a custom recovery is installed.
You can kill your phone from even attempting to check for any otas by using
Root Explorer or something similar, go to system/app and add bak to the en
d of each of these files:
HtcCOTAClient.apk
HtcCOTAClient.odex
You want them to look like:
HtcCOTAClient.apkbak
HtcCOTAClient.odexbak
You could also remove them.
Click to expand...
Click to collapse
I froze that with TiBu but it still shows up
as a pending update.
Experimenting, I tried freezing HtcDM
apk and service and the notices went away.
Is that safe to leave DM frozen, (what else does it do)?
My intent is to just prevent this a future OTA
updates auto-installing while I asleep. i woke
to find myself looking at a failed attempt
and hung in AmonRA, I rebooted to normal
and everything runs as normal.
fuzzynco said:
I froze that with TiBu but it still shows up
as a pending update.
Experimenting, I tried freezing HtcDM
apk and service and the notices went away.
Is that safe to leave DM frozen, (what else does it do)?
My intent is to just prevent this a future OTA
updates auto-installing while I asleep. i woke
to find myself looking at a failed attempt
and hung in AmonRA, I rebooted to normal
and everything runs as normal.
Click to expand...
Click to collapse
Not to be a PIA, but why freeze if you can just add bak to the end of the file name and you will achieve the same thing? If you ever want to go back you just delete the bak?
So for me it sounds like I need to get back to a stock recovery to be able to successfully perform the update?
Sent from my ADR6425LVW using xda app-developers app
Gee thanx for the help people...
Sent from my ADR6425LVW using xda app-developers app
You must be on the stock recovery to take an OTA. The stock recovery performs the update. So flash the stock recovery and then do the update or deal with no update.
Is there a way to flash the stock recovery without it wiping my phone?
Sent from my ADR6425LVW using xda app-developers app
Unless you're running a completely stock rom (with nothing removed), you won't be able to install the update anyway...
If you want to stop it from trying to come down, delete or rename /system/etc/security/otacerts.zip.
As for re-installing the stock recovery, you probably would need to RUU your phone unless it's s-off.
So if I do a back up, then go back to stock recovery which will wipe my phone, then perform the ota update, will a restore revert the ruu back and I'm back to square one, or does the ruu not roll back?
Sent from my ADR6425LVW using xda app-developers app
fivedezs said:
So if I do a back up, then go back to stock recovery which will wipe my phone, then perform the ota update, will a restore revert the ruu back and I'm back to square one, or does the ruu not roll back?
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
If you are on a stock rom you should be able to flash the stock recovery from fastboot without wiping the phone. Just find the recovery.IMG from the 605.12 ruu and flash it in fast boot to your phone. Then take the update and when complete flash your custom recovery in fast boot again and flash su zip.
Sent from my Nexus 7 using Tapatalk HD
fivedezs said:
So if I do a back up, then go back to stock recovery which will wipe my phone, then perform the ota update, will a restore revert the ruu back and I'm back to square one, or does the ruu not roll back?
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
A restore would not overwrite any of the firmware on the phone, just the rom.
As dottat pointed out, you can download the latest RUU, extract the recovery image from it and flash that via fastboot. I'd still back up your rom with your custom recovery first in case the rom pieces in the update bork something...
Can anyone point me in the direction of where I can find the stock ruu?
Sent from my ADR6425LVW using xda app-developers app
fivedezs said:
Can anyone point me in the direction of where I can find the stock ruu?
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Check androidpolice.com, it's over there, should be able to search for it...
Need a copy of the stock recovery
I am S-On and unlocked. I need to reflash the stock recovery to apply the OTA firmware update, right? I cannot find a copy of it anywhere. Anyone know where I can get this? I downloaded the stock RUU and tried to pull it out, but I cannot unzip the file. I would be grateful for any help. Thanks.
Hi well this is my second DNA trying to root destroyed the first one lol... Well anyways the first one I downloaded supersu and busybox and figured out it didn't work and I ruined it now.... This is my second phone I have flashed the superuser and binaries. I am figuring out that I have root but its not working correctly.. mostly my changes that I need root for are not lasting through reboot I'm not losing root but I'm losing my changes as in when I delete amazon its gone but when I reboot its back. my only assumption is that its because busybox is missing can anyone confirm this and is there any possible way where I can just get the busybox zip... I have been on the busybox.net website and seen the downloads but I would like confirmation before u destroy this phone to which I hope don't not happen.
Unless you have s-off or have flashed a new kernel, the system partition is right protected, even when you think it isn't. I think that is what is causing your problem.
Why don't you flash a room that already had root/busybix installed?
c2a5nn1o4n said:
Hi well this is my second DNA trying to root destroyed the first one lol... Well anyways the first one I downloaded supersu and busybox and figured out it didn't work and I ruined it now.... This is my second phone I have flashed the superuser and binaries. I am figuring out that I have root but its not working correctly.. mostly my changes that I need root for are not lasting through reboot I'm not losing root but I'm losing my changes as in when I delete amazon its gone but when I reboot its back. my only assumption is that its because busybox is missing can anyone confirm this and is there any possible way where I can just get the busybox zip... I have been on the busybox.net website and seen the downloads but I would like confirmation before u destroy this phone to which I hope don't not happen.
Click to expand...
Click to collapse
Sent from my HTC6435LVW using Tapatalk 2
c2a5nn1o4n said:
Hi well this is my second DNA trying to root destroyed the first one lol... Well anyways the first one I downloaded supersu and busybox and figured out it didn't work and I ruined it now.... This is my second phone I have flashed the superuser and binaries. I am figuring out that I have root but its not working correctly.. mostly my changes that I need root for are not lasting through reboot I'm not losing root but I'm losing my changes as in when I delete amazon its gone but when I reboot its back. my only assumption is that its because busybox is missing can anyone confirm this and is there any possible way where I can just get the busybox zip... I have been on the busybox.net website and seen the downloads but I would like confirmation before u destroy this phone to which I hope don't not happen.
Click to expand...
Click to collapse
When first unlocking and rooting my phone, I thought the same thing about busy box. But what you need to do is flash a new kernel first and foremost which will remove write protection.
I'm not really trying to flash a Rom yet personally I was waiting to see if liberty was coming but I guess it wont be coming I'm having a problem with pushing soffbin do I need do fastboot and soffbin in the same folder?
Sent from my HTC6435LVW using Tapatalk 2[/QUOTE]
c2a5nn1o4n said:
I'm not really trying to flash a Rom yet personally I was waiting to see if liberty was coming but I guess it wont be coming I'm having a problem with pushing soffbin do I need do fastboot and soffbin in the same folder?
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
[/QUOTE]
Flashing a Kernel is not flashing a rom. It just helps with battery, gives you sweep2wake, and allows you actual root access
Flashing a Kernel is not flashing a rom. It just helps with battery, gives you sweep2wake, and allows you actual root access[/QUOTE]
I'm thinking about flashing viper Rom it seems to be very stable will that fix my problem?
c2a5nn1o4n said:
Flashing a Kernel is not flashing a rom. It just helps with battery, gives you sweep2wake, and allows you actual root access
Click to expand...
Click to collapse
I'm thinking about flashing viper Rom it seems to be very stable will that fix my problem?[/QUOTE]
No, again, you need to flash a kernel first so that you have write permissions
c2a5nn1o4n said:
I'm thinking about flashing viper Rom it seems to be very stable will that fix my problem?
Click to expand...
Click to collapse
Reading your OP and the rest of your comments in this thread, you're all over the place. Things you are doing will not fix your original problem and trying to achieve s-off just because it looks popular and running into difficulties trying to achieve it only adds to problems and confusion. I suggest you step back, slow down and get familiar with terms before you break another phone. While a small portion of the info is EVO 4G specific, you should check these out for general knowledge:
http://androidforums.com/evo-4g-all-things-root/278898-android-partitions-kernels-explained.html
http://androidforums.com/evo-4g-all...ore-information-about-android-partitions.html
Your root is probably sticking in between boots. As we don't have any ROMs that free up the wasted space in the system folder, it's pointless for you to try to delete apps that you don't want installed. You can simply go into Settings\Apps\All and force stop them and then disable. If that doesn't work, you can use Titanium Backup and hit the middle "Backup/Restore" tab. Click on the app you want and Freeze it (this will stop it from running.) If that doesn't float your boat, you can try to uninstall it.
docnok63 said:
Your root is probably sticking in between boots. As we don't have any ROMs that free up the wasted space in the system folder, it's pointless for you to try to delete apps that you don't want installed. You can simply go into Settings\Apps\All and force stop them and then disable. If that doesn't work, you can use Titanium Backup and hit the middle "Backup/Restore" tab. Click on the app you want and Freeze it (this will stop it from running.) If that doesn't float your boat, you can try to uninstall it.
Click to expand...
Click to collapse
Anything he does with will not stick through the boot because he doesn't really have root access. I had the exact same problem before flashing a writeable kernel. After I flashed DSB 2.5.4 [when I originally was going through the process] that corrected the whole busybox/binaries issue. Using Titanium Backup at this point is pointless as well because after he restarts his phone, they'll all be back.
Edit: Plus it will say you have root without a writeable kernel but you don't have write permissions to have things like uninstalling bloatware stick through a boot.
UrGuardian999 said:
Anything he does with will not stick through the boot because he doesn't really have root access. I had the exact same problem before flashing a writeable kernel. After I flashed DSB 2.5.4 [when I originally was going through the process] that corrected the whole busybox/binaries issue. Using Titanium Backup at this point is pointless as well because after he restarts his phone, they'll all be back.
Edit: Plus it will say you have root without a writeable kernel but you don't have write permissions to have things like uninstalling bloatware stick through a boot.
Click to expand...
Click to collapse
You're right. I had assumed he had unlocked and flashed an unsecure boot image before attempting to flash su and busybox. Perhaps I did assume too much. I'll refer him to here in that case.
UrGuardian999 said:
Anything he does with will not stick through the boot because he doesn't really have root access. I had the exact same problem before flashing a writeable kernel. After I flashed DSB 2.5.4 [when I originally was going through the process] that corrected the whole busybox/binaries issue. Using Titanium Backup at this point is pointless as well because after he restarts his phone, they'll all be back.
Edit: Plus it will say you have root without a writeable kernel but you don't have write permissions to have things like uninstalling bloatware stick through a boot.
Click to expand...
Click to collapse
Ok so I have to have busybox? I've downloaded the viper Rom with the boot img I'm downloading cubed 3.1.3 kernal now so I just go into recovery and flash the kernal correct I'm a noon to HTC this is entirely different than by bionic
c2a5nn1o4n said:
Ok so I have to have busybox I've downloaded the viper Rom with the boot img I'm downloading cubed 3.1.3 kernal now so I just go into recovery and flash the kernal correct I'm a noon to HTC this is entirely different than by bionic
Click to expand...
Click to collapse
The Viper Rom has Stock DSB Kernel boot.img zip'd with it. You can flash that rom and flash the Stock DSB modules with it and you'd be good to go
UrGuardian999 said:
The Viper Rom has Stock DSB Kernel boot.img zip'd with it. You can flash that rom and flash the Stock DSB modules with it and you'd be good to go
Click to expand...
Click to collapse
That's actually the opposite of what actually is the case. The modules are packaged with the rom and you have to flash the boot.img manually.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
That's actually the opposite of what actually is the case. The modules are packaged with the rom and you have to flash the boot.img manually.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I downloaded the boot.img and the Rom then went to recovery and only the Rom was there how do I flash the boot img manually
c2a5nn1o4n said:
I downloaded the boot.img and the Rom then went to recovery and only the Rom was there how do I flash the boot img manually
Click to expand...
Click to collapse
Nvr mind I understand but do I fastboot the boot img first or after I flash the Rom
c2a5nn1o4n said:
Nvr mind I understand but do I fastboot the boot img first or after I flash the Rom
Click to expand...
Click to collapse
The order doesn't matter
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
The order doesn't matter
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Also on my other DNA I installed cynogen but not the bootimage and when I would try to reboot I would get messed up lines would that have caused that? If it would my brain has dropped to a new low
If using Cubed 3.1.3 you'll have to reflash the modules though, correct?
UrGuardian999 said:
If using Cubed 3.1.3 you'll have to reflash the modules though
Click to expand...
Click to collapse
Nope still on stock kernal
I'm currently flashing viper as well right now, had to stop and go to work right in the middle of it. My apologies hahah