How do I know whether I m using stock rom or custom .
And if I root my phone but didn't install custom rom so after unrooting will I get official updates
Thanks
No, unrooting is not enough. To quote myself from your other thread:
Flippy498 said:
Your system has to be not-rooted and mount as read-only. If you flash TWRP or install SuperSu it's mounted as read/write. Easiest way for you to recover the abiltity to install OTAs is flashing a RUU (if there is one for you actual firmware version). Boot to Download Mode and look at the line with OS at the beginning. Then search for a RUU that has the same version or a higher version. Only the SKU (= the number behind the second dot) has to be same. If the RUU you need is an *.exe then boot your phone to Download Mode, connect it to your PC, disable your internet connection (just for safety reasons), your firewall and your antivirus software (bith can interfere with a RUU) and execute the file as an admin. If the RUU is a *.zip then rename it to 0PJAIMG.zip, place it in the root directory of a SD card that is not bigger than 32gb and formatted to fat32, put the card into your phone, reboot to Download Mode and flash the file by pushing the volume up button.
Click to expand...
Click to collapse
You can check whether you're on a stock or a custom rom by looking at the software number in settings > about > software information. If you use a custom rom then its name and its version will be stated there (e.g. ViperOneM9 3.5.0 in my case).
This is a very bad thread name...
Ahmed_alishah said:
How do I know whether I m using stock rom or custom .
And if I root my phone but didn't install custom rom so after unrooting will I get official updates
Thanks
Click to expand...
Click to collapse
To get official updates you must unroot, flash stock recovery. and relock your phone, of course
luckyluke1605 said:
To get official updates you must unroot, flash stock recovery. and relock your phone, of course
Click to expand...
Click to collapse
This is not true. First there is no need to relock and second unrooting is not enough on the M9. You must either flash a RUU or an untouched TWRP backup. Otherwise you cannot recover the read-only state of your system and the update will fail.
Flippy498 said:
This is not true. First there is no need to relock and second unrooting is not enough on the M9. You must either flash a RUU or an untouched TWRP backup. Otherwise you cannot recover the read-only state of your system and the update will fail.
Click to expand...
Click to collapse
If you haven't flash rom cook, then no need for RUU or backup, unless M9 is different from M8. While using M8 I return to stock many times, but haven't tried with M9. When I got M9, I went directly to rom cook because of overheating
luckyluke1605 said:
(...) unless M9 is different from M8 (...)
Click to expand...
Click to collapse
That's the point. If you compare the M9 with the M8 there are completely different security checks implemented. You cannot update the M9 if you mounted it as read/write (e.g. by flashing SuperSu or installing a custom Rom) without flashing a RUU or restoring an untouched system image.
Flippy498 said:
That's the point. If you compare the M9 with the M8 there are completely different security checks implemented. You cannot update the M9 if you mounted it as read/write (e.g. by flashing SuperSu or installing a custom Rom) without flashing a RUU or restoring an untouched system image.
Click to expand...
Click to collapse
Thanks for the note. I'll pay attention if I want back to stock
Related
so here it goes:
i bought the asia tw m8 (HTC__621) just when it got out and unlocked BL,rooted,installed custom roms
so eventually i cant update to newer android versions through ota.
my hboot is 3.16 and i tried s-off
firewater doestnt work on asia tw and sunshine developer wont help me since i live in a county that can`t use paypal
so dear devs. anyone......pleasee help me out
i dont know what to do....
specially when android L is coming to our devices.
thx in advance
Collection of stock backus Go there download the nandroid backup for your device(1.54.709.12) and the stock recovery also on post 1.
Restore the nandroid backup for your device with the custom recovery(It was made with TWRP so use TWRP) flash back the stock recovery and just follow all the OTA updates to get to the latest 4.4.4 and you'll also be ready for 5.0 when it launches(whenever).
You literally did no searching for your problem at all.
armin0131 said:
so here it goes:
i bought the asia tw m8 (HTC__621) just when it got out and unlocked BL,rooted,installed custom roms
so eventually i cant update to newer android versions through ota.
my hboot is 3.16 and i tried s-off
firewater doestnt work on asia tw and sunshine developer wont help me since i live in a county that can`t use paypal
so dear devs. anyone......pleasee help me out
i dont know what to do....
specially when android L is coming to our devices.
thx in advance
Click to expand...
Click to collapse
I am sure firewater should work on your device. I just S-OFF and gained superCID. Your device is basically a GSM phone. The only advantage of doing OTA updates are that you will be getting updates a tad faster. The disadvantage is it might brick your phone with wrong firmware/device ID. My advice would be to try to get S-OFF again. If your phone is rooted and bootloader unlocked go ahead and flash a custom recovery such as TWRP. If you do no know how to flash your recovery you can download an app called Flashify and it will flash TWRP for you via google play store app.
Once you get TWRP recovery you can reboot into recovery and simply do a system restart. It will ask if you want to install superSU. Make sure you have superSU installed. follow the instructions from here http://firewater-soff.com/instructions/ I recommend being on a stock sense ROM. Make sure you have debugging enabled via developer option and enabling unknown devices. Once you push firewater to your phone and allow superSU app to grant permission you SHOULD get s-OFF.
Once you get s-OFF you can change your phone version ID to superCID via bootloader+adb command "fastboot oem writecid 1111111" After that you can just flash over any firmware you want. I say wait for devs to get official gpe 5.0 dumps and it'll be way better than an OTA rom.
IF your phone ever gets into a bootloop or frozen reboot it via holding down volume up+down+power. The phone will reboot.
vang2k said:
I am sure firewater should work on your device. I just S-OFF and gained superCID. Your device is basically a GSM phone. The only advantage of doing OTA updates are that you will be getting updates a tad faster. The disadvantage is it might brick your phone with wrong firmware/device ID. My advice would be to try to get S-OFF again. If your phone is rooted and bootloader unlocked go ahead and flash a custom recovery such as TWRP. If you do no know how to flash your recovery you can download an app called Flashify and it will flash TWRP for you via google play store app.
Once you get TWRP recovery you can reboot into recovery and simply do a system restart. It will ask if you want to install superSU. Make sure you have superSU installed. follow the instructions from here http://firewater-soff.com/instructions/ I recommend being on a stock sense ROM. Make sure you have debugging enabled via developer option and enabling unknown devices. Once you push firewater to your phone and allow superSU app to grant permission you SHOULD get s-OFF.
Once you get s-OFF you can change your phone version ID to superCID via bootloader+adb command "fastboot oem writecid 1111111" After that you can just flash over any firmware you want. I say wait for devs to get official gpe 5.0 dumps and it'll be way better than an OTA rom.
IF your phone ever gets into a bootloop or frozen reboot it via holding down volume up+down+power. The phone will reboot.
Click to expand...
Click to collapse
People should stop telling people that firewater should work for sure on certain devices ! It's never a guarantee !!!
It's a try and see ! Perform firewater on the stock rom and stock recovery, if it's not working you definitely need sunshine
I recommend being on a stock sense ROM. Make sure you have debugging enabled via developer option and enabling unknown devices. Once you push firewater to your phone and allow superSU app to grant permission you SHOULD get s-OFF.
Once you get s-OFF you can change your phone version ID to superCID via bootloader+adb command "fastboot oem writecid 1111111" After that you can just flash over any firmware you want. I say wait for devs to get official gpe 5.0 dumps and it'll be way better than an OTA rom.
IF your phone ever gets into a bootloop or frozen reboot it via holding down volume up+down+power. The phone will reboot.[/QUOTE]
well the problem is I am way ahead of you I have installed TWRP installed countless roms I'm not a noob I know my way around phones...
and because of my cid and modelid I'm not able to use fire water.
if you can, suggest a way that I can update my frimwire i've tried a lot of things
its not my first rodeo.
helpful suggestions please.thanks in advance
Thanks for saying this stuffbut they are not helping.
well the problem is I am way ahead of you I have installed TWRP installed countless roms I'm not a noob I know my way around phones...
and because of my cid and modelid I'm not able to use fire water.
if you can, suggest a way that I can update my frimwire i've tried a lot of things
its not my first rodeo.
helpful suggestions please.thanks in advance
for the last time:it is the Asia Taiwan(2.5 ghz ver.) a lot of other users tried firewater
and so did I and I can't use it because I'm living in a country that is restricted to use paypal
Mr Hofs said:
People should stop telling people that firewater should work for sure on certain devices ! It's never a guarantee !!!
It's a try and see ! Perform firewater on the stock rom and stock recovery, if it's not working you definitely need sunshine
Click to expand...
Click to collapse
Mr hofs is there any way to use sunshine without paying through paypal?for example paying through google play gift card!
BerndM14 said:
Collection of stock backus Go there download the nandroid backup for your device(1.54.709.12) and the stock recovery also on post 1.
Restore the nandroid backup for your device with the custom recovery(It was made with TWRP so use TWRP) flash back the stock recovery and just follow all the OTA updates to get to the latest 4.4.4 and you'll also be ready for 5.0 when it launches(whenever).
Click to expand...
Click to collapse
If you are unable to use sushine to s-off due to Paypal, just return to stock ROM and recovery to get the OTAs as stated above.
Mr Hofs said:
People should stop telling people that firewater should work for sure on certain devices ! It's never a guarantee !!!
It's a try and see ! Perform firewater on the stock rom and stock recovery, if it's not working you definitely need sunshine
Click to expand...
Click to collapse
redpoint73 said:
If you are unable to use sushine to s-off due to Paypal, just return to stock ROM and recovery to get the OTAs as stated above.
Click to expand...
Click to collapse
Wouldn't integrity of the files in the system and data partitions be a problem?!
Cause when you unlock some apps which are in data partition get deleted.
and when the rom is rooted and im guessing the nandroid backup is rooted...
the system partition is changed.
please correct me if i'm wrong
thx
Is there any place i can get the stock untouched rom for my cid number?
i went to htc-dev website's download section and saw a few things about asia tw downloads.but couldnt understand it or how it's used.I would appreciate it if you went there and take a look for yourself
thx
armin0131 said:
Wouldn't integrity of the files in the system and data partitions be a problem?!
Cause when you unlock some apps which are in data partition get deleted.
and when the rom is rooted and im guessing the nandroid backup is rooted...
the system partition is changed.
please correct me if i'm wrong
thx
Click to expand...
Click to collapse
Are you talking about system changes preventing OTA updates? If so, being rooted has nothing to do with it, it won't prevent an OTA from installing. It'll remove root from the device in which case you'll have to re-root(if you want) but it won't prevent the OTA from installing.
Besides as far as I know, unless stated differently, the backups in the thread are all unrooted.
armin0131 said:
Is there any place i can get the stock untouched rom for my cid number?
i went to htc-dev website's download section and saw a few things about asia tw downloads.but couldnt understand it or how it's used.I would appreciate it if you went there and take a look for yourself
thx
Click to expand...
Click to collapse
Guess you should have made a backup of your device before you messed around. That way you would have known for a fact it was "untouched" .
Just download the backup provided in the link, flash a stock recovery and do the OTA's. You can even go through the small effort ahead of time and "unroot" it just in case it was "rooted" which I doubt it will be.
Go here
http://forum.xda-developers.com/showthread.php?t=2701376
And read the first AND second post with care !
armin0131 said:
Mr hofs is there any way to use sunshine without paying through paypal?for example paying through google play gift card!
Click to expand...
Click to collapse
There is. You can send them US Amazon Gift Card in order to get the code for Sunshine.
Poslano z mojega HTC One_M8 z uporabo Tapatalk
Mr Hofs said:
Go here
http://forum.xda-developers.com/showthread.php?t=2701376
And read the first AND second post with care !
Click to expand...
Click to collapse
I wonder... :angel:
Mr Hofs said:
Go here
http://forum.xda-developers.com/showthread.php?t=2701376
And read the first AND second post with care !
Click to expand...
Click to collapse
Ok what i wanna know is that are the deleted apps for example flashlight
Restored in the 1.54.709.12 backup? So no MD5 problem when i wanna OTA?
armin0131 said:
Wouldn't integrity of the files in the system and data partitions be a problem?!
Cause when you unlock some apps which are in data partition get deleted.
and when the rom is rooted and im guessing the nandroid backup is rooted...
the system partition is changed.
Click to expand...
Click to collapse
Root alone does not change system partition. Its only changes to system files you do after root that will prevent OTA.
And in theory, the stock backups in Mr Hofs collection should be made without root, I believe. Root is not needed to make a nandroid.
As far as I have seen, the couple HTC apps that are "deleted" upon bootloader unlock do not affect OTA. There are lots of folks here with unlocked bootloaders that were able to return to stock ROM and recovery and OTA.
redpoint73 said:
Root alone does not change system partition. Its only changes to system files you do after root that will prevent OTA.
And in theory, the stock backups in Mr Hofs collection should be made without root, I believe. Root is not needed to make a nandroid.
As far as I have seen, the couple HTC apps that are "deleted" upon bootloader unlock do not affect OTA. There are lots of folks here with unlocked bootloaders that were able to return to stock ROM and recovery and OTA.
Click to expand...
Click to collapse
There are some already rooted.
XSL-FO said:
There are some already rooted.
Click to expand...
Click to collapse
One for a know fact as its stated in the download link. And it's very usable for official ota as its 100% complete. And if it bothers people it's rooted they have to read the second post too as it contains a flashable zip to delete root access. But that's not being said here because people probably don't read enough very well !
And indeed root is not needed for a nandroid backup. Only a custom recovery is enough to create one.
ooof that made me sound interesting !
Cheers.
Mr Hofs said:
One for a know fact as its stated in the download link. And it's very usable for official ota as its 100% complete. And if it bothers people it's rooted they have to read the second post too as it contains a flashable zip to delete root access. But that's not being said here because people probably don't read enough very well !
Cheers.
Click to expand...
Click to collapse
Well, la-di-da
armin0131 said:
Ok what i wanna know is that are the deleted apps for example flashlight
Restored in the 1.54.709.12 backup? So no MD5 problem when i wanna OTA?
Click to expand...
Click to collapse
Ahh ... you're asking about my backup that I uploaded.
No ... nothing is deleted from backup 1.54.709.12, everything is there like the flashlight, calculator & etc. No root, no busybox... simply clean stock.
In fact, once you restore the backup with full wipe of your current ROM, you'll get the setup wizard just like when you setup the phone for the first time.
I originally had a stock sense M8 (bought it first day) but since October, I changed my phone to GPE (GPE Firmware and everything) and have been using 5.0 eversince using SkyDragon rom. Ran into issues a few weeks ago, and i've been waiting hard to go back to sense and use the newer 5.0 sense version.
However, today I ran into multiple issues, I thought installing the latest Sense Lollipop firmware and installing the latest ARHD 5.0 rom would do the trick, sadly that did not work.
I flashed the latest sense firmware and the ROM only for it to boot saying my Data is corrupt and i have to reset my phone, i say okay(was going to do that anyway) but then I access my recovery (TWRP) and my Internal storage/Cache/Data will not mount. I tried going back to GPE (atleast so my phone would work) but I cant do that either because even with the GPE firmware, the data partition wont mount and my internal storage shows 0 MB in TWRP, now im just stick in a bootloop/bricked device for hours. Any help would really be appreciated...thanks a lot.
Dev Edition RUU is what I would recommend. Partitioning is different on GPE versus Sense. So I'm guessing running the firmware only, since its not a complete image, did not change the partitioning back to the Sense partition scheme.
Converting from GPE back to Sense is not trivial, and not to be taken lightly. It seems like you tried to make up your own process instead of following any definitive guide or advice, which I do not recommend.
redpoint73 said:
Dev Edition RUU is what I would recommend. Partitioning is different on GPE versus Sense. So I'm guessing running the firmware only, since its not a complete image, did not change the partitioning back to the Sense partition scheme.
Converting from GPE back to Sense is not trivial, and not to be taken lightly. It seems like you tried to make up your own process instead of following any definitive guide or advice, which I do not recommend.
Click to expand...
Click to collapse
Thanks for your reply, to get this clear:
I should flash the Dev Edition RUU from (http://forum.xda-developers.com/htc-one-m8/development/ruu-m8-developer-edition-sense-1-54-t2884777) (3.28.1540.5) and then update the firmware to 4.16.1540.8 by just flashing that separate zip. However, if I flash the RUU wouldn't it relock my bootloader and put me on S-On and lose root and the custom recovery(Im terribly sorry if this sounds dumb, but my phone is soft bricked and I really need to get everything right this time), Is that the case if I flash the dev edition RUU? Thanks again.
Austin3161337 said:
However, if I flash the RUU wouldn't it relock my bootloader and put me on S-On and lose root and the custom recovery
Click to expand...
Click to collapse
No, RUU will not relock the bootloader. The only way the bootloader gets locked/unlocked is if you do so yourself.
Same with s-off, there is nothing that can change that aside from you making it s-on yourself.
Yes, you will lose custom recovery, as RUU will install stock recovery. So just flash stock recovery by fastboot after RUU. Then flash the ROM you want, which should already be rooted (so losing root is a moot point).
Official firmware.zip will also write stock recovery. So doing so would have caused the loss of TWRP anyway (unless it was a user modified firmware zip).
redpoint73 said:
No, RUU will not relock the bootloader. The only way the bootloader gets locked/unlocked is if you do so yourself.
Same with s-off, there is nothing that can change that aside from you making it s-on yourself.
Yes, you will lose custom recovery, as RUU will install stock recovery. So just flash stock recovery by fastboot after RUU. Then flash the ROM you want, which should already be rooted (so losing root is a moot point).
Official firmware.zip will also write stock recovery. So doing so would have caused the loss of TWRP anyway (unless it was a user modified firmware zip).
Click to expand...
Click to collapse
So I downloaded the RUU from (http://www.htc.com/us/support/htc-one-m8/news/) but its an .exe which requires me to plug my phone in which my computer cannot recognize because the phone won't boot at all, is there anyway I can install the RUU by not really needing to connect the phone to the computer? (Put the file in the external SD and install it via the bootloader maybe?) Any tips on that? Thanks
Austin3161337 said:
So I downloaded the RUU from (http://www.htc.com/us/support/htc-one-m8/news/) but its an .exe which requires me to plug my phone in which my computer cannot recognize because the phone won't boot at all
Click to expand...
Click to collapse
The phone doesn't need to boot into OS to run the RUU. It just needs to be able to get into bootloader/fastboot mode, which it can if the screen comes on.
If the device doesn't show on your PC, its a different issue. USB connectivity issue is almost always a driver issue. Install HTC Sync and HTC drivers, if you haven't already. Or uninstall and install them again.
I have a similiar issue. I had a tombile ruu.zip that a flashed as a 0P6Bimg.zip a kitkiat sense version for tmobile. Everything is cool and it runs fine. When I change cid and mid then flashed the sense lollipop firmware I lost my internal memory and twrp read storage as 0mb.
So idk
I flashed the Dev RUU as recommended by redpoint73, booted up and now it says that its updating to the latest firmware android 5.0 (OTA Update) However, I am going to install a custom recovery (TWRP) and put on ARHD instead, thanks for the help, and pretty much unbricking my device, lol.
Austin3161337 said:
I flashed the Dev RUU as recommended by redpoint73, booted up and now it says that its updating to the latest firmware android 5.0 (OTA Update) However, I am going to install a custom recovery (TWRP) and put on ARHD instead, thanks for the help, and pretty much unbricking my device, lol.
Click to expand...
Click to collapse
You're very welcome. Happy to help.
Did you have to do anything to get the RUU to run (like install drivers), or did you just end up running the RUU exe, and it worked?
redpoint73 said:
You're very welcome. Happy to help.
Did you have to do anything to get the RUU to run (like install drivers), or did you just end up running the RUU exe, and it worked?
Click to expand...
Click to collapse
I already had HTC Sync installed, had to boot into Fastboot USB for the thing to get recognized.
So long story short I screwed up.
Flashed a custom recovery and didn't backed up the stock one, I already tried checking several threads with the nandroid backups and recoveries but not the one for my device.
my cid HTC_332
mid 0P6B16000
software 1.12.599.20
s-on, thanks in advance.
Doesn't appear to be one. I'd S-OFF your device and then just flash the unbranded Developer Edition RUU instead as I don't think there have been any updates for your version
Gmoro said:
my cid HTC_332
software 1.12.599.20
s-on, thanks in advance.
Click to expand...
Click to collapse
I never expect some people are still on 1.x version. I removed all my nandroid backups for 1.x
Guess I need to reupload all 1.x bakups again :crying:
You can use 1.57.599.1 backup and then update all the way to the latest lollipop version 4.20.599.3 (1.57.599.1 --> 2.25.599.1 --> 3.36.599.2 --> 4.20.599.3)
If you still runs the stock 1.12.599.20 but don't have the stock recovery, what you can do is download the OTA but select install later, copy the OTA zip to PC. Open the OTA zip with 7-zip, open firmware.zip, extract out the recovery.img <--- use this recovery.img to proceed OTA installation
ckpv5 said:
I never expect some people are still on 1.x version. I removed all my nandroid backups for 1.x
Guess I need to reupload all 1.x bakups again :crying:
Click to expand...
Click to collapse
You'll be saving my phone, thanks.
Also another question, in order to install otas I need to lock my bootloader and remove root, right?
Since I'm s-on.
Gmoro said:
Also another question, in order to install otas I need to lock my bootloader and remove root, right?
Since I'm s-on.
Click to expand...
Click to collapse
No, not correct. There is no need to lock bootloader for OTA.
OTA will remove root.
Stock 2.25.599.1 recovery - http://sourceforge.net/projects/htconem8/files/Recovery/2.25.599.1_recovery.img/download
Hi Folks,
Well, I'm S-OFF and running ViperROM with 2.10.401.1 firmware (from sneakyghost thread) and TWRP Recovery on an international device with unlocked bootloader and SuperCID.
Now I want to play again with a full fresh and clean stock experience. How to accomplish this?
The easiest way would be to run a 2.10.401.1 RUU exe, but I couldn't find one. I guess it's not available and maybe never will be.
So, after reading threads I would assume the way I have to go is to run an 1.32 RUU exe and then I should get the 2.10 OTA
Is that right or do I have to relock the bootloader to get stock OTAs ? (Cos of S-OFF)
Hope you could help me out on that one and point me in the right direction.
Thx
You have to be 100% stock to get OTAs successfully. Since you're s-off, just running an earlier RUU exe should do it, but you may need to relock.
Under no circumstances should you go back to s-on.
DroidShift79 said:
Hi Folks,
Well, I'm S-OFF and running ViperROM with 2.10.401.1 firmware (from sneakyghost thread) and TWRP Recovery on an international device with unlocked bootloader and SuperCID.
Now I want to play again with a full fresh and clean stock experience. How to accomplish this?
The easiest way would be to run a 2.10.401.1 RUU exe, but I couldn't find one. I guess it's not available and maybe never will be.
So, after reading threads I would assume the way I have to go is to run an 1.32 RUU exe and then I should get the 2.10 OTA
Is that right or do I have to relock the bootloader to get stock OTAs ? (Cos of S-OFF)
Hope you could help me out on that one and point me in the right direction.
Thx
Click to expand...
Click to collapse
Hi
Did you check this thread...
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
MAX 404 said:
Hi
Did you check this thread...
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
Click to expand...
Click to collapse
Yes, did that. But the full ZIP that is there doesn't touch the /system partition, so it's not the clean way I want to go.
THX anyway.
DroidShift79 said:
Yes, did that. But the full ZIP that is there doesn't touch the /system partition, so it's not the clean way I want to go.
THX anyway.
Click to expand...
Click to collapse
Hi
I see....guess the only way for now is as you point out earlier RUU and upgrade from there.
good luck
MAX 404 said:
Hi
I see....guess the only way for now is as you point out earlier RUU and upgrade from there.
good luck
Click to expand...
Click to collapse
Thought of this,
just not sure if I need to relock bootloader to get official otas
DroidShift79 said:
Thought of this,
just not sure if I need to relock bootloader to get official otas
Click to expand...
Click to collapse
If you're S-OFF you don't need to relock to get OTAs. I converted my carrier handset to unbranded and received OTA updates after flashing a RUU without relocking.
Sent from my HTC One M9 using Tapatalk
THX kingvortex. I just do it and report back.
Thanks all of you.
DroidShift79 said:
Thought of this,
just not sure if I need to relock bootloader to get official otas
Click to expand...
Click to collapse
kingvortex said:
If you're S-OFF you don't need to relock to get OTAs. I converted my carrier handset to unbranded and received OTA updates after flashing a RUU without relocking.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
hi mates
I do not think S-OFF , S-ON or locked bootloaders are much of an issue to get OTA, check points 8, 9 and 10 from this thread
EDIT : kingvortex you are right oem locked is necessary with s-on
http://forum.xda-developers.com/one...ery-twrp-touch-recovery-t3066720/post59745198
8. How do I restore stock system so that I can accept an OTA?
Check the "Mount system as read-only" box in the Mount menu.
Restore stock "System Image" backup (This will only work if you've made a System Image backup prior to making any modifications to /system like root it). As of the official 2.8.6.1 version, it is no longer necessary to fastboot flash the stock system image.
NOTE: If you made a stock system backup with one of the Beta TWRP versions, you will have to rename the backup file in the backup folder manually from "system.emmc.win" to "system_image.emmc.win" for the new official TWRP to see it as a "System Image" backup rather than a "System" backup. Otherwise, you'll get an error that the backup can't be restored because system is read-only.
Fastboot flash stock recovery (fastboot flash recovery recovery_signed.img)
NOTE: It is also possible to restore stock recovery via the TWRP GUI. Rename the stock recovery file to "recovery.emmc.win" and place in the backup folder with the stock system image. Recovery will then show as a restore option. MAKE SURE YOU REALLY WANT TO DO THIS, AS TWRP WILL BE GONE WHEN YOU REBOOT OUT OF RECOVERY!!
Reboot to system, install OTA.
9. What if I have an RUU? Do I need to worry about all this OTA nonsense?
Not if you don't care about losing all your data. If you're S-ON and have an RUU available for your exact variant (model ID and CID must match) and software number (main version must be the same or newer), then you can get back to a fully stock state by relocking (fastboot oem lock) and flashing an RUU. However, if you'd prefer to take an OTA to keep your data intact, the method stated above is how to do so. Or, you can just run a custom ROM and wait for your ROM chef to update their ROM to the latest software (though you'll still have to find a way to update your firmware if you're not S-OFF)
10. After I go through all this and successfully apply an OTA, how do I make sure I have a clean starting point again?
After the OTA is applied and TWRP is flashed, it will once again detect an untouched system, which will mount system read-only and allow you to make a fully stock backup and start the process over again, this time with the new base.
Well, what I did so far, was to use the 1.32.401.17 ruu.exe
Flash went fine, but no OTA did show up.
So I wanted to flash the 1.32.401.8 ruu zip.
But putting it on sdcard or using fastboot flash zip failed.
Wonder why!?
Later on I'll try Max 404 find.
MAX 404 said:
hi mates
I do not think S-OFF , S-ON or locked bootloaders are much of an issue to get OTA, check points 8, 9 and 10 from this thread
EDIT : kingvortex you are right oem locked is necessary with s-on
http://forum.xda-developers.com/one...ery-twrp-touch-recovery-t3066720/post59745198
8. How do I restore stock system so that I can accept an OTA?
Check the "Mount system as read-only" box in the Mount menu.
Restore stock "System Image" backup (This will only work if you've made a System Image backup prior to making any modifications to /system like root it). As of the official 2.8.6.1 version, it is no longer necessary to fastboot flash the stock system image.
NOTE: If you made a stock system backup with one of the Beta TWRP versions, you will have to rename the backup file in the backup folder manually from "system.emmc.win" to "system_image.emmc.win" for the new official TWRP to see it as a "System Image" backup rather than a "System" backup. Otherwise, you'll get an error that the backup can't be restored because system is read-only.
Fastboot flash stock recovery (fastboot flash recovery recovery_signed.img)
NOTE: It is also possible to restore stock recovery via the TWRP GUI. Rename the stock recovery file to "recovery.emmc.win" and place in the backup folder with the stock system image. Recovery will then show as a restore option. MAKE SURE YOU REALLY WANT TO DO THIS, AS TWRP WILL BE GONE WHEN YOU REBOOT OUT OF RECOVERY!!
Reboot to system, install OTA.
9. What if I have an RUU? Do I need to worry about all this OTA nonsense?
Not if you don't care about losing all your data. If you're S-ON and have an RUU available for your exact variant (model ID and CID must match) and software number (main version must be the same or newer), then you can get back to a fully stock state by relocking (fastboot oem lock) and flashing an RUU. However, if you'd prefer to take an OTA to keep your data intact, the method stated above is how to do so. Or, you can just run a custom ROM and wait for your ROM chef to update their ROM to the latest software (though you'll still have to find a way to update your firmware if you're not S-OFF)
10. After I go through all this and successfully apply an OTA, how do I make sure I have a clean starting point again?
After the OTA is applied and TWRP is flashed, it will once again detect an untouched system, which will mount system read-only and allow you to make a fully stock backup and start the process over again, this time with the new base.
Click to expand...
Click to collapse
HTC One m9 :Boot loader is,unlocked but device is not rooted will I get official Android 6 marshmallow
Bcoz now I get official maintenance update but after downloading can't install them .
Thanks
Ahmed_alishah said:
HTC One m9 :Boot loader is,unlocked but device is not rooted will I get official Android 6 marshmallow
Bcoz now I get official maintenance update but after downloading can't install them .
Thanks
Click to expand...
Click to collapse
Do you have stock recovery installed? Are you on a custom rom?
Ahmed_alishah said:
HTC One m9 :Boot loader is,unlocked but device is not rooted will I get official Android 6 marshmallow
Bcoz now I get official maintenance update but after downloading can't install them .
Thanks
Click to expand...
Click to collapse
No you cannot. Bootloader must be locked (not relocked) and everything must be as stock (except s-off).
I wish I stole my HTC M9.
jsaxon2 said:
Do you have stock recovery installed? Are you on a custom rom?
Click to expand...
Click to collapse
Actually I bought used I found it was rooted like supersu file was their I unrooted it from that aap so now I want to know whether I can install official update or not bcoz I can download bcoz I get notification system update available I downloaded it but while installation it gets aborted .
And I think it's stock rom..
shivadow said:
Bootloader must be locked (not relocked) and everything must be as stock (except s-off).
Click to expand...
Click to collapse
Ahmed_alishah said:
Actually I bought used I found it was rooted like supersu file was their I unrooted it from that aap so now I want to know whether I can install official update or not bcoz I can download bcoz I get notification system update available I downloaded it but while installation it gets aborted .
And I think it's stock rom..
Click to expand...
Click to collapse
There is no need to lock/relock. Your system has to be not-rooted and mount as read-only. If you flash TWRP or install SuperSu it's mounted as read/write. Easiest way for you to recover the abiltity to install OTAs is flashing a RUU (if there is one for you actual firmware version). Boot to Download Mode and look at the line with OS at the beginning. Then search for a RUU that has the same version or a higher version. Only the SKU (= the number behind the second dot) has to be same. If the RUU you need is an *.exe then boot your phone to Download Mode, connect it to your PC, disable your internet connection (just for safety reasons), your firewall and your antivirus software (bith can interfere with a RUU) and execute the file as an admin. If the RUU is a *.zip then rename it to 0PJAIMG.zip, place it in the root directory of a SD card that is not bigger than 32gb and formatted to fat32, put the card into your phone, reboot to Download Mode and flash the file by pushing the volume up button.
shivadow said:
Bootloader must be locked (not relocked) and everything must be as stock (except s-off).
Click to expand...
Click to collapse
My Developer Edition M9 was shipped with the bootloader unlocked, with 5.0 (1.32.617.30), and it received the OTA updates to 5.1 (2.11.617.15) just fine.
Thanks everyone