According to the Verizon Galaxy S5 Update Page:
Android® security patches and bug fixes.
Resolved a ring-back tone issue on calls to non-Verizon phones.
Fixed an issue where some users reported difficulty making calls to non-Verizon customers.
Click to expand...
Click to collapse
The security patch included is (most likely) the July one, since Samsung also just released a new software update to international models which includes the July security patch and Verizon has been updating the "Galaxy S" series phones with the July update over the past few weeks.
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQF2_G900VVZW2DQF2_G900VVRU2DQF2_HOME.tar.md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQF2_G900VVZW2DQF2_G900VVRU2DQF2_HOME_No_Aboot.tar.md5.zip
Appreciate that, but how do you get the Odin firmware file out of curiosity?
drewcu said:
Appreciate that, but how do you get the Odin firmware file out of curiosity?
Click to expand...
Click to collapse
Updato is one way; this shows the list for the Verizon S5 with the most recent at the top; they haven't gotten the new update up yet though.
I think that another way would be for someone to dig through the update.zip file which would be on the phone of someone who got the OTA update downloaded but had not yet installed it yet.
To confirm, the only thing that's different between the dev-friendly version (when it comes out) and the stock is the missing aboot? Thanks again.
drewcu said:
To confirm, the only thing that's different between the dev-friendly version (when it comes out) and the stock is the missing aboot? Thanks again.
Click to expand...
Click to collapse
Yes and the firmware just came out today so I'm currently in the process of uploading both versions.
Dudash said:
Yes and the firmware just came out today so I'm currently in the process of uploading both versions.
Click to expand...
Click to collapse
Is this flashable with Odin only or possibly need to already be on a specific kernal? I have tried on two S5900V's through TWRP and both result in a failure message. Both are on jkruse de-bloated MM rom at the moment.
Kaliaila said:
Updato is one way; this shows the list for the Verizon S5 with the most recent at the top; they haven't gotten the new update up yet though.
I think that another way would be for someone to dig through the update.zip file which would be on the phone of someone who got the OTA update downloaded but had not yet installed it yet.
Click to expand...
Click to collapse
The link for the update zip is not working when you tap or click on it
Sent from my SM-G900V using Tapatalk
---------- Post added at 11:25 AM ---------- Previous post was at 11:16 AM ----------
No one believe update.zip files anymore ? i need one badley
Sent from my SM-G900V using Tapatalk
Kastro1784 said:
The link for the update zip is not working when you tap or click on it
Sent from my SM-G900V using Tapatalk
---------- Post added at 11:25 AM ---------- Previous post was at 11:16 AM ----------
No one believe update.zip files anymore ? i need one badley
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
Odd. It works for me.
Sent from my SM-G900V using Tapatalk
Since no one wanted to chime in and help me out in my post, you need to unzip the file and load the md5 into Odin's AP slot and flash it. Then let the phone do its thing and flash the latest TWRP with odin after. Then go back into TWRP and flash supersu to gain root again. Trying to flash right within TWRP is not an option, not sure why its not explained.
So this update wont "factory reset" my device?
AWESOME1092387456 said:
So this update wont "factory reset" my device?
Click to expand...
Click to collapse
I dirty flashed two S5's last night with Odin, no factory reset and both phones kept their bootloaders un touched since unlocked. :good:
stuck on Verizon boot screen
After the update via OTA, my aunt's phone has been stuck on Verizon boot screen. Tried booting into safe mode, with same result. Any ideas on how not to lose all her data? Thanks!
This sucks I wanna download this so bad but my computer is down smdh is it possible someone can make and ota update zip file for me so can flash this through stock recovery on my phone ?
Sent from my SM-G900V using Tapatalk
I guess no one knows how to do it huh smdh
Sent from my SM-G900V using Tapatalk
Rumsfield said:
I dirty flashed two S5's last night with Odin, no factory reset and both phones kept their bootloaders un touched since unlocked. :good:
Click to expand...
Click to collapse
Did you loose root?
I dirty flashed and lost root, was unable to get it back.
Reloaded TWRP via Odin and then flashed SuperSU, nothing. Wiped and restore backup all good. ..
mastertech007 said:
Did you loose root?
I dirty flashed and lost root, was unable to get it back.
Reloaded TWRP via Odin and then flashed SuperSU, nothing. Wiped and restore backup all good. ..
Click to expand...
Click to collapse
I always flash super su and whatever else I need in recovery after I've flashed the rom so I cant give you a definitive answer. Both phones did upgrade without data loss and now advanced calling/wifi calling actually work now which is why I flashed in the first place.
Working?
Is this working? Ive tried everything and i have the Toshiba chip. Emmc 11. It soft bricks if i try to downgraded to stock builds.
JasonD1180 said:
Is this working? Ive tried everything and i have the Toshiba chip. Emmc 11. It soft bricks if i try to downgraded to stock builds.
Click to expand...
Click to collapse
The new file seemed to unlock boot loader. Couldnt get odin to flash twrp......
JasonD1180 said:
The new file seemed to unlock boot loader. Couldnt get odin to flash twrp......
Click to expand...
Click to collapse
If you flash the dev boot loader friendly version it wont screw with your bootloader whatsoever. Before you restart go back in TWRP and flash supersu to get root again. Saying it "unlocked boot loader" may cause confusion to people because it does not, you need to manually go from locked to DEV status via a few of the methods posted in here.
Rumsfield said:
If you flash the dev boot loader friendly version it wont screw with your bootloader whatsoever. Before you restart go back in TWRP and flash supersu to get root again. Saying it "unlocked boot loader" may cause confusion to people because it does not, you need to manually go from locked to DEV status via a few of the methods posted in here.
Click to expand...
Click to collapse
Ive not had twrp or root on this device but it went from saying vzw official binary to samsung original. Will i be able to root as long as twrp flashes?
Related
I have a verizon galaxy S3 sch-i535 that I successfully rooted & unlocked to T-mobile have been using it for a while
with no issues until yesterday when I had to install a new T-Mobile sim card. I got the dreaded " The process com. android. phone has stopped" I cleared all the phone cache as was recommended. But when I boot into recovery mode it comes up with android recovery instead of clockwork mod recovery. which is what I have. I wanted to
clear the cache in that as well which was recommended. I can receive calls and text and can send text but I can't
make a phone call. Can someone help me please! Thanks
H779 said:
I have a verizon galaxy S3 sch-i535 that I successfully rooted & unlocked to T-mobile have been using it for a while
with no issues until yesterday when I had to install a new T-Mobile sim card. I got the dreaded " The process com. android. phone has stopped" I cleared all the phone cache as was recommended. But when I boot into recovery mode it comes up with android recovery instead of clockwork mod recovery. which is what I have. I wanted to
clear the cache in that as well which was recommended. I can receive calls and text and can send text but I can't
make a phone call. Can someone help me please! Thanks
Click to expand...
Click to collapse
You can re-flash your phone with the firmware of sammobile
You will lose root.
H779 said:
I have a verizon galaxy S3 sch-i535 that I successfully rooted & unlocked to T-mobile have been using it for a while
with no issues until yesterday when I had to install a new T-Mobile sim card. I got the dreaded " The process com. android. phone has stopped" I cleared all the phone cache as was recommended. But when I boot into recovery mode it comes up with android recovery instead of clockwork mod recovery. which is what I have. I wanted to
clear the cache in that as well which was recommended. I can receive calls and text and can send text but I can't
make a phone call. Can someone help me please! Thanks
Click to expand...
Click to collapse
Sounds like you may be on one of the locked bootloaders which is why a custom recovery won't work
Sent from my Nexus 5
ShapesBlue said:
Sounds like you may be on one of the locked bootloaders which is why a custom recovery won't work
Sent from my Nexus 5
Click to expand...
Click to collapse
Sorry I didn't get back sooner. working crazy hours. So is there and option here. I got this bootloader from this site. I think from chainfire.
H779 said:
I have a verizon galaxy S3 sch-i535 that I successfully rooted & unlocked to T-mobile have been using it for a while
with no issues until yesterday when I had to install a new T-Mobile sim card. I got the dreaded " The process com. android. phone has stopped" I cleared all the phone cache as was recommended. But when I boot into recovery mode it comes up with android recovery instead of clockwork mod recovery. which is what I have. I wanted to
clear the cache in that as well which was recommended. I can receive calls and text and can send text but I can't
make a phone call. Can someone help me please! Thanks
Click to expand...
Click to collapse
How to install a working custom recovery again:
Flash TWRP as "AP" using ODIN while phone is connected in "DOWNLOAD" mode.
I really appreciate your iron will to use a CDMA S3 with GSM service
LS.xD said:
How to install a working custom recovery again:
Flash TWRP as "AP" using ODIN while phone is connected in "DOWNLOAD" mode.
I really appreciate your iron will to use a CDMA S3 with GSM service
Click to expand...
Click to collapse
If he is on the locked bootloader flashing a custom recovery will brick his device. I understand your intentions are good but by doing so this will not help
Sent from my Nexus 5
---------- Post added at 09:43 AM ---------- Previous post was at 09:42 AM ----------
H779 said:
Sorry I didn't get back sooner. working crazy hours. So is there and option here. I got this bootloader from this site. I think from chainfire.
Click to expand...
Click to collapse
Post a screen shot of your about phone screen, if its on the 4.3 ML1 or 4.4.2 NE1 bootloader you do not have the option of flashing a custom recovery other than safestrap
Sent from my Nexus 5
ShapesBlue said:
If he is on the locked bootloader flashing a custom recovery will brick his device. I understand your intentions are good but by doing so this will not help
Sent from my Nexus 5
---------- Post added at 09:43 AM ---------- Previous post was at 09:42 AM ----------
Post a screen shot of your about phone screen, if its on the 4.3 ML1 or 4.4.2 NE1 bootloader you do not have the option of flashing a custom recovery other than safestrap
Sent from my Nexus 5
Click to expand...
Click to collapse
My bad. If you're still on Android 4.1.1 or Android 4.1.2 you can permanently unlock your bootloader. Which firmware is actually installed?
Thanks I don't know why this occurred just because I changed sims . I'm not that savey just persistent Btw your message only says flash TWRP usind AP in odin. the link is missing when I log in to XDA on my PC the link shows up only on my Gmail.
H779 said:
Thanks I don't know why this occurred just because I changed sims . I'm not that savey just persistent Btw your message only says flash TWRP usind AP in odin. the link is missing when I log in to XDA on my PC the link shows up only on my Gmail.
Click to expand...
Click to collapse
As posted previously:
Post a screen shot of your about phone screen, if its on the 4.3 ML1 or 4.4.2 NE1 bootloader you do not have the option of flashing a custom recovery other than safestrap
Sent from my Nexus 5
version 4.0.4, baseband I535VRLHE, build number IMM76DI535VRALHE
H779 said:
version 4.0.4, baseband I535VRLHE, build number IMM76DI535VRALHE
Click to expand...
Click to collapse
Wow, still on ICS. Might be because your on such an old bootloader
Sent from my Nexus 5
I guess I'm confused, When I originally Unlocked this verizon phone to use a T-Mobile sim I flashed a new bootloader about a week ago Does the original bootloader still exist and is flashed over? hope this isn't a stupid question.
H779 said:
version 4.0.4, baseband I535VRLHE, build number IMM76DI535VRALHE
Click to expand...
Click to collapse
Pretty good You can use EZ unlock 1.2 to unlock your bootloader and then install the TWRP I mentioned earlier
---------- Post added at 05:08 PM ---------- Previous post was at 05:01 PM ----------
H779 said:
I guess I'm confused, When I originally Unlocked this verizon phone to use a T-Mobile sim I flashed a new bootloader about a week ago Does the original bootloader still exist and is flashed over? hope this isn't a stupid question.
Click to expand...
Click to collapse
May you post a link to the "bootloader" you think you flashed earlier?
I deleteted it because I didn't think I needed any longer. I remember it being something like : vrzbootchain.tar thats all I remember
Lubeck can you please send me the TWRP link. All that came through was " Flash TWRP using AP in Odin Thanks
LS.xD said:
How to install a working custom recovery again:
Flash TWRP as "AP" using ODIN while phone is connected in "DOWNLOAD" mode.
I really appreciate your iron will to use a CDMA S3 with GSM service
Click to expand...
Click to collapse
Why? Link is working...
BUT I don't know what exactly you did with your bootloader, so I can't guarantee its compatible.
I just received notification for OTA update. (134MB)
BLU_p0010UU_V11_GENERIC_5.1_20151123-0956
1. Stagefright patch
2. google security patches
3. Mcafee security 2015
4.Other bug fixes
Anyone tried it ?
i want to know if it is going to try and stick me with mcafee. . . happy to see an update, though!
you can remove mcafee after the update.
Can anyone upload ota?
Yes please. I'm rooted and it won't let me download the update. If someone could even offer a system dump that would be helpful.
---------- Post added at 02:29 PM ---------- Previous post was at 02:28 PM ----------
If only for the stage fright patch
---------- Post added at 02:32 PM ---------- Previous post was at 02:29 PM ----------
Also if someone could offer a system dump of the newest upgrade I'd be more than willing to cook up a rooted stock rom. I know I haven't been on the forums much lately at all but I remember working on stuff back in the t-mobile g1 days
Rooting after the update
I only first tried to root my Blu Pure XL after the update was installed. I find that the boot loader is locked and I can not find a way to gain access. I am not sure if the update added this major inconvenience but I suspect it did as the rooting method as described will not work for me at all. Any thoughts or suggestions?
blacksmithjk said:
I only first tried to root my Blu Pure XL after the update was installed. I find that the boot loader is locked and I can not find a way to gain access. I am not sure if the update added this major inconvenience but I suspect it did as the rooting method as described will not work for me at all. Any thoughts or suggestions?
Click to expand...
Click to collapse
ive updated with every ota and root works fine... boot loader isnt locked... try to flash twrp via fastboot, and if that doesnt work enable developer options in settings and "Enable OEM unlock"
but like i said Ive flashed back to stock FW with SP tool (compete stock boot, recovery, and system ver .11) so if any update would have locked BL it would have locked mine... but it didnt, doesnt, and hasnt...
Follow the thread about twrp... it gives you very easy to follow directions.
Yeah, I did the OTA update before rooting, and it didn't want to allow me after the OTA update.
I downloaded multiple files from all over the place, placed them in a "root" subfolder and it still seemed impossible.
Got it done AFTER 3 days
so...
using flashboot to flash twrp, after the OTA,
then using twrp to flash the SU.zip took 3 days?
what files and "root folder" are you referring to?
Sounds like sever case of lack of reading or lack or user error;
But Im glad you stuck with it long enough to get it working...
ArconHadron said:
Yeah, I did the OTA update before rooting, and it didn't want to allow me after the OTA update.
I downloaded multiple files from all over the place, placed them in a "root" subfolder and it still seemed impossible.
Got it done AFTER 3 days
Click to expand...
Click to collapse
tbirdguy said:
ive updated with every ota and root works fine... boot loader isnt locked... try to flash twrp via fastboot, and if that doesnt work enable developer options in settings and "Enable OEM unlock"
but like i said Ive flashed back to stock FW with SP tool (compete stock boot, recovery, and system ver .11) so if any update would have locked BL it would have locked mine... but it didnt, doesnt, and hasnt...
Follow the thread about twrp... it gives you very easy to follow directions.
Click to expand...
Click to collapse
tbirdguy said:
so...
using flashboot to flash twrp, after the OTA,
then using twrp to flash the SU.zip took 3 days?
what files and "root folder" are you referring to?
Sounds like sever case of lack of reading or lack or user error;
But Im glad you stuck with it long enough to get it working...
Click to expand...
Click to collapse
Thanks, hardest part was actually getting phone to boot into flash mode.
Specifically, holding Power plus Volume+ is fine, but you have to let go of the power button first, then the Volume+.
Plus, I had to adb reboot before getting the TWRP rom to flash properly....
Not my best effort, but findintg SPECIFIC instructions were difficult, and had to manually search for latest fastflash and TWRP......v2.8.6.0
ArconHadron said:
Thanks, hardest part was actually getting phone to boot into flash mode.
Specifically, holding Power plus Volume+ is fine, but you have to let go of the power button first, then the Volume+.
Plus, I had to adb reboot before getting the TWRP rom to flash properly....
Not my best effort, but findintg SPECIFIC instructions were difficult, and had to manually search for latest fastflash and TWRP......v2.8.6.0
Click to expand...
Click to collapse
Fastflash?
Manually search?
Under the Development heading there are 5 topics, 2 of which are for TWRP recoveries (3.0.2 is buggy but works, just takes long time to wipe and restore; and theres SOOOOO many posts about how to flash them and how to use SP Flash Tool... so once again; glad you stuck with it, but Im still going with user error due to fail to RTFM
I'm trying to get my phone ready to install this rom ( http://forum.xda-developers.com/gal...xtrestolite-deodexed-mod-edition-1-0-t3094423 ) and my current specs are: Model: SM-G920V, Android Version: 5.0.2. Baseband: OC3, Kernel version: 3.10.61, Build: OC3, Hardware: MDF v2.0 R2, VPN 1.4 R4.
This is a virgin untouched phone from the day S6 released. I wanted to make sure I do this right as I remember messing up my S5 upgrading the build to something nobody could root and you couldn't go back to the old version. I'd like to not repeat that with this phone
Also is it possible to get the newest MM beta perhaps? Like with this rom ( http://forum.xda-developers.com/showpost.php?p=65588463&postcount=9473 )
Thanks.
After 30+ views and 0 replies I decided to try for myself. I found pingpongroot and did that. Rooted successfully. Then I downloaded twrp manager and tried to install the newest of that. It says it installed successfully and asked me to reboot. I rebooted and now I'm stuck at a bright blue start up failed screen.
Any idea how to fix this?
I was typing up something as you posted that lol. Oh well.
You were on a winner with ping pong (root without voiding warranty), but you've blown that now by flashing twrp.
Best bet now would be to flash latest 5.1.1 stock ROM via odin, then install arter97s modded version of twrp 3.0.0-0 (V13) and SuperSU 2.68 to get you up to date and wait for marshmallow.
Or just flash the older twrp 2.8.something as is now to hopefully just get you up and running again.
Latest official twrp is pretty much broken currently.
Edit: scratch that, arters mod won't work on your phone. Just find an older 2.8 version of twrp for your phone and try that.
Sent from my SM-G920I using Tapatalk
self_slaughter said:
I was typing up something as you posted that lol. Oh well.
You were on a winner with ping pong (root without voiding warranty), but you've blown that now by flashing twrp.
Best bet now would be to flash latest 5.1.1 stock ROM via odin, then install arter97s modded version of twrp 3.0.0-0 (V13) to get you up to date and wait for marshmallow.
Or just flash the older twrp 2.8.something as is now to hopefully just get you up and running again.
Latest official twrp is pretty much broken currently.
Sent from my SM-G920I using Tapatalk
Click to expand...
Click to collapse
How should I go about flashing twrp 2.8? I can use volume down + home + power to get to the downloading screen... Is there an odin way to install 2.8?
ElementalWindX said:
How should I go about flashing twrp 2.8? I can use volume down + home + power to get to the downloading screen... Is there an odin way to install 2.8?
Click to expand...
Click to collapse
Yeah odin is the usual way of installing it. Find the .tar or .tar.md5 and flash that via odin.
Sent from my SM-G920I using Tapatalk
self_slaughter said:
Yeah odin is the usual way of installing it. Find the .tar or .tar.md5 and flash that via odin.
Sent from my SM-G920I using Tapatalk
Click to expand...
Click to collapse
What would be wrong with using 3.0.1 or 3.0? They are only working with MarshMellow at the moment?
Ahhh. Just read up. Your bootloader is locked. No custom recoveries will work.
You should of just stopped at ping pong. It was your only way of getting root. (Which was what I was originally going to suggest lol)
This thread may be of some help recovering.
http://forum.xda-developers.com/verizon-galaxy-s6/help/samsung-s6-sm-g920v-bricked-t3129928
Sent from my SM-G920I using Tapatalk
self_slaughter said:
Ahhh. Just read up. Your bootloader is locked. No custom recoveries will work.
You should of just stopped at ping pong. It was your only way of getting root. (Which was what I was originally going to suggest lol)
This thread may be of some help recovering.
http://forum.xda-developers.com/verizon-galaxy-s6/help/samsung-s6-sm-g920v-bricked-t3129928
Sent from my SM-G920I using Tapatalk
Click to expand...
Click to collapse
Sorry for sounding so newb but I rooted the phone so doesn't that mean it's unlocked? I read that thread and I'm downloading those 2 zip files to attempt to use odin to flash one of them. Unfortunately the mirror is so 1980s slow it will take 6 hours to download each file.
Ping pong used a completely different exploit to get root. Now you need a custom recovery or kernel to get root, both of which you can't do with a locked bootloader.
What did you flash originally? Hopefully you can just flash stock recovery back and stay on 5.0.2 to keep root.
If you are forced to update you may never get root again unless a new exploit is found.
Sorry, I haven't had much to do with a locked bootloader so can't be a great help. Do plenty of reading while whatever you are downloading is going and hope you can find a way to stay on 5.0.2
Sent from my SM-G920I using Tapatalk
---------- Post added at 06:06 AM ---------- Previous post was at 05:52 AM ----------
Try this link. It is the same firmware you are on currently and I seem to be maxing out my connection downloading it.
http://stockfirmware.androidrootz.com/download-all_vzw_g920vvru1aoc3_g920vvzw1aoc3_cl4318389_qb4424773_rev02_user_low_ship-zip/
Flash that via odin and if it works, You should be able to run ping pong again and keep root at least.
self_slaughter said:
Ping pong used a completely different exploit to get root. Now you need a custom recovery or kernel to get root, both of which you can't do with a locked bootloader.
What did you flash originally? Hopefully you can just flash stock recovery back and stay on 5.0.2 to keep root.
If you are forced to update you may never get root again unless a new exploit is found.
Sorry, I haven't had much to do with a locked bootloader so can't be a great help. Do plenty of reading while whatever you are downloading is going and hope you can find a way to stay on 5.0.2
Sent from my SM-G920I using Tapatalk
---------- Post added at 06:06 AM ---------- Previous post was at 05:52 AM ----------
Try this link. It is the same firmware you are on currently and I seem to be maxing out my connection downloading it.
http://stockfirmware.androidrootz.com/download-all_vzw_g920vvru1aoc3_g920vvzw1aoc3_cl4318389_qb4424773_rev02_user_low_ship-zip/
Flash that via odin and if it works, You should be able to run ping pong again and keep root at least.
Click to expand...
Click to collapse
Thanks I got that file and did successfully flash it with odin and did re-root with pingpong. How do I get my phone to the next step to get a rom loaded? I tried using twrp manager to load 2.8.7.2 and that just gave me the same result of the same blue screen. I'm reflashing back to the original rom right now sigh.
Ahh good times, that worked out well then. No custom recovery will work on your phone unless they find a way to unlock the bootloader. As for roms, check the Verizon s6 section. There was some there although most are probably abandoned by now since not many people would still have 5.0.2. Can't really help you on that front.
Sent from my SM-G920I using Tapatalk
self_slaughter said:
Ahh good times, that worked out well then. No custom recovery will work on your phone unless they find a way to unlock the bootloader. As for roms, check the Verizon s6 section. There was some there although most are probably abandoned by now since not many people would still have 5.0.2. Can't really help you on that front.
Sent from my SM-G920I using Tapatalk
Click to expand...
Click to collapse
So what version allows an unlocked boot loader and whats the best way to upgrade to that? The person whose rom I quoted in post #1 says they recommend using twrp.
ElementalWindX said:
So what version allows an unlocked boot loader and whats the best way to upgrade to that? The person whose rom I quoted in post #1 says they recommend using twrp.
Click to expand...
Click to collapse
It's your specific phone that is locked. (SM-G920V). Big difference to 920F or 920I etc...
Not much you can do about it unfortunately. Lucky you even got root.
Sent from my SM-G920I using Tapatalk
self_slaughter said:
It's your specific phone that is locked. (SM-G920V). Big difference to 920F or 920I etc...
Not much you can do about it unfortunately. Lucky you even got root.
Sent from my SM-G920I using Tapatalk
Click to expand...
Click to collapse
wtf? So Verizon phones sold in America are screwed out of the ability to do roms? Thats a first for me. This sucks.
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.
Title kind of stays it all. I have a Google Play Store phone, unlocked the bootloader and rooted. Do I need to unroot to take the update VZW says is coming today? Unroot and re-lock the bootloader?
I do not have TWRP installed. Should I install that and just wait for a flashable .zip?
Thanks for any help!
Coronado is dead said:
Title kind of stays it all. I have a Google Play Store phone, unlocked the bootloader and rooted. Do I need to indoor to take the update VZW says is coming today? Indoor and unlock the bootloader?
I do not have TWRP installed. Should I install that and just wait for a flashable .zip?
Thanks for any help!
Click to expand...
Click to collapse
Your post is confusing. You have a Google model but you want to take a Verizon update? That won't happen via OTA. If you're rooted with or without TWRP an OTA will fail. You'll need to download a stock file and flash it manually. Then you can update from it. For example, I flashed a stock Google rom to my Verizon model and immediately received an OTA. Then I flashed TWRP and rooted again.
What do you mean by "do I need to indoor"?
Sent from my Pixel using Tapatalk
---------- Post added at 06:44 PM ---------- Previous post was at 06:43 PM ----------
No need to lock the bootloader.... Ever. Unless you need to send in for warranty.
Sent from my Pixel using Tapatalk
joshw0000 said:
Your post is confusing. You have a Google model but you want to take a Verizon update? That won't happen via OTA. If you're rooted with or without TWRP an OTA will fail. You'll need to download a stock file and flash it manually. Then you can update from it. For example, I flashed a stock Google rom to my Verizon model and immediately received an OTA. Then I flashed TWRP and rooted again.
What do you mean by "do I need to indoor"?
Sent from my Pixel using Tapatalk
---------- Post added at 06:44 PM ---------- Previous post was at 06:43 PM ----------
No need to lock the bootloader.... Ever. Unless you need to send in for warranty.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Hey, thanks for replying
1. Indoor was an autocorrect I guess, was on my phone before. I meant: 'do I need to unroot.' I'll correct that now.
2. Well, I have a Google Play phone, but a Verizon SIM in it. As such, I receive the Verizon specific firmwares, that's how the Pixels pull (I think). My current build is NDE63X, which as I understand it is the Verizon version of the last update. I've never flashed a full ROM (well, not on this phone ), so the phone pulled it all on its own.
Coronado is dead said:
Hey, thanks for replying
1. Indoor was an autocorrect I guess, was on my phone before. I meant: 'do I need to unroot.' I'll correct that now.
2. Well, I have a Google Play phone, but a Verizon SIM in it. As such, I receive the Verizon specific firmwares, that's how the Pixels pull (I think). My current build is NDE63X, which as I understand it is the Verizon version of the last update. I've never flashed a full ROM (well, not on this phone ), so the phone pulled it all on its own.
Click to expand...
Click to collapse
Crap you're right. I flashed NDE63V last night and let my phone update.... back to NDE63X.
You can download firmwares here - https://developers.google.com/android/images
Sent from my Pixel using Tapatalk
Download firmware you want to flash from https://developers.google.com/android/images and flash it with http://forum.xda-developers.com/pixel/development/tool-skipsoft-android-toolkit-google-t3482761
Coronado is dead said:
Title kind of stays it all. I have a Google Play Store phone, unlocked the bootloader and rooted. Do I need to unroot to take the update VZW says is coming today? Unroot and re-lock the bootloader?
I do not have TWRP installed. Should I install that and just wait for a flashable .zip?
Thanks for any help!
Click to expand...
Click to collapse
I suggest following the how to apply OTA via fastboot guide.
I downloaded the OTA, used adb sideload to apply it. Let the phone reboot and finish the update. Then **BOOTED** twrp and flashed SuperSU 2.78 sr5
VadimTk said:
Download firmware you want to flash from https://developers.google.com/android/images and flash it with http://forum.xda-developers.com/pixel/development/tool-skipsoft-android-toolkit-google-t3482761
Click to expand...
Click to collapse
thanku
Tried to use adb sideload to install this update. Got an error that says "Could not find 'META-INF/com/google/android/update-binary" in the zip file. Opening the zip in winrar shows that it is absolutely NOT structured with that format, but after downloading the update multiple times I can confidently say that it isn't an issue of file corruption. I am guessing it is because I have TWRP installed and it is expecting stock recovery, but I am not 100% sure how to resolve this.
I have a verizon phone unlocked by depixel8 and I just really don't want to flash any stock image for fear that it would relock and force me to take the new OTA during initial setup.
renegadeone8 said:
Tried to use adb sideload to install this update. Got an error that says "Could not find 'META-INF/com/google/android/update-binary" in the zip file. Opening the zip in winrar shows that it is absolutely NOT structured with that format, but after downloading the update multiple times I can confidently say that it isn't an issue of file corruption. I am guessing it is because I have TWRP installed and it is expecting stock recovery, but I am not 100% sure how to resolve this.
I have a verizon phone unlocked by depixel8 and I just really don't want to flash any stock image for fear that it would relock and force me to take the new OTA during initial setup.
Click to expand...
Click to collapse
I have an unlocked VZW Pixel as well, you can flash the OTA update via adb sideload with the factory recovery just fine. Your bootloader will stay unlocked unless you lock it yourself. The only difference is with the latest update, you can't unlock it if you do lock it. So just leave it unlocked and you're fine. As was already said, let it boot, then flash root again and you're back in business.
Thanks
jjlangen said:
I have an unlocked VZW Pixel as well, you can flash the OTA update via adb sideload with the factory recovery just fine. Your bootloader will stay unlocked unless you lock it yourself. The only difference is with the latest update, you can't unlock it if you do lock it. So just leave it unlocked and you're fine. As was already said, let it boot, then flash root again and you're back in business.
Click to expand...
Click to collapse
I am pretty sure having TWRP was the issue. I couldn't for the life of me get the OTA to flash, but it flashed the full stock image (replacing TWRP with stock recovery in the process) just fine. I realized after I wrote this that manually flashing wouldn't affect the bootloader and just went for it.
I don't even really need TWRP on this phone for now, I really only unlocked for when Cyanogen gets ported and incase any cool custom Kernels come out, but am just going to leave it stock for now.