Database Info

New update for boost k2 cl

Downloaded the new ota for boost. I am s-off with unlocked boot loader and installed twrp. Do I need to go back to stock recovery and relock to install? Thanks

biga1 said:
Downloaded the new ota for boost. I am s-off with unlocked boot loader and installed twrp. Do I need to go back to stock recovery and relock to install? Thanks
Click to expand...
Click to collapse
i get the same thing, guess I will wait and see what they say.....

@banderz777 and @biga1, If you are S-Off you do not need to relock the bootloader. If you are S-On then you must relock the bootloader. You will need to flash your stock recovery to proceed with the OTA, then after it finishes you may flash back your TWRP recovery.

I don't have stock recovery for jb 422 , where can I find it....

banderz777 said:
I don't have stock recovery for jb 422 , where can I find it....
Click to expand...
Click to collapse
Inside the original 4.2.2 OTA zip will be another zip called, firmware. Unzip firmware.zip and you will find your stock recovery.

Modding.MyMind said:
Inside the original 4.2.2 OTA zip will be another zip called, firmware. Unzip firmware.zip and you will find your stock recovery.
Click to expand...
Click to collapse
Thanks really just wanted the stock recovery, I delected the OTA off my PC, so now back to donwloading it...... LOL should have saved it....:crying::crying:

banderz777 said:
Thanks really just wanted the stock recovery, I delected the OTA off my PC, so now back to donwloading it...... LOL should have saved it....:crying::crying:
Click to expand...
Click to collapse
Hold on to the firmware.zip lol. Could come in handy down the road

Modding.MyMind said:
Inside the original 4.2.2 OTA zip will be another zip called, firmware. Unzip firmware.zip and you will find your stock recovery.
Click to expand...
Click to collapse
Mmmm, I fastboot flashed the stock recovery that I extracted from the firmware. Tried to install the ota and got the red triangle. not sure what I did wrong. T.I.A.

Studip Me......
Modding.MyMind said:
Hold on to the firmware.zip lol. Could come in handy down the road
Click to expand...
Click to collapse
@
@moddingMyMind.... yes I never should have deleted it in the first place and yes I am keeping it for the future.... LOL.
P.S I have the recovery now.
---------- Post added at 07:48 PM ---------- Previous post was at 07:45 PM ----------
biga1 said:
Mmmm, I fastboot flashed the stock recovery that I extracted from the firmware. Tried to install the ota and got the red triangle. not sure what I did wrong. T.I.A.
Click to expand...
Click to collapse
@ biga1 are you S-OFF or S-ON ?, or just try locking your bootloader and see, you do still have the unlock bin from HTC.

@Modding.MyMind I am S-OFF. I do NOT have my unlock bin from HTC anymore :crying:

The OTA is applying a lot of patches to your system directory. It is always recommended that you have all apps whether bloatware or not which originally came on the device to insure the OTA doesn't abort. If what the OTA is updating isn't found on your phone then it will terminate. You can get another unlock_code.bin by simply redoing the steps again over at htcdev.

Modding.MyMind said:
The OTA is applying a lot of patches to your system directory. It is always recommended that you have all apps whether bloatware or not which originally came on the device to insure the OTA doesn't abort. If what the OTA is updating isn't found on your phone then it will terminate. You can get another unlock_code.bin by simply redoing the steps again over at htcdev.
Click to expand...
Click to collapse
ahhhh. that makes sense. my phone is far from stock now and been debloated. I have my original stock backup that I can reinstall but is this ota update going to make a big difference? Thanks for all the help

biga1 said:
ahhhh. that makes sense. my phone is far from stock now and been debloated. I have my original stock backup that I can reinstall but is this ota update going to make a big difference? Thanks for all the help
Click to expand...
Click to collapse
I haven't accepted the update yet. Been reviewing the patches before I accept it. Also weary about the hboot image inside the firmware.zip that comes with the OTA. Not sure what affects it may have so I am snooping around a bit.

Ok. I feel better. You have been my barometer for this device. Thanks for all your support for the boost users.
Sent from my C525c using XDA Free mobile app

Has anyone flashed the latest ota with success? And if so are there any notable improvements? Thanks
Sent from my C525c using XDA Free mobile app

biga1 said:
Has anyone flashed the latest ota with success? And if so are there any notable improvements? Thanks
Sent from my C525c using XDA Free mobile app
Click to expand...
Click to collapse
I haven't yet simply because my core.odex file is modified which will cause it to abort. But, I have mainly seen complaints about the OTA and nothing otherwise.

I've updated....nothing special.....no complaints about it here......but nothing new either

Nexus 5 with "TeamWin" failed update - and won't start again

Hello everyone.
Two hours ago I received the notification about the Android 5.0 update. I downloaded it and hit "Install". Then, "TeamWin" started, but not the update. I rebooted into System and tried to update again - but it tells me that 4.4.4 is the latest version I can get now. I'm on Build KTU84P now.
1) Do I need to remove TeamWin? If yes, with what?
2) How can I start the update again? I'm on a super slow connection and it would hurt to download the 500 MB again…
Thank you!

Fablus said:
Hello everyone.
Two hours ago I received the notification about the Android 5.0 update. I downloaded it and hit "Install". Then, "TeamWin" started, but not the update. I rebooted into System and tried to update again - but it tells me that 4.4.4 is the latest version I can get now. I'm on Build KTU84P now.
1) Do I need to remove TeamWin? If yes, with what?
2) How can I start the update again? I'm on a super slow connection and it would hurt to download the 500 MB again…
Thank you!
Click to expand...
Click to collapse
You need to remove TeamWin, and load up your stock recovery. I don't have the exact instructions for this unfortunately.
The OTA update will come back to your phone soon, usually. Did for me within the hour.
The issue I am having now, back with stock recovery, is during the install I am getting a dead Android error icon, and can't continue. Looking for any help I can, and hopefully it will help you too.

Mysticodex said:
You need to remove TeamWin, and load up your stock recovery. I don't have the exact instructions for this unfortunately.
The OTA update will come back to your phone soon, usually. Did for me within the hour.
The issue I am having now, back with stock recovery, is during the install I am getting a dead Android error icon, and can't continue. Looking for any help I can, and hopefully it will help you too.
Click to expand...
Click to collapse
Maybe we need http://forum.xda-developers.com/google-nexus-5/general/stock-checker-zip-prepare-ota-t2927865?
Gosh, this used to be so easy all the time.

if you are using twrp, why the heck are you trying to install the ota? why not download(from xda) and flash a recovery flashable stock or aosp build, and make life much easier for yourself? heck, i dirty flashed from 444 to 5.0 via an aosp flashable zip without any issues, and kept all my data.

simms22 said:
if you are using twrp, why the heck are you trying to install the ota? why not download(from xda) and flash a recovery flashable stock or aosp build, and make life much easier for yourself? heck, i dirty flashed from 444 to 5.0 via an aosp flashable zip without any issues, and kept all my data.
Click to expand...
Click to collapse
I've read http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523 and it clearly states
-Do a factory reset (maybe you can keep data coming from STOCK 4.4.4 - maybe)
Click to expand...
Click to collapse
And I didn't want to count on a maybe.

I'm using stock recovery, rooted as per normal, and a custom kernal. OTA is giving an Android dead error, with no text. Trying to figure out how to diagnose this.

Fablus said:
I've read http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523 and it clearly states
Click to expand...
Click to collapse
it clearly states what? to use recovery version 2.8+? i used an older version, twrp version 2.6.2.4. what else?
---------- Post added at 05:51 PM ---------- Previous post was at 05:48 PM ----------
Mysticodex said:
I'm using stock recovery, rooted as per normal, and a custom kernal. OTA is giving an Android dead error, with no text. Trying to figure out how to diagnose this.
Click to expand...
Click to collapse
it wont flash over a rooted rom anymore as of lollipop. you can flash the factory img via fastboot though, in your bootloader.

simms22 said:
it clearly states what? to use recovery version 2.8+? i used an older version, twrp version 2.6.2.4. what else?
---------- Post added at 05:51 PM ---------- Previous post was at 05:48 PM ----------
it wont flash over a rooted rom anymore as of lollipop. you can flash the factory img via fastboot though, in your bootloader.
Click to expand...
Click to collapse
Trying to remove the root right now via SuperSU. I am hopeful it will work better afterwards.
Edit: SuperSU unrooted it, rebooted, did OTA again, error again. Is there no way to find out what this error is?

[Q&A] EXE/ZIP RUU M8_VZW 5.0.1 (s-off only)(newest)

Q&A for EXE/ZIP RUU M8_VZW 5.0.1 (s-off only)(newest)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for EXE/ZIP RUU M8_VZW 5.0.1 (s-off only)(newest). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

billblack said:
Long time lurker. I read and can use Google . Regardless, it failed and scared the crap out of me as it wouldn't boot. Got back into boot loader, fired up EXE again and it seems to have finished the 2nd time. A few more grey hairs, but all is good my friend. Thanks.
Click to expand...
Click to collapse
Same thing happened to me! Failed the first time around, worked the second. Booting now and it appears to be working (Android is upgrading...)

So when I use the ruu for sdcard and I reboot after I get send to recovery and can't boot system. Why is that?

EXE/ZIP RUU M8_VZW 5.0.1 Help
I installed the RUU zip via SD last night. I was running Dottat's EXE/ZIP RUU M8_VZW 4.4.4 (s-off only) with stock recovery. When I flashed the 5.0.1 RUU zip, I have a couple Partition Fails (unfortunately, I don't remember exactly which ones). However, in the time since I installed it, I saw all the new messages in the thread about others having the same Partition Fail errors. Even with the errors, my phone booted fine. I am having some weirdness though (major lag after sending a message in Facebook Messenger app....a reboot resolves the lag for a little while, then it returns; Verizon Caller ID app won't load; logging in to Swiftkey keyboard's cloud with my Google account fails with an error). So I see the new zip to flash the L Hboot BEFORE flashing the RUU. Obviously too late for that. Also, I installed TWRP recovery in place of the stock recovery.
So my question is: How should I proceed with trying to get the 5.0.1 to flash with no errors? Should I install Dottat's 4.4.4 (s-off), which will get me back to stock recovery...then let it boot up. Then flash the L hboot, and then finally flash the 5.0.1 RUU? Or are there other alternatives?
Thanks!

mbarcus said:
I installed the RUU zip via SD last night. I was running Dottat's EXE/ZIP RUU M8_VZW 4.4.4 (s-off only) with stock recovery. When I flashed the 5.0.1 RUU zip, I have a couple Partition Fails (unfortunately, I don't remember exactly which ones). However, in the time since I installed it, I saw all the new messages in the thread about others having the same Partition Fail errors. Even with the errors, my phone booted fine. I am having some weirdness though (major lag after sending a message in Facebook Messenger app....a reboot resolves the lag for a little while, then it returns; Verizon Caller ID app won't load; logging in to Swiftkey keyboard's cloud with my Google account fails with an error). So I see the new zip to flash the L Hboot BEFORE flashing the RUU. Obviously too late for that. Also, I installed TWRP recovery in place of the stock recovery.
So my question is: How should I proceed with trying to get the 5.0.1 to flash with no errors? Should I install Dottat's 4.4.4 (s-off), which will get me back to stock recovery...then let it boot up. Then flash the L hboot, and then finally flash the 5.0.1 RUU? Or are there other alternatives?
Thanks!
Click to expand...
Click to collapse
Run it once more. The failed PU was for the data partition. If you run it once more it will be successful. I think the root cause here is the changes to partitions that occurred with this OTA and that the likely solution is to flash the L hboot first before doing the RUU to L. Once on L firmware/OS you can use the RUU again with no issues.
One big dang speed bump in all the fun.

dottat said:
Run it once more. The failed PU was for the data partition. If you run it once more it will be successful. I think the root cause here is the changes to partitions that occurred with this OTA and that the likely solution is to flash the L hboot first before doing the RUU to L. Once on L firmware/OS you can use the RUU again with no issues.
One big dang speed bump in all the fun.
Click to expand...
Click to collapse
Can I run the RUU again using TWRP? Or do I need to be on Stock Recovery? And thank you for your help!!

mbarcus said:
Can I run the RUU again using TWRP? Or do I need to be on Stock Recovery? And thank you for your help!!
Click to expand...
Click to collapse
recovery doesnt' weigh in here. You can install it from bootloader using the SD card method.

How do I flash L Hboot? with twrp? do I have to flash it or can I just use the ruu to get to the new 5.0.1 firmware? thanks

So you asked to report our experience ...
First, let me say thanks. I am now on 5.0.1 and back to root thanks to your work and willingness to share.
Background:
I was stock 4.4.4, unlocked, s-off with TWRP recovery when the VZW 5.0.1 OTA hit. I had a number of bloatware apps frozen through Titanium Backup and probably due to a combination of all that I couldn't load the update. Reflashing boot, system and recovery still wouldn't let me take the OTA, so I ended up using HTC SyncManager repair to make Verizon happy. I got the update, kept unlocked and s-off, but lost root.​
Recovering Root:
After finding your stuff, I first tried loading through the bootloader with your zips in the root of my SD card (128 GB, single partition, exFAT). No go for either the hboot or the RUU. both gave me a "Wrong image" message and only allowed reboot to system.
So the next step was to try flashing with TWRP. I flashed TWRP 2.8.5.0 via fastboot and then let it do all it's stuff (Busybox, SuperSU, SD Card Fix, etc.) , rebooted to system just to have everything catch up to itself, and then rebooted to TWRP recovery. I then flashed the hboot and the RUU through TWRP, rebooted, and I'm back to full root.​
So again, thanks! A happy camper backing everything up with Titanium again and hoping that you really wanted to hear a real-world experience.

A_Levis said:
First, let me say thanks. I am now on 5.0.1 and back to root thanks to your work and willingness to share.
Background:
I was stock 4.4.4, unlocked, s-off with TWRP recovery when the VZW 5.0.1 OTA hit. I had a number of bloatware apps frozen through Titanium Backup and probably due to a combination of all that I couldn't load the update. Reflashing boot, system and recovery still wouldn't let me take the OTA, so I ended up using HTC SyncManager repair to make Verizon happy. I got the update, kept unlocked and s-off, but lost root.​
Recovering Root:
After finding your stuff, I first tried loading through the bootloader with your zips in the root of my SD card (128 GB, single partition, exFAT). No go for either the hboot or the RUU. both gave me a "Wrong image" message and only allowed reboot to system.
So the next step was to try flashing with TWRP. I flashed TWRP 2.8.5.0 via fastboot and then let it do all it's stuff (Busybox, SuperSU, SD Card Fix, etc.) , rebooted to system just to have everything catch up to itself, and then rebooted to TWRP recovery. I then flashed the hboot and the RUU through TWRP, rebooted, and I'm back to full root.​
So again, thanks! A happy camper backing everything up with Titanium again and hoping that you really wanted to hear a real-world experience.
Click to expand...
Click to collapse
There's just one problem with this all.... lol...
you can't flash the RUU or hboot zips through TWRP.

..

dottat said:
There's just one problem with this all.... lol...
you can't flash the RUU or hboot zips through TWRP.
Click to expand...
Click to collapse
Well, XDA does call me a "Junior Member". Probably a good reason for that.
Looking back at the TWRP log, it seems you are right and my attempts to flash hboot and RUU from TWRP failed (but any indication of that flashed by so fast that I couldn't tell). So does that mean that my fastboot flash of TWRP recovery opened up everything that I needed to get root directly from TWRP (installation of BusyBox and SuperSU)?

A_Levis said:
Well, XDA does call me a "Junior Member". Probably a good reason for that.
Looking back at the TWRP log, it seems you are right and my attempts to flash hboot and RUU from TWRP failed (but any indication of that flashed by so fast that I couldn't tell). So does that mean that my fastboot flash of TWRP recovery opened up everything that I needed to get root directly from TWRP (installation of BusyBox and SuperSU)?
Click to expand...
Click to collapse
Most recoveries will offer to flash su on an unrooted rom. You can either do that or manually flash the newest supersu.zip After you boot up you can install busybox from an app like this... https://play.google.com/store/apps/details?id=stericson.busybox
So what rom/firmware are you currently on?

After using the RUU, it finished with a successful update. I booted into recovery to create a backup, but now when I try to boot back into the OS, it goes back into TWRP like it would if I were booting into recovery. Anyone have any ideas?
---------- Post added at 10:30 PM ---------- Previous post was at 10:25 PM ----------
Nickchapstick said:
So when I use the ruu for sdcard and I reboot after I get send to recovery and can't boot system. Why is that?
Click to expand...
Click to collapse
After looking for a little bit, it appears I'm having a similar issue.

klw7890 said:
After using the RUU, it finished with a successful update. I booted into recovery to create a backup, but now when I try to boot back into the OS, it goes back into TWRP like it would if I were booting into recovery. Anyone have any ideas?
---------- Post added at 10:30 PM ---------- Previous post was at 10:25 PM ----------
After looking for a little bit, it appears I'm having a similar issue.
Click to expand...
Click to collapse
You were able to boot up the OS successfully the first time right?

dottat said:
You were able to boot up the OS successfully the first time right?
Click to expand...
Click to collapse
Yes. It booted to OS the first time, after the RUU completed, but now it just boots back into recovery.

klw7890 said:
Yes. It booted to OS the first time, after the RUU completed, but now it just boots back into recovery.
Click to expand...
Click to collapse
Stock recovery?

dottat said:
Stock recovery?
Click to expand...
Click to collapse
Initially, yes. I flashed the latest TWRP. I think I might have flashed the wrong version. I'm rerunning the RUU. I really appreciate the help.
If it was the right version by chance, do you have any idea what could've caused that?

klw7890 said:
Initially, yes. I flashed the latest TWRP. I think I might have flashed the wrong version. I'm rerunning the RUU. I really appreciate the help.
If it was the right version by chance, do you have any idea what could've caused that?
Click to expand...
Click to collapse
Did you use flashify? Reason I ask is that app still thinks it's a Sprint phone. Use the twrp I have posted in the op.

dottat said:
Did you use flashify? Reason I ask is that app still thinks it's a Sprint phone. Use the twrp I have posted in the op.
Click to expand...
Click to collapse
"That app" being TWRP Manager?

[OTA] Official Marshmallow build MCG24.251-5

WARNING: THIS HAS BRICKED PHONES! It is suspected that having an encrypted phone causes these bricks, but that has not been confirmed. If your data partition is encrypted, it is extra important that you perform a factory reset before taking this OTA. Doing this will remove the encryption.
WARNING: INSTALLING THIS ON A LOCKED BOOTLOADER WILL ELIMINATE ALL CHANCE OF YOU EVER UNLOCKING YOUR BOOTLOADER.
If your bootloader is unlocked, it will not be re-locked after this update.
Do NOT flash this using TWRP. If you want to do that, use this version: http://forum.xda-developers.com/droid-turbo/development/rom-mcg24-251-5-100-stock-t3512949
So if you're a bad enough dude to flash this anyway, follow these instructions:
1. Backup all data on your phone. It will be lost.
2. If your bootloader is locked, make sure you are on SU4TL-49. If you aren't, take all available OTAs until you are.
3. If your bootloader is unlocked and you have TWRP installed, flash SU4TL-49 using this package: https://mega.nz/#!3xRhiaSR!KxH2Ya_BYK4zBjrxmej7dqaaDJVT1coTFJVJ5Fvb2WM
4. If you have TWRP installed on your phone, download the stock SU4TL-49 recovery here: https://mega.nz/#!L1AkQD4T!qoZIlLa-wuUBLMEi_gE574meiHd6Pehb34a-x3Gb-V8 and install it using the install image option in the install menu in TWRP. Reboot to recovery.
3. Perform a factory reset using the stock recovery menu. This will wipe all data and ensure that everything is formatted exactly as it should be.
4. Boot the phone normally and place the marshmallow update on the root of the directory that pops up when you plug in your phone.
5. Boot to recovery and at the stock recovery menu, select "apply update from sdcard."
6. Select the update and cross your fingers.
Get the update here: https://mega.nz/#!v0pRwThS!Pz9xuOSPjiOMtjlORkFrZ_ok0GTKqCfGzi5KmbDpHQ8

TheSt33v said:
WARNING: THIS HAS BRICKED PHONES! Do not use this unless you know what you're doing.
I will do my best to provide more detailed instructions later today. Good luck.
https://mega.nz/#!v0pRwThS!Pz9xuOSPjiOMtjlORkFrZ_ok0GTKqCfGzi5KmbDpHQ8
Click to expand...
Click to collapse
Are you sure that that file is the right one? It has the same version number as su4tl-49.

zys52712 said:
Are you sure that that file is the right one? It has the same version number as su4tl-49.
Click to expand...
Click to collapse
I'm positive. I seem to remember they did the same thing with SU4TL-49. The OTA was named after SU4TL-44 for some reason.

This is the stock recovery version, correct?

koftheworld said:
This is the stock recovery version, correct?
Click to expand...
Click to collapse
Correct. You install this using the sideload option in the stock recovery.

TheSt33v said:
Correct. You install this using the sideload option in the stock recovery.
Click to expand...
Click to collapse
Thanks for the info and the download! You finally brought the wall down. I'm waiting for the twrp version myself
.

Thank you, now we can see what can be done with the new modem, kernel, etc...
Looking forward to a plethora of improvements to our phones

koftheworld said:
Thanks for the info and the download! You finally brought the wall down. I'm waiting for the twrp version myself
.
Click to expand...
Click to collapse
I'm testing the TWRP version now. It should be up shortly.
EDIT: I flashed it and it seems to work fine. Uploading now. Should be up in a few hours. I'll check on it after I go run some errands real quick.

Despite having software status report official, not modified, I too got a status 7 error. Downloading again.
---------- Post added at 09:52 PM ---------- Previous post was at 09:51 PM ----------
zys52712 said:
Are you sure that that file is the right one? It has the same version number as su4tl-49.
Click to expand...
Click to collapse
This used to always be Motorola's naming scheme. New updates were named after the firmware version they replaced.

Sweet. I am going to wait till it is more stable. I do have a bad esn Turbo but I will need to unlock to bootloader to test.

Mirror for people having "quota exceeded" error at Mega
https://yadi.sk/d/AhmhE-yX32E84p
Rename to Blur_Version.24.81.5.quark_verizon.verizon.en.US.zip before use, throw in internal storage, and check for updates.
PS: I have 64Gb Employee Edition, and still had not receive update by air. What a shame, VZ! )

kitcostantino said:
Despite having software status report official, not modified, I too got a status 7 error. Downloading again.
---------- Post added at 09:52 PM ---------- Previous post was at 09:51 PM ----------
This used to always be Motorola's naming scheme. New updates were named after the firmware version they replaced.
Click to expand...
Click to collapse
Error 7? Are you trying to flash this in TWRP? Because you can't do that with this package. You need the stock recovery. I'm uploading a TWRP-friendly version now, but the internet is being slow today.

TheSt33v said:
Error 7? Are you trying to flash this in TWRP? Because you can't do that with this package. You need the stock recovery. I'm uploading a TWRP-friendly version now, but the internet is being slow today.
Click to expand...
Click to collapse
Negative. Stock recovery on a system that reports "Official". I'm at a loss.

kitcostantino said:
Negative. Stock recovery on a system that reports "Official". I'm at a loss.
Click to expand...
Click to collapse
Strange. Try reflashing SU4TL-49. If my TWRP package doesn't do it for you, use the full firmware package and do it manually with fastboot.

Installed successfully on two devices.
...
kitcostantino, did you refresh system, kernel, modem and recovery by SU4TL-49? Are you sure you didn't mess with Turbo Maxx ROMs in the past? Foreign bootloader can cause even brick, not just error. See bootloader status at fastboot mode should be " locked, status 0"

s5610 said:
Installed successfully on two devices.
...
kitcostantino, did you refresh system, kernel, modem and recovery by SU4TL-49? Are you sure you didn't mess with Turbo Maxx ROMs in the past? Foreign bootloader can cause even brick, not just error. See bootloader status at fastboot mode should be " locked, status 0"
Click to expand...
Click to collapse
lol. lawd, No. Ive been rocking status 3 for over a year.
As a tip, if anyone else with an unlocked bootloader runs into this,
what i had to do was restore my su-44 unmodified backup, OTA to SU-49, and then, after confirming my
q/e status was 0/1 i was able to update via the file in my Mega download folder. all is well now. they even added the newer version of command center. sweet. thank you all!!

It works in LOCKED BOOTLOADER??? .-.

square1230 said:
It works in LOCKED BOOTLOADER??? .-.
Click to expand...
Click to collapse
Um, I couldn't tell you.i be been unlocked since the day Sunshine could unlocked our bootloader's. What I can tell you is you should absolutely unlock that via Sunshine before you even dream of applying this update. There will never be another opportunity.
Just my
.02. This is likely the last update for this phone, and your only chance of seeing N is via custom Roms.

TWRP version up now: http://forum.xda-developers.com/droid-turbo/development/rom-mcg24-251-5-100-stock-t3512949

square1230 said:
It works in LOCKED BOOTLOADER??? .-.
Click to expand...
Click to collapse
Yes it should. See instructions in OP.

Update received - flashing via TWRP?

Hey there fellow U11 Users,
I just received the update concerning 60fps HD-Video etc. I use TWRP so the update can't be installed by itself. So I have two questions:
A
Where do I find the update file. I looked around a lot but couldn't locate it.
B
Once found, can I just flash it with TWRP?
Thanks in advance!

Dito13 said:
Hey there fellow U11 Users,
I just received the update concerning 60fps HD-Video etc. I use TWRP so the update can't be installed by itself. So I have two questions:
A
Where do I find the update file. I looked around a lot but couldn't locate it.
B
Once found, can I just flash it with TWRP?
Thanks in advance!
Click to expand...
Click to collapse
See here: https://forum.xda-developers.com/u11/how-to/collection-htcu-u11-ruu-firmware-t3612048/page63

Alright, thanks! :good: That only leaves the first question unanswered.

Dito13 said:
Alright, thanks! :good: That only leaves the first question unanswered.
Click to expand...
Click to collapse
/data/data/com.htc.updater/files
btw...twrp can install the update but you need to flash the firmware.zip inside the ota manually

Thank you kindly!

OMJ said:
/data/data/com.htc.updater/files
btw...twrp can install the update but you need to flash the firmware.zip inside the ota manually
Click to expand...
Click to collapse
Just to be clear: I only flash the firmware.zip manually via TWRP or do I need to flash the whole ota?
Sorry for the question. I mostly handled Nexus devices...

Dito13 said:
Just to be clear: I only flash the firmware.zip manually via TWRP or do I need to flash the whole ota?
Sorry for the question. I mostly handled Nexus devices...
Click to expand...
Click to collapse
twrp will install the ota zip but it wont install the firmware.zip inside, you have to extract & manually install from download mode

grrr.... I tried following your suggestions, but recieved error 7 in TWRP. Can you help me in the right direction?

Dito13 said:
grrr.... I tried following your suggestions, but recieved error 7 in TWRP. Can you help me in the right direction?
Click to expand...
Click to collapse
list your steps your using to install the ota via twrp....personally, I let the system initiate the install (booted into OS) as if I was 100% stock, once twrp loads, it automatically installs except for the firmware.zip
more details here...

OK, I am a Noob to the HTC world. I am used to easy flashing/rooting/etc. on Nexus devices.
TWRP doesn't do anything after accepting the ota. When I try to install the OTA via TWRP I receive Error 7. I worked my way through a lot of guides here on XDA concerning manual OTA installing. One thing I tried was flashing back to stock recovery which I found in the firmware.zip of the OTA in bootloader mode. That failed also ("FAILED (remote: not allowed on PRODUCTION device).
Edit: The device has obviously an unlocked bootloader, s-on, rooted via magisk and is a DGLU device, software number 1.16.400.5

Are you on an Untouched System Image? Completely stock ROM? While it is great we can flash the OTA in TWRP, the system stills needs to be stock, and of course will still have to fastboot firmware.

schmeggy929 said:
Are you on an Untouched System Image? Completely stock ROM? While it is great we can flash the OTA in TWRP, the system stills needs to be stock, and of course will still have to fastboot firmware.
Click to expand...
Click to collapse
Yes, everything is stock.
I managed to flash the stock recovery now. I didn't remember to use the download mode /sorry. Then Then I checked for the ota again, downloaded it and tried to apply but I landed in the stock recovery with the red exclamation mark and then nothing happened.

Dito13 said:
Yes, everything is stock.
I managed to flash the stock recovery now. I didn't remember to use the download mode /sorry. Then Then I checked for the ota again, downloaded it and tried to apply but I landed in the stock recovery with the red exclamation mark and then nothing happened.
Click to expand...
Click to collapse
re-flash twrp and try it again.

schmeggy929 said:
re-flash twrp and try it again.
Click to expand...
Click to collapse
Same result unfortunately. TWRP hands out Error 7 and "system partition has unexpected contents" or something like that although I didn't do any tinkering with the stock rom. I flashed Magisk and did a backup before and that was all.

Dito13 said:
Same result unfortunately. TWRP hands out Error 7 and "system partition has unexpected contents" or something like that although I didn't do any tinkering with the stock rom. I flashed Magisk and did a backup before and that was all.
Click to expand...
Click to collapse
Only thing I would say is start fresh. Backup all the data for your apps first. Flash the RUU, Take the OTA and reinstall all your apps.

schmeggy929 said:
Only thing I would say is start fresh. Backup all the data for your apps first. Flash the RUU, Take the OTA and reinstall all your apps.
Click to expand...
Click to collapse
Thanks again - seems to have worked. It will be interesting to see which problems occur with the Android Oreo update which was announced till the end of the year by HTC