Related
I have an htc One running on the Reliance Network. Versions 4.1.2 / 1.29.651.10
It is Bootloader Unlocked with TWRP 2.6.0.1 and root
I have downloaded the mouthful OTA_M7_WL_JB_50_SPCS_Sprint_WWE_1.31.651.2-1.29.651.10_release_326731tcfazf1gnytc7g74.zipOTA_M7_WL_JB_50_SPCS_Sprint_WWE_1.31.651.2
-1.29.651.10_release_326731
When I try to flash it using TWRP it bombs out as there is no MD5 file.
I have two queries:
1. How do I update the TWRP to 2.6.3.0?
2. How do I install the update.
I prefer to use the fastboot method?
I have downloaded the update to my PC since aborting deletes the file. Also, I have the TWRP on my PC.
Please advise and help.
Check PM
sgiitk said:
I have an htc One running on the Reliance Network. Versions 4.1.2 / 1.29.651.10
It is Bootloader Unlocked with TWRP 2.6.0.1 and root
I have downloaded the mouthful OTA_M7_WL_JB_50_SPCS_Sprint_WWE_1.31.651.2-1.29.651.10_release_326731tcfazf1gnytc7g74.zipOTA_M7_WL_JB_50_SPCS_Sprint_WWE_1.31.651.2
-1.29.651.10_release_326731
When I try to flash it using TWRP it bombs out as there is no MD5 file.
I have two queries:
1. How do I update the TWRP to 2.6.3.0?
2. How do I install the update.
I prefer to use the fastboot method?
I have downloaded the update to my PC since aborting deletes the file. Also, I have the TWRP on my PC.
Please advise and help.
Click to expand...
Click to collapse
You cannot upgrade when your phone is rooted(i got to know from hetaldp)
I upgraded to JB 4.3, it awesome. Touch is Excellent. i too use relaince. there are no issues.
BUT remember you cannot root again, as over i am facing problems,,,
check : http://forum.xda-developers.com/showthread.php?t=2494594
So Please kindly wait, till the root for hTC ONE for upgraded JB 4.3 one Comes...
Are you using Sprint or T-Moile or Version HTC ONE?
To get upgrade installed, please un-root, relock, and then you can perform the update...
[email protected] said:
You cannot upgrade when your phone is rooted(i got to know from hetaldp)
I upgraded to JB 4.3, it awesome. Touch is Excellent. i too use relaince. there are no issues.
So Please kindly wait, till the root for hTC ONE for upgraded JB 4.3 one Comes...
Are you using Sprint or T-Moile or Version HTC ONE?
To get upgrade installed, please un-root, relock, and then you can perform the update...
Click to expand...
Click to collapse
It is Sprint, and from Hetal. Unrooting and relocking can be a pain, reloading everything. However, for almost two years I did not do any work on the Android side, so have forgotten everything.
I do not mind a locked phone it I can get to 4.3
Can you please pm me with the unrooting, relocking and the 4.3! Root for 4.3 is inevitable - just a matter of time.
Following the GooManager route I managed to get TWRP 2.6.3.0 installed, except the phone did not reboot. I did check it is 2.6.3.0.
Now the problem of the OTA remains. Maybe I will be forced to follow pm.mohanani's route of relocking. I cannot understand if I relock the bootloader then is not the unrooting automatic!
Also, Mr Mohanani GooManager requires root, so do not bother.
Managed to upgrade to 4.3 using Sprint_HTC_One_m7wls_3_04_651_2_RUU from Android Central as suggested by Hetal. I had to do a <fastbook oem lock> first. No problems except it wiped the data totally. Working fine. I have a few points / questions
1. Booting into Recovery is showing the Red Exclamation in a Triangle. Obviously not working, as in rooted!!
2. The Boot into recovery is showing both [RELOCKED] and S-off.
- Is this the cause?
- As per Hetal S-off means that I can root straight away irrespective of the Relocked status
- I guess OTA to KitKat (when it comes) is also a no go.
- What recovery is suggested TWRP 2.6.3, CWM (version?), or some other. This means that 4.4 will again be a full reload.
- Any fixes?
sgiitk said:
Managed to upgrade to 4.3 using Sprint_HTC_One_m7wls_3_04_651_2_RUU from Android Central as suggested by Hetal. I had to do a <fastbook oem lock> first. No problems except it wiped the data totally. Working fine. I have a few points / questions
1. Booting into Recovery is showing the Red Exclamation in a Triangle. Obviously not working, as in rooted!!
2. The Boot into recovery is showing both [RELOCKED] and S-off.
- Is this the cause?
- As per Hetal S-off means that I can root straight away irrespective of the Relocked status
- I guess OTA to KitKat (when it comes) is also a no go.
- What recovery is suggested TWRP 2.6.3, CWM (version?), or some other. This means that 4.4 will again be a full reload.
- Any fixes?
Click to expand...
Click to collapse
There is no need to accept the OTA if you are s-off
bigdaddy619 said:
There is no need to accept the OTA if you are s-off
Click to expand...
Click to collapse
Thanks. So I will again wait for the 4.4 RUU to be available on XDA or somewhere, and then install and forget OTA.
The point is recovery. I presume with S-off custom recovery must to be installed.
Do I install TWRP which takes care of root or do you suggest some other route, ie, root (how?) > recovery.
sgiitk said:
Thanks. So I will again wait for the 4.4 RUU to be available on XDA or somewhere, and then install and forget OTA.
The point is recovery. I presume with S-off custom recovery must to be installed.
Do I install TWRP which takes care of root or do you suggest some other route, ie, root (how?) > recovery.
Click to expand...
Click to collapse
Install TWRP 2.6.3.0
Option 1 flash SuperSU or another superuser file and run stock rooted
Option 2 flash a custom rom
Still stuck. I downloaded GooManager, and it will go into download > nowstarting and hang forever. I was advised to go the adb fastboot way, i.e.
download latestTWRP image filethen
adb reboot bootloader
then when I get
ui fstboot
fastboot flash recovery <twrp-recovery-name.img>
and its done.
I downloaded the .img file. Put everything into c:\recovery. Moved there under the command prompt. Plugged the phone into the computer, got both the drives (htc sync manager, and HTCONE) . So the connection was kosher.
Then gave adb reboot bootloader
The adb daemon started, but it found no device.
Obviously I being a noob in this game was missing something.
Also, I hear that the ROMs are available which to not reformat the storage. Are these the Deodexed versions or something.
Also, once in ten calls or so the screen goes totally blank at the end and is pain to restart the phone.
Checked up with http://forum.xda-developers.com/showthread.php?t=2497712
Seems that I am S-off but no rooted! Now what??
After a day or so and some cool thought I think I may have the problem identified. It is likely to be the lack of a root. I tried the following and the responses there from:
adb reboot bootloader
rebooted into bootloader Showing relocked and S-off. No fastboot option in the lower menu!
Now:
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img
I get
sending recovery <8600kB>...
Okay [ 1.140s]
writing 'recovery'...
FAILED <remote not allowed>
finished. total time 1.170s
Any ideas, and when may I expect root for 4.3. At the moment the phone appears to be working file, but no recovery!! HELP!!
Do I need to unlock again despite S-off. Also, then what is the bitstream I send it from 4.3 - the same as the old one!!
Yes you need to unlock your bootloader again to be able to flash twrp
I did as per the htc route - Do the unlock, reinstalled the OS, download the bitstream, etc, and then the OS reloaded. Still Goomanager could not get TWRP 2.6.3.0 so used the fastboot route and succeeded in downloading it to the phone. Thanks for encouraging me and putting me on the right track.
Now ho to root. Then I may as well get Titanium up!
You can get SuperSU or Superuser from the playstore or install a custom rom.
A very interesting experience. I could not enter bootloader [Down-vol + power was just restarting the phone], even adb devices was drawing a blank. So I decided to do a factory reset from phone. Lo and behold it dropped me into the TWRP screen. I managed to root, restarted to the main Downloaded su checker which completed the root. Confirmed. Then downloaded Titanium with Pro license (I have it) and did a recovery. Also, TWRP Manager (downloaded) is working and I am able to start into bootloader, etc.
When I try and look for upgrades with TWRP installer it says none. I know 2.6.3.0 has been upgraded to 2.6.3.2 Let sleeping dogs lie.
Also, I have not checked with adb devices but I am sure that too will now work.
Thanks, but what is going on. Is it only God and maybe Google know what happened?
Thanks for helping, and keeping me going.
I had more or less decided to revert to 4.1 and do an S-on <fastboot oem writesecureflag 3> and bootloader lock and look for OTA!
Added on 25th November
adb still not recognising the beast. adb devices gets a blank list. Phone is available under Windows so drivers etc are Ok.
A noob question. I saw
Stock Rooted 3.04.651.2 Odex & De-Odexed
Insecure Boot img. init.d support, data/app support
Stock Rooted 3.04.651.2 Odex
Stock Rooted 3.04.651.2 De-Odexed
on the upgrade thread. Now what do the terms Rootedm Odex and De-Odexed mean to the average user. Stock means the basic htc ROM I presume.
Also, rooted means what stages are covered.
afaik to upgrade you lock the bootloader, do the upgrade, and then in normal situations again unlock the bootloader, root and install a custom recovery (TWRP does the rooting - hopefully).
Do these ROMs take care of some or more of these stages?
Hello,
I'd like to ask few question about using the factory reset option with a stock 4.3 sense rom (unlocked bootloader, rooted and twrp recovery)
So, i rooted my device to try out viper4android but turns out its completely useless to me as i later learned that stock does not allow read/write to system partition and now i'm wondering how to go back safely.
As i said above, i'm still using the stock 4.3 rom with an unlocked bootloader no other changes made, so my question is to go back stock (using factory reset) do i need to:
1. Flash stock recovery and do a factory reset.
2. Flash stock recovery, relock bootloader and do a factory reset.
3. Guru reset M7
4. Other?
Thanks ~
EDIT:
Quick update, so just flashed stock recovery and used factory reset, now ofc the root did remain, so now my question is, can i
take ota safely with stock rom/recovery but rooted?
Thanks ~
Anyone please, are any of my choices the good one (if so wich one)?
Goolum said:
Anyone please, are any of my choices the good one (if so wich one)?
Click to expand...
Click to collapse
This is the way to go back to a stock ROM:
http://forum.xda-developers.com/showthread.php?t=2541082
If you’re on hboot which is above 1.44, then first thing is to downgrade that:
so download this: http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
in bootloader/FASTBOOT USB, flash it:
fastboot oem rebootRUU
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot flash zip 1.29.401.12_hboot_1.44.zip <---- just in case the above said “failed flush again”
fastboot reboot-bootloader
--> and confirm hboot is now 1.44
Thank you for your help, the problem is i'm on hboot 1.55 and rumrunner ain't working because of the
secure stock kernel, so i cannot go with the ruu way, wich is why i was wondering if i could simply use
the factory reset option since other than being rooted it is fully stock, or else the htc1 guru reset option.
Goolum said:
Anyone please, are any of my choices the good one (if so wich one)?
Click to expand...
Click to collapse
Post ur getvar all if ur confused as to which RUU to flash
As i said above flashing a ruu ain't an option since i'm s-on, what i meant by factory reset is the built in option (either through fastboot
or settings) with stock sense since i did not change anything, just unlocked the bootloader and rooted, and if that's not possible then if
guru reset utility for peoples with s-on is a good idea.
So i ended flashing stock recovery and used factory reset, everything did go alright tho ofc the root did remain, so now my question is, can i
take kitkat ota safely with stock rom/recovery but rooted? Or the fact that it's rooted risk messing up stuff? Oh and i dont mind loosing root.
Thanks ~
Goolum said:
So i ended flashing stock recovery and used factory reset, everything did go alright tho ofc the root did remain, so now my question is, can i
take kitkat ota safely with stock rom/recovery but rooted? Or the fact that it's rooted risk messing up stuff? Oh and i dont mind loosing root.
Thanks ~
Click to expand...
Click to collapse
Your fine...you will lose root tho...
so say i upgrade my rooted htc one once the ota update becomes ready.. what happens? i dont want to end up with a bricked phone.. would it harm my phone in any way?
thaaaanxxx
monrokhoury said:
so say i upgrade my rooted htc one once the ota update becomes ready.. what happens? i dont want to end up with a bricked phone.. would it harm my phone in any way?
thaaaanxxx
Click to expand...
Click to collapse
An OTA update will not work on a rooted phone! For the OTA to work it needs stock recovery, stock rom and all of the files that it is attempting to update. If anything is missing then it will error out and return to your present setup.
and to complete what majmoz already said, if your rom is 100% stock, and you have flashed back your stock recovery, the phone will update fine but you will loose root. You'll need to flash a custom recovery after the OTA to re-root the rom.
Guys you're very helpful and i must thank you for that. i am on the official 4.4.3 rom so i just need to restore the stock recovery? how to do that? and will the current rooting method work on lollipop (and should i follow the same steps to install clockwork recovery)? Will the ota update relock the bootloader?
i'm sorry if i'm asking too many questions but i don't trust any other forum.
monrokhoury said:
Guys you're very helpful and i must thank you for that. i am on the official 4.4.3 rom so i just need to restore the stock recovery?
Click to expand...
Click to collapse
If you have not modified anything to your rom (Kernel is stock and always was, you have not deleted any /system files and you still have or restored all the content in /data/preload (wiped during bootloader unlock), so yes all you need to do is to flash back the stock recovery that match your version.
how to do that?
Click to expand...
Click to collapse
The same way you did to flash a custom recovery:
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot
and will the current rooting method work on lollipop
Click to expand...
Click to collapse
Flash the latest supersu from a custom recovery. Version 2.37 and above should work on lollipop
and should i follow the same steps to install clockwork recovery
Click to expand...
Click to collapse
You always flash the recovery using the same commands, stock or custom, on all versions its always:
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot
Will the ota update relock the bootloader?
Click to expand...
Click to collapse
OTA updates will never affect the bootloader status (S-ON/S-OFF, LOCKED/UNLOCKED/RELOCKED)
If you have not modified anything to your rom (Kernel is stock and always was, you have not deleted any /system files and you still have or restored all the content in /data/preload (wiped during bootloader unlock), so yes all you need to do is to flash back the stock recovery that match your version.
Click to expand...
Click to collapse
So, if I did flash a custom kernel, and did uninstall system programs (but didn't flash a custom Rom), what are my options if I'd like to upgrade to lollipop?
Thanks!
Sent from my HTC One using XDA Free mobile app
I got an OTA update named OTA_M7_UL_L50_SENSE60_MR_TMOUS_7.18.531.35-7.18.531.2_release_450302.zip with size about 180MB.
Did anybody else get it?
I can't apply the update though because I have twrp and the phone is rooted. I was wondering if someone else got the update and applied it successfully on a rooted phone.
devsk said:
I got an OTA update named OTA_M7_UL_L50_SENSE60_MR_TMOUS_7.18.531.35-7.18.531.2_release_450302.zip with size about 180MB.
Did anybody else get it?
Click to expand...
Click to collapse
Should post this question here: http://forum.xda-developers.com/showthread.php?t=2305490
and the answer is probably yes since I don't see why T-mobile USA would push an ota update only to you
7.18.531.35 is the t-mobile US equivalent of 7.17.1540.35 which is the latest version with the stagefright 1.0 vulnerability fixed.
I can't apply the update though because I have twrp and the phone is rooted. I was wondering if someone else got the update and applied it successfully on a rooted phone.
Click to expand...
Click to collapse
You need to be on 100% stock rom including stock recovery to install ota updates. Better to return to stock using a ruu before applying the update imo since many users soft bricked their phones when attempting to install lollipop ota updates on stock rooted phones. If you need the RUU, look in the RUU collection thread, there is a 7.18.531.2 RUU posted there (link in my signature). Don't forget that questions should be posted in the q&a section, not in general. :good:
Thanks for your help. I found the RUU for my version. So, since I need to go back to RUU flash, I will need to re-setup my phone from scratch again just for getting this OTA....sucks!!
I wish they would make it easier to update modified phones. Just overwrite my root changes to /system and destroy my recovery but keep my /data and /sdcard. I can recover from that much faster than doing RUU and set up from scratch!!
So, on m7, isn't there way to flash stock on /system and stock recovery through fastboot and then take the OTA? I have done that on at least Samsung and Moto phones in the past and it worked fine.
So, if I restore system and boot partitions from my backup to stock, can I sideload the OTA ZIP using TWRP?
I should have made a recovery.img from the original stock recovery partition. Do you know if I can find the stock recovery here somewhere?
devsk said:
I wish they would make it easier to update modified phones. Just overwrite my root changes to /system
Click to expand...
Click to collapse
It is, you'll loose root every time you do an ota update.
and destroy my recovery
Click to expand...
Click to collapse
The ota is flashed using the stock recovery, and the stock recovery is also updated in that process.
So, on m7, isn't there way to flash stock on /system and stock recovery through fastboot and then take the OTA? I have done that on at least Samsung and Moto phones in the past and it worked fine.
Click to expand...
Click to collapse
Yes, either using a RUU, or a combination of a stock rom/backup (/system partition) flashed using twrp and then flashing the stock recovery back.
So, if I restore system and boot partitions from my backup to stock, can I sideload the OTA ZIP using TWRP?
Click to expand...
Click to collapse
No, the updater-script will only work with stock recovery
I should have made a recovery.img from the original stock recovery partition.
Click to expand...
Click to collapse
You can't backup the stock recovery directly from the phone (actually yes you can but it requires s-off and its somewhat complicated.
Do you know if I can find the stock recovery here somewhere?
Click to expand...
Click to collapse
already uploaded here:
https://www.androidfilehost.com/?fid=23991606952604831
or you can extract it from the ota update.
It was possible to update a stock rom + rooted phone simply by flashing the stock recovery back in the past (on kitkat roms and eariler) but it looks like its not possible anymore on lollipop updates. So much ppl posted here with the same problem: "Phone is stuck at HTC splash screen after installing update on stock rooted phone". Example here and here
The biggest problem if the ota install fine but the phone is stuck at the booting screen (like in the link above) is that your firmware will be updated to 7.18.531.35 so you won't be able to use the 7.18.531.2 RUU anymore unless you achieve S-OFF or edit your MISC partition.
alray said:
It is, you'll loose root every time you do an ota update.
The ota is flashed using the stock recovery, and the stock recovery is also updated in that process.
Yes, either using a RUU, or a combination of a stock rom/backup (/system partition) flashed using twrp and then flashing the stock recovery back.
No, the updater-script will only work with stock recovery
You can't backup the stock recovery directly from the phone (actually yes you can but it requires s-off and its somewhat complicated.
already uploaded here:
https://www.androidfilehost.com/?fid=23991606952604831
or you can extract it from the ota update.
It was possible to update a stock rom + rooted phone simply by flashing the stock recovery back in the past (on kitkat roms and eariler) but it looks like its not possible anymore on lollipop updates. So much ppl posted here with the same problem: "Phone is stuck at HTC splash screen after installing update on stock rooted phone". Example here and here
The biggest problem if the ota install fine but the phone is stuck at the booting screen (like in the link above) is that your firmware will be updated to 7.18.531.35 so you won't be able to use the 7.18.531.2 RUU anymore unless you achieve S-OFF or edit your MISC partition.
Click to expand...
Click to collapse
Thanks for the great help! I can't thank you enough.
One question: if I do fail to apply the OTA zip after restoring boot, system and recovery to stock, I will still be able to get TWRP back on the recovery through fastboot and restore my full TWRP backup to get a working system back, right? Is there a gotcha in that route?
devsk said:
Thanks for the great help! I can't thank you enough.
One question: if I do fail to apply the OTA zip after restoring boot, system and recovery to stock, I will still be able to get TWRP back on the recovery through fastboot and restore my full TWRP backup to get a working system back, right? Is there a gotcha in that route?
Click to expand...
Click to collapse
yes, even if the ota installation fails, you''ll be able to access fastboot, flash back twrp and restore your twrp nandroid backup. :good:
alray said:
yes, even if the ota installation fails, you''ll be able to access fastboot, flash back twrp and restore your twrp nandroid backup. :good:
Click to expand...
Click to collapse
Awesome!! :good::good:
If I have a P9 on Nougat B391, I receive an OTA, am currently rooted on Magisk v14. If I install the OTA anyway? What will happen? I know I will lose root, but will my bootloader be relocked? Am I going to lose any data?
Would like to know what will happen next as I am thinking of installing it. thanks!
there are 2 posible outcomes, maybe 3.
1. update will be successfull and you will lose root, twrp, bootloader can be locked too, but on fastboot it will shown as unlocked, if you cant instal twrp, then you need to unlock bootloader even if there is tuped unlocked.
2. update will fail and you will be back on same build you was.
3. never hapened to me, but are possible, that phone got bricked!
Arnys said:
there are 2 posible outcomes, maybe 3.
1. update will be successfull and you will lose root, twrp, bootloader can be locked too, but on fastboot it will shown as unlocked, if you cant instal twrp, then you need to unlock bootloader even if there is tuped unlocked.
2. update will fail and you will be back on same build you was.
3. never hapened to me, but are possible, that phone got bricked!
Click to expand...
Click to collapse
IMO, (2) is most possible utcome. (3) may happen if you force DLOAD and other manual methods.
Better:
1) unroot by Magisk Uninstaller, find the download link in the post https://forum.xda-developers.com/showpost.php?p=74913863&postcount=1
2) flash from TWRP original stock boot img
3) wipe Dalwik and Cache from TWRP
3) flash from fastboot original stock recovery
4) let it make OTA update but select in the System Update settings to use Full (not differential) update - it will not delete your apps and settings
Of course, you will loose root and TWRP but bootloader will remain unlocked and you will not risk bricking the phone.
Arnys said:
there are 2 posible outcomes, maybe 3.
1. update will be successfull and you will lose root, twrp, bootloader can be locked too, but on fastboot it will shown as unlocked, if you cant instal twrp, then you need to unlock bootloader even if there is tuped unlocked.
2. update will fail and you will be back on same build you was.
3. never hapened to me, but are possible, that phone got bricked!
Click to expand...
Click to collapse
thanks, this roughly gives me an idea on what would happen and the risks it contains! thanks a lot!
zgfg said:
IMO, (2) is most possible utcome. (3) may happen if you force DLOAD and other manual methods.
Better:
1) unroot by Magisk Uninstaller, find the download link in the post https://forum.xda-developers.com/showpost.php?p=74913863&postcount=1
2) flash from TWRP original stock boot img
3) wipe Dalwik and Cache from TWRP
3) flash from fastboot original stock recovery
4) let it make OTA update but select in the System Update settings to use Full (not differential) update - it will not delete your apps and settings
Of course, you will loose root and TWRP but bootloader will remain unlocked and you will not risk bricking the phone.
Click to expand...
Click to collapse
thanks a lot! it's useful to know how to unroot my phone as there isn't any particular guide for this phone model haha. anyway, is there a way to unroot and lock my bootloader without wiping my phone?
roottree said:
thanks a lot! it's useful to know how to unroot my phone as there isn't any particular guide for this phone model haha. anyway, is there a way to unroot and lock my bootloader without wiping my phone?
Click to expand...
Click to collapse
Magisk Uninstaller does not wipe your phone.
However, unlocking or relocking Bootloader (from Fastboot) triggers Factory restore