Related
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?
Hello,
I just installed latest OTA with security fixes and after reboots it's stuck at the white HTC screen.
I'm s-off, relocked and have custom recovery.
How to get into android without losing data?
Thanks in advance
mderksen said:
Hello,
I just installed latest OTA with security fixes and after reboots it's stuck at the white HTC screen.
I'm s-off, relocked and have custom recovery.
How to get into android without losing data?
Thanks in advance
Click to expand...
Click to collapse
How exactly did you install it? The usual way, doenloaded the OTA and let your phone upgrade? Or you took the firmware.zip and flashed it via fastboot?
help plz
donkeykong1 said:
How exactly did you install it? The usual way, doenloaded the OTA and let your phone upgrade? Or you took the firmware.zip and flashed it via fastboot?
Click to expand...
Click to collapse
i am facing the same problem.. i downloaded it frm settings>about>software update..
i was running teamwin recovery.. it failed to install..
thn i flashed stock recovery..
thn installed the ota frm software updates...
btw now my phn is stuck on the boot screen... plz hlp...
HTC M7UL
ROOTED
i was running 7.19.401.22
I'm facing the same problem: Stuck on white HTC screen.
1. Saw the notice for the OTA update for 7.19.401.30.
2. Since I was running Teamwin, reflashed 7.19.401.22 stock firmware.
3. Installed OTA 7.19.401.30.
4. Stuck on black screen (nothing on it, but illuminated)
5. Factory Reset.
6. Stuck on white HTC screen.
donkeykong1 said:
How exactly did you install it? The usual way, doenloaded the OTA and let your phone upgrade? Or you took the firmware.zip and flashed it via fastboot?
Click to expand...
Click to collapse
The normal way. I got a new update message on Android. I downloaded it and let it install. It rebooted twice or three times and now after boot it's stuck at the HTC white screen.
The only thing i could imagine is the custom recovery (twrp teamwin) which should be replaced by stock before i ran the update.
Now i see reflashing stock recovery in the replies here is not helping people either...
Same here.
Unlocked, S-Off, Stock 7.19.401.22 Rom and recovery . White Screen after applying the update.
Any hints?
Same problem here.
1. Running stock ROM, downloaded OTA.
2. Flashed stock recovery 7.19.401.22 via fastboot.
3. Installed OTA (default software update tool).
4. Device rebooted into recovery, installed, rebooted.
5. Stuck at htc one logo (white screen).
Is rooted, S-ON.
khfaisal994 said:
i am facing the same problem.. i downloaded it frm settings>about>software update..
i was running teamwin recovery.. it failed to install..
thn i flashed stock recovery..
thn installed the ota frm software updates...
btw now my phn is stuck on the boot screen... plz hlp...
HTC M7UL
ROOTED
i was running 7.19.401.22
Click to expand...
Click to collapse
muschi.muscholini said:
I'm facing the same problem: Stuck on white HTC screen.
1. Saw the notice for the OTA update for 7.19.401.30.
2. Since I was running Teamwin, reflashed 7.19.401.22 stock firmware.
3. Installed OTA 7.19.401.30.
4. Stuck on black screen (nothing on it, but illuminated)
5. Factory Reset.
6. Stuck on white HTC screen.
Click to expand...
Click to collapse
Jorgo-Bo said:
Same here.
Unlocked, S-Off, Stock 7.19.401.22 Rom and recovery . White Screen after applying the update.
Any hints?
Click to expand...
Click to collapse
An3skmbi said:
Same problem here.
1. Running stock ROM, downloaded OTA.
2. Flashed stock recovery 7.19.401.22 via fastboot.
3. Installed OTA (default software update tool).
4. Device rebooted into recovery, installed, rebooted.
5. Stuck at htc one logo (white screen).
Is rooted, S-ON.
Click to expand...
Click to collapse
You all having the same problem that occurred with the 7.19.401.22 update, something wasn't 100% stock and the ota installed anyway causing a bootloop. For those having s-off, downgrade to 7.19.401.22 using a ruu to re-stock your phone and then update it to .30 before modding anything, not even installing root and it will update fine. For those stuck on the bootscreen with s-on, if your firmware is still 7.19.401.22 do same as above, if your firmware was updated to 7.19.401.30 (most likely it is) you'll need to unlock the bootloader if not already done, flash a custom recovery and restore a 7.19.401.30 nandroid backup (and flash back the 7.19.401.30 stock recovery if needed)
Thanks for your explanation. I did a RUU reset with 7.19.401.22 signed zip. After that i installed the update. All fine now. Phone is up and running again.
alray said:
You all having the same problem that occurred with the 7.19.401.22 update, something wasn't 100% stock and the ota installed anyway causing a bootloop. For those having s-off, downgrade to 7.19.401.22 using a ruu to re-stock your phone and then update it to .30 before modding anything, not even installing root and it will update fine. For those stuck on the bootscreen with s-on, if your firmware is still 7.19.401.22 do same as above, if your firmware was updated to 7.19.401.30 (most likely it is) you'll need to unlock the bootloader if not already done, flash a custom recovery and restore a 7.19.401.30 nandroid backup (and flash back the 7.19.401.30 stock recovery if needed)
Click to expand...
Click to collapse
thanks dear dev... i was thinking of doing so.. but i have something important on my phone storage... now am backing up those files using adb... thn am going for it....
many many thanks...
alray said:
You all having the same problem that occurred with the 7.19.401.22 update, something wasn't 100% stock and the ota installed anyway causing a bootloop. For those having s-off, downgrade to 7.19.401.22 using a ruu to re-stock your phone and then update it to .30 before modding anything, not even installing root and it will update fine. For those stuck on the bootscreen with s-on, if your firmware is still 7.19.401.22 do same as above, if your firmware was updated to 7.19.401.30 (most likely it is) you'll need to unlock the bootloader if not already done, flash a custom recovery and restore a 7.19.401.30 nandroid backup (and flash back the 7.19.401.30 stock recovery if needed)
Click to expand...
Click to collapse
weird, i just looked at the updater-script, and everything looks normal, first it checks all the files then performs the patches if everything matches.... did you ever figure out what the culprit was?
nkk71 said:
weird, i just looked at the updater-script, and everything looks normal, first it checks all the files then performs the patches if everything matches.... did you ever figure out what the culprit was?
Click to expand...
Click to collapse
No I did not looked at it yet. I just remember it was the same scenario with the previous ota:
Unlocked BL + custom recovery + stock rooted rom
restored stock recovery
downloaded and installed the ota update, no error during the update process
reboot and stuck at htc boot screen
I remember many ppl were having the same issue early June in the update thread, I have also experienced the same issue from 7.17.1540.7 to .21
(stock rooted, flashed back stock recovery, installed the update and phone stuck at HTC boot screen. Waited a lot thinking it was only the cache being rebuilt but after an hour, still not booted).
Very strange
Same here. I´ve installed the patch via OTA, all was running fine but the boot at the end stops at the white HTC screen.
OS 7.19.401.30, no root
I´ve tried start with power butten, out of the recovery the boot, even today a factory reset was without success. And the phone isn´t recognized by pc.
What should I do to get a working phone again?
Greetings mammaonecat
mammaonecat said:
Same here. I´ve installed the patch via OTA, all was running fine but the boot at the end stops at the white HTC screen.
OS 7.19.401.30, no root
I´ve tried start with power butten, out of the recovery the boot, even today a factory reset was without success. And the phone isn´t recognized by pc.
What should I do to get a working phone again?
Greetings mammaonecat
Click to expand...
Click to collapse
How long did you waited, first boot after an ota update can take longer (10 mins) than usual. Is your booloader unlocked/locked/re-locked?
Could someone provide me with a Nandroid backup of 7.19.401.30?
alray said:
How long did you waited, first boot after an ota update can take longer (10 mins) than usual. Is your booloader unlocked/locked/re-locked?
Click to expand...
Click to collapse
More than 30 minutes. The bootloader is locked. S-Off.
I´ve found also this: Android system recovery <3e>
LRX22G release-keys
E: missing bitmap oem_unlock_bg (Code -1)
E: missing bitmap oem_unlock_bg_yes
E: missing bitmap oem_unlock_bg_no
E: missing bitmap icon ruu (Code-1).
Greetings mammaonecat
I could not recover my data in any way... Tried whole saturday.
Just flashed RUU again and OTA's. The last OTA went fine now. After last OTA i rooted the phone again.
please give me the full stock rom of htc one m7 7.19.401.30 because i fail to flash the new update 186 mb patches... i do evry thing but i when the phone reboot to recovery mode he abrot the instalation of the update notes i m s-on i instal aroma stuck recovery and i relock the bootloader because unloking bootloader give nothing plz help
Hello everyone,
I'm having the same problem. I have an international HTC One M7. My OTA half worked (I put the stock recovery before flash), and now my phone says "7.19.401.30" when I'm in the bootloader. I am S-ON with unlocked.
Can I flash a RUU (zip format) with an older version (7.19.401.22) ? Is it possible ?
Other information, when I go into the stock recovery, I have lines of errors. Something like this :
E:missing bitmap oem_unlock_bg
E:missing bitmap oem_unlock_bg_yes
E:missing bitmap oem_unlock_bg_no
PS : I tried a usual .exe RUU but it failed.
Thanks for your help.
Loweack said:
Hello everyone,
I'm having the same problem. I have an international HTC One M7. My OTA half worked (I put the stock recovery before flash), and now my phone says "7.19.401.30" when I'm in the bootloader. I am S-ON with unlocked.
Can I flash a RUU (zip format) with an older version (7.19.401.22) ? Is it possible ?
Other information, when I go into the stock recovery, I have lines of errors. Something like this :
E:missing bitmap oem_unlock_bg
E:missing bitmap oem_unlock_bg_yes
E:missing bitmap oem_unlock_bg_no
PS : I tried a usual .exe RUU but it failed.
Thanks for your help.
Click to expand...
Click to collapse
I had the same problem. I installed the 7.19.401.22 zip from a connected USB-stick with CWM recovery and my phone booted again with all my settings and apps as they were before the update (apart from supersu)
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?
Note, this is my first attempt at rooting and flashing a custom rom.
I unlocked the bootloader and attempted to flash cm. Also used SuperSU and twsp to backup. The flash did not go through, as far as I could tell. The phone would still boot, with the warning, however once I attempted an OTA update from 4.4 to 5.0 the phone is now stuck on the unlocked bootloader warning. HELP!!!
naboyd32cp said:
Note, this is my first attempt at rooting and flashing a custom rom.
I unlocked the bootloader and attempted to flash cm. Also used SuperSU and twsp to backup. The flash did not go through, as far as I could tell. The phone would still boot, with the warning, however once I attempted an OTA update from 4.4 to 5.0 the phone is now stuck on the unlocked bootloader warning. HELP!!!
Click to expand...
Click to collapse
When in fastboot mode, device is UNLOCKED, Status Code 3, Software Status Modified. Any help would be appreciated!