Related
So I've stayed at 2.19.40.20 because I wanted to wait to see if a better way to unlock the bootloader would be found, but I've given up and unlocked my bootloader (the unoffical way).
I want to get up to speed and update to the latest OTA.
Can I just flash the latest one or do I need to download every one til the newest update and sideload them individually?
If I have to do each one can I just load them one after the other, or do I need to reboot the phone and let it fully load to the OS for every update?
I did side load the latest one when I was coming from the 18 something that came with my phone. Loading the full 1.1gig firmware did the trick.
So just for clarification, to take me from 2.19.40.20 to 2.20.40.139 I should just flash the latest Stock ROM from the ASUS site?
DiGecko said:
I did side load the latest one when I was coming from the 18 something that came with my phone. Loading the full 1.1gig firmware did the trick.
Click to expand...
Click to collapse
Azdinflash said:
So just for clarification, to take me from 2.19.40.20 to 2.20.40.139 I should just flash the latest Stock ROM from the ASUS site?
Click to expand...
Click to collapse
Yes that should do it.
I was seriously dreading having to update, but this shows that my worries were unfounded, thanks!
I don't need to unroot as I'm flashing the whole rom, right?
The_wolf88 said:
Yes that should do it.
Click to expand...
Click to collapse
Azdinflash said:
I was seriously dreading having to update, but this shows that my worries were unfounded, thanks!
I don't need to unroot as I'm flashing the whole rom, right?
Click to expand...
Click to collapse
You need to unroot and make sure you are sideloading the whole 1.1 gig one.
DiGecko said:
You need to unroot and make sure you are sideloading the whole 1.1 gig one.
Click to expand...
Click to collapse
Does unrooting include removing Xposed?
Yes, and don't try to install it after you get to 139 firmware, as far as I know it still causes bootloop.
Wait, if I flash the 1.1 gig stock ROM, do I lose everything in the internal memory?
DiGecko said:
Yes, and don't try to install it after you get to 139 firmware, as far as I know it still causes bootloop.
Click to expand...
Click to collapse
I did a little digging, and it seems that the bootloop was fixed a few days ago:
http://forum.xda-developers.com/zenfone2/general/guide-to-install-xposed-installer-t3116476/page26
J M L said:
There's a new Xposed out, v78, which claims to fix a bootloop on 5.0 roms due to a security fix. I haven't tried it yet because I'm running a backup. Here is the thread and changelog.
We want the sdk21-x86 version.
Installed with no problem in TWRP with the flash able zip. Took a few minutes to boot, but seems to be working.
Click to expand...
Click to collapse
Good to know. No, you would not loose anything, at least I did not. Everything migrated over without any issues.
So I've gotten through sideloading the current version with no hiccups. Booted into system fine, it's the right version in the About section, and my internal memory came through intact.
I've flashed TWRP, and booted into it to install SuperSU when I got this message: "TWRP may have detected an unmodified system partition"
It explains that I can keep it as read only and make it easier to take official updates, but then TWRP will not be able to stop the stock ROM from replacing it and will not offer to root my device.
Should I keep it "Read Only" or should I allow the modification?
Any one knows how to re-lock the bootloader of one plus 3???
And
How to remove that screen on boot up after unlocking one plus three??? :/
If you read the screen properly ull see the instructions on the screen itself do everything the same way you unlock the bootloader just instead of oem bootloader unlock type oem bootloader lock ...but make sure you're on stock rom and recovery
zubinvig said:
If you read the screen properly ull see the instructions on the screen itself do everything the same way you unlock the bootloader just instead of oem bootloader unlock type oem bootloader lock ...but make sure you're on stock rom and recovery
Click to expand...
Click to collapse
But then My root access will be wiped??
I want root access and dont want than annoying screen
two questions different answer but I would bet if there is a way to remove nag screen a google search would find it. Keep searching threads
there is no reason to re-lock bootloader, its still under warranty through Oneplus even with unlocked bootloader. but if u really want to
1. fastboot flash stock recovery (fastboot flash recovery recovery.img) (make sure u download the file, its somewhere here on the forums
2. reboot and then reboot to fastboot (fastboot oem lock) (i have never re locked a bootloader so i am not sure if it will rewipe ur device again like unlocking it does)
3. boot to OS and get developer options again and uncheck OEM Unlock (do this last)
i would not recommend re locking since it wont void warranty and seemed like a lot people screwed up their devices relocking it, but they also unchecked the oem unlock before flashing stock recovery, also i am not sure if step 2 is needed, i would just make sure u flash stock recovery 1st before doing anything
HELP
I try to relock the bootloader but in this momento my oneplus 3 is blocked...I cant update with the stock rom...please some help!!! :crying:
zubinvig said:
If you read the screen properly ull see the instructions on the screen itself do everything the same way you unlock the bootloader just instead of oem bootloader unlock type oem bootloader lock ...but make sure you're on stock rom and recovery
Click to expand...
Click to collapse
What happens if i follow same steps with installed FREEDOM OS on my oneplus 3. You said make sure you are in stock OS.
Once i have unlocked the phn my device doesn't get recognised by the pc when i use command" fastboot devices".. Now, i'm unable to flash twrp, plz solve my issue.!!!
Arun Ammineni said:
What happens if i follow same steps with installed FREEDOM OS on my oneplus 3. You said make sure you are in stock OS.
Click to expand...
Click to collapse
ecarchi said:
I try to relock the bootloader but in this momento my oneplus 3 is blocked...I cant update with the stock rom...please some help!!! :crying:
Click to expand...
Click to collapse
What part of be on stock OS is so hard to understand?
If you're not absolutely stock when relocking, you will brick your device.
Then good luck trying to enable OEM Unlocking when not being able to boot.
As someone who messes with their phone, relocking your bootloader is one of the worst possible things you can do.
If not done correctly, it WILL brick your device.
If you want to go back to stock, then surely do, there is absolutely no need to relock your boot loader unless you're selling your device to someone or if you're looking to pass SafetyNet for Android Pay or something.
Also, you cannot have the cake as well as eat it. You need to have an unlocked boot loader for root, exposed, etc. There is no way around this.
Phones previously had to be reverse engineered and exploited to gain root access, now OEMs freely allow unlocking.
kgs1992 said:
What part of be on stock OS is so hard to understand?
If you're not absolutely stock when relocking, you will brick your device.
Then good luck trying to enable OEM Unlocking when not being able to boot.
As someone who messes with their phone, relocking your bootloader is one of the worst possible things you can do.
If not done correctly, it WILL brick your device.
If you want to go back to stock, then surely do, there is absolutely no need to relock your boot loader unless you're selling your device to someone or if you're looking to pass SafetyNet for Android Pay or something.
Also, you cannot have the cake as well as eat it. You need to have an unlocked boot loader for root, exposed, etc. There is no way around this.
Phones previously had to be reverse engineered and exploited to gain root access, now OEMs freely allow unlocking.
Click to expand...
Click to collapse
I hope you can read this. I'm not a noob and I am looking to relock my bootloader because I am going to sell it. The person wants it fully stock so I need to relock the bootloader in order to regain access to official Ota updates.
I need to be on complete stock (stock recovery and rom) right? Would you please kindly point me to where I need to go to download the stock Rom and recovery. There's some TWRP flashable OTA zips on Oneplus forums that restore stock Rom and recovery but I want to be sure that that is enough and that I don't end up bricking my device for something as stupid as this. Any help would greatly be appreciated!
Arthurvben said:
I hope you can read this. I'm not a noob and I am looking to relock my bootloader because I am going to sell it. The person wants it fully stock so I need to relock the bootloader in order to regain access to official Ota updates.
I need to be on complete stock (stock recovery and rom) right? Would you please kindly point me to where I need to go to download the stock Rom and recovery. There's some TWRP flashable OTA zips on Oneplus forums that restore stock Rom and recovery but I want to be sure that that is enough and that I don't end up bricking my device for something as stupid as this. Any help would greatly be appreciated!
Click to expand...
Click to collapse
Fash 3.2.4 FW from here.
Follow all instructions from here (except I would suggest sideloading the StockROM before relocking).
Arthurvben said:
I hope you can read this. I'm not a noob and I am looking to relock my bootloader because I am going to sell it. The person wants it fully stock so I need to relock the bootloader in order to regain access to official Ota updates.
I need to be on complete stock (stock recovery and rom) right? Would you please kindly point me to where I need to go to download the stock Rom and recovery. There's some TWRP flashable OTA zips on Oneplus forums that restore stock Rom and recovery but I want to be sure that that is enough and that I don't end up bricking my device for something as stupid as this. Any help would greatly be appreciated!
Click to expand...
Click to collapse
I followed the same guide posted on OnePlus Forum to re-lock my bootloader. Just follow them, it works.
Here is that link from OnePlus forum.
1. I restored my stock rom backup from TWRP
2. Flashed Stock recovery
3. fastboot oem lock
4. Sideload stock ROM
Done.
I unlocked because stock ROM I felt was much stabler and hassle free. Have rooted and played with custom ROMs enough in my Nexus 5 days. Just too much stress and can end up with non-working features. Might root again in future if I find something compelling in custom ROM.
batmobile_bang said:
I followed the same guide posted on OnePlus Forum to re-lock my bootloader. Just follow them, it works.
Here is that link from OnePlus forum.
1. I restored my stock rom backup from TWRP
2. Flashed Stock recovery
3. fastboot oem lock
4. Sideload stock ROM
Done.
I unlocked because stock ROM I felt was much stabler and hassle free. Have rooted and played with custom ROMs enough in my Nexus 5 days. Just too much stress and can end up with non-working features. Might root again in future if I find something compelling in custom ROM.
Click to expand...
Click to collapse
If you unlock bootloader and root device. Do you still get OTA updates if you stay on stock ROM?
borijess said:
If you unlock bootloader and root device. Do you still get OTA updates if you stay on stock ROM?
Click to expand...
Click to collapse
If you unlock device, you will still be able to apply OTA. If you rooted by modifying the /system partition, OTA will fail, but if thou rooted using systemless method, you can apply OTA.
Iam on stock OOS 4.0.3 and i was plagued by the same error
--adb sideload the complete rom (with locked bootloader)-- method worked for me.
Previously i had unlocked bootloader and was on freedom OOS 2.3 with TWRP and then i realized that stock updates are better.
So i installed stock recovery and and tried to flash Stock Firmware 4.0.3 through sideload command and it failed.
then i installed TWRP and then installed stock OOS 4.0.3 and it installed fine but with some error.
Then i installed stock recovery
So i rebooted it and after long time it was installed but then i started getting dm_verity error and also i was frustated with unlocked bootloader message.
So i locked my boot loader first from fastboot oem lock and then sideloaded the stock 4.0.3 again and it really worked.
So now i am on stock rom and stock recovery and no more dm_verity error or unlocked bootloader msg to wait for 5 secs...
Now iam really loving my Oneplus 3..
Hi hope someone can verify.
I'm running stock 3.2.7 unrooted with stock recovery. The bootloader is still unlocked as I tried out a few custom ROMs about a month back. I now want to wipe and sell the phone so need to lock the bootloader. Can I just do the standard OEM lock in adb or should I also sideload the full 3.2.7 update zip again?
Thanks
just oem lock it. but everything will be removed when you do that.
Playa82 said:
just oem lock it. but everything will be removed when you do that.
Click to expand...
Click to collapse
Thanks, I thought so but I had to check. Strange... after rooting phones and installing custom ROMs for maybe 8 years, I don't think I've ever relocked a bootloader.
It's safer to flash stock again then to relock bootloader, even if you think you are stock (including recovery) maybe you are not.
But except the booting screen, you won't gain anything from relocking bootloader, even the warranty will work with bootloader unlocked.
SpaceGooner said:
Hi hope someone can verify.
I'm running stock 3.2.7 unrooted with stock recovery. The bootloader is still unlocked as I tried out a few custom ROMs about a month back. I now want to wipe and sell the phone so need to lock the bootloader. Can I just do the standard OEM lock in adb or should I also sideload the full 3.2.7 update zip again?
Thanks
Click to expand...
Click to collapse
Deleted my comment for incorrect information
Le_Zouave said:
It's safer to flash stock again then to relock bootloader, even if you think you are stock (including recovery) maybe you are not.
But except the booting screen, you won't gain anything from relocking bootloader, even the warranty will work with bootloader unlocked.
Click to expand...
Click to collapse
Thanks, but I plan to sell my OP3 to a high street store that buys and sells second-hand phones and tablets. Although it's only 3 months old and in immaculate condition, I'm guessing they may be reluctant to buy it if the start up screen says 'this phone can't be trusted...'
No choice in this situation - I will need to relock the bootloader I guess.
If you lock the bootloader, everything will be wiped and phone won't boot till you flash OOS.
ungeeked said:
If you lock the bootloader, everything will be wiped and phone won't boot till you flash OOS.
Click to expand...
Click to collapse
Thank you. So after OEM lock, when you say flash OOS do you mean sideload a full update zip? That's what I was asking in my original post.
SpaceGooner said:
Thank you. So after OEM lock, when you say flash OOS do you mean sideload a full update zip? That's what I was asking in my original post.
Click to expand...
Click to collapse
Yup.
SpaceGooner said:
Thank you. So after OEM lock, when you say flash OOS do you mean sideload a full update zip? That's what I was asking in my original post.
Click to expand...
Click to collapse
Follow:
https://forums.oneplus.net/threads/...lus-3-and-go-back-completely-to-stock.456232/
ritchiedrama said:
Follow:
https://forums.oneplus.net/threads/...lus-3-and-go-back-completely-to-stock.456232/
Click to expand...
Click to collapse
Ta mate. I already saw that thread but as I'm running a clean sideloaded OOS that has never been rooted, I am already back to stock. Anyway, as opinion seems to be divided on whether OEM lock alone is enough, I will also sideload a full OOS update zip again to be sure.
Won't be doing it for a few days though so it's all academic at the moment.
ritchiedrama said:
Follow:
https://forums.oneplus.net/threads/...lus-3-and-go-back-completely-to-stock.456232/
Click to expand...
Click to collapse
i did that guide too. i came from cm13. thiss guide works perfect if you follow all steps exactly.
Hey there,
I've got my first HTC device some days ago (-> HTC 10), but coming from a Nexus 5 where things are handled differently, I'm currently quite confused on how all of this works with my HTC 10.
I'd like to apologize in advance if the following questions seem to be stupid or unnecessary, but I'd like to use my device to the fullest and therefore I need your help.
My device is not branded (as far as I can tell) and I've already unlocked it via the steps on htcdev.com + I've installed TWRP + SuperSU (thanks to my previous knowledge with my N5 this was somewhat easy).
Now I got my first OTA update and this is when things got complicated. Several questions popped up and I tried to answer them myself while looking over here, but after reading all those threads I'm even more confused than before :/
My questions are the following:
1) Is there any way to manually update your device with the newest OTA update WITHOUT losing any data? (see question 2)
2) Do I need a microSD card in order to do so? I've seen several YT videos where they did a backup of the current system, but there still was a data wipe after flashing, so why even bother doing a backup at all?
3) My device is unlocked but with S-ON. Do I need S-OFF after all? As far as I can tell I don't need this, but is there any scenario I'd probably need it? (see question 4)
4) I'm thinking about getting a custom rom (Leedroid seems to be pretty decent). Can you recommend any of those custom roms and do I need S-OFF in order to flash them?
5) S-OFF + Locked or S-OFF + Unlocked? What's the difference? Any issues with the warranty?
6) If I do use a custom rom (e.g. Leedroid), is there also a way to update it to further versions without losing any data?
7) Where do I get the latest firmware for manually updating my device? I've already found a thread for it (http://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297), but my current firmware (1.90.401.5) or the one for the OTA update that already popped up (1.95.401.3) isn't listed over there. [EDIT: found my current firmware. Do I need to flash to it in order to do the OTA update?)
8) One last general question: as far as I understand it, unlocking your device is also the same as debranding it? I'm not sure if I'm mixing things up when reading about this. Is there any way to see if my device was branded before I did unlock/root it though?
I'm completely fine with losing my current data if that means that I can set it up my device in such a way that I can avoid any further data wipes when flasing/updating.
I'd be absolutely grateful if someone would answer those questions and help me to understand all of this.
Greetings,
makit_
1) Yes..you can apply the OTA manually, which won't flash the firmware image in the update but you can then find a no-wipe version of the new firmware on xda and flash it. Check out the faq in the twrp thread
2) for flashing firmware packages generally yes its better to have an SD card but I *think* it's possible to do it by issuing fastboot commands
3) s-off is needed if you wanna flash a new firmware I believe
4) you don't need S-off to flash a new ROM that's compatible with your firmware. Leedroid should work for you (this answer can be easily found by checking out each ROM thread and reading the Prerequisites section)
5) yes, most of the time you can "dirty flash" a new version of the same rom on top of the old one without wiping. If any issues pop up, or if it's a new base with large differences, then a wipe is needed. You can usually tell if a wipe is required by checking out what the developer says in the thread when a new updated is posted
6) I'm sure it's in a thread somewhere, you gotta search (I think sneakyghost's thread might have them)! And again you need S-off if you wanna flash firmwares
not an expert but here's my thoughts...
1) Is there any way to manually update your device with the newest OTA update WITHOUT losing any data? (see question 2) Yes. But if you want official update from HTC or your carrier via OTA you should be on stock. If you're on custom ROM, you can always dirty flash. But updating to a newer build, ROM dev sometimes recommend a full wipe
2) Do I need a microSD card in order to do so? I've seen several YT videos where they did a backup of the current system, but there still was a data wipe after flashing, so why even bother doing a backup at all?
SD card is not a requirement but is recommended since a full back-up size is ranging from 5gb-10gb maybe more depending in how many apps you installed. Backup is also recommended so you can always go back/restore your working ROM in case you messed up updating.
3) My device is unlocked but with S-ON. Do I need S-OFF after all? As far as I can tell I don't need this, but is there any scenario I'd probably need it? (see question 4). You need s-off mostly on updating your firmware or converting your device to other carrier or if you want to be unlocked. Right now you can flash any custom roms you like since we do not have a major update yet eg.1.x to 2.x. Once 2.x firmware is released, You can easily flash this firmware. But if you're S-ON, you can only update your firmware via official OTA from your carrier or if @Sneakyghost provide specific firmware for your carrier (matching cid and mid) in this thread else you're stock at 1.x firmware and ROMs that will only work on that specific firmware.
4) I'm thinking about getting a custom rom (Leedroid seems to be pretty decent). Can you recommend any of those custom roms and do I need S-OFF in order to flash them? See my answer in #3
5) S-OFF + Locked or S-OFF + Unlocked? What's the difference? Any issues with the warranty? If you're S-off you can always revert back to S-on and return to stock for warranty purposes.
6) If I do use a custom rom (e.g. Leedroid), is there also a way to update it to further versions without losing any data? Yes. see also #1
7) Where do I get the latest firmware for manually updating my device? I've already found a thread for it (http://forum.xda-developers.com/htc-...u-ota-t3359297), but my current firmware (1.90.401.5) or the one for the OTA update that already popped up (1.95.401.3) isn't listed over there. [EDIT: found my current firmware. Do I need to flash to it in order to do the OTA update?)See @Sneakyghost thread linked in #3. Firmware updating can be done via OTA or via fastboot(firmware zip can be downloaded) or full RUU (updating both ROM and firmware).
8) One last general question: as far as I understand it, unlocking your device is also the same as debranding it? I'm not sure if I'm mixing things up when reading about this. Is there any way to see if my device was branded before I did unlock/root it though? I think you meant sim unlocking here?? Generally, "unlocking" mostly mentioned in xda refers to bootloader
Tarima said:
1) Yes..you can apply the OTA manually, which won't flash the firmware image in the update but you can then find a no-wipe version of the new firmware on xda and flash it. Check out the faq in the twrp thread
2) for flashing firmware packages generally yes its better to have an SD card but I *think* it's possible to do it by issuing fastboot commands
3) s-off is needed if you wanna flash a new firmware I believe
4) you don't need S-off to flash a new ROM that's compatible with your firmware. Leedroid should work for you (this answer can be easily found by checking out each ROM thread and reading the Prerequisites section)
5) yes, most of the time you can "dirty flash" a new version of the same rom on top of the old one without wiping. If any issues pop up, or if it's a new base with large differences, then a wipe is needed. You can usually tell if a wipe is required by checking out what the developer says in the thread when a new updated is posted
6) I'm sure it's in a thread somewhere, you gotta search (I think sneakyghost's thread might have them)! And again you need S-off if you wanna flash firmwares
Click to expand...
Click to collapse
Thanks for your response! The numeration is wrong though as I edited my post while you were already typing your answers, but I figured it out nonetheless
–––––––––––––––––––––––
side_flip15 said:
1) Is there any way to manually update your device with the newest OTA update WITHOUT losing any data? (see question 2) Yes. But if you want official update from HTC or your carrier via OTA you should be on stock. If you're on custom ROM, you can always dirty flash. But updating to a newer build, ROM dev sometimes recommend a full wipe
Click to expand...
Click to collapse
When using a custom ROM, is it also possible to save your data so you can restore it after the full wipe?
side_flip15 said:
2) Do I need a microSD card in order to do so? I've seen several YT videos where they did a backup of the current system, but there still was a data wipe after flashing, so why even bother doing a backup at all?
SD card is not a requirement but is recommended since a full back-up size is ranging from 5gb-10gb maybe more depending in how many apps you installed. Backup is also recommended so you can always go back/restore your working ROM in case you messed up updating.
Click to expand...
Click to collapse
As far as I can tell, when doing a backup, you dont save your data 'partition' as it is encrypted anyways. Do I assume right that when doing a backup, I cannot restore my data I had before doing the flash?
side_flip15 said:
3) My device is unlocked but with S-ON. Do I need S-OFF after all? As far as I can tell I don't need this, but is there any scenario I'd probably need it? (see question 4). You need s-off mostly on updating your firmware or converting your device to other carrier or if you want to be unlocked. Right now you can flash any custom roms you like since we do not have a major update yet eg.1.x to 2.x. Once 2.x firmware is released, You can easily flash this firmware. But if you're S-ON, you can only update your firmware via official OTA from your carrier or if @Sneakyghost provide specific firmware for your carrier (matching cid and mid) in this thread else you're stock at 1.x firmware and ROMs that will only work on that specific firmware.
Click to expand...
Click to collapse
I've already seen the sunshine thread which is about turning S-OFF. While it is possible to go back to S-ON, it was recommended to let your device stay in S-OFF. Is there a high risk in bricking your device when trying to go back to S-ON?
side_flip15 said:
4) I'm thinking about getting a custom rom (Leedroid seems to be pretty decent). Can you recommend any of those custom roms and do I need S-OFF in order to flash them? See my answer in #3
5) S-OFF + Locked or S-OFF + Unlocked? What's the difference? Any issues with the warranty? If you're S-off you can always revert back to S-on and return to stock for warranty purposes.
Click to expand...
Click to collapse
As far as I know, doing so will void your warranty. Won't they notice if I just revert it myself and then send it in for warranty?
side_flip15 said:
7) Where do I get the latest firmware for manually updating my device? I've already found a thread for it (http://forum.xda-developers.com/htc-...u-ota-t3359297), but my current firmware (1.90.401.5) or the one for the OTA update that already popped up (1.95.401.3) isn't listed over there. [EDIT: found my current firmware. Do I need to flash to it in order to do the OTA update?)See @Sneakyghost thread linked in #3. Firmware updating can be done via OTA or via fastboot(firmware zip can be downloaded) or full RUU (updating both ROM and firmware).
Click to expand...
Click to collapse
Sorry this might be a rather dumb question, but I always thought ROM and firmware are the same thing. Or is it that updating my device via OTA is updating my firmware, while installing something like Leedroid is altering my ROM?
Again, thanks for all your responses in advance! You're helping me out a lot!
Greetings,
makit_
When using a custom ROM, is it also possible to save your data so you can restore it after the full wipe?
Click to expand...
Click to collapse
its possible but there's possibility that you might have some issue. Not sure though, never done that. I always use titanium backup to restore my apps.
As far as I can tell, when doing a backup, you dont save your data 'partition' as it is encrypted anyways. Do I assume right that when doing a backup, I cannot restore my data I had before doing the flash?
Click to expand...
Click to collapse
Data partition can be backed up actually and can be restored.
I've already seen the sunshine thread which is about turning S-OFF. While it is possible to go back to S-ON, it was recommended to let your device stay in S-OFF. Is there a high risk in bricking your device when trying to go back to S-ON?
Click to expand...
Click to collapse
Agree. there is no sense in reverting back to s-on unless if it's for warranty purposes.
Is there a high risk in bricking your device when trying to go back to S-ON?
Click to expand...
Click to collapse
I would say NO. I never used sunshine to s-off. I am using a hardware s-off and I did not experience any issue going back to s-on.
As far as I know, doing so will void your warranty. Won't they notice if I just revert it myself and then send it in for warranty?
Click to expand...
Click to collapse
On the device itself, I don't think so as long as you return it in full stock state. But if I remember correctly HTC dev requires you to provide your imei when requesting for unlock token bin file used to unlock bootloader, So if your unlock you device via HTC dev they have your imei in their record. They know that you already unlocked your device and warranty is void already.
Sorry this might be a rather dumb question, but I always thought ROM and firmware are the same thing
Click to expand...
Click to collapse
Take a look at this link. It provides you a complete explanation between ROM and Firmware.
Or is it that updating my device via OTA is updating my firmware, while installing something like Leedroid is altering my ROM?
Click to expand...
Click to collapse
Updating via official OTA usually updates ROM and firmware.
Installing a custom rom does not update firmware. Yes, it only alters ROM. But your ROM should always match your firmware at least the first digit of the firmware version (eg. 1.xx). For instance Android N (firmware veraion to be 2.x) arrives and LeeDroid updates its ROM to this, to be able to flash this latest custom rom, your firmware should also be at latest 2.x firmware else it will not boot. In this case, you need to update your firmware either via OTA, Fastboot or RUU.
makit_ said:
Thanks for your response! The numeration is wrong though as I edited my post while you were already typing your answers, but I figured it out nonetheless
–––––––––––––––––––––––
When using a custom ROM, is it also possible to save your data so you can restore it after the full wipe?
As far as I can tell, when doing a backup, you dont save your data 'partition' as it is encrypted anyways. Do I assume right that when doing a backup, I cannot restore my data I had before doing the flash?
I've already seen the sunshine thread which is about turning S-OFF. While it is possible to go back to S-ON, it was recommended to let your device stay in S-OFF. Is there a high risk in bricking your device when trying to go back to S-ON?
As far as I know, doing so will void your warranty. Won't they notice if I just revert it myself and then send it in for warranty?
Sorry this might be a rather dumb question, but I always thought ROM and firmware are the same thing. Or is it that updating my device via OTA is updating my firmware, while installing something like Leedroid is altering my ROM?
Again, thanks for all your responses in advance! You're helping me out a lot!
Greetings,
makit_
Click to expand...
Click to collapse
Thats a thing that iam also interested in. Iam also new to htc.
I think with firmware they mean bootloader. But nobody gave me a good answer till now...
side_flip15 said:
its possible but there's possibility that you might have some issue. Not sure though, never done that. I always use titanium backup to restore my apps.
Click to expand...
Click to collapse
I know that app by name, but never used it. Will take a look into it
side_flip15 said:
I would say NO. I never used sunshine to s-off. I am using a hardware s-off and I did not experience any issue going back to s-on.
Click to expand...
Click to collapse
Do you mean like this? (found in another forum):
1. First step is to unlock bootloader:
a) If bootloader unlock is turned off on your phone, you need to turn it on first:
- Boot to Android OS and perform initial setup if necessary
- Go to Menu -> Developer settings and tick "Enable OEM unlock"
Run XTC 2 Tool and open "Bootloader unlock" tab, follow instructions to unlock your bootloader.
2. Reboot to download mode, open "HTC 10" tab and install twrp recovery, you can get it here:
[...]
or
[...]
3. Boot to Bootloader, and press "Reboot to recovery".
4. In "HTC 10" tab press "Do S-OFF button".
5. Wait for the process to finish. Done.
Click to expand...
Click to collapse
side_flip15 said:
On the device itself, I don't think so as long as you return it in full stock state. But if I remember correctly HTC dev requires you to provide your imei when requesting for unlock token bin file used to unlock bootloader, So if your unlock you device via HTC dev they have your imei in their record. They know that you already unlocked your device and warranty is void already.
Click to expand...
Click to collapse
Yeah, I've done it this way. Sucks. But maybe it's not this bad at all. As I'm trying to be safe anyway, I probably only need to make use of the warranty if I'd accidentally drop my device. Those cases are still valid for warranty as far as I can tell (extract from the htcdev.com site: 'Please understand that you will not be able to return your device to the original state and going forward your device may not be held covered under the warranty for all claims resulting from the unlocking of the bootloader.'). Do you also know anything about this?
side_flip15 said:
Take a look at [... ]this link[/URL]. It provides you a complete explanation between ROM and Firmware.
Click to expand...
Click to collapse
Thanks, will look into it.
side_flip15 said:
Updating via official OTA usually updates ROM and firmware.
Installing a custom rom does not update firmware. Yes, it only alters ROM. But your ROM should always match your firmware at least the first digit of the firmware version (eg. 1.xx). For instance Android N (firmware veraion to be 2.x) arrives and LeeDroid updates its ROM to this, to be able to flash this latest custom rom, your firmware should also be at latest 2.x firmware else it will not boot. In this case, you need to update your firmware either via OTA, Fastboot or RUU.
Click to expand...
Click to collapse
Good to know. So in order to use the latest Leedroid and get rid of that OTA update notification, I should do the following:
1) Go back to stock (flash via RUU)
2) Hardware S-OFF (see above)
3) Flash latest OTA update
4) Custom Recovery again (TWRP) + Root (SuperSU)
5) Install latest Leedroid (have to read about it first, but afaik I have to install the zip of it via TWRP)
6) done
Is this correct or are there any mistakes?
And thanks a ton, you've helped me so much already!
Greetings,
makit_
makit_ said:
1) Is there any way to manually update your device with the newest OTA update WITHOUT losing any data? (see question 2)
Click to expand...
Click to collapse
If you are stock with only SU, then this is how I've gone about installing OTAs without wiping data:
1. Download ota (Settings>About>Software Updates) and move downloaded OTA from /data/data/com.htc.updater/files to sd card
2. In TWRP restore stock 'System Image' and 'Boot'
3. Reboot to Downloader
4. Flash stock recovery (fastboot.exe flash recovery xxx.img) --> can use current ota.zip > extract firmware.img from zip (if using 7zip -> rename .zip to .rar to extract fw)
5. Reboot to stock recovery
6. Install OTA in stock recovery
7. Reboot to Downloader
8. Reinstall TWRP (fastboot.exe flash recovery twrpxxx.img)
9. Backup stock 'System Image' and 'Boot'
10. In TWRP reflash SuperSu/Xposed/etc
yankee1390 said:
If you are stock with only SU, then this is how I've gone about installing OTAs without wiping data:
1. Download ota (Settings>About>Software Updates) and move downloaded OTA from /data/data/com.htc.updater/files to sd card
2. In TWRP restore stock 'System Image' and 'Boot'
3. Reboot to Downloader
4. Flash stock recovery (fastboot.exe flash recovery xxx.img) --> can use current ota.zip > extract firmware.img from zip (if using 7zip -> rename .zip to .rar to extract fw)
5. Reboot to stock recovery
6. Install OTA in stock recovery
7. Reboot to Downloader
8. Reinstall TWRP (fastboot.exe flash recovery twrpxxx.img)
9. Backup stock 'System Image' and 'Boot'
10. In TWRP reflash SuperSu/Xposed/etc
Click to expand...
Click to collapse
This sounds very convenient and not far too different than what I was used to with my N5. Guess I'll give it a go! Already found a way to disable the HTC lock screen http://forum.xda-developers.com/htc-10/help/disable-htc-10-lockscreen-t3418108 (which is annoying especially when using a different launcher as the lock screen background is still the one from the stock launcher). Only thing bugging me now is that BoomSound notification, but I guess I can live with that
makit_ said:
This sounds very convenient and not far too different than what I was used to with my N5. Guess I'll give it a go! Already found a way to disable the HTC lock screen http://forum.xda-developers.com/htc-10/help/disable-htc-10-lockscreen-t3418108 (which is annoying especially when using a different launcher as the lock screen background is still the one from the stock launcher). Only thing bugging me now is that BoomSound notification, but I guess I can live with that
Click to expand...
Click to collapse
may look at installing XPosed as they have a module "XNotifications" that lets you hide any type of notification
yankee1390 said:
may look at installing XPosed as they have a module "XNotifications" that lets you hide any type of notification
Click to expand...
Click to collapse
Will also look into this. I've used Xposed on my N5 but wasn't sure the HTC 10 is already fully supported (have read something about that, but those threads were already 3-4 months old). Thanks!
So I'm trying to do the step-by-step instructions from yankee1390 because I guess that's the easiest way for me to handle things. Now I've already got my first (and hopefully only) issue with it: I did no backup when I first installed TWRP and before I've rooted my device. So in order to accomplisch step 2) (restore stock system image + boot in TWRP), can I use the files from the RUU provided here -> http://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297?
I've found the one matching my current firmware (1.90.401.5), so is it ok if I use those for step 2?
And by the way, I guess I have to do a backup after every OTA update (and before rooting) so I always have the right files for restoring, huh?
Greetings,
makit_
edit: may have found the solution to it Will update once I'm done.
makit_ said:
So I'm trying to do the step-by-step instructions from yankee1390 because I guess that's the easiest way for me to handle things. Now I've already got my first (and hopefully only) issue with it: I did no backup when I first installed TWRP and before I've rooted my device. So in order to accomplisch step 2) (restore stock system image + boot in TWRP), can I use the files from the RUU provided here -> http://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297?
I've found the one matching my current firmware (1.90.401.5), so is it ok if I use those for step 2?
And by the way, I guess I have to do a backup after every OTA update (and before rooting) so I always have the right files for restoring, huh?
Greetings,
makit_
edit: may have found the solution to it Will update once I'm done.
Click to expand...
Click to collapse
Link didn't work on my app so can't confirm if that will work. However any TWRP stock backup that matches your current version should work. RUUs will wipe your data if you use them.
Definitely good idea to backup after each ota before modifying system partition to make next ota easier. Though usually someone on here can provide a backup if you don't get one.
I know that app by name, but never used it. Will take a look into it
Click to expand...
Click to collapse
i suggest you purchase a pro version. It's a really a must-have app
Do you mean like this? (found in another forum):
Click to expand...
Click to collapse
Yes. This is the process how to s-off using xtc2clip - A very handy tool that works almost every HTC devices. Support is great too.
Yeah, I've done it this way. Sucks. But maybe it's not this bad at all. As I'm trying to be safe anyway, I probably only need to make use of the warranty if I'd accidentally drop my device. Those cases are still valid for warranty as far as I can tell (extract from the htcdev.com site: 'Please understand that you will not be able to return your device to the original state and going forward your device may not be held covered under the warranty for all claims resulting from the unlocking of the bootloader.'). Do you also know anything about this?
Click to expand...
Click to collapse
Yeah. They might not know we can s-off. lol
Good to know. So in order to use the latest Leedroid and get rid of that OTA update notification
Click to expand...
Click to collapse
If you mean OTA notification from HTC, most of the custom ROMs already disabled that, I believe. And they provide you with their own OTA update (Not all, some do. Like ViperRom)
I should do the following:
1) Go back to stock (flash via RUU)
2) Hardware S-OFF (see above)
3) Flash latest OTA update
4) Custom Recovery again (TWRP) + Root (SuperSU)
5) Install latest Leedroid (have to read about it first, but afaik I have to install the zip of it via TWRP)
6) done
Click to expand...
Click to collapse
This is correct but there is an easier way after you s-offed.
1. Download the latest firmware.zip, if you're not on the latest yet. Flash it via fastboot commands in download.
mode. Instruction is available in the link I provided earlier in @Sneakyghost firmware thread.
2. Flash TWRP.
3. Download your desired custom ROM (LeeDroid). This is in .zip file.
4. Reboot to recovery, wipe data/factory reset then flash the LeeDroid.zip. Just follow the instructions in aroma.
by the way, if you'll flash firmware.zip make you select the matching CID and MID of your device. You might end up bricking your device flashing a wrong firmware. If you can provide me your CID and MID, I'll link you to the correct firmware for your device. To do so, reboot to bootloader and type the following commands in cmd, remove your IMEI and SN and post the result here.
And thanks a ton, you've helped me so much already!
Click to expand...
Click to collapse
You are welcome.
---------- Post added at 02:22 AM ---------- Previous post was at 01:44 AM ----------
I never done updating software via HTC official update. I don't know but for me I don't see any reason sticking to stock ROM. There are a lot of custom ROMs out there tweaked for better performance and battery life. They are also always updated to latest build.
side_flip15 said:
i suggest you purchase a pro version. It's a really a must-have app
Yes. This is the process how to s-off using xtc2clip - A very handy tool that works almost every HTC devices. Support is great too.
Yeah. They might not know we can s-off. lol
If you mean OTA notification from HTC, most of the custom ROMs already disabled that, I believe. And they provide you with their own OTA update (Not all, some do. Like ViperRom)
This is correct but there is an easier way after you s-offed.
1. Download the latest firmware.zip, if you're not on the latest yet. Flash it via fastboot commands in download.
mode. Instruction is available in the link I provided earlier in @Sneakyghost firmware thread.
2. Flash TWRP.
3. Download your desired custom ROM (LeeDroid). This is in .zip file.
4. Reboot to recovery, wipe data/factory reset then flash the LeeDroid.zip. Just follow the instructions in aroma.
by the way, if you'll flash firmware.zip make you select the matching CID and MID of your device. You might end up bricking your device flashing a wrong firmware. If you can provide me your CID and MID, I'll link you to the correct firmware for your device. To do so, reboot to bootloader and type the following commands in cmd, remove your IMEI and SN and post the result here.
You are welcome.
Click to expand...
Click to collapse
Thanks for all your help. I will look into it when I need it. For now I'll stick with stock (see below)
side_flip15 said:
I never done updating software via HTC official update. I don't know but for me I don't see any reason sticking to stock ROM. There are a lot of custom ROMs out there tweaked for better performance and battery life. They are also always updated to latest build.
Click to expand...
Click to collapse
I love using stock android, that's why I also loved using my Nexus 5. I used CyanogenMod with another device many years ago but I am willing to use a custom ROM for my HTC 10, but only after I already know how it feels with stock ROM. So I will stick with it for several weeks and see how it feels, and when I'm farmiliar with it, I will switch to a custom ROM So thanks a lot, you've given me a lot of information I will still need for further experimenting with my phone!
Piggybacking on this thread because my new-to-me HTC 10 is coming in the mail and I'm planning what to do with it. It is already bootloader unlocked and s-off. I would like to use Leedroid, ElementalX, Magisk, and Xposed.
I've never had an HTC device so I just want to make sure I'm doing this right. So I think this is what I need to do:
1) Flash TWRP via ADB
2) Flash SuperSU in TWRP
3) Flash everything else...Leedroid, ElementX, Xposed, Magisk. In that order? Can I flash them all at once (just keep adding zips to the TWRP list) or do I have to boot between each one?
Xposed is more important to me than a custom ROM, because I need to use Amplify and PowerNap to improve my battery life. Would it be better just to stay on stock instead of Leedroid?
@jrbmed08
TWRP is flashed via fastboot, not ADB.
No need to flash SuperSU via recovery since LeeDroid has root already.
You can flash everything at once.
Sent from my HTC 10
I love using stock android, that's why I also loved using my Nexus 5. I used CyanogenMod with another device many years ago but I am willing to use a custom ROM for my HTC 10, but only after I already know how it feels with stock ROM. So I will stick with it for several weeks and see how it feels, and when I'm farmiliar with it, I will switch to a custom ROM So thanks a lot, you've given me a lot of information I will still need for further experimenting with my phone!
Click to expand...
Click to collapse
When I said stock ROM, i meant stock HTC ROM and it's not stock Android. It's a skinned android called HTC sense. . If you want a stock android to run in your HTC 10 you can flash a AOSP based custom ROM.
Magnum_Enforcer said:
@jrbmed08
TWRP is flashed via fastboot, not ADB.
No need to flash SuperSU via recovery since LeeDroid has root already.
You can flash everything at once.
Sent from my HTC 10
Click to expand...
Click to collapse
Ah yeah, sorry, fastboot is what I meant. Thank you! I haven't had an unlocked bootloader in quite a while (was using TWRP and Sony stock-based ROMs on a locked Z3c), so it will be interesting to flash kernels and such again.
d_Schizzo said:
Thats a thing that iam also interested in. Iam also new to htc.
I think with firmware they mean bootloader. But nobody gave me a good answer till now...
Click to expand...
Click to collapse
not only bootloader, it contains everything. radio.img and any other thing. "low-lewel-stuff", kernel etc, recovery (if stock signed firmware, which is not modded/removed). there are many important things inside.
but firmware is meant for every device the same. it contains everything so that this device can run/work properly.
So some might remember me awhile back ago... https://forum.xda-developers.com/pixel-xl/help/unlocking-verizon-bootloader-t3557290
I got tired of not having a unlocked/rooted device since I just dropped so much money on a new phone for my 27th bday sooo I took it back to verizon and swapped it for a new one. I was having the battery problems where my phone would hit 30-15% and just die on me OR the screen would die on me but the phone stayed on no problems.. I'd be in a phone call and the screen would shut off and I couldnt get it to turn back on without plugging in a charger or battery bank.
I've got my new phone now and everything is working flawlessly.. It's unlocked, has twrp installed and rooted just fine..
Now I remember seeing something about once I unlock/root the device my OTA becomes disabled so where do I get the OTA update for the device so I can go to 7.1.1 or later this month 7.1.2? I found this https://developers.google.com/android/ota and I see the 7.1.1 update but it's 800mbs which means I'm guessing if I flash that i'd be completely reinstalling a new copy of android and lose all of my data and have to go through setting up my phone again etc..
How do I just get the update itself and flash that? When I use the OTA on my Pixel XL the download is only like 200MB it doesn't install though just says it failed. Still new to all of this but I'm learning and how else am I gonna learn if I don't ask questions
a point in the right direction would be great.
https://developers.google.com/android/images
Sent from my Pixel XL using Tapatalk
---------- Post added at 07:23 PM ---------- Previous post was at 07:22 PM ----------
Point point
Sent from my Pixel XL using Tapatalk
wyrdtrtle said:
https://developers.google.com/android/images
Sent from my Pixel XL using Tapatalk
---------- Post added at 07:23 PM ---------- Previous post was at 07:22 PM ----------
Point point
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
These images are even bigger than the ones I linked.. the 7.1.1 update is 1.8GB? the file I'm downloading via my Phone is 282.1 MB?
[QUOTE=
If you go to that link in the post above you can download the newest firmware. Unzip it and open the bat file with note editor or something like that and remove the -w and it will update without losing your data.
Dimmizer said:
These images are even bigger than the ones I linked.. the 7.1.1 update is 1.8GB? the file I'm downloading via my Phone is 282.1 MB?
Click to expand...
Click to collapse
You use your original link and sideload it with TWRP.
TonikJDK said:
You use your original link and sideload it with TWRP.
Click to expand...
Click to collapse
Thanks
Upper left corner Link to OTA's smaller
Sent from my Pixel XL using Tapatalk
Now one last question...
From official TWRP webpage it says
Never try official ota updates using TWRP. Its not recommended. should I wait to update to 7.1.1 or flash? any pros/cons?
Thanks for all the help and ansrewing of questions so far
Edit: should I unroot and try to OTA again and if it works just reroot the device?
Dimmizer said:
Now one last question...
From official TWRP webpage it says
Never try official ota updates using TWRP. Its not recommended. should I wait to update to 7.1.1 or flash? any pros/cons?
Thanks for all the help and ansrewing of questions so far
Edit: should I unroot and try to OTA again and if it works just reroot the device?
Click to expand...
Click to collapse
You are unlocked, so the only danger here is that you bootloop and lose your data. Make sure your data is backed up and sideload the ota with the directions on googles ota page and re install TWRP.
That's the easiest way and pretty darn safe. I dont recall seeing anyone having trouble with that.
Looking at unrooting my device so I can do OTA updates via the phone and then I'll just reroot again but during the unroot process it says
Attempt to restore stock boot image? This is require for OTA's to succeed. If you manually decrypted your device, note that this might prevent my device from booting.
How do I know if I manually decrypted it? I used depixel8 to unlock bootloader and used SuperSU to root so am I safe to proceed or should I not attempt to restore a stock boot image?
Dimmizer said:
Looking at unrooting my device so I can do OTA updates via the phone and then I'll just reroot again but during the unroot process it says
Attempt to restore stock boot image? This is require for OTA's to succeed. If you manually decrypted your device, note that this might prevent my device from booting.
How do I know if I manually decrypted it? I used depixel8 to unlock bootloader and used SuperSU to root so am I safe to proceed or should I not attempt to restore a stock boot image?
Click to expand...
Click to collapse
You did not decrypt it. That isn't currently doable.
TonikJDK said:
You are unlocked, so the only danger here is that you bootloop and lose your data. Make sure your data is backed up and sideload the ota with the directions on googles ota page and re install TWRP.
That's the easiest way and pretty darn safe. I dont recall seeing anyone having trouble with that.
Click to expand...
Click to collapse
Doing what you said now
[
Dimmizer said:
Looking at unrooting my device so I can do OTA updates via the phone and then I'll just reroot again but during the unroot process it says
Attempt to restore stock boot image? This is require for OTA's to succeed. If you manually decrypted your device, note that this might prevent my device from booting.
How do I know if I manually decrypted it? I used depixel8 to unlock bootloader and used SuperSU to root so am I safe to proceed or should I not attempt to restore a stock boot image?
Click to expand...
Click to collapse
I wouldn't unroot with that, doesn't work all the time just flash the newest firmware and you will be unrooted. You are going to have a bad time if you do.
mk so another question..
https://twrp.me/faq/officialota.html
twrp says NOT to flash ota with twrp? so should I flash back to a stock recovery or just use twrp? if so how? lol
https://developers.google.com/android/ota
The google site explains what to do but I'm assuming it's explaining things as if I had a stock recovery and I don't..
lol... I know this isn't that hard and I'm just being paranoid cause I don't wanna brick my phone etc. but also it's like ALLLL this work just so I can flash new android update to my phone... and this whole thing seems to be taking longer than it really needs to.
Dimmizer said:
lol... I know this isn't that hard and I'm just being paranoid cause I don't wanna brick my phone etc. but also it's like ALLLL this work just so I can flash new android update to my phone... and this whole thing seems to be taking longer than it really needs to.
Click to expand...
Click to collapse
Hit the link below, it explains it well and you will see it worked for others.
https://forum.xda-developers.com/pixel-xl/help/rooted-twrp-recovery-how-update-ota-t3524279
If you ever bootloop don't freak, its an unlocked google phone. Flashing back to stock is easy.
The only thing that was in question was the bootloader unlock, once its unlocked your safe. It wont relock unless you lock it. But, if you do lock it, its locked for good. Afaika
Sent from my Pixel XL using Tapatalk
Dimmizer said:
lol... I know this isn't that hard and I'm just being paranoid cause I don't wanna brick my phone etc. but also it's like ALLLL this work just so I can flash new android update to my phone... and this whole thing seems to be taking longer than it really needs to.
Click to expand...
Click to collapse
Dimmizer said:
mk so another question..
https://twrp.me/faq/officialota.html
twrp says NOT to flash ota with twrp? so should I flash back to a stock recovery or just use twrp? if so how? lol
https://developers.google.com/android/ota
The google site explains what to do but I'm assuming it's explaining things as if I had a stock recovery and I don't..
Click to expand...
Click to collapse
I flashed OTA with twrp on my buddy's pixel for the Feb update worked just fine. Just make sure it's the OTA and not the factory image. But the best way would be using fastboot
Most anything you flash (stock updates, custom roms, will overwrite recovery. But not a problem, you just re-boot it to flash it, or just boot it and flash su and reboot device.
Sent from my Pixel XL using Tapatalk
awesome , thanks again everyone for your time and the help, very much greatly appreciated.