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?
The more I read the more confused I get. Could someone sort me out?
<complain>I got the moto x because of the quick OTA updates. Now it seems that because I installed TWRP and froze a few apps with TB that this feature is totally borked!</complain> is that correct? I cannot update without stock recovery and all the original apps installed / unfrozen?
In my predicament would the easiest thing to do be
1. Unfreeze any system apps I've frozen.
2. Use msfastboot to reflash stock recovery?
3. Accept the OTA or somehow flash it manually (I'm not sure about this last one see below)
I accidentally accepted the OTA download and now it bugs me to install. I won't install because it just reboots into TWRP. But it does keep prompting me to set at time to install. If I simply flash stock recovery I think i will still get this prompt. Would that be the easiest way to go?
Thanks for any advice.
pairustwo said:
The more I read the more confused I get. Could someone sort me out?
<complain>I got the moto x because of the quick OTA updates. Now it seems that because I installed TWRP and froze a few apps with TB that this feature is totally borked!</complain> is that correct? I cannot update without stock recovery and all the original apps installed / unfrozen?
In my predicament would the easiest thing to do be
1. Unfreeze any system apps I've frozen.
2. Use msfastboot to reflash stock recovery?
3. Accept the OTA or somehow flash it manually (I'm not sure about this last one see below)
I accidentally accepted the OTA download and now it bugs me to install. I won't install because it just reboots into TWRP. But it does keep prompting me to set at time to install. If I simply flash stock recovery I think i will still get this prompt. Would that be the easiest way to go?
Thanks for any advice.
Click to expand...
Click to collapse
1. - You do not need to unfreeze apps. The apps are still there untouched in the file system, and in recovery the OS hasn't booted enough to know that the apps are "frozen". By the way, frozen apps are basically just tagged in the OS as not available....so with the OS not running (just recovery is), they aren't "frozen" in recovery.
2. - Yes, fastboot to flash stock recovery. Boot to bootloader mode, fastboot flash recovery recovery.img (you don't need mfastboot for recovery, though you can still use it.)
3. - Accept the OTA. Since yours is trying to install, you should be able to boot to bootloader, flash stock recovery and on reboot it will start the install of the OTA. When done and booted.....reflash TWRP if you like.
That would be the way to go, yes.
Flash stock recovery and try to upgrade. If you cannot, try to unfreeze all sys apps. That should do it. ?
OK. So maybe not such a huge PIA as I had thought. I will track down the recovery file and read the instructions for flashing.
Thanks
@pairustwo
Every time another OTA comes out, people who modify their phones ask the same question. I've written up a FAQ based on the past OTA's.. -> http://mark.cdmaforums.com/MotoX-OTA.html if you want to read it to get more info.
Part of the issues you are talking about when taking an OTA is that the OTAs want to patch and replace only SOME files on your phone, so it checks to make sure the update is for your phone and its android version by evaluating certain files on the phone, that they exist and that their check sums match what the update expects.
i.e. change/modify/delete files the OTA update checks before installing, and the OTA will refuse to install.
If it didn't do this, the wrong update could possibly flash to your phone, replacing files with incompatible versions and making a big mess.
So yeah, "getting back to stock" (or as close to it as you can) is always recommended before taking an OTA so the "check" doesn't fail and prevent the OTA from applying.
In the past, freezing apps with Ti Backup was enough of a modification to cause the OTA's to fail. So often it is still suggested to un-freeze those done with TiBackup.
The OTA zip file (as downloaded) will only flash from Stock Recovery. TWRP and CWM for example don't properly process and flash them, so if you try to install when stock recovery is NOT on your phone, you get stuck in a bootloop. Using mFastboot to flash stock recovery back on is fine for those with unlocked bootloaders. Locked Bootloader users, is another matter.
There is a way "side load" the OTA, IF you have stock recovery, your phone hasn't received the push from Moto or your Carrier yet, and the OTA Zip file has leaked. But it still requires you get back to stock, etc. just as if you were getting it OTA.
So I've tried to flash back to stock but am having an issue. Does anyone have a link to a stock recovery image? Maybe the one I have is corrupt.
pairustwo said:
So I've tried to flash back to stock but am having an issue. Does anyone have a link to a stock recovery image? Maybe the one I have is corrupt.
Click to expand...
Click to collapse
Answered here -> http://forum.xda-developers.com/moto-x/moto-x-qa/dead-android-red-exclamation-t2778189
and I made this -> http://mark.cdmaforums.com/MotoX-EnterStockRecovery.htm
I've been out of circulation of the whole xda thing for a while with my HTC One M7 (AT&T version) but I decided to convert the thing to GPE and get updated to android 5.1.
The conversion went smoothly using this guide but now I am having some troubles applying the OTA to update to 5.1
I have tried unrooting by using the unroot option on SuperSU and then flash the OTA using stock recovery, only to find that when I want to access stock recovery I get a screen with the android alien lying down and the error "No command".
I figured I could flash the stock recovery with fastboot to fix this (downloaded 5.11.1700.3 from here) but I still get the same screen and error when selecting the recovery option from the fastboot screen.
In a desperate move I also tried flashing CWM and trying to flash the zip file but the OTA fails to install that way.
What am I doing wrong here?
Thanks in advance for your help
Hi,
I have a rooted pure edition device running TWRP recovery. Actual system is LP 5.0.0. The system is bugging me to update 5.0.2 via wireless, but have no wireless available. I have tried to do this at the cafe but when it restarts, TWRP is taking over in boot sequence and an signature error appears in the log. Then when I reboot the system, it constantly shuts down.
Lucky I had a recovery file, but now I have the zip file in the /cache dir, 5.0.0 wants to restart the device all the time!!
This wifi update is going to be a problem as I do not use this technology at all. This is a true buggery from Motoblur and have looked into CM12 however there is no CM12 available for us, only a nightly release that fails to install through TWRP.
Any help is welcome.
Thanks in advance.
You cannot update until you put the stock recovery back on the device and unroot.
That is really really annoying... I cant unroot my device everytime there is an update thats just ridiculous...
Is that what you do? Otherwise, what do you do? Did you manage to get CM running?
You can also stop the ota by freezing or renaming the moto ota service. But yes, I unroot, flash stock recovery and update. Then flash twrp and reroot .
Okay will do that. Are you on 5.0.2 0r 5.1?
No CM12 for us aye?
What method do you recommend for xt1092 unroot. Via SU or Multitool?
I got an OTA update notification several months ago and wanted to update but realized it won't work as long as I have TWRP Recovery.
Now I decided to install the update. Therefore I flashed a stock recovery (M8_MINI_UL_Stock_Recovery_2.19.401.2.img).
When trying to update, the phone goes to the stock recovery and the update proceeds but after about one quarter of the progress bar, it stops and shows the red exclamation mark (!).
I have stock rom, stock recovery, unlocked bootloader, dt2w kernel.
Do I need to reflash the stock kernel and if so, where can I get it and how can I do it (fastboot flash boot.img?)?
Is it also really required to relock the bootloader in order to succeed in updating and if so, how can I do it?
Regards
So far I've tried flashing original kernel, original recovery and relocking but the update still fails.
I also took the firmware.zip included in the OTA and flashed it via h-boot. Seemed to update bootloader, recovery and radio.
Then I rebooted, again got the update notification and tried to install it.
But still the same error. Any ideas?