Guestn/a posts Thanks: 0
So.. The Android 5.1.1 version is here and I've unrooted my phone for the update, but it still shows "Could not verify." Are there any files that cause the verifying process to know that I had rooted my device? If yes, can I delete it or what? Or are there any other ways to update without flashing a ftf file? (1. Because that ftf file is very big and my Internet speed couldn't afford it. 2. Because I don't want to wipe my apps and data) Any help would be appreciated!
@OP, If I understand right, it's the custom recovery you might have that prevents the OTA update from completing successfully. Which, in a way, is a good thing.
Step 1: reroot your phone while you still can.
Step 2: download any of a number of flashable, pre-rooted 5.1.1 ROMs with recovery (*.zip) floating around now and flash it with your current recovery, wiping only cache and Dalvik upon exit. This is what I've done to keep all my date and settings and still be rooted and have recovery on 5.1.1.
wicozani said:
@OP, If I understand right, it's the custom recovery you might have that prevents the OTA update from completing successfully. Which, in a way, is a good thing.
Step 1: reroot your phone while you still can.
Step 2: download any of a number of flashable, pre-rooted 5.1.1 ROMs with recovery (*.zip) floating around now and flash it with your current recovery, wiping only cache and Dalvik upon exit. This is what I've done to keep all my date and settings and still be rooted and have recovery on 5.1.1.
Click to expand...
Click to collapse
After I flash this, can my phone update OTA or the same problem will happen?
As far as we know, custom recoveries will always prevent OTA updates to our Xperia devices. Why are OTA updates seemingly so important to you? With your custom recovery installed, you can always simply flash the new update when it becomes available; often before the OTA update is released.
Sent from my D6503 using Tapatalk
wicozani said:
As far as we know, custom recoveries will always prevent OTA updates to our Xperia devices. Why are OTA updates seemingly so important to you? With your custom recovery installed, you can always simply flash the new update when it becomes available; often before the OTA update is released.
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
Hmm okay thankyou
wicozani said:
As far as we know, custom recoveries will always prevent OTA updates to our Xperia devices. Why are OTA updates seemingly so important to you? With your custom recovery installed, you can always simply flash the new update when it becomes available; often before the OTA update is released.
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
Can you give me a link for the official ROM? Thanks!
Can I use the AOSPA ROM? Does it need to unlock my bootloader to flash it?
Some consideration about this thread.
1) Not never the OTA updade overwrite the ROOT, example I passed from .627 to .28 through OTA update without lose the root and recovery. This depend of kind of update.
2) I think that to install a pre-rooted rom is not a good thing, because the baseband is almost always different an this can create issue related the WI-fi and carrier signal (3G, 4G).
3) I always installed the root, recovery and mod as well. But now I have understand that is not really necessary to install this. At least the stock Z2 have a good/beautiful OS and good hardware and there is no need to change some colors or icons to improve it.
I'm boring to flash and restore my data every new firmware or new mod. (now a new firmware is already certified and will be ready soon).
Maybe I will think to change the room when my phone will be obsolete
Regards
giancaleone said:
Some consideration about this thread.
1) Not never the OTA updade overwrite the ROOT, example I passed from .627 to .28 through OTA update without lose the root and recovery. This depend of kind of update.
2) I think that to install a pre-rooted rom is not a good thing, because the baseband is almost always different an this can create issue related the WI-fi and carrier signal (3G, 4G).
3) I always installed the root, recovery and mod as well. But now I have understand that is not really necessary to install this. At least the stock Z2 have a good/beautiful OS and good hardware and there is no need to change some colors or icons to improve it.
I'm boring to flash and restore my data every new firmware or new mod. (now a new firmware is already certified and will be ready soon).
Maybe I will think to change the room when my phone will be obsolete
Regards
Click to expand...
Click to collapse
Totally understand, thankyou, so I just flash the original ROM from AOSPA and without root is enough right?
Wayhome said:
Totally understand, thankyou, so I just flash the original ROM from AOSPA and without root is enough right?
Click to expand...
Click to collapse
If you do not have an unlocked bootloader, you cannot flash anything but a pre-rooted stock 5.1.1 ROM with recovery. There are several types available in the General Z2 column.
Sent from my D6503 using Tapatalk
I have a crazy thought flashed across my mind haha, that file that I downloaded via OTA SYSTEM UPDATE is still there, can I make it as a zip file and flash it?
Wayhome said:
I have a crazy thought flashed across my mind haha, that file that I downloaded via OTA SYSTEM UPDATE is still there, can I make it as a zip file and flash it?
Click to expand...
Click to collapse
Why would you do that? You wouldn't have root and you wouldn't have a recovery; you'd be stuck, unable to root and install a recovery. Do what I said and you'll be fine.
Sent from my D6503 using Tapatalk
Can you help me to find one? That doesn't need to unlock bootloader to flash.
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
Hey guys,
I am not new to the rooting or CWM scene but I like to double check these things with different phone models just in case as I do not want an expensive brick, especially with the S3 as I am looking to get one of these bad boys.
My question is, If I root/Install CWM will this cause issues with OTA updates or updates through Samsung Kies ? Or once an Update is installed would I simply need to re-root and install CWM again ?
I was taking a look at this thread and it bought my question to mind: http://forum.xda-developers.com/showthread.php?t=1703488
I would for now like to stick to the Stock Roms and just want to be aware of the consequences of having Root/CWM and Updating my phone.
Cheers guys.
If you root, your device status will show as "Modified," and you won't get OTA updates.
Not a big deal as long as XDA is up and running, IMO. You'll get update here faster than you'll get them OTA anyway in nearly all cases.
donalgodon said:
If you root, your device status will show as "Modified," and you won't get OTA updates.
Not a big deal as long as XDA is up and running, IMO. You'll get update here faster than you'll get them OTA anyway in nearly all cases.
Click to expand...
Click to collapse
Ahh right, what about CWM ? As you say, even if I cannot Update OTA or through Kies I can use Odin. I guess I just need to find out about installing any updates with CWM installed, Though I should imagine nothing will happen as the stock recovery would be put back and I would simply have to install CWM again but any further info would be great
Thanks !
panzerscope said:
Ahh right, what about CWM ? As you say, even if I cannot Update OTA or through Kies I can use Odin. I guess I just need to find out about installing any updates with CWM installed, Though I should imagine nothing will happen as the stock recovery would be put back and I would simply have to install CWM again but any further info would be great
Thanks !
Click to expand...
Click to collapse
If you use desktop Odin to flash, you'll lose the custom recovery and be reverted to stock recovery. You'll likely need to relfash the recovery again as well as root, unless the ROM you flash via Odin is pre-rooted.
Mobile Odin will allow you to flash the tar file and keep root, recovery, etc. 99% of the time, I use mobile Odin for stock ROMs these days.
I'm still on a rooted 4.1.2 and have the second OTA update to 4.3 (.109) in my notifications. Rather than go through the whole flashing process, I wondered if anyone had successfully used the Survival mode in SuperSU to retain root from this point to .109?
Chimpdaddy said:
I'm still on a rooted 4.1.2 and have the second OTA update to 4.3 (.109) in my notifications. Rather than go through the whole flashing process, I wondered if anyone had successfully used the Survival mode in SuperSU to retain root from this point to .109?
Click to expand...
Click to collapse
you can try ot yourself,.but i reckon it will give you error while applying update.
Rootk1t said:
you can try ot yourself,.but i reckon it will give you error while applying update.
Click to expand...
Click to collapse
Yup, I'd read similar. I was more concerned that it would update but I'd lose root, so have to then do the full process.
Chimpdaddy said:
Yup, I'd read similar. I was more concerned that it would update but I'd lose root, so have to then do the full process.
Click to expand...
Click to collapse
I have a rooted 422 with su pro, The update process aborts mid way and the OS is left untouched, leaving all as it was. I am just too lazy to do the flashtool thing and all, so I left it alone.
I was able to go from 412 to 422 with the OTA and keep root.
bjrmd said:
I have a rooted 422 with su pro, The update process aborts mid way and the OS is left untouched, leaving all as it was. I am just too lazy to do the flashtool thing and all, so I left it alone.
I was able to go from 412 to 422 with the OTA and keep root.
Click to expand...
Click to collapse
I know, so lazy, if I wait long enough 4.4 will come around and that might keep root!
Nobody's read a successful account of this working then? I may as well just try it and see...
Possibly
If you have bought Supersu pro then you could try survival mode, provided that your phone is only root and doesn't have a custom recovery installed.
I personally haven't tried it on my tablet but on other phones like G2, OTA update retains root.
If you have CWM or TWRP installed then it won't let you update.
adielee said:
If you have bought Supersu pro then you could try survival mode, provided that your phone is only root and doesn't have a custom recovery installed. I personally haven't tried it on my tablet but on other phones like G2, OTA update retains root. If you have CWM or TWRP installed then it won't let you update.
Click to expand...
Click to collapse
Judging by all the posts I have read here so far, attempting to update to 4.3 via OTA will fail if your tablet's current firmware has been modified to have root access. Having SuperSU Pro installed with Install SuperSU into /system and/or Survival mode enabled does not help. I have attempted an OTA update with 10.4.B.0.577 and 10.4.1.B.0.109, and the update failed in both attempts. It's okay with me though. After reading about 4.3's bugs and seeing its UI, I don't really want to update to 4.3 anymore.
Cat McGowan said:
Judging by all the posts I have read here so far, attempting to update to 4.3 via OTA will fail if your tablet's current firmware has been modified to have root access. Having SuperSU Pro installed with Install SuperSU into /system and/or Survival mode enabled does not help. I have attempted an OTA update with 10.4.B.0.577 and 10.4.1.B.0.109, and the update failed in both attempts. It's okay with me though. After reading about 4.3's bugs and seeing its UI, I don't really want to update to 4.3 anymore.
Click to expand...
Click to collapse
you're right, but besides bugs introduced as every firmware does, some very positive tweaks were done "under the bonnet" like TRIM enabled to make less wearing of flash modules, and some performance tweaks noticeable not only in launcher, but mostly in games too.
So if you have root and recovery installed you can backup your data and install .109 prerooted firmware to evaluate it yourself.
Rootk1t said:
you're right, but besides bugs introduced as every firmware does, some very positive tweaks were done "under the bonnet" like TRIM enabled to make less wearing of flash modules, and some performance tweaks noticeable not only in launcher, but mostly in games too.
So if you have root and recovery installed you can backup your data and install .109 prerooted firmware to evaluate it yourself.
Click to expand...
Click to collapse
I would also recommend to flash a pre-rooted 4.3 from scratch for performance and less issues, but if you have a lot of apps installed and everything set up the way you want it can be a pain in the a$#.
Also the OP doesn't want to flash. But if he can it means that the OTA won't install because he has a custom recovery.
I don't see why Supersu pro with survival mode won't work for an OTA to keep root. This is provided that a you do not have a custom recovery installed. It's kind of the purpose for survival mode and if you do a search it works with most other updates with other devices (even for 4.4.2)
It may be possible that other mods may affect the OTA especially ones which were flashed or possibly xposed.
adielee said:
I don't see why Supersu pro with survival mode won't work for an OTA to keep root. This is provided that a you do not have a custom recovery installed. It's kind of the purpose for survival mode and if you do a search it works with most other updates with other devices (even for 4.4.2) It may be possible that other mods may affect the OTA especially ones which were flashed or possibly xposed.
Click to expand...
Click to collapse
I do not have (nor do I want) a custom recovery or custom ROM installed on my XTZ. I only have root access, which I achieved by using DooMLoRD's Easy Rooting Toolkit when I first received my XTZ back in May 2013. Since then, thanks to SuperSU Pro, I have updated my XTZ's firmware via OTA twice without losing root access. It is only with the last two XTZ firmware releases, 10.4.B.0.577 and 10.4.1.B.0.109, that the OTA updates fail. I suspect Sony's latest firmware releases include detection of root access, etc., which causes the update's failure to install.
Nope
Cat McGowan said:
I do not have (nor do I want) a custom recovery or custom ROM installed on my XTZ. I only have root access, which I achieved by using DooMLoRD's Easy Rooting Toolkit when I first received my XTZ back in May 2013. Since then, thanks to SuperSU Pro, I have updated my XTZ's firmware via OTA twice without losing root access. It is only with the last two XTZ firmware releases, 10.4.B.0.577 and 10.4.1.B.0.109, that the OTA updates fail. I suspect Sony's latest firmware releases include detection of root access, etc., which causes the update's failure to install.
Click to expand...
Click to collapse
Well, I tried it, thinking the worse that could happen is that it would abandon the install, but unfortunately it went right through and upgraded to 4.3 and I lost root
I'd put it into OTA survival mode but not into system/apps. I had no xposed or recovery anything, just root.
So there we go. Thanks for the discussion guys, hope this is useful to someone else.
How do I root it in 4.3? Any ideas?
Try this
http://forum.xda-developers.com/showthread.php?t=2703774
Sent from my SGP311 using xda app-developers app
I have an unlocked 5X with TWRP installed (but have not yet modified system.)
I'm about to flash SuperSu but have 2 questions.
1) Will I lose functions such as the fingerprint reader if the device is rooted?
2) Is there a risk of getting in a bootloop if a firmware update is downloaded?
harryspar said:
I have an unlocked 5X with TWRP installed (but have not yet modified system.)
I'm about to flash SuperSu but have 2 questions.
1) Will I lose functions such as the fingerprint reader if the device is rooted?
2) Is there a risk of getting in a bootloop if a firmware update is downloaded?
Click to expand...
Click to collapse
1) Will I lose functions such as the fingerprint reader if the device is rooted?
if you install the stock rom you will keep this functionality otherwise you need to wait concerning CM13 build
2) Is there a risk of getting in a bootloop if a firmware update is downloaded?
there is always a risk but minor
harryspar said:
2) Is there a risk of getting in a bootloop if a firmware update is downloaded?
Click to expand...
Click to collapse
You will not be able to flash ota with a custom recovery. When a new update arrives you will have to wait for a twrp compatible zip or return to complete stock to flash the update
wickedesires said:
You will not be able to flash ota with a custom recovery. When a new update arrives you will have to wait for a twrp compatible zip or return to complete stock to flash the update
Click to expand...
Click to collapse
Right, I remember this happening with other devices, as the OTA uses a recovery script.
I wonder if there will be nag screens for OTA's. This rendered my wife's S4 so annoying to use, with a persistent notification, until I found a block method (disallowing notifications didn't work since I'd have had to disable notifications for the entire Android System UI...)
harryspar said:
I wonder if there will be nag screens for OTA's.
Click to expand...
Click to collapse
I went about 5 days before I installed the b140 update and I don't recall any annoying notifications. I know exactly what you mean though my s5 active did the same thing because I didn't want to update and lose root. I finally found a way to disable it but like you said it was very irritating.
HI, do the OTA updates still work after unlocking bootloader, installing TWRP and rooting?
I've ordered one and was thinking about doing the about doing the above right out of the box.
Yes, will work
pratikp16 said:
HI, do the OTA updates still work after unlocking bootloader, installing TWRP and rooting?
I've ordered one and was thinking about doing the about doing the above right out of the box.
Click to expand...
Click to collapse
OTA AFTER
Unlocking bootloader - Yes
Installing TWRP - probably yes, but it might replace TWRP with default recovery during update
Rooting - idk
Hey guys
I would like to bring this topic up again because I want to be super sure.
I unlocked BL, installed twrp and rooted with supersu, stable Rom.
Now I got ota update notice. Is it save to update or will it brick?
No, you probably will end with an unbootable device or defective operating system (but it could work too, it's unpredictable without trying).
You will end flashing a fastboot image via MiFlash, so better not OTA updating and flashing directly a full ROM image when you're ready to update.
If you want to try the OTA update, backup your data before because it could become inaccessible after.
BubuXP said:
No, you probably will end with an unbootable device or defective operating system (but it could work too, it's unpredictable without trying).
You will end flashing a fastboot image via MiFlash, so better not OTA updating and flashing directly a full ROM image when you're ready to update.
If you want to try the OTA update, backup your data before because it could become inaccessible after.
Click to expand...
Click to collapse
OK, will loose settings and App data when flashing the (updated) full stock image?
edwardenglish said:
OK, will loose settings and App data when flashing the (updated) full stock image?
Click to expand...
Click to collapse
If I remember well, there should be an option to retain settings and apps data (it depends on what .bat file you choose to flash), but I advise against preserving this data, as it will probably cause many problems afterward.
BubuXP said:
If I remember well, there should be an option to retain settings and apps data (it depends on what .bat file you choose to flash), but I advise against preserving this data, as it will probably cause many problems afterward.
Click to expand...
Click to collapse
Yes that's what I thought so too.
So to sum it up correctly with unlocked BL and root one should only update via flashing whole image and do a clean flash loosing all data and settings.