Will flashing a different recovery in order to root risk bricking the phone if an OTA comes out? Or does doing this disable OTAs?
Spaded21 said:
Will flashing a different recovery in order to root risk bricking the phone if an OTA comes out? Or does doing this disable OTAs?
Click to expand...
Click to collapse
Flashing a recovery won't run the risk of bricking your phone providing you follow the instructions of course
If an OTA comes out and in the update it had a new recovery image it would just overwrite it. It won't disable OTAs but I would suggest delaying them and not letting them install. Normally an OTA will fail if the system image its looking for doesn't match. So I am under the impression if you remove some of the bloat any OTA would fail. Hope this helps.
Thanks for the response. I am coming from the Tbolt and in another popular Android forum there was a large warning saying never to accept an OTA while rooted because it could brick the phone. It also said it's possible for an OTA to apply itself. They said that custom ROMs disable OTAs so you don't have to worry about this.
So basically, a more simple question would be: If I follow this guide http://forum.xda-developers.com/showthread.php?t=2012346 and everything works and I'm rooted on a stock ROM, do I have to worry about any harm or bricking the phone after?
So if the rooting goes successfully, I don't have to worry about anything after that?
Spaded21 said:
Thanks for the response. I am coming from the Tbolt and in another popular Android forum there was a large warning saying never to accept an OTA while rooted because it could brick the phone. It also said it's possible for an OTA to apply itself. They said that custom ROMs disable OTAs so you don't have to worry about this.
So basically, a more simple question would be: If I follow this guide http://forum.xda-developers.com/showthread.php?t=2012346 and everything works and I'm rooted on a stock ROM, do I have to worry about any harm or bricking the phone after?
Click to expand...
Click to collapse
The bigger risk with an ota was that it could flash a bootloader. The risk wasn't in the recovery itself.
Related
Hello all. I am on stock 1.13 and had Google wallet set up on EVO LTE release day. Since then, of coursem Wallet quit working due to an error on boot saying the device isn't certified. The new 1.22 has come out that FIXES Wallet, but before flashing stuff I am supposed to clear Wallet's security settings so I don't brick the secure element forever.
Well I can't open Wallet since it says the device is not certified (blah blah blah). So am I safe to flash a new ROM? Remember, I had Wallet set up originally before it became "Not certified" so I am worried about flashing!
If you're stock then just let the OTA run and it will work since it's not doing a hard reset or flashing a new rom. If you were rooted, before it stopped working, you could flash a zip that only contains the OTA and you should be good to go. However if you flash a full ROM that includes the OTA then it will brick it.
Thanks Cordy. The OTA fails for me. I tried twice now and it will get about 1/4 progress bar when applying OTA update and then I get an error screen.
Am I safe to install TWRP in order to manually flash OTA zip?
Thanks again for your response!
NP before I answer that question, I guess it would be easier if you tell me what your setup is.
Stock shipped ROM 1.13 - Root, SU, and LazyPanda S-OFF. Google Wallet Setup prior to device blocking error.... Can't install OTA...
Wondering if TWRP will brick Wallet
Well twrp will just flash to your recovery partition. I assume what bricks the secure element is not being able to clear settings through the app to let it do it properly and then wiping the data partition. That said if your S-OFF check the dev section there is a thread that has the files and info you need. You can update your firmware through the bootloader and when one is available just flash an update.zip that only adds the OTA stuff and doesn't wipe your data. Yes you will need a custom recovery such as TWRP to do the latter.
Again, what bricks the secure element is still unconfirmed. I've flashed many ROMs without first clearing my Wallet settings, and I've flashed ROMs just clearing data in Settings -> Apps -> Manage Apps, and my Wallet still works fine. But I don't imagine applying the OTA would brick your secure element, as that's an update directly from the manufacturer.
Install TWRP. Flash Captain's 1.22 firmware zip. Download the 1.22 OTA zip and remove the firmware package out of the zip... then flash the 1.22 OTA zip in receovery.
You don't want to take the OTA via recovery in its original form. It contains the firmware package with hboot and stock recovery. Thats why I advised to flash Captains firmware first that does not contain hboot and recovery. Then remove the firmware package out of the original 1.22 OTA and flash the OTA through recovery.
Hopefully that works.
leerage said:
Install TWRP. Flash Captain's 1.22 firmware zip. Download the 1.22 OTA zip and remove the firmware package out of the zip... then flash the 1.22 OTA zip in receovery.
You don't want to take the OTA via recovery in its original form. It contains the firmware package with hboot and stock recovery. Thats why I advised to flash Captains firmware first that does not contain hboot and recovery. Then remove the firmware package out of the original 1.22 OTA and flash the OTA through recovery.
Click to expand...
Click to collapse
But I also took out the boot.img from that firmware.zip, which will need to be flashed for the device to boot after the OTA is applied. And I don't think TWRP will allow firmware to be flashed, so it would have to be done through the bootloader.
Captain_Throwback said:
But I also took out the boot.img from that firmware.zip, which will need to be flashed for the device to boot after the OTA is applied. And I don't think TWRP will allow firmware to be flashed, so it would have to be done through the bootloader.
Click to expand...
Click to collapse
Oh man now I'm really confused!
What is the best option you can think of for my scenario? (to not brick wallet security module)
Thanks all
Kujila said:
Oh man now I'm really confused!
What is the best option you can think of for my scenario? (to not brick wallet security module)
Click to expand...
Click to collapse
There's no guarantee that flashing anything will brick your secure element.
I doubt Sprint/HTC would release an OTA that would brick your secure element, since no one that's unrooted can get into Wallet to clear their settings.
Captain_Throwback said:
Again, what bricks the secure element is still unconfirmed. I've flashed many ROMs without first clearing my Wallet settings, and I've flashed ROMs just clearing data in Settings -> Apps -> Manage Apps, and my Wallet still works fine. But I don't imagine applying the OTA would brick your secure element, as that's an update directly from the manufacturer.
Click to expand...
Click to collapse
I respect that. I honestly stopped keeping up with the whole thing since I wasn't rooting just yet. Interesting you were able to do that without bricking your secure element. From accounts I read early on including the posted sticky about it if you didn't clear settings through app and flashed a new Rom it would brick it. Also why ppl were warned that if they used Wallet prior to it being unavailable and then S-OFF without being able to clear settings first that resulted in a Secure Element brick. I'd say be safe rather than sorry.
Sent from my EVO using xda app-developers app
Captain_Throwback said:
There's no guarantee that flashing anything will brick your secure element.
I doubt Sprint/HTC would release an OTA that would brick your secure element, since no one that's unrooted can get into Wallet to clear their settings.
Click to expand...
Click to collapse
I think he is concerned about flashing a full Rom based on the earlier conversation. As you stated flashing the OTA won't break anything so if you flash a rooted version of the update you will be fine which is what he is looking for. He is concerned about someone releasing a full Rom that includes the update that will clear data that has the chance to brick his secure element.
Sent from my EVO using xda app-developers app
Captain_Throwback said:
There's no guarantee that flashing anything will brick your secure element.
I doubt Sprint/HTC would release an OTA that would brick your secure element, since no one that's unrooted can get into Wallet to clear their settings.
Click to expand...
Click to collapse
Cordy said:
I think he is concerned about flashing a full Rom based on the earlier conversation. As you stated flashing the OTA won't break anything so if you flash a rooted version of the update you will be fine which is what he is looking for.
Click to expand...
Click to collapse
I can not apply the OTA update to 1.22, as it gets 1/4 of the way through and then provides a red device "warning" screen and stops dead.
So I should be patient and wait for a "root version" of the update like Cordy says?
Thanks all! :highfive:
Kujila said:
I can not apply the OTA update to 1.22, as it gets 1/4 of the way through and then provides a red device "warning" screen and stops dead.
So I should be patient and wait for a "root version" of the update like Cordy says?
Thanks all! :highfive:
Click to expand...
Click to collapse
If I'm not mistaken you said you're on stock recovery, did you do a check for update and try installing it that way? Actually now that I think of it if you're trying to flash the OTA as is, have you modified anything in your system folder like status bar mods, tether mods stuff like that. If you have any mods chances are that's what's causing the update to fail. Either way I'd hold off. You already said you flashed Captain Throwbacks firmware zip through the bootloader so you're good as far as having the latest radios and what not. Next is to just wait until someone makes a rooted OTA update.zip and flash that. Curiously how is the newer firmware reacting with the older software base?
I actually have TWRP. I do have a tether mod so that might mess it up too
There's someone uploading a root version so I will try that when it gets posted:
http://forum.xda-developers.com/showpost.php?p=28609753&postcount=55
Thanks!
Kujila said:
I actually have TWRP. I do have a tether mod so that might mess it up too
There's someone uploading a root version so I will try that when it gets posted:
http://forum.xda-developers.com/showpost.php?p=28609753&postcount=55
Thanks!
Click to expand...
Click to collapse
Ok so those two would've been you're issues. Had you put back stock recovery it would've still failed when checking the signature of the files that the tether mod uses. Once xHausx uploads his update.zip you should be good to go since you already have the firmware.
Fixed it by installing the 1.22 root zip OVER my existing 1.13 installation, without wiping anything.
Wallet is OK!
Also I got 4G now :highfive::good::highfive::good:
The file : http://forum.xda-developers.com/showthread.php?t=1766628
Hi everyone. Im real good with tech but i cant find anyone having asked...
I want to go buy the S4 and I will definitely root it (following the posted instructions on here) but before i do, will i be able to instal OTA updates after and if not, is there another way id be able to install updates? I used Voodoo rootkeeper on my tablet after rooting and the 1st ota went fine and kept root, the 2nd ota killed the root even while using Voodoo...
Please, any any all responses asap appreciated. I want to get the phone asap as i am tired of my rooted Bionic.
Thank all.
bobstone said:
Hi everyone. Im real good with tech but i cant find anyone having asked...
I want to go buy the S4 and I will definitely root it (following the posted instructions on here) but before i do, will i be able to instal OTA updates after and if not, is there another way id be able to install updates? I used Voodoo rootkeeper on my tablet after rooting and the 1st ota went fine and kept root, the 2nd ota killed the root even while using Voodoo...
Please, any any all responses asap appreciated. I want to get the phone asap as i am tired of my rooted Bionic.
Thank all.
Click to expand...
Click to collapse
Just wait for a rooted stock ROM based on the OTA to be made by a dev. You never NEED to take an OTA.
Thanks but im not sure what you mean. I have no interest in loading custom roms nor over-screwing around with the phone. Do you mean wait for another root process or wait for a download for an ota update?
Thanks again
Im guessing you mean a rom will be released again after the ota is out with the ota integrated in it... That process makes me kind of nervous as i need my phone for work as well as personal and cant risk screwing up the phone or erasing data eta...
There is pretty much always someone that releases the stock ROM flashable in a custom recovery so you can have a rooted stock ROM. Look at the dev beanstownm106 ROM in the development section. It is basically the stock ROM rooted with some very minor tweaks, but flashable with a custom recovery like TWRP.
BUT...there is almost never anything you can't do with basically any ROM that you can do with the stock ROM. So you really don't need the stock ROM...some people just prefer it. For my old Thunderbolt, it was pretty well known that for a long time there was a custom ROM, very similar to the stock ROM, that was more stable than stock (SkyRaider Zeus).
Another BUT: if you need Good for work, prepare for a constant fight with root detection. And you will want to back up your data often. I have a BB for work that I leave untouched (its not mine).
One more thing...the Loki workaround has its advantages...the bootloader is still locked and untouched, so it would be pretty hard to brick the device because you can get back into download mode and use odin to flash back to factory.
Whats the loki workaround? Also, im dont want to be doing any kind of flashing... I just simply want to root the s4 (which i now have) and be able to run ota updates or if not, download the ota and install the update manually. And if i get an ota, if it will kill root, even if i run voodoo.
Please, if someone could, let us all know if ota wont run or will kill root on say the s3 or s4 and if downloadable updates are another option... without flashing anything or going to crazy.
Thanks again in advance.
I am giving two VZW GS4's to my parents for Christmas and I would like to make things as simple as possible for them, which means getting rid of all the boatware that Verizon/Samsung includes. I'm familiar with rooting/flashing etc. with my Sprint GS4, but I am still somewhat bewildered by all the info regarding the VZW phones and all the different versions.
These VZW phones are on the NC5 baseband (?) and if I understand correctly they can be rooted with towelroot but cannot install a custom recovery because the bootloader is locked.
Once I root, will the phone still receive OTA updates and install properly, or will there just be a continual message saying that the update failed?
I don't plan on trying to install a custom ROM, but if I understand correctly the only way to do so is by using safestrap?
Is it possible to backup the phone, similar to a ROM backup in TWRP for example? Will I be able to return to a full stock state after root? In other words, after I root what happens if I do a factory data reset?
Thanks in advance.
buckeyestargazer said:
I am giving two VZW GS4's to my parents for Christmas and I would like to make things as simple as possible for them, which means getting rid of all the boatware that Verizon/Samsung includes. I'm familiar with rooting/flashing etc. with my Sprint GS4, but I am still somewhat bewildered by all the info regarding the VZW phones and all the different versions.
These VZW phones are on the NC5 baseband (?) and if I understand correctly they can be rooted with towelroot but cannot install a custom recovery because the bootloader is locked.
Once I root, will the phone still receive OTA updates and install properly, or will there just be a continual message saying that the update failed?
I don't plan on trying to install a custom ROM, but if I understand correctly the only way to do so is by using safestrap?
Is it possible to backup the phone, similar to a ROM backup in TWRP for example? Will I be able to return to a full stock state after root? In other words, after I root what happens if I do a factory data reset?
Thanks in advance.
Click to expand...
Click to collapse
1. You are correct. The nc5 can only be rooted. The bootloader is not unlocked or even possible to workaround; safestrap is your only option.
2. Once you root, your phone will not be stock anymore so OTAs will not work. You must unroot and restore your phone back to stock in order to update via OTA. However, if you learn how to use ODIN, your life will become much easier.
3. Safestrap is the only way.
4. You can backup with Safestrap. Yes you will be able to return back to a full stock state using ODIN. If you use ODIN to factory reset, your phone becomes back to stock i.e. unrooted.
Raymondlikesroot said:
2. Once you root, your phone will not be stock anymore so OTAs will not work. You must unroot and restore your phone back to stock in order to update via OTA. However, if you learn how to use ODIN, your life will become much easier.
Click to expand...
Click to collapse
Thanks. One more question: Once rooted, if I stay on the stock rom, will the phone still receive OTA update notifications (even though it will fail install)?
I'm a little familiar with odin so I should be able to go back to full stock if necessary.
buckeyestargazer said:
Thanks. One more question: Once rooted, if I stay on the stock rom, will the phone still receive OTA update notifications (even though it will fail install)?
I'm a little familiar with odin so I should be able to go back to full stock if necessary.
Click to expand...
Click to collapse
Yes, unfortunately, you will receive constant update messages. However, if you are rooted, you can stop these messages. Download an app called "titanium Backup" and freeze fwupdate.apk. That specific app is what causes all the update messages to appear.
I have my T-Mobile LG V-10 rooted with Sir-Altus rom currently.
Without starting a fight or anything, I am trying to find out how I could go about restoring my phone to stock to be able to accept the Marshmellow update successfully without bricking my phone.
I understand that there is a difficulty in rooting Marshmellow and I am OK with that.
Can anyone link to a step-by-step on how to restore my phone to fully stock so I can accept the Marshmellow update and apply it?
Thank you,
Whiteice
WhiteiceDMSTech said:
I have my T-Mobile LG V-10 rooted with Sir-Altus rom currently.
Without starting a fight or anything, I am trying to find out how I could go about restoring my phone to stock to be able to accept the Marshmellow update successfully without bricking my phone.
I understand that there is a difficulty in rooting Marshmellow and I am OK with that.
Can anyone link to a step-by-step on how to restore my phone to fully stock so I can accept the Marshmellow update and apply it?
Thank you,
Whiteice
Click to expand...
Click to collapse
Should be pretty straight-forward. Also as an FYI, you now CAN root you LG V10 starting from 6.0 (Marshmallow) stock. So there's really not much risk involved. I think the upgrade from 5.1.1 to 6.0 relocks your bootloader so...i don't think you have to do much. If you have an upgrade option in your settings on the phone you can take it or you can go to the LG website and download the software and follow the steps. http://www.lg.com/us/support/mobile-software-updates
Can I accept the update on the phone rooted and with TWRP installed?
"I wouldn't do it by just downloading the update and installing it through the ui", you'll probably get stuck in a boot loop on the lg logo boot screen! Try researching kdz or tot flashing! Youll then only have to click a few times on your PC and after that the file should just upgrade the phone through your USB hub
You can uodate using Eliminater74's Rom.
Flash Part 1 - Dont Reboot
Flash Part 2 - Dont Reboot
Flash Super SU
*in Eliminater74s Rom OP it says to use Fastboot again to OEM unlock. Just read it thoroughly*
I recently installed a custom recovery on my exynos s9+ on stock pie. I actually thought unlocking oem and installing a custom recovery + root would trip Knox and prevent me from getting any updates but it didn't. Was roaming on my phone today and somehow found myself in the phone update menu. I tapped on check for updates and low and behold I could download an update. My problem is now that I'm on a custom recovery how would any update i download even manage to install? And even if it does is there a possibility that it might cause troubles like re-enabling dm-verity lock and bricking my phone? I wanna know what might happen if I proceed to download and install that OTA update.
drickles said:
I recently installed a custom recovery on my exynos s9+ on stock pie. I actually thought unlocking oem and installing a custom recovery + root would trip Knox and prevent me from getting any updates but it didn't. Was roaming on my phone today and somehow found myself in the phone update menu. I tapped on check for updates and low and behold I could download an update. My problem is now that I'm on a custom recovery how would any update i download even manage to install? And even if it does is there a possibility that it might cause troubles like re-enabling dm-verity lock and bricking my phone? I wanna know what might happen if I proceed to download and install that OTA update.
Click to expand...
Click to collapse
Personally I would not do the OTA as it may not update properly (if even at all). Every phone I have rooted before this was one of the cautions usually posted... I would double check in what ever tutorial, thread, utility faq you used to make sure.
I would suggest you wait for an update to be made that is flashable with your custom recovery. If your custom recovery has the feature (like TWRP) make a backup of what you have installed, flash the update and if things don't work you can restore your backup.
I miss having that kind of backup/restore ability via custom recovery on my phone.. sure comes in handy when things go sideways
Nothing happens. According to my experience and contents in the OTA zip, twrp will simply just spit it out. No dm-verity re-lock or bricking too.
You can always download one of the custom systems which are regularly updated.
Example would be Soldier ROM.
I recommend find your new firmware and flash it. You will lose all of your file and root-recovery you can have them all back