I have my bootloader unlocked and the phone is rooted, but I'm on the stock Verizon ROM. Any warnings/issues known with updating from NDE63P? Thanks!
No problems here. I've installed the last three versions of WETA on mine.
spotmark said:
No problems here. I've installed the last three versions of WETA on mine.
Click to expand...
Click to collapse
Hi, sorry for the newbie question but I only got my pixel XL yesterday...WETA?
smokeydriver said:
Hi, sorry for the newbie question but I only got my pixel XL yesterday...WETA?
Click to expand...
Click to collapse
Custom ROM, in the development section.
smokeydriver said:
I have my bootloader unlocked and the phone is rooted, but I'm on the stock Verizon ROM. Any warnings/issues known with updating from NDE63P? Thanks!
Click to expand...
Click to collapse
The consensus seems to be that as long as bootloader is unlocked a firmware update can't relock it. I asked this question, and someone explained that Verizon would have to specifically ask Google to come up with something in an update that relocked the bootloader, which is highly unlikely. You should be able to update without any fear of any issues.
theycallmerayj said:
The consensus seems to be that as long as bootloader is unlocked a firmware update can't relock it. I asked this question, and someone explained that Verizon would have to specifically ask Google to come up with something in an update that relocked the bootloader, which is highly unlikely. You should be able to update without any fear of any issues.
Click to expand...
Click to collapse
So doing the OTA update to 7.1.1 is good to go? I did unlock it and root it. Just got the update last night. It is a Verizon phone. Loving it so far as an honest opinion.
Landancer30 said:
So doing the OTA update to 7.1.1 is good to go? I did unlock it and root it. Just got the update last night. It is a Verizon phone. Loving it so far as an honest opinion.
Click to expand...
Click to collapse
Yeah, I'm on the latest update and still unlocked and root. The biggest issue is if you ever have to get a replacement through insurance the unlock method was patched in the latest update, but as long as you're already unlocked and don't relock you're good to go.
Related
I have recently purchased an HTC One for verizon and was thinking about rooting it and unlocking it.....my question is I just recently updated to the 4.3 OTA update and I am wondering if I can still root it and unlock it or do I have to wait for a tool to do so?
JSDragon said:
I have recently purchased an HTC One for verizon and was thinking about rooting it and unlocking it.....my question is I just recently updated to the 4.3 OTA update and I am wondering if I can still root it and unlock it or do I have to wait for a tool to do so?
Click to expand...
Click to collapse
I just got a new One with 4.3 also. We're stuck with s-on for now.
mmuzzy said:
I just got a new One with 4.3 also. We're stuck with s-on for now.
Click to expand...
Click to collapse
Sad face ok thank you for the reply and for your time
Does anyone know if the tool to hack the HTC One will be updated for the 4.3 update by chance?
JSDragon said:
Does anyone know if the tool to hack the HTC One will be updated for the 4.3 update by chance?
Click to expand...
Click to collapse
You can wait, or ask beaups, but ETA is kinda rude to some ppl.
on 4.3
I was s-off so not sure this will work for you but what i did was i needed to write a super cid of 1111111 then went to htcdev and got unlock code and unlocked then wrote my regular cid back there are instructions on xda then i had to use fastboot to install custom boot and root again because i lost adb for some unknown reason.
i have to go to work if you want i'll post all the links i used tonight
Yeah I will wait and be patient I am sure being a program developer its annoying when people wine for updates to their programs.
bregga said:
I was s-off so not sure this will work for you but what i did was i needed to write a super cid of 1111111 then went to htcdev and got unlock code and unlocked then wrote my regular cid back there are instructions on xda then i had to use fastboot to install custom boot and root again because i lost adb for some unknown reason.
i have to go to work if you want i'll post all the links i used tonight
Click to expand...
Click to collapse
You have to be S-Off to write the cid to 11111111. If you try to do it without S-OFF the phone just freezes.
So i was thinking about trading my Galaxy S4 out for a HTC one because it seems the only phone getting dev support and not fubar from verizon. If i got a new one today would i be able to root and flash roms right away or is there a possibility of new update blocking it.
lightnx said:
So i was thinking about trading my Galaxy S4 out for a HTC one because it seems the only phone getting dev support and not fubar from verizon. If i got a new one today would i be able to root and flash roms right away or is there a possibility of new update blocking it.
Click to expand...
Click to collapse
There is a 4.3 update that will block you from flashing roms. It will likely pop the moment you turn the phone on so stay alert for that.
I got my phone directly through Verizons concession line about a week ago.
vpxf said:
There is a 4.3 update that will block you from flashing roms. It will likely pop the moment you turn the phone on so stay alert for that.
Click to expand...
Click to collapse
Or ask the seller to provide you with the build number and version. I did that before I bought my One but unfortunately the guy updated it to 4.3 before shipping it out
Take it not to take an update is the question. Unlocked bootloader just worried it will f up something.
kitila said:
Take it not to take an update is the question. Unlocked bootloader just worried it will f up something.
Click to expand...
Click to collapse
Hello...
Bootloader unlocked or not, it doesn't matter in case you want to update via OTA. If you are on stock firmware, you are good to go... :good:
5.1 said:
Hello...
Bootloader unlocked or not, it doesn't matter in case you want to update via OTA. If you are on stock firmware, you are good to go... :good:
Click to expand...
Click to collapse
That is what I thought just wanted to double-check because these damn pixels seem like they have went the way of Apple
Hi. Im new here so please help me.
I have a Moto Z Play XT1635-02 on 7.0 with the 1st May Patch installed.
I unlocked the bootloader to root this device.
I rooted with this:
https://forum.xda-developers.com/moto-z-play/how-to/correct-rooting-moto-z-play-feb-17-t3560268
Now i want to go back to stock firmware to accept the OTA i just recieved for 7.1.1.
My main query is that, i have RETGB device and its on build number NPN25.137-24.3
I can't find any firmware for RETGB software channel.
I did find the OTA for this, which i have downloaded through the moto ota link generator tool by erfanoabdi.
Now, can any one guide me on how to restore stock without messing up my device?
I have downloaded two retail firmwares:
1)XT1635-02_ADDISON_7.0_NPNS25.137-24-1-9_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
2)XT1635-02_ADDISON_7.0_NPNS25.137-24-1-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Is it safe to flash any of these on my May patched device or should i somehow find the may patched firmware?
Waiting for your kind replies! :')
sheri.khan said:
Hi. Im new here so please help me.
I have a Moto Z Play XT1635-02 on 7.0 with the 1st May Patch installed.
I unlocked the bootloader to root this device.
I rooted with this:
https://forum.xda-developers.com/moto-z-play/how-to/correct-rooting-moto-z-play-feb-17-t3560268
Now i want to go back to stock firmware to accept the OTA i just recieved for 7.1.1.
My main query is that, i have RETGB device and its on build number NPN25.137-24.3
I can't find any firmware for RETGB software channel.
I did find the OTA for this, which i have downloaded through the moto ota link generator tool by erfanoabdi.
Now, can any one guide me on how to restore stock without messing up my device?
I have downloaded two retail firmwares:
1)XT1635-02_ADDISON_7.0_NPNS25.137-24-1-9_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
2)XT1635-02_ADDISON_7.0_NPNS25.137-24-1-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Is it safe to flash any of these on my May patched device or should i somehow find the may patched firmware?
Waiting for your kind replies! :')
Click to expand...
Click to collapse
Just flash the below link and you will be on 7.1.1, and yes it is that simple.
https://forum.xda-developers.com/moto-z-play/development/rom-single-dual-sim-t3620551
Jimi Mack said:
Just flash the below link and you will be on 7.1.1, and yes it is that simple.
https://forum.xda-developers.com/moto-z-play/development/rom-single-dual-sim-t3620551
Click to expand...
Click to collapse
Thank you!
I should flash this through TWRP?
Also after flashing this, the future OTA updates(If any) will be installed without any problems on my retgb channel?
sheri.khan said:
Thank you!
I should flash this through TWRP?
Also after flashing this, the future OTA updates(If any) will be installed without any problems on my retgb channel?
Click to expand...
Click to collapse
Yes on TWRP no on future updates.. being there is not official release for you. Plus the next major update if it happens would not be till O is released which we would not see till way after the new year.
Once you unlock bootloader and root, no going back...
Jimi Mack said:
Yes on TWRP no on future updates.. being there is not official release for you. Plus the next major update if it happens would not be till O is released which we would not see till way after the new year.
Once you unlock bootloader and root, no going back...
Click to expand...
Click to collapse
Thanks brother.
I don't seem to get why the RETGB firmware isn't released.
I literally can't find anyone except i guess two or just 3 people who have the same software channel.
Thanks again!
On the Verizon blackberry priv, there was a way to install the ROM with no Verizon bloatware, no rooting or anything.
Same with my T-Mobile s7 edge, is there something for the Verizon moto z play?
jzamalot said:
On the Verizon blackberry priv, there was a way to install the ROM with no Verizon bloatware, no rooting or anything.
Same with my T-Mobile s7 edge, is there something for the Verizon moto z play?
Click to expand...
Click to collapse
I don't think that its possible with the Verizon MZP.
There's no access for anyone to unlock its bootloader as of yet.
So there's no development for it either.
But who knows? Don't lose the hope! :'D
sheri.khan said:
I don't think that its possible with the Verizon MZP.
There's no access for anyone to unlock its bootloader as of yet.
So there's no development for it either.
But who knows? Don't lose the hope! :'D
Click to expand...
Click to collapse
Thanks, just wondering because the blackberry priv bootloader was also never unlocked or ever rooted
I had this phone rooted and unlocked when it was 5.0.1.
my brother upgraded it to 6.0.1 N910VVRU2CQF2 by mistake.
Can I root and unlock the bootloader again?
Thank you
mrme12 said:
I had this phone rooted and unlocked when it was 5.0.1.
my brother upgraded it to 6.0.1 N910VVRU2CQF2 by mistake.
Can I root and unlock the bootloader again?
Thank you
Click to expand...
Click to collapse
I personally have no clue, but from what I do know, when I upgraded from 5.1.1 to 6.0.1 or whatever it is/was, I had to do the rooting/unlocking process again. We all did. Have you even tried it? If so, are you getting any errors? I noticed that hsbadr's thread on stock ROMs isn't updated to this version, yet. You might want to wait around for someone to give you a more firm answer. I'm just giving you food for thought.
https://forum.xda-developers.com/no...mware-firmware-kernel-modem-recovery-t2942937
EDIT: Maybe this thread will help you. It's actually updated to CQI2, so "maybe" you're good to go. - https://forum.xda-developers.com/no...t/howto-bootloader-unlock-upgrade-to-t3398144
I am a bit confused by all the posts about this subject
I would like to unlock my phone, for future rooting, when everything is more stable, meanwhile I want to get OTA updates on the phone "automaticaly", is that possible
You can definitely unlock the bootloader and still receive OTA.
And for your first point, rooting is plenty stable already, so no need to wait for that. Though if you aren't well versed in fastboot or root upgrade processes, you should definitely read all the most recent guides on it to make your transition smoother.
Thank you :good:
I did my share of rooting with Samsung S1, S3 and S5
Then bougth an LG V10, had to buy a "IMAGE" from a Chinese guy, using Alibaba "paypal" in chinese, to be able to activate LTE 20
Have been quiet for a couple of years, and didnt really have the need to root to have the V10 doing what I wanted, but want to be able to root if I have too much free time
melorib said:
Thank you :good:
I did my share of rooting with Samsung S1, S3 and S5
Then bougth an LG V10, had to buy a "IMAGE" from a Chinese guy, using Alibaba "paypal" in chinese, to be able to activate LTE 20
Have been quiet for a couple of years, and didnt really have the need to root to have the V10 doing what I wanted, but want to be able to root if I have too much free time
Click to expand...
Click to collapse
You will probably find this less confusing than Odin. But you need to read up on using latest SDK, adb, fastboot, etc.
We're now using Magisk to root and be able to use Paypal.
wtherrell said:
You will probably find this less confusing than Odin. But you need to read up on using latest SDK, adb, fastboot, etc.
We're now using Magisk to root and be able to use Paypal.
Click to expand...
Click to collapse
Thanks, I work with IT, and already used adb to enable LTE frequencies on my LG V10. And of course I have been reading about Magisk, but will wait for more stable versions
melorib said:
Thanks, I work with IT, and already used adb to enable LTE frequencies on my LG V10. And of course I have been reading about Magisk, but will wait for more stable versions
Click to expand...
Click to collapse
There's issues with Magisk and some other phones, but topjohnwu has a Pixel 2 I believe, so he tests on that.
Magisk for our phones is perfectly stable, the only issue is people don't like the dtbo image being edited to remove AVB 2.0/dm-verity.
My bootloader is unlocked on my XL 2 and I am on Verizon. I have yet to get the January OTA. I haven't gotten an OTA since I got the phone in October
canemaxx said:
My bootloader is unlocked on my XL 2 and I am on Verizon. I have yet to get the January OTA. I haven't gotten an OTA since I got the phone in October
Click to expand...
Click to collapse
Strange, there was at least an update in January
Nov, Dec and January .....I have had to flash the full image if all 3. No OTA has ever come to this device
canemaxx said:
Nov, Dec and January .....I have had to flash the full image if all 3. No OTA has ever come to this device
Click to expand...
Click to collapse
Why? I want OTA updates...
I'm not sure why they just have not come to my phone.
canemaxx said:
I'm not sure why they just have not come to my phone.
Click to expand...
Click to collapse
You only unlocked the bootloader? Maybe because it is Verizon, the bootloader is supposed to to be locked!
I can't see that being the reason as I bought the phone from the Google store
canemaxx said:
I can't see that being the reason as I bought the phone from the Google store
Click to expand...
Click to collapse
Sounds strange, maybe you updated before OTA was available for Verizon...
In 2 weeks I get mine, going to unlock before any update, it was bought December, so it has at least one update missing...
canemaxx said:
I can't see that being the reason as I bought the phone from the Google store
Click to expand...
Click to collapse
You can buy the locked Verizon phone from the Google Store, but apparently you ordered the correct one (unlocked, carrier free). Devices on the Verizon network (both locked and unlocked) receive regular OTAs, so don't worry- the status of the bootloader has nothing to do with why your device hasn't received the update yet. The difference is having the unlocked variant, you don't have to use Verizon specific images, and you can change carriers at any time, including internationally. Usually with just a SIM card change.
The OTA updates are staged randomly and roll out over a couple of weeks. Your OTA will eventually come by itself. Sometimes people wait a month (or even longer). If you don't want to wait, then just download the OTA and sideload it. Every month, the new OTAs (and full images) are posted by Google. You are free to download and flash them. Instructions on how to do this are provided by Google at the top of the download page. You don't even need to be bootloader unlocked to sideload OTAs.
v12xke said:
You can buy the locked Verizon phone from the Google Store, but apparently you ordered the correct one (unlocked, carrier free). Devices on the Verizon network (both locked and unlocked) receive regular OTAs, so don't worry- the status of the bootloader has nothing to do with why your device hasn't received the update yet. The difference is having the unlocked variant, you don't have to use Verizon specific images, and you can change carriers at any time, including internationally. Usually with just a SIM card change.
The OTA updates are staged randomly and roll out over a couple of weeks. Your OTA will eventually come by itself. Sometimes people wait a month (or even longer). If you don't want to wait, then just download the OTA and sideload it. Every month, the new OTAs (and full images) are posted by Google. You are free to download and flash them. Instructions on how to do this are provided by Google at the top of the download page. You don't even need to be bootloader unlocked to sideload OTAs.
Click to expand...
Click to collapse
Thanks I know how to sideload or flash the full image but just was hoping I wouldn't have to again and again
Are your phones enrolled on the Android Beta Program ? My P2 was and I never got the Jan. Update till I Unenrolled from the beta program. Immediately afterwards I checked and Jan update was available.