Develop Bugs

[Q] When switching to Yakju..

I'm aware of the tutorial regarding how it's done, so I'm not asking that. My question is that if by chance I experience the roaming problems and have to root/unlock bootloader to repair, using the guides to relock and unroot.. will I still be able to keep Yakju at 4.0.2 and receive future OTA updates?
The reason I bought this phone was to avoid rooting and unlocking altogether, but this Yakjuux nonsense is really irritating especially since I'm waiting on updates that have absolutely no timeline of being released for GSM/Yakjuux builds.
tl;dr
If I root and unlock bootloader to switch to Yakju, will relocking and unrooting take away my Yakju status/4.0.2?

SL1VR said:
I'm aware of the tutorial regarding how it's done, so I'm not asking that. My question is that if by chance I experience the roaming problems and have to root/unlock bootloader to repair, using the guides to relock and unroot.. will I still be able to keep Yakju at 4.0.2 and receive future OTA updates?
The reason I bought this phone was to avoid rooting and unlocking altogether, but this Yakjuux nonsense is really irritating especially since I'm waiting on updates that have absolutely no timeline of being released for GSM/Yakjuux builds.
tl;dr
If I root and unlock bootloader to switch to Yakju, will relocking and unrooting take away my Yakju status/4.0.2?
Click to expand...
Click to collapse
if you switch to stock Yakju you will receive Yakju ota's... whether locked, unlocked, rooted or unrooted

ogdobber said:
if you switch to stock Yakju you will receive Yakju ota's... whether locked, unlocked, rooted or unrooted
Click to expand...
Click to collapse
My issue isn't just with the OTAs, I simply don't want to be unlocked or rooted. But like I said, I'm sick of waiting for a 4.0.1 volume fix, and 4.0.2.. when everyone else is already using them months prior.
If I can clarify,
I want to be back to completely stock, unrooted, relocked bootloader, but on 4.0.2 Yakju. Is this possible?

SL1VR said:
My issue isn't just with the OTAs, I simply don't want to be unlocked or rooted. But like I said, I'm sick of waiting for a 4.0.1 volume fix, and 4.0.2.. when everyone else is already using them months prior.
If I can clarify,
I want to be back to completely stock, unrooted, relocked bootloader, but on 4.0.2 Yakju. Is this possible?
Click to expand...
Click to collapse
yes, if you flash the stock images from google for 4.0.2 then you will be stock 4.0.2 (yakju) that is what you are looking for right?
so flash the images and relock the bootloader
Like I said, when it comes to ota's, stock is stock. it doesn't matter if your phone is rooted or unlocked

ogdobber said:
yes, if you flash the stock images from google for 4.0.2 then you will be stock 4.0.2 (yakju) that is what you are looking for right?
so flash the images and relock the bootloader
Like I said, when it comes to ota's, stock is stock. it doesn't matter if your phone is rooted or unlocked
Click to expand...
Click to collapse
Oh okay, so I can flash the stock image for Yakju through Google's image page for GSM, then relock the bootloader, Ill be okay? And my warranty will be intact?

Just to shed some light, I used the Galaxy Nexus toolkit from another thread, unlocked bootloader, flashed Yakju, and relocked bootloader all within 10 minutes with completely painless execution (after struggling getting the proper drivers installed. Fyi, used the pdanet drivers.) Anyone reading this topic, there's NOTHING to be concerned about when doing this, just make sure you do it right.
Sent from my Galaxy Nexus using XDA App

Could you please post the link of the instruction on how to do this... I am also on rogers and i'm sick of waiting for them... You buy a nexus to get updates on time....

brewcrew2243 said:
Could you please post the link of the instruction on how to do this... I am also on rogers and i'm sick of waiting for them... You buy a nexus to get updates on time....
Click to expand...
Click to collapse
here you go
http://forum.xda-developers.com/showthread.php?t=1464881

You don't have to root. Just unlock the bootloader to push the radio file to your phone.
If you're on 4.0.1 then flash/update to 4.0.2, you'll loose any existing root you had on your phone.

[Q] Help! Converting Docomo Galaxy Nexus to International Yakju Unlocked

I've seen plenty of rooting guides for the Docomo Galaxy Nexus, and guides to sim unlock the device on its original japanese custom software, but no guides to convert the docomo-locked japanese galaxy nexus into a fully stock international unlocked version. It should technically be possible, since both are the i9250 and exactly identical when it comes to hardware, and the only difference, to my knowledge, is the software that runs on the docomo-locked galaxy nexus. If I were to flash a stock ICS 4.0.4 yakju build directly from google's download site, would the docomo nexus become "factory unlocked" on its own after flashing, just like any international version? Would it be able to receive OTA updates directly from google in the future? Also, if anyone could help me know how to go about flashing the yakju 4.0.4 onto the docomo nexus from scratch, it would be greatly appreciated. I ask because I was able to purchase a carrier-locked Docomo Galaxy Nexus for $415 USD, and was told that it could be fully converted to a phone exactly identical to the international unlocked version (except, of course, for the Docomo branding on the back cover). I'm sure this would be useful to many people. If anyone would be willing to give me some guidance, it would really help me out a lot! I am relatively new to android hacking, but did have a nexus s in the past, on which I ran cyanogenmod 9. I am in the USA, and am using AT&T. Once again, it would be a huge help if someone could guide me in the right direction, and I figured there was no better place to look than XDA! Thank you so much!

Docomo Galaxy Nexus
monoloco1 said:
I've seen plenty of rooting guides for the Docomo Galaxy Nexus, and guides to sim unlock the device on its original japanese custom software, but no guides to convert the docomo-locked japanese galaxy nexus into a fully stock international unlocked version. It should technically be possible, since both are the i9250 and exactly identical when it comes to hardware, and the only difference, to my knowledge, is the software that runs on the docomo-locked galaxy nexus. If I were to flash a stock ICS 4.0.4 yakju build directly from google's download site, would the docomo nexus become "factory unlocked" on its own after flashing, just like any international version? Would it be able to receive OTA updates directly from google in the future? Also, if anyone could help me know how to go about flashing the yakju 4.0.4 onto the docomo nexus from scratch, it would be greatly appreciated. I ask because I was able to purchase a carrier-locked Docomo Galaxy Nexus for $415 USD, and was told that it could be fully converted to a phone exactly identical to the international unlocked version (except, of course, for the Docomo branding on the back cover). I'm sure this would be useful to many people. If anyone would be willing to give me some guidance, it would really help me out a lot! I am relatively new to android hacking, but did have a nexus s in the past, on which I ran cyanogenmod 9. I am in the USA, and am using AT&T. Once again, it would be a huge help if someone could guide me in the right direction, and I figured there was no better place to look than XDA! Thank you so much!
Click to expand...
Click to collapse
Actually, I have done something similar, so let me put the steps that I followed:
1. Download the Galaxy Nexus Toolkit from its XDA thread and set it on your PC
2. Setup the drivers for Galaxy Nexus - This was the toughest step for me. The above toolkit itself gives an option, but that did not work on my PC. I ended up downloading the latest version of Android SDK and setting it up again so that my GNex could connect properly.
3. Start the Galaxy Nexus Toolkit and follow the instructions to unlock bootloader etc. I used option 7, which unlocks bootloader, roots and flashes CWM recovery - all in one step. The toolkit provides sufficient online instructions so its a piece of cake once you can successfully connect your GNex to the PC
4. Get the stock version of 4.0.4 for GSM (I think Google provides some links)
5. Use recovery mode to wipe date and install the zip
6. SIM unlock using IMEI code purchased online or using nv_data.bin method or use the F***Docomo.apk developed by one of the developers on XDA (Although this apk may not yet work on 4.0.4, I can confirm that it works on 4.0.2)
In my case, instead of flashing stock, I flashed ARHD 2.1.5 and used the apk to SIM unlock.
The toolkit and the apk are easily searchable on XDA. Hope the above helps
Enjoy your GNex

kizuki.buy said:
Actually, I have done something similar, so let me put the steps that I followed:
1. Download the Galaxy Nexus Toolkit from its XDA thread and set it on your PC
2. Setup the drivers for Galaxy Nexus - This was the toughest step for me. The above toolkit itself gives an option, but that did not work on my PC. I ended up downloading the latest version of Android SDK and setting it up again so that my GNex could connect properly.
3. Start the Galaxy Nexus Toolkit and follow the instructions to unlock bootloader etc. I used option 7, which unlocks bootloader, roots and flashes CWM recovery - all in one step. The toolkit provides sufficient online instructions so its a piece of cake once you can successfully connect your GNex to the PC
4. Get the stock version of 4.0.4 for GSM (I think Google provides some links)
5. Use recovery mode to wipe date and install the zip
6. SIM unlock using IMEI code purchased online or using nv_data.bin method or use the F***Docomo.apk developed by one of the developers on XDA (Although this apk may not yet work on 4.0.4, I can confirm that it works on 4.0.2)
In my case, instead of flashing stock, I flashed ARHD 2.1.5 and used the apk to SIM unlock.
The toolkit and the apk are easily searchable on XDA. Hope the above helps
Enjoy your GNex
Click to expand...
Click to collapse
Hello. Thank you very much for your detailed explanation. I had a few questions regarding the process: 1.) Is it necessary to use an unlock code/unlock program to unlock the phone after flashing the yakju build? If I were to flash the yakju build to the galaxy nexus without using a sim unlock method on the docomo software, would the phone unlock itself automatically after flashing yakju, since the yakju software contains different radios than those found in the docomo software? 2.) I noticed that the yakju build on google's download site downloads as a .tar file. I was wondering, before I even attempt to flash it, if it is safe to flash a .tar file on clockworkmod,or if I need to somehow extract it. If so, how should I go about doing this? Once extracted from the .tar file, can the yakju file then be flashed in clockworkmod recovery as if it were any other rom? 3.) Will I still be able to receive OTA updates directly from google as they become available?
Once again, thank you so much for your help!

monoloco1 said:
Hello. Thank you very much for your detailed explanation. I had a few questions regarding the process: 1.) Is it necessary to use an unlock code/unlock program to unlock the phone after flashing the yakju build? If I were to flash the yakju build to the galaxy nexus without using a sim unlock method on the docomo software, would the phone unlock itself automatically after flashing yakju, since the yakju software contains different radios than those found in the docomo software? 2.) I noticed that the yakju build on google's download site downloads as a .tar file. I was wondering, before I even attempt to flash it, if it is safe to flash a .tar file on clockworkmod,or if I need to somehow extract it. If so, how should I go about doing this? Once extracted from the .tar file, can the yakju file then be flashed in clockworkmod recovery as if it were any other rom? 3.) Will I still be able to receive OTA updates directly from google as they become available?
Once again, thank you so much for your help!
Click to expand...
Click to collapse
1. Flashing yakju will not unlock a SIM-locked phone. There can be 3 scenarios,
i) Phone is currently SIM-locked --> You will need to SIM unlock even after flashing yakju
ii) Phone is currently 'temporarily' SIM unlocked --> Flashing a new ROM or factory reset will lead to phone getting SIM locked again. So needs to be SIM unlocked again
iii) Phone is currently permanently SIM unlocked --> No need to do anything after flashin yakju.
2. My understanding is that .tar cannot be flashed directly using CWM. It should be containing a zip file with ROM and probably the image files for baseband etc. If you want to manually flash, you can also follow the instructions here --> http://forum.xda-developers.com/showthread.php?t=1391881
3. You should be getting OTA updates after flashing yakju

I am not sure If i have a similar problem. Please help
kizuki.buy said:
1. Flashing yakju will not unlock a SIM-locked phone. There can be 3 scenarios,
i) Phone is currently SIM-locked --> You will need to SIM unlock even after flashing yakju
ii) Phone is currently 'temporarily' SIM unlocked --> Flashing a new ROM or factory reset will lead to phone getting SIM locked again. So needs to be SIM unlocked again
iii) Phone is currently permanently SIM unlocked --> No need to do anything after flashin yakju.
2. My understanding is that .tar cannot be flashed directly using CWM. It should be containing a zip file with ROM and probably the image files for baseband etc. If you want to manually flash, you can also follow the instructions here --> http://forum.xda-developers.com/showthread.php?t=1391881
3. You should be getting OTA updates after flashing yakju
Click to expand...
Click to collapse
I just bought a new galaxy nexus gt-i9250 from Ebay India
The seller says I can use any SIM. Here;e the link:
http://_cgi_.ebay.in/ws/eBayISAPI.dll?ViewItem&item=280923671374 (Please remove the '_')
Is there a way for me to find out if my phone is "temporarily' SIM unlocked or Permanently Sim unlocked?
Also,
one of my fellow buyers reported that, he got an offical Jelly Bean OTA when he turned on the device and the phone got bricked when he updated it. Could this happen? If we are getting an OTA from google, then it means that it is in the 'yakju' build everyone's talking about and the phone shouldn't be bricked. Isn'it?
Sorry it sounded sounded dumb. I am new to using android.

Does anybody know if the docomo phones that newegg sells are perm or temp sim-unlocked? will the phone keep the sim unlock after going to yakju?

GateCityRadio said:
Does anybody know if the docomo phones that newegg sells are perm or temp sim-unlocked? will the phone keep the sim unlock after going to yakju?
Click to expand...
Click to collapse
I have a Newegg Docomo (bought it in April). First thing I did to it was flash yakju 4.0.4 (IMM76D) using the GNex Toolkit and pop in my AT&T SIM, which had previously been in an AT&T GS II (SGH-I777). It worked like a champ immediately - no muss no fuss. I think it was SIM-unlocked by whomever Newegg gets them from.
I've since gotten the IMM76I and JRO03C updates OTA.

UnusualSuspect said:
I have a Newegg Docomo (bought it in April). First thing I did to it was flash yakju 4.0.4 (IMM76D) using the GNex Toolkit and pop in my AT&T SIM, which had previously been in an AT&T GS II (SGH-I777). It worked like a champ immediately - no muss no fuss. I think it was SIM-unlocked by whomever Newegg gets them from.
I've since gotten the IMM76I and JRO03C updates OTA.
Click to expand...
Click to collapse
Thanks a bunch! I know this is a little OT, but did yours look used at all? Any scratches or dents?

Stuck in 4.0.2?

I have a Galaxy Nexus, its running 4.0.2, no mods, root or whatever.
I'm sseing a lot of people getting 4.0.4 updates since a few weeks already, but my device is not recieving it.
Is it normal? Should I be worried? How long may it normally take?

I'm exactly in the same situation you are, been waiting for the ICS 4.0.4 update since March 28th and still nothing. (Vodafone Portugal, fyi)
I've been reading the forums left and right trying to understand why and how to get the update and here's what I've gathered:
- You are running a ICS version which was compiled by Samsung so basically all the Over-The-Air updates will have to come from Samsung, instead of Google.
- If you wish to get ICS 4.0.4 you need to flash the official Google Images which can be found here: https://developers.google.com/android/nexus/images
If you do so, you will no longer receive updates from Samsung and will most likely always be on the latest version of Android.
Now the down side of it:
- Flashing stock images might require you to root your phone which results in loss of warranty (and I'm not 100% sure on this one so I appreciate someone to correct me if I am wrong)
- It will erase all of your personal data. From photos, to SMS's, wi-fi networks, to app-specific settings, etc.
How to do it?
There's a couple of threads around, here's one to start you with:
http://forum.xda-developers.com/showpost.php?p=20310934&postcount=2
Hope it helped.

woah woah woah.....are you on verizon? if so, that is the problem verizons Gnex is still on 4.0.2 where all other nexus's are on 4.0.4 right now. you are just going to have to wait it out for a couple of weeks (i am guessing) or root and install a 4.0.4 ROM
if you are on a GSM network or a spring Gnex user...then there is an issue.

stevesmind said:
Now the down side of it:
- Flashing stock images might require you to root your phone which results in loss of warranty (and I'm not 100% sure on this one so I appreciate someone to correct me if I am wrong)
Click to expand...
Click to collapse
no it does not require root, just unlocking the bootloader, which will wipe the device. it is easy enough to relock. instead of fastboot oem unlock, its fastboot oem lock.

[Tool][HTC 10][S-On]Firmware Updater

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

Sideloaded NDE63X, can I relock bootloader for my Verizon Pixel XL?

As the title states, I successfully sideloaded the most recent ota since I couldn't find a proper guide to flash the factory image (nor the proper image for that matter). Checking the kernel and what not everything appears to be stock, and I know I don't have root anymore or any of the apps that go with that.
This being said, will I be able to relock the bootloader? I need to return my phone to Verizon and want to make sure the phone is as factory as I can get so they don't get all up in my face about it.
or.....
Will the fact that my bootloader is unlocked but nothing else has been changed be acceptable to return the phone? Anyone know from experience?

Anthony825 said:
As the title states, I successfully sideloaded the most recent ota since I couldn't find a proper guide to flash the factory image (nor the proper image for that matter). Checking the kernel and what not everything appears to be stock, and I know I don't have root anymore or any of the apps that go with that.
This being said, will I be able to relock the bootloader? I need to return my phone to Verizon and want to make sure the phone is as factory as I can get so they don't get all up in my face about it.
or.....
Will the fact that my bootloader is unlocked but nothing else has been changed be acceptable to return the phone? Anyone know from experience?
Click to expand...
Click to collapse
I doubt they'd care but the warning when turning the device one might. Anyways, I believe after a flash of the full factory image, you should be able to relock the bootloader.
Don't hold me liable for anything, but I'm almost certain that you just need to be running stock everything.
Sent from my Pixel XL

I couldn't do the factory image flash. Couldn't find exactly everything I needed and didn't want to chance guesswork. So I side loaded the most recent ota and it appears I'm stock everything....

Anthony825 said:
I couldn't do the factory image flash. Couldn't find exactly everything I needed and didn't want to chance guesswork. So I side loaded the most recent ota and it appears I'm stock everything....
Click to expand...
Click to collapse
Hey man, you ever managed to relock your bootloader? I'm thinking of doing it too since I may need to RMA mine as well.