Many custom roms block ota's but root66 is essentially stock so I just wondered if it blocks ota's? Even with bootloader unlocked I assume an ota would jam a phone on stock root66 with nothing frozen?
Last edited:
Does Root66 Block ota's
- Thread starter recDNA
- Start date
I don't believe that it does, but there is a guide here on how to hopefully block OTA updates
http://forums.androidcentral.com/ve...k-verizon-otas-post-bootloader-rom-flash.html
http://forums.androidcentral.com/ve...k-verizon-otas-post-bootloader-rom-flash.html
Because the OTA will fail if it tries to load if you have a custom recovery image flashed on your device.
Root66 alone no... root66 is just the stock factory image with some slight adjustments in order to hack/root the phone. If you want a stock custom ROM... use NoSympathys zip aligned deoxed stock ROM and you'll be fine against blocking OTAs.
What baffles me is directions say if you don't like how root process goes you can just flash factory stock (as long as bootloader is locked) and you lose root and are back to stock s on.
If you can be rooted and flash a stock rom to unroot why is it if you are rooted stock (root66) and you don't freeze anything that an ota should do anything more than just return you to stock s on?
If you can be rooted and flash a stock rom to unroot why is it if you are rooted stock (root66) and you don't freeze anything that an ota should do anything more than just return you to stock s on?
That's usually the case if all you did was root and not add a custom recovery or modify anything. In the past, if you changed/deleted bloatware, it has caused updates to fail as it looks for those files before installing. It would download and try to install and fail but not brick the device. requiring you to pull the battery. CWM is similar in that the update will download and try to install but fail requiring a battery pull. Problem is that it'll likely just keep trying to install and you'll wake up one morning wondering why your phone alarm didn't go off only to find it got stuck after trying to install an update. The most effective way if you don't want to install a custom rom is to install the rooted version of the update once it's available (generally before the OTA would be pushed to you anyways) and not even worry about the OTA.
Good point...chances are if you only rooted and didn't freeze or change any system files, then accepting an OTA will just make you lose root.. if you did change system files, chances are you'll end up with a bricked phone.
Like I've mentioned, my previous device was the Galaxy Nexus... accepting an OTA only unrooted the phone, previous device before that was the Thunderbolt... which you had also and if you remember, members were left with soft bricked phones... so its always recommended not to accept an OTA while rooted.. better to be safe than sorry.
Now what makes an OTA different then someone just pushing a stock image to their device?
-An OTA is updating the existing OS on the phone, which could be a problem if something is detected that shouldn't be there.
-Flashing a stock image removes the entire OS off the phone and replaces it with a new one.
As usual that was a great explanation. You may recall I wanted to know as much as possible b4 rooting my tbolt too! I don't mean to be a pita I just like to understand as fully as possible. A key factor I hadn't consider is that flashing the stock image wipes the system whereas an ota doesn't. I could see where that could be a key difference.
I know it isn't fair to ask you about it so I will study the websites to see what I can figure out.
Now I'm trying to study how the internal memory on this phone is so different than the tbolt and how relatively little info goes to the sd card. I wouldn't want to accidentally wipe my nandroids when wiping data before installing a new rom.
I know it isn't fair to ask you about it so I will study the websites to see what I can figure out.
Now I'm trying to study how the internal memory on this phone is so different than the tbolt and how relatively little info goes to the sd card. I wouldn't want to accidentally wipe my nandroids when wiping data before installing a new rom.
That's cool.. it actually took me a few minutes to remember the difference between installing an OTA and flashing a stock image LOL.. so thanks for the refresher.
Internal storage is tricky.. as you would think the word wipe would include wiping everything. You can research it ....but very quickly...
...just remember that the only way to wipe the internal storage is to factory reset the phone by going to the phones settings---security---factory reset.
...the only way to wipe the external storage is by formatting the card, either through the phones security settings or from your computer.
...when flashing a ROM, wiping data does not delete the internal storage (only a factory reset will)
Internal storage is tricky.. as you would think the word wipe would include wiping everything. You can research it ....but very quickly...
...just remember that the only way to wipe the internal storage is to factory reset the phone by going to the phones settings---security---factory reset.
...the only way to wipe the external storage is by formatting the card, either through the phones security settings or from your computer.
...when flashing a ROM, wiping data does not delete the internal storage (only a factory reset will)
Then wiping data, dalvik, and cache in cwm is all that is necessary to flash a new rom? No equivalent to wiping system as on tbolt?
Some ppl wipe the system files before installing a rom. Some developers actually have a system wipe included in the flashing process when the rom is installed through CWM.
Oh, the key thing is that it doesn't wipe the nandroids. I'm not used to dealing with system memory vs sd card storage.
Similar threads
Trending Posts
-
-
Samsung Calendar - Foursquare asking for your Location
- Started by Trees
- Replies: 0
-
-
-
Facebook
Twitter
Instagram