Related
Hi!
I got an M8 a few weeks ago, and regretfully wasn't thinking and allowed a few OTA updates.
So I was at firmware version 2.22.531.5, Android 4.4.3. There were 2 other OTA updates pending that I ignored because I realized that it may make it harder to root or s-off. I realize now I already performed the updates which would make Firewater not work.
I unlocked the bootloader, and flashed TWRP 2.8.0.1, then flashed the latest SuperSU.
Now the update notices stopped.
Few questions:
1. Does anyone know what updates beyond the version above were sent OTA, and how beneficial these updates are?
2. I'll probably get sunshine...but might wait. Can I install a different ROM without S-off?
3. Since I'm at 4.4.3, I may stay with stock until 4.5 (or whatever L is). But I definitely want to get some junk off the phone. I was going to use Titanium and uninstall a bunch of stuff... I have had a few HTC phones before and could identify what apps were part of the ROM framework, but it's not as easy to discern what apps I need to keep on this phone. Does anyone know of a thread that talks about what stock apps can be uninstalled? Or, in the alternative, if you have deleted apps, can you let me know which ones?
I know that's a lot of questions... Thank you in advance for any answers!
syntropic said:
Hi!
I got an M8 a few weeks ago, and regretfully wasn't thinking and allowed a few OTA updates.
So I was at firmware version 2.22.531.5, Android 4.4.3. There were 2 other OTA updates pending that I ignored because I realized that it may make it harder to root or s-off. I realize now I already performed the updates which would make Firewater not work.
I unlocked the bootloader, and flashed TWRP 2.8.0.1, then flashed the latest SuperSU.
Now the update notices stopped.
Few questions:
1. Does anyone know what updates beyond the version above were sent OTA, and how beneficial these updates are?
2. I'll probably get sunshine...but might wait. Can I install a different ROM without S-off?
3. Since I'm at 4.4.3, I may stay with stock until 4.5 (or whatever L is). But I definitely want to get some junk off the phone. I was going to use Titanium and uninstall a bunch of stuff... I have had a few HTC phones before and could identify what apps were part of the ROM framework, but it's not as easy to discern what apps I need to keep on this phone. Does anyone know of a thread that talks about what stock apps can be uninstalled? Or, in the alternative, if you have deleted apps, can you let me know which ones?
I know that's a lot of questions... Thank you in advance for any answers!
Click to expand...
Click to collapse
1, pretty sure that's latest update
2, u can still install custom roms etc. u won't be able to downgrade firmware/change variant of m8 without s off
3, Check HERE
Thank you!
I had one follow up question...
If I had just gone with sunshine from the start (and not gone with the token from HTC to unlock the bootloader), would I have still gotten OTA updates?
Which change (custom recovery, unlocked bootloader) stops the OTA updates?
Thanks to anyone again in advance!
syntropic said:
Thank you!
I had one follow up question...
If I had just gone with sunshine from the start (and not gone with the token from HTC to unlock the bootloader), would I have still gotten OTA updates?
Which change (custom recovery, unlocked bootloader) stops the OTA updates?
Thanks to anyone again in advance!
Click to expand...
Click to collapse
you would have been fine with OTA from the start, the following stops OTA updates:
custom recovery installed
missing system apps removed
incorrect firmware etc
You can freeze apps with Titanium, and if doing so doesn't cause any issues, go ahead and uninstall.
exocetdj said:
you would have been fine with OTA from the start, the following stops OTA updates:
custom recovery installed
missing system apps removed
incorrect firmware etc
Click to expand...
Click to collapse
Ok...But before I read this, I was just going through settings and I checked the "check for updates" section, and it wants to install firmware version 2.22.531.6. So maybe if you are still using stock (despite installing custom recovery), you still get OTA updates?
The update sounds minor given it's incremental version (but tmous/HTC claims it's for important security updates), and I'd probably ignore it... But unfortunately, because I checked in the first place and perhaps because I'm on stock (minus a few apps I'm trying to delete: Amazon, Facebook, Kid Mode), for whatever reason the update reminder stays in my notifications and is pretty insistent.
Can I install this without calamity?
Thank you!
syntropic said:
Ok...But before I read this, I was just going through settings and I checked the "check for updates" section, and it wants to install firmware version 2.22.531.6. So maybe if you are still using stock (despite installing custom recovery), you still get OTA updates?
Click to expand...
Click to collapse
You will get the OTA notification just fine with custom recovery, and it will download as well. The problem is, when you go to install, OTA requires stock recovery and will fail when it doesn't find it. Might also bootloop looking for stock recovery, can't remember exactly.
redpoint73 said:
You will get the OTA notification just fine with custom recovery, and it will download as well. The problem is, when you go to install, OTA requires stock recovery and will fail when it doesn't find it. Might also bootloop looking for stock recovery, can't remember exactly.
Click to expand...
Click to collapse
Oh boy... So what's the solution? It finally downloaded on its own and is now pestering me to install. I don't want to deal with a bootloop. ****...
Can I delete the update from recovery, it just disable the updater and delete it?
What are my options? Thanks!!
syntropic said:
Oh boy... So what's the solution? It finally downloaded on its own and is now pestering me to install. I don't want to deal with a bootloop. ****...
Can I delete the update from recovery, it just disable the updater and delete it?
What are my options? Thanks!!
Click to expand...
Click to collapse
The OTA zip should be in your download folder on internal memory, delete this then uncheck auto update checking and u should be without the constant notifications.
If you want to update, u will need to reinstall a fresh nand with all stock apps included
exocetdj said:
The OTA zip should be in your download folder on internal memory, delete this then uncheck auto update checking and u should be without the constant notifications.
If you want to update, u will need to reinstall a fresh nand with all stock apps included
Click to expand...
Click to collapse
I think I'm going to do this (install nand). I am going to get sunshine/s-off, then flash fresh stock RUU... will I still need to then lock bootloader?
Could you just give me a short list of steps to do this? I want to lock bootloader with s-off because I want get the @$&)!& HTC free 100GB Google Drive promo and all the updates.
I really appreciate it Archer...
No problem
1, sunshine s off
2, Flash relevant nand/firmware
3, use this guide to stock lock (not relock) bootloader HERE
4, u will have a stock m8 with S off ready for future OTAs (remember not to remove any apps preinstalled in the nand)
not sure of the 100GB promo as i use dropbox lol :silly::highfive::good:
---------- Post added at 03:07 PM ---------- Previous post was at 03:06 PM ----------
syntropic said:
I think I'm going to do this (install nand). I am going to get sunshine/s-off, then flash fresh stock RUU... will I still need to then lock bootloader?
Could you just give me a short list of steps to do this? I want to lock bootloader with s-off because I want get the @$&)!& HTC free 100GB Google Drive promo and all the updates.
I really appreciate it Archer...
Click to expand...
Click to collapse
see above buddy
exocetdj said:
see above buddy
Click to expand...
Click to collapse
Cool... And I have read that as long as you do it that way (using echo -ne '\x00....' and not "fastboot oem lock" when in fastboot mode with adb running) you will get "***LOCKED***" back and not RELOCKED.
When it's RELOCKED Google can't confirm your information so the promo won't work...But if locked, you can do it.
Now I just have to do it all..
Thanks!!
syntropic said:
Cool... And I have read that as long as you do it that way (using echo -ne '\x00....' and not "fastboot oem lock" when in fastboot mode with adb running) you will get "***LOCKED***" back and not RELOCKED.
When it's RELOCKED Google can't confirm your information so the promo won't work...But if locked, you can do it.
Now I just have to do it all..
Thanks!!
Click to expand...
Click to collapse
U are all set dude
Krassermensch's Firmware Update Tool
My situation:
I'm too young to buy the Sunshine App to set my device S-Off but I want to update my device's firmware every time a firmware update's available. Since I compile ROMs and cannot do that via OTA updates the only acceptable way for me is to install signed firmwares in a locked bootloader. After doing that manually I thought I should write a tool that installs the right firmware for your device automatically. As I'm already running the latest firmware on my device after doing the procedure manually I cannot test if the flash part works correctly. Anyway, I achieved to read out the CID as well as the current firmware version and my tool reports that I'm running the latest firmware version I integrated for my device what's correct. So this part works well.
How the tool works:
The tool asks you if you've already installed the HTC USB drivers on your computer. If you haven't you can install it easily using my tool. After that the tool explains you how to set up your phone to be detected by the computer. Then it checks which device you have and checks which firmware's currently installed on it. Right after that the tool installs all the firmwares newer than the one that's currently installed on your phone one after another until the latest firmware my tool is shiped with runs on your device. The procedure doesn't wipe your data since signed firmware-updates are installed.
Requirements:
- An HTC 10
- A computer running windows
- An internet connection
- An unlocked bootloader
- An installed TWRP
Who is this tool for?
All the people who can't or don't want to set their device S-Off while running a non-stock ROM.
Why should I use this tool?
- It updates your firmware to the latest one available for your device automatically
- It doesn't wipe your storage
- You don't need to be S-Off
Download
https://www.androidfilehost.com/?fid=745425885120704223
When the file is downloaded just extract it on your Windows computer and run the batch file. Everything else will be explained.
Important to know
Your boot and recovery partitions will be replaced by the stock ones so after successfully updating your firmware you need to reflash TWRP as well as your Boot partition.
This process is performed automatically now. No need to do that manually.
Tools using ADB just like mine may interfere with other tools that also use ADB. Make sure all these tools are disabled.
Now I need your feedback to be able to optimize the tool! I'll add new firmwares from time to time. I'm looking forward to your reviews
GitLab
https://gitlab.com/Feulner/Firmware-Update-Tool-HTC10
If you like my work consider a donation to support me in financing computer-components which are meant to replace the defect ones in my broken PC.
If you donate you'll donate to my father who will gimme the money. Thank you really much!
This works with unsigned firmware?
Good job, though irrelevant to me
xunholyx said:
This works with unsigned firmware?
Good job, though irrelevant to me
I would guess that you would have to have matching CID and MID of course.
Click to expand...
Click to collapse
No no, not unsigned firmware. I'll explain it more detailed tomorrow or so. The tool just checks your device's CID as well as your device's current firmware version and updates it to the most current firmware version I integrated in my tool. If your firmware is very old the tool also updates again and again until you have the lässt firmware automatically.But it uses signed firmware packages. The biggest advantage is that it should work fully automatic. Try it out and let me know what you think. I go to bed now...
krassermensch said:
No no, not unsigned firmware. I'll explain it more detailed tomorrow or so. The tool just checks your device's CID as well as your device's current firmware version and updates it to the most current firmware version I integrated in my tool. If your firmware is very old the tool also updates again and again until you have the lässt firmware automatically.But it uses signed firmware packages. The biggest advantage is that it should work fully automatic. Try it out and let me know what you think. I go to bed now...
Click to expand...
Click to collapse
I'm s-off since the day after I got my phone, so.......
It sounds like a great idea. I'm sure lot of people will appreciate this. If it does work like you say, WAY better than going back to stock.
xunholyx said:
I'm s-off since the day after I got my phone, so.......
It sounds like a great idea. I'm sure lot of people will appreciate this. If it does work like you say, WAY better than going back to stock.
Click to expand...
Click to collapse
Since when do you have to go back to stock to "fastboot flash zip some_firmware.zip" (as this tool does)?
--beaups
Hm sounds good, but i wont use it until we have some more information what it actually does.
As far as i know, theres no way to just update your firmware with signed zips without partly wiping your device. I had to reflash Viper10 (or restore a nandroid backup) the last time i updated my firmware, cause boot and recovery partitions got replaced. Not completely sure if this affects stock devices, it may work there, but not for devices which are modified with a custom ROM. For this you need a NoWipe firmware from sneakyghosts thread, but these cant be flashed while s-on.
So please explain in more details what your tool does, of course when youve got your sleep .
It most likely flashes firmware zips from OTA updates since those do not wipe the device. He already said it does that, he said if you're on a very old firmware it will keep updating your firmware progressively until you're on the latest version. So if you've never updated before, and there have been three updates since then, the tool will flash the firmware zip of each OTA one after the other.
Updated the main post, hopefully everything's clear now. I need your reviews now. I'm also thinking about an automatic bootloader lock with backup solution so you don't need to lock your bootloader manually and also don't lose your data partition.
Why it doesn't work with unlocked bootloader?
CroCop18 said:
Why it doesn't work with unlocked bootloader?
Click to expand...
Click to collapse
I didn't try but normally your HTC 10 would block the installation if the bootloader is unlocked. Could you try it out and report. It's a bit hard to try it out by myself currently... It will most probably report that your new firmware's flashed but it actually will not be flashed after that if your bootloader's unlocked. If it's flashed anyway it'd be perfect since I'd not have to make a backup solution in that case. But I guess that the 10 isn't different to the M9 for example when it comes to firmware flashing. I read that you can have an unlocked bootloader if your device is S-Off but those are things I haven't been able to try out so far...
krassermensch said:
I didn't try but normally your HTC 10 would block the installation if the bootloader is unlocked. Could you try it out and report. It's a bit hard to try it out by myself currently... It will most probably report that your new firmware's flashed but it actually will not be flashed after that if your bootloader's unlocked. If it's flashed anyway it'd be perfect since I'd not have to make a backup solution in that case. But I guess that the 10 isn't different to the M9 for example when it comes to firmware flashing. I read that you can have an unlocked bootloader if your device is S-Off but those are things I haven't been able to try out so far...
Click to expand...
Click to collapse
Really? You don't know how to unlock your bootloader? You don't need S-Off for it.
This answers the question I had wondered about. How does this install OTAs with a custom recovery? It doesn't, correct?
You need to be stock for this. The first thing you do after unlocking the bootloader (which pretty much anyone here has done) is to flash a custom recovery.
This tool will only work for users who are still completely on stock.
IO would test myself, but I'm already S-Off/unlocked bootloader/custom recovery/modified firmware/custom ROM|, and I don't want to take the time to go back to stock and incrementally update the steps to see what won't work. I think as soon as you flash custom recovery, you can't use this method.
If you want to unlock your bootloader, HTC provides the method and instructions at htcdev.com
xunholyx said:
Really? You don't know how to unlock your bootloader? You don't need S-Off for it.
This answers the question I had wondered about. How does this install OTAs with a custom recovery? It doesn't, correct?
You need to be stock for this. The first thing you do after unlocking the bootloader (which pretty much anyone here has done) is to flash a custom recovery.
This tool will only work for users who are still completely on stock.
IO would test myself, but I'm already S-Off/unlocked bootloader/custom recovery/modified firmware/custom ROM|, and I don't want to take the time to go back to stock and incrementally update the steps to see what won't work. I think as soon as you flash custom recovery, you can't use this method.
If you want to unlock your bootloader, HTC provides the method and instructions at htcdev.com
Click to expand...
Click to collapse
Sure I know how to unlock a boitloader. If you watch my profile you can see I'm a ROM maintainer. I have to use custom recoveries to do that. People interpret my posts wrongly sometimes. I dunno why. Anyway, I use TWRP but after flashing a recovery or any other image file I lock my bootloader again for safety reasons. You just need to have a locked bootloader to use my tool currently... And no, u don't need to be stock. This tool just requires a locked or relocked bootloader. U can use whatever ROM u like. U just need to have a locked bootloader and my tool installs the latest firmware I integrated for your HTC 10 model. I know what I do. You should just read my posts a bit more carefully to prevent yourself from contending wrong things...
krassermensch said:
Sure I know how to unlock a boitloader. If you watch my profile you can see I'm a ROM maintainer. I have to use custom recoveries to do that. People interpret my posts wrongly sometimes. I dunno why. Anyway, I use TWRP but after flashing a recovery or any other image file I lock my bootloader again for safety reasons. You just need to have a locked bootloader to use my tool currently...
Click to expand...
Click to collapse
" I read that you can have an unlocked bootloader if your device is S-Off" quote from you
I did read it wrong. I was thinking that you meant you needed soff to unlock bootloader.\
And yes, now that I understand what you meant, with S-Off you shouldn't need to re-lock your bootloader.
xunholyx said:
" I read that you can have an unlocked bootloader if your device is S-Off" quote from you
I did read it wrong. I was thinking that you meant you needed soff to unlock bootloader.\
And yes, now that I understand what you meant, with S-Off you shouldn't need to re-lock your bootloader.
Click to expand...
Click to collapse
Yeah, dude, I think I wouldn't be able to write a batch tool with fastboot and adb if I didn't know the whole stuff. My broken Nexus 4 has teached me a lot over the last 3½ years
Just to confirm... and thanks for the tool
I have a HTC 10 and nothing has been done to it since I bought it (Stock everything) will this tool keep it that way but give me the latest OTA?
Milamber said:
Just to confirm... and thanks for the tool
I have a HTC 10 and nothing has been done to it since I bought it (Stock everything) will this tool keep it that way but give me the latest OTA?
Click to expand...
Click to collapse
You do not need this tool if you are Stock everything, unless you unlocked your bootloader.
Milamber said:
Just to confirm... and thanks for the tool
I have a HTC 10 and nothing has been done to it since I bought it (Stock everything) will this tool keep it that way but give me the latest OTA?
Click to expand...
Click to collapse
No, I could write a tool for manual OTA flashing, too, but I don't want to do that since OTAs are for stock devices which are notified about OTA updates automatically. If you want to flash OTAs quicker: there's a thread here on xda where OTA zips are shared with an explaination how to flash it manually... This tool can be used by stock device's owners but it wouldn't be necessary...
krassermensch said:
I didn't try but normally your HTC 10 would block the installation if the bootloader is unlocked. Could you try it out and report. It's a bit hard to try it out by myself currently... It will most probably report that your new firmware's flashed but it actually will not be flashed after that if your bootloader's unlocked. If it's flashed anyway it'd be perfect since I'd not have to make a backup solution in that case. But I guess that the 10 isn't different to the M9 for example when it comes to firmware flashing. I read that you can have an unlocked bootloader if your device is S-Off but those are things I haven't been able to try out so far...
Click to expand...
Click to collapse
Thanks for your explanations, now i understand your tool a bit more.
But if it only works with a locked/relocked bootloader i cant use it. Really no offense and i dont want to sound rude (!), but isnt it already a design problem? You said the tool is designed for people with non-stock ROMS, but that does imply that you have an unlocked bootloader to flash and keep your ROM and recovery up to date. To use your tool you have to relock the bootloader after flashing the ROM. But to update the ROM to a newer version you have to unlock the bootloader again via HTCDev (and loosing your data while doing this)? Sounds a bit weird to me...or did i miss something?
So which adb commands are you using? Didnt have the time to check your script yet (sorry!). Because im S-On with my bootloader unlocked an i COULD flash a signed firmware.zip i extracted from an official OTA via ADB. This wiped my boot and recovery partitions, but not data. Just had to restore the two partitions to get everything working again.
-Vulture- said:
Thanks for your explanations, now i understand your tool a bit more.
But if it only works with a locked/relocked bootloader i cant use it. Really no offense and i dont want to sound rude (!), but isnt it already a design problem? You said the tool is designed for people with non-stock ROMS, but that does imply that you have an unlocked bootloader to flash and keep your ROM and recovery up to date. To use your tool you have to relock the bootloader after flashing the ROM. But to update the ROM to a newer version you have to unlock the bootloader again via HTCDev (and loosing your data while doing this)? Sounds a bit weird to me...or did i miss something?
So which adb commands are you using? Didnt have the time to check your script yet (sorry!). Because im S-On with my bootloader unlocked an i COULD flash a signed firmware.zip i extracted from an official OTA via ADB. This wiped my boot and recovery partitions, but not data. Just had to restore the two partitions to get everything working again.
Click to expand...
Click to collapse
So you could flash the firmware-update.zip from the OTA without relocking your bootloader?
And it was really updated after that?
krassermensch said:
So you could flash the firmware-update.zip from the OTA without relocking your bootloader?
And it was really updated after that?
Click to expand...
Click to collapse
Thats what i did, bootloader was unlocked and flash successfully. I extracted the firmware.zip from an official OTA (TMOB-101) for my device and flashed it via ADB from my PC. Since the firmware.zip is signed, it can be flashed. Doesnt work with modified zips however, like the ones from sneakyghosts thread. He removed unnecessary stuff like the flash command for boot and recovery which my broke my phone initially. Thats why you need TWRP to restore them later.
As you already said with your tool, its also important here to get the right file to flash and not to skip a firmware update in between. You have to go from very old -> old -> current without skipping old.
I used the step-by-step instructions from here:
http://forum.xda-developers.com/htc-10/how-to/2016-05-27-fastboot-flashing-firmware-t3387520
Hi,
I was reading the threads about upgrading / unlocking the bootloaders.
After spending almost half day rooting and rerooting, I have a few questions.
Right now I am on BPA1, rooted, stock. In order to install an Marshmallow ROM, it looks like I have to upgrade the bootloader, to minimum CPD1. Here it gets confusing. I already changed the CID to developer and the bootloader is unlocked. If I try to upgrade:
1. Can I flash just the bootloader (and eventually the modem) and not the entire stock firmware?
2. Will I lose root? If yes, I have to reroot, but the rooting tools are kind on unreliable, spent a lot of time already, no guarantee they will work again...In order to push the files for bootloader unlock, root is required. Is there a way to keep root? Flashing the stock firmware seems to lock the bootloader and eliminate root, so every time something needs to be upgraded, we have to go through the same process?
3. At this point, it looks that there are so many updates: CPD, CPF, CPG, CPJ, that I need a CPR if I have to repeat the process 4 times! Some roms don't require the latest update, but if it installed, will it work? E.g. the rom requires CPF and I upgrade to CPJ, what happens?
Thanks!
razvu said:
Hi,
I was reading the threads about upgrading / unlocking the bootloaders.
After spending almost half day rooting and rerooting, I have a few questions.
Right now I am on BPA1, rooted, stock. In order to install an Marshmallow ROM, it looks like I have to upgrade the bootloader, to minimum CPD1. Here it gets confusing. I already changed the CID to developer and the bootloader is unlocked. If I try to upgrade:
1. Can I flash just the bootloader (and eventually the modem) and not the entire stock firmware?
2. Will I lose root? If yes, I have to reroot, but the rooting tools are kind on unreliable, spent a lot of time already, no guarantee they will work again...In order to push the files for bootloader unlock, root is required. Is there a way to keep root? Flashing the stock firmware seems to lock the bootloader and eliminate root, so every time something needs to be upgraded, we have to go through the same process?
3. At this point, it looks that there are so many updates: CPD, CPF, CPG, CPJ, that I need a CPR if I have to repeat the process 4 times! Some roms don't require the latest update, but if it installed, will it work? E.g. the rom requires CPF and I upgrade to CPJ, what happens?
Thanks!
Click to expand...
Click to collapse
Yeah it definitely gets a little confusing, but I might be able to clear up a few of your questions. The bootloader you want to upgrade to is the cpd1 version, after that the only things that change when you upgrade to pf3, pg2, and pj1 are the kernels and modems. Right now I'm using the latest pj1 firmware and my bootloader has never changed from cpd1 and flashed between the different versions several times and for unlocking the bootloader on 6.0 you do have to repeat the process you did for lp, unfortunately.
kevintm78 said:
Yeah it definitely gets a little confusing, but I might be able to clear up a few of your questions. The bootloader you want to upgrade to is the cpd1 version, after that the only things that change when you upgrade to pf3, pg2, and pj1 are the kernels and modems. Right now I'm using the latest pj1 firmware and my bootloader has never changed from cpd1 and flashed between the different versions several times and for unlocking the bootloader on 6.0 you do have to repeat the process you did for lp, unfortunately.
Click to expand...
Click to collapse
OK, so what file do I need to download and flash? I have to unloack the CPD1 bootloader and reroot? Which app? Kingroot or Kingoroot?
Once this is updated, how can I upgrade the modems and kernels, can I flash them individually?
Thanks!
razvu said:
OK, so what file do I need to download and flash? I have to unloack the CPD1 bootloader and reroot? Which app? Kingroot or Kingoroot?
Once this is updated, how can I upgrade the modems and kernels, can I flash them individually?
Thanks!
Click to expand...
Click to collapse
These are excellent questions that I'm sure a lot of members are thinking, but just haven't formally asked.
I have a Developer Device that I got directly from a Samsung 2 years ago. When hsbadr put out CM 14.1, I was still on Android 5.1.1. It seemed like a daunting task to do all that was required to get to CM 14.1, but I went ahead with it. I decided that it just made more sense to have my device CID changed to the one that everyone else was on, so I went through all the motions. Yes, the root thing was very touchy. But it really wasn't all that bad.
I'm now on bootloader CPD1, and just today upgraded the baseband by odin flashing the partial firmware for CPJ2 baseband.
Can't wait for hsbadr's next build!!!!
Ok, so in conclusion, which file needs to be flashed to upgrade to CPD1? Is it a stock tar, or the bootloader can be flashed just by itself? After flashing I'm gonna lose root again and have to start over before changing the CID?
You mentioned that you have a developer edition. I have one developer and one retail. My developer is still on an older Jasmine, but it needs to sent for repair. I'm trying to get the retail one done, so I can use it in the meantime. Then, the plan is to get the same thing done on the developer edition. I was hoping that would be easier, as the bootloader is unlocked, but apparently that's not the case.
Sent from my SM-N910V using XDA Free mobile app
Nobody can recommend the right file to flash?
Sent from my SM-N910V using XDA Free mobile app
I am also looking for advice on how to upgrade the bootloader. I am on BPA1 currently but everything I find keeps upgrading everything but the bootloader.
Thanks in advance for any help you can provide.
So I might have gotten a nice stroke of luck here. Got a Pixel XL from Verizon with no intentions to do any modifying of any kind. I took the OTA update to 7.1.1. A few weeks later, I finally dove into the forums to see what kinda development we got going for this phone. I read that the bootloader is forever locked. Since buying the phone, I had tons of freezes, crashes, and reboots. I sent the phone in to Verizon and got my replacement with 7.1! I unlocked the bootloader and I couldn't hold true to my initial plans of not modifying it. Currently I have a Verizon Pixel XL, bootloader is unlocked, twrp, franco r6 kernel, root. On build NMF26O. What is the best/quickest method for updating with these monthly security patches and such?
https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886
Step 9
joooe said:
https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886
Step 9
Click to expand...
Click to collapse
Either I'm going crazy or just plain dumb, but there's only 8 steps when I go to that link
jdpro22 said:
Either I'm going crazy or just plain dumb, but there's only 8 steps when I go to that link
Click to expand...
Click to collapse
You are right LOL. There is no Step 9 :laugh:
I myself am not clear yet, but I think you need to flash stock recovery and kernel and then you could take the OTA update and install it. That will be the easiest. But I always like to do it clean, so I download the OTA and then sideload it via ADB. Obviously I take a backup before and then restore it.
But just make sure that there is a way to restore stock recovery, I am not clear about that part, stock boot.img is easy to find and flash, I don't know whether that restores the stock recovery too or not.
Start at step 4 here: https://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478
Just remember to delete "-w" from flash-all.bat so your data is not wiped!
I have a Verizon Pixel XL with unlocked bootloader, TWRP, and root on NHG47K. I have been updating it via sideloading the OTAs since I got the phone. I've seen on the forums that a lot of people flash the full factory image. I wanted to know what the difference was between sideloading the OTA vs flashing the full factory image?
There is not too much difference,
OTA is changing only what has been changed, size varies with 100 MB to 600 MB of more. But if you had some problems with unchanged partitions they may not fixed.
Factory image flashing has bigger size (latest is 1.8 GB), wiping your data by default (manually editing for non wipe is possible), mainly for fresh start even without wiping data.
Thanks for the info. Couple more questions:
1. Does sideloading just the OTA, flip the active slot?
2. Is there a way to check if the April OTA updated the bootloader as well. I'm guessing the May OTA does update the bootloader since applying it has broken TWRP and root for people.
savi0 said:
Thanks for the info. Couple more questions:
1. Does sideloading just the OTA, flip the active slot?
2. Is there a way to check if the April OTA updated the bootloader as well. I'm guessing the May OTA does update the bootloader since applying it has broken TWRP and root for people.
Click to expand...
Click to collapse
Hello,
1 - OTA will install on the other slot.
2 - International April version has the same bootloader as March and earlier versions. There is an updated bootloader for Verizon, not the one that breaks Root/TWRP by the way. The May OTA does brake Root/TWRP.
Cheers...
5.1 said:
Hello,
1 - OTA will install on the other slot.
2 - International April version has the same bootloader as March and earlier versions. There is an updated bootloader for Verizon, not the one that breaks Root/TWRP by the way. The May OTA does brake Root/TWRP.
Cheers...
Click to expand...
Click to collapse
To clarify your meaning... The May Verizon OTA does or does not break root?
sliding_billy said:
To clarify your meaning... The May Verizon OTA does or does not break root?
Click to expand...
Click to collapse
Hello,
Every May releases break Root. It's a general security patch for Pixel devices (as far as I understand).
Cheers...
sliding_billy said:
To clarify your meaning... The May Verizon OTA does or does not break root?
Click to expand...
Click to collapse
Applying the OTA or flashing a full factory image does "break" root and TWRP in the sense that you have to reflash TWRP and apply root again. Apparently the May factory image/OTA is applying a new bootloader which is not allowing the re-application of TWRP and root after flashing. Chainfire made a post detailing that it was due to the new May bootloader detecting an unsigned image, ie TWRP, and then not allowing it to boot.
Here is the link to that post: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
savi0 said:
Applying the OTA or flashing a full factory image does "break" root and TWRP in the sense that you have to reflash TWRP and apply root again.
Click to expand...
Click to collapse
Hello,
If you try to reinstall Root or TWRP after May OTA I think you are going to have a bad surprise. It's up to you...
savi0 said:
Apparently the May factory image/OTA is applying a new bootloader which is not allowing the re-application of TWRP and root after flashing. Chainfire made a post detailing that it was due to the new May bootloader detecting an unsigned image, ie TWRP, and then not allowing it to boot.
Here is the link to that post: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Click to expand...
Click to collapse
First you say you have to reapply TWRP and Root and now you say it won't allow it... You shouldn't reinstall either TWRP or Root on May bootloader for the moment.
If you want those, flash the April bootloader as stated in other threads talking about the issue...
Cheers...
5.1 said:
First you say you have to reapply TWRP and Root and now you say it won't allow it... You shouldn't reinstall either TWRP or Root on May bootloader for the moment.
If you want those, flash the April bootloader as stated in other threads talking about the issue...
Cheers...
Click to expand...
Click to collapse
Sorry, I should have clarified that you are only able to apply TWRP and root to images and bootloaders that were released before the May updates.
You are absolutely right in that that I should not be installing TWRP or Root on the May bootloader because it'll result in bootloops.
savi0 said:
Sorry, I should have clarified that you are only able to apply TWRP and root to images and bootloaders that were released before the May updates.
You are absolutely right in that that I should not be installing TWRP or Root on the May bootloader because it'll result in bootloops.
Click to expand...
Click to collapse
Hey,
As a workaround, you can flash April bootloader. It's not a big deal and works fine anyway.
Cheers...
5.1 said:
Hello,
Every May releases break Root. It's a general security patch for Pixel devices (as far as I understand).
Cheers...
Click to expand...
Click to collapse
That's what I assumed you meant (that the new BL was in all May builds), but your working sounded like maybe it was left out of the Verizon OTA build. I'm just waiting patiently for a TWRP/SU build that doesn't need me to mismatch the BL. It wasn't like there was any functional reason to upgrade in May.
sliding_billy said:
That's what I assumed you meant (that the new BL was in all May builds), but your working sounded like maybe it was left out of the Verizon OTA build. I'm just waiting patiently for a TWRP/SU build that doesn't need me to mismatch the BL. It wasn't like there was any functional reason to upgrade in May.
Click to expand...
Click to collapse
Yeah. A few posts above yours @savi0 pointed to a Chainfire posts relating the issue. You can also check the last posts from EX Kernel. flar2 posted a link to the latest security bulletin...
Normally, we won't have to wait too long to get back TWRP/Root.
Cheers...
sliding_billy said:
I'm just waiting patiently for a TWRP/SU build that doesn't need me to mismatch the BL. It wasn't like there was any functional reason to upgrade in May.
Click to expand...
Click to collapse
Although I have the Automatic system update option shut off, in the past my Pixel has used cellular data while remaining on the prior version after the update notification appears. I think the phone wasted about 1 GB the last time I didn't take an OTA update. That essentially means I can not take the update and possibly cause the phone to waste cellular data, shut off cellular data to avoid the usage while remaining on the prior version, or take the update. Actually I have seen a fourth option linked below, but that keeps my phone constantly awake and doesn't allow deep sleep, so I never tried the alteration long enough to see if it would avoid cellular data usage if the change was made before the OTA notification.
https://www.androidexplained.com/pixel-hide-ota-notification/
alluringreality said:
Although I have the Automatic system update option shut off, in the past my Pixel has used cellular data while remaining on the prior version after the update notification appears. I think the phone wasted about 1 GB the last time I didn't take an OTA update. That essentially means I can not take the update and possibly cause the phone to waste cellular data, shut off cellular data to avoid the usage while remaining on the prior version, or take the update. Actually I have seen a fourth option linked below, but that keeps my phone constantly awake and doesn't allow deep sleep, so I never tried the alteration long enough to see if it would avoid cellular data usage if the change was made before the OTA notification.
https://www.androidexplained.com/pixel-hide-ota-notification/
Click to expand...
Click to collapse
Hello,
I don't understand what you mean when you say:
alluringreality said:
That essentially means I can not take the update and possibly cause the phone to waste cellular data, shut off cellular data to avoid the usage while remaining on the prior version, or take the update
Click to expand...
Click to collapse
If you have issues, just sideload the latest OTA from Google here:
https://developers.google.com/android/ota
Instructions are available on this page.
Good luck...
alluringreality said:
Although I have the Automatic system update option shut off, in the past my Pixel has used cellular data while remaining on the prior version after the update notification appears. I think the phone wasted about 1 GB the last time I didn't take an OTA update. That essentially means I can not take the update and possibly cause the phone to waste cellular data, shut off cellular data to avoid the usage while remaining on the prior version, or take the update. Actually I have seen a fourth option linked below, but that keeps my phone constantly awake and doesn't allow deep sleep, so I never tried the alteration long enough to see if it would avoid cellular data usage if the change was made before the OTA notification.
https://www.androidexplained.com/pixel-hide-ota-notification/
Click to expand...
Click to collapse
I have been concerned about the system using data while waiting to update the phone, but I do not see that happening. I have automatic update turned off in dev settings as well as the google play services notification disables so as not to accidental click it. I see the update available if I look at the check for updates area in system, but it just is sitting at the download and install option there. I have checked my data use since the BL issue came about, and there is no data use besides normal.
Mainly I was just noting that not taking an update can potentially result in cellular data usage, in case anyone wasn't aware of the possible issue. The top items in my cellular data usage were the same as the images in the following thread when I avoided taking an OTA update.
https://forum.xda-developers.com/pixel-xl/help/android-os-sucking-mobile-data-t3597680/
savi0 said:
Sorry, I should have clarified that you are only able to apply TWRP and root to images and bootloaders that were released before the May updates.
You are absolutely right in that that I should not be installing TWRP or Root on the May bootloader because it'll result in bootloops.
Click to expand...
Click to collapse
Will the factory images (May or after) lacking the "Verizon" designation lock my Bootloader if flashed to a Verizon Pixel XL (That currently has Unlocked BL and TWRP)?
Sorry, but this is getting Hella confusing.
I'm going to update TWRP, then planning on flashing Factory Image 8.1.0 (OPM1.171019.021, Mar 2018) https://dl.google.com/dl/android/aosp/marlin-ota-nhg47q-73c108b9.zip
Do I need to worry about anything flashing this build?
Just trying to make sure I don't screw myself here, as I really NEED an unlocked Bootloader/ROOT... but I'm still running 7.1.1
Wish there was a forum for us with Verizon Pixels and Unlocked BL's...
PrettyPistol555 said:
Will the factory images (May or after) lacking the "Verizon" designation lock my Bootloader if flashed to a Verizon Pixel XL (That currently has Unlocked BL and TWRP)?
Sorry, but this is getting Hella confusing.
I'm going to update TWRP, then planning on flashing Factory Image 8.1.0 (OPM1.171019.021, Mar 2018) https://dl.google.com/dl/android/aosp/marlin-ota-nhg47q-73c108b9.zip
Do I need to worry about anything flashing this build?
Just trying to make sure I don't screw myself here, as I really NEED an unlocked Bootloader/ROOT... but I'm still running 7.1.1
Wish there was a forum for us with Verizon Pixels and Unlocked BL's...
Click to expand...
Click to collapse
If OEM unlocking is toggled and your bootloader is unlocked, just assume it is a google version. Flashing a factory image can't lock your bootloader.
shagbag913 said:
If OEM unlocking is toggled and your bootloader is unlocked, just assume it is a google version. Flashing a factory image can't lock your bootloader.
Click to expand...
Click to collapse
The "OEM unlocking" setting is greyed out. And underneath it says "bootloader is already unlocked" (slider is to the left).
That is what you mean by "toggled", correct?
Thanks for the reply! I appreciate it greatly.
PrettyPistol555 said:
The "OEM unlocking" setting is greyed out. And underneath it says "bootloader is already unlocked" (slider is to the left).
That is what you mean by "toggled", correct?
Thanks for the reply! I appreciate it greatly.
Click to expand...
Click to collapse
Yep.