Hey, Here is a link to the Android Oreo OTA
https://samsung.firmware.science/download?url=48993/1488/SS-N950USQS2BQK2-to-U2CQL1-UP
https://drive.google.com/open?id=1xTtsn6gcg4JEX2dYKPiXTWVhPiGPzIBn
Before you can do this build you will need to be on 2BQK2, so to get to that you need this build: https://samsung.firmware.science/download?url=48993/1488/SS-N950USQU2BQJA-to-S2BQK2-UP
ODIN for BQK2: https://androidfilehost.com/?fid=889964283620771190
this file for BQJA is on SamMobile, SamFirm, and Updato. These are OTA updates besides the flashing required in that.
UPDATE! New build has been released. It is CQL7. To get to that, flash BQK2 with Odin (linked above) then OTA from BQK2 to BQL5 then another OTA from BQL5 to CQL7.
BQK2 to BQL5: https://samsung.firmware.science/download?url=48993/1488/SS-N950USQS2BQK2-to-S2BQL5-UP
BQL5 to CQLB: https://samsung.firmware.science/download?url=48993/1488/SS-N950USQS2BQL5-to-U2CQLB-UP
BRA8 to CRB8 https://samsung.firmware.science/download?url=48993/1488/SS-N950USQS3BRA8-to-U3CRB8-UP
THIS WILL UPDATE YOUR BOOTLOADER TO V3, YOU CAN NOT DOWNGRADE
BQL5 Odin: https://samsung-firmware.org/download/Galaxy__Note8__/c7o0/VZW/N950USQS2BQL5/N950UOYN2BQL5/
Oh just a side note, this may be unstable and crash, you have been warned.
This is a discord server with things as they come out. discord.gg/4uxusu8
thanks to thesbros for making the website
(https://i.imgur.com/oBT3bTA.jpg)
(https://i.imgur.com/f8CU1IP.jpg)
mweinbach said:
Hey, Here is a link to the Android Oreo OTA
https://samsung.firmware.science/download?url=48993/1488/SS-N950USQS2BQK2-to-U2CQL1-UP
Before you can do this build you will need to be on 2BQK2, so to get to that you need this build: https://samsung.firmware.science/download?url=48993/1488/SS-N950USQU2BQJA-to-S2BQK2-UP
ODIN for BQK2: https://drive.google.com/uc?id=19gW_CxUf2HdL4UYyxTkyOnBY8cluRIVS&export=download
this file for BQJA is on SamMobile, SamFirm, and Updato. These are OTA updates besides the flashing required in that.
I currently have an S8 on the Oreo beta and will be buying a Note8 this weekend because of this. I AM SO EXCITED!
Oh just a side note, this may be unstable and crash, you have been warned.
Click to expand...
Click to collapse
How does one go about flashing this? I'm currently on Sprints latest update
mweinbach said:
Hey, Here is a link to the Android Oreo OTA
https://samsung.firmware.science/download?url=48993/1488/SS-N950USQS2BQK2-to-U2CQL1-UP
Before you can do this build you will need to be on 2BQK2, so to get to that you need this build: https://samsung.firmware.science/download?url=48993/1488/SS-N950USQU2BQJA-to-S2BQK2-UP
ODIN for BQK2: https://drive.google.com/uc?id=19gW_CxUf2HdL4UYyxTkyOnBY8cluRIVS&export=download
this file for BQJA is on SamMobile, SamFirm, and Updato. These are OTA updates besides the flashing required in that.
I currently have an S8 on the Oreo beta and will be buying a Note8 this weekend because of this. I AM SO EXCITED!
Oh just a side note, this may be unstable and crash, you have been warned.
Click to expand...
Click to collapse
And again thanks to ..... lol
This is the unlocked version ???
Sent from my SM-N950U1 using Tapatalk
Del
powerstroke said:
How does one go about flashing this? I'm currently on Sprints latest update
Click to expand...
Click to collapse
1. Download Odin and flash this https://drive.google.com/uc?id=19gW_CxUf2HdL4UYyxTkyOnBY8cluRIVS&export=download
1.5 In CSC use HOME_CSC to keep data, normal to wipe
2. Download this file: https://samsung.firmware.science/download?url=48993/1488/SS-N950USQS2BQK2-to-U2CQL1-UP
3. If you have an SD card, transfer that to your Sd carz
4. Boot into recovery
5.SD: select update from sd card then select your OTA called update.zip
5.ADB: on your phone select sideload over adb then type adb sideload update.zip (replace that update.zip with full file directory)
nexus6r3plicant01 said:
This is the unlocked version ???
Sent from my SM-N950U1 using Tapatalk
Click to expand...
Click to collapse
N950U, so kinda but no, not really. If you set your CSC to A then yah, if not it has carrier bloat.
mweinbach said:
1. Download Odin and flash this https://drive.google.com/uc?id=19gW_CxUf2HdL4UYyxTkyOnBY8cluRIVS&export=download
1.5 In CSC use HOME_CSC to keep data, normal to wipe
2. Download this file: https://samsung.firmware.science/download?url=48993/1488/SS-N950USQS2BQK2-to-U2CQL1-UP
3. If you have an SD card, transfer that to your Sd carz
4. Boot into recovery
5.SD: select update from sd card then select your OTA called update.zip
5.ADB: on your phone select sideload over adb then type adb sideload update.zip (replace that update.zip with full file directory)
Click to expand...
Click to collapse
I'm already on sprints latest. That ok or do I need to downgrade before doing update.zip in recovery? Any mirrors for U2CQL1? Every time I try to download, it fails
powerstroke said:
I'm already on sprints latest. That ok or do I need to downgrade before doing update.zip in recovery? Any mirrors for U2CQL1? Every time I try to download, it fails
Click to expand...
Click to collapse
You need to be on BQK2 as linked in OP
Been downloading that ota file for 15 min and only at 1 percent lol. Thanks for this tho. Can't wait to see if this works.
jaceypoo said:
Been downloading that ota file for 15 min and only at 1 percent lol. Thanks for this tho. Can't wait to see if this works.
Click to expand...
Click to collapse
Uploading a mirror as i type this.
jaceypoo said:
Been downloading that ota file for 15 min and only at 1 percent lol. Thanks for this tho. Can't wait to see if this works.
Click to expand...
Click to collapse
I seriously just got to about 750 mb downloaded of the file and it just stops and starts over. Can't get it downloaded? What the heck lol
I was at 12 percent and the same thing happened to me lol. I'll just wait for the mirror.
Somehow, after 4 attempts at downloading, it worked and only took ~5 mins. everything appears to be in the zip file. I loaded the BK2 file (never got cell signal, and had a lot of strange things in settings) and am applying the update now. Hopefully this doesn't screw up anything. with the BK2 my settings showed custom for the status though, so not sure if I just screwed myself out of Knox stuff.
---------- Post added at 10:14 PM ---------- Previous post was at 09:35 PM ----------
Looks like it's working, some things I noted:
I had a few strange apps in my service folder (BoA and some games)
Samsung connect was causing a bunch of force closures.
Even though I was on unlocked before this, I ended up on Verizon (my carrier).
Everything else seems normal, and had I done a wipe I'd probably be in even better shape. Might to a whole tomorrow.
Sent from my SM-N950U using Tapatalk
damn, this was sniffed out from the AT&T servers?
_Dennis_ said:
Somehow, after 4 attempts at downloading, it worked and only took ~5 mins. everything appears to be in the zip file. I loaded the BK2 file (never got cell signal, and had a lot of strange things in settings) and am applying the update now. Hopefully this doesn't screw up anything. with the BK2 my settings showed custom for the status though, so not sure if I just screwed myself out of Knox stuff.
---------- Post added at 10:14 PM ---------- Previous post was at 09:35 PM ----------
Looks like it's working, some things I noted:
I had a few strange apps in my service folder (BoA and some games)
Samsung connect was causing a bunch of force closures.
Even though I was on unlocked before this, I ended up on Verizon (my carrier).
Everything else seems normal, and had I done a wipe I'd probably be in even better shape. Might to a whole tomorrow.
Click to expand...
Click to collapse
Can u post some screenshots? Anything new in settings or design?
note3userr said:
Can u post some screenshots? Anything new in settings or design?
Click to expand...
Click to collapse
Settings is new some screen shots of it here
https://www.imgur.com/a/c0MJ2
Sent from my SM-N950U using Tapatalk
where is the odin for this? The link does not have Odin
technicalvampire said:
where is the odin for this? The link does not have Odin
Click to expand...
Click to collapse
Don't need odin for this, it's an OTA.
Just put it on your phone, and go to recovery mode and flash from update.zip or whatever.
Longcat14 said:
Don't need odin for this, it's an OTA.
Just put it on your phone, and go to recovery mode and flash from update.zip or whatever.
Click to expand...
Click to collapse
First part does...
Related
If you are rooted in V10G with Tmobile P769, then you can bypass OTA and go straight to rooted V20D JB with CWM already installed.
Here is a copy of rooted CWM back up of P769 V20D
http://forum.xda-developers.com/showpost.php?p=40775018&postcount=772
The latest lock boot loader CWM (v1.5) for JB is here.
http://forum.xda-developers.com/showpost.php?p=36620368&postcount=1
The radio update zip file is here.
http://forum.xda-developers.com/showpost.php?p=40844363&postcount=37
1) First delete the version 1.4 CWM
>>> 1. Delete /system/bootstrap directory
>>> 2. Delete /system/bin/e2fsck file
>>> 3. Rename /system/bin/e2fsck.bin file to e2fsck
2) Download and install version 1.5 CWM
3) If you have Titanium Back up, make a fresh back up.
4) Download and copy V20D back up folder to clockworkmod back up folder.
4.5) Download and copy radio.zip to SD.
5) Reset and go into CWM.
6) set the back up format to 'tar'
7) run Back up to external SD. This will give you a latest back up of you V10G.
8) run Restore from external SD and find the V20 back up folder.
8.5) run Install Zip from SD for the radio.zip file. NOTE this update takes 2-3 min. Do not panic.
9) When the opration is finished, reboot.
You should be in a fresh rooted V20D JB. Now download Titanium Back up and restore your apps.
Please thank the file contributors in their posts for their effort.
__________. _________________________________________________________________________
Original post is not related to above and removed to lessen the confusion.
removed.
mjb1994 said:
(ge.tt/547NI4f/v/0) there is the link for my whole cache including the OTA.
As for android updating, it has been 14 min and it just now finished fully booting
I will post again after I restore root
Update: I was able to successfully restore root with Voodoo OTA RootKeeper
Just like everyone else has stated although, While in SuperSU the first re-installation failed, but you just go back into the app and install it again and it successfully installs the su binaries
I find it hilarious and awesome that I haven't had to re root the phone since I got it in February and rooted with 10e (when the method was easy). I used Voodoo for 10G and now with 20D
The whole process took a good 15 min.
Click to expand...
Click to collapse
here's MJB's entire cache folder, it may or may not have the SBin.
removed.
Need the KDZ file t flash in!
csrow said:
Here is the link to the OTA zip file posted by Lelus.
https://dl.dropboxusercontent.com/u/54534987/ad6729f33f2f.ota_update_V10g_MR_FINAL_to_V20d_JB_QA_FINAL.zip
Just need to find the other file to see if it can trigger the update.
Click to expand...
Click to collapse
hi. I can't find original post of this. I d-loaded zip but don't know how to apply properly without losing root. can you either point me to the thread or tell me if I should just use voodoo then flash with CWM?
removed.
I have restored the rooted backup. Works great except for loss of service. The update included new radio. Anyone able to make a flash able zip?
Sent from my Nexus 4 using Xparent Skyblue Tapatalk 2
Somairotevoli said:
I have restored the rooted backup. Works great except for loss of service. The update included new radio. Anyone able to make a flash able zip?
Sent from my Nexus 4 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Not sure if there is a way to upgrade radio via cwm. You can try replacing /system/bin/rild to one from ics
TFT_xKripple said:
here's MJB's entire cache folder, it may or may not have the SBin.
Click to expand...
Click to collapse
where ? no link
Well, I was going to write and tell people I can't get the OTA update and also seem to be unable to reinstall the stock apps so it will pick up the OTA update (rooted with 10g from another user), but....NEVER MIND! Will try this method and see if it works.
One question - in the instructions it says delete 1.4. Ok, from the link page I get that, but curious....wouldn't installing 1.5 just erase and overwrite 1.4 anyway? Why the need to delete it, other than just having a clean install? Doesn't matter to me really, just curious.
did everything you said below and I got the MD5 mismatch! It aborted the JB update in CWM. . and suggestions?
csrow said:
If you are rooted in V10G with Tmobile P769, then you can bypass OTA and go straight to rooted V20D JB with CWM already installed.
Here is a copy of rooted CWM back up of P769 V20D
http://forum.xda-developers.com/showpost.php?p=40775018&postcount=772
The latest lock boot loader CWM (v1.5) for JB is here.
http://forum.xda-developers.com/showpost.php?p=36620368&postcount=1
1) First delete the version 1.4 CWM
2) Download and install version 1.5 CWM
3) If you have Titanium Back up, make a fresh back up.
4) Download and copy V20D back up folder to clockworkmod back up folder.
5) Reset and go into CWM.
6) set the back up format to 'tar'
7) run Back up to external SD. This will give you a latest back up of you V10G.
8) run Restore from external SD and find the V20 back up folder.
9) When the restore is finished, reboot.
You should be in a fresh rooted V20D JB. Now download Titanium Back up and restore your apps.
Enjoy.
__________. _________________________________________________________________________
Original old post : IGNORE
I am looking for a file which I think is needed for the JB update to occur for Tmobile 769.
The actual OTA ZIP file has been already posted but I am looking for the file
/sbin/recovery.
If you are rooted and have received "OTA is ready message", before you update your phone, please look for the above file and post it here for us.
TIA
Click to expand...
Click to collapse
Nathan.7118391 said:
did everything you said below and I got the MD5 mismatch! It aborted the JB update in CWM. . and suggestions?
Click to expand...
Click to collapse
I've had this happen on my nexus 7 before. Redownload the file and copy it over again. Something got fudged up while moving it around.
---------- Post added at 10:40 PM ---------- Previous post was at 10:39 PM ----------
Prof24 said:
Well, I was going to write and tell people I can't get the OTA update and also seem to be unable to reinstall the stock apps so it will pick up the OTA update (rooted with 10g from another user), but....NEVER MIND! Will try this method and see if it works.
One question - in the instructions it says delete 1.4. Ok, from the link page I get that, but curious....wouldn't installing 1.5 just erase and overwrite 1.4 anyway? Why the need to delete it, other than just having a clean install? Doesn't matter to me really, just curious.
Click to expand...
Click to collapse
Im pretty sure installing 1.5 over 1.4 is totally fine(I did). Never hurts to be too safe though.
1) You may be able to just install V1.5 on top of V1.4. I don't know. It's just two deletes and one rename to get rid of V1.4.
2) If you are getting MD5 mismatch, make sure you do not rename the file directory. Try downloading again and you can also check using an external MD5 checker app.
Does this flash the radios too? Those are also needed.
Everything seems to work fine without flashing baseband.
Sent from my LG-P769 using xda premium
kevev said:
Does this flash the radios too? Those are also needed.
Click to expand...
Click to collapse
Yes, the radio seems fine. It looks like the 4 radio fls files were patched during the update. Actually, the signal level has improved around -5 dB. Just make sure you turn off the wi-fi calling option from the set up.
If you leave the option on, it will keep on try to turn off the radio.
P.S. - Anyone know how to get rid of Quick slide apps on the notification area?
So are we saying this CWM zip does not flash the radios?
It would be good to flash the new radios. It may help with cell reception.
More bars does not mean better reception if you have not flashed the radios. It just means that the new software is not reading what it is expecting from radio.
Will this work for rooted 10e as well?
csrow said:
Yes, the radio seems fine. It looks like the 4 radio fls files were patched during the update. Actually, the signal level has improved around -5 dB. Just make sure you turn off the wi-fi calling option from the set up.
If you leave the option on, it will keep on try to turn off the radio.
P.S. - Anyone know how to get rid of Quick slide apps on the notification area?
Click to expand...
Click to collapse
Is there an issue with the Wi-Fi calling option on JB? I use it in my house due to bad reception, will updating cause issues? Anyone know? Thanks!
I just captured the new Sense 6 update also ...Enjoy [June 4 2014]
http://www.androidfilehost.com/?fid=23501681358542441
MD5: 317bae285618b070279b3a58b2e308e5
============================================================
Posted this in the other 4.4.2 thread I figured it would be easier to find in it's own thread.
http://www.androidfilehost.com/?fid=23329332407573841
MD5: 0b2648c271f52d0d543246119dfb2a8d
Flash in Stock recovery >Recovery_Cingular_US_3.17.502.3.img >> http://d-h.st/6bH
flashing stock recovery
download the above file and put it with your fastboot / adb files
boot the phone to fastboot usb
open command prompt from the fastboot folder
type
fastboot flash recovery Recovery_Cingular_US_3.17.502.3.img
fastboot erase cache
fastboot reboot-bootloader
now your ready to flash the ota.zip
Many have problems just using the stock recovery alone.. if this is your situation you need to RUU back to 3.17.502.3 First.
I posted the link here >> http://www.androidruu.com/getdownlo...13_10.38j.1157.04_release_334235_signed_2.exe
If your s-on you'll have to lock the bootloader before flashing the RUU
fastboot oem lock
Here is a mirror...
https://www.dropbox.com/s/90b05vd22i5uot3/OTAPkg.zip
AT&T 4.4.2 OTAPkg.zip
And of course if your looking to just flash the firmware, just click the link in my sig!?
clsA said:
Posted this in the other 4.4.2 thread I figured it would be easier to find in it's own thread.
http://www.androidfilehost.com/?fid=23329332407573841
MD5: 0b2648c271f52d0d543246119dfb2a8d
Flash in Stock recovery >Recovery_Cingular_US_3.17.502.3.img >> http://d-h.st/6bH
I'll post more instructions if needed
Click to expand...
Click to collapse
thank much! i downloaded the update, and then immediately realized that i didn't have stock firmware. I could have flashed the stock rev, but then i would have to wait till tomorrow to download again, since at&t won't let me.
clsA said:
Posted this in the other 4.4.2 thread I figured it would be easier to find in it's own thread.
http://www.androidfilehost.com/?fid=23329332407573841
MD5: 0b2648c271f52d0d543246119dfb2a8d
Flash in Stock recovery >Recovery_Cingular_US_3.17.502.3.img >> http://d-h.st/6bH
I'll post more instructions if needed
Click to expand...
Click to collapse
i have a big problem. i tried to flash the update zip, and it said failed. then i tried to flash what i though was the stock recov that i downloaded. but it had a bunch of number and letters. forgot that it was an IMG file. so then i rebooted and it said "android is upgrading" now when o boot i get
system ui has stopped" and "dialer has stopped" i thought i made a backup from a previous rom, but it's not there. I NEED TO GET THE PHONE BACK ON! HOW? i can access recovery but that's it.
---------- Post added at 01:09 AM ---------- Previous post was at 01:06 AM ----------
clsA said:
Posted this in the other 4.4.2 thread I figured it would be easier to find in it's own thread.
http://www.androidfilehost.com/?fid=23329332407573841
MD5: 0b2648c271f52d0d543246119dfb2a8d
Flash in Stock recovery >Recovery_Cingular_US_3.17.502.3.img >> http://d-h.st/6bH
I'll post more instructions if needed
Click to expand...
Click to collapse
i have a big problem. i tried to flash the update zip, and it said failed. then i tried to flash what i though was the stock recov that i downloaded. but it had a bunch of number and letters. forgot that it was an IMG file. so then i rebooted and it said "android is upgrading" now when o boot i get
system ui has stopped" and "dialer has stopped" i thought i made a backup from a previous rom, but it's not there. I NEED TO GET THE PHONE BACK ON! HOW? i can access recovery but that's it. i can't adb sideload either.. well i don't know how. i can enable it but how can i get the zip over to the phone. if i can do that i should be fine
vividblu2020 said:
i have a big problem. i tried to flash the update zip, and it said failed. then i tried to flash what i though was the stock recov that i downloaded. but it had a bunch of number and letters. forgot that it was an IMG file. so then i rebooted and it said "android is upgrading" now when o boot i get
system ui has stopped" and "dialer has stopped" i thought i made a backup from a previous rom, but it's not there. I NEED TO GET THE PHONE BACK ON! HOW? i can access recovery but that's it. i can't adb sideload either.. well i don't know how. i can enable it but how can i get the zip over to the phone. if i can do that i should be fine
Click to expand...
Click to collapse
don't panic if you can access recovery your fine
download a rom and push it to your phone
boot phone to recovery / go advanced / screen / timeout never
on you pc you should have a folder with adb and fastboot
put the rom you choose in the folder with adb
then open a command prompt in the same folder (shift + right click - command prompt here)
in the window type
adb devices
your serial number should be here
adb push rom.zip /sdcard/
let it copy is takes a few min and you can tell it's done
now from your phone go to install
find the rom.zip and flash
you should be up and running
Is the RUU available yet? Can someone please provide a link if it is? Thanks.
Sent from my HTC One using xda app-developers app
clsA said:
don't panic if you can access recovery your fine
download a rom and push it to your phone
boot phone to recovery / go advanced / screen / timeout never
on you pc you should have a folder with adb and fastboot
put the rom you choose in the folder with adb
then open a command prompt in the same folder (shift + right click - command prompt here)
in the window type
adb devices
your serial number should be here
adb push rom.zip /sdcard/
let it copy is takes a few min and you can tell it's done
now from your phone go to install
find the rom.zip and flash
you should be up and running
Click to expand...
Click to collapse
i"ll be sure to do that if i get in the shape again, i was so upset that i forgot i had a rom i could just flash. so im gonna put that mirror link ota on my phone, and flash it. but is their a stock i can use as a base? can i just use any stock rom, and then update my phone that way? and what about root? is their a root method for 4.4.2??
vividblu2020 said:
i"ll be sure to do that if i get in the shape again, i was so upset that i forgot i had a rom i could just flash. so im gonna put that mirror link ota on my phone, and flash it. but is their a stock i can use as a base? can i just use any stock rom, and then update my phone that way? and what about root? is their a root method for 4.4.2??
Click to expand...
Click to collapse
you seem very confused .. you can't flash any of these OTA like a rom it won't work !!
users using custom ROMs can't download latest OTA from HTC,
1) If you want to download and flash latest OTA, your device must have completely stock system partition and recovery. Every OTA update is checking MD5 of each file on system partition to ensure .apk patch can be applied. If even one of 1000 files won't match, OTA update installation will fail. In this case you need to flash the latest official update you can find (A RUU) (even one year old) and later download official OTA updates.
Click to expand...
Click to collapse
Here's the RUU I posted in another thread
http://dl3.htc.com/application/RUU_...13_10.38j.1157.04_release_334235_signed_2.exe
clsA said:
you seem very confused .. you can't flash any of these OTA like a rom it won't work !!
Here's the RUU I posted in another thread
http://forum.xda-developers.com/showpost.php?p=50573283&postcount=43
Click to expand...
Click to collapse
its not that im confused, its just that i thought the ota was the same as a rom zip. but it makes sense now that you have to be completely stock to use the ota.
anyway! thanks for the link
---------- Post added at 03:07 AM ---------- Previous post was at 02:13 AM ----------
vividblu2020 said:
its not that im confused, its just that i thought the ota was the same as a rom zip. but it makes sense now that you have to be completely stock to use the ota.
anyway! thanks for the link
Click to expand...
Click to collapse
so do i need to relock my bootloader? i am s-off and I'm downloading the link for "s-off"
vividblu2020 said:
so do i need to relock my bootloader? i am s-off and I'm downloading the link for "s-off"
Click to expand...
Click to collapse
No.
cschmitt said:
No.
Click to expand...
Click to collapse
thanksss
Have you all been able to unlock your bootloader again and flash your custom recovery after the update? And, does the Ota preserve your user data?
Sent from my HTC One using xda premium
after i flash the IMG file to fastboot using ADB what do i need to do next? cause i don't know how to flash the update zip. When I was in the bootloader I tried to get into what I thought was the flashed stock. But it showed a black screen and it was just a picture of my phone with a circular arrow inside a circle. and i had to options before i flashed the RUU and went back to stock. the only one is "unlocked" so i still have S-Off? it doesn't say tampered
Has some issues...I would advise NOT taking the update....heres one issue thats pretty big if your like me and like to take pics and use the editing features...
https://drive.google.com/file/d/0Bx5-C2BrwNVxTDNBRFNoMTFQNjg/edit?usp=sharing
Wonders_Never_Cease said:
Has some issues...I would advise NOT taking the update....heres one issue thats pretty big if your like me and like to take pics and use the editing features...
https://drive.google.com/file/d/0Bx5-C2BrwNVxTDNBRFNoMTFQNjg/edit?usp=sharing
Click to expand...
Click to collapse
I'm not seeing the issue in the video you shared. What happens to the picture?
Sent from my HTC One using Tapatalk
Photo editing functions are all broken....
guy4jesuschrist said:
I'm not seeing the issue in the video you shared. What happens to the picture?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Wonders_Never_Cease said:
Photo editing functions are all broken....
Click to expand...
Click to collapse
Is that only in the stock camera/gallery app, or in any photo editing app you've tried? I
If only stock, it wouldn't be a big deal for me since I use Snapseed, PicsArt, Photogrid, and Instagram.
Are there any other issues you've heard of or had in this new update?
Sent from my HTC One using Tapatalk
Wonders_Never_Cease said:
Photo editing functions are all broken....
Click to expand...
Click to collapse
Stock HTC One, at&t, just updated to 4.4.2 yesterday morning (approx 11am EST).
I was able to successfully edit three pictures... The first, a simple rotate, changed the pic and ovetwrote the original. The second, also from a separate folder, I cropped a pic and saved it. This created a second image of the edited content. Finally, I edited a pic from the camera pic folder, which included crop and effects. This saved correctly as a separate file as well.
Sent from my secret lair in an undisclosed mountainside.
Some people havce this issue some do not, do not know why this occurs, but its been confirmed from [email protected] in photo editing software....so we shall see
Downloads:
- G900P_PCA_Stock_Deodexed_Rooted_ROM.zip
- G900P_PCA_Stock_Modem+Bootloader.tar.md5 (Required!)
- G900P_PCA_Stock_Recovery.tar.md5 (Optional)
1. Place the ROM onto your device (use either internal or ext-sdcard).
2. Flash with TWRP.
3. Completely turn off device (important!) then boot into Download Mode and Odin flash the Modem and Bootloader. The ROM will not boot without them!
4. After a reboot the device will remain on the Sprint splash screen for 10 - 15 minutes before completely rebooting.
Tip: For faster speed turn off animations from Developer Options!
Optional:
- G900P_PCA_Batch_Debloater (Customizable)
Kernel:
- Stock kernel with chainfire's sepolicy patch and BETA SuperSu v2.74.
Notes:
- Your knox warranty bit will be tripped!
- No need to wipe prior to flashing, the ROM will automatically wipe system and userdata.
Thanks for making this dude! Any bugs you know of?
Thanks man! I've been waiting for something like this that makes the update worth trying. Can't wait to update after work.
chippinganimal said:
Thanks for making this dude! Any bugs you know of?
Click to expand...
Click to collapse
It's untouched stock, other than deodexed and root, so it should be solid.
@muniz_ri I'm happy to meet you on the s5. I'm grateful
Is the SD Card corrupted issue fixed and if so how did you do it?
pyromayniyak said:
Is the SD Card corrupted issue fixed and if so how did you do it?
Click to expand...
Click to collapse
That issue was only in the other rom by @malbert16442. This one is workjng fine.
can i go from stock rooted NK4 directly to this? is a factory reset required (or just "highly recommended")?
dmolavi said:
can i go from stock rooted NK4 directly to this? is a factory reset required (or just "highly recommended")?
Click to expand...
Click to collapse
I would recommend reseting unless your flashing a rom on the same android version.
chippinganimal said:
I would recommend reseting unless your flashing a rom on the same android version.
Click to expand...
Click to collapse
Thanks....will do. But no problems going from NK4 to PCA? Will backups from Titanium work across from 4.4.4 to 6.0.1?
dmolavi said:
Thanks....will do. But no problems going from NK4 to PCA? Will backups from Titanium work across from 4.4.4 to 6.0.1?
Click to expand...
Click to collapse
Yeah there should be no issues as long as you follw the instructions in the OP. Sorry but i dont really have experiece with using titanium backup, so i wouldnt know how that would work...
Copy that. Fingers crossed (and nandroid backup, here i come)
dmolavi said:
Copy that. Fingers crossed (and nandroid backup, here i come)
Click to expand...
Click to collapse
Your only issue maybe Applications versions. You are jumping from KK to MM. Download the newest Apps and restore only Data.
Sent from my SM-G900P using Tapatalk
hmmm i'm getting a corrupt zip file notice in TWRP when trying to flash this from internal memory.
dmolavi said:
hmmm i'm getting a corrupt zip file notice in TWRP when trying to flash this from internal memory.
Click to expand...
Click to collapse
booted up for me, at the setup screen now. Try redownloading it... maybe a corrupt download
---------- Post added at 11:56 PM ---------- Previous post was at 11:55 PM ----------
@muniz_ri maybe you could create another version of the rom that is more debloated of most of the sprint crap that is preinstalled other than that thanks for making this rom bro!
I tried 4 different downloads. Does it need to be in the root of the internal memory? Or renamed? It keeps saying it's failing validation...twrp 3.0.2.0.
dmolavi said:
I tried 4 different downloads. Does it need to be in the root of the internal memory? Or renamed? It keeps saying it's failing validation...twrp 3.0.2.0.
Click to expand...
Click to collapse
i just downloaded it through the internet app on my phone which placed it in the downloads folder and flashed twrp, same version you are running, wiped everything, and selected the zip, and it installed. I dunno whats going on with your phone though :/
chippinganimal said:
i just downloaded it through the internet app on my phone which placed it in the downloads folder and flashed twrp, same version you are running, wiped everything, and selected the zip, and it installed. I dunno whats going on with your phone though :/
Click to expand...
Click to collapse
I didn't do a wipe...but that shouldn't impact the validation.
Will not load into Odin after flashing...
Downloaded, flashed, and tried to Odin the bootloader and modem, but phone will not be recognized by Odin. Sugesstions?
what slot do i put the modem/bootloader in? BL or CP? and do i need to get rid of the .md5 extension first?
Edit - put it in BL, odin said pass. Now i'm sitting at the "Sprint" (white background) splash screen. I'll let it simmer for a while. Fingers crossed again
Edit 2 - Hot sh!t...I'm up and running. 10 minutes on the Sprint splash screen. Now to redownload my apps and restore all the data. Ten thumbs up
Just got an update on my watch and, as always, pulled the update.zip for you guys!
If you're having troubles installing this ZIP please refer to this post here: http://forum.xda-developers.com/showpost.php?p=67403296&postcount=19
----------
Quick Install "Guide" if it's still failing for you:
1) Install TWRP from THIS THREAD HERE
2) Reboot into fastboot mode by turning the watch off and on again and while the black screen shows up constantly swipe from the left upper corner to the lower right corner.
3) Flash the TWRP provided above and reboot into recovery, then push the unpacked TWRP backup into "/sdcard/TWRP/BACKUPS/xxxxxxxxxxx/" (to get the last folder simply make a backup of only your boot partition first, it's the fastest)
4) Restore the backup provided IN THIS POST HERE onto your watch via the in 1 flashed TWRP
1) MUCH EASIER: Flash these instead the TWRP way, far far easier!
2) Let the OTA update install automatically
----------
ZIP MD5: 6844d45bf6d4a1e1d6b15e908579d354
>> DROPBOX <<
>> GOOGLE DRIVE <<
>> OneDrive <<
EpicLPer said:
Just got an update on my watch and, as always, pulled the update.zip for you guys!
ZIP MD5: 6844d45bf6d4a1e1d6b15e908579d354
>> DROPBOX <<
>> GOOGLE DRIVE <<
Click to expand...
Click to collapse
I've got TWRP 3.0.?? on the watch and it refuses to flash, error is
Code:
Unable to statfs '/system/.'.
I've flashed the stock recovery in LG G Watch tools. It went fine, so I've proceeded to install the update the standard way. It seemed to be fine, but than it stopped, with the "Dead Android" image. After using the reset button the built in recovery is dead, but the watch boots. Any ideas?
EDIT: TWRP won't mount /system for some reason, you tap the checkbox and nothing happens. Not even as RO.
kokesh said:
I've got TWRP 3.0.?? on the watch and it refuses to flash, error is
I've flashed the stock recovery in LG G Watch tools. It went fine, so I've proceeded to install the update the standard way. It seemed to be fine, but than it stopped, with the "Dead Android" image. After using the reset button the built in recovery is dead, but the watch boots. Any ideas?
EDIT: TWRP won't mount /system for some reason, you tap the checkbox and nothing happens. Not even as RO.
Click to expand...
Click to collapse
You have to use the edited one on my '' how to root guide'' as the official TWRP those not support squashfs
Xmaster24 said:
You have to use the edited one on my '' how to root guide'' as the official TWRP those not support squashfs
Click to expand...
Click to collapse
Thank you. Your recovery mounts /system, but I am still getting the same error.
kokesh said:
Thank you. Your recovery mounts /system, but I am still getting the same error.
Click to expand...
Click to collapse
yeah it can't write to it, you have to use the stock recovery for that. You are able to write to it but you must first format the partition as writable and then flash your system image/ backup. I'm getting the usual "old keys" error of TWRP not error you mentioned, just means The TWRP is too old base
---------- Post added at 11:13 AM ---------- Previous post was at 11:02 AM ----------
Those anyone have a link to the 6.0.1 stock recovery?
Those anyone have a link to the 6.0.1 stock recovery?
Click to expand...
Click to collapse
Isn't it possible to get it from the 6.0.1 OTA?
kokesh said:
Isn't it possible to get it from the 6.0.1 OTA?
Click to expand...
Click to collapse
No, its stored in a propietary .dat file so good luck with that. Hopefully someone wasn't as foolish as me and deleted their recovery backup
Xmaster24 said:
No, its stored in a propietary .dat file so good luck with that. Hopefully someone wasn't as foolish as me and deleted their recovery backup
Click to expand...
Click to collapse
We could try flashing an older version of Android Wear (the one provided with the one Toolbox someone made here) and let it update to the latest version again.
EpicLPer said:
We could try flashing an older version of Android Wear (the one provided with the one Toolbox someone made here) and let it update to the latest version again.
Click to expand...
Click to collapse
Nope I found it thank god. I had kept a backup of the awful stock kernel just in case when I was initially testing invisiblek's kernel. Luckily its still there in all its awful glory and I will share it here as when you boot up with the stock kernel the system auto flashes the stock recovery because thats how stock is for everything
Xmaster24 said:
Nope I found it thank god. I had kept a backup of the awful stock kernel just in case when I was initially testing invisiblek's kernel. Luckily its still there in all its awful glory and I will share it here as when you boot up with the stock kernel the system auto flashes the stock recovery because thats how stock is for everything
Click to expand...
Click to collapse
Btw. I tried going back to stock yesterday (without locking the bootloader tho) but I may have used a wrong or too old stock recovery version.
Also the only reason why the OTA is reporting an issue while flashing the package with the squashfs enabled TWRP is because the script gets a string back that's not identical with the one it expects. Maybe someone could "hack out" that check and make it TWRP flashable.
EpicLPer said:
Btw. I tried going back to stock yesterday (without locking the bootloader tho) but I may have used a wrong or too old stock recovery version.
Also the only reason why the OTA is reporting an issue while flashing the package with the squashfs enabled TWRP is because the script gets a string back that's not identical with the one it expects. Maybe someone could "hack out" that check and make it TWRP flashable.
Click to expand...
Click to collapse
No the problem is the TWRP was built on an old base of the LG G watch specifically the last 5.1.1 update so the zip thinks the whole system is still on 5.1.1 as TWRP is still on that. I don't think the 6.0.1 source has been released yet so I don't think a recovery could be built with a 6.0.1 base of the lg g watch.
Xmaster24 said:
No the problem is the TWRP was built on an old base of the LG G watch specifically the last 5.1.1 update so the zip thinks the whole system is still on 5.1.1 as TWRP is still on that.
Click to expand...
Click to collapse
That's exactly what I mean with the check and the "wrong" string it gets back I have no clue on how to disable this check inside the ZIP-script tho.
EpicLPer said:
That's exactly what I mean with the check and the "wrong" string it gets back I have no clue on how to disable this check inside the ZIP-script tho.
Click to expand...
Click to collapse
it's not worth it, just flash the stock boot.img once I upload it, waiting for the ART cache to build now
---------- Post added at 12:10 PM ---------- Previous post was at 12:05 PM ----------
xmaster24 said:
it's not worth it, just flash the stock boot.img once i upload it, waiting for the art cache to build now
Click to expand...
Click to collapse
omfg the new kernel actually has a hotplug!!!!!!!!!!!!!!!!!! Finally more than 1 core on stock!!!!!!!!!!!!!
Xmaster24 said:
it's not worth it, just flash the stock boot.img once I upload it, waiting for the ART cache to build now
---------- Post added at 12:10 PM ---------- Previous post was at 12:05 PM ----------
omfg the new kernel actually has a hotplug!!!!!!!!!!!!!!!!!! Finally more than 1 core on stock!!!!!!!!!!!!!
Click to expand...
Click to collapse
You mean the new OTA kernel or the 6.X kernels?
EpicLPer said:
You mean the new OTA kernel or the 6.X kernels?
Click to expand...
Click to collapse
the stock kernel and nvm it was just AIDA64 glitching out, actually thought more than one core was in use The upside it thought the reboot button is back! don't know why they ever removed it but collio
Xmaster24 said:
nvm it was just AIDA64 glitching out, actually thought more than one core was in use ;-(
Click to expand...
Click to collapse
I actually think there are more than 1 cores activate at a time now, the watch has gotten pretty fast with the latest updates and so on, I don't even feel the need for a custom kernel anymore since that.
EpicLPer said:
I actually think there are more than 1 cores activate at a time now, the watch has gotten pretty fast with the latest updates and so on, I don't even feel the need for a custom kernel anymore since that.
Click to expand...
Click to collapse
Nope after about 1 minute after boot the phone locks to 787mhz with userspace governor and I can confirm there is no CPU hotplug aswell. I don't know how you survive with the abysmal lag but ok cool. During the first minute of boot for whatever reason it uses 2 cores and ondemand, would rather have that always lol.
EpicLPer said:
We could try flashing an older version of Android Wear (the one provided with the one Toolbox someone made here) and let it update to the latest version again.
Click to expand...
Click to collapse
Tried, didn't work. My guess is that it didn't handle squash FS. I was left with dead Android guy on the screen
For everyone to enjoy HERE is the stock kernel, @EpicLPer add this to the op to save everyone some trouble. NOTE: you have to boot to system once before the stock recovery is restored. Also it is a twrp backup so you have to adb push it to /sdcard/TWRP/BACKUPS/ to use it. If someone could just get the boot.img raw that would be great, I was too lazy to do it lel.
Xmaster24 said:
Nope after about 1 minute after boot the phone locks to 787mhz with userspace governor and I can confirm there is no CPU hotplug aswell. I don't know how you survive with the abysmal lag but ok cool. During the first minute of boot for whatever reason it uses 2 cores and ondemand, would rather have that always lol.
Click to expand...
Click to collapse
Actually... mine's running pretty well, no lag, no freezing animations, apps take 1 second to open and scrolling is smooth too.
Either I have some leftovers of an old kernel (which I don't think, or, hope) or I'm having a magic LG Watch
OTA zip (Qualcomm) retail 3.3.2018 "Blur_Version.26.11.27.owens.retail.en.US"
Hello everyone. I saw that there was an update pending on my Moto E4 Plus today so I DLed it and put it into OneDrive. I don't have much time available to do much with it for now but in case anyone else can do something with it, you can DL it HERE.
Chad The Pathfinder said:
Hello everyone. I saw that there was an update pending on my Moto E4 Plus today so I DLed it and put it into OneDrive. I don't have much time available to do much with it for now but in case anyone else can do something with it, you can DL it HERE.
Click to expand...
Click to collapse
Thanks, @Chad The Pathfinder. Good to see you here.
I'm on boost mobile e4 plus stock but rooted. Is this zip for twrp flashing to bring rooted stock versions up to date?
shezzy83 said:
I'm on boost mobile e4 plus stock but rooted. Is this zip for twrp flashing to bring rooted stock versions up to date?
Click to expand...
Click to collapse
It is for the retail XT1775 only. It's an official OTA update.
---------- Post added at 06:21 PM ---------- Previous post was at 05:40 PM ----------
Chad The Pathfinder said:
Hello everyone. I saw that there was an update pending on my Moto E4 Plus today so I DLed it and put it into OneDrive. I don't have much time available to do much with it for now but in case anyone else can do something with it, you can DL it HERE.
Click to expand...
Click to collapse
I can probably make this work to flash with TWRP, but you'll need to have your system, oem and boot.img original stock before flashing. If anyone is willing to test it for me, I will modify the ota zip when I have a chance. I have the Boost XT1766 so I can't test it myself. Let me know if anyone is willing to test it because if not, I won't waste my time modifying the ota.
Sent from my Moto E (4) Plus using XDA Labs
I'm willing to try it. I'm a little confused about the requirements you mentioned though. I'm on stock but with a few modifications I've made here and there. Would I need to uninstall Magisk?
Chad The Pathfinder said:
I'm willing to try it. I'm a little confused about the requirements you mentioned though. I'm on stock but with a few modifications I've made here and there. Would I need to uninstall Magisk?
Click to expand...
Click to collapse
If you look inside the ota zip, there are patches for the boot.img, system.img, oem.img, modem.img, etc. If you don't have the original stock versions of these it may fail to install properly and will likely cause problems. Hence the reason for the asserts in the OTA zip to check for the proper unmodified versions of these. If I had the XT1775 I would just flash stock firmware and update officially then pull the imgs, make an updated stock ROM with the system and boot, and make an make a twrp flashable ota zip with the other modem, fsg and oem.imgs. So, you basically have to do the same as if you were going to update officially minus reflashing stock recovery. You almost might as well just flash your latest stock firmware and take the ota update, then pull the modem, fsg and oem and make a system and boot backup with twrp which I can make an updated ROM and twrp flashable ota for others to update without that hassle. Your choice. I asked another user to provide me with a backup after they updated, but they had to go somewhere for a few days and said they would when they returned. I could give you a stock ROM flashable so you don't have to flash firmware with fastboot. I already have one made, I just haven't uploaded and posted it yet.
Sent from my Moto E (4) Plus using XDA Labs
Goose03 said:
If you look inside the ota zip, there are patches for the boot.img, system.img, oem.img, modem.img, etc. If you don't have the original stock versions of these it may fail to install properly and will likely cause problems. Hence the reason for the asserts in the OTA zip to check for the proper unmodified versions of these. If I had the XT1775 I would just flash stock firmware and update officially then pull the imgs, make an updated stock ROM with the system and boot, and make an make a twrp flashable ota zip with the other modem, fsg and oem.imgs. So, you basically have to do the same as if you were going to update officially minus reflashing stock recovery. You almost might as well just flash your latest stock firmware and take the ota update, then pull the modem, fsg and oem and make a system and boot backup with twrp which I can make an updated ROM and twrp flashable ota for others to update without that hassle. Your choice. I asked another user to provide me with a backup after they updated, but they had to go somewhere for a few days and said they would when they returned. I could give you a stock ROM flashable so you don't have to flash firmware with fastboot. I already have one made, I just haven't uploaded and posted it yet.
Sent from my Moto E (4) Plus using XDA Labs
Click to expand...
Click to collapse
Sure. If you want to send me the flashable you have I'll do that tonight and see what happens.
Chad The Pathfinder said:
Sure. If you want to send me the flashable you have I'll do that tonight and see what happens.
Click to expand...
Click to collapse
I'll have to modify the ota zip for you first so you can flash it after the stock ROM. As soon as I have a chance to, I'll upload that and the stock ROM zip for you. You didn't modify your oem partition at all did you? If so, I'll give you a flashable oem zip to restore that back the way it was also. Just make sure you have stock firmware ready to flash with fastboot in case something doesn't go right. Most of the ota is modem related, no bootloader patches, so it should work fine and hard bricking shouldn't be a concern.
Sent from my Moto E (4) Plus using XDA Labs
Goose03 said:
I'll have to modify the ota zip for you first so you can flash it after the stock ROM. As soon as I have a chance to, I'll upload that and the stock ROM zip for you. You didn't modify your oem partition at all did you? If so, I'll give you a flashable oem zip to restore that back the way it was also. Just make sure you have stock firmware ready to flash with fastboot in case something doesn't go right. Most of the ota is modem related, no bootloader patches, so it should work fine and hard bricking shouldn't be a concern.
Sent from my Moto E (4) Plus using XDA Labs
Click to expand...
Click to collapse
I did not modify the oem partition. I've just made small changes like changed the boot animation, splash screen and some other things like that. Nothing major. have attempted to make a deodex version with a couple of different kitchens to make some other changes but haven't had enough time to really get into anything.
Chad The Pathfinder said:
I did not modify the oem partition. I've just made small changes like changed the boot animation, splash screen and some other things like that. Nothing major. have attempted to make a deodex version with a couple of different kitchens to make some other changes but haven't had enough time to really get into anything.
Click to expand...
Click to collapse
I'm uploading the ROM now. I just got done modifying the ota zip and I'll give you links as soon as they're done uploading. I made a deodexed Sprint variant version. Was planning on deodexing the retail version also. I may as well wait for the newer version though. The trick is, you need to deodexed the oem apps and framework also or it won't boot.
Sent from my Moto E (4) Plus using XDA Labs
Thanks. I'm in town right now. I'll check when I get home and flash if its ready. If all goes well, you want me to send you a twrp backup of boot and system only right?
Chad The Pathfinder said:
Thanks. I'm in town right now. I'll check when I get home and flash if its ready. If all goes well, you want me to send you a twrp backup of boot and system only right?
Click to expand...
Click to collapse
Yes. It'll be a little while, uploads are going really slow and keep failing on AFH. I had it almost uploaded twice and it keeps failing.
Sent from my Moto E (4) Plus using XDA Labs
I couldn't even log into AFH earlier. That's why I used OneDrive in the op.
Chad The Pathfinder said:
I couldn't even log into AFH earlier. That's why I used OneDrive in the op.
Click to expand...
Click to collapse
I have been having issues uploading to AFH too. Man, I wish they would finally get this fixed.
Chad The Pathfinder said:
I couldn't even log into AFH earlier. That's why I used OneDrive in the op.
Click to expand...
Click to collapse
Finally got it
ROM: https://www.androidfilehost.com/?fid=746010030569959248
OTA:
So, here's what I want you to do.
1. Make a backup before you do anything.
2. Flash a Magisk uninstaller.
3. Flash the ROM. (if it should fail to flash, please get a recovery log so I can see exactly what failed.)
4. Flash the OTA zip. (again, if it should fail to flash, please get a recovery log so I can see exactly what failed.)
5. If everything flashes ok, reboot recovery to make sure you don't lose twrp.
6. Make a system backup.
7. Use fastboot to pull the boot.img, modem.img, fsg.mbn, and the oem.img.
Edit: actually, if you could pull everything you see in a stock firmware package and pull them so they have the same name and file extension, that would be great.
I'll be working until about 8 tonight. (3.5.18) I'll work on it tonight and let you know what happens.
Edit: I managed to get the "Blur_Version.26.11.27.owens.retail.en.US--XT1775_TWRP_flashable" down loaded but the other was taking too long and failed a couple of times. I will try again when I can.
so glad you guys are working on this My daughter and her moms xt1775 just popped the update message and im not "allowed" to work on them too often so i cant experiment with you. So a twrp flashable update would be great if i dont have to unroot reroot stock.img etc etc it will be a painless (for me) update.
A Sort-of Related Question
I installed the update by using RSD Lite to go back to stock, taking the update as an OTA, then reflashing TWRP and Magisk. All was fine, until I tried to restore a back up. Which failed, unable to mount System. Thereafter, all reboots take me to Bootloader. I can't use RSD Lite again, as I have updated to a later version. (Believe me, I have tried multiple times!) I tried flashing the two zips, but I fail at the OTA. I was able to load Lineage, which works, but still reboots to Bootloader, then to the ROm.
I have tried fastboot oem fb_mode_clear via both ADB and TWRP Terminal but that fails as well.
Any thoughts on clearing this?
NEVER MIND - Tried a different PC and the mode clear command worked! Whew! The good news is that is something that might be worth trying if you get stuck.
koop1955 said:
I installed the update by using RSD Lite to go back to stock, taking the update as an OTA, then reflashing TWRP and Magisk. All was fine, until I tried to restore a back up. Which failed, unable to mount System. Thereafter, all reboots take me to Bootloader. I can't use RSD Lite again, as I have updated to a later version. (Believe me, I have tried multiple times!) I tried flashing the two zips, but I fail at the OTA. I was able to load Lineage, which works, but still reboots to Bootloader, then to the ROm.
I have tried fastboot oem fb_mode_clear via both ADB and TWRP Terminal but that fails as well.
Any thoughts on clearing this?
NEVER MIND - Tried a different PC and the mode clear command worked! Whew! The good news is that is something that might be worth trying if you get stuck.
Click to expand...
Click to collapse
The modified ota zip I posted failed to flash? Did you happen to get a recovery log?
Sent from my Moto E (4) Plus using XDA Labs
Goose03 said:
The modified ota zip I posted failed to flash? Did you happen to get a recovery log?
Sent from my Moto E (4) Plus using XDA Labs
Click to expand...
Click to collapse
Of course, sent to you via PM.
I don't think that it is a quality of your zip, I think it is related to my earlier attempt at installing the OTA itself.