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
Hi there,
So my new OPO came with a build of CM11S which doesn't appear to have any OTA updates, or the OTA function has been disabled. I have heard about this new CO12 update (YNG1TAS2I3) which is supposed to fix the touchscreen issues once and for all, and I would like to move up to this latest official build. I would like to keep all of my data partition intact if it can be done because without root, there doesn't seem to be any way of backing up data/apps. I am not rooted so I only have the original stock recovery.
I just want to point out that I don't have any touchscreen issues on this OPO, my first One had these issues and I sent it back and was given a replacement. With this 2nd OPO, I wanted to stay away from lollipop until the issue was fixed in a new update, which seems to have happened now.
My question is, which official build should I flash/install?, and which would be the best method to do this? (without rooting ) I was thinking, flash the latest CM11S and see if the OTA updates will take me up to the latest build
Im currently on CM11.0-XNF9XBS28K - Build No. KTU84Q.
Thanks
See section 8 of my guide here:
http://forum.xda-developers.com/showthread.php?t=2839471
Your guide says that i need an unlocked bootloader for step 8. And to unlock boot my bootloader, means the data will be wiped. Can I use the stock recovery to just flash the update zip? Or will that also wipe my data?
donk165 said:
Your guide says that i need an unlocked bootloader for step 8. And to unlock boot my bootloader, means the data will be wiped. Can I use the stock recovery to just flash the update zip? Or will that also wipe my data?
Click to expand...
Click to collapse
You can use stock recovery to flash an update zip. But you really should unlock your bootloader anyway, you're gonna need it unlocked just in case something goes wrong in future, it's best to do it now while you can actually backup your data.
Heisenberg said:
You can use stock recovery to flash an update zip. But you really should unlock your bootloader anyway, you're gonna need it unlocked just in case something goes wrong in future, it's best to do it now while you can actually backup your data.
Click to expand...
Click to collapse
Okay, well how can I back my data up from here? I know your guide says I should do the unlock when I first get the phone, but I've already been using the phone for about 3-4 weeks.
Back on my first OPO, when I was being told to do the display patches, I tried omegavesko's Simple ADB Backup and when it came to restoring, it didn't really work properly, many things got missed despite it being a "full backup". I assumed because I'm upgrading from Kitkat to Lollipop, I can just apply the update and my data will be kept intact?
donk165 said:
Okay, well how can I back my data up from here? I know your guide says I should do the unlock when I first get the phone, but I've already been using the phone for about 3-4 weeks.
Back on my first OPO, when I was being told to do the display patches, I tried omegavesko's Simple ADB Backup and when it came to restoring, it didn't really work properly, many things got missed despite it being a "full backup". I assumed because I'm upgrading from Kitkat to Lollipop, I can just apply the update and my data will be kept intact?
Click to expand...
Click to collapse
Just copy any important personal data (images, music, etc) from your internal storage to your PC. You can't do anything about your apps though unfortunately. The update won't wipe any of your data.
Heisenberg said:
Just copy any important personal data (images, music, etc) from your internal storage to your PC. You can't do anything about your apps though unfortunately. The update won't wipe any of your data.
Click to expand...
Click to collapse
Okay, I have taken all of my needed files, did SMS and call log backups and I'm ready to unlock the bootloader, so do i just do step 1 of your guide then straight to step 8? I was gonna fastboot the latest CM11 build and then after that should I wait for OTA or just do another fastboot session but this time use the CO12 build?
Just installed all the USB and fastboot drivers now.
Edit: Its all done now, I unlocked the bootloader, then I used the fastboot version of cm-11.0-XNPH05Q and did all the fastboot commands to give me the latest CM11, then i was prompted with a pre-requisite update before CO12, then after I got the update to cm-12.0-YNG1TAS17L. After those, I didn't get an OTA to the newest CO12, so then finally I downloaded and applied the incremental OTA from YNG1TAS17L to YNG1TAS2I3 and installed that through CM stock recovery.
donk165 said:
Okay, I have taken all of my needed files, did SMS and call log backups and I'm ready to unlock the bootloader, so do i just do step 1 of your guide then straight to step 8? I was gonna fastboot the latest CM11 build and then after that should I wait for OTA or just do another fastboot session but this time use the CO12 build?
Just installed all the USB and fastboot drivers now.
Edit: Its all done now, I unlocked the bootloader, then I used the fastboot version of cm-11.0-XNPH05Q and did all the fastboot commands to give me the latest CM11, then i was prompted with a pre-requisite update before CO12, then after I got the update to cm-12.0-YNG1TAS17L. After those, I didn't get an OTA to the newest CO12, so then finally I downloaded and applied the incremental OTA from YNG1TAS17L to YNG1TAS2I3 and installed that through CM stock recovery.
Click to expand...
Click to collapse
Cool, so you're all good?
Heisenberg said:
Cool, so you're all good?
Click to expand...
Click to collapse
Yeah man, all good now, thank you for pointing me in the right direction. That CM11 I started on was weird having no OTA updates, and I was very wary after CO12 on my first OPO and then getting touchscreen problems. I'm glad this new build is out with the fixes. Hopefully I'll never see those issues on this phone now.
My v10 downloaded an OTA , which im assuming is 6.0
1. Im rooted on stock 6.0 and unlocked boot loader. Will the OTA work without messing up anything ? Ill have to root again im sure, just want some info before i pull the trigger.
I don't think the update will even proceed being that you're on a rooted ROM. I have that notification too, and i just don't know how to turn it off.
I to am rooted,unlockboot and stock rom. I don't feel like taking a chance. So I used titanium backup to freeze the software update and in the drop down notification if you press it, it's a notification from Google play services if you block it in apps it will disappear from your drop down. I also deleted the update zip in the cache folder.I used es file explorer ,device/cache/update
popwar said:
My v10 downloaded an OTA , which im assuming is 6.0
1. Im rooted on stock 6.0 and unlocked boot loader. Will the OTA work without messing up anything ? Ill have to root again im sure, just want some info before i pull the trigger.
Click to expand...
Click to collapse
Okay, I'm assuming you are on H90120e (system version). There is a root exploit for the H90120j update. You just do the following:
Make a backup of your apps and settings
Flash your phone to the new update (H90120j)?
Take a look at either one of these threads to root your device again:
http://forum.xda-developers.com/tmobile-lg-v10/general/step-step-guide-rooting-lg-v10-using-t3382631
OR
http://forum.xda-developers.com/tmobile-lg-v10/general/root-android-6-0-h901-t3382819
You can't flash the phone that is already rooted and has TWRP.
I am in this same situation. On stock rom with root and twrp. I want to update to the new update, but do not want to loose all my apps, settings, etc.
Question is, how to do the initial update before having to re-root again?
How do we flash the phone with the new update?
bhagiratha said:
You can't flash the phone that is already rooted and has TWRP.
I am in this same situation. On stock rom with root and twrp. I want to update to the new update, but do not want to loose all my apps, settings, etc.
Question is, how to do the initial update before having to re-root again?
How do we flash the phone with the new update?
Click to expand...
Click to collapse
Why can't you flash the phone that is already rooted and has TWRP?
All you are doing is opening the LGUP tool and flashing the new H90120j .kdz file using the "refurbish" option then flashing the H90120j .tot file that has TWRP using the "update" option which will flash the phone regardless of what is running on your phone. The guides on the first link explain that. I believe your concern is keeping all of your settings and apps. Look up Titanium backup, it works for me.
Thank you. I only flash the LGH901AT-01-V20j-310-260-JUL-12-2016-ARB02+0ROOTTWRP tot file and all is good.
Well except that I lost Dolby audio.
I will look for a fix.
jun19inf said:
Okay, I'm assuming you are on H90120e (system version). There is a root exploit for the H90120j update. You just do the following:
Make a backup of your apps and settings
Flash your phone to the new update (H90120j)?
Take a look at either one of these threads to root your device again:
http://forum.xda-developers.com/tmobile-lg-v10/general/step-step-guide-rooting-lg-v10-using-t3382631
OR
http://forum.xda-developers.com/tmobile-lg-v10/general/root-android-6-0-h901-t3382819
Click to expand...
Click to collapse
Hi,
Do I have to use LGUP to install the update or can I click install on the dropdown of my phone?
I'm on stock MM 6.0 (H90120e) Rooted and I will not have access to my main PC for another week as I'm traveling.
Thanks,
-NJ
Anyone?
bhagiratha said:
You can't flash the phone that is already rooted and has TWRP.
I am in this same situation. On stock rom with root and twrp. I want to update to the new update, but do not want to loose all my apps, settings, etc.
Question is, how to do the initial update before having to re-root again?
How do we flash the phone with the new update?
Click to expand...
Click to collapse
There's a guide in general that tells how to do all this. In fact jun19inf WROTE it.
In a nutshell, do a twrp backup.
Upgrade to 20j by flashing the stock 20j kbz.
Enable usb debugging and oem unlock
flash tot that has twrp in it.
Now you can go into twrp and 1) root via supersu 2) restore ONLY data from your twrp backup taken previously to get your apps etc back. Alternatively Titanium Backup will also do just fine.
njdevils28 said:
Hi,
Do I have to use LGUP to install the update or can I click install on the dropdown of my phone?
I'm on stock MM 6.0 (H90120e) Rooted and I will not have access to my main PC for another week as I'm traveling.
Thanks,
-NJ
Click to expand...
Click to collapse
If all is you have is root, you should be able to unroot in the SuperSU settings, and then let the update install. But if you have TWRP, then I can't see any way to do the update without using a PC to flash your phone back to stock ROM and recovery. Although you may check the dev. section to see if Eliminator has a flashable ROM to bring you up to date.
Sent from my LG-H901 using XDA-Developers mobile app
YrrchSebor said:
If all is you have is root, you should be able to unroot in the SuperSU settings, and then let the update install. But if you have TWRP, then I can't see any way to do the update without using a PC to flash your phone back to stock ROM and recovery. Although you may check the dev. section to see if Eliminator has a flashable ROM to bring you up to date.
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
Ah. Thank you very much!
-NJ
Hi all. I just got my factory warranty back and I attempted to root it. Everything went as it should, until just after the install finished. Instead of rebooting normally, it now will only reboot into TWRP. Once there, when I try to flash a custom ROM (in this case, Bliss, but I don't think it matters, I get an error message that says the zip file is corrupt. Then, while still in recovery, when I tried to wipe everything except the sd card, it says mkfs.fat process ended with error. I then powered down and attempted the factory reset. I scrolled down on both screens and it did not say anything about any errors, so I assumed it took. However, it reboots right back into TWRP recovery. It also boots right to TWRP recovery when I try to boot normally. Of course, adb does not recognize the phone in any mode that I can get into (fastboot/recovery/download), so, I can't use LG Bridge to reflash the original firmware. Does anybody have any ideas for a fix? I know that this replacement phone had 6.0 on it. I thought I did everything to a t? TIA...
OK, not sure how I got there, but when I attempt to reboot from TWRP it says No OS Installed! Are you sure you want to reboot? That at least says what the problem is. Does anybody know how to fix this?
Where can I download the update file?
wbexpress said:
Hi all. I just got my factory warranty back and I attempted to root it. Everything went as it should, until just after the install finished. Instead of rebooting normally, it now will only reboot into TWRP. Once there, when I try to flash a custom ROM (in this case, Bliss, but I don't think it matters, I get an error message that says the zip file is corrupt. Then, while still in recovery, when I tried to wipe everything except the sd card, it says mkfs.fat process ended with error. I then powered down and attempted the factory reset. I scrolled down on both screens and it did not say anything about any errors, so I assumed it took. However, it reboots right back into TWRP recovery. It also boots right to TWRP recovery when I try to boot normally. Of course, adb does not recognize the phone in any mode that I can get into (fastboot/recovery/download), so, I can't use LG Bridge to reflash the original firmware. Does anybody have any ideas for a fix? I know that this replacement phone had 6.0 on it. I thought I did everything to a t? TIA...
OK, not sure how I got there, but when I attempt to reboot from TWRP it says No OS Installed! Are you sure you want to reboot? That at least says what the problem is. Does anybody know how to fix this?
Click to expand...
Click to collapse
Did you select refurbish or upgrade?
I believe you need to select upgrade when flashing or you get stuck in TWRP
Sent from my LG-H901 using XDA-Developers mobile app
How to root V10 T-mobile M.M ver V20L
How to root V10 T-mobile M.M ver V20L
Can some one guide me on the following:
1. Can I flash back and downgrade to Software version V20J from V20L.
2. Is there any root method for V10 t-mobile MM ver V20L.
1. It is well explained in this forum, you CANNOT go back without facing a software brick.
2. You can root your phone through Dirty_Cow method or by flash Eliminater74 ROM (Part1 & Part2).
Again, search for that in this section and in development one...
jonsat said:
1. It is well explained in this forum, you CANNOT go back without facing a software brick.
2. You can root your phone through Dirty_Cow method or by flash Eliminater74 ROM (Part1 & Part2).
Again, search for that in this section and in development one...
Click to expand...
Click to collapse
Thanks so much for your reply, I was about to flash it to downgrade my V10 from V20L to V20J i even downloaded the files for it Phew....
Okay, I have searched most of the rootings are V20J i have not found a method for rooting and twrp for V20L software update.
Please if u can share the link, that would be helpful...
thanks regards,
I wonder how people perform searches... by the way, few lines under this very thread, there is:
https://forum.xda-developers.com/tmobile-lg-v10/general/root-20l-dirty-cow-t3498722
jonsat said:
I wonder how people perform searches... by the way, few lines under this very thread, there is:
https://forum.xda-developers.com/tmobile-lg-v10/general/root-20l-dirty-cow-t3498722
Click to expand...
Click to collapse
Awwhh GOD!!! big thanks for your help, u r truly an awesome person. Peace and blessing upon u.
regards,
Hi
I really need help to go stock on my device.
I unlocked my bootloader, flashed TWRP and Magisk on stock rom and installed the ViperU Magisk Module.
I also made a NANDROID of the stock ROM before, unfortunately there is no Recovery in it, since i had TWRP already installed.
Then an OTA (oktober 17 security patch) was available for my device and i startet the install process, but it didn't install.
TWRP open recovery would run not even 1 second then exit.
In order to get the OTA I restored stock recovery (which i had to extract from OTA, since i forgot to back it up) and started OTA.
--> Red Triangle!
Even after restoring stock NANDroid the OTA wouldn't install.
My mistake i think was that i didn't kept the stock system read only when i did the backup in twrp and swiped to allow modifications.
According to some threads here, even mounting the system r/w would break OTA functionality.
So since i also have no RUU for my device, i don't have the chance either to go back to stock. Maybe you did that mistake too.
The only way i can think of now, is to go temporary S-OFF, change CID and MID (to 401 international for example), flash Firmware and run the RUU for it.
But i'm not sure it'll still work after flashing the firmware.
Can anyone maybe confirm this way would work?
And is there an other way available?
Thanks!
Quick Specs:
-Unlocked Bootloader
-S-ON
-Firmware: 1.27.166.7
-CID: VODAP110
-MID: 2PZC10000
Nightmare
Quick Specs:
-Unlocked Bootloader
-S-ON
-Firmware: 1.27.166.7
-CID: VODAP110
-MID: 2PZC10000[/QUOTE said:
Hello, Have you looked at this list to see if you could take one from here?
https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit#gid=0
Click to expand...
Click to collapse
michaelbsheldon said:
Hello, Have you looked at this list to see if you could take one from here?
https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit#gid=0
Click to expand...
Click to collapse
Hi
Yes, unfortunately there's nothing available for my device.
Does the phone boot into os?
You cannot take an OTA with TWRP. You need an untouched system image to take the OTA. Easiest way is to RUU to your current firmware. Let the system update.
schmeggy929 said:
You cannot take an OTA with TWRP. You need an untouched system image to take the OTA. Easiest way is to RUU to your current firmware. Let the system update.
Click to expand...
Click to collapse
Actually that's not true, TWRP appareantly has a open recovery which works with OTA.
Also the RUU doesn't have to match your Firmware.
What i did was following:
-Had TWRP and a running ROM, rootet with magisk
-Downloded a RUU for my MID (picked the 401 one for international unlocked, i think you can take any)
-Installed sunshine and went temp s-off
-Went into download mode and changed cid to a matching one (HTC__034 -> Europe for me, there are other compatibles)
-Renamed the RUU (2PZCIMG.zip) and put it in the root of my SD-Card
-Inserted the SD-Card and rebootet to download (there's an option in download mode for that)
-pressed volume up to start installation
-Done, phone reboots with stock system, stock recovery and right firmware
Also I installed TWRP right back and magisk and tried to take the OTA. It installed without problems through TWRP.
Afaik, it will work, but replace TWRP in the end, so you will have to reflash twrp after every OTA, or you just take the recovery out of the
OTA and flash it through SD-Card (you have to rename it).
So that's the way to go if you have to go stock and there's nothing in the collection for your version.
Hope this helps.
Edit: Please remember to keep TWRP in read only! you will still be able to flash zips like magisk for example.
Hey,
after you had flashed the 004 Ruu, did you change S-off back to S-On?
2eli0 said:
Hey,
after you had flashed the 004 Ruu, did you change S-off back to S-On?
Click to expand...
Click to collapse
since s-off is still temporary it will go back to s-on as soon as you boot into recovery or rom.
also, i flashed the 1.27.401.5 ruu, since i wanted to see if the update to 1.27.401.12 ota works with twrp and magisk installed.
it does, just remember to keep recovery read only!
What do you mean by "read only"? Is there a setting where I can do that?
2eli0 said:
What do you mean by "read only"? Is there a setting where I can do that?
Click to expand...
Click to collapse
If you take a bone stock phone (when you buy it for example, or after running a ruu), the first time you flash twrp and
boot into it, it will ask you if you want to keep the system in read only, in order not to break the OTA functionality.
But you won't be able to restore backups or install zip which changes system partition (Custom ROMs, xposed, etc.).
If you want to keep OTA functionality, you can keep it read only and still be able to flash zips like magisk and so on.
Once you swipe to allow modifications doe, there is no way back, so keep that in mind!
Mounting the system partition once in rw (read/write) will break OTA permanently.
If you ever decide that you want to modify the system partition anyway (going custom ROM) you can change the setting:
TWRP-->Mount-->"Mount system partition read only"-->uncheck it
Correct me if i'm wrong.
Nightmare[ITA said:
;75529278]If you take a bone stock phone (when you buy it for example, or after running a ruu), the first time you flash twrp and
boot into it, it will ask you if you want to keep the system in read only, in order not to break the OTA functionality.
But you won't be able to restore backups or install zip which changes system partition (Custom ROMs, xposed, etc.).
If you want to keep OTA functionality, you can keep it read only and still be able to flash zips like magisk and so on.
Once you swipe to allow modifications doe, there is no way back, so keep that in mind!
Mounting the system partition once in rw (read/write) will break OTA permanently.
If you ever decide that you want to modify the system partition anyway (going custom ROM) you can change the setting:
TWRP-->Mount-->"Mount system partition read only"-->uncheck it
Correct me if i'm wrong.
Click to expand...
Click to collapse
Ah ok, got it.
I would want to keep the OTA functionality, since I want to keep it stock with root privileges. That's all.
I won't try custom roms anytime soon. Thanks for the tip.
If I had known that before I flashed twrp I would have been able to update OTA now, right?
2eli0 said:
Ah ok, got it.
I would want to keep the OTA functionality, since I want to keep it stock with root privileges. That's all.
I won't try custom roms anytime soon. Thanks for the tip.
If I had known that before I flashed twrp I would have been able to update OTA now, right?
Click to expand...
Click to collapse
Pretty much, ya. I missed that part the first time too
Nightmare[ITA said:
;75529808]Pretty much, ya. I missed that part the first time too
Click to expand...
Click to collapse
Ahh, dang it. Well, I'd say we learn by mistakes.
Thanks for the hint.
I will try the version you tried. It's still downloading.
Btw. did the download take like ages for you?
During the day I get like 100-200 KB/s and sometimes even less. In the evening like 11 pm it's 3 MB/s...
My connection is fine.
2eli0 said:
Ahh, dang it. Well, I'd say we learn by mistakes.
Thanks for the hint.
I will try the version you tried. It's still downloading.
Btw. did the download take like ages for you?
During the day I get like 100-200 KB/s and sometimes even less. In the evening like 11 pm it's 3 MB/s...
My connection is fine.
Click to expand...
Click to collapse
Yes, over the last few months AFH has been extremely slow.
Ok I will state it in another way. The easiest way to take the OTA is on an Untouched System and Recovery Image lol. You can with TWRP however the firmware will not flash. Hence probably your problem. You do know there is an RUU for 2.33.166.6 for your carrier. https://www.htcdev.com/devcenter/downloads
I have already seen that, but its like 400 mb big, if I remember correctly, hence not the entire files, right?
schmeggy929 said:
Ok I will state it in another way. The easiest way to take the OTA is on an Untouched System and Recovery Image lol. You can with TWRP however the firmware will not flash. Hence probably your problem. You do know there is an RUU for 2.33.166.6 for your carrier. https://www.htcdev.com/devcenter/downloads
Click to expand...
Click to collapse
lol. That's the site i was searching for.
But since it's the source code, you would have to compile it first, right?
Anyway, are you sure? Cause from what i can see the firmware got updated too.
In fact, in this post under point 4. it states, that it's working.
The htcdev stuff is source only. No good. Also, once you flash twrp you can't take ota. You must be stock to take ota (s-off and bootloader remain untouched and do not matter for flashing, there is no need to s-on nor relock the bootloader ever).
To achieve stock just flash the same firmware you currently use as a zip from the external sdcard. The only things lost is root and twrp.
Nightmare[ITA] said:
lol. That's the site i was searching for.
But since it's the source code, you would have to compile it first, right?
Anyway, are you sure? Cause from what i can see the firmware got updated too.
In fact, in this post under point 4. it states, that it's working.
Click to expand...
Click to collapse
Yeah i guess you are right it is the source code. Even with TWRP stills seems like a lot of work to update. Ya'll need some custom ROMs installed. Flash signed firmware.zip, reflash TWRP and flash updated ROM. All done. If by chance you ever needed to return to stock, flash your system image backup. Ya'll make things so complicated when they really aren't. lol
Nightmare[ITA said:
]Actually that's not true, TWRP appareantly has a open recovery which works with OTA.
Also the RUU doesn't have to match your Firmware.
What i did was following:
-Had TWRP and a running ROM, rootet with magisk
-Downloded a RUU for my MID (picked the 401 one for international unlocked, i think you can take any)
-Installed sunshine and went temp s-off
-Went into download mode and changed cid to a matching one (HTC__034 -> Europe for me, there are other compatibles)
-Renamed the RUU (2PZCIMG.zip) and put it in the root of my SD-Card
-Inserted the SD-Card and rebootet to download (there's an option in download mode for that)
-pressed volume up to start installation
-Done, phone reboots with stock system, stock recovery and right firmware
Also I installed TWRP right back and magisk and tried to take the OTA. It installed without problems through TWRP.
Afaik, it will work, but replace TWRP in the end, so you will have to reflash twrp after every OTA, or you just take the recovery out of the
OTA and flash it through SD-Card (you have to rename it).
So that's the way to go if you have to go stock and there's nothing in the collection for your version.
Hope this helps.
Edit: Please remember to keep TWRP in read only! you will still be able to flash zips like magisk for example.
Click to expand...
Click to collapse
Well, I managed to do it exactly the way you did.
Everything worked just fine. I changed the CID to HTC__034 and flashed the ruu file updated to Oreo and flashed TWRP kept it at read only and rooted the phone.
Thanks for that :good:
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