Related
Hi all, please correct me if I placed this at the wrong thread.
I recently was flasing my phone with stock roms due to some technical difficulties I had. I realize the system will create an Android folder in my ext SD card. Is this normal? Do I need to be worry about it?
By the way, I am currently using 3.32.707.9 as my ROM, when I check my OS version in bootloader, there isn't anything there. Why is that so?
Can I flash back a lower version of ROM? For instance, 1.54.707.7
Thanks for helping in advance!
My responses below, in red font:
jkidz91 said:
I recently was flasing my phone with stock roms due to some technical difficulties I had. I realize the system will create an Android folder in my ext SD card. Is this normal? Do I need to be worry about it? Totally normal, no need to worry.
By the way, I am currently using 3.32.707.9 as my ROM, when I check my OS version in bootloader, there isn't anything there. Why is that so? This is usually due to using an older version of TWRP (known bug). This number is useful for determining your current firmware version (hboot, radio, etc.) but you can also determine that by looking at the hboot number and radio numbers themselves
Can I flash back a lower version of ROM? For instance, 1.54.707.7 Yes. Usually, you want the ROM version (1.x, 2.x etc.) to correspond to your current firmware. But its usually been found that a higher number firmware will usually work with older (smaller number) ROMs
Click to expand...
Click to collapse
redpoint73 said:
My responses below, in red font:
Click to expand...
Click to collapse
Which version of TWRP should I be using for now?
How do I verify which firmware am I using?
jkidz91 said:
Which version of TWRP should I be using for now?
How do I verify which firmware am I using?
Click to expand...
Click to collapse
What are your current hboot and radio baseband numbers?
Do you know what Android version you were on (4.4.2, 4.4.3, etc.) before you unlocked the bootloader and started flashing ROMs?
redpoint73 said:
What are your current hboot and radio baseband numbers?
Do you know what Android version you were on (4.4.2, 4.4.3, etc.) before you unlocked the bootloader and started flashing ROMs?
Click to expand...
Click to collapse
Current hboot is 3.19.0.0000
Radio baseband: 1.25.21331147A1.06G_20.69.4196.01_F
Previously should be on 4.4.2...I guess...ROM version 1.54.707.7
jkidz91 said:
Current hboot is 3.19.0.0000
Radio baseband: 1.25.21331147A1.06G_20.69.4196.01_F
Previously should be on 4.4.2...I guess...ROM version 1.54.707.7
Click to expand...
Click to collapse
Your hboot and radio numbers indicate your phone was either purchased with Lollipop firmware, or updated to LP firmware at some point.
You should use the latest version TWRP 2.8.7.
redpoint73 said:
Your hboot and radio numbers indicate your phone was either purchased with Lollipop firmware, or updated to LP firmware at some point.
You should use the latest version TWRP 2.8.7.
Click to expand...
Click to collapse
Yea, I upgraded to LP through phone update once.
Btw, I installed the latest version of TWRP as u said and was prompt by it by saying "TWRP has detected an unmodified system partition" and for permission to allow modifications...should I allow it?
jkidz91 said:
Yea, I upgraded to LP through phone update once.
Btw, I installed the latest version of TWRP as u said and was prompt by it by saying "TWRP has detected an unmodified system partition" and for permission to allow modifications...should I allow it?
Click to expand...
Click to collapse
I haven't seen this before, its a new feature for 2.8.7 (which you can have Googled just as easily as I just did):
we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery.
https://twrp.me/site/update/2015/06/22/twrp-2.8.7.0-released.html
Its actually not at all clear anymore what you are trying to do. You've posted in 2 or 3 different threads, asking about flashing firmware, running the RUU, or now you've flashed TWRP and maybe flashing an old 1.54 based ROM? Can't tell what your plan or end goal is at this time; and I'm not sure you know either.
redpoint73 said:
I haven't seen this before, its a new feature for 2.8.7 (which you can have Googled just as easily as I just did):
we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery.
https://twrp.me/site/update/2015/06/22/twrp-2.8.7.0-released.html
Its actually not at all clear anymore what you are trying to do. You've posted in 2 or 3 different threads, asking about flashing firmware, running the RUU, or now you've flashed TWRP and maybe flashing an old 1.54 based ROM? Can't tell what your plan or end goal is at this time; and I'm not sure you know either.
Click to expand...
Click to collapse
Basically my goal is to update my phone to LP..sorry for the confusion caused. I have managed to update the phone according to the link you gave as for the TWRP, I did some Google search as well...and decided not to allow the function...am I doing correct on this?
jkidz91 said:
Basically my goal is to update my phone to LP..sorry for the confusion caused. I have managed to update the phone according to the link you gave
Click to expand...
Click to collapse
Meaning you updated by RUU?
jkidz91 said:
as for the TWRP, I did some Google search as well...and decided not to allow the function...am I doing correct on this?
Click to expand...
Click to collapse
So you updated (apparently) to LP by RUU. Now what are you trying to do? Its still not clear.
Are you trying to root? If so, I'd allow the change, and then flash SuperSU 2.46 to root.
The text and link I provided is pretty clear about the mentioned TWRP function. The main reason to say "no" is to have a fully stock image, of which you can make a nandroid backup. Otherwise, you will probably want to pick "yes".
redpoint73 said:
Meaning you updated by RUU?
So you updated (apparently) to LP by RUU. Now what are you trying to do? Its still not clear.
Are you trying to root? If so, I'd allow the change, and then flash SuperSU 2.46 to root.
The text and link I provided is pretty clear about the mentioned TWRP function. The main reason to say "no" is to have a fully stock image, of which you can make a nandroid backup. Otherwise, you will probably want to pick "yes".
Click to expand...
Click to collapse
Correct me if I am wrong, if I would want to later on update my phone to higher OS, I should not allow TWRP to mount the system..correct?
Currently my situation is, I did not allow TWRP to do the mounting and I rooted the phone...and everything is working fine so far...does that mean I am safe?
jkidz91 said:
Correct me if I am wrong, if I would want to later on update my phone to higher OS, I should not allow TWRP to mount the system..correct?
Currently my situation is, I did not allow TWRP to do the mounting and I rooted the phone...and everything is working fine so far...does that mean I am safe?
Click to expand...
Click to collapse
If its working fine (for whatever purposed you need root), than you're good.
Although obviously, if you want to modify the system partition in the future, you will need write protection for that partition disabled.
You can always make a stock TWRP backup (which you should do, anyway) with the system unmounted, to return to for future OTA. Or return to stock using the RUU.
You also need the stock recovery to update by OTA. So your phone is not going to OTA update (update will fail) in its present configuration (with TWRP installed), regardless.
redpoint73 said:
If its working fine (for whatever purposed you need root), than you're good.
Although obviously, if you want to modify the system partition in the future, you will need write protection for that partition disabled.
You can always make a stock TWRP backup (which you should do, anyway) with the system unmounted, to return to for future OTA. Or return to stock using the RUU.
You also need the stock recovery to update by OTA. So your phone is not going to OTA update (update will fail) in its present configuration (with TWRP installed), regardless.
Click to expand...
Click to collapse
I need the Titanium backup to recover my apps and data ><
Hmmm..TWRP backup of the ROM...this is what you are talking about right?
Before that, does that mean that if the system has been tampered before, the OTA will not go in? This is what the link you gave just now talking about?
About the stock recovery, I am fully aware of this
I am really sorry if I keep causing trouble to you...I just want to double confirm...I have spent few days just to get my phone for working right...really exhausting to the mind ><
jkidz91 said:
Hmmm..TWRP backup of the ROM...this is what you are talking about right?
Before that, does that mean that if the system has been tampered before, the OTA will not go in? This is what the link you gave just now talking about?
Click to expand...
Click to collapse
Yes, the new feature seems to be aimed at ensuring the ROM is untampered, for making a full "stock" backup for OTA purposes.
jkidz91 said:
I am really sorry if I keep causing trouble to you...
Click to expand...
Click to collapse
No trouble at all. If I didn't enjoy helping, I wouldn't bother responding.
redpoint73 said:
Yes, the new feature seems to be aimed at ensuring the ROM is untampered, for making a full "stock" backup for OTA purposes.
No trouble at all. If I didn't enjoy helping, I wouldn't bother responding.
Click to expand...
Click to collapse
Got it! Whenever I do back up, do I need to back up the data? As I already got the Titanium to backup all my user apps.
What I am saying is the recovery let me choose what to back up...I chose only system, and boot i think...
redpoint73 said:
No trouble at all. If I didn't enjoy helping, I wouldn't bother responding.
Click to expand...
Click to collapse
Hi, after updating to Lollipop and using it for past few days, everything seems to be working fine...however, I have got a slight issue with Facebook app...whenever I am on my mobile data, I will have error loading the latest news feed. It is working fine on WiFi.
I have tested loading other apps with Mobile Data only...and they are working fine...I have researched online and some said I shall do a factory reset before and after a major update to OS...should I do this?
jkidz91 said:
Got it! Whenever I do back up, do I need to back up the data? As I already got the Titanium to backup all my user apps.
What I am saying is the recovery let me choose what to back up...I chose only system, and boot i think...
Click to expand...
Click to collapse
If the intent was to just backup a "stock ROM" than no need to backup user data.
If the intent is to make a recovery image, that you can just revert to and start using with no (or very little other actions) than backup data. But as you said, you can restore data (at least app data) with Titanium.
---------- Post added at 09:06 AM ---------- Previous post was at 09:04 AM ----------
jkidz91 said:
Hi, after updating to Lollipop and using it for past few days, everything seems to be working fine...however, I have got a slight issue with Facebook app...whenever I am on my mobile data, I will have error loading the latest news feed. It is working fine on WiFi.
I have tested loading other apps with Mobile Data only...and they are working fine...I have researched online and some said I shall do a factory reset before and after a major update to OS...should I do this?
Click to expand...
Click to collapse
If you updated by RUU then no need to factory reset. RUU already wiped all partitions, in a much more comprehensive way than factory reset.
Try clearing app cache for Facebook; or uninstalling Facebook app, and reinstalling, without restore data for that app with Titanium.
redpoint73 said:
If you updated by RUU then no need to factory reset. RUU already wiped all partitions, in a much more comprehensive way than factory reset.
Try clearing app cache for Facebook; or uninstalling Facebook app, and reinstalling, without restore data for that app with Titanium.
Click to expand...
Click to collapse
Tried doing so...not working...anyway, can I run the RUU again to wipe off the entire phone and set up as new?
jkidz91 said:
Tried doing so...not working...anyway, can I run the RUU again to wipe off the entire phone and set up as new?
Click to expand...
Click to collapse
You can run the RUU until the cows come home, if you want.
redpoint73 said:
You can run the RUU until the cows come home, if you want.
Click to expand...
Click to collapse
What does that mean? >< i tried to do it...it failed...should I just download a stock 4.19.707.2 rom and flash it?
So i have a twrp-3.2.0-m8.img flashed as the custom recovery which works fine. I tried to install SuperSU and got the binaries error of which i downloaded a much newer version and flashed it through twrp. From flashing it, this has screwed up my phone and i can only boot into hboot and recovery. When i try to boot it normally, it just stays on the HTC boot screen with the green and black text. How can i fix it back to normal or root it correctly?
Just restore your backup ... you should already make one before you tried to root it.
Post here fastboot getvar all result without serial & imei no then we'll see what you need.
ChiefMustardo said:
So i have a twrp-3.2.0-m8.img flashed as the custom recovery which works fine. I tried to install SuperSU and got the binaries error of which i downloaded a much newer version and flashed it through twrp. From flashing it, this has screwed up my phone and i can only boot into hboot and recovery. When i try to boot it normally, it just stays on the HTC boot screen with the green and black text. How can i fix it back to normal or root it correctly?
Click to expand...
Click to collapse
When I helped you previously, I had to advise you to provide the proper details. So why are you repeating the same mistakes here? You need to help us help you, by posting the proper details.
In addition to the getvar output requested by ckpv5, what versions of SuperSU did you use? "Much newer version" doesn't really tell us anything (at least not specific enough for us to help you).
Your current firmware version greatly affects what version TWRP and SuperSU you need to use to avoid problems that you mentioned (no boot). So we can't begin to properly help, until you provide the proper info.
Additionally, you started another thread asking same/related questions. I won't respond to that thread, as making multiple threads (for related issues) is confusing and will only cause more problems (such as hopping back and forth between the threads). Bump your existing thread, if you have to (and asking subsequent questions in that existing thread is an acceptable way of doing that). But please don't make more threads. I have some input on the specific questions you asked in the other thread:
ChiefMustardo said:
Can someone please explain to me why when i use twrp or cwm no ROM installs and the md5 check fails as does the signature verification and it says that the zip file is corrupt. It isn't because i got it from the skydragon website.
Click to expand...
Click to collapse
Can't say for sure why TWRP is failing, until you provide the getvar info. It can be a mismatch between your current firmware and the TWRP version. But we have no way of telling, unless you provide the requested details.
And are you trying to use multiple TWRP versions, or just the one mentioned? And BTW, there is no TWRP 3.2.0, so I assume you mean 3.0.2, but please confirm.
Also, I would avoid CWM, as it hasn't been updated in a very long time, which can create a lot of issue in itself.
What is the exact file name, or Skydragon version of the ROM you are trying to install (also very important)?
Just because you downloaded from Skydragon website, does not exclude the possibility the file is corrupt. A perfectly working file can get corrupted during download to your phone/computer. Try downloading twice, to eliminate that as a possibility.
You should also turn off MD5 verification in TWRP; which is probably causing the MD5 error (as mentioned by dottat here). MD5 check typically not used for ROMs (particularly if there was no MD5 hash code supplied with the ROM).
Here is my fastboot getvar all
http://prntscr.com/bd24cj
ChiefMustardo said:
Here is my fastboot getvar all
http://prntscr.com/bd24cj
Click to expand...
Click to collapse
It was also the SuperSU 2.46
ChiefMustardo said:
It was also the SuperSU 2.46
Click to expand...
Click to collapse
Skydragon: SkyDragon+M8+v4.0.0+Sense+8+MM
TWRP: twrp-3.0.2-0-m8
Philz touch: philz_touch_6.26.6-m8
1. You used wrong TWRP recovery 2.7.x.x that make your version-main now empty.
2. You installed wrong SuperSU - 2.46 is NOT for Marshmallow.
3. When you install a custom ROM, it is pre-rooted, no need to root before or after the ROM installation.
I suggest you revert to stock first then redo the whole thing ... rooting or installing a custom ROM, these you can do later after you fix your phone.
Read this for the drivers - http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
And this for installing RUU - http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Once it is back to stock, unlock the bootloader again with the unlock_code.bin that you received from htc. If it is not working, apply for a new one.
Once unlocked and after first boot and run setup & everything - install TWRP 3.0.2-0
then install custom ROM (no need to install SuperSU)
ChiefMustardo said:
It was also the SuperSU 2.46
Click to expand...
Click to collapse
That version is really old, released about Feb 2015!
SuperSU 2.65 is recommended. Anything older than 2.52 or so does not include the ability to root MM, and will fail with no boot/boot loop.
---------- Post added at 12:26 PM ---------- Previous post was at 12:24 PM ----------
ckpv5 said:
3. When you install a custom ROM, it is pre-rooted, no need to root before or after the ROM installation.
Click to expand...
Click to collapse
That is true, its not clear what the OP is currently trying to accomplish. This thread started out asking about root (stock ROM?) than started another thread asking about custom ROMs.
Its one or the other, not both (root vs. custom ROM) since as you mention, custom ROMs are already rooted.
I have tried using RUU to get it back to stock but it gets stuck in the updating 0/7 screen
ChiefMustardo said:
I have tried using RUU to get it back to stock but it gets stuck in the updating 0/7 screen
Click to expand...
Click to collapse
Just kill the process, and start it again. This is a reported issue for some folks.
If the issue reoccurs, we may have to look at USB connection issues.
Are you using the RUU zip method that ckpv5 directed in Post #7 above?
The RUU method you have suggested seems like it isworking.
The RUU worked thank you so much. Now to install SkyDragon ROM.
I tried the RUU.exe multiple times but that didn't work but yeah, ckpv5's method has worked. It is on Optimizing 44 of 153
ChiefMustardo said:
I tried the RUU.exe multiple times but that didn't work but yeah, ckpv5's method has worked.
Click to expand...
Click to collapse
The .exe is finicky. Anything but Windows 7 and USB 2.0 can cause problems with its USB connectivity. The zip method is more reliable (as you've seen).
It worked. How do i install a custom ROM? Do i get twrp 3.0.2 then install the zip from that? Also, do i keep my bootloader locked or unlock it?
ChiefMustardo said:
It worked. How do i install a custom ROM? Do i get twrp 3.0.2 then install the zip from that? Also, do i keep my bootloader locked or unlock it?
Click to expand...
Click to collapse
Read again : http://forum.xda-developers.com/showpost.php?p=67197327&postcount=7
Clearly stated :
ckpv5 said:
Once it is back to stock, unlock the bootloader again with the unlock_code.bin that you received from htc. If it is not working, apply for a new one.
Once unlocked and after first boot and run setup & everything - install TWRP 3.0.2-0
then install custom ROM (no need to install SuperSU)
Click to expand...
Click to collapse
OK thanks. Do I not require s-off then?
Also, i just tried to install the ROM with twrp (slide right to flash) and it said zip file is corrupt.
ChiefMustardo said:
OK thanks. Do I not require s-off then?
Click to expand...
Click to collapse
For the huge majority of mods (flashing custom ROMs, root, and much more) s-off is not needed. S-off is only needed for a few very specific things, such as manually flashing hboot, radio, changing CID or MID, and a few others.
---------- Post added at 09:27 AM ---------- Previous post was at 09:26 AM ----------
ChiefMustardo said:
Also, i just tried to install the ROM with twrp (slide right to flash) and it said zip file is corrupt.
Click to expand...
Click to collapse
What ROM specifically? Did you deselect the MD5 check in TWRP, as previously advised?
redpoint73 said:
For the huge majority of mods (flashing custom ROMs, root, and much more) s-off is not needed. S-off is only needed for a few very specific things, such as manually flashing hboot, radio, changing CID or MID, and a few others.
---------- Post added at 09:27 AM ---------- Previous post was at 09:26 AM ----------
What ROM specifically? Did you deselect the MD5 check in TWRP, as previously advised?
Click to expand...
Click to collapse
I am using the skydragon ROM (latest for Marshmallow) but in the zip the only file there is system. It also skips the MD5 check and has a progress bar for a bit and then comes up with the corrupt zip message.
Hi, I have bought used here in Italy a op3, when turn on in the display I can see a message about the bootloader unlock, and so I think that the previously owner have unlocked the unit. Now I have a problem with the update, I have tried with ota and with USB but the phone stop the update and show me the message installation failed, then I can only reboot. How I can relock the Bootloader? Thanks in advance for your help.
before you re-lock the bootloader you should make sure that you are running the stock oxygenOS rom and receovery, see below:
https://forums.oneplus.net/threads/...lus-3-and-go-back-completely-to-stock.456232/
thanks for your reply, I, think that the phone now running with OxygenOS 3.2.2 stock, so I can directly relock the bootloader? If I do an hard reset the bootloader will be relocked?
alchemist76 said:
thanks for your reply, I, think that the phone now running with OxygenOS 3.2.2 stock, so I can directly relock the bootloader? If I do an hard reset the bootloader will be relocked?
Click to expand...
Click to collapse
you might be running OOS 3.2.2 stock but still have a custom recovery - boot into recovery first just to confirm that you have the stock recovery as well
still if you have a custom recovery, it's easier to get update. Just download the full rom and flash it with TWRP (I don't think there is another custom recovery), it won't wipe the data. Even if the previous owner did a slight modification on OOS 3.2.2, it will overwrite it.
updates can be downloaded many days before the OTA appear on the phone.
Ok I think that I have a custom recovery, TWRP working with non rooted phone? I have checked and my phone not have root. Please can you explain how I can update through TWRP?
if you want to stay unlocked and use TWRP that's fine, but note that you will need to MANUALLY UPDATE every time if you're on the stock OOS ROM.
if you are not comfortable with this, follow the instructions on the link i sent you to get back to full stock with stock recovery as well, so updates OTA work correctly.
https://forums.oneplus.net/threads/...lus-3-and-go-back-completely-to-stock.456232/
2x4 thanks for your help, I not have any problem to keep my phone unlocked, but I don't able to update not even in manual way, maybe I wrong something.
I have enabled usb debug on op3, have connected the phone to my laptop and opened minimal ADB, then have downloaded the oxygenOS 3.2.4 put the phone in sideload mode, cecked the connection with adb devices command and the phone is connected. Then writed adb sideload and have dragged the oxigenOs .3.2.4 . but nothing happen in adb minimal and on the phone. After a bit the phone give me the same message that appears when I try to uptade through ota, installation failed an I can only reboot. Thanks again for your suggestions.
alchemist76 said:
2x4 thanks for your help, I not have any problem to keep my phone unlocked, but I don't able to update not even in manual way, maybe I wrong something.
I have enabled usb debug on op3, have connected the phone to my laptop and opened minimal ADB, then have downloaded the oxygenOS 3.2.4 put the phone in sideload mode, cecked the connection with adb devices command and the phone is connected. Then writed adb sideload and have dragged the oxigenOs .3.2.4 . but nothing happen in adb minimal and on the phone. After a bit the phone give me the same message that appears when I try to uptade through ota, installation failed an I can only reboot. Thanks again for your suggestions.
Click to expand...
Click to collapse
sorry, im not really sure what you mean, but if you're following the instructions on that post step by step and verifying what you get it should work.
You need to successfully flash the full zip to get the stock rom+recovery on there
ok sorry for my confusion. Please can you explain to me the right way to update a bootloader unlocked phone?
alchemist76 said:
ok sorry for my confusion. Please can you explain to me the right way to update a bootloader unlocked phone?
Click to expand...
Click to collapse
the bootloader being locked or unlocked is irrelevant - your issue is your non-stock recovery.
the full Oxygen OS zip includes the stock recovery from OnePlus, which OTA updates are programmed to use to automatically update your phone.
since you have TWRP recovery instead, you'll need to download and manually flash OxygenOS
download the full ZIP for 3.2.4 from this thread and flash it via TWRP recovery:
http://forum.xda-developers.com/oneplus-3/how-to/oxygen-os-3-2-4-released-t3437911
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.
Ok so I'm an android noob and my HTC One M9 is soft bricked, I'm not even sure if it can be fixed. It has (had) android 4.4.2, TWRP and it is unlocked. It all started because my phone randomly stopped booting up, it started freezing at the HTC logo. After trying a lot of things and nothing worked I decided to do a factory reset, but I accidentally deleted my whole OS from my recovery. I decided to flash a new ROM and I downloaded the latest version of ViperOneM9. I flashed it from my recovery, the installation went smooth with no errors. When I tried to start my phone it booted only to bootloader. I tried reinstalling the ROM several times but it didn't fix it. I read on another forum that I should update my recovery (it was an older version, maybe 2.8.7.0, I'm not sure). I downoaded the latest version and flashed it from my old recovery. After that my recovery became inaccessible as well - it says "Failed to boot to recovery mode. Press volume up or down to back to menu". I tried installing several different versions of TWRP with fastboot but none worked. I decided not to mess with my phone anymore, so I took it to a repair shop. They couldn't fix it, I just got my phone back from them. I don't know what they tried, but everything is the same- phone can't boot up, can't access recovery mode. . Can someone please help?
I'd guess your firmware is out of date. The latest version of ViperOneM9 assumes that you're on the Android 6.0 firmware. As for TWRP being non-functional, that's probably because the latest version (3.x.x.x) also assumes you're on the Android 6.0 firmware and isn't compatible with 4.4.2 firmware.
If you know your MID & CID, perhaps the easiest way to get the latest firmware on your phone is the SD-card method of flashing an RUU. You will lose everything on internal memory (probably a non-issue, since the OS was already deleted), and your phone will be reset to factory defaults. You'll need to unlock the bootloader, flash TWRP, and root (if you so choose) all over again. But the RUU will get you on your feet again, and with the latest firmware.
Alternatively, you could flash the old TWRP version and then a pre-Android 6.0 ROM onto your M9, which should restore functionality, albeit with an old version of the Android OS.
Are you sure that you own a One M9. The oldest android version for the M9 is 5.0. Your problems might be caused by the fact that you're flashing files that aren't compatible with your phone.
Sent from my HTC One S using XDA Labs
computerslayer said:
I'd guess your firmware is out of date. The latest version of ViperOneM9 assumes that you're on the Android 6.0 firmware. As for TWRP being non-functional, that's probably because the latest version (3.x.x.x) also assumes you're on the Android 6.0 firmware and isn't compatible with 4.4.2 firmware.
If you know your MID & CID, perhaps the easiest way to get the latest firmware on your phone is the SD-card method of flashing an RUU. You will lose everything on internal memory (probably a non-issue, since the OS was already deleted), and your phone will be reset to factory defaults. You'll need to unlock the bootloader, flash TWRP, and root (if you so choose) all over again. But the RUU will get you on your feet again, and with the latest firmware.
Alternatively, you could flash the old TWRP version and then a pre-Android 6.0 ROM onto your M9, which should restore functionality, albeit with an old version of the Android OS.
Click to expand...
Click to collapse
Thanks a lot for the help, I fixed my recovery but I have no idea from where can I find a pre-Android 6.0 ROM. I can't find download links on the official sites of the ROMs
Flippy498 said:
Are you sure that you own a One M9. The oldest android version for the M9 is 5.0. Your problems might be caused by the fact that you're flashing files that aren't compatible with your phone.
Sent from my HTC One S using XDA Labs
Click to expand...
Click to collapse
5.0.1 wasn't it?..
Beamed in by telepathy.
shivadow said:
5.0.1 wasn't it?..
Beamed in by telepathy.
Click to expand...
Click to collapse
Might be. It's been some time since I used firmware 1.x. The whole point of that post was that I wanted to explain that there's never been a 4.4.2 rom.
Sent from my HTC One S using XDA Labs