Related
hi, i have Rooted original rom,. unlocked with clockwork mod recovery.
tonight my phone got a OTA 20B,
i tried to install in but my phone is now only rebooting to recovery, is there a way to bypass?
makkie88 said:
hi, i have Rooted original rom,. unlocked with clockwork mod recovery.
tonight my phone got a OTA 20B,
i tried to install in but my phone is now only rebooting to recovery, is there a way to bypass?
Click to expand...
Click to collapse
How many different threads are we going to get from people asking this same question?
Don't accept an OTA update on a modified phone! If you want it then flash the original .kdz then OTA update then redo root and recovery.
hi all,
sorry to sound like a complete idiot in advance !
I have been trying for over a month now to find some way to return my phone to stock so I can get the new ota update but im just having no luck !
I have tried everything to unroot , relock boot loader, and return to stock, I can successfully unroot, successfully relock the boot loader but cannot update OTA everytime I download the ota and allow the phone to start update process the phone boots into bootlaoder and a new line appears in the normal messages **** security warning*** when this happens I loose recovery and the phone hasn't updated. I then have to re-unlock the bootloader to then flash a recovery.
I cant flash RUU as there isn't an RUU available for me, H3G_001 , I have tried the suggested CWM nandroid backup, but this fails half way through something to do with android_secure
I cant seem to get the phone to successfully grant s-off to try the change cid method, I have tried to do this using HTC one kit by hasoon but no luck,
if anyone could please help it would me much appreciated
regards
okz19
Probably you don't have the stock rom or the recovery, because the secure warning come out when you aren't fully stock..
Look on this site: http://www.htc1guru.com/downloads/stock-rom-downloads/
Mine One works now fine and i have update to the latest OTA.
Justin2003 said:
Look on this site: http://www.htc1guru.com/downloads/stock-rom-downloads/
Mine One works now fine and i have update to the latest OTA.
Click to expand...
Click to collapse
Is better link to XDA
still stuck!
hi all as you can probably tell form the age of this topic, I have been stuck for a while !!! (11 October ! )
I am still having problems trying to get the new update 2.24.771.3
my phone is carrier locked to three uk
it is unrooted
custom recovery cwm touch
bootloader unlocked / tampered
I understand I need stock recovery and to lock bootloader
I don't have stock rom
my problem is as follows, my phone has been telling me for atleast 4 months now that I have a software update, when I click it it restarts takes me to cwm recovery verifys install then gets stuck on cannot mount data ....
I understand I need to flash stock recovery, I have tried to do this using the "all in one kit" however when I click flash my own recovery, (phone reboots into bootloader) I then proceed to select the stock recovery.img the cmd box then hangs "waiting for device" I am then alerted by my computer that the usb device has malfunctioned. ( I am on windows 8 and have turned of signature verification)
I cannot use the supposed simple method of RUU as there isn't one available for my stupid network!!
I have tried to use a cwm recovery image, this usually starts then spits out android_secure is missing.
yes I do have a hammer ready to hit the phone with, but just before I do this is there ANYONE with any last tips to help me, because ive just about had enough with this stupid phone !
the phone has 24 hours left to live, can you save its life ?
thanks in advance for any help.
1. You cannot install an OTA with a custom recovery.
2. I've encountered a CWM bug having to do with .android_secure. There's a hidden folder in /sdcard that caused it, I don't remember whether this file is ".android_secure" or another. You can probably wipe the sdcard before restoring the backup. If that fails, you can probably manually restore the backup with ADB (this will be hard).
3. If you want to install the custom recovery, boot to the fastboot and use USB to install the recovery. Don't use a toolkit because they're useless when anything goes wrong.
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?
Hey everyone
I've recently solved my OTA problem (seen here) but I soon discovered yet another problem.
When I tried to enter SuperSU, I received the following error shown below.
As mentioned before, I'm on 4.4.2 and I have NO desire whatsoever to unlock my bootloader all over again. Is there anyway to re-root my phone without unlocking my bootloader or will I need to do just that in order to re-root?
Thanks in advance
Anyone?
Please help :crying:
ArmyMan007 said:
Please help :crying:
Click to expand...
Click to collapse
From what I know, and by the error displayed on the attached screenshot, you need to do the whole rutine all over again. I am pretty sure rooting can not be done if bootloader is locked, which might mean you have a stock recovery image as well - and since that is not keen to be rooted (as far as I know) you need to flash a custom recovery like twrp. I might be wrong in all this, I'm newish to all this.
ArmyMan007 said:
Hey everyone
I've recently solved my OTA problem (seen here) but I soon discovered yet another problem.
When I tried to enter SuperSU, I received the following error shown below.
As mentioned before, I'm on 4.4.2 and I have NO desire whatsoever to unlock my bootloader all over again. Is there anyway to re-root my phone without unlocking my bootloader or will I need to do just that in order to re-root?
Thanks in advance
Click to expand...
Click to collapse
Since you are S-ON you can not flash a custom recovery or root without unlocking your bootloader.
Frogger209 said:
From what I know, and by the error displayed on the attached screenshot, you need to do the whole rutine all over again. I am pretty sure rooting can not be done if bootloader is locked, which might mean you have a stock recovery image as well - and since that is not keen to be rooted (as far as I know) you need to flash a custom recovery like twrp. I might be wrong in all this, I'm newish to all this.
Click to expand...
Click to collapse
Well, for starters, my bootloader is unlocked (as mentioned before), thus we eliminate the bootloader unlocking dilemma. But it still doesn't tell me how can I re-root my device: you want to tell me that I have to do is to flash a custom recovery and install SuperSU again, and my phone will be rooted again?
majmoz said:
Since you are S-ON you can not flash a custom recovery or root without unlocking your bootloader.
Click to expand...
Click to collapse
Like I wrote before: I DO have an unlocked bootloader
ArmyMan007 said:
Well, for starters, my bootloader is unlocked (as mentioned before), thus we eliminate the bootloader unlocking dilemma. But it still doesn't tell me how can I re-root my device: you want to tell me that I have to do is to flash a custom recovery and install SuperSU again, and my phone will be rooted again?
Click to expand...
Click to collapse
flash twrp 2.6.3.3. boot in recovery then exit, twrp will prompt you to root the phone. Then yo ucan flash back the stock recovery for future ota updates.
alray said:
flash twrp 2.6.3.3. boot in recovery then exit, twrp will prompt you to root the phone. Then yo ucan flash back the stock recovery for future ota updates.
Click to expand...
Click to collapse
Why can't I flash twrp 2.7.1.0? and don't I need to install SuperSU via twrp? and what do you mean that twrp will promote me to root the phone? it never did that before..
ArmyMan007 said:
Why can't I flash twrp 2.7.1.0?
Click to expand...
Click to collapse
latest known bug free version of twrp is 2.6.3.3/.4 thats why we always recommend using this version.
and don't I need to install SuperSU via twrp? and what do you mean that twrp will promote me to root the phone? it never did that before..
Click to expand...
Click to collapse
that is for the M8 but same thing apply for the M7:
http://www.youtube.com/watch?v=bKGKlkJRroQ#t=122
or flash the latest su binary from twrp
alray said:
latest known bug free version of twrp is 2.6.3.3/.4 thats why we always recommend using this version.
that is for the M8 but same thing apply for the M7:
http://www.youtube.com/watch?v=bKGKlkJRroQ#t=122
or flash the latest su binary from twrp
Click to expand...
Click to collapse
I used to install the latest binary within twrp and it never asked me to do so. Now I got root access again Can I flash my stock recovery again?
ArmyMan007 said:
I used to install the latest binary within twrp and it never asked me to do so. Now I got root access again Can I flash my stock recovery again?
Click to expand...
Click to collapse
yes you can flash your stock recovery again, might be a good idea to do a nandroid backup of your current config before flashing back the stock recovery.
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot
alray said:
yes you can flash your stock recovery again, might be a good idea to do a nandroid backup of your current config before flashing back the stock recovery.
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
Will do! Thanks a bunch!!!
So i unlocked my moto and rooted it with magisk. I also flashed the twrp recovery. Now as i wanted to unroot the my moto, I unrooted from masgik uninstall option. But the twrp is still present in there. I think the stock recovery is override by the twrp. I need help as i wanted to be fully stock and lock the bootloader.
I think if i tried to lock bootloader now it will brick the moto as the stock recovery is not there. Help me guys.
sonangrai said:
So i unlocked my moto and rooted it with magisk. I also flashed the twrp recovery. Now as i wanted to unroot the my moto, I unrooted from masgik uninstall option. But the twrp is still present in there. I think the stock recovery is override by the twrp. I need help as i wanted to be fully stock and lock the bootloader.
I think if i tried to lock bootloader now it will brick the moto as the stock recovery is not there. Help me guys.
Click to expand...
Click to collapse
check out this post if you still have twrp recovery
https://forum.xda-developers.com/one-power/development/rom-twrp-flashable-stock-rom-t3916393
Jsonkat said:
check out this post if you still have twrp recovery
https://forum.xda-developers.com/one-power/development/rom-twrp-flashable-stock-rom-t3916393
Click to expand...
Click to collapse
I appreciate your help. But i am on Android 10 and i cannot flash the lower versions of android which may cause bootloop