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.
Related
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?
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
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.
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?
I'll be switching to Project Fi soon from ATT. With the switch I'll lose my only reason for being rooted (wifi hotspot) since Fi offers hotspot for no extra charge. Am I able to install OTA updates with an unlocked bootloader if everything else is stock (ie. not rooted)?
geicogecko said:
I'll be switching to Project Fi soon from ATT. With the switch I'll lose my only reason for being rooted (wifi hotspot) since Fi offers hotspot for no extra charge. Am I able to install OTA updates with an unlocked bootloader if everything else is stock (ie. not rooted)?
Click to expand...
Click to collapse
I think you should be able to
Sent from my Pixel 2 XL using Tapatalk
You cannot take OTA updates normally with an unlocked bootloader. The phone will download the update, but the update will fail.
You CAN update manually using either OTA or factory images from here and following my guide here.
To sideload OTA images using either stock recovery or TWRP, follow the instructions here.
Excellent, thank you. I'd rather not wipe the phone so I guess I'll settle for sideloading OTAs. And it would be nice to be able to root later on if I decide I need to.
geicogecko said:
Excellent, thank you. I'd rather not wipe the phone so I guess I'll settle for sideloading OTAs. And it would be nice to be able to root later on if I decide I need to.
Click to expand...
Click to collapse
The nice thing about getting an OTA is that it installs in the background and a quick reboot to finish the update. Why not start fresh with a full wipe since you're changing carriers. It's not super difficult to get it set up again and now you have a clean install. I say that because I'm about to suggest you relock the bootloader and see how it runs. You obviously have the oem switch enabled so its really easy to go back and unlock if you so desire. Just a thought. I liked Project Fi when I had it but it didn't make financial sense in my case with a family plan. Good luck.
geicogecko said:
Excellent, thank you. I'd rather not wipe the phone so I guess I'll settle for sideloading OTAs. And it would be nice to be able to root later on if I decide I need to.
Click to expand...
Click to collapse
Just for ****s and giggles, I tried installing the OTA zip through TWRP. Worked like a charm.
Please note that if you do this, the kernel and recovery will revert to stock, so you'll have to boot TWRP via fastboot and reflash.
socal87 said:
Just for ****s and giggles, I tried installing the OTA zip through TWRP. Worked like a charm.
Please note that if you do this, the kernel and recovery will revert to stock, so you'll have to boot TWRP via fastboot and reflash.
Click to expand...
Click to collapse
Did you let it reboot on its own, or did you manually boot into TWRP, find the file and flash it that way?
k.s.deviate said:
Did you let it reboot on its own, or did you manually boot into TWRP, find the file and flash it that way?
Click to expand...
Click to collapse
I'm not sure I understand your question. I flashed the OTA file in recovery using TWRP. There is no way to flash things in recovery without rebooting...
socal87 said:
I'm not sure I understand your question. I flashed the OTA file in recovery using TWRP. There is no way to flash things in recovery without rebooting...
Click to expand...
Click to collapse
After the OTA downloaded, did you just reboot when it asked you to, or, did you manually boot into TWRP and find the OTA file to flash. OR, did you download the OTA from an third party and flash that way.
k.s.deviate said:
After the OTA downloaded, did you just reboot when it asked you to, or, did you manually boot into TWRP and find the OTA file to flash. OR, did you download the OTA from an third party and flash that way.
Click to expand...
Click to collapse
I downloaded the OTA directly from https://developers.google.com/android/ota, then rebooted into TWRP and flashed the zip.
I'm on stock software with the exception of Magisk and Flash kernel, so OTAs always fail. Thus, I have Automatic System Updates turned off in Developer Options.
Regardless of how you do it, the OTA will always overwrite /boot, so you'll lose custom kernel and recovery.
bobby janow said:
The nice thing about getting an OTA is that it installs in the background and a quick reboot to finish the update. Why not start fresh with a full wipe since you're changing carriers. It's not super difficult to get it set up again and now you have a clean install. I say that because I'm about to suggest you relock the bootloader and see how it runs. You obviously have the oem switch enabled so its really easy to go back and unlock if you so desire. Just a thought. I liked Project Fi when I had it but it didn't make financial sense in my case with a family plan. Good luck.
Click to expand...
Click to collapse
I may do this eventually. I want to see what having a non-rooted phone is like first. I haven't had a non-rooted phone in probably eight years. If I find out I really don't need root for anything, I may relock the bootloader.
socal87 said:
Just for ****s and giggles, I tried installing the OTA zip through TWRP. Worked like a charm.
Please note that if you do this, the kernel and recovery will revert to stock, so you'll have to boot TWRP via fastboot and reflash.
Click to expand...
Click to collapse
Wait... do you mean you actually flashed the downloaded, official OTA zip using TWRP over a rooted OS with no issues at all?... Interesting. Was that flashed OTA, a security patch only?
Sent from my Moto Z2 Play using XDA Labs
The Analog Kid said:
Wait... do you mean you actually flashed the downloaded, official OTA zip using TWRP over a rooted OS with no issues at all?... Interesting. Was that flashed OTA, a security patch only?
Sent from my Moto Z2 Play using XDA Labs
Click to expand...
Click to collapse
When the 9.0 update came out, I installed that via TWRP. Again, as noted, this will install it to both slots, and when it boots, it will boot via the other slot.
So, for instance, if you happen to be on slot A, and you install the OTA, it installs the stock kernel to slot B, and boots via that slot - stock kernel, no Magisk or TWRP. After it boots , when it is "Finishing update", it installs the stock kernel to slot A.
So, every time you flash an OTA, you need to let it boot, then reboot into bootloader, boot TWRP via fastboot, install TWRP, install kernel, and Magisk.
geicogecko said:
I may do this eventually. I want to see what having a non-rooted phone is like first. I haven't had a non-rooted phone in probably eight years. If I find out I really don't need root for anything, I may relock the bootloader.
Click to expand...
Click to collapse
So... How's the non-rooted phone experience going so far? Because I can't get fully used to the experience yet (I have this phone for a month now) and coming from... well, ALL of my previous devices rooted too (about an eight year span as well). Even though the phone in question (Z2 Play) runs very smooth and plain "force-close-less" (yeah, you know root) I still don't find myself quite at home without Xposed and it's useful modules, for example... Oreo is nice indeed but, on the other hand, I also have this little tiny bit temptation for Android 9... Sure, if it ever lands on my phone in less than a year! Quite a bet.
Sent from my Moto Z2 Play using XDA Labs
---------- Post added at 10:31 PM ---------- Previous post was at 10:28 PM ----------
socal87 said:
When the 9.0 update came out, I installed that via TWRP. Again, as noted, this will install it to both slots, and when it boots, it will boot via the other slot.
So, for instance, if you happen to be on slot A, and you install the OTA, it installs the stock kernel to slot B, and boots via that slot - stock kernel, no Magisk or TWRP. After it boots , when it is "Finishing update", it installs the stock kernel to slot A.
So, every time you flash an OTA, you need to let it boot, then reboot into bootloader, boot TWRP via fastboot, install TWRP, install kernel, and Magisk.
Click to expand...
Click to collapse
... That's only if you want to preserve root, I guess? AND for Pixel devices, right?
Sent from my Moto Z2 Play using XDA Labs
The Analog Kid said:
So... How's the non-rooted phone experience going so far? Because I can't get fully used to the experience yet (I have this phone for a month now) and coming from... well, ALL of my previous devices rooted too (about an eight year span as well). Even though the phone in question (Z2 Play) runs very smooth and plain "force-close-less" (yeah, you know root) I still don't find myself quite at home without Xposed and it's useful modules, for example... Oreo is nice indeed but, on the other hand, I also have this little tiny bit temptation for Android 9... Sure, if it ever lands on my phone in less than a year! Quite a bet.
Sent from my Moto Z2 Play using XDA Labs
---------- Post added at 10:31 PM ---------- Previous post was at 10:28 PM ----------
... That's only if you want to preserve root, I guess? AND for Pixel devices, right?
Sent from my Moto Z2 Play using XDA Labs
Click to expand...
Click to collapse
Yes. If you're otherwise stock aside from an unlocked bootloader, you can sideload the OTA zip...or, copy it to internal storage, reboot to recovery, and install it that way.
If you want to keep TWRP, you'll have to boot the TWRP image after installing and rebooting, then flash TWRP. The OTA does not wipe data (obviously); it just returns everything in /boot and /system to stock.
The Analog Kid said:
So... How's the non-rooted phone experience going so far? Because I can't get fully used to the experience yet (I have this phone for a month now) and coming from... well, ALL of my previous devices rooted too (about an eight year span as well). Even though the phone in question (Z2 Play) runs very smooth and plain "force-close-less" (yeah, you know root) I still don't find myself quite at home without Xposed and it's useful modules, for example... Oreo is nice indeed but, on the other hand, I also have this little tiny bit temptation for Android 9... Sure, if it ever lands on my phone in less than a year! Quite a bet.
Click to expand...
Click to collapse
So I actually took the advice and relocked the bootloader. No issues. I think there was one app that I would've needed root for, but I can't remember what it was. I didn't use Xposed. I don't even know if it works on the Pixel. Like I said in the opening post, I only needed it to enable wifi hotspot, so others may notice it more.
Were you able to update with ota after relocking your boot loader? I tried it after and the update would install but stay at 0% then eventually fail. Any suggestions? Thanks.
ychongy13 said:
Were you able to update with ota after relocking your boot loader? I tried it after and the update would install but stay at 0% then eventually fail. Any suggestions? Thanks.
Click to expand...
Click to collapse
You should be able to install the latest OTA image using stock recovery:
https://developers.google.com/android/ota