Get your lollipop here. Below is the full OTA from 4.4.4/KTU84P/N910AUCU1ANIE to 5.0.1/LRX22C/N910AUCU1COC4.
I have also include an flashable update.zip with the ota. Please read info below.
OTA/cfg only:
https://mega.co.nz/#!mZB3QBZR!tsWqPGQynF_AgWxsO8xZJy5u4pqfb8HKv5jV_SonVI8
For now this zip is useless until have root. It's here to be available when we are able to use it.
Update.zip: Custom recovery only: {{{{WARNING UNTESTED}}}} Although it's most likely perfect it's untested. See update.zip info below.
https://mega.co.nz/#!jQwxkaIb!UBrf26IRhdSgGnk935qE4GejP-wZG7HR4uZOIb5V3cA
OC4 odin Tar newest:
COMING SOON Waiting for Kies to update version
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Update.zip INFO
In the past pre-rooting the zips was causing WiFi in to fork,so the zip is not rooted.
The update.zip and the actual cfg are almost identical with a few exceptions. They update identically using the same method.
Both use a series of update patches to inject new code in existing apk's some do get fully replaced but very few. So for this reason rooting using them needs to be done in a specific manner. You can thank Samsung/KNOX and SELinux for that.
How to upgrade with update.zip and keep root
It's best to be 100%stock before updating.
Remove SU app from system,do not remove the>>>>>>binary<<<<<<
Boot recovery,flash update zip,reboot
Install SU zip after rom fully boots and profit.
You...are...awesome!!!
Update.zip added.
what is this? I thought we only have a temp root
darkbots said:
Update.zip added.
Click to expand...
Click to collapse
Hi bro! I changed the name of .cfg and on recovery stock says failed to verify signature...
Deleted
darkbots said:
Get your lollipop here. Below is the full ota from 4.4.4/KTU84P/N910AUCU1ANIE to 5.0.1/LRX22C/N910AUCU1COC4.
I have also include an flashable update.zip with the ota. Please read info below.
OTA/cfg only:
https://mega.co.nz/#!mZB3QBZR!tsWqPGQynF_AgWxsO8xZJy5u4pqfb8HKv5jV_SonVI8
Update.zip: Custom recovery only: {{{{WARNING UNTESTED}}}} Although it's most likely perfect it's untested. See update.zip info below.
https://mega.co.nz/#!jQwxkaIb!UBrf26IRhdSgGnk935qE4GejP-wZG7HR4uZOIb5V3cA
OC4 odin Tar newest:
COMING SOON Waiting for Kies to update version
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Update.zip INFO
In the past pre-rooting the zips was causing WiFi in to fork,so the zip is not rooted.
The update.zip and the actual cfg are almost identical with a few exceptions. They update identically using the same method.
Both use a series of update patches to inject new code in existing apk's some do get fully replaced but very few. So for this reason rooting using them needs to be done in a specific manner. You can thank Samsung/KNOX and SELinux for that.
How to upgrade with update.zip and keep root
It's best to be 100%stock before updating.
Remove SU app from system,do not remove the>>>>>>binary<<<<<<
Boot recovery,flash update zip,reboot
Install SU zip after rom fully boots and profit.
Click to expand...
Click to collapse
Now obviously anyone on these forums knows the deal here, if it's flashable it's risky, but this raises some flags that need addressed.
This is for the AT&T yes? If I'm not mistaken, this device has a locked bootloader, so then it goes without saying that your custom recovery flash only is untested. So is the expectation that users here are supposed to test it?
This is only the stock update put in a zip, then I cleaned some of the updater. This way if your on stock kitkat with custom recovery you can take the ota. There's zero risk here other than what Samsung messed up. I assumed it would be obvious we can use them yet because of not having root. I've done this a lot for several devices it's crazy easy to do,and you only need to change its zip and clean the updater.
rondoo said:
Hi bro! I changed the name of .cfg and on recovery stock says failed to verify signature...
Click to expand...
Click to collapse
You can't change the name extention or open the cfg .Put it on a sd, use stock recovery sd install option.
darkbots said:
You can't change the name extention or open the cfg .Put it on a sd, use stock recovery sd install option.
Click to expand...
Click to collapse
Did it and...
failed to verify whole-file signature
signature verification failed
download again you have a corrupted file
having same problem here.
failed to verify whole-file signature
signature verification failed.
I just bought note 4. This is AT&T model firmware version N910AUCU1BNK3. This is unlocked phone. I am using this phone in Pakistan. Currently it is with Kitkat. Once I am trying to update to lollipop through OTA it shows its is lastest firmware but I know Lollipop already released. Please help me how to update my phone ? I want my phone keep unlock as I am using in Pakistan.
waqas.ahmad said:
I just bought note 4. This is AT&T model firmware version N910AUCU1BNK3. This is unlocked phone. I am using this phone in Pakistan. Currently it is with Kitkat. Once I am trying to update to lollipop through OTA it shows its is lastest firmware but I know Lollipop already released. Please help me how to update my phone ? I want my phone keep unlock as I am using in Pakistan.
Click to expand...
Click to collapse
you can not update at&t version outside of US. I struggled a lot and finally gave up and installed lollipop (5.0.1) manually using files shared by the guys from here.
annttiigs said:
you can not update at&t version outside of US. I struggled a lot and finally gave up and installed lollipop (5.0.1) manually using files shared by the guys from here.
Click to expand...
Click to collapse
If I update manually, will my phone SIM Locked? Currently it is unlocked.
What about Knox? will is break?
Can you share me the firmware link which I exactly download and install in my phone?
waqas.ahmad said:
If I update manually, will my phone SIM Locked? Currently it is unlocked.
What about Knox? will is break?
Can you share me the firmware link which I exactly download and install in my phone?
Click to expand...
Click to collapse
I have used this one and and no issue:
http://forum.xda-developers.com/note-4-att/general/to-stock-files-latestcoc4-build-t3107391
but all is on your own risk.
annttiigs said:
I have used this one and and no issue:
http://forum.xda-developers.com/note-4-att/general/to-stock-files-latestcoc4-build-t3107391
but all is on your own risk.
Click to expand...
Click to collapse
I have downloaded the firmware from the link you sent me.
You tried to install it on unlocked phone ? Firmware Version N910AUCU1BNK3?
Do I need to load all files or just AP is ok ?
waqas.ahmad said:
I have downloaded the firmware from the link you sent me.
You tried to install it on unlocked phone ? Firmware Version N910AUCU1BNK3?
Do I need to load all files or just AP is ok ?
Click to expand...
Click to collapse
Plase follow the discussion there. Those all were my questions as well. You need to put each file in its location in Odin means you will use all files. My phone was unlocked and I dont remember my fw version. Please read the discussion there.
hi this link for CFG is dead , can you reup link ?>
+1 Please re-upload
A few months ago I rooted my phone (z00ad) so I could remove some bloatware that came with it.
I used titanium back-up to delete those apps, and of course I first made an back-up of an app before i deleted it.
But I was stupid enough to accidently delete DMClient (the system update app).
So as soon as I discovered that I was very happy with my back-up but everytime I try to re-install it it says app not installed.
I also tried to use a third party installer called system app installer but it gives me an error that says: Mounting error, Cannot mount system partition as Read/Write.
So what should I do?
Can it be fixed, or do I need to flash a complete new rom?
I still need to get very nice updates that I would really like to have so I would be really happy if someone could help me.
stenpep said:
A few months ago I rooted my phone (z00ad) so I could remove some bloatware that came with it.
I used titanium back-up to delete those apps, and of course I first made an back-up of an app before i deleted it.
But I was stupid enough to accidently delete DMClient (the system update app).
So as soon as I discovered that I was very happy with my back-up but everytime I try to re-install it it says app not installed.
I also tried to use a third party installer called system app installer but it gives me an error that says: Mounting error, Cannot mount system partition as Read/Write.
So what should I do?
Can it be fixed, or do I need to flash a complete new rom?
I still need to get very nice updates that I would really like to have so I would be really happy if someone could help me.
Click to expand...
Click to collapse
Yeah TI can't restore apps in the x86 way asus put them there. so i would recommend to freeze the apps instead of uninstalling them. You have to flash the pre-root firmware of the version you are on first, then you can update without a problem.
cmendonc2 said:
Yeah TI can't restore apps in the x86 way asus put them there. so i would recommend to freeze the apps instead of uninstalling them. You have to flash the pre-root firmware of the version you are on first, then you can update without a problem.
Click to expand...
Click to collapse
Thanks kor your help,
But I would like to get a bit more help because I am new in flashing and rooting.
Few questions:
Where do I get the rom?
How do I flash it?
Extra details:
Model: ASUS_Z00AD
I am running WW-ASUS_Z00A-2.13.40.13
stenpep said:
Thanks kor your help,
But I would like to get a bit more help because I am new in flashing and rooting.
Few questions:
Where do I get the rom?
How do I flash it?
Extra details:
Model: ASUS_Z00AD
I am running WW-ASUS_Z00A-2.13.40.13
Click to expand...
Click to collapse
You can look in the device index: http://forum.xda-developers.com/zenfone2/general/index-asus-zenfone-2-wip-t3149748. The pre-root firmware is in the firmware post. Instructions for updating OTA without bootloop is in the guides post.
cmendonc2 said:
You can look in the device index: http://forum.xda-developers.com/zenfone2/general/index-asus-zenfone-2-wip-t3149748. The pre-root firmware is in the firmware post. Instructions for updating OTA without bootloop is in the guides post.
Click to expand...
Click to collapse
so this is where i need to be? http://forum.xda-developers.com/showpost.php?p=61687943&postcount=3
and then scroll down to pre-rooted firmware, so i would get a site called mega.
so I need to flash the version I am running right now?
and these are the instructions : http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835 ?
thanks!
stenpep said:
so this is where i need to be? http://forum.xda-developers.com/showpost.php?p=61687943&postcount=3
and then scroll down to pre-rooted firmware, so i would get a site called mega.
so I need to flash the version I am running right now?
and these are the instructions : http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835 ?
thanks!
Click to expand...
Click to collapse
Yes, and be sure that you are downloading and installing the correct versions for your phone (Z008 vs Z00A) and flash the software versions that you currently have, as indicated in the guide.
Hi Guys,
I feel completely lost with all the guides to flash my ZE551ML.
- Root (I counted 3 ways to it)
- Unlock the bootloader
- Install recovery (So much alternatives)
- And Finally the CM13 Rom
In some guides, there are files from April or June 2015.
I already flashed Android Devices but with the Zenfone 2 I feel anxious about all the doc around.
The way you root and the recovery you install will affecte the CM13
Is there a clear up to date step by step that tell what to do not options I can have?
Thanks
Step 1. Unlock the bootloader.
Step 2. Flash the TWRP recovery 2.8.7.0
Step 3. Download and insert CM 13 and gapps pico 6.0 x86 in your internal/sd card.
Step 4. Boot into recovery using Vol buttons + Power.
Step 5. Wipe data, cache, dalvik cache, system.
Step 6. Flash CM 13, and then gapps from your internal/sd card.
Step 7. Reboot system.
Sayan44 said:
Step 1. Unlock the bootloader.
.....
....
....
.
Click to expand...
Click to collapse
Thanks man,
It is more about the files to use :
To Unlock the bootloader (img file, driver and adb tools)
I see that from your steps there no need to root?
I downlaoded those files : from mega /#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw!pkVXnYLK (And they are to root only if I am not wrong)
bobrah said:
Thanks man,
It is more about the files to use :
To Unlock the bootloader (img file, driver and adb tools)
I see that from your steps there no need to root?
Click to expand...
Click to collapse
What is your device? ZE 550 ML or 551 ML. There are official apks available on asus website for both models. Download them and install them.
Bad idea using the official unlocker it is still giving errors, I would do more research here before using the official unlocker
Sent from my Nexus 7 using Tapatalk
jimchee said:
Bad idea using the official unlocker it is still giving errors, I would do more research here before using the official unlocker
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I Have the 551 ML Variant.
Indeed, I read here in one Thread to avoid official unlocker and this is what is causing headaches. To Many info so at the end you learn nothing.
So what do you recommend as method and with what files?
Thanks.
To unlock the bootloader through the unofficial way, your firmware has to be 2.19.40.20. If your firmware is newer than this, then you'll need to downgrade. If not, you just need to upgrade.
1. Downgrade to 2.19.40.20: http://www.asus.com/zentalk/forum.php?mod=viewthread&tid=12528 (before downloading the firmware, check if your device is CN or WW)
You'll need to downgrade both the firmware and recovery to the same version, which is 2.19.40.20.
2. Root: http://forum.xda-developers.com/zenfone2/general/zenfone-2-root-easy-t3114003
3. Unlock bootloader: http://forum.xda-developers.com/zenfone2/general/congrats-to-bootlocker-unlocked-t3138547
4. Flash custom recovery (I chose TWRP): https://twrp.me/devices/asuszenfone2.html
Download the twrp-2.8.7.2-Z00A.img image and follow the steps under "Fastboot Install Method (No Root Required)" to flash it.
This is how I unlocked the bootloader and flashed the TWRP custom recovery on my Zenfone 2. If you follow each step as described, you'll be fine. I don't know if there's already another easier way to do these things, but this is what I followed and worked flawlessy.
Also, there is a tool called WinDroid that promisses to do all this a lot easier, BUT I haven't tested it myself, so I can't say if it really works or not: http://forum.xda-developers.com/zen...l-windroid-universal-android-toolkit-t3206907
XeidiDent said:
To unlock the bootl.....
Click to expand...
Click to collapse
Thanks buddy,
You saved my asses because I was going to start the install and I have WW_2.20.40.156
I prefer to wait the official cyanogen release or tools working with my actual rom version.
Too Risky and Too many factors
Thanks again
The other option is to use windroid tool which has worked well to unlock the bootloader and you can also install twrp with it
Sent from my Nexus 7 using Tapatalk
hello,
"Unlock Device App: Unlock boot loader
Notice:
1. Update your software image to V2.20.40.139 or latest version"
I have rooted my device, then i used the unlock app by asus, and finally i flash twrp with the twrp manager app and all is good.
Sorry for my bad english
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.
Hi everyone, this is my first post
This winter I had decided to install the GCam on my Mi A2 lite, so I followed a guide (I'm not able to mod any phone) I managed to install the cam. To install that I obv needed to root my phone and indeed on Root Checker that was rooted. Some months later, the phone was automaticatly updated and after that I don't know how that lost his rooting and the possibilty to use Gcam (and other apps). I didn't want to do all the process again so I let that go.
Now I'd like to install the Pixel Experience ROM on my Xiaomi tho, but I read that I need to have root permission and the bootloader unlocked. My bootloader is already uncloked, because in developer's option, under "Unlock OEM" is written. "the bootloader's already unlocked."), but I have no root permission. I don't know what to do, because as I said I'm totally ignorant.
Can I install a custom recovery without root permission? How can I install the Pixel Rom? I need to root again my phone?
Thank you all for you help!
spaga97 said:
Hi everyone, this is my first post
This winter I had decided to install the GCam on my Mi A2 lite, so I followed a guide (I'm not able to mod any phone) I managed to install the cam. To install that I obv needed to root my phone and indeed on Root Checker that was rooted. Some months later, the phone was automaticatly updated and after that I don't know how that lost his rooting and the possibilty to use Gcam (and other apps). I didn't want to do all the process again so I let that go.
Now I'd like to install the Pixel Experience ROM on my Xiaomi tho, but I read that I need to have root permission and the bootloader unlocked. My bootloader is already uncloked, because in developer's option, under "Unlock OEM" is written. "the bootloader's already unlocked."), but I have no root permission. I don't know what to do, because as I said I'm totally ignorant.
Can I install a custom recovery without root permission? How can I install the Pixel Rom? I need to root again my phone?
Thank you all for you help!
Click to expand...
Click to collapse
You need for sure an unlocked bootloader but regarding root although you don´t need it to flash a custom recovery nor a custom rom probably is better that you have it so you might need to do other things like install mods that need root.
Just flashing the Magisk you´ll recover the lost root status again but if you don´t have recovery now just boot on it through fastboot and then flash it over your actual rom or if you want the Pixel rom just follow the tutorial posted in the thread.
SubwayChamp said:
You need for sure an unlocked bootloader but regarding root although you don´t need it to flash a custom recovery nor a custom rom probably is better that you have it so you might need to do other things like install mods that need root.
Just flashing the Magisk you´ll recover the lost root status again but if you don´t have recovery now just boot on it through fastboot and then flash it over your actual rom or if you want the Pixel rom just follow the tutorial posted in the thread.
Click to expand...
Click to collapse
Do I need a TWRP Recovery tho? Because I read on some guides that's a requisite to instal Pixel Rom.
And please, can you link me the tutorial you mean? Because I can't find out that.
spaga97 said:
Do I need a TWRP Recovery tho? Because I read on some guides that's a requisite to instal Pixel Rom.
And please, can you link me the tutorial you mean? Because I can't find out that.
Click to expand...
Click to collapse
Yes, you need a custom recovery like TWRP and regarding tutorial there is a how-to-install method on every custom rom and also in the thread of a Pixel rom https://forum.xda-developers.com/mi-a2-lite/development/rom-pixel-experience-t3911489 they´re just some few steps
SubwayChamp said:
Yes, you need a custom recovery like TWRP and regarding tutorial there is a how-to-install method on every custom rom and also in the thread of a Pixel rom https://forum.xda-developers.com/mi-a2-lite/development/rom-pixel-experience-t3911489 they´re just some few steps
Click to expand...
Click to collapse
To be honest I can't find where's the tutorial into that thread :crying:
Anyway I've just thought that maybe I've already have a TWRP. I did a lot of operations when I installed the GCam, so maybe I also did that. Is there a way to find out if I already have it?
spaga97 said:
To be honest I can't find where's the tutorial into that thread :crying:
Anyway I've just thought that maybe I've already have a TWRP. I did a lot of operations when I installed the GCam, so maybe I also did that. Is there a way to find out if I already have it?
Click to expand...
Click to collapse
Oh sorry since I don´t use PE rom nevermind there is not a tutorial there but you will find one here https://forum.xda-developers.com/mi...0-ressurection-remix-os-xiaomi-mi-a2-t3954197 it´s the same process (more or less) for any custom rom.
If you are on a custom rom just booting using advanced power reboot you can go to recovery to see if it still stays there, also you can go manually using key combination (vol up + pwr from a device off) and you have too adb reboot recovery command to boot on it.