Hi, so I have Z2 on 5.0.2 and I've rooted my phone about a month ago with this guide: http://forum.xda-developers.com/xperia-z2/general/root-t3108230. And now, when the 5.1 update was released I can't update because my phone says it's up to date. I've tried connecting to PC and update through PC companion but same result occurred.
Now before you start saying that I won't be able to update through OTA because I have dual recovery, I can remove the recovery and do full unroot can't I? But that's currently not my problem because I won't get the OTA anyway.
BTW, my friend (same country, same phone) received the update 2-3w weeks ago...
So, my question is.. Is the fact that I've rooted my phone affecting OTA? And if so, can I just unroot and then I will receive the update?
Or just install a rooted 5.1 zip in recovery? Pretty sure this has been talked about over and over and over and over and over............
Sent from my D6503 using Tapatalk
o0 Matt 0o said:
Or just install a rooted 5.1 zip in recovery? Pretty sure this has been talked about over and over and over and over and over............
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
Well, I've read that, but 1. I heard about some people having issues with prerooted roms and 2. I wasn't really sure if I could with the guide I followed. I guess I'm gonna try it then...
You can always flash a generic ftf via flashtool, it is an unmodified stock firmware file, no root etc..
Related
Hey guys im curious if I need to update in order to update
The thing is I own a C6806 unlocked in the US and I haven't received the 4.4 update yet not even via pc companion
The thing is it only shows the. 136 Which I decided not to perform because of the bugs
So do I need to update to. 136 first?
Thanks
southsidejamaicaqueens said:
Hey guys im curious if I need to update in order to update
The thing is I own a C6806 unlocked in the US and I haven't received the 4.4 update yet not even via pc companion
The thing is it only shows the. 136 Which I decided not to perform because of the bugs
So do I need to update to. 136 first?
Thanks
Click to expand...
Click to collapse
Well, you can flash the ftf file instead of waiting of the update.
southsidejamaicaqueens said:
Hey guys im curious if I need to update in order to update
The thing is I own a C6806 unlocked in the US and I haven't received the 4.4 update yet not even via pc companion
The thing is it only shows the. 136 Which I decided not to perform because of the bugs
So do I need to update to. 136 first?
Thanks
Click to expand...
Click to collapse
Every ROM has its bugs so be not afraid of them, take the improvement and learn to appreciate it. For your case, that would be no problem to skip it.
Omate today told that the new firmware update is available by OTA update. But, I checked this update and I did not found anything. If my device is rooted can i still able to received updates or this is the Problem? Also, can I make unroot to able to Update? Any one have to advice
I'm on stock
elsabea said:
Omate today told that the new firmware update is available by OTA update. But, I checked this update and I did not found anything. If my device is rooted can i still able to received updates or this is the Problem? Also, can I make unroot to able to Update? Any one have to advice
Click to expand...
Click to collapse
I haven't rooted and I could download and apply the OTA fine, so it would appear that rooting prevents OTA!
andreasmartens said:
I haven't rooted and I could download and apply the OTA fine, so it would appear that rooting prevents OTA!
Click to expand...
Click to collapse
I install application called OTA ROOT KEEPER which allow me to unroot the device and re root again, but also nothing happens after unroot it
Why don't you check threads before you open new one?!
I opened one and we said everything there...
Sent from my D6503 using Tapatalk
Hi All!
I have a T-Mobile version of Z2. If I flash the unlocked firmware version will I receive OTA updates for this? Or Sony checks my IMEI and give me update acorrdingly? I want to rid all of the T-Mobile bloatwares
Thanks!
Hi,
there are two ways to get rid of this:
1st install any official Rom via Flashtool (so your warranty isn't broken).
2nd way is to root device and just change the customer ID then you get the official Sony Firmare via Sony Update Service.
Via Flashtool you've got the option to flash back the T-Mobile Firmware.
Greets,
n3087
AttilaGolik said:
Hi All!
I have a T-Mobile version of Z2. If I flash the unlocked firmware version will I receive OTA updates for this? Or Sony checks my IMEI and give me update acorrdingly? I want to rid all of the T-Mobile bloatwares
Thanks!
Click to expand...
Click to collapse
n3087 said:
Hi,
there are two ways to get rid of this:
1st install any official Rom via Flashtool (so your warranty isn't broken).
2nd way is to root device and just change the customer ID then you get the official Sony Firmare via Sony Update Service.
Via Flashtool you've got the option to flash back the T-Mobile Firmware.
Greets,
n3087
Click to expand...
Click to collapse
Thanks! So, if I understand correctly if I flash the official unlocked ROM via Flashtool, after that when a new update comes in OTA I will get the T-Mobile version because the phone's customer ID?
Anyone else
If you update with an OTA on an unlocked bootloader you will brick your device for sure so dont do it, just flash stock kernel and relock your bootloader and then you can update with an OTA.
Hope this is enough info.
Sent From My Z2 On Mw Revolution V2.4
.. A Piece Of Art From A Rom ..
Pandemic said:
If you update with an OTA on an unlocked bootloader you will brick your device for sure so dont do it, just flash stock kernel and relock your bootloader and then you can update with an OTA.
Hope this is enough info.
Sent From My Z2 On Mw Revolution V2.4
.. A Piece Of Art From A Rom ..
Click to expand...
Click to collapse
I'm talking about locked bootloader, but network unlocked. I bought my phone from T-Mobile, but with SIM unlocked and I think I will get the general firmware earlier than T-Mobile version, plus bloatfree.
Flash Generic FTF and all updates you receive via OTA will be for that Generic FTF, no T-Mobile stuff will be installed it if via OTA if you have network free firmware.
Hope that helps you
I am on T mobile Croatia. I flashed inernational rom with flashtool, after that i got 4.4.4 OTA same day it was released. No root, no unlocked bootloader.
Sent from my D6503 using XDA Free mobile app
Hello,
I have the following phone:
Moto Z
XT1650-03
RETEU
Android 6.0.1 MPL24.246-45
When I got the phone I only unlocked the bootloader en flashed TWRP recovery.
Now the Android 7 OTA update is released. I got the popup for de OTA update but it wasn't able to install the update because of TWRP Recovery.
After that I flashed the recovery with a stock recovery from the stock Android 6.0.1 MPL24.246-17 ROM, found in a Moto Z official/stock ROM forum here on XDA. After that I downloaded the OTA update again on my Moto Z, it starts with installing the update, then it restarts in recovery, it seems work fine when I see the stock recovery screen with installing the update, but after a few minutes I get an "Error!" with the "Android man with open belly" symbol. Luckily the phone stil boots and is working fine.
What's going wrong with the OTA update? Mismatch between the rom (MPL24.246-45) and recovery (MPL24.246-17) version?
My goal is to get stock Android 7 on my Moto Z. Who can tell me what's the best step for me to achieve this? Should I try another recovery to get the OTA update working?
Thank you!
Same happened to me when i tried updating the new 540mb update over Nougat. I think it happened because of the kernel (disabling force encryption), not sure :/
Manish54 said:
Same happened to me when i tried updating the new 540mb update over Nougat. I think it happened because of the kernel (disabling force encryption), not sure :/
Click to expand...
Click to collapse
Ok, thank you for your answer. But I did not do anything with encryption... And how did you solve this, are you able to install that update now?
I gave my phone to the service center today and told them that it happened after the OTA update. I have my fingers crossed that they don't find out about the unlocked bootloader before fixing it.
wmerbe38 said:
...
What's going wrong with the OTA update? Mismatch between the rom (MPL24.246-45) and recovery (MPL24.246-17) version?
My goal is to get stock Android 7 on my Moto Z. Who can tell me what's the best step for me to achieve this? Should I try another recovery to get the OTA update working?
Thank you!
Click to expand...
Click to collapse
Possible. Flash stock recovery from Rogers firmware which is a -45 subrelease.
Anyway I wouldn't upgrade by OTA...
enetec said:
Possible. Flash stock recovery from Rogers firmware which is a -45 subrelease.
Anyway I wouldn't upgrade by OTA...
Click to expand...
Click to collapse
Do you mean the Rogers firmware from this forum?
https://forum.xda-developers.com/moto-z/how-to/update-to-7-0-nougat-xt1650-03-retus-t3513095
wmerbe38 said:
Do you mean the Rogers firmware from this forum?
https://forum.xda-developers.com/moto-z/how-to/update-to-7-0-nougat-xt1650-03-retus-t3513095
Click to expand...
Click to collapse
Yes, that one.
enetec said:
Yes, that one.
Click to expand...
Click to collapse
Ok, I already flashed de stock .45 Recovery from Rogers.
My plan is the following:
- Reset device to factory defaults
- Download the OTA update to the device, just how it's meant to be
- See if it wil update successfully now
Or what can you recommend me to get to fully stock Nougat? This one:
https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342
Or wait and stay on Android 6.0.1 till there is more information/ROM's/updates about this device? I know something about flashing/ROM's (before I had a OnePlus One with Cyanogen) but not as much as you guys do and I don't want to brick my device
wmerbe38 said:
Ok, I already flashed de stock .45 Recovery from Rogers.
My plan is the following:
- Reset device to factory defaults
- Download the OTA update to the device, just how it's meant to be
- See if it wil update successfully now
Or what can you recommend me to get to fully stock Nougat? This one:
https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342
Or wait and stay on Android 6.0.1 till there is more information/ROM's/updates about this device? I know something about flashing/ROM's (before I had a OnePlus One with Cyanogen) but not as much as you guys do and I don't want to brick my device
Click to expand...
Click to collapse
Second choice is the (safe...) way to go...
Hello All
I would really appreciate the help on my situation.
I have bought a new motherboard from aliexpress. and it turns out the board is a VS990 with H901 5.1 installed on it.
Its working like a charm now I received the OTA update to android 6 but I am very scared to go ahead with the update as it will most probably brick the phone. Has anyone experienced same situation? Do i go ahead and let it do the OTA update? If not is there anyway I can install Nugget on my (Half / Half) setup ?
I will very much appreciate the help please.
Thanks
ramyboy said:
Hello All
I would really appreciate the help on my situation.
I have bought a new motherboard from aliexpress. and it turns out the board is a VS990 with H901 5.1 installed on it.
Its working like a charm now I received the OTA update to android 6 but I am very scared to go ahead with the update as it will most probably brick the phone. Has anyone experienced same situation? Do i go ahead and let it do the OTA update? If not is there anyway I can install Nugget on my (Half / Half) setup ?
I will very much appreciate the help please
Thanks
Click to expand...
Click to collapse
hi
before you install the update, check weather is rooted or not, if rooted update will stop, otherwise it will update the phone, i'm having att phone i updated manually, update was messed up my phone, now phone its 6.0 but errors on my phone, if you are not sure what you doing, please don't updated.
jurneybegin said:
hi
before you install the update, check weather is rooted or not, if rooted update will stop, otherwise it will update the phone, i'm having att phone i updated manually, update was messed up my phone, now phone its 6.0 but errors on my phone, if you are not sure what you doing, please don't updated.
Click to expand...
Click to collapse
Thank you but my issue is not work root. My phone it's not rooted. My board is a VS900 verizon board but the FW is t mobile. That is why i am worried to accept the OTA.
ramyboy said:
Hello All
I would really appreciate the help on my situation.
I have bought a new motherboard from aliexpress. and it turns out the board is a VS990 with H901 5.1 installed on it.
Its working like a charm now I received the OTA update to android 6 but I am very scared to go ahead with the update as it will most probably brick the phone. Has anyone experienced same situation? Do i go ahead and let it do the OTA update? If not is there anyway I can install Nugget on my (Half / Half) setup ?
I will very much appreciate the help please.
Thanks
Click to expand...
Click to collapse
These posts should help you, I also thought I was in your boat until I searched my whole motherboard.
https://forum.xda-developers.com/tm...k-h901-f600l-board-2017-t3635697/post75788253
https://forum.xda-developers.com/tm...k-h901-f600l-board-2017-t3635697/post75799801
My motherboard also had vs990 printed on it but the "t" link is soldered. So my v10 is a h901, which makes sense since I bought mine from my local T-Mobile store right after release.
If you plan on rooting do not take the ota. It is much easier to root on 5.1 (10c), the fastboot commands are still intact. All updates after 5.1 get more difficult to root. Once rooted there is twrp flashable .zip in the development forum to safely bring you to the latest 7.0 update (30c) and is also a full firmware update.
Sent from my Moto Z (2) using XDA Labs
skywalker-live said:
These posts should help you, I also thought I was in your boat until I searched my whole motherboard.
https://forum.xda-developers.com/tm...k-h901-f600l-board-2017-t3635697/post75788253
https://forum.xda-developers.com/tm...k-h901-f600l-board-2017-t3635697/post75799801
My motherboard also had vs990 printed on it but the "t" link is soldered. So my v10 is a h901, which makes sense since I bought mine from my local T-Mobile store right after release.
If you plan on rooting do not take the ota. It is much easier to root on 5.1 (10c), the fastboot commands are still intact. All updates after 5.1 get more difficult to root. Once rooted there is twrp flashable .zip in the development forum to safely bring you to the latest 7.0 update (30c) and is also a full firmware update.
Sent from my Moto Z (2) using XDA Labs
Click to expand...
Click to collapse
Man you are a life saver.. I have just unlocked my bootloader. Now where is that forum with the TWRP Nugget Please???
ramyboy said:
Man you are a life saver.. I have just unlocked my bootloader. Now where is that forum with the TWRP Nugget Please???
Click to expand...
Click to collapse
Did you take apart your phone and verify your soldered link?
Do you have twrp 3.2.1 installed?
All the info you need can be found https://forum.xda-developers.com/tmobile-lg-v10/development
Reading about anything you plan to do will help prevent a brick.
To install twrp
'fasboot flash recovery <twrp.img>' (extract .img from .zip) https://androidfilehost.com/?fid=818070582850501883
Linked from https://forum.xda-developers.com/tmobile-lg-v10/development/twrp-3-2-1-h901-t3765971
'reboot recovery'
From twrp flash this .zip (firmware)
https://drive.google.com/file/d/0Bz7RQirmMu9MZHNSc3hjRTF3X0U
Linked from
https://forum.xda-developers.com/tmobile-lg-v10/development/h901-t-mobile-nougat-v30b-twrp-t3639203
Then flash this .zip (30c update)
https://androidfilehost.com/?fid=673956719939821713
Linked from
https://forum.xda-developers.com/tm.../h901-t-mobile-nougat-v30c-flashable-t3744648
Then flash magisk 16.0 (current stable version) for root. Done.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Read all threads I linked, some parts of them are old and have been superseded but will still provide valuable info that should prevent a brick.
Sent from my Moto Z (2) using XDA Labs
skywalker-live said:
Did you take apart your phone and verify your soldered link?
Do you have twrp 3.2.1 installed?
All the info you need can be found https://forum.xda-developers.com/tmobile-lg-v10/development
Reading about anything you plan to do will help prevent a brick.
To install twrp
'fasboot flash recovery <twrp.img>' (extract .img from .zip) https://androidfilehost.com/?fid=818070582850501883
Linked from https://forum.xda-developers.com/tmobile-lg-v10/development/twrp-3-2-1-h901-t3765971
'reboot recovery'
From twrp flash this .zip (firmware)
https://drive.google.com/file/d/0Bz7RQirmMu9MZHNSc3hjRTF3X0U
Linked from
https://forum.xda-developers.com/tmobile-lg-v10/development/h901-t-mobile-nougat-v30b-twrp-t3639203
Then flash this .zip (30c update)
https://androidfilehost.com/?fid=673956719939821713
Linked from
https://forum.xda-developers.com/tm.../h901-t-mobile-nougat-v30c-flashable-t3744648
Then flash magisk 16.0 (current stable version) for root. Done.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Read all threads I linked, some parts of them are old and have been superseded but will still provide valuable info that should prevent a brick.
Sent from my Moto Z (2) using XDA Labs
Click to expand...
Click to collapse
That is great.. I will read them all very carefully and I will try to do it tommorrow.
2 points :
First I have already installed TWRP recovery for LG V10 H901 (File: twrp-2.8.7.1-h901.img & SuperSU v2.56 and now i am rooted.
Second I am sure now even without looking at the Link that my board is a H901 else I think the boot loader would have never been simply unlocked. Dont you agree?
ramyboy said:
That is great.. I will read them all very carefully and I will try to do it tommorrow.
2 points :
First I have already installed TWRP recovery for LG V10 H901 (File: twrp-2.8.7.1-h901.img & SuperSU v2.56 and now i am rooted.
Second I am sure now even without looking at the Link that my board is a H901 else I think the boot loader would have never been simply unlocked. Dont you agree?
Click to expand...
Click to collapse
SuperSU is abandoned. TWRP 2.8.7.1 can't flash nougat, you'll need to upgrade to the 3.2.1 I linked but will only have to flash the .zip from TWRP. SuperSU will get removed when you flash the system updates so then you should have no problem installing magisk, just do a factory reset in TWRP after you do the updates before magisk to remove and data from SuperSU that my be left.
Your 2nd point is dead on, the h901 is the only US carrier branded v10 that can be bootloader unlocked. True vs990's were locked down tight in true Verizon fashion.
Sent from my Moto Z (2) using XDA Labs
Looking the posts you shared i understand that i cant upgrade 5.1 directly to nugget.. Corrent me if i am wrong. If not then which 6.0 should i flash using rtwp? And can i upgrade instead of wiping over the rooted 5.1? I would love to keep my apps and setting.
ramyboy said:
Looking the posts you shared i understand that i cant upgrade 5.1 directly to nugget.. Corrent me if i am wrong. If not then which 6.0 should i flash using rtwp? And can i upgrade instead of wiping over the rooted 5.1? I would love to keep my apps and setting.
Click to expand...
Click to collapse
That's the point of these twrp flashable updates, to update without wipeing . For the Android 6.0 updates use the part 1 (firmware) and part 2 (system, boot) 20L files in this thread.
https://forum.xda-developers.com/tmobile-lg-v10/development/rom-v10h901v20estock-customized-t3360240
It is still heavily suggested to wipe when changing major Android versions. Minor updates within the same version don't cause too much trouble, but data structure varies between major version updates. All this being said some people don't have problems with dirty (no wipe) flashes.
Sent from my Moto Z (2) using XDA Labs
skywalker-live said:
That's the point of these twrp flashable updates, to update without wipeing . For the Android 6.0 updates use the part 1 (firmware) and part 2 (system, boot) 20L files in this thread.
https://forum.xda-developers.com/tmobile-lg-v10/development/rom-v10h901v20estock-customized-t3360240
It is still heavily suggested to wipe when changing major Android versions. Minor updates within the same version don't cause too much trouble, but data structure varies between major version updates. All this being said some people don't have problems with dirty (no wipe) flashes.
Sent from my Moto Z (2) using XDA Labs
Click to expand...
Click to collapse
I dont understand why this happened . I followed the exact steps .. Downloaded Part 1 L and Part 2 L
Flashed part 1 with TWRP and did not reboot. Then flashed Part 2.. Then rebooted.. Now my phone doesnt even turn on.
This must be a hard brick.. I cant even go into TWRP any more .. and no logo appears.. the phone is detected on PC as QSUSB_BULK
ramyboy said:
I dont understand why this happened . I followed the exact steps .. Downloaded Part 1 L and Part 2 L
Flashed part 1 with TWRP and did not reboot. Then flashed Part 2.. Then rebooted.. Now my phone doesnt even turn on.
This must be a hard brick.. I cant even go into TWRP any more .. and no logo appears.. the phone is detected on PC as QSUSB_BULK
Click to expand...
Click to collapse
There are a few threads that discuss recovering from bricked 20J software that you could try. (20L is said to be the only software that can downgrade, but only to 20J) Most people had LG do warranty exchange. This is the frustrating part of LG phones, how easy LG made it to brick if you didn't fully read up on what you were doing.
Sent from my Moto Z (2) using XDA Labs
hi. can anyone help me to fix my phone after update to MM 6.0, having errors LG vpn has stopped, finger print not working n and can't uninstall any program its reboot itself, I'm using ATT phone had 5.1 LP, motherboard is board is a VS990
im looking correct firmware to correct these errors on MM or upgrade to 7.0?
Please help me
skywalker-live said:
There are a few threads that discuss recovering from bricked 20J software that you could try. (20L is said to be the only software that can downgrade, but only to 20J) Most people had LG do warranty exchange. This is the frustrating part of LG phones, how easy LG made it to brick if you didn't fully read up on what you were doing.
Sent from my Moto Z (2) using XDA Labs
Click to expand...
Click to collapse
Hi Skywalker
I tried the image sd card method provided by tungkick and i could go to download mode. I uses 20j tot and flashed succesfully but phone keeps looping lg logo and verdication fail message in red.. you think this the wrong firmware? Whats the next step?
ramyboy said:
Hi Skywalker
I tried the image sd card method provided by tungkick and i could go to download mode. I uses 20j tot and flashed succesfully but phone keeps looping lg logo and verdication fail message in red.. you think this the wrong firmware? Whats the next step?
Click to expand...
Click to collapse
The unbricking thread should have some input on that problem, just search for it.
Sent from my Moto Z (2) using XDA Labs