Fixed.
RusherDude said:
If I am on 4.4 stock rooted, with a custom recovery, and stuff modified on /system.. what I do when the update to 4.1.1 comes?
If I don't do nothing, the update will download automatically (which I don't want at all...), then try to patch and fail (I guess it won't even start since it detects that it's not stock system and recovery to flash the update) and it may even loop downloading and failing by what I readed being a bug on some 4.3 roms on the Nexus 4?
So how I should act in the following situations? First make a nandroid then..
a) I wanna flash it asap: I get the ota zip asap its posted and flash it on CWM and hope it goes ok. I may **** up stuff and have to revert to the nandroid, or 1it can go ok and just lose root and the system changes, right?
b) I wanna stay on 4.4 until all the stuff is ported to 4.1.1: It will at some point download the ota (****) by itself and spam me continuously to install it, right? If I wanna stay on 4.4 until all the stuff I use its compatible with 4.1.1, what I got to do to evade the auto-downloading of the ota and the spam about the update?
I don't know.. any way to stop the auto-update from working or so? That would be great!
Thanks in advance.
Click to expand...
Click to collapse
Here is what I just did, and it worked perfectly.
1. Take note of all the mods you installed so you can install them afterwards.
2. Put phone in bootloader mode / fastboot
3. Grab the 4.4 stock image from Google. Extract system.img file from it and flash that through fastboot (without the -w command) (fastboot flash system system.img). Don't worry you won't lose anything if you omit -w. Apps and data are preserved, it just set the \system area back to stock
4. Copy the OTA udpate zip to your phone, flash with TWRP. Since everything is 'back to stock' it should flash fine.
I had to re-root with TWRP after flashing before I rebooted. Everything was good to go. Then reflash your mods.
sonicdeth said:
Here is what I just did, and it worked perfectly.
1. Take note of all the mods you installed so you can install them afterwards.
2. Put phone in bootloader mode / fastboot
3. Grab the 4.4 stock image from Google. Extract system.img file from it and flash that through fastboot (without the -w command) (fastboot flash system system.img). Don't worry you won't lose anything if you omit -w. Apps and data are preserved, it just set the \system area back to stock
4. Copy the OTA udpate zip to your phone, flash with TWRP. Since everything is 'back to stock' it should flash fine.
I had to re-root with TWRP after flashing before I rebooted. Everything was good to go. Then reflash your mods.
Click to expand...
Click to collapse
Ok, that covers the a) situation where I want to flash it asap, thanks! (also note everyone, you got to disable xposed and all mods before flashing the ota)
PS: You can just flash the stock kernel and undo all the system changes, no need to flash the entire 4.4 stock zip.
What about the b) situation?
RusherDude said:
Ok, that covers the a) situation where I want to flash it asap, thanks! (also note everyone, you got to disable xposed and all mods before flashing the ota)
PS: You can just flash the stock kernel and undo all the system changes, no need to flash the entire 4.4 stock zip.
What about the b) situation?
Click to expand...
Click to collapse
Don't know why you'd want to go all the way back to 4.1.1. That's from July '12.
mattjorgs said:
Don't know why you'd want to go all the way back to 4.1.1. That's from July '12.
Click to expand...
Click to collapse
Wut? in the b) situation I just wanna STAY on 4.1 until all the stuff is ported to 4.1.1 (if something needs porting).
RusherDude said:
Wut? in the b) situation I just wanna STAY on 4.1 until all the stuff is ported to 4.1.1 (if something needs porting).
Click to expand...
Click to collapse
You mean 4.4? And 4.4.1? Lol
Sent from my Nexus 5 using Tapatalk
How to update to 4.4.1
I am rooted/bootloader unlocked with TWRP v2.6.3.1. When I try to flash in recovery manually with ota zip, I get a Failed error with error "E: error executing updater binary in zip"
What are step to update for a device like mine??
Cheeze[iT] said:
You mean 4.4? And 4.4.1? Lol
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Omg yea, 4.4 lol, fail haha
Related
Ok so I just recently got my hands on a Nexus 5 which I rooted with CF Auto Root and relocked the bootloader with Bootunlocker for security (I'm guessing I should unlock before the update). I see reports surfacing of a possible 4.4.3 update in the near future. So before that happens I want to figure out the best practice for updating a N5 with CF Auto Root. It stands to reason I'll do a full backup so that's a given.
I'm not new to rooting. Done it a few times. Just haven't had a device that gets regular OTAs in my country so it hasn't come up.
Is there a way to update so that root is preserved? Obviously I'd like to keep the process as simple as possible but if I have to work from scratch it's not the end of the world.
As I understand it, you can do normal OTA as long as it's stock but you lose root. In that case, does the OTA relock the bootloader or will it stay unlocked? Which then basically means a new root which wipes the device.
Or perhaps it's better to ask what the best procedure for updating a stock Nexus 5 with CF Auto Root.
Everything that you have ever wanted to know about OTA can be found here http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
Ah thanks. Appreciate it.
generally no, after ota you lose root. but there are apps that will save your root so that you keep root after an update.
I've been looking at Survival Mode in Super SU and RootKeeper but there seems to be some question as to their success.
Reaper1242 said:
I've been looking at Survival Mode in Super SU and RootKeeper but there seems to be some question as to their success.
Click to expand...
Click to collapse
ive never used any since i dont ota, i update my custom rom as soon as its updated, but ive heard of success with rootkeeper. but it doesnt matter, it literally takes 3 minutes to root a nexus the right way(via fastboot).
Yea, I should use fastboot in future.
Reaper1242 said:
As I understand it, you can do normal OTA as long as it's stock but you lose root. In that case, does the OTA relock the bootloader or will it stay unlocked? Which then basically means a new root which wipes the device.
Click to expand...
Click to collapse
The stock Android OS update will not relock the bootloader. So, once you apply the OTA.zip file in recovery, all you will need to do is reflash the SuperSU, and you are done.
(Note that depending on your system status, you may not be able to apply the OTA.zip directly - for instance, if you have updated/deleted system files etc, in which case, you will first need to go back to stock - refer to the link that @mistahseller provided for details about how to go back to stock)
jj14 said:
The stock Android OS update will not relock the bootloader. So, once you apply the OTA.zip file in recovery, all you will need to do is reflash the SuperSU, and you are done.
(Note that depending on your system status, you may not be able to apply the OTA.zip directly - for instance, if you have updated/deleted system files etc, in which case, you will first need to go back to stock - refer to the link that @mistahseller provided for details about how to go back to stock)
Click to expand...
Click to collapse
you would need to flash a custom recovery first, then supersu in your custom recovery.
Thanks everyone for the responses.You've made everything much clearer.
simms22 said:
you would need to flash a custom recovery first, then supersu in your custom recovery.
Click to expand...
Click to collapse
Good point. I assumed that op had installed a custom recovery when he rooted, but that is not always the case.
Ok so I'm going to sideload myself. Been a while so I just want to confirm the process so I don't screw up.
I'm using TWRP
Obviously I'll do a NANdroid and probably Titanium as well.
1) Unlock bootloader with Bootunlocker
2) Connect device to PC
3) Boot into TWRP recovery and go to Advanced > ADB Sideload
4) type adb sideload update.zip (or whatever I call the file)
5) reboot device and check if it's working
6) reboot to recovery and reflash superuser.zip
I think that's it. Is there anything else I need to be aware of? If I'm right it should then be updated, rooted and in the same state before I updated.
I am in the same situation. I am currently rooted with a unlocked boot loader. When 4.4.3 comes along I plan to upgrade it. I have only rooted and have CWM no custom ROM. I know o cannot perform a OTA update. So do I copy the update zip (4.4.3) and just flash in CWM? Is this correct, and if so do I lose root/ boot loader. Thanks. I have read the thread above but do not understand
Sent from my Nexus 5 using XDA Premium 4 mobile app
dec1153 said:
I am in the same situation. I am currently rooted with a unlocked boot loader. When 4.4.3 comes along I plan to upgrade it. I have only rooted and have CWM no custom ROM. I know o cannot perform a OTA update. So do I copy the update zip (4.4.3) and just flash in CWM? Is this correct, and if so do I lose root/ boot loader. Thanks. I have read the thread above but do not understand
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Flash stock system.img and flash recovery.img and then do the update.zip from the stock recovery..
If you don't want to flash, then make sure you have removed all the modifications you have done to system apps. If you don't remember then I would certainly recommend flashing stock images...
Sent from my Nexus 5 using Tapatalk
Currently running Android 4.4.3. I have TWRP installed. To upgrade can I just flash system.img and radio.img within TWRP? I believe that this is how I upgraded from 4.4.2 to 4.4.3 but my memory is hazy and this was before I installed a custom kernel. I'm not sure on whether I need to do anything additional such as rolling back to stock 4.4.3 before upgrading to 4.4.4. I've seen people discuss this but I think that's just if one wants to run the OTA update.
you can. or you can just dirty flash(no wiping) a stock rooted rom from the android development section, and your kernel, and reboot
prnz said:
Currently running Android 4.4.3. I have TWRP installed. To upgrade can I just flash system.img and radio.img within TWRP? I believe that this is how I upgraded from 4.4.2 to 4.4.3 but my memory is hazy and this was before I installed a custom kernel. I'm not sure on whether I need to do anything additional such as rolling back to stock 4.4.3 before upgrading to 4.4.4. I've seen people discuss this but I think that's just if one wants to run the OTA update.
Click to expand...
Click to collapse
You are correct, except you flash img files with fastboot.
Aerowinder said:
You are correct, except you flash img files with fastboot.
Click to expand...
Click to collapse
Thanks. Is there any way to do it from recovery? I hate having to hook up the USB cable, etc.
Also, this seems a lot easier than what is suggested here (Special Scenario #1) http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
1) downloaded factory image from https://developers.google.com/androi...ges#hammerhead
2) extract the tgz, the tar within that, then extract the the zip within that to get the system.img and boot.img files
3) moved these two files into the adb folder (for the fastboot/adb method)
4) downloade SuperSU-v1.80.zip from http://download.chainfire.eu/supersu
5) put SuperSU-v1.80.zip on your phone's internal storage
6) download the 4.4.1 OTA update zip from http://android.clients.google.com/pa...M.7ed504f6.zip
7) rename it to ota.zip
8) move ota.zip onto your phone's internal storage
9) boot into bootloader
10) open command prompt from your adb folder
11) connect USB cable
12) type 'fastboot devices' to check the connection
13) type 'fastboot flash system system.img'
14) type 'fastboot flash boot boot.img'
15) use volume and power buttons to boot into recovery (TWRP)
16) install ota.zip
17) install SuperSU-v1.80.zip
18) clear dalvik and cache
19) reboot phone
Click to expand...
Click to collapse
Seems to me like people go to a lot of extra work installing the OTA instead of the factory images.
prnz said:
Thanks. Is there any way to do it from recovery? I hate having to hook up the USB cable, etc.
Also, this seems a lot easier than what is suggested here (Special Scenario #1) http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
Seems to me like people go to a lot of extra work installing the OTA instead of the factory images.
Click to expand...
Click to collapse
extra work is done in both those methods. just dirty flash a precompiled rooted stock rom and your kernel. itll take seconds to a minute, and you wont lose anything. and you do that in recovery.
simms22 said:
extra work is done in both those methods. just dirty flash a precompiled rooted stock rom and your kernel. itll take seconds to a minute, and you wont lose anything. and you do that in recovery.
Click to expand...
Click to collapse
Not to create a flamewar but I'm too afraid of security issues to install a pre-rooted ROM.
prnz said:
Not to create a flamewar but I'm too afraid of security issues to install a pre-rooted ROM.
Click to expand...
Click to collapse
have you ever seen or heard(a real one, not just "stories") of a security issue?
prnz said:
Not to create a flamewar but I'm too afraid of security issues to install a pre-rooted ROM.
Click to expand...
Click to collapse
The ones on XDA are safe. Just as safe as you rooting your stock ROM.
Sent from my Nexus 5 using Tapatalk
I just got the OTA Update to Lollipop
and after i download the files, i press the install and reboot,then my nexus goes to recovery mode (CWM 6)
and then there appears :
. . . (theres still some description)
E:signature verification failed
then i just reboot and get my nexus still on 4.4
im actually forget which ROM im using right now
but in settings , it is KTU84P
FYI : I just unrooted this devices and this happened too when i was trying to upgrade with Nexus Update Checker.
Please help me guys
you need to be STOCK for OTA to work. Custom recovery, custom rom, any modifications to system etc will all prevent OTA from working.
jasonftfw said:
you need to be STOCK for OTA to work. Custom recovery, custom rom, any modifications to system etc will all prevent OTA from working.
Click to expand...
Click to collapse
how to make it sure/check it , that im using stock ROM or not
and how to uninstall CWM ?
Flash stock recovery and did you make any modifications to stock ROM or flash a custom ROM? If so you need to undo all mods and replace anything you removed that is part of system, or just install stock.
jasonftfw said:
Flash stock recovery and did you make any modifications to stock ROM or flash a custom ROM? If so you need to undo all mods and replace anything you removed that is part of system, or just install stock.
Click to expand...
Click to collapse
I'm having the same problem, I had already flashed /system and /boot back to stock, just didn't flash recovery (because it wasn't needed before on KK), now I've flashed everything back to stock, but now it says "system up to date" how do i solve this now? I did grab the ota zip, so maybe i can force it to flash with that zip on the stock recovery?
DarknessWarrior said:
I'm having the same problem, I had already flashed /system and /boot back to stock, just didn't flash recovery (because it wasn't needed before on KK), now I've flashed everything back to stock, but now it says "system up to date" how do i solve this now? I did grab the ota zip, so maybe i can force it to flash with that zip on the stock recovery?
Click to expand...
Click to collapse
Yeah, download ota file and sideload it, otherwise you're waiting for the ota to become available to you again via download on device.
jasonftfw said:
Yeah, download ota file and sideload it, otherwise you're waiting for the ota to become available to you again via download on device.
Click to expand...
Click to collapse
I have my own ota file (grabbed it from the /cache partition before flashing stock), how do i sideload it?
---------- Post added at 03:01 AM ---------- Previous post was at 02:56 AM ----------
DarknessWarrior said:
I have my own ota file (grabbed it from the /cache partition before flashing stock), how do i sideload it?
Click to expand...
Click to collapse
just got the OTA notification again, so I'll give it another shot (yeah, i just quoted myself)
DarknessWarrior said:
I have my own ota file (grabbed it from the /cache partition before flashing stock), how do i sideload it?
Click to expand...
Click to collapse
Use cmd prompt to use adb. You'll need android SDK if you don't have it. Navigate in cmd where your adb is (also have your update.zip in that directory). Run adb and then adb reboot boot loader, wait for boot loader, on device go to recovery. Once recovery is up, press vol up while holding power to access menu, go to apply update from adb then back in cmd run adb sideload update.zip
jasonftfw said:
Use cmd prompt to use adb. You'll need android SDK if you don't have it. Navigate in cmd where your adb is (also have your update.zip in that directory). Run adb and then adb reboot boot loader, wait for boot loader, on device go to recovery. Once recovery is up, press vol up while holding power to access menu, go to apply update from adb then back in cmd run adb sideload update.zip
Click to expand...
Click to collapse
thanks but I got the OTA notification again and is now installing without problems
DarknessWarrior said:
thanks but I got the OTA notification again and is now installing without problems
Click to expand...
Click to collapse
Never hurts to know how to sideload for future.
jasonftfw said:
Never hurts to know how to sideload for future.
Click to expand...
Click to collapse
agreed.
I just installed Android Sdk and downloaded the ota from google and im having problems it doesnt side load
jasonftfw said:
Flash stock recovery and did you make any modifications to stock ROM or flash a custom ROM? If so you need to undo all mods and replace anything you removed that is part of system, or just install stock.
Click to expand...
Click to collapse
DarknessWarrior said:
I'm having the same problem, I had already flashed /system and /boot back to stock, just didn't flash recovery (because it wasn't needed before on KK), now I've flashed everything back to stock, but now it says "system up to date" how do i solve this now? I did grab the ota zip, so maybe i can force it to flash with that zip on the stock recovery?
Click to expand...
Click to collapse
sry i already forgot all about these things (flashing,etc.)
so how is the easiest way to flash stock Recovery ?
or should i direct flash the stock ROM ? but is it gonna delete all of my datas ?
Thanks for your answer btw
Falconite said:
sry i already forgot all about these things (flashing,etc.)
so how is the easiest way to flash stock Recovery ?
or should i direct flash the stock ROM ? but is it gonna delete all of my datas ?
Thanks for your answer btw
Click to expand...
Click to collapse
check out the toolkit from wugfresh, that might be the easiest way for you if you don't know what you're doing... maybe take some notes so that you do remember what you're doing for future.
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.
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