Don't know if this is big news, but I got this about 2 hours ago.
https://photos.app.goo.gl/jmTOr4CqFuB4zlam2
gleonard3 said:
Don't know if this is big news, but I got this about 2 hours ago.
Click to expand...
Click to collapse
same
Android one or regular?
Android One. Project Fi.
Got it too.
same here
Can this OTA be located on the phone for safe keeping?
Was anybody able to grab the download-URL to fetch an OTA.zip for fastboot-flashing? Thanks
sleeptab said:
Was anybody able to grab the download-URL to fetch an OTA.zip for fastboot-flashing? Thanks
Click to expand...
Click to collapse
You can use this tool instead.
https://motoota.lolinet.com/
rafikowy said:
You can use this tool instead.
https://motoota.lolinet.com/
Click to expand...
Click to collapse
I was skeptical at the link till found the thread for it. I will try it after I get off work tonight if no one else has.
Neffy27 said:
I was skeptical at the link till found the thread for it. I will try it after I get off work tonight if no one else has.
Click to expand...
Click to collapse
This part works, I was able to get the OTA. Thanks
However, in Recovery ADB Sideload did not work (not able to mount) and Install update from SD Card option only shows some cryptic codes, nothing special. As my device isn't rooted and I only have little basic knowledge from HTC-phones, I think I'm done with it for the moment.
sleeptab said:
This part works, I was able to get the OTA. Thanks
However, in Recovery ADB Sideload did not work (not able to mount) and Install update from SD Card option only shows some cryptic codes, nothing special. As my device isn't rooted and I only have little basic knowledge from HTC-phones, I think I'm done with it for the moment.
Click to expand...
Click to collapse
Would you mind sharing the parameters for the tool to get the OTA?
I have flashed PAYTON_FI_OPW27.57-25-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC on a "-7" device, but I'm still on the reteu update channel and don't receive the January update.
As for adb (sideload), it isn't yet supported in the TWRP for this device. But the zip file you downloaded is most likely not meant to be flashed using TWRP.
sleeptab said:
This part works, I was able to get the OTA. Thanks
However, in Recovery ADB Sideload did not work (not able to mount) and Install update from SD Card option only shows some cryptic codes, nothing special. As my device isn't rooted and I only have little basic knowledge from HTC-phones, I think I'm done with it for the moment.
Click to expand...
Click to collapse
Yes, please share the link or the OTA zip!
Neffy27 said:
Yes, please share the link or the OTA zip!
Click to expand...
Click to collapse
Model: moto x4
Software-version: Blur_Version.27.21.2.payton_fi.google_fi.en.US
Carrier: retus
And here you are https://motoota.lolinet.com/index.p...2.payton_fi.google_fi.en.US&carrier=retus&sn=
steveeJ said:
Would you mind sharing the parameters for the tool to get the OTA?
I have flashed PAYTON_FI_OPW27.57-25-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC on a "-7" device, but I'm still on the reteu update channel and don't receive the January update.
As for adb (sideload), it isn't yet supported in the TWRP for this device. But the zip file you downloaded is most likely not meant to be flashed using TWRP.
Click to expand...
Click to collapse
That's quite right because Motorola doesn't roll out Project-Fi-Updates on reteu and it's not possible to change update-channel on your device. That's why I entered "retus" as Carrier into the OTA link generator.
If I had TWRP I would be happy, at the moment bootloader is still locked and I don't have time to restore all data after wiping. So I tried on original Recovery. And install zip is not possible as long as device is encrypted. That's why I said I'm out for now.
Unable to flash with the stock recovery too...
Can't see the files with Update via SD Card, and error with adb sideload.
Getting the February security update right now. A1.
Same problem here :
I'm on a European XT1900-7 reteu software channel, as well and I previously flashed the Android One Project-Fi firmware.
Now I'm trying to manually flash the OPWS27.1.1 OTA update zip file
You will be able to see and select the ota file only when placing it on an external SD card.
Although, the problem remains the same as with adb sideload
Error messages are :
Code:
-- Install /sdcard/ota.zip ...
E:failed to unmount /
E:failed to set up expected mounts for install; aborting
Installation aborted
ulysse34 said:
Same problem here :
I'm on a European XT1900-7 reteu software channel, as well and I previously flashed the Android One Project-Fi firmware.
Now I'm trying to manually flash the OPWS27.1.1 OTA update zip file
You will be able to see and select the ota file only when placing it on an external SD card.
Although, the problem remains the same as with adb sideload
Error messages are :
Code:
-- Install /sdcard/ota.zip ...
E:failed to unmount /
E:failed to set up expected mounts for install; aborting
Installation aborted
Click to expand...
Click to collapse
You can see it so you're device is encrypted?
But good to know it's the same message.
Does anybody know if it's possible to flash OTA with TWRP?
The device is encrypted by default, I guess. Correct?
I'm on stock recovery.
Any ideas on how to fix things and flash the ota?
According to posts in other Motorola subforums, it should be possible to switch software channel. Did anybody try on the x4 yet?
Related
Hi guys, as I cant stand the ads I'm thinking of rooting the device but I wonder if I can have OTA updates after this and if yes, do I have to re-root the phone after the updates?
thxxx
epivitor said:
Hi guys, as I cant stand the ads I'm thinking of rooting the device but I wonder if I can have OTA updates after this and if yes, do I have to re-root the phone after the updates?
thxxx
Click to expand...
Click to collapse
If you have non gpe device then yes root will deny ota.
No my device isnt the gpe.
How can I update my phone then ?
epivitor said:
No my device isnt the gpe.
How can I update my phone then ?
Click to expand...
Click to collapse
flash stock rom
update via OTA
again root..
solved...
reversegear said:
flash stock rom
update via OTA
again root..
solved...
Click to expand...
Click to collapse
There is no other easier way to do this?
I had in mind something like download the update to the pc and apply it to the phone with usb connection. Isnt that possible. Could this method I thought brick the phone?
epivitor said:
There is no other easier way to do this?
I had in mind something like download the update to the pc and apply it to the phone with usb connection. Isnt that possible. Could this method I thought brick the phone?
Click to expand...
Click to collapse
afaik OTAs cannot be installed via PC
name itself says Over The Air
reversegear said:
afaik OTAs cannot be installed via PC
name itself says Over The Air
Click to expand...
Click to collapse
I wanted to say if I get the OTA update from another source not over the air of course, could I flash it without porblem through usb cable?
epivitor said:
I wanted to say if I get the OTA update from another source not over the air of course, could I flash it without porblem through usb cable?
Click to expand...
Click to collapse
no you cannot flash OTAs via PC
S0bes said:
If you have non gpe device then yes root will deny ota.
Click to expand...
Click to collapse
Really? My XT1032 is rooted since i bought it and I was still able to apply the February OTA. Didn't wait for it to reach my phone though - I've downloaded it here on XDA, then checked for updates.
epivitor said:
There is no other easier way to do this?
I had in mind something like download the update to the pc and apply it to the phone with usb connection. Isnt that possible. Could this method I thought brick the phone?
Click to expand...
Click to collapse
you can install CWM.
Then make a full backup. You can move it on your pc or let it take space on your phone.
After that you can apply any patches via CWM or install root or whatsoever
When your phone will show the next update you should:
1) Boot into CWM and recover your backup. BUT! You should recover only part of it. The system part.
backup and restore -> advanced restore from /sdcard -> choose your backup -> restore system
2) wait till it complete.
Now you can delete your backup.
Reboot your phone (reboot system now)
After that you will see 2 messages and if you wanna be able to apply ota you have to make the right choises
Q: ROM may flash stock recovery on boot. Fix?
A: NO
Q: Root access is missing. Root device?
A:NO
After all that steps you'll get:
1) clear system part (which means no root, modified files etc)
2) default recovery
I've read "mixed" opinions about this; some say rooted devices lose updates and some say otherwise. I've also heard that if you flash ROM A on top of ROM B that's your original ROM, and you get signature errors you no more receive OTA updates. By the way, I was able to receive OTA updates on my Asia Retail XT1033 that was flashed to Retail UK XT1032. It would be cool if some senior member here shed some light on this subject.
knizmi said:
Really? My XT1032 is rooted since i bought it and I was still able to apply the February OTA. Didn't wait for it to reach my phone though - I've downloaded it here on XDA, then checked for updates.
Click to expand...
Click to collapse
yes, it can be so. I heard about the same situation from few people. But other still can not apply ota with root
S0bes said:
yes, it can be so. I heard about the same situation from few people. But other still can not apply ota with root
Click to expand...
Click to collapse
I think that people who have reported that they can't apply the OTA update had messed their /system partition in other ways than just rooting.
I've studied the update package and all it does is that it first checks if the files (and only those files) that are going to be updated are untampered with and if everything is allright, they are patched.
To sum it up - you can have extra files on your /system folder (like the su binary), but all of the updated files must be stock. The updater really doesn't care if su, xposed or other mods are present.
knizmi said:
I think that people who have reported that they can't apply the OTA update had messed their /system partition in other ways than just rooting.
I've studied the update package and all it does is that it first checks if the files (and only those files) that are going to be updated are untampered with and if everything is allright, they are patched.
To sum it up - you can have extra files on your /system folder (like the su binary), but all of the updated files must be stock. The updater really doesn't care if su, xposed or other mods are present.
Click to expand...
Click to collapse
Is there a problem if some of the apps are disabled ? (not with titanium backup but through settings->apps->select the app ->disable)
epivitor said:
Is there a problem if some of the apps are disabled ? (not with titanium backup but through settings->apps->select the app ->disable)
Click to expand...
Click to collapse
No, disabled apps are still where they are supposed to be. The OTA updater checks if the file is there (it is), if the fingerprint matches (it does) and then it patches the app even when it's disabled.
Hi folks, so, I received OTA update for my Moto G (XT1032).
Phone was rooted (I did unroot from SuperSU). Also, I've re-installed Stock recovery (to make sure) and wiped cache/dalvik.
But, update still fails.
I don't have much root-related soft (like Xposed etc) installed - so pretty sure this should not cause an issue.
But still, update fails.
Any ideas how to troubleshoot/make it work? Maybe installing OTA somehow from recovery (custom one, TWRP)?
Any comments - much appreciated. I guess I'm not alone in this, but still...
Thanks
Same problem here
Ulverinho said:
Hi folks, so, I received OTA update for my Moto G (XT1032).
Phone was rooted (I did unroot from SuperSU). Also, I've re-installed Stock recovery (to make sure) and wiped cache/dalvik.
But, update still fails.
I don't have much root-related soft (like Xposed etc) installed - so pretty sure this should not cause an issue.
But still, update fails.
Any ideas how to troubleshoot/make it work? Maybe installing OTA somehow from recovery (custom one, TWRP)?
Any comments - much appreciated. I guess I'm not alone in this, but still...
Thanks
Click to expand...
Click to collapse
Have to install stock ROM again then update it via ota. Could also try flashing an ota update file via the official recovery of your phone.
A_Bunny said:
Have to install stock ROM again then update it via ota. Could also try flashing an ota update file via the official recovery of your phone.
Click to expand...
Click to collapse
Yep, my guess was the same. As per official recovery - I'll try adb sideload, but first time it couldn't find phone (all drivers installed and up-to-date).
http://forum.xda-developers.com/moto-g/help/driver-fastboot-falcon-s-t2820848
This error pops up - I can't find solution also...
Ulverinho said:
Yep, my guess was the same. As per official recovery - I'll try adb sideload, but first time it couldn't find phone (all drivers installed and up-to-date).
http://forum.xda-developers.com/moto-g/help/driver-fastboot-falcon-s-t2820848
This error pops up - I can't find solution also...
Click to expand...
Click to collapse
Install the recovery with fastboot not adb.
A_Bunny said:
Install the recovery with fastboot not adb.
Click to expand...
Click to collapse
Well, I might misunderstood, but:
I have official recovery (fastboot is mode of it, I guess, when U press Power+volume key?)
I've read about adb sideload zip_name_of_OTA.zip
I don't know any other way to install OTA apart from let phone handle it OR adb sideload.
Ulverinho said:
Well, I might misunderstood, but:
I have official recovery (fastboot is mode of it, I guess, when U press Power+volume key?)
I've read about adb sideload zip_name_of_OTA.zip
I don't know any other way to install OTA apart from let phone handle it OR adb sideload.
Click to expand...
Click to collapse
Just load it onto your phone before you flash it. Your ROM does work.
A_Bunny said:
Just load it onto your phone before you flash it. Your ROM does work.
Click to expand...
Click to collapse
Load ZIP of OTA on SD Card and install it from Recovery? Will it work?
Ulverinho said:
Load ZIP of OTA on SD Card and install it from Recovery? Will it work?
Click to expand...
Click to collapse
It may work if it is the stock recovery.
A_Bunny said:
It may work if it is the stock recovery.
Click to expand...
Click to collapse
Got this, screenshot in attachment.
Fingerprints are wrong. In build.prop - I can see it's fine, fingerprint of current 4.4.4. - matches expected.
But as soon as update starts - it says that 4.4.2 is fingerprint of my OS. Bollocks.
Edited OTA zip, edited some metadata file...
Why it won't install on pretty clean phone - I can't understand...Previous installs of OTA went fine with root etc.
Ulverinho said:
Got this, screenshot in attachment.
Fingerprints are wrong. In build.prop - I can see it's fine, fingerprint of current 4.4.4. - matches expected.
But as soon as update starts - it says that 4.4.2 is fingerprint of my OS. Bollocks.
Edited OTA zip, edited some metadata file...
Why it won't install on pretty clean phone - I can't understand...Previous installs of OTA went fine with root etc.
Click to expand...
Click to collapse
Well the only thing I would recommend would be to install the stock system though fastboot manualy.
Ulverinho said:
Hi folks, so, I received OTA update for my Moto G (XT1032).
Phone was rooted (I did unroot from SuperSU). Also, I've re-installed Stock recovery (to make sure) and wiped cache/dalvik.
But, update still fails.
I don't have much root-related soft (like Xposed etc) installed - so pretty sure this should not cause an issue.
But still, update fails.
Any ideas how to troubleshoot/make it work? Maybe installing OTA somehow from recovery (custom one, TWRP)?
Any comments - much appreciated. I guess I'm not alone in this, but still...
Thanks
Click to expand...
Click to collapse
i feel ya same thing here, than i tryed installing a stock lollipop from here via twrp witch ended up messing my phone with failing the procedure wondered around couldnt revert to stock since im a noob and didnt even backed up the rom,but at the and of the day thank god for the cm12.1 finally menaged to make my phone running again at least
Greetings, I have the same problem, it is the last screen that appears when you install the update, and then restarts it goes off the screen update error ...
To anyone having issues:
1. Make sure you're on completely stock 4.4.4 (Refer to http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688 and use only untouched 4.4.4 version for your phone if you have to reflash before continuing)
2. Make sure you're on stock recovery (Refer to http://forum.xda-developers.com/showthread.php?t=2649763)
*Uninstall XPOSED if using it
3. I personally let update run on its own after reverting everything to stock.
fusionice said:
To anyone having issues:
1. Make sure you're on completely stock 4.4.4 (Refer to http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688 and use only untouched 4.4.4 version for your phone if you have to reflash before continuing)
2. Make sure you're on stock recovery (Refer to http://forum.xda-developers.com/showthread.php?t=2649763)
*Uninstall XPOSED if using it
3. I personally let update run on its own after reverting everything to stock.
Click to expand...
Click to collapse
Yeah, that's the better way.
But I guess, I can install Stock 5.* straight away after wiping? Why bother about OTA, if there is ROM available?
fusionice said:
To anyone having issues:
1. Make sure you're on completely stock 4.4.4 (Refer to http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688 and use only untouched 4.4.4 version for your phone if you have to reflash before continuing)
2. Make sure you're on stock recovery (Refer to http://forum.xda-developers.com/showthread.php?t=2649763)
*Uninstall XPOSED if using it
3. I personally let update run on its own after reverting everything to stock.
Click to expand...
Click to collapse
Yep.
The solution is backup data, restore stock last firmware using fastboot guide posted in this forum and not even update apps (cancel gmail registration and everything it asks when it first starts) ONLY update motorola update services so you can get the ota again an install it. If you have the ota downloaded you can flash it through recovery but using the last recovery version (.61) and of course last firmware version. If you guys flash it all through fastboot, it should install w/o any problems.
Hi Everyone
Can anyone please stop my suffering? I tried everything and I am lost...
My phone kept asking me to update to KAS254 which I finally managed to do by flashing stock recovery...but now it is giving me another OTA, some weird alphanumeric combination, around 60MB.
Thing is I cannot update it and the update keeps popping up and I am going crazy already.
TWRP returns this log:
Code:
...
....
Source: oneplus/bacon/A0001: 6.0.1/MHC19Q/ZNH2KAS254 : user/release-keys
Target: oneplus/bacon/A0001: 6.0.1/MHC19Q/ZNH2KAS2X1 : user/release-keys
Verifying current system...
Package expects build fingerprint of oneplus/bacon/A0001/6.0.1/MHC19Q/ZNHKAS254 : user/release-keys or oneplus/bacon/A0001: 6.0.1/MHC19Q/ZNH2KAS2X1 : user/release-keys;
this device has oneplus/bacon/A0001: 5.1.1/LMY48B/YOG4PAS1NO: user/release-keys
Updater process ended with ERROR: 7
Error installing zip file '@/cache/recovery/block.map
...
...
So appearently, I still have some Android L leftovers, but I don't know what that is.
Could anyone please help? I am going nuts!!
Thanks XDA!!!
Sopis said:
Hi Everyone
Can anyone please stop my suffering? I tried everything and I am lost...
My phone kept asking me to update to KAS254 which I finally managed to do by flashing stock recovery...but now it is giving me another OTA, some weird alphanumeric combination, around 60MB.
Thing is I cannot update it and the update keeps popping up and I am going crazy already.
TWRP returns this log:
So appearently, I still have some Android L leftovers, but I don't know what that is.
Could anyone please help? I am going nuts!!
Thanks XDA!!!
Click to expand...
Click to collapse
You can not do OTA with a customer recovery like TWRP. If you want the latest stock firmware you will need to download the latest from https://cyngn.com/support and flash all the files via fastboot then reinstall TWRP and SuperSU for root.
Durso81 said:
You can not do OTA with a customer recovery like TWRP. If you want the latest stock firmware you will need to download the latest from https://cyngn.com/support and flash all the files via fastboot then reinstall TWRP and SuperSU for root.
Click to expand...
Click to collapse
hi, thanks for your reply..I did that but it did not work
Sopis said:
hi, thanks for your reply..I did that but it did not work
Click to expand...
Click to collapse
What do you mean did not work? What happen when you flashed all the stock files via fastboot?
are you saying that I should apply the downloaded file via fastboot?
what I did is downloaded the recovery and updated to KAS54, then another update popped up and again I cannot update...no I get the same error, but this time it says I have KAS254 and the package expects something newer..
Sopis said:
are you saying that I should apply the downloaded file via fastboot?
what I did is downloaded the recovery and updated to KAS54, then another update popped up and again I cannot update...no I get the same error, but this time it says I have KAS254 and the package expects something newer..
Click to expand...
Click to collapse
Are you running stock recovery or twrp? Cause your title says twrp.
hey, I got it finally..thanks for the effort...thread can be deleted
Hey there fellow U11 Users,
I just received the update concerning 60fps HD-Video etc. I use TWRP so the update can't be installed by itself. So I have two questions:
A
Where do I find the update file. I looked around a lot but couldn't locate it.
B
Once found, can I just flash it with TWRP?
Thanks in advance!
Dito13 said:
Hey there fellow U11 Users,
I just received the update concerning 60fps HD-Video etc. I use TWRP so the update can't be installed by itself. So I have two questions:
A
Where do I find the update file. I looked around a lot but couldn't locate it.
B
Once found, can I just flash it with TWRP?
Thanks in advance!
Click to expand...
Click to collapse
See here: https://forum.xda-developers.com/u11/how-to/collection-htcu-u11-ruu-firmware-t3612048/page63
Alright, thanks! :good: That only leaves the first question unanswered.
Dito13 said:
Alright, thanks! :good: That only leaves the first question unanswered.
Click to expand...
Click to collapse
/data/data/com.htc.updater/files
btw...twrp can install the update but you need to flash the firmware.zip inside the ota manually
Thank you kindly!
OMJ said:
/data/data/com.htc.updater/files
btw...twrp can install the update but you need to flash the firmware.zip inside the ota manually
Click to expand...
Click to collapse
Just to be clear: I only flash the firmware.zip manually via TWRP or do I need to flash the whole ota?
Sorry for the question. I mostly handled Nexus devices...
Dito13 said:
Just to be clear: I only flash the firmware.zip manually via TWRP or do I need to flash the whole ota?
Sorry for the question. I mostly handled Nexus devices...
Click to expand...
Click to collapse
twrp will install the ota zip but it wont install the firmware.zip inside, you have to extract & manually install from download mode
grrr.... I tried following your suggestions, but recieved error 7 in TWRP. Can you help me in the right direction?
Dito13 said:
grrr.... I tried following your suggestions, but recieved error 7 in TWRP. Can you help me in the right direction?
Click to expand...
Click to collapse
list your steps your using to install the ota via twrp....personally, I let the system initiate the install (booted into OS) as if I was 100% stock, once twrp loads, it automatically installs except for the firmware.zip
more details here...
OK, I am a Noob to the HTC world. I am used to easy flashing/rooting/etc. on Nexus devices.
TWRP doesn't do anything after accepting the ota. When I try to install the OTA via TWRP I receive Error 7. I worked my way through a lot of guides here on XDA concerning manual OTA installing. One thing I tried was flashing back to stock recovery which I found in the firmware.zip of the OTA in bootloader mode. That failed also ("FAILED (remote: not allowed on PRODUCTION device).
Edit: The device has obviously an unlocked bootloader, s-on, rooted via magisk and is a DGLU device, software number 1.16.400.5
Are you on an Untouched System Image? Completely stock ROM? While it is great we can flash the OTA in TWRP, the system stills needs to be stock, and of course will still have to fastboot firmware.
schmeggy929 said:
Are you on an Untouched System Image? Completely stock ROM? While it is great we can flash the OTA in TWRP, the system stills needs to be stock, and of course will still have to fastboot firmware.
Click to expand...
Click to collapse
Yes, everything is stock.
I managed to flash the stock recovery now. I didn't remember to use the download mode /sorry. Then Then I checked for the ota again, downloaded it and tried to apply but I landed in the stock recovery with the red exclamation mark and then nothing happened.
Dito13 said:
Yes, everything is stock.
I managed to flash the stock recovery now. I didn't remember to use the download mode /sorry. Then Then I checked for the ota again, downloaded it and tried to apply but I landed in the stock recovery with the red exclamation mark and then nothing happened.
Click to expand...
Click to collapse
re-flash twrp and try it again.
schmeggy929 said:
re-flash twrp and try it again.
Click to expand...
Click to collapse
Same result unfortunately. TWRP hands out Error 7 and "system partition has unexpected contents" or something like that although I didn't do any tinkering with the stock rom. I flashed Magisk and did a backup before and that was all.
Dito13 said:
Same result unfortunately. TWRP hands out Error 7 and "system partition has unexpected contents" or something like that although I didn't do any tinkering with the stock rom. I flashed Magisk and did a backup before and that was all.
Click to expand...
Click to collapse
Only thing I would say is start fresh. Backup all the data for your apps first. Flash the RUU, Take the OTA and reinstall all your apps.
schmeggy929 said:
Only thing I would say is start fresh. Backup all the data for your apps first. Flash the RUU, Take the OTA and reinstall all your apps.
Click to expand...
Click to collapse
Thanks again - seems to have worked. It will be interesting to see which problems occur with the Android Oreo update which was announced till the end of the year by HTC
Hope by performance fixes they mean memory leak fix.
I have not seen os ram usage this low after boot in many months.
Did you have round corner?
yaral said:
Did you have round corner?
Click to expand...
Click to collapse
It squared it when I screenshot.
Anybody figure out how to turn off the rounded corners?
Anyone know what the modem sucurity patch is about? Kinda don't want to take it cuz of the sim lock issues awhile back.
enigma2446 said:
Anyone know what the modem sucurity patch is about? Kinda don't want to take it cuz of the sim lock issues awhile back.
Click to expand...
Click to collapse
no clue but i fastboot flashed the images because the OTA refused to work, but flashing the images worked. i'm still able to connect to ATT towers from my sprint sim unlocked PH-1.
TomTheGeek3 said:
no clue but i fastboot flashed the images because the OTA refused to work, but flashing the images worked. i'm still able to connect to ATT towers from my sprint sim unlocked PH-1.
Click to expand...
Click to collapse
Noob question here: When using fastboot to flash the update image, do you have to worry about the "slot A" vs "slot B" thing?? Can you provide a little more insight? I've been reading around the forum, and I'm a little worried about bricking my phone! (The bootloader on my phone is unlocked and I've rooted the phone, but I haven't flashed a third-party ROM. The OTA update feature gives me a "couldn't update" message.)
adiejg said:
Noob question here: When using fastboot to flash the update image, do you have to worry about the "slot A" vs "slot B" thing?? Can you provide a little more insight? I've been reading around the forum, and I'm a little worried about bricking my phone! (The bootloader on my phone is unlocked and I've rooted the phone, but I haven't flashed a third-party ROM. The OTA update feature gives me a "couldn't update" message.)
Click to expand...
Click to collapse
No you don't have to worry about it. The flash all file in the zip will do all the work for you. It wont take update via ota because you have to be on the stock boot.img. the stock boot img has the recovery built into the ramdisk there for if your rooted then there is no stock recovery to use for ota. Be cautious because flashing via fastboot will wipe the phone.
enigma2446 said:
No you don't have to worry about it. The flash all file in the zip will do all the work for you. It wont take update via ota because you have to be on the stock boot.img. the stock boot img has the recovery built into the ramdisk there for if your rooted then there is no stock recovery to use for ota. Be cautious because flashing via fastboot will wipe the phone.
Click to expand...
Click to collapse
If I edit the .bat file and remove "format userdata", that will prevent the wipe?
njsges said:
If I edit the .bat file and remove "format userdata", that will prevent the wipe?
Click to expand...
Click to collapse
It should without issues but always prepare for hickups.
Anyone else having issues when trying to update to the February release? I tried to sideload the OTA update and that kept giving me the error "adb sideload failed to read command: no error" and then I decided to follow Morphius's suggestion here to just unroot my device by flashing to stock bootloader in order to try to take the OTA update and that OTA keeps failing as well. Anyone else having this issue?
hssxda said:
Anyone else having issues when trying to update to the February release? I tried to sideload the OTA update and that kept giving me the error "adb sideload failed to read command: no error" and then I decided to follow Morphius's suggestion here to just unroot my device by flashing to stock bootloader in order to try to take the OTA update and that OTA keeps failing as well. Anyone else having this issue?
Click to expand...
Click to collapse
Are you rooted?
After three days running, memory Leak not fixed.. Bummer
enigma2446 said:
No you don't have to worry about it. The flash all file in the zip will do all the work for you. It wont take update via ota because you have to be on the stock boot.img. the stock boot img has the recovery built into the ramdisk there for if your rooted then there is no stock recovery to use for ota. Be cautious because flashing via fastboot will wipe the phone.
Click to expand...
Click to collapse
Again, a very noob question, (and I do apologize) but can I use something like Titanium Backup to make sure I can restore all my apps the way they were after I flash the update via fastboot? Reinstalling everything seems like a gigantic pain in the backside.
adiejg said:
Again, a very noob question, (and I do apologize) but can I use something like Titanium Backup to make sure I can restore all my apps the way they were after I flash the update via fastboot? Reinstalling everything seems like a gigantic pain in the backside.
Click to expand...
Click to collapse
Titanium Backup used to require root access. You probably need to be rooted before you update via fastboot and run the backup through Titanium Backup. Then you will need to copy your backup files to a computer because fastboot flashing will erase your phone data. Next apply the fastboot update, root again, copy your backup back to the phone and restore your backup.
enigma2446 said:
Are you rooted?
Click to expand...
Click to collapse
I was but I followed all the proper steps but for some reason this morning my computer wouldn't real the OTA zip file. I tried it tonight using a different USB port on my laptop and it is worked first time... so weird...
d14r1 said:
After three days running, memory Leak not fixed.. Bummer
Click to expand...
Click to collapse
I don't have memory leak anymore..
1.5gb ram not in usage.
The last time I restarted my phone was after the update.
I'm using my Essential 'phone in the UK having recently purchased it used. On the 7th I had a notice to say that an update was available. When I tried to install it it downloaded, but refused to install saying: Couldn't update... installation problem. As far as I know the 'phone is running the stock software but I noticed that no updates had been installed since October 2018. I unchecked 'allow bootloader unlocking' in case that was the issue, but still couldn't perform the update.
I went onto the Essential website and downloaded the OTA image to my iMac, then, following the guide, sideloaded the update on to the 'phone. This worked well and I now have an updated PH-1. I'll have to see if March's update now installs correctly or not.
so.... am i reading this right... and here is my thinking...
to keep root and still take the OTAs
- go to Essentials site and download the image zip
- (to keep root) copy boot.img to your device, patch it through magisk, then copy it back to your ota folder.
- open flashall.bat, comment the format userdata (to keep your data), change the boot.img line to patched_boot.img
- run flashall.bat
- profit